I1130 11:36:17.981369   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:17.981380   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:20.916603   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:20.916625   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:22.937316   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:22.937336   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:25.312581   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:25.312605   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:27.939422   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:27.939443   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:30.947673   93466 leaderelection.go:352] lock is held by zhanxis-MBP.lan_4a53e0d2-acf5-467a-b026-dc593473ba5d and has not yet expired
I1130 11:36:30.947708   93466 leaderelection.go:253] failed to acquire lease karmada-system/karmada-operator
I1130 11:36:33.085412   93466 leaderelection.go:258] successfully acquired lease karmada-system/karmada-operator
I1130 11:36:33.085485   93466 recorder.go:103] "events: zhanxis-MBP.lan_590c201c-ddca-41d7-b49e-81e6f5f03713 became leader" type="Normal" object={Kind:Lease Namespace:karmada-system Name:karmada-operator UID:2814df43-e133-461c-877b-a9ef22293d19 APIVersion:coordination.k8s.io/v1 ResourceVersion:502228 FieldPath:} reason="LeaderElection"
I1130 11:36:33.085658   93466 controller.go:185] "Starting EventSource" controller="karmada" controllerGroup="operator.karmada.io" controllerKind="Karmada" source="kind source: *v1alpha1.Karmada"
I1130 11:36:33.085684   93466 controller.go:193] "Starting Controller" controller="karmada" controllerGroup="operator.karmada.io" controllerKind="Karmada"
I1130 11:36:33.086225   93466 reflector.go:221] Starting reflector *v1alpha1.Karmada (0s) from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:262
I1130 11:36:33.086239   93466 reflector.go:257] Listing and watching *v1alpha1.Karmada from sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:262
I1130 11:36:33.186927   93466 shared_informer.go:285] caches populated
I1130 11:36:33.187016   93466 shared_informer.go:285] caches populated
I1130 11:36:33.187068   93466 controller.go:227] "Starting workers" controller="karmada" controllerGroup="operator.karmada.io" controllerKind="Karmada" worker count=5
I1130 11:36:40.394839   93466 karmada_controller.go:36] "Started syncing karmada" karmada="karmada-system/karmada" startTime="2022-11-30 11:36:40.39481 +0800 CST m=+22.460318542"
I1130 11:36:40.401272   93466 karmada_controller.go:86] "Reconciling karmada" name="karmada"
I1130 11:36:40.401292   93466 karmada_controller.go:38] "Finished syncing karmada" karmada="karmada-system/karmada" duration="6.474959ms"
I1130 11:36:40.401322   93466 karmada_controller.go:36] "Started syncing karmada" karmada="karmada-system/karmada" startTime="2022-11-30 11:36:40.401315 +0800 CST m=+22.466823876"
I1130 11:36:40.401334   93466 karmada_controller.go:86] "Reconciling karmada" name="karmada"
I1130 11:36:40.401337   93466 karmada_controller.go:38] "Finished syncing karmada" karmada="karmada-system/karmada" duration="19.375µs"
I1130 11:36:50.553945   93466 karmada_controller.go:36] "Started syncing karmada" karmada="karmada-system/karmada" startTime="2022-11-30 11:36:50.553926 +0800 CST m=+32.619571709"
I1130 11:36:50.553984   93466 karmada_controller.go:94] "Deleting unable gc resources" karmada="karmada-system/karmada"
I1130 11:36:50.559509   93466 karmada_controller.go:38] "Finished syncing karmada" karmada="karmada-system/karmada" duration="5.574833ms"
I1130 11:36:50.559571   93466 karmada_controller.go:36] "Started syncing karmada" karmada="karmada-system/karmada" startTime="2022-11-30 11:36:50.559562 +0800 CST m=+32.625208042"
I1130 11:36:50.559602   93466 karmada_controller.go:45] "Karmada has been deleted" karmada="karmada-system/karmada"
I1130 11:36:50.559607   93466 karmada_controller.go:38] "Finished syncing karmada" karmada="karmada-system/karmada" duration="42.459µs"

Operator Command:
Usage:
  karmada-operator [flags]

Generic flags:

      --controllers strings
                A list of controllers to enable. '*' enables all on-by-default controllers, 'foo' enables the controller named
                'foo', '-foo' disables the controller named 'foo'.
                All controllers: karmada
                Disabled-by-default controllers:  (default [*])
      --kube-api-burst int32
                Burst to use while talking with kubernetes apiserver. (default 100)
      --kube-api-qps float32
                QPS to use while talking with kubernetes apiserver. (default 50)
      --leader-elect
                Start a leader election client and gain leadership before executing the main loop. Enable this when running
                replicated components for high availability. (default true)
      --leader-elect-lease-duration duration
                The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire
                leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be
                stopped before it is replaced by another candidate. This is only applicable if leader election is enabled.
                (default 15s)
      --leader-elect-renew-deadline duration
                The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must
                be less than or equal to the lease duration. This is only applicable if leader election is enabled. (default 10s)
      --leader-elect-resource-lock string
                The type of resource object that is used for locking during leader election. Supported options are 'leases',
                'endpointsleases' and 'configmapsleases'. (default "leases")
      --leader-elect-resource-name string
                The name of resource object that is used for locking during leader election. (default "karmada-operator")
      --leader-elect-resource-namespace string
                The namespace of resource object that is used for locking during leader election. (default "karmada-system")
      --leader-elect-retry-period duration
                The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only
                applicable if leader election is enabled. (default 2s)
      --resync-period duration
                ResyncPeriod determines the minimum frequency at which watched resources are reconciled.

Karmada controller flags:

      --concurrent-karmada-syncs int
                The number of karmada controller reconcilers that are allowed to sync concurrently. (default 5)

Logs flags:

      --log-flush-frequency duration
                Maximum number of seconds between log flushes (default 5s)
      --log-json-info-buffer-size quantity
                [Alpha] In JSON format with split output streams, the info messages can be buffered for a while to increase
                performance. The default value of zero bytes disables buffering. The size can be specified as number of bytes
                (512), multiples of 1000 (1K), multiples of 1024 (2Ki), or powers of those (3M, 4G, 5Mi, 6Gi). Enable the
                LoggingAlphaOptions feature gate to use this.
      --log-json-split-stream
                [Alpha] In JSON format, write error messages to stderr and info messages to stdout. The default is to write a
                single stream to stdout. Enable the LoggingAlphaOptions feature gate to use this.
      --logging-format string
                Sets the log format. Permitted formats: "json" (gated by LoggingBetaOptions), "text".
                Non-default formats don't honor these flags: --add-dir-header, --alsologtostderr, --log-backtrace-at, --log-dir,
                --log-file, --log-file-max-size, --logtostderr, --one-output, --skip-headers, --skip-log-headers,
                --stderrthreshold, --vmodule.
                Non-default choices are currently alpha and subject to change without warning. (default "text")
  -v, --v Level
                number for the log level verbosity
      --vmodule pattern=N,...
                comma-separated list of pattern=N settings for file-filtered logging (only works for text log format)

Misc flags:

      --kubeconfig string
                Paths to a kubeconfig. Only required if out-of-cluster.

Global flags:

      --add-dir-header
                If true, adds the file directory to the header of the log messages (DEPRECATED: will be removed in a future
                release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --alsologtostderr
                log to standard error as well as files (no effect when -logtostderr=true) (DEPRECATED: will be removed in a future
                release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
  -h, --help
                help for karmada-operator
      --log-backtrace-at traceLocation
                when logging hits line file:N, emit a stack trace (default :0) (DEPRECATED: will be removed in a future release,
                see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --log-dir string
                If non-empty, write log files in this directory (no effect when -logtostderr=true) (DEPRECATED: will be removed in
                a future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --log-file string
                If non-empty, use this log file (no effect when -logtostderr=true) (DEPRECATED: will be removed in a future
                release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --log-file-max-size uint
                Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the
                value is 0, the maximum file size is unlimited. (default 1800) (DEPRECATED: will be removed in a future release,
                see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --logtostderr
                log to standard error instead of files (default true) (DEPRECATED: will be removed in a future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --one-output
                If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect
                when -logtostderr=true) (DEPRECATED: will be removed in a future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --skip-headers
                If true, avoid header prefixes in the log messages (DEPRECATED: will be removed in a future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --skip-log-headers
                If true, avoid headers when opening log files (no effect when -logtostderr=true) (DEPRECATED: will be removed in a
                future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --stderrthreshold severity
                logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or
                -alsologtostderr=false) (default 2) (DEPRECATED: will be removed in a future release, see
                https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components)
      --version version[=true]
                Print version information and quit

@lonelyCZ updated

/hold cancel

cc @lonelyCZ

change: import sharedcli pkg of the karmada repo.
cc @lonelyCZ

Hi, @carlory , could you help to list what dependencies we have to import from main repo for the operator?

@lonelyCZ ok! I will do it later.

close it due to karmada#2973


OCC-245: Upgrade to latest OC preview to test System.Text.Json

OCC-245
Fixes #442

@sarahelsaig do you have an idea when this will be completed? Are there any known bugs this far that were not reported or addressed?
Just trying to get our ducks in a row to release 2.0 to the public.
Thank you

I have some kind of ISession bug that says:

OrchardCore.DisplayManagement.Implementation.DefaultHtmlDisplay|ERROR|Func2 thrown from System.Func2[[OrchardCore.DisplayManagement.Implementation.ShapeDisplayContext, OrchardCore.DisplayManagement, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null],[System.Threading.Tasks.Task, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]] by InvalidOperationException System.InvalidOperationException: Two concurrent threads have been detected accessing the same ISession instance

It's not yet clear what causes it so I have not reported it. To my knowledge this is the only problem left for OCC.

OrchardCore.DisplayManagement.Implementation.DefaultHtmlDisplay|ERROR|Func2 thrown from System.Func2[[OrchardCore.DisplayManagement.Implementation.ShapeDisplayContext, OrchardCore.DisplayManagement, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null],[System.Threading.Tasks.Task, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]] by InvalidOperationException System.InvalidOperationException: Two concurrent threads have been detected accessing the same ISession instance

@sarahelsaig this is likely a problem in your code not in OC. We'll it could be OC but I don't think it is since we have added lots testing in OC to check for this is many cases.
last time I had that issue is was coming from migrations. One migration step was creating a new index while I had another migration that was reading the database which caused a concurrency issue. I avoided that by deferring the migration that queries the database and everything was solved. I don't know if this is the problem here or help but I though I would at least share this.
Do you know the controller that cause this exception? maybe start there since the exception is thrown from the shape rendering call. maybe you are updating records from the view for some reason?

@sarahelsaig any new bugs that aren't reported yet? Is there an ETA that you can share with us for this PR?

The build timed out again.

The build timed out again.

I've just found this threadPerHost setting for ZAP, which likely could fix the hang/timeout problem if set to 1. I will add the option to UITT and test it tomorrow.

Hmm, interesting, thanks!

Unfortunately threadPerHost does not work. The only way I was able to mitigate this problem was to reduce the run time of the active scan by setting maxActiveScanDurationInMinutes from 10 to 5.

@MikeAlhayek do you want to check this?


use the new popover attribute/api for popovers

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/popover

Yeah, but also: Switching to using the Popover API for the Menu component to a large degree removes the need for the menu component in the first place.
It would be useful to extract floating and tabster into its own modifiers (see also https://github.com/hokulea/aria-voyager/blob/main/packages/ember-aria-voyager/package/README.md)
This would make possible the following beautiful API for a menu component with pure HTML plus element modifiers:
<button popovertarget='my-popover'>Open popover</button>
<menu popover id='my-popover' {{float}} {{tabster}}>
  <button role='menuitem' >my menuitem</button>
</menu>

popoverModifier can target the button with popovertarget='${element.id}'
const float modify(element, ,positionalArguments, namedArguments) {
    const referenceElement = document.querySelector(`[popovertarget='${element.id}']`) // with options to override in positionalArguments
    …
}

can popover attribute'd things be nested? can you have a menu open on a menu?
or is it that dialogs can nest, and you'd popovers must be the top (no nesting).
In any case, I'm still waiting for Baseline to give the go-ahead

I would still want a component though... because wiring up id / target attributes between elements is error prone, and it's nice to have a component do that for me

{{float}} {{tabster}}

I am a big fan of this.
For floating, you kinda have to use a component for now though, because you need to anchor the floater to something (usually a button)

modifier https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/src/floating-ui/modifier.ts#L36
component https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/src/floating-ui/component.gts#L53

These were taken from https://github.com/CrowdStrike/ember-velcro as they're not keeping up with things at a pace I like (and they're cool with it)
See:

https://github.com/CrowdStrike/ember-velcro/pull/199/files

In particular, this FloatingUI wrapper still needs to be documented
Here is an example usage, in the Popover component: https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/src/components/popover.gts#L216
(it combines button and menu together)[^menu]
Though, I will point out, that these components are usually pretty light. But I find the amount of ceremony involved with plain HTML (and to do it correctly, etc) to often be too much. I would like to write less when I'm working on apps.
[^menu]: Here, where the content is used: https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/src/components/menu.gts#L171 it's using a Role of menu for the menu -- because for a generic popover, you can't really know if your going to be used as a menu or not (seen here: https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/src/components/popover.gts#L125 -- but also, It does look like the element is customizable, so this probably needs some exploration)
{{tabster}}
I think this is doable, tbh.
The tabster code in menu.gts is specific to menus, but the tabster modifier can assume that it would be used on multiple kinds of things, and switch off the element / role that it's used on.
This would be a great PR, tbh <3

For floating, you kinda have to use a component for now though, because you need to anchor the floater to something (usually a button)

yes, but also no! :) In the popover api I have great success utilizing that a popover is strictly tied to a button with popovertarget=element.id. See my example above with:
modifier((element) => {
   const target = document.querySelector(`[popovertarget='${element.id}']`)`
})

In my experience, this makes it possible to not need to wrap it in a component. 🎉

can popover attribute'd things be nested? can you have a menu open on a menu?

Yes, I have success using popovers inside popovers and dialogs. – especially for tooltips this is necessary. Works out of the box for most borwsers, and a good polyfill for older versions.

I have success using popovers inside popovers and dialogs. – especially for tooltips this is necessary. Works out of the box for most browsers, and a good polyfill for older versions.

This is excellent news!
Any word on when Safari will be included in the Baseline? is it worth it to wait? or should we go-ahead and start using native popover?
(which reduces a fair amount of internal complexity, and potentially removes the need for portalling, which fixes some a11y issues / tab-order issues).

strictly tied to a button with popovertarget=element.id.

This is the ceremony that I like avoiding.
This project should probably provide the primitives for folks to do what you want to do though -- and I would gladly accept a PR to enable that <3
Also, I should probably add to all the component docs answering "why a component" -- would be good to expose what is abstracted / why the component exists in the first place (also allowing smart folks (such as yourself!) to choose when it makes sense to use the underlying modifier primitives)

This is turning out nice

anchorTo here (I renamed it): https://ember-primitives.pages.dev/5-floaty-bits/anchor-to.md


Adding support for multilingual MonoT5 reranker

Adding support for multilingual MonoT5 reranker.
Using AutoModelForSeq2SeqLM() for loading T5/mT5 models.
A list containing the models name with its predictions tokens was added to help users.

@ronakice, could you please take a look and once you are comfortable, merge it?

Hey @ronakice, I will merge this one but please let us know if you have any concerns


Failed to create JWT

Access token is missing required scopes [u'user:name', u'user:see', u'user:keystore', u'user:validated:email', u'user:validated:phone', u'user:address'] (/base/data/home/apps/e~tff-backend/20170914t184448.404104754256813064/plugins/tff_backend/bizz/user.py:65)

User registered before fix was deployed


Move comments to correct blank page issue

Changes merged in a different PR: https://github.com/corda/corda-docs-portal/pull/2135


🐞 Module init errors with python SDK and custom ca certificates

What is the issue?
Using podman, I am running a custom engine version v0.11.9 with an internal ca cert mounted in /usr/local/share/ca-certificates/.
I can successfully initialize modules for both Go and TypeScript SDKs but am facing an error when initializing a module with the Python SDK with dagger init --sdk python.
Codegen is failing at the installation of uv via pip:
Collecting uv==0.2.11 (from -r /reqs.txt (line 1))
Stderr:
...'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c.10006)

🤔 I'm wondering if the custom CA cert and/or the CURL_CA_BUNDLE and REQUESTS_CA_BUNDLE environment vars are not getting applied from the custom engine to the codegen container as I see entries in the engine logs like :
level=debug msg="> creating tw29lol6zrzv... [update-ca-certificates]" span=[internal] exec /runtime"
level=debug msg="> container done tw29lol6zrzv... [update-ca-certificates]" error="<nil" span="[internal] exec '/runtime"

Additional discussion and original thread at https://discord.com/channels/707636530424053791/1253778132259835965
Dagger version
dagger 0v.11.9 (registry.dagger.io/engine) darwin/amd64
Steps to reproduce
1.  Configure the connection interface with the custom endpoint for the custom runner.
export _EXPERIMENTAL_DAGGER_RUNNER_HOST="podman-container://dagger-engine-v0.11.9"

3. Initialize a new dagger module that will use the Python SDK
I am running this in an empty ci/ directory within a project.
dagger init --sdk python

Log output
x ModuleSource.asModule: Module! 22.6s
! failed to create module: select: failed to update codegen and runtime: failed to generate code: failed to call sdk module codegen: select: call function "Codegen": process "/runtime" did not complete successfully: exit code: 2

Error: failed to generate code: input: moduleSource.withContextDirectory.withName.withSDK.withSourceSubpath.asModule resolve: failed to create module: select: failed to update co degen and runtime: failed to generate code: failed to call sk module codegen: select: call function "Codegen": process "/runtime" did not complete successfully: exit code: 2

Stdout:
marshal: json: error calling MarshalJSON for type *dagger. GeneratedCode: input: container.from.withEnWariable.withEnariable.withEnWariable.withEnvariable.withMountedCache.wi thDefaultTerminalCd.withEnvVariable.withNewFile.withExec.file resolve: process "pip install -r /reqs.txt" did not complete successfully: exit code: 1

Stdout:
Could not fetch URL https://pypi.org/simple/uv/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/uv (Caused by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c.10006)'))) - skipping

Stderr:
WARNING: Retrying (Retry(total-4, connect-None, read-None, redirect-None, status-None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY FAILED] certificate verify failed: unable to get local issuer certificate (ssl.c: 1006) '))': /simple/uv/
WARNING: Retrying (Retry(total=3, connect-None, read-None, redirect-None, status-None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:7006)' ))': /simple/uv/
WARNING: Retrying (Retry(total-2, connect=None, read=None, redirect-None, status-None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY FAILED] certificate verify failed: unable to get local issuer certificate ( ssl.c:1006)'))': /simple/uv/
broken by 'SSLError(SSLCertVerificationError(1. 'ISSL: CERTIFICATE VERTF
WARNING: Retrying (Retry(total=1, connect-None, read-None, redirect-None, status-None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY FAILED]
certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)' ))': /simple/uv/
WARNING: Retrying (Retry(total=0,
connect-None, read-None, redirect-None, status-None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY
FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c: 1006) ' ))': /simple/uv/
ERROR: Could not find a version that satisfies the requirement uv=0.2.11 (from versions: none)
ERROR: No matching distribution found for uv=0.2.11

@jeremywitte, can you check if it works in Dagger v0.12?

@jeremywitte, can you check if it works in Dagger v0.12?

All is good - I can successfully initialize a python module with custom ca certs starting with Dagger v0.12.0!
Thanks


hoofoot.com extractor Add new extractor

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

What is the purpose of your pull request?

[ ] Bug fix
[x] New extractor
[ ] New feature

Description of your pull request and other information
Added a new extractor for the site hoofoot.com. The site contains latest football highlight videos.

This is already well covered by generic extractor. What's the point?


Fix the build on windows

Rustbox doesn't build on Windows, so I made that an optional dependency.  This disables 2048 on Windows, but Travis-CI will continue to build 2048.
Maybe this would be better as a "cfg" based on OS?

I'm not sure we have a viable alternative that's cross platform.... I'm tempted to suggest having a "windows" feature flag that disables things that are problematic on windows rather than a concrete "2048" flag.

Looks like maybe #[cfg(not(windows))] or something with target_os. My only thought was that 2048 was a better descriptor of the feature being enabled.

Yeah I agree, I feel like as we move forward we'll see more samples that only work on not windows though.

Just checking back in on this.  I guess I'll explain why I went the way I did.
I didn't use Platform-specific dependencies because it requires specifying the dependency for every target.triple that we support. (http://doc.crates.io/manifest.html#the-dependencies-section.)  That seems like an easy way to forget a platform and say break the build on OSX or x86_64 linux or something just to conditionally compile one feature.
Maybe "unixOnly" isn't the best way to describe the set of platforms which support the feature.  Someone want to bikeshed on that?

Hmm I'd like to hear @aochagavia or @pfalabella 's opinion before deciding. :)

I think using a feature is a good idea.

@ghotiphud Are you comfortable with how this looks? I feel comfortable merging.

Looks good to me.

@ghotiphud Thanks so much!


No Power BI button?

In the Enable the Template app section it says "The data collection process will complete in two to 48 hours depending on the size of your tenant. The Go to Power BI button will be enabled (no longer gray) when data collection is complete."
I don't see a Go to Power BI button
Also in the Start the template app section it says Copy tenant ID - How?

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

ID: 65732911-21e9-0902-51fa-0d3ae0caaa7a
Version Independent ID: 3682fff5-36fc-1d69-96ef-88f7f73225d5
Content: Enable Microsoft 365 usage analytics - Microsoft 365 admin
Content Source: microsoft-365/admin/usage-analytics/enable-usage-analytics.md
Service: o365-administration
GitHub Login: @efrene
Microsoft Alias: efrene

@msbemba Thank you very much for the contribution and sharing this explanation. @jarvisington Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


API: Change Period('NAT') to return NaT

[x] closes #12759, #13582

[x] tests added / passed

[x] passes git diff upstream/master | flake8 --diff

[x] whatsnew entry

pd.Period('NaT', freq='D') now returns pd.NaT rather than its own nat repr.

To be compat with Period arithmetic, pd.NaT now supports addition / subtraction with int (previously ValueError).

pd.NaT + 1
# pd.NaT

Added tests for following:

[x] Period and PeriodIndex, Series ops

[x] add, sub, comp

[x] PeriodIndex creation from list-like which contains Period and NaT (#13430)
[x] PeriodIndex boxing
[x] .to_period
[x]  __contains__ any NaT-like(pd.NaT, None, float('nan'), np.nan)

CC @MaximilianR

[Current coverage][cc-pull] is 84.33%

Merging [#13609][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master     #13609   diff @@
==========================================
  Files           138        138
  Lines         51092      51100     +8
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43087      43096     +9
+ Misses         8005       8004     -1
  Partials          0          0

Powered by Codecov. Last updated by [c2cc68d...3a3f799][cc-compare]
[cc-base-branch]: https://codecov.io/gh/pydata/pandas/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/pydata/pandas/compare/c2cc68d6eb233bc74c6bd032650704030c4b9a9d...3a3f799534ab526025a8708cb44776c4f384b41c?src=pr
[cc-pull]: https://codecov.io/gh/pydata/pandas/pull/13609?src=pr

@sinhrks Can you rebase this? Then it will be easier to review the additional changes (as I think the first commit is now already in master?)

@jorisvandenbossche sure. updated.

thanks @sinhrks this is really nice!


Cant build chouchbase-lite-android on windows using Android Studio version-2.0 Gradle version -2.10

I am trying to build couchbase-lite-android using command '/gradlew assemble' in windows 7 and its giving me below error
Execution failed for task ':libraries:couchbase-lite-java-forestdb:buildNative'.
> A problem occurred starting process 'command  C:\Users\..\android-ndk-r11c-windows-x86_64\android-ndk-r11c/ndk-build

Android Studio version-2.0
Gradle version -2.10
I believe there in windows system 'ndk-build' would be 'ndk-build.cmd' and I tried using this command in every grade file where this used but again I am having below error
make: *** No rule to make target C:/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/jni/../vendor/cbforest/vendor/sqlite3-unicodesn/fts3_unicode2.c', needed by C:/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/obj/local/armeabi-v7a/objs/CouchbaseLiteJavaForestDB/C_/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/jni/__/vendor/cbforest/vendor/sqlite3-unicodesn/fts3_unicode2.o'.  Stop.

duplicated with https://github.com/couchbase/couchbase-lite-android/issues/820

Hi @dhams ,
When you have time, please try to build from master branch?
Thanks!

Hi @hideki . I have tested with master branch and it seem issue is still there.Getting error like
make: *** No rule to make targetC:/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/jni/../vendor/cbforest/vendor/sqlite3-unicodesn/fts3_unicode2.c', needed by C:/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/obj/local/armeabi-v7a/objs/CouchbaseLiteJavaForestDB/C_/Users/../CouchBAseDemo/libraries/couchbase-lite-java-forestdb/jni/__/vendor/cbforest/vendor/sqlite3-unicodesn/fts3_unicode2.o'. Stop.
my project structure is like below.
Project
|
-app
-libraries
|
-couchbase-lite-android
-couchbase-lite-java-core
-couchbase-lite-java-forestdb
-couchbase-lite-java-native

Hi @dhams,
Can you check followings?

Did you call 'git submodule update --init --recursive'?
Is current Android.mk same with https://github.com/couchbaselabs/couchbase-lite-java-forestdb/blob/master/jni/Android.mk? Please check.
Does calling ndk-build -C jni at directory of couchbase-lite-java-forestdb work?

Note to Self:
I tested the build with couchbase-lite-android. Not build with  application. I should test submodule solution.

@dhams,
I believe the deepest file path by nested submodules is longer than 255 (windows file path limitation). Then git submodule update --init --recursive does not work. There are not entire source codes are not cloned from github.
<directly>\<application project dir>\libraries\couchbase-lite-android\libraries\couchbase-lite-java-forestdb\vender\....

Please try to create you application folder under C:\? or use libs instead of libraries?
Thanks!
Hideki

@hideki Thanks for your reply.
I have also tried to checkout the code in C folder. The code is almost downloaded from gihub using
git submodule update --init --recursive command but two times that has generated failed logs
Clone of 'git://github.com/snej/sqlite3-unicodesn.git' into submodule path 'vendor/sqlite3-unicodesn' failed Failed to recurse into submodule path 'libraries/couchbase-lite-java-forestdb/vendor/cbforest'
Submodule path 'libraries/couchbase-lite-java-native/vendor/sqlcipher/vendor/sqlcipher': checked out 'c01b94fb6a6b54e00b9839e7314893f72c9dab22' Failed to recurse into submodule path 'libraries/couchbase-lite-java-forestdb'
Attached full logs of that event . Please check if you can find anything wrong.
module_log.txt

@dhams, I believe longest file path makes git submodule update --init --recursive fail. Can you try to change project name shorter. Also you can try to change libraries to libs that is described in https://github.com/couchbase/couchbase-lite-android/wiki/Add-Couchbase-Lite-to-your-project-as-a-submodule. Also you can also change couchbase-lite-android, couchbase-lite-java-core, couchbase-lite-java-forestdb and couchbase-lite-java-native shorter name when you do git submodule add.


Social

As part of this PR
Added OAuth flow for Twitter login and account linking

Implement Twitter OAuth authentication for user login
Add functionality to connect Twitter social account with user account
Enable users to link their Twitter account to their existing profile
Hooks for refresh token
Implement feature to  watch ended streams

LFG


Memory Increase

Hi, congratulation on your excellent work.
I have tried to train your model. But I find the memory usage of GPU during training is increasing. Do you know why it is?

Hi @mingqiJ , happy to help. Could you provide more details?

Which script are you running?
Do you see CPU memory increasing or GPU memory? Which GPU are you using?
Are there any plots we can look at?

Hi,
I used scripts/scannet/scannet_swin_benchmark.sh. But use bigger image size
The GPU memory is increasing with the iteration increase.
Before the 150 iterations, the print out (log text) shows max_mem: 59464M.
After some iterations, the print out (log text) shows max_mem: 63285M.
In fact, I have added torch.cuda.empty_cache() at the end of the run_step() function in Trainer, otherwise the max_mem increase faster. But adding torch.cuda.empty_cache() dramatically increase the training time.

I see, I wouldn't worry too much about max_mem since the unprojected point cloud will have variable surviving points after voxelizations.
Could you let it run for a couple hours and share with me the wandb link of the run? That would track the GPU memory usage, and we can see if it is monotonically increasing or just randomly varying (which is expected).

Okay. I already have one. You mean this?

yep :)
I think this looks pretty normal! Doesn't it?

Yes. It looks normal. Emm, don't know why it outs of memory last time. Thank you.
Btw, how long you need to train ODIN-Swinb using 2 A100 on scannet dataset?

I think it was about 1.2 days, you can take a look at training logs here: https://huggingface.co/katefgroup/odin_logs/tensorboard
In my experience, max_mem is somewhat mislesding: usually it needs to be decently lower than the max capacity of the GPU. I suspect that's because it displayes average max_memory across several iterations. And because there can be variabilty in point cloud size across iterations, the actual max_memory is larger.

I see. Thanks for your answer.
So if log file said : eta: 1 day, 22:04:47. It means 1 day and 22 hours?

yes

Thank you. I don't have any questions.

ok amazing!


Is it abandoned? Update signalr version.

If not, update to signalR package version v7.
"@microsoft/signalr": "^7.0.4",

Btw, do you know where is it possible to check breaking changes across @microsoft/signalr major versions?
Which new feature do you need that older package versions don't support?
Unless it's needed due to breaking changes, I'd prefer to avoid a new major version of this package
If it's possible to support multiple major versions of @microsoft/signalr without breaking changes on our side, I'd go that route

From a quick look at the repo commits into the SignalR TS client, there doesn't seem to be any breaking changes which would affect this package, just internal or purely additional changes
Updating peerDependencies to accept newer versions of @microsoft/signalr here should be the way: `"@microsoft/signalr": "^5.0.0 || ^6.0.0 || ^7.0.0", as well as bumping this

I published a new version which bumps deps and accept new major version of signalr
Check out if it works for you


[PE-D] No error when supplied END_DATE is before START_DATE for Find command

Steps to reproduce:

Input 'find start/2022-04-01 end/2022-03-01' as command

Result display shows '0 tasks listed!'

Based on the UG, "Harmonia finds the tasks whose deadline is between the START_DATE and END_DATE inclusive.", if the intended meaning for this line is to display all tasks with deadline between both dates supplied, then the result should have displayed the list of tasks, however it did not, hence should show an error message instead of '0 tasks listed!'.
Expected result:
Result display to show that the END_DATE supplied is after START_DATE, which does not make sense and not allowed as input.
Actual result:

Labels: severity.Medium type.FeatureFlaw
original: hsiaojietng/ped#2

Actually not a bug. But it's good to have an additional check on this.


Context data capture and merge for XDM mapper

Description
This feature enables capture of all context data events that are handled by the Edge Bridge extension, with the ability to merge the data dictionaries of those events to create an easy-to-use output for the XDM mapper tool.
It is possible to merge with or without key case sensitivity (ex with case insensitive merge: product.id == Product.Id == PrOdUcT.iD), and this setting applies throughout the deep merge process; given nested dictionaries with matching keys on both sides of the merge, the inner keys will also use the same case sensitivity setting.
Please note:

ContentView button functionality related to the new context data capture APIs is for testing purposes and will be removed before the final merge

May be helpful to add capability to the test app to be able to send custom JSON objects as track action/state payloads to better test context data capture APIs

Request for feedback:

The current location of the new functionality is currently in EdgeBridge.swift; would like to get thoughts on if a helper class or some other location would be more appropriate
in deepMerge L#264 in EdgeBridge.swift, currently keys within the same dictionary that are equivalent in the case insensitive compare are collapsed into one entry using case sensitive ordering, with the last entry being taken (in this case, whatever the last entry's data type is is taken without any kind of merge logic with other equivalent keys). I used case sensitive ordering in this case so that the merge would be deterministic in terms of consistent results in the final merge. Without this ordering, there is no guarantee what key value pair will make it to the final merge. However, would like to get feedback on if this approach is a good way to handle key collisions within the same dictionary when using a case insensitive compare.
ex:

[
"key1": "string",
"Key1": ["key2": 123],
"KEY1": ["key3":"value"]
]

// After consolidation becomes:
["KEY1":["key3":"value"]]

// NOT (that is, no deep merge when consolidating within the same dictionary):
["KEY1":["key2": 123, "key3":"value"]]

as a follow-up to the above point, the logic for merging keys into the base dictionary L#289-L#293 in the case insensitive merge has no defined order, and will result in non-deterministic results (either way for the internal case and merge case i think the behavior should be consistent)
should we control the final JSON output's key order? Either by alphabetical, value type, etc? what about for nested structures? (adds some complexity to the final output process)

Related Issue
See MOB-16906 for additional details
Motivation and Context
This is to help users of the extension quickly capture and merge context data from track action/state Events for use in the XDM mapper tool.
How Has This Been Tested?
Tested using various context data payloads sent though trackAction API that test (see test payloads in ContentView.swift):

the merge logic with/without case sensitive key comparisons
value type conflicts when keys collide in merge operation (both raw value type and Optional status)
key casing conflicts when using case insensitive merge
deep merge for nested JSON objects

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Hi @timkimadobe , I'd suggest moving the functionality out of the EdgeBridge class to a new class. Maybe something like ContextDataCapturer?  The new class will contain all the logic to capture, merge, and report the results. EdgeBridge would contain an instance of this class but only call it for the start/stop APIs and to pass Events.

@timkimadobe You have the public APIs to start/stop the capture as static functions to class EdgeBridge. Instead, can you create an EdgeBridge+PublicAPI class which defines the public APIs? Like other public APIs in the SDK, they will dispatch events to the Event Hub which are then listened for and handled by EdgeBridge. You will need to update EventType in Core to include a new EventType.edgeBridge property and possibly add one or two EventSouce properties to represent the start/stop capture events.

Thanks for the followup review Arjun! I liked the suggested simplifications to the constants, and I've updated the logical flow where they are used to reflect the type change

Thanks for the updates @timkimadobe, I added few more comments. Feel free to change the wordings for the log messages as suited. I have written it in a way to give you an idea. Let me know if you have any doubts/concerns.

I believe the responsibility of collecting, storing and clearing the events should be with the capturer and we should pass the entire array of events for generating the report.
getCaptureReport(events: [Event], merge: Bool, caseSensitiveMerge: Bool) -> String


Publish "Overview of modern web tooling" article

See https://docs.google.com/document/d/1T4s2R_aLefiNWxeC4g-dbEXXfBw_tGw5NdSOS6OCRvM/edit#heading=h.w95jqs1xx0k8 for documentation spec for this article.
Author: Remy
Acceptance criteria

[x] First/second draft reviewed and sent back with feedback.

[x] Final draft agreed upon.

[x] Final draft published.

See https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Overview


Corrupted buffer in Chrome 79 (legacy web engines)

After https://github.com/jellyfin/jellyfin-web/pull/4613 (+https://github.com/jellyfin/jellyfin-web/pull/4702), JASSUB stopped working in Chrome 79 (and presumably on TVs with legacy web engines).
1.7.1

It looks like the buffer was copied incorrectly. It is updated when the event changes, but remains corrupted.
With asyncRender: false, it seems to work.
1.5.13 (for reference)

Sample
test.ass.txt

hmmmm this is a nasty one
TLDR: I recommend you disable async render based on user agent if UA is < Chrome79
I'm not really sure what happens here, while async render is running, the underlying data won't ever be mutated, so it's not like the corruption is caused by something changing the data, so I assume this is a bug in chromium that was fixed a while back
this most likely stems from the fact JASSUB passes memory references instead of copies to the browser, which causes this, simply because it's a LOOOOOOT faster than copies
I could fix this in JASSUB, but I'm not sure I'd want to

I could fix it by copying memory, but I don't like that idea because it's pretty much saying "hey, all clients need to render stuff 10% slower [random value, but it's likely higher]" just because an older engine has bug which no longer exists in newer version
I could parse useragent, but that's also a bad idea in case someone wants to run the library in NodeJS using node-canvas

I really think it'd be better to add a check in the jellyfin-web app, in the constructor simply as you said disable asyncRender if it's an old version of webOS disable asyncRender, as there isn't much performance to gain by using it on those older engines as the hardware running it likely won't be able to render any complex typesetting even with the help of asyncRender
I'll see if I can make a PR sometime next week if you aren't sure how to do this

asyncRender: true works with 1.5.13 (I tried reversing those PRs).

and it's also significantly slower on heavy TS
using an older version means you lose quite a few important features, mainly Firefox performance improvements, SIMD improvements and colorspace conversion

Found that replacing subarray with slice fixes the corruption. But it creates a copy, iiuc.
https://github.com/ThaUnknown/jassub/blob/9476f4f9a0f226a23920bea7f91be467f45c3195/src/worker.js#L236
Introduced https://github.com/ThaUnknown/jassub/commit/41d630460e9bd49ab7a99193babecc8a3147965e#diff-a19812fe5175f5ae8fccdf2c9400b66ea4408f519c4208fded5ae4c3365cac4dR235

yes as I said it's because of the references not copies, but again, changing this drops performance a LOT, so it's way better to parse useragent and disable asyncRender on old browsers which have bugs in createImageBitmap, rather than reducing the rendering performance of all browsers that don't even have the issue
realisation
hm I'll try reproducting the bug, and making a test for it like it's done for the alpha bug, but I'm very afraid its a WASM thing
then simply slice instead of subarray on an if check if the bug exists

I managed to track down and reproduce the bug, TLDR chromium used to ignore the offset from a subarray completly, and also mangle some of the data [massive woes], so i'll add a check for this, and set async render to use slice if this happens

this should be fixed in 1.7.2

also any chance i could get the video that you used? seems cool for debugging timestamps

Nothing special.
#!/bin/bash

IMAGE=banner-light.png
OUTPUT_IMAGE=out.png
OUTPUT=out.mp4

H264LEVEL=5.1

convert "$IMAGE" -background gray -gravity center -extent 1920x1080 "$OUTPUT_IMAGE"
ffmpeg -loop 1 -i "$OUTPUT_IMAGE" -c:v libx264 -profile:v high -level:v $H264LEVEL -t 300 -pix_fmt yuv420p -vf scale=1920x1080 -vf "drawtext=text='%{pts\:hms}': x=(w-tw)/2: y=h-(2*lh): fontcolor=white: fontsize=48" "$OUTPUT"

You may need to set the I-frame interval, because it is 10s due to the still image.

fixed the wrong function location in 1.7.3

@dmitrylyzo I assume this fixed it?

You reverted the last change too much and this comment is valid again.


Fix token choice w/ checkpointing, add tests

Description
Now token choice remembers its discrete choices.
Checklist

[x] Is this PR focused on a single feature without the possibility of being divided into smaller PRs?
Kinda, adding switch tests could be split, but IMO it's a nice extra
[x] Are all variables set with logical defaults that are backward compatible?
[x] ~I attached link to neptune if it was necessary~
[x] Have you successfully executed the linter and tests?
[x] Are all functions concise and don't require splitting?
[x] Is there documentation for arguments and complex logic?
[x] Are there no temporary solutions in the code? Should a task be added to Trello to refine the code?
[x] Are all functions placed in appropriate files?
[x] Is the PR name meaningful and descriptive?
[x] Is PR description provided, or unnecessary?

Other questions:

[ ] If I made changes to the requirements or anything related to the Singularity image I did generate new image and upload a new image to the clusters
[ ] If this change is significant enough I notified all individuals working with this repository (@channel in slack channel)
[ ] If there is a need for a second reviewer I requested additional review

Reviewer's checklist:

[ ] Does the Neptune link work and does it actually compare the situation before and after the PR?
[ ] Do I understand the code?
[ ] Do I think another reviewer is not needed or I commented that this PR need another reviewer?

The tests pass, but does it run? I'd like a neptune run for 10 steps

Merged in another PR


Browser console warning about React 18 and ReactDOM.render

Describe the bug
Now that React 18 is released, creating a new project (npx create-react-app my-project) and running that project will show the browser console warning:
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot
printWarning @ react-dom.development.js:86

The project DOES run, however.
Did you try recovering your dependencies?
N/A as a new project
npm --version is: 8.1.4
Which terms did you search for in User Guide?
Didn't find anything for "React 18" or "render" or "ReactDOM"
Environment
Environment Info:

  current version of create-react-app: 5.0.0
  running from /Users/swiftone/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 12.1
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: Not Found
    npm: 8.1.4 - ~/.nvm/versions/node/v16.13.0/bin/npm
  Browsers:
    Chrome: 99.0.4844.84
    Edge: Not Found
    Firefox: 94.0.1
    Safari: 15.2
  npmPackages:
    react: ^18.0.0 => 18.0.0
    react-dom: ^18.0.0 => 18.0.0
    react-scripts: 5.0.0 => 5.0.0
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce

npx create-react-app my-project
cd my-project
npm start
(view console in browser)

Expected behavior
No browser console errors
Actual behavior

Reproducible demo
Any project, see steps to reproduce

While this should be a pretty trivial fix to the template, I must admit I was a bit surprised CRA just installed a different major version of React - wouldn't it make sense to have a setting for the major version or React it assumes?

I have been replaced in the index.js for that error as ..
import React from 'react';
import ReactDOM from "react-dom/client";
import './index.css';
import App from './App';
ReactDOM.createRoot(document.querySelector("#root")).render(<React.StrictMode></React.StrictMode>);

I may have commented in the wrong place after reading this but I had found the issue reported from the default test when running it after an initial new project setup with create-react-app.
https://github.com/testing-library/react-testing-library/issues/509#issuecomment-1083580862

There is generally no reason to update a global CRA so very few people who install it would do that

Perhaps a warning when the expected major version doesn't match?  I understand encouraging up-to-date CRA, but "CRA will break randomly, and when it does the solution is to wait" doesn't sound like a great solution either.

Working example in TypeScript:
import { BrowserRouter } from 'react-router-dom';
import { createRoot } from 'react-dom/client';
import { StrictMode } from 'react';
import App from './App';
import reportWebVitals from './reportWebVitals';
import './index.css';

const container = document.getElementById('root');
const root = createRoot(container as HTMLElement);
const app = (
  <StrictMode>
    <BrowserRouter>
      <App />
    </BrowserRouter>
  </StrictMode>
);

root.render(app);

reportWebVitals();

I replaced the code in the index.js with this one, the error disappeared. Waiting for the fixes here:
import ReactDOMClient from 'react-dom/client';
import App from './App';

const container = document.getElementById('root');
const root = ReactDOMClient.createRoot(container);

root.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

A uma incoerência na propria documentação, pois o methodo createRoot não existe, inves disso usei o methodo createPortal.

You can make:  npm install react@18 react-dom@18
import React from 'react';
import * as ReactDOM from 'react-dom/client';
import App from './App';
const root = ReactDOM.createRoot(document.getElementById('root'));
root.render()
This will fix.

this work for me,
`
import { StrictMode } from 'react';
import App from './App';
import reportWebVitals from './reportWebVitals';
import { BrowserRouter } from "react-router-dom";
var ReactDOM = require('react-dom/client');
const container = document.getElementById('root');
const root = ReactDOM.createRoot(container as HTMLElement);
const app = (

);
root.render(app);
reportWebVitals();`
"dependencies": {     "@emotion/react": "^11.9.0",     "@emotion/styled": "^11.8.1",     "@fontsource/roboto": "^4.5.5",     "@mui/icons-material": "^5.6.1",     "@mui/material": "^5.6.1",     "@testing-library/jest-dom": "^5.16.4",     "@testing-library/react": "^12.1.5",     "@testing-library/user-event": "^13.5.0",     "@types/jest": "^27.4.1",     "@types/node": "^16.11.26",     "react": "^18.0.0",     "react-dom": "^18.0.0",     "react-router-dom": "^6.3.0",     "react-scripts": "5.0.0",     "typescript": "^4.6.3",     "web-vitals": "^2.1.4"   },


Document security design

Hi, in well-typed/cborg#230 I'm comparing various high-level characteristics of Haskell serialisation libraries. One aspect is security - for example I've seen several libraries reject optimisations for security reasons - 1, 2 - what tradeoffs did you make for this library?

So far, I haven't looked specifically to security issues.
If you have some specific attack/test case to suggest, I would be very interested to look into it further.
Generally speaking, I suspect that Flat should be fairly resilient to attacks for two reasons:
A) Every input is a valid value.
Consider: data TertiumDatur = False | True | Maybe
This type has only 3 valid values but in all byte-oriented serialisation protocols, it would be serialised as a byte, leaving 253 potential invalid values.
In Flat, that has an optimal bit-oriented encoding, False would be 0, True would be 10 and Maybe would be 11. There are NO invalid values that can be read in.
B) When it comes to data structures, Flat will encode them either as lists, one item at the time, or as arrays that are lists of chunks of up to 256 elements at most, making it harder to play tricks with memory.

There are two broad classes I can think of right now - invalid data attacks and resource usage attacks.
The example you gave is a short-range invalid data attack which is easy to detect - although I see no difference between having 253 invalid values that you give a DecodeFailure for, vs 1 invalid value - what do you do with b"11" in your example, for example? OTOH there are also long-range invalid attacks involving assumptions the library might make across more of the data. For example in the links above the issue was, when encoding a set as a sorted stream, during deserialisation one must check that the stream of elements is actually sorted.
Then there are also resource usage attacks, generally it shouldn't be possible to represent an extremely huge data structure in a small amount of serialised bytes, e.g. https://brhfl.com/2017/11/svg-bomb/ - the processing time and space complexity should be proportional to the size of the input. Another example is exploiting a predictable hash function of a hash table to purposefully make it run in O(n) worst-case time for every operation on every single element; one defense here would be to serialise into some predictable canonical order unrelated to the hash function, but choose the hash function non-deterministically at runtime, and deserialise the canonical ordering as if the user had called the main insertion API.

Regarding the absence of invalid values, I agree that is a minor point but it is a valid one.

In the case of TertiumDatur the decoding logic would be:
if nextBit==0
then False
else if nextBit==0
then True
else  Maybe
If nextBit then error "TooMuchData"
So there is really no way to create an invalid value, by design.
Though obviously invalid values are easy to check for also in a byte-oriented system.

Regarding the larger problem of violated assumptions in decoded data, such as sorting, I think that is useful to remind that in 'flat', as in any data formats, data transfer is, at least conceptually if not always in practice, a two steps process:
A) The original data type is mapped to a data type supported by the exchange format (e.g. a map might be mapped to  a list of tuples, or an ordered set to a simple list)
B) The exchange format type is encoded and decoded

Tipically, the exchange format type system is less expressive than the programming language where the data originates from so it cannot enforce property like sorting or hashing properties, this is entirely the responsibility of the upper language layer and, once defined at that level, could be easily ported across exchange/storage systems.
It's a bit like asking if a file system can enforce the property that haskell source files should be correctly formatted. It can't, to a file system a source file it's just a chunk of bytes.
In practice naturally, as the two steps of mapping and exchanging are conflated in the exchange format code it makes sense to ask if the conversion is dealt with correctly.
I will check to see if there are any obvious vulnerabilities in this area.

Regarding the resource usage attack based on some kind of combinatorial explosion, I guess that would require a way to create a loop by referring back to a previous point. I don't see how that could work in the context of a simple ADT encoding system as flat.

I am afraid however that flat might be vulnerable to a simpler attack: just a very long input stream that causes an out of memory error.

This is all quite interesting, and I am quite willing to investigate it further.

It would be useful to have some specific test cases, though.
If you have any concrete example of potentially vulnerable data structure in mind, that would be a great starting point.
Is your interest academic or are you selecting a safe data exchange library for some real-world application?

Great, thanks for the clarifications.

this is entirely the responsibility of the upper language layer and, once defined at that level, could be easily ported across exchange/storage systems.
It's a bit like asking if a file system can enforce the property that haskell source files should be correctly formatted. It can't, to a file system a source file it's just a chunk of bytes.

I agree with this for the low-level serialisation framework itself, though these libraries typically also contain instances for common data structures like container - e.g. flat seems to do this OK for Set, and an example of a rejected / insecure approach would be this one.

I am afraid however that flat might be vulnerable to a simpler attack: just a very long input stream that causes an out of memory error.

I think it's not the responsibility of the serialisation framework to protect against this - if the input stream is long, a higher layer can detect this and enforce a limit, e.g. by dividing the input into chunks that can be deserialised individually. However if the stream is say 4KB yet the serialisation framework expands this to use 16GB of memory, then this is not something that higher layers can easily protect against. In general I'd say a linear expansion relative to the input, is acceptable.

I guess that would require a way to create a loop by referring back to a previous point. I don't see how that could work in the context of a simple ADT encoding system as flat.

This sounds safe yes. If there is no way to refer to other parts of the ADT, then the structure must be a tree and therefore acyclic.

Is your interest academic or are you selecting a safe data exchange library for some real-world application?

I'm selecting something for real-world use cases. I'll have to look at the format detail in more depth, to come up with specific examples - I don't think it's easy to construct general concrete examples across all serialisation frameworks, although I attempted to describe some general abstract issues. But it sounds like you would treat those cases as bugs to be fixed, which is at least encouraging - e.g. the store library makes an explicit design choice not to cover such issues.

Sure, I would be glad to make 'flat' safer.
Let me know when you come up with some examples we can work on.

Feel free to reopen this issue if you want to discuss it further.


Re-add ServiceSpreadingPriority priority algorithm

Fixes #12542 by restoring the "ServiceSpreadingPriority" priority to spread based solely on the services matching a pod. Does so by reusing the SelectorSpreadPriority function with an empty controller lister (so only services are taken into account)

@gmarek

IIUC this makes services-spreading twice as important as replication controller spreading. I don't know if it's bad or not...
I must admit I still don't know what's the serialized scheduler config, but I see that if something like this is used somewhere mentioned change will break it. Is this behavior expected, i.e. that removing some "old" algorithm is not a backward compatible change?

cc @bgrant0607

@gmarek this just preserves the old algorithm behavior for anyone who had a scheduler config file that specified "ServiceSpreadingPriority" explicitly. The associated test just makes sure all the options that used to be honored via the config file still are.
In general, I prefer the new selector behavior. I can't think of a good reason someone would use both  ServiceSpreadingPriority and SelectorSpreadPriority together

@gmarek I mostly wanted your input as the author of the SelectorSpreadPriority algorithm... will an empty ControllerLister give us equivalent behavior to the old ServiceSpreadingPriority algorithm?

@liggitt I may be wrong, but doesn't putting it in defaults.go with weight 1 enable it by default?

@liggitt I may be wrong, but doesn't putting it in defaults.go with weight 1 enable it by default?

you're right. moved to init() to register but not include in defaultPriorities()

Thanks. LGTM

@gmarek Think of the configuration file as an API. Really we should treat all component configuration similarly. If we change any configuration fields or command-line flags, we break everyone's customized cluster turnup implementations that were depending on removed features.

@k8s-bot ok to test

Both shippable and Jenkins looks like flakes (or broken head).

LGTM
Thanks for fixing, sorry for the oversight.

Shippable is failing while trying to verify gendocs. Rebase should fix the problem. Could you do it?

It was a broken head. Pinged CJ about it last night. I think it should be fixed now, so I'm going to rerun shippable.

tests look good. @davidopp any other comments?

@k8s-bot ok to test

@k8s-bot test this [testing build queue, sorry for the noise]

Automatic merge from SubmitQueue


better convergence criteria in preset passmanagers

What is the expected enhancement?
 The reason is that it internally repeats the optimization loop until circuit depth stays constant. However it should care about circuit size too.
To reproduce the circuit:
OPENQASM 2.0;
include "qelib1.inc";
qreg q[8];
cx q[1],q[2];
cx q[2],q[3];
cx q[5],q[4];
cx q[6],q[5];
cx q[4],q[5];
cx q[3],q[4];
cx q[5],q[6];
cx q[5],q[4];
cx q[3],q[4];
cx q[2],q[3];
cx q[1],q[2];
cx q[6],q[7];
cx q[6],q[5];
cx q[5],q[4];
cx q[7],q[6];
cx q[6],q[7];

Hey @ajavadia, I was a bit new to Transpiler optimization but would love to work on this issue. Is there any good starting point to learn how CX cancellation works, before diving into the code?

@kdk, would specific benchmarking be needed before this change can be added to the transpiler? I was thinking that searching over an additional optimization for the size of the circuit would have some kind of time overhead.

Additional benchmarking is good - we already have it running at https://qiskit.github.io/qiskit/, so you can see things there.  It doesn't hurt to run asv locally - the benchmarks are in the Qiskit/qiskit repo, and you can use asv dev to test your commit against the main branch.  You'll likely want to read up on its docs so you can limit the benchmarking to only the suites you care about; the whole suite takes quite a long time to run.
Some performance regression is acceptable here, provided that the "track" benchmarks improve; it's ok if we're taking a little bit more time, but getting better results (within reason - that's why we have different levels as well).

The benchmarking results we'd need to look at first are the ones that are marked time_ for the same sorts of transpiler benchmarking, and given that we care about depth as well as size, we might want to add duplicates of track_depth to track_size as well

This is spot on. I wouldn't expect the timing to be too much at risk here, the overhead of a size check should be small, and the time-cost of extra runs through the optimization loop should be offset by the improved circuit output, but I suppose we can see what comes back from the existing benchmarks after this merges.

(I don't think asv allows us to track more than one thing off the same benchmark run, but that's worth trying as well).

There's an open feature request for this ( https://github.com/airspeed-velocity/asv/issues/543 ) but our approach to date has been to duplicate the benchmark for each metric we'd like to track.


How to manually trigger a resize?

We're using custom fonts in our app that might take a bit for them to load. When they've successfully been rendered, react-textarea-autosize does not automatically resize.
In version 7, we could simply call _resizeComponent() to force an update. This is no longer possible in version 8.
// Version 8.3.2
import TextareaAutosize from 'react-textarea-autosize';
import React = require('react');

class NoteComponent extends React.Component {
    private _contentTextArea: HTMLTextAreaElement;

    constructor(props) {
        super(props);
    }

    componentDidMount() {
        // Wait for the fonts to finish rendering and then trigger a resize.
        setTimeout(() => {
            this._contentTextArea._resizeComponent(); // Not working.
        }, 500);
    }

    render () {
        return <TextareaAutosize ref={n => this._contentTextArea = n} />
    }
}

What's the official way of triggering an update / resize?

You could trigger a rerender with a new key

Ahh, of course! Thank you!

But it is not the same. If we change key focus will be lost.


Review PR

Description
This task bring the a problem during the last semester, since we add the project to a class at UnB, we have now a lot of PR's to be reviewed, so to have our project updated as possible, we decided to allocate a task for this.
Tasks

[x] PR's reviewed
[ ] PR's merged

Pull requests reviewed, we add some default comments in the last prs, since the students got the same error about testing and coding the project


Allow wrapping extra file meta data in HTML comment

Meta data for extra files has to be placed at the top of the
file. Since each line has to be prefixed with a # those lines are
displayed as headers when viewing markdown files on GitHub. This
commit allows hiding the meta data section in rendered markdown on
GitHub by wrapping it in an HTML comment:
<!--
# @title Some title
-->

Rest of document

Looks great, thanks @tf!


Allow units via thin-edge json

Describe the solution you'd like
Currently devices can not send unit via the thin-edge json approach. However this is needed for some use cases where the device is actively sending the unit.
Describe alternatives you've considered
Data point library does work works on platform side, however at some points  the unit should come directly from the device itself (e.g. switch mode metric <-> imperial).
Additional context

Is the unit sent along all and every data points? Or is the unit defined as metadata of the measurement source ?

There is broader discussion about thin-edge json here https://github.com/thin-edge/thin-edge.io-specs/pull/19

@mbay-SAG @mbie-sag
Is it really useful to send the unit along with each and every measurement? Or you'd rather want the ability to set/update the unit of a measurement (its metadata) either as a static configuration or as a dynamic property? Expecting the unit with every measurement would definitely be the easiest thing to implement. But wouldn't that put unnecessary burden on the end user in terms of wasted bandwidth on every measurement sent?
As an extended query, when a measurement is sent without a unit from the device, what would be the preferred behaviour?

That measurement remains unit-less?
It has the same unit as the last measurement?
Inherit the unit from some metadata associated with that measurement (assuming we support some action to set/update the unit for a measurement at a device level)?

Currently on C8Y the unit can be send, but is optional. So I would expect that if I pack the unit into my json, that it is used by the mapper. However if not, then not.
How the ui handles that is nothing that is implemented within thin-edge, is it? I personally would prefer that the ui uses the unit from the last measurement where a unit was provided but this seems to be problematic considering retentions etc.

We accidentally published docs describing this feature, though it isn't implemented. Below is the docs that can be added to the docs/src/references/mappers/c8y-mapper.md page once the implementation is done:
#### Measurement with unit

The unit is a metadata associated with measurements which can be registered as a metadata message for a given measurement type.
If the following metadata message is registered for the `environment` measurement type:

```sh te2mqtt formats=v1
tedge mqtt pub -r te/device/main///m/environment/meta '{
  "units": {
    "temperature": "°C"
  }
}'

Then subsequent messages will be mapped with the registered unit value as follows.

%%te%% (input)
te/device/main///m/environment

{
  "temperature": 23.4
}

Cumulocity IoT (output)
c8y/measurement/measurements/create

{
  "type": "environment",
  "time": "2021-04-22T17:05:26.958340390+00:00",
  "temperature": {
    "temperature": {
      "value": 23,
      "unit": "°C"
    }
  }
}


System.Collections.Generic.KeyNotFoundException

https://github.com/dotnet/SqlClient/blob/main/src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/SqlConnectionPoolGroupProviderInfo.cs#L107
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary。
    at TValue System.Collections.Generic.Dictionary<TKey, TValue>.get_Item(TKey key)
    at PermissionSet Microsoft.Data.SqlClient.SqlConnectionPoolGroupProviderInfo.CreateFailoverPermission(SqlConnectionString userConnectionOptions, string actualFailoverPartner)
    at void Microsoft.Data.SqlClient.SqlConnectionPoolGroupProviderInfo.FailoverCheck(bool actualUseFailoverPartner, SqlConnectionString userConnectionOptions, string actualFailoverPartner)
    at void Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, string newPassword, SecureString newSecurePassword, bool redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
    at void Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, string newPassword, SecureString newSecurePassword, bool redirectedUserInstance)
    at new Microsoft.Data.SqlClient.SqlInternalConnectionTds(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, object providerInfo, string newPassword, SecureString newSecurePassword, bool redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, ServerCertificateValidationCallback serverCallback, ClientCertificateRetrievalCallback clientCallback, DbConnectionPool pool, string accessToken, SqlClientOriginalNetworkAddressInfo originalNetworkAddressInfo, bool applyTransientFaultHandling)
    at DbConnectionInternal Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
    at DbConnectionInternal Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
    at DbConnectionInternal Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptionsuserOptions, DbConnectionInternal oldConnection)
    at DbConnectionInternal Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
    at bool Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, uint waitForMultipleObjectsTimeout, bool allowCreate, bool onlyOneCheckConnection, DbConnectionOptions userOptions, out DbConnectionInternal connection)
    at void Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen()

What is your connection string?

data source=<IP_ADDRESS>;initial catalog=BetaUserConfig_DB;user id=BetaUserConfig_DB_Admin;password=xxxxx;TrustServerCertificate=true;

That looks like a valid connection string, and I tried a similar connection string and it ran through successfully without an issue. However, the code indicated where the exception was thrown shows that FailOverPartner key doesn't exist in the SqlConnectionString, which sounds similar to this https://github.com/dotnet/SqlClient/issues/1594 issue where by setting the FailoverPartner to an empty string, it'll will get around this.

@pengweiqhca what version of SqlClient are you using?

@pengweiqhca what version of SqlClient are you using?

4.1.0

I'm also hitting this (or rather a customer of ours is). We are using Microsoft.Data.SqlClient 4.1.0. The connection string is Data Source=XXXXX;Initial Catalog=XXXXX;Integrated Security=True;Pooling=False;Trust Server Certificate=True;Application Name="Red Gate Software - SQL Tools"

@pengweiqhca @mark-raymond could try out the fix in the PR #1614 and see if it resolves your issue.  The PR is tagged in the upcoming release, but I don't have the test environment with a server with AG to verify it before it can be merged.

The pipeline generated the nuget package from the PR which you can download from here: https://sqlclientdrivers.visualstudio.com/904996cc-6198-4d39-8540-eca72bdf0b7b/_apis/build/builds/51479/artifacts?artifactName=Artifacts&api-version=7.0&%24format=zip

@pengweiqhca and @mark-raymond could you verify it with the provided NuGet, please?

Ah, the issue was hit by a customer of ours, I don't actually have access to the environment myself to test against.


The configuration for the "user" component must contain a "class" element.

User is configured as an application component in [[\yii\web\Application]] by default.

When I configurated this component inside module then i get error -
The configuration for the "user" component must contain a "class" element.
class RestModule extends Module
{
    public function init()
    {
        parent::init();

        \Yii::configure($this, require(__DIR__ . '/config/main.php'));
    }

//config for Module
return [
    //....
    'components' => [
        'user' => [
            'identityClass' => 'rest\versions\v1\models\User',
            'enableSession' => false,
        ],
    ],
];

Config works fine for application
 'components' => [
        'user' => [
            'identityClass' => 'common\models\User',
        ],
    ],

I suppose you got this error when you were trying to migrate or to do something using the console, it is true that Yii add the class automatically in your component configuration and the user is indeed defined as such, but that only applies for applications based on a web\Application.
I also suppose you are using a custom user configuration and you added it to the config files under the common\ folder. Correct me if I am wrong!
Given that common is used by both by the console and the web part of the application, Yii is working correctly but indeed getting an invalid configuration.
Simply moving the user configuration to the config files ones under frontend (or whatever folder contains your web accessible structure) should solve the issue.

Thank you Anini. That was exactly my problem. I putted it in to common config to use it in frontend and backend application.

ffg

I also got this error
Exception 'yii\base\InvalidConfigException' with message 'The configuration for the "user" component must contain a "class" element.'
Please help me


changes made to title

changed the title to windows 10 and changed the logo

Thanks man thought you would ignore
On Sat, 12 Oct, 2024, 12:00 am Chetan Khulage, @.***>
wrote:

Merged #20 https://github.com/Chetan-KK/Windows-10-Clone/pull/20 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/Chetan-KK/Windows-10-Clone/pull/20#event-14612857085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCGIFSW56JHXBMZ2XLYNGH3Z3AKMVAVCNFSM6AAAAABPH4VE3KVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGYYTEOBVG4YDQNI
.
You are receiving this because you authored the thread.Message ID:
@.***>


How to describe rotations

From #183 it came up that we need to decide how we want to describe rotations.

Oops, I wasn't very careful about the fact that the order of matrix multiplication matters. We need to choose whether we want to use intrinsic or extrinsic rotation, what order, etc.
Alternatively, we could forego all this subtlety by using the axis-angle formalism. Thoughts?

Edit: IMO quaternions are the best way to do this. Very efficient. I'll change this class to ConstrantRotationZ that just has Omega_z and makes life easy for the common case. We can do general rotations in a followup.

Ping @adrn @jnibauer

Unfortunately JAX won't be doing (/deprecated) a scipy-like Rotation object.
We either need to implement our own (not so hard structurally because of equinox, but careful mathematics) or ensure that the Array API support in Scipy means we can just use SciPy (that would be sooo nice) — see https://github.com/scipy/scipy/releases/tag/v1.14.0rc1.


Where is ChatMemberUpdated?

Expected behavior
When i handle newChatMembers, I want to know the invite link the user use
Actual behavior
I find a class name ChatMemberUpdated in other SDK and in this pr https://github.com/kotlin-telegram-bot/kotlin-telegram-bot/pull/236, but not in the latest version

Added on https://github.com/kotlin-telegram-bot/kotlin-telegram-bot/pull/301


AMD Media - Fix FFmpeg swscale error when using hwdec for amd_media

The error was most likely triggered when updating FFmpeg version.
For VAAPI- ffmpeg returns wrong pix_format which was causing failure in swscale.

For #1305

Test Passing with pr
runvx 1.0.0
OK: using AMD OpenVX 1.3.0
OK: loaded 2 kernels from libvx_amd_media.so
VAAPI device created for device /dev/dri/renderD128 and stream 0
INFO: reading 2048x1024 into slice#0 from /home/kiriti/develop/mivisionx-kiriti/MIVisionX/data/videos/AMD_driving_virtual_20.mp4
csv,HEADER ,STATUS, COUNT,cur-ms,avg-ms,min-ms,clenqueue-ms,clwait-ms,clwrite-ms,clread-ms
csv,OVERALL,  PASS,     1,      , 50.37, 50.37,  0.00,  0.00,  0.00,  0.00 (median 50.370)
> total elapsed time:   0.05 sec
Average Decode Time per frame (ms): 0.792564
Average Transfer Time per frame (ms): 12.6994


Handle cases where kube auth requires exec'ing unavailable command

This happens when it uses 'aws' for example but it's not available from IDE's PATH.

Tried to do something like
#[cfg(not(feature = "incluster"))]
fn resolve_exec_command(command: &str) -> Option<String> {
    // use default shell to run which and get the path of the command
    // the idea is if there's shell profile/bashrc/zshrc that sets the PATH, we can
    // use that to resolve the command
    let shell = which::which("$SHELL")
        .inspect_err(|err| tracing::debug!("failed resolving shell {err:?}")).ok()?;

    let output = std::process::Command::new(shell)
        .arg("-c")
        .arg(format!("which {command}"))
        .output()
        .inspect_err(|err| tracing::debug!("failed running which command via shell {err:?}")).ok()?;

    let resolved_command = String::from_utf8(output.stdout)
        .inspect_err(|err| tracing::debug!("failed parsing which command output {err:?}")).ok()?;
    if resolved_command.is_empty() {
        None
    } else {
        tracing::debug!("resolved {resolved_command}");
        Some(resolved_command)
    }
}

but that didn't work 😢


fix(tap-agent): EIP712 domain separator name

Quick fix before we update to a more recent version of tap-core that provides a single source of truth for the EIP-712 domain separator.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-1 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.178%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tap-agent/src/agent.rs
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2445

Relevant Lines:
3870

💛  - Coveralls


Importing Problem

When I import this in dependencies it gives me this error
[image_editor_pro] flutter pub get
Running "flutter pub get" in image_editor_pro...
Error on line 31, column 3 of pubspec.yaml: A package may not list itself as a dependency.

   ╷

31 │   image_editor_pro:

   │   ^^^^^^^^^^^^^^^^

   ╵
pub get failed (65;    ╵)
exit code 65

@shubhamhhum show all your pubspec.yaml, yaml file is sensitive on spaces.

I did this issue long ago. At that time I was learning flutter. This problem may have happened due to my internet connection. Now I have also deleted that project. It is working now.


require.resolveWeak is not parsed in ESM packages

Bug report
What is the current behavior?
In packages with type: "module", webpack fails to parse and replace require.resolveWeak() expressions.
If the current behavior is a bug, please provide the steps to reproduce.

Clone https://github.com/johndiiorio/webpack-require-resolveWeak
Run npm install
Navigate to both ./cjs and ./esm and run npm run build from within each directory.
Notice that in ./cjs/dist/bundle.js, the require.resolveWeak call was replaced, but was not in ./esm/dist/bundle.js.

What is the expected behavior?
The replacement was successful regardless of the type.
Other relevant information:
webpack version: 5.72.0
Node.js version: 17.9.0
Operating System: Arch Linux 5.17.1-arch1-1
Additional tools: n/a
This appears to be similar to #15372, as mentioned here.

this done intentionally since in esm there is no require, you should not use type: "module" for this module.. You can fix this using webpack.config e.g. setting type in module.rules:
module.exports = {
   module: {
      rules: [{ type: "javascript/auto" /* you can add test property here */ }]
   }
};


Malformatted CLI output

System:

OS: Windows 7
CPU: x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Memory: 9.43 GB / 15.67 GB

Binaries:

Yarn: 1.6.0 - D:\Program Files\Yarn\bin\yarn.CMD
npm: 5.3.0 - C:\Program Files\nodejs\npm.CMD

Steps to reproduce
Run warriorjs on first stage
Expected Behavior
Output on terminal should look correct
Actual Behavior
Output does not look correct

Hello @TheHolyWaffle, thanks for reporting this bug. I couldn't reproduce it. I wonder if it has to do with the diamond character next to the score being broken on Windows (for which I created #112).
Now, for me to be able to troubleshoot this, I'd need to know:

Did this break in level 2 or was also broken in level 1?
What's the code in Player.js?

Thanks!

Same problem here. And I think it broke in every level.

I'm using the integrated terminal of visual studio code.
I'm not in my office right now so I will test the character issue later.

Ok I've found a working solution, the text is now displaying and animating properly.
Can someone using Windows test it ?
In C:\Users\*username*\AppData\Roaming\npm\node_modules\@warriorjs\cli\lib\ui
or C:\Users\*username*\AppData\Roaming\npm\lib\ui
Open printBoard.js and change line 25 :
const warriorStatusRows = 2;
to
const warriorStatusRows = 4;

Hey @Eveneit! Thanks for the efforts you're putting on this. I think I know what's going on thanks to you, and I'm working on a fix. I'll let you know when it's done and, if you could test it, that'd be awesome!

@Eveneit the possible fix was pushed to #120.

It works like a charm. 😂

@jack45j Which one: @Eveneit's fix or #120? The former is a valid workaround, but is not a fix because it'll break those platforms where this is working correctly. #120 is potentially a fix for everyone, but I'd need confirmation from someone experiencing this issue.

The @Eveneit's fix. I changed warriorStatusRows to 4 and the output issue just solved on windows7. But I thought the key point occurs this issue is not caused by this variable.

Hey @Eveneit, looking at #134 it looks like #120 fixed this issue. Can you please confirm that so I can close this? Thanks!

@olistic Yes it did, the game is working alright on Windows since you merged #print-row-refactor !


Implement test mode

Before running we need to check if everything is working.
For example,

ability to write to tmp dir
connection to telegram api
access to zabbix web ui

Tmp dir creates with chmod 777.
--debug option is enough.


Improve exception handling for writers

UserExceptions are expected to be informative enough for the final user to make easier the support for our toolkit. This commit fix some bugs in this exception handling by:

Use a more consistent error message for failing opening a writer. While an exception occur, previous implementation called java.nio.Path#toFile, causing a NPE in the case of HDFS paths (for example). This is fixed by using a method which encapsulate the logic for handling this errors: it uses the URI string, the name of the exception and the message produced.
Closing the writers throws if they cannot be closed. We were using ClosingUtils#close for out writers at the end of our tools, but this is wrong because any IOException will be silent. In the case of a failure happens while closing, we should warn the user somehow. Thus, there is a new method for achieving this in ReadWriterFactory, which is used in the tool #close method.

Note: this commit adds Mockito as dependency for testing.
Closes #163 and partially solving #106

Ready to go when test pass!


Fix a stray file called "secondpr"

There is a stray file, can someone make it into correct section.

Added my comments here: https://github.com/twindle-co/twindle/pull/217#discussion_r506852002

Where to move it any suggestion?

If it needs to go into faq or somewhere else please contact relevant people to ask

I will contact them when I get free time.

@pranavgoel29 go ahead and raise a pr deleting it?

ok I am doing that


The command to changing the install path in the document does not work on Windows

I attempted to follow the instructions in the document to changing the install path using the following command, but encountered an error on a Windows system.
$env:UV_INSTALL_DIR = "C:\Custom\Path" powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

in PowerShell 7:
ParserError:
Line |
   1 |  $env:UV_INSTALL_DIR = "C:\Custom\Path" powershell -ExecutionPolicy By …
     |                                         ~~~~~~~~~~
     | Unexpected token 'powershell' in expression or statement.

in Windows PowerShell:
所在位置 行:1 字符: 40
+ $env:UV_INSTALL_DIR = "C:\Custom\Path" powershell -ExecutionPolicy By ...
+                                        ~~~~~~~~~~
表达式或语句中包含意外的标记“powershell”。
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

Although I'm not sure if this method(https://github.com/astral-sh/uv/pull/9507) will be accepted, at least it can solve your current problem.
 $env:UV_INSTALL_DIR = "C:\Custom\Path"; powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Although I'm not sure if this method(#9507) will be accepted, at least it can solve your current problem.
$env:UV_INSTALL_DIR = "C:\Custom\Path"; powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Thank you, that resolved my issue.


Update projects to target SignalR 5.0

I've combined this with the freemods PR to avoid some weird version conflicts (test projects aren't explicitly referencing SignalR so required an osu.Game update to work... but osu.Game update requires code changes in freemods branch).


buttonDefaultText is not Working

@dotansimha,
I have provided buttonDefaultText on my dropdown configs, but it is not executing provided custom text on button.
here's my extra settings, which I'm passing on dropdown.
`dynamicTitle: false,
buttonDefaultText: "Columns",`
on this, i assume that button have to display Projects whatever happens, if any value of dropdown is selected or not.

This is working fine for me,
Remember that buttonDefaultText is a property of translation-texts and not of extra-settings


Email Client Support ?

This does not work on many email clients. SVG is hardly supported, and base64 inline png's is hit or miss. The following is based on using the png3x() function
Breaks on Gmail (Chrome), Inbox by Gmail, Outlook on Windows (2013 and 2016), Android 6.0, AOL Mail (Explorer - adds a border)
Works on iPhone, iPad, Apple Mail 10 & 11, Outlook.com (Explorer),
There's a good 1/3 email users that this does not work with according too https://emailclientmarketshare.com/
Maybe we should just use old remote url png's and stop base64 in lining them? Building emails that work on this ancient email clients is the worse head-ache ever

you need to use the nodemailer base64tos3 plugin
im going to enforce it in the next release
On Nov 1, 2017 4:48 PM, "Michael Lage"<EMAIL_ADDRESS>wrote:

This does not work on many email clients. SVG is hardly supported, and
base64 inline png's is hit or miss. The following is based on using the
png3x() function
Breaks on Gmail (Chrome), Inbox by Gmail, Outlook on Windows (2013 and
2016), Android 6.0, AOL Mail (Explorer - adds a border)
Works on iPhone, iPad, Apple Mail 10 & 11, Outlook.com (Explorer),
There's a good 1/3 email users that this does not work with according too
https://emailclientmarketshare.com/
Maybe we should just use old remote url png's and stop base64 in lining
them? Building emails that work on this ancient email clients is the worse
head-ache ever
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ladjs/font-awesome-assets/issues/6, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAf7hdG_UPq-527CmsJEd_-5XNSpmeX-ks5syNkagaJpZM4QOzMe
.

closing because the solution already exists https://github.com/ladjs/nodemailer-base64-to-s3


Is it relative precision or error?

In scipy.linalg.interpolative, the statement of line 831 and line 852 is opposite. Which one is correct? Could you unify the meanning of eps_or_k in all of SVD.

The SVD can be computed to any relative precision or rank (depending on the
value of `eps_or_k`).

and
eps_or_k : float or int
    Relative error (if `eps_or_k < 1`) or rank (if `eps_or_k >= 1`) of
    approximation.

I don't see those as opposite. Can you explain your question in more detail?

Dear @rgommers
Please read scipy.linalg.interpolative line 851 and scipy.linalg._interpolative_backend line 452, the same value, however, it is opposite statement.

"Relative error" and "Relative precision" mean the same thing.

Line 452 in _interpolative_backend.py:
:param eps:
    Relative precision.

(it would be helpful to include code, line numbers change over time and saves us work)
Those do mean the same thing. There's no issue, so closing.


Shining up README and adding full reference

People googling the paper title might find it useful to have the github repo show up in the search results

Thanks! This is very helpful. (The one slight change I made is to remove the "pip install" comment, since the Pypi version of TICC is the "blackbox" branch, rather than the "master" branch). But other than that, it looks great!


flaky create action when using a custom SessionsControllers

Somebody else already wrote a nice stackoverflow question: http://stackoverflow.com/questions/7740706/devise-401-return-on-correct-login-with-custom-sessions-controller
I already started debugging the problem:
It seems like strategy.valid? does return nil in lib/warden/proxy.rb:308 when instead it should indicate success.
devise: 1.5.0, warden: 1.1.0

in my case the sessions/new view was constructed incorrectly leading to a wrong params layout


There's no "modal" prop in the Select component

I couldn't make the Select component "non-modal"

Seconding this. Came across this issue upon noticing the scrollbar shift: https://github.com/radix-ui/primitives/discussions/1586

Any solutions? When I click select, the elements inside my sticky header navbar shift because the scrollbar disappears.

@LeonLiu2020 Could you provide a screenshot

+1. This seems like the same issue (with the same solution) as for DropdownMenu.  The inability to set modal=false for Select means that scroll bars always disappear when a Select is active. This might make sense in some contexts, but it can be jarring in others.  It would be great to have the option to disable this behavior.

@LeonLiu2020 @jhawson @patriciatiffany Ariakit is the best alternative for Radix now try it.


Backport "Attempt implicit search for old style implicit parameters in Application matchArgs"

Backports #19737 to the LTS branch.
Fixes #19594
This prevents munit from updating to Scala 3.3.x: https://github.com/scalameta/munit/issues/565

Really hope this will be backported - unblocking 3.3 on MUnit in turn unblocks several other libraries that have already moved on to LTS, and in turn unblocks Scala Native 0.5.0 upgrades (the chain is long, yeah)

I've started the Open CB to check how it affects other projects.

We've not found any new regressions in the Open CB related to this PR.

It was backported in https://github.com/scala/scala3/pull/20936 and released in 3.3.4
We must have missed this PR for manual backport, but we handled it based on the LTS backports queue


Update ratings-and-reviews.md

Updating based on current rating logic in Store. The number of ratings in Store is currently equal to the number of most recent ratings. This will be changed to lifetime count of ratings in future.

@IpsitaChoudhary : Thanks for your contribution! The author(s) have been notified to review your proposed change.