Make @measure more flexible

Made it so things like this now work:
julia> using MeasureTheory

julia> using MacroTools

julia> using StatsFuns

julia> @measure MvNormal(μ,Σ) ≃ (1/sqrt2π^length(μ)) * Lebesgue(Real)^size(μ);

julia> prettify(@macroexpand @measure MvNormal(μ,Σ) ≃ (1/sqrt2π^length(μ)) * Lebesgue(Real)^size(μ))
quote
    struct MvNormal{P} <: MeasureTheory.AbstractMeasure
        par::P
    end
    function MvNormal(nt::NamedTuple)
        P = typeof(nt)
        return MvNormal{P}(nt)
    end
    MvNormal(; kwargs...) = MvNormal((; kwargs...))
    function MeasureTheory.basemeasure(μ::MvNormal{P}) where P
        return (1 / sqrt2π ^ length(μ.par.μ)) * Lebesgue(Real) ^ size(μ.par.μ)
    end
    MvNormal(μ, Σ) = MvNormal(; μ, Σ)
end

julia> μ = randn(3);

julia> Σ = let x = randn(10,3)
           x' * x
       end;

julia> basemeasure(MvNormal(μ, Σ))
MeasureTheory.ScaledMeasure{Float64,PowerMeasure{Lebesgue{Real},1}}(-2.7568155996140185, PowerMeasure{Lebesgue{Real},1}(Lebesgue{Real}(), (3,)))

Currently I'm just escaping the whole thing, we'll need another pass once we have it working properly to make things more hygienic.

Codecov Report

Merging #18 into master will increase coverage by 6.42%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage    8.57%   15.00%   +6.42%
==========================================
  Files          16       16
  Lines         140      140
==========================================
+ Hits           12       21       +9
+ Misses        128      119       -9

Impacted Files
Coverage Δ

src/combinators/power.jl
0.00% <ø> (ø)

src/probability/normal.jl
0.00% <ø> (ø)

src/macros.jl
83.33% <100.00%> (+37.50%)
:arrow_up:

Continue to review full report at Codecov.

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


Error on running project

Hi
Thanks for the wonder full boiler plate combo.
I have cloned the boiler plate in my local.
Then i have given npm install.
npm run start:dev
In this point I am getting error as below screenshot
Please help me to get fix this
Branch:master

Hi @prakash-ar ,
We have stopped developing the next-boilerplate project. You can create a nextjs project with the same features using superplate.


create melee role for invader core removal

This should spawn on demand for cores, probably not worth bothering to send to multiple rooms, especially bc cores can respawn very quickly sometimes

new role brick is has been created, but still needs to be spawned by the room. Also should be able to attack creeps during free time


[Bug] Crash when dattempting to deconstruct ghosts

When you are trying to deconstuct a mixed ghost/real railway, the map crashes

thanks for the report, I'll take a look into that

fixed with 00ae839a5e10e41b5d19d5c6ea53261aec43adfc.
do note that unfortunately deconstruction/deletion of ghosts is not supported due to limitations.
I could work around it but that would be very hacky and pretty complex :/


Inline getattr for dask.delayed objects

When using methods with Delayed values, a task is first created for
the attribute access, and a second task is created for the method call.
While the scheduler overhead of doing two tasks is minimal, this causes
problems when using delayed with distributed/multiprocessing, as methods
aren't necessarily pickleable. To fix this, we inline all calls to
getattr (which should also improve performance, since these calls are
cheap).

A second option would be to create another class DelayedAttr, which special cases __call__ (similar to DelayedLeaf. This seemed like the cheaper option though.

Seems good to me.  As an FYI I found inline_functions to be surprisingly expensive in dask.array

I don't expect graphs to get too huge when using delayed objects - if this becomes overly expensive we can always rewrite using the second option above.

I've definitely made huge graphs with delayed objects, but yes, I agree that waiting until this is a demonstrable issue seems ideal.


Xk: add new projects

@Jomula, is the status quo that CI fails on every one of these PRs because the JSON validation workflow needs to be updated?

I will try to take care of it this week

I was also looking into it. Just haven't had much time lately due to conferences/workshops.

It´s working now :D


New version: stevencohn.OneMore version 4.1

- [ ] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

Duplicate #26123


[BUG] labelColor when rendering an array of labels is not working

Expected Behavior

When returning an array  of objects from labelColor on tooltips.callbacks, the squares should get the colour returned from the function.
Current Behavior

When returning an array from labelColor on tooltips callbacks, all squares appear black.
Possible Solution

N/A
Steps to Reproduce (for bugs)

http://jsbin.com/xuqalax/edit?html,js,output
Context

I was trying to add thousand separators, and for that I needed to edit the label callback on tooltips. I then realized I would also need to override labelColor in order to get the previous behaviour, but it didn't work as expected.
Environment

Chart.js version: 2.5.0
Browser name and version: Google Chrome Version 56.0.2924.87 (64-bit)

@brenolf the labelColor tooltip is called for each item in the tooltip already, so no need to return an array. See http://jsbin.com/rezecuzeju/1/edit?html,js,output

This is still an issue, I believe. If you return an array in the label callback, it makes multiple labels, but there is no way to define multiple colors. They all have to be the same color.

I'm also experiencing this same issue, all label colours are the same even though I am specifying an array of different colours.

Not sure if you guys are still looking for it but here what worked on my end
            ```

tooltips: {
mode: 'index',
intersect: false,
callbacks: {
label: function(tooltipItem, data) {
var val = (data.datasets[tooltipItem.datasetIndex].data[tooltipItem.index] != '') ? data.datasets[tooltipItem.datasetIndex].data[tooltipItem.index] : 'N/A';
var ctg = data.datasets[tooltipItem.datasetIndex]['label']
return ctg + ' : ' + val;
},
}
},

pls tell if there is any solution or work around for the aforementioned issue?


sfAutoload include fix for HHVM support

fixes the 2 dubious tests, hhvm is not likely to fix this issue soon :(

Linked to https://github.com/facebook/hhvm/issues/1447

Now only APC is failing, that's great ! :+1:

Thanks, good job !


Dark Mode

Description
Dark mode for the 3bot admin panel

A toggle button in the header (Dark mode)

Verified


Dataset Error: DaNE contains empty samples at the end

The dataset DaNE, contains empty samples at the end. It is naturally easy to remove using a filter but should probably not be there, to begin with as it can cause errors.
>>> import datasets
[...]
>>> dataset = datasets.load_dataset("dane")
[...]
>>> dataset["test"][-1]
{'dep_ids': [], 'dep_labels': [], 'lemmas': [], 'morph_tags': [], 'ner_tags': [], 'pos_tags': [], 'sent_id': '', 'text': '', 'tok_ids': [], 'tokens': []}
>>> dataset["train"][-1]
{'dep_ids': [], 'dep_labels': [], 'lemmas': [], 'morph_tags': [], 'ner_tags': [], 'pos_tags': [], 'sent_id': '', 'text': '', 'tok_ids': [], 'tokens': []}

Best,
Kenneth

Thanks for reporting, I opened a PR to fix that

Thanks for reporting, I opened a PR to fix that

One the PR is merged the fix will be available in the next release of datasets.
If you don't want to wait the next release you can still load the script from the master branch with
load_dataset("dane", script_version="master")

One the PR is merged the fix will be available in the next release of datasets.
If you don't want to wait the next release you can still load the script from the master branch with
load_dataset("dane", script_version="master")

If you have other questions feel free to reopen :)

If you have other questions feel free to reopen :)


Failed to bring up Control Plane: Failed to verify healthcheck: Service [kube-apiserver] is not healthy

My infrastructure:
Ubuntu 16.04 xenial servers ( kernel: 4.4.0-119-generic )
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.4 LTS
Release:	16.04
Codename:	xenial

docker-ce: 17.03.2
rancher/server: rancher/server:preview
rancher/agent: rancher/agent:v2.0.0-beta3
kubernetes version: v1.9.5-rancher1-1
network provider: flannel
ingress provider: Nginx
everything else by default
Hello, i'm trying to deploy k8s cluster via Rancher following this manual: https://rancher.com/docs/rancher/v2.0/en/quick-start-guide/#create-a-cluster
I have a single node Rancher server in docker. Rancher's server container log hasn't any errors and Rancher's UI works. I use custom cluster definition as it described above, but i can't deploy any k8s node...kube-apiserver on controlplane node continuously falls down with errors:
E0413 09:24:46.749507       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Namespace: the server was unable to return a response in the time allotted, but may still be processing the request (get namespaces)
E0413 09:24:46.750234       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/apiextensions-apiserver/pkg/client/informers/internalversion/factory.go:73: Failed to list *apiextensions.CustomResourceDefinition: the server was unable to return a response in the time allotted, but may still be processing the request (get customresourcedefinitions.apiextensions.k8s.io)
E0413 09:24:46.750300       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.ClusterRoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterrolebindings.rbac.authorization.k8s.io)
E0413 09:24:46.750369       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.ResourceQuota: the server was unable to return a response in the time allotted, but may still be processing the request (get resourcequotas)
E0413 09:24:46.750415       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/kube-aggregator/pkg/client/informers/internalversion/factory.go:73: Failed to list *apiregistration.APIService: the server was unable to return a response in the time allotted, but may still be processing the request (get apiservices.apiregistration.k8s.io)
E0413 09:24:46.751444       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: the server was unable to return a response in the time allotted, but may still be processing the request (get services)
E0413 09:24:46.753077       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.ServiceAccount: the server was unable to return a response in the time allotted, but may still be processing the request (get serviceaccounts)
E0413 09:24:46.753173       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Endpoints: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints)
E0413 09:24:46.754624       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.Role: the server was unable to return a response in the time allotted, but may still be processing the request (get roles.rbac.authorization.k8s.io)
E0413 09:24:46.754805       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.Secret: the server was unable to return a response in the time allotted, but may still be processing the request (get secrets)
E0413 09:24:46.755014       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.ClusterRole: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
E0413 09:24:46.755092       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.Pod: the server was unable to return a response in the time allotted, but may still be processing the request (get pods)
E0413 09:24:46.756484       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.RoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get rolebindings.rbac.authorization.k8s.io)
E0413 09:24:46.757642       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.PersistentVolume: the server was unable to return a response in the time allotted, but may still be processing the request (get persistentvolumes)
E0413 09:24:46.758085       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.LimitRange: the server was unable to return a response in the time allotted, but may still be processing the request (get limitranges)
E0413 09:24:46.759325       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *storage.StorageClass: the server was unable to return a response in the time allotted, but may still be processing the request (get storageclasses.storage.k8s.io)
E0413 09:24:47.716763       1 storage_rbac.go:175] unable to initialize clusterroles: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
I0413 09:25:17.717900       1 trace.go:76] Trace[1939526606]: "Create /api/v1/namespaces" (started: 2018-04-13 09:24:47.717319731 +0000 UTC m=+65.801015337) (total time: 30.000544445s):
Trace[1939526606]: [30.000544445s] [30.000362502s] END
E0413 09:25:17.718427       1 client_ca_hook.go:78] Timeout: request did not complete within allowed duration
E0413 09:25:47.717979       1 storage_rbac.go:175] unable to initialize clusterroles: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
F0413 09:25:47.718008       1 hooks.go:188] PostStartHook "rbac/bootstrap-roles" failed: unable to initialize roles: timed out waiting for the condition

My etcd logs:
$ docker logs -f etcd
2018-04-13 09:01:02.355136 I | etcdmain: etcd Version: 3.1.12
2018-04-13 09:01:02.355247 I | etcdmain: Git SHA: 918698add
2018-04-13 09:01:02.355255 I | etcdmain: Go Version: go1.8.7
2018-04-13 09:01:02.355271 I | etcdmain: Go OS/Arch: linux/amd64
2018-04-13 09:01:02.355279 I | etcdmain: setting maximum number of CPUs to 2, total number of available CPUs is 2
2018-04-13 09:01:02.355479 N | etcdmain: the server is already initialized as member before, starting as etcd member...
2018-04-13 09:01:02.355513 I | embed: peerTLS: cert = /etc/kubernetes/ssl/kube-etcd-192-168-168-211.pem, key = /etc/kubernetes/ssl/kube-etcd-192-168-168-211-key.pem, ca = , trusted-ca = /etc/kubernetes/ssl/kube-ca.pem, client-cert-auth = true
2018-04-13 09:01:02.357126 I | embed: listening for peers on https://<IP_ADDRESS>:2380
2018-04-13 09:01:02.357269 I | embed: listening for client requests on <IP_ADDRESS>:2379
2018-04-13 09:01:02.361323 I | warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
2018-04-13 09:01:02.361722 I | etcdserver: name = etcd-vkc-k8s-etcd01
2018-04-13 09:01:02.361740 I | etcdserver: data dir = /var/lib/rancher/etcd
2018-04-13 09:01:02.361748 I | etcdserver: member dir = /var/lib/rancher/etcd/member
2018-04-13 09:01:02.361754 I | etcdserver: heartbeat = 100ms
2018-04-13 09:01:02.361760 I | etcdserver: election = 1000ms
2018-04-13 09:01:02.362145 I | etcdserver: snapshot count = 10000
2018-04-13 09:01:02.362170 I | etcdserver: advertise client URLs = https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:4001
2018-04-13 09:01:02.363905 I | etcdserver: restarting member 3e0a251cab4ef89c in cluster dc3606aa30226616 at commit index 8
2018-04-13 09:01:02.363951 I | raft: 3e0a251cab4ef89c became follower at term 4
2018-04-13 09:01:02.364010 I | raft: newRaft 3e0a251cab4ef89c [peers: [], term: 4, commit: 8, applied: 0, lastindex: 8, lastterm: 4]
2018-04-13 09:01:02.381788 I | warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
2018-04-13 09:01:02.383423 I | warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
2018-04-13 09:01:02.383503 I | etcdserver: starting server... [version: 3.1.12, cluster version: to_be_decided]
2018-04-13 09:01:02.383554 I | embed: ClientTLS: cert = /etc/kubernetes/ssl/kube-etcd-192-168-168-211.pem, key = /etc/kubernetes/ssl/kube-etcd-192-168-168-211-key.pem, ca = , trusted-ca = /etc/kubernetes/ssl/kube-ca.pem, client-cert-auth = true
2018-04-13 09:01:02.387452 I | etcdserver/membership: added member 3e0a251cab4ef89c [https://<IP_ADDRESS>:2380] to cluster dc3606aa30226616
2018-04-13 09:01:02.387635 N | etcdserver/membership: set the initial cluster version to 3.1
2018-04-13 09:01:02.387694 I | etcdserver/api: enabled capabilities for version 3.1
2018-04-13 09:01:02.764726 I | raft: 3e0a251cab4ef89c is starting a new election at term 4
2018-04-13 09:01:02.764830 I | raft: 3e0a251cab4ef89c became candidate at term 5
2018-04-13 09:01:02.764864 I | raft: 3e0a251cab4ef89c received MsgVoteResp from 3e0a251cab4ef89c at term 5
2018-04-13 09:01:02.764891 I | raft: 3e0a251cab4ef89c became leader at term 5
2018-04-13 09:01:02.764903 I | raft: raft.node: 3e0a251cab4ef89c elected leader 3e0a251cab4ef89c at term 5
2018-04-13 09:01:02.765338 I | etcdserver: published {Name:etcd-vkc-k8s-etcd01 ClientURLs:[https://<IP_ADDRESS>:2379 https://<IP_ADDRESS>:4001]} to cluster dc3606aa30226616
2018-04-13 09:01:02.765420 I | embed: ready to serve client requests
2018-04-13 09:01:02.766108 I | embed: serving client requests on [::]:2379

Can you try cleaning the nodes and try again?  Thanks for your reply! This issue might be closed now


Update all macOS targets to 12.0

Platforms Impacted

[ ] iOS
[x] macOS

Description of changes
Some of our macOS targets were providing their own deployment overrides in their xcscheme files, which has been triggering GitHub failure checks. This removes those overrides and brings us to 12.0 across the board.
Binary change
n/a
Verification
n/a
Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Not caused by this review so feel free to split to a separate change - I totally missed that the settings for the xctest target were added directly into the .pbxproj. Should be quick enough to move to an xcconfig to prevent the duplication and over specification?


infinite-image-browsing listen <IP_ADDRESS>? (standalone ubuntu)

Is there a way to set it to listen on <IP_ADDRESS> and choose the port?
Unfortunately, localhost is not very interesting when using cloud computing.
Thanks for taking a look.

python app.py --host="<IP_ADDRESS>" --port=8888

Thanks for the swift reply.
I installed the deb file, so I figured I needed to start it with "infinite-image-browsing"
Using the git, I get this error:
sudo python3 app.py --host="<IP_ADDRESS>" --port=8888 Traceback (most recent call last):   File "/tmp/sd-webui-infinite-image-browsing/app.py", line 221, in <module>     launch_app(**vars(args))   File "/tmp/sd-webui-infinite-image-browsing/app.py", line 201, in launch_app     app = app_utils.get_root_browser_app()   File "/tmp/sd-webui-infinite-image-browsing/app.py", line 142, in get_root_browser_app     self.wrap_app(app)   File "/tmp/sd-webui-infinite-image-browsing/app.py", line 121, in wrap_app     infinite_image_browsing_api(   File "/tmp/sd-webui-infinite-image-browsing/scripts/iib/api.py", line 597, in infinite_image_browsing_api     class MatchImagesByTagsReq(BaseModel):   File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 98, in __new__     private_attributes = inspect_namespace(   File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 352, in inspect_namespace     raise PydanticUserError( pydantic.errors.PydanticUserError: A non-annotated attribute was detected: size = 200. All model fields require a type annotation; if sizeis not meant to be a field, you may be able to resolve this error by annotating it as aClassVaror updatingmodel_config['ignored_types']`.
For further information visit https://errors.pydantic.dev/2.3/u/model-field-missing-annotation
`
I'm using comfyui, so no A1111 or anything like that.

Try updating to the latest version and see if this problem is resolved.

Thanks, that fixed it.
Thanks for your very prompt and speedy response!


CounterTerm now support data of the array type

make CounterTerm more generic
add more tests

Codecov Report

Merging #22 (b519ce4) into master (2438892) will increase coverage by 1.25%.
The diff coverage is 92.30%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   35.44%   36.70%   +1.25%
==========================================
  Files          30       30
  Lines        2034     2068      +34
==========================================
+ Hits          721      759      +38
+ Misses       1313     1309       -4

Files Changed
Coverage Δ

src/common/para_builder.jl
65.51% <33.33%> (+5.17%)
:arrow_up:

src/common/counterterm.jl
85.32% <96.55%> (+3.39%)
:arrow_up:

src/vertex4/ver4_PH_l.jl
61.11% <100.00%> (+1.88%)
:arrow_up:


нет настройки в modmenu

при наведении на мод, modmenu показывает ошибку

Sorry, I don't speak Ukrainian, but I can still see the error message.  It should go away if you drop the jar from https://github.com/gbl/GBfabrictools/releases/tag/1.4 into your mods folder. Will publish a fixed version of ClickThrough soon.


[Feature] Tags

Purpose

Apply Tags when Creating Linode from StackScript, Image, and Backup
Add and delete Tags from Linodes Detail page
View Tags from Linodes Landing
Search for Tags in the Top Search

@Jskobos I assume we're going to need some kind of UX/UI for a Tags landing page


api: silence warning if API response failed due to connection closed

The Cilium API handlers are wrapped by a logic that takes care of recovering from potential panics triggered by the handlers themselves, emitting an associated warning. One such panic occurs when it is not possible to write the response to the client, due to the connection having already been terminated (as WriteResponse just panics on error). Considering that this condition is expected (e.g., the client may have timed out in the meanwhile [1]), let's slightly adapt the wrapper to lower the severity of this specific error to debug level, and avoid printing the associated stack trace.
[1]: for instance, it is possible to trigger this condition by running any cillium-dbg command that invokes an API in a loop, configuring a very short timeout.
Fixes: https://github.com/cilium/cilium/issues/36109

/test

I think the main important bit here is to make sure the debug log on line 35 is different from the debug log on line 45. WDYT?

I had previously made the messages identical because they could still be distinguished looking at the associated fields, which are different, but yeah, your suggestion makes sense to make the difference more explicit.

/test


React 18 release broke create-react-app appname --template redux

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

<EMAIL_ADDRESS>
What is the current behavior?
When I use the command:
npx create-react-app someappname --template redux
Since yesterday when React 18 was released as production, I now get this error every time:

Here it is again in text:
Installing template dependencies using npm...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^17" from<EMAIL_ADDRESS>npm ERR! node_modules/react-redux
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\minae\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR!      C:\Users\minae\AppData\Local\npm-cache_logs\2022-03-30T07_04_35_242Z-debug.log
npm install --no-audit --save<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>failed
What is the expected behavior?
It creates a react-redux app as normal.
Which browser and OS are affected by this issue?
n/a
Did this work in previous versions of React Redux?

[ ] Yes

Yeah, this is an unfortunate consequence of both CRA and NPM default behavior:

CRA apparently always installs the latest React by default
NPM now always installs peer deps, and errors if it can't find a match.

I may have to put out a React-Redux v7.2.x emergency patch that bumps the peer dep to accept React 18 just to work around this, although I don't like that.
The real solution is that we need to finish up React-Redux v8 and release it, but that'll be at least a couple weeks.
See https://github.com/reduxjs/react-redux/issues/1740#issuecomment-1083184887 for some additional thoughts.

Agree on NPM default behavior. But I think an emergency patch makes sense.
I have a non-CRA project. It is a React UI component library:

Uses<EMAIL_ADDRESS>Has peer deps of<EMAIL_ADDRESS>No dev/deps to react or react-dom

After react@18 is released, the CI pipeline of the project suddenly broke with zero code change.
NPM try to install react@18 because the project says it wants<EMAIL_ADDRESS>Then it conflicted.
On the other side, if the project doesn't have peer deps set, it is fine.

I've put out React-Redux 7.2.7 as a stopgap, but the real answer is we need to get v8 out the door.


POST and GET request returns inconsistent result on different pods

Bug Report
We have two prometheus pods in the same cluster and namespace and when start time is specified equal to the end time, one pod returns empty data and another pod returns multiple rows of data.
POST:
curl -X POST "http://localhost:9091/api/v1/query_range?start=2019-12-11T00:00:00Z&end=2019-12-11T00:00:00Z&step=15s" -d 'query=(kube_pod_status_phase{phase="Running", namespace="default"} ==1)'
GET:
curl "http://localhost:9091/api/v1/query_range?start=2019-12-11T00:00:00Z&end=2019-12-11T00:00:00Z&step=15s" -d 'query=(kube_pod_status_phase{phase="Running", namespace="default"} ==1)'
Environment
Kubernetes version v1.16.2

System information:
Darwin 18.7.0 x86_64

prometheus, version 2.10.0
build user:       root@a49185acd9b0
build date:       20190525-12:28:13
go version:       go1.12.5

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


How do I use this plugin?

After installing, I don't see any key bindings to it. I searched in "Keymap" settings for "case" and "string", but nothing appeared.
I just want an easy way to switch between various string cases (camel case etc...).
I use Android Studio 2.3.1.

is the plugin enabled?

yes

Works for me, try to reinstall it.

Can you please explain how to use it, and write it on main page of this repo?

Actions are available under Editor context menu, Edit menu, or via the shortcut "alt M" and "alt shift M". You can setup your own shortcuts for better usability.

A restart did it, but how can I choose for the toggle, which types to toggle between?
Also, is there one that guesses, based on context, which type to use? For example, if it sees it's a static-final variable (constant), it could guess I want to use uppercase only (with underscore character) .

Ok then.
What you see is what there is, nothing more, nothing special.

Can you please add this feature though? Some of the styles there I will never use...

Sure, I can click on the "Merge pull request" button.

If you mean I can add this, sadly I don't know anything about creating Android Studio plugins, so I don't want to ruin yours.


Migrate to ml4gw preprocess

Migrates whitener and standard scaler to ml4gw versions

This looks good. I'll approve it now. Feel free to merge when you have some of the minor details above done.


[flutter_tools] According to AnalysisSeverity return exit code detailed proposal

[flutter_tools] According to AnalysisSeverity return exit code detailed proposal
No matter what level(error, warning, info) issues flutter analyze always return fatal exit code(1). CI/CD environment receive 1(!0) e.g. Jenkins Build step 'Execute shell' marked build as failure. I propose according to AnalysisSeverity level return fatal(1) or success(0) exit code.
dartanalyzer reference
diff flutter analyze --help dartanalyzer --help
dartanalyzer have extra options:
    --fatal-infos                 Treat infos as fatal.
    --fatal-warnings              Treat non-type warnings as fatal.

In Dart SDK --fatal-infos and --fatal-warnings options affect the exit code should be fatal or success.
sdk/pkg/analyzer_cli/lib/src/options.dart
infosAreFatal = cast(args['fatal-infos']) || cast(args['fatal-hints']),
warningsAreFatal = cast(args['fatal-warnings']),

sdk/pkg/analyzer_cli/lib/src/driver.dart
 bool _shouldBeFatal(ErrorSeverity severity, CommandLineOptions options) {
    if (severity == ErrorSeverity.ERROR) {
      return true;
    } else if (severity == ErrorSeverity.WARNING &&
        (options.warningsAreFatal || options.infosAreFatal)) {
      return true;
    } else if (severity == ErrorSeverity.INFO && options.infosAreFatal) {
      return true;
    } else {
      return false;
    }
  }

sdk/pkg/dartdev/lib/src/commands/analyze.dart
      // Return an error code in the range [0-3] dependent on the severity of
      // the issue(s) found.
      if (hasErrors) {
        return 3;
      }

      bool fatalWarnings = argResults['fatal-warnings'];
      bool fatalInfos = argResults['fatal-infos'];

      if (fatalWarnings && hasWarnings) {
        return 2;
      } else if (fatalInfos && hasInfos) {
        return 1;
      } else {
        return 0;
      }

In Flutter SDK _AnalysisSeverity enum level from high to low:
flutter/packages/flutter_tools/lib/src/dart/analysis.dart
enum _AnalysisSeverity {
  error,
  warning,
  info,
  none,
}

flutter analyze & dartanalyzer experiments
Analyze code:
class MockAnalyzeBase extends AnalyzeBase {
  MockAnalyzeBase(ArgResults argResults) : super(argResults);

  @override
  Future<void> analyze() {
    // TODO: implement analyze
    throw UnimplementedError();
  }
}

MockAnalyzeBase exist 2 issues, it doesn't have required parameters and using wrong TODO format.
flutter analyze considers any level of AnalysisSeverity to be a fatal exit code(1).
$ flutter analyze
Analyzing hermetic...

warning • The parameter 'experiments' is required • analyze_test.dart:105:44 •
       missing_required_param
   info • Use Flutter TODO format: // TODO(username): message,
          https://URL-to-issue • analyze_test.dart:109:5 • flutter_style_todos

2 issues found. (ran in 2.6s;)
$ echo $?
1

dartanalyzer lint is the same as flutter analyze info, considers warning and info AnalysisSeverity to be a success exit code(0).
$ dartanalyzer .
Analyzing hermetic...
  warning • The parameter 'experiments' is required. • analyze_test.dart:105:44 • missing_required_param
  lint • Use Flutter TODO format: // TODO(username): message, https://URL-to-issue. • analyze_test.dart:109:5 • flutter_style_todos
1 warning and 1 lint found.
$ echo $?
0

Use // ignore: missing_required_param suppressing warning rule.
class MockAnalyzeBase extends AnalyzeBase {
  // ignore: missing_required_param
  MockAnalyzeBase(ArgResults argResults) : super(argResults);

  @override
  Future<void> analyze() {
    // TODO: implement analyze
    throw UnimplementedError();
  }
}

flutter analyze considers info AnalysisSeverity  to be a fatal exit code(1).
$ flutter analyze
Analyzing hermetic...

   info • Use Flutter TODO format: // TODO(username): message,
          https://URL-to-issue • analyze_test.dart:110:5 • flutter_style_todos

1 issue found. (ran in 2.8s;)
$ echo $?
1

dartanalyzer considers info AnalysisSeverity  to be a success exit code(0).
$ dartanalyzer .
Analyzing hermetic...
  lint • Use Flutter TODO format: // TODO(username): message, https://URL-to-issue. • analyze_test.dart:110:5 • flutter_style_todos
1 lint found.
$ echo $?
0

dartanalyzer add --fatal-infos option considers info AnalysisSeverity to be a fatal exit code(1).
$ dartanalyzer . --fatal-infos
Analyzing hermetic...
  lint • Use Flutter TODO format: // TODO(username): message, https://URL-to-issue. • analyze_test.dart:110:5 • flutter_style_todos
1 lint found.
$ echo $?
1

warning is higher than info:
dartanalyzer add --fatal-warnings option considers info AnalysisSeverity to be a success exit code(0).
$ dartanalyzer . --fatal-warnings
Analyzing hermetic...
  lint • Use Flutter TODO format: // TODO(username): message, https://URL-to-issue. • analyze_test.dart:110:5 • flutter_style_todos
1 lint found.
$ echo $?
0

Remove // ignore: missing_required_param
class MockAnalyzeBase extends AnalyzeBase {
  // ignore: missing_required_param
  MockAnalyzeBase(ArgResults argResults) : super(argResults);

  @override
  Future<void> analyze() {
    // TODO: implement analyze
    throw UnimplementedError();
  }
}

dartanalyzer add --fatal-warnings option considers warning AnalysisSeverity to be a fatal exit code(2).
Analyzing hermetic...
  warning • The parameter 'experiments' is required. • analyze_test.dart:105:44 • missing_required_param
  lint • Use Flutter TODO format: // TODO(username): message, https://URL-to-issue. • analyze_test.dart:109:5 • flutter_style_todos
1 warning and 1 lint found.
$ echo $?
2

Summary
0: success exit code
!0: fatal exit code
Related Issues
https://github.com/flutter/flutter/issues/60471
Tests
I added the following tests:
In flutter/packages/flutter_tools/test/commands.shard/permeable/analyze_once_test.dart
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Hi @jonahwilliams I hava a detailed proposal about exit code and flutter analyze & dartanalyzer experiments as mentioned above.

I like the idea, left some comments for improvement

Hi @jonahwilliams relate to generateErrorsMessage I fix the reviews on https://github.com/flutter/flutter/pull/61146 aim at Unified analyze error log format

61589 seems a break change, may need to be explained in next flutter stable version(CHANGEDLOG). Because AnalysisSeverity level warning & info issues not return fatal exit code(1) but success exit code(0).

@jonahwilliams Hi

If fatal-infos and fatal-warning were defaulted to true, would this be non-breaking?

Yes fatal will same as before.

Sorry for coming to this late, I only just learnt about this PR.
What is the use case for not failing if there's am info-level, lint-level, hint-level, or warning-level message?
Would that use case be handled by disabling the relevant feature in the analyzer options yaml file?

Sorry for coming to this late, I only just learnt about this PR.
What is the use case for not failing if there's am info-level, lint-level, hint-level, or warning-level message?
Would that use case be handled by disabling the relevant feature in the analyzer options yaml file?

Hi, Xie above list flutter analyze & dartanalyzer experiments diffs.
This PR aim to support --[no]fatal-infos or --[no]fatal-warnings in the global scope.
In analysis_options.yaml we usually modified for a certain rule.

The Related Issues mentioned here really affect the actual development especially CI. @jonahwilliams

Taking another took

any updates on this ?


Start from eta-phi space as latent space

In eta-phi space, points are already clustered really well. Could we apply a "residual approach" and only add/extend these coordinates to really "start" from this as the latent space

The latent space already seems to start from an eta-embedding early on:


Fix checkPropertiesEqual

Hi
Thought I'd take a stab at fixing this as per the WARN comment above it.
In our case, we pass quite a few props in navigation calls, including arrays and functions. The !== check fails for those, allowing for the double-tap effect mentioned  in https://github.com/aksonov/react-native-router-flux/issues/384
The proposed solution is to use lodash's isEqual which provides a solid equality check that should suffice for most cases. isEqual is bundled separately to prevent bloating RNRF.
Additionally to isEqual I also opted to exclude checking functions altogether, as those are usually generated inline as part of the navigation call, failing isEqual as well.
Thoughts?

This is great. I have the same issue of double calls to Actions which cause two pushes to happen.

@aksonov are you interested in merging my fix? I'll re-open the PR w/ the just 1st commit if you are

@barakcoh Yes, I'm interested

Could you please resolve conflicts and re-send PR, I've fixed the build

Closing in favor of https://github.com/aksonov/react-native-router-flux/pull/1682


add missing interfaces for sub-classes of PerformanceEntry

Fixes #58644
The interface were missing for subclasses of PerformanceEntry which causes an error when we try to run below code snippet Playground Link
function pageWasRealoaded(): boolean {
    return performance
        .getEntriesByType('navigation')
        // Error: TS2339: Property type does not exist on type PerformanceEntry
        // This is wrong, because this is a PerformanceNavigationTiming object
        .some(entry => entry.type === 'reload');
}

I have added missing interfaces for different subclasses for every return type which can be found here. All of them inherit from PerformanceEntry interface.
I found that some interface were missing some properties. For example PerformanceResourceTiming.initiatorType
I think there are still changes that needs to be done. Thanks @lll000111 for guiding me.
Please provide feedback.

@microsoft-github-policy-service agree

I have now found that I might need to add interfaces in webworker.generated.d.ts because the issue is not resolved yet.
Earlier, I compiled the code to JavaScript and ran that compiled code. I missed that TypeScript compiler is still throwing the same error.

I just found that some entry types are not supported by getEntriesByType(). See here. I added interfaces for them too, earlier. So, I will have to remove them in the next commit.

@RyanCavanaugh The issue is still not getting solved, can you please help me with this?


1.41, 1.42, and 14.3 install packages using system pip rather than virtualenv pip

The correct packages to install and uninstall are calculated based on what is installed in the virtualenv, but then the installation occurs in the system pip. 1.4.0 and earlier behave correctly.
This is on a CentOS 6 machine using the Software Collections Repository's Python 2.7; the system Python is 2.6.
pip-sync is invoked as
$ sudo scl enable python27 '/usr/local/envs/foo/bin/pip-sync requirements.txt'

The installed packages end up in
/usr/lib/python2.6/site-packages

Yes, this has been deliberately changed. The previous behaviour was consider a bug by many. The pip-sync behaviour right now is that it will simply invoke pip, leading to whichever pip happens to be on the PATH first. You can inspect for yourself which version that is by running:
$ which pip
That will likely point to /usr/bin/pip in your case.

So that requires the virtualenv be activated first:
$ source /usr/local/envs/foo/bin/activate

Thanks. Please close.

Glad that fixed it!


Capture Shield native users and roles

From Elasticsearch 2.3 shield can now be configured via API, and the shield roles and users are stored in Elasticsearch.  Previously it was possible to debug all shield issues from the shield config files attached, but now increasingly this will not be included - would it be possible to capture the shield users and roles (if shield is installed) as well?

Added a while back.


Player controls improvements

Allow using custom icon for player controls play button
Improve focus rect display for player progress bar
Prevent hiding player controls while focus is inside

Coverage decreased (-0.02%) to 99.083% when pulling 1587d4fb01da99c0a8f8f8f9f116e0547a34e178 on tf:player-controls-improvements into d2caa5a288f35b85134976897e3b36e9e2c0fa23 on codevise:master.


Fix module name mistake in Readme

⚠ IMPORTANT POINTS: ⚠

Give the PR an appropriate Title.
If you want to fix a lot of Issues together, please consider opening a Draft PR first and mention alL the issues in a list along with the status of the fix that you are working on.
Mention the IssueNumber in your PR if it is fixing an Issue with closes #IssueNumber.
Please provide sufficient information regarding the changes you have made.
Please read the CONTRIBUTION guidelines first otherwise your PR may not get merged.

@shubhamgrg04 great,it would be shortly merged by one of the maintainers

Hey @shubhamgrg04, thanks for the fix!


FR: Dissection of Accept header

Currently the only way to inspect the Accept header is to manually apply string splitting, for example;
found = []
lines = request.headers.getall('Accept', [])
for line in lines:
    found += line.split(",")

It would be nice if bottle had support for this out of the box, perhaps something like;
request.accept_content_type = ['application/json', 'text/html']

Admittedly the naming convention of accept_content_type is a bit crappy, so I'd welcome other suggestions.
Thoughts?

After tumbling down the rabbit hole, I've emerged with a complimentary library which handles content negotiation and media type rendering, with pretty much flawless results. I'm going to close this issue out for now, but will update it with a link once the library is stable.

What library?


showSelectionBar in opposite direction

I need the selection bar to travel: From position of handle -> Max. position, instead of how it is now: From min. position -> position of handle. I couldn't find a way to configure it to make this happen.
Currently:
|=========o----------------|
Need:
|----------------o=========|

Currently this is not possible. I'm taking a look at it to see if it could be done quickly.

It was easy. Just need to add the unit test coverage and it's OK on my side. Tell me if this corresponds to what you need.

Available with 2.4.0 by using the showSelectionBarEnd option.

Great! Works perfectly. Happy for such fast response.


made plugin compatible with Webpack 4

In Webpack 4 callback function will not be specified cause it requires a promise to be returned. Or nothing returned if plugin is synchronous.
This PR will fix Webpack 4 compatibility issues.

I think the owner of this repo is not an active user and sounds to me this repo is dead.
I think it is better to fork it and publish a new version with new name Or maybe use the code directly instead of the plugin.

Yeah I think I'm gonna do it soon

@sherlock1982
Here we go : https://github.com/almothafar/webpack-inline-manifest-plugin try this.


Rename respelling -> resize (or scale?)

making a fraction have a larger denominator is "expanding"; the inverse is "reducing". so, the name for an operation that either expands or reduces might be better expressed as something with a spatial connotation, like "resize" or "scale" (or "scaleTo"? seems verbose)

I thing I vote for scale(denominator:) and scale(numerator:).
The only issue is, is that it feels like it is actually changing size. However, it should be explicit that the underlying arithmetic value is the same.

Ok, that makes sense to me. I guess the name fits since you're technically multiplying n & d by scalars. :)

In related news, what about mutate.
I was trying to differentiate the two methods (one where the original arithmetic value is maintained, and one where it is corrupted).
It could be nice to have a pair of names that are polar in the same field.

i think maintain/corrupt isn't an atomic enough pair to base the names on. many operations can maintain the value, and many operations can corrupt it.


pairwise_distance validation fail on pipeline with MKL error

On pipeline, it seems following mkl libs are making pairwise_distance numba_np validation fail:
LD_PRELOAD="${CONDA_PREFIX}/lib/libmkl_intel_ilp64.so ${CONDA_PREFIX}/lib/libmkl_tbb_thread.so ${CONDA_PREFIX}/lib/libmkl_core.so" python -c "import dpbench; dpbench.run_benchmarks()"
Some observations:
without LD_PRELOAD mkl libs, the numba_np will pass validation.
Nan is observed when LD_PRELOAD is set: for example:
here is an example when case size is set to 4:
numba_np [[1.16129922 0.96464119] [ nan nan]]
numba: [[0.72923054 0.62394497] [0.51538559 0.28274484]]
Based on Sasha, it might be a bug in MKL lib, so we have to load MKL lib manually. The fix will be available in 2023.0 which will be tested once it is available.

This issue does not seem to occur anymore. Please re-open if needed.

This seems to be occurring again in CI.

Issue no longer occurs.


Add support for Swift with swiftlint

As far as I can tell, SwiftLint seems to follow the GCC format exactly.
See https://github.com/realm/SwiftLint.

My apologies, I completely missed that! Let me know if you'd like me to rebase/squash that commit into the prior one or not.

Nah, it looks pretty good to me. Whenever a few commits show up in a pull request, I just --squash merge the pull request via GitHub. I'll merge this one now.
Cheers! :beers:


browser.waitFor > 5000 ignored

Hi,
I tried to use waitFor with values way beyond 5000. Initial calls after system startup take that much time because of lazy initializations in backend systems. Very high timeouts did not work so I searched and found that there is a fixed value of 5000 in eventloop.coffee in wait (currently line 159).
Would it be possible to either increase this value or have it as an additional option in options?
Regards,
Sven.

Increasing the value would just make "not doing anything useful" tests take longer to complete. Adding another option would just complicate the API and documentation. Using two wait calls in sequence will give you twice the wait time, without having to learn any new API changes, or compromise with other people's preferred timeout.

I had a related experience using browser.wait(condition, callback). The callback was called even though the condition function never returned true (after exhausting eventloop's 5000 ms timeout). Is this by design? The result, in our case, was tests "passing" despite intermediate assertions failing.

The callback will not wait forever. I don't think being stuck forever helps.

Agree. I'm just thinking that the callback should be called with an error if the condition timed out without being satisfied.

Why shouldn't the client decide how long browser.waitFor should really wait? As of now every value above 5000 will get capped to 5000 by eventloops fixed timeout. I can use browser(..., {waitFor: 150000}) but this will not result in 150000 ms wait but in 5000 ms wait. If I want a single call to have a longer timeout why shouldn't I? No need for API changes no need to increase the fixed timeout. Again: I'm talking about the option "waitFor" handed to browser.visit, I know I can hand over a timeout instead of options, but I want to use both "runScripts" and "waitFor".

Short version is, waiting has to eventually terminate, otherwise people will be wondering why Zombie is stuck forever and never returning.
Having one sane limit for default behavior and some way to over-ride it for special case is acceptable. Suggest a pull request and I'll look at it.

I understand the endless waiting issue, will try to come up with a sane suggestion.

It won't wait if there's nothing to wait for.

@vainrobot I'm having a similar issue in the sense my dom updates and zombiejs has no idea the event occured (I'm replacing the 'src' on an image tag).  Think this is a separate issue from .wait as @assaf said there is nothing to wait for.   I just opened up the source code today and my best guess are these DOM events aren't in the eventLoop so they are never deferred to in the .wait.  So maybe this should be a different issue-thread on whether or not there should be an interace to register custom-dom events for onload.  Or is there one and I don't know?
I see all sides of this argument.  I think it caused some confusion on my part as I had some async/race-conditions in my tests that I could not figure out, even after jacking my waitFor up to 20000.  I had missed the one the block of text in the documentation that mentioned the 5000 default-cap.    I'd like to be able to bump this value up just abit to give myself some cushion.


added single product display page

Fixes - #7
PFA Screenshot of the Screen.

Hey @chandansgowda plz resolve the merge conflict

Congrats @chandansgowda 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/)
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.
That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.


HealthScope CRD is missing

Describe the bug
On a fresh installation of Kubevela, the HealthScope CRD has not been registered.
To Reproduce

Follow the Getting Started to install Kubevela on Kind.
List scopes

$ kubectl get scopedefinitions.core.oam.dev
No resources found in default namespace.
$ kubectl get healthscopes.core.oam.dev
No resources found in default namespace.

Expected behavior
Since the runtime implements an operator for the HealthScope, the CRD should be generated and registered in the system during the installation.
Screenshots

Cluster information

Kind cluster created following the getting started with kindest/node:v1.18.15.

Additional context
After applying the health scope definition from the oam-kubernetes-runtime I was able to obtain the scope as expected

$ kubectl get healthscopes.core.oam.dev app-health -oyaml
apiVersion: core.oam.dev/v1alpha2
kind: HealthScope
metadata:
  creationTimestamp: "2021-04-14T16:54:04Z"
  generation: 2
  managedFields:
  - apiVersion: core.oam.dev/v1alpha2
    fieldsType: FieldsV1
    fieldsV1:
      f:spec: {}
    manager: kubectl-create
    operation: Update
    time: "2021-04-14T16:54:04Z"
  - apiVersion: core.oam.dev/v1alpha2
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        f:workloadRefs: {}
      f:status:
        .: {}
        f:healthConditions: {}
        f:scopeHealthCondition:
          .: {}
          f:healthStatus: {}
          f:healthyWorkloads: {}
          f:total: {}
    manager: manager
    operation: Update
    time: "2021-04-14T16:54:09Z"
  name: app-health
  namespace: default
  resourceVersion: "5968"
  selfLink: /apis/core.oam.dev/v1alpha2/namespaces/default/healthscopes/app-health
  uid: 5b6966e0-ae45-4527-b9db-43560377f3e2
spec:
  workloadRefs:
  - apiVersion: apps/v1
    kind: Deployment
    name: express-server
status:
  healthConditions:
  - componentName: express-server
    diagnosis: 'Ready:1/1 '
    healthStatus: HEALTHY
    targetWorkload:
      apiVersion: apps/v1
      kind: Deployment
      name: express-server
      uid: 1f732f24-6c2d-4355-b813-55c9c14076a5
  scopeHealthCondition:
    healthStatus: HEALTHY
    healthyWorkloads: 1
    total: 1

@dhiguero Thanks for reporting this issue.
The healthscope in KubeVela is in namespaced scope https://github.com/oam-dev/kubevela/blob/master/charts/vela-core/templates/definitions/healthscopes.yaml#L5, while it is in cluster scope in OAM Kubernetes Runtime https://github.com/crossplane/oam-kubernetes-runtime/blob/master/charts/oam-kubernetes-runtime/templates/scopedefinitions.yaml.
So you may check healthscope by kubectl get healthscopes.core.oam.dev -n vela-system. As you installed KubeVela by default, vela-system should be the system namespace.
And could you please show me your application manifest, I can run it myself. Thanks.

Thanks for the clarification, I have tried again from a fresh install, and this is the output I get:
$ kubectl -n default get scopedefinitions.core.oam.dev
No resources found in default namespace.
$ kubectl -n test get scopedefinitions.core.oam.dev
No resources found in test namespace.
$ kubectl -n vela-system get scopedefinitions.core.oam.dev
NAME                        DEFINITION-NAME
healthscopes.core.oam.dev   healthscopes.core.oam.dev

It is true that the definition is installed in vela-system, but I would expect healthscopes.core.oam.dev to be "available" as scopedefinitions.core.oam.dev in every namespace as with the previous oam-kubernetes-runtime given that it is a default core scope.
Could you please elaborate on this change from the previous behavior?
By the way, this is the application I was using for the test (based on the existing example from the getting started):

app-with-scope.yaml
kind: HealthScope
metadata:
  name: app-health
spec:
  workloadRefs: []
---
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: first-vela-app
spec:
  components:
    - name: express-server
      type: webservice
      properties:
        image: crccheck/hello-world
        port: 8000
      scopes:
        "healthscopes.core.oam.dev": "app-health"

@dhiguero Hi, the definitions in  vela-system can work in any namespace. This change was introduced in https://github.com/oam-dev/kubevela/pull/1085
And the issue is https://github.com/oam-dev/kubevela/issues/918
In the design, vela-system is the KubeVela system level namespace, any definitions there can be widely used in any namespaces as system built-in capability. While other namespaces are user level namespace, definitions there can be seperated by user.
\cc @zzxwill


Issue with cacheDidUpdate plugin in workbox-precaching when other callbacks are also used

In my application, I display a splash screen and wait for complete the installation of the service worker and only then display the content, because the service worker must manipulate the csp token for several tabs for all requests in the API.
On a slow connection, the installation of a service worker can take up to a minute. I would like to keep the user busy with the progress of caching elements at this time.
I read #2406 and wrote a custom plugin for cacheDidUpdate:
export const cacheDidUpdate = async ({ cacheName, request, old Response, new Response, event, state }) => {
    const { log } = console;
    log('cacheDidUpdate', cacheName, state);
};

I used it in the service worker
addPlugins([cacheDidUpdate ]);

but I didn't see anything in the console.
What am I doing wrong?

Can you try it with
addPlugins([
  {cacheDidUpdate},
]);

A plugin is an object that has callback functions with properties like cacheDidUpdate. (There might be multiple callbacks in a single plugin object.) Your code looks like it's just passing in a function named cacheDidUpdate as if it were a plugin object.
Hopefully that works. Otherwise, we can reopen the issue./

I'm sorry - a typo.
in fact, my code is as follows
const my Plugins = {
   handlerDidError,
   cachedResponse Will Be Used,
   cachedupdates
};

add Plugins([my Plugins]);

but the result is the same

I've found the problem:
If I use to
addPlugins([
  {cacheDidUpdate},
]);

when I add some plugings
addPlugins([{
    cacheDidUpdate,
    handlerDidError,
    cachedResponseWillBeUsed,
}]);

cacheDidUpdate doesnt work
Here is the code of the other plugins
export const handlerDidError = ({ request }) => {
    logError(request);

    return null;
};
export const cachedResponseWillBeUsed = async ({ cacheName, request, cachedResponse }) => {
    if (cachedResponse) {
        return cachedResponse;
    }

    const cache = await caches.open(cacheName);
    const response = await fetch(request);

    if (!response.ok) {
        logError(request, 'Error loading asset');
        return null;
    }
    await cache.put(request, response.clone());
    return response;
};

Hmmm... let me look into that more closely, as in general, you should be able to use various plugin callbacks together.
I'm glad you have a workaround for the time being, though.

I'm revisiting this, and just to clarify, are you saying that cacheDidUpdate never fires, or that cacheDidUpdate fires sometimes, but not when your cachedResponseWillBeUsed function does the cache.put()?
If you mean the latter, then that's excepted, as cacheDidUpdate only fires as part of a cache update performed by the cachePut() method of a StrategyHandler. It won't fire for arbitrary cache.put() calls that are made elsewhere in the code.

if I use both plugins: cacheDidUpdate and cachedResponseWillBeUsed - cacheDidUpdate never fires
cacheDidUpdate fires only if cachedResponseWillBeUsed is missing

I'm still unclear on exactly what's going on.
Taking a step back, https://github.com/GoogleChrome/workbox/issues/2858 tracks another request to "repair" precached assets outside of the normal service worker lifecycle.
If we added that functionality in an upcoming release (but only for precache manifest entries that had an integrity property), could that replace your "repair" plugins?

See #2921 for the proposed "repair" logic.

If we added that functionality in an upcoming release (but only for precache manifest entries that had an integrity property), could that replace your "repair" plugins?

This would definitely help us get rid of our "recovery" plugin!

The precaching repair functionality is now live in https://github.com/GoogleChrome/workbox/releases/tag/v6.3.0

The precaching repair functionality is now live in https://github.com/GoogleChrome/workbox/releases/tag/v6.3.0

Thanks!

@jeffposnick
Unfortunately, I have one option when integrity property does not save -/ root route in the case of SSR.
This is not a static element - they are dynamically generated depending on the browser, for each client, and depending on many other parameters - so it is not possible to use integrity property for it, but this element must be present in the cache  and must be "repair" if it is not in the cache

I don't feel comfortable adding in automatic precache repair functionality unless integrity is also being used.
If I had a dynamically generated HTML page that was heavily customized for each client, I don't think I would use precaching for that to begin with, though, since it's probably very difficult to generate a meaningful hash of the contents at build time.
Using a StaleWhileRevalidate, CacheFirst, or even NetworkFirst runtime caching route for those types of documents makes more sense to me. You can ensure that it's added to the cache during installation via a custom install handler.
// Don't include and entry for `'/'` in your precache manifest.
precacheAndRoute(self.__WB_MANIFEST);

self.addEventListener('install', (event) => {
  event.waitUntil(
    caches.open(INDEX_CACHE)
      .then((cache) => cache.add('/'))
  );
});

registerRoute(
  // If you need to support /index.html as well,
  // this criteria would need to be tweaked and you'd
  // want to add a cacheKeyWillBeUsed plugin to normalize.
  ({url}) => url.pathname === '/',
  new StaleWhileRevalidate({
    cacheName: INDEX_CACHE,
  })
);

This solves the problem, but breaks the uniformity and simplicity - the developer will have to be informed about this case and should not forget to exclude the ` / ' route from the manifest and add the code to the worker service.
The solution with integrity, it seems to me, complicates the process - it forces us to write additional code for generating hash, although we have either revision or its hash / version is contained in the resource name itself
My opinion about restoring pre-cache elements is that they can and should be re-requested uniformly and all the information for this is already in the manifest.

This solves the problem, but breaks the uniformity and simplicity - a developer will have to be informed about this case and should not forget to exclude the ` / ' route from the manifest and add the code to the worker service.

All of the Workbox tools that are used to generate a manifest, by default, will look at actual assets on disk (or in a webpack asset pipeline, if you're using webpack), and create a revision parameter based on the actual static contents of what it finds. If the contents of / are generated or customized dynamically, on the server, then it stands to reason that they don't uniquely depend on static assets. I'm not sure how you ended up with an entry for / in your precache manifest, unless you used the templatedURLs option (which generates a compound revision hash from multiple static dependencies), or if you manually added a hard-coded entry for /. In either of those cases, the developer needs to go out of their way to add / to the manifest, so it's not extra work to exclude it.

My opinion about restoring pre-cache elements is that they can and should be re-requested uniformly without writing a code and all the information for this is already in the manifest.
In the case of the ' / ' route (and other resources generated dynamically by the server), you should not need to request a resource with integrity info.

To repeat what I mentioned above—I think the fundamental issue is that you shouldn't have / in your precache manifest, if its contents vary based on a dynamic server response. This is what runtime caching is meant to deal with.
CC: @malchata, who is working on revamping our docs, in case this is something that we can clarify there.

To repeat what I mentioned above—I think the fundamental issue is that you shouldn't have / in your precache manifest, if its contents vary based on a dynamic server response. This is what runtime caching is meant to deal with.

Why not ? I'm sorry, but I don't understand why we can't have / in the precache manifest - it's just a resource that, like other resources, must be in the precache manifest for normal offline operation.
I agree that it is not static and generating a revision for it does not make sense, but it is possible that there may be several such resources in the project and it is possible to add a flag to the manifest configuration that this is a dynamic resource and it just needs to be loaded
If we had an option in the workbox configuration that the resource is dynamic , there would be no need to generate integrity property (and how about the idea of putting integrity generation (if it is still needed) under the hood of the workbox if there is a flag in the configuration?)

Why not ? I'm sorry, but I don't understand why we can't have / in the precache manifest - it's just a resource that, like other resources, must be in the precache manifest for normal offline operation.

It's just that workbox-precaching is not designed to handle the caching lifecycle of this sort of resource. I apologize if it's not clearer in the documentation, and it's obviously possible to make workbox-precaching do things that it's not intended to do, but your service worker is going to be more resilient over all if you go with, and not against, the intended design.
Workbox's solution for caching dynamic resources is to use a runtime route to handle serving what's already in the cache and updating it with the most appropriate strategy based on your knowledge of your architecture. It might be stale-while-revalidate, or network-first, or something else. If you need to guarantee that the resource is in the cache during service worker installation, writing a custom install handler, as in the example above, will give you that guarantee.
If you're asking about how to configure our build tools to generate this sort of runtime caching route, you can do that with the runtimeCaching configuration option.

It's just that workbox-precaching is not designed to handle the caching lifecycle of this sort of resource. I apologize if it's not clearer in the documentation, and it's obviously possible to make workbox-precaching do things that it's not intended to do, but your service worker is going to be more resilient over all if you go with, and not against, the intended design.

The library should simplify the life of the developer and for the developer, the simplicity of its use lies in a simple declaration of what he would like to pre-cache - and this is a simple list of resources.
Considering your suggestions and objections, the developer should be very well versed in the nuances of the library when working with static and dynamic resources, although he does not need it and complicates the use of the library.
He would like to declare that the library should cache, and you suggest that he actually return to manually writing the logic of the service worker - then why do we need a library?
I apologize if my statements are harsh, but I think like a library user and in this form I see chaos: in one place I have to use the library, and in other places I have to write native code for the implementation of the service worker. So isn't it easier then to write everything with hands?
the ' / ' route is one of the elements of the precache list - why should I process it separately from the other elements of this list?
This only complicates the use of the library and introduces confusion

If you're asking about how to configure our build tools to generate this sort of runtime caching route, you can do that with the runtimeCaching configuration option.

I'm talking about writing by hands integrityManifestTransform - it should be automated with workbox with an option in config

Thanks for continuing to engage with us here—I do want to figure out exactly how you've approached Workbox, and learn from that had we could better guide folks towards better outcomes in our documentation (or add in new features when appropropriate).

The library should simplify the life of a developer. The simplicity of its use lies in a simple declaration of what he would like to pre-cache - and this is a simple list of resources.

So I wanted to push back a bit here, because while you're able to pass in whatever list of precache entries you want to precacheAndRoute(), the expectation and documented behavior is that updates will only happen if you use a revision property for each entry that reflects the corresponding URL's contents. We give the following warning in the docs: Never hardcode revision info into a "hand written" manifest, as precached URLs will not be kept up to date unless the revision info reflects the URL's contents!
Based on what you're describing, there's an entry for / in your precache list, but I don't understand how its being added, or what its revision property is being set to. Is one of the Workbox build tools generating the entry for /? Or are you adding it in manually outside of the build process, and if so, how are you guaranteeing at build time that its revision parameter uniquely fingerprints the dynamic HTML that's returned from the server?

I apologize if my statements are harsh, but I think like a library user and in this form I see chaos: in one place I have to use the library with it's declarations, and in other places I have to write native code for the implementation of the service worker. So isn't it easier then to write everything with hands?

That's a fair point, and the custom install handler that I described above could be written using the warmStrategyCache() method of workbox-recipes instead. (workbox-recipes is new-ish, and my instinct is sometimes just to go with the underlying service worker API when coming up with quick examples.)
import {warmStrategyCache} from 'workbox-recipes';
import {registerRoute} from 'workbox-routing';
import {StaleWhileRevalidate} from 'workbox-strategies';

const indexStrategy = new StaleWhileRevalidate({cacheName: INDEX_CACHE});

registerRoute(
  ({url}) => url.pathname === '/',
  indexStrategy
);

warmStrategyCache({
  strategy: indexStrategy,
  urls: ['/'],
});

I'm talking about writing by hands integrityManifestTransform for generating integrity property - it should be automated with workbox with an option in config

This goes back to my earlier point, since the same complication around generating a revision property applies to generating a integrity value: I don't see how a theoretical integrityManifestTransform could be written (either by you, or as part of Workbox) that would work in this use case, because the HTML response from the server is dynamic, and you don't know what the SHA-256 hash of it will be ahead of time. That's why I'm strongly suggesting that you shouldn't go out of your way trying to force workbox-precaching to handle that URL, and instead should use runtime caching with the workbox-strategy class that makes the most sense for the freshness guarantees you want.

Ok, I'll tell you how our service worker is arranged and how we would like it: we generate the manifest using the InjectManifest plugin.
In the service worker, we add the ' / ' route to the manifest
const гupdatedManifest = [
    ...self.__WB_MANIFEST,
    {
        url: '/',
        revision: packageJson.version,
    },
];

Webpack generates us resource names with contenthash.
This is quite enough to have a consistent precashe for offline.
Given that other developers may not have the contenthash, you suggest generating an integrity attribute for them.
In order to make it clear to workbox that it is necessary to generate an integrity attribute for static resources under the hood, I would add the generateIntegrityAttribute flag to InjectManifest,
        new InjectManifest({
            swSrc: '...',
            swDest: 'sw.js',
            ...
            generateIntegrityAttribute: true
        }),

a dynamically generated resources (resources without the integrity attribute) I would upload it as it is - they do not require any verification.
Now I hope everything is clear and transparent, and when" repairing" the damaged precache, you can safely download all the resources specified in the manifest.

Thanks for sharing that.
I think we'll add in an addIntegrity configuration option in a future Workbox release, most likely defaulted to false, to make using integrity easier in the future. (Some folks end up loading items in their precache manifest from cross-origin CDNs, and they don't always have CORS enabled, which won't work with subresource integrity, so I don't know that we'll ever default to adding in those attributes.)
Getting back to your specific usage, apart from all other aspects of this discussion, I would recommend that you don't add any entries to the precache manifest that is generated by the build tools unless you're sure that the revision field uniquely identifies the actual content associated with the URL. Based on what you've described, the contents of / are dynamically generated and don't correspond 1:1 to a value known at build time like packageJson.version. Using runtime caching for /, as described above, sounds like a much safer option for your use case. The "repair" step, where the network is consulted when there's a cache miss, is already implemented in runtime caching strategies like NetworkFirst or StaleWhileRevalidate.
I am at a loss for how the Workbox libraries could prevent you from doing what you're doing, so I don't think that this is a problem that could just be solved by improving the developer experience. We currently have warnings enabled if you just manually added an entry with a url and without a revision property, but stopping someone from explicitly passing in an entry that has a revision property which doesn't correspond to the URL's  contents is a different problem.
https://github.com/GoogleChrome/workbox/blob/03055e64014a46f6cc977a3a50ad814c6409d36a/packages/workbox-precaching/src/PrecacheController.ts#L158-L169

Getting back to your specific usage, apart from all other aspects of this discussion, I would recommend that you don't add any entries to the precache manifest that is generated by the build tools unless you're sure that the revision field uniquely identifies the actual content associated with the URL. ...

This approach greatly complicates the life of the developer and disorients beginners - static resources and a ' / ' router make up the precache list for the application to work offline. You suggest dividing this list and processing its elements in different ways.
If I were developing a workbox, I would implement such a contract
new InjectManifest({
    swSrc: '...',
    swDest: 'sw.js',
    include: [
       {
          url: '/',
          revision: <revision or empty>,
          dynamic: true
       },
       { url: /*.(js|json)$/ },
       { url: /*.(css)$/ },
    ],
    addIntegrity: true
}),

and under the hood I would get the integrity attribute for non-dynamic resources and for dynamic resources I would also do what you suggested above under the hood:
const indexStrategy = new StaleWhileRevalidate({cacheName: INDEX_CACHE});

registerRoute(
  ({url}) => url.pathname === '/',
  indexStrategy
);

warmStrategyCache({
  strategy: indexStrategy,
  urls: ['/'],
});

this would make it easier for both developers and beginners to understand that there is a list of precache resources - it is enough to describe it and the library itself knows how to load it and how to restore it.
Thus, the developer would only have to focus on working with the rest of the resources that are not included in the precache list.

In the interest of closing out this issue, I've revisited the original complaint, which is that when you add your cachedResponseWillBeUsed plugin to workbox-precaching, your cacheDidUpdate plugin isn't called anymore.
I went through a reproduction steps, and identified the following issue: your cachedResponseWillBeUsed plugin executes its "cache repair" logic any time the cachedResponse parameter is undefined.
During the install event, when processing a precache entry that's never been seen before, cachedResponseWillBeUsed will be passed an undefined cachedResponse, but this isn't an error condition—it's the expected behavior. Therefore, you should just return early from your cachedResponseWillBeUsed plugin if its called during install. This will allow your cacheDidUpdate to get called once workbox-precaching adds the new entry to the cache—as opposed to your "cache repair" logic adding the entry to the cache.
In other words, your code should change to:
const cachedResponseWillBeUsed = async ({cacheName, request, cachedResponse, event}) => {
  // Return early if cachedResponse is already set, or if this is an InstallEvent,
  // where cachedResponse being undefined is not an error.
  if (cachedResponse || event instanceof InstallEvent) {
    return cachedResponse;
  }

  // Your "cache repair" code goes here.
}

Hopefully this change in your cachedResponseWillBeUsed logic unblocks you from implementing the specific logic you believe is needed in your service worker.
I don't have much more to add beyond what I've already mentioned upthread regarding the other topics.

@jeffposnick thanks!

(I've updated the code sample to use event.type === 'install' instead of event instanceof InstallEvent, since the latter apparently won't work in Safari, where InstallEvent is not defined in the ServiceWorkerGlobalScope.


Rewrite script examples that use form inputs as apps

The examples that use form inputs were authored as scripts instead of apps in the interest of time, but are going to confuse first-time authors.
If an example use form inputs, we need to show how to handle those inputs in an app.

Most of the Form examples are already written as Wave apps. Only the following examples are in the script format.
Text
Text / Size
Label
Link
Progress
Progres / Updating
Message Bar
Separator
Frame
Frame / Path
Template
Markup

I think this is because all of the above Form components are non-interactive. Interactive components like Form Button, Form Textbox are already in wave apps. @lo5 So do we still need to migrate above components also to wave apps?

Ah! Thanks for the analysis - we can close this.


com.unity3d.player does not exist

I've installed react-native-unity-view as it mentioned in the instruction and exported Unity project.
I clone react-native-unity-demo project and paste my unity project. It gives me an error related to unity3dplayer.
What can be wrong?
react-native-cli: 2.0.1
react-native: 0.57.1
react-native-unity-view: ^1.1.5,
react-native-firebase: ^5.0.0,
Unity engine version: 2018.2.14f1

Task :react-native-unity-view:compileDebugJavaWithJavac FAILED
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityUtils.java:10: error: package com.unity3d.player does not exist
import com.unity3d.player.UnityPlayer;
^
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityUtils.java:21: error: cannot find symbol
private static UnityPlayer unityPlayer;
^
symbol:   class UnityPlayer
location: class UnityUtils
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityUtils.java:26: error: cannot find symbol
public static UnityPlayer getPlayer() {
^
symbol:   class UnityPlayer
location: class UnityUtils
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityView.java:11: error: package com.unity3d.player does not exist
import com.unity3d.player.UnityPlayer;
^
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityView.java:19: error: cannot find symbol
private UnityPlayer view;
^
symbol:   class UnityPlayer
location: class UnityView
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityView.java:21: error: cannot find symbol
protected UnityView(Context context, UnityPlayer view) {
^
symbol:   class UnityPlayer
location: class UnityView
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityViewManager.java:12: error: package com.unity3d.player does not exist
import com.unity3d.player.UnityPlayer;
^
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityUtils.java:49: error: cannot find symbol
unityPlayer = new UnityPlayer(activity);
^
symbol: class UnityPlayer
Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityUtils.java:73: error: cannot find symbol
UnityPlayer.UnitySendMessage(gameObject, methodName, message);
^
symbol:   variable UnityPlayer
location: class UnityUtils
Note: Q:\LocalRepo\react-native-unity-demo-master\node_modules\react-native-unity-view\android\src\main\java\com\reactnative\unity\view\UnityViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
9 errors

Probably same as this https://github.com/f111fei/react-native-unity-view/issues/25
@f111fei What do you think?

Is it stable way to solve ussue?

Probably same as this #25
@f111fei What do you think?

Probably the same issue as well

Duplicate https://github.com/f111fei/react-native-unity-demo/issues/21


Fix rollback issue

The version of goleveldb that we were using before returned nil instead of []byte{}. Unfortunately, this changes the behavior in v0.20.0 of github.com/cosmos/iavl. The sdk and iavl interpret nil as "doesn't exist", which meant that the iavl mistakenly couldn't rollback to past states if the tree was empty (which happened for modules that had an empty genesis state and no state updates thereafter).

Devil's advocacy: pinning a specific version as non buggy isn't very future proof.

Completely agree. The package itself appears to be abandoned. I really hope we can move to a different db at some point, as a long-term solution. The main thing precluding us from doing that right now is the tx indexing, which depends on a comet-style db backend (to fix that, we'll need to vendor and rewrite this function) :(
So we're stuck with this until we prioritize a db refactor.


Pylance import suggestion doesn't recommend variable I'm trying to import

 Environment data

Language Server version: 2022.4.1
OS and version: darwin arm64
Python version (and distribution if applicable, e.g. Anaconda): python 3.10
python.analysis.indexing: true
python.analysis.typeCheckingMode: basic

 Expected behaviour
Cmd-. should suggest the correct import path for a variable called app_session here:
semgrep/publish.py
    if not app_session.token:
        # ...

where app_session is defined as:
semgrep/app/__init__.py
from .session import AppSession

app_session = AppSession()

 Actual behaviour
When semgrep/app/__init__.py is not open in a tab

This suggestion comes up which is very far off.
When semgrep/app/__init__.py is open in a tab

This suggestion comes up, which is defined as:
semgrep/app/session.py
class AppSession(requests.Session):
    ...

 Logs
https://gist.github.com/underyx/c308790296457d25360c3145e43d78d6

Pylance only include symbols exported from top level package module (ex, semgrep/__init__.py) to prevent completion list become too long.
but we do provide hidden knob on how much we include in completion (with performance cost, of course)
see this for more detail - https://github.com/microsoft/pylance-release/issues/2533#issuecomment-1089268739

@underyx I think you have indexing off, so we fallback to the behavior where we only get data from files that are already consumed through opened files, either directly or indirectly.
also, by default, we don't import most of variables since python has nothing to indicate which variable is supposed to be used outside or it is supposed to be used only locally.


[#2237] feat(core): Add the support of PermissionManager

What changes were proposed in this pull request?
Add the support for permission manager.
Why are the changes needed?
Fix: #2241
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add a new UT.

Continue to polish your code when you feel ready. I think it is not ready for review.

I have added cache for the role. Could you review this pull request again?

@jerryshao All comments are addressed.

CI passed. I will merge this pull request to the main branch.


Final touches

Milestone3: Change design
The following changes are being introduced:

A few changes to the overall feel of the project but the structure remained the same.

Thanks for approving my work!👊


Move generated patterns to API

The annotation based compile-time code generator reads javaslang.$ and generates javaslang.Patterns.
Changes:

[ ] Add the patterns to javaslang.API
[ ] Remove existing compile-time dependency to javaslang-match from javaslang/pom.xml
[ ] Add test compile-time dependency in order to unit-test the code generator
[ ] Remove javaslang.$ (and javaslang.Patterns)

We will not fuse the Pattern concept with the Value concept. This is obsolete.


chore: remove routing_test.rs

Didn't end up being useful for e2e testing, and is now superseded by the latter.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 49.19%. Comparing base (41cf4a7) to head (e9372ea).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #193      +/-   ##
==========================================
- Coverage   49.40%   49.19%   -0.22%
==========================================
  Files          24       24
  Lines         927      927
  Branches      927      927
==========================================
- Hits          458      456       -2
- Misses        446      448       +2
  Partials       23       23

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


Minor test update

Ticket
No ticket.

There are some conflicts as well. :(

Changes Unknown when pulling db026b88abbb5350b38d9563f5fd2875d173a587 on Menda:minor-test-update into ** on toladata:dev-v2**.


[FILTERS] Fix trace on table view load

STR:

Access table view

Expected result:
Table view loads normally
Actual result:
Table view loads with console errors table.js:57708 Uncaught TypeError: self.filters.loadScroll is not a function

See PR #150
Changes
Removed all calls to loadScroll()
Updated jqueryUI Autocomplete with correct div

closing --> PR was merged + no activity for months


Feature/rusu1/remap operator s01/multi domains

Merged multi-domain support branch into operator branch.

Did not merge into develop. Just merged a sub branch into my main branch.
From: Edward Rusu<EMAIL_ADDRESS>Reply-To: visit-dav/visit<EMAIL_ADDRESS>Date: Tuesday, February 19, 2019 at 11:34 AM
To: visit-dav/visit<EMAIL_ADDRESS>Cc: "Rusu, Eddie"<EMAIL_ADDRESS>Your activity<EMAIL_ADDRESS>Subject: [visit-dav/visit] Feature/rusu1/remap operator s01/multi domains (#79)
Merged multi-domain support branch into operator branch.

You can view, comment on, or merge this pull request online at:
https://github.com/visit-dav/visit/pull/79
Commit Summary

Unrolled first level of dataTree
Added global rectilinear grid
Added skeleton for ClipDomain function
Added check for domains without cells
Tagged rectilinear grid with variable arrays
Added clipping and volume calculations
Added rectilinear grid and properties as class fields
rgrid values tracked from domain to domain to produce accurate final grid
Changed GetBounds to work on class fields
Cleaned out old code.
Fixed bad initialization problem
Moved mem managment of pointer class fields to the constructor and destructor
Added some deletes for memory clean up
Added a recursive domain tree traversal for nested domains.
Moved element debugging output to track the entire rgrid, not just each domain.
Resolved merge conflict. Added todo.

Reply to this email directly, view it on GitHubhttps://github.com/visit-dav/visit/pull/79, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ARtLA7JpSK7XI2a08O6ZxMsTZ7wlhcI5ks5vPFHCgaJpZM4bDtPe.


bug: Not an editor command: RepoLink

I installed this plugin to lazy.nvim (LazyVim) but the command doesn't register for some reason.
return {
  "9seconds/repolink.nvim",
  event = "VeryLazy",
  dependencies = {
    "nvim-lua/plenary.nvim",
  },
  cmd = {
    "RepoLink",
  },
  keys = {
    { "<leader>yl", ":RepoLink<CR>", mode = { "n", "v" }, desc = "Copy git URL", silent = true },
  },
}

repolink.nvim: latest from master
lazy.nvim: v11.14.1
LazyVim: v12.38.2

Sorry I didn't follow the readme. Should have put opts={} even though it's empty.


Delete dead keyed_cell module

Description
Looks like this was added with a callsite in https://github.com/vercel/turbo/pull/6160 , and the callsite was removed in https://github.com/vercel/turbo/pull/6172 .
Testing Instructions
cargo check

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#8761  👈
#8760
#8758
main

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

Join @bgw and the rest of your teammates on  Graphite

Merge activity

Jul 16, 3:06 PM EDT: @bgw started a stack merge that includes this pull request via Graphite.


charts/netbox/templates/CronJob.yaml has a wrong indent on the extraVolumes

Hello,
Here I noticed the wrong indent which was defined for extraVolumes
{{- if .Values.extraVolumes }}
  {{- include "common.tplvalues.render" (dict "value" .Values.extraVolumes "context" $) | nindent 8 }}
{{- end }}

There should be nindent 10 instead of nindent 8

Sorry I missed it, it should have been fixed in this PR #53


Add a EIP-1559 feature flag

Overview
Currently, we have the list of EIP-1559-capable chains hardcoded.
We need to use the config service instead.
Requirements

Add a new Feature EIP_1559_SUPPORTED in the config-service admin (both staging and prod)
Update the types to include it.
Refactor the frontend code to use that
Get rid of src/config/chain-workarounds.ts

@katspaugh, apologies. We need not forget to add it to the types, nonetheless.

Thanks @fmrsabino, I'll move this to the gateway so as to add the types.

@iamacook this was meant for safe-react, please don't transfer issues at will.

Just to clarify, there are no types for features on the Safe Client Gateway. No action should be required by the backend team for this

@fmrsabino, we have our own gateway types. The above would need to be added to our FEATURES enum.


How to identify the disconnected state

If I understand correctly when TCP send fails the process method will just stop doing anything. Is there some way I could identify this state in the Arduino script so it could try reconnecting?

This project has a lot of limitations, you can try esp_mqtt or wait for other project like esp_mqtt and support arduino


Update ServiceContainer.php

Hello there. Can you please advise if this PR will be merged? Fixing the typo would help a lot =)

Hello there!
Could you evaluate the possibility of merging this PR?
This typo is causing some issues when registering the services.
@doubaokun, @misddev1412, @Liliandev

Will merge and publish soon.


dlrs_ContactTrigger: execution of AfterDelete caused by: dlrs.RollupService.RollupValidationException

When I am trying to merge contacts in Salesforce, I am getting this error:
dlrs_ContactTrigger: execution of AfterDelete caused by: dlrs.RollupService.RollupValidationException: Scheduled rollups are running in legacy mode and are unable to resolve corresponding shadow rollups. Please visit the Lookup Rollup Summary Tools tab for more information and steps to resolve. (dlrs)
It only started to happen after I installed v2.12 of DLRS (upgraded from 2.2). I deleted all scheduled Apex Jobs, and re-scheduled them after the upgrade, but I still get this error. Any idea, why?
Thanks!

I am getting the same error while merging records after upgrading to version 2.2 last week.

@filkanczula fyi, I was able to resolve the error by going to the schedule and clicking on "Manage Child Triggers" and following through all the prompts.

Let me know if this helps.

I've had them installed, so what I did is I went ahead and removed them, and installed again. I will see if that made any changes.

I think now the real-time calculation actually works, which wasn't the case, but the error persists when merging :/


WIP: GitHub auth config

Adds the GitHub ID Provider to the auth config and requires this GH ID Provider to be present on the config in order to authenticate via GitHub

@msteffen here's a WIP of the github auth config. I manually tested the basic flow in a local cluster (activating enterprise and auth via robot token, setting config without github, trying to login via github and failing because it's not allowed) and it seems to be working.
I'm working now on creating test for this in auth_test but wanted to get something up for you to look at since I promised you a first pass at a PR by today.

Closing this in favor of #3992


Add CloakingDevice

Closes https://github.com/KSP-CKAN/NetKAN/pull/2421

LGTM! Merging with Thanks! :D


[Package Request]: Touch Designer

How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://derivative.ca/download
Publisher: DERIVATIVE
Package Name: TouchDesigner
Description: TouchDesigner is a software product from Derivative (Toronto and Los Angeles) which is used to build interactive 3D and 2D applications. It is "procedural", "node-based", real-time and is considered a visual programming language. It is designed to give its users enormous flexibility in building applications without needing to program in a conventional way.
Package Version: 2023.11760
Installer URL: https://derivative.ca/download/release-download/38?width=650&height=300
Notes: It has WEB INSTALLER (~545MB) and FULL INSTALLER (~2.4GB) available for download!

[!WARNING]
The minimal system requirements of this package contains physical GPU hardware (AMD, Nvidia or Intel). This kind of packages cannot pass Azure Pipelines configured by Microsoft, since the runner VM cannot simulate them (see #107639).


Add support for default credentials provider chain

The AWS default credentials provider chain will try to resolve credentials from default locations (IAM instance profiles, files, environment variables, etc). This makes providing credentials directly in the plugin optional.
Resolves #12

I will test it along with #11 in dev branch. Thanks.


Update

Please can you update your packages for near versions of flutter, and please make it for work also in WEB.

@Lorenzobettega Late but maybe you would like to give try to pdf_manipulator plugin as it also supports compressing pdf to a certain extent with also many functionalities with iText7 support.


Add window family: confined Gaussian

Hello,
May I request the addition of a new family of windows to scipy.signal: Confined Gaussian windows. These have minimal RMS bandwidth for given RMS temporal width (http://www.sciencedirect.com/science/article/pii/S0165168414001388)
Cheers,
Gabriel

@gcrau that seems like a reasonable addition. If you or someone else wants to implement it, that's welcome I think.
Should go into signal.windows only (no more new windows in the signal namespace is what we discussed last year).

@gcrau
I am looking into this for a real-time application that I want to model in Numpy.
Keep you posted.


[Bug]: Landscape format images have blurry thumbnails

What happened?
I uploaded images for model reviews and all 16:9 ones get blurry thumbnails.
From looking at other images it seems the wider the image, the blurrier the thumbnail.
Steps to reproduce the problem
Check the reviews on this model's page for example : https://civitai.com/models/7241/mix-pro-v3
Look closely, some thumbnails are sharp, others are a bit or quite blurry.
What should have happened?
--
What platforms do you use to access the site?
No response
What browsers do you use to access the site?
No response
Additional information, context and logs
No response

No blur here.

From looking at other images it seems the wider the image, the blurrier the thumbnail.

We use scaling within Cloudflare Images to size everything down to 400px wide inside the review preview carousels, they then get scaled down further by your browser to 300px min based on how many review tiles we're showing. There are a few things that could be happening here:

Really wide images scaling down to 400px might lose detail
The browser isn't scaling 400px to 300px appropriately

Either way, when I browse that page I don't see anything particularly blurry, would you mind sharing a few screenshots so I can make more sense of how blurry you mean?

Here the top one is blurry, the bottom one is sharp.
And I know what's happening : the images get resized to 400px width as you said, then they get displayed as croped squares of 400*400. So for landscape ratio images, since their height is less than 400px after the resize, the actually get zoomed in to fit in the 400px height. And zoomed in means blurry.
Solution: resize landscape ratio images to 400px height not width

Honestly images should be 2-4x the actual viewing size for retina displays. Using AVIF will cut out on size substantially. We're long past the ages of 64k dialup and needing such tiny images.

Hey all, with the newest release on Civitai, this should have been sorted out. Please let us know if there are any issues with it again