Open JohanLorenzo opened 8 years ago
@arcturus It seems the SW is correctly registered but can't fetch the content of https://knilxof.org:4443/ping. Would it be possible to print out what's the response given?
@JohanLorenzo you can enable debug on SW following the next steps to build a version of the library with debug:
npm install
gulp bundle-debug
And rebuild the app
Looking at this.
Hey @JohanLorenzo what I see is that https://knilxof.org:4443/
has invalid certificate that's why we can't get any data from it. Once you add exception - it works fine.
Or you see something different?
Note I'm using your PR https://github.com/fxbox/app/pull/161 locally
Also I'm wondering why do we need real registration server?
I feel tests will be too flaky if we rely on external thing....
That might be it. One one hand, https://knilxof.org:4443/
may not be an issue because it intermittently passed. On the other hand, that's one clear change between the old tests set up and the new one.
If that's the problem, re-issuing a Let's Encrypt certificate should make the PR pass for the next few days. I remember @gmarty and @michielbdejong were talking about it, last week. I don't recall if it was addressed, though.
On your second point, I agree the real registration server shouldn't be used. That's a good follow up, IMO.
So, I'd propose we fix the certificate on knilxof and see if it makes things better. If not, we change mock out the registration server.
If that's the problem, re-issuing a Let's Encrypt certificate should make the PR pass for the next few days.
I'm not sure if that's enough :) I suspect that your PR is relying on real foxbox instance now and its signup and login pages are quite different from what we had in simulator. I didn't go through your PR so maybe you already have necessary changes in tests, if so that's great!
On your second point, I agree the real registration server shouldn't be used. That's a good follow up, IMO. So, I'd propose we fix the certificate on knilxof and see if it makes things better. If not, we change mock out the registration server.
Yep, it can surely be a follow-up, agree.
So @michielbdejong could you please help with updating certificate at https://knilxof.org:4443/
?
So nothing to do for me here, unassigning.
I'm not sure if that's enough :) I suspect that your PR is relying on real foxbox instance.
The PR hasn't (shouldn't have :smiley: ) changed the role of the simulator. We still use it for the integration tests.
OK then I think I'm missing something in the integration tests setup.. Let's talk on irc once you come back from London :)
re-issuing a Let's Encrypt certificate should make the PR pass for the next few days. I remember @gmarty and @michielbdejong were talking about it, last week. I don't recall if it was addressed, though.
It was, current certificate is valid 3 June - 1 Sep 2016, you can check this by viewing the padlock details on https://knilxof.org:4443/.
Steps to reproduce
Manually:
cargo build
gulp
./run.sh
Automatically:
npm test | grep -v 'firefox_profile'
Results
The "connect to your foxbox" button remains greyed out. This makes the Seleniums tests in #161 flaky (around 1/3 times).
The webconsole shows: