Failed to open the serial port

I can't open any Quectel BG95 modem serial port enumerated on the USB port, I keep getting the error:
**** Failed to open the serial port /dev/ttyUSB3 ****
Other terminals like Putty can open the port without problems (without sudo permission).
Usually as a workaround I restarted the PC and Serial Monitor was able to open the port, but from today this workaround no longer works.
Maybe it's the same problem reported here:
https://github.com/microsoft/vscode-serial-monitor/issues/142
/home/parmi/.config/Code/logs/20240112T132216/window1/exthost/output_logging_20240112T132216/1-Serial Monitor Logging.log
2024-01-12T13:22:16.789Z [info] [vscode-serial-monitor] Activating extension
2024-01-12T13:22:17.125Z [debug] [vscode-serial-monitor.monitor] VsCodeHostAdapter [webview -> host]: {"service":"monitorHost","type":"initialize","kind":"request","messageId":0}
2024-01-12T13:22:17.381Z [debug] [vscode-serial-monitor.monitor] VsCodeHostAdapter [webview <- host]: {"service":"monitorHost","type":"initialize","kind":"response","messageId":0,"payload":{"localization":{"displayLanguage":"en","displayLanguageKind":"VSCode"},"ports":[{"portName":"/dev/ttyUSB1","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB2","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB4","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB0","friendlyName":"FTDI","vid":"0403","pid":"6001"},{"portName":"/dev/ttyS0"},{"portName":"/dev/ttyS1"},{"portName":"/dev/ttyS10"},{"portName":"/dev/ttyS11"},{"portName":"/dev/ttyS12"},{"portName":"/dev/ttyS13"},{"portName":"/dev/ttyS14"},{"portName":"/dev/ttyS15"},{"portName":"/dev/ttyS16"},{"portName":"/dev/ttyS17"},{"portName":"/dev/ttyS18"},{"portName":"/dev/ttyS19"},{"portName":"/dev/ttyS2"},{"portName":"/dev/ttyS20"},{"portName":"/dev/ttyS21"},{"portName":"/dev/ttyS22"},{"portName":"/dev/ttyS23"},{"portName":"/dev/ttyS24"},{"portName":"/dev/ttyS25"},{"portName":"/dev/ttyS26"},{"portName":"/dev/ttyS27"},{"portName":"/dev/ttyS28"},{"portName":"/dev/ttyS29"},{"portName":"/dev/ttyS3"},{"portName":"/dev/ttyS30"},{"portName":"/dev/ttyS31"},{"portName":"/dev/ttyS4"},{"portName":"/dev/ttyS5"},{"portName":"/dev/ttyS6"},{"portName":"/dev/ttyS7"},{"portName":"/dev/ttyS8"},{"portName":"/dev/ttyS9"}],"supportedBauds":[300,1200,2400,4800,9600,19200,38400,57600,74880,115200,230400,250000],"loggingSeverity":"warn","closable":"no","settings":{"lineEnding":"\r\n","dataBits":8,"dtr":false,"rts":false,"autoReconnectionEnabled":false,"logFileDirectory":"/home/parmi/Desktop","logFileEnabled":0,"customBaudRates":[]},"fontInformation":{},"timestampFormat":"%H:%M:%S:%L"}}
2024-01-12T13:22:17.381Z [debug] [vscode-serial-monitor.monitor] Received serial monitor initialization response {"localization":{"displayLanguage":"en","displayLanguageKind":"VSCode"},"ports":[{"portName":"/dev/ttyUSB1","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB2","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB4","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB0","friendlyName":"FTDI","vid":"0403","pid":"6001"},{"portName":"/dev/ttyS0"},{"portName":"/dev/ttyS1"},{"portName":"/dev/ttyS10"},{"portName":"/dev/ttyS11"},{"portName":"/dev/ttyS12"},{"portName":"/dev/ttyS13"},{"portName":"/dev/ttyS14"},{"portName":"/dev/ttyS15"},{"portName":"/dev/ttyS16"},{"portName":"/dev/ttyS17"},{"portName":"/dev/ttyS18"},{"portName":"/dev/ttyS19"},{"portName":"/dev/ttyS2"},{"portName":"/dev/ttyS20"},{"portName":"/dev/ttyS21"},{"portName":"/dev/ttyS22"},{"portName":"/dev/ttyS23"},{"portName":"/dev/ttyS24"},{"portName":"/dev/ttyS25"},{"portName":"/dev/ttyS26"},{"portName":"/dev/ttyS27"},{"portName":"/dev/ttyS28"},{"portName":"/dev/ttyS29"},{"portName":"/dev/ttyS3"},{"portName":"/dev/ttyS30"},{"portName":"/dev/ttyS31"},{"portName":"/dev/ttyS4"},{"portName":"/dev/ttyS5"},{"portName":"/dev/ttyS6"},{"portName":"/dev/ttyS7"},{"portName":"/dev/ttyS8"},{"portName":"/dev/ttyS9"}],"supportedBauds":[300,1200,2400,4800,9600,19200,38400,57600,74880,115200,230400,250000],"loggingSeverity":"warn","closable":"no","settings":{"lineEnding":"\r\n","dataBits":8,"dtr":false,"rts":false,"autoReconnectionEnabled":false,"logFileDirectory":"/home/parmi/Desktop","logFileEnabled":0,"customBaudRates":[]},"fontInformation":{},"timestampFormat":"%H:%M:%S:%L"}
2024-01-12T13:22:36.523Z [debug] [vscode-serial-monitor.monitor] VsCodeHostAdapter [webview -> host]: {"service":"monitorHost","type":"initialize","kind":"request","messageId":0}
2024-01-12T13:22:36.656Z [debug] [vscode-serial-monitor.monitor] VsCodeHostAdapter [webview <- host]: {"service":"monitorHost","type":"initialize","kind":"response","messageId":0,"payload":{"localization":{"displayLanguage":"en","displayLanguageKind":"VSCode"},"ports":[{"portName":"/dev/ttyUSB1","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB2","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB4","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB0","friendlyName":"FTDI","vid":"0403","pid":"6001"},{"portName":"/dev/ttyS0"},{"portName":"/dev/ttyS1"},{"portName":"/dev/ttyS10"},{"portName":"/dev/ttyS11"},{"portName":"/dev/ttyS12"},{"portName":"/dev/ttyS13"},{"portName":"/dev/ttyS14"},{"portName":"/dev/ttyS15"},{"portName":"/dev/ttyS16"},{"portName":"/dev/ttyS17"},{"portName":"/dev/ttyS18"},{"portName":"/dev/ttyS19"},{"portName":"/dev/ttyS2"},{"portName":"/dev/ttyS20"},{"portName":"/dev/ttyS21"},{"portName":"/dev/ttyS22"},{"portName":"/dev/ttyS23"},{"portName":"/dev/ttyS24"},{"portName":"/dev/ttyS25"},{"portName":"/dev/ttyS26"},{"portName":"/dev/ttyS27"},{"portName":"/dev/ttyS28"},{"portName":"/dev/ttyS29"},{"portName":"/dev/ttyS3"},{"portName":"/dev/ttyS30"},{"portName":"/dev/ttyS31"},{"portName":"/dev/ttyS4"},{"portName":"/dev/ttyS5"},{"portName":"/dev/ttyS6"},{"portName":"/dev/ttyS7"},{"portName":"/dev/ttyS8"},{"portName":"/dev/ttyS9"}],"supportedBauds":[300,1200,2400,4800,9600,19200,38400,57600,74880,115200,230400,250000],"loggingSeverity":"warn","closable":"yes","settings":{"lineEnding":"\r\n","dataBits":8,"dtr":false,"rts":false,"autoReconnectionEnabled":false,"logFileDirectory":"/home/parmi/Desktop","logFileEnabled":0,"customBaudRates":[]},"fontInformation":{},"timestampFormat":"%H:%M:%S:%L"}}
2024-01-12T13:22:36.656Z [debug] [vscode-serial-monitor.monitor] Received serial monitor initialization response {"localization":{"displayLanguage":"en","displayLanguageKind":"VSCode"},"ports":[{"portName":"/dev/ttyUSB1","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB2","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB4","friendlyName":"Quectel, Incorporated","vid":"2c7c","pid":"0700"},{"portName":"/dev/ttyUSB0","friendlyName":"FTDI","vid":"0403","pid":"6001"},{"portName":"/dev/ttyS0"},{"portName":"/dev/ttyS1"},{"portName":"/dev/ttyS10"},{"portName":"/dev/ttyS11"},{"portName":"/dev/ttyS12"},{"portName":"/dev/ttyS13"},{"portName":"/dev/ttyS14"},{"portName":"/dev/ttyS15"},{"portName":"/dev/ttyS16"},{"portName":"/dev/ttyS17"},{"portName":"/dev/ttyS18"},{"portName":"/dev/ttyS19"},{"portName":"/dev/ttyS2"},{"portName":"/dev/ttyS20"},{"portName":"/dev/ttyS21"},{"portName":"/dev/ttyS22"},{"portName":"/dev/ttyS23"},{"portName":"/dev/ttyS24"},{"portName":"/dev/ttyS25"},{"portName":"/dev/ttyS26"},{"portName":"/dev/ttyS27"},{"portName":"/dev/ttyS28"},{"portName":"/dev/ttyS29"},{"portName":"/dev/ttyS3"},{"portName":"/dev/ttyS30"},{"portName":"/dev/ttyS31"},{"portName":"/dev/ttyS4"},{"portName":"/dev/ttyS5"},{"portName":"/dev/ttyS6"},{"portName":"/dev/ttyS7"},{"portName":"/dev/ttyS8"},{"portName":"/dev/ttyS9"}],"supportedBauds":[300,1200,2400,4800,9600,19200,38400,57600,74880,115200,230400,250000],"loggingSeverity":"warn","closable":"yes","settings":{"lineEnding":"\r\n","dataBits":8,"dtr":false,"rts":false,"autoReconnectionEnabled":false,"logFileDirectory":"/home/parmi/Desktop","logFileEnabled":0,"customBaudRates":[]},"fontInformation":{},"timestampFormat":"%H:%M:%S:%L"}

Serial Monitor v0.11.0
OS: Ubuntu 22.04.3 LTS
Visual Studio Code:

Version: 1.85.1
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:47:11.635Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-14-generic snap

