Fix : View challenges button does not fix to the bottom of card

Fixed: #93
@rishipurwar1  Kindly review the changes, I have tested the changes on the live site using the devtools

PR has merge conflict please resolve it.


Add new logo and header designs

Related Issue or Background Info
Resolves #476.
Additional Information

design done, may want to go back and clean-up code

Screenshots / Demos

@katiealoisi @hmyers-cms I added screenshots of the new header to the PR. What do you think?

@katiealoisi @hmyers-cms I added screenshots of the new header to the PR. What do you think?

It looks great @maya ! thumbs up from me and @hmyers-cms

It looks great @maya ! thumbs up from me and @hmyers-cms


lseek should return the resulting offset

According to posix, lseek returns the resulting offset.

So true. I'll just need to patch the tests also before pulling this in,
sometime next week . Thanks!
Den 6 jul 2015 18:18 skrev "Hans-Erik Floryd"<EMAIL_ADDRESS>
According to posix, lseek returns the resulting offset.
You can view, comment on, or merge this pull request online at:
https://github.com/pellepl/spiffs/pull/27
Commit Summary

lseek should return the resulting offset

File Changes

M src/spiffs_hydrogen.c
https://github.com/pellepl/spiffs/pull/27/files#diff-0 (2)

Patch Links:

https://github.com/pellepl/spiffs/pull/27.patch
https://github.com/pellepl/spiffs/pull/27.diff

—
Reply to this email directly or view it on GitHub
https://github.com/pellepl/spiffs/pull/27.


[master] Bug 1324596 - [GSS] [6.2.z] 6.2.2 unable to open/edit some assets with specific user

(cherry picked from commit c181908753e20512bad67c342d32c4ae6af13277)

jenkins please retest

@manstis This can go in once the build passes and it gets +1

+1 to merge.


"The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer."

Description
Many of my pipelines require resources on an external network and so I have a job to connect to a VPN.
As of 24th January GMT, The VPN connection job has failed with error:
"Remote Access error 789 - The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer"
This is a similar issue that was plaguing Windows 10/11 installs recently: https://docs.microsoft.com/en-us/answers/questions/691993/can39t-connect-to-any-vpn-after-today39s-windows-u.html
I don't think i'm able to uninstall updates on the build images so I am currently blocked in any of my pipelines on Microsoft hosted agents. I have tried windows-2019 and windows-2022.
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Starting: Initialize job
Agent name: 'Hosted Agent'
Agent machine name: 'WIN-BIQBKUFF0CU'
Current agent version: '2.196.2'
Operating System
Virtual Environment
Virtual Environment Provisioner
Current image version: '20220116.1'
Is it regression?
yes, last success was on image '20211219.1'
Expected behavior
No response
Actual behavior
No response
Repro steps

Attempt to connect to an L2TP VPN as part of a pipeline

Hello @aalohr-pt!
unfortunately we can not manage camulative updates, the only way is probably using a different vpn service. I believe someone at https://github.community/ has come across this problem too, so we highly recommend asking for help there, but please feel free to reach us out again if you have questions left.


[Feature request]I have an idea

展开收起之后Luckysheet宽度不能自适应

The width of the Luckysheet is not adaptive after unfolding

yes, I have kinda fixed this issue by using a hack react resize dector, by calling luckysheet.resize() whenever the parent div changes size but implementing this on luckysheet would be nice

yes, I have kinda fixed this issue by using a hack react resize dector, by calling luckysheet.resize() whenever the parent div changes size but implementing this on luckysheet would be nice

The problem is solved. Thank you


Removing restriction of mandatory fields in list()

Cisco Spark APIs has now made "displayName" and "email" as optional fields to list the people in an organization. Changing the code in such a way that "displayName" and "email" specification are optional.

Awesome!  Thank you @Deepar3292 !  I will review the changes shortly and merge your pull request if there are no issues.  -Thank you for your contribution!


http://p5js.org/js/p5.min.js - 404 not found

the p5 libraries are not found for me.
I tried all browsers I have.

<title>404 Not Found</title>

404 Not Found

nginx

thanks. can you tell which page this is linked from, or where the broken link is?

ah nevermind, I understand the problem, thank you! will look into it.


Implement abcast and sbcast

Implement asynchronous and synchronous broadcast functionality (abcast
and sbcast)
Implement tests for above functionality
Update documentation

Changes Unknown when pulling 52e1132399856bf2360ddafb934a550da78291f3 on feature/broadcast_functions into ** on master**.


adds podman support

Hello, Please feel free to ignore this PR, but since I did the work, I thought I'll at least offer it.
I'm running on Fedora as my base machine, and was unable to run the container due to selinux limitations, I ended up rebuilding a new container based on fedora.

Hi @ohadlevy,
Thanks for the contribution! I apologize it has taken me a while to get around to review.
I am not familiar with docker myself. The existing docker configuration was contributed by another community member. Could you explain the benefits of this configuration as well as how to use it?

Hi,
The main value (for me) ws the ability to run it on my system, the base container that is currently offered does not follow SELinux and my system ended up rejecting the various network configuration changes.
another plus (for me again) that I was able to build it using podman vs docker, as docker is slowly phasing out on some common distributions.
in order to test it, I've published the image at quay.io/ohadlevy/tuya, so if you are using docker-compose you could simply change the image reference (from tuya:latest to quay.io/ohadlevy/tuya:latest)

Hi, I originally added the docker-functionality on tuya. The main reason that I used a ubuntu-based image was that I could use install_prereq.sh without problems. I'll try @pdugas approach (https://github.com/ct-Open-Source/tuya-convert/issues/796) with a an alpine-image.
@ohadlevy Your image btw. isn't specific to podman, it would work perfectly well with docker, since these buildfiles are interchangeable after OCI (Open Container Initiative). It is just using an fedora-minimal instead of a ubuntu-minmal image inside the container.
I know it's a long time since you opened the PR, but do you still know some errors you got? Did you build from original Dockerfile in this project with docker or podman?
Since fedora prefers podman and you need to change some internals to get docker working (https://fedoramagazine.org/docker-and-fedora-32/) podman would be the way to go. Normally everything from the README should be interchangeable for podman (for example use "podman build" instead of "docker build" and podman-compose instead of docker-compose)

Hi, I originally added the docker-functionality on tuya. The main reason that I used a ubuntu-based image was that I could use install_prereq.sh without problems. I'll try @pdugas approach (https://github.com/ct-Open-Source/tuya-convert/issues/796) with a an alpine-image.
@ohadlevy Your image btw. isn't specific to podman, it would work perfectly well with docker, since these buildfiles are interchangeable after OCI (Open Container Initiative). It is just using an fedora-minimal instead of a ubuntu-minmal image inside the container.
I know it's a long time since you opened the PR, but do you still know some errors you got? Did you build from original Dockerfile in this project with docker or podman?
Since fedora prefers podman and you need to change some internals to get docker working (https://fedoramagazine.org/docker-and-fedora-32/) podman would be the way to go. Normally everything from the README should be interchangeable for podman (for example use "podman build" instead of "docker build" and podman-compose instead of docker-compose)

I know it's a long time since you opened the PR, but do you still know some errors you got? Did you build from original Dockerfile in this project with docker or podman?

the main issue was with SELinux alerts on my host machine, I assume it depends on the base image (e.g. ubunutu) and usage of host networking. using a fedora based image eliminated that concern. regardless, if alphine works, I'm more than happy :)
I actually built it using quay, which is building using docker (I think) but it worked just as well on my local podman instance.


type parameter: some methods with specific types can't be compiled if return types contains the specific type

What version of Go are you using (go version)?

$ go version
go version devel go1.18-3396878af4 Sat Dec 4 17:16:07 2021 +0000 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/smallnest/Library/Caches/go-build"
GOENV="/Users/smallnest/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/smallnest/go/pkg/mod"
GONOPROXY=""
GONOSUMDB="*"
GOOS="darwin"
GOPATH="/Users/smallnest/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/Users/smallnest/sdk/gotip"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/smallnest/sdk/gotip/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="devel go1.18-3396878af4 Sat Dec 4 17:16:07 2021 +0000"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qj/vk5g8vfs09s94dg375c1db700000l2/T/go-build1693723073=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I have defined a List[T any] type and defined a generic method Len. I have also defined some methods for specific types.
Some methods with specific types can be compiled but some can't:
package type_parameter

type List[T any] struct {
	next  *List[T]
	value T
}

func (l *List[T]) Len() int {
	return 0
}

func (l *List[string]) Length() int {
	return 0
}

// Wrong!!!
// func (l *List[int]) Size() int {
// 	return 0
// }

func (l *List[int]) Say() string {
	return "hello List[int]"
}

// Wrong!!!
// func (l *List[string]) Greet() string {
// 	return "hello List[string]"
// }

What did you expect to see?
All methods with  specific types can't be defined or all methods with specific types can be defined. It should keep consistent.
What did you see instead?
If types in return of methods with specific types contains the specific type, the method can't be compiled, for example,(l *List[int]) Size() int and (l *List[string]) Greet() string can'r be compiled :
func (l *List[int]) Size() int {
	return 0
}
func (l *List[string]) Greet() string {
	return "hello List[string]"
}

func (l *List[int]) Size() int {
   return 0
}

This doesn't do what you think it does. The current type parameters design doesn't allow specialization. Above, List[int] is exactly like List[Y], in other words it's an undefined type parameter named int, that shadows the pre-declared identifier int.
See #47419.


docs: readme

Hey. I added the missing links. Please review

Checklist:

[ ] My code adheres to the established style guidelines of this project.
[ ] I have conducted a self-review of my code.
[ ] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

Thanks for this @Olexandr88


RuntimeError: Windows not yet supported for torch.compile

Is it simply because the win environment does not support torch.compile?
Even it can still generate images, are there any solutions to fix it?  Thanks!

RuntimeError                              Traceback (most recent call last)
Cell In[4], line 2
1 models = WurstCoreC.Models(
----> 2    **{**models.to_dict(), 'generator': torch.compile(models.generator, mode="reduce-overhead", fullgraph=True)}
3 )
5 models_b = WurstCoreB.Models(
6    **{**models_b.to_dict(), 'generator': torch.compile(models_b.generator, mode="reduce-overhead", fullgraph=True)}
7 )
File ~\anaconda3\envs\casada\lib\site-packages\torch_init_.py:1723, in compile(model, fullgraph, dynamic, backend, mode, options, disable)
1720 else:
1721     backend = _TorchCompileWrapper(backend, mode, options, dynamic)
-> 1723 return torch._dynamo.optimize(backend=backend, nopython=fullgraph, dynamic=dynamic, disable=disable)(model)
File ~\anaconda3\envs\casada\lib\site-packages\torch_dynamo\eval_frame.py:583, in optimize(backend, nopython, guard_export_fn, guard_fail_fn, disable, dynamic)
548 def optimize(
549     backend="inductor",
550     *,
(...)
555     dynamic=None,
556 ):
557     """
558     The main entrypoint of TorchDynamo.  Do graph capture and call
559     backend() to optimize extracted graphs.
(...)
581             ...
582     """
--> 583     check_if_dynamo_supported()
584     # Note: The hooks object could be global instead of passed around, however that would make
585     # for a confusing API usage and plumbing story wherein we nest multiple .optimize calls.
586     # There is some prior art around this, w/r/t nesting backend calls are enforced to be the same
587     # compiler, however, this feels onerous for callback and hooks, and it feels better to give our users an
588     # easier to understand UX at the cost of a little more plumbing on our end.
589     hooks = Hooks(guard_export_fn=guard_export_fn, guard_fail_fn=guard_fail_fn)
File ~\anaconda3\envs\casada\lib\site-packages\torch_dynamo\eval_frame.py:535, in check_if_dynamo_supported()
533 def check_if_dynamo_supported():
534     if sys.platform == "win32":
--> 535         raise RuntimeError("Windows not yet supported for torch.compile")
536     if sys.version_info >= (3, 12):
537         raise RuntimeError("Python 3.12+ not yet supported for torch.compile")
RuntimeError: Windows not yet supported for torch.compile

You can comment out the compile section.  It runs fine without it on Windows.


Whitelist $EZSQL_ERROR in variable naming conventions sniff

Though obscure, this global variable is used by WordPress core in wpdb, as a remnant of when it was forked from EzSQL. See https://core.trac.wordpress.org/browser/branches/4.6/src/wp-includes/wp-db.php#L1350.
See #691 for previous discussion.

Tests are failing on PHPCS master and on PHP 5.2.
In master it looks like the phpcbf output format has changed, and for PHP 5.2 it looks like its choking on a namespace separator.

@westonruter See https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/696 as to why this is failing on master. develop is currently failing on master as well.

@JDGrimes Could you rebase (& squash) so that we can get the travis checks to pass ? I can't merge until they do :disappointed:


fix: a crash that can happen when deleting mods

This should fix a crash that could happen when deleting mods, which seems to have been introduced with the disabled button change in 65c0c4241a4906884b1fb1265b7bebf0d96da6a8.
I did not fully explore the cause, but it seemed like the crash would occur when you had at least 1 mod enabled and deleted another mod. I believe this was because we begin a disabled section (BeginDisabled), but we do not properly close out that section when a mod is deleted.

Ah thank you, i missed that when changing it over!

Have you considered joining the contributors discord, id love to discuss ideas for how to improve Lampray

I had not really considered joining since I do not really use Discord and was planning to only make a few changes. I can drop in and try to remember to check in every now and then.


Cleanup node bindings

The node bindings (https://github.com/ethereum/c-kzg-4844/tree/main/bindings/node.js) seem to contain quite a few files and it makes it hard to review the actual code. Can we tidy them up somehow?
/cc @dgcoffman

Each of those files serves a purpose. What tidying do you imagine? Happy to review a PR.

Will be handled as part of https://github.com/ethereum/c-kzg-4844/issues/153


Some issues with Scorecard plot type

Should be:

But now:

Formatting for col data and plot problems

check show as example

format we ith %  - means multiply by 100 and put  % in the beginning of the number
%## means:
0.1 -> %10

Example

Solved in 3.1.71


Migrate Music and game commands to application commands(slash commands)

Feature request: This would be a major improvement and get rid of the need for using quotes when passing multiple parameters for commands like !genplay, we can ask for parameters directly like /featurerequest and /reportbug.
Submitted by: mfcash
Server: mfDiscord

Should be incorporated in Dollar 2.0 when we break apart music.py(I imagine this would be done at the same time)


Still having Image/camera scaling placement issues

I re-checked my corners and my Preferences
I am set for 300x200  and my corners at 0,0, 0,100, 100,0, 100,100 are where they are supposed to be.  Dimensions up and down are spot on.
But when I PLACE SOMETHING, it is WAY off.
If I burn a 100x100mm box, it is as close to 100x100 as my calipers can measure, but it won't be where it is supposed to be.
I tried placing something as close to the origin as I could get it  (0,0) on screen.
It moved about 1.5" diagonally to place the image.
What can I print/burn to find out where I am off.
The camera, screen and reality don't agree currently, and it is making placing (and trusting the placement) tough.
Here is a video of what I tried
https://drive.google.com/file/d/1HgwgqNx9PtEiW75ExHPAmTMT71Asow70/view?usp=sharing
I created a 40x40 box in Inkscape.  I cleaned it and reduced the drawing to the selecxtion,
making it as clean and small as I could
Pulled it into MK40, aligned it with the box on my target
Told MK40 to go to the corner of the box, which MK40 said it was...
When I look at the laser, it is WAY off the mark.
This is what MK40 is showing me on the screen

This is where the laser actually -is-

PS... My HOME is now (supposedly) set to physical 0,0.

When I pulled it in the dimensions got garbled a bit, but the CORNER, is what I am looking at, it is still -WAY- off where MK says it is.

Camera needs to be mounted in a way that is useful, and also proven to be repeatable for the top-down bed view. I need to prop mine open to about 11", and use bubble levels to make sure the lid doesn't flex which would change the point of aim of the camera. These views are both from the same camera; one with the lid closed, and the other with the lid open for a top-down view.

The 6x9 checkerboard is used to Detect Distortions. This needs to be done for every corner at least once, and the center of the bed. Position, flatness, and lighting are critical for this to work. Do not stop trying if on corner doesn't work. Try a different position, adjust the lighting. Be aware not to move the camera.

Eight is a decent number of adjustment if they are well spread around the bed. Again; don't cut corners in this process.

Here is what the image looks like after the adjustment matrix is applied. Notice how all the corners are equally distorted to adjust for the camera lens. If one corner or edge is unlike the rest, it's not good enough.

The terminal window is opened and the command rect 0 0 100% 100% is typed. After typing the command; press return. This command is used to create a rectangle of the entire size of the bed. This will depend on the bed size being already set accurately in the Preferences beforehand to work.

The outline needs to be moved to a cut or engrave operation, and then run on some kind of substrate. I used card stock in this case. It's imperative not to touch or move the material after the outline is marked.

Perspective handles are moved to each corner of the marked box as accurately as possible. The dotted lines should explicitly align with the lines made from the outline routine.

After checking the Correct Perspective checkbox; it will skew, crop, and adjust aspect ratio (to fit the bed size set in Preferences). This is the usable area of the bed based on the bed size set in Preferences. Both Correct Fisheye, and Correct Perspective need to be checked in order to have a view that is useful to send to the background image of the scene.

This is the final background placed. Proven accurate to within a few millimeters. And that too can be tuned by inspecting for minor placement errors, and making fine adjustments to the perspective handles.
This is written as documentation for the camera setup process, which will be used for the wiki. Please advise if anything is unclear, it can be improved upon, or explained further.

Ok -THAT- got me within mm's.
What WASNT clear before was that you needed so many perspective corrections
-AND-
You needed to do Fisheye AND Perspective, even if the image looked OK.
My 6x9 grid is almost 180x280, so I didn't think I had to move it around to do the corners.
Again, Documentation and assuming that users know what the programmers had in mind.
WE CAN'T READ MINDS !!
Additional Notes to add to Set-up/Calibration Wiki
Materials NEEDED
10"x13" piece of heavy card stock paper or Carboard.
(It should be LARGER than 200mmx300mm by at least 25mm on all sides)
Sharpie pen
6x9 Grid printed (size recommendation)
Good description of how to burn corner marks
"Circle 100% 100% 1mm" isn't the complete command sequence. It just creates an operation object; it doesn't burn the circle or even move to that location... some other commands are needed.  Similarly, RECT 100% 100% just creates an Operations object. It doesn't burn the box.   Will need to tell people to adjust the power for the material they plan to Mark; at 100% power, it will make a mess of paper or cardboard, you need to either do a "Power 10%" (or whatever the command is) or tell people to turn down their front panel power.
Steps   (with your pictures)

Reset K40
Set HOME to 0,0
Reset Perspective & Fisheye and make sure boxes are clear
Use the 6x9 Grid in the Corners (2x GOOD images in each corner is recommended)
Turn on  "Correct Fisheye"
Turn on "Correct perspective."
Mark the corners by doing
Move 0% 0%
Test Button to mark
Move 0% 100%
Test Button to mark                                         (Or provide a COMPLETE script of how to burn the corners)
Move 100% 0%
Test Button  to mark
Move 100% 100%
Test Button to mark
HIGHLIGHT THE CORNERS WITH SHARPIE if you can't see the marks clearly on the Camera
Move the Perspective Corners to the Marked Corners

Note: You can "Full Screen" the Window and zoom to help get the placement exact.
This SEEMS to work.   Get a lot of "ill-conditioned Matrix, Keep trying" though, not sure what that actually means.

The wiki has already been updated with a number of possible way to do the setup (and probably more to be added). Not everyone will have a specific set of materials on hand, or even the same bed setup as a starting point. No assumptions can be made; and many specifics only apply to individual use cases, not a generic set of setup and use guidelines.
The instructions provided say: "The outline needs to be moved to a cut or engrave operation". There is a way to do that part from the terminal (more automatic), but that burden is placed on the user explicitly; and for good reason... An Operation choice, and settings for marking that rect would depend on the material used as you noted. Even valid Red or Blue operations, or user specific settings can not be assumed. Lack of automatic classification furthermore places the burden of running the laser on the user, instead of trying to fire the laser automatically without the user understanding what is going on. Even simply placing the rect into an existing operation might go unnoticed by the user; that could cause a head crash, or laser firing on the smoke vent if other setup constraints are also ignored. This was very much on purpose (despite having tested many other options which "seem" easier).
 Instructions can't require 0,0 home, not every machine can use that setup; most notably the stock smoke vent is in the laser path. Resetting Fisheye might not be an appropriate instruction; since some users might not need or wish to delete the matrix they already have (it would already be saved if it had been created by the user in the past). It is fine to overwrite that matrix with a new setup. The script for the complete burn "corners" was provided (rect 0 0 100% 100%). There are in fact more complex aliases that draw alignment marks only in each corner, and not the full rectangle specified in the instructions. But those aliases are even less easy to understand in terms of intent, since they contain a dozen or more commands. It's been tested; and an alias command can even do the HOME, as well as place the alignment marks in an Operation ready to run. That is simply not done for the reasons stated above (not safe, and the user needs to be involved as well as follow every one of the instructions). The sharpie wouldn't be needed if you used the rect 0 0 100% 100% command. The rect 0 0 100% 100% was chosen since the lines are visible with even low-res or blurry cameras (burning tiny dots with the laser test are not likely to be visible in the camera view, even when zoomed in).
Indeed; you can zoom in to get really in depth with the perspective corner markings, but for the screen shots that would have been difficult to show clearly. I also did it zoomed out to see how terrible it could be, and it worked just fine. In my experience, it's nice to do some fine tuning after further testing anyway. Doing a manual adjustment of those handles later to correct minor placement issues can allow for sub-millimeter accuracy. Quite frankly though; the stability of the camera mounting location (lid flex, repeatable opening position, etc.) is likely to have more effect on alignment than fine tuning the perspective handles.
The Distortion Detection routine is rather complicated. It's analyzing the camera image to find the 6x9 grid, and use it to warp the image in a favorable way. If that detection, or the math goes wrong; it won't intentionally record garbage data. Yes, it's difficult. You may need to nudge the checkerboard around or adjust the lighting. But there really isn't a way to do that setup manually. I found that rotating the checkerboard helped sometimes, but other times I just moved on, and came back to address a particular location later with success.

One other reason I avoided recommending the Test Fire at four corners, and a Sharpie marker to highlight them; is it adds an opportunity to bump things out of alignment before the perspective is set. It's an avoidable point of failure, and one that could cause frustration for an end user. That was also mentioned in the instructions explicitly: "It's imperative not to touch or move the material after the outline is marked.".

Ok, all makes sense, especially the vent being in the way of the laser on
the traverse that crosses it.
HOWEVER:   RECT 0 0 100% 100% doesn't burn the rectangle by its-self.
Neither does Circle 100% 100% 1mm
If I could have used those commands, I would have as I could do that with
the cover down and not touch anything for 8-10 commands.  There is some
OTHER command that is needed to execute the burn of the marks.
ASSUMING that the user -HAS- put down something appropriate to serve as a
target
what would be the sequence
Circle 0 100% 1mm
Circle 100% 100% 1mm
Circle 100% 0 1mm
Circle 0 0 1mm
Power 30%      < or something so that it just marks paper/cardboard and
doesn't blow through it and torch things
<what goes here to tell it to burn the circles the above instructions put
onto the operations list?>
If you aren't comfortable writing these, then -ALL- reference to this needs
to be removed so the non-hacker user doesn't start a fire or hurt
something.  The "Move x% y% and then test button"  then needs to be well
documented, very much like you did for me...  (probably safer. maybe an
"advanced" section with the command/script in THAT section)
I apologize for dragging you through this (again), but I am not a hacker
any more.  The K40 stuff is my 4th or 5th priority, and not anything
related to my day job, other than I would like to make some giveaways
someday and I enjoy tinkering.  My "Z" axis bed is just waiting on a GT2
belt and it will get installed... Probably will never use it much, but it
was fun to build and debug...
Bob Sisson
On Mon, Feb 15, 2021 at 2:35 PM Joseph Lane<EMAIL_ADDRESS>wrote:

One other reason I avoided recommending the Test Fire at four corners, and
a Sharpie marker to highlight them; is it adds an opportunity to bump
things out of alignment before the perspective is set. It's an avoidable
point of failure, and one that could cause frustration for an end user.
That was also mentioned in the instructions explicitly: "It's imperative
not to touch or move the material after the outline is marked.".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meerk40t/meerk40t/issues/359#issuecomment-779414508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJ2GYZUCIZXLGII4DK2Y3TS7FZRVANCNFSM4XTTWUCA
.

As for things not moving, I use strong MAGNETS to hold stuff down.  It will
hold to the frame, or if you have installed a honeycomb bed, they will
stick to that as well.
Bob
On Mon, Feb 15, 2021 at 2:35 PM Joseph Lane<EMAIL_ADDRESS>wrote:

One other reason I avoided recommending the Test Fire at four corners, and
a Sharpie marker to highlight them; is it adds an opportunity to bump
things out of alignment before the perspective is set. It's an avoidable
point of failure, and one that could cause frustration for an end user.
That was also mentioned in the instructions explicitly: "It's imperative
not to touch or move the material after the outline is marked.".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meerk40t/meerk40t/issues/359#issuecomment-779414508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJ2GYZUCIZXLGII4DK2Y3TS7FZRVANCNFSM4XTTWUCA
.

The circle command doesn't give an appropriate guide for the perspective handles; in fact, it is likely to be used very incorrectly, generating significant placement error. Those circles wouldn't be drawn outside of the cutting area, and thus the perspective handles would need to mark a point with no reference at all based on circular markings. The corners need to be marked with at least a line, or a rectangle. The fully bounded rectangle has significant advantages in this situation.
Yes; the object is still not put into an operation; on purpose. Doing so makes the terminal commands more complicated, but also makes the instructions considerably more confusing. The instructions simply can't explain every possible MeerK40t setup. It can't even assume basic things, like Red is always Cut; since the user can configure all those themselves (or not have done any configuration at all). Can't assume Blue/Engrave either; maybe the user has only don't cuttings jobs with Red/Cut. Instructing the user to move the recently created rect 0 0 100% 100% into a cut or engrave operation; is the instruction for that process; that absolutely requires the end user to make some specific and necessary decisions. The newly created rect needs to be dragged from elements, where it appeared; into an appropriate operation... The user performing that action should be using their own knowledge of their setup to make that happen.
You mention power needs to be dictated in the instructions again; which would be a HUGE problem for individual users. That "30%" setting on a k40 with digital controls could amount to more than 100% of the safe laser power on some machines. Similarly; lasers with analog power control also don't have a 30% setting, or any safe percentage, or knob position either. That's entirely machine specific (and something that every user should have learned about before turning the laser on). Even a current draw value, is not a sound metric to be included in the instructions.
There is no range of default settings that can be shared universally. Things like air assist (which aren't a default or stock install on a k40) dramatically change even the most basic guidelines for power and speed on a given material; not to even consider variables like orifice size of that air assist nozzle, distance from the work, the aim point of the nozzle, or the pressure.
It's obviously a work in progress. But I've spent considerable effort to be agnostic about documentation for the camera setup. Many things were learned in the process; even noting that "stock" dimensions of any specific k40 machine are not a given. Some machines even have a physically smaller bed than others. In other cases; a user has already made accommodations for the bed position (shift), and size. Those things need to be universally accepted and respected. Giving too many instructions can be just as dangerous as too few.
Rest assured, every suggestion, issue, and potential use case is considered carefully. Fully automatic operations have already been tested. Ultimately it came back to the same thing described earlier; that  instructions need to work for every user, and every use case. The goal of documentation for any process should also be; "First, do no harm". Especially so with lasers involved.

FIXED !


Make EXPORT operations jobs

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw1DKmbKhg2MIECH/reckJOuIfaskEA6r0
Description: The long-running parallel EXPORT statement functions as a job, so it shows up in the jobs view and can be paused, resumed, and canceled like other jobs.
Long-running EXPORT jobs do not provide any indication of their progress or status. They can produce files to a cloud storage location without the user being able to validate that the full set of data has been written.
Team:
Github Tracking Issue: https://github.com/cockroachdb/cockroach/issues/28213

This seems to have been de-prioritized for 20.1

Closing for now - will open a new issue whenever this is added to the roadmap.


CLI is unable to resolve the prisma schema if it is in the docs folder

@pantharshit00
A command like this does not work
npx prisma-docs-generator serve --schema=./src/db/prisma/schema.prisma.


request help: How to configure adding headers based on separated traffic?

Issue description
How to configure adding headers based on separated traffic?
How to implement the following configuration in apisix ingress?
split_clients "$remote_addr" $helloworld_backend {
    10%   helloworld_grey_server
    *     helloworld_official_server
}

upstream helloworld_official_server{
    server helloworld_official-svc.applet.svc.cluster.local:11001 max_fails=3 fail_timeout=10s weight=100;
    server helloworld_official-svc.applet:11001 max_fails=3 fail_timeout=10s weight=100;
}

upstream helloworld_grey_server{
    server helloworld-grey-svc.applet.svc.cluster.local:12001 max_fails=3 fail_timeout=10s weight=100;
    server helloworld-grey-svc.applet:12001 max_fails=3 fail_timeout=10s weight=100;
}

location /helloworld/v1/ {
    if ($helloworld_backend ~ "helloworld_grey_server") {
        proxy_set_header grey "yes";
    }

    proxy_pass  http://$helloworld_backend/;

}

Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.6.0
your Kubernetes cluster version (output of kubectl version): 1.22.0
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
name: httpbin-route
spec:
http:

name: rule4
match:
hosts:

nginx.testapisix.com
paths:
/*
backends:
serviceName: nginx-srv
servicePort: 80
weight: 10
proxy_set_header: (need to add a header here, how to achieve it?)
serviceName: nginx-srv1
servicePort: 80
weight: 90

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: httpbin-route
spec:
  http:
  - name: rule4
    match:
      hosts:
      - nginx2.qikqiak.com
      paths:
      - /*
    backends:
     - serviceName: nginx-srv
       servicePort: 80
       weight: 10
       proxy_set_header: (need to add a header here, how to achieve it?)
     - serviceName: nginx-srv1
       servicePort: 80
       weight: 90

I think you can use the traffic-split plugin. https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/plugins/traffic-split.md

Thank you for your reply
But I hope this header is added on the controller instead of being passed through the client
               weight:50                                 proxy_set_header(grayheader: grayvalue)
            ------------->  UpstreamA  --------------------------------------------

Client ---                                                                                -------->  Backend
weight:50
------------->  UpstreamB ---------------------------------------------

You mean this, right?
client -->  /api --> header(version:v1) --> service1
                         --> header(version:v2) --> service2

If that's the case.
Currently, setting request headers for specific services on routing is not supported

你是说这个，对吧？
client ---->  /api  --- header(version:v1) ---> service1
                    --- header(version:v2) ---> service2

如果是这样的话。 目前不支持在路由上为特定服务设置请求头

OK    thanks for your reply


⚠ ODIGDesigns has degraded performance

In 1e0d1a2, ODIGDesigns (https://www.odigdesigns.com.au) experienced degraded performance:

HTTP code: 200
Response time: 6701 ms

Resolved: ODIGDesigns performance has improved in 2267d34.


INFO: Disabling dom.workers breaks Dashlane password manager

I hope this helps other folks.

FF 59.0.2(64-bit) Windows 10
Dashlane 5.9.3

Thanks. dom.workers.enabled is deprecated/removed in FF60 - see 1434934


--location required in az deployment group create command

When I try to execute the command in the "Deploy template" section, I get an error that says that "az deployment create: error: the following arguments are required: --location/-l"

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

ID: 7bf283cd-65c2-09ad-0af2-37bf95fe4d90
Version Independent ID: 46451ccf-174a-e4da-433f-aa8c5570557d
Content: Tutorial - Create & deploy template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Nevermind, my bad I had switched group create with create group

@simonech Glad to know that you have self resolved and closed the issue. Thanks for the update.


SqlRs: SQL Server 2016 SSRS init fails on AWS

Details of the scenario you tried and the problem that is occurring
We have a configuration that we run against a provisioned AWS VM Windows Server 2016 + SQL Server 2016 SP1 Standard. (We use the latest AMI that matches the name pattern Windows_Server-2016-English-Full-SQL_2016_SP1_Standard*)
Our set of partial configurations is not trivial - we have a workflow that compiles and pushes these configurations to the target server. One of the first things it does is set the machine name, which causes a reboot. Our workflow then waits for the machine to boot back up and then waits for the configuration run to finish.
Recently, we noticed that after a while the workflow starts reporting that DSC has encountered an error, but there's nothing in the Event Log. However, there is an entry in the log file:
Verbose logs showing the problem
  {"time": "2018-12-14T15:26:07.040+00:00", "type": "verbose", "message": "[HOSTING-TEST]: LCM:  [ Start  Resource ]  [[SqlRS]SSRSConfig]  "},
  {"time": "2018-12-14T15:26:07.040+00:00", "type": "verbose", "message": "[HOSTING-TEST]: LCM:  [ Start  Test     ]  [[SqlRS]SSRSConfig]  "},
  {"time": "2018-12-14T15:26:07.103+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\Microsoft\\SQLServer\\ReportServer\\RS_MSSQLSERVER\\v13\\Admin,'className' = MSReportServer_ConfigurationSetting'."},
  {"time": "2018-12-14T15:26:07.930+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Enumerate CimInstances' complete."},
  {"time": "2018-12-14T15:26:07.952+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-07: Reporting services localhost\\MSSQLSERVER are not initialized."},
  {"time": "2018-12-14T15:26:07.957+00:00", "type": "verbose", "message": "[HOSTING-TEST]: LCM:  [ End    Test     ]  [[SqlRS]SSRSConfig]  in 0.9170 seconds."},
  {"time": "2018-12-14T15:26:07.958+00:00", "type": "verbose", "message": "[HOSTING-TEST]: LCM:  [ Start  Set      ]  [[SqlRS]SSRSConfig]  "},
  {"time": "2018-12-14T15:26:08.007+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\Microsoft\\SQLServer\\ReportServer\\RS_MSSQLSERVER\\v13\\Admin,'className' = MSReportServer_ConfigurationSetting'."},
  {"time": "2018-12-14T15:26:08.031+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Enumerate CimInstances' complete."},
  {"time": "2018-12-14T15:26:08.034+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root/cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2018-12-14T15:26:08.060+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Enumerate CimInstances' complete."},
  {"time": "2018-12-14T15:26:08.064+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-08: Initializing Reporting Services on localhost\\MSSQLSERVER."},
  {"time": "2018-12-14T15:26:08.068+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-08: Setting report server virtual directory on localhost\\MSSQLSERVER to ReportServer."},
  {"time": "2018-12-14T15:26:08.090+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = SetVirtualDirectory,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:26:12.634+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:26:12.647+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-12: Adding report server URL reservation on localhost\\MSSQLSERVER: http://+:8888."},
  {"time": "2018-12-14T15:26:12.648+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = ReserveUrl,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:26:17.700+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:26:17.701+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-17: Adding report server URL reservation on localhost\\MSSQLSERVER: https://hosting-test.elements.symplectic.org:443."},
  {"time": "2018-12-14T15:26:17.702+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = ReserveUrl,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:26:23.254+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:26:23.256+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-26-23: Setting reports virtual directory on localhost\\MSSQLSERVER to ReportServer."},
  {"time": "2018-12-14T15:26:23.259+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = SetVirtualDirectory,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:03.371+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:03.381+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-27-03: Adding reports URL reservation on localhost\\MSSQLSERVER: http://+:8888."},
  {"time": "2018-12-14T15:27:03.395+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = ReserveUrl,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:08.437+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:08.438+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] 2018-12-14_15-27-08: Adding reports URL reservation on localhost\\MSSQLSERVER: https://hosting-test.elements.symplectic.org:443."},
  {"time": "2018-12-14T15:27:08.440+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = ReserveUrl,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:13.992+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:13.994+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = GenerateDatabaseCreationScript,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:14.910+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:15.024+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_Service'."},
  {"time": "2018-12-14T15:27:15.269+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Enumerate CimInstances' complete."},
  {"time": "2018-12-14T15:27:15.270+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = GenerateDatabaseRightsScript,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:15.289+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:15.371+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Preferred module SqlServer found."},
  {"time": "2018-12-14T15:27:15.375+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Importing PowerShell module 'SqlServer' with version '21.0.17240' from path 'C:\\Program Files\\WindowsPowerShell\\Modules\\SqlServer\\21.0.17240\\SqlServer.psm1'."},
  {"time": "2018-12-14T15:27:16.429+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:16.479+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'msdb'."},
  {"time": "2018-12-14T15:27:16.523+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'master'."},
  {"time": "2018-12-14T15:27:16.554+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:16.581+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:16.687+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:18.524+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'master'."},
  {"time": "2018-12-14T15:27:18.535+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'msdb'."},
  {"time": "2018-12-14T15:27:18.729+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:18.765+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:18.765+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:18.842+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:19.112+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Caution: Changing any part of an object name could break scripts and stored procedures."},
  {"time": "2018-12-14T15:27:19.207+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:19.306+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:19.309+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:19.390+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:19.645+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Caution: Changing any part of an object name could break scripts and stored procedures."},
  {"time": "2018-12-14T15:27:19.688+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:19.775+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:19.875+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:21.241+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] The module 'CreateRdlChunk' depends on the missing object 'CreateSegmentedChunk'. The module will still be created; however, it cannot run successfully until the object exists."},
  {"time": "2018-12-14T15:27:21.241+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] The module 'CreateRdlChunk' depends on the missing object 'CreateChunkSegment'. The module will still be created; however, it cannot run successfully until the object exists."},
  {"time": "2018-12-14T15:27:21.627+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:21.636+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:21.657+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'master'."},
  {"time": "2018-12-14T15:27:21.701+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:21.732+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServerTempDB'."},
  {"time": "2018-12-14T15:27:21.757+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'msdb'."},
  {"time": "2018-12-14T15:27:21.782+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'master'."},
  {"time": "2018-12-14T15:27:21.814+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Changed database context to 'ReportServer'."},
  {"time": "2018-12-14T15:27:21.816+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = SetDatabaseConnection,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:28.863+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:28.866+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Perform operation 'Invoke CimMethod' with following parameters, ''instance' = MSReportServer_ConfigurationSetting (InstanceName = \"MSSQLSERVER\"),'methodName' = InitializeReportServer,'namespaceName' = root/Microsoft/SQLServer/ReportServer/RS_MSSQLSERVER/v13/Admin'."},
  {"time": "2018-12-14T15:27:29.008+00:00", "type": "verbose", "message": "[HOSTING-TEST]:                            [[SqlRS]SSRSConfig] Operation 'Invoke CimMethod' complete."},
  {"time": "2018-12-14T15:27:29.055+00:00", "type": "verbose", "message": "[HOSTING-TEST]: LCM:  [ End    Set      ]  [[SqlRS]SSRSConfig]  in 81.0980 seconds."},
  {"time": "2018-12-14T15:27:29.055+00:00", "type": "error", "message": "PowerShell DSC resource MSFT_SqlRS  failed to execute Set-TargetResource functionality with error message: Method InitializeReportServer() failed with an error. Error: The feature: \"Scale-out deployment\" is not supported in this edition of Reporting Services. (rsOperationNotSupported) (HRESULT:-2146233088) "},

It looks like the initialisation only partially fails - after this has run, Reporting Services Configuration Manager looks fine, but logging into the web GUI gets you a 503, until we manually restart the SSRS service.
After the restart, SSRS seems to be working fine, our custom roles/policies resources to their job, we can deploy reports, etc.
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
I'll see if I can produce a minimal configuration to replicate this problem.
SQL Server edition and version the target node is running
Microsoft SQL Server 2016 (SP1-CU8) (KB4077064) - 13.0.4474.0 (X64)   Feb 24 2018 13:53:17   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

I'll see if I can find a Win2016+SQL2016 AMI that doesn't exhibit this problem.
SQL Server PowerShell modules present on the target node
Name         Version    Path
----         -------    ----
SqlServer    21.0.17240 C:\Program Files\WindowsPowerShell\Modules\SqlServer\21.0.17240\SqlServer.psd1
SqlServer    20.0       C:\Program Files\WindowsPowerShell\Modules\SqlServer\SqlServer.psd1
SQLASCMDLETS 2.0        C:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLASCMDLETS\SQLASC...
SQLPS        1.0        C:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS\SQLPS.psd1

The operating system the target node is running
OsName               : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 14393.2608.amd64fre.rs1_release.181024-1742
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

Version and build of PowerShell the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.14393.2608
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.2608
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Version of the DSC module that was used ('dev' if using current dev branch)
Name         Version  Path
----         -------  ----
SqlServerDsc <IP_ADDRESS> C:\Program Files\WindowsPowerShell\Modules\SqlServerDsc\<IP_ADDRESS>\SqlServerDsc.psd1

I've now tested with two different AWS AMIs, with our production configuration, which uses xSqlServer <IP_ADDRESS>, and our "test" configuration, where the only difference is an upgrade to SqlServerDsc module v<IP_ADDRESS> (with appropriately renamed resources and parameters).
The production configuration succeeds on both AMIs and the test configuration fails on both with the above error.
Is the CIM class used in SqlServerDsc trying to configure this "Scale Out Deployment" with InitializeReportServer() method?

I wonder if it fails on this - it would suggest that.
https://github.com/PowerShell/SqlServerDsc/blob/457082c151ee5d2fe992a9dc0a2ed4389594fe37/DSCResources/MSFT_SqlRS/MSFT_SqlRS.psm1#L428-L436
So it can never get to the point that it restarts the service
https://github.com/PowerShell/SqlServerDsc/blob/457082c151ee5d2fe992a9dc0a2ed4389594fe37/DSCResources/MSFT_SqlRS/MSFT_SqlRS.psm1#L453
We should really add more verbose messages in this resource so it's easier to track how far it gets.
Anyway, I don't think scale out deployment is a supported scenario as of yet, so not sure why it tires to configure it that way.
Can you please provide the parts of configuration script that configures the Reporting Services? So it's is possible to reproduce this.

Hi,
I've managed to replicate the problem with absolutely minimal configuration. I tested with the following AWS AMI (eu-west-01 region, the ID will be different in different regions):
Windows_Server-2016-English-Full-SQL_2016_SP1_Standard-2018.12.12 (ami-0cdf848d0b03c0b61)

On a clean install, first install SqlServerDsc:
Install-Module -Name SqlServerDsc -RequiredVersion <IP_ADDRESS> -SkipPublisherCheck -Force

Then, save this to a .ps1 script and run it from PowerShell prompt:
configuration ConfigureSsrs {

    Import-DscResource -ModuleName SqlServerDsc

    $reservedUrls = @("http://+:8888")

    Node "localhost"{
        SqlRS SSRSConfig {
            InstanceName = "MSSQLSERVER"
            DatabaseServerName = "localhost"
            DatabaseInstanceName = "MSSQLSERVER"
            ReportServerReservedUrl = $reservedUrls
            ReportsReservedUrl = $reservedUrls
        }
    }
}

ConfigureSsrs

Start-DscConfiguration -Path .\ConfigureSsrs -Wait -Force -Verbose

You'll get the same error:
PowerShell DSC resource MSFT_SqlRS  failed to execute Set-TargetResource functionality with error message: Method
InitializeReportServer() failed with an error. Error: The feature: "Scale-out deployment" is not supported in this
edition of Reporting Services. (rsOperationNotSupported) (HRESULT:-2146233088)
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

@bozho Wonder if they way it configures it is they way to configure a scale out deployment, and since the Standard version does not support it (see Scale out deployment (Web farms) under Reporting Services Features Supported by the Editions of SQL Server , then it fails. This probably works if you use Enterprise edition of SQL 2016.
So the problem is that this should be able to correctly initialize SSRS 2016 Standard as well.

The strange thing is that if I use the xSqlServer module and its xSQLServerRSConfig resource to configure SSRS 2016 on the same AMI, it succeeds. As far as I can tell, xSQLServerRSConfig also calls InitializeReportServer, only through WMI not CMI.
And why would InitializeReportServer even try to configure scale-out deployment?
Are there two different versions of InitializeReportServer being executed?

Ok, found out why the xSqlServer is working - WMI method calls are not checking return values. The The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported) error still happens, but it's ignored.
The code in SqlServerDsc checks return values on CIM method calls, and fails.
You write better code and you're worse off... :-)

@johlju I can confirm this is still happening. Would it make sense to treat this as a warning? I see no way to control the "scale-out deployment" option on SSRS...

But if you get this error, aren’t the wrong edition used if you get this error? :thinking: Or is this just a warning reported back from the CIM call, but we treat it as an error? If so we can just output a warning for this, but an error in all other cases.
The integration test for SqlRS does not report this error, at least the tests doesn’t fail. Is it because we use the Evaluation (equals the Enterprise) version for the tests?

But if you get this error, aren’t the wrong edition used if you get this error?

No idea, we use SQL Standard on AWS (this is SQL 2016), so SSRS is bundled with it. AWS image contains a default install of SQL Server, with SSRS just installed, not configured/initialised (there's an option in SQL Setup for that).
SqlRS sets up the virtual directories, reserves URLs, and simply calls the Initialise method. Older versions of the resource would simply ignore any errors - I would bet SSRS Configuration GUI also ignores this error, since I've found no mention of that option/setting.

I’m good with outputting a warning for now, when this error is reported, until we know if this is a bug in the CIM method, or any other reason it is reporting this error. :)

Ok, I'll work on the patch

@johlju Heh, I had a hunch and did a bit more testing by executing Set-TargetResource manually line by line...
It seems that executing CIM method SetDatabaseConnection initialises SSRS. Calling Get-ReportingServicesData -InstanceName $InstanceName right after executing SetDatabaseConnection, but before executing InitializeReportServer returns SSRS configuration where IsInitialized it True.
I suppose by executing InitializeReportServer when IsInitialized, SSRS thinks we're doing the scale-out deployment and returns an error on SQL Standard. Older versions of the module were ignoring return values from CIM methods and we never caught the error.
So, the suggested patch here would be not to execute InitializeReportServer CIM method when initialising SSRS.

Awesome detective work on this one too! :smiley:


Value too long for type character varying error on Update preview

Describe the bug
Getting an error when trying to preview/create a new Update:

Update failed: value too long for type character varying(255)

To Reproduce
Not exactly sure, to be honest.
Started out trying to bring this document over from HackMD and initially it worked fine (one needs to copy-paste the formatted version into the WYSIWYG editor), but with a few edits to make it look better with Open Collective's formatting at some point it started throwing this error back on edits, and even when trying to create a new document.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: Arch Linuxe (Gnome on Wayland)
Browser Firefox
Version 85

Additional context
Add any other context about the problem here.

@flaki I wasn't able to reproduce, I tried copy pasting the content from HackMD + doing some edits but can't get the bug yet. Tested on https://staging.opencollective.com/captainfact_io/updates/welcoming-the-rustfest-project
Would you be able to copy paste the exact content that's triggering the error? Best would be to get it from the .ql-editor:

We'll have to close if we can't reproduce I'm afraid.

255 can't be about the content itself, it's either slug, title, image, tags, summary or notificationAudience.

If I try to submit a long title, I get:

Tell me that it's not title, it has its own validation. I discard image, tags or notificationAudience because they're not in the form. We have summary left ...

It's autogenerated by generateSummaryForHTML. I suspect an issue with utf8 handling in generateSummaryForHTML.
Reproducing here: https://github.com/opencollective/opencollective-api/pull/5041

Note that 1. the hackmd's current latest content is different from what produced the bug and 2. it's definitely an iterative bug, it needed multiple modifications to surface, so I'm guessing it might be some junk getting into the text area due to transforms. I can do some testing over the weekend to see if I can get this to reproduce on staging!

Oh yes that VARCHAR(255) surprised me too, but if it's auto-generated on submission that would make sense. I really wish I saved the request/response when I submitted this to help reproduce 🤔

It's just a blind guess, but we could try https://github.com/parshap/truncate-utf8-bytes

Also there's not much UTF-8 in that post for the first half at least that is relevant here (maybe the quotes?).
I've been trying to reproduce for the past 10 minutes but without much luck.
I guess if we can't find the root cause you could just treat the symptoms (and ensure that summary contents are the correct byte length or set up some logging to see if this reproduces in the wild).

I'm discarding utf-8 now and looking at improper truncating of html tags.

Tentatively fixed in https://github.com/opencollective/opencollective-api/pull/5041
Closing!


New feature request: fast thumbnails preloading for user selected folders

Description of the new feature / enhancement
User right clicks on the folder in the Explorer &  select option "preload thumbnails" from the context menu.
After that, a one time process start &  thumbnails are generated for each file in the folder, with 100% CPU/GPU power.
Scenario when this would be used?
Right now, wen user opens folder, full of images and videos,  thumbnails are generated in the background, only for files currently visible on the screen. For folders with thousands of files, it takes a lot of time to find the right file -  when there are no thumbnails yet. Especially for images formats like .HEIC  (gaining popularity) it takes forever to generate thumbnails, as extension for this file type it's extremely slow.
Pre-generating thumbnails with a full CPU/GPU power, would help a lot for professionals working with large multimedia folders.
Supporting information
There is a tool on the web, with similar functionality (MIT License), but it appears the project is no longer in the active development.
https://github.com/bruhov/WinThumbsPreloader
there are forks, that adds multi threading for faster .heic generation but these are buggy.

That would be great !

Pretty much needed! This should be done by windows in background for new files when pc is in IDLE, quite annoying having to wait for thumbnail generation for videos and images

Seems like there is a more maintained fork under the same license, would still be neat to see this integrated into PowerToys though: https://github.com/Mfarooq360/WinThumbsPreloader

I'm not really sure if those generated thumbnails are working with latest windows 11 explorer gallery and photos app.

Pretty much needed! This would be amazing to be done by windows in background for new files when pc is in IDLE, quite annoying having to wait for thumbnail generation for videos and images

The problem with that though is that on most people's computers there are tens of thousands (if not hundreds of thousands) of images and short movies in the system folders of all of your apps and games and the operating system itself and if Windows were to create thumbnails of all of them it would take up a very large chunk of disk space.  Windows has no way of knowing which folders you want to have thumbnails for and which folders you don't.
Though they really should do what you suggested with the obvious folders like Documents/Pictures and Documents/Videos

throwing this out there : i have a 24 core cpu and an nvidia rtx 4090 that can run crysis, but for some reason i need to wait around for a cache update to show a simple image thumbnail, just curious what's the deal here,
how does the thumbnail process in windows 11 actually work? it seems like something which is a straightforward linear algebra transform and not anything which requires delay or caching. are we FIFO or LIFO? I certainly tend to look at most recent screenshots first!
i thought "cache invalidation" was one of the hardest parts of computer science, and the "bitter lesson" is just to throw more compute at our problems, so could anyone enlighten me as to how we can gpu accelerate file explorer so this never happens ? it's an honest dealbreaker, i don't care about copilots, i just want the basic stuff to actually work

Windows should have a native and shared api for generating and showing images and thumbnails as mobile os do. Windows 11 23H2 gallery is completely broken even today. Just try to scroll fast through a big image gallery, the explorer.exe process just grows leaking memory everywhere until it explodes and hangs.

I have over 15K photos in my Pictures folder and this app did a great job preloading thumbs. However, I have realized that after preloading, folder views are reset and now all I'm looking to yellow folders with tiny "JPG"1 icon in the center. No folder previews .. so how to fix it?

Bump in hopes of raising awareness as this is a very big pain-point for me and clearly a lot of other people. [WinThumbsPreloader](https://github.com/Mfarooq360/WinThumbsPreloader works most of the time but still has some issues and inconsistencies like the guy above mentioned. Having this built into PowerToys with better integration would be wonderful!

This should be natively implemented in windows across all applications, with thumbnails pregeneration and global cache like mobile phones do. And please, fix the new windows explorer gallery, leaks memory until explodes still today!

Windows should also handle network mounts without locking up the entire explorer when unavailable but let's be realistic here- all of these are not new issues. MS never cared enough to even acknowledge any of them, never mind fix. PowerToys is the best and only thing we got in addressing windows shortcomings, with a team of devs and contributors who actually care about a better user experience.

Would be a massive help for data science. I'm sifting through a small scale dataset with 30k images making tweaks and trying to notice small patterns that need to be removed. When scrolling in full screen mode there's lots of flickering as the files load off from an ssd


less unpacked proof characterizing P -> Q when P closed, Q open

I don't know which style you prefer.
It's also only necessary that $\lnot P$ is open, not that $P$ is closed, but I don't know whether this is useful.

I prefer this proof and I think it makes sense to state it in the extra generality, that it is enough if $\neg P$ is open. One example of such a proposition $P$, which is not closed, would be $P(x):\equiv \neg\neg(x=0)$ for $x\in R$.


Broken link leads to 404 error

Broken link "Update rollup for Configuration Manager current branch, version 1902." leads to 404 error

Hi @colliefury, in which article do you see this link?

Hi Aaron,
aka.ms/dadocs -> Tutorials-> Pilot Windows 10 -> under topic "Connect Configuration Manager"
I am v-dadut btw
Thanks,
Damian
Get Outlook for Androidhttps://aka.ms/ghei36

From: Aaron Czechowski<EMAIL_ADDRESS>Sent: Thursday, June 13, 2019 12:12:34 PM
To: MicrosoftDocs/SCCMdocs
Cc: colliefury; Mention
Subject: Re: [MicrosoftDocs/SCCMdocs] Broken link leads to 404 error (#1644)
Hi @colliefuryhttps://github.com/colliefury, in which article do you see this link?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/SCCMdocs/issues/1644?email_source=notifications&email_token=ALCYRNGSDLKLIYIV25YAWSTP2KL2FA5CNFSM4HX5DYVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXUX47A#issuecomment-501841532, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALCYRND6TMKCSYFSXKX5QA3P2KL2FANCNFSM4HX5DYVA.

Got it. Yep, by design. That article isn't published yet. More coming soon.


Bottom navigation bar gets pushed above keyboard

When clicking on to a text input field, the bottom navigation bar, which was supposed to be covered underneath the keyboard would get pushed above instead. This happens throughout the app, including Search and Topic Services. The issue was tested for both iOS (iPhones) and Android (Samsung 8) and was only found on Android.
Below is the video demonstration for staging version 1.29.1 on Android:

Acceptance Criteria

[ ]  When a text input field is clicked/focused, the bottom nav is covered underneath the keyboard.

Steps for QA:

Go to Search.
Click on any text input field.

Staging 1.32.0 - passes


add USER_LIBS to common.mk

This is to solve issue #376; libraries can now be added to a project with the addition of USER_LIBS=... to the Makefile without removing those from parameters.mk.

Wouldn't the following do the same (libm is used as example)?
PROGRAM=test

include ../../common.mk

LIBS+=m

Yes, the end effect is the same. To me, at least, having a USER_LIBS variable makes the solution clearer when trying to add a library.

I believe that EXTRA_LIBS will be better name.


Update svd tests for svd_flip in dask

Hey @TomAugspurger, I'm trying to figure out the best way to integrate https://github.com/dask/dask/pull/6613.
The svd, pca, and incremental pca tests are all broken for any dask >= 2.26.0 install because the svd_flip in dask is now different from scikit-learn.
Ideally I could tweak the tests a little to deal with different signs in results but I didn't realize how often they are behind a few levels of abstraction, e.g. assert_estimator_equal: https://github.com/dask/dask-ml/blob/b94c587abae3f5667eff131b0616ad8f91966e7f/tests/test_pca.py#L25-L30
My first thought to fix this was to do something like this instead:
def test_basic():
     # This would also need to exist in TruncatedSVD and IncrementalPCA
     a = dd.PCA(sklearn_compatible=True)  # This will preserve the original behavior, but default to False?
     b = sd.PCA()
     a.fit(dX)
     b.fit(X)
     assert_estimator_equal(a, b)

I dislike muddling the signatures with that parameter, but I can't think of a much better solution.  Another possibility would be to modify all the tests such that any checks that compare SVD results (or something derived from them) to scikit-learn are sign-independent.  That would make the tests a bit uglier/more complicated but is probably ideal.
Has this come up before where you have some functionality that diverges from scikit-learn for performance reasons but still want to preserve compatible behavior in unit tests?

FYI https://github.com/dask/dask-ml/pull/737 is a fix for TruncatedSVD that takes this approach from above:

Another possibility would be to modify all the tests such that any checks that compare SVD results (or something derived from them) to scikit-learn are sign-independent

I'll keep looking at how to do the same in PCA/IncrementalPCA tests.

Closing since the changes in https://github.com/dask/dask/pull/6658 ensure sign stability after small changes to the input data, and the incremental PCA tests now work without changes.


etcdctl: add a new option --open-ended for unlimited range permission

This commit adds a new option --open-ended to the command etcdctl role
grant-permission. If the option is passed, an open ended permission
will be granted to a role e.g. from start-key to any keys those are
larger than start-key.
Example:
$ ETCDCTL_API=3 bin/etcdctl --user root:p role grant r1 readwrite a b
$ ETCDCTL_API=3 bin/etcdctl --user root:p role grant --open-ended r1 readwrite c
$ ETCDCTL_API=3 bin/etcdctl --user root:p role get r1
Role r1
KV Read:
        [a, b) (prefix a)
        [c, <open ended>
KV Write:
        [a, b) (prefix a)
        [c, <open ended>

Note that a closed parenthesis doesn't follow the above
for indicating that the role has an open ended permission ("" is a valid range end).
Fixes https://github.com/coreos/etcd/issues/7468

@heyitsanthony updated based on your comments, especially for changing the option name (--open-ended -> --from-key) and following the wire RPC protocol (\xff -> \x00). Could you take a look?

lgtm. Thanks!

@heyitsanthony thanks, I'm merging it


control space insertion behavior in linenoise

currently, if size of completion candidates is 1, always insert space after inserting a candidate.
in some situation, space insertion is not needed (ex. variable, field, method name completion).
need to change DSState_complete api

basic support in commit fc7ebab7cad9cfe37b7001229fcb6b2b9ab8ce6e


No data for selected store in settings, when data exists

For some reason the plugin says there's no data for selected stores, even if some stores have the data on https://isthereanydeal.com website.
For example:
Playnite screen:

https://isthereanydeal.com/game/wartales/info/

The settings:

The selected stores:
Blizzard, Epic Game Store, Fanatical, GOG, GamersGate, GreenManGaming, Humble Store, Itch.io, Microsoft Store, Origin, Steam, Ubisoft Store
Notice both Steam and GamersGate are listed in https://isthereanydeal.com/game/wartales/info/ page.
I might work on a fix in the next few days.

And this is the actual api response:
https://api.isthereanydeal.com/v01/game/prices/?key=fa49308286edcaf76fea58926fd2ea2d216a17ff&plains=wartales&region=eu2&country=LT&shops=steam,gamersgate
{
  ".meta": {
    "currency": "EUR"
  },
  "data": {
    "wartales": {
      "list": [
        {
          "price_new": 27.99,
          "price_old": 34.99,
          "price_cut": 20,
          "url": "https://store.steampowered.com/app/1527950/",
          "shop": {
            "id": "steam",
            "name": "Steam"
          },
          "drm": [
            "steam"
          ]
        },
        {
          "price_new": 34.99,
          "price_old": 34.99,
          "price_cut": 0,
          "url": "https://www.gamersgate.com/product/wartales/?aff=0c8572c286145f07e7903dee1650f54778ae9149",
          "shop": {
            "id": "gamersgate",
            "name": "GamersGate"
          },
          "drm": [
            "steam"
          ]
        }
      ],
      "urls": {
        "game": "https://isthereanydeal.com/#/page:game/info?plain=wartales"
      }
    }
  }
}

So data is definitely there


Ask detail settings before export to ARIA2 RPC

How to Ask detail settings before export to ARIA2 RPC?

If you select the "ask details settings before download" option, it will only ask detail settings before auto-capture is triggered at present.

If you select the "ask details settings before download" option, it will only ask detail settings before auto-capture is triggered at present.

how to enable "ask details settings before download" to click the right button

how to enable "ask details settings before download" to click the right button

You can copy the link to ariaNG to new a task manually and then tune the option as you need.

You can copy the link to ariaNG to new a task manually and then tune the option as you need.

"ask details settings before download"

"ask details settings before download"


feat: Implement Device System Events

Also, refactored to use common Messaging Bootstrap Handler
closes #4099
Implements related ADR
Dependent on the following PRs:

https://github.com/edgexfoundry/go-mod-core-contracts/pull/752
https://github.com/edgexfoundry/go-mod-bootstrap/pull/360

Signed-off-by: Leonard Goodell<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[x] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[x] I have opened a PR for the related docs change (if not, why?)
link TBD

Testing Instructions
Run edgex stack with Device Virtual
Stop Core Metadata container
Build and run this branch locally (require branches from PR referenced above) with DEBUG enabled
Using curl or postman delete, add and remove Device Virtual devices (can't use EdgeX UI from docker since core-metadata is running locally)
Verify log show debug message that System Event was published
New Dependency Instructions (If applicable)

Codecov Report

Merging #4101 (c91a622) into main (062af8d) will decrease coverage by 3.69%.
The diff coverage is 75.86%.

@@            Coverage Diff             @@
##             main    #4101      +/-   ##
==========================================
- Coverage   47.32%   43.63%   -3.70%
==========================================
  Files         114      120       +6
  Lines        9850    10591     +741
==========================================
- Hits         4662     4621      -41
- Misses       4801     5586     +785
+ Partials      387      384       -3

Impacted Files
Coverage Δ

internal/core/metadata/application/device.go
13.09% <75.86%> (ø)

...nternal/core/metadata/application/deviceprofile.go
0.00% <0.00%> (ø)

...rnal/core/metadata/application/provisionwatcher.go
0.00% <0.00%> (ø)

...nternal/core/metadata/application/devicecommand.go
0.00% <0.00%> (ø)

...ternal/core/metadata/application/deviceresource.go
0.00% <0.00%> (ø)

...nternal/core/metadata/application/deviceservice.go
0.00% <0.00%> (ø)

internal/core/metadata/application/notify.go
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 062af8d...c91a622. Read the comment docs.

@farshidtz , @jim-wang-intel create this PR to test which go-mod and which version has triggered this. We have narrowed it down to go-mod-bootstrap v2.2.1-dev.9
https://github.com/edgexfoundry/edgex-go/pull/4105
I am taking a look at the commit for that to see how it could be impacting this.

@farshidtz , that change to go-mod-bootstrap was to make sure the exit code it set properly when bootstrapping fails. Before it always returned with 0 exit code.
I suspect that the issue with Secret Store setup in the test was always there, be now has the proper exit code.

@farshidtz , found the culprit !
The file token provider is incorrectly returning false in its bootstrap hander which now causes it to exit with non-zero exit code.
We'll get a fix in for that which will un-block this PR.

@jim-wang-intel , @farshidtz , Rebased this PR to pull in fixes from the other PR.

Put in draft to it doesn't get merged until this PR is merged otherwise TAF tests will fail.
https://github.com/edgexfoundry/edgex-compose/pull/261#pullrequestreview-1055010670


Remove sign in pages from robots.txt so the crawler can remove them from the index

User story
As PM I want sign in pages to be removed from robots.txt, so the crawler can remove them from the index and they don't show up as false positives in Search Console
Acceptance criteria

[ ] users/signin doesn't show up in SC as "Indexed, though blocked by robots.txt"
[ ] users/github/login doesn't show up in SC as "Indexed, though blocked by robots.txt"

Tasks
If relevant, you can make a checklist for tasks.

[ ] This is an incomplete task.

Please re-file as kuma issue if still valid.


feature: extend CLI support for FastAPI server

Is your feature request related to a problem? Please describe.
We want to add extended CLI support for src/argilla/tasks/server because it is limited now.
Describe the solution you'd like
I would like to mimic https://www.uvicorn.org/deployment/
Describe alternatives you've considered
N.A.
Additional context
N.A.

Hi @davidberenstein1957 can I pick this up ?

@vasudevanubrolu to pick up this issue, you just need to for our repo, clone your fork and make changes to the 'argilla/tasks/server' file. Let me know if you need additional context.

@vasudevanubrolu can we re-align w.r.t. this issue too?

@davidberenstein1957 sure I want to complete it this week if its ok

Yes that would be great 💪🏽 Let me know if I can help with anything.

@vasudevanubrolu You should be able to copy a lot of code from the main and/or run method in the uvicorn codebase.
https://github.com/encode/uvicorn/blob/fc2130bf1a740acaa502530079bfbd595fa7a94c/uvicorn/main.py#L467C7-L467C7
Also, you will need to update.
https://github.com/argilla-io/argilla/blob/292d2e38b91c44c1e9a49c44fcaa76b60f63c478/src/argilla/tasks/server/__main__.py#L25-L30
And update the docs and reference the uvicorn options.

docs/_source/getting_started/installation/configurations/server_configuration.md

@gabrielmbmb shouldn't this be tracked as part of #3579?

src/argilla/cli/server/start.py

https://github.com/encode/uvicorn/blob/fc2130bf1a740acaa502530079bfbd595fa7a94c/uvicorn/main.py#L467-L518


The dynamic model sequence is shaking

Hello Yinghao,
Thank you for your wonderful job! But there is a problem I met. When I run the demo code on data attached on the respository, the SMPL model fits well on every frame.  However, when I render the SMPL models as a consecutive video, the model is shaking. How to deal with this problem? Thank you!

Sorry for the late response. Can you please be more specific about the issue? May I ask where do you think the shaking comes from? The 3D model part or the rendering part? Please note you might want to add translation into the rendering pipeline.


Close aiohttp responses

Description:
In response to the Not enough system resources issue reported with 0.33.3 I went through and looked at places were we might leak some sockets. Focused on aiohttp and came up with these places.
Related issue (if applicable): Not enough system resources
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Instead of finally, we can use the response object as a context manager so that the response will be automatically closed when the code is done with the request.