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

support calling python scripts with arguments, by injecting them as args in scope #358

Closed

Conversation

mgor
Copy link
Collaborator

@mgor mgor commented Nov 11, 2024

No description provided.

@mgor mgor requested a review from boffman November 11, 2024 17:27
@mgor mgor force-pushed the feature/execute_python_script_args branch from 2e797c4 to 27677a4 Compare November 11, 2024 17:52
mgor added 6 commits November 13, 2024 13:07
removed pyzmq dependency, since it will come via locust.
using a dev version of locust with additional debug logging in `locust.runners`.
added additional debug logging in `grizzly.locust`.
enable DEBUG for those two loggers after configuring logging and before locust starts.

use the global Context instance when getting a Context for async-messaged handling.

use socket options ZMQ_RELAXED and ZMQ_CORRELATED, which will allow send-send on a socket, if a recv for some reason isn't registered for it.

add timestamp to when a message from influx is logged, seems to come later that the event actually was fired under certain conditions.
locust.py:
- do not call _spread_sticky_tags_on_workers in _grizzly_distribute_users, it has already been done in _prepare_rebalance
- handle KeyError, which can happen if a worker is missing

influxdb.py:
- include response_time in metrics for heartbeat_received (locust feature needed, which is on the used locust branch)

async_message/__init__.py:
- include request_id in logging

async_message/utils.py:
- start timer outside of while-loop to get correct time spent in polling for response

async_message/mq/__init__.py:
- include request_id in logging
@mgor mgor force-pushed the feature/execute_python_script_args branch from 47b841a to f3f0211 Compare November 15, 2024 14:03
@mgor mgor force-pushed the feature/execute_python_script_args branch from bc9b562 to 85042f0 Compare November 18, 2024 10:25
@mgor mgor closed this Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant