Wesley [13:19]
@eng-team: so @geoffturk and I have been testing frost-api.qa today, we discovered an issue with poetUrl not being honored by the environment variable set as POET_URL, but only for the WorksController.create function. When trying to create a work, Frost API was failing to connect to node, as it was using the default value set, which is on the localhost / loopback interface:
Wesley [13:19] @eng-team: so @geoffturk and I have been testing frost-api.qa today, we discovered an issue with
poetUrl
not being honored by the environment variable set asPOET_URL
, but only for theWorksController.create
function. When trying to create a work, Frost API was failing to connect to node, as it was using the default value set, which is on the localhost / loopback interface:You can see that I have loaded the correct configuration as printed out when frost-api starts up:
yet, WorksController was still trying to communicate with node on http://127.0.0.1:18080 to get around this, I created a new branch, and changed the configuration to this: https://github.com/poetapp/frost-api/blob/bug/node-loopback/src/configuration.ts#L77 frost-api WorksController.create was then communicating to the correct node now and we were not getting any more errors, and were able to create works https://frost-api-testing.qa.poetnetwork.net contains the fix I made https://frost-api.qa.poetnetwork.net is running with v1.3.0 which will cause errors so theres def something funky happening with the configuration