Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Config server requires restart for new remote repos
See original GitHub issueI am using Brixton.M2 and I noticed some behavior that was unexpected to me.
I started my config server, it was serving requests fine. Then I pushed a new branch to my git repo that the config server is using. I tried retrieving a plain text file (using the ResourceController’s endpoint) with the new branch as the label. The config server cannot find the label and returns an error to that effect. I thought this was strange. I sent a POST request to the config server’s /refresh endpoint thinking this might cause it to pull from the remote. However, it continues to not be able to find the new label until I restart the config server.
It would be nice if a full server restart were not required to serve newly pushed branches.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This works for me now in 1.4.0 snapshots. I assume it was fixed as a side effect (maybe with #439).
@haripriya-apptium please dont randomly comment on issues. Please open a new issue if you are having an issue, and provide as much information as possible so we can evaluate what might be wrong.