Mod does not respect block spawn rules or Forge CheckSpawn event

The spawner does not appear to check Forge's LivingSpawnEvent.CheckSpawn event, nor does it check if blocks overrode isValidSpawn. Looks like the check appears around the following code area:
https://github.com/CreeperHost/SoulShards/blob/d4103a16a0d955dd92a94b89d884b8e52c01a6d9/src/main/java/net/creeperhost/soulshardsrespawn/block/TileEntitySoulCage.java#L112-L113
This is causing several mob spawning issues with Compact Machines where enderman/shulkers are outside machine rooms. Adding these event checks would mean other mods can guard against spawns without specific compat code.

Would this also be why soul cages stop spawning when players move more than 128 blocks away, even when using chunk loaders? (tested with both FTB Chunks and Chunk Loaders).
Playing Direwolf20 1.18 pack, and everything seems ok except when I move beyond 128 blocks from the spawner, even for a tier 5.

pretty sure my issue is not specific to soul shards.  Seeing the same thing with dreadful dirt and agitators.  if it is related, then it's some odd interaction between forge and 1.18 spawning mechanics.  Opened an FTB issue here:
https://github.com/FTBTeam/FTB-Modpack-Issues/issues/922

Would this also be why soul cages stop spawning when players move more than 128 blocks away, even when using chunk loaders? (tested with both FTB Chunks and Chunk Loaders).
Playing Direwolf20 1.18 pack, and everything seems ok except when I move beyond 128 blocks from the spawner, even for a tier 5.

This is a different issue and will need to be opened as a new issue however since we don't check if a player is nearby in higher tier soul shards this sounds like a chunk loading issue

The spawner does not appear to check Forge's LivingSpawnEvent.CheckSpawn event, nor does it check if blocks overrode isValidSpawn. Looks like the check appears around the following code area:
https://github.com/CreeperHost/SoulShards/blob/d4103a16a0d955dd92a94b89d884b8e52c01a6d9/src/main/java/net/creeperhost/soulshardsrespawn/block/TileEntitySoulCage.java#L112-L113
This is causing several mob spawning issues with Compact Machines where enderman/shulkers are outside machine rooms. Adding these event checks would mean other mods can guard against spawns without specific compat code.

I'm still trying to figure out a good way to implement this, The entire point of a T5 shard is that it ignores spawn conditions, Still trying to figure out how to do this without breaking the T5 shard

Might be the reason why a cow shards L1 only spawns cows when it is dark which is counterintuitive.

This should be fixed in later builds of the mod


export: fix exporting extras sub-dependencies

[x] Added tests for changed code.
[ ] Updated documentation for changed code. (n/a)

Closes #1293.
When exporting groups specified by the --extras flag, sub-dependencies should be exported.
This PR fixes the regression by:

factoring out common logic from installer.py and exporter.py to utils/extras.py
adding tests for generating a complete list of required packages given a list of extras
adding a test for the specific regression experienced

@sdispater sorry for the regression

@brycedrennan thanks for the review - anything else to do before this can be merged?

Nope - looks good. I just need to deep dive myself to make sure I understand whats going on here.

@brycedrennan ping

@sdispater ping

@stephsamson thanks for getting this merged!


addNdefListener error on Windows 10

On Lumia 950XL nfc.addNdefListener return NO_NFC_OR_NFC_DISABLED. When i use nfc.addTagDiscoveredListener it detects the tag without error, but i don't have any information writen on it.

On Windows, addTagDiscoveredListener only detects that presence of the tag. There's no way to get the meta data, that function was added so you could write new messages to an unformatted tag.
nfc.addNdefListener should work on Lumia 950XL, it's possible you hit a bug. Can you create a simple reproducible test case and post the code?


Extract updater/proxy tags from Dockerfile

This is an attempt at automating the update of the updater and proxy
image using Dependabot, using it to update the Dockerfile and
extracting the values.
When we run ncc build, it copies the Dockerfile to the dist folder
so gets included in the bundle that's run by actions.
Fixes: https://github.com/github/dependabot-updates/issues/2102

Closing in favour of https://github.com/dependabot/updater-action/pull/72 and https://github.com/dependabot/updater-action/pull/73


test Windows binary

Strangely, this PR is not getting the latest commits from the branch. Created a new one.


Nest.js v8 Dependency Issues

I'm getting various issues installing the latest versions of Nest.js & Mercurius.
One being: https://github.com/nestjs/graphql/blob/master/package.json#L80
I'm not sure apollo-server-core should even be a peerDependency.  Perhaps this library needs to make all the optional dependencies optional using "peerDependenciesMeta"?

well unfortunately apollo-server-core is not optional, because @nestjs/graphql uses it (using @nestjs/graphql directly requires either apollo-server-express or apollo-server-fastify that has a direct dependency with apollo-server-core)
we could add apollo-server-core as a depencency keeping aligned with the peerDep defined on @nestjs/graphql, or simply modifying the install instructions including it


10.0.19044.1566 Not Supported

Can I please get an ini and/or termservice dll for 10.0.19044.1566 windows 10?
Thanks.

Duplicate of https://github.com/stascorp/rdpwrap/issues/1725

hi
we would want fix for 19044, not 19041
the duplicate is for 19041, and not running for me (i have10.0.19044.1566)
thank's for job

hi we would want fix for 19044, not 19041 the duplicate is for 19041, and not running for me (i have10.0.19044.1566) thank's for job

See carefuly your termsrv.dll version and say me if it 19044 😉

But I still don't know how to fix it? Are you saying I can use the term service from that other issue? Because I tried that and I had to system restore cause the remote services got messed and I couldn't load Windows.

sorry for loose your time, it was just that i don't reboot computer after change the rdwrap.ini file...
That's work ! :)
in the read me, frequently asked questions, maybe you can add these lines

install steps
launch in admin mode install.bat
get the rdwrap.ini file for your windows version in issue section
replace the C:\Program Files\RDP Wrapper\rdpwrap.ini by this one
add users in "Remote Desktop Users" group
reboot !!!!

one more time, thanks :)

Glad it worked for you, but simply replacing the ini didn't work for me, stopped term service, replaced ini, turned term service service back on, rebooted and nothing changed.

Glad it worked for you, but simply replacing the ini didn't work for me, stopped term service, replaced ini, turned term service service back on, rebooted and nothing changed.

Try autoupdate from asmtron or my modded rdpwrapper

Glad it worked for you, but simply replacing the ini didn't work for me, stopped term service, replaced ini, turned term service service back on, rebooted and nothing changed.

Try autoupdate from asmtron or my modded rdpwrapper

Was I not supposed to use the black version? I tried installing it and now my Remote Desktop Services service won't start.


Suggestion for kinematic2d move_and_slide_with_snap()

Godot version:

3.1dev compiled 17/07/2018
Issue description:

I see this function now in kinematic2d and my opinion is that this can be simply accomplished by adding that parameter with default value to move_and_slide:

NOW:

move_and_slide (linear_velocity, floor_normal, infinite_inertia, slope_stop_min_velocity, max_bounces, floor_max_angle)
move_and_slide_with_snap (linear_velocity, snap, floor_normal, infinite_inertia_ slope_stop_min_velocity_ max_bounces, floor_max_angle)

SUGGESTION:

move_and_slide (linear_velocity, floor_normal, infinite_inertia, slope_stop_min_velocity, max_bounces, floor_max_angle, snap= default value to no snap)
If snap is added behind last parameter and with default value, there is no breaking compatibility.
I feel that this two functions can be too redudant and move_and_slide_with_snap can go out of script screen easely. To long, tooo, looooong.
I don´t know if this make sense but thanks for read.
Juan Post:
https://godotengine.org/article/godot-31-will-get-many-improvements-kinematicbody

If infinite_inertia was added, snapping can also be added, and snapping is used mostly on sidescroll so it can be:
move_and_slide (linear_velocity, floor_normal, snap, infinite_inertia, slope_stop_min_velocity,  max_bounces, floor_max_angle)

New arguments should go to the end. infinite_inertia was moved to end as well.

Sometimes when scripting in godot i think that can be awesome to have a keyword to specify to use default argument. Something like that:
move_and_slide ( Vector2(1,1), def, def, def, def, def, Vector2(1,0))
... it can be ugly by stetics, but very useful (I know that def is function in python.....)

For 4.0 we plan to refactor the KinetaticBody(2D) APIs to rely less on passing so many cryptic arguments, but use class-wide configuration and a better interface to pass custom values.
It's not fully defined how it should be done exactly, but this will definitely be addressed at the same time.


Uncaught TypeError: fns[i] is not a function

I added "fuckadblock.js" and some javascript code from README.md to my application and got this:

Uncaught TypeError: fns[i] is not a function

Seems like io.use( 'some literal', function(){} ) used instead of io.use( function(){} ) when migrated to socket >1.0.


Working version for ubuntu 14.04

Came across this project while looking for a Docker varnish container.
I was not able to get the official docker hub build working, so attempted a local build. That was also failing with errors about libc6 dependancies. I stripped down the Dockerfile a bit and was able to get it building and working.
I am not sure if you still want the locales package. I left it out of this set of commits.

Thanks for the PR @rtrauntvein and sorry for the awful old replay.
Most of these changes where fixed by #2 and I will close down this PR. If there's still some things you'll like to change, add a new PR and I will looks at it ASAP.


added following method

2 different PRs for same issue? @JatinGera27aug

ya for 1st time, i used vs code commit functionality directly but that was giving error like permission denied, don't know how an extra one is created

Okay, @JatinGera27aug, so closing this one.


Default epsilon in rbf.py fails for colinear points

Commit ce66e32b3efb3fd4756700cce3db81c4d76bd605 changed the default epsilon used by the Rbf interpolator. Unfortunately, this choice raises a ValueError for colinear points lying along an axis, because the min and max "difference" is the same, causing a divide by zero.
For example, trying
from scipy.interpolate import Rbf
Rbf([1,2,3], [4,4,4], [2,5,8])

will fail. This is because line 205-207 [1] has
ximax = np.amax(self.xi, axis=1)
ximin = np.amin(self.xi, axis=1)
self.epsilon = np.power(np.prod(ximax - ximin)/self.N, 1.0/dim)

In the example above, ximax=[3,4] and ximin=[1,4], so the product of their difference is zero.
I suspect that the default could be adjusted in a way that doesn't raise an exception. The current version uses the volume of a bounding (hyper)cube, but the example is a case where this cube is zero. What about just dropping zeros before np.prod?
[1] https://github.com/scipy/scipy/blob/adbf5a6b7f3f32b2fdfb456582b98d0af9a12838/scipy/interpolate/rbf.py#L207

Fixed by gh-5264, closing.


Issue #196 CVE 2016 0751 incorrectly flagged

fix CVE-2016-0751 False Positive

Coverage increased (+4.3%) to 100.0% when pulling 5b3f74faeb10a7d897091664d9ce80c2581145a1 on MKgridSec:issue-#196_CVE-2016-0751-incorrectly-flagged into 8eb9b7b6ea41a7d6e88e68f77565529d4184d0cd on thesp0nge:master.


net: coap: Fixed discovery response formatting according to RFC6690

This PR resolves #31609
Signed-off-by: Kasun Hewage<EMAIL_ADDRESS>

Please, no merge commits in PRs. Just rebase your stuff against latest master and force push to this PR.

Please, no merge commits in PRs. Just rebase your stuff against latest master and force push to this PR.

I will rebase and push.

I will rebase and push.

Lookd like only the build 14 was failed. Any idea?

Lookd like only the build 14 was failed. Any idea?


mn should not (or should) accept --controller remote,ip=<IP_ADDRESS>:6653 syntax

Hi ALL
I am running Helium SR-1 in Ubuntu and Mininet version 2.2.0. I am connecting it to ODL with this command
sudo mn --topo=single,1 --mac --controller=remote,ip=<IP_ADDRESS>:6653 --switch ovsk,protocols=OpenFlow13
Mininet says it cannot connect to ODL
*** Adding controller Unable to contact the remote controller at <IP_ADDRESS>:6653:6633
But there are OpenFlow v1.3 flows in wireshark. I can see hello messages and all other OpenFlow messages.
ovs-vsctl show also shows controller connected.
Why does it say that the controller is not connected.

As Seenu pointed out on the mailing list, the correct syntax is ip=x,port=y
Using ip=x:y has the desired result, but prints an error message because neither ip nor port are set correctly.
We could handle this by splitting x:y into ip,port.


[question/feature request] Is there a way to read source pixels?

Hi! 🙂
Libjpeg library allows reading source pixels (RGB/Gray in YCbCr color space in most cases) from a jpeg file.
I noticed that the libjxl examples (decode-oneshot) always convert pixels to a specific format. Is there a way to access the original pixels without converting them to a different format?

In 'native' lossy mode, the data is in XYB colorspace and if you want it in that space, you can ask for that.
In lossless mode, you can of course get the data in their original colorspace (RGB or CMYK).
So I guess the question is mostly about recompressed JPEGs, where the internal space is YCbCr, sometimes with chroma subsampling.
We could easily add an option to skip the YCbCr to RGB conversion and return the data in YCbCr. It's more complicated to add an option to get yuv420 data though — the current API is hardcoded for interleaved color data (RGB or RGBA).
How important is this feature request? What are the use cases where this would be useful/needed? The API could be extended with an option to skip upsampling and return yuv420 data in some way, but that will take some nontrivial amount of work and I'm not sure if it's worth the effort...

Thanks! I'm currently just experimenting with libjxl and my current goal is to decode a jxl file as fast as possible (preserving the original color space and pixel format) even if I get XYZ pixels not immediately suitable for displaying in an UI app for example.

In 'native' lossy mode, the data is in XYB colorspace and if you want it in that space, you can ask for that.
In lossless mode, you can of course get the data in their original colorspace (RGB or CMYK).

Could you please demonstrate this with a couple if lines of code, or just name api functions I need to use?

To do the least amount of color conversions, you could use JxlDecoderSetPreferredColorProfile() with as argument a JxlColorEncoding that has color_space set to JXL_COLOR_SPACE_XYB, in combination with using a JxlPixelFormat that has data_type set to JXL_TYPE_FLOAT and endianness set to JXL_NATIVE_ENDIAN.


add Remainder, still need the tests

Trying to add Remainder transformation, but the tests is needed

Codecov Report

Merging #27 (11e6430) into master (806be6f) will decrease coverage by 6.62%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   77.50%   70.88%   -6.63%
==========================================
  Files          12       12
  Lines         289      316      +27
==========================================
  Hits          224      224
- Misses         65       92      +27

Impacted Files
Coverage Δ

src/transforms/remainder.jl
0.00% <0.00%> (ø)

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 806be6f...11e6430. Read the comment docs.

I was writing the tests but forgot the other PR that will make changes in tests/transforms.jl, so I decided not to push the tests for the Remainder for now.

Closing in favor of #28


Modify HttpGet() to return whether the request was successful.

Changes HttpGet() to return a bool indicating success, and store the response in an out parameter. This lets us differentiate between a backend/server failure, and an empty response.

This lets us differentiate between a backend/server failure, and an empty response.

Is there a way to differentiate between a server failure, and the case where a user cannot be found by the server (ie non osloin user)? With that we can then reliably tell in pam_oslogin_login.cc whether we should return DENIED or SUCCESS.

If the user can't be found by oslogin, then we should return SUCCESS to avoid preventing a local user from logging in. We could return DENIED on a server failure, but then this would then also block local users in the event of a backend failure. Returning SUCCESS ensures we don't impact a local user's ability to log in, but DENIED would definitely be more secure, so I can see value in both choices. This behavior also only applies to the user lookup--if we fail the authorize call at any point, that will always result in DENIED.
The risk would be if that exact call failed, the similar lookup in the auth_keys command would also have to fail(and the user also has to have local ssh keys), and all other lookups succeeded, we may accidentally permit a user who shouldn't log in. A persistent backend failure would mean other user lookups would fail, and nss would also not be able to get the user's info, so it is unlikely we would even get this far.
@illfelder any preference on what we should do?

Currently we are discussing a trade-off between security and reliability. In order to prevent blocking local user logins when the OS Login backends are down, and in order to prevent allowing a non-authorized user from logging into the VM, I propose we do the following:
Today, when a user logs in with OS Login, the PAM module will create a file in a particular directory to grant the user sudo permission (assuming the user is authorized). We should create a second directory for non-sudo users. When a non-sudo OS Login user logs in, we can create a file in that second directory. If we get a server error authorizing a user, check if the user has a file associated with them. Deny the user login if they do.
What do you think?

Note: the other benefit of this approach is that we can also address an edge case where a user is deleted from their G Suite organization so the user lookup fails, but the local account still exists.

Let's lay out the risks of both sides, and see how likely each will happen:

Solution A. Return DENIED on server failure, the risk is a local user won't be able to login.
Solution B. Return SUCCESS, the risk is an OSLogin user with their pubkey stored at /home/<user>/.ssh/authorized_keys will be able to log in.

The risk of Solution A can be realized when there is a persistent server failure, and the user info is not already cached by metadata server. Which is highly probable imo.
The risk of Solution B can be realized when there is a transient server failure, where the NSS call passes, but the following PAM call fails. Given that both calls are retried, and the already restricting prerequisite of it, I think it will be very unlikely to happen in practice. And if this is only a regular user, the damage of the potential bad login won't be too dramatic either.
So I am leaning towards Solution B (current implementation). WDYT?

The solution in my comment above doesn't prevent local user login, and prevents OS Login users from logging in without an authorization check. That obviates the security concern without affecting availability. The only downside is a file creation for every user.


python311Packages.requests-pkcs12: 1.16 -> 1.18

Diff: https://github.com/m-click/requests_pkcs12/compare/1.16...1.18
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

8 packages built:

python310Packages.pytenable
python310Packages.pytenable.dist
python310Packages.requests-pkcs12
python310Packages.requests-pkcs12.dist
python311Packages.pytenable
python311Packages.pytenable.dist
python311Packages.requests-pkcs12
python311Packages.requests-pkcs12.dist


Pull Request: UNet Segmentation Model Integration for HipMRI Prostate Cancer Study

This pull request introduces a UNet-based model for semantic segmentation of the prostate gland in MRI images, specifically tailored for the HipMRI Prostate Cancer Study dataset. The model has been simplified to reduce overfitting and achieves a minimum Dice Similarity Coefficient (DSC) of 0.75 on the test set for the prostate label.
Types of Changes
New feature: Added a new segmentation model and associated scripts.
Bug fix: N/A
Breaking change: N/A
Documentation update: Updated README and added comments for clarity.
Added Files:

modules.py: For declaring UNET model
train.py: Training procedure, utilising the modules and dataset files
predict.py: Uses the trained model and modules.py UNET model for inference
dataset.py: Organises and proprocesses NIFTI form data for training and prediction

Dice Similarity Coefficient for each class:
Class 0: Dice = 0.9968
Class 1: Dice = 0.9839
Class 2: Dice = 0.9194
Class 3: Dice = 0.9493
Class 4: Dice = 0.8975
Class 5: Dice = 0.8873

This is an initial inspection, no action is required at this point

Solves problem: The problem is well solved, all labels reached over 0.88 DICE score. The report is detailed, clear and well-structured. Prediction figures and DICE are reported. The UNet figure in the readme includes a residual unit, but this is not implemented. It would be better to replace this UNet figure with the basic one, aligning with the implementation.
Implementation: Data augmentation is used. Hpyerparameter is hard-coded rather than using ArgParse. Otherwise, all functions and classes are great.
Design: Great
Comment: Very detail and well-structured
Difficulty: Easy

Note
The pull request should be created on topic-recognition branch not main.

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation.
Spacing and comments.
No Header blocks. -1
Recognition Problem
Good solution to problem.
Driver Script present.
File structure present.
Good Usage & Demo & Visualisation & Data usage.
Module present.
Commenting present.
No Data leakage found.
Difficulty : Easy. UNet2D (Easy Difficulty)-10
Commit Log
Some/Adequate Meaningful commit messages. -1
Good Progressive commits. No logical flow.-2
Documentation
Readme :Good.
Model/technical explanation :Good.
Description and Comments :Good.
Markdown used and PDF submitted. PDF checked.
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch). Submitted on time.
Feedback action required: Feedback marks possible +2 if the requested changes are made. PR on wrong branch. Correct for merge.-2
Request Description is good.
TOTAL-16

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes

Feedback marks possible +2 if the requested changes are made (see above).

Cant merge because of conflicting changes to main repo files (gitignore). Please update for merge, doesn't affect grade.

Segmentations not one hot encoded -2 additionally, Feedback applied +2

@shakes76 gitignore removed.
Also I do not understand why outputs must be one hot encoded. It uses class indices.
Was this specified somewhere ?
It works as intended.
Thanks

Yes it is standard practice to one-hot encode in segmentation and I discussed this in lectures etc.
Still have conflict in README file of parent recognition directory. Can't merge still.

@shakes76 I think I fixed the issue with the README.
Thanks. Let me know if anything else I have missed.


Fix/conda test

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   83.89%   83.89%
=======================================
  Files           1        1
  Lines         149      149
=======================================
  Hits          125      125
  Misses         24       24

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 da61c1b...fafc9b0. Read the comment docs.


The performance improvement with GPU is not significant

I ran the code of this article: https://github.com/AI4Finance-Foundation/FinRL-Tutorials/blob/master/1-Introduction/Stock_NeurIPS2018_SB3.ipynb
I trained all algorithm in 3571 seconds using the CPU(intel-9900k)
Then I reinstalled pytorch with cuda11.8 and started training with cuda device
I trained all algorithm in 2731 seconds using the GPU(RTX2080)
I didn't change any of the code in the article, why not much performance improvement only 23% ?
Previously I used tensorflow or yolo, I'll get a tens of times better performance when I switching to a GPU.
Do you have any examples of training using GPU？Thanks

Is the algorithm running for 2731 seconds including data import, preprocessing, and training, or just the training time?

Is the algorithm running for 2731 seconds including data import, preprocessing, and training, or just the training time?

Both times are the time it takes to run all the code in that article, including data import, preprocessing, and training

Is the algorithm running for 2731 seconds including data import, preprocessing, and training, or just the training time?

Both times are the time it takes to run all the code in that article, including data import, preprocessing, and training

There may be a reason why the improvement rate is only 23%. The GPU only accelerated the training process, as the libraries used in data preprocessing do not utilize the GPU. Please verify the improvement in only the training process, a test can be conducted using datetime from Python.

Is the algorithm running for 2731 seconds including data import, preprocessing, and training, or just the training time?

Both times are the time it takes to run all the code in that article, including data import, preprocessing, and training

This may be the reason why the improvement rate is only 23%. The GPU only accelerated the training process, as the libraries used in data preprocessing do not utilize the GPU. Please verify the improvement in only the training process, a test can be conducted using datetime from Python.

I rerun the code and only count training time, 3365 seconds cost on CPU, 2608 seconds cost on GPU, nothing changed as before, still 22% improvement.

It could be batch size too small? I don't see any doc in sb3 readthedocs that introduce how to train on gpu.

It could be batch size too small? I don't see any doc in sb3 readthedocs that introduce how to train on gpu.

ooh, SB3 is not optimized for GPU…if I remember correctly.

It could be batch size too small? I don't see any doc in sb3 readthedocs that introduce how to train on gpu.

ooh, SB3 is not optimized for GPU…if I remember correctly.

SB3 support GPU via cuda version of pytorch.
https://stable-baselines3.readthedocs.io/en/master/modules/ppo.html
I run this example by cpu, training takes 40+ minutes. When I switch to gpu, it only takes a few seconds.
I don't understand why it didn't work on this project, 40+ minutes to few seconds.

It could be batch size too small? I don't see any doc in sb3 readthedocs that introduce how to train on gpu.

ooh, SB3 is not optimized for GPU…if I remember correctly.

https://stable-baselines3.readthedocs.io/en/master/modules/ppo.html
That's true, I run the example of the article above, it cost 110s (I cange total_timesteps to 200000) and I change to cuda version of pytorch, it cost 220s.


Update package-lock.json.

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

Project coverage is 89.33%. Comparing base (340359a) to head (e0385fc).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #442   +/-   ##
=======================================
  Coverage   89.33%   89.33%
=======================================
  Files          58       58
  Lines        4387     4387
  Branches      413      413
=======================================
  Hits         3919     3919
  Misses        467      467
  Partials        1        1

Flag
Coverage Δ

unittests
89.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


GPU-aware communication with UCX in Charm++

Extracted only the parts relevant to Charm++ (and not AMPI and Charm4py) from #2791.
Changes:

Adds GPU-aware communication capabilities to Charm++ by extending the UCX machine layer. One significant change is that the regular entry method is now called after the data transfer is complete, instead of after it is initiated. The transfer is still tracked asynchronously within the runtime system.
Updated OSU latency benchmark
Removed time measurement code
Fixed bug in buildold script
Updated documentation

Ready for review. Tested with the verify example (examples/charm++/cuda/gpudirect/verify) and OSU latency benchmark (benchmarks/charm++/cuda/gpudirect/latency).


Support for .NET Core?

Any plans to support .NET Core?

I have sent a pull request some time ago with the lib converted to .NET Core (well, DNX still) https://github.com/ppatierno/azuresblite/pull/4 and it has not been pulled into the main branch. If we can get @ppatierno to pull a newer update, I will do the conversion to NetStandardLib1.6.

I have just updated my PR #4 to include support for netcorestandard1.6. Lets hope @ppatierno pulls in the changes.


[thought] cache layer and return

I have a notion that I'd like to add a cache layer that checks to see if the site has been rendered and stored in the last X amount of seconds. I have two ideas around this:

Use the google-cloud node libs to use datastore as a key/val store (ala https://github.com/stephenplusplus/google-cloud-kvstore)
Use an external redis/memcache setup (which is in the gae flex docs).

Option one obviously binds the container to be less portable (and I'd think this would be an enabled feature rather than a requirement to run the container). Option two has more flexibility (not bound to GCP), but still sits in the same boat (probably shouldn't be a requirement).
Would this be something that would be interesting to you @samuelli as a PR? Did you have any thoughts on the topic of caching?

Yep, this is all stuff I wanted to add but haven't quite had the time to work on yet.
Definitely planning a pretty complex caching layer. Given that rendering can be pretty slow, I'm thinking some combination of parameters in the request (eg. time before stale, time for refresh) that result in a queued render.
eg. you request resource a (stale = 6 day, refresh = 1 day), and if it was cached 2 days ago, you would serve the cached render and queue a render to update the cache (since refresh was requested at 1 day).
No opinions on cloud/redis. What are the storage limits for values in both?
More generally, the whole bot-render needs to be architected properly to scale properly.

The queued render is a good idea; there is a pretty clean path to this on the existing GCP side (cron/task queues) although could arch something different. As you note, there's some complexity there via time before stale and what not, but doable. :-)

No opinions on cloud/redis. What are the storage limits for values in both?
Text long has a 1MB limit in GAE datastore (non-indexed), String in Redis has a 512MB limit.

More generally, the whole bot-render needs to be architected properly to scale properly.
If you've got a doc lying around, happy to contribute however I can.

Unrelated, why is only returning head awesome? That's planned to be changed to return the whole (serialised) response. Ref: https://github.com/justinribeiro/pwa-firebase-functions-botrender/blob/master/functions/index.js#L67
1MB should be fine... if we use compression.
I sent you the doc of what I have so far, but it's mostly around what needs to be done and less about architectural design. I haven't spent too much time thinking about architecture, but I'm expecting it to be mostly pretty layered/modular.
Caching is one layer, rendering another, queues another etc. I'd want to extract/publish a few node modules as well. I'd also like to do some pretty heavy load testing too.

Unrelated, why is only returning head awesome? That's planned to be changed to return the whole (serialised) response. Ref: https://github.com/justinribeiro/pwa-firebase-functions-botrender/blob/master/functions/index.js#L67

It's awesome because when I tested this last year with headless_shell and some other AppEngine python things, I found that you can actually return even less to most link sharing bots (they really just love those open graph tags). Cut down the response to bare bones data, speed up where item is being shared. Now, should you only send the <head>? Probably not. :-) Basically playing "pffft who needs valid data" in which case the upcoming change I'm fine with (makes sense to me). I think I'll put a note in there about that.

I sent you the doc of what I have so far, but it's mostly around what needs to be done and less about architectural design. I haven't spent too much time thinking about architecture, but I'm expecting it to be mostly pretty layered/modular.

Cool. I'll have a look and try not to pester you (I know you're busy).

It's awesome because when I tested this last year with headless_shell and some other AppEngine python things, I found that you can actually return even less to most link sharing bots (they really just love those open graph tags).

@justinribeiro @samuelli Can we not have both the functionalities in bot-render?

Send limited amount of data for social sharing/link sharing bots (taking Open Graph tags into account).
Dump complete HTML DOM for search engine bots.

Probably, control this by having an additional query param in the existing route.
Background: I landed on this repo looking for a solution to our use case - Replace PhantomJS by Chrome headless in a service responsible for serving a rendered HTML DOM of a provided URL. We use this service to serve our Single Page Application (AngularJS) to search engine bots.

I have done the same for our use case here. Please let me know your views and if I need to modify anything to fit into your contributing guidelines.

I've suggested this before, but the benefits seems questionable. Performance & size is not typically a concern with any of these bots. This solution already requires differential serving, so having to do another check for sharing/search adds a little bit of extra complexity.
My thoughts at this stage are to serve full content to all of these agents until there is a demonstrable case for why this would be needed. It seems nice in theory, but the practical implications are unclear at this stage.

Memcached or datastore?
Memcached is a distributed memory object caching system which allows for rapid reads/writes. Google Cloud Datastore is a NoSQL, scaling datastore.

Size: Gzip size of a sample page on webcomponents.org was 30KB. Redis free tier only supports 30MB which means we’re limited to storing 1000 pages in the cache. For any reasonable service size, this would result in a high cache miss rate.
Performance: memcached is an order of magnitude faster than Cloud Datastore. However, a cache miss is significantly more costly since we’ll have to re-generate the result again which is pretty slow given the headless rendering times.

Datastore is the more appropriate fit for what we need, which is a large storage system where read performance is not critical.

Closing this as there is a basic cache layer implemented now.


Adds avro file support

Adds avro file helper where rows returns a table of data  (array of arrays); the first being the "header", all others are the data
Adds NdrImport::Avro::Table that ensures header_lines and footer_lines are always 1 and 0 respectively. All other "table" logic is inherited from NdrImport::Table
#93

Looks good. @ollietulloch is it worth putting in a class method like NdrImport::Avro::Table.from_schema(safe_path) that returns a new instance of NdrImport::Avro::Table seeded from the Acro schema? It could then be serialised in YAML as a scaffold transformation, or used to feed a like-for-like import process automatically?

Also @bshand, at what point do you think these should be farmed out to new gems, so that every install doesn't need every filetype dependency?

Looks good. @ollietulloch is it worth putting in a class method like NdrImport::Avro::Table.from_schema(safe_path) that returns a new instance of NdrImport::Avro::Table seeded from the Acro schema? It could then be serialised in YAML as a scaffold transformation, or used to feed a like-for-like import process automatically?

@timgentry - nice idea, I'll take a look

Looks good. @ollietulloch is it worth putting in a class method like NdrImport::Avro::Table.from_schema(safe_path) that returns a new instance of NdrImport::Avro::Table seeded from the Acro schema? It could then be serialised in YAML as a scaffold transformation, or used to feed a like-for-like import process automatically?

@timgentry - nice idea, I'll take a look

@timgentry - initial commit here: 07914c2. It just scaffolds basic column mappings for now

@ollietulloch Looks good to me. @bshand can you merge if you're happy with it?

This will resolve #94


loadTestModel doesn't seem to work

Loading a test model doesn't seem to work:
r = te.loadTestModel('feedback.xml')
Traceback (most recent call last):
File "", line 1, in
r = te.loadTestModel('feedback.xml')
File "C:\Tellurium-Winpython\python-2.7.13.amd64\lib\site-packages\tellurium\tellurium.py", line 862, in loadTestModel
return roadrunner.testing.getRoadRunner(string)
File "C:\Tellurium-Winpython\python-2.7.13.amd64\lib\site-packages\roadrunner\testing\testfiles.py", line 37, in getRoadRunner
r.load(data.decode())
File "C:\Tellurium-Winpython\python-2.7.13.amd64\lib\site-packages\roadrunner\roadrunner.py", line 3559, in load
self._load(*args)
File "C:\Tellurium-Winpython\python-2.7.13.amd64\lib\site-packages\roadrunner\roadrunner.py", line 2765, in _load
return _roadrunner.RoadRunner__load(self, uriOrSBML, options)
NotImplementedError: Wrong number or type of arguments for overloaded function 'RoadRunner__load'.
Possible C/C++ prototypes are:
rr::RoadRunner::load(std::string const &,rr::Dictionary const *)
rr::RoadRunner::load(std::string const &)

This is a duplicate of
https://github.com/sys-bio/roadrunner/issues/400
I reported some time ago. Would be great to get this fixed.

Fixed by commit https://github.com/sys-bio/roadrunner/commit/3a8d9799266a42bca5814de9ac19db05b5a9d5da


Improve detection of cases where subtype reduction is unnecessary

Fixes #53425.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot perf test faster
@typescript-bot test top100

The new errors above actually seem... good?

Looks like people who declared something with
let x: void | number;
if (maybe) {
  x = 32;
}
x;

now get an error, which they absolutely should have.

@typescript-bot run dt

@jakebailey @RyanCavanaugh I think the new errors are better. They're caused by the change to use initialType in the calls to isTypeSubsetOf but aren't actually necessary to fix the original issue. Previously, the undefined we'd inject in the initial type to catch missing initialization situations was seen as a "foreign" type because it isn't part of the declared type.  That in turn would make it look like all code paths initialized the variable and we wouldn't report the error.

To be fair, nobody should be declaring things as T | void anyway.  void !== undefined.  https://github.com/microsoft/TypeScript/issues/42709 FTW 😉


Confusing warning message for sbt version mismatch

[x] I've read the CONTRIBUTING guidelines

steps
Use a different version of sbt using -sbt-version argument than what is present in project/build.properties
$ cat project/build.properties
sbt.version=1.1.6
$ sbt -sbt-version 1.2.0 update
[warn] sbt version mismatch, current: 1.2.0, in build.properties: "1.1.6", use 'reboot' to use the new value.
...

problem
Warning message is confusing regarding which version of sbt will be used in project
expectation
Warning message should tell what version of sbt will be used in the project and offer alternative to switch back to version from build.properties. new value is ambiguous wording in the message
notes
sbt version: 1.2.0

Thanks for the report @anilkumarmyla. Do you have a suggestion for an exact wording? (If not, it's ok too)

@eed3si9n It would be nice if it said what version of sbt it will be using for the command to be executed and optionally offer alternative to use the version in build.properties. Something in the lines of [warn] sbt version mismatch, using: 1.2.0, in build.properties: 1.1.6, use 'reboot' to use the version in build.properties

ok. Also how about not showing any warnings at all if sbt.version is passed in via command line?

Also how about not showing any warnings at all if sbt.version is passed in via command line?

That is also fine, but it is always good to show the sbt version being used on the project as an info log.

I just run into that and found it also confusing. I was not aware of reboot, so I tried it and got exactly the same message.
➜ update-to-play-2.8 git:(update-to-play-2.8) ✗ sbt -Dsbt.version=1.2.8
[warn] sbt version mismatch, current: 1.2.8, in build.properties: "1.3.5", use 'reboot' to use the new value.

...

sbt:play-grpc> reboot
[warn] sbt version mismatch, current: 1.2.8, in build.properties: "1.3.5", use 'reboot' to use the new value.

...

sbt:play-grpc> sbtVersion
[info] play-grpc-scalatest / sbtVersion
[info]  1.2.8

Basically, reboot is not changing to the version in build.properties.

Reboot is not changing the version to the one in build.properties. Does anyone know how to force sbt to update to the correct version?


Raspberry Pi 3 init timeout

Hello,
I've got some error message from example.js
init GT511-C3 at 9600 baud...
init error: timeout!
serialport successfully closed!
init GT511-C3 at 115200 baud...
TypeError: There's no write queue for that file descriptor (after write)!

I've tried on Raspberry Pi 2 and it's run completely. Any idea or suggestion please?

Now I can resolve it from this.


Stopped working

The quickstart example returns nothing.
If the cell Name is given instead of the numeric id, the ows Feature request returns but does not contain a property "WARNCELLID" and line 245 raises:
Illegal property name: WARNCELLID for feature type dwd:Warngebiete_Gemeinden
WARNCELLID seems to be no longer supported
Instead AGS (digits 2-9 of warncell id) TYPE (first digit of warncell id) must be used, apparently

In the query dwd:Warngebiete_Gemeinden/Kreise, the WARNCELLID is no longer returned.

In the module core.py, change the line
query += f"&CQL_FILTER={kwargs['cql_filter']}"
to
query += f"&CQL_FILTER%3D{kwargs['cql_filter']}"

The problem is that DWD did a lot of, in my opinion bad, changes.

WARNCELLID was replaced by FID. But: WARNCELLID was unique over all tables (Gemeinden, Kreise, Binnenseen, See), FID is not unique over all tables.
The FID attribute is not part of the Warning info, so search must be done by name.
The table containing the "Gemeinde" warnings dwd:Warnungen_Gemeinden cannot be queried anymore.

I'm currently testing a version which only supports Landkreise, due to the given constrains.

Are these changes documented?
Here https://www.dwd.de/DE/leistungen/warnungen/aenderungen_herbst2021.html?nn=16102&lsbId=397560 they write about upcoming changes in autumn and the warncellid. This does not sound like they want to drop the warncellid. Maybe it is only bug in the DWD software?

I cannot query the Warnungen by FID:
https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd%3AWarnungen_Landkreise&CQL_FILTER=FID%3D304&OutputFormat=application/json

That what i meant with:

The FID attribute is not part of the Warning info, so search must be done by name.

My current status:

It seems as if the warncell id is part of the id field when quering for regions. Example result "id": "Warngebiete_Kreise.103158000"
https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd:Warngebiete_Kreise&OutputFormat=application/json
The warncell id is also part of the id field when quering for warnings. Example result "id": "Warnungen_Landkreise.109576<IP_ADDRESS>.1.276.DWD.PVW.1622966655491.0.3"
https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd:Warnungen_Landkreise&OutputFormat=application/json
So the solution is retrieving the whole tables and searching in Python.

Still unresolved:

The table dwd:Warnungen_Gemeinden is missing, so warnings "auf Gemeindeebene" cannot be queried currently.

I think DWD messed up a lot.
Should i publish an update or should we wait for DWD to fix their error?

As of https://geoportal.sachsen.de/cps/capabilities_viewer.html?url=https%3A%2F%2Fmaps.dwd.de%2Fgeoserver%2Fwfs%3FSERVICE%3DWFS%26VERSION%3D2.0.0%26REQUEST%3DGetCapabilities , the feature is dwd:Warnungen_Gemeinden_vereinigt :
https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd:Warnungen_Gemeinden_vereinigt&OutputFormat=application/json&CQL_FILTER=IDENTIFIER%3D'<IP_ADDRESS>.276.0.DWD.PVW.1622965080000.c104d27b-4dd0-4bd0-af7b-714f2f09801b.DEU'

It is very strange that there is no blog post about that changes.

The table dwd:Warnungen_Gemeinden_vereinigt is not new. It exists since i started the development of this api.
The problem with dwd:Warnungen_Gemeinden_vereinigt is that the warnings in this table do not contain any information to link the warnings to regions defined in dwd:Warngebiete_Gemeinden.

In the capabilities document, Warnungen_Gemeinden is not defined. Maybe it was not official?
Warnungen_Landkreise can be directly accessed by AREADESC filter: CQL_FILTER=AREADESC:'Saale-Holzland-Kreis'

But then the table dwd:Warngebiete_Gemeinden doesn't make sense.
I think i will make a fix, which works for everyting execpt "Gemeinden".

I changed the code and this works for Kreise:
    def __generate_query(self, identifier):         self.__query = {                         "typeName": "dwd:Warnungen_Landkreise"                     }         self.__query[                        "CQL_FILTER"                     ] = f"AREADESC='{identifier}'"

Wow, what a lively community in this project!
I have poke a lot around in den dwd geoserver and it seems they erased WARNCELLID from all layers. And not only the layer dwd:Warnungen_Gemeinden is missin on the geoserver, but also, in the json-file for use in the WarnApp -  where WARNCELLID is still the dictionary key - no WARNCELLIDs starting with "8" for type "Gemeine" (municipality) are currently reported.
I seem the have given up reporting my individual municipalities "Gemeine", alt all.
I have sent a request to<EMAIL_ADDRESS>ans asked them to clear up, whether this is a malfunction, an error or an intentional change (which is not yet reflected in their documentation)
BTW: Still having the layer "dwd:Warngebiete_Gemeinden" makes sense, since one can match the individual municipality area polyons ("Gemeinde") to the joint municipality warning areas ("Gemeinden_vereinigt") to determine if a warning is issued for an individual municipality. This is a standard opertation for a geospacial information system and easy in theory but would be an completely unnecessary complication for any project like this.

I've just released v1.0.4 of the api to PyPi. It works with "Landkreise". I'll create a pull-request on HA.
@CDMIUB I'll leave this issue open until you report back what DWD answered to your email.

Hey there,
I got a reply to my email (sent it around the same time):
"es handelt sich wirklich um einen Fehler, der seit letztem Donnerstag auftritt.

Auch unser Feuerwehrinformationssystem ist davon betroffen.
Leider ist die Ursache noch nicht gefunden.
Ich hoffe, dass wir im Laufe des Tages das Problem lösen können."
(It's a bug on dwd's side which they are hoping to fix today).
Thanks for your effort though! I guess the change should be rolledback.

Now they fixed their error. All work done for nothing.
But both versions (1.0.3 and 1.0.4) work with the fixed api.
1.0.4 creates higher loads on the dwd servers but may be more robust.

Although all the work was in the end "fürn Ar..." a big thank you to your guys for going to fix it so quickly!


Not able to suspend CronJob

During maintenance purpose I want to disable all CronJobs, For default Kubernetes CronJob we can execute following command
kubectl patch cronjobs <job-name> -p '{"spec" : {"suspend" : true }}'

However I cannot see an option to do this in CronJobber . Is there a way to disable and enable Cronjob without playing with schedules.

You can do exactly the same with tzcronjobs. Just specify tzcronjobs instead of cronjobs.

@Luis-TT it is not working , I tried following and getting error.
$>  kubectl patch tzcronjob cronjob-runnightlyjobs -p '{"spec" : {"suspend" : true }}'
Error from server (UnsupportedMediaType): the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml

kubectl patch defaults to strategic, which is not supported for Custom Resource types, you need to use a --type=merge strategy.


[WIP] Demonstration on the Rosalin shot-frugal optimization

Title: Frugal shot optimization with Rosalin
Summary: In this tutorial we investigate and implement the Roaslin (Random Operator Sampling for Adaptive Learning with Individual Number of shots) from Arrasmith et al. In this paper, a strategy is introduced for reducing the number of shots required when optimizing variational quantum algorithms, by randomly sampling operators from the cost Hamiltonian.
Relevant references: Andrew Arrasmith, Lukasz Cincio, Rolando D. Somma, and Patrick J. Coles. "Operator Sampling for Shot-frugal Optimization in Variational Algorithms." arXiv:2004.06252 (2020).
Possible Drawbacks: n/a
Related GitHub Issues: n/a

Website build
Commit: 79cbd4e7ee75c8b92871ecbe0b85b7076695335e
Circle build number: 703
Website zip: https://703-214003948-gh.circle-artifacts.com/0/tmp/qml_html.zip
Website url: https://703-214003948-gh.circle-artifacts.com/0/_build/html/index.html
Please double check the rendered website build to make sure everything is correct.


Colors Wrong

using st with :set termguicolors. never had this issue with any other theme using gui* colors.
happens in kitty, too

looked more closely at your image on home page .. strings really are that dark. hmm, I'd reconsider. good luck ♥


Create Log4j informational page

This is designed to inform the public about the exploit and how to take action.
Needs an informed and basic explanation on why and how the exploit works.

note: mkdocs does not support footnotes :(

Need to look into the new CVE


Show old version after update

Version
4.2.2
Environment info
  System:
    OS: Windows 10 10.0.17763
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
  Binaries:
    Node: 13.8.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.13.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.17763.831.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
vue --version
What is expected?
@vue/cli 4.2.2
What is actually happening?
@vue/cli 4.1.1
and warning while I create new project

After update with npm I saw text below
C:\Users\Adv.DESKTOP>npm list -g --depth=0
C:\Users\Adv.DESKTOP\AppData\Roaming\npm
--<EMAIL_ADDRESS>--<EMAIL_ADDRESS>--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>C:\Users\Adv.DESKTOP>vue --version
@vue/cli 4.1.1

C:\Users\Adv.DESKTOP>npm -g install @vue/cli
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
C:\Users\Adv.DESKTOP\AppData\Roaming\npm\vue -><EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules@vue\cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

<EMAIL_ADDRESS>updated 1 package in 55.67s

C:\Users\Adv.DESKTOP>vue info
Environment Info:
System:
OS: Windows 10 10.0.17763
CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Binaries:
Node: 13.8.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.13.6 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.17763.831.0
npmGlobalPackages:
@vue/cli: Not Found
C:\Users\Adv.DESKTOP>

Would you please run yarn global list to see if there's another instance of @vue/cli?

C:\Users\Advart.DESKTOP>yarn global list
yarn global v1.22.0
info "<EMAIL_ADDRESS>has binaries:

quasar
info "<EMAIL_ADDRESS>has binaries:
vue
info<EMAIL_ADDRESS>has binaries:
eslint
info<EMAIL_ADDRESS>has binaries:
gulp
info<EMAIL_ADDRESS>has binaries:
parcel
info<EMAIL_ADDRESS>has binaries:
prettier
info<EMAIL_ADDRESS>has binaries:
yarn-upgrade-all
Done in 2.25s.

That doesn't make sense. There must be an old version of @vue/cli installed somewhere in the system.
Please run where vue (or Get-Command vue if you're using PowerShell) to see where it's installed.

C:\Users\Adv.DESKTOP>where vue
C:\Program Files\nodejs\vue
C:\Program Files\nodejs\vue.cmd
C:\Users\Adv.DESKTOP\AppData\Local\Yarn\bin\vue
C:\Users\Adv.DESKTOP\AppData\Local\Yarn\bin\vue.cmd
C:\Users\Adv.DESKTOP\AppData\Roaming\npm\vue
C:\Users\Adv.DESKTOP\AppData\Roaming\npm\vue.cmd

The first two don't seem right to me. I don't have such files on my system. Maybe you can remove them and see if the new version works.

@sodatea Thank you! Now it's all right


Spike/dispose

This PR add IDisposable to some of our moving parts that (may) need it.
Historically we did not do this because this parts are expected to live for the duration of your application but it does not hurt to be explicit.
SniffingConnectionPools holds a ref to ReaderWriterLock which needs to dispose some events.
Transport held a SemaphoreSlim which really holds a system handle.
The ownership of the semaphore (used for sniffing on startup) moves to ConnectionSettings with this PR because new ElasticClient() implicitly creates a new Transport() each time, eventhough the IConnectionPool interface is already resilient to this it means we create more Semaphores then strictly needed if folks are new'ing clients all the time.
Therefore this PR also introduces some documentation on the recommended life times of our objects.
See this test for more info
The interfaces implement IDisposable for it's Level1 disposables using the pattern as outlined by Stephen Cleary:
http://www.codeproject.com/Articles/29534/IDisposable-What-Your-Mother-Never-Told-You-About
No object disposed exceptions are thrown as the previous article explains:

Instead of checking for the disposed state and throwing an exception, I recommend supporting "undefined behaviour". Accessing a disposed object is the modern equivalent of accessing deallocated memory.

To help prevent getting into this state all the Dispose() methods are explicitly implemented.
More rants against the classical dispose pattern: http://blogs.msmvps.com/peterritchie/2013/01/20/the-dispose-pattern-as-an-anti-pattern/

Sweet, glad this is being sorted. Thanks!

Left one minor nitpick comment, but otherwise this looks good.  Really like the documentation tests. :+1:

Good catch @gmarz updated :+1:


[SPARK-28583][SQL] Subqueries should not call onUpdatePlan in Adaptive Query Execution

What changes were proposed in this pull request?
Subqueries do not have their own execution id, thus when calling AdaptiveSparkPlanExec.onUpdatePlan, it will actually get the QueryExecution instance of the main query, which is wasteful and problematic. It could cause issues like stack overflow or dead locks in some circumstances.
This PR fixes this issue by making AdaptiveSparkPlanExec compare the QueryExecution object retrieved by current execution ID against the QueryExecution object from which this plan is created, and only update the UI when the two instances are the same.
How was this patch tested?
Manual tests on TPC-DS queries.

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/testing-k8s-prb-make-spark-distribution-unified/13572/
Test PASSed.

Test build #108479 has started for PR 25316 at commit 97bce6f.

Test build #108479 has finished for PR 25316 at commit 97bce6f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class InsertAdaptiveSparkPlan(

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/108479/
Test PASSed.

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/testing-k8s-prb-make-spark-distribution-unified/13770/
Test PASSed.

Test build #108685 has started for PR 25316 at commit 1705242.

Test build #108685 has finished for PR 25316 at commit 1705242.

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/108685/
Test PASSed.

LGTM if https://github.com/apache/spark/pull/25316/files#r309864918 is addressed

Test build #108778 has started for PR 25316 at commit f570281.

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/testing-k8s-prb-make-spark-distribution-unified/13859/
Test PASSed.

Merging to master

Test build #108778 has finished for PR 25316 at commit f570281.

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/108778/
Test PASSed.


Can not establish connection with jdbc:iotdb://<IP_ADDRESS>:6667/

Can not establish connection with jdbc:iotdb://<IP_ADDRESS>:6667/. because Required field 'statusCode' was not present! Struct: TS_Status(statusCode:null)

This is due to the version of client and server is not match. Please make sure that your client version is compatible with the server.
0.8.x is only compatible with 0.8.x
0.9.x is only compatible with 0.9.x
0.10.0-SNAPSHOT is only compatible with 0.10.0-SNAPSHOT


Editor GPU: Moving to monitor with different scale breaks rendering

After moving from 100% scale to 200% scale monitor:

Actually fixed this yesterday


panic on HEAD

fn bug() {
let client = Client::new();
let url = "https://www.reddit.com/r/france/search?q=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2V7RI0aehXQ&restrict_sr=on"; // HEAD fails, GET passes
// let url = "https://www.reddit.com/r/france/search?q=https%3A%2F%2Fwww.youtube.com%2F%3D2V7RI0aehXQ"; // fails
// let url = "https://www.reddit.com/r/france/search?q=https%3A%2F%2Fwww.youtube.com%2F%3D"; // passes
// let url = "https://www.reddit.com/r/france/search?q=https%3A%2F%2Fwww.youtube.com%2F"; // passes
eprintln!("pre head|send");
match client.head(url).send() {
    Ok(r) => {
	println!("{:?}", r);
    },
    Err(e) => eprintln!("[error] {}", e)
}
}

backtrace here => http://dpaste.com/3YBZD0W
panic => thread 'reqwest-internal-sync-runtime' panicked at ': ToStrError { _priv: () }', libcore/result.rs:945:5
note: Run with RUST_BACKTRACE=1 for a backtrace.
thread 'main' panicked at 'event loop thread panicked', /home/agumonkey/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.9.1/src/client.rs:482:13
First url failed on HEAD, I tried simplifying it until it caused no more panic. Then I tried GET just in case .. and it doesn't always fail when HEAD fails.
I have no idea what causes that.

The panic was coming from calling val.to_str().unwrap() when getting the LOCATION header. It seems it sometimes contains non-ASCII characters?

It indeed has at least one UTF-8 char: http://unicode.scarfboy.com/?s=é (https://pastebin.com/6CvcXaru line 27)
Could this be hyper not liking reddit 'charset ' parameter or reddit being non RFC compliant ?

It's because RFC 7230 claims that header values should be ASCII, or otherwise the bytes are opaque (the encoding can't be inferred). So, HeaderValue::to_str will return an error if the bytes aren't ASCII, since it can't by default assume to use UTF-8.
I've updated reqwest in this specific instance to simply try to decode as UTF-8. This has been published in 0.9.2.

Thanks a lot. I apologize if this wasn't supposed to be reqwest's job (I'm new in the rust ecosystem)


Shuttingdown the Keyboard

I seem to be having issues shutting the keyboard down both when I press the ON/OFF button and then I do the SHUTDOWN keycode. It shuts down for a second and then comes back on. Is there anyway to be able to shutdown the keyboard entirely until I press the ON/OFF button again?

Do you have USB connection?
When USB is connected, it will not shutdown.
When USB is disconnected, holding down the ON/OFF for more than 3 seconds will shutdown the keyboard. Fn + b will also shutdown the keyboard.

Yeah I have been trying this as well, but it is still turning on immediately after. The suspend function seems to work as intended tho

That's weird. When the keyboard is powered by the battery, any reset should power off the keyboard.
With the default keymap, The BOOT keycode (Fn + b) will reset the keyboard, and only run the built-in bootloader if powered by USB. If powered by the battery, the keyboard will power off before getting a chance to run the bootloader.


control-service: remove deprecated classes in codebase.

Why
We want to remove dependencies on all deprecated classes to enable us to upgrade at a later date
How has this been tested?
unit and integration tests.
Signed-off-by: murphp15<EMAIL_ADDRESS>

to enable us to upgrade
To upgrade what ? Can you clarify in the PR description.


Allow usage of the chocolatey.org/install.ps1 to be overridden

Checklist

[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.
There are a couple places where the Chocolatey install script is pulled from https://chocolatey.org/install.ps1 where it would be good to allow overriding it in some fashion, so that we can test functionality or building Boxstarter prior to publishing updates to the script, and ensure we're not breaking the things in Boxstarter that use the install.ps1
Describe The Solution. Why is it needed?
Allow overriding the install.ps1 URL with either another URL or a file path, perhaps by looking up an environment variable or some other mechanism to permit it to be overridden in places where it is currently used.
Additional Context
No response
Related Issues
No response

@mwallner @flcdrg I think this has already been discussed in Discord, however, we need to remove the Chocolatey CLI installation script from Boxstarter and use the one at https://community.chocolatey.org/install.ps1.
Are either of you able to test Boxstarter using this new script?
@gep13 would it be possible to bring the new script in each time a release is done?

I can look into this in the next couple of days, note that we still need to be able to use the bundled/offline Installer in some scenarios - will try to come up with a list of the different options available for initial deployments.

@pauby said...
@gep13 would it be possible to bring the new script in each time a release is done?

It could certainly be added to the release process to do this, would be better if this was automated though, rather than requiring human work.

@gep13 said
It could certainly be added to the release process to do this, would be better if this was automated though, rather than requiring human work.

I wasn't expecting this to be done manually but through automation.

imo the most efficient way of reducing the usage of https://chocolatey.org/install.ps1 would be as follows:

rip out old/unused code and modules (looking at you, Boxstarter.Testrunner, Boxstarter.Azure) - that'd reduce the number of different bootstrapping-paths
evaluate IF we may remove the usage of the boostrapping-url altogether, we need to be able to use the bundled version of chocolatey.nupkg anyway (remote + fully-contained scenarios)
replace hardcoded strings to the install script with a Get-BoxstarterChocolateyBootstrapURL function, inside the function, look if a env-var (something like env:BoxstarterChocoBootstrapUrl) is defined, otherwise fall back to the official url

@vexx32  / @pauby - how would you feel about adding ad $env:BoxstarterChocoBootstrapUrl => if this is set prior to bootstrapping Boxstarter, it will use this environment variable to fetch the chocolatey install script from.
NOTE: if choco is being bootstrapped from https://chocolatey.org/install.ps1, also .net framework 4.5 (4.0.30319) will be installed beforehand atm. (which is outdated as minimum requirement iirc)

how would you feel about adding ad $env:BoxstarterChocoBootstrapUrl => if this is set prior to bootstrapping Boxstarter, it will use this environment variable to fetch the chocolatey install script from.

This sounds like a good idea to me.


Document propertysource reload file watch option

The reload options in the current documentation all require calling the k8s API. This is why we are told that to "access ConfigMaps on OpenShift the service account needs at least view permissions".
But if we mounted the ConfigMap as a volume we could still watch the file for changes. There's an example of doing this in the JHipster Registry project by @srinivasa-vasu. This kind of hot loading wouldn't require any service account. It would be an approach to using configmaps with java that is closer to that with other languages and still allow for hot loading. (See 'Centralized configuration in Kubernetes' section of https://www.jhipster.tech/kubernetes/ for more info.)
This is just a suggestion. I've not actually thought any further than the above for what would be involved in implementing it.

If it's just watching a file, I don't think that is specific to kubernetes at all.

Apologies, I should have put more thought into this before raising. Perhaps it should be a Spring Boot or Spring Cloud feature request. I also apologise if my comments seemed critical - this project is providing great tools and options for Spring developers. I am wondering if there's a further option that could be offered.
Here is a use-case I have in mind. Imagine that a developer is tasked with porting an existing app to Kubernetes. It makes extensive use of '@RefreshScope' but the Architect now wants to use different ConfigMaps for different services. Spring Cloud Kubernetes would be an obvious choice in this scenario. But the cluster admin isn't happy about creating service accounts. (Based loosely on https://stackoverflow.com/questions/50097597/rabbitmq-as-spring-cloud-bus-in-kubernetes-for-spring-boot-applications/50113708?noredirect=1#comment87677210_50113708)
It would save this imaginary developer time and politics if there were a way to watch for config changes without needing a service account. Then they could mount the application.properties to the /config/ directory and use Spring Boot's externalised configuration feature. This would also have the merit of using the volume mount pattern prominent with k8s apps, which is already being prominently used (https://github.com/trisberg/devoxx-spring-boot-k8s/blob/master/actors/config/actors-deployment.yaml) and recommended (https://stackoverflow.com/a/50462990/9705485) for scenarios without use of RefreshScope and which the README for the Spring Cloud Kubernetes project recommends for Secrets (it currently notes "access to secrets via API may be restricted for security reasons, the preferred way is to mount secret to the POD").
Here I am assuming that if I did set up a Spring Boot app to read an externalised application.properties and I were to make a change to that file then there is nothing in the Spring ecosystem currently that I could use to detect that change and automatically trigger a refresh (https://stackoverflow.com/questions/39387272/reload-property-value-when-external-property-file-changes-spring-boot). It seems a solvable problem if the file can be watched and refreshes programmatically triggered.
Perhaps there is good reason against providing such a feature. Maybe it would encourage overuse of @RefreshScope? Presumably that is why reload is disabled by default in Spring Cloud Kubernetes? Or other disadvantages that I am overlooking?

Blocked by https://github.com/spring-cloud/spring-cloud-commons/issues/605

I agree would be good for the next major

Closing this in favor of https://github.com/spring-cloud/spring-cloud-commons/issues/605


Using same version of preact for pre-rendering

Fixes #795
What kind of change does this PR introduce?
Fixes duplicate preact problem.
Did you add tests for your changes?
Already exist
Does this PR introduce a breaking change?
No

Maybe we should add a note on that somewhere in the FAQ maybe? or Readme?

about the comments i added?

Well..... For users. I think users will expect the user-land preact to affect pre-rendering Preact.

Note: I really wanted both bundle and pre-rendering.js to use preact from user land but sadly doesn't work that way. Can anyone help tell me why
// @marvinhagemeister

@hassanbazzi I updated the PR to use modules from user land instead its just that it has an added step of installing preact-render-to-string in user land

Not entirely sure how to write a test for it

:| this was breaking the current tests....
i'll add the fix for tests ASAP

I already have it


Network Firewall Rules on the Storage Account

Is it possible to configure network restrictions via the Storage Account Firewall and still allow the Genomics service to read the input and save the output data?

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

ID: 8fcb147c-ad94-4926-6cec-da6013c6006a
Version Independent ID: a2a1e627-0b49-4757-51b3-9a1e3ddd432e
Content: Quickstart: Run a workflow - Microsoft Genomics
Content Source: articles/genomics/quickstart-run-genomics-workflow-portal.md
Service: genomics
GitHub Login: @grhuynh
Microsoft Alias: grhuynh

thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

At this time this is not possible. You could possibly get something working with a pretty big hole in the firewall to allow access from a wide-range of batch server IP addresses, but likely not what you really want.

At this time this is not possible. You could possibly get something working with a pretty big hole in the firewall to allow access from a wide-range of batch server IP addresses, but likely not what you really want.

No. Ideally it have been a little more specific. Without a Service Tag for Azure Batch either it'd be overhead to maintain.
Thanks for confirming 👍

No. Ideally it have been a little more specific. Without a Service Tag for Azure Batch either it'd be overhead to maintain.
Thanks for confirming 👍


[BUG] shift return the wrong result of zero array

That looks correct to numerical precision. Is the concern the near-zero values that aren't truly zero? If so I think this is more of a documentation issue than a bug.

Get it, thanks


Bump version in docker hub

Hello!
Could you be so kind to rebuild docker hub image using the latest nginx:alpine-stable? It got TLS 1.3 support in 1.14 but your image seems to be built upon older version.
Thanks!

done

nginx version: nginx/1.14.0```
Thank you!


Make laboratory out of the platform

Share resources and results.
E.g., enable people to share stories through Medium or other blog types.

Duplicate of #51


fix: multi thread error on matplotlib default backend

The following script consistently fails when the multi-threading option is active, entering an infinity loop triggered by matplotlib backend. The fix consists in temporarily changing the backend while creating the plots (ty @fabclmnt for the help with this one).
import pandas as pd
import numpy as np

from pandas_profiling import ProfileReport

def create_dataframes(size=1000, alt=False):
    size = size if not alt else size * 2
    time_steps = np.arange(size)

   df1 =  pd.DataFrame(
        {
            "sin": map(lambda x: round(np.sin(x * np.pi / 180), 2), time_steps),
            "gaussian": map(lambda x: round(x, 2), np.random.normal(0, 1, size)),
        }
    )

    df2 = pd.DataFrame(
        {
            "sin": map(lambda x: round(np.sin(x * np.pi / 180), 2), time_steps),
            "miss2": np.random.choice([0, 1, 2, 3, np.nan], replace=True, size=size),
         }
    )

    return df1, df2

if __name__ == '__main__':
    df1, df2 = create_dataframes()
    prof1 = ProfileReport(df1, title="p1")
    prof2 = ProfileReport(df2, title="p2")
    prof1.to_file("p1.html")
    prof2.to_file("p2.html")

Codecov Report
Base: 90.90% // Head: 90.90% // No change to project coverage :thumbsup:

Coverage data is based on head (02bdfc9) compared to base (36fad3c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1149   +/-   ##
========================================
  Coverage    90.90%   90.90%
========================================
  Files          178      178
  Lines         5090     5090
========================================
  Hits          4627     4627
  Misses         463      463

Flag
Coverage Δ

py3.8-ubuntu-latest-pandas
90.90% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/pandas_profiling/visualisation/context.py
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Sync book-store

[x] Run bin/configlet sync -u -e book-store --yes --docs --filepaths --metadata --tests include (updates the Markdown files and maybe tests.toml)

docs: instructions unsynced: book-store

[x] Drop strict types comments from test file and example code (these are useless)
[ ] Add and sync test meta data to tests (uuid / @testdox in DocBlocks)
[ ] Decide on adding / adjusting / ordering test cases to match current problem specs

book-store: missing 3 test cases

Do not redesign the student's interface or add test cases that would invalidate existing community solutions. These are extra tasks, which should be discussed in advance.

OK, this exercise has some complicated issues...

The canonical data states "implementors should use proper fixed-point or currency data types of the corresponding language and not float." Our implementation currently uses float. We may opt to use int and cents as the canonical test data contains them already or continue using float.
assertEquals() is not appropriate for float values. There is assertEqualsWithDelta() for floating point comparison. This might already make the current example code pass the tests.
The missing tests seem to be those that "optimize" the price for cases with 5 different books but a group of 5 is not the optimum. I do not know the history of the exercise, but these seem to be added to catch edge cases of optimizing. I think we should have them.

Any additional findings / thoughts?

My 5cents.

I would go for int as that is the right way to handle amount in PHP, if not using a money library.

The assertEqualsWithDelta() would not be needed then.

I think we should include all test cases, en ever exercise, unless there are some functionality in PHP making it super hard or impossible.

I have forgotten have to look up how many people have already solved the exercise, and how many it would break for.

@homersimpsons Your opinion about 1. / 2.? Proper float comparison or using int instead?

I know I always prefer int for monetary values. I think it is a good way to show students that this could be used and avoids most rounding issues. It may helps them in the future too when they wil handle monetary values.
I would prefer to avoid float here. Another alternative could be to use BCMath.
So my vote is (from most preferred to least preferred) int > bcmath >> float.

There is 61 solutions, only ~40% of 153 people who tried this. So this should be improved.

61 solutions looks fine for me to change this completely.

OK, thanks everybody. We agreed on int and as we break existing solutions with that we will have all test cases with exactly the data from canonical data. @tomasnorre please continue with the PR.

I'll take care tomorrow or beginning of next week.


subscription: Remove unnecessary select_related fields and clean up.

Follow-up to create stream: Faster stream creation

Remove extra unnecessary select_related fields from bulk_access_users_by_email and bulk_access_users_id

bulk_access_user_queryset -> used when fetching a user other than the acting user

_base_user_queryset -> used when fetching the acting user, prefetching more fields

Addressed the Review comments
Add bulk_access_user_queryset

I did a bit more work on naming and also adjusted the place in #31808. I'm still not convinced the various models.py functions make the best use of these helpers, but this version is definitely progress.

Merged, thanks @abdelrahman725!


Add trailing commas to the existing codebase where necessary

We decided to use trailing commas in case of multiple lines as PEP 8 recommends.
The current codebase has to be re-formatted to include these commas.

This is now done.


Discussions: Show usernames when hovering over reactions

Is your feature request related to a problem?
When using reactions on posts or answers in the discussion tab, there seems to be no way for other users to tell who the author of these reactions is.
Describe the solution you'd like
Show the names of the users who used the reaction when hovering over it.
Example: Zulip

Describe alternatives you've considered
No response
Additional context
No response

I am working on a solution :) thanks for the input!


Fix crash

When the player is set velocity, the server will crash
I may be too anxious

Can you for the love of god follow the PR template? I have literally 0 information on this issue and what exactly it fixes. Also provide more detail in the name of the PR.

Can you for the love of god follow the PR template? I have literally 0 information on this issue and what exactly it fixes. Also provide more detail in the name of the PR.

I made a mistake, it is different from https://github.com/Cubed-Development/Modern-Warfare-Cubed/pull/146 correlation

Can you for the love of god follow the PR template? I have literally 0 information on this issue and what exactly it fixes. Also provide more detail in the name of the PR.

When the player is set velocity, the server will crash

Can you for the love of god follow the PR template? I have literally 0 information on this issue and what exactly it fixes. Also provide more detail in the name of the PR.

When the player is set velocity, the server will crash

Please provide a crash report

I will just redo that entire config on Monday


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/523 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 74682df:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


kustomize buildoptionはvaluesではなくmanifestからpatchを当てる

ArgoCD導入時のhelmのvaluesで変更しようとすると

Plan Result
CI link
Plan: 0 to add, 1 to change, 0 to destroy.

Update

helm_release.argocd

Change Result (Click me)

  # helm_release.argocd will be updated in-place
  ~ resource "helm_release" "argocd" {
        id                         = "argocd"
      ~ metadata                   = [
          - {
              - app_version = "v2.9.3"
              - chart       = "argo-cd"
              - name        = "argocd"
              - namespace   = "argocd"
              - revision    = 2
              - values      = jsonencode(
                    {
                      - configs = {
                          - cm = {
                              - create    = true
                              - kustomize = {
                                  - buildOptions = "--enable-helm"
                                }
                            }
                        }
                    }
                )
              - version     = "5.51.6"
            },
        ] -> (known after apply)
        name                       = "argocd"
        # (26 unchanged attributes hidden)

      - set {
          - name  = "configs.cm.kustomize.buildOptions" -> null
          - value = "--enable-helm" -> null
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

:white_check_mark: Apply Succeeded
CI link
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
Details (Click me)
Acquiring state lock. This may take a few moments...
helm_release.argocd: Refreshing state... [id=argocd]
google_project_service.project_service["compute.googleapis.com"]: Refreshing state... [id=infra-403801/compute.googleapis.com]
google_project_service.project_service["apigateway.googleapis.com"]: Refreshing state... [id=infra-403801/apigateway.googleapis.com]
google_project_service.project_service["cloudresourcemanager.googleapis.com"]: Refreshing state... [id=infra-403801/cloudresourcemanager.googleapis.com]
google_project_service.project_service["iam.googleapis.com"]: Refreshing state... [id=infra-403801/iam.googleapis.com]
google_project_service.project_service["servicecontrol.googleapis.com"]: Refreshing state... [id=infra-403801/servicecontrol.googleapis.com]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # helm_release.argocd will be updated in-place
  ~ resource "helm_release" "argocd" {
        id                         = "argocd"
      ~ metadata                   = [
          - {
              - app_version = "v2.9.3"
              - chart       = "argo-cd"
              - name        = "argocd"
              - namespace   = "argocd"
              - revision    = 2
              - values      = jsonencode(
                    {
                      - configs = {
                          - cm = {
                              - create    = true
                              - kustomize = {
                                  - buildOptions = "--enable-helm"
                                }
                            }
                        }
                    }
                )
              - version     = "5.51.6"
            },
        ] -> (known after apply)
        name                       = "argocd"
        # (26 unchanged attributes hidden)

      - set {
          - name  = "configs.cm.kustomize.buildOptions" -> null
          - value = "--enable-helm" -> null
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.
helm_release.argocd: Modifying... [id=argocd]
helm_release.argocd: Still modifying... [id=argocd, 10s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 20s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 30s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 40s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 50s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 1m0s elapsed]
helm_release.argocd: Still modifying... [id=argocd, 1m10s elapsed]
helm_release.argocd: Modifications complete after 1m18s [id=argocd]
Releasing state lock. This may take a few moments...

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.


[SUBS] Add more extension points

Problem

As a developer I'd like for my app to be able to easily respond to the widget through events and callbacks

Solution

The solution should follow a clear use case as defined by a community project or target integration

I think this issue is underspecified.
Current callbacks:

onButtonClick -  fires when any button is pressed, the callback can filter to react to specific button presses based on the parameter buttonType which is passed in.
onRouteChange - fires when we go from PaymentOption -> Wrap -> Review etc. Passed in parameter is the actual step we changed to.
onTransactionSent -> fires when we sent a transaction, the passed in parameter is the transaction hash
onSuccess -> fires when a stream has started
onSuccessButtonClick - @deprecated in favor of onButtonClick
onPaymentOptionUpdate - fires when the user changes paymentOptions

Lets specify what do we need.


SA1649 - File name must match first type name - false positive error

This rule mistakenly fires for files with double postfix names, i.e.
File "AppEventReceiver.svc.cs"
That contains class:
public class AppEventReceiver : AppEventReceiverBase
Will fire the rule. It shouldn't and it doesn't in the original stylecop tool. .
Fix should be fairly easy by using the filename "before the first dot" instead of "filename without extension" for matching the class name.
And thanks for a great tool :-)

Thanks for the report. I think that makes sense, and it should definitely be an easy fix :+1:

Well this didn't qualify as easy after all - it required modifications to the test framework to allow testing these cases. But I got it working!

Fantastic, thanks! :-)
Looking forward to RC1.


feat(delivery): move common app setup to script file

This is an experimental-ish PR

Extracted from #387
In furtherance of #347

N.B: This does NOT include the gcloud run deploy steps; perhaps it's worth creating a follow-up issue for those.

Met with @grayside today; we decided that instead of

importing manually-created IAM permissions
we should:
give the Cloud Build Service Account (CBSA) permissions to create those permissions itself

We should document that decision as a decision record, given that it may compromise project security.


Gamepad names

What problem does this solve or what need does it fill?
Bevy uses Gilrs for gamepad support. Gilrs knows the names of all detected gamepads. E.g. when I connect a Nintendo Switch Joy-Con, the gilrs ev example prints:
Power info of gamepad 0(Joy-Con (R)): Unknown

Bevy, however, doesn't take this information into account. Thus, within bevy, I can only identify gamepads by their id which is not a nice user experience when I want to have an in-game menu where a user can choose between multiple selected gamepads.
What solution would you like?
Extending the Gamepad struct with a name would require cloning a lot of String types around, maybe a better solution would be to have a Resource HashMap<Gamepad, String> which would allow getting the name of a gamepad when needed?
What alternative(s) have you considered?
I suppose I could directly import gilrs and get the names from there, but that would be quite the overhead.

Extending the Gamepad struct with a name would require cloning a lot of String types around, maybe a better solution would be to have a Resource HashMap<Gamepad, String> which would allow getting the name of a gamepad when needed?

IMO we can put this in the existing Gamepads resource, which tracks the registered game pads :)


Fix stretch for custom branding image in Safari on sign up page

Summary
This PR applies the fix known from https://github.com/mattermost/mattermost-webapp/pull/10862 (login page) now also for the sign up page.
Ticket Link
https://mattermost.atlassian.net/browse/MM-46522
Screenshots

before
after

Release Note
NONE

Hello @phpfs,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/232262


Upgrade microk8s to 1.28

Microk8s 1.28 has serialized pulls disabled by default.

/canonical/self-hosted-runners/run-workflows 38f986f

/canonical/self-hosted-runners/run-workflows 38f986ff7bc769db1bb00c5be3efb6e41bfd4397

Can we check any impacts on snap-openstack in case of refresh of existing snap with microk8s 1.26-strict/stable installed.

We can, but merging this in sunbeam-terraform shouldn't impact that ?


Use Docker volumes for cosmos chains

A major milestone towards completing #200.
The remaining work will be to respect IBCTEST_SKIP_FAILURE_CLEANUP for
volumes, and adjusting the penumbra and internal/tendermint packages to
also use Docker volumes.

This commit ended up as part of #219.


Association between a service worker and global objects

In section 4.2.4 step 9.4, the source of the MessageEvent is set to a ServiceWorker object that represents the service worker associated with the global object specified by the incumbent settings object.
How is a service worker associated to the global object?
cc @annevk

Also, it seems .source should be set to the ServiceWorker object that corresponds to the service worker where the message originated, which isn't really what this seems to define.

How is a service worker associated to the global object?

ServiceWorkerGlobalScope has an associated service worker: https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#dfn-service-worker-global-scope-service-worker
Just missed the xref url to it. Fixed: cdb025b9f035fe6a660c5bc19896d77776b7fc57

.source should be set to the ServiceWorker object that corresponds to the service worker where the message originated

It's set to the right one that corresponds to the service worker associated with the ServiceWorkerGlobalScope object, as just explained above, who's posting this message.

Closing.

Relevant blink bug: crbug.com/403693


Newest pylint (2.15.4) has intriduced some new rules.

See error when running pre-commit run --all-files

I think we should consider "pinning"/allowing a more restrictive range of pylint versions (as discussed offline). So instead of having the dependency be pylint~=2.15, which is equal to pylint>=2.15,<3, it should probably only allow a specific minor version at a time, i.e.: pylint~=2.15.0 or similar, which is equal to pylint>=2.15.0,<2.16.
An alternative is to use == and stick to a single specific version at any given time. While this, honestly, might be the best solution for this package, it also gives rise to certain issues/annoyances:

Many more pylint package dependabot PRs.
A possibility to lose out on automatically published hotfixes.

Hmm... I don't think that we have run into a situation where it is impossible to keep up with pylint restrictions yet. I'd rather keep it as is and try to stay on top of new released suggestions for improved code (but one can also decide on a team-level to disregard certain rules, altough I prefer to keep this to an absolute minimum).


Make apache/orc-dev:centos7 up-to-date with ORC-1322

This issue aims to publish the result of https://github.com/apache/orc/pull/1325
BEFORE

AFTER

$ docker run -it --rm apache/orc-dev:centos7 /opt/rh/devtoolset-9/root/usr/bin/g++ --version
g++ (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This is done.
cc @wgtmac and @williamhyun


Release 1.0.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.727%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
67

Relevant Lines:
126

💛  - Coveralls


Ability to change the close button view.

Right now, the close button is hardcoded, which does match my UI style. It would have been helpful if there was an ability to pass a view instead of Image(systemName: "xmark.circle")

Hi Nijinsha!
I'm not sure what you're asking for. As you can see in UsageExample.swift, you are completely free to customize the toolbar of the SymbolsPicker view and add whatever close button you want. Image(systemName: "xmark.circle") is only the example I provided.
The SymbolsPicker view is only about the list of symbols and the relative search bar, it does not involve any close button or other navigation items. I opted for this approach recently precisely to leave freedom of navigation.
Let me know if I answered your question.

I meant this line of  code
Is there a way to change this systemImage?

Sorry for the misunderstanding, now I understood the request. I just released version 1.0.6 of the package which adds the ability to specify a custom close button.


Improve coloring

The coloring is inconsistent between operating systems: on Windows, the color tone is a bit muted in comparison with Linux, for instance.
Edit: Upon investigation, it seems that the difference is due to the fact that the Windows implementation has an sRBG surface format, where on my Linux it falls back to Brgba8Unorm

Note: https://github.com/gfx-rs/wgpu/wiki/Texture-Color-Formats-and-Srgb-conversions explains this better.


output logging for file_watch

Codecov Report

Merging #595 into master will decrease coverage by 74.26%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #595       +/-   ##
===========================================
- Coverage   90.13%   15.86%   -74.27%
===========================================
  Files          41       40        -1
  Lines        3172     3094       -78
===========================================
- Hits         2859      491     -2368
- Misses        313     2603     +2290

Impacted Files
Coverage Δ

vent/core/rq-dashboard/rq_dash_settings.py
0% <0%> (-100%)
:arrow_down:

vent/core/rq-worker/settings.py
0% <0%> (-100%)
:arrow_down:

vent/core/rq-worker/test_rq_worker.py
6.66% <0%> (-93.34%)
:arrow_down:

tests/test_menu.py
9% <0%> (-91%)
:arrow_down:

vent/core/file-drop/test_file_drop.py
12.5% <0%> (-87.5%)
:arrow_down:

vent/api/plugins.py
8.2% <0%> (-85.19%)
:arrow_down:

vent/api/actions.py
9% <0%> (-84.79%)
:arrow_down:

vent/api/menu_helpers.py
7.79% <0%> (-83.99%)
:arrow_down:

vent/menus/inventory.py
8.92% <0%> (-83.93%)
:arrow_down:

vent/menus/help.py
17.39% <0%> (-82.61%)
:arrow_down:

... and 28 more

Continue to review full report at Codecov.

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


fix url decoding ( '+' is not decoded to ' ' anymore)

We had the problem that users write a '+' in the editor. And after saving this the '+' change to a ' '.
The java URLDecoder class has an unexpected behavior regarding the '+' character.

@wasabeef what about this PR ?