Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign up"updated nightly" #18
Comments
This comment has been minimized.
This comment has been minimized.
|
That's definitely not the idea, it should be updated nightly. I've just taken a look and it's not rebuilding the nightly database because of a change in the data files structure, something about ammo_type not being available. This will be fixed in a few minutes. |
Sheco
added a commit
that referenced
this issue
Apr 14, 2016
This comment has been minimized.
This comment has been minimized.
|
Alright, with this patch, I forced a database update and the item browser should not need to be changed to display "rarely ever updated" as the nightly process should be able to automatically update it without a problem. Thank you for your report. |
This comment has been minimized.
This comment has been minimized.
|
Heh, sorry, man, it's just that the JSON format does seem to shift once in a while without anyone noticing. No emails from your auto-updater when it fails? Later edit: Oh, right, the item browser is being impacted by the current drive to remove default values from the JSONs; sadly, I don't think those are described in any actual JSON -- so you'll have to treat them as unknowns and/or possibly hard-code the defaults somewhere. In any case, I'll make sure to give you another poke if it seems like the IB is falling behind again. Thanks for the fix! |
narc0tiq
closed this
Apr 14, 2016
This comment has been minimized.
This comment has been minimized.
|
Yes, it's not the first time some small details break the indexer, I haven't been followed the game in a long time so I am completely out of the loop so I miss these kinds of things. Would you mind checking why the mosin44's object is incomplete? is that the way that it's expected to be? I definitely appreciate being updated when these kinds of things fall back, even when I am not entirely involved anymore, I am more than happy to update the item browser if people need it. Thanks! |
This comment has been minimized.
This comment has been minimized.
|
Incomplete in what way? It should be valid JSON; it may be missing some expected fields, as mentioned in my edit -- there's currently a big operation going on to remove default values from the JSON objects, under the theory that it's redundant to specify values that are just the same as they would be if left out (example: CleverRaven/Cataclysm-DDA#15776). Looks like @Cyrano7's been doing the bulk of that work . |
This comment has been minimized.
This comment has been minimized.
|
Yes, the JSON is perfectly valid, but those missing expected fields make the indexer in Item.php exit unexpectedly. For example, I assume AMMO objects always have an ammo_type attribute. (Line 178) If the data files start omitting these values, I would have to either ignore the objects or define a sensible default. What do you think? |
This comment has been minimized.
This comment has been minimized.
|
Defining the defaults is the right idea, though you may get oddities if the There's going to be a jq script to check for redundant defaults, but we On Thu, Apr 14, 2016, 19:49 Sergio Duran notifications@github.com wrote:
|
This comment has been minimized.
This comment has been minimized.
mugling
commented
Apr 14, 2016
I suspect it's the
Most of the defaults can be found in the |
This comment has been minimized.
This comment has been minimized.
mightyagrippa
commented
Sep 14, 2016
|
Sorry to necro this, but it seems relevant. Development browser is showing current version |
narc0tiq commentedApr 14, 2016
From the front page of http://cdda-trunk.estilofusion.com/, the following paragraph (emphasis mine):
Given that the item browser's last update was
0.C-11261-g75886c0and CDDA is currently at0.C-12973-g5234160, perhaps a change in verbiage is in order? "Updated infrequently", or something to that effect?