-
Notifications
You must be signed in to change notification settings - Fork 81
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
use of closed file #90
Comments
Hi @tcurdt, Have you tried with
|
Thanks for the pointer. I don't think I tried. But my main gripe is the useless error message. It should be better no matter what. |
Fixed at #99 |
marcelosalloum
added a commit
to lightsail-network/java-stellar-sdk
that referenced
this issue
Aug 8, 2022
### What Fix the deployment CI that uploads the jar to the GitHub release by updating the image version of cibuilds/github from `0.10` to `0.13`. ### Why Close #449. In an attempt to fix the deploy job, that's failing at: https://github.com/stellar/java-stellar-sdk/blob/b2a93410a39f7b39f4dbb8e462214ae119a3996b/.circleci/config.yml#L20-L29 With the error message: ```text Failed to upload one of assets: one of the goroutines failed: failed to upload asset: /root/project/build/libs/stellar-sdk.jar: failed to upload release asset: /root/project/build/libs/stellar-sdk.jar: stat /root/project/build/libs/stellar-sdk.jar: use of closed file ``` Example of a failed deploy: [deploy (669)](https://app.circleci.com/pipelines/github/stellar/java-stellar-sdk/539/workflows/de14000a-07fe-481c-8707-787d3f58bd48/jobs/669/steps) This error seems to have been fixed at tcnksm/ghr#99 and released in version `0.11.0`. Also referenced in tcnksm/ghr#90.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to test the re-upload of a release
Honestly I have no clue what that error message is trying to tell me. "use of closed file"?
I figured I delete the asset on github and try again - which then worked.
So I see two issues:
The text was updated successfully, but these errors were encountered: