Set Xauthority by default

This seems necessary on Ubuntu 22, following the tests in issue #1

pulled this PR, re-built the docker image and ran using docker run --rm --interactive --tty --env DISPLAY=$DISPLAY --net host --name easyturtle easyturtle
success !
(note requires xhost +local:docker after every reboot...)
I think PR is ready to merge! @ic

Thank you, @ljburtz


Change wording in map menu

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue: Closes #9976

Description
Changes "Collapse all challenges" to "Hide all challenges" for easier understanding

@Rlin415 thanks a lot for the fix.
:sparkles: Congratulations on your first contribution to Free Code Camp :sparkles:


Implement remaining sidetree DID operations with API for CLI

In addition to create, resolve, sign, verify and deactivate, implementations of the following will allow events like revocation:

[ ] update: perform an update (add/remove keys and/or services). TODO: How the data is passed to the binary/fns
[ ] reset or recover: perform a recovery operation to reset the entire DID document
[ ] Deactivate: related to #30

Task for this issue:

[ ] Consider general error enum for ION crate to remove use of Result<_, Box <dyn Error>> in API


Fix target-branch for azure devops client.

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Fix target-branch for Azure DevOps client. It seems the PR #1074 isn't sufficient enough for Azure DevOps after testing.  @CrispyDrone
:arrow_heading_down: What is the current behavior?
After providing the targetbranch argument, NuKeeper keep checking against the default branch of the repo.
:new: What is the new behavior (if this is a feature change)?
Fix the PR #1074
:boom: Does this PR introduce a breaking change?
nop
:bug: Recommendations for testing
Provide the --targetBranch argument against the Azure DevOps repo and see that NuKeeper will check dependencies against the provided --targetBranch.
:memo: Links to relevant issues/docs

:thinking: Checklist before submitting

[ ] All projects build
[x] Relevant documentation was updated
[x] Unit tests added

After reviewing the class I saw something strange in the method "CreateSettingsFromLocal". There is a variable remoteInfo instantiated but never used.
It seems to be refactored during this PR #841. I'm not sure if we should provide the remoteinfo variable to the method "CreateRepositorySettings"
Any ideas?

And any ideas how I can fix the builds to finish this PR. TIA :)

@CrispyDrone can you confirm that this adds to your PR? And maybe review this one?

@CrispyDrone can you confirm that this adds to your PR? And maybe review this one?

@kwlin @MarcBruins
I only have an Azure Devops Server instance at work, so unfortunately I cannot test it very easily there. I do have a personal azure devops service instance that I could try out. I'll give it a try.

@kwlin @MarcBruins
I only have an Azure Devops Server instance at work, so unfortunately I cannot test it very easily there. I do have a personal azure devops service instance that I could try out. I'll give it a try.

@CrispyDrone thanks for verifying my changes. I have tested my changes against Azure DevOps but not against Azure Devops Server Instance ;)
Any pointers how I can fix the builds?

@CrispyDrone thanks for verifying my changes. I have tested my changes against Azure DevOps but not against Azure Devops Server Instance ;)
Any pointers how I can fix the builds?

@CrispyDrone any help needed for completing this PR?

@CrispyDrone  sorry for the delay in reply (was very busy lately). Anyway thanks for the additional fix and I'm curious about other issues you have found :)
I can apply the change in the PR but I'm not sure what the PackageUpdater class does.

@skolima  Could you review this PR also? I'm tagging you because of your great work of merging my PR's 😄

Yeah, that looks ok.


code snippet need colors

The website has some labs that have code snippets like java or yaml, it would be good to configure this snippets to be render with color based on programing or markup language
Example using xml https://csantanapr.github.io/cloudnative-learning-101/cloudnative-learning-101/1.0.0/Cloud_Native_Module/Lab1.html

I think I found the fix using [source, xml]
https://asciidoctor.org/docs/user-manual/#enabling-source-highlighting

There are still more pages to fix


support orderBy on collectPhase

Previously the collectPhase.orderBy() property wasn't supported in the
execution-phase of sys tables. Therefore the Planner had to add a
TopNProjection instead.
This commit adds support for the orderBy property so that the planner no
longer has to differentiate between sys and doc tables.
Unfortunately, as there is no hard-limit on the collectPhase it will now
always order ALL rows und not just LIMIT rows.

ack


diff drive robot cannot rotate in bullet-feathestone

Environment

OS Version: Ubuntu 24.04
Binary, gz-physics7 installed along with ros2 jazzy

Description
I apologize if this was address somewhere before. I'm working on a robot with differential drive using bullet-featherstone physics engine. The robot can move forward and backward without any issues but struggles to rotate in place. Instead of rotating, the robot slips, with no significant rotation. Even with the sample diff_drive.sdf, the vehicle is unable to turn or rotate in place. I also tried setting the caster friction to 0 but to no avail.

Expected behavior: Diff drive robot can rotate in place
Actual behavior: Diff drive robot does not rotate in place

Steps to reproduce

gz sim diff_drive.sdf --physics-engine gz-physics-bullet-featherstone-plugin
gz topic -t /model/vehicle_green/cmd_vel -m gz.msgs.Twist -p "linear: {x: 0.0}, angular: {z: 5.0}"

Output

https://github.com/user-attachments/assets/a12581db-0aff-4f01-a4e9-40b51799cfe2

I think the default torsional friction value in bullet is causing this issue. As a workaround, try setting it to 0 to all the wheels and the ground plane, i.e. add this to the <collision> element in sdf:
          <surface>
            <friction>
              <torsional>
                <coefficient>0.0</coefficient>
              </torsional>
            </friction>
          </surface>

I see, thank you for your help!
Setting the wheel and the ground plane torsional friction to 0 works.


unicode/utf8: make DecodeRune and DecodeLastRune inlineable

Code like the following is unfortunately very common:
r, n := rune(b[0]), 1
if r >= utf8.RuneSelf {
    r, n = utf8.DecodeRune(b)
}

and we have several examples in the standard library itself:

fmt/format.go:347
fmt/print.go:1101
regexp/regexp.go:418
regexp/regexp.go:465
bytes/bytes.go:482
bytes/bytes.go:560
bytes/bytes.go:781
bytes/bytes.go:836
bufio/bufio.go:295
strings/strings.go:741
strconv/quote.go:43
strconv/quote.go:266

All of these cases ultimate come down to the caller manually performing inlined logic for the ASCII case. We should make it such that DecodeRune and DecodeLastRune are inlineable for the ASCII case. Unfortunately my attempts to do so exceed the inline budget by ever so much:
// cannot inline DecodeRune: function too complex: cost 87 exceeds budget 80
func DecodeRune(p []byte) (r rune, size int) {
	if len(p) > 0 && p[0] < RuneSelf {
		return rune(p[0]), 1
	}
	return decodeRune(p)
}

// cannot inline DecodeLastRune: function too complex: cost 93 exceeds budget 80
func DecodeLastRune(p []byte) (r rune, size int) {
	if len(p) > 0 && p[len(p)-1] < UTFMax {
		return rune(p[len(p)-1]), 1
	}
	return decodeLastRune(p)
}

We should find a way to make these inlinable whether by special casing them, clever tricks to make the cost lower, by increasing the inline budget, etc.
\cc @CAFxX @josharian @mdempsky @martisch

FWIW, I gave it a shot before: https://go-review.googlesource.com/c/go/+/332770
Unfortunately yes, I really can not see a way to make it work without messing with the inliner or adding some kind of annotation.

Seem to remember commenting on a similar issue, that couldn't do the same with binary.Uvarint().
#31666
But now with for loop inlining since added to go, Uvarint() can be made to (replace range use) inline as whole without needing a separate func.

The inline cost of the following implementation is 83:
func DecodeRune(p []byte) (r rune, size int) {
	if len(p) > 0 && p[0] < RuneSelf {
		r, size = rune(p[0]), 1
	} else {
		r, size = decodeRune(p)
	}
	return
}

And this one is 81:
func DecodeRune(p []byte) (r rune, size int) {
	if len(p) > 0 && p[0] < RuneSelf {
		return rune(p[0]), 1
	}
	r, size = decodeRune(p)
	return
}

Maybe the inline cost calculation should consider whether or not bound checks are eliminated.
Here, the bound checks for p[0] are eliminated, so its cost should be some lower.
BTW, why the inline costs of function calls are so large?

The ExtraCall budget is 57 plus two arguments we had at least 64 budget, maybe we can force inline by asm code.
However I've tried modified the ExtraCall budget  and it appears only improve ASCII related DecodeRune and regression on slow path.
https://perf.golang.org/search?q=upload:20210922.6
name                               old time/op  new time/op  delta
RuneCountTenASCIIChars             9.27ns ± 1%  9.27ns ± 1%     ~     (p=0.151 n=9+9)
RuneCountTenJapaneseChars          37.8ns ± 2%  38.2ns ± 1%   +1.09%  (p=0.022 n=10+8)
RuneCountInStringTenASCIIChars     9.26ns ± 0%  9.26ns ± 0%     ~     (p=0.333 n=10+10)
RuneCountInStringTenJapaneseChars  39.3ns ± 1%  38.1ns ± 2%   -3.07%  (p=0.000 n=10+10)
EncodeASCIIRune                    1.71ns ± 0%  1.71ns ± 0%     ~     (all equal)
EncodeJapaneseRune                 2.86ns ± 0%  2.83ns ± 0%   -1.12%  (p=0.000 n=10+9)
AppendASCIIRune                    0.26ns ± 0%  0.26ns ± 0%   -2.44%  (p=0.000 n=7+10)
AppendJapaneseRune                 3.09ns ± 0%  3.08ns ± 0%   -0.02%  (p=0.029 n=9+9)
DecodeASCIIRune                    2.06ns ± 0%  0.26ns ± 0%  -87.53%  (p=0.000 n=8+8)
DecodeJapaneseRune                 3.60ns ± 0%  3.73ns ± 0%   +3.52%  (p=0.000 n=10+8)
FullRune/ASCII                     1.03ns ± 0%  1.18ns ± 3%  +14.28%  (p=0.000 n=10+10)
FullRune/Incomplete                2.18ns ± 2%  2.14ns ± 1%   -2.00%  (p=0.000 n=10+10)
FullRune/Japanese                  1.03ns ± 0%  1.18ns ± 3%  +15.03%  (p=0.000 n=9+10)

However I've tried modified the ExtraCall budget and it appears only improve ASCII related DecodeRune and regression on slow path.

Isn't that expected? With inlining, we generally want to get the common case to be inlined (i.e., ASCII), and perform the function call for the less common case (i.e., multibyte Unicode).


global .hgignore file is ignored

Ag doesn't respect global ~/.hgignore file.
I want to mention that this is not the standard file name though, it is usually set in users configuration (.hgrc) like this:
[ui]
ignore = ~/.hgignore

And can be queried with this command:
 hg config ui.ignore

It would be nice to have this supported.

ag doesn't rely on any existing binaries on the system, such as hg or git. Using something like hg config ui.ignore would require that to be installed.
Assuming hg is installed, we could run hg locate in mercurial directories to get 100% accurate ignores. We wouldn't need special logic for parsing .hgignore files or applying their ignores.
But, there are a handful of downsides to relying on hg:

If hg is not installed, how do we get our ignores? Do we forget about them and search every file?
If hg is installed but the repo is in some broken / strange state, ag will crash
If hg locate is slow, ag will be slow
Is hg now a dependency of ag in apt / brew / macports / yum / packman?

tl;dr - hg config ui.ignore is not going to happen
But an OK solution would be to blindly assume the global ignore would be located at ~/.hgignore. I bet this guess will be correct for 95% of global ignores, which is a lot better than the 0% we're getting right now.

Hmm, I agree with your concerns. Assuming the file is named ~/.hgignore doesn't sound like a bad idea now.


SetIxfr with empty ns and mbox -> Malformed Packet

With "dig" the ns and mbox field is empty (inside the packet a byte with value 0 for both strings).
But SetIxfr will create malformed packets which causes "dns: bad xfr rcode: 1".
BTW: Parsing the error string to get the code number is kinda cumbersome. Wouldn't it be better to have an own error type which holds the rcode number? Something like type XfrError struct{ Rcode int }?

Yes SetIxfr will happily do what it is told to do.
Agree with the typed errors. That would have been a better idea, sadly that horse has left the barn.

Yes SetIxfr will happily do what it is told to do.

And how do you tell SetIxfr to create a correct packet with empty ns
and mbox? SetIxfr("example.com.", 7, "", "") won't do the trick.

Agree with the typed errors. That would have been a better idea, sadly that horse has left the barn.

You only export the error interface, so this should work without
breaking anything:
`type XfrError struct { Rcode int }
func (e *XfrError) Error() string {
if e == nil {
return "dns: "
}
return "dns: bad xfr rcode: " + strconv.Itoa(e.Rcode)
}`
And use it in xfr.go c <- &Envelope{in.Answer, &XfrError{in.Rcode}}.
But I understand if you don't take the chance to break stuff like
err.(*dns.Error). Maybe something for a dns.v2.
Would also be nice to return the error string via RcodeToString[e.Rcode]
in dns.v2.

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] SetIxfr with emtpy ..." ]

And how do you tell SetIxfr to create a correct packet with empty ns
and mbox? SetIxfr("example.com.", 7, "", "") won't do the trick.

SetIxfr("example.com.", 7, ".", ".")
should work.

Agree with the typed errors. That would have been a better idea, sadly that horse has left the barn.

You only export the error interface, so this should work without
breaking anything:
`type XfrError struct { Rcode int }
func (e *XfrError) Error() string {
if e == nil {
return "dns: "
}
return "dns: bad xfr rcode: " + strconv.Itoa(e.Rcode)
}`
And use it in xfr.go c <- &Envelope{in.Answer, &XfrError{in.Rcode}}.
But I understand if you don't take the chance to break stuff like
err.(*dns.Error). Maybe something for a dns.v2.
Would also be nice to return the error string via RcodeToString[e.Rcode]
in dns.v2.

Yeah v2 :-)
You're right though, this can be changed without breaking code. Care to submit
a PR?

SetIxfr("example.com.", 7, ".", ".")
should work.

You're absolutely right - can't believe I didn't tried this. ;)
My bad, issue closed.

Yeah v2 :-)
You're right though, this can be changed without breaking code. Care
to submit a PR?

Well, I've added it into PR #507, but if this is unhandy and you prefer
a new PR, let me know.

It's better to do as a separate PR (1 issue -> 1 pr)


fix various keybinding/shortcut bugs

fixes #5332
fixes #5579
depends on https://github.com/pyapp-kit/app-model/pull/82

I tested this (along with the app-model PR) and it all worked as advertised! 🎉
I'll try and take a closer look at the code tomorrow evening.

Why test are passing in cases when this should not work with not fixed app-model?

Why test are passing in cases when this should not work with not fixed app-model?

Same reason they pass without this PR at all? 🤔

Same reason they pass without this PR at all? :thinking:

So it means that this PR does not contain proper test? :thinking:

So it means that this PR does not contain proper test? 🤔

For the symbol swapping I can create tests since that would be fairly trivial (with patching I think). I was also thinking of straight-up porting this logic to app-model (see this issue), and we could test there, what do you think of doing that at the cost of this PR taking a bit longer? We could then make a release on app-model for that and the other dependency for this PR since they're related and not stagger dependency bumping.
The GUI aspect is a bit more difficult to test but I could try covering it. Much of the codebase lacks proper GUI tests.

Does that also includes fixes of #5064 ?

it does fix #5047 however

It does not, but I can look into porting that over too.

That's fine, I can rebase later. I would just hope that there were more review/merge of pending PRs, as otherwise things like this keep happening, where work conflicts and we need to keep rebasing.

I would just hope that there were more review/merge of pending PRs

please ask for a specific PR on zulip #reviews stream. Most of us spend free/unpaid time on maintenance napari and it is easy to lose some PR.

please ask for a specific PR on zulip #reviews stream. Most of us spend free/unpaid time on maintenance napari and it is easy to lose some PR.

Sorry if I made you feel you were not doing enough, I know the feeling and I am doing my best to also help unblock by reviewing/rebasing fixing trivial mistake in CI.

Hi all, sorry for the delay, I've been on vacation and just got back. It looks like @Czaki was advocating for more GUI test coverage, would you still like this prior to merge (since it will further delay the bugfix)? Also are there any opinions on moving some of the symbol rendering to app-model and making sure it's tested on that end?

I think we're fine without gui-specific tests... The think we should make sure we test is that if someone changes something elsewhere we don't suddenly lose some of this stuff.

Hi @Czaki, I wanted to check if you've had an opportunity to give this a test and/or if you still would like to see GUI tests in this PR!

Hi @kne42, I talked with @Czaki about this last Friday and the consensus is that having a test would be ideal. Local checks have been successful, but we need an automated method to prevent regressions in the future.
I am happy to assist / take over if you need help, just let me know!

I've tried it locally on Mac, and it seem  some logic is wrong.
Pressing ⌘E for a shortcut ends up assigning it to ^E, vice versa.

Note that on main, trying to Edit a shortcut press say ⌘E, ends up while editing with Control+E, with Control fully spelled, while with this PR this become Ctrl-E, with the short spelling of Ctrl.
There also seem to not work with existing custom shortcuts, i.e. if on main I set a shortcut to ⌘⇧D and checkout this PR, the shortcut appear empty in the preference windows,

Ok it seem for whatever reason my local install was not picking up the newer App-Model and it does work.
I've found another bug though, I can't assign the ⌘E shortcut as alt-E is the shortcut on international keyboard for the ´ combining key, and seem to affect any other combining keys do you want me to open another issue for this ?

I've found another bug though, I can't assign the ⌘E shortcut as alt-E is the shortcut on international keyboard for the ´ combining key, and seem to affect any other combining keys do you want me to open another issue for this ?

yes please, if im understanding correctly, you want to set the shortcut as ⌘E but it becomes ´ instead? seems like it could get pretty hairy if that's the case

I am happy to assist / take over if you need help, just let me know!

@jaimergp I am super stressed/busy right now so any help with the GUI tests would be greatly appreciated!

Just checked and this works locally once app-model is updated. Alt-E is a problem but Cmd-Alt-E is not, and Alt-E is also a problem on main, so I suggest we merge this. (Optionally after merging in @Czaki's suggestion of changing list to set.)
While typing it shows "Meta-E" or "Meta-Alt-E", it would be cool if the Mac-native symbols appeared while typing but that can be updated later imho. @Czaki I also think this should go in 0.4.18, I've added the milestone accordingly, but of course you can modify it if you disagree.

While typing it shows "Meta-E" or "Meta-Alt-E", it would be cool if the Mac-native symbols appeared while typing but that can be updated later imho.

@jni For me, this PR does that: https://github.com/napari/napari/pull/5064 but I'm not sure how it interacts with this one.

@Czaki I also think this should go in 0.4.18, I've added the milestone accordingly, but of course you can modify it if you disagree.

This PR fixes issue related to #5103 which has 0.5.0 milestone, so that one would also need back porting...

so that one would also need back porting...

If you backport a lot, I can remind you of my backport bot

This PR fixes issue related to #5103 which has 0.5.0 milestone, so that one would also need back porting...

but I do not backport anything related to app model keys.


[11.x] Allow adding array or string for web and api routes in bootstrap/app.php

This PR is Resubmitted after Taylor feedback

This pull request proposes an enhancement to Laravel's bootstrap/app.php file, enabling developers to add routes in array format or as strings for both web and api route groups.
Motivation
The motivation behind this enhancement is to provide developers with greater flexibility and convenience when defining routes, particularly in scenarios where applications have different guards and need to create different routes for each guard rather than writing require/require_once in route file.
Use Cases
In projects where route management becomes complex due to the proliferation of routes or diverse authentication scenarios, this will simplifies the process by enabling developers to organize routes into multiple route files effortlessly. By allowing routes to be defined in array format, developers can easily create separate route files corresponding to different functionalities, user roles, or authentication guards. This approach promotes code organization and maintainability, as each route file can focus on a specific aspect of the application, making it easier to understand and manage.
Additional Context
I'm developing an ecommerce website with five different guards, and I want to include separate route files for each guard. Using require or require_once made my code look outdated, and I disliked it. Let's simplify by allowing arrays as well in the $web parameter of withRouting() method in Illuminate\Foundation\Application

We'll have to revert this one unfortunately because of https://github.com/laravel/framework/issues/51406


scrcpy --otg -Vdebug only works with USB debugging enabled

Please read the prerequisites to run scrcpy.
Also read the FAQ and check if your issue already exists.
Environment

OS: [e.g. Debian, Windows, macOS...] Windows 11
Scrcpy version: [e.g. 2.5]
scrcpy -v
scrcpy 2.5 https://github.com/Genymobile/scrcpy

Dependencies (compiled / linked):

SDL: 2.30.4 / 2.30.4
libavcodec: 61.3.100 / 61.3.100
libavformat: 61.1.100 / 61.1.100
libavutil: 59.8.100 / 59.8.100
libusb: - / 1.0.27
Installation method: [e.g. manual build, apt, snap, brew, Windows release...]
Device model:
Android version: [e.g. 14]

Describe the bug
I want to use "--otg" to use mouse and keyboard to enable USB debugging, but it only works, when it is already enabled. With usb debugging disabled, I get the following error:
scrcpy --otg -Vdebug
scrcpy 2.5 https://github.com/Genymobile/scrcpy
INFO: Killing adb server (if any)...
DEBUG: Read string: libusb error: Entity not found
ERROR: Could not find any USB device
Please paste terminal output in a code block.

Please do not post screenshots of your terminal, just post the content as text instead.

https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#otg-issues-on-windows


Want to know about generate auto ssl limit of lua-resty-auto-ssl

Just I have installed and configure GUI/lua-resty-auto-ssl and its working fine! I want to know about the limit, how many certificate generate by lua-resty-auto-ssl? Any limit per day or week?
I am using ubuntu system and configured lua-resty-auto-ssl well, when I run the sub-domain(https://sub.domain.com) it is creating auto ssl for that sub-domain.
I want to know the limit, how many domain I can use per day or week for generate auto ssl using lua-resty-auto-ssl?

This module is using Dehydrated to issue certificates from Let’s Encrypt. So you are limited by LE.
https://letsencrypt.org/docs/rate-limits/

Thanks. @gjongenelen


Durind testing i received this output . Here first 2 characters  are matching but still probablity is showing zero 7528 21ATI 1STAR 11 vs 7552 9118 3125

35202226293 vs 35202-2562938-3
FAAEER vs FATHER
08.05.222 vs 08.05.2029
accuracy is very bad


are there any way ffi for python?

OS : macos
any way to ffi for python 3.7?
i just import libfilecoin_signer_ffi.dylib on python  by cdll
and call some methods on dylib but it occur something segfault.

:link: zboto Link

I investigated a bit, and perhaps your issue has been fixed in the 2 years it's been open, but I was able to use the library from Lisp without segfault.
It depends on how you used the library, but perhaps you provided a non-zero terminated string? Currently we are using ffi_support::FfiStr which wants a 0-terminated string like C's.
Not sure what's python's behavior about passing strings via FFI.
If it's still a problem please reopen with more detailed error reproduction steps, thanks!


[BUG] Java Client SDK RestoreIndex is throwing Missing required property 'RestoreResponse.snapshot'

Attached code is throwing error with AWS OpenSearch, but index is getting restored as expected.
 			RestoreRequest.Builder builder = new RestoreRequest.Builder();
			builder.repository(repoName);
			builder.snapshot(snapshotName);
			builder.indices(Arrays.asList(settings.get("indices").split(",")));
			builder.partial(false);
			return openSearchClient.snapshot().restore(builder.build());

org.opensearch.client.util.MissingRequiredPropertyException: Missing required property 'RestoreResponse.snapshot'
	at org.opensearch.client.util.ApiTypeHelper.requireNonNull(ApiTypeHelper.java:89)
	at org.opensearch.client.opensearch.snapshot.RestoreResponse.<init>(RestoreResponse.java:58)
	at org.opensearch.client.opensearch.snapshot.RestoreResponse.<init>(RestoreResponse.java:51)
	at org.opensearch.client.opensearch.snapshot.RestoreResponse$Builder.build(RestoreResponse.java:122)
	at org.opensearch.client.opensearch.snapshot.RestoreResponse$Builder.build(RestoreResponse.java:95)
	at org.opensearch.client.json.ObjectBuilderDeserializer.deserialize(ObjectBuilderDeserializer.java:92)
	at org.opensearch.client.json.DelegatingDeserializer$SameType.deserialize(DelegatingDeserializer.java:55)

Do you have any screenshots?
See attached stack trace above
Do you have any additional context?
Using client version 2.9.1

Similar error happening with
                       CreateSnapshotRequest.Builder builder = new CreateSnapshotRequest.Builder();
			builder.repository(repoName);
			builder.snapshot(snapshotName);
			return openSearchClient.snapshot().create(builder.build());

org.opensearch.client.util.MissingRequiredPropertyException: Missing required property 'CreateSnapshotResponse.snapshot'
at org.opensearch.client.util.ApiTypeHelper.requireNonNull(ApiTypeHelper.java:89)
at org.opensearch.client.opensearch.snapshot.CreateSnapshotResponse.<init>(CreateSnapshotResponse.java:62)

@shasti421 Is this specific to AWS, or does this happen with vanilla OpenSearch? Also can you reproduce this with curl or is it a client problem?


Issue from website page 升级 Flutter

From URL: https://www.flutterchina.club/upgrading.md

@hangiangai https://www.flutterchina.club/ 看起来是一个爱好者翻译的网站，不像是flutter官方网站，你需要联系网站作者。

That is a community website not maintained by the Flutter team. Try https://github.com/flutterchina/website/issues


Add PasswordUtil.GeneratePassword

This method generates a random password that is guaranteed to contain a mix of character types, and does not need to be escaped if used in a connection string.
Based on a comment here: https://github.com/dotnet/aspire/pull/1295/files#r1428294263
The algorithm is designed to generate a password that meets SQL Server complexity requirements (e.g., to avoid the following error message):

The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols.

Microsoft Reviewers: Open in CodeFlow

This is not going to generate a secure password (eg it's issuing pseudo random generator). If it's not secure, why not simply use "password" or some other fixed value?
@GrabYourPitchforks

We should keep in mind that our current password generation is also not secure. I raised this internally and it was suggested that we do something like:
byte[] key256 = RandomNumberGenerator.GetBytes(32);
return Convert.ToBase64String(key256);

At long enough lengths that would likely be sufficient for generating a password with enough entropy. We would need to make sure that we observe the other password requirements such as special characters, upper, lowercase etc.

If it's not secure, why not simply use "password" or some other fixed value?

I assumed (perhaps incorrectly) that this was just intended to generate a pseudorandom password for testing that would stop people hard-coding a fixed default. If the actual intent of this method is to generate a production-ready password that would be stored in Azure Key Vault or similar, then this approach is obviously inadequate.

Its not for production generation, deployment tools will do that. But if we are going to take a step forward its worth addressing a few of these issues :)

I assumed (perhaps incorrectly) that this was just intended to generate a pseudorandom password for testing that would stop people hard-coding a fixed default. If the actual intent of this method is to generate a production-ready password that would be stored in Azure Key Vault or similar, then this approach is obviously inadequate.

Thanks. One other thing to bear in mind is that we have code scanners for things that look like passwords and tokens. To avoid triggering that we generally use the text "placeholder" which makes it clear it's not real (I don't have full context here.)


design.md links bevy-design-patterns as bevy_best_practices instead of bevy-design-patterns

At design.md, bevy-design-patterns goes to https://github.com/tbillington/bevy_best_practices instead of the proper link of: https://github.com/MiniaczQ/bevy-design-patterns (I'm not entirely sure if this is the right link).

@MiniaczQ would you prefer we remove it entirely? I have no problem linking to an outdated document, but it's yours, so your call :)

I'll try to get it updated with the few patterns that emerged and we can correct the link.
I'm fine with deleting it though, right now it serves no purpose


bug- texture

nomarl  is frist png ,   but sometime it auto became second png

this happend the latest viro version , before version no have this

@dthian


Add ConcatenateNode

Draft PR.
Some initial work for ConcatenateNode.
Includes

New class ConcatenateNode
New helper/utility function cartesian_product
2 test cases for shape, ndim, and buffer initialization

Taking a look at NumPy's implementation, I think it might be simpler to keep a start  for each concatenated array. E.g. for
[[ 0 1 ]  [[ 4 5 ]  [[ 8 ]
 [ 2 3 ]]  [ 6 7 ]]  [ 9 ]]

concatenated on axis 1 the we get
strides = [40, 8]  // strides of the resulting array
array0_start = 0
array1_start = 16
array2_start = 32

Or, for axis 0
[[ 0 1 ]
 [ 2 3 ]]
[[ 0 1 ]
 [ 2 3 ]]
[[ 0 1 ]]

strides = [16, 8]  // strides of the resulting array
array0_start = 0
array1_start = 32
array2_start = 64

Then setting the initial state looks like
std::vector<ssize_t> strides_into = {40, 8};
std::vector<ssize_t> array_starts = {0, 16, 32};

double* buff;  // allocate to the size of the array we're moving into

for (ssize_t i = 0; i < 3; ++i) {
    // create a view into our buffer with the same shape as our input array starting at the correct place
    auto view_it = ArrayIterator(buff + array_starts[i], this->ndim(), array_ptrs[i].shape().data(),  this->strides().data());

    // now just copy that data
    std::copy(array_ptrs[i]->begin(state), array_ptrs[i]->end(state), view_it);
}

Updates work similarly, but instead of copying you just do view_it + update.index;

With the minor issue that we don't actually let you use ArrayIterators to modify, as they all return const :laughing:. But we can change that.

https://github.com/dwavesystems/dwave-optimization/pull/162 has a mutable iterator implementation.

Taking a look at NumPy's implementation, I think it might be simpler to keep a start for each concatenated array. E.g. for
[[ 0 1 ]  [[ 4 5 ]  [[ 8 ]
 [ 2 3 ]]  [ 6 7 ]]  [ 9 ]]

concatenated on axis 1 the we get
strides = [40, 8]  // strides of the resulting array
array0_start = 0
array1_start = 16
array2_start = 32

Or, for axis 0
[[ 0 1 ]
 [ 2 3 ]]
[[ 0 1 ]
 [ 2 3 ]]
[[ 0 1 ]]

strides = [16, 8]  // strides of the resulting array
array0_start = 0
array1_start = 32
array2_start = 64

Then setting the initial state looks like
std::vector<ssize_t> strides_into = {40, 8};
std::vector<ssize_t> array_starts = {0, 16, 32};

double* buff;  // allocate to the size of the array we're moving into

for (ssize_t i = 0; i < 3; ++i) {
    // create a view into our buffer with the same shape as our input array starting at the correct place
    auto view_it = ArrayIterator(buff + array_starts[i], this->ndim(), array_ptrs[i].shape().data(),  this->strides().data());

    // now just copy that data
    std::copy(array_ptrs[i]->begin(state), array_ptrs[i]->end(state), view_it);
}

Updates work similarly, but instead of copying you just do view_it + update.index;

Cool! I'll get started on it
Where/how is strides_into being used?

Oops, strides_to is the same as this->strides() in my example above. Typo

This is the same idea as above, but I wrote a snippet that's hopefully a bit clearer for the view idea
import numpy as np

# Get 3 arrays
A = np.asarray([[0, 1], [2, 3]])
B = np.asarray([[4, 5], [6, 7]])
C = np.asarray([[8], [9]])

# Made a concatenated array over axis 1
D = np.concatenate((A, B, C), axis=1)

# Now, recover their views in the D array
A_view = D[:, 0:2]
B_view = D[:, 2:4]
C_view = D[:, 4:5]

# Edit the same entry in B and B_View
B[1, 1] = 100
B_view[1, 1] = 100

print(B)
print(D)


Prefix has rolled over to cccccb.* for newer devices

At some point in the last nine years, the YubiKey IDs have incremented/decremented a bit. The RegEx needs to likely come off one position to account for current/future growth.
Example:
cccccbengijujuknrknduruuulkhuhghdcffdlbbkljl
     ^-- sixth position b instead of c

Fixed via #7


Error page contact info

Update contact link and email headers on error pages
Changes

change href of contact us link on 404 and 500 pages to about-us/contact us/
add current url to let us know link mailto subject

Testing

Check out branch and run ./frontend.sh & ./runserver.sh
On http://localhost:8000/500/ and http://localhost:8000/404/, verify that:

contact us button links to the contact us page
let us know link mailto subject contains the current url

Review

@cfpb/cfgov-frontends

Screenshots
500 page let us know link:

404 page let us know link:

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

👍

Changes Unknown when pulling feeda2175f44e74d6024c72f38085c6654a9708e on error-page-contacts into ** on master**.

@sebworks Oh, sorry, I missed your PR with the mailto updates!
Do we need another review, or can this be merged?

@schaferjh, does this work for you?

Looks good to me!


[Todo List] Manage several lists

Extension
https://www.raycast.com/maggie/todo-list
Description
It would be nice to have one list for work and one for personal stuff etc
Who will benefit from this feature?
Most people I would guess
Anything else?
No response

@raycastbot close this issue


Korio Mingwx64

I want to use korio with mingwx64 on Windows. I used the following gradle setup:
repositories { mavenCentral() }
dependencies { implementation("com.soywiz.korlibs.korio:korio-mingwx64:2.20") }

Yet, building the project gives me:
Execution failed for task ':compileKotlinMingwX64'.
> Could not resolve all files for configuration ':mingwX64CompileKlibraries'.
   > Could not find com.soywiz.korlibs.korio:korio-mingwx64:2.20.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/soywiz/korlibs/korio/korio-mingwx64/2.20/korio-mingwx64-2.20.pom
       - https://dl.bintray.com/jetbrains/kotlin-native-dependencies/com/soywiz/korlibs/korio/korio-mingwx64/2.20/korio-mingwx64-2.20.pom
       - https://maven.pkg.github.com/Dominaezzz/kotlin-imgui/com/soywiz/korlibs/korio/korio-mingwx64/2.20/korio-mingwx64-2.20.pom
       - https://maven.pkg.github.com/Dominaezzz/kgl/com/soywiz/korlibs/korio/korio-mingwx64/2.20/korio-mingwx64-2.20.pom

Should have been 2.2.0.

Hi, may I know how did you solve that issue? I bumped into similar issue too.

I had "com.soywiz.korlibs.korio:korio-mingwx64:2.20" in dependencies, instead of "com.soywiz.korlibs.korio:korio-mingwx64:2.2.0".

Also, if you look at the error:
Incompatible abi version. The current default is '1.4.2', found '1.5.0'. The library produced by 1.5.20 compiler

Probably was using an older version of Kotlin and korio 2.2.0 is compiled against Kotlin 1.5.20.
Normally you don't include korio-mingwx64, but korio that has a metadata linking to each supported platform/architecture.


Make Encode a supertrait of EncodeLen

Currently, EncodeLen has the following signature.
pub trait EncodeLen {
    fn encode_len(&self) -> usize;
}

The documentation specifies here that EncodeLen::encode_len is guaranteed to be the amount of bytes written with Encode::encode. The problem lies in that you can have a type implement EncodeLen but not Encode, which makes no sense, because the entire purpose of EncodeLen is to be used with Encode.
This PR simply adds Encode as a supertrait of EncodeLen.

Merged and published in 0.4.0


TEXT_MATCH support for dictionary encoded columns

Currently based on documentation TEXT_MATCH only supports columns encoded as RAW,
Need support for TEXT_MATCH on dictionary encoded columns too, to avoid converting
dictionary encoded columns to RAW.

I can add it.

We should also consider supporting standalone text index (without forward index). This could potentially save a lot of spaces.

@pradeepgv42 , I have merged the support for text index on dictionary encoded columns. Please give it a try and let me know if you face any issues. Thanks

PR https://github.com/apache/incubator-pinot/pull/5667

Thanks a lot, will give it a try and let you know


Installation error

Im getting this issue when installing:

I've pushed an update. Cannot reproduce, need some more details.
Can you tell me:

which MySQL version you are using?
if you have tried php artisan plugin:refresh Adrenth.RssFetcher (CAUTION: this will probably delete some plugin data).
Is the MySQL InnoDB driver installed/present?

~ Alwin

Maria DB 10.0
Yes ive tried and it still gives the same error
yes InnoDB is installed

Hey, thanks for pasting those exceptions, that makes a lot of sense to me. This should be an easy fix :-) My database configuration allows me to have longer keynames.  I have modified the length of the keys, so this issue should be resolved.
Make sure you have installed version 1.0.14.

issue still occrs for me :(

The build of version 1.0.14 was not triggered bij Marketplace. It should be released by now. Please install 1.0.14 which addresses this issue.

im still getting:
SQLSTATE[HY000]: General error: 1709 Index column size too large. The maximum column size is 767 bytes. (SQL: alter table `adrenth_rssfetcher_items` add unique `item_id_unique`(`item_id`))

The index which the migration file is trying to create is named item_id_unique for the column item_id.
This is basic SQL and this is correct:
alter table `adrenth_rssfetcher_items` add unique `item_id_unique`(`item_id`))

This is de PHP code from the migration file:
$table->string('item_id')->unique('item_id_unique'); // VARCHAR(255)

The cause of this issue is that you are using a different collation type on your database than the common utf8. I think you have created the database with a utf8mb4 (4-bytes character size). With utf8 the database uses 3 bytes per character (2553 = 765 bytes). With utf8mb4 collation each character takes up to 4 bytes (2554 = 1020) which exceeds the setting of 767 bytes.
I have changed the length of the fields to 191 characters (4*191=764 bytes). Which should be fine.
This issue is addressed in release 1.0.15. Please let me know if this works for you.
Please rate my plugin if you like it on octobercms.com. Thanks!

still getting:
"SQLSTATE[HY000]: General error: 1005 Can't create table `animezero_db_anime`.`#sql-ea6_331a` (errno: 150 "Foreign key constraint is incorrectly formed") (SQL: alter table `adrenth_rssfetcher_items` add constraint items_source_id_foreign foreign key (`source_id`) references `adrenth_rssfetcher_sources` (`id`) on delete cascade)" on line 666 of


Button on documentation page refreshes the page

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
On https://mui.com/material-ui/react-text-field/ the search icon button right under:

Customization does not stop at CSS. You can use composition to build custom components and give your app a unique feel. Below is an example using the InputBase component, inspired by Google Maps.

Refreshes the page when clicked.
Expected behavior 🤔
Button to have e.preventDefault() or something
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎
No response

@ritwaldev
The fix was actually simple, the type of IconButton was submit and when you click on those submit typed button, the page refreshes.
Just changed the type from submit to button fixed the problem.


fields submitFailed does not change after a submit failed

The state of the form has a property submitFailed that turns true after a submission fails, for example when the form isn't valid, but the same property in the fields remains false.
is this intended? if so, when does the property in the fields turns true?
Thanks in advance.

Yes, this is intended. In v1, any subsection of the fields (i.e., any node) can be submitted as a "form" - that is to say, if you want to submit the entire user or just user.address, you can do so. So the submitFailed only reflects that submission has failed when trying to submit that specific model.
Hope that helps!

Thanks! Yes it helped.


Add uc 08 derive simulation production configuration parameters

This PR adds the functionality defined in UC8 with the following four applications:

simtools-production-calculate-resource-estimates
-- calculates compute and storage resources --

simtools-production-generate-grid
-- generates a grid of simulation points --

simtools-production-generate-simulation-config
-- generates simulation parameters for a specific grid point --

simtools-production-scale-events
-- metric evaluation and statistical error calculations --

Modules are stored in production_configuration:

calculate_statistical_errors_grid_point.py
derive_computing_resources.py
generate_production_grid.py
generate_simulation_config.py
interpolation_handler.py

Would like start the discussions how to best organize the code. At this point most of it is in the applications, but we want to move it into modules.
Suggest to start a module to put those classes in. What would be a good name?

simtools.production_tools (don't like tools, seems to cover everything)
simtools.production_configuration
simtools.simulation_production
...something shorter...?

This module would include all classes currently defined in

simtools/applications/derive_resources.py (which will be renamed to simtools/applications/derive_computing_resources.py
simtools/applications/generate_grid.py (which will be renamed to simtools/applications/generate_production_grid.py)
simtools/applications/generate_simulation_config.py
`simtools/utils/calculate_statistical_errors_grid_point.py (maybe we can find a shorter name)

@orelgueta , @tobiaskleiner : please comment.

Not much for me to comment. This is the first time I see that those modules are in applications and I definitely agree they should go into simtools instead. In terms of which name to put them under, I would vote for simtools.production_configuration.
However, I would also check if we can integrate these classes with the current modules we have (at least partly).

I agree with the simtools.production_configuration suggestion and to move some parts into visualization or in other parts.

@tobiaskleiner -thanks a lot!
Couple of 'technical' comments from browsing once through the code:

in general: we want to have a simple application calling the different classes (more or less what you put into the docstring) for some given input files. No 'main' in the modules (e.g., as in SimulationConfig)
try to avoid too many hard-wired items (e.g., paths, file names)
need to discuss if we use units in general or not (it is generally clearer with units)

calculate_statistical_errors_grid_point

if it possible that 'effective area' is actually trigger efficiency without the multiplication by the scatter area? I at least can't find the scatter area anywhere.
suggest to separate the file into two with one class per file (I think we always have one class per file only)

generate_grid:

lat/long of the observatory should be read from the model parameters for each site (reference_point_latitude and reference_point_longitude)
suggest to discuss how we treat the data levels and their corresponding accuracies; not sure if this should be hardwired or be part of a configuration input (same for high/low precision)

resource_estimates.yaml:

we try not to have any data files in the source code. During operation, we will retrieve this information probably from a database. I suggest for now to move it into "tests/resources" (as we are developing code and use this mostly for testing)
suggest to do minor changes to the format and add a name to the zenith fields (dictionary). If possibly and not too much work, explicit units would be nice (and not encoded in the names)

@tobiaskleiner - before I start the review, could you make sure that the integration tests run successfully?

Running the example production_generate_simulation_config gives:
 python simtools/applications/production_generate_simulation_config.py  --azimuth 60.0 --elevation 45.0 --nsb 0.3 --data_level "A" --science_case "high_precision"  --file_path tests/resources/production_dl2_fits/prod6_LaPalma-20deg_gamma_cone.N.Am-4LSTs09MSTs_ID0_reduced.fits --file_type "On-source" --metrics_file  tests/resources/production_simulation_config_metrics.yaml --site North
Effective Area Error (avg): 0.000, Reference: 0.020
Signal Efficiency Error: 0.020, Reference: 0.020
INFO::calculate_statistical_errors_grid_point(l278)::calculate_error_energy_estimate_bdt_reg_tree::Calculating Energy Resolution Error
Energy Estimate Error: 0.184, Reference: 0.050
Gamma-Ray PSF Error: 0.010, Reference: 0.010
Image Template Methods Error: 0.050, Reference: 0.030
error_eff_area {'relative_errors': array([0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.01799919e-08,
       2.21965306e-08, 3.88179482e-08, 5.76378038e-08, 7.53500614e-08,
       8.98535771e-08, 1.20081083e-07, 1.46732027e-07, 1.66036331e-07,
       2.16994290e-07, 2.42594940e-07, 2.92140457e-07, 3.35214284e-07,
       3.58574316e-07, 4.90549293e-07, 4.77865852e-07, 6.57241537e-07,
       6.62752408e-07, 6.89972899e-07, 1.03031658e-06, 1.26143022e-06,
       1.53338834e-06, 1.47603219e-06, 1.79685160e-06, 2.19451145e-06,
       1.94774912e-06, 3.34303448e-06, 4.51782360e-06, 3.89789862e-06,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00,
       0.00000000e+00, 0.00000000e+00])}
INFO::production_generate_simulation_config(l180)::main::Simulation parameters: {'core_scatter_area': np.float64(200070.0), 'viewcone': np.float64(1053.0), 'number_of_events':<PHONE_NUMBER>4}
INFO::production_generate_simulation_config(l183)::main::Simulation parameters saved to: /workdir/external/simtools/simtools-output/production_generate_simulation_config/configured_simulation_params.json

Is a viewcone of 1053 reasonable? I assume it is in degrees.
Here and throughput the added code: there are no units anywhere. I assume that this output is in the units expected by CORSIKA, but I am not entirely sure. The code also relies on certain units of the values read from the DL2 file, and I think at least there the units are given in the header or table columns. I suggest to use units (as we do not know if DL2 files change in future).

Also surprised how small the error on the effective areas area (same for the values in tests/unit_tests/production_configuration/test_generate_simulation_config.py)

First: great work @tobiaskleiner! This adds an almost complete framework for the configuration.
This PR is unusual big with several independent applications added, all including important . Too late to split it up, but we need to do it in pieces (I will sent a review for the first application out soon).
I have looked until now at production_generate_simulation_config only, which determines the configuration parameters for a single grid point.
Quite a few of the statistics questions are open, including the details of the metrics. I would suggest that you add a small discussion note on this topic into the implementation gitlab (UC8) directory addressing the following question:

what metrics do we want to consider and how are they calculated
how to we determine from the metrics the number of required events
how to you plan to calculate the scatter area and view cone

I think it is easier to discuss the methodical approach there and not as part of the code review. Maybe for future we should discuss the methods before the implementation starts.
Additional, we should discuss the concepts / impact of data level and science cases in with implementation gitlab. I think the science cases are not documented anywhere? What are the assumptions / motivation?

@GernotMaier thanks for the review. I went through the comments and adressed most of them. Few more points need discussion/implementation see #1233, #1227, #1219. Will let you know when I have fixed the unit tests for another review.

@GernotMaier thanks again for the review of the first part of the PR. Went through your comments and fixed the unit/integration tests. I factored out the event scaling logic and added a file for helper functions in the production configuration folder. In there we could also move the dl2 reading part in a later stage.
Let me know if the changes make sense and if so you could start reviewing the other parts of the PR.


Call method quickfix formatting improvement

              CALL METHOD me->blah->blah
                EXPORTING
                  x = 1
                  y = 2
                CHANGING
                  z = 3
                  f = 4.

is fixed to
              me->blah->blah( EXPORTING x = 1
                                        y = 2 CHANGING z = 3 f = 4 ).

abaplint should insert newlines before exporting/changing/receiving/exceptions

I think it should take the old parameters code, so its quick fixed to
              me->blah->blah(
                EXPORTING
                  x = 1
                  y = 2
                CHANGING
                  z = 3
                  f = 4 ).

in a quick fix, there might be a lot of other rules applied or not applied causing the formatting to be changed

I think it should take the old parameters code, so its quick fixed to
              me->blah->blah(
                EXPORTING
                  x = 1
                  y = 2
                CHANGING
                  z = 3
                  f = 4 ).

in a quick fix, there might be a lot of other rules applied or not applied causing the formatting to be changed

https://rules.abaplint.org/functional_writing/

https://rules.abaplint.org/functional_writing/


MSID: 93052 Version: 2 DOI: 10.1101/2<IP_ADDRESS>1185

MSID: 93052
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>1185
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=93052
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1185

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/93052v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>1185
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/93052/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [title-upper-case] Content of <title> element is entirely in upper case: Is that correct? 'STAR METHODS'
warn: [title-upper-case] Content of <title> element is entirely in upper case: Is that correct? 'EXPERIMENTAL MODEL AND SUBJECT DETAILS'
warn: [title-upper-case] Content of <title> element is entirely in upper case: Is that correct? 'QUANTIFICATION AND STATISTICAL ANALYSIS'


Wharton GSR Current Bookings

Example:
{
    "reservations": [
        {
            "booking_id": 100648,
            "date": "Feb 06, 2019",
            "endTime": "9 p.m.",
            "location": "JMHH G61",
            "startTime": "8:30 p.m."
        },
        {
            "booking_id": 100661,
            "date": "Feb 06, 2019",
            "endTime": "10 p.m.",
            "location": "JMHH 378",
            "startTime": "9:30 p.m."
        }
    ]
}

Example with no session ID:
{
    "error": "No Session ID provided."
}

Example with bad session ID:
{
    "error": "Wharton Auth Failed. Session ID is not valid."
}

@ezwang How do we update penn-sdk-python on travis-ci? It's holding up both mine and @evakill's  pull requests.


test(deploy): add tests for deploy command

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

v4.0.0
GitHub release

Your semantic-release bot :package::rocket:


RuntimeError: range of [nan, nan] is not finite

wandb --version && python --version && uname
wandb, version 0.8.31
Python 3.8.2
Linux
Description
When running sweeps, for several runs I get this error:
Traceback (most recent call last):
  File "model.py", line 494, in <module>
    train(**kwargs)
  File "model.py", line 395, in train
    pass  # This comment shows up if we ran into a callback error
  File "/home/marcel/git/model-in-the-loop/mitlmodels/ml_utils.py", line 61, in __exit__
    raise exc_type(exc_val).with_traceback(exc_tb) from None
  File "model.py", line 373, in train
    learn.fit_one_cycle(max_epochs, slice(lr_init, lr_init * 30), wd=wd,
  File "/home/marcel/.local/lib/python3.8/site-packages/fastai/train.py", line 23, in fit_one_cycle
    learn.fit(cyc_len, max_lr, wd=wd, callbacks=callbacks)
  File "/home/marcel/.local/lib/python3.8/site-packages/fastai/basic_train.py", line 200, in fit
    fit(epochs, self, metrics=self.metrics, callbacks=self.callbacks+callbacks)
  File "/home/marcel/.local/lib/python3.8/site-packages/fastai/basic_train.py", line 101, in fit
    loss = loss_batch(learn.model, xb, yb, learn.loss_func, learn.opt, cb_handler)
  File "/home/marcel/.local/lib/python3.8/site-packages/fastai/basic_train.py", line 34, in loss_batch
    if not skip_bwd:                     loss.backward()
  File "/home/marcel/.local/lib/python3.8/site-packages/torch/tensor.py", line 195, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/home/marcel/.local/lib/python3.8/site-packages/torch/autograd/__init__.py", line 97, in backward
    Variable._execution_engine.run_backward(
  File "/home/marcel/.local/lib/python3.8/site-packages/wandb/wandb_torch.py", line 256, in <lambda>
    handle = var.register_hook(lambda grad: _callback(grad, log_track))
  File "/home/marcel/.local/lib/python3.8/site-packages/wandb/wandb_torch.py", line 254, in _callback
    self.log_tensor_stats(grad.data, name)
  File "/home/marcel/.local/lib/python3.8/site-packages/wandb/wandb_torch.py", line 207, in log_tensor_stats
    tensor = flat.histc(bins=self._num_bins, min=tmin, max=tmax)
RuntimeError: range of [nan, nan] is not finite

There are plenty of runs in the same sweep where there's no error at all and everything runs smoothly. It also does not occur consistently for certain configurations.

As a quick fix, try to use WandbCallback(log=None)

Thanks Marcel. @adrnswanberg could you take a look?

@adrnswanberg thanks for fixing this!


Fix the DCP MVP metadata so that additions can happen

#175

not sure what this is.
related issue is closed.
closing


Fix compiler error when running with the new LKG

We can't run pack this until the LKG passes as green,  this is one half of that.
The other which I can't change is to update the baselines for the tsserverlibrary.d.ts:
@ tests/baselines/reference/api/tsserverlibrary.d.ts:8525 @ declare namespace ts.server {
        static resolveModule(moduleName: string, initialDir: string, host: ServerHost, log: (message: string) => void, logErrors?: (message: string) => void): {} | undefined;
        isKnownTypesPackageName(name: string): boolean;
        installPackage(options: InstallPackageOptions): Promise<ApplyCodeActionCommandResult>;
-        private readonly typingsCache;
+        private get typingsCache();
        getCompilationSettings(): CompilerOptions;
        getCompilerOptions(): CompilerOptions;

Which can't pass on both the current LKG, and a potential update to the LKG.

Closing this PR, someone will be updating the LKG today anyway and they can do all of it then 👍


Backport 1.0 - Add cluster setting to spoof version number returned from MainResponse (#847)

Backport of #847 into 1.0 branch.
This change adds a new cluster setting "compatibility.override_main_response_version"
that when enabled spoofs the version.number returned from MainResponse
for REST clients expecting legacy version 7.10.2.
Signed-off-by: Marc Handalian<EMAIL_ADDRESS>Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing PR... will cherry-pick from 1.x.

cherry picked in https://github.com/opensearch-project/OpenSearch/commit/9891ecbb403007c53e75e2cd88b1cbc76e2c6fda


rename config post_body_formatter to be request_body_formatter

Allow legacy configuration post_body_formatter
in response to issue https://github.com/zipmark/rspec_api_documentation/issues/243

Looks good. Sorry for taking a while to get to this. Thanks!


[BUG] Fix simple documentation bug

The section "Running the test suite" was labeled as _run_tests although the references are to _run-tests. For some reason, the _run_tests reference points to a similar section in the documentation of statsmodels. This glorious one-character PR fixes the bug and the link now works correctly.
I skipped the changelog entry for this tiny thing.

thx @ruuskas


feat: add sorting visualizer lab to cert

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 #56800

Replacement for #56800

I think we want to change the challengeType to 25 here. See PR


BREAKING(web-sys): Remove support for CanvasRenderingContext2D and BufferSource from createImageBitmap

Resolves #3227
Both APIs are broken, to some extent, which is why I think it makes sense to remove them despite the potential breakage.
Calling createImageBitmap with a BufferSource will instantly throw an error, and calling it with a CanvasRenderingContext2D will also fail except in Firefox, where it gives a deprecation warning.
BufferSource was there as part of the abandoned video capture worker API (https://w3c.github.io/mediacapture-worker). It looks like we inherited it from Firefox, which supported it behind a flag at the time we copied our WebIDL from it but later removed it. I also removed the rest of that API while I was at it.
CanvasRenderingContext2D is there because, for whatever reason, Firefox non-standardly accepts it in createImageBitmap, and we took our WebIDL from them. It's deprecated, and https://bugzilla.mozilla.org/show_bug.cgi?id=1500782 talks about removing it, but it hasn't been done yet.

Sounds reasonable to me, thanks!


How can I add a custom command option for rspec --order like rspec --order prioritized

Hey,
I am working on a gem to prioritize specs in a specific order and just realized that calling rspec path_1 path_2 path_3 applies the preset ordering to path_1, path_2, path_3 instead of running it in passed order.
So I was wondering how can I achieve this the easiest way.
As far as I know by now I would have to use register_ordering and looked at some example for that. So far so good, but how would I add an option to use my newly defined order from command line?
Thanks!

In short, you can't. Currently you can configure the ordering globally, or define a strategy to tag examples with.
However I was surprised that this didn't just work, so I fixed it, #3025 will allow custom ordering via the CLI in a future version. Closing in favour of #3025, please see if that will suit your use case.

@JonRowe Ok thank you!!


Revert "Support error reporting via napari-error-monitor"

Reverts napari/napari#4040

see discussion in #4040


Add RISE: EverRise

[x] I understand that token listing is not required to use the Polygon Wallet with a token.

Please provide the following information for your token.
Token Name: EverRise
Token Symbol: RISE
Decimals: 18
Polygon Address: 0x0cD022ddE27169b20895e0e2B2B8A33B25e63579
Ethereum Address: 0x0cD022ddE27169b20895e0e2B2B8A33B25e63579
Logo URI: https://data.everrise.com/icons/polygon/0x0cd022dde27169b20895e0e2b2b8a33b25e63579.png
Project Name: EverRise
Project Summary: EverRise is a blockchain technology company focused on increasing accessibility to decentralized finance by bringing security and multi-chain solutions to the space through an innovative ecosystem of decentralized applications.
The EverRise Token (RISE), the original buyback token, is a multi-chain collateralized cryptocurrency that serves as a utility token for cross-chain transfers and protects both the ecosystem and investors with its innovative Buyback and Staking protocol.
Project Contact<EMAIL_ADDRESS>Project Website: https://www.everrise.com/
Mainnet: https://polygonscan.com/token/0x0cD022ddE27169b20895e0e2B2B8A33B25e63579

This token is not mapped on Polygon Mainnet. Please go through the below docs and raise a mapping request.
https://docs.polygon.technology/docs/develop/ethereum-polygon/submit-mapping-request/


example setup

IS there an example setup somewhere (that runs straight away?)

https://github.com/spiral/roadrunner/wiki/PHP-Workers

So I save this:
http:
  address:    <IP_ADDRESS>:8080
  workers:
    command:  "php psr-worker.php"
    pool:
      numWorkers: 4

in .rr.yaml, right?
then I start rr (on Windows), but it still give me the same help.

rr have set of sub-commands serve is one you want, so rr serve. In order to see more debug info rr serve -v -d

You can read more about server commands here: https://github.com/spiral/roadrunner/wiki/Server-Commands

command:  "php psr-worker.php" does not work for me, because I have no php in my path,
so I want to use the exact location where it php is installed.
Then it gives me an error:
WARN[0000] config: While parsing config: yaml: line 4: found unknown escape character
so I changed all backslashes into forward slashes, but now it gives me:
RRO[0000] [http]: unable to connect to worker: unexpected response, header is missing: exit status 1

Sounds like you have invalid characters in your yaml (this format is very picky about indents), try json:
{
  "http": {
    "address": "<IP_ADDRESS>:8080",
    "workers": {
      "command": "path-to-php/php psr-worker.php",
      "pool": {
        "numWorkers": 4
      }
    }
  }
}

If you still get an error, try to invoke your php script manually and see what happen:
php psr-worker.php

It should not die and must wait.

Ok, was missing the psr-worker.php.
Now it complains about not having a vendor folder....
Nothing states a composer action.... hmmm... now what to do?

Composer action is first in a list, please check how to install and configure composer here: https://getcomposer.org/download/

hmm.. missed that (it was on top of page, sorry)
Now it works without any messages  (except the hello world)
Thanx for the patience

NP :)


Update to Quarkus 1.0.0-CR2 and regen

ok to test

ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/421/


Spelling Corrections.

Fixed the spellings across multiple files.

nice! did you you anything to check for the spelling or you do it manually

check

Combination - tool (WebStorm) to identify misspelled words, manual (open every file) to check the code.


Unable to grant owner access to User members

I couldn't able to add new member in GCP(iam) with the role owner using the gcloud command The below command fails:
gcloud projects add-iam-policy-binding linuxacademy-3 --member<EMAIL_ADDRESS>--role roles/owner
With the below Error:
ERROR: (gcloud.projects.add-iam-policy-binding) INVALID_ARGUMENT: Request contains an invalid argument.
- '@type': type.googleapis.com/google.cloudresourcemanager.v1.ProjectIamPolicyError
  member<EMAIL_ADDRESS>  role: roles/owner
  type: SOLO_MUST_INVITE_OWNERS

But, the same command works well for other roles like: viewer, browser...! It just doesn't work for "owner". Is there any alternative for this; if yes, How to add this in my Python Code. Please help me here..!
Thank you!
Regards,
Rohith

Awaiting credentials from Google for GSuite so I can confirm the issue.

Experiencing the same issue assigning role\owner. Please advise if a workaround is available.
Thanks.

Assigned to @crwilcox at the behest of @JustinBeckwith

I get the same behavior... Is it confirmed that this behavior is unintended? If it is intended - why?
Thanks

@rohithmn3, @lucasbrynte
It looks like this behavior is intended. The documentation says that it is not possible to grant he owner role through gcloud  or the Cloud IAM API. Owners can only be added through the GCP Console.


Support arrays in tuples

Example:
let b: { int, int[5] };

currently errors out with
Error: compiler internal error: non-fixed array size found in scalarize_array()
   ╭─[sha256.pnt:1:15]
   │
 1 │ let b: { int, int[5] };
   │               ───┬──
   │                  ╰──── non-fixed array size found in scalarize_array()

Works now.


Consider providing Typescript definitions

+1

Is there a typescript version of json-schema?  Not understanding what the
benefit would be. Can one of you allude to what the change would be?
On Jun 3, 2016 6:17 AM, "Renaud Hébert-Legault"<EMAIL_ADDRESS>wrote:

+1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jdorn/json-editor/issues/590#issuecomment-223575965,
or mute the thread
https://github.com/notifications/unsubscribe/AH4Ql5Dpj9hTFT0GguCrr6TlwzslaOlLks5qIClrgaJpZM4IOWze
.

In order to directly reference javascript libraries in typescript you provide essentially interfaces that ahow every method and property and their appropriate type. That ends up providing autocompletion and warnings when things arent done correctly. Alternatively you can cast to ANY but you lose typescript benefits.

+1

So far I can say TypeScript is the best extension for JavaScript. And it would be great if you could provide a TypeDefinition File for your JSON Editor


Certificate for www.auroraoss.com invalid

Hi. I realise that https://auroraoss.com/ is your canonical domain. Nonetheless I accidentally typed to visit https://www.auroraoss.com/ and got a browser warning that the certificate is invalid. Hopefully this is an easy fix! Thanks for reading.

I didn't quite get this. Are you saying we should redirect www.auroraoss.com to auroraoss.com or something similar?

I'll have a chat with our server boi, thnx for the heads up!

Should be fixed now. If it isn't working just yet, wait for a few hours maybe or clear your cache (or if you added exception for www., remove it).

Looks good to me. Thanks!


[Bug] No sound using docker @ catalina (OSX)

Current Behavior
The browser renders video nicely (a bit heavy) but no sound can be heared. All permissions (also to media and audio) are granted.
Expected Behavior
Sound coming from a media (like a video) should be heared clearly once started.

From the logs I can see the service pulseaudio (in the linux container) is disabled. So how can this pulseaudio be activated in the docker-compose.yml file please?

Make sure that WEB_AUDIO environment variable is set to 1. See https://github.com/jlesage/docker-firefox?tab=readme-ov-file#environment-variables for more details.

Closing this issue. Please re-open if needed.


Support existing Cloudfront distributions

The plugin currently expects a logical name for distribution in the config. It would be great to also support preexisting cloudfront distribution.
Benefits:

integrates better for people working with other infrastructure as code tools, such as terraform.
can help speed up deployments since cloudfront usually takes more than 20 minutes to provision.
allows for keeping the buckets and other resources in different regions (lambda@edge needs to be in us-east-1 and serverless doesn't support multi-region deployments as far as I know)

Easy fix would be accepting a cloudfront id or arn as well.

I suggest you always search issues for a project before opening a new one. For example, a search for "existing" would've netted you some very detailed responses that clearly explain why your request can't be supported, and provide alternatives.
Remember, every minute open source maintainers are responding to "the same question, yet again" is a minute that we're not writing the software you know and love 😉

Got it :+1: Will do. Thanks

Interesting. Hadn't considered it from that angle. Thanks @ChristophP!


Adda const_definition function to the trait

For simple types, this would return the same thing as const_type. For structs and enums, this would return the entire definition of the type. This would allow types to be generated in build.rs without the need to be explicitly defined redundantly.

This is done.


Installation of bricknil and dependencies on Gentoo Linux

Hi,
at first many thanks for publishing this project.
I have created install scripts (ebuilds) to install bricknil and dependencies on Gentoo Linux.
I tried a first example with the Lego Boost movehub succesfully.
Hopfully I find some time to experiment with the Control+ stuff.
The ebuilds can be found here:
https://github.com/justxi/bricks

I am currently using the fork https://github.com/janvrany/bricknil.
Gentoo ebuilds are also available for that.


WIP: Port WirePattern to Process API

Since we have the Process API now, it would solve a lot of WirePattern issues to make it actually just a "configurator" for Process API.

[x] Make all "normal" WirePattern cases to be handled by Process API
[x] Mark the more esoteric features (group, field, postpone/resume etc) deprecated and fall back to legacy WirePattern
[ ] Ensure Process API supports addressable ports correctly
[ ] Make Process API de-duplicate brackets when forwarding from multiple ports

There are several WirePattern issues to consider:

Addressable port in WirePattern behaves incorrectly when receiving IP from another component #252
WirePattern duplicate groups on output #269
WirePattern doesn't obey arrayPolicy "any" #275
WirePattern doesn't forward groups correctly when edges to in-port and param-port are both async #276
Weird doc string in wirepattern #281
Exception: OUT Socket ID required #293
Network shutdown may cause WirePattern to fire again #470
WirePattern adds group on error outports #485
WirePattern does not respect required: false #490

I think group and field are not really esoteric. They were one of the original reasons for WirePattern to emerge.

@trustmaster I know, but they're a little difficult to implement without reading packets from buffer in different order they were added in

@bergie yep, and that's one of the reasons I decided to fix&deprecate WirePattern rather than port it onto Process API back in June.

OK, with the current state the only failing tests are related to group de-duplication and arrayport handling. Looking pretty promising.

Now only failing on dupe groups (when we forward < a < b from in1 and same < a <b from in2 you get < a < b < a < b)

Why all the changes to the tests in spec/Helpers.coffee?

@jonnor couple of reasons:

Some tests were reusing same component instance across different WirePattern setups, which doesn't work with Process API
Cleaned some test interdependencies (using proper before/after etc)
Added async/sync versions of some tests to verify correctness in both modes
Some tests were kind of wrong (doing async things in sync wirepattern) that only worked because WirePattern didn't actually care

Some tests were kind of wrong (doing async things in sync wirepattern) that only worked because WirePattern didn't actually care.
There will very likely be components like these in the wild, especially since async is opt-in.

In general we're very likely to have components, graphs and programs, which rely on WirePattern "bugs" to function correctly. This makes me very skeptical to forcing use of this new WirePattern implementation. I think we should at least add a way to opt-out, "give me the old WirePattern". Ideally settable for a whole process (for instance via envvar, module-level variable), so one can quickly test whether old/new WirePattern is cause of behavior changes. And per-component, so that one can isolate only the broken component.

Legacy mode is indeed pretty easy to add since we already have fallback logic in place for couple of the options (group, field) we didn't add Process API support for yet

OK, now we should be essentially complete. No fallbacks except if you enable them manually, either with:

Passing a legacy: true to WirePattern
Setting the NOFLO_WIREPATTERN_LEGACY env var


Blog: Week 35 (August 30th - September 3rd)

This amends Week 34 to include all release notes from PRs.

Thanks, I've updated the previous week to include all release notes from the PRs.


Better accessibility for reveal

I enhanced the accessibility of reveal based on this issue #6572.

:+1:
We should probably include an accessibility writeup in the doc and a focus-eater extension to the js.
As @gerardkcohen said, changing the <a> to a <button> is important. I am able to take a look at the SASS if need be.

Hey guys! This is awesome, we'd love to pull it own and start testing, would you consider this complete?

Yes, based on the feedback from #6572 I'd consider this as a valid solution.

Yeah, I think this should work. I would write up a bit about how to make an accessible modal and link to some sites, but the code should work.
(I only have Voiceover to test with)

Since there seems to not be much more happening in here, I will just close the PR.

Can you re-open this? We have an accessible modal for Foundation 6 but would be awesome to have it for 5. We have time to test it an merge it now. Thanks!

Reference https://github.com/zurb/foundation/issues/6579

Hi,

Hi, nothing happend here for a while so I closed this PR.
Unfortunately it seems that I closed it again by accident just now...
However, I reopen it so you can use it for Foundation 5.
If there is anything to do for Foundation 6 regarding accessibility I'd be happy to help as well.

:+1: what's the status of this?

Thanks for the PR and comments!
@Owlbertz shoot me an email so we can get you on the Foundation 6 private release!


toast notification functionality for Read Docs in Banner component.

This feature utilizes React Toastify to display a brief notification when the "Read Docs" button is clicked, informing users that the documentation is currently under development.
Here is the screenshoot :

Steps to Remove Notification Functionality:

Remove the import statements for ToastContainer and toast and its Css.
Delete the line.
Remove the div wrapping the ReadDocsButton that contains the onClick handler.

fixes - #6

@mayankmehta19032003 can you display the same popup/alert when user clicks Get Started ?

Add notification on Get started also now its working on both Read Docs and  Get started .

@mayankmehta19032003 Thanks ! Everything looks good to me 👍


⚠ Secret Website 3 has degraded performance

In b7e0937, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2201 ms

Resolved: Secret Website 3 performance has improved in 4137f5d.


Remove duplicate Config listings

Good spot, thanks – although already removed in main. (A copy/pasta error – I think I've removed all the duplicates now!)


[ENH] Switched to requesting available terms for diagnosis and assessment tool from API

Closes #261

Changes proposed in this pull request:

Removed the hardcoded options for diagnosis and assessment tool
Switched to requesting available terms for diagnosis and assessment tool from API
Sorted categorical options since the assessment tool terms included a mix of lowercase and uppercase labels
Implemented logic to display a message when the diagnosis and assessment tool options are not retrieved

Checklist

[x] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see https://neurobagel.org/contributing/pull_requests for more info)
[x] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

oh, and please check that all is still happy and running after resolving the merge conflicts


[WFLY-17739] Remove uses of deprecated AbstractRemoveStepHandler methods

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

A bunch of ci.wildfly.org jobs blew up for environmental reasons, but the two that didn't had what look like related failures, which I'll need to sort.

/retest


net/http: accept cookies with space in the name

Hello,
net/http does not allow space in cookie name. That's what the RFC mandates unfortunately broken web applications set cookies with names containing a space.
Repro: http://play.golang.org/p/MhiJ2KKFqA
I see we're already flexible for values, so maybe we can be flexible for names too?
CL: https://go-review.googlesource.com/#/c/11863/
Thanks.

Dealing with cookies from malformed web applications is always possible by manually processing the {Set,}Cookie header. This is painful as one has to reimplement the functionalities of net/http's cookie handling. But as it is doable there is no fundamental need weaken the standard library.
IMHO there is a qualitative difference between malformed values and malformed names (e.g. almost no programming language allows names with spaces). The malformed values were allowed because such values are very common and work on all major browsers (with appropriate quoting). E.g. not all values are allowed, bytes with the high bit set are considered invalid (even if Firefox handles UTF-8 encoded cookie values very well) because they are not that common in the wwild.
I didn't think it through, but I could imagine that allowing spaces in names could produce parsing ambiguities. So please no.

True, it can be re-implemented locally. In that particular case (Google Bug 22245291) I'm also hoping to get the application fixed.
--

The malformed values were allowed because such values are very common

Where did we get the data that space in values was very common? can we check if space in name is common as well?
I think it would help us make a informed decision:

if it's as common as a space in value, maybe balance in favor of consistency and allow it
if it's less common as a space in value, maybe balance in favor of rejecting it

--

and work on all major browsers

Space in cookie name works with Chrome 43. I also checked, it works in Firefox 38 and IE 11. If following major browsers implementation was an argument in the previous decision, maybe balance in favor of consistency and allow it.
--

I could imagine that allowing spaces in names could produce parsing ambiguities

Name and value are separated with = so I don't see why space would create an ambiguity but maybe, do you have any example?
There's also the case of spaces at the beginning or end but I think we can just trim, like the major browsers do.

Where did we get the data that space in values was very common? can we check if space in name is common as well?

This was not a scientific statistic evaluation.

Space in cookie name works with Chrome 43. I also checked, it works in Firefox 38 and IE 11. If following major browsers implementation was an argument in the previous decision, maybe balance in favor of consistency and allow it.

No, this statement is misleading. If any major browsers (and curl) wouldn't be able to handle spaces in cookie values Go probably wouldn't have allowed them. The support in major browsers works just in one direction: "No complete support in browser" ==> "No support in Go" cannot be reverted to state "Major browser support" ==> "Go should support it too."

Does anybody want to argue for this with data? Otherwise I'm inclined to close the bug.

Please close away.
On 25 September 2015 at 04:13, Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

Does anybody want to argue for this with data? Otherwise I'm inclined to
close the bug.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/11519#issuecomment-143008398.


feat(snippetz): migrate and deploy snippetz playground

Currently, we don't have a playground example for the @scalar/snippetz package in the monorepo.
This PR migrates the old snippetz demo, containerizes, and deploys it.

wow much bundle savings

AWESOME! Is that deployed already, what's the URL?

It will be deployed by cloud build on merge! I can give you the url then 😄

wow much bundle savings

This seems to have been saved in the lockfile??


Failed to run mediapipe with gpu support for Facemesh solution with refine landmarks

I built mediapipe facemesh example with gpu support on jetson platform using the reference of the markdown file provided in the following link -
https://forums.developer.nvidia.com/t/mediapipe/121120/36
and also with reference to this git repository -
https://github.com/jiuqiant/mediapipe_python_aarch64
The example is working fine on GPU without setting the refine_landmarks parameter as True.
And it is working fine on CPU with and without setting refine_landmarks parameter as True.
Error on running mediapipe facemesh example on gpu with refine_landmarks set as True

System information

Jetson Xavier AGX
Jetpack version - 4.5
Mediapipe version - 0.8
Programming language - Python (3.6.9)
Bazel version - 3.7.2

it's good that the GPU path works for facemesh when refine_landmarks is false, that means the mediapipe GPU configuration/setup is fine.
the refine_landmarks = true option actually runs a different ML model (here)
it seems that model has some op that isn't compatible with the tensorflow gpu delegate.
since https://github.com/google/mediapipe/issues/2797 has the same issue and seems to be using only c++, it is unlikely a python issue.
i'm suspecting some mismatch with the model file and tensorflow version.  it may be that a newer tflite runtime is needed (changed [here](https://github.com/google/mediapipe/issues/2797 seems to be using c++,)).
maybe you can try using a snapshot of tensorflow that is closer to the release date of refine_landmarks (Oct 06, 2021)..?

Hi @Dreadlocke1984, Could you please respond on this https://github.com/google/mediapipe/issues/2678#issuecomment-989348636. if the issue still persists

if there is a
use_advanced_gpu_api: true
in the graph, try setting it to false.
see https://github.com/google/mediapipe/pull/2463

if there is a use_advanced_gpu_api: true in any of the graphs, try setting it to false. see #2463

Thanks for the reply brother @mcclanahoochie
there is no  use_advanced_gpu_api: true in any graph, I assume this option is in the inference calculator right?
for the reference.
face_landmark_gpu.pbtxt
# Runs a TensorFlow Lite model on GPU that takes an image tensor and outputs a
# vector of GPU tensors representing, for instance, detection boxes/keypoints
# and scores.
node {
  calculator: "InferenceCalculator"
  input_stream: "TENSORS:input_tensors"
  input_side_packet: "MODEL:model"
  input_side_packet: "CUSTOM_OP_RESOLVER:op_resolver"
  output_stream: "TENSORS:output_tensors"
  options: {
    [mediapipe.InferenceCalculatorOptions.ext] {
      # Do not remove. Used for generation of XNNPACK/NNAPI graphs.
    }
  }
}

can you suggest any other solution?


Replace internal ncp usage with fs-extra and ensure files are writable before writing

This change allows nativefier to build apps even if nativefier's files are readonly.
Partially fixes #977. Although the application now builds in nixos, it refuses to run. That is, nativefier <website> completes without errors but the binary produced doesnt run (reports no such file or directory). Generally, binaries built for FHS compliant distributions wouldn't work on nixos as binaries are not located at /usr/bin. I suspect that one of the dependencies (perhaps election-packer) is the cause of this issue. I believe that wrapping the produced build using buildFHSUserEnv would work, however I am yet to test that.

Before, I do understand your concern and I was really excited to see when the build first completed, I was immediately let down by the fact that wouldn't run. Anyhow, each of the concerns in order:

Yes, but not quite. This PR would fix builds if nativefier is installed using Nix. If the system is running Nix on top of a FHS distribution, the produced build should work (build refers to the website wrapped in electron). Furthermore, this PR would take one step towards using nativefier on Nixos (nix only system). Again, I think the issue is with electron-packager and using a tool in Nix called buildFHSUserEnv, it should be able to make it work (this tool is often used for proprietary programs which we can't inform the proper locations of dependencies)

From my understanding of the code Lines 146-175 and testing, ncp is unable to copy a directory if it is read only as it first sets the permissions on the directory then attempts to populate it (which would fail). In contrast, fs-extra is able to copy read only directories however it preserves its permissions Lines 152-160. Therefore, when using fs-extra.copy, it is necessary to set the permissions to writeable before writing or creating any file (perhaps 700 is the wrong mode, I want to make changes). With respect to using chmod in conjunction with ncp, it is infeasible as you would have to change permissions on the source which you wont own (root) in order for the copy to succeed then change the permissions back after the copy is done.

I understand this too. How do you feel if I create a directory called scripts which would contain a javascript file (called build-app-static) which would be called upon instead of ncp? I believe it should work as it would be almost identical to how ncp works. The file would just contain three lines (perhaps more to report errors) to perform the necessary copies using fs-extra.

@hqurve

[...] this PR would take one step towards using nativefier on Nixos

Okay.

[...] When using fs-extra.copy, it is necessary to set the permissions to writeable before writing or creating any file (perhaps 700 is the wrong mode, I want to make changes).

Okay. Pls do a bit of spelunking around and testing in a non-Nix Linux to see what the best mode is, how close it is to current behavior, and if diverging, if it'll break other usage.

How do you feel if I create a directory called scripts which would contain a javascript file (called build-app-static) which would be called upon instead of ncp? I believe it should work as it would be almost identical to how ncp works. The file would just contain three lines (perhaps more to report errors) to perform the necessary copies using fs-extra.

Okay. Nit: to keep our folder structure simple for approach-ability to new contributors, I don't like too many folders in the root of the project, especially when they contain just one or two files. Instead of putting your new build-app-static in a new scripts folder, pls just shove it in our .github folder. I know this has nothing to do with GitHub, but we use this folder (which is necessary anyway for github stuff) as dumping ground for a couple other things that don't fit elsewhere.
And of course, pls remove the ncp & @types/ncp dependencies from package.json
Thanks!

Okay, I set the mode to 755 (read and execute for anyone, but the owner can write). Also, I realized that many different files/directories could be written (for example inject) so for the easy of maintaining, I scanned the entire file tree and make it writable.

Could you please explain to me why the tests are failing. Locally, they all pass but here, the errors include

    expect(received).toEqual(expected) // deep equality

    Expected: {"test": 456}
    Received: "{\"test\": 456}"

      199 |   test.each([
      200 |     { arg: 'always-on-top', shortArg: '' },
    > 201 |     { arg: 'block-external-urls', shortArg: '' },
          |            ^
      202 |     { arg: 'bounce', shortArg: '' },
      203 |     { arg: 'clear-cache', shortArg: '' },
      204 |     { arg: 'conceal', shortArg: 'c' },

      at src/cli.test.ts:201:12
      ```
From what I could tell, the expected is `JSON.stringify({"test": 456})` while the receeved is `JSON.stringify(JSON.stringify({"test": 456}))`. Can you explain why this is happenning? should I rebase?

Closing as abandoned. If you find a solution to the latest trouble trouble you had, feel free to rebase and add a comment, and I'll be happy to re-review.


Feature/dockerbuilds

Added docker container for Jenkinsfiles as build option, modified the files to run steps only when the repository was changed

Wrong base branch selected


Rendu Switch with CodeAstText

$sb={
    Switch ($Grade)
    {
        {$grade -ge 90} { "Grade A";Break}
        {$grade -ge 80} { "Grade B";Break}
        {$grade -ge 70} { "Grade C";Break}
        {$grade -ge 60} { "Grade D";Break}
        default { "Grade F" }
    }
}

Find-FlowChart -scriptblock $sb | New-FlowChartGraph -CodeAsText
gives:
digraph "a" {
}

wich seems pretty wrong to me... !

GenerateGraph Method was missing for SwitchNode


Fix attach/detach test

What does this PR do?
Add similar tests like yorkie-team/yorkie#111
What are the relevant tickets?
This test is for #111
Checklist

[x] Added relevant tests
[x] Didn't break anything

Pull Request Test Coverage Report for Build 453789210

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 77.605%

Totals

Change from base Build 453785048:
0.0%

Covered Lines:
2003

Relevant Lines:
2511

💛  - Coveralls


Info

Hello, I would like to know if there is some form of the file not being decrypted ...
Because currently with GameGuardian it is possible to see the code again.
Is there any way not to do that?

May be you need ELGGByRevo (Encrypt Lua GG By Revo).
That's a Lua script to encrypt lua script. But it's not opensource. The release is encrypted by itself.


Nanoc::Spec::HelperHelper introduced an ordering requirement in 990d6963

By making @items immutable in https://github.com/nanoc/nanoc/commit/990d696398202886d8dfa5891ad6e725f74d2150#diff-4a5a2171683f37ed95183db55a9b2e97L34, an item created in a test context does not see future created items. (By "see" I mean the first item's @context.items includes only itself, the second item's @context.items includes the first and itself, etc.)
Steps to reproduce

Create a test.rbrequire 'nanoc'
require 'nanoc/spec'

class TestMe
  def described_class
    self.class
  end

  include Nanoc::Spec::HelperHelper

  def doit
    first = ctx.create_item('item', {}, '/index.html')
    second = ctx.create_item('item2', {}, '/index2.html')

    puts Nanoc::VERSION
    puts first.instance_variable_get(:@context).items.size
    puts second.instance_variable_get(:@context).items.size
  end
end

TestMe.new.doit

ruby test.rb with 4.6.1 or 4.6.2 installed.

Expected behavior
Output:
4.6.2
2
2

(First item does know about the second item)
Actual behavior
When run with 4.6.2:
4.6.2
1
2

(First item doesn't know about the second item)
When run with 4.6.1:
4.6.1
2
2

(First item does know about the second item)
Details
I use Spec::HelperHelper extensively to simulate different items before running tests. For example I create two items and call a method on the first (the rspec subject). With nanoc 4.6.2 the item's context will not include other items created after the subject.

Yeah, this one’s tricky to solve while keeping the API the same. I propose changing the API so you can do
ctx.create_item('item', {}, '/index.html')
ctx.create_item('item2', {}, '/index2.html')

first = items['/index.html']
second = first = items['/index2.html']

I like the idea of create_item not modifying the context, so I’d like to keep it that way.

Any functional programmer likes immutability. Unfortunately it's not Ruby's strong side, but that's why there is Elixir. Unfortunately, Elixir does not have nanoc ;-)
I'm not sure mixing both styles is beneficial here. Perhaps we need a special mutable collection for testing (and use the one deprived of :<< in production).
Also, what about ctx returning a new context?
ctx.create_item(...)
   .create_item(...)

ctx.items['/index.html'] # This is the point there the item is created with both items in its collection

I assume you mean something like this:
ctx = ctx.create_item(…)

ctx.items['/index.html']

otherwise, you’d still be modifying ctx!
I’m okay with code that mutates objects, as long as it’s explicit in doing so. The old #create_items implementation wasn’t explicit in its mutation, and that’s one of the reason why it broke.
I have a slight preference for the API that has mutation, because it’s simpler.

What I meant is that ctx.create_item returns a modified copy of itself.
ctx.create_item() # creates a copy of ctx (#1)
   .create_item() # creates copy #2, which has all modifications of #1

This way the original ctx remains untouched, and #1 contains only the first item, and #2 contains the first and the second item.

I don’t feel that a purely function approach buys us much, and it makes things more complicated. This is especially true in tests, where the amount of set-up logic is typically small and straightforward.
I like your idea of chaining, though. Perhaps this could work:
ctx
  .create_item(…)
  .create_item(…)

first = ctx.items['/first.html']
second = ctx.items['/second.html']

If, for some reason, having a mutable ctx is not desired or not an option, it’s always possible to create a separate one that will not be mutated, with HelperContext.new.

A potential fix is in #1112.

I'm still in the middle of adjusting my specs, but this looks good to me. Even made the specs a bit clearer!

👍 Thank you!