linux/poky.git/bitbake, branch 5.1_M1Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=5.1_M12024-06-04T11:05:20+00:00bitbake: asyncrpc: Use client timeout for websocket open timeout2024-06-04T11:05:20+00:00Joshua WattJPEWhacker@gmail.com2024-06-03T16:44:03+00:00urn:sha1:c88bee1a5e336cc589eb7d7e5f31db43e8836611
The default connection timeout for websockets is 10 seconds, so use the
provided client timeout instead (which defaults to 30 seconds).
(Bitbake rev: 23681775e5941e54ebead469addf708fca1e6beb)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: tests/fetch: Tweak to work on Fedora402024-05-31T15:56:25+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-31T11:38:49+00:00urn:sha1:f24ffc087b4edd3915bc6a5da61d35845499f36d
On Fedora40, "localhost" sometimes resolves to ::1 and sometimes to 127.0.0.1
and python only binds to one of the addresses, leading to test failures.
Use 127.0.0.1 explicitly to avoid problems of the name resolution, we're trying
to test things other than the host networking.
(Bitbake rev: 9adc6da42618f41bf0d6b558d62b2f3c13bedd61)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: fetch2/wget: Fix failure path for files that are empty or don't exist2024-05-31T15:56:25+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-30T16:55:49+00:00urn:sha1:f81127b6195dd94280389c3dd4a82abdad85faa8
When we intercepted the file download to a temp file, we broke the
exist/size checks which need to happen before the rename. Correct
the ordering.
For some reason, python 3.12 exposes this problem in the selftests
differently to previous versions.
(Bitbake rev: c56bd9a9280378bc64c6a7fe6d7b70847e0b9e6d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: hashserv: client: Fix changing stream modes2024-05-31T15:56:25+00:00Joshua WattJPEWhacker@gmail.com2024-05-30T15:42:30+00:00urn:sha1:c2d2ae7b1d16c30ca9333a61a2765bdf59dddcba
When switching from normal mode to stream mode, skip calling
self._set_mode() again because this will cause a recursion into the
_set_mode() function and causes problems.
Also cleanup some of the error checking during this process
This bug affected when a client would attempt to switch from one stream
mode to another, and meant that the server would get an invalid message
from the client. This would cause the server to disconnect the client,
and the client would then reconnect in normal mode which was the mode it
wanted anyway and thus it would carry on without any errors. This made
the bug not visible on the client side, but resulting in a lot of
backtrace JSON decoding exceptions in the server logs.
(Bitbake rev: 1826bc41ab3369ac40034c5eaf698748b769b881)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: siggen: Batch unihash_exists checks2024-05-31T15:56:25+00:00Joshua WattJPEWhacker@gmail.com2024-05-30T15:41:27+00:00urn:sha1:5a308474c21a44e22a3cc8e23a9a41269cb51266
Similar to looking up unihashes, use the batch API when checking if a
unihash exists to speed up lookups
(Bitbake rev: 0ac521ff37b578f7487bca0eccc7dc9e5974991b)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: asyncrpc: Remove ClientPool2024-05-31T15:56:25+00:00Joshua WattJPEWhacker@gmail.com2024-05-30T15:41:26+00:00urn:sha1:247d08ae0765fdd73f80e7608f76e36983e2109d
Batching support on the client side has proven to be a much more
effective way of dealing with server latency than multiple client
connections and is also much nicer on the server, so drop the client
pool support from asyncrpc and the hash server
(Bitbake rev: 6f80560f1c7010d09fe5448fdde616aef8468102)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: siggen: Drop client pool support2024-05-31T15:56:25+00:00Joshua WattJPEWhacker@gmail.com2024-05-30T15:41:25+00:00urn:sha1:f618d1dfd7dd414cb458467d0e35b135d6e7cd32
Drops support for client pools, since batching support in the client
code has proven to be much more effective
(Bitbake rev: 85dafaf8e070459f7de7bfb37300d8b60a27002e)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake: Drop older python version compatibility code2024-05-31T15:56:25+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-30T09:37:45+00:00urn:sha1:2ff7af74bc84c2132af00c0fda78ef00c4e5fcbc
cooker: We can call multiprocessing close() unconditionally and tweak a
comment give 3.8 is now the minimum version.
lib/bb: We can drop the logger addition code only needed before 3.6
asyncrpc/hashserv: Since the minimum version is 3.8, we can drop the
conditional code.
(Bitbake rev: 16f4386400f88ba50605307961c248bef09895c1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: cooker: Improve handling errors during parsing when profiling2024-05-31T15:56:25+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-30T09:35:24+00:00urn:sha1:277e07d1cc83abf66c9088e4a5d9594b2603492d
We've seeing profiling tracebacks when parse errors occur during
profiling. Try and avoid these but not processing invalid profiles.
(Bitbake rev: 171bd9dd575307fbd61b5179ad86131d76add067)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: lib/bs4: Avoid soupsieve warning2024-05-31T12:09:54+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-31T12:09:44+00:00urn:sha1:eacebfc1696a5690753ee28cf17f3380c316749a
(Bitbake rev: 8e444cd9913d1ee0672b5583e263e5927c3221df)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>