Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Build] add common to tsconfig #411

Merged
merged 2 commits into from
Apr 15, 2022

Conversation

kavilla
Copy link
Member

@kavilla kavilla commented Apr 15, 2022

Description

Need to include common to be compiled down with the release
artifact

Signed-off-by: Kawika Avilla kavilla414@gmail.com

Issues Resolved

#410

Check List

  • New functionality includes testing.
    • All tests pass, including unit test, integration test and doctest
  • New functionality has been documented.
    • New functionality has javadoc added
    • New functionality has user manual doc added
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Need to include common to be compiled down with the release
artifact.

Issue resolved:
opensearch-project#410

Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
@codecov-commenter
Copy link

codecov-commenter commented Apr 15, 2022

Codecov Report

Merging #411 (fc23904) into main (5421f98) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #411      +/-   ##
============================================
- Coverage     70.40%   70.35%   -0.06%     
  Complexity       81       81              
============================================
  Files           123      123              
  Lines          3849     3849              
  Branches        612      612              
============================================
- Hits           2710     2708       -2     
- Misses          960      962       +2     
  Partials        179      179              
Flag Coverage Δ
dashboards-notifications 86.40% <ø> (ø)
opensearch-notifications 60.33% <ø> (-0.09%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...rch/notifications/action/SendNotificationAction.kt 72.72% <0.00%> (-9.10%) ⬇️
.../notifications/action/PublishNotificationAction.kt 72.72% <0.00%> (-9.10%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5421f98...fc23904. Read the comment docs.

@qreshi
Copy link
Contributor

qreshi commented Apr 15, 2022

@kavilla Was this always a requirement? Dashboards didn't fail to come up when I was testing Notifications locally. How can we reproduce this on our side in the future to avoid catching at the time of the full distribution build?

Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
@kavilla
Copy link
Member Author

kavilla commented Apr 15, 2022

@qreshi yeah it would be acceptable with TypeScript files but when we compile down the files when producing a release artifact we have to tell the compiler to include these files.

@qreshi
Copy link
Contributor

qreshi commented Apr 15, 2022

Looks like since common was missing from the produced artifact it wouldn't be caught unless the built artifact was used to test with.

This can probably be added to the GitHub Actions workflow later so it uses the built artifact and catches discrepancies like this.

@qreshi
Copy link
Contributor

qreshi commented Apr 15, 2022

Created an issue for tracking the above: #412

@peterzhuamazon peterzhuamazon merged commit 793831a into opensearch-project:main Apr 15, 2022
@kavilla kavilla deleted the avillk/add_common branch April 15, 2022 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG][RUNTIME][2.0.0] NotificationsDashboards case dashboards not able to start with MODULE_NOT_FOUND
5 participants