"Report an issue" doesn't work within VSCode

Code of Conduct

[X] I agree to follow this project's Code of Conduct

On what operating system are you seeing the problem?
macOS (Apple/arm64)
VS Code version
Version: 1.93.1 (Universal)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0
Version of Confluent extension
v0.16.3
To Reproduce

Open the "Confluent" tab from left nav
Under "Support", select "Report an issue"
Fill in details, make sure all required fields are complete
Click "Create on GitHub"

Current vs. Expected behavior
Expect: Able to create an issue on github
Actual: No response upon clicking the button
Relevant log output
No response
Which area(s) are affected? (Select all that apply)
Installation
Additional context
No response

Hi Derek,
The 'Report an issue' functionality makes use of common infrastructure internal to VS Code. When you hit the 'Preview on GithHub,' submit button on the the form, it hands off to your system's web browser with a URL to GitHub that prefills out GitHub's issue reporter form, for you to then refine and submit. Apologies that it did not work for you that time. Could the browser window perhaps have been obscured or perhaps blocked at the GitHub login flow? It does look from your other reports that it has worked for you in the past, and also it appears that it was used to report this issue (given the system and A/B test details it provides). Could you perhaps try again and confirm? Thanks!
I just used it to create https://github.com/confluentinc/vscode/issues/297, and it worked as expected.

@derek1ee one more suggestion: when you have the Issue Reporter window open, try to open the dev tools pane (F12) before trying to submit an issue; there may be some silent network errors happening:

I was not able to open the dev tool panel?
Just tried this again, it looks like the issue only repros when "Confluent" extension is selected, if I change it to "C#" for example, a browser tab is successfully opened and an issue created.
Do we have some additional validation maybe that blocks issue creation from vsode?

@derek1ee  Are you trying to file an issue from a non-Confluent-firewall-active machine yet from a github account linked to your Confluent account? That won't work due to ConfluentInc's organization settings vs the half-open vscode repo (and not due to anything in the extension itself). If you either:

Be logged into GitHub on a non-confluent-firewall computer using a GitHub account that is unafilliated with ConfluentInc,
Be logged into your ConfluentInc GitHub account but use the issue reporting functionality from behind Confluent firewall.

Then it really should work and has been tested both ways.
Does this help?

I was not able to open the dev tool panel?

@derek1ee it looks like this may be controlled by a new Issue Reporter setting released in 1.93:

Try this:

go into your settings (Cmd+,)
filter @id:issueReporter.experimental.auxWindow
uncheck/disable that "Aux Window" setting
reopen the Issue Reporter

F12 (or fn+F12, depending on keyboard settings) should now surface the dev tools panel.
Let me know if this helps at all!

@shouples turning the experimental feature off allowed me to open F12 to see network traffic. Looks like the POST call failed 403 Forbidden:
{
"message": "Resource protected by organization SAML enforcement. You must grant your OAuth token access to this organization.",
"documentation_url": "https://docs.github.com/articles/authenticating-to-a-github-organization-with-saml-single-sign-on/",
"status": "403"
}

@derek1ee that helps, thanks! Do you see any indicators in the Accounts section prompting for additional GitHub sign-in or anything?

@shouples Doesn't appear to be, see screenshot below. I will send you the network trace offline.

Thanks again for your patience on this one @derek1ee -- I'm going to go ahead and close this since it isn't specifically related to our extension.
For anyone else that encounters this behavior, this seems to be related to how VS Code handles SAML sessions when the user is part of a GitHub organization that requires SAML/SSO.
Within VS Code, a basic authentication with GitHub (like for settings sync) only requires the email scope, but other extensions (like GitHub Pull Requests) will require more, that may prompt users to reauthenticate and/or show users this kind of GitHub page from their default browser:

Once the user clicks "Authorize" for their given organization, the Issue Reporter functionality should work as expected and stop returning 403 errors.


Release Google.Cloud.Deploy.V1 version 1.0.0-beta01

Changes in this release:
Initial release.

Created release for Google.Cloud.Deploy.V1-1.0.0-beta01


OpenTelementry

The production environment should start a collector service and a jaeger service.
I think, for the beginning it is ok to start the all-in-one-jaeger-service that only holds the data in memory. After this is done, we can think about saving the spans on disk.
See https://github.com/OpenSlides/OpenSlides/pull/6322/files

A few thoughts:

The OpenTelemtry services should be optional, either as a single feature (enableOpenTelemetry) or individually (enableOpenTelemetryCollector etc.).
The Web UI should be available under the main instance domain, e.g., https://example.com/jaeger/, not on a separate port.
The Web UI must require authentication (probably using a new Docker secret).


Use alternative to scan /proc/net/tcp in the next Android version