I'm also having trouble connecting to a UART-USB Prolific Adapter.
I managed to successfully perform connection and activity with the same device on a Windows Machine
But both Ubuntu and Fedora displays the same message:
**** Failed to open the serial port /dev/ttyUSB0 ****
I'm able to open connection with other Serial devices.
Using dmesg | grep tty
I've tried communicating between 2 USB-Serial adapters. But I'm getting the same error -32:
[  227.380831] pl2303 ttyUSB1: pl2303_get_line_request - failed: -32
[  227.384994] pl2303 ttyUSB1: pl2303_get_line_request - failed: -32
[  227.385980] pl2303 ttyUSB1: pl2303_get_line_request - failed: -32
[  227.388969] pl2303 ttyUSB1: error sending break = -32
[  234.021402] pl2303 ttyUSB1: error sending break = -32
[  234.126054] pl2303 ttyUSB0: error sending break = -32
[  250.306071] pl2303 ttyUSB0: pl2303_get_line_request - failed: -32
[  250.316000] pl2303 ttyUSB0: pl2303_get_line_request - failed: -32
[  268.288965] pl2303 ttyUSB1: pl2303_get_line_request - failed: -32
[  268.294195] pl2303 ttyUSB1: pl2303_get_line_request - failed: -32
[  297.268640] pl2303 ttyUSB1: error sending break = -32
[  298.531848] pl2303 ttyUSB0: error sending break = -32
My best guess is that something happened on the Linux Driver kernel that does not respond correctly to the VsCdoe Serial Monitor Extension command.
I could, on the same Ubuntu machine, comunicate with the USB-Serial adapter using minicom. But not the Extension.

@parmi93 Could you test these steps: https://github.com/microsoft/vscode-serial-monitor/issues/142#issuecomment-1864644326, and let me know the results? It could be that this, as you pointed out, is the same issue as #142. If so, we'll close this item and link it to the other bug.
Thanks!

I managed to open the /dev/ttyUSB3 port with the node project (test.zip).
But if I uncomment line 10 of serialport.ts I get this error:
parmi@parmi-Dell-G16-7630:~/Downloads/test$ sudo dmesg | grep tty
[  643.724396] usb 1-8: FTDI USB Serial Device converter now attached to ttyUSB0
[  650.505375] usb 1-10: GSM modem (1-port) converter now attached to ttyUSB1
[  650.505573] usb 1-10: GSM modem (1-port) converter now attached to ttyUSB2
[  650.505766] usb 1-10: GSM modem (1-port) converter now attached to ttyUSB3
parmi@parmi-Dell-G16-7630:~/Downloads/test$ npm run build

><EMAIL_ADDRESS>build
> tsc -p .

parmi@parmi-Dell-G16-7630:~/Downloads/test$ node dist/serialport.js
(node:8001) UnhandledPromiseRejectionWarning: Error: Error: Inappropriate ioctl for device, cannot set
(node:8001) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:8001) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
parmi@parmi-Dell-G16-7630:~/Downloads/test$
I also noticed that if I try to open the  /dev/ttyUSB3 port via Serial Monitor after I get the error **** Failed to open the serial port /dev/ttyUSB3 **** I can't open the port even with your node project, I have to close Visual Studio Code to be able to reopen the port with your node project, while other tools (like Putty) manage to open the port even with Visual Studio Code still open.

@parmi93 Have you attempted to open the Serial Monitor through the VS Code Serial Monitor extension with various combinations of the RTS and DTR settings?
I'm currently trying to investigate if there would be a way to work around this external issue, but I wanted to confirm that you've tried that as well. Thanks.

Yes, I just tried again Serial Monitor through the VS Code to open the port with all possible combinations of RTS and DTR, none worked.
I also tried all possible combinations of dtr and cts with serialPort.set(), none of them worked, It only works if this line is commented out.

@parmi93, thank you for the confirmation. This definitely seems like some issue with the serialport library and how it handles the .set() method.
However, this is happening enough that we should attempt to have some workaround, therefore, I'll mark this bug as external but make a note to investigate providing some kind of workaround.

I too experience this issue, when trying to upload to arduino. Is there no way I can "hack" my way out of this?
Since I cannot monitor using VSC, I have to use Arduino IDE to monitor. And since I do this, the serial port is blocked and therefore I cannot use the upload function in VSC either. A bit annoying :-)

@jegjessing @parmi93 Thank you all for your patience, I understand this is a frustrating issue. Since this is an external issue, there isn't too much we can do about it.
However, I have plans to, as a workaround, maybe add a setting that disables the RTS and DTR settings for people who are in the situation, or maybe at least not invoke the method call that seems to cause this issue when the requested RTS and DTR settings aren't enabled.
Would some kind of workaround like this work for you all?

I think it should be fine =)

@atomsmith or @parmi93, as a quick sanity check before I implement the workaround idea, could you slightly modify the test I had you run?
In the new SerialPort invocation, could you add rtscts: true to the object passed into the constructor? Ensure that the serialPort.set method is not commented out, I want to see if actually this has something to do with it.
Thanks! And thanks for your continued patience with this.

I tried to add rtscts: true to the constructor, but it still fail to open the port (I tried again all the four combination of serialPort.set(...)), I can only open the port when serialPort.set(...) is commented out.

@parmi93 @atomsmith @jegjessing @lawrencerb
Because I've noticed that the bug here on the external dependency: https://github.com/serialport/node-serialport/issues/2636, is only happening on linux, I wonder if a quick way to unblock you all is to only call this method if we're not on linux.
Could you all manually switch the extension of this zip to .vsix, install it, and test to see if this fixes your issue?
vscode-serial-monitor.zip

Now I don't get any error when I open the port, but I noticed that I get no response from the modem when I send a command, I'm sure that the command reaches the modem because if I send a reboot command the modem restarts, but for some reason serial monitor doesn't show any data it receives, I've tried all combinations of DTR and RTS.
I had also noticed this behaviour with the test.zip you had created, at the time I hadn't said anything simply because I thought that since it was a test it was "expected".
Also another problem I've always noticed, is that when the port is closed "without warning", for example if the device reboots or if I remove the USB cable, the serial monitor detects "the closure" showing the message ---- Closed serial port /dev/ttyUSB3 due to disconnection from the machine ----, but then it doesn't allow you to open any other port, it keeps showing the error **** Failed to open the serial port /dev/ttyUSB2 ****, I have to restart VS Code to be able to reopen the port.

@parmi93
I apologize that I'm needing your all's help for debugging, but since I don't have the required hardware, if you could test again with the test.zip. While testing that program, if you modify line 3, you could test different settings of: rtscts, xon, xoff, etc. This will help me understand what the issue is that's happening. I'm wondering if there are different settings that we need to start the serial port with.
Additionally, does it fail to open if you call .set even with no parameters?

I did some digging in the code (serialport.ts) and realized that the serialPort.write() method is never called, so it was impossible that the device could receive any command I sent.
I then edited the last part of the script serialport.ts from:
// on any data into stdin
stdin.on( 'data', function( key ){
  // esc ( end of text )
  if ( key.toString() === '\u001B' ) {
    process.exit();
  }
});

to:
// on any data into stdin
stdin.on( 'data', (data) => {
  if ( data.toString() === '\u001B' ) {
      process.exit();
  }
  serialPort.write(data.toString())
});

(I've never used NodeJS before so I don't know what I'm doing, but it seems to work)
With the modified script I can successfully send and receive responses from the device.
I also added the following boolean parameters rtscts, xon, xoff, xany, hupcl to the SerialPort constructor setting their values with all 32 possible combinations, in all 32 cases I was always able to send and receive replies from the device successfully.
I tried calling the set method without parameters (serialPort.set({})), but again the port fails to open with the following error:
parmi@parmi-Dell-G16-7630:~/Downloads/test$ node dist/serialport.js
(node:18844) UnhandledPromiseRejectionWarning: Error: Error: Inappropriate ioctl for device, cannot set
(node:18844) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:18844) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I also tried the new "vscode-serial-monitor.zip" you shared here:
https://github.com/microsoft/vscode-serial-monitor/issues/142#issuecomment-2049930857
with this version of the extension I can open the port, send and receive responses from the device successfully with all combinations of DTR/RTS.

@parmi93 Wow, thank you so much for your willingness to test and investigate so much. As far as I can tell, I think this confirms that the issue is strictly with the .set method.
Could you confirm for me, what OS are you on? The thing I tried to add in this vsix: https://github.com/microsoft/vscode-serial-monitor/issues/159#issuecomment-2034645480 was simply checking which OS was being used.
What value gets returned if you get the value of process.platform in a node program?

The value I get from process.platform is simply linux.

Hm, and to confirm, you said that this vsix (once changing the extension) only works for transmitting but not receiving?
vscode-serial-monitor.zip

https://github.com/microsoft/vscode-serial-monitor/issues/159#issuecomment-2034645480 -> Only works for transmitting
https://github.com/microsoft/vscode-serial-monitor/issues/142#issuecomment-2049930857 -> Works for transmitting and receiving
https://github.com/microsoft/vscode-serial-monitor/issues/159#issuecomment-2059329785 -> Works for transmitting and receiving

@parmi93 Okay if the most recent vsix works, I will try to get that in PR and merge that and have it in the pre-release in the coming days. Thanks!

@parmi93 If all goes well, this should be in pre-release tomorrow 👍


[workers] update wrangler dev docs for v3

Remove --experimental-local and --local.
Add --remote
update wording to show that local is new default

--persist will want to be removed (not a thing anymore) - Miniflare persists by default and remote talks to 'live' bindings.


Improvement enlarge merge_filter_callback timeout_m… #42602

