deleting kube-prometheus yields errors (v0.22.0)

(This is kind of related to previous issue #1571 - for which the resolution was to run kubectl create -f manifests/ twice.)
To summarize the commands below, I found that when I delete kube-prometheus then errors are printed - are the errors benign? If so, then perhaps I should just simply change the command to kubectl delete -f manifests/ | true (to ignore/suppress the errors - i.e. for the command to have a non-error return code)?
~/v0.22.0_prometheus-operator/prometheus-operator/contrib/kube-prometheus
$ kubectl get pods -n monitoring
NAME                                  READY     STATUS              RESTARTS   AGE
alertmanager-main-0                     2/2       Running             0          3h
grafana-67b7f55895-f7qth                1/1       Running             0          3h
kube-state-metrics-69df7cf6bc-z55b6     4/4       Running             0          3h
node-exporter-lwb42                     2/2       Running             0          3h
prometheus-k8s-0                        3/3       Running             1          3h
prometheus-k8s-1                        3/3       Running             1          3h
prometheus-operator-8d78694b-bd2wn      1/1       Running             0          3h
$ kubectl delete -f manifests/
namespace "monitoring" deleted
customresourcedefinition "alertmanagers.monitoring.coreos.com" deleted
customresourcedefinition "prometheuses.monitoring.coreos.com" deleted
customresourcedefinition "prometheusrules.monitoring.coreos.com" deleted
customresourcedefinition "servicemonitors.monitoring.coreos.com" deleted
clusterrole "prometheus-operator" deleted
clusterrolebinding "prometheus-operator" deleted
deployment "prometheus-operator" deleted
service "prometheus-operator" deleted
serviceaccount "prometheus-operator" deleted
secret "alertmanager-main" deleted
service "alertmanager-main" deleted
serviceaccount "alertmanager-main" deleted
secret "grafana-datasources" deleted
configmap "grafana-dashboard-k8s-cluster-rsrc-use" deleted
configmap "grafana-dashboard-k8s-node-rsrc-use" deleted
configmap "grafana-dashboard-k8s-resources-cluster" deleted
configmap "grafana-dashboard-k8s-resources-namespace" deleted
configmap "grafana-dashboard-k8s-resources-pod" deleted
configmap "grafana-dashboard-nodes" deleted
configmap "grafana-dashboard-pods" deleted
configmap "grafana-dashboard-statefulset" deleted
configmap "grafana-dashboards" deleted
clusterrole "kube-state-metrics" deleted
clusterrolebinding "kube-state-metrics" deleted
clusterrole "node-exporter" deleted
clusterrolebinding "node-exporter" deleted
clusterrole "prometheus-k8s" deleted
clusterrolebinding "prometheus-k8s" deleted
rolebinding "prometheus-k8s" deleted
rolebinding "prometheus-k8s" deleted
role "prometheus-k8s" deleted
role "prometheus-k8s" deleted
Error from server (NotFound): error when deleting "manifests/0prometheus-operator-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com prometheus-operator)
Error from server (NotFound): error when deleting "manifests/alertmanager-alertmanager.yaml": the server could not find the requested resource (delete alertmanagers.monitoring.coreos.com main)
Error from server (NotFound): error when deleting "manifests/alertmanager-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com alertmanager)
Error from server (NotFound): error when stopping "manifests/grafana-deployment.yaml": deployments.extensions "grafana" not found
Error from server (NotFound): error when deleting "manifests/grafana-service.yaml": services "grafana" not found
Error from server (NotFound): error when deleting "manifests/grafana-serviceAccount.yaml": serviceaccounts "grafana" not found
Error from server (NotFound): error when stopping "manifests/kube-state-metrics-deployment.yaml": deployments.extensions "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-role.yaml": roles.rbac.authorization.k8s.io "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-roleBinding.yaml": rolebindings.rbac.authorization.k8s.io "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-service.yaml": services "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-serviceAccount.yaml": serviceaccounts "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-state-metrics)
Error from server (NotFound): error when stopping "manifests/node-exporter-daemonset.yaml": daemonsets.extensions "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-service.yaml": services "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-serviceAccount.yaml": serviceaccounts "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com node-exporter)
Error from server (NotFound): error when deleting "manifests/prometheus-prometheus.yaml": the server could not find the requested resource (delete prometheuses.monitoring.coreos.com k8s)
Error from server (NotFound): error when deleting "manifests/prometheus-roleBindingConfig.yaml": rolebindings.rbac.authorization.k8s.io "prometheus-k8s-config" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleBindingNamespace.yaml": rolebindings.rbac.authorization.k8s.io "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleConfig.yaml": roles.rbac.authorization.k8s.io "prometheus-k8s-config" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleNamespace.yaml": roles.rbac.authorization.k8s.io "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-rules.yaml": the server could not find the requested resource (delete prometheusrules.monitoring.coreos.com prometheus-k8s-rules)
Error from server (NotFound): error when deleting "manifests/prometheus-service.yaml": services "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-serviceAccount.yaml": serviceaccounts "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com prometheus)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorApiserver.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-apiserver)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorCoreDNS.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com coredns)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubeControllerManager.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-controller-manager)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubeScheduler.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-scheduler)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubelet.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kubelet)

Do the objects actually still exist? The custom resources are cleaned up just by deleting the CRDs, still curious why things like the the ServiceAccounts got those errors.

I verified (for a subset of the objects) that after running the delete that they no longer exist (more details below).
So maybe the only thing here is to do | true? In which case this issue could be closed (if there's nothing in kube-prometheus that needs to be fixed).

After the create ...:
$ kubectl get pods -n monitoring
NAME                                  READY     STATUS    RESTARTS   AGE
alertmanager-main-0                   2/2       Running   0          5m
alertmanager-main-1                   2/2       Running   0          4m
alertmanager-main-2                   2/2       Running   0          4m
grafana-67dbf88558-pk2l7              1/1       Running   0          6m
kube-state-metrics-69df7cf6bc-6hb82   4/4       Running   0          6m
node-exporter-7ckls                   2/2       Running   0          6m
prometheus-k8s-0                      3/3       Running   1          5m
prometheus-k8s-1                      3/3       Running   1          4m
prometheus-operator-8d78694b-f22bv    1/1       Running   0          6m
$ kubectl get services -n monitoring
NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
alertmanager-main       ClusterIP   <IP_ADDRESS>     <none>        9093/TCP            6m
alertmanager-operated   ClusterIP   None             <none>        9093/TCP,6783/TCP   5m
grafana                 ClusterIP   <IP_ADDRESS>     <none>        3000/TCP            6m
kube-state-metrics      ClusterIP   None             <none>        8443/TCP,9443/TCP   6m
node-exporter           ClusterIP   None             <none>        9100/TCP            6m
prometheus-k8s          ClusterIP   <IP_ADDRESS>   <none>        9090/TCP            6m
prometheus-operated     ClusterIP   None             <none>        9090/TCP            5m
prometheus-operator     ClusterIP   None             <none>        8080/TCP            6m
$ kubectl get serviceaccounts -n monitoring
NAME                  SECRETS   AGE
alertmanager-main     1         6m
default               1         6m
grafana               1         6m
kube-state-metrics    1         6m
node-exporter         1         6m
prometheus-k8s        1         6m
prometheus-operator   1         6m
$ kubectl get servicemonitors --all-namespaces
NAMESPACE    NAME                      AGE
monitoring   alertmanager              6m
monitoring   coredns                   6m
monitoring   kube-apiserver            6m
monitoring   kube-controller-manager   6m
monitoring   kube-scheduler            6m
monitoring   kube-state-metrics        6m
monitoring   kubelet                   6m
monitoring   node-exporter             6m
monitoring   prometheus                6m
monitoring   prometheus-operator       6m

and same commands after the delete :
$ kubectl get pods -n monitoring
No resources found.
$ kubectl get services -n monitoring
No resources found.
$ kubectl get serviceaccounts -n monitoring
No resources found.
$ kubectl get servicemonitors --all-namespaces
Error from server (NotFound): Unable to list "servicemonitors": the server could not find the requested resource (get servicemonitors.monitoring.coreos.com)

though I suppose a sentence could be added to the kube-prometheus/README.md to specify the kubectl command to run to teardown the stack

That sounds fantastic, would you like to create a PR and add what you would have expected :slightly_smiling_face: ?

If I were going to make such a change, then the snippet after the line below is what I'd change this part of the README.md to.
But I feel that would be a band-aid at best. Is anyone else at least occasionally encountering this #1609 issue and/or #1571 ? Instead of making the documentation update shown below, I'd of course prefer the steps be fixed so they always work (though I don't have any ideas off the top of my head how to do that).
With the change below, we'd be ignoring any legitimate errors encountered by those kubectl commands, which is obviously not ideal at best.

Simply create the stack by running the following command twice:
$ kubectl create -f manifests/ | true

And to teardown the stack:
$ kubectl delete -f manifests/ | true

I think we're expecting too much from kubectl here. It's not a configuration management tool, it is simply a tool to interact with the Kubernetes API on a simple basis. It doesn't solve all problem and it shouldn't, this is a more complex rollout problem, which kubectl is just not made for.

Totally agree, thanks Frederic. I imagine a solution would involve more than tweaking the two kubectl commands.
Unless I hear otherwise from you, I'll plan on submitting a PR to make the aforementioned README.md change when I get a chance. And maybe eventually some sort of code change can be made to kube-prometheus so it gets deployed & torn-down every time without a hitch (the issues I've encountered with the two commands only happen sometimes).

That sounds good to me, we drop in a note as well that says why that’s there.


Calc should have a new format that simply unquotes string values

Same effect as :quotestrings off

Suggest @q (which is not currently used). What about @Q? ... Should check other duplicates to see what the precedent is.

Even THIS is not enough if I want to do this:
monthly($P,$R,$N) -> {`Full monthly payment is $$${PMT($P,$R,$N)@2,d}`@q}

Because the function result is still a string, with or without the "@q" inside the function, therefore we need to do:
monthly(345000,0.35,360)@q
in order to have the final result come out without quotes....
Therefore, we need yet another change, but I don't know what it would be...

Another possibility is to allow functions to be annotated with a format for their return value, maybe like this:
define a($b)@q = { $b }
We would need to break out the formatting code from "visitExprStmt" into a separate function, which would then be called by "evaluateFunction" when/if there is an annotation for the return value format.  And, of course, we would have to save the format specifier in the FunctionDeclaration object.
This seems kinda hokey, but not excruciatingly bad ... A bit of work to separate out the formatting code, but it needs to be done anyway -- the visitor function has gotten quite nasty now (100s of lines of code, well, 330 to be (semi-) precise).
Grammar changes would be trivial (just add "FORMAT ?" after "formalParamList ?" in "defineStmt".

Well, am implementing this enhancement, and it works, but it STILL doesn't solve the problem.  Because the formatting normally occurs at the "expr" level, even formatting the function result still gets the quoting done "too early" to be useful. But, maybe we can figure out a way to propagate the format upwards, somehow .... So, I think the formatting at the function level makes sense for some other reasons anyway.  Or maybe we can muck with the grammar and put the formatting down lower anyway, so it is at the level where function results are now getting formatted and everything would be fine.  Anyway, going to commit to a new branch to work on further.

We could possibly return a Pair upward from the level that detects either function or expr formats, and then uses them at visitExpr level to do the formatting, even if a lower level has the format spec. Have to investigate to see what makes sense.

We could allow formats at variable "declaration" time, like this:
first@4X = 0xFFFF; first -> 0xFFFF
which would then be passed up layer by layer until "visitExpr" where the format could be overridden or this low-level one passed up is recognized and used.

Based on the (non) success of things in #161 we might need just the opposite of @q (maybe @Q?) that adds extra quotes. Otherwise I don't see how we can emulate JSON.stringify (from Javascript) to get Quine to work right.

Adding "@Q" to do the extra quotes. Makes "quine" work also.


Changed firestore quickstarts rules

Wrote these rules for a pending blogpost
Do you think these rules are easier to understand or harder?
I can also get rid of the validation function formattedCorrectly().

IMO these are too abstract to serve as a quickstart. We should start a repo with a bunch of different sample rules (and tests for them).

@ryanpbrewster like this repo?
https://github.com/firebase/snippets-rules
It has rules which are Travis CI tested against the emulator.  Feel free to send PRs to it or tell me what you'd want to see!


Best Practice for Live Data

For my current project, I have a RAG built on a live data source. I am handling detection of when the underlying data changes and am able to trigger indexing it. I am working on a couple improvements to the API to make it easier to do async and concurrent operations with HyperVectorDB, but that's going to come later.
What I am facing right now is removing old records from the vector database. A document may change or be removed entirely, at which point I'd like to remove the old vector for the database.
What would be the recommended method for doing this? I'd like to avoid re-vectorizing the entire data source if possible. I don't see anything in the current API for doing this, and if it isn't currently supported I will come up with something and make a PR ASAP.

I usually use the delete and add methods however I have been considering adding update, updateat etc methods to it,  I also want to overhaul the caching system to be a bit less destructive as a most of the time the whole cache does not need to be invalidated.


BUG: plasma tests failing in conda builds on linux

Describe the bug, including details regarding any error messages, version, and platform.
#14832 switched on the test suite within the conda-builds, which itself synced with https://github.com/conda-forge/arrow-cpp-feedstock/pull/875
In the process of doing so, currently all tests starting with test_plasma in their name were skipped,
https://github.com/apache/arrow/blob/2c768a1767c0d7b33644910e0e96a949bc6f6f42/dev/tasks/conda-recipes/arrow-cpp/meta.yaml#L377-L379
This only fails on linux, not on osx (windows doesn't have plasma). Additionally, it seems that there are two binaries for plasma-store-server being installed, one in $PREFIX/bin and one in $PREFIX/lib/python3.x/site-packages/pyarrow/. I'm pretty sure this is a left-over from making libarrow python-independent?
To fix this, the line quoted above should be removed, and the conda-linux tests still pass. Ideally, there should only be one plasma-store-server binary being installed.
Component(s)
C++ - Plasma

I'm pretty sure this is a left-over from making libarrow python-independent?

This is not related. $PREFIX/lib/python3.x/site-packages/pyarrow/plasma-store-server is for users who don't have system Apache Arrow C++. (For example, pyarrow wheel users.)
We can stop installing $PREFIX/lib/python3.x/site-packages/pyarrow/plasma-store-server by the following:
diff --git a/dev/tasks/conda-recipes/arrow-cpp/build-pyarrow.sh b/dev/tasks/conda-recipes/arrow-cpp/build-pyarrow.sh
old mode 100644
new mode 100755
index 692ffb7806..98c0fa9181
--- a/dev/tasks/conda-recipes/arrow-cpp/build-pyarrow.sh
+++ b/dev/tasks/conda-recipes/arrow-cpp/build-pyarrow.sh
@@ -9,6 +9,7 @@ export PARQUET_HOME=$PREFIX
 export SETUPTOOLS_SCM_PRETEND_VERSION=$PKG_VERSION
 export PYARROW_BUILD_TYPE=release
 export PYARROW_BUNDLE_ARROW_CPP_HEADERS=0
+export PYARROW_BUNDLE_PLASMA_EXECUTABLE=0
 export PYARROW_WITH_DATASET=1
 export PYARROW_WITH_FLIGHT=1
 export PYARROW_WITH_GANDIVA=1

See also:

https://github.com/apache/arrow/blob/apache-arrow-10.0.1/python/setup.py#L202-L203
https://github.com/apache/arrow/blob/apache-arrow-10.0.1/python/setup.py#L495-L501

Since plasma got removed, I'm closing this issue.


Nil senderId warning

I keep receiving this warning:

<FIRInstanceID/WARNING> Firebase messaging not setup correctly, nil senderID.

on every app start. What is it caused by?
In my application:didFinishLaunchingWithOptions: method, the only call that's related to Firebase is [FIRApp configure].

I assume that your GoogleServices-Info.plist file contains a valid GCM_SENDER_ID value. Getting it on every app start is strange. I'm not able to reproduce this, could you be more specific about what Firebase features you are using?

Yes, the sender id is present and is valid. I'm using the Messaging part.

That warning would be logged if an attempt to retrieve the IID token is made before the Sender ID of the InstanceID was set. You should check to make sure that you are not calling [InstanceID token] somewhere very early. If that is not the case I will file an internal bug to dig deeper into this warning log.
If you are only using Messaging and you are getting your IID token, then you can ignore this warning and we will clean it up in a future release.
Since I'm unable to reproduce it, could you give me some specifics about the deivice and iOS version you are seeing this issue with and have you tried multiple devices?

And when is the Sender ID set? In the [FIRApp configure] call? If yes, I'm only accessing the token after that call. More specifically, in the kFIRInstanceIDTokenRefreshNotification notification handler and in the applicationDidBecomeActive:.
I tested it on iPad Mini 2 Retina with iOS 9.1 and on a couple of iPhone 5s, iPhone 6 and iPhone 6s with iOS 10.1 and again on an iPhone 6s with iOS 10.2.

Removing or delaying the call to [FIRApp configure] I'm able to get that log msg.
Could you add appropriate logging to confirm whether the error is occurring in the token refresh callback or in applicationDidBecomeActive?

@revolter Seems like something is weird with your GoogleService-info file. Can you try re-downloading it? Head to the Firebase console, click the gear in the upper-left and select project settings, make sure your app is selected, and then click the download button labeled GoogleService-info.plist. Delete your old GoogleService file from your xcode project, then drag in the new one. See if that helps at all...

Firstly, how can it get corrupted? It actually downloaded it automatically for me when I went through the starting guide IIRC.
Secondly, something's fishy, I have 3 apps in Firebase, each with different Client ID, but after downloading the plist files again, indeed the new ones are different, but now the Client ID is the same between these 3 apps, and previously it was unique. Did the id generation suddenly change?

I downloaded the files again and this time, nothing is changed in git. So the original issue is not related to the plist files.

@kroikie, No, they're not the problem:
2016-12-19 15:45:54.387: <FIRInstanceID/WARNING> Firebase messaging not setup correctly, nil senderID.
...
2016-12-19 15:45:54.861419 Mondly Korean[3160:1017315] FIREBASE: Debug: AppDelegate.m:528 applicationDidBecomeActive: enter
2016-12-19 15:45:54.902620 Mondly Korean[3160:1017315] FIREBASE: Debug: AppDelegate.m:555 applicationDidBecomeActive: connect
2016-12-19 15:45:54.902665 Mondly Korean[3160:1017315] FIREBASE: Debug: AppDelegate.m:696 connectToFirebase enter
2016-12-19 15:45:54.907479 Mondly Korean[3160:1017315] FIREBASE: Debug: AppDelegate.m:764 connectToFirebase exit
2016-12-19 15:45:54.907528 Mondly Korean[3160:1017315] FIREBASE: Debug: AppDelegate.m:559 applicationDidBecomeActive: exit

As you can see, the applicationDidBecomeActive: is called ~475 milliseconds after the warning is printed.

Hi @revolter could you check when you are getting the token, I'm thinking that you may be requesting the token before configure.

That's what I did for my last comment.

This issue has staled pretty significantly. The Firebase messaging not setup correctly, nil senderID warning has since been entirely removed from the code in InstanceID.
Sorry we were unable to resolve your issue on time.


Add transparency support for LightmapGI

Salvages  #90109 (co-authored by @Guerro323)
Fixes https://github.com/godotengine/godot/issues/77590
I added the required changes for compatibility and adjusted the algorithm to the antialiasing of direct light samples that was introduced awhile ago.
Although unrelated to this PR (observable in master), there seems to be a regression/change of behavior that shadows of lights with size 0 appear much softer, depending on the texel scale. I know, a higher texel scale increases the resolution of the light map, but compared to the screenshots of the original PR it's definitely different. Maybe this new behavior is desired, because hard shadows can look bad on low-res light maps.

Note
(Copied from the original PR)
The culling logic was updated in the Lightmapper to correctly support Back and Disabled cull modes.
To preserve the current behavior and to not have any breaking change, the first direct light rays will retain the old behavior where light is blocked even if it should be culled.
This behavior is still needed otherwise there would be holes in the shadows of penetrated meshes (which can be quite common) and would need the material to be updated to Disabled cull mode, which may not be intuitive in most cases.
TL;DR: There should be no breaking changes on existing scenes. This do need some more testing but all my scenes looked correct.

The issue that @Calinou found is tricky. So far I found out that the artifact only appears when the light direction and the surface are orthogonal to eachother. Rotating the directional light slightly removes it.

Update: The artifacts are gone when this part is commented out (trace_ray(...) in lm_compute.glsl):
if (icell != ivec3(hit_cell)) {
	// It's possible for the ray to hit a triangle in a position outside the bounds of the cell
	// if it's large enough to cover multiple ones. The hit must be ignored if this is the case.
	continue;
}

Maybe @DarioSamo could give some insight here, as I'm not that familiar with the lightmapper.

Update: I could confirm that the original PR also had these issues. Furthermore, I found out the artifacts are gone when this part is commented out (trace_ray(...) in lm_compute.glsl):
if (icell != ivec3(hit_cell)) {
	// It's possible for the ray to hit a triangle in a position outside the bounds of the cell
	// if it's large enough to cover multiple ones. The hit must be ignored if this is the case.
	continue;
}

Doing that shouldn't be the solution, so maybe @DarioSamo could give some insight here, as I'm not that familiar with the lightmapper.

That code seems correct to me, I feel that'd probably indicate the DDA traversal is not reaching the cell it should. Large triangles can cover multiple cells, but the hit must be inside the cell picked by the DDA for it to be valid. It's not an easy area to debug I'm afraid.

Had a somewhat related issue which was a weird pattern being present when a directional light is only rotated on one axis and has shadow blur set to a value greater than 0 (the default is 1.0)
The light in this setup has shadow blur set to 1.0, and rotated at (-45.0, 0.0, 0.0)

Setting the blur to 0.0 removes the pattern

Another issue was light leaking when a point light had an integer position on the x-axis or z-axis, below is a picture where the light has a position of (0.0, 0.5, 2.0)

Moving the light, with or without the mesh, to (0.015, 0.5, 2.015) seemed to remove the lines, any value below that exhibited some leaks but they got thinner as the value increased.

Unlike the first issue, this one was not caused by shadow blur.
Tried giving it tolerances of 1.1, 1.414, 1.5, and 2.0, and found 2.0 to fix both issues faced. Not sure if 2.0 is too large to the point that it is equivalent to commenting out the code entirely.
The code used was length(vec3(icell) - hit_cell) > 1.5 instead of icell != ivec3(hit_cell)
Length > 1.5

Length > 2.0

Tested with Callinou's orthogonal MRP and 1.4 and beyond seemed to fix the issue.
Length > 1.3

Length > 1.5

Update:
Just for reference: The reason why this fails now is that trace_ray_any_hit was used before, which calls trace_ray with p_any_hit = true, returning RAY_ANY before the discussed optimization check.
@spookto Thanks for doing those experiments. I came to a similar conclusion with the method shown below: 0.5 - which is still unexpectedly large to my understanding (since I don't know where the error comes from, it's too large to be caused by numerical instability/floating point precision errors).
vec3 position = p_from + dir * distance;
if (any(lessThan(position, cell_min)) ||
		any(greaterThan(position, cell_max))) {
	// It's possible for the ray to hit a triangle in a position outside the bounds of the cell
	// if it's large enough to cover multiple ones. The hit can be ignored if this is the case.
	continue;
}

with
const float CELL_EPSILON = 0.5;
const vec3 cell_min = bake_params.to_cell_offset + vec3(icell) / bake_params.to_cell_size - CELL_EPSILON;
const vec3 cell_max = bake_params.to_cell_offset + vec3(icell + 1) / bake_params.to_cell_size + CELL_EPSILON;

However, this broke again when increasing the bounds of the lightmap domain (by placing objects further away).
Regardless of the actual cause: This is a pure optimization and not needed for the lightmapper to work properly. And the operations that are skipped aren't that costly, so we might as well remove the branch entirely.
In fact, my gut feeling was right, without this check the lightmap of my test scene baked in 26 seconds vs. 28 seconds before. The test scene consisted of many large and simple surfaces.
After that, I tested it with the more complex global illumination demo (https://github.com/godotengine/godot-demo-projects), which showed a very similar improvement (218s -> 201s, 7-8% faster, release build).
So, removing it fixes all weird artifacts and actually improves performance, although we might conceal the underlying issue.
I'm not sure how we should proceed at this point.

I was testing this and there are two related issues i noticed:

When multiple translucent surfaces overlap they get "cancelled" (blacked/shadowed) out very easy
Even if the translucent areas have color, the shadows are still treated as grayscale

Fortunately both are easy to fix with the following patch, which essentially "mixes" both the shadow contribution and surface color from all hits and applies the color to the final light contribution:
diff --git a/modules/lightmapper_rd/lm_compute.glsl b/modules/lightmapper_rd/lm_compute.glsl
index 12291de6ea..0b91cc5445 100644
--- a/modules/lightmapper_rd/lm_compute.glsl
+++ b/modules/lightmapper_rd/lm_compute.glsl
@@ -474,6 +474,7 @@ void trace_direct_light(vec3 p_position, vec3 p_normal, uint p_light_index, bool
 	}

 	float penumbra = 0.0;
+	vec3 colorization = vec3(1.0);
 	if (false) {
 		const bool use_soft_shadows = (light_data.size > 0.0);
 		const uint ray_count = AA_SAMPLES;
@@ -625,7 +626,8 @@ void trace_direct_light(vec3 p_position, vec3 p_normal, uint p_light_index, bool
 				}

 				if (contribute) {
-					penumbra = max(penumbra - hit_albedo.a - EPSILON, 0.0);
+					colorization = mix(colorization, hit_albedo.rgb, hit_albedo.a);
+					penumbra *= 1.0 - hit_albedo.a;
 				}

 				p_position = hit_position + r_light_dir * bake_params.bias;
@@ -639,7 +641,7 @@ void trace_direct_light(vec3 p_position, vec3 p_normal, uint p_light_index, bool
 		penumbra = clamp(penumbra, 0.0, 1.0);
 	}

-	r_light = light_data.color * light_data.energy * attenuation * penumbra;
+	r_light = light_data.color * light_data.energy * attenuation * colorization * penumbra;
 }

 #endif

Technically this isn't physically correct (that'd require collecting all hits, sorting by the distance from the ray origin and doing alpha blending for each one of them) but it is still better than not taking colors into account. It can easily be seen when bounces are at 0 as shown below.
Before the patch without bounces:

(notice the black blob where the two shadows from the planes at the bottom middle intersect)
After the patch without bounces:

(notice that instead of a black blob where the two shadows from the planes at the bottom middle intersect now there is some colorized light that comes from mixing the reddish translucent surface with the yellow translucent surface)
It is also visible with bounces, though less so as the indirect lighting give the impression that there is some colorization going on.
Before the patch with bounces:

After the patch with bounces:

I noticed that the soft shadow code is disabled so i didn't touch it to add the change.

Have you tested it with directional and with physically based lights?

Have you tested it with directional and with physically based lights?

I didn't try directional lights but they seem to work fine:

As for physical lights, i never used those before so i just enabled them in the advanced settings. I may have done something wrong since they look more broken than nice but the colors do get taken into account during mixing:

For comparison this is how master (i.e. without this PR and the patch i wrote above) currently looks:

As for physical lights, i never used those before so i just enabled them in the advanced settings. I may have done something wrong since they look more broken than nice but the colors do get taken into account during mixing:

Adding a camera attribute to your environment should fix it. It's an "expected behavior". See: #87531

Originally this was supposed to be only a salvage of https://github.com/godotengine/godot/pull/90109, and I was planning to do the other one after that, but if we can agree on combining the functionality I'd be happy to do that.
The main issue we need to decide on still remains: how we proceed with the DDA traversal fix.

Originally this was supposed to be only a salvage of #90109, and I was planning to do the other one after that, but if we can agree on combining the functionality I'd be happy to do that. The main issue we need to decide on still remains: how we proceed with the DDA traversal fix.

Let's keep this PR short and focused. We can add transparent color shortly after.
I would like to get @DarioSamo's input on the DDA traversal fix. If it is indeed just a small optimization, I have no problem removing it for now.

@Geometror A lot of the performance optimizations I made were using the scene from here: https://github.com/godotengine/godot/issues/75440. If you find no regressions with that, then the optimization can go.

Although we might conceal the underlying issue.

This also remains true, but I've reviewed the code that generates the triangle clusters and found no issues I could identify. I didn't code the DDA traversal myself either but it didn't look incorrect to me. Either of those elements could be wrong here and it's pretty tough to find out without a more exact testing setup on the CPU.

Trying the scene at #75440 seems impossible as the 'Plotting mesh into acceleration structure' step seems to freeze, however this freeze doesn't happen on v4.4dev6 and v4.3.
Also found that the console gets flooded with ERROR: servers/rendering/renderer_rd/storage_rd/material_storage.cpp:2040 - Parameter "shader" is null. in Forward+ and Mobile, and ERROR: drivers/gles3/storage/material_storage.cpp:2273 - Parameter "shader" is null.  in Compatibility, when baking a scene with a MeshInstance3D that has surface materials, which is common on imported meshes. However the error messages don't seem to cause any visible issues in the baking result.

Making the mesh unique and then clearing its surface_0 material seems to remove the error. Changing the mesh's override_material doesn't seem to change the error's behavior.
Issues I previously experienced have been fixed. Thanks a lot. :smile:
MRP for the error
light_error_mrp.zip

Tried latest artifact. Errors don't print and it no longer freezes on the plotting step.
Baking the sun temple looks lighter compared to 4.4dev6.
There are also small light leaks in the corners seen in the global illumination demo.

@spookto Thanks a lot for testing, but just to save you time, sometimes I do a push to sync the progress between my devices (which can be in a broken state). Usually I write a comment whenever meaningful progress was made.
 The sun temple scene completely breaks when the cell check discussed above isn't in place (only after #85653 and so far I couldn't figure out why).
There are also some additional light leaks along seams, so I'm going to mark this as draft since it clearly isn't ready and consumes a lot more time than originally anticipated.
With cell check/without before #85653 it looks like that (no lights enabled besides sun)

I was finally able to fix all issues:

The DDA algorithm had a small issue in the way the cells were traversed that caused rays parallel to and close to grid planes to miss. By fixing that, the discussed cell check could be kept without causing grid line artifacts.
Removed shader_get_cull_mode in favor of material_get_cull_mode since we only have the material RID per triangle and fixed the light leaks along edges

As expected, baking of the sun temple scene is a bit slower (since the scene contains transparent vegetation), but not too bad. (90s -> 111s, default of max. 8 transparency rays)
The original PR had a default of 64 transparency rays, but I think for most scenes that is way to high, so I changed it to 8.
Sun temple with texel scale set to 2

Thanks!


Uncaught SoapFault exception: [a:ErrorSchemaValidation] .... The string '2017-04-21' is not a valid DateTime value.

Version (e.g. 1.0, dev-master): 1.0, dev-master
PHP version: 5.5.38-1
Microsoft Exchange version: 2013
Description of problem:
I am trying to use this example https://github.com/jamesiarmes/php-ews/blob/master/examples/user/meeting-suggestions.php and I get the error below.
$start = new DateTime('tomorrow 00:00:00');
$end = new DateTime('next thursday 00:00:00');
$version = Client::VERSION_2013;

PHP Fatal error:  Uncaught SoapFault exception: [a:ErrorSchemaValidation] The request failed schema validation: The 'http://schemas.microsoft.com/exchange/services/2006/types:StartTime' element is invalid - The value '2017-04-21' is invalid according to its datatype 'http://www.w3.org/2001/XMLSchema:dateTime' - The string '2017-04-21' is not a valid DateTime value.
Additional details:

I am unable to reproduce your issue using that example. Could you post your full request code?

I think the format is wrong. Try
$start = '2015-12-24T00:00:00';
or

$start = new DateTime('tomorrow 00:00:00');
$start = $start->format('Y-m-d').'T00:00:00';

because your $start is a whole object and the datatype wants only a string in a special datetime-string-format....


Feature Request: store locations in jumplist

Thanks for the excellent plugin! I would like to suggest a small tweak to better integrate with Neovim's existing navigation tools - saving the current location to the jumplist before jumping to a new symbol.
This would allow users to move between symbols with a combination of aerial and the standard <c-o>/<c-i>/etc. jump operators.
I think this should only take a 1-line (or so) change around here (although I haven't read through the codebase in depth): https://github.com/stevearc/aerial.nvim/blob/aff1bb8fecff83d3e3a2d544c4d4e6d65718bd19/lua/aerial/navigation.lua#L237-L241
Specifically, it should suffice to set the ' register with m' just before jumping, if the user has jumping configured. If you're open to this, I'd be happy to make a PR.

This seems like a good idea, sure!

That will be a great feature, I really miss it

Finally got around to this in #305, sorry for the delay.

Closed by #424


[RESOLVED] Unavailable by ICMP ping

Problem started at 23:32:16 on 2022.10.01
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Operational data: Down (0)
Original problem ID: 3786
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23133&eventid=3786

Problem has been resolved in 41m 0s at 00:13:16 on 2022.10.02
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Original problem ID: 3786


Host frequently completely freezes, displaying weird graphics

Description

Quite frequently after an unsuccessful connection attempt from the client (Oculus Quest 2), my KDE desktop completeley freezes, displaying some weirdly distorted graphics. Some examples:

Sometimes I can switch over to one of the virtual consoles or zap the X server, sometimes the system is completely frozen; but even in the former case, I'm usually  unable to restart X (when I do so, the system just hangs).
General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environement
Hardware
Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
https://linux-hardware.org/?probe=bc0462d8e3
CPU:
GPU:
Audio:
Installation
ALVR Version:
17.0.1+1643781622+0541c19e on both client and server
SteamVR Version:
1.20.4
Install Type:

[x] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):

Debian GNU/Linux 11 (bullseye) (up-to-date)

Last time this happened, I managed to switch to a virtual terminal, where the following message was printed repeatedly in an interval of a few seconds:
[drm:amdgpu_job_timeout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
Any ideas...?

Try this:

disable steamvr home, this should fix gfx ring failure on polaris, but it still crashes for me in comp ring
disable async reprojection ("enableLinuxVulkanAsync": false in SteamVR/resources/settings/default.vrsettings )
disable realtime SteamVR capabilities:
add return 0 in SteamVR/bin/vrstartup.sh here:

function SteamVRLauncherSetup()
{
        return 0

and reset capabilities on bin/linux64/vrcompositor-launcher by setcap -r
setcap -r ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher

Last step will not work if you are using SteamVR 1.14, because of bug in SDL, but should work with recent versions, disabling async reprojection should fix jitter on recent SteamVR versions. Disabling realtime capabilities seems to fix most of GPU hangs, realtime vulkan vrcompositor implementation seems to do some weird things.
And it is recommended to use recent git mesa version on polaris because they committed very important fix: :https://www.phoronix.com/scan.php?page=news_item&px=AMD-VCE-Better-Speed

Did it fix GPU crash? Recent alvr nightly disabled async reprojection by default. The only thing left is disabling realtime priority if it still works unstable with amd (but it maybe kernel-specific)

I'm currently unable to do any further investigation since for the last few days SteamVR has been refusing to start, complaining about "a key component not working properly (307)". I'll keep trying, though, always using the latest ALVR from master, compilation of which works like a charm. Great build script! :)

@tcrass please read the release notes
On AMD GPUs you need to downgrade Mesa to 21.0. If you can’t downgrade Mesa and want to keep the previous behavior (jitter) you have to enable async reprojection in Settings->Video->Advanced options. Failing to do so will result in SteamVR crashing with error 307.

l'll keep trying, though, always using the latest ALVR from master, compilation of which works like a charm. Great build script! :)
thats because what you need to do in the release version has been automated using stuff from wgpu to detect your vendor and apply that setting accordingly
As this issue really doesn't have a use being open as its own and everything that can be done is done other than releasing a new version with the automated patch I would close this.

Also in the patch notes(nevermind not in the patch notes :eyes: ) you aren't suppose to put on your headset before setting that setting failing to do so will guarantee a crash.

Hi ColdIce1605,

As this issue really doesn't have a use being open as its own and everything that can be done is done other than releasing a new version with the automated patch I would close this.

agreed!
However...

@tcrass please read the release notes

...I'm not quite sure which release/patch notes you are referring to (ALVR? Mesa? Which version/commit?). Could you please provide a link?
Cheers --
Torsten


Upgrade GoVpp

Coverage decreased (-0.06%) to 76.216% when pulling 2360652d7ca411a15007825817ddc87d8f25755e on lukasmacko:master into 4b2227f142cfdb096e8aaf535b71d5aea47ac2e6 on contiv:master.


[MINOR][DOCS] Clarify config descriptions

This aligns with the doc change here: 10680
Change Logs
Minor docs update.
Impact
Minor docs update.
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed


Public Methods unable to use

The public methods mentioned in document they are unable to import and unavailable for use

What do you mean? You should be able to access public methods using ref. Here is an example of usage:
import React, { useRef } from 'react';
import { View } from 'react-native';
import InstagramStories, { InstagramStoriesPublicMethods } from '@birdwingo/react-native-instagram-stories';

const YourComponent = () => {

  const ref = useRef( null ); // if using typescript - useRef<InstagramStoriesPublicMethods>( null )

  const stories = [{
    id: 'user1',
    name: 'User 1',
    imgUrl: 'user1-profile-image-url',
    stories: [
      { id: 'story1', source: { uri: 'story1-image-url' } },
      { id: 'story2', source: { uri: 'story1-video-url' }, mediaType: 'video' },
      // ...
    ]}, // ...
  ];

  const setStories = () => ref.current?.setStories( stories );

  return (
    <View>
      <InstagramStories
        ref={ref}
        stories={stories}
        // ...
      />
     <Pressable onPress={setStories}>{...}</Pressable>
    </View>
  );
};

export default YourComponent;

If there is any problem with any method, let me know. Thank you

thanks for guide me
these thins was not mentioned in documents so that was confusing for me

Sure, no problem. I will edit readme in next version.


Partially deserialize the message?

I have a use case that I want to check a message if it has Header field, then deserialize only this part to get the timestamp in it. Can I use this library to implement this efficiently?

Yes, but I am away from the office right now and it is not the most documented feature. I will give you more details the next week

I created an example for you here: https://github.com/facontidavide/type_introspection_tests/blob/master/example/selective_deserialization.cpp
Note that the raw_buffer that I create manually here, is usually obtained from ShapeShifter or Rosbag Messages.

@facontidavide Thank you very much. The example works like a charm.
I also find a way to check if a connection/type has any header.
Parser parser;
const ROSType header_type(datatype<std_msgs::Header>());
std::map<std::string, bool> topics_has_header;

for (auto &conn : view.getConnections()) {
  parser.registerMessageDefinition(conn->topic, ROSType(conn->datatype),
                                   conn->msg_def);
  if (topics_has_header.find(conn->topic) != topics_has_header.end())
    continue;
  auto msg_info = parser.getMessageInfo(conn->topic);
  bool has_header =
      nullptr != parser.getMessageByType(header_type, *msg_info);
  topics_has_header.emplace(conn->topic, has_header);
}


Is it possible make some 'processing' for data?

What if I want do some actions to on api calls? Like prepare data, save in my own way.. resend it to another service? Any hooks for this?

It’s a fundamental feature for microrest to be able to hook the default API’s behaviour. That’s what we try to do using middlewares based on stackPHP. This work is visible on the branch stackphp. But it’s a work in (realy slow) progress…

So is it possible? How?

In fact, It isn't yet possible. But the idea is to use microrest as middleware (thank's to stackphp), and by adding your own middleware after Microrest be able to override the http response.


compare cognate judgments

In [1]: from lingpy import *

In [2]: lex = LexStat.from_cldf('cldf/cldf-metadata.json')

In [5]: lex.renumber("cognacy", "cogid")

In [6]: lex.cluster(method="sca", threshold=0.45, ref="scaid")

In [7]: from lingpy.evaluate.acd import bcubes

In [8]: bcubes(lex, "cogid", "scaid")
*************************
* B-Cubed-Scores        *
* --------------------- *
* Precision:     0.8266 *
* Recall:        0.6360 *
* F-Scores:      0.7189 *
*************************'

This does not look very hopeful to me. I think a clearer error analysis in edictor would be best.
But an exemplary analysis can be done with lingpy:
In [14]: from lingpy.evaluate.acd import bcubes, diff

In [14]: diff(lex, "cogid", "scaid")

This yields for "yellow":
Concept: yellow, False Positives: yes, False Negatives: yes
Acoma               	kʲú/utʃí/in̉/ni     	   1	   1
ProtoKeresan        	kʲú/utʃin̉/nɪ       	   1	   1
SantaAna            	kʲú/utʃin̉/nɪ       	   1	   1
SantaDomingo        	kʲú/utʃin̉/nɪ       	   1	   1
AztecTetelcingo     	kostiːk             	   2	   2
AztecZacapoaxtla    	kostik              	   2	   2
ClassicalAztec      	kos+tli             	   2	   6
Cahuilla            	té/esnek+iʃ         	   4	   4
Chemehuevi          	oasiak+ka           	   5	   5
Comanche            	oha                 	   5	   7
NorthernPaiute      	oha                 	   5	   7
SouthernUte         	oá/a+kːatɨ          	   5	  16
Mono                	oha+pono            	   5	  21
NorthernTepehuan    	oama                	   5	  23
Papago              	s+oam               	   5	  23
PimaDeOnavas        	s+oam               	   5	  23
SoutheasternTepehuan	uam                 	   5	  23
Tubatulabel         	ú/uam               	   5	  23
Pannamint           	oa                  	   5	  25
ShoshoniGosiute     	oa                  	   5	  25
SouthernPaiute      	oä/æ                	   5	  25
Comecrudo           	jalu+i              	   8	   8
Kitanemuk           	7/ʔamariy/jo7/ʔ     	   8	  18
Tubar               	kí/isara+kar        	   8	  39
Zuni                	lh/l̥upzʔi          	   8	  42
Cora                	ty/jáu/aumwa        	   9	   9
Cupeno              	kɨnɨkí̵/ɨnɨʔɨ+ʃ     	  10	  10
Yaqui               	huːsai              	  11	   7
Eudeve              	savei               	  11	  11
Mayo                	sawá/ari            	  11	  11
Tarahumara          	sawaró/oa+me        	  11	  11
Mayo                	sawá/ali            	  11	  11
Yaqui               	sawái/ai            	  11	  11
Guarijio            	saʔwató/o+me        	  11	  13
Opata               	saguăi              	  11	  14
SanJuanPuebloTewa   	tsˀáy/aiy/jiʔ       	  11	  15
Gabrielino          	pay/jū/uːwit        	  12	  12
Hopi                	siká/aŋpɨ           	  14	  14
Huichol             	taraɨy/je           	  15	  15
Kawaiisu            	hɨvɨ+gidɨ           	  16	  16
Kiowa               	guɔtˀ+kˀoː          	  17	  17
Luiseno             	aṣ/ʂó/o+ʔṣ/ʂu+ʃ     	  19	  19
Pipil               	tultik              	  28	   2
Serrano             	ṣ/ʂac̣/ʈʂiːc̣/ʈʂi+ʔn	  33	  33
Tubar               	mó/okʷasa+kara      	  44	  39

The major problem here is the cognate judgment: there are plenty of partial cognates, and this prevents the automated approach to recognize them.

I made a test one should NOT do: testing with lexstat despite low coverage.
lex.cluster(runs=10000)
lex.cluster(method="lexstat", threshold=0.55, ref="lexstatid")
bcubes(lex, "cogid", "lexstatid")
In [27]: bcubes(lex, "cogid", "lexstatid")
*************************
* B-Cubed-Scores        *
* --------------------- *
* Precision:     0.9530 *
* Recall:        0.5466 *
* F-Scores:      0.6947 *
*************************'
Out[27]: (0.9529780395511854, 0.5466122427624786, 0.6947357150097971)

What the results tell us is: STRICT cognates, backed by lexstat, seem to be very clear (high precision). But lexstat fails to detect the deeper signal, which is why it's recall sucks. Yet this has two major reasons:

partial cognates (we do not test automatically and the annotation deals with partial cognates in an ad-hoc manner, but it is not trivial to deal with this consistently anyway)
languages with low coverage: we have often only 100 words per language, so less chance to retrieve sound correspondences for all language pairs

I think, in summary, one can say that this means that the cognates are okay. I'd favor to have a much more thorough analysis with partial cognates, but there's a core of cognates which are substantiated by the automated method and the manual judgments. Comparing the cases where the manual judgments go farther can probably reveal where the automated method cannot find enough signal, but humans can, as they use additional evidence.

Okay, with the smaller selection of about 38 languages, we get:
*************************
* B-Cubed-Scores        *
* --------------------- *
* Precision:     0.9517 *
* Recall:        0.5829 *
* F-Scores:      0.7230 *
*************************'

So still not really a lot with the default settings, but it shows the methodological dilemma: deep cognates cannot be identified by the method (yet/ever) ;)

Code is in scripts/cognates.py. Requires cldf/cltoolkit (and the code there may change)


DEP Dependencies for CMS 6

Issue https://github.com/silverstripe/.github/issues/191

We'll create a CMS 6 branch for now and look at support at a later date


[feature request] CronJob support

It looks like CronJob is not supported kind.
Any plans to add it?

I've moved this to the schema repo which is where all Score features start :)


"react/destructuring-assignment": should NOT have additional properties

Hello,
I'm encountering the error
Oops! Something went wrong! :(

ESLint: 8.12.0

Error: .eslintrc.js#overrides[4]:
	Configuration for rule "react/destructuring-assignment" is invalid:
	Value {"ignoreClassFields":false,"destructureInSignature":"always"} should NOT have additional properties.

with the rule
        "react/destructuring-assignment": [
          `warn`,
          `always`,
          { ignoreClassFields: false, destructureInSignature: `always` },
        ],

I think it's the destructureInSignature property causing issues. Not sure why, lifted it off of the docs and subbed in values. I don't think there are any typos nor conflicting rules.
Additional information:
My eslint packages are:
    "eslint": "^8.12.0",
    "eslint-config-airbnb": "^19.0.4",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-graphql": "^4.0.0",
    "eslint-plugin-import": "^2.25.4",
    "eslint-plugin-jsx-a11y": "^6.5.1",
    "eslint-plugin-prettier": "^4.0.0",
    "eslint-plugin-react": "^7.29.4",
    "eslint-plugin-react-hooks": "^4.3.0",

Because it’s not published yet. You need to look at the docs on the latest tagged version, not on the default branch (for every repo on github).

Oh, I see. How do we view the docs on the latest tagged version?


composer: PHP 7 added

Also drop default value for notifications.

Btw, could you also add this package to Travis? It looks like it's not triggered.

Done :D Thanks for that warning! :o

Thanks!


filter is not working for the main name

django.core.exceptions.FieldError: Cannot resolve keyword 'name' into field. Choices are: city_id, country, created, daily, hourly, id, latitude, longitude, name_ar, name_de, name_en, name_es, name_fr, name_it, name_nl, name_ru, name_sv, name_tr, name_ua, name_zh_cn, name_zh_tw, state, updated, users, weather
cities.filter(name="test")
any idea to search over all languages with the same key name?

Yes, that's by design.
You could do something like this:
from translated_fields import to_attribute

cities.filter(**{to_attribute("name"): "test"})

(See here for the reasoning https://github.com/matthiask/django-translated-fields#other-features)

Thank you for answering
if i want use the functions of the field
contains
example
            kwargs = {
                f"name_{language}__icontains": name,
                f"name_en__icontains": name
            }
            cities = cities.filter(**kwargs)

Thank you for your hard works <3

I'll assume that you have found a solution which works for you. I re-read your initial question again and there's a way to do this as well, for example as follows:
from django.db.models import Q
q = Q{**{City.name.fields[0]: "test"})
for field in City.name.fields[1:]:
    q |= Q(**{field: "test"})
cities.filter(q)

The idea is to generate a Q() object for each language's name field and OR them together (q | q)


Fix docs for Color

Search doesn't come up with any results since Color is just aliased to Colour:
https://docs.disnake.dev/en/latest/search.html?q=Color.blurple
https://github.com/DisnakeDev/disnake/blob/860bede15391cdbf9b048359c48e1b66ad826cee/disnake/colour.py#L333

relevant project card

I already have an implementation for that, I will commit it in #153.

Update: it looks like sphinx/rtd doesn't have an alias thing, so I decided to directly do it in the JavaScript

As I told both shiftinv and Victorsitou earlier I didn't find any fuzzy/alias search for sphinx. The JS implementation looks like the cleanest solution to avoid making duplicate entries for Color and Colour.


Update an Open Dropdown Menu

Right now I'm putting together a hacky solution using the search functionality provided in this framework.
However, overall, I'd like the ability to dynamically update the dropdown menu items on a dropdown that's open.
My use case is as follows:
When the user first taps on the dropdown, we make an async call to get the items. While this call is occurring I show a single item, that represents the loading state. Once these items have been fetched, I'd like to push them into the already open menu.  As of right now, I don't think there's a way to update the state of the DropDownMenu, besides hacking together something with the search controller (which is what I'm going to do)
Edit: My hack unfortunately doesn't even work either :( This is because the searchController only goes through the items on the DropDownRoute, which is not updated with the latest items either

Sure, give it a try.
I think it's more difficult than that, check _handleTap() method.
I think we need ValueListenableBuilder to achieve this.

This is a hacky solution for now that auto re-open the dropdown menu in milliseconds:
  final dropdownKey = GlobalKey<DropdownButton2State>();
  bool _isOpen = false;

  List<String>? items;
  String? selectedValue;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: DropdownButtonHideUnderline(
          child: DropdownButton2(
            key: dropdownKey,
            hint: Text(
              'Select Item',
              style: TextStyle(
                fontSize: 14,
                color: Theme.of(context).hintColor,
              ),
            ),
            onMenuStateChange: (bool isOpen) async {
              _isOpen = isOpen;
              if (isOpen && items == null) {
                //Simulate api call delay to show loading for 3 seconds
                await Future.delayed(const Duration(seconds: 3));
                setState(() {
                  items = [
                    'Item1',
                    'Item2',
                    'Item3',
                    'Item4',
                  ];
                });

                //Return if the user already closed the menu
                if (!_isOpen) return;

                Navigator.of(context).pop();
                //await removeDropdownRoute to avoid _dropdownRoute != null Exception
                await Future.delayed(const Duration(milliseconds: 100));
                dropdownKey.currentState!.callTap();
              }
            },
            items: items == null
                ? [
                    const DropdownMenuItem<String>(
                      enabled: false,
                      child: Center(
                        child: CircularProgressIndicator(),
                      ),
                    ),
                  ]
                : items!
                    .map((item) => DropdownMenuItem<String>(
                          value: item,
                          enabled: false,
                          child: Text(
                            item,
                            style: const TextStyle(
                              fontSize: 14,
                            ),
                          ),
                        ))
                    .toList(),
            value: selectedValue,
            onChanged: (value) {
              setState(() {
                selectedValue = value as String;
              });
            },
            buttonHeight: 40,
            buttonWidth: 140,
          ),
        ),
      ),
    );
  }

