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
The freespace
informer is broken for 32-bit architectures
#202
Labels
exp/novice
Someone with a little familiarity can pick up
kind/bug
A bug in existing code (including security flaws)
P1
High: Likely tackled by core team if no one steps up
Comments
hsanjuan
added
kind/bug
A bug in existing code (including security flaws)
exp/novice
Someone with a little familiarity can pick up
status/in-progress
In progress
P1
High: Likely tackled by core team if no one steps up
labels
Oct 26, 2017
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
This should fix tests. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
Closed
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
This should fix tests. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
hsanjuan
added a commit
that referenced
this issue
Oct 26, 2017
Fix #202: Fix informers and allocators for 32-bit architectures
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/novice
Someone with a little familiarity can pick up
kind/bug
A bug in existing code (including security flaws)
P1
High: Likely tackled by core team if no one steps up
It turns out that 10GB of
StorageMax
> than 32bit and we useint
all around for metrics.Fix upcoming...
The text was updated successfully, but these errors were encountered: