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
Fix Windows installer to correctly detect running Kolibri #8083
Conversation
@radinamatic @micahscopes Can you try to find the actual
Evaluates to something? Otherwise wouldn't it just be |
@jonboiser That's the first thing both @rtibbles and @micahscopes asked for, but PID files were apparently OK 😕 |
The most confusing thing here is that it is picking up a discrete line in the PID file, it's just picking up the third line instead of the second. |
Additional testing of a stripped down version of the PID reading code running against a Kolibri server shows very consistent output - always picking up the correct port, and returning nothing when the port is not available to be read. Really not sure what is causing this to go awry in production. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, thank you @rtibbles! 👍🏽
For posterity - @micahscopes had made the correct fix, but we needed to rebuild the exe and commit it to the repo for the fix to take effect. |
Summary
This integrates a fix for the Windows installer, so that the installer gets the correct port information from
server.pid
when putting together a running Kolibri instance's base URL.References
server.pid
for port info kolibri-installer-windows#188Reviewer guidance
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)