Merge v2 into main branch

y
Tim @.***> schrieb am Sa., 12. Okt. 2024, 13:54:

You can view, comment on, or merge this pull request online at:
https://github.com/TimMcCool/scratchattach/pull/250
Commit Summary

cd79939
https://github.com/TimMcCool/scratchattach/pull/250/commits/cd7993959859b026f32fb9d285332afb2c736239
.
8be78d6
https://github.com/TimMcCool/scratchattach/pull/250/commits/8be78d602d7c74786f425e2521099f4caaf8bd5f
.
d01de5d
https://github.com/TimMcCool/scratchattach/pull/250/commits/d01de5d364bd1e07f120448e0d3988a36eae9bf2
.
bcd0d2b
https://github.com/TimMcCool/scratchattach/pull/250/commits/bcd0d2bf37030b186d7a8d8a10d53db098ea4975
.
632fde0
https://github.com/TimMcCool/scratchattach/pull/250/commits/632fde0abae41ca3319f46b8620d80bf538c5aef
.
d21e3ed
https://github.com/TimMcCool/scratchattach/pull/250/commits/d21e3eda1bcd710ea1aded2ce22cd8d7207d24e4
.
f98e5d4
https://github.com/TimMcCool/scratchattach/pull/250/commits/f98e5d40d81701e8bdb3fb11f12b5790b701cd3b
.
fc4da0e
https://github.com/TimMcCool/scratchattach/pull/250/commits/fc4da0e73d4fb253bb696a48186daf6faa01cc12
added date_limit field to iterative fetchers
60d65d7
https://github.com/TimMcCool/scratchattach/pull/250/commits/60d65d7a756128e666a5e7cdc0fd84f3eea5e4d6
added various API endpoints
b601b8b
https://github.com/TimMcCool/scratchattach/pull/250/commits/b601b8b088da09b9281dd94140517a36a96de179
.
c9e37f1
https://github.com/TimMcCool/scratchattach/pull/250/commits/c9e37f16b34c313f8eff5c32b575a98a86bc480d
.
e30cae3
https://github.com/TimMcCool/scratchattach/pull/250/commits/e30cae39cc2b053d1f67e4176a694101de0e4f37
.
33d96c0
https://github.com/TimMcCool/scratchattach/pull/250/commits/33d96c00222e3a7f9b3bd15866a98427939ded1f
.
b7a1c8a
https://github.com/TimMcCool/scratchattach/pull/250/commits/b7a1c8aade4e87252de42abb77ae96f74b8a08f8
.
fba896f
https://github.com/TimMcCool/scratchattach/pull/250/commits/fba896fa21b2115c44c5d4157f06bc7a70e5e414
.
11dd8c2
https://github.com/TimMcCool/scratchattach/pull/250/commits/11dd8c20e0ece53ccedd8653fe509288e41fe0c1
.
cf29a1c
https://github.com/TimMcCool/scratchattach/pull/250/commits/cf29a1c9e374b40d816c00b4c350a3964815bfd9
.
c00e67f
https://github.com/TimMcCool/scratchattach/pull/250/commits/c00e67f626ff7d361d097d8012414754ca41b7ac
.
cd40176
https://github.com/TimMcCool/scratchattach/pull/250/commits/cd40176adb10cbcc1fedb365507aaafd3cf78cc6
.
ecba49d
https://github.com/TimMcCool/scratchattach/pull/250/commits/ecba49d40936ceaa32e9aea50ef257a45589845e
added filterbot
3833435
https://github.com/TimMcCool/scratchattach/pull/250/commits/38334356dd9cdf55d61907d4042c5ee9e35d10c3
.
3770234
https://github.com/TimMcCool/scratchattach/pull/250/commits/377023431b183170d6108c48567c998ab25184b3
filterbot finished
df71d47
https://github.com/TimMcCool/scratchattach/pull/250/commits/df71d47e074f2d4f0ef0810a49831bb0f778ea4d
implemented centralized request handler
07bb496
https://github.com/TimMcCool/scratchattach/pull/250/commits/07bb49674ce0ed1808ce59cac1a2ba6c9e65c733
.
4f1c9a0
https://github.com/TimMcCool/scratchattach/pull/250/commits/4f1c9a0e5b341b8c13f254c18f9e3e53533da2b0
fixed circular imports
314292e
https://github.com/TimMcCool/scratchattach/pull/250/commits/314292e5e6273205901a92ef9ecbad074897c0e7
.
4bd90b1
https://github.com/TimMcCool/scratchattach/pull/250/commits/4bd90b1939a61672f99c4c59bd0fc42bba5d9822
.
9373c83
https://github.com/TimMcCool/scratchattach/pull/250/commits/9373c83ef64e1e347691e41e7d08c70a08e0c5f5
added proxy support
5ff715c
https://github.com/TimMcCool/scratchattach/pull/250/commits/5ff715c0801597ddc4e3137acf5342d054f4697c
.
382e9d3
https://github.com/TimMcCool/scratchattach/pull/250/commits/382e9d39b51b84aed1882a6a11c5522e930543bd
started implementing new cloud classes
caf7480
https://github.com/TimMcCool/scratchattach/pull/250/commits/caf74801bbdfb718ea150770242752bf889f5c8e
added get_cloud and connect_cloud
7eb60e8
https://github.com/TimMcCool/scratchattach/pull/250/commits/7eb60e82d7efdcdefb85772075b88a4444328ebb
fixed import error
372f9f9
https://github.com/TimMcCool/scratchattach/pull/250/commits/372f9f97d606c9426f022045a1d018662ac59179
fixed more import errors
bf9f9ff
https://github.com/TimMcCool/scratchattach/pull/250/commits/bf9f9ffa9d4a74edf789d9d8e0dce7306e02be93
fixed some bugs
51625ce
https://github.com/TimMcCool/scratchattach/pull/250/commits/51625ce94b39862f624b28bcc4fbb297a5cb6d76
.2
d90107e
https://github.com/TimMcCool/scratchattach/pull/250/commits/d90107e1425215741863b18046c9fe285a244ae6
.
f768bce
https://github.com/TimMcCool/scratchattach/pull/250/commits/f768bce5b7f20e01cf4b579c3db057c80e381334
.
62dbe42
https://github.com/TimMcCool/scratchattach/pull/250/commits/62dbe421f80739be35173d8368f9505fb13fd7ea
fixed circular import
3eab664
https://github.com/TimMcCool/scratchattach/pull/250/commits/3eab66419c2ad389140b980678b356d9d883a0f6
.
f61a82d
https://github.com/TimMcCool/scratchattach/pull/250/commits/f61a82d66bef80056f2072a053b16d75dc84d3e6
finished reworking cloud events
d751f50
https://github.com/TimMcCool/scratchattach/pull/250/commits/d751f50f838084788fbc5c839307318994eba012
bug fixes
c18ccd6
https://github.com/TimMcCool/scratchattach/pull/250/commits/c18ccd6a5d187433a0d333a82b217993e360850f
fixed circular import
fb31f61
https://github.com/TimMcCool/scratchattach/pull/250/commits/fb31f619d0317cb83e735afef278144d978a8fbb
fix
553187e
https://github.com/TimMcCool/scratchattach/pull/250/commits/553187eafb96c495b70dd232e2477f3d37636e5f
fixed circular import
62581d9
https://github.com/TimMcCool/scratchattach/pull/250/commits/62581d9180770b3cfe0797b97cae592e8d78d846
.
3778490
https://github.com/TimMcCool/scratchattach/pull/250/commits/3778490fa9550cb424601329f6f49e85b255b16a
.
d5d9d56
https://github.com/TimMcCool/scratchattach/pull/250/commits/d5d9d56d39d9aaa3cb5ba2eae76e58bd81d6df21
fixes
405bc4d
https://github.com/TimMcCool/scratchattach/pull/250/commits/405bc4d3a4be921bcd7bfc3c697650a4355e7215
deleted old cloud code
85d558d
https://github.com/TimMcCool/scratchattach/pull/250/commits/85d558d4961d76518c510bfebe9447b05e229dc5
.
18ef5a7
https://github.com/TimMcCool/scratchattach/pull/250/commits/18ef5a75de52e46190182a7af38974b3c14139db
different fixes
42fb615
https://github.com/TimMcCool/scratchattach/pull/250/commits/42fb61556202a41c7af71d29f463b900886fb5fb
enforced naming conventions
fe37001
https://github.com/TimMcCool/scratchattach/pull/250/commits/fe37001cae18177345148e7b145095a550adb403
added more linking functions
05a9677
https://github.com/TimMcCool/scratchattach/pull/250/commits/05a96776a29ff6537680991911f8ff8de56927ac
fix
3e242ec
https://github.com/TimMcCool/scratchattach/pull/250/commits/3e242ecf54b15fabc21159421ab0fbf68572ef23
.
f88863c
https://github.com/TimMcCool/scratchattach/pull/250/commits/f88863c72274592c4d23a7b7d52156cce3278935
.
a0c7d5f
https://github.com/TimMcCool/scratchattach/pull/250/commits/a0c7d5f8eed79708268df7a36420b6edbb8396bd
.
647fa39
https://github.com/TimMcCool/scratchattach/pull/250/commits/647fa3935e5c9bcd7f60ffa9e4f692d518427604
.
6357c12
https://github.com/TimMcCool/scratchattach/pull/250/commits/6357c122553cd6e51beecc2e1ec075ce92679cd0
.
d4cf858
https://github.com/TimMcCool/scratchattach/pull/250/commits/d4cf858c9c71cddc3de8b3fbe27186432cd90d9d
.
a977bdc
https://github.com/TimMcCool/scratchattach/pull/250/commits/a977bdc95ebf3f36b5ca0cbc61462a7d3a52c226
bug fix
7cc16b8
https://github.com/TimMcCool/scratchattach/pull/250/commits/7cc16b8240b376a682dc956bac085631744a796b
.
7abba2d
https://github.com/TimMcCool/scratchattach/pull/250/commits/7abba2dfa01a46d1c1ea87452d42f7d6aff6b06f
,
863b86c
https://github.com/TimMcCool/scratchattach/pull/250/commits/863b86ccbdbd608b86018d8949f1729e846610b8
.
7b6308e
https://github.com/TimMcCool/scratchattach/pull/250/commits/7b6308e1be1e5d5e3ae7b6e3fca8efc2670b0928
added option to self-host cloud server
84bcb00
https://github.com/TimMcCool/scratchattach/pull/250/commits/84bcb0010acf30566aed3f24945bca058f30ce92
.
ec62fa5
https://github.com/TimMcCool/scratchattach/pull/250/commits/ec62fa53a967ae004a17368235ccc50b5b89a997
.
08c4cc1
https://github.com/TimMcCool/scratchattach/pull/250/commits/08c4cc1a2df92aaf480d97077f5dd8efb9f990e6
added cloud.set_vars (for setting multiple cloud variables simultaneously)
e8c79e8
https://github.com/TimMcCool/scratchattach/pull/250/commits/e8c79e8e16243b97f5a1058ac2906e5d2300996b
.
4442086
https://github.com/TimMcCool/scratchattach/pull/250/commits/4442086401b075fe7ed58f378c6f2eff2f096bfd
.
f993824
https://github.com/TimMcCool/scratchattach/pull/250/commits/f993824f129187fc005037aedef23bdcbf5304d7
removed a possible freezing problem
7db78a0
https://github.com/TimMcCool/scratchattach/pull/250/commits/7db78a0e884107d586f11453caac1eb5f0965203
fix
be0afe6
https://github.com/TimMcCool/scratchattach/pull/250/commits/be0afe6a678b1a83a0b69a9279a6a3a093cc1634
.
ece6bee
https://github.com/TimMcCool/scratchattach/pull/250/commits/ece6bee65e90d2727d5b8eecc671f3232e157df5
.
8d4e487
https://github.com/TimMcCool/scratchattach/pull/250/commits/8d4e487d96c7d05e5b1537b012179473f661206a
fixed bug in Comment.reply()
244309e
https://github.com/TimMcCool/scratchattach/pull/250/commits/244309e918a732d91b47ae627744ae66133e2bad
.
64baef7
https://github.com/TimMcCool/scratchattach/pull/250/commits/64baef7d6d76af61ef1cc8eaac0bb9b34b1c069e
bug
f34c4e9
https://github.com/TimMcCool/scratchattach/pull/250/commits/f34c4e98c09799a3fe5d567c9b8183c511a10882
.
da32271
https://github.com/TimMcCool/scratchattach/pull/250/commits/da322714248fd0dddc2ec07205a999f6ee2b5025
.
0141c86
https://github.com/TimMcCool/scratchattach/pull/250/commits/0141c86663af2053de9fc03b3b1fcde694bfa1a1
.
978e9f3
https://github.com/TimMcCool/scratchattach/pull/250/commits/978e9f3677094b20f8917f843a83b3aba51d7504
fixed small bug
802670f
https://github.com/TimMcCool/scratchattach/pull/250/commits/802670f4858ab3e4f0c9c0890f1cc4e43e1034b4
removed dead scratchdb functions
293064f
https://github.com/TimMcCool/scratchattach/pull/250/commits/293064fce1b1002d731c04e65dfbbed72f6d7abe
removed never-to-come user.forum_posts() function
50ed901
https://github.com/TimMcCool/scratchattach/pull/250/commits/50ed901d65dd2efea33acf996a32cda51bc3b3ff
removed useless raw arg
548d68d
https://github.com/TimMcCool/scratchattach/pull/250/commits/548d68d7dd30704b8cbc06456062431a486c6768
fixed wording in docstring
492769b
https://github.com/TimMcCool/scratchattach/pull/250/commits/492769b5f5b15763bb4ef9024185f1f4eda0a660
.
b60cfb4
https://github.com/TimMcCool/scratchattach/pull/250/commits/b60cfb43a584487b6b908c758b1642b92e8c94e7
.
06c313f
https://github.com/TimMcCool/scratchattach/pull/250/commits/06c313fc7f13eb5e901fd243c0fb180d0986dca9
.
48fd6d1
https://github.com/TimMcCool/scratchattach/pull/250/commits/48fd6d1ab271c939b8f365fb1cdba435264edc66
.
1c3a6e7
https://github.com/TimMcCool/scratchattach/pull/250/commits/1c3a6e7f9b135785a33f1fb13b8bb351e7382ec6
.
9dd2985
https://github.com/TimMcCool/scratchattach/pull/250/commits/9dd2985028b59582d256b02ff5c56d0c5dd09130
fixed potential ssl issue
35ea753
https://github.com/TimMcCool/scratchattach/pull/250/commits/35ea753ea03aadc85fee6489c21871db2ef5639f
fixed all bugs in project.py and some bugy in comment.py
2e19236
https://github.com/TimMcCool/scratchattach/pull/250/commits/2e192368f9ae26417a8c43e02c497aeed891ef32
fixed bug in Comment.reply()
dfee75b
https://github.com/TimMcCool/scratchattach/pull/250/commits/dfee75b4b04275d10faffa6a67d15840827f5639
.
61705bb
https://github.com/TimMcCool/scratchattach/pull/250/commits/61705bba4f3fbd10c0cbe650617a15aad5b265a5
fixed bug in User.post_comment
4952b5b
https://github.com/TimMcCool/scratchattach/pull/250/commits/4952b5b1586ba229ac3fa227059f776c1aef8da7
.
64cba96
https://github.com/TimMcCool/scratchattach/pull/250/commits/64cba9638e87d5484d49c88204dc3f7344cc4db7
.
58a8847
https://github.com/TimMcCool/scratchattach/pull/250/commits/58a884764b78450b02e3621cb986b9c742cead64
.
8e50cc9
https://github.com/TimMcCool/scratchattach/pull/250/commits/8e50cc987b7db80278b0bfaa5237e607922886d7
.
a496e45
https://github.com/TimMcCool/scratchattach/pull/250/commits/a496e450cbe67a62abbee29f85a7b74811cb2d33
fixed bug in topic.posts()
0b00af6
https://github.com/TimMcCool/scratchattach/pull/250/commits/0b00af6b1c7e7dca36aa9994b3314dc5adaf2b9e
.
fe64e79
https://github.com/TimMcCool/scratchattach/pull/250/commits/fe64e790836e8dfe12b135a3e576688e8cd8e827
fixed another bug (wrong comment source)
6a75882
https://github.com/TimMcCool/scratchattach/pull/250/commits/6a758824e17cf1dfaed101c74e870f39869b040c
.
344bf52
https://github.com/TimMcCool/scratchattach/pull/250/commits/344bf52b93c66553387c64abcd9395b5922615e5
fixed
9c042ed
https://github.com/TimMcCool/scratchattach/pull/250/commits/9c042ed3f22470f155bc0b0a01be76ad6d62c309
.
2ebc58b
https://github.com/TimMcCool/scratchattach/pull/250/commits/2ebc58b6bcc913c2db3179f737427e02886b79ac
.
c8b7d8f
https://github.com/TimMcCool/scratchattach/pull/250/commits/c8b7d8f39132514b7e615dfb5ae5e6b90653a861
fixed filterbot
f40a4ed
https://github.com/TimMcCool/scratchattach/pull/250/commits/f40a4eddce11e6e6d82370341fd5070f82246d50
Add files via upload
605971a
https://github.com/TimMcCool/scratchattach/pull/250/commits/605971a96e9442bb95c9f6f7a801f52833e8faac
Add files via upload
d1e1dfa
https://github.com/TimMcCool/scratchattach/pull/250/commits/d1e1dfac2ac86e33a89bd75262e7a1854491d051
new logos added
d924c16
https://github.com/TimMcCool/scratchattach/pull/250/commits/d924c16129c1525e4dd9e22e16c5f200aa82f97b
Merge branch 'v2' of https://github.com/TimMcCool/scratchattach into v2
11cc1f8
https://github.com/TimMcCool/scratchattach/pull/250/commits/11cc1f89a265f27d28770364b96412f646029fea
Delete logos/scratchattachlogo.svg
96c400f
https://github.com/TimMcCool/scratchattach/pull/250/commits/96c400fbd37c90c1bfc3bfd950e077d17d084372
Update README.md
6a7eb4b
https://github.com/TimMcCool/scratchattach/pull/250/commits/6a7eb4b2b986d16fa68559aa622ca6342e304d28
Update README.md
4d7427d
https://github.com/TimMcCool/scratchattach/pull/250/commits/4d7427d4029250b0f6ade46f11dcf3c3dd3f67f1
.
d710547
https://github.com/TimMcCool/scratchattach/pull/250/commits/d710547bbedb45c7163b7cb9317f38b4324d2066
Completed tw cloud server feature
2f398f0
https://github.com/TimMcCool/scratchattach/pull/250/commits/2f398f0f3c76e558e9160ff408aa75123d55c234
bug fix
8953bb2
https://github.com/TimMcCool/scratchattach/pull/250/commits/8953bb2176f44d3b4a4b49e0ecacb039ff3ed029
another bug fix
9a13733
https://github.com/TimMcCool/scratchattach/pull/250/commits/9a137332e5cba253af5b78a50e0addaa7e867f70
added "server agent"
d784a04
https://github.com/TimMcCool/scratchattach/pull/250/commits/d784a0479e04f3810a792d266c8fbf096bd96a79
var names specified without ☁ in cloudserver
7f60ce5
https://github.com/TimMcCool/scratchattach/pull/250/commits/7f60ce5e8a2598c90ca40163c057fcfa9d467dee
.
9d41035
https://github.com/TimMcCool/scratchattach/pull/250/commits/9d41035f5c21833f639a77c43c0c5b3a59c7cbaf
made it so server-side sets are actually sent
c9888b8
https://github.com/TimMcCool/scratchattach/pull/250/commits/c9888b86a0a1ad4254877860d443fe918af87b67
finished cloud server tool
e1bdad8
https://github.com/TimMcCool/scratchattach/pull/250/commits/e1bdad841b198ff7fb1098c8d9163a9cb3626baf
.
b3c4393
https://github.com/TimMcCool/scratchattach/pull/250/commits/b3c4393ac5e72be01e2f45f45023e3c65eab495d
.
34d0a01
https://github.com/TimMcCool/scratchattach/pull/250/commits/34d0a01c1d828c816f690e4673d87fe23ef4c526
.
db14a69
https://github.com/TimMcCool/scratchattach/pull/250/commits/db14a691bad5a798c2d3669a8a521ae1bff1d5e6
.
102c5ef
https://github.com/TimMcCool/scratchattach/pull/250/commits/102c5efb50b659de03f2ea13c0ebe121e66ea14f
bug
0a836c8
https://github.com/TimMcCool/scratchattach/pull/250/commits/0a836c8253421c23e5c4493dd3dea3f9659b24fd
bug fix
fae41fd
https://github.com/TimMcCool/scratchattach/pull/250/commits/fae41fd3b1060dddd9e9deeecf2f35b9678c960e
.
43f7b86
https://github.com/TimMcCool/scratchattach/pull/250/commits/43f7b8686e95d5490985c4b537ce07f3420fa84f
.
7d3e147
https://github.com/TimMcCool/scratchattach/pull/250/commits/7d3e147e7b7058ed8efeb3b50dca5de785675087
.
aa681fc
https://github.com/TimMcCool/scratchattach/pull/250/commits/aa681fcc0f9f73ac54428b49e4242d201ce9b370
bug fix
ce1b59a
https://github.com/TimMcCool/scratchattach/pull/250/commits/ce1b59af1fd0264a670de148021f65f4d96399b8
bug fix
7c31cda
https://github.com/TimMcCool/scratchattach/pull/250/commits/7c31cdac48c04a785561771cafb7dc68a34d27c0
bug fix
f050bd9
https://github.com/TimMcCool/scratchattach/pull/250/commits/f050bd933cae3fd404b13df2213b43e266c86df5
bug fix
4e9238b
https://github.com/TimMcCool/scratchattach/pull/250/commits/4e9238be67f1e4e3e3be8b86dca6e7375f325cc5
.
d441fb6
https://github.com/TimMcCool/scratchattach/pull/250/commits/d441fb670e279eea7b6f59601ab67506b89ab350
added error code
fc58da8
https://github.com/TimMcCool/scratchattach/pull/250/commits/fc58da8ab4e83e1ee5e3c0560b06b3a299999073
.
d3de1fd
https://github.com/TimMcCool/scratchattach/pull/250/commits/d3de1fd0134e0cb37af3236c7fdf103c8ce9dd84
improvement
12bd090
https://github.com/TimMcCool/scratchattach/pull/250/commits/12bd09029754f39d2dc14a07c88ec731db6583b3
.
02c2267
https://github.com/TimMcCool/scratchattach/pull/250/commits/02c2267be021b38ce7746fe6987096aedcdfdf5b
.
d800ed2
https://github.com/TimMcCool/scratchattach/pull/250/commits/d800ed270f797e0a34f75488c86b28909d251225
.
5ee1e5d
https://github.com/TimMcCool/scratchattach/pull/250/commits/5ee1e5d24b21df4c692947b8dc3773b4914d64d6
added User.verify_identity
9c483fe
https://github.com/TimMcCool/scratchattach/pull/250/commits/9c483fe5e15f41aa8b019d6bf9f16075cbeeeaa6
.
eff1f08
https://github.com/TimMcCool/scratchattach/pull/250/commits/eff1f0858f744c7ced6e34d49ae31484395900a7
fix
7d38c5f
https://github.com/TimMcCool/scratchattach/pull/250/commits/7d38c5f0fa36aaa73c16d286c8e916d283e6e32c
.
c690c35
https://github.com/TimMcCool/scratchattach/pull/250/commits/c690c35e2b0ed9322e1dc38bb13e7b1a6d23eeea
.
2bd5aa6
https://github.com/TimMcCool/scratchattach/pull/250/commits/2bd5aa6cf4e69a1db400bb58769ba8e4a128d748
.
25fde71
https://github.com/TimMcCool/scratchattach/pull/250/commits/25fde718bb37ffd5b9115587396dff0bcf6feff3
added project json capabilites (unfinished beta)
90a87f9
https://github.com/TimMcCool/scratchattach/pull/250/commits/90a87f95592c9742f53aa4ab49c433e8c1c4e9e8
.
308fa21
https://github.com/TimMcCool/scratchattach/pull/250/commits/308fa21cf4598d14ddd7a92935a238b6fb00f396
.
0659d80
https://github.com/TimMcCool/scratchattach/pull/250/commits/0659d80b2e084f89a0162dc273f9919ccfb7305d
fixed a typo
05114b3
https://github.com/TimMcCool/scratchattach/pull/250/commits/05114b3eadd35cd03e649ec8377fa54296159c7b
.
dc54c45
https://github.com/TimMcCool/scratchattach/pull/250/commits/dc54c458b3695787ab8320deda5d334a04a64933
.
e0b2366
https://github.com/TimMcCool/scratchattach/pull/250/commits/e0b2366b70ff345afec44e6c4d1936da1e2c391f
bug fix
804a473
https://github.com/TimMcCool/scratchattach/pull/250/commits/804a47361740987e3601247eb6163ba0533d51bf
.
9144b3a
https://github.com/TimMcCool/scratchattach/pull/250/commits/9144b3a1c7327fb28df0a0325036bf19106a9812
fixed loading blocks from project json
8b18a58
https://github.com/TimMcCool/scratchattach/pull/250/commits/8b18a585c5752ffe2c629fcb963da09778a506e4
fixed "customes" typo
79b046b
https://github.com/TimMcCool/scratchattach/pull/250/commits/79b046b5a13d7e4edd53477d3ba685d2843a3076
fixed sprite keywords that dont exist in bg sprite
1a62945
https://github.com/TimMcCool/scratchattach/pull/250/commits/1a62945c0bb31b1edbc5ae179a1e1ed70ab37764
fixed incorrect index at monitor read-in
5bdc6f8
https://github.com/TimMcCool/scratchattach/pull/250/commits/5bdc6f84b0fd06d6e671005bc0be953065ed66f3
.
6276f7b
https://github.com/TimMcCool/scratchattach/pull/250/commits/6276f7b057201c82279ab45b96cd8740b75c64ef
fixed a bug with non-existent atttribute of monitor class
2df4056
https://github.com/TimMcCool/scratchattach/pull/250/commits/2df405601998e2a1affb7a655ab316a25918b966
.
0c83d30
https://github.com/TimMcCool/scratchattach/pull/250/commits/0c83d3096b7adb75d72e09b17becc134dfa253f5
fixed wrong attribute referenced
0e565d4
https://github.com/TimMcCool/scratchattach/pull/250/commits/0e565d43dfc8ceccdf480a1912271c56a463d7c8
rename Project.project_body() to Project.body()
f74a139
https://github.com/TimMcCool/scratchattach/pull/250/commits/f74a1399ace4f3b2d53757ce37f8db4fcf6f8b98
.
d37f31d
https://github.com/TimMcCool/scratchattach/pull/250/commits/d37f31d80cf717dd4bed7f95a6b90663fd0f5844
.
b8e72c7
https://github.com/TimMcCool/scratchattach/pull/250/commits/b8e72c7fe506329aa3de68a19eefbe54739fa167
more bug fixes
8eb689b
https://github.com/TimMcCool/scratchattach/pull/250/commits/8eb689b196727274784b56f1e2a8d200c3289b00
fixed user_agent funtion
d25125a
https://github.com/TimMcCool/scratchattach/pull/250/commits/d25125afa225a75e5701dbe9375551b6157da3fc
more bug fixes in project_json_capabilities.py
b084210
https://github.com/TimMcCool/scratchattach/pull/250/commits/b084210f96a2a881ddad40b19c84f5198fa734c5
added .download_url to ProjectBody.Asset
88781b1
https://github.com/TimMcCool/scratchattach/pull/250/commits/88781b180564e70b4e3ba3ae0ddabeea31037547
.
7424178
https://github.com/TimMcCool/scratchattach/pull/250/commits/7424178d664e0fee1ac2325148565cbdeadc0c06
.
0faca90
https://github.com/TimMcCool/scratchattach/pull/250/commits/0faca9000f3e6ff179b025e49679103b6ab117cd
.
95c869c
https://github.com/TimMcCool/scratchattach/pull/250/commits/95c869c5e6a34273839ffb851e60a9a6b2439273
.
0690a19
https://github.com/TimMcCool/scratchattach/pull/250/commits/0690a197f1cced114ee7beaea3169384047e8948
bug fix
010c770
https://github.com/TimMcCool/scratchattach/pull/250/commits/010c770fe5f4890b991455be808e5f20d1f9700b
added a docstring
64fcf54
https://github.com/TimMcCool/scratchattach/pull/250/commits/64fcf54c7b5d1d69381eb2d8de3d27d63b4c5910
some bug fixes
1a3e45b
https://github.com/TimMcCool/scratchattach/pull/250/commits/1a3e45bcaa1d564775befde8f6ef1c9bb5a8d0bf
added session_string from TheCommCraft's PR
4cab74a
https://github.com/TimMcCool/scratchattach/pull/250/commits/4cab74ad46181a9d485a192419986dd0f18b4a53
bug fix
be42f41
https://github.com/TimMcCool/scratchattach/pull/250/commits/be42f41926f66f55eaa1788cc03fe79d0f320b25
implemented BackpackAsset class
22401e4
https://github.com/TimMcCool/scratchattach/pull/250/commits/22401e401f821b07b312d8b77921b9bcdcf08608
small improvement in all download functions
8ac3d6a
https://github.com/TimMcCool/scratchattach/pull/250/commits/8ac3d6ad8b9be95c63df895fb17a1c5392f4948b
fixed bugs
63544bc
https://github.com/TimMcCool/scratchattach/pull/250/commits/63544bc1873ec8e5c21fb5c4b081ae118b51f882
cleaned up init.py file
402a5a7
https://github.com/TimMcCool/scratchattach/pull/250/commits/402a5a75a436dea2a6778a7911edac73b3978673
bug fix
e2ba0af
https://github.com/TimMcCool/scratchattach/pull/250/commits/e2ba0af8726d642a6d8af6a829ba063075dac186
fixed circular import and other bug
7fe7e2a
https://github.com/TimMcCool/scratchattach/pull/250/commits/7fe7e2ac221a8c7a58a72f3fcb04670ea5654bcd
added empty_project, project_body_from_dict and project_body_from_file
functions
06cf20d
https://github.com/TimMcCool/scratchattach/pull/250/commits/06cf20d9cfc708f3177dafc376d6a7393291cf7b
added functions for uploading assets
96b8038
https://github.com/TimMcCool/scratchattach/pull/250/commits/96b803836228f782b5d2a3ef0ea019540c148551
finished project json capabilities (still needs to be tested tho)
b0e17ef
https://github.com/TimMcCool/scratchattach/pull/250/commits/b0e17efe91fc066cc0d1426698f4865ea4de8b08
bug fix
6a90b47
https://github.com/TimMcCool/scratchattach/pull/250/commits/6a90b47469927d9dd2d6de5e93b37b2ab7f66ec1
rename
969a993
https://github.com/TimMcCool/scratchattach/pull/250/commits/969a9937db0a91099150be8a3277a730cd4a3846
fixed bug that didn' allow adding softfilters and spamfilters
fb24405
https://github.com/TimMcCool/scratchattach/pull/250/commits/fb244054eb8e46aed13d7dfb0e63196705e0c394
added scratchattach website
b7a3a33
https://github.com/TimMcCool/scratchattach/pull/250/commits/b7a3a3369030cbcb1974ec048eb7249710abb7f5
finished scratchattach website and made it deploy-ready
d4b4c27
https://github.com/TimMcCool/scratchattach/pull/250/commits/d4b4c274ff535bb649713ccba0b694e5ec3a5034
moved website in correct folder
11aed13
https://github.com/TimMcCool/scratchattach/pull/250/commits/11aed1356f882005318bb97b72003b610b1b3c80
fixed a bug affected projects received with studio.projects()
fbb9820
https://github.com/TimMcCool/scratchattach/pull/250/commits/fbb9820e77354b251cb27179b54043ae5564ad52
fixed bug in website
f228a22
https://github.com/TimMcCool/scratchattach/pull/250/commits/f228a22f8a3ead7f06c148c7ba5e6b0dbc82c95d
fixed another small bug in website
fffa14d
https://github.com/TimMcCool/scratchattach/pull/250/commits/fffa14df1d541aa86c407561ea79492c1ecb4ac0
small changes to website
8da9562
https://github.com/TimMcCool/scratchattach/pull/250/commits/8da956266982a9f78736d59e67e2c407c1ebc026
small change to website
960947e
https://github.com/TimMcCool/scratchattach/pull/250/commits/960947e8f56f2c4cbdac5a35ed3bc7d229c6aab3
added CustomCloud and improved the documentation / docstrings of cloud
classes
47376f8
https://github.com/TimMcCool/scratchattach/pull/250/commits/47376f82caef10e9a50ad4cac9fe0cc8b0e95f76
small change to website gradient
a459e49
https://github.com/TimMcCool/scratchattach/pull/250/commits/a459e4918b645384cbd3c18f764f676eeb042f36
added safe cloud var set ratelimit
305c1c1
https://github.com/TimMcCool/scratchattach/pull/250/commits/305c1c13e7dca0e0dbc5de1cd551c2173d7547ab
added intelligent rate limits
1029c71
https://github.com/TimMcCool/scratchattach/pull/250/commits/1029c71a0d328a88f6b60ca9de272f19b67a5184
fixed division by zero bug
1e4465c
https://github.com/TimMcCool/scratchattach/pull/250/commits/1e4465c3b278749e7d31ac28fd2f50f34e1b8962
fixed bug
8ab3808
https://github.com/TimMcCool/scratchattach/pull/250/commits/8ab380877c9ddcc842f931e0f9f19bf3ce795123
fix
b305a2e
https://github.com/TimMcCool/scratchattach/pull/250/commits/b305a2e5dce66e26f9447bd73e63504a3462059d
intelligent wait times are now working
8294983
https://github.com/TimMcCool/scratchattach/pull/250/commits/82949839a57d9d57d3dc08d797a822aa2137b96c
fixed for tw cloud
fc017f4
https://github.com/TimMcCool/scratchattach/pull/250/commits/fc017f4e5a75b34dc149b653a55f03924fc8d7b6
.
bdb8344
https://github.com/TimMcCool/scratchattach/pull/250/commits/bdb834441268afd7f322e12331ce31f5182c0654
,
83d572c
https://github.com/TimMcCool/scratchattach/pull/250/commits/83d572c99e68fdef4799d0e7c1ae7c6b0036fa39
reworked cloud requests, introduced Condition class
bf1c1a4
https://github.com/TimMcCool/scratchattach/pull/250/commits/bf1c1a4f36c751390c18414c2bf91d695fdcb545
started debugging new cloud requests
92668e8
https://github.com/TimMcCool/scratchattach/pull/250/commits/92668e8441be7c17f1233942944b485d67118540
.
12e4737
https://github.com/TimMcCool/scratchattach/pull/250/commits/12e4737398e57962f5d773a456717bbba5f45420
.
e0948ca
https://github.com/TimMcCool/scratchattach/pull/250/commits/e0948cad7593ee553c4c4ccaf6d66b4e1298bf20
cloud requests now functional
8c79748
https://github.com/TimMcCool/scratchattach/pull/250/commits/8c79748ca509d43b14328ac3d904d7ddbf620463
bug fixes, cloud requests now working
6ce1aa0
https://github.com/TimMcCool/scratchattach/pull/250/commits/6ce1aa0ef11fc82ae6975339a36f1d3688373905
implemented get_requester, get_timestamp, get_exact_timestamp functions,
removed old cloud requests code
4746f8c
https://github.com/TimMcCool/scratchattach/pull/250/commits/4746f8c9d8bd6b4b24329cb080f5a7c5b246a6ee
replaced conidition with event
8dde721
https://github.com/TimMcCool/scratchattach/pull/250/commits/8dde721021dc27d8ea80e9be56ede795b25d3d46
added cloud storage, send_from_backend to cloud requests and backend
support for TCP-like packet loss prevention (method for re-requesting lost
packets)
f03df8c
https://github.com/TimMcCool/scratchattach/pull/250/commits/f03df8cfd9e17a74e1b9f9c4baa9d08aa9112ef8
added file for CloudRequestsAsync. CloudStorage has not been tested yet
dd20c1c
https://github.com/TimMcCool/scratchattach/pull/250/commits/dd20c1c0fd6f09b1300c09b83081ca6e9dc34f81
.
c57dbc9
https://github.com/TimMcCool/scratchattach/pull/250/commits/c57dbc96069cc24baf5424f1206b612210bcef13
small bug fix
e44c49e
https://github.com/TimMcCool/scratchattach/pull/250/commits/e44c49e369beb50c0df72950f8f5e86a70f7b499
added hard_stop to cloud requests
28bc38a
https://github.com/TimMcCool/scratchattach/pull/250/commits/28bc38a7a8ebccc2c4e3107ad34bc035781f5f7d
cooldown for send operation
890d6c7
https://github.com/TimMcCool/scratchattach/pull/250/commits/890d6c7dcc33cdb9f140108c6269a36d62fd9969
added better cooldowns
2757e79
https://github.com/TimMcCool/scratchattach/pull/250/commits/2757e7966837fddc8f8658a0f349848a9715592f
added higher limits
1a54484
https://github.com/TimMcCool/scratchattach/pull/250/commits/1a54484a70cfc6d45dfbfd60c6392bd32f86f33b
.
d32f483
https://github.com/TimMcCool/scratchattach/pull/250/commits/d32f4832feb15e29d194a5d68a596eb05ce45a42
added MultiEventHandler
4f77c3b
https://github.com/TimMcCool/scratchattach/pull/250/commits/4f77c3bae83174bc26358fa7eaf6f138379c4c5b
.
ed7fc04
https://github.com/TimMcCool/scratchattach/pull/250/commits/ed7fc04c2c3f1460f804fc11a159c4a784d8e720
.
7dc4592
https://github.com/TimMcCool/scratchattach/pull/250/commits/7dc45927f5cf6b43588ad292e4534b6220e16364
fixed bug regarding BackpackAsset.download()
58734ff
https://github.com/TimMcCool/scratchattach/pull/250/commits/58734ff29d574fe48ae4b5c6d6be0d96139c2822
fixed small bugs
cb99398
https://github.com/TimMcCool/scratchattach/pull/250/commits/cb9939843b2dca58fa4cd7bf7c6bca352291a443
removed debugging print
b4a3acb
https://github.com/TimMcCool/scratchattach/pull/250/commits/b4a3acbe214c1acaf3aa73302a148c441d8dec1a
.
6abefa4
https://github.com/TimMcCool/scratchattach/pull/250/commits/6abefa42921298f9f5a2fae860744946062f5f81
.
15e73a5
https://github.com/TimMcCool/scratchattach/pull/250/commits/15e73a5596200ec7fedf843be1b63f0f3ad4f087
uploaded updated cloud requests sprite
555ca5f
https://github.com/TimMcCool/scratchattach/pull/250/commits/555ca5f4289070192314734aac3e01eb9aec5056
.
b07266f
https://github.com/TimMcCool/scratchattach/pull/250/commits/b07266f24e4499db94ab5cd71ef3272c3e937a81
finished cloud storage
5753312
https://github.com/TimMcCool/scratchattach/pull/250/commits/57533128a715dafb2e686657ad933208bcf9b971
added ping operation to storages
c1b2e05
https://github.com/TimMcCool/scratchattach/pull/250/commits/c1b2e053cf2e850f30fb586af785d617bfe2b19a
added cloud storage template sprite
002e3a5
https://github.com/TimMcCool/scratchattach/pull/250/commits/002e3a5962718eec46672e8d407444e6ffc02255
.
48a9494
https://github.com/TimMcCool/scratchattach/pull/250/commits/48a94947a693143d7ad090d8658ce404f5bac5e0
fixed cloud storages template
fb7f100
https://github.com/TimMcCool/scratchattach/pull/250/commits/fb7f1008a7d038d9888ada8c9d139477514773a7
removed asyncio cloud requessts because I will not implement these
2e3a08b
https://github.com/TimMcCool/scratchattach/pull/250/commits/2e3a08bb0c4507487c679699e8b4fa442407e674
added error messages to cloud storages
a027ece
https://github.com/TimMcCool/scratchattach/pull/250/commits/a027ece3006add12b2ea92122815b690a26cd0ba
added on_set event to cloud storage databases
c79ad35
https://github.com/TimMcCool/scratchattach/pull/250/commits/c79ad3589d24a008a817d59db63878c46e52abd2
.
a226409
https://github.com/TimMcCool/scratchattach/pull/250/commits/a226409a02dca2eccf678f5151c56df9abc935ba
.
c1232ba
https://github.com/TimMcCool/scratchattach/pull/250/commits/c1232badb831c2d3be576fc452abd2f7ea2d063a
rename read_sb3_file
50ca889
https://github.com/TimMcCool/scratchattach/pull/250/commits/50ca8890c76aa8a8e053eb7b8133453d54b97295
.

You are receiving this because you are subscribed to this thread.Message
ID: @.***>

because v2 is finished

Have you changed the Docs yet?
Tim @.***> schrieb am Sa., 12. Okt. 2024, 13:56:

because v2 is finished
—
Reply to this email directly, view it on GitHub
https://github.com/TimMcCool/scratchattach/pull/250#issuecomment-2408537198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCKMZSSLYQ2GW63IR3ZMOLZ3EE7XAVCNFSM6AAAAABP2LCNO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGUZTOMJZHA
.
You are receiving this because you commented.Message ID:
@.***>

no, I'm still working on that rn. The code for v2 is merged into the main branch, but there's no automated PyPi upload so on PyPi there's still the old version atm


Create control for animated XYZ Layers sequence

Make layer switching only for fully loaded tiles and implement it with an animated sequence.

PR https://github.com/openglobus/openglobus/pull/546


make Rapido not invasive

Closed with https://github.com/nextbitlabs/Rapido/commit/1af743df7cd4b29174ac4df4b4e14e8a1e50c278.


Update all the outdated dependencies and all necessary changes in components..

Description
Update all dependencies to the latest version so that all the new features in updated dependencies could be implemented in this project.
I have completed this task, please me the task so I can immediately make a pull request within 5 minutes.
Expected Behavior
Behavior of the website remains same.

Is someone working on this issue , if not i request the maintainer to assign this to me.

Is someone working on this issue , if not i request the maintainer to assign this to me.

Bro I have been working already.. please find other issue make pull req..

@pjoshi999 go ahead

Is someone working on this issue , if not i request the maintainer to assign this to me.

Bro I have been working already.. please find other issue make pull req..

Okay bro ..work on it i ll find some other issue to work on.


feature-card-image.html

i have created the template as per the assigned issue#112.
screenshot:

Please use a different image like in the issue. @hritikbhattacharya


[WIP] Show captions of image in media details

Description (required)
Fixes #2337
What changes did you make and why?

fetched captions of media by using mediawiki api
Added captions section in media details

Tests performed (required)
Tested ProdDebug on Motorola Moto G5 plus with API level 24.
Screenshots showing what changed (optional - for UI changes)

@nicolas-raoul I have used english as the default language for testing and also have enabled language fallback .
What should be the default language in which captions should be shown?

Codecov Report

Merging #2662 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2662      +/-   ##
=========================================
- Coverage    2.75%   2.75%   -0.01%
=========================================
  Files         260     260
  Lines       12430   12450      +20
  Branches     1125    1126       +1
=========================================
  Hits          343     343
- Misses      12060   12080      +20
  Partials       27      27

Impacted Files
Coverage Δ

app/src/main/java/fr/free/nrw/commons/Media.java
1.5% <0%> (-0.04%)
:arrow_down:

...n/java/fr/free/nrw/commons/MediaDataExtractor.java
0% <0%> (ø)
:arrow_up:

...fr/free/nrw/commons/media/MediaDetailFragment.java
0% <0%> (ø)
:arrow_up:

...rw/commons/mwapi/ApacheHttpClientMediaWikiApi.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ceaaa9...73d4c24. Read the comment docs.

Looks great!
Please use the Android locale. For instance, if the Android phone is in French, the caption should be shown in French.
Multilingualism is the goal of captions, actually :-)
I just added French captions to https://commons.wikimedia.org/wiki/File:Münster,_St.-Paulus-Dom,Alter_Chor--2019--_3789-93.jpg

@nicolas-raoul I have updated my PR

@nicolas-raoul I have made it singular and have added java docs :-)

@maskaravivek Sure I will add it :)

@maskaravivek I have added unit test cases.

I am closing this one since another one is already available for this issue, see #2933


help?

Hi everybody.
Straight to the point. The code just doesn't work for me. Therefore, please give a link to the working code in Google Collab.

brother, the title of the question is misleading


Component does not fail gracefully when a section title cannot be found

https://github.com/metal/metal-reading-progress/blob/master/src/ReadingProgress.js#L35
When this querySelector returns null an error is thrown. It would be nice if it either passes an empty string as the title or throws a more helpful error.

Yep. /cc @fernandosouza you guys can go a head and push a fix for it.

Sorry for the delay, @eduardolundgren. I'm going to take a look.


Fix Node#getStart(sourceFile, true) throwing when node has a js doc and no parent

Fixes #35028
I unfortunately don't have time to add tests, improve the code, or do any more work on this so this is just a resubmission of #35029.

Thanks @sheetalkamat for quickly pointing me in the right direction to add tests.


Onboard team members

[x] Get team members GitHub user names
[x] Send GitHub invitation to playgrounds team
[x] Find and send guide to help new team members get onboarded

All members with github account have been added to the org
Some members prefer notion for work tracking. To accomodate these contributors, we will create a new pipeline to transfer completed assets to the org


New doc

Fix inconsistencies throughout API + new documentation start

Please someone review

I've made a few comments. Looking forward seeing the next step of the documentation.


feat(visit): Add path-aware variants

TODOs

[ ] Create AstKind enum, which is c-like enum without any data
[ ] Create AstNodeRef enum, which stores parent info like, &'a ObjectLit
[ ] Add a method to convert node to AstKind
[ ] Add a method to convert node to AstNodeRef
[ ] Adjust other codegen parts to use __ast_path
[ ] Add cfg(feature = "path") to items. (I didn’t do this because it makes development harder)
[ ] Implement swc_visit::AstKindPath
[ ] Implement swc_visit::AstNodePath

Maybe this could be done in a non breaking way?
Add two function to Visit/VisitMut add_parent_path and remove_parent_path and default them to noop. If user would like to save parent path, they could add a field on their Struct and overrider these functions. Hopefully rust could optimize that cost away.
This would require a bit more boilerplate, but doesn't need an extra feature and all the problems.

@Austaras This is not a breaking change.
This is about creating more traits.
I want to use the feature flag because

Core transforms will not use path-aware visitor
Making it optional via feature flag will improve compile time. (release build takes more than 1 hour at the moment)

But well, I think your solution is better than creating a whole new trait. ~(Except the compile time in release mode)~
Oh well we can use feature flag in this case too

After thinking about more things, I found that your solution is better in all cases, thank you!

I found one problem.
For dyn Visit, two dynamic method calls for each visitor methods call seems like too much.
Any ideas?

Core transforms will not use path-aware visitor

Well I'm currently writing something greatly in need of parent scope.

For dyn Visit, two dynamic method calls for each visitor methods call seems like too much.

That won't happen -- https://godbolt.org/z/1aG8T84vK

@Austaras LLVM has devirtualizer so you need more code to avoid it.
See assembly of https://play.rust-lang.org/?version=stable&mode=release&edition=2021&gist=311d925a04c1e683ccc1c23996116e4d

See https://godbolt.org/z/9WzGYaM3Y

Your example doesn't have a default impl for add_parent_path -- do you mean this? In Visit::method1, there's only call to print.

I meant the count of callq

Your example doesn't have a default impl for add_parent_path -- do you mean this? In Visit::method1, there's only call to print.

In your example, the trait is devirtualized. f3 has call to print

Oh it's same in my example

LLVM has devirtualizer
https://doc.rust-lang.org/std/hint/fn.black_box.html could be used to avoid that

I decided to fo with with_path because main use case is &dyn Visit


Support for patch-based version bumps on dockerfiles

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
Hello, dependabot team 👋
We have docker images that follow a naming convention of <language>-<major>.<minor>.<patch>-<platform>. We noticed that fetch_latest_version essentially only sorts by this regex and picks up the last one. So given a FROM statement that references 2.4.0-slim and this set of tags, 2.5.0-slim is recommended instead of 2.4.1-slim.
Is there any plan to support patch-based version updates, somehow? If not, do you have any recommendations on how we can customize dependabot to have this behavior, through say a plugin or something similar?
Thank you!

Did you try something like
version: 2
updates:
  - package-ecosystem: "docker" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "daily"
    ignore:
      - dependency-name: "*"
        update-types: ["version-update:semver-major", "version-update:semver-minor"]

Hi David, thanks for responding.
We have, but unfortunately it still recommended a minor bump instead of a patch bump.

yup, that worked for us. and just mentioning this here for future readers since it's not explicitly described in the docs, you can include repository name and the image name like so:
# given an image tag <account ID>.dkr.ecr.us-west-2.amazonaws.com/base/foo/bar/ruby:3.2.1-focal-jemalloc
version: 2
updates:
  - package-ecosystem: "docker" # See documentation for possible values
    directory: "/" # Location of package manifests
    schedule:
      interval: "daily"
    ignore:
      - dependency-name: "base/foo/bar/ruby"
        update-types: ["version-update:semver-major", "version-update:semver-minor"]

Thanks for posting back your testing. Happy to review a PR to the docs site to improve this!

I saw that you proposed a documentation update at https://github.com/github/docs/pull/24736. Thanks so much! 😍


Add explicit error to ConsistentRead

What type of PR is this?
/kind bug
What this PR does / why we need it:
Return a specific error when ConsistentRead fails because it cannot get a consistent content on given file to give caller an opportunity to make better decision what to do about it.
Which issue(s) this PR fixes:

Helps to work around https://github.com/kubernetes/kubernetes/issues/101791
Prerequisite of https://github.com/kubernetes/kubernetes/pull/102059
Release note:
ConsistentRead now returns distinct error code when it cannot get a consistent read of a file.

returning of specific error in itself is a good idea and hence lgtm.
/lgtm

Fixed gofmt

/lgtm

/assign @dims
for approval.  See https://github.com/kubernetes/kubernetes/pull/102059 for the full story.

/approve
/lgtm
thanks @jsafrane


Input_results_in_2d.mp4 is same as input.mp4

Hi,
After running baseline.sh, the experiment folder was created with the resultant video. This video is exactly the same as the input video with no keyframes or mesh on the human doing the side monster walk action.
Could you help me out.
Thank you!

Hi, sorry for the late reply. Have you figured out the problems?

Yes, i incorrectly installed the Render Env. Now it is working.

Hi! How did you installed the render env. correctly? I tried following the instructions but still no results.
Thanks for your help!


[SPARK-37805][TESTS] Refactor TestUtils#configTestLog4j method to use log4j2 api

What changes were proposed in this pull request?
SPARK-37795 add a scalastyle rule to ban org.apache.log4j imports, but there is still one place to retain the imports of org.apache.log4j in o.a.spark.TestUtils.
This pr refactor configTestLog4j method in o.a.spark.TestUtils to use log4j2 api and let the log behavior using log4j2.x be the same as that using log4j1.x before. In fact, the configTestLog4j method behavior before this pr is invalid because PropertyConfigurator.configure method in org.apache.logging.log4j:log4j-1.2-api is an empty method as follows:
https://github.com/apache/logging-log4j2/blob/491a0b3787975b6fc95b6a8cb3da76dc7517c65f/log4j-1.2-api/src/main/java/org/apache/log4j/PropertyConfigurator.java#L39-L47
Another change of this pr is rename the method name from configTestLog4j  to configTestLog4j2.
Why are the changes needed?
Clean up the org.apache.log4j imports left in Spark internal and let configTestLog4j method behavior keep consistent between log4j1.x and log4j2.x.
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Pass the Jenkins or GitHub Action
Manual test

Run the test cases using configTestLog4j method in the following 3 scenarios:

without this pr to test log4j2.x
with this pr to test log4j2.x
run git reset --hard 19227983e91a54b5f27ade6412dad1088dfcba9e to test log4j1.x

For example WholeStageCodegenSparkSubmitSuite, run
mvn clean install -DskipTests -pl sql/core -am
mvn test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.execution.WholeStageCodegenSparkSubmitSuite

Scenario 1 does not print any logs to the console, scenario 2 and scenario 3 will print similar logs to the console

cc @dongjoon-hyun

cc @viirya

FYI, @LuciferYang . It was intentionally ignored at that time after discussing with @williamhyun offline.

FYI, @LuciferYang . It was intentionally ignored at that time after discussing with @williamhyun offline.

What is the specific reason? I didn't find it in SPARK-37795

GA run failed，Let me check it first

GA Passed

8d0a078 merge with master

Looks OK pending tests

GA passed

Merged to master

thanks all


ExecutorUtils.newThreadFactory should create Error handling Threads

A vanilla Java Thread that executes a Runnable does not handle RuntimeExceptions thrown by the Runnable. We have added uncaughtExceptionHandlers to ensure that any RuntimeExceptions are at least logged. This logic is encapsulates in ExecutorUtils.newThreadFactory.
However, uncaughtExceptionHandlers do not handle Errors (e.g. OutOfMemoryError or NoClassDefFoundError). It simply swallows them and does not log them.
The easiest way to avoid this it to always use Callable instead of Runnable, as Callable handles this; however, legacy projects may be stuck using Runnables.
One possible solution is to add instrumentation to ExecutorUtils.newThreadFactory to produce Threads that catch any Errors and throw them as RuntimeExceptions. This is exactly what Callable does - if a Error is thrown in a Callable it gets wrapped in an ExecutionException.

Closed, detailed explanation in https://github.com/linkedin/gobblin/pull/875


cleanup links for api and src/tests

[approve ci]

[approve ci]

[approve ci rocky ubuntu]

[approve ci]


Add pytest to dev requirements

Wanted to lock down the pytest version before working on any tests

Thanks for that, Scott! Already merged @smturro2


Update CDK project so it only provisions a single AZ

RDS Sql Express Edition runs in one AZ only. But RDS requires a VPC with minimum two AZs. So no need to update AZ to 1.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html


[otbn] Evaluate spec change: set flags in BN.MULQACC

For ECC crypto, @felixmiller has determined in https://github.com/lowRISC/opentitan/issues/2470 that BN.MULQACC which is also able to set flags would save one instruction.
With the 128x128 multiplications (OTBN MULH) a typical sequence for a full 256x256 mult looks like this:
BN.MULH w3, w1.L, w2.L
BN.MULH w4, w1.U, w2.U
BN.MULH w5, w1.U, w2.L
BN.ADD w3, w3, w5 << 128
BN.ADDC w4, w4, w5 >> 128
BN.MULH w5, w1.L, w2.U
BN.ADD w3, w3, w5 << 128
BN.ADDC w4, w4, w5 >> 128

(this gives [w4, w3] = w1*w2)
The last instructions in such a sequence is always an ADDC with the consequence that the flags are set based on the result.
Often the MSB needs to be tested afterwards (e.g. in a subsequent Select instruction).
Workaround in the PoC is to add a dummy BN.ADD at the end of each multiplication and add 0 to the result. This adds quite some overhead though and we should probably set the flags in BN.MULQACC.SO and BN.MULQACC.WO well.
We need to make sure though that this does not brake things elsewhere (a previously set flag supposed to survive a multiplication instruction)
Tasks in this issue:

[ ] Come to an agreement if we should do that.
[ ] Update the spec with the new semantics
[ ] File follow-ups to update the implementation (RTL and simulator)

estimate 2

@felixmiller is commenting in https://github.com/lowRISC/opentitan/issues/3683

We might think of setting the MLZ Flags in the MULQUACC instruction if:

This is not a timing problem in the HW
We are sure that we do not clobber flags anywhere that are needed after an MULQACC where we can switch to the other FG

This would save us dummy instructions in the multiplication kernels, where this is performance critical.
I need to analyze #2 first before we move forward.

The current MULQACC implementation doesn't touch the flags but this can be altered so it does. We should probably see the timing results for the version without first to understand how much slack we have to play with (as this is likely to increase the critical path).
One outstanding question is are we happy with only affecting FG0? We'll need to play with instruction encodings if we want to target FG0 and FG1.

At this point I can easily add flag computation for a fixed flag group to MULQACC. I think we still need to decide on whether we want MULQACC to choose a flag group (meaning playing with the encoding). @felixmiller any thoughts?

@GregAC: I would say if we have the encoding space available it would be better to allow setting the flag group (Didn't we somehow find an empty bit recently).
Another thing I came across:
The typical sequence where MULQACC setting the flags would be helpful looks like this (last 4 instructions of mult kernel in Barrett):
bn.mulqacc            w9.0, w11.1,  64
bn.mulqacc.so w18.L,  w9.1, w11.0,  64
bn.mulqacc.so w18.U,  w9.1, w11.1,   0
bn.add                w18, w18, w31

the last instruction is the dummy instruction for setting the flags currently.
An issue I am seeing now is that the actual result (in w18) that has to be evaluated for the flags is never fully available in a single MULQUACC since it is assembled over two instructions. Or could it be gained from the accumulator in the 3rd instruction somehow before shifting?
In order to answer #2 from @imphil 's question above I tested setting the C and M flag in bn.mulqacc.so when used to shift out the upper half word and the L flag when used to shift out the lower half word. There is no point in setting Z flag since we don't know whether the other half word was zero.
This then allows to get rid of the dummy add. It did not create an issue with existing code (RSA+ECC).
If this is the only way to set the flags I wonder if this does not over-complicate the spec...

One way to get the bit is only allow shifts of 0 and 64 for shifting the multiply result before adding to the accumulator (the <acc_shift_imm> field in the spec). We only use 0 and 64 I think. I specified the 128 and 196 just to add a little extra functionality, but didn't have a particular use in mind. Given we don't seem to have a use for them and we do have a use for the flag group setting it would make sense to sacrifice one for the other.
On the half-word writes how about a slightly more complex flag semantics much like you've already mentioned?

When writing to .L only set the L flag
When writing to .U only set the M flag

Zero is trickier but not impossible e.g. we could do

When writing to .L set Z based on the half-word it's writing
When writing to .U clear Z if the half-word it's writing is non-zero otherwise leave it alone

I'm not certain what to do with C. We could generate something based upon the carry out of the accumulate sum but with the way we're using MULQACC you shouldn't ever get a carry generated so leaving C alone, like with the logical operations would be a reasonable option.

Agreed to move forward with this spec change. Requires updates to spec, ISS, SW, and RTL.

For bn.mulqacc (without writeback), I assume we're going to leave flags unchanged? In which case, shall we keep the 2-bit shift, or knock that down to 1 as well for uniformity?

I'd go for uniformity

I've written a proposed patch for the spec and done the corresponding ISS changes. Of course, everything will break if we push this up without changing the RTL too, so I've just pushed it to a branch on my fork. You should be able to get a copy with something like:
git fetch https://github.com/rswarbrick/opentitan.git mulqacc-flags
git checkout -b FETCH_HEAD mulqacc-flags

@GregAC: Please can you take a look? I think the new spec does what we agreed above (and think that I implemented it right in the ISS!). Note that the smoke test doesn't assemble with this change: the calculation of w31 on line 259 uses a shift of 128. Looking harder, this code comes from the "replacing MULH" example. Are we sure we're ok with losing that trick? If not, we could choose to keep the larger shifts for bn.mulqacc and bn.mulqacc.wo and only disallow them for the .so variant (which means we can re-use the destination halfword bit).

I think we can avoid the need for the 128 bit shift by using two .so as the final two instructions.
However I quite like the idea of keeping larger shifts for the plain bn.mulqacc and bn.mulqacc.wo. It has some intuitive sense behind it in that if you're using .so you're accumulating things bit by bit, shifting out as you go so 0 and 64 is all you need (with 128/192 what you accumulate doesn't effect the 128-bits you're shifting out), but with bn.mulqacc and bn.mulqacc.wo alone you're doing things a bit differently so the wider shift possibilities are more useful.

Ok, sounds good. I'll update the spec to look like that (with 2 bits for shifting except for bn.mulqacc.so).

Oh, wait! There's a spare bit in bn.mulqacc.so anyway! We can have 2-bit shifts everywhere. Yippee!

Right. I've pushed up what I hope is a much more sensible solution. It's at the branch above, and I've also opened a draft PR so that people can shoot it down make constructive criticism :-)


Allows HaveSearchParams expectation to accept nil

Before, have_search_params(:with, :published_at, nil) would strip out the nil and return false positives. Now, expectations with nil will ensure the correct query is formed.
Here's a more verbose example of the problem and the fix:
class Post < ActiveRecord::Base
  searchable { time :published_at }
end

# search for unpublished posts
Post.search { with(:published_at, nil) }
expect(Sunspot.session).to have_search_params(:with, :published_at, nil)
#=> PASSES

# but if the search is incorrect...
# BEFORE
Post.search { with(:published_at, Time.now) }
expect(Sunspot.session).to have_search_params(:with, :published_at, nil)
#=> STILL PASSES

# AFTER
Post.search { with(:published_at, Time.now) }
expect(Sunspot.session).to have_search_params(:with, :published_at, nil)
#=> FAILS AS EXPECTED

Good catch, and thanks for the PR. Changes are in gem version <IP_ADDRESS>.


added search persistence when moving from bookmark to home

Fixes #224
Description
Added search persistency when moving from bookmark context to home.

Other information

Checklist:

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

@makkoncept The issue was when we clicked on the home button, it called the function loadStoredSearch, which basically first checks whether the other setting enableSearchStorage is checked or not, so when moving from bookmark to home, it creates a problem.
Also, there was issue when someone searches a query, so I had to remove the condition and store the result no matter what.
And created 2 different functions, one when the home button gets clicked and the other when the extension is open.
Please verify it.

@techievivek Thanks for the PR! I will check it out soon.

@makkoncept Thank you for pointing out the bug, I will fix the bug soon and update the PR.

This works fine but I have found a very subtle bug. When the user searches for a query that returns an empty result then the localStorage is not updated as the result array is empty. This means that after switching from the bookmarks section, the last correct result will be loaded. That's good. But, below the loaded images in this particular case, the "No image found" message is still present. Please refer to the gif below:

The issue was if an invalid input was searched, the localStorage wasn't cleared, and thus moving from Bookmark to Home left with the same result, so once the input has been validated along with other parameters, I clear the localStorage. Please have a look at updated PR.

After switching from the bookmarks section to the search section, instead of the "No images found" message, the default search section message can be shown.

@makkoncept I will go through it and update the PR. Thank you

@makkoncept Please have a look at the Updated PR, I have added the required changes.


[Icons] Simplify paths on icons

As a part of our ongoing effort to optimize the Spark Tokens icon library, we propose simplifying the paths on our icons. This optimization aims to enhance performance and reduce the complexity of the icons.

I've made an initial attempt at using the Illustrator script in auto mode to simplify the paths of icons. However, the results are not very promising, as you can see in this comparison: Before/After Path Simplification. Further refinement is needed to ensure the original appearance of icons is not compromised.


2020.3 support

Tracking issue for the IntelliJ 2020.3 major release, which the plugin isn't compatible with.
We're new to this ecosystem, is it normal for the Bazel plugin to trail ~1/2 year behind the IJ release? (not complaining, just wondering - if this is normal, we'll probably have to ask external contributors to our project to pin their IJ release)

Duplicate of https://github.com/bazelbuild/intellij/issues/2102.

Oh, I somehow missed that. Thanks!


Flakifying Pirouette using haskell.nix

Use haskell.nix to provide a proper build environment.
All content in nix/ and shell.nix may be deleted if we want to force the migration to flakes.
The flake may be tested using direnv (a .envrc is set up), or simply with
$ nix develop
$ cabal run

Profiling has not been tested yet.

Is there some learning material about flakes for those of us not yet enlightened?
Also, do the build instructions need to be updated in the README?

@facundominguez For flakes in general, I think the nixos manual is quite good https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html.
Indeed the build instructions ought to be updated.


LeftOperand class is an enum which is not compliant with IDS or its use of ODRL

The info model models the LeftOperand of a constraint as an enum. This means that the infomodel cannot express constraints other than those defined in the enum class. For example, it is impossible to express policies that include usage constraints other than the 17 defined in the enum class.
My understanding of IDS is it supports ODRL and extensible policy constraints so this is a bug in the info model. This is currently a severe blocker for the EDC and need to reach out to the infomodel folks for help.
.cf https://gist.github.com/jimmarino/0e4b1cddc6d42bd704c13e48881797ff

Tried to note down some observations, past discussion outcomes, and next steps @jimmarino.
Policy Language in IDS

IDS extends ODRL: the IDS Usage Control Language was initially defined as a profile of the ODRL language
Referring to this comment, IDS introduces pre- and post-duties that could, nevertheless, be mapped to ODRL
In IDS, it was tried to map use case requirements to policy classes (see here for templates) and thus, attributes as the left operand or actions were restricted to a number of enums that seemed reasonable.

Action: IDS vs ODRL
Taking a look at this documentation, this is the current status:

Action: A thing one might be permitted to do or prohibited from doing to something.

has super-classes: action
is in domain of: action refinement, is included in
is in range of: action, is included in
has members: aggregate by consumer, aggregate by provider, anonymize, compensate, delete, distribute, ecrypt, grant use, log, modify, next policy, notify, read, track provenance, use, write (16)

ODRL defines top-level actions (use, transfer). According to the documentation, Action terms must be defined using the includedIn property referring to an encompassing Action and either use or transfer as the top-level parent term by transitive means. Details on the includedIn and implies properties can be defined by ODRL profiles.
The ODRL vocabulary defines 72 action types. Some of them appear in IDS, a lot of them not. On top of that, IDS defines other actions (marked cursive).
LeftOperand: IDS vs ODRL
Taking a look at this documentation, this is the current status:

LeftOperand: Instances of the LeftOperand class are used as the leftOperand of a Constraint.

has super-classes: left operand
is in domain of: broader LeftOperand
is in range of: broader LeftOperand, leftOperand
has members: absolute geo-spatial position, count, current event, delay, elapsed time, endpoint, execution system, path to attribute, payAmount, payment, policy evaluation time, purpose, quantity, recurrence rate, security level, state, user (17)

broader LeftOperand: This LeftOperand is transitively included in the object LeftOperand.

The ODRL vocabulary defines 34 operand types. Same as for actions, some of them appear in IDS, a lot of them not. On top of that, IDS defines other values.
Problem

The EDC wants to support full ODRL independent from a specific use case. Mapping an ODRL policy to IDS as-is causes information loss in a way it should not. If IDS simply extended ODRL, one could argue that not supporting IDS features is bad but a design decision. However, any information originally expressed in ODRL should be mappable to IDS.
Members of an IDS Infomodel object are expressed as Java enum classes (in the IDS Infomodel libraries). Thus, custom values cannot be set.

Possible Solution
Long-Term

Alignment of definition and identifiers for IDS actions and leftOperands (and other attributes that may be restricted by IDS).
Steps to put into practice:

Change IDS Information Model: new release (v5.x.x.?).
Adapt IDS Infomodel CodeGeneration and IDS Infomodel Serializer to support new IDS Information Model version.
Integrate new libraries into EDC.

Challenges

Adaptations cannot be integrated in IDS Infomodel v4 because of breaking changes.
New IDS Infomodel v5 will bring more changes than that.
No release date for v5 planned for now.
Work for alignment needs to be done first (difficulties are not to be underestimated because IDS interprets values different from ODRL and thus cannot use the same terms).

Current Work

IDS Information Model clean up: usage of application profiles; remove duplicated identifiers, use existing (e.g. ids:mediaType to IANA MediaTypes)
Alignment of ODRL and IDS actions (document in IDS ThinkTank, not accessible -> maybe you could make this a public discussion @Brandstaedter?)

Short-Term ("Quick Fixes")
EDC

Possible (very bad) workaround for the moment: All java classes (Infomodel lib) support a properties map. An "odrl to ids"-transformer could insert the ODRL Action/leftOperand as a custom property of an fix IDS Action/leftOperand. An "ids to odrl"-transformer knows that and takes this property to map it back to odrl. So in general, we just "forget" all IDS enums and only use the ones from ODRL.

IDS java libraries (not sure what can be implemented and how)

Change the IDS Infomodel CodeGeneration (and thus also the serializer) to provide a wrapper class. This could expect the pre-defined enums, but also custom strings - and map this to json-ld.
Change the IDS Infomodel CodeGeneration (and thus also the serializer) to enrich enum classes with the possibility to add custom strings - on the same level as the default enums, so not as a custom property as mentioned above).

Contact

IDS Information Model: responsibles from Fraunhofer FIT are @JohannesLipp and @clange
IDS Usage Control language: responsibles from Fraunhofer IESE are @Brandstaedter and @hosseinzadeha
IESE-side contact person from ODRL: @riannella

I will convert this to a discussion as this is no concrete todo for now. Rather, we need to define next steps from this.


[Popper] The anchorEl prop provided to the component is invalid

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/p/sandbox/date-component-h3rd46
Video illustrating the problem: https://drive.google.com/file/d/1o4sQGAuk3N2cRw6t4o44PlE4p_hUdb23/view?usp=sharing
The example above uses a MuixTimePicker (it uses the popper component internally) to implement a date input into an AgGrid table column filter. If you click on a part of the page that is not related to either the column menu or the calendar, the calendar will jump to the upper left corner of the screen before being closed.
Current behavior 😯
Popper component (hereinafter MuiBasePopper) have useEffect witch call forceUpdate method of PopperJS instance on every time after MuiPopperBase was rendered. This behavior sometimes leads to undesirable results. In my case, the problem arises because it is not possible to correctly determine the position of the anchorEl when MuiPopperBase closing.
Expected behavior 🤔
It would be nice if forceUpdate method of PopperJS instance do not called in cases where correct updating position is not possible. Or would be some way to control this through props.
Context 🔦
When embedding MuiPopperBase and dependent components into third party libraries, we don't always have full control over the rendering process. I understand that the sudden removal of the anchorEl from the DOM is an emergency situation. But it would be nice if MuiPopperBase to handle it more gently.
The closest issue I could find.
Your environment 🌎

npx @mui/envinfo
System:
    OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
Binaries:
  Node: 20.5.1 - ~/.nvm/versions/node/v20.5.1/bin/node
  Yarn: Not Found
  npm: 9.8.0 - ~/.nvm/versions/node/v20.5.1/bin/npm
Browsers:
  Chrome: 120.0.6099.129
npmPackages:
  @emotion/react: 11.11.3 => 11.11.3
  @emotion/styled: 11.11.0 => 11.11.0
  @mui/base:  5.0.0-beta.16
  @mui/core-downloads-tracker:  5.15.1
  @mui/icons-material: 5.14.9 => 5.14.9
  @mui/lab: 5.0.0-alpha.145 => 5.0.0-alpha.145
  @mui/material: 5.15.1 => 5.15.1
  @mui/private-theming:  5.15.1
  @mui/styled-engine:  5.15.1
  @mui/system:  5.15.1
  @mui/types:  7.2.11
  @mui/utils:  5.15.1
  @mui/x-date-pickers: 6.18.6 => 6.18.6
  @mui/x-tree-view: 6.0.0-alpha.4 => 6.0.0-alpha.4
  @types/react:  18.2.20
  react: 18.2.0 => 18.2.0
  react-dom: 18.2.0 => 18.2.0
  typescript:  5.1.6

tsconfig
{
    "compilerOptions": {
        "allowSyntheticDefaultImports": true,
        "baseUrl": "./",
        "experimentalDecorators": true,
        "jsx": "react-jsx",
        "module": "esnext",
        "moduleResolution": "node",
        "paths": {
            "@/*": ["./src/*"],
            "assets": ["./public"],
            "sprite": ["./src/images/icons"]
        },
        "resolveJsonModule": true,
        "strict": true,
        "strictFunctionTypes": false,
        "strictNullChecks": true,
        "target": "esnext"
    },
    "exclude": ["node_modules", "**/*.spec.ts"]
}

We are not going to include Popper in future versions of Base UI. We will use Floating UI under the hood for all components that contain popups.

@karamws If your "dynamic form" is a parent React component, then it's probably not the same problem. One way or another, you can provide custom Popper component via slot props ({ popper: YoursFixedPopper }). You can use a copy of Popper component as a basis.


Bug in optimization of Bayesian (Variational Posterior)

First, thank you for the great work! I really like the ideas you presented with UCB, which is why I looked at your code in detail and stumbled across the following:
In your implementation of the variational posterior for the Bayesian layer, the two parameters defined for optimization (i.e. initialized with torch.nn.Parameter) are mu and rho. However, rho is only used once to initialize sigma. After that it does not have any impact on sigma and does not affect the outcome of future iterations (apart from scaling the learning rate). In other words, it is subject to optimization, but the optimized value does not have any effect on the weight distribution. I checked it explicitly, sigma stays the same throughout the whole process. That is, the resulting uncertainty is not the result of optimization but rather the result of random initialization.
I am also a little confused about the function update_lr(), so I have the following questions, hoping that I understood the code correctly:

Why are the classifiers only subject to optimization in the first task?
When the function is used for the adaptive learning rate update, why are the means not included in the optimization?

I hope you can help me with these concerns.

I faced the same issue too. I found out that using torch.as_tensor() is the cause of this issue by blocking the gradient flow:
it is better to cheng the 2 lines:
log_var = w1 * torch.as_tensor(lvps).to(device).mean() log_p = w2 * torch.as_tensor(lps).to(device).mean()
To the following:
log_var = w1 * torch.stack(lvps).to(device).mean() log_p = w2 * torch.stack(lps).to(device).mean()


Profiling tool - step 5 - clarity of text output

the prgress message during step 5 reads “* Step 5/5: generating plots... Plotting data for alltoallv calls: 2110/1” but it is not clear what "/1" means. (The 2110 is the number of the captured call being rendered and is updated for as each one is rendered).

Fixed with the work i have been doing on the generation of graphs


chore(main): release 1.2.2

:robot: I have created a release beep boop
1.2.2 (2023-06-01)
Bug Fixes

versioning: test release workflow (523ddb1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/AppelBoomHD/alfred-vscode-github/releases/tag/v1.2.2 :sunflower:


unable to use CURI format for reference in the form editor

From @sabrinatoro on June 20, 2018 21:52
In the Form Editor: I am unable to add a reference in the following format:
ZFIN:ZDB-PUB-170818-4
The message on the form is : "The proper format for references in a GO annotation is 'DB:accession_number': evidence(1)"
When using the "Search Database" function, the reference imported in the ZFIN:ZDB-PUB-### format.
The form not allowing this format is an issue, especially for the reference which do not have corresponding PMID. (I can add example if needed)
Note: There does not seem to be an issue when using the Graph view.
Copied from original issue: geneontology/noctua#565

Thanks for reporting this @sabrinatoro
@tmushayahama - let us know if you need any additional info.  Thx.

@tmushayahama
I've tested this with various permutations of possible paper identifiers and all worked fine.
Thx.


Manually deploy node with external bridge and Float

Description
As a developer I want to manually deploy node with external bridge and Float
Once the #930 bug is fixed , use the node pki to get the crypto in the node path of vault
1.Use the keystores to deploy bridge and float manually with node
Acceptance Criteria

the bridge and float connection with node is working

The following are changes required for node bridge float integration :

Modify the node and node registration chart to take float address as p2pAddress when firewall is enabled
Modify the node config for external bridge to true when firewall is enabled
Create an Ansible role to fetch network-parameters file from node container and copy it to bridge and float containers
Or for step 3 explore http api endpoint of networkmap service to provide the network parameter file
Change bridge and float charts to fetch keystores from vault paths
Cleanup the bridge and floats charts to put config file inside the container and use credentials from vault


Are there plans to support a javascript port?

I don't plan at this time to work on any ports, but there are a number of ports listed in the README that others have done. Happy to answer questions for anyone who is working on a port, and people are welcome to send a PR linking to their port from the README.


update clap and swayipc to 3.0

The update of swayipc to 3.0 should fix i3 incompatibilities.
Surprisingly, the binary size decreased to 1.3M from 1.4M.

Thanks!


Remove redundant sponsor logos

Massive search&replace so that only the main introduction page shows the sponsor logos (this seems to be consistent with the new tutorial material for Climatematch as well).

Apologies, closing this PR and moving the branch to the main NeuromatchAcademy repository instead of doing the PR from my personal fork.


[gatsby-plugin] Nothing in outDir

So I followed the instructions but couldn't see any files generated in the specified outDir and neither some UI server that open in the browser.
Here's my project: https://github.com/muuvmuuv/portfolio/tree/development
Just add your plugin.
    {
      resolve: 'gatsby-plugin-bundle-stats',
      options: {
        // https://github.com/relative-ci/bundle-stats/tree/master/packages/webpack-plugin
        outDir: `${__dirname}/reports`,
      },
    },

Hi @muuvmuuv,  outDir needs to be relative to your build folder
https://github.com/relative-ci/bundle-stats/tree/master/packages/webpack-plugin#bundlestatswebpackpluginoptions
For your case, the config should be:
    {
      resolve: 'gatsby-plugin-bundle-stats',
      options: {
        // https://github.com/relative-ci/bundle-stats/tree/master/packages/webpack-plugin
        outDir: `reports`,
      },
    },

i just noticed that gatsby plugin doc is pointing to the v1 package, will fix that ;)

Oh yes, sorry, but there is still no file generated.

Uff... I have looked into the wrong directory ^^ thank you!


Suggestion: Include thanks.dev sponsors

What problem do you want to solve?
Right now, we are getting sponsorship money from thanks.dev, but we aren't displaying any of those sponsors on the website.
What do you think is the correct solution?
Update the fetch-sponsors.js script to include thanks.dev sponsors.
Here's the API:
https://api.thanks.dev/v1/entity/gh/eslint/donors
For each donor, we should look at the last item in the payments array and, if the month is the current month, include them as a sponsor. For example, we are currently in October 2024, so only payments marked as 2024-10 should be included.
Participation

[ ] I am willing to submit a pull request for this change.

Additional comments
No response

Ill pick this

Thanks!


No loot received

Upon defeating a rare boss the loot window opened and when I selected "Take all" the loot window disappeared like usual but no loot was added to my inventory.
Inventory was not full
Loot was not spawned onto ground like it would with a full inventory
Included in that loot drop was a Venasurite, Super Rod and Vines x4

Contact me the next time you are online.


Release v0.9.0-rc.3 and to test with a multi-tenant setup

I think @phoban01 's example https://github.com/phoban01/flux-terragrunt-poc is a really multi-tenant example to test against.


Extend CTest suite and enable it inside NEURON

Description
This PR contains three main changes:

CoreNEURON's CTest tests are now run as part of the top-level make test target even when CoreNEURON is built as a submodule of NEURON.
Several CMake helper functions are added: cnrn_add_test_group,
cnrn_add_test and cnrn_add_test_group_comparison. These faciliate
including integration tests in the CoreNEURON CTest suite.
The new helpers are used to include several tests from the external
https://github.com/neuronsimulator/ringtest repository.

Minor additional fixes were needed to make the existing CoreNEURON tests
run when CoreNEURON is built as a submodule of NEURON.
How to test this?
# From nrn master
mkdir build
cd build
cmake .. -DNRN_ENABLE_TESTS=ON -DNRN_ENABLE_CORENEURON=ON
make -j
make test

Test System

OS: BB5
Compiler: PGI 20.9
Backend: CPU

Use certain branches for the SimulationStack CI
CI_BRANCHES:NEURON_BRANCH=master,

Closing this PR as it was decided to redistribute the contents across https://github.com/neuronsimulator/nrn and https://github.com/BlueBrain/CoreNeuron differently.


Feature Request: RegionsPluginEvents -> region-update

We currently have the region-updateD event that is fired by the region plugin. I was wondering how tricky it would be to also expose "region-update" in order to trigger other functions when a region is being updated (in our case the user drags a region on the timeline).
This event could be de-bounced as well to only fire every 200ms if it introduces performance issues.
Please let me know any thoughts.

Sure, makes sense! I will add the new event.

The region-update is now available in 7.8.2 📦. Cheers!


Can we check the annotation saving status through CVAT API's

In CVAT UI I can see, whenever I press the save button to save annotations the status changes like saving I wanted to know if I can access it through API

You see this message on UI during saving request is performed.
The request is sync, so, this state is not saved on the server and there is no way to get it from the server.


Use docker ubuntu image

Coverage remained the same at 80.733% when pulling dad669c52fd9bcbc1c6d0e8079d44855bc574efa on useUbuntuDockerImage into 92aa0cbfceddd5786c33601eca8c3d7b10e3794a on master.


chore: more mobile compatibility

couple of updates:

ensuring the schema.graphql are always up to date (needed to make sure the tooling doing the comparison are using an up to date files)
adding the generated.gql from the current deployed application (2.1.66). need more CI/CD iteration on that
adding associated github actions

I would take a different approach to this. Lets sync

How about this: https://github.com/GaloyMoney/galoy/pull/2448? It depends on https://github.com/GaloyMoney/galoy-mobile-deployments/tree/main/deployed-schemas which gets updated every 'beta' deploy. If we want to drop compatibility we just delete a file in that folder.


Update FAQ.rst

time.sleep(1): No point to wake up if there is nothing to do. Use time.sleep(schedule.idle_second()).
However, schedule.idle_second() returns negative value if no more jobs to run.
def run_threaded() is also a thread, making schedule.next_run() not a None.

I've gone ahead and created #399 inspired by this pr to give this example it's own place in the docs. Let me know what you think!


Feature/build website

:heavy_check_mark: Working using classes and objects.
:heavy_check_mark: Working using concepts of Single Responsibility and Tightly Coupled Objects.
:heavy_check_mark: Todo list app can show, create, delete and edit projects and todos.

:heavy_check_mark: Show add todo only if you have created a project
:heavy_check_mark: Show current project activities
:heavy_check_mark: Add class to show active and current project

