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.

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

Make the BUILD_WITH_GEO_LIBRARIES warning fatal #1115

Merged
merged 1 commit into from
Nov 11, 2020
Merged

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented Nov 11, 2020

The BUILD_WITH_GEO_LIBRARIES feature was removed in the previous PR, and replaced with a warning that the feature is no longer supported.

After further thought I believe it would be best to make this warning fatal, to prevent unexpected failures at runtime, if consumers of the library either aren't invoked during the build, or were previously installed/cached and were dynamically linked against the library.

Continuation of #1113 / W-7654424.

The `BUILD_WITH_GEO_LIBRARIES` feature was removed in the previous PR,
and replaced with a warning that the feature is no longer supported.

After further thought I believe it would be best to make this warning
fatal, to prevent unexpected failures at runtime, if consumers of the
library either aren't invoked during the build, or were previously
installed/cached and were dynamically linked against the library.

Continuation of #1113 / @W-7654424@.
@edmorley edmorley marked this pull request as ready for review November 11, 2020 16:42
@edmorley edmorley requested a review from a team as a code owner November 11, 2020 16:42
@edmorley edmorley merged commit ce684e4 into main Nov 11, 2020
@edmorley edmorley deleted the geos-warning-fatal branch November 11, 2020 18:47
@edmorley edmorley mentioned this pull request Nov 12, 2020
dryan pushed a commit to dryan/heroku-buildpack-python that referenced this pull request Nov 19, 2020
The `BUILD_WITH_GEO_LIBRARIES` feature was removed in the previous PR,
and replaced with a warning that the feature is no longer supported.

After further thought I believe it would be best to make this warning
fatal, to prevent unexpected failures at runtime, if consumers of the
library either aren't invoked during the build, or were previously
installed/cached and were dynamically linked against the library.

Continuation of heroku#1113 / @W-7654424@.
edmorley added a commit that referenced this pull request Aug 15, 2022
Since:
- the error has been in place since Nov 2020 (#1115), so the vast
  majority of apps/users will have already seen it
- even without this explicit check, if a GDAL install fails we still print
  the standard instructions via the warnings system:
   https://github.com/heroku/heroku-buildpack-python/blob/5f896a434c29c6835395083503f4768457e9adc1/bin/warnings#L49-L58
  https://github.com/heroku/heroku-buildpack-python/blob/5f896a434c29c6835395083503f4768457e9adc1/spec/hatchet/pip_spec.rb#L227-L240

GUS-W-11593037.
pull bot pushed a commit to eloisetwaine/heroku-buildpack-python that referenced this pull request Aug 15, 2022
Since:
- the error has been in place since Nov 2020 (heroku#1115), so the vast
  majority of apps/users will have already seen it
- even without this explicit check, if a GDAL install fails we still print
  the standard instructions via the warnings system:
   https://github.com/heroku/heroku-buildpack-python/blob/5f896a434c29c6835395083503f4768457e9adc1/bin/warnings#L49-L58
  https://github.com/heroku/heroku-buildpack-python/blob/5f896a434c29c6835395083503f4768457e9adc1/spec/hatchet/pip_spec.rb#L227-L240

GUS-W-11593037.
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.

2 participants