WebSocket connection failed / Undefined Node

After update to 1.7 (installed .deb x64 from site) most extensions that required an node domain stopped working, returning "Max connection attempts reached" error. Including git, ftp and sql.
On the console, even with live preview and all extensions disabled I got tons of

WebSocket connection to 'ws://localhost:38443/' failed: Unexpected response code: 401

Also, both "Enable Node Debugger" and "Restart Node" say that can't call method of undefined.
Checked /etc/hosts and have "<IP_ADDRESS> localhost" configured.
Tried to run with sudo and gksu for testing but then I can't even open the development tools or install extensions to test. But the node options also return undefined object.
I got those installed packages:
sudo apt list | grep "brackets\|nodejs"
brackets/now 1.7.0-16898 amd64 [installed,local]
nodejs/testing,now 4.3.1~dfsg-3 amd64 [installed]
nodejs-dbg/testing 4.3.1~dfsg-3 amd64
nodejs-dev/testing,now 4.3.1~dfsg-3 amd64 [installed,automatic]
nodejs-legacy/testing,testing 4.3.1~dfsg-3 all

I returned to 1.6 for now and the extensions are working properly.

I think this problem also caused my https://github.com/adobe/brackets/issues/12505.

I have the same issue:
WebSocket connection to ‘ws://localhost:34273/’ failed: Unexpected response code: 401
I don't see a socket open.  I am assuming that I should see one:
netstat -ntlp | grep 34273
I also tried by the pid:
$ ps -ef | grep -i node
skp 9789 9764 0 18:21 pts/20 00:00:00 /opt/brackets/Brackets-node /opt/brackets/node-core
$ netstat -ntlp | grep 9977
I didn't try reverting back to 1.6, but I noticed the issue when I was trying to install version 1.7

There was an issue with 1.7 Linux 64 builds. It was to do with brackets unable to connect to Node. We have now fixed the problem and refreshed the builds. Could you guys download the Linux 1.7 builds again from brackets.io and check?

@nethip  That worked great for me.  I can now install all of the extensions that I was trying to, so I am good to go.  Thank you very much.

@nethip It's solved! Thanks very much =)

@nethip It's worked :D
Thanks

@nethip It isn't working for me actually. I just downloaded the 1.7 64-bit.deb installer from brackets.io. I am using Ubuntu 16.04. I get the same error WebSocket connection to 'ws://localhost:46339/' failed: Unexpected response code: 401 thus when I try to install any extensions, Brackets freezes with this error Installation Failed" : "Unknown internal error.". If I open it with sudo, I can't even open the console. Am I not doing something correctly or does someone else still have the issue? Thanks in advance.

@f4z3k4s Since you are getting the issue on both 1.7 and 1.6, it leads me to think that this is a different issue, but I'm not sure.
I had initially installed on Ubuntu 16.04  64-bit from the WebUpd8 repository.  To install the version from brackets.io, I had to install the libgcrypt11 from the WebUpd8 post, and then install the deb package.  That fixed my problem, and I was able to install the extensions that I wanted.  Then, a while after that, I noticed it doing the same thing again.  My theory is that I had run updates and that it had reinstalled the version from the repo.  After reinstalling the version from brackets.io the error went away again.
I don't know if any of that helps.

@f4z3k4s I agree with @digitaleagle . It could be a different issue.
Do you use any proxy or have a different mapping of localhost on your system? Also there could be another software like an AntiVirus program which may be blocking opening of local ports.

I managed to solve the problem with the help of @digitaleagle . Without having libgcrypt11 installed separately, you can't even install the deb. Why I could install it previously was because I first installed brackets from the WebUpd8 repo with apt-get, after I removed it, but not purged it, and libgcrypt was still available for the deb file which I downloaded from brackets.io.
The following I did to make it work:

I purged the previously installed brackets totally with
sudo apt-get purge brackets
I also removed the ppa with
sudo add-apt-repository --remove ppa:webupd8team/brackets
I installed libgcrypt this way:
wget http://ftp.acc.umu.se/mirror/cdimage/snapshot/Debian/pool/main/libg/libgcrypt11/libgcrypt11_1.5.3-5_amd64.deb
sudo dpkg -i libgcrypt11_1.5.3-5_amd64.deb
And after this I was able to install brackets 1.7 from the deb file, and extensions are working.

Thanks for the help guys, keep up the good work.
Cheers!:)


php, html and etc. files

i am use your demo website*
fix PHP files:
just click on php/html file and more usability files

Directory Lister does not actually serve files, it only lists them. File serving is handled by your web server. In this case PHP files are interpreted by the PHP engine (which allows Directory Lister to run) and doesn't actually output anything to the browser.
As for the demo, we're hosting the raw application files (including PHP files) which isn't recommend for the reasoning stated above.


Implementation of YOLOv7 in MIT license?

Hi,
Is https://github.com/WongKinYiu/yolov7 also in plan for MIT license implementation?

Yes, originally, we were supporting YOLOv7, but we took the services down to improve the code further. We will resume the service soon. Please keep an eye on this project for updates.


Fix capabilities version, upgrade SDK to v0.1.4, fix Clippy lints

This PR fixes a fairly significant bug in the capabilities response, where the connector returns an invalid version. It returns a semver range, rather than just a semantic version, which is against the spec. It's probably a holdover from an old version of the spec that never got changed.
This has caused issues now that engine actually looks at the value in that property.
The PR also updates the NDC Rust SDK to the latest easily updatable version (v0.1.4). A more recent version brings in new newtypes that I'm not prepared to deal with for this small fix.
The PR also fixes all the various clippy lint warnings across the code (in separate commit for easier reviewing).

 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.


example of gfx-backend-gl v0.4.0 doesn't compile

Reproduction involves just getting the latest version from crates.io with a Cargo.toml, and the crate itself wont compile.
# ...
[dependencies]
gfx-backend-gl = "*"

More specifically, I was trying to get the example to compile locally, as opposed to building from the example repository itself, and couldn't get it working.
The error:
   Compiling gfx-backend-gl v0.4.0
error[E0308]: mismatched types
    --> /home/simon/.cargo/registry/src/github.com-1ecc6299db9ec823/gfx-backend-gl-0.4.0/src/device.rs:1945:21
     |
1945 |                     config.extent.width as f64,
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected u32, found f64

error[E0308]: mismatched types
    --> /home/simon/.cargo/registry/src/github.com-1ecc6299db9ec823/gfx-backend-gl-0.4.0/src/device.rs:1946:21
     |
1946 |                     config.extent.height as f64,
     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected u32, found f64

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
error: could not compile `gfx-backend-gl`.

It looks like the version on https://crates.io/crates/gfx-backend-gl is 3 months old, while the version in the Github master is 11 days old https://github.com/gfx-rs/gfx/tree/master/src/backend/gl

Are there any plans to publish an updated gfx-backend-gl soon? Being able to unravel the winit/glutin/backend-gl compatibility knot would be great, if this happens to be just a painless patch release that no one saw demand for yet, I hereby declare interest. :) Thanks for your efforts! :+1:

We can't publish the updated gfx-backend-gl without that being a breaking (minor) change, since it depends on winit. If we release a breaking version here, than this would mean the version will be confusingly different from gfx-hal, which isn't the best in longer term...
The only proper solution is to consider gfx-hal-0.5 release. I created https://github.com/gfx-rs/gfx/milestone/13 and will be adding issues to it that are blocking us.

I understand, thank you for the clarification and insight through the tracking milestone, I'm looking forward to 0.5 then! :tada:


Replace old model to shared model in synchronizer

Signed-off-by: luckychess<EMAIL_ADDRESS>

Description of the Change

Synchronizer: replace old model to shared model.
Benefits

Old model is a subject to remove so we are one step closer to success now.
Possible Drawbacks
None.

Usage Examples or Tests [optional]
Tests were changed accordingly.

One comment about const refs: almost all pass by value cases will be changed when other components (like consensus gate) move to a shared model. I do not want to touch them now because all these cases will gone very soon after other components to shared model migration.

please pay attention to codacy review https://app.codacy.com/app/stinger112/iroha/pullRequest?prid=1453166


🐛 Bug Report: Deleting conflicting entityRef is not resulting in entity being restored in a new Group.

📜 Description
When I move an entity between owners in the catalog I get an error like this:
Detected conflicting entityRef resource:default/main-db already referenced by file:<dir>/catalog/team-red.yaml and now also file:<dir>/catalog/team-orange.yaml type=plugin

I used to look up the UID of the first entity (UI or via GUI)
Then I would DELETE via API
However this is no longer working (Backstage 1.11.x / 1.12.x) - the DELETE succeeds but the replacement entity does not appear in the catalog.
👍 Expected behavior
I believe DELETEing the 1st entity should result in the second entity appearing in the catalog (effectively changing the owner)
👎 Actual Behavior with Screenshots
I was able to get the UID
I then DELETED and tried to get the item again
{
  "error": {
    "name": "NotFoundError",
    "message": "No entity with uid <UID>",
    "stack": "NotFoundError: No entity with uid <UID>\n    at <dir>/node_modules/@backstage/plugin-catalog-backend/dist/index.cjs.js:3619:15\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
  },
  "request": {
    "method": "GET",
    "url": "/entities/by-uid/<UID>"
  },
  "response": {
    "statusCode": 404
  }
}

But the second entity is not appearing in the catalog
There are no orphans
curl -X GET localhost:7007/api/catalog/entities?filter=metadata.annotations.backstage.io/orphan=true

With matching entity names.
I now have 0 entities of the correct name.
👟 Reproduction steps
I ran Backstage locally with a local catalog set of files.
Once running I took an Entity from 1 catalog file and moved to a second file.
I was able to observe the Conflicting entityRef message.
I then found the UID of the 1st entityRef (i.e the entity before the move)
I then DELETED via the API and confirmed it was deleted.
No replacement entity appeared with a new Owner.
No entity appeared at all.
Restarting Backstage with a clean DB results in the Entity being created in the correct Group - so I believed the file is well-formed.
I am not however able to recreate the DB (easily).
📃 Provide the context for the Bug.
Currently changing entity owners in the catalog is not working - and if we resolve the conflicting entityref we lost the entity entirely.
🖥 Your Environment
OS:   Linux <IP_ADDRESS>-microsoft-standard-WSL2 - linux/x64
node: v18.14.2
yarn: 1.22.19
cli:  0.22.5 (installed)
backstage:  1.12.1
Dependencies:
@backstage/app-defaults                          1.2.1
@backstage/backend-app-api                       0.4.1
@backstage/backend-common                        0.18.3
@backstage/backend-dev-utils                     0.1.1
@backstage/backend-plugin-api                    0.5.0
@backstage/backend-tasks                         0.5.0
@backstage/backend-test-utils                    0.1.35
@backstage/catalog-client                        1.4.0
@backstage/catalog-model                         1.2.1
@backstage/cli-common                            0.1.12
@backstage/cli                                   0.22.5
@backstage/config-loader                         1.1.9
@backstage/config                                1.0.7
@backstage/core-app-api                          1.6.0
@backstage/core-components                       0.12.5
@backstage/core-plugin-api                       1.5.0
@backstage/errors                                1.1.5
@backstage/eslint-plugin                         0.1.2
@backstage/integration-aws-node                  0.1.2
@backstage/integration-react                     1.1.11
@backstage/integration                           1.4.3
@backstage/plugin-api-docs                       0.9.1
@backstage/plugin-app-backend                    0.3.43
@backstage/plugin-auth-backend                   0.18.1
@backstage/plugin-auth-node                      0.2.12
@backstage/plugin-catalog-backend-module-github  0.2.6
@backstage/plugin-catalog-backend                1.8.0
@backstage/plugin-catalog-common                 1.0.12
@backstage/plugin-catalog-graph                  0.2.28
@backstage/plugin-catalog-import                 0.9.6
@backstage/plugin-catalog-node                   1.3.4
@backstage/plugin-catalog-react                  1.4.0
@backstage/plugin-catalog                        1.9.0
@backstage/plugin-circleci                       0.3.16
@backstage/plugin-events-node                    0.2.4
@backstage/plugin-explore-common                 0.0.1
@backstage/plugin-explore-react                  0.0.27
@backstage/plugin-explore                        0.4.1
@backstage/plugin-github-actions                 0.5.16
@backstage/plugin-github-issues                  0.2.5
@backstage/plugin-github-pull-requests-board     0.1.10
@backstage/plugin-home                           0.4.32
@backstage/plugin-kubernetes-backend             0.9.4
@backstage/plugin-kubernetes-common              0.6.1
@backstage/plugin-kubernetes                     0.7.9
@backstage/plugin-org                            0.6.6
@backstage/plugin-permission-backend             0.5.18
@backstage/plugin-permission-common              0.7.4
@backstage/plugin-permission-node                0.7.6
@backstage/plugin-permission-react               0.4.11
@backstage/plugin-proxy-backend                  0.2.37
@backstage/plugin-scaffolder-backend             1.12.0
@backstage/plugin-scaffolder-common              1.2.6
@backstage/plugin-scaffolder-node                0.1.1
@backstage/plugin-scaffolder-react               1.2.0
@backstage/plugin-scaffolder                     1.12.0
@backstage/plugin-search-backend-node            1.1.4
@backstage/plugin-search-backend                 1.2.4
@backstage/plugin-search-common                  1.2.2
@backstage/plugin-search-react                   1.5.1
@backstage/plugin-search                         1.1.1
@backstage/plugin-tech-radar                     0.6.2
@backstage/plugin-techdocs-backend               1.6.0
@backstage/plugin-techdocs-module-addons-contrib 1.0.11
@backstage/plugin-techdocs-node                  1.6.0
@backstage/plugin-techdocs-react                 1.1.4
@backstage/plugin-techdocs                       1.6.0
@backstage/plugin-user-settings                  0.7.1
@backstage/release-manifests                     0.0.9
@backstage/test-utils                            1.2.6
@backstage/theme                                 0.2.18
@backstage/types                                 1.0.2
@backstage/version-bridge                        1.0.3
Done in 0.89s.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

ping @backstage/catalog-core

up on this one

Ping @backstage/catalog-maintainers

Alright, thanks for the reproduction case that deals with local files - that does make it easier. I'll try to get some time to try to trigger that happening.

Wanted to make sure you get a ping about the above comment @backstage/catalog-maintainers in case you want to give it a read

Ping @backstage/catalog-maintainers

I am experiencing the same issue here. In my case, I used the GithubEntityProvider to look for a catalog-info.yaml file in every repo. In my setup I support multiple orgs and we're in the process of moving a bunch of repos from one org to another. In some cases this triggers this issue. I think that it might be race-condition-y.
If the old entity (from before the move) exists at the same time as the new entity (from after the move) tries to get ingested then this issue happens and I have to manually fix things to get things back in order.
I managed to mitigate this issue a bit by setting catalog: { orphanStrategy: delete } in my config. With that setting things work out most of the time. The general flow (as far as I understand) goes a like this:

We have a location that points to oldorg/repo and an entity that emitted from that in the catalog
We move the repo to neworg/repo
The old location gets removed & stops emitting the entity
Backstage deletes the orphan
The entity disappears from the catalog
GithubEntityProvider finds the repo in the new org
It creates a location for it and that location emits the entity
The entity shows up in the catalog

I managed to find a simple workaround to fix this issue when it happens. I simply delete the location from the catalog using the backstage UI. The location itself is hard to find in the UI because I can't filter by location targets (https://github.com/backstage/backstage/issues/23098) so I have to look it up through the API and then navigate to it.
What's annoying is that I don't have a good way to figure out which entities are affected by this. The simplest solution I found to this is to use the API to list all locations in the new org and then use the API to delete those.


feat: merchantCity field normalized

What kind of change does this PR introduce?

Feature

What is the current behavior?

The merchantCity field is not normalized. Allowing inconsistent data to be stored in the brcode.

What is the new behavior?

The merchantCity field is normalized. Removing any non-alphanumeric characters and converting to uppercase.

:tada: This PR is included in version 2.4.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Change docs to Docusaurus

The current documentation is lacking. We should migrate to Docusaurus or similar.

Yeah, Mintlify is half baked. We learned.

I don't think we should tag this as Next Release, though, if users are not complaining about it as a top priority. There are other items that should be associated with the milestone.


0.12.0: unusable stage1 "host" image

On Debian, rkt's build system produces unusable stage1 "host" image. As far as I understand the problem, systemd binaries located in /bin and /lib are not copied to image rootfs as they are expected to be under /usr. On run-time rkt fails to start an image as follows:
         Starting Journal Service...
[  OK  ] Started Pod shutdown.
[  OK  ] Started hello Reaper.
systemd-journald.service: Main process exited, code=exited, status=203/EXEC
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.

Besides default location of stage1 image in /usr/bin is a violation of FHS.

Possible duplicate of https://github.com/coreos/rkt/issues/1758
/cc @krnowak

Definitely related but IMHO not a duplicate.

It seems to be about journald:
Where is systemd-journald on Debian? Rkt is looking both in /usr/lib/journald and /lib/journald:
https://github.com/coreos/rkt/blob/master/stage1/init/init.go#L234
We can add more directories to search if necessary.

It seems to be about journald:

Not just systemd-journald but pretty much all systemd binaries and probbaly even bash (/bin/bash).

Where is systemd-journald on Debian?

/lib/systemd/systemd-journald

We can add more directories to search if necessary.

Yes please, that seems to be necessary. Thanks.

Where is systemd-journald on Debian?

/lib/systemd/systemd-journald

The directory /lib/systemd is already in the list of installAssets:
	systemdJournaldBin, err := lookupPath("systemd-journald", \
                "/usr/lib/systemd:/lib/systemd")
	if err != nil {
		return err
	}

And looking at your logs, it does not fail when copying systemd-journald but later when executing it. What version of systemd is installed on the host? I wonder if rkt fails to copy some dependencies. Can you check this on the host?
$ dpkg -l systemd
$ ldd /lib/systemd/systemd-journald

And if you start rkt with --no-overlay, it will be easier to check in /var/lib/rkt/pods/run/xxxxx/stage1/rootfs/ if some deps were not copied correctly.

I can reproduce the problem on Debian. Investigating this...

Thanks for your tips and quick patch, Alban.
Systemd v228; ldd /lib/systemd/systemd-journald prints
    linux-vdso.so.1 (0x00007ffc17b21000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007ff28eb81000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff28e979000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007ff28e755000)
    libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007ff28e474000)
    libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007ff28e26b000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff28e04d000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff28dca4000)
    /lib64/ld-linux-x86-64.so.2 (0x0000560344a13000)
    libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff28da36000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff28d831000)
    libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007ff28d61e000)
    libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007ff28d419000)

I started rkt with --no-overlay and inspected /var/lib/rkt/pods/run/xxxxx/stage1/rootfs/ mount but could not find any missing libraries.
However even with c22595a applied to 0.12.0 I'm still getting the same error...

I updated to 5af87c1a22f154180070cb965965f0fa54449ea5 but it should not make a difference.
# DIR=/var/lib/rkt/pods/run/db3379aa-afc0-4d8e-a14d-3526d79b6d82/stage1/rootfs

# grep ExecStart $DIR/usr/lib/systemd/system/systemd-journald.service
ExecStart=/lib/systemd/systemd-journald

# ls -l $DIR/lib/systemd/systemd-journald
-rwxr-xr-x 1 root root 318040 Nov 30 13:08 /var/lib/rkt/pods/run/db3379aa-afc0-4d8e-a14d-3526d79b6d82/stage1/rootfs/lib/systemd/systemd-journald

# ldd $DIR/lib/systemd/systemd-journald
	linux-vdso.so.1 (0x00007ffe3b3b7000)
	libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f04dbca8000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f04dbaa0000)
	liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f04db87c000)
	libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f04db59b000)
	libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007f04db392000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f04db174000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f04dadcb000)
	/lib64/ld-linux-x86-64.so.2 (0x000055f7fc52c000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f04dab5e000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f04da959000)
	libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f04da746000)
	libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f04da541000)

#  ls -l $DIR
total 21820
-rwxr-xr-x 1 root root   751000 Nov 30 12:37 appexec
-rwxr-xr-x 1 root root   752024 Nov 30 12:37 enter
drwxr-xr-x 3 root root     4096 Nov 30 12:37 etc
lrwxrwxrwx 1 root root        4 Nov 30 12:37 flavor -> host
-rwxr-xr-x 1 root root  9027312 Nov 30 12:37 gc
-rwxr-xr-x 1 root root 11036504 Nov 30 12:37 init
lrwxrwxrwx 1 root root        7 Nov 30 12:37 lib -> usr/lib
lrwxrwxrwx 1 root root        9 Nov 30 12:37 lib64 -> usr/lib64
drwxr-xr-x 3 root root     4096 Nov 30 12:37 opt
-rwxr-xr-x 1 root root   746872 Nov 30 12:37 prepare-app
-rwxr-xr-x 1 root root      226 Nov 30 12:37 reaper.sh
drwxr-xr-x 4 root root     4096 Nov 30 12:37 rkt
drwxr-xr-x 5 root root     4096 Nov 30 13:08 usr

@onlyjob Do you also have the symlinks lib -> usr/lib and lib64 -> usr/lib64 in the rootfs directory?

Sorry, I did not check symlinks but it works now. :)
All good, thank you!


Add GET /transactions/queued endpoint

Closes #156
Implements /chains/:chainId/safes/:safeAddress/transactions/queued route.

Coverage: ?%. Remained the same when pulling d9f2de3b577aeed3fb520fbe8edf26abf78ac917 on 156-add-get-safessafe_addresstransactionsqueued-route into 3a64d88312c536495c8d0afc18b8b444753cd95a on main.

I've changed the approach (related to this discussion) in the controller tests to use builders in 96d459c. I've removed all the JSON files related to these feature tests. Hopefully, this approach is easier to follow. I also think the use of matchers (i.e. objectContaining) makes easier to focus in the parts being tested (in this case ordering, labels, headers, and conflict types) instead of in the transactions mapping itseft (covered by other tests). Any feedback is welcomed @fmrsabino @moisses89 🙂


Remove deprecated Google Code import path

Fixes warning when running
$ go get github.com/bgentry/heroku-go
warning: code.google.com is shutting down; import path code.google.com/p/go-uuid/uuid will stop working

Thanks! :v:


Rendering on Android is incorrect / low resolution

Looks like when rendering on some Android devices the output does resemble the splats but looks very low resolution; not sure if incorrect sorting or if something with the data goes wrong. I tested this also with the live page from this repo.
Tested on Xiaomi 11T. Works fine on other Android devices like Quest 3
Some images of how it looks (after all splats have been loaded):

Image 1
Image 2

Thank you for the report.
That seems unusual.
Which browser are you using?
Does this issue occur every time?
Doesn't it resolve even after reloading the page?
Can you see that the number of splats is increasing?

this is latest Chrome
issue occurs every time on this device
it does not resolve after reloading the page, it is persistent
yes, I can see the number of splats increasing (triple checked, it's all of them)

Hmm, I'm not sure what's causing it.
I'll check at a nearby electronics store to see with which devices the issue occurs.
I'll be creating a test script, so please wait for a few days.

Some more tests on random devices here:

Mobile Device
Works (✅) vs Blurry (❌)
GPU

iPhone 11
✅
A13 Bionic

iPhone 14
✅
A16 Bionic

iPad Pro
✅
M2

Quest 2 Browser
✅
XR 2 Gen 1

Quest 3 Browser
✅
XR2 Gen 2

Samsung Galaxy Tab S8
✅
Adreno 730

Xiaomi 11T
❌
ARM Mali-G77

Huawei Mate 20
❌
ARM Mali-G76

Huawei P30 Pro
❌
ARM Mali-G76

Google Pixel 5
✅
Adreno 620

Google Pixel 6
❌
ARM Mali-G78

NOKIA 5.4
✅
Adreno 610

So seems ARM Mali is the problem here.

@aras-p maybe you have an idea? Shader code is here: https://github.com/quadjr/aframe-gaussian-splatting/blob/8aa3d91813d6583f124c7fda53d04f800674e442/index.js#L48

The same issue is visible on my smartphone as well.
I have a Huawei P30 Pro and I tested it on Firefox Mobile (118.2.0).
Using the debugging tool about:debugging I managed to get the console log, there are no error, just warning.

Console logs
!Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “accelerometer”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “gyroscope”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “accelerometer”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “gyroscope”. gaussian-splatting
!Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. Sample.3c5b792f.js:7:2737
!Feature Policy: Skipping unsupported feature name “accelerometer”. Sample.3c5b792f.js:7:2737
!Feature Policy: Skipping unsupported feature name “gyroscope”. Sample.3c5b792f.js:7:2737
!WebRTC: Using more than two STUN/TURN servers slows down discovery index-f8ccf2d9.js:3760
 Particle system powered by three.quarks. https://quarks.art/ index-f8ccf2d9.js:5826:19254
#Made with ♥ by 🌵 Needle - https://needle.tools — Version 3.20.1 index-f8ccf2d9.js:6754:1857
 @@Needle Engine — No license active, commercial use is not allowed. Visit https://needle.tools/pricing for more information and licensing options. index-f8ccf2d9.js:4337:15@@
!Your model is using scaled mesh colliders which is not optimal for performance Cube
!Object { x: 0.001, y: 0.001, z: 0.001 }
!index-f8ccf2d9.js:6656:1816260
THREE.!WebGLTextures: sRGB encoded textures have to use RGBAFormat and UnsignedByteType. index-f8ccf2d9.js:3616:38905
!WebGL warning: readPixels: `pixels` type does not match `type`. 6
#download progress: 2.02% 5.77 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT. 5
#download progress: 4.91% 8.73 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT. 5
#download progress: 7.27% 9.33 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT. 5
#download progress: 9.69% 10.43 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 11.77% 10.75 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT. 5
#download progress: 13.09% 10.71 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 17.00% 11.89 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT. 5
#download progress: 20.74% 11.75 Mbps index-f8ccf2d9.js:6752:1325
!WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT.
!After reporting 32, no further warnings will be reported for this !WebGL context.
#download progress: 24.33% 11.64 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 26.33% 11.52 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 29.77% 11.58 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 32.71% 11.76 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 35.95% 11.49 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 39.54% 11.80 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 43.18% 11.95 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 46.63% 12.20 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 50.22% 12.03 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 57.05% 12.23 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 58.25% 11.10 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 61.94% 11.41 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 68.72% 11.78 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 72.46% 11.18 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 76.05% 11.30 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 83.09% 11.31 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 86.28% 10.73 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 89.72% 10.71 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 91.32% 10.57 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 95.51% 10.94 Mbps index-f8ccf2d9.js:6752:1325
#download progress: 99.10% 10.73 Mbps index-f8ccf2d9.js:6752:1325
#Completed download. index-f8ccf2d9.js:6752:1201
!An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page. index-f8ccf2d9.js:3616:227538

Some more tests on random devices here:
Mobile Device	Works (✅) vs Blurry (❌)	GPU
iPhone 11	✅	A13 Bionic
iPhone 14	✅	A16 Bionic
iPad Pro	✅	M2
Quest 2 Browser	✅	XR2 Gen 1
Quest 3 Browser	✅	XR2 Gen 2
Samsung Galaxy Tab S8	✅	Adreno 730
Xiaomi 11T	❌	ARM Mali-G77
Huawei Mate 20	❌	ARM Mali-G76
Huawei P30 Pro	❌	ARM Mali-G76
Google Pixel 5	✅	Adreno 620
Google Pixel 6	❌	ARM Mali-G78
NOKIA 5.4	✅	Adreno 610
So seems ARM Mali is the problem.

Wow, thanks for the great information.
I've made a small change that might fix the issue.
Could you try out the code I pushed to the main branch?"
I assumed that the 'int' in GLSL is 32 bits, but according to ChatGPT, it seems that it is not specified.
Commit id is d26566c.

Another possibility could be a difference in endianness.
I'll try to find a smartphone with ARM Mali.

Another possibility could be a difference in endianness

No, all GPUs are little endian.
Mali-G7x is a capable GPU, and should fully support both full 32-bit floats, and full 32-bit integers. So my guess would be on "something to do with driver side". Random ideas:

Even if GLSL ES specification does say that within a vertex shader, both float and int is highp, maybe the driver gets it wrong? i.e. adding precision highp float; precision highp int; to the shader source. In theory not needed, in practice, Android drivers {insert grumbling noises}.
I do remember that "a while ago", basically only ARM Mali GPUs in theory could not do floating point textures (but right now I don't remember whether they could not sample from them, or render into them). That had nothing to do with hardware (the hardware could always do it), but rather something to do with patents. Since then, said patents presumably have expired, and with fairly recent drivers they can do it all as expected. But if you're on old Android version, you might be hitting that issue.

❌  https://github.com/quadjr/aframe-gaussian-splatting/commit/d26566c11b546fb953ee8944c0cb3e48d3c7eb36 did not help
❌ precision highp float; precision highp int; did not help

Another possibility could be a difference in endianness

No, all GPUs are little endian.
Mali-G7x is a capable GPU, and should fully support both full 32-bit floats, and full 32-bit integers. So my guess would be on "something to do with driver side". Random ideas:

Even if GLSL ES specification does say that within a vertex shader, both float and int is highp, maybe the driver gets it wrong? i.e. adding precision highp float; precision highp int; to the shader source. In theory not needed, in practice, Android drivers {insert grumbling noises}.
I do remember that "a while ago", basically only ARM Mali GPUs in theory could not do floating point textures (but right now I don't remember whether they could not sample from them, or render into them). That had nothing to do with hardware (the hardware could always do it), but rather something to do with patents. Since then, said patents presumably have expired, and with fairly recent drivers they can do it all as expected. But if you're on old Android version, you might be hitting that issue.

I also wonder why there's a WebGL warning: drawElementsInstanced: TEXTURE_2D at unit 1 is of type UINT, but the shader samples as FLOAT in the reported WebGL logs. The shader does declare sampler as usampler2D as I would expect. Something gets lost on three.js side?

Thank you for the valuable information.
I'm also curious about the reported WebGL logs. I use one float texture and one uint texture, and utilize sampler2D for the float and usampler2D for the uint.
A-Frame and three.js prepend some lines to the beginning of the shader script, but they don't alter the actual processes.
Given the blurred image, it appears that the color and position are accurate, but the rotation and scale are wrong. This means that the issue lies in the unpacking process.
https://github.com/quadjr/aframe-gaussian-splatting/blob/f9f876ef07ff511ec147489951a54d546f97b195/index.js#L78

Another random thought: isn't usampler2D only available since GLSL ES 3.0 (i.e. WebGL2)? Maybe the Mali shader compiler is really more strict than the others, and goes "uhh you are using GLSL ES 1.0 shader, let me ignore usampler2D". Using WebGL2 and #version 300 es in the shader would be a fix then (might also need other changes to be done).

So a ShaderMaterial in three.js actually prepends some additional data, including glslVersion:
https://github.com/mrdoob/three.js/blob/35a26f178c523514673d992da1aece23c1cfca6e/src/renderers/webgl/WebGLProgram.js#L311
For a non-RawShaderMaterial it's already #version 300 es.
I tried turning it into a RawShaderMaterial, which works too when

specifying glslVersion: THREE.GLSL3 (which adds that version define)
changing attribute uint splatIndex; to in uint splatIndex;
adding out vec4 fragColor; in the fragment shader and setting that
But unfortunately it doesn't change the incorrect rendering.

For another data point, I see this issue on Pixel 7 with ARM Mali-G710. I can confirm it occurs across Chrome/Firefox/Samsung Internet. Thanks for your work!

I've got strange result on Pixel 6a.
When the number of splats is limited, the result is almost same with Safari on Mac.
However, when the number of splats increases, the result on the Pixel 6a becomes blurred.

This seems to be a bug in ARM Mali-G7x.
I'll examine the behavior a little more.

Some splats are not drawn on Pixel 6a.

I've fixed the issue!
The default precision of the float sampler on Arm Mali G7x is lower than that on other devices.
I used a float sampler to determine the absolute scale of splats, but due to the lower precision, small splats were treated as having a scale of 0.0.
I added precision highp sampler2D; to the vertex shader, and the issue has been resolved.
I've tested it on the Pixel 6a, Pixel 6, and Pixel 7.
Thank you all!

Ah! I should have realized this earlier. In retrospect, an extremely obvious issue. All samplers are "low precision" in GLSL ES by default. And I guess other GPU vendors, when reading from a lowp sampler into a full precision float, go "well, just read me full actual float", the Mali presumably does a bit more literal spec interpretation, "sample texture into a low precision variable, and then convert that into a float". Good catch.


Dashboard Refresh - need add one more limitation

In scenario of Dashboard having tile against AS Server where the specific model in AS is using Direct Query Model, the dashboard won't be able to trigger auto refresh, This is because Power BI Read Data_modified coulmn from AS DBschema_Catalogs using Adom function to determine whether dashboard refresh need to be triggered .
However that particular column only updated when the date that the catalog was last modified. This make sense of import mode because Import AS Model refresh would trigger a reprocess then Catalog would update, however for a Direct Query AS Model it does not required any model process to get refresh triggered, instead AS Model would directly trigger query to data source whenever required (It's same like Direct Query scenario in Power BI where metadata does not change)
[Please Refer to ICM:https://portal.microsofticm.com/imp/v3/incidents/details/297208391/home

Thanks for your comment, @KerryWang94. This issue has been assigned to the doc author for review.

Hi @KerryWang94,
I didn't understand your question - can you please explain what you're after?
Thanks,
Kesem


Introduce Email Notification System

This PR introduced the Email Service, Gmail configuration dashboard, and email notification for sharing workflow.
clientSecret is introduced in the core/amber/src/main/resources/application.conf
In order to enable the email notification:

Set clientId and clientSecret in core/amber/src/main/resources/application.conf.
Login to Texera with an admin account.
Open the Gmail dashboard under the admin tab.
Authorize a Google account for sending emails.
Send a test email.

After this change, we can introduce more email notifications on the front end. The email service will handle the requests.

@aglinxinyuan can you please add those steps to our wiki?

@aglinxinyuan can you please add those steps to our wiki?

Added to Guide for Developers.


added SVG animation  to the education page

#567
preview:

This resolves the need for a SVG animation for Education Page.
Feedback:

Please give a new PR where you have commented on all such SVG animations's code throughout the website in the following format

``
<!--
----------------------------------------------
SVG ANIMATION FOR EDUCATION PAGE
-----------------------------------------------
``

2. Like the cards on all the pages, try to make sure the SVG animation, heading beside it and the subheadings are loaded dynamically from education.js, research.js, expereince.js and project.js (If you wish you can raise separate PRS for each)


[api-minor] Simplify how the list of points are structured

Instead of sending to the main thread an array of Objects for a list of points (or quadpoints), we'll send just a basic float buffer.
It should slightly improve performances (especially when cloning the data) and use slightly less memory.

/botio test

/botio-windows test

/botio test

/botio-windows test

Two questions:

Are the ref-test "failures" actually expected?
If so, what's the explanation for the changes?

Two questions:
* Are the ref-test "failures" actually expected?

* If so, what's the explanation for the changes?

I didn't expect the changes and their are due to the fact I chose to set the data in some Float32Array which makes the check failing:
https://github.com/mozilla/pdf.js/blob/17e09e54785ed09dd3417983c3ed4085e8ee1fa4/src/display/annotation_layer.js#L535-L539
So in last version of the patch I changed for Float64Array.
I think we don't need to have 64-bits precision here and 32-bits is enough but it can be done in a follow-up.
And it'll require to make few other changes especially when we test the equality of two numbers with different precisions or we could just try to pass every floating data  into Float32Array (which could make sense for data.rect).

/botio test

/botio-windows test

I didn't expect the changes and their are due to the fact I chose to set the data in some Float32Array which makes the check failing:

Interesting, thank you!

I didn't expect the changes and their are due to the fact I chose to set the data in some Float32Array which makes the check failing:

Interesting, thank you!

Yes (thx for the tip: I didn't know fround) or just use a Float32Array for the data.rect, but as said I think it's worth doing that in follow-up, or do you prefer we switch to 32-bits precision in this patch ?

[...] or just use a Float32Array for the data.rect,

Off the top of my head I cannot tell how much else that'd affect, so perhaps we shouldn't do that here.
My untested idea was that we'd use Float32Array as originally in this patch, and simply change https://github.com/mozilla/pdf.js/blob/95a7de9f986c449cb949d39af948dbe97f60948e/src/display/annotation_layer.js#L531 into
const [rectBlX, rectBlY, rectTrX, rectTrY] = this.data.rect.map(e => Math.fround(e));

Given that this is the first [api-minor] patch for the new release, could you create a patch to bump the library version to 4.4 with a reference to the merge commit of this patch, similar to https://github.com/mozilla/pdf.js/commit/3ff93ede07d3813244fef83097c88411dd2dec2a? Thanks!


Security Improvements

This pull request has been made by the security transformer slash command via Slack. Please review the PR and go ahead and merge once you are happy with the changes.

👋 Closing this as this repo is an npm module rather than an app


Dedup organizations

Populate grid identifiers
Remove duplicate organizations
Improve code in how organizations are queried/found/stored when new ORCID record is created.

Added a merge feature to the admin area and dedup'd a bunch of records.


ERROR: 0:5: '' : unary '-' not allowed for provided data type

[Shaders, screenshots, error log, etc.] [ZIP]
variant_12_reduced_338_simplified.frag:
#version 440

void f()
{
    - (vec2(0.0, 0.0) * mat4x2(0.0));
}

Compile error log:
ERROR: 0:5: '' : unary '-' not allowed for provided data type
ERROR: 0:5: '' : unary '-' not allowed for provided data type

Reported:
https://software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/703553

Fixed by Intel in <IP_ADDRESS>42.


Add support for our Fine-tuning API

Add support for our new Fine-tuning API.

I'm going to backport this to Ruby I noticed that the example examples/completion.py is the same as examples/code_completion.py. Is this intended?

Noticed that this change undid #80


Use RetDec's JSON output for ASM <-> C mapping

The new RetDec JSON C output contains info on token assembly addresses.
Use this info for ASM <-> C code association.
Study how r2ghidra does it and use the same solution if possible.

Study the r2 feature called panel mode. It looked very cool when pancake showed it in r2con 2019. r2ghidra probably uses it. If id does not, r2dec should.

This was implemented in #6


Experiment overloaded compose method

Ideally all optics should compose together with a single function (or even better using function composition like in haskell). Early versions of Monocle were using a unique compose method but it doesn't play nicely with type inference, in particular when you compose optics coming from typeclasses (e.g. at, index) or "generic" optic (e.g. def some[A]: Prism[Option[A], A]).
Here is a snippet illustrating the problem:  https://github.com/julien-truffaut/Monocle/blob/master/example/src/test/scala/monocle/ComposeIssueExample.scala
Here is an explanation of type inference limitation caused by overloaded method definition: http://stackoverflow.com/a/7847406/2356120
However, in many practical cases an overloaded compose method can be used and this will offer us the possibility to have a much terser syntax e.g.
lensA compose prismB compose isoC
// or even
lensA ∘ prismB ∘ isoC
// instead of
lensA composePrism lensB composeIso lensC
// or
lensA ^<-? lensB ^<-> lensC

A default of this approach is that users will see a non consistent API (sometimes you can use compose sometimes you need to use composeLens) so we would leak scala type inference issue to Monocle API :-1:
However, I think that API terseness is a key to make optics useful, so I don't have a strong opinion if we should add it or not.

Probably a bad idea


Minor PHP and comment fixes

Changes proposed in this pull request:

Define the properties of the Linter class
Fix incorrect type in AbstractRule.php docblock
Fix call to instantiated LogicException class in TwigLexer.php
Update the comments in FunctionalTest.php to refer to this repository

I used PHPStan to analyse the code to find issues in the code and made a fix for a couple of them in this PR. The tool gave some other errors as well but they weren't as straightforward to fix.

Thank you!


lfs_cache_prog: assert(pcache->block == 0xffffffff)

The following program:
#include "lfs.h"
#include "emubd/lfs_emubd.h"
#include <stdio.h>
#include <string.h>
#include <stdlib.h>

lfs_t lfs;
lfs_emubd_t bd;

int lfs_emubd_prog_wrap(const struct lfs_config *c, lfs_block_t block,
            lfs_off_t off, const void *buffer, lfs_size_t size) {
    static int n = 0;
    if (++n == 13) {
        return 42; // Force error on 13th operation
    }
    return lfs_emubd_prog(c, block, off, buffer, size);
}

const struct lfs_config cfg = {
    .context = &bd,
    .read  = &lfs_emubd_read,
    .prog  = &lfs_emubd_prog_wrap,
    .erase = &lfs_emubd_erase,
    .sync  = &lfs_emubd_sync,

    .read_size   = 8,
    .prog_size   = 8,
    .block_size  = 8192,
    .block_count = 64,
    .lookahead   = 8192,
};

int main(void) {
    lfs_emubd_create(&cfg, "blocks");

    if (lfs_format(&lfs, &cfg)) {
       exit(1);
    }
    if (lfs_mount(&lfs, &cfg)) {
       exit(2);
    }
    if (lfs_unmount(&lfs)) { // Don't know why this is necessary, but it seems to be?
       exit(3);
    }
    if (lfs_mount(&lfs, &cfg)) { // Don't know why this is necessary, but it seems to be?
       exit(4);
    }
    if (lfs_mkdir(&lfs, "A") != 42) {
       exit(5);
    }
    lfs_mkdir(&lfs, "B");

    lfs_emubd_destroy(&cfg);
}

Has the following failure within lfs_mkdir(&lfs, "B");:
lfs: lfs.c: lfs_cache_prog: Assertion `pcache->block == 0xffffffff' failed.
Aborted

Note the wrapper that forces an error on operation 13. Note also that this doesn't happen if prog  returns LFS_ERR_CORRUPT. (Is program returning a positive error code considered an unrecoverable error? If so then this ticket is invalid.)

Returning a positive error code isn't valid, apparently.


Automation switch is off, but Motion switch active

I have the below setup:
{
"type": "automation",
"name": "A-Kühl-Gefrier",
"period": 60,
"autoOff": false
}
If one fridge door opens, the switch is set to on.
After 1 min the motion detection is active. In that case I check, if door is still open:

yes: message to me
no: turn off switch

That works fine. Nevertheless after I have turned of the switch, the motion switch is active every Minute. How can I really deactivate. What is going wrong?.
Usually the motion detection should be off, if the switch itself is off, isn‘t it.

Version 3.2.1


sudo ./renew.sh -y fails due to missing acme_tiny.py

python: can't open file 'acme_tiny.py': [Errno 2] No such file or directory

Is renew.sh not in the same directory as acme_tiny.sh for you?  renew.sh L34 should ensure that usage of $install_dir isn't needed.


fix: your cgo build is fixed

Things to note:

For the go binding for zmq4 to compile, libzmq-dev must be installed on the machine - not hermetic.
Once that is done, the next issue is that adding cdeps = [...] nor really any other c-related optiosn actually work.

I even added an absurd link option oogabooga and that did not break the linking step. (It doesn't even appear in the link command line).

It seems to be a bug in rules_go. See the proposed fix at:

See: https://github.com/bazelbuild/rules_go/issues/4135

Thanks. Yeah I saw your bazel-discuss@ updates and the PR.
Regards,
HaiXin
On Mon, Oct 7, 2024 at 2:57 AM Filip Filmar @.***>
wrote:

See: bazelbuild/rules_go#4135
https://github.com/bazelbuild/rules_go/issues/4135
—
Reply to this email directly, view it on GitHub
https://github.com/thx123/bazel-cgo/pull/1#issuecomment-2396462430, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFBXR26K24WLCLVR2FZUPLZ2JLG3AVCNFSM6AAAAABPCWFW3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGQ3DENBTGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


⚠ Bofrost.ch has degraded performance

In 98b3532, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 2069 ms

Resolved: Bofrost.ch performance has improved in 15314bc.


Want to Add JS Projects - Percentage Scored

Describe the project you want to add with tech stack
I want to add a JS Project as Percentage Scored
Expected behavior
It is a stylish animated JS Project made with Babel JS.
Screenshots (optional)

Additional context (optional )
Pls assign this issue to me under GSSOC 23

Pls assign this issue to me under GSSOC 23


Karavan Web - Unable to scroll to bottom of the properties

Hi @mgubaidullin , thanks for your effort building and maintaining such a cool tool.
Properties for some components are impossible to reach (scroll). For example, http and https component have long list of properties, and Security and Advanced options are not visible.

Same issue is on the UI Builder side (where Add new Route and Add Route configuration buttons are not accessible)

Tested on version 4.1.

It does not look like 4.1.

There is no 'Download Image' button in 4.1
There is no huge white empty space between header with filename + 'Run' button  and Designer tabs (routes, rest, beans)

Hi @mgubaidullin , sorry, my bad.
I copy pasted a command from https://github.com/apache/camel-karavan/blob/4.1.0/docs/WEB_DOCKER.md and haven't noticed that command contains 4.0.0. version instead of the 4.1.0
docker run -it --rm  --name karavan
--network karavan -p 8080:8080
-e KARAVAN_GIT_INSTALL_GITEA=true
-e KARAVAN_IMAGE_REGISTRY_INSTALL=true
-v /var/run/docker.sock:/var/run/docker.sock
ghcr.io/apache/camel-karavan:4.0.0
On 4.1.0 works well.


Fix capitalization of Bulk Methyl Seq L2 Attribute

Fix capitalization of Proportion of minimum CpG Coverage 10X --> Proportion of Minimum CpG Coverage 10Xto align with attribute reference in row 63
Closes https://github.com/ncihtan/data-models/issues/254

Thanks @clarisse-lau. It looks like the description is duplicated. Can you double check and open a PR fixing it!

Fixed the conflict by reverting the change proposed in #256 (revert in #258 ) and integrating both changes in this PR #253


Undefined array key 0 with php 8.1 and readonly

I have the following classes and test:
<?php

declare(strict_types=1);

namespace JsonMapper\Tests\Implementation\Php81;

class WithConstructorReadOnlyPropertyCollection
{
    /**
     * @param WithConstructorReadOnlyPropertySimple[] $simples
     */
    public function __construct(public readonly array $simples)
    {
    }
}

<?php

declare(strict_types=1);

namespace JsonMapper\Tests\Implementation\Php81;

class WithConstructorReadOnlyPropertySimple
{
    public function __construct(public readonly ?int $status = null)
    {
    }
}

    /**
     * @requires PHP >= 8.1
     */
    public function testCanHandleCustomConstructorsWithEmptyArray(): void
    {
        $factoryRegistry = new FactoryRegistry();
        $mapper = JsonMapperBuilder::new()
            ->withDocBlockAnnotationsMiddleware()
            ->withObjectConstructorMiddleware($factoryRegistry)
            ->withPropertyMapper(new PropertyMapper($factoryRegistry))
            ->build();

        $json = (object) [
            'simples' => [],
        ];

        $result = $mapper->mapToClass($json, WithConstructorReadOnlyPropertyCollection::class);

        self::assertInstanceOf(WithConstructorReadOnlyPropertyCollection::class, $result);
        self::assertIsArray($result->simples);
        self::assertInstanceOf(WithConstructorReadOnlyPropertySimple::class, $result->simples[0]);
    }

Basically a collection with items. But the schema allows (and that is ok) empty items.
However I get an "Undefined array key 0" from the default factory, because it assumes a key => value.
fyi ... for me it happened after the update of the php 8.1 but the error is also in the bestfit + without readonly reproducable

any updates on this issue?

@template-provider time and holidays season made me forget these reports. Sorry for that it wasn't my intention to leave you in the dark on it.
Working on it in https://github.com/JsonMapper/JsonMapper/pull/148

Merged, will be releasing a new version in a couple of minutes

@DannyvdSluijs I was also facing the same error in OMS API. After upgrading, the issue is resolved. Thanks :)


ROX-21957: compliance scans use separate pipelines for V1 and V2

Description
Moving V1 and V2 scans to use separate pipelines
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
UT and spinning up a cluster to ensure objects populate as expected.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test gke-qa-e2e-tests


Why is this so long?

I was trying to read this article to learn what this was all about, and what I can use it for, but I am kind of lost in the wall of test in the article, and wondering why its so long.
I mean it could be something like this:
The way I understand there are some simple steps you need to do.
Create a class
Publish a package
Run the script from your Environment
And then perhaps some extra info about roles and security.
How can those simple steps be such a long wall of text??
Sorry I am just wondering why?
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 2f09e8fa-e5dc-2e5d-3613-c6b4f6d7191a
Version Independent ID: 2f09e8fa-e5dc-2e5d-3613-c6b4f6d7191a
Content: Run custom X++ scripts with zero downtime - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/deployment/run-custom-scripts.md
Service: dynamics-365-cross-app
GitHub Login: @AndersGirke
Microsoft Alias: aevengir

Bug 834368 has been logged to address this issue.

@rudiobtain , Thank you for getting in touch. The reason why the text is like this is that the author believed that this amount of information was necessary in order to understand and use the feature.


fix(spelling): Fixed spelling in error handling - ceritificate vs certificate.

I found a minor spelling mistake in the code, that meant that the error handling is not reporting the right things.
Fixed spelling mistake, so that Serenity BDD reports the right error.
Changed from:
case /self signed ceritificate in certificate chain/.test(this.error.message):
Changed to:
case /self signed certificate in certificate chain/.test(this.error.message):
I know that you can find the diff in the git tab, but this is to enable other people to find this PR if they see the error message with a spelling mistake.

Awesome, thank you @andreasmarkussen!


fix: [M3-8424] - Fix CodeQL alerts for DOM text reinterpreted as HTML

Description 📝
This PR attempts to reproduce and resolve the CodeQL code scan alerts for DOM text reinterpreted as HTML. Alternatively, these alerts might be determined to be false positives and will be dismissed as so.
Changes  🔄
List any change relevant to the reviewer.

The changes proposed by this PR were generated by GitHub's Copilot Autofix feature.

Target release date 🗓
10/16/2024
How to test 🧪
Prerequisites
(How to setup test environment)

Install the CodeQL extension on VSCode
Install the CodeQL CLI tool using this guide

Once you reached the Create a database of your code with CodeQL step, cd into the src/ directory of the manager package and execute the codeql database create codeqldb --language=javascript command.
This is the last step you'll follow on this guide.

In a separate VSCode window, open the codeql-repo (this is one of the directories created using the linked guide).
Click on the CodeQL icon found in the VSCode sidebar.
Select the DataBase created from executing the codeql database create codeqldb --language=javascript command. (This DataBase will be located in the src/ directory of the manager package.

Verification steps
(How to verify changes)

In the Queries tab, navigate to the javascript/ql/src/Security/ directory.
Under CWE-079 locate the XssThroughDom.ql query and run it by clicking the play button.

Verify that running the query returns 0 results.

Under CWE-116 run all the queries by clicking the play button at the directory level.

Verify that running the query returns 0 results.

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

In the same boat as Hussain - encodeURIComponent makes sense to me. Will the other alerts be dismissed as false positives?

My hope is that by merging this small change, we should see if the alert goes away or at least trigger a new alert, which may provide more context. I will check with John and Jaalah before I take an action with respect to handling the alert on the GitHub page.

@carrillo-erik This PR is being reverted. Not only did it not fix the dependabot warnings but it introduced a bad bug - see https://github.com/linode/manager/pull/11017


⚠ Bofrost.lu has degraded performance

In cf2be78, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1266 ms

Resolved: Bofrost.lu performance has improved in 43ecd9f after 20 minutes.


PEP changes and code improvements in agents.ipynb

Also corrected typos in documentation and simplified some code in agents.ipynb.
Minor edit in agents.py

Thanks for the review.
Corrected it along with some other typos.

Updated

@MrDupin is this PR approved or please tell me if any more changes needed?

@goswami-rahul Peter Norvig merges changes. If you've passed all tests and stuck to style-guides, you should be fine.

This PR now contains commits that are already merged. This might lead to merge conflicts later. I'd suggest you close this PR, update your working directory, create a new branch and add just the changes that you originally wanted to make and open a new pull request. Always make a new branch before submitting a pull request or there will be duplicated changes.

This PR is messed up. I think it is because of commits in the master branch. Closing this PR.


Graceful shutdown

Currently the irc processes do not gracefully shutdown. This means, that all current connected channels will not be migrated to other instances within a low time-frame. This means, all channels will be only collected if our purge system is collecting stale processes and supervisors. But this will take ~30 seconds.

Finally implemented :muscle:


Reduce allocations

These are some small changes that should have a big effect on the overall number of allocations. There is still room for improvement but this was a bunch of low hanging fruit.

:+1:

@sharwell I implemented your feedback

:+1:


Missing binary for macOS (x86_64) with download-libtorch feature

I understand this is probably a @pytorch issue, but with download-libtorch I cannot run things locally with 2.4.0:
error: failed to run custom build command for `torch-sys v0.17.0`

Caused by:
  process didn't exit successfully: `/Users/cuducos/Library/CloudStorage/Dropbox/Projects/airnope/target/debug/build/torch-sys-6f2b19bbf05ccb75/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=LIBTORCH_USE_PYTORCH
  cargo:rerun-if-env-changed=LIBTORCH
  cargo:rerun-if-env-changed=TORCH_CUDA_VERSION

  --- stderr
  Error: https://download.pytorch.org/libtorch/cpu/libtorch-macos-x86_64-2.4.0.zip: status code 403

It makes sense: we can see here that this URL does not exist (maybe it should even be a 404, not 403, but anyway…).
Should tch-rs do something about it? Maybe check the URL before the download and offer a friendly error message if the binary does not exist for a given arch and os combo.

Just adding to the context: builds for macOS on x86 are gone for good.


Update macOS pool name in azure-pipelines.yml

The old name is no longer supported.

/cc @leculver


OutOfMemory exceptions for multiple opening of packages >256

See #80
Related: http://paulstovell.com/blog/nuget-performance

fixed by #87


Before install: drop existing partitions

In order to avoid collisions between newly generated partition tables, device names and UUIDs, mountpoints etc. it is strongly recommended to wipe the target installation disk or at least dropping existing partitioning tables.

Fixed with commit Exit if creating partition table fails and unmount filesystems.


BUG: optimize: Fix constraint condition in inner loop of nnls

This pull request fixes a bug in _nnls caused by a wrong check for constraint violation.
The check made was s[P].min() <= tol, which according to the paper this function is based on
(https://analyticalsciencejournals.onlinelibrary.wiley.com/doi/abs/10.1002/(sici)1099-128x(199709/10)11%3A5<393%3A%3Aaid-cem483>3.0.co%3B2-l) should have been s[P].min() <= 0.
This behaviour could cause non-converging iterations for definitely well-posed problems.
I have s[P].min() <= 0.
Closes #20302

Hi @ezander do you have any examples where this actually causes any errors? Because hitting actual zeros are never feasible in floating point arithmetic hence we have to assume things zero if they are small enough. That's why a tol is used. If the inequality was strict indeed we would have used zero instead of tol.

Hi @ezander do you have any examples where this actually causes any errors?
Yes, I do. I used nnls for fitting some piecewise linear function to some data using monotonicity constraints. And in very few of the cases the algorithm did not converge (or rather threw some RuntimeError), which I could trace back finally to the inner loop of _nnls. I could put that into a unit test, however, it is a bit messy and I was unable to extract some nice small MWE from it.

Because hitting actual zeros are never feasible in floating point arithmetic hence we have to assume things zero if they are small enough. That's why a tol is used. If the inequality was strict indeed we would have used zero instead of tol.
Sure, but we're not testing for equality to zero here. If it was s[P].min()==0 and you would turn that into -tol<s[P].min()<tol, I'd be totally fine, but here the check is s[P].min()<0, which checks for an interval $(-\infty,0)$ anyway, so there is no need for additional tolerance IMHO.

And, BTW, I think the inequality should be strict, because it's purpose is to check for a constraint violation, which is only given if some s is negative, not when it's just zero.

Messy or not if we can get some testing for this function that would be actually great. And if this solves these edge cases that also very nice. The authors also mention

In practice the NNLS algorithm seldom enters the inner loop C.

but apparently you managed to find those examples. The runtime warnings might be coming from the solve operations and indicates the illposedness of the problem anyways so if you can confirm that, that would be great too.
The strictness of the inequality is something I wondered while I was coding and in fact later they mention in the text

When a new variable has been included in the passive set P, there is a chance that in the unconstrained solution to the new least squares problem (step B4) some of the regression coefficients of the free variables will turn negative (step C1).

So they are indeed looking for negativity however having zero is the indicator that the constraint is still active hence it has to be nonstrict. In fact that's why all start by zeroing the set. Hence there is some confusion there algorithmically.

Also did you notice any performance benefits from this? If you have SciPy 1.11 lying around and if you have time for even a feeling based benchmark it would help us to judge whether there is any regression or not.

Okay. I'll try to set up a test case as unmessy as possible. But I can't do that before Sunday.
So far, I haven't seen a performance benefit. In my cases either the inner loop ran only once, or did not terminate at all (except of course by the max iterations criterion).

Okay. I'll try to set up a test case as unmessy as possible. But I can't do that before Sunday.

No problem, please take your time.

So far, I haven't seen a performance benefit. In my cases either the inner loop ran only once, or did not terminate at all (except of course by the max iterations criterion).

For this function, even no news is good news hence that's already good enough sign.

I added a test case for the bug now. If you want to see it, just revert the < 0 line back to <= tol and it should fail the test.

Hi @ezander apologies for the delay. I reorganized the inner loop and tested with your examples and the one given in #20302 and seemingly all pass. Could you please stress test it again as I understand you have a family of these pathological examples?

@lucascolley @j-bowhay do you know what the failing tests are complaining about?

Yes, you may need to add this file here (if appropriate):
https://github.com/scipy/scipy/blob/2a43e5a4b98c1c67a1a0d4acfa1b640cdb1cfc17/scipy/_lib/tests/test_warnings.py#L84-L114

Sounds like we should at least change to np.testing.suppress_warnings.

That's really strange; silencing warnings should not be this complicated though. But OK let me try.

Sounds like we should at least change to np.testing.suppress_warnings.

I could be wrong but that wasn't how I interpreted the comment in the test. I think it is saying to use np.testing.suppress_warnings in tests and then if unavoidable use in library code use warnings.catch_warnings()/warnings.catch_warnings() and add to the list bellow. @rgommers as the original author of the comment would you be able to confirm?

Ah yes sorry, just saw that the filter is in the public function.

Hi @ezander apologies for the delay. I reorganized the inner loop and tested with your examples and the one given in #20302 and seemingly all pass. Could you please stress test it again as I understand you have a family of these pathological examples?

Hi @ilayn, sorry, I also have a deadline looming, but I think I can do that the coming week.

@tylerjereddy I think this is ready to go and is eligible for backporting. Judging by the noise it generated, I think 1.13 is good enough for a fix. But not sure if this would cause a disruption on your end.
Could you let me know your preference?

@ezander I took the liberty to go ahead with preparing it for a possible v1.13 addition. But please let us know if you encounter more issues and I will be happy to work on it further. This is just to fix the obvious issues you highlighted and the issue in #20302

@ilayn Ok, I put the backport label on this please merge if it is reviewed/ready to go. If it is a bug fix that merits a backport I'll try to put it into 1.13.0rc2. 1.13.0 stable may become urgent pretty soon with NumPy 2.0.0rc1 imminent now.

Done


How to send text result back to main thread when using listen_in_background?

I've gone through as many of the examples and issues as I could possibly find and I haven't been able to come across a good solution. I have a main class which starts the recognizer class. The recognizer listens in the background and then calls the callback function while the main class performs other tasks (starting the UI, handling config file changes, etc.). When I try to pause listening the system throws a "cannot join current thread" error. I know that this is because I'm calling stop_listening while it's on the child thread, but I'm unsure how to get the callback function to send data back to the main thread so that the main thread can call the stop_listening function instead of the child thread.
Please help me understand this. Thanks!
Steps to reproduce
Using listen_in_background, set a callback function to be used when the audio is recognized. Within the callback function, emit a message to another waiting class.
import speech_recognition as sr
from threading import Thread,current_thread
import gi
from gi.repository import GObject as gobject

class MainThreadClass:
    def __init__(self, opts):
        self.recognizer = Recognizer()
        self.recognizer.connect('finished', self.recognizer_finished)
        self.recognizer.listen()

    def self.recognizer_finished:
        print current_thread()  // Child thread
        self.recognizer.pause()

class Recognizer(gobject.GObject):
    __gsignals__ = {
        'finished' : (gobject.SIGNAL_RUN_LAST, gobject.TYPE_NONE, (gobject.TYPE_STRING,))
    }
    def __init__(self):
        self.r = sr.Recognizer()
        self.m = sr.Microphone()
        with self.m as source:
            self.r.adjust_for_ambient_noise(source)

    def callback(self, recognizer, audio):
        try:
            text = recognizer.recognize_sphinx(audio, "en-US", self.keywords, None)
            self.emit("finished", text)
        except sr.UnknownValueError:
            print("Sphinx could not understand audio")
            self.emit("finished", '')
        except sr.RequestError as e:
            print("Sphinx error; {0}".format(e))

    def listen(self):
        print current_thread()  // Main Thread
        self.stop_listening = self.r.listen_in_background(self.m, self.callback)

    def pause(self):
        print current_thread() // Child thread
        self.stop_listening()

Expected behaviour
The recognizer_finished function should be in the main thread, and the call to recognizer.pause() should work.
Actual behaviour
Code throws a "cannot join current thread" error.
Say something! (listen function)
<_MainThread(MainThread, started<PHONE_NUMBER>39456)>

Got it! Now to recognize it (Callback function)...
<Thread(Thread-1, started daemon<PHONE_NUMBER>04160)>

++++++++++++++
Pausing (Pause function)
<Thread(Thread-1, started daemon<PHONE_NUMBER>04160)>
Traceback (most recent call last):
  File "./Blather.py", line 183, in recognizer_finished
    self.checkCommandFile()
  File "./Blather.py", line 201, in checkCommandFile
    self.read_commands()
  File "./Blather.py", line 114, in read_commands
    self.recognizer.pause()
  File "/mnt/Sage/Projects/blather/Recognizer.py", line 79, in pause
    self.stop_listening()
  File "/usr/local/lib/python2.7/dist-packages/speech_recognition/__init__.py", line 627, in stopper
    listener_thread.join()  # block until the background thread is done, which can be up to 1 second
  File "/usr/lib/python2.7/threading.py", line 931, in join
    raise RuntimeError("cannot join current thread")
RuntimeError: cannot join current thread

System information
My system is Ubuntu 17.04 x64
My Python version is Python 2.7.14.
My Pip version is pip 9.0.1 from /usr/local/lib/python2.7/dist-packages
My SpeechRecognition library version is 3.7.1
My PyAudio library version is 0.2.11
I installed PocketSphinx from pip.

Hi @ajbogh,
listen_in_background will create its own thread, and you have to call stop_listening from the same thread as you originally called it from. That said, if you install the latest library version (301f889399772bbb9ebc41e3748032ef83e1d48a or later), you can now call stop_listening(False) instead of stop_listening(), and this will fix your issue!


Bug: Bug that prevents page creation if images are submitted before saving the page.

Host

item
version

OS
Ubuntu 20.04

GROWI
6.0.7

node.js
14.17.6

npm
6.14.15

yarn
1.22.18

Using Docker
no

Using growi-docker-compose
no

(Accessing https://{GROWI_HOST}/admin helps you to fill in above versions)
Client

item
version

OS
Windows 11

browser
Google Chrome 110.0.5481.180 (Official Build) （64 ビット） (cohort: 110_Win_Cotrol)

How to reproduce? (再現手順)

Create a new page
Upload an image by pasting a file into the editor area
save the page

Then i got following bellow error:

@3265
Thank you for taking the time to raise this issue!
This problem has been fixed in the latest version (v6.0.8). I believe updating will resolve this issue.


Image issues in the getnighthawk homepage

Description
The image is not aligned properly with the supporting heading.

Expected Behavior
Align the image and the supporting heading to the same level.
Environment:

OS: [e.g. Ubuntu]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]
Device: [e.g. laptop, iPhone 8]

[Optional] To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

[Optional] Additional Context

Contributor Resources

See the Contributing to getnighthawk.dev Website
See the Project Site section of GetNighthawk project doc

@AnshumanDhiman the first part of the issue already has an open issue.

@warunicorn19 well I thought size of the image should be increased for the time being. But I think its ok if we're changing the whole image. That's a lot better. I updated the issue.

@AnshumanDhiman there have been some site updates since this bug was filed. Will you confirm if this is still on open defect?

@AnshumanDhiman there have been some site updates since this bug was filed. Will you confirm if this is still on open defect?

I checked it. The issue is solved. Let me close this issue


Feature Request: Create OCWare host emulator for CLI Testing

Product: (OC-SDR, OC-LTE, OC-LTE, OC-Power, others)
OC-SDR
Component: (PSU, GBC, BBU, FEM, LED, ME)
GBC
Category:

Software/stack

Description
Describe the solution you'd like
Create host emulator for CLI/OC-admin. Idea is to run the OCWare without the need of physical hardware.
Is your feature request related to a problem? Please describe.
In order to fully test CLI it would be useful to have a full emulator to break dependency on hardware for tests.

Originally commented by mayuri2016
Added few comments on this feature requirement. Will call for discussion to explore this option more and feasible solution.
Proposed Functionality Details:
This capability will provide host emulator platform removing dependency of actual physical hardware.
•	Required transmitter which can generate OCMP packets as its generated by host SW to send to firmware
•	Required receiver to receive these packets, validate the packet content and send response back
•	Transmitter can be either a host Linux machine where CLI SW can be run and OCMP packets can be generated
•	If there is need to explore additional functionalities for Intel, option for qemu emulator can be checked. But only for OCMP packets testing, this may not be required.
•	Checked for TI microcontroller emulator- currently there is no open source simulator available for these low cost microcontroller. Keil or IAR provides this feature, but that comes with a license.
•	TI recommends to use Launchpad to emulate tiva microcontroller as its most easier approach.
For the receive part, below 4 ways can be explored:
o	Use TI DK Launchpad to receive OCMP packets and send response, while other HW functionalities can be stubbed out
o	If its just needs to be sw component to send/receive OCMP packets independent of TIVA, current host sw can be customized to make it work like this.
o	Unit test framework might be doing similar functionalities for host sw- receiving commands from CLI and sending back dummy reply

Originally commented by samudhira
We implemented OCWARE_STUB application to stubbing the config and status parameter values requested from the CLI application. In that, we are using Ethernet UDP communication to send/receive the message frame from/to middleware application. So far we have implemented config and status parameters for all te subsystem. Now we are in under discussion for command, alerts and other parameters.


Lab 4-1: KimTay Pet Supplies

When doing the Lab the website crashed on me and when trying to do it again i kept getting the error Kimtable does exist when I keep selecting the lab
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/question
This is issue tracker for VS Code editor itself.
Please use proper feedback channel for your course.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Elasticsearch deployment automation does not work anymore

Calling
PUT https://management.azure.com/subscriptions/309065ca-a060-4592-8096-b74694126b61/resourceGroups/azure-demo-01-monitoring-rg/providers/Microsoft.Elastic/monitors/test-elasticsearch?api-version=2023-02-01-preview
{"location":"westeurope","properties":{"monitoringStatus":"Enabled","userInfo":{"emailAddress":"THES@softwareag.com"}},"sku":{"name":"ess-consumption-2024_Monthly@TIDgmz7xq9ge3py"},"tags":{}}

does not work anymore for a token retrieved locally using az account get-access-token. I am always getting the following error message:
Status 400
{
    "error": {
        "code": "BadRequest",
        "message": "Cannot proceed with the request as the user is not authorized"
    }
}

It is still working fine with a token retrieved in Azure Cloud Shell (in the Azure Portal) - for the same user.
Some more details:
I have been using Terraform for setting up my Azure infrastructure including an instance of Managed Elasticsearch for several months, and it has always been working fine until yesterday (08.12.23) morning CET. It failed for the first time yesterday (08.12.23) afternoon, and it has failed ever since.
Please find the Terraform configuration of a repro case in the attachment.
Since Friday afternoon, it would always complain:
│ Error: creating Monitor (Subscription: "309065ca-a060-4592-8096-b74694126b61"
│ Resource Group Name: "azure-demo-01-monitoring-rg"
│ Monitor Name: "azure-demo-01-elasticsearch"): performing MonitorsCreate: unexpected status 400 with error: BadRequest: Cannot proceed with the request as the user is not authorized
│
│   with module.monitoring.azurerm_elastic_cloud_elasticsearch.default,
│   on monitoring\monitoring-elasticsearch.tf line 1, in resource "azurerm_elastic_cloud_elasticsearch" "default":
│    1: resource "azurerm_elastic_cloud_elasticsearch" "default" {

Yes, I am the owner of the resource group, and Terraform is working fine for dozens of other resources. Yes, I can log-in to Elastic Cloud with my Microsoft account<EMAIL_ADDRESS>Yes, I can create an Elasticsearch instance in the same RG with the same resource configuration with the same user in Azure portal.
I have tried the Terraform script with location westeurope, eastus and southeastasia. Same result.
I have tried creating the resource using Azure CLI:
az elastic monitor create -n test-elasticsearch -g azure-demo-01-monitoring-rg --user-info "{firstName:Thomas,lastName:Hesse,companyName:'Software<EMAIL_ADDRESS>--sku "{name:ess-consumption-2024_Monthly@TIDgmz7xq9ge3py}"
Result:
(BadRequest) Cannot proceed with the request as the user is not authorized
Code: BadRequest
Message: Cannot proceed with the request as the user is not authorized

I have exported an ARM template in the Azure Portal, cf. attachment. I can create the resource using the template in the Azure Portal, but it fails when I try the following:
az deployment group create --resource-group azure-demo-01-monitoring-rg --template-file ExportedTemplate-azure-demo-01-elasticsearch.json --parameters @ExportedTemplate-azure-demo-01-elasticsearch-parameters.json
Result:
{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/309065ca-a060-4592-8096-b74694126b61/resourceGroups/azure-demo-01-monitoring-rg/providers/Microsoft.Resources/deployments/ExportedTemplate-azure-demo-01-elasticsearch","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"BadRequest","message":"Cannot proceed with the request as the user is not authorized"}]}}
I have even tried calling the Azure Management API:
PUT https://management.azure.com/subscriptions/309065ca-a060-4592-8096-b74694126b61/resourceGroups/azure-demo-01-monitoring-rg/providers/Microsoft.Elastic/monitors/test-elasticsearch?api-version=2023-02-01-preview
{"location":"westeurope","properties":{"monitoringStatus":"Enabled","userInfo":{"emailAddress":"THES@softwareag.com"}},"sku":{"name":"ess-consumption-2024_Monthly@TIDgmz7xq9ge3py"},"tags":{}}

Result:
Status 400
{
    "error": {
        "code": "BadRequest",
        "message": "Cannot proceed with the request as the user is not authorized"
    }
}

I have tried multiple versions of the API.
Yes, I am using a valid token, the API is working fine for other resource types.
Some more results of my analysis:

Terraform is working fine when I run it in an Azure DevOps pipeline. It only fails when I run it locally.
az elastic monitor list is working fine. Only az elastic monitor create fails when I run it locally.
az elastic monitor create is working fine when I run it in a Cloud Shell in Azure Portal, but not on my PC.
Creating a token in Cloud Shell with az account get-access-token and using it in Postman on my PC is working fine, but not with a token created with az account get-access-token on my PC. When I compare the tokens, I see a difference in the unique_name claim. It is<EMAIL_ADDRESS>for the token created in Cloud Shell and<EMAIL_ADDRESS>for the token created locally, cf. attachments.

Maybe this is causing the issue? Please note that my Elastic Cloud username is<EMAIL_ADDRESS>Are you taking the Elastic Cloud username from the unique_name claim of the token and not from the userInfo.emailAddress of the request body? Or are you forwarding the token to Elastic Cloud? (I hope not…)
Anyhow: How can I log-in to Azure CLI in such a way that Terraform and az elastic monitor create are working locally again?
JWT_Payload_Local.json
JWT_Payload_Cloud_Shell.json
Currently I see no way of setting up the resource automatically. Please help!
Best regards,
Thomas

Same issue, looks like replacing elastic_cloud_email_address with the current account's email do the trick but as OP mentioned it breaks the idea of automated provisioning.


Call column_type on parsed field to get the actual column type

Fixes bug where column type was not being detected which caused sorting to fail when sorting by a string column
containing nil values. In this case, the nil value was not getting  substituted with a value that allows for proper sorting

@gtanzillo Would it be possible to add a spec showing what this fixes?

possible spec which cover the issue:
diff --git a/spec/models/miq_report_result_spec.rb b/spec/models/miq_report_result_spec.rb
index 41f506b9a1..3bbee37f2f 100644
--- a/spec/models/miq_report_result_spec.rb
+++ b/spec/models/miq_report_result_spec.rb
@@ -108,6 +108,24 @@ RSpec.describe MiqReportResult do
       allow(ManageIQ::Reporting::Charting).to receive(:detect_available_plugin).and_return(ManageIQ::Reporting::C3Charting)
     end

+    # nil represents maximum value from all values for the column
+    context "any column value is nil on report result" do
+      it "sorts results correctly when column is string" do
+        MiqReport.seed_report(name = "Vendor and Guest OS")
+        vm = Vm.first
+        vm.update_attributes(:operating_system => FactoryBot.create(:operating_system, :name => "Linux", :product_name => "Linux"))
+        vm_amazon = FactoryBot.create(:vm_amazon)
+
+        rpt = MiqReport.where(:name => name).last
+
+        rpt.generate_table(:userid => "test")
+        report_result = rpt.build_create_results(:userid => "test")
+        report_result.reload
+
+        expect(report_result.report_results.table.data.first['vendor_display']).to eq(vm_amazon.vendor_display)
+      end
+    end
+

Jansa backport details:
$ git log -1
commit adeeee5d5ea1be0c4c90ad252da5c0934ec911ef
Author: Jason Frey<EMAIL_ADDRESS>Date:   Mon Aug 3 10:00:31 2020 -0400

    Merge pull request #20398 from gtanzillo/report-sort-col-type

    Call `column_type` on parsed field to get the actual column type

    (cherry picked from commit 6c94d5d2f4ef7b24a1f26d2eba0a77f4ac4a00b1)


Support protobuf in web

Request Statement
When making a request for data with content type "application/protobuf" or "application/x-protobuf" or "application/octet-stream" and expecting a response of type Response<List<int>> you can get protobuf content from a REST API using dio in Windows, iOS, and Android but not on Web.
Web causes issues because the browser's XMLHttpRequest doesn't recognize protobuf as a valid wire format without some coaxing. Or rather the browser sees a stream of bytes and assumes we want to interpret those bytes as a file. You can see this in action by hitting an endpoint serving protobuf in your browser. The browser will attempt to download the content as a file.
Solution Brainstorm
No response

Hello! It turns out I have made a silly mistake,
I was reading the data correctly but the browser has CORS. (Curse you CORS!)
I added support on my backend for the correct CORS related headers and everything works as it should.


Getting unknown property: yii\web\Application::enableRegistration

Hi Dmitry,
Thanks again for this excellent module!
Yesterday I stumbled into what might be a logic bug, please verify as follows:
HOW TO REPRODUCE

Integrate yii2-user with Yii2-advanced template using configuration in documentation.
Override the registration model as documented in https://github.com/dektrium/yii2-user/blob/master/docs/overriding-models.md. In my case, the only 'magic' introduced is to use a different template for the registration process.

Now the introduced controller looks like this (listing of frontend\controllers\RegistrationController):
<?php
namespace frontend\controllers;
use Yii;
use dektrium\user\controllers\RegistrationController as BaseRegistrationController;
class RegistrationController extends BaseRegistrationController
{
    public function actionRegister()
    {
        $this->layout = '/_register.php';
        return parent::actionRegister();
    }
}

Test as follows;
Open URL: http://localhost/registration/register (Remember the URL is incorrect by design - this is a test! The correct URL is http://localhost/user/registration/register BUT we also need to test how the application will behave when it meets the unexpected)
OUTCOME
"Getting unknown property: yii\web\Application::enableRegistration". This also happens when you test with http://localhost/registration/resend. It doesn't  happen for any other incomplete actions from https://github.com/dektrium/yii2-user/blob/master/docs/available-actions.md
EXPLANATION
The extension of RegistrationController is located in the Yii2 standard folder for Controllers (frontend\controllers) therefore Yii sends the request to this as Controller (really extension) but the code reproduced above calls  return parent::actionRegister() when apparently the module is not initialized. The error occurs because parent::actionRegister() in the module tests for the setting enableRegistration
public function actionRegister()
    {
        if (!$this->module->enableRegistration) {
            throw new NotFoundHttpException();

REQUIREMENT/EXPECTED BEHAVIOUR
The module is properly integrated with Yii2 and the overriding of the controller seems valid, I suggest that the module should throw new NotFoundHttpException() if you agree with my analysis or otherwise please let me know what I've done wrong
Regards,
Adam

The problem is that when you accessing registration controller via url registration/register (not user/registration/register, Yii sets the controllers' module property to Application. There are two ways to fix throwing Getting Unknown property exception:

restrict access to those urls via urlManager
check for module class:

<?php
namespace frontend\controllers;
use Yii;
use dektrium\user\controllers\RegistrationController as BaseRegistrationController;
class RegistrationController extends BaseRegistrationController
{
    public function actionRegister()
    {
        if (!($this->module instanceof \dektrium\user\Module)) {
            throw new NotFoundHttpException();
        }
        $this->layout = '/_register.php';
        return parent::actionRegister();
    }
}

Ok, thanks


Issue Hosting Images Larger Than ~200MB

Watson Version: 1.2.11
.NET Framework: 4.6
Issue:
I am building an application which is meant to host up files to be uploaded to a web interface. Recently we were running tests with large .tif files and we noticed the application would hang when we tried to access the content route associated with that image. For example, the user would select an image which would get copied to a cache folder next to the .exe which is where the image would get hosted from (<IP_ADDRESS>/img/testimage.tif) whenever we try to access this URL the application hangs and we have to force exit. We noticed that with 175MB images it's able to chug through but once we go past 200MB images we start experiencing this issue. Is this package capable of hosting up such large files?

Hi @ekarkosApollo yes it is - are you settings Server.ReadInputStream = false and then using HttpRequest.DataStream and HttpRequest.ContentLength, or are you using HttpRequest.Data?

I was not able to find the Server.ReadInputStream setting, it may be because I am on an older version. I believe we are just using HttpRequest.Data, however we are not responding to the HttpRequest with the image data, we are simply copying it into a directory and setting that as an endpoint where the other application can access it along the lines of server.AddContentRoute("/img/" + fileName) and that URL then gets handed off to the other application which handles uploading.

Ah ok, I see what's happening.
ContentRouteProcessor.cs upon GET is reading the file info memory rather than returning the stream.
So we'll need to do two things.

I'll need to amend the method to support sending a stream back to Watson, which will eliminate the need to load the entire file info memory.

I'll have to ask you to set the ReadDataStream variable to false on your side.

I should be able to get to this today or tomorrow, hopefully that timeline will be ok for you?
Cheers, Joel

I had a few minutes and think I have this knocked out.  Tested both with streams and with byte arrays and the logic is working and disposing of streams appropriately.  NuGet v2.1.3 will be going live shortly (https://www.nuget.org/packages/Watson/2.1.3) and the commit can be found here: https://github.com/jchristn/WatsonWebserver/commit/39baf658b70137c802041468b364d8e9686e8b29
Could you test on your end by adding Server.ReadInputStream = false?  Thanks!

Awesome, I will work on updating our application to the newest version, I will need some time but I will keep you updated.
Thanks so much for the quick responses and resolution.

My pleasure!  Please re-open or file another issue if there are problems.  Cheers

This update seemed to fix the issue we were having with large files thank you so much!
I don't know if you want a separate issue opened for this, but we are now seeing a problem with getting data out of a POST.
Whenever we receive a POST the data that used to be contained in request.Data is null. Do the 2.0.x+ versions of this package get data from POSTs differently now?

For reference I am currently on version 2.1.3 targeting .NET framework 4.6.2

Hi Eric if you have ReadStream set to true on the server the request body will be in HttpRequest.DataStream and HttpRequest.ContentLength will be set.
Sent from my iPhone

On Aug 1, 2019, at 2:35 PM, Eric Karkos<EMAIL_ADDRESS>wrote:
For reference I am currently on version 2.1.3 targeting .NET framework 4.6.2
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


migration to jupyter book 0.14

Describe your changes
Migrates ploomber-core to jupyter-book 0.14 (https://github.com/ploomber/contributing/issues/35). Only needed to change image due to lack of conf.py
Issue ticket number and link
Closes x
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have added thorough tests (when necessary).
[x] I have added the right documentation in the docstring and changelog (when needed)

great work!