Skip to content

Fix possible integer overflow in memory allocation in geohash_encode #23

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

Merged
merged 1 commit into from
Jan 26, 2018
Merged

Fix possible integer overflow in memory allocation in geohash_encode #23

merged 1 commit into from
Jan 26, 2018

Conversation

emirb
Copy link
Contributor

@emirb emirb commented Jan 26, 2018

No description provided.

@codecov-io
Copy link

codecov-io commented Jan 26, 2018

Codecov Report

Merging #23 into master will increase coverage by 0.12%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   67.39%   67.51%   +0.12%     
==========================================
  Files           3        3              
  Lines         506      508       +2     
==========================================
+ Hits          341      343       +2     
  Misses        165      165
Impacted Files Coverage Δ
geohash.c 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e373186...1c24b0b. Read the comment docs.

@derickr derickr merged commit b6d963b into php-geospatial:master Jan 26, 2018
@emirb emirb deleted the geohash_encode_negative_precision branch January 26, 2018 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants