Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fixed Radiobrowser - Access Error issue on some models #79
base: master
Are you sure you want to change the base?
Fixed Radiobrowser - Access Error issue on some models #79
Changes from all commits
c8ccc96
5754569
11a97c2
05a2b1e
02cf0e3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's that for? We can use
self.id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No we can't because the Access Error issue was caused by ID size limit to 15 chars in some radios. That's why we have to translate UUID (36 chars) to a fairly unique ID that will fit the limitation. Currently it is 12 chars, because with the prefix "RB_" it comes to exactly 15 chars.
I am using this dictionary in memory to avoid reading fetching the stations all over again from the remote service. While my_stations reads the stations all over again from the file, calculates ID and matches it on the fly, there are usually much more stations returned by the radiobrowser and going there twice just to find a matching UUID would be really slow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand.
Can we split this cache speed improvement off of the functionality fix? Would be nice for testing and traceability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry, I am not quite sure what you meant by that. There is no "cache speed improvement" here. Just keeping the ID-UUID dictionary of the last search response. How else would you be able to find the original station when the radio returns an ID that is nothing but a digest value that you calculated from the original station UUID?
The id_registry is absolutely necessary for this fix to work.