Add variables

Description of the Change
At long last, this PR adds support for snippet variables.
Variables have been a part of snippets since TextMate invented them. They’ve also been supported in Sublime Text and VSCode for ages, and probably other editors. And variable support is part of the LSP specification for snippets.
This PR is based partly on @Aerijo's pull request from 2019. I borrowed some tests from that PR, and I decided that it was best to start with its overhauled PEGjs file that could already parse all the new constructs. I felt safe doing this because the overhaul ended up passing all of the existing body-parser-spec.js tests, not to mention other tests that would’ve started failing if there were any subtle parser regressions.
Otherwise, the code is my own. For the variables and other features that VSCode added, I copied their exact implementation where possible, since the LSP spec itself doesn’t provide a sample implementation.
README updates
I added documentation for the new feature to this package's README. While I was at it, I figured I might as well replace all mentions of “Atom” with “Pulsar” and make various other custodial changes.
Not yet implemented
Choice syntax
This gets us practially full compatibility with the LSP spec, but the one main absence is the “choice” syntax where a snippet can define an enum of possible values like ${1|one,two,three|}. The idea is that the IDE’s autocompleter will pop up to invite the user to choose between them.
I’m fine with this in concept, but it’s a bit too much to bite off in this PR, so I did the same thing @Aerijo did: make it so that we grok choice syntax, but translate it to something we can support. For instance, ${1|one,two,three|} for now will be treated exactly like ${1:one} — the first choice is treated as placeholder text. In the future, when we can support this more robustly, this fallback behavior will still be useful in situations where the user has disabled autocomplete-plus.
UUID variable
VSCode supports $UUID in a snippet for generating a new UUID each time it’s invoked. I have no problem with this behavior, but I didn’t want to introduce a new dependency for something so obscure.
Luckily, Node defines randomUUID in the built-in crypto package. Unluckily, it was added in v14.17, and we’re currently on v14.16. But I hear we’ll be able to upgrade to a newer Electron version quite soon, so I decided to make UUID support contingent upon the existence of that method. If it exists, we add a resolver for $UUID. That means we’ll get new functionality automatically when Electron gets upgraded.
Comment-related variables
VSCode defines $BLOCK_COMMENT_START, $BLOCK_COMMENT_END, and $LINE_COMMENT for language-agnostic usage of comments inside snippets. We’re close to being able to support this, but the way this is handled right now is via scoped settings that define only editor.commentStart and sometimes editor.commentEnd. To oversimplify: we usually know only the line-comment syntax for a given scope, not the block-comment syntax.
@Aerijo suggested that this data be tied more closely to the grammar in this proposed RFC. I think we should use this approach, but keep the data within scoped settings files.
But I’ll open a separate issue to explain exactly why.
Alternate Designs
I really do admire the aforementioned PR, but I decided to avoid its pitfalls by making this change as incremental as possible. I’m sure there are other good ideas present in its changes, and if so I think we can adopt them incrementally in future PRs.
Benefits
Here are some examples of snippets that are now possible:
$TM_SELECTED_TEXT$0

Select some text, invoke this snippet via key shortcut, and have that text wrapped in an anchor tag. The contents of the clipboard are assumed to be the URL.
**${1:${TM_SELECTED_TEXT}}**$0

VSCode defines this one (and the italic equivalent) for Markdown files: select text and make it bold with a keystroke. Or, if no text is selected, it’ll insert ** delimiters on either side of the cursor.
## $CURRENT_YEAR-$CURRENT_MONTH-$CURRENT_DAY

Do you mantain a changelog file in Markdown format? Give that a tab trigger and you’ve got a simple way to generate a heading for today’s date.
Possible Drawbacks
I can’t think of any. All the tests pass and there won’t be any performance regressions.
Applicable Issues
Closes #9.

Not something that needs to be addressed instantly but if this is new functionality we want to make sure we document it in the Pulsar docs as well. Happy to do it myself using the content from the readme, this is really just to make sure we have it on the radar somewhere.
Currently we have https://pulsar-edit.dev/docs/launch-manual/sections/using-pulsar/#snippets which will need to be updated.

Yeah, also happy to do that. Tabstop transformation never even got documented after I added it way back when, so it'll feel good to cover that as well.

At a glance the changes here look awesome, even if a bit in depth. I'd like to take more time to take a good read through everything here. But anyways this is fantastic! And glad to see new features coming about. The work is very much appreciated! And just to make sure we get enough eyes on this one since it is a bit bigger @pulsar-edit/core @pulsar-edit/packages

Just found a bug when doing some other work: when a snippet is invoked via tab trigger, the package selects the typed prefix so that it will be replaced when the editor inserts the snippet body. But it wasn't selected when the user pressed Tab, so it shouldn't show up in $TM_SELECTED_TEXT. In fact, $TM_SELECTED_TEXT will always be '' when a snippet is invoked via tab trigger.
Wrote a fix and a new spec to cover this case. The download server is acting up, so we'll have to try CI again when it's fixed.

Just popping in to say: I don't know much about snippets, and all of the diff in this PR is around stuff that's totally new to me, so I don't think I'd be able to provide much timely and meaningful feedback on this one, sorry.

Just popping in to say: I don't know much about snippets, and all of the diff in this PR is around stuff that's totally new to me, so I don't think I'd be able to provide much timely and meaningful feedback on this one, sorry.

Yeah, I fear that this will take a while to review just because few who regularly use Pulsar are familiar with this feature, or else they'd have clamored for its inclusion by now. :)
Maybe the acceptance criteria can be as simple as trying some of the snippets in the unit tests in both Pulsar in VSCode and asserting that they work roughly identically.

Just popping in to say: I don't know much about snippets, and all of the diff in this PR is around stuff that's totally new to me, so I don't think I'd be able to provide much timely and meaningful feedback on this one, sorry.

Yeah, I fear that this will take a while to review just because few who regularly use Pulsar are familiar with this feature, or else they'd have clamored for its inclusion by now. :)
Maybe the acceptance criteria can be as simple as trying some of the snippets in the unit tests in both Pulsar in VSCode and asserting that they work roughly identically.

I think this is probably the best thing we can do. Or even seeing that all tests pass is a good sign already, even moreso considering you've added some new specs that ensure the functionality of the new feature.
I'm erroring on the side of a light approval here if I'm not able to find the time to review more in depth.

It's been almost two months. I haven't been lobbying for landing this because I've been, uh, busy with something else, but I think we should make a decision.
If folks want more assurances before we land it, I'm happy to have that discussion. Otherwise I'll be requesting that “light approval” that @confused-Techie mentioned.

Well, if it works, I agree on adding them.
Only one thing: these pascalcase for example, can we add some testcases for them too?

Only one thing: these pascalcase for example, can we add some testcases for them too?

There's a new test for the casing flags.

OK, I'm going to merge this PR sometime this week. Speak now or forever hold your peace!


Restrict Authentication to @Auth { allow: owner } on a object created via PostConfirmation authorization trigger.

Which Category is your question related to?
API AppSync Authorization
Amplify CLI Version
latest
Description
I have a Lambda PostConfirmation trigger, triggered when a user does the sign-up. On that trigger, I save some user-related information to a Dynamo table via AppSync Client.
At the User Schema level, I want to restrict the allowed rule to the 'owner' type, to not allow any other authenticated user to do operations on other objects they don't own.
Since the initial 'create user' operation is done via AppSync from Lambda using the IAM role, the authenticated user is not an owner of the object, and when the user performs operations for that object when it's authenticated,  it gets the Unauthorized Exception.
Here is the Schema definition:
type User
  @model
  @auth(
    rules: [
      { allow: public, operations: [create], provider: iam }
      { allow: owner, provider: userPools }
    ]
  ) {
  extId: String! @index(name: "byExtId", queryField: "userByExtId")
  email: String! @primaryKey
  country: String!
  firstName: String!
  lastName: String!
  yearOfBirth: Int!
  owner: String!
}

The owner is set at the Lambda level also, when the creation is done.
Any advice please?

Solution:
In my case, I had to set to the owner, the Cognito ID, like: owner: attributes?.sub?.trim().
Previously,  the email was used.
await appsyncClient.mutate({
     mutation: gql(createUserMutation),
     variables: {
       input: {
         firstName: attributes?.given_name?.trim(),
         lastName: attributes?.family_name?.trim(),
         country: attributes?.address?.trim(),
         yearOfBirth: attributes?.profile ? Number(attributes.profile.trim()) : undefined,
         email: attributes?.email?.trim(),
         extId: attributes?.sub?.trim(),
         owner: attributes?.sub?.trim(),
       },
     },


503 Service unavailable - https://jpa.kapsi.fi/nanopb/download/

Hi, I can't download nanopb from https://jpa.kapsi.fi/nanopb/download/.
Please help check it out.

I'm able to download nanopb 0.4.0 from that page.


Multiple charts only works for column chart

Tried to generate multiple Line chart but it throws this error TypeError: Cannot set property 'c:ser' of undefined

Tried to generate multiple chart with multiple types, but I got error:
node:events:495 Uncaught TypeError: o.c:chartSpace.c:chart.c:plotArea[chartTagName].push is not a function


remove CustomImportOrder

What is the purpose of the change
Remove unnecessary rules： https://github.com/apache/incubator-dubbo/issues/2980
Brief changelog
checkstyle.xml
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #2982 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2982      +/-   ##
==========================================
- Coverage   63.95%   63.92%   -0.04%
==========================================
  Files         584      584
  Lines       26059    26059
  Branches     4562     4562
==========================================
- Hits        16666    16657       -9
- Misses       7217     7222       +5
- Partials     2176     2180       +4

Impacted Files
Coverage Δ

...ache/dubbo/remoting/transport/AbstractChannel.java
37.5% <0%> (-50%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
37.5% <0%> (-4.17%)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
63.04% <0%> (-2.18%)
:arrow_down:

...rg/apache/dubbo/common/timer/HashedWheelTimer.java
60.62% <0%> (-1.75%)
:arrow_down:

...pache/dubbo/registry/support/AbstractRegistry.java
80.07% <0%> (-1.13%)
:arrow_down:

...pache/dubbo/remoting/transport/AbstractServer.java
47.91% <0%> (-1.05%)
:arrow_down:

...he/dubbo/registry/multicast/MulticastRegistry.java
65.08% <0%> (+1.29%)
:arrow_up:

...he/dubbo/remoting/transport/netty/NettyServer.java
71.42% <0%> (+3.57%)
:arrow_up:

...onfig/spring/extension/SpringExtensionFactory.java
84.61% <0%> (+5.12%)
:arrow_up:

Continue to review full report at Codecov.

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


AuthInfo Error on sfdx force:apex:test:run

Summary
Suddenly, whenever I click the run test link in an Apex Unit Test, or run any variants of the sfdx force:apex:test:run command, the process exits with an error value (1) and prints the message ERROR:  Cannot create an AuthInfo instance that will overwrite existing auth data.
I removed authorization for the default org (sfdx force:auth:logout) and then authorized it again, and still the same error.
I am running the current version of sfdx and all plugins:
@salesforce/plugin-generator 1.0.1 (core)
@salesforce/sfdx-trust 2.1.0 (core)
builtins 1.0.0 (core)
salesforcedx 45.4.1

What steps can I take to remedy? Obviously I can try uninstalling / reinstalling SFDX but that seems rather brute force for something that was working only a few days ago.

I also started receiving this error today on certain CLI commands.

@alpha-bytes @dalden-calepa-salesforcedx, we just made an update that should fix this. Would you please update your CLI and try again?

This seems to have done the trick - thank you!


Documented command name utilizes underscores, however only dashes work for me

Use of  inventree_part_import  as documented:

$ inventree_part_import
inventree_part_import: command not found

inventree-part-import works however

Thanks, fixed.


Async chunk unexpectedly merged with split chunks

Bug report

What is the current behavior?
In some conditions, webpack does not output an async chunk for a module imported with import(), but merges it with split chunks.
If the current behavior is a bug, please provide the steps to reproduce.

git clone https://github.com/cdoublev/webpack-issue
npm i
npm run build

./dist will contain common.js, main.js, runtime.js.
If you remove at least one 1 (byte) in src/pages/home.js and retry npm run build, or if you revert the change from #18750 (included in webpack@5.95.0), ./dist will also contain pages/home.js.
What is the expected behavior?

./dist should contain the async chunk pages/home.js.
Other relevant information:
webpack version: 5.95.0
Node.js version: 22.9.0
Operating System: Windows 10
Additional tools:

Hi @cdoublev and Webpack team,
I'm new to open-source contributions and came across this issue. I was able to reproduce the bug as described, and here’s a summary of my findings:
Issue Summary: Webpack was merging the pages/home.js module with other chunks instead of creating a separate async chunk, resulting in unexpected behavior during the project build.
Steps Taken:

I modified webpack.config.js by setting mode to production and updating the splitChunks settings to adjust chunking thresholds.
After rebuilding, pages/home.js was successfully generated as a separate async chunk, which resolved the issue.

Suggested Solution: To achieve the expected behavior, the following splitChunks configuration worked:
splitChunks: {     chunks: 'all',     minSize: 1000,     maxSize: 20000, }
Let me know if there’s any additional information or further testing I can assist with. I’d be happy to help!

Thanks for digging in. SplitChunksPlugin is intended for gathering common dependencies between chunks. I think it should not remove entry/normal chunks. Am I wrong?

Thank you for your feedback! I understand that SplitChunksPlugin should primarily gather common dependencies without impacting entry chunks. Here’s the updated configuration:
splitChunks: {     chunks: 'async',     minSize: 1000,     maxSize: 20000,     name: 'common' },
Please let me know if this approach aligns with the intended functionality, or if there’s anything more specific you’d recommend!

I'll try to look at this soon, accidentally missed the report


ck.list_all_files() with 'limit' specified doesn't work as expected

Two issues with ck.list_all_files() with limit set:

limit is not passed internally to recursive calls. This means if you're listing files from a directory with sub-directories, the results will be unlimited.

the function actually returns limit+1 items.

Should be fixed.


provide licence info with release

maybe the user should be able to read both the metamorpheus license and the thermo license if they like from within the program. In GUI, from the help menu and from the CMD with -l ?

merged with #1811


Make stuff look pretty

I've lost track of what changes were made so I'm just going to dump the screenshots here. This all works without issue in Classic.

Oh and for completeness:


Makes items dropped while in a locker go into the locker

About the PR

Fixed unintended behaviour where items dropped while inside a locker went onto the floor, rather than into the locker's storage. Maybe fixes #17230?
Why / Balance

Bug bad.
Technical details

Game was trying to insert items into the locker twice. I don't fully understand why it was set up this way, but the second attempt saw the item was already in, freaked out, and dropped it on the floor outside the locker. I just made the first insert attempt be conditional on it not taking place in a container, because there's a second one that (I think) does the same thing if you are. I tested it and it didnt give me any errors and worked. If there's a way this should be working other than this, let me know and I'll change it, the hard part was figuring out what was causing it.
Media

[X] 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:

fix: Due to a budget oversight, items dropped while in lockers were teleporting out of the locker. This has now been rectified.

I believe you're not supposed to do RP changelog messages, to make it more clear to users and to shorten the amount they have to read

This works with disposal pipes too, this PR fixes it?

This works with disposal pipes too, this PR fixes it?

Yeah, tested it, works as intended.

superceded


PIL Image Method Deprecation Error

I get the following error when running legofy from the command line: AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
After some quick Googling, it appears that this is an issue with PIL having deprecated this method.

Related with this, I installed legofy using pip in a Ubuntu environment, and still having this error. Example of code from /usr/local/lib/python3.10/dist-packages/legofy/init.py:
def legofy_image(base_image, brick_image, output_path, size, palette_mode, dither):
    new_size = get_new_size(base_image, brick_image, size)
    base_image.thumbnail(new_size, Image.ANTIALIAS)
    if palette_mode:
        palette = get_lego_palette(palette_mode)
        base_image = apply_thumbnail_effects(base_image, palette, dither)
    make_lego_image(base_image, brick_image).save(output_path)


copy pypdf2 to internal system from conda-forge

What's the motivation?

We have this package already: https://anaconda.org/lightsource2-tag/pypdf2/files. Closing the issue.


new wix-custom-labels plugin

@agankarin @roibWix why are we going for a one label to fit them all instead of a specific @maturity label?


Handle loading from local files for MPT

This PR allows the MPT model to be loaded from local files. Without this change, an exception will be thrown by hf_hub_download function if model_id is a local path.

@Narsil can you help review? Thanks!


Grid Table - Filter field loses focus when hovering over other sorting buttons, interrupts user input

OpenUI5 version: 1.71.50, also tested with 1.110.0
Browser/version (+device/version): Edge Chromium 110.0.1587.63, Windows 10 x64 22H2
Steps to reproduce the problem:

Click on the header of a column which has filtering and sorting enabled
In the menu, click on the input field for filter values and start typing
Move mouse pointer and hover over one of the sorting buttons in said menu and try continue typing

What is the expected result?
It is possible to continue typing in the filter field. User input is not interrupted.
What happens instead?
Filter input field loses focus and no longer accepts input until you hover over the filter input field to give it focus again.
Any other information?
Occurs in sap.ui.table.Table. Minor issue, but some users listed this as undesired behavior in case they accidentally move the mouse pointer during typing.
It is possible to observe said behavior in the sample library (e.g. https://openui5.hana.ondemand.com/#/entity/sap.ui.table.Table/sample/sap.ui.table.sample.MultiHeader).

Hello @LukasSanders ,
Thank you for sharing this finding. I've created an internal incident https://support.wdf.sap.corp/sap/support/message/2370012744. The status of the issue will be updated here in GitHub.
Regards,
Plamen Ivanov


ChartJS Definition

Definition Request for Chartjs : http://www.chartjs.org/
As a side note I deleted the current folder as it is only ///referenceing DXChart and should not camp in the chartjs folder. User report : http://stackoverflow.com/questions/25856878/code-for-chartjs-typescript-definition-file

This definitions have already been created  (ChartJS). So... this issue has to be closed?


fix overlay bounds confliction from array

Does any other open PR do the same thing?

NO
What issue is this PR fixing?
Fix for the overlay bounds array conflicts eg: southern latitude exceeds northern latitude caused if you put BottomLeft and TopRight coordinates into array. (iOS was already working. This fix only for ANDROID)
(please link the issue here)
How did you test this PR?

I tested in both Genymotion Emulator;
Android v9.0
ARMv64
and my device running MIUI;
Android v9.0

😻


To add decryption/decompression/encryption/compression for CLE release

Tbl files are zstd compressed + encrypted.
Encryption algorithm is Blowfish CTR with the following parameters:
Key: 16 4b 7d 0f 4f a74c ac d3 7a 06 d9 f8 6d 20 94
IV: 9d 8f 9d a1 49 60 cc 4c

Decryption/Decompression done (with package zstandard unfortunately, didn't find a single script that would avoid the dependency)
Won't do the reencryption/compression as it is not needed.
The processing still needs to be added to the tbl2json and dat2py though.


Identifiers validation failed for dataset Base de datos programa de rescate ECA-Liquefaction correspondiente a México (Recaptura)

Identifier validation failed for the dataset Base de datos programa de rescate ECA-Liquefaction correspondiente a México (Recaptura):

Crawler attempt: 4
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 66
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 66 total records; 66 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3757073/step

New IDs sample:

Old IDs sample:

urn:catalog:ECA:NO APLICA:NO APLICA:0153f782e62e5607fd8977f8e83ec038
urn:catalog:ECA:NO APLICA:NO APLICA:018e6cc892f6ebba2c441a602006b8d2
urn:catalog:ECA:NO APLICA:NO APLICA:06e0e4f286f01c750841fdc04460726c
urn:catalog:ECA:NO APLICA:NO APLICA:0c68aab3ccefa9fcc7bd891281889833
urn:catalog:ECA:NO APLICA:NO APLICA:1087a8d059a0c7d6d0805156282d7bed
urn:catalog:ECA:NO APLICA:NO APLICA:2cb083a855732f4ac1dcd3f2bbe407c6
urn:catalog:ECA:NO APLICA:NO APLICA:398d35f6195ed9c5de8fab0d1da97995
urn:catalog:ECA:NO APLICA:NO APLICA:5a0d4328fc6e95b35c79c58d95b0b84d
urn:catalog:ECA:NO APLICA:NO APLICA:6b22c4933ba7856e986666202b3ba6c5
urn:catalog:ECA:NO APLICA:NO APLICA:71c2a81e4583723cdc97e0d95372478f

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Base de datos programa de rescate ECA-Liquefaction correspondiente a México (Recaptura) : https://doi.org/10.15468/fna7z9.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Base de datos programa de rescate ECA-Liquefaction correspondiente a México (Recaptura):

Crawler attempt: 5
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 66
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 66 total records; 66 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3757192/step

New IDs sample:

Old IDs sample:

urn:catalog:ECA:NO APLICA:NO APLICA:0153f782e62e5607fd8977f8e83ec038
urn:catalog:ECA:NO APLICA:NO APLICA:018e6cc892f6ebba2c441a602006b8d2
urn:catalog:ECA:NO APLICA:NO APLICA:06e0e4f286f01c750841fdc04460726c
urn:catalog:ECA:NO APLICA:NO APLICA:0c68aab3ccefa9fcc7bd891281889833
urn:catalog:ECA:NO APLICA:NO APLICA:1087a8d059a0c7d6d0805156282d7bed
urn:catalog:ECA:NO APLICA:NO APLICA:2cb083a855732f4ac1dcd3f2bbe407c6
urn:catalog:ECA:NO APLICA:NO APLICA:398d35f6195ed9c5de8fab0d1da97995
urn:catalog:ECA:NO APLICA:NO APLICA:5a0d4328fc6e95b35c79c58d95b0b84d
urn:catalog:ECA:NO APLICA:NO APLICA:6b22c4933ba7856e986666202b3ba6c5
urn:catalog:ECA:NO APLICA:NO APLICA:71c2a81e4583723cdc97e0d95372478f

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Base de datos programa de rescate ECA-Liquefaction correspondiente a México (Recaptura) : https://doi.org/10.15468/fna7z9.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Do not include helm ConfigMaps by default

they probably contain (gziped, base64 encoded) secrets
It's kind of a shame not to capture them in a backup but I can't have (even very obfuscated) secrets in my backup repo, plus with the versioning there may be quite a few.
While in principle secret values could be included as a Secret out of band (as with the install instructions of kube-backup) and not need to be part of values, this loses the one and done nature of helm install, so most (all?) official charts do not follow this pattern and instead do last mile injection via a values.yaml that is saved in whole as part of the ConfigMaps :(

With more support of e.g. https://github.com/skuid/helm-value-store this could change but for now its probably best not to back them up by default
(Warning: I am opening this PR before fully testing, but its pretty straightforward so I thought I'd get it on your plate first and test now)

This doesn't look like it will break anything (and if it does, it will break apps deployed by a system that should have reproducable deployments).
I'm thinking about cleaning up interfaces to the script so these selectors become more more dynamic and natural to the user, but that will require time. That does however also include that i try to restrain myself from adding new env parameters that have no longevity.
I'll certainly follow up on this PR but i'm not sure (yet) this is the right approach. Thanks! :+1:

Will add a feature to add custom labelselectors manually. Thanks for your contribution!


Call hierarchy: missing outgoing calls inside function expression

TypeScript Version:  3.9.2

Search Terms:
Code
const c = function () {
    return {};
};
const b = function () {
    return c();
};
const a = function () {
    return b();
};
a();

Place cursor on a (in const a) and then run "peek call hierarchy" (configured to show outgoing calls).
Expected behavior:
Call to b should be shown.
Actual behavior:

Playground Link:
Related Issues:
If we use function declarations instead of function expressions, this works as expected.

We need some sort of special-casing, at least for consts immediately initialized with functions, and potentially also lets and vars. Work with @rbuckton and @sandersn to see other parts of the compiler/LS where we do similar logic.


Feature: cli flag to skip cache

Description
It looks like there's some kind of cache thing going on.
Seems confusing because none of this tool is extensively documented yet.

> comtrya apply --no-cache

Additional information
Add more context which didn't fit in the fields above.

Hmm. We don't have a cache in place oO

Maybe cache isn't the right word, but there's clearly logic in all the actions that determine if it should take action or not.
I see output in the terminal that indicates it decided to not copy files because they haven't changed or something like that.

@airtonix There's no cache, but we perform a plan step before we execute our "atoms".
Atoms are individual actions on your machine.
Example:
When you do file.copy, that's actually a touch FILE, write contents to file, and chmod of the file.
If the file exists, we don't touch.
If the contents are the same, we don't rewrite them
If the mods are what we expect, we don't reset them
If you have a valid use-case for skipping plan checks, please reopen with further details.


feat[next][dace]: generic symbolic expressions as fieldop args

This PR adds support for symbolic expressions as field-operator arguments. This is needed to support expressions like (0 - 4) which is used in GTIR to represent the negative value -4.

I will update this PR with support for generic scalar arguments.


running into CORS or Access-Control-Allow-Origin issues

@zaccharles
on OSX, if I open frontend/client.html directly I get:
Origin null is not allowed by Access-Control-Allow-Origin.
so i tried:
python3 -m http.server 7025

then navigate to http://localhost:7024/client.html
and put https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/ in the Step 1 - Enter API URL input box, where i guess the url from the output of serverless deploy :
endpoints:
  GET - https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/signed-url
  GET - https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/signed-post

but then after selecting a file and clicking upload it fails:

on safari:
Fetch API cannot load https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/signed-url due to access control checks.
https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/signed-url

Failed to load resource: Origin http://localhost:7025 is not allowed by Access-Control-Allow-Origin.
client.html:62

on chrome:
Access to fetch at 'https://flimxcxxxx.execute-api.us-east-1.amazonaws.com/dev/signed-url' from origin 'http://localhost:7024' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

note

D20200803T220824
this looks relevant: https://www.serverless.com/blog/cors-api-gateway-survival-guide
is this related to       'Access-Control-Allow-Credentials': true, ?

Hi @timotheecour,
I mentioned CORS a couple of times in the blog post. You definitely need to configure it otherwise I'd definitely expect you will get a CORS error like that.


Look for correct sources.list.d file for apt::ppa

In Ubuntu 15.10 the path of the apt sources file, which is generated by
apt-add-repository, changed to include the distid. This breaks apt::ppa
idempotency, since it does not recognize the repository is already
added.
Reported on puppet-users as well:
https://groups.google.com/forum/#!topic/puppet-users/YzeMyZYUo98

This has broken the tests.

@imphil thanks for the work, it does need rebased.

sorry, i know it is annoying.

@tphoney , don't worry. I just didn't find time to get into the details of how to run the tests, as they still fail and need to be adjusted. Maybe this week.

I appreciate the effort :+1:

Here we go. Please let me know if that's OK or if other changes are needed.

The code looks good to me @imphil. I am not an expert in apt, so i will get this raised in the community meeting tomorrow. Where it will be reviewed. Thanks again for the work !!

It seems alright to me but we'd need to check on the Beaker tests before merging this.

@tphoney @daenney Acceptance tests appear to run clean on PCCI. https://ci.voxpupuli.org/buildlogs/puppetlabs+puppetlabs-apt+582+1454517856+PASS


Can't find city

Hi everyone!
Thanks for using our app!
Please post here to add new cities in this format:

City: Hong Kong
Country: Cn
Timezone: Asia/Hong_Kong
Offset: +08:00

Or simply: Hong Kong, CN and I`ll do the rest.

Jeddah, SA from @bocciaman
Hong Kong, CN from @ExHongKonger

City: Sapporo
Country: Japan
Timezone: Asia/Japan
Offset: +09:00
IATA: CTS

City: Timbuktu
Country: Mali
Timezone: Africa/Mali
Offset: 0:00
IATA: TOM

City: Busan
Country: South Korea
Timezone: Asia/Korea
Offset: +09:00
IATA: PUS

City: Tehran
Country: Iran
Timezone: Mid-East
Offset: +03:30
IATA: IKA

City: Kolkata
Country: India
Timezone: India
Offset: +05:30
IATA: CCU
Note: Calcutta (the old name for Kolkata) is in the database

City: Yangon
Country: Myanmar
Timezone: Myanmar
Offset: +06:30
IATA: RGN
Note: Rangoon (the old name for Yangon) is in the database

City: Chennai
Country: India
Timezone: India
Offset: +05:30
IATA: MAA
Note: Madras (the old name for Chennai) is in the database

City: Chittagong
Country: Bangladesh
Timezone: Bangladesh
Offset: +06:00
IATA: CGP

City: Pyongyang
Country: N. Korea
Timezone: Korea
Offset: +09:00
IATA: FNJ

City: Lanzhou
Country: Cn
Timezone: Asia/China
Offset: +08:00
IATA: LHW

City: Osaka
Country: Japan
Timezone: Asia/Japan
Offset: +09:00
IATA: KIX

City: Daegu
Country: South Korea
Timezone: Asia/Korea
Offset: +09:00
IATA: TAE

City: Saint Louis
Country: USA
Timezone: Central Time(US & Canada)
IATA: STL

@ExHongKonger @santoshdhanshetti All done.

City: San José, CR
Costa Rica
Central Standard Time (CST) and does not change for daylight savings.
Offset: UTC -6.

Thanks a lot I was able to add Saint Louis. This is an amazing utility.
On Tue, 11 Oct 2022 at 5:44 PM, Alexey Tarutin @.***>
wrote:

@ExHongKonger https://github.com/ExHongKonger @santoshdhanshetti
https://github.com/santoshdhanshetti All done.
—
Reply to this email directly, view it on GitHub
https://github.com/tarutin/hovrly/issues/8#issuecomment-1274588312, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBCEIQPMXPLDVZZIXGGYQDWCVK2BANCNFSM6AAAAAARBJRBGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Regards,
Santosh Dhanshetti
(c) +91<PHONE_NUMBER>
www.santoshdhanshetti.com | www.frontendtechnologies.com

City: Suva
Country: FJ
Timezone: Pacific/Fiji
Offset: +12:00

@darwindogs done
@Stickyhavr done, but US San José more popular. I'l fix it at next update

Thanks. San Jose, California has no accent while San José, Costa Rica does.
In case that would help differentiate them.
If countries that are entirely in one timezone were an option, then you
could choose Costa Rica and leave it at that. Interestingly, searching
Costa Rica shows a town in Mexico which I didn’t know existed until now.
:-) Thanks again.

City: Kuwait City
Country: KW
Timezone: Arabia Standard Time
Offset: +03:00

@Stickyhavr try search like san jose, cr
@winstonjoy done!

City: Kuala Lumpur
Country: MY
Timezone: Asia/Kuala_Lumpur
Offset: GMT+8 (UTC+8)

@d4n3sh done

Awesome. Thank you sir

City: Beijing
Country: Cn
Timezone: Asia/Beijing
Offset: ?

@How2Github done

City: Havana
Country: Cuba
Timezone: America/Havana
Offset: UTC-5

City: Kiev
Country: Ukraine
Timezone: Eastern European Time
Offset: UTC/GMT +2 hours


Build error: multiple definition of std::placeholders::_1 and std::placeholders::_2

Thanks for all the work put into SEAL library.
FYI: I encounter the following error when building:
note: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/13/libstdc++.a(placeholders.o):(.rodata._ZNSt12placeholders2_2E+0x0): multiple definition of `std::placeholders::_2'; /home/user/src/zno-fhe-src/target/x86_64-unknown-linux-gnu/debug/build/zno-seal-src-test-f04cc592cd967030/out/install/lib/libseal-4.1.a(ciphertext.cpp.o):/usr/include/c++/13/functional:295: first defined here
          /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/13/libstdc++.a(placeholders.o):(.rodata._ZNSt12placeholders2_1E+0x0): multiple definition of `std::placeholders::_1'; /home/user/src/zno-fhe-src/target/x86_64-unknown-linux-gnu/debug/build/zno-seal-src-test-f04cc592cd967030/out/install/lib/libseal-4.1.a(ciphertext.cpp.o):/usr/include/c++/13/functional:294: first defined here
          collect2: error: ld returned 1 exit status

This is resolved by building with Clang++ 16.0.6
The error is observed by building with G++ 13.2.0


Hello. Could you send a link to your dataset？

ssd5_optimized_inference_graph.pb

Hi trunghung, they are linked in the acknowledgments. Though there are some better ones out there now.  This paper goes over a few hand ones in section 6 https://arxiv.org/pdf/2006.05927.pdf


build recipe only for cuda

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Do we need a build number change here?

No, we shouldn't need to change the build number.


eth_chainId

How to extend request methods, such as eth_chainId?

Could you please elaborate on what it is you are asking for and trying to do?

Closed so far


Can't active the mod

Hi, the mode is really beautiful! But unfortunately I cant turn on the mod using ctrl + ins on my laptop. I've activated the ctrl option and the toggle both to true. Can you help me?

Hey, could you please provide the .ini you are using?


Binja hangs on auto-analysis, gobbles RAM

Version and Platform (required):

Binary Ninja Version: [e.g. 3.2.3944-dev]
OS: Windows
CPU Architecture AMD64

Bug Description:
During initial auto-analysis, Binja gets stuck on a function and spins, consuming more and more RAM (I let it run for a few hours)
After rolling back to an older version (3.2.3932-dev) this behavior does not occur BUT the following output hits the Log window:
Skipping analysis for function at 0x1400be080 : Exceeds 'analysis.limits.maxFunctionUpdateCount'. If possible, please report this issue.
Analysis update took 97.592 seconds
Skipping analysis for function at 0x1400bdd80 : Exceeds 'analysis.limits.maxFunctionUpdateCount'. If possible, please report this issue.
Skipping analysis for function at 0x1400bcfc0 : Exceeds 'analysis.limits.maxFunctionUpdateCount'. If possible, please report this issue.

The binary is a video game server binary - DayZServer_x64.exe I have uploaded it here https://drive.google.com/file/d/1833KSDwVxT6BR7W7Ev-UC9_YHpG97R2D/view?usp=sharing in an encrypted zip with the password: "binja"

Thanks for reporting this!
Fixed in 3.2.3945-dev.


feat: Add http message signature (RFC9421) based request authentication for allowed sources

This PR supports two types of message signature procedures:

DHKex (X25519 and ECDH-P256) based HMAC-SHA256 signature
Public key based signature (EdDSA and ECDSA-P256)

Additionally, we specified wire protocol and wire format for exposed public keys.

For review, we need to update docs explaining brand-new wire protocol and format for HTTP message signature.

We also implemented new features called "httpsig transition margin", which allows us to solve problems related to key updates. In particular, even if new public keys are published for DHKex at a sender and the latest keys are not yet fetched by a receiver (i.e., the receiver still have stale public keys of the sender), the receiver can still verify the request dispatched from the sender securely.

Supported online registry hosting a list of HTTP message signatures enabled domains, much like the dnscrypt/dnscrypt-resolvers. Unlike the list fetched by clients, the registry for http message signatures enabled domains is referred to by relays and target resolvers.


[Do not merge] Pull request for validation purposes

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Abandoning this PR, since this was done as a way to verify issues with another pull request.


Add out-of-date update recommendation tip

This requires us to update the expected days to the next release and the date of the current release when we fixate a release. That's why the release process is updated too.

I'm not sure if this is a good idea or not or if the implementation looks sensible. Comments welcome.

I think we need to split this up. I agree with introducing a release cycle. As well, although it must always remain optional to upgrade (because code defines consensus), recording it in the binary as part of the release process, measuring against it and displaying a warning when the binary is likely to be outdated could be acceptable, depending on the text.
I am however not sure that this should be a UI tip, because these tips are only displayed on Qt binaries with wallet enabled, whereas the process would be valid for all installations - including wallet disabled and headless instances. I think that the most important bugfixes and protocol updates are happening outside of wallet functionality. We have a facility that displays a warning for pre-release binaries, and I was thinking that perhaps that would be a better vehicle to extend?

I like that idea. Extending GetWarnings() makes sense too; my reading of the code suggests it occurs in more places than just startup, which is why I liked the tips idea.
I'll split this into either two PRs or two commits, based on the preference of any developer who cares to comment (I have no preference). First part: just the date code in headers and release process update. Second part: user notification, including text.

First part: just the date code in headers and release process update.
Second part: user notification, including text.

This sounds like a good plan to me.

I've rebased this on top of #3191 and kept the commits as structured so it's easier to review the changes. This seems like an improvement, but I have mixed feelings about the new header. Moving this to a draft so we're not tempted to merge without squash/rebase.

I'm re-running the i686-win CI step because it failed at downloading a ccache deb.

I think this is feature complete now. Commits need squashing; is there documentation to add?
I'm also interested in feedback on my modifications to the RPC tests. I'm not convinced the implementation is wonderful, but at least it's self-contained.

I've squashed and rebased.


Add QueryConfig to TableConfig with the query timeout setting

Following PR will use this setting as the query timeout

Codecov Report

Merging #5162 into master will decrease coverage by 0.03%.
The diff coverage is 90.90%.

@@             Coverage Diff              @@
##             master    #5162      +/-   ##
============================================
- Coverage     66.02%   65.98%   -0.04%
  Complexity       12       12
============================================
  Files          1050     1051       +1
  Lines         54117    54136      +19
  Branches       8071     8074       +3
============================================
- Hits          35729    35724       -5
- Misses        15734    15769      +35
+ Partials       2654     2643      -11

Impacted Files
Coverage Δ
Complexity Δ

...va/org/apache/pinot/common/config/TableConfig.java
88.51% <88.88%> (+2.74%)
0.00 <0.00> (ø)

...va/org/apache/pinot/common/config/QueryConfig.java
100.00% <100.00%> (ø)
0.00 <0.00> (?)

...er/validation/BrokerResourceValidationManager.java
25.00% <0.00%> (-56.25%)
0.00% <0.00%> (ø%)

...a/manager/realtime/RealtimeSegmentDataManager.java
50.00% <0.00%> (-25.00%)
0.00% <0.00%> (ø%)

...elix/core/relocation/RealtimeSegmentRelocator.java
23.68% <0.00%> (-21.06%)
0.00% <0.00%> (ø%)

.../impl/dictionary/LongOffHeapMutableDictionary.java
52.68% <0.00%> (-15.06%)
0.00% <0.00%> (ø%)

...impl/dictionary/FloatOffHeapMutableDictionary.java
53.76% <0.00%> (-13.98%)
0.00% <0.00%> (ø%)

.../org/apache/pinot/core/startree/StarTreeUtils.java
72.97% <0.00%> (-13.52%)
0.00% <0.00%> (ø%)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
46.34% <0.00%> (-6.10%)
0.00% <0.00%> (ø%)

...config/instance/InstanceAssignmentConfigUtils.java
67.50% <0.00%> (-5.00%)
0.00% <0.00%> (ø%)

... and 21 more

Continue to review full report at Codecov.

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


Add myself to reviewers of some mis code

Please provide a description of this PR:
I think I am qualified to most of the code, so add myself to help review.
Prs reviewed by me https://github.com/istio/istio/pulls?q=is%3Apr+reviewed-by%3Ahzxuzhonghu+
cc @costinm @linsun @howardjohn @nmittler @ericvn

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
95ed5893697ca7211993de518ec6f23dd0cadf6c
link
unknown
/test unit-tests_istio

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

/test unit-tests_istio


Extension hides site-packages directory in workbench explorer

Bug: Notebook Editor, Interactive Window, Python Editor cells

Steps to cause the bug to occur
Install vscode-python. The site-packages directory is no longer accessible from the explorer sidebar as it is hidden.

Actual & Expected behavior
site-packages should be accessible from the sidebar and you should be able to open files from it.

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       N/A
Extension version: 2019.MM.#####-xxx
VS Code version:                                #.##
Setting python.jediEnabled:               true | false
Python and/or Anaconda version:     3.7.4
OS:                                                     Windows
Virtual environment:                          venv | virtualenv

Developer Tools Console Output

@brettcannon this would not be something we modify in the DS code. This is either a core feature or VS code is doing this.

The extension does nothing to the file explorer, so it will be a VS Code issue.


feat(QuestionnaireForm): add support for exists, !=, etc. operators

This PR adds support for the !=, >, >=, <, <=, and exists operators for QuestionnaireItem. See: http://hl7.org/fhir/R4/valueset-questionnaire-enable-operator.html
The FHIR spec is a little unclear about what to do when comparison between types that are "potentially comparable" are made, such as Time and DateTime.
Currently the behavior is to ignore comparisons between types that are "potentially" comparable.
If the two types compared are not exactly equal and if the current answer is not undefined, then a match is not made. If the values are exactly the same type or the answer is undefined then the comparison is performed and the match is made based on the comparison.
This may be something that should be discussed in the future.
Please let me know if I missed anything obvious in this PR.
This closes #2683.

coverage: 94.22% (-0.02%) from 94.236% when pulling 82488df0e926fd98be445aeecccfdf7bb762cb02 on ThatOneBro:derrick/feat/add-questionnaire-exists-support into 41a57f91b07b6f7c1065f8880be4997de1716152 on medplum:main.

Nice! This all looks good. One thought have you tested with an answer with valueCoding? Previously the deepEquals didn't work with it so we may need a specific conditional for it, or perhaps even structuring the comparisons prior

Sure I think I can add some tests for valueCoding, I think we can make sure that the = and != are working properly for it.

Current status: fixing how comparisons are done for certain types of TypedValues under the hood. Finishing #2717 first


ingress catalog link is dead

NG: https://github.com/kubernetes/ingress-nginx/blob/master/docs/catalog.md
OK: https://github.com/kubernetes/ingress-nginx/blob/master/docs/ingress-controller-catalog.md
For example, this page contain dead link.
https://kubernetes.io/docs/concepts/services-networking/ingress/#loadbalancing
Old page is this, so I think its change is correct.
https://github.com/kubernetes/ingress-nginx/blob/nginx-0.12.0/docs/catalog.md
Note:
China page don't have this link.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.11 Features: set Milestone to 1.11 and Base Branch to release-1.11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
Please delete this note before submitting the pull request.

Hello steveperry-53.
Nice to meet you. Please approve :)
I have already checked my changes at deployed staging now.
https://deploy-preview-8736--kubernetes-io-master-staging.netlify.com/docs/concepts/services-networking/ingress/#loadbalancing
NG page now: https://kubernetes.io/docs/concepts/services-networking/ingress/#loadbalancing
/assign @steveperry-53

Great job!
/approve
/lgtm


Make use of gem components where possible

What
Update several instances of custom markup or markup directly from the design system.
Why
This is part of an ongoing effort in the govuk accessibility team to use components in as many places as possible, ensuring that we can more easily deploy bugfixes and accessibility updates across our apps and avoid blind spots in our code coverage.
No visual changes.
Card

🚀

🚀


prettier apex plugin

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes
to run prettier:

Make sure you have yarn installed.
Run yarn install to install development dependencies
Run yarn prettier --check . for warning/error msgs of or yarn prettier --write . to autoformatting all the code.

@MatthewBlanski this should be ready for review.

@spinkelman readme has been updated. If you are interested, feel free to take a look at the branch page: https://github.com/SalesforceFoundation/EDA/tree/feature/232__prettierApexPlugin
fyi @MatthewBlanski @lbeller


asana export 1.1.2 hangs for quite a while after seemingly being finished

Hey @plswiderski
Thanks for this handy tool! 👍
It seems the executable hangs for quite a while after the tasks seemingly is finished.
See here the output
root@973ae5728a14:/app# java -jar /app/asanaexporter.jar "${API_KEY}" "${ORGANISATION}"
 INFO [main] (UserDownloadCommand.java:55) - Downloaded userData.
 INFO [main] (ProjectsDownloadCommand.java:35) - Downloaded 20 projects.
 INFO [main] (Main.java:62) - Start importing tasks from last modification date 2024-03-10T10:39:52.391Z.
 INFO [main] (Main.java:72) - Imported 0 tasks in 8 s.
 INFO [main] (Main.java:75) - Start generate csv.
 INFO [main] (Main.java:77) - Csv file is generated.
 INFO [main] (Main.java:79) - Start writing last modification dateTime.
 INFO [main] (Main.java:81) - Last modification dateTime is written.

Then it hangs for about three minutes.
Looking at the source code I suspect the main process is waiting for the threads to terminate: https://github.com/plswiderski/asanaexporter/blob/fa81d128339b1df3141e968a043a4a7f93c1aa6c/src/main/java/io/bitbucket/pablo127/asanaexporter/Main.java#L68
Is this something that can be tuned a bit?
It's not really a dealbreaker, but perhaps something to improve upon :)
It would at least make testing faster
Thanks for the great work!
Best Regards,
Levi

Hi!
Thank you for your feedback. It is nice that asanaexporter is helpful for you.
I will look into waiting process in the future. Maybe it will be possible to make it faster. Thanks.


Trojan服务器部署完，当天正常第二天就无法使用了，Windows客户端报proxy/trojan: failed to find an available destination / common/retry: all retry attempts failed错误（如图）是怎么回事？服务器上没有做任何改动。

 --客户端日志
/nginxweb/nginx-error.log
2023/11/17 21:58:17 [error] 6804#6804: 174 open() "/nginxweb/html/.env" failed (2: No such file or directory), client: <IP_ADDRESS>, serv
er: kqqkw.., request: "GET /.env HTTP/1.1", host: "13..."
2023/11/17 22:24:55 [error] 6804#6804: 176 open() "/nginxweb/html/Core/Skin/Login.aspx" failed (2: No such file or directory), client: 124.1
56.187.113, server: kqqkw.., request: "HEAD /Core/Skin/Login.aspx HTTP/1.1", host: "13...:80"
2023/11/17 22:28:42 [error] 6804#6804: 177 open() "/nginxweb/html/.env" failed (2: No such file or directory), client: <IP_ADDRESS>, serv
er: kqqkw.., request: "GET /.env HTTP/1.1", host: "13..."
2023/11/17 22:37:40 [error] 6804#6804: 182 open() "/nginxweb/html/js/jquery-3.5.1.slim.min.js" failed (2: No such file or directory), client
: <IP_ADDRESS>, server: kqqkw.., request: "GET /js/jquery-3.5.1.slim.min.js HTTP/1.1", host: "13...", referrer: "http://13.1
14.103.150/"
2023/11/17 22:37:40 [error] 6804#6804: 183 open() "/nginxweb/html/js/bootstrap.bundle.min.js" failed (2: No such file or directory), client:
<IP_ADDRESS>, server: kqqkw.., request: "GET /js/bootstrap.bundle.min.js HTTP/1.1", host: "13...", referrer: "http://13.114
.103.150/"
2023/11/17 22:37:44 [error] 6804#6804: 180 open() "/nginxweb/html/favicon.ico" failed (2: No such file or directory), client: <IP_ADDRESS>,
server: kqqkw.., request: "GET /favicon.ico HTTP/1.1", host: "13..."
2023/11/17 22:56:22 [error] 6804#6804: 187 open() "/nginxweb/html/.env" failed (2: No such file or directory), client: <IP_ADDRESS>, serv
er: kqqkw.., request: "GET /.env HTTP/1.1", host: "13..."
2023/11/18 00:00:33 [error] 6804#6804: 191 open() "/nginxweb/html/Core/Skin/Login.aspx" failed (2: No such file or directory), client: 124.1
56.187.113, server: kqqkw.., request: "HEAD /Core/Skin/Login.aspx HTTP/1.1", host: "13...:80"
2023/11/18 00:30:26 [error] 6804#6804: 192 open() "/nginxweb/html/.env" failed (2: No such file or directory), client: <IP_ADDRESS>, serve
r: kqqkw.., request: "GET /.env HTTP/1.1", host: "13..."
2023/11/18 00:46:21 [error] 6804#6804: 196 open() "/nginxweb/html/.env" failed (2: No such file or directory), client: <IP_ADDRESS>, serv
er: kqqkw.., request: "GET /.env HTTP/1.1", host: "13..."
2023/11/18 01:35:54 [error] 6804#6804: 202 open() "/nginxweb/html/Core/Skin/Login.aspx" failed (2: No such file or directory), client: 124.1
56.187.113, server: kqqkw.., request: "HEAD /Core/Skin/Login.aspx HTTP/1.1", host: "13...**:80"

https://ping.pe/ 用这个网站测试服务器是否被GFW封端口 可以在服务器修改其他端口试试， trojan 现在被识别的很厉害 换 xray 最新的 XTLS-Vision-REALITY 协议吧

收到，感谢。

发件人: Jin @.>
发送时间: 2023年11月18日 22:34
收件人: jinwyp/one_click_script @.>
抄送: Cheros Peng @.>; Author @.>
主题: Re: [jinwyp/one_click_script] Trojan服务器部署完，当天正常第二天就无法使用了，Windows客户端报proxy/trojan: failed to find an available destination / common/retry: all retry attempts failed错误（如图）是怎么回事？服务器上没有做任何改动。 (Issue #255)
https://ping.pe/ 用这个网站测试服务器是否被GFW封端口 可以在服务器修改其他端口试试， trojan 现在被识别的很厉害 换 xray 最新的 XTLS-Vision-REALITY 协议吧
―
Reply to this email directly, view it on GitHubhttps://github.com/jinwyp/one_click_script/issues/255#issuecomment-1817524848, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2IKVXKIT5OO5YQYZ7AXG7DYFDBPBAVCNFSM6AAAAAA7QTU5UCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGUZDIOBUHA.
You are receiving this because you authored the thread.Message ID: @.***>


Group konflux-ci/tekton-catalog updates

This update will allow noise reduction by grouping quay.io/konflux-ci/tekton-catalog/* tekton updates into a single PR.

@gnaponie do you know why is there both matchPackagePatterns and matchDepPatterns?

@staticf0x check this out: https://github.com/renovatebot/renovate/discussions/14885
I think we should drop matchPackagePatterns. I think it's coming from the old build-service's renovate, I believe we can remove that.
I was actually thinking about filing a card about clearing this conf a little bit, because it comes with a lot of warnings. We can include this too in that card (since this was approved, and it will be merged once the CI completes).

/lgtm
/approve

/lgtm
/approve

What does it take to run the rest of the checks?

Hi @scoheb do you know what is missing to trigger the remaining tests or allow this PR to proceed?

/ok-to-test

/lgtm cancel

/lgtm

/remove-approve

/approve

/ok-to-test

/ok-to-test

/ok-to-test


[stdlib][nfc] Move (most) SDK tests into their own folder.

Similar to how they are in source. Should help clear up confusion about where to route issues. Also renames a handful of tests that were prefixed with Test, as this pattern isn't consistently followed.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - ae40afc78187489164185121d15158c7f9259d16

That HomeKit failure is valid—you're shadowing the HomeKit overlay.

Ah, I'm skipping iOS tests when I ran them locally, duh.

Build failed
Swift Test OS X Platform
Git Sha - ae40afc78187489164185121d15158c7f9259d16

While we're at it, I think the overlay tests that are in validation-test should not be there, and are most of the time just "-typecheck -verify" tests. Why don't we just move them all in either test or validation-test? Since our CI would currently run validation tests for macOS even in "smoke test" mode, I'm slightly in favor of validation-test/SDK as a final destination.

Please don't. Validation tests are over there because they slow down local testing. Ideally everything would be in test/, but in practice the signal-to-(time-and-noise) ratio is low for a handful of things.

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Connect-PnPOnline fails after updating PnP.PowerShell to v2.1.1

Notice
Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:

Are you using Invoke-PnPSiteTemplate or Get-PnPSiteTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues.
Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/powershell/tree/master/src/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/pnpframework/issues

Reporting an Issue or Missing Feature
Please confirm what it is that your reporting
As part of connecting to SharePoint to download files, I've been using "Connect-PnPOnline" and it was working fine, until I updated the "PnP.Powershell" library to v2.1.1
After the update the same PS script which ran successfully fails with the following error:
Error: The 'Connect-PnPOnline' command was found in the module 'PnP.PowerShell', but the module could not be loaded. For more information, run 'Import-Module PnP.PowerShell'.
Expected behavior
Please describe what output you expect to see from the PnP PowerShell Cmdlets
Connect-PnPOnline should be working as before
Actual behavior
Please describe what you see instead. Please provide samples of output or screenshots.
Error: The 'Connect-PnPOnline' command was found in the module 'PnP.PowerShell', but the module could not be loaded. For more information, run 'Import-Module PnP.PowerShell'.
Steps to reproduce behavior
Please include complete script or code samples in-line or linked from gists
Connect-PnPOnline -Url $url -Credentials $cred
What is the version of the Cmdlet module you are running?
(you can retrieve this by executing Get-Module -Name "PnP.PowerShell" -ListAvailable)
v2.1.1
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Had the same issue. For us, it is Add-PnPStoredCredential command and Import-Module does not solve it either. Also opened a discussion ticket here: https://github.com/pnp/powershell/discussions/2964

@Subi-Sri @LiyuanWang123 - v2.1.1 does not support PS5 nor the ISE, you need to use PS7.
If you are still using PS5, you can use v1.12.0 however bug fixes and improvements will only be done on the 2.x releases in the future.

@veronicageek We are using PS7 though.

Thank you!  Turns out I was on PowerShell 5 The $PSversionTable command is handy.  I assumed that I was on 7 since I ran the installer for it without issue.
This time I installed PS 7 from the Microsoft Store and all is well.

Thanks again!


Show flatpak manifest dialog only once

Fixes #50
cc @SeaDve

Tested it and works as intended now for me


GraphQLite is automatically making interface implementations when it shouldn't

Version: 5.0.1
According to https://graphqlite.thecodingmachine.io/docs/inheritance-interfaces, GraphQLite should only make an Impl type when it can't find another type that implements that interface:

If GraphQLite cannot find a proper GraphQL Object type implementing an interface, it will create an object type "on the fly".

However, it does it no matter what on my end:
/**
 * @GraphQL\Type
 */
interface MobileAppInterface
{
	/**
	 * @GraphQL\Field
	 */
	public function getVersionCode(): ?int;
}

/**
 * @GraphQL\Type
 */
class AndroidApp implements MobileAppInterface
{
	public function getVersionCode(): ?int
	{
		// TODO: Implement getVersionCode() method.
	}
}

This generates the following schema:
interface MobileAppInterface {
  versionCode: Int
}

type MobileAppImpl implements MobileAppInterface {
  versionCode: Int
}

type AndroidApp implements MobileAppInterface {
  versionCode: Int
}

@MattBred I've noticed the same thing.  It's a bit harmless, as the interface isn't used, just generated in the schema.  But, it is sloppy and confusing.
A PR on this would be awesome :)

As you can see here:
https://github.com/thecodingmachine/graphqlite/blob/3b97f9d020297658e32833e9b3d49e7b27c650dd/src/Mappers/RecursiveTypeMapper.php#L212-L223
Your type somehow is not yet part of the typeRegistry, might be a ordering issue in the recursive type mapper?

It's probably related to the mapping cache in the RecursiveTypeMapper.  Note that the Interface type names are different.  The implementation around this is shaky.  It mostly works, but an improved design is really needed.

You are right, this seems quite naive. The interface type name is generated in this function called on line 214 above:
https://github.com/thecodingmachine/graphqlite/blob/3b97f9d020297658e32833e9b3d49e7b27c650dd/src/NamingStrategy.php#L31-L34
It should actually check if there is a class in php implementing this interface. At least thats what the docs suggest it does but apparently not.

There are two mappings as well, the actual class and the GQL name.  I don't find that these two mappings work well with each other either.  IMO, we'd benefit from having a single mapping cache that's more robust.

@oojacoboo what do you mean by two mappings?

The RecursiveTypeMapper has:

mappedClasses
classToTypeCache
classToInputTypeCache
interfaceToClassNameMap

I found it frustrating to work with all of these different maps and think this responsibility would probably be better left to a mapping abstraction.

I have ran into the same issue, this causes issues when generating types from schema, i have to handle the interface type even though i already know it would be one of N types

A PR on this is certainly welcomed!

You are right, this seems quite naive. The interface type name is generated in this function called on line 214 above:
https://github.com/thecodingmachine/graphqlite/blob/3b97f9d020297658e32833e9b3d49e7b27c650dd/src/NamingStrategy.php#L31-L34
It should actually check if there is a class in php implementing this interface. At least thats what the docs suggest it does but apparently not.

My guess is the code that is commented out here is what is supposed to be skipping this creation if a class implementing that interface exists?
https://github.com/thecodingmachine/graphqlite/blob/069d62a69eeeb97f8559d7623ab137774863e7e0/src/Mappers/RecursiveTypeMapper.php#L328


Support pydantic v1

https://pydanticlogfire.slack.com/archives/C06EDRBSAH3/p1715039582297379
It doesn't have to be rendered nicely, but it shouldn't break.

Another case of this breaking things for a user: https://pydanticlogfire.slack.com/archives/C06EDRBSAH3/p1715089742992309?thread_ts=1715088823.604819&cid=C06EDRBSAH3

Wow, thanks for being so proactive on this!


mv partition union rewrite failed

Desc
When the time partition in the WHERE clause of a query is a proper subset of the materialized view (MV) partitions, the materialized view partition UNION rewrite will fail. The materialized view partition UNION rewrite will only succeed when the WHERE clause of the query includes all the partitions of the materialized view.
Steps to reproduce the behavior (Required)

CREATE TABLE '...'
CREATE database mv_test;
use mv_test;

CREATE TABLE area_dim_table (
area_code bigint(20) NOT NULL COMMENT "",
area_name varchar(256) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(area_code)
DISTRIBUTED BY HASH(area_code)
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT",
"enable_persistent_index" = "false",
"unique_constraints" = "area_code",
"compression" = "LZ4"
);
CREATE TABLE shop_dim_table (
shop_code bigint(20) NOT NULL COMMENT "",
shop_name varchar(256) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(shop_code)
DISTRIBUTED BY HASH(shop_code)
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT",
"enable_persistent_index" = "false",
"unique_constraints" = "shop_code",
"compression" = "LZ4"
);
CREATE TABLE fact_table (
shop_code bigint(20) NOT NULL COMMENT "",
dim_public_date_info_date date NULL COMMENT "",
area_code bigint(20) NOT NULL COMMENT "",
measure_num bigint(20) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(shop_code)
PARTITION BY RANGE(dim_public_date_info_date)
(PARTITION p20240913 VALUES [("2024-09-13"), ("2024-09-14")),
PARTITION p20240914 VALUES [("2024-09-14"), ("2024-09-15")),
PARTITION p20240915 VALUES [("2024-09-15"), ("2024-09-16")),
PARTITION p20240916 VALUES [("2024-09-16"), ("2024-09-17")))
DISTRIBUTED BY HASH(shop_code)
PROPERTIES (
"replication_num" = "1",
"dynamic_partition.enable" = "true",
"dynamic_partition.time_unit" = "DAY",
"dynamic_partition.time_zone" = "Asia/Shanghai",
"dynamic_partition.start" = "-3",
"dynamic_partition.end" = "3",
"dynamic_partition.prefix" = "p",
"dynamic_partition.history_partition_num" = "0",
"in_memory" = "false",
"storage_format" = "DEFAULT",
"enable_persistent_index" = "false",
"foreign_key_constraints" = "(shop_code) REFERENCES default_catalog.mv_test.shop_dim_table(shop_code);(area_code) REFERENCES default_catalog.mv_test.area_dim_table(area_code)",
"compression" = "LZ4"
);
2. INSERT INTO '....'
insert into area_dim_table values(1,'区域1');
insert into area_dim_table values(2,'区域2');
insert into shop_dim_table values(1,'门店1');
insert into shop_dim_table values(2,'门店2');
insert into shop_dim_table values(3,'门店3');
insert into fact_table values(1,'20241009',1,1);
insert into fact_table values(2,'20241009',2,1);
insert into fact_table values(3,'20241009',2,2);
insert into fact_table values(1,'20241010',1,1);
insert into fact_table values(2,'20241010',2,1);
insert into fact_table values(3,'20241010',2,2);
3. CREATE  and refresh MV
CREATE MATERIALIZED VIEW test_fact_all_join_mv
DISTRIBUTED BY HASH(shop_code)
PARTITION BY(dim_public_date_info_date)
REFRESH DEFERRED MANUAL
AS SELECT t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name,sum(measure_num)
from fact_table AS t0
left join area_dim_table AS t1 on t0.area_code=t1.area_code
left join shop_dim_table AS t2 on t0.shop_code=t2.shop_code
group by t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name;
REFRESH MATERIALIZED VIEW test_fact_all_join_mv;
4. insert into
insert into fact_table values(1,'20241011',1,1);
insert into fact_table values(2,'20241011',2,1);
insert into fact_table values(3,'20241011',2,2);
5.SELECT
-- rewrite失败
TRACE REWRITE SELECT t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name,sum(measure_num)
from fact_table AS t0
left join area_dim_table AS t1 on t0.area_code=t1.area_code
left join shop_dim_table AS t2 on t0.shop_code=t2.shop_code
where t0.dim_public_date_info_date in ('20241009','20241011')
group by t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name;
explain SELECT t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name,sum(measure_num)
from fact_table AS t0
left join area_dim_table AS t1 on t0.area_code=t1.area_code
left join shop_dim_table AS t2 on t0.shop_code=t2.shop_code
where t0.dim_public_date_info_date in ('20241009','20241011')
group by t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name;
--rewrite成功
TRACE REWRITE SELECT t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name,sum(measure_num)
from fact_table AS t0
left join area_dim_table AS t1 on t0.area_code=t1.area_code
left join shop_dim_table AS t2 on t0.shop_code=t2.shop_code
where t0.dim_public_date_info_date in ('20241009','20241010','20241010')
group by t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name;
explain SELECT t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name,sum(measure_num)
from fact_table AS t0
left join area_dim_table AS t1 on t0.area_code=t1.area_code
left join shop_dim_table AS t2 on t0.shop_code=t2.shop_code
where t0.dim_public_date_info_date in ('20241009','20241010','20241010')
group by t0.dim_public_date_info_date,t0.shop_code,t0.area_code,t1.area_name,t2.shop_name;
Expected behavior (Required)
Query has already been successfully rewritten by: test_fact_all_join_mv.
Real behavior (Required)
Query cannot be rewritten, please check the trace logs to find more information.
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()
3.1.15

Starrocks v3.3 has optimized union rewrite this a lot, can you try the newest version of StarRocks v3.3?


Document EventGrid and distributed tracing

We should have a Readme section, or a sample, or maybe both, to describe what we do with distributed tracing.
This should include  a lien to https://github.com/cloudevents/spec/blob/master/extensions/distributed-tracing.md
This should explain our auto-magic behavior to populate the extension if we detect the HTTP headers.

Chevron is asking for event tracing capability and visibility through App Insights. Just an FYI.

Added in readme:
https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/eventgrid/azure-messaging-eventgrid/README.md#distributed-tracing


Add support for analytic definition of color function

Description
This PR adds support for analytic definition of the color function in the case file.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Scope

[x] This PR comprises a set of related changes with a common goal

If you cannot check the above box, please split your PR into multiple PRs that each have a common goal.
How Has This Been Tested?
Created an initial condition with an analytical color function

This may not actually work as intended. I'll send a message when I verify it works.

I can confirm this functions as expected. The problems I was seeing are an IO issue on a different branch where I implemented this same feature to accomplish something I needed.


run into error when run the sample code given in step 5

I tried to follow the exercise of step 5 in Runbook TestPane  and run into error like this. could anyone advice how should I proceed?
error :Connect-AzAccount : The term 'Connect-AzAccount' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:12 char:28
the sample code look like this : -
Ensures you do not inherit an AzContext in your runbook
Disable-AzContextAutosave –Scope Process
$connection = Get-AutomationConnection -Name AzureRunAsConnection
Wrap authentication in retry logic for transient network failures
$logonAttempt = 0
while(!($connectionResult) -And ($logonAttempt -le 10))
{
$LogonAttempt++
# Logging in to Azure...
$connectionResult =    Connect-AzAccount                                -ServicePrincipal
-Tenant $connection.TenantID                                -ApplicationId $connection.ApplicationID
-CertificateThumbprint $connection.CertificateThumbprint
Start-Sleep -Seconds 30

}
$AzureContext = Get-AzSubscription -SubscriptionId $connection.SubscriptionID
Get-AzVM -ResourceGroupName myResourceGroup -AzContext $AzureContext

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

ID: 8dcc44c4-9f64-6b0c-e045-0e5e3c567970
Version Independent ID: 6456a6aa-bdeb-651c-0c83-a84d4541f735
Content: Create a PowerShell runbook in Azure Automation
Content Source: articles/automation/learn/automation-tutorial-runbook-textual-powershell.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@fannie666  Thank you for bringing this to out notice, we will look into it and get back to you at the earliest.

thanks so much. I am actually now using 30 days trial of free azure account. everything is just in the portal. I am totally new to azure..hope you could give some advice on this

@fannie666 My sincere apologies for delayed response on this.  One of the possible reasons for the error you see is:

The module that contains the cmdlet isn't imported into the Automation account.
The module that contains the cmdlet is imported but is out of date.

For resolving the error, can you please try one of the following tasks:

For an Azure module, see How to update Azure PowerShell modules in Azure Automation to learn how to update your modules in your Automation account.
For a non-Azure module, make sure that the module is imported into your Automation account.

For additional troubleshooting document please refer here
Hope the above information helps. At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


Drift detection makes CLI output where bold

Intended that the full output is bolded?

That's a question for @Jolg42  — I like the attention drawing bold font for dev diagnostics personally, but I don't know if it's intentional.

The bold text here is from devDiagnostic.action.reason

It's printed as part of the prompt here https://github.com/prisma/prisma/blob/15e1ca308c3e4fe3036d9326f83c27ed1a40c0c9/src/packages/migrate/src/commands/MigrateDev.ts#L322
From what I see the bold comes from passing the text to the "prompts" lib which adds bold to all the text passed.
So not intended I think. We could print the reason independently as console.info and then do the prompt.

Similar is true for the reset:

Let me help with this one, already made the PR at #9329


cleanup: remove duplicate code

Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@Madhu-1 do you see any other duplicate codes which can be moved to util ? if yes, please include those to in this PR.

@humblec currently I can figure out this much, if I found any other code duplication I will send followup PR
@gman0 PTAL


Does not use semver

Checklist
Before submitting this bug report, I ensured that…

[x] I can read
[x] I can reproduce this in an isolated environment (e.g. only CC:T, Create and CC:C Bridge)
[ ] I have uploaded the full logs (We recommend https://mclo.gs/)
[x] the used versions are all still supported and up-of-date
[x] there is no duplicate of this bug

Description

You do not use semver
Users see the following warnings in their log:
[ForkJoinPool-1-worker-4/WARN]: Mod cccbridge uses the version 1.6.2b-fabric which isn't compatible with Loader's extended semantic version format (Could not parse version number component '2b'!), SemVer is recommended for reliably evaluating dependencies and prioritizing newer version
Steps to Reproduce

Launch game

Expected behavior

Use valid semver
Footage

Version

Minecraft v1.20.1
Mod Version 1.6.2b
ModLoader Fabric

Will be fixed with next version


🐛 [BUG] -Typo Error

**there is a typo error in Error 404 page
Instead of oops it written opps
I know its a small error but every conribution counts. So assign me this task**

Well, according to the guidelines given a typo can't be considered as a contribution. Sorry.
Thanks for making me aware about it, really appreciate it.


RxJava 2 support

Currently the library doesn't do RxJava 2. Are there any plans immediately in the works for adding support in for this? I'd be happy to fork and then open a PR if not.

Hello @imperial-crystalline-recursion,
sadly we don't have the migration to RxJava 2 on our time line just now. Please feel free to fork and open a PR, I would be happy to take a look at it, thanks for the suggestion!

@imperial-crystalline-recursion I am happy to inform you, that we have now a released version with RxJava 2. support: https://github.com/contentful/contentful.java/releases/tag/java-sdk-8.0.0 🎉
Please let us know what you think ....


Some Classes not in Doc Search

When using the generated search the class RowToList is not found even though the module documentation for Prim.RowList has been generated.

Thank you for the report!
Unfortunately, Prim.* modules are built-in, they don't have real sources. Pursuit, being a Haskell app, has access to their docs that are constructed specially (see https://hackage.haskell.org/package/purescript-0.13.5/docs/Language-PureScript-Docs-Prim.html)
docs-search app is written in PS and can't link to the purescript compiler to get the data from there.

Thanks

I guess this should be moved to spacchetti/purescript-docs-search#31


Counter of items [Features request]

Issue description
I would like to see a function added that will show us which is the selected rom number from the total number for each system. Example: '2/100' or '2 of 100'. I can't find this option or fuction in batocera.

Hi, Having that data in a new theme binding would be great. We already have the total number data, we just need the number of the selected rom/item.
In the theme we would use both variables and give it the desired format: 1-100 1/100 or 1 of 100 etc.


Add type constructs required to support Immutable.js Records

I have being wondering how one could annotate set, update or merge style functions on immutable records found in Immutable.js
In fact I find I'm not sure how immutable data structures can at all type checked with flow given that there are no syntax for it in JS so the best I could come up with was something along these lines:
var set <Record:Object> = (key:string, value:any, record:Record) => Record;
var update <Record:Object> = (key:string, f:(value:any) => any) => Record;
var merge <Record:Object, Overrides:Object> => (overrides:Overrides:, record:Record) => Record;

But than neither key or value seems to be restricted to the the Record keys / value types of the Record type. I imagine if flow is given the source for these functions it maybe able to infer that invalid key would invalidate return type constraint and there for fail to type check. Although it would be better to be able to express this with a type signature itself in case there is no typed implementation available for example Object.assign is one example of that.
I am also unsure how that would even work if these functions were defined on prototype I imagine something like this:
interface Record <fields:Object> {
  set(key:string, value:any) => Record<fields:Object>;
  update <T> (key:string, f:(value:T) => T) => Record<fields>;
  merge <T> (overrides:T) => Record<fields>;
}

But then I'm not sure how to say that this instance must be record that has fields type signature.

I've been trying to achieve similar things when trying to add types for https://github.com/rackt/redux, and I've just recently found that in the type declaration for React there's some possibly useful (internal) features to achieve that kind of type checks: https://github.com/facebook/flow/blob/master/lib/react.js#L25
Haven't tried them though, but if they work then probably could be more reason to make them part of the public API

@leoasis see #875

Ahhh, so we need to wait for it a bit more then :cry:

We've been kicking around this idea for a while now and I'm hoping to address some of this in the coming months. The much bigger/impactful change to improve Immutable.js types, supporting this types, has already landed. Helping Flow understand Immutable.Record in a type safe way is an important goal for me personally, FB internally, and I hope the JS community at large.
Watch this space for updates. Please don't +1—it's already prioritized. Just hit the subscribe button, please.

This might need to be a totally separate initiative, but how about an extension to flow and an accompanying Babel plugin to support data types that can be instantiated, whose properties would be immutable by default? For example:
data type User {
	id: ?number,
	mutable firstName: string,
	mutable lastName: string,
	mutable email: string,
	mutable password: string,
	//"mutable" here means only that you can set the address property to a
	//different address; the address itself is immutable.
	mutable address: ?Address
}

data type Address {
	id: ?number,
	streetAddress: string;
	city: string;
	stateOrProvince: StateOrProvince;
	country: Country;
	postalCode: PostalCode;
}

let john = new User({firstName:'John', lastName:'McCarthy'});
john.address = new Address({...});
john.address.city = 'New City'; //compile error; city is immutable

I'm thinking of this as being for objects that contain only data properties and no methods (if it were to support methods as well, then it would be getting into the same territory as classes and we don't need two separate constructs for that)...so in reality User might be a class while Address could be a data type. But mutable properties can still be useful for properties that can legitimately change, e.g. if a person gets a new email address or even changes their name, it's still the same person.
There should probably also be the ability to declare subtypes; maybe an "extends" keyword that specifies the prototype relationship as in classes.
Sorry if this is too off-topic for this thread. I posted it here because I think it's relevant to the big picture of how to better support the declaration of data types that are not necessarily mutable classes. I was thinking of maybe writing a Babel plugin for this but if it could be a joint effort with flow that would be great.

@mbrowne I already experimented with something like this: https://github.com/stephanos/babel-plugin-immutable-record - I haven't been able to use it a lot so far so consider this early-beta ;)

Nice. It doesn't support a mix of mutable and immutable properties like I was thinking of, but of course that can be accomplished with classes and perhaps it's more common for data types to be either entirely mutable or immutable. Or alternatively this could serve as a nice starting point if I decide to implement my syntax above - thanks for pointing it out.

Hey @samwgoldman, is this still being prioritized? Any update since a year ago?

@samwgoldman  I don't understand how the Facebook developers use this in their daily life? You advocate the following three pretty heavily: react.js, flow, immutable.js. But the three can not work together successfully when you try to use the Record type of immutable.js, which for me is the most useful type. My guess is that you must have some kind of workaround so that your codebase typechecks. If so, could you please share your experience with us?

@hmeerlo I'm not at Facebook, but I struggled with this for a while to, and this is what I came up with:
/* @flow */

import * as Immutable from 'immutable';

/**
 * This is a restricted typed interface to `immutable.Record`.
 *
 * Notably, the `get` and `set` methods are missing, because they expose
 * holes in the type system.
 *
 * @private
 */
declare class IRecord<T: Object> {
    /**
     * Create a new typed immutable record with the values given.
     *
     * @memberof TypedRecord
     * @param {$Shape<T>} values The values to initialize this record with.
     * @returns {$Subtype<IRecord<T>>} The record instance.
     */
    constructor(values: $Shape<T>): void;

    /**
     * @memberof TypedRecord
     * @returns {string} A string representation of this record.
     */
    inspect(): string;

    /**
     * Set the given key to the given value.
     *
     * @memberof TypedRecord
     * @returns {$Subtype<IRecord<T>>} The updated record instance.
     */
    set<A>(key: $Keys<T>, value: A): $Subtype<IRecord<T>>;

    /**
     * Update the given key to the value returned by the given function.
     *
     * @memberof TypedRecord
     * @returns {$Subtype<IRecord<T>>} The updated record instance.
     */
    update<A>(key: $Keys<T>, updater: (value: A) => A): $Subtype<IRecord<T>>;

    /**
     * @memberof TypedRecord
     * @param {$Shape<T>} values
     *   Values to replace in the current record.
     * @returns {$Subtype<Record<T>>}
     *   A new record with the given values.
     */
    merge(values: $Shape<T>): $Subtype<IRecord<T>>;

    /**
     * Apply a batch of mutations to this record. This may be more efficient
     * than calling `merge` multiple times.
     *
     * @memberof TypedRecord
     * @param mutator
     *   A mutator function that accepts the current record and returns a
     *   new one.
     * @returns {$Subtype<IRecord<T>>} The new record.
     */
    withMutations(
        mutator: (mutable: $Subtype<IRecord<T>>) => $Subtype<IRecord<T>>,
    ): $Subtype<IRecord<T>>;

    /**
     * Convert this record to a normal Javascript object.
     *
     * @memberof TypedRecord
     * @return {Object} A plain Javascript object of this record.
     */
    toJS(): Object;
}

/**
 * Converts an `immutable.Record` specification to a class constructor for
 * typed immutable records. The return value of this function is a **class**
 * and not an instance of a class. The instance methods of the class returned
 * are documented on this function.
 *
 * The parameter doubles as both the type specification for this record and
 * as the initial default values used whenever a record is constructed.
 *
 * **Example usage:**
 *
 * ```
 * class Foo extends TypedRecord({x: 0, y: 'foo'}) {
 *   x: number;
 *   y: string;
 * }
 *
 * const foo1 = new Foo({x: 5});
 * expect(foo1.x).toEqual(5);
 * expect(foo1.y).toEqual('foo');
 *
 * // This won't type check.
 * const foo2 = foo1.merge({x: 'not a number'});
 * // Neither will this.
 * const foo3 = new Foo({y: 5});
 * ```
 *
 * @function
 */
export default function TypedRecord<T: Object>(spec: T): Class<IRecord<T>> {
    return Immutable.Record(spec);
}

This lets you do things like
export Class Foo extends TypedRecord({
    field1: 0,
    field2: '',
}) {
    field1: number;
    field2: string;
}

where accessing the instance members field1 and field2 directly will have meaningful types (notice the lack of a get method in the IRecord class above). The merge function will be typed nicely as well, but the set and update functions still subvert the type system.
It's not perfect by any stretch, but this is the best I could come up with.

@BurntSushi Please accept my 'Hero of the day' award! Finally something that is quite useable considering the current shortcomings of flow.

@hmeerlo: you may also want to take a look at debugger.html's type for Record.
It's similar to what BurntSushi posted, but it doesn't use classes. I've been using it for a few weeks and it works fine, even though it feels a bit wonky.
I had a hard time wrapping my mind around using it for polymorphic records (that is, records which hold other records of any shape) or using that in a polymorphic function (which would take, for example, any record that has the field foo of type number).
Aaand the errors reported by Flow when you use this approach are not that straightforward, but other than that it's okay – well, it's better than having either no records or no types at all.

Is it unresolved yet?
I notice that $Shape is already used here:
https://github.com/facebook/immutable-js/blob/master/type-definitions/immutable.js.flow#L1146
@Gozala

Any news on this issue?
Is it possible to use Immutable and Flow together?


splits xxxxxxx not found, failed to publish splits.

Describe the bug
A clear and concise description of what the bug is.
I'm observing the error in the logs
quickwit-indexer-2 quickwit     splits `01HT2BDEQ76A92T8X010XD38G3` not found exit_status=Failure(failed to publish splits
quickwit-indexer-2 quickwit
quickwit-indexer-2 quickwit Caused by:
quickwit-indexer-2 quickwit     splits `01HT2BDEQ76A92T8X010XD38G3` not found)
quickwit-indexer-2 quickwit 2024-03-28T10:59:12.176Z  INFO quickwit_actors::spawn_builder: actor-exit actor_id=Publisher-quiet-2Dom exit_status=failure(cause=failed to publish splits
quickwit-indexer-2 quickwit
quickwit-indexer-2 quickwit Caused by:
quickwit-indexer-2 quickwit     splits `01HT2BDEQ76A92T8X010XD38G3` not found)
quickwit-indexer-2 quickwit 2024-03-28T10:59:12.176Z ERROR quickwit_actors::actor_context: exit activating-kill-switch actor=Publisher-quiet-2Dom exit_status=Failure(failed to publish splits
quickwit-indexer-2 quickwit
quickwit-indexer-2 quickwit Caused by:
quickwit-indexer-2 quickwit     splits `01HT2BDEQ76A92T8X010XD38G3` not found)

It resolves after sometime and then happen again. I tried to restart cluster but still no luck.
Steps to reproduce (if applicable)
Steps to reproduce the behavior:
It started to happen after upgrade to 0.8.0.
Expected behavior
No error message about splits don't exist.
I'm using gcs as storage and metastore as well.

Output of quickwit --version
Quickwit 0.8.0 (x86_64-unknown-linux-gnu 2024-03-18T15:20:23Z 7af4596)
The index_config.yaml

{
  "commit_timeout_secs": 30,
  "docstore_compression_level": 8,
  "docstore_blocksize": 1000000,
  "split_num_docs_target": 10000000,
  "merge_policy": {
    "type": "stable_log",
    "min_level_num_docs": 100000,
    "merge_factor": 10,
    "max_merge_factor": 12,
    "maturation_period": "2days"
  },
  "resources": {
    "heap_size": "2.0 GB"
  }
}

Can you share more logs? (Before the error)


[Snyk] Upgrade casbin from 5.19.3 to 5.23.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade casbin from 5.19.3 to 5.23.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 10 versions ahead of your current version.
The recommended version was released a month ago, on 2023-02-04.

Release notes

Package name: casbin

5.23.2 - 2023-02-045.23.2 (2023-02-04)
Bug Fixes

fix typo in subject_priority_policy.csv (#425) (ada2543)

5.23.1 - 2023-02-025.23.1 (2023-02-02)
Bug Fixes

avoid the impact of line breaks CRLF in frontend.test.ts (#420) (7c32e23)

5.23.0 - 2023-02-015.23.0 (2023-02-01)
Features

support updateGroupingPolicy(), updateNamedGroupingPolicy(), getImplicitResourcesForUser() (#419) (46c0f3a)

5.22.0 - 2023-01-315.22.0 (2023-01-31)
Features

support subjectPriority (#417) (e83d505)

5.21.0 - 2023-01-215.21.0 (2023-01-21)
Features

support setNamedRoleManager() (#416) (869e8f9)

5.20.4 - 2023-01-205.20.4 (2023-01-20)
Bug Fixes

add groupPolicy for GetPermissionForUser in frontend.ts (#415) (5d1a679)

5.20.3 - 2023-01-105.20.3 (2023-01-10)
Bug Fixes

Multiline Separator Handling (#411) (ab3467a)

5.20.2 - 2023-01-085.20.2 (2023-01-08)
Bug Fixes

Upgraded CI Nodejs version to v14.16.18. (#410) (9aadcd7)

5.20.1 - 2022-12-315.20.1 (2022-12-31)
Bug Fixes

delete unused files in examples (#407) (323a750)

5.20.0 - 2022-12-295.20.0 (2022-12-29)
Features

defaultrolemanager.ts: add hierarchical domain support for rbac (#380) (da980af), closes #377

5.19.3 - 2022-12-02

    from casbin GitHub release notes

Commit messages

Package name: casbin

c5af76a chore(release): 5.23.2 [skip ci]
ada2543 fix: fix typo in subject_priority_policy.csv (#425)
ba83cb3 chore(release): 5.23.1 [skip ci]
7c32e23 fix: avoid the impact of line breaks CRLF in frontend.test.ts (#420)
5bfc390 chore(release): 5.23.0 [skip ci]
46c0f3a feat: support `updateGroupingPolicy()`, `updateNamedGroupingPolicy()`, `getImplicitResourcesForUser()` (#419)
abf7623 chore(release): 5.22.0 [skip ci]
e83d505 feat: support subjectPriority (#417)
a2ab183 chore(release): 5.21.0 [skip ci]
869e8f9 feat: support setNamedRoleManager() (#416)
2b2cfb8 chore(release): 5.20.4 [skip ci]
5d1a679 fix: add groupPolicy for GetPermissionForUser in frontend.ts (#415)
a704ebb chore(release): 5.20.3 [skip ci]
ab3467a fix: Multiline Separator Handling (#411)
9f3d2bb chore(release): 5.20.2 [skip ci]
9aadcd7 fix: Upgraded CI Nodejs version to v14.16.18. (#410)
2a05042 chore(release): 5.20.1 [skip ci]
323a750 fix: delete unused files in examples (#407)
cf0c257 chore(release): 5.20.0 [skip ci]
da980af feat(defaultrolemanager.ts): add hierarchical domain support for rbac (#380)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing as it requires manual intervention to resolve conflict. The upgrade will be included in next version updates cycle of LoopBack.


OverlayDialog: fix overlay dialog oversize display issue.

Please help to review: @nblfeng

Please help to review: @nblfeng

nice~ 👍