No success with tokeninfo

I manged to pass a user token from rdpgw through xrdp with enable_token_login=true and pam-jwt back to rdpgw.
The generated rdp file contains the username with concatenated token:
gatewayhostname:s:rdpgw.lab.0x1b.ch:8443
full address:s:ubuntu03.lab.0x1b.ch:3389
username:s:beat^_eyJhbGciOiJkaXIiLCJjdHkiOiJKV1QiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2IiwiemlwIjoiREVGIn0..kyekj2rYsFoUl781IkGG0w.x8vf2eBx_szYtYGfuYjtoTD33DBUENzvhPRjAWaho7zZw1BVgXjyPnmqkqiZdAbuBTMKuwN6YIGDsiN1gvIzLQ.b82or-ul-bCkDmtvUVMmbg
gatewaycredentialssource:i:5
gatewayprofileusagemethod:i:1
gatewayusagemethod:i:1
...

xrdp-sesman successfully calls the PAM module:
Apr 11 20:28:05 ubuntu03 xrdp[8765]: [INFO ] sending login info to session manager, please wait...
Apr 11 20:28:05 ubuntu03 pam-jwt[8613]: token url set to https://rdpgw.lab.0x1b.ch:8443/tokeninfo?access_token

According to rdpgw's log I get the identical token back to validate - sadly no success:
Apr 11 20:28:05 rdpgw.lab.0x1b.ch docker[9665]: rdpgw  | 2024/04/11 18:28:05 Identity SessionId: b74ac558-9a75-40ab-a611-18a73ad09964, UserName: : Authenticated: false: Path: /tokeninfo?access_token=eyJhbGciOiJkaXIiLCJjdHkiOiJKV1QiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2IiwiemlwIjoiREVGIn0..kyekj2rYsFoUl781IkGG0w.x8vf2eBx_szYtYGfuYjtoTD33DBUENzvhPRjAWaho7zZw1BVgXjyPnmqkqiZdAbuBTMKuwN6YIGDsiN1gvIzLQ.b82or-ul-bCkDmtvUVMmbg
Apr 11 20:28:05 rdpgw.lab.0x1b.ch docker[9665]: rdpgw  | 2024/04/11 18:28:05 Cannot decrypt token go-jose/go-jose: missing payload in JWS message

Now I'm lost, the encoder and decoder for the user token goes beyond my Go skills 😬  I'm not sure if I screwed something up or if the code to encode and decode the limited JWT do not match.
For completeness my rdpgw.conf:
Server:
 CertFile: /opt/rdpgw/server.pem
 KeyFile: /opt/rdpgw/key.pem
 GatewayAddress: rdpgw.lab.0x1b.ch:8443
 Port: 8443
 Hosts:
  - ubuntu01.lab.0x1b.ch:3389
  - ubuntu02.lab.0x1b.ch:3389
  - ubuntu03.lab.0x1b.ch:3389
 HostSelection: unsigned
 SessionKey: d505d0d5ce23977b9d544e224692f77d
 SessionEncryptionKey: f088998ac5b017a2593f211a8ce39ca9
OpenId:
 ProviderUrl: https://rdpgw.lab.0x1b.ch/auth/realms/demo
 ClientId: rdpgw
 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Client:
 UsernameTemplate: "{{ username }}\x1f{{ token }}"
 NetworkAutoDetect: 0
 BandwidthAutoDetect: 1
 ConnectionType: 6
Security:
  PAATokenSigningKey: fc4c2095bc3409375461bc9ef36f7b89
  PAATokenEncryptionKey: 8188742ac3cf0efe67805a9797d2a349
  UserTokenEncryptionKey: d3ecd7e565e56e37e2f2e95b584d8c0c
  UserTokenSigningKey: 5aa3a1568fe8421cd7e127d5ace28d2d
  VerifyClientIp: true
  EnableUserToken: true
Caps:
 TokenAuth: true

I fixed this is master now (I think). Issue was that the UserTokenSigningKey wasn't used as it makes the token bigger and we have very limited space.
So for your version can can remove UserTokenSigningKey and I think it will work. Or switch to the latest image (no release yet) and then signing will be done (with the caveat above). Also the new version supports not signing and just encryption when UserTokenSigningKey is omitted.

Thanks @bolkedebruin for the quick fix! I had to add the possibility of providing an empty UserTokenSigningKey, now the token based login works nicely.

Just in case someone else wonders about the limits like me and bashes their head against this...
As far as I can see, the reason why the limit is 255 bytes, is that the X.224 length field is a single byte.
This is a view into the TCP packet:
Internet Protocol Version 4, Src: <IP_ADDRESS>, Dst: <IP_ADDRESS>
Transmission Control Protocol, Src Port: 35334, Dst Port: 3389, Seq: 1, Ack: 1, Len: 263
TPKT, Version: 3, Length: 263
    Version: 3
    Reserved: 0
    Length: 263
ISO 8073/X.224 COTP Connection-Oriented Transport Protocol
    Length: 2
    PDU Type: CR Connect Request (0x0e)
    Destination reference: 0x0000
    Source reference: 0x0000
    0000 .... = Class: 0
    .... ..0. = Extended formats: False
    .... ...0 = No explicit flow control: False
Remote Desktop Protocol
    Routing Token/Cookie [truncated]: Cookie: mstshash=LOCALHOST\USERNAME\x1FeyJhbGciOiJkaXIiLCJjdHkiOiJKV1QiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2IiwiemlwIjoiREVGIn0.......
    Type: RDP Negotiation Request (0x01)
    Flags: 0x00
    Length: 8
...

xrdp will note something like:
[ERROR] Invalid length indicator in [ITU-T X.224] CR-TPDU (Connection Request). expected 258, received 2

In case the username field is too long, the single byte length field is simply being rolled over, the Cookie: mstshash= value being too long.
It's not that the JWT token has to be less than 511 (or 255) bytes, all of it together hast to fit in the length field.
The cookie contains a hostname, the username, the byte \x1f and the JWT token.  The longer each one is, the less likely it is to work.
Signing the Token using UserTokenSigningKey increases the size of the JWT from 213 to 298 bytes for me, making it impossible to fit, hence no signing key is a good start.

x.224 Connection Request: 7 bytes
RDP Negotiation: 28 bytes + (\, \x1f, \r\n as structure within the mstshash)

So 255-7-28-1-1+2 = 218 bytes left for host/user/token, or just 3 bytes for host/user, depending on the length of the username because it's also encoded in the token.  I'm not sure if I'm missing anything or if the host can be skipped (must be a client thing, cursory look into xfreerdp was unsuccessful, xrdp simply ignores it)...
Hopefully not embarrassing myself on the internet.... :roll_eyes:

Thanks @BuJo - you did not embarrass yourself. I think you've summarized it pretty well.

Thanks @BuJo for the explanation - it's good to understand what happens.
So basically to make use of a token based SSO, we have to skip the signing part. It's probably not the best from a security standpoint, at least it works on my machine. I had to edit the code to do so, in the current state an empty UserTokenSigningKey is filled with a random value and I had to disable this step.
From my understanding we have to disable UserTokenSigningKey randomization or - if a skip of signing the token is too dangerous - skip auto login as a whole 🤔 Any opinions from your side, @bolkedebruin?

Not a cryptographer nor security personell, but here is my take:
As there is only a single entity for which the token is encrypted to, there is as far as I can see no need for a signature, as there is only one who can encrypt and decrypt it.  Only in distributed models, where the multiple entities can encrypt the same thing (for example in public-key cryptography) there is a need for signatures to build trust.
It think it's safe to not use the signature.
The out of band connection between rdpgw and pam-jwt seems to me the lynchpin.
The flow of the JWT token:
flowchart LR
  rdpgw --https--> user
  user --> rdp-client
  rdp-client --> xrdp
  xrdp --> xrdp-sesman
  xrdp-sesman --> pam-jwt
  pam-jwt --https--> rdpgw

As long as the encryption key did not leak, TLS v1.3 is used for perfect forward secrecy, the https terminates in rdpgw somewhat directly, the https certificates have not been leaked, or rdpgw/pam-jwt sharing the same Host.. should be safe.


Rework error handling

As comment data is precious, we want to store to retry on any error, and
store to the database if there have been too many attempts.
We should probably raise the exception so that it fails loudly, but the
results are currently chained in a way that'd make that more difficult.
This also sets acks_late on the shared_tasks (rather than using a global
setting) due to the importance of the task. Acks_late will allow a task to be
taken when the original worker process dies (not due to an exception, but
some abrupt failure outside of our process).
For eregs/notice-and-comment#286

Just a minor point that should not hold up this PR - since we are setting acks_late for all the task handlers, why not just set it in the Celery configuration?

It boils down to reusability. These tasks (at least submit comment; I think there's more room for disagreement around publish_tracking_number) require acks_late to function properly. Relying on the shared global configuration increases the likelihood of errors due to misconfiguration but also pollutes the global namespace. Does that seem reasonable?

Once again, thank you for the explanation.


sqlx prepare fails with error "unsupported type NULL of column #2"

I have a query that in my master branch works fine, but when I try to modify the query to add some additional clauses, the sqlx prepare command fails with:
$ cargo sqlx prepare --database-url sqlite://db.sqlite --check
   Compiling squeakroad v0.0.2 (/home/yzernik/work/squeakroad)
error: unsupported type NULL of column #2 ("amount_change_sat")
    --> src/models.rs:2597:39
     |
2597 |           let account_balance_changes = sqlx::query!("
     |  _______________________________________^
2598 | | SELECT * FROM
2599 | | (select orders.seller_user_id as user_id, orders.seller_credit_sat as amount_change_sat, 'received_order' as event_type, orders.public_id...
2600 | | from
...    |
2628 | | OFFSET ?
2629 | | ;", limit, offset)
     | |__________________^
     |
     = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unsupported type NULL of column #3 ("event_type")
    --> src/models.rs:2597:39
     |
2597 |           let account_balance_changes = sqlx::query!("
     |  _______________________________________^
2598 | | SELECT * FROM
2599 | | (select orders.seller_user_id as user_id, orders.seller_credit_sat as amount_change_sat, 'received_order' as event_type, orders.public_id...
2600 | | from
...    |
2628 | | OFFSET ?
2629 | | ;", limit, offset)
     | |__________________^
     |
     = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

This is the query, and this is the pull request that is failing.
Related to https://github.com/launchbadge/sqlx/issues/1350

Thanks for the schema & query, I've added a fix into PR #1960.

I also have a query that fails for this exact error. I can't isolate a minimum example, but this is my project commit:
https://github.com/rongcuid/gqlforum-rs/commit/6b0e97b0ae81aa6574bb8eca0103645f5c7c878c
Hopefully it is not too large. The same query sql/topic_by_id.sql works in SQLite console.

I got the same error also after factoring out the WITH clause into a view. The view's column type seems to be NULL for the post_number column. Maybe this is the issue? SQLite doesn't seem to give types for view columns.

@rongcuid my app is also using SQLite. I wonder if sqlx has more difficulty checking types when the db is SQLite?

@tyrelr I noticed that the prepare command fails for certain queries when I have an empty database.
In my app buyers put ratings on orders. When I run prepare when there are no ratings, it fails:
$ cargo sqlx prepare --database-url sqlite://db.sqlite --check
   Compiling squeakroad v0.0.2 (/home/yzernik/work/squeakroad)
error: unsupported type NULL of column #1 ("weighted_average")
    --> src/models.rs:1959:28
     |
1959 |           let seller_infos = sqlx::query!(
     |  ____________________________^
1960 | |                     "
1961 | |         SELECT weighted_average, total_amount_sold_sat, users.email
1962 | |         FROM
...    |
1991 | |          total_amount_sold_sat DESC
1992 | |             ;")
     | |_______________^
     |
     = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `squeakroad` due to previous error
error: `cargo check` failed with status: exit status: 101

But after I put at least one rating in the database, it works again:
$ cargo sqlx prepare --database-url sqlite://db.sqlite --check
   Compiling squeakroad v0.0.2 (/home/yzernik/work/squeakroad)
    Finished dev [unoptimized + debuginfo] target(s) in 41.98s

That's interesting, @yzernik.
Nothing on the macro side inspects actual data rows within the tables, as far as I'm aware.  Sqlx retrieves the declared table column types, and the query plan, and all calculations are based on those inputs.  Based on that, I wouldn't expect the presence of data within a table to impact the outcome of the check.  But I believe if the non-empty database has statistics, i suppose the query optimizer COULD select a different query plan, and that alternate query plan may be lucky enough to avoid this bug?

I realized that I can use "query" instead of "query!" for the queries where type inference fails as a workaround for now. Is it expected that these queries will work in v0.7?

Just ran into the same sort of error using query! against sqlite with a column that was the result of a join against a common table expression.

I realized that I can use "query" instead of "query!" for the queries where type inference fails as a workaround for now. Is it expected that these queries will work in v0.7?

I was still able to use query! by using a override (https://docs.rs/sqlx/latest/sqlx/macro.query.html#overrides-cheatsheet) on the affected column.

I'm running into the same issue I believe. I have a small reproducible example using SQLite
Here's some relavent info
cargo.toml
sqlx = { version = "0.6.2", features = [ "sqlite", "runtime-actix-native-tls" ]}
actix-web = "4.2.1"

main.rs

#[actix_web::main]
async fn main() -> std::io::Result<()> {
    // .env file with DATABASE_URL=sqlite:sqlite.db
    let pool = SqlitePool::connect("sqlite.db").await.unwrap();

    let mut conn = pool.acquire().await.unwrap();

    sqlx::query!(
        r#"
        CREATE TABLE IF NOT EXISTS Ads (
            company,
            position,
            remote,
            apply_link,
            description,
            paid
        )
    "#
    )
    .execute(&mut conn)
    .await
    .unwrap();

   // insert data here if you wish

    let res = sqlx::query!(r#"select company, position from Ads"#)
        .fetch_all(&pool)
        .await
        .unwrap();
   Ok(())
}

You'll get these errors
error: unsupported type NULL of column #1 ("company")
   --> src/main.rs:123:15
    |
123 |     let res = sqlx::query!(r#"select company, position from Ads"#)
    |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

error: unsupported type NULL of column #2 ("position")
   --> src/main.rs:123:15
    |
123 |     let res = sqlx::query!(r#"select company, position from Ads"#)
    |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)


Migplan validation should check for existence of image registry

Some users have failed migrations due to the fact that there was no internal registry configured on the destination cluster. We should at the very least present a warning condition if we detect no image registry is configured on the destination as it provides a poor user experience.
This can be checked with the following resource:
configs.imageregistry.operator.openshift.io cluster
The ManagementState field should be Managed

As Dylan mentions, this check would be implemented as an additional validation, probably on the MigCluster resource.

@sseago do you recall if the BZ you mention above was ever fixed? If so, could we have a link here?

This was probably fixed in 1.2. I could search for the BZ, but there still might be value in validating ahead of time rather than failing the validation if there are internal images on src and dest is missing the registry.


Does Kitematic require admin rights to pull the container ?

Error pulling image (latest) from docker.io/brandl/tissue_miner, mkdir /mnt/sda1/var/lib/docker/graph/_tmp/866adaba2a181c39a5651e7bf4db4c2ac3d41e8efb787d08831b2cc40f2a4772: read-only file system
Best regards

It looks like your VM may need to be restarted.
Can you close down Kitematic and issue the following: docker-machine restart default

In my case, it was because, does not support the processes that were running when free up memory ran smoothly

Thanks a lot to both of you for your comments. I did it again with admin rights and it worked. But that might not be the good reason... because I restarted the computer (hence the VM) in the meantime. Of note, I'm using an up-to-date MacOSX Yosemite. I haven't tried on Linux yet.


defaultLocale not wokring when getting translations dynamically (weird flicker)

Environment
Nuxi 3.4.3
RootDir: /app
Nuxt project info:

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.4.3
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>                                                                                1:05:29 PM
Builder:          vite
User Config:      app, components, css, postcss, modules, i18n, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://codesandbox.io/p/sandbox/loving-david-ytv9tc?file=%2Fnuxt.config.js%3A26%2C20
Describe the bug
As you can see in the config, I have set the defaultLocale to "el" (Greek) but for some reason "en" (English) gets loaded at first load of the page (no cookies set).
Also (in my project locally) if I explicitly change it to el using the language switcher then when i refresh the page there's a weird flickering happening where firs the translation keys are shown (for like 1 sec) and then the el translations are shown. This doesnt seem to happen in the reproduction link though, on refresh it just goes back to English.
Any help on this would be greatly appreciated
EDIT: Found out that if I change detectBrowserLanguage to false then the defaultlLocale is respected. But still there's a weird flicker when the page loads:
Screencast from 21-06-2023 12:32:06 ΜΜ.webm
Additional context
No response
Logs
No response

I fixed the flickering issue by deleting the node_modules folder and reinstalling them (got the asnwer from https://github.com/nuxt-modules/i18n/issues/1812).
This is kinda weird but ok.
Got a question though (related to the defaultLocale and detectBrowserLanguage):
What if i want to use cookies for my language switching but not detect the browser's language? is that a possibility?
For example I want to have "el" as my default language and when switching to "en" (through a dropdown or something) I want it to be kept in a cookie so as to be persistent when the page refreshes. Kinda like the way it works in detectBrowserLanguage but without the whole browser language detection thing.

You can use useCookieLocale composable.
https://v8.i18n.nuxtjs.org/api/composables#usecookielocale
As notice, set detectBrowserLanguage: false on nuxt config.
This issue has been changed to a question, so we will close.
Thansk!

So how should it be used? I've turned off detectBrowserLanguage and useCookieLocale is returning empty value. (I'm trying to use cookie without detectBrowserLanguage)


Rbac rules auth client provisioning

Added partial import func support to different directories.
Tested with partial and full provisioning (templates and auth clients).

Codecov Report

Merging #157 (5a15983) into 2021.3.x (0589c8e) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##           2021.3.x     #157      +/-   ##
============================================
- Coverage     39.52%   39.51%   -0.02%
============================================
  Files           598      599       +1
  Lines         58757    58781      +24
============================================
+ Hits          23226    23227       +1
- Misses        32791    32814      +23
  Partials       2740     2740

Impacted Files
Coverage Δ

pkg/provision/config.go
0.00% <0.00%> (ø)

pkg/provision/migrations_202103_templates.go
0.00% <ø> (ø)

pkg/provision/partial.go
0.00% <0.00%> (ø)

pkg/handle/handle.go
85.71% <0.00%> (+7.14%)
:arrow_up:

Continue to review full report at Codecov.

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


Separated cohortModules and modules endpoints

#2617  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

There are type changes required in the FE to match these changes.


Rules documentation

I love you guys for implementing this piece of software, but where can I find more details on the rules themselves? I tried reading the source code and your two part article (linked to from ratelimit.io), but I'm still struggling to understand them.
Say for example:
const rules = [
  { interval: 1, limit: 5 },
  { interval: 3600, limit: 1000, precision: 10000 }
]

Is this adding two separate rate limiting counting strategies with the following rules:
Assumptions:

interval is in seconds
limit is number of successful requests
precision is number of tokens/buckets to break up the interval into

rules[0]
For every one second a consumer is permitted 5 requests (count is reset at the top of the second)
rules[1]
For every one hour, there will be 10000 buckets where a consumer will be permitted 1000
requests per bucket (count for each bucket will be reset one hour after the bucket's timeslice)
So basically, by doing new RateLimiter(client, rules) we'd effectively be getting two rate limiters since we have two rules for counting.

After re-reading the Sliding Window in article 2 and the lua source code again I have another take on the interpretation of rules[1]. I believe precision: 10000 is actually an error in the example because in the lua code any value larger than the interval will result in the precision being set to the interval.
https://github.com/dudleycarr/ratelimit.js/blob/master/lua/check_limit.lua#L8-L9
Here's an example to illustrate my new understanding:
Assumptions:

interval is in seconds
limit is number of successful requests per bucket
precision is the duration of a bucket in seconds that will divide the interval (must be <= interval)

Given a rule like: { interval: 3600, limit: 1000, precision: 10 }
Then the rule means: For every one hour there will be 360 buckets (one every 10 seconds), where a consumer can make 1000 requests per bucket (i.e. 10 seconds).


'MAX_DEPTH' was not declared in this scope

hardware: ESP32 Lilygo T-Display
Arduino IDE: 1.8.12
Windows 10
Doing the simple example, and it cannot compile. Error out with:
'MAX_DEPTH' was not declared in this scope

I was able to get passed that error by defining and including all menu related h files and definitions AFTER the declaration of the TFT_eSPI.h input file. But now I get this error:
'TFT_BACKLIGHT_ON' was not declared in this scope
and this variable is normally defined in the TFT_eSPI library


Add BlockRoom settings test cases for userPref

Codecov Report

Merging #246 into master will increase coverage by 0.25%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #246      +/-   ##
============================================
+ Coverage     68.82%   69.07%   +0.25%
- Complexity      705      708       +3
============================================
  Files           114      114
  Lines          2377     2377
  Branches        295      295
============================================
+ Hits           1636     1642       +6
+ Misses          595      589       -6
  Partials        146      146

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/model/UserPrefs.java
71.57% <0.00%> (+6.31%)
25.00% <0.00%> (+3.00%)

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 b8d074e...f363fef. Read the comment docs.


Enhances coverage of config and removes a few redundant code paths.

It looked like my patchy old unit tests could use some enhancements, so that's exactly what I did. This is still rather flat and haphazard though, so if you'd prefer testing of methods in different sub-describes then let me know.

Not sure what the AppVeyor breakage is about.

Coverage increased (+0.2%) to 29.34% when pulling e328ce00f3358cc33406019d6c7548f3e4fc175a on qubyte:config-coverage-enhancements into 216ba936211c2ff65ec5d2b87fe173c289e26827 on mage:master.

0.2%
Really getting stuck into the low hanging fruit. 🤣

By the way... Given that mage is tested on Node 4 and up, what is your policy on supported ES2015 features?

Coverage decreased (-16.6%) to 12.551% when pulling ebb1a8de14abaef8351a78b7ef54cc7116891b89 on qubyte:config-coverage-enhancements into 216ba936211c2ff65ec5d2b87fe173c289e26827 on mage:master.

Coverage increased (+0.2%) to 29.368% when pulling c55bbff12bcc0d744bbb29c4e63d07dc71955025 on qubyte:config-coverage-enhancements into 216ba936211c2ff65ec5d2b87fe173c289e26827 on mage:master.

Coverage increased (+0.2%) to 29.368% when pulling c55bbff12bcc0d744bbb29c4e63d07dc71955025 on qubyte:config-coverage-enhancements into 216ba936211c2ff65ec5d2b87fe173c289e26827 on mage:master.

Coverage increased (+0.2%) to 29.368% when pulling c55bbff12bcc0d744bbb29c4e63d07dc71955025 on qubyte:config-coverage-enhancements into 216ba936211c2ff65ec5d2b87fe173c289e26827 on mage:master.

The Appveyor failure is because you do not have the Appveyor config file  which is in PR #11 right now.

@qubyte Hey, first of all, thanks for contributing, that's really cool :)
With regards to what language features you can use. You may use most language features the lowest common denominator (Node 4) supports (in fact, it's encouraged), which is quite a lot. I do ask in those cases that you mark the files to 'use strict';.
What I do want to discourage is using language features "because we can". The reader of the code comes first, performance comes second, clever trickery comes.. well, it's not on the list ;)

#11 has been merged by the way

I'll rebase on master to fix the appveyor breakage.
Agreed on all counts about usage of features! The reason I ask in this case is because there are a few places which would definitely benefit. For example, this:
var joinKeys = Object.keys(a.value);
var bKeys = Object.keys(b.value);

// Add keys from b.value that were not present in a.value;
for (var i = 0; i < bKeys.length; i++) {
	var bKey = bKeys[i];

	if (joinKeys.indexOf(bKey) === -1) {
		joinKeys.push(bKey);
	}
}

is more succinctly expressed in a Node 4 and above compatible way as:
const aKeys = Object.keys(a.value);
const bKeys = Object.keys(b.value);

// A union of unique keys from a.value and b.value.
const joinKeys = Array.from(new Set(aKeys.concat(bKeys)));

I can open a follow-up PR with suggestions soon.

Coverage increased (+0.2%) to 29.368% when pulling 568d1900914c6bfea897b33ca23772c26bbadcd8 on qubyte:config-coverage-enhancements into f4502b4b82bf8b241ef2079f2756be126a22b7a0 on mage:master.

@qubyte Ah yes, that code is example is rather on the edge for now :) I don't particularly mind that remaining old-style.

I'd go the route of a function to name what's going on there.

Or, given that we don't actually need that to be an array...
function mergeObjects(a, b) {
	const aKeys = Object.keys(a.value);
	const bKeys = Object.keys(b.value);
	const joinKeys = new Set(aKeys.concat(bKeys));
	const returnObj = {};

	// Compare each key-by-key.
	for (const key of joinKeys) {
		returnObj[key] = merge(a.value[key], b.value[key]);
	}

	// Make a new matryoshka with the results.
	return new Matryoshka(returnObj, a.source, true);
}

Ouch, sorry about that.

Don't forget 'use strict' at the top of the file (or your const iteration will break on Node 4)

Superseded by #17


Whereami cache metadata

Made a modification to whereami to cache the GCE instance metadata when the whereami_payload object is created. Previous to this update, each call to whereami would also hit the local metadata endpoint, which added a lot of latency for no tangible benefit (the metadata we're scraping doesn't change for the lifetime of the container). local testing bumped RPS by a factor or 4-8x at same resource consumption.
Tested locally, on Cloud Worktation, on Cloud Run, and on GKE in both HTTP & gRPC modes.
$ grpcurl whereami-grpc-01-b4i6txyukq-uc.a.run.app:443 whereami.Whereami/GetPayload
{
  "pod_name": "localhost",
  "pod_name_emoji": "😴",
  "project_id": "spanner-reporter-01",
  "timestamp": "2023-01-17T19:22:51",
  "zone": "us-central1-1",
  "gce_instance_id": "0071bb48157a2593e287744d134d312f2e099c4dc08daaaed011d052037f2b686f7990cb8d618a55d2873654797323de7def3ca3e4252231eec5ccff3836fee439",
  "gce_service_account"<EMAIL_ADDRESS>}

$ curl <IP_ADDRESS>
{
  "backend_result": {
    "cluster_name": "ap-asm-1",
    "gce_instance_id": "8238644740387196205",
    "gce_service_account": "am-arg-01.svc.id.goog",
    "host_header": "whereami-backend",
    "metadata": "backend",
    "node_name": "gk3-ap-asm-1-nap-kngdrcpt-08300ff7-zvd6",
    "pod_ip": "<IP_ADDRESS>",
    "pod_name": "whereami-backend-6d76d56fbf-kd56g",
    "pod_name_emoji": "🚶🏻",
    "pod_namespace": "default",
    "pod_service_account": "whereami-backend",
    "project_id": "am-arg-01",
    "timestamp": "2023-01-17T19:27:43",
    "zone": "us-central1-b"
  },
  "cluster_name": "ap-asm-1",
  "gce_instance_id": "5514516116051545384",
  "gce_service_account": "am-arg-01.svc.id.goog",
  "host_header": "<IP_ADDRESS>",
  "metadata": "frontend",
  "node_name": "gk3-ap-asm-1-nap-kngdrcpt-1404e0a0-vmxm",
  "pod_ip": "<IP_ADDRESS>",
  "pod_name": "whereami-frontend-7484d594b9-dq7kr",
  "pod_name_emoji": "🫵",
  "pod_namespace": "default",
  "pod_service_account": "whereami-frontend",
  "project_id": "am-arg-01",
  "timestamp": "2023-01-17T19:27:43",
  "zone": "us-central1-a"
}

this looks great! besides a small q, LGTM 👍


[7.x] Fix exit code of down/up commands when already down/up

This will return exit code 0 instead of boolean true. The boolean will be cast to an int resulting in exit code 1, but if the application is already down/up exit code 0 would be desirable.
Change
$ php artisan down
Application is now in maintenance mode.
$ echo $?
0
$ php artisan down
Application is already down.
$ echo $?
- 1
+ 0

$ php artisan up
Application is now live.
$ echo $?
0
$ php artisan up
Application is already up.
$ echo $?
- 1
+ 0

Context
Our deploymenttool (DeployHQ) performs php artisan down before uploading the changes, but stops if this fails. If the deployment fails later in the process - composer install or a migration might fail - our tool stops and the application is still in maintenance mode. If we fix the error and restart the deployment php artisan down now returns an exit code other than 0 and our tool thinks it failed and stops the deployment. This results in a 'locked' state where we have to manually bring the application back up before we can start a new deployment.

Please send to 8.x, since this is a breaking change.

@GrahamCampbell This is partially true, but the down command was changed in #30422 making it a breaking change back then in 6.x. Should I fix the down command in 6.x and fix the up command in 8.x then?

I think it's best to only make the changes on 8.x, and document this in the upgrading guide, so we don't break people's deployments.


Adding Simons Algo tutorial pull request

These are the files for the Simon's Algorithm tutorial I've written, which includes a Q# notebook for the quantum part and a Python notebook for the classical part

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: notanotterpun sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Support CircleCI

Create a file similar to the one for travis that holds variables for circle.

Decide which CI to pick based on environment variables set by them in build.js

@Furizaa this will help.


BUG: Problem in contact form Html code; Feedback and contact  section is removed; Testimonial Images not visible; Website title logo removed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Problem in contact form Html code

Feedback and contact  section is removed

Testimonial Images not visible

Website title logo removed

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me the issue @Its-Aman-Yadav
thank youuu

Sure work on it

I have done it @Its-Aman-Yadav
Please check it
Thanks 🙂


Syntax error

Line 651 has extra semicolon
font-family: var(--font-family-editor); !important;
should be (no semicolon before !important
font-family: var(--font-family-editor) !important;

I didn't notice any any change in how things look but wasn't really paying attention. I was increasing the content width in vscode and vscode flagged the error.


Could the normal images used in the proposed work be uploaded ?

Hello,
I have been admiring the transparency and quality of your work.
However, is there any possibility that you could upload the normal images used in the work as well ? It would have been of much help.
Thank you

Any update on this?
Can you please share the '.npy' for normal and other non-covid images?

@dipayandas97  and @BRim28  did you guys figure out a work around on this?
@armiro can you point me to the normal images?

wait a second, I think he used the images from here: https://www.kaggle.com/paultimothymooney/chest-xray-pneumonia and used the data from chest_xray/test/NORMAL


New version of robotjs on npm

Need for new release version on npm
Expected Behavior
New version of robotJs on npm.
Current Behavior
In the begining of last year were implemented some fixes for mouse scroll issue on windows. On actual version 0.6 it's not implemented and bug still exist.
Possible Solution
Release of a new version on npm 0.6x to pass this fixes to npm
Steps to Reproduce (for bugs)

When we use mouse scroll it doesn't work on windows with version 0.6

Context
I need this scroll to implement in electron project on Windows OS
Your Environment

RobotJS version: 0.6
Operating System: Windows

Maybe you want to give https://github.com/nut-tree/nut.js try. It’s an enhanced framework for desktop automation combining possibilities of robot-js with image matching via OpenCV which provides prebuilt binaries for several node and Electron versions.
It provides a nice API and additional features like highlighting desktop regions or retrieval of window coordinates / dimensions.


CSS Resource Plugin and HMR

Hi Fuse-Box team !
I think there is a little issue between HMR and CSS Resource.
We are creating an app with huge PNG files, and when HMR is triggered, png are cuts in half.
It took me a while to understand why but I think that HMR is triggered before CSS Resource has finished copying files. It works on small files because it's quick enough to be copied before the browser has the refresh trigger.
Another thing, is it possible to avoid CSS Resource copying resources each time we build ? Maybe it can check filesize or so to avoid useless copies.
Thanks for your help !

Hello ! I'm finally back with a solution with this issue.
I'm working on a fork of CSSResourcePlugin.
The copyFile function is asynchronous and, the Promise is not listened by the transform method, which allow Fuse to refresh the page without resources copied entirely when having huge resources.
This is how I patched it, sync file copying. Not great because it's blocking the main thread but it seems to be working :
const copyFile = (source, target) =>
{
	if (!fs.existsSync(source)) return;
	ensureDir(path.dirname(target));
	fs.copyFileSync(source, target);
};


TabsTitleControl.layout slows down startup

Extracted from https://github.com/Microsoft/vscode/issues/34745#issuecomment-341472944

Closing as per https://github.com/Microsoft/vscode/issues/34745#issuecomment-344556393


Improve UI of Visitor count

Describe the feature
The visitor count thing looks very plain and normal, I can make it more beautiful and appealing with glassmorphism n also give some better shape like circle rather than plain rectangle and some beautiful hover effect. Kindly assign this issue to me. PS: I love working with UI and can make your website more beautiful
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@anuragverma108 @huamanraj @RitiChandak @RishabhDhawad Kindly assign this to me


Modify CloseExport() test to NOT expect idempotence with already-closed handle.

CloseExport() test had "todo" comment and missing failure expectation when closing an export with an export handle that had already been closed (i.e.: an invalid handle)

Completed


Virtual Console Solo Frame give a delay when playing Audio

Describe the bug
Starting songs in a solo frame have a delay if another one was playing.
To Reproduce

Add 2 songs or more in Functions
Add 2 buttons in a Solo Frame in Virtual Console
Attach each song to theses buttons
Click the first button to start the song attached with no delay, but clicking the other button while the previous song is active have a small delay (and all subsequent presses while a song is active)

Expected behavior
No delay should be present.
The bug is not present in a normal Frame.
Workaround
If I add a small Fade-out time (even 1ms) to the songs, there's no delay.
Desktop

OS: Windows 11
QLC+ Version 4.13.1
Laptop speakers

Please build QLC+ with Qt 6.8.x and try and see if the delay is still there

I have loaded a test version here
https://www.qlcplus.org/downloads/test/index.php?p=Windows
Please test and report if it solves the issue, thanks

Improved results.
Where v4.13.1 measured a 378ms gap (mp3 vs 368ms with flac), the responsiveness with QT6 is improved.
Playing audio in a solo frame has an improved gap measurement of 29ms for mp3 and 29ms for flac. Great!
test-tones.zip
Observation: The qt5 however, showed a 'nice' 11ms fade out, where qt6 cuts the audio stream directly.
Observation 2: (bug) double-clicking a button, renders QLC+ (both versions) in an unresponsive state and even crashes.
*test environment: A 2 mp3 files, 2 flac files - a project with 2 buttons in a solo frame. v4.13.1 and v4.13.2 GIT


Opt-out of PyCell

Like we have #[pyclass(unsendable)] to opt-out of Send, many users will not want their pyclass to be mutable. It would be nice if we could allow them to opt-out of having PyCell as the backend, so that they don't have to deal with the performance cost.

Perhaps this opt-out could be #[pyclass(immutable)] ?
Though TBH I think I prefer immutable-by-default, so perhaps we should have #[pyclass(mutable)] to opt-in to PyCell!

Could we couch this in terms of exclusive and non-exclusive access rather than mutability?

First step of this in #1979 has now been merged. A future refinement will be to make mutability (and accompanying overhead) opt-in.

I'm going to close this in favour of #4369, which I believe we plan to do soon as part of the improvements targeting freethreading.


Identify extended base state

I have a core component, it has ellipsis state.
I extend this stylesheet, and it is displayed as an unknown pseudo-state.
Everything works great, just see this warning

@lbelinsk Is this still happening? We were not reproduce it


chore: bdd-nh-1589810420 to 0.0.1

chore: Promote bdd-nh-1589810420 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


CVE-2022-42004: Bump version for "jackson-databind" plugin

https://github.com/advisories/GHSA-rgv9-q543-rqg4
Expected Behavior
jackson-databind installs the jackson-databind-2.13.4.jar plugin. The plugin version should be >= 1.15.3 to patch the vulnerability.
Current Behavior

gradle v7.6 installs the jackson-databind-2.13.3.jar plugin. According to https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42004, the vulnerability is patched in jackson-databind-2.13.4.jar.

Thank you for reporting this issue.
The issue is in the backlog of the relevant team but it might take a while before a fix is made.

This was actually fixed with Gradle 8.0 already


plotly figures not showing online

From @dotis: The plotly plots on the EFGB page render ok from RStudio, but show up blank when using the URL.

I suspect necessary JS files were not all pushed to website, per these missing files from the JavaScript Console on Google Chrome:


Commissioning with iOS chiptool fails due to  CHIP Error 0x0000002F: Invalid argument

Problem
Commissioning with iOS chiptool fails due to - CHIP Error 0x0000002F: Invalid argument
SHA: 4279b678c16453b332d8e3108098b678a2940df6

Build iOS chiptool
Build M5 board with iOS chiptool
Try to pair with iOS chiptool - it fails with:
2022-03-09 19:39:28.998384-0800  localhost CHIPTool[9143]: (CHIP) DevicePairingDelegate Commissioning complete. NodeId 1 Status ../../../../../../../../../../../connectedhomeip/src/controller/AutoCommissioner.cpp:159: CHIP Error 0x0000002F: Invalid argument

pairing-fail-change-setup-discriminator-chiptool-logs.txt
commisioning-fails-change-setup-discriminator.txt

Added another set of logs using default discriminator
failed-to-pair-invalid-argument-M5-logs.txt
failed-pairing-invalid-argument-chiptool-log.txt

Build M5 board with iOS chiptool

I assume that's with all-clusters-app?

Yes all clusters app

The PairDevice call for setup codes where the device is discovered first over BLE was inconsistent with the rest of the PairDevice calls such that if you discovered a device over BLE you would establish a pase session only, whereas if you discovered it over mdns first you would get a full commissioning. This was a race condition on the behaviour.
If you want to just establish PASE, there was a new call added that will do that - EstablishPASEConnection with a setup code.
Does this happen in the iOS chip tool? If so, I can prepare a patch to update, but I don't have a good way to test this as it's not in the CI and I don't have a way to test.

@cecille So I am at a loss as to how this is supposed to work now.  The way it used to work was:

We would call PairDevice with a code.
If the device was discovered on-network, it would get commissioned.
If the device was discovered via BLE we would establish PASE and call back into the "pairing complete" bits to allow the consumer to get network info and call Commission.

In the new setup, if I call PairDevice that will try to commission and fail out.
If I call EstablishPASEConnection, that works for the BLE case, but now the on-network case is broken: we get the "pairing complete" callback, but there is no way to tell that network info does not need to be provided in this case, so we end up trying to provide it, which is not the desired flow here.
Given the current API surface, how do we get the behavior that we want, exactly?

Does this happen in the iOS chip tool?

Yes, exactly.


Host Storage Folders are reordering

v1.2.0-RC1, Win 10
If you have more than one host storage folders configured you will see that they are changing their order in the list all the time (every couple of seconds). That is really disturbing to look at in the UI as well.

and a couple of seconds later...

They get returned from a map I think. So siac should probably sort by name


Update vim_configurable to vim 8.0005

Motivation for this change
fix #18800
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Can't we just use the src from the regular vim expression? Otherwise this will diverge eventually

I was wondering the same thing, this should probably use the vim drv as a starting point.

I was wondering if vim should just be derived from vim_configurable as
vim_configurable is more general? But, I thought this was the simplest
thing for now as they've been using different versions for awhile.
On Wed, Sep 21, 2016, 5:55 AM Alexander Ried<EMAIL_ADDRESS>wrote:

@groxxda approved this pull request.
Using vim.src is probably not worth the effort since vim needs
refactoring anyway ( #18763
https://github.com/NixOS/nixpkgs/issues/18763 )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/18801#pullrequestreview-944139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-hHJ_3odLjyYi2XpG5A0FBu7Ux6oM8ks5qsSk7gaJpZM4KCRjs
.

This breaks the darwin build, the python patch does not apply.

@LnL7, when you say "the python patch doesn't apply", what python patch? How can I reproduce the problem? (Note: I'm a newbie so pardon my ignorance).

@winksaville You can remove the optional call to always apply the patch, I can take a look if you can't figure it out but I'm not sure if I'll have time today.
https://github.com/winksaville/nixpkgs/blob/08d7cfa4203dd5adc8b98979ab085a8a100c3f34/pkgs/applications/editors/vim/configurable.nix#L76

@LnL7 are you saying we never want to apply the patch or we always want to apply the patch?
Is this a problem with vim 8.005 only or with other builds too? For instance I noticed that vim/configurable.nix was using 7.4.826 where as previously vim/default.nix was using 7.4.1585.
Also, note the odd logic in line 75 with the 'or true':
(stdenv.isDarwin && (config.vim.darwin or true))
I currently don't have a darwin environment setup so I'm unable to test.

@winksaville I suspect the vim package does not need that patch because it does not have python support

@winksaville the attr.path or true is common. It is there because config might not have a vim attribute, or if it has, that vim attribute set might not have a darwin attribute. Accessing an invalid key will yield an error, but the or true will "catch" the error and return true instead:
nix-repl> config = { vim = { linux = true; }; }

nix-repl> config.vim.darwin
error: attribute ‘darwin’ missing, at (string):1:1

nix-repl> config.vim.darwin or true
true

@LnL7 was suggesting you remove the optional so when you build vim the patch gets applied.
Another option would be to get the source manually and apply the patch. Or with help of nix:
 ~/nixpkgs nix-shell . -A vim_configurable

[nix-shell:~/nixpkgs]$ cd /tmp

[nix-shell:/tmp]$ unpackPhase
unpacking source archive /nix/store/yhz9549411wsyfp5anxlclgcb266xvva-vim-v7.4.826-src
source root is vim-v7.4.826-src

[nix-shell:/tmp]$ cd vim-v7.4.826-src/

[nix-shell:/tmp/vim-v7.4.826-src]$ $prePatch

[nix-shell:/tmp/vim-v7.4.826-src/src]$ patch < ~/nixpkgs/pkgs/applications/editors/vim/python_framework.patch
patching file configure
[...]

This will most probably fail and you can inspect further. Interestingly the patch did not apply for me with the old vim version either...

@groxxda, but doen't (config.vim.darwin or true) always evaluate to true and would therefore appear to me to be unnecessary. And regarding removing optional that's trivial but doing much beyond that is going to get me into trouble with you guys.
@LnL7, python can support python as an interpreter although I've never used it, see here and here for instance. So I'm guessing if you install vim using nix is that vim should use nix's version of python not some random version installed on the platform. But as I said, I'm just guessing.

@winksaville i admit this is not intuitive because the or is quite different from the logic ||:
nix-repl> { x = false; }.x or true
false

nix-repl> { x = false; }.x or false
false

nix-repl> { x = false; }.y or true
true

nix-repl> { x = false; }.y or false
false

while the logic || yields:
nix-repl> { x = false; }.y || true
error: attribute ‘y’ missing, at (string):1:1

nix-repl> { x = false; }.y || false
error: attribute ‘y’ missing, at (string):1:1

The proposal was only to remove it to test the patch locally and fix the patch. Of cource you should not commit the removed optional :wink:

@groxxda, I think I understand or, I see from here its a set operator that defines a default if the Set on the LHS yields an "empty" result or an "error", please correct me if I'm wrong.
@LnL7 please test and let me know if you'd like me to do anything else or if it needs a more sophisticated change I can certainly close this pull request and a proper one can be supplied.

@winksaville The patch is no longer needed for this version as far as I can tell, you can remove the python_framework.patch file and the patches attribute.

OK
On Thu, Sep 22, 2016, 12:20 PM Daiderd Jordan<EMAIL_ADDRESS>wrote:

@winksaville https://github.com/winksaville The patch is no longer
needed for this version as far as I can tell, you can remove the
python_framework.patch file and the patches attribute.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/18801#issuecomment-249002137, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA-hHH9Uhz0QwaAxn79Eqrri2-gaCSVYks5qstUOgaJpZM4KCRjs
.

@LnL7 I've updated the pull request to remove python_framework.patch.
If a user 'manually' changed version to 7.4.826 or some other earlier version, would vim no longer 'work' on darwin? If so should we instead conditionally apply python_framework.patch?

While you indeed can override the version, this is not something we account for in nixpkgs.
In some cases we do keep multiple versions around, but only if there's a reason for that.


test

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes
Replace me
Replace me
Replace me

Breaking Changes
Replace me
Replace me

Testing Evidence
Please provide any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
As part of this Pull Request I have
Checked for duplicate Pull Requests
Associated it with relevant issues, for tracking and closure.
Ensured my code/branch is up-to-date with the latest changes in the main branch
Performed testing and provided evidence.
Updated relevant and associated documentation.

This was a test, please ignore.


 Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:warning: Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
:recycle: Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: php/tests/vaas/composer.lock
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/builds/no-one-common/renovate-github/renovate/repos/github/GDATASoftwareAG/vaas":"/builds/no-one-common/renovate-github/renovate/repos/github/GDATASoftwareAG/vaas" -v "/builds/no-one-common/renovate-github/renovate/cache":"/builds/no-one-common/renovate-github/renovate/cache" -e COMPOSER_CACHE_DIR -e COMPOSER_AUTH -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/builds/no-one-common/renovate-github/renovate/repos/github/GDATASoftwareAG/vaas/php/tests/vaas" docker.io/renovate/sidecar bash -l -c "install-tool php 8.2.3 && install-tool composer 2.5.4 && composer update phpunit/phpunit --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins"
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires phpunit/phpunit ^10, found phpunit/phpunit[10.0.0, ..., 10.0.15] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - phpspec/prophecy-phpunit is locked to version v2.0.1 and an update of this package was not requested.
    - phpspec/prophecy-phpunit v2.0.1 requires phpunit/phpunit ^9.1 -> found phpunit/phpunit[9.1.0, ..., 9.6.5] but it conflicts with your root composer.json require (^10).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Not mergable until prophecy-phpunit supports phpunit 10.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 10.x releases. However, if you upgrade to 10.x manually then Renovate will reenable minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


WordPress.Security.ValidatedSanitizedInput.MissingUnslash does not accept stripslashes()

This is weird, but WordPress.Security.ValidatedSanitizedInput.MissingUnslash sniff accepts only stripslashes_deep (type-ignorant) or stripslashes_from_strings_only (type-ignorant) and does not accept the plain type-strict stripslashes.

but what if the type is not an array?


show core token balances (including liquid core token balance) in cleos get account

Resolves #4066.
Example outputs:
$ programs/cleos/cleos get account alice
permissions:
     owner     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
        active     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
memory:
     quota:     5.971 KiB    used:     4.158 KiB

net bandwidth:
     staked:          5.0000 SYS           (total stake delegated from account to self)
     delegated:      13.0000 SYS           (total staked delegated to account from others)
     used:               157 bytes
     available:        41.47 MiB
     limit:            41.47 MiB

cpu bandwidth:
     staked:          5.0000 SYS           (total stake delegated from account to self)
     delegated:       0.0000 SYS           (total staked delegated to account from others)
     used:             1.619 ms
     available:        2.302 sec
     limit:            2.304 sec

SYS balances:
     liquid:         4960.0000 SYS
     staked:           10.0000 SYS
     unstaking:         0.0000 SYS
     total:          4970.0000 SYS

producers:     <not voted>

and
$ programs/cleos/cleos get account eosio
privileged: true
permissions:
     owner     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
        active     1:    1 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
memory:
     quota:     324.4 MiB    used:     1.113 MiB

net bandwidth:
     staked:   74999999.5000 SYS           (total stake delegated from account to self)
     delegated:       0.0000 SYS           (total staked delegated to account from others)
     used:             10.33 KiB
     available:        164.8 TiB
     limit:            164.8 TiB

cpu bandwidth:
     staked:   74999997.5000 SYS           (total stake delegated from account to self)
     delegated:       0.0000 SYS           (total staked delegated to account from others)
     used:             499.2 ms
     available:         9600 hr
     limit:             9600 hr

unstaking tokens:
     time of unstake request:  2018-06-12T22:08:15 (funds will be available in 50.39 hr)
     from net bandwidth:              0.0000 SYS
     from cpu bandwidth:              2.5000 SYS
     total:                           2.5000 SYS

SYS balances:
     liquid:    849989947.2914 SYS
     staked:    149999997.0000 SYS
     unstaking:         2.5000 SYS
     total:     999989946.7914 SYS

producers:
     eosio

v1.0.3 cleos should still be able to work as it used to with a chain_plugin version running with these changes.
A cleos version with these changes should still be able to work (granted without displaying the core token balances) with a v1.0.3 chain_plugin.
However, these changes do technically change the JSON structure of get_account_results. In particular, a new optional field core_liquid_balance is added in.

I just built from master after this merge. Should I be seeing this new core_liquid_balance field in the get_account rpc result (I don't)?

@okayplanet: Only if you are connecting to an API node also compiled with these changes. If you are just using cleos to connect to existing v1.0.3 public API nodes, then you won't see the new fields (at least not until those nodes upgrade to the upcoming v1.0.4 release).

@arhag I am using my own node.  I pulled latest on two boxes, and reran the ./eosio_build.sh and the results still are not there.  Are there some cached folders I need to blow away by chance, before building?

@okayplanet you should check if your system symbol is 'EOS' if you are using mainnet


Please add support for coffee2 files!

Good idea. I think this should be simply configurable. Is .coffee2 somewhat standardized or is it just you? If the former, then I'll add it to the default extensions

More concretely, I think that this must be doable without an extension config option, by setting vscode setting
"files.associations": {
  "*.coffee2": "coffeescript"

and CoffeeSense should respect that setting. It does not, currently. However for LSP usage outside of VSCode, there still needs to be an extension option either way.

Hmm, it's a convention we're using to be able to support both compilers as we haven't migrated fully. Not sure if it's standardized. We do have that file association set up in VSCode, but that doesn't work - get a bunch of red squigglys in the coffee2 files.

This is now possible with version 1.3.0 (you need to check that VSCode updated the extension, it usually takes two reloads for that). Check setup.md - can you test this out and tell me if it now works as desired?

Awesome, works now, thank you so much!! 🎉


chore: switching from ora to cli-core spinner

Description of changes
Extension of a contributor's PR #12175

Issue #, if available

Description of how you validated changes
Checklist

[x PR description included
[x] yarn test passes
[x] Tests are changed or added
[n/a] Relevant documentation is changed or added (and PR referenced)
[n/a] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[n/a] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

some tests are failing but they are not related to the changes.

LGTM


metrics: now support TOML files

Companion to https://github.com/iterative/dvc/pull/7965

Thanks @alexmojaki !


Posthog event logging updates

What kind of change does this PR introduce?
This PR adds a version number of the openadapt build to posthog events, so its easier to debug the source of erroneous events. It also adds a fix so that submenus in the tray, that have the name of the recording are not reported, rather the underlying action is reported

Summary
Address #768

Checklist

[x] My code follows the style guidelines of OpenAdapt
[x] I have performed a self-review of my code
[ ] If applicable, I have added tests to prove my fix is functional/effective
[x] I have linted my code locally prior to submission
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
[x] New and existing unit tests pass locally with my changes

How can your code be run and tested?
In utils.py, comment out the lines that disable posthog in the get_posthog_instance function. I have added a property to psothog events that will differentiate dev events from events coming from the app, so this can be used when we need to test without polluting the events charts. Play around with the tray (also the submenus) and check that the events are logged correctly

@KIRA009 can you please fix merge conflicts? I believe we should pass in recording to get_perf_stats


Method override does not work correctly with "crocks" library

Steps to reproduce:
const Arrow = require("crocks/Arrow");

class K extends classes(Arrow, Object) {
  compose(...args) {
    console.log("THIS WILL NOT RUN");
    return super.compose(...args);
  }
}

const k = new K([x => x]);
const l = new K([x => x]);
k.compose(l);  // returns an instance of Arrow but no console.log

This thing is that crocks defines a new compose method on each instance of Arrow, rather than defining a single compose method for all Arrows.
This is not an issue in Polytype, it's intended that you can define a method on a specific object and that would take precedence over methods defined in a base class.
To get what you want you could probably hook yourself in the constructor and overwrite the compose method with your own version.
class K extends classes(Arrow, Object) {
  constructor (arrowArgs) {
    super(arrowArgs);
    const originalCompose = this.compose;
    this.compose = function (...args) {
      console.log("THIS WILL NOT RUN");
      return originalCompose.apply(this, args);
    }
  }
}

Note that there is no point in calling super.compose in your class because there is no compose method in any superclass, it's all on the current object.

Ah, that makes sense. Yes, that is the workaround I am currently using. I love crocks but I am guessing that to fix this, one would have to rewrite most of the constructor functions. Anyway, thank you @fasttime ; closing this issue for now.


Custom params in StackNavigator route config

Hello, it's possible to inject custom params in StackNavigator config?
For example:
const Navigator = StackNavigator({
  Registration: {
  	screen: Application,
  	content: Registration,
  },
  Login: {
  	screen: Application,
  	content: Login,
  },
});

class Application extends Component
{
    render() {
        return this.props.navigation.content;
    }
}

You might want to look into screen props.

Since this issue looks like a question, I'm going to close it. Please do not take this personally :). We are referring those who ask questions to Stack Overflow or the #react-navigation channel on Reactiflux.


[FN] Fix for unconfirmed transactions getting stuck in wallet db

This relates to the issue when we send lots of cross-chain transactions of the same value from mainnet node to sidechain and some of the transaction duplicates getting stuck in wallet database.
We sent 201 transactions, sidechain wallet received 201 confirmed ones plus had 28 unconfirmed stuck in wallet database, even though these unconfirmed ones were removed from the mempool.
Upon investigation, wallet manager tx removal code was narrowed down as an issue. The for loop has a rather strange logic in it for handling double spends.
This logic needs to be carefully reviewed as it seems to be buggy.

Any possibility of implementing a test for this guy @fenix2222 ?
Can you explain the scenario that you think is happening, the order of events, so that we can test it?

Any possibility of implementing a test for this guy @fenix2222 ?
Can you explain the scenario that you think is happening, the order of events, so that we can test it?

There is already a test for it, but I will see if I can add another one to test the exception case.
With the current code (for loop) there could be a number of issues.
Let's say first transaction in address.Transactions list (i.e. i = 0) matches idsToRemove. We remove it and decrement i by 1. Now we already created an issue as i = -1 and if we get to the next if statement and try to access address.Transactions.ElementAt(i) it will throw an exception. We are also reassigning array instead of just deleting the item address.Transactions = address.Transactions.Except(new[] { transaction }).ToList();. If we deleted transaction, we shouldn't need to check if it had matching spend outputs.
The second problem, let's say our transaction is unconfirmed, its id doesn't match idsToRemove but it has matching unconfirmed spenddetails, we should remove this tx instead of making spenddetails null.

@zeptin Can you check this PR?

Closing for now until we experience this issue again.


Pass additional config to react-syntax-highlighter (e.g. showLineNumbers)

Currently, the user can set the syntax highlighting theme and the supported languages in their theme.  However, they cannot pass any of the many other props that react-syntax-highlighter accepts.  Several of these seem like they might be too complex to usefully pass in from a theme, but a few look like they'd be useful.
In particular showLineNumbers, startingLineNumber, lineNumberContainerStyle, and wrapLines all seem like they would be useful.  Would it make sense to pass them in?
If so, I'd be happy to submit a PR to add that functionality.
I've already modified the relevant code in mdx/src/Code.js for my local copy (I really wanted line numbers!) so it wouldn't be much effort to summit a PR if you think the feature would be more broadly useful.

With the changes in v2, you can now supply your own syntax highlighting component with a theme, which should let you specify any props you'd like for react-syntax-highlighter and also install newer versions of the library. Here's an example of what adding syntax highlighting to a theme now looks like: https://github.com/jxnblk/mdx-deck/blob/master/packages/themes/src/syntax-highlighter.js


fix: add alby offset workaround

Not doing any functional changes on nwc.getalby.com, it's now deprecated


Use basename implementation from glib-2.0

This is portable across various platforms and system C libraries e.g. basename differs between glibc and musl, where glibc provides a GNU implementation and POSIX version, and musl provides posix version only and Newer version of musl have removed prototype for basename in string.h [1] which caused build failures with gcc-14 on musl systems.
g_path_get_basename() is implemented in glib-2.0 and is portable across these systems. It allocates a new string for the returned value which should be free'd by user, however, all our usecases here are in main() functions, so technically we are not going to leak any memory.
[1] https://git.musl-libc.org/cgit/musl/commit/?id=725e17ed6dff4d0cd22487bb64470881e86a92e7

Could you please verify whether simple solution like that will work: https://github.com/arkq/bluez-alsa/tree/basename ?
If possible I would like to avoid pulling in glib-2.0 dependency on bluealsa clients.

Could you please verify whether simple solution like that will work: https://github.com/arkq/bluez-alsa/tree/basename ?
If possible I would like to avoid pulling in glib-2.0 dependency on bluealsa clients.

yes that works too, although posix basename does not guarantee that input string will be unmodified. Thats the reason why I was trying to use something thats compatible with GNU basename implementation because unknowingly lot of software on linux assumes glibc and hence GNU implementation.

although posix basename does not guarantee that input string will be unmodified

With the bluez-alsa usage of basename it's guaranteed that the argument will not be modified.
Many thanks for reporting the issue!


Bug Report

While starting project, these bugs are encountered

this is not a bug actually you forgot to add the .env file with relevant environment variables.

this is not a bug actually you forgot to add the .env file with relevant environment variables. one of them is for connecting with db that causing a mongoose error.

@prajjwalarora Thanks for helping her, I like your open-source spirit!
@shrishti-c If you are still having issues, do add a couple more screenshots so that I can review. The whole error message is still not visible.

/reviewed

/close-issue/

This is not an error as said by @prajjwalarora. Besides adding environment variables, you need to start MongoDB in a new cmd tab.


[BUG] Scene action won't execute write mode user procedure when other parts are all readonly

MATCH (q:Message {role: 'user'}) WHERE id(q) in $nodes

CALL chat.ask(q, 'gpt-3.5-turbo') YIELD ans, r

// Bloom don't honor `chat.ask` as being WRITE mode,
// we have to put some write ops in this scene action,
// or nothing will happen. Guess Bloom runs it with a
// readonly tx, then fails silently.
MERGE (ans)-[r1:CONTINUES]->(q)

RETURN ans, r1

I guess the box showing

This query manipulates data. All changes will be executed within the selected search timeout, although only the specified maximum number of unique nodes will be displayed.

indicates whether  bloom will execute this scene action with a writable tx, without detected it "manipulates data", Bloom won't show this box, and the scene action will silently do nothing, even with no error reporting at all.

My procedure is indeed marked as writing mode:
  @Procedure(name = "chat.ask", mode = Mode.WRITE)

So I consider this a bug.

Also if I mistakenly marked my procedure as readonly, and it does writes in execution, I suggest Bloom do report the incident clearly.

Hello @complyue!
Thank for opening the issue, Bloom usually detect if the query is a Write or Read query based on presence/absence of any "SET" clause, this is not a comprehensive way of detecting it but it works most of the times when the users are not using stored procedures.
In case of store procedures there is a way to enforce a WRITE transaction for Search Phrases and Scene Actions:

In the "Setting" panel enable the "Experimental" section
Open the "Experimental" panel and you will find a toggle "Allow write transactions"

Now when you add a new Scene Action or Search Phrase a new checkbox allows you to force the "WRITE" transaction when executing your query

I see that you're using ChatGPT with bloom, that's great! If you're interested around this topic you might found useful APOC Extended https://neo4j.com/labs/apoc/5/ml/openai/ and several blog post around how to use text to cypher for querying your KG
Hope this helps!


Fetch operator schema from the database

###Description of the Tech Debt###
Currently the operator form is getting the form schemas it needs from the frontend (from app/data/jsonSchemaForm/). We need to switch these to be fetching the schemas from the database so that we are only maintaining it in one place.
The following steps need to be taken for both, and all but the first and last steps here need to be done for both the form, and the form summary components.

[x] ensure the schema in the database is up to date
[x] remove andy anyOf / default from the database schema
[x] add a query to the component fetching the jsonSchemas by their slug
[x] switch the form to use the schema in the above query response
[ ] switch the import in the components test to point to the schema in schema/data/prod/json_schema/
[ ] remove the schema from the frontend directory we were importing from before
[ ] remove the frontend schema import from validationSchema and add the new schema name to app/server/middleware/graphql/databaseSchemaConfiguration.ts so the validation plugin can find the correct schema

###Tech Debt Triage#
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring: 1 / 2  (the risk increases if we add/remove fields from, or start versioning the schema)

Level
Value

High
3

Medium
2

Low
1

Technical Debt - Risk Types
Level
Value

Business Area Risk - Risk of business area visibility / damage to user experience

Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it

System Fault Risk - Risk of system errors or application downtime

Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?

Time Sink Risk - How much will this tech debt slow the development process down

TOTAL SCORE:

Thank you @gurjmatharu! Not much to test here, but I can see the code getting the schema from the db


Upgrade dependency for yargs-parser to reduce security risk

Upgrade yargs-parser to latest version to reduce security risk.
Current version (10.1.0) has vulns including  Improper Input Validation in yargs-parser
Latest version is 18.1.3: https://www.npmjs.com/package/yargs-parser

Looks like we've got four different versions of yargs-parser installed: 18.1.3, 9.0.2, 10.1.0, 13.1.2.


Copy to clipboard fails silently on Firefox

Firefox implemented support for ClipboardItem about a year ago (see https://bugzilla.mozilla.org/show_bug.cgi?id=1619947), but they still don't have it activated by default.

Unless the user manually sets dom.events.asyncClipboard.clipboardItem in about:config, clicking the copy button in the app will throw a ReferenceError: ClipboardItem is not defined that is unhandled.
I would suggest adding a .catch() handler in the promise resolved at https://github.com/stevebauman/showcode/blob/32a4b902e27be472dd2e8337d470e77294a6092b/components/Preview.vue#L730, and/or to disable the copy button altogether (and probably showing a helpful message on how you can activate the feature) if typeof ClipboardItem === 'undefined'.
I would do a PR for it myself, but I don't want to mess around in your code without knowing how you would want that handled.

Thanks for letting me know @lupinitylabs. Do you know if document.execCommand("copy") would work in Firefox for images?

No, I'm afraid document.execCommand("copy") does not seem to do anything on images. It works for text, but that's about it.

Dang, so I guess our only solution is to disable the button or show a message upon clicking copy like you mentioned?

Yes, that's also how Carbon seems to do it. With the config key set to false, they don't show the copy image menu item, when it's true, it shows.
It's a little frustrating that it takes Mozilla years to adopt web standards, and when they do, they don't activate them by default.

I would favor a solution where a message is shown that explains why copy isn't available over silently hiding or disabling the button, because it's not transparent for users why this feature would be missing or disabled.


Auth / Safety Check for access to Firebase

look e.g. here:

https://firebase.google.com/docs/database/security/get-started?authuser=0

https://firebase.google.com/docs/app-check?authuser=0&hl=de

https://developer.android.com/training/safetynet/attestation?hl=de&authuser=0

Firestore access rules

Done like this:
https://firebase.google.com/docs/auth/android/anonymous-auth#java_3


ERROR WHILE TESTING ON A LOCAL VIDEO FILE

While testing on a local video file. I came across this error
"""
double free or corruption (!prev)
Aborted (core dumped)
"""
command used : python3 darknet_video.py --input videos/case1.mp4 --out_filename videos_output/case1.avi --weights ./backup/yolov4-crowdhuman-608x608_final.weights --dont_show --ext_output --config_file ./cfg/yolov4-crowdhuman-608x608.cfg --data_file ../data/crowdhuman-608x608.data --thresh 0.25
I double checked every parameter. weights are loaded properly.
[yolo] params: iou loss: ciou (4), iou_norm: 0.07, obj_norm: 1.00, cls_norm: 1.00, delta_norm: 1.00, scale_x_y: 1.05
nms_kind: greedynms (1), beta = 0.600000
Total BFLOPS 127.248
avg_outputs = 1046494
Allocate additional workspace_size = 52.43 MB
Try to load weights: ./backup/yolov4-crowdhuman-608x608_final.weights
Loading weights from ./backup/yolov4-crowdhuman-608x608_final.weights...
seen 64, trained: 384 K-images (6 Kilo-batches_64)
Done! Loaded 162 layers from weights-file
Loaded - names_list: data/crowdhuman.names, classes = 2
videos/case1.mp4
FPS: 4
Objects:
person: 50.31%    (left_x: 250   top_y:  59   width:   7   height:  33)
person: 88.72%    (left_x: 259   top_y:  60   width:   9   height:  34)
FPS: 26
Objects:
person: 49.94%    (left_x: 250   top_y:  59   width:   7   height:  33)
person: 88.43%    (left_x: 259   top_y:  60   width:   9   height:  34)
double free or corruption (!prev)
Aborted (core dumped)
How to solve this issue?

I myself have never used "darknet_video.py".  Have you tried the "darknet" executable instead?

darknet executable is working good enough. But can't save the video output using executable. we can see the output that detection is happening, but can't see the output video.

I think you could report the issue to the maintainer of "darknet_video.py".


sql error on start of new lxd

2015/05/08 14:17:26 DbQuery: query "SELECT max(version) FROM schema" error "sql: Scan error on column index 0: converting string "" to a int: strconv.ParseInt: parsing "": invalid syntax"

Note that this doesn't seem to cause any problems, it just looks ugly :)

Well, that's only a Debug output (Debugf()), I'm not sure it needs any action.
We specifically swallow errors like this there (https://github.com/lxc/lxd/blob/master/shared/db.go#L169), and the upper-layer code relies on this behaviour already (since we return nil, err).

Fair enough. I'll close this and hope that #482 will improve things a bit.


driver: uart: npcx: fix deadlock of writing UFTCTL register

In order to avoid a concurrency situation during writing UFTCTL register,
this CL adds critical sections to prevent the unexpected result if the
driver wants to set/clear bits of this register.
Once it passed the verification on the platforms, we will submit it officially for code review.
Signed-off-by: Mulin Chao<EMAIL_ADDRESS>Signed-off-by: Jun Lin<EMAIL_ADDRESS>

Tested 2000 reboot cycles and it didn't deadlock at all (where it could reliably deadlock in fewer than 100 cycles before), so LGTM.

Tested 2000 reboot cycles and it didn't deadlock at all (where it could reliably deadlock in fewer than 100 cycles before), so LGTM.

Thanks for testing this PR on platforms. So far, we have only duplicated the deadlock symptom on our evb. It's very valuable information for us.

Update validation progress on Nuvoton's side. We have duplicated the symptom on platforms successfully. After applying this PR, the symptom is gone over 500 iterations currently.


Will Yarp bindings and iCub bindings for python change the previous functions and complied project?

Recently, I want to try to use python to control the physical iCub names iCubOsaka01.
But I found that in the current version in our lab's PCs, there are no Yarp bindings and iCub bindings.
So I want to install it.
While installing the Yarp bindings and iCub bindings, will these affect the existing demos like Emotion_Demo, Green_Ball, etc. ?
Just referring to the tutorial link, is it enough? Do I have other stuff to notice?

Hi @YANGGANG1971
Bindings go alongside the standard build products, thus if you compile bindings you won't overwrite your current builds.


Runner name deprecation + deprecate 'misc-flasher' to prefer 'misc'

An alternative to https://github.com/zephyrproject-rtos/zephyr/pull/60894. As pointed out there, the 'misc-flasher' ZephyrBinaryRunner name is inconsistent with the names of these associated files:

zephyr/boards/common/misc.board.cmake
scripts/west_commands/runners/misc.py

The runner probably should have been named 'misc' all along. I added it in a hurry to get an issue report to go away a long time ago, and I wasn't thinking about how it would evolve. Right now it only "flashes", but it would be trivial to extend this to add miscellaneous debug support as well.
Clean things up so that the flasher's name is "misc".
To avoid breaking out of tree boards, though, preserve backwards compatibility by allowing runners to declare deprecated names as well, and keep the old 'misc-flasher' name around, but deprecated.

Looks like CI is flagging some real issues; I'll update when I've fixed them.

@fabiobaltieri please revisit

hey https://github.com/zephyrproject-rtos/zephyr/pull/61243/commits/6ff9efb88e0a64815644edadb4005418970e672f#r1294803186 is still relevant, asking if this should have something like https://github.com/zephyrproject-rtos/zephyr/pull/60894/commits/c63f621d7ccd92d244f1c70f44682f188fddbd0c


This is Abell with Tailwind

What type of PR is this?

[x] Feature
[ ] Bug Fix
[ ] Refactor
[ ] Documentation Update

Description
Added unit tests?

[x] No, I want help in writing tests.
[ ] No, I want someone else to write tests.
[ ] No, The addition does not need tests.
[ ] Yes

My Github project link
abell-demo
[optional] Random GIF to +1 someone's day
Random Gif

I will add back the logo and and documentation link and remove my name

This is great! Should we move this to https://github.com/abelljs/integrations instead?
I was thinking playground here can be simpler playgrounds to make sure abell doesn't break. So we can write tests over playground examples etc.
And abelljs/integrations can be the place people refer to when they want to see how to integrate abell with their favorite tools. We can also think of some way to use those integration examples as templates in npx create-abell command


#18 Add FindEigen3 module

I only added my name to make clear right away that the file contains changes.

Next time please add: # Modified by ${NAME} on {DATE}, ${SUMMARY} below the copyright notice instead.
Again if you are absolutely certain your changes are copyrightable (and this definition is quite fuzzy), you may add your name. But if you have the slightest of doubts (here simply renaming a variable), it is better just putting a notice of changes as advised.
Thanks for suggesting the use of the upstream Eigen find module by the way. I (wrongly) thought Kevin was in a rush for a fix so I went ahead and committed it.


when retryable error happens, cosmos client returns empty result for pagination query

Package Name:  azure-cosmos
Package Version:  4.5.2b5 (as well as master)
Operating System: linux
Python Version:  3.11

Describe the bug
the very first pagination query, means no continuation token, returns no result if a retryable error happens
specifically, if https://github.com/Azure/azure-sdk-for-python/blob/azure-cosmos_4.5.2b5/sdk/cosmos/azure-cosmos/azure/cosmos/_execution_context/aio/base_execution_context.py#L127 throws exception, _has_started, which is set to True already, won't be revert back to the original value, thus when retry calling into _fetch_items_helper_no_retries, it will skip the while loop if there is continuation token, and returns 0 result.
we have verified, if we try catch https://github.com/Azure/azure-sdk-for-python/blob/azure-cosmos_4.5.2b5/sdk/cosmos/azure-cosmos/azure/cosmos/_execution_context/aio/base_execution_context.py#L127 and revert _has_started back to the original value, then the issue is resolved.
To Reproduce
Steps to reproduce the behavior:

send any no QueryItems query with expected non empty result concurrently
until hitting 429
some of the query start returning empty result

Expected behavior
A clear and concise description of what you expected to happen.
the query should either fail or return correct result
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

This issue is addressed and fixed in PR 35090 @hihihuhu @nicknotfun


Release_config not work at all

Expected Behavior
Transfer pokemons with CP lower than X and IV lower than Y
Actual Behavior
Console:
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950] [IV 0.58]
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950]
release_config.json
"Primeape": { "release_under_cp": 900, "release_under_iv": 1, "cp_iv_logic": "and" },
In-game

Steps to Reproduce
Start the bot lol
Other Information
OS: Windows 10
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here)
Last dev downloaded a few minutes ago. (Seriously, i don't know how i can use git command)

You chose the option AND which means:
[CP 950] [IV 0.58]
if(CP<900 AND IV<1):
release
since CP>900 the result will be false

No issue, your config specifes that both CP and IV pokemon values needs to be true in order to transfer it
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950] [IV 0.58]
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950]
release_config.json
"Primeape": { "release_under_cp": 900, "release_under_iv": 1, "cp_iv_logic": "and" },

but still, kinda confuse.
He want to hunt CP 900+ Primeape with IV potential = 1
How to config then?
We should improve this logic

in my config say
Don't transfer a primeape with 900 or more AND IV 1 or more, and the bot don't transfer a primeape 950 (OK) with IV 0.58 (not OK)

i see that you are right, do 0.99 until its fixed :)

still not working with AND and IV 0.99, but work fine with OR

[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950] [IV 0.58]
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950]
release_config.json
"Primeape": { "release_under_cp": 900, "release_under_iv": 1, "cp_iv_logic": "and" },```

This means: `if cp < 900 AND iv < 1 THEN release`

In that case, the release config is broken, the primeape is 950, OK but the IV is lower than 1

for me it seems that release_config.json is never used with the new -cf config.json logic

@crusardri dude... it's a logic AND. It's working as expected. if cp < 900 AND iv < 1 . CP is less than 900? False. IV is less than 1? True. False AND True = False,  so it won't release. Nothing is broken, it's boolean math.

Math logic:
OR
0 0 = 0
0 1 = 1
1 0 = 1
1 1 = 1
AND
0 0 = 0
0 1 =0
1 0 = 0
1 1 = 1
Pokemon used: Primeape PC 950 (>900) IV 0.58 (<1)
[2016-07-24 14:09:43] [x] Captured Primeape! [CP 950] [IV 0.58]
My config
"Primeape": { "release_under_cp": 900, "release_under_iv": 1, "cp_iv_logic": "and" },
Expected Behavior
if primeape is PC >900 AND IV >1, keep
Actual Behavior
if primeape is PC >900 OR IV >1, keep

@crusardri:

IV condition is False and CP condition is True, right? Agree on this?
False AND True is False
Returning False means it SHOULD NOT transfer.

With this configuration you're only keeping in your Pokemon list whatever has CP higher than 900 and IV 1 (IV 1 is almost impossible to find).

Just check the code, it's clear:
if 'release_under_cp' in release_config:
                min_cp = release_config['release_under_cp']
                if cp < min_cp:
                    release_results['cp'] = True

Transforming into text: if pokemon cp is lower than 'release_under_cp', it should be released based on that criteria. Same happens to IV.
Your pokemon CP = 950 and IV = 0.58, config is CP 900 and IV 1.
950 < 900 = FALSE
0.58  < 0.1 = TRUE
False AND True = False = not release.

ahhh, ok, i understand now, but it don't have any sense.
Why the config is for transfer instead of keep it?

The file is named release_config.json and the name of the key is release_under_cp...

IMHO, it's pretty clear what it means.

@douglascamata and how did you manage to use release_config file with the config_file logic ?

Ok, it's my fault, close the issue if you want.
@mehdi-S
release when the pokemon have PC lower than X and IV lower than Y, or release when the pokemon have PC lower than X or IV lower than Y
PC is 950 and IV is 0.58
the config says PC 900 and IV 1
950 > 900 = false
0,58 < 1 = true
OR = X + Y
AND = X * Y
OR: false + true = true, release it
AND: flase * true = false, keep it

@mehdi-S I don't know about config_file logic + release_config.json file. I implemented the release_config.json logic before the config_file one. I just woke up a few minutes ago and saw it there, so...


What could be causing slow reloads

Hi there! it's me again. I was wondering if their is any reason reloads are pretty slow? 20seconds>? Have uninstalled - installed and updated the cli.

@anubhavg8!, Thanks for reaching out. Your issue might be with the CLI rather than this project. Could you open an issue in the CLI repository for more targeted assistance?
Best regards.


add tailwind elements integration with django

Project Information

Project Name: Tailwind Elements
Project URL: https://tailwind-elements.com/ & https://github.com/mdbootstrap/Tailwind-Elements
Description: Bootstrap components recreated with Tailwind CSS, but with better design and more functionalities

Criteria
Please answer the following questions about the project you are submitting. This will help us evaluate if the project should be included in the Awesome Django list.

Is the project new?

[x] Yes
[ ] No

How long has the project been maintained?
over 2 years

How many releases has it had if it's a library or package?
https://tailwind-elements.com/docs/standard/getting-started/changelog/ - The following list is not complete.

Are you the author or are you submitting the project on behalf of a company?

[ ] I am the author
[x] I am submitting on behalf of a company
[ ] Other (please specify)

What makes it awesome?
Tailwind Elements provides documentation and resources specifically tailored to integrating their UI components with Django, making it straightforward for Django developers to incorporate these components into their projects!

Additional Information
Please provide any additional information that you believe is relevant to the project or its evaluation for inclusion in the Awesome Django list. This might include information about the project's documentation, test coverage, community support, or any unique features that set it apart from other Django projects.
Thank you for your submission!

We appreciate the pull request. We are going to pass on it for now but might reconsider it down the road.


Change assembly name for lazer

Hopefully this will address the issue where we cannot use gosu and lazer at the same time... Need tests immediately

@Dr_Shindo provide more info on testing plz

Confirmed that issue is caused by process name clash.
@CloneWith you can add your non-workaround solution on this PR or, simply merge this if you want.

 New PRs would be created whenever I investigate more on this.


Fix duplicate startup logging

Noticed this in the startup log e.g.:
2019-08-13 14:02:36,807 INFO  - Starting java -Xmx128m -jar "my.jar"
2019-08-13 14:02:36,823 INFO  - Starting java -Xmx128m -jar "my.jar"

Not sure if the second set of logging is meant to be for mentioning that extensions were loaded or something or was maybe just the result of a merge conflict being resolved with duplicate lines. Duplicate was introduced here - https://github.com/kohsuke/winsw/commit/2546168ed395ab992ca357dddd02d861cf885cf5#diff-aa1cd4852033c3fac020e2c2d6c29637R267


Remove all deprecations

API should not have anything deprecated as it's new:
  /**
   * Calculate mean on aggregated {@code MeasureValue}s.
   *
   * @since 0.1.0
   * @deprecated since 0.13, use {@link Distribution} instead.
   */
  @Immutable
  @AutoValue
  @Deprecated
  @AutoValue.CopyAnnotations
  public abstract static class Mean extends Aggregation {

@SergeyKanzhelev if you take care of this (I saw the PR) please assign this to you so we don't duplicate the work.

This is done now I think.


[WIP] Update textattack-feedstock

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: tensorflow>=2 must contain a space between the name and the pin, i.e. tensorflow >=2
requirements: run: tensorflow_text=>2 must contain a space between the name and the pin, i.e. tensorflow_text =>2

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: sentence_transformers>0.2.6 must contain a space between the name and the pin, i.e. sentence_transformers >0.2.6
requirements: run: gensim==3.8.3 must contain a space between the name and the pin, i.e. gensim ==3.8.3

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: gensim==3.8.3 must contain a space between the name and the pin, i.e. gensim ==3.8.3
requirements: run: sentence_transformers>0.2.6 must contain a space between the name and the pin, i.e. sentence_transformers >0.2.6

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The requirements section contained an unexpected subsection name. pip is not a valid subsection name.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Can't make the bar reach the end while extending the scope with a big amount of data

Here is an example: Angular Loading Bar
I have tried to call the .complete() function in the finally block but it seems not working.
Is it possible?

I'm having a somewhat similar issue, it just appears at about 15% and then disappears. No animation at all.

Having the same issue as @juanmanavarro. Loader will not complete with larger requests. Any help would be appreciated @chieffancypants

Confirmed. Interestingly it seems OK if I change the code to do the scope assignment in a timeout: http://codepen.io/faceleg/pen/eZgdGq