You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
release/index.json for v6.8.1 has invalid modules value #519
I assume the modules value originates from fetchModVersion() in dist-indexer.js. I've manually tested the regexes in that method against node_version.h and node.h, where the former seems to match perfectly fine, meaning it should not have resolved the modules value to null.
Any thoughts on how this might have happened? Could we execute dist-indexer.js manually to see if it was a temporary glitch, and the correct modules value gets resolved now?
The dist indexer at our old www host is pretty much identical to currently deployed at new place (just making sure that no un-committed code was running)
The scripts look like they are invoked the same way
I've run it again and it's updated. This can happen if the tag is not pushed to the public repo before being promoted. @evanlucas I think you did 6.8.1, do you recall if this happened?
Activity
phillipj commentedon Oct 15, 2016
Just noticed v6.8.1 also has
zlib: nulltargos commentedon Oct 15, 2016
It's also missing the
npmpropertytargos commentedon Oct 15, 2016
And
uvis an empty stringphillipj commentedon Oct 16, 2016
/cc @nodejs/release
MylesBorins commentedon Oct 16, 2016
/cc @nodejs/ctc
jbergstroem commentedon Oct 17, 2016
The likely cause is us switching www hosts (was running out of disk space). Not sure exactly what.
rvagg commentedon Oct 17, 2016
I've run it again and it's updated. This can happen if the tag is not pushed to the public repo before being promoted. @evanlucas I think you did 6.8.1, do you recall if this happened?
evanlucas commentedon Oct 17, 2016
Looking back, I may not have pushed the tag when I promoted
rvagg commentedon Oct 18, 2016
pretty sure nodejs/node#9142 will solve this