| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Without entering an asynchronous scope, logs are the same before. When
entering an asynchronous scope (either thread-based of
scheduler/task-based), all log lines within an asynchronous scope
contain its ID.
Currently this is only used in GNU Taler, for debugging requests across
multiple services. This allows us to get all log lines pertaining to a
particular request for a user or another service.
|
| |
|
|
|
|
|
| |
(Thread-safe logging isn't really relevant for GNUnet itself, but it is
necessary for the GNU Taler exchange)
|
| |
|
| |
|
|
|
|
| |
transport API to pass them to (TNG) service
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
service.c:481:15: warning: suggest braces around initialization of subobject
[-Wmissing-braces]
while (0 != GNUNET_is_zero (&list[i].network))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This copies the central part of gnunet-uri. Should better be in some
shared code.
Also eliminate helper lib "gnunet-qr-utils.h", which is no longer
used.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This helps keeping environments concise and functional package
managers like guix this will ensure `gnunet-uri` from the same
environment is used.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
These functions are copied from dns/gnunet-helper-dns.c,
move them into a common library.
Or think about implementing a even more elaborate version.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Still to-do:
* running gnunet-uri
* Proper error handling
* integration into build system (automake)
Reimplementing in C was chosen since
- official zbar python-bindings support python 2 only,
- none of the other bindings available at PyPI supports the high-level
"processor" interface which gnunet-qr uses
- implementing bindings for zbar using ctypes required addin a lot of
low-level error handling code, thus implementing in C seamed to be
easier,
- the programm is short, thus re-implementing is not such complicated, and
- this allows to reduce the number of dependencies (here: another
Python version), which should ease porting to other plattforms (zbar
is a dependency anyway).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This copies the central part of gnunet-uri. Should better be in some
shared code.
Also eliminate helper lib "gnunet-qr-utils.h", which is no longer
used.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This helps keeping environments concise and functional package
managers like guix this will ensure `gnunet-uri` from the same
environment is used.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
These functions are copied from dns/gnunet-helper-dns.c,
move them into a common library.
Or think about implementing a even more elaborate version.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Still to-do:
* running gnunet-uri
* Proper error handling
* integration into build system (automake)
Reimplementing in C was chosen since
- official zbar python-bindings support python 2 only,
- none of the other bindings available at PyPI supports the high-level
"processor" interface which gnunet-qr uses
- implementing bindings for zbar using ctypes required addin a lot of
low-level error handling code, thus implementing in C seamed to be
easier,
- the programm is short, thus re-implementing is not such complicated, and
- this allows to reduce the number of dependencies (here: another
Python version), which should ease porting to other plattforms (zbar
is a dependency anyway).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|