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

Investigate issue with sqlite 3.49.1 #1797

Open
emlys opened this issue Feb 19, 2025 · 2 comments
Open

Investigate issue with sqlite 3.49.1 #1797

emlys opened this issue Feb 19, 2025 · 2 comments
Assignees
Labels
critical for issues likely to obstruct the whole dev team (e.g. broken builds)

Comments

@emlys
Copy link
Member

emlys commented Feb 19, 2025

Tests are currently failing/hanging likely due to a dependency update. Currently investigating. See https://github.com/natcap/invest/actions/runs/13394893863

@emlys emlys added the critical for issues likely to obstruct the whole dev team (e.g. broken builds) label Feb 19, 2025
@emlys emlys self-assigned this Feb 19, 2025
@emlys emlys mentioned this issue Feb 19, 2025
3 tasks
@emlys
Copy link
Member Author

emlys commented Feb 19, 2025

The issue is with the latest sqlite version, 3.49.1.

@emlys emlys changed the title Tests failing on main Investigate issue with sqlite 3.49.1 Feb 19, 2025
@dcdenu4
Copy link
Member

dcdenu4 commented Feb 20, 2025

Looks like this issue here: conda-forge/sqlite-feedstock#130

dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
dcdenu4 added a commit to dcdenu4/invest that referenced this issue Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical for issues likely to obstruct the whole dev team (e.g. broken builds)
Projects
None yet
Development

No branches or pull requests

2 participants