# Release preparation v1.76

**URL:** <https://forum.storj.io/t/release-preparation-v1-76/22151>\
**Category:** STORJLINGS\
**Created:** [April 3, 2023, 11:16am UTC](https://forum.storj.io/t/release-preparation-v1-76/22151 "2023-04-03T11:16:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [April 6, 2023, 10:16am UTC](https://forum.storj.io/t/release-preparation-v1-76/22151/2 "2023-04-06T10:16:40Z")

</div>

> [@littleskunk](#):
>
> [58f465c](https://github.com/storj/storj/commit/58f465c) storagenode/piecestore: improve cancelation detection logic

The nodes which have updated to this version have started spitting out the following error from time to time.  
`2023-04-06T09:52:30.270Z ERROR piecestore upload failed {EU1.storj.io, "PUT", "error": "context canceled", "errorVerbose": "context canceled\n\tstorj.io/common/rpc/rpcstatus.Wrap:75\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Upload.func5:498\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Upload:529\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:243\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:33\n\tstorj.io/common/rpc/rpctracing.(*Handler).HandleRPC:61\n\tstorj.io/common/experiment.(*Handler).HandleRPC:42\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:124\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:66\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:114\n\tstorj.io/drpc/drpcctx.(*Tracker).track:35", s2319360}`

Please ignore some alterations I made to make the logs more informative/compact. What I think is going on here is that this drpc closed error occurs when the piece is already committed but the error is a typical cancelation error, which now gets classified as failed upload.  
What I don’t really know is whether in this case the node gets to keep the piece or it gets cleaned up in garbage collection. Either way, this seems like either a canceled or a successful transfer that wasn’t canceled quick enough to prevent it form being committed.

---

_[View the full topic](https://forum.storj.io/t/release-preparation-v1-76/22151)._
