- 21 Dec, 2021 2 commits
-
-
Jérome Perrin authored
Reading this spec, we probably want to change ``` entry_run = 'from %s import %s; %s()' % (mod, func, func) ``` to ``` entry_run = 'import sys; from %s import %s; sys.exit(%s())' % (mod, func, func) ``` to follow https://packaging.python.org/en/latest/specifications/entry-points/#use-for-scripts , this is also what `zc.recipe.egg` does. /reviewed-by @kirr /reviewed-on !1108
-
Kirill Smelkov authored
In e328aa49 (component/nxdtest: Prepare for nexedi/nxdtest!13) I reworked how nxdtest script is generated and splitted it into nxdtest itself and .nxdtest.pyexe python interpreter, so that sys.executable could be used to correctly spawn other python scripts: 3) rework how nxdtest script is generated and split it into .nxdtest.pyexe and nxdtest itself. .nxdtest.pyexe is python interpreter via which nxdtest is run. This interpreter has all eggs required by nxdtest in sys.path, so that nxdtest could spawn its trun.py via sys.executable. If we don't care to have properly setup sys.executable, trun.py will fail when importing any module that nxdtest.py could already successfully import. Initially I tried to workaround this issue via adjusting $PYTHONPATH <- sys.path in main nxdtest script, but @jerome points out that, $PYTHONPATH, if set, also affects processes that trun.py spawns, which is not good: nexedi/slapos!1095 (comment 146799) -> so fix this via running nxdtest via environment where sys.executable is properly setup python interpreter with path for all eggs that nxdtest has access to. Because we already have half-way workarounds for similar problem in several places, and because running a script with correctly setup sys.executable is generally better, I would say it should be a good idea to rework zc.recipe.egg:scripts to generate all scripts to work this way, but I do not want to fight about it. So let's leave this scheme nxdtest-specific for now. This patch addresses the last paragraph and provides a general pyprog buildout macro that could be used to generate python script for any entry point to run with correctly set sys.executable. /reviewed-by @jerome /reviewed-on nexedi/slapos!1108
-
- 17 Dec, 2021 6 commits
-
-
Thomas Gambier authored
-
Joanne Hugé authored
-
Joanne Hugé authored
IMS and MME are in the same instance, but there is only one TUN per instance. IMS is not crucial right now so we temporarily remove it until we implement a clean solution.
-
Joanne Hugé authored
-
Xavier Thompson authored
We were trying to patchelf a file that apparently exists when Theia is compiled on Debian 8, 10 and 11, but not on Debian 9.
-
Xavier Thompson authored
See merge request nexedi/slapos!1105
-
- 16 Dec, 2021 7 commits
-
-
Xavier Thompson authored
Include the hash of all parameters related to the embedded instance as a comment in the standalone script, so that if the hash changes, the script and its own hash change as well, and standalone service will be restarted.
-
Xavier Thompson authored
Generate standalone script in instance-theia.cfg.jinja.in instead of in software.cfg, avoiding the need to forward all the parameters.
-
Xavier Thompson authored
Include the hash of the relevant parameters in the abstract socket path, so that when changing these instance parameters the promise waits until the standalone service has taken the new parameters into account.
-
Xavier Thompson authored
Change "Embedded Instance" to "embedded_instance", and rename existing "Embdded Instance" into "embedded_instance" for compatibility.
-
Joanne Hugé authored
-
Joanne Hugé authored
-
Xavier Thompson authored
-
- 15 Dec, 2021 6 commits
-
-
Thomas Gambier authored
-
Joanne Hugé authored
-
Joanne Hugé authored
-
Joanne Hugé authored
-
Joanne Hugé authored
-
Joanne Hugé authored
-
- 14 Dec, 2021 3 commits
-
-
Léo-Paul Géneau authored
-
Jérome Perrin authored
Installing will setup git hooks, so we can do one step further and also configure the mergetool
-
Jérome Perrin authored
otherwise curl uses system ca-certificates if the system package is installed and otherwise is not able to verify server certificates, usually being observed in slapos as git refusing to clone with error: SSL certificate problem: unable to get local issuer certificate
-
- 13 Dec, 2021 10 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Romain Courteaud authored
-
Xavier Thompson authored
See merge request nexedi/slapos!1103
-
Joanne Hugé authored
-
Xavier Thompson authored
On Debian 9, the given rpath seem to be ignored when compiling the `keytar` dependency of theia, for unknown reasons.
-
Xavier Thompson authored
- Move [theia] section and dependencies into component/theia - Make [theia] section shared
-
Xavier Thompson authored
-
Jérome Perrin authored
This was missing in this software and in 03c5b311 (Stop using hexagonit.recipe.download, 2021-12-03) the hash got out of sync
-
Jérome Perrin authored
-
- 12 Dec, 2021 6 commits
-
-
Jérome Perrin authored
also mention automatic installation method
-
Jérome Perrin authored
-
Jérome Perrin authored
Since https://github.com/eclipse-theia/theia/pull/10343 theia depend on nodejs >= 12 and they test on 12 and 14. Use 14 to have an officially tested version. This removes the strong requirement to have python2.7 in theia, so we just use the software python, which might be python3
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-