regression: global namespace no longer matters

at some point a change was made that breaks code that relies on the global namespace field, i.e. the one provided with the openwhisk constructor.
now, the namespace is either the per-request options.namespace or names.default_namespace(), the latter of which does not pay attention to the global option:
const default_namespace = () => {
  return process.env['__OW_NAMESPACE'] || '_'
}

this breaks our code. luckily we are still pre-production, or this would've been a nightmare.
perhaps this: 9269e96534d5286c69d8dcc9d97043035ad4c897

btw, this was very difficult to debug, because the error reporting from the npm is scant. perhaps have an option to report verbose errors, where the details of the (failed) request are emitted?

That would help. In particular don't swallow the error response from the controller if that happening - the container code would help debug user problems.

I've pushed a fix to remove the regression and published a new version. I've added a unit test to ensure this doesn't happen again.
The precedence order for calculating namespaces is: options.namespace, global_options.namespace, env param, ‘_'.
I agree that we should have a debug property to dump the raw requests & responses. I did open a ticket a while ago to add this.
https://github.com/openwhisk/openwhisk-client-js/issues/15

I found some more edge cases thanks to @starpit and pushed out the fixes.


Let _WD_Window accept unformatted handles

Pull request
Proposed changes
_WD_Window($sSession, "handles") returns an array of handles. This lets _WD_Window accept its own return values directly instead of having to remember to type '{"handle":"' & $aHandles[1] & '"}' each time
Checklist
Put an x in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!
This is simply a reminder of what we are going to look for before merging your code.

[X] I have read and noticed the CODE OF CONDUCT document
[X] I have read and noticed the CONTRIBUTING document
[X] I have added necessary documentation or screenshots (if appropriate)

Types of changes
Please check x the type of change your PR introduces:

[ ] Bugfix (change which fixes an issue)
[X] Feature (change which adds functionality)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (functional, structural)
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
_WD_Window needs formatted handles
What is the new behavior?
_WD_Window attempts to format unformatted handles
Additional context
N/A
System under test
Please complete the following information.

OS: Windows 10
OS Arch.: X64
Browser: Edge
Browser version: 110.0.1587.50

I've left the conditional in the __WD_JsonHandle since it would break scripts that already add {"handle":

little late but...
Should we do the same here:
https://github.com/seadoggie01/WebDriver/blob/26eb680fd85ac83934b2644d2c2d20e8469c41db/wd_core.au3#L590-L594

@mlipok I don't believe this is needed here, but I'd like the hear your reasoning why you believe it is needed.


Tamper Chrome v2 close after reload

Hi there,
I'm new with this extension and I'm trying to intercept requests done when loading a window. After loading page, when F5 (or mouse reload) is done, extension self close, without capturing anything.
Looking at the video provided in your webpage, this is not the behaviour desired, so I don't know if I'm doing something wrong or if Chrome have made any config changes (90.0.4430.93 - Build oficial - Windows 64 bits).
Thanks

I think I was able to reproduce. Are you reloading the window with
TamperDev? Or the main window

I'm reloading window, TamperDev doesn't show any button to reload and, if I press F5 to reload, TamperDev window closes automatically

which window are you reloading?
the window that tamper dev opens, or the window of the website you are using

If I reload on TamperDev window, it closes automatically without reloading browser window.
If I reload on browser window, it also closes TamperDev extension and lost all work done with it

oh ok. I can't reproduce reloading the browser window, but I'll keep
looking into it. =/

@sirdarckcat - I have this issue as well, but first: cool extension!!
Below are the steps to reproduce using Chrome 91.0.4472.77 on Mac OS X 11.4.
There is a 34 second video demonstrating the closing of the extension behavior at the bottom of this comment.

Open Tamper Dev extension, and enable intercept immediately. Note that the extension closes if you refresh page from Chrome initially with intercept not enabled; this is not demonstrated in video.
Refresh page in Chrome - intercepts successfully
Without changing any headers, send request and then send response
Tamper Dev closes, and then bar at top of Chrome closes

See video, uploaded 06/14/2021 (should be good for a year or so): https://www.screencast.com/t/9URPKGw0e

Awesome! Could you please check the console logs? On chrome://extensions
Also, could you try on a "clean" profile? Without other extensions


Configure WLAN from AP mode

Hi, thanks for maintaining this software!
I'm wondering if the cloud binding can be skipped entirely, since my AC, a Midea Portasplit, is discoverable on <IP_ADDRESS> in AP mode.
https://gist.github.com/mweinelt/0addd575269467e8a1ad27b8c4d08fb5
The app would need to configure the WLAN credentials on the device, since otherwise the AC wouldn't be able to pair with the cloud.

Hi there.
That's cool! Never thought to try to querying the device while in AP mode.
I would like to eliminate the cloud component from this library. It still relies on the cloud to determine the token/key pair for the V3 protocol.
As for provisioning the WiFi without the app, any chance you could setup a packet capture?

Sure, just tried onboarding it onto a rather restricted quarantine WLAN I have at home (DNS/NTP DNAT, and only HTTPS outgoing), and it made it join the WLAN. I have a PCAP of when the phone joined the AP of the AC for four seconds, before returning to the previous WLAN.
https://shells.darmstadt.ccc.de/~hexa/portasplit-pairing.pcapng
Unfortunately the only exchange between phone and AC seems to be TLS encrypted.
I then ran discovery, to which it responded once, and for some reason interacted with the cloud. After that it stopped being discoverable, but it remains pingable.
 ./msmart-ng discover -d <IP_ADDRESS>