Android will limit what files can be read from /proc/*.
So I've filed a feature request and it was implemented:
https://issuetracker.google.com/issues/109758967
Patch:
https://android-review.googlesource.com/q/topic:"getConnectionOwnerUid"+(status:open OR status:merged)
API currently is:
int getConnectionOwnerUid(int protocol, InetSocketAddress local, InetSocketAddress remote);
This API is available to VPN apps only and the VPN must be up and running.

We should use in the VPN mode
We should find a way to read from /proc/net/* in the rooted mode

https://developer.android.com/reference/android/net/ConnectivityManager.html#getConnectionOwnerUid(int, java.net.InetSocketAddress, java.net.InetSocketAddress)

We should find a way to read from /proc/net/* in the rooted mode

That API is allowed to use either with active VPN or with NETWORK_STACK permission in manifest.
So adding permission may be a solution.

This is a signature-level signature

I have filed a request for the getConnectionOwnerUid API to be allowed for all apps (not only for VPN or System apps) - https://issuetracker.google.com/u/1/issues/131204361
I wanted to know if this idea was already discussed in your initial feature request (https://issuetracker.google.com/issues/109758967), it looks like your feature request report is not public. Could you please make it public, if it is okay? If not, could you please tell me if this was discussed before. Does the Android team have any issues allowing this API for all apps to use?

Initially, I asked it to be available to all apps and not just the VPN apps, but they refused. Tbh, I haven't pushed it too much.
Your usecase seems valid, but I suppose we'll need more examples to make it feasible to implement.
Also, I can't change issue visibility, it seems it was marked as private automatically when it was created.


Licensing and other questions

Hi again,
I have now forked your code and would like to ask you some questions before I proceed.

Licensing
My own code is MIT licensed (swyh-rs), your code is Apache licensed. If I modify your code in my fork I suppose I would have to switch to a dual license. What are your thoughts on this?
Modifying your code in my fork for my needs

I would like to get rid of libsndfile, by hiding it behind a feature. I have no use for it, and it is a dependency I would like to avoid. If I use libsndfile I can as well use libflac-sys or libflac-bound, and the reason I was looking for a pure Rust implementation of Flac encoding was to avoid the use of libflac. What are your views on this? libsndfile is only used for testing AFAICS. A better alternative would perhaps be to split the crate in two : flacenc-core (lib) and flacenc (binary).
I will have to make some structs public (like MetaDataBlock and possibly others) if I want to use the low-level API of flacenc-rs.
I will probably have to extend or change or write an alternative for PreloadedSignal, so that is behaves like a buffer for writing and reading samples

All this leads me to the following question: do I plod ahead in my fork on my own or are you interested in integrating my changes in one way or another in your code (me creating pull requests and you commenting and requesting changes before approving etc...)
Looking forward to your opinion on this.

As an owner of this project, I encourage you to contribute to the main branch via PR rather than making a fork. However, this product is also an unofficial Google product, so you will need to submit Google Contributor License Agreement (CLA; https://cla.developers.google.com/).
In case if you are not okay with CLA, I can modify the code on behalf of you for making it more accessible by e.g.:

making libsndfile dependency optional (in library mode)
making some structs public (please let me know which)

With the above changes, I think you can be integrate this library in your project without making a fork.

I have no problem with the CLA, done.
And I totally agree that it is better to contribute with PR's.
I suppose that the only struct that needs to be public for me to use the library is MetaDataBlock.
I had a go at making libsndfile and clap optional using a feature and #[cfg], and it works but it makes the code messy and ugly with all these #[cfg] in my opinion, Rust can apparently not cope gracefully with both a main.rs and a lib.rs with different dependencies in the same crate.
Would you be prepared to split the crate  into a library (core) and a binary crate?

Thanks, I'm fine with splitting the crate.
I prefer to keep the main library logic in the root crate, and to move "main.rs" to, e.g., "cli" sub-crate.
Please prepare two PRs one for splitting, and the other one for the rest.

Thanks! I'll try the "split" PR first before I start anything else.

Please prepare two PRs one for splitting, and the other one for the rest.

I don't think it can be done in seperate PR's, because in my opinion part of components.rs should go in lib (BitRepr, MetaDataBlock related) while other parts (file and Stream related) could (should?) go to bin.
What is your opinion on this?

I think everything except for "main.rs" can be in the library.
Not in your case, but Stream may also have library use cases.
There're only few CLI-specific functions outside of "main.rs", so I think it's fine.
(e.g. serde-dependency in "config.rs" may not be relevant for library usage, but I think for now it's okay.)
I suggested preparing two PRs because I prefer one commit per PR.
But, now I recognize that this case actually requires commit dependency, so please ignore the previous advise.
I now think you should use one PR, with 2 commits.

I agree that file support should be in the library, but because of the dependency on libsndfile I think it should also be an optional feature of the library.
I'll prepare a PR that splits off main.rs but leaves everything else as is, is that OK?
And perhaps we can discuss the libsndfile issue after that?


Update to 2.0 plugin

I have update the project structure and merge this changes in this PR to PR #2.


Editor Freezes Frequently in Windows 10, then Resumes

Environment

Windows 10
v1.13 (& also Insiders Edition)

Behaviour

The editor freezes while typing, copying, clicking to place cursor:

cursor does not move or flash
all menus and controls within the editor become unresponsive

After an interval of between 10 - 30 seconds, the editor picks up where it left off (i.e. 'catches-up' with any typing /copying/pasting, navigation).
Freeze does not affect any other open application / task-bar / desktop
Behavior is very frequent (once every 5 minutes or more).

Steps to Reproduce

open editor
open any file
begin typing, place cursor, copy / paste or navigate

Other Information

Behaviour recent (started since 29 June, 2017)
Behaviour occurs with Insiders Edition
Behaviour occurs with extensions disabled / uninstalled
Editor virtually unusable while this behaviour persists

If you open the Developer Tools, do you see any errors in the console?
Can you also record a Profile in the Developer Tools?

select Profiles > Record JavaScript CPU Profile and press Start
now produce the hang/slowness
stop profiling (press Stop or the red button), save the profile, and share it with us

Thanks.

I had this freezing in win 10. I opened the developer tool and checked it, and Vue2 Snippets for Visual Studio Code generated an error. After removing it, it works normally. Check your VS Code extension.

Here is a profile for the freeze I had today, it really has no pattern, it just freezes when focused again, and all I did here is open dev tools, start recording, switched to vscode, kept recording until it was unfrozen, switched back to dev tools, to stop recording...
https://1drv.ms/u/s!AmCfg5Cb-j0doF8XwfGKgmS6NG0N


mudslide cannot send message

Hi @robvanderleek
After a few successful messages mudslide stopped sending messages. I logged out and logged in several times, but without success. The device is visible in connected devices on Android.
How to find the cause of the problem ?
Attached is a screenshot of the unsuccessful sending.

Thank you !
Best regards
Goran

Hi @Goran53nja
Sorry to hear, can you try again with the latest version? npx mudslide@latest

Hi @robvanderleek
Thank you. Same again.

OS Debian 12...
The installation was done according to this instruction....
https://community.home-assistant.io/t/alternative-howto-for-using-whatsapp-notifications-sent-from-a-linux-host/674505

Hi @Goran53nja
I just tested the logout/login procedure and for me it still works with the latest version of Mudslide.
Perhaps you can test it from a different machine?
To be sure there's no stale cache data you can also manually clean the cache folder that's reported when you run npx mudslide@latest me
Also, you can run the send command with the -vvv flag, that will generate a lot of debug messages that could indicate where it goes wrong: npx mudslide@latest -vvv send me 'Hello world'
If the problem is related to the Baileys library that Mudslide is based upon, or related to your WA account, I'm afraid I can't help you any further.

Hi @robvanderleek

I just tested the logout/login procedure and for me it still works with the latest version of Mudslide.

Login and logout works for me and the Android device sees an active connected device.  Different machine I can try later.

To be sure there's no stale cache data you can also manually clean the cache folder that's reported when you run npx mudslide@latest me
Also, you can run the send command with the -vvv flag, that will generate a lot of debug messages that could indicate where it goes wrong: npx mudslide@latest -vvv send me 'Hello world'

Here I copy the command output  there are no  any debug messages:
/ |   | | () | | _ __ _   _  | | __
| |  | | | | ' | |/ _ \ | '| | | |/ | |/ /
| || || | |) | |  __/ || |  | || | (|   <
__,|.__/||_|_||   _,|_|_|_\
Welcome to Armbian_community 24.8.0-trunk.164 Bookworm with Linux 6.6.31-current-sunxi
No end-user support: untested automated build
System load:   46%           	Up time:       2:31	Local users:   2
Memory usage:  4% of 1.93G  	IP:	       <IP_ADDRESS>
CPU temp:      37°C           	Usage of /:    12% of 15G
[ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]
host@cubietruck:~$ npx mudslide@latest -vvv send me 'A test text message from my linked account to my phone’

^C
host@cubietruck:~$ npx mudslide@latest -vvv send me 'A test text message from my linked account to my phone’
^C
host@cubietruck:~$ npx mudslide@latest login
ℹ  info      In the WhatsApp mobile app go to "Settings > Connected Devices >
ℹ  info      Connect Device" and scan the QR code below
✔  success   Logged in
…  awaiting  Closing WA connection, waiting for 1 second(s)...
⭐ Please star Mudslide on GitHub! https://github.com/robvanderleek/mudslide
host@cubietruck:~$ npx mudslide@latest -vvv send me 'A test text message from my linked account to my phone’
^C
host@cubietruck:~$ ls
host@cubietruck:~$ ls -l -a
sveukupno 40
drwx------ 4 host host 4096 lip  18 10:29 .
drwxr-xr-x 3 root root 4096 lip  17 10:18 ..
-rw------- 1 host host 2442 lip  19 14:24 .bash_history
-rw-r--r-- 1 host host  220 lip  17 10:18 .bash_logout
-rw-r--r-- 1 host host 3601 lip  17 10:20 .bashrc
-rw------- 1 host host   20 lip  18 10:29 .lesshst
drwxr-xr-x 3 host host 4096 lip  17 11:03 .local
drwxr-xr-x 5 host host 4096 lip  17 10:33 .npm
-rw-r--r-- 1 host host  807 lip  17 10:18 .profile
-rw-r--r-- 1 host host    0 lip  17 10:26 .sudo_as_admin_successful
-rw-r--r-- 1 host host    0 lip  17 10:18 .Xauthority
-rw-r--r-- 1 root root   78 lip  17 10:20 .xsessionrc
host@cubietruck:~$ cd .npm/
host@cubietruck:~/.npm$ ls
_cacache  _logs  _npx  _update-notifier-last-checked
host@cubietruck:~/.npm$ cd _cacache/
host@cubietruck:~/.npm/_cacache$ ls
content-v2  index-v5  tmp
host@cubietruck:~/.npm/_cacache$ cd content-v2/
host@cubietruck:~/.npm/_cacache/content-v2$ ls
sha512
host@cubietruck:~/.npm/_cacache/content-v2$ cd sha512/
host@cubietruck:~/.npm/_cacache/content-v2/sha512$ ls
00  0b  13  1e  2b  35  3e  4e  58  64  6d  77  88  92  a0  ad  ba  c3  d0  dc  e6  f1  fd
01  0c  14  1f  2c  36  41  4f  59  65  6e  78  8a  93  a1  ae  bb  c5  d2  dd  e7  f2  fe
02  0d  15  20  2d  37  42  51  5b  67  6f  7b  8b  94  a3  af  bc  c6  d3  df  e8  f4  ff
03  0e  17  25  2e  38  43  52  5d  68  70  7d  8d  95  a4  b0  bd  c8  d4  e0  e9  f6
06  0f  19  26  31  39  45  53  5e  69  71  7e  8e  96  a5  b2  be  c9  d7  e1  ea  f7
08  10  1a  28  32  3a  48  54  5f  6a  74  82  8f  97  a6  b3  c0  ca  d8  e3  ed  f8
09  11  1b  29  33  3b  49  55  60  6b  75  84  90  9a  a7  b5  c1  cb  d9  e4  ef  f9
0a  12  1c  2a  34  3d  4b  56  63  6c  76  86  91  9d  ac  b7  c2  cf  da  e5  f0  fa
host@cubietruck:~/.npm/_cacache/content-v2/sha512$ cd ..
host@cubietruck:~/.npm/_cacache/content-v2$ cd ..
host@cubietruck:~/.npm/_cacache$ cd ..
host@cubietruck:~/.npm$ ls
_cacache  _logs  _npx  _update-notifier-last-checked
host@cubietruck:~/.npm$ cd _npx/
host@cubietruck:~/.npm/_npx$ ls
3d8e8e1f43a0b507  ce95761724e6020f
host@cubietruck:~/.npm/_npx$ cd 3d8e8e1f43a0b507/
host@cubietruck:~/.npm/_npx/3d8e8e1f43a0b507$ ls
node_modules  package.json  package-lock.json
host@cubietruck:~/.npm/_npx/3d8e8e1f43a0b507$ ls
node_modules  package.json  package-lock.json
host@cubietruck:~/.npm/_npx/3d8e8e1f43a0b507$ cd ..
host@cubietruck:~/.npm/_npx$ ls
3d8e8e1f43a0b507  ce95761724e6020f
host@cubietruck:~/.npm/_npx$ cd ..
host@cubietruck:~/.npm$ npx mudslide@latest logot
^C
host@cubietruck:~/.npm$ npx mudslide@latest logout
✔  success   Logged out
…  awaiting  Closing WA connection, waiting for 1 second(s)...
⭐ Please star Mudslide on GitHub! https://github.com/robvanderleek/mudslide
host@cubietruck:~/.npm$ cd .npm/
-bash: cd: .npm/: Nema takve datoteke ili direktorija
host@cubietruck:~/.npm$ ls
_cacache  _logs  _npx  _update-notifier-last-checked
host@cubietruck:~/.npm$ cd _cacache/
host@cubietruck:~/.npm/_cacache$ ls
content-v2  index-v5  tmp
host@cubietruck:~/.npm/_cacache$ rm -R *
host@cubietruck:~/.npm/_cacache$ cd ..
host@cubietruck:~/.npm$ npx mudslide@latest login
ℹ  info      In the WhatsApp mobile app go to "Settings > Connected Devices >
ℹ  info      Connect Device" and scan the QR code below
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█
████ ▀█▄█▄ ▀▄  █ ▄▀█▀█ ▄  █▀   ▀▀█▄▄▄█ █▀▄  ▄▄▄▄█ ▄█▀██
██ ▄██ ▄ █▄▀▄▄▄▄▄▀▀▀ ███▄▄ █▀▀█▄▄▄██ ▄▄▀▄██▄██▄▀▀▀▄▄▄██
█  ▄▄ ▀▄▀▀▀▀█  █▀▄ ▄  ▀▀█  ▀██▀█▄▀▄█    ██ ▄██▀ ▄█▄▀▄██
███ █▀█▄ ██▄▄▄█ ▄█  █▀ ▀▀▀▀▄▄█  █▄▄█▀ ▀█▀ ▄▄▄  ▄ ▄▀█▄▄█
█

✔  success   Logged in
◼  pause     Wait until WhatsApp finishes connecting, then press any key to exit
…  awaiting  Closing WA connection, waiting for 1 second(s)...
⭐ Please star Mudslide on GitHub! https://github.com/robvanderleek/mudslide
host@cubietruck:~/.npm$ npx mudslide@latest -vvv send me 'A test text message from my linked account to my phone’

^C
host@cubietruck:~/.npm$ ls
_cacache  _logs  _npx  _update-notifier-last-checked
host@cubietruck:~/.npm$ cd _cacache/
host@cubietruck:~/.npm/_cacache$ ls
content-v2  index-v5  tmp
host@cubietruck:~/.npm/_cacache$ cd content-v2/
host@cubietruck:~/.npm/_cacache/content-v2$ ls
sha512
host@cubietruck:~/.npm/_cacache/content-v2$

it's possible a hardware problem, I'll see when I try another machine

I also think it's best to first try it on a different machine.
Note that the cache folder from Mudslide is not inside the .npm folder. You can see what location Mudslide uses by running npx mudslide@latest me.


Add exception for Turtlico

Original submission was already a rename https://github.com/flathub/flathub/pull/1604


fuzz: limit the number of hosts when slow-start aggression is used

Commit Message: fuzz: limit the number of hosts when slow-start aggression is used
Additional Description:
When running the fuzzer with many hosts and SlowStart aggression enabled, the querying of the aggression runtime-value is very costly - the calls to value() of the MockLoader and MockSnapshot are dominating and can cause a timeout.
This PR limits the number of hosts in this case.
Risk Level: low - fuzz only
Testing: added fuzz test case
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
Fixes fuzz issue 67692

/wait


Sample weights in python sklearn interface

Please add "sample_weight" parameter in fit function and "class_weight" parameter when initializing LGBMClassifier()

You can use train_fields={'weight'=YOUR_WEIGHT_ARRAY} for sample weight now. We can make it more clear in the future. By class weight, do you mean scale_pos_weight for binary classification? It's not supported in multiclass classification yet. But you can use the same sample weights for each class to achieve it.


Add support for AES-GCM decryption

This PR adds support for AES-128-GCM, AES-192-GCM, and AES-256-GCM encryption methods.
Implementation
The implementation ended up being exactly the one that @ahukkanen described in the issue comment: https://github.com/onelogin/ruby-saml/issues/541#issuecomment-714646399
The AES-GCM encryption is formed as described in https://www.w3.org/TR/xmlenc-core1/#sec-AES-GCM

The ciphertext in AES GCM consists of 96-bit Initialization Vector (IV) + encrypted octets + and 128-bit Authentication Tag (T). No padding is used.

 So the ciphertext message is as following
IV (96bit) + data + T (128bit)

Tests
The tests fixtures were formed like this:

Copy the encrypted assertion and key from an existing AES-CBC test fixture to assertion.xml and key.txt
Form the encrypted message:

plaintext_response = File.read("assertion.xml")
cipher = OpenSSL::Cipher.new("AES-128-GCM").encrypt
iv = Random.bytes(12)
key = File.read("key.txt")
key.force_encoding("ASCII-8BIT")
cipher.iv = iv
cipher.key = key
cipher_text = cipher.update(plaintext_response) + cipher.final
auth_tag = cipher.auth_tag

# Form the message as described in https://www.w3.org/TR/xmlenc-core1/#sec-AES-GCM
base_64_string = Base64.strict_encode64(iv + cipher_text + auth_tag)
File.write("encrypted-assertion.base64", base_64_string)

Copy the encrypted-assertion.base64 to response fixture and base64 encode it.

A plaintext example of the fixture can be found here https://gist.github.com/silppuri/121f2099ac06dfca35e96c674e6135ea
TODO

[x] Test this in a test environment with an IdP that uses AES-GCM encryption

Coverage decreased (-0.5%) to 97.476% when pulling 55a2389a9065519253e5e7bebef45765355eb498 on silppuri:support-aes-gcm into 9f710c5028b069bfab4b9e2b66891e0549765af5 on onelogin:master.

I tested this in a testing environment with and IdP using the AES-128-GCM algorithm successfully.

@pitbulk any way I can help to get this forward?

@pitbulk any way I can help to get this forward?


Docker daemon crashes when "docker exec" spawns background processes

Output of docker version:
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 23:54:00 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 61
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 81
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.16-boot2docker
Operating System: Boot2Docker 1.12.0 (TCL 7.2); HEAD : e030bab - Fri Jul 29 00:29:14 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.789 GiB
Name: default
ID: QK4D:BFZ2:222M:LKM6:2JFW:D7VD:AKOY:OJIT:VXJY:23C2:ZZQI:FVFF
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 14
 Goroutines: 24
 System Time: 2016-08-24T18:24:45.59605555Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Tested in VirtualBox on OSX + Linux Physical Host
Steps to reproduce the issue:

docker exec -it "container_id" /bin/bash
[from inside the container] sleep 1000 &
[from inside the container] exit

Describe the results you received:
Upon issuing exit, the container is crashed.  The docker daemon is also crashed.  At this point, I must restart the docker daemon (either docker-machine restart, or service docker restart) in order to regain control.
Describe the results you expected:
Upon issuing the "exit" command, I should be able to exit the container.  The spawned children processes can keep running (or be terminated - debatable).  But the docker daemon should not crash under these circumstances.

Can you provide the daemon logs from the crash?

ping @mlaventure
I get a deadlock do this.
$ docker run -d --name test busybox top
$ docker exec sh -c 'sleep 1000 & exit'

Logs from attaching to running container, spawn off sleep, and attempted to exist...nothing further seen.
time="2016-08-24T18:44:07.384429657Z" level=debug msg="starting exec command 608f939a9da4443b40c3e47d6f8ab721529f3aa560365a1c2786b8c884cbec13 in container bb6957e6946aae351e08ba9bb04aad329c6d815efe979163917fed4efa71096c"
time="2016-08-24T18:44:07.384611010Z" level=debug msg="attach: stdin: begin"
time="2016-08-24T18:44:07.384610510Z" level=debug msg="attach: stdout: begin"
time="2016-08-24T18:44:07.384769204Z" level=debug msg="Calling POST /v1.24/exec/608f939a9da4443b40c3e47d6f8ab721529f3aa560365a1c2786b8c884cbec13/resize?h=24&w=198"
time="2016-08-24T18:44:07.473844913Z" level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"start-process\", Id:\"bb6957e6946aae351e08ba9bb04aad329c6d815efe979163917fed4efa71096c\", Status:0x0, Pid:\"608f939a9da4443b40c3e47d6f8ab721529f3aa560365a1c2786b8c884cbec13\", Timestamp:(*timestamp.Timestamp)(0xc82089fed0)}"
time="2016-08-24T18:44:07.473902244Z" level=debug msg="libcontainerd: event unhandled: type:\"start-process\" id:\"bb6957e6946aae351e08ba9bb04aad329c6d815efe979163917fed4efa71096c\" pid:\"608f939a9da4443b40c3e47d6f8ab721529f3aa560365a1c2786b8c884cbec13\" timestamp:<seconds:1472064247 nanos:473433101 > "
time="2016-08-24T18:44:25.401166469Z" level=debug msg="containerd: process exited" id=bb6957e6946aae351e08ba9bb04aad329c6d815efe979163917fed4efa71096c pid=608f939a9da4443b40c3e47d6f8ab721529f3aa560365a1c2786b8c884cbec13 status=0 systemPid=1925

On Mac, I can attempt to kill the container..no further log after logging the kill.  Kill doesn't terminate.
time="2016-08-24T18:46:27.077292393Z" level=debug msg="Calling POST /v1.24/containers/bb6957e6946a/kill?signal=KILL"
time="2016-08-24T18:46:27.077354395Z" level=debug msg="Sending 9 to bb6957e6946aae351e08ba9bb04aad329c6d815efe979163917fed4efa71096c"

sorry, was on PTO. I can reproduce the issue using indeed, will have a look

This is actually the expected behavior.
The sleep 1000 & started in the background inherit the standard descriptors of the exec initial sh which in turn keeps the connection to the docker client alive.
The proper fix is to use docker exec -d <id> sleep 1000 instead


raw_cache: add support for Amazon EFS

EFS's native relatime snaps atime to be equal to the mtime on access, so we much now check for atime >= mtime, in order to find files that were accessed.
That's OK because we already have logic to reset atime far in the past on writes, for APFS.
However, resetting atime in the past doesn't guarantee an atime update on EFS (I assume it has separate internal atime/mtime fields and updates those automatically with relatime).
We now check whether a newly opened file wasn't marked as touched, and explicitly snap atime forward to mtime if necessary.

coverage: 99.086% (+0.2%) from 98.924%
when pulling 0835be1930718972ff97ac899e3fca400d43413e on pkhuong/efs
into b3091a1ef0f5d935bcfe8583bec9420163851930 on main.

Already tested on Linux with EFS and ext4. should also

[ ] check this didn't break OS X/APFS.

coverage: 99.086% (+0.2%) from 98.924%
when pulling c8dc69c2e8a380fdc121218b2ac827d04115f085 on pkhuong/efs
into b3091a1ef0f5d935bcfe8583bec9420163851930 on main.


sort items multiselect for active = true

I wonder if there is a way of ordering the internal elements of multiselect, placing on top those who have been selected and to bring them in alphabetical order. ???

Hi @alex-oko ,
Unfortunately there's no such feature.

Too bad, I am also looking for this. Can you suggest an approach?
Intuitively I would start sorting my input model array. Using the orderBy filter could be cool, too.

Hi is very simply i customize code and here is the plugin customized
isteven-multi-select-customized.zip


ANNOTATE:CHIPSEEKER_PEAKPLOT failed due to memory allocation

Description of the bug
Job failed because there wasn't enough memory allocated. This is a little more problematic than just updating resources because for every job that failed, 20+ subjobs were created (this is running in parallel) which did not have enough memory. Since the max attempts is 2 this can really escalate quickly. We need to

[ ] update the memory for this module
[ ] decrease retries to 1x

Command output:
  GRanges object with 66127 ranges and 2 metadata columns:
            seqnames              ranges strand |    pvalue    qvalue
               <Rle>           <IRanges>  <Rle> | <numeric> <numeric>
        [1]     chr1<PHONE_NUMBER>45      * |     15.18     14.75
        [2]     chr1<PHONE_NUMBER>14      * |     10.54     10.18
        [3]     chr1<PHONE_NUMBER>56      * |      5.85      5.59
        [4]     chr1<PHONE_NUMBER>36      * |      3.20      3.03
        [5]     chr1<PHONE_NUMBER>17      * |     64.14     63.30
        ...      ...                 ...    ... .       ...       ...
    [66123]     chrX 155651333-155651534      * |      3.81      3.62
    [66124]     chrX 155662420-155662621      * |      6.09      5.83
    [66125]     chrY   11085350-11085551      * |      2.64      2.50
    [66126]     chrY   11156173-11156374      * |     16.16     15.71
    [66127]     chrY   11156459-11156660      * |     12.06     11.67
    -------
    seqinfo: 24 sequences from an unspecified genome; no seqlengths
  >> binning method is used...2024-02-23 00:28:55
  >> preparing body regions by gene... 2024-02-23 00:28:55
  >> preparing tag matrix by binning...  2024-02-23 00:28:55
  >> preparing matrix with extension from (TSS-20%)~(TTS+20%)... 2024-02-23 00:28:55
  >> 87 peaks(0.4930296%), having lengths smaller than 800bp, are filtered... 2024-02-23 00:29:15

Command error:
  Warning messages:
  1: In normalizePath("~") :
    path[1]="/home/sevillas2": No such file or directory
  2: package 'dplyr' was built under R version 4.3.2
  Error in t.star[r, ] <- res[[r]] :
    number of items to replace is not a multiple of replacement length
  Calls: plotPeakProf2 ... plotAvgProf.binning.internal -> getTagCount -> getTagCiMatrix -> boot
  In addition: Warning message:
  In parallel::mclapply(seq_len(RR), fn, mc.cores = ncpus) :
    scheduled cores 63, 68, 69, 71, 76, 80, 82, 95, 96, 100, 110, 119 did not deliver results, all values of the jobs will be affected
  Execution halted

Command used and terminal output
Ran within NF workflow, but this is the specific command ran

 chipseeker_peakplot.R \
      --peak CTCF.gem.sorted.merged.consensus.bed \
      --outfile-prefix CTCF.gem \
      --genome-txdb TxDb.Hsapiens.UCSC.hg38.knownGene \
      --genome-annot org.Hs.eg.db

duplicate of #169


Team Subscription

Is it possible to support team subscriptions, and manage team subscription per organization? so each organization manager can create a subscription for each team member and pay for that.

To me this appears to be more generally a question about best-practice in managing multi-user subscriptions, than necessarily related to pinax-stripe.
Commonly, one user - the billing user - has the subscription. Users from his organisation would be invited and linked via one-to-many relationships to the billing user. A billing transfer would mean, all related users are updated to point to the new billing user.
It appears that even Google AdWords handles it this way (without having deeper insight into the source code itself).


[wip] run decoding on a background isolate

This eliminates jank on the ui thread when parsing big responses.
Fixes #60.
I updated the existing test cases for the changes.
What I have not changed, yet, is to move decoding of the raw String from the response into a dart object to the background, i.e. we still rely on the default dio decoding, which in itself might be slow for big responses.
Also, there are two places in the generator code that don't use the new decoding, because there were no test cases for them previously and I didn't bother to check what they are actually supposed to return.
TODO:

[x] convert most types in background isolate
[ ] decode raw response String to dart object in background isolate
[ ] add annotation to decide per class and per method whether the decoding should happen in the background. What should be the default? Decoding in the background might be a bit slower, but it is always safe and leaves the UI jank free, so I guess this should be the new default, because it is generally hard to decide for users which of their requests should be performed in the background to avoid jank.
[ ] add more test cases for the missing code paths and convert those types in the background as well

You can test these changes in your code with the following dependencies in your pubspec.yaml:
dependencies:
  retrofit:
    git:
      url: git://github.com/nioncode/retrofit.dart
      path: annotation
      ref: isolate

dev_dependencies:
  retrofit_generator:
    git:
      url: git://github.com/nioncode/retrofit.dart
      path: generator
      ref: isolate

dependency_overrides:
  retrofit:
    git:
      url: git://github.com/nioncode/retrofit.dart
      path: annotation
      ref: isolate

Please make sure the code change can pass the analyzer check

Symbol links are used to add the latest sample code to pub.dev website.
example folder is excluded in analysis_options.yaml file, but I don't know why it's still been checked.

And please also make sure pub test in generator  will pass before you commit the code.

I have added some new features which cause a lot of conflicts.
I am planning to do some changes to your PR, but it seems minor changes can be applied.'
Can you solve the conflicts and the comments to your code? Or do you mind I pick your code from here and then create a new commit?

I will probably not work on this for the next couple weeks. I thought about this a bit more and I think it makes more sense to do both, the HTTP request and the JSON decoding, in a separate isolate to avoid copying the data twice (once the raw http data into the isolate and then the json decoded data out of it) [btw. I think it could also be the case that decoding the data into the original map could already freeze the UI, so this must be done in the isolate anyways].
This might even be easier to code since then the current synchronous code can stay as is, but the whole method will be put into an isolate. What do you think about this approach? Then I'd just close this PR and open another one in a couple of weeks.

I agree that we should provide an option to let HTTP requests and data convention run in a separated isolate. This option should be able to disable since user may provide other global isolate management.  As you mentioned, we need to find a better solution to solve this issue.

I have considered a bit more about the data convention. It may be handled all the staffs here in this library. So that we have only one method which is needed to put in isolate.

Yes, my idea was roughly the following:

add a way to let users provide e.g. an IsolateRunner so that we have a long living isolate that does not have to be spawned before each request and teared down afterwards
if no IsolateRunner was provided, we either a) spawn and tear down an isolate upon each request, or b) do everything on the main isolate, like we currently do
in the isolate, we run both, the HTTP request, and the data deserialization and then pass the result back to the main isolate

I'd prefer option a) to never block the UI by default. Then, if users want to reduce the delay of the http calls that happens because of the isolate creation, they can provide an IsolateRunner.
What do you think about this approach?

For 2nd,  It should be better to use a) for flutter project and b) for dart project.
The solution probably is to provide one annotation to enable this feature or not?
What do you think?

Why should it behave differently for flutter and dart? Is there any reason to NOT use an isolate in dart?
I don't know if an annotation is the right approach, the IsolateRunner should be provided in the constructor so that it can be disposed by the user if required. Is this possible with an annotation or do you just want to use the annotation for enabling / disabling the whole feature?

The main point from my side is that we should provide a way to disable isolate when they need.
There are many times data copy out-in even they provide a global runner.

what if they get the deserialized data and then do a complex compution.


fix streamlit import to account for older versions

Looks good!
Maybe a small comment as to why/which streamlit version this is necessary for would be helpful.


Implementation of creating custom large dataset

I want to create own dataset with self-recorded or non-publicly available data. I have read the documentation and still unable to upload my own dataset in pytorch_geometric.data.Data
Can anyone show me real implementation of creating own custom large dataset with some non public data and share that dataset as well?

I sadly don't have an example for you yet, but if you provide some information on where you are struggling I'm happy to help. If it's easier for you, you can also try to create a networkx graph from your data, and convert it into the PyG format via torch_geometric.utils.from_networkx.


Face recognition for high accuracy

Hello everybody...i maked a project with face_recognition library using raspberry pi 3 in real time..i added 45 people and In some peoples they identify faces incorrectly,how i can to increase face recognition accuracy??in addition, I set the tolerance parameter to 0.54 but it not worked for me,
thank you in advance for your support

How do you use multiple photos for each person?i used facerec_from_webcam_faster.py in the examples directory

Same question. How do you use multiple photos for each person? I used opencv demo.

@roiksail @stoneWeb , I think, @cftang0827  just use more photos for a person on training.

Yes, I used scikit-learn SVM and KNN module to make a simple classifier. However, the cons is that you can only classify the person in your database.
[Person1] vector1
[Person1] vector2
[Person1] vector3
[Person2] vector1
[Person2] vector2
[Person2] vector3
[Person2] vector4
For my experience, I think knn with distance metric is better.
And you may use svm for gender classification
Thanks.


styles are missing when using defineAsyncComponent within vue file

Hello @baiwusanyu-c ,
The plugin seems to have an issue when we use defineAsyncComponent the following:
const ComponentB = defineAsyncComponent(() =>
	import("../ComponentB/ComponentB.vue")
);

At this point it does not inject the style. Would it be possible to look into this as well?
Here's what creates an issue:
Repo:
https://github.com/SavkaTaras/vue-cue-issues/
File (line 13):
https://github.com/SavkaTaras/vue-cue-issues/blob/master/src/components/ComponentA/ComponentA.vue
Thank you,
Taras

The problem is here https://github.com/vuejs/core/pull/7942/files#diff-56930a63772d2e89f19432918b9d6ed851ede4159b0d32404e0c1d8c159fec99R1382
This logical judgment is not complete. When using defineCustomElement to directly wrap an asynchronous component, it is like
defineCustomElement(defineAsyncComponent(/Comp.vue/)) In this case, vue will automatically add the style of Comp.vue to the shadow, which will cause the logic of PR 7942 to add styles repeatedly. In order to prevent this situation, this is used judgment logic.

In the question code you gave, the asynchronous component exists in the descendant of the custom component wrapped by defineCustomElement (not the  son component), which requires further processing and judgment


CSS child combinator throws error

Describe the bug
If you use a child combinator (>) in an embedded <style> tag, the app immediately throws error and stops. I guess the parser thinks of it as a stray closing tag?
To Reproduce
Steps to reproduce the behavior:

yarn create slidev .
directly start with the starter template
for example, edit the line 73 from h1 to h1 > span in slides.md
https://github.com/slidevjs/slidev/blob/d81b650a3e4fe196e1f49dbad50807431077e558/demo/starter/slides.md#L73
See the error

[plugin:vite:vue] Tags with side effect (<script> and <style>) are ignored in client component templates.

/@slidev/slides/2.md:21:1

19 |  Learn more: https://sli.dev/guide/syntax#embedded-styles
20 |  -->
21 |  <style scoped>
   |   ^
22 |
23 |  h1 > span {

AFAIK it never fails without child combinators, nor via external CSS such as in style.css.
Desktop (please complete the following information):

OS: Ubuntu 20.04 (WSL 1)
Browser: N/A
Slidev version: 0.28.1

Is there a workaround for this problem?  I'd like to be able to use child combinators in embedded styles.

Still reproduces as of v0.36.10.

It sounds like stalebot shouldn't have closed this.


Turn on Security opts including labeling for docker build

Currently docker build is not passing HostConfig to daemon.Create.
this patch creates the default HostConfig and passes it to daemon.Create.
This will cause the SELinux labeling to turn on for docker build.  Basically
it causes a SecurtyOpt field to be created.  In the future this might also
allow us to use seccomp and UserNamespace with docker build.
Docker-DCO-1.1-Signed-off-by: Dan Walsh<EMAIL_ADDRESS>(github: rhatdan)

Seems like we can just pass an empty HostConfig struct to daemon.Create instead of storing it in the builder.

@cpuguy83 Does it matter, I would have to add import runconfig to internals.go.  Is there something "stored" when I do a docker build?

I feel the need for .... mmm, an selinux and docker colouring book.

LGTM

@SvenDowideit I have been thinking about creating a "Container" colouring book...

@rhatdan You're right, my only concern is people later coming and adding to b.HostConfig when it's not necessary, and instead handle this in daemon.Create:
if hostConfig == nil {
    hostConifg = &runconfig.HostConfig{}
}

So you want something like this patch? @cpuguy83

@rhatdan That's my thought, yes.
As always, and I should have mentioned prior, IANTM.

We shall see what @crosbymichael
The biggest change here, is now anyone calling daemon.Create with a nil hostconfig will get securityopt turned on as opposed to us only turning this on for docker build.  I am fine with the change.

Yeah, I was looking at the history of the API side of that. It would be older clients that would have a nil hostConfig, but I'm not sure that having a nil one would matter.  Especially since it would get a hostConfig (even if empty) when it starts anyway.

@rhatdan :heart:

LGTM

LGTM


Resolves triggered A&A using updated TOC stream name changes.

@DanielJMaher @FBRTMaka Please review.

Note that this PR will require a database build.

@birdage @FBRTMaka
PLEASE REVIEW ASAP

@DanielJMaher looks good to me, @FBRTMaka what do you think?

@oceanzus looks good Jim! :+1:


Some basic changes

I did some basic changes to improve the readability of the code.

Thanks for pointing out typo mistakes


RE PlayerCharacter.h

So.  Should I assume this is ready?

Forgot to draft sorry, there is still a few things left to get in for this one

It's good to go now for review


Can customize scroll element not just window by using scrollBehavior api.

What problem does this feature solve?
When using scrollBehavior api, it seems that only supports window scroll i.e.
const router = new VueRouter({
    routes: [...],
    scrollBehavior(to, from, savedPosition) {
        {
            x: 10,
            y: 10
        }
    }
})

// window triggers scrolling
window.scrollTo({x: 10, y: 10});

,  so, I hope add a param into the return object element, that the element triggers scrolling, not only window.
What does the proposed API look like?
const router = new VueRouter({
    routes: [...],
    scrollBehavior(to, from, savedPosition) {
        {
            return {
                element: document.querySelector("#app"),
                x: 10,
                y: 10
            }
        }
    }
})

//
// element triggers scrolling
element.scrollTo({x: 10, y: 10});

you can already do that with selector: https://router.vuejs.org/en/advanced/scroll-behavior.html

@posva
But this is not what I want..   The window will still trigger scrolling eventually.
Like:
// window.scrollTo()
I hope the passed element  trigger scrolling, Like:
// element.scrollTo({x: 10, y: 10});

Ah sorry, this is a duplicate of #1187

Thanks ! Got it:)


Performance of the CUE-System

I have a pretty Huge Harlow Story.
After every Link it freezes for some Seconds. I only have this Problem on Android-Devices, older and new Ones. I think the GC on Android is kinda slow.
Do you have any Idea how I could fix this?

I'd say, split your story into sub stories, then chain your stories on the last passage of the previous story.

Sounds like good solution. I will try it. Thanks ;)

Great that you reported the issue, I will take measure right away :)


Immediate Remediation of Porch Areas

Introduction
A few areas of the porch require immediate remediation. This involves the removal of flaky paint from various areas when necessary and the application of a quick coat of paint to improve its appearance.
Specific and Tiny Detailed Tasks

[ ] 1: Scrape off flaky paint from the porch rails when necessary (Estimated time: 2 hours)
[ ] 2: Scrape off flaky paint from the porch flooring (Estimated time: 2 hours)
[x] 3: Apply a quick coat of paint to the porch rails (Estimated time: 2 hours)
[x] 4: Apply a quick coat of paint to the porch flooring (Estimated time: 2 hours)

Acceptance Criteria

All flaky paint is removed from each specific area of the porch.
A quick coat of paint is applied to each specific area of the porch, improving its immediate appearance.
All tasks are completed within the estimated timeframes.

Story Points
Each task is assigned a story point of 1, totaling to 4story points for this issue.
Total Estimated Time
The total estimated time for this task is 8 hours or approximately 1 day, considering breaks and potential minor delays.

This task is done by quick application of paint to the porch flooring and rails without scraping off flaky paint.


Unable to update sonoff dongle-P directly connected through usb to home assistant.

Here is the error log:
`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service banner: starting

Add-on: ZigStar TI CC2652P/P7 FW Flasher
ZigStar TI CC2652P/P7 firmware flasher add-on
Add-on version: 0.4.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.2  (amd64 / qemux86-64)
Home Assistant Core: 2024.4.4
Home Assistant Supervisor: 2024.04.4
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service banner successfully started
s6-rc: info: service cc2652-flasher: starting
[18:56:13] INFO: Starting CC2652P flasher with Sonoff /dev/ttyUSB0
Setting filename to /root/firmware.hex
sonoff
Opening port /dev/ttyUSB0, baud 500000
Reading data from /root/firmware.hex
Your firmware looks like an Intel Hex file
Connecting to target...
ERROR: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[18:56:13] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`

Forgot to switch off Z2M


prompt reached the max tokens

I import 7 pdf files, total size is 173MB, when i query, sometimes there will be an error:
InvalidRequestError: This model's maximum context length is 4097 tokens, however you requested 4106 tokens (3850 in your prompt; 256 for the completion). Please reduce your prompt; or completion length.

This looks like a small bug in the way we estimate token usage. Should be fixed soon.
In the meanwhile you can set chunk_size_limit to be a slightly smaller value (than 4097) when constructing the index to avoid this issue.

This looks like a small bug in the way we estimate token usage. Should be fixed soon.
In the meanwhile you can set chunk_size_limit to be a slightly smaller value (than 4097) when constructing the index to avoid this issue.

This solution only works when similarity_top_k=1.
I have also tried reducing the max_input_size in PromptHelper, doesn't solve the problem.
Changing the LLM to GPT-3.5 could work.
I suspect openAI counts tokens differently, especially for CJK characters.


Add support for indexers (support for Arrays/Lists/Dictionaries/etc)

At present, FormatWith supports basic property navigations in parameter keys. However, it does not support combining this with indexers to navigate into objects arrays, lists, or dictionaries.
For example, this is currently supported:
string result = "{foo.bar}".FormatWith(new
{
    foo = new { bar = "test" }
});

However, we should be able to do this:
string result = "{foo[\"bar\"].Length}".FormatWith(new
{
    foo = new Dictionary<string, string> { ["bar"] = "test" }
});

This is the code that will need to be changed:
https://github.com/crozone/FormatWith/blob/3fbb5ee16b5db299ead5d8851becba8b08021b86/FormatWith/Internal/FormatWithMethods.cs#L320-L361

This will potentially solve https://github.com/crozone/FormatWith/issues/23.


fix: crash when Modal gets shown on Android < 9

📜 Description
Fixed a crash when progress value becomes Infinity and can not be serialized to JS.
💡 Motivation and Context
It happens when we try to divide any double/float number (except 0) by 0.0. In our case we were trying to divide height / persistentKeyboardHeight. To shed more light on the issue I modified condition it.isNan() to it.isNaN() || it.isInfinite(), and we get:
 LOG  {"duration": 160, "eventName": "onKeyboardMoveStart", "height": 0, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 47.71428680419922, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 47.71428680419922, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 47.71428680419922, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 46.57143020629883, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 42.85714340209961, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 36.57143020629883, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 28, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 17.714284896850586, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 9.142857551574707, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 2.2857143878936768, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 0, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMove", "height": 0, "progress": 0, "target": -1}
 LOG  {"duration": 160, "eventName": "onKeyboardMoveEnd", "height": 0, "progress": 0, "target": -1}

In onStart the keyboardHeight=0, isKeyboardVisible-false and we don't update this.persistentKeyboardHeight (it's 0.0 by default).
From logs above it looks like keyboard is animating from 47 pixels to 0, but in fact there is no keyboard animation on the screen at all! 🤯 So in my understand it's a bug somewhere in google code (or in my code - but such animation is not correct). Below are the options that I considered for a fix:
1⃣ add a condition, that will check if a prev height !== 0 and if nextHeight === 0 then ignore an animation
Such solution will add more complexity, more if-statements without an explicit benefits and warranty that it will fix/work for other similar scenarios.
2⃣ check that target == -1 and ignore animation then
Not a reliable solution, because we start to depend on 3rd party variables state. And it's a known fact, that if you get a transitive dependencies, then the solution drastically becomes more complex.
3⃣ add isInfinite check and set progress to 0 then
While it fixes a crash we still get an incorrect height values so any animation that depends on these values will be running and it will look strange 😬
4⃣ don't attach keyboard callbacks to Modal window on Android 9
The most perspective solution - on Android < 12 all events are passing through the main window (and actually attaching a callback is not necessary there, but when I implemented https://github.com/kirillzyusko/react-native-keyboard-controller/pull/466 and https://github.com/kirillzyusko/react-native-keyboard-controller/pull/624 I decided to keep the code for consistency). So if we remove these callbacks (if we attach them to window only for Android 12) then all code works well on both platforms.
Closes https://github.com/kirillzyusko/react-native-keyboard-controller/issues/714
📢 Changelog
Android

don't attach keyboard callbacks on Android < 12 to Modal window;

🤔 How Has This Been Tested?
Tested in reproduction example and on CI.
📸 Screenshots (if appropriate):
https://github.com/user-attachments/assets/76331e0d-6779-4a4b-a837-ba4802ac4139
📝 Checklist

[x] CI successfully passed
[x] I added new mocks and corresponding unit-tests if library API was change

I'm not sure if the root cause is the same, but I encountered some crashes in production from the same piece of code (height / persistentKeyboardHeight resulting in INF). This issue isn't limited to Android versions below 9.

@antFrancon may I ask you to update to 1.15.0 and check if the problem happens again? If yes, then please, open a new issue with all the information that you can gather and we can decide what to do next to fix this problem 👀
Maybe you can discover when this problem happens, i. e. user went from background to foreground, or opened a Modal or something else - any additional information can be super helpful 🙏

@kirillzyusko Of course! I'm investigating this right now. I'll open a separate issue after gathering more information.

@antFrancon thank you! ❤


Issues/1 - Create React frontend client

Created shell UI with ReactJS
Integrated react routing
Integrated typescript and linting
Integrated Material UI and Sass

@ottogiron Yes, I used create-react-app for the front end project. I guess it makes sense to have a development Readme section.

@ottogiron Can you check Readme.md and let me know if I have missed something?


Answer Doorbell and View camera

Hi, would be great if you could answer the Doorbell like on the Unifi Access app, and view the doorbell camera before unlocking. And also to have the doorbell chime come through HA on the android tablet speaker

Unifi Access video feed is unfortunately not available via the public API
As for doorbell chime, you can easily create an automation to support that. Use the doorbell_pressed binary_sensor as a trigger when set to true triggers an action like play an audio file (chime) on a media_player (tablet, speaker, etc…).


non-nullable

Thanks for the pull request. I'll merge this when non-nullable is production ready.

I just change this function,and work good;
Stream? on() {
if (T == dynamic) {
return streamController.stream;
} else {
return streamController.stream.where((event) => event is T).cast();
}
}

null-safety is now released, will you update and publish a new relase?
https://dart.dev/null-safety/migration-guide


Swift 2.0 support

I notice there's no Swift-2.0 branch for CVCalendar.
Has Swift 2.0 support been considered? What is the migration strategy?
(Note, "Pull Requests gratefully accepted" is a valid response to this issue :-)

+1

+1

+1

Need this as well please :+1:

I see that a new release for Swift 2 was posted, but the pod does not seem to be available. Is this possible?

+1

For this moment, I opened CVCalendar folder in my folder project with pods and I updated the files manually. I hope can help while is update on cocoapods

@dasoga That's actually not necessary and not the way to go, you should specify the repository location in the podfile instead until the podspec is being updated, i.e.
pod 'CVCalendar', :git => 'https://github.com/Mozharovsky/CVCalendar', :branch => 'master'

@elsesiy thanks dude, i didn't know that!

I just cloned the master branch, which according to the log, should have been converted to Swift 2.0, but still Xcode asks me if I want to convert to latest Swift syntax and the compiler reports a bunch of error.
What's the status here?

@erikjalevik The master branch supports Swift 2.0, so how did you clone the branch? Are you using cocoapods? If so please have it point to the git repository as stated above, since the podspec hasn't been updated yet. Otherwise please have a look at  https://github.com/Mozharovsky/CVCalendar/pull/115#issuecomment-142946245

Are this still errors in the 2.0 version? I am unable to compile with Swift 2.0, but it seems like that is the latest version. So still in development?

@derdida Swift 2 is officially supported by now. I already mentioned several times, that the pod spec hasn't been updated yet, so you have to specify the repository as mentioned above. If you're not using cocoapods please make sure you've added the sources to compile sources in build settings. If you've further remarks, please let us know and specify as specific as possible what the exact problem is.

Pinging @Mozharovsky would you be able to update the podspec to match the 1.2.0 release? Also, you  might want to pull the current 1.2.0 release on GitHub for this repos releases.

@dwightwatson Thanks for contributing and helping others to use this library (https://github.com/Mozharovsky/CVCalendar/issues/123)
Since this is a recurring issue, I have created a PR with the updated Podspec rightaway. Hopefully @Mozharovsky will merge it soon!

Hello guys! Version 1.2.6 has been pushed into CocoaPods, check this out!

Hello, yes, the 1.2.6 works for me, however still some warnings are presented when compiling, is there any method to get rid of it?

@poppindouble We'll take care of it soon, just ignore them :+1:

@poppindouble If you're on the master branch, the latest commit should've cleaned all warnings! -> Close

Thanks!!
On Sunday, 1 November 2015, Jonas-Taha El Sesiy<EMAIL_ADDRESS>wrote:

Closed #113 https://github.com/Mozharovsky/CVCalendar/issues/113.
—
Reply to this email directly or view it on GitHub
https://github.com/Mozharovsky/CVCalendar/issues/113#event-451398233.

how to get lastdate of a month from my input date.Ex. input: 24-9-16 output: 30-9-16


RLHF-V data problem

Thank you for your excellent work, but there is no description related to the training data "RLHF-V" in the repository.
Could you please provide the relevant processing code?

Hi, we have the same problem. Have you found the solution? Thank you.

I processed the data from [llamafactory/RLHF-V] into a suitable format, and I can run the V-DPO model now.
However, since the authors have not responded to me, I am unaware of the specific data construction methods mentioned in the paper :(
Here is the RLHF-V data I processed: RLHF-V-Dataset-5.7k.json.
You can extract the images from [llamafactory/RLHF-V] using the following code:
import cv2
import numpy as np
import pandas as pd

rlhf_v = pd.read_parquet("./rlhf-v.parquet")
path_prefix = './images'

print('Processing images : ')
for index, img in enumerate(rlhf_v["images"]):
    image_bytes = img[0]['bytes']
    image_np = cv2.imdecode(np.frombuffer(image_bytes, dtype=np.uint8), cv2.IMREAD_COLOR)
    cv2.imwrite(path_prefix + f"/{index}.jpg", image_np)
print('finish')

I processed the data from [llamafactory/RLHF-V] into a suitable format, and I can run the V-DPO model now. However, since the authors have not responded to me, I am unaware of the specific data construction methods mentioned in the paper :(
Here is the RLHF-V data I processed: RLHF-V-Dataset-5.7k.json. You can extract the images from [llamafactory/RLHF-V] using the following code:
import cv2
import numpy as np
import pandas as pd

rlhf_v = pd.read_parquet("./rlhf-v.parquet")
path_prefix = './images'

print('Processing images : ')
for index, img in enumerate(rlhf_v["images"]):
    image_bytes = img[0]['bytes']
    image_np = cv2.imdecode(np.frombuffer(image_bytes, dtype=np.uint8), cv2.IMREAD_COLOR)
    cv2.imwrite(path_prefix + f"/{index}.jpg", image_np)
print('finish')

Thank you for your instruction,  I will try it : )


python310Packages.aiorun: 2021.10.1 -> 2022.11.1

Diff: https://github.com/cjrh/aiorun/compare/refs/tags/v2021.10.1...v2022.11.1
Changelog: https://github.com/cjrh/aiorun/blob/v2022.11.1/CHANGES
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

3 packages built:

python310Packages.aiorun
python39Packages.aiorun
unifi-protect-backup


Listed everything alphabetically

@sdmg15 I think you should update the CONTRIBUTING.md to ask contributors to list their contributions alphabetically.

OMG, you did a large set !
isn't there a tool that can check that after each commit ?
THanks.

Actually, I don't know anything in particular. But, I think I might be able to help. Give me some time, I'll get back to you. ok?

Sure.

What I am thinking is to make a script that would verify if two files have the same content, irrespective of the line they are present in. would that be okay?

I  don't get you well, the task of checking dupes is already done by awesome-bot I think.

My bad, I misunderstood you completely.
So, my reply to this question

isn't there a tool that can check that after each commit ?

No, I am not aware of any such tool.

:sweat_smile:
Ok now we agree.

Resolved conflicts, and if there are any issues with the PR then let me know


Include channel claim_id for channel based URI resolutions

resolve on a channel based URL does not include the claim_id for the channel. This means that one cannot build a permanent URL based on the return values of a non-permanent URL. E.g.
./lbrynet-cli resolve @IGNonLBRY/linked-ep6
{
  "@IGNonLBRY/linked-ep6": {
    "certificate": {
      "address": "bVmpKZZTv8rwnRbmicnsFGBQ5xii2pu6r9",
      "amount": "100",
      "claim_id": "82433028490fb130238ad6cdd59d48bdb64b7d79",
      "claim_sequence": 1,
      "decoded_claim": true,
      "depth": 42592,
      "effective_amount": "100",
      "has_signature": false,
      "height": 156023,
      "hex": "08011002225e0801100322583056301006072a8648ce3d020106052b8104000a03420004c73e433e1fa00b5e52c09d10f5a23629f123976c8fe11cbe0f21bd0afb15596203cf3b3c7346a8ffd0058b7183e5c7580da64555b6aaf10ed74f206b952f1880",
      "name": "@IGNonLBRY",
      "nout": 1,
      "supports": [],
      "txid": "324c2d2bed3ece3443192d26da914a5a94a7b70e5ddc8dac74ccf0f66af0150a",
      "value": {
        "certificate": {
          "keyType": "SECP256k1",
          "publicKey": "3056301006072a8648ce3d020106052b8104000a03420004c73e433e1fa00b5e52c09d10f5a23629f123976c8fe11cbe0f21bd0afb15596203cf3b3c7346a8ffd0058b7183e5c7580da64555b6aaf10ed74f206b952f1880",
          "version": "_0_0_1"
        },
        "claimType": "certificateType",
        "version": "_0_0_1"
      }
    },
    "claim": {
      "absolute_channel_position": 0,
      "address": "bKpnkakDNuAyFYFiJuUdZxwiXidTMhXeyE",
      "amount": 1.0,
      "channel_name": "@IGNonLBRY",
      "claim_id": "53101af252b56e6aab9d45c977f83507b2fe594e",
      "claim_sequence": 1,
      "decoded_claim": true,
      "depth": 42546,
      "effective_amount": 1.0,
      "has_signature": true,
      "height": 156069,
      "hex": "080110011af401080112ac01080410011a154c696e6b656420546f6765746865722045702e2036222b576520426172656c79205375727669766564205a656c646127732056616820527574612044756e67656f6e2a0349474e3212436f7079726967687420323031372049474e38004a4368747470733a2f2f73332e616d617a6f6e6177732e636f6d2f66696c65732e6c6272792e696f2f7468756d626e61696c732f69676e2d6c696e6b65642d30362e6a706752005a001a41080110011a3013a6acf40bf5751f7721b3b89ae446646f39a138300e97b216b98f81585aba941919dbc2cb0863ac787c944b1689045d2209766964656f2f6d70342a5c080110031a4014bc78b41ba6319345db9d581594fb3e6a11f45dcb5e629b02df8806abe722082e0f01b09020ea9b6fa8c78aa6908fc04860ae985c00a4ac78bbffaba77a5c15221482433028490fb130238ad6cdd59d48bdb64b7d79",
      "name": "linked-ep6",
      "nout": 0,
      "signature_is_valid": true,
      "supports": [],
      "txid": "5e090c41391f55b05b68d282225e162de895b251169a29b0b5b63dd74ca908a3",
      "valid_at_height": 156069,
      "value": {
        "claimType": "streamType",
        "publisherSignature": {
          "certificateId": "82433028490fb130238ad6cdd59d48bdb64b7d79",
          "signature": "14bc78b41ba6319345db9d581594fb3e6a11f45dcb5e629b02df8806abe722082e0f01b09020ea9b6fa8c78aa6908fc04860ae985c00a4ac78bbffaba77a5c15",
          "signatureType": "SECP256k1",
          "version": "_0_0_1"
        },
        "stream": {
          "metadata": {
            "author": "IGN",
            "description": "We Barely Survived Zelda's Vah Ruta Dungeon",
            "language": "en",
            "license": "Copyright 2017 IGN",
            "licenseUrl": "",
            "nsfw": false,
            "preview": "",
            "thumbnail": "https://s3.amazonaws.com/files.lbry.io/thumbnails/ign-linked-06.jpg",
            "title": "Linked Together Ep. 6",
            "version": "_0_1_0"
          },
          "source": {
            "contentType": "video/mp4",
            "source": "13a6acf40bf5751f7721b3b89ae446646f39a138300e97b216b98f81585aba941919dbc2cb0863ac787c944b1689045d",
            "sourceType": "lbry_sd_hash",
            "version": "_0_0_1"
          },
          "version": "_0_0_1"
        },
        "version": "_0_0_1"
      }
    },
    "claims_in_channel_pages": 0
  }
}

The permanent URL for lbry://@IGNonLBRY/linked-ep6 is @IGNonLBRY#82433028490fb130238ad6cdd59d48bdb64b7d79/linked-ep6, but since the channel claim id is not included, this URI cannot be built from the response provided by resolve.

Isn't it right at the top in the cerficate section? Third item.

Bah, so it is, how did I mess up checking that? What prompted this is that it does not appear to be available in the fileList action inside of the app, but I'll have to dig more.


Add Ghidra to Maven Central (or another Maven repository)

Is your feature request related to a problem? Please describe.
In order to create applications/libraries depending on Ghidra, one must either a) package the single jar and use it as a dependency (which is a 150+MB jar, mostly composed of unused resources) or b) customise the classpath significantly. Furthermore, it requires developers of these applications/libraries to have Ghidra installed locally in order to build applications using Ghidra. Libraries depending on Ghidra which are exported to Maven Central or used via jitpack or similar cannot explicitly declare the dependency to be used by other projects and would need to package Ghidra within the jar (shadowed) to be used by other projects.
Describe the solution you'd like
Add Ghidra to Maven Central or another Maven repository. Preferably, this would allow for the archival of all features individually so that these dependencies can be selectively collected as-necessary.
Describe alternatives you've considered
As workarounds, one can simply have Ghidra installed locally and significantly customise the gradle/maven buildscripts or single-jar the application. Local maven repos can be spun up by developers, but this is also significantly sub-optimal.
Additional context
N/A

At this time we have no plans to distribute Ghidra outside of how we are currently doing it on GitHub.  Apologies for any inconveniences this might cause.


Cookie.CookieError: Illegal key value: _csrf/link

Steps to reproduce the problem:

mitmdump -t .
visit http://dailymotion.com using the proxy
website tries to set cookie _csrf/link, which crashes mitmdump

What is the expected behavior?
I would expect mitmdump to not crash, but either forward the cookie as is, or not forward it.
What went wrong?
According to RFC 6265 (Cookie RFC), which refers to RFC 2616 (HTTP), "_csrf/link" is an invalid
cookie name because it contains a "/". Visiting the website with Chrome does not segfault Chrome, but instead continues as if the cookiename is valid. I believe mitmdump should handle this error gracefully instead of crashing.
Traceback (most recent call last):
File "/usr/local/bin/mitmdump", line 9, in
load_entry_point('mitmproxy==0.18', 'console_scripts', 'mitmdump')()
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/main.py", line 102, in mitmdump
master.run()
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/dump.py", line 350, in run
super(DumpMaster, self).run()
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/controller.py", line 27, in run
self.tick(0.1)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/flow.py", line 845, in tick
return super(FlowMaster, self).tick(timeout)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/controller.py", line 39, in tick
handle_func(obj)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/dump.py", line 334, in handle_response
flow.FlowMaster.handle_response(self, f)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/flow.py", line 1039, in handle_response
self.process_new_response(f)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/flow.py", line 936, in process_new_response
self.stickycookie_state.handle_response(f)
File "/usr/local/lib/python2.7/dist-packages/mitmproxy/flow.py", line 337, in handle_response
c = http_cookies.SimpleCookie(str(i))
File "/usr/lib/python2.7/Cookie.py", line 583, in init
if input: self.load(input)
File "/usr/lib/python2.7/Cookie.py", line 640, in load
self.__ParseString(rawdata)
File "/usr/lib/python2.7/Cookie.py", line 677, in __ParseString
self.__set(K, rval, cval)
File "/usr/lib/python2.7/Cookie.py", line 589, in __set
M.set(key, real_value, coded_value)
File "/usr/lib/python2.7/Cookie.py", line 459, in set
raise CookieError("Illegal key value: %s" % key)
Cookie.CookieError: Illegal key value: _csrf/link
I would submit a fix myself, but I'm a bit swamped with other work right now
Any other comments?

Mitmproxy Version: 0.18
Operating System: Ubuntu

We are using the python standard cookie lib, which states the following in its documentation (py2 and py3 alike):
https://docs.python.org/2/library/cookie.html
https://docs.python.org/3/library/http.cookies.html

The module formerly strictly applied the parsing rules described in the RFC 2109 and RFC 2068 specifications. It has since been discovered that MSIE 3.0x doesn’t follow the character rules outlined in those specs and also many current day browsers and servers have relaxed parsing rules when comes to Cookie handling. As a result, the parsing rules used are a bit less strict.

The character set, string.ascii_letters, string.digits and !#$%&'*+-.^_`|~: denote the set of valid characters allowed by this module in Cookie name (as key).

So fixing this or handling gracefully might be tricky - without shipping our own cookie parsing lib.
And just removing the cookie (i.e. gracefully ignoring it) might lead to confusing results and creates more harm than good.

Or we might be able to get way with it by using this trick: https://bugs.python.org/issue2193#msg124178


Add create-react-app and gatsby starter examples to project

Should put in an examples folder.
This will let us easily test SSR and the library's build in general in other systems.

not doing this in the project


Set flag to enable sourcemap

Turn out they change the default in webpack 2.0, we just have to enable it

Coverage remained the same at 29.912% when pulling 00889cb83b8de19617b41631d97c8eb50b2d35d1 on qingweibinary:qingwei/use_webpack2 into f9d82ca8472eecfbded8fba0e8ef4ac7e72fcb2a on binary-com:master.


Unstable and freezes

I'm using the plugin with SignalK 2.7.0 on a Raspberry Pi 3B+. The plugin can run for several hours, and then just stops reporting values without any error messages in the logs. Everything else in SignalK seems to be running just fine, so it's only the Victron BL plugin that stops.
The last log entry just looks totally normal.
Apr 10 18:21:20 signalk signalk-server[9574]: 2024-04-10T16:21:20.888Z signalk-victron-ble {"updates": [{"source": {"label": "Victron", "type": "Bluetooth", "src": "XX:XX:XX:XX:XX:XX"}, "timestamp": "2024-04-10T16:21:20.887456Z", "values": [{"path": "electrical.solar.mppt-100-50.voltage", "value": 12.52}, {"path": "electrical.solar.mppt-100-50.current", "value": 0.0}, {"path": "electrical.solar.mppt-100-50.chargingMode", "value": "off"}, {"path": "electrical.solar.mppt-100-50.panelPower", "value": 0}, {"path": "electrical.solar.mppt-100-50.loadCurrent", "value": null}, {"path": "electrical.solar.mppt-100-50.yieldToday", "value": 0}]}]}

Restarting SignalK brings the plugin back to life, until it stops again after approx 10 hours.
What can be done to make the plugin run stable over time?

I'm afraid I haven't seen this behaviour, so you're probably going to have to debug it for me.
Can you still see it running in ps? Can you see what it got stuck on, with strace or gdb?

You could also try running it standalone, with the test harness. You can create a test-devices.json file, with contents like:
{
  "devices": [
    {
      "id": "house",
      "mac": "D9:8F:D1:D8:CB:F2",
      "key": "9ee0db100da5ce487156ac665c399ddb",
      "secondary_battery": "start"
    },
   { ... }
  ]
}

Listing all your devices that you have registered in SignalK. Then run ./test.

Thanks for the feedback. I think the problem was on my side. After making a few adjustments on the Bluetooth stack in my RPi and changing the Load Output Operation Mode in my SmartSolar to Always on, the plugin has now run without interruption for several days. I think the changing Load Operation Mode in fact was the important part.
Thanks for a great plugin and quick response!


Touch area issue on some UI elements (38dp -> 48dp)

Android device: all
Android OS version: all
FirebaseUI version: 4.1.0

Step 3: Describe the problem:
Steps to reproduce:
After uploading the app to Google Play, the automatically created pre-launch reports state that some clickable parts of the Firebase UI have a too small size (38dp, should be 48dp).
Observed Results:

Expected Results:
Firebase-UI should not give any problems in the pre-launch reports of Google Play.

This has been fixed and released in version 4.2.1.


Update subgraphNameByChainMap for Arbitrum chain

This pull request includes a change to the subgraphNameByChainMap in the subgraphNameByChainMap.ts file to add support for the Arbitrum chain.

sdk/subgraph-manager-common/src/utils/subgraphNameByChainMap.ts: Added ChainId.ARBITRUM to the subgraphNameByChainMap to support the Arbitrum chain.

Summary by CodeRabbit

New Features

Added support for the Arbitrum chain by mapping ChainId.ARBITRUM to the subgraph name 'summer-protocol-artitrum'.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (dev@db6e28f). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             dev     #543   +/-   ##
======================================
  Coverage       ?   73.68%
======================================
  Files          ?       19
  Lines          ?      152
  Branches       ?        4
======================================
  Hits           ?      112
  Misses         ?       40
  Partials       ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: new 1.2.3

:tada: This PR is included in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[CWS-2398] Add syscall context to rename event

What does this PR do?
This PR adds syscall arguments to the rename event.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Refactoring

Refactored to fit Expenditure Expert.

Codecov Report

Merging #127 (2d791d4) into master (4f7660a) will decrease coverage by 4.56%.
The diff coverage is 74.26%.

@@             Coverage Diff              @@
##             master     #127      +/-   ##
============================================
- Coverage     72.15%   67.59%   -4.57%
+ Complexity      399      341      -58
============================================
  Files            70       67       -3
  Lines          1232     1117     -115
  Branches        125      101      -24
============================================
- Hits            889      755     -134
- Misses          311      321      +10
- Partials         32       41       +9

Impacted Files
Coverage Δ

src/main/java/seedu/address/Main.java
0.00% <ø> (ø)

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

...in/java/seedu/address/commons/core/LogsCenter.java
78.37% <ø> (ø)

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...java/seedu/address/logic/commands/ExitCommand.java
100.00% <ø> (ø)

.../expense/exceptions/DuplicateExpenseException.java
0.00% <0.00%> (ø)

...l/expense/exceptions/ExpenseNotFoundException.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
0.00% <0.00%> (-20.00%)
:arrow_down:

src/main/java/seedu/address/ui/ExpenseCard.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/ui/ExpenseListPanel.java
0.00% <0.00%> (ø)

... and 33 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 4f7660a...2d791d4. Read the comment docs.


Vickel: Watch Chose2B

Vickel requests the watch of the watch_keyword Chose2B. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Chose2B has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Role based access control for team members

Restrict the CRUD operations on the back of RBAC.

Hi, I like to work on this.
Can you give more details about it?


Configure automated Docker builds based on github commits

@bpben @j-t-t @alicefeng @shreyapandit  I got my access to the D4D Docker Hub account elevated and we now have automated builds running on all branches - https://hub.docker.com/r/datafordemocracy/crash-model/tags/
Basically whenever a commit is pushed to a branch on the main repo, it will trigger a build of an image that is tagged with that branch name (the exception being master branch which relates to the image tagged latest)
We can enable/disable this for any branch as necessary, but right now it's probably fine to have all branches enabled.
Thanks.

I've created a PR that updates the documentation around the Docker aspect of the project, as well as clearing up a bunch of old references to boston-crash-model
https://github.com/Data4Democracy/crash-model/pull/137

Another PR to resolve last of Docker updates -
https://github.com/Data4Democracy/crash-model/pull/140


raw_mesh --scene buggy keeps repainting even when nothing changes

Repro:
$ cargo r -p raw_mesh
# watch your CPU burn

This seems to be a regression introduced by https://github.com/rerun-io/rerun/pull/2846.

we had a redraw bug that was fixed in 0.8.1. Could be that this got fixed with that, need to confirm.

Confirmed fixed (at least I fail to reproduce on latest main)

I interpreted the original title as a freeze (infinite loop), but it is really an unnecessary repaint, and yes, it is still there.


Add view support

[x] Orm
[ ] Kit

Is there a ticket or anything where we can track the status of view on drizzlekit? Thanks!

Is there a ticket or anything where we can track the status of view on drizzlekit? Thanks!

This is that.

Views are now supported in Kit


Introspection does not generate correct relation

Bug description
npx prisma introspect

Does not produce relation in documentation.
How to reproduce

Initialize database

CREATE TABLE "Category" (
    id SERIAL PRIMARY KEY
);
CREATE UNIQUE INDEX "Category_pkey" ON "Category"(id int4_ops);
CREATE TABLE "Post" (
    id SERIAL PRIMARY KEY
);
CREATE UNIQUE INDEX "Post_pkey" ON "Post"(id int4_ops);
CREATE TABLE "_CategoryToPost" (
    id SERIAL PRIMARY KEY,
    "A" integer NOT NULL REFERENCES "Category"(id) ,
    "B" integer NOT NULL REFERENCES "Post"(id)
);
CREATE INDEX "_CategoryToPost_B_index" ON "_CategoryToPost"("B" int4_ops);

Run npx prisma introspect

Expected behavior
Result similar to documentation.
model Post {
  id         Int        @id @default(autoincrement())
  categories Category[] @relation(references: [id])
}
model Category {
  id    Int    @id @default(autoincrement())
  posts Post[] @relation(references: [id])
}

Actual behavior
model Category {
  id             Int              @default(autoincrement()) @id
  CategoryToPost CategoryToPost[] @relation("CategoryTo_CategoryToPost")
}

model Post {
  id             Int              @default(autoincrement()) @id
  CategoryToPost CategoryToPost[] @relation("PostTo_CategoryToPost")
}

model CategoryToPost {
  A        Int
  B        Int
  id       Int      @default(autoincrement()) @id
  Category Category @relation("CategoryTo_CategoryToPost", fields: [A], references: [id])
  Post     Post     @relation("PostTo_CategoryToPost", fields: [B], references: [id])

  @@index([B], name: "_CategoryToPost_B_index")
  @@map("_CategoryToPost")
}

Environment & setup

OS: Windows
Database: PostgreSQL
Prisma version: @prisma/cli: 2.0.0-beta.3
Node.js version: v12.13.0

If you look at https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-schema/relations#conventions-for-relation-tables-in-implicit-m-n-relations, one of the requirements for prisma to pick up the implicit many to many relationship is A unique index defined on both foreign key columns. What you've posted doesn't have that and instead has an id column in _CategoryToPost. It should work if you remove the id column and add the unique index.

@TLadd I get this warning instead
*** WARNING ***

These models do not have a unique identifier or id and are therefore commented out.
- "CategoryToPost"

It should work if you remove the id column and add the unique index.

You also need to "add the unique index" as in the documentation, then the join table should be converted into an implicit relation between these two tables.

Ok, I finally make it works. Also, is UNIQUE constraint not design to work?
UNIQUE("A", "B") /* Not work */
CREATE UNIQUE INDEX "_CategoryToPost_AB_unique" ON "_CategoryToPost"("A" int4_ops,"B" int4_ops) /* Work */