…s (#42602)
Sometimes we encounter [E1008]Reached timeout=1000ms, at this time, like other rf-related rpc requests, the timeout should be set larger.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall


chore: use B160, B256 and U256 coming from revm and ruint

As the title says, it uses the above types everywhere it is possible deprecating the ones coming ethers-core.
This is a step in the direction of having every reth-primitives type to be arbitrary and proptest::arbitrary derivable, as well as leveraging ruint. This will enable https://github.com/paradigmxyz/reth/pull/513 and proptest tests for every type (which complements test-fuzz).
Since their interfaces are slightly different, a lot of files got touched...
Some other things:

There's a lot of U256::from(...) replacing into() because of: https://github.com/recmo/uint/blob/main/src/from.rs#L1-L5
Using the revm-interpreter branch, which in the future should be changed to revm-primitives. Currently using revm and revm-interpreter from my repo while this is getting merged https://github.com/bluealloy/revm/pull/314
I'm aliasing B160 to H160 and B256 to H256... It made the transition easier to fix, but should I remove it?

I'm aliasing B160 to H160 and B256 to H256... It made the transition easier to fix, but should I remove it?

this makes it less painful, we could then phase that out crate by crate

@recmo cc for visibility

@joshieDo what do we need to get this over the line?

Current options:

merge as is
create a PR with the above suggestions into ruint. it's pretty easy to add, altho not sure where or if @recmo wants it
recmo adds it

next steps (outside this PR):

Wrapper struct around bytes::Bytes + arbitrary
ruint type for Bloom + arbitrary
move other Ux types (like U64) into ruint

SGTM. Pinged @recmo in DMs about the above notes, Remco pls let us know if you'd be open to  us adding some more changes to ruint like: fn zero(), investigating From<_> for T issue (maybe making a breaking change in your existing from(..) fn sig, and adding some more wrapper types, perhaps behind a feature flag. (Else we can add them to revm-primitives?)


Fix --generate-hashes with bare VCS URLs

#807 introduced an unhandled edge case when bare VCS URLs like git+git://github.com/jazzband/pip-tools@7d86c8d3ecd1faa6be11c7ddc6b29a30ffd1dae3 are used with pip-compile --generate-hashes:
$ cat requirements.in
git+https://github.com/jazzband/pip-tools@7d86c8d3ecd1faa6be11c7ddc6b29a30ffd1dae3
$ pip-compile --generate-hashes
Traceback (most recent call last):
  File "/Users/jcwork/.pyenv/versions/pip-tools/bin/pip-compile", line 11, in <module>
    load_entry_point('pip-tools', 'console_scripts', 'pip-compile')()
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/jcwork/Documents/pip-tools/piptools/scripts/compile.py", line 357, in cli
    hashes = resolver.resolve_hashes(results)
  File "/Users/jcwork/Documents/pip-tools/piptools/resolver.py", line 88, in resolve_hashes
    return {ireq: self.repository.get_hashes(ireq) for ireq in ireqs}
  File "/Users/jcwork/Documents/pip-tools/piptools/resolver.py", line 88, in <dictcomp>
    return {ireq: self.repository.get_hashes(ireq) for ireq in ireqs}
  File "/Users/jcwork/Documents/pip-tools/piptools/repositories/local.py", line 78, in get_hashes
    return self.repository.get_hashes(ireq)
  File "/Users/jcwork/Documents/pip-tools/piptools/repositories/pypi.py", line 299, in get_hashes
    return {self._get_file_hash(cached_link)}
  File "/Users/jcwork/Documents/pip-tools/piptools/repositories/pypi.py", line 323, in _get_file_hash
    with open_local_or_remote_file(location, self.session) as f:
  File "/Users/jcwork/.pyenv/versions/3.5.3/lib/python3.5/contextlib.py", line 59, in __enter__
    return next(self.gen)
  File "/Users/jcwork/Documents/pip-tools/piptools/repositories/pypi.py", line 397, in open_local_or_remote_file
    response = session.get(url, headers=headers, stream=True)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/pip/_vendor/requests/sessions.py", line 546, in get
    return self.request('GET', url, **kwargs)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/pip/_internal/download.py", line 439, in request
    return super(PipSession, self).request(method, url, *args, **kwargs)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/pip/_vendor/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/pip/_vendor/requests/sessions.py", line 640, in send
    adapter = self.get_adapter(url=request.url)
  File "/Users/jcwork/.pyenv/versions/3.5.3/envs/pip-tools/lib/python3.5/site-packages/pip/_vendor/requests/sessions.py", line 731, in get_adapter
    raise InvalidSchema("No connection adapters were found for '%s'" % url)
pip._vendor.requests.exceptions.InvalidSchema: No connection adapters were found for 'git+https://github.com/jazzband/pip-tools@7d86c8d3ecd1faa6be11c7ddc6b29a30ffd1dae3'

This is because PyPIRepository.get_hashes incorrectly detects all non-editable URLs as hashable, instead of only artifact URLs.
This PR does two things in separate commits (so you can confirm the failing behavior and test case if you want):

Add a failing test case by having test_url_package try all URLs with and without --generate-hashes
Fix the test case by updating get_hashes to use a better hashability check, modeled on the hashability logic in pip's RequirementPreparer.prepare_linked_requirement

Changelog-friendly one-liner: Fix --generate-hashes with bare VCS URLs
Contributor checklist

[x] Provided the tests for the changes.
[x] Requested a review from another contributor.
[x] Gave a clear one-line description in the PR (that the maintainers can add to CHANGELOG.md on release).
[x] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

@jcushman squash please commits.

Squashed!

pip-tools v3.8.0 is released


QUESTION: How to inject mock of firebase app in unit tests?

I am using the following library to mock firebase in my unit tests: https://github.com/soumak77/firebase-mock
I am able to create an entire mock of the firebase SDK which I would like angularfire to use during unit testing.  In order to achieve this, I would like to pass an instance of a mocked firebase.app.App to angularfire versus angularfire internally creating an app.  How would I go about doing this?

Anyone have feedback on this?  Dependency injection is a must have to test apps that use this library.

@soumak77 There's nothing out-of-the-box for you to use, but it's possible to set it up yourself. Each AngularFire feature takes in some config tokens that are used to make an app.  All you need to do is either alias the @firebase/app module to your firebase-mock module or use Webpack's NormalModuleReplacement plugin. That way it will switch out the real Firebase App module for the mock module and you won't have to do any code changes. Let me know if that sounds like that will work.

@davideast angularfire2 already makes use of a FirebaseAppProvider.  Is there a way to override this provider to allow me to control how the app is generated?

@soumak77 No, the FirebaseAppProvider is not used in the services. Due to Zone.js issues we have to create the app inside the service. Therefore your best bet it to replace the module at build time, this is also the easiest option.

Closing since we already have an issue to create testing docs, feel free to continue discussing.


ValidationError missing reference to model being validated

In pydantic 1.x, ValidationError has a model property which references the model being validated.
We used this when deciding what error to show to the user.
It doesn't seem possible to get this information in 2.x.
Would you consider adding it back?
(I'm guessing this issue belongs in core and not in pydantic. If it's in the wrong place, let me know)

Good question - I don't think we'll add this back, but we will allow subclassing of ValidationError, which will enable support for something like this on the user side.
See https://github.com/pydantic/pydantic/issues/9686 to track that progress. Going to close this as resolved for now 👍


pre-commit: PR111014

Link: https://github.com/llvm/llvm-project/pull/111014
Requested by: @goldsteinn

/close


ci: run cypress as part of the CI validation process

Related Issue(s)

resolves #156

Quick overview of the change
Added a new ci workflow for running integration tests
Quick testing guide

closing this for now but will work on it again later when nightly is available


Added benchmark suite

This adds a benchmark suite to Prism.
Since I already explained everything in benchmark.html, I won't repeat myself but the basic idea is that the whole benchmark configuration is in benchmark/config.js.
Points to discuss

~I added support for multiple remote branches because it was easy and useful for testing my implementation but maybe we don't need it?~ It was pretty easy to implement, so let's just keep it.
~rn, I only display the mean, margin of error, and sample count. Anything else we need?~ More information can be added in future PRs if needed.
~The summary is quite simple, so maybe we could add something?~ It displays enough information IMO.

I think this just needs a proper review.
@mAAdhaTTah I looked over it again and did some minor refactoring. I think it's good to go but it would be nice if you could review it.

@RunDevelopment I think this can be merged :)

There's still one open comment.
cc @mAAdhaTTah

@RunDevelopment sorry, I approved, I don't think that change is necessary.

@mAAdhaTTah Ahh ok. I always read "approved + comments" as "approved if all comments resolved". I'll keep that in mind in the future.

In this case, I thought I had commented and resolved so that's my bad.


R-Value now extracted from xlsx file

so is besser :-)

of corse, one moment

Thanks @Rubber1Duck


The metadata of the file created by the TextSplitter class (doSplitDocuments method) is getting the incorrect page number

After running this sample application (ai-openai-rag) I noticed that there are 12 entries in the vector_store table, but the page_number field (in the metadata column) for all the entries is shown as 10.
`vector_store=# select metadata from vector_store;
metadata
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
{"file_name": "/target/classes/data/medicaid-wa-faqs.pdf", "page_number": 10}
(12 rows)`
Looks like the doSplitDocuments method in the TextSplitter class is generating this incorrect page_number for all the documents.

+1

Seems fixed by https://github.com/spring-projects/spring-ai/commit/6753e242e8f9fa5dfc8ee239ba2add6c1c2b6855 so can we close this issue?
https://github.com/spring-projects/spring-ai/pull/934 -> Enhance test about incorrect page number case

#934 is adding a test, and not changing any code.  The test is creating the metadata with the page_number explicitly and validating that it worked as expected.  What is reported in this issue looks to be a bug in PagePdfDocumentReader, so this issue should remain open.  Also, that sample app needs to be updated, I'll fix that.


[TRITON-MLIR][BACKEND]AtomicRMWOp supports scalar

AtomicRMWOp supports scalar

I would wait for additional comments from @ptillet , not sure if he has any suggestions on the test files.

I would wait for additional comments from @ptillet , not sure if he has any suggestions on the test files.

Do you mean if we should have seperate test files, or any other concern?

I would wait for additional comments from @ptillet , not sure if he has any suggestions on the test files.

cases such as smaller problem sizes that requires for thread level mask is currently marked as TODO, since there are know issues in the optimizer as we discusses.

Left a small comment but otherwise LGTM. Do you want to take a stab at fixing the bug in TritonGPU? This is almost surely happening here https://github.com/openai/triton/blob/triton-mlir/include/triton/Dialect/TritonGPU/IR/TritonGPUAttrDefs.td#L227

Left a small comment but otherwise LGTM. Do you want to take a stab at fixing the bug in TritonGPU? This is almost surely happening here https://github.com/openai/triton/blob/triton-mlir/include/triton/Dialect/TritonGPU/IR/TritonGPUAttrDefs.td#L227

Hi, Phil, do you refer to the issue in smaller problem sizes, where accum of warpsPerThread is not 32?

Yep I'm referring to that. I am prioritizing flash attention right now. I could take a look when I'm back at full work capacity in 8 days, but you might just wanna take a look since it seems like a very localized issue


