cmd/compile: add unrolling stage for automatic loop unrolling

Loop unrolling is a tecnique intended to speed up loops. It's supported by other mature compilers such as Clang.
This proposal consists of possible implementation ideas: general loop unrolling rules and how they can apply to Golang compiler, and some simple benchmarks reflecting this optimization performance on simple constant range loops.
It's easy to begin with a simple constant range for loops such as:
for i := 0 ; i < 1000 ; i++ {
	a[i] += 2;
}

And then add more features inside unroll package which will represent a loop unrolling optimization pass.
Unroll package implementation ideas
The following approach could already be easily integrated inside Golang optimization pipeline right after the inlining stage.
// Inlining
base.Timer.Start("fe", "inlining")
if base.Flag.LowerL != 0 {
	inline.InlinePackage()
}
noder.MakeWrappers(typecheck.Target) // must happen after inlining

// Unrolling
unroll.UnrollPackage()

UnrollPackage() will traverse each function to find for loops and check if it's appropriate for unrolling, then perform unrolling by calling Unroll() function if so.
// Unroll function takes 2 parameters:
// forstmt - an appropriate for loop,
// unroll - an unrolling factor (the amount of times the body will be repeated).
// It unrolls it in-place and returns a tail which should be placed right after the loop.
// The tail is generated if for range isn't divisible by the unrolling factor.
func Unroll(forstmt *ir.ForStmt, unroll uint32) (tail ir.Nodes) {
	....
}

It's important to calculate the unrolling factor correctly. If it's too big we can run into a problem when a for loop body exceeds the instruction cache. A possible idea of picking the factor is by reusing the part of the inlining stage, that is, hairyVisitor since there was already a lot of work done for choosing the weights of the nodes.
if A = maximum weight of the for loop which is short enough to be kept in cache, and B = the weight of a for loop body calculated by the extended version of hairyVisitor, then  the unrolling factor = A / B. If it's greater than 1 then loop unrolling is beneficial for that loop.
Unroll function implementation ideas
When unroll variable is picked a for loop can be unrolled in 4 steps. Once again, we're dealing with constant values here:

Align condition so the loop does not go out of the boundaries (i < 1000 -> i < 1000 / unroll * unroll)

if forstmt.Cond != nil {
	cmp := forstmt.Cond.(*ir.BinaryExpr)
	val := ir.ConstValue(cmp.Y).(int64)
	alignedval = val / int64(unroll) * int64(unroll)
	newval := ir.NewConstExpr(constant.MakeInt64(alignedval), cmp.Y)
	cmp.Y = newval
}

Modify post expression so the induction variable goes unroll steps at a time (i++ -> i += unroll)

// Unroll post
if forstmt.Post != nil {
	post := forstmt.Post.(*ir.AssignOpStmt)
	inc := ir.ConstValue(post.Y).(int64)
	unrolledinc := inc * int64(unroll)
	newinc := ir.NewConstExpr(constant.MakeInt64(unrolledinc), post.Y)
	post.Y = newinc
}

Modify body.

This step is a little bit more complex since to only copy the body isn't enough. Suppose unroll is 4 and the body of the loop is:
for i := 0 ; i < 100 ; i++ {
	sum += i
}

Just coping the body 4 times isn't enough since it gives us:
for i := 0 ; i < 100 / 4 * 4 ; i+=4 {
	sum += i
	sum += i
	sum += i
	sum += i
}

The correct version is:
for i := 0 ; i < 100 / 4 * 4 ; i+=4 {
	sum += i
	sum += i + 1
	sum += i + 2
	sum += i + 3
}

Firstly, we must find all induction variables and then after coping the body, apply shifting operation each time.
Keeping that in mind, body unrolling can be implemented in the following way:
// Firstly, copy original version of a body
bodycopy := ir.DeepCopyList(base.Pos, forstmt.Body)

// Copy the body unroll - 1 times, apply shifting and insert it in the body
for unr := uint64(1); unr < unroll; unr++ {
	appendbody := ir.DeepCopyList(base.Pos, bodycopy)

	// i is a loop induction variable
	// Note: there could be multiple induction variables for a loop.
	shiftNodes(appendbody, i, uint64(inc)*unr)

	forstmt.Body.Append(appendbody...)
}

// shiftNodes function takes 3 parameters:
// nodes - a list of nodes,
// orig - an original node that's going to be shifted,
// shift - a shift constant.
// It generates a new node which represents an expression orig + shift and
// changes every orig reference to the new expression.
func shiftNodes(nodes ir.Nodes, orig ir.Node, shift uint64) {
	idx := ir.NewConstExpr(constant.MakeUint64(shift), orig)
	idx.SetType(types.Types[types.TUINTPTR])
	idx.SetTypecheck(1)

	shifted := ir.NewBinaryExpr(base.Pos, ir.OADD, orig, idx)
	shifted.SetType(orig.Type())
	shifted.SetTypecheck(orig.Typecheck())

	var edit func(ir.Node) ir.Node
	edit = func(x ir.Node) ir.Node {
		ir.EditChildren(x, edit)
		if x == orig {
			return shifted
		}
		return x
	}

	for _, node := range nodes {
		edit(node)
	}
}

Suppose we have a loop:
for i := 0 ; i < 101 ; i++ {
	sum += i
}

And the unroll is 3. Than it should be unrolled to this:
for i := 0 ; i < 101 / 3 * 3 ; i+=3 {
	sum += i
	sum += i + 1
	sum += i + 2
}

Since 101 isn't divisible by 3 there are 101 % 3 operations that hasn't been performed yet:
sum += 99
sum += 100

This should also be generated and placed after the for loop.
for idx := val / unroll * unroll; idx < val; idx++ {
	appendtail := ir.DeepCopyList(base.Pos, bodycopy)
	placeConst(appendtail, i, idx)
	tail.Append(appendtail...)
}

// placeConst function takes 3 parameters:
// nodes - a list of nodes,
// orig - an original node that's going to be replaced by a constant,
// con - a constant itself.
// It generates a new constant and changes every orig reference to the new contant node.
func placeConst(nodes ir.Nodes, orig ir.Node, con int64) {
	i := ir.NewConstExpr(constant.MakeInt64(con), orig)
	i.SetType(types.Types[types.TINT64])
	i.SetTypecheck(1)

	var edit func(ir.Node) ir.Node
	edit = func(x ir.Node) ir.Node {
		ir.EditChildren(x, edit)
		if x == orig {
			return i
		}
		return x
	}

	for _, node := range nodes {
		edit(node)
	}
}

Results
The following lines of code:
var a [100]int

for i := 0 ; i < 100 - 1; i++ {
	a[i] += 2
}

currently are compiled to:
 1053eb3:	31 c0                	xor    eax,eax
 1053eb5:	eb 09                	jmp    1053ec0 <_main.main+0x60>
 1053eb7:	48 83 44 c4 18 02    	add    QWORD PTR [rsp+rax*8+0x18],0x2
 1053ebd:	48 ff c0             	inc    rax
 1053ec0:	48 83 f8 63          	cmp    rax,0x63
 1053ec4:	7c f1                	jl     1053eb7 <_main.main+0x57>

After applying a very basic version of loop unrolling with the above approach those are compiled to:
 1053eb3:	31 c0                	xor    eax,eax
 1053eb5:	eb 1c                	jmp    1053ed3 <_main.main+0x73>
 1053eb7:	48 83 44 c4 18 02    	add    QWORD PTR [rsp+rax*8+0x18],0x2
 1053ebd:	48 83 44 c4 20 02    	add    QWORD PTR [rsp+rax*8+0x20],0x2
 1053ec3:	48 83 44 c4 28 02    	add    QWORD PTR [rsp+rax*8+0x28],0x2
 1053ec9:	48 83 44 c4 30 02    	add    QWORD PTR [rsp+rax*8+0x30],0x2
 1053ecf:	48 83 c0 04          	add    rax,0x4
 1053ed3:	48 83 f8 60          	cmp    rax,0x60
 1053ed7:	7c de                	jl     1053eb7 <_main.main+0x57>
 1053ed9:	48 83 84 24 18 03 00 	add    QWORD PTR [rsp+0x318],0x2
 1053ee0:	00 02
 1053ee2:	48 83 84 24 20 03 00 	add    QWORD PTR [rsp+0x320],0x2
 1053ee9:	00 02
 1053eeb:	48 83 84 24 28 03 00 	add    QWORD PTR [rsp+0x328],0x2

Body is repeated 4 times with the shifted indices. Tail is placed after the loop that handles 96th, 97th and 98th indices.
Benchmarks
func BenchmarkUnrolling(b *testing.B) {
	var a [100]int

	for j := 0 ; j < b.N ; j++ {
		for i := 0 ; i < 100 - 1; i++ {
			a[i] += 2
		}
	}
}

name          old time/op  new time/op  delta
Unrolling-12  51.7ns ± 0%  23.9ns ± 3%  -53.71%  (p=0.016 n=4+5)

Related: #49997

This is not an API change, so taking this out of the proposal process.
In my opinion the most important consideration is compile time.  The Go compiler has a much greater emphasis on compile time than a compiler like clang.
CC @randall77 @golang/runtime

Another consideration is binary size. We don't want to just unroll everything, as that can lead to binary bloat.
I think there's definitely something we can proceed with here. The way I see it there are 2 parts:

The mechanism of loop unrolling
The heuristics for loop unrolling

It would be good to start with figuring out how to implement 1, and have a very conservative heuristic for 2. Once we have that working, we can investigate improving the heuristic to encompass more cases. Whether that is using profile-directed feedback, or analysis of what kind of loop bodies would benefit the most, or whatever.

Maybe we should do the loop invariant optimization first?

@erifan is mentioning #15808, I think. I agree that fixing that issue would also help, but I don't think there is any fundamental need to order the two. Other than, perhaps, #15808 is easier and the heuristics are probably a lot easier to figure out.

@erifan is mentioning #15808, I think. I agree that fixing that issue would also help, but I don't think there is any fundamental need to order the two. Other than, perhaps, #15808 is easier and the heuristics are probably a lot easier to figure out.

Yeah, I agree that there is no necessary connection between the two, I mean if loop unrolling is based on loop invariant hoisting , will this optimization be a little easier to implement?
In addition, perhaps not very relevant to this topic, do we need to consider loop-related optimizations from a higher dimension. Because maybe in the future we will also consider auto-vectorization, I hope we have a general consideration.

cc @dr2chase who did some experiment with loop unrolling in SSA.

I've played with both loop unrolling and loop invariant hoisting, and when the Go world was very very Intel-oriented neither of these reliably made sense (and their code was unpleasant).  I recently attempted to revive the invariant-hoisting CL and could not easily get it to work (and I am not likely to look at this again before March 7, i.e., the likely go1.18 release date).
But in general, the wins were less than awesome, binary sizes go up a bit with loop unrolling, and for a given binary-size/compile-time budget it was not at all clear that this was the best way to increase performance.  It also creates problems for debugging.

I've played with both loop unrolling and loop invariant hoisting

I'm interested in invariant loop hoisting. Where is the CL you revived? I suspect it would help more on Power or maybe even ARM64.

Here's the hoisting CL, newly revived: https://go-review.googlesource.com/c/go/+/37338.
It lacks a test, but I did hand-verify it.
Unrolling, I didn't do as good a job on that CL (it merely boilerplated the body, didn't handle iterator arithmetic cleverly).  Unrolling is tricky because updating SSA in place is a pain (I can try to find that one, nonetheless).

Note that this CL changes arm64 code generation for one of the codegen tests (so it fails), which is something I'll need to look at.  I'm also doing a quick round of benchmarking on amd64 and a low-end arm64.

But in general, the wins were less than awesome, binary sizes go up a bit with loop unrolling, and for a given binary-size/compile-time budget it was not at all clear that this was the best way to increase performance. It also creates problems for debugging.

I think there are still valid use cases for this feature, especially for more performance-sensitive Go applications. At the very least, we can provide an option for Go users to enable better performance at the cost of larger binary size, longer compile time, and harder debugging as mentioned. By providing this option to Go developers, they can select the appropriate optimization levels depending on the specific tradeoffs of their applications and whether they have performance-critical code or not.
For example, we could add this feature behind an opt-in experimental flag. This approach is adopted by compilers of other programming languages such as:

GCC and Clang: -O3, -Os, or -Oz.
rustc, the Rust compiler: 3, "s", or "z" (some discussion here).
swiftc, the Swift compiler: -O or -Osize.

Now that we have PGO, maybe we can add this just to the most "hot paths"?
The trade-off of binary size\ performance speed up heuristic is already decided there, so we can just use that.

Although not strictly bound to loop invariant, as @erifan and @randall77 said, the performance would have better gains, as more loops would be candidates to the unroll since their body size would decrease. In the current state of discussion on whether to implement this at all, it might help enlighten the situation.
It might unroll loops that were never intended to fully run, where there are "break" or "return" in it. (this is also a limitation of GCC https://godbolt.org/z/qE9s6s3cs )
One of the main benefits of unrolling is instruction cache-hits so in places where there is a function call, the benefit would be less significant.
With big loops, the reminder might be huge, causing an almost x2 binary size than what is needed.
Note that GCC for the least does the reminder calculation before the loop not after, https://godbolt.org/z/GnrjdMKT7 , not sure if that has consequences.

All in all, a more sophisticated manner of unrolling would yield a better byte\time ratio IMHO
The most conservative approach is a good start - completely unrolling the function with no loop, for loops with

I agree that PGO would make loop unrolling far more tenable, so I've added it to the PGO umbrella issue (#62463).
Note however that loop unrolling is not just a balance with binary size/i-cache pressure. On modern CPUs, simply unrolling a loop is often a pessimization, for example if it contains conditional branches then unrolling it will increase pressure on the branch predictor (Intel Optimization Manual, "Loop Unrolling"). It's really a lot like inlining: the main benefit is generally not the unrolling itself, but the follow-on optimizations it enables. That said, that just makes PGO an even better fit for this, since it would allow us to focus where we spend compile time analyzing whether unrolling a loop is even worthwhile.


UCMA 3.0 Runtime download

Why is there no UCMA 3.0 Runtime download available from Microsoft?
The article describes how to use SEFAUtil with SfB 2015 and it's part of the ResKit for SfB 2015 but it only works with UCMA 3.0???
At least give us the possibility to download UCMA 3.0 Runtime or much better would be to update the SEFAUtil to UCMA 5.0.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 5e97f81b-dfc0-6b20-fb06-4addeface54b
Version Independent ID: 830ab805-b0a2-41a4-42a6-ee248ae1bacb
Content: Bereitstellen des SEFAUtil-Tools in Skype for Business 2015
Content Source: Skype/SfbServer/deploy/deploy-enterprise-voice/deploy-the-sefautil-tool.md
Service: unspecified
GitHub Login: @kenwith
Microsoft Alias: kenwith

@heebtob - thank you for the feedback on this. I am looking into this now and will update this issue as I find more information. Thanks for taking the time to make the docs better!

@heebtob - I was in contact with a senior escalations engineer internally and found at that you are exactly right that SEFAUtil is compiled against UCMA 3.0. We are filing a bug to request SEFAUtil to be compiled against UCMA 5.
Everyone agrees with you that we should keep the 3.0 runtime available for download since other customer's applications might be relying on it. The SDK would install the runtime. Here is the link: https://www.microsoft.com/en-us/download/details.aspx?id=10566
I am not a subject matter expert in this area so submitted the following Pull Request to improve the document. I added a link to the download. Please let me know what you think. Also, these are open source docs now and if there is a better way to improve it would be awesome if you were open to submit a Pull Request too but if you would rather not I can edit my PR too.
My PR is: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/pull/177

Update - It was noticed that UCMA 5.0 Runtime should be used when running SEFAUtil shipping with Skype for Business Server 2015. I am updating the Pull Request now with this info.

PR updated - please check. I am also checking internally to confirm this is correct info: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/pull/177

@kenwith - Thank you for helping me. My use case is to disable call forwardings with a simple web service. The web service calls the SEFAUtil to disable them. It's a special development for a customer.
The problem is that the SEFAUtil doesn't work on my server and I don't know why. It's a Windows Server 2016 with UCMA Runtime 4.0 and 5.0 installed. The server is already part of an application pool with an application endpoint (runs with UCMA 5.0) for another application. So everything related to certifcates etc. already works. I just added a new application endpoint for sefautil and tried to disable a call forward. It doesn't work but the application throws no error message at all. The only hint I had from the article was that I need UCMA 3.0. I couldn't install the SDK because I have no Visual Studio 2010 on the server. It tells me that Visual Studio 2010 is a requirement for the installation.
It's really hard to troubleshoot because the SEFAUtil gives no error message. I hope you're right and I don't need UCMA 3.0. I will do some wireshark sniffing and some sniffing on the SfB server side. Maybe I will find the cause this way.

@heebtob - I think we might need an official support. Do you have a way to open a support ticket? I am going to keep talking to people too that might know but with a support ticket it will go straight to the right person that can help. This is really valuable info you are finding so I will capture when we resolve this and get the article updated. It concerns me that you would have to go to Wireshark for a product that should work so if you can open a support ticket and let me know the reference I will follow up internally too to make sure this is resolved. It is really not a good experience to have to go to the levels you are going to get this to work and I want to get it solved on the product level.

@heebtob Please try running Steps 1, 2, and 3 from the SfB Deployment Wizard on the Trusted Application Computer.  SEFAUtil requires the local configuration store to be present, as well as a certificate.  I believe that is another aspect missing in the docs.

@chtartMSFT thanks for this! I will get this in the doc ASAP.

I updated the doc and am pushing it out.. takes a little time to pull over to german. Thanks for reporting!

Awesome, thanks for reporting.


Add Candle

Website
https://candlelabs.org
ChainId
534

Hi @samisbakedham I have just done this also!


Greater than and Less than??

I can't get > or < to work. As soon as I insert them, that span disappears and all KaTeX spans after it stop working too.
That is, this HTML,

Produces this result:

The second list item works as soon as I remove the > sign.
It the second list item also works fine with \geq instead of >

And of course, "& g t ;" doesn't work in the span at all.
Am I missing something here or is this a bug? I can't imagine no one has caught this before.
What's the right way to use a greater than or less than sign with KaTeX?

n > 2

should definitely work.

If not, can you post a simple jsbin that shows the problem?

It does not work.
I'm not familiar with jsbin. Can you provide more details?

Here's two examples of how to do it:
http://jsbin.com/zebiwodeto/edit?html,output

I'm still not sure what you want me to do. If I put that code on my page it works.
But < s p a n   c l a s s = " k a t e x " > n   & g t ;   2 < / s p a n > does not work on my site, though everything else in KaTeX has been fine.

Well, how are you running katex?

By the way: you can make code formatting by putting backticks around a piece of text instead of putting spaces between every letter.

Looks like we have a local copy of katex.min.js and katex.min.css
Also we have this:
llab.mathDisplaySetup = function () {     var cssFile, jsFile, css, js;     cssFile = llab.paths.css_files.math_katex_css;     jsFile  = llab.paths.math_katex_js;     css = getTag('link', cssFile, 'text/css');     css.rel = "stylesheet";     js = getTag('script', jsFile, 'text/javascript');     $(js).attr({'onload': 'llab.displayMathDivs()'});     document.head.appendChild(css);     document.head.appendChild(js); }
llab.displayMathDivs = function () {     $('.katex, .katex-inline').each(function (idx, elm) {         katex.render(elm.innerHTML, elm, {throwOnError: false});     });     $('.katex-block').each(function (idx, elm) {         katex.render(elm.innerHTML, elm, {             displayMode: true, throwOnError: false         });     }); }

Try changing .innerHTML to .textContent.

That worked!! Thanks!!!

No problem. :)


FORTRAN Version

This is a FORTRAN version of the leap year program

Added "part 2" reasoning

Thanks for being the first pull request on this project. I appreciate the extra effort in adding the reason for each leap year type. I see now that the CONTRIBUTING file may have implied this, although I really just wanted to explain to someone who might not know enough about leap years to understand. I will modify my instructions to be more clear.


Update application-gateway-create-url-route-arm-ps.md

Videopathrule used the wong poolsettings

Hi @ingmar79, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@jimdial Could you please review this proposed update in the public repo from @ingmar79?

#sign-off
It's a good catch, please accept.

@ingmar79 - Thanks!


fix(curriculum): Added Hint for Step 49 of Statistics Calculator

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56938

I have corrected Step 49 of the Statistics Calculator, which now provides a useful hint if the initial value of the reduce function is missing.

Hi there,
Thanks for creating this pull request.
The linked issue has not been triaged yet, and a solution has not been agreed upon. Once the issue is open for contribution, you are welcome to update this pull request to reflect the issue consensus. Until the issue is open for contribution, we will not be able to review your pull request.


feat: integrate warm/cold account concepts in EXTCODEXXX opcodes

Feature Request
As mentioned in the EVM spec:

Access sets have been introduced in the hardfork Berlin. They are kept per transaction (and not per call context). Two of them exist: the touched contracts addresses, and the touched contract storage slots. If an address or slot is present in the set, it is called 'warm', otherwise it is 'cold'. The dynamic cost of some opcodes depends on whether the address or slot is warm or cold.
Addresses: a set of contract addresses that have been touched in the current transaction. It is initialized with the sender and receiver (or the new contract address in case of a creation) of the transaction, as well as all the precompiled contracts. When an opcode accesses an address that is not present in the set, it adds it in it. The relevant opcodes are EXTCODESIZE, EXTCODECOPY, EXTCODEHASH, BALANCE, CALL, CALLCODE, DELEGATECALL, STATICCALL, CREATE, CREATE2 and SELFDESTRUCT.
Slots: a set of contract address and their storage slot keys that have been accessed. It is initialized to empty. When an opcode accesses a slot that is not present in the set, it adds it to it. The relevant opcodes are SLOAD and SSTORE
When a context reverts, the sets are also reverted to the state they had before that context.

For now, Kakarot will treat any account as cold and won't cache in memory "warm" accounts.
To do: make apparent these concepts and hard code the fact that accesses are cold. Gas consumed should be parametrised and therefore gas consumed should be in line with cold accounts.
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)

In kakarot conversation:

Yep! So we also drop support for warm/cold accesses. this task would become simply hardcoding the cold access gas costs into kakarot and documenting in comments that we don't use warm access

@jobez is this already done and I didn't see it?

Yeah, it is hard coded for cold gas access right now.


No Email Notification is sent for a particular email address in registering a user in STORE sign up

Suggested Labels:
Type/Bug
APIM 2.2.0
Affected Product Version:
wso2am-2.1.0-update5
OS, DB, other environment details and versions:
Standalone
DB - H2
Browser - Chrome Version 61.0.3163.100 (Official Build) (64-bit)
JDK - jdk1.8.0_121
Steps to reproduce:
1.Run APIM 2.1.0 update 5
2.Access API Store
3. Go to user Sign up
4. Add a user giving a particular email address
Observation
No email message is sent for the users email address by notifying that he has registered that email address under wso2 API store. In order to validate a particular email address which is given in the signup user needs to get a email for his account.

duplicate of https://github.com/wso2/product-apim/issues/4070. Hence closing


JWT tokens

In AE api decide the jwt and use the expire date inside instead of req expire date. Also, if 401 when getting a new token, send a param to force a cache purge first. And finally, think about adding some sort of process locking to ensure only one process generates a token at any given time.

No longer an issue I think.


compactor DeleteObjects return 405 with s3-compatible seaweedfs

Describe the bug
compactor DeleteObjects failed with return code 405 while meta success, because missing resource bucket in compactor request path
s3 config:
stateStore:
dataDirectory: risingwave/hummock001
s3:
endpoint: mydomain.com
bucket: rw-s3-dev
region: us-east-1
credentials:
secretName: s3-credentials
request will to https://rw-s3-dev.mydomain.com
Error message/log
<IP_ADDRESS> - - [20/Dec/2023:01:35:50 +0000] "POST /?delete&x-id=DeleteObjects HTTP/1.1" 405 0 "-" "aws-sdk-rust/1.0.1 os/linux lang/rust/1.75.0-nightly"
<IP_ADDRESS> - - [20/Dec/2023:01:35:50 +0000] "PUT /risingwave/hummock001/checkpoint/0?x-id=PutObject HTTP/1.1" 200 0 "-" “aws-sdk-rust/1.0.1 os/linux lang/rust/1.75.0-nightly”

To Reproduce
compactor running
Expected behavior
return code 200 with object deleted success
How did you deploy RisingWave?
kubernetes with operator
The version of RisingWave
1.5.0
Additional context
there is other with 405
<IP_ADDRESS> - - [20/Dec/2023:02:30:28 +0000] "PUT /?lifecycle HTTP/1.1" 405 0 "-" "aws-sdk-rust/0.55.3 os/linux lang/rust/1.75.0-nightly"

Hi @dramer-817 , we noticed that you are using seaweedfs as the remote object storage. We support s3-compatible storage, but not every storage is very compatible with s3, so I think this error may lie in seaweedfs. I don’t know if you have other alternative object storage options?

hi @wcy-fdu thank you for your response, i will try with minio later but it nice if seaweedfs supported too.
Additional info, i tried with aws s3api cli and success
aws --profile seaweedfs-rw --endpoint-url https://rw-s3-dev.mydomain.com/ s3api delete-objects --bucket risingwave --delete file://delete-rw.json
{
   "Deleted": [
       {
           "Key": "hummock001/255/1.data"
       }
   ]
}

delete-rw.json:
{
 "Objects": [
   {
     "Key": "hummock001/255/1.data"
   }
 ],
 "Quiet": false
}

nginx log:
<IP_ADDRESS> - - [20/Dec/2023:08:39:29 +0000] "POST /risingwave?delete HTTP/1.1" 200 162 "-" "aws-cli/2.14.5 Python/3.11.6 Linux/6.6.7-1-MANJARO source/x86_64.manjaro.23 prompt/off command/s3api.delete-objects"

there is bucket name in post request path

it seems seaweedfs works with config stateStore use minio
stateStore:
    dataDirectory: hummock
    # Declaration of the MinIO state store backend.
    minio:
      # Endpoint of the MinIO service.
      # endpoint: <IP_ADDRESS>:9000
      endpoint: https://rw-s3-dev.mydomain.com

      # Name of the MinIO bucket.
      bucket: risingwave

      # Credentials to access the MinIO bucket.
      credentials:
        # Name of the Kubernetes secret that stores the credentials.
        secretName: s3-credentials

        # Key of the username ID in the secret.
        usernameKeyRef: username

        # Key of the password key in the secret.
        passwordKeyRef: password

nginx log:
<IP_ADDRESS> - - [21/Dec/2023:07:21:59 +0000] "POST /risingwave/?delete&x-id=DeleteObjects HTTP/1.1" 200 211 "-" "aws-sdk-rust/1.0.1 os/linux lang/rust/1.75.0-nightly"

the objects got deleted, but still ?lifecyle not return 200 with minio or seaweedfs with minio config, maybe it's ok


PHP message: PHP Fatal error: Uncaught ReflectionException: Class log does not exist in

I can't get laravel to run because of the following error. The log is from the nginx error.log.
I get an error 500 in chrome when trying to connect. Phpmyadmin is showing his page correctly.

08:43:53 [error] 7#7: *13 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught ReflectionException: Class log does not exist in /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:734
Stack trace:
#0 /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(734): ReflectionClass->__construct('log')
#1 /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(629): Illuminate\Container\Container->build('log', Array)
#2 /var/www/laravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(697): Illuminate\Container\Container->make('log', Array)
#3 /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(849): Illuminate\Foundation\Application->make('log')
#4 /var/www/laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php(804): Illuminate\Container\Container->resolveClass(Object(ReflectionParameter))

@Shmp does this issue still exist?!

I will try a new installation with fresh containers this week. Will report back asap

@Shmp thanks, also don't forget to rebuild the containers before testing it.

Did a fresh install with laradock, build the contrainers, edited the docker-compose.yml, rebuild the containers again. Everything works 👍


Fixing link contribution

I don't know if this on purpose, but link to CONTRIBUTING.md is broken. Just fix that problem.

As mentioned earlier, PRs should be independent. We have fixed the CONTRIBUTING links in a separate PR. Thank you for the fix 👍


Geolocation and search box to change location

What is the unit ?
I put 10 and was thinking it was kilometers but it was so small like 10m so I tried 10000 and it was so huge, finally my go value was 1500.
Also feature that would be cool is a geolocation button to scan in our areas and a search box to change location around the globe very easily
Btw nice project, i prefer this one than the others

Glad you like it.
The unit is meters.

A search box, or button to go to your geo-location would be nice!


[SPARK-41428][UI] Protobuf serializer for SpeculationStageSummaryWrapper

What changes were proposed in this pull request?
Add Protobuf serializer for SpeculationStageSummaryWrapper
Why are the changes needed?
Support fast and compact serialization/deserialization for SpeculationStageSummaryWrapper over RocksDB.
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UT

@gengliangwang this PR is ready to be reviewed

@techaddict Do you mind if I hold on to the review for one day and wait for the refactor in https://github.com/apache/spark/pull/39148?
cc @LuciferYang

@gengliangwang sounds good 👍🏼

@techaddict FYI https://github.com/apache/spark/pull/39148 is merged. Can you resolve the conflicts?

@techaddict updated the PR

@gengliangwang addressed comments 👍🏼

Thanks, merging to master


Add auto merge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/utool-feedstock#3.


Remove the  from the ChoiceBoard component

At the ChoiceBoard.tsx component there is a  that won't be used for now. Remove the component and the import.

I really would love to work on this !

Just assigned to you, @hannydevelop
Go for it !! 🏃🏻
Can't wait to check your PR.

I made my first PR three hours ago!
How's it?

Just assigned to you, @hannydevelop
Go for it !! 🏃🏻
Can't wait to check your PR.

Hello if my commit is OK can I get another task? I am learning React anyways

Hi @hannydevelop ! Great PR..!
I'm merging this right now. Meanwhile, I have just invited you as part of the team of this project. If you could accept it would be awsome. ☀

Hi @hannydevelop ! Great PR..!
I'm merging this right now. Meanwhile, I have just invited you as part of the team of this project. If you could accept it would be awsome. ☀

I would accept the request once I get 2 step authentication setup!
Thank you so much I can't wait to be part of the team.
The next task can be a React task, am learning React already


generate-event sns adds in " html entities

On aws-cli version 0.6.2
Expected output of sam local generate-event sns notification --message "$(cat event.json)"
{
    "Records": [
        {
            "EventVersion": "1.0",
            "EventSource": "aws:sns",
            "EventSubscriptionArn": "arn:aws:sns:EXAMPLE",
            "Sns": {
                "MessageId": "95df01b4-ee98-5cb9-9903-4c221d41eb5e",
                "Signature": "EXAMPLE",
                "Type": "Notification",
                "TopicArn": "arn:aws:sns:us-east-1:111122223333:ExampleTopic",
                "MessageAttributes": {
                    "Test": {
                        "Type": "String",
                        "Value": "TestString"
                    },
                    "TestBinary": {
                        "Type": "Binary",
                        "Value": "TestBinary"
                    }
                },
                "SignatureVersion": "1",
                "Timestamp": "1970-01-01T00:00:00.000Z",
                "SigningCertUrl": "EXAMPLE",
                "Message": "{\n  \"foo\": \"bar\"\n}",
                "UnsubscribeUrl": "EXAMPLE",
                "Subject": "example subject"
            }
        }
    ]
}

Actual output:
{
  "Records": [
    {
      "EventVersion": "1.0",
      "EventSubscriptionArn": "arn:aws:sns:us-east-1::ExampleTopic",
      "EventSource": "aws:sns",
      "Sns": {
        "SignatureVersion": "1",
        "Timestamp": "1970-01-01T00:00:00.000Z",
        "Signature": "EXAMPLE",
        "SigningCertUrl": "EXAMPLE",
        "MessageId": "95df01b4-ee98-5cb9-9903-4c221d41eb5e",
        "Message": "{
  "foo": "bar"
}",
        "MessageAttributes": {
          "Test": {
            "Type": "String",
            "Value": "TestString"
          },
          "TestBinary": {
            "Type": "Binary",
            "Value": "TestBinary"
          }
        },
        "Type": "Notification",
        "UnsubscribeUrl": "EXAMPLE",
        "TopicArn": "arn:aws:sns:us-east-1:123456789012:ExampleTopic",
        "Subject": "example subject"
      }
    }
  ]
}

My event.json file:
{
  "foo": "bar"
}

On aws-cli version 0.3.0 it works correctly. However, the way you have to invoke generate-event is different between versions. The way to call generate-event on v0.3.0 with the correctly formatted response is this way: sam local generate-event sns --message "$(cat event.json)" which outputs the first json blob.
For now my workaround is to use the older version; but when will this be fixed going forward so:
a) newer versions of aws-cli has backwards compatibility
b) json files are parsed correctly
c) you can pass in a json file directly into the generate-event command without the cat command?

It looks like https://github.com/awslabs/aws-sam-cli/commit/dcd65f4442233d054c5ee8371e0c5e5e2f7ed7b4 is the commit that introduced this issue. With this commit, sam uses a templating engine. The solution would be to make a PR and change {{message}} to {{{message}}} in this file https://github.com/awslabs/aws-sam-cli/blob/develop/samcli/commands/local/lib/generated_sample_events/events/sns/Sns.json#L12 (and ideally doing the same for all events).
You can look at https://github.com/noahmorrison/chevron/blob/master/tests/test.mustache for more details about how the templating engine renders variables.

@ste00martin Thanks for the report. @jackdbernier is correct. {{message}} will be html echoed by default and that using {{{message}}} instead is the correct behavior we want across all events. I have a patch for this in my fork. Hoping to get this out for a PR after I make a second pass through all the events.
More details on how mustache behaves in the variable section here

The combo of triple braces and json escaping works.
For instance,
sam local generate-event sns notification --message "$(jq '.|tojson' event.json)"

will output
{
  "Records": [
    {
      "EventSource": "aws:sns",
      "EventVersion": "1.0",
      "EventSubscriptionArn": "arn:aws:sns:us-east-1::ExampleTopic",
      "Sns": {
        "Type": "Notification",
        "MessageId": "95df01b4-ee98-5cb9-9903-4c221d41eb5e",
        "TopicArn": "arn:aws:sns:us-east-1:123456789012:ExampleTopic",
        "Subject": "example subject",
        "Message": ""{\"name\":\"Jacques\"}"",
        "Timestamp": "1970-01-01T00:00:00.000Z",
        "SignatureVersion": "1",
        "Signature": "EXAMPLE",
        "SigningCertUrl": "EXAMPLE",
        "UnsubscribeUrl": "EXAMPLE",
        "MessageAttributes": {
          "Test": {
            "Type": "String",
            "Value": "TestString"
          },
          "TestBinary": {
            "Type": "Binary",
            "Value": "TestBinary"
          }
        }
      }
    }
  ]
}

if you omit the jq part you will end up with something like "Message": "{"name": "Jacques"}", and that is not valid. It used to work before and I think it is because it was using https://docs.python.org/3/library/json.html to generate the event. So --message "$(cat event.json)" needs to become something like --message "$(jq '.|tojson' event.json)". This is not as straightforward as it used to be but with 1 or 2 examples. It will definitely work out just fine.
Thanks for jumping on that.

This was released in v0.9.0
Closing


Address pytest warnings

This should just about do it for cleaning up the pytest output.
Commits are atomic and probably best left un-squashed for git blame/history purposes.

Codecov Report

Merging #3625 (a5ef13b) into master (ef1cb2e) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3625      +/-   ##
==========================================
- Coverage   94.38%   94.36%   -0.03%
==========================================
  Files         420      420
  Lines       46070    46068       -2
==========================================
- Hits        43482    43470      -12
- Misses       2588     2598      +10

Impacted Files
Coverage Δ

moto/awslambda/models.py
92.22% <ø> (-0.03%)
:arrow_down:

moto/batch/models.py
82.44% <ø> (-1.51%)
:arrow_down:

moto/ec2/utils.py
95.25% <0.00%> (-0.30%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #3625 (a5ef13b) into master (ef1cb2e) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3625      +/-   ##
==========================================
- Coverage   94.38%   94.36%   -0.03%
==========================================
  Files         420      420
  Lines       46070    46068       -2
==========================================
- Hits        43482    43470      -12
- Misses       2588     2598      +10

Impacted Files
Coverage Δ

moto/awslambda/models.py
92.22% <ø> (-0.03%)
:arrow_down:

moto/batch/models.py
82.44% <ø> (-1.51%)
:arrow_down:

moto/ec2/utils.py
95.25% <0.00%> (-0.30%)
:arrow_down:

Continue to review full report at Codecov.

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

I'll rebase and reopen this when the build is fixed.

I'll rebase and reopen this when the build is fixed.


Feature/rst 1264 session expired

I think this was merged to master too.

I think this was merged to master too.


calling Files.exe from code not working in version 2.1.15

Description
I recently installed version 2.1.13, and updated code to use files.exe to open folders (Windows Explorer has problems with OneDrive).  It was working great, but after the update to 2.1.15, it cannot find Microsoft.Net dlls: mrt100_app.dll, SharedLibrary.dll and VCRUTNTIME140_APP.dll.  Files works when I click the windows icon, and used to work when I clicked files.exe, but not after the update
Steps To Reproduce
click on files.exe in WindowsApps
Expected behavior
I expect the app to open
Files Version
2.1.15
Windows Version
Windows 11 21H2 22000.527
Relevant Assets/Logs
debug.log
debug_fulltrust.log

@wrdoss is this still an issue after resetting the app?

I tried reinstalling the program, but that didn't work - I even tried
adding the directories that contain the missing dlls into the system
environment path.
Is there anything else I can try?
Thanks!
Bill
On Sat, Feb 26, 2022 at 7:40 PM Yair Aichenbaum @.***>
wrote:

@wrdoss https://github.com/wrdoss is this still an issue after
resetting the app?
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/8507#issuecomment-1052921760,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX6FZIRF2YSU5CWFBRKMNWLU5F6IVANCNFSM5PKOI6IA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Bill

Have you tried making a shortcut to files and link that. you can drag it from the start menu to desktop to make it.

I tried dragging the Files icon from the start menu, but Windows won't let
me drop it anywhere.  I also tried repairing, resetting and reinstalling
the app, with no luck.
In version 13, I was able to simply call files.exe to open Files.  Is there
another step that I should be taking?  I'm in the Beta Windows 11 program,
so could that cause a problem?
BTW, thanks for taking the time to help!
On Sun, Feb 27, 2022 at 4:52 PM Josh-65 @.***> wrote:

Have you tried making a shortcut to files and link that. you can drag it
from the start menu to desktop to make it.
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/8507#issuecomment-1053709611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX6FZIQY4CPDKUDVM7FK4D3U5KTJDANCNFSM5PKOI6IA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Bill

Yes, The app started working perfectly a few builds ago. I'm really
impressed with it - thank you!
On Mon, May 9, 2022, 9:45 AM Yair Aichenbaum @.***>
wrote:

@wrdoss https://github.com/wrdoss can you see if this issue is fixed
with the preview version? https://files.community/download/preview
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/8507#issuecomment-1121198725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX6FZIXSOU45QYPAAM42A3LVJEQHVANCNFSM5PKOI6IA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for your feedback


[PRP-334] Add CORS policy to doc upload s3 bucket

Ticket
https://wicmtdp.atlassian.net/browse/PRP-334
Changes

What was added, updated, or removed in this PR.

Add CORS policy to doc upload s3 bucket

Context for reviewers

Testing instructions, background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers. Explain how the changes were verified.

Because we are re-architecting doc upload to upload documents on the client-side in https://wicmtdp.atlassian.net/browse/PRP-332, we need to update our s3 bucket CORS policy to allow the participant site to PUT files into the S3 bucket
Testing

Screenshots, GIF demos, code examples or output to help show the changes working as expected. ProTip: you can drag and drop or paste images into this textbox.

This terraform change has been applied to the dev environment and the WIP for #89 has also been deployed to the dev environment. A successful upload looks like this:

Test by:

Walking through the PRP until you get to upload in the dev environment
Upload a file
The file preview should work
[Bonus] Check that the file has been uploaded to the dev s3 bucket

Trying to upload a document yields this in the dev environment, will attempt again

@rocketnova I enabled the HTTPS mode in my browser (Chrome) and it didn't make a difference

@rocketnova I enabled the HTTPS mode in my browser (Chrome and Safari) and it didn't make a difference

@aplybeah This was a good catch. Sasha and I did a bunch more work to identify this issue and address it in #93


[en] fix links for blog/_posts/2018-05-29-announcing-kustomize

from #42634
Fixed some oudated links in blog post: Introducing kustomize; Template-free Configuration Customization for Kubernetes
Page updated: content/en/blog/_posts/2018-05-29-announcing-kustomize.md

The same changes will be applied to the Korean translation of this page, that I am translating right now.

Please rebase against main; see https://lwkd.info/2023/20230606#developer-news for more context.

I rebased it and Netlify build issue was fixed.

/lgtm
/approve


Release v0.12.0b1

Release v0.12.0b1
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[x] New Release

Additional requirements

[ ] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct.

[x] I agree to follow this project's Code of Conduct

This release is a breaking change and requires FT to use  dev version of CLI and Worker.
See the FT test triggered here: https://github.com/repository-service-tuf/repository-service-tuf-api/actions/runs/8116790828

@kairoaraujo I cannot force merge as the ft tests are required and I don't have permission to override that:


Datepicker: Popout day of month width squishes day view in firefox

If you have a limited column size your day view for your popout date picker will be squished in firefox. This is not an issue with chrome as it keeps its static size. Resize the screen to see the difference if necessary.
http://plnkr.co/edit/kV8ICxL8Jiwmttzyt13G?p=preview

Perhaps modifying the templates for the day, month, and year components with an appropriate min-width would work to fix this - feel free to file a PR for this.

@wesleycho That worked. I will try to file a pr soon


error creating hosts file on CentOS

OK, we'll only exclude domains in the whitelist.
Traceback (most recent call last):
  File "updateHostsFile.py", line 468, in <module>
    main()
  File "updateHostsFile.py", line 126, in main
    updateReadme(numberOfRules)
  File "updateHostsFile.py", line 366, in updateReadme
    out.write(line.replace('@NUM_ENTRIES@', "{:,}".format(numberOfRules)))
ValueError: zero length field name in format

CentOS 6.7
Python 2.6.6

fixed by installing python2.7
https://www.digitalocean.com/community/tutorials/how-to-set-up-python-2-7-6-and-3-3-3-on-centos-6-4


setuser not setting $HOME

Gday, I'm having a problem getting setuser to work as advertised:
root@ccdcb3a62797:/# setuser $USERNAME echo $USERNAME
consul
root@ccdcb3a62797:/# setuser $USERNAME echo $USER

root@ccdcb3a62797:/# setuser $USERNAME echo $HOME
/root
root@ccdcb3a62797:/# setuser $USERNAME whoami
consul
root@ccdcb3a62797:/# setuser $USERNAME env
HOSTNAME=ccdcb3a62797
CONSUL_VERSION=0.6.0
LS_COLORS=
USERNAME=consul
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
DL_LOCATION=/tmp/consul.zip
SHLVL=1
HOME=/home/consul
LESSOPEN=| /usr/bin/lesspipe %s
LESSCLOSE=/usr/bin/lesspipe %s %s
_=/sbin/setuser
USER=consul
UID=999

Am I doing something incorrect here? Seems my runit script is interpolating $HOME as either /root or the empty string, so I'm getting failures.

The echo arguments are evaluated as the current shell user, try
setuser haproxy sh -c 'echo $HOME'


OTG RT-1.3: BGP Route Propagation (Add WatchAll)

resolves #1488
BGP Route Propagation test has GetAll which retrieves learnt prefixes. GetAll fails sometimes when BGP is taking sometime to exchange the routes.
Added WatchAll with timer to check if routes are learnt.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1191

Relevant Lines:
2135

💛  - Coveralls

/gcbrun

/gcbrun


Increase coverage for events

Added tests for the endpoint for retrieving all events.
Depends on previous changes from #26, most of the changes for this PR are in events/test_routes.py.

This looks good, but encouraging you not to build test components you aren't using yet.
There's a term you may see referring to this: YAGNI


Fix #2078 by removing the NavigateUri's from the hyperlinks

Summary of the Pull Request
For some reason the NavigateUri property on the Hyperlinks in the about dialog don't work. This is a workaround for that bug. Instead of using NavigateUri, I'm just using a Click handler to do the same thing.

PR Checklist

[x] Closes #2078
[x] CLA signed. If not, go over here and sign the CLA
[N/A] Tests added/passed

@msftbot wait 1 hour before merging this pr

@msftbot don't merge this pr

@msftbot please don't merge this PR until july 1st, 2030

@msftbot forget everything I've told you

This is straight up the wrong fix. Looks like sometimes the dialog won't auto-crash the app. Sometimes it will. I'll experiment more.


Enable hash-arg feature in moka-cht

Utilize moka-cht's hash-arg feature to avoid calculating the same hash twice for a key at both Moka cache and cht sides.

I will close this for now. I will tackle to this again once I am done with other high priority items.


Fix rejectWithResponse deprecation until versions

When deprecating the rejectWithResponse for the Devise and OAuth2PasswordGrant authenticators, we put the wrong until version in the deprecation - that version should be 3.0.0 of course, not 2.0.0 which is the version the deprecations were introduced with.

@marcoow we should have updated all deprecation notices when releasing 2.0 😳https://github.com/simplabs/ember-simple-auth/blob/ad52181f2995c53bddbc217776a179eadd3e40a0/addon/authenticators/devise.js#L87 for instance.

@marcoow we should have updated all deprecation notices when releasing 2.0 😳

Ouch, you're right of course 🤦♂ I fixed it now.


Process config attributes / options in the order defined in the config schema when using "pack config" CLI command

Right now attributes are not processed / displayed in the order defined in the config schema when using st2 pack config command. This could be a bit confusing to the user.
This ties into the age old "preserve ordering when reading and writing out YAML files" issue.
This is not a big blocker for now, but something we should fix in the future to provide a better user experience.

I'm annoyed by this problem. And I want to solve it.
Would you please assign this issue to me?

@userlocalhost you are more than welcome to take a stab at this issue! Thank you for volunteering :)

Thank you for your prompt reply.
I got it. I'll make a PR after finding the way to solve it.

If the config data that st2api received can store to the datastore, and load it in order. This problem can be resolved.
There is a PR to let mongoengine to store object data (e.g. the fields which are defined in 'st2common/model/db/*') to the datastore in order.
If this feature is merged, this problem could be solved with small changes of st2.
So please wait until that PR is settled.


[GSSOC'23]Adding glow effect

Adding glow on hover on these icons

hey, I wanted to contribute to this issue under GSsoc'23, can you please assign this issue to me.

Please assign this task to me , i can make this work.

Can i be assigned this issue under GSSOC'23?


Fix mybinder from having conflicting dependencies

Dockerfile currently uses  jupyter/minimal-notebook:c54800018c2c to build the extension on top of. This image is over a year old, and causes dependency conflicts.
This should be updated to a later or latest minimal-notebook image in order to have an acceptable jupyterlab version.
Conflicting Dependencies:
JupyterLab              Extension            Package
>=0.15.2-0 <0.16.0-0    >=0.19.1-0 <0.20.0-0 @jupyterlab/application
>=0.15.2-0 <0.16.0-0    >=0.19.1-0 <0.20.0-0 @jupyterlab/apputils
>=0.15.2-0 <0.16.0-0    >=0.19.1-0 <0.20.0-0 @jupyterlab/console
>=1.0.4-0 <2.0.0-0      >=2.1.4-0 <3.0.0-0   @jupyterlab/coreutils
>=0.15.2-0 <0.16.0-0    >=0.19.1-0 <0.20.0-0 @jupyterlab/docmanager
>=0.15.2-0 <0.16.0-0    >=0.19.3-0 <0.20.0-0 @jupyterlab/filebrowser
>=0.15.2-0 <0.16.0-0    >=0.19.2-0 <0.20.0-0 @jupyterlab/notebook
>=0.15.2-0 <0.16.0-0    >=0.19.1-0 <0.20.0-0 @jupyterlab/rendermime

Acceptance Criteria:

jupyterlab_voyager mybinder build works properly

Sounds good to me!

Fixed by https://github.com/altair-viz/jupyterlab_voyager/pull/67


Fixes to Rust CandidateBlock, PyScheduler, TransactionCommitCache

These fixes were found in integrating the Rust BlockPublisher with the already committed Rust and Python code. They are necessary for the Rust BlockPublisher PR.

@aludvik I am concerned with your statement needs to be cleaned up or have summaries added. Looking through git log from master there are regularly commit messages without a body and regularly without a why.

@boydjohnson that is fair. I am definitely guilty of leaving them off at times and have been called out for it. I think the goal should be to always include a commit message that will help reviewers understand why you are doing something and I have been trying to let people know in general when I find that missing.
As an example, consider "Add check for None python state_hash in BatchResult". Looking at just that commit and the summary, I would have no context to understand why this is a thing that should be done or if it is correct or not. Another sentence below the summary stating "Python can also pass a None object instead of a String" makes it easier to understand why that was added later on.

I am opening this PR again.


OAK-D SR , Couldn't access depth information while running depthai_demo.py

While running demo code - depthai_demo.py . we couldn't access the depth information but able to access RGB view from the OAK- D SR camera.
depthai$ python3 depthai_demo.py
Using depthai module from:  /home/delta/.local/lib/python3.8/site-packages/depthai.cpython-38-x86_64-linux-gnu.so
Depthai version installed:  <IP_ADDRESS>
Setting up demo...
Available devices:
[0]<PHONE_NUMBER>CF5D1200 [X_LINK_UNBOOTED]
USB Connection speed: UsbSpeed.SUPER
OV9782 requires 720 or 800 resolution, defaulting to SensorResolution.THE_800_P
Disabling depth...
Disabling depth preview...
Disabling depthRaw preview...
Disabling left preview...
Disabling rectifiedLeft preview...
Disabling right preview...
Disabling rectifiedRight preview...
[1844301001CF5D1200] [1.1] [0.907] [MonoCamera(2)] [error] Camera not detected on socket: 2
[1844301001CF5D1200] [1.1] [0.907] [MonoCamera(0)] [error] Camera not detected on socket: 1

Thanks for the report @Srikiranrao
We are working on an updated Demo / Viewer which will better support newer devices. CC: @zrezke

Hey @Srikiranrao,
You can try the new depthai-viewer which should work with Oak-D SR.
To install: python3 -m pip install depthai-viewer==0.0.7 --extra-index-url https://test.pypi.org/simple
Then run using:
python3 -m depthai_viewer
# OR
depthai-viewer

@zrezke , Thanks. After following steps. I am facing another issue as mentioned below.
this occurs when I select the camera module and try to run it.
Connected cam doesn't have IMU, skipping IMU creation...
Getting cam by socket:  CameraBoardSocket.CAM_B  Cameras:  [CameraConfiguration(fps=30, resolution=<CameraSensorResolution.THE_800_P: 'THE_800_P'>, kind=<CameraSensorType.COLOR: 0>, board_socket=<CameraBoardSocket.CAM_B: 1>, stream_enabled=True, name='Left'), CameraConfiguration(fps=30, resolution=<CameraSensorResolution.THE_800_P: 'THE_800_P'>, kind=<CameraSensorType.COLOR: 0>, board_socket=<CameraBoardSocket.CAM_C: 2>, stream_enabled=True, name='Right')]
[1844301001CF5D1200] [1.2] [3.016] [DetectionNetwork(6)] [warning] Network compiled for 6 shaves, maximum available 10, compiling for 5 shaves likely will yield in better performance
Updating pipeline: successful with message: {'message': 'Pipeline started'}
[1844301001CF5D1200] [1.2] [3.112] [system] [critical] Fatal error. Please report to developers.
Closing device...
Done
Sending message:  {"type": "Error", "data": {"action": "FullReset", "message": "Device disconnected"}}
[2023-06-06T07:08:52Z ERROR re_viewer::depthai::depthai] Error: Device disconnected
Got message:  {'type': 'DeviceProperties', 'data': {'DeviceProperties': {'id': '', 'cameras': [], 'imu': None, 'stereo_pairs': []}}}
Handling action:  Action.SELECT_DEVICE
Selecting device:

@Srikiranrao, Thanks for reporting this issue. Seems like you're experiancing the same issue as here. Maybe it would be best if you subscribe to that issue, to get updates as we try to resolve it...

Any estimates on how long the fix the SDK and depthai_demo.py? It'd make a difference knowing if it was in days, rather than a few weeks - we're pretty heavily blocked on needing to estimate the depth - that's why we bought the device in the first place.

@LinasKo we've fixed it just now, and will be adding to v2.22.0. You may expect updated demo and others tomorrow if all goes according to plan

I had the same issue. Could you guys update the documentation Could you guys update this page to let users know that the SR doesn't work with the demo application? https://docs.luxonis.com/en/latest/pages/tutorials/first_steps/#first-steps-with-depthai so new users know it doesn't work? Seriously unprofessional


PHP VCR not sending request body

When PHP VCR is enabled the request bodies don't get sent on a POST even though the Content-Length header is set and it correctly records the body.

I can't figure out what's wrong from debugging and examining the source code. However I do see that POST is not actually tested in integration tests.

Some questions:
What is the content of the POST body when you send it?
What HTTP library are you using?

Thank you Justin for fixing this in #122. Is your original issue solved?

Yes. Thanks.
On Fri, Jun 19, 2015 at 12:40 PM, Adrian Philipp<EMAIL_ADDRESS>wrote:

Thank you Justin for fixing this in #122
https://github.com/php-vcr/php-vcr/pull/122. Is your original issue
solved?
—
Reply to this email directly or view it on GitHub
https://github.com/php-vcr/php-vcr/issues/120#issuecomment-113584586.


Make undo / redo a tree instead of a stack (vim-like)

All text editors I know have undo and redo stacks. However, having a tree like vim does would be extremely useful for some cases where a stack just isn't enough. Thoughts / opinions?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10575656-make-undo-redo-a-tree-instead-of-a-stack-vim-like?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).

To give an example I often encounter this situation:
I have two ways of solving a problem in my code: I write out the first solution. I test it and now I write the second solution and compare them. I want to decide which solution I go with, I switch back and forth, do some tweaks on Solution 1 and 2 to see which one is more flexible / readable / etc. with a stack, I would have an extremely hard time while with a tree, this would be an easy task.
This feature obviously wouldn't change the normal undo/redo behavior which still acts like a stack. You'd just have an extra command to select between the branches. This would also not break API compatibility.

What's the benefit of having the editor track a full undo-tree vs just managing two git branches via a plugin?

Sorry but I don't quite understand your question. This has nothing to do with git. I'm talking about the cmd-z / ctrl-z and cmd-shift-z / ctrl-y / ctrl-shift-z commands in the text editor and that it would be extremely useful to have a tree over a stack. I have provided a common use case.
Sure you could have two git branches and switch back and forth (if that's your question), but that's way more tedious and I personally don't think an editor's design should depend on what we can already do with other tools, its features should give you a convenient alternative over using those tools. Obviously, nothing can replace git, but you get the gist - otherwise, ultimately,  we could argue that the whole editor is redundant since we already have cat and tail and head and could use those instead of Lime.

I think @quarnster was suggesting someone write a plugin that does the same thing but uses a git repo under the hood. Rather than building it into the editor itself.
I can see the value in this as a feature, but it's pretty low priority.

My point is that from the use case presented, it doesn't seem to me like you care about every single branch in a potential undo-forest. Wouldn't a K.I.S.S. solution like saving your file into "solution1.cpp" and "solution2.cpp", and linking that "active" file to the originally named file, either manually or via a plugin solve the use case much more trivially?

Another example / use case:
I added and changed a lot of code, and now it doesn't compile / work, damn! How did it look before again before I broke it? Let's take a quick look....
CMD-Z, CMD-Z, CMD-Z, CMD-Z ... (*100), accidentally press Z without CMD, now the whole progress is gone because I typed Z. Good grief, now I have to rewrite everything!

IMO the CMD-Z*100 then a mistaken "z" destroying the whole stack is much more a convincing use case for implementing this :)
If we limit it, it should be user configurable. In a sense, "regular" stack undo-redo is just the tree undo-redo limited to a single branch.

Awesome! :D It's also worth mentioning that I often copy some text, delete it to insert somewhere else later, make 100+ edits, and in the meantime fill the clipboard with other things. So I have to Undo*100 to find the deleted text again.
It'd be nice to be configurable, for sure. What do you think about the memory limitations? I think it would be great to have some "intelligence" behind it. Certain possibilities that come to mind:

Keep last X branches (configurable, default to 10?)
Keep branches whose edit-count weighs ≥X% of the active branch's. (configurable, default to 10)
Example:
Open Editor, 10 * Edit, 5 * Undo, 50 * Edit
Branch b1 (inactive) has 10 edits in total, 5 since separated from b2.
Branch b2 (active)    has 55 edits.
Relative to their fusion point, b1 has 5 edits, b2 has 50, which is 10%, so b1 remains in the tree.
If user makes another edit to active branch, b1 will be removed. 1 Undo + 1 Edit will have no effect on b1.

Opinions?

Well, this needs to be implemented in steps but I can see it as something like:

[ ] Extend undo-redo into a tree, but keeping it work like current undo-redo
[ ] Add in ability to switch tree branch (preferably a visual tree and ability to select any change in the tree)
[ ] Define a user configurable memory budget allowance for the undo-redo tree. Once the budget is overrun, trim the tree.

[ ] How much memory is saved by merging several undo-steps into a single one?
[ ] How much memory is saved by cutting the <= X% branches?
[ ] Should it be possible to save/restore parts of the tree to disc?
[ ] Worst case, just cut off the oldest changes


Implement Rust launcher project structure

Implement Rust launcher project structure. This issue only aims to include changes regarding BGArmor's project structure, libraries and related things.

Implemented on #7


single-quote-character not a string, fixes #2039

For Smalltalk, a single quote character... $'
does not start a string e.g.  'foobar'.
Fixes #2039.

Thank you for the fix @bencoman!
Before we can merge this, you have to rebuild Prism (this is also the reason why the build failed). To do this run the npx gulp command. This will automatically minify all languages definitions.

I'm not familiar with this error "cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing."

Unfortunately, neither am I, but I still have a fix.
Please revert your changes to package.json and package-lock.json. Then use npm ci instead of npm install. After that, npx gulp again. This should fix the build and also revert the ~10 other minified files that changed.

cipm was the name of the npm ci command before it was merged into npm core. npm ci uses the lockfile only to install the npm dependencies. It's warning you that because the lockfile & the pkg.json out of sync, relying on the lockfile alone won't produce the expected results, so it errors.
That said, @RunDevelopment's solution should work.

Thank you for contributing @bencoman!


HA not connecting to Loxone since 2023.8

**Which Model do you use from loxone? Gen 1
Which software version does your loxone use? <IP_ADDRESS>
How did you install HomeAssistant? Over Hassio or manual install? Hassio
Which Version do you use of HomeAssistant? 2023.8
Describe the bug
A clear and concise description of what the bug is.
Paste the error log with the following settings:
Logger: homeassistant.config_entries
Source: helpers/device_registry.py:165
First occurred: 8:21:35 pm (1 occurrences)
Last logged: 8:21:35 pm
Error setting up entry PyLoxone for loxone
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/loxone/init.py", line 228, in async_setup_entry
await miniserver.async_update_device_registry()
File "/config/custom_components/loxone/miniserver.py", line 223, in async_update_device_registry
device_registry.async_get_or_create(
File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 511, in async_get_or_create
device_info_type = _validate_device_info(config_entry, device_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 165, in _validate_device_info
raise DeviceInfoError(
homeassistant.helpers.device_registry.DeviceInfoError: Invalid device info {'configuration_url': 'http://<IP_ADDRESS>:80', 'connections': {('mac', '<IP_ADDRESS>')}, 'default_manufacturer': 'Loxone', 'identifiers': {('loxone', '504F9410A2DE')}, 'manufacturer': 'Loxone', 'model': 'Miniserver (Gen 1)', 'name': 'Miniserver', 'sw_version': '<IP_ADDRESS>'} for 'loxone' config entry: device info needs to either describe a device, link to existing device or provide extra information.

Got the same issue, with a Gen 2 miniserver
My log:  (This shows up for 8 times and I also got the indivual ones, those show up 2 times, what makes 4 :) )
`Logger: homeassistant.config_entries
Source: helpers/entity_component.py:187
First occurred: 9:33:31 PM (8 occurrences)
Last logged: 9:33:31 PM
Error setting up entry PyLoxone for cover
Error setting up entry PyLoxone for fan
Error setting up entry PyLoxone for light
Error setting up entry PyLoxone for climate
Error setting up entry PyLoxone for alarm_control_panel
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 132, in async_setup_entry
return await component.async_setup_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 187, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!`

@jdenver13 I updated PyLoxone on HACS, and that fixed it for me!

@jdenver13 I can confirm, updating PyLoxone fixed the problem.
Many thanks to @JoDehli for the quick fix!

Thank you, updates just come through and problem solved.

I have still the same issue even after updating to 0.4.6. Any ideas why?

@I-am-OK-86 that is another error. Not the same as the other users had. There is something wrong with your setup?
Unexpected error importing loxone/system_health.py
Unexpected error importing loxone/logbook.py
Unexpected error importing loxone/cast.py
Unexpected error importing loxone/significant_change.py
Unexpected error importing loxone/hardware.py
This errors are very strange. In my binding there are no such files used. I do not know why they should be imported. please uninstall pyloxone completely and reinstall it. And if you still has this problem make another issue and describe completely what setup you use and how you installed your system. Docker, bare or Hassio ....

Thanks, still the same issue after deleting the whole installation. I created ticket #191. Thanks or your support.


Use Decompose for shared navigation

As discussed on Twitter, here is a draft just to demonstrate how it would look like. Only the main Android app is working - it looks and feels basically the same, just added some fancy screen transitions. Wear, Auto (commented out), and any other platforms or tests are not touched yet. This should be also compatible with SwiftUI if needed. Unit and integration testing should be also pretty easy.
Tests and checks should be failing for now.
Please let me know your thoughts, feel free to discard if not interested, or I can finish the rest.

is idea that Decompose would provide something similar instead?

Yes, there are two options. Either expose states via a Flow wrapper (like CFlow), or use Value provided by Decompose. IN the latter case, the SwiftUI side works as explained in the docs.

I guess more general question then is whether view models have a place when using Decompose?  Are there ways of using Decompose to specifically address shared navigation alone or is expectation that those broader changes would be needed as well to do that?

There is no such an entity as ViewModel in Decompose. In Jetpack Compose, the ViewModel plays two roles: 1. It retains in the back stack; 2. It retains over configuration changes.
With Decompose, the first case is handled automatically - components are retained in the back stack.
The second case can be handled explicitly via InstanceKeeper if needed. However, in Confetti it is already handled by the app-scoped repository, so the app works just fine.

I have updated the iOS app.

Updated Android Auto app

Not sure if it needs a rebase or something but getting following for some reason
gh pr checkout 688
From https://github.com/joreilly/Confetti
 ! [rejected]          refs/pull/688/head -> decompose  (non-fast-forward)
failed to run git: exit status 1

Perhaps, that's because I force-pushed one of the commits

ah, maybe I have branch here from before....let me delete it and try again.....yep, that was it!

The failure before was related to jvm target and due to instance not running....should be addressed by https://github.com/joreilly/Confetti/pull/702


add Oxbridge Academy

http://oxbridgedu.az/en/article/5

@Jaguanda Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@Jaguanda You might miss my previous comment. Please react.

@Jaguanda I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Ros2 v0.8.0 emergency handler

Depends on https://github.com/tier4/AutowareArchitectureProposal.iv/pull/274

[x]  Build passed if rebase on tracking branch
Package: emergenecy_handler

[x] ros2 run success
Node: emergenency_handler

[x] Test  passed


1 feature

Current coverage is 100.00%

Branch #6 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


#254 - Update the dropbox script location.

@rultor merge

@rultor merge

@driver733 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@driver733 Oops, I failed. You can see the full log here (spent 3min)

92% [3 libsoup-gnome2.4-1 5463 B/16.4 kB 33%]

100% [Working]

Fetched 618 kB in 0s (5048 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ...

Preparing to unpack .../libcups2_2.2.1-8+deb9u2_amd64.deb ...
Unpacking libcups2:amd64 (2.2.1-8+deb9u2) over (2.2.1-8+deb9u1) ...
Preparing to unpack .../libsoup2.4-1_2.56.0-2+deb9u2_amd64.deb ...
Unpacking libsoup2.4-1:amd64 (2.56.0-2+deb9u2) over (2.56.0-2+deb9u1) ...
Preparing to unpack .../libsoup-gnome2.4-1_2.56.0-2+deb9u2_amd64.deb ...
Unpacking libsoup-gnome2.4-1:amd64 (2.56.0-2+deb9u2) over (2.56.0-2+deb9u1) ...
Setting up libsoup2.4-1:amd64 (2.56.0-2+deb9u2) ...
Setting up libsoup-gnome2.4-1:amd64 (2.56.0-2+deb9u2) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up libcups2:amd64 (2.2.1-8+deb9u2) ...
 Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree

Reading state information... 0%

Reading state information... 0%

Reading state information... Done

The following additional packages will be installed:
  hashdeep
The following NEW packages will be installed:
  hashdeep md5deep
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 136 kB of archives.
After this operation, 315 kB of additional disk space will be used.

0% [Working]

Get:1 http://deb.debian.org/debian stretch/main amd64 hashdeep amd64 4.4-4 [124 kB]

4% [1 hashdeep 6608 B/124 kB 5%]

83% [Waiting for headers]

Get:2 http://deb.debian.org/debian stretch/main amd64 md5deep all 4.4-4 [12.0 kB]

86% [2 md5deep 5162 B/12.0 kB 43%]

100% [Working]

Fetched 136 kB in 0s (2215 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package hashdeep.
(Reading database ...

Preparing to unpack .../hashdeep_4.4-4_amd64.deb ...
Unpacking hashdeep (4.4-4) ...
Selecting previously unselected package md5deep.
Preparing to unpack .../archives/md5deep_4.4-4_all.deb ...
Unpacking md5deep (4.4-4) ...
Setting up hashdeep (4.4-4) ...
Setting up md5deep (4.4-4) ...
+ curl https://raw.githubusercontent.com/andreafabrizi/Dropbox-Uploader/master/dropbox_uploader.sh -o dropbox_uploader.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 49655  100 49655    0     0   258k      0 --:--:-- --:--:-- --:--:--  259k
+ chmod +x dropbox_uploader.sh
+ ./dropbox_uploader.sh

 This is the first time you run this script, please follow the instructions:

 1) Open the following URL in your Browser, and log in using your account: https://www.dropbox.com/developers/apps
 2) Click on "Create App", then select "Dropbox API app"
 3) Now go on with the configuration, choosing the app permissions and access restrictions to your DropBox folder
 4) Enter the "App Name" that you prefer (e.g. MyUploader6609943122720)

 Now, click on the "Create App" button.

 When your new App is successfully created, please click on the Generate button
 under the 'Generated access token' section, then copy and paste the new access token here:

 # Access token:
 > The access token is 5o7qRn8BbEUAAAAAAAAKvzYIcb1V8GDbp8Gd24XV3ogR95gJOU0El33Yyvp125wJ. Looks ok? [y/N]: container c6cbaf068a22e4560d9b362718e30962fbd942ee44cb809cdf33ee31e7c98b12 is dead
Fri Jul 13 11:04:31 CEST 2018


False positive on io.gitlab.arturbosh.detekt:detekt-cli due to misidentified cpe io.gitlab.gitlab

False positive on libraries

detekt-cli-1.0.0.RC6-4.jar - io.gitlab.arturbosch.detekt:detekt-cli:1.0.0.RC6-4 - reported as cpe:/a:gitlab:gitlab:1.0.0.rc6
detekt-core-1.0.0.RC6-4.jar - io.gitlab.arturbosch.detekt:detekt-core:1.0.0.RC6-4 - cpe:/a:gitlab:gitlab:1.0.0.rc6
detekt-rules-1.0.0.RC6-4.jar - io.gitlab.arturbosch.detekt:detekt-rules:1.0.0.RC6-4 - cpe:/a:gitlab:gitlab:1.0.0.rc6
detekt-api-1.0.0.RC6-4.jar - io.gitlab.arturbosch.detekt:detekt-api:1.0.0.RC6-4 - cpe:/a:gitlab:gitlab:1.0.0.rc6

<dependency>
   <groupId>io.gitlab.arturbosch.detekt</groupId>
   <artifactId>detekt-cli</artifactId>
   <version>1.0.0.RC6-4</version>
</dependency>

Looks like a misidentification as the gitlab project due to being under the same namespace (io.gitlab)

Thanks for the FP report!

No problem at all!
I just realised that the fix is simply a PR to
dependencycheck-base-suppression.xml, so I will do it later today.
El El mar, 27 mar 2018 a las 11:12, Jeremy Long<EMAIL_ADDRESS>escribió:

Thanks for the FP report!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/1151#issuecomment-376471659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHMSgsto74seEsuaLE1triSzsQKKEsg7ks5tihCUgaJpZM4S7wkJ
.

Actually @jeremylong, let me know if this is a bug since I feel that cpe:/a:gitlab:gitlab should not be picking up io.gitlab.arturbosch.
If it is - I'd love to fix it as well (although may need some guidance).
Otherwise I'll submit an update to the suppression file.

@reddyalready Updating the suppression file for this is likely the best option. PRs are welcome - or I will sweep through all the FP reports in the near future and update the suppressions file as appropriate.


Enabling sangbox_cgroup_only causes the creation of pods with small memory.limits settings to fail

Enabling sandbox_cgroup_only will add VM processes etc. to the pod's cgroups, when setting Pod a small resource.limits.memory, e.g. 50MiB, will cause the VM to fail to start.
Or set a larger value, for example 2GiB, the container will be OOM during actual use, even if the container is not used to the limit value.
Should we consider adding vm's quota to cgroupfs?

/cc @devimc.

@Bevisy could you please provide the relevant logs so we can see what's going on?
Running kata-collect-data.sh

this is is expected since kata needs more than 50M of ram to run, please consider using Pod Overhead https://kubernetes.io/docs/concepts/scheduling-eviction/pod-overhead/


[stable/prometheus-operator] expose sessionAffinity

Signed-off-by: Yusuke Otsuka<EMAIL_ADDRESS>
What this PR does / why we need it:

expose prometheus's sessionAffinity config for multiple prometheus and grafana environment

This value is needed for High Availability configuration.
Which issue this PR fixes

fixes #10044

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @gianrubio @mjhd-devlion

/unassign @gianrubio @mjhd-devlion

I misunderstood the document. This PR does not solve my problem.


Fix missed case in "observe" type check

Redux briefly checks that observer received in observe function is a valid object and throw TypeError with useful user message if is not.
However, it missed null case, as typeof null === 'object' (well-known js issue) and then failed with the obscure error message Cannot read property 'next' of null.  I'm sure that there is no reason to not to show the correct error message in all relevant cases
https://github.com/reactjs/redux/blob/master/src/createStore.js#L237
This PR fixes that inconsistency by throwing TypeError with the same useful message in case of null observer
Note that this PR is not a breaking change in any way

Thanks!


Question about sliding window

Dear authors,

Do you use sliding window over the input video in both algorithms ? (ICASSP and CVPRW)
Since the input video size is reduced to N-15 frames from N how do you extract per frame labels ( 0 or 1 ) ?

Thank you in advance

Hi,

Yes, for both algorithms we use the I3D network with sliding window over the input video to extract features (windows size: 16 frames, stride: 1 frame)
Because of the window size of 16 frames for the feature extraction we get a reduced number (N-15) of feature vectors. We assign the feature vector always to the middle frame of the window. Therefore you don't get features for the first and last few frames and also no boundary predictions. In case you need them you can extend the video by half of the window size on both sides.