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

[bug] parallel calling fGetObject() using local cache will cause unexpected error #1005

Open
fishbar opened this issue Feb 15, 2022 · 0 comments

Comments

@fishbar
Copy link

fishbar commented Feb 15, 2022

the local tmp file for speed up download is dangeruos! when the fGetObject() is parallel called with same arguments,
the cache file will be polluted, the cache file will be filled with origin file’s fragment in chaos order(deps on each caller network loading speed)
image

node js example:
image

so the local cache shoud be banned by default, for Advanced User using option to enable it

@fishbar fishbar changed the title [bug] parallel calling fGetObject(). with local cache will cause unexpected error when [bug] parallel calling fGetObject() using local cache will cause unexpected error Feb 15, 2022
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

No branches or pull requests

1 participant