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

[ipfs/go-bitswap] TestCancelOneRequestDoesNotTerminateAnother is flaky #88

Open
dirkmc opened this issue Sep 10, 2020 · 1 comment
Open
Labels
need/triage Needs initial labeling and prioritization

Comments

@dirkmc
Copy link
Contributor

dirkmc commented Sep 10, 2020

Failed
=== RUN   TestCancelOneRequestDoesNotTerminateAnother
    TestCancelOneRequestDoesNotTerminateAnother: providerquerymanager_test.go:174: Collected all peers on cancelled peer, should have been cancelled immediately
--- FAIL: TestCancelOneRequestDoesNotTerminateAnother (0.01s)
@dirkmc dirkmc added the need/triage Needs initial labeling and prioritization label Sep 10, 2020
@Jorropo Jorropo changed the title TestCancelOneRequestDoesNotTerminateAnother is flaky [ipfs/go-bitswap] TestCancelOneRequestDoesNotTerminateAnother is flaky Jan 27, 2023
@welcome
Copy link

welcome bot commented Jan 27, 2023

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@Jorropo Jorropo transferred this issue from ipfs/go-bitswap Jan 27, 2023
Jorropo pushed a commit to ipfs/go-libipfs-rapide that referenced this issue Mar 23, 2023
…ies (ipfs#88)

* feat: update go-unixfs and use built in automatic sharding and unsharding
* chore: update deps

Co-authored-by: Adin Schmahmann <[email protected]>
Co-authored-by: Gus Eggert <[email protected]>

This commit was moved from ipfs/go-mfs@e61420f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant