More implicit bounds (?Sized, ?DynSized, ?Move)

The concept of implicit bound was introduced together with dynamic sized type. While having a : Sized bound is more specialized than no bound at all, we expect that : Sized is much more common, and thus should be present by default. We introduced the : ?Sized syntax in #490 to opt-out of this default bound. The syntax : ?Sized is called "relaxed bound".
Later, new RFCs and PRs tried to introduce more traits like Sized which the common case is "this should be implemented", e.g.

#1858 and rust-lang/rust#44917 introduced the ?Move bound, since most types do not contain internal references and thus can be freely moved around.
#1993 and rust-lang/rust#46108 introduced the ?DynSized bound, since most types have known size and alignment at runtime.
https://gankro.github.io/blah/linear-rust (semiseriously) introduced the ?Leave bound, since most types can be drop'ed.

These traits themselves are often necessary at language level beyond trait bounds, e.g. Move is needed for immovable generators (for lack of a better solution), DynSized is needed to reject struct tails without known alignment, and Leave is needed to support linear type.
However, the expansion of implicit bounds experienced push back from lang team due to ergonomic cost, that

?Sized itself being a "negative feature" confuses users, adding ?Move and ?DynSized will only make the situation worse,

introducing new relaxed bound means downstream packages will need to reevaluate every API to see if adding : ?Trait makes sense, and this needs to be done for every new relaxed bound.

the necessity of  Move and DynSized is orthogonal to whether they need to be default.

the backward-compatibility may be a lie 🍰 — Relaxing the bounds in associated type, in particular FnOnce::Output, means the user of the trait will get less promises, which is a breaking change:
let should_be_movable: Closure::Output = closure();
let but_it_errored = should_be_movable;

Essentially, the bounds on an associated type cannot be added (which breaks implementers) or removed (which breaks users).

So the questions are,

Should we embrace ?Trait and allow language to grow more similar traits, despite the stated problems above?
If we decide to stop at ?Sized, what else should we do regarding Move and DynSized?
Would there be a balanced solution in the middle of the two extremes?

I am filing this issue here to Move the discussion from those two different PRs to a potentially more proper place, as it seems having a non-Sized relaxed bound itself should require more discussion around the language design.

?Sized itself being a "negative feature" confuses users, adding ?Move and ?DynSized will only make the situation worse,

I think it will make it better, because sized is right now one single exception. If there are more of it, it becomes more of a rule.

@kennytm I think some of your links go to the wrong comment... the last three all go to the same comment by @arielb1

Relevant: https://gankro.github.io/blah/linear-rust/
(I really would like more implicit bounds, however I am concerned about making things too complicated)

Worth noting that while Sized currently is not implied in many cases (e.g. on a trait) we probanly should make things like Move get implied everywhere, and require explicit where Self: ?Move to opt out.

@Manishearth I'd expect it to be written more often as trait Foo: ?Move.

@mikeyhew thanks, I’ll update it after the holiday.

Is there a "induction based" solution? I mean, what if
trait Foo {
    fn foo1(&self);
    fn foo(self);
}

automatically implies
trait Foo : ?Sized + ?DynSized + ?Move + ... {
    fn foo1(&self);
    fn foo(self) where Self: Move;
}

The (naive) idea is that wherever 'move operation' is implied in the method signature, an implicit 'where clause' requiring the type is Move is automatically added on a method basis. The existence of Move bound should automatically assume Sized and DynSized, i think...
On the concrete type side, make these auto trait. So they're automatically inferred just like Send and Sync...
I wonder if this can work?

@comex

So we have a hierarchy: ?DynSized < DynSized < Move < Sized

Having Move be a supertrait for Sized is something I've thought about, but there are potential types that are Sized + ?Move: for example, immovable generators or self-borrowing structs. Move definitely requires DynSized – you can't move something unless its size (and alignment, presumably) is known.
But Sized + ?Move is probably rare enough that we can just have people write exactly that for it.
Sized means Sized + Move
Move means Move (no Sized, and implies DynSized)
Sized + ?Move means Sized (without Move)
DynSized means DynSized (no Sized or Move)
The only difference between this and what you wrote is that Sized + ?Move is an option.

@lxrec

I think it's confusing only because Referent does not sound like it means LiterallyAnyType. It sounds like it exists solely for the custom DST use case and should never be mentioned in code that's not specifically messing with custom DSTs. If the goal is instead for all Rust types to implement those possibly-fat pointer create/split methods (is there any reason we wouldn't want this?), we should probably change the strawman name for it to Anything or AnyType or Unrestricted or something like that.

I hear you. If you're coming at it with the goal of removing all possible trait bounds, or to specify that T can be any type without any restriction, then having to write T: Referent does sound like a weird detail.
But in what context would you actually want to do that? Like, when would you have a generic type argument, associated type, or trait Self type that can literally be any type, without restriction? Usually you want to do something with values of that type. So if you only need to have it behind a pointer or reference, then you write T: Referent. If for some reason you need to be able to get its size and alignment, you write T: DynSized. And so on.
Perhaps there are cases where you're writing generic code and you literally have no requirements about the type, you don't even need it to be behind a pointer, but I'd like to see concrete examples. Two that I know of are LittleEndian and BigEndian from the byteorder crate. They are currently implemented as empty enums, which are Sized, so you don't need to write T: Referent. But they could, theoretically, be implemented as !Referent types, if we added them to the languages – and if that is desired, I would also like to add Type to your list of potential (pseudo) trait names. The behaviour of writing T: Type would be it just removes any and all default trait bounds. By writing T: Referent now, !Referent types could be backward-compatibly added to the language without the need for ?Referent syntax.

@withoutboats you say in https://github.com/rust-lang/rfcs/issues/2255#issuecomment-359988669 that the general concern less weirdness than making things "everyone's problem". But isn't it the other way around? Once can always ignore ?-trait bounds along with the weird use-cases that motivate them, but with positive trait, now everyone needs to care just to get back to the default case.

I had an idea that might be able to help with the ergonomics of ?-traits, and with commonly-repeated trait bounds in general: a language feature to opt into or opt out of a default bound at the crate or module level. For example, if you are implementing a smart pointer type, and you find that for every type parameter, you have to write ?Sized, then you could opt out of the default Sized bound for type parameters in that module.
Making default bounds a first-class language feature that libraries can use, instead of a special case for only a handful of builtin traits, would hopefully make them less confusing. It would also pave the way for changing which traits are default bounds in a new epoch edition.

For anyone who stumbles across this in the future:
The ?Moved trait bound didn't happen, because a new implicit bound was always the "brute force", "sledgehammer" option for those problems, and we've since found a better, more targeted solution: the Pin<T> library type. See https://doc.rust-lang.org/std/pin/ and https://boats.gitlab.io/blog/post/2018-03-20-async-vi/ for details on that.
The situation with ?DynSized is different, but mostly because Sized implies DynSized, which gives that proposal a loophole for some of the biggest problems discussed here. Thus, it's better discussed in the specific RFC thread proposing it: https://github.com/rust-lang/rfcs/pull/2594.
AFAIK, there are no other suggestions for new implicit bounds with strong motivation/demand.

Yeah i still don't fully grok all the compatibility concerns. With associated types, for example would say rather than Trait::Assoc: DynSized is not part of the trait itself, but a well-formedness condition on anything referring to the trait, and one would write Trait::Assoc: ?DynSized at the usage site to opt-out, just as one does with fresh type variables.

I am trying to find out what the general concerns are around ? bounds. I am coming here from https://github.com/rust-lang/rfcs/pull/3729 which suggests that we should have traits where adding a bound relaxes the requirements, which I find quite concerning and non-intuitive.
The issue here is rather long, is there a good summary anywhere? Replying to the concerns in the issue description:

?Sized itself being a "negative feature" confuses users, adding ?Move and ?DynSized will only make the situation worse,

Sure, but spelling this as T: ValueSized and making this implicitly mean "we now know less about T than if we didn't write anything"  is IMO even more confusing.

introducing new relaxed bound means downstream packages will need to reevaluate every API, to see if adding : ?Trait makes sense, and this needs to be done for every new relaxed bound.

This is true no matter the syntax we use for this, so avoiding ? bounds does not help.
@davidtwco you mention several times in your RFC that the lang team doesn't like ? bounds; do you know of a good write-up explaining why?

@davidtwco you mention several times in your RFC that the lang team doesn't like ? bounds; do you know of a good write-up explaining why? Niko said he'd most that here but it seems that never happened.

I don't know of a good write-up, I got that impression from reading all of prior art that I linked in #3729 - I got the impression that ?Sized is generally seen as confusing and hard to understand for new users, and as such adding more ?Traits isn't desirable.
I personally don't find the proposed alternative from #3729 more confusing, it's not necessarily the most intuitive but no more or less than ?Sized (I'm more familiar with ?Sized by now, but that's about the only difference).
In the recent language team design meeting on #3729 (while it was still a draft and ValueSized was called DynSized), there was this exchange on the subject:

Josh: General :+1: to the design here, but I think we should take a moment to consider the alternative of using ?DynSized, and the tradeoff between that and the proposed approach.
Among other things, using ?DynSized seems like it would not interact as cleanly with const, creating a more complex model for people. So on balance the RFC's approach seems like the right one. But I didn't see any discussion of that in the RFC.
davidtwco: I avoided introducing any ?Trait syntax because it seemed like the language team were firmly against introducing more of that in all the prior art.
Josh: You're not wrong, and we probably still are. Just want to figure out if we're losing anything by dismissing that approach, or if (as appears to be the case) the design in this RFC is just better in every way and we wouldn't want to do ?DynSized even if lang was completely fine with it.
NM: I am not sure what ?DynSized would even mean but it just seems megaconfusing to me. You are opting out from the default bound but it's not a binary thing, so what level are you opting out to?
NM: Note that there is a separate question of "when do you add entirely new kinds of default bounds"-- some features I want will require that (e.g., must move types) -- but that's a different set of complexities from this proposal, which is more about the "binary to multi-level".

With the proposals from #3729 in mind, I got the impression that ?Trait syntax was seen as even less desirable as with const traits and with hierarchies, it's even more confusing.

?Sized definitely is confusing, but no more than the minimum amount of confusion. The concept is normally ignored through a lot of a programmer's early Rust, so of course having to think about it suddenly is going to catch people by surprise. I'd make a comparison to lifetimes: introducing a lifetime into a function or a structure takes people by surprise until they get used to it, because you can write a lot of Rust with totally elided lifetimes. That's just where the ergonomic optimum is.
I'm with Ralf: spelling negative bounds as positive bounds just to avoid typing a ? doesn't actually help anyone, it's just worse.

The best write-up I can remember off the top of my head is that withoutboats' recent blog post on Pins has a "?Move"section about why a ?Move bound was rejected as a solution to the self-referential futures problem, in particular why it would've been a backwards-incompatible change.

That's an orthogonal problem, I think. That problem is not solved by picking a different syntax, it is a semantic issue.
The question of how to write down a type that is "not statically const Sized but still weaker-Sized" is a purely syntactic one.

Niko wrote up his thoughts on this here.
The lang team hasn't made a decision on this matter, and personally, I'd like to see more discussion and analysis.


feat: Add more providers

@leecalcote

@Nikhil-Ladha we're adding a few more providers - disable for now.
@prateeksahu we're adding an inactive "UT Austin" provider, which serves to indicate that a repository of research data is forthcoming.

Coool, Good to go!👍🏼

@prateeksahu @pranavk2 @tiwari @ame505


Fix: TypeError: Cannot read property "exists" from undefined.

Added exists to the property saved right from the start.
When deleting after the refresh, property which are TRUE are reseted to null, else they will alway be true forever since they would be saved as TRUE.
Removed the print "Refreshing " + name.
Reason: Having to click OK for each datatable config does not help to control the plugin, it slow down the process.
Here is a use case:

User has 10 datatable to refresh.
He start the process.
The user need to click ok for each config (he cannot click cancel).

Without the print, the whole refresh is made automatically without intervention. (Start and forget)

No problem!


MSAL/AD V2 not supported yet

We have been seeing a couple of issues related to AAD V2 auth flow not supported (including MSAL). It is probably worth adding a note here until its supported.
Reference: https://social.msdn.microsoft.com/Forums/en-US/8e687a97-12f7-4313-bc20-2d00179dc550/running-azure-function-with-azure-ad-auth-in-portal-results-in-401-unauthorized?forum=AzureFunctions

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

ID: 75e17529-8b8a-1d67-f0e1-840d1d3ca990
Version Independent ID: 265645df-ef21-4631-1744-7014b3ee681a
Content: Authentication and authorization - Azure App Service
Content Source: articles/app-service/overview-authentication-authorization.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: mahender,cephalin

@jcbrooks92 Thank you for raising this up to us. We'll update this doc along with the other below doc to include a note on this limitation.
https://docs.microsoft.com/en-us/azure/app-service/configure-authentication-provider-aad

@jcbrooks92 We have merged and update that includes a note with the current limitation. The change should be public within 24 hours.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

For developers new to these docs, AAD and MSAL are abbreviations / acronyms they can't relate to. If possible, please make a first use of the entire term before using the abbreviations. I had trouble finding out what MSAL stands for.


DataEditor edit window location issue

Describe the bug
After opening DataEditor's edit window, the edit window does not move when scrolling the web page.
To Reproduce
Steps to reproduce the behavior:

Double click the cell

Scroll the page

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Specifics (please complete the following information):

Python Version: 3.11.64
Reflex Version: 0.3.4
OS: Windows 11
Browser (Optional): Chrome

Additional context
Add any other context about the problem here.

The problem appears to have been resolved in version 0.3.5.

I thought this issue was resolved, but it still exists in version 0.3.6.

@Evenzel does it work for you in 0.3.5 and regressed in 0.3.6? Or was it never working?

As far as I remember, it didn't work at all

The issue is also present in the component itself, so it's not an error of implementation on Reflex side.
Maybe we could try to implement some workaround for this, but it might be easier to report the issue in glide-data-grid directly.
(On this page: https://glideapps.github.io/glide-data-grid/?path=/story/glide-data-grid-docs--editing-data the problem you describe happens)


exec.Command run ffmpeg error Could not find video device with name XXX among source devices of type video

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

$ go version
go version go1.16.6 windows/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
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\奔波霸\AppData\Local\go-build
set GOENV=C:\Users\奔波霸\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\奔波霸\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\奔波霸\go
set GOPRIVATE=
set GOPROXY=https://goproxy.io,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.6
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=F:\work\my\web\client\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\奔波霸\AppData\Local\Temp\go-build1829956365=/tmp/go-build -gno-record-gcc-switches

What did you do?
func main() {
	cmd := exec.Command("ffmpeg.exe", "-re", "-f", "dshow", "-i", "video='CyberTrack H3'", "-f", "mpegts", "-an", "-vcodec", "libvpx", "-cpu-used", "5", "-deadline", "1", "-g", "10", "-error-resilient", "1", "-auto-alt-ref", "1", "-f", "rtp", "rtp://<IP_ADDRESS>:5004")
	cmd.Stderr = os.Stderr
	cmd.Stdout = os.Stdout

	err := cmd.Run()
	if err != nil {
		log.Println(err)
		return
	}
	err = cmd.Run()
	if err != nil {
		log.Println(err)
	}
}

What did you expect to see?
I want to execute
ffmpeg -re -f dshow -i video='CyberTrack H3' -r 30 -s 1280x720 -f mpegts -an -vcodec libvpx -cpu-used 5 -deadline 1 -g 10 -error-resilient 1 -auto-alt-ref 1 -f rtp rtp://<IP_ADDRESS>:5004

in  exec.Command。

cannot execute the command line in the exec.Command.
At that time, I could successfully execute the change command directly in the terminal。 like

What did you see instead?
[dshow @ 0000019b48476500] Could not find video device with name ['CyberTrack H3'] among source devices of type video.
video='CyberTrack H3': I/O error

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


SVG working example

Category

[ ] Question
[ ] Bug
[X] Enhancement

Expected or Desired Behavior
Would we be able to get an example of the SVG elmType working? I have attempted to use it but almost all element types and property names needed to construct the SVG are not allowed by the specification.
For example:

viewBox is not an allowed attribute, but required to create an SVG properly
using txtContent to fill in the entire contents of the SVG wraps the contents with double quotes, making it fail
fill is not an allowed attribute, making colouring the SVG very difficult.

Unfortunately, pretty much everything outside of paths are unavailable in SVGs. However, there is a working sample that demonstrates drawing a pie chart using a combination of a containing div (with the fill style set that gets used by the SVG) available here:
number-piechart

I would love to see the full power of SVG elements supported (fill, stroke, circle, etc.) as it would allow many more visualizations. Sounds like a great candidate for UserVoice.


script (execution/loading) OR (script execution)/(loading) mechanisms

This question: "Does this specification enable new script execution/loading mechanisms?" is ambiguous and should be clarified.
I interpreted it broadly, as one should in the context of ambiguity in security, as (script execution)/(loading) mechanisms, especially since there were no other questions about "loading" of arbitrary (not just script) resources, which has network effects, tracking, etc.
For reference: http://dev.w3.org/csswg/css-ui-3/#security-privacy-considerations

I agree with @tantek's interpretation in http://dev.w3.org/csswg/css-ui-3/#security-privacy-considerations


[release-1.18] Update golang.org/x/net and grpc-go

Please provide a description of this PR:
Update various dependencies. Up to RMs if they wish to include this. I tried to limit the dependency updates.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-distroless_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-distroless

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-distroless_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-distroless

analyze-tests_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test analyze-tests

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-distroless_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-distroless

analyze-tests_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test analyze-tests

integ-cni_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-cni

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-distroless_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-distroless

analyze-tests_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test analyze-tests

integ-cni_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-cni

integ-pilot-multicluster_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-multicluster

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test lint

gencheck_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test gencheck

integ-basic-arm64_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-basic-arm64

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-ipv6_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ipv6

integ-ds_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-ds

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-distroless_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-distroless

analyze-tests_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test analyze-tests

integ-cni_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-cni

integ-pilot-multicluster_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-multicluster

integ-pilot_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote

integ-pilot-istiodremote-mc_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-istiodremote-mc

integ-cni_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-cni

integ-pilot-multicluster_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot-multicluster

integ-pilot_istio_release-1.18
6eece45fafa2d77dc4932caa3aa5c4abda950126
link
true
/test integ-pilot

integ-ambient_istio_release-1.18
1862639e29c865d9b0ad6435b76df9e674d6d6a5
link
true
/test integ-ambient

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

/retest


⚡ Added & updated some icons

Added Movie Web and Updated Coinbase

Thanks 🚀🙂 (I have changed the branch to next, I'm preparing v4.1 🥳)

Alright buddy^^ 🫠


Uncaught TypeError: $(...).bootstrapDualListbox is not a function

I downloaded the "bootstrap4DualListbox" plugin, added the configuration in adminlte.php :
'bootstrap4DualListbox' => [
            'active' => true,
            'files' => [
                [
                    'type' => 'css',
                    'asset' => true,
                    'location' => 'vendor/bootstrap4-duallistbox/bootstrap-duallistbox.min.css',
                ],
                [
                    'type' => 'js',
                    'asset' => true,
                    'location' => 'vendor/bootstrap4-duallistbox/jquery.bootstrap-duallistbox.min.js',
                ],
            ],
        ],

But when trying to make it work I get this error in the browser console:

Uncaught TypeError: $(...).bootstrapDualListbox is not a function
the script is like this:

and my html is :

Bootstrap Duallistbox

              <button type="button" class="btn btn-tool" data-card-widget="collapse">

              </button>
              <button type="button" class="btn btn-tool" data-card-widget="remove">

              </button>

                  Multiple

           Showing all 7     <button type="button" class="btn btn-sm clear1" style="float:right!important;">show all</button>      <input class="form-control filter" type="text" placeholder="Filter">
     <button type="button" class="btn moveall btn-outline-secondary" title="Move all">>></button>
   <select multiple="multiple" id="bootstrap-duallistbox-nonselected-list_" name="_helper1" style="height: 104px;"><option selected="">Alabama</option><option>Alaska</option><option>California</option><option>Delaware</option><option>Tennessee</option><option>Texas</option><option>Washington</option></select>

           Empty list     <button type="button" class="btn btn-sm clear2" style="float:right!important;">show all</button>      <input class="form-control filter" type="text" placeholder="Filter">
          <button type="button" class="btn removeall btn-outline-secondary" title="Remove all"><<</button>
   <select multiple="multiple" id="bootstrap-duallistbox-selected-list_" name="_helper2" style="height: 104px;"></select>

<select class="duallistbox" multiple="multiple" style="display: none;">
                    <option selected="">Alabama</option>
                    <option>Alaska</option>
                    <option>California</option>
                    <option>Delaware</option>
                    <option>Tennessee</option>
                    <option>Texas</option>
                    <option>Washington</option>
                  </select>

            Visit Bootstrap Duallistbox for more examples and information about
            the plugin.

Is there something I am doing wrong? or is it some bug? Thanks

Hi @alejandromora99 , probably you are doing something wrong since I have used several plugins this way without any problem. Be sure to check next things:

That files vendor/bootstrap4-duallistbox/bootstrap-duallistbox.min.css and vendor/bootstrap4-duallistbox/jquery.bootstrap-duallistbox.min.js exists inside the public folder of your project. Also check that paths are correct and that file permissions are ok.

Before initializing a plugin, it is always nicely to wait for document to be ready. Also, you need to push scripts inside the provided js section tag to include custom javascript/jquery code:
@push('js')

@endpush

It worked for me to wait for the document to be ready :), I have a question, why use @push ('js') and not @section ('js')?

@alejandromora99 With @section()  you define the entire content that you will later render with yield(), with @push() you can push multiple elements into a @stack(), so you can push multiple javascript code into the same tag. Read next:

https://laravel.com/docs/8.x/blade#stacks
https://laravel.com/docs/8.x/blade#layouts-using-template-inheritance

@Shidersz  Ahh thanks friend, one last question, does this adminlte package provide jquery to the whole project? I just realized that I can use jquery in the views and in my laravel mix js files without injecting a cdn

@alejandromora99 Yea, jQuery is actually required by the underlying AdminLTE package. You may check master.blade.php file to see what files are included in the base layer.


added adding Folders to project, replaces BrowseForFoldersDialog by CommonOpenFileDialog

Hi,
I've implemented adding folders to projects/project-filters (only for virtual folder).
Please have a look at it.

Hi,
since I'm not sure whether this project is actively maintained, and I think the changes in this PR are really useful for the community, I'll wait two more days for a reaction, otherwise I will revoke it and publish a new VS-Extension.
Tobias

I will have look at this as soon as possible, have patience.

Ok, thanks!
Am 2021-03-13 11:11, schrieb Cecilia Wirén:

I will have look at this as soon as possible, have patience.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Links:
[1]
https://github.com/ceciliasharp/Extension.FolderToSolutionFolder/pull/13#issuecomment-798086746
[2]
https://github.com/notifications/unsubscribe-auth/ACCX7W5TBBNILR5SS5DGQVTTDM247ANCNFSM4ZARQYBA

@tobias-loew I have tried your changes out now and they will be a good addition to the extension. But would like to have an other name for the folder add just to clarify that it will add the files as liked file not actually add them. Can 'add folder as linked files' work or will that be too confusing you think? the more correct description would be something like "add folder content as folder and link foldes files into them" but that is tooooooo long :-D

There is also to consider, that .net-projects and non-.net-projects (like C/C++) behave differently:

.net-projects add real folders: adding a folder to a .net-project will create the folder on disk (if it doesn't already exist), files are copied (if not already present)
non-.net-projects add virtual-folders: the added folder only exists in the VS-projects, files are just links

The code currently handles both transparently: it first tries to add virtual-folders. If that doesn't work it tries real-folders.
So, best would be some text describing both, or dynamically adjusted text depending on the project type.

I just tried it out on a console application .net 3.5 and the folders were created on disk but the files were not created just linked. (so not copied that you describe). nices way of handling this would be to catch what type of project it is and show the different menu options depending on that.

Of course, you're right: I didn't use the extension for testing file-insertion on .net-projects, but simply dragged one in from the explorer, which resulted in file-copying.
I checked the docu of ProjectItems (https://docs.microsoft.com/en-us/dotnet/api/envdte.projectitems?view=visualstudiosdk-2019): it has both Methods AddFromFile and AddFromFileCopy.
It seems that .net-projects should use AddFromFileCopy, non-.net-projects and the solutions-folders should use AddFromFile.

IMHO only the combinations (real-folder + AddFromFileCopy) and (virtual-folder + AddFromFile) make sense, as (real-folder + AddFromFile) will end up with a bunch of empty folders and for (virtual-folder + AddFromFileCopy) you  don't know, what the base-folder is or you put all files in the same folder and end up with name-conflicts,
So, how to figure out if virtual or real folders should be added to a project: the list of different project-types is quite-long (as of 2016 https://www.codeproject.com/Reference/720512/List-of-Visual-Studio-Project-Type-GUIDs) and rather incomplete (at least Intel-Fortran-projects are missing, but I guess many more, plus there will be new ones), so it could be a two stage test: first looking for a registered project type, otherwise use the rootItems.AddFolder test (and that can be cached, even to the SettingsStore )


[WIP] Fix Travis MacOS pyenv install error

The MacOS job is failing on Travis due to an error in pyenv install.
Do not merge yet.

Duplicate of https://github.com/chainer/chainer/pull/6754.


[Designer] Adaptive Card works on emulator but not Teams

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/8065
Details from original post:
Hi there,
I tested Adaptive card by curl to my MS Teams webhook:
curl -H 'Content-Type: application/json' -d @size1.json  $mywh
In the json file, I specified external URL image https://image-charts.com/chart?cht=pd&chd=t%3A24.119127516778523%2C74.66442953020135%2C1.2164429530201342&chs=700x400&chdl=Failed|Passed|Skipped&chl=24.1%25|74.7%25|1.2%25&chco=ed421f|37b84c|A9A9A9&chli=2384&chlps=color%2CFFFFFF|font.size%2C10|textStrokeWidth%2C0.4&chdlp=b
From my team channels, image is not rendered:

However, it's working on Adaptive Cards https://adaptivecards.io/designer as below image:

My json file is here:
size1.json.zip
Document Details
⚠ Do not edit this section.It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

The same question is being tracked here at https://learn.microsoft.com/en-us/answers/questions/1104017/adaptive-card-works-on-emulator-but-not-ms-teams.html. Please follow above thread for further updates.
We are closing this issue here, please feel free to reach out to us if you have any questions. Thank you.


{"error":"Valve's servers appear to be offline, please try again later","code":5}

Doesnt matter what I do, I always get this error.
Updating Game Files...
Logging in *****bot
*****bot Generating TOTP Code from shared_secret
*****bot About to connect
Listening for HTTP on port: 1739
Connected to the database
*****bot Connected
Fetched items_game_cdn.txt
Fetched csgo_english.txt
*****bot Log on OK
*****bot Received servers.
Fetched items_game.txt
Please help

Hi friend, are you sure the account you are using has CSGO?

As @Muritavo said, you need to own CSGO on the account as stated in the readme.


Split kslides into multiple submodules that on can opt in

At the moment, kslides-core, holds implementation of every plugin and add on. This is not convenient for someone who just needs something basic.
e.g. For someone who doesn't even need to utilize plots (and the plotykt library), has no option bu to bring in the whole plotykt train when they add kslides-core as a dependency.
I haven't gone through the whole code base, but I think it might be a good idea to split these and let them be added as add ons.
kslides-core, can have just the kslides block and other core functionality as the name implies. Other modules like using plotykt or kotlin-playground(assuming it brings in third-party dependencies) can be optional dependencies store into a module like kslides-ploty (or something similar).
In the end, we will have kslides-core as only a core dependency, and other add ons to be added only when needed.
Also, kslides require some transitive dependencies to be included by the consumer. This is a little bit tedious, we can leverage the amount of transitive dependencies and yet include them all without requiring additional dependencies (especially transitive ones)

I agree, they should be split out. I will work on it this week. Thanks!

Hello there, is there a contribution guide I can read about this so that I may be able to contribute?

Sorry, I am afraid no such guide exists.

So, does that mean I can't contribute?

You are free to contribute. Just submit a PR.

I separated plotly-kt support into a separate module: com.github.kslides.kslides:kslides-plotly


fix(react-query): omit unnecessary type

BREAKING CHANGE: If project have these omitted type by this commit, It will be breaking change.
Omit unnecessary type

isLoadingError, isRefetchError: type relative with error
queryKey, queryFn: if options have to be 3rd useQuery parameter, queryKey, queryFn field have to be omitted in options type

PR Checklist

[x] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

Breaking Change seems a bit minor, so it will be released with other BCs.

@artechventure, I resolved some conflict in a1b8456.

I close this Pull Request. because of far distance with main branch.


Markdown Editor

To add a WYSIWYG for when editing markdown files. Similar to what is offered on Github and Gitea. Easily highlight a text and click the B button to make it bold, or the I button to make it italic. Easily add links, lists, tables, etc.
Would be useful for creating documentation on code before publishing it on Github or Gitea by using VS Code as a offline markdown editor.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


DioError [DioErrorType.DEFAULT]: SocketException

DioError [DioErrorType.DEFAULT]: SocketException

I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
Flutter

Platform Version
1.20.0

Dio Version
3.0.10

Android Studio / Xcode Version
Android Studio 4.0.1 / Xcode 11.1 (11A1027)

Repro rate
sometimes 90% (As long as it appears, it will always appear)

Repro with our demo prj
I don't know it, I haven't tried it with the demo, the time limit is tight

Demo project link
Sorry, This APP is in the development stage and not yet online

Issue Description
Exception message: DioError [DioErrorType.DEFAULT]: SocketException: Failed host lookup: 'goat.cacifu.com' (OS Error: nodename nor servname provided, or not known, errno = 8)
As long as this problem occurs, restart the emulator or mobile phone to be normal, but it will recur after a while.
After testing, the server configuration is normal and correctly configured.

The latest discovery is that I initiated multiple requests on a page without using the Future.wait([Futures]) method. I don’t know if it is caused by this. After I changed to Future.wait([Futures]) method, it seems to be normal, but it remains to be seen.

After observation and testing, the problem still exists after switching to Future.wait([Futures])

your problem will easily solved all u have to do is to add this line in your Android>app>main>src>AndroidManifesto.xml file
<uses-permission android:name="android.permission.INTERNET" />
after the package name or under the manifesto tag

Thank you very much for your answer. I have configured and checked as you said. Whether the problem still exists or not remains to be seen. In addition, according to my observation during this period, I found that the problem may be whether my computer uses a proxy or not.

Hello, I encountered the same problem as the class.


Missing avatar and Misalignment within Footer Author Card in Firefox

Following up from TryGhost/Ghost#9646.

The full-post-footer element is misaligned in Firefox. However it works fine in Chrome.
The default avatar is also not displayed in both browsers (in the case where there is no profile image set for the author).

The comparison screenshots are below.
Chrome - Single Author with no Profile Image Set (Issue: Missing avatar)

Chrome - Single Author with Profile Image Set (Working As expected)

Firefox - Single Author with no Profile Image Set (Issue: Missing avatar and Misaligned)

Firefox - Single Author with Profile Image Set  (Working As expected)

Steps to Reproduce

Create a post under an author with no profile image set.
View it in firefox

Technical details

Casper Version: 2.3.0

I can take this up and send a PR to fix this in an hour.


Edit: WLVT-DT1

Channel ID (required)
WLVTDT1.us
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
No response
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
https://image.pbs.org/bento3-prod/wlvt2-pbs/2019 PBS39 Blue/e5fd2adf69_PBS39-2019-Blue.png
Notes
add logo

Must be under 512px.


[Doc Improvement] [Developer-portal-for-Teams]

removed analyze your app's usage section

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
95
4
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 554ab0c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


B-18173 Move history tracking for PPM weight docs

B-18173
Summary
This PR addresses the need to track a closeout counselors actions when reviewing weight tickets, whether they make adjustments or are approving or rejecting the weight. It also includes migrations and move_history_fetcher.sql changes for B-18174 and B-18175 as well; I chose to include that work in this PR so we wouldn't create 3 separate temp tables in 3 separate PRs and slow our query down.
How to test

Login as a service counselor and view closeout PPMs
Review documents and make adjustments to the values while reviewing a weight ticket
Accept or reject your changes and save
Navigate to Move history and confirm your changes are reflected there

I'm not seeing the changes I made during document review reflected in the move history

I'm not seeing the changes I made during document review reflected in the move history

Hmm.. Closeout PPMS, changes to weight tickets (not pro-gear or other tickets for this specific PR)


Add tests to trigger space to switch mode

Add tests to trigger space to switch mode between structure and content

@vxsx fixed

:+1:


Provide installation method for cluster without OLM

Depends on #77, #74

Same comment as in #75

Same comment as in #75

Long term solution can be figured out later.


Explain commitments

The graph protocols use Pedersen commitments, but it is not explained how they work. There should be a dedicated chapter on commitments.

Closed by d6932a8e56de29a1fb7407e87073a0531b98b486


Advanced name preview doesn't seem to work.

See attached screenshot for example.

I am using Google Chrome. didn't test if the problem persists on other browsers.

The Advanced name Preview currently only shows BBCode preview, for testing purposes.
Consider using [img]http://i.imgur.com/UbNPI0E.jpg[/img]KEKTUS , or wait until html previews have be re-implemented. By the way, has the game changed urls or perhaps shut down? I time out whenever I try to open the game.

I time out too, which is a bit unfortunate.


BUG - ExchangeLocation gets cleared when search name has space and search is assigned to a case.

Hi,
I noticed that when creating a compliance search like this:
New-ComplianceSearch -Name "Search 1" -ExchangeLocation "all" -ContentMatchQuery "test123 OR 123qwe"
it all works and ExchangeLocatoin is {ALL}, but when creating it like this:
New-ComplianceSearch -Name "Search 1" -ExchangeLocation "all" -ContentMatchQuery "test123 OR 123qwe" -case "1234"
Exchange location is empty. I fugured out that it is a matter of space in the name of the search.
To sum up:
When creating a compliance search and name of the search contains a space - it is not an issue UNTIL you would like it to be assigned to a case - in such situation search name cannot contain a space sign as then the ExchangeLocation attribute is cleared.

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

ID: 6e72de6a-dd0f-e6e3-c4b1-63ee1cf752e8
Version Independent ID: 228e51b7-a16a-1e5d-11c9-95cdc30b23dd
Content: New-ComplianceSearch (exchange)
Content Source: exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@zaicnupagadi, thanks for writing that up. I updated the description of the Name and Case parameters accordingly.


JAVA-2916: implement ObjectId spec

Made changes to the ObjectId based on the spec. The biggest change is replacing the machine and process IDs to a random 5-byte array.
The ObjectId spec: https://github.com/mongodb/specifications/blob/master/source/objectid.rst
Evergreen patch: https://evergreen.mongodb.com/version/5c0ab24fe3c3315423120911

Minor change.
Evergreen patch: https://evergreen.mongodb.com/version/5c0ed1742fbabe335d419b11

Evergreen patch: https://evergreen.mongodb.com/version/5c0f16be2a60ed57fa31610f


Introducing branching operator

Hi, please take a look at my shot at implementing the branch/try!/? operator.
In this approach i've implemented it via branch property, which propagates the types correctly and is chainable, e.g
val: float = get_cmd_line().branch.parse_float().branch
the only inconvenience is that functions need to be decorated with @branching in order to turn the auxiliary exception on the error path and return it by value to the calling code
I've also fixed __eq__ on the Err to handle exception comparison - it's very useful in conjunction with @as_result that tends to return Err[std exception]

Hi @gp-alex, thank you for this PR. I don't currently have the time to go through this PR, but I'll time to come back to this as soon as I'm able.
Just a few things off the top of my head.
I'm not 100% sure about your proposed .branch operator. It's a bit ad-hoc, I haven't seen something like this. Since this library is heavily influence by Rust and the Result type, we'd like to match the APIs as much as possible in Python. Have you considered the do-notation support or the .and_then operator? There's also some discussion about flow and bind here https://github.com/rustedpy/result/issues/146 which I think is more appropriate to explore over a ad-hoc .branch operator

I've also fixed eq on the Err to handle exception comparison - it's very useful in conjunction with @as_result that tends to return Err[std exception]

I'll take a look at this after. But it would be better to separate any bug fix/code improvement work from the new functionality to keep PRs small and focused.

I've also fixed eq on the Err to handle exception comparison - it's very useful in conjunction with @as_result that tends to return Err[std exception]

If we were to introduce this exception comparison behavior then this library is changing the behavior of exception equality away from what Python does by default.
In normal Python ValueError("something") == ValueError("something") is False.
But the proposed change would make this True if you wrap the two in an Err, Err(ValueError("something")) ==  Err(ValueError("something")).
I don't think it would be good idea for this library to make this decision for the programmer. The programmer should implement this logic themselves and control how they want do exception equality.


AspireShop deploys to Azure in broken state

AspireShop bug report
User Story
As a software engineer trying out the AspireShop sample, I expect that when I deploy to Azure using the azd init and azd up commands that the sample be deployed to azure in complete working order.
Bug Description:
I pulled down the aspire-samples and tried to deploy the AspireShop web site to azure using azd init and azd up - the only material changes I made to the application was setting up instrumentation for App Insights. The basketcache and catalog and catalogdbmanager services are all broken. Please see the following screenshshots and information below for help in diagnosing and troubleshooting this.
Redis Error Message
The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: UnableToConnect (None, 0-read, last-recv: 0) on basketcache:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 5s ago, last-write: 4s ago, unanswered-write: 5s ago, keep-alive: 60s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 5s ago, v: <IP_ADDRESS>420, command=GET, timeout: 5000, inst: 0, qu: 0, qs: 12, aw: False, bw: CheckingForTimeout, rs: ReadAsync, ws: Idle, in: 0, in-pipe: 0, out-pipe: 0, last-in: 0, cur-in: 0, sync-ops: 0, async-ops: 29, serverEndpoint: basketcache:6379, conn-sec: 56, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: basketservice--76q7go8-557676c66f-8f7ml(SE.Redis-v<IP_ADDRESS>420), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=0,Free=32767,Min=4,Max=32767), POOL: (Threads=4,QueuedItems=0,CompletedItems=5147,Timers=9), v: <IP_ADDRESS>420 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) UnableToConnect (None, 0-read, last-recv: 0) on basketcache:6379/Interactive, Flushed/ReadAsync, last: ECHO, origin: ResetNonConnected, outstanding: 12, last-read: 5s ago, last-write: 4s ago, unanswered-write: 5s ago, keep-alive: 60s, state: ConnectedEstablishing, mgr: 10 of 10 available, last-heartbeat: never, global: 5s ago, v: <IP_ADDRESS>420

Broken containers screenshot

Azure App Insights screenshot

This issue also repro on AspireWithDapr sample using VS 17.12 Preview 4 + Aspire 9.0.0.


Request for a short wiki on how Drywall can be integrated with Android

Drywall is perfectly working for web based app, if I want to use the webservice from an Android or iOS app, how do I proceed?

Thanks for opening an issue. #383 had a similar question.
My answer there is essentially the same:

[...] You could customize the API to support mobile/desktop app clients, but those decisions aren't baked in. I also suggest checking out Frame, which is the Drywall API, built with hapi instead of express, has much better testing and doesn't come with all the front-end stuff.

Thank you! Frame is awesome!


Segfault when compiling with clang

For some reason when compiling with clang without optimizations rm_vec4_wrapf segfaults on my machine. It may happen with other functions aswell, will look into it.
Compiling with any of -O1, -O2 or -O3 fixes the segfault...

Tested almost all of the vec4 functions and for some reason almost all of them segfaults?!
maybe it's an issue of how clang handles intrinsics?

Update: it seems to be the same on windows using cl...

Update: it works on x64 Native tools etc. using cl, but not on x86 using cl. Might just be my pc though.

Seems to be fixed right now. Probably because of better way of converting from struct to float* using unions instead of doing some wacky pointer stuff.


Remove log4j vulnerability

This change upgrades the log4j dependency to a version that is not known to have vulnerabilities. A vulnerability (https://www.cvedetails.com/cve/CVE-2017-5645/) has been reported for the previous version.
Fixes #75

Coverage remained the same at 93.223% when pulling c755aebac6b6c0203c6e287dd3dba43e27f8c846 on pedro-carneiro:remove-log4j-vulnerability into 662a53c88d1acb002d018cde0d448c56955e9125 on Unleash:master.

thanks :fire:


Tado device_tracker exception when mobile device location unknown

Description:
Tado device_tracker exception when mobile device has geofencing enabled but location is currently unknown. This happens when a mobile phone app hasn't been active for a longer periode of time.
The tracker crashed and all devices where marked as 'away'.
Related issue (if applicable): fixes. No issue registered.

Hello @jmvermeulen,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

13b43ad54fa6935bfd684cf135ffd21ac30f347e - This commit has something that looks like an email address (j.vermeulen@rgbplus.nl). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hi @jmvermeulen,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Sorry for double review. I make a misstake and use the wrong button.

@pvizeli thanks for the review!
Applied your change.


Link in this git about is incorrect

The current link in the git about is incorrect, the correct link is: https://themes.gohugo.io/themes/hugo-theme-codex/
Not a big issue, but also easy to fix. Pls update it if possible 👍

Thank you. Fixed!


EdgeGPT这个项目是否可以参考？

https://github.com/acheong08/EdgeGPT
只要提供cookie就可以使用，不需要VPN，所以如果你这个项目中提供导入cookie是否就能用了？

The chat API used in the project you mentioned can be accessed directly in China and does not get redirected. Cookies are used for account authentication.
BingGPT is different from that project, it needs to load a page of Bing that will detect your IP on the server side. You only need to use VPN when you start the app. Chat requests sent after the page is loaded do not require a VPN.

所以，如果你提前将Bing的网页资源嵌入在本地，只是将后台的请求通过websocket直连是否就成？

The page will be updated by Bing continuously, it is meaningless to save the page locally. It would be better to look for EdgeGPT-based websites or software depending on your needs.


page is not responsive al all

Describe the bug
The website's responsive design is failing on multiple device sizes. Specifically, on small screens (e.g., smartphones with a width of 320px or less), the navigation menu overlaps with the header content,
To Reproduce
Navigation Menu: Implement a media query targeting screens with a width of 320px or less to adjust the styling of the navigation menu. Consider using a collapsible menu or hamburger icon to save space.
Images
: Ensure images use responsive design techniques, such as setting the max-width to 100% and height to auto, to maintain their aspect ratio and fit within the screen dimensions.
Horizontal Scrolling:
Review the CSS for any fixed-width elements that may be causing horizontal scrolling and adjust them to be responsive. Use relative units like percentages or viewport widths (vw) instead of fixed pixels.
Screenshots

Please assign me this issue

@devagya-rattan Issue assigned to you

Please assign me this issue

You can work on it
I have some other work to do
On Tue, 11 Jun 2024, 10:03 Ad2iti2003, @.***> wrote:

Please assign me this issue
—
Reply to this email directly, view it on GitHub
https://github.com/SUGAM-ARORA/UniCollab/issues/194#issuecomment-2159773471,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2W5TLLHLXLJIY5ORCQMFQLZGZ42BAVCNFSM6AAAAABISECJBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZG43TGNBXGE
.

@SUGAM-ARORA  can i work on this

@Tejsvapandey1 Yes you can work on this. When the required changes has been made you can tag me


Even when the items in  are updated,  does not update.

Describe the bug
Even when the items in  are updated,  does not update.
Reproduction
https://stackblitz.com/~/github.com/recsater/flowbite-svelte-issue-template?file=src/routes/%2Bpage.svelte

click sdf to add item.
Before click the header to sort, table is not updated.

Flowbite version and System Info
System:
    OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (16) x64 Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
    Memory: 37.61 GB / 62.73 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 23.0.0 - ~/.nvm/versions/node/v23.0.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v23.0.0/bin/npm
    pnpm: 9.15.0 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chrome: 131.0.6778.204

    "@sveltejs/adapter-auto": "^3.3.1",
    "@sveltejs/kit": "^2.10.1",
    "@sveltejs/vite-plugin-svelte": "^5.0.1",
    "@types/ramda": "^0.30.2",
    "autoprefixer": "^10.4.20",
    "flowbite": "^2.5.2",
    "flowbite-svelte": "^0.47.4",
    "flowbite-svelte-icons": "^2.0.2",
    "postcss": "^8.4.49",
    "postcss-load-config": "^6.0.1",
    "svelte": "^5.11.2",
    "svelte-animated-icons": "^0.7.0",
    "svelte-awesome-icons": "^2.0.1",
    "svelte-check": "^4.1.1",
    "tailwindcss": "^3.4.16",
    "typescript": "^5.7.2",
    "vite": "^6.0.3"

duplicate of #1493


[WFLY-16349] Upgrade to jakarta.* versions of MP reactive messaging

https://issues.redhat.com/browse/WFLY-16349

@kabir This will conceptually conflict with 2 open PRs:
https://github.com/wildfly/wildfly/pull/15515
https://github.com/wildfly/wildfly/pull/15528
The first one might need some work as it might be doing more dependencyMgmt stuff than is strictly necessary. But anyway we should align on how/where we manage these TCK versions.
The latter is partly about getting rid of use of jakarta.el:jakarta-el-api, which we won't use at runtime (we use a spec fork, which now has a release) so we shouldn't use it at compile or test time. So we shouldn't introduce another use of it here.

@bstansberry I think it should be in order now. I tried to do this before finishing on Friday but that el-api dependency made it a bit more complicated than first thought.


Feat/update data process

[中文版模板 / Chinese template]
🤔 This is a ...

[ ] New feature
[x] Bug fix
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Enhancement feature
[ ] Refactoring
[ ] Update dependency
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Release
[ ] Site / documentation update
[ ] Demo update
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link

🔗 Related PR link

🐞 Bugserver case id

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] TypeScript definition is updated/provided or not needed
[ ] Changelog is provided or not needed

🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough

https://github.com/VisActor/VChart/blob/c0ccc60b9e5ff47c64a798c0517bf66dc7a144c4/packages/vchart/src/model/interface.ts#L208
reMakeData是不是可以删掉了？

https://github.com/VisActor/VChart/blob/c0ccc60b9e5ff47c64a798c0517bf66dc7a144c4/packages/vchart/src/model/interface.ts#L208
reMakeData是不是可以删掉了？

done


Migration runner and MigrationContent functions

This PR externalizes the logic in migration runners and the migrationContent function.  MigrationContent is now a public function with a flag to disable templating.  This PR simplifies the findMigrations functions so they can be overwritten more easily.

Thanks!


Parcel validator ignores missing scripts.defines

I created a parcel to distribute some files on a cluster. I had no need for environment variables so I omitted the env script. After validating and activating my parcel, CM would fail to start any CDH roles. The STDERR output showed that the PARCEL_DIRNAME was using the name of my parcel instead of CDH. This made it impossible for agent scripts to locate bigtop.
It seems that in /usr/lib/cmf/service/common/cloudera-config.sh source_parcel_environment assumes that $SCRIPT_ARRAY and $DIRNAME_ARRAY are congruent. Because my parcel.json omitted scripts.defines, these arrays were incongruent and so CDH_DIRNAME got set to my parcel's name in cdh_env.sh.
The analysis in the preceding paragraph could be wrong. The upshot is that everything worked again after I added a defines script to my parcel. The parcel validator should not have approved a parcel without the required script.

Fixed in 5.3 update.


API: Get relations for an object uuid

Request:
GET shield.io/admin/v1beta1/objects/{id}/relations?subject_kind=user&relation_type=member
Response:
{
    "relations": [
        {
            "user": {
                // shall have the entire user object
            },
            "group": {
                // shall remain empty as the type is user
            },
            "type": "user",
            "role": "member"
        },
        {
            "user": {
                // shall remain empty as the type is group
            },
            "group": {
                // shall have the entire group object
            },
            "type": "group",
            "role": "owner"
        }
    ]
}

Should we mention that the user/group is actually the subject in this response. One way to do that would be as below -
{
    "relations": [
        {
            "subject": {
                "user": {
                    // shall have the entire user object
                },
                "group": {
                    // shall remain empty as the type is user
                }
            },
            "subject_type": "user",
            "role": "member"
        },
        {
            "subject": {
                "user": {
                    // shall remain empty as the type is group
                },
                "group": {
                    // shall have the entire group object
                }
            },
            "subject_type": "group",
            "role": "owner"
        }
    ]
}

Yes, let's go with subject_kind and relation_type both in request params and response's relation objects.
Yes, we can put user and group inside the subject, my only concern was the extra level of nesting. If we are fine with that, we can definitely go with it.

Based on the discussion, the final request/response contract shall look like the following:
Request:
GET shield.io/admin/v1beta1/objects/{id}/relations?subject_type=user&role=member
Response:
{
    "relations": [
        {
            "subject": {
                "user": {
                    // shall have the entire user object
                },
                "group": {
                    // shall remain empty as the type is user
                }
            },
            "subject_type": "user",
            "role": "member"
        },
        {
            "subject": {
                "user": {
                    // shall remain empty as the type is group
                },
                "group": {
                    // shall have the entire group object
                }
            },
            "subject_type": "group",
            "role": "owner"
        }
    ]
}

Will look into making the "subject" a oneof field, which will take one of the user or group values. This might make the response JSON, look a bit different from the one above.


[soy] Extend mode and add tests

Extend soy mode with

template/variable definitions
variable usage checking
types
additional keywords (as, and, or, not, in)
indentation fixes
tests

With changes

Without

Thanks! Merged as https://github.com/codemirror/CodeMirror/commit/2bed274eb4287624cdc5c07762a32c4042e3b3dc


dir .docker_config not created on first startup

Beta 5.0.2
Starting ioBroker...
/opt/scripts/iobroker_startup.sh: Zeile 501: /opt/iobroker/.docker_config/.healthcheck: Datei oder Verzeichnis nicht gefunden

Thank you. There was an issue with some new paths. :) I just corrected it. Beta Branch is now building. Think a new build v5.0.2beta will be available for download in 30 minutes.
Regards,
André


Add test_helper to RssLogsControllerTest

Fixes at least:
$ rails t test/controllers/rss_logs_controller_test.rb
/vagrant/mushroom-observer/test/controllers/rss_logs_controller_test.rb:3:in `<top (required)>': uninitialized constant FunctionalTestCase (NameError)

class RssLogsControllerTest < FunctionalTestCase
....

Coverage: 93.341%. Remained the same when pulling bd037c2042ff3d27c01fb1f9506331761c9e3f61 on jdc-rss_logs_controller_test into aba26916451c6453c517c71742c7a18e9c2a1624 on master.


[gw-api]added: support for full path rewrite

Add support for gateway-api full path rewrite (HTTPPathModifier)
This change is only an initial version of support.
It is better to change istio.HTTPRewrite but thats a public api change.
Feedback is most welcomed

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

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

/ok-to-test

@LiorLieberman: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5b939a7bbdb9215dd5bcca222538a12a1c1b2b5f
link
true
/test lint

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5b939a7bbdb9215dd5bcca222538a12a1c1b2b5f
link
true
/test lint

gencheck_istio
5b939a7bbdb9215dd5bcca222538a12a1c1b2b5f
link
true
/test gencheck

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

@LiorLieberman: PR needs rebase.

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

Can we make it %FULLREPLACE()% ? Nothing Istio specific about it.
Hopefully at some point Envoy could implement this natively - there is
little point using a regex to just set a value.
On Thu, Jan 5, 2023 at 6:27 AM Lior Lieberman @.***>
wrote:

@.**** commented on this pull request.
In pilot/pkg/networking/core/v1alpha3/route/route.go
https://github.com/istio/istio/pull/42605#discussion_r1062532578:

@@ -477,7 +477,20 @@ func applyHTTPRouteDestination(
out.Action = &route.Route_Route{Route: action}

if in.Rewrite != nil {

action.PrefixRewrite = in.Rewrite.GetUri()

action.ClusterSpecifier = &route.RouteAction_Cluster{

	Cluster: in.Name,

}

uri := in.Rewrite.GetUri()

if fullURI, isFullPathRewrite := cutPrefix(uri, "*fullreplace*"); isFullPathRewrite && model.UseGatewaySemantics(vs) {

summarizing my understanding from our offline chat.
I will go with %ISTIO_FULLREPLACE()%
and should come up with a better proposal of how(and if) we want to insert
substitutions to istio (similar to what envoy supports here
https://github.com/envoyproxy/envoy/blob/main/source/common/formatter/substitution_formatter.cc
Thoughts? @costinm https://github.com/costinm @howardjohn
https://github.com/howardjohn
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/42605#discussion_r1062532578, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2R5JFMLI2CVZZARXF3WQ3K63ANCNFSM6AAAAAATMEYZ44
.
You are receiving this because you were mentioned.Message ID:
@.***>

@LiorLieberman: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

integ-cni_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-cni

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

integ-cni_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-cni

integ-helm_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-helm

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

integ-cni_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-cni

integ-helm_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-helm

unit-tests_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

integ-cni_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-cni

integ-helm_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-helm

unit-tests_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests

lint_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test lint

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

@LiorLieberman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests-arm64

integ-basic-arm64_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-basic-arm64

integ-telemetry_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry

integ-pilot_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-pilot

integ-operator-controller_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-operator-controller

integ-security_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-security

integ-telemetry-mc_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-telemetry-mc

integ-cni_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-cni

integ-helm_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-helm

unit-tests_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test unit-tests

lint_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test lint

integ-distroless_istio
c7434f5630de72d1666121a721545f4e94f737ec
link
true
/test integ-distroless

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

/test integ-telemetry


Users want to be able to create Camel Routes and / or Rest DSL from an OpenAPI spec

We need an action that can take an OpenAPI spec (as uri or file) and generate Camel Routes, Rest DSL or both from it using the Camel REST DSL OpenApi Maven Plugin. (Is Camel JBang using that one? If yes we might instead just invoke the JBang commands)

this will be done in VS Code Language Support extension: https://issues.redhat.com/browse/FUSETOOLS2-2173


Skeleton of a solver that supports state variables

Given a collection of intents, generate a solution that satisfies all of them. This requires building a wrapper around the constraint solver that can handle state variables, b256 variables, etc. The first iteration of this could be quite simple.

There's another solver issue. Closing for now.


Revert "Update dependency jwilder/nginx-proxy to v1"

Reverts xwp/xwp-vip-site-template#149
Fixes #160

Closing in favour of #162


Reintroduce build changes lost in merge and format readme

Cleans up package.json
Formats README
Corrects Spelling

🥳

looks great!


Stream aggregation results

Would it be possible to add an .each() method to aggregation results similar to that found on find. If we could stream each result that would help a lot with out of memory problems on big result sets.
Looking at the native mongodb driver, it seems as though data can be streamed from the cursor created by var cursor = collection.aggregate() via cursor.on('data'). I'm not really familiar with the internals of eaither driver, but maybe that could be exposed via .each().

+1

This would be a really good idea

Does anybody know if you can still get the native collection in Monk 2 like you could in Monk 1. In Monk 1 you could do:
db.get('collectionName').col
to get the native mongodb collection and use aggreagte method on that which I assume could be streamed:
http://mongodb.github.io/node-mongodb-native/2.0/tutorials/streams/


enable zooming further than native zoom

enable zooming using the maxZoom layer option

:+1: thanks for the contribution!