Preserve context (logs, volume data) of cluster/pods when tezos nodes error

We need to be able to do meaningful investigations for some node errors postmortem.

related to #263 #264 #112


Update slick, slick-hikaricp to 3.5.0

About this PR
📦 Updates

com.typesafe.slick:slick
com.typesafe.slick:slick-hikaricp

from 3.4.1 to 3.5.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.slick" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.typesafe.slick" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:pvp, commit-count:1

Superseded by #611.


Vocabulary from ATHENA for Synthea data converted into OMOP CDM

https://ohdsi.org/software-tools/
ATHENA allows you to both search and load standardized vocabularies. It is a resource to be used, not a software tool to install. To download a zip file with all Standardized Vocabularies tables select all the vocabularies you need for your OMOP CDM. Vocabularies with standard concepts and very common usage are preselected. Add vocabularies that are used in your source data. Vocabularies that are proprietary have no select button. Click on the “License required” button to incorporate such a vocabulary into your list. The Vocabulary Team will contact you and request you demonstrate your license or help you connect to the right folks to obtain one.
ATHENA LINKS
Vocabularies: Click Here
Source Code: GitHub
“10-Minute Tutorial” Video: Click Here

Task marked done in the Project, so closing this issue


TSC Meeting 2022-01-26

Please add topics for the agenda as comments on this issue.
The standing agenda items are:

Review TSC issue backlog
Review TSC-tagged issues (toggle to "open" after checking for recently "closed" items)

@ampproject/tsc

Cancelling since there are no topics.


Bug: Failed to display anything and then wiped my file on restart

I tried to open a TODO.md file in vs code with run me installed. It didn't render any of the markdown. When I tried to restart the extension, it cleared everything in file.
I'm on Ubuntu 24 LTS x64 Linux using VS code v1.92.1

Sorry to hear! Could you please share the content of the TODO.md before it got wiped?

Sure, it was a very small file:
- Update the `extract_records` function in `src/llm_utils.py` to use the openai API.
- Remove all gemini dependencies


fix: interp var file

Must be merged after #75
Fixes

#56

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/terraform?version=dev:90526fd710b4796f75e59920fad01c89d31965d1


[Not sure] SVS Sync Interest with multicast forwarding hint

Since NDN testbed only has /ndn/multicast set to use the multicast strategy by default, to make our app work we had to make the whole workspace prefix be under /ndn/multicast. But this also multicasts Data Interests.
We want to support arbitrary workspace prefix. Maybe we should use forwarding hints to multicast SVS Sync Interests?

Since NDN testbed only has /ndn/multicast set to use the multicast strategy by default, to make our app work we had to make the whole workspace prefix be under /ndn/multicast. But this also multicasts Data Interests.

Sync group prefix and application data prefix can be chosen independently.
As an example, StateVectorSync C++ library chat example uses a sync group prefix that starts with /ndn/svs and allows each participant to choose a different prefix for published application data.

That leads back to the discussion on application namespace vs forwarding namespace...
This app uses application namespace for security and management, so all forwarding related thing should be expressed in ForwardingHints.

I'm afraid NFD would not treat ForwardingHint: /ndn/multicast as multicast Interest.
StrategyChoice lookup is based on PIT entry name i.e. Interest name, and ForwardingHint is not considered whatsoever.
Thus, the effective strategy would be whatever strategy that matches the Interest name.
NDNts side should be okay.
If you invoke fw.nodeNames.append(new Name("/ndn/multicast")), NDNts FIB lookup will use Interest name, so that incoming Interest with this ForwardingHint can reach the correct producer handler.

After discussion we think this is not the correct way to do things.


Add a URI replacement handler

Ok. How is the implementation for CSharp meant to work? Are there any constraints or would it be the same as this one?

It is meant to follow the typical middleware implementations with options and tracing. You can look at other languages including go to see how it was modeled.

So, the design for delegating replacement to a different type has to be changed?

Not by much I believe. It's mostly a matter of making the replacement keys and values configurable


As there hasn't been any activity over the past month on this repository, I forked it to fix some issues and implement the features I needed

As there hasn't been any activity over the past month on this repository, I forked it to fix some issues and implement the features I needed:

https://github.com/AmadeusITGroup/sonar-stash/commit/4c0f92861349704782f070390020bd4905992266 fixes https://github.com/AmadeusITGroup/sonar-stash/issues/25 (Comment "xxx" cannot be pushed to Stash like it does not belong to diff view)
https://github.com/AmadeusITGroup/sonar-stash/commit/2742d30de25bc04ee2b5ae2679a2b46c5b955680 implements https://github.com/AmadeusITGroup/sonar-stash/pull/20 (Make summary comment optional) + https://github.com/AmadeusITGroup/sonar-stash/commit/ccb6b80e7fd58e094b28de4a9dba42326bbbbe7d adds the ability to display a tiny summary while hiding the overview for the developer to be notified when the incremental analysis has been performed.
I also did some cleanup in terms of line endings, formatting, etc. to ease future contributions

Tell me if you're interested in merging this contribution or if I shall keep adding my new features on my fork.

Hello David,
For your information, we are working on next plugin version (1.1.0) which will integrates mainly issues #11 and #14. This version will be release at the beginning of next year but both features should be available before Xmas on master branch.
We have not planned to integrate #20 in release 1.1.0 but it could be a candidate for next version. Nevertheless, we are interested by your fix on #25 for version 1.1.0: could it be possible to open a dedicated pull-request with only this change?
Cheers,
Antoine

Hello David,
For your information, we are working on next plugin version (1.1.0) which will integrates mainly issues #11 and #14. This version will be release at the beginning of next year but both features should be available before Xmas on master branch.
We have not planned to integrate #20 in release 1.1.0 but it could be a candidate for next version. Nevertheless, we are interested by your fix on #25 for version 1.1.0: could it be possible to open a dedicated pull-request with only this change?
Cheers,
Antoine

Hi,
You can cherry pick https://github.com/racodond/sonar-stash/commit/4c0f92861349704782f070390020bd4905992266
Regards,
David

This pull-request can be closed: we will open dedicated Pull-requests to integrate #20 and #25.

Linked to Pull-resquest #24


Config does not handle boolean values

Version:  0.7.0
In the process of writing a plugin, we've run  into a bug wherein config values added to lemur.conf.py cannot reliably be set to boolean False.   It appears that if a var is so set, the following prevents the config from loading and yields mysterious exceptions that don't easily trace back to this problem.
def validate_conf(app, required_vars):
    """
    Ensures that the given fields are set in the applications conf.
    :param app:
    :param required_vars: list
    """
    for var in required_vars:
       if not app.config.get(var):
            raise InvalidConfiguration("Required variable '{var}' is not set in Lemur's conf.".format(var=var))

The problem is that if CONFIG_VAR is False, if not app.config.get(var) will return False and raise InvalidConfiguration.
Should it not be  if var in app.config, which would confirm existence of the key, not let its value interfere with the validation?

This seems totally reasonable. I have a PR up at https://github.com/Netflix/lemur/pull/1630 .

Merged. Please let me know if this doesn't resolve your issue.


.news not working

When trying to access the .news element I'm getting an error.
I've tried multiple approach but all the same outcome.

There is no attribute called news, only the attribute _news or the the method news.


Allow setting value of 'automountServiceAccountToken' in pod helm template traefik v2

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
Version: v26.1.0
Traefik chart doesn't have an option to set a value to 'automountServiceAccountToken' on pod level.
This makes a traefik deployment on an AKS with policies not compliant, the pod will be marked as a non-compliant resource.
Affected policy: 'Kubernetes clusters should disable auto-mounting API credentials'
To reproduce:
kubectl exec traefik-pod cat /var/run/secrets/kubernetes.io/serviceaccount/token
This outputs the secret token.
Manually setting this property on the service account results in traefik not functioning properly and pod settings takes precedence.
Expected reflection of an example pod:

apiVersion: v1
kind: Pod
metadata:
name: traefik
spec:
serviceAccountName: traefik
automountServiceAccountToken: false

Expectation of policy:
traefik pod is shown as compliant / not shown as non-compliant.

Hello @mloiseleur,
thanks for your response that was helpful, when I manually set this property in the used service account, resources can't be read. I would have to implement a mechanism to manually mount the token and then handle the rotation/expiration of this token. I think this is not a proper solution.
Let me discuss this topic, then I will either do a PR or just close it.
Thank you!

Since there is nothing to do on the Chart, I close this issue.
Feel free to re-open if I missed something.


[REQUEST] Implement semantic verification of fields price ans transfer_duration in fare_attributes.txt

Is your feature request related to a problem? Please describe.
These numeric fields should be user configurable so that suspicious values can be reported.
Describe the solution you'd like

[ ] Add new Warning notice:

SuspiciousPriceNotice
SuspiciousTransferDuration

[ ] Add support to provide thresholds for these fields values via configuration file and/or command line

[ ] Determine default values for said thresholds

No semantic validation of fields yet, per discussion.


Memory problems at scale

@vitorheidrich raised this issue on the qiime2 forum where the silva database was failing to solve the database due to memory issues.
As a proposed solution, one option is a re-factor to run the command through dask - which may be more memory efficient.  Pros aare thta we are no longer limited by trying to solve the 1M seq dataframe. Potential cons are that it probably means breaking out the database step and will be slower for smaller databases.

I think I have a solution. @vitorheidrich, will you try and see if it works for you? It may be easiest to access via Git and then just check out the branch.
https://github.com/jwdebelius/q2-sidle/tree/memory-refactor
If preliminary testing, I was able to reconstruct the Silva database you gave me in like 15 minutes with 4 cores on my macbook with nothing dedicated, so hopefully 🤞 it works. However, this also represents a major refactor, so I updated the docs as well:
https://q2-sidle.readthedocs.io/en/memory-refactor/index.html
There's a fairly good probability of typos in the new docs, but when I ran everything through the tutorial, it worked. (They will need to be updated to fully work, you need to sub the branch name fo the download.)
Give it a whirl and please me know how it works for you.

That's great news! Thank you for looking into this
I'll give it a try later this week and I will let you know how it goes

It worked! With those regional databases + default parameters it took 90min to finish the database reconstruction.
Really cool solution. Once again thank you very much for your efforts with this plugin!

Im glad! And 90 min feels reasonable? I think you could increase the cores (default is 1 iirc) but Im not sure I could easily speed up the code by that mucch.

I definitely could use a much higher number of cores, but I just wanted to test if the process would finish (whichever the running time would be), so honestly I am just glad it worked.

Closed via #27


Fix Find Garages by IP address

Describe the bug
Find Garages using IP Adress doesn't work.
To Reproduce
Steps to reproduce the behaviour:

Go to 'https://parkify-web.herokuapp.com/garage/find/
Click on 'Find by IP'
'Internal Server Error' Appears.

Expected behaviour
Find the nearest garage and show the location on the map.

Sure. Do tell me if you need any help with the setup. :)

Done


feat (sync-service): support OPTIONS requests

This PR fixes https://github.com/electric-sql/electric/issues/1646 by adding support for HTTP OPTIONS requests.

@robacourt Current implementation accepts all origins by explicitly allowing the provided origin (when provided as an origin header in the request). I chose to implement it like that because access-control-allow-origin: * only works for requests without credentials. So this looked to be a more robust way of accepting any origin.


Speed up processing of small row datasets with ProcessPool

We use pyarrow serialization instead of standard pickling. Unfortunatelly, pyarrow serialization
does not support decimals, so we modify the codec to decode decimals always as strings.
Updated all tests to reflect the decimal->string behavior.

Added documentation to codecs.py, although it is not very visible. Will need to work on a better user guide.


Removed dotnet command suffix (.exe) and changed to lowercase

The dotnet command need to be lower case and without the .exe suffix in order to run on *nix

merci


KAFKA-12738: address minor followup and consolidate integration tests of PR #11787

This PR addresses the remaining nits from the final review of https://github.com/apache/kafka/pull/11787
It also deletes two integration test classes which had only one test in them, and moves the tests to another test class file to save on the time to bring up an entire embedded kafka cluster just for a single run

Test failures are unrelated, will merge

Merged to trunk


[Question]

what are the admin commands for this gamemode

There are no chat commands. Users with ULX ranks of admin, superadmin, or owner will spawn with the godstick SWEP. It looks like a police baton. Right click while holding it to see the admin powers. Select an item from the drop down menu, then left click to perform the selected action.

ok thanks thought the godstick was just for invulnerablity


Normalize full key name to avoid resource update on identical key names

Description
We have multiple apt repositories that have key names similar enough so the cookbook treats them as the same when performs remote_file cache (due to regex below).
Issues Resolved
This PR makes sure that remote_file caches remote key with a unique name and thus avoids updating resources on every chef run.
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] The CLA has been signed.

Apologies for bumping this: do you think it's something that makes sense @tas50 ?

Concept seems sound. Passing this over to @thommay as he worked on the cookbook last

Friendly bump 👋 : does anyone have objections of shipping this? We've ran it successfully on production for couple of months already.

@bai If you made this same PR against chef/chef ( https://github.com/chef/chef/blob/master/lib/chef/provider/apt_repository.rb#L156 ) we'd take it there, and then it'd get propagated out with compat_resource . In the not so long term we'll remove these resources from the cookbook.
Sorry for the slow response!

Thanks for taking your time explaining this @thommay — I've just created a similar PR at https://github.com/chef/chef/pull/5290

awesome, thanks. Closing this now.


Bug: SyntaxError: Invalid regular expression: /~/**/: Nothing to repeat

Describe the bug
After upgrading to 4.0.1. I get this error.
SyntaxError: Invalid regular expression: /~/**/: Nothing to repeat
Occurred while linting /Users/me/project/app/hooks/useClickOutside.ts:1
Rule: "perfectionist/sort-imports"

SyntaxError: Invalid regular expression: /~/**/: Nothing to repeat
Occurred while linting /Users/me/project/app/hooks/useClickOutside.ts:1
Rule: "perfectionist/sort-imports"
    at new RegExp (<anonymous>)
    at Module.matches (/Users/me/project/node_modules/eslint-plugin-perfectionist/dist/utils/matches.js:3:35)
    at /Users/me/project/node_modules/eslint-plugin-perfectionist/dist/rules/sort-imports.js:172:57
    at Array.some (<anonymous>)
    at matchesInternalPattern (/Users/me/project/node_modules/eslint-plugin-perfectionist/dist/rules/sort-imports.js:172:33)
    at registerNode (/Users/me/project/node_modules/eslint-plugin-perfectionist/dist/rules/sort-imports.js:233:39)
    at ruleErrorHandler (/Users/me/project/node_modules/eslint/lib/linter/linter.js:1076:28)
    at /Users/me/project/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/Users/me/project/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
Process finished with exit code -1

Code example
No problem with latest 3.x build but 4.0.1 crashes on every file.
ESLint version
8.57.0
ESLint Plugin Perfectionist version
4.0.1
Additional comments
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Sorry it's our problem.

Looks like the internalPattern was changed from:
internalPattern: ['~/**']

to
internalPattern: ['^~/.*'],

This fixed it.

It looks like the previous internalPattern setting ['~/**'] is no longer valid. My project is remix, which uses ~ tilde as the prefix for internal packages.
Here is my rule configuration. I want react types and then react packages to always come first. When I change the internalPattern to the new default ['^~/.*'], it sorts external packages that start with @ before everything.
'perfectionist/sort-imports': [
  'error',
  {
    type: 'natural',
    internalPattern: ['~/**'],
    newlinesBetween: 'never',
    groups: [
      'react-type',
      'react',
      'react-other-type',
      'react-other',
      ['external-type', 'external'],
      ['builtin-type', 'builtin'],
      ['internal-type', 'internal'],
      ['parent-type', 'parent'],
      ['sibling-type', 'sibling'],
      ['index-type', 'index'],
      'side-effect',
      ['object', 'unknown'],
      'style',
    ],
    customGroups: {
      value: {
        react: ['react'],
        'react-other': ['react-*'],
      },
      type: {
        'react-type': ['react'],
        'react-other-type': ['react-*'],
      },
    },
  },
],

This seems to me to be a bug since the custom group docs state that you can put react first, but the default internalPattern regex does not honor the group order.

We've also got this error:
SyntaxError: Invalid regular expression: /=== ** ===/: Nothing to repeat

Rule definition:
'perfectionist/sort-enums': ['error', { partitionByComment: '=== ** ===' }],

Hi @alfaproject
** is not a valid regular expression. The error is expected.


Groups inheritance by world doens't work

Groups don't inherits permissions in inherted worlds.
Small setup to reproduce
Create a server with two worlds : world1 and world2
Make world2 inherits from world1
Create group User
Create group Admin which inhertis from User
Add permission node minecraft.command.op to User group in world1
Set the group of a player user to User
Set the group of a player admin to Admin
What's happening :
As expected, the player user can /op himself in world1 and world2 because world2 inherits from world1
However the player admin doens't have acces to /op command neither in world1 or world2
What I expected (inheritance) :
Because the player admin inherits from the group User and the group User has access to /op in world1, any user in group Admin should have access to /op in world1. Furthermore because world2 inherits from world1, admin could also /op himself in world2. This is only simple inheritance logic.
Conclusion
It is really an annoying issue, because when I add a permission to a low level group in a specific world, I have to add the same permission in the same specific world to other groups that inherit from that first group.
The logical inheritance behavior in my opinion would be that a group also inherits the worlds permissions from its parents groups.
Thank you

Could you add a comment with your permissions file as I think this would supply clarity.

I am using the SQL backend. It's a bit hard to show you that.
I'll do some testing again.

Ahh right, from what you wrote it confused me a little. You wrote:
Create group Admin
Create group User which inhertis from Admin
Which would mean User inherits from Admin.
Which means User gets all of the same permissions as Admin. Surely you would want this the other way around? Admin inheriting from User. Meaning an Admin can do everything a User can and then you add permissions that you only want an admin to use.
Forgive me if i'm spelling out the obvious. :smile:

Yes , you're right. Admin inherits from User

That's unrelated to your problem though?

I'm going to check that tonight, I'll get back to you. Maybe it's a mistake of mine.

User error is almost always the cause of problems. ;)


Not playing music when hosting on ubuntu

I downloaded a music bot and tried to run it on my Windows computer. It worked fine, but when I tried to host it on my Ubuntu VPS, it only said 'Now playing:' and immediately said 'Queue is empty. You can play some more music, byebye... ✅'

try uninstalling ffmpeg-static
npm uninstall ffmpeg-static
npm ci
npm update
Then install ffmpeg using npm install ffmpeg. This worked for me


Fix typo in return type of nd_item::get_group_range(size_t)

Fixes the return type of nd_item::get_group_range(). Issue was reported in #380.

All CPU and CUDA unit tests pass:
https://github.com/hipSYCL/hipSYCL-ci-bot/actions/runs/386121581


Update AudioDispatcher.java

Actually play the file

Sorry about the poor documentation. first time ever submitting a pull request :)

@haimomesi Hi :)
What your PR fix, or what feature you want to add?


Question: How to use gateway when auth is enabled

Tried curl as per
https://github.com/coreos/etcd/blob/master/Documentation/dev-guide/api_grpc_gateway.md
Couldn't figure out a way to use this when auth is enabled.

duplicates #6643


GE: Nodes are intermittently losing their "Free to use" status

On multiple occasions, we have noticed that some nodes lose their "Free To Use" status. I routinely go through all nodes and double check that they are free to use.
As an example, Herbert noticed that these two nodes had lost their free to use status this morning, and I have now switched them back on:
Salsburg: FLeByELHK22evRYqJokHsCMCF9wQpLtuyehUp1LgR5eM
Vienna 1: HnfiAFsUedqRdpdccj9BeKDuZsevpaDQuAWrHP9MHiZU

Possibly related to (and solved by) https://github.com/threefoldtech/tfexplorer/pull/82

I was thinking the same. We need to test if this still happens with this version of the explorer


how can i get printer_error/triplets/ps541_60.txt

I will appreciate your help

So you need to generate this for your printer. This file in particular was generated for our own printer. Also, you should not need it to run our code.

down


Convert SpatialPointsFrame to a Dask DataFrame subclass

Addresses https://github.com/pyviz/datashader/issues/705
This PR converts the SpatialPointsFrame class into a subclass of dask.dataframe.DataFrame to simplify the integration with existing libraries such as Holoviews.
The existing properties have now been prefixed by spatial_ to reduce the likelihood of collisions with dataframe columns.
cc @philippjfr

Great! I'll try it out shortly.

My main concern is about the persist method, can we load a dataframe and then persist it without discarding the metadata?

that’s a good point, having persist preserve metadata and stay a SpatialPointsFrame makes sence. I’m done for the night but feel free to make any updates you want in the branch.

So a Dask DataFrame doesn't have an idea of what class it is and a method to create a new object of that same class when a new object is returned?  That seems like something that should be addressed in Dask if it uses methods in that way, so that it's practical to subclass, though of course we can work around it here.

Even if it did, there'd be several problems, first of all this implementation now overrides the __init__ to create the dataframe from a file. I think that should be refactored to reproduce the standard constructor but also require the metadata to be passed in. I would then move the logic to load the data from parquet to a separate classmethod, which constructs the SpatialDataFrame for you. However even when that's done and we could have dask try to make new instances of the class it still wouldn't know about the spatial metadata and copy it. I'll play around a bit and see what I can suggest, but I don't think we'd get away without at least some magic.

However even when that's done and we could have dask try to make new instances of the class it still wouldn't know about the spatial metadata and copy it.

The idea would be to provide a copy constructor that can be extended by the subclass to copy the metadata as well.  I.e., the subclass would still have to extend some bits, but only the methods that it's actually extending would need to be implemented at that level.

Starting to make some progress, one issue is I've been getting typing are typing errors from _build_partition_grid these go away when I remove the ngjit decorator. Secondly, dask is creating new SpatialPointFrame instances but breaking because the constructor's signature is different.
I'll shortly push an update which adds a proper constructor and moves the loading code into a from_parquet staticmethod. I'll have to think of a nice solution for copying the spatial metadata though.

Okay just pushed a new commit. I reorganized the constructor, moved the code to SpatialPointsFrame from a parquet file to a from_parquet staticmethod, and implemented a working persist method. All other methods seem to construct a regular dask.DataFrame, which I think is okay for now.

And here it is working from holoviews (the print output is checking the type inside the canvas.points call):

Oh and to make it all work I've given the subclass a _spatial attribute, which determines whether the spatial metadata is available and disables the spatial features if not. This ensures that a user decides to construct a SpatialDataFrame themselves or some functionality in dask makes a copy of the object it'll still work as normal, but raise errors when trying to use the spatial features.

I think I'd still prefer it if we made a spatial accessor namespace to avoid polluting the DataFrame namespace. I also think query_partitions could be renamed, I don't think it's necessarily relevant to a user that it's querying partitions would spatial_query or if we were to namespace it spatial.query be okay? Unless you think that's misleading since it doesn't guarantee that only points within the queried region are returned.

I think I'd still prefer it if we made a spatial accessor

That's fine, I'll add a SpatialProperties class to encapsulate these

spatial_query or if we were to namespace it spatial.query

I think sframe.spatial_query makes sense since this is truly a method on the dataframe, whereas everything else in spatial. will use property syntax.

Sounds good.

Not sure how I managed to push broken syntax, guess I didn't test it after I did a last refactor. Sorry about that.

No problem!
Are you still having trouble with jit on _build_partition_grid?  It seems to be working for me now.

Definitely still seeing the jit errors, I'll try again by building a new file in a second but here's what I'm seeing:
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function(<class 'list'>) with argument(s) of type(s): (())
 * parameterized
In definition 0:
    All templates rejected with literals.
In definition 1:
    All templates rejected without literals.
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: resolving callee type: Function(<class 'list'>)
[2] During: typing of call at /Users/philippjfr/development/datashader/datashader/spatial/__init__.py (676)

File "../../datashader/spatial/__init__.py", line 676:
def _build_partition_grid(dask_divisions, p):
    <source elided>
    search_divisions = np.array(
        list(dask_divisions[1:-1]))
        ^

numba version?

> numba.__version__
'0.41.0'

Hmm, I'm on 0.42.0. Do you want to try that version?

No change, still errors even after I try building a new parquet file. That said the fix is pretty simple, I just cast the tuple to a list outside the function, i.e.:
self._partition_grid = _build_partition_grid(
            list(self._distance_divisions), self._p)
...
search_divisions = np.array(dask_divisions[1:-1])

Great, I'll make that change as well

@philippjfr I made those updates. Let me know if you any other thoughts on the API. The changes so far have been a definite improvement 🙂

Thanks for doing that, I'm very happy with it now. Having it just work once loaded is really nice. Let's see what @jbednar, otherwise I'm happy for this to be merged.

Can you point me to the current syntax for making the parquet file be sorted, then how to load it?

Here you go:
# Partition and save
ddf = dd.read_parquet('/Users/philippjfr/development/datashader/examples/data/nyc_taxi_wide.parq').persist()
spf = SpatialPointsFrame.partition_and_write(ddf, 'pickup_x', 'pickup_y', compression='snappy')

# Load
spf = SpatialPointsFrame.from_parquet('./nyc_test.parq/').persist()

Can you please add a file-format version identifier of some sort to the metadata in the Parquet file so that if we extend it in the future, we'll be able to detect that an old file has incomplete or incorrect metadata?

Already there from the last PR:
https://github.com/pyviz/datashader/blob/231364fb7eacb6866ab11733694491afc49bee21/datashader/spatial/__init__.py#L286-L294
I've been bit by this in the past when defining custom file formats 🙂

Leaving the last two comment for @philippjfr to weigh in on.

Already there from the last PR:

Great! Somehow I missed that.

Added fix for when Canvas is in auto range mode (x_range or y_range not specified).
I have to run, so feel free to make any docstring changes before merging, or I can pick it up again this evening.

@jbednar I've updated the docstring, ready to merge from my perspective.


[MINOR][BUILD] Remove duplicate configuration of maven-compiler-plugin

