Skip to content
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

get_djuser_name error specificity #1175

Closed
CBroz1 opened this issue Oct 31, 2024 · 0 comments · Fixed by #1192
Closed

get_djuser_name error specificity #1175

CBroz1 opened this issue Oct 31, 2024 · 0 comments · Fixed by #1192

Comments

@CBroz1
Copy link
Member

CBroz1 commented Oct 31, 2024

The following error message could be more specific

if len(query) != 1:
raise ValueError(
f"Could not find name for datajoint user {dj_user}"
+ f" in common.LabMember.LabMemberInfo: {query}"
)

The error message is written assuming the case of len(query) == 0, but a dj user name could exist twice in this table, causing confusion

CBroz1 added a commit to CBroz1/spyglass that referenced this issue Nov 20, 2024
@CBroz1 CBroz1 linked a pull request Nov 21, 2024 that will close this issue
7 tasks
@CBroz1 CBroz1 mentioned this issue Nov 27, 2024
7 tasks
edeno pushed a commit that referenced this issue Dec 5, 2024
* #1175

* #1185

* #1183

* Fix circular import

* #1163

* #1105

* Fix failing tests, close download subprocesses

* WIP: fix decode changes spikesort tests

* Fix fickle test

* Revert typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant