-
Notifications
You must be signed in to change notification settings - Fork 21
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
2025 deal with intermittent upload error #779
Conversation
📦 Next.js Bundle AnalysisThis analysis was generated by the next.js bundle analysis action 🤖 Two Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. |
Codecov Report
@@ Coverage Diff @@
## master #779 +/- ##
=======================================
Coverage 83.86% 83.87%
=======================================
Files 473 473
Lines 8069 8074 +5
Branches 1568 1570 +2
=======================================
+ Hits 6767 6772 +5
Misses 1244 1244
Partials 58 58
Help us with your feedback. Take ten seconds to tell us how you rate us. |
From what I have seen, the origin of the error seems to be related to a chrome caching issue in the 2 calls ( |
b35cf1b
to
f0b0313
Compare
Description
Details
URL to issue
https://biomage.atlassian.net/browse/BIOMAGE-2025
Link to staging deployment URL (or set N/A)
https://ui-martinfosco-ui7791.scp-staging.biomage.net/
Links to any PRs or resources related to this PR
Integration test branch
master
Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.
Code updates
Have best practices and ongoing refactors being observed in this PR
Manual/unit testing
Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.
Documentation updates
Optional