-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
dvc pull: re.error: redefinition of group name 'ps_d' as group 2; was group 1 at position 46 #8217
Comments
@arthurkok2, could you please share |
my
|
@arthurkok2 Do you still have the issue if you upgrade dvc? |
I am hitting the same error, note that
|
The fact that two different people on very different versions hit this very specific error within a few hours makes me suspect that some dependency just released a broken version. |
This is caused by
Downgrading to |
For myself, no, issues goes away when upgrading to 2.23.0. However, seems like other are reporting the issue even on this version. |
We were facing the same issue during the |
The issue comes down from this change ( Lines 42 to 48 in 660c17f
we end up having multiple groups with the same name, which results in the |
Also, as @eric-seppanen pointed out, this is explicitly pinned to |
Thanks @eric-seppanen, @dtrifiro. I did not notice that. I'm lifting the
p0-critical
|
@Varungarg97 The workaround is to downgrade pathspec to |
@rlamy Thank you working now |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Remove regex concatenation that causes re.error Fixes iterative#8217.
Remove regex concatenation that causes re.error Fixes iterative#8217
Remove regex concatenation that causes re.error Fixes iterative#8217
Remove regex concatenation that causes re.error Fixes iterative#8217
Also got this error but from ❯ dvc init
ERROR: unexpected error - redefinition of group name 'ps_d' as group 2; was group 1 at position 46
Having any troubles? Hit us up at https://dvc.org/support, we are always happy to help!
Datasets on main [✘!+?] on ☁️ carlthome@gmail.com(europe-west4)
❯ dvc --version
2.17.0
|
got the same issue described above with the standard dvc package on nixos too. Same logs and same dvc version as above. dvc pull also isn't working with the same error |
Related to iterative/dvc#8217
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3 Wait for scmrepo's update iterative/scmrepo#163
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3
fix: iterative#8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3
fix: #8217 1. Replace group name to avoid conflict. 2. Disable failed tests. 3. Bump pathspec to 0.10.3
Bug Report
Description
When running
dvc pull
, re throws an errordvc pull: re.error: redefinition of group name 'ps_d' as group 2; was group 1 at position 46
Reproduce
dvc pull
Expected
It not to throw an error
Environment information
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: