quinnj opened a new issue, #463: URL: https://github.com/apache/arrow-julia/issues/463
For the last couple of releases, I've been receiving the following docs page build error as an email: <img width="973" alt="image" src="https://github.com/apache/arrow-julia/assets/2896623/62b9dd7a-1821-441e-bb97-ad2fb6e9072e";> I originally thought this was just some configuration error in our own Julia-doc-building stack, but since those have been resolved, the 2.6.2 release seems to have successfully been generated/built: https://github.com/apache/arrow-julia/tree/gh-pages/v2.6.2, but navigating to the docs page: https://apache.github.io/arrow-julia/stable/, still redirects to a very old release (2.2.0), which confirms the email saying the pages build error is preventing the docs site from reflecting the accurate current version. Doing a little googling on the email error message, I found a thread where [this comment](https://github.com/orgs/community/discussions/9104#discussioncomment-5315485) specifically mentioned that if the org is is on a legacy billing plan, then that can lead to this build error. @kou, can I ask for your help in trying to confirm if this is what the core issue is for us? Is the apache GitHub org on the legacy billing plan, thus preventing our GitHub Pages from having symlinks? It would at least be helpful to confirm if that's the issue, though I don't know what exactly would be the next steps from that point (is there a way to push the apache org to use the non-legacy billing system? perhaps we need to manually restructure how we do the doc generation/symlinks for the repo?). Also a friendly ping to [yoannchaudet](https://github.com/yoannchaudet) in case they are in a position to help diagnose the issue for us here, since they seemed so helpful in other threads involving this kind of GH pages error. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
