Remove workaround in crd validator

Courtesy of https://danielmangum.com/posts/how-kubernetes-validates-custom-resources/

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

Test name
Commit
Details
Required
Rerun command

integ-helm-tests_istio
47525bd8ea483cc5c5c0cf7c3342c7a5a801fce5
link
unknown
/test integ-helm-tests_istio

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

/retest


Add gflags dependency to the glog package

The glog package explicitly disables the gflags dependency (https://github.com/ruslo/hunter/blob/master/cmake/projects/glog/hunter.cmake#L34-L35) which means the resulting application cannot take advantage of glog's command line flags (--alsologtostderr, --v=1, etc). These are quite useful in development and testing so I'd like to get the dependency restored if possible.
Happy to submit a pull request if that will help.

Glog should be "hunterized":

https://docs.hunter.sh/en/latest/creating-new/cmake-dependencies.html#maintenance

It means you need to add hunter_add_package(gflags) into the code. Please send pull request to https://github.com/hunter-packages/glog.

Can do. What's the procedure for pointing HunterGate at a development repo/branch for testing? Example: pull gflags from https://github.com/v1bri/gflags.

What's the procedure for pointing HunterGate at a development repo/branch for testing?

Not sure what you mean by this.

Setup Travis and Appveyor to test off your git hunter fork. Then check out the latest pkg. from https://github.com/ingenue/hunter update it with the hunter upstream from  https://github.com/ruslo/hunter. Then modify the the pkg location in the /hunter/cmake//hunter.cmake (and update the sha) to the repo you want to test from. Then check that all in under your hunter fork under the pkg. branch then travis and appveyor should go to work.

Oh and if you were just wanting to test locally on your machine all you need is your hunter fork checked out and then just modify /hunter/cmake/projects/{name}/hunter.cmake (and sha) to point at your repo. So for this case if you are testing glog with a modified gflag then modify
/hunter/cmake/projects/gflags/hunter.cmake
...
hunter_add_version(
    PACKAGE_NAME
    gflags
    VERSION
    2.1.2-p0
    URL
    "https://github.com/hunter-packages/gflags/archive/v2.1.2-p0.tar.gz"
    SHA1
    113255cba87b6af61663014f446e2d69d0d2bc3a
)
...

to
...
hunter_add_version(
    PACKAGE_NAME
    gflags
    VERSION
    2.1.2-p0
    URL
    "https://github.com/v1bri/gflags"
    SHA1
    new sha
)
...

then goto /hunter/examples/glog and run
cmake -H. -B_build
cmake --build _build
and that should test it likely any errors will occur at first cmake call.

It's better to use jenkins.py script:

https://github.com/ruslo/hunter/wiki/dev.hunter.root#jenkinspy

Closing inactive discussion.


Logout on Browser/Window close

How do I automatically sign out when the user closes the browser ? Could you please suggest if we have any configuration changes that would enable this
Thanks

The configuration options are in the README - https://github.com/thoughtbot/clearance#configure
You can experiment with values for cookie_expiration depending what you need there.


any config for change short-cut?

for example, shift mouse over only when i want to create.
and don't auto create other ghost.

Sorry, I'm not sure what you mean?
You can change the hotkey to enable/disable the mod in the controls menu.


improvement of validating arguments

Issue #, if available:
I passed interface { Value(key interface{}) interface{} } to the first argument of the handler.
package main

import (
	"github.com/aws/aws-lambda-go/events"
	"github.com/aws/aws-lambda-go/lambda" // v1.13.3
)

type valuer interface {
	Value(key interface{}) interface{}
}

func handler(ctx valuer, v interface{}) (events.APIGatewayProxyResponse, error) {
	return events.APIGatewayProxyResponse{
		Body:       "Hello",
		StatusCode: 200,
	}, nil
}

func main() {
	lambda.Start(handler)
}

Actual Behavior:
It fails with "handler takes two arguments, but the first is not Context. got interface".
Here is the result of running with SAM CLI.
% curl http://localhost:3000/hello
{"message":"Internal server error"}

% sam local start-api
Mounting HelloWorldFunction at http://<IP_ADDRESS>:3000/hello [GET]
You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions, changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template
2021-03-07 18:19:00  * Running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)
Invoking hello-world (go1.x)
Skip pulling image and use local one: amazon/aws-sam-cli-emulation-image-go1.x:rapid-1.20.0.

Mounting /Users/shogoichinose/tmp/2021-03-07-lambda-context/aws-sam-golang/.aws-sam/build/HelloWorldFunction as /var/task:ro,delegated inside runtime container
START RequestId: 2cdebf6d-a4fa-4e36-bf64-996d10686f29 Version: $LATEST
handler takes two arguments, but the first is not Context. got interface: errorString
null
END RequestId: 2cdebf6d-a4fa-4e36-bf64-996d10686f29
REPORT RequestId: 2cdebf6d-a4fa-4e36-bf64-996d10686f29  Init Duration: 0.27 ms  Duration: 100.46 ms     Billed Duration: 200 ms Memory Size: 128 MB     Max Memory Used: 128 MB
Lambda returned empty body!
Invalid lambda response received: Invalid API Gateway Response Keys: {'errorType', 'errorMessage'} in {'errorMessage': 'handler takes two arguments, but the first is not Context. got interface', 'errorType': 'errorString'}
2021-03-07 18:19:05 <IP_ADDRESS> - - [07/Mar/2021 18:19:05] "GET /hello HTTP/1.1" 502 -

Expected Behavior:
It should be same result as the first argument is context.Context.
package main

import (
	"context"

	"github.com/aws/aws-lambda-go/events"
	"github.com/aws/aws-lambda-go/lambda"
)

func handler(ctx context.Context, v interface{}) (events.APIGatewayProxyResponse, error) {
	return events.APIGatewayProxyResponse{
		Body:       "Hello",
		StatusCode: 200,
	}, nil
}

func main() {
	lambda.Start(handler)
}

% curl http://localhost:3000/hello
Hello

% sam local start-api
Mounting HelloWorldFunction at http://<IP_ADDRESS>:3000/hello [GET]
You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions, changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template
2021-03-07 18:20:01  * Running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)
Invoking hello-world (go1.x)
Skip pulling image and use local one: amazon/aws-sam-cli-emulation-image-go1.x:rapid-1.20.0.

Mounting /Users/shogoichinose/tmp/2021-03-07-lambda-context/aws-sam-golang/.aws-sam/build/HelloWorldFunction as /var/task:ro,delegated inside runtime container
END RequestId: 4827cdf0-3fab-4a19-b352-f3f10977d442
REPORT RequestId: 4827cdf0-3fab-4a19-b352-f3f10977d442  Init Duration: 0.17 ms  Duration: 111.62 ms     Billed Duration: 200 ms Memory Size: 128 MB     Max Memory Used: 128 MB
No Content-Type given. Defaulting to 'application/json'.
2021-03-07 18:20:05 <IP_ADDRESS> - - [07/Mar/2021 18:20:05] "GET /hello HTTP/1.1" 200 -

Another example:
package main

import (
	"context"

	"github.com/aws/aws-lambda-go/events"
	"github.com/aws/aws-lambda-go/lambda"
)

type customContext interface {
	context.Context
	MyCustomMethod()
}

func handler(ctx customContext, v interface{}) (events.APIGatewayProxyResponse, error) {
	return events.APIGatewayProxyResponse{
		Body:       "Hello",
		StatusCode: 200,
	}, nil
}

func main() {
	lambda.Start(handler)
}

It panics with "reflect: Call using *context.valueCtx as type main.customContext".
aws/aws-lambda-go should return an error with more friendly message.
% curl http://localhost:3000/hello
{"message":"Internal server error"}

% sam local start-api
Mounting HelloWorldFunction at http://<IP_ADDRESS>:3000/hello [GET]
You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions, changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template
2021-03-07 18:16:20  * Running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)
Invoking hello-world (go1.x)
Skip pulling image and use local one: amazon/aws-sam-cli-emulation-image-go1.x:rapid-1.20.0.

Mounting /Users/shogoichinose/tmp/2021-03-07-lambda-context/aws-sam-golang/.aws-sam/build/HelloWorldFunction as /var/task:ro,delegated inside runtime container
START RequestId: 0ae34f7a-c15b-45ce-a094-0e5d7800324e Version: $LATEST
reflect: Call using *context.valueCtx as type main.customContext: string
[{"path":"github.com/aws/aws-lambda-go@v1.13.3/lambda/function.go","line":35,"label":"(*Function).Invoke.func1"},{"path":"runtime/panic.go","line":965,"label":"gopanic"},{"path":"reflect/value.go","line":406,"label":"Value.call"},{"path":"reflect/value.go","line":337,"label":"Value.Call"},{"path":"github.com/aws/aws-lambda-go@v1.13.3/lambda/handler.go","line":124,"label":"NewHandler.func1"},{"path":"github.com/aws/aws-lambda-go@v1.13.3/lambda/handler.go","line":24,"label":"lambdaHandler.Invoke"},{"path":"github.com/aws/aws-lambda-go@v1.13.3/lambda/function.go","line":67,"label":"(*Function).Invoke"},{"path":"reflect/value.go","line":476,"label":"Value.call"},{"path":"reflect/value.go","line":337,"label":"Value.Call"},{"path":"net/rpc/server.go","line":377,"label":"(*service).call"},{"path":"runtime/asm_amd64.s","line":1371,"label":"goexit"}]
END RequestId: 0ae34f7a-c15b-45ce-a094-0e5d7800324e
REPORT RequestId: 0ae34f7a-c15b-45ce-a094-0e5d7800324e  Init Duration: 0.18 ms  Duration: 81.29 ms      Billed Duration: 100 ms Memory Size: 128 MB     Max Memory Used: 128 MB
Lambda returned empty body!
Invalid lambda response received: Invalid API Gateway Response Keys: {'errorType', 'errorMessage', 'stackTrace'} in {'errorMessage': 'reflect: Call using *context.valueCtx as type main.customContext', 'errorType': 'string', 'stackTrace': [{'path'<EMAIL_ADDRESS>'line': 35, 'label': '(*Function).Invoke.func1'}, {'path': 'runtime/panic.go', 'line': 965, 'label': 'gopanic'}, {'path': 'reflect/value.go', 'line': 406, 'label': 'Value.call'}, {'path': 'reflect/value.go', 'line': 337, 'label': 'Value.Call'}, {'path'<EMAIL_ADDRESS>'line': 124, 'label': 'NewHandler.func1'}, {'path'<EMAIL_ADDRESS>'line': 24, 'label': 'lambdaHandler.Invoke'}, {'path'<EMAIL_ADDRESS>'line': 67, 'label': '(*Function).Invoke'}, {'path': 'reflect/value.go', 'line': 476, 'label': 'Value.call'}, {'path': 'reflect/value.go', 'line': 337, 'label': 'Value.Call'}, {'path': 'net/rpc/server.go', 'line': 377, 'label': '(*service).call'}, {'path': 'runtime/asm_amd64.s', 'line': 1371, 'label': 'goexit'}]}
2021-03-07 18:16:27 <IP_ADDRESS> - - [07/Mar/2021 18:16:27] "GET /hello HTTP/1.1" 502 -

Description of changes:
The validateArguments validates that the first argument implements context.Context.
It is documented in the official document:

https://docs.aws.amazon.com/lambda/latest/dg/golang-handler.html#golang-handler-structs
The handler may take between 0 and 2 arguments. If there are two arguments, the first argument must implement context.Context.

The validateArguments should validate that the first argument is an interface and a subset of context.Context.

The handler may take between 0 and 2 arguments. If there are two arguments, the first argument must be an interface and a subset of context.Context.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #365 (96bd7dc) into master (6c2af88) will increase coverage by 0.37%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #365      +/-   ##
==========================================
+ Coverage   72.22%   72.59%   +0.37%
==========================================
  Files          19       19
  Lines         738      748      +10
==========================================
+ Hits          533      543      +10
  Misses        138      138
  Partials       67       67

Impacted Files
Coverage Δ

lambda/handler.go
97.33% <100.00%> (+0.41%)
:arrow_up:

Continue to review full report at Codecov.

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

The validateArguments should validate that the first argument is an interface and a subset of context.Context.

Defining a handler to take only a subset of context.Context seems weird to me, can you help me understand why this would be a useful feature?

Actually, I don't have any idea for useful use case of this feature.
But, defining a handler to take only a subset of context.Context comes from the Go language specification.
For example, the handler takes a subset of context.Context, and it works well: https://play.golang.org/p/vPOtIklA3il
package main

import (
	"context"
)

// valuer is a subset of context.Context
type valuer interface {
	Value(key interface{}) interface{}
}

func handler(ctx valuer) {
	return
}

func main() {
	handler(context.TODO())
}

In other hand, the handler takes a superset of context.Context.
It causes a compile error: https://play.golang.org/p/EQ1qAb9zOkJ
package main

import (
	"context"
)

// customContext is a superset of context.Context
// In other words, `customContext` implements `context.Context`.
type customContext interface {
	context.Context
	MyCustomMethod()
}

func handler(ctx customContext) {
	return
}

func main() {
	// compile error:
	// cannot use context.TODO() (type context.Context) as type customContext in argument to handler:
	// context.Context does not implement customContext (missing MyCustomMethod method)
	handler(context.TODO())
}

In this case, the first argument of the handler implements context.Context.
But we can't write handler(context.TODO()).

Note that I'm using the word "subset" as a term of mathematics.

https://en.wikipedia.org/wiki/Subset
In mathematics, a set A is a subset of a set B if all elements of A are also elements of B; B is then a superset of A. It is possible for A and B to be equal; if they are unequal, then A is a proper subset of B.

So, interface{} is a subset of context.Context, and context.Context is also a subset of context.Context.

Codecov Report

Merging #365 (92870ee) into master (5d64132) will increase coverage by 0.37%.
The diff coverage is 100.00%.

:exclamation: Current head 92870ee differs from pull request most recent head 530da2f. Consider uploading reports for the commit 530da2f to get more accurate results

@@            Coverage Diff             @@
##           master     #365      +/-   ##
==========================================
+ Coverage   72.22%   72.59%   +0.37%
==========================================
  Files          19       19
  Lines         738      748      +10
==========================================
+ Hits          533      543      +10
  Misses        138      138
  Partials       67       67

Impacted Files
Coverage Δ

lambda/handler.go
97.33% <100.00%> (+0.41%)
:arrow_up:

Continue to review full report at Codecov.

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

Can we merge this?
Or does someone have some questions?

Hi, any progress?
It is a very rare corner case, however it confuses users. e.g. #377
I'm still waiting for merging this.

I think the size of the changes to resolve https://github.com/aws/aws-lambda-go/issues/377 be reduced, by making the context type check an equality one.

Your example may break compatibility.
e.g. myContext works with current version, because myContext implements context.Context (argumentType.Implements(contextType) is true)
// myContext has same definition with context.Context.
type myContext interface {
	Deadline() (deadline time.Time, ok bool)
	Done() <-chan struct{}
	Err() error
	Value(key any) any
}

func handler(ctx myContext, v interface{}) (events.APIGatewayProxyResponse, error) {
	return events.APIGatewayProxyResponse{
		Body:       "Hello",
		StatusCode: 200,
	}, nil
}

func main() {
	lambda.Start(handler)
}

but after fixing, validation will fail because argumentType == contextType is false. https://go.dev/play/p/Z66z7_GuPZR
package main

import (
	"context"
	"fmt"
	"reflect"
	"time"
)

// myContext has same definition with context.Context.
type myContext interface {
	Deadline() (deadline time.Time, ok bool)
	Done() <-chan struct{}
	Err() error
	Value(key any) any
}

func main() {
	contextType := reflect.TypeOf((*context.Context)(nil)).Elem()
	myContextType := reflect.TypeOf((*myContext)(nil)).Elem()

	// but not equals.
	fmt.Println(contextType == myContextType)
	// Output:
	// false
}

I've just opened a new pull request https://github.com/aws/aws-lambda-go/pull/475.
It is rework of this pull request, but it doesn't accept valuer.

closing since https://github.com/aws/aws-lambda-go/pull/475 was merged


Update cert_sync_detection to use ansible builtin instead shell

Update cert_sync_detection to use ansible builtin instead shell
With shell detection we have some issues:

errors with comm comm: file 2 is not in sorted order
clients with dot in name are not parse correctly
ansible dry-run not working

@kyl191 would it be possible to get a new version of this role published to Ansible Galaxy? I need the fix in this issue but the last published galaxy version is from 2021. Would be much appreciated!


Place Memoria Logo into Folder

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

All checks have passed, however I'm not sure why it is saying not eligible for automerge. This is simply an addition to the asset folder - I added the logo. No deletions or anything changed. Just one logo addition.

Does the Logo URL and the Logo placement into the asset folder need to be done at the same time?


Pull request template

What is the purpose of this Pull Request?
The purpose it have a template for Pull Request to make reviews easier
What was done to achieve this purpose?
I add a PULL_REQUEST_TEMPLATE.md to .github folder.
How to test if it really works?
I don't know how can it be done :(
I think that we should trust on github documentation about it
Who can help reviewing it?
@jtemporal @anaschwendler @cuducos

Would you mind adding a version bump?

Coverage remained the same at 85.667% when pulling 64d35366d1e25b074b47fdec651033f536389691 on lipemorais:pull-request-template into bc316958e3de587d2f72b1f4c0a3ad0bcf9878f5 on datasciencebr:master.

Coverage remained the same at 85.667% when pulling 0be5732f25b7bfde938a98d93f8f6bd49a66ef33 on lipemorais:pull-request-template into bc316958e3de587d2f72b1f4c0a3ad0bcf9878f5 on datasciencebr:master.


add a few languages from the whole config doc to the home page

Description
Add languages that are in the huge documentation file to the homepage
I may leave this PR hanging in case I find other stuff to update in the doc
Type of change

Docs

Checklist

[x] My code follows the style and contributing guidelines of this project.
[ ] I ran Alejandra to format my code. // Not relevant its .adoc
[x] I have performed a self-review of my own code and tested it.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[ ] This change requires a documentation update.
[x] I have updated the documentation accordingly.

Screenshots & Logs
Not Relevant I think

@Vagahbond is this PR ready to be merged, or are there still things you would like to do?

@Vagahbond is this PR ready to be merged, or are there still things you would like to do?

Not yet, so you might as well merge it for now and I'll make another pr later

I forgot it was in WIP sorry :pepega:


build: simplify the build rules (NFC)

The minimum version of CMake is set to 3.19.6.  Remove the workarounds for the older releases of CMake allowing us to simplify the build rules.

@swift-ci please test


pipenv 2020.4.1b1: KeyError: 1 on install

$ pipenv install django-robots
Installing django-robots…
Adding django-robots to Pipfile's [packages]…
✔ Installation Succeeded
Pipfile.lock (b798c1) out of date, updating to (ceb148)…
Locking [dev-packages] dependencies…
Building requirements...
Resolving dependencies...
✔ Success!
Locking [packages] dependencies…
Building requirements...
Resolving dependencies...
✘ Locking Failed!
Traceback (most recent call last):
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 807, in <module>
    main()
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 802, in main
    _main(parsed.pre, parsed.clear, parsed.verbose, parsed.system, parsed.write,
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 785, in _main
    resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages)
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 746, in resolve_packages
    results, resolver = resolve(
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/resolver.py", line 728, in resolve
    return resolve_deps(
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/utils.py", line 1371, in resolve_deps
    results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/utils.py", line 1088, in actually_resolve_deps
    resolver.resolve_constraints()
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/utils.py", line 846, in resolve_constraints
    marker = marker_from_specifier(candidate.requires_python)
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 719, in marker_from_specifier
    for marker_segment in cleanup_pyspecs(spec):
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 259, in cleanup_pyspecs
    specs = normalize_specifier_set(specs)
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 240, in normalize_specifier_set
    return normalize_specifier_set(SpecifierSet(",".join(spec_list)))
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 232, in normalize_specifier_set
    return {_format_pyspec(spec) for spec in specs}
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 232, in <setcomp>
    return {_format_pyspec(spec) for spec in specs}
  File "/home/flimm/.local/lib/python3.8/site-packages/pipenv/vendor/requirementslib/models/markers.py", line 164, in _format_pyspec
    if not next_tuple[1] <= MAX_VERSIONS[next_tuple[0]]:
KeyError: 1

I'm on Ubuntu 20.04. If I downgrade to an older version of pipenv, I do not experience this issue.

thanks for the report! This one at least I can test myself easily!
are you using the system install of python? how did you install pipenv?

I installed pipenv by running:
pip install --upgrade --pre pipenv

I'm using system Python 3.8.
$ which pipenv
/home/flimm/.local/bin/pipenv
$ which python3
/usr/bin/python3
$ which python
/usr/bin/python

My .bashrc adds ~/.local/bin to PATH.

I can reproduce here. The root cause is django-robots has a casual python-requires value >1.1.1 and our specifier parser doesn't handle that.


Fixes the modal from force-turning the device to portrait

Fixes https://github.com/mmazzarolo/react-native-modal-datetime-picker/issues/20
Overview

Test Plan

@SudoPlz I created #416 , so that you can pass your own orientations 👍 Thanks for the PR btw!

Sounds good, thanks @mmazzarolo


After one player finishes the intro steps, the lobby should display, before the other players finish

Using an unmanagedGame in empirica means that the lobby doesn't display (except for a brief moment between game creation and game status assignment, see: here ), so we need to render it explicitly.
Do this by checking whether the player has been assigned to a game, and then if they have not (but are done with the intro steps) then display the lobby.

complete in https://github.com/Watts-Lab/deliberation-empirica/pull/569


Use the right appName on init

local-cli was getting the appName from process.argv instead of using appName parameter.

Assigning to @foghina to take a look.

This is not correct, process.argv can contain useful args for the generator (e.g. --skip-ios). This drops those arguments. You could do something like:
var args = [appName].concat(process.argv.slice(4));

But please make sure command line arguments get passed down to the generator.

BTW, are you running into any specific issues due to this particular behavior?

You are right, @foghina. I didn't think about the other arguments.
I'll update the PR with your changes. Anyway, I'm not sure if this is the best option; since the dependency on process.argv is still there, maybe it's just better to remove the read appName from them and remove the appName argument from init.
I found the issue while trying to create a new project programmatically from the repl (probably an unsupported scenario anyway).

For this we could push the arguments list up. I.e. we can make init() take an args parameter and just pass process.argv from cli.js, so that others can more easily invoke init() without requiring a specific process.argv.

Since local-cli/cli.js is just exporting the required func "as is", I think react-native-cli/index.js could be a better place to handle command line args: https://github.com/facebook/react-native/blob/373c8777f6bad3a935089bd4c59bf2e15896de63/react-native-cli/index.js#L149
It already depends on process.argv anyway, so it doesn't require an extra dependency.

Sounds like a plan! Can you update your PR?

Done.

Thanks!


Creates RUN_SOLID_QUEUE_IN_PUMA env var

Set RUN_SOLID_QUEUE_IN_PUMA to any value to cause solid queue to run within puma. In render.yaml, the default is to enable the in-puma queue worker.
This is helpful in settings where puma load is low, and running a dedicated worker is unnecessary.
fixes #63

I'm going to go ahead and merge this in so I can try a new deploy to render


How does a user fix a bad Application input? A bad "path" for example

While troubleshooting a wego app with a user, it wasn't immediately obvious how someone could remediate an invalid Application CR parameter. In this case, it was the path parameter that needed to be changed.
The remediation step that was actually taken: wego app remove my-app, then re-added the app.

Decision: alloow the user to re-run app add with different inputs in order to remediate bad user input.

We should push a new commit with the changes to that same branch

@jpellizzari
I have some questions about this task I want to get clarification on.

Does this only have to do with the auto-merge=false path?
If so is the scope of this issue only if the pr has not been merged yet?

Does this only have to do with the auto-merge=false path?

That was NOT the original intent, but I see how that could be tricky.
@J-Thompson12  Can you do some investigating and find out if it would be easier to start with --automerge=false for updates, or if it would be easier to just do the same things no matter if its automerge or not?

Situations:

PR is open
Auto-merged already

The new directory structure may make this work easier. Moving to Icebox for now.


Adding Images to Bars in Race

These are some of the changes I included to be able to add images to the bars as they move (check gif in README.md file).
I am creating a pull request so that other people can take a look.
Right now it is not very generalizable and things could move much faster with someone who actually knows how Matplotlib works.
The only changes with respect to the original project are in _bar_chart_race.py and in the README.md file to explain my goal. I included 3 additional parameters to the initializer class plus a docstring at the end.

Well done, do you intend to update the tutorial.md file and describe how to add the images to the bars?

I totally forgot about that document. I will include a description of how to use the new parameters. There is still a lot of work to do to get it working for all cases.

I created a YouTube video about a bar chart race I made using this package and the modification. The end of the video is mainly showing the code, in case someone wants to collaborate and wants to see what I did (more specific code part is around minute 5 or 6, but look at the timestamps):
https://youtu.be/9hqGRehzEsI

I created a YouTube video about a bar chart race I made using this package and the modification. The end of the video is mainly showing the code, in case someone wants to collaborate and wants to see what I did (more specific code part is around minute 5 or 6, but look at the timestamps):
https://youtu.be/9hqGRehzEsI

Embedded link go to local host!?

I created a YouTube video about a bar chart race I made using this package and the modification. The end of the video is mainly showing the code, in case someone wants to collaborate and wants to see what I did (more specific code part is around minute 5 or 6, but look at the timestamps):
https://youtu.be/9hqGRehzEsI

Embedded link go to local host!?

Sorry, I messed up the order of the hyperlink in mark down in the first try, but it is fixed now.


Issue-229: Support Proxies in Docker Daemon

Closes #229 (for RHEL systems)
Added initial support for Docker daemon using a proxy on RHEL systems. I will add Ubuntu in the future, but currently short on time to do so. If the proxy vars are set in all.yml and the system is a RHEL system, the http-proxy.conf file is created in a Docker systemd directory and the daemon is reloaded and restarted. This has worked as expected in my environment for doing docker pulls from docker.io and quay.io through a proxy.

Hello,
I think this change can be applied to other OS's too.
Juste one condition would be necessary :
when: ansible_service_mgr == "systemd"

I'm going to do the test on debian in order to confirm

Good call, yeah, that will probably work out better. I'll make the change this morning.

Confirmed works on CentOS. Should be ready for merge if your Debian testing bypasses this, @Smana.

Another comment, is there a reason why you didn't make use of handlers ?
I think we should replace the following lines:
- name: reload systemctl daemons
  shell: systemctl daemon-reload
  when: systemddockerproxy.changed

- name: restart docker so configs are applies
  service: name=docker state=restarted
  when: systemddockerproxy.changed

with a handler file roles/docker/handlers/main.yml
---
- name: restart docker
  command: /bin/true
  notify:
    - reload systemd
    - reload docker

- name : reload systemd
  shell: systemctl daemon-reload
  when: ansible_service_mgr == "systemd"

- name: reload docker
  service:
    name: docker
    state: restarted

and a notify there
- name: drop docker environment conf to enable proxy usage
  template:
    src: http-proxy.conf.j2
    dest: /etc/systemd/system/docker.service.d/http-proxy.conf
  notify: restart docker

Updated and confirmed working. Thanks for the help on how to use handlers!


Authorization

Implement semi "authorization" to enter the main web page with a questionnaire.

I assume you actually want to merge these changes with the master branch, not leo-development? Though it seems most of these changes were included in your most recent pull request for master. So maybe delete this request?

I assume you actually want to merge these changes with the master branch, not leo-development? Though it seems most of these changes were included in your most recent pull request for master. So maybe delete this request?

Yes you're right, this is one of the branches I've been reorganizing into another to properly pull request into the master. I'll delete the request


HTTP client switching

Currently, we use got-scraping for making HTTP calls, but that is getting outdated as we speak. We need to find a way to allow using different HTTP clients, like curl-impersonate or axios.

The interface should mimic that of got-scraping for BC reasons, with features not supported by https://github.com/apify-projects/node-curl-impersonate/tree/master omitted. Index signatures will be used to keep compatibility with eccentric usage of got-scraping.

We will most likely do that later this year, but the support for doing this "somehow" should be done during Q3, so let's try to make it work now on runtime at the cost of not perfect typing, and improve in v4 where we can afford breaking stuff.


[qt5-webengine] Work around mixed abseil-cpp issue

On MS Windows qt5-webengine fails to build if it picks up abseil-cpp headers from vcpkg instead of its own abseil-cpp headers. This is exactly the same problem as was dealt with in commit 484762d429e3 for protobuf.
Fixes #39528

[x] Changes comply with the maintainer guide.
[ ] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Should these ci.baseline.txt skips be removed?
https://github.com/microsoft/vcpkg/blob/d723b88bd690d5a00b0160c182ddd1dbd61071df/scripts/ci.baseline.txt#L964-L970

Yes.
@tsondergaard Could you please remove below records from the vcpkg\scripts\ci.baseline.txt file(line 964~970)? Thank you!
# Missing prerequisites for CI success
# Fail due to outdated protoc headers.
# D:\buildtrees\qt5-webengine\x64-windows-dbg\src\core\debug\gen\net/third_party/quiche/src/quic/core/proto/cached_network_parameters.pb.h(17):
# fatal error C1189: #error:  This file was generated by an older version of protoc which is
# Succesful built requires protobuf to be installed after qt5-webengine not before. Otherwise the build picks up the wrong headers from inside vcpkg.
qt5-webengine:x64-windows=skip
qt5-webengine:x86-windows=skip

I waitting the merge done to test quickly the Qt5-WebEngine build on my host computer....

/azp run

I waitting the merge done to test quickly the Qt5-WebEngine build on my host computer....

I built it locally myself when I pushed cb2386335234bb29f19dc73cfea4729270cef9a4
I restarted the build because arm64_windows died due to an infrastructure issue

I applied the patch locally from the tsondergaard branch, and it pass here:
Computing installation plan...
The following packages will be built and installed:
<EMAIL_ADDRESS>Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe
Installing 1/1<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- qt5-webengine requires a lot of free disk space (>100GB), ram (>8 GB) and time (>2h per configuration) to be successfully build.
-- As such qt5-webengine is currently experimental.
-- If qt5-webengine fails post build validation please try manually reducing VCPKG_MAX_CONCURRENCY and open up an issue if it still cannot build.
-- If it fails due to post validation the successfully installed files can be found in C:/vcpkg/packages/qt5-webengine_x64-windows
-- and just need to be copied into E:/dk/x64-windows
-- Found external ninja('1.11.0').
-- Using cached qtwebengine-everywhere-opensource-src-5.15.14.tar.xz.
-- Extracting source E:/d/qtwebengine-everywhere-opensource-src-5.15.14.tar.xz
-- Applying patch common.pri.patch
-- Applying patch gl.patch
-- Applying patch build_1.patch
-- Applying patch build_2.patch
-- Applying patch 0001-Support-ICU-74-in-LazyTextBreakIterator.patch
-- Applying patch workaround-protobuf-issue.patch
-- Applying patch 0001-Fix-jumbo-build-error-due-to-ResolveColor-redefiniti.patch
-- Using source at E:/b/qt5-webengine/src/5.15.14-90a5fb30b8.clean
-- Getting CMake variables for x64-windows
-- Using cached msys2-mingw-w64-x86_64-pkgconf-1~2.2.0-1-any.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.5.3-3-x86_64.pkg.tar.zst.
-- Using msys root at E:/d/tools/msys2/1e74ca60daa10104
-- Configuring x64-windows-rel
-- Configuring x64-windows-rel done
-- Configuring x64-windows-dbg
-- Configuring x64-windows-dbg done
-- Package build-x64-windows-dbg
-- Package build-x64-windows-rel
Gilles Caulier

Thanks for the fix!


http adapter -rootPath option

Add a -rootPath option to read http that can specify a path into the retrieved object from which the points should be processed.
Fixes #146.

@mstemm

Other than the above question, which won't really affect this code, lgtm.

Looks good. +1


Allow deprecating k8s versions

What this PR does / why we need it: This PR allows removing support for k8s versions (by setting the "supported" value to false in the version map) and keep support for scaling/upgrading those clusters
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #3399
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

Tests running on  https://github.com/CecileRobertMichon/acs-engine/compare/k8s-versions-distinct...CecileRobertMichon:test-deprecate-versions  (disables all versions expect [1.8.15 1.9.9 1.10.5 1.11.0])
Deploy a deprecated version (expected to fail): https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-deployment/206/console
Upgrade a cluster deployed with a now deprecated version: https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-upgrade/128/console

TODO:

Only validate version that we are upgrading to in upgrade (not the version we are upgrading from)

Only allow upgrade for versions currently supported (allow list for create and upgrade is identical)

Fix the orchestrators command to reflect the above

upgrade: https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-upgrade/145/console
scale: https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-scale/46/console

/lgtm


not able to import functions - brotli() and and Struct Certificate

Rust-analyzer is just fine with this, but trunk cannot find the imports at compile.
Hope I'm not missing something?
reqwest = { version = "0.11.18", features = ["json", "brotli", "rustls-tls"] }

use reqwest::{StatusCode, ClientBuilder, Certificate};

let cert = Certificate::from_pem(&buf).unwrap();
    let client = ClientBuilder::new()
        .brotli(true)
        .add_root_certificate(cert)
        .build()
        .unwrap();

I'm not sure what the issue could be. That's how to enable the features... Is there anything special about your build environment?

It works in plain-vanilla non-builder mode i.e. if I don't use brotli and add_root_certificate and just do a Client::new().
Not sure how to use these functions.

If you create a completely separate project and try it, does it work?
It works in our CI and most other people's projects. So I wonder if you use a different build tool, or have some patch in your Cargo.toml, or something in .cargo/config, or anything.

made it work. Thank you.


ARROW-10863: [Python] Fix pandas skip in ExtensionArray.to_pandas test

@github-actions crossbow submit -g integration wheel

@github-actions crossbow submit -g wheel

@github-actions crossbow submit -g integration

@jorisvandenbossche Are you happy with the build results? If so, will merge.

Hmm, the pandas master/nightly builds are failing, and it is in tests that I touched, it seems unrelated (just by accident that a recent change in pandas master also impacted those tests). It seems that the pytest monkeypatching functionality cannot handle inherited methods.
Will take a look at that tomorrow.


MongoDB 3 repositories for Debian/Ubuntu/RedHat-centOS-OLinux/AmazonLinux

@Poil squash here too please. Thanks.

+1

Works perfectly, thanks


debug rstudio selenium test

CLOSE PR: changes in this branch have been merged to refractor_buildtest and would be merged to main later


⚠ Bofrost.de has degraded performance

In dbe05e1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1931 ms

Resolved: Bofrost.de performance has improved in f1fd671 after 14 minutes.


ScrollView

Does anyone have a sample for scrollview ?

<StackLayout>
  <ScrollView>
    ... anything ...
  </ScrollView>
</StackLayout>

In the future you may want to ask this question on the {N} slack channel:
https://t.co/uExEluDrmO
And please just keep this in mind:
https://github.com/NativeScript/codeofconduct

This is also a great example repo you can try:
https://github.com/NativeScript/sample-Groceries

This is also a specific {N} + ng2 repo you can try:
https://github.com/NathanWalker/angular2-seed-advanced
Instructions to run the NativeScript app:
https://github.com/NathanWalker/angular2-seed-advanced#run-nativescript-app

Another sample repo:
https://github.com/NativeScript/sample-ng-todomvc

@NathanWalker
I tried to get ScrollView working in TabView but not successful.  Do you have any idea?


Create fun-random-api.json

Requirements completed
Description

I made a express site for host discord fun api.
Link to Website

https://fbf6f1ec-874e-4ec5-b02e-c4cfdbaa148d.id.repl.co/

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

Closed for inactivity.


Add quick start documentation page

@Tabrizian: Instead of having a new page, do you think we can embed this in the Perf Analyzer readme? https://github.com/triton-inference-server/client/blob/main/src/c++/perf_analyzer/README.md#performance-analyzer

Moved to main PA readme 👍


[stable/fluent-bit] upgrade to fluent-bit v1.1.3

https://fluentbit.io/announcements/v1.1.3/

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

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

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

Added another commit to switch URLs in Chart.yaml to https.. because, security ;-)

/ok-to-test

/lgtm


Request file

There is no requirements.txt file. Please upload file requirements.txt.

Hi @ma893460966! Have you managed to figure out the requirements and would like to share them? Thanks

I don't do research in this area anymore, so I didn't explore it further, but good luck!


Set a fixed font  for the accessibility labels

Currently, the accessibility labels are generated using system fonts.
Since our local environment is on a mac and the CI pipeline runs on a linux container, the accessibility labels have different fonts.
Suggestions: Maybe make the font custimizable

Thank you for your feedback.
We are specifying the font, but it might not be installed on some operating systems. Is the new image a Linux image?
We might need to look for a font that is installed on both operating systems.
https://github.com/takahirom/roborazzi/blob/0b0143ea4d4f1c3c2ab307db27e57d0a505f040a/roborazzi-painter/src/commonJvmMain/kotlin/com/github/takahirom/roborazzi/AwtRoboCanvas.kt#L592-L593
https://github.com/takahirom/roborazzi/blob/0b0143ea4d4f1c3c2ab307db27e57d0a505f040a/roborazzi-painter/src/commonJvmMain/kotlin/com/github/takahirom/roborazzi/AwtRoboCanvas.kt#L182

Yes, it is a linux image :)
Using a font installed in both systems would definitely work!

@takahirom
Any plans on how we want to tackle this?
I can gladly help as well 😊

@sergio-sastre
Thank you for raising your hand!
We may need to determine which font works best for the label.
While Java provides some fonts, they are actually mapped to specific fonts by the JDK implementation. However, we prefer not to bundle a font. Could we perhaps use Android fonts or something similar in Robolectric? 💭
https://docs.oracle.com/javase/8/docs/api/java/awt/Font.html?utm_source=chatgpt.com

Logical fonts are the five font families defined by the Java platform which must be supported by any Java runtime environment: Serif, SansSerif, Monospaced, Dialog, and DialogInput. These logical fonts are not actual font libraries. Instead, the logical font names are mapped to physical fonts by the Java runtime environment. The mapping is implementation and usually locale dependent, so the look and the metrics provided by them vary. Typically, each logical font name maps to several physical fonts in order to cover a large range of characters

But if it works and we don't have to bundle font files, I don't have any particular opinion.

I'll take a look at it in a couple of weeks, I'm afraid it is not gonna be possible before


[Map][Google] Add documentation about ux_map.google_maps.default_map_id

Q
A

Bug fix?
no

New feature?
no

Issues
Fix #...

License
MIT

I've just tilted that I've missed to document the new feature introduced in #2350 for #2306

Did you update the google mpas recipe ?

Did you update the google mpas recipe ?

Opened https://github.com/symfony/recipes/pull/1354

When you will install UX Google Map 2.22 for the first time (or update the recipe) ✨

This is really nice! 👏


update railties dependency

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   96.55%   96.55%
=======================================
  Files          24       24
  Lines         872      872
=======================================
  Hits          842      842
  Misses         30       30

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 c71c391...7ff454e. Read the comment docs.

also update activesupport dependency
:mag_right: Click to see changes since last update.


Create a basic Result of the quiz

Edit this file

This components are good for this task
https://daisyui.com/components/stat

Ok I'll work on it 👍

Ok I'll work on it 👍

If this component needs more information about the result let me know which are those

Items required for the ScoreBoard:

number of questions answered correctly, incorrectly, skipped
positive score, negative score, grand total score
avg score (iff med pde toh baaki vandho nthi)
and if difficulty is enabled:
- number of questions answered correctly : easy, medium, hard
- number of questions answered incorrectly : easy, medium, hard
- number of questions skipped : easy, medium, hard

i guess aatli info on the score board is sufficient for now....

can we have it like easyCorrectQuestions,etc...

this one done....


Add from_reader and to_writer methods

These match what other serde serialisers offer.
This PR is mostly a rebase of https://github.com/alexcrichton/toml-rs/pull/257, with just one extra commit.

Could these methods perhaps return a new error enum instead of fitting an Arc and io::Error into the existing one?

Done. That was actually much simpler than I'd anticipated.

Updated. I'm not sure I'm convinced of the multiple layers of errors being returned though, I think adding the Io entry was simpler to deal with.

toml-rs has moved to https://github.com/toml-rs/toml_edit.  Feel free to rebase your PR against that repo and open a new issue there.


Notifications (recreated)

I have done all the following:

[x] added the feature
[x] added documentation for the feature
[x] added tests for the feature
[x] ran mypy, black, and unit tests

I've added a new feature, the notifications !
notifs = client.notifications()
for notif in notifs:
    print(f"Part: {notif.part}")
    print(f"Ident: {notif.ident}")
    print(f"Number: {client.notification_number}")
    for n in notif.notifications:
        print(f"Id: {n.id}")
        print(f"Type: {n.type}")
        print(f"Message: {n.message}")
        print(f"Action: {n.action}")

Returns for me:
Part: Communication
Ident: secMessagerie
Number: 1
Id: Discussions
Type: 2
Message: Discussions
Action: 2

@bain3

@bain3 pas de news sur la feature ?

@bain3


Always update context's issuedAt

Fixes #111 .
This PR also logs whenever there is an issuedAt mismatch, i.e. user clicks outdated buttons

Pull Request Test Coverage Report for Build 386

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

Totals

Change from base Build 378:
0.0%

Covered Lines:
167

Relevant Lines:
182

💛  - Coveralls


W-14764289-add-limit-property-43-dm

Closing this PR as the runtime team confirmed that the memory bursting may bring issues. The parameter won't be included.


[UI Uploader] Not tall enough when uploading multiple documents

Feedback on reddit
UI Uploader - When clicking "Details", it shows a list that isn't tall enough to display all documents, and doesn't scroll.
The details list also disappears when a new document in the list is processed if you're uploading a lot of them (my test-folder with 40 documents)

Obsolete. UI uploader was removed from 2.1.


Change default import path to Assets/RealityToolkit

This error is being reported by the Mac host, has something changed/been updated with the build tools

Packages/com.realitycollective.buildtools/Editor/AssemblyInfo.cs(6,28): error CS7034: The specified version string does not conform to the required format - major[.minor[.build[.revision]]]


prompt_async is blocking on windows

Consider the following:
import asyncio

from prompt_toolkit.shortcuts import prompt_async

async def spam():
    while True:
        print("hello");
        await asyncio.sleep(0.1);
        print("World");
        await asyncio.sleep(0.1);

async def my_coroutine():
    while True:
        result = await prompt_async('Say something: ', patch_stdout=True)
        print('You said: %s' % result)

loop = asyncio.get_event_loop()
loop.run_until_complete(asyncio.gather(my_coroutine(), spam()))
loop.close()

What I expect to happen: The prompt is pushed down by a continual stream of Hello and World
What actually happens: Each time I push a single character, an extra Hello or World is printed - the output does not advance while waiting for a single character.

Hi @eric-wieser,
Thank you for reporting! I think this is a windows-only issue. The way that stdin is read blocks the event loop. If I recall correctly, this was fixed on the 2.0 branch. Could you check that out. I believe that the code above is compatible with 2.0. (However, it'll still take some time for 2.0 to release.)
Thanks,
Jonathan

Installing the 2.0 branch gives the following error:
Traceback (most recent call last):
  File "main.py", line 20, in <module>
    loop.run_until_complete(asyncio.gather(my_coroutine(), spam()))
  File "C:\Program Files\Python 3.5\lib\asyncio\base_events.py", line 342, in run_until_complete
    return future.result()
  File "C:\Program Files\Python 3.5\lib\asyncio\futures.py", line 274, in result
    raise self._exception
  File "C:\Program Files\Python 3.5\lib\asyncio\tasks.py", line 239, in _step
    result = coro.send(value)
  File "main.py", line 16, in my_coroutine
    result = await prompt_async('Say something: ')
  File "<string>", line 6, in prompt_async
NameError: name 'create_asyncio_event_loop' is not defined

eventloop.utils.AsyncioTimeout is also missing, even though 'AsyncioTimeout' in eventloop.utils.all`.
Are there no automated tests on the 2.0 branch to catch these things?

Hi @eric-wieser,
Can you check whether this is still the case with the 2.0.1 release?
If not, I can close this issue.
Thanks!

Tested this with the modernized version of the initial case:
import asyncio
from prompt_toolkit import PromptSession
from prompt_toolkit.patch_stdout import patch_stdout

async def spam():
    while True:
        print("hello");
        await asyncio.sleep(0.1);
        print("World");
        await asyncio.sleep(0.1);

async def my_coroutine():
    session = PromptSession()
    while True:
        with patch_stdout():
            result = await session.prompt_async('Say something: ')
        print('You said: %s' % result)

loop = asyncio.get_event_loop()
loop.run_until_complete(asyncio.gather(my_coroutine(), spam()))
loop.close()

Seems to be working as expected (prompt line is continuously pushed down even when typing).


Error When Like Media

I got response StatusCodeError: 302, when using method like
reference: https://github.com/jlobos/instagram-web-api#likeparams

I tried and everything works perfectly. Can you provide more details please ?

I tried and everything works perfectly. Can you provide more details please ?


Track tech debt

Parent issue to track tech debt

[ ] OTelSpanBuilder.addLink(SpanContext, Attributes) ignores attributes (with a warning)
[ ]

We'll stay with individual issues labelled with technical-debt


"There is no funtion named 'Shader_GetBitDepth'

Hello there!
Many thanks for the new release <IP_ADDRESS> Stable!
Starting this Version, I'm getting the above mentioned error, i.e. "There is no function named 'Shader_GetBitDepth' when using SuperResXBR(Passes=5, Factor=4). (See Screenshot).
What is causing this problem?
Many thanks for your help!
Onbekend

I'm sorry, I can't upload the screenshot. It says "Something went really wrong, and we can't process that file. Try again."

Import("C:\Other Apps\Staxrip_<IP_ADDRESS>_x64_stable_local\Apps\Plugins\AVS\NNEDI3\edi_rpow2.avsi")
LoadPlugin("C:\Other Apps\DGDecNV_2<IP_ADDRESS>\x64 Binaries\DGDecodeNV.dll")
LoadPlugin("C:\Other Apps\Staxrip_<IP_ADDRESS>_x64_stable_local\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
Import("C:\Other Apps\Staxrip_<IP_ADDRESS>_x64_stable_local\Apps\Plugins\AVS\Shader\Shader.avsi")
DGSource("D:\StaxRip_Temp\Destination Wedding (2018)\Destination Wedding (2018).dgi", i420 = true)
ConvertBits(16)
Crop(0, 140, -0, -140)
SuperResXBR(Passes=5, Factor=4)
Spline64ResizeMT(1920, 800, prefetch = 4)
ConvertBits(10)

The shader dll has not been loaded in your script, It's why your getting the error. I'll take a look why it's not autoloading.
FYI, you can do resizing with SuperRes. Spline isn't really needed when SuperRes is used.
If your going to convert to 16bits you might as well use Dither_resize16. Which will covert the depth to 8Bits & resize with one function.
It might help speed up your encoding.

Update It was trying to load the avsi file twice and ignore the dll.
The Source code has been updated with the changes.

Many thanks for the quick response!
Fantastic!
:-)
And thanks for the tips!


Second Time All Button Mapping has been lost

This is the second time since the plugin was released that all button mapping has been lost.
This time I noticed that all remotes were missing from HomeKit. When they showed up again, the mapping was gone.

Any chance you were able to retain the logs across restarts?

Also, which version(s) are/were you running?

Version 2.4.2. Not sure how to check the logs.


Added ability to control output details

We have a large number of features and specs so the output can get a little overwhelming.
Output control has been added in 2 config options outputDetails and outputSummary;
outputDetails
Specify which categories to show in the details output eg --outputDetails="failed,pending" will hide anything that is passing.
outputSummary
Display a summary at the end of the process to get some statistics across all test sources.

Thanks! Good stuff. Will get this merged in and released as soon as I scramble back my write access.


Add traditional chinese support

Hi,
I know there is Chinese Simplified version but still some terms different from Chinese Traditional,
so I've translated this awesome style guide to Chinese Traditional (zh-Hant-TW).
Could you add the link?

Thanks for the contribution!


Preview fails to render link with target=_blank

The following syntax fails to render properly in VSC preview:
If your password is managed by [!DNL Adobe], you can [change the password in your Adobe account](https://helpx.adobe.com/manage-account/using/change-or-reset-password.html){target="_blank"}.

The content renders properly when rendered:
https://experienceleague.adobe.com/docs/data-workbench/using/hidden-test-page.html#preview-issue

Confirmed that this is fixed in 2.1.3


Is there's any good tuturial that shows how to add plugins and configure previous ones please, I'm new here :)

There's a good section in the docs about this (see here). Also if you just open up packages.fnl there's example code commented out that shows you how how to do it.


Important! broken since version 2.2.2

see https://github.com/joepie91/python-whois/issues/151

Confirming that version 2.4.3 throws "bad escape \s" with python 3.7 while version 2.2.2 works


Reports don't update state until you click into them.

This is a platform-wide issue coming from the back end, as it happens equally to messages, but whatever the case we've got to solve it. More internal discussion happening in Slack.
Reproduction steps:

Sign into any account
Make sure your account have several workspace users with reports outstanding
Additionally, make sure that each individual has submitted reports previously, and these have been reimbursed.
Click into the workspace chat

Actual result: The reports don’t correctly reflect their state until you click into them – whether the report has been paid, or is still outstanding and needs to be paid.
Expected result: Reports show their correct state whether or not you click into them.

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0118840394603d0ff0
Upwork Job ID:<PHONE_NUMBER>628341760
Last Price Increase: 2023-07-27

Did some investigation. It seems that when we open the App the iou reports are not fetched from the backend anymore, and the report preview action in the chat doesn't contain all the info needed here to properly build the report preview text. I'll open a discussion in Slack about the solution that I am thinking about, to make sure I don't break other things.

We haven't concluded the Slack convo yet

Our best hunch is that this is the same root cause as fetching IOU/expense reports, an initiative already being worked on. We'll keep this issue open until we confirm that's the case, though also moving this to weekly in the meantime.

Still holding on #278883

Closing this one, as it's now resolved since we started fetching iou/expense reports.


rTorrent purge action

Motivation for changes:
rTorrent currently supports adding, updating, and removing a torrent from rTorrent. However, it does not support removing the torrent and the torrent data. This PR adds the ability to specify a purge action for the rTorrent plugin that will both remove the torrent data and remove the torrent from rTorrent
Detailed changes:

RTorrent class

Add purge_torrent method

'RTorrentOutputPlugin' class

Update the action schema enumeration to include purge
Add a purge action handler to the on_task_output method
Add a purge_entry method for the purge action handler to call that handles the call to the RTorrent class' purge_torrent method

Add tests for the rTorrent purge functionality

Config usage if relevant (new plugin or updated schema):
tasks:
   rtorrent_purge:
    from_rtorrent:
      uri: scgi://localhost:5000
    accept_all: yes
    rtorrent:
      uri: scgi://localhost:5000
      action: 'purge'

Log and/or tests output (preferably both):
2023-08-03 16:07:29 VERBOSE  details       rtd             Produced 2 entries.
2023-08-03 16:07:29 VERBOSE  task          rtd             ACCEPTED: `ubuntu-23.04-live-server-amd64.iso` by if plugin because matched requirement: custom1 == 'ubuntu'
2023-08-03 16:07:29 VERBOSE  task          rtd             ACCEPTED: `ubuntu-23.04-desktop-amd64.iso` by if plugin because matched requirement: custom1 == 'ubuntu'
2023-08-03 16:07:29 VERBOSE  details       rtd             Summary - Accepted: 2 (Rejected: 0 Undecided: 0 Failed: 0)
2023-08-03 16:07:30 VERBOSE  rtorrent      rtd             Purged ubuntu-23.04-live-server-amd64.iso (D6B4535BA8F2B34012BC633569F113E77017E032) in rtorrent
2023-08-03 16:07:30 VERBOSE  rtorrent      rtd             Purged ubuntu-23.04-desktop-amd64.iso (443C7602B4FDE83D1154D6D9DA48808418B181B6) in rtorrent

@gazpachoking Noticed the functionality to remove a torrent and its associated data was not available for rTorrent when I was doing my other PR... so just knocked this out real quick as well!

Seems great, thanks again!

No problem, happy to contribute! I've updated the wiki as well


git: Add support for adding tag info to commit

Add a new struct Tag that represents a Git annotated tag and add it as a new field Commit.ReferencingTag, allowing for a commit to contain information about its referencing tag. Add support for verifying the referencing tag as well.
Update the cloning logic to include the tag object in the returned commit object when checking out via a specific tag, a semver range or if the provided refname points to a tag.
Related to: https://github.com/fluxcd/source-controller/issues/1133
Example usage: https://github.com/fluxcd/source-controller/pull/1187

Is this part of https://github.com/fluxcd/source-controller/issues/1133? if so please add it to the PR description.

wondering whether we should also add support for verifying tags if .spec.ref.name points to a tag?

If we can automagically resolve this, it would probably be good for feature completeness.

Failing BitBucket Server test is due to TLS issues on the upstream server and not related to these changes.


Core20: VDPAU broken on AMD GPUs

I noticed in my testing that Moonlight seems to be unable to find the VDPAU driver on Core20 with an AMD GPU. The Core18-based Snap seems to work fine.
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory

The problem seems to be the following lines in va-wrapper:
elif [[ $VENDOR == *"X.Org"* ]]; then
  export VDPAU_DRIVER_PATH="/usr/lib/$ARCH/vdpau/"
fi

I'm not sure what that was intending to do. I don't think that path would ever be accessible from within a strictly confined Snap. The correct path is $SNAP/usr/lib/$ARCH/vdpau which is what would be used if the above code was not present at all.
The Core18 Snap fails with the VDPAU_DRIVER_PATH value, then succeeds with $SNAP/usr/lib/$ARCH/vdpau (no clue where it's getting that path)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau//libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/870/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = 21

The Core20 Snap tries VDPAU_DRIVER_PATH value then a bunch of different library paths before failing:
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau//libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/lib/gl/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/lib/gl32/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/void/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/lib/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/lib/x86_64-linux-gnu/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/dri/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/pulseaudio/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

Is it safe to simply remove those lines in va-wrapper? Presumably they were there for some reason...
glxinfo.txt

Hm, this wrapper script was copy/pasted from somewhere else long ago; and that line doesn't really make much sense now. This should be fixed by https://github.com/maxiberta/moonlight-snap/commit/06e2607abeaa0242ce026bd8ba4da2a995924767, on edge. Please let me know if it works for you. Thanks!

Confirmed fixed, thanks.


Bypass on AzDo build; Test before delete

Incorporated the check for presense of tslint.json before deleting it.
For the other fix submitted here:
https://github.com/Voitanos/eslint-preset-spfx-react/pull/4/commits/6ccb07c239414c9d13640c6ce83d0a35fffe9599#diff-4f6f6e58aa2ce2bf60b27890aa5f99d6eb824f4f3d59f1b101bcce144b66d2ebL4-R4
This isn't necessary. The IS_BUILD is an environment variable. You can set that on the CI task using the CI platform's way of saying it's a build.


feat: 3346 customized response messages

As discussed with @yusukebe here https://github.com/orgs/honojs/discussions/3346
The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[x] Add TSDoc/JSDoc to document the code

Hi @marceloverdijk
Thank you for creating the PR. I have some requests:

I think the changes of src/context.ts and src/utils/mime.ts are not necessary in this feature. Please remove them.
Can you separate this PR for Basic Auth and Bearer Auth?  This means you will close this PR and create new two PRs.

No problem, I will update (and separate) the PR this evening.

@marceloverdijk
Thank you!

@marceloverdijk
Making strings as constant like APPLICATION_JSON_UTF_8 is good idea. But, it does not depends this feature and we can do it another PR.

@yusukebe I created the following (separated) PR's:

https://github.com/honojs/hono/pull/3371
https://github.com/honojs/hono/pull/3372
https://github.com/honojs/hono/pull/3370


404 at /get-%20started/07_multi_container/

I found a broken link : https://docs.docker.com/get- started/07_multi_container/

let me close this ticket as we need more details


Enable selective schema caching

Based on issue #146 reported by @oscar067 and the fix in PR #147 by the same awesome person, I created this PR to address the same issue from my own POV to achieve two objectives:

Be able to enable/disable the caching of schema in the srclient package.
Be able to choose which schemas get cached in this extension with the proposed caching solution by @oscar067.

@oscar067 WDYT?

Hi @mostafa ,
The way I use the xk6-kafka to test our microservices is by generating million of events which can be consumed by the microservice under test, that's because I need do the test with schema registry (consumers use it), and also I want to enable cache by default, because:

I do not want to test the perfomance of the schema registry.
I want xk6 to behave as other produces which also cache the schema.

I was testing the solution with master branch, as summary the  test now produce 11414 and previously 257870 with 50vu in 1 minute.
I'm trying to figure out what's happening on master branch, any help will be appreciated :)
This is my schema registry configuration:

  schemaRegistry: {
    url: schemaRegistry,
    tls: {
      enableTls: enableTlsSchemaRegistry,
      insecureSkipTlsVerify: true,
      clientCertPem: "/certs/cert.pem",
      clientKeyPem:  "/certs/cert.key",
      serverCaPem:   "/certs/rootg3_b64.cer",
    },
    enableCaching: true
  },

And this is the test configuration:
export const options = {
  //I want it back :) discardResponseBodies: true,
  insecureSkipTLSVerify: true,
  teardownTimeout: '360s',
  tlsAuth: [
    {
      domains: [],
      cert: open('/certs/cert.pem'),
      key: open('/certs/cert.key')
    }
  ],
  vus: 50,
  duration: "1m"
}

Result is: 11414 message count

However with previous branch with the patch (https://github.com/oscar067/xk6-kafka) : 257870

@riferrei With previous branch I also did some tests using the sync.Map in https://github.com/oscar067/srclient/tree/v1.0.1 and it wrote 18614

Seems it improves the performance.

@oscar067 The enableCaching: true parameter in the schemaRegistry configuration causes the caching of the srclient to be enabled, which I think isn't what you want. Instead, use the enableCaching: true parameter on the schema itself to enable the use of the xk6-kafka cache that you proposed.

I didn't use the correct branch for doing the tests so I didn't apply the changes on my code.
Indeed what I want is configure on the schema itself :)


Refactor Avatar Component

#704
Refactor Avatar, support props spread which filtering custom attributes from propTypes,
fix test eslint error.

Looks good!


Replacing a file attachment with a file of the same name doesn't work correctly

Currently if you try and replace it with the same file it thinks it already exists and puts a (2) next to the filename.
Also if you have a corrupt item which has the actual file missing it instead just allows you to upload it but deletes it immediately when it gets replaced.
EDIT:
It was worse than this

Add resource - upload a single file with the attachment dialog - save
Add resource - simply close the dialog
Original uploaded file would be deleted but attachment would still exist

Verified in master, 6.6 and 6.5


Feature Request: prevent Folded background color to override LineNr

Here is what my colorscheme looks like with a few statements folded:

The Folded background overrides the gray "gutter" (i.e. LineNr) color, which disturbs the gray continuity. It would be nice if there was some way of preventing that.
Steps to reproduce:
vim -u NONE
:set termguicolors
:set number
:hi Normal guifg=#e6e1dc guibg=#2f2f2f
:hi LineNr guifg=#8a8885 guibg=#e3e3e3
:hi Folded guifg=#bc9458 guibg=NONE
<type a few paragraphs and fold one of them by typing zfip>

I made a patch a couple of years ago, but it was not accepted.
The patch is still available here (I just modified it so it would apply again.)

I ran into this myself as well. I don't mind so much the actual signs not being shown in a folded sign column, but I do mind (aesthetically) the off-coloring.

I also ran into this issue today. 😄


syntax needs to be edited

the section for printing the list of the items in a container is
List the blobs in the container
    generator = block_blob_service.list_blobs(container_name)
    for blob in generator:
        print("\t Blob name: " + blob.name)```

But it needs to be

print("\nList blobs in the container")
generator = block_blob_service.list_blobs(container_name)
for blob in generator:
print("\t Blob name: " + blob.name)

The lines are not indented correctly

---
#### Document Details

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

* ID: 15591874-317e-ce4c-0dff-20d06b625e40
* Version Independent ID: be7fed9a-343a-0ec7-a94d-02c354d1ae33
* Content: [Azure Quickstart - Create a blob in object storage using Python](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-python)
* Content Source: [articles/storage/blobs/storage-quickstart-blobs-python.md](https://github.com/Microsoft/azure-docs/blob/master/articles/storage/blobs/storage-quickstart-blobs-python.md)
* Service: **storage**
* GitHub Login: @craigshoemaker
* Microsoft Alias: **cshoe**

@aaronjolson Thanks for the feedback. We are actively investigating and will get back to you soon.


proposal: conclude field tracking experiment

I propose to decide whether field tracking becomes an official feature and is available by default or can be removed.
Background
The field tracking experiment (activated via GOEXPERIMENT=fieldtrack runs since about 10 years now and leads to quite some special cases in the compilers (go and gccgo) as well as unique bugs like #42686. Usefulness and shape didn't change much. It looks more like an obscure feature to me at the moment than a real experiment where someone is active collecting data and analysing the impacts of it.
Maybe it is time to wrap it up, document the results and make a decision of whether Go should have this feature or not and act on that decision.

This feature seems to be obscure and not well documented. What was it intended to do?

The best docs for GOEXPERIMENT=fieldtrack are probably still the CL that introduced it: https://codereview.appspot.com/6749064.
It's used within Google for large scale handling of protobufs, which is why people keep reporting bugs about it.  Any other large scale user of protobufs could use it too if they wanted, and for all I know some do; there is some support for it in the google.golang.org/protobuf package.  So I don't think it's going to go away.
But we could discuss ways of moving it out of GOEXPERIMENT.  See also #42681.

I think the way forward is to simply have better regression tests for fieldtrack. We are interested in continuing to support its existing users, but I don't think we're ready to make it a more generally supported feature than that. E.g., I think we'd still like the flexibility to be able to change its semantics if necessary.

This mode is available for users who want it, much like dev.boringcrypto is.
Google uses both of them.
But neither is appropriate for Go proper, and neither is going to be enabled in the main Go distribution by default.

FWIW, a couple days I worked on https://go-review.googlesource.com/c/go/+/275034, and I would have accidentally broken fieldtracking again; except it was caught by the (super basic) test case I previously added in https://go-review.googlesource.com/c/go/+/271217.
So I already have a lot more confidence that field tracking should cause less maintenance pain going forward.


Avoid refecth of invalidated data

If I have a call route that invalidate a deleted data is there a way to not try to refetch it  ? Since it was deleted this would be an unnecessary server call.
Should there be a different metadata such as removed instead of invalidate?

@drFabio yes, instead you should set it to null, or undefined. invalidate is meant to indicate to the cache that some fragment it stale, should be deleted, and re-requested from the server next time.

That makes sense, thanks. My only issue would be that I can't remove a key (say something indexed by id) but I think this is not such a drag


GET /aidpackages/{id}/pledges throws 403

GET /aidpackages/{id}/pledges (Admin API) throws 403 with the following content:
{
   "schemas":[
      "urn:ietf:params:scim:api:messages:2.0:Error"
   ],
   "detail":"Operation is not permitted. You do not have permissions to make this request.",
   "status":403
}

@jayasanka-sack was this issue fixed somewhere? I tried to reproduce this in prod yesterday, but couldn't. I got a 401 error code on some pledges in my local setup though.

It appered without us doing any change in the first place. So it could be an intermittent issue in Asgadeo. @nipunsampath is looking into it.

Closing this since it works now @manuranga


Since when Sharepoint has a maximum of 2,000 lists and libraries in a site collection? What will happen?

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
I've read there is a maximum of 2000 lists and libraries in a site collection, this is in the Sharepoint documentation, at least since December 2021.
https://docs.microsoft.com/es-es/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits
But before this date, there was no limit, the documentation before december says:
"There is no limit to the number of document libraries you can have on a site."
I have verified that since 6th April, the sites that are surpassing this limit of 2000 libraries, when you create a library, an error jumps with this message:
Exception from HRESULT: 0x8107140D
But even if this happens, the library is created.
So my question is:

is this true? The error happens because of the limit?
what will happen in the future if the site oversteps the limit? Will create library/list be disabled? Or this error will continue happening.
If the limit is overpassed, what will be the consequence in the support / "guarantee"?
If there are consequences, is there a difference between passing the limit before december 2021 (when it was changed the limit) or after this date?.
Wouldn't it be better to create a type of suscription to overpass the limit of 2000 libraries?
Could you please give more info in general?

Thx.

While I don't have the exact answers for you. 2,000 has always been a number to be aware of. Documentation dating back over a decade has always recommended to keep lists to under 2,000 as the interface for enumerating lists/libraries does not perform well beyond 2000.
My two cents - While every requirement is different, if you have over 2,000 lists or libraries in a given site, it gives me a feeling of a larger problem in how your architecture was implemented. It may be time to re-think/architect what has been built in your environment.
I hope someone from Microsoft will be able to answer the questions you have though.

@bcameron1231 - thank you for the answer.
I completely agree with you. The docs always recommend to plan accordingly.

The document recommendations have changed, as far as I know, they never mentioned this limit, on the contrary they specify:
"There is no limit to the number of document libraries you can have on a site."
At the end, it has to be with an error of service update to provide optimizations in Sharepoint, surely related with this 2000-list limitation, but they have rolled it back, for the moment:
https://admin.microsoft.com/#/servicehealth/advisories/:/alerts/SP358241
Literally:
April 15, 2022 7:44 PM
Title: Users may be unable to create new document libraries in site collections
User Impact: Users may be unable to create new document libraries in site collections.
More info: Creations through both the user interface and Client Side Object Model (CSOM) method are affected.
Current status: Our deployment of the fix is progressing as expected, and users will experience relief incrementally as it reaches their environment. We expect that this process will complete by our next update.
Scope of impact: This issue may potentially affect any of your users attempting to create new document libraries in site collections via the user interface or CSOM method.
Start time: Tuesday, March 29, 2022, 9:39 PM (7:39 PM UTC)
Root cause: A recent service update intended to provide general service optimizations inadvertently disabled a previous configuration change, causing available routing infrastructure to be limited when requesting new document library creation.


Add staking instructions for mainnet

Congrats on the launch! 🎉
I added some new screenshots and instructions for Metamask setup and a link to stake.rocketpool.net/ for staking on mainnet, let me know if the wording needs to be fixed anywhere
Wasn't sure if I should mention the rETH limit but I can add that in too

Closing since the docs were updated already :)


[CWS] reduce amount of failed opens in hash resolver

What does this PR do?
This PR makes sure that in the hash resolver we don't try to open multiple times the same file. This is an optimization for the case where a given workload has a lot of PIDs, and we cannot open the file, so all opens fail.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Unifying kernel tests

At the moment, all of our non-reference kernel tests are basically the same (except for the templated tests, but I will get to that): We generate some random matrices or load one of the ani matrices, execute each of our kernels, maybe in multiple configurations on reference and the executor we are testing and compare the result for equality or near-equality.
This approach means a lot of code duplication, a lot of potential for inconsistencies and a lot of work in case we need to change an internal kernel interface.
With a very hacky and inaccurate bash one-liner, I looked at the amount of different lines between CUDA and HIP as well as OMP and CUDA/HIP for each test:

> for f in cuda/test/**/*.c*; do echo $f; ff=${f##cuda/}; fff=${ff%%.c*}; c1=$(diff -y --suppress-common-lines $f hip/${fff}.* | grep "^" | wc -l);c2=$(cat $f | wc -l); echo "$c1 / $c2" | bc -l; done
cuda/test/base/exception_helpers.cu
.18072289156626506024
cuda/test/base/math.cu
.07228915662650602409
cuda/test/components/cooperative_groups.cu
.33716475095785440613
cuda/test/components/merging.cu
.13103448275862068965
cuda/test/components/prefix_sum.cu
.03191489361702127659
cuda/test/components/searching.cu
.06530612244897959183
cuda/test/components/sorting.cu
.12056737588652482269
cuda/test/factorization/par_ilu_kernels.cpp
.26011560693641618497
cuda/test/matrix/coo_kernels.cpp
.04580152671755725190
cuda/test/matrix/csr_kernels.cpp
.11893583724569640062
cuda/test/matrix/dense_kernels.cpp
.12231759656652360515
cuda/test/matrix/ell_kernels.cpp
.04624277456647398843
cuda/test/matrix/hybrid_kernels.cpp
.07272727272727272727
cuda/test/matrix/sellp_kernels.cpp
.06060606060606060606
cuda/test/preconditioner/jacobi_kernels.cpp
.13129973474801061007
cuda/test/solver/bicg_kernels.cpp
.12885154061624649859
cuda/test/solver/bicgstab_kernels.cpp
.16713091922005571030
cuda/test/solver/cg_kernels.cpp
.15073529411764705882
cuda/test/solver/cgs_kernels.cpp
.17191977077363896848
cuda/test/solver/fcg_kernels.cpp
.14736842105263157894
cuda/test/solver/gmres_kernels.cpp
.15107913669064748201
cuda/test/solver/ir_kernels.cpp
.13768115942028985507
cuda/test/solver/lower_trs_kernels.cpp
.11695906432748538011
cuda/test/solver/upper_trs_kernels.cpp
.12209302325581395348
cuda/test/stop/criterion_kernels.cpp
.07619047619047619047
cuda/test/stop/residual_norm_reduction_kernels.cpp
.06164383561643835616
cuda/test/utils/assertions_test.cpp
.09638554216867469879
> for f in omp/test/**/*.cpp; do echo $f; ff=${f##omp/}; fff=${ff%%.cpp}; c1=$(diff -y --suppress-common-lines $f cuda/${fff}.* | grep "^" | wc -l);c2=$(cat $f | wc -l); echo "$c1 / $c2" | bc -l; done
omp/test/components/prefix_sum.cpp
.05376344086021505376
omp/test/factorization/par_ilu_kernels.cpp
.30769230769230769230
omp/test/matrix/coo_kernels.cpp
.24444444444444444444
omp/test/matrix/csr_kernels.cpp
.65886939571150097465
omp/test/matrix/dense_kernels.cpp
.56441717791411042944
omp/test/matrix/ell_kernels.cpp
.72398190045248868778
omp/test/matrix/hybrid_kernels.cpp
.07305936073059360730
omp/test/matrix/sellp_kernels.cpp
.47950819672131147540
omp/test/preconditioner/jacobi_kernels.cpp
.08366533864541832669
omp/test/solver/bicg_kernels.cpp
.20000000000000000000
omp/test/solver/bicgstab_kernels.cpp
.15449438202247191011
omp/test/solver/cg_kernels.cpp
.11808118081180811808
omp/test/solver/cgs_kernels.cpp
.14942528735632183908
omp/test/solver/fcg_kernels.cpp
.11619718309859154929
omp/test/solver/gmres_kernels.cpp
.13357400722021660649
omp/test/solver/ir_kernels.cpp
.12213740458015267175
omp/test/solver/lower_trs_kernels.cpp
.44221105527638190954
omp/test/solver/upper_trs_kernels.cpp
.45959595959595959595
omp/test/stop/criterion_kernels.cpp
.11111111111111111111
omp/test/stop/residual_norm_reduction_kernels.cpp
.40983606557377049180

Except for some cases where we actually have different test sets (like omp ELL vs GPU ELL), most of the files have less than 20% differences, and I am sure if we were to look at it more closely, most of these differences would just be the names `omp`, `cuda` or `hip` in the namespaces and executor variables. (and of course some inconsistencies due to the fact that changes were only made to one of the tests, but not matched with the other executors)
Thus I would like to discuss whether you consider it sensible to unify the kernel tests into a single code structure, and if so, what the best approach to implementing this would be.
I'm thinking of a wrapper that amounts to something like
ref->run(make_operation(...));
for (auto exec : execs) {
    try {
        exec->run(make_operation(...));
    } catch (NotImplemented...) {}
    ASSERT_*
}

This would again cut down on the test runtimes (as I assume the reference implementations are often our bottleneck) and provide additional benefits, like a simple enumeration of missing kernels.
This would also allow us to extend our GPU tests to the templated setting, while still avoiding issues with missing 64bit support in cuSPARSE/hipSPARSE.
I would of course still keep the individual test folders, since there are certain components etc. that are specific to the executors and should only be tested there.

In current test compilation, hip test has some link problem in ginkgo static library.
We use gcc compiler but add the hip linker.
It might cause some problems in combining the tests.

Another approach we could always take is add some macros to reduce the duplication and generate some of the boiler-plate code that most kernel tests have. It would probably not help in the compilation time, but would ease the writing of tests.


Challenge 2 Answer

Challenge 2 Answer using window function.

Removed the folder challenges/challenge2/answers. Can you send the PR again but move the files to the folder challenges/challenge_2? Thanks in advance!


Bug: Link not copied if only the link selected

Lexical version:
Steps To Reproduce

Open https://codesandbox.io/s/lexical-rich-text-example-5tncvy
Type Hello World
Select: ell
Add a link to the selection
Select: ell
Ctrl+C -> copy
Move the caret somewhere else then ctrl+V -> paste

The current behavior
The pasted "ell" does not have the link on it.
The expected behavior
"ell" should be a link
https://youtu.be/zx9JiVKk4gw

Fixed in #2474