Michaël Zasso
Michaël Zasso
I think access by IP address and SSH is all we need to manage it and connect it to Jenkins.
Then it could be part of a nightly job like https://ci.nodejs.org/view/All/job/sxa-rvnodetest/
1. I would advocate for `a`, with `b` and `c` as possible intermediary steps. 2. You mean runtime-deprecated? It depends on the impact. If there is no popular module that...
I will help on the build and V8 side.
It happened. Thank you @marco-ippolito and @RafaelGSS !
CITGM results: https://ci.nodejs.org/job/citgm-smoker/nodes=ubuntu1804-64/2751/#showFailuresLink Unfortunately, all modules that depend on node-gyp fail at install time because of another deprecation. - Affects [`ava`](https://ci.nodejs.org/job/citgm-smoker/nodes=ubuntu1804-64/2751/testReport/junit/(root)/citgm/ava_v3_15_0/), [`csv-parser`](https://ci.nodejs.org/job/citgm-smoker/nodes=ubuntu1804-64/2751/testReport/junit/(root)/citgm/csv_parser_v3_0_0/), [`ember-cli`](https://ci.nodejs.org/job/citgm-smoker/nodes=ubuntu1804-64/2751/testReport/junit/(root)/citgm/ember_cli_v3_27_0/) through an old version of `graceful-fs` -...
Isn't the session implementable/exposable as a middleware? That would make it much easier to customize where it is enabled.
Was there a technical reason for implementing it this way?
I understand. Then I think it's important that this proposal defines a to exclude the session from either: - A route prefix - A group of routes
> Yes, we can wrap it inside a try/catch statement. But then that prevents the global exception handler from being called. You could also wrap it in a `try/finally` statement.