Add Catalan language

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: #4312
Other information
This will add Catalan to the list of supported languages.

Thanks!


How do I download the mod

I've tried downloading the artifacts for some of the versions found in Actions, it tells that It's expired. I wanted to ask this question in the discord server, but the link appears to be expired.

Go to our fabric repository and join the discord via the url you will find there :)


The New Designer does not parse desired outputs from content envelope

Describe the Bug with repro steps
In the previous version of the designer, the content envelope containing the base64 encoded version of the desired output was decoded and displayed in the output monitor for the designer, which is not the case anymore.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using Preview Designer or GA Designer
Preview
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
Output received from API call:
{
"statusCode": "OK",
"body": {
"content": {
"$content-type": "application/xml",
"$content": "PENSRUFURVJlc3BvbnNlIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL0JhcGkvQlVTMTAxMS8iPjxCQU5LQ09VTlRSWT48L0JBTktDT1VOVFJZPjxCQU5LS0VZPjwvQkFOS0tFWT48UkVUVVJOPjxUWVBFIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPkU8L1RZUEU+PElEIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPkFSPC9JRD48TlVNQkVSIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPjEwNDwvTlVNQkVSPjxNRVNTQUdFIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPkJhbmsgS2V5IGFhIG11c3QgY29udGFpbiBvbmx5IG51bWJlcnM8L01FU1NBR0U+PExPR19OTyB4bWxucz0iaHR0cDovL01pY3Jvc29mdC5Mb2JTZXJ2aWNlcy5TYXAvMjAwNy8wMy9UeXBlcy9SZmMvIj48L0xPR19OTz48TE9HX01TR19OTyB4bWxucz0iaHR0cDovL01pY3Jvc29mdC5Mb2JTZXJ2aWNlcy5TYXAvMjAwNy8wMy9UeXBlcy9SZmMvIj4wMDAwMDA8L0xPR19NU0dfTk8+PE1FU1NBR0VfVjEgeG1sbnM9Imh0dHA6Ly9NaWNyb3NvZnQuTG9iU2VydmljZXMuU2FwLzIwMDcvMDMvVHlwZXMvUmZjLyI+QmFuayBLZXk8L01FU1NBR0VfVjE+PE1FU1NBR0VfVjIgeG1sbnM9Imh0dHA6Ly9NaWNyb3NvZnQuTG9iU2VydmljZXMuU2FwLzIwMDcvMDMvVHlwZXMvUmZjLyI+YWE8L01FU1NBR0VfVjI+PE1FU1NBR0VfVjMgeG1sbnM9Imh0dHA6Ly9NaWNyb3NvZnQuTG9iU2VydmljZXMuU2FwLzIwMDcvMDMvVHlwZXMvUmZjLyI+PC9NRVNTQUdFX1YzPjxNRVNTQUdFX1Y0IHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPjwvTUVTU0FHRV9WND48UEFSQU1FVEVSIHhtbG5zPSJodHRwOi8vTWljcm9zb2Z0LkxvYlNlcnZpY2VzLlNhcC8yMDA3LzAzL1R5cGVzL1JmYy8iPjwvUEFSQU1FVEVSPjxST1cgeG1sbnM9Imh0dHA6Ly9NaWNyb3NvZnQuTG9iU2VydmljZXMuU2FwLzIwMDcvMDMvVHlwZXMvUmZjLyI+MDwvUk9XPjxGSUVMRCB4bWxucz0iaHR0cDovL01pY3Jvc29mdC5Mb2JTZXJ2aWNlcy5TYXAvMjAwNy8wMy9UeXBlcy9SZmMvIj48L0ZJRUxEPjxTWVNURU0geG1sbnM9Imh0dHA6Ly9NaWNyb3NvZnQuTG9iU2VydmljZXMuU2FwLzIwMDcvMDMvVHlwZXMvUmZjLyI+TE9HSUNBUFBTPC9TWVNURU0+PC9SRVRVUk4+PC9DUkVBVEVSZXNwb25zZT4="
}
}
}
Expected Behavior:

Actual Behaviour:

Browser
Edge
Additional context
No response
AB#24244819

@ccastrotrejo as discussed, thanks.


Slack announcement for Figma v11 All themes Beta

Create a Slack announcement and push to the appropriate channels to surface the v11 All themes Beta library.
Use the Slack blast used for C4IP announcements.

Linda already announced this!


Is there a reason why var is used instead of const in the whole project?

It's not a big change but it could add a little bit to the intent of the code.

@nicu-chiciuc See: https://github.com/hyperapp/hyperapp/blob/master/CONTRIBUTING.md#style
The reason is that I want to avoid introducing a compile step in the project. It shows that Hyperapp is simple.
One day, when IE11 is no longer supported, we'll use const, arrow functions, etc.


Documentation implies ROPC supports private clients

Hello,
The following documentation clearly states that ROPC does not support confidential clients:
https://docs.microsoft.com/en-us/azure/active-directory-b2c/add-ropc-policy?tabs=app-reg-ga&pivots=b2c-user-flow#ropc-flow-notes

However the information on this page implies there exist scenarios when confidential clients are supported (and that a client secret or assertion must be provided):

