API usage

The "routes.py" file does not have an entry point that receives images in Base64 string, so I can not complete this example of the video, (https://www.youtube.com/watch?v=HeKCQ6U9XmI) I managed to make it work but only with local files
In fact, this postman file is not the same as the video sample https://github.com/serengil/deepface/blob/master/api/deepface-api.postman_collection.json

you can send img1_path and img2_path content as base64 as well as exact image path


fix regression: MiMa failing to extract

test run: https://scala-ci.typesafe.com/job/scala-2.11.x-jdk8-integrate-community-build/245/consoleFull (404 til Jenkins gets in gear)

@dwijnand you might want to look into the details here, this is just me trying for the quick fix without really investigating

extraProjects is a 0.13.13 feature, so that's the reason.
Did it fail during extracting or running? Because your test run above extracted fine.

It failed during extraction before. aborting the run and merging.

In retrospect we shouldn't've upgrade mima to the prerelease


python311Packages.wagtail: 6.0.2 -> 6.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.wagtail is: A Django content management system focused on flexibility and user experience
meta.homepage for python311Packages.wagtail is: https://github.com/wagtail/wagtail
meta.changelog for python311Packages.wagtail is: https://github.com/wagtail/wagtail/blob/v6.1/CHANGELOG.txt
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 6.1 with grep in /nix/store/n02ar62dy4712nzywbxd69iqx24i3law-python3.11-wagtail-6.1
found 6.1 in filename of file in /nix/store/n02ar62dy4712nzywbxd69iqx24i3law-python3.11-wagtail-6.1

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

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-localize
python311Packages.wagtail-modeladmin
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-localize
python312Packages.wagtail-modeladmin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n02ar62dy4712nzywbxd69iqx24i3law-python3.11-wagtail-6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/3800a38d42cea7013b4233e064577e62406321a6#python311Packages.wagtail

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n02ar62dy4712nzywbxd69iqx24i3law-python3.11-wagtail-6.1
ls -la /nix/store/n02ar62dy4712nzywbxd69iqx24i3law-python3.11-wagtail-6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages failed to build:

python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
python311Packages.wagtail-modeladmin
python311Packages.wagtail-modeladmin.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist
python312Packages.wagtail-modeladmin
python312Packages.wagtail-modeladmin.dist

8 packages built:

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-factories.dist
python311Packages.wagtail.dist
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-factories.dist
python312Packages.wagtail.dist

Maintainer pings
cc @sephii for testing.

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

8 packages failed to build:

python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
python311Packages.wagtail-modeladmin
python311Packages.wagtail-modeladmin.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist
python312Packages.wagtail-modeladmin
python312Packages.wagtail-modeladmin.dist

8 packages built:

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-factories.dist
python311Packages.wagtail.dist
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-factories.dist
python312Packages.wagtail.dist

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.wagtail is: A Django content management system focused on flexibility and user experience
meta.homepage for python311Packages.wagtail is: https://github.com/wagtail/wagtail
meta.changelog for python311Packages.wagtail is: https://github.com/wagtail/wagtail/blob/v6.1.1/CHANGELOG.txt
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 6.1.1 with grep in /nix/store/pyyj1z7f3qkrvgia7dc8lhn6qx9ky2bp-python3.11-wagtail-6.1.1
found 6.1.1 in filename of file in /nix/store/pyyj1z7f3qkrvgia7dc8lhn6qx9ky2bp-python3.11-wagtail-6.1.1

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

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-localize
python311Packages.wagtail-modeladmin
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-localize
python312Packages.wagtail-modeladmin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pyyj1z7f3qkrvgia7dc8lhn6qx9ky2bp-python3.11-wagtail-6.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/3fbaf6d550e7fa11344ffc651ba7b9f80dd9534d#python311Packages.wagtail

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pyyj1z7f3qkrvgia7dc8lhn6qx9ky2bp-python3.11-wagtail-6.1.1
ls -la /nix/store/pyyj1z7f3qkrvgia7dc8lhn6qx9ky2bp-python3.11-wagtail-6.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages failed to build:

python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
python311Packages.wagtail-modeladmin
python311Packages.wagtail-modeladmin.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist
python312Packages.wagtail-modeladmin
python312Packages.wagtail-modeladmin.dist

8 packages built:

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-factories.dist
python311Packages.wagtail.dist
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-factories.dist
python312Packages.wagtail.dist

Maintainer pings
cc @sephii for testing.

8 packages failed to build:
python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
python311Packages.wagtail-modeladmin
python311Packages.wagtail-modeladmin.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist
python312Packages.wagtail-modeladmin
python312Packages.wagtail-modeladmin.dist

PR is fine but requires https://github.com/NixOS/nixpkgs/pull/315187

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.wagtail is: A Django content management system focused on flexibility and user experience
meta.homepage for python311Packages.wagtail is: https://github.com/wagtail/wagtail
meta.changelog for python311Packages.wagtail is: https://github.com/wagtail/wagtail/blob/v6.1.2/CHANGELOG.txt
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 6.1.2 with grep in /nix/store/ymw8iakhpr2xc18f24x6wxqnw0kwrwsp-python3.11-wagtail-6.1.2
found 6.1.2 in filename of file in /nix/store/ymw8iakhpr2xc18f24x6wxqnw0kwrwsp-python3.11-wagtail-6.1.2

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

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-localize
python311Packages.wagtail-modeladmin
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-localize
python312Packages.wagtail-modeladmin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ymw8iakhpr2xc18f24x6wxqnw0kwrwsp-python3.11-wagtail-6.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/b622fa50192d59dfc24abb01db51d6a9c1fd2463#python311Packages.wagtail

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ymw8iakhpr2xc18f24x6wxqnw0kwrwsp-python3.11-wagtail-6.1.2
ls -la /nix/store/ymw8iakhpr2xc18f24x6wxqnw0kwrwsp-python3.11-wagtail-6.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

8 packages failed to build:

python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
python311Packages.wagtail-modeladmin
python311Packages.wagtail-modeladmin.dist
python312Packages.wagtail-localize
python312Packages.wagtail-localize.dist
python312Packages.wagtail-modeladmin
python312Packages.wagtail-modeladmin.dist

8 packages built:

python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-factories.dist
python311Packages.wagtail.dist
python312Packages.wagtail
python312Packages.wagtail-factories
python312Packages.wagtail-factories.dist
python312Packages.wagtail.dist

Maintainer pings
cc @sephii for testing.


TAR files with PAX format are throwing exception

You can replicate this issue with this file:
https://registry.npmjs.org/mout/-/mout-1.0.0.tgz
or
https://registry.npmjs.org/rxjs/-/rxjs-5.0.0-beta.6.tgz
SharpCompress.Common.InvalidFormatException: Not a tar file.
  at SharpCompress.Reader.Tar.TarReader.Open(Stream stream, Options options)

Just something to put on the todo list
Quick google description
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.bpxa500/pxarchfm.htm


GLesmos slider uniforms

A big performance optimization in GLesmos would be passing in sliders (and list literals? Maybe inspect the ticker to detect which can change in normal operation) as uniforms to reduce the need for recompilation.

After merging #805, this is built in to Desmos's emitGLSL function. The second parameter is the number of uniforms.
If you write emitGLSL(chunk, 100), it'll replace the first 100 number constants with uniforms (starting with _DCG_SC_0).
@radian628 Would it be simple to handle this in the shader caching system? I suspect yes. We cache the compiled programs based on the strings. So we just need to remember to bind the uniforms to the program.

Excited I got this working!


Clean up MapAdapter

This PR contains two minor clean up changes to the MapAdapter:

Use timber for logging
Remove the renderJsonLayer -- we don't need it anymore since we now take a viewport based approach to offline area selection

Thanks @shobhitagarwal1612! It's ready for another check when you get a chance.


Pricing: AWS Transfer Family ($.30 per hour - SFTP Endpoint fee)

I have created POC for Live Streaming (Europe Ireland region):

AWS MediaLive
AWS MediaPackage

I have used live streaming for max 30-40 minutes. After my testing of live streaming, I had deleted MediaPackage Endpoint and Stopped the MediaLive Channel.
After 24 hours I charged:

MediaLive: $0.89
MediaPackage: $0.04
Transfer Family (AWS Transfer Family EU-ENDPOINT - $.30 per hour - SFTP Endpoint fee: 432.000 Hourly)  - $129.60 (?????)

No used:
AWS CloudFront
Why below charges?
Transfer Family (AWS Transfer Family EU-ENDPOINT - $.30 per hour - SFTP Endpoint fee: 432.000 Hourly) - $129.60
Any alternate solution?

I have used Standard Definition (SD) with Single-pipeline channel.

Hi there,
I am unsure as to where the transfer family fees are coming from as we don't use SFTP anywhere in the workflow. The Media Services don't use SFTP either. Could it be possible this was from some other setup in your account?

Yes, my bad. It looks like SMTP charges are fro other service.
Thanks @morjoan


Creating your first map sample code does not work

I am trying to learn how to use OpenLayers. Following the Tutorials in the Documentation, I have tried to start with the sample code given under Creating your first map.
The sample page displays nothing.
It would be helpful if the samples in your tutorial actually work!!

Are you talking about http://openlayers.org/workshop/en/basics/map.html ?

Or https://openlayers.org/en/latest/doc/tutorials/concepts.html ?

I was referring to this one: https://openlayersbook.github.io/ch01-getting-started-with-openlayers/example-01.html
Incidentally, http://openlayers.org/workshop/en/basics/map.html does not work either.

We don't maintain the openlayers book

@staplesj you should report your issue to https://github.com/openlayersbook/openlayersbook.github.io/issues

Our workshop doesn't work since the demo.opengeo.org service is down, we should probably use a different service in our workshop

Blue marble does not work. I have been using
new ol.layer.Tile({
          source: new ol.source.OSM()
        }),

also
var layers = [
        new ol.layer.Tile({
          source: new ol.source.TileWMS({
            url: 'https://ahocevar.com/geoserver/wms',
            params: {
              'LAYERS': 'ne:NE1_HR_LC_SR_W_DR'
            }
          })
        })
      ];

I have been working my way through the Beginners Openlayers3. There are some outdated functions that need to be replaced as well. I am slowly making a list with solutions. Would it help to post these here or on my own github?

As I said that WMS is down, so bluemarble down is to be expected. If it's related to the OpenLayers book, this repo is not a good place to ticket those issues but use the link that @fredj provided.
If you're not sure post them on your own github first and we can help you decide where to put them.
cc @acanimal is there any active development on the book of openlayers these days?

Yes, I am learning OL3 using many sources and fixing things along the way. I'll see if I can post something helpful on my github. It is nice to have an alternative WMS when one fails.

Link https://openlayersbook.github.io/index.html is the companion of OpenLayers3 Cookebook from PackPub written by @ThomasG77 (I wrote the OpenLayers2 Cookbook 😄  ).
I wrote too The Book of OpenLayers3 with the samples at http://www.acuriousanimal.com/thebookofopenlayers3 🎉

Ah too many books to keep track of @acanimal ;-) thanks for your feedback

http://openlayers.org/workshop/en/basics/map.html fixed with https://github.com/openlayers/workshop/pull/72


Tab key doesn't work in multiline string setting textarea

Testing https://github.com/microsoft/vscode/issues/79571
This issue is to note that the tab key doesn't work in the multiline string setting textarea, because tab is used to move focus to the next element.
The monaco editor uses Ctrl+M to toggle between two modes: tab meaning to move focus, and tab meaning to insert a tab character into the editor. Maybe the textarea can do something similar?

Discussed offline and closing as a wontfix. Feel free to comment on this issue if you want it re-opened, though, or if you have an alternative solution to suggest.


Fix: Resolve San Francisco Pipeline Yaml Variable Assignment Issue

Description
This is a fix to resolve a missed change to pipeline.yaml variable for municipal trips, which ultimately caused pipeline failure.
Checklist

[x] (Required) This pull request is appropriately labeled
[x] Please merge this pull request after it's approved

Use the sections below based on what's applicable to your PR and delete the rest:
Data Onboarding

[x] I'm adding or editing a dataset
[x] The Google Cloud Datasets team is aware of the proposed dataset
[x] I put all my code inside  datasets/san_francisco and nothing outside of that directory

Merged and deployed to production


Precomputed permutation scores

Description
The precomputed permutation scores need to be made accessible.

Solved via #5.


Who is the author in a scheme file?

Hello,
In a scheme file we can find the name of an author. Who is he? He can be:

The creator of the file.
The creator of the scheme.

If I use the solarized theme, the author should be @altercation (scheme creator) or myself (file creator)?
To answer this, we could look at the use. Why should we add the author? What is the benefit of each one?
In another hand, could be use both?
For now, I think we should use the original author.
What do you think?

For now, I think we should use the original author.

Agree.
Whoever ported the template (i.e. you) gets attribution via the commit log.

Whoever ported the template (i.e. you) gets attribution via the commit log.

Yes! Good point!
I will close this issue. If someone wants to add something, feel free to comment.


Reflow should remove the tailing spaces except the last line

Hi there,
When I use the reflow feature, I also end up with two spaces between the ending word of a line and the starting word of next line. E.g.,
test<space>
test
will become
test<space><space>test
This is very inconvenient to me. I really love this feature (I use this feature frequently in TextWrangler). So I expect that it can become
test<space>test
In addition, we should leave the spaces for the last line of this block. E.g.,
test<space>
test<space><space><space>
should become
test<space>test<space><space><space>
So I made this change and hope it can be added to the package.
Cheers,
Hengfeng Li

Hi @HengfengLi, can you please add a spec for this to make sure that it doesn't regress in the future?  Thanks!


Add release helm charts workflow

Hi everyone,
I do understand that the helm-chart release should also be official under the operator name/domain but sometimes it is really hard to keep sync/install it from sources when you also want to keep in sync with the latest changes of the chart or even to extreme install it e.g. on GKE via terraform -- as such you have to install it into some registry which is then able to be used are repo.
To really get rid of all those manual steps I did test this workflow with one demo example and it seems to work out-of the box thanks to https://github.com/helm/chart-releaser-action.
So instad of installing it from sources (I didnt' update the documentation yet, but I can also do it when this goes through so that we also adapt them with the change on how to use the chart(s)) we could just do:
helm repo add flink-operator https://spotify.github.io/flink-on-k8s-operator/

and then install it via:
helm install [RELEASE_NAME]  flink-operator/flink-operator --set operatorImage.name=[IMAGE_NAME]

In order to get this deployed we should also enable the:

In your repo, go to Settings/Pages. Change the Source Branch to gh-pages.

as explained here: https://github.com/helm/chart-releaser-action#pre-requisites
What do you think about this?

@GezimSejdiu sorry for the late reply on this.


New release?

It's been a while since the last release, and the latest master crashes with django19 (which is at rc, and will be release in less than a couple of weeks).
Can we get a new release (1.0.1?), that's django19-compatible? :)

All our builds are passing. As long as Django 1.9 is not stable don't expect it to be added to the build matrix.
What is crashing? Can you post a stack trace? Can you provide a PR?

Django 1.9 has already been stabilized, and is currently on rc1.
master works with django1.9, but the latest release isn't working, that why I was merely mentioning a new release and didn't give much more details. :D
Notably, 87bb09c fixes a deprecation from 1.7 that no longer works on 1.9, but that didn't make it into 1.0.0.

I'd recommend you add 1.9 to the build matrix, and we see what happens. If all goes well with the code as it is. Your PR is appreciated.
As soon as 1.9 is officially out we'll merge that into master and package a release, I'd suppose.

I've added 1.9 to the dependency matrix (along with py35 which was also missing, and has been release for some time now).
Hopefully this can be merged in and a new release can be made? :D

bump

@brainrape See our Gitter chat. Joost must take a decision on the version number. We're getting there.

Thanks

Finally release version 2.0.0 that is compatible with 1.9 thanks to @hobarrera.


Hosting the sample on Azure

Hi,
I deployed the app to the cloud using Azure App Services, I properly updated the parameters:
Parameter | Value
App type | Web App
Sign on URL | https://cloud_service_URL>
Redirect URI | https://cloud_service_URL>/callback
I also updated the values in the file constants.js
redirectUri: 'https://cloud_service_URL>/callback'
notificationUrl: 'https://cloud_service_URL>/listen'
But I'm getting this error after trying to login:

Any idea to solve this issue?
Thanks

Update.
I moved from a free server to a paid server it seems like the free version doesn't support webhooks. Anyway, I got a new error that I think is related to socket.io.
Any idea about how can I successfully implement socket.io on Azure's App service? or which parameters should I change or add to the sample?
Thanks

Update.
I moved from a free server to a paid server it seems like the free version doesn't support webhooks. Anyway, I got a new error that I think is related to socket.io.
Any idea about how can I successfully implement socket.io on Azure's App service? or which parameters should I change or add to the sample?
Thanks

@Ajaldin looks like a socket.io error. Please check if this helps _https://stackoverflow.com/questions/11995406/socket-io-referenceerror-io-is-not-defined_.

@Ajaldin looks like a socket.io error. Please check if this helps _https://stackoverflow.com/questions/11995406/socket-io-referenceerror-io-is-not-defined_.

Hi, I tried all of them, none of them worked for me so far. It's definitely a problem with socket.io, somehow when I run the app that path is not reaching the socket.io resource, therefore, generating errors and not establishing the socket even having got the subscription.
Any idea?

Hi, I tried all of them, none of them worked for me so far. It's definitely a problem with socket.io, somehow when I run the app that path is not reaching the socket.io resource, therefore, generating errors and not establishing the socket even having got the subscription.
Any idea?

Sorry @Ajaldin I am not sure why you are facing this issue with socket io. I will go ahead and close this issue from here. Kindly follow this link https://github.com/socketio/socket.io to raise the issue.

Sorry @Ajaldin I am not sure why you are facing this issue with socket io. I will go ahead and close this issue from here. Kindly follow this link https://github.com/socketio/socket.io to raise the issue.

I had to edit part of the code in order to have this running on Azure App Services.


Gulp: development flag

This is more a usability issue regarding the development workflow.
Since we use gulp --dev in the most cases, and gulp quite rarely, it makes sense to make development a default environment (vice versa compared to what is it right now). So:
gulp // runs development mode

And
gulp --prod / gulp -p // runs production mode

I find this quite useful, but I want to hear your opinion as well.

Good idea, I already used it like that on my own project

There are 3 modes, the last one is not documented :-(

gulp --dev - runs dev mode
gulp build - runs production mode - only compilations
gulp - runs production mode with static server but without watch (gulp build + browserSync server)

Do we need 3rd mode? If yes, how would we run it?

I like the third mode. Using it, you can test the proper bundling of all production assets.

What about this?

gulp - runs dev mode
gulp build --prod - runs production build
gulp --prod - runs production build with browserSync

Well, I would suggest just flip the logic of gulp --dev right now, since refactoring all the tasks may take additional time and discussion (for example, prepare task is essentially build task, which runs differently in dev and prod, so it makes sense to have build and build --prod instead of prepare)

Well, in the grand scheme of things, I think having PRODUCTION as default is always a good option.

Please think about all running projects. Imagine situation you are working on more than one project and you don’t know if run gulp or gulp --dev. How can we prevent this situation? The same for BE developers. They will hate us!
Should we switch this commands on all projects? Or create some patch? Who will do it? What will be the timing?

@vbulant @janpanschab I understand the maintenance issues. But this would be a nice thing to have on new projects. If think about it, relying on implemented solution limits us in improving our devstack, we may have the same situation when migrating to Webpack, for example. This concerns almost any relatively big change.
But I really understand the consequences, I am just thinking of things which may make development process better. In the end, it is all about the agreement (somebody taught BE developers to run gulp --dev ;) )

@kettanaito I’m not against improvements at all.
Let me explain my point of view.
The devstack is intended to be used throughout our local dev env and CI servers – Circle, .NET deployment, etc (correct me if I’m wrong, @janpanschab). And because CI servers are considered production envs, our devstack should default to production in my opinion.
It’s nice and convenient to have development env as default in case you use a devstack just for your development env or if you have separate pipelines for dev and prod…
So, back to your development as default point:
Maybe it can be done differently, eg. having gulp as development watcher and gulp build as production pipeline. But then we’d need to rethink our yargs based logic (--dev)…
Or utilize npm scripts and have "start": "gulp --dev" and "build": "gulp build" which is similar to create-react-app. But still, in case we do this, we need to ensure it’s used only for new projects so that it doesn’t break current/old ones (deployments).
But still, I’m perfectly OK with the current solution (default prod, optional dev) and I don’t think changing it is worth the effort. But I’m open to continue the discussion for sure.

I feel the same. I can sign it.
@vbulant great explanation.

@vbulant then for the sake of better maintenance I would think of having 1 legacy version, and 1 up-to-notch version of development stack. Project on older versions may utilize the devstack as they have used to, at the same time we will not have any obstacles to introducing really any technology we wish to new projects, without thinking of how it may affect the old ones.
What a deep discussion that started :)

@kettanaito When that time comes (need for split to legacy/top-notch versions), we can think about it for sure.
But I think generally it’s not a problem. When you add webpack instead of browserify, but the API stays the same (gulp build), it’s going to work just fine… So imho it’s not about features that much as it is about the API which is used by deployments, CLI etc…

@vbulant agree :)
Well, I don't think bringing another level of commands abstraction (in the form of npm scripts) is a good idea, it may lead to more confusion than easing in the workflow.


improve dependency declaration with extended attributes

It seems that Maven allows pom modules to have dependencies which are not declared. In order to collect those kind of dependencies the syntax and logic for adding dependencies should be improved.
Use case: org.lwjgl:lwjgl-glfw:3.3.3:natives-macos-arch64 where the last token is a classifier attribute in maven pom.
According to a post from stackoverflow:
https://stackoverflow.com/questions/35052763/downloading-lwjgl-natives-with-ivy

An alternative is to use https://github.com/maveniverse/mima as @maxandersen suggested. It needs to be studied and dive deeper into it.

The advantage of Mima is it's consistent with the broader maven artifact system. There are edge cases especially in the overlap of maven and gradle published artifacts that ivy does not handle in same ways.

I started to develop a replacement for dependency handling using MIMA. It seems it works fine.

Any chance the syntax could be same as in jbang so no need to change ?
I'm also open on adjusting in jbang if there is some case not covered.

It is an interesting question which raised some options and considerations which I took before implementing the magic as they are. I will try to be brief on it, but it will take some text since there are many things to be discussed.
I agree with your option to use // as the start of DEPS command. I think the reason is to be friendly with java compilation and also to be compatible with any Java editor which could be used to write jbang code. However, this works only for one line magic commands. I am wondering what could be used for multi line (or cell) magic commands?
I know, or at least this is my understanding from a limited research over jbang documentation, that you do not have to treat the case of a cell magic command. For notebooks is simple to define a multi-line magic commmand, that would be limited by cell itself. This is not available in a Java file, thus a terminal marker is needed. Additionally, in order to be compatible with Java editors, I suppose it should stay also in a comment. For that there are two options: /**MAGIC_KEY ... */ or /*MAGIC_KEY ... */.
All the above treats the syntax problem. This can be solved with some effort. The benefit would also be that it eventually be compatible with running the same code from jbang with no additional changes. If you have other suggestions for syntax I would gladly hear. Especially because I don't fully like how multi-row magics looks, even if I am not able to identify what it is.
There is something else which is not syntax related and is about how dependency commands behaves.
In jbang there is a single one line command for importing dependencies. If one has to import multiple dependencies, that it write multiple lines or one line with those dependencies enumerated. One problem which I see here is conflict dependencies. What happens when there is a conflicting dependency issue? For illustration one can import two dependencies, both of them depending on the same third package, but with different versions?
I approached this problem in the following way. Dependency magics gives only instructions regarding which dependencies to be added to the current execution, but without actually collecting the dependencies. There is also the possibility to add dependency overrides which instructs the interpreter on how to resolve some conflicts. In the end, there is an one line command which starts actually the resolve process and bringing resources in the execution space.
Solving dependency after each //DEPS command brings some problems which I find hard to solve. For illustration we have the following scenario:

add dependency A which transitively requires B-1.0
add dependency C which transitively requires B-2.0
add override for B to version 2.0
resolve and collect

If add dependency do also the collect and resolve, that kind of scenario could not be solved. For some cases it can be solved in the sense that a proper order of declarations could solve that, but it seems to me much harder or error prone.
In the end, thank you a lot for you attention. I will try to make those things compatible, as I like the benefit of using into normal Java editors. I am inclined to make a double syntax available. But I am eager to hear your opinion regarding both syntax and semantic issues.

I solved without mima since I was not able o understand how one can manage conflicts. Postpone for later a study on that topic.


Update gitlab version

First of all, awesome! Thanks for all your effort, very much appreciated!
This looks good to merge (just a trivial .gitignore conflict-- don't worry about it) but I am still considering the impact of switching to the v4 API.

That works for me. Ideally both API's would be supported, but given you'd need two versions of the library that seems a bit hard. Maybe create a separate branch that's Gitlab API V4 friendly.


ASTNode::simplify has supralinear performance with deep nesting of expressions

Version
Yosys 0.39+1 (git sha1 f7153573c, ccache clang++ 14.0.6 -O0 -fPIC)
On which OS did this happen?
Linux
Reproduction Steps
Run yosys stackoverflow.v -p hierarchy while commenting out some of the 512 levels of nesting (with stackoverflow.v being the example from https://github.com/YoWASP/yosys/issues/37) and observe time plus stack usasge, for example with valgrind --tool=drd --main-stacksize=16777216 --show-stack-usage=yes.
Expected Behavior
Time is linear in input size.
Actual Behavior
Time is quadratic in input size:

(link to the spreadsheet)
LibreOffice Calc provides the following polynomial fit:

Also, using 24.5K per nesting level seems excessive and results in issues such as https://github.com/YoWASP/yosys/issues/37.

using 24.5K per nesting level

I ran massif on stackoverflow.v. In the peak snapshot, I can see
92.53% (3,345,110B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
->32.73% (1,183,104B) 0x720AB4: Yosys::AST::AstNode::clone() const (frontends/ast/ast.cc:253)
| ->32.69% (1,181,664B) 0x720BB7: Yosys::AST::AstNode::clone() const (frontends/ast/ast.cc:256)
| | ->32.63% (1,179,648B) 0x720BB7: Yosys::AST::AstNode::clone() const (frontends/ast/ast.cc:256)

and so on, there's a lot of deep copies of nodes. There's also a lot of memory spent on parser-constructed AstNodes. Edited massif.log. The sizeof(AstNode) is 288B according to a dump I did some weeks back. This means we need 85 AstNodes per ternary nesting level.

That's 24.5K of stack memory, not heap memory. (I'm sure heap use isn't great either, but that's not what I'm talking about.)
You only get 1M of stack on Windows and macOS, so beyond 80 levels or so Yosys crashes.

...right, of course.  valgrind --tool=massif --heap=no --stacks=yes ./yosys garbage/stackoverflow.v -p "hierarchy" says we get up to 1,335,808 bytes of stack, but can't attribute it to its sources. perf shows that AstNode::detectSignWidthWorker takes up 90% of the runtime.

Just noticed that we're raising the stack size in a linux ifdef in kernel/rtlil.cc


remove redundant code.

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

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

Thanks a lot for your contribution. Could you also help sign the CLA? @SimonCqk


"Open in Terminal" from Explorer doesn't load the system PATH variable

Windows Terminal version
1.15.2875.0
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce
This assumes PowerShell as your default shell. Adjust for cmd as needed.

Go to the start menu and find terminal and launch it. (Or use the run dialog).
Run $Env:Path and see that it lists everything in the users PATH as well as the system PATH
Open any folder in Explorer.
Right click and select "Open in Terminal"
Run $Env:Path and see that it lists only the users PATH.

Expected Behavior
Terminal should behave exactly the same no matter how it is opened.
Actual Behavior
Different PATH variables are loaded depending on where you loaded the terminal from. There appears to be no way to tell either, so some software behaves differently.

This seems to be duplicated with #12808 and #12602 which in turn seems to be duplicates themselves: https://github.com/microsoft/terminal/issues/12602#issuecomment-1060709230
@zadjii-msft You might have a better feeling which issue to best pick as the one to keep track of.

It seems that #12808 is the opposite of this one. It loads system but not user. I see user being loaded but not system.
#12602 could be either way round. Note: this happens to me even if no terminal processes are running, so it's not a WM_SETTINGCHANGE thing.


Create blog /blog 📰

Compile static html files from markdown to create blog posts, potentially using remark-loader
Each post should have its own URL stanflint.dev/blog/title-of-a-post

Site has switched to using svelte as a frontend framework since creating this issue


[New chain]: Linea Mainnet 1.4.1

Summary

https://github.com/safe-global/safe-deployments/pull/553
https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-59144.json

Chain ID
59144
Chain detail URL
https://chainlist.org/chain/59144
RPC URL
https://linea-mainnet.public.blastapi.io
Blockscout Client URL
No response
Etherscan Client URL
https://lineascan.build
Etherscan Client API URL
https://api.lineascan.build
Version
1.4.1
Address (Master copy)
0x41675C099F32341bf84BFc5382aF534df5C7461a
Deployment Tx hash (Master copy)
0x60994f9dd09e5c0d8d6bbc3ed9a00ce12ac23fd6f4667a26877fb8933a3bed80
Block explorer URL (Master copy)
No response
Address (Master copy L2)
0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Deployment Tx hash (Master copy L2)
0x839027c786c8cd0fdd7873c49f177f37a18443ef4384a7fbf7c7648aaf60b996
Block explorer URL (Master copy L2)
No response
Address (Proxy factory)
0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67
Deployment Tx hash (Proxy factory)
0xac77edf920af5ff3563a60e74dbc74739a37eab8ab9599c453cb2090250ca351
Block explorer URL (Proxy factory)
No response

/execute


[firebase_crashlytics] RangeError: Value not in range: -1

I'm seeing a RangeError exception at https://github.com/flutter/plugins/blob/f254cd2573db895d927abeff1e2b7a1dfb177b1b/packages/firebase_crashlytics/lib/src/firebase_crashlytics.dart#L189
  List<Map<String, String>> _getStackTraceElements(List<String> lines) {
    final List<Map<String, String>> elements = <Map<String, String>>[];
    for (String line in lines) {
      final List<String> lineParts = line.split(RegExp('\\s+'));
      try {
        final String fileName = lineParts[0];
        final String lineNumber =
            lineParts[1].substring(0, lineParts[1].indexOf(":")).trim();
        final String className =
            lineParts[2].substring(0, lineParts[2].indexOf(".")).trim();
        final String methodName =
            lineParts[2].substring(lineParts[2].indexOf(".") + 1).trim();

line is set to "package:flutter/src/foundation/assertions.dart 519:9     new FlutterError.fromParts.<fn>" and the className line throws an exception because lineParts[2] is new which doesn't contain a ..
I would add more information but this bug seems pretty self-explanatory :)
The bug was introduced by the new code in https://github.com/flutter/plugins/pull/1080
@kroikie @collinjackson Could you guys take a look?

@matthewlloyd
The issue at https://github.com/flutter/flutter/issues/32178 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @rmtmckenzie
I see the merged PR
may I close this issue?
Thank you

@iapicca Since it's merged I don't see why not. Thanks!

thanks @rmtmckenzie


Blacklist @_resources from views

Currently, the @_resources instance variable that decent exposure encapsulates is still available in the views. Normally this is not an issue since the exposures are lazily evaluated and if the view is the first to call the defined helper method then @_resources will always be nil. However if the controller is the first to access the exposure for whatever reason, the value will be in the resources hash and also in the view.
This pull request explicitly blacklists the @_resources instance variable so it is now truly encapsulated by the controller.

Durran,
Nice! Thanks for this. At the risk of climbing onto my soapbox, this once again exposes the brokenness of using instance variables as an interface.
In other news, have you checked out the "nunu" branch at all? It represents what will become decent_exposure 2.0. I'm thinking that this patch should apply for it as well.
What say you, @voxdolo, shall we merge?

Just verified it locally. Works as advertised and is a good idea in general (and should be included in the nunu branch). Thanks D!  Consider it merged.


Support Nullmarked on module-info (JPMS)

If a module-info exists and it has the Nullmarked annotation, all packages contained within should be treated as though they are also Nullmarked unless they are NullUnmarked, and etc... you get it. I know this behavior is desired, so this is mostly just so it can be tracked.

We should and will eventually support this.  But generally speaking, at this point it doesn't seem like a library can rely just on annotating module-info to get the desired behavior; see https://github.com/jspecify/jspecify/issues/496#issuecomment-2532696315


Running next build fails due to a TypeError

When running next build I have the following error :

./node_modules/next-firebase-auth-edge/src/auth/auth-request-handler.ts:240:11
Type error: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type 'UpdateRequest & { deleteAttribute?: string[] | undefined; deleteProvider?: string[] | undefined; linkProviderUserInfo?: (UserProvider & { rawId?: string | undefined; }) | undefined; photoUrl?: string | ... 1 more ... | undefined; disableUser?: boolean | undefined; mfa?: { ...; } | undefined; localId: string; }'.
No index signature with a parameter of type 'string' was found on type 'UpdateRequest & { deleteAttribute?: string[] | undefined; deleteProvider?: string[] | undefined; linkProviderUserInfo?: (UserProvider & { rawId?: string | undefined; }) | undefined; photoUrl?: string | ... 1 more ... | undefined; disableUser?: boolean | undefined; mfa?: { ...; } | undefined; localId: string; }'.

Runtime : node@18
NextJS version : 14.0.3

Hello @jntakpe,
Could you provide your tsconfig.json?

Thanks for reporting.
I could not reproduce the issue you're having in<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>Could you provide output of npx next info command?
I am interested in typescript version you're using

Operating System:   Platform: darwin   Arch: arm64   Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:34 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8103 Binaries:   Node: 20.10.0   npm: 10.2.3   Yarn: 1.22.19   pnpm: N/A Relevant Packages:   next: 14.0.3   eslint-config-next: 14.0.2   react: 18.2.0   react-dom: 18.2.0   typescript: 5.2.2 Next.js Config:   output: N/A

Hey @jntakpe! I am unable to reproduce the issue with starter example and provided configuration. Is there a chance you could create a public repository affected with the issue?

Closing the issue as outdated


[test](ES Catalog)Add mapping _routing test case (#42074)

Proposed changes
bp #42074

run buildall


Add examples for Ingress

Add 3x examples for Ingress:

Matching any IP
Matching a single domain name - without TLS (express.example.com)
Matching a single domain name with TLS (express.example.com) - use Ingress annotations from cert-manager to indicate the certificate should be provisioned automatically from LetsEncrypt. Add a staging HTTP01 Issuer definition.

I'll take this up :)

Thank you 👍

If @utsavanand2 can't get to this, I can pick it up, lmk 👍 !

PR #3 Resolves this issue


adding ssh-rsa keys for harshalgupta

adding harshalgupta rsa keys

Can one of the admins verify this patch?

Harshal is in the Reliance Jio Cloud storage team, reports to Abhishek.

ok to test

please test this

please test this

please test this

Merging pull request as both checks have passed, and the modifications are to the correct files.


feat(ProofTheory): Define logical symbols abstractly; opens new top-level section, drawing from lean4-logic

I'll add some brief comments since @YaelDillies pinged me, but I don't have strong opinions here; my interests are in using logic for formalization rather than formalizing logic.
I am not sure about the value of including a general proof theory library in Mathlib. There is a long tradition of computer scientists formalizing proof-theoretic stuff on the Coq model of doing it in small, independent projects. That's because the formalizations tend not to be very reusable. Projects are generally self-contained and don't depend on one another, and people like to use their own notation and idiosyncratic setups. In other words, people generally prefer to implement the specific logical systems they are interested in from scratch and optimize the implementation to the specific applications they have in mind, rather than taking over infrastructure that someone else has designed.
To be clear: I have no objection to merging this PR and indeed no strong opinions either way,  but I am guessing that it won't be a very actively used corner of Mathlib. @digama0 has thought about things like this -- similar questions come up with formalizations of the simply typed lambda calculus -- so I am curious to hear what he thinks. It might be nice to have a canonical proof theory development in Mathlib as a model that others can modify and adapt for their own purposes.
Two small comments: logic currently plays a big role in the model theory library, so it's worth asking how this PR fits with the syntax there (https://leanprover-community.github.io/mathlib4_docs/Mathlib/ModelTheory/Syntax.html) and whether unifying them will have any benefits. Also: these definitions of conjunction and disjunction over a finset are noncomputable but I can't imagine any applications where conjunction and disjunction aren't AC operations, in which case one can stay computable and use Finset.fold.

Also: @fpvandoorn has formalized a lot of logic (including model theory and proof theory), so it would be good to hear from him as well.


Processor plugins

Alongside importer plugins, we should create processor plugins that run on a raw Dataset after import to create a derived dataset. Any raw Dataset can link to zero or more derived Datasets. For phase 1, the actual processor functions can be simple and useless.

I'd say for phase 1 the processor functions can be a mix of "useless", demo functions, and ones that drive our phase 1 use case workflows.

@annehaley, we have a working job running infrastructure in place, along with a couple of "dummy" computational routines, right? That is probably enough to call this closed--we can add more such processor modules alongside those dummy ones. What do you think?

Absolutely. we just changed the name for what was originally discussed as "processors" to "jobs". Closing with reference to #26.


Remedy Incident Plugin

@gokumar please review. plugin (Incident) is ready for QA.

Updated library with pre-parsing feature.
Works with minimal field mapping required.

LGTM


[ADAP-669] [CT-2779] [Bug] Incremental model merge/drop queries missing the dbt app comment to identify as dbt query

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The merge query and the drop table query that are sent to BigQuery for incremental models that use the insert/overwrite+dynamic strategy are missing the comment on the first row, which includes a JSON string to identify the query as being issued from dbt along with the dbt version, which looks like this: "/* {"app": "dbt", "dbt_version": "1.5.1", "profile_name": ...............*/"
Expected Behavior
The merge query and the drop table query that are sent to BigQuery for incremental models that use the insert/overwrite+dynamic strategy include a comment on the first row, which includes a JSON string to identify the query as being issued from dbt along with the dbt version, which looks like this: "/* {"app": "dbt", "dbt_version": "1.5.1", "profile_name": ...............*/"
Steps To Reproduce
Use the below config to setup a incremental model using the insert/overwrite dynamic strategy, the perform 2 dbt runs, the first one will do a full refresh and the second will do an incremental run, which includes 3 queries: create tmp table, merge using tmp table, drop tmp table. The last 2 steps of merge and drop will not have the dbt app comment on the first line of the query, or anywhere in the query body.
Relevant log output
No response
Environment
- OS: Win 11
- Python: 3.11.4
- dbt: 1.5.1

Which database adapter are you using with dbt?
bigquery
Additional Context
No response

Hello! Thanks for opening up this issue. Are you interested in contributing this fix?
I'm also going to tag @Kayrnt (who I've been told is a bigquery incremental expert)

Who's the snitch 😏 ?
I've had a look and could reproduce it on latest version.
At least not on the mentioned intermediate queries.
Yet some of them missed it and therefore I opened a PR to fix it (see )
For instance, I had a quick test on a model
{{ config(
    materialized="incremental",
    incremental_strategy="insert_overwrite",
    partition_by={
      "field": "_partition",
      "granularity": "day",
      "data_type": "timestamp",
      "time_ingestion_partitioning": True,
      "copy_partitions": True,
    },
    on_schema_change='append_new_columns'
) }}

SELECT
    timestamp_trunc(CURRENT_TIMESTAMP(), day) as _partition,
    'some value' as col1

then it generated
/* {"app": "dbt", "dbt_version": "1.6.0b8", "profile_name": "default", "target_name": "dev", "node_id": "model.dbt_queries.test_bug_copy_partition"} */

     -- Clean up the temp table
  drop table if exists `my_test_project`.`dbt_cou`.`test_bug_copy_partition__dbt_tmp__b6954f0d-18cb-4d3f-b7b0-cd3257c4652a`


Document how to use the proxy from a Proxy SDK

Hello again,
It is not super clear that UNLEASH_PROXY_SECRETS corresponds to clientKey when creating the client from the JavaScript Proxy SDK.
To make it easier to get started, maybe an example in the README after the list of Proxy SDKs might clarify? Or just mention that the secret should go in clientKey.
Or even change clientKey to proxySecret?

Second that. clientKey seems a much better name and sounds similar to what i.e. Sentry or Stripe would suggest using.

It makes sense. To not break existing configurations we should probably just support both in parallel (at least the env variable) but start migrating towards CLIENT_KEYS or PROXY_CLIENT_KEYS ?

@ivarconr yea, sounds like a good idea! As for the naming, I'd go either for PROXY_CLIENT_KEYS or PROXY_PUBLISHABLE_KEYS.
Stripe calls it a "Publishable" key to distinguish from "private" keys – this way people know that it's ok to keep it in the open. It's a great developer experience because you don't have to think twice, but also that would be a non-trivial effort to introduce a new name across different Unleash packages.


Fix panics when subcommand is missing

Ticket
https://github.com/mattermost-community/mattermost-plugin-google-drive/issues/41
Test cases
Use the ticket description for testing
Also worth doing a quick sanity test on receiving notifications for comments, deleted comments and resolved commets. Make sure the received message is formatted correctly as before

Looks good. I took a quick search through the codebase and found a few more similar cases where we are accessing by index, but not checking the size of the slice:
https://github.com/mattermost-community/mattermost-plugin-google-drive/blob/269439f5076f7051a5428845583700e0f098b8d9/server/plugin/notifications.go#L118
https://github.com/mattermost-community/mattermost-plugin-google-drive/blob/269439f5076f7051a5428845583700e0f098b8d9/server/plugin/notifications.go#L147
https://github.com/mattermost-community/mattermost-plugin-google-drive/blob/269439f5076f7051a5428845583700e0f098b8d9/server/plugin/notifications.go#L153
https://github.com/mattermost-community/mattermost-plugin-google-drive/blob/269439f5076f7051a5428845583700e0f098b8d9/server/plugin/create.go#L41-L42
I don't know if these are issues, but I thought I'd point them out. If they are, might be a good opportunity to knock these out, too 🙂

Thanks for finding those, those responses are coming from Google but it's worth double checking their indexes exist. I'll push a fix for those in a sec

@davidkrauser I think I covered any potential panics, any function that calls getCommentUsingDiscussionID is already protected from a panic so I didn't add an extra check to those

I have tested the slash commands without arguments and the plugin is not panicking anymore. LGTM Also I saw that you have added a new feature to show the user's name and the user image who has created the document. I looked around it a little and it is working fine, but maybe like do want me to test some more edge cases around it? If so please do let me know,

Thanks for checking Arush, I don't think it's possible to manually test that because Google would have to omit some fields from it's response in order to trigger that code path


Latest version in HelmRelease does not pull expected version from OCI Registry

Describe the bug
The registry contains helm charts the versions 0.9.0, 0.10.0, 0.11.0, ...
When I configure a HelmRelease with the version "0.*", the helm chart with version 0.9.0 is pulled. Expecting the highest version to be pulled.
HelmRelease:

spec:
  interval: 1m
  chart:
    spec:
      chart: demoapp
      version: "0.*"
      sourceRef:
        kind: HelmRepository
        name: my-helm-repo
        namespace: gitops-flux-configuration
      interval: 1m

The problem ONLY occurs if the HelmRepository references an OCI Registry.
For testing purposes I switched to a dedicated Helm Repository in artifactory and the expected latest version was pulled.
I tried several different values for version in the HelmRelease resource:

version: "0.*"
version: "0.x.x"
version: "*"

All with the same result: Version 0.9.0 of the helm chart is pulled.
I encountered the problem last week with the new release of the source controller and have the same result after updating to the Flux v0.31.0 release today.
Can anyone confirm this behavior?
Steps to reproduce
Setup HelmRelease and HelmRepository resources to pull a version range from an OCI registry.
Provide multiple versions of the helm chart in the docker registry e.g. 0.9.0, 0.10.0, ...
Expected behavior
Latest version of the helm chart is pulled. (i.e., the one with the highest version)
Screenshots and recordings
No response
OS / Distro
N/A
Flux version
v0.31.0
Flux check
N/A
Git provider
No response
Container Registry provider
Artifactory
Additional context
No response
Code of Conduct

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

fixed in https://github.com/fluxcd/source-controller/pull/769


Setting nested field

Bug Description
With those 2 definitions:

use pyo3::prelude::*;

#[pyclass]
#[derive(Debug, PartialEq, Clone)]
pub struct Beta {
    #[pyo3(get, set)]
    pub field: i32,
}

#[pymethods]
impl Beta {
    #[new]
    pub fn new(field: i32) -> Self {
        Beta { field }
    }
}

#[pyclass]
#[derive(Debug, PartialEq, Clone)]
pub struct Alpha {
    #[pyo3(get, set)]
    pub beta: Beta,
}

#[pymethods]
impl Alpha {
    #[new]
    pub fn new(beta: Beta) -> Self {
        Alpha { beta }
    }
}

You can do (in a python script):

import testlib

if __name__=="__main__":
    beta = testlib.Beta(field=1)
    alpha = testlib.Alpha(beta)

    print(alpha.beta.field) # prints 1

    alpha.beta.field = 2

    print(alpha.beta.field) # still prints 1!

The workaround would be to set alpha.beta into testlib.Beta(field=2), but this style does not scale well with multiple fields and more nested ones.
Steps to Reproduce

Clone the repo ntakouris/pyo3-set-nested-field-bug and cd into it
pip3 install .
python3 usage.py should print 1 and 1 instead of 1 and 2
View usage.py content

Backtrace
No response
Your operating system and version
Ubuntu 20.04.3 LTS
Your Python version (python --version)
Python 3.8.10
Your Rust version (rustc --version)
rustc 1.58.0 (02072b482 2022-01-11)
Your PyO3 version
0.15.1
How did you install python? Did you use a virtualenv?
apt
Additional Info
No response

This is not possible to change with the structs as defined. On attribute access, PyO3 must clone the member (in this case alpha.beta) and therefore the field is set on the copy.
If you need such hierarchies to work, you need to make at least the Alpha::beta field a Py<Beta>, so that PyO3 can hand out references without problems.

@birkenfeld so, no support for types that are copied by default like ints

Not sure what you mean here? An int is immutable anyway, so this is no issue for ints.

In this case an int is passed by value, so there's no need to reference count / use Rc<RefCell<>> and/or Py<Beta>,for it be implemented. Unless I am missing something.

field itself is fine to stay as a simple int field. The problem lies in the intermediary Beta. The Python code
alpha.beta.field = 2

is the same as
tmp = alpha.beta
tmp.field = 2

and in the first line PyO3 clones the Beta for tmp, since it cannot hand out a Rust reference to it.
If Alpha has beta: Py<Beta>, the beta field is already a Python object and PyO3 can just hand out a new Python reference to it.

See also #1358. I'd love to make this more ergonomic one day!


Add workflows and workflow templates for PR decoration with test reports

Proof of functionality:

A PR without a report-config.yml:

PR: https://github.com/turing85/quarkus-artemis/pull/14
Initial comment is not posted: https://github.com/turing85/quarkus-artemis/actions/runs/10802614248
Build runs normally: https://github.com/turing85/quarkus-artemis/actions/runs/10802614245
Reports are not created: https://github.com/turing85/quarkus-artemis/actions/runs/10802711846

A PR with report-config.yml:

PR: https://github.com/turing85/quarkus-artemis/pull/13
Initial comment is posted: https://github.com/turing85/quarkus-artemis/actions/runs/10802375811
Build runs normally: https://github.com/turing85/quarkus-artemis/actions/runs/10802375881
Reports are created: https://github.com/turing85/quarkus-artemis/actions/runs/10802531966

@gastaldi just for completeness: I updated the samples with fresh runs against the most recent version.


Use new ESRI source for Clark County, WA

Thanks to some discussion with the team at TriMet, we learned that there is now a web portal for data from Clark County, WA.
So, unlike in the past, we won't need @nvkelso to order a DVD to his address to get the most up to date data.
More details can be found at the following places:
https://hub-clarkcountywa.opendata.arcgis.com/datasets/7ee0659e52a14986b1958df0499fd456_0
https://gis.clark.wa.gov/gishome/metadata/#/layer/6279
https://services2.arcgis.com/ylxwjFBdCPBzP16d/arcgis/rest/services/SitusAddress/FeatureServer/0/query?outFields=*&where=1%3D1
https://gis.clark.wa.gov/mapsonline/index.cfm?
https://gis.clark.wa.gov/gishome/

re-run this please


environment problem in qat for stable diffusion

I followed
pip install intel-extension-for-transformers
pip install -r requirements.txt
pip install transformers==4.34.1

but there exists hugging-face version conflict, and I checked dependabot's advice(#981) upgrade transformers version to 4.36.0.
It threw an error like
loaded_sub_model = load_method(os.path.join(cached_folder, name), **loading_kwargs)
  File "/home/miniconda3/envs/qat/lib/python3.9/site-packages/transformers/modeling_utils.py", line 2863, in from_pretrained
    raise ImportError(
ImportError: Using `low_cpu_mem_usage=True` or a `device_map` requires Accelerate: `pip install accelerate`

it seems a problem from transformers, what's the right way to create the environment?

https://github.com/intel/intel-extension-for-transformers/blob/main/examples/huggingface/pytorch/text-to-image/quantization/qat/requirements.txt
please install the requirements.txt under the qat example folder.


Bryson Mundia

What Do you think?

@AllanRegush image displayed seems to be incorrect (just noticed it)

Good Catch @HariAcidReign


Use provided region when creating S3 bucket

Currently if the bucket does not exist, its is created by the plugin. However, the region in which it's created is us-east-1, no matter what the configured region is. I would like to create a PR for this if this project is maintained.

cc @sullis

https://github.com/gilt/sbt-aws-lambda/pull/48


Governance. Off-chain data source. CORS error for subsquare

Description
When user switch off-chain data source to subscare - that fall down with CORS error
Steps to Reproduce

Go to settings page
Switch data source to Subsquare
Go to Referenda page

Expected Behavior
Get off-chain data from the subsquare
Actual Behavior
Request fall down with CORS error

Environment
https://github.com/novasamatech/nova-spektr/commit/285a866ace2a82902e4c1017492b05e98a657e6f

Reproduced on the dev build only.


Partition explainer PyTorch support

Hi, thanks for your work!
This is the updated #2400 PR.
Summary:

Partition explainer supports torch classification models.
New Jupyter notebook example with PyTorch.

Thanks again! This looks good. See my one comment on the save_name option.

Hi, thanks for the answer and the review!


Infinite navigation on redirects

Describe the bug
If i throw the redirect error inside beforeLoad for component or inside parent layouts for the same location.href - i got an infinite redirects.
Your Example Website or App
It doesn't metter
Steps to Reproduce the Bug or Issue
I'am on /wizard/choice route
My file structure
- _auth.tsx
- _auth.wizard.choice.tsx

export const Route = createFileRoute('/_auth')({
	beforeLoad: async ({ context, location }) => {
		const auth = getAuth(context.app)
		await auth.authStateReady()

		if (!auth.currentUser) {
			throw redirect({ to: '/wizard/choice', replace: true })
		}
	},
	component: AppLayout,
})

Expected behavior
Ignore redirect on the same pathname or location.href
Screenshots or Videos
No response
Platform

macOS
Chrome
"@tanstack/react-router": "^1.35.1"

Additional context
No response

can you please provide a minimal complete example by forking one of the existing examples on Stackblitz?

I had the same issue, in my case I noticed I was not handling the auth in redirected route leading to infinite redirects.

closing this as no further information was provided


Incompatible with ruby2ruby 1.3.1

When Bud is used with ruby2ruby 1.3.1, the tc_temp and tc_wc tests fail.

The tc_wc issue turned out to be a bug in ruby2ruby 1.3.1 -- for now, 5d48d8b31fd7878f0ef05b25a3053f207d8f1245 makes ruby2ruby < 1.3.1 a Bud dependency, until the R2R bug is fixed by upstream.


iPTMnet

integrate iPTMnet "Interactive Sequence view"
at least as an image
see here for an example:
http://research.bioinformatics.udel.edu/iptmnet/entry/P06493/
also their sequence alignment is cool, see here
http://research.bioinformatics.udel.edu/iptmnet/visual/msa/tree/P06493/

It would be great if this is available as a web service (I think we have asked about this already?).
There is a bug if you click  try the browse option and click 'fission yeast' (needs reporting)

We can link to this view quite soon
http://research.bioinformatics.udel.edu/iptmnet/entry/Q09170/
but ideally long term we would want to
a) enbed widget in gene  page
b) with ability to  toggle the alignment view on the fly?
c) widget would ideally also display extension on mouse over (added by, removed by etc)

Also look at
dbPAF: an integrative database of protein phosphorylation in animals and fungi.

again, will be very cool....

as a first step, added to external links for #477

duplicate
https://github.com/pombase/website/issues/143


firefox: pin icu to 72, fix timezone issue

Description of changes
temp workaround for https://github.com/NixOS/nixpkgs/issues/238025
after recent update to icu73, firefox fails to detect local timezone
this is caused by https://github.com/unicode-org/icu/pull/2323 interacting with firefox sandbox
I've filed a bug upstream https://bugzilla.mozilla.org/show_bug.cgi?id=1839287
meanwhile I think just pinning icu for firefox is ok, alternative fix could be wrapping firefox in TZ=:/etc/localtime
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Updated the commit message to use the correct attribute and expanded on why this issue happens.
Unfortunately I could not reproduce this locally, but I'm not opposed to pinning to icu72 if it helps users and the issue gets tracked upstream.

@mweinelt thank you,
two questions

should we backport this to 23.05 ?
since you are not the first who cant reproduce the issue, is it hard for you provide to build-vm setup that I can have a look at ? ( curiosity )

Backport in https://github.com/NixOS/nixpkgs/pull/238853.


Colour Temp not correct after home assistant core update.

Home Assistant Adaptive Lighting Issue Template
Bug Reports
If you need help with using or configuring Adaptive Lighting, please open a Q&A discussion thread here instead.
Before submitting a bug report, please follow these troubleshooting steps:
Please confirm that you have completed the following steps:

[x] I have updated to the latest Adaptive Lighting version available in HACS.
[x] I have reviewed the Troubleshooting Section in the README.
[x] (If using Zigbee2MQTT) I have read the Zigbee2MQTT troubleshooting guide in the README.
[x] I have checked the V2 Roadmap and open issues to ensure my issue isn't a duplicate.

Required information for bug reports:
Please include the following information in your issue.
Issues missing this information may not be addressed.

Debug logs captured while the issue occurred. See here for instructions on enabling debug logging:

[home-assistant_2024-02-07T15-28-58.723Z.log](https://github.com/basnijholt/adaptive-lighting/files/14195890/home-assistant_2024-02-07T15-28-58.723Z.log)

Your Adaptive Lighting configuration:

[ALConfig_Home.txt](https://github.com/basnijholt/adaptive-lighting/files/14195964/ALConfig_Home.txt)

(If using Zigbee2MQTT), provide your configuration files (remove all personal information before posting):

devices.yaml
groups.yaml
configuration.yaml ⚠; Warning REMOVE ALL of the PERSONAL INFORMATION BELOW before posting ⚠;

mqtt: server:
mqtt: user:
mqtt: password:
advanced: pan_id:
advanced: network_key:
anything in log_syslog if you use this

Brand and model number of problematic light(s)

[configuration_yaml.txt](https://github.com/basnijholt/adaptive-lighting/files/14195891/configuration_yaml.txt)
[groups_yaml.txt](https://github.com/basnijholt/adaptive-lighting/files/14195892/groups_yaml.txt)

Brand: Philips Hue White Ambience Light bulbs (A60 – B22 smart bulb – 1100)

Describe the bug and how to reproduce it:

When upgrading the Home Assistant Core form 2023.12.4 to any later update (2024.1.1 - 2024.1.6) the lights in the 'Home' adaptive lighting entry (config attached) default to the lowest colour temperature and will not change to a whiter colour temperature no matter what time of day it is.
Restoring the update reverts the functionality to as expected - white during the day and redder at night as per the settings.
All lights are Hue 'White Ambience' bulbs connected via the Hue Home Assistant integration.

Steps to reproduce the behavior:

Update home assistant core from 2023.12.4 to any later update.
Lights automatically transition to warmest light temperature.

I believe this is not the same issue as #902 and #893 as the brightness is consistently correct i.e. brightness stays 100% even though the colour temperature is not correct.


added a class for the page numbers in the pager so you can easily style them in re…

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
It's hard to style the pager because all items are list elements with no class.
https://github.com/swimlane/angular2-data-table/issues/267
What is the new behavior?
You can now style the numbers in the pager like you want. In my case i just hide them on mobil views, because you can scroll....
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Awesome! Thanks!

+1

How can I fix this problem ?


Tweak Parse and SILGen to support loading swiftinterface files

Handle accessors, initializers, and deinitializers without bodies, which will all appear in textual interface files.

@swift-ci Please smoke test

@swift-ci Please smoke test

Whoops, this breaks deinit \n override func test().

@swift-ci Please smoke test

…still got it wrong. I should just run the full test suite locally before the next try.

@swift-ci Please smoke test

@swift-ci Please smoke test


"watch dusage" fails with TypeError sometimes

Hi, I'm trying to use watch dusage to monitor the number of files while installing bigger conda environment. The command worked at the beginning, but now it usually gives me the error message below:
dusage v0.1.0
Traceback (most recent call last):
  File "/cluster/bin/_dusage/dusage", line 324, in <module>
    main()
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/cluster/bin/_dusage/dusage", line 309, in main
    print(tabulate(table, headers_blue, tablefmt="simple", stralign="right"))
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/tabulate.py", line 1555, in tabulate
    + ["\t".join(map(_text_type, row)) for row in list_of_lists]
  File "/cluster/bin/_dusage/venv/lib64/python3.6/site-packages/tabulate.py", line 1555, in <listcomp>
    + ["\t".join(map(_text_type, row)) for row in list_of_lists]
TypeError: __str__ returned non-string (type ColorfulString)

Thanks for reporting! I am looking into it ...

I confirm that I see the same with watch dusage (this will simplify debugging). Can you confirm that everything looks normal when you run it manually but it starts to break down when run through watch?

Yes, I haven't seen the error yet when using dusage manually. watch dusage worked for a few minutes and then resulted in the error that it kept showing on each attempt afterwards.

Thanks. I am looking into it.

watch dusage seems to work on Saga and Betzy but does not seem to work on Fram. I am unsure why. I am thinking of adding a flag where you can disable colors because without colors it works also on Fram.

I have another idea how to solve it ... working on it.

I need to think more about it. I could introduce some hacks/workarounds but I am hesitant because I don't understand why it fails. I know this is not satisfactory but for the moment I recommend to not use it through "watch". I need to think and experiment more to understand the issue.

Thanks for looking into it! I didn't expect / know that watch would make the execution so different from the normal invocation, but I guess sometimes these things turn out to be more complicated than expected...

I thought more about it and will add a flag to display without colors and then it works. I tried some other things but it never quite worked but this should work. There is some subtle interplay of terminal and terminal colors but it's a bit of a rabbit hole.

As an example: watch has a --color flag which can be made to work but the colors end up messed up. So something is incompatible there or outdated. I am working on a fix.

I added an option --no-colors in 4d3cff69059cb095741eaba3e7eadde3771f665e.
Now you can do: watch dusage --no-colors

Maybe use os.isatty() to make a sensible default choice?

Thanks! I will test it.

... or a try/except solution to this.


update web_sys::Geolocation to latest webidl

This PR updates the Geolocation webidl files to the latest version of the spec.
That the Geolocation webidl description is not up to the latest spec also came up in #2491.
The update is based on https://www.w3.org/TR/geolocation and more specifically the version https://www.w3.org/TR/2021/WD-geolocation-20210607/.
Changes in the PR

rename: Position -> GeolocationPosition
rename: PositionError -> GeolocationPositionError
rename: Coordinates -> GeolocationCoordinates

Testing

basic geolocation accessor test (though only tested in Firefox Linux 89.0 64-Bit and Chromium Linux 91.0.4472.77 64-Bit)
tested with a sample application on Firefox Android 89.1.1

Browser support
According to the respective MDN pages, the supported browser versions are

Geolocation
** Chrome  50 (2016-04-13)
** Edge    79 (2020-01-15)
** Firefox 55 (2017-08-08)
GeolocationPosition
** Chrome  79 (2019-12-10)
** Edge    79 (2020-01-15)
** Firefox 72 (2020-01-07)
GeolocationPositionError
** Chrome  79 (2019-12-10)
** Edge    79 (2020-01-15)
** Firefox 72 (2020-01-07)
GeolocationCoordinates
** Chrome  79 (2019-12-10)
** Edge    79 (2020-01-15)
** Firefox 72 (2020-01-07)
PositionOptions
** Chrome  50 (2016-04-13)
** Edge    79 (2020-01-15)
** Firefox 55 (2017-08-08)

The dates are either for the interface renaming,
or for when the required secure-context for the API is supported.
According to CanIUse linked in the spec, it should also be supported by all major browsers.
Please let me know of any topics that should be addressed, since this is my first contribution to web_sys.
For creating this PR, I used https://rustwasm.github.io/docs/wasm-bindgen/contributing/web-sys/supporting-more-web-apis.html as a reference, that I was pointed to on Discord.

@alexcrichton thanks for the feedback.
I can not answer completely, if the API does not fully work in any browser. The only information I can provide is the summary from the MDN pages.
But with the a current Chrome/Firefox and the current web-sys API description you can for example call geolocation.get_current_position() and receive objects.
However, they are not of the types that are mentioned in the API.
More details are described in #2491 by @torhovland, where had to manually implement the types that are changed in this PR.
I can fully understand, if this breaking change may not be mergeable right now.
As far as I understand, it is currently also not possible detect and translate older APIs to the latest one in the generated code.

I think breaking changes are fine as long as the old API is basically defunkt, we weren't super strict in our initial import of WebIDL from Firefox. Can you confirm that the changed APIs here don't work in browsers though? With that I think this is fine to merge.

@alexcrichton I think the main question is, how to define defunkt :-)
The current API can be called in the browsers I tested

basic geolocation accessor test (though only tested in Firefox Linux 89.0 64-Bit and Chromium Linux 91.0.4472.77 64-Bit)
tested with a sample application on Firefox Android 89.1.1

However, the returned values do not match the existing IDL type definitions for the browsers tested by me.
The workaround as described in #2491 and the accompanying blogpost is to implement the 'missing' types manually.
Those 'missing' types are changed by the updated IDL files in this PR and with these changes I was able to use the generated API without the manual type definitions.
Unfortunately, I can not provide more pro's and/or con's than this description, since I do not have more platforms available with which I could test and I am not sure, what implications this breaking change will result in for existing users of this API (if there are any).

Hm ok, sorry but this is a lot of breakage to stable APIs, so I'm not confident enough to merge this at this time. Unfortunately there are no plans for a web-sys major version bump at this time, so this is unfortunately stuck :(. I don't really have a great idea how to fix this easily.

@alexcrichton thanks for the feedback. And as stated previously, I totally understand if this can not be merged as of yet.
I did a bit more digging and if I am not mistaken, the changes were introduced to the spec in Februrary 2019 according to this commit (https://github.com/w3c/geolocation-api/commit/de3d4ee2d23fb957e307ad74a73d8e912ea7c2cb).
It is a bit difficult to find out, since the IDL file is not maintained as a dedicated files in the repository.
The pages caniuse.com and wpt.fyi also do not provide details on which the oldest browser version is that support the new API. So the only data is the one I got from MDN in the PR description.
I will leave the PR open until a solution can be found. And for my project I will probably go ahead and copy the generated files directly into the project's repository.

For anyone interested in updated bindings, I added the generated files from this PR to a gloo-like create for geolocation here https://gitlab.com/mkroehnert/mk-geolocation.
Please not that the lib is provided as is.
It is not fully finished since it is currently only used in a personal project and will be without regular maintenance/updates.
Therefore please check the Warnings section of the README before using.


Overfitting when further pre-training MPT-7b

Hey guys.
I am further pre-training the MPT-7b model on ~700mb of text.
The model is learning and the validation metrics improve over the optimization period, but in inference time I get awful results often repeating a single word. I am testing some 350ba to ~700ba of training.
I am using 4 A100 80gb cards and following the docs of the repo concerning data pp and training.
Any idea how to overcome this?

Just curious what's your batch size and how many epochs are you training your data on?

I used the default global_train_batch_size: 1024 (in the pretrain/MPT-7b.yaml) and trained for 750ba. I noticed the config does not mention epochs but "ba" which I inferred as batches.

Do you want to try seeing max_duration to be 1ep or 2ep (something like max_duration: 2ep)?

There might also be a bug as of right now with training with AliBi if that is what you are training with that we are trying to fix. Are you seeing a warning where some weights aren't being initialized when loading in a checkpoint at inference time? If so, include model.config_overrides.learned_pos_emb: false in your yaml

I will try to set the max_duration to 1-2 ep and report back


bug with directive "replace" property

When i insert the value of attribute with same name as one of the isolate scope property into directive template. Space symbol is appended to scope property.
http://jsbin.com/bohicegaka/3/edit?js,console,output

Is this a duplicate of https://github.com/angular/angular.js/issues/8132?

yas it's duplicate.

replace: true is deprecated. As noted in the linked issue, this bug will not be fixed.


Bireme启动正常，maxwell的Mysql 同步至Greenplum，在mysql中插入数据greenplum中没有反应。。。

12:56:50 INFO  Bireme - Start getting metadata of target tables from target database.
12:56:50 INFO  Bireme - Finish getting metadata of target tables from target database.
12:56:50 INFO  Bireme - Start establishing connections for loaders.
12:56:50 INFO  Bireme - Finishing establishing 1 connections for loaders.
12:56:50 INFO  ChangeLoader - Loader Start, corresponding table stg.test.
12:56:50 INFO  TaskGenerator - TaskGenerator Start.
12:56:50 INFO  Dispatcher - Dispatcher Start.
12:56:50 INFO  Provider mysql - Provider mysql Start.
请问哪里出问题了呢？

Please verify the content in kafka and check if bireme poll data from correct kafka topic.

emmm....It seems like maxwell was not working well...Thanks~


New version: TranslucentTB.TranslucentTB version 2<IP_ADDRESS>

Auto-updated by vedantmgoyal2009/winget-pkgs-automation
Microsoft Reviewers: Open in CodeFlow

@KevinLaMS

But winget install TranslucentTB should not install an old version. The version WinGet installs is old, broken on Windows 11, and not supported anymore.
Windows Terminal also depends on WinUI 2.6, and is updated regularly on WinGet, so what's up with that?

Worse even, while it does find a duplicate when the msstore source is enabled, it does not say which one is newer:

You should be able to find the version of the package by searching for it via winget search or by being specific with winget show:

Currently, the Microsoft Store API that WinGet depends on doesn't expose a version; so "Unknown" in this case is the latest version that you published to the Microsoft Store (Retail).

Windows Terminal also depends on WinUI 2.6+, and is updated regularly on WinGet, so what's up with that?

Windows Terminal ships with a pre-built version of WinUI 2.7 which is outside of the installation process.
I should have been a bit more clearer but this only affects applications that have Microsoft.UI.Xaml listed as a dependency (<Dependency></Dependency>) in their AppxManifest.xml file.

If the version WinGet distributes cannot be updated to something newer, then TranslucentTB should be removed entirely from WinGet.

PR was created for it: #44603


Reference Equations from Canuto

At the moment it is quite challenging to see exactly what is going on with the code. It would be useful if the equations used from the Canuto book can be referenced, that way the user can easily see what is going on.

Resolved in bb6b4be


nonexistent breakpoint on migration from 0.2.0 -> 1.1.1

Error:
A conditional value was caught referencing a nonexistent breakpoint.

ResponsiveValue requires a parent ResponsiveBreakpoint to reference breakpoints. Add a ResponsiveBreakpoint or remove breakpoint references.

I'm trying to migrate to 1.1.1, I just want to scale from 0 to 450 and resize when above 450, it worked perfectly on 0.2.0, but I cannot get it to work on 1.1.1 despite following the migration guide.
0.2.0 code:
Widget responsiveness(BuildContext context, Widget child) {
  return ResponsiveWrapper.builder(
    child,
    defaultScale: true,
    minWidth: 450,
    breakpoints: [
      const ResponsiveBreakpoint.resize(450, name: MOBILE),
    ],
  );
}

1.1.1 code:
Widget responsiveness(BuildContext context, Widget child) {
  return ResponsiveBreakpoints.builder(
    useShortestSide: true,
    breakpoints: [
      const Breakpoint(
        start: 0,
        end: 450,
        name: MOBILE,
      ),
      const Breakpoint(
        start: 450.1,
        end: double.infinity,
        name: 'rest',
      ),
    ],
    child: ResponsiveScaledBox(
      width: ResponsiveValue<double>(
        context,
        conditionalValues: [
          Condition.equals(name: MOBILE, value: 450),
        ],
      ).value,
      child: child,
    ),
  );
}

For anyone with the same issue. ResponsiveBreakpoints.builder and any ResponsiveFramework widget cannot be in the same build method. They have to be separated.
The solution was to take
ResponsiveScaledBox(
      width: ResponsiveValue<double>(
        context,
        conditionalValues: [
          Condition.equals(name: MOBILE, value: 450),
        ],
      ).value,
      child: child,
    )

To a separate widget/function.


Do not evaluate variadic template types

This is a workaround for an internal clang assertion that gets triggered
if we try to evaluate a variadic template type reference.
Fixes #283
r? @emilio

 Warning

These commits modify unsafe code. Please review it carefully!

Rebased and fixed the merge conflict :)

@bors-servo r=emilio

:pushpin: Commit 1c18ec7 has been approved by emilio

:hourglass: Testing commit 1c18ec7 with merge 94fff83...

:sunny: Test successful - status-travis


Debug root package

I am unsure if I am doing something wrong here..
Currently when I try to run continue and just Debug, it will try to execute the current package.
This often fails, as the package would not have a main and thus not be executable.
Is it possible to somehow specify that a configuration that tries to debug the root package of the project, rather than the currently open file?

I am unsure if I am doing something wrong here..

Hey! no problem.. I don't understand exactly what you are doing. When you start the debug session, which option you select from the list? Check the documentation that you can pass the build_flags. Maybe you can use that to specify the root of your project.

I simply choose Debug.
I assume that results in it trying to run the package I am in, but that is not executable.
So I need it to use the root from gopls 🤔
If that is out of scope, that is understandable - as I said, may be my setup. Can you confirm you have the same happen to you?
I can create a small reproduction if needed?

Still an issue.

Hi, @Jomik! I recently faced the same issue as you did. You are absolutely correct that the Debug option attempts to run the current file. This occurs because the DAP configuration uses the ${file} placeholder.
However, we have several other options available that we can use to customize DAP configuration.
As an example, here's my configuration that runs /cmd/main.go from any file within the project:
require("dap-go").setup({
	dap_configurations = {
		{
			type = "go",
			name = "Debug main.go",
			request = "launch",
			program = "${workspaceFolder}/cmd/main.go"
		},
	}
})

I hope this helps!

Tks @tehaleph for chiming in!
@Jomik feel free to reopen if you still have an issue


Adding general tips of how to troubleshoot the instalation of single user nix installer

Checking environment variables
env
env | grep 'some_env_var name'

declare -px > env.sh
source env.sh

https://stackoverflow.com/a/39119103
The ~/tmp and/or /tmp: No space left on device when using docker-compose, why ?
## FIX for running out of space / tmp, which is used for building
fileSystems."/nix/.rw-store" = {
  fsType = "tmpfs";
  # options = [ "mode=0755" ];
  options = [ "mode=0755" "nosuid" "nodev" "relatime" "size=14G" ];
  neededForBoot = true;
};

From: https://githubmemory.com/repo/colemickens/nixcfg/issues/3

Using the CLI

nix flake update --override-input nixpkgs nixpkgs/84aa23742f6c72501f9cc209f29c438766f5352d

The WSL2

Linux GUI app support now shipping as part of the Windows Subsystem for Linux
microsoft/winget-cli
O MELHOR sistema operacional para programação com Fabio Akita | #HipstersPontoTube: start=179&end=221&version=3

TODO: take a look in that.

However, if nix has to build a derivation, it has to spin up a builder... And builders run in a user namespace with uids and gids mapped and significantly less permissions. That builder is what's spitting out that error.
From: https://github.com/NixOS/nixpkgs/issues/67465#issuecomment-643886723

Good defaults
TODO: insvestigate

keep-outputs = true       # Nice for developers
keep-derivations = true   # Idem
From: https://ianthehenry.com/posts/how-to-learn-nix/garbage-collection/

TODO:

https://github.com/nix-community/nix-installers/tree/93907b1b4a34b4391bc3e776a410213669f64074

$ nix build github:nix-community/nix-installers/93907b1b4a34b4391bc3e776a410213669f64074#deb
$ ls -al result
lrwxrwxrwx 1 pedro pedro 68 jul  6 13:04 result -> /nix/store/a6li3c1in0cia6a4nsmy4nnvh3b550hq-nix-multi-user-2.9.1.deb

echo "$(ps -ocomm= $(ps -q $$ 1> /dev/null 2> /dev/null && echo '-q') $$)"rc


Use properties for event.tags and event.unavailability

Fixes #76

Are you happy there's nothing weird going on with the chair schedule being changed in the tutorial? I'm pretty sure it's just the different order of constraints but worth making sure we're sure.

(Possibly as a second issue/PR we should have a short how to going over "manipulating event unavailability and tags" just briefly showing the other two methods.)

Are you happy there's nothing weird going on with the chair schedule being changed in the tutorial? I'm pretty sure it's just the different order of constraints but worth making sure we're sure.

I agree it's probably nothing but I'd like to go through that and make sure I'm happy it's still a valid solution. I've not done that yet.

Found a bug...

This looks good to me. Not sure what order you prefer this to go in re #75 so will leave merging to you. :+1:

OK. I'm just looking at cleaning up one of those dicts a little....

Let's get #75 finished first and then I can just alter the one line in here to fix it


Multichannel Video Issue

Hi, I'm trying to change the channel audio and subtitles from MKV file, but doesn't work. I think would be add some lines of code after uri property in load method as self._playbin.set_property("current-audio", index). I need help to fix that! Thanx!
PD: I don't speak english, sorry for my bad english.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15183433-multichannel-video-issue?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

Fixed and share my code in pull request :)


Immutable sampler for Ycbcr conversion, compiled with slang

Hi everyone, I could use some help fixing a difficult problem that seems to have no clear answer.
To help in reproing the issue, I created a 100% repro test case in the Vulkan Video sample, using an HLSL shader compiled with both DXC and slang. Neither compiler seems able to output SPV binaries that are equivalent to the GLSL fragment shader, thus unable to do YCbCr conversion via immutable samplers. This is a serious problem for me as my path tracer needs to be able to sample video textures on the fly without converting them first to RGB, which I've done for a single texture but adds massive overhead.
This is the branch I made with 100% repro:
https://github.com/BattleAxeVR/vk_video_samples/tree/main/vk_video_decoder
If I compile this very basic HLSL pixel shader using slangc (all it does is sample a texture and draw on to a fullscreen quad), I can see my YUV 420 planar video textures but only the Y channel (so it looks red).
The immutable texture sampler, whose job it is to automatically convert YUV planar textures to RGB, is clearly not bound or not working somehow, and I'm unable to figure out why. It's beyond my understanding and google is no help, really. Nobody seems to know
https://github.com/BattleAxeVR/vk_video_samples/blob/main/vk_video_decoder/video_pixel_shader.frag.hlsl
This is the command line I used:
slangc video_pixel_shader.frag.hlsl -entry main -stage fragment -o video_pixel_shader.spv
No other code is changed from the default GLSL pipeline, and dropping in the slang-compiled HLSL vertex shader into the demo works 100%. I tried everything but no idea what's going on. I originally tried using DXC but it exhibits the same issue: only showing red (first channel) instead of full colour.
This is what the bug looks like in my engine, but it's the same thing in the official Nvidia code sample. Video textures show up red instead of full colour.
Thanks for any help or insights you may have!

This was originally created here:
https://github.com/nvpro-samples/vk_video_samples/issues/60
But it seems to be out of scope for that repository to fix.

I noticed that your glsl code uses sampler2d, which is a combined texture sampler. The HLSL is using a separate sampler state so that could be the cause.
Looks like a driver issue though.
If you want the equivalent of combined texture sampler in slang, you can try using Sampler2D in Slang instead of Texture2D, which will map to sampler2d in glsl / spirv.

If this is a driver issue, then maybe we should close this one but I'll post on the originating bug someone who can try to triage the issue and see if we can get it moving. Thanks, and sorry this issue on the other repo didn't get movement faster.

I noticed that your glsl code uses sampler2d, which is a combined texture sampler. The HLSL is using a separate sampler state so that could be the cause.
Looks like a driver issue though.
If you want the equivalent of combined texture sampler in slang, you can try using Sampler2D in Slang instead of Texture2D, which will map to sampler2d in glsl / spirv.

+1
Does switching over from Texture2D to Sampler2D fix the issue?

I will try this ASAP!

Sadly, it seems neither DXC nor slang support the DirectX 9 syntax of sampler2d and tex2, complaining about deprecated functionality or just missing identifiers:

In DXC if I switch from sampler2d to sampler, it says tex2d is deprecated, regardless of whether I specify it's ps_4_0 or ps_6_6

If you want the equivalent of combined texture sampler in slang, you can try using Sampler2D in Slang instead of Texture2D, which will map to sampler2d in glsl / spirv.

Can you tell me what the equivalent of this HLSL shader is in slang? That would actually compile, at least
uniform sampler tex;
struct VSOutput
{
[[vk::location(0)]] float2 UV : TEXCOORD0;
};
float4 main(VSOutput input) : SV_TARGET
{
float4 colour = tex2D(tex, input.UV);
return colour;
}

Sampler2D tex;
struct VSOutput
{
    float2 UV : TEXCOORD0;
};

float4 main(VSOutput input) : SV_TARGET
{
    float4 colour = tex.Sample(input.UV);
    return colour;
}

Sampler2D has everything that Texture2D has, except that the Sample methods does not take an additional SamplerState parameter.

That did it! Thanks so much! I had a feeling it was a syntax or binding issue like this.
DXC won't compile this code (I guess Sampler2D is a slang-specific identifier?). So it looks like slangd is the answer.
I can close this now.

Yes, Sampler2D is a Slang specific feature that gives our users direct access to combined texture samplers when targeting spirv or glsl.
According to the vulkan spec YCbCr textures only works with combined texture samplers, so Sampler2D is the right answer here.

For completeness, I tried tex.SampleLevel and tex.SampleGrad and the former works but SampleGrad crashes during pipeline creation. I enabled anisotropy and max aniso = 16 but didn't use the debug validation layers to see what the error was, but I'll open a new issue about it later. SampleLevel is an OK compromise for now, for my path tracer to manually pick the LOD even if aniso isn't done properly yet. Of course, I know that planar YUV 420 video textures don't actually have mips, but you should ideally be able to sample them anisotropically.

I got an alternative fix in DXC now, so this issue is truly closed with two viable alternatives. A+ everyone, so much appreciated! I have other slang use cases anyway, but for now I'll stick to DXC for this particular issue to avoid having to do a bunch of refactoring.
https://github.com/microsoft/DirectXShaderCompiler/issues/4179#issuecomment-1890069615


[Enhancement] Toast messages for application, org and page modifications

Summary
Add toast bars for application, organization and page addition, deletion or copy actions. Adding, removing users and widgets
Motivation
https://www.figma.com/file/dLgbc6Nw3DY9yYLqPJJR2i/Improve-signposting-across-the-app-|-Wed-30-June-2021?node-id=201%3A56580

This seems solved

@Nikhil-Nandagopal  reopening as this has not been resolved. We created this to show success toasters when we create/rename apps, orgs and pages.