Opened 2 years ago
Closed 2 years ago
#2326 closed defect (fixed)
Advanced NetDb lookup returns O,P and X for O caps searches
Reported by: | Reportage | Owned by: | zzz |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.38 |
Component: | apps/console | Version: | 0.9.37 |
Keywords: | NetDb, advanced lookup | Cc: | |
Parent Tickets: | Sensitive: | no |
Description
When searching for 'O' caps peers, 'O', 'P' and 'X' class peers are returned. Only 'O' class peers should be returned.
On a related note, searches for transports return with the navigation tab highlighted on 'Summary', not 'Router Lookup'.
The search query also includes empty fields for unspecified parameters which could be truncated to only include the active parameter. eg: netdb?netdbLookup=caps&caps=O&cost=&c=&fam=&r=&ip=&ipv6=&mtu=&port=&type=&ssucaps=&tr=ntcp2&v=&sybil2= could be truncated to netdb?netdbLookup=caps&caps=O.
Support for searching using multiple fields would be welcome.
Subtickets
Change History (2)
comment:1 Changed 2 years ago by
Component: | router/netdb → apps/console |
---|---|
Status: | new → accepted |
comment:2 Changed 2 years ago by
Milestone: | undecided → 0.9.38 |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
numbering the OP paragraphs 1-4:
1-3 fixed in 67d1cadf956414627ee3ef381427bce4df560eb5 to be 0.9.37-2
4 is hard, if you mean that multiple fields should be ANDed. They are currently ORed, more or less, kinda.
AND would be nice but it's unlikely to happen, especially since it's hidden behind advanced config.
Declaring victory on 3 out of 4.