DEBUG:asyncio:Using selector: EpollSelector
INFO:msmart.cli:Discovering <IP_ADDRESS> on local network.
DEBUG:msmart.discover:Discovery sent to <IP_ADDRESS>:6445.
DEBUG:msmart.discover:Discovery sent to <IP_ADDRESS>:20086.
DEBUG:msmart.discover:Waiting 5 seconds for responses...
DEBUG:msmart.discover:Discovery response from <IP_ADDRESS>: 837000c8200f00005a5a0111b8007a80000000000000000000000000ca6da8dd72ff00000000000000000180000000003eeb02751427b9cf925e5e6f77e3a9131eb4add3f5f71f70ffd1806456d9511e3b825cf56e84f78d5c136eb663484b06c22ca8752eed0e940e8241e605c60e0e4ab5b028b105970803db5c62e6d3613d8321eeb7860067759d3cee1b455e8c267f7f6c5939a7eb7c724f8e7b1eaad44d0bb19369bf0317b24d3a4de9e6a13106b90186fda67f0ca6e7ad4936ac025e8200000000000000000000000000000000
DEBUG:msmart.discover:Decrypted data from <IP_ADDRESS>: ca79a8c02c19000030303030303050303030303030305131414337324444413836444341303030300b6e65745f61635f364443410000bf0302000000000000000000ac000c0200000000ac72dda86dca150067012236000300000000000000000000000000000000000000000018000000000000000000000000
INFO:msmart.cloud:Using Midea cloud server: https://mp-prod.appsmb.com (China: False).
INFO:httpx:HTTP Request: POST https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/v1/user/login/id/get "HTTP/1.1 200 "
DEBUG:msmart.cloud:API response: {"code":"0","msg":"ok","data":{"loginId":"cc19aa32-dfb1-4c12-90b4-94fd05cd"}}
DEBUG:msmart.cloud:Received loginId: cc19aa32-dfb1-4c12-90b4-94fd05cd
DEBUG:msmart.discover:Discovered 1 devices.
INFO:httpx:HTTP Request: POST https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/mj/user/login "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:API response: {"code":0,"msg":"成功","data":{"randomData":"fe119674796878f8b67bd229ff5880b3fcc85e9e20b2fa5e35c1157dbc2969bd","uid":"83947250d2448ffdf02e111c74bad51e","accountId":"1023665078","nickname":"midea","mdata":{"tokenPwdInfo":{"tokenPwd":"8b94ffdde444400eb0029a077c107ee3","expiredDate":1724026286065,"createDate":1721434286065},"userInfo":{"sourceId":"mj_12345","empId":"5456771537545216","address":"","gender":"0","mobile":"midea@mailinator.com","userDeptInfoList":null,"extras":null,"nameEn":null,"employeeNumber":null,"headPhoto":null,"uid":"83947250d2448ffdf02e111c74bad51e","name":"midea<EMAIL_ADDRESS>DEBUG:msmart.cloud:Received accessToken: T1m0w9ju9czk39vn6
DEBUG:msmart.discover:Fetching token and key for udpid 'd51fa7950ef935ac400a7e45cdd2025b' (little).
INFO:httpx:HTTP Request: POST https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/v1/iot/secure/getToken "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:API response: {"code":"0","msg":"ok","data":{"tokenlist":[{"udpId":"d51fa7950ef935ac400a7e45cdd2025b","key":"d69ca01e24b643d6b34eb31bbd7b08e63f92f69c83e9430ea5457377b3c58360","token":"1FB6C9A7FA24EAF7D2DB41741E14327121160D86E5EAE9B31506C90028BA1E8527A91C69728DDE9FABF7FFEB42B66AB37890AD8D6F5420C2646D5D5F0C7FEE6D"}]}}
INFO:msmart.lan:Creating new connection to <IP_ADDRESS>:6444.
DEBUG:msmart.lan:Connected to <IP_ADDRESS>:6444.
INFO:msmart.lan:Authenticating with <IP_ADDRESS>:6444.
DEBUG:msmart.lan:Sending data to <IP_ADDRESS>:6444:<PHONE_NUMBER>0000001fb6c9a7fa24eaf7d2db41741e14327121160d86e5eae9b31506c90028ba1e8527a91c69728dde9fabf7ffeb42b66ab37890ad8d6f5420c2646d5d5f0c7fee6d
DEBUG:msmart.lan:Received data from <IP_ADDRESS>:6444:<PHONE_NUMBER>0fa5a54552524f52
DEBUG:msmart.discover:Fetching token and key for udpid '50e4760c8157626d39458b9d3ddea07b' (big).
INFO:httpx:HTTP Request: POST https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/v1/iot/secure/getToken "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:API response: {"code":"0","msg":"ok","data":{"tokenlist":[{"udpId":"50e4760c8157626d39458b9d3ddea07b","key":"a874f04fc93c406da05e9bf6596ab458f2bc22b656bd4545874fec88f8ed8980","token":"BF050DD1177DDCB38F5EEFA280F5CE4B6C117BA59D99897BB39B68C1E70A59FB157573077AD7738426A30471AED55CA14895DBBF5F03322A02B8E424E432029D"}]}}
INFO:msmart.lan:Authenticating with <IP_ADDRESS>:6444.
DEBUG:msmart.lan:Sending data to <IP_ADDRESS>:6444:<PHONE_NUMBER>000001bf050dd1177ddcb38f5eefa280f5ce4b6c117ba59d99897bb39b68c1e70a59fb157573077ad7738426a30471aed55ca14895dbbf5f03322a02b8e424e432029d
DEBUG:msmart.lan:Received data from <IP_ADDRESS>:6444:<PHONE_NUMBER>0fa5a54552524f52
INFO:msmart.cli:Found 1 devices.
INFO:msmart.cli:Found device:
{'ip': '<IP_ADDRESS>', 'port': 6444, 'id':<PHONE_NUMBER>57514, 'online': False, 'supported': False, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_6DCA', 'sn': '000000P0000000Q1AC72DDA86DCA0000', 'key': None, 'token': None}

Thanks for collecting the capture. I'll take a look.

I then ran discovery, to which it responded once, and for some reason interacted with the cloud. After that it stopped being discoverable, but it remains pingable.

The cloud interaction comes from the library. It's trying to determine the token/key pair necessary for the "V3" protocol. Interesting that your first query of the device used the "V2" protocol.

Oh another thing to keep in mind. If you're totally blocking the device from connecting outside there's a watchdog that will kick and reboot the device.

Took a quick glance at your capture and it does appear you've capture some packets while it was in AP mode. I think they'll have to be decrypted but might be something useful in there.

I'm interested in this too, I have a brand new (to me) portable Midea AC.  Happy to do a packet capture or whatever I can do to assist.  Also,. any idea what the watchdog is looking for? wonder if a simple fake server can be setup just to keep it content.

Also,. any idea what the watchdog is looking for? wonder if a simple fake server can be setup just to keep it content.

I don't exactly. I think I've tried a DNS redirect to a valid host and it needs a little more than that. Haven't investigated any further

I've filtered down the packet capture to what I believe are the provisioning packets
portasplit-pairing-provisioning.zip
Most interesting a No 9 & 10 which I believe are a provisioning command and an ACK.
The decrypted contents dumped as hex and ASCII in 16 byte chunks
ee308e61ebdda41d67a79d2fee7c529f
1664697374727573742e6c6f7373792e
6e6574776f726b0b6368616e67656d65
31323306e6956e41f7a0166469737472
7573742e6c6f7373792e6e6574776f72
6b09010101021444450204010d140024
04170034041401640b1b010304543a00
0004116d6f64756c652e617070736d62
2e636f6d0502bb010601020703020601

b'\xee0\x8ea\xeb\xdd\xa4\x1dg\xa7\x9d/\xee|R\x9f'
b'\x16distrust.lossy.'
b'network\x0bchangeme'
b'123\x06\xe6\x95nA\xf7\xa0\x16distr'
b'ust.lossy.networ'
b'k\t\x01\x01\x01\x02\x14DE\x02\x04\x01\r\x14\x00$'
b'\x04\x17\x004\x04\x14\x01d\x0b\x1b\x01\x03\x04T:\x00'
b'\x00\x04\x11module.appsmb'
b'.com\x05\x02\xbb\x01\x06\x01\x02\x07\x03\x02\x06\x01'

Here's a guess at the contents:

SSID length: 22
SSID: distrust.lossy.network
Password length: 11
Password of changeme123
Country code DE
Sever length: 17
Server: module.appsmb.com
Port: 443

SSID and PSK are correct.

Any chance either of you could perform additional captures while provisioning on networks with different security type. (e.g. None, WPA, WPA2).
It just occurred to me that some part of the provision packet probably includes a security type byte,
Including the MAC address of the network's AP might also be beneficial.

The MAC for the AP in my case was e6:95:6e:41:f7:a0.

Cool cool.
In that case, bytes 16 - 80 probably break down like so
16 - SSID Length = 22
64697374727573742e6c6f7373792e6e6574776f726b - SSID = distrust.lossy.network
0b - PSK Length = 11
6368616e67656d65313233 - PSK = changeme123
06 - Channel? Security Type?
e6956e41f7a0 - AP MAC
16 - SSID Length 2 = 22
64697374727573742e6c6f7373792e6e6574776f726b - SSID 2

Channel 13 (2472 MHz)
20 MHz width
WPA2-PSK

Pairing with an open network:
https://shells.darmstadt.ccc.de/~hexa/midea-portasplit-open.pcapng
config wifi-iface 'radio0_vlan121'
	option ifname 'radio0_vlan121'
	option device 'radio0'
	option network 'vlan121'
	option mode 'ap'
	option ssid 'open.lossy.network'
	option encryption 'none'

phy#0
	Interface radio0_vlan121
		ifindex 15
		wdev 0x3
		addr e6:95:6e:41:f7:a0
		ssid open.lossy.network
		type AP
		channel 9 (2452 MHz), width: 20 MHz, center1: 2452 MHz
		txpower 20.00 dBm

Pairing with a WPA-TKIP network:
https://shells.darmstadt.ccc.de/~hexa/midea-portasplit-wpa-tkip.pcapng
config wifi-iface 'radio0_vlan121'
	option ifname 'radio0_vlan121'
	option device 'radio0'
	option network 'vlan121'
	option mode 'ap'
	option encryption 'psk+tkip'
	option key 'changeme123'
	option ssid 'wpa-tkip.lossy.network'

phy#0
	Interface radio0_vlan121
		ifindex 26
		wdev 0xd
		addr e6:95:6e:41:f7:a0
		ssid wpa-tkip.lossy.network
		type AP
		channel 9 (2452 MHz), width: 20 MHz, center1: 2452 MHz
		txpower 20.00 dBm

I would have tried SAE as well, but the old rooted Android has no support for it. The trick for it to become capturable is to disable Bluetooth, or else it will try to do the setup that way.
The three provided captures are WPA2, Open and WPA.

Thanks.
WPA and WPA2 are nearly identical. Aside from SSID, the only difference is the first 2 bytes.
Open has a zero length PSK (obviously). The first 16 bytes are also different, but after the 2nd SSID field the packet is identical
WPA
Hex View  00 01 02 03 04 05 06 07  08 09 0A 0B 0C 0D 0E 0F

00000000  35 39 8E 61 EB DD A4 1D  67 A7 9D 2F EE 7C 52 9F  59.a....g../.|R.
00000010  16 77 70 61 2D 74 6B 69  70 2E 6C 6F 73 73 79 2E  .wpa-tkip.lossy.
00000020  6E 65 74 77 6F 72 6B 0B  63 68 61 6E 67 65 6D 65  network.changeme
00000030  31 32 33 06 E6 95 6E 41  F7 A0 16 77 70 61 2D 74  123...nA...wpa-t
00000040  6B 69 70 2E 6C 6F 73 73  79 2E 6E 65 74 77 6F 72  kip.lossy.networ
00000050  6B 09 01 01 01 02 14 44  45 02 04 01 0D 14 00 24  k......DE......$
00000060  04 17 00 34 04 14 01 64  0B 1B 01 03 04 54 3A 00  ...4...d.....T:.
00000070  00 04 11 6D 6F 64 75 6C  65 2E 61 70 70 73 6D 62  ...module.appsmb
00000080  2E 63 6F 6D 05 02 BB 01  06 01 02 07 03 02 06 01  .com............

WPA2
Hex View  00 01 02 03 04 05 06 07  08 09 0A 0B 0C 0D 0E 0F

00000000  EE 30 8E 61 EB DD A4 1D  67 A7 9D 2F EE 7C 52 9F  .0.a....g../.|R.
00000010  16 64 69 73 74 72 75 73  74 2E 6C 6F 73 73 79 2E  .distrust.lossy.
00000020  6E 65 74 77 6F 72 6B 0B  63 68 61 6E 67 65 6D 65  network.changeme
00000030  31 32 33 06 E6 95 6E 41  F7 A0 16 64 69 73 74 72  123...nA...distr
00000040  75 73 74 2E 6C 6F 73 73  79 2E 6E 65 74 77 6F 72  ust.lossy.networ
00000050  6B 09 01 01 01 02 14 44  45 02 04 01 0D 14 00 24  k......DE......$
00000060  04 17 00 34 04 14 01 64  0B 1B 01 03 04 54 3A 00  ...4...d.....T:.
00000070  00 04 11 6D 6F 64 75 6C  65 2E 61 70 70 73 6D 62  ...module.appsmb
00000080  2E 63 6F 6D 05 02 BB 01  06 01 02 07 03 02 06 01  .com............

Open
Hex View  00 01 02 03 04 05 06 07  08 09 0A 0B 0C 0D 0E 0F

00000000  9D 4F 6B 64 7B E5 79 F7  49 BF 14 4A 38 39 6D 95  .Okd{.y.I..J89m.
00000010  12 6F 70 65 6E 2E 6C 6F  73 73 79 2E 6E 65 74 77  .open.lossy.netw
00000020  6F 72 6B 00 06 E6 95 6E  41 F7 A0 12 6F 70 65 6E  ork....nA...open
00000030  2E 6C 6F 73 73 79 2E 6E  65 74 77 6F 72 6B 09 01  .lossy.network..
00000040  01 01 02 14 44 45 02 04  01 0D 14 00 24 04 17 00  ....DE......$...
00000050  34 04 14 01 64 0B 1B 01  03 04 54 3A 00 00 04 11  4...d.....T:....
00000060  6D 6F 64 75 6C 65 2E 61  70 70 73 6D 62 2E 63 6F  module.appsmb.co
00000070  6D 05 02 BB 01 06 01 02  07 03 02 06 01           m............

Open w/ zero padding to match WPA length
Hex View  00 01 02 03 04 05 06 07  08 09 0A 0B 0C 0D 0E 0F

00000000  9D 4F 6B 64 7B E5 79 F7  49 BF 14 4A 38 39 6D 95  .Okd{.y.I..J89m.
00000010  12 00 00 00 00 6F 70 65  6E 2E 6C 6F 73 73 79 2E  .....open.lossy.
00000020  6E 65 74 77 6F 72 6B 00  00 00 00 00 00 00 00 00  network.........
00000030  00 00 00 06 E6 95 6E 41  F7 A0 12 00 00 00 00 6F  ......nA.......o
00000040  70 65 6E 2E 6C 6F 73 73  79 2E 6E 65 74 77 6F 72  pen.lossy.networ
00000050  6B 09 01 01 01 02 14 44  45 02 04 01 0D 14 00 24  k......DE......$
00000060  04 17 00 34 04 14 01 64  0B 1B 01 03 04 54 3A 00  ...4...d.....T:.
00000070  00 04 11 6D 6F 64 75 6C  65 2E 61 70 70 73 6D 62  ...module.appsmb
00000080  2E 63 6F 6D 05 02 BB 01  06 01 02 07 03 02 06 01  .com............


Added warning message for unsupported ffmpeg version

Resolves https://github.com/pytorch/vision/issues/4022.

Hey @datumbox, @prabhat00155!
You approved or merged this PR, but no labels were added.

@NicolasHug, @datumbox , @fmassa  I see labels in this PR, what is this talking about?

You need to put one of the "module" labels or bug/improvement/new feature, etc. I think we should document the process a bit better because I understand now it's a bit confusing. :)

You need to put one of the "module" labels or bug/improvement/new feature, etc. I think we should document the process a bit better because I understand now it's a bit confusing. :)

Okay, thank you!


[New Game]: Aim Training Game

Aim training game is a simple and addictive game where the player's objective is to pop as many bubbles as possible within a limited time. Colorful bubbles randomly appear on the screen, and the player must quickly click on them to pop them. Each popped bubble earns the player a point, and the score is displayed in real-time. The game lasts for 30 seconds.

Closing this as exists #2341


Improve animation synchronization

The way animation timing is synchronized right now is subject to some error due to network latencies. It also has a weak point where it relies on a peer's response, which could fail. This should be improved.

This should be redone to match the soundinstance synchronization pattern

#239 should be completed before this work is completed, as animation needs the same abilities as sound.


fix: Change asynchronous dependencies for tox

Noticed WARNINGS in Travis CI output:
WARNING:test command found but not installed in testenv
Looks like the test environments expected to use requirements-test.txt
with one extra package, gevent. Tests should be able to run without
issues.

Coverage remained the same at 94.318% when pulling ed501dde6f10eb3684456546d234b4236d2dae39 on e4r7hbug:fix/tox into 91cf58beb45a877322b2fe9453258a885ea4f043 on daniellawrence:master.

Good pickup :+1:

:yum:


Color property for floating title

I have looked into documentation and code but wasn't able to find the parameter for this property :
Floating title text color when text box is not focused.
I've tried to change all the color properties, but it will always stays dark gray color.
Anyone can help me changing it?

Same for me :/ it is not changing from Interface builder nor programmatically

The property you have to set is called
titleColor


CDE-66 Preview missing functionalities

Issue #CDE-66
Problem: Preview missing functionalities
Solution:
Fix chip ui misalignment, add icon functionality
https://github.com/MetaCell/cde-mapper/assets/67194168/6d3b30ae-f8b5-416e-b652-9abd2e33df98

Sorry @afonsobspinto I don't see any misalignment between table and chips, like even the parent box of each chip has fixed height

@Aiga115 I still see the misalignment. I'm adding @ddelpiano as reviewer to see what he experiences.


if nearest points needed immediately after adding new points?

Hello everyone,
i was wondering if there is a more efficient way in this case?
The moment after adding new points into graph, i need the top k( less than m and ef)  nearest neighbors for exactly these new points before adding other new points.
in short, i need the knn of these points immediately after adding them.
It seems natural to add_items first and then knn_query.
However, i think  searchBaseLayer  when building graph does similar things in knn_query.
In the code, top_candidates are sorted by distance before doing heuristic select. I print several  top k elements in top_candidates when adding new points and they are equal with the results doing knn_query.
I mean will the immediate queried nearest points have some connection with the points stored in top candidates? I have a feeling that it has... if so, will it be more efficient to get top k directly from top_candidates than querying them later?
Any help would be greatly appreciated.

Hi @qumingzhentmnan,
Yes, it would be more efficient to extract them from the searchBaseLayer before the heuristic.
Probably the difference compared to additional querying is not that big, since you the removed edges by the heuristic should be easily retrieved (compared to a search for a different element, e.g. random). But this is an unnecessary  overhead.

Thank you for your reply!
Let me see if I understand you correctly. You mean i can get k nearest elements before heuristic without extra knn_query ?
After i submitted this issue, i further test this on 10M dataset. However, comparing to knn_query results, the results in top_candidates(before heuristic) are less accurate and miss several nearer points.  It puzzles me.
As i modify your code a little bit, maybe i made some mistake during modification.
So, i want to make sure it theoretically correct to omit knn_query.
Many thanks,

Hi @qumingzhentmnan,
Yes, the accuracy should be very similar (on average). There might be some subtile factors, but even if there is a slight performance difference it should be negated by slightly altering ef_construntion.
If the difference is large that should be investigated, it should not be so.

Thank you so much for your reply!
Yes, you are right!
Maybe it is because i set ef two times lager than ef_constrction, and misses some points in top_candidates doing add_items. I get same result after setting ef_constrction = ef =200 (vector dim = 512).
Well, at first, i hope to get knn directly so to save time spent on knn_query. However, it seems that i have to set larger ef_constrction to get same results, leading more time on building index.
I don't know whether to laugh or cry for this result. I may go deeper to find out how much time can be saved if getting it directly with larger ef_constrction. I hope for improvement as it seems to need more modification....
In your opinion, which could be faster, larger ef_constrction and extract knn directly with no knn_query part or ef_constrction smaller than ef with extra knn_query?
What’s more, I am quite new to C++, if possible, can you give me some advice on how to get elements in top_candidates and return them to python elegantly? A temporary priority_queue, like the one in searchKnn ? if so ,gonna to change the type of function addPoint, seems a lot work.
Many thanks!

@qumingzhentmnan Sorry for a late reply. I can help with C++ instructions when needed.
Changing the type of addPoint should not be that hard. You can add a reference to a queue as an additional argument and copy to the nearest neighbors. This is a bit messy, but in case it is just a hack should not take too much time.
I think that larger ef_construction is better, but this is only a hypothesis.

Thank you for your reply!
I further tested ef_con =200 for 1m data.
it took 40% longer  doing add_items comparing ef_con=100 for every new point, with slightly difference in knn_query.
As index building time are greatly concerned and with no comparision of recall, the second option, ef_con smaller than ef with extra knn_query seems faster than larger ef_con .
Again, thanks for your great work.
Ps:  data =1M, random data

I see. Thanks for reporting!


Add shortcut to arweave.app

Adds a hyperlink from address in header and menu to open arweave.app

This one is good, but you can't currently sign in with arweave.app. It's not to a point where it actually works for dApps. Let's hang onto this one until the arweave.app integration is working.

Possibly swap it with a https://viewblock.io link instead?
e.g. https://viewblock.io/arweave/address/89tR0-C1m3_sCWCoVCChg4gFYKdiH5_ZDyZpdJ2DDRw

🍻


pidgin: put packages in a different scope

Description of changes
Moved pidgin plugins to its own scope like how it works with python and many others.
Basically I exposed the scope through pidgin passthru like how it works with python3.pkgs and then added aliases for pidgin and pidginPackages and the original packages so existent configs should not break, also added a withPlugins that works basically the same as python3.withPackages.
I also added myself as a maintainer.
It might cache miss because I worked in the dependency orders for buildInputs for example.
NOTE: scope work might be wrong, this is my first attempt doing something like this

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 243679 run on x86_64-linux 1

3 packages built:

chatty
pidgin
telepathy-haze

HMMM nice catch
I was assuming that pkgs would get the scope + the global scope as a fallback

Result of nixpkgs-review pr 243679 run on x86_64-linux 1

1 package marked as broken and skipped:

pidginPackages.tdlib-purple

27 packages built:

chatty
pidgin
pidginPackages.pidgin-carbons
pidginPackages.pidgin-indicator
pidginPackages.pidgin-latex
pidginPackages.pidgin-mra
pidginPackages.pidgin-msn-pecan
pidginPackages.pidgin-opensteamworks
pidginPackages.pidgin-osd
pidginPackages.pidgin-otr
pidginPackages.pidgin-sipe
pidginPackages.pidgin-skypeweb
pidginPackages.pidgin-window-merge
pidginPackages.pidgin-xmpp-receipts
pidginPackages.purple-discord
pidginPackages.purple-facebook
pidginPackages.purple-googlechat
pidginPackages.purple-hangouts
pidginPackages.purple-lurch
pidginPackages.purple-matrix
pidginPackages.purple-mm-sms
pidginPackages.purple-plugin-pack
pidginPackages.purple-signald
pidginPackages.purple-slack
pidginPackages.purple-vk-plugin
pidginPackages.purple-xmpp-http-upload
telepathy-haze


Fix typo

@ryanguest thanks for your patience at first, but #13 already fix it , I'm sorry for that 😞,
but I still wanna give a big appreciation for your time on it, thank you and cheers 😄.


cmd/link: occasional failures with "unreachable sym in relocation" since 2021-09-12

greplogs --dashboard -md -l -e ': unreachable sym in relocation: '
2021-11-22T23:00:32-0244343/freebsd-amd64-13_0
2021-11-19T21:57:03-6027b21/freebsd-amd64-13_0
2021-11-16T19:18:26-8122e49-6c36c33/freebsd-amd64-12_2
2021-09-12T01:06:53-0d8a4bf/linux-riscv64-unmatched
CC @cherrymui @thanm

Not really sure what to do with this bug, given the failure mode. Normally I would lease a builder and run some test or set of tests in a loop to try to reproduce -- in this case, even if I were able to reproduce it a few times, what then?  I don't see any commonality in terms of the symbols that are suddenly being switched from reachable to unreachable.

Maybe it is due to memory corruption somewhere?

“possible memory corruption on FreeBSD” is #46272, open since May. 😩
Still, it seems odd to me that this particular failure mode doesn't show up in the logs until recently. Maybe the memory corruption has a non-trivial interaction with the 1.18 GC changes? (Perhaps the corruption is triggered by having the GC active during some step of the linking process?)

Just out of curiosity, how far back does "greplogs" go? What's the oldest log that it will fetch?

Depends on what you've downloaded with fetchlogs. (It looks like my semi-arbitrary database for the main repo currently goes back to 2019-06-06.)

Checking on this as a release blocker. Are there any updates? @thanm

Still look like memory corruption. Seems no new failure occurred since 11-22. Haven't tried to reproduce.

I kicked off a goswarm on freebsd-amd64-12_2 this morning trying to reproduce the issue. I'll leave it running for a day or two and see if that catches any new instances of the bug. I tried to do something similar for an AMD-specific VM (e.g. netbsd-amd64-9_0-n2d) but all.bash crashes almost immediately there (most of the time doesn't make it past the bootstrap).

OK, it took a while, but the swarm I started this morning did find a new instance of this problem on tip with freebsd-amd64-12_2 just now, so it definitely looks like this bug is alive and kicking.

Related: https://github.com/golang/go/issues/46272#issuecomment-991981762. I will retest this bug once we have an updated version of FreeBsd on our builders with the fix.

I ran a goswarm test (using the updated freebsd-amd64-13_0 builder image to include the fix) and did not detect any new failures over the course of a 40 hour run with 10 gomotes, so I am going to go ahead and close out this bug. See #46272 for more details on the kernel problem and the fix.


Toolbar opening delay

While I was working and going around the Plone site I found that clicking to toolbar button loads toolbar but with transition of 0.3s which could be good if it would be visible to user but, instead of that it can be seen it opens with delay of 0.3s which creates confusion for a while whether user clicked the button or not making it annoying. These tools on homepage are very frequent to use and shouldn't have trasition effects for more smooth and fast navigation across website.

Solution:
Remove transition or add another kind of transition for more visual and fast navigation.
https://github.com/plone/volto/assets/114601400/70ac7745-8ecf-4396-a259-b243ebb6e91c
When navigating around website this feature becomes annoying to use and leads to double click and that also closes the toolbar.... making user kind of frustrating (I faced this issue while navigating around website).

can you assign this to me?

@AKA717 please read and follow Contributing to Plone and First-time contributors, especially Things not to do.

@singhcoder694 before doing any work on this issue, please read and follow Item 2 in Work with GitHub issues.
I see you already created a pull request with your proposed fix, but in the future to avoid extra work, it is a good idea to discuss and determine what, if anything, needs to be done before you do any work.

Sorry for that it won't happen again and thank you for the valuable
guidance.
On Fri, 19 Jan, 2024, 17:35 Steve Piercy, @.***> wrote:

@singhcoder694 https://github.com/singhcoder694 before doing any work
on this issue, please read and follow Item 2 in Work with GitHub issues
https://6.docs.plone.org/contributing/first-time.html#work-with-github-issues
.
I see you already created a pull request with your proposed fix, but in
the future to avoid extra work, it is a good idea to discuss and determine
what, if anything, needs to be done before you do any work.
—
Reply to this email directly, view it on GitHub
https://github.com/plone/volto/issues/5657#issuecomment-1900295495, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MZ47HVTHTAHUPYGWYU33LYPJOO7AVCNFSM6AAAAABCAJOHTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBQGI4TKNBZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@stevepiercy got it and joined groups, thankyou for informing about this. From next time I would discuss and create issues if required...

@singhcoder694 as a newcomer trying to get your first contribution in please read the docs carefully.
https://6.docs.plone.org/contributing/first-time.html#work-with-github-issues
"2. Discuss whether you should perform any work"
Before trying to work on an issue that you think you found, open the issue first and see if there is any consensus
in fixing that issue.
Sometimes what can appear as a bug for you could be a feature that works as intended.
In order to avoid extra work that has a low chance of getting merged, consider raising the issue first and waiting to
work on it until you get some feedback from the community.
For instance your perceived delay is a transition added on the dropdowns to have a smooth opening and closing
effect rather than the hard show and hide.
There are some instance where you want to avoid transitions in which case it would be handled within a media
query prefers-reduced-motion but if that is the route it needs to be approved and changed in other places as well.
I am closing this issue, if you really want to contribute to this project then consider this advice:
Want to work on something?
Start with something easy first, an issue that has the easy label
41 lvl: easy

Want to help?
Look at the tickets where help is asked as long as you have the knowledge to help
31 needs: help


[backport] Add a workaround for ROCm 4.3.0 for testing

Backport of #5662 by @takagi

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit a5647bd2c50094e18d78aa3be00c835a4643fa1c, target branch v9) succeeded!


EXPERIMENTAL: GH-40686: [C++] Add MemoryPool API to resize without copying the data

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@felipecrv Just so that you understand better what I have in mind.

@felipecrv Just so that you understand better what I have in mind.

Right. But now I'm curious for the motivating use-cases.
One abstract case I have in mind i dynamically-growing containers: let's say I'm appending a value to a container and size==capacity already, Reallocate(capacity+1) is wasteful (better to grow capacity geometrically), but if I can resize to capacity+1 in-place, that's preferrable.

Right. But now I'm curious for the motivating use-cases.

It's explained in the issue description.

For reference, here are the micro-benchmark results on my machine. But bear in mind that evaluating the actual usefulness of this first requires plugging it into existing code (such as a Parquet decoder):
-------------------------------------------------------------------------------------------------
Benchmark                                       Time             CPU   Iterations UserCounters...
-------------------------------------------------------------------------------------------------
ReallocateGrowing<SystemAlloc>             259625 ns       259558 ns         2697 items_per_second=246.573k/s percent_in_place=0
ReallocateGrowingNoCopy<SystemAlloc>         6024 ns         6023 ns       119303 items_per_second=10.6263M/s percent_in_place=75
ReallocateGrowing<Jemalloc>                  9389 ns         9387 ns        74572 items_per_second=6.81772M/s percent_in_place=93.75
ReallocateGrowingNoCopy<Jemalloc>            5572 ns         5571 ns       125529 items_per_second=11.4872M/s percent_in_place=93.75
ReallocateGrowing<Mimalloc>                 71605 ns        71591 ns         9742 items_per_second=893.964k/s percent_in_place=54.6875
ReallocateGrowingNoCopy<Mimalloc>           10113 ns        10112 ns        69571 items_per_second=6.32909M/s percent_in_place=78.125

ReallocateShrinking<SystemAlloc>           203288 ns       203237 ns         5293 items_per_second=314.904k/s percent_in_place=0
ReallocateShrinkingNoCopy<SystemAlloc>       6659 ns         6658 ns       105071 items_per_second=9.61302M/s percent_in_place=73.4375
ReallocateShrinking<Jemalloc>                9691 ns         9689 ns        71743 items_per_second=6.60514M/s percent_in_place=93.75
ReallocateShrinkingNoCopy<Jemalloc>          6433 ns         6253 ns       114823 items_per_second=10.2355M/s percent_in_place=98.4375
ReallocateShrinking<Mimalloc>                5895 ns         5894 ns       118059 items_per_second=10.858M/s percent_in_place=89.0625
ReallocateShrinkingNoCopy<Mimalloc>          2047 ns         2046 ns       341842 items_per_second=31.2752M/s percent_in_place=98.4375

Benchmark results are encouraging except for jemalloc which needs more massaging to fully exploit (see comments in the source):
-------------------------------------------------------------------------------------------------
Benchmark                                       Time             CPU   Iterations UserCounters...
-------------------------------------------------------------------------------------------------
ReallocateGrowing<SystemAlloc>             267140 ns       267082 ns         2620 items_per_second=239.627k/s percent_in_place=0
ReallocateGrowingNoCopy<SystemAlloc>         6271 ns         6270 ns       111590 items_per_second=10.2078M/s percent_in_place=75
ReallocateGrowing<Jemalloc>                  9133 ns         9132 ns        76586 items_per_second=7.00834M/s percent_in_place=93.75
ReallocateGrowingNoCopy<Jemalloc>           23503 ns        23500 ns        29719 items_per_second=2.72346M/s percent_in_place=26.0635
ReallocateGrowing<Mimalloc>                 72325 ns        72311 ns         9674 items_per_second=885.071k/s percent_in_place=54.6875
ReallocateGrowingNoCopy<Mimalloc>           10122 ns        10120 ns        69251 items_per_second=6.32395M/s percent_in_place=78.125

ReallocateShrinking<SystemAlloc>           206661 ns       206608 ns         5258 items_per_second=309.765k/s percent_in_place=0
ReallocateShrinkingNoCopy<SystemAlloc>       6571 ns         6570 ns       106790 items_per_second=9.74056M/s percent_in_place=73.4375
ReallocateShrinking<Jemalloc>                9396 ns         9394 ns        74619 items_per_second=6.81305M/s percent_in_place=93.75
ReallocateShrinkingNoCopy<Jemalloc>         23662 ns        23658 ns        29572 items_per_second=2.70523M/s percent_in_place=26.0422
ReallocateShrinking<Mimalloc>                5882 ns         5881 ns       119515 items_per_second=10.8828M/s percent_in_place=89.0625
ReallocateShrinkingNoCopy<Mimalloc>          2064 ns         2064 ns       339045 items_per_second=31.0091M/s percent_in_place=98.4375

For the record, this is very much work-in-progress and the real usefulness of this will be judged once it is plugged in existing functionality (for example some Parquet reader or decoder facility).


Add $(broadcaster) variable

Should $(streamer) be an alias for $(broadcaster)? I think not but I'm open to opinions
Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[x] Documentation in docs/ or install-docs/ was updated, if applicable

Fixes #925

Should $(streamer) be an alias for $(broadcaster)?

No, it should be semi-consistent with how the variable currently functions ($(tb:broadcaster), not $(tb:streamer))


RFE: No directory should be created when 'fn init' fails

fn init xxx --runtime yyy will fails because the 'yyy' runtime doesn't exist but still, an empty 'xxx' dir will be created.

I'd like to pick this one up.
Reproduced on current master below:
$ ~/projects/go_workspace/src/github.com/fnproject/cli/fn init xxx --runtime yyy
Creating function at: /xxx
Runtime: yyy
Init does not support the yyy runtime, you'll have to create your own Dockerfile for this function.
ERROR: could not detect entrypoint or cmd for yyy, use --entrypoint and/or --cmd to set them explicitly
$ ls
xxx/

Fix just needs some review at https://github.com/fnproject/cli/pull/129

Fix is merged. Just need someone to close this issue since the PR didn't do it.


Add alerts to choreo

Replaces DriverStation.reportWarning/reportError calls with wpilib's alerts api.
Fixes #996.

I don't think a C++ port is needed since it doesn't have the "auto" API.

I don't think a C++ port is needed since it doesn't have the "auto" API.

There are still DriverStation.reportError usages though in the Choreo class; not sure if thats needed

There are still DriverStation.reportError usages though in the Choreo class; not sure if thats needed

I think your branch is out of date, because grep doesn't show any instances of DriverStation in the C++ API.


New remote local flow demo

This is some PR

This should be merged soon

Done

Done

accepted pull request.


Reformulate nonlinear constraints correctly for CHR

Manually replaces nonlinear constraints in model with changed constraints when applying convex hull reformulation.
Ensures that a model is given at least two constraints.

fork needs to be rebased


How to use 1.3B OPT weights in metaseq-api-local API?

I'm trying to use 1.3B OPT weights in metaseq-api-local API and test some inference examples. But I got stucked.
There are two reshard files of 1.3B OPT. But CHECKPOINT_LOCAL in constants.py can only point to a reshard.pt file. What is the correct way to load these two reshard files? (P.S. the comments in constants.py  says MODEL_SHARED_FOLDER = "/example/175B/reshard_no_os" but there is CHECKPOINT_FOLDER = os.path.join(MODEL_SHARED_FOLDER, "175B", "reshard_no_os") in line 49, is this also a mistake?

You can modify the paths manually to load different models. Also, I think this script is related.

@soloice I know that we can modify path to load different models. My question is CHECKPOINT_LOCAL can only point to a ckpt file but not a list of reshard file.

I have the same question. I assume this is not a bug: the only thing missing here is a script to merge all sharded checkpoints.

I guess there is a way to direct load two reshard file (and infer under the strategy of model paralleling) rather than merging them.

Consolidating all asks for model loading into https://github.com/facebookresearch/metaseq/issues/88, which will be released soon from HuggingFace.
We also have https://github.com/facebookresearch/metaseq/issues/78 and https://github.com/facebookresearch/metaseq/issues/77 open to fix some of these usability issues on our end.


Add CategoryFilter

Hi, devs! I want to suggest CategoryFilter for admin. I found it useful for my project. And maybe it will useful for others:
class CategoryFilter(admin.SimpleListFilter):
    title = _('Category')
    parameter_name = 'category'

    def lookups(self, request, model_admin):
        limit_choices_to = {'publisher_is_draft': False, 'application_urls': 'ProductsListApp'}
        queryset = Page.objects.filter(**limit_choices_to)
        return [(page.id, page.get_title()) for page in queryset]

    def queryset(self, request, queryset):
        if self.value():
            return queryset.filter(cms_pages__id=self.value())

@admin.register(Product)
class ProductAdmin(SortableAdminMixin, CMSPageAsCategoryMixin, models.ModelAdmin):
    list_filter = (CategoryFilter, )

This code may be put to shop/admin/product.py
P. S. The title CategoryFilter may be incorrect title for universial shop. I don't know how should call more correct title..

Thanks
How about naming it something like CMSPageFilter?
In my opinion it fits better to the terminology

I am agree. Product has field "cms_pages" then name CMSPageFilter is more fit for filter.

Thanks for the hint. A CMSPageFilter  will be added in version 0.9.2.


[Opinion] Migrate to docker compose file version 3 and without extends, to support swarm deployment.

I thing it would be nice if the copier template is compatible with docker swarm out of the box.
Currently docker swarm requires a compose file of version 3.0 or higher, and it also doesn't support the extends key.

This never happened before because we didn't have a proper templating tool as we do today. It would be nice indeed.

This never happened before because we didn't have a proper templating tool as we do today. It would be nice indeed.

Hi @Yajo , I started working on this, by using macros.
For example, this macro is for volumes:
{%- macro common_yaml_odoo_volumes() %}
    volumes:
      - filestore:/var/lib/odoo:z
{%- endmacro %}```
, I started working on this, by using macros.
For example, this macro is for volumes:

{%- macro common_yaml_odoo_volumes() %}
volumes:
- filestore:/var/lib/odoo:z
{%- endmacro %}```
Then I use it in `common.yaml` like this:

services:
odoo:
...
{{ macros.common_yaml_odoo_volumes() }}
I plan to make a macro for every key like `volumes` and then use it in `devel.yaml`, `prod.yaml` and `test.yaml`.
Am I going in the right direction?```
Then I use it in `common.yaml` like this:

services:
odoo:
...
{{ macros.common_yaml_odoo_volumes() }}
I plan to make a macro for every key like `volumes` and then use it in `devel.yaml`, `prod.yaml` and `test.yaml`.
Am I going in the right direction?

It seems some of your macros broke your comment 😋
For what I can understand, if I were to use macros, I think common.yaml would disappear. For the rest, I guess you're right.

I've kind of done this, although not using copier. In then end using a .env file like the old scaffolding just made more sense for the compose files.
I'd recommend having common.yaml -> docker-compose.yml, in .gitignore ignore docker-compose.override.yml and unignore docker-compose.yml, then just have 3 override files, linking for each environment. invoke develop then just links the test override file to be docker-compose.override.yml

It could be an option too. Although given Copier can generate any files and repeat any code comfortably, maybe the best would be to just generate those 3 environments completely and statically, allowing freedom for further overrides if needed.


fix duplicated dcterms:description predicate

Even though syntactically correct, most software will only honor either the first or last occurrence

Can one of the admins verify this patch?


forge test --debug uses huge amounts of memory for complex tests, spilling into swapfile and causing kernel to kill the task (macOS)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (7545c7a 2024-03-12T00:17:55.654014000Z)
What command(s) is the bug in?
forge test --debug
Operating System
macOS (Apple Silicon)
Describe the bug
The Forge debugger uses huge amounts of RAM, which macOS has no problem compressing, for what it's worth, but it still spills over into swapfile.
Having poked around the debugger and having a vague understanding of its mechanisms, I believe this is because the entire test is executed first, and the VM's state at each step during execution is saved. Intuition tells me this might also include sourcemaps, etc (perhaps tests should make more use of references vs clones/copying, if they aren't? not my wheelhouse).

Problems arise when the swapfile grows large enough that the kernel decides it's "too big" (in my case, with 500+GB free, ~41GB, when OS-reported memory usage of forge is ~384GB) and kills the process.
Repro:
Clone this repo: https://github.com/ProjectOpenSea/seaport-1.6/tree/4240dc6b30fa73f4b6b437fb588ebe583e796e3a
Edit this file: https://github.com/ProjectOpenSea/seaport-1.6/blob/main/test/foundry/new/FuzzMain.t.sol#L42
Change xtest_concrete to the following:
function test_concrete2() public {
        (
            uint256 seed,
            uint256 orders,
            uint256 maxOfferItemsPerOrder,
            uint256 maxConsiderationItemsPerOrder
        ) = (
            3,
            1,
<PHONE_NUMBER>8132815718688868832803618110488078917419162154611084291530410,
            10
        );
        bytes memory callData = abi.encodeCall(
            this.test_fuzz_generateOrders,
            (seed, orders, maxOfferItemsPerOrder, maxConsiderationItemsPerOrder)
        );
        (bool success, bytes memory result) = address(this).call(callData);
        if (!success) {
            if (result.length == 0) revert();
            assembly {
                revert(add(0x20, result), mload(result))
            }
        }
    }

Run the following: forge test -vvv --debug test_concrete2

#7383 and #7385 only target the debugger
I tried running this forge test -vvv --debug test_concrete2
but it never entered the debugger because it failed
 Error: Mutation UnusedItemParameters_Token did not revert with the expected reason
  Error: a == b not satisfied [bytes]
        Left: 0x8baa579f
       Right: 0x6ab37ce7

though I saw it spike to > 100GB, so I think the issue is related to fuzzing.
will investigate a bit more

@mattsse failure is expected – the debugger wouldn't be much use if you could only debug tests that pass. It's also not a fuzz test, so if Forge is fuzzing things, it shouldn't be.
Building latest master, will give that a shot!

@emo-eth I think I found the issue, it was indeed debug info collecting I believe.
could you please try main?
it's down to 15GB on my machine when it launches the debugger, with a few more fixes I think we should be able to improve this a lot more

thanks!
I'll close this and track followups separately.


[C++] Extend hash-join unit tests to cover both empty and length=0 batches

Follow-up to ARROW-15938 so that we can merge ARROW-15938 for the RC.  This just adds the unit test requested in the review.
Reporter: Weston Pace / @westonpace
Note: This issue was originally created as ARROW-17226. Please see the migration documentation for further details.

@westonpace is this still required or can be closed? As I can see the reference ticket was delivered already.

I believe this can be closed.


Help with passing string to imported function

I have a function that takes a string param, like this:
uint32_t font_measure(uint32_t fontID, char* text);

That I am trying to expose, like this:
static web49_interp_data_t wasi_import_font_measure(void* wasi_untyped, web49_interp_t interp) {
  uint32_t fontID = interp.locals[0].i32_u;
  uint32_t textPtr = interp.locals[1].i32_u;
  char text[512];
  memcpy(text, WEB49_INTERP_ADDR(void *, interp, textPtr, 512), 512);
  return (web49_interp_data_t){.i32_u = font_measure(fontID, text)};
}

This works, but seems like the wrong way to me (using max-length of 512 to pull the whole thing.) Is this the right way to pull the string? Is there a better way to get the string-length up-front? Should I rewrite all functions that take string params to include length param, too?

char * by definition has no builtin length, if you want a length you can either pass one or do pascal-style strings. WASM strings are kinda a mess right now.

Yeh, for sure. I see that WASI includes length on all of their string-param functions, but I can generally get by with /0-delimited strings, elsewhere. I was hoping to not have to change my import ABI, but that makes sense.

I would put the length first, but yea that would work. Also strlen if you null terminate.

WASM doesn't segment memory at all, you get a buffer. you can ever write to NULL 😨... I'm gonna close this issue in a bit unless there's anything else relevant.

So it would look like this?
len = strlen(WEB49_INTERP_ADDR(void *, interp, textPtr, MAX_STRING_SIZE));

Ah, sorry, nevermind, just saw this:
size_t memlen = strlen(wasi->argv[i]) + 1;
memcpy(WEB49_INTERP_ADDR(void *, interp, head2, memlen), wasi->argv[i], memlen);

Thanks!


Feature request: initializing an Estimator without training

Would it be possible to implement a method in Estimator to initialize the variables in the model? For example, it would then be possible to use predict before using train what is not possible actually. In some cases, the lack of this method could be very inconvenient.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 45 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 16 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


Divide by zero error

It is possible for a token counter to return zero tokens, leading to a division by zero error in the merge_splits function:
  File "C:\Users\user\miniconda3\envs\project\Lib\site-packages\semchunk\semchunk.py", line 78, in merge_splits
    average = cumulative_lengths[midpoint] / tokens if cumulative_lengths[midpoint] else average
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
ZeroDivisionError: division by zero

Thanks for this! This bug is now fixed in v0.3.2 :)


What is the Default value of containerConcurrency in Inference Service

/kind feature
Need help with understanding the default value for container concurrency value. If I will not specify any value, will 1 be taken as concurrency value?
Thanks.
apiVersion: "serving.kserve.io/v1beta1" kind: "InferenceService" metadata:   name: "flowers-sample" spec:   predictor:     containerConcurrency: 10     model:       modelFormat:         name: tensorflow       storageUri: "gs://kfserving-examples/models/tensorflow/flowers"

Hi @sidharthkumarpradhan , as far as I know the default containerConcurrency for KServe ISVC is 0, which is no limit, you can verify it by checking the knative resources service.serving.knative.dev.

The default container concurrency is depends on the knative configuration.
/close


⚠ Bofrost.at has degraded performance

In 4ad98c9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 867 ms

Resolved: Bofrost.at performance has improved in 7c089c8.


Update listener methods in ClientGgp

Some of the listener methods implemented in ClientGgp had some differences compared to the ones in OrbitApp, given by recent updates on them. They have been reviewed and updated.

Merging this, thanks!


Disable everything but SSL

Environment

OS: Ubuntu 14
Erlang/OTP: 19
EMQ: 2.2

Description
I need to disable web socket access, tcp, wss, and api. The only thing I want to allow access through is ssl. Is there any way to do that in the configuration, or is the only way to modify the source in emqttd_app and prevent the listeners from being started?
For that matter, is there an easy way to disable all of the built in authentication plugins without breaking everything? I would just like to use the mysql authentication and dont need the rest, when I delete them from the makefile and relx.config i get errors so there should be an easier way i think.
Thank you,

@rauger

Remove or comment the 'listener' configuration items in etc/emq.conf to disable a listener.
Just enable the emq_auth_mysql plugin.

@emqplus
Environment

OS: Windows Server 2016
Erlang/OTP: I install the latest version(10.1.2020)
EMQ: 3.4.5

Description
Hi, my scenario is different, I just want SSL connection, is there had any better way to disable web socket access, tcp, wss, and api, instead of remove or comment the 'listener' configuration items in etc/emq.conf to disable a listener.
Thank you


🐛 Fix shells for docs

Docs are derivations in derivations, not derivations in components so
they are missed by collectComponentsRecursive nad did not get any
shells. Now we add on shells for them specifically and add a warning
that the docs shell itself it not valid since it's just the
symlinkJoin without anything useful.
Fixes #281

A little strange that we give certain targets a special meaning. I.e. this logic would not be true if I created a component with mkComponent and then just happened to name a target docs that was a derivation, I would not be able to get a shell for it.

But I also see that we have already committed to aforementioned special-casing in component.nix so ignore what I said...

But I also see that we have already committed to aforementioned special-casing in component.nix so ignore what I said...

Yeah. We could do something like tagging everything created with the base.documentation funcitons (and add a base.documentation.includeInCombinedDocs function to tag custom derivations), and then do all the special stuff with everything in the component that has the tag. Then it wouldn't matter where in the component they were so it would be a bit flatter.
But that would be a bit bigger effort (and major version update) so maybe this can work in the meanwhile.

Couldn't the shells for sub-derivations be handled with passthru?


Add remaining 8.xx

8.00, 8.01, and 8.03 offsets all appear to be the same
8.52 appears to match 8.50
9.51 appears to match 9.50/9.60

Untested, just happened to have 99% off the offsets from other stuff

@Al-Azif Awesome! Was going to begin working on FW 8.00. Thank you so much for your contribution!

Any reason why @kmeps4 opened up a new PR, without putting me as a co-author even, rather than just confirming this commit works? As now this PR is in conflict.

Any reason why @kmeps4 opened up a new PR, without putting me as a co-author even, rather than just confirming this commit works? As now this PR is in conflict.

Sorry Azif but I also fixed some typo you had on the stage1 and stage2 and one bad offset as oxf0xf typo also... I didn't saw any issues doing a PR with the fixes.. credits are all yours!!!

Normally you'd commit to my branch and co-authoring is done like this https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors. I'm mentioned in the PR title

A strategic mistake I see here 🫠

Well this PR matches the repo now, just with some semblance of proper credit

Any reason why @kmeps4 opened up a new PR, without putting me as a co-author even, rather than just confirming this commit works? As now this PR is in conflict.

Dam lol


Flag to reference external documents.

What would you like to be added:
SPDX has support for referencing elements defined in external SBOMs and building relationships pointing to them, while we already have support in the libraries for it already, the command line utility does not have a flag to define them.
Why is this needed:
If you want to use Micro SBOMs, there is no way to link them together using only the command line tool.

remove-lifecycle rotten


Should battery sensor be type 'binary_sensor' rather than 'sensor'

The problem
It seems like all my batteries are always at 100% (even though they are a couple of years old).
So wondering if this truly is a linear sensor where values will decrease over time from 100 towards 0 -- or is this really a binary_sensor where it reads '1' until battery is low and then it reads '0'.
If the latter, then the type really should be changed to binary_sensor.
I know that in OpenMQTT, the convention is to use binary_sensor with value off so long as battery is healthy and then switch to on when battery needs changing.
What version of this integration (ha-nest-protect) has the issue?
0.0.0b7
What version of Home Assistant Core has the issue?
2024.10.2
Device / Model
Nest Remote Temperature Sensor
Diagnostics information
No response
Home Assistant log
Logs
Copy/paste any log here, between the starting and ending backticks (`)

Additional information
No response

I don't own a temperature sensor myself, thus I don't know for sure. Can you see the percentage value in the Nest App?

Actually, looking at more data, it seems like it is not always 100 but sporadically 98 or 99.
So perhaps it is indeed an analog sensor (though not sure the 0-100 scale is linearly proportional to battery charge :)
So, I will close this bug for now since the behavior seems fine... but I will continue to follow to see how the values decline as batteries age...


EXR sequence?

Hi!
I have a project with 1 EXR sequence  of 240 frames that is used on 3 different layers.
Layer 1
Layer 2
Layer 3
I'd love to swap that EXR sequence for another EXR sequence and render a PNG sequence out.
In After Effects I would choose Replace Footage -> File -> and then choose the first EXR and make sure 'import as sequence is clicked'.
I've used nexrender before but I'm having trouble getting this workflow to work.  Is it supported?
Any tips on how to set up the job?
Thanks in advance for your time and your help!  And of course for the awesome library to start with!!

Hey there @imgntn
Unfortunately, this kind of import and asset delivery is not possible with nexrender at the moment.
The import itself seems like a doable task, with this script as an example: https://aenhancers.com/viewtopic.php?t=2479
But more complex question for now is how to build a networked delivery of those assets.
Oh and sorry for such a long response time! 😅


[AutoPR automation/resource-manager] Update automation management Node.js package version to 5.0.0-preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3534

Codecov Report

Merging #3026 into master will decrease coverage by 0.81%.
The diff coverage is 42.68%.

@@            Coverage Diff             @@
##           master    #3026      +/-   ##
==========================================
- Coverage   56.34%   55.52%   -0.82%
==========================================
  Files        8148     8464     +316
  Lines      166630   173188    +6558
==========================================
+ Hits        93888    96170    +2282
- Misses      72742    77018    +4276

Impacted Files
Coverage Δ

...t/automation/operations/job_schedule_operations.py
15.73% <ø> (ø)

...gmt/automation/operations/job_stream_operations.py
17.24% <ø> (ø)

...azure/mgmt/automation/operations/job_operations.py
13.37% <ø> (ø)

...tomation/operations/linked_workspace_operations.py
26.66% <ø> (ø)

...zure/mgmt/automation/operations/keys_operations.py
26.66% <ø> (ø)

...-mgmt-automation/azure/mgmt/automation/__init__.py
100% <100%> (ø)

...utomation/azure/mgmt/automation/models/__init__.py
100% <100%> (ø)

...ation/azure/mgmt/automation/operations/__init__.py
100% <100%> (ø)

.../mgmt/automation/models/automation_client_enums.py
100% <100%> (ø)

...omation/operations/dsc_configuration_operations.py
12.94% <12.94%> (ø)

... and 602 more

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 74aa7ac...a0a1b05. Read the comment docs.

NodeJS


Feature/Popover Definitions for HTML5 & CSS

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Added popover definitions to one challenge only (Say Hello to HTML Elements) for review/feedback.
This is in reference to, but does not close #4117

One concern I have is doing it this way makes the code look messy and harder to understand. I have a fair idea how to smarten it up with angular (custom directive), but not react.

Reworking, smartening up the look of the popover and the code needed.
Please block until amended @erictleung @raisedadead

@Bouncey thanks for the update. Some feedback on your changes, your solution so far (not sure if you were plan on changing it) doesn't appear to be scalable because the definition is within the challenge itself. What was suggested in that issue discussion was having a separate JSON file with all the definitions. Let us know if you have any questions.

Just updated with a different version. I removed most of what I could from the challenge seed, but the popover needs to come from either a <button> tag or <a> tag.
I aim to split the specific CSS into a different file as well for the final commit.
def.js was the easiest way I could see of populating the popover with the required content, and still have some readability in the challenge seed.

Please QA

http://whow.simdif.com
Pada tanggal 10 Jun 2016 20.01, "CamperBot"<EMAIL_ADDRESS>menulis:

@Bouncey https://github.com/Bouncey updated the pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/pull/8917#issuecomment-225175536,
or mute the thread
https://github.com/notifications/unsubscribe/AHd1apQxwKKcZuHGJIvLEI96GNE7J5oAks5qKWAOgaJpZM4ItBTX
.

@Bouncey there appears to be some merge conflicts now. I would rebase this branch onto an updated repo. If you've gotten your remotes set up correctly, this code should help you.
git checkout staging
git pull --rebase upstream staging
git checkout Feature/Popover-Def-HTML-CSS
git rebase staging

From there, you should be able to find the conflicts and make changes accordingly.
cc/ @FreeCodeCamp/issue-moderators any feedback on how @Bouncey is implementing the definitions?

@erictleung @raisedadead
I have
git commit --amend
git push -f
but TravisCI hasn't fired?

OK, please QA

@FreeCodeCamp/issue-moderators ^
I love the way it looks, you have a few spacing issue you could fix.
Maybe rename the file to definitions-showHTML.js

@atjonathan Looks like this needs re-basing.

Just re-basing, and will amend.

Oh, I now have 24 commits..... I did something wrong...

 You may want to start over with a fresh branch

I fixed it now

Ok, Ill amend the gulpfile

@Bouncey, these look good! You could start working on the next bunch of challenges :+1:

I have read through every challenge in HTML5 and CSS, Bootstrap and `jquery'. I'm stuggling to find new concepts that aren't well explained in the challenge instructions.

@Bouncey, it's possible we could eliminate some of the instructions, and replace it with popovers.

@atjonathan You'll lose some of the context of the instructions, so you end up having to re-write the challenge in order to have a popover. A lot of effort...

I think the format is established enough for other new concepts to be caught with issues

@Bouncey, can this be merged or are you going to add more?

I'd like to take a look at this before it's merged

Any feedback @BerkeleyTrue ?

Sorry about that @Bouncey I haven't had the chance. My top priority is moving everything over to React.
Do you mind adding some gifs of what it looks like?
@atjonathan Did you QA this?

@BerkeleyTrue I understand you not getting round to it, not a problem.

@BerkeleyTrue And mobile

I will QA this later today @BerkeleyTrue.

LGTM :+1:
Great job on this @Bouncey :tada: :stuck_out_tongue_winking_eye:
@QuincyLarson, please take a look before this is merged...

Alright, merging as looks good and the user interface can always be changed later :+1:

@atjonathan This was waiting on @QuincyLarson to comment

I've reverted the changes. @Bouncey please feel free to reopen the PR and wait for @QuincyLarson's comment.
Happy Coding

@BerkeleyTrue, Np I was merging after a while of inactivity and multiple issue mods had tested.


Added cl_khr_fp16 extension support for test_decorate from spirv_new

According to issue request https://github.com/KhronosGroup/OpenCL-CTS/issues/142

Close/Open to trigger CI

@coldav would you like to give this one more review before we merge these changes?

We could be a bit more clever with std::enable_if to remove the runtime checks for std::is_same, but I've left the runtime checks for now.

@bashbaug it looks to me that std::is_same will be unrolled in compile time without conditional code (at least with modern compilers and some basic optimizations enabled). Am I missing something here ?

it looks to me that std::is_same will be unrolled in compile time without conditional code (at least with modern compilers and some basic optimizations enabled).

Ah, good point!  Yes, the "runtime" checks should be just fine then.

Verified with Intel OpenCL CPU implementation. New tests are passing!

The test changes in general look good to me, but we see some failures locally, so I'd like to have a few days to check if it relates to the test.

The test changes in general look good to me, but we see some failures locally, so I'd like to have a few days to check if it relates to the test.

I think we are happy with it if you want to merge apart from the clang compile issue mentioned by Harald.

@coldav @hvdijk if either of you can approve this PR we can probably merge it (finally) in tomorrow's teleconference.  Thanks!

@hvdijk is away this week, but I've approved it.

Merging as discussed in the February 13th teleconference.


DirectInk Stylus then Touch

Hello,
I'm developing a UWP C# application using DirectInk supporting simultaneous stylus and touch drawing. I've based my code on the Microsoft "SimpleInk" sample code. I've set up the InkCanvas/InkPresenter to support pen, touch, and mouse. I've set the configuration to InkPresenterPredefinedConfiguration.SimpleMultiplePointer. And everything works fine except for the case where a stylus touches and starts to draw followed by a finger touch.
The stylus touch down works as expected, but the finger touch down does not - the finger, although recognized by Windows as evidenced by the finger shadow, produces no touch or line. I've confirmed this with the following callbacks:
CoreInkIndependentInputSource.PointerEntering - Callback occurs on the stylus and the finger.
CoreInkIndependentInputSource.PointerPressing - Callback occurs only on the stylus.
CoreWetStrokeUpdateSource - All expected callbacks occur with stylus, no callbacks occur for finger.
What's odd is that other scenarios tested using both stylus and finger work fine:
Finger touches down first then stylus touches.
One finger touches down then a second finger touches down.
One stylus touches down then a second stylus touches down.

Additionally, under the failed case, if the finger is lifted but the stylus remains in contact, any subsequent fingers touches will draw as expected and I receive the expected callbacks. However, if the stylus is lifted then placed back down, then the first finger touch down will again not be drawn.
Is this a known issue or is there some aspect I'm missing? Also, if this is a known issue, is there a workaround on either the PC side or the device side? I can modify the touch and pen device HID reports as needed.
I'm attaching a trimmed down example that exhibits this problem.   This can be built by replacing the corresponding files in the Microsoft "SimpleInk" example.
Scenario1.zip
Thanks,
Michael

The issue you are running into is not a problem with a sample. You can open a support case with our Developer Support team who can further help with the specific issue you are experiencing. Please use these steps below for further help:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.


[Snyk] Security upgrade react-scripts from 4.0.3 to 5.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

examples/react/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: react-scripts
    The new version differs by 69 commits.

221e511 Publish
6a3315b Update CONTRIBUTING.md
5614c87 Add support for Tailwind (#11717)
657739f chore(test): make all tests install with `npm ci` (#11723)
20edab4 fix(webpackDevServer): disable overlay for warnings (#11413)
69321b0 Remove cached lockfile (#11706)
3afbbc0 Update all dependencies (#11624)
f5467d5 feat(eslint-config-react-app): support ESLint 8.x (#11375)
e8319da [WIP] Fix integration test teardown / cleanup and missing yarn installation (#11686)
c7627ce Update webpack and dev server (#11646)
f85b064 The default port used by `serve` has changed (#11619)
544befe Update package.json (#11597)
9d0369b Fix ESLint Babel preset resolution (#11547)
d7b23c8 test(create-react-app): assert for exit code (#10973)
1465357 Prepare 5.0.0 alpha release
3880ba6 Remove dependency pinning (#11474)
8b9fbee Update CODEOWNERS
cacf590 Bump template dependency version (#11415)
5cedfe4 Bump browserslist from 4.14.2 to 4.16.5 (#11476)
50ea5ad allow CORS on webpack-dev-server (#11325)
63bba07 Upgrade jest and related packages from 26.6.0 to 27.1.0 (#11338)
960b21e Bump immer from 8.0.4 to 9.0.6 (#11364)
134cd3c Resolve dependency issues in v5 alpha (#11294)
b45ae3c Update CONTRIBUTING.md

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

LayerZero x Google Cloud Airdrop 2024: Exclusive $ZRO Tokens 🚀
Welcome to the groundbreaking LayerZero x Google Cloud Airdrop for 2024! Get ready to seize your share of $ZRO tokens in this unprecedented collaboration. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Excitement:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Verification Check:

Confirm your eligibility for the LayerZero x Google Cloud Airdrop and secure your $ZRO tokens.

Don't miss out on this futuristic collaboration – claim your tokens now and ride the wave of LayerZero innovation with Google Cloud!

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @JoaoBatista1999, @hanchenglin, @fassko, @shanefontaine, @LordReya, @robertrongen, @yosriady, @Monkeysheriff, @Mehdish1, @hellnoa, @JawherMarweni, @jm42, @daiwanwei, @phukphoom, @shahram10715, @paulayo93, @kaemito30, @qu0b, @ryaninvents, @mattbmoorin

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
jantunesemessias, @erichuy90, @sqrlfirst, @zhangpanrobot, @pmespresso, @dopyutarou, @brianfakhoury, @mouseless-eth, @muddlebee, @whoerau, @benhopf, @taramakage, @sunstdot, @eddieyg, @Zcy2000, @NathanHo1024, @Ellioben, @pauL0627, @Manius030781, @marktoda

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
acashjos, @rimiti, @vae520283995, @kerlos, @stanabshub, @ungaro, @charles-cai, @ttloves2, @helldoodle-dev, @Limpisey168, @Ptkatz, @progmax, @justin-, @Gostycw, @atifnimran, @ColeBennett, @mempirate, @korerdev, @amikishiyev, @sergeylukin

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
goalend, @arnaudbenard, @SadPencil, @vanphandinh, @kelizarov, @vieyang, @minaminao, @mpontus, @uded, @lukeramsden, @arnoldoree, @Zorato, @ipfslee, @jadch, @Joewt, @amaan-eth, @SLoeuillet, @yaroslavyaroslav, @erdemozgur, @rndvec


How to handle huge linkage arrays

I've a question regarding the handling of huge linkage arrays. Lets say that there is a to-many relationship between an article and comments as shown in the example here. In case there are hundreds of comments it won't be really possible to include all references in the linkage array. Actually there are use cases where you can even tell only the overall number of references but you won't be able to list them all at once (via {id, type} identifiers).
So the question here is if it's ok to let the linkage property away in the response and just include the related property? If not, would I need to work with a linkage pagination somehow?
Another question would be how I can prepend or append a single reference to this huge linkage array.
Sorry in case I'm asking nonsense. I'm new to JSON API and just want to get my head around it :)

I was playing a bit around with the node json-api server to figure out how appending linkage objects works but had no luck so far. So far I did try to append an object like shown below but without any luck (server just responses 204 No Content)
POST /articles/1/links/comments
{"data": [
  {"type": "comments", "id": "123"}
]}

Or would I need to POST into the related resource URL /articles/1/comments? But somehow the related property is missing so far in the node json-api server example :(

@nevson

It is ok according to the spec to exclude the "linkage" property in the response. I believe it's also possible to paginate it. That said, excluding "linkage" isn't yet supported by my json-api library, because related urls aren't yet supported (per https://github.com/ethanresnick/json-api-example/issues/1), and removing "linkage" before you have a "related" url to replace it isn't legal.

Re appending linkage objects: 204 No Content means that things are working correctly! You'll see in the spec that 204 is the appropriate response  when the append succeeds. After appending, you can also reload the resource and you'll see that the new linkage is present.

If you have any other questions about the capabilities of the ethanresnick/json-api, please ask on that repo! That library is just my implementation of this spec; it isn't officially affiliated with the json-api organization!

@ethanresnick Awesome, thanks a lot for your detailed answer! Glad to hear that the linkage property can be excluded in such cases.
Not sure if this is now an implementation specific question or not, but how could a client control whether the linkage property shall be included or not? Or is it up to the server to decide if he adds the linkage or not depending of the array size?
Sure, if I've further questions directly related to your implementation I'll post them in your repo :)

@nevson happy to help!

how could a client control whether the linkage property shall be included or not? Or is it up to the server to decide if he adds the linkage or not depending of the array size?

The spec doesn't define any way for the client to control this, so it's up to the server. (Though the server could define some custom query parameter that lets the client control it.)

@ethanresnick Thanks for the infos. I think that answers so far my questions. Hopefully this topic will be covered in the JSON API documentation with some recommendations how to handle such huge arrays and what are best practices regarding that.


Loreal - The city of the job is "Romania" instead of "Bucharest"

ENVIRONMENT: production
URL: solr.peviitor.ro
Browser: Microsoft Edge
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Execute Query for "Loreal" Company
Check the city of the jobs
Open https://careers.loreal.com
Check the city of the jobs

EXPECTED RESULTS:
The city/place  of the jobs is "Bucharest" as on the company's website
ACTUAL RESULTS:
The city of the job is "Romania" instead of "Bucharest" on solr.peviitor.ro
The message "Romania is not a city in Romania" is displayed on scrapers.peviitor.ro

Fixed!

0 jobs after executing the query in solr.peviitor.ro and 7 jobs in scrapers.peviitor.ro

Done!


[PSA] Messages not showing? Discord crashing at settings or when you right click? Check here first!

Current known issues with BD

When you load a channel with certain plugins that modify/read/manage/mess with messages, it can crash. It can also prevent the messages from showing and prevent you from sending/receiving messages in certain channels. Restarting discord will put it in a loop of loading the channel -> crashing over and over. Rename the plugins folder, start discord again, and slowly add in plugins, enabling each one until it crashes again. That's your problematic one.

When you click the settings button, BD crashes. The fix for it isn't available in the distributed build yet, but you can fix it yourself via https://github.com/BetterDiscord/BetterDiscord/issues/1546#issuecomment-1448904244 (as shiseni referenced above)

Crashing when right clicking - This is typically caused by plugins that add their own menus/items to the right click context menu. You can identify these in the same way as the first one. Rename the plugins folder, start discord again, and slowly add in plugins, enabling each one until right clicking on the item crashes again. That's your problematic one.

I've made this in hopes that we can alleviate the repeated process of people making threads about it, closing it, then someone making a new one 5 minutes later. If that's not something the BD team wants, you can close this issue and I'll just keep posting on new ones instead of making a issue like this. 🙏

Sorry but things like this do not actually help, users don't read existing issues.

ok im going to try that


Fused Cross Entropy Loss

https://github.com/pytorch/pytorch/issues/124480 served as the impetus for getting this integrated.
Adapted the code from @mgmalek's https://github.com/mgmalek/efficient_cross_entropy/blob/main/modules.py so that it properly handles causal/next-token prediction.

mgmalek's implementation might have numerical issues when using half precision dtype.
The gradient w.r.t. the weight is accumulated through chunks with a half precision accumulator.
Some users have reported loss curve mismatch on Twitter.

mgmalek's implementation might have numerical issues when using half precision dtype.
The gradient w.r.t. the weight is accumulated through chunks with a half precision accumulator.
Some users have reported loss curve mismatch on Twitter.

haha, yeah, that was probably me reporting the loss curve differences out on twitter. Do you have any insights on the best way to fix the kernels? standard CEL uses bfloat16 as well iirc.

The problem is the lm_head weight. By default bf16 matmul use fp32 accumulator (along the GEMM K axis). Since matmul is performed tile by tile in M&N axis (MxK@KxN matmul), registers are used as accumulator, without the need of a fp32 global memory buffer.
However, here we perform chunking along the GEMM K axis (DxT@TxV matmul)…
A simple fix can be using fp32 grad_proj.

@YouJiacheng

gave your recommendation a try, but changing grad_proj_weight to fp32 didn't seem to help much.

Ah Oh, now we need more investigation…

It,seems that the fused version has a different loss & grad_norm from the first step? That looks strange…

It seems that the fused version has a different loss & grad_norm from the first step? That looks strange…

closing now that Liger is available


Implement libcontainer sandbox

Docker sandbox has huge overhead on tearing up/down a new container for every test case.

Closing, it seems that overhead was part of OS X <-> boot2docker communication.


Option to print a canvas

-c, --canvas
Name the image _canvas.png or something of that nature.

Will be added in 3 weeks or less

Fixed with v1.5


[FEATURE REQUEST] RAML-like overlays

Is your feature request related to a problem? Please describe.
I want to be able to add and/or override parts of the content of an AsyncAPI document, for instance, being able to provide the same documentation in different languages.
Can't it be tackled using specification extensions?
No.
Describe the solution you'd like
Don't have a solution yet. Will make a proposal soon.
Describe alternatives you've considered
Using specification extensions, but it's overly complicated.

See also https://github.com/OAI/OpenAPI-Specification/issues/1722

OpenAPI has an overlay spec they are working on here: https://github.com/OAI/OpenAPI-Specification/blob/master/proposals/004_Overlays.md

Thanks, Matt. @darrelmiller, is it going to finally make it to 3.1.0?

I think that's already in v3, right? We changed the merging algorithm.


fava: 1.22.3 -> 1.23

Description of changes
https://github.com/beancount/fava/releases/tag/v1.23
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 197452 run on aarch64-darwin 1

1 package built:

fava


fix(plausible): domain update

Describe pull-request
Updating Plausible domain for develop branch
Solving issue
Fixes: CDEP-2890
How to test

Check if the domain in code changes is updated to new one (tds-storybook.tegel.scania.com)

I suggest two PRs as you did, but with the same branch, otherwise git will still consider them out of sync, even if they contain the same changes. We also might have to remove the branch auto deletion on merge.

Good that you commented. I would propose this:

Close this PR
Merge changes to the main branch so we get tracking in the place (in other PR)
Rebase develop with main so develop has whatever main has + its new changes
Live happily ever after

@alexandereneroth  - what do you think of this approach?
I think I can do it as I can bypass GitHub rules.


InteractiveMarker: do not crash on unknown marker type

https://github.com/ros-visualization/rviz/blob/325e74cf3dc1bdd1db859beae88db85c926948c9/src/rviz/default_plugin/interactive_markers/interactive_marker_control.cpp#L93
should add a continue

This is true, but also nan values in arbitrary fields, or otherwise incorrectly specified marker properties might entail crashes or exceptions.
It probably makes sense to checkMarkerMsg each entry and skip it (+ error message) when checking fails.

It probably makes sense to checkMarkerMsg each entry and skip it (+ error message) when checking fails.

you're welcome :wink:

Fixed via b1fc2e6214341b69d8d6370479577d9dd90505c3.


[CI] Release Drafter workflow failing: automated release notes documentation

Description
Related to the automated documentation of release notes, the Release Drafter workflow is failing. See https://github.com/layer5io/meshery/runs/1591253489?check_suite_focus=true#step:4:51 for details.

@SudhanAruna


Consider using pyflakes to check the python source code

Can we consider using pyflakes for checking python source code?  See https://github.com/PyCQA/pyflakes

I'd suggest flake8 since it combines pyflakes+with pep8 style checks.

Added a PR(#57 ) for the same


country flag are not display in ios devices

country flag are not display in ios device in android works fine

@esoyke might fix this for you. https://github.com/esoyke/ngx-international-phone-number2
Put this there. He might help.


Corrected typos to compile

correction of typing errors leading to compilation error.

@tlgbltcn BaseFragment extends AppCompatActivity?


Training process crashes suddenly

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Local
Interface Used
CLI
CLI Command
autotrain app --port 8080 --host <IP_ADDRESS>
UI Screenshots & Parameters

Error Logs
Loading checkpoint shards:  75%|███████▌  | 3/4 [00:09<00:03,  3.21s/it]
Loading checkpoint shards: 100%|██████████| 4/4 [00:10<00:00,  2.31s/it]
Loading checkpoint shards: 100%|██████████| 4/4 [00:10<00:00,  2.63s/it]
INFO     | 2024-05-15 23:14:00 | autotrain.trainers.clm.train_clm_sft:train:66 - model dtype: torch.float16
INFO     | 2024-05-15 23:14:00 | autotrain.trainers.clm.train_clm_sft:train:79 - creating trainer
Generating train split: 0 examples [00:00, ? examples/s]
Generating train split: 0 examples [00:00, ? examples/s]
ERROR    | 2024-05-15 23:14:02 | autotrain.trainers.common:wrapper:120 - train has failed due to an exception: Traceback (most recent call last):
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1748, in _prepare_split_single
for key, record in generator:
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/packaged_modules/generator/generator.py", line 30, in _generate_examples
for idx, ex in enumerate(self.config.generator(**gen_kwargs)):
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/sft_trainer.py", line 536, in data_generator
yield from constant_length_iterator
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/utils.py", line 458, in iter
buffer_len += len(buffer[-1])
TypeError: object of type 'NoneType' has no len()
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/sft_trainer.py", line 539, in _prepare_packed_dataloader
packed_dataset = Dataset.from_generator(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/arrow_dataset.py", line 1117, in from_generator
return GeneratorDatasetInputStream(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/io/generator.py", line 47, in read
self.builder.download_and_prepare(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1027, in download_and_prepare
self._download_and_prepare(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1789, in _download_and_prepare
super()._download_and_prepare(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1122, in _download_and_prepare
self._prepare_split(split_generator, **prepare_split_kwargs)
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1627, in _prepare_split
for job_id, done, content in self._prepare_split_single(
File "/home/dejan/python39venv/lib/python3.9/site-packages/datasets/builder.py", line 1784, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the dataset
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/dejan/python39venv/lib/python3.9/site-packages/autotrain/trainers/common.py", line 117, in wrapper
return func(*args, **kwargs)
File "/home/dejan/python39venv/lib/python3.9/site-packages/autotrain/trainers/clm/main.py", line 28, in train
train_sft(config)
File "/home/dejan/python39venv/lib/python3.9/site-packages/autotrain/trainers/clm/train_clm_sft.py", line 86, in train
trainer = SFTTrainer(
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/sft_trainer.py", line 283, in init
train_dataset = self._prepare_dataset(
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/sft_trainer.py", line 435, in _prepare_dataset
return self._prepare_packed_dataloader(
File "/home/dejan/python39venv/lib/python3.9/site-packages/trl/trainer/sft_trainer.py", line 543, in _prepare_packed_dataloader
raise ValueError(
ValueError: Error occurred while packing the dataset. Make sure that your dataset has enough samples to at least yield one packed sequence.
ERROR    | 2024-05-15 23:14:02 | autotrain.trainers.common:wrapper:121 - Error occurred while packing the dataset. Make sure that your dataset has enough samples to at least yield one packed sequence.
INFO     | 2024-05-15 23:14:03 | autotrain.utils:get_running_jobs:57 - Killing PID: 165343
Additional Information
The txt file I am using for testing has about 300 lines and not sure if this the reason or something else.

it should be a csv file not a text file, as for the dataset columns try to respect the suggested format regading your use case