-
Notifications
You must be signed in to change notification settings - Fork 48
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
chore(metrics): init Metrics in app init, cleanup setup code to one b… #1167
Open
Avantol13
wants to merge
14
commits into
master
Choose a base branch
from
chore/metrics-cleanup
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
0a8556b
chore(metrics): init Metrics in app init, cleanup setup code to one b…
Avantol13 e04afeb
chore(ci): don't run every check twice on prs
Avantol13 986b93e
Update fence/__init__.py
Avantol13 f1279cc
chore(refactor): non-flask specific directory, address review comments
Avantol13 f47ef83
chore(docs): add details about running unit tests
Avantol13 5f80e58
chore(lock): use updated library
Avantol13 6275a44
Merge branch 'master' into chore/metrics-cleanup
Avantol13 3b9fc15
chore(links): correct microsoft links so they resolve
Avantol13 7b8a1b1
Merge remote-tracking branch 'origin/chore/metrics-cleanup' into chor…
Avantol13 a41aa20
fix(links): use new microsoft learning links to docs
Avantol13 f5a0304
chore(docs): update docstring
Avantol13 868fdf2
fix(links): fix broken docs links
Avantol13 97a24f5
fix(metrics): fix path to setup prometheus file
Avantol13 68abf8c
chore(deps): relock, new version
Avantol13 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
#!/usr/bin/env bash | ||
# This script is called by: | ||
# UWSGI during startup, this gets moved to the /fence directory in the Dockerfile | ||
# - It prepares the prometheus_multiproc_dir folder to store the metrics from separate uwsgi workers (per PID) | ||
# run.py | ||
# - So local runs setup necessary environment vars and folders for prometheus metrics | ||
# Test framework in conftest | ||
# - So test runs setup necessary environment vars and folders for prometheus metrics | ||
|
||
# Usage: | ||
# ./script_name.sh [DIR] [true] | ||
|
||
# Default directory if no argument is provided | ||
DIR=${1:-/var/tmp/uwsgi_flask_metrics} | ||
|
||
# Determine whether to wipe the directory (default is to wipe) | ||
SETUP_DIR=${2:-true} | ||
|
||
set -ex | ||
|
||
if [[ "$SETUP_DIR" == "true" ]]; then | ||
echo "setting up $PROMETHEUS_MULTIPROC_DIR. clearing existing files, ensuring it exists, chmod 755" | ||
rm -Rf "$DIR" | ||
mkdir -p "$DIR" | ||
chmod 755 "$DIR" | ||
fi | ||
|
||
if id -u nginx &>/dev/null; then | ||
chown "$(id -u nginx)":"$(id -g nginx)" "$DIR" | ||
fi | ||
|
||
export PROMETHEUS_MULTIPROC_DIR="$DIR" | ||
echo "PROMETHEUS_MULTIPROC_DIR is $PROMETHEUS_MULTIPROC_DIR" |
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
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
There can be edge cases where the "automatic merge" messes something up, and the CI succeeds on the "branch run", but fails on the "PR run". In that case you have to update your branch manually and fix the conflict that git didn't see. It has happened to me a handful of times, not sure it's worth running the CI twice on every PR, but 🤷♀️
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.
Does it happen in other repos? which automatic merge are you referring to?
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.
it can happen in any repo
i can't find documentation about it but this is my understanding from what i observed:
when 2 checks run (for push and for PR) they're not necessarily running on the same code. The "push" check runs on the branch's code, and the "PR" check runs on the code that would be on master after merging the PR. If there are any changes on master that aren't on the branch, it performs a merge automatically and runs the CI on that. It's the same code that would end up on master if you choose to merge without updating your branch first - git/github finds no conflict and merges. Occasionally it does it wrong, and it can be caught by the "PR" CI check
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.
We should be protected against people merging without first updating their branch, at which point the push should run again. I do remember issues in the past vaguely... but I can't find any documentation in GH Actions that leads me to believe it's necessary to have both of these. Unless you have a strong opinion, I would rather not run everything twice and just get feedback on the code on
main
when the branch-creator merges it in and pushes those commits.