Move managing OIDC elsticsearch user configmap and secret from operator

Description
Move managing of OIDC Elsticsearch users ConfigMap and Secret from operator to kube-controller.
ConfigMap tigera-known-oidc-users and Secret tigera-oidc-users-elasticsearch-credentials, needs to updated by few other internal components and doesn't fit well into tigera-operator design.

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

@Suraiya-Hameed Why is this change needed ?

What uses the ConfigMap and Secret? I'm wondering if we need an annotation on a pod so that when they change/update the pod gets restarted to pick up those changes.
Should the operator continue to watch these resources and block logstorage if they don't exist?

Do the ILM changes need to be in this PR? It seems like the changes are not related and it would be easier to review if they were separate.
If it is necessary they are in this PR could you explain why since I didn't understand.

@tmjd That is partially my fault. I saw some inefficiencies with locking and suggested to clean that up. That led to the refactoring.

What uses the ConfigMap and Secret? I'm wondering if we need an annotation on a pod so that when they change/update the pod gets restarted to pick up those changes.

This ConfigMap and Secret are managed by kube-controller, it watches and re-creates it as needed, and es-proxy writes into the ConfigMap and reads from Secret. We are already passing the Elasticsearch license type to kube-controller, and the kube-controller creates/deletes this ConfigMap and Secret based on that environment value.

Should the operator continue to watch these resources and block logstorage if they don't exist?

That's a good idea, consequence of not having this ConfigMap and Secret is that SSO-like functionality will not work when moving from ManagerUI to Kibana. It does make sense to block logstorage till they are available.

Do the ILM changes need to be in this PR? It seems like the changes are not related and it would be easier to review if they were separate.
If it is necessary they are in this PR could you explain why since I didn't understand.

The changes to elasticsearch file can be a separate PR, it is mostly refactoring and has a fix to handle scenario where Elasticsearch password changes in the background.

/merge-when-ready

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.


readme: add codecov badge

This pull request adds the following badge showing the coverage status on the README file:

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

Project coverage is 81.51%. Comparing base (3fcc128) to head (d0df8cf).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #145   +/-   ##
=======================================
  Coverage   81.50%   81.51%
=======================================
  Files          11       11
  Lines        1060     1082   +22
=======================================
+ Hits          864      882   +18
- Misses        126      128    +2
- Partials       70       72    +2

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


Propose fix a typo

Does this help?

Thanks!

Coverage remained the same at 100.0% when pulling f32291c2a51fa702d8e15a4b49e8c330e0608914 on jeis2497052:master into fef4102e518110f13716fa065ad351a3b75295df on google:master.


Tt

Description

Why

Possible Implementation & Open Questions

Is this something you're interested in working on?

[ ] YES
[ ] NO

@PALAVALASA-SAIKUMAR Hi, please don't spam Open Source repositories with fake issues.
It's a really annoying practice. If you want to test how issues work, you can do so on one of your personal repos.
The first rule of Open Source or any development is to "keep the place cleaner than how you found it", not to litter it.
Thank you.
Developers usually look at issue to see how stable is the repository and to see if there is something to improve.
Please close your issue if it's not relevant, because maintainers shouldn't have to deal with this type of stuff.


Adding support in System for hl

While I was going through System, I noticed that you couldn't check the totalMemory, so I was searching and I found out that it is totally possible to check the memory, (I'm not sure about gc, but it seems like the same)

Thanks for your PR. I've made a similar PR one year ago here https://github.com/openfl/openfl/pull/2491.
But yours seems more complete because you have added gc call, I haven't tested though.
Why to chose untyped instead of int for memory?

Why to chose untyped instead of int for memory?

I was just following what the majority had, which was untyped.
But I think it would be better to remove that since hl.Gc seems to be pretty close to neko?


Loop attribute not working

var homeLoopAudio = new Pizzicato.Sound({
source: 'file',
loop: true,
options: {
path: audiosHome[randomVariable],
volume: 0.1
}
}, function() {
homeLoopAudio.play();
});
The loop is not working, and i don't know why. Anyone with the same problem?

The loop option should be inside the options object:
var toto = new Pz.Sound({
  source: 'file',
  options: {
    path: 'some-audio-file.mp3',
    loop: true
  }
}

More info here: https://github.com/alemangui/pizzicato#sounds-from-a-file-example


Version of matplotlib specified in poetry.lock is yanked

Running poetry install gives the following warning:
Warning: The file chosen for install of matplotlib 3.9.1 (matplotlib-3.9.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl) is yanked. Reason for being yanked: The Windows wheels, under some conditions, caused segfaults in unrelated user code.  Due to this we deleted the Windows wheels to prevent these segfaults, however this caused greater disruption as pip then began to try (and fail) to build 3.9.1 from the sdist on Windows which impacted far more users.  Yanking the whole release is the only tool available to eliminate these failures without changes to on the user side.  The sdist, OSX wheel, and manylinux wheels are all functional and there are no critical bugs in the release.   Downstream packagers should not yank their builds of Matplotlib 3.9.1.  See https://github.com/matplotlib/matplotlib/issues/28551 for details.

Sounds like this is only going to cause issues on Windows, but using a more recent version would get rid of the warning.

version 3.9.3 is used now after https://github.com/CQCL/pytket-docs/pull/410
See the updated lock file https://github.com/CQCL/pytket-docs/blob/main/poetry.lock#L2233
I'm closing this for now. If I missed something feel free to reopen.


Cannot connect to the Docker daemon at ... Is the docker daemon running? [ee4 beta2]

With Ubuntu 18.04 OpenVZ virtualization I got this error when intalling ee4 beta2
Downloading our Docker images. This might take a while...
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Run "ee help site" for more information on how to create a site.

After command:

ee site create eates.tk --wpredis
Warning: This is a beta version. Please don't use it in production.

I got:
Error: docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

@jasomdotnet I have never used OpenVZ. According to what I could find on the StackOverflow - https://stackoverflow.com/a/35951482/4108721,

Docker requires two features of Linux kernel in order to operate: control groups and namespaces. So you need a kernel with these features.

So can you check which version of OpenVZ are you using and does that version of OpenVZ support Docker?

With command
uname -a
I found this
Linux **** 3.16.6-042stab131.42 #1 SMP Tue Jun 26 21:15:19 CEST 2018 x86_64 x86_64 x86_64 GNU/Linux

Can you share the output of

ls /proc/self/ns
grep 'CONFIG_USER_NS' /boot/config-$(uname -r)
cat /proc/cgroups

Closing this issue for now as it has not received a response yet. If you're still facing this problem, feel free to create a new issue.


ChefDK 1.2.22 / 1.3.6 appbundle and postinst-symlinked binaries mismatch

Description
Align https://github.com/chef/chef-dk/blob/v1.2.22/omnibus/config/software/chef-dk-appbundle.rb#L15-L26 and https://github.com/chef/chef-dk/blob/v1.2.22/omnibus/package-scripts/chefdk/postinst#L39:

/usr/local/bin/chef-zero symlink should be replaced with chef-vault one
/usr/local/bin/dco symlink missing by design?
/usr/local/bin/fauxhai symlink should be removed
/usr/local/bin/print_execution_environment symlink missing by design?

ChefDK Version
1.2.22
Platform Version
macOS Sierra 10.12.3
Replication Case
Via https://packages.chef.io/files/stable/chefdk/1.2.22/mac_os_x/10.12/chefdk-1.2.22-1.dmg or brew cask install chefdk (https://github.com/caskroom/homebrew-cask/blob/master/Casks/chefdk.rb):
$ find /usr/local/bin -lname '/opt/chefdk/*'
/usr/local/bin/berks
/usr/local/bin/chef
/usr/local/bin/chef-apply
/usr/local/bin/chef-client
/usr/local/bin/chef-shell
/usr/local/bin/chef-solo
/usr/local/bin/chef-zero
/usr/local/bin/cookstyle
/usr/local/bin/delivery
/usr/local/bin/fauxhai
/usr/local/bin/foodcritic
/usr/local/bin/inspec
/usr/local/bin/kitchen
/usr/local/bin/knife
/usr/local/bin/ohai
/usr/local/bin/push-apply
/usr/local/bin/pushy-client
/usr/local/bin/pushy-service-manager
/usr/local/bin/rubocop

vs.
$ find /opt/chefdk/bin/*
/opt/chefdk/bin/berks
/opt/chefdk/bin/chef
/opt/chefdk/bin/chef-apply
/opt/chefdk/bin/chef-client
/opt/chefdk/bin/chef-shell
/opt/chefdk/bin/chef-solo
/opt/chefdk/bin/chef-vault
/opt/chefdk/bin/cookstyle
/opt/chefdk/bin/dco
/opt/chefdk/bin/delivery
/opt/chefdk/bin/foodcritic
/opt/chefdk/bin/inspec
/opt/chefdk/bin/kitchen
/opt/chefdk/bin/knife
/opt/chefdk/bin/ohai
/opt/chefdk/bin/print_execution_environment
/opt/chefdk/bin/push-apply
/opt/chefdk/bin/pushy-client
/opt/chefdk/bin/pushy-service-manager
/opt/chefdk/bin/rubocop

applies to 1.3.6 as well: https://github.com/chef/chef-dk/blob/v1.3.6/omnibus/package-scripts/chefdk/postinst#L39


feat: implement station production view backend

Overview
Contains all changes required in the backend to use a station viwe. A station view tells the people working at that station what they need to produce. They can also mark the ingredients as produced at the assembly station.
Closes KAN-127
Closes kan-127
Related Jira Story
Link to the Jira Story and any relevant Sub-Tasks that are addressed by this pull request.
https://simonsays-zhaw.atlassian.net/browse/KAN-34?atlOrigin=eyJpIjoiMTczMjgxZjYwMmM1NGU2MDk3Mzk1YzNhZjE3NzNmZDUiLCJwIjoiaiJ9
Backend Changes

Implemented Station View
Updated Ingredients to fulfil all requirements (can be marked as no need to produce)

Definition of Done

[x] The feature must be fully tested and all specified requirements being met as outlined in the feature description.
[x] Unit and integrations test must be written for any business logic.
[x] Sufficient negative tests must be included to assess the robustness and error handling capabilities of the code.
[x] The pull request must be reviewed and approved by at least one codeowner of the modified files.
[x] All pipelines on the pull request succeed.
[x] Refactoring on the code has taken place.

Additional Notes
This Pull Requests only contains backend changes. As backend and frontend currently works a bit out of sync.

Please review the above changes. Upon approval, please squash the commits following the guidelines before merging to the main branch.

Closed due to issues with the frontend tests.


Feature/discourse comments

This re-opens @breezyfasano's original PR #1069
Preview
https://deploy-preview-2218--docs-getdbt-com.netlify.app/blog/how-to-build-a-mature-dbt-project-from-scratch
Original description:
Description & motivation
Adding comments to the dev blog via Discourse embeds
How to Review:

Preview link: click on any blog post!
Below each post content, there should be an embed that says 'start discussion'! That's the discourse embed. Let me know if you all can see it

A note about Discourse's embed functionality from the Discourse docs:

One important thing to note with this setup is that users have to navigate to your forum to post replies. This is intentional, as we feel that the posting interface on a Discourse forum is currently much richer than what we could embed via Javascript.

Edit 4:08pm CT:
Here are the comments in action! this does create a discourse topic, but I just commented to test the system works as planned and then deleted the topic it made. Screenshots below.
On the Website

On Discourse Topic

@JKarlavige looks like the iframe is too smol somtimes https://www.loom.com/share/bf2c2d7dd0274c2f98feb58e7f5a8124

@JKarlavige looks like the iframe is too smol somtimes https://www.loom.com/share/bf2c2d7dd0274c2f98feb58e7f5a8124

Yeah seeing that on my end as well, looks to only occur in Chrome. TBH, i'm not crazy about this iframe, there's a couple of other things i'm noticing.

It won't adapt to dark mode, so we'll have a white box at the bottom.
In Firefox, there's no padding, so it looks pretty bad in dark mode.
The "1 Reply" button doesn't seem to work for me.

The script is generating the height of the iframe, so i'm not sure how we can work around that. We might be able to set a predefined height, but would have to setup vertical scrolling.
What are your thoughts on holding off on this, and building it out with the API in the same way we did with the DiscourseFeed component? Obviously that would push us back to after Coalesce though.

I think that's the right call - thanks @JKarlavige. Twas worth a shot

I think that's the right call - thanks @JKarlavige. Twas worth a shot

Yeah definitely worth trying it out. Posted an update in the Asana task for us to circle back to this and build it out in a similar way to the DiscourseFeed component.


Update bottom_sheet.xml

I guess this solves #9

Nice catch.
I merged it into the dev branch for a future release (03a4dc4ff3b4fef69e27b6e88d1f490f00d4075e).


Issue on saving the output

Hello,
After selecting 1000 json files the choose files button still shows the number of json files selected. But there is no way to download the output. Can you please address this issue?
Thanks.

Hi 👋🏻
The download is supposed to be automatic after selecting the files.
If the files are very large I imagine it may take a little time (the processing time) before the download takes place.
I tried to reproduce your problem with at least 1000 files and I did not encounter any problems, however my files do not contain a lot of data.
Are you still having the problem ?

@theMIK27 Did you read my previous message ?
Can you detail your manipulation and / or do you still encounter the problem ?

Hey,
Sorry for the late reply. I did try, but the total volume of that 1000 files is a little more than 80 GB, and it takes a whole lot of time. I waited around 20-25 minutes but never got the output.
Thanks.


WIP: fix: restore missing exports declarations

Closes: https://github.com/TanStack/query/issues/3882

Codecov Report

Merging #3892 (812bdc6) into main (eab6e2c) will increase coverage by 0.41%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3892      +/-   ##
==========================================
+ Coverage   96.36%   96.77%   +0.41%
==========================================
  Files          45       57      +12
  Lines        2281     2668     +387
  Branches      640      784     +144
==========================================
+ Hits         2198     2582     +384
- Misses         80       84       +4
+ Partials        3        2       -1

Impacted Files
Coverage Δ

src/core/queryCache.ts

src/react/reactBatchedUpdates.ts

src/react/QueryClientProvider.tsx

src/core/focusManager.ts

src/core/mutation.ts

src/devtools/Explorer.tsx

src/react/useBaseQuery.ts

src/react/logger.native.ts

src/react/useInfiniteQuery.ts

src/devtools/tests/utils.tsx

... and 92 more

Continue to review full report at Codecov.

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

Thanks. Are you sure that this is all we need? According to @sachinraja, there is more work to be done to be fully ESM compliant - e.g. to use the .mjs extension. That's why I've created this issue:

https://github.com/TanStack/query/issues/3882

We've also had some problems with useSyncExternalStore and react-native, so I'd rather not rush this issue. Also not sure how we can properly test this with various bundlers before we release 🤔
I would also really like to get the feature back that allowed us to import the devtools in production via a separate entry point

@TkDodo Yup, marked as WIP for now as there are still more things to be moved/refactored.

@TkDodo @tannerlinsley So most of the things are covered by this PR to restore EMS compliant exports.
The only thing left is this (https://github.com/TanStack/query/pull/3521):
Types are now emitted into lib instead of a separate types directory. This will help support TypeScript, which will add support for "exports" in the next release.

I'm not entirely sure why some packages are build to cjs with subdirectories, while others are not.
I assume that packages depending on other packages from monorepo have that behavior.
However it's kind of weird that react-query/build/cjs has also query-core build copy.
Is that something to be expected?

@sachinraja please have a look at this PR if you find the time :)


Getting 1006 Error Code on Close

I am migrating my bot to a new slack and I am getting this error "message" on the close handler.  My bot is alive for about 10 seconds before it freezes and throws this error.  I've changed no code

Hmm, I just switched to a better internet connection and it's working.  I'm guessing it had to do with not having a good enough connection.


TC-OPCREDS-3.5 - Automate

https://github.com/project-chip/connectedhomeip/pull/34345#issuecomment-2494928683


Recent Update Issues

I'm currently working to track down more info on the following issues (which commit introduced them, etc.). I'm currently seeing a couple of issues after bringing my fork up to date:
1. Compiling & loading are failing due to doom-themes-visual-bell-config being a void function:
INIT-PACKAGES ERROR (/home/gilbertw1/.emacs.d/modules/ui/doom/config.el): (void-function doom-themes-visual-bell-config)

I'm guessing you have an update coming soon for doom-themes?
2. I am unable to run make compile on a clean checkout. I receive the following error when attempting to do so:
Format specifier doesn’t match argument type
make: *** [Makefile:26: compile] Error 255

3. I've started receiving the following error on startup:
[persp-mode] Error: Can not autoresume perspectives -- (error Variable binding depth exceeds max-specpdl-size)

After which emacs become completely unresponsive to all further commands. Occasionally I'll see an additional error about lisp-eval-depth as well. I've tried updating the max values for both of these limits, but I've had no success so far.
I'll post more here, once I determine more about the causes of each error, and if modifications I've made are to blame.
Thanks!

Thanks @gilbertw1 for looking into this.  From a fresh install, I am experiencing the same error in 1.

@cthachuk you should be able to work around 1 by commenting out that function call in modules/ui/doom/config.el (would give you a line number, but I'm mobile now)

Thanks, @gilbertw1.  Commenting indeed works around 1.  Just to confirm (sorry, no fix), I also quickly run into an error, related to 3, during interactive use (invoking a command for instance): Lisp nesting exceeds 'max-lisp-eval-depth' .

Ack, sorry about that. I jumped the gun with a doom-themes update. I believe all three issues are related to that. I'm working on a fix now.

I've zeroed in on the issue:
1 is caused by the (doom-themes-visual-bell-config) call on line 40 in ui/doom/config.el, which doesn't exist in doom-themes yet.
3 is caused by line 247 in core/core-ui.el. nlinum-hl-mode tries to activate nlinum-mode from nlinum-mode-hook, causing infinite recursion. I already fixed this in nlinum-hl, but published this update too soon, and it hasn't been pulled on Melpa yet.
2 I can't reproduce and am uncertain about, so far.

Thanks for the quick response! I'm back up and running nicely after:

Commenting out the (doom-themes-visual-bell-config) call.
An additional run of make which updated nlinum-hl

Regarding problem 2, it's a bit strange. I only noticed it when I tried to pull a clean copy of my config (and subsequently yours), and tried to run make compile for the first time on either. I can still compile properly on an existing config, but new ones fail everytime for me.

You're right. I tried a fresh install and it would install the out-of-date nlinum-hl (with the recursion error). Very strange. I've bumped the version number. Perhaps it will fix itself in the next Melpa build.

I found the source of problem 2:
Format specifier doesn’t match argument type
make: *** [Makefile:26: compile] Error 255

The problem is that it's no longer using hlissner by default and that's the error it gets when there is no private module matching the user's username. You probably never see it since your computer obviously uses hlissner when you have a new checkout.
You might want to look into adding a friendly error message when this occurs and update your Readme to explain the need to copy the hlissner module or create a new one matching the user's username.
Looks like that explains all the issues I've run into. Thanks for your quick responses!

That should do it, let me know if it continues.

I think that commit fixed that. Now the only issue is (doom-themes-visual-bell-config) not being available in doom-themes on master. I've commented that line out temporarily.

Whoops! Forgot about that for a moment.
I've commented it out for now, so you can safely update.

Thanks!
Also, just FYI, a make install on a fresh clone from latest master fails (probably due to 7005ae1 ?):
Eager macro-expansion failure: (error "Package ‘persistent-soft-’ is unavailable")
Package ‘persistent-soft-’ is unavailable
make: *** [Makefile:51: .local/autoloads.el] Error 255

@aminb I just pushed a update for that issue (in #96)

@hlissner Thanks, but I still got the same error on a fresh clone. Do you not get any errors on a new clone?


Add configuration for kerberos authentication for Ufs HDFS

What changes are proposed in this pull request?
Add configuration for Kerberos: 1) Allow user to specify Kerberos authentication Ufs HDFS. 2) Allow user to specify the location of krb5.conf file ; 3) allow user to enable autorenewal auth with keytab
Why are the changes needed?
Tested out with Kerberos auth for Ufs HDFS. It failed without the change.
Does this PR introduce any user facing changes?
no

@HelloHorizon @beinan Can one of you approve the workflow to kick off the run?

@beinan  Can you review?

@beinan it lgtm

Just addressed the feedback. Thanks @beinan and @HelloHorizon

alluxio-bot, merge this please.

alluxio-bot, merge this please

https://github.com/Alluxio/alluxio/issues/16446
@beinan @HelloHorizon @shangxinli Please take a look at this PR and the comments left by @kuszz , It seems cannot work well when we mount two or more hdfs underfilesystem which use kerberos auth type.


Confusing method called "isAuthenticated()"

This method looks like a getter for the isAuthenticated property, which btw is set on $rootScope (also confusing), but it is not.
Maybe it should be renamed idTokenIsNotExpired() or similar?

It's actually doing a direct check on the token for whether it is expired. Idea being you can do something like:

...

As a public method I think it's more understandable being called isAuthenticated, no?

In that case simply using vm.authManager.isAuthenticated and not even using $rootScope is cleaner as proposed in https://github.com/auth0/angular-jwt/issues/90
Internally, the "isAuthenticated()" method can then be properly renamed to what it actually does and used in the process of setting authManager.isAuthenticated to true or false.

I'm not sure I follow. The isAuthenticated method doesn't set anything but rather returns a boolean. Are you talking about authenticate?

https://github.com/auth0/angular-jwt/search?utf8=✓&q=isAuthenticated&type=
The same phrase is being used for different purposes.
If there is a variable inside a class and a method with the same name, it is often assumed to return the value of that variable, but not here.
Proposal: Stop using $rootScope.isAuthenticated (as suggested in #90 ) and the confusion goes away as well.
The usage will then be, from views:

...

Instead of the cryptic auto-magic variant that only works in views where $rootScope is inherited:

...


Why envoy response different result from different pod?

Description:
I had checked flow_control, and we used default settings.
step 1 :when we use curl in envoy pod
curl --location 'http:/<IP_ADDRESS>:95/material/picture/upload' \
--header 'x-custom-sso: true' \
--header 'Authorization: XT3G6Q1MXvo9r6udULIgOGeDUjNPHG%2B29DneuXYqdCbhvV9uldRljm%2BCATwsN%2FEaSBWfYEo8j1hgUmM1cu07C037PL2j2U2IHzuG2sJU%2B7WQ4FUpatSfIonzWTWTzFIoqEAFNk238wQ80TOEhIlWuIL6zEO5T07TBda1OZNdOlI%3D' \
--form<EMAIL_ADDRESS>
it response

step 2: use curl in other pod
curl --location 'http:/<IP_ADDRESS>:95/material/picture/upload' \
--header 'x-custom-sso: true' \
--header 'Authorization: XT3G6Q1MXvo9r6udULIgOGeDUjNPHG%2B29DneuXYqdCbhvV9uldRljm%2BCATwsN%2FEaSBWfYEo8j1hgUmM1cu07C037PL2j2U2IHzuG2sJU%2B7WQ4FUpatSfIonzWTWTzFIoqEAFNk238wQ80TOEhIlWuIL6zEO5T07TBda1OZNdOlI%3D' \
--form<EMAIL_ADDRESS>
it response

<IP_ADDRESS>  is host mechine ip.
envoy's version is 1.14.1

Without knowing what is different between the two pods, I can't say what is going on here.
Version 1.14 has been unsupported for a very long time.

@ggreenway Thanks.
First curl return http status 413


Update Whoops to 2.0

But still does not work fine.
The layout seems a bit broken. And I can't see source code.

Foundation uses custom Whoops resources, loaded from /src/Whoops, which contain the page templates. I can only assume those aren't compatible anymore either.
It's probably easier to fix this by requiring v1.x instead of dev-master or 2.x.

Yes, please merge https://github.com/fuelphp/foundation/pull/22 first.
It fixes 1.x. And can run FuelPHP without errors.


Remove VideoFrame.to_qimage?

As discussed on gitter, I'm not comfortable with the to_qimage helper for a couple of reasons:

it's tied to PyQt4
it doesn't deal with row alignment issues
it has no from_qimage counterpart

My recommendation would be to purely and simply drop this helper.

Agreed.


How do I add this to my project in angular 6?

In Angular 6 I am getting
ERROR in node_modules/ngx-restangular/src/ngx-restangular-http.d.ts(2,10): error TS2305: Module '"/Users/andrejkaurin/Apps/gpx/gpx-ui/client/node_modules/rxjs/Observable"' has no exported member 'Observable'.
ngx-restangular version: "2.3.0-beta.3"
"@angular/cli": "6.0.3"
"typescript": "2.7.2",

Please update to support angular6

Anyone know a way to use this in Angular 6 without an update?

Guys it is doing great job with angular 6, you can follow this steps to get correct.
$ npm install --save ngx-restangular
Import the restangular module into your app root module
import { RestangularModule } from 'ngx-restangular';
Now, add the module to import list of @NgModule decorator
imports = [
....
RestangularModule.forRoot(restangularConfigFactory)
....
]
Place the below code in app root module
export function restangularConfigFactory(RestangularProvider){
RestangularProvider.setBaseUrl("server address");
}
Now you can use anywhere in other components by doing dependency injection of Restangular

Works with version 3.0.0


Google group options only work from command line

I use a config file for setting oauth2_proxy (v2.1) up, but the Google group related options did not seem to be recognized.  I put them on the command line instead, and they work there.  Is that known, intentional, a bug, I did something wrong...?

Duh, never mind - forgot that the CLI options use "-" and the config file options use "_"


Ensure hygiene filters are restored before moving to next task

See https://github.com/Microsoft/vscode/pull/14115/files/2e1545d59d67c27f60e10cf32f11c74841dfa1d6#diff-97f7cff0ca69e05dd0c8b3914440d43f - this is probably an issue on all platforms. Perhaps the reason it's mainly been an issue for me is that I don't have the tslint extension installed?

@Tyriar The funnelling behaviour is intentional. The rationale, at least for its original implementation, was:
all ⊃ eol ⊃ indentation ⊃ copyright ⊃ typescript
Each of those is a set of files.
Does this not apply anymore?

@bpasero kept telling me to fix my files, the reason being is that the coverage of the pre-commit hook is far smaller than the tslint extension.
The file I wanted that was getting skipped was src/vs/code/test/electron-main/backup.test.ts. copyrightFilter removes the pattern `'!/test/' for some reason would be the underlying cause if the tunnel was intentional, why wouldn't copyright statements be required for tests?

Not really sure why. Let's not filter them out at that step then, see what happens. 👍  Should I look into it?

Removing it probably won't give any new warnings for tslint as gulp tslint runs exclusively with tslintFilter anyway.

Oh I see, the subset of files in gulp tslint is larger than the one in gulp hygiene.
Fixed that in d5e8fcf by adding removing the **/test/** filter and fixing all the hygiene issues in there. Now, the subset of files that pass through tslint when running gulp tslint is the same as when running gulp hygiene. 👍

Thanks @joaomoreno!


Update Composer dependencies (2020-08-14-00-03)

Visual regression test passed!
View the visual regression test report


PoS Remote Node Indexer and Manager

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

feature/pos-networking-and-syncing

PR #876

PR #768

PR #857

PR #879   👈

PR #860

PR #861

PR #858

PR #859

PR #792

PR #793

This stack of pull requests is managed by Graphite.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

feature/pos-networking-and-syncing

PR #876

PR #768

PR #857

PR #879   👈

PR #860

PR #861

PR #858

PR #859

PR #792

PR #793

This stack of pull requests is managed by Graphite.

@tholonious @lazynina thanks for your suggestions for simplifying the RemoteNodeIndexer! I definitely prefer our newset iteration of the indexer. It's cleaner and better aligns with my initial objective of making this code efficient and generic.


twilio::signaling::SipTU::process() crash

One of the crashes referenced in #74.
twilio-signaling crash.txt

Folded into #74.


Language messed up.

Describe the bug
When selecting a new language, not all of the content is in that language. (Eg.: "Your Feed")
To Reproduce
Steps to reproduce the behavior:

Select new language (not English)
See, that many things are still in English. (Which aren't supposed to be)

Expected behavior
Everything is supposed to be in the selected language.
Screenshots

What device are you on?
OS: MacOS Big Sur
Device: Macbook Pro M1 (2021)
Browser: Safari
Additional context
Maybe add translate feature for messages, room names, etc. for some content.

Not all of the translation keys have been added. If you wish to contribute, please see the translation files to make your changes and submit a pull request to get them added.
As for a translations feature, please make a seperate issue as a feature request, though I imagine something like this would be implemented later rather than sooner.


Translated README file into spanish

Hello there!
I found out that redux-saga hasn't been translated into spanish, so I decided to start by translating your README file.
I didn't find any CONTRIB files about how this project gets its PRs, so I just went ahead with this file as a first step, I'll try to translate the rest as I can.
Please let me know if there are any issues with this PR.

Thanks! Great PR


Rewrite UI with Ink

Better testability, nicer code than all the crappy code that’s in table.js 😔

https://github.com/vadimdemedes/ink
https://vadimdemedes.com/posts/building-rich-command-line-interfaces-with-ink-and-react

Progress so far (not pushed to GH yet):
Default output

With -v for verbosity
Using -v|vv|vvv will include the actual complex selectors, colors and perhaps media queries and browserhacks too. Or maybe that

To decide

How many verbosity lebels should there be?
What should be in which verbosity level?

Numbers are fake, these are just mockups to represent the final output


CON-2702: fixed breaking cart when cart coupons don't have a price

Coverage decreased (-0.009%) to 23.758% when pulling 8e553748b8263de798d910147aca916321129b5f on CON-2702-pwa-cart-black-screen-discount-products into b8d6f90a8f0a3f65aee972c7341d82613712be3a on master.


Performance improvement: Maths APIs

Note: for support questions, please use the #engine-user-help channel in our Discord or create a discussion. This repository's issues are reserved for feature requests and bug reports.
Describe the issue:
Currently all maths operations within NovelRT::Maths are handled at runtime, when many could also be marked as constexpr to make the performance cost a compile-time cost, meaning that runtime would be faster.
Please provide the steps to reproduce if possible:

clone the repo
switch to main
call AlignUp from the Maths utilities header
Observe the issue

Expected behaviour:
Certain functions should be marked as constexpr and have their bodies updated accordingly for free perf gain.
Please tell us about your environment:
N/A
Additional context:
I am already adjusting some headers as part of the imgui update as needed - please check if #522 has been merged before picking this up.

Since #522 has been closed, I assume this can be opened up again. But the work that you've done can still be used.
PopCount(uint32_t), Log2(uint32_t), LeadingZeroCount32(uint32_t) and LeadingZeroCount64(uint64_t) are pretty straight forward when it comes to adding constexpr. However, for degree <-> radian conversion, GLM makes it a little bit less straight forward. For a regular use case they would most likely be constexpr. But if a developer were to make GLM use hardware intrinsics, then it would not be able to be marked constexpr.
The way it decides is through this macro magic:
// N2235 Generalized Constant Expressions http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2235.pdf
// N3652 Extended Constant Expressions http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3652.html
#if (GLM_ARCH & GLM_ARCH_SIMD_BIT) // Compiler SIMD intrinsics don't support constexpr...
#	define GLM_HAS_CONSTEXPR 0
#elif (GLM_COMPILER & GLM_COMPILER_CLANG)
#	define GLM_HAS_CONSTEXPR __has_feature(cxx_relaxed_constexpr)
#elif (GLM_LANG & GLM_LANG_CXX14_FLAG)
#	define GLM_HAS_CONSTEXPR 1
#else
#	define GLM_HAS_CONSTEXPR ((GLM_LANG & GLM_LANG_CXX0X_FLAG) && GLM_HAS_INITIALIZER_LISTS && (\
		((GLM_COMPILER & GLM_COMPILER_INTEL) && (GLM_COMPILER >= GLM_COMPILER_INTEL17)) || \
		((GLM_COMPILER & GLM_COMPILER_VC) && (GLM_COMPILER >= GLM_COMPILER_VC15))))
#endif

#if GLM_HAS_CONSTEXPR
#	define GLM_CONSTEXPR constexpr
#else
#	define GLM_CONSTEXPR
#endif

The a solution for this might be to mark DegreesToRadians(float) and RadiansToDegrees(float) with GLM_CONSTEXPR, but that leaks a bit of the implementation detail. So i would not mind a second opinion on that.

On another note, some of the functions in NovelRT::Math::Utilities could make use of already made implementations, PopCount(uint32_t) noted that it could be replaced by std::popcount(int) when compiling for C++ 20. But since the current plans are to keep C++ 17 support for the foreseeable future. It might be able to make use of __builtin_popcount(int) for clang/GCC and fall back on the current implementation on MSVC, like how it is done with NovelRT::Utilities::BitCast<TTo,TTFrom>(const TFrom&). This would make it a little bit more complicated, as there will be more preprocessors making it visually more cluttered.

My take here is we should just do the safe ones - i.e. guaranteed wins without finnicky flag changes - and go from there.


Added support for milestone filter

As per the latest docs, a milestone title can be passed as an argument to filter the issues by that milestone (http://docs.gitlab.com/ee/api/issues.html#list-project-issues)
This adds a milestone key to the array of allowed params.

Thanks. Are you planning on a new release any time soon? I am using a downstream package (http://github.com/vinkla/gitlab) which is pulling in ^7.13, so even an incremental release would let me pull it into production.

Yep, just pushed 7.13.1. Didn't realise it had been nearly a year since the last release 😮


Revisit usage of box-shadow

IMO the shadows used in the app are weird, here's a notification with its default shadow:
box-shadow: rgba(0, 0, 0, 0.53) 0px 0px 8px;

That shadow is unnatural, shadows are caused by objects obstructing a light source, the object in this case is the notification itself and for that shadow to happen the light source should come perpendicularly out of the notification, i.e. it should be perpendicular to the screen, basically it's as if I'm the light source in this scenario, and I'm not usually the main light source in the real world.
In the real world the biggest light source is the sun and during the day it's pretty much always above the objects obstructing its light rays, i.e. the shadow one sees usually is more accentuated at the bottom, not at the top, nor it is uniformly distributed like in the screenshot above.
Here's what a notification with a more natural shadow would look like:
box-shadow: 0 4px 5px 0 rgba(0, 0, 0, 0.14), 0 1px 10px 0 rgba(0, 0, 0, 0.12), 0 2px 4px -1px rgba(0, 0, 0, 0.4);

I think that's a significant improvement, considering we are talking about a shadow, enough of an improvement that I had to open this issue 😅

I wonder how the bot would think this issue is about a slow startup, maybe sun -> star -> start-up? 🤔

Forwarding to @bpasero and @misolori since this is notifications.

We do not have to support to specify more than one shadow color for theme authors. We use widget.shadow currently:
https://github.com/microsoft/vscode/blob/12979c45f17ca571cab023d3542626940d7f3ab6/src/vs/workbench/browser/parts/notifications/notificationsToasts.ts#L452
If we want to revisit box-shadows, we should probably do this consistently throughout all of our uses, there are many more.

Verification:

Compare notifications/quick pick/web dialog shadows are less vibrant than stable version (see for comparison)


Some AVM1 fixes

Makes SWF 123 from the archive show more stuff. Still not fully working, but progress.
r? @yurydelendik.

/botio reftest

/botio reftest

r+


Branch 144215355

Merge conflict in contrib/learn/python/learn/ops/seq2seq_ops.py:
stack/pack (google side) and array_ops_ (github side)
Merged to use array_ops.stack.

Jenkins, test this please.

Ignoring timeouts.


about training datasets

Hi! We are interested in your paper. Can you provide the link of Entry Antispoofing Dataset?

@YmanChris   i have two of the dataset mentioned in the papers but i don't know how to pass the dataset in for training, do  you have any idea?

@YmanChris i have two of the dataset mentioned in the papers but i don't know how to pass the dataset in for training, do you have any idea?

I haven't run the project. But I think it's not a problem to do. You can read the code of training like this.

@YmanChris 我有两个论文中提到的数据集，但我不知道如何将数据集传递给训练，你知道吗？

you can use https://pan.baidu.com/disk/main#/index?category=all

@Lewis0427  How will he login, where are the login user name and password details? have you run this antispoof script? if you have pls can we have a short meeting at your convenience? kindly share your email address or whatsapp contact?

@Lewis0427 How will he login, where are the login user name and password details? have you run this antispoof script? if you have pls can we have a short meeting at your convenience? kindly share your email address or whatsapp contact?

I would like to ask if you can share the data set used in the article, and how to obtain the PKL file mentioned in the original code. If you have it, can you share it? Thank you very much for your help! For sharing, you can use Google Drive or Baidu Netdisk.

So is the Entry Antispoofing Dataset provided??

Is there any update on this ?
What is in the pickle files ?
Can we atleast get the structure of the dataset ?
What might be the file extensions if I'm using videos?
What kind of labels are we passing ?

@vrindamathur1428 @Lewis0427 let me share the dataset with you soon, I will return here to share the link on Google drive

Can you share the dataset?

@vrindamathur1428 @Lewis0427 let me share the dataset with you soon, I will return here to share the link on Google drive

Can you share the dataset?

@vrindamathur1428 @Lewis0427 let me share the dataset with you soon, I will return here to share the link on Google drive

Can you share the dataset and Pretrained? Help me

@vrindamathur1428 @Lewis0427 let me share the dataset with you soon, I will return here to share the link on Google drive

hi sir may I know the pickle file's dataset structure ? thank you~


The bot isn't start

Ignoring exception in on_ready
Traceback (most recent call last):
  File "C:\Users\LENOVO\AppData\Roaming\Python\Python36\site-packages\discord\client.py", line 224, in _run_event
    yield from coro(*args, **kwargs)
  File "bot.py", line 89, in on_ready
    for role in client.get_server(WEREWOLF_SERVER).role_hierarchy:
AttributeError: 'Client' object has no attribute 'get_server'

I have the code error like this.

(Bit late on this but just in case someone else has the same issue:)
You have the wrong version of discord.py installed. Use the async version, not the rewrite version.


Google Colab example does not work

Running the Google Colab example produces an error.
To Reproduce

Select "Open in Colab"
Enter OpenAI credentials
Run top to bottom
Obtain error (screenshot below)

Expected behavior
No error
Screenshots

Desktop (please complete the following information):
Not really relevant, but ...

OS: OSX 13.6.3
Safari 16.6

comment out the embeddings:
graph_config = {
    "llm": {
        "api_key": OPENAI_API_KEY,
        "model": "gpt-3.5-turbo",
        "temperature":0,
    },
    # "embeddings":{
    # }
}

Thank you guys, I fixed the example :)


node, html() is not a function

I'm running this in node:
npm install --save html-chain
var html = require('html-chain')
var test = html
.add('div',
that works but not
var test = html()....
as it is documented in the README.md

Cheers for noticing this, it seems I introduced this in https://git.io/vr2fb, which caused the browser and module versions to be instantiated as a function and object respectively. I'll fix this so the module version requires the function instantiation the same as the browser version. This will be published as the next major version 3.0.0.

Version 3.0.0 has now been released and published - https://github.com/maael/html-chain/releases/tag/v3.0.0 / https://www.npmjs.com/package/html-chain.


feat: replace checkpoint with library version

This deletes all the checkpoint folder and replaces it with the
checkpoint npm package recently published. Effectively marking the
separation of checkpoint from sx-api 🎉.

The lint script is broken (similar than on Checkpoint repo previously) otherwise It works well

@bonustrack I believe I fixed this already, when you checked out the PR did you run yarn install before running lint?

@perfectmak Nvm just did a yarn --check-files and now it work


https://www.upmin.com/admin-rails is a bad link

upmin.com now forwards to the github repo. all other links are going to continue to fail. If there are some docs that need updated, please submit a PR with updates to those. Thanks!

Sure, but the very first link in the repo will produce a 404.  Was there a special section you wanted "admin-rails" to point to in the wiki or something?

I removed it.
Thanks for reporting.


transaction lifetime

Hello,
thanks for creating Gorm, it seems really solid. I have a question about controlling transaction lifetimes. If the default behavior is to create transactions for every save and delete, is there a way to specify the life cycle?
For example, imagine I have two tables that need to be updated within the same transaction, and I want the first save to be rolled back if the second one fails. What is the correct way to do that?
I can imagine using the callbacks to trigger additional operations, but it's complicated in the struct callbacks to figure out what the overall operation was without adding some sort of global state, or possibly introducing something into the scope level.
Also what is the correct way to do interleaved transactions? For example, right now, if I start a transaction at the beginning of a method and run multiple saves within that transaction gorm complains about there being an existing transaction running.
Is there some way for gorm to detect that a transaction is currently running and not add a new transaction and rollback assuming that this is being handled elsewhere?
Many thanks in advance.

Hmm, ok after poking around more, I found doc/development.md, it seems I can control the behavior of the callback chains. Is this an appropriate way to control transaction lifecycles?

tx := db.Begin()
tx.Save(&user)
tx.Save(&product)
tx.Save Or Rollback

Hi Jinzhu,
thanks for the response. Does this work too?
tx := db.Begin()
tx.Create(&user)
tx.Save(&product)
tx.Commit() or Rollback()
Thanks
Yan

OK, Sorry for the issue. One comment. The documentation in the README, is a bit ambiguous, and it would be awesome is there was a bit of explanation about the lifetime of a transaction. I think when I was unit testing it I managed to do something wrong and trigger some warnings, totally my fault. Thanks gain.

Yes, this will works also.
The transactions will only be closed automatically if it is started by itself.


Created sample 23 serving sensor devices as CoAP with service registration over SRP

Hi,
I created a sample with CoAP and SRP. It's a rough without proper error handling and complex logic. But I think it serves its purpose as a sample application.
Feel free to give any feedback. Thanks!
Best
Dongha

Hey - sorry I did not got a notification about this. I might have a look soon.
@wassfila do you wanna have a look as well?

This is cool, thanks @0xlee for this contribution. I just had a quick look at the code, to check that it is serious and not spam (that happens). It looks good. I did not test it, but if we happen to do it, then we might bring any adjustment if necessary, e.g. small renaming or stuff.
I'm glad you like this project and added on it, note that we have a website where we publish the firmware samples with an overview
https://www.homesmartmesh.com/docs/microcontrollers/nrf52/thread_sensortag/#zephyr-tag-firmware
but I would not suggest adding anything in it now, as I'm reworking it with a new framework
and @Informaticore yes, it is going to happen even if this idea was started since a long time and it is going to look awesome
https://github.com/HomeSmartMesh/website-astro
Once I'm done with that, I'll start documenting some new projects I'm starting


Add ranges and range arrays types

This PR enables using postgres range types in query! macros.

Would NUMRANGE be covered by this?

@feymartynov can you please try rebasing and see if it fixes the CI failure?

@abonander seems to be fixed


Video recording duration

Hi,
if i register a video with this code:

from picamera import PiCamera
camera = PiCamera(resolution=(3280, 2464), framerate=30)
camera.start_recording('video.h264', format='h264', quality=10, resize=(1920, 1080))
camera.wait_recording(10)
camera.stop_recording()
camera.close()

the video recorded duration is only 2 or 3 second.
I have test more combination like set resolution to (1920, 1080) and remove resize in method start_recording but the result is the same.
If i register a video with this command:

sudo raspivid -t 10000 -o video.h264

the video recorded duration is 10 second.
Can anyone help me?
Where am I doing wrong?
Thanks.

The sensor can't produe 8MPix @ 30fps - see https://picamera.readthedocs.io/en/latest/fov.html#sensor-modes
It'll be producing probably 1920x1080 @ 30fps and then cropping and upscaling in the ISP.
The ISP will only produce around 120MPix/s (either in or out) so whilst it's trying to take in 30fps, to produce 8MPix output images it'll be dropping frames to produce a maximum of 15fps.
Resize is then a fairly expensive operation, so I suspect you'll be maxing out the processing on that resize too.
H264 you normally set the bitrate rather than the quality. Quality goes and fixes the Qp (quantisation parameter) and can do strange things.


Runner is not alive

When we run the scripts in gauge with js langauge we do see this issue as "runner is not alive" and tests are getting skipped
Version:
Gauge version: 1.4.1
Commit Hash: a82478a
Plugins
html-report (4.1.2)
js (2.3.17)
json-report (0.3.6)
reportportal (1.12.0)
screenshot (0.1.0)
xml-report (0.2.3)
Taiko version:
Version: 1.2.7 (Chromium: 88.0.4314.0) RELEASE

My guess is that something caused an error during the script run, which went unhandled causing the runner to crash.
Do you see anything in the log that might give a hint?
There isn't much info here to delve any deeper.

@sriv  Thanks for your reply. Please check this info and also attached the  gauge.log
I see this error message when i run from local also.
Error:
Error Message: error reading from server: read tcp <IP_ADDRESS>:57616-><IP_ADDRESS>:57615: wsarecv: An existing connection was forcibly closed by the remote host.
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:

Error Message: Runner is not Alive
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:
Successfully generated html-report to => d:\latestframe\reports\html-report\index.html
Successfully generated json-report to => d:\latestframe\reports\json-report
Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:57615: connectex: No connection could be made because the target machine actively refused it."
Specifications:	1 executed	0 passed	1 failed	0 skipped
Scenarios:	1 executed	0 passed	1 failed	0 skipped
Total time taken: 7m53.061s
Updates are available. Run gauge update -c for more info.
Error: Tests failed.

gauge.log

@sriv @NivedhaSenthil  can anyone have a look at this?.. due to this issue we were not able to proceed and blocked!. Thanks in Advance

From the logs, this is the error thrown from taiko:
Error: WebSocket is not open: readyState 3 (CLOSED)

This is a bit tricky to debug without a project where we can replicate this issue. Is there a sample project that you can share? I can try and replicate this issue.

@sriv  I will try to share the sample one.
By looking at this error await we should use before any action i checked my framework it looks good. any suggestion why we get this error as Error: WebSocket is not open: readyState 3 (CLOSED).
browser.js looks like:
beforeScenario(async () => {
if (process.env.api_test_run === 'false') {
await setConfig({ navigationTimeout: parseInt(process.env.test_timeout) });
    if (process.env.host === "local") {
        await openBrowser({ headless: headlessChrome, ignoreCertificateErrors: true, args: ['--no-sandbox', '--start-fullscreen', '--disable-web-security', '--disable-RendererCodeIntegrity'] })
        await deleteCookies();
    } else if (process.env.host === "docker") {
        await openBrowser({ headless_chrome: true, ignoreCertificateErrors: true, args: ['--disable-setuid-sandbox', '--no-sandbox', '--start-fullscreen', '--disable-web-security'] })
        await deleteCookies();
    }
}

});
afterScenario(async () => {
if (process.env.api_test_run === 'false') {
await closeBrowser();
}
});
beforeSpec(async () => {
gauge.message(Environment: ${process.env.environment}, SiteName: ${process.env.siteName});
});
gauge.customScreenshotWriter = async () => {
const screenshotFilePath = path.join(process.env['gauge_screenshots_dir'], screenshot-${process.hrtime.bigint()}.png);
await screenshot({ path: screenshotFilePath });
return path.basename(screenshotFilePath);
};
afterStep(async () => {
if (process.env.api_test_run === 'false') {
gauge.screenshot();
}
});
Any suggestions

I am also facing this issue and blocked with using the automated tests with the below versions. Please help me to fix this issue ASAP.
`gauge -v
Gauge version: 1.2.1
Commit Hash: fa7918b
Plugins
html-report (4.0.12)
js (2.3.17)
json-report (0.3.6)
reportportal (1.12.0)
screenshot (0.1.0)
taiko -v
Version: 1.2.5 (Chromium: 88.0.4314.0) RELEASE`

I am also facing this issue and blocked with using the automated tests with the below versions. Please help me to fix this issue ASAP.

Is there any other info you can provide. Like when you started seeing this error? After an upgrade? How do you run these tests? What os are you using.

Thanks @zabil for taking a looking this issue. Please find the below requested details.
ok sure, I have been using old versions of gauge (1.0.5) and used to get this issue and then it might be due to the old version so I upgraded to 1.2.1 and still facing the same issue.
I am trying to run the specs through jenkins which is setup in ubuntu box and also directly through the terminal. If I run the individual specs I don't get this issue and when I try to run a group of specs through sets (which has around 5-10 specs) or by passing all the 10 specs file through command line I get this issue.
Below are the errors I get in the terminal and in gauge.log
Terminal Errors
Specification: specs/S47.spec         Error Message: error reading from server: EOF         Stacktrace:  [runner: 1]         Error Message: Runner is not Alive         Stacktrace:  [runner: 1]     Error Message: Runner is not Alive     Stacktrace:  [runner: 1]   Error Message: Runner is not Alive   Stacktrace:  [runner: 1]  Failed to kill runner. rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:33111: connect: connection refused"
gauge.log
26-11-2021 09:41:57.813 [js] [ERROR] at WebSocket.emit (node:events:369:20) 26-11-2021 09:41:57.813 [js] [ERROR] at Receiver.receiverOnMessage (/var/lib/jenkins/workspace/TestProject1/node_modules/ws/lib/websocket.js:970:20) 26-11-2021 09:41:57.813 [js] [ERROR] at Receiver.emit (node:events:369:20) 26-11-2021 09:41:57.813 [js] [ERROR] at Receiver.dataMessage (/var/lib/jenkins/workspace/TestProject1/node_modules/ws/lib/receiver.js:517:14) 26-11-2021 09:41:57.813 [js] [ERROR] at /var/lib/jenkins/workspace/TestProject1/node_modules/ws/lib/receiver.js:468:23 26-11-2021 09:41:57.813 [js] [ERROR] at /var/lib/jenkins/workspace/TestProject1/node_modules/ws/lib/permessage-deflate.js:308:9 26-11-2021 09:41:57.826 [Gauge] [ERROR]  Failed Step: Click "Selecr" button 26-11-2021 09:41:57.826 [Gauge] [ERROR] Specification: specs/S47.spec 26-11-2021 09:41:57.826 [Gauge] [ERROR] Error Message: error reading from server: EOF 26-11-2021 09:41:57.826 [Gauge] [ERROR] Stacktrace:  26-11-2021 09:41:57.826 [Gauge] [ERROR] Error Message: Runner is not Alive 26-11-2021 09:41:57.826 [Gauge] [ERROR] Stacktrace:  26-11-2021 09:41:57.827 [Gauge] [ERROR] Error Message: Runner is not Alive 26-11-2021 09:41:57.827 [Gauge] [ERROR] Stacktrace:  26-11-2021 09:41:57.827 [Gauge] [ERROR] Error Message: Runner is not Alive 26-11-2021 09:41:57.827 [Gauge] [ERROR] Stacktrace:  26-11-2021 09:41:57.829 [Gauge] [ERROR] Failed to kill runner. rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:33111: connect: connection refused" 26-11-2021 09:43:33.330 [Gauge] [ERROR]

@sankarasai18-gauge - something has caused the gauge-js runner to crash. It is not clear what, so it is a bit difficult to suggest what is a fix here, without having access to a sample project.
@poornadeem - I put your code in a fresh js project, and I see it is working ok. So I am afraid I need more information to suggest a workaround
One thing is clear though, this is not an isolated incident, and has been a point of concern for some time now. I'd like to fix the root cause -

gauge-js (or any runner) should not crash when there is an error in user code.
in case of a crash, the cause of the error should be reported, rather than a generic stacktrace.

For the above case, I'd need help from the users - if you have some time, please try and provide cases where you see this occurring. This is something that would help immensely.

in case of a crash, the cause of the error should be reported, rather than a generic stacktrace.

Adding to this.
It's likely to be a problem with the page being tested. If it's a specific test that fails all the time it will be filtering it with a tag and running all the tests except that one to see if this happens.

Thanks @sriv @zabil , Its randomly failing in different tests and pages and not always in the same pages/tests. Since its an internal project I am unable to share it here.
I came across thread (https://github.com/puppeteer/puppeteer/issues/4428#issuecomment-500178290) about browser.on('disconnected') and not sure whether this will fix the runner issue?
There is  a similar issue (https://github.com/getgauge/taiko/discussions/1879#discussioncomment-484646) and got fixed by switching to headless mode.  But I am running the tests in headless mode through jenkins/terminal.

@zabil @sriv  found that whenever we see an timeout issue, after that seeing as "runner is not alive". we tried adding more time for elements and tried out.For navigation used as below:
await setConfig({navigationTimeout : 3000000})
For elements we use like:
await waitFor(
$(${departFlightPage.resultFlight()}),
process.env.test_timeout
);
process.env.test_timeout =3000000 externally we give as.
I would like to get a suggestion when the timeout occurs why the runner is getting closed,any suggestions would be an great help?

@zabil @sriv I tried with the below versions of gauge and taiko (1.0.7/1.0.5) and got a different error this time as below and not the above one Runner is not Alive.
So any idea whats the root cause of the below issue?. Looks like Runner is not Alive is specific to latest versions of gauge/taiko and not the scripts 🤔

gauge -v
Gauge version: 1.0.7
Commit Hash: ed7b4fd6
Plugins

html-report (4.0.12)
js (2.3.17)
json-report (0.3.6)
screenshot (0.1.0)
xml-report (0.2.3)
taiko -v
Version: 1.0.5 (Chromium: 81.0.3994.0) RELEASE
gauge.log
29-11-2021 09:40:53.923 [Gauge] [ERROR] Specification: specs/TR/scenarios/tr_s1.spec:18
29-11-2021 09:40:53.923 [Gauge] [ERROR] Error Message: rpc error: code = Unavailable desc = transport is closing
29-11-2021 09:40:53.923 [Gauge] [ERROR] Stacktrace:
29-11-2021 09:40:53.924 [Gauge] [ERROR] Error Message: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:33185: connect: connection refused"
29-11-2021 09:40:53.924 [Gauge] [ERROR] Stacktrace:
29-11-2021 09:40:53.924 [Gauge] [ERROR] Error Message: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:33185: connect: connection refused"
29-11-2021 09:40:53.924 [Gauge] [ERROR] Stacktrace:

The error message indicating that "Runner is not alive" was added later to explain the "rpc errors". The underlying cause is still the same, I believe.

Is this problem solved？ I use Python，also have this problem. Before this, it never appear. I try restart/shut off the mathine,it does not help.
qa@qadeMac-mini cedarhd-workplus-android-test % gauge run specs
Python: 3.8.9
Error occurred while waiting for runner process to finish.
Error : exit status 1
Error Message: error reading from server: EOF
Stacktrace:
Error Message: Runner is not Alive
Stacktrace:
Successfully generated html-report to => /Users/qa/Project/py/cedarhd-workplus/cedarhd-workplus-android-test/reports/html-report/index.html
Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50546: connect: connection refused"
Specifications: 0 executed      0 passed        0 failed        0 skipped
Scenarios:      0 executed      0 passed        0 failed        0 skipped
Total time taken: 291ms

@yicaifeitian we still see this issue.

I am seeing this issue when running Java projects as well. `
Failed to kill Runner: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:35303: connect: connection refused"

I was also facing the same issue.
But now resolved some mistake in step implementation.  Later resolved.
node version: v16.13.1
taiko: 1.2.8
Old code:
const headless = process.env.headless_chrome.toLowerCase() === 'true';
beforesuit(async () => {
await openBrowser({
headless: headless
})
});
afterSuite(async () => {
await closeBrowser();
});
Error:

Solution: changed spelling of "beforeSuite "

Experiencing the same issue here on my mac while using gauge-js.
Anyone got a workaround or a temporary fix?


Adding additional status code metrics

Coverage increased (+0.05%) to 67.268% when pulling 9911ce18732822dd436f84a56c51b721eb2385fd on kevgliss:metrics into 7f823a04cd4f3089d812c3d9f95e591b7602e014 on Netflix:master.


Updated Readme to include pph_unlock_password_data update & account c…

Updated Readme to include pph_unlock_password_data update & account creation in locked phase

Hi @dhishan. Thanks for your PR! I only found that nit.

Also I have created a sample application, separating the creation,
reloading and unlocking with exploring various functions of the library.
Will it add value if we add it as an sample application in the repo?
On Fri, Sep 2, 2016 at 10:40 AM, Santiago Torres<EMAIL_ADDRESS>wrote:

Hi @dhishan https://github.com/dhishan. Thanks for your PR! I only
found that nit.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PolyPasswordHasher/PolyPasswordHasher-C/pull/12#issuecomment-244393930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvJD3m0J2So1ZEspLM_EbCbp68eyI0fks5qmDVlgaJpZM4JzxJq
.

👍 thanks!


DynamicModel validate fail

What steps will reproduce the problem?
I create a simple code like
$post = Yii::$app->request->post();

$model = DynamicModel::validateData($post, [
    [['mid', 'email'], 'required'],
    ['mid', 'number'],
    ['email', 'email']
]);

if ($model->hasErrors()) {
    return ["message" => "Validation fail. Please check your input!"];
}

return ["message" => "Validation pass!"];

What is the expected result?
When I try to access my API by sending only one parameter (for example just a email parameter) I should get an Validation fail. Please check your input! error message from $model->hasErrors().
What do you get instead?
I get an error message Getting unknown property: yii\\base\\DynamicModel::mid
In this case does the required validation just check the parameter values?
Does not check whether the parameters are sent or not? Do I have to make my own validation like isset($_POST['mid'])  before DynamicModel::validateData?
Additional info

Q
A

Yii version
2.0.14-dev

PHP version
7.1.11

Operating system
Win

Before validate you must assign $email and $mid with the same params in $_POST like this:
$email = ArrayHelper::getValue($post, 'email');
and
$mid = ArrayHelper::getValue($post, 'mid');

@maoxuner @berthojoris after more then 5 years, this has been fixed in the latest 2.0.48 release :)

Everything's possible in OpenSource when you take initiative :)


Improve type safety of URLPattern args

This makes the types closer to the behavior of the polyfill and the Chrome implementation by using a discriminated union to determine if the second arg is allowed, and then sharing the args between methods in a tuple type.
Note that this is a breaking change for TypeScript users, as I wanted to get rid of URLPatternInput to improve type safety. If possible, I'd recommend a major release for this.

@SanderElias can you review this?


Remove safe_deployment_abci

The safe_deployment_abci should be removed from the ElCollectooorr.

This has been resolved in a previous PR


Added kustomization in root dir referencing the deploy kustomization

I have added this commit to enable others to reference Kustomize from the root directory. You can use my fork as an example by running kustomize build https://github.com/jdbohrman/argocd-operator.

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

Thanks for your contribution @jdbohrman!


iOS 13 Support?

Hi, thanks for this great work! I think the iOS 14 requirement is unnecessary for this, you can easily integrate this for iOS 13 too. This is just a suggestion and it's important I think :)
Anyway, thanks again :)

fixed in 2.0.0 :)


fix: fix global session timeout calculate

ref: https://github.com/cectc/dbpack/issues/
Ⅰ. Describe what this PR did
fix global session queue add job with wrong delay at
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #118 (be813e3) into dev (9eff19f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #118   +/-   ##
=======================================
  Coverage   48.23%   48.23%
=======================================
  Files          55       55
  Lines        5759     5759
=======================================
  Hits         2778     2778
  Misses       2738     2738
  Partials      243      243

Impacted Files
Coverage Δ

pkg/dt/undolog/table_records.pb.go
21.67% <ø> (ø)

pkg/dt/undolog/undo_log.pb.go
29.13% <ø> (ø)

Continue to review full report at Codecov.

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

LGTM

LGTM


must-gather: gather ceph logs only when storageclusters is present

Now, must gather will only collect ceph logs when there will be a storage cluster deployed. Otherwise, it will skip it.
Signed-off-by: RAJAT SINGH<EMAIL_ADDRESS>

Re pushing since CI failed for no reason.

Re pushing since CI failed for no reason.

/test ocs-operator-ci

/test ocs-operator-ci

/lgtm

/lgtm

/cherry-pick release-4.7

/cherry-pick release-4.7


restart hdparm service on reboot

I have installed and started the hdparm service, but when my retronas is rebooted, the service is not restarted; I have to manually enter the RetroNAS Main Menu -> Advanced -> hdparm -> Start
Can this service be (optionally) restarted on reboot?
https://github.com/danmons/retronas/discussions/332#discussioncomment-7549055_

this service is run from a timer,, continue this discussion in the discussion area

Fixed via https://github.com/danmons/retronas/commit/51329c158a0535ebc300651147ed922aa200e0f4


Fix macro recording

First thing I fixed was I started returning closeInput for openDialogue as expected https://github.com/codemirror/CodeMirror/blob/f9c0e370ec4ddace08bb799965b3f46f9536a553/addon/dialog/dialog.js#L96
Then I fixed a issue where cursorActivity was dispatched twice on change events, once during the change and once from monaco's cursor activity. This caused maybeReset to be true because it goes through https://github.com/brijeshb42/monaco-vim/blob/master/src/cm/keymap_vim.js#L5234-L5239 twice

@brijeshb42 when should I expect 0.0.8?

Just published with fixes for supporting latest monaco as well.


Update ExamplesHub scene paths

This change addresses a CI failure where the examples hub scenes were failing path validation due to moving the examples folder (#7509).

/azp run


Helptext: Missing sizes in Figma

Helptext should come in small, medium, large. Must be updated in Figma.

Added Small, medium and large sizes to both HelpText and Popover. https://www.figma.com/file/vpM9dqqQPHqU6ogfKp5tlr/Felles-komponenter?type=design&node-id=20759%3A80130&mode=design&t=pFMkxezHjX6MVQWE-1


Swish-1 and GELU activation for transformers

This adds support for two activation types to transformers:

Swish-1 (Ramachandran et al. 2017: Searching for Activation Functions)
GELU (Hendrycks and Gimpel 2016: Bridging Nonlinearities and Stochastic Regularizers with Gaussian Error Linear Units)

The first paper reports that Swish-1 beats ReLU on transformer models.  The second reports that GELU beats Swish-1, but not explicitly tested on transformers.
Edit: If we want to avoid a bunch of sequential major version bumps, this can wait until #226 is ready to go and we can have a single bump for all transformer updates.
Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[x] System tests pass (pytest test/system)
[x] Passed code style checking (./pre-commit.sh or manual run of pylint & mypy)
[x] You have considered writing a test
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

+1 on syncing with #226 and #222 to not end up with Sockeye 1.inf :)

This should be up to date and ready to merge.


Compilation errors

error[E0277]: the trait bound `std::string::String: glib::translate::ToGlibPtr<'_, *mut i8>` is not satisfied
  --> /home/chessnokov/.cargo/registry/src/github.com-1ecc6299db9ec823/gio-0.5.0/src/subprocess.rs:40:35
   |
40 |         let stdin_buf = stdin_buf.to_glib_full();
   |                                   ^^^^^^^^^^^^ the trait `glib::translate::ToGlibPtr<'_, *mut i8>` is not implemented for `std::string::String`
   |
   = help: the following implementations were found:
             <std::string::String as glib::translate::ToGlibPtr<'a, *const u8>>
             <std::string::String as glib::translate::ToGlibPtr<'a, *mut u8>>
   = note: required because of the requirements on the impl of `glib::translate::ToGlibPtr<'_, *mut i8>` for `std::option::Option<std::string::String>`

error[E0308]: mismatched types
  --> /home/chessnokov/.cargo/registry/src/github.com-1ecc6299db9ec823/gio-0.5.0/src/subprocess.rs:57:77
   |
57 |             ffi::g_subprocess_communicate_utf8_async(self.to_glib_none().0, stdin_buf, cancellable.0, Some(callback), Box::into_raw(user_data) as *mut _);
   |                                                                             ^^^^^^^^^ expected u8, found i8
   |
   = note: expected type `*const u8`
              found type `*mut i8`

error: aborting due to 2 previous errors

Some errors occurred: E0277, E0308.

That's fixed in git https://github.com/gtk-rs/gio/pull/155
@GuillaumeGomez should make a bugfix release for this

Yes. I'll try to do it today.


Create resource definition not show port options

Describe the bug
Resource Definition template webservice attributes Ports form show wired option
Steps to reproduce

Go to resource definition to create a new resource definition
Choose webservice template and version v0.0.5
Config Baisc information for the resource definition.

Result

The Ports do not show 80 option by default.
https://github.com/seal-io/walrus/assets/85595852/cbde30a0-6047-473c-8653-21b4d8a30e55

Expected behavior

Ports selection options shows correctly.
Environment

Walrus version: UI dev-4955441
Walrus version: Server abc217a55cf7a6c0c39d4f8dec61d32ced2436b7

Additional context
Add any other context about the problem here.

Env:  walrus-ui: 6b316d39797a9bb76af6eec65d28de85e76be1dd
Test Result: PASS


Use error log for the following message

{"level":"info","pid":2949,"pkg":"http","service":"ocs","service":"ocs","scope":"notifications","time":"2024-03-13T10:37:33.194115379+01:00","caller":"github.com/cs3org/reva@v1.27.0/pkg/notification/notificationhelper/notificationhelper.go:228","message":"notification trigger skipped, notification helper is misconfigured"}

Hello, this is a test


devstack: fix the permission of all directories

In 352d58a7afd9e2261e639af78e4fb4c99d8f9f81 of openstack/devstack.git
fixing of permissions on existing directories was dropped. The script
that is changed here relied on that. Adapt it to also take over fixing
the permission of the rest of the directories.

The commit message looks bit confusing to me, the action is not about changed permissions, just about different directory ...

It is about changing the owner of more directories, as the new target of the chown is the parent of the old target.

Without it the error is:
+ ./stack.sh:main:374                      :   mkdir -p /opt/stack/logs
mkdir: cannot create directory ‘/opt/stack/logs’: Permission denied

Amended the commit message, please rereview.


Defining single integration test encapsulating several resources

How to define integration test that encapsulates several resources.
For instance we would like to couple together:

batch account
batch application
batch pool
etc.

What is the correct way of doing that in Magic Modules?
The test should like like this:

create batch account
update batch account - idempotent (same parameters)
update batch account - different parameters (possibly different example)
create batch application
update batch application - idempotent
update batch application - different parameters
delete batch application
delete batch account
How the definition of such tests should look like?

It is not supported in MM. Need more investigation.


Preview shows inaccurate UI

UI in preview:

Same UI on a web page:

Link to app and chat
https://labs.writingmate.ai/share/0Y87
https://labs.writingmate.ai/chat?forkMessageId=8b353d1b-2bf3-4f0e-8268-0172b6e60e04&forkSequenceNo=0

this is fixed. Both preview and shared app shows the same result. To fix the layout of the tabs, I recommend saying "use standard DaisyUI tabs"


Update nginx to v1.5.1

/kind enhancement
What this PR does / why we need it:
Update nginx to v1.5.1: ref
Additionally bind it to nodes with worker.gardener.cloud/system-components label, that it does not run on the same nodes as e2e tests.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/lgtm
/approve


Error in the 2nd CA policy for blocking: Restrict access to privileged resources

Hello,
In the second policy in step 5.c it states: ExtensionAttribute1, the operator to Equals and the value to SAW.
I have tested the rules as I was unsure if it worked with devices that didn't report device information for one reason or another
According to my tests - devices that don't report device information is indeed not blocked. However surprisingly devices that does report device information and is not matching the attribute was also not blocked!
If I modify the Policy so it uses an include filter and set the filter to: "device.extensionAttribute1 -ne SAW" instead, the policy works and it blocked all devices that is not reporting device information and/or does have the correct value in the attribute.
//Peter D.

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

ID: fcc79933-58e1-66d1-81ae-f43802d41223
Version Independent ID: 5be1fefc-356e-d1eb-ab97-8cbe5654ff43
Content: Filter for devices as a condition in Conditional Access policy - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/conditional-access/concept-condition-filters-for-devices.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@IAmPetersCode
Thank you for reaching out to us. We are looking into this issue and will get back to you on this

@IAmPetersCode Apologies for the delay in responding to this issue.
Please send me an email to<EMAIL_ADDRESS>with Sub - Attn: Givary and following details in the email body:
Link to this thread/post
We can connect offline and discuss further on this.

@IAmPetersCode As per offline discussion we had, i am marking this issue as resolved.


Test Implementations of Focus Traps with Components

For accessibility, test out some traps to keep SR inside the component.

With F7, the current page has a class of current-page.
Components such as modals, popovers, or alerts, are not within the current-page. They are also handled by F7 so the user cannot reach them unless they are opened.
Those two things make the strategy where when opening a component we can toggle the aria-hidden on outside parts. That part with F7 will only be the current-page. On close of the component, toggle it back.
Tested On:
Popovers

Toast's general purpose not requiring user interaction makes it not need the focus trap. Toast + SR-text works well for feedback information.


"'clang-c/Platform.h' file not found" after brew install --with-toolchain

I ran brew install with tool chain llvm and I still get "'clang-c/Platform.h' file not found". Not sure if I am missing a step.

You need a pkg-config file.
sudo swift ClangSwift/utils/make-pkgconfig.swift

@ddddxxx what to do if I'm getting?
Running /usr/bin/which /usr/local/opt/llvm/bin/llvm-config...
error: Failed to find llvm-config. Ensure llvm-config is installed and in your PATH

Is there a build instruction? Or at least a list of system requirements to have?


[AutoPR mixedreality/resource-manager] Add TypeScript ARM mixedreality package

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5270

(message created by the CI based on PR content)

TS PR


Search bar

In the navbar, to the right, a text field needs to be displayed. Typing in the text area will cause the devices list to be opened, filtered by the text typed into the field.

Since converting back end, this needs to be reimplemented.


Authenticating the user/Expected errors could use more details.

The description of the response under "Authenticating the user"/"Expected errors" isn't very helpful. It would be nice to know the HTTP Response codes that should be checked and what fields the JSON response object contains. Is it always a 400 response? Could it be a 500 response?

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

ID: 58bc32c3-9e21-a56a-f876-3e750576f228
Version Independent ID: 83231247-55a8-e69b-0712-8c7b1481a02d
Content: OAuth 2.0 device authorization grant - Microsoft Entra
Content Source: articles/active-directory/develop/v2-oauth2-device-code.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@martingbrown
Thanks for your feedback! We will investigate and update as appropriate.

@OwenRichards1
Can you please check and add your comments on this doc update request as applicable.

@martingbrown
I'm going to assign this to the document author so they can take a look at it accordingly.

@martingbrown The HTTP/S status line returned by Entra ID's token issuance services adhere closely to standards outlined in RFC 7231§3.1.
Suffice to say...

4XX status codes are used when the client has sent a bad, malformed, or otherwise unserviceable request.
5XX status codes are used when the service experiences an issue, such as gateway timeout or outage.

The vast majority of errors that will arise in these circumstances will be 4XX class errors. I would expect 5XX errors to show up here only in the event of outage; status page for Azure services can be found here.
In general, we advise developers to use our MSAL libraries to communicate with our token issuance services; these handle the try{}/catch{} of success and error cases.
For developers coding against the wire protocol, separating success from errors is most important - hardly any 4XX or 5XX errors are resolvable without user interaction, with the notable exception of Claims Challenges. Any 4XX class error will be accompanied by error body and AADSTS error code. These are documented here.


Biometrics doesn't work

Ok I have followed the wiki and used flatpak run --filesystem=home --command=goldwarden com.quexten.Goldwarden setup browserbiometrics
I get the output below.
When I try to use biometrics it complains about not being setup in the bitwarden desktop app.  I am using firefox.
Native messaging host directory already exists: /var/home/todd/.config/google-chrome/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/google-chrome-beta/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/google-chrome-unstable/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/chromium/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/microsoft-edge-beta/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.config/microsoft-edge-dev/NativeMessagingHosts/
Native messaging host directory already exists: /var/home/todd/.mozilla/native-messaging-hosts/
Found chrome-like browser: /var/home/todd/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/BraveSoftware/Brave-Browser-Beta/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/BraveSoftware/Brave-Browser-Nightly/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/chromium/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/google-chrome/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/google-chrome-beta/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/google-chrome-unstable/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/microsoft-edge-beta/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found chrome-like browser: /var/home/todd/.config/microsoft-edge-dev/NativeMessagingHosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Found mozilla-like browser: /var/home/todd/.mozilla/native-messaging-hosts
Removing old manifest and proxy script
Writing new manifest
Writing new proxy script
Done

Is this just #278 ?


Emacs site-start: Use correct feature name

Motivation for this change
Tramp upstream recently dropped the autoload cookie from
tramp-remote-path. This makes Emacs error when trying to load tramp.
Using the correct feature name fixes this.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Can you confirm it still works with this change in emacs 25? (ideally we would also support emacs 24 but not a hard requirement).

@matthewbauer That variable has been defined in tramp-sh.el since at least Emacs 24, so should be all good.

Ok thanks


:checkhealth is broken

Running healthchecks...
E5009: Invalid $VIMRUNTIME: /nix/store/minvn39fypkwayivr8w7w2ba0jlrsspl-neovim-unwrapped-9f32deb/share/nvim/runtime
Error executing lua: Vim:E117: Unknown function: health#efmls_configs#check
stack traceback:
	[C]: in function 'call'
	...-unwrapped-9f32deb/share/nvim/runtime/lua/vim/health.lua:303: in function <...-unwrapped-9f32deb/share/nvim/runtime/lua/vim/health.lua:271>

It prevents any other healthchecks from running.

This doesn't look like you are on the latest nvim version, latest is nvim 0.9.x. Are you on at least nvim 0.7 or 0.8?

I'm on nvim v0.10.0-dev-9f32deb

It looks like the health API may have changed since I also get this in a notification:
vim.health.report_ok() is deprecated, use vim.health.ok() instead. :help deprecated

That's interesting to know but that shouldn't give the error, can you try on the latest nightly? I don't really plan for nightly version because they change quite frequently.
I just tried on the homebrew version NVIM v0.10.0-dev-1361+g0892c1cd9-Homebrew which is following master and I do get the deprecated message but no errors.

Same issue. It may have something to do with the way Neovim is installed via Nix, however it doesn't happen with any other plugin and it works if I don't load efmls-configs.
12:33:47 msg_show    checkhealth Running healthchecks...
   Warn  12:33:47 notify.warn vim.health.report_error() is deprecated, use vim.health.error() instead. :help deprecated
This feature will be removed in Nvim version 0.11
   Warn  12:33:47 notify.warn stack traceback:
	...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:201: in function 'deprecate'
	...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:226: in function 'report_error'
	...git/efmls-configs-nvim/lua/efmls-configs/health/init.lua:19: in function 'check'
	[string "require("efmls-configs.health").check()"]:1: in main chunk
	[C]: in function 'pcall'
	...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:306: in function <...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:271>
   Error  12:33:47 msg_show.emsg    checkhealth E5009: Invalid $VIMRUNTIME: /nix/store/cw5y9yy5m3cm8s2h1hiw2ifan1xczbpw-neovim-unwrapped-2eecb1b/share/nvim/runtime
12:33:47 msg_show    checkhealth Error executing lua: Vim:E117: Unknown function: health#efmls_configs#check
stack traceback:
	[C]: in function 'call'
	...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:303: in function <...-unwrapped-2eecb1b/share/nvim/runtime/lua/vim/health.lua:271>

Yeah, I don't have a nix environment for me to test but it's an interesting problem. I will push out PR to support the new health API in any case to prepare for it.


Send Email with Template

I didn't see example that consist:

Send email with Thymeleaf HTML Template
Send email with MailGun HTML Template
Can You provide the sample?

Thanks in advance

@hendisantika, thanks for your question.
Mailgun Java SDK is the only wrapper that uses Mailgun API
https://documentation.mailgun.com/en/latest/api_reference.html
As described in Mailgun documentation
https://documentation.mailgun.com/en/latest/api-templates.html#store-new-template
The template engine is used to render the template. This is valid only if the template parameter is provided.
Currently, the Templates API supports only the handlebars engine.
What is Handlebars:
https://handlebarsjs.com/guide/#nested-input-objects
Because the Mailgun Java SDK does not have additional logic and only uses the Mailgun API, anything that works with curl or Postman should work with the Mailgun Java SDK.
If so, it is better to ask such questions directly in the Mailgun Help Center
https://help.mailgun.com/hc/en-us

OK. Thanks for the answer.


Minting on ordinalswallet discord

Hey guys  who should i contact abt a partnership ? For a minting on your discord for example.  Feel free to contact us https://twitter.com/BitcoinApesNFT <3

dm sent


Add a seed script until we can get "real data"

This is branched off of #52 , should probably wait for that to merge first.
fixes #56

Cross join has me cross eyed, this is what magic looks like

sorry, i re-did what I did earlier. this is what the data looks like now.
salz=# select * from salz.users order by random() limit 5;
 id  |  username  |         created_at         |         updated_at         | icon_path  | identity_provider | identity_provider_id | elo
-----+------------+----------------------------+----------------------------+------------+-------------------+----------------------+------
  43 | testuser28 | 2024-09-17 18:53:15.562518 | 2024-09-18 18:53:15.562518 | user28.png | basicauth         | testuser28           | 1055
  37 | testuser22 | 2024-10-03 07:35:39.468683 | 2024-10-04 07:35:39.468683 | user22.png | basicauth         | testuser22           | 1873
  95 | testuser80 | 2024-11-12 13:57:01.220621 | 2024-11-13 13:57:01.220621 | user80.png | basicauth         | testuser80           | 1264
 106 | testuser91 | 2024-09-26 00:20:53.599211 | 2024-09-27 00:20:53.599211 | user91.png | basicauth         | testuser91           | 1948
  99 | testuser84 | 2024-08-29 06:30:57.274928 | 2024-08-30 06:30:57.274928 | user84.png | basicauth         | testuser84           | 1762

salz=# select * from salz.bots order by random() limit 5;
 id  |         created_at         |         updated_at         | upload_path  | user_id | status
-----+----------------------------+----------------------------+--------------+---------+---------
 205 | 2024-11-01 15:09:33.975872 | 2024-11-01 15:24:33.975872 | bots/101.zip |     101 | healthy
 150 | 2024-09-28 03:03:17.419942 | 2024-09-28 03:18:17.419942 | bots/46.zip  |      46 | healthy
 124 | 2024-10-12 08:10:18.078328 | 2024-10-12 08:25:18.078328 | bots/20.zip  |      20 | healthy
 162 | 2024-10-22 22:05:39.744661 | 2024-10-22 22:20:39.744661 | bots/58.zip  |      58 | healthy
 146 | 2024-09-20 06:52:19.838565 | 2024-09-20 07:07:19.838565 | bots/42.zip  |      42 | healthy

salz=# select * from salz.games order by random() limit 5;
 id  |         created_at         |         updated_at         |  status  | upload_path
-----+----------------------------+----------------------------+----------+-------------
 205 | 2024-11-21 13:43:13.090601 | 2024-11-21 13:50:12.224678 | Running  |
 213 | 2024-10-10 12:24:46.937309 | 2024-10-10 12:24:46.937309 | Pending  |
 207 | 2024-11-10 09:45:41.173085 | 2024-11-10 10:18:35.05068  | Finished |
 210 | 2024-10-07 20:20:26.824309 | 2024-10-07 20:57:53.951735 | Finished |
 241 | 2024-10-29 17:21:33.31329  | 2024-10-29 17:21:33.31329  | Pending  |

salz=# select * from salz.game_participants where game_id = 207;
 game_id | user_id | bot_id |        score         |        updated_at
---------+---------+--------+----------------------+---------------------------
     207 |      46 |    150 |  0.07028710385794446 | 2024-11-10 10:18:35.05068
     207 |     106 |    210 |   0.4518557837314263 | 2024-11-10 10:18:35.05068
     207 |      88 |    192 |   0.1932157663146994 | 2024-11-10 10:18:35.05068
     207 |      51 |    155 | 0.012945860688300392 | 2024-11-10 10:18:35.05068
     207 |      83 |    187 |   0.3594883922182346 | 2024-11-10 10:18:35.05068

salz=# select * from game_participants where game_id = 208;
 game_id | user_id | bot_id | score |         updated_at
---------+---------+--------+-------+----------------------------
     208 |     111 |    215 |       | 2024-10-24 00:34:35.803958
     208 |      52 |    156 |       | 2024-10-24 00:34:35.803958
     208 |     115 |    219 |       | 2024-10-24 00:34:35.803958
     208 |      80 |    184 |       | 2024-10-24 00:34:35.803958
     208 |      49 |    153 |       | 2024-10-24 00:34:35.803958
(5 rows)

also, after this abomination of a PR maybe we should talk commit message standards xD


aac too complex

windows, specific devices
Microphone Array Realtek(R) Audio 4 channels, 16 bit 48000 Hz

around here https://github.com/mediar-ai/screenpipe/blob/89f7f0302325bf2ab9641c0a66921405f1bb969e/screenpipe-audio/src/pcm_decode.rs#L41

tried before to hard code to max 2 channels when encoding to file using ffmpeg but had another issue dont remember what

solution would be to send recorded audio to STT directly instead of encoding to disk and doing STT

solved


Use configured admin's default site login_template

If the developer modifies their default admin site login_template, this will allow explorer to respect the specified login_template. This has the benefit of also making no change if the developer does not change the default admin site.
Override default admin: https://docs.djangoproject.com/en/dev/ref/contrib/admin/#overriding-the-default-admin-site
Changing the admin login_template: https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.AdminSite.login_template
According do the docs, the login_template attribute dates back to 1.7 at least.

hi @wgordon17, thanks for your PR. tests seem to be failing here; think you can make the necessary updates to get the build passing before we merge?


Remove "debug" links.

Please remove these links:

this need for debugging, when users contact support

We can hide it to "The swap was stuck? Try to reload the page. Debug information [here]"

Implemented as it was suggested in the previous comment