:heavy_check_mark: You can create projects or todos(activities for the project)
:heavy_check_mark: When you create a new project it will be displayed in the projects list and highlighted as the current project
:heavy_check_mark: If you want to create a todo list and the projects list is empty, it will create the default project (Project 1)
:heavy_check_mark: If you want to create a todo list and there are project in the list, it will create the todo in the current project
:heavy_check_mark: To create a todo in a specific project, first select the project and then create the todo
:heavy_check_mark: You can delete or edit todos
:heavy_check_mark: If you delete a project then the first project in the list will be the current project and it will display the todos list
:heavy_check_mark: Add showMessage to show messages in DOM instead of alert()
:heavy_check_mark: Add information about npm installation, watch and start the app locally using scripts
:heavy_check_mark: Add webpack-dev-server as a development dependency

:heavy_check_mark: Let a user be able to select which project he is creating a todo for
:heavy_check_mark: Let the project be filterable to only its todos
:heavy_check_mark: Create a default project, you can use localstorage to store this


Mistake on complex filtering example in doc?

I think that there a mistake on Complex Filtering Example
Expected: "Find books with 2 possible dates and a specific author"
But result for me is: "Find books with 2 possible dates OR a specific author"
Or, with my own example below (filtering on User model):
Expected: "Find users with username containing 'mi' or 'E' and in "Bureau" department"
Result: "Find users with username containing 'mi' or 'E' OR in "Bureau" department"
To obtain expected result:
const filters = {
  $and: [
    {
      $or: [
        {username: {$contains: 'mi'}},
        {
          username: {$contains: 'E'}
        }
      ]
    },
    {
      'department': {
        name: {$eq: 'Bureau'}
      }
    }
  ]
}

hello @olivierbaudouin. that's true, however, the documentation is correct. the expected behavior when no operator passed is $and you don't have to specify it explicitly. clearly, there is an issue with the resolver of the package. Any PR to fix that is welcome.

I think it is a logical grouping(brackets)  issue.
Expected Query:  ('mi' or 'E') and (in "Bureau" department")
Result Query: "'mi' or 'E' and in "Bureau" department"
So accordingly operator precedence SQL find the results for mi or (E and in Bureau).
I speculate package is not designed to group using or operator as below.
('mi' or 'E') or (in "Bureau" department")
@abbasudo If that possible what should be the query string ?


clean up still interfering with builds

Folluw up of #43 and #40. It looks like that the latest builds are still failing: http://<IP_ADDRESS>:8080/job/Jbin_uT32__tf2_ros__ubuntu_trusty_i386__binary/3/consoleFull
I logged into the slave but couldn't find any hashes in the log file matching the errors in the console output, e.g.:
Error removing intermediate container bed26c5d4211: The given container is <nil>

But it looks like there are still multiple cron jobs deleting docker stuff:
# HEADER: This file was autogenerated at 2015-02-03 00:30:17 +0000 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: docker_cleanup_images
15 */2 * * * bash -c "python3 -u /home/jenkins-slave/cleanup_docker_images.py"
# Puppet Name: docker_cleanup_containers
5 */2 * * * bash -c "docker ps -aq | xargs -L1 docker rm "

It also looks like that the cleanup log file does not contain any output for the last 17h.

Trying to run the cleanup script manually on one of the slaves:
Traceback (most recent call last):
  File "/home/jenkins-slave/cleanup_docker_images.py", line 4, in <module>
    import dateutil.parser
ImportError: No module named 'dateutil'

Did you also resolved the duplicate cronjobs?

Yeah, in the 1st commit,  495d802. The ensure absent was there, but it didn't specify the user, and the default was 'root' not 'jenkins-slave' https://github.com/ros-infrastructure/buildfarm_deployment/commit/495d802186d426a922aaf999d1dffa5af944374a#diff-a2052a49729c2f5f50ebbc65e3d02352R163
I also added the cleanup rule for the repo. The job does not exist on the master so I didn't add a cleanup for it.

Also, since the last run, I verified the cronjob has gone away:
# HEADER: This file was autogenerated at 2015-02-16 23:30:11 +0000 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: docker_cleanup_images
15 */2 * * * bash -c "python3 -u /home/jenkins-slave/cleanup_docker_images.py"

This seems to happen again:

http://<IP_ADDRESS>:8080/job/Ibin_uS32__controller_manager__ubuntu_saucy_i386__binary/2/
http://<IP_ADDRESS>:8080/job/Ibin_uS32__forward_command_controller__ubuntu_saucy_i386__binary/2/
http://<IP_ADDRESS>:8080/job/Ibin_uS32__cob_default_robot_config__ubuntu_saucy_i386__binary/2/


New Proposal button

Once the entire proposal process is finished and all fields are read-only (see Issue #5) we should provide a New Proposal button which restarts the form fresh from the beginning to facilitate creation of multiple proposals without having to press refresh.

 proposal-creator: New Proposal button


String does not match the pattern of "^\d+[KMG]?$". - "php.memoryLimit": "-1"

This, line 117, gives a "String does not match the pattern of "^\d+[KMG]?$"." while a valid option defined in the description is '-1'

Same issue on other repo

Indeed. I'll have a look. Thanks.


Integrator studio have soap to rest conversion issue

Description
HI Team,
Below issues observed regarding SOAP to REST conversion and you can follow the below steps to reproduce the issue.

While creating rest api using wsdl file, In Generated swagger we can see that rootElement_ is getting added for all the schemas but while reference it is applying only for request, not for the response.
'Default_Object' added when reading elements that contain '-' character.

Steps to Reproduce

Use wsdl file which contains '-' character in schema.
Generate an API with this wsdl file(browse the wsdl file and import it to the ESB project).
Go to the generated API and search for the relevant resource and check the swagger definition.

Affected Component
IntegrationStudio
Version
8.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

public fixes: https://github.com/wso2/soap-to-rest/pull/11
https://github.com/wso2/integration-studio/pull/1227 has already been merged.


1.Modify the database to MySQL version 5.7

2.Add database initialization script

@pref-mail  The default should be sqlite you can look at how i did it in #191.

Thanks for your contribution. MariaDB was already added, so I don't think we need this anymore.


Buttons in Send Box appear cut off

The send box contains icon buttons that appear cut off:

The culprit is ROOT_CSS defined in BotFramework-WebChat/packages/component/src/SendBox/Assets/*
Please fix this to take on at least 40px for the height (or anything really that fixes the style)

What version of Web Chat are you using - latest or master? Also, can you include your Web Chat related code including your custom CSS? It's unlikely, but are there any console errors?
Thanks

Hi thank you for the quick reply. My code is a duplicate of the minimizable-web-chat sample
It is using the latest Web Chat package. No other custom CSS done besides those in the sample.


fix GAN example arguements under pl_example

What does this PR do?
It is a simple fix for generative adversarial network example in pl_examples argument error.  I didn't file an issue as it is a too simple bug with a need of simple fix.
Before
Traceback (most recent call last):
  File "generative_adversarial_net.py", line 275, in <module>
    main(args)
  File "generative_adversarial_net.py", line 244, in main
    model = GAN(args)
  File "generative_adversarial_net.py", line 122, in __init__
    self.generator = Generator(latent_dim=self.hparams.latent_dim, img_shape=img_shape)
  File "generative_adversarial_net.py", line 62, in __init__
    nn.Linear(1024, int(np.prod(img_shape))),
TypeError: int() argument must be a string, a bytes-like object or a number, not 'Namespace'

After
GPU available: True, used: False
TPU available: None, using: 0 TPU cores
/opt/conda/lib/python3.8/site-packages/pytorch_lightning/utilities/distributed.py:49: UserWarning: GPU available but not used. Set the --gpus flag when calling the script.
  warnings.warn(*args, **kwargs)

  | Name          | Type          | Params | In sizes | Out sizes
----------------------------------------------------------------------------
0 | generator     | Generator     | 1.5 M  | [2, 100] | [2, 1, 28, 28]
1 | discriminator | Discriminator | 533 K  | ?        | ?
----------------------------------------------------------------------------
2.0 M     Trainable params
0         Non-trainable params
2.0 M     Total params
Epoch 0:   1%|█▋                                                                                | 11/938 [00:01<02:06,  7.35it/s, loss=0.564, v_num=1]

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[ ] Check that target branch and milestone match!

Did you have fun?
Make sure you had fun coding 🙃

@jihoonl Thank you!
@PyTorchLightning/core-contributors We currently don't have the tests for examples?

@jihoonl Thank you!
@PyTorchLightning/core-contributors We currently don't have the tests for examples?


logs
DescrC:\Users\bened\Desktop\bmcr_crea_clock>flutter run -d chrome
Launching lib\main.dart on Chrome in debug mode...
Building application for the web...                                10,5s
Attempting to connect to browser instance..                         8,6s

Warning: Flutter's support for web development is not stable yet and hasn't
been thoroughly tested in production environments.
For more information see https://flutter.dev/web

�  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
For a more detailed help message, press "h". To quit, press "q".
Debug service listening on ws://<IP_ADDRESS>:55713/GssH6Lymv-8=
Thursday January 16
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
The following UnimplementedError was thrown during a scheduler callback:
UnimplementedError

When the exception was thrown, this was the stack:
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/j
s_dev_runtime/private/ddc_runtime/errors.dart 196:49  throw_
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/shader.dart 51:5                           createPaintStyle
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/bitmap_canvas.dart 265:45                  [_applyPaint]
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/bitmap_canvas.dart 508:5                   drawCircle
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/surface/recording_canvas.dart 899:11       apply
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/surface/recording_canvas.dart 78:18        apply
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/surface/picture.dart 253:35                paintCallback
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/surface/surface.dart 71:14                 commitScene
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_eng
ine/engine/surface/scene_builder.dart 520:5           build
package:flutter/src/rendering/layer.dart 801:35
buildScene
package:flutter/src/rendering/view.dart 230:36
compositeFrame
package:flutter/src/rendering/binding.dart 405:18
drawFrame
package:flutter/src/widgets/binding.dart 797:13
drawFrame
package:flutter/src/rendering/binding.dart 283:5
[_handlePersistentFrameCallback]
package:flutter/src/scheduler/binding.dart 1108:15
[_invokeFrameCallback]
package:flutter/src/scheduler/binding.dart 1047:9
handleDrawFrame
package:flutter/src/scheduler/binding.dart 856:7
<fn>
package:build_web_compilers/src/dev_compiler/C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/j
s_dev_runtime/private/isolate_helper.dart 50:19       internalCallback
════════════════════════════════════════════════════════════════════════════════════════════════════
Another exception was thrown: UnimplementedError
Another exception was thrown: UnimplementedError
Another exception was thrown: UnimplementedError
Another exception was thrown: UnimplementedError
ibe your issue and include the command you're running, flutter_web version, browser version

PHOTO OF THE GUILT:

here a screenshot of the minuscule virus, believe me, I do not have any floating action button in my Widgets but there is one in the Render Tree with a clear ID:
└LayoutId-[<_ScaffoldSlot.floatingActionButton>](id: _ScaffoldSlot.floatingActionButton)
How can I get rid of him, that is the question? How did he enter the render view, that is quite worrying?
DESCRIPTION OF THE GUILT:

@iapicca
flutter run -d chrome with SafeArea
CASE 02  d chrome.txt
flutter run --verbose with SafeArea
CASE 02 --verbose.txt
Thanls for your help

@benedicte69 could you share the Dart code you are trying to run?

Thanks. Unfortunately, it is not possible, despite its boilerplates it is a private code under licence. flutter run -d chrome seems to be working in all my other app excepted suddenly in this one on January 16. That is a pity, I would have liked to improve the responsiveness of it too experiment further and my fetich tool for that is chrome. That's lifeNow I am cleaning my computer from A to Z... The best thing I can do when things start going wrong...
Le mercredi 5 février 2020 à 21:39:52 UTC+1, Mouad Debbar<EMAIL_ADDRESS>a écrit :
@benedicte69 could you share the Dart code you are trying to run?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Without a way to reproduce the issue on our end there is nothing for us to do here. I'm closing the issue for now, but feel free to re-open if you can provide a minimal reproducible-example


Undefined behaviour when capture contains multiple sessions

It doesn’t yet support TeleportService, for example. A new tab in the packet viewer should be opened for each session.

This issue should be resolved now.