Unable to create users with sfdx command - getting a JWT error

Using the latest salesforce/cli version -- the cli version we tried is [2.24.4 and [1.86.7-legacy.0] when we create user we are getting the JWT token error
Command we run
first, we authenticate to the scratch org created using JWT
echo "Authenticating to the org"
sf org login jwt --client-id=${{ secrets.SAGE_PEOPLE_DEVHUB_CONSUMER_KEY }} --username=${{ needs.Build_time_scratch_org.outputs.sysadminusername }}  --instance-url ${{ needs.Build_time_scratch_org.outputs.instanceUrl }} --jwt-key-file ./server.key --set-default
sf org display --target-org ${{ needs.Build_time_scratch_org.outputs.sysadminusername }} --json
Upon success of org display we tried to create users
sf org create user --json username=${username} profileName="Standard User" firstName=${firstname} lastName=${lastname} --target-org ${sysadmin} > user.json
Error details
{
"code": 1,
"context": "CreateUserCommand",
"commandName": "CreateUserCommand",
"message": "Error authenticating with JWT.\nErrors encountered:\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer",
"name": "SfError",
"status": 1,
"stack": "SfError: Error authenticating with JWT.\nErrors encountered:\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer\nuser hasn't approved this consumer\n    at SfError.wrap (/usr/local/lib/node_modules/@salesforce/cli/node_modules/@salesforce/core/lib/sfError.js:79:20)\n    at catchCreateUser (file:///usr/local/lib/node_modules/@salesforce/cli/node_modules/@salesforce/plugin-user/lib/commands/org/create/user.js:244:23)\n    at getNewUserAuthInfo (file:///usr/local/lib/node_modules/@salesforce/cli/node_modules/@salesforce/plugin-user/lib/commands/org/create/user.js:227:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async CreateUserCommand.run (file:///usr/local/lib/node_modules/@salesforce/cli/node_modules/@salesforce/plugin-user/lib/commands/org/create/user.js:71:33)\n    at async CreateUserCommand._run (/usr/local/lib/node_modules/@salesforce/cli/node_modules/@oclif/core/lib/command.js:304:22)\n    at async Config.runCommand (/usr/local/lib/node_modules/@salesforce/cli/node_modules/@oclif/core/lib/config/config.js:417:25)\n    at async run (/usr/local/lib/node_modules/@salesforce/cli/node_modules/@oclif/core/lib/main.js:85:16)",
"exitCode": 1,
"warnings": [
"The --target-dev-hub flag is deprecated and is no longer used by this command. The flag will be removed in API version 57.0 or later."
]
}
this was all working correctly before .. we have seen this happening for the last 1 week only ..
This is breaking our CI completely

I have updated the cli version to the ticket

Was your org recently updated to a hyperforce instance?  If so, creating users with JWT auth won't work due to server side changes, not CLI changes.  If this is the case you should switch to use auth url.

@shetzel  shetzel the way we do is we use JWT to authenticate to dev hub so u are saying that will not work going forward

@subashniprasannasagecom - I'm saying it will not work if your org is on hyperforce.  Recent CLI versions will output an error message stating if this is the case.  If it is, and you need to create users in a scratch org from the CLI, you'll need to switch to use the auth url method.  That's outside of the CLI's control since it's server side.  But the first thing to do is find out if you're on a hyperforce instance.  https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000BsIhCSAV

yes my org is hyperforce server .. is there any workaround for this ..as it is run in CI


Set up a test for internal links

Right now it's too easy to break links and links get broken.
It would be nice if we would check all intra links with GitHub Actions to detect breakage.

$ zola check


Controller node not being properly tainted

/opt/bin/taint-and-uncordon had a syntax issue with the kubectl taint command. Was failing with error: at least one taint update is required and the controller node was still getting pods scheduled to it. PR fixes the syntax as per http://kubernetes.io/docs/user-guide/kubectl/kubectl_taint/

Current coverage is 68.99% (diff: 100%)

Merging #199 into master will not change coverage

@@             master       #199   diff @@
==========================================
  Files             4          4
  Lines          1132       1132
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            781        781
  Misses          262        262
  Partials         89         89

Powered by Codecov. Last update 2b29fc3...3822c52

@artushin Thanks for your help!
I'm not sure how I'd made a mistake like this slipped into the v0.9.2-rc.2 release but your fix does seems to be correct.
Please give me a day or two to test before/after merging your fix by running our e2e tests.

Taint-and-cordon still fails:
taint-and-uncordon[25536]: [14820.578848] hyperkube[5]: error: Node 'ip-10-0-0-224.us-west-2.compute.internal' already has a taint with key (node.alpha.kubernetes.io/role) and effect (NoSchedule), and --overwrite is false

With that fixed, I'm seeing a failure with
taint-and-uncordon[26251]: rm: unable to remove pod "1696c88c-99f4-4810-bb77-d406315f1452": remove /var/lib/rkt/pods/exited-garbage/1696c88c-99f4-4810-bb77-d406315f1452/stage1/rootfs: device or resource busy

Haven't used rkt, so that'll require a bit of investigation. Also my controller is becoming CPU bound eventually. Maybe because of this issue and a ton of un-garbage-collected rkt images? I dunno.

sudo rkt run
...
 --uuid-file-save=/var/run/coreos/taint-and-uncordon.uuid \
...
sudo rkt rm --uuid-file=/var/run/coreos/taint-and-uncordon.uuid

seems broken. Can you just rely on regular gc?

Any updates on this? Is the snippet

sudo rkt run
...
--uuid-file-save=/var/run/coreos/taint-and-uncordon.uuid
...
sudo rkt rm --uuid-file=/var/run/coreos/taint-and-uncordon.uuid

safe to remove without affecting other parts?
I'm having problems with the CPU usage. Turns out that if I reboot the instance, the CPU usage resets, however, weird things happen after rebooting e.g. pods not being able to see each other, multiple restarts of DNS and apiserver containers, etc.

@reiinakano , @artushin these commands delete container which rkt created to run command, do you have an idea how it might be related to high CPU time?

@redbaron When I was seeing the issue, rkt list had a ton of errors like
list: Unable to read pod fb7842e7-ab0a-49fb-845a-2399b36a8151 manifest:
  error reading pod manifest

so I assume those failed taint-and-uncordon containers were being kept around possible increasing CPU usage from failing GC? Someone with more rkt knowledge should look into the failure case of running the taint-and-uncordon job. In the meantime, if the script passes, the CPU usage issue shouldn't occur.
Don't understand why simply getting that script to run without error relieved so much cpu though, because unlike @reiinakano, I didn't rebuild the cluster, I just edited the script in /opt.

Even after I editing the '/opt/bin' script so that the taint works, the task still just fails over and over. As @artushin noted the sudo rkt rm --uuid-file=/var/run/coreos/taint-and-uncordon.uuid always seems to fail with rm: unable to remove pod.
Jan 08 21:15:57 ip-<IP_ADDRESS>.ap-southeast-2.compute.internal taint-and-uncordon[13188]: rm: unable to remove pod "53f4b000-7782-4b60-81b5-2997$
Jan 08 21:15:57 ip-<IP_ADDRESS>.ap-southeast-2.compute.internal systemd[1]: kube-node-taint-and-uncordon.service: Main process exited, code=exite$
Jan 08 21:15:57 ip-<IP_ADDRESS>.ap-southeast-2.compute.internal systemd[1]: kube-node-taint-and-uncordon.service: Unit entered failed state.
Jan 08 21:15:57 ip-<IP_ADDRESS>.ap-southeast-2.compute.internal systemd[1]: kube-node-taint-and-uncordon.service: Failed with result 'exit-code'.

These failed, but not cleaned up rkt pods seem to mount up and grow a docker clean-up task that runs about every 60s. I don't know how rkt works either. But it may be this clean up task that gradually grows and increase the load as the number of failed containers mount.
You can see the slow, but inevitable death-spiral on this controller I just made. The taint-and-uncordon is patched to always work, but the rkt task fails each time, and the number pods in the 60s clean-up task gets longer and longer, and the CPU load higher and higher.

Hi remade the same cluster as above, this time fully removing the taint-and-uncordon task from the cloud-init file. Compare the CPU profiles, it is back to normal and comparable with my other clusters, settling at 15% soon after launch. Compare that with when the taint-and-uncordon task was still there, the CPU is never below 60% and slowly climbs to 100% over time.

Although the controller is stable with taint-and-uncordon removed, that problem with the periodic clean-up task persists, it just doesn't get any worse. Every time is it just eight containers mentioned in the errors every 60 seconds, plus the error opening '/run/docker/libcontainerd/docker-containerd.pid'.
I guess there is a deeper problem with the rkt container tasks that we just don't notice until one goes awry like taint-and-uncordon does. It could be we could reduce the controller CPU load further by solving this problem
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal kubelet-wrapper[1537]: E0108 23:51:33.217869    1537 container_manager_linux
.go:625] error opening pid file /run/docker/libcontainerd/docker-containerd.pid: open /run/docker/libcontainerd/docker-containerd.pid: no suc
h file or directory
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.233938247Z" level=error msg="Handle
r for GET /containers/3da5a08fd693749466ccfd1ed1b52164619bf86c4a2a39f1c0caafdf6c450ccd/json returned error: No such container: 3da5a08fd69374
9466ccfd1ed1b52164619bf86c4a2a39f1c0caafdf6c450ccd"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.267776846Z" level=error msg="Handler for GET /containers/73ddc461d2b1f0746853940eadb7951b939d0ae4e0a5257a41e17bbf48646293/json returned error: No such container: 73ddc461d2b1f0746853940eadb7951b939d0ae4e0a5257a41e17bbf48646293"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.273305898Z" level=error msg="Handler for GET /containers/1bc2af7f3283cd951ad93ed8918761bac247cef4d6b366fa0e071addd3583003/json returned error: No such container: 1bc2af7f3283cd951ad93ed8918761bac247cef4d6b366fa0e071addd3583003"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.282636512Z" level=error msg="Handler for GET /containers/f68bdb07afd94c87b2c55060894bef4b4e30a9a9b5e56c4e068de74ac34d7e8e/json returned error: No such container: f68bdb07afd94c87b2c55060894bef4b4e30a9a9b5e56c4e068de74ac34d7e8e"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.283499144Z" level=error msg="Handler for GET /containers/e18bc18d22fc7cf5722ed3bf39ade10e59b78809ef5786c8fc71d77fd0869132/json returned error: No such container: e18bc18d22fc7cf5722ed3bf39ade10e59b78809ef5786c8fc71d77fd0869132"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.284049871Z" level=error msg="Handler for GET /containers/e071cceebc9c4a2813fd3c61be60e4388b6d98bbee77092fd1a3439fb64af2ff/json returned error: No such container: e071cceebc9c4a2813fd3c61be60e4388b6d98bbee77092fd1a3439fb64af2ff"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.284594161Z" level=error msg="Handler for GET /containers/3755d84cb13cc852423bb29635476a7a4f3d9053d254c376432add0af64b61d0/json returned error: No such container: 3755d84cb13cc852423bb29635476a7a4f3d9053d254c376432add0af64b61d0"
Jan 08 23:51:33 ip-1-1-1-1.region.compute.internal dockerd[1421]: time="2017-01-08T23:51:33.285088451Z" level=error msg="Handler for GET /containers/a30eb84ec2e8f61118b9a4715b11d640db1d1dc91d86e4a871f4657697ee2e1d/json returned error: No such container: a30eb84ec2e8f61118b9a4715b11d640db1d1dc91d86e4a871f4657697ee2e1d"

do these container IDs have anything in common? are they from same failed/exited container?

@redbaron I don't know what those containers IDs are from, there was no obvious mention of them in journalctl since boot. The 60s clean-up errors were always dockerd errors, and that list grew when the rkt task was repeatedly failing. I have no clue how/if they are related. It may be a red herring; I don't actually know the growing clean-up errors are behind the growing CPU load. I just know that taint-and-uncordon failing continuously is bad news for the stability of my controller nodes :-)

I'd rather like to avoid rkt here so that we can completely solve this issue until it is fixed in rkt v1.22.0 via https://github.com/coreos/rkt/pull/3486.

Agree, best to avoid rkt until that gnaly issue is fixed.

Suggest '-vxec' for better error handling and to avoid uncordoning an untainted node by mistake if the taint command throws an error (as happened with the '=' typo).
Suggest '--overwrite' just in case of a re-run due to the uncordon throwing an error the first time or some other error (as happened with the rkt task).

LGTM. Thanks to all for your contribution! :bow: @redbaron @artushin @whereisaaron @reiinakano

Quick question, but could I pull in this new merge and do kube-aws update without having to rebuild my cluster? Sorry, don't really understand the internals of kube-aws

@reiinakano Yes, it is designed to work in this case. However please beware of the fact that it isn't strictly tested with every combination of changes. Could you mind taking a look at the "full update" (which is your case) section of the relevant kube-aws doc for more info regarding what kind of updates kube-aws is intended to support and how.

Also note that if you had not yet enabled experimental.nodeDrainer and correct grace periods for your pods with enough replicas, you may encounter some down-time. kube-aws does replaces your nodes one-by-one hence you have to teach kube-aws, your kubernetes cluster and your pods how to tolerate single node replacement.

I see. Thanks @mumoshu !


Header

beautiful

Looks good. If this was a longer project I'd nag you to run Prettier on it though and remove the curly brackets around the image srcs.


https://pennydreadfulmagic.com/charts/cmc/7773-cmc.png went berserk

LOTS of graphs look like this right now and are presumably cached forever in that state. We should clear them, clear Briar_Moss's "racist" deck where the cards changes, work out what causes this and fix.

Put in some hackery to check the file size of the graph before deciding whether to display or regenerate which is a proxy for "didn't get fully generated". Added some warning-logging so we can see how often this happens on prod. 59aadb63.


Remove "off" position from switcher in Settings "show amounts in"

Please, remove off position from this switcher
it should be only USD/BTC

related to https://github.com/BeamMW/beam-ui/issues/587

please, compare design with https://github.com/BeamMW/beam-ui/issues/595

Checked


Enable packaging at https://packager.io/gh/pkgr/statsd

This pull request enables automatic packaging of statsd for Debian/Ubuntu/CentOS/RHEL using packager.io. The packages come with init scripts and a facility to install additional npm modules if needed.
Example installation instructions at https://packager.io/gh/pkgr/statsd/install?bid=15#ubuntu-14-04-statsd

thanks for the contribution!


Add icon.editable to show icon when content is editable

Coverage decreased (-0.1%) to 75.422% when pulling 3b99d8f71376c2c1419a4b31c8e167acc33b6551 on bry4n:add-editable into 7f1312d496d62270a42a7871efd60aee935784f2 on nickburns2006:master.


Add check if EXERCISM_PRETTIER_VERSION matches prettier in package.json #1196

Issue #1196
Include check in the PR pre check to validate if ENV EXERCISM_PRETTIER_VERSION matches prettier in package.json, if not, set version in package.json to ENV.

@laulujan Great start. You could check out your change by changing package.json in the root to 2.3.0. It should then log your message in the "pre-check" job.
However, this updates the environment to be "correct", but it won't use the correct version when running the format workflow. Instead of "fixing" it, it's probably best to blow up (error), and/or post a comment to the PR that the version mis-matches.

Thanks, @SleeplessByte I committed a change that includes a message if the versions don't match, I also included a regex to compare only the version without the compatibility character, let me know if I understood correctly or if I still need to add something!

Great!
Now all we need is throwing an error instead of commenting, so that it surfaces on PRs :). After you've made that change, we can try it out.

Thanks @SleeplessByte I included the error in the new commit, let me know what you think!!

Alright. Onto the next thing.
Currently it's checking the current environment (so the environment of when pr.ci.yml runs). However, EXERCISM_PRETTIER_VERSION is only set on a step in action-format.yml and verify-code-formatting.yml. We therefore can't rely on env to read this value.
What it needs to do is:

Read out both values (action-format.yml and verify-code-formatting.yml)
Check each of those instances

The rest is looking good :)

Thank you @SleeplessByte , I was wondering, is it ok if I  add https://github.com/nodeca/js-yaml as a dependency to read the yml files? Or do you know another approach I can take to read those files? Thanks in advance!!

Yeah, we can guess here and read the source files as text (using node's regular fs). Why? Well, yes, we could parse the .yml file, but we are really looking for EXERCISM_PRETTIER_VERSION: x.y.z. We know that that doesn't appear anywhere in those files except for the "right place".

"But @sleeplessbyte, what about the future?"

Good point. When someone else adds another instance of EXERCISM_PRETTIER_VERSION, for example as a comment, your check will throw an error, and it will be up to that person to fix it ;).
So in short: read the file as text, search for the value by parsing it as text, for example using regular expressions.

Great, thank you for your guidance, I included the changes in my latest commit, let me know what you think!

@laulujan I've converted your idea and combined it with changes we have in https://github.com/exercism/javascript-test-runner among other repos. Thank you so much for working on this, it was the basis of those changes.


Add proxy arguments to operator image build

Can you please put the integration tests result on the PR description.

The acceptance tests run automatically, here: https://build.weblogick8s.org:8443/job/WebLogic Kubernetes Operator Kind/job/PR-4083/1/display/redirect


Add contents to ReadMe

Coverage remained the same at 70.32% when pulling f9a157bf95615e601d0ca6006f4fa47d3c020f36 on readme into d6286578e054ab8e41f3533329ba51ee72d98b99 on master.


Display year with type 'datetime'

Ask your Question
The mode date displays MM/DD/YYYY as options. datetime displays day+month/hour/second/am+pm. I am interested in displaying the year too, which is available on Android but not iOS. Ideally, day+month/hour/year, though any complete date-time with year would work too.
Is this level of customisation available in the library?

Is this level of customisation available in the library?

Nope, but you can probably look into the community datetime picker (that is being used under the hood by this library) 👍

Great, thanks for the prompt reply @mmazzarolo and your hard work on the library!


enable fuzzing on armhf

This fixes issues with targeting a 32 bit armhf machine.
I notice before a user was testing on their Raspberry Pi Zero. Should armhf be a separate target?
sys/targets/targets.go: Bump armv6 to armv7 in arm target to enable compilation for armhf architecture.
pkg/host/host_linux.go: When running an unsupported architecture for kallsyms parsing, return instead of panic during kallsyms support check.

I notice before a user was testing on their Raspberry Pi Zero. Should armhf be a separate target?

Hard to say. We have limited info as to how people are using syzkaller for arm.
@xairy Will ARMv7 work for your devices?
If yes, I guess we can go with this for now. Until somebody will complain and explain.

pkg/host/host_linux.go: When running an unsupported architecture for kallsyms parsing, return instead of panic during kallsyms support check.

This is not OK. The check is there to notice new unsupported archs. If we comment it out, we won't notice that an arch in unsupported and won't add necessary support.
Instead we need to properly support arm there.
@xairy you had something for kallsyms format testing? Where is that? We need to start collecting per-arch fragments, or the parsing will break.

Codecov Report

Merging #1104 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1104      +/-   ##
==========================================
- Coverage   67.28%   67.28%   -0.01%
==========================================
  Files         119      119
  Lines       20617    20619       +2
==========================================
  Hits        13873    13873
- Misses       6085     6087       +2
  Partials      659      659

Impacted Files
Coverage Δ

pkg/host/host_linux.go
50% <0%> (-0.26%)
:arrow_down:

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 dfd3394...faaecca. Read the comment docs.

I notice before a user was testing on their Raspberry Pi Zero. Should armhf be a separate target?

Hard to say. We have limited info as to how people are using syzkaller for arm.
@xairy Will ARMv7 work for your devices?
If yes, I guess we can go with this for now. Until somebody will complain and explain.

No, Raspberry Pi Zero uses armv6, so compiling for armv7 will likely break.
@Codysseus Isn't armv7 supposed to be backwards compatible with armv6? Why do you need to compile for armv7?

pkg/host/host_linux.go: When running an unsupported architecture for kallsyms parsing, return instead of panic during kallsyms support check.

This is not OK. The check is there to notice new unsupported archs. If we comment it out, we won't notice that an arch in unsupported and won't add necessary support.
Instead we need to properly support arm there.
@xairy you had something for kallsyms format testing? Where is that? We need to start collecting per-arch fragments, or the parsing will break.

I'll send a PR soon.

@xairy I intend to target armhf which is armv7+, so I can't just use armv6.

@Codysseus I still don't get it. The code compiled for armv6 should run on armv7. Is this correct?

@xairy Yes. However I encountered issues compiling for arm. In sys/targets/targets.go, the arm target uses arm-linux-gnueabihf- which I intend on using, but causes the following errors on compilation:
/usr/arm-linux-gnueabihf/include/c++/7/ext/type_traits.h: In function ‘bool __gnu_cxx::__is_null_pointer(std::nullptr_t)’:
/usr/arm-linux-gnueabihf/include/c++/7/ext/type_traits.h:162:35: sorry, unimplemented: Thumb-1 hard-float VFP ABI
__is_null_pointer(std::nullptr_t)
                                ^

If this is to workaround some toolchain bug, then exporting CFLAGS with necessary flags may be the right workaround. CFLAGS=... make should work and CFLAGS should be added at the end, so override previous flags.
We don't respect CFLAGS in pkg/csource/build.go at the moment. But I think we should.

Well, arm-linux-gnueabihf- builds for armhf, so I don't think it's a toolchain bug. If the arm target is staying with the same arm version, line 159 in sys/targets/targets.go should be changed to arm-linux-gnueabi-.

If the arm target is staying with the same arm version, line 159 in sys/targets/targets.go should be changed to arm-linux-gnueabi-.

Are there any downsides to this? @xairy will it work for your devices?

I've realized that I actually couldn't figure out the right way to cross compile syz-executor for Raspberry Pi Zero (I think it required some of the linked libs to be built for armv6, which my toolchain didn't have), so I had to switch to native on-the-board compilation. So I don't mind any changes done to CrossCFlags and CCompilerPrefix, however I think CFlags should remain at armv6.

Great, so I will change this PR to only modify the CCompilerPrefix. Is the arm kallsyms parsing problem going to be solved in another PR?

Great, so I will change this PR to only modify the CCompilerPrefix.

Merged.

Is the arm kallsyms parsing problem going to be solved in another PR?

@xairy added the test:
https://github.com/google/syzkaller/commit/1ee782d53c445be1996975e1c7fd2b7bb063d4b7
Please add a similar test with a kallsyms sample from your kernel and a proper regexp to extract syscalls.


CI for Node

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not

Running - and failing - workflow
The workflow ran! But it failed 😭. But, that's OK. Every time CI fails, it's an opportunity to learn from what's causing it. By running CI with GitHub Actions, we have access to the logs for the attempted build. These are found:

In the Actions tab
In the merge box for this pull request, by clicking on "Details".

If you navigate over to the build logs, you may notice that the error is "No tests found".

Learning how to read build logs and isolate the cause of the problem is an art on its own. We'll try and cover some of the basics here. In our case, the source of the error is the npm test command. The npm test command looks for a testing framework. We want to use Jest, as we mentioned earlier. Jest requires unit tests in a directory named __test__. A __test__ directory doesn't exist on this branch.
Step 3: Add your first test
Not to worry, I've got you covered! Navigate to the open pull request titled Add Jest tests and merge it into this branch. That'll get us the test files we need. I'll respond when you merge the Add Jest tests pull request into this branch.
⌨ Activity: Add your first test script for CI to pick up

Navigate to the open pull request titled Add Jest tests
Merge the pull request

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not


Workspace customization

Support a custom display text.


Where to find documentation on plot- and style-options of various hv Elements & backends?

From the user guide on http://holoviews.org/user_guide/Customizing_Plots.html:

on style options: For whichever backend has been selected, HoloViews can tell you which options are supported[...]
on plot options: HoloViews documents these options fully in its online help and in the Reference Manual .

Where, how :)? E.g. hv.help(hv.Curve) does not list them. The Reference Manual doesn't seem to list them either (at least not directly?).

hv.help should list them once the hv.extension() has been loaded, initializing the active backend.

Perfect, thanks. I saw now that the FAQ mentions the general hv.help(obj)-pattern as well, but I'd vote for adding basically your comment as close as possible to the sentences I quoted above. I can do a quick doc PR for that if you want?

Yes that would be great, thanks!


Reduce public methods in LCM

This PR is ready for review.
Summary

Changed API calls to ISDL instead of LCM
Added request listener calls to ISDL
Create instance of ISdlConnecitonListener instead of LCM implementing to further reduce public methods

CLA

[x] I have signed the CLA

Codecov Report

Merging #1000 into feature/sdl_java_base will decrease coverage by 0.04%.
The diff coverage is 0%.

@@                     Coverage Diff                     @@
##             feature/sdl_java_base    #1000      +/-   ##
===========================================================
- Coverage                    45.13%   45.09%   -0.05%
  Complexity                    3613     3613
===========================================================
  Files                          433      433
  Lines                        20131    20134       +3
  Branches                      2157     2157
===========================================================
- Hits                          9087     9079       -8
- Misses                       10603    10616      +13
+ Partials                       441      439       -2

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/smartdevicelink/proxy/SdlProxyBase.java
6.52% <0%> (-0.01%)
16 <0> (ø)

...smartdevicelink/encoder/VirtualDisplayEncoder.java
24.43% <0%> (-4.55%)
8% <0%> (ø)

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 e1e6c0a...cf83e80. Read the comment docs.


Lab 1 - The tests are located in test.spec.js instead of test.js.

https://github.com/HOGENT-MLOps/mlops-labs/blob/720a1c33d6252e9660abd7b7e19149007ecc1b50/assignment/01-docker.md?plain=1#L128C8-L128C8

This is fixed in https://github.com/HOGENT-MLOps/mlops-labs/blob/04ae7c443fd66129777b383074d610321e6e2590/assignment/01-docker.md?plain=1#L130


Update MD file on new branch 2017-25-14_15-11-09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Implement Skeleton Loading Screens

Right now, when Zap is loading for whatever reason, we have this gradient animation with our bolt. I actually think it looks pretty cool but there are much bigger UX wins to be had.
An obvious one is skeleton loading screens. Through various studies that have proven to be much more effective at reducing the cognitive load for users, keeping users engaged and reducing the rate at which users leave the application.
To implement them for starters, here are the below images:

The screens should be animated as if it's going from light to dark. Also, I'd like to use this issue to highlight the other Zap UIs that will need skeleton loading screen designs. Channel UI? Anything else?

Some work was done on this a while back in https://github.com/LN-Zap/zap-desktop/pull/2413 although the approach there was to show the skeleton items when the activity list is empty (ie, after new wallet creation) where as I think the intention here is to show it whilst the app is in a loading state.

Skeleton screens are very useful when the app takes a while to load resources or fetch data. In my experience Zap is pretty zappy and I never have to wait for stuff to load. I'm wondering what areas of the UI would benefit the most from this.

Closed via https://github.com/LN-Zap/zap-desktop/pull/2879

Weird thing is that this change made me perceive the loading process to be slower than it previously did even though it's not actually slower. It could be that it's just me though.


Sign in with Apple works -- all 5 sign-in methods work.

Eliminated some unneeded import jquery boiler plate.

👍


Upgrade logback_classic and slf4j to version to 1.5.6

Hey Terry, just FYI: https://github.com/ausaccessfed/rapid-idp/issues/1452#issuecomment-2262141566
/opt/idp/jetty/lib/logging/slf4j-api-2.0.6.jar
/opt/idp/jetty/lib/logging/logback-classic-1.5.6.jar
/opt/idp/jetty/lib/logging/logback-core-1.5.6.jar
/opt/idp/shibboleth-src/shibboleth-identity-provider-5.1.3/webapp/WEB-INF/lib/slf4j-api-2.0.13.jar

Upgrade the following jars that are used by the installed:

jcl-over-slf4j-2.0.16.jar
logback-classic-1.5.7.jar
logback-core-1.5.7.jar
spring-jdbc-6.1.12.jar


Graduate 'DisallowInsecureCSRUsageDefinition' to GA (part 2)

In https://github.com/cert-manager/cert-manager/pull/6927, we graduated this feature in the webhook.
However, that PR did not include graduating this feature in the controller and removing the deprecated code.
That is what this PR does.
Kind
/kind cleanup
Release Note
Graduate the 'DisallowInsecureCSRUsageDefinition' feature gate to GA. (part 2)

/retest


Animated webp

Is animated webp supported? I'm uploading this image but I only get a still?

Hey @marcuslindblom! Did you set IMGPROXY_MAX_ANIMATION_FRAMES?

@DarthSim oh, nope. I thought that one was for videos 😀
What value can you recommend?

IDK, it depends on your case, the RAM you have, the time you're ready to wait for the image to be ready, and stuff. I've seen GIFs with up to 300 frames and theoretically, this is not a limit. Yet most animated images have fewer frames. So there's no silver-bullet value for this config. Some set it to 999 meaning "I don't care, just process everything".

Ok, I'll do some experiments.


add ARE instructions to README

The "getting started" section of the README is a bit out of date and could do with instructions on using ARE

eg https://forum.access-hive.org.au/t/introduction-to-cosima-cookbook-data-explorer-and-access-nri-intake-catalog/1144#start-are-jupyterlab-session-8

Also related: #322

Also see https://github.com/aekiss/HPC-Data-CFD-2023/blob/main/README.md#start-are-jupyterlab-session


Unity.gitignore ignore meta files for already ignored unitypackages

Reasons for making this change:
Files that are not tracked should not have tracked metafiles.
With this .gitignore I got a lot of

Hi Tymski,
your observation is correct. Due to the blocking of *.unitypackage and because of some Unity Asset Store packages come with .unitypackage files, the related meta file needs to be ignored too. Else, they get added with the first commit and deleted with the next commit done by someone else or after cleaning the repository.
I see two options to solve this:

Either completely remove the "*.unitypackage" line from the gitignore (However, I guess this was already discussed at some point and the decision was made pro adding it to the gitignore at that time, which is fine.)
Or add the *.unitypackage.meta file as Tymski suggests (to provide consistency).

@shiftkey I recommend to accept this pull request or, in case you need more opinions, raise a discussion.


Gravity changer crashes when im trying to use it in 1.18.2

Gravity changer crashes when im trying to use it in 1.18.2 even without any other mods(accept of cloth config and fabric api). It just says: "An unexpected issue occured and the game has crashed. We're sorry for the inconviniance. this crash may be caused by an invalid Java Runtime configuration. Check any custom configuration settings. Exit Code: 1". I already tryed changing following things in fabric.mod.json: "fabricloader": ">=0.11.3" to "fabricloader": ">=0.13.3" and "minecraft": "1.18.x" to "minecraft": "1.18.2" but it still didnt work. any help?

did you make sure you were on java 17?

No i didn't, I'm gonna do that tomorrow when I have access to my pc and tell you how it went

my java version is 1.8.0_321 idk how to check if its 17

Same thing happens to me to

same

i'm a bit late, but a PR was made with this fork that ported it to 1.18.2
until its merged, your best option is to use the fork

You can also use these forks #1 #2


Download always failing?

Select your issue type: (check at least one)

[x] Bug
[ ] Question
[ ] Suggestion
[ ] Other (please describe):

Describe your issue:
Is there any change in 9anime side? because when i tried to download any anime from any server, it always gives me Failed message

i dont know how to get the error message, tried installing in developer mode and checked console log, nothing appears there

Hi this is most likely happening because 9anime added a server query param for the url used to get videos

I will try to find a fix for this asap.

@lap00zza
the problem is more deeper on that
they have encode the token for the grabber url
encoded using client side javascript
from /all.js
$.ajax(e.grabber, {
data: o,
success: function(t) {
i[R](uU, e.subtitle),
t[Xy] ? t[Xy] === di ? r.Ei(xM + sp + di + sp + kE + sp + vP + sp + kH + sp + ST + sp + Qa + sp + jM + sp + fF + sp + n_) : (r.$i(i, t[Xy], t.token),
r.Fi(i, t[Xy])) : r.Xi(i, t[R])
},
error: function() {
iR < 1 ? (i[R](dt, iR + 1),
r.Oi(i, e)) : r.Ei(xM + sp + iz + sp + GU + sp + vP + sp + fF + sp + n_ + Ey + gr)
}
})
},

@grabberboy yup. I was just looking at it via the chrome debugger sometime back. Thing is this decryption happens sometime between onsuccess/oncomplete and before generating the _. But the thing is if I manually step in and trace line by line the decryption function never seems to get called (weird), My best guess is that they put a time duration check during which it can be decrypted.

@lap00zza the time duration is the worst scenario
lets look more on it

My findings till now. I got really tired after being at this for 4 hours. Might take a crack at it again tomorrow. Some of the variables are renamed.
// Tracehelper
window.src = 12
window.fakeSrc = "";
Object.defineProperty(window, "src", {
    configurable: false,
    get() {
        return fakeSrc;
    },
    set(x) {
        console.trace();
        console.log(JSON.parse(JSON.stringify(x)));
        this.fakeSrc = x;
    }
});

/* --- */
// so
// -> ajax call to get link
// -> `success` calls `NI` with the JSON response and the callback `cb`
// -> `NI` calls callback `cb` after 200 ms
// -> `cb` calls `OI` with the epsiode element and `x` (contents of window.src)
//     `x` contains the decoded token and option parameter
// Final observation, js has ~200 ms to decrypt token/option param. IF it gets
// delayed Oi gets called with encrypted token/option.
// ---
// t is the episode element
function success(n) {
    Ni(n, function(x) /*name: cb*/ {
        if(x.error)
            i.Ei("An error occured please refresh the page (ERR 1)")
        else
            if (x.type === "direct")
                Oi(t, x)
            else
                if (x.type === "iframe")
                    i.Ri(x.target)
    })
}

function Ni(i, n) {
    var e = this;
    window.src = i,
    window.srcsrc = !0, /* !0 = true */
    window.setTimeout(function() {
        i = window.src,
        delete window.src,
        delete window.srcsrc,
        n.call(e, i)
    }, 200)
}

// i is the element
// e is the json object
function Oi(i, e) {
    var r = this
      , o = e.params;
    return i.data("apiErrorCount", i.data("apiErrorCount") || 0),
    $[oI](o, {
        _i: t.XTOKEN,
        mobile: n.mobile() ? 1 : 0
    }),
    $.ajax(e.grabber, {
        data: o,
        success: function(t) {
            i.data("subtitle", e.subtitle),
            if(t.error)
                if (t.error === "token")
                    r.Ei("API: token invalid please refresh this page and try again")
                else
                    (r.$i(i, t[Xy], t.token), r.Fi(i, t[Xy]))
            else
                r.Xi(i, t[R])
        },
        error: function() {/*...*/}
    });
}

// second function responsible for decryption
window.setTimeout(function() {
    if(window.src)
        if(window.srcsrc === true)
            window.srcsrc = false;
            window.src = decrypt(window.src)
}, 50);

function decrypt(t) {
    var n;
    if (Object.prototype.toString.call(t) === "[object Array]")
        for (n = 0; n < t.length; n++)
            t[n] = decrypt(t[n]);

    else if (Object.prototype.toString.call(t) === "[object Object]")
        for (n in t)
            if(Object.prototype.hasOwnProperty.call(t, n))
                t[n] = decrypt(t[n]);

    else
        typeof t === "string" && (t = t[0] === "." ? function(t, i) {
            var n, e = [];
            if (i || (i = 13),
            !(i %= 26))
                return t;
            for (n = 0,
            l = t.length; n < l; n++)
                c = t.charCodeAt(n),
                c >= 97 && c <= 122 ? e[n] = (c - 71 + i) % 26 + 97 : c >= 65 && c <= 90 ? e[n] = (c - 39 + i) % 26 + 65 : e[n] = c;
            return String.fromCharCode.apply(vA, e)
        }(t.substr(1), -18) : t);
    return t
}
/* --- */

// notes
// -> _ is calculated from the encrypted token and options

the encryption is rot-8. you have to decrypt all variable values starting with a dot.

strip the beginning dot
do rot-8
done

fore example: in params.token the value starts with a . and options starts with a . (dot) too. if its not a direct link but an iframe, youll see the target starts with a . and has to be decrypted too. thats it, nothing more

@hoppler WOAH thanks so much. I was having trouble identifying. Just tested, it is indeed rot-8.

Not just failing, it doesn't even showed up like "Downloading 001" (select all or just one episode) then all "Done".

good findings but still the ts value is encrypted in unknown method
hope @hoppler can see this too

@Vysair the fix will take some time. There were 2 main hindrances:

Finding the encryption scheme for token/options (which is solved)
Finding the encryption scheme for ts

Once the 2nd one is done I will release a fix for the downloads. (Best guess: within max 2 days)

Here you go
def main():
    expected = "1511690400"
    ts = "YNPxYNX5YGHwYA=="

    firstCharMap = []
    secondCharMap = []
    for n in range(65, 91):
        firstCharMap.append(chr(n))
        if n % 2 != 0:
            secondCharMap.append(chr(n))
    for n in range(65, 91):
        if n % 2 == 0:
            secondCharMap.append(chr(n))

    result = ""
    for i in range(len(ts)):
        charReplaced = False
        for y in range(len(secondCharMap)):
            if ts[i] == secondCharMap[y]:
                result += firstCharMap[y]
                charReplaced = True
                break
        if not charReplaced:
            result += ts[i]
    import base64
    real_ts = base64.b64decode(result)
    print real_ts
    print "Success" if real_ts == expected else "failure"

if __name__ == '__main__':
    main()

Thanks so much @hoppler . For anyone reading this thread, I will release a fix for 9anime Companion tomorrow.

Can someone please test these artifacts: https://ci.appveyor.com/project/lap00zza/9anime-companion/build/<IP_ADDRESS>/artifacts and tell me if downloads are working for F2, G2 and G3.

Can't wait for the fix ! unfortunately can't help with testing because I'm not at home, but hopefully the issue will be resolved till tomorrow !

Getting this after installing. And download from F2, G2 and G3 still not working.

they update again
token is not in rot8 anymore

Maybe they are spying on us?
I wish i could help but i have been spending too much time watching anime and too little working on my JS skills (i fell bad for it).
Anyways, thank to everyone working on solving this issue and i hope that i can help in future ones.

https://twitter.com/9animeto/status/933685120539561984
They have said it

Looking at their discord it doesn't seem like they are going to war anyone.

We can only hope that this is only one-time change, and things get stabilize soon.

Well, that discord message dates september and the tweet is from november so it is a little outdated.

Probably because of a misunderstanding. One of my friend who knows the owner told me the owner thinks:

when they enabled the adblock detection I made 9anime Companion not work on purpose

But that is not at all true. It was still working if you disabled Remove Ads and Remove Social Share. But I have no clue why they added detection for social share. Ads I can understand.

Well, i only started to use 9anime a few days ago, it said "we stopped the pop up's please turn off the adblocker" and so  did but now they are using pop ups again, there is no option to donate or pay to turn off this ads. I believe that a better service will make more donators and more people willing to help. A good way to make the service better is to coexist with this extension that makes the website much better.

Well i dont know if this will help us, but i think you should remove the
ability to hide the ads, maybe by doing that, we are showing to 9anime guys
that we dont have intention to hurt their income
leave adblocking to the users, they can use adblock extensions
On Nov 26, 2017 11:53 PM, "SolvingTheWorld"<EMAIL_ADDRESS>wrote:

Well, i only started to use 9anime a few days ago, it said "we stopped the
pop up's please turn off the adblocker" and so did but now they are using
pop ups again, there is no option to donate or pay to turn off this ads. I
believe that a better service will make more donators and more people
willing to help. A good way to make the service better is to coexist with
this extension that makes the website much better.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lap00zza/9anime-Companion/issues/106#issuecomment-347022435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AErDTJxFfSjGlTCqE16b9KRxgVgFhPbyks5s6ZeAgaJpZM4QqVM9
.

I think @awangn6600 is right. You should probably remove the adblock feature. Also, it would be better if you could talk to the admin of 9anime and figure something out. I assure you people would love to have 9anime companion as an official extension for 9anime.

A fix is on the way but if possible can you guys please share your thought about remove adblocker here: https://www.reddit.com/r/9anime/comments/7ftuvp/poll_9anime_companion_remove_ads/

tentative fix for downloads: https://ci.appveyor.com/project/lap00zza/9anime-companion/build/<IP_ADDRESS>/artifacts

Remove Remove Ads from the official build (Chrome Web Store, Addons.Mozilla.Org), but still be available in a separate branch in the GitHub repository so that people can compile themselves.

The tentative fix is working.

Great work, thank you.

@lap00zza rapidvideo removed? i always use rapid video because the download link doesnt expire quickly like google server one
is there any problem with rapidvideo?

@awangn6600 its target link is encrypted as well. I will patch it as soon as I find out how to decrypt.

could you take give me a lead which part of the code to take a look? maybe i can do something about it

@awangn6600 sure. Basically you need to look in a file called all.js. But its encrypted (packed js). So you will need to wait till its decrypted and then check the called lines from the f12 Network tab.

@awangn6600 lets continue the rapidvideo discussion here: #109


Add ability to delete workflow by filename / state

Multiple additions:

Add ability to filter workflows by workflow filename (in addition to the name)
Add ability to filter workflows by state
Add ability to perform a 'dry run' which logs the changes but doesn't perform the actual deletion.

thanks @Mattraks!


v2 release with generic approach

Fixes #41

@Michal-Leszczynski We are all looking forward to merging this pr.

Rather than create a /v2/, I propose with https://github.com/google/btree/pull/45 that we simply create a generic interface as well as the non-generic, backwards-compatible Item interface, and use that for Go 1.18 and beyond to implement the backwards-compatible Item interface.  Thoughts?

Closing as #45 I believe handles this same issue.  If there's any issues with that or it fails to work correctly, though, happy to reopen this.


modules_force_load can be loaded earlier

I'm using modules_force_load for KMS, and booster gives a little dissatisfying result because by the time the mode switch completes my display manager would already have started.
mkinitcpio loads its MODULES "before anything else is done". I think we can do the same, since module loading is performed with a syscall and does not rely on any CLI utilities.

because by the time the mode switch completes my display manager would already have started.

Could you please share more information about the issue you see? Is the problem due to booster gets into userspace before all the modules_force_load completely loaded?
Currently booster loads modules_force_load asynchronously and does not wait for the operation completion. At the time I was implementing it was not clear whether a wait is needed.

mkinitcpio loads its MODULES "before anything else is done"

The "before anything else is done" condition is quite vague and restrictive. One of the booster goals is to get into userspace as fast as possible. And to achieve it booster tries to exploit parallelism as much as possible. If loading modules needs to be done synchronously at the beginning of the booster execution then it limits parallelism a lot.
So instead of "before anything else is done" I suggest to start with "before root filesystem is mounted" condition and see if it works.
Please check wip branch. I just pushed a change that makes booster waiting for modules loading before switching to the new root filesystem. Let me know if it fixes your issue.

I was lying, I thought I regenerated the image but I actually didn't. So I didn't enable modules_force_load.
Now actually trying to boot with modules_force_load: amdgpu, the GPU driver doesn't initialize. I opened #104.
What I originally meant to say is that this line can be moved further up in boost():
https://github.com/anatol/booster/blob/e825838500dabb5d993ca22c1de55b9e65662b9c/init/main.go#L662
Making a few directory probably takes no time and it can run first, but we probably should be loading the modules before setting up the console font. Not sure if this actually makes a difference as I thought though, since I mistakenly assumed when I opened this issue that modules_force_load is configured when it wasn't.
I will fix the symlinks, try again booting, then report back.

Making a few directory probably takes no time and it can run first, but we probably should be loading the modules before setting up the console font.

there are few things that should be done before we load the modules. e.g. starting udev listener should start before we modules loading to avoid missing udev events.
Moving virtual console config after loading modules sounds fine to me.

With 90dd03a it seems that we are already loading things as early as we can, so this can be considered resolved.
I originally thought that 9337bc6 is unnecessary now, but if I revert it then a kernel null dereference happens so let's just keep that for compatibility's sake...
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: [drm:amdgpu_dm_init.isra.0.cold [amdgpu]] *ERROR* amdgpu: failed to initialize sw for display support.
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: [drm] kiq ring mec 2 pipe 1 q 0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: [drm] JPEG decode initialized successfully.
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: memmap_init_zone_device initialised 2097152 pages in 14ms
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: amdgpu: HMM registered 8176MB device memory
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: amdgpu: SRAT table not found
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: amdgpu: Virtual CRAT table created for GPU
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: amdgpu: Topology: Add dGPU node [0x731f:0x1002]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: kfd kfd: amdgpu: added device 1002:731f
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: amdgpu 0000:0a:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 10, active_cu_number 40
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: BUG: unable to handle page fault for address:<PHONE_NUMBER>00ecc8
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: #PF: supervisor read access in kernel mode
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: #PF: error_code(0x0000) - not-present page
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: PGD 100068067 P4D 100068067 PUD 10273f067 PMD 0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CPU: 12 PID: 252 Comm: init Not tainted 5.14.0-xanmod1-cacule-1 #1
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F33a 01/22/2021
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RIP: 0010:get_modes+0xa3/0x510 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Code: f0 b2 ff 84 c0 75 78 ba e0 01 00 00 be 80 02 00 00 48 89 df e8 0e d9 b2 ff 89 83 c8 04 00 00 4c 8b 23 49 8b 84 24 a8 39 01 00 <48> 83 b8 c8 ec 00 00 00 74 14 48 8b 83 d8 04 00 00 81 78 38 80 00
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RSP: 0018:ffffbb690137f6f8 EFLAGS: 00010246
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RAX:<PHONE_NUMBER>000000 RBX: ffff9b9c80f34000 RCX:<PHONE_NUMBER>000000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RDX: ffff9b9c8deba3c0 RSI: ffff9b9c8deba3c0 RDI: ffff9b9c8deba7c0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RBP: ffff9b9c82e3a800 R08: ffff9b9c80f340a0 R09: ffff9b9c80f340a0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R10:<PHONE_NUMBER>00000a R11:<PHONE_NUMBER>00000a R12: ffff9b9c8de60010
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R13: ffff9b9c80f340a0 R14:<PHONE_NUMBER>000003 R15: ffff9b9c80f34000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: FS:  000000c000380090(0000) GS:ffff9b9faed00000(0000) knlGS:0000000000000000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CR2:<PHONE_NUMBER>00ecc8 CR3:<PHONE_NUMBER>d7c000 CR4:<PHONE_NUMBER>350ee0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Call Trace:
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  drm_helper_probe_single_connector_modes+0x1d0/0x860 [drm_kms_helper]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? kfree+0xc3/0x3d0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  drm_client_modeset_probe+0x27f/0x13f0 [drm]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? kmem_cache_alloc_trace+0x169/0x2e0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? amdgpu_driver_open_kms+0xd5/0x200 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  __drm_fb_helper_initial_config_and_unlock+0x44/0x4c0 [drm_kms_helper]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? drm_client_init+0x131/0x160 [drm]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  amdgpu_fbdev_init+0xb9/0xf0 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  amdgpu_device_init.cold+0x1415/0x1af5 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  amdgpu_driver_load_kms+0x67/0x300 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  amdgpu_pci_probe+0x110/0x1a0 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  local_pci_probe+0x42/0x80
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? pci_match_device+0xd7/0x110
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  pci_device_probe+0xfa/0x1b0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  really_probe+0x1e7/0x3e0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  __driver_probe_device+0xfe/0x180
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  driver_probe_device+0x1e/0x90
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  __driver_attach+0xc0/0x1c0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? __device_attach_driver+0xe0/0xe0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? __device_attach_driver+0xe0/0xe0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  bus_for_each_dev+0x89/0xd0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  bus_add_driver+0x12b/0x1e0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  driver_register+0x8f/0xe0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? 0xffffffffc0b1c000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  do_one_initcall+0x57/0x220
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  do_init_module+0x5c/0x260
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  load_module+0x247c/0x2640
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  ? __do_sys_finit_module+0xae/0x110
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  __do_sys_finit_module+0xae/0x110
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  do_syscall_64+0x3b/0x90
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RIP: 0033:0x4a1bbb
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Code: e8 ea eb fb ff eb 88 cc cc cc cc cc cc cc cc e8 bb 2f fc ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RSP: 002b:000000c000418d70 EFLAGS: 00000202 ORIG_RAX:<PHONE_NUMBER>000139
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RAX: ffffffffffffffda RBX: 000000c000035000 RCX:<PHONE_NUMBER>4a1bbb
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RDX:<PHONE_NUMBER>000000 RSI: 000000c000424020 RDI:<PHONE_NUMBER>000008
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RBP: 000000c000418dd8 R08: 00007f6e9dc32d01 R09:<PHONE_NUMBER>000000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R10: 00007f6e76ea1328 R11:<PHONE_NUMBER>000202 R12: 000000c000424020
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R13:<PHONE_NUMBER>000001 R14: 000000c000161d40 R15:<PHONE_NUMBER>000002
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Modules linked in: ext4 amdgpu(+) jbd2 mbcache crc16 aesni_intel crypto_simd ghash_clmulni_intel crct10dif_pclmul crc32c_intel cryptd crc32_pclmul igb xhci_pci xhci_pci_renesas dca drm_ttm_helper drm_kms_help>
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CR2:<PHONE_NUMBER>00ecc8
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: fbcon: Taking over console
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: ---[ end trace 857fbdce8ddca9b5 ]---
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RIP: 0010:get_modes+0xa3/0x510 [amdgpu]
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: Code: f0 b2 ff 84 c0 75 78 ba e0 01 00 00 be 80 02 00 00 48 89 df e8 0e d9 b2 ff 89 83 c8 04 00 00 4c 8b 23 49 8b 84 24 a8 39 01 00 <48> 83 b8 c8 ec 00 00 00 74 14 48 8b 83 d8 04 00 00 81 78 38 80 00
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RSP: 0018:ffffbb690137f6f8 EFLAGS: 00010246
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RAX:<PHONE_NUMBER>000000 RBX: ffff9b9c80f34000 RCX:<PHONE_NUMBER>000000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RDX: ffff9b9c8deba3c0 RSI: ffff9b9c8deba3c0 RDI: ffff9b9c8deba7c0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: RBP: ffff9b9c82e3a800 R08: ffff9b9c80f340a0 R09: ffff9b9c80f340a0
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R10:<PHONE_NUMBER>00000a R11:<PHONE_NUMBER>00000a R12: ffff9b9c8de60010
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: R13: ffff9b9c80f340a0 R14:<PHONE_NUMBER>000003 R15: ffff9b9c80f34000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: FS:  000000c000380090(0000) GS:ffff9b9faed00000(0000) knlGS:0000000000000000
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Sep 21 11:33:20 ishitatsuyuki-ryzen kernel: CR2:<PHONE_NUMBER>00ecc8 CR3:<PHONE_NUMBER>d7c000 CR4:<PHONE_NUMBER>350ee0

Closed by 9047c94a78f182ed274f7abda1ede16c071c0b27


Ask for update

We should not force-autoupdate the application, but ask the user if he wants do download the new update. Not everytime you are connected to the internet you want to download a 54 MB application without knowing. And if an application update has a major problem, users can simply download an older version of the app.
(on macOS: What about using the same pattern as the Mac App Store deals with updates? macOS Update

I think the easiest and quickes solution would be to just add a yes and a no button to the dialog that informs you about the update. Would that be a good first step?

Yes, of course. Let’s start with that and extend it later.


Intial Commit of Server and Client:Connecting React FrontEnd, Node and E…

Connecting React FrontEnd, Node and Express Backend and Postgres Database

@ecunnin2  You are right about the src/components folder. I will add that in a follow up commit

Sounds good

Sounds good


Error when starting Tabmon Services after installing on Tableau server

I installed TabMon on the Tableau Server and the config is as below. I did not install and initialize PostGres as its already installed for the tableau DB accounts:

The Error from my logs are as below:
2017-08-07 12:30:41,777 [5] INFO TabMon.Config.TabMonConfigReader - Loading TabMon user configuration..
2017-08-07 12:30:41,808 [5] DEBUG TabMon.Config.TabMonConfigReader - Loading database configuration..
2017-08-07 12:30:41,808 [5] INFO TabMon.Config.TabMonConfigReader - Connecting to results database..
2017-08-07 12:30:43,870 [5] FATAL TabMon.Config.TabMonConfigReader - Could not initialize writer: Failed to establish a connection to 'localhost'.
2017-08-07 12:30:43,870 [5] DEBUG TabMon.Helpers.HostnameHelper - Successfully resolved 'localhost' to 'ckt-qa-iftab-02'.
2017-08-07 12:30:43,870 [5] FATAL TabMon.Config.TabMonConfigReader - Invalid options in configuration: [Host='Primary\ckt-qa-iftab-02', Writer='null', PollInterval='30', TableName='countersamples']
2017-08-07 12:30:43,870 [5] INFO TabMon.TabMonAgent - Initializing TabMon..
2017-08-07 12:30:43,870 [5] FATAL TabMon.TabMonAgent - Invalid TabMon options specified!
Aborting..
2017-08-07 12:30:43,870 [5] FATAL Topshelf.Runtime.Windows.WindowsServiceHost - The service did not start successfully
Topshelf.TopshelfException: The service did not start successfully (returned false).
at Topshelf.Runtime.Windows.WindowsServiceHost.OnStart(String[] args)

Hello,
Is TabMon on the same machine as Postgres? Could you attach your TabMon config to this issue?
Thanks,
Dan

Closing this due to lack of activity.


[requires.io] dependency update on master branch

Coverage remained the same at 100.0% when pulling 77459a46f3eeec5765c41d321d60df6a1549376f on requires-io-master into 9639168a56e8d4f3be2f666a74eec3596223b0b2 on master.

Coverage remained the same at 100.0% when pulling ec892f2a81f7df5ee930e20545ffa7a3bba8fff2 on requires-io-master into 9639168a56e8d4f3be2f666a74eec3596223b0b2 on master.


First-person camera position/rotation offset

One pretty critical feature that I've missed when going from CameraPlus to Camera2 is the ability to change the positional and rotational offset relative to the HMD center. This is particularly bad for me because I tend to rotate my HMD upwards unintentionally on more strenuous maps, leading to an uncomfortable viewing experience.
I've tried looking all over the wiki and config files and I can't seem to find anything — I don't think this would be too hard to implement, though.

You can edit the targetpos and targetrot in the config file. Only the targetpos' z value is exposed in the settings UI because having all values there would clutter the UI quite a bit as well as being of no use to most.
https://github.com/kinsi55/CS_BeatSaber_Camera2/wiki/Camera-Configuration#targetpos--targetrot

Interesting. I had tried changing it, but it must have not worked without a restart. Either way, this issue has been solved. Thanks!


[ci] parallelize R package installs in CI jobs

This week, @jnolis taught me that the R function install.packages() can support parallel package installations! That function supports an argument Ncpus. If set to a value greater than 1, R will install multiple packages at the same time.
See https://stat.ethz.ch/R-manual/R-patched/library/utils/html/install.packages.html for more.
This PR proposes setting that argument to the value of parallel::detectCores() in this project's CI jobs and documentation of how to run them manually. I think this should reduce the time it takes R CI jobs to run, especially on Linux where CRAN does not prepare precompiled binaries. {parallel} comes installed in all standard installations of R, so this does not introduce a new dependency for LightGBM's CI jobs.
Windows and Linux runners from GitHub Actions have a single 2-core CPU and macOS runners have a single 3-core CPU: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources.

 It's hard to get an accurate estimate of the timing for these things because so many factors impact runtime of the CI jobs, including the response times and availability of multiple package managers.
But it does look roughly like what I'd expect...this change seems to offer a noticeable speedup on Linux (where R packages have to be installed from source) and only a small speed up (if any) on Window and macOS (where CRAN provides binaries).

/gha run r-solaris

/gha run r-valgrind

What about static_analysis workflow?

Ah yes, you're totally right, thank you. I'll add this to that job as well.


WebSocketClient does not connect

After updating to version 2.0.14 I cannot connect via WebSocketClient.
I checked the cause of the problem:

the WebSocketClient start() function is not called. Previously, it was called at the end of subscribe()
So this should be corrected, or the start() function should be made public.

fix: https://github.com/terra-money/terra.js/commit/998fdfbaabee7d81176d3d2bb377ea0a5dfb61d0


My app refuses to open with start button

I've added all the dependencies and started moving a bit of code over to get this working in my app, however when I try to add this code:
Center(child: StartButton(nextScreen: SecondScreen())),
To my app's sign in screen, it will not open, without any reason in output
Launching lib/main.dart on iPhone SE (2nd generation) in debug mode...
Xcode build done.                                           16.7s
Connecting to VM Service at ws://<IP_ADDRESS>:59244/sUqI-ad52vQ=/ws
Lost connection to device.
Exited (sigterm)

Were you able to run the example app?

Yes the example app runs fine

@BermyToiga The plugin has been modified to have only the authentication flow. Can you please try again?

Seems to work now, thanks!
On Thu, Nov 26, 2020, 6:58 AM Sarika<EMAIL_ADDRESS>wrote:

@BermyToiga https://github.com/BermyToiga The plugin has been modified
to have only the authentication flow. Can you please try again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atsign-foundation/at_widgets/issues/1#issuecomment-734229564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF2I3I5XJWKLXX6QTCUMLJDSRYYERANCNFSM4UBJC7MQ
.


fix(network): give up a peer without log a reason

What this PR does / why we need it:
Add warn log before give up peer
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:

/lgtm


Rocko backports

Two backports from master for the rocko branch to fix issues I ran into.

Can one of the admins verify this patch?

add to whitelist

ok to test

@koenkooi this PR looks to be created against master. Didn't you want to do it for rocko?

Yes, I forgot to select the right branch, sorry about that, should be fixed now.

Thanks @koenkooi


Thanks before even starting rapid review

I noticed that the "Thank you for your contribution!" message is present even if I haven't started a review.

Yes, this was part of the wireframes and includes an ask to review the code of conduct. Is this no longer desired, or should it be changed or moved?

Agreed to remove only the first sentence, "Thank you for your contribution!"


[BUG] Support for<EMAIL_ADDRESS>

Bug report
Report for: Lucia
Since cookies can only be set using cookies instead of setHeaders, cookies array returned from auth methods cannot be easily set.
Additional info
Version
v0.8.3
Reproduction
none
Additional notes
release notes

Fix planned for v0.8.4

This will be addressed by providing setCookie method, which takes SvelteKit's cookie api and n number of cookie strings.
const user = await auth.createUser()
setCookie(cookies, ...user.cookies)

fixed with #72 (v0.8.4)


python3Packages.txtorcon: disable tests on aarch64-darwin

Motivation for this change
Build failure on aarch64-darwin: http://ix.io/3Nqi
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 156623 run on aarch64-darwin 1

4 packages built:

magic-wormhole (python39Packages.magic-wormhole)
python310Packages.magic-wormhole
python310Packages.txtorcon
python39Packages.txtorcon

Result of nixpkgs-review pr 156623 run on x86_64-darwin 1


chore: Resolve some Sonar findings

use String#replace() instead of String#replaceAll where no regexp replacement is needed
use instanceof with variable assignment
changed some string concatenation findings

Will open later again


Only works in HTML documents

Make sure to use the HTML namespace by doing doc.createElementNS("http://www.w3.org/1999/xhtml", "whatever") in your code. Also, instead of using div, you might want to use _, as it might confuse users who look at the script and think that using div is significant.

hello from the future of awesome web browsers! it this still relevant? :)


Fixed title underline

Coverage remained the same at 96.045% when pulling dfc02c02838e33a710d55ac35414fa8a41f1b8d5 on andy/fix-title into dede006bb22f799457e655be911f033b8e15af53 on master.


[Container Cert] Container can be launched successfully with SELinux  and CGroups enabled

Container can be launched successfully with SELinux  and CGroups enabled on the underlying RHEL host

@tonytcampbell is there already an existing check that does this ? Was hoping to get a bit more background on this. Does this imply essentially ensuring if the appropriate SCC is in place ?

I can take this one.
/assign

Hi @tonytcampbell,
I was looking at this issue and trying to find out what kind of test can be run here.
The thing is SELinux labels are enforced by the container runtime spinning up the container in order to separate containers from other containers including the host file system. This is not attached to the image itself. If the entry point for a specific image, command or script, requires access beyond what is allowed it will get a permission denied at the LSM (Linux security module) layer and will generate an AVC (access vector cache) message that can be tracked down on the host with proper permissions. My question is if catching those errors from the system would be a valid test in the certification context. To increase security though it's definitely not necessary to test it, because SELinux is a Linux feature itself and has its own tests. The system will break the command trying to trespass its perimeter. If the deployment needs to use a different SELinux label, context etc. then SCCs and other mechanisms on deployment must be put in place by the administrator of that system. So I really would appreciate to have conversation with the engineers that requested this test to understand what they have in mind. I think I'm missing something.
On the cgroup side, which is a completely different thing from SELinux I don't see a test at all. All containers will be registered in specific cgroups no matter what the image says. That's on the system/runtime not the container image. How could a container image not work with cgroups? That I don't get it. Besides that, if there is a reasonable use case here it should be another issue. Those 2 features are completely unrelated. Again, I'm really curious about this and would be glad to pick the minds behind this issue and have a nice chat.
Always happy to help. Let me know what I can do.

Closing this issue due to no activity, please open a new issue if needed.


Fail to pull singularity image in HPC environment

I am running dev reomtely in a HPC cluster.
Meaning, I do not have superuser authorization and I need to rely on singularity.
First, I load the singularity module with all dependencies:
$ module load autoload singularity/3.2.1

Then I try running the test case, but it fails because it is unable to access the singularity image
$ ./run_nextflow_test.sh
[...]
Error executing process > 'output_documentation'

Caused by:
  Failed to pull singularity image
  command: singularity pull  --name metatdenovo.simg.img docker://metatdenovo.simg > /dev/null
  status : 255
  message:
    [34mINFO:    Starting build...
    FATAL:   Unable to pull docker://metatdenovo.simg: conveyor failed to get: Error reading manifest latest in docker.io/library/metatdenovo.simg: errors:
    denied: requested access to the resource is denied
    unauthorized: authentication required

Even building the image through singularity is no good:
$ ./build_singularity.sh
INFO:    Starting build...
FATAL:   While performing build: conveyor failed to get: Error loading image from docker engine: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Singularity runs normally after loading the modules, same for nextflow:
$ singularity version
3.2.1
$ nextflow -version

      N E X T F L O W
      version 20.04.1 build 5335
      created 03-05-2020 19:37 UTC (21:37 CEST)
      cite doi:10.1038/nbt.3820
      http://nextflow.io

I am not sure if the problem is related to my local HPC settings or the settings of the image.

The workflow is under development, so nobody built and uploaded an image anywhere, you'll have to do that yourself. There are scripts in the repo to do this. First you need to build a Docker image and, since you don't have root on the cluster, you'll have to do this on another computer where you have root access. It's probably easiest to build the singularity image there too so you don't have to upload the Docker image anywhere.


Added parenthesis check around "document" elements and fixed non-existent document.window filter to window.document

document.cookie and document.write are filtered but can easily be evaded by (document).cookie and (document).write.
Also the $_never_allowed_regex checked for document.window which is always undefined and won't work.
It should be window.document.

That's cool, but parts of your patch only add parentheses without preserving the old checks.
Also, we have private channels for security-related stuff.

I'm not sure if i understand you correctly but the old checks are preserved.
I added the parenthesis \(?document\)? with the ? modifier so they are optional, preserving the old check.
For this check:
'(\(?document\)?|\(?window\)?(\.document)?)\.(location|on\w*)',

the old behavior is changed but that is the point, the old behavior was invalid.

My bad, I didn't notice the ? modifier.


Output video is not cropped correctly

My preview layer is the full size of the iPhone 6 screen. However the video produced is of an aspect ratio slightly different and doesn't fill the screen.

I had the same problem and found a fix. It has to do with setting the AVCaptureSessionPreset. The default is set to AVCaptureSessionPresetPhoto in the _setupSession method around line 1116. For some reason calls to setCaptureSessionPreset does not actually change it. The method is ran but [_captureSession canSetSessionPreset:captureSessionPreset] returns NO. To fix this change the line sessionPreset = AVCaptureSessionPresetPhoto; where I previously mentioned to whatever preset you desire. AVCaptureSessionPresetHigh should work.

thanks, we've got a bug tracking this
:paperclip: https://github.com/piemonte/PBJVision/issues/74


Location Tool: Subtracting/Excluding a Shape on a Blank Map, Adds it

Bug
Clicking "Exclude" on pre-loaded shape still adds it on a blank map.
To Reproduce
Steps to reproduce the behavior:

Go to  /locations/new
Search for a location, like "Colorado." Select it.
Instead of adding, click "Subtract"
Error: The shape is added.

Alt:

Go to /locations/new
Create a custom shape.
Instead of adding, click "Subtract"
Error: The shape is added.

Expected behavior
Clicking "Subtract" on a blank canvas should have the same effect as cancelling the action.
Screenshots
Desktop (please complete the following information):

Win 10, FF 72

Approved.


Allow to disable colors

This adds options to handle color in output, as mentioned in #425.
Two environment variables allow to alter the coloring:

CLICOLOR defaults to 1 and can disable coloring
CLICOLOR_FORCE defaults to 0 and bypass tty checking

This follows the logic from https://bixense.com/clicolors/ although there is no real standard ruling color options.
A new dependency was added: atty, to check if we are in a tty (and avoid coloring output when piped).
I don't find my current handling of coloring flag in error/success/info functions really elegant, do not hesitate to suggest a cleaner way to do it.
For now I did not replace term_painter, but it does not seems to play well with the CLICOLOR_FORCE option. Switching to termcolor is the next step.
TODO:

[x] replace term_painter by termcolor

Neat thanks!
Can you also add support for NO_COLOR (http://no-color.org/) so we cover all usecases?
@ianare are you fine with env variables rather than a flag?

Great, thanks! I'm OK with the environment variables, since by default the output will not be colored when piped.

Nice! Can you also update the docs (getting-started/cli-usage.md)?

Oh sure, I'll take a look at the doc.

I added a paragraph in cli-usage page, let me know if there is anything else.

I feel like get_color_choice (and has_color for that matter) could be converted to a static? Whilst it's not necessarily heavily computational, it is done every time something is logged, when the value will never change at runtime.

Thanks!


Added deployment.rst to provide usage instructions

For facility e4s deployments

@wspear i added a few notes about Perlmutter. I think you should write the user documentation from perspective of new user that has no knowledge of what is PErlmutter, NERSC, etc... In that case providing some context for the system would help.

I am merging this in. Thanks @wspear.


[incubator/cassandra] Add pod anti-affinity

It seems to be important to runs Cassandra' pods which won't be co-located, especially in a production environment. In this PR is my proposal to add an option to use pod anti-affinity.

/ok-to-test

/assign

I'd suggest you go for this approach which is more flexible:
https://github.com/kubernetes/charts/blob/ea5e1a13bb3f75f1102bf59ff0ab8e44cde716f4/stable/kibana/templates/deployment.yaml#L45-L48

It seems it's already done in PR #3892


localstack: 3.0.0 -> 3.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/localstack/versions.
meta.description for localstack is: A fully functional local Cloud stack
meta.homepage for localstack is: https://github.com/localstack/localstack
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.2 with grep in /nix/store/z9x1rnm1hdnnc1c8bq10yfanw44zzrg7-python3.11-localstack-3.0.2
found 3.0.2 in filename of file in /nix/store/z9x1rnm1hdnnc1c8bq10yfanw44zzrg7-python3.11-localstack-3.0.2

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
localstack
python310Packages.localstack
python311Packages.localstack

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/a7bdd70631f4c9ea6f19fa8d60a4b5685971dc58#localstack

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

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

2 packages built:

localstack (python311Packages.localstack)
python310Packages.localstack

Maintainer pings
cc @jonringer for testing.

Already on staging-next.


UWP Pedometer.GetDefaultAsync()

On Nokia lumia 929 Pedometer.GetDefaultAsync() always returns null. Is this device unsupported ? Cause i can use pedometers from store, so device can check steps

This is a question about device platform support, not a question about the sample. You can open a support case with our Developer Support team who can further help with the specific problem you are experiencing. Please use these steps below for further help:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.


feat(color): Add support for 8 CSS hexcolor values (#RRGGBBAA)

#RRGGBBAA hexadecimal color notation supported by Chrome, Firefox
#306

Thanks @beautyfree! I will take a look at this, this weekend.

Closed in favor of #318


Make possible to start Peon without DI loading of any querying-related stuff

There are three steps:

Depend on QueryRunnerFactoryConglomerate lazily in TaskToolboxFactory
Extract QueryablePeonModule with the querying-related stuff loaded on Peon currently
Generalize druid.extensions.moduleExcludeList config as druid.modules.excludeList to be able to filter not only modules from extensions, but also "core" modules.

Putting into 0.10.1 because druid.extensions.moduleExcludeList was added just in this version, to avoid compatibility problems with removing some configuration that was added just in the previous version. Also the lack of this feature may be blocking for other people who run Peons with Spark/Hadoop tasks.

@leventov does this really need to be in 0.10.1?

@fjy if not druid.extensions.moduleExcludeList will appear in a released version, that is better to avoid. Plus we were not really able to run some Spark tasks without this PR, so not including it may be blocking for some users.

Would you elaborate on how DI of querying-related stuffs blocks peons from running with Spark/Hadoop tasks?

@jihoonson it's because we include our own extensions with configuration options, that are included for realtime peons, and so sneak into configuration for other types of peons. Those config options couldn't be instantiated on Spark peons, because we already exclude some other extensions/modules on them, I don't remember for what exact reason.

@himanshug Did you want to review this PR?

:+1:  looked at it today, i think its fine given that @leventov has a real use case for it.

I'll create a backport


Cherry picking CombinedAnalyzer interface

Please provide a description of this PR:

Hi @jjamroga. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

normally, we just backport bugfix, why we need this?


logs: add ldk sublogger

This PR implements solution to #28:

Adds a sublogger (or subsystem logger) LDK
Then target that sublogger on MessageInstance

I tried adding just the prefix ldk: {} but it didn't feel right.
Few examples
Current log
2024-06-10T19:02:45.197452-04:00 TRACE lndk::onion_messenger - Missing reply path when responding to Offers onion message with path_id None
Only prefix:
2024-06-10T19:02:45.197452-04:00 TRACE lndk::onion_messenger - ldk: Missing reply path when responding to Offers onion message with path_id None
With subsystem (this PR)
2024-06-10T19:20:58.794410-04:00 TRACE ldk - Missing reply path when responding to Offers onion message with path_id None

Thanks for the PR @mauricepoirrier! I'll give this a test run later this week.

@orbitalturtle great, force pushed with update.
Thanks for the review 🙌🏼


Make sure to return the leased array from the destructor/finalizer

There are certain use cases, where deterministic disposal via an explicit call to Dispose is hard (say, when the leased object is shared among some threads), hence letting the destuctor to return the leased array can address the aforementioned use cases

Unfortunately, I disagree with this proposal. The finalizer is NOT a destructor and best practices say that if you need deterministic finalization, then you must explicitly call the Dispose method to free up resources. For your specific use-case of sharing this resource with multiple threads, then use modern techniques such as singleton registrations in a dependency container to manage the lifetime of this resource with the entire application.


Preserve the original port if it is specified

The SpoofingClient replaces the entire URL.Host, which is actually the URL authority, so it replaces the port as well. We need to preserve the port. This will enable advanced E2E testing on non-standard ports.

/assign @srinivashegde86

This fix is not needed anymore because this code is removed in https://github.com/knative/pkg/pull/620.


Problems with fullscreen (-f / -fullscreen)

Hello,
After upgrading to Iterm2 3.0 and I2cssh 2.0 the fullscreen options seems to be broken.
I have tried both options
i2cssh --fullscreen -nb -Xp=9090 Servers
or
i2cssh -F -nb -Xp=9090 Servers
We did a workaround on this just by creating a new Iterm2 profile and set the "Window" -> "Style" mode to Fullscreen and added the profile information to .i2csshrc

BTW Create product using it everyday ;)

Yea the -F flag doesn't work for me either.


Ability to save spec by calling remote url and load spec by getting data from remote url + way to clear settings

Hello guys!
I am working on integrating open api support into some go project (uadmin -> but I am heavily changing it to be easily used in real projects)
So, I found this project, I am gonna provide a way to start a server where developers which use uadmin have out of the box way to start locally oaie-sketch and ability to load/save spec from/to remote url.
So, I refactored this project a little bit, now it's ready to be published as own npm package that could be easily used in javascript world.
The main goal is provide a way to work with oaie-sketch locally.
Please review my solution.

Here is an example of usage:
For example I open my local url: http://localhost:8083/?saveToFileEndpoint=/spec
and in this changeset I store/load spec from the fs.
https://github.com/sergeyglazyrindev/uadmin/commit/2d7b445ba225e9d32291f8fdb53c303c1129c9dc

This is first step of improvements, I am gonna move all code into typescript and cover with tests, etc.


Error importing AWS targetGroup with pulumi cli

What happened?
I encountered an error while executing the import command for AWS targetGroup:
pulumi import aws:alb/targetGroup:TargetGroup new-targetgroup arn:aws:elasticloadbalancing:eu-west-1:XXXXXXXX:targetgroup/my_targetGroup/YYYYYYYYYY
The error message received was:
error: anonymous.pp:28,22-29,14: cannot assign expression of type (null) to location of type list({ onDeregistration: output(string) | string, onUnhealthy: output(string) | string } | output({ onDeregistration: string, onUnhealthy: string })) | output(list({ onDeregistration: string, onUnhealthy: string }))?: ;
Expected Behavior
The resource TargetGroup should have been imported correctly without any error.
Steps to reproduce
To reproduce the issue, just execute the targetGroup import command:
pulumi import aws:alb/targetGroup:TargetGroup
Output of pulumi about
pulumi about
CLI
Version      3.68.0
Go Version   go1.20.4
Go Compiler  gc

Host
OS       ubuntu
Version  22.04
Arch     x86_64

Backend
Name           dom
URL            s3://pulumi-state-backends
User           sergio
Organizations

Additional context
I have attempted to downgrade the Pulumi CLI to previous versions, but I am still encountering the same error.
Contributing
I would like to contribute to the resolution of this issue. Please let me know if there is any guidance or assistance I can provide.
Thank you for your attention to this matter.

It happens exactly the same.
A month ago I imported a target group and it worked, but currently I get that error

@SergioGenially and @MoralGr  Thank you for reporting this issue.
I'm trying to reproduce this with all the latest: CLI 3.68.0 and @pulumi/aws 5.41.0. I created a target group with the following repro:
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const main = new aws.ec2.Vpc("main", {cidrBlock: "<IP_ADDRESS>/16"});
const test = new aws.lb.TargetGroup("test", {
    port: 80,
    protocol: "HTTP",
    vpcId: main.id,
});

And then import the resulting target group as another resource. The command succeeds for me.
I suspect I need to set some other property on my target group to reproduce. Could you please provide more details about your target group configuration, ideally, as a Pulumi program?
Also, which version of the provider are you using?
Thank you!

Hello @mikhailshilkov.
We was using @pulumi/aws 5.30.0... After upgrading the plugin to 5.41.0 the import ran successfully.
Thank you so much for your support and sorry for the inconvenience.

This issue has reappeared starting with v6.7.0 and confirmed in 6.13.3.
The issue does not exist in v6.6.1.

Noting https://github.com/pulumi/pulumi/blob/master/pkg/codegen/hcl2/model/diagnostics.go#L41 possibly where the error is coming from.

Thank you all, apologies for the experience here, we'll have a look shortly, this sounds like it's something that need to be fixed by an integration test so we stop regressing on it.

https://github.com/pulumi/pulumi-aws/issues/2517 I believe is where this was dealt with before.

6.32.0 - not affected
6.21.0 - not affected
6.18.2 - not affected
6.18.1 - affected
6.18.0 - affected
6.17.0 - affected
6.13.3 - affected

Adding a regression test in https://github.com/pulumi/pulumi-aws/pull/3859 and closing for now as it appears to be fixed in the latest provider v6.32.0.


Default Integer Values Cause Validation Error

I have the following definition in my *.json file:
"Card": {
    "required": [
        "number",
        "exp_month",
        "exp_year"
    ],
    "properties": {
        "number": {
            "type": "string",
            "default": "0123456789123456"
        },
        "exp_month": {
            "type": "integer",
            "format": "int64",
            "default": 12
        },
        "exp_year": {
            "type": "integer",
            "format": "int32"
        }
    }
}

Validation fails based on the fact that the default value of exp_month is set to 12. Setting the value to "12" causes successful validation, however, the default value is then of the wrong type in the model.

Validation from what?

http://online.swagger.io/validator/debug?url=http://{myUrl}/swagger.json

Any chance you can share with me the URL? Even in email if you prefer to keep it private.

http://<IP_ADDRESS>/swagger.json
This URL will be active for the next few days, at least.
I've corrected the issue, so this JSON will validate correctly. Update one of the default integer values without including quotes to reproduce.

Can you host a sample that will not validate? Would just make the testing faster.

It's under test at the moment, Will have to wait until tomorrow.

Thanks, got something up and running. There's indeed a problem but I need to investigate it further.

This is indeed a bug. Please follow https://github.com/swagger-api/validator-badge/issues/23.


[SPARK-9962][ML][WIP] Decision Tree training: prevNodeIdsForInstances.unpersist() at end of training

NodeIdCache: prevNodeIdsForInstances.unpersist() needs to be called at end of training.

Merged build triggered.

Merged build started.

Test build #41842 has started for   PR 8541 at commit 2fe5c3d.

Test build #41842 has finished for   PR 8541 at commit 2fe5c3d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41842/
Test PASSed.

Merged build finished. Test PASSed.

Changes LGTM (renaming public method but the class is package private), but why do we need this (CC @jkbradley)? prevNodeIdsForInstances is never persisted in the first place

@feynmanliang I think it is (sort of), so nodeIdsForInstances.persist(StorageLevel.MEMORY_AND_DISK) and then eventually prevNodeIdsForInstances is set to this and nodeIdsForInstances is updated. (So there isn't an explicit cache call on something with that name but it totally is set to an RDD we want to unpersist). Or at least thats what I remember from reading through the code/JIRA (could have been off though)

Yep, it's a valid issue.  But...I just noticed: prevNodeIdsForInstances is already unpersisted on line 179.  Incorrectly.  That 179 should be within deleteAllCheckpoints.  Would you mind making that fix, removing cleanupCache, and making the same fix in the spark.mllib version?  Thanks!

@jkbradley thanks for catching that, I'll switch this PR back to WIP and ping you when I've got those changes in too.

Merged build triggered.

Merged build started.

Test build #42702 has started for   PR 8541 at commit c6e3f3f.

Test build #42702 has finished for   PR 8541 at commit c6e3f3f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42702/
Test PASSed.

Is this still WIP?

Oh no, sorry just forgot to update the title. Will do that momentarily.
On Monday, September 21, 2015, jkbradley<EMAIL_ADDRESS>wrote:

Is this still WIP?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8541#issuecomment-142138199.

--
Cell :<PHONE_NUMBER>
Twitter: https://twitter.com/holdenkarau
Linked In: https://www.linkedin.com/in/holdenkarau

LGTM, merging with master.  Thanks!


test: issue with global .asyncapi file getting overwritten while testing

Description

Running integration testing was overwriting the global .asyncapi file and it was quite annoying while developing.
We basically check if the NODE_ENV is test, and use .test.asyncapi file to do all the testing related operations.

Related issue(s)
Fixes #23

In your issue you have:

It would be nice to configure the root context service to load context from different files.

Of course not in this PR, but maybe we should have something like global config for CLI with info about path to the asyncapi context?
And last, please change the prefix for PR title to test not fix, we don't fix the code, but only fix the tests :)

@Souvikns You have one workflow which didn't pass :)

Yeah, I am trying to figure that out because test cases are passing in windows and ubuntu, only failing in macOS.

@magicmatatjahu can you rerun that specific action once, because it is running in my local machine.

sreenshot


v0.4.0

It seems like the bugs have been shaken out of v0.4.0. The docs probably just need a final once over to ensure a smooth transition into v0.5.0 and beyond.

The release has been tagged from the branch releases/v0.4.0


Fixes an issue with a completion callback not being called in PacketTunnelProvider.

Task/Issue URL: https://app.asana.com/0/0/1205410509758167/f
macOS PR: https://github.com/duckduckgo/macos-browser/pull/1579
iOS PR: https://github.com/duckduckgo/iOS/pull/1971
Description
Fixes an issue with a completion callback not being called in PacketTunnelProvider.
Additionally, this PR improves the code to make it impossible for this to happen again in the future.
Steps to test this PR
Test that NetP works fine in the macOS and iOS PRs.

Internal references:
Software Engineering Expectations
Technical Design Template

I'm closing this.  The errors being raised by Xcode make me think this could be trouble down the road, so I'd prefer to just add the completion callback that was missing and avoid all the move to async code.


Resources page

Resources that need to find a home on the website:

https://planner.langaracs.tech

course availability (https://docs.google.com/spreadsheets/d/1au-d_-j5VrDwNvTFUHbp8WI_URfDc9lGSvi1eUiTJXE/edit#gid=0)

course outlines (see #course-outlines channel on discord)

user-contributed notes for courses

Jon's transfer guide

other transfer guides (https://old.reddit.com/r/langara/wiki/index)

other transfer resources (slides from the transfer panels)

It might be better to split into a resources page and transfer information page.

closed by b848cd7
(only took 10 months...)