-
Notifications
You must be signed in to change notification settings - Fork 210
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
Allow arbitrary networktables address #764
Allow arbitrary networktables address #764
Conversation
Still need to fix the UI!
Need to get validation working!
LGTM though I'd like to do some testing. Do we already have any unit tests that confirm the old settings JSON is parsed correctly? That might be good to have. |
Would need a corresponding docs PR before merge IMO. |
It does do so, but I can put a unit test together. If I do so, will the PR get approved soon, or will it still be a 2024 item? If the latter, I won't put a rush on it. Until this PR is accepted, teams do havee a workaround: put an entry for a 127.0.0.* in the /etc/hosts ("C:\Windows\System32\drivers\etc\hosts" on Windoze) file for team 9999 and using 9999 as the team number:
|
agreed. again, willing to do, but if this is getting pushed off to 2024, I won't make it a priority. how to coordinate the PRs so that the doc change does not get pulled before the code change? |
…dress' into allow_arbitrary_networktables_address
unit test done. commit 36a35d2 |
Thanks! Unit test looks good to me. I know it's low risk but I'm a little hesitant to make this change mid-season, and is probably a post-champs thing? So no rush here. |
PR should be simultaneous (or at least, the docs PR should be after the code PR). Issue: PhotonVision/photonvision-docs#271 |
oof ouch wpiformat |
boop |
Just needs wpiformat and then we can merge |
…b.com/fovea1959/photonvision into allow_arbitrary_networktables_address
This change should not be merged until PR PhotonVision/photonvision#764 is applied. Co-authored-by: Matt <[email protected]>
This change allows specification of hostnames and ip4 addresses for the team number. Helpful if you want to run photonvision on the same PC as simulated robot code; just point photonvision at "localhost", and it will connect to the simulator's network tables.
This takes care of the requested feature in #570.