-
Notifications
You must be signed in to change notification settings - Fork 373
console: bound queue to 10 items #6486
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
Open
hannesm
wants to merge
1
commit into
ocaml:master
Choose a base branch
from
hannesm:console-bound-queue
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Maybe instead of removing items from the queue without telling anyone, we could just add one when it reaches the threshold that says that the rest hasn't been added. Though it should be a programing error on our part if this ever happens (be it a threshold value too low or something that we haven't thought of happening), so maybe just showing a warning unconditionally instead could be a solution?
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've no idea what the purpose of the commit that introduced this queue was, and what the desired semantics are: should the earliest messages be preserved? the latest ones? on which platform(s) does it matter?
depending on the answer to the questions above, I see multiple options: remove the queue entirely; only add the earliest N messages (adding a truncated message is definitively nice); or add the latest N messages (here as well a truncated message would be nice).
Maybe @dra27 who wrote the code years ago can explain his needs when he wrote that code.
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.
actually thinking about it more, i prefer the solution with the warning. This way you would have seen the need to use
OpamCoreConfig.init
almost immediately when using the library.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.
You mean a warning once when the queue is full (and messages are dropped)? Or a warning for each log message being dropped?
Honestly, from the API I read nowhere that OpamCoreConfig.set/update needs to be called at any time -- and there are sane defaults :) -- so I don't quite understand why there should be a warning, and more fundamentally I don't understand that there's a queue...
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.
The purpose is that
--cli
needs to be evaluated beforeOpamCoreConfig
because some of the environment variable might not be available with some of the values of CLI for example. So a couple of things happens beforeOpamCoreConfig.init
gets run andlog
gets called. So since the config hasn't been initialized opam doesn't know yet if something has to be shown on screen so those log messages need to be kept untilOpamCoreConfig.init
is called.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.
Thanks for your excellent explanation.