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.

Sign up for GitHub

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

Jump to bottom

Track down which dependency is logging errors #3655

Closed
busma13 opened this issue Jun 14, 2024 · 2 comments
Closed

Track down which dependency is logging errors #3655

busma13 opened this issue Jun 14, 2024 · 2 comments
Assignees
@busma13 @sotojn
Labels
bug dependencies Pull requests that update a dependency file
Milestone
v2.1

Comments

@busma13
Copy link
Contributor

busma13 commented Jun 14, 2024

E2e tests are spitting out thousands of lines of errors. We believe a dependency update from PR #3608 introduced the errors.

Example:

  ERROR  failed to read input source map: failed to parse inline source map url
v1ReplicaSetCondition.js.map
Caused by:
    relative URL without a base
    at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/swc-0.275.1/src/lib.rs:405
  ERROR  failed to read input source map: failed to parse inline source map url
v1ReplicaSetList.js.map
Caused by:
    relative URL without a base
    at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/swc-0.275.1/src/lib.rs:405
  ERROR  failed to read input source map: failed to parse inline source map url
v1ReplicaSetSpec.js.map
Caused by:
    relative URL without a base
    at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/swc-0.275
@busma13 busma13 added bug dependencies Pull requests that update a dependency file labels Jun 14, 2024
@godber godber added this to the v2.1 milestone Jun 17, 2024
@busma13
Copy link
Contributor Author

busma13 commented Jun 17, 2024

The errors are coming from @swc/core. They start showing up at version 1.4.12.

I believe this issue is referring to the problem we are having: swc-project/swc#8789

@busma13 busma13 changed the title Track down which dependency is creating errors Track down which dependency is logging errors Jun 17, 2024
@busma13
Copy link
Contributor Author

busma13 commented Jun 17, 2024

I am going to revert back to the previous version we were using (1.4.0) until there is a fix.

@busma13 busma13 mentioned this issue Jun 17, 2024
Merged
godber pushed a commit that referenced this issue Jun 18, 2024
@busma13
revert @swc/core to version 1.4.0 (#3661)
b54c210 
When upgrading `@swc/core` from v1.4.0 to v1.5.5 there was a change that
results in source mappings failing. This would print thousands of lines
of error messages in out e2e tests, but everything seems to compile
okay. To cut down this noise until there is a fix, this PR reverts the
`@swc/core` version back to 1.4.0.

More details and links here: #3655
@godber godber closed this as completed Jul 11, 2024
@busma13 busma13 mentioned this issue Jan 2, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@busma13 busma13

@sotojn sotojn

Labels
bug dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
3 participants
@godber @busma13 @sotojn