-
Notifications
You must be signed in to change notification settings - Fork 58
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
Listing exchange keys not found instead of erroring in SDF #746
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
@romainsacchi Agree, I think we'll be seeing this issue more and more with more users using scenarios. If you think the solution you wrote was good, feel free to make it a PR. Otherwise, making it a draft PR so I have an example of your ideas and can make something permanent would be nice. If you don't have the time, I'd be happy to take this over partially, if you can put some mockup in paint of what you'd like to see for example would already be really helpful! I think there are a few things to consider:
|
@romainsacchi As a temporary fix, we now tell users how many of the total exchanges are broken.
|
Closing this as resolved in #1025 |
activity-browser/activity_browser/bwutils/superstructure/manager.py
Line 126 in 622c70d
Would it be better to print the list of exchanges not found in a popup window and maybe drop them and go on with the calculation, instead of throwing an error?
I think the error message may not be super clear to the user, plus it would not know what the faulty exchanges are.
I had to modify the code to make it export
df
to find out what the missing keys were.The text was updated successfully, but these errors were encountered: