xGov-123: AlgoDirectory (directory.algo)

Hey Silent, can you explain to me how this is different than arc53 aside from being forced to buy a directory.algo segment & listings expiring?

@kylebeee The proposed ARC-53 standard ("A specification for a decentralized, Self-declared, & Verifiable Tokens, Collections, & Metadata") could certainly be utilized in directory listings to provide structured data for tokens and collections.
The Directory is not going to be opinionated about how listings are defined beyond some core fields.  It could be possible, for example, to have one listing that self-identifies as ARC-53 and displays as such in the UI while another listing (for which ARC-53 is not relevant) follows a schema such as schema.org and displays differently.
Once the core open source platform is created, the community could contribute additional ways to visualize listing data for various schema or even treat the directory as a white-label product that could be forked, rebranded, and customized for specific purposes.

Would highly recommend utilizing it or even extending it! When i proposed it, directory.algo was top of mind as a use case for it and i made sure it was an extensible, living standard so that things like schema.org could be added to it.

Be sure to change the status to Final if you want to be part of the next session
status: Draft -> status: Final

Proposer, please post your algorand forum discussion thread link here. Thank you.


Henchman artifacts are missing in circleci.

No artifacts @ https://circleci.com/gh/apigee/henchman/124#artifacts
Last artifact found for master @ https://circleci.com/gh/apigee/henchman/104#artifacts

https://discuss.circleci.com/t/artifacts-not-getting-collected/465/10
Someone had a similar issue and had to manually transfer artifacts. So package.sh now transfers artifacts.


undeclared identifier in srcsel.v

There are two undeclared identifier , rob_data1 and rob_data2, in srcsel.v

Dear ycyang0508
Thank you for your report.
The module "src_prf_or_arf" which has rob_data1 and rob_data2 was unnecessary and was removed from this repo.
Sincerity,
ridecore team


browser-esbuild will not resolve local paths in SASS stylesheets

Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
If you use either the builder @angular-devkit/build-angular:application or @angular-devkit/build-angular:browser-esbuild, and utilize local paths to reference stylesheets, the build will break.
package.json
...
"dependencies": {
  ...
  "@angular/material": "^17.0.0",
  "@shared/styles": "file:./src/shared/styles",
  ...
}
...

src/styles.scss
@use "@angular/material"; // this one works fine
@use "@shared/styles/functions"; // this one breaks the build

src/shared/styles/functions.scss
// exists

Please provide a link to a minimal reproduction of the bug
https://github.com/yutamago/repro-esbuild-package-sass-import/tree/master
Please provide the exception or error you saw
ng serve

| Building...X [ERROR] Can't find stylesheet to import.
  ╷
3 │ @use "@shared/styles/functions";
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  src\styles.scss 3:1  root stylesheet [plugin angular-sass]

    angular:styles/global:styles:1:8:
      1 │ @import 'src/styles.scss';
        ╵         ~~~~~~~~~~~~~~~~~

Application bundle generation failed. [1.986 seconds]

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 17.0.0
Node: 18.18.0
Package Manager: npm 9.6.7
OS: win32 x64

Angular: 17.0.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0
@angular-devkit/build-angular   17.0.0
@angular-devkit/core            17.0.0
@angular-devkit/schematics      17.0.0
@angular/cli                    17.0.0
@angular/material               17.0.0
@schematics/angular             17.0.0
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else?
No response

Thanks, that's a solution I can live with. I'll try it out first thing in the morning.

Having this same issue as well.

If you are still encountering issues after the changes described above, please let us know.

The issue I'm having is similar, but not identical. I have a reference to a .scss file that contains my variables and I use an import statement at the top of other .scss files to reference it. The result is the same as the original poster's. I'll push my branch tomorrow morning and open a new issue with steps to reproduce.
Sorry to have to mention it. Thanks for everything you and the team do to make Angular what it is.


opensycl: 0.9.4 -> 24.02.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/OpenSYCL/OpenSYCL/releases.
meta.description for opensycl is: Multi-backend implementation of SYCL for CPUs and GPUs
meta.homepage for opensycl is: https://github.com/OpenSYCL/OpenSYCL
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 24.02.0 with grep in /nix/store/iz8pj3agli8yvgxh4p8b6j43fk4lqj7b-OpenSYCL-24.02.0
found 24.02.0 in filename of file in /nix/store/iz8pj3agli8yvgxh4p8b6j43fk4lqj7b-OpenSYCL-24.02.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
opensycl
opensyclWithRocm

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/6ee9527300511b423fbc60ddb3d935dcfcf2aabb#opensycl

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

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

1 package failed to build:

opensyclWithRocm

1 package built:

opensycl

Maintainer pings
cc @yboettcher for testing.

@ofborg build opensyclWithRocm

It won't build with rocm without any modifications. I'm short on time as of now, but it looks like due to rocm providing an opencl implementation, the build system enables opencl support, which requires a patched version of the spirv-llvm-translator. It does build locally when I explicitly disable the opencl build.
I have not yet managed to make cmake use the translator from nixpkgs. Instead, it tries to download (and patch) the translator at build time.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/OpenSYCL/OpenSYCL/releases.
meta.description for opensycl is: Multi-backend implementation of SYCL for CPUs and GPUs
meta.homepage for opensycl is: https://github.com/OpenSYCL/OpenSYCL
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 24.06.0 with grep in /nix/store/l67sylgq3ksd9r32rbjpw78gsvydccbx-OpenSYCL-24.06.0
found 24.06.0 in filename of file in /nix/store/l67sylgq3ksd9r32rbjpw78gsvydccbx-OpenSYCL-24.06.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

opensycl
opensyclWithRocm

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/2ab260cb9931a6b1073b73268bc3c06014ad8145#opensycl

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

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

1 package failed to build:

opensyclWithRocm

1 package built:

opensycl

Maintainer pings
cc @yboettcher for testing.

Add a :+1: reaction to pull requests you find important.

I had another go at the fetchcontent problems by patching the cmake files to just use find_program for the llvm-spirv-translator and supplying the patched translator (similar for the opencl headers). That worked, but I still could not get the opencl backend to build. It appears that adaptivecpp uses some symbols from the opencl-clhpp header that don't exist in the clhpp version provided by nixpkgs. It appears that the last update to the nixpkgs clhpp was 3 years ago, while a git blame on the clhpp repository for the symbol in question shows that it was added some time last year.
Due to the outdated version of clhpp in nixpkgs, I would disable the opencl backend for now. As for testing: I can only test the rocm and host backend. I cannot test cuda.
I also noticed that the "generic" workflow of acpp does not work with hip on nix, but I currently have no idea why. When I instruct acpp to compile for a specific hip architecture, it works. If I rely on their jit, it does not. The openmp backend works in both cases.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/OpenSYCL/OpenSYCL/releases.
meta.description for opensycl is: Multi-backend implementation of SYCL for CPUs and GPUs
meta.homepage for opensycl is: https://github.com/OpenSYCL/OpenSYCL
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 24.10.0 with grep in /nix/store/51q7a73c20d5kgpvhdgwhwd4k6dgm6np-OpenSYCL-24.10.0
found 24.10.0 in filename of file in /nix/store/51q7a73c20d5kgpvhdgwhwd4k6dgm6np-OpenSYCL-24.10.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

opensycl
opensyclWithRocm

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/51q7a73c20d5kgpvhdgwhwd4k6dgm6np-OpenSYCL-24.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/b799e2d93e710f1c273994c37d57a366bdfab7a9#opensycl

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/51q7a73c20d5kgpvhdgwhwd4k6dgm6np-OpenSYCL-24.10.0
ls -la /nix/store/51q7a73c20d5kgpvhdgwhwd4k6dgm6np-OpenSYCL-24.10.0/bin

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

x86_64-linux

:x: 1 package failed to build:

opensyclWithRocm

:white_check_mark: 1 package built:

opensycl

Maintainer pings
cc @yboettcher for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Minimize opportunities for malware to save keys on quarantined hardware

There are many ways that malware on the quarantined hardware could save the private keys to persistent storage. This would be a significant breach of Glacier security, since now a thief would only need to steal one laptop and/or USB key to get access to my funds, instead of having to steal multiple paper keys in multiple physical locations.
The design document mentions "Non-persistent memory environments for cryptographic tasks" as a tactic, but the protocol doesn't put a lot of effort into prevention. There are some simple steps we can take to minimize these opportunities.

Remove HDD

See #8

Remove App USB ASAP

The App USB is mounted read-write and could easily be used to write keys to persistent storage. There's no reason to leave it connected once Glacier and the other software have been copied off.
The Boot USB is mounted as read-only so would require more work (and presumably root access) to use as persistent storage.

Prevent use of sudo

There are many other persistent storage mechanisms in modern laptops. Malware could remount the Boot USB as read-write, re-flash the BIOS firmware, etc. Most if not all such operations would require root access.
Unfortunately the default Ubuntu Live environment allows the use of sudo without any password, making such access trivial for malware.
Based on the security best practice of "principle of least privilege", we should have the user change the default sudo privilege level before running GlacierScript. This will also require the user to use passwd to create a unique password for the default user (otherwise malware would just use the default password).
passwd
sudo rm /etc/sudoers.d/casper

There is a command line option for grub (toram) that loads the entire OS into ram (at least as far as I've tested it with my experimentation on icecube).
Perhaps when booting the live USB the user could be instructed to access the grub prompt and add this option to grub's command line. I suppose there must be a way to do so right before one chooses to "Try ubuntu without installing it"
I am not sure whether this is workable with a bloated distro that takes a lot of RAM and I haven't tried it myself, but it might be a good idea to check.

@jazarija I suspect that will require far too much RAM. Already, Ubuntu 18.10 is too big to download on a 4GB laptop (see comment on #25).

I see. I still think having a custom distro built from a script to be a superior solution for minimizing this attack surface, though I don't have the required motivation to promote it and make it mainstream.

The same suggestion applies to section 5.2 instruction 4 d) where the user generates the signed transaction and is again using the mobile phone's QR reader.


LINT: Replace mocha runner?

There's not much development happening, a test runner is unlikely to be a priority


Allow set al num buffers

This was the best way I could think of to do this without breaking the API. I would probably prefer to pass this in as part of the constructor, but didn't want to cause a bunch of unnecessary refactoring. I know we discussed this before but I really believe that being able to control the number of buffers is important.

Outdated.


When adding multiple view with scrollview,it cant be scrollable.

Well, that's because you might have
app:flipOnTouch="true"

enabled in your xml layouts. Set this flipOnTouch attribute to false, and then your views will be scrollable. But then you will have to flip it yourself on any button click etc.

yes I have app:flipOnTouch="true" in XML . so I just remove it in each view then do it programically? I want to flip when user click on it as well as it should be scrollable? This is possible?

Yes. It could be possible. You have to add touch event listener and manually detect the difference in scrolling and touching, and programmatically flipping the view.


feat: added deployment scripts execution after deploy service pack step

closes #49

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[core] OpenGL ES extensions recorded incorrectly

Issue description
The GL_OES_compressed_ETC1_RGB8_texture extension is not being reported by raylib on the Raspberry Pi, even though the pi's OpenGL ES implementation supports it.
I can see that glGetString(GL_EXTENSIONS)  here in rlgl.h is returning a string that includes "GL_OES_compressed_ETC1_RGB8_texture".
The problem seems to be that the dup string, from which the extension string is tokenized, is freed  while elements of extList still have pointers into the now-deallocated string.
The free() call seems to mark the beginning of the freed memory, and that marker garbles the start of the extension string, causing the first element ("GL_OES_compressed_ETC1_RGB8_texture", as it turns out) to be missed. It's just luck that the rest the string is preserved for as long as needed by the parsing code.
I've confirmed that commented out the RL_FREE call "fixes" this problem, but obviously this isn't a solution. I didn't immediately see a trivial/not-ugly fix.
Environment
Raspbian Stretch Lite, 4.14 kernel, full Open GL not enabled.

Ouch! Good catch! Yes you're right! No worries, I can review that part of the code!

Terrific--thanks!

@DanRosenfeld Code reviewed on commit https://github.com/raysan5/raylib/commit/a386cedae6ddb1bc844ee3eea80a61066ba4105d.
Please, let me know if it works, I haven't tested it on the RPI.

Closing this issue, please reopen if problem persist.

Reviewed again in commit https://github.com/raysan5/raylib/commit/a727f5768f6e588d45e47dd26da9af82597ba1d3.


Thread.Abort is not supported in .NET Core

Since the upgrade to .NET Core, the application occasionally closes without warning when I click the "Cancel" button while many threads are running.  No error message is displayed, so I pulled the source and reproduced locally while running under the Visual Studio debugger, and got this PlatformNotSupportedException:

Thread abort is not supported on this platform.

At this call stack:
   at System.Threading.Thread.Abort()
   at SQLQueryStress.LoadEngine.ThreadKiller.KillEm() in C:\Code\SqlQueryStress\src\SQLQueryStress\LoadEngine.cs:line 610
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

The problem is at this line of code, and the reason is documented here:

This method is obsolete. On .NET 5.0 and later versions, calling this method produces a compile-time warning. This method throws a PlatformNotSupportedException at run time on .NET 5.0 and later and .NET Core.

I'd be interested in contributing a fix, but wanted to open the issue before starting, to discuss possible solutions (don't want to overstep my bounds!).
The docs on How to Stop a Thread indicate that CancellationTokens should be used to cooperatively cancel threads.
However, reading through the source code, I wonder if the Thread.Abort could just be removed altogether.  It looks like you have cooperative cancellation built in, and this Thread.Abort is kind of a "last resort" if threads aren't ending quickly enough.
Removing Thread.Abort fixes the problem in my case - all of the threads eventually successfully cancel, and control returns to the UI
Like I said, I'm glad to contribute a fix - but wanted to make sure there's not some context I'm missing, as I'm very new to the codebase 🙂

My repro scenario involve spinning up 200 threads of a query that will all be blocked indefinitely.  Once they have all successfully started (I can see all 200 connections on the SQL Server side), I click cancel.  If you'd all like the details, let me know!

By the way, thanks for maintaining this excellent tool - it has been a huge help to me as I learn things about SQL Server.

Interesting - So in other words, the "ThreadKiller should really only be concerned with closing Connections...

@ErikEJ and calling Cancel() on the running SqlCommand objects, yeah!  "Killing" the threads should really be about cleanly ending the work the threads are doing.  Maybe the class could be renamed to ThreadEnder or WorkStopper (kidding! 😜).
As a related but separate thought, I had the idea that it might be useful to see the number of active threads in the UI.  This would give users an indication that progress is being made on the cancel operation.  I could open a separate issue for that if you think it has merit.

Good idea, please create a separate issue for that.

I have created a PR here: https://github.com/ErikEJ/SqlQueryStress/pull/90

@ErikEJ I just tested that PR with my scenario, and this change has uncovered a race condition. There are two different methods calling QueryOutInfo.CompleteAdding() - the main StartLoad(BackgroundWorker) method, and the StartLoadThread method that represents the individual running threads.
As the last of the threads are canceling, the StartLoad one completes adding for that BlockingCollection, and then the last one or two load threads try to add items to the collection and throw errors.
I need to look into a little more closely (maybe tomorrow) to make a suggestion about the fix, but wanted to let you know there was a problem with the PR in the meantime.

Is that not #88 you discovered?

@ErikEJ No, I believe we introduced this here now that I've had a chance to take a closer look.  I was off about QueryOutInfo.CompleteAdding() being the problem, that was a symptom.
After cancelling a SqlCommand and closing the SqlConnection, the KillEm method used to loop until the Thread was finally dead (checking Thread.IsAlive).  The calling code is expecting that when the threads in cancellerThreads complete, that the corresponding load threads are also complete.
The simplest solution might be to add that looping behavior back in to CancelEm, just leaving out the Thread.Abort line.  This would comply with the expectations of the calling code.  I tried that locally and it worked for me.

Great! I have updated the PR...


tarball: add --show-trace to nix-env command

Description of changes
Otherwise, when this fails on Hydra, we have no way of seeing what went wrong, e.g. https://hydra.nixos.org/log/2210x8gsd8jgdx73qa7hmhmmridyy7yp-nixpkgs-tarball-23.05pre450719.c11c55dd08a.drv
Draft until my nix-build -A tarball pkgs/top-level/release-small.nix is done.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Also for the channel script as discussed?


Write a concise guide on ETL to link from the landing page

Description:
Write a concise guide on ETL to link from the landing page
Affected Product Version:
EI 1.1.0

Wrote [1] and merged it via [2].
[1] https://ei.docs.wso2.com/en/7.1.0/streaming-integrator/guides/performing-etl-tasks/
[2] https://github.com/wso2/docs-ei/pull/2016


Major update to the Mixer docs.

Revamp the docs to remove programmer-level info and present an
operator-centric view of the design.

Deemphasize "Mixer" in favor of Policies and Telemetry throughout. We now
focus on the "What" rather than the "How".

Increase consistency in the terms we use to avoid confusion for the reader.

Staging site: https://geeknoid.github.io/istio.github.io/

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid, geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

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


Analytics

Traditional analytics tools don't provide graph analytics. Helm would enable this.
When enabled we could record paths taken by the user, then:

Identify common paths. If one exists already, recommend the shorter path to the user.
If one doesn't exist, give this feedback to the app developer <-- common navigation paths / usages to improve UX. We could measure how this affects retention.

Also say there was an on-boarding process, with X screens to complete. We measure the total time, and time on each screen. Then optimize to lessen the time on each screen. We could measure the conversion rate from download -> sign up.
--
One More:
If the app has a free version, and there was a desire to convert customers to the super-duper version analyze what paths users most commonly take to get to the 'sign me up for super-duper' screen, and highlight those paths.
^-- So yeah, graph analytics would be a cool feature, especially for the UX folks.

That's actually a great idea on its own (leaving aside Helm for a sec). I also think it might be possible with Helm as we speak, but yeah, I suppose the nav graph should probs be replicated. I'll think about it, but the idea is sound in its own (I don't seen it as a Helm feature, but I'm considering exposing the required data for other third parties to use)


How to run more than one Pilosa instance on the same machine should be more obvious

How to run 2 separate (non-clustered) Pilosa instances with different ports on the same server isn't very obvious:
First server runs OK as expected:
$ ./pilosa server -b :10501 -d dir1

Running the second server fails with error running server: server.Open: opening NodeSet: Failed to start TCP listener. Err: listen tcp :14000: bind: address already in use:
$ ./pilosa server -d dir2

Currently, the workaround is setting cluster.type to static or assigning different gossip-ports work.
An easy solution would be setting cluster.type to static by default and only enable gossip if cluster/gossip related configuration is provided.

Let's hold off on addressing this until the cluster resize work in #896 is complete.

no longer relevant due to changes in clustering and config


Add timeout to the websocket connection

When the Websocket connection locks for network reasons the whole thing just locks and provides no further output than
nlopes/slack2017/12/27 09:00:54 slack.go:91: Dialing to websocket on url wss://mpmulti-8ba0.lb.slack-msgs.com/websocket/KyN3bSd_30LXwzzJptxDwSH7ueeXerZuHa0qIX9IVmQpvepYC136bNxZfrEQiLCAreT6dtohZimnvM0q6H4GvkrSb3higukMj7iLJAwi9n0J_iEkhphlNo9Y4FyoPVhQeonNOVJC5KKQm-vgVypo_ifflS5IqSX-cLk5gp7GwRc=

With this PR the logs now continues with
2017/12/27 09:01:04 Received Slack Event &slack.ConnectionErrorEvent{Attempt:18, ErrorObj:(*websocket.DialError)(0x11664200)}
nlopes/slack2017/12/27 09:01:04 slack.go:91: Failed to dial to the websocket: websocket.Dial wss://mpmulti-8ba0.lb.slack-msgs.com/websocket/KyN3bSd_30LXwzzJptxDwSH7ueeXerZuHa0qIX9IVmQpvepYC136bNxZfrEQiLCAreT6dtohZimnvM0q6H4GvkrSb3higukMj7iLJAwi9n0J_iEkhphlNo9Y4FyoPVhQeonNOVJC5KKQm-vgVypo_ifflS5IqSX-cLk5gp7GwRc=: tls: DialWithDialer timed out
nlopes/slack2017/12/27 09:01:04 slack.go:91: reconnection 19 failed: websocket.Dial wss://mpmulti-8ba0.lb.slack-msgs.com/websocket/KyN3bSd_30LXwzzJptxDwSH7ueeXerZuHa0qIX9IVmQpvepYC136bNxZfrEQiLCAreT6dtohZimnvM0q6H4GvkrSb3higukMj7iLJAwi9n0J_iEkhphlNo9Y4FyoPVhQeonNOVJC5KKQm-vgVypo_ifflS5IqSX-cLk5gp7GwRc=: tls: DialWithDialer timed out
nlopes/slack2017/12/27 09:01:04 slack.go:97:  -> reconnecting in 5m0s

Which can be useful when running things on flaky connections, as connections can simply block forever for network weather reasons.
I also added a couple of debug log lines that helped me to troubleshoot the path to reach the websocket lockup from https://github.com/nlopes/slack/issues/226

lgtm but I'd like a second opinion as not very familiar with the managed WS code.

LGTM once 10 * time.Second is fixed.

actually there is one change we should do, but doesn't have to be part of this PR.
the net.Dialer should be configurable. the timeouts will vary depending on the network.

Ok, the change is done.
@james-lawrence I agree, all those timeouts should be configurable, I didn't want to go that far as I was debugging a networking problem and just wanted to have it solved. But it should totally be configurable.
Could you point me to what is the general way to do it? There is at least another timeout defined in the WebSocket proxy file (and a keepalive). I rather not pass a lot of arguments to get it done, but to use some form of configuration object, unless there's a better way.

@pcarranza I would normally do it this way:
type RTMOption func(*RTM)

type RTMOptionWebsocketDialer(d net.Dialer) RTMOption {
   return func(rtm *RTM) {
      rtm.dialer = d
   }
}

// NewRTM returns a RTM, which provides a fully managed connection to
// Slack's websocket-based Real-Time Messaging protocol.
func (api *Client) NewRTM(option ...RTMOption) *RTM {
	return api.NewRTMWithOptions(options...)
}

// NewRTMWithOptions returns a RTM, which provides a fully managed connection to
// Slack's websocket-based Real-Time Messaging protocol.
// This also allows to configure various options available for RTM API.
func (api *Client) NewRTMWithOptions(option ...RTMOption) *RTM {
	result := &RTM{
		Client:           *api,
		IncomingEvents:   make(chan RTMEvent, 50),
		outgoingMessages: make(chan OutgoingMessage, 20),
		pings:            make(map[int]time.Time),
		isConnected:      false,
		wasIntentional:   true,
		killChannel:      make(chan bool),
		disconnected:     make(chan struct{}),
		forcePing:        make(chan bool),
		rawEvents:        make(chan json.RawMessage),
		idGen:            NewSafeID(1),
                dialer:             &net.Dialer{
			Timeout:   10 * time.Second,
			KeepAlive: 30 * time.Second,
	        	DualStack: true,
        	},
	}

        for _, opt := range options {
                opt(&r)
        }

        // ....
}

but given someone added an RTMOptions struct, you could just the dialer field to that.

added a way to do it without breaking backwards compatability with current Options methods.


Create an Admin View of Database

Talked with client about format. Wants it to be organised per student (students as first column) with sets of two columns for each question in the configuration file. These two columns are for whether the student completed the question, and the number of tries they took.

May want to split database files per-config, or look into grouping tables within the database file on a per-config basis.

Barebones. Still needs a way of clearing the database of all data, if client wants to.

Added clear data button.


Issue1338

@SpikedKira Can you please review this PR for accuracy?

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Saved content is cleared when we edit and close the attributes drop-down, such as color, brand, etc.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
Master
Issue Description
When editing select-type attributes with dropdown content, if content is already present, the saved entries are cleared automatically when we edit an option and close it.
Preconditions

Admin must be logged in.
Attributes like color, brand must have save content.

Steps to reproduce

Go to Admin -> Catalog -> Attributes -> Edit Color attribite -> Options -> Edit Red and close it.
We can see that the color content is missing.r

Expected Result
The content must not be cleared it shall be there.
Actual Result
Currently we can see that the content is missing.
Video
https://github.com/user-attachments/assets/96fc937e-c9d4-47d1-96b5-c25d356fcff1
Screenshots
No response
Additional context
No response

Checked and Found that the issue has been fixed and working fine. Now we can see that the details are not cleared and also working fine. Please check the video for reference.
Video
https://github.com/user-attachments/assets/b7d17852-a1a2-4d75-a233-fc55887abf69


Adding Git & Github tutorial to the English (screencast)

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
This screencast was performed by ShankyJS, and does a walk-through the main concepts of Git and also explains Github and the relation between Git  and Github.
Why is this valuable (or not)?
Is valuable because this is a 2 hours video with free-content about Git and Github.
How do we know it's really free?
It's a public video on youtube without ads :+1:
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[X] Not a duplicate
[X] Included author(s) if appropriate
[X] Lists are in alphabetical order
[X] Needed indications added (PDF, access notes, under construction)

Finally, all checks passed, the screencast added was done by me :raised_hands: please merge :+1:

For youtube, we prefer "playlist" links and the name of the producer/creator.

Hi @eshellman, this youtube content is a screencast of 2 hours in the same link, I have added a new commit adding the author to the name of the content.

Thanks, and welcome to free-programming-books!


Change welcome to my first app to welcome to nameOfApp

Is your feature request related to a problem? Please describe.
Inside the src/routes/index.js, the following code is created
router.get('/', (req, res) => {
  res.status(200).send({
    message: 'Welcome to my first app'
  })
})

Describe the solution you'd like
I would suggest having it created as
router.get('/', (req, res) => {
  res.status(200).send({
    message: 'Welcome to ${nameOfTheApplicationUsedToCreate}'
  })
})

Where the nameOfTheApplicationUsedToCreate is the name that the user input when doing nodejs-api-cli init
Describe alternatives you've considered
Any suggestion is welcome
Additional context
N/A

I can help with this!

Sure @leonardxfce.

Just raise a PR and I will take a look. If all is well, then I will go ahead, review and merge.

Apologies for this but it task is too difficult for me. I'll leave.

If you need any help with this, I can offer it.
There are also other tasks that are easier.
Just do let me know how I can help

Can I pick this up please?

Sure. Thanks for your contribution @README1ST


refactor: update debian script.

This PR fix script on Debian 8.

Does this handle #210 too ?

@strk No.

Just fix start/stop/reload on Debian 8 using system init.

LGTM -- I noticed it drops the redirection of stdout to /dev/null (or am I wrong?)

@strk Yes, you are right. I will fix that.

I actually like that. I mean... hiding outputs is never a good idea to me.
If it has to be directed somewhere, better direct to a logfile (which is
what the issue I linked was asking, bascially).

@strk Yes I know your point. I think we need create another PR to fix problem you reference.

@strk Missing your comment. All messages already logged on /home/git/log not /dev/null

@appleboy when I first filed that issue (in Gogs) what I was after was mostly Panic messages, which were printed to stderr I think (or stdout) and so always got lost. I proposed a PR which redirected stdout/stderr to a file but was not merged because not portable. Indeed it looks like having the caller (the Debian script, in this case) doing that redirection was one simple way to obtain what I was asking for. I don't know what the current idea is. Me I'd be ok with having everything going to stdout and then delegate redirection to the wrapper, so as I see you're touching that script I wonder... is there a standard way to deal with stdout/stderr in those scripts ? Should we adopt the same way ? Just let's make sure Panic messages are not lost though, as that's really bad when your server respond with Internal Server Error messages and you can't know what's going on.

@strk I know your point. I will take look at it and create another after this is merged. ok?

Thanks @appleboy !

Trusted LGTM


updated kecontact adapter to 2.0.1

@Sneak-L8
Please avoid issuing PRs with al lotz of outdated commits as this cause much more effort to check.
Either sync your fork befor changing stable.json or even mor comfortable use www.iobroker.dev, select you adapter and release and click at SET STABLE. You can also edit directly at the iobroker github repo which will also create a clean baranch.
Thanks in advance

Thanks for your information. Sorry, I did a sync fork before editing. Perhaps I was too quick editing in IDE before all syncs were completed.
But setting stable versions via iobroker.dev is good news. I didn't know about it. But that's awesome. I will do it that way in future releases. Great stuff!


中文snippets

在Sublime Text 3中，可以设置中文snippets，效果像附图中所示：

而在vscode中，只能设置成英文字符开头后面带中文的snippets，比如像：
“country.中国”   这样是可以的，但是如果第一个字符是中文就不行了。
盼望能实现像Sublime Text 3中那样支持中文开头的snippets

You're saying that snippets don't match with a chinese prefix? This works for me. Can you post your snippets here?

Yes, very correct, that snippets can not be prefixed with Chinese, for example, this is without any effect:
	"中国.北京": {
		"prefix": "中国.北京",
		"body": [
			"中国.北京('$1','$2')",
			"$3"
		],
		"description": "到中国北京"
	}

I see that the implementation of Sublime Text 3 is that each snippets is a file,
Then use the file name to match the user's input

The snippet works and is shown. 中 is most likely not a word character in the programming language you are using. Closing as dupe

#32201

You enter the characters "中" can appear immediately snippets?
I enter "中" and then press "Ctrl + space" key will appear snippets
If snippets is in English, there is no need to press Ctrl + space will appear immediately snippets


Unable to get image from AWS S3 bucket

I'm using the image beeyev/thumbor-s3:7.4-alpine.
Thanks for providing the example with MinIO. Thumbor works as expected with MinIO with the following configuration:
LOG_LEVEL=info

LOADER=thumbor_aws.loader
AWS_LOADER_REGION_NAME=local
AWS_LOADER_BUCKET_NAME=awesome-bucket-img
AWS_LOADER_S3_ACCESS_KEY_ID=oc
AWS_LOADER_S3_SECRET_ACCESS_KEY=changeme
AWS_LOADER_S3_ENDPOINT_URL=http://minio:9000
AWS_LOADER_ROOT_PATH=/img

RESULT_STORAGE=thumbor_aws.result_storage
AWS_RESULT_STORAGE_REGION_NAME=local
AWS_RESULT_STORAGE_BUCKET_NAME=awesome-bucket-img-cache
AWS_RESULT_STORAGE_S3_ACCESS_KEY_ID=oc
AWS_RESULT_STORAGE_S3_SECRET_ACCESS_KEY=changeme
AWS_RESULT_STORAGE_S3_ENDPOINT_URL=http://minio:9000
AWS_RESULT_STORAGE_ROOT_PATH=/img-cache

RESULT_STORAGE_STORES_UNSAFE=True
RESULT_STORAGE_EXPIRATION_SECONDS=2629746

# SECURITY_KEY=changeme
ALLOW_UNSAFE_URL=True
QUALITY=80
MAX_AGE=86400
AUTO_PNG_TO_JPG=True
HTTP_LOADER_VALIDATE_CERTS=False

I'm now trying to use two AWS S3 bucket with the following config (minus the secrets of the IAM user):
LOG_LEVEL=info

LOADER=thumbor_aws.loader
AWS_LOADER_REGION_NAME=us-east-1
AWS_LOADER_BUCKET_NAME=awesome-bucket-img
AWS_LOADER_S3_ACCESS_KEY_ID=
AWS_LOADER_S3_SECRET_ACCESS_KEY=
AWS_LOADER_S3_ENDPOINT_URL=http://awesome-bucket-img.s3-website-us-east-1.amazonaws.com
AWS_LOADER_ROOT_PATH=/img

RESULT_STORAGE=thumbor_aws.result_storage
AWS_RESULT_STORAGE_REGION_NAME=us-east-1
AWS_RESULT_STORAGE_BUCKET_NAME=awesome-bucket-img-cache
AWS_RESULT_STORAGE_S3_ACCESS_KEY_ID=
AWS_RESULT_STORAGE_S3_SECRET_ACCESS_KEY=
AWS_RESULT_STORAGE_S3_ENDPOINT_URL=http://awesome-bucket-img-cache.s3-website-us-east-1.amazonaws.com
AWS_RESULT_STORAGE_ROOT_PATH=/img-cache

RESULT_STORAGE_STORES_UNSAFE=True
RESULT_STORAGE_EXPIRATION_SECONDS=2629746

# SECURITY_KEY=changeme
ALLOW_UNSAFE_URL=True
QUALITY=80
MAX_AGE=86400
AUTO_PNG_TO_JPG=True
HTTP_LOADER_VALIDATE_CERTS=False

Here is the policy I use to allow the Thumbor IAM user to read from awesome-bucket-img and read/write to the bucket awesome-bucket-img-cache.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket",
                "s3:GetObject*"
            ],
            "Resource": [
                "arn:aws:s3:::awesome-bucket-img",
                "arn:aws:s3:::awesome-bucket-img/*",
                "arn:aws:s3:::awesome-bucket-img-cache",
                "arn:aws:s3:::awesome-bucket-img-cache/*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": "s3:*Object",
            "Resource": [
                "arn:aws:s3:::awesome-bucket-img-cache/*"
            ]
        }
    ]
}

Thumbor fails to get the image from the AWS bucket with the following error:
  File "/usr/local/lib/python3.10/site-packages/thumbor/handlers/__init__.py", line 212, in get_image
    result = await self._fetch(self.context.request.image_url)
  File "/usr/local/lib/python3.10/site-packages/thumbor/handlers/__init__.py", line 884, in _fetch
    loader_result = await self.context.modules.loader.load(
  File "/usr/local/lib/python3.10/site-packages/thumbor_aws/loader.py", line 89, in load
    status_code, body, last_modified = await client.get_data(
  File "/usr/local/lib/python3.10/site-packages/thumbor_aws/s3_client.py", line 143, in get_data
    response = await client.get_object(Bucket=bucket, Key=path)
  File "/usr/local/lib/python3.10/site-packages/aiobotocore/client.py", line 371, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred () when calling the GetObject operation:

2023-03-21 02:23:04 thumbor:ERROR [BaseHandler] get_image failed for url `triforce.png`. error: `An error occurred () when calling the GetObject operation: `
2023-03-21 02:23:04 tornado.access:ERROR 500 GET /unsafe/triforce.png (<IP_ADDRESS>) 213.96ms

For some reason the boto client does not provide details about the error (no error code or reason).
Do you have thoughts on why Thumbor can not read the image from the AWS S3 bucket?
Thanks for having created this Thumbor image!

The solution was to use the http://s3.us-east-1.amazonaws.com for AWS_LOADER_S3_ENDPOINT_URL and AWS_RESULT_STORAGE_S3_ENDPOINT_URL.


Feature Improvement_01

Description
I have observed that only some currency types are supported, I request that you please add more currency types for example, (Indian rupee - ₹ INR)
Screenshots & Videos

SaveApp Version
1.09
Android Version
14

Thank you for the report, I'll work on that

This feature will be included in the next release, which will be available in the next few days


[Backport] Upgrade netty 4 to fix CVE-2020-11612 (#9651)

Backport #9651 to 0.18.0

Clean backport


[Feature Request] Send text captions together with attachments/send multiple attachments in one message

This is a dupe of this ticket. My original caption and Tanay's response are quoted below.

This is most notable when sending an attachment as a reply in the client app together with a text caption, but the text caption does not get included in the reply.

This is already implemented but needs a server side API to actually be usable on the client. If you want, you can open an FR on server side just so zach doesn't forget.

Additionally, I was wondering if this could also apply for inserting attachments in between text parts of a message, like in this comment from an AirMessage ticket.

endpoint added


Wrong Color in Emacs Terminal Mode Running in WSL2

What happened?
Different theme color (in this case Nord) in emacs -nw running in WSL2 in Windows Terminal.
Arch WSL2:

For comparison, in native Arch:

What did you expect to happen?
Nord Theme is applied as it should be
Steps to reproduce

Install WSL2
Install ArchWSL
Install emacs and doom

System Information

Emacs version: 27.1
Emacs Distro: Doom
Operating System: Arch Linux on Windows 10 x86_64 20H2
Kernel: 5.4.72-microsoft-standard-WSL2
Terminal: Windows Terminal v1.6.10571.0
Installed commit of doom-themes: I don't really know how to check this, but as I installed doom-themes, the latest in repo is 4199e74

I think this issue is related to terminal emulator used. The WSL one used Windows Terminal. Arch used kitty. Both are running emacs -nw

Sorry for the late response. This seems like a Windows Terminal configuration issue. Unfortunately, I don't have a Windows system or environment available to me at the moment, and I know little about the WSL environment, much less the Windows Terminal, so I don't know how best to debug this. You may have better luck asking on /r/emacs or a larger community.


Correcting reference in css to 'label' instead of 'button', which was…

… wrong

Thanks, @geertjanw. Please sign the CLA before we can merge it.
I'll be updating samples and docs once NetBeans 11.1 is released.


Error information reduced when handled by the store

Instead of having
{ [Error: ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG: Dynamic SQL is not allowed in stored function or trigger]
  code: 'ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG',
  errno: 1336,
  sqlState: '0A000',
  index: 0 }

The error displays as
2015-03-25T14:33:34.395Z	83abaactibg9/1427294013981/62171/-	ERROR	plugin	mysql-store	BWK	{eraro=true,orig=,code=entity/error,seneca={code=entity/error,valmap={code=ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG,errno=1336,sqlState=0A000,index=0}},package=seneca,msg=seneca: entity/error,details={code=ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG,errno=1336,sqlState=0A000,index=0},callpoint=at error (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/mysql-store.js:109:14)}
2015-03-25T14:33:34.396Z	83abaactibg9/1427294013981/62171/-	ERROR	act	mysql-store	BWK	OUT	re8lrbbzmxs6/0u75gujj4kuq	role:entity,cmd:save	15	{cmd=save,role=entity,ent={length=74,latitude=53.134952545166,longitude=-6.0814452171326,vehicle_speed=0,vehicle_heading=197,sat_visible=144,sat_used=53,hdop=248,status_gsm=0,status_moving=0,status_heart_beat=0,status_gps=1,status_engine_state=1,status_backup_battery_failure=0,<LEN>=17},name=event,base=sys}	ENTRY	A;1zy48uf5fmg9	-	seneca: entity/error	entity/error	{code=ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG,errno=1336,sqlState=0A000,index=0,plugin={}}	Error: seneca: entity/error
    at errormaker (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca/node_modules/eraro/eraro.js:94:15)
    at Seneca.root.fail (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca/seneca.js:188:21)
    at error (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/mysql-store.js:109:14)
    at Query.<anonymous> (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/mysql-store.js:294:16)
    at Query.report [as _callback] (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/mysql-store.js:70:19)
    at Query.Sequence.end (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
    at Query.ErrorPacket (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/node_modules/mysql/lib/protocol/sequences/Query.js:93:8)
    at Protocol._parsePacket (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/node_modules/mysql/lib/protocol/Protocol.js:271:23)
    at Parser.write (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/node_modules/mysql/lib/protocol/Parser.js:77:12)
    at Protocol.write (/Users/nherment/workspace/vision-live/nodejs-payload-extractor/node_modules/seneca-mysql-store/node_modules/mysql/lib/protocol/Protocol.js:39:16)

which is cryptic and not actionable.
Same goes for errors on a specific field or a specific table.

I don't have a great answer for you, but I figured I'd share my thoughts since no one has responded to you yet..
You are right, the Error string itself is missing, the[Error: ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG: Dynamic SQL is not allowed in stored function or trigger] bit.
However, do note that the rest of the information is there:
{code=ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG,errno=1336,sqlState=0A000,index=0...}
Although not in a terribly friendly format, it is at least actionable. :)

ohh you're right, I missed that..
it's just weird and annoying formatting.
Closing this ;)

thx a lot btw !

You are very welcome! I am glad I could help =)


Updates for Phoenix 1.7

Thanks for creating this PR @jfreeze, I've had to hurriedly copy your changes into our fork as we needed them too https://github.com/getdizzie/scrivener_html. I know a few people have started forks, but nothing seems to have turned into proper hex published package – maybe we need to turn our fork into something proper that others can contribute to & use more easily.


adding vit

@nikhil1904 The first verification stage is complete: the official domain for  Vit vellore is vit.ac.in, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://chennai.vit.ac.in/files/v2-chennai-it-policy.pdf

@nikhil1904 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


README. md

Signed-off-by: Daksh Jha<EMAIL_ADDRESS>
Description

What does this PR do?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New chore (expected functionality to be implemented)

Checklist:

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[ ] I've signed off with an email address that matches the commit author.

The change is regarding documentation.


Vulkan: Glitching and laggy UI on NVIDIA + Wayland

Bugsquad note: This issue has been confirmed several times already. No need to confirm it further.

Godot version
stable 4.0 (although present in last rc)
System information
Fedora Linux 37 (Workstation Edition)
Issue description
Here's a video of me opening and closing some nodes for reference
This bug appeared in the last RC, and is still there in stable.
This glitchy effect is not just affecting node trees, but all the other "toggleable" menus and such, like directories, properties and etc.
Steps to reproduce
Not sure how to reproduce this, but here are more info about my PC which might help track it down
CPU: AMD Ryzen™ 5 4600H with Radeon™ Graphics × 12
GPU: NVIDIA GeForce GTX 1650 Ti
I'm running Wayland, with nvidia driver version being 525.89.02-1.fc37
Minimal reproduction project
Bug is not specific to a project

@Calinou Done with reproductions you mentioned:
While staying on Wayland, enabling Single Window Mode and restarting the editor still behaved the same. When I changed to Compatibility it worked fine however.
After testing it on X11, it seems there are no such glitches under any combination of these settings, so I guess you're right

I also have this on wayland but it does go away on x11. But because I really don't want to use x11 I will just use godot on windows for now

This bug appeared in the last RC, and is still there in stable.

If you can compile the engine from source, you could look into bisecting the regression to greatly speed up troubleshooting.

4.0.rc5's commit hash (good) is 0cd148313213e2923004be65bafd6a3781c917ec.
4.0.stable's commit hash (bad) is 4.0.stable.

I think I have the same issue. Selecting different entries in the node tree or almost any other UI list causes the UI to flash like in the video. Also on Fedora 37 with wayland on an NVIDIA laptop. I tried bisecting the issue and ended up way further back on b42bbca2666bb0b52156b8b396af54a1429c7077.
Does that make any sense? Reverting that commit seems to fix the flashing in the scene's node tree but doesn't do anything on other UI elements (For example the settings dialog where it still happens). However it's been difficult to test this as the issue stops occurring consistently whenever I try to reproduce it. I might've gotten something wrong

Also now that I've come around to use latest version more 4.0.2 seems to do that a lot less, definitely less noticeable than in the video (but I've updated OS version, kernel version and nvidia drivers in the meantime so maybe it had something to do with that?)

I'm still getting this in 4.0.2 really bad.
Same as OP, Single window mode doesn't help, but compatibility mode fixes it.
I'm on arch (btw) with latest nvidia drivers running hyprland compositor.
Only seems to effect the 2D UI, 3D seems to run smooth. I'll stick to Windows for the time being.

Also getting this on 4.0.2, nvidia. Single window mode did nothing.
The main issue is stuttering in most editor UI elements. The worst is code editor.
Typing code in slow-mo lmao.

I'm also getting the same input lag on nvidia + wayland (GNOME, Arch-based) on 4.0.3. X11 works fine, issue is immediately obvious on switch to wayland.

@Calinou experiencing this issue on amd gpu too, it's not just nvidia

Would be curious to know what Xwayland version is being used since it seems to work fine on regular Xorg and just fail under Xwayland.
$ Xwayland -version
The X.Org Foundation Xwayland Version 22.1.9 (12201009)
X Protocol Version 11, Revision 0
Build ID: xorg-x11-server-Xwayland 22.1.9-2.fc38

I do not see an issue if I pass --disable-vsync to the editor.  Tested with the following launch options:
bin/godot.linuxbsd.editor.x86_64 --display-driver x11 --rendering-driver vulkan --rendering-method forward_plus --disable-vsync

I believe this is https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317
If it is the case, it should react on setting XWAYLAND_NO_GLAMOR=1 in /etc/environment. Sadly, on my machine this makes all X11 applications unbearably slow (like, snail-slow - we are speaking about 3-10 fps).
The problem should disappear, or become much rarer, when Godot has native Wayland support (the race condition is still there but gets triggered much less).

This problem will also be fixed, or so I hope (and presume) when explicit sync support finally lands.

^ Brilliant news. Did notice this happening with the latest version and it was quite jarring but not unusable - Just a lengthy delay on most UI actions. Thankfully I still swap between both window sessions on KDE but look forward to this being addressed

No idea if this will help anyone while we're waiting for the native PR, but if I run in it hyprland as a floating window rather than a tiled window, and keep it under what seems to be approx 1920x1080 resolution, all of these issues go away for me. As soon as I tile it, at seemingly any size, or expand the window on one of my larger monitors it becomes slow and delayed again.

Note that Wayland support is opt-in currently, so if you didn't enable it manually, it would still be using Xwayland. If that's your case and the bug is fixed anyway, then it was fixed by another change impacting X11.

Note that Wayland support is opt-in currently, so if you didn't enable it manually, it would still be using Xwayland. If that's your case and the bug is fixed anyway, then it was fixed by another change impacting X11.

Tested both with Wayland and X11 Display Server, couldn't notice the difference in terms of this issue.
During last few releases it has been better and better, but occasionally still appears in 4.2.1 - while in 4.3 from my testing it doesn't appear to be the case. Whatever fixed it was probably one of 4.3's changes.
All in all, issue has been fixed and it's happy day for Wayland ❤

From my untrained eye, it feels like the frame order is messed up.

See https://github.com/godotengine/godot/issues/84137.

I wonder if the aforementioned PRIME detection is messing up something; perhaps selecting the iGPU with the __GLX_VENDOR_NAME makes everything panic. Also, the wiki entry you linked describes some other methods, such as also setting DRI_PRIME or running everything through prime-run (offered by nvidia-prime), which should set the relevant properties automatically. Could you try doing that?

Tried setting DRI_PRIME to 1 and using prime-run when opening up godot and experienced the same issue from earlier, the icon in the task bar appears but no window does:
{DRI_PRIME example)

Update: Nvidia stable 555 drivers appeared to have fixed many issues related to this, I still need to stay on 4.2 for jolt, but in a month or two most of these problems may be sorted out.

I'm using Nvidia v555 drivers, and while it irons out 90% of bigger problems - it's still noticeable if you look for it. That's why I got mistaken earlier.
So no, it doesn't fix it completely but it gets better!

I don't know which driver I'm on, since I just use the System Update app provided by Nobara (pretty new to Linux).
But, using "prefer Wayland" in rc2 and panning a visual shader, I feel that it's at most 15fps... it's super noticeable while not toggling the Wayland option the editor experience is smooth.

I have this exact same issue as described. I did some testing.
Using latest Arch with an AMD card and sway.

It was working fine with 4.2 and old Arch (while it was a bit laggy ?).
I have the DRI_PRIME warning, setting it does nothing.
Forcing xwayland does nothing.
Switching to compatibility renderer fixes the issue.
Switching Godot to fullscreen fixes the issue. You read that correctly.

The fullscreen part makes me think it might be related to hardware acceleration.
If you have anything to try I can run some tests.

Here is a showcase of Godot jittering (without update_continuously) so you can have a look :
https://github.com/user-attachments/assets/2aa3b9ee-c6a4-465c-a5fd-6838a74ca506
I took the time to bisect from 4.2 all the way up to 4.3.
From this commit, editor settings path changed. I navigated through ~/.config/godot/ and ran diff editor_settings-4.3.tres editor_settings-4.tres.
I noticed in 4.2 I had interface/editor/update_continuously = true, but not in 4.3.
Enabling update_continuously in 4.3 fixed the issue.
Is this expected behavior ?

Enabling update_continuously in 4.3 fixed the issue.

In my case, enabling update_continuously doesn't have any effect.
This is a fresh install of Godot 4.3.stable, and the option wasn't in the editor_settings-4.3.tres file, so I added it to the last line. I can also confirm that the issue disappears when the window is in fullscreen mode.

Arch Linux
Kernel 6.10.7
Swaywm 1.9
AMD RX 6750 XT
Mesa 24.2.1

On my laptop running Arch Linux and Hyprland on an integrated Radeon 760M, I have never experienced the issue in either fullscreen, tiled or floating mode.


RFC: Keyframes api

Static
Transforms:
const fadeIn = keyframes({
  from: { opacity: 0 },
  to: { opacity: 1 },
});

To:
export const fadeIn = {
  name: 'keyframes-a',
  keyframes: `
    from: { opacity: 0; }
    to: { opacity: 1; }
  `,
  variables: {},
};

And then consuming:
Transforms:
import { fadeIn } from './fade-in';

  hello world

To:
import { fadeIn } from './fade-in';

<>

    hello world

</>

Dynamic
Transforms:
export const fadeIn = (props) => keyframes({
  from: { opacity: 0 },
  '50%': { color: props.color },
  to: { opacity: 1 },
});

To:
export const fadeIn = (props) => ({
  name: 'keyframes-a',
  keyframes: `
    from: { opacity: 0; }
    50%: { color: var(--color-a); }
    to: { opacity: 1; }
  `,
  variables: { '--color-a': props.color },
});

And then consuming it, transforms:
import { fadeIn } from './fade-in';

const Component = props =>

  hello world

To:
import { fadeIn } from './fade-in';

const Component = props => {
  const keyFramesA = fadeIn({ color: props.color });

  return <>

      hello world

  </>
};

This is basically the mixins #17 apis - work on them in tandem

So the above kind of breaks our compile time bit because we're doing some css magic at runtime. It also makes it harder to do css extraction later - so maybe we shouldn't go down that path just yet.
I we keep the constraints we have currently:

everything done at compile time
everything baked into compiled css
we promote reuse via components - not through css atoms
dynamic properties need to be tied to a component

What would that look like for keyframes?

And then we compile the css to:
@keyframes cc-abc123 {
  from { opacity: 0 }
  to { opacity: 1 }
}

.cc-abc123 {
  animation: cc-abc123;
}

Hashing the keyframes to generate a unique name. This also means we can do dynamic keyframes tied to a component using the currently existing behaviour.

update:
we should do both words ignoring the double transform.
const fadeIn = keyframes`
  from { opacity: 0 }
  to { opacity: 1 }
`;

to
@keyframes cc-abc123 {
  from { opacity: 0 }
  to { opacity: 1 }
}
.cc-abc123 {
  animation: cc-abc123;
}


Support for flow

See https://github.com/area9innovation/flow9.
Description

[x] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3Aflow+"import+runtime"
https://github.com/search?q=extension%3Aflow+"flowutils"&type=Code

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

https://github.com/area9innovation/flow9/blob/1a3fb95a1fe0c09d71738064dd6eafda10c51af3/lib/string.flow

Sample license(s):

https://github.com/area9innovation/flow9/blob/1a3fb95a1fe0c09d71738064dd6eafda10c51af3/LICENSE.txt#L5-L6

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

pull request is still gud for the work in progress


2DSE: Replaced "Load Project" with "Restore Project"

This change hopefully makes it easier to understand what this button does compared to "Load Project".

I changed "Show Editor" to "Shape Editor" to make it even more generic.

This should truly prevent any misinterpretation of what these buttons do.


Update main_test.js

write tests for each function and use mock in MailSystem-send

[x] A clear title (name your PR "[LAB{lab_number}] {your_student_id}")
[x] A meaningful message for PR, as well as its commits
[x] From your specific branch (not main or other's branch) merging to your branch
[x] Excluding any irrelevant files, such as binaries, text files, or dot files
[x] Passing all CI (You should check it first to pass one of the validations in CI. However, you need to make sure your PR passes all CI after you submit it.)

Please read the spec carefully.


Changes with better Implementation of acro-

Once likely changes, assumptions, etc. are able to be referenced via a predefined id and are no longer manually defined, import sections 4.2, 5.1 and 6  from SWHS where applicable.

#276

This is a note to self for something slightly different.

At this point Likely Changes and most of the Assumptions have been imported. Still need to work on Requirements (implement in SWHS), Instance Models (issue #276), Data Definitions, etc.

This should be looked at for 'completion'.  I think that @halonazhao has also worked on this. And most definitely the various acro functions should NOT be used.  They were a solution idea that turned out to not be a good idea at all!

@JacquesCarette So should I remove the acro- functions from,
https://github.com/JacquesCarette/Drasil/blob/95532f9a012c8d034312beb1fdfe3cf2b88a7007/code/Data/Drasil/SentenceStructures.hs#L109-L122
https://github.com/JacquesCarette/Drasil/blob/95532f9a012c8d034312beb1fdfe3cf2b88a7007/code/Data/Drasil/Concepts/Documentation.hs#L15-L26
and if so, should I replace them with anything?

Yes - by the proper referencing system that @szymczdm has implemented. It's best if he shows you an example or two.

#987 removes all of these acro- functions - is this issue closed then? @JacquesCarette

It will be as soon as #987 is actually merged in. You should look at #360 and #742 as well once you're done this, as I think they are both 'affected'.

Actually, now that I reread the whole thing carefully, I am not 100% sure that it is all done. This seems to be about NoPCM content that might not be present, even though it is there in SWHS.

@JacquesCarette Is this an OK implementation? I have it now that NoPCM uses acronyms and SWHS uses acronymsFull
https://github.com/JacquesCarette/Drasil/blob/2b26c28212acfd861eace23938cbd7966a0cf8e8/code/drasil-example/Drasil/SWHS/Concepts.hs#L12-L18
Other that this, I think NoPCM already takes what it needs from SWHS

Yes.  And good!


Add support for mozilla-esr128 and comm-esr128 repositories. r=RyanVM

Thank you for including Thunderbird in this!

This has been deployed.


Feature/registry

📚 Documentation preview 📚: https://anemoi-utils--35.org.readthedocs.build/en/35/

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

Project coverage is 89.40%. Comparing base (ba4279f) to head (15a9591).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #35   +/-   ##
========================================
  Coverage    89.40%   89.40%
========================================
  Files            5        5
  Lines          151      151
========================================
  Hits           135      135
  Misses          16       16

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


Issues about Performance on OTB2013.

Hello! I tested SiamFC-3s-color-pretrained model on OTB2013 with your python-ported eval code. However,  the OPE AUC is about 0.5868, lower than reported 0.608 in SiamFC paper, And the tracker MEEM reachs 0.5561 while reported 0.566 in corresponding papers.   Codes for eval your tf-SiamFC: python run_trackers.py -t "SiamFC" -s cvpr13, and plot : python draw_graph.py. Is anything inconsistent with your settings? Thanks very much.

Hi,
The reported 0.608 is computed using the color+gray model. Therefore, SiamFC-3s-gray-pretrained should be used for comparison instead of SiamFC-3s-color-pretrained.
Using SiamFC-3s-gray-pretrained, the OPE AUC is 0.596. This is lower than the reported 0.608 due to platform differences (TensorFlow v.s. Matconvnet). Specifically, it is mainly caused by tf.image.crop_and_resize . This is a known issue and discussed here.
Since tracking is a sequential decision problem, it is not unusual to see small errors accumulate and the tracker starts drifting.  We observe that the tracking performance of saved models in different epochs varies considerably. In tracking, ± 0.01 happens from time to time, I wouldn't worry too much about the correctness of the implementation : )

Thank you very much.  I have acquired a lot with your code.

Glad it helps : )


Add button on forgot password form to resend email verification mails for an account

the button/link will trigger the following action:

check if the user does not have any verified email addresses
check if there are no ongoing email address verifications for the user

if both of the above checks pass:

for every non verified mail address:

if the address is ONLY registered by that user, send a verification mail

To be deployed to staging in next iteration


chore(schema): harden composer purl format

@mason-org/triage notify(Reason::NewPullRequest)
This comment ensures a notification is delivered to maintainers.
 🤖 This is an automated comment.    📖 Source code


Consistent hot/cold spot colors for local moran

This PR is to

fix inconsistent cold/hot spot colors in local moran scatterplot addressing https://github.com/pysal/splot/issues/131 and https://github.com/pysal/splot/issues/178
plot the dots for the cold/hot spots in the local moran scatterplot after the insignificant ones so that the cold/hot spots are more visible

Before:

After:

Fine with this but we should probably move these plotting functions to esda anyway.

Agreed.

nice. I actually thought this was already fixed. The other thing we need to fix is ensuring a square axis. The current implementation always elongates the Y to make it look like the slope of the regression line is 1.
+1 on the move. We should probably start a plotting branch in esda soon

The other thing we need to fix is ensuring a square axis. The current implementation always elongates the Y to make it look like the slope of the regression line is 1.

You sure about that? right now the scale of units along x and y is the same. If you enforce square axis, this would get distorted.

checkout cell 6 in the splot docs https://nbviewer.org/github/pysal/splot/blob/main/notebooks/esda_morans_viz.ipynb
that slope is supposed to be .35

the distance between 0 and 2 on y is not the same as on x.

Sorry to disagree, but it is.

The slope is wrong but the axes and the scatter are correct.
They are not the same on the subplot within plot_moran but they are the same on moran_scatterplot.
So, I believe that:

on moran_scatterplot we need to fix the visualisation of the slope.
on plot_moran we need to ensure that scale of x and y is the same (ax.set_aspect('equal')) and fix the visualisation of the slope

lol ok yes, bad example
i'm still confident there's still an issue that all the moran plots in splot and up with a slope that appears to be 1

yeah, slope is wrong on all of these

I moved the discussion on regression line to #186. I have also figured out why it is wrong.


SPARK-30010 Remove deprecated SparkConf.setAll Traversable

What changes were proposed in this pull request?
As per SPARK-30010 we need to remove deprecated SparkConf.setAll Traversable which I have done here.
Why are the changes needed?
Deprecated setAll is set to be removed
Does this PR introduce any user-facing change?
No
How was this patch tested?
By running tests locally

This is user facing, unless SparkConf is considered private
[INFO] Compiling 69 Scala sources to /Users/stevel/Projects/sparkwork/cloud-integration/cloud-examples/target/test-classes...
[ERROR] /Users/stevel/Projects/sparkwork/cloud-integration/cloud-examples/src/test/scala/com/cloudera/spark/cloud/s3/commit/S3ACommitBulkDataSuite.scala:96: type mismatch;
 found   : Traversable[(String, String)]
 required: Iterable[(String, String)]
[ERROR]     sparkConf.setAll(settings)
[ERROR]                      ^

And as the setAll[Traversable] isn't in the 2.x branch, it means that if you use the setAll methods, you cannot have code which compiles against both branches.
I think a more graceful migration might be in order, such as restoring the removed method, but having it log at warn at runtime that the method will go away.
At the very least, the change should be in the release notes.

Right, both are in 3.0.x, but the old one is in 2.x only, and the new one is in 3.1.x only. You can work vs 2.x and 3.0.x simultaneously right now
I'm not against adding the new method to 2.x as well, as 2.13 compatibility is not a concern there, and I think it's not ambiguous?
It's not in release notes as 3.1.x isn't released yet, but I'll mark it for 3.1.x release notes.

I've just pulled it out and done the iteration myself, so it's not holding me up. It's just that it could stop linking.
+1 for the release notes
up to you about the 2.x backport. It might help others


nixos/bluetooth: add option for experimental settings

Description of changes
bluetoothd uses the flag -E or --experimental to enable experimental interfaces.
Unknown:

Does this require a package built with experimental flags? (bluez5-experimental)
If so, should we change the default package if this configuration option is true?

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Thank you for your change, apologies for the delay.

Description of changes
bluetoothd uses the flag -E or --experimental to enable experimental interfaces.
Unknown:

Does this require a package built with experimental flags? (bluez5-experimental)

Probably.

If so, should we change the default package if this configuration option is true?

If so, yes.


Update flat to new g+ logo

Thanks for the pull request! Could you show me a screenshot?

I'd love to, just not sure how to compile it 😭

Have you tried this? https://github.com/sapegin/social-likes/blob/master/Contributing.md#building-and-running-tests
And then open specs/specs.html.


Cherry-pick PRs from main to release/5.9

This cherry-picks the following PRs to release/5.9, effectively bringing release/5.9 up-to-date with main

https://github.com/apple/swift-syntax/pull/1462

Only modifies a test utility that is not part of the toolchain, so very low risk and useful to trace performance problems

https://github.com/apple/swift-syntax/pull/1436

This fixes minor parsing bugs found by #1339, so we should take it into 5.9

https://github.com/apple/swift-syntax/pull/1456

Fixes a known bug that we previously allows = with unbalanced whitespace

https://github.com/apple/swift-syntax/pull/1457

Cleanup with a slight performance boost that is needed for regex lexing

https://github.com/apple/swift-syntax/pull/1440

Generally improves our structure to represent versions in the SwiftSyntax tree. I wouldn’t want to ship 5.9 with the old representation where a float was used to represent the major and minor version. Also fixes a parser bug where we would expect arbitrary float literals (like 1.0e2 for the major version) and hex integer literals for the patch version

https://github.com/apple/swift-syntax/pull/1442

Needed for macros AFAICT

https://github.com/apple/swift-syntax/pull/1445

Low risk, improves diagnostics

https://github.com/apple/swift-syntax/pull/1422

Fixes an issue that we had the wrong code-generated files checked in

https://github.com/apple/swift-syntax/pull/1444

Low risk, improves diagnostics

https://github.com/apple/swift-syntax/pull/1441

Improves what will be highlighted in a diagnostic from a single character to an entire token. Dramatically improves how the highlight looks IMO.

https://github.com/apple/swift-syntax/pull/1380

We weren’t diagnosing editor placeholders as error. That was bad. This fixes it.

https://github.com/apple/swift-syntax/pull/1429

Low risk, improve diagnostics

https://github.com/apple/swift-syntax/pull/1435

Fixes a build-time warning about a non-excluded CMakeLists.txt. Super-low risk

https://github.com/apple/swift-syntax/pull/1339

All the code added by this is behind #if and makes cherry-picking a lot easier because this touches a lot. Thus, low risk

https://github.com/apple/swift-syntax/pull/1427

If we are not willing to enable these assertions (or after this PR preconditions) now, I think we will never have the guts to do so. So let’s get it in now while we still have time until the real release.

https://github.com/apple/swift-syntax/pull/1432

Similar to above, we should enable these assertions for 5.9. Also this is lower risk because it only affects Release+Assert builds, not plain release builds.

@swift-ci Please test

To the editor placeholder we also need to cherry pick in the swift repo. If that also have a 5.9 branch

https://github.com/apple/swift/pull/64805
@swift-ci Please test

To the editor placeholder we also need to cherry pick in the swift repo. If that also have a 5.9 branch

Thanks for keeping track of things. I forgot about that. I opened https://github.com/apple/swift/pull/64805.

https://github.com/apple/swift/pull/64805
@swift-ci Please test macOS


Add basic benchmark for consensus adding blocks

My worries:

Adding a block does not actually seem to be constant time. For now the go benchmark doesn't seem to notice since this doesn't show until you have many more blocks.

The testing benchmark records memory usage, but doesn't seem to have any way of outputting it easily, so I manully ran the benchmark and made it a test function. (running with go test ./modules/consensus/ -run=Bench -v -tags='debug testing')

This also measures the memory allocations for the initial startup, which is probably a significant portion of the memory usage. We should be able to make use of the information regardless though.

if you have debugging enabled, adding a block is going to be linear time in the size of the consensus set, I believe. This happens because we hash the whole consensus set every block.
I guess we need a better way to toggle the debugging intensity, this isn't the only place where it's bad.

So I'll leave this PR out there for a bit, but as it is a PR into an old branch it needs to be remade to pull into master. I do think there is some value in having such a benchmark specifically for consensus that does not wait for all the other modules to update, but a similar more comprehensive benchmark will also be useful.

If you want a benchmark that targets just the consensus package, you're going to need to use a consensus module that has no subscribers (no miner, wallet, etc.), which means you are going to need to manually make all of the blocks.
The miner has a function SolveBlock that will take any block and solve it for a given target, it's completely possible to make that benchmark (just have the miner subscribed to a different consensus set), but it's a lot of manual coding.

Is this PR into the right branch? You probably want to merge it with master.


Bug: Parsing error: Cannot set property index of Error which has only a getter

Before You File a Bug Report Please Confirm You Have Done The Following...

[X] I'm using eslint-plugin-vue.
[X] I'm sure the problem is a parser problem. (If you are not sure, search for the issue in eslint-plugin-vue repo and open the issue in eslint-plugin-vue repo if there is no solution.
[X] I have tried restarting my IDE and the issue persists.
[X] I have updated to the latest version of the packages.

What version of ESLint are you using?
latest
What version of eslint-plugin-vue and  vue-eslint-parser are you using?

vue-eslint-parser@latest
eslint-plugin-vue@latest

What did you do?

Configuration
ESLint Config
module.exports = {
  extends: [
    // add more generic rulesets here, such as:
    'eslint:recommended',
  ],
  parser: 'vue-eslint-parser',
  parserOptions: {
    parser: '@typescript-eslint/parser',
    ecmaVersion: 6,
    extraFileExtensions: ['.vue'],
    ecmaFeatures: {
      jsx: true,
    },
    project: true, // will work if disable this line
  },
  plugins: ['@typescript-eslint'],
}

tsconfig
{
  "compilerOptions": {
    "baseUrl": ".",
    "target": "es6",
    "module": "esnext",
    "moduleResolution": "node",
    "strict": true,
    "jsx": "preserve",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "skipLibCheck": true,
    "lib": ["esnext", "dom"],
  },
  "include": [
    "."
  ],
  "exclude": ["node_modules"]
}

App
<template>

1

</template>

What did you expect to happen?

What actually happened?

Link to Minimal Reproducible Example
https://github.com/zWingz/test-vue-eslint
Additional comments
enable or disable the project: true

https://github.com/typescript-eslint/typescript-eslint/issues/7597

me too ,how to do

Downgrading to v9.2.1 removes the bug but misses out on important things like the integration with generic Vue 3.3 components.
npm i -D<EMAIL_ADDRESS>

Downgrading to v9.2.1 removes the bug but misses out on important things like the integration with generic Vue 3.3 components.
npm i -D<EMAIL_ADDRESS>

still no work

Downgrading to v9.2.1 removes the bug but misses out on important things like the integration with generic Vue 3.3 components.
npm i -D<EMAIL_ADDRESS>

still no work

Same here (Windows 10, pnpm<EMAIL_ADDRESS><EMAIL_ADDRESS>


stoped support, firefox 66.03

Version
5.1.0
Browser and OS info
firefox 66.03
Steps to reproduce
update firefox to ^66.03
What is expected?
normal use
What is actually happening?
stoped support

I have this problem

me too :( and also, i cannot download vuejs webtools from mozillas addons, see screenshot.
same firefox version (on macOS Mojave 10.14.4).

As now, signing add-ons is required as per
https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct#w_what-can-i-do-if-firefox-disables-an-installed-add-on
Workaround in the meantime. Use Firefox Developer Edition and set
extensions.langpacks.signatures.required to false

Same problem, workaround didn't works for me.

It's an upstream issue in Firefox itself:
https://twitter.com/mozamo/status/1124484255159971840
A hotfix should be available to you soon:
https://twitter.com/mozamo/status/1124627930301255680

thanks very much, now it works, I will close this issue.


Request for documentation

I an trying to upgrade Unity in an existing project (from 3.0.1304.1 to 5.11.1). Version 3.0.1304.1 is quite old, so I encounter some issues. I've looked at the change log and other documentation, but cannot port my code.
I have code that accomplishes two things:

Use a ContainerControlledLifetimeManager for all classes deriving from some base class X, without specifying that for every class derived from X.
Use the default constructor when resolving for all classes deriving from base class Y, without specifying that for every class derived from Y.

It utilizes a LifetimeManagerFactory that is no longer available, and I don't know what to replace it with.
And should I derive IOCConstructorSelectorPolicy from ISelect now and should IOCConstructorSelectorPolicy.SelectConstructor then be replaced by Select (as per the ISelect interface) and how do I implement this Select function?
Could you give me some pointers, and perhaps this can be used to enhance the current documentation?
    /// <summary>
    /// This class merely exists for readability: avoid having to write the class it derives from.
    /// </summary>
    public class IOCConfigLifetimeExtension : DefaultLifetimeManagerExtension<ContainerControlledLifetimeManager, X>
    {}

    /// <summary>
    /// An IOC strategy to use a specific LifetimeManager (<typeparamref name="TLifetimeManager"/>) for subclasses of <typeparamref name="TBaseClass"/>.
    /// </summary>
    public class DefaultLifetimeManagerExtension<TLifetimeManager, TBaseClass> : UnityContainerExtension where TLifetimeManager : LifetimeManager, new()
    {
        protected override void Initialize()
        {
            var theFactory = new LifetimeManagerFactory(Context, typeof(TLifetimeManager));
            Context.Strategies.Add(new DefaultLifetimeManagerStrategy(theFactory, TypePredicate), UnityBuildStage.TypeMapping);
        }

         private bool TypePredicate(Type type)
         {
             return typeof (TBaseClass).IsAssignableFrom(type);
         }
    }

    public class DefaultLifetimeManagerStrategy : BuilderStrategy
    {
        public DefaultLifetimeManagerStrategy(LifetimeManagerFactory factory, Predicate<Type> typePredicate)
        {
            mFactory = factory;
            mTypePredicate = typePredicate;
        }

        public override void PreBuildUp(IBuilderContext context)
        {
            if (context.Existing == null) {
                var theLifetime = context.Policies.GetNoDefault<ILifetimePolicy>(context.BuildKey, false);

                if (theLifetime == null && mTypePredicate(context.BuildKey.Type)) {
                    theLifetime = mFactory.CreateLifetimePolicy();
                    context.PersistentPolicies.Set(theLifetime, context.BuildKey);
                }
            }
        }
        private readonly LifetimeManagerFactory mFactory;
        private readonly Predicate<Type> mTypePredicate;
    }

    /// <summary>
    /// A Unity extension that prioritizes the default constructor for classes derived of Y when available, otherwise the default resolve method is used.
    /// </summary>
    public class IOCExtension : UnityContainerExtension
    {
        protected override void Initialize()
        {
            var theDefaultConstructorSelectorPolicy = Context.Policies.Get<IConstructorSelectorPolicy>(null);
            Context.Policies.SetDefault<IConstructorSelectorPolicy>(new IOCConstructorSelectorPolicy(theDefaultConstructorSelectorPolicy));
        }

        public class IOCConstructorSelectorPolicy : IConstructorSelectorPolicy
        {
            public IOCConstructorSelectorPolicy(IConstructorSelectorPolicy defaultConstructorSelectorPolicy)
            {
                mDefaultConstructorSelectorPolicy = defaultConstructorSelectorPolicy;
            }

            public SelectedConstructor SelectConstructor(IBuilderContext context, IPolicyList resolverPolicyDestination)
            {
                Type theType = context.BuildKey.Type;
                if (typeof(DataNode).IsAssignableFrom(theType)) {
                    ConstructorInfo theDefaultConstructorInfo = theType.GetConstructor(Type.EmptyTypes);
                    if (theDefaultConstructorInfo != null && theDefaultConstructorInfo.IsPublic) {
                        return new SelectedConstructor(theDefaultConstructorInfo);
                    }
                }
                return mDefaultConstructorSelectorPolicy.SelectConstructor(context, resolverPolicyDestination);
            }

            private readonly IConstructorSelectorPolicy mDefaultConstructorSelectorPolicy;
        }
    }

I have the same problem, how to upgrade?

This is an interesting problem. I do not have a suggestion at the moment. Perhaps if you could give me a scenario where this should be useful I could give you better answer?


Clarify documentation on configuration settings

It is not entirely clear from the documentation (neither the README or developer.algorand.org) what the right combination of settings between go-algorand and algorand-indexer are. Specifically, when using algorand-indexer with go-algorand in archival mode is it really necessary to have isIndexerActive set to true? Is it redundant? Is it for backward-compatibility with v1? If we remove it would we support v2 exclusively or would the v2 indexer API endpoints also break? If both algorand-indexer and isIndexerActive are set are we supporting both v1 and v2 and wasting disk space unnecessarily? Some small elaboration on these points would be very helpful.

Yeah, the old algod config.json "IsIndexerActive" filed is obsoleted by the standalone algorand-indexer and if your deployment isn't using the 2 APIs on algod that use the old indexer features in it, "IsIndexerActive" should be false

Hey @ejbaran would you be able to help with this documentation issue?

The documentation is here:
https://developer.algorand.org/docs/run-a-node/setup/indexer/
You can think of Indexer v1 and Indexer v2 as separate features. The documentation treats the installation that way as well which is why it doesn't mention setting isIndexerActive for the v2 setup.
You are correct with your questions. V1 is still around for backwards compatibility, you don't need to turn it on. If you had it on before, I don't think turning it off will free up the disk space.


an issue with setting environment

Hello.
Have you encountered problems with installation of diff-gaussian-raterization?
I tried manually to install all packages, but only pip install submodules/diff-gaussian-rasterization  did not work.
If you solved this problem, or know how to solve it, please explain.
Thank you

Generally, "conda env create --file environment.yml" will help you to install diff-gaussian-raterization.
Otherwise, "cd submodules/diff-gaussian-rasterization & pip install -e ." may help.

Generally, "conda env create --file environment.yml" will help you to install diff-gaussian-raterization. Otherwise, "cd submodules/diff-gaussian-rasterization & pip install -e ." may help.

i did as you mentioned, also i downloaded again by git clone --recurse-submodules https://github.com/USTC3DV/FlashAvatar-code.git, then git checkout main, but neither your instruction, nor  conda env create --file environment.yml worked out.
Also i downloaded from git clone https://github.com/graphdeco-inria/diff-gaussian-rasterization.git and again pip install -e . did not work.
Do you have any idea, how to resolve this issue?

Well, sorry to say that I have no idea. Maybe you should try to install the environment of original 3DGS first to find some clues.
(One possible reason: diff-gaussian-rasterization has its own submodule which should be git-clonned if you install all packages manually.)

@xiangjun-xj I do not know what to do either... At least thank you for your responses so much!
Could you share your cuda version?

@xiangjun-xj I do not know what to do either... At least thank you for your responses so much!
Could you share your cuda version?

11.7


Feature: Highlight regex capture groups in terminal output

My favorite feature of behave, a Python port of cucumber, is the capture group highlighting. This is helpful for two reasons:

It helps validate complex regexes during step development
It informs someone viewing the output which portion of the step is dynamic and could be modified

When validating how easy this would be to add, I found that the current implementation of using Examples: sections actually didn't do what the user would expect, so has been removed until it does.
It didn't actually handle the variables in the tests, so it effectively didn't do anything but print skipped for them all.

@brycefisher I'm currently reviewing the output of this tool, so if you had some screenshots of this behaviour it would be helpful for me. :smile:

Hi @bbqsrc ! Sorry for the delay. Do you mean the python package behave? I can gladly show some screenshots if so

yeah, please do :)

I can toss in one, right of my dev station

As you can see the parts in lighter shade of green are regexp captures

Aha! This would require some changes to some events but not inconceivable.

It's pretty useful when debugging with command line, less when you use integrated tools (but that's a separate ticket, as I want tests from here to work in clion damn it! :D)

Resolved in #136. Now captures are higlighted with a bold style.


works better on different screen sizes

Allows the snake app to be more easily played on different screen sizes and should prevent errors on screen sizes smaller than 128x64.

Thank you!


Add testing

I am not very experienced with testing and would like to familiarise myself with the node.js test runner (which has been built in since version 20). The tests can certainly be improved, but they are a start and better than no tests at all :slightly_smiling_face:

Thank you guys.


Optional parameters for serializer

Hi,
I'm in a position where I need to pass additional parameters to the serializer. I pull a collection of locations, and for each item, I need to show the distance from that requests IP to the Location object. The problem is the only way I can see to do this is something like:
locations.each do |location|
    location.source_coords = [lat, lng]
end
locations

The problem is that it's not the Location objects responsibility to deal with this, it's more the responsibility of the serializer. How can I pass the param to the serializer?
Thanks

+1

Don't know from the top of my head, but we should figure this one out.

grape-active_model_serializers depends on active_model_serializers.  Shouldn't this be something that active_model_serializers should worry about?

+1

This is a super old thread, so I'm going to close this now.
Though it might not be exactly what you were looking for, ASM supports this type of conditional rendering of serialized data via the fields functionality: https://github.com/rails-api/active_model_serializers/blob/master/docs/general/fields.md


Export data from Volcano Plot

After creating a Volcano Plot on mzmine 4.1.0 from a feature list, when exporting the data to Excel, we get a table with the columns log2(fold change) and -log10(p-Value) but not associated with the feature ID, mass or retention time. This association would be useful.
The information exists since we can already click on each point of the volcano blot to obtain the bloxplot with the corresponding feature ID.
So my question is: would it be possible when exporting to add information on the feature ID at a minimum, or even the m/z and RT?

Good idea, will add the feature id as a z-axis, so it's in the exported data, which will also include the tooltip.


[Feat]: Add API Endpoint for  Project Admin to Delete Testimonials

Is your feature request related to a problem? Please describe.
There is currently no API endpoint available to delete testimonials from the database. This feature is essential for maintaining the integrity of the website's content and ensuring that outdated or irrelevant testimonials can be removed when necessary.
Describe the solution you'd like.
Create a new API endpoint in the backend that allows authenticated admins to delete testimonials by their unique identifier (ID) from the database.

A new API endpoint should be created in the backend with an appropriate URL and HTTP method (e.g., DELETE /api/testimonials/:id).
The endpoint should require authentication to ensure that only admins can access it.
When a DELETE request is made to the endpoint with a valid testimonial ID, the corresponding testimonial should be deleted from the database.
The backend should handle any potential errors gracefully and return appropriate error responses.
The frontend should be updated to include a user interface (UI) element or button that allows admins to initiate the deletion process for a specific testimonial.
The deletion process should be confirmed with a confirmation dialog or prompt to prevent accidental deletions.
After successful deletion, the frontend should provide feedback to the admin, indicating that the testimonial was successfully deleted.
Proper testing should be conducted to ensure the new API endpoint functions as expected and that testimonials are correctly deleted from the database.

Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response

@AnirudhPanda ,please review and merge my pull request.

@AnirudhPanda ,can you guide me to work on any other issues like searchbar or anything else ?