| Age | Commit message (Collapse) | Author |
|---|
|
due to zmq, we are hitting the limit and getting app crashes.
- Resolves: #7319
|
|
thanks for making our lives easier during all this time, now we're
starting a relationship with pyinstaller.
maybe our roads cross again in the future.
|
|
we won't be using this for packaging though.
it can be useful to avoid installing it, although installing from wheel is
quite straightforward in osx.
|
|
|
|
|
|
|
|
|
|
The tests where using deferToThread to run without need, I remove it
and now it's easier to debug when one test fails.
- Resolves: #7343
|
|
--use-leap-wheels sets --trusted-host (remove it when we have a proper
cert) and WHEELHOUSE to https://ftp.lizard.leap.se
Until we get ftp.lizard cname, use lizard as the wheels server.
- Related: #7339
|
|
The new pyinstaller method will rule out the launcher, we need the
updater working inside bitmask client.
- Closes: #7291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generate_wheels uses $WHEELHOUSE to generate and store the wheels for
requirements.pip and requirements-testing.pip (if it exists).
pip_install_requirements.sh installs requirements.pip from them if
possible (if not, then it fetches them from pypi) or, if passed the
--testing flag, it installs requirements-testing.pip.
Related: #7327
|
|
|
|
|
|
to workaround the incompatibility problem with Qt libs found in ubuntu
|
|
there are a couple of manual steps needed
|
|
linux only, at the moment, but it's a good start :)
|
|
|
|
- update pip
- install base reqs
|
|
Is useful for new providers to be able to use the stable Bitmask
version with this flag to be able to use custom certificates.
- Resolves: #7250
|
|
|
|
|
|
this is part of a process to make the setup of the development mode less
troublesome. from now on, setting up a virtualenv in pure development
mode will be as easy as telling pip to just install the external
dependencies::
pip install -r pkg/requirements.pip
and traversing all the leap repos for the needed leap dependencies doing::
python setup.py develop
- Related: #7288
|
|
|
|
otherwise the module cannot be imported (in the pseudo-pkg produced by
the sumo tarball)
- Releases: 0.9.0
|
|
- Releases: 0.9.0
|
|
Also, do not raise assertionerror, log warning instead.
|
|
otherwise, events are not correctly registered
- Resolves: #7149
|
|
Fix:
If the logbook controller is not started the stop call will fail.
Trying to start it twice fails.
|
|
lemur/buildbot is intentionally off
|
|
- Resolves: #7284
|
|
|
|
|
|
|
|
Prevent locks caused by the zmq log handler reaching the zmq's HWM (High
water mark / buffer limit) and causing some components to block until
the buffer is empty (running the zmq handler for instance).
We run the zmq handler in the background all the time to prevent this.
- Resolves: #7222
|
|
some general notes about the QA process
|
|
s/self/sync
|
|
Due to #7139 (the logbook log centralizer) logs from 3rd party libs are
included in the centralized logs with lots of debug information and we
don't want that.
We use the existing silencer to exclude logs that are not from leap
modules.
- Resolves: #7185
|
|
The logger is the first thing to be created and on a first run the
config path won't exist. This way we make sure the path always exists.
|
|
if the lsb_release utility is present on system, log part of its output
so we can have more information about the platform bitmask is running
on.
- Resolves: #7162
- Releases: 0.9.0
|
|
- Related: #7139
- Related: #7140
- Related: #7141
- Related: #7142
- Related: #7143
- Related: #7144
- Related: #7180
- Related: #7184
|
|
Rotate bitmask.log file on each start.
|
|
Forward Twisted logs to logging and use logbook to handle logging logs.
Store the bitmask logs on the config folder.
|
|
API to get the children has changed on latest psutil, this takes care
of it.
|