While it's generally true confidential clients require a client id and either a secret or assertion, the content of this page is supposed to specifically document ROPC requirements (only)... so I don't think it's appropriate to include information about client secrets or assertions that suggest either may be used in ROPC scenarios.
I'm requesting that the "Condition" for client_secret and client_assertion parameters be changed to "Not supported" and the "Description" for these two parameters indicate ROPC doesn't support confidential clients.  I also recommend including a link to supporting documentation in the "Description" field for these params that call out the ROPC limitation (https://docs.microsoft.com/en-us/azure/active-directory-b2c/add-ropc-policy?tabs=app-reg-ga&pivots=b2c-user-flow#ropc-flow-notes).
Thank you,
Keith

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

ID: b3eac288-4ddd-1099-1c86-885aa42a566f
Version Independent ID: 190585ca-8337-0644-2182-75b77f53c175
Content: Sign in with resource owner password credentials grant - Microsoft identity platform
Content Source: articles/active-directory/develop/v2-oauth-ropc.md
Service: active-directory
Sub-service: develop
GitHub Login: @nickludwig
Microsoft Alias: ludwignick

@mrkeiths
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@mrkeiths, thanks for bringing this up. I see what you're saying, but I think there's two different contexts to consider here. The first is AAD B2C, which does not support confidential clients for ROPC. This is correctly identified in the B2C doc (1st image you listed above). The second context is non-B2C AAD, where confidential client ROPC is technically supported but not by any of the official SDK's. So, if you were to build your own confidential client app completely from scratch (without use of any official SDK), ROPC would be possible. Given this, I think our listing of client_secret and client_assertion as "Sometimes required" in the non-B2C doc is correct - so, I don't think any docs changes are needed here. Would love to hear any follow up thoughts you may have, though!

@nickludwig thank you for the explanation.  I did notice the comment about ROPC being absent from confidential clients in MSFT SDKs.  This was confusing to me since I had also read the support statement I shared about ROPC + confidential clients in B2C scenarios (I overlooked the B2C distinction that you pointed out).
Now that you've clarified, I agree the documentation is correct, but I'm also wondering if there could be a better distinction made on this page between B2C and non-B2C? ("sometimes required" seems a little weak IMO)
You've answered my question and I appreciate your time.  I'll let you decide if clarifying remarks are worth adding and what they might look like, However, if it would be helpful, I'd be happy to come up with a suggestion and/or share feedback about anything you might propose.  Otherwise, you're welcome to close this inquiry.
Thanks again, Keith

@mrkeiths - Happy to help!
And yeah, I tend to agree that "sometimes required" is weak in the context of ROPC. It might be hard to change given that this lines up with the vocabulary used for all our other protocol documentation, but I'll do some brainstorming to see if there are any other options that would work better.
Given that your question has been answered, I'm going to close the thread for now. I will re-open if we decide to re-word "sometimes required". Once again, thank you for your detailed feedback and engagement!

#please-close


Use latest ghcr image for tests

Description:
Change Operator tests to use the ghcr Operator image instead of the ECR Operator image

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Should we really be using the latest image though? Wouldn't we want to target the same version that is used in the ADOT Collector? What happens when the collector version drifts behind the upstream operator version?

Should we really be using the latest image though? Wouldn't we want to target the same version that is used in the ADOT Collector? What happens when the collector version drifts behind the upstream operator version?

Yes, it is true that the ADOT Collector version will drift behind the upstream Operator version in between releases. But, the Operator tests would only be ran during Operator CI, which happens when we want to release the ADOT Operator, which happens alongside ADOT Collector releases

Does there need to be a process established for pinning versions in a release branch then?

Since Operator Ci will be ran continuously (see edit above) then the problem of having the ADOT Collector version drift behind the upstream Operator version becomes an issue again. Does the test framework allow for a way to use the correct ADOT Operator image during non-release CI, but also use the latest ghcr image during a release CI? Yes though, we need to be able to use the right image/pin the right version during release.

Marking as draft for now; opting to use correct ADOT Operator image during Operator CI to prevent drifting of versions, and researching a way to set Operator image in test framework during Operator CI for a release specifically

Food for thought coming up.

We know that the collector will always have a dependency on go.opentelemetry.io/collector in the root go.mod file
We can pull the version out of that in the github workflow
Turn the operator version into a variable and set the variable in the calling workflow

There would be an edge case where the collector version gets updated before the corresponding upstream operator version is available. In this case we would probably need to check to see if the image exists before running the tests. If the image doesn't exist the workflow should probably fail.

Closing as #750 addresses this issue


new C tutorial doesn't compile

83ddea53e added a nativecall C tutorial which doesn't pass xt/
I've committed some updates that mark the C code as such, and output text as such so they aren't tested, leaving these 4 chunks:
$ xt/examples-compilation.t doc/Language/nativecall.pod6 2>&1 | grep 'not ok'
not ok 24 - doc/Language/nativecall.pod6 chunk 24 starts with “sub getadd” compiles
not ok 25 - doc/Language/nativecall.pod6 chunk 25 starts with “class Addr” compiles
not ok 26 - doc/Language/nativecall.pod6 chunk 26 starts with “method fla” compiles
not ok 27 - doc/Language/nativecall.pod6 chunk 27 starts with “ \#!/usr/bin” compiles

Not sure how much effort it is to make this compile-able, but it would be nice if it passed the test.
Note that we can use ":preamble" on a code block if we need to make something available to a different block.

First and last should better be skipped, right? First one is C code and the last one a script.

C code is skippable by adding :lang.  The script is  Perl 6 and should be valid code.

:lang(c)

I'll check it out

The code at the last one works correctly:
$ perl6 full-example.p6
perl6 full-example.p6
return val: 0
Name: google.com
AF_INET SOCK_STREAM
<IP_ADDRESS>
AF_INET SOCK_DGRAM
<IP_ADDRESS>
AF_INET SOCK_RAW
<IP_ADDRESS>
AF_INET6 SOCK_STREAM
2a00:1450:4003:809::200e
AF_INET6 SOCK_DGRAM
2a00:1450:4003:809::200e
AF_INET6 SOCK_RAW
2a00:1450:4003:809::200e

It yields an error Unexpected block in infix position (missing statement control word before the expression?) which I can't really figure out in test. The other two are using data structures that haven't been declared. There are many other skipped tests here and there, some of them using dummy class names. Hope this is OK.

You should not be using :skip-test without documenting why you're skipping the test. Please see: https://github.com/perl6/doc/blob/master/EXAMPLES.md which documents the various options you have when dealing with sample code.
The first item you skipped is Perl 6 code, not C; the method is also Perl 6 code, not C.
There was no need to remove the shebang line in the last example.

I know both methods are Perl6 code. I tested them outside, and they worked. I added the comment above to document why I was skipping the test. I probably shouldn't have eliminated the shebang, but then taking it out is no big deal either.
I will try and see if some of that works, if not I'll document the skipping inline using the mechanism indicated in the page you have pointed to.


Can't move requests into folders (or folders into folders)

Expected Behavior
When I drag a request on a folder it should move there.
Actual Behavior
It doesn't go there.
Reproduction Steps
This is exactly the same as 5182 which was closed since you said the fix would be in 2022.6.0 but it still doesn't work in that version.
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2022.6.0
What operating system are you using?
Windows
Operating System Version
Windows 11 Enterprise Version 10.0.22621
Installation method
Downloaded exe
Last Known Working Insomnia version
No response

Hi @vetterj73 thanks for reporting this!
Can you confirm that this only happens to you when the folder is "unwrapped" / "closed"?
I was trying to reproduce what you mention, and the only case where I can't move a request or a folder into another folder is if the destination folder is not expanded.
cc @Samuelfaure @izzat-sq

@filfreire Negative, I cannot move a request to the folder in any situation (expanded or closed)

@Samuelfaure can you double check the version that you are running (Check in the Help tab):

Also would you be able to share the logs after trying to move a request or a folder:

Here are my whole specs

Nothing happens in the log when I try to move the request to the folder :/ neither in main nor renderer (however if I do other actions I do see something happening in the logs)

Here are my Insomnia specs
Version: Insomnia 2022.6.0
Build date: 9/26/2022
OS: Windows_NT x64 10.0.22621
Electron: 19.0.3
Node: 16.14.2
V8: <IP_ADDRESS>-electron.0
Architecture: x64
The video show me trying to move a request to a folder.
https://user-images.githubusercontent.com/9198450/200014653-476359eb-2ddf-40d9-83d9-31da2d9aa477.mp4

This is my version. In my case, i cannot drag and drop at all. Not just into folders (both expanded and closed), but also cannot drag and drop to change the position of the request.

This was reported before and has been broken since 2022-5.1.
2022.7.0-beta.4 finally fixes it
https://github.com/Kong/insomnia/issues/5101

@darcyrush I am certain I had the problem in 2022-4 (see my original issue https://github.com/Kong/insomnia/issues/5182)

How can I download the beta?
Sent from Yahoo Mail on Android
On Tue, Nov 8, 2022 at 2:32 AM, @.***> wrote:
This was reported before and has been broken since 2022-5.1.
2022.7.0-beta.4 finally fixes it
#5101
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@vetterj73 Available in the release section: https://github.com/Kong/insomnia/releases

I installed the beta and it wiped out my previous project.  I know that is probably my issue since I didn't have it sync'd to the cloud.
Jeremy Vetter (612) 910 - 4225
On Tuesday, November 8, 2022 at 10:11:45 AM CST, Samuel FAURE<EMAIL_ADDRESS>wrote:

@vetterj73 Available in the release section: https://github.com/Kong/insomnia/releases
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Closing since as fixed since beta.4

This still doesn't work with this version
Version: Insomnia 2022.7.0-beta.4
Build date: 11/2/2022
OS: Windows_NT x64 10.0.22621
Electron: 21.2.0
Node: 16.16.0
V8: <IP_ADDRESS>-electron.0
Architecture: x64
https://user-images.githubusercontent.com/9198450/201247474-412bade8-c2eb-4c55-8868-532db25a912f.mp4

@vetterj73, you need to release your mouse click when you see the dotted lines. It also helps if you drag to the right first

That works it is a little confusing because most moves like this you release the mouse when you are over the folder.
Thanks
Jeremy Vetter (612) 910 - 4225
On Friday, November 11, 2022 at 02:14:15 AM CST, darcyrush<EMAIL_ADDRESS>wrote:

@vetterj73, you need to release your mouse click when you see the dotted lines. It also helps if you drag to the right first
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


added logNodeWhenPicking setting, state and function

I've added a setting for inspector: Log Node when picking in Settings > UI pane. It also works on tree selection. It simply logs the node to console. I've seen a few requests and I think this is a sensible start. Putting it in the UI pane is questionable but didn't want to clutter other areas & keep it alongside the other picking toggle setting.

https://forum.babylonjs.com/t/read-write-metadata-using-the-inspector/34208
Closes #13027

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13643/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13643/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13643/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13643/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13643/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13643/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13643/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13643/merge#BCU1XR#0

Thanks for the PR!
That's not exactly what the issue is talking about. The issue refers the metadata object - a plain javascript object that every node has. The idea is to be able to display the object's metadata in the inspector (not in the console). And maybe allow editing it in the future.


wasi: benchmarks fd_readdir for both real and fake file systems

It is likely we'll have to special-case real files in wasi, as wasi-libc makes behavioral choices based on presence of non-zero inode data. This adds a defensive benchmark, so that we know what our performance base case is. This adds both real and fake file systems as both patterns are in use today.
$ go test -run='^$' -bench '^Benchmark_fdReaddir$'
goos: darwin
goarch: amd64
pkg: github.com/tetratelabs/wazero/imports/wasi_snapshot_preview1
cpu: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Benchmark_fdReaddir/embed.FS-16         	  457398	      2416 ns/op
Benchmark_fdReaddir/os.DirFS-16         	   45662	     26271 ns/op
PASS
ok  	github.com/tetratelabs/wazero/imports/wasi_snapshot_preview1	35.632s

See https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-17 and https://github.com/WebAssembly/wasi-filesystem/issues/65
cc @jerbob92

I added a benchmark of a continued read. This reads the same amount of dirents, but some from memory and rest from disk.
Benchmark_fdReaddir
Benchmark_fdReaddir/embed.FS
Benchmark_fdReaddir/embed.FS-16                    	  505809	      2402 ns/op
Benchmark_fdReaddir/embed.FS_-_continued
Benchmark_fdReaddir/embed.FS_-_continued-16        	  586935	      2089 ns/op
Benchmark_fdReaddir/os.DirFS
Benchmark_fdReaddir/os.DirFS-16                    	   44936	     26617 ns/op
Benchmark_fdReaddir/os.DirFS_-_continued
Benchmark_fdReaddir/os.DirFS_-_continued-16        	  245131	      4880 ns/op

Thanks for the help again @jerbob92. I'll implement the fstat next, since we can see how much it costs now.


chore: remove redirects

👷 Deploy Preview for theonedev processing.

Name
Link

🔨 Latest commit
0c34ef418c44963b6efe0dda04ca5856c85ed832

🔍 Latest deploy log
https://app.netlify.com/sites/theonedev/deploys/63b932aa9bf8d0000959e58f


Workaround for #2951 (extended timers were not actually usable)

I don't know if I'm creating this the right way, but the list of changes is correct. (Apologies if the trivial tab -> space changes are undesirable.)
The changes were tested against nrf52840 and work fine. I reviewed the other chips and confirmed that all with "extended" in any impl_timer!() now reference timer3, while the others reference timer0 (which is as they should).
Would be happy to see someone conceive of a cleaner or more obvious way to do this.

Closing as apparently I should do this only against main/HEAD, with the chiptool PAC changes included. Will try again another time when we've been able to migrate our code to use that stuff.


feat: roadmap section

Feature Request
Feature Proposal
Create the roadmap section as the fifth section of the landing page following the Figma design:
The roadmap is just an image so it won't be too difficult. The issue #17 will provide the material for the mobile version.

Closed by #26


[Enemy In Shadows] Missing Talent in text

Under "Heart of the Empire", under "Bolts in the Dark", 1st paragraph, third sentence.
It is missing the text "Sixth Sense" before the word "Talent".From: gustmic (originally Emil100#8185)foundry: 10.303wfrp4e: 6.6.0wfrp4e-core: 3.1.5wfrp4e-eis: 3.1.7Active Modules: combat-utility-belt, dice-calculator, dice-so-nice, gm-notes, healthEstimate, lib-wrapper, michaelghelfi, music-d20-sampler, permission_viewer, pings, settings-extender, socketlib, torch, vtta-tokenizer, wfrp4e-actor-sheet-print, wfrp4e-eis-maps, wfrp4e-gm-toolkit

Make sure your imported documents are up to date, this has been fixed previously in https://github.com/moo-man/WFRP4e-FoundryVTT/issues/1615


Fix Large Query Support

Experienced a problem when running large queries where the Interface
slice isn't reset and holds the previous records instead of receiving the new data.
Any data over 4000 records will just be replaced by the 2001-4000 records block over and over again.
Replicate by querying any set of IDs with at least 4001 records. Unique the returned IDs and you'll find that repetition pattern.
I haven't yet determined if this is correct behavior in Go but the docs for json.Unmarshal suggest that objects should be cleared before Unmarshaling. I believe it may be a Go problem we're working around. I don't know enough Go to say for sure. I'll try and find out but the workaround should be reliable either way.
https://golang.org/pkg/encoding/json/

If it's overwriting the other attributes it's ok to just init the slice.


"History" input coordinate list does not work (ArcMap)

I've typed and pasted multiple coordinates into the input control, but the drop-down list does not display the previously entered coordinates.

In my opinion, this can be looked at for a future release of the tools.

Based on @dfoll testing it has been determined that the coordinate is only saved to the history if you used the Map point tool to specify the location. Typing/pasting in a coordinate and hitting return is not saving the coordinate.

verified


Default Browser Configuration

As per our discussion in #50, this issue is to decide and track what to do about default browser configurations.

Following a conversation on Teams, there's an agreement that there should be some sort of default browser configuration. In addition, the test_case, test_suite and test_run config files should have optional parameters to override higher level preferences. Highest level would be default, then test_run, test_suite, and then test_case.

Config parser does not fully meet requirements for more complex use cases.

Currently no plans to change implementation.


Create Stack should target /stacks/create/review

https://github.com/awslabs/service-workbench-on-aws/blob/4b5928ebbbd837d2e20781a213c2fcb630fbdd95/addons/addon-base-raas-ui/packages/base-raas-ui/src/parts/data-sources/parts/AccountCfnPanel.js#L181
When launching Create Stack, switch the link to "/stacks/create/review" as opposed to "/stacks/new". E.g.,
https://$REGION.console.aws.amazon.com/cloudformation/home?region=$REGION#/stacks/create/review?stackName=studyName&templateURL=https://s3.amazonaws.com/solutions-reference/solution.template

. This will reduce required click-through traffic to register a study by two or more clicks and page refreshes.

see: https://github.com/awslabs/service-workbench-on-aws/blob/4b5928ebbbd837d2e20781a213c2fcb630fbdd95/addons/addon-base-raas/packages/base-raas-services/lib/data-source/data-source-registration-service.js#L34

After discussing this with the dev team, we've decided to keep the original CloudFormation URL. Even though this means the user will have to click through more screens to create the stack, we believe this is in the best interest of the customer. From a customer awareness and security perspective it allows the user to more carefully examine the resources that the CF stack is creating. It also allows the user to customize settings on the CF stack.
Thanks for bringing this idea to our attention though. We really appreciate your initiative to help.


Release 0.1.0

@rohitnarula7176,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Roll Flutter Engine from d5bf3afc601f to 0e70fc3e6253 (1 revision)

https://github.com/flutter/engine/compare/d5bf3afc601f...0e70fc3e6253
2024-08-16<EMAIL_ADDRESS>Manual roll Dart SDK from 44635f897535 to 8c02ad43e01a (3 revisions)  (flutter/engine#54581)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Bring back icons for Node/Edge graph table types

Azure Data Studio Version: Insiders
OS Version: Windows System Enterprise

Steps to Reproduce:
Icons needed to differentiate between different table types. They were in version 1.34 but removed since then.

Does this issue occur when all extensions are disabled?: Yes/No

@alanrenmsft

Any chance we can get this for the August Release? We may be doing another PGI demo in September and will need to be able to visually describe node vs graph tables to audience members @alanrenmsft

not sure, the priority of this is lower than other issues that I am working on. but I will try to get to this once I am done with other high priority bugs.


Add a few new ways to laugh and cry with emotes

About the PR
 You can now Sob and chortle
Why / Balance
 I see people do all the 3 without a noise.

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: You can now Sob and Chortle with emotes

Pouting is silent.

This is now good to review I believe 👍


refactor(traverse): do not expose TraverseCtx::new

Creating a TraverseCtx with TraverseCtx::new should be an internal API within oxc_traverse. Don't expose it outside the crate.

#3226  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

May 11, 12:16 AM EDT: @Boshen started a stack merge that includes this pull request via Graphite.


Support for signing non XML data

SignXML only supports signing XML files. This pull-request adds support for signing non-XML data, useful for example for signing binary files or arbitrary byte streams.

Thanks for your contribution. To continue, we would need some documentation with examples, references to relevant parts of the XML Signature standard, test cases, and a reference to an interop counterparty implementation (another implementation of XML Signature that you intend to use this with and can confirm that it works with the result).

Hello! Right now I'm trying to sign arbitrary ASCII data needed to prepare requests for a bank SOAP API. If this is out of scope for the library, please let me know :)
Unfortunately, this API is not public. From the scraps of documentation I gathered, it's implemented in .net (but the guys  I'm working with don't seem to know specifics either).
In a nutshell, I'm trying to get a detached XAdES signature for a provided byte-stream (https://www.w3.org/TR/xmldsig-core1/#def-SignatureDetached)

OK, thanks for those details. Yes, this application is generally within the scope of this library and I understand the constraints regarding the non-public API, and that you may not know which XML Signature implementation the counterparty uses.
However, we still need examples and test cases to proceed.

OK, thanks for those details. Yes, this application is generally within the scope of this library and I understand the constraints regarding the non-public API, and that you may not know which XML Signature implementation the counterparty uses.
However, we still need examples and test cases to proceed.

I understand, I'll add them. Is it better to keep this PR as it is now and slowly fix it or should I retract it and submit it later, in a more complete form?

Is it better to keep this PR as it is now and slowly fix it or should I retract it and submit it later, in a more complete form?

I don't mind keeping this PR open, but I'm fine either way. Please do what works best for your workflow. Looking forward to adding this change. Thanks.


Invalid argument error with mission_items in mission_raw.py

Hi @julianoes
I have been trying to execute a simple mission with mission_items using mission_raw.py.  I referred to the existing github issues related to this particular issue, I still get invalid argument error...
I am trying to execute a simple mission with RTL. I am doubtful whether to give the lat,long, alt as zeros ( i gave the home location) for RTL [MAV_CMD (20)] as other parameters(1-4) are zeros (according to mavlink_mission.cpp)
Here is the code..suggest corrections needed:
import asyncio
from mavsdk import System
from mavsdk.mission_raw import MissionItem

async def run():
    drone = System()
    await drone.connect(system_address="udp://:14540")

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print(f"-- Connected to drone!")
            break

    print_mission_progress_task = asyncio.ensure_future(
        print_mission_progress(drone))

    # included to add redundancy
    running_tasks = [print_mission_progress_task]
    termination_task = asyncio.ensure_future(observe_is_in_air(drone, running_tasks))

    mission_items = []
    mission_items.append(MissionItem(1,6, 22, 1, 1, 0, 10,  0, float('nan'),  169385325,  817945425, 10.0, 0))
    mission_items.append(MissionItem(2,6, 16, 1, 1, 0, 10,  0, float('nan'),  169388925,  817942725, 10.0, 0))
    mission_items.append(MissionItem(3,2, 20, 1, 0, 0,  0,  0,   0,           169385025,  817940325, 10.0, 0))

    await drone.mission_raw.upload_mission(mission_items)

    print("mission uploaded")
    await asyncio.sleep(2)

    print("Waiting for drone to have a global position estimate...")
    async for health in drone.telemetry.health():
        if health.is_global_position_ok and health.is_home_position_ok:
            print("-- Global position estimate OK")
            break

    await drone.action.arm()
    print("arming the done")

    await drone.mission_raw.start_mission()
    print("started the mission")

    await termination_task

async def print_mission_progress(drone):
    async for mission_progress in drone.mission.mission_progress():
        print(f"Mission progress: "
              f"{mission_progress.current}/"
              f"{mission_progress.total}")

async def observe_is_in_air(drone, running_tasks):
    was_in_air = False

    async for is_in_air in drone.telemetry.in_air():
        if is_in_air:
            was_in_air = is_in_air

    if was_in_air and not is_in_air:
        for task in running_tasks:
            task.cancel()
            try:
                await task
            except asyncio.CancelledError:
                pass
        await asyncio.get_event_loop().shutdown_asyncgens()

        return

if __name__ == "__main__":
    # Run the asyncio loop
    asyncio.run(run())

error:
 raise MissionRawError(result, "upload_mission()", mission_items)
mavsdk.mission_raw.MissionRawError: INVALID_ARGUMENT: 'Invalid Argument'; origin: upload_mission(); params: ([<mavsdk.mission_raw.MissionItem object at 0x7f89ac7830a0>, <mavsdk.mission_raw.MissionItem object at 0x7f89ac7836a0>, <mavsdk.mission_raw.MissionItem object at 0x7f89ac7837f0>],)

PS: similar arguments with just takeoff and land MAV_CMDs also result in the same error.

Ok, the seq and current fields were wrong, here is what uploads for me:
#!/usr/bin/env python

import asyncio
from mavsdk import System
from mavsdk.mission_raw import MissionItem

async def run():
    drone = System(mavsdk_server_address="localhost")
    await drone.connect()

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print(f"-- Connected to drone!")
            break

    print_mission_progress_task = asyncio.ensure_future(
        print_mission_progress(drone))

    # included to add redundancy
    running_tasks = [print_mission_progress_task]
    termination_task = asyncio.ensure_future(observe_is_in_air(drone, running_tasks))

    mission_items = []
    mission_items.append(MissionItem(0,6, 22, 1, 1, 0, 10,  0, float('nan'),  169385325,  817945425, 10.0, 0))
    mission_items.append(MissionItem(1,6, 16, 0, 1, 0, 10,  0, float('nan'),  169388925,  817942725, 10.0, 0))
    mission_items.append(MissionItem(2,2, 20, 0, 0, 0,  0,  0,   0,           169385025,  817940325, 10.0, 0))

    await drone.mission_raw.upload_mission(mission_items)

    print("mission uploaded")
    await asyncio.sleep(2)

    print("Waiting for drone to have a global position estimate...")
    async for health in drone.telemetry.health():
        if health.is_global_position_ok and health.is_home_position_ok:
            print("-- Global position estimate OK")
            break

    await drone.action.arm()
    print("arming the done")

    await drone.mission_raw.start_mission()
    print("started the mission")

    await termination_task

async def print_mission_progress(drone):
    async for mission_progress in drone.mission.mission_progress():
        print(f"Mission progress: "
              f"{mission_progress.current}/"
              f"{mission_progress.total}")

async def observe_is_in_air(drone, running_tasks):
    was_in_air = False

    async for is_in_air in drone.telemetry.in_air():
        if is_in_air:
            was_in_air = is_in_air

    if was_in_air and not is_in_air:
        for task in running_tasks:
            task.cancel()
            try:
                await task
            except asyncio.CancelledError:
                pass
        await asyncio.get_event_loop().shutdown_asyncgens()

        return

if __name__ == "__main__":
    # Run the asyncio loop
    asyncio.run(run())

Ok, the seq and current fields were wrong, here is what uploads for me:
#!/usr/bin/env python

import asyncio
from mavsdk import System
from mavsdk.mission_raw import MissionItem

async def run():
    drone = System(mavsdk_server_address="localhost")
    await drone.connect()

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print(f"-- Connected to drone!")
            break

    print_mission_progress_task = asyncio.ensure_future(
        print_mission_progress(drone))

    # included to add redundancy
    running_tasks = [print_mission_progress_task]
    termination_task = asyncio.ensure_future(observe_is_in_air(drone, running_tasks))

    mission_items = []
    mission_items.append(MissionItem(0,6, 22, 1, 1, 0, 10,  0, float('nan'),  169385325,  817945425, 10.0, 0))
    mission_items.append(MissionItem(1,6, 16, 0, 1, 0, 10,  0, float('nan'),  169388925,  817942725, 10.0, 0))
    mission_items.append(MissionItem(2,2, 20, 0, 0, 0,  0,  0,   0,           169385025,  817940325, 10.0, 0))

    await drone.mission_raw.upload_mission(mission_items)

    print("mission uploaded")
    await asyncio.sleep(2)

    print("Waiting for drone to have a global position estimate...")
    async for health in drone.telemetry.health():
        if health.is_global_position_ok and health.is_home_position_ok:
            print("-- Global position estimate OK")
            break

    await drone.action.arm()
    print("arming the done")

    await drone.mission_raw.start_mission()
    print("started the mission")

    await termination_task

async def print_mission_progress(drone):
    async for mission_progress in drone.mission.mission_progress():
        print(f"Mission progress: "
              f"{mission_progress.current}/"
              f"{mission_progress.total}")

async def observe_is_in_air(drone, running_tasks):
    was_in_air = False

    async for is_in_air in drone.telemetry.in_air():
        if is_in_air:
            was_in_air = is_in_air

    if was_in_air and not is_in_air:
        for task in running_tasks:
            task.cancel()
            try:
                await task
            except asyncio.CancelledError:
                pass
        await asyncio.get_event_loop().shutdown_asyncgens()

        return

if __name__ == "__main__":
    # Run the asyncio loop
    asyncio.run(run())

Ok, the seq and current fields were wrong, here is what uploads for me:
#!/usr/bin/env python

import asyncio
from mavsdk import System
from mavsdk.mission_raw import MissionItem

async def run():
    drone = System(mavsdk_server_address="localhost")
    await drone.connect()

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print(f"-- Connected to drone!")
            break

    print_mission_progress_task = asyncio.ensure_future(
        print_mission_progress(drone))

    # included to add redundancy
    running_tasks = [print_mission_progress_task]
    termination_task = asyncio.ensure_future(observe_is_in_air(drone, running_tasks))

    mission_items = []
    mission_items.append(MissionItem(0,6, 22, 1, 1, 0, 10,  0, float('nan'),  169385325,  817945425, 10.0, 0))
    mission_items.append(MissionItem(1,6, 16, 0, 1, 0, 10,  0, float('nan'),  169388925,  817942725, 10.0, 0))
    mission_items.append(MissionItem(2,2, 20, 0, 0, 0,  0,  0,   0,           169385025,  817940325, 10.0, 0))

    await drone.mission_raw.upload_mission(mission_items)

    print("mission uploaded")
    await asyncio.sleep(2)

    print("Waiting for drone to have a global position estimate...")
    async for health in drone.telemetry.health():
        if health.is_global_position_ok and health.is_home_position_ok:
            print("-- Global position estimate OK")
            break

    await drone.action.arm()
    print("arming the done")

    await drone.mission_raw.start_mission()
    print("started the mission")

    await termination_task

async def print_mission_progress(drone):
    async for mission_progress in drone.mission.mission_progress():
        print(f"Mission progress: "
              f"{mission_progress.current}/"
              f"{mission_progress.total}")

async def observe_is_in_air(drone, running_tasks):
    was_in_air = False

    async for is_in_air in drone.telemetry.in_air():
        if is_in_air:
            was_in_air = is_in_air

    if was_in_air and not is_in_air:
        for task in running_tasks:
            task.cancel()
            try:
                await task
            except asyncio.CancelledError:
                pass
        await asyncio.get_event_loop().shutdown_asyncgens()

        return

if __name__ == "__main__":
    # Run the asyncio loop
    asyncio.run(run())

Thank you very much for the prompt reply. But i have a question. For ardupilot , i saw that the seq starts with 0 whereas for px4 it starts with 1.

@julianoes
Thank you very much for your prompt reply.


Remove leading / character from API urls

Closes #7878

@zsonglorman Hi! I planned a release for tomorrow 🙂

@zsonglorman 8.9.2 has been released on NuGet


Support for NB 1.5.0 Hold my beer update

Add 1.5.0 hash
Add support for HMB mode ladder ending
Added Y position to the variables read in memory
Changed door ending check to include fixed y & x position to avoid splitting when explorer the secret "true ending" area
For the HMB ladder ending check, checks range of y position because I think the timer can trigger while you're jumping
Reads a different parts for the save file to figure out the current level. BUT reading bestLevelId means that the autosplitter works only for fresh file, won't split for reusing a save from the start (which does activate the timer)

Wait I think I figured out how to support NG+

This look awesome, merging


Add failing test for double exposures #56

#56

Hello, @Morred!
I closed & reopened your PR just to initiate a re-run of Travis CI checks. Build still fails but this time it's just due to RuboCop offenses. RSpec tests pass fine as you can see here: https://travis-ci.org/intridea/grape-entity/jobs/73909288 so issue #56 can be considered as solved.
I will not merge this PR because new specs from #151 for this issue are sufficient. If you don't think so and want this to be merged please somehow fix RuboCop offenses.
spec/grape_entity/entity_spec.rb:338:52: C: Use the new lambda literal syntax ->(params) {...}.

            expose :media, using: SoundEntity, if: lambda { |object, _| object.sound? }

                                                   ^^^^^^

spec/grape_entity/entity_spec.rb:339:52: C: Use the new lambda literal syntax ->(params) {...}.

            expose :media, using: PhotoEntity, if: lambda { |object, _| object.photo? }

                                                   ^^^^^^

I personally don't like this type of RuboCop offense about lambda syntax and if you think the same feel free to open a separate PR with patch for .rubocop.yml.
I also don't like defining constants like PhotoEntity in specs because these things are global and survive among rspec examples. I know there are some specs in entity_spec.rb that already define constants but it's something that I want to get rid of. I already had issues with constants while working on this project. @dblock, what do you think? Also I need to say that this problem is gracefully solved in https://github.com/Casecommons/with_model gem but it's only for ActiveRecord models. I also seen a good workaround for this in Her gem, please look at https://github.com/remiprev/her/blob/49cd15ffbad2aec104810753a90d9a7b6977fd31/spec/support/macros/model_macros.rb#L6 and https://github.com/remiprev/her/blob/c39fbb6d211109da5f2ff8c35fff4b5a85d8d5c9/spec/spec_helper.rb#L21


now plots directly the input lp3. includes tests to validate prior behavior.

The following table contains the correct discharges of the input function for the west sac analytical flow-frequency function:

Frequency
Flow
Stage

0.5
202306
23.86

0.2
373981
27.38

0.1
508002
29.5

0.04
696277
31.66

0.02
848335
33.04

0.01
1009190
34.58

0.005
1179084
36.11

0.002
1417793
37.58

I see the discharges in the above table within inputFunction, it seems like inputFunction is not making it to the user interface
https://github.com/HydrologicEngineeringCenter/HEC-FDA/blob/9c73650bfc2d259b56e75dfe58e2ac1f1532b970/HEC.FDA.ViewModel/TableWithPlot/Base/BaseLP3TableWithPlot.cs#L71


fix: add exclusion scope for webterminal

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

I accesses webterminal in my openshift cluster, which resulted in an alert.
I created a copy of the default policy.
Afterwards I created the policy as in the commit, imported it into ACS and overwrote the original default policy.
Now i accessed webterminal again. ACS  created a violation for the copy, but not for the overwritten default policy.

Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/ok-to-test


Add campaign attribution support

Fix CybercentreCanada/assemblyline#260
Note: Patch has not been tested yet

If you do find that you will be able to use more the attribution tags than actor, campaign, malware_family, maybe I should consider re-architecting some code to allow that 🤔

I don't have any specific use case for more at the moment, so I've stopped on just adding this. I think it may be generally useful, but no specific need.

The patch should be available for testing on the development channel for the service.

Thanks! I've just tested it - works well! Sanitization makes my names a little funny, but I don't think it's a problem. However, I've caught another issue - if (not) source_cfg.get("...") else does not work well when something is in the column 0 :D

Pushed fixes for column 0. It has already been tested by me.

Patch should be included in the latest stable release!


Fix the unread count not going away when you've signed out

Fixed Issues
$ https://github.com/Expensify/App/issues/11671
Tests
For web, desktop, and mobile web:

Sign in and have another account send you a message
Verify that the unread counter goes up (either page title or icon badge). For mobile web, you need to open the browser window which shows the open tabs in order to verify the page titles.
Access the unread chat
Verify that the unread counter goes down
Make sure you have at least 1 unread chat showing on the counter and sign out
Verify that the unread counter goes away completely

For native devices:
The badge counters don't work in local environment, so they can't really be tested. Just generally do some regression testing to ensure that the unread stuff works like it should

Sign in and have another account send you a message
Verify that the LHN appears with the unread chat
Go into the chat
Go back to the LHN and verify the chat is no longer marked as unread

[ ] Verify that no errors appear in the JS console

Offline tests

Be signed into the app with an unread chat
Sign out
Verify that the counter goes away

web offline test video
https://user-images.githubusercontent.com/1228807/207709796-5145656b-0604-4ae1-b938-fc2457460a2e.mp4

QA Steps

Sign in and have another account send you a message
Verify that the unread counter goes up (either page title or icon badge). For mobile web, you need to open the browser window which shows the open tabs in order to verify the page titles.
Access the unread chat
Verify that the unread counter goes down
Make sure you have at least 1 unread chat showing on the counter and sign out
Verify that the unread counter goes away completely

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/1228807/207711078-dccbea3e-60f7-4ba8-9f38-24aa97dd6aec.mp4

Mobile Web - Chrome

https://user-images.githubusercontent.com/1228807/207711095-df8df60d-2ea5-4cb1-b04d-4ad39889c396.mp4

Mobile Web - Safari

https://user-images.githubusercontent.com/1228807/207711142-fba0e1e9-4ede-45de-b16e-0e7e6783a956.mp4

Desktop

https://user-images.githubusercontent.com/1228807/207711165-e882098e-c84d-4f07-8899-759a6487c615.mp4

iOS

https://user-images.githubusercontent.com/1228807/207711194-f2c5d80a-ec06-4235-b4d1-794d12d67e19.mp4

Android

https://user-images.githubusercontent.com/1228807/207711203-9f588af0-1f19-46b8-a75b-b0af31229c19.mp4

@tgolen lint check is failing.

@sobitneupane if you're able to get to this soon, then I'll let you take the first crack at it.

Fixed the lint errors :+1:

@tgolen I didn't get the expected output. I tried sending some messages. But unread indicator did not update.
https://user-images.githubusercontent.com/25876548/207784602-5e92b7a9-6810-4da1-a24c-d670ec02085c.mov

@tgolen I didn't get the expected output. I tried sending some messages. But unread indicator did not update.

@sobitneupane i think that the subscription isn't imported anywhere in the App

OK, I fixed the lib import and retested it to make sure it's working again.

OK, I'll look into those unit tests.

Unit tests are passing now

Screenshots/Videos

Web

Desktop
https://user-images.githubusercontent.com/25876548/208104739-f56efa8a-2f42-4fc5-94dc-3b7a04169433.mov

iOS
https://user-images.githubusercontent.com/25876548/208104795-15c80931-62d5-416f-a032-47216be1df8c.mov

Android

Screenshots/Videos

Web

Desktop
https://user-images.githubusercontent.com/25876548/208104739-f56efa8a-2f42-4fc5-94dc-3b7a04169433.mov

iOS
https://user-images.githubusercontent.com/25876548/208104795-15c80931-62d5-416f-a032-47216be1df8c.mov

Android

It tests well on Web. I was unable to test on mWeb due to sign in issues (403 errors). I will test it once my IP will be whitelisted.
On Desktop, unread indicator in not shown in my device. In fact, It is not shown in staging app as well (so might be some issue on my end)

Could it be your notification settings? @puneetlath Would you be able to test on Desktop and upload a screenshot/video instead?

Works well for me on Desktop:
https://user-images.githubusercontent.com/1371996/208196118-85eb5912-03f3-4577-afbd-c9973d176680.mov

Screenshots/Videos

Web
https://user-images.githubusercontent.com/25876548/208226136-0e27f362-084a-48a1-bead-34417ada6267.mov

Mobile Web - Chrome
https://user-images.githubusercontent.com/25876548/208226182-a22b66ca-6601-4a4f-9e27-517f5ec52fcf.mov

Mobile Web - Safari
https://user-images.githubusercontent.com/25876548/208226172-30de3196-41a3-4787-8b5d-ebe40cb50503.mov

Desktop
https://user-images.githubusercontent.com/25876548/208226145-59f084cb-6085-4d84-94aa-3fd0d956ddbe.mov

iOS
https://user-images.githubusercontent.com/25876548/208226214-79a97aec-1efc-4638-b990-1b5d7c3720ec.mov

Android
https://user-images.githubusercontent.com/25876548/208226199-40e07559-214f-4836-b035-45fae812e2d2.mov

@tgolen I am getting following console error.

OK, I'm not sure how that can happen, but I've added a check for a null report object now which should prevent that from happening.

@sobitneupane are you able to test again?

@tgolen With the latest change, when we reload the page after sign out (or close the tab and reopen expensify on new tab after signout), the unread count reappears.
Tested with the following account:
email<EMAIL_ADDRESS>Password: Feya86Katya
I was able to reproduce the issue on chrome only (not on firefox, safari and chrome incognito).

OK, thanks for reporting that. Let me look into that. That's really strange.

I tried to reproduce it, and I couldn't reproduce it in Chrome on either MacOS or Android mobile web. This is what I did:

Sign into an account that has an unread chat
Verify the title shows there is an unread chat
Sign out
Verify the title shows 0 unread chats
Refresh
Verify the title still shows 0 unread chats

I'm going to remerge main into this branch just to see if that helps you. Please make sure to do a fresh npm i before testing it again.

I was able to reproduce similar issue in staging as well.
When I log out from one account and login to another account, reports from logged out account also appears in the newly logged in account.
So, I think https://github.com/Expensify/App/pull/13600#issuecomment-1358943509 bug is also caused by the same issue.

I don't think I'm following you. The changes in this PR can't affect anything on staging, so the changes here should only improve any problems you saw on staging.

I mean to say https://github.com/Expensify/App/pull/13600#issuecomment-1359997799 and https://github.com/Expensify/App/pull/13600#issuecomment-1358943509 bug might be caused by same issue. And might not be related to this PR. I will report it in expensify-bug channel to see if any other user has seen the similar bug.

https://user-images.githubusercontent.com/25876548/208750220-0c34fe25-2061-4872-b274-955969a48948.mov

@sobitneupane so are you still seeing issues with this PR or no?
I just tried testing on Chrome and wasn't able to reproduce the issue.

@puneetlath Yes, I am still reproduce https://github.com/Expensify/App/pull/13600#issuecomment-1358943509 issue. Interestingly, I can only reproduce it on chrome non-incognito.

Hm, I was definitely also testing it in chrom non-icognito. When I first tried to reproduce it, I thought it happened, but then I had some errors in the JS console about missing libs, and that's when I ended up remerging main into the branch and restarting webpack. That made the errors go away and I could no longer reproduce it at all.

@tgolen I haven't tested these changes yet , but what I see in @sobitneupane video I can see where the bug is . i can tell that this is related to both onyx clear logic which delay clearing and the fact that you have imported the subscriber in the whole App . The subsriber should be imported in AuthScreen . Because when he refresh before onyx finish , the data that wasn't cleared will be used by onyx and the subscriber will be triggered again (we have data and subscriber is imported) a fix for this will be to import subscriber on AuthScreen  and/or to close the subscriber connection after logout

@tgolen as yo can see here the subscriber callback is called on guest screen when Onyx have data (unfinished clearing)
https://user-images.githubusercontent.com/36869046/208905751-92e49910-6e67-4b43-8a1e-aae22213a016.mov

@fedirjh Thanks for those comments! I think it's perfectly fine to have the subscriber where it is. Shouldn't we be more concerned with why there is still report data in Onyx after signing out? That seems to be the root of the issue.

Today I tried to reproduce the issue with a large account. I've got an account with 4000 reports and 4000 users, and I wasn't able to reproduce the issue of Onyx not clearing out all the data. I think we need to try and zero-in on how exactly to reproduce that and treat it as a separate issue. Though, I also saw that we are reverting some of the changes to Onyx.clear(), so we might want to hold off on doing anything until we know what the final state of Onyx.clear() will be.
For this PR, I think the changes are good and will remain good regardless of what happens to fix Onyx.clear().

We have new issue to handle issues like this. I think we can move forward this this PR.
@puneetlath Overall change looks good to me.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @puneetlath in version: 1.2.47-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.2.47-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Cannot read properties of undefined (reading 'User') to set PeoplePicker principalTypes

Category
[ ] Enhancement
[ ] Bug
[x] Question
Version
Please specify what version of the library you are using: [     3.7 & 3.8.0    ]
Expected / Desired Behavior / Question
 import {PeoplePicker, PrincipalType} from "@pnp/spfx-controls-react/lib/PeoplePicker";
 <PeoplePicker
    context={props.spfxContext}
    titleText={'Select user'}
    ensureUser={true}
    principalTypes={[PrincipalType.User]}
    showHiddenInUI={false}
    resolveDelay={500}
/>

PeoplePicker always get

Uncaught TypeError: Cannot read properties of undefined (reading 'User')

But if I change the import statement to
import {PeoplePicker, PrincipalType} from "@pnp/spfx-controls-react/lib/controls/peoplepicker";
The PeoplePicker rendered successfully.
The spfx version is 1.14, the pnp/sp version is 3.4.1, I also installed "rush-stack-compiler-4.2"(This is required by pnpjs v3).
I am working on SharePoint Online with a mac mini.
I had make a similar demo with pnpjs v2 and rush-stack-compiler-3.9, the PeoplePicker worked well. But I cannot make sure this is caused by rush-stack-compiler.
So whether this is compatible with pnpjs v3, or I have missed something?
Thanks!

Thanks @yungfu - replacing the import statements worked for me.

@AJIXuMuK - Add a ListPicker to webpart, and add import { ListPicker } from '@pnp/spfx-controls-react';.
<ListPicker
  context={props.spfxContext}
/>
<PeoplePicker
    context={props.spfxContext}
    titleText={'Select people'}
    principalTypes={[PrincipalType.User]}
    ensureUser={true}
/>

In my project, I import ListPicker in another component file. They are all imported to one grandfather component. Finaly, I found that, any component that we can import { IconPicker or others } from '@pnp/spfx-controls-react'; directly will cause this issue.

I get the same error when trying to upgrade to any version I tried <3.10.0 from my current 3.4.1 with both SPFx 1.14.0 and SPFx 1.15.2. Changing the import statement as mentioned by the op helps for me too. Unfortunately 3.10.0 has another issue, as described in #1292

Hi @yungfu,
Since you've raised the issue, do you still have trouble and if it does, did you have the chance to retry with recent versions (>=3.10)?

I cannot reproduce this issue on 3.15. seems it has been fixed.


For read-only access to preset security policies

[Enter feedback here]
The Global Reader role is not listed as being allowed to view these policies. Is this correct or does this role need to be added?

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

ID: 4f6f1cf3-a121-3c6e-9380-79440f4c6671
Version Independent ID: 9b1bc5d1-8ecc-d0f9-092e-325c6acff4fe
Content: Preset security policies - Office 365
Content Source: microsoft-365/security/office-365-security/preset-security-policies.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@chrisda Please add your comment and help us resolving this issue. Thanks

Lack of Global Reader was an omission that has since been fixe.
Thanks for the feedback.
Closing


Flutter 3.22 build failed on Android

Fails to compile on Flutter 3.22.0
../../AppData/Local/Pub/Cache/hosted/pub.dev/flutter_neumorphic_plus-3.3.0/lib/src/widget/app_bar.dart:185:14: Error: The getter 'headline5' isn't defined for the class 'TextTheme'.

'TextTheme' is from 'package:flutter/src/material/text_theme.dart' ('../../flutter/default/packages/flutter/lib/src/material/text_theme.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'headline5'.
.headline5!
^^^^^^^^^
../../AppData/Local/Pub/Cache/hosted/pub.dev/flutter_neumorphic_plus-3.3.0/lib/src/widget/container.dart:121:69: Error: The getter 'bodyText2' isn't defined for the class 'TextTheme'.
'TextTheme' is from 'package:flutter/src/material/text_theme.dart' ('../../flutter/default/packages/flutter/lib/src/material/text_theme.dart').
Try correcting the name to the name of an existing getter, or defining a getter or field named 'bodyText2'.
style: this.textStyle ?? material.Theme.of(context).textTheme.bodyText2!,

Same problem here

@feykro use the following until they fix it (my forked version):
flutter_neumorphic_plus:      { git: { url: https://github.com/bsz0206/flutter_neumorphic_plus2.git } }

@bsz0206 Thanks, I'll try after I'm done with the rest of the issues in my project! I don't know if you plan on maintaining your fork and/or releasing it, but I think Neumorphism deserves a well-maintained package! In my opinion, it could use some polish and modernization, such as negative depth for text or surface tint for widgets.

I've refactored this project at https://github.com/gsmlg-dev/material-neumorphic.
This package is not yet qualified enough for production use.
If you want to use this package, it's recommended to clone it and include it in your project using Melos.

@gsmlg Can we at least merge my pull request. It is only two lines in app_bar.dart and makes it compatible with the new flutter material. The current one cannot build for android.
It actually addresses to Analysis issues:
Pass static analysis 0/50
trigger folding of the section
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 93 issues. Showing the first 2:
ERROR: The getter 'headline5' isn't defined for the type 'TextTheme'.
ERROR: The getter 'bodyText2' isn't defined for the type 'TextTheme'.

@gsmlg Can we at least merge my pull request. It is only two lines in app_bar.dart and makes it compatible with the new flutter material. The current one cannot build for android.
It actually addresses to Analysis issues:
Pass static analysis 0/50 trigger folding of the section 0/50 points: code has no errors, warnings, lints, or formatting issues Found 93 issues. Showing the first 2:
ERROR: The getter 'headline5' isn't defined for the type 'TextTheme'. ERROR: The getter 'bodyText2' isn't defined for the type 'TextTheme'.

Your pr has already been merged for a month, but foggot to publish to pub.dev.
Now this package has been publish to pub.dev as 3.4.0


Material-Sprint: general feedback

Would be wise to prefix all classes that are required in HTML to be prefixed with "wsk" eg "wskCheckbox" to minimize clashing with 3rd party styles / class names

Element classnames are not consistent in their naming method. Some have dashes some are a form of camel case. I believe style guides prefer regular camel case eg "myClassName" - need to standardize on one form across all components.

All demo.html HTML files - general whitespace tidy up required. For example see https://github.com/google/web-starter-kit/blob/material-sprint/app/styleguide/fab/demo.html#L9

Generally speaking many components need to consider situation where by instances of that component are made after the document load. Eg programatically using JavaScript.

It would be nice to have consistency between implementations. I am happy to write an interface or such which all "components" should implement for the JS layers. This would contain common methods we can be sure are available for key life events (eg when you need to programatically add a new instance after dom load), and also define a skeleton for where to position things eg enums, function prototypes etc so ordering between all components is familiar too. @addyosmani let me know if this is a route we should take for final production version.

Thanks for filing this issue. As part of our move to the new CSS library this summer https://github.com/google/web-starter-kit/issues/674, we're closing issues related to the 0.5.x styles, which will no longer be supported moving forward. We recommend holding off on PRs to the styles in master as they're going to be replaced by something much better soon.


Figure out deployment

This may or may not be tricky. I really don't know right now.

This shouldn't be too bad. #22 will introduce a cloudformation template that we can use in order to create the resources necessary to run the whole environment.
We can write a script to publish our lambda code to S3 (#25 could help automate this), and let the CFT do the heavy lifting of creating the SQS queue, lambda, DynamoDB table, etc.


bpf: initial pcap exporter for lb

See commit msgs.

test-me-please

test-me-please

test-me-please

test-me-please

retest-1.21-4.9

retest-runtime

retest-runtime

Hit https://github.com/cilium/cilium/issues/15469 in 4.19: unrelated.

Hit #14959 in 4.9: unrelated.

Hit #15469 and https://github.com/cilium/cilium/issues/15472 in net-next: unrelated.


Improve documentation about interoperability with official Dropbox client

Maestral's Github page says:

Never sync a local folder with both the official Dropbox client and Maestral at the same time.

This could be more explicit. Does it mean you must use completely separate local folders for the two clients? Or does it mean you can use the same folder but must never have both client apps running?
Whatever the answer, I suggest this information is critical and should be found in more places: within https://maestral.app/docs; in the app's setup dialogs.
If the answer is that the two clients must not even share a local folder, the app's setup dialog could be further enhanced to warn people who select an existing folder at the default ~/Dropbox location.
It would also be useful to set expectations for what happens if Maestral adopts an existing folder that was previously synced by the official client. Subject to the documented caveats about symlinks and such, should a user expect this to be a safe operation?

This could be more explicit. Does it mean you must use completely separate local folders for the two clients? Or does it mean you can use the same folder but must never have both client apps running?

That is a good question. I would recommend to use completely separate folders. This is because the official Dropbox client uses extended attributes (xattr) to associate sync metadata with files. Maestral will under some circumstances overwrite and delete such metadata. The Dropbox client can probably recover from that but might spend more time indexing local files as a result.

It would also be useful to set expectations for what happens if Maestral adopts an existing folder that was previously synced by the official client. Subject to the documented caveats about symlinks and such, should a user expect this to be a safe operation?

This is safe, as long as you don't regularly switch between sync clients (see above). The local folder will be indexed, as will be the remote, and any equal files will be treated as synced. Any differences will undergo standard conflict resolution and may result in conflicting copies.
I agree, the docs can be improved here. Pull requests are always welcome :) The website lives in the  website branch.

I had the same question, I'm happy to submit a pull request for the docs. Is this an accurate summary?

You can use the official and Maestral clients at the same time on a single host as long as you do not sync the same folder with both clients as the same time.

OK -

~/Dropbox/* with the Dropbox client
~/Dropbox-Maestral/* with the Maestral client

Not OK -

~/Dropbox/* with the Dropbox client and the Maestral client

On any single host you should avoid frequently switching which client is used to sync a folder.

You can sync the same folders from different hosts using both the official and Maestral clients at the same time.

OK -

~/Dropbox/* on hostA with the Dropbox client
~/Dropbox/* on hostB with the Maestral client

Be aware that this approach may increase the time it takes for the Dropbox client to sync a folder.

@Gestas, yes, this mostly sums it up.

On any single host you should avoid frequently switching which client is used to sync a folder.

Small disclaimer: I have actually tested how the official Dropbox client handles syncing a folder which was previously being synced by Maestral before.


clock_tower_adjusted

whoops i messed up the other pull request

hmm the clocktower is too far right on my screen

Looking at this again, I think the hill needs to be fixed, not the clocktower. Maybe use media queries to change its size based on screen width, and put the clocktower back. Also the blue box at the top should not stretch to the end of the screen.

I think it would be better to start this one from scratch given that, so I'm going to close this pr


py file opens and closes instantly

i guess i ve done everything right this is what is shown on idle file its probably a dumb mistake by me but if you can help thx a lot.
py idle error.txt

Post a screenshot I would
Rather avoid downloading things

Incorrect json settings

uhm how exactly do i fix that ?

That answer is on the readme
Sent from my iPhone

On Aug 29, 2022, at 3:01 PM, orytel @.***> wrote:

uhm how exactly do i fix that ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

oh my bad seems to work now but im getting this which says just to type $settings on the server and i did but still not working after restarting
Exception ignored in thread started by: <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x000001FBE55B7BA0>>
Traceback (most recent call last):
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\gateway.py", line 299, in _response_loop
func(resp)
File "C:\Users\Orytel\Desktop\MudaeAutoBot-4\MudaeAutoBot.py", line 686, in on_message
user = bot.gateway.session.user
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\session.py", line 42, in user
return self.settings_ready['user']
KeyError: 'user'
2022-08-29 22:03:46,278:Could not find settings for<PHONE_NUMBER>89873687, please trigger the '$settings' command in the server and run the bot again.

The channeldata folder is empty obtain the $setting text block from mudae
Sent from my iPhone

On Aug 29, 2022, at 5:04 PM, orytel @.***> wrote:

oh my bad seems to work now but im getting this which says just to type $settings on the server and i did but still not working after restarting
Exception ignored in thread started by: <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x000001FBE55B7BA0>>
Traceback (most recent call last):
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\gateway.py", line 299, in _response_loop
func(resp)
File "C:\Users\Orytel\Desktop\MudaeAutoBot-4\MudaeAutoBot.py", line 686, in on_message
user = bot.gateway.session.user
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\session.py", line 42, in user
return self.settings_ready['user']
KeyError: 'user'
2022-08-29 22:03:46,278:Could not find settings for<PHONE_NUMBER>89873687, please trigger the '$settings' command in the server and run the bot again.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

so i use $settings and copy and paste the result on channeldata folder ?

With the bold asterisk and the correct naming scheme
Sent from my iPhone

On Aug 29, 2022, at 5:11 PM, orytel @.***> wrote:

so i use $settings and copy and paste the result on channeldata folder ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

i guess the issue is because the $lang aint eng have u tried it on other lenguages ?

No it works in any language there are several mudae players that are playing non English version of mudae
Sent from my iPhone

On Aug 29, 2022, at 5:31 PM, orytel @.***> wrote:

i guess the issue is because the $lang aint eng have u tried it on other lenguages ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

does not make any sense then shouldnt this be fine ?
"Configurações do Server
Server Premium I
Prefix":$ ("$prefix)
Lang":"pt-br ($lang)
Claim reset":"cada 120 min. ($setclaim)
Minuto exato do reset":"xx":"28 ($setinterval)
Reset alterada":"por +0 min. ($shifthour)
Rolls por hora":"15 ($setrolls)
Tempo antes da reação dos rolls sumir":"45 sec. ($settimer)
Raridade de spawn para personagens já casados":"6 ($setrare)
Server game mode":"1 ($gamemode)
Channel instance":"1 ($channelinstance)
Slash commands":"ativado ($toggleslash)
Ranking":"ativado ($toggleclaimrank/$togglelikerank)
Ranks exibidos durante os rolls":"claims e likes ($togglerolls)
Séries de Hentai":"desativado ($togglehentai)
Séries com imagens""Gore":"ativado ($toggledisturbing)
Rolls sniping":"0 ($togglesnipe)
Kakera sniping":"0 ($togglekakerasnipe)
Limite de caracteres por harém":"8100 ($haremlimit)
Reacts":"apenas para wishes públicas ($togglereact)
Reações personalizadas":"não ($claimreact)
Trade de Kakera":"ativado ($togglekakeratrade)
Cálculo de Kakera":"claim e like rank (e número de personagens casados) ($togglekakeraclaim/$togglekakeralike)
Valor de kakera exibido durante os rolls":"ativado ($togglekakerarolls)
$kakeraloot wishprotect":"ativado ($togglewishprotect)"

so now this should be a discum issue ?
Exception ignored in thread started by: <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x0000018161A87CD0>>
Traceback (most recent call last):
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\gateway.py", line 299, in _response_loop
func(resp)
File "C:\Users\Orytel\Desktop\MudaeAutoBot-4\MudaeAutoBot.py", line 686, in on_message
user = bot.gateway.session.user
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\session.py", line 42, in user
return self.settings_ready['user']
KeyError: 'user'

so now this should be a discum issue ?
Exception ignored in thread started by: <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x0000018161A87CD0>> Traceback (most recent call last): File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\gateway.py", line 299, in _response_loop func(resp) File "C:\Users\Orytel\Desktop\MudaeAutoBot-4\MudaeAutoBot.py", line 686, in on_message user = bot.gateway.session.user File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\session.py", line 42, in user return self.settings_ready['user'] KeyError: 'user'

Go to your discum package folder: /discum/gateway/types.py. Add some type under channelTypes. For instance:
channelTypes = {
0: "guild_text",
1: "dm",
2: "guild_voice",
3: "group_dm",
4: "guild_category",
5: "guild_news",
6: "guild_store",
10: "guild_news_thread",
11: "guild_public_thread",
12: "guild_private_thread",
13: "guild_stage_voice",
14: "type_14",
15: "type_15"
}
more info in here https://github.com/vivinano/MudaeAutoBot/issues/137
but that should fix it

You need to the the bold asterisk as needed
Sent from my iPhone

On Aug 30, 2022, at 2:19 PM, orytel @.***> wrote:

done but still getting same error aswell for the server $settings error shouldnt it look like smtg like this ?
"Prefix":$ ("$prefix)
Lang":"pt-br ($lang)
Claim reset":"cada 120 min. ($setclaim)
Minuto exato do reset":"xx":"28 ($setinterval)
Reset alterada":"por +0 min. ($shifthour)
Rolls por hora":"15 ($setrolls)
Tempo antes da reação dos rolls sumir":"45 sec. ($settimer)
Raridade de spawn para personagens já casados":"6 ($setrare)
Server game mode":"1 ($gamemode)
Channel instance":"1 ($channelinstance)
Slash commands":"ativado ($toggleslash)
Ranking":"ativado ($toggleclaimrank/$togglelikerank)
Ranks exibidos durante os rolls":"claims e likes ($togglerolls)
Séries de Hentai":"desativado ($togglehentai)
Séries com imagens""Gore":"ativado ($toggledisturbing)
Rolls sniping":"0 ($togglesnipe)
Kakera sniping":"0 ($togglekakerasnipe)
Limite de caracteres por harém":"8100 ($haremlimit)
Reacts":"apenas para wishes públicas ($togglereact)
Reações personalizadas":"não ($claimreact)
Trade de Kakera":"ativado ($togglekakeratrade)
Cálculo de Kakera":"claim e like rank (e número de personagens casados) ($togglekakeraclaim/$togglekakeralike)
Valor de kakera exibido durante os rolls":"ativado ($togglekakerarolls)
$kakeraloot wishprotect":"ativado ($togglewishprotect)"
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

can you show me what a functioning one looks like ?

There is one in the code of a functioning settings I think but if not there several in closed issues
Sent from my iPhone

On Aug 30, 2022, at 3:00 PM, orytel @.***> wrote:

can you show me what a functioning one looks like ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

still gettings same error for these did i miss something ?
_ __ ** Configurações do Server**_ __
Server Premium I
· Prefix: $ ($prefix)
· Lang: pt-br ($lang)
· Claim reset: cada 120 min. ($setclaim)
· Minuto exato do reset: xx:28 ($setinterval)
· Reset alterada: por +0 min. ($shifthour)
· Rolls por hora: 15 ($setrolls)
· Tempo antes da reação dos rolls sumir: 45 sec. ($settimer)
· Raridade de spawn para personagens já casados: 6 ($setrare)
· Server game mode: 1 ($gamemode)
· Channel instance: 1 ($channelinstance)
· Slash commands: ativado ($toggleslash)
· Ranking: ativado ($toggleclaimrank/$togglelikerank)
· Ranks exibidos durante os rolls: claims e likes ($togglerolls)
· Séries de Hentai: desativado ($togglehentai)
· Séries com imagens 'Gore': ativado ($toggledisturbing)
· Rolls sniping: 0 ($togglesnipe)
· Kakera sniping: 0 ($togglekakerasnipe)
· Limite de caracteres por harém: 8100 ($haremlimit)
· Reacts: apenas para wishes públicas ($togglereact)
· Reações personalizadas: não ($claimreact)
· Trade de Kakera: disabled ($togglekakeratrade)
· Cálculo de Kakera: claim e like rank (e número de personagens casados) ($togglekakeraclaim/$togglekakeralike)
· Valor de kakera exibido durante os rolls: ativado ($togglekakerarolls)
· $kakeraloot wishprotect: ativado ($togglewishprotect)

u added ** for bold in txt file right?

yeah the darker ones have the ** it might be something else causing it it's weird

I guess what is the error currently ?

Issues with closing has been fixed now this is a keyword user error so will be closing to keep all user error under 1 issue

If everything else is fixed then it would be a discum issue i haven’t encountered it to fix it
Sent from my iPhone

On Aug 29, 2022, at 6:02 PM, orytel @.***> wrote:

so now this should be a discum issue ?
Exception ignored in thread started by: <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x0000018161A87CD0>>
Traceback (most recent call last):
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\gateway.py", line 299, in _response_loop
func(resp)
File "C:\Users\Orytel\Desktop\MudaeAutoBot-4\MudaeAutoBot.py", line 686, in on_message
user = bot.gateway.session.user
File "C:\Users\Orytel\AppData\Roaming\Python\Python310\site-packages\discum\gateway\session.py", line 42, in user
return self.settings_ready['user']
KeyError: 'user'
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.


AD2020 Update

What does this PR do?

Adds changes made in semester AD2020

Related issues

Merge Checklist:

[ ] The branch is up-to-date (i.e. rebased) with the base branch
[ ] No code style issues (eslint and flow)

Test changes:
-Changed some snapshots to compare them to shallow containers
UI/UX changes:
-join us button in members goes to candidates (as it should)
-solved members issue
-warehouse link changed to roborrego's forked wharehouse repo


[EDQ-417] Created a 'visit date disparity' data quality metric notebook

Changed it so the dataset is imported from the notebooks module - never explicitly written in.

* Finished with the procedure, observation, measurement, drug, and condition table queries and calculations.
Successfully merged all of the dataframes and outputted to a CSV
Created a valid 'other scripts' version of the date disparity check. Essentially removed the unioned_ehr prefixes.

@nishanthpp93 this and PR #458 should be ready for review/merging.

cancel this PR. I am going to add the 'metrics over time' change to this branch

replaced by PR #462 (made sense to put the two updates together since they were related)


Pass Herald.collection#deny functions instead of values

Fixes the following error on startup while using Meteor v1.2.1.
Error: deny: Value for `update` must be a function
    at packages/mongo/collection.js:755:1
    at Array.forEach (packages/es5-shim/.npm/package/node_modules/es5-shim/es5-shim.js:417:1)
    at Function._.each._.forEach (packages/underscore/underscore.js:105:1)
    at [object Object].addValidator (packages/mongo/collection.js:752:1)
    at [object Object].Mongo.Collection.deny (packages/mongo/collection.js:804:1)
    at Posts.getNotificationProperties.properties.postAuthorName (lib/herald.js:7:21)
    at /home/sneakertack/work/gh/gh-purple/.meteor/local/build/programs/server/boot.js:249:

Prior to https://github.com/meteor/meteor/pull/5442 this error in the Telescope codebase wasn't being properly caught.

Thanks, I'll work in your changes. BTW, please make future PRs to the devel branch if you can :)


Release Google.Analytics.Admin.V1Alpha version 2.0.0-alpha11

Changes in this release:
Bug fixes

BREAKING CHANGE Update the ReportingAttributionModel enum to rename CROSS_CHANNEL_DATA_DRIVEN to PAID_AND_ORGANIC_CHANNELS_DATA_DRIVEN, CROSS_CHANNEL_LAST_CLICK to PAID_AND_ORGANIC_CHANNELS_LAST_CLICK, CROSS_CHANNEL_FIRST_CLICK to PAID_AND_ORGANIC_CHANNELS_FIRST_CLICK, CROSS_CHANNEL_LINEAR to PAID_AND_ORGANIC_CHANNELS_LINEAR, CROSS_CHANNEL_POSITION_BASED to PAID_AND_ORGANIC_CHANNELS_POSITION_BASED CROSS_CHANNEL_TIME_DECAY to PAID_AND_ORGANIC_CHANNELS_TIME_DECAY, ADS_PREFERRED_LAST_CLICK to GOOGLE_PAID_CHANNELS_LAST_CLICK (commit c79ae51)
BREAKING CHANGE Update the AdsWebConversionDataExportScope enum to rename CROSS_CHANNEL to PAID_AND_ORGANIC_CHANNELS, ADS_PREFERRED to GOOGLE_PAID_CHANNELS (commit c79ae51)

Created release for Google.Analytics.Admin.V1Alpha-2.0.0-alpha11


file.ctime, file.mtime, file.cday, and file.mday returning incorrect dates

What happened?
file.ctime, file.mtime, file.cday, and file.mday returning incorrect and often impossible dates such as 2022-54-27 or 2022-17-15 or 2022-00-15

DQL
TABLE file.ctime as Created, file.mtime as "Last modified"
SORT file.mtime descending

JS
No response
Dataview Version
0.4.21
Obsidian Version
0.14.16
OS
Windows

Any repro instructions? Have you been able to reliably reproduce this in a clean test vault and/or on the current beta?

Huh. After deleting my Obsidian configuration folder (.obsidian) and only installing dataview, the script returns the correct dates. Looks like I have to do some digging on my end.
Thanks for the suggestion. Much appreciated! 🙏


COLTRANE_CONTENT_DIRECTORY setting doesn't work

Hi there! 👋
I set COLTRANE_CONTENT_DIRECTORY to a different value (in my case, help_content) and doing this doesn't change anything. Changing the environment variable to a non-existent directory does nothing, it still reads from content, and renaming the content directory, no matter what the environment variable is set to, makes things crash.
Wanted to make sure and file this bug. If I find time later, I might take a crack at fixing it myself. 🔧

I just tried changing COLTRANE_CONTENT_DIRECTORY in the example app .env file (https://github.com/adamghill/coltrane/blob/main/example_standalone/.env#L10) and I renamed the content directory to help_content and the site loads for me.

If you can provide a PR or a sample app that replicates this issue, let me know. Thanks!

It's been a while, so I'm going to close it. Feel free to re-open if you have a test case I can replicate with.

Sure. Sorry, haven't had the margin to explore it more, I've just left
Coltrane's stuff in the content directory for now. One of these days I
may peg it down. Thanks for this--using it for some user facing
documentation in an internal app!
On May 25, 2024, "netlify[bot]" @.***> wrote:

It's been a while, so I'm going to close it. Feel free to re-open if
you have a test case I can replicate with.

—
Reply to this email directly, view it on GitHub
<https://github.com/adamghill/coltrane/issues/57#issuecomment-
2131707403>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AIDAAI7T4AVHRFDC2XOQDOLZEEPKFAVCNFSM6AAAAABBPB5KTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRG4YDONBQGM>.
You are receiving this because you authored the thread.Message ID:
@.***>


[WIP] Add periodic job for envoy and containerd

This patch add the periodic jobs for envoy and containerd arm
build.

containerd-build-arm64-periodic
envoy-build-arm64-periodic

The links [1] [2] was adding the trigger jobs for each pr of envoy and containerd, and this patch is adding
the periodic job in openlab.
[1] https://github.com/theopenlab/envoy/pull/1
[2] https://github.com/theopenlab/containerd/pull/1

We should add containerd/containerd and envoyproxy/envoy to /etc/zuul/main.yaml, and then restart zuul. but now, there still are many running jobs, so I will recheck after these jobs complete and zuul restart.

Let us to merge this PR after https://github.com/theopenlab/envoy/pull/1 and https://github.com/theopenlab/containerd/pull/1/ are merged.

The job is not loaded, we should restart zuul in production env, but there still are many running jobs.


Not working when used inside an $mdDialog

HI,
I am trying to use the stepper inside an mdDialog. The stepper is getting displayed successfully, but when I click on the continue button, its keep on loading its not opening the next step. Please find the plunker link below.
https://plnkr.co/edit/ixMI8FKbhyTgL5sYieVa?p=preview
Click on the test button to open the mdDialog

It's working.
The instance of MaterialStepper is only available after upgraded.
e.g.
var element = document.querySelector('.mdl-stepper');
var stepper; // element.MaterialStepper == undefined
componentHandler.upgradeAllRegistered();
stepper = element.MaterialStepper;


Add "link" to Invariant Violation: Missing parameter exception

Could the following error message:
Uncaught Error: Invariant Violation: Missing "sampleId" parameter for path "/samples/details/:sampleId"
have a "link" at the end, so it would be
Uncaught Error: Invariant Violation: Missing "sampleId" parameter for path "/samples/details/:sampleId" in link
or something like that to indicate it was on the anchor/link... cause i just spent 2 hours trying to figure out this error thinking it was some rendering/component mistake, lol :3
Anyways... great work on the router, easy and simple, it's fantastic!!

I'm not sure we can even know that. If we can we'll happily add it. Thanks :)


Copying the model to another machine

I have downloaded the model (python -m spacy.en.download) on Windows. Now I'd like to transfer it to another machine, running Linux. Copying the data dir doesn't seem to do the trick. Is there a straightforward way to copy the model without downloading it again?

Hmm, that should work, but we haven't tested that. It's simply not a use-case we thought about yet, but we are not aware that we added anything in the design of the data packages that prevents copying the data dir between platforms. I assume you have good reasons for doing that, still could you please elaborate?
Are you sure you are copying the right path? You can get the data dir with python -c "import sputnik; print(sputnik.default_data_path('spacy'))".
 Does it understand that the model is already installed?

It has to do with using a mobile internet connection. I get the following error after copying data/:
RuntimeError                              Traceback (most recent call last)
/my/projects/spacy/transform.py in <module>()
	16
	17
---> 18 nlp = spacy.en.English(parser=False, tagger=False, matcher=False, entity=False)
	19
	20 transform( 'sample.txt', 'sample_out.txt' )

/usr/local/anaconda/lib/python2.7/site-packages/spacy/language.pyc in __init__(self, data_dir, vocab, tokenizer, tagger, parser, entity, matcher, serializer, load_vectors, package, vectors_package)
	223         if package is None:
	224             if data_dir is None:
--> 225                 package = util.get_package_by_name()
	226             else:
	227                 package = util.get_package(data_dir)

/usr/local/anaconda/lib/python2.7/site-packages/spacy/util.pyc in get_package_by_name(name, via)
	28         raise RuntimeError("Model %s not installed. Please run 'python -m "
	29                            "spacy.en.download' to install latest compatible "
---> 30                            "model." % name)
	31     except CompatiblePackageNotFoundException as e:
	32         raise RuntimeError("Installed model is not compatible with spaCy "

RuntimeError: Model None not installed. Please run 'python -m spacy.en.download' to install latest compatible model.

When attempting to download (as root):
# python -m spacy.en.download
Model already installed. Please run 'python -m spacy.en.download --force' to reinstall.

Ok, understood.
I'd like you to run a few commands and share the output here to get a better view on your system:

run as root and as non-root:
python -c "import spacy; print(spacy.about.__version__)"

run as root and as non-root:
python -c "import sputnik; print(sputnik.util.default_data_path('spacy'))"

run as root and as non-root:
python -m sputnik --name spacy find

Generally it is recommended that you download/install spaCy and the model with the same user with which you later run code. Why? Because spaCy stores its model by default in the Python path which is sometimes different. Otherwise, it's also not unlikely you could end up with two different spaCy versions which complicates matter further.

Yes, I installed spacy on Windows via conda, using the method provided in the instruction. Here's the output on Linux (spacy installed by root):
# python -c "import spacy; print(spacy.about.__version__)"
0.100.6

$ python -c "import spacy; print(spacy.about.__version__)"
0.100.6

# python -c "import sputnik; print(sputnik.util.default_data_path('spacy'))"
/usr/local/anaconda/lib/python2.7/site-packages/spacy/data

$ python -c "import sputnik; print(sputnik.util.default_data_path('spacy'))"
/usr/local/anaconda/lib/python2.7/site-packages/spacy/data

# python -m sputnik --name spacy find
[
{
	"name": "en",
	"version": "1.0.9"
}
]

$ python -m sputnik --name spacy find
[]

As root, I can run this successfully:
# python -c "import spacy; nlp = spacy.en.English(parser=False, tagger=False, matcher=False, entity=False)"

The script I have produces a segmentation fault afterwards, any idea why?
import io
import spacy

from spacy.tokens.doc import Doc

def transform( in_file, out_file ):

	global nlp

	with io.open( out_file, 'w', encoding='utf8') as o_f:
		with io.open( in_file, 'rb' ) as i_f:
			for byte_string in Doc.read_bytes( i_f ):
				doc = Doc( nlp.vocab ).from_bytes( byte_string )
				doc.is_parsed = True
				o_f.write(transform_doc( doc ))

nlp = spacy.en.English( parser=False, tagger=False, matcher=False, entity=False )

transform( 'sample.txt', 'sample_out.txt' )

Great, it seems we can conclude that copying model files over from Windows to Linux seems to work if the user on Linux is root.
Now, why doesn't this work as non-root? To me this looks like a permission problem.
In your setup both root and non-root share the same data directory: /usr/local/anaconda/lib/python2.7/site-packages/spacy/data. Depending on your umask setting files created by root can't be read by non-root.
Can you please check that all files under /usr/local/anaconda/lib/python2.7/site-packages/spacy/data are readable by non-root?
For the segmentation fault please open a separate ticket - it seems to be not related to original issue, correct?

OK, thanks.