-
Notifications
You must be signed in to change notification settings - Fork 298
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 test connection on integration create #5328
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vstpme
added
pr:no public docs
Added to a PR that does not require public documentation updates
release:ignore
PR will not be added to release notes
labels
Dec 4, 2024
matiasb
approved these changes
Dec 4, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Dec 4, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Dec 4, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
Dec 5, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Dec 5, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Dec 5, 2024
This reverts commit 9c754e4.
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 6, 2024
# What this PR does Adds some logging for inbound email + comment on why I disabled `pytest-socket` in a [recent PR](#5328) ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
pr:no public docs
Added to a PR that does not require public documentation updates
release:ignore
PR will not be added to release notes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to https://github.com/grafana/support-escalations/issues/13751
Checklist
pr:no public docs
PR label added if not required)release:
). These labels dictate how your PR willshow up in the autogenerated release notes.