stm32cubemx: 5.6.1 -> 6.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/stm32cubemx/versions.
meta.description for stm32cubemx is: "A graphical tool for configuring STM32 microcontrollers and microprocessors"
meta.homepage for stm32cubemx is: "https://www.st.com/en/development-tools/stm32cubemx.html"
meta.changelog for stm32cubemx is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.0.1 with grep in /nix/store/07fw1knnxxgwc75fmawbbsy3baaivf46-stm32cubemx-6.0.1

directory tree listing: https://gist.github.com/4355036105a8af332ebb2f1789e2a300

du listing: https://gist.github.com/3d2457167f70ae82e20b4b155bb2b354

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
stm32cubemx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/07fw1knnxxgwc75fmawbbsy3baaivf46-stm32cubemx-6.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A stm32cubemx https://github.com/r-ryantm/nixpkgs/archive/a171248792a8482e0408857df513163631c23736.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/07fw1knnxxgwc75fmawbbsy3baaivf46-stm32cubemx-6.0.1
ls -la /nix/store/07fw1knnxxgwc75fmawbbsy3baaivf46-stm32cubemx-6.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

stm32cubemx

Maintainer pings
cc @wucke13 for testing.

Looks good to me!


[P4_Symbolic] Adding p4_symbolic/packet_synthesizer/coverage_goal.proto

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 584 targets (2 packages loaded, 48 targets configured).
INFO: Found 584 targets...
INFO: From Compiling p4_symbolic/sai/parser.cc:
p4_symbolic/sai/parser.cc: In function 'absl::lts_20230802::StatusOr<std::vectorz3::expr > p4_symbolic::EvaluateSaiParser(const SymbolicPerPacketState&)':
p4_symbolic/sai/parser.cc:59:51: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
59 |   constraints.push_back(icmp.valid == (ipv4.valid && ipv4.protocol == 0x01 ||
|                                        ~^~~~~~~~~~~~~~
p4_symbolic/sai/parser.cc:61:50: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
61 |   constraints.push_back(tcp.valid == (ipv4.valid && ipv4.protocol == 0x06 ||
|                                       ~^~~~~~~~~~~~~~
p4_symbolic/sai/parser.cc:63:50: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
63 |   constraints.push_back(udp.valid == (ipv4.valid && ipv4.protocol == 0x11 ||
|                                       ~^~~~~~~~~~~~~~
INFO: Elapsed time: 6.263s, Critical Path: 5.25s
INFO: 4 processes: 1 internal, 3 linux-sandbox.
INFO: Build completed successfully, 4 total actions
Test Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 584 targets (0 packages loaded, 10 targets configured).
INFO: Found 394 targets and 190 test targets...
INFO: Elapsed time: 186.584s, Critical Path: 117.71s
INFO: 244 processes: 289 linux-sandbox, 18 local.
INFO: Build completed successfully, 244 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.6s
//gutil:proto_matchers_test                                              PASSED in 0.7s
//gutil:proto_ordering_test                                              PASSED in 0.6s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.6s
//gutil:test_artifact_writer_test                                        PASSED in 0.9s
//gutil:testing_test                                                     PASSED in 0.7s
//gutil:timer_test                                                       PASSED in 5.1s
//gutil:version_test                                                     PASSED in 2.4s
//lib:basic_switch_test                                                  PASSED in 0.9s
//lib:ixia_helper_test                                                   PASSED in 1.2s
//lib/basic_traffic:basic_p4rt_util_test                                 PASSED in 1.2s
//p4rt_app/tests:state_verification_test                                 PASSED in 3.0s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.6s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.1s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.0s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.7s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.6s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.1s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.7s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.8s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.2s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.6s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.1s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 5.5s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 1.0s
//sai_p4/instantiations/google/tests:p4_fuzzer_integration_test          PASSED in 4.5s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.9s
//tests/qos:gnmi_parsers_test                                            PASSED in 0.1s
//tests/qos:gnmi_parsers_test_runner                                     PASSED in 0.0s
//thinkit:bazel_test_environment_test                                    PASSED in 0.5s
//thinkit:generic_testbed_test                                           PASSED in 1.0s
//thinkit:mock_control_device_test                                       PASSED in 0.6s
//thinkit:mock_generic_testbed_test                                      PASSED in 1.5s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.9s
//thinkit:mock_ssh_client_test                                           PASSED in 0.3s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.7s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 1.6s
Stats over 5 runs: max = 1.6s, min = 0.8s, avg = 1.0s, dev = 0.3s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 45.5s
Stats over 50 runs: max = 45.5s, min = 0.8s, avg = 3.9s, dev = 10.6s
Executed 190 out of 190 tests: 190 tests pass.
INFO: Build completed successfully, 244 total actions

Co-authored-by: kheradmandG<EMAIL_ADDRESS>

@kishanps , could you pls review


Bump up ruby and gems

What did we change?
Bump up Rails and ruby versions
Why are we doing this?
To bring compatibility for Rails 6
How was it tested?

[x] Specs
[x] Locally
[ ] Staging

Thanks for the contribution. It looks like our ezcater_rubocop gem may need to be updated to a newer version that supports ruby 2.6. I'll look at doing that and then this can be rebased.

Thanks, Tim, just reverted it back to 2.5. Perhaps, best to do the ruby change in another PR once you have ezcater_rubocop updated

CI test reporter is failing:
Coverage report generated for RSpec to /home/circleci/ezcater/coverage. 53 / 54 LOC (98.15%) covered.
Error: response from https://api.codeclimate.com/v1/test_reports.
HTTP 401: You are not authorized for this action
Usage:
  cc-test-reporter after-build [flags]

No, I ran tests on another branch and it correctly submitted the coverage. Perhaps it is restricting to members of our Github org?
I don't think there is anything more you need to do here. I'm happy that the tests are passing with the exception of the coverage. Do you need a release cut so that you can test in combination with other things?

CI test reporter is failing:
Coverage report generated for RSpec to /home/circleci/ezcater/coverage. 53 / 54 LOC (98.15%) covered.
Error: response from https://api.codeclimate.com/v1/test_reports.
HTTP 401: You are not authorized for this action
Usage:
  cc-test-reporter after-build [flags]

Any idea, why?

Great, yes please if you can cut a new release that would be amazing, thank you 🙏

@gauravtiwari you should be all set with v1.1.0


feat: emulated mimc (WIP)

Work in progress WIP for emulated MiMC. Do not merge!
Open issues right now:

[ ] we get an import cycle because we use mimc in for logderivargument and multicommit. Both in both cases we do not need to use MiMC specifically. There, we can also do the squaring instead of using MiMC. Actually this is already implemented in the mulmod PR. After we have merged that we can change mimc.NewMiMC to return hash.FieldHasher instead. Then it is clearer what the function is about. Most importantly, then we can also implement hash.FieldHasherGeneric[t emulated.FieldParam] as an interface.
[ ] implement emulated mimc
[ ] implement Fiat-Shamir using hash.FieldHasherGeneric

cc @ThomasPiellard
Description

Fixes #848
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How has this been tested?

[ ] Test A
[ ] Test B

How has this been benchmarked?

[ ] Benchmark A, on Macbook pro M1, 32GB RAM
[ ] Benchmark B, on x86 Intel xxx, 16GB RAM

Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I did not modify files generated from templates
[ ] golangci-lint does not output errors locally
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

We use alternative approach in PLONK verifier.