Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEATURE] core-cli query node should also contain position and geo

See original GitHub issue

Is your feature request related to a problem? Please describe.

We often use external (bash/python) scripts to interact with or visualize different aspects of the simulation. coresendmsg and core-cli can be used to update positions but for external tools to extract the position we always parse the *.xy files in the filesystem as core-cli query node -i 39983 -n 1 only delivers the following output:

ID   | Name    | Type
1    | n1      | DEFAULT
Connected To | ID  | MAC Address       | IP4 Address        | IP6 Address
wlan3        | 0   | 00:00:00:aa:00:00 |       | 2001::10/128

Describe the solution you’d like

Either adding pos/geo to the default output or add a verbose flag that will contain these information would be really helpful - also for interactive debugging of headless simulations. Similarly, having query session have all positions/geo locations in a tabular view for all nodes at once would be really nice!

Describe alternatives you’ve considered

--json does seem to contain these information but also much more. This behavior is kind of undocumented. It took me a while to find this. It’s fine for automated parsing but pretty overwhelming for interactive analyses.

Thank you for the great work so far!

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

bharndencommented, Mar 22, 2022

adding the json flag back, which will have similar values, some cases may not be directly protobuf translation, but the session dump will be.

also adding geo output to the session overview for the simple printed view, hopefully these are ok for now.

these are on develop for next release.

bharndencommented, Mar 21, 2022

I think your asks are reasonable, I would probably look to add the json support back in with the caveat you noted, that it could change if the related protobufs change. That might be reasonable to deal with though and ideally don’t end up changing often/much.

Read more comments on GitHub >

github_iconTop Results From Across the Web

coreemu - Bountysource
Describe the bug. Updating the geo position of a node during runtime using core-cli produces an error. To Reproduce Steps to reproduce the...
Read more >
Search Geospatially — Node.js - MongoDB
You can query data based on geographical location using geospatial query operators. ... This section contains examples of geospatial queries using different ...
Read more >
Mongoose geo query does not return correct result
It's not a GeoJSON field. Because a GeoJSON has to be included a coordinate type value like the following; location: { 'type': {...
Read more >
Query a feature layer (spatial) | Overview - ArcGIS Developers
A feature layer can contain a large number of features stored in ArcGIS . To access a subset of the features, you can...
Read more >
Super fast proximity searches of geo coordinates. - GitHub
This Node module provides everything you need to get proximity information for geo locations. More specifically: Fast querying of nearby locations to a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found