-
Notifications
You must be signed in to change notification settings - Fork 169
toxcore: update to 0.2.7. #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
#ifndef _POSIX_C_SOURCE | ||
// For nanosleep(). | ||
-#define _POSIX_C_SOURCE 199309L | ||
+#define _POSIX_C_SOURCE 200112L |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this?
If we want to overwrite or define _POSIX_C_SOURCE
we shall do it from main package's level with -D_POSIX_C_SOURCE=200112L
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Please add proposed changelog entry. |
Where do I add the changelog entry? |
Here so a committer can land this change with a ready changelog. |
|
Any action required? |
It's pending until someone else than me will grab it, I'm swamped to do it myself (and I don't know how to test it myself). |
Add missing DEPENDS Upstream changes: 0.84 Mon 16 Jul 2018 17:49:10 BST - Put back credential cache code lost in Signature 4 patch (Branislav Zahradník) 0.83 Tue 10 Jul 2018 22:30:23 BST - All patches by Branislav Zahradník - Use Signature 4 by default only for amazonaws host (issue #29) - Relaxing constraint on owner id, accepting any string (issue #18) - Enable secure by default (issue #23) - Sanity object uris to avoid invalid signature (issue #28) 0.82 Sat 7 Jul 2018 14:28:06 BST - Use HEAD request to determine bucket region (patch by Branislav Zahradník) 0.81 Thu 28 Jun 2018 20:27:44 GMT (TRIAL RELEASE) - Restore CHANGES files format - Change path to new github repo - Add optional delimiter parameter to Net::Amazon::S3::Client::Bucket->list (patch by Christian Lackas) - Add expected and received ETag value if upload is detected as being incorrect. - Add support for all location constraints when creating buckets - making DateTime coercion optional for last_modified (something that might happen million of times without ever been used, in a rather expensive operation) (patch by Christian Lackas) - avoiding MD5 calculation of large files (chunked uploads) that are then never used (patch by Christian Lackas) - add ability to set use_virtual_host to use virtual host method of making requests which eliminate having to set the region endpoint of a bucket. (patch by Christian Lackas) - Add V4 support (patch by Branislav Zahradník)
Hello iphydf,
First of all thank you very much for updating it!
iphydf writes:
Any action required?
Probably it's worth to first import it in pkgsrc-wip to ease the
review process (ATM, at least on NetBSD-current the build seems to
fail, full log at the end of this reply).
If you do not have access to pkgsrc-wip please give a look to:
<https://www.pkgsrc.org/wip/users/>
On a (not-so)-current NetBSD the build fails with:
[...]
[ 53%] Built target auto_typing_test
In file included from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:7:0:
/usr/include/g++/cstdio:176:11: error: '::vfscanf' has not been declared
using ::vfscanf;
^~~~~~~
Scanning dependencies of target auto_lan_discovery_test
Scanning dependencies of target auto_encryptsave_test
[ 53%] Building C object CMakeFiles/auto_lan_discovery_test.dir/auto_tests/lan_discovery_test.c.o
/usr/include/g++/cstdio:177:11: error: '::vscanf' has not been declared
using ::vscanf;
^~~~~~
/usr/include/g++/cstdio:179:11: error: '::vsscanf' has not been declared
using ::vsscanf;
^~~~~~~
/usr/include/g++/cstdio:186:22: error: '__gnu_cxx::vfscanf' has not been declared
using ::__gnu_cxx::vfscanf;
^~~~~~~
/usr/include/g++/cstdio:187:22: error: '__gnu_cxx::vscanf' has not been declared
using ::__gnu_cxx::vscanf;
^~~~~~
/usr/include/g++/cstdio:189:22: error: '__gnu_cxx::vsscanf' has not been declared
using ::__gnu_cxx::vsscanf;
^~~~~~~
In file included from /usr/include/g++/bits/localefwd.h:42:0,
from /usr/include/g++/string:43,
from /usr/include/g++/stdexcept:39,
from /usr/include/g++/array:39,
from /usr/include/g++/tuple:39,
from /usr/include/g++/functional:55,
from /usr/include/g++/memory:79,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:9:
/usr/include/g++/cctype:87:11: error: '::isblank' has not been declared
using ::isblank;
^~~~~~~
[ 54%] Building C object CMakeFiles/auto_encryptsave_test.dir/auto_tests/encryptsave_test.c.o
[ 55%] Linking C executable tox-bootstrapd
[ 55%] Built target tox-bootstrapd
[ 56%] Linking C executable auto_lan_discovery_test
Scanning dependencies of target auto_toxav_basic_test
[ 57%] Building C object CMakeFiles/auto_toxav_basic_test.dir/auto_tests/toxav_basic_test.c.o
In file included from /usr/include/g++/random:38:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/cmath:1101:11: error: '::double_t' has not been declared
using ::double_t;
^~~~~~~~
[ 57%] Built target auto_lan_discovery_test
/usr/include/g++/cmath:1102:11: error: '::float_t' has not been declared
using ::float_t;
^~~~~~~
/usr/include/g++/cmath:1105:11: error: '::acosh' has not been declared
using ::acosh;
^~~~~
/usr/include/g++/cmath:1109:11: error: '::asinh' has not been declared
using ::asinh;
^~~~~
/usr/include/g++/cmath:1113:11: error: '::atanh' has not been declared
using ::atanh;
^~~~~
/usr/include/g++/cmath:1117:11: error: '::cbrt' has not been declared
using ::cbrt;
^~~~
/usr/include/g++/cmath:1121:11: error: '::copysign' has not been declared
using ::copysign;
^~~~~~~~
/usr/include/g++/cmath:1125:11: error: '::erf' has not been declared
using ::erf;
^~~
/usr/include/g++/cmath:1129:11: error: '::erfc' has not been declared
using ::erfc;
^~~~
/usr/include/g++/cmath:1137:11: error: '::expm1' has not been declared
using ::expm1;
^~~~~
/usr/include/g++/cmath:1157:11: error: '::hypot' has not been declared
using ::hypot;
^~~~~
/usr/include/g++/cmath:1161:11: error: '::ilogb' has not been declared
using ::ilogb;
^~~~~
/usr/include/g++/cmath:1165:11: error: '::lgamma' has not been declared
using ::lgamma;
^~~~~~
/usr/include/g++/cmath:1177:11: error: '::log1p' has not been declared
using ::log1p;
^~~~~
/usr/include/g++/cmath:1185:11: error: '::logb' has not been declared
using ::logb;
^~~~
/usr/include/g++/cmath:1205:11: error: '::nextafter' has not been declared
using ::nextafter;
^~~~~~~~~
/usr/include/g++/cmath:1213:11: error: '::remainder' has not been declared
using ::remainder;
^~~~~~~~~
/usr/include/g++/cmath:1221:11: error: '::rint' has not been declared
using ::rint;
^~~~
/usr/include/g++/cmath:1229:11: error: '::scalbln' has not been declared
using ::scalbln;
^~~~~~~
/usr/include/g++/cmath:1233:11: error: '::scalbn' has not been declared
using ::scalbn;
^~~~~~
Scanning dependencies of target auto_crypto_test
[ 58%] Building C object CMakeFiles/auto_crypto_test.dir/auto_tests/crypto_test.c.o
[ 58%] Linking C executable auto_encryptsave_test
In file included from /usr/include/g++/random:51:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/bits/random.tcc: In member function 'void std::poisson_distribution<_IntType>::param_type::_M_initialize()':
/usr/include/g++/bits/random.tcc:1250:32: error: call of overloaded 'lgamma(double)' is ambiguous
_M_lfm = std::lgamma(__m + 1);
^
In file included from /usr/include/g++/random:38:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/cmath:1531:3: note: candidate: constexpr float std::lgamma(float)
lgamma(float __x)
^~~~~~
/usr/include/g++/cmath:1535:3: note: candidate: constexpr long double std::lgamma(long double)
lgamma(long double __x)
^~~~~~
In file included from /usr/include/g++/random:51:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/bits/random.tcc: In member function 'std::poisson_distribution<_IntType>::result_type std::poisson_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&, const std::poisson_distribution<_IntType>::param_type&)':
/usr/include/g++/bits/random.tcc:1357:52: error: call of overloaded 'lgamma(double)' is ambiguous
__param._M_lfm - std::lgamma(__x + __m + 1));
^
In file included from /usr/include/g++/random:38:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/cmath:1531:3: note: candidate: constexpr float std::lgamma(float)
lgamma(float __x)
^~~~~~
/usr/include/g++/cmath:1535:3: note: candidate: constexpr long double std::lgamma(long double)
lgamma(long double __x)
^~~~~~
In file included from /usr/include/g++/random:51:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/bits/random.tcc: In member function 'void std::binomial_distribution<_IntType>::param_type::_M_initialize()':
/usr/include/g++/bits/random.tcc:1484:33: error: call of overloaded 'lgamma(double)' is ambiguous
_M_lf = (std::lgamma(__np + 1)
^
In file included from /usr/include/g++/random:38:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/cmath:1531:3: note: candidate: constexpr float std::lgamma(float)
lgamma(float __x)
^~~~~~
/usr/include/g++/cmath:1535:3: note: candidate: constexpr long double std::lgamma(long double)
lgamma(long double __x)
^~~~~~
In file included from /usr/include/g++/random:51:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/bits/random.tcc: In member function 'std::binomial_distribution<_IntType>::result_type std::binomial_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&, const std::binomial_distribution<_IntType>::param_type&)':
/usr/include/g++/bits/random.tcc:1624:35: error: call of overloaded 'lgamma(double)' is ambiguous
std::lgamma(__np + __x + 1)
^
In file included from /usr/include/g++/random:38:0,
from /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.6/testing/random_testing.cc:10:
/usr/include/g++/cmath:1531:3: note: candidate: constexpr float std::lgamma(float)
lgamma(float __x)
^~~~~~
/usr/include/g++/cmath:1535:3: note: candidate: constexpr long double std::lgamma(long double)
lgamma(long double __x)
^~~~~~
[...]
Thank you!
|
vscanf(3) is protected with |
@iamleot is this a regression over 0.2.5? |
Added a patch that's upstreamed in TokTok/c-toxcore#1094.
Hello iphydf,
iphydf writes:
@iamleot is this a regression over 0.2.5?
Yes, toxcore-0.2.5 built fine.
|
That's very strange. I'm doing |
Does 0.2.7 build fine again? |
Leonardo Taccari writes:
[...]
Yes, toxcore-0.2.5 built fine.
[...]
Whoops, sorry, I meant toxcore-0.2.4 (latest version in pkgsrc-current)!
|
Hello iphydf,
iphydf writes:
Does 0.2.7 build fine again?
Yes, now it builds and install fine, thanks!
However - but please note that this is not a regression! - the test
seems stuck, i.e. doing a `make test':
% make test
=> Bootstrap dependency digest>=20010302: found digest-20160304
===> Testing for toxcore-0.2.7
Running tests...
Test project /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.7
Start 1: TCP
...and nothing seems to progress (doing a ^T I can see
`load: 0.00 cmd: make 27707 [wait] 0.00u 0.01s 0% 2128k').
Can you reproduce that as well and/or any idea on what's going on?
(Of course for any possible further testing and/or more debugging
output do not hesitate to contact me!)
|
It works for me on SmartOS. Can you attach gdb and see where it's stuck? 0% cpu could mean it's stuck in a system call (e.g. networking). |
iphydf writes:
```
Test project /home/pbulk/build/chat/toxcore/work/c-toxcore-0.2.7
Start 1: TCP
1/41 Test #1: TCP .............................. Passed 15.93 sec
```
It works for me on SmartOS. Can you attach gdb and see where it's stuck? 0% cpu could mean it's stuck in a system call (e.g. networking).
Sure (I have recompiled it via `CFLAGS=-g3'):
% gdb -p `pgrep auto_TCP_test`
[...]
(gdb) bt
#0 0x000073c4856d630a in recvfrom () from /usr/lib/libc.so.12
#1 0x0000000000405dce in net_recv (sock=..., sock@entry=..., buf=buf@entry=0x7f7fffc6f720, len=len@entry=96)
at /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.7/toxcore/network.c:1440
#2 0x000000000040358a in test_basic () at /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.7/auto_tests/TCP_test.c:114
#3 0x000000000042a66b in TCP_suite () at /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.7/auto_tests/TCP_test.c:844
#4 main () at /tmp/pkgsrc/chat/toxcore/work/c-toxcore-0.2.7/auto_tests/TCP_test.c:857
Thanks!
|
I'll see if I can get a netbsd VM up and running to test this. Filed TokTok/c-toxcore#1146. Do any of the other tests work? E.g. if you do ./auto_conference_test? |
Hello iphydf,
iphydf writes:
I'll see if I can get a netbsd VM up and running to test this.
Filed TokTok/c-toxcore#1146. Do any of the other tests work? E.g. if you do ./auto_conference_test?
Here the complete output:
| % ./auto_conference_test
| creating 16 toxes
| [#1] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#1] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#1] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33445
| [#2] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#2] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#2] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33446
| [#3] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#3] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#3] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33447
| [#4] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#4] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#4] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33448
| [#5] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#5] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#5] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33449
| [#6] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#6] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#6] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33450
| [#7] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#7] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#7] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33451
| [#8] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#8] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#8] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33452
| [#9] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#9] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#9] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33453
| [#10] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#10] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#10] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33454
| [#11] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#11] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#11] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33455
| [#12] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#12] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#12] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33456
| [#13] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#13] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#13] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33457
| [#14] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#14] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#14] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33458
| [#15] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#15] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#15] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33459
| [#16] DEBUG network.c:836 new_networking_ex: Dual-stack socket: enabled
| [#16] DEBUG network.c:849 new_networking_ex: Failed to activate local multicast membership. (49, Can't assign requested address)
| [#16] DEBUG network.c:881 new_networking_ex: Bound successfully to [::]:33460
| creating a chain of friends
| waiting for everyone to come online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| tox #11: is now connected
| currently 0 toxes are online
| tox #1: is now connected
| tox #2: is now connected
| tox #5: is now connected
| tox #10: is now connected
| tox #12: is now connected
| tox #13: is now connected
| tox #16: is now connected
| currently 0 toxes are online
| tox #3: is now connected
| tox #7: is now connected
| tox #14: is now connected
| tox #15: is now connected
| currently 0 toxes are online
| tox #4: is now connected
| tox #8: is now connected
| tox #9: is now connected
| currently 0 toxes are online
| tox #6: is now connected
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| currently 0 toxes are online
| tox #13: is now connected to friend 0
| currently 1 toxes are online
| tox #5: is now connected to friend 0
| tox #11: is now connected to friend 0
| tox #12: is now connected to friend 1
| tox #14: is now connected to friend 1
| tox #15: is now connected to friend 0
| currently 4 toxes are online
| tox #4: is now connected to friend 1
| [#4] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| tox #10: is now connected to friend 1
| tox #13: is now connected to friend 1
| tox #14: is now connected to friend 0
| currently 5 toxes are online
| tox #11: is now connected to friend 1
| tox #12: is now connected to friend 0
| currently 6 toxes are online
| tox #1: is now connected to friend 0
| tox #2: is now connected to friend 0
| tox #7: is now connected to friend 0
| tox #8: is now connected to friend 1
| tox #9: is now connected to friend 1
| tox #9: is now connected to friend 0
| tox #10: is now connected to friend 0
| currently 11 toxes are online
| tox #6: is now connected to friend 1
| tox #8: is now connected to friend 0
| currently 12 toxes are online
| tox #7: is now connected to friend 1
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| currently 12 toxes are online
| tox #5: is now connected to friend 1
| tox #6: is now connected to friend 0
| currently 13 toxes are online
| tox #3: is now connected to friend 0
| currently 14 toxes are online
| tox #2: is now connected to friend 1
| tox #16: is now connected to friend 0
| currently 15 toxes are online
| tox #15: is now connected to friend 1
| currently 15 toxes are online
| tox #3: is now connected to friend 1
| tox #4: is now connected to friend 0
| currently 16 toxes are online
| friends connected, took 59 seconds
| tox #1: inviting its first friend
| waiting for invitations to be made
| tox #2: invited next friend
| tox #3: invited next friend
| tox #4: invited next friend
| tox #5: invited next friend
| tox #6: invited next friend
| tox #7: invited next friend
| tox #8: invited next friend
| tox #9: invited next friend
| tox #10: invited next friend
| tox #11: invited next friend
| tox #12: invited next friend
| tox #13: invited next friend
| tox #14: invited next friend
| tox #15: invited next friend
| waiting for all toxes to be in the group
| current peer counts: [9, 9, 10, 10, 11, 11, 12, 12, 13, 13, 14, 14, 15, 15, 16, 16]
| current peer counts: [9, 10, 10, 11, 11, 12, 12, 13, 13, 14, 14, 15, 15, 16, 16, 16]
| current peer counts: [10, 10, 11, 11, 12, 12, 13, 13, 14, 14, 15, 15, 16, 16, 16, 16]
| current peer counts: [[#1] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| 10[#2] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 11[#3] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 11[#4] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 12, 12, 13[#7] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 13, 14, 14, 15, 15, 16, 16, 16, 16, 16]
| current peer counts: [11, 11, 12, 12, 13, 13, 14, 14, 15, 15, 16, 16, 16, 16, 16, 16]
| current peer counts: [11, 12, 12, 13[#5] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 13, 14[#7] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 14, 15, 15[#10] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 16, 16, 16, 16, 16, 16, 16]
| current peer counts: [[#1] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| 12[#2] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 12[#3] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 13[#4] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 13[#5] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 14[#6] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 14[#7] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 15[#8] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 15[#9] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 16[#10] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 16, 16, 16, 16, 16, 16, 16]
| current peer counts: [[#1] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| 12, 13[#3] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| , 15, 14, 15, 15, 15, 16, 16, 16, 16, 16, 16, 16, 16, 16]
| current peer counts: [13, 16, 15, 15, 15, 15, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16]
| current peer counts: [16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16]
| group connected, took 2 seconds
| [#1] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| [#6] DEBUG net_crypto.c:1195 send_lossless_packet: send_data_packet failed
| tearing down toxes
| test_many_group succeeded, took 73 seconds
Thanks!
|
Thanks, that means toxcore public API works fine, it's just the TCP test. |
2.0.4 (2018-04-12) Merged Pull Requests * fix labelling #37 (thommay) 2.0.1 (2018-02-28) Full Changelog Merged pull requests: * enable metadata to be got and set #32 (thommay) * Logging methods (debug, info, warn, error, fatal) all return nil #27 (olleolleolle) 2.0.0 (2018-02-27) Merged pull requests: * Structured Logging #30 (thommay) * RSpec: use 3.7, disable monkey patching mode #28 (olleolleolle) * README: Format a line of code using Markdown, not RDoc #24 (olleolleolle) * Travis: update Ruby versions, pass lint #22 (olleolleolle) * Require Ruby 2.2+ #20 (tas50)
* Update MASTER_SITES and HOMEPAGE ----- version 1.7.2 ------ 01-05 Mark Lindner <markl@avalon> * lib/libconfig.c - fixed slow leak in config_destroy() * <multiple> - miscellaenous build file fixes ----- version 1.7.1 ------ 2017-11-15 Mark Lindner <markl@avalon> * lib/wincompat.c, lib/wincompat.h - added fsync() implementation for Windows * lib/libconfig.c, lib/libconfig.h - added CONFIG_OPTION_FSYNC * lib/libconfigcpp.c++, lib/libconfig.h++ - added Config::OptionFsync * doc/libconfig.texi - Documentation updates 2017-11-14 Mark Lindner <markl@avalon> * lib/strbuf.c - bugfix in strbuf_append_char() ----- version 1.7 ------ 2017-10-24 Mark Lindner <markl@avalon> * INSTALL - Added information about installing from a git snapshot * configure.ac - Bumped version to 1.7 * doc/libconfig.texi - Updated documentation, added new chapter on libconfig bindings/implementations for other languages * examples/c/Makefile.am, examples/c/example4.c, examples/c/example4.cfg, examples/c/cfg_includes/*.cfg - New example program * lib/Makefile.am - bumped library version to 11:0:0; added new source files * lib/grammar.c, lib/grammar.y, lib/scanner.c, lib/scanner.h - regenerated * lib/grammar.y - allow optional trailing comma in lists and arrays * *.vcproj - updated with new source files, library dependency * lib/libconfig.c, lib/libconfig.h - various code cleanup; reworked options API; moved some value parsing logic into lib/util.c and lib/util.h; added new option CONFIG_OPTION_ALLOW_SCIENTIFIC_NOTATION; bugfix to disallow adding a group or a list to an array; changed default float precision from 2 to 6; fixed conversion between int and int64 types; added config_clear(); added support for include functions; added config_set_hook() and config_get_hook() * lib/libconfigcpp.c++, lib/libconfig.h++ - moved Option enum from Setting to Config; added OptionAllowScientificNotation; added clear(); reworked options API; added evaluateIncludePath(); fixed casting to unsigned int (don't clip negative values to 0) * lib/parsectx.c, lib/parsectx.h - code cleanup * lib/scanctx.c, lib/scanctx.h - added support for include functions; code cleanup; removed non-portable directory reading code; * lib/scanner.l - added support for include functions; moved some parsing code to lib/util.c and lib/util.h; code cleanup * lib/strbuf.c, lib/strbuf.h - added strbuf_append_char(); code cleanup * lib/strvec.c, lib/strvec.h - new functions for managing arrays of string pointers (for filename lists) * lib/util.c, lib/util.h - value parsing and formatting code and memory management macros and functions extracted from other files * lib/wincompat.h - new macros for testing relative paths; replaced INT32_MAX/INT32_MIN with INT_MAX/INT_MIN. * tests/tests.c - fixed test failures and improper testing of int type conversions ----- version 1.6 ------ 2015-12-31 Jose Luis Tallon <jltallon@adv-solutions.net> * Added include_dir feature (support for Debian-style conf.d/ includes) (pull request #36) * Added octal_ints feature (support for integer expressed in octal, useful for permissions and masks in UNIX-like systems (pull req #42) * Fixed "Removing a setting removes all siblings" (issue #41) Props random85 * Allow specifying the number of decimals wanted when outputting Based upon a suggestion by zhaopingsun (issue #31) * Make libconfig usable from CMake (pull request/issue #28) Props thfi * Documentation fixes - Copyright and examples - Included TeX patch from Debian (fixes FTBS with TeXlive) * Resync Debian packaging includes updated packages for GCC5 transition 2015-10-14 Thomas Fischer <fischer@unix-ag.uni-kl.de> * configure, configure.ac, debian/libconfig++9-dev.install, debian/libconfig9-dev.install, lib/Makefile.am, lib/Makefile.in, lib/libconfig++Config.cmake.in, lib/libconfigConfig.cmake.in, libconfig.spec.in - locating libconfig in CMake-based projects 2015-08-14 Mark Lindner <markl@neuromancer> * lib/wincompat.h - Fixed Windows portability issue * lib/libconfig.h++ - added missing operator[](std::string&).
2018-10-27 -- 0.9.0 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Out-of-bounds write in uriComposeQuery* and uriComposeQueryEx* Commit 864f5d4c127def386dd5cc926ad96934b297f04e Thanks to Google Autofuzz team for the report! * Fixed: Detect integer overflow in uriComposeQuery* and uriComposeQueryEx* Commit f76275d4a91b28d687250525d3a0c5509bbd666f Thanks to Google Autofuzz team for the report! * Fixed: Protect uriResetUri* against acting on NULL input Commit f58c25069cf4a986fe17a80c5b38687e31feb539 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Be fully compliant to C89 (GitHub #28) and C++98 in test code * Fixed: Fix off-by-one in uriComposeQueryCharsRequired* and ...Ex* Reported space requirements were 1 byte bigger than necessary * Changed: Marked as deprecated: Deprecated functions: uriNormalizeSyntaxMaskRequired[AW] uriParseUri[AW] uriParseUriEx[AW] * Added: Add convenience functions to ease user code to parse a single URI New functions: uriParseSingleUri[AW] uriParseSingleUriEx[AW] uriParseSingleUriExMm[AW] * Added: Support for custom memory managers (GitHub #26, #35), see Doxygen New functions (as extension of existing ones): uriAddBaseUriExMm[AW] uriComposeQueryMallocExMm[AW] uriDissectQueryMallocExMm[AW] uriFreeQueryListMm[AW] uriFreeUriMembersMm[AW] uriNormalizeSyntaxExMm[AW] uriParseSingleUriExMm[AW] uriRemoveBaseUriMm[AW] New functions (for convenience): uriCompleteMemoryManager uriEmulateCalloc uriEmulateReallocarray uriTestMemoryManager New error codes: URI_ERROR_MEMORY_MANAGER_FAULTY URI_ERROR_MEMORY_MANAGER_INCOMPLETE New types: UriFuncCalloc UriFuncFree UriFuncMalloc UriFuncRealloc UriFuncReallocarray UriMemoryManager * Added: Add non-void versions of uriNormalizeSyntaxMaskRequired* New functions: uriNormalizeSyntaxMaskRequiredEx[AW] * Changed: Migrate test suite from CppTest to GoogleTest 1.8.1 * Improved: Make test suite free of memory leaks (GitHub #31) Thanks to AddressSanitizer! * Removed: Support for pointless define URI_SIZEDOWN (GitHub #29) Related configure option --enable-sizedown has also been removed. * Soname: 1:23:0
Updated in wip by Paolo Vincenzo Olivo. Remove upstreamed patches. 2021-01-10 (0.6.3) Volker Gropp <bwmng(at)gropp.org> * remove outdated copyright and email * Merge pull request #25 from fweimer/patch-1 AC_QEF_C_NORETURN: Include <stdlib.h> for exit * Merge pull request #27 from ofalk/master Fix potential write to unallocated memory. * Merge pull request #28 from vgropp/#2-fix-csv-bits feat: #2 output bits in csv * Merge pull request #29 from vgropp/#2-fix-csv-bits fix(doc): #2 output bits in csv * Merge pull request #32 from vgropp/new-netstat-#5 feat: add support for newer (2016+) linux netstat #5 2019-01-01 14:50 (0.6.2) Volker Gropp <bwmng(at)gropp.org> * Merge pull request #22 from vgropp/issue-#13 to fix windows build * Merge pull request #20 from dreibh/master CSV file output: fix for timestamp inaccuracy and Y-2038 problem * Merge pull request #21 from vgropp/travisci add travisci * Merge pull request #17 from Himura2la/master Add the started time in "sum" mode * Merge pull request #18 from Himura2la/fix-dynamic Fix DYNAMIC and ANSIOUT in config * Merge pull request #10 from SoapGentoo/fixes Use `static inline` instead of `inline` * Merge pull request #9 from adventureloop/master Always fflush the pipe * Merge pull request #7 from samueloph/fsf_address_clean Update FSF address * Merge pull request #6 from samueloph/master Fix typos * fix nan and inf values on fast refresh (fixes debian bug #532331)
upstream NEWS content: Drop support for Python 3.6, which went end-of-life December 2021 by @anoadragon453 in #28 Configure setuptools to automatically discover new modules under src/matrix_common by @anoadragon453 in #27 Add a MXCUri class for representing Matrix media uri's by @anoadragon453 in #29
3.0.2 (2022-11-11) What's Changed * Simplify charset parsing by @semaperepelitsa in #28 3.0.1 (2022-10-08) What's Changed * Fix ReDos/performance when receiving crafted response headers by @ooooooo-q in #27 3.0.0 (2022-08-08) What's Changed * Add support for the new Faraday streaming API by @iMacTia in #26 Why a 3.0 release? What's the breaking change? Faraday 2.5 introduces a new streaming API and other changes that we want to take advantage on. However, releasing a new 2.x version of the gem would cause it to be pulled in projects where Faraday has not been updated to v2.5+ yet, causing errors. For this reason, we're instead releasing this as v3.0, which only the next (compatible) version of faraday will allow to use. 2.1.0 (2022-07-28) What's Changed * Handle verify_hostname ssl option by @kazarin in #23 2.0.3 (2022-05-17) What's Changed * Add Errno::EALREADY to list of Net::HTTP exceptions by @iMacTia in #21 2.0.2 (2022-04-10) What's Changed * Add Ruby 3.1 to CI by @petergoldstein in #15 * Anchor Encoding references to avoid faraday-encoding conflicts by @nbibler in #18 2.0.1 (2022-01-05) Fixes * Add back support for Faraday 1.0 2.0.0 (2022-01-04) What's Changed * Test on Ruby 3 by @tricknotes in #3 * Update gem to be compatible with Faraday 2.0 by @iMacTia in #9 * chore: Move development deps to Gemfile by @olleolleolle in #10 * refactor: CI: Inline scripts, cache gems by @olleolleolle in #11 * fix: gemspec metadata for changelog notes by @olleolleolle in #12 * Honor Content-Type charset by @xkwd in #13
3.0.2 (2022-11-11) What's Changed * Simplify charset parsing by @semaperepelitsa in #28 3.0.1 (2022-10-08) What's Changed * Fix ReDos/performance when receiving crafted response headers by @ooooooo-q in #27 3.0.0 (2022-08-08) What's Changed * Add support for the new Faraday streaming API by @iMacTia in #26 Why a 3.0 release? What's the breaking change? Faraday 2.5 introduces a new streaming API and other changes that we want to take advantage on. However, releasing a new 2.x version of the gem would cause it to be pulled in projects where Faraday has not been updated to v2.5+ yet, causing errors. For this reason, we're instead releasing this as v3.0, which only the next (compatible) version of faraday will allow to use. 2.1.0 (2022-07-28) What's Changed * Handle verify_hostname ssl option by @kazarin in #23 2.0.3 (2022-05-17) What's Changed * Add Errno::EALREADY to list of Net::HTTP exceptions by @iMacTia in #21 2.0.2 (2022-04-10) What's Changed * Add Ruby 3.1 to CI by @petergoldstein in #15 * Anchor Encoding references to avoid faraday-encoding conflicts by @nbibler in #18 2.0.1 (2022-01-05) Fixes * Add back support for Faraday 1.0 2.0.0 (2022-01-04) What's Changed * Test on Ruby 3 by @tricknotes in #3 * Update gem to be compatible with Faraday 2.0 by @iMacTia in #9 * chore: Move development deps to Gemfile by @olleolleolle in #10 * refactor: CI: Inline scripts, cache gems by @olleolleolle in #11 * fix: gemspec metadata for changelog notes by @olleolleolle in #12 * Honor Content-Type charset by @xkwd in #13
textproc/uriparser: security update Revisions pulled up: - textproc/uriparser/Makefile 1.11 - textproc/uriparser/distinfo 1.9 ------------------------------------------------------------------- Module Name: pkgsrc Committed By: bsiegert Date: Mon Oct 29 16:17:25 UTC 2018 Modified Files: pkgsrc/textproc/uriparser: Makefile distinfo Log Message: Update uriparser to 0.9.0. 2018-10-27 -- 0.9.0 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Out-of-bounds write in uriComposeQuery* and uriComposeQueryEx* Commit 864f5d4c127def386dd5cc926ad96934b297f04e Thanks to Google Autofuzz team for the report! * Fixed: Detect integer overflow in uriComposeQuery* and uriComposeQueryEx* Commit f76275d4a91b28d687250525d3a0c5509bbd666f Thanks to Google Autofuzz team for the report! * Fixed: Protect uriResetUri* against acting on NULL input Commit f58c25069cf4a986fe17a80c5b38687e31feb539 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Be fully compliant to C89 (GitHub #28) and C++98 in test code * Fixed: Fix off-by-one in uriComposeQueryCharsRequired* and ...Ex* Reported space requirements were 1 byte bigger than necessary * Changed: Marked as deprecated: Deprecated functions: uriNormalizeSyntaxMaskRequired[AW] uriParseUri[AW] uriParseUriEx[AW] * Added: Add convenience functions to ease user code to parse a single URI New functions: uriParseSingleUri[AW] uriParseSingleUriEx[AW] uriParseSingleUriExMm[AW] * Added: Support for custom memory managers (GitHub #26, #35), see Doxygen New functions (as extension of existing ones): uriAddBaseUriExMm[AW] uriComposeQueryMallocExMm[AW] uriDissectQueryMallocExMm[AW] uriFreeQueryListMm[AW] uriFreeUriMembersMm[AW] uriNormalizeSyntaxExMm[AW] uriParseSingleUriExMm[AW] uriRemoveBaseUriMm[AW] New functions (for convenience): uriCompleteMemoryManager uriEmulateCalloc uriEmulateReallocarray uriTestMemoryManager New error codes: URI_ERROR_MEMORY_MANAGER_FAULTY URI_ERROR_MEMORY_MANAGER_INCOMPLETE New types: UriFuncCalloc UriFuncFree UriFuncMalloc UriFuncRealloc UriFuncReallocarray UriMemoryManager * Added: Add non-void versions of uriNormalizeSyntaxMaskRequired* New functions: uriNormalizeSyntaxMaskRequiredEx[AW] * Changed: Migrate test suite from CppTest to GoogleTest 1.8.1 * Improved: Make test suite free of memory leaks (GitHub #31) Thanks to AddressSanitizer! * Removed: Support for pointless define URI_SIZEDOWN (GitHub #29) Related configure option --enable-sizedown has also been removed. * Soname: 1:23:0 To generate a diff of this commit: cvs rdiff -u -r1.10 -r1.11 pkgsrc/textproc/uriparser/Makefile cvs rdiff -u -r1.8 -r1.9 pkgsrc/textproc/uriparser/distinfo
2022-04-03: Gaupol 1.11 ======================= * Add IBM858, ISO-8859-11 and ISO-8859-16 encodings * Fix displayed line lengths being incorrect for subtitles with special characters such as apostrophes 2021-10-06: Gaupol 1.10.1 ========================= * Fix playing selection (#188) 2021-09-30: Gaupol 1.10 ======================= * Fix subtitle display when seeking to selection start (#181) * Fix search dialog result sometimes not being selected * Fix rare RecursionError with spell-check 2020-12-31: Gaupol 1.9 ====================== * Add framerates 30, 50, 59.94 and 60 fps (#164) * Add selecting next/previous from video position (#154) * Allow shifting positions of all open projects (#66) * Fix error dialog when video playback fails (#153) * Fix the order of audio tracks in the menu (#129, qnga) * Fix spell-check split words correction task to not hang (#171) * Add Dutch translation (Heimen Stoffels) 2020-04-10: Gaupol 1.8 ====================== * Add action set start from video position (#148) * Add and fix English spell-check special cases * Add and fix OCR spell-check special cases * Add Interlingue translation (OIS) * Add Portuguese translation (Hugo Carvalho) * Update translations 2019-08-04: Gaupol 1.7 ====================== * New app icon, as full-color and symbolic SVGs (#119) * Better initial preview experience (#136) * Disable loading of problematic gstreamer-vaapi (#79) * Use gspell for spell-check instead of PyEnchant and GtkSpell (#12) * Use the reverse domain name "io.otsaloma.gaupol" for desktop file, appdata file and icons 2019-06-08: Gaupol 1.6 ====================== * Add text correction pattern to unpack ligatures * Don't show video files in recent file menus (#130) * Update translations 2019-02-03: Gaupol 1.5 ====================== * Add support for building a Flatpak * Highlight changed parts in "Correct Texts" (#34) * Add keybinding Ctrl+I for toggling italic (#118) * Add keybinding Ctrl+I for toggling italic while editing (#118) * Change keybinding for Invert Selection to Ctrl+J * When opening multiple files, skip ones already open * Adapt to various GTK deprecations * Add 64x64 and 128x128 icons * Update AppData XML file * Bump iso-codes dependency to >= 3.67 * Update translations 2018-07-07: Gaupol 1.4.1 ======================== * Fix TypeErrors due to video player pipeline queries failing (#78) * Make 'setup.py --record' include compiled extensios as well (#91) 2018-05-01: Gaupol 1.4 ====================== * Update the `--video-file` argument to not just select the video file, but also load it in the internal video player (#75) * Fix subtitles with special characters not being displayed by the internal video player (#74) * Fix seeking to selection start if at less than one second (#76) * Fix pasting texts from outside Gaupol, e.g. from a text editor * Update checks for required GStreamer elements (#73) * Update translations 2017-11-12: Gaupol 1.3.1 ======================== * Fix pattern file syntax to not be corrupted by msgfmt (#70) 2017-11-11: Gaupol 1.3 ====================== * Use gtksink instead of autovideosink with the integrated video player, making it work on Wayland too (#60) * Add a hidden preference to disable autoplay (#57) * Allow loading video by drag-and-drop (#59) * Fix missing icon in GNOME shell on Wayland (#62) * Fix unhandled exception when adding recent menu items * Fix video player actions being sensitive when playback initialization fails (#52) * Fix Gaupol freezing after changing audio track (#58) * Fix error quitting if a file is still being loaded (#54) * Fix duplicate tags when decoding MPL2 (devcompl, #68) * Install appdata XML file under /usr/share/metainfo * Prefer iso-codes JSON files over XML files (#10) * Bump GStreamer dependency ≥ 1.6 * Drop build dependency on intltool (use gettext instead, #13) * Add donate button to about dialog * Update translations 2017-04-23: Gaupol 1.2 ====================== * Add support for the WebVTT file format (#46) * Add support for the LRC file format (#39) 2017-03-18: Gaupol 1.1 ====================== * Fix error when using the Save All As dialog to save all time-based format documents as frame-based or vice versa * Fix unhandled exception when trying to write non-numeric data into integer or float cells * Add Icelandic translation (Sveinn í Felli) * Remove severely incomplete Catalan, Polish and Swedish translations * Update translations 2016-10-29: Gaupol 1.0 ====================== * Fix size of custom font with GTK 3.22 (#40) * Show an error dialog if the integrated video player fails to initialize playback due to e.g. missing codecs * Fix error trying to undo more actions than exist when holding down Ctrl+Z (#38) 2016-08-20: Gaupol 0.92 ======================= * Fix error saving document from a time-based format to a frame-based or vice versa ([#28][]) * Fix error clicking undo or redo button dropdown arrow when no document is yet open ([#29][]) * Fix action states after subtitle cell editing cancelled ([#30][]) * Fix recent file menu states to update correctly ([#31][]) * Fix save as dialog to always add filename extension ([#32][]) * Update AppData file * Update translations [#28]: otsaloma/gaupol#28 [#29]: otsaloma/gaupol#29 [#30]: otsaloma/gaupol#30 [#31]: otsaloma/gaupol#31 [#32]: otsaloma/gaupol#32 2016-07-16: Gaupol 0.91 ======================= * Use header bars for dialogs * Migrate from deprecated `Gtk.UIManager`, `Gtk.Action` etc. to `Gtk.Application`, `Gio.Action` etc. * Add mpv for preview with precise seek (`--hr-seek=yes`) * Make mpv the default preview video player on non-Windows systems and set the default preview offset to one second * Make seek length configurable in the preferences dialog * Add find and replace to the toolbar * Have both Ctrl+F and Ctrl+H open the find and replace dialog * Have both Ctrl++, Ctrl+- and numpad equivalents control volume * Remove external video player output window (if you want to see that output, start Gaupol from a terminal) * Use a monospace editing font by default * Add support for IBM273, IBM1125, KOI8-T and KZ1048 character encodings (whether these are actually available depends on your version of Python) * Drop the bookmarks extension * Fix Cancel button behaviour when quitting Gaupol by closing the main window and having unsaved changes ([#14][]) * Fix line length measure em to be narrower ([#763589][]) * Have the text view right-click spell-check language menu set the language permanently * Don't show the "Use Shift+Return for line-break" help message if it's likely to overlap with the text being edited * Only force theme variant if `dark_theme` in config file is `true`, thus respecting any global settings ([#753315][]) * Make `GTK_THEME=Adwaita:dark gaupol` work correctly * Move web pages to <http://otsaloma.io/gaupol/> * Move releases to <https://github.com/otsaloma/gaupol/releases> * Move bug tracker to <https://github.com/otsaloma/gaupol/issues> * Move documentation to <https://github.com/otsaloma/gaupol/tree/master/doc> * Close mailing lists, use Gitter instead: <https://gitter.im/otsaloma/gaupol> * Use Transifex for translations: <http://www.transifex.com/otsaloma/gaupol/> * Update AppData file * Bump GTK dependency to ≥ 3.12 * Bump PyGObject dependency to ≥ 3.12 * Drop optional dependencies on PT fonts * Add Serbian translation (Miroslav Nikolić) * Update French translation (Jean van Kasteel) [#14]: otsaloma/gaupol#14 [#753315]: https://bugzilla.gnome.org/show_bug.cgi?id=753315 [#763589]: https://bugzilla.gnome.org/show_bug.cgi?id=763589
0.1.6.3 * Specify protocol.file.allow=always for latest git #28
Upstream changes: 1.17 2022-11-11 Todd Rinaldo <toddr@cpan.org> * Switch changelog entries to metacpan friendly format * #29 - Fix printf format conversion specifiers in croak to support size_t on all platforms * #11,#30 - Tty.pm: pre-allocate buffer for ioctl but leave it length 0 * #28 - Use $arg to match @ARGV in Makefile.PL
Upstream changes: 0.51 2022-08-15 - Bump min perl version to 5.16 (as per core Mojolicious) 0.50 2022-08-08 - Allow client_id / client_secret in body params (GH #28) 0.49 2022-06-02 - Fix tests broken by Mojolicious multiple render fixes (GH #27) 0.48 2021-06-15 - Accept error_description from auth methods (GH #26)
fastmap 1.1.1 ============= * Updated hopscotch-map library to 2.3.0. * Closed #24: Added a `$clone()` method to `fastmap`. (#26) * Fixed #27: If a `fastmap` object has no holes in the lists storing keys and values, and then it is serialized and then unserialized, the new `fastmap` would contain zero items. (#28) * Faster implementations of `fastmap` `$keys()` and `$as_list()` methods.
What's Changed - Add NetBSD by @0323pin in #3 - Migrate from tui-rs to ratatui by @AmmarAbouZor in #4 - settings improvements by @AmmarAbouZor in #13 - [Documentation] Create README Badges by @kevinmatthes in #14 - CI Improvements by @AmmarAbouZor in #15 - Changed: Help popup improvements by @AmmarAbouZor in #17 - Added: Export current journal's content by @AmmarAbouZor in #18 - Increase Version by @AmmarAbouZor in #19 - Fixed setting backend path from CLI by @AmmarAbouZor in #22 - Added: Release CD action by @AmmarAbouZor in #24 - Fixed: Export journal extension by @AmmarAbouZor in #25 - Changed: Enhance render loop by @AmmarAbouZor in #28 - Added: CITATION.cff by @kevinmatthes in #26 - Added: Edit current journal content in external editor by @AmmarAbouZor in #29 - Added: configure CHANGELOG maintenance utilities by @kevinmatthes in #16 - Added: Tabs and scrolling to help popup by @AmmarAbouZor in #32 - Fixed: bugs in fragment creation by @kevinmatthes in #33 - Added: Multi-selection for journals by @AmmarAbouZor in #34 - Changed: bump baptiste0928/cargo-install to v2.1.0 by @kevinmatthes in #36 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #37 - Added: Export Import functions for multiple journals by @AmmarAbouZor in #39 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #40 - Fixed: Synchronizing problems with sqlite back-end by @AmmarAbouZor in #41 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #42 - Changed: improve GHA linting speed dramatically by @kevinmatthes in #43 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #44 - Addd: Option to Use Git Configured Editor as External editor by @AmmarAbouZor in #45 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #46 - [Aeruginous] Create Missing CHANGELOG Fragments by @AmmarAbouZor in #48 - Chore: Add dependabot by @AmmarAbouZor in #50 - [Aeruginous] Assemble CHANGELOG by @github-actions in #52
v1.3.1 Changes Drop 3.7 support by @bagel897 in #28 do sys path hack by @bagel897 in #31 Misc Update deps by @bagel897 in #29 Update docs by @bagel897 in #30 v.1.3.0 Features Enum Support by @bagel897 in #19 Misc Use trusted publishing by @bagel897 in #17 deduplicate ci by @bagel897 in #20 chore: Configure Renovate by @renovate in #21 chore(deps): update pre-commit hook hadialqattan/pycln to v2.4.0 by @renovate in #23 chore(deps): update pre-commit hook pre-commit/mirrors-prettier to v3.1.0 by @renovate in #25 chore(deps): update pre-commit hook psf/black to v23.12.1 by @renovate in #26 chore(deps): update pre-commit hook charliermarsh/ruff-pre-commit to v0.1.11 by @renovate in #22 chore(deps): update actions/checkout action to v4 by @renovate in #27
Changes from changelog: [4.16.0] 2024-01-14 Added - Include a check to prevent multiple entries with the same keys in 'bin/validate_json_data.py' - Reuse translations from ISO 639-2 for ISO 639-5 Changed - Rename nb.po to nb_NO.po - Rename mo.po to ro_MD.po - Translation updates for ISO 3166-1 - Translation updates for ISO 3166-2 - Translation updates for ISO 3166-3 - Translation updates for ISO 639-2 - Translation updates for ISO 639-3 - Translation updates for ISO 639-5 - Translation updates for ISO 4217 - Translation updates for ISO 15924 - Reformat python files with black Fixed - Fix: always use country code for parent in ISO 3166-2 - ISO 3166-2: Fix subdivision names for Finland. Fixes #37 [4.15.0] 2023-04-27 Changed - Translation updates for ISO 3166-1 - Translation updates for ISO 3166-3 - Translation updates for ISO 639-2 [4.14.0] 2023-04-27 Changed - Translation updates for ISO 3166-1 - Translation updates for ISO 3166-2 - Translation updates for ISO 3166-3 - Translation updates for ISO 639-2 - Translation updates for ISO 639-3 - Translation updates for ISO 639-5 - Translation updates for ISO 4217 - Translation updates for ISO 15924 Fixed * ISO 3166-2: Fix wrong Spanish translation [4.13.0] 2023-02-28 Added - ISO 3166-1: Add missing common names for Laos, Iran, and Syria. Fixes #32 Changed - Translation updates for ISO 3166-1 - Kazakh from Debian BTS. Closes: #1025423 - Catalan from Debian BTS. Closes: #1026972 - Translation updates for ISO 3166-2 - Translation updates for ISO 3166-3 - Translation updates for ISO 639-2 - Translation updates for ISO 639-3 - Translation updates for ISO 639-5 - Translation updates for ISO 4217 - Translation updates for ISO 15924 Fixed - ISO 3166-3: Fix withdrawal dates of AN, CS and YU. Fixes #28 [4.12.0] 2022-11-06 Changed - ISO 3166-1: Update name for TR (Turkiye). Fixes #38 - Translation updates for ISO 3166-1 - Translation updates for ISO 3166-2. Closes: #1020633 - Translation updates for ISO 3166-3 - Translation updates for ISO 639-2 - Translation updates for ISO 639-3 - Translation updates for ISO 639-5 - Translation updates for ISO 4217 - Translation updates for ISO 15924 Fixed - ISO 3166-2: Remove comment from Dutch translation. Fixes #41
What's Changed Fix NetBSD's host checkup. by @fraggerfox in #24 Added better kernel support for MorphOS by @polluks in #27 make strip_color_code_stuff not use awk or sed by @st0rmw1ndz in #28 Fix a bug where cargo reported 1 installed package when none were installed Fixed a bug where zsh would report a decimal number for used memory Updated the EndeavourOS logo with better colors Fixed bug where the space between the logo and info text was sometimes inconsistent Support the $NO_COLOR environment variable
Revision history for App-ClusterSSH 4.16 2020-06-20 Duncan Ferguson <duncan_ferguson@user.sf.net> - Further fix for 'resolve_names' error when adding hosts via the UI - Fix missing space separator for ssh_args (thanks to Petr Vorel) 4.15 2020-05-18 Duncan Ferguson <duncan_ferguson@user.sf.net> - Include all utilies within each man page - Add in 'command_pre' and 'command_post' configuration options - Fix 'Add Host' menu error finding 'resolved_names' - Ensure lib path is added to range tests to find the libraries - Mark permission test as TODO as it appears to be inconsistent 4.14 2019-08-21 Duncan Ferguson <duncan_ferguson@user.sf.net> - Include README within the repository, not just created tar.gz files - Add 'autoquit' setting to 'File' menu (Github issue #114) - Correct macro_hostname to be the FQDN of the server where cssh is being run (Github issue #116) - Add in user defined macros 4.13.2_02 2019-01-14 Duncan Ferguson <duncan_ferguson@user.sf.net> - Fix Getopt-Long minimum version - Fix excess test output when Sort::Naturally isn't installed 4.13.2_01 2018-11-24 Duncan Ferguson <duncan_ferguson@user.sf.net> - Move all Tk code into its own module as-is - Fix for 'bad pad value "3m"' error when using Tk 804.034 - Update to Perl::Tidy 20181117 - Convert to using Dist::Zilla 4.13.2 2018-03-14 Duncan Ferguson <duncan_ferguson@user.sf.net> - Fix for running builds in parallel - Improvements to SUPPORT and REPORTING BUGS sections in documentation 4.13.1 2018-03-05 Duncan Ferguson <duncan_ferguson@user.sf.net> - Minor update to fix failing tests due to 3rd party perltidy changes 4.13 2017-12-27 Duncan Ferguson <duncan_ferguson@user.sf.net> - Ensure ssh_args is keep unset if it is emptied in the configuration file - Obey configured console position (Debian bug 758215) (Github issue #100) 4.12 2017-12-23 Duncan Ferguson <duncan_ferguson@user.sf.net> - Fix 'undefined value' error 4.11 2017-12-22 Duncan Ferguson <duncan_ferguson@user.sf.net> - Fix for multiple range expansion, as in 'h{a,b}{1,2}' (Github issue #97) (Thanks to lazyfrosch) - Upgrade Perl::Tidy requirement to version 20171214 (Github issue #99) (Thanks to eserte) - Add in 'external command pipe' to allow for some commands being passed in from the command line 4.10_02 2017-08-08 Duncan Ferguson <duncan_ferguson@user.sf.net> - Include coverage tests in the resources - Include the version of cssh in the utility documentation and README - Fix dashes (-) not being accepted in hostname range expansion (Github issue #89) - Amend ranges to work on ports, FQDN's and IP addresses - Fix bug tracker links in the main documentation (Github issue #92) - New options to specify --rows, --columns and --fillscreen (Github pull request #88) (Thanks to AsharLohmar) 4.10_01 2017-04-12 Duncan Ferguson <duncan_ferguson@user.sf.net> - Allow 'include' directives when reading SSH configuration files (Github issue #77) (thanks to Azenet) - Generate README when creating the distribution from cssh man page so www.cpan.org and www.metacpan.org can display documentation 4.09 2017-03-11 Duncan Ferguson <duncan_ferguson@user.sf.net> - Add perl-5.24 Travis-CI automated testing config - Correct a logic bug around the --debug option (Github issue #75) - Fix 'Re-add closed windows' not using the correct username (Github issue #72) - Update copyright year - Make WM decorations algorithm configurable as causes problems on some systems (Debian bug 842965, re Github pull request #66) (thanks to Tony Mancill) 4.08 2016-10-18 Duncan Ferguson <duncan_ferguson@user.sf.net> - Add perl-5.8, 5.10 and 5.12 to Travis-CI automated testing - Fix building and testing on perl-5.8.9 - Improve testing on systems that do not have xterm installed - Take into account WM decorations when tiling (Github pull request #66) (thanks to Andrew Stevenson) - Add option in the config file to hide the menu (Github issue #69) - Add 'unique_servers' into the configuration file to match command line option (Github issue #70) 4.07 2016-04-30 Duncan Ferguson <duncan_ferguson@user.sf.net> - Fixed tests on systems where bash is not installed in /bin/bash (Github issue #60) - Include link to travis-ci site in release emails for automated build and test reports - Rework hostname expansion to be pure-perl rather than relying on the bash shell (Github issue #53) 4.06 2016-03-26 Duncan Ferguson <duncan_ferguson@user.sf.net> - Failure to find the terminal binary should not be fatal - Fix processing of '--extra_tag_file' and its configuration item (Github issue #51) - Add bash shell expansion on host names containing a '{' character (Github issue #53) - Fix tests when running on a server without xterm installed (such as Travis CI via GitHub) - Expand $HOME and ~ correctly when looking for files (thanks to Andrew Stevenson) - Typo correction in README (thanks to Ankit Vadehra) 4.05 2015-11-28 Duncan Ferguson <duncan_ferguson@user.sf.net> - Change default key_quit from 'Control-q' to 'Alt-q' (Github issue #50) - Amend tests to always use C locale as some error messages are hardcoded in English (Github issue #49) 4.04_01 2015-11-21 Duncan Ferguson <duncan_ferguson@user.sf.net> - Ensure documentation is generated using same perl as the build (Github issue #45) - Pass '--action' through macro parsing (Github issue #42) - Workaround for glitch in KDE where windows can become unmoveable (Github issue #46) (thanks to Brandon Perkins) - Add in '--quiet | -Q ' option to reduce output in certian scenarios - Add in 'csftp' command 4.04 2015-11-03 Duncan Ferguson <duncan_ferguson@user.sf.net> - Include bash completion script in distribution (Github issue #29) - Allow re-adding closed session (Github issue #27 - thanks to Andrew Stevenson) - Allow sorting windows in natural order (Github isue #28 - thanks to Andrew Stevenson) - Fix links in metadata files to trackers (Github issue #41) - Fix ctel and ccon not working correctly (Github issue #35) - Amend t/10host.t to use a random hostname to prevent clashes (Github issue #23) - Amend coght message in README to match all other files for the perl license
# evaluate 1.0.1 * Fix buglet revealed when by using `rlang::abort()` inside of `evaluate()`. # evaluate 1.0.0 * Setting `ACTIONS_STEP_DEBUG=1` (as in a failing GHA workflow) will automatically set `log_echo` and `log_warning` to `TRUE` (#175). * evaluate works on R 3.6.0 once again. * `evaluate()` improvements: * Now terminates on the first error in a multi-expression input, i.e. `1;stop('2');3` will no longer evaluate the third component. This matches console behaviour more closely. * Calls from conditions emitted by top-level code are automatically stripped (#150). * Result has a class (`evaluate_evaluation`/`list`) with a basic print method. * Plots created before messages/warnings/errors are correctly captured (#28). * Handler improvements: * The default `value` handler now evaluates `print()` in a child of the evaluation environment. This largely makes evaluate easier to test, but should make defining S3 methods for print a little easier (#192). * The `source` output handler is now passed the entire complete input expression, not just the first component. * `evalute(include_timing)` has been deprecated. I can't find any use of it on GitHub, and it adds substantial code complexity for little gain. * `is.value()` has been removed since it tests for an object that evaluate never creates. * New `local_reproducible_output()` helper that sets various options and env vars to help ensure consistency of output across environments. * `parse_all()` adds a `\n` to the end of every line, even the last one if it didn't have one in the input. Additionally, it no longer has a default method, which will generate better errors if you pass in something unexpected. * New `trim_intermediate_plots()` drops intermediate plots to reveal the complete/final plot (#206). * `watchout()` is no longer exported; it's really an implementation detail that should never have been leaked to the public interface. # evaluate 0.24.0 * The `source` output handler can now take two arguments (the unparsed `src` and the parsed `call`) and choose to affect the displayed source. * The package now depends on R 4.0.0 in order to decrease our maintenance burden.
# wk 0.9.4 - Ensure package tests pass against sf 1.0-18 (#224, #225). # wk 0.9.3 - Ensure package compiles with `STRICT_R_HEADERS=1` (#222). # wk 0.9.2 - Add `wk_crs()` and `wk_set_crs()` methods for `bbox` (#213) - Fix wk_trans inconsistent meta flags handling (#217) - Ensure package builds on arm64 for Windows (#220) # wk 0.9.1 - Fix format strings/arguments for R-devel (#209). # wk 0.9.0 ## Breaking changes - The common well-known binary representation of POINT EMPTY (i.e., POINT (nan nan)) is now handled as POINT EMPTY allowing empty points to roundtrip through `wkb()` vectors (#196, #204). - `xy(NA, NA)` is now read as a null feature instead of POINT EMPTY. This preserves the invariant that null features can also be identified using `is.na()` (#205). - `xy(NaN, NaN)` is now read as POINT EMPTY and `is.na(xy(NaN, NaN))` now returns `FALSE`. This means that both EMPTY and null points can roundtrip through `xy()` (#205). ## Bugfixes and improvements - `wk_meta()` now contains a new column `is_empty`, which is `TRUE` for any feature that contains at least one non-empty coordinate. This allows more efficient detection of features with zero coordinates (#197, #199). - Updated PROJ data to use the latest pull of the database packaged with PROJ 9.3.0 (#201). - The wk package now compiles once again on gcc 4.8 (#203, #206). - Fixed `sfc_writer()` to correctly attach the `classes` attribute to sfc output with mixed geometry types (#195). - Function `sfc_writer()` now has an argument `promote_multi` to write any input as the MULTI variant. This makes it more likely that an input vector will be read as a single geometry type (#198). - The `wk_collection_filter()` now correctly increments the `part_id` when calling the child handler (@brownag, #194). # wk 0.8.0 * Added `wkb_to_hex()` (@anthonynorth, #183). * Implemented `vctrs::vec_proxy_equal()` for `wkb()` vctrs (@anthonynorth, #183). * Fixed `sfc_writer()`, which had returned NULL for some inputs (e.g., via `wk_collection()`) (@anthonynorth, #182, #186). * Added `wk_clockwise()` and `wk_counterclockwise()` to re-wind polygon rings (@anthonynorth, #188). * New replacement-function mode for `wk_coords<-()` for in-place modification of coordinates (@mdsumner, #187). * New function `wk_trans_explicit()` migrated from crs2crs (@mdsumner, #187). # wk 0.7.3 * Fix tests for updated waldo package (#178). # wk 0.7.2 * Fix use-after-free warnings. # wk 0.7.1 * Fix implicit reliance on error `as.data.frame.default()`, which no longer occurs in r-devel (#166). # wk 0.7.0 * Remove legacy headers that are no longer used by any downstream package (#146). * `validate_wk_wkt()` now errors for an object that does not inherit from 'wk_wkt' (#123, #146). * Added `wk_crs_projjson()` to get a JSON representation of a CRS object. To make lookup possible based on shortcut-style CRS objects (e.g., `"EPSG:4326"` or `4326`), added data objects `wk_proj_crs_view` and `wk_proj_crs_json` that contain cached versions of rendered PROJJSON based on the latest PROJ version (#147). * Added a `wk_crs_proj_definition()` method for `wk_crs_inherit()` (#136, #147). * Conversion to sf now uses the `sfc_writer()` for all wk classes, making conversions faster and fixing at least one issue with conversion of NA geometries to sf (#135). * `wk_plot()` now plots `NULL`/`NA` geometries and mixed geometry types more reliably (#142, #143, #149). * Exported EMPTY geometries to well-known text now include dimension (e.g., `POINT Z EMPTY`) (#141, #150). * Fixed bug where `wk_polygon()` doubled some points when the input contained closed rings (#134, #151). * Fixed bug where `wk_count()` exposed uninitialized values for empty input (#139, #153). * The `xy_writer()` now opportunistically avoids allocating vectors for Z or M values unless they are actually needed (#131, #154). * Added example WKT for all geometry types and dimensions plus helper `wk_example()` to access them and set various properties (#155). * Fixes warnings when compiling with `-Wstrict-prototypes` (#157, #158). * Removed `wk_chunk_map_feature()` in favour of using chunking strategies directly (#132, #159). * Optimized `wk_coords()` for `xy()` objects (#138, #160). * Added accessor methods for record-style vectors: `rct_xmin()`, `rct_xmax()`, `rct_ymin()`, `rct_ymax()`, `rct_width()`, `rct_height()`, `crc_center()`, `crc_x()`, `crc_y()`, `crc_r()`, `xy_x()`, `xy_y()`, `xy_z()`, and `xy_m()` (#144, #161). * Added rectangle operators `rct_intersects()`, `rct_contains()`, and `rct_intersection()` (#161). # wk 0.6.0 * Fixed `wk_affine_rescale()` to apply the translate and scale operations in the correct order (#94). * Add `wk_handle_slice()` and `wk_chunk_map_feature()` to support a chunk + apply workflow when working with large vectors (#101, #107). * C and R code was rewritten to avoid materializing ALTREP vectors (#103, #109). * Added a `wk_crs_proj_definition()` generic for foreign CRS objects (#110, #112). * Added `wk_crs_longlat()` helper to help promote authority-compliant CRS choices (#112). * Added `wk_is_geodesic()`, `wk_set_geodesic()`, and argument `geodesic` in `wkt()` and `wkb()` as a flag for objects whose edges must be interpolated along a spherical/ellipsoidal trajectory (#112). * Added `sf::st_geometry()` and `sf::st_sfc()` methods for wk geometry vectors for better integration with sf (#113, #114). * Refactored well-known text parser to be more reusable and faster (#115, #104). * Minor performance enhancement for `is.na()` and `validate_wk_wkb()` when called on a very long `wkb()` vector (#117). * Fixed issue with `validate_wk_wkb()` and `validate_wk_wkt()`, which failed for most valid objects (#119). * Added `wk_envelope()` and `wk_envelope_handler()` to compute feature-wise bounding boxes (#120, #122). * Fixed headers and tests to pass on big endian systems (#105, #122). * Incorporated the geodesic attribute into vctrs methods, data frame columns, and bbox/envelope calculation (#124, #125). * Fix `as_xy()` for nested data frames and geodesic objects (#126, #128). * Remove deprecated `wkb_problems()`, `wkt_problems()`, `wkb_format()`, and `wkt_format()` (#129). * `wk_plot()` is now an S3 generic (#130). # wk 0.5.0 * Fixed bugs relating to the behaviour of wk classes as vectors (#64, #65, #67, #70). * `crc()` objects are now correctly exported as polygons with a closed loop (#66, #70). * Added `wk_vertices()` and `wk_coords()` to extract individual coordinate values from geometries with optional identifying information. For advanced users, the `wk_vertex_filter()` can be used as part of a pipeline to export coordinates as point geometries to another handler (#69, #71). * Added `wk_flatten()` to extract geometries from collections. For advanced users, the `wk_flatten_filter()` can be used as part of a pipeline (#75, #78). * `options("max.print")` is now respected by all vector classes (#72, #74). * Moved implementation of plot methods from wkutils to wk to simplify the dependency structure of both packages (#80, #76). * Added `wk_polygon()`, `wk_linestring()`, and `wk_collection()` to construct polygons, lines, and collections. For advanced users, `wk_polygon_filter()`, `wk_linestring_filter()`, and `wk_collection_filter()` can be used as part of a pipeline (#77, #84). * Added a C-level transform struct that can be used to simplify the the common pattern of transforming coordinates. These structs can be created by other packages; however, the `wk_trans_affine()` and `wk_trans_set()` transforms are also built using this feature. These are run using the new `wk_transform()` function and power the new `wk_set_z()`, `wk_set_m()`, `wk_drop_z()`, `wk_drop_m()`, functions (#87, #88, #89). # wk 0.4.1 * Fix LTO and MacOS 3.6.2 check errors (#61). # wk 0.4.0 * Removed `wksxp()` in favour of improved `sf::st_sfc()` support (#21). * Rewrite existing readers, writers, and handlers, using a new C API (#13). * Use new C API in favour of header-only approach for all wk functions (#19, #22). * Use cpp11 to manage safe use of callables that may longjmp from C++. * Vector classes now propagate `attr(, "crs")`, and check that operations that involve more than one vector have compatable CRS objects as determined by `wk_crs_equal()`. * Added an R-level framework for other packages to implement wk readers and handlers: `wk_handle()`, `wk_translate()`, and `wk_writer()` (#37). * Added a native reader and writer for `sf::st_sfc()` objects and implemented R-level generics for sfc, sfg, sf, and bbox objects (#28, #29, #38, #45). * Implement `crc()` vector class to represent circles (#40). * Added a 2D cartesian bounding box handler (`wk_bbox()`) (#42). * Refactored unit tests reflecting use of the new API and for improved test coverage (#44, #45, #46). * Added `wk_meta()`, `wk_vector_meta()`, and `wk_count()` to inspect properties of vectors (#53). * Modified all internal handlers such that they work with vectors of unknown length (#54). # wk 0.3.4 * Fixed reference to `wkutils::plot.wk_wksxp()`, which no longer exists. # wk 0.3.3 * Fixed WKB import of ZM geometries that do not use EWKB. * Added `xy()`, `xyz()`, `xym()` and `xyzm()` classes to efficiently store point geometries. * Added the `rct()` vector class to efficiently store two-dimensional rectangles. * Fixed the CRAN check failure caused by a circular dependency with the wkutils package. * Added S3 methods to coerce sf objects to and from `wkt()`, `wkb()` and `wksxp()`. # wk 0.3.2 * Fixed EWKB output for collections and multi-geometries that included SRID (#3). * Fixed CRAN check errors related to exception handling on MacOS/R 3.6.2. # wk 0.3.1 * Added a `NEWS.md` file to track changes to the package.
Added New display formats for enhanced visualization: git: Display Git status information for files grid: Present files in an organized grid layout sizemap: Visualize file sizes with proportional representation table: Show files in a structured table format timeline: Group files by creation/modification dates Interactive plugin management system Plugin update functionality via CLI Extended configuration options for customization Plugin support for default and long format customization Enhanced Significant performance improvements: Optimized tree view rendering More efficient recursive file listing Better memory management for large directories Plugin system improvements: Refined plugin interface for better integration More robust plugin installation process Enhanced plugin discovery and loading Sorting functionality: More accurate file sorting across all formats Improved performance for large directory sorting Fixed Memory leaks in recursive directory listing Plugin installation reliability issues Color output consistency across different formats What's Changed docs: add AUR instructions by @malteo in #28 Add Homebrew to readme by @triyanox in #30 Enhance display formats, plugin system, and performance optimizations for file listing by @triyanox in #31
textproc/uriparser: security update Revisions pulled up: - textproc/uriparser/Makefile 1.11 - textproc/uriparser/distinfo 1.9 ------------------------------------------------------------------- Module Name: pkgsrc Committed By: bsiegert Date: Mon Oct 29 16:17:25 UTC 2018 Modified Files: pkgsrc/textproc/uriparser: Makefile distinfo Log Message: Update uriparser to 0.9.0. 2018-10-27 -- 0.9.0 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Out-of-bounds write in uriComposeQuery* and uriComposeQueryEx* Commit 864f5d4c127def386dd5cc926ad96934b297f04e Thanks to Google Autofuzz team for the report! * Fixed: Detect integer overflow in uriComposeQuery* and uriComposeQueryEx* Commit f76275d4a91b28d687250525d3a0c5509bbd666f Thanks to Google Autofuzz team for the report! * Fixed: Protect uriResetUri* against acting on NULL input Commit f58c25069cf4a986fe17a80c5b38687e31feb539 >>>>>>>>>>>>> SECURITY >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Fixed: Be fully compliant to C89 (GitHub #28) and C++98 in test code * Fixed: Fix off-by-one in uriComposeQueryCharsRequired* and ...Ex* Reported space requirements were 1 byte bigger than necessary * Changed: Marked as deprecated: Deprecated functions: uriNormalizeSyntaxMaskRequired[AW] uriParseUri[AW] uriParseUriEx[AW] * Added: Add convenience functions to ease user code to parse a single URI New functions: uriParseSingleUri[AW] uriParseSingleUriEx[AW] uriParseSingleUriExMm[AW] * Added: Support for custom memory managers (GitHub #26, #35), see Doxygen New functions (as extension of existing ones): uriAddBaseUriExMm[AW] uriComposeQueryMallocExMm[AW] uriDissectQueryMallocExMm[AW] uriFreeQueryListMm[AW] uriFreeUriMembersMm[AW] uriNormalizeSyntaxExMm[AW] uriParseSingleUriExMm[AW] uriRemoveBaseUriMm[AW] New functions (for convenience): uriCompleteMemoryManager uriEmulateCalloc uriEmulateReallocarray uriTestMemoryManager New error codes: URI_ERROR_MEMORY_MANAGER_FAULTY URI_ERROR_MEMORY_MANAGER_INCOMPLETE New types: UriFuncCalloc UriFuncFree UriFuncMalloc UriFuncRealloc UriFuncReallocarray UriMemoryManager * Added: Add non-void versions of uriNormalizeSyntaxMaskRequired* New functions: uriNormalizeSyntaxMaskRequiredEx[AW] * Changed: Migrate test suite from CppTest to GoogleTest 1.8.1 * Improved: Make test suite free of memory leaks (GitHub #31) Thanks to AddressSanitizer! * Removed: Support for pointless define URI_SIZEDOWN (GitHub #29) Related configure option --enable-sizedown has also been removed. * Soname: 1:23:0 To generate a diff of this commit: cvs rdiff -u -r1.10 -r1.11 pkgsrc/textproc/uriparser/Makefile cvs rdiff -u -r1.8 -r1.9 pkgsrc/textproc/uriparser/distinfo
# isoband 0.2.7 - Remove compile-time dependency on testthat. - Changed maintainer after the original author (Claus Wilke) donated codebase to r-lib. isoband 0.2.6 ---------------------------------------- - Update to the latest testthat headers for compatibility with LLVM clang 15.0.0. - Correct label angle for current aspect ratio in `isolines_grob()` (#28, @eliocamp). isoband 0.2.5 ---------------------------------------- - Add a new label placer function `label_placer_middle()` (#24, @jamarav). - The vendored testthat/catch code now uses a constant value for the stack size rather than relying on `SIGSTKSZ`. See: r-lib/testthat#1373
# Rdpack 2.6.2 - `RStudio_reprompt` now issues a more informative error message when not called on a suitable file or function. Fixes issue #30, reported by @daattali. - now the LaTeX macro `\slash` is wrapped in a condition, so that it is passed on for LaTeX related output but converted to `/` for other formats (such as html). Fixes GeoBosh/rbibutils#9, reported by @MLopez-Ibanez. - fixed the test for the fix in Rdpack v2.6.1 (see below) to work with R-4.4.2, since that R-devel change was not carried on to R-4.4.2. (Note: the error concerns the test only. The fix in the code of the package works for any R version.) Fixes issue #37, reported by @charles-plessy. # Rdpack 2.6.1 - R-devel c86938 turned to error the warning for a non-existing key in the bib file. Fixed `insert_bib` (and a related test) to handle that. # Rdpack 2.6 - fixed issues causing 'lost braces' (actually, superfluous braces) NOTEs from checks in R-devel occuring with some accented LaTeX characters. These NOTEs are not yet activated on CRAN but if/when they do, developers using Rd macros `\insertRef` and `\insertCite` can eliminate them by building their packages with Rdpack (>= 2.6) and rbibutils (>= 2.2.16). Thanks to Sebastian Meyer for tracing down the issues. - fixed a `Sweave` expression in 'man/predefined.Rd' to not emit unnecessary braces (see the note above). # Rdpack 2.5 - Rd macros `insertCite` and friends were calling `\insert_citeOnly()` with argument `key` instead of `keys`. This was not an error since partial matching is ok here but not good practice. Fixes issue #28 reported by Marcel Ramos. - changed the saved value in "tests/testthat/dummyArticle.rds" used in 'test-bib.R' with a value obtained with R-devel r84896 n previu versins of R there wasasuperfluous final ' .'). - in some cases when square brackets were requested, rather than round ones, `\insertCiteOnly` was using closing round parenthesis. - in some cases `\insertCiteOnly` was not handling well the last cite when it was followed by free text.
## Changes in version 0.14.1 **Released on March 29th, 2025.** * Issue #263: fix release tarball by relying on `make dist`. * Document ATF to Kyua mappings for metadata properties. * Support `require.diskspace` ATF metadata property. * Support backwards compatible `unprivileged_user` metadata property for ease of use dealing with ATF vs Kyua. * Fix building from source by tracking `utils/process/Kyuafile.in` and `engine/execenv/execenv_fwd.hpp` with automake. ## Changes in version 0.14 **Released on December 31st, 2024.** * Replace `--with-atf` with `--enable-atf`. The latter must be specified to enable ATF support and the Kyua tests by proxy. * Require newer versions of ATF (0.21) and Lutok (0.5). This is being done as part of a multi-phase deprecation of pre-C++11 environments. * Vendor the ATF m4 files from the freebsd/atf repo. * Translate `is_exclusive` metadata to its ATF counterpart. * Issue #236: fix accidental test forkbomb in specific user environments with `integration` tests by avoiding infinite recursion calling kyua. * Fix the build on Ubuntu 24.04. - execenv support added. This FreeBSD-specific feature allows tests to be executed in jails. * Issue #169: Remove deprecated `readdir_r` use. * Fix build issue on more recent versions of MacOS. * Fix build issue on IllumOS. * Fix issues with PID reuse in testcases. * Escape characters captured from stderr and stdout in HTML output. * `integration/cmd_report_test:verbose`: fix regular expression used in tests which would break in certain user environments. * Add Cirrus CI support for testing Kyua on FreeBSD. * Remove `UTILS_UNUSED_PARAM` macro. * Fix document rendering with newer versions of doxygen. * Issue #152: explicitly require C++11 language features when compiling Kyua. Remove `std::shared_ptr` compatibility header, `utils/shared_ptr.hpp`. * Fix `igor` and `mandoc -Tlint` reported issues with generated manpages. * Issue #167: fix typos in kyua(1) manpage. ## Changes in version 0.13 **Released on August 26th, 2016.** * Fixed execution of test cases as an unprivileged user, at least under NetBSD 7.0. Kyua-level failures were probably a regression introduced in Kyua 0.12, but the underlying may have existed for much longer: test cases might have previously failed for mysterious reasons when running under an unprivileged user. * Issue #134: Fixed metadata test broken on 32-bit platforms. * Issue #139: Added per-test case start/end timestamps to all reports. * Issue #156: Fixed crashes due to the invalid handling of cleanup routine data and triggered by the reuse of PIDs in long-running Kyua instances. * Issue #159: Fixed TAP parser to ignore case while matching `TODO` and `SKIP` directives, and to also recognize `Skipped`. * Fixed potential crash due to a race condition in the unprogramming of timers to control test deadlines. ## Changes in version 0.12 **Released on November 22nd, 2015.** This is a huge release and marks a major milestone for Kyua as it finally implements a long-standing feature request: the ability to execute test cases in parallel. This is a big deal because test cases are rarely CPU-bound: running them in parallel yields much faster execution times for large test suites, allowing faster iteration of changes during development. As an example: the FreeBSD test suite as of this date contains 3285 test cases. With sequential execution, a full test suite run takes around 12 minutes to complete, whereas on a 4-core machine with a high level of parallelism it takes a little over 1 minute. Implementing parallel execution required rewriting most of Kyua's core and partly explains explains why there has not been a new release for over a year. The current implementation is purely subprocess-based, which works but has some limitations and has resulted in a core that is really complex and difficult to understand. Future versions will investigate the use of threads instead for a simplified programming model and additional parallelization possibilities. * Issue #2: Implemented support to execute test cases in parallel when invoking `kyua test`. Parallel execution is *only* enabled when the new `parallelism` configuration variable is set to a value greater than `1`. The default behavior is still to run tests sequentially because some test suites contain test cases with side-effects that might fail when run in parallel. To resolve this, the new metadata property `is_exclusive` can be set to `true` on a test basis to indicate that the test must be run on its own. * Known regression: Running `kyua debug` on a TAP-based test program does not currently report the output in real time. The output will only be displayed once the test program completes. This is a shortcoming of the new parallel execution engine and will be resolved. * Removed the external C-based testers code in favor of the new built-in implementations. The new approach feels significantly faster than the previous one. * Fixed the handling of relative paths in the `fs.*` functions available in `Kyuafile`s. All paths are now resolved relative to the location of the caller `Kyuafile`. `Kyuafile.top` has been updated with these changes and you should update custom copies of this file with the new version. * Changed temporary directory creation to always grant search permissions on temporary directories. This is to prevent potential problems when running Kyua as root and executing test cases that require dropping privileges (as they may later be unable to use absolute paths that point inside their work directory). * The cleanup of work directories does not longer attempt to deal with mount points. If a test case mounts a file system and forgets to unmount it, the mount point will be left behind. It is now the responsibility of the test case to clean after itself. The reasons for this change are simplicity and clarity: there are many more things that a test case can do that have side-effects on the system and Kyua cannot protect against them all, so it is better to just have the test undo anything it might have done. * Improved `kyua report --verbose` to properly handle environment variables with continuation lines in them, and fixed the integration tests for this command to avoid false negatives. * Changed the configuration file format to accept the definition of unknown variables without declaring them local. The syntax version number remains at 2. This is to allow configuration files for newer Kyua versions to work on older Kyua versions, as there is no reason to forbid this. * Fixed stacktrace gathering with FreeBSD's ancient version of GDB. GDB 6.1.1 (circa 2004) does not have the `-ex` flag so we need to generate a temporary GDB script and feed it to GDB with `-x` instead. * Issue #136: Fixed the XML escaping in the JUnit output so that non-printable characters are properly handled when they appear in the process's stdout or stderr. * Issue #141: Improved reporting of errors triggered by sqlite3. In particular, all error messages are now tagged with their corresponding database filename and, if they are API-level errors, the name of the sqlite3 function that caused them. * Issue #144: Improved documentation on the support for custom properties in the test metadata. * Converted the `INSTALL`, `NEWS`, and `README` distribution documents to Markdown for better formatting online. ## Changes in version 0.11 **Released on October 23rd, 2014.** * Added support to print the details of all test cases (metadata and their output) to `report`. This is via a new `--verbose` flag which replaces the previous `--show-context`. * Added support to specify the amount of physical disk space required by a test case. This is in the form of a new `required_disk_space` metadata property, which can also be provided by ATF test cases as `require.diskspace`. * Assimilated the contents of all the `kyua-*-tester(1)` and `kyua-*-interface(7)` manual pages into more relevant places. In particular, added more details on test program registration and their metadata to `kyuafile(5)`, and added `kyua-test-isolation(7)` describing the isolation features of the test execution. * Assimilated the contents of all auxiliary manual pages, including `kyua-build-root(7)`, `kyua-results-files(7)`, `kyua-test-filters(7)` and `kyua-test-isolation(7)`, into the relevant command-specific manual pages. This is for easier discoverability of relevant information when reading how specific Kyua commands work. * Issue #30: Plumbed through support to query configuration variables from ATF's test case heads. This resolves the confusing situation where test cases could only do this from their body and cleanup routines. * Issue #49: Extended `report` to support test case filters as command-line arguments. Combined with `--verbose`, this allows inspecting the details of a test case failure after execution. * Issue #55: Deprecated support for specifying `test_suite` overrides on a test program basis. This idiom should not be used but support for it remains in place. * Issue #72: Added caching support to the `getcwd(3)` test in configure so that the result can be overriden for cross-compilation purposes. * Issue #83: Changed manual page headings to include a `kyua` prefix in their name. This prevents some possible confusion when displaying, for example, the `kyua-test` manual page with a plain name of `test`. * Issue #84: Started passing test-suite configuration variables to plain and TAP test programs via the environment. The name of the environment variables set this way is prefixed by `TEST_ENV_`, so a configuration variable of the form `test_suites.some_name.allow_unsafe_ops=yes` in `kyua.conf` becomes `TEST_ENV_allow_unsafe_ops=YES` in the environment. * Issues #97 and #116: Fixed the build on Illumos. * Issue #102: Set `TMPDIR` to the test case's work directory when running the test case. If the test case happens to use the `mktemp(3)` family of functions (due to misunderstandings on how Kyua works or due to the reuse of legacy test code), we don't want it to easily escape the automanaged work directory. * Issue #103: Started being more liberal in the parsing of TAP test results by treating the number in `ok` and `not ok` lines as optional. * Issue #105: Started using tmpfs instead of md as a temporary file system for tests in FreeBSD so that we do not leak `md(4)` devices. * Issue #109: Changed the privilege dropping code to start properly dropping group privileges when `unprivileged_user` is set. Also fixes `testers/run_test:fork_wait__unprivileged_group`. * Issue #110: Changed `help` to display version information and clarified the purpose of the `about` command in its documentation. * Issue #111: Fixed crash when defining a test program in a `Kyuafile` that has not yet specified the test suite name. * Issue #114: Improved the `kyuafile(5)` manual page by clarifying the restrictions of the `include()` directive and by adding abundant examples. ## Changes in version 0.10 **Experimental version released on August 14th, 2014.** * Merged `kyua-cli` and `kyua-testers` into a single `kyua` package. * Dropped the `kyua-atf-compat` package. * Issue #100: Do not try to drop privileges to `unprivileged_user` when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and `unprivileged_user` do not match. * Issue #79: Mention `kyua.conf(5)` in the *See also* section of `kyua(1)`. * Issue #75: Change the `rewrite__expected_signal__bad_arg` test in `testers/atf_result_test` to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms. ## Changes in kyua-cli version 0.9 **Experimental version released on August 8th, 2014.** Major changes: The internal architecture of Kyua to record the results of test suite runs has completely changed in this release. Kyua no longer stores all the different test suite run results as different "actions" within the single `store.db` database. Instead, Kyua now generates a separate results file inside `~/.kyua/store/` for every test suite run. Due to the complexity involved in the migration process and the little need for it, this is probably going to be the only release where the `db-migrate` command is able to convert an old `store.db` file to the new scheme. Changes in more detail: * Added the `report-junit` command to generate JUnit XML result files. The output has been verified to work within Jenkins. * Switched to results files specific to their corresponding test suite run. The unified `store.db` file is now gone: `kyua test` creates a new results file for every invocation under `~/.kyua/store/` and the `kyua report*` commands are able to locate the latest file for a corresponding test suite automatically. * The `db-migrate` command takes an old `store.db` file and generates one results file for every previously-recorded action, later deleting the `store.db` file. * The `--action` flag has been removed from all commands that accepted it. This has been superseded by the tests results files. * The `--store` flag that many commands took has been renamed to `--results-file` in line with the semantical changes. * The `db-exec` command no longer creates an empty database when none is found. This command is now intended to run only over existing files. ## Changes in kyua-testers version 0.3 **Experimental version released on August 8th, 2014.** * Made the testers set a "sanitized" value for the `HOME` environment variable where, for example, consecutive and trailing slashes have been cleared. Mac OS X has a tendency to append a trailing slash to the value of `TMPDIR`, which can cause third-party tests to fail if they compare `${HOME}` with `$(pwd)`. * Issues #85, #86, #90 and #92: Made the TAP parser more complete: mark test cases reported as `TODO` or `SKIP` as passed; handle skip plans; ignore lines that look like `ok` and `not ok` but aren't results; and handle test programs that report a pass but exit with a non-zero code. ## Changes in kyua-cli version 0.8 **Experimental version released on December 7th, 2013.** * Added support for Lutok 0.4. * Issue #24: Plug the bootstrap tests back into the test suite. Fixes in `kyua-testers` 0.2 to isolate test cases into their own sessions should allow these to run fine. * Issue #74: Changed the `kyuafile(5)` parser to automatically discover existing tester interfaces. The various `*_test_program()` functions will now exist (or not) based on tester availability, which simplifies the addition of new testers or the selective installation of them. ## Changes in kyua-testers version 0.2 **Experimental version released on December 7th, 2013.** * Issue #74: Added the `kyua-tap-tester`, a new backend to interact with test programs that comply with the Test Anything Protocol. * Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which first appeared in Automake 1.11.2. Fixes a problem in Ubuntu 10.04 LTS, which appears stuck in 1.11.1. * Issue #24: Improve test case isolation by confining the tests to their own session instead of just to their own process group. ## Changes in kyua-cli version 0.7 **Experimental version released on October 18th, 2013.** * Made failures from testers more resilent. If a tester fails, the corresponding test case will be marked as broken instead of causing kyua to exit. * Added the `--results-filter` option to the `report-html` command and set its default value to skip passed results from HTML reports. This is to keep these reports more succint and to avoid generating tons of detail files that will be, in general, useless. * Switched to use Lutok 0.3 to gain compatibility with Lua 5.2. * Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which first appeared in Automake 1.11.2. Fixes a problem in Ubuntu 10.04 LTS, which appears stuck in 1.11.1. ## Changes in kyua-cli version 0.6 **Experimental version released on February 22nd, 2013.** * Issue #36: Changed `kyua help` to not fail when the configuration file is bogus. Help should always work. * Issue #37: Simplified the `syntax()` calls in configuration and `Kyuafile` files to only specify the requested version instead of also the format name. The format name is implied by the file being loaded, so there is no use in the caller having to specify it. The version number of these file formats has been bumped to 2. * Issue #39: Added per-test-case metadata values to the HTML reports. * Issue #40: Rewrote the documentation as manual pages and removed the previous GNU Info document. * Issue #47: Started using the independent testers in the `kyua-testers` package to run the test cases. Kyua does not implement the logic to invoke test cases any more, which provides for better modularity, extensibility and robustness. * Issue #57: Added support to specify arbitrary metadata properties for test programs right from the `Kyuafile`. This is to make plain test programs more versatile, by allowing them to specify any of the requirements (allowed architectures, required files, etc.) supported by Kyua. * Reduced automatic screen line wrapping of messages to the `help` command and the output of tables by `db-exec`. Wrapping any other messages (specially anything going to stderr) was very annoying because it prevented natural copy/pasting of text. * Increased the granularity of the error codes returned by `kyua(1)` to denote different error conditions. This avoids the overload of `1` to indicate both "expected" errors from specific subcommands and unexpected errors caused by the internals of the code. The manual now correctly explain how the exit codes behave on a command basis. * Optimized the database schema to make report generation almost instantaneous. * Bumped the database schema to 2. The database now records the metadata of both test programs and test cases generically, without knowledge of their interface. * Added the `db-migrate` command to provide a mechanism to upgrade a database with an old schema to the current schema. * Removed the GDB build-time configuration variable. This is now part of the `kyua-testers` package. * Issue #31: Rewrote the `Kyuafile` parsing code in C++, which results in a much simpler implementation. As a side-effect, this gets rid of the external Lua files required by `kyua`, which in turn make the tool self-contained. * Added caching of various configure test results (particularly in those tests that need to execute a test program) so that cross-compilers can predefine the results of the tests without having to run the executables. ## Changes in kyua-testers version 0.1 **Experimental version released on February 19th, 2013.** This is the first public release of the `kyua-testers` package. The goal of this first release is to adopt all the test case execution code of `kyua-cli` 0.5 and ship it as a collection of independent tester binaries. The `kyua-cli` package will rely on these binaries to run the tests, which provides better modularity and simplicity to the architecture of Kyua. The code in this package is all C as opposed to the current C++ codebase of `kyua-cli`, which means that the overall build times of Kyua are now reduced. ## Changes in kyua-cli version 0.5 **Experimental version released on July 10th, 2012.** * Issue #15: Added automatic stacktrace gathering of crashing test cases. This relies on GDB and is a best-effort operation. * Issue #32: Added the `--build-root` option to the debug, list and test commands. This allows executing test programs from a different directory than where the `Kyuafile` scripts live. See the *Build roots* section in the manual for more details. * Issue #33: Removed the `kyuaify.sh` script. This has been renamed to atf2kyua and moved to the `kyua-atf-compat` module, where it ships as a first-class utility (with a manual page and tests). * Issue #34: Changed the HTML reports to include the stdout and stderr of every test case. * Fixed the build when using a "build directory" and a clean source tree from the repository. ## Changes in kyua-cli version 0.4 **Experimental version released on June 6th, 2012.** * Added the `report-html` command to generate HTML reports of the execution of any recorded action. * Changed the `--output` flag of the `report` command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a `--with-atf` flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped `kyua` subcommands by topic both in the output of `help` and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made `help` print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level `test_suites` tree must be declared as strings. Similarly, the `-v` and `--variable` flags to the command line must now carry a `test_suites.` prefix when referencing any variables under such tree. ## Changes in kyua-cli version 0.3 **Experimental version released on February 24th, 2012.** * Made the `test` command record the results of the executed test cases into a SQLite database. As a side effect, `test` now supports a `--store` option to indicate where the database lives. * Added the `report` command to generate plain-text reports of the test results stored in the database. The interface of this command is certainly subject to change at this point. * Added the `db-exec` command to directly interact with the store database. * Issue #28: Added support for the `require.memory` test case property introduced in ATF 0.15. * Renamed the user-specific configuration file from `~/.kyuarc` to `~/.kyua/kyua.conf` for consistency with other files stored in the `~/.kyua/` subdirectory. * Switched to use Lutok instead of our own wrappers over the Lua C library. Lutok is just what used to be our own utils::lua module, but is now distributed separately. * Removed the `Atffile`s from the source tree. Kyua is stable enough to generate trustworthy reports, and we do not want to give the impression that atf-run / atf-report are still supported. * Enabled logging to stderr for our own test programs. This makes it slightly easier to debug problems in our own code when we get a failing test. ## Changes in kyua-cli version 0.2 **Experimental version released on August 24th, 2011.** The biggest change in this release is the ability for Kyua to run test programs implemented using different frameworks. What this means is that, now, a Kyua test suite can include not only ATF-based test programs, but also "legacy" (aka plain) test programs that do not use any framework. I.e. if you have tests that are simple programs that exit with 0 on success and 1 on failure, you can plug them in into a Kyua test suite. Other than this, there have been several user-visible changes. The most important are the addition of the new `config` and `debug` subcommands to the `kyua` binary. The former can be used to inspect the runtime configuration of Kyua after parsing, and the latter is useful to interact with failing tests cases in order to get more data about the failure itself. Without further ado, here comes the itemized list of changes: * Generalized the run-time engine to support executing test programs that implement different interfaces. Test programs that use the ATF libraries are just a special case of this. (Issue #18.) * Added support to the engine to run `plain` test programs: i.e. test programs that do not use any framework and report their pass/fail status as an exit code. This is to simplify the integration of legacy test programs into a test suite, and also to demonstrate that the run-time engine is generic enough to support different test interfaces. (Issue #18.) * Added the `debug` subcommand. This command allows end users to tweak the execution of a specific test case and to poke into the behavior of its execution. At the moment, all this command allows is to view the stdout and stderr of the command in real time (which the `test` command currently completely hides). * Added the `config` subcommand. This command allows the end user to inspect the current configuration variables after evaluation, without having to read through configuration files. (Issue #11.) * Removed the `test_suites_var` function from configuration files. This was used to set the value of test-suite-sepecific variables, but it was ugly-looking. It is now possible to use the more natural syntax `test_suites.<test-suite-name>.<variable> = <value>`. (Issue #11.) * Added a mechanism to disable the loading of configuration files altogether. Needed for testing purposes and for scriptability. Available by passing the `--config=none` flag. * Enabled detection of unused parameters and variables in the code and fixed all warnings. (Issue #23.) * Changed the behavior of "developer mode". Compiler warnings are now enabled unconditionally regardless of whether we are in developer mode or not; developer mode is now only used to perform strict warning checks and to enable assertions. Additionally, developer mode is now only automatically enabled when building from the repository, not for formal releases. (Issue #22.) * Fixed many build and portability problems to Debian sid with GCC 4.6.3 and Ubuntu 10.04.1 LTS. (Issues #20, #21, #26.) ## Changes in kyua-cli version 0.1 **Experimental version released on June 23rd, 2011.** This is the first public release of the `kyua-cli` package. The scope of this release is to provide functional replacement for the `atf-run` utility included in the atf package. At this point, `kyua` can reliably run the NetBSD 5.99.53 test suite delivering the same results as `atf-run`. The reporting facilities of this release are quite limited. There is no replacement for `atf-report` yet, and there is no easy way of debugging failing test programs other than running them by hand. These features will mark future milestones and therefore be part of other releases. Be aware that this release has suffered very limited field testing. The test suite for `kyua-cli` is quite comprehensive, but some bugs may be left in any place.
## Release 0.5.1 (9-Nov-2024) * properly require "setuptools" for install (#47, jameshilliard) ## Release 0.5.0 (7-Nov-2024) * correctly close a mailbox which still has a nameplate (#28) * remove python2 support * test on python 3.8, 3.9, 3.10, 3.11 and 3.12 series * drop "six" (#35) * upgrade "versioneer"
2.0.0 (2025-04-24) What's Changed * Alternative ZFRS to improve memory allocation by @whomwah in #28 * Upgrade StandardRB dependencies by @whomwah in #30 * Update rubocop by @whomwah in #31 * Fix 'do your own rendering' example. by @jamesneal in #32 * Dependency upgrades by @whomwah in #33 * Add Ruby 3.2 to CI by @whomwah in #34 * chore: Updating dependencies by @whomwah in #40 * chore: add workflow_dispatch: to workflow by @whomwah in #41 * Feat/fixes april 2025 by @whomwah in #44 * Releases/v2.0.0 by @whomwah in #45 New Contributors * @jamesneal made their first contribution in #32
What's Changed - Add NetBSD by @0323pin in #27 - merge more config file settings into config by @aikomastboom in #28 - Merge entries within the 'commands' config by @warpfork in #29 - chore: update deps and msrv by @chenrui333 in #31 - feat: add dependabot by @chenrui333 in #32 - chore: update action deps and replace deprecated actions-rs/toolchain with actions-rust-lang/setup-rust-toolchain by @chenrui333 in #33
No description provided.