furtherance breaks on startup

Describe the bug
When trying to run the furtherance time tracker the application crashes with:
thread 'main' panicked at 'Failed to retrieve template child. Please check that it has been bound and has a #[template_child] attribute.', /build/furtherance-1.6.0-vendor.tar.gz/gtk4/src/subclass/widget.rs:1305:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Steps To Reproduce
Steps to reproduce the behavior:

Run furtherance from the unstable channel: nix-shell -p furtherance --run "furtherance"

Expected behavior
I expected the application to start.
Screenshots
n/a
Additional context
This seems to be a problem with multiple gtk-rs applications at the moment. I think this is basically a duplicate of #219216 or #216770 but if I'm understanding it correctly the issue has to be addressed in each application separately.
Notify maintainers
@CaptainJawZ
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.9, NixOS, 22.11 (Raccoon), 22.11.3535.799d153e4f3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(radke): `""`
 - channels(root): `"home-manager-22.11.tar.gz, nixos-22.11, nixos-unstable"`

I'll try to fix it this weekend, thank you for such a detailed report!

I think the source of the problem is described here: https://github.com/NixOS/nixpkgs/pull/217069/files

The fix is to upgrade gtk-rs to >= 0.5.3.

Since lakoliu upgraded the version upstream 3 weeks ago (see https://github.com/lakoliu/Furtherance/commit/dff62a9e31ff85305eb2d70b036ee25c90e4feeb) I think we just have to bump the version to 1.7 and we should be golden :-)
(I just tested it, and at least locally, I got it working by just swapping out the version number and sha hashes)

pull request is up, thanks for your suggestions!
thankfully it was an easy fix, sorry for the delay, it was holiday in my country.
https://github.com/NixOS/nixpkgs/pull/225656

Should be fixed by https://github.com/NixOS/nixpkgs/pull/230249
Thanks for the great response :-)


Improve maintenance of gem

Currently delayed_paperclip supports lot of background backends. It would be easier to maintain code if we could reduce it.
My idea is to move forward and go altogether with paperclip 5.0 (which currently is in beta) and drop support for Rails < 4.2 and Ruby 2.0 https://github.com/thoughtbot/paperclip/blob/f7aa32069cc798dc96ca07c8dceee2ced7a1b571/NEWS#L5-L6
Rails 4.2 introduced ActiveJob, so what do you think about dropping support for other backends and use only AJ?

@morgoth I think we should do this with a major version change

Yes, sure - with some deprecation warning in minor release.
Altogether with https://github.com/jrgifford/delayed_paperclip/pull/169 what should be the next release? Major or just minor?

ongoing on https://github.com/jrgifford/delayed_paperclip/pull/178


How can I change one file in a marathon app?

Is there a way to trigger a redeploy for a Marathon application already running in a DC/OS cluster, without changing the definition file (.json) as the configuration for that app would remain the same.
For example I need to make a change in the index.php file and redeploy the app by means of Docker image using Jenkins.
Thank you

@andrei-bv the Marathon API has a /v2/apps/{app_id}/restart endpoint via which you can trigger a restart for all associated tasks. The related dcos-cli command is dcos marathon app restart [--force] <app-id>

Restarting the app assumes that you are overwriting the tag in use for your docker image and that forcePullImage is set to true. Another way which is imo preferable is to update the app :
echo '{"container": {"docker": {"image": "my-app:X.Y.Z" } } }' | dcos marathon app update /my-app

This would deploy the same app with the specified image tag and kill the previous one.
@meichstedt : let us know if you rather suggest another approach for this.

@bamarni - forcePullImage is set to TRUE in my configuration file and also the image tag is unique with every try, set as the git commit id (${GIT_COMMIT}) - but unless I change the marathon definition file, trying to redeploy thru Jenkins UI will not work. I get "Build successful" in Jenkins - but no restart in DC/OS.

@andrei-bv : forcePullImage only pulls the image for the given tag in use in your marathon definition. The other way that I recommended to you is to update the app with the new tag you want.

@bamarni i'm trying it through the method you described above, echo'ing the JSON, but this completely removes existing config for the docker part. Here are the steps:
Before:
"container": {     "docker": {       "image": "abc/myimage:v1",       "forcePullImage": true,       "privileged": false,       "portMappings": [         {           "containerPort": 8000,           "protocol": "tcp",           "servicePort": 10122,           "labels": {             "VIP_0": "/a/b:8000"           }         }       ],       "network": "BRIDGE"     }   }
Execute:
echo '{"container": {"docker": {"image": "abc/myimage:v2" } } }' | dcos marathon app update a/b
Results in:
"container": {     "docker": {       "image": "abc/myimage:v2",       "forcePullImage": false,       "privileged": false,       "network": "HOST"     }   }
I would expect that only the {image} part is changed. Of course we can extend the json we echo with the necessary values, but that feels like a bit too much.
Btw, we are running a pretty old version:

dcoscli.version=0.4.15
dcos.version=1.8.8

Has this behaviour been changed in newer versions perhaps?

Thank for the explanation @meichstedt, I missed that as I was testing with a minimal container definition.

@meichstedt  thanks for explaining 👍


Add a logmessage_rtr config for new gorouter_time and app_time fields

This should fix the issue we're having where router log formats changed with cf 12.17
notes from upstream

These fields were introduced in routing-release 0.196.0 https://github.com/cloudfoundry/routing-release/releases/tag/0.196.0 which forms part of cf-deployment v12.17.0 https://github.com/cloudfoundry/cf-deployment/releases/tag/v12.17.0

Security Considerations
None

LGTM!


SELinux preventing Polkit policy from loading

On Fedora 39, I've noticed that the polkit policy will not load when selinux is set to enforcing.
From the audit log:
type=AVC msg=audit(1697115971.173:129): avc:  denied  { open } for  pid=1046 comm="polkitd" path="/usr/share/polkit-1/actions/com.quexten.goldwarden.policy" dev="dm-0" ino=559338 scontext=system_u:system_r:policykit_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0

Fixed by sudo chcon system_u:object_r:usr_t:s0 /usr/share/polkit-1/actions/com.quexten.goldwarden.policy
Todo:

[ ] Fix this in the setup

Should be fixed by 55b3383fb90141c121a1fc7f4d01b5e5e129b795 but requires more testing.


Problems with ODBC MSAccess and UTF8

Hi
Please look at the attached pictures. All software is running on the Windows2012r2 server.
Database2.zip
Database2.zip

My guess is that something is wrong inside DBeaver. It's så strange that only row-id 15 (Lodz) but spelled with Polish letters is wrong.. Can anyone perhaps explain ?
Thanks in advance.

I see that city name in 14th row is in ASCII. 15th row is in unicode.
Why do you think it is something inside DBeaver?

Hey, and thanks for the swift answer  :-)
All other two-byte special characters is ok. Even the € which is a three
byte unicode.
I use this table over and over to ensure that I have controle over the
european countries, and ONLY DBeaver has problems with this when it comes
to MS-Access...
PostGreSQL has no problems with this. Try to see the two files I have
attached.
In my sample-data there is a lot of unicode... Why only the polish ones
went wrong ?
And here you can see how well it works in DBeaver/PostgreSQL
[image: image.png]
So I will still argue that DBeaver/MSAccess has "issues"
Venlig hilsen
Thorkil Johansen
Tel: +45 4070 6547
Den søn. 17. feb. 2019 kl. 18.11 skrev Serge Rider<EMAIL_ADDRESS>
:

I see that city name in 14th row is in ASCII. 15th row is in unicode.
Why do you think it is something inside DBeaver?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/5299#issuecomment-464482674,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALjw1Zgyp20hyGu47qHlLMI24qGMjDkKks5vOY1UgaJpZM4a_o61
.

$allery
€urocity
Aberdeen
cities
Lodz
Łódź
Preußisch Oldendorf
Überlingen
Zagreb
Ælligelyng
Østerby
Aalborg
Ålestrup

The names of the cities has a lot of UTF-8 characters in them. But ONLY when I use DBeaver and the JDBC/ODBC connection I got this problem. As you can see, the Powershell uses the exact same ODBC driver and PS has no problems.  Therefore I say (or guess) it is inside DBeaver that the solution has to be found.

Hi. Do we agree that there is an issue here ?

I'm not sure how this happened but even this is a bug then most likely it is originated in UCanAccess driver.
If you are on windows then you could try ODBC MS Access driver to validate this: http://ucanaccess.sourceforge.net/site.html

As I documented in the first post, I can read through the Access driver without problems from PowerShell and other software. There is only one ODBC driver in use on my server.
Since most of the characters (outside basic ANSI) if from codepage "Western" and since the two Polish characters is outside "Western" I'll suggest that you look into DBeaver to find the spot where you miss to use UTF correctly.
Again: All kind of software on my server can do this correct, Only DBeaver fails.

This is what I see (using UCanAccess 4.0.2 driver):

So I can't even reproduce this issue.
The problem is in your driver configuration (what exactly driver do you use?) or in your driver version (e.g. old UCanAccess or some old ODBC bridge driver).

I'm using 64bit 'Microsoft Access Driver (*.mdb, *.accdb)'
Version 14.00.7180.5000
From Microsoft Cooperation

Could you try to UCanAccess driver (not ODBC) in DBeaver?

there is no update on ticket for a long time.
Tiket closed


Makes dev_setup.py script more portable

This will avoid problems where pip on PATH does not map to the version of Python that the script was started with.
I believe the exec_command function is now unused, but didn't want to just delete it. LMK if you want it gone and I'll take it out.

Codecov Report

Merging #2062 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2062   +/-   ##
=======================================
  Coverage   53.06%   53.06%
=======================================
  Files        4774     4774
  Lines      119483   119483
=======================================
  Hits        63406    63406
  Misses      56077    56077

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 5ecbcc0...4f5237e. Read the comment docs.

Thanks @zooba :). This was highly inspired by CLI, so they have the same issue (if you feel like PR it ;))
Yes, you can get rid of of exec_command if you have time. Thanks!

Thanks @zooba :)


Joining Tables

You can join tables in apigility?

Can we re-open this issue until we get a working example?

Followed the steps in https://apigility.org/documentation/recipes/join-tables
However, after removing the configuration for zf-apigility.db-connected Users\V1\Rest\Users\UsersResource, I am getting the following error:
Unable to resolve service "user_locations" to a factory; are you certain you provided it during configuration?
Help please. Did we miss a step here? Thanks in advance!


Added Directory class

Support for listing assets, products and tier configs.

Codecov Report

Merging #63 into master will increase coverage by 1.35%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
+ Coverage   90.95%   92.31%   +1.35%
==========================================
  Files          31       32       +1
  Lines        1438     1470      +32
==========================================
+ Hits         1308     1357      +49
+ Misses        130      113      -17

Impacted Files
Coverage Δ

connect/resources/base.py
94.31% <ø> (+5.68%)
:arrow_up:

connect/resources/fulfillment_automation.py
37.5% <ø> (ø)
:arrow_up:

connect/resources/directory.py
100% <100%> (ø)

connect/resources/__init__.py
100% <100%> (ø)
:arrow_up:

connect/exceptions.py
98.14% <0%> (+1.85%)
:arrow_up:

connect/models/schemas.py
94.16% <0%> (+2.43%)
:arrow_up:

connect/models/server_error_response.py
100% <0%> (+10%)
: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 5034f88...3c22b4a. Read the comment docs.


Detekt compiler plugin configuration does not respect exclusions set

I configure the plugin by following the instructions in the docs:
tasks.withType<org.jetbrains.kotlin.gradle.tasks.KotlinCompile>().configureEach {
    detekt {
        exclude("build/")
        include("**/*.kts")
    }
}

my regular detekt configuration:
detekt {
    config.setFrom("config/detekt.yml")
    // Scan project dir for files
    source.setFrom(projectDir)
    // Config file is built upon default
    buildUponDefaultConfig = true
    // Turns on all the rules. `false` by default.
    allRules = true
    // Additional output on task execution
    debug = true
    // If set to `true` the build does not fail when the maxIssues count was reached
    ignoreFailures = false
    enableCompilerPlugin = true
}

but when I run .\gradlew compileKotlin it analysis the whole build folder. Also when I run it twice with .\gradlew compileKotlin --no-build-cache it does not analyse the build folder anymore which implies that this behavior happens with my source files which I want to get analysed but are only analysed in the first run which would be a wrong behavior

This issue is waiting for authors feedback since 30 days. Please comment providing the requested feedback or this issue will be closed in 7 days.

This issue is waiting for authors feedback since 30 days. Please comment providing the requested feedback or this issue will be closed in 7 days.


changes to the image context menu

I was noticing a double set of separators in my context menu and so I found that Firefox had some changes in its image context menu. For example "View Image Info" no longer seems to exist. #context-sep-copyimage also does not exist but there is now a #context-sep-setbackground. Also the order of the items has changed some.
I attached a copy of the new image-context.css (renamed to txt).
image-context.txt

Thanks for the notice, it's fixed now.


Not able to deploy apps from images.

acorn version v0.7.0-alpha1-141-g5197ed75+5197ed75
Steps to reproduce the problem:
acorn run -n mytestnew2 sangeetha/myfirstacorn:v0.0.1
mytestnew2
STATUS: ENDPOINTS[] HEALTHY[] UPTODATE[]
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] [image-pull: could not parse reference: ]
^C%

 acorn run -n mytest1 ghcr.io/acorn-io/library/hello-world
mytest1
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] [image-pull: could not parse reference: ]
^C%

Looks like @cjellick got this! Unassigned myself


Too much procrastination/taking too much breaks

I mean... to be honest I was worrying about this one a little too much, but since I gave away all my amnesia mods over on RoozerXC/AmnesiaMods out of demotivation and i have been thinking about working on Hate is Peace slowly and meticulously, as well as trying to strengthen and pick myself back up from all the stress thats made me put myself down many times, i think ill try to give this one a little close anyway since i feel a little better knowing i did my best


Typo in readme

I think you meant var instead of const. Javascript !== Swift :-)

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const ;)


Use patch for ARM64 assembly bitmap extraction

This temporarily replaces the Arrow dependency with the fix in https://github.com/apache/arrow/pull/37785 - making it possible to read Parquet files with all null values on ARM64 devices.
Fixes #57.

@tschaub If desired, instead of using that patch (until it is merged) you could also just build with the noasm tag which should fix the issue until the fix is merged in. The noasm tag will just force it to default to the pure go implementation rather than use the vectorized assembly which has the issue.

Thanks, @zeroshade.  I figured this could be an opportunity to help validate the fix too.  If it doesn't get merged or if other issues come up, I'll go with the noasm tag.


Compile error

Running make out/tty-share results in:
tty-share/pty_master.go:10:2: cannot find package "github.com/elisescu/pty" in any of:
        /usr/lib/go/src/github.com/elisescu/pty (from $GOROOT)
tty-share/main.go:14:2: cannot find package "github.com/elisescu/tty-share/common" in any of:
        /usr/lib/go/src/github.com/elisescu/tty-share/common (from $GOROOT)

I could probably fiddle with it to make it run but it looks like there's a step missing in the makefile.

go get github.com/elisescu/pty
go get github.com/elisescu/tty-share/common

That fixed the problem! Thanks!
Maybe it'd be a good idea to add something to the readme?


download.sh didn't work

Rally version (get with esrally --version): esrally 1.1.0
Invoked command: sh ~/.rally/benchmarks/tracks/default/download.sh geopoint
Configuration file (located in ~/.rally/rally.ini)):
JVM version:
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
OS version: CentOS Linux release 7.1.1503 (Core)
Description of the problem including expected versus actual behavior:  documents.json.bz2 and documents-1k.json.bz2 are unavailable. They are HTML pages.
.
Steps to reproduce:

curl http://benchmarks.elasticsearch.org.s3.amazonaws.com/corpora/geopoint/documents.json.bz2
curl http://benchmarks.elasticsearch.org.s3.amazonaws.com/corpora/geopoint/documents-1k.json.bz2

Describe the feature:
Curl can not download files from AWS S3 now, also in download.sh.

Thanks very much for your interest in Rally.
This appears to be a user question, and we'd like to direct these kinds of things to the forums. If you can stop by there, we'd appreciate it. This allows us to use GitHub for verified bug reports, feature requests, and pull requests.
There's an active community in the forums that should be able to help get an answer to your question. As such, I hope you don't mind that I close this.


How to plot as 2 series?

Hello @ncp1402
I would like to plot 2 seriers graph. I mean single line graph but with different color/representation.
Eg like this:
.
Can you please help in ploting like that. Thanks

create 2 plots with different styles.

I didn't get you exatly.
are you saying to create 2 separate plots or graps
i.e 2 QlLinePlot { id:plot}
or
addGraph(names[i], true, colors[i], 1, 'solid');
if so how to add data points to both of them?

create 1 plot with 2 graphs:
addGraph('Actual', true, "blue", 2, 'solid');
addGraph('Future', true, "blue", 1, 'dash');

Then add points, for future points on Actual graph add NaNs:
addPoints(0, [0.3,NaN]); // Actual points visible, Future invisible
addPoints(1, [0.1,NaN]);
addPoints(2, [0.6,NaN]);
addPoints(3, [NaN,0.9]); // Actual points invisible, Future visible
addPoints(4, [NaN,0.2]);
addPoints(5, [NaN,0.7]);

wow ! Perfect Thanks a lot :+1:


APNS Notification caused error: 8 for device

Summary: I see APNS Notification caused error: 8 for device error in my logs when I send out a push notification. The notification is delivered correctly though.

[x ] You've met the prerequisites.

[x ] You're running the latest version of Parse Server.

├─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>  │ │ │ ├─┬<EMAIL_ADDRESS>  │ │ ├──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>

[x ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
Environment="NODE_ENV=development"
Environment="DATABASE_URI=mongodb://localhost:27017/development"
Environment="APP_ID=XXXXXXXXXXXXXXX"
Environment="CLIENT_KEY= XXXXXXXXXXXXXXX"
Environment="RESTAPI_KEY= XXXXXXXXXXXXXXX"
Environment="MASTER_KEY= XXXXXXXXXXXXXXX"
Environment="PORT=1337"
Environment="PARSE_MOUNT=/parse"
Environment="SERVER_URL=https://push.xenim.de:1337"

var api = new ParseServer({
    databaseURI: databaseUri || 'mongodb://localhost:27017/dev',
    cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
    appId: process.env.APP_ID || 'XXXXXXXXXXXXXXXXX',
    clientKey: process.env.CLIENT_KEY || 'XXXXXXXXXXXXXXXXX',
    restAPIKey: process.env.RESTAPI_KEY || 'XXXXXXXXXXXXXXXXX',
    masterKey: process.env.MASTER_KEY || 'XXXXXXXXXXXXXXXXX', //Add your master key here. Keep it secret!
    push: {
    ios: [
    {
      pfx: process.env.APN_PUSH_DEVELOP_P12_PATH || __dirname + '/push-certificates/XenimDevelopmentPushCertificate.p12', // The filename of private key and certificate in PFX or PKCS12 format from disk
      bundleId: 'com.stefantrauth.Xenim', // The bundle identifier associate with your app
      production: false // Specifies which environment to connect to: Production
    },
    {
      pfx: process.env.APN_PUSH_PRODUCTION_P12_PATH || __dirname + '/push-certificates/XenimDistributionPushCertificate.p12', // The filename of private key and certificate in PFX or PKCS12 format from disk
      // cert: '', // If not using the .p12 format, the path to the certificate PEM to load from disk
      // key: '', // If not using the .p12 format, the path to the private key PEM to load from disk
      bundleId: 'com.stefantrauth.Xenim', // The bundle identifier associate with your app
      production: true // Specifies which environment to connect to: Production
    }
    ]},
    serverURL: process.env.SERVER_URL || 'https://myserver.com:1337'  // Don't forget to change to https if needed
});

Steps to reproduce
This is how I send out my push message:
    curl -X POST \
      -H "X-Parse-Application-Id: XXXXXXXXXXXXXXX" \
      -H "X-Parse-Master-Key: XXXXXXXXXXXXXXXXX" \
      -H "Content-Type: application/json" \
      -d '{
            "where": {
              "deviceType": {
                "$in": [
                  "ios"
                ]
              }
            },
            "data": {
              "title": "The Shining",
              "alert": "All work and no play makes Jack a dull boy."
            }
          }'\   https://myserver.com/parse/push

The push message gets delivered correctly to my device. I have only one single device registered to this parse-server.
In the logs I see APNS Notification caused error: 8 for device. I do not know why this error happens.
My thoughts on this: This looks like parse is trying to send out the notification two times: First with the production.p12 certificate and after that with the development.p12 certificate. The first try fails, because the device token belongs to a device in development mode.
I run parse-server with NODE_ENV=development. So this might be an issue with parse server trying to send the notification to production?
Logs/Trace
I receive this error when I try to send out a push notification:
    Mar 18 14:35:18 xsn-app parse-app[31790]: Can not find sender for push type android, {"where":{"deviceType":{"$in":["ios"]}},"data":{"title":"The Shining","badge":"1","alert":"All work and no play makes Jack a dull boy."}}
    Mar 18 14:35:18 xsn-app parse-app[31790]: APNS Notification caused error: 8 for device  Device {
    Mar 18 14:35:18 xsn-app parse-app[31790]: token: <Buffer 65 97 1a 22 d3 01 da 60 7a 10 5e 2f a8 95 e2 79 73 08 04 36 4c 94 08 1d de 8d df de fb 6e 6e 7b>,
    Mar 18 14:35:18 xsn-app parse-app[31790]: connIndex: 0,
    Mar 18 14:35:18 xsn-app parse-app[31790]: appIdentifier: 'com.stefantrauth.Xenim' } { encoding: 'utf8',
    Mar 18 14:35:18 xsn-app parse-app[31790]: payload:
    Mar 18 14:35:18 xsn-app parse-app[31790]: { title: 'The Shining',
    Mar 18 14:35:18 xsn-app parse-app[31790]: aps:
    Mar 18 14:35:18 xsn-app parse-app[31790]: { badge: undefined,
    Mar 18 14:35:18 xsn-app parse-app[31790]: sound: undefined,
    Mar 18 14:35:18 xsn-app parse-app[31790]: alert: 'All work and no play makes Jack a dull boy.',
    Mar 18 14:35:18 xsn-app parse-app[31790]: 'url-args': undefined,
    Mar 18 14:35:18 xsn-app parse-app[31790]: category: undefined } },
    Mar 18 14:35:18 xsn-app parse-app[31790]: expiry: undefined,
    Mar 18 14:35:18 xsn-app parse-app[31790]: priority: 10,
    Mar 18 14:35:18 xsn-app parse-app[31790]: retryLimit: -1,
    Mar 18 14:35:18 xsn-app parse-app[31790]: device: undefined,
    Mar 18 14:35:18 xsn-app parse-app[31790]: compiled: '{"title":"The Shining","aps":{"alert":"All work and no play makes Jack a dull boy."}}',
    Mar 18 14:35:18 xsn-app parse-app[31790]: truncateAtWordEnd: false,
    Mar 18 14:35:18 xsn-app parse-app[31790]: _alert: 'All work and no play makes Jack a dull boy.' }
    Mar 18 14:35:18 xsn-app parse-app[31790]: APNS Connection 1 Notification transmitted to 65971a22d301da607a105e2fa895e279730804364c94081dde8ddfdefb6e6e7b
    Mar 18 14:35:18 xsn-app parse-app[31790]: APNS Connection 0 Disconnected
    Mar 18 14:35:18 xsn-app parse-app[31790]: APNS Connection 0 Connected

I got this error when I defined both production and dev in iOS Push, I think this parse-server is trying to send both with production and the dev cert and obviously one of them will always fail, If you remove the production config you will lose this error.... but his is just my observation...

So is this behaviour intended? I expected parse-server to send push notifications respecting its node environment?

I guess it is error because you can define production and dev together in the array... maybe it always tries production first and then not do the dev, but my app is still in dev so it is hard to say for me... I just left the comment here because I also want a response from Parse developers...

As soon as I define only the development push certificate the error does not occur.
    push: {
    ios: [
    {
      pfx: process.env.APN_PUSH_DEVELOP_P12_PATH || __dirname + '/push-certificates/XenimDevelopmentPushCertificate.p12', // The filename of private key and certificate in PFX or PKCS12 format from disk
      bundleId: 'com.stefantrauth.Xenim', // The bundle identifier associate with your app
      production: false // Specifies which environment to connect to: Production
    }
    // ,{
    //   pfx: process.env.APN_PUSH_PRODUCTION_P12_PATH || __dirname + '/push-certificates/XenimDistributionPushCertificate.p12', // The filename of private key and certificate in PFX or PKCS12 format from disk
    //   // cert: '', // If not using the .p12 format, the path to the certificate PEM to load from disk
    //   // key: '', // If not using the .p12 format, the path to the private key PEM to load from disk
    //   bundleId: 'com.stefantrauth.Xenim', // The bundle identifier associate with your app
    //   production: true // Specifies which environment to connect to: Production
    // }
    ]},

I think the best way to do it is to have completely separated setups for production and development.

separate database
separate parse-server instance on different ports/urls
separate APN configuration for each instance

@KudosGuy you are right, when passing multiple certificates, the ParsePushAdapter will try sending on each configuration sequentially.
@funkenstrahlen you are right about the strategy, having multiple apps for dev and prod. I used that strategy in the past with parse.com apps, and build settings on the Xcode project or JS app.


Sigh, need private folder reset

Without getting into my opinions on UX, I am here to kindly request my private folder for smf be reset. I did indeed reset my paper key (though I had no files previously, so why do I need to go through these hoops of resetting it?)

$ keybase sign -m "$(date): Please completely reset folder /keybase/private/smf because I no longer have access to any of the devices it is keyed for."
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5wcIkHbsAv3myH ev3MDsl4mUkZ4PF cFs0dBILvcOEocp MyA4xmnFPCkNpPo eRf4AyxuZd64WBB 75l3Ai3xhokI9d5 x7M5sbnlaPXgRRw uajb0gDUNdY6W6y d89WzJA32x1k6NY 243KchQ6E6xG1AO EAiKL19FHl1W6gQ 9mfNK1BHYf8aEkq 8LvFN2bTWKemQ09 8J0Mu7dLgij2Xel 5yza7IG43cnCxz4 fcWt6P5TS9mz3Eg eggQQ9rj0oGCn6N 1PrJRDJWV07ujq3 fHRZjhB99cfbvbU rRMY7IU9mvQKIBL Fzqp0UBlD32oPaX AtJDfebmrenYP0S ioiRRBtOfMkpLoA 7k1ZgK9hGT72B5d hzLAyFeZJKFeB2j 0Da9hPzzRkDxjf0 RD9z2m1BAiYg9II krUrQnlfxF5nQ0d caP7OOodhwyfIL5 ckp3SOFS4vQSdP0 md1lntVw0y8b28b sO. END KEYBASE SALTPACK SIGNED MESSAGE.

Ok, I've reset the folder for you.  Please close this out if things seem ok.
We'd value hearing any suggestions you have for improving the UX.  Is there something we could have done to minimize the risk of losing your paper key?
We are a small startup and are actively working on other higher-priority things right now.  In the fullness of time, I agree it would be nice to have a secure way to reset folders that don't have any data yet.  It's not trivial for the server to do it, though, since we don't want the server to be able to mess with folders arbitrarily.  So we'd need to build a nice GUI around letting the user securely request the resets, and we just haven't had time to design/build it yet.  Sorry for the inconvenience!


EMC values above the max Long limit not being formatted properly.

EMC Values bigger than Java's Long.MAX_VALUE (9,223,372,036,854,775,807, 9 Quintillion) are currently not formatted at all, the current suspect is incorrect number comparisons, which fail as numbers get larger. It is safe to assume that after Double.MAX_VALUE (1.7976931348623157e+308), a crash or at least some kind of breaking would happen, but it's practically impossible to get that high naturally. I'm looking into ways to fix this, such as making everything a biginteger.

Fixed in 1.0.9 via df926a611f0ee3733e65959d681e5b88786eea23


Parallelism

the problem is embarrassingly parallel, but the implementation is embarrassingly not parallel.
So this PR remedies that, hopefully.

The search algorithm has been rewritten. It's parallelizable now, but somehow less performant than what we had before. Need to figure out why.

Clippy is complaining about unused functions like optimize; I don't know yet whether we'll want to actually call a function like that or whether the search algorithms should really be implemented as iterators instead. Might be cleaner.
Another thing clippy is complaining about is some debug logging which ought to be removed before the merge

works on my machine 🤷

Git's a mess since I did a merge, I'll see if i can rebase & squash some of it together later

The checks all pass now. The branch is ready to merge in. But I want to characterize the performance before I do.


Cookies are not handled

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure it has not already been reported

Fastify version
3.17.0
Plugin version
1.4.4
Node.js version
14.x
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
Lambda OS
Description
In the lamda event cookies are in the cookies property and not in header. See:
{
...
"cookies":["FOO=Bar"]
...
}

But in the current state we don't map this value. Also in the current context i'm using API Gateway V2
Steps to Reproduce
Send cookies within Api Gateway v2
Expected Behavior
No response

thank you @zekth, it's included in v1.5.0


Admin shell 38

Closes #38 by @entwanne
Just creating the PR for readability.
Successful PR Checklist:

[ ] Tests
[ ] Documentation (optionally: run spell checking)
[ ] Had a good time contributing? (if not, feel free to give some feedback)

@entwanne would you mind re-opening a draft PR ? I'm using the "My PRs" view a lot and this one is cluttering it a bit :)


giphy.com - Gif's not responsive

Hi, thank you for your amazing theme!
I have a little bug. On the standart template "casper" i can integrate gifs in full mode but in fizzy not.
look at this screenshots :)
https://imgur.com/a/fi8DvAy
The Code for the gifs:

via GIPHY

Hey, when I copy the code you provided into the editor as an HTML block, it simply shows a small gif.
Probably you should work on with the code and see what might be changed .
I cannot replicate your problem, please provide with more detail.


support for exporting scenarios?

Specifically the "ts" files I still can't find a way to export with the "dummy bones" (I call them that because they exist in mltd but apparently not in the model)
Most scenarios have one or more "ts" files that contain the "extras" of the sescenario, so when exporting them with asset studio the "spot lights" have all the lights set to one bone instead of having one bone per light.
(As I wrote this I remembered that a long time ago I read in the readme a "stage editor: wip" and afterwards it disappeared)

The scenes are basically static. Some objects have simple scripts attached. The scripts control simple transforms (usually translation and rotation). But until now there is no sign of complex animations in the scenes.
I think this is what you can do: use Asset Studio to export them into separate objects, and reassemble them in the MMD scene.
The removed project was supposed to be a scenario editor. A scenario (not a scene) is the control data of specific MV aspects, like lighting, character animations, effects, screens, cameras, object animations, etc. Later I found it simply not a good idea, because there is no easy way to replace the modified data into original files, and designing a new format (with maintenance) is just too much work to do. So the project was removed.


Molar Mass Calculator

Enter calculator name -
Molar Mass Calculator
Describe calculator functionality -
The Molar Mass Calculator takes the amount of the substance in grams ( could be multiples or sub-multiples of the unit ) and moles of that substance and calculates the molar mass of that substance with the standard relation.
The inputs and outputs are inter-connected, if the user tries to change one of them, the other two values maintain the correct dependency and change along with it.
In case you face a problem in calculating the number of Moles, you can simply refer to the Moles Calculator in the repository.
Under which category you wish to place it -

[ ] Computer Science
[ ] Mathematics
[ ] Physics
[x] Chemistry
[ ] Biology
[ ] Art
[ ] Finance
[ ] Scientific
[ ] Health
[ ] Sports
[x] Let project owner decide
[ ] Suggest a new category - (Answer here)

@SarthakKeshari kindly assign me this issue

@SarthakKeshari  please assign this issue to me

Hey @Zinc-ion,
Assigned.
You may contribute your code under the folder path -
calc_for_everything\calculators\src\chemistry\molarMassCalc
Issue completion deadline - 31st Oct 05:00:00 pm IST
NOTE - In case the issue completion deadline is not met, the issue will be assigned to a new participant


Convert Functional API to Model Subclassing with Normalization Layers

Could anyone please teach me how to convert the Functional API to Model subclassing in this TensorFlow Official Tutorial? I suppose an elegant chuck of code should be what combines the Normalization layer with the remaining layers. I went through the tutorial, trying to reproduced the process to fit my purpose. I have only 1 predictor (age) and 1 target variable (se), both are continues variables.
Here's how I refactored the code:
from tensorflow.data import Dataset
from tensorflow.keras import Input
from tensorflow.keras.backend import clear_session
from tensorflow.keras.layers import Normalization

def df_to_dataset(dataframe, batch_size, shuffle=True):
  dataframe = dataframe.copy()
  labels = dataframe.pop("se")
  ds = Dataset.from_tensor_slices((dict(dataframe), labels))
  if shuffle:
    ds = ds.shuffle(buffer_size=len(dataframe))
  ds = ds.batch(batch_size)
  ds = ds.prefetch(batch_size)
  return ds

def get_normalization_layer(name, dataset):
  normalizer = Normalization(axis=None)
  feature_ds = dataset.map(lambda x, y: x[name])
  normalizer.adapt(feature_ds)
  return normalizer

test_ds = df_to_dataset(test, batch_size=5, shuffle=False)

[(train_features, label_batch)] = test_ds.take(1)
print(f"Every Feature: {list(train_features.keys())}")
print(f"A batch of ages: {train_features['age']}")
print(f"A batch of targets: {label_batch}")

batch_size = 128
train_ds = df_to_dataset(train, batch_size=batch_size)
val_ds = df_to_dataset(val, batch_size=batch_size, shuffle=False)
test_ds = df_to_dataset(test, batch_size=batch_size, shuffle=False)

all_inputs = []
encoded_features = []

# Numeric features
clear_session()
for header in ["age"]:
  numeric_col = Input(shape=(1, ), name=header)
  normalization_layer = get_normalization_layer(header, train_ds)
  encoded_numeric_col = normalization_layer(numeric_col)
  all_inputs.append(numeric_col)
  encoded_features.append(encoded_numeric_col)

Below the Functional API part, which worked as expected, like in the tutorial:
import tensorflow as tf
from tensorflow import math
from tensorflow.keras import Model, Input
from tensorflow.keras.backend import clear_session
from tensorflow.keras.losses import Loss
from tensorflow.keras.optimizers import Adam
from tensorflow.keras.layers import Dense, Normalization, Concatenate, Dropout
from tensorflow.keras.callbacks import ReduceLROnPlateau, EarlyStopping

class QuantileLoss(Loss):

  def __init__(self, quantiles):
    super().__init__()
    self.quantiles = tf.convert_to_tensor(quantiles)

  def call(self, y_true, y_pred):
    y_true = tf.convert_to_tensor(y_true)
    y_pred = tf.convert_to_tensor(y_pred)
    errors = math.subtract(y_true, y_pred)
    loss = math.reduce_mean(
        math.maximum(
            math.multiply(self.quantiles, errors),
            math.multiply(
                math.subtract(
                    self.quantiles, 1
                ),
                errors
            )
        ),
        axis=-1
    )
    return loss

clear_session()

earlystopping = EarlyStopping(patience=10)
lr_schedule = ReduceLROnPlateau(
    patience=5,
    monitor="val_loss",
    verbose=1
)
callbacks = [lr_schedule, earlystopping]
quantiles = [0.021, 0.157, 0.5, 0.841, 0.977, 0.998]
all_features = Concatenate()(encoded_features)
print(all_features.shape)
x = Dense(256, activation="selu")(all_features)
x = Dropout(0.3)(x)
x = Dense(64, activation="selu")(x)
output = Dense(len(quantiles))(x)
model = Model(all_inputs, output)
quantile_loss = QuantileLoss(quantiles)
model.compile(optimizer=Adam(learning_rate=0.001), loss=quantile_loss)
history = model.fit(train_ds, validation_data=val_ds, epochs=100, callbacks=callbacks)

I was trying to refactor the Functional implementation to make the code look more elegant.
class QuantileRegressor(Model):

  def __init__(self, quantiles, hidden_units):
    super().__init__()
    self.quantiles = quantiles
    self.concatenate = Concatenate()
    self.normalizer = Normalization(axis=None)
    self.hidden_dense = Dense(hidden_units, activation="selu")
    self.dropout = Dropout(0.3)
    self.output_dense = Dense(len(quantiles))

  def call(self, inputs):
    self.normalizer.adapt(inputs["age"])
    # The line above gave me an error!
    # Is it a good idea to place encoded_features, all_inputs here?
    # inputs here seemed to be a dictionary.
    return None

earlystopping = EarlyStopping(patience=10)
lr_schedule = ReduceLROnPlateau(
    patience=5,
    monitor="val_loss",
    verbose=1
)
callbacks = [lr_schedule, earlystopping]
quantiles = [0.021, 0.157, 0.5, 0.841, 0.977, 0.998]
hidden_units = 256
clear_session()
model = QuantileRegressor(quantiles, hidden_units)
quantile_loss = QuantileLoss(quantiles)
model.compile(optimizer=Adam(learning_rate=0.001), loss=quantile_loss)
history = model.fit(train_ds, validation_data=val_ds, epochs=10, callbacks=callbacks)

self.normalizer.adapt(inputs["age"]) in the call method resulted in
RuntimeError: in user code:

    /usr/local/lib/python3.7/dist-packages/keras/engine/training.py:853 train_function  *
        return step_function(self, iterator)
    <ipython-input-24-3f4f9f8eec72>:18 call  *
        self.normalizer.adapt(inputs["age"])
    /usr/local/lib/python3.7/dist-packages/keras/engine/base_preprocessing_layer.py:230 adapt  **
        _disallow_inside_tf_function('adapt')
    /usr/local/lib/python3.7/dist-packages/keras/engine/base_preprocessing_layer.py:591 _disallow_inside_tf_function
        raise RuntimeError(error_msg)

    RuntimeError: Detected a call to `PreprocessingLayer.adapt` inside a `tf.function`. `PreprocessingLayer.adapt is a high-level endpoint that manages its own `tf.function`. Please move the call to `PreprocessingLayer.adapt` outside of all enclosing `tf.function`s. Note that you can call a `PreprocessingLayer` directly on `Tensor`s inside a `tf.function` like: `layer(x)`, or update its state like: `layer.update_state(x)`.

That's why I am asking the question. What is the standard or preferred way using Model Subclassing, when adapting a Normalization layer?

@JyotiPDLr The tutorial seems to work fine, please have a look at the gist.  Thank you!


Integrate with Polars rust dataframe

Hi there,
I am currently working with dataframes in Polars and was wondering about the following:

I have a dataframe in my program. How can I insert each row into the sql database through sqlx?
I want to query the database. How can I read the results into the dataframe?

Thanks

This would be similar to pandas.to_sql

I'm just trying to familiarise myself with the Rust ecosystem and came across this, but this would be a feature request for polars. pandas.to_sql is handled by pandas itself and, to my knowledge, requires no special functionality on any of the part of the SQL bindings. It wraps around SQLAlchemy.
For what it's worth (and only passingly relevant to this), I never use pandas.to_sql because I'm at the mercy of their implementation. For postgresql they were at the mercy of executemany for a long time which was implemented badly. It was always faster to create an in-memory CSV and use COPY in that case. pandas now supports that, but I don't want to be reliant on their implementation of a generic to_sql() method.

I see. I have created a PR on their repo as well.
https://github.com/pola-rs/polars/issues/3540


feat: chapter 18 - localization

Chapter 18: Localization
This pull request adds a new feature to the application.
Topics Covered

Localizing Resources
Configuration Qualifiers
Testing Alternative Resources

How to Test
To test the new feature, you can do the following:

Clone the repository.
Install the dependencies.
Run the application.
The new feature should be available.

Screenshots

Known Issues
There are no known issues with this pull request.
References
Reviewers
Thanks!

Looks good to me.


Create a new repo for Cosmos REST implementation

We should evaluate split cosmos API REST code into another repository, it should be easier and faster to make changes to it and the core application.
It also may help to lower coupling with the core.

Already did the API in the same repo


python311Packages.yalexs: 1.8.0 -> 1.9.0

Diff: https://github.com/bdraco/yalexs/compare/refs/tags/v1.8.0...v1.9.0
Changelog: https://github.com/bdraco/yalexs/releases/tag/v1.9.0
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.august
python310Packages.yalexs
python310Packages.yalexs.dist
python311Packages.yalexs
python311Packages.yalexs.dist


Add school SZ-Ybbs

Institution/School Name
SZ-Ybbs
Instiution/School Website
https://www.sz-ybbs.ac.at/
Email Users
Please place an x between the square brackets if yes

[x] Students
[x] Academic/Teaching Staff
[x] Other/Support Staff
[ ] Alumni

Education Levels
Please place an x between the square brackets if yes

[ ] Post-graduate research
[ ] Graduate School
[ ] College (University) or Undergraduate School or equivalent
[ ] Community College or equivalent
[x] High School or equivalent
[ ] Elementary School or equivalent

@davidblaimauer Pull request merged. Thank you!


Medical specialist examination mirror evaluation branch

Need several examination terms. Possibly a pattern?

Possibly an examination by body part branch (new Uberon pattern) too


FM/PM Gates in OpenPulse

What is the expected behavior?
Currently, OpenPulse (and Qiskit Pulse's implementation https://arxiv.org/pdf/2004.06755.pdf) only supports playback of AM (amplitude modulation) waveforms on a given Channel. It does allow for e.g. SetFrequency/ShiftPhase/etc. instructions, but that only allows for discrete frequency and phase modulation, not continuous.
There has been significant theoretical & experimental work on using FM (Frequency Modulation)/PM (Phase Modulation) gates for quantum computing, and each type of modulation has its own use case. Small sampling of papers from a quick arXiv search (encompassing pretty much all quantum platforms):

https://arxiv.org/pdf/2008.05670.pdf
https://arxiv.org/pdf/1908.08003.pdf
https://arxiv.org/pdf/1905.09292.pdf
https://arxiv.org/ftp/arxiv/papers/1712/1712.05261.pdf
https://arxiv.org/pdf/1706.06570.pdf

Ideally, as a platform-independent waveform specification language, OpenPulse/Qiskit Pulse should support continuous Frequency/Phase Modulation just as it does Amplitude Modulation.
What would need to be modified

Channel abstractions. They might need independent sub-channels for Frequency/Amplitude/Phase.
Schedule Drawing. Some way of showing how frequency & phase vary over time (not just amplitude) would be needed.
Schedule -> PulseQObj conversion. The low-level PulseQObj representation would probably need to be changed
PulseQObj JSON schema.
OpenPulse Backend schema. Some method of specifying what modulation types are available on a given channel/backend would probably be required.

What are the expected issues?
I assume that there are compatibility issues with the IQX/IBMQ waveform hardware in supporting continuous FM/PM gates (hence why the frequency & phase modulation is currently discrete).

I think this is a great idea for an extension platform-independent capabilities of OpenPulse. As you note if added to Qiskit our hardware would only support the instruction if we added support for it, however, that should not limit what Qiskit is capable of support.

Channel abstractions. They might need independent sub-channels for Frequency/Amplitude/Phase.
Schedule Drawing. Some way of showing how frequency & phase vary over time (not just amplitude) would be needed.

This is the blocker I currently see as well. Currently, we only support executing a single instruction per-channel at a time (instructions are not allowed to overlap). This is tricky as while we can think of AM/FM/PM as three different ways of emiting a pulse, at the end of the day they all consume the same physical resource. We should brainstorm how this could be represented and implemented in a way that doesn't break backward compatibility.
Some ideas:

Include a separate type of Play instruction, eg., PlayFM, PlayPM. This would automatically enforce only a single type of pulse that could be played on a physical resource at a time, be easy to implement, however, it would be very inflexible.
Introduce new channels deriving from PulseChannel, eg., AMChannel(pulse_channel), FMChannel(pulse_channel), and PMChannel. These could then either be mapped to the original PulseChannel by the pulse compiler (see this for an example) before being emitted to hardware, eg., the AM/FM/PMChannels mapping to a single PulseChannel could be compiled into a single long Play(waveform, channel) in the worst case. If the backend supported these channels natively it could consume them in its own serialization format. This opens up the question of what instructions these new channels would support, eg., SetAmplitude, on an FM/PMChannel?
Changing to a linearly times instruction representation and execution model, eg., playing an AM pulse and a FM pulse one after the other would allow the hardware to execute them one after the other as it is aware that these pulses affect different sub-channels (a major refactor).

Any thoughts would be much appreciated.

@taalexander thanks for the response. I wasn't sure if this belonged here or in https://github.com/qiskit/rfcs and wanted to gauge interest first.
For context, my interest in this is because I have a hardware waveform generator that has individual & continuous control of the AM, FM, and PM channels, so describing waveforms in OpenPulse as essentially AM-only reduces its capabilities.
Personally, I would envision that only one instruction per MODULATION channel would be permitted. For example, consider an AWG channel. Each of AM, FM, PM can be modulated simultaneously and continuously, though they output to the same channel. This capability currently can't be expressed in OpenPulse.
Regarding ideas above:

I would lean away from this. I will expand more in 2.
I envision something more like this. So a continuous FM gate could look something like

import qiskit.pulse as qp
with qp.build() as fm_gate_schedule:
    fm_channel = qp.FMChannel(channel_index)
    am_channel = qp.AMChannel(channel_index)
    qp.set_frequency(qubit_lo_freq=5.6 GHz, fm_channel)
    qp.play(qp.Constant(100, 1.0), am_channel)
    qp.play(qp.Gaussian(100 dt, +0.1 GHz, sigma=10), fm_channel)

   *  ``Play()`` might then run the checks for scaling on different channels (that is, while AM channels can obviously scale ``abs(amp) in [0, 1]``, frequency can scale e.g. ``[-100 GHz, +100 GHz]``. This could be implemented by each waveform/``ParametricPulse`` having a ``check_am()`` or ``check_fm()`` method.
   * As for interpreting these channels, I wouldn't see the user (submitter)-end compiler doing much with these pulses, other than validating that they match the capabilities of the backend. That is, they would be submitted to the backend as separate channels, and it would be up to the backend to combine them into the single output channel as appropriate (trivial for the above AWG example). Obviously, some ``PulseBackendConfiguration`` values to specify capabilities would be required.

While this would be a clean representation, it doesn't encompass all existing gate schemes. For example, see Fig. 3a of https://arxiv.org/pdf/1905.10421.pdf which simultaneously modulates AM & FM. So while this would be a step in the right direction, I don't know if the major refactoring that would require is worth the cost.

The discussion above is interesting and did not reach a conclusion, but I'm going to close this feature request for now due to lack of continued interest.  I believe qiskit.pulse has changed quite significantly since this discussion, so not everything said may still apply (I'm not an expert on the pulse module), and further work on OpenPulse as part of the OpenQASM 3 effort may also have affected things.
I'll close this now as I don't believe it's something that any maintainer could commit to implementing or shepherding a full project through, but that's not to say discussion on it needs to stop.  If there's more to say, or someone willing to put in the time to design this addition properly in collaboration with other interested parties, please open a new issue for discussion.


SSL wrong version number.

Greetings,
I have an issue on my local build for development where i cannot get the application to properly connect to the DB because of a SSL issue.
I keep getting this issue at:
 ⨯ TypeError: fetch failed
    at async login (./src/lib/auth/actions.ts:64:26)
Cause: [Error: 00F88DA8327F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
] {
  library: 'SSL routines',
  reason: 'wrong version number',
  code: 'ERR_SSL_WRONG_VERSION_NUMBER'
}

Problem is, this is a completely fresh clone from github, the .env is the only edited part.
How can i solve this error?

@iamtouha I forgot to add some details.
For local development i use a locally hosted mysql server, so basically the project is currently completely cut off from the web.
apparently this bug is already known within drizzle and has a workaround for, however this did not help me.
Refer to this Issue for further details.

Hi @Fr3akyMurk , have you tried removing ?ssl={"rejectUnauthorized":true} part from DATABASE_URL for local development?

Hello, @iamtouha
Yeah i have removed it and tried many different ways to connect to the db but it always results in an error.
I've tried ?allowPublicKeyRetrieval=true and &useSSL=false
Although i am unsure if &useSSL=falsedoes any change, it certainly doesn't when used in practice.
My connection string looks like this, it's quite similar to planetscales url.
mysql://<user>:<password>@localhost:3306/luciatest?allowPublicKeyRetrieval=true&useSSL=false

Okay so, i did some digging.
I played around and changed a few things.
More prominently, i checked the migration code and applied it to the index file.
This seems to resolve the connection issues but then the code starts to complain about an await statement in a top level module.
import mysql from "mysql2/promise";
//import { drizzle } from "drizzle-orm/planetscale-serverless";
import { drizzle } from "drizzle-orm/mysql2";
//import { Connection } from "@planetscale/database";

import { env } from "@/env";
import * as schema from "./schema";

//export const connection = new Connection({ url: env.DATABASE_URL });
//export const db = drizzle(connection, { schema });

const connection = await mysql.createConnection(env.DATABASE_URL);
export const db = drizzle(connection, { schema, mode: "default" })

Figured this information would be better off to be sent to you considering you made majority of the code.
Unhandled Runtime Error

Error: await is only valid in async functions and the top level bodies of modules
Call Stack
(action-browser)/./src/server/db/index.ts
/home/mark/nextjs-typescript-starter/next-lucia-auth/.next/server/app/(auth)/login/page.js (904:1)

mysql.createConnection is not an async function. please remove the await before the function call and see if the error persists.

That is true, ```mysql.createConnection``

dang! use await before mysql.createConnection.
which node version are you using? also, what is set on your compileropsions.taget value in tsconfig file?

Alright, i have reverted to the code that was posted.
I use node 20.9.0, i am aware that newer versions are available but right now i doubt it's relevant.
I think you meant compilerOptions.target, to answer, it's currently set at "es2022".
I also thought a bit about it, but it could be that the connection still fails but we don't know that because the code running fails before the connection even happens, i will have to check mysql logs if i want to know if the app even connects.

@Fr3akyMurk  No. drizzle connects smoothly with planetscale using DB_URL

Well yeah, and so does it with any local databases, however this time it just has issues.
To be fair i have never used mysql with connectionsteings in projects before so i don't really know what the issue may be.

I do not understand anything with this.
It is not a problem on my system only as i have tried this on my main computer, my laptop and a vm.
The error persists either way.
There is little to no documentation on this error and how to fix it.
Using Planetscales link to connect does not work because i get the same SSL issue (different issue but still SSL related)
How do you develop the project? Locally or somehow in the cloud?
I am unaware of any way to develop directly in the cloud.

Could you please spare some time to create a PR with the changes you made? I will add these changes to a new branch so that someone facing the same problem will benefit.

Alright, i will look into it.

I will not add my changes, those changes are not reasonable.
However Kinfish (the other contributor) found a much better solution, he uses pg drivers instead of mysql promise based drivers, i will look into that and if it works i will open a pr with that solution for you to view.
My edits are too dramatic for something so simple.


Running the code example in instruction

HI,
I'm new to this library so I installed on my website and created a page and copied the code to create a simple PDF from a url and save it on the server but when I run the page it gives me a blank page and no file is saved. Any suggestions?
<?php
require('wkhtmltopdf/vendor/autoload.php');
use mikehaertl\wkhtmlto\Pdf;
// You can pass a filename, a HTML string, an URL or an options array to the constructor
$pdf = new Pdf('https://www.bnfgallery.ir/mobl/listresid.php');

// On some systems you may have to set the path to the wkhtmltopdf executable
// $pdf->binary = 'C:\...';

if (!$pdf->saveAs('https://www.bnfgallery.ir/mobl/1.pdf')) {
    $error = $pdf->getError();
    // ... handle error here
}

Is wkhtmltopdf installed and executable?
Can you execute it from PHP e.g. with a simple system('wkhtmltopdf')?
Have you checked your server logs? Is there any error?
Have you tried with a simpler example i.e. not using an external URL but some static HTML content?

And most obvious: Is there something in $error?

I just uploaded the download to my server and used the codes, also tried the internal link like "residkala.php", didn't make any difference

And most obvious: Is there something in $error?

the page is blank and shows nothing!

And most obvious: Is there something in $error?

Could not run command wkhtmltopdf 'listresid.php' '/tmp/tmp_wkhtmlto_pdf_jne4BY.pdf'

I'm sorry, but I can not really help you any further. It could be a certain server configuration or something similar. There are too many possible reasons but this is out of the scope of our library. It works fine with an unrestricted server. You need to do your own research on this.
Also again try with a string, not a URL (also not another PHP page) as I suggestd in step 4 above.

Have you looked at the error message above I sent you?

Hello again,
First off, I would like to thank you for your great work, it is much appreciated. Secondly, I changed the temp folder permission to 777 and stil get the same error. I was wondering if there would be a way to change the tmp directory to some newly created folder. Regards

https://github.com/mikehaertl/phpwkhtmltopdf#wrapper-options


Fix: Typo

This pull request

[x] fixes a typo

💁♂ Spotted while investigating #8083.
Running
git grep -i 'v-prefix' | wc -l

on current main yields
      13

and running
git grep -i 'v prefix' | wc -l

on current main yields
      13

as well.

Thanks to you!


dynamically set current rating if it exists

this patch initialize the rating form with the proper value if authenticated user already rate a content.

Awesome, thank you.


Adding a local storage workflow

Adding a workflow node for the local storage engine.

Merged.
Thanks for your contribution !


Update scala-library, scala-reflect to 2.12.16

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

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

Files still referring to the old version number
The following files still refer to the old version number (2.12.11).
You might want to review and update them manually.
.travis.yml

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #206.


New test to change exercise and solution for it.

There is a missing case when solution involves multiples currencies.
I added a new test and I change the solution for pass new testcase.
iex(2)> Change.generate(21, [10, 2, 5])
{:ok, %{2 => 3, 5 => 1, 10 => 1}}

@weapp Thanks for the PR!
This exercise actually has a standardized set of tests that should be implemented in all language tracks (which you can see here). Want to open a PR adding this test case there first? If it's added then we can go ahead and add it in here, but for consistency's sake we always try and just implement what's in that cannonical_data.json file in each language track.

Ok, sorry @devonestes, I didn't know this file.
But, I think that the current tests don't match with this .json. I should change all tests?

@weapp Absolutely! If you see inconsistencies between our implementation and any of those cannonical_data.json files, pull requests updating our implementation are much appreciated!!
And I think your other test is a good one to add, by the way. It should just be discussed and added as part of that cannonical_data.json first 😉


Update .gitignore

No pressure on merging the .gitignore, the message of what I want to do with this file just started getting a bit annoying when switching branches, and I like to have a justMyCode: false flag (see below) so that I can use a locally pip-installed version via flit install --pth-file
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
        },
        {
            "name": "Python: Installed Packages",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": false,
            "env": {
                "PYTEST_ADDOPTS": "--no-cov"
            }
        }
    ]
}

thanks @sgbaird !!


chore(requirements): update dependencies and CI

Updates the dependencies to
cloudevents==1.7.0
flake8==5.0.4
pytest==7.2.0
Flask==2.2.2

Also adds CI runs on pull requests, drops support for Python 3.6 and
adds support for 3.9 and 3.10.
/kind chore
Signed-off-by: Lance Ball<EMAIL_ADDRESS>

/lgtm


[TextField] Fix controlled input warning in React 15

Problem Description
I'm getting this error after upgrading to React 15 and MUI 0.15.0-beta.1
TextField is changing a uncontrolled input of type text to be controlled. Input elements should not switch from uncontrolled to controlled (or vice versa)

Versions

Material-UI: 0.15.0-beta.1
React: 15.0.1
Browser: Google Chrome Canary (Version 52.0.2712.0 canary (64-bit))

@maticrivo Please review your use of the input -- this is not a material-ui issue

@maticrivo more info: https://github.com/facebook/react/pull/5864

Is this going to be fixed in 2.0 or do we need a fix before that is done?

it would be nice to have it fixed

Mmmm... any ideas on how avoid it?
Am I doing something wrong?
<TextField type="text" fullWidth={ true } label="Project" value={ project } onChange={ event => this.setState({ project: event.target.value }) } />

@abelosorio I also faced this just now. Seems that here's how things should be done in the new API:
  <TextField
    value={ project }
-  onChange={ handleChange }
+  InputProps={{
+    onChange: handleChange,
+  }}
  />

Thanks @kachkaev, I'll try it.

I'd like to get this fixed to, I have the same issue, but I do not understand @abelosorio soution, could you explain more?

@rsweeney21 exactly!
I changed my initial state in Redux for two Selects from
const initialState = {
  clientData: null,
  year: null,
  month: null
};

to
const initialState = {
  clientData: null,
  year: '',
  month: ''
};

where year and month are the values for the Select components.
This warning then disappears.


Support global vars, volumes and volumeMounts for workspace statefulsets within helm chart

Hello!

Support global vars, volumes and volumeMounts for workspace statefulsets from the operator being supported in the helm chart templates.
This is really an ask that should require two changes:

Add helm templating to create a place for global values or a flag to have workspace pods inherit envs,volumes and volumeMounts from the operator config.
Make the operator deploy statefulsets using additional global configs in addition to what comes from the workspaceTemplate with the stack configs.

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Affected area/feature

I take this as a feature request to provide for global customization of the Workspace. I suppose the operator could have a cluster-scoped and/or namespace-scoped configuration object, providing a default workspace template (and would be merged with the stack's own template).
A possible workaround would be to use a mutating webhook, to apply some defaults into the Stack object or directly into the Workspace object.
@drduker to help make the case for this feature, could you share some specific use cases that you have in mind?

Use case is an offline deployment where you have local libraries that require netrc variables set.  This vars need to go onto the workspace pods.  Could use kyvero yes.  I’m setting the values per stack in the workspace template values now.  But it’s redundant and was not quick to find the usage for that.  Had to look up spec and play around with that.


Create WidgetTester.ensureVisible(Finder) closes (#8185)

This is just a shorthand for
Scrollable.ensureVisible(tester.element(finder))

I signed it


Button tooltips are allowed to go off-screen.

https://i.imgur.com/AYVuwmI.png

I see that this is still an issue; My buttons went so far offscreen, I cannot relocate, do you know a fix?


Coverity scan reports four issues in pugixml code

Coverity scan reports four issues in pugixml code, all of medium impact. These are:
Dereference after null check
Refers to code where a pointer or reference is checked against null or assigned null and then later dereferenced. Dereferencing a null pointer leads to undefined behavior, which is usually a program crash. Coverity reports this error in three cases:

Checking against NULL and then dereferencing on a path on which it was null.
Assigning NULL and then taking a path on which the value has not changed.
Dereferencing the return value from dynamic_cast without first checking it against NULL. If you know that the value will always be non-null, then you can use static_cast to avoid a defect report.

Coverity reports two instances of this error in pugixml.cpp:
1. Issue in line 4691:
4679        PUGI__FN xml_parse_result load_buffer_impl(xml_document_struct* doc, xml_node_struct* root, void* contents, size_t size, unsigned int options, xml_encoding encoding, bool is_mutable, bool own, char_t** out_buffer)
4680        {
4681                // check input buffer
    1. Condition !contents, taking true branch.
    2. var_compare_op: Comparing contents to null implies that contents might be null.
    3. Condition size, taking false branch.
4682                if (!contents && size) return make_parse_result(status_io_error);
4683
4684                // get actual encoding
4685                xml_encoding buffer_encoding = impl::get_buffer_encoding(encoding, contents, size);
4686
4687                // get private buffer
4688                char_t* buffer = 0;
4689                size_t length = 0;
4690
    CID 117652 (#1 of 1): Dereference after null check (FORWARD_NULL)4. var_deref_model: Passing null pointer contents to convert_buffer, which dereferences it.
4691                if (!impl::convert_buffer(buffer, length, buffer_encoding, contents, size, is_mutable)) return impl::make_parse_result(status_out_of_memory);
4692

Details on how the null ptr is dereferenced:
2245        PUGI__FN bool convert_buffer(char_t*& out_buffer, size_t& out_length, xml_encoding encoding, const void* contents, size_t size, bool is_mutable)
2246        {
2247                // fast path: no conversion required
    1. Condition encoding == pugi::encoding_utf8, taking false branch.
2248                if (encoding == encoding_utf8)
2249                        return get_mutable_buffer(out_buffer, out_length, contents, size, is_mutable);
2250
2251                // source encoding is utf16
    2. Condition encoding == pugi::encoding_utf16_be, taking true branch.
2252                if (encoding == encoding_utf16_be || encoding == encoding_utf16_le)
2253                {
2254                        xml_encoding native_encoding = is_little_endian() ? encoding_utf16_le : encoding_utf16_be;
2255
    3. Condition native_encoding == encoding, taking false branch.
    4. deref_parm_in_call: Function convert_buffer_generic dereferences contents.
2256                        return (native_encoding == encoding) ?
2257                                convert_buffer_generic(out_buffer, out_length, contents, size, utf16_decoder<opt_false>()) :
2258                                convert_buffer_generic(out_buffer, out_length, contents, size, utf16_decoder<opt_true>());
2259                }
2260

2. issue in line 10855:
10855                void optimize(xpath_allocator* alloc)
10856                {
     1. Condition this->_left, taking true branch.
10857                        if (_left)
10858                                _left->optimize(alloc);
10859
     2. Condition this->_right, taking false branch.
     3. var_compare_op: Comparing this->_right to null implies that this->_right might be null.
10860                        if (_right)
10861                                _right->optimize(alloc);
10862
     4. Condition this->_next, taking true branch.
10863                        if (_next)
10864                                _next->optimize(alloc);
10865
     CID 63267 (#1 of 1): Dereference after null check (FORWARD_NULL)5. var_deref_model: optimize_self dereferences null this->_right. [show details]
10866                        optimize_self(alloc);
10867                }

Details on how the null ptr is dereferenced:
10869                void optimize_self(xpath_allocator* alloc)
10870                {
10871                        // Rewrite [position()=expr] with [expr]
10872                        // Note that this step has to go before classification to recognize [position()=1]
     1. Condition this->_type == pugi::impl::<unnamed>::ast_filter, taking false branch.
     2. Condition this->_type == pugi::impl::<unnamed>::ast_predicate, taking false branch.
10873                        if ((_type == ast_filter || _type == ast_predicate) &&
10874                                _right && // workaround for clang static analyzer (_right is never null for ast_filter/ast_predicate)
10875                                _right->_type == ast_op_equal && _right->_left->_type == ast_func_position && _right->_right->_rettype == xpath_type_number)
10876                        {
10877                                _right = _right->_right;
10878                        }
10879
10880                        // Classify filter/predicate ops to perform various optimizations during evaluation
     3. Condition this->_type == pugi::impl::<unnamed>::ast_filter, taking false branch.
     4. Condition this->_type == pugi::impl::<unnamed>::ast_predicate, taking false branch.
10881                        if ((_type == ast_filter || _type == ast_predicate) && _right) // workaround for clang static analyzer (_right is never null for ast_filter/ast_predicate)
10882                        {
10883                                assert(_test == predicate_default);
10884
10885                                if (_right->_type == ast_number_constant && _right->_data.number == 1.0)
10886                                        _test = predicate_constant_one;
10887                                else if (_right->_rettype == xpath_type_number && (_right->_type == ast_number_constant || _right->_type == ast_variable || _right->_type == ast_func_last))
10888                                        _test = predicate_constant;
10889                                else if (_right->_rettype != xpath_type_number && _right->is_posinv_expr())
10890                                        _test = predicate_posinv;
10891                        }
10892
10893                        // Rewrite descendant-or-self::node()/child::foo with descendant::foo
10894                        // The former is a full form of //foo, the latter is much faster since it executes the node test immediately
10895                        // Do a similar kind of rewrite for self/descendant/descendant-or-self axes
10896                        // Note that we only rewrite positionally invariant steps (//foo[1] != /descendant::foo[1])
     5.  Condition this->_type == pugi::impl::<unnamed>::ast_func_translate, taking false branch.
10910                        if (_type == ast_func_translate &&
10911                                _right && // workaround for clang static analyzer (_right is never null for ast_func_translate)
10912                                _right->_type == ast_string_constant && _right->_next->_type == ast_string_constant)
10913                        {
10914                                unsigned char* table = translate_table_generate(alloc, _right->_data.string, _right->_next->_data.string);
10915
10916                                if (table)
10917                                {
10918                                        _type = ast_opt_translate_table;
10919                                        _data.table = table;
10920                                }
10921                        }
10922
10923                        // Use optimized path for @attr = 'value' or @attr = $value
     7. Condition this->_type == pugi::impl::<unnamed>::ast_op_equal, taking true branch.
     8. Condition this->_left, taking true branch.
     9. Condition this->_left->_type == pugi::impl::<unnamed>::ast_step, taking true branch.
     10. Condition this->_left->_axis == pugi::impl::<unnamed>::axis_attribute, taking true branch.
     11. Condition this->_left->_test == pugi::impl::<unnamed>::nodetest_name, taking true branch.
     12. Condition !this->_left->_left, taking true branch.
     13. Condition !this->_left->_right, taking true branch.
     14. deref_parm: Directly dereferencing parameter this->_right.
10924                        if (_type == ast_op_equal &&
10925                                _left && // workaround for clang static analyzer (_left is never null for ast_op_equal)
10926                                _left->_type == ast_step && _left->_axis == axis_attribute && _left->_test == nodetest_name && !_left->_left && !_left->_right &&
10927                                (_right->_type == ast_string_constant || (_right->_type == ast_variable && _right->_rettype == xpath_type_string)))
10928                        {
10929                                _type = ast_opt_compare_attribute;
10930                        }

Inferred misuse of enum
An enumeration value for one enum type may be misinterpreted as a different, unrelated enumeration value in a different type. An enumeration value in one type may have no meaningful interpretation in another enum type, leading to a range of logic errors.
Coverity reports two instances of this error in pugixml.cpp:
3. issue in line 10086:
10082
10083                        bool once =
     first_enum_type: Enum type for _test is established as pugi::impl::<unnamed>::nodetest_t here.
10084                                (axis == axis_attribute && _test == nodetest_name) ||
10085                                (!_right && eval_once(axis_type, eval)) ||
     CID 63229 (#1 of 1): Inferred misuse of enum (MIXED_ENUMS)mixed_enums: Mixing enum types pugi::impl::<unnamed>::nodetest_t and pugi::impl::<unnamed>::predicate_t for _test.
10086                                (_right && !_right->_next && _right->_test == predicate_constant_one);
10087

4. issue in line 10926:
10924                        if (_type == ast_op_equal &&
10925                                _left && // workaround for clang static analyzer (_left is never null for ast_op_equal)
     CID 124553 (#2 of 2): Inferred misuse of enum (MIXED_ENUMS)mixed_enums: Mixing enum types pugi::impl::<unnamed>::predicate_t and pugi::impl::<unnamed>::nodetest_t for _test.
10926                                _left->_type == ast_step && _left->_axis == axis_attribute && _left->_test == nodetest_name && !_left->_left && !_left->_right &&
10927                                (_right->_type == ast_string_constant || (_right->_type == ast_variable && _right->_rettype == xpath_type_string)))
10928

Hope this helps. If need more info, feel free to ask. Thank for developing and maintaining pugixml. Great code!

Just to confirm - all of these are false-positives. I've submitted a change that should fix one of them. Not sure how to cleanly work around other issues yet.

Coverity supports source code annotations to mark code in which a particular issue should be ignored. I have not much knowledge about Coverity but one way to deactivate a false positive is to add a comment line before the statement causing the false positive (see the Coverity manual, section 6.1.8. Suppressing False Positives with Code Annotations,  https://scan4.coverity.com/doc/en/cov_checker_ref.html#codeannotate ).
The sintax is
// coverity[event-tag]
e.g.
In my code I have a switch statment in which a case value is not, on purpose, finished with a break to force to execute the code in the next case value:
    switch(m_status)
    {
        case circle_start:
            m_circle.init(0.0, 0.0, m_radius, m_radius);
            m_circle.rewind(0);
            m_status = circle_point;
            //continues in next case code

         case  circle_point:
			...

Coverity reported an event of type "unterminated_case" in first case statement. To supress this false positive I just included one comment line before the offending case statement:
    switch(m_status)
    {
        // coverity[unterminated_case]
        case circle_start:
            m_circle.init(0.0, 0.0, m_radius, m_radius);
            m_circle.rewind(0);
            m_status = circle_point;
            //continues in next case code

        case  circle_point:
			...

Hope this helps. I've you like, could try this solution and see what happends.


Formatting error on Windows machines

The prettier-plugin-embed-embed does not load the prettier-plugin-sql on Windows machine in VS Code and shows this error on the VS Code DevTools when saving a file.
Error: Cannot format embedded language identified by "sql", because plugin "prettier-plugin-sql" is not loaded.

No error shows up in the output panel of VS Code, as it shows that the formatting was completed, this was also mentioned here
["INFO" - 12:28:29 PM] Formatting completed in 810ms.

This the content of the Prettier config file
/** @type {import('prettier').Config} */
const prettierConfig = {
  plugins: ['prettier-plugin-embed', 'prettier-plugin-sql'],
  singleQuote: true,
  trailingComma: 'all',
};

/** @type {import('prettier-plugin-embed').PrettierPluginEmbedOptions} */
const prettierPluginEmbedConfig = {
  embeddedSqlComments: ['sql'],
  embeddedSqlTags: ['sql'],
};

/** @type {import('prettier-plugin-sql').SqlBaseOptions} */
const prettierPluginSqlConfig = {
  language: 'postgresql',
  keywordCase: 'upper',
  identifierCase: 'lower',
  dataTypeCase: 'lower',
  functionCase: 'lower',
  expressionWidth: 30,
};

const config = {
  ...prettierConfig,
  ...prettierPluginEmbedConfig,
  ...prettierPluginSqlConfig,
};

export default config;

The SQL code that should be formatted
export async function up(sql: Sql) {
await sql`
CREATE TABLE workshops (
id integer PRIMARY key generated always AS identity,
title varchar(70) NOT NULL,
workshop_date varchar(40) NOT NULL,
timeframe varchar(40) NOT NULL,
location varchar(40),
category varchar(40),
image varchar(50) NOT NULL,
price integer NOT NULL,
description varchar NOT NULL
    )
  `;
}

I am using the following versions for the plugins
"prettier": "^3.2.5",
"prettier-plugin-embed": "^0.4.13",
"prettier-plugin-sql": "^0.18.0",

Running this Prettier command from the command line was able to format the file
pnpm prettier migrations/00000-createTableWorkshops.ts --write

Hi Victor,
Thank you very much for this detailed report. It's very helpful. I pushed a fix in #85. Will you check if the test package in https://github.com/Sec-ant/prettier-plugin-embed/pull/85#issuecomment-1953422584 does resolve this issue?

Hello, @Sec-ant,
Thank you so much for the prompt answer and fix. I can confirm that the fix pushed in https://github.com/Sec-ant/prettier-plugin-embed/pull/85 did fix the issue, and now the SQL codes can be formatted on save, but I want to know if there is any downside in this approach (Removing the throwIfPluginIsNotFound check). What was the purpose of this code and why is it no longer necessary?
https://github.com/Sec-ant/prettier-plugin-embed/assets/74430629/678483c6-b48c-4cb3-9d97-c362f69f018d

What was the purpose of this code

The function throwIfPluginIsNotFound is supposed to print an explaining message when the formatting of embedded languages failed silently because of the user not loading the corresponding language plugins (like prettier-plugin-sql or plugins for other languages).

Why is it no longer necessary

TL;DR, this function does more harm than good.
The paths of the loaded plugins are registered in the options object in Prettier which can be accessed by this plugin. So this function finds the paths of all the loaded plugins and checks if the required plugin is loaded. If it cannot find the required plugin it then throws and exits early without trying to format the embedded blocks, and prints the explaining message.
However there're several issues with this approach:

A user can fork a language plugin and rename or relocate it for whatever reason without modifying its function. And with this approach the user cannot use the forked plugin because the check fails.
To pair the plugin path with the required plugin name requires some additional work to deal with path separators on different platforms (Win vs Linux vs MacOS) or runtimes (node vs deno vs web etc.). Additionally the function more or less works in a heuristic way so it is error-prone.
The initial intention to introduce this function is to provide explaining messages to the users but due to the logging service used in the VSCode extension is unavailable to the plugin, it can only log messages to the DevTools console which basically defeat the purpose.

So I decide to remove this function.

You're welcome to share them if you have better ideas @Eprince-hub, otherwise I'm going to move forward and release a new version including this fix.

@Sec-ant, amazing! I think it makes sense to go on with this fix, as you have explained above 👍
Thank you

The fix is shipped in v0.4.14.


Bug with 2-digit APRS SSID Suffixes

Hi,
this is a great piece of work! Unfortunately it does not accept APRS-SSIDs with more than one digit for the suffice (like -11 for a balloon).
The fix is simple AFAIK:
Change line 114 in ax25.py to
 assert(len(ssid) <= 2)

It seems not that simple :-( Now, the resulting packets cannot be properly decoded.

I seem to understand the problem: The SSID seems to be encoded as 4 Bits in the resulting AX.25 sequence of octets. So somewhere in the code, the string of a one-digit SSID is being translated in the respective bit pattern. But I did not find out where :-(
If you an ASCII character beyond the numbers, you can actually get the proper pattern. For instance, -K will actually produce -11 for a balloon as a temporary fix. But it would really be very nice to fix this issue, for APRS defines up to 16 SSIDs.
Thanks in advance!

Ok, now I have a solution that should work reliably:
Insert the following at line 113 of ax25.py:
		if 10 <= int(ssid) <= 15: 			ssid = chr(ord(ssid[1])+10)
That will translate the SSIDs 10 - 15 to a character that will later be properly converted into the 4-bit representation of these SSIDs.
@casebeer It would be great if you could add this fix to the release.
73s
Martin


Refactor the perk lottery checks

This is now done as a separate step after the perks have been calculated, which allows two things to be fixed:

Rerolling into a lottery perk would not correctly flag it (visible in seed 1600042, when rerolling the first row)
It wasn’t possible to properly factor in the lottery perks themselves

This also fixes gambling into a lottery perk.

This also has the nice advantage of making searching for perks a bit faster. 👍


Use of colon in request path for API creation

Unable to specify special characters such as a colon (:) in request path i.e. path must only contain alphanumeric and '. -, _, ~' characters.

Only characters contained in RFC 3986's section 2.3 unreserved characters list are allowed in the request_path property.

Characters that are allowed in a URI but do not have a reserved
purpose are called unreserved.  These include uppercase and lowercase
letters, decimal digits, hyphen, period, underscore, and tilde.

unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

I believe it would be wrong to accept characters from the reserved list (aka URI delimiters defined in section 2.2) since they would need to be percent encoded when your consumers are making the request to Kong, which would make things confusing for them. If they would be sent not percent encoded, we would not comply to RFC 3986 in the way that request_path is supposed to be contained in a URI section delimited by /, which would not be the case if other delimiting characters were allowed.

Hi Charbonnier,
Can you please provide guidance regarding how we should proxy these type of requests?
https://localhost/wapi/v1.2.3/record:host?name~=abcmachine&ipv4addr~=<IP_ADDRESS>&_return_type=xml-pretty
https://localhost/wapi/v1.2.3/network?network=<IP_ADDRESS>&_return_type=xml-pretty&_return_fields=network,netmask,options,extattrs
Thanks, Kathy
From: Thibault Charbonnier<EMAIL_ADDRESS>Sent: Friday, November 06, 2015 11:10 PM
To: Mashape/kong
Cc: Maher, Kathy
Subject: Re: [kong] Use of colon in request path for API creation (#692)
Only characters contained in RFC 3986https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc3986&d=CwMCaQ&c=gtIjdLs6LnStUpy9cTOW9w&r=gFEejS4hzs1eGwRbNnwrLKtyDc4uDMIztPDHP1LxfVE&m=aJeTMbRE3fpN06YYxeDmaYaoelI70GZhzqS2JiGG37o&s=igrPDFrFA_7cVc7e8ukgXW2zbL0ve7Qf2UTBGL39wb8&e='s section 2.3 unreserved characters list are allowed in the request_path property.
Characters that are allowed in a URI but do not have a reserved
purpose are called unreserved. These include uppercase and lowercase
letters, decimal digits, hyphen, period, underscore, and tilde.
unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"
I believe it would be wrong to accept characters from the reserved list (aka URI delimiters defined in section 2.2) since they would need to be percent encoded when your consumers are making the request to Kong, which would make things confusing for them. If they would be sent not percent encoded, we would not comply to RFC 3986 in the way that request_path is supposed to be contained in a URI section delimited by /, which would not be the case if other delimiting characters were allowed.
—
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Mashape_kong_issues_692-23issuecomment-2D154623348&d=CwMCaQ&c=gtIjdLs6LnStUpy9cTOW9w&r=gFEejS4hzs1eGwRbNnwrLKtyDc4uDMIztPDHP1LxfVE&m=aJeTMbRE3fpN06YYxeDmaYaoelI70GZhzqS2JiGG37o&s=w04HwIK8tDzhdgoavEW0CnA7qD2g_AMnXIOBdb9bovg&e=.

If you wish to route by path, your request_path could be:

/wapi/
or /wapi/v1.2.3/
or even /wapi/v1.2.3/network and /wapi/v1.2.3/record.

If you wish to route by Host, (request_host), then it depends on the domain name on which Kong is hosted.
Up to you. Please read the proxy docs.


Feature/150 design homepage

Resolves #150
Homepage redesigned. Some details will be completed for final milestone. These details are: displaying real story date and location with 2-3 lines of story text, changing all stories/followings stories buttons to toggle.
After:

Before:

We can add date and location info of stories as text as seen in story details. @ckertam can you help about these fields? Then we provide better version for milestone 2 also.

@aykutkantas We can do it with reverse geocoding. Get first location point's name field to show it :)

story date and location added


Create functions_ikram_celal_keskin.py

Describe your changes
Checklist

[X] I have read the [CONTRIBUTING]
[X] I have performed a self-review of my own code
[X] I have run the code locally and it works as expected
[X] I have commented my code, particularly in hard-to-understand areas

Screenshots (if appropriate)

I saw that others were using the ‘tracemalloc’ module. I wanted to try something different.


Plans to create an alternative for vue?

Hi there,
I love the idea of this project and I am looking for a while now for such a thing for Vue.
Are there any plans to create such a package as well?

Hi there,
I love the idea of this project and I am looking for a while now for such a thing for Vue.
Are there any plans to create such a package as well?

We would love to support vue, but we want to nailed down with react first.


Can you create a template of this poster in overleaf?

I have tried to open it in overleaf, but the compilation fails:
/usr/local/texlive/2017/texmf-dist/tex/latex/fontspec/fontspec.sty, line 28
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!
! Fatal fontspec error: "cannot-use-pdftex"
!
! The fontspec package requires either XeTeX or LuaTeX.
!
! You must change your typesetting engine to, e.g., "xelatex" or
! "lualatex"instead of plain "latex" or "pdflatex".
!
! See the fontspec documentation for further information.
!
! For immediate help type H <return>.
!...............................................

l.28 \msg_fatal:nn {fontspec} {cannot-use-pdftex}

|'''''''''''''''''''''''''''''''''''''''''''''''
| This is a fatal error: LaTeX will abort.
|...............................................

LaTeX errors are always a vague gibberish to me, but this one is particularly so.

There is already a template on overleaf: https://www.overleaf.com/latex/templates/gemini-poster-theme/nzpspqjryjhx
This theme needs to be compiled with LuaTeX. You can do this in "project settings":

The compiler should be set to LuaLaTeX.


DO NOT MERGE: Test CI stability

Testing the stability of the v1.8 branch.

test-backport-1.8

Closing as the CI failures were fixed by https://github.com/cilium/cilium/pull/15750


Prefix haskell package name with "haskell-"

Issue description
This is related to Repology. Basically all of the haskell packages use the name attribute for just their name. It would be nice to prefix it with something like "haskell-" to make it obvious that this is the "haskell" version of the package and not something else with the same name.
See: https://repology.org/metapackage/a50/related
/cc @peti

We used to have haskell- prefixes but dropped them a long time ago because they serve no purpose inside of Nixpkgs.

Having something in the name would be nice when looking at store paths.

It’s interesting how many different ways package managers name them. Here are all packages for the containers module:
https://repology.org/metapackage/haskell:containers/versions

Ports uses hs-
Lots of Linux users use ghc- including guix
gobo uses Haskell-

It doesn’t rreally matter which one we use just that there’s a way to differentiate between haskell and nonhaskell packages.

In case of Python we have a prefix that describes what interpreter it is for, both implementation and language version.

Shouldn't we be telling Repology attr paths, not names in derivations? Then we'd tell them haskellPackages.foo with no effort.

@dezgeg The attrpaths feel like some internal nixpkgs detail to me.

On the other hand, we are saying we want people to use nix-env -A all the time, so maybe not.

This file in the Repology source is good inspiration for how other package repositories handle this this kind of problem:
https://github.com/repology/repology-rules/blob/cf597026b26d56411db1245c9728226f09feb56c/500.wildcard.yaml#L52
Repology disambiguates sub package sets by using a name: prefix, like haskell:a50.
If we added a rule like this, it would handle this for us on Repology:
- { setname: "haskell:$0", noflag: not_haskell, name-pat:"(.*)", wwwpart: hackage.haskell.org, family: [nix-unstable, nix-stable] }

I'll work on getting that rule in, but it seems like it would be worth changing the name of the package for more general usage.

Oh, sorry, that doesn't work because not all haskellPackages packages have a Hackage homepage. It looks like I can fix the rPackages though because they are all prefixed by r-.

Here is the fix for the rPackages https://github.com/repology/repology-rules/pull/30

That doesn't work because not all haskellPackages packages have a Hackage homepage.

I think it would be find to change our package set so that Hackage package refer meta.homepage to hackage rather than the URL given in the Cabal file. Those URLs are oftentimes flat out wrong. The  Hackage URL, however, is definitely correct and it's also not going to disappear over time, so arguable it's more valuable for our users.
Generally speaking, I think this problem should be solved in the code that generated the package lilst, i.e. there should be some general-purpose mechanism that maps from a nested attribute path into a prefixed package name so that haskellPackages.foo can come out as haskell-{haskellPackages.foo.name}. The same mechanism can be useful for other cases, like Emacs packages, gnome packages, and whatnot.

@AMDmi3 has already said he's ok with our current format: https://github.com/repology/repology/issues/560

@globin, do I understand that repology ticket correctly when I interpret it as saying that they will extend their harvester so that it no longer classifies our R and Haskell packages as "meta packages"?

I wanted to do this, but I hoped that it would only be a temporary fix. If nix haskell packages are prefixed, it won't be needed.

@AMDmi3 I have a solution: we can update the nix.py parser to look for keys starting with haskellPackages and immediately prefix "haskell:" to the package name. I'm working on this currently

I guess this is fine to look at other things in repology. But shouldn’t haskell packages be prefixed regardless of how repology works? That’s at least consistent with how most other language packages work. In addition they’ll be grouped together in the package search & avoid potential name collisions with non-Haskell packages.

I guess this is fine to look at other things in repology. But shouldn’t haskell packages be prefixed regardless of how repology works?

I completely agree. After 4a8797d8276aa1bd9c09d1f591eef1bd04adf2ec was commited, nix's "to be built" list became really confusing, so I reverted that commit. I'm really surprised nobody voiced the intention to do the same before now.
In case anyone cares I vote for ghc-${version}- prefix. You'd be surprised how helpful that is. Like you'd immediately notice that older ghcs are build just for a single jailbreak-cabal binary.

Another issue to consider is that some Haskell packages are already prefixed with haskell-. For example, https://hackage.haskell.org/package/haskell-abci . It seems nice that Repology uses : for separating the package namespaces because a : is less likely to appear in the name of a package.

@oxij, can you please share more detail about which particular jailbreak binary is build with an older version of ghc? I looked around the source code in master and I can find any such case.

@globin Can we reopen this because it does not seem like there is consensus on prefixing?

I fixed the prefixing issue relating to Repology by using the first part of the attrpath (if the attrpath has a . in it) as a package "category", and making a rule that prefixes haskell: to the name of any nix package with the category haskellPackages. For example, https://repology.org/metapackage/haskell:mtl/versions .
I think this issue should remain open because we haven't finished resolving the other potential issues regarding prefixing or not.

Just my 2 cents, if nix community decides to prefix haskell packages (I fully support this idea), please notify me beforehand so I could add corresponding rule and avoid package names bouncing back and forth in repology, polluting feeds.

@matthewbauer Why did you close this?

I've change my mine on this one. IMO the rule should be-

If your package set uses recurseIntoAttrs, then you MUST prefix each package name with the language.
If your package set does not use recurseIntoAttrs, you can choose to prefix or not.

Haskell doesn't use recurseIntoAttrs so this seems fine.


Fix 0.41 import statements in RCTTVRemoteHandler.m

Want to fix build on 0.48.1
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

You also opened #15783. Should we keep this PR open?


ClientModel: Remove types in .Internals.Primitives namespace

https://github.com/Azure/azure-sdk-for-net/pull/40151 removed two of the three types remaining in the .Internals.Primitives namespace from the ClientModel public API.  This PR removes the final type HttpClientPipelineTransport.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core