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

Fix Padrino instrumentation causing boot loop #1143

Merged
merged 1 commit into from
Jul 4, 2024
Merged

Conversation

tombruijn
Copy link
Member

@tombruijn tombruijn commented Jul 3, 2024

Apply the same boot loop fix as for Sinatra for Padrino from PR #1105.

For Sinatra apps noticed in our test setup that when I added a Sinatra app to the Rails app, and loaded the Sinatra instrumentation as specified in our docs it would get stuck in a boot loop. This was caused by the two different configs overwriting each other every time.

Apply the same fix for Padrino by checking first if AppSignal has already started and skipping the auto start.

Part of #329
Based on #1142

Apply the same boot loop fix as for Sinatra for Padrino from PR #1105.

For Sinatra apps noticed in our test setup that when I added a Sinatra
app to the Rails app, and loaded the Sinatra instrumentation as
specified in our docs it would get stuck in a boot loop. This was caused
by the two different configs overwriting each other every time.

Apply the same fix for Padrino by checking first if AppSignal has
already started and skipping the auto start.
Copy link
Contributor

@unflxw unflxw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder, instead of applying this fix on each integration, would it make sense for Appsignal.start to do nothing if AppSignal has already been initialised?

@tombruijn
Copy link
Member Author

I wonder, instead of applying this fix on each integration, would it make sense for Appsignal.start to do nothing if AppSignal has already been initialised?

Yes, that's definitely something I have in mind too. I would want to make that change in a major version release to avoid shipping breaking changes for some apps. So... I have ideas for Ruby gem version 4 ;)

@tombruijn tombruijn changed the base branch from padrino-middleware to main July 4, 2024 06:46
@tombruijn tombruijn merged commit 10722b6 into main Jul 4, 2024
117 checks passed
@backlog-helper
Copy link

backlog-helper bot commented Jul 4, 2024

  • This Pull Request has been closed or merged, but is still in a column that is considered to be 'in progress'. Please move the Pull Request to the 'Done' column when no more work will be done on this. - (More info)

This is a message from the daily scheduled checks.

New issue guide | Backlog management | Rules | Feedback

@tombruijn tombruijn deleted the padrino-fix-boot-loop branch July 10, 2024 18:36
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.

3 participants