Opened 11 years ago

Last modified 11 years ago

#156 new

numerous HASH-named category names and descriptions on gmoc-db

Reported by: chaos@bbn.com Owned by: somebody
Priority: major Milestone:
Component: Database Version:
Keywords: Cc:
Dependencies:

Description

The category table at https://gmoc-db.grnoc.iu.edu/measurement/services/snapp.cgi?method=get_categories_by_parent;parent_id=5 contains a large number of malformed entries which look like:

{"category_id":"202852","name":"HASH(0x2aaaac25fa10)","description":"HASH(0x2aaaac25fa10)"},{"category_id":"205570","name":"HASH(0x2aaaac28d200)","description":"HASH(0x2aaaac28d200)"},

Figure out where these entries are coming from, fix the submitter to do the right thing, and get rid of them.

Change History (1)

comment:1 Changed 11 years ago by chaos@bbn.com

Mitch thinks this is being caused by the node_info block submitted by measurement data from gmoc.py, which contains an empty:

  <tags/>

element, and the server-side parser handles that by returning an empty hash instead of an empty array, leading to shenanigans.

  • gmoc.py might as well not submit an empty tags element in node_info. We could remove that.
  • Mitch will try a fix on the server-side to ignore a category when the empty hash is returned by the parser, rather than try to insert it.
Note: See TracTickets for help on using tickets.