Closed michaelkirk closed 7 months ago
re: build failure https://github.com/pelias/api/actions/runs/5627436077
Because of fa9838fed8b7f43603af65d5282561c55a9a44fb, it looks like I need to add my own repo/org variables in order for tests to pass. I've done that here:
...and now tests are passing
(except for the docker --push, for which I haven't configured secrets. It seems like it'd be more convenient to use the pre-existing secrets.GH_TOKEN
rather than requiring manual config, but that's a separate issue).
It's not a big deal, but I expect others will get confused by this as well.
Hi @michaelkirk, I've merged https://github.com/pelias/query/pull/134, can you please update this PR so the package.json
dependency points to the latest pelias/query (which should be 11.2):
npm install pelias-query@latest --save
.. and then open it up for review, tx!
Done (and rebased).
I missed an occurrence somehow. Let me fix this up, retest, and I'll re-open shortly.
You didn't miss the macrocounty
one, I added that a few weeks ago in https://github.com/pelias/api/pull/1552 🙏
Here's the reason for this change :rocket:
In pursuit of eventually supporting es8, I've dropped some es6 only behavior in https://github.com/pelias/query/pull/134.
It's a draft because it depends on https://github.com/pelias/query/pull/134 being released first.
Here's what actually got changed :clap:
cutoff_frequency
.Here's how others can test the changes :eyes:
Other than
npm test
, I've run the north-america tests.Note: The north-america tests aren't all passing, but the ones that are failing are exactly the same as when I run from current master. I'm assuming (🤞) that the failures reflect changes in the input data since the tests were updated, as hypothesized over here.
north-america integration test output before north-america test output after