-
Notifications
You must be signed in to change notification settings - Fork 13
[org-node] Bug: Failed to send update refs request to client: receive failed #70
Comments
@cloudhead any chance this would be due to using an org with the address of Other thoughts, maybe the state of the repo is stale on my end? Let's sync next week when you're available. Will make some more progress on rad subscribe and ssh signing implementations and try to debug this in the process. |
Pretty sure this is due to a divergent branch between upstream and local repo, but we probably need to handle this error a little more gracefully than calling |
Hmm, actually I am not sure this is the issue. It might be, but it seems there may be another issue at play. @cloudhead if you have time tomorrow let's try to sync and walk through it for sanity check purposes. Also, this is occurring in the UpdateRefs handler, and not the set head method. The bizarre thing is that when I look at the mono repo git tree, the ref appears to be there, but when attempting to set the symbolic reference, it errors, suggesting the target does not exist. Possibly corrupted mono-repo? |
As far as I can tell, this is due to a replication bug: radicle-dev/radicle-link#782 I don't think it should happen in normal scenarios, ie. if things are working correctly, though I guess it's possible if the server shuts down abruptly in the middle of replication, so we need a way to handle that. |
I'm encountering the same issue in my local setup:
|
I'll see if we can be more graceful about this. |
Let me know a good time to get a pair programming session together. It's going to need to be early morning my time, somewhere around 4-5am PST. Just send me a msg on discord. |
I see some works on #77, let me know if there is anything I can assist with. |
Closing as we haven't this pop up in a while. |
While testing rad subscribe, noticing error when attempting to send req requests to client, exiting with a receive failed.
Also appears maybe the monorepo project I have could be corrupted? e.g. panics on
reference target must exist
.Possibly due to changing location of org-node socket.The text was updated successfully, but these errors were encountered: