Add upstream tracking info to Contributing doc

Recommendation is to add upstream tracking commands to CONTRIBUTING.md. Which specifies name of master branch, how to add upstream tracking (my macro didn't work because it relies on the name being master), as well as fetch/merge because I was already there.
(Sorry for the extra commits from the closed fork yesterday. Tried squashing them but to no avail.)

This change is

This is a great addition, Sean. Thanks! I have a few minor suggestions (see below). And I'd like you to try squashing the unrelated commits as follows:

Get on your local branch.
Run git rebase -i gh-pages. This will open the commit list in VIM.
Press i to enter edit mode.
At the top, delete all "pick" lines EXCEPT the one for adding Keep Contributing section.
Press esc, then :, then wq, then enter. At this point, you will have squashed the commits down to only the one relevant.
Run git push --force origin <you branch name>. This should force your local branch to overwrite the remote branch.

If that doesn't work, I'll create another branch and learn how to cherry pick the right commit from your branch.
Previously, sploiselle (Sean Loiselle) wrote…
> #### Add upstream tracking info to Contributing doc
>
> Recommendation is to add upstream tracking commands to CONTRIBUTING.md. Which specifies name of master branch, how to add upstream tracking (my macro didn't work because it relies on the name being `master`), as well as fetch/merge because I was already there.
>
>
>
> (Sorry for the extra commits from the closed fork yesterday. Tried squashing them but to no avail.)
>
>
>

Review status: 0 of 1 files reviewed at latest revision, 2 unresolved discussions.

CONTRIBUTING.md, line 47 [r2] (raw file):

    ```

    ``` shell

This an arbitrary style thing, but let's keep git fetch upstream and git merge upstream/gh-pages in the same code block.

CONTRIBUTING.md, line 51 [r2] (raw file):

    ```

4. Repeat the write, build, push, pull flow from the __Get Started__ section above.

Let's make Get Started a link. All headers are link anchors by default, so you can use this syntax:
Get Started

Comments from Reviewable

CONTRIBUTING.md, line 51 [r2] (raw file):
Previously, jseldess wrote…
> Let's make Get Started a link. All headers are link anchors by default, so you can use this syntax:
>
> [Get Started](#get-started)

Formatting for that link is `[Get Started](#get-started)`

Comments from Reviewable

Hey @sploiselle, I see that you've made the adjustments to CONTRIBUTING.md, but it looks like there are still some unrelated commits in here. Is it ok for me to open a new PR with your CONTRIBUTING.md changes, close this one, and then have you review to validate that I caught everything you wanted?

@jseldess That would be great. I've caught myself in a rat's nest of commits which I've been trying to untangle all morning.


Create a static volume with Azure disks in Azure Kubernetes Service does not suceed

I'm trying to mount an Azure Disk in my aks according to the docs https://docs.microsoft.com/en-us/azure/aks/azure-disk-volume but this just results in an error.
These are the events of the pod mypod:
│   Warning  FailedScheduling    4m36s                default-scheduler        0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.                                                                                │
│   Normal   Scheduled           4m21s                default-scheduler        Successfully assigned default/mypod to XXX
│   Normal   NotTriggerScaleUp   4m30s                cluster-autoscaler       pod didn't trigger scale-up: 1 pod has unbound immediate PersistentVolumeClaims                                                                             │
│   Warning  FailedMount         2m18s                kubelet                  Unable to attach or mount volumes: unmounted volumes=[azure], unattached volumes=[kube-api-access-8657k azure]: timed out waiting for the condition         │
│   Warning  FailedAttachVolume  20s (x2 over 2m21s)  attachdetach-controller  AttachVolume.Attach failed for volume "pv-azurediskdemo" : Attach timeout for volume /subscriptions/XXX/resourceGroups/MC_...
│   Warning  FailedMount         4s                   kubelet                  Unable to attach or mount volumes: unmounted volumes=[azure], unattached volumes=[azure kube-api-access-8657k]: timed out waiting for the condition

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

ID: 74be7378-92bc-0e59-0b70-c6b10e80d9b6
Version Independent ID: f7f1eeb3-efe7-86e2-1fd7-04341b2c77cc
Content: Create a static volume for pods in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/azure-disk-volume.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@matlion , thanks for reaching out. I'll try to repro this and check why this is happening.

It would also help to get some more information why the mount fails.
Permissions? Name mismatch?

Hi @matlion , I was not able to do a repro of this. As this channel is for docs improvement, I would request you to please post the same query on our Microsoft QnA forum so that community members/experts can look into this.


add gtfs-rt-printer

Thanks @laidig!  I moved it to the GTFS Realtime Utilities section as I think it fits better there.


swift4.2?

swift4.2?

This project is on Objective C, you can update it to Swift 4.2. I've plan to update it on Swift but right now I don't have the free time for it. Hope you can understand it.


Use a different separator for sed 's' command

The sed expression that is used to set specific config values doesn't work while trying to set the following config:  CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder"
Instead, it throws the following error:
sed: -e expression # 1, char 80: unknown option to 's'
This is because the argument separator (comma) also appears in the expression argument itself. That causes sed to interpret the h in binder,hwbinder as an option to the s command.
This change makes semicolon (;) the separator instead of comma (,) to avoid the issue. If a new config value with a semicolon in it is ever added to the list in $CONFIGS_EQ, this will have to be changed.

Is this PR in the wrong place?


Dynamic member lookup fails to autocomplete sendable key path

Description
If a type with dynamic member lookup is constrained to sendable key paths, then the compiler fails to show autocomplete for the members.
Reproduction
@dynamicMemberLookup struct S<A> {
  subscript<B>(dynamicMember keyPath: KeyPath<A, B> & Sendable) -> S<B> {
    fatalError()
  }
}

func f(_ s: S<String>) {
  s.count  // Compiles, but members do not show up when autocompleting from 's.'
}

Expected behavior
I expect autocomplete to show the members.
Related bug: I can add an unavailable overload for non-sendable key paths, and it restores autocomplete, but it also allows such accesses to compile even though they should be unavailable:
extension S {
  @available(*, unavailable)
  subscript<B>(dynamicMember keyPath: KeyPath<A, B>) -> S<B> {
    fatalError()
  }
}

struct T {
  @MainActor var p = 0
}

func f(_ s: S<T>) {
  s.p  // Compiles, but it shouldn't
}

Environment
swift-driver version: 1.115 Apple Swift version 6.0.2 (swiftlang-<IP_ADDRESS>.2 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Additional information
No response

@xedin Another key path sendability bug...

cc @ahoppen, this might be a code completion issue  since the signature of dynamic member subscript is allowed to provide & Sendable and code completion might not handle protocol compositions correctly in some situations?…
Re: s.p that is most likely due to concurrency checker not diagnosing synthesized code, if completion issue turns up to be non-typecker I think you should file a new one for s.p example specifically.

Yes, it’s indeed a code completion issue. Removing & Sendable makes the result show up.


[FLINK-32706][table] Add built-in SPLIT_STRING function

What is the purpose of the change
This is an implementation of SPLIT
Brief change log
Splits a string into an array of substrings based on a delimiter. If the delimiter is not found, then the original string is returned as the only element in the array. If the delimiter is empty, then all characters in the string are split. If either, string or delimiter, are NULL, then a NULL value is returned.
If the delimiter is found at the beginning or end of the string, or there are contiguous delimiters, then an empty space is added to the array.

Syntax
SPLIT(string, delimiter)

Arguments
string: The string need to be split
delimiter: Splits a string into an array of substrings based on a delimiter

Returns
If the delimiter is not found, then the original string is returned as the only element in the array. If the delimiter is empty, then all characters in the string are split. If either, string or delimiter, are NULL, then a NULL value is returned.

Examples

SELECT SPLIT('abcdefg', 'c');
Result: ['ab', 'defg']

See also

ksqlDB Split function
ksqlDB provides a scalar function named SPLIT which splits a string into an array of substrings based on a delimiter.
Syntax: SPLIT(string, delimiter)
For example: SPLIT('a,b,c', ',') will return ['a', 'b', 'c'].
https://docs.ksqldb.io/en/0.8.1-ksqldb/developer-guide/ksqldb-reference/scalar-functions/#split

Apache Hive Split function
Hive offers a function named split which splits a string around a specified delimiter and returns an array of strings.
Syntax: array split(string str, string pat)
For example: split('a,b,c', ',') will return ["a", "b", "c"].
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF

Spark SQL Split function
Spark SQL also offers a function named split, similar to the one in Hive.
Syntax: split(str, pattern[, limit])
Here, limit is an optional parameter to specify the maximum length of the returned array.
For example: split('oneAtwoBthreeC', '[ABC]', 2) will return ["one", "twoBthreeC"].
https://spark.apache.org/docs/latest/api/sql/index.html#split

Presto Split function
Presto offers a function named split which splits a string around a regular expression and returns an array of strings.
Syntax: array split(string str, string regex)
For example: split('a.b.c', '.') will return ["a", "b", "c"].
https://prestodb.io/docs/current/functions/string.html

Verifying this change
This change added tests in CollectionFunctionsITCase.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

If the delimiter is empty, every character in the string is split

Is that a requirement? As far as I can tell ksqlDB is the only engine that has that behaviour. Moreover after switching to splitByWholeSeparatorPreserveAllTokens you do not guarantee this behaviour anymore.
@MartijnVisser What do you think should be the behaviour for an empty delimiter?

@dawidwys @MartijnVisser I think I should change the description,  If the delimiter is empty, we will return entire string.

Now we use splitByWholeSeparatorPreserveAllTokens, when delimiter is empty, it will return entire string.

Actually it splits by whitespaces: https://github.com/apache/flink/blob/8e5220b288e49c99333a4bc8ef7e3d5d27193921/flink-table/flink-table-runtime/src/main/java/org/apache/flink/table/data/binary/BinaryStringDataUtil.java#L107

I think we can change the description,

Let's first agree what is the desired behaviour.

@MartijnVisser What do you think should be the behaviour for an empty delimiter?

I've taken a tour along the various databases:

Postgres doesn't have a SPLIT function, but leverages regexp_split_to_table or regexp_split_to_array. When an empty delimiter is provided, it throws an error. https://www.postgresql.org/docs/current/functions-string.html
MySQL doesn't have a SPLIT function either, but has SUBSTRING_INDEX.
MSSQL Server has STRING_SPLIT https://learn.microsoft.com/en-us/sql/t-sql/functions/string-split-transact-sql?view=sql-server-ver16 which also doesn't accept empty delimiters
Spark has a SPLIT function and accepts empty delimiters, having the same behavior as ksqlDB https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.functions.split.html
Presto has a SPLIT function and accepts empty delimiters, same behavior as ksqlDB https://prestodb.io/docs/current/functions/string.html
Clickhouse actually has a wide variety with splitByChar, splitByString, splitByRegexp etc https://clickhouse.com/docs/en/sql-reference/functions/splitting-merging-functions. splitByString appears to have the same behavior as Spark and Presto

All in all, I could find 3 implementations of SPLIT in ksqlDB, Spark, and Presto. All 3 accept empty delimiters. I would think then we should follow the same behavior, since all others have different function names for comparable/similar features

@MartijnVisser To confirm, you suggest to support an empty delimiter and in that case split all characters, meaning:
SPLIT('abcde', '') = ['a', 'b', 'c', 'd', 'e']
SPLIT('It is', '')=['I', 't', ' ', 'i', 's']

@MartijnVisser To confirm, you suggest to support an empty delimiter and in that case split all characters, meaning:
SPLIT('abcde', '') = ['a', 'b', 'c', 'd', 'e']
SPLIT('It is', '')=['I', 't', ' ', 'i', 's']

@MartijnVisser To confirm, you suggest to support an empty delimiter and in that case split all characters, meaning:
SPLIT('abcde', '') = ['a', 'b', 'c', 'd', 'e']
SPLIT('It is', '')=['I', 't', ' ', 'i', 's']

Now if the delimiter is empty, we will return input string, here is a test case.
https://github.com/apache/flink/pull/24365/files#r1603638142

To confirm, you suggest to support an empty delimiter and in that case split all characters

Yes

@dawidwys So We can use splitByWholeSeparatorPreserveAllTokens when the delimiter is not empty. When the delimiter is empty, do we need to handle this situation specially?

When the delimiter is empty, do we need to handle this situation specially?/
Yes, we do. Do you mind updating the PR?


Release 1.9.3

Changelog:
* Fixed inconsistent decompilation with floating point values
* Fixed inconsistent decompilation with non-static inner classes

Codecov Report
Patch coverage: 70.40% and project coverage change: +0.04% :tada:

Comparison is base (c537d08) 77.18% compared to head (0af9247) 77.23%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##             master     #305      +/-   ##
============================================
+ Coverage     77.18%   77.23%   +0.04%
- Complexity     8084     8099      +15
============================================
  Files           222      222
  Lines         25939    25959      +20
  Branches       6721     6723       +2
============================================
+ Hits          20022    20050      +28
+ Misses         3909     3894      -15
- Partials       2008     2015       +7

Files Changed
Coverage Δ

...java/decompiler/main/extern/IFernflowerLogger.java
45.45% <0.00%> (-4.55%)
:arrow_down:

...rg/jetbrains/java/decompiler/main/ClassWriter.java
72.74% <23.07%> (+0.15%)
:arrow_up:

.../decompiler/main/decompiler/PrintStreamLogger.java
39.21% <25.00%> (-2.65%)
:arrow_down:

...org/jetbrains/java/decompiler/main/Fernflower.java
60.39% <60.00%> (+0.80%)
:arrow_up:

...tbrains/java/decompiler/main/ClassesProcessor.java
80.28% <84.21%> (+4.27%)
:arrow_up:

.../jetbrains/java/decompiler/struct/ContextUnit.java
82.35% <87.23%> (-0.53%)
:arrow_down:

...brains/java/decompiler/main/DecompilerContext.java
93.47% <100.00%> (+0.29%)
:arrow_up:

...compiler/modules/decompiler/exps/ConstExprent.java
89.09% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


dataset

Hello great project.
How to get this train dataset that train in source.

I have added the instructions to create the database.


create-react-app v2.1.8 fails running because of @svgr dependencies not found

Is this a bug report?
Yes. I opened it because the other 2 issues were closed, but without any solution. I tried this on other computers and I couldn't reproduce it.
Environment
System:
OS: macOS 10.14.3
CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Binaries:
Node: 8.15.1 - ~/.nvm/versions/node/v8.15.1/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v8.15.1/bin/npm
Browsers:
Chrome: 72.0.3626.121
Safari: 12.0.3
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: 2.1.8
Steps to Reproduce

npx create-react-app my-app or npm create-react-app my-app

Expected Behavior
It should create a new boilerplate app with create-react-app
Actual Behavior
The most common error i got is this:
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
But sometimes, i will get one of those other errors:
<EMAIL_ADDRESS>Request failed \"404 Not Found\""
<EMAIL_ADDRESS>Request failed \"404 Not Found\"
another one which i found interesting:
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@svgr%2fplugin-svgo - Not Found
npm ERR! 404 '@svgr/plugin-svgo@latest' is not in the npm registry. Your package name is not valid, because name can only contain URL-friendly characters
Other things i tried
Tried different version of node, npm and yarn, same issue.
Install node from binaries / from nvm.
Tried uninstalling yarn, but received the same error message.
Then I tried to install the @svgr/plugin-svgo package globally with both npm and yarn, but again failed with @svgr/plugin-svgo@latest not found
https://status.npmjs.org/ and http://status.yarnpkg.com don't report any incident.

Hmm. The package definitely exists. Perhaps you're behind an npm package proxy server or something?

@ianschmitz exactly! this issue https://github.com/storybooks/storybook/issues/15 helped me remember that i had some custom configuration in .npmrc (private npm proxy). I think it was not setup correctly and raised issues to some scoped npm packages like @svgr

Can we close this issue?

Yes, solved!


Keep OTel collector version updated in product telemetry functional test

https://github.com/nginxinc/nginx-gateway-fabric/pull/1659 added a functional test that install OTel collector in a cluster using helm.
For predictability, the version of the chart is kept static in a go file:
const (
	. . .
	collectorChartVersion = "0.73.1"
)

Find a automated way to keep the version updated here similar to dependabot.

#1832 Also adds a constant version which should be fixed to update automatically.
const (
    debugImage = "busybox:1.28"
)

Update: #1832 no longer adds a constant version and thus does not need to be taken into consideration.


chore: add lint:fix script

Strong preferences

If we change this in Tres, we should do it all the subprojects, e.g., Cientos. (I bounce around quite a bit between them. 🤪)
Whatever the fix incantation becomes, it should cover the same files as the regular lint.

Weak preference
pnpm run lint --fix works fine for me across Tres and the subprojects. It also runs on the same files as pnpm run lint.

Closing due to inactivity. Feel free to reopen.


Publish to maven repostiory

First version is published here:
http://repo1.maven.org/maven2/de/jgoldhammer/alfresco-jscript-extension/


2122: fix tab from input not retaining focus

Delivers #2122.

Somehow this has picked up a commit from a different ticket. Might need to merge master into this branch? If the commit has already been merged to master though then this is fine and I can merge.

Ah thanks! Rebased and pushed... looks good now :beers:


Update redis-rs version

@lee-hen I'll test and publish it in 24 hours. I think I should add test workflow of github action with docker setting.

And I'll add .idea directory to .gitignore

@lee-hen Hello I tested your pull request. But unfortunately, redis 0.22.1 does not compatible with redis_cluster_async 0.7.0. So I can't merge this pull request. I think I should wait until redis_cluster_async support redis 0.22.X


Install: pod cc-operator-daemon-install cannot be running

Try make deploy to install CAA via operator.
Pod cc-operator-daemon-install crashed.
Check the logs:
/opt/kata-artifacts/scripts/kata-deploy.sh: line 17: SHIMS: unbound variable

It looks like related to recent changes to kata-deploy.sh:
https://github.com/kata-containers/kata-containers/commit/7164ced4dc2fedf5cee381bad36e31959563cdcb#diff-08a680425cfe93e69c4108dc8fd91a9aeaefbf016bd9941b03c66834bf87a341L16
Also related to operator issues:
https://github.com/confidential-containers/operator/issues/229
https://github.com/confidential-containers/operator/issues/230

Tried a quick fix to add required env variables:
https://github.com/genjuro214/operator/blob/main/config/samples/ccruntime/base/ccruntime.yaml
kubectl apply -k "github.com/genjuro214/operator/config/samples/ccruntime/peer-pods"

Tried a quick fix to add required env variables: https://github.com/genjuro214/operator/blob/main/config/samples/ccruntime/base/ccruntime.yaml
kubectl apply -k "github.com/genjuro214/operator/config/samples/ccruntime/peer-pods"

I have a PR on the operator side that needs to be merged and it should solve this issue: https://github.com/confidential-containers/operator/pull/240

The operator issue has been fixed by the PR above.


Small fixes

Coverage remained the same at 39.883% when pulling 67d54e705cac169c3a30cf1074fe0466c29ed7d8 on MMP0:patch-39 into d6f6ed5c296a93adba4507a29b1a37f333c15f11 on NyaaPantsu:dev.


Upload fact check

*Description
Check media launched a new  API to import  fact-checks in Check.
Solution
Write a daily cron script that

Use RSSJson to fetch uploads from Pesacheck.
Process data as per the documentation.
Upload the content.
Use Sentry as a mechanism for logging status updates of the uploads

Alternatives

The ideal alternative would be to use a medium API  but we are limited by the fact that medium no longer supports public API.

Additional context

Since RSS JSON limits us to only 10 items per request, the team mentioned that they upload 15 - 20 checks per month. Doing a daily cron getting 10 items each ensures that no item is missed.
The API handles conflicts by returning 409 status code if similar titles are uploaded.

Your take @kilemensi

Thanks @koechkevin.
Can you clarify a bit more on "RSS JSON limits us to only 10 items per request"? e.g. can I say I want to start from a given date or it just return the latest 10 items and that's it? Meaning, if we run it now, it will return the 10 items published in Jan but nothing published from Dec (assuming PesaCheck publishes 10 articles per month).
... and why is the issue here in the UI repo? Isn't this app basically an API?

@kilemensi Sorry for replying this late, I was on a call.
The free version has a limitation of  maximum of 10 items per request. There is a parameter order_by and order_dir  which requires API key, and we can use it to sort by pubDate, desc.

Move


library skeletop project has non working playwright config

Describe the bug
When i npm create a Library skeleton project, playwright does not work. when I run pnpm test i get this error:

><EMAIL_ADDRESS>test /Users/christoph/Projects/temp/my-lib
> playwright test

Running 1 test using 1 worker

[WebServer] Svelte libraries should include "svelte" in either "dependencies" or "peerDependencies".
[WebServer] npm[WebServer]  ERR! Missing script: "preview"
npm ERR![WebServer]
npm ERR! To see a list of scripts, run:
npm ERR![WebServer]    npm run
[WebServer]
[WebServer] npm[WebServer]  ERR!      /Users/christoph/.npm/_logs/2023-02-11T16_35_20_453Z-debug-0.log
Error: Process from config.webServer was not able to start. Exit code: 1

Reproduction
npm create svelte@next my-lib
# select library skeleton project, and keep everything as default but enable playwright
cd my-lib
pnpm i
pnpm test

Logs
No response
System Info
System:
    OS: macOS 13.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 62.63 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.4.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Edge: 108.0.1462.46
    Firefox Developer Edition: 107.0
    Safari: 16.3
    Safari Technology Preview: 16.4
  npmPackages:
    @sveltejs/adapter-auto: ^1.0.0-next.90 => 1.0.3
    @sveltejs/kit: ^1.0.0-next.587 => 1.5.5
    @sveltejs/package: ^1.0.0-next.6 => 1.0.2
    svelte: ^3.54.0 => 3.55.1
    vite: ^4.0.0 => 4.1.1

Severity
annoyance
Additional Information
No response

This will be fixed by #8922 (https://github.com/sveltejs/kit/pull/8922/files#r1103666805)


strict-ssl: false in .bowerrc stopped working after 1.5.3 version of bower

The 1.60 and higher version of bower don't seem to apply the strict-ssl setting properly. I had to revert to 1.5.3 to get it to work again.

Related? #1972

Yes, it is the same issue

whew, i thought i was going crazy! Yes, I am having this problem as well. :-(

Closing, please keep an eye on #1972


Set repos up as GitHub Template repos

GitHub recently added a new repository setting to mark a repo as a "template repository".
It's quite easy to set up (see docs) and basically just adds a little badge to the repo which allows people to copy the repo to their account (NB: not fork it, there's no link here).
This will obviously skip some of the bionitio functionality such as renaming the project within the code, however it could offer a second alternative route for users.

Wow, thanks @ewels. Will check it out.


Admin integration

Hi,
This is a question/feature request.
I really like the concept behind this package. However, I'm not sure how one could use it in django's admin. Even though DRF is now working on an admin, I don't think it competes with django's own yet, so I like to give certain users access to django's admin page.
The question is, how to implement the permissions rules in the admin itself? i.e. admins of a certain object should have r/w permissions for that object in the admin but not for any other. Is this possible? I don't mind using another package for this, as long as the rules are coming from dry-rest-permissions. Is there a possibility to extend dry-rest-perms to support the admin or take advantage of another package that is already well integrated with the admin (i.e. django-guardian's admin integration receiving its rules from dry-rest)?

Currently there is no hook in for the django admin pages. This has been requested once before, but I haven't gotten to it yet.

Cool. Its obviously a low priority. I had seen the request on twitter before, but thought this was a better place to put it.


fix: cli multiple input

Description
With this PR, if the input pattern points to more than one file, we expect it to work for all of them. In the current version, it only produces output for the first file.
Validation
For example, expect the command below to produce output for all markdown files in the api directory;
npx api-docs-tooling -i PATH_TO_NODE/doc/api/*.md -t json-simple -o .

Sorry, what exactly was not working? For me Im able to have this working with same arguments but -i "/path/to/*.md"

Sorry, what exactly was not working? For me Im able to have this working with same arguments but -i "/path/to/*.md"

When I check for the main branch, -i "/path/to/*.md" gives me a JSON output of 268 lines containing only addons 🤔
{
  "version": "v20.11.1",
  "changelog": "https://raw.githubusercontent.com/nodejs/node/HEAD/CHANGELOG.md",
  "input": "../node/doc/api/addons.md",
  "target": [
    "json-simple"
  ],
  "output": "."
}

For me it work fine when I surround with quotes, but if this PR fixes it let's get it merged :)

For me it work fine when I surround with quotes, but if this PR fixes it let's get it merged :)

Since it is a string array containing more than one file, at worst we fixing the input type 😄 Now I get it, it worked for me too when I added double quotes 👀


loss.py is missing

Hi authors,
Congrats on publishing amazing work. When I try to run the code,
https://github.com/CharlesGong12/RECE/blob/f9a40445f3d0f5c7b2aa8c5c784f55290525aef9/utils/__init__.py#L1C1-L2C1
This loss function is not defined or missing in the repo.
Could you check this?
Thanks in advance

Hi, thanks for your attention to our work.
Code about the loss function is not used and it was for gradient-based adversarial training, like PGD, in my early exploring stage. I deleted the related code and updated the git repository. The code can be directly run now.
Any further questions, plz don't hesitate and contact me.


Change the temp folder location used by CommitUpdate

SD-1742, originally created on 11/2/2010 03:00:41 by David Pierson
Change the temp folder location used by CommitUpdate
Mainly for Windows CE / WMP7 with limited storage
Code provided in thread
community.sharpdevelop.net/forums/t/9910.aspx
Also check the Silverlight version on codeplex.

Since neither CE or WMP7 is supported anymore I am closing this. If this feature is needed for some other reason, please create a new issue.


Linked data not recorded

Hi,
I have a strange problem that I don't understand...
This is an example:
package main

import (
	"fmt"

	"github.com/jinzhu/gorm"
	_ "github.com/mattn/go-sqlite3"
)

type Address struct {
	gorm.Model
	Line string
}

type User struct {
	gorm.Model
	Name    string
	Address Address
}

func main() {

	ds, err := gorm.Open("sqlite3", "./test.sqlite")
	if err != nil {
		panic(err)
	}

	ds.LogMode(true)
	ds.CreateTable(User{})
	ds.CreateTable(Address{})

	u := User{
		Name:    "Foo",
		Address: Address{Line: "4 rue test"},
	}

	ds.Create(&u)

	out := User{}
	ds.Find(&out, User{Name: "Foo"})
	fmt.Println(out)

}

The output log is:
(/home/patachou/tmp/go/main.go:29)
[2015-09-24 00:18:58]  [194.00ms]  CREATE TABLE "users" ("id" integer,"created_at" datetime,"updated_at" datetime,"deleted_at" datetime,"name" varchar(255) , PRIMARY KEY ("id"))

(/home/patachou/tmp/go/main.go:30)
[2015-09-24 00:18:58]  [133.38ms]  CREATE TABLE "addresses" ("id" integer,"created_at" datetime,"updated_at" datetime,"deleted_at" datetime,"line" varchar(255) , PRIMARY KEY ("id"))

(/home/patachou/tmp/go/main.go:37)
[2015-09-24 00:18:58]  [1.51ms]  INSERT INTO "users" ("created_at","updated_at","deleted_at","name") VALUES ('2015-09-24T00:18:58+02:00','2015-09-24T00:18:58+02:00','<nil>','Foo')

(/home/patachou/tmp/go/main.go:40)
[2015-09-24 00:18:58]  [0.67ms]  SELECT  * FROM "users"  WHERE ("users".deleted_at IS NULL OR "users".deleted_at <= '0001-01-02') AND (("name" = 'Foo'))
{{1 2015-09-23 22:18:58.800735738 +0000 UTC 2015-09-23 22:18:58.800735738 +0000 UTC <nil>} Foo {{0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC <nil>} }}

As you can see, the "Address" value is not saved... Documentation says that it should record Address before to save user. Am I wrong ?

Address missing a UserID column

I don't agree... Looking your documentation I see that User has a "BillingAddress" and Address type has no UserID column
In User struct, you write:
BillingAddress    Address         // One-To-One relationship (has one)

And Address:
type Address struct {
    ID       int
    Address1 string         `sql:"not null;unique"` // Set field as not nullable and unique
    Address2 string         `sql:"type:varchar(100);unique"`
    Post     sql.NullString `sql:"not null"`
}

So, documentation is wrong either there is something that is badly explained.
So, the User table must have Address ID in the "address" field, and not the inverse. Right ?

You need a field to declare the relations between those two structs.
In the README, you will find the BillingAddressID in User's struct to declare user has one BillingAddress.
For your example, you could have a UserID in Address's struct or AddressID in User's struct. both will build the relations better them. the README should contains examples for both of them.


Fix: ssh_master ssh_slave - rename

As discussed in https://github.com/bluebanquise/bluebanquise/issues/625

Forgot molecule tests update, converting to draft.

Looks good to me.

Thanks !
Merging 😊


Only reconcile namespaces which exist in Cloud Map

The Cloud Map Controller attempts to reconcile every namespace in the cluster. We should cache the list of active namespaces in Cloud Map and only reconcile the intersection.

This would prevent cleaning up orphaned service imports.
Cacheing Cloud Map namespace and service lists alleviates the impact on Cloud Map APIs (#122), and splitting service/endpoint reconciliation cycles will reduce unnecessary K8s API calls (#119).
We could consider deny-listing known internal K8s namespaces but it's probably not worth prioritizing at this time.


Implement unifier and advanced parser

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

905 of 908 (99.67%)  changed or added relevant lines in 20 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 99.632%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lispyc/utils.py
24
25
96.0%

lispyc/nodes/special.py
208
210
99.05%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
1034

Relevant Lines:
1037

💛  - Coveralls


feat: beautify new post indicator, refs. #59

Should be valid after https://github.com/smartive-education/app-pizza-hawaii/pull/75 merged


Add back HCLK ppips.

Replaced with https://github.com/SymbiFlow/prjxray-db/commit/82bf5f158cd8e9a11ac4d04f1aeef48ed1a528a5


Fix existing Python imports with isort

It'll be a big diff, but it's a one-time diff that cleans up a lot of our files.

Got it.

https://github.com/ambuda-org/ambuda/pull/318 completed this issue.


Tracking 3D UNET calibration work

@nvpohanh ETA July 2

Calibration set is added together with #627 . Should we close this?

done


reorder popupCharacters of 'e' / add 'µ' to popupCharacters of 'u'

reorder popupCharacters of 'e' : Du to position of 'e', its popup characters appears horizontaly centered. Consistently closest character is € and è is the farthest
add 'µ' to popupCharacters of 'u'

Build failed seems caused by Circle's configuration and not by modifications

This PR is targetting an old branch. We do not hold each language in its own branch any longer. We are in a mono-repo layout. Please make you changes in the master branch. The French language is under languages/french/


Nested pure val that refers to params caches wrong value

Consider the following example:
module test {
  def foo(x) = {
    pure val bar = x + 1
    bar
  }

  var t: int

  run aTest = (t' = foo(1)).then(t' = foo(2)).then(all{
    assert(t == 3),
    t' = t,
  })

}

The pure value bar here refers to x, which is parameter to foo, so the value for bar cannot be cached (since it changes if x changes). Currently, it is cached, resulting in this behavior:
  test
    1) aTest failed after 1 test(s)

  1 failed

  1) aTest:
      /home/gabriela/projects/quint/examples/test.qnt:10:5 - error: Assertion failed
      10:     assert(t == 3),

    [Frame 0]
    foo(1) => 2

    [Frame 1]
    foo(2) => 2

    Use --seed=0x84c63e40f06ed --match=aTest to repeat.

/home/gabriela/projects/quint/examples/test.qnt:10:5 - error: Assertion failed
10:     assert(t == 3),
        ^^^^^^^^^^^^^^

error: Tests failed

see how in Frame 1, foo(2) => 2, which should be 3.
PS: I couldn't reproduce this by calling foo() in the REPL with different values. The bug appeared only in the simulator.

This is pretty annoying, I'm having to use val instead of pure val in a lot of places to avoid hitting weird caching.

Yeah, I can reproduce it. Let's see whether I can fix it quickly.

Oh, it looks like the it was introduced in the recent caching of top-level pure vals in #837. Actually, the code applies to nested pure vals too. This is why it is happening.


[main > release/client/2.0]: Extract serialized blobs from the ISnapshot instead of fetching from driver which could make network calls #21908

Description
Extract serialized blobs from the ISnapshot which contains blob contents instead of fetching from driver which could make network calls. This affects the cases in Data virtualization where initial blob contents for some trees are missing in the snapshot and therefore driver does not have the contents cached, so it ends up making a bunch of network calls.

Approving and merging patch


vue-config.js  can't Cteate

Version
3.0.3
Reproduction link
http://localhost:8000/configuration/org.vue.vue-cli
Node and OS info
Node v8.11.3 / yarn 1.9.4 / macOs
Steps to reproduce
vue-config.js
What is expected?
It can create file's vue-config.js
What is actually happening?
Configure your Vue project .
It can't Create file vue-config.js  in project

I'm sorry but could you be more specific on what's happening? The description is too vague here.

Cannot save any configuration via Vue U after updating to vue 3.0.3 from 3.0.1 I changes in fields don't tracked, button freezes in refresh state to Cannot save any configuration via Vue UI after updating to vue 3.0.3 from 3.0.1 I changes in fields don't tracked, button freezes in refresh state

same problem https://github.com/vuejs/vue-cli/issues/2522


IMAGING-305 - Replace Collections.sort with list.sort.

Coverage remained the same at 76.667% when pulling c50f22b430b59d0bb984883693e1785d6dc0e80e on arturobernalg:feature/IMAGING-305 into 9d850d22a546963b86d13322db5d28350bd4ce81 on apache:master.

And merged, thanks @arturobernalg !


Helm: Enabled Modifying namespace of ServiceMonitors

Problem Statement
In some setup, ServiceMonitors are needs to be present in certain monitoring specific namespaces, and till now it used to deploy all ServiceMonitors in the same namespace where we are deploying the helm release. So using .Values.serviceMonitor.namespace you can supply the namespace where you want to deploy ServiceMonitors.
Proposed Changes
Just need to add a key in the values file, also I am keeping the default values(default .Release.Namespace) to be backward-compatible.
Checklist

[x] I have read the contribution guidelines
[x] All commits are signed with git commit --signoff
[x] My changes have reasonable test coverage
[x] All tests pass with make test
[x] I ensured my PR is ready for review with make reviewable

/approve

Hey @k4kratik, thank you for this :bow: :+1:

Thanks! @moolen  🎉🍻


fix: Typo in "Deperectation warnings"

Should be "Deprecatation warnings"

Fixed in release 10.0.7


libsecret: 0.21.2 -> 0.21.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for libsecret is: A library for storing and retrieving passwords and other secrets
meta.homepage for libsecret is: https://wiki.gnome.org/Projects/Libsecret
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.21.3 in filename of file in /nix/store/6nq4qsd9dnqrkba6w012b6v3lbj5qp51-libsecret-0.21.3

Rebuild report (if merged into master) (click to expand)

752 total rebuild path(s)

752 package rebuild(s)

First fifty rebuilds by attrpath
CHOWTapeModel
ChowKick
abaddon
abracadabra
adapta-gtk-theme
aegisub
ahoviewer
akkoma
alfaview
alfis
almanah
amule
amule-daemon
amule-gui
amule-web
ansel
anytype
apache-directory-studio
apostrophe
appgate-sdp
archi
arduino-ide
armcord
asc
asn1editor
astroid
audacity
aws-workspaces
ayatana-indicator-datetime
ayatana-indicator-session
badwolf
balsa
bambu-studio
beeper
bespokesynth
bespokesynth-with-vst2
beyond-identity
birdfont
bitwarden
bitwarden-directory-connector
bitwarden-directory-connector-cli
blackbox
boatswain
bochs
boinc
bookworm
bossa
bossa-arduino
bubblemail
budgie.budgie-control-center

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6nq4qsd9dnqrkba6w012b6v3lbj5qp51-libsecret-0.21.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libsecret https://github.com/r-ryantm/nixpkgs/archive/0b8c8f6ec4679886733bdc4adf644bcbeee9dbb2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0b8c8f6ec4679886733bdc4adf644bcbeee9dbb2#libsecret

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6nq4qsd9dnqrkba6w012b6v3lbj5qp51-libsecret-0.21.3
ls -la /nix/store/6nq4qsd9dnqrkba6w012b6v3lbj5qp51-libsecret-0.21.3/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @bobby285271 @hedning @jtojnar @dasj19 @amaxine @lovek323 @7c6f434c for testing.

@ofborg eval

Looks like the pam modile depends on gnome-keyring-daemon program so it might create a cyclic dependency if we enable it for GNOME 47.


vimPlugins.markdown-preview-nvim not working

When running :MarkdownPreview I get the following error (silently, I have to run :mes to see it)
internal/modules/cjs/loader.js:892
  throw err;
  ^
Error: Cannot find module 'tslib'
Require stack:
- /nix/store/5pvg3ncxdr0iqs8qm8j2163khsrl43y5-vimplugin-markdown-preview-nvim-2021-03-10/share/vim-plugins/markdown-preview-nvim/app/lib/app/index.js
- /nix/store/5pvg3ncxdr0iqs8qm8j2163khsrl43y5-vimplugin-markdown-preview-nvim-2021-03-10/share/vim-plugins/markdown-preview-nvim/app/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
    at Function.Module._load (internal/modules/cjs/loader.js:745:27)
    at Module.require (internal/modules/cjs/loader.js:961:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.<anonymous> (/nix/store/5pvg3ncxdr0iqs8qm8j2163khsrl43y5-vimplugin-markdown-preview-nvim-2021-03-10/share/vim-plugins/markdown-preview-nvim/app/lib/app/index.js:3:17)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Module.require (internal/modules/cjs/loader.js:961:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/nix/store/5pvg3ncxdr0iqs8qm8j2163khsrl43y5-vimplugin-markdown-preview-nvim-2021-03-10/share/vim-plugins/markdown-preview-nvim/app/lib/app/index.js',
    '/nix/store/5pvg3ncxdr0iqs8qm8j2163khsrl43y5-vimplugin-markdown-preview-nvim-2021-03-10/share/vim-plugins/markdown-preview-nvim/app/index.js'
  ]
}

building my system with 8d8a28b47b7c41aeb4ad01a2bd8b7d26986c3512
@ing @SuperSandro2000 since you're the last person to touch generated.nix and I don't know who specifically to @.

there are a few plugins that regularly break (unicode.vim too). Whoever tackles this it would be nice to add a checkPhase (see https://github.com/NixOS/nixpkgs/pull/117285 for inspiration).

tslib is missing. Probably the package.json for that plugin needs to be updated.

According to README https://github.com/iamcco/markdown-preview.nvim/#install--usage
The extension requires a yarn init to populate the node_modules first. But we currently simply download and unpack the source code.
I'm curious about how it works at the first place.


unittests_umer

Codecov Report

Merging #32 (f3ae55f) into master (d2d2eab) will increase coverage by 0.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   90.60%   91.15%   +0.55%
==========================================
  Files         100      100
  Lines        3076     3076
==========================================
+ Hits         2787     2804      +17
+ Misses        289      272      -17

Flag
Coverage Δ

unittests
91.15% <ø> (+0.55%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

domainlab/compos/nn_zoo/net_conv_conv_bn_pool_2.py
100.00% <0.00%> (+30.30%)
:arrow_up:

domainlab/utils/utils_img_sav.py
100.00% <0.00%> (+31.81%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


NIFI-4975 Add GridFS processors

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@pvillard31 @mattyb149 @mans2singh Anyone up for a code review?
All of the tests work out of the box w/ dockerized Mongo using defaults:
docker run --name mongotest -p 27017:27017 mongo:latest

@mattyb149 when I rebased this commit, I added fixes for the integration tests so they could run again with the new way of handling EL.

@zenfenan @mattyb149 any chance we could get a review going for this before 1.8?

@zenfenan @mattyb149 any chance we could close this one? It's been sitting here for almost a year and hits some big Mongo functionality.

@zenfenan @mattyb149 anyone?

@mattyb149 Everything should be in order based on your feedback now.

@mattyb149 Wrote up documentation for all three new processors that should set things straight.

+1 LGTM, thanks for the new features and for adding the extra documentation! Waiting for Travis then merging to master


[runtime] addressed review comments outlined in #1950

What's in this pull request?
Addresses final review comments outlined in #1950
@gparker42

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

Working on understanding Linux build failure

I guess this is a "flaky" test that can fail on Linux?
    @skipIfWindows #llvm.org/pr24452: Get lldb-mi tests working on Windows
    @skipIfFreeBSD # llvm.org/pr22411: Failure presumably due to known thread races
    @expectedFlakeyLinux("llvm.org/pr24717")
    def test_lldbmi_break_insert_function_pending(self):

I'm not worried about that lldb test failure.

Looks good.


Add 'updated' to queryfields; dateFormat template command; bug fix.

I've included the 'updated' field into the default query fields, as it seemed like an oversight, and I need it :)
In the process, noticed that export-templates was broken due to a typo, so fixed that.
I've added a dateFormat template helper, so I can get the create/update time in a more report friendly form.

Nice, looks good, thanks!
Side note, you could have added "updated" to your default list of queryfields via configuration by modifying your ~/.jira.d/config.yml to have:
queryfields: summary,created,updated,priority,status,reporter,assignee

-Cory


Using UUID Output from “generator/Create and sign provenance” Step in generator_generic_slsa3 Job

When using generator_generic_slsa3 in the workflow, the last part of the "generator/Create and sign provenance" step outputs "Uploaded signed attestation to rekor with UUID". I would like to use this UUID value as input in a subsequent job. How should I do this?

You would have to modify the workflow to save the command output as  Step, Job, and Workflow outputs. We would welcome a PR.
From

https://github.com/slsa-framework/slsa-github-generator/blob/main/.github/workflows/generator_generic_slsa3.yml#L237

your_command | tee >(read -r output; export MY_VAR="$output")

And set the output like this

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter

CAn you tell us more about your use-case for outputting the rekor UUID as a workflow output?

Can you tell us more about your use-case for outputting the rekor UUID as a workflow output?

We need to search for unique logs in sigstore using the rekor UUID to verify provenance. Using only the hash isn’t sufficient to identify the provenance generated by the current workflow, especially if the deployment fails or multiple people deploy the same code. Therefore, the rekor UUID as a workflow output is crucial for accurately identifying the generated provenance.

For Sigstore, we want to discourage doing live lookups in the log in favor of verifying persisted inclusion proofs offline. We've filed an issue (https://github.com/slsa-framework/slsa-github-generator/issues/3750) to track support for this. In the meantime, adding the Rekor entry UUID as output seems reasonable.

Closing due to inactivity.


chore(ci) Set up CircleCI

Let's try it.

Trying to find a workaround to solve https://bugs.php.net/bug.php?id=75951.


Add a new advanced/custom_strategy example

Description
This PR adds a new example for using Custom Access Strategies. It can serve as boilerplate for customers wanting to implement them.
The docs here will be updated to match this to bring them in line with the other examples.

Current dependencies on/for this PR:

main

PR #87   👈

This comment was auto-generated by Graphite.


Update Remove-SPEnterpriseSearchComponent.md

Format example

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPEnterpriseSearchComponent.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


"Alexandru cel Bun", "Viișoara", "Agârcia" and "Bisericani" are listed in the drop-down menu

Description:
"Alexandru cel Bun", "Viișoara", "Agârcia" and "Bisericani" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Alexandru cel Bun" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Alexandru cel Bun, NEAMȚ".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Viișoara" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Viișoara, NEAMȚ (Alexandru cel Bun)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Agârcia" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Agârcia, NEAMȚ (Alexandru cel Bun)".

Step 7
Type "Bisericani" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Bisericani, NEAMȚ (Alexandru cel Bun)".


Some proxies failed to resolve.

After analyzing a lot of data, most of the addresses are doing a good job of detection. The address below belongs to a proxy, but there is no way to resolve it, I don't know if I'm using the wrong method or what?
TransparentUpgradeableProxy?
"""
Error processing proxy resolver EIP1967Proxy: missing revert data (action="call", data=null, reason=null, transaction={ "data": "0x5c60da1b", "to": "0x3E135c3E981fAe3383A5aE0d323860a34CfAB893" }, invocation=null, revert=null, code=CALL_EXCEPTION, version=6.7.1)
"""
Create2BeaconProxy?
"""
Failed to resolve proxy for address: 0x581acd618ba7ef6d3585242423867adc09e8ed60
Failed to resolve proxy for address: 0xa6a3448ea5f5f15ee6c089279712f720c0e16a7f
Failed to resolve proxy for address: 0xb6fc082fdc4dbe19e85d50bde82214919526cb2a
Failed to resolve proxy for address: 0xc088661f2703e5c011612d6a7ff960ee669f8b56
Failed to resolve proxy for address: 0x9b9278c8eb1e49eb3ced22a2d4e144479f07c7df
Failed to resolve proxy for address: 0x9608b7496838e7e00a57cb681b469666a33d8b20
Failed to resolve proxy for address: 0xe5f74b8e5ece57ef1c129523133b5d19ddf8f19d
Failed to resolve proxy for address: 0x5faf6a2d186448dfa667c51cb3d695c7a6e52d8e
Failed to resolve proxy for address: 0x1b80250c32d5b5e278d03e9843475c56bf0a439e
Failed to resolve proxy for address: 0xb9e068ea140511175b6e487b5b48e993bf11838d
Failed to resolve proxy for address: 0xe1aef926b8c94a3fbbeade65afc94dc02803ed40
Failed to resolve proxy for address: 0x8217772e6fe703f18c5c08ea04ab962395f62aa6
Failed to resolve proxy for address: 0x4af84cfb08b484cd32e4378a4b627a5f009b5117
Failed to resolve proxy for address: 0xcca916ff964fdc93cfbe7d34cd888ff28142e645
Failed to resolve proxy for address: 0xdff8bad97aae5995ba0c8d4bdd36f8b5d577e9e4
Failed to resolve proxy for address: 0xbaf6c73a06afd9e02a4af28901698e52fe3cc973
Failed to resolve proxy for address: 0xb8945c69aeb8ad8e16f1e49eaef5c7e48011d178
Failed to resolve proxy for address: 0x0f7c258ef6abd872dd5481785116556a85856ada
Failed to resolve proxy for address: 0x29f033720d84d0f85c1beccf80e51449c06ca2d2
Failed to resolve proxy for address: 0xeb07c09a72f40818704a70f059d1d2c82cc54327
Failed to resolve proxy for address: 0x574cce720237a9d2e679d9093c508e0cceeb2535
Failed to resolve proxy for address: 0xbd2861c0f43f6e8d571fcfa5a7c77d13d5695ebf
Failed to resolve proxy for address: 0x5cd5623aa41a139021645765cebfb4a82a43f029
Failed to resolve proxy for address: 0xd4108bb1185a5c30ea3f4264fd7783473018ce17
Failed to resolve proxy for address: 0x67b9f46bcba2df84ecd41cc6511ca33507c9f4e9
Failed to resolve proxy for address: 0x64c24088de9c5c9197ced6ce9adce16c802fd844
Failed to resolve proxy for address: 0xbf9b32dae8c5267c9295e875f8943b1224d12975
Failed to resolve proxy for address: 0x29b145edfa80b20a3f6f79b57ef4b1ca33ad2777
Failed to resolve proxy for address: 0x471de8beadecd171de505a707bdf0e783a794126
Failed to resolve proxy for address: 0x60a80cbd47e738c88ff414f304fc9b116be37b92
Failed to resolve proxy for address: 0x2e4c82b9f5aa477aba5594ecf5412e4f42c56b7f
Failed to resolve proxy for address: 0x902cf5373317bb3e42660e9f4e85aa21532c0e44
Failed to resolve proxy for address: 0x490d19e4cca09e552c5b1844410e9163182b44d4
Failed to resolve proxy for address: 0xdacf926c6ed25232db5d64288659784147335f5e
Failed to resolve proxy for address: 0xec3c709993f5deda568d6dab09c90bf533021171
Failed to resolve proxy for address: 0x50ace5c459bc3ba3bc1aad7dfb62f88bb94afa06
Failed to resolve proxy for address: 0x5868125220188b260b31e0b4f7a53d3e965a0907
Failed to resolve proxy for address: 0x88ee509e02cfa939430cb8452e63c296be770f96
Failed to resolve proxy for address: 0x8aab6f7f32f9da2c5efb6ab62d76130aeaa5cf69
Failed to resolve proxy for address: 0x35822eaf02cae69e97f5fa36f0188686fa544e21
Failed to resolve proxy for address: 0xa9e1f9c1ec6ecb103c260c3eda0fa28e2785c57a
Failed to resolve proxy for address: 0x5c0a86a32c129538d62c106eb8115a8b02358d57
Failed to resolve proxy for address: 0x5d1c5dee420004767d3e2fb7aa7c75aa92c33117
Failed to resolve proxy for address: 0x829b97a6218d320e97c0a915eb8a07c4dd408cd5
Failed to resolve proxy for address: 0xd1e9a67c7e0558b55341ffdbbef9d34b9db6f235
Failed to resolve proxy for address: 0xf8f815859a6b3447cbeb04301fa35a86c5272f0d
Failed to resolve proxy for address: 0x7f30476e51d7f6286a74b3b314fff51bc7cead92
Failed to resolve proxy for address: 0x1d47322cddbb832b74d8b584aa42ece998498ebe
Failed to resolve proxy for address: 0xa8d412f570401eaad3059d3d4df6336fb37e17e0
Failed to resolve proxy for address: 0x614a03f9db294c7def83423f9719d22410c1abef
Failed to resolve proxy for address: 0x14d1551e734a324ba148158de9981f17f9de73c4
Failed to resolve proxy for address: 0xc58ad9817a324aafa489d30eaf53376b28a9641e
Failed to resolve proxy for address: 0x8c3ab8544b32d0181d53f0004cc51793101e9536
Failed to resolve proxy for address: 0x28cad0a218d15b7b651a06b444f39e7186b52fcb
Failed to resolve proxy for address: 0x3dfc321b714262902468b024d704f6039b650570
Failed to resolve proxy for address: 0xa813f02f95228642a60f6e3cf5ac0273c4160613
Failed to resolve proxy for address: 0x3e7d590b398a8bd7a12fb6071af197bf74248895
Failed to resolve proxy for address: 0x4723df875d4bfdfe4190236b307ec4a65b00002e
Failed to resolve proxy for address: 0x7f44bb621bd9ddceb02540ea2b51c60d6cc4b430
Failed to resolve proxy for address: 0x4c9725cd7db182d5b23e99855e357e3f4742c137
Failed to resolve proxy for address: 0x8eb40c1805ae6a6ce8e8b09ca0e5bbad5a2af7ca
Failed to resolve proxy for address: 0x2c7a424fc64a78cd263ff767d7af875647fcd3b0
Failed to resolve proxy for address: 0x555cccf378b01c550cc7cc7aa138eec70e4c4f33
Failed to resolve proxy for address: 0x9fcb13e8563fb8954b64d50074be596a651a67f5
Failed to resolve proxy for address: 0xb05827f130d2aac67081d9ca84742a6d199a5d9d
Failed to resolve proxy for address: 0x790a60024bc3aea28385b60480f15a0771f26d09
Failed to resolve proxy for address: 0x366834589352937c88aaad8be569e606d58a3f81
Failed to resolve proxy for address: 0xf6fa4cf51258c21cb94918b1100c99968f32f6e0
Failed to resolve proxy for address: 0xa2999e886a9f4d1bae6ecfec614edfce5d8e06c2
Failed to resolve proxy for address: 0xf78b9bae2f7968918deeda37551b7dd83b6dffea
Failed to resolve proxy for address: 0xba63baffcebb44aa560e5f0671d1049ffa05c1c9
Failed to resolve proxy for address: 0x70f79de002b434ee033ea7e9349c310e18f7eb46
Failed to resolve proxy for address: 0xa183014cef1dfc81cb3fd1dd2ce2ea1380fd983d
Failed to resolve proxy for address: 0xe53e3d446a2ac0d19f6481a2462dd43309f341d7
Failed to resolve proxy for address: 0xd4d5f210a1c6acf2a5d2f7f6ab3158711236c417
Failed to resolve proxy for address: 0xd30dd3b2804d4a41b2c796a4b5ac307b2672e2f3
Failed to resolve proxy for address: 0x8363713fe51ad37a113a1aa1ae61b20e42414e5c
Failed to resolve proxy for address: 0xd7df60f0857cfb0003f389ff338df50ba5c17fde
Failed to resolve proxy for address: 0x663134dc10acac6a5f5ad9d3231c51d71de0f0da
Failed to resolve proxy for address: 0xa07c7cebcd136a5c255ad20534d31cd1afba42e6
Failed to resolve proxy for address: 0x7472fbf0130a71d1241890cf5d068be4778c6154
Failed to resolve proxy for address: 0x2b39eceafe795cd4debca0721f2f68409e3b7df2
Failed to resolve proxy for address: 0x48672352e191b2e78bbc319e1d3e751ffc64439d
Failed to resolve proxy for address: 0x04e037787a6e79e6aaea79dbb7a7c4109f49d4bd
Failed to resolve proxy for address: 0x4a7a4c6cf6f0d0e9542df29974e40b4de2178ebc
Failed to resolve proxy for address: 0x804bc39d5670ca176203556dac06fcd7ed37ddb1
Failed to resolve proxy for address: 0xf80ffb0699b8d97e9fd198ccbc367a47b77a9d1c
Failed to resolve proxy for address: 0xcb48144a9fd2c4fa23905762d4e4257d6136adbc
Failed to resolve proxy for address: 0x164a468709bc32f826979fd20322a3ea676a3481
Failed to resolve proxy for address: 0x08765c76c758da951dc73d3a8863b34752dd76fb
Failed to resolve proxy for address: 0xb91bca4c6a607448a093803b3b2a9a4ed3e9f71e
Failed to resolve proxy for address: 0x7e94fb2a0d2db1ff9c85ac818fd28b8bcb799a8b
Failed to resolve proxy for address: 0x4e4a158159e35cce9c94344d503091d8b2a90952
Failed to resolve proxy for address: 0x90b9162018be1b4b09073eca5925b08d19b63541
Failed to resolve proxy for address: 0xe61186dea096349eb5652d45c16079d56d2c2b22
Failed to resolve proxy for address: 0x7229e4e13dd6668c34026f4baa2e44a704bfa5ae
Failed to resolve proxy for address: 0xc60af90a13173353565832f02a2a48222b97ab15
Failed to resolve proxy for address: 0xb31858b8a49dd6099869b034da14a7a9cad1382b
Failed to resolve proxy for address: 0xbf5c04491638bbb3912092e9e9427e376b6554cb
Failed to resolve proxy for address: 0x3451b4c5395b3fe06aa629af73207cfaa28131d1
Failed to resolve proxy for address: 0x4786d62edf0dc42d905107f8b04bbc2779afe90d
Failed to resolve proxy for address: 0x9251e59b053d9407a16f1bd53a3136f4897d7c06
Failed to resolve proxy for address: 0x66d461ba3f1da2b32bf5b8dca3a40b905ab7c639
Failed to resolve proxy for address: 0xcb784233855c97d8532f8eefa094ba876187a150
Failed to resolve proxy for address: 0xabbdbb92cd58fd2f7dba953855b88ed2a2be1465
Failed to resolve proxy for address: 0x929fd5879847f41f05b6cf3746b4343f38b8741b
Failed to resolve proxy for address: 0x96ad7aee7cf43ae2165c485b40c18cae0eba98b4
Failed to resolve proxy for address: 0x1ea1ccfecc55938a71c67150c41e7eba0743e94c
Failed to resolve proxy for address: 0x11df658567e615f69d23289be8a27a9c260ce297
Failed to resolve proxy for address: 0xcbc439fbb8ef91f64631d13187c8d4c96410e8ca
Failed to resolve proxy for address: 0x65879e73aecfc8a1cc7fe44a2ffb3392721e5652
Failed to resolve proxy for address: 0x47be8559ecbaeb84c759c215497d40334f97d754
Failed to resolve proxy for address: 0x3d21b6f588428fcb9091ebd799feabe3eaf4977f
Failed to resolve proxy for address: 0xaeb780ca1b17e9429f84e15a375491cb5372b4ca
Failed to resolve proxy for address: 0x573f76519bb7fd10c95b38f4ffd569d9a3989c39
Failed to resolve proxy for address: 0x4500dcdcb468979f859c56cfcb1040173c69dde8
Failed to resolve proxy for address: 0xa48f2713a0c92b0395ba964e68079d8b07da729d
"""
Vyper_contract?
"""
Failed to resolve proxy for address: 0x2d5d4869381c4fce34789bc1d38acce747e295ae
Failed to resolve proxy for address: 0x84ca3bf4822a342e9c1ad27bd5fbcf5fc5e37128
Failed to resolve proxy for address: 0xff8f8a38c80b9899a928152d58f219fdccd4306c
Failed to resolve proxy for address: 0xd1a075c806e40d79e32ea09553e7080d5d9d4b29
Failed to resolve proxy for address: 0xf59d66c1d593fb10e2f8c2a6fd2c958792434b9c
Failed to resolve proxy for address: 0xd070f6216ef1f2609dfae2ae7e3d7208b1e993d5
Failed to resolve proxy for address: 0x378cb52b00f9d0921cb46dfc099cff73b42419dc
Failed to resolve proxy for address: 0x16825039dfe2a5b01f3e1e6a2bbf9a576c6f95c4
Failed to resolve proxy for address: 0xd8c620991b8e626c099eaab29b1e3eea279763bb
Failed to resolve proxy for address: 0x6fafca7f49b4fd9dc38117469cd31a1e5aec91f5
Failed to resolve proxy for address: 0x4fdd1b06ef986238446be0f3ea163c1b6fe28cc1
Failed to resolve proxy for address: 0x7f7df0e9a040dda05fc609143cc8da7cc6c59587
Failed to resolve proxy for address: 0xa72ad1293b253522fde41f1104aa432d7669b299
Failed to resolve proxy for address: 0x2807387f1212cb2852ab97cdaa3627daca5e4661
Failed to resolve proxy for address: 0xb85e3fe36a6084985e66d704abd4be4ea51e06ce
Failed to resolve proxy for address: 0xafb6c80ff3cfdae5977df0196f3d35cd65e3c7a3
Failed to resolve proxy for address: 0xba3cfea6514cf5acddeff3167df0b7a4337751bc
Failed to resolve proxy for address: 0x5dc81697fc0b3752c1277d260064374e95e8a18b
Failed to resolve proxy for address: 0xfc1cf3dc111981ea4372e91f437581524f3721be
Failed to resolve proxy for address: 0xe02c8114b66e838e028ae743fee915ba530b24e6
Failed to resolve proxy for address: 0xe4174e39beeebb85c7c36cba68f316a5144e7d08
Failed to resolve proxy for address: 0x817fe0d7935170dc91ccbe4aa3450abde302bf10
Failed to resolve proxy for address: 0x528d50dc9a333f01544177a924893fa1f5b9f748
Failed to resolve proxy for address: 0x59518884eebfb03e90a18adbaaab770d4666471e
Failed to resolve proxy for address: 0x7158c1bee7a0fa5bd6affc77b2309991d7adcdd4
Failed to resolve proxy for address: 0x1f8ad2cec4a2595ff3cda9e8a39c0b1be1a02014
Failed to resolve proxy for address: 0x5120feabd5c21883a4696dbcc5d123d6270637e9
Failed to resolve proxy for address: 0x2dfb14e32e2f8156ec15a2c21c3a6c053af52be8
Failed to resolve proxy for address: 0xdf5110ef6bc751cbaf76d35b8a3f312b581b5173
Failed to resolve proxy for address: 0x8472e9914c0813c4b465927f82e213ea34839173
Failed to resolve proxy for address: 0xfd0877d9095789caf24c98f7cce092fa8e120775
Failed to resolve proxy for address: 0xf11b141be4d1985e41c3aea99417e27603f67c4c
Failed to resolve proxy for address: 0x6d765cbe5bc922694afe112c140b8878b9fb0390
Failed to resolve proxy for address: 0x497590d2d57f05cf8b42a36062fa53ebae283498
Failed to resolve proxy for address: 0x4962b6c40b5e9433e029c5c423f6b1ce7ff28b0f
Failed to resolve proxy for address: 0x2147935d9739da4e691b8ae2e1437492a394ebf5
Failed to resolve proxy for address: 0x63739d137eefab1001245a8bd1f3895ef3e186e7
Failed to resolve proxy for address: 0xce0f1ef5aaab82547acc699d3ab93c069bb6e547
Failed to resolve proxy for address: 0xf962b098ecc4352aa2ad1d4164bd2b8367fd94c3
Failed to resolve proxy for address: 0x71955515adf20cbdc699b8bc556fc7fd726b31b0
Failed to resolve proxy for address: 0x4856a7efbbfcae92ab13c5e2e322fc77647bb856
Failed to resolve proxy for address: 0xa2619fdfb99abeb533a1147461f3f1109c5ade75
Failed to resolve proxy for address: 0xb98df7163e61bf053564bde010985f67279bbcec
Failed to resolve proxy for address: 0xd2c65e20c3fde3f18097e7414e65596e0c83b1a9
Failed to resolve proxy for address: 0x477faf103dadc5fe5baa40951cf7512dcbc18126
Failed to resolve proxy for address: 0x2f194da57aa855caa02ea3ab991fa5d38178b9e6
Failed to resolve proxy for address: 0x49b3e44e54b6220af892dba48ae45f1ea6bc4ae9
Failed to resolve proxy for address: 0xaf322a2edf31490250fdeb0d712621484b09abb6
Failed to resolve proxy for address: 0xac1c90b9c76d56ba2e24f3995f7671c745f8f308
Failed to resolve proxy for address: 0xb32747b4045479b77a8b8eb44029ba12580214f8
Failed to resolve proxy for address: 0x1ae8ccd120a05080d9a01c3b4f627f865685d091
Failed to resolve proxy for address: 0x56a5fd5104a4956898753dfb060ff32882ae0eb4
Failed to resolve proxy for address: 0x3466c90017f82dda939b01e8dbd9b0f97aef8dfc
Failed to resolve proxy for address: 0x7356f09c294cb9c6428ac7327b24b0f29419c181
Failed to resolve proxy for address: 0x0e880118c29f095143dda28e64d95333a9e75a47
Failed to resolve proxy for address: 0x0e8a7717a4fd7694682e7005957dd5d7598bf14a
Failed to resolve proxy for address: 0x314f951d144b397a088ea9eac5218bdc7db2ed4a
Failed to resolve proxy for address: 0xfcf8eda095e37a41e002e266daad7efc1579bc0a
Failed to resolve proxy for address: 0xed0244b688cf059f32f45e38a6ac6e479d6755f6
Failed to resolve proxy for address: 0x8e666277c3de28df68a78ede1274603eeea02d34
Failed to resolve proxy for address: 0x5dcd2999ff0685f6165938ec717b26b48998921c
Failed to resolve proxy for address: 0xa5ed287499e3c192c444336342bc4b0e25f51d88
Failed to resolve proxy for address: 0xa5588426040db2c83db16f640f64c7fb265974d4
Failed to resolve proxy for address: 0x83c8df34c6a9d31b97516791f85bac51ed37d49e
Failed to resolve proxy for address: 0xab2ccd6652a170f8fafff115b03ceb30fe855daf
Failed to resolve proxy for address: 0x0bacea14e683e42059c069bc96187520cb282cb9
Failed to resolve proxy for address: 0x8174bff3c861ef667b5f911884f4f7324b2b9c4f
Failed to resolve proxy for address: 0xda82b333a79cb07ddcec69580088f3d8b8f62915
Failed to resolve proxy for address: 0x23d737c8836977739b9a8dc6ddaf64c67bc936f7
Failed to resolve proxy for address: 0x386af2b835d90bc3c5d4e7ae3b1d27ba0f1d0724
Failed to resolve proxy for address: 0x56c218d200247cc7687b4fac31a371e38f6c8b55
Failed to resolve proxy for address: 0x9df9d1d176702bded106149f29005a9be1277ab4
Failed to resolve proxy for address: 0x6a072ff54db0a61476c53d829cd4ad8c91739825
Failed to resolve proxy for address: 0x4264c78898744167a26f886da6ce763965e4bba1
"""
Failed to resolve proxy for address: 0x9e9404849b9a6dd520bd6199aee5ce7f76c09245

Oh that's a great list, thank you! I'll try to tackle some of these next week.

Latest release (v0.8.1 or v0.8.2 coming in a moment) should have this fixed (included a few tests from the addresses you included too). Thanks! Please report back if you find more. :)


feat(mr): mr settings scaffolding

Closes: https://issues.redhat.com/browse/RHOAIENG-7057
Description
Scaffolding for model registry admin settings, component with just empty state for now

How Has This Been Tested?
manually tested that the nav item shows up based on useArea, and that the page renders the empty state properly
Test Impact
none, just scaffolding for now
Request review criteria:
make sure the nav item appears properly and that the page renders empty state with an action button that navs to model registries.
i had to run /backend vs :ext from /frontend as the :ext doesn't have the setting for it yet.
Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/retest-required

Codecov Report
Attention: Patch coverage is 44.44444% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 78.09%. Comparing base (54f4402) to head (ca003db).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2810      +/-   ##
==========================================
- Coverage   78.09%   78.09%   -0.01%
==========================================
  Files        1075     1076       +1
  Lines       22607    22616       +9
  Branches     5715     5715
==========================================
+ Hits        17656    17661       +5
- Misses       4951     4955       +4

Files
Coverage Δ

frontend/src/concepts/areas/const.ts
100.00% <ø> (ø)

frontend/src/concepts/areas/types.ts
100.00% <100.00%> (ø)

frontend/src/utilities/NavData.tsx
97.91% <100.00%> (+0.09%)
:arrow_up:

frontend/src/app/AppRoutes.tsx
91.66% <50.00%> (-1.82%)
:arrow_down:

...es/modelRegistrySettings/ModelRegistrySettings.tsx
0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


issue in csi data collection

not able to run this command , cant get past this step

From the Readme:

Notice, this project requires version (v4.3) of ESP-IDF.

and

Important: It is important that you are able to successfully build and flash the example project from the esp-idf guide onto your own esp32. If you have issues building the example project on your hardware, do not create an issue in this github repo. We will not be able to assist with general ESP32 issues (those issues that are unrelated to this project).

However, looking at the screenshot, I do not see any errors. What is the issue that you need solved? The command you run will not print any information, it should be writing data to the .csv file

I have a similar issue. I'm having trouble saving CSI data into csv files -- the csv files are being created but they're empty/broken when I run the command in the screenshot below. I was expecting to see at least something being saved into the csv file since when I ran idf.py monitor I did see CSI data being printed in the terminal (though it was very laggy). I've also tried idf.py monitor | findstr "CSI_DATA" > my-experiment-file.csv  but it shows the same result.

我也遇到了这个问题

I am also having the same issues. I am not able to stop the CSI data into css file. But when I run idf.py flash monitor  I can see the following output. Can you please help me out?

Hello, I'm facing issue as @ag220502 has mentioned. After flashing it shows this green and white text, but no CSI Data...


chore: deprecate plugins

Summary
Plugins will be removed in 3.0.

Will there be anything instead of plugins? We use post-processing


Uncontrolled datetime formats

We've been using your library for a while and there have been quite a few validation errors from uncontrolled datetime formats. About two hundred date-time formats come from these formats:
2010-07-04 04:18:23 +03:00
2024-02-19 01:30:15.927683+11
07 Aug 2024
2008-08-31 04:14:06 KST
2024/01/01 01:05:04 (JST)
The parser from dateutils.parse was able to control the first three formats, and by adding a method to remove the "(" and ")" and using tzinfos i was able to convert all of them properly:
def clean_timezone(date_str)
return re.sub(r'(([^)]+))', r'\1', date_str).strip()
... Existing code ...
tzinfos = {
'KST': tz.gettz('Asia/Seoul'),  # Korea Standard Time UTC+9
'JST': tz.gettz('Asia/Tokyo'),  # Japan Standard Time UTC+9
}
....
if type(whois_info['created']) == str:
created = parse(clean_timezone(whois_info['created']), tzinfos=tzinfos)
else:
created = whois_info['created']
...
I noticed you're using a list of date_time formats and trying to parse the string with these formats:
https://github.com/pogzyb/asyncwhois/blob/b9cdc92a57b9a56e64fbb23947e9223c77ab47c6/asyncwhois/parse.py#L337-L350
I think you would be better off by using dateutil.parser with a few tzinfos and then having a reduced list that is used when that can't cut it.
Here I put a python script (in .txt) to test all your formats + these 5, and their timings with dateutils.parser and with your function. There are 6 commented formats which would be the only ones you need to control with an except and your method  instead of with dateutil.parser. The tests might not be 100% accurate because your list could be ordered by popularity and so doing the same amount of tests with each format would not be the best method, however i think the difference in time is enough to indicate that the new method might be better.

asynwhois_vs_custom_tests.txt

Hi,
Thanks for clearly outlining and describing the issue! I agree with your assessment, dateutil.parse seems like a much better option for handling date parsing. I attempted to add your suggestions in #94 . Specifically, the BaseParser and parse_date function now look like this:
class BaseParser:
    reg_expressions = {}

    date_keys = ()
    multiple_match_keys = ()

    # For handling special cases in TLD parser classes
    known_date_formats = []
    # Extra formats that dateutil might not figure out
    extra_date_formats = [
        "%Y-%m-%dT%H:%M:%SZ[%Z]",  # 2007-01-26T19:10:31Z[UTC]
        "%Y-%m-%dT%H:%M:%S.%fZ",  # 2018-12-01T16:17:30.568Z
        "%Y-%m-%dT%H:%M:%S%zZ",  # 1970-01-01T02:00:00+02:00Z
        "%Y-%m-%dt%H:%M:%S.%fz",  # 2007-01-26t19:10:31.00z
        "%Y-%m-%d %H:%M:%SZ",  # 2000-08-22 18:55:20Z
        "before %b-%Y",  # before aug-1996
    ]
    # Additional timezone info for dateutil
    timezone_info = {
        "KST": tz.gettz("Asia/Seoul"),  # Korea Standard Time UTC+9
        "JST": tz.gettz("Asia/Tokyo"),  # Japan Standard Time UTC+9
        "EEST": tz.gettz("Europe/Athens"),  # Eastern European Summertime UTC+3
    }

    ...

    def _parse_date(self, date_string: str) -> Union[datetime, str]:
        """
        Attempts to convert the given date string to a datetime.datetime object
        otherwise returns the input `date_string`
        :param date_string: a date string
        :return: a datetime.datetime object
        """

        def _datetime_or_none(dt_string: str, dt_format: str) -> Union[datetime, None]:
            try:
                return datetime.strptime(dt_string, dt_format)
            except ValueError:
                return None

        # first, try the known formats
        for date_format in self.known_date_formats:
            if date := _datetime_or_none(date_string, date_format):
                return date
        # next, try dateutil.parse
        try:
            clean_date_string = re.sub(r"\(([^)]+)\)", r"\1", date_string).strip()
            return parse(clean_date_string, tzinfos=self.timezone_info)
        except ParserError:
            pass
        # finally, try extra formats
        for date_format in self.extra_date_formats:
            if date := _datetime_or_none(date_string, date_format):
                return date
        # no luck parsing
        return date_string

I also added and modified your example script under tests/test_dateparsers.py, which looks like:
from datetime import datetime

from asyncwhois.parse import BaseParser

def test_dateparsers():  # noqa
    date_and_time_examples = [
        "2010-07-04 04:18:23 +03:00",
        "2024-02-19 01:30:15.927683+11",
        "2008-08-31 04:14:06 KST",
        "2024/01/01 01:05:04 (JST)",
        "07 Aug 2024",
    ]
    date_and_time_examples += [
        "02-jan-2000",
        "11-February-2000",
        "20-10-2000",
        "2000-01-02",
        "2.1.2000",
        "2000.01.02",
        "2000/01/02",
        "2011/06/01 01:05:01",
        "2011/06/01 01:05:01 (+0900)",
        "20170209",
        "20110908 14:44:51",
        "02/01/2013",
        "2000. 01. 02.",
        "2014.03.08 10:28:24",
        "24-Jul-2009 13:20:03 UTC",
        "Tue Jun 21 23:59:59 GMT 2011",
        "2007-01-26T19:10:31",
        "2007-01-26T19:10:31Z",
        "2007-01-26T19:10:31Z[UTC]",  # extra
        "2018-12-01T16:17:30.568Z",  # extra
        "2011-09-08T14:44:51.622265+03:00",
        "2013-12-06T08:17:22-0800",
        "1970-01-01T02:00:00+02:00Z",  # extra
        "2011-09-08t14:44:51.622265",
        "2007-01-26T19:10:31",
        "2007-01-26T19:10:31Z",
        "2007-01-26t19:10:31.00z",  # extra
        "2011-03-30T19:36:27+0200",
        "2011-09-08T14:44:51.622265+03:00",
        "2000-08-22 18:55:20Z",  # extra
        "2000-08-22 18:55:20",
        "08 Apr 2013 05:44:00",
        "23/04/2015 12:00:07",
        "23/04/2015 12:00:07 EEST",
        "23/04/2015 12:00:07.619546 EEST",
        "2015-04-23 12:00:07.619546",
        "August 14 2017",
        "08.03.2014 10:28:24",
        "Tue Dec 12 2000",
        "before aug-1996",  # extra
        "2017-09-26 11:38:29 (GMT+00:00)",
    ]

    bp = BaseParser()

    for dt in date_and_time_examples:
        result = bp._parse_date(dt)
        assert isinstance(result, datetime), f"Failed to parse date string: {dt}"

Let me know if this looks OK or if there is anything I may have overlooked in your suggestion.


Add body metadata columns for body center coords, size

Add columns for the coordinates and size (in pixels) of all bodies in a frame.  Best approach may be to add to existing body tables.

Is this redundant w #93?

Yes

Closed in favor of #93, which contains more detail


Set CPU as default device in INC training examples

Set temporarily CPU as default device in INC training examples, this will be removed when neural-compressor next release is out

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Verio iq ui

We are publishing the OneTouch VerioIQ driver for your consideration.

I'm closing this PR, as I've now moved these changed to a new PR in #157. This enables me to resolve merge conflicts etc. faster.


where to set secret_key without tripping deprecation warnings

The devise secret_key should be set differently in development/test, and production, and I think that the production key should kept out of github.  So initializing it from config/environments/production.rb would seem to make sense, with that file being stored on production machines only via capistrano's mechanisms for doing this.
A naive method would add this to environments/*.rb:
Devise.setup do |config|
  config.secret_key = 'something'
end

this runs afoul of the deprecation warnings, since it sets up the configuration without all the things that later on are loaded from config/initializers/devise.rb.   Short of throwing in a require into initializers/devise.rb to load another file.
Is there some way to store this in config/secrets.yml, for instance?

@mcr
I think you can use env variable, for example:
config.secret_key = ENV['DEVISE_SECRET_KEY']

Or you can take a look at the Rails custom configuration. There's awesome tips in how proper set your custom configurations. You can do something like this:
config.secret_key = Rails.configuration.x.devise.secret_key

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.


CMake improvements for stand-alone builds

Improves the Bond CMake build to make it easier to build the minimum amount needed to consume Bond in a C++ project.

Improve logic to locate a pre-compiled gbc
Add ability to request that just the libraries be built and no additional tools (like bf)

MSVC C++ 2013 build timed out. Merging anyway.


Could not access subscriptions due to expired login refresh token

Azure Data Studio Version: 1.31.0
OS Version: Windows_NT x64

On the SQL Migrations extension, my Azure subscriptions weren't populating caused by an expired login token. It looks like I last logged into my Microsoft account on ADS on 2021-02-09. Since it's been more than 90 days, the login token expired.
There should be some form of communication letting me know I should re-login or why my subscriptions weren't loading.
Resolved this by removing my Microsoft account and logging in again.
Response error! - {"error":"invalid_grant","error_description":"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-02-09T19:27:38.3331129Z and was inactive for 90.00:00:00.\r\nTrace ID: {TRACE ID}\r\nCorrelation ID: {CORRELATION ID}\r\nTimestamp: 2021-07-01 23:04:41Z","error_codes":[700082],"timestamp":"2021-07-01 23:04:41Z","trace_id":{TRACE ID},"correlation_id":{CORRELATION ID},"error_uri":"https://login.microsoftonline.com/error?code=700082"}

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

Duplicate of #14159


WIP: Interpfilter search

Coverage increased (+0.03%) to 75.452% when pulling 6f58eec5b580da645506173081011fb702f69663 on tdaede:interpfilter_search into edbc586999d6a1e49e1e35d84a0c8a2c9dcf7990 on xiph:master.


Do not add Nest sensors via discovery

Description:
Currently there is no way to disable the Nest sensors and binary sensors. This is caused by two problems.

Current behaviour is that all the sensors that are available for the Nest devices a user have (thermostat, protect or camera) are added as default when a Nest device is discovered by home-assistant and there is no config for the sensors.
Discovered devices do not use a config so sensors that are added via discovery will not use the configured settings.

This PR changes the Nest sensors so that users have to configure it if they want to use them. Users need to add the sensors to there config. If configured without a monitored_condition list all available sensors will be added, otherwise a list can be specified.
Example entry for configuration.yaml (if applicable):
# example with monitored_conditions list
sensor:
  - platform: nest
    monitored_conditions:
      - 'temperature'
      - 'target

# example without monitored_conditions list
binary_sensor:
  - platform: nest

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

That's not exactly correct. Only sensors that are appropriate to the device are added. There's logic to check the device type, and add only fields it supports. If that isn't happening, it's definitely a bug.

That is what I mean. You indeed only get the sensors for the devices you have. But it is not possible to configure that only specific or no sensors show up for the devices you have. As discussed on Gitter I will change this PR so the code is both user friendly for users that do not want sensors and users that have a Nest protect that only works with sensors.

Somehow I destroyed my branch with a merge. Will make a new PR when i got this worked out.

You should still be able to save your branch, see here
git fetch --all
git rebase updstream/dev


DBZ-1677 Include root cause when PostgreSQL scheam refresh fails when streaming

https://issues.redhat.com/browse/DBZ-1677

Good catch, applied. Thx, @Naros!


C++/Python getTraitProperty consistency.

Closes #57
C++ getTraitProperty method now returns std::optional<T> rather than throwing when invoked without a default parameter. This mirrors the python behaviour of returning None in this case.
Also adds pair of tests to python test suite to add missing checks about traitViews constructed around empty traitsdatas.

Following on from our discussion, didn't spot anything on a squiz through of C_API, CODING_STYLE and CODING_STANDARDS about not using standard library types in an interface because of the c-api.

The first commit [Core] Copy python error mode in getTraitProperty could do with updating with the issue number and getTraitProperty -> getSomeProperty or similar.

@feltech Changed the first commit in a rebase as suggested.


Delete/Drop Function

Have you considered the addition of a delete/remove/drop type function? I've started to use your library and have come across a use case where it would be advantageous to be able to explicitly identify a column to be removed. Currently I would have to get all of the column names, find which index I want to remove, and then generate a series of indexes excluding that one to perform a Select operation.
I am happy to have a first pass at adding this type of function if there is a consensus it would be helpful.

Hello!
This was easy enough to implement and I think is a nice utility function to have.
You can find the implementation on the dev branch, please test it to see if it suits your use cases and let me know.
I called the method Deselect, although probably Drop is a better name. If all is good, you can send a PR with the name change and I will merge it, I'm a bit starved for time lately.
Best,
Alex

Thanks, that seems to do the trick! I'll update the function name at submit a PR shortly.

Have submitted PR #35 to change the function to Drop.

PR merged, thank you!


2 - Drink Submission

As a user, I want to submit drink recipes into a bartender’s dictionary.

This would be a POST route to the database.


Small QA tweaks, make debounce for email check 1 second, remove period for email error

#2365  👈
main

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

Join @nickgraz and the rest of your teammates on  Graphite


One step to add in the Readme

Everything worked here but I could not see the correct QRG in wavelogs "live qso".
Solution:
Hardware Interfaces --> Options "Set default" solved this "small" issue. Maybe helpful for some.
Without "default" (or manually clicking in "station"/"radio") it worked while clicking in bandmap, but not if i put in a qrg manually in the trx.
Anyways thanks for the cool software.

Radio will be saved after 1st QSO.
Process:

Open Live-Logging
Set Radio at Radio-Tab
Do QSO
Log

After that QSO the radio is "pinned" to the chosen one.

Radio will be saved after 1st QSO.

Thank you. Can be added to Readme as well for the next "customer" :-)

Done. tnx fer hint


gh-1349 - added onFailure method to GraphHook

Codecov Report

Merging #1350 into develop will decrease coverage by 0.63%.
The diff coverage is 71.42%.

@@              Coverage Diff              @@
##             develop    #1350      +/-   ##
=============================================
- Coverage       65.3%   64.66%   -0.64%
+ Complexity      1542     1455      -87
=============================================
  Files            694      579     -115
  Lines          22186    18027    -4159
  Branches        2763     2296     -467
=============================================
- Hits           14488    11657    -2831
+ Misses          6566     5425    -1141
+ Partials        1132      945     -187

Impacted Files
Coverage Δ
Complexity Δ

...ava/uk/gov/gchq/gaffer/graph/hook/Log4jLogger.java
42.85% <0%> (-17.15%)
0 <0> (ø)

.../gchq/gaffer/graph/hook/OperationChainLimiter.java
89.47% <0%> (-4.98%)
0 <0> (ø)

...ov/gchq/gaffer/graph/hook/OperationAuthoriser.java
82.6% <0%> (-1.84%)
0 <0> (ø)

...gchq/gaffer/graph/hook/NamedOperationResolver.java
82.75% <0%> (-2.96%)
0 <0> (ø)

.../src/main/java/uk/gov/gchq/gaffer/graph/Graph.java
56.44% <100%> (-0.75%)
0 <0> (ø)

...chq/gaffer/federatedstore/FederatedAccessHook.java
90.62% <100%> (+0.3%)
0 <0> (ø)
:arrow_down:

...v/gchq/gaffer/graph/hook/AddOperationsToChain.java
89.83% <80%> (-1.55%)
0 <0> (ø)

...q/gaffer/accumulostore/SingleUseAccumuloStore.java

...accumulostore/retriever/AccumuloItemRetriever.java

...tore/retriever/impl/AccumuloElementsRetriever.java

... and 114 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 b87db23...0194734. Read the comment docs.


Sync stopped

I've been running polkadot with just a single peer connection, in part to uncover these bugs.
Full trace (-l sync=trace) attached.
synctrace-dead-1.txt
Related #4367

@arkpar one to look into.

Here it looks like GRANDPA service issues a lot of explicit fork sync requests that interfere with normal sync. The fix would be to prioritize normal sync over downloading old forks.


Apply i18n-extract-server and i18n-extract-merge and translate missin…

Summary
Apply i18n-extract-server and i18n-extract-merge and translate missing strings
Ticket Link
None

@levb regarding your comment here: https://github.com/mattermost/mattermost-plugin-apps/pull/273#issuecomment-958155087
The correct make command are make i18n-extract-server and make i18n-merge-server. I fixed it here, and added the missing spanish translations.
@hanzei It would be awesome if we could add these to the ci. I think it would still fail on master, since make i18n-merge-server removes the "line break at the end of the file" that my IDE adds automatically, but that is something that can be solved easily. Nevertheless, I would say it is really low priority.

@hanzei Weird... it seems that I have indeed v2.1.2. When I run i18n-extract-server the only change I get is the line break at the end of the file. What changes are you seeing?

On master:
$ make i18n-extract-server
Please update your assets/i18n/translate.*.json files and execute "make i18n-merge-server"
If you don't want to change any locale file, simply remove the assets/i18n/translate.??.json file before calling "make i18n-merge-server"
If you want to add a new language (for example french), simply run "touch assets/i18n/active.fr.json" and then run the "make i18n-extract-server" again
[sumacheb@jupiter apps]$ git diff
─────────────────────────────────────────────────────────────────────────────────────────────────────────
modified: assets/i18n/active.en.json
─────────────────────────────────────────────────────────────────────────────────────────────────────────
@ assets/i18n/active.en.json:13 @
  "command.debug.kv.clean.hint": "[ App ID ]",
  "command.debug.kv.clean.label": "clean",
  "command.debug.kv.clean.submit": "Deleted {{.Count}} keys for `{{.AppID}}`, namespace `{{.Namespace}}`.",
  "command.debug.kv.create.description": "Create a new key-value for an App.",
  "command.debug.kv.create.hint": "[ AppID keyspec ]",
  "command.debug.kv.create.label": "create",
  "command.debug.kv.description": "View and update apps' KV stores.",
  "command.debug.kv.edit.description": "View or edit specific KV keys of an app.",
  "command.debug.kv.edit.hint": "[ AppID keyspec ]",

Codecov Report

Merging #285 (440a427) into master (898ebe1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #285   +/-   ##
=======================================
  Coverage   25.98%   25.98%
=======================================
  Files          74       74
  Lines        4157     4157
=======================================
  Hits         1080     1080
  Misses       2970     2970
  Partials      107      107

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 898ebe1...440a427. Read the comment docs.


multi-language support - Chinese

I am China，What can I do to support Chinese

Hello, thanks for wanting to help, but for now i don't have a plan to add new language options since I'm still changing a lot of things.


[W-8903763] Support Platform Encryption: Removed SOQL Filters

Critical Changes
Changes
To support Shield Platform Encryption, removed unnecessary SOQL Filters on fields that can be probabilistically encrypted.

disbursementsCreateController_TEST
DatabaseService_TEST

Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Definition of Done to see any additional details for the items below:

[ ] Any net new LWC work has JEST test coverage 50% or above
[ ] Default Sa11y tests pass for all LWC components
[ ] 🔒 Secure both Front-end (LWC) & back-end (Apex) as necessary
[ ] 🔑 Grant users access in Permission Sets (Object, Field, Apex Class) as necessary
[ ] Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name
[ ] Make sure that ACs are updated (if any gaps)
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer

[ ] Pull Request contains draft release notes
[ ] Labels, help text, and customer facing messages are reviewed by Docs
[ ] QE story level testing completed

W-8903763