-
Notifications
You must be signed in to change notification settings - Fork 133
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
fix(RHINENG-10654): Reimplement Sentry #2881
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2881 +/- ##
===========================================
- Coverage 63.44% 48.00% -15.44%
===========================================
Files 202 105 -97
Lines 4650 2552 -2098
Branches 858 468 -390
===========================================
- Hits 2950 1225 -1725
+ Misses 1689 917 -772
- Partials 11 410 +399
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exposed federated modules are failing to be build. Here is the common error:
ERROR in ./src/components/FavoriteServices/DashboardFavorites.tsx
Module build failed (from ./node_modules/swc-loader/src/index.js):
Error: Bindings not found.
at Compiler.<anonymous> (/home/martin/insights/insights-chrome/node_modules/@swc/core/index.js:227:19)
at Generator.next (<anonymous>)
at /home/martin/insights/insights-chrome/node_modules/@swc/core/index.js:31:71
at new Promise (<anonymous>)
at __awaiter (/home/martin/insights/insights-chrome/node_modules/@swc/core/index.js:27:12)
at Compiler.transform (/home/martin/insights/insights-chrome/node_modules/@swc/core/index.js:203:16)
at Object.transform (/home/martin/insights/insights-chrome/node_modules/@swc/core/index.js:352:21)
at Object.<anonymous> (/home/martin/insights/insights-chrome/node_modules/swc-loader/src/index.js:97:21)
@ container entry ./DashboardFavorites[0]
8664357
to
e0ebc19
Compare
I believe the issue is the tsconfig, "sourceRoot": "/", |
ci keeps failing because it cant find the container for this PR |
/retest |
1 similar comment
/retest |
converting to draft for a bit. I need to find a better way to map the source maps. there are too many with no refs |
4da0c29
to
ae816c2
Compare
ae816c2
to
38c88f0
Compare
it fails because the package.json file is missing from the directory /opt/app-root/src/ inside the container. Has this happened before? @Hyperkid123 |
@adonispuente you can ignore the Jenkins issues. The pipeline is broken nd will be fixed once we migrate to konflux. |
/retest |
4168a53
to
73bcacd
Compare
Just a heads up, this PR seems to be causing a webpack-dev-server issue and looping forever in some jenkins jobs. 12:21:01 [webpack-cli] TypeError: Cannot read properties of undefined (reading 'constructor')
12:21:01 at /home/tester/workspace/node_modules/webpack-dev-server/lib/Server.js:1860:22
12:21:01 at Array.find (<anonymous>)
12:21:01 at /home/tester/workspace/node_modules/webpack-dev-server/lib/Server.js:1859:60
12:21:01 at Array.forEach (<anonymous>)
12:21:01 at Server.initialize (/home/tester/workspace/node_modules/webpack-dev-server/lib/Server.js:1846:17)
12:21:01 at Server.start (/home/tester/workspace/node_modules/webpack-dev-server/lib/Server.js:3358:16)
12:21:01 at async Command.<anonymous> (/home/tester/workspace/node_modules/@webpack-cli/serve/lib/index.js:158:21)
12:21:01 at async Command.parseAsync (/home/tester/workspace/node_modules/commander/lib/command.js:935:5)
12:21:01 at async Command.<anonymous> (/home/tester/workspace/node_modules/webpack-cli/lib/webpack-cli.js:1356:13)
12:21:01 at async Command.parseAsync (/home/tester/workspace/node_modules/commander/lib/command.js:935:5)
12:21:03 making HTTP(S) head request to url:https://127.0.0.1:1337/webpack-dev-server ...
12:21:03 (node:82) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS
|
73bcacd
to
b41e5ad
Compare
/retest |
@Hyperkid12 Everything else is passing other than synk. I dont have access to view why its failing. Can you give me perms? |
It's just a random thing in package.json nothing you should need to be worried about. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something is wrong with the build process. Here is how I can reproduce issues in my machine.
- run
npm ci
- run
npm run build
- run
npm i
- run
npm run build
If I try to run build after regular dependency install, the build fails with:
assets by status 9.45 KiB [cached] 8 assets
runtime modules 9.36 KiB 14 modules
built modules 237 bytes [built]
modules by path ./src/components/FavoriteServices/*.tsx 78 bytes
./src/components/FavoriteServices/LandingNavFavorites.tsx 39 bytes [built] [code generated] [1 error]
./src/components/FavoriteServices/DashboardFavorites.tsx 39 bytes [built] [code generated] [1 error]
./src/index.ts 39 bytes [built] [code generated] [1 error]
container entry 42 bytes [built] [code generated]
./src/pdf/DownloadButton.tsx 39 bytes [built] [code generated] [1 error]
./src/layouts/SatelliteToken.tsx 39 bytes [built] [code generated] [1 error]
ERROR in ./src/components/FavoriteServices/DashboardFavorites.tsx
Module build failed (from ./node_modules/swc-loader/src/index.js):
Error: Bindings not found.
at Compiler.<anonymous> (/Users/martin/insights/insights-chrome/node_modules/@swc/core/index.js:227:19)
at Generator.next (<anonymous>)
at /Users/martin/insights/insights-chrome/node_modules/@swc/core/index.js:31:71
at new Promise (<anonymous>)
at __awaiter (/Users/martin/insights/insights-chrome/node_modules/@swc/core/index.js:27:12)
at Compiler.transform (/Users/martin/insights/insights-chrome/node_modules/@swc/core/index.js:203:16)
at Object.transform (/Users/martin/insights/insights-chrome/node_modules/@swc/core/index.js:352:21)
at Object.<anonymous> (/Users/martin/insights/insights-chrome/node_modules/swc-loader/src/index.js:97:21)
@ container entry ./DashboardFavorites[0]
...
Until this is eliminated, I can't merge the PR.
a78614f
to
15847d2
Compare
@Hyperkid123 After investigating the issue you described, this seems to be an issue with master branch. Currently on master, Deleteing package.lock file and then running |
@adonispuente we do not have the build issues on other branches. The changes to the build must be the root cause. The cypress component tests have their own webpack configuration. I suggest trying to poking awround there. |
355ea5f
to
3c544b7
Compare
3c544b7
to
882a33b
Compare
@Hyperkid123 I believe we're ok now. I wasnt able to replicate the errors you mentioned after running your flow with this version of the PR. |
@adonispuente when i run Other than that I think we are good now. let me just do one more pass over the code. |
This reconfigures sentry so that it handles multiple frontends properly with chrome being the wrapper.
Currently there are a few changes I need to make in the settings of the repo itself to add secret keys to the environment, as well as a CI/CD addition, but these changes will allow the projects to be better monitored. I dont have perms for this and will ping platform team in regards to the set up aspect, those changes must be merged for this to work at all
This is step 1, but by the end, ideally, the cp-001 project will only report errors sentry deems is from chrome, and all the apps will have their own projects where we can monitor the health of specific apps.
All the apps would need to do after this is done is have a similar PR like this : https://github.com/RedHatInsights/insights-advisor-frontend/pull/1268/files
and then some CI/CD changes + secret variables added
https://issues.redhat.com/browse/RHINENG-10654