Skip to content
This repository has been archived by the owner on May 11, 2023. It is now read-only.

rad-track fails to find ref refs/rad/id #259

Open
joelhans opened this issue Sep 26, 2022 · 6 comments
Open

rad-track fails to find ref refs/rad/id #259

joelhans opened this issue Sep 26, 2022 · 6 comments

Comments

@joelhans
Copy link

joelhans commented Sep 26, 2022

Could be related to #164. I'm using two systems to reproduce the issue, both on v0.6.1, but I've also experienced this issue when switching between multiple identities on the same system.

This is blocking me from updating any documentation regarding code collaboration and the patch/review commands.

Here are the steps I took to reproduce, first on my laptop:

rad auth --init
rad clone ...
cd radicle-example
... made some changes
git add .
git commit -m "..."
rad push
rad patch --sync

On my desktop:

$ rad track hyym1tmxtcsn154arxiqoya48h7h3x587reaonwnw3y9qnj3y1fmsg
Establishing 🌱 tracking relationship for radicle-example

ok Tracking relationship with hyym1tmxtcsn154arxiqoya48h7h3x587reaonwnw3y9qnj3y1fmsg established
!! Syncing peer identity rad:git:hnrkbqxunxzep8py9ysdqtsjn4748761dq91y from willow.radicle.garden...

== Command failed fatal: couldn't find remote ref refs/rad/id
@joelhans
Copy link
Author

Reproduced this again on v0.6.1, using two fresh identities and a fresh project.

➜ rad track hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag 
Establishing 🌱 tracking relationship for radicle-docs-examples

ok Tracking relationship with hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag exists
!! Syncing peer identity rad:git:hnrkgnwr4z84yhdzet97k1rxizz9n1sbca97y from pine.radicle.garden...

== Command failed fatal: couldn't find remote ref refs/rad/id

@slack-coder
Copy link
Contributor

I've recevied the

Reproduced this again on v0.6.1, using two fresh identities and a fresh project.

➜ rad track hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag 
Establishing 🌱 tracking relationship for radicle-docs-examples

ok Tracking relationship with hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag exists
!! Syncing peer identity rad:git:hnrkgnwr4z84yhdzet97k1rxizz9n1sbca97y from pine.radicle.garden...

== Command failed fatal: couldn't find remote ref refs/rad/id

Hi @joelhans, anyway you could post the steps here you used to create and test the project? Do
you know which seed node you pushed the project too?

@slack-coder
Copy link
Contributor

@joelhans you may have to ensure the same seed ID is being used.

@joelhans
Copy link
Author

joelhans commented Sep 29, 2022

I'm trying to follow the steps from this script, but just in a manual fashion so I can test the steps involved in the patch workflow.

Here are the steps I took to create the project:

git init
touch README.md
git add .
git commit -m "Initial commit"
rad init
rad push

When I ran rad push for the first time, I chose pine.radicle.garden. Git config confirms as such on both the original project dir and the cloned project dir:

git config --local rad.seed
https://pine.radicle.garden/

Passing --seed pine.radicle.garden to rad track doesn't seem to change the error.

@cloudhead
Copy link
Contributor

Whos id is this: hnrkgnwr4z84yhdzet97k1rxizz9n1sbca97y?

@joelhans
Copy link
Author

joelhans commented Oct 3, 2022

That belongs to docs-tester-two, the second test identity I created to reproduce this.

$ rad self
Profile 49a43ca4-d4fc-4f97-9c29-9d2bc38eaada
├── Name           docs-tester-two                                                                  
├── URN            rad:git:hnrkgnwr4z84yhdzet97k1rxizz9n1sbca97y                                    
├── Peer ID        hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag

Here is that user's remote on the same project: https://app.radicle.network/seeds/pine.radicle.garden/rad:git:hnrkcrkn8u6drx6aprr4ehhejio1ms4gz4mry/remotes/hydk7ntpdp9em9xhfgj4phtkjh51e18wza11uitsxjyqsqum66t3ag/tree

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants