| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This functionality is now better fulfilled by using an off-the-shelf network
file system technology to share the BE object directory. This has the advantage
of a more comprehensive and integrated security model as well.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The implementation of this option contained syntax errors and did not work. For
more information, see https://gitlab.com/bugseverywhere/bugseverywhere/issues/7.
|
|
|
|
| |
Signed-off-by: Matěj Cepl <mcepl@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was introduced in:
commit 400c9251eedbd1caa3b28135b4bc5d2bf2124ac5
Author: W. Trevor King <wking@tremily.us>
Date: Thu Jan 24 02:43:53 2013 -0500
util:wsgi: If we're logging to a file, shift libbe.LOG too
where the removed handlers clobbered our initial
TimedRotatingFileHandler.
|
|
|
|
| |
This avoids attempts to log to stderr if we're daemonizing the server.
|
|
|
|
|
|
|
| |
This makes it easier to tweak log verbosity and redirect logs to other
handlers. For example, the WSGI servers are unstable with stderr
closed, and crash with an IOError if they try to print a warning to
stderr.
|
|
|
|
|
|
| |
This brings BEExceptionApp into closer agreement with
libbe.ui.command_line.dispatch(), and avoids having the server go down
when a user submits a silly command.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows you to manage BE servers from inetd scripts, etc.
Shortcomings of the current implementation:
* ServerCommand._daemonize() currently only sets a SIGTERM handler and
double forks. If you want to do this right, see PEP 3143.
Unfortunately, the PEP seems to have stalled, python-daemon appears
unmaintained, and I don't care enough at the moment to do this
right.
* ServerCommand._get_pidfile() races between checking for an existing
PID file and claiming the file itself. It is possible that two
processes would check around the same time, and both see no existing
file. Then they would both open the PID file and write their pid,
without noticing that the other process was contending for the file.
Solving this requires file locking, which is difficult to do
portably. This shouldn't be an issue in normal operation, where
each server will be using its own PID file path.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This was broken in the creation of libbe.util.wsgi from
libbe.command.serve:
commit 0fa17f6bf6a809df14ae1930542059a9e62066b0
Author: W. Trevor King <wking@tremily.us>
Date: Mon Aug 27 13:37:58 2012 -0400
libbe:util:wsgi: extract WSGI utilities into a separate module.
|
|
|
|
|
|
|
|
|
|
|
| |
This was lost in the creation of libbe.util.wsgi from
libbe.command.serve:
commit 0fa17f6bf6a809df14ae1930542059a9e62066b0
Author: W. Trevor King <wking@tremily.us>
Date: Mon Aug 27 13:37:58 2012 -0400
libbe:util:wsgi: extract WSGI utilities into a separate module.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The old implementation caused a number of unittest errors.
This commit adds a WSGICaller instance as WSGITestCase.caller, and
provides a wrapper .getURL method which copies the
status/headers/etc. from the caller back into the WSGITestCase.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This will help avoid confusion between
be serve-storage
and
be serve-commands
|
|
|
|
|
|
|
| |
The bulk of the work is in regard to XML, with new BugDir.xml and
.from_xml methods to support the new <bugdir> entity. I also split
the guts import_xml's ._run method into sub-methods to make the import
logic more obvious.
|
|
|
|
|
|
| |
This fixes .test_get_initial_value for the HTTP backend, because the
tests use TestingHTTP.getURL, which only catch HandlerError, not the
more specific storage exceptions.
|
|
|
|
|
| |
By appending '.py' to *everything*, it was listing '__pycache__' for
Python 3.
|
| |
|
| |
|
|
|
|
|
| |
Also rework liburl2.HTTPError handling to get both the reason and the
error code into the HTTPError message.
|
|
|
|
| |
This way they can be shared with the upcoming Command._run_remote.
|
|
|
|
|
|
|
| |
To test this, you'll need to build an egg. You can use setuptools to
do this, by applying:
<snip-patch>
|
|
|
|
|
|
|
|
|
|
|
| |
WTK: This is the meat of Niall's
commit 4632cb6d22faa7220540f92af67693084f80f033
Author: Niall Douglas ...
Date: Wed Feb 22 17:46:06 2012 +0000
Fixed small bug where running from inside zip support was over
preferring .pyc files
|
|
|
|
|
|
|
|
|
|
|
| |
WTK: This is a portion of Niall's
commit 7f7a7738bcbcfd06a026f2985c1823a4ba5eb55b
Author: Niall Douglas ...
Date: Tue Feb 21 20:35:28 2012 +0000
Several hacks to make BE compatible with bbfreeze and therefore
compilable into a self contained directory
|
|
|
|
|
| |
This avoids errors if the comment text references a repository that
you don't have locally.
|
|
|
|
| |
and stdout to be overridden. This is necessary on Windows as there is no way for external programs to set stdin or stdout charsets :(
|
|
|
|
|
|
|
|
|
|
| |
This was at one point used by `update_copyright.py`. Now that that is
an external package (and doesn't use `Pipe` anymore either), we can
safely remove this code.
As a side benifit, the Pipe doctests will no longer be there to fail
on OS X and other systems sufficiently different from my development
box.
|
|
|
|
| |
Also add `**kwargs` to `invoke` so we can specify the environment.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some temporary changes to encoding.py seem to have been added to
commit 1512c0e2a64e19c8d4e5697257a4df5ddd8bc727
Author: W. Trevor King <wking@drexel.edu>
Date: Tue Nov 8 07:14:43 2011 -0500
by accident.
The initial change came from discussions with Niall Douglas, during
which I realized that "filesystem encoding" ususally means the
encoding for the *path*, not the *contents*. To avoid further
confusion I'd renamed `get_filesystem_encoding` to the less ambiguous
`get_text_file_encoding`. This commit should complete the transition.
|