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

TargetJobConfig is no longer exercised and is now broken #3687

Open
charleskawczynski opened this issue Mar 11, 2025 · 0 comments
Open

TargetJobConfig is no longer exercised and is now broken #3687

charleskawczynski opened this issue Mar 11, 2025 · 0 comments

Comments

@charleskawczynski
Copy link
Member

My beloved TargetJobConfig, which I periodically use, to help find performance and latency issues, is now broken and appears to be no longer exercised.

Can we please fix this feature and keep it as a test somewhere?

I thought @nefrathenrici had hooked in a test somewhere, but I can't find it.

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

No branches or pull requests

1 participant