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

Having more than two farms causes the first farm call to be delayed until it's called again #99

Open
ConnorDY opened this issue Oct 18, 2019 · 2 comments

Comments

@ConnorDY
Copy link

ConnorDY commented Oct 18, 2019

Steps for re-creating the issue:

  1. Setup two farms
  2. Call both farms
  3. They both fire as soon as they're called as expected
  4. Setup a third farm
  5. Call any of the farm
  6. Call that farm again

You'll notice the first and second call fire when the second call is made.

EDIT:
This only occurs when I'm running this locally on my Mac.
It appears to work fine when deployed on linux.

@ConnorDY ConnorDY changed the title Have more than two workers causes the first worker call to be delayed until it's called again Having more than two workers causes the first worker call to be delayed until it's called again Oct 18, 2019
@ConnorDY ConnorDY changed the title Having more than two workers causes the first worker call to be delayed until it's called again Having more than two farms causes the first worker call to be delayed until it's called again Oct 18, 2019
@ConnorDY ConnorDY changed the title Having more than two farms causes the first worker call to be delayed until it's called again Having more than two farms causes the first farm call to be delayed until it's called again Oct 18, 2019
@rvagg
Copy link
Owner

rvagg commented Oct 20, 2019

@ConnorDY I don't suppose you could come up with a test case that triggers this? Having a test that we could make pass might be the best way to get this addressed. I simply don't have time to investigate it myself.

@rvagg
Copy link
Owner

rvagg commented Oct 20, 2019

^ by "test case", I mean a PR that introduces a change to the test suite here that would fail under the conditions you mention.

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

2 participants