https://user-images.githubusercontent.com/70890146/202493174-2db2b0ce-f5a7-48a1-8664-8d692c3db20c.mov

Thank you for that @AhmedLSayed9 .  Unfortunately; I have another wrench to throw into things -- I'm using the DropdownButtonFormField2; and so it's state is not DropDownButton2State, which complicates me calling callTap().

You can use dropdownButtonKey property now in v1.9.1
I think a secondary key to access the child is more proper 🙂

@AhmedLSayed9  v1.9.1 is working based on your solution above, thank you ahmed!
One thing I noticed though, is that I'm seeing the following error in the log (after updating from v1.8.9 -> v1.9.1 [I tried v1.9.0 as well]):
The following _CastError was thrown during paint():
Null check operator used on a null value

The relevant error-causing widget was:
  DropdownButtonFormField2<_DropDownWrapper>-[GlobalKey#07451] DropdownButtonFormField2:file:///Users/Cody/Dev/Work/Verfico/flutter_app/lib/views/themed/themed_dropdown_form_field.dart:65:20
When the exception was thrown, this was the stack:
#0      RenderIndexedStack.debugDescribeChildren (package:flutter/src/rendering/stack.dart:793:26)
#1      DiagnosticableTreeNode.getChildren (package:flutter/src/foundation/diagnostics.dart:2985:48)
#2      DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1620:32)
#3      DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#4      DiagnosticsNode.toJsonList.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1686:19)
#5      MappedListIterable.elementAt (dart:_internal/iterable.dart:413:31)
#6      ListIterator.moveNext (dart:_internal/iterable.dart:342:26)
#7      new _GrowableList._ofEfficientLengthIterable (dart:core-patch/growable_array.dart:189:27)
#8      new _GrowableList.of (dart:core-patch/growable_array.dart:150:28)
#9      new List.of (dart:core-patch/array_patch.dart:51:28)
#10     ListIterable.toList (dart:_internal/iterable.dart:213:44)
#11     DiagnosticsNode.toJsonList (package:flutter/src/foundation/diagnostics.dart:1687:8)
#12     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1654:23)
#13     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#14     DiagnosticsNode.toJsonList.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1686:19)
#15     MappedListIterable.elementAt (dart:_internal/iterable.dart:413:31)
#16     ListIterator.moveNext (dart:_internal/iterable.dart:342:26)
#17     new _GrowableList._ofEfficientLengthIterable (dart:core-patch/growable_array.dart:189:27)
#18     new _GrowableList.of (dart:core-patch/growable_array.dart:150:28)
#19     new List.of (dart:core-patch/array_patch.dart:51:28)
#20     ListIterable.toList (dart:_internal/iterable.dart:213:44)
#21     DiagnosticsNode.toJsonList (package:flutter/src/foundation/diagnostics.dart:1687:8)
#22     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1654:23)
#23     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#24     DiagnosticsNode.toJsonList.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1686:19)
#25     MappedListIterable.elementAt (dart:_internal/iterable.dart:413:31)
#26     ListIterator.moveNext (dart:_internal/iterable.dart:342:26)
#27     new _GrowableList._ofEfficientLengthIterable (dart:core-patch/growable_array.dart:189:27)
#28     new _GrowableList.of (dart:core-patch/growable_array.dart:150:28)
#29     new List.of (dart:core-patch/array_patch.dart:51:28)
#30     ListIterable.toList (dart:_internal/iterable.dart:213:44)
#31     DiagnosticsNode.toJsonList (package:flutter/src/foundation/diagnostics.dart:1687:8)
#32     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1654:23)
#33     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#34     DiagnosticsNode.toJsonList.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1686:19)
#35     MappedListIterable.elementAt (dart:_internal/iterable.dart:413:31)
#36     ListIterator.moveNext (dart:_internal/iterable.dart:342:26)
#37     new _GrowableList._ofEfficientLengthIterable (dart:core-patch/growable_array.dart:189:27)
#38     new _GrowableList.of (dart:core-patch/growable_array.dart:150:28)
#39     new List.of (dart:core-patch/array_patch.dart:51:28)
#40     ListIterable.toList (dart:_internal/iterable.dart:213:44)
#41     DiagnosticsNode.toJsonList (package:flutter/src/foundation/diagnostics.dart:1687:8)
#42     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1654:23)
#43     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#44     DiagnosticsNode.toJsonList.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1686:19)
#45     MappedListIterable.elementAt (dart:_internal/iterable.dart:413:31)
#46     ListIterator.moveNext (dart:_internal/iterable.dart:342:26)
#47     new _GrowableList._ofEfficientLengthIterable (dart:core-patch/growable_array.dart:189:27)
#48     new _GrowableList.of (dart:core-patch/growable_array.dart:150:28)
#49     new List.of (dart:core-patch/array_patch.dart:51:28)
#50     ListIterable.toList (dart:_internal/iterable.dart:213:44)
#51     DiagnosticsNode.toJsonList (package:flutter/src/foundation/diagnostics.dart:1687:8)
#52     DiagnosticsNode.toJsonMap.<anonymous closure> (package:flutter/src/foundation/diagnostics.dart:1648:25)
#53     DiagnosticsNode.toJsonMap (package:flutter/src/foundation/diagnostics.dart:1661:6)
#54     WidgetInspectorService._nodeToJson (package:flutter/src/widgets/widget_inspector.dart:1606:18)
#55     WidgetInspectorService._reportStructuredError (package:flutter/src/widgets/widget_inspector.dart:937:44)
#56     FlutterError.reportError (package:flutter/src/foundation/assertions.dart:1184:14)
#57     RenderObject._debugReportException (package:flutter/src/rendering/object.dart:1519:18)
#58     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2800:7)
#59     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#60     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#61     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#62     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#63     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#64     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#65     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#66     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#67     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#68     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#69     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#70     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#71     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#72     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#73     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#74     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#75     _RenderDecoration.paint.doPaint (package:flutter/src/material/input_decorator.dart:1504:17)
#76     _RenderDecoration.paint (package:flutter/src/material/input_decorator.dart:1559:5)
#77     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#78     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#79     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:144:15)
#80     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#81     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#82     RenderBoxContainerDefaultsMixin.defaultPaint (package:flutter/src/rendering/box.dart:2900:15)
#83     RenderFlex.paint (package:flutter/src/rendering/flex.dart:1088:7)
#84     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#85     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:239:13)
#86     _RenderSingleChildViewport.paint.paintContents (package:flutter/src/widgets/single_child_scroll_view.dart:562:17)
#87     PaintingContext.pushLayer (package:flutter/src/rendering/object.dart:460:12)
#88     PaintingContext.pushClipRect (package:flutter/src/rendering/object.dart:520:7)
#89     _RenderSingleChildViewport.paint (package:flutter/src/widgets/single_child_scroll_view.dart:566:40)
#90     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2796:7)
#91     PaintingContext._repaintCompositedChild (package:flutter/src/rendering/object.dart:155:11)
#92     PaintingContext.repaintCompositedChild (package:flutter/src/rendering/object.dart:98:5)
#93     PipelineOwner.flushPaint (package:flutter/src/rendering/object.dart:1116:31)
#94     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:515:19)
#95     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:884:13)
#96     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:378:5)
#97     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1175:15)
#98     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1104:9)
#99     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:1015:5)
#100    _invoke (dart:ui/hooks.dart:148:13)
#101    PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:318:5)
#102    _drawFrame (dart:ui/hooks.dart:115:31)
The following RenderObject was being processed when the exception was fired: RenderPointerListener#8b42c relayoutBoundary=up24
...  parentData: <none> (can use size)
...  constraints: BoxConstraints(w=363.4, 0.0<=h<=Infinity)
...  size: Size(363.4, 24.0)
...  behavior: opaque
...  listeners: down, panZoomStart
RenderObject: RenderPointerListener#8b42c relayoutBoundary=up24
  parentData: <none> (can use size)
  constraints: BoxConstraints(w=363.4, 0.0<=h<=Infinity)
  size: Size(363.4, 24.0)
  behavior: opaque
  listeners: down, panZoomStart
...  child: RenderConstrainedBox#fd169 relayoutBoundary=up25
...    parentData: <none> (can use size)
...    constraints: BoxConstraints(w=363.4, 0.0<=h<=Infinity)
...    size: Size(363.4, 24.0)
...    additionalConstraints: BoxConstraints(0.0<=w<=Infinity, h=24.0)
...    child: RenderPadding#a7621
...      parentData: <none> (can use size)
...      constraints: BoxConstraints(w=363.4, h=24.0)
...      size: Size(363.4, 24.0)
...      padding: EdgeInsets.zero
...      textDirection: ltr
...      child: RenderFlex#4853b OVERFLOWING
...        parentData: offset=Offset(0.0, 0.0) (can use size)
...        constraints: BoxConstraints(w=363.4, h=24.0)
...        size: Size(363.4, 24.0)
...        direction: horizontal
...        mainAxisAlignment: spaceBetween
...        mainAxisSize: min
...        crossAxisAlignment: center
...        textDirection: ltr
...        verticalDirection: down
...        child 1: RenderPadding#6818a relayoutBoundary=up1
...          parentData: offset=Offset(0.0, 0.0); flex=null; fit=null (can use size)
...          constraints: BoxConstraints(0.0<=w<=Infinity, 0.0<=h<=24.0)
...          size: Size(346.0, 24.0)
...          padding: EdgeInsets(16.0, 0.0, 16.0, 0.0)
...          textDirection: ltr
...        child 2: RenderSemanticsAnnotations#5fdb3 relayoutBoundary=up1
...          parentData: offset=Offset(346.0, 0.0); flex=null; fit=null (can use size)
...          constraints: BoxConstraints(0.0<=w<=Infinity, 0.0<=h<=24.0)
...          size: Size(24.0, 24.0)

This wasn't happening in the earlier version I mentioned above; so something may have been changed to cause this? :(

I'm unable to release the issue above. Can you provide a working sample that cause it?

@AhmedLSayed9 This seems to be an issue on my end. I refactored by code, and it's no longer an issue. Sorry about that!.  I'm editing my above comment so no one gets confused


Export Art

The ability to export the art for the cards, backgrounds, and icons would be incredibly valuable to anyone working to port old stacks to newer systems, or wanting to rescue old artwork.
If an export is beyond the scope of this project, just having a way to hide everything but the card or background art so someone can take a screenshot without buttons or fields would be useful.

Ok, I'll make a new version with what you are suggesting (including the list of the icons).
Would you be interested in global text export? I'm not sure how it could be done.

Would you be interested in global text export? I'm not sure in what format and in how many files the text could be exported.

This would be a very useful feature for me as well.

Ok then!

That would be amazing!
Also really useful would be if you could export  a text file with the data you display in the Info tab for buttons and fields, along with the position, size, and id, if possible. That would make it really easy for me to automate the process of porting my stacks.

I've made a new release  with these changes, HyperCardPreview 1.3.

This is great. Thank you!

Fantastic! Thank you!


TypeScript support for VS Code notebooks

🔍 Search Terms
"TypeScript", "VS Code", "VS Code notebooks", "notebook", "intellisense", "JavaScript cell"
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
We would like to have d.ts files affect JavaScript cells in a VS Code notebook. For the full context, the original feature request was for VS Code: https://github.com/microsoft/vscode/issues/195745 We were encouraged by the VS Code team to create a request here because intellisense functionality comes from TypeScript.
Currently, JavaScript cells in a VS Code notebook is using some non-configurable intellisense and cannot be affected by a jsconfig.json. It would be great if we could have this working for non-Jupyter notebooks. For example, in the "include" configuration in the jsconfig, in addition to **/*.js we could have **/*.ipynb and **/*.foobarnb.
📃 Motivating Example
VS Code notebooks are very powerful and are increasingly used to develop software. TypeScript intellisense is an extremely useful feature for JS/TS developers and it would benefit developers if you can use that in a notebook. Currently, you need to write your code in a *.js JavaScript file, configure the jsconfig to include that file, then repeatedly copy paste the file content into a JavaScript cell in a notebook.
💻 Use Cases
Multiple teams at my workplace are using a JavaScript notebook to develop software. We can't execute some code in a file using Node.js because we need some integrations that are only in the notebook. We need intellisense from various JavaScript classes we have that are given in the .d.ts files.
Currently, there are two workarounds we are using:

Live without intellisense - there is no autocompletion and you need to type your classes and functions correctly the first try or rely on the notebook to display a syntax error after you've run the code
Use existing intellisense in a JavaScript file, write your code in that file, then repeatedly copy paste the file contents into the JavaScript notebook to test your code

we have plugin support to add external files and external files that act as js using plugins getExternalFiles and vscode command to add extension support using protocol.Configure request which other plugins like vue etc use to add extra files to the project. This should use similar approach to extend the additional files to be added instead of any changes to tsserver

@sheetalkamat Thanks for your response. Can you explain what you mean by this the getExternalFiles and protocol.Configure? Is this something on jsconfig.json? Or is there some change that needs to be done in VS Code codebase?

Here are some links for language service plugins and how it interacts with tsserver:
https://github.com/Microsoft/TypeScript/wiki/Writing-a-Language-Service-Plugin
here is example of plugin that gives extra files using getExternalFiles https://github.com/angular/angular/blob/main/packages/language-service/src/ts_plugin.ts

@c3danielxu are you using some built-in functionality, or have you tried out https://github.com/DonJayamanne/typescript-notebook ?

Thanks @sheetalkamat I will take a look at the resources you linked. @DanielRosenwasser I have a custom implementation of a Node.js notebook (inspired by the TypeScript notebook) but the feature request is more generic. For example, even with minimal files I can go to definition for my class Calculator but does not work in TypeScript notebook.

@sheetalkamat @DanielRosenwasser I was under the impression that TypeScript cannot support notebooks natively due to not using the Language Server Protocol. Is that something that is on your radar or planned in the foreseeable future? That way VS Code can bump their TypeScript version and hopefully that will allow for intellisense in notebooks.

LSP is fairly unrelated to whether or not notebooks are supported. There are a slew of other concerns for some sort of in-house notebook support.

Creating a TypeScript language service plugin to provide intellisense support to VS Code notebooks. Thanks all for the help!


Moving original files to orig breaks mod.sh, should be copied

In the beginning of mod.sh the original Content folder gets moved to orig as well as DuckGame.exe. This will cause the script to fail because later when the exe is being patched it first complains that Content can't be found and then later we end up with an empty DuckGame.exe (0 bytes). Copying the folder rather than moving it should fix this.

This is weird because moving should be enough. The first step XnaToFna does is copy everything from the orig backup directory back into the game directory.
https://github.com/0x0ade/XnaToFna/blob/1607442eaf2e5cd5ffba7b5cbc02fa317d27faca/src/XnaToFnaUtil.cs#L124
For now, I'll update mod.sh to copy to the orig folder instead. I'll check the issue in XnaToFna as soon as I get back home.

XnaToFna errors when the directory Content can't be found (since it's now in orig). Don't know enough about it to tell if a step happens in the wrong order or something


utils: simplify and proof positions

proofpositions is needed for the new block download protocol that
requires the client to compute for which proof positions it needs.
Exporting gives utreexod the ability to call it.
Simplifying is just cherry on top and prevent possible infinite loop bugs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

48 of 48 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 81.934%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.02%

Covered Lines:
3084

Relevant Lines:
3764

💛  - Coveralls


Refactor utility functions in separate files

This PR intends to refactor utility functions present inside lib/Conversion/LowerDIP/LowerDIPPass.cpp into separate files. These files are created on the basis of their generic utility and DIP specific utility.
The main purpose of this change is to improve re-usability of these functions across the entire project (developers writing code after the merger of this change should use/improve already available implementation(s) instead of developing similar infrastructure over and over again).
Ref : https://github.com/buddy-compiler/buddy-mlir/pull/23#issuecomment-1155984380

@meshtag Please ping me when this PR is ready.


what's the meaning of the offset when the values of offset is very large?

the value will become very large, even 10^3 when i use deformable convolution in other network, i want to know what the meaning it is when getting so large?

I think this value may not be meaningful. I suspect the network diverged in your training.

I used in mnist, and it diverged. so i don't understand the meaning?


Lambda function in c++

Added the example code of lambda function in c++ .
Description of Change

Checklist

[ ] Added description of change
[ ] Added file name matches File name guidelines
[ ] Added tests and example, test must pass
[ ] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[ ] Relevant documentation/comments is changed or added
[ ] PR title follows semantic commit guidelines
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.

Notes:

@Panquesito7 is this even valid?

Don't think this is a valid algorithm, unfortunately.


Import Workflow Files from @moderntribe/actions

We are using actions from the @moderntribe/actions repo in a number of places in StellarWP — the square1/composer action, for example.
I thought it was worthwhile to import these files into this StellarWP repo for more straightforward governance [i.e. "keeping it in one org"], and just in case there would be some scenario where we lost access to the repo.
https://app.asana.com/0/1206581172125548/1206616396718524/f

We can ditch the square1 and dokku workflows, otherwise this looks good!

@borkweb fixed! ready for a review


ARROW-12033: [Minor][Docs] Fix link in developers/benchmarks.html

Before:

After:

Thanks @dianaclarke !

Thanks @cyb70289! Much appreciated.


prevent infinite recursion and stack overflow

The writeRuleAs(String ruleName, Object ruleSource) method was
invoking itself, which would recurse infinitely, until a stack overflow
is thrown.
It appears that it should be invoking writeRule() instead.

Thanks!  This commit looks right.  But I won't be able to integrate it until I get time to add a unit test.  If you have time to add a unit test for it, I could integrate right away.

I had started writing a unit test, but using a Mockito mock service was more involved than I had expected. I probably just need my own RESTService impl that supports putValue() and exists(). I'll take a look.

Let me caveat: when I say "unit test" in this project, I technically mean integration test.  We like to run our tests against the server to ensure that things are working as expected end-to-end.  And it helps us catch things when changes in the server break our tests.  I think the only place we mock anything in our "unit tests" is something you contributed.  Would you be comfortable adding a test to AlertingTest.java?  Or even better, just take one of the existing tests in there that calls writeRule and change it to use writeRuleAs.

I'd be happy to add a test to AlertingTest, but those integration tests are currently failing when I run them.
There seems to be a permissions issue. Any idea what roles the user that the tests use are supposed to have? Maybe the test bootstrap is missing something?
I'm running MarkLogic 9.0-20170113 and have a clean checkout of the develop branch.
I have uninstalled the test database and appserver using bootstrapper.teardown() and then followed the instructions to run:

mvn test-compile
mvn exec:java@test-server-init
mvn test

However, results are:

Tests run: 609, Failures: 0, Errors: 540, Skipped: 0

I see various failures in the run:

com.marklogic.client.test.SuggestTest  Time elapsed: 0.012 sec  <<< ERROR!
com.marklogic.client.ForbiddenUserException: Local message: User is not allowed to delete documents. Server Message: You do not have permission to this method and URL.
at com.marklogic.client.impl.JerseyServices.deleteDocument(JerseyServices.java:603)

testSemUuid0Exec(com.marklogic.client.test.PlanGeneratedTest): Local message: User is not allowed to apply resource at rows. Server Message: You do not have permission to this method and URL.

testAggregates(com.marklogic.client.test.TuplesHandleTest)  Time elapsed: 0.007 sec  <<< ERROR!
com.marklogic.client.ForbiddenUserException: Local message: User is not allowed to write /config/query. Server Message: You do not have permission to this method and URL.
at com.marklogic.client.impl.JerseyServices.putPostValueImpl(JerseyServices.java:2817)

testFnHead1Exec(com.marklogic.client.test.PlanGeneratedTest)  Time elapsed: 0.011 sec  <<< ERROR!
com.marklogic.client.ForbiddenUserException: Local message: User is not allowed to apply resource at rows. Server Message: You do not have permission to this method and URL.
at com.marklogic.client.impl.JerseyServices.checkStatus(JerseyServices.java:4305)

I removed the users and re-ran the bootstrap.xqy methods to create users and roles. I encountered errors for two roles do not exist, temporal-document-protect and temporal-document-wipe. I'm assuming they are bleeding edge only available in the latest MarkLogic builds?
After commented out these lines in the bootstrap.xqy:

local:security-eval(
'sec:privilege-add-roles("http://marklogic.com/xdmp/privileges/temporal-document-protect", "execute", "rest-admin")'),
local:security-eval(
'sec:privilege-add-roles("http://marklogic.com/xdmp/privileges/temporal-document-wipe", "execute", "rest-admin")'),

However, I still saw permissions errors, such as this:

testTransactions(com.marklogic.client.test.SPARQLManagerTest): Local message: User is not allowed to apply resource at /graphs/sparql. Server Message: You do not have permission to this method and URL.

amd now I'm seeing REST-INVALIDPARAM errors for the return type object

testFnTrueExpr0Exec(com.marklogic.client.test.PlanGeneratedTest): Local message: failed to apply resource at rows: Bad Request. Server Message: REST-INVALIDPARAM: fn.error(null, 'REST-INVALIDPARAM', 'unknown output type: '+outputType); -- Invalid parameter: unknown output type: object

But, the AlertTest tests execute, so I can add and verify.

One thing that I noticed, wasn't sure if this is another bug or intended behavior...
If writeRuleAs(ruleName, ruleSource) invokes [writeRule(ruleName, writeHandle)](https://github.com/marklogic/java-client-api/blob/develop/src/main/java/com/marklogic/client/impl/RuleManagerImpl.java#L141) and the writeHandle is a RuleDefinition with a name, then it will be saved with the RuleDefinition name, not the name provided when writeRuleAs was invoked.
I would think that the purpose of writeRuleAs() is to ensure that it is saved with the name provided and that we would want to clear the RuleDefinition.name prior to invoking writeRule(). I'm updating writeRuleAs() with the following, to ensure that it is saved with the name specified:
if (sourceHandle instanceof RuleDefinition) {
  ((RuleDefinition) sourceHandle).setName(ruleName);
}


Made order place button using Javascript

Made a button with an animation for an order placed, with help of JavaScript. Contributing under gssoc'23 please check it out.

@Siddharth961  change your file name script.js to app.js

@Siddharth961 change your file name script.js to app.js

@Spyware007 Thanks, changed it to app.js.  Also i made this change to my previous button. Please check it out now.


Refine IP addressing choices

We should refine the IP address choices made available when creating a server.

Consider not offering the option to create the Utility IP/interface.
Consider removing the addressing option altogether, and always going with either public IPv4 only, or public IPv4+IPv6.

As discussed internally, public IPv4 only for now

Open the lib/ConfigOptions.php file and remove the code between lines #40 to #45, which is as follows:
private function getNetworking()
{
    $nw['ipv4only'] = 'Public IPv4 Only';
     $nw['default'] = 'Public Default (IPv4, IPv6 & Utility)';
     return $nw;
 }

Also, remove line #81, which contains the following code within lib/ConfigOptions.php file:
$this->createIPFields($groupId, $this->getNetworking());
Open the lib/vmManager.php file and find the line #69 and replace from
$networking = $this->params['configoptions']['ipaddress'];
to
$networking = "ipv4only";

Fixed by #60


STx withdrawal from m blockchain wallet went to a random wallet

Describe the bug
STx withdrawal from blockchain wallet went to a random wallet
Transaction ID 0x06d5be1af744bc2a533458c93e42f728708454f5cdf89959222e7e6c60c45f91
Address SP2JC5XYNHZ7ZZQR174XE9C4NGXMTR81C2MSYFGRC
Block#  129,247
Time stamp 9:24:48 PM 11/20/2023
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots or consol.log to help explain your problem.
Desktop (please complete the following information):

OS:
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: iPhone
OS: [e.g. iOS8.1]
Browser via blockchain app
Version

Additional context
Add any other context about the problem here: tried to transfer STx from the airdrop to my wallet on an exchange instead it went to a random wallet with over $100k worth of stx.

This isn't an Explorer issue.
Please ask for community support on the #support channel in Discord.


printWidth doesn't work in Sublime Text 3

In my JsPrettier.sublime-settings I have:
  "prettier_options": {
    "printWidth": 120
  },

If I try to save the following line:
const longLine = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20]

This is what I get:
const longLine = [
  1,
  2,
  3,
  4,
  5,
  6,
  7,
  8,
  9,
  10,
  11,
  12,
  13,
  15,
  16,
  17,
  18,
  19,
  20
]

I don't think it's a SublimeJSPrettier problem, because when I replace prettier_cli_path with "[/path/to/]prettier-standard/node_modules/prettierx/bin/prettierx.js", the printWidth option is respected.

prettier-standard CLI doesn't support flags list printWidth, to configure formatting, please edit .prettierrc file in project directory


text in between <> will be displayed as nothing

Steps to reproduce
go to webview because i was flabbergasted why sometimes theres a word or two missing. turns out all the missing words are wrapped in <>.
Expected behavior
if the original written as . it should not be omitted.
<>. i think the parser recognize this as html tags so thats why it is being omitted?
Actual behavior
from certain .
displayed as:
from certain .
LNReader version
1.1.19
Android version
Android 11
Device
Tab S6
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.19.
[X] I will fill out all of the requested information in this form.

frustrated because it also happens in github i will now revert this what im saying with this >< instead of this <>.

Nebula< is written. but it was omitted due to <>.

i think you guys get the point right?

Could you provide an example of a novel and chapter along with the source where this issue can be reproduced?

Hello! I believe the OP is reading the same novel as me. Try "Omniscient Reader's Viewpoint", Chapter 388, the fourth paragraph:
[Nebula, , has opened a portal that wil summon you].
Over here it showsup correctly:
https://www.lightnovelworld.com/novel/omniscient-readers-viewpoint-265/chapter-388

Perhaps we can sanitize the <> here:
https://github.com/LNReader/lnreader/blob/484c2b7e33fc4832b2d987c7f8a3dce74ef7b642/src/screens/reader/ReaderScreen.tsx#L298
Or there some special mark up to prevent it from reading it as html here:
https://github.com/LNReader/lnreader/blob/484c2b7e33fc4832b2d987c7f8a3dce74ef7b642/src/screens/reader/ReaderScreen.tsx#L346
Honestly, I don't have experience with app development at all so I'm very hesitant to touch the code myself. However, this will definitely improve the reading experience of this app as key character names are within those <>. I had thought it was an error in the translation for the past 50 or more chapters and now I feel like an idiot :c

Yes I also have this issue

chapter = document.querySelector('chapter');
chapter.innerHTML = chapter.innerHTML
.replace(/<(\w+\b[\s\w’\']+)>/g, '<$1>');

Not a perfect solution but a lot of them should show with this..

Say the novel name and chapter


Add editing .gitignore to the interface

Inspired by Sublime Text's GitSavvy. Certain patterns and filenames can be explicitly added to .gitignore from within the UI.

Thanks. I'll refer it.


chore: Migrate warm up cache endpoint to api v1

SUMMARY

This PR deprecates the superset/warm_up_cache endpoint and creates the api/v1/cachekey/warm_up_cache endpoint to replace it.
The new endpoint has the following key differences:

Follows command pattern
uses PUT instead of GET
accepts a json body validated by marshmallow instead of query params
added openapi spec

Also improves test coverage
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@villebro, @michael-s-molina , @john-bodley can you take a look please. I'm not confortable with the logic behind warm_up_cache and not sure if cachekey is the right place for this. An alternative could be to place it on api/v1/chart and/or api/v1/dataset

An alternative could be to place it on api/v1/chart and/or api/v1/dataset

I would model these endpoints under the resources they refer to. I feels really weird for me treating cache warm up as a first-level resource.

Moved to api/v1/chart


QnAbot vs Serverless Bot Framework

What is the difference between this and serverless bot framework? If one was to start building on either, what would is the more strategic, supported path by AWS?
Serverless bot framework has a more "official" set of documentation and discoverability on AWS site, however QnAbot seems to be more active.
https://github.com/awslabs/serverless-bot-framework/
https://aws.amazon.com/solutions/implementations/serverless-bot-framework/?did=sl_card&trk=sl_card

@traverse-elastictier Hi - great question! The answer is... it depends!
The serverless bot framework solution is a good starting point if you are building your own transactional bot, say to provide self service workflows with different intents and multi-turn conversations to elicit slot values.. like ordering a product, booking an appointment, etc.
Whereas the QnABot - this project - is ideal if your bot needs are focused mostly on Q&A use cases.. you can get get up and running fast without coding, but it also has extensibility and plenty of feature to not lock you in.  If you're not sure, watch this new video demo that covers many of the QnAbot features: https://www.youtube.com/watch?v=4Wxu775i5yM
Without programming, the QnABot open source solution allows customers to quickly deploy self-service conversational AI on multiple channels including their contact centers and their web sites, also social media channels, SMS text messaging, or even Alexa skills. QnABot uses multiple AWS services including Amazon Lex, Amazon Kendra, Amazon Translate and more. Customers can configure curated answers to frequently asked questions using an integrated content management system supporting rich text and rich voice responses optimized for each channel, or they can expand the service’s answer knowledge base to include unstructured documents and PDFs, and existing web page content. The solution supports multiple languages with optional automatic translation of answers to the user’s local language. This video demonstrates many of these features and includes a bonus prototype demo of live agent transfer from the chat bot web UI
We'll also be adding something like this soon to the serverless bot framework documentation to help answer your question as well.

Question and Answer Bots
Serverless Bot Framework allows for a quick implementation of an end to end chatbot solution with different functionalities listed above. If you want to implement a chatbot that is specialized in question and answer (Q&A) or frequently asked questions (FAQ), then refer to this blog post: Create a Question and Answer Bot with Amazon Lex and Amazon Alexa

@rstrahan thank you for the response! Nice job on the video demo, that is how I discovered QnABot. What are the commercial use rights for QnABot? If its used as the basis of a commercial product, are there any legalese or use rights to be aware of?

@rstrahan  -> Also, is there guidance for updating and patching serverless bot framework when operating in a production setting?

Hi @traverse-elastictier
Re first question on commercial use rights for QnABot, see the licence file - https://github.com/aws-samples/aws-ai-qna-bot/blob/master/LICENSE.md
Re second question on serverless bot framework - please follow up on that via that project's site.
Cheers
Bob