Skip to content

Conversation

brendanm2025
Copy link

We’ve implemented a temporary fix that should restore Gitpod environment usability. We’ve tweaked the Gitpod environment code so that it deletes the buggy file (build/cp310/_version_meson.py) at the end of the Gitpod build process. Now, contributors should be able to run pandas immediately upon opening it in Gitpod. We’ve yet to solve the underlying issue, but this patch resolves Issue #59459.

Updated the tasks when setting up the Gitpod environment. All command line output during setup should now be logged into a file (setup.log), and echos are done before each segment of setup. This way, we should be able to narrow down the exact command that causes the weird pandas version to be downloaded.
Changed lines 176 - 190, just gonna see what happens when we try to build the project w/ Gitpod
It sorta worked, but not exactly.
Let's see if this fixes it
Removed faulty file from gitpod cp310 folder causing a build error when using the gitpod environment.
For bug fix
Copy link
Contributor

github-actions bot commented Jan 9, 2025

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

@github-actions github-actions bot added the Stale label Jan 9, 2025
@mroeschke
Copy link
Member

Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.

@mroeschke mroeschke closed this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DOC: Development on Gitpod have problems

2 participants