Update default dependencies and Synapse setup - #180
Closed
Kubuxu wants to merge 4 commits into
Closed
Conversation
Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
Contributor
Author
|
Multiple flows succeeded, multi upload one failed due to: Which I think can be tracked back to pricing changes. Should be addressed by FilOzone/synapse-sdk#928 |
39 tasks
Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
84 tasks
90 tasks
rvagg
added a commit
that referenced
this pull request
Aug 24, 2026
Instead of cloning example-storage-e2e.js and having to npm install the whole of synapse, we instead implement all of our client code in here and pull in Synapse as a dependency as it's supposed to be used. Frontier runs will still clone Synapse but will do a minimal prod npm install and avoid build. We use the Typescript directly, without compile, and rewrite the source paths from dist/ to src/ dynamically. This change also splits up the storage e2e testing in a way that's more explicit and verbose for our needs and also easier to extend to cover new variations of concerns. Closes: #179 Closes: #180
rvagg
added a commit
that referenced
this pull request
Aug 24, 2026
Instead of cloning example-storage-e2e.js and having to npm install the whole of synapse, we instead implement all of our client code in here and pull in Synapse as a dependency as it's supposed to be used. Frontier runs will still clone Synapse but will do a minimal prod npm install and avoid build. We use the Typescript directly, without compile, and rewrite the source paths from dist/ to src/ dynamically. This change also splits up the storage e2e testing in a way that's more explicit and verbose for our needs and also easier to extend to cover new variations of concerns. Closes: #179 Closes: #180
Contributor
Author
Contributor
|
oh sorry, and my fix didn't actually fix this, I'm working on properly fixing the synapse thing btw |
Kubuxu
commented
Aug 25, 2026
| pdp: Some(Location::GitCommit { | ||
| url: "https://github.com/FilOzone/pdp.git".to_string(), | ||
| commit: "cc3f5eaffee7df80471b671a4e35a42b000685b8".to_string(), | ||
| }), |
Contributor
Author
There was a problem hiding this comment.
chief changes to run new branches in CI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
3f3d9633c09bf1e8343e722f3c16daa4de7cce98maincommits for filecoin-services and PDPVerification
cargo test config::tests::default_config_uses_requested_source_revisionscargo fmt --checkgit diff --check