Skip to content
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.

Sign up for GitHub

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

Jump to bottom

RangeError in Windows due to AtomicFixnum limit #125

Closed
eli-darkly opened this issue Jan 31, 2019 · 1 comment
Closed

RangeError in Windows due to AtomicFixnum limit #125

eli-darkly opened this issue Jan 31, 2019 · 1 comment

Comments

@eli-darkly
Copy link
Contributor

While looking into #124, I found that there's another Windows incompatibility. In events.rb, we're using a Concurrent::AtomicFixnum to store a millisecond timestamp value. AtomicFixnum has different maximum values depending on the system architecture, and on Windows that limit is too low for the values we're storing. This is a known issue with concurrent-ruby.
@eli-darkly eli-darkly mentioned this issue Jan 31, 2019
Closed
@eli-darkly
Copy link
Contributor Author

Fixed in the 5.5.3 release.

LaunchDarklyCI pushed a commit that referenced this issue Jan 26, 2021
@eli-darkly
Merge pull request #125 from launchdarkly/eb/ch60312/precompute-reasons
ae89808 
(6.0 - #3) precompute evaluation reasons when we receive a flag
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eli-darkly