What changes were proposed in this pull request?
<release>${java.version}</release> and <maven.compiler.release>${java.version}</maven.compiler.release> (https://github.com/apache/spark/pull/46024/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R117)
are equivalent duplicate configuration, so remove <release>${java.version}</release>.
https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-release.html
Why are the changes needed?
Simplify the code and facilitates subsequent configuration iterations.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @LuciferYang @dongjoon-hyun

Sorry for being late. I missed your ping here, @zml1206 .

Thank you for review. @dongjoon-hyun


Store#select() method should be changed

Store interface has 2 methods:
    List<Material> select(JobName jobName, JobTimestamp jobTimestamp,
                          MetadataPattern metadataPattern)

    List<Material> select(JobName jobName, JobTimestamp jobTimestamp,
                          MetadataPattern metadataPattern, FileType fileType)

I think these 2 are not good. I only need one. And the FileType should be the 3rd argument, like Store#write() method.

I realized that I need both of 2 select methods. I need the select method without FileType.


add effect frame

ref：https://github.com/zzxyb/wsm/blob/master/effects/wsm_effect.h

[ ] Add public post-processing special effects，Support window effects and screen output effects，Support OpenGLES、Vulkan、Pixman
[ ] Incorporate window screenshot and recording functions into post-processing effects，ref protocol：https://github.com/zzxyb/wsm/blob/master/protocols/wsm-surfacecopy-unstable-v1.xml
[ ] add window radius、border effect
[ ] add window shadow

LGTM


[event-hubs] Removed checkpointstore sample and reference it instead

The checkpointstore sample in event-hubs introduces a circular package dependency in order to be built. This sample already exists in TS in the checkpointstore package, so remove it from this package and reference that instead. I included a comment in receiveEvents.js and receiveEvents.ts pointing to the other sample on GitHub.
I also converted the TS sample in checkpointstore to have a CommonJS-compatible copy as well, which is referenced in the TS version of the receiveEvents sample.

Make a check that there is no stale link in the package readme for event hubs to the checkpoint store sample

I removed all the dead links in the README to the outdated samples as well as the link definitions at the bottom. The only place "checkpoint" appears in the samples directory is in the link to the checkpointstore repo that I added to the receiveEvents files.


mermaid shortcode doesn't render the nested box for a subgraph.

shortcode doesn't render the nested box for a subgraph.
works fine here
https://tinyurl.com/y4ge79rh

but not within hugo shortcode.
{{< mermaid class="text-center">}}
flowchart TB
    c1-->a2
    subgraph one
    a1-->a2
    end
    subgraph two
    b1-->b2
    end
    subgraph three
    c1-->c2
    end
{{< /mermaid >}}

Do you mean the yellow background? That might be related to the mermaid theme we use.

Fixed. If that's not what you requested, please let me know.

Finally got around to looking at your fix.  Yes it's good.  now subgraph boxes are "visible".  Thx.


Appendix A: browserspy.dk available via https

You can update the link and descriptive text to https.

finally .. i remember checking that only a few weeks ago. Done


Git tags are not valid semvers

Impossible to use conan version ranges because the git tags are not valid semver because of the 'v' prefix.
See https://docs.conan.io/en/latest/versioning/version_ranges.html.
Steps to reproduce:

Specify "nlohmann_json/[~=v3.9]@clickshare/stable" in
Error upon build is:
 ERROR: Version range '~=v3.9' from requirement 'nlohmann_json/[~=v3.9]@project/stable' required by '...' could not be resolved in local cache

It seems the documentation is not up-to-date as it says use nlohmann_json. I found in an earlier bug report to use jsonformoderncpp from vthiery. Anyway that works for me but the latest version is 3.7.3.

The Page you linked do not mention git tags. This page (https://git-scm.com/book/en/v2/Git-Basics-Tagging) describes that adding a v-prefix is common practice. I am not sure why this is a problem with Conan.

You're right, it's mainly git tagging which is not compatible with semver. Looks like only the v is the problem 🙄.

I don't really see a problem.

Looking at https://semver.org/ I find
No, “v1.2.3” is not a semantic version. However, prefixing a semantic version with a “v” is a common way (in English) to indicate it is a version number. Abbreviating “version” as “v” is often seen with version control. Example: git tag v1.2.3 -m "Release version 1.2.3", in which case “v1.2.3” is a tag name and the semantic version is “1.2.3”.

so IMHO it is conan's job to support v prefixes.

Closing this issue as it is not related to this library.


MERC-8927 Related products query

Fix related products to respect custom related products from Control Panel.
Currently the related products field is not being respected from the Control Panel. This change is to pull the related products data from the individual product and to display the correct related products on the PDP (Product Details Page)
Customized Related Products from CP

Updated Related Products on PDP

Hey there! Thank you for your contribution. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: https://github.com/vercel/commerce/pull/966


Sidebar main element still do not fill the whole height

@avoinea do you know what we changed there for it to behave different now?

@avoinea it seems #2292 fixed some things but also broke others. Where it was wrong (the sshot in the PR)? Can I have a look? I think that we might need both:
    height: 100%;
    min-height: 100%;

@sneridagh Indeed :disappointed:
One solution would be to remove the raised segments but maybe there is a better one out there.

For quanta we should re-visit it, for sure. However, can I take a look where it fails with the height?

@sneridagh It was mostly within InlineForm but I already removed the raised and segments here https://github.com/plone/volto/pull/2295/files#diff-152a160265a543b914f56865c5c6b77c87866f006303b0682d087b90e2b675daR41
Thus, I think we can revert it to height: 100% and then look for a better fix if it replicates elsewhere.


Bring Metadata Library back!

Is your feature request related to a problem? Please describe.
Since both Python client and Go service library share the schema models for mlmd types, there should be only one source of truth for creating/using types and for testing.
Describe the solution you'd like
Bring back the yaml metadata library definitions and mapper from the older GraphQL code base to restore the metadata library feature.
The library can be used for:

Generating Go and Python types to keep them aligned
Initializing mlmd on REST service startup
Optionally Go/Python/ROBOT framework test code could also be potentially generated to validate that all fields are used and supported

Describe alternatives you've considered
Keeping ml metadata schema synced in separate Go and Python codes and tests is not maintainable in the long run as the number of types increase.
Additional context
None

I think this will be of convenience as we will eventually modify our entities (eg ModelArtifact) for instance to add new fields etc.
Or even for new entities.

Optionally Go/Python/ROBOT framework test code could also be potentially generated to validate that all fields are used and supported

On other hands, as explained in the meeting, this won't necessarily detect other types of misalignment such as https://github.com/opendatahub-io/model-registry/issues/206
Based on these, I would conclude this is important but not our top priority atm; unless I missed something!


migration: restore status on re-create

When re-creating a v1alpha1 Hive resource, perform an update after the create so that the status is re-created as well.

/lgtm


Add whois.nic.google

Add support for .app, .dev, .how, .page, .soy (www.registry.google)
Update xn--q9jyb4c (.みんな) to use whois.nic.google

Thanks for this @derekjc! for the record I ended up starting my fork in which I merged some of the pending PRs (including yours slightly adapted in 547709393e1becef4aad576833e606b239e9ca55) and more fixes to come. So people who need this can use my fork in the meantime:
gem 'whois-parser', github: 'jarthod/whois-parser' # Unofficial but more up-to-date fork, check status at https://github.com/jarthod/whois-parser


[SPARK-45811][PYTHON][DOCS] Refine docstring of from_xml

What changes were proposed in this pull request?
This PR proposes to improve the docstring of from_xml.
Why are the changes needed?
For end users, and better usability of PySpark.
Does this PR introduce any user-facing change?
Yes, it fixes the user facing documentation.
How was this patch tested?
Manually tested.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.


Fixing tests after upstream change in YAROM

Coverage decreased (-0.2%) to 77.95% when pulling e0daf0c00c5050d75acd6dc38ca4843be752b8d1 on quickfix/limit-yarom-dependency into 87dead2e828f74c0c0aecc32899b7571044aab85 on master.


ATLAS-3661 Create 'spark_column_lineage' type and relationship definition

What changes were proposed in this pull request?
Create spark_column_lineage type and relationship definition to add support of column level lineage for CREATE TABLE AS SELECT ... statements and views. Column level lineage refers to lineage created between the input and output columns.
For example:
hive > create table employee_ctas as select id from employee;

For the above query, lineage is created from employee to employee_ctas, and also from employee.id to employee_ctas.id.
How was this patch tested?
Manually using modified version of Spark Atlas Connector:

Installed and started Atlas.
1100-spark_model.json is updated with proposed changes. Atlas is restarted.
Executed the next statements using spark-shell:

spark.sql("create table sparkemployee_1_2(id int,name string)");
spark.sql("create table sparkemployee_ctas_1_2 as select id from sparkemployee_1_2");

Verified that each table has column entities and spark_column_lineage entity is created.

Attaching screenshots.

cc @HeartSaVioR @sarathsubramanian

+1 for PR, thanks @vladhlinsky for PR.

what version is spark-atlas-conection used

What version does spark-atlas-connector use?

What version does spark-atlas-connector use?

@lyyprean @CavalierHE
I think cloudera has not open sourced it yet, and completely hiding the implementation of column lineage harvester!

@lyyprean @CavalierHE
I think cloudera has not open sourced it yet, and completely hiding the implementation of column lineage harvester!

maybe，how about apache？


Documentation to use timer in Countdown

@itaditya I would love to help with this. I am trying to use your project to display a countdown timer. I would start the timer at 00:05:00 and then countdown with the circle decrementing instead of incrementing, however I cannot get this to work. Do you have any suggestions?

If I use counter :"-1000" I do get a decreasing display but only in quadrant 1 of the circle. Additionally the time starts at 23:59:59 and the decrease does not appear to be in seconds.


ringback on sip response 180

When using same the output for player and alert, the ringback when sip 180 is received results in call not possible to establish. This due to the sound card is busy playing sound files in one format, and opus tries to set the card in another format.
I'm not sure If problem exist if using G711 or other 8kHz codecs. But we are having problems when using opus.

this was implemented in commit e223601e6ac48e0c4829c77c016a38ee21b5633a


NDEFRecord.text causes NSInternalInconsistencyException when writing on iOS

For some reason using NDEFRecord.text or NDEFRecord.custom with type "T" and TNF Well Known when writing on a tag on iOS causes an exception listed below:
2019-10-22 09:57:47.847897+0300 Runner[269:5769] *** Assertion failure in +[NFCNDEFPayload wellKnowTypeTextPayloadWithString:locale:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreNFC/Stockholm-300.59.2/CoreNFC/NFCNDEFPayload.m:188
2019-10-22 09:57:47.848353+0300 Runner[269:5769] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Please use -wellKnownTypeTextPayloadWithString:locale: replacement'
*** First throw call stack:
(0x180f4c98c 0x180c750a4 0x180e4ed1c 0x1812848f4 0x1a964cbd0 0x102599ca8 0x10259b0a4 0x102597b6c 0x1025976f4 0x104489828 0x10448ac04 0x104491b74 0x104492710 0x10449dae4 0x180c69fa4 0x180c6cae0)
libc++abi.dylib: terminating with uncaught exception of type NSException

Other TNF's do not seem to cause this with same payload. However, my tags work only with Well Known type T write messages (tested with Android) so I would appreciate, if someone have more insight on how to fix this.

I am about to take a closer look.
I think the error occurs between line 391 and 395 in NfcInFlutterPlugin.m.

You are most likely right. After searching, I think that wellKnowTypeTextPayloadWithString should probably be changed to wellKnownTypeTextPayloadWithString on row 393. wellKnowTypeTextPayloadWithString is marked depracated and that is probably the exception is thrown.

Good spot!
Replacing it with wellKnownTypeTextPayloadWithString seems to do the trick.
- wellKnowTypeTextPayloadWithString
+ wellKnownTypeTextPayloadWithString

The only difference is a 'n'. I wonder if it was a typo 🤔
I'll release a new version with the fix shortly.

I have released version v2.0.1 with the fix.

Nice, thank you!


Cli support

Codecov Report

Merging #1 into master will decrease coverage by 16.62%.
The diff coverage is 19.04%.

@@              Coverage Diff              @@
##             master       #1       +/-   ##
=============================================
- Coverage     84.81%   68.18%   -16.63%
- Complexity       36       44        +8
=============================================
  Files             6       10        +4
  Lines            79      110       +31
=============================================
+ Hits             67       75        +8
- Misses           12       35       +23

Impacted Files
Coverage Δ
Complexity Δ

src/Composer/EventHandler.php
0% <0%> (ø)
1 <1> (?)

src/Composer/ComposerOutputAdapter.php
0% <0%> (ø)
2 <2> (?)

src/Console/FormatCommand.php
0% <0%> (ø)
2 <2> (?)

src/Console/ConsoleOutputAdapter.php
0% <0%> (ø)
2 <2> (?)

src/Console/Application.php
0% <0%> (ø)
1 <1> (?)

src/Wingman.php
100% <100%> (ø)
10 <3> (+3)
:arrow_up:

... and 1 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 0363ba7...2746c53. Read the comment docs.


VisLeafletFlowMap: Invalid LatLng object: (NaN, NaN)

This error occurs when calling fitView on the component
Error in<EMAIL_ADDRESS>(1365:11)
Invalid LatLng object: (NaN, NaN)

Using firefox on mac
Instructions to reproduce:

Load the following stackblitz https://stackblitz.com/edit/react-ts-m4jm7q?file=App.tsx
Replace <maptiler-key> with maptiler kay
Click the toggle button in the web preview

@rokotyan Thanks for the response, this resolved my issue


Some title

Some description

The Buildbot has detected a new failure on builder example-builder1 running on example-worker1 while building root at step 2 "shell".
Full details are available at: http://<IP_ADDRESS>:8011/#/builders/103/builds/61
Here is the relevant piece of the build log for the reference:
Step 2 (shell) failure: 'trial hello' (failure)
...
builtins.AssertionError: 'hello err world' != 'hello world'
- hello err world
?      ----
+ hello world

hello.test_hello.TestHello.test_world_unicode
-------------------------------------------------------------------------------
Ran 2 tests in 0.097s

FAILED (failures=2)


added-jimages

issue: #530
I have also fetched the latest commits.
Proposed Changes

Additional Info
I have uploaded all the photos and converted them to appropriate heights.
Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the documentation.
[x] 🎀 I have updated the documentation accordingly.
[x] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes here
Image goes here

Please open all the links to new tab, it isn't looking good at the bottom with infinite clicks

Means the pictures

Are you telling about pictures


Exporting routes to PDF throwing an error.

Generating PDF
Error generating report
Cannot read properties of undefined (reading 'styles')

Does anyone encounter the same issue as mine

Can you confirm what version of the application you're using? In the recently released 4.4.0 branch we did some improvements to the PDF export process so want to double check if this is still an issue in the latest release or not.

Hi @jasonmccollumwoolpert I'm using 4.4.0 right now. Let me try to use the previous version to check if this is the issue of the latest version.

Just released v4.4.1, which should address this issue. Can you try updating your deployment and confirm?

Hi @jasonmccollumwoolpert
It works perfectly! Thank you for the help


bug: fetch failed

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.8.3
Operating system/version
MacOS Ventura 13.2.1 (Apple M1 Max)
Describe the bug
I've found that on Mac machines (M1 or Intel), fetching Git repositories (through sync or similar) sometimes does not work, and I have to keep re-running the same check/update/sync command in order for it to go through. Perhaps there needs to be a lower max number of concurrent jobs like on packer, although I'm not sure what the exact issue is.

Steps To Reproduce

Open Lazy with :Lazy
Press S to sync (or U or C)

Expected Behavior
Sync goes through with no errors, plugins are updated accordingly
Repro
Could be a flakey git issue since this only sometimes happens, unlikely config related.
Config can be found here though: https://github.com/axieax/dotconfig/blob/main/nvim/lua/axie/lazy/init.lua

That's something on your machine. Not a lazy.nvim bug. Try setting concurrency to a low number like 10 to resolve this.

I am also facing this issue in a M1 machine :(

I also ran into this recently. Started getting the fetch failed mentioned in the title for no apparent reason. Like @canvanaut I also ran into a similar problem with packer a while back (see https://github.com/wbthomason/packer.nvim/issues/746#issuecomment-1256096146).
Glad to say that setting the concurrency to 50 solved it for me! So I think it's safe to say that this definitely isn't a bug in lazy.nvim but in macOS (or something in between the two anyways).

I've only just stumbled into this issue after using lazy for a while now. Not sure why I would suddenly starting seeing this issue.
You mention setting a concurrency? Where about should this be set?
-- I WAS USING...
-- require("lazy").setup("plugins")

-- I THINK I SHOULD BE SETTING...
require("lazy").setup({{import = "plugins", concurrency = 10}})

If the above is correct, that made no difference. Like I say I've never had this issue before with lazy.nvim so it's surprising it has just started happening 🤔

The above isn't correct. It should be:
require("lazy").setup("plugins", { concurrency = 10 })


Create Definition of Done

Not required, see: https://github.com/SSWConsulting/SSW.Rewards.Mobile/issues/435


Document when flutter packages get + pod install need to be run in add-to-app

It's currently easy to break the Flutter module <-> iOS outer app connection which requires rerunning flutter packages get in the flutter project folder followed by pod install in the iOS project folder.
Either document them (such as when changing pubspec, when moving directories #34294) or make it less fragile (perhaps via #32993)

@xster how is this resolved? Running flutter packages upgrade, then flutter packages get then be pod install still doesn't work.

What's the error message exactly?

no errors afaik, those commands randomly stop updating the integration, even wiping the Pods folder doesn't work

deleting Derived Data seems to do the trick 😬

Merging into https://github.com/flutter/flutter/issues/32862


Wrong Output

Does anyone has values of bottom_threshold and frame_length for which the script is working perfectly. I tried my luck but not getting the results.

@akib-islam did u try ?
If got the perfect values , pls post it here
Thanks in advance :)

I tried but couldn't able to find the pair of values for which this script works perfectly.


COMP: Add backwards compatible EnlargeRegionOverBox

This adds a backwards compatible signature following the addition of
another argument in
609319760ae5c8c780c4b9be156a4a865ab79439
@romangrothausmann please take a look.

Following build issues reported in RTK as discussed here:
https://discourse.itk.org/t/imagealgorithm-backward-incompatible-change/1725/2

Thanks @thewtex for the compatibility additions, looks good to me.

I still have some issues it seems:
https://my.cdash.org/viewBuildError.php?buildid=1630397
I'll try to suggest an alternative correction ASAP.

Should this be merged or abandoned?

Closing, to be replaced by a patch fixes the RTK build.


tf-model-remediation: Keyword arguments not supported by original model: ['mask']

Reposting  from tensorflow/model-remediation as I was hoping to use MinDiff framework in my work however there hasn't been a response from the team in that repo
System information
Relevant Versions:
Running locally for now on Windows 10 Pro Version 10.0.19042 Build 19042
python 3.6.9
tensorflow 2.3.1
tensorflow-model-remediation 0.1.3
transformers 4.3.2
From provided: TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
output: v2.3.0-54-gfcc4b966f1 2.3.1
Describe the current behavior
Hi I've been trying to debug this for a few days, I'm using the MinDiff remediation similarly to how it's used in the tutorial. Using the debugger I see the 'mask' value is None from the caller.
The base model I am using to remediate unfairness is TFBertForSequenceClassification from HuggingFace's transformers library. It compiles to tf.keras, so from the documentation should be compatible with the MinDiff framework
Describe the expected behavior
I expect the library to be able to train a mindiff framework with the provided code.
Standalone code to reproduce the issue
Code to reproduce (I can't share my data, but I've tried loading the BERT weights from a TF trained Transformers with the same issue. I've also commented out wrapping the TFBertForSequenceClassification in tf.keras model but it does not make a difference to the stacktrace.
bert_model = TFBertForSequenceClassification.from_pretrained(path_to_bert, from_pt=True)
# optimizer = tf.keras.optimizers.Adam(learning_rate=learning_rate)
# loss = tf.keras.losses.BinaryCrossentropy()
# bert_model.compile(optimizer=optimizer, loss=loss)

min_diff_weight = 1.5

# Create the dataset that will be passed to the MinDiffModel during training.
dataset = md.keras.utils.input_utils.pack_min_diff_data(
    train_ds_main, train_ds_unpriv, train_ds_priv)

# Wrap the original model in a MinDiffModel, passing in one of the MinDiff
# losses and using the set loss_weight.
min_diff_loss = md.losses.MMDLoss()
model = md.keras.MinDiffModel(bert_model,
                              min_diff_loss,
                              min_diff_weight)

# Compile the model normally after wrapping the original model.  Note that
# this means we use the baseline's model's loss here.
optimizer = tf.keras.optimizers.Adam(learning_rate=learning_rate)
loss = tf.keras.losses.BinaryCrossentropy()
model.compile(optimizer=optimizer, loss=loss, metrics=['accuracy'])

model.fit(dataset, epochs=epochs)

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Stacktrace:
Epoch 1/1000
Traceback (most recent call last):
  File "*/src/benchmarking/run_model.py", line 450, in <module>
    main()
  File "*/src/benchmarking/run_model.py", line 446, in main
    eval_min_diff_bert(**kwargs)
  File "*/src/benchmarking/run_model.py", line 211, in eval_min_diff_bert
    model.fit(dataset, epochs=epochs)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\keras\engine\training.py", line 108, in _method_wrapper
    return method(self, *args, **kwargs)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\keras\engine\training.py", line 1098, in fit
    tmp_logs = train_function(iterator)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\def_function.py", line 780, in __call__
    result = self._call(*args, **kwds)
  File *\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\def_function.py", line 823, in _call
    self._initialize(args, kwds, add_initializers_to=initializers)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\def_function.py", line 697, in _initialize
    *args, **kwds))
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\function.py", line 2855, in _get_concrete_function_internal_garbage_collected
    graph_function, _, _ = self._maybe_define_function(args, kwargs)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\function.py", line 3213, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\function.py", line 3075, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\framework\func_graph.py", line 986, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\eager\def_function.py", line 600, in wrapped_fn
    return weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "*\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\framework\func_graph.py", line 973, in wrapper
    raise e.ag_error_metadata.to_exception(e)
ValueError: in user code:

    *\anaconda3\envs\mindiff\lib\site-packages\tensorflow\python\keras\engine\training.py:806 train_function  *
        return step_function(self, iterator)
   *\anaconda3\envs\mindiff\lib\site-packages\tensorflow_model_remediation\min_diff\keras\models\min_diff_model.py:473 call  *
        min_diff_loss = self.compute_min_diff_loss(
   *\anaconda3\envs\mindiff\lib\site-packages\tensorflow_model_remediation\min_diff\keras\models\min_diff_model.py:371 compute_min_diff_loss  *
        predictions = self._call_original_model(x, training=training, mask=mask)
    *\anaconda3\envs\mindiff\lib\site-packages\tensorflow_model_remediation\min_diff\keras\models\min_diff_model.py:234 _call_original_model  *
        return self.original_model(inputs, **kwargs)
    *\anaconda3\envs\mindiff\lib\site-packages\transformers-4.2.2-py3.8.egg\transformers\models\bert\modeling_tf_bert.py:1405 call  *
        inputs = input_processing(
    *\anaconda3\envs\mindiff\lib\site-packages\transformers-4.2.2-py3.8.egg\transformers\modeling_tf_utils.py:345 input_processing  *
        raise ValueError(

    ValueError: The following keyword arguments are not supported by this model: ['mask'].

Thank you!

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Configuration tab is incomplete for most types

These tabs need their details filled in, based on similar output to kubectl describe

resolved now for most types; will file individual issues for specific resource kinds as needed


Fix Typo in website

Community Contribution
Link to live project, video, or image:

Sharing

[x] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:

This is not a bug. http://codingtra.in is a valid URL. Nevertheless many thanks.


A couple questions about features

Hello! This looks awesome. I'm interested in using it, but there are a couple critical features I couldn't suss out looking at the readme and javadoc.

Does this handle sealed classes, or do you need subtype annotations still?
How does this handle null safety/strictness? Does it handle anything like TypeQualifierDefault for default notnull-ness? (Edit: just brought myself up to date... I guess the new thing would be @NullMarked per https://jspecify.dev/blog/)
What convention does it use to serialize/deserialize polymorphic types? Ex: {"type": "abc", ...} vs {"abc": { ... }}
How does it determine field names, or is there any way to control serialization/deserialization naming conventions? Like HelloWorld vs hello_world vs helloWorld

Oh thanks for the quick answers!
Ah right, I missed @Json(naming=...).  I was looking it either as a property of the annotation processor or on the Builder method, but that makes sense.
Re @type do you mean it does {"type": "abc", ...} by default but using something like @typeProperty="t" you can change it to {"t": "abc", ...}? I'm not sure I can see how other form I mention (using a single-field object to tag the type) would be indicated this way.  My explanation might not have been totally clear... this is a better overview of the different styles I meant to refer to: https://serde.rs/enum-representations.html with {"type": "abc", ...} being "internally tagged".

I don't think we do anything special

So just to confirm, if I read your answer right, it does not specifically check for or error on null values during deserialization?

Okay, much appreciated!  Please feel free to close this issue, unless you wanted to mention any of this stuff in the documentation/readme or something.