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

Do not strictly enforce resource resolution in pyodide #7646

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

philippjfr
Copy link
Member

@philippjfr philippjfr commented Jan 21, 2025

In our optimized pyodide wheels we do not ship various resources, which means that when we attempt to resolve the resources it will error. Therefore we do not enforce the strict resolution and simply assume the file(s) will be present.

Copy link

codecov bot commented Jan 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.78%. Comparing base (7d7cb17) to head (f10b47b).
Report is 3 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #7646       +/-   ##
===========================================
+ Coverage   71.79%   86.78%   +14.98%     
===========================================
  Files         345      346        +1     
  Lines       52216    52217        +1     
===========================================
+ Hits        37488    45315     +7827     
+ Misses      14728     6902     -7826     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@philippjfr philippjfr merged commit b92f0c9 into main Jan 21, 2025
17 checks passed
@philippjfr philippjfr deleted the pyodide_resource_fallback branch January 21, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant