Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove dependency between curator and web #229
Comments
This comment has been minimized.
This comment has been minimized.
|
Option no. 1 was what I was leaning toward in the beginning but was time-constrained against. Go ahead and implement that. |
This comment has been minimized.
This comment has been minimized.
|
Also, I had not been aware of the non-blocking send idiom: var ch = someChannel
select {
case ch <-foo:
// ch is able to receive.
default:
// ch is unavailable.
}Fascinating. |
This comment has been minimized.
This comment has been minimized.
|
Yep. Works for reads as well: http://play.golang.org/p/ql0qSUVXeX |
This comment has been minimized.
This comment has been minimized.
|
Great. Please keep this insights up. They are really appreciated. If you want to verbally work with me in compiling a list of smells, I will be happy to pay special attention to these in the design and code review process. |
This comment has been minimized.
This comment has been minimized.
|
The old storage is gone. Closing this. |
juliusv
closed this
Dec 10, 2014
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
bernerdschaefer commentedMay 7, 2013
Since curation is a core prometheus feature, and reporting the current status on the HUD is not, this communication shouldn't happen through potentially blocking channel communication.
Proposal 1 (preferred)
Introduce a new struct which atomically reads/updates the curation state. It's simpler, and has the advantage that the curator and web are only synchronized when the status page is requested. Something like:
Proposal 2
Change the current status updates to nonblocking sends, e.g.: