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

fix: migrate from forked file-type to original #192

Merged
merged 3 commits into from
Mar 10, 2025

Conversation

SgtPooki
Copy link
Member

@SgtPooki SgtPooki commented Mar 6, 2025

Title

fix: migrate from forked file-type to original

Description

Tests currently failing locally

Related #191 (comment)

Notes & open questions

seems to make no difference in size.. this is expected and ideal.

Before change:

image

After change:

image

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation if necessary (this includes comments as well)
  • I have added tests that prove my fix is effective or that my feature works

@SgtPooki SgtPooki requested a review from a team as a code owner March 6, 2025 17:22
Copy link
Member Author

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

self review

@SgtPooki SgtPooki marked this pull request as draft March 6, 2025 18:08
@SgtPooki
Copy link
Member Author

SgtPooki commented Mar 6, 2025

This is not passing locally on macos for me.. even after pulling down a fresh clone for this branch. So i am not sure we can switch back to file-type yet.

@2color
Copy link
Member

2color commented Mar 7, 2025

I ran the tests with this PR locally it passed (for node.js). Which test failed for you @SgtPooki? Was it in a browser runtime?

@SgtPooki
Copy link
Member Author

SgtPooki commented Mar 7, 2025

I ran the tests with this PR locally it passed (for node.js). Which test failed for you @SgtPooki? Was it in a browser runtime?

It was gateway conformance..

@helia/verified-fetch-gateway-conformance:          TestDagPbConversion has a success rate of at least 35.38%:
@helia/verified-fetch-gateway-conformance:      Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/sgtpooki/code/work/ipshipyard/ipfs/helia-verified-fetch/packages/gateway-conformance/dist/src/conformance.spec.js)

i'm thinking I need a restart.. it's failing on other runs too.. not sure what's going on. I think since it passed in CI and passed for you we can proceed.. I will update this PR once #193 is in (or I can update file-type in that pr)

Copy link
Member Author

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

self review

@SgtPooki SgtPooki marked this pull request as ready for review March 10, 2025 19:22
@SgtPooki SgtPooki merged commit 28320e1 into main Mar 10, 2025
20 checks passed
@SgtPooki SgtPooki deleted the chore/use-file-type-unforked branch March 10, 2025 19:29
github-actions bot pushed a commit that referenced this pull request Mar 10, 2025
## [@helia/verified-fetch-v2.6.1](https://github.com/ipfs/helia-verified-fetch/compare/@helia/verified-fetch-2.6.0...@helia/verified-fetch-2.6.1) (2025-03-10)

### Bug Fixes

* migrate from forked file-type to original ([#192](#192)) ([28320e1](28320e1))
Copy link

🎉 This PR is included in version @helia/verified-fetch-v2.6.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants