Getting a weird number for timestamp in onTouchStart, onTouchMove, onTouchEnd events of View

Description
Consider the following code:
const log = (e) => console.log(e.nativeEvent.timestmap, Date.now())
return (
    <View
        onTouchStart={onTouchStart}
        onTouchMove={onTouchMove}
        onTouchEnd={onTouchEnd}>
        {props.children}
    </View>
)

Results:

On iOS simulator (iOS 14) the event logged 192388424.34784204 while at the same point in time  Date.now() logged<PHONE_NUMBER>368.
On an actual iPhone (iOS 14) the event logged 66961920.69195832 while at the same point in time Date.now() logged<PHONE_NUMBER>203
On an actual Android device (Android 10, Xiaomi Mi A2) the event logged 262563274 while at the same point in time Date.now() logged<PHONE_NUMBER>331

Questions

What does the event's timestamp represent? It's clearly not an epoch timestamp. Right?
Is it ticks? Doesn't seem to be ticks because none of the methods I found online to convert ticks to epoch dates worked.
How can I get the event's timestamp 192388424.34784204 and know when in time this event happened?

React Native version:
System:
    OS: macOS 10.15.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 297.70 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
    Yarn: 1.22.4 - ~/.nvm/versions/node/v12.18.1/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.0.1 4.0.1
    Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

PS: This also happens to a 0.62 react-native project.
Steps To Reproduce

Add a View component somewhere in any codebase
Use any the onTouchStart, onTouchMove, onToucheEnd props on that component
Log the event.nativeEvent.timestamp and a Date.now() in the callback.
Observe the difference in the numbers. Date.now() is clearly an epoch date - the other one isn't

Expected Results
The event.nativeEvent.timestamp should be an epoch date or something that can be turned into an epoch date.
Snack, code example, screenshot, or link to a repository:
const log = (e) => console.log(e.nativeEvent.timestmap, Date.now())
return (
    <View
        onTouchStart={onTouchStart}
        onTouchMove={onTouchMove}
        onTouchEnd={onTouchEnd}>
        {props.children}
    </View>
)

Nope it hasn't been fixed

I don't have an answer, but as far as I know here lies the Android code:
https://github.com/facebook/react-native/blob/4804e682388e40b82fb4a39fea256b3002a0aba6/ReactAndroid/src/main/java/com/facebook/react/uimanager/events/TouchesHelper.java#L67
https://github.com/facebook/react-native/blob/4804e682388e40b82fb4a39fea256b3002a0aba6/ReactAndroid/src/main/java/com/facebook/react/uimanager/events/Event.java#L110

So what are these timestamps on iOS? What are they on Android now? I'm super confused...

I want to know how to compare two different events timestamps to determine how much time has passed. How should I do this? On web, it's simple and uses the traditional epoch ms number. iOS shows some strange decimal format: 2829761.919135...


User tutorial for installing OpenEBS on CoreOS + Kubernetes

The default Core-OS image doesn't enable iscsi which is required for OpenEBS volumes.
The tutorial should include the pre-requisites/steps to configure iscsi-initiator through kubelet-wrapper. details mentioned by @maikotz in #160

After finishing my evaluation, I'm happy to help.

https://coreos.com/os/docs/latest/iscsi.html#automatic-iscsi-configuration


ml-pipeline-ui not bundled with kubeflow?

So I successfully enabled kubeflow with microk8s and apparently the ml-pipeline-ui either doesn't come installed by default with the kubeflow add-on or it somehow failed to start because when I run kubectl get service --all-namespaces | grep ml-pipeline all I see is the ml-pipeline service, no ml-pipeline-ui. I'm trying to connect the kfp Python SDK client to the pipeline service, but the Python SDK wants the ml-pipeline-ui service.
So should I try to get this service running and configured myself? Any help would be greatly appreciated.
inspection-report-20211014_231459.tar.gz

New steps are leading to a different error when trying to connect to the ml-pipeline client with kfp python module.
New steps
sudo snap install microk8s --classic --channel=1.21/stable
microk8s enable dashboard dns storage gpu metallb:<IP_ADDRESS>-<IP_ADDRESS>
# Seems to like having this step done before enabling kubeflow
microk8s config > ~/.kube/config
microk8s enable kubeflow
# I want to be able to use jupyter with kubeflow (though GPU isn't currently detected)
microk8s.juju refresh jupyter-ui --revision 10

New Error
Installing and testing kfp is the same.
python3 -m pip install kfp
python3 -c "import kfp;client = kfp.Client()"

But the error is new and different.
ERROR:root:Failed to get healthz info attempt 1 of 5.
Traceback (most recent call last):
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp/_client.py", line 410, in get_kfp_healthz
    response = self._healthz_api.get_healthz()
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api/healthz_service_api.py", line 63, in get_healthz
    return self.get_healthz_with_http_info(**kwargs)  # noqa: E501
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api/healthz_service_api.py", line 134, in get_healthz_with_http_info
    return self.api_client.call_api(
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 364, in call_api
    return self.__call_api(resource_path, method,
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 188, in __call_api
    raise e
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 181, in __call_api
    response_data = self.request(
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 389, in request
    return self.rest_client.GET(url,
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 230, in GET
    return self.request("GET", url,
  File "/home/thomas/.local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 224, in request
    raise ApiException(http_resp=r)
kfp_server_api.exceptions.ApiException: (503)
Reason: Service Unavailable
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Mon, 18 Oct 2021 23:47:41 GMT', 'Content-Length': '173'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"no endpoints available for service \"ml-pipeline\"","reason":"ServiceUnavailable","code":503}

It repeats this message four more times before failing.
New inspection report to go along with the new install steps and the new error. Any help is much appreciated. Thank you!
inspection-report-20211018_195547.tar.gz

Update
Reading through this documentation on connecting a kfp client to the kfp-api, I tried to set up port forwarding as they prescribe, but to the pod running the kfp-api.
By going through the code that runs with microk8s enable kubeflow I was able to figure out that ml-pipeline is a service that exposes the ports 8887 and 8888 for grpc and http connections for the kfp-api deployment.
# Find the pod name that corresponds to the kfp-api
pod=$(kubectl get pods -n kubeflow -o wide | grep "kfp-api-[^o]" | cut -f1 -d ' ' -)
# Verify that port 8888 is open.
port=$(kubectl get pod $pod -n kubeflow --template='{{(index (index .spec.containers 0).ports 0).containerPort}}{{"\n"}}')
# Use that pod name to set up port forwarding.
kubectl port-forward $pod 3000:$port -n kubeflow

opening up a new terminal and starting entering the following into the IPython REPL
import kfp
client = kfp.Client(host='http://localhost:3000')

yields no errors. Not sure if this should be touched upon in the microk8s kubeflow addon documentation in a similar fashion to the way it would be nice to know microk8s.juju refresh jupyter-ui --revision 10 is needed to enable the jupyter server in kubeflow would be great. Haven't tested it past connecting to the client, but that was my acceptance criteria for getting this issue resolved so I'm closing.


How confidence score is calculated in DetectNet?

The 5th parameter is a confidence value for every bounding-box. How is it calculated? Where can I find it in the code?
For example in COCO data set this value is in [0,1] interval, but in DetectNet output it can be more than 1.

I don't find the root of this bug. @lukeyeager can you help me please?


kubernetes default "admin" user isn't authorized to do anything useful

Issue description
In NixOS 18.03, with a default installation of an "all-in-one"
kubernetes cluster, the configured and default "admin" user isn't able
to do anything useful when kubectl is used by connecting it to the
https port. This is probably caused by the configuration of
kube-apiserver to use RBAC but without associating the admin user to
none of the administrative groups.
Steps to reproduce
In a fresh installation of NixOS 18.03 add the following to
configuration.nix:
  services.kubernetes.roles = [ "master" "node"];

Then switch the configuration with:
# nixos-rebuild switch

When the new configuration is installed, open a terminal and type:
# kubectl -s https://localhost --insecure-skip-tls-verify get nodes
Please enter Username: admin
Please enter Password: **********
Error from server (Forbidden): nodes is forbidden: User "admin" cannot list nodes at the cluster scope

#

Use the default configured password for user admin:
"kubernetes". Compare that result with the use of the unsecured http
port 8080:
# kubectl get nodes
NAME          STATUS    ROLES     AGE       VERSION
giskard.lan   Ready     <none>    1m        v1.9.1

#

The solution to this issue is to associate the admin with the
"system:masters" group defined by the kube-apiserver:
# kubectl describe clusterrolebinding cluster-admin
Name:         cluster-admin
Labels:       kubernetes.io/bootstrapping=rbac-defaults
Annotations:  rbac.authorization.kubernetes.io/autoupdate=true
Role:
  Kind:  ClusterRole
  Name:  cluster-admin
Subjects:
  Kind   Name            Namespace
  ----   ----            ---------
  Group  system:masters

#

That is achieved by adding that group name to the user file created by
the configuration:
# echo 'kubernetes,admin,0,"system:masters"' > /tmp/users

Then add this line to configuration.nix:
  services.kubernetes.apiserver.basicAuthFile = /tmp/users;

Then install the configuration and re-run the first kubectl line:
# nixos-rebuild switch
building Nix...
building the system configuration...
...
starting the following units: kube-apiserver.service

# kubectl -s https://localhost --insecure-skip-tls-verify get nodes
Please enter Username: admin
Please enter Password: **********
NAME          STATUS    ROLES     AGE       VERSION
giskard.lan   Ready     <none>    25m       v1.9.1

#

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.15.18, NixOS, 18.03.132336.ef74cafd3e5 (Impala)
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.0.1
channels(root): "nixos-18.03.132336.ef74cafd3e5"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

cc @offlinehacker

Maybe this is related, but last time I tried setting up K8s,   the kube-dns service wouldn't come up as it couldn't connect to the apiserver. I feel it was maybe some permission problem as well

Eh, you should open another issue and to try to clarify it a bit.

This is now superseded by the current state of Kubernetes


Allow to manually set a street name in the AddressForm widget

Currently, AddressForm uses RadioField to show nearest streets in the radius of 100m. However, sometimes this list of streets is not complete so I think it would be helpful to allow setting a street name manually.

Yes this would be very good.  I found that the proper street name wasn't available in this case so I had to enter it incorrectly and then come back later to fix with a different editor.  In the screenshot below I was trying to add a POI with addr:street=Pearl Street, but that wasn't an option.  If there was a custom field I would have just typed it in.

The reason I'm hesitant to add a free-form editor for a street name, is that it might lead to broken addr:street values: some that resemble road names, some just plain wrong. It is actually a very rare case (I think) that an amenity is addressed with a road name that's not there.
So this option would require I guess real-time looking for a similar names around and suggesting these.

Done in 0.7.


Add logrus plugin

This PR adds a logging plugin for using logrus.

Ive updated the code to use GetLevel as suggested, it makes sense to use that. Thank you!
I also spotted an error where I had not initialized the empty field map so I have added a fix for that as well.


DOCK-2519: Support phrases in search

Description
This PR changes our main search box so that the user can search for a phrase by enclosing the phrase in double quotes.  For example, the search phrase "santa cruz" california searches for entries that either contain the phrase "santa cruz" or the word "california".
The proposed code is a bit of a compromise, due to the very complicated and circular nature of the existing search code.  Ideally, the query builder would propagate the parsed terms (which it used to create the search query) to the other parts of the system that needed them.  However, the tweaks required to do so would have potentially tickled many possible/previous bugs (think "the return of the Self-DOS"), so it wasn't worth the risk.
Instead, we call the parsing code twice: once to build the query, and another time to display the terms in the UI.  Initially, I tried to embed the responsible function in the most logical spots in the existing services, but ran afoul of circular dependency injection (DI) problems.  Next, I tried to create a new service for the function, but this necessitated dozens and dozens and dozens of lines to code to inject the necessary setup (especially for testing).  It was gross, took hours, and I only got halfway before deciding to try something different.
Instead, I put the function in a helper file.  I am well aware that [to some] this is not the "Angular way", but relative to the previous alternative, it is vastly more compact, clean, and understandable.  I implore us to please accept it, given the inherent difficulty of the search code, as a remedy in this particular situation.  (For tons of fun, see this link for more discussion about Angular and helper functions: https://www.reddit.com/r/angular/comments/a3o6jy/you_cant_have_helper_classes_in_angular/)
This change exposes a quirk in the way that Elasticsearch "summarizes", via ellipsis, the "matching" fields that it displays in the results.  After searching for the phrase "x y", in the summarized description/topic/category hit results, you'll see the text x...y more than you would expect.  If anyone has ideas about how to fix this, please comment.
Review Instructions
On qa, search for a phrase that matches some entries, per the description above, and confirm that the results look correct.
Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-2519
dockstore/dockstore#5839
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

This change exposes a quirk in the way that Elasticsearch "summarizes", via ellipsis, the "matching" fields that it displays in the results. After searching for the phrase "x y", in the summarized description/topic/category hit results, you'll see the text x...y more than you would expect. If anyone has ideas about how to fix this, please comment.

The Elasticsearch highlighting options are defined here https://github.com/dockstore/dockstore-ui2/blob/e6b57842f3f0eef101885712acc59d3cd9259b92/src/app/search/query-builder.service.ts#L132
We actually do the "ellipsing" in the UI to join the highlight fragments that Elasticsearch returns. Example https://github.com/dockstore/dockstore-ui2/blob/e6b57842f3f0eef101885712acc59d3cd9259b92/src/app/search/search-workflow-table/search-workflow-table.component.html#L83
Off the top of my head, I don't know how to fix it so that the fragments contain the whole match_phrase, but poking around the Elasticsearch docs, we could experiment with specifying a highlight query https://www.elastic.co/guide/en/elasticsearch/reference/current/highlighting.html#specify-highlight-query

Looks good, is it "integration-test-able?" So we can show the new queries in practice?

Right now, we don't test the content of the actual search results (the hits produced by Elasticsearch) at all (unless I missed it) because it's difficult to do for a number of reasons.  Would be great to make it better, but to solve the problem, we probably need to overhaul the test database so it contains a large enough number of entries with the right keyword/facet mix to test the various search features.  Probably should be done in one or more) [big] future ticket(s).

Off the top of my head, I don't know how to fix it so that the fragments contain the whole match_phrase, but poking around the Elasticsearch docs, we could experiment with specifying a highlight query https://www.elastic.co/guide/en/elasticsearch/reference/current/highlighting.html#specify-highlight-query

Did some more testing and it appears that the x...y thing happens less than it first seemed.  On occasion, it's slightly annoying (why are there ellipsis there, there's no word between?), but not sure it's easily remedied.  If the fragments contained some positional info, we could make a judgement call as to whether to insert the ellipsis or not.  But they don't.  So, probably ok to merge this in its current more-useful-than-before-but-slightly imperfect state.

Off the top of my head, I don't know how to fix it so that the fragments contain the whole match_phrase, but poking around the Elasticsearch docs, we could experiment with specifying a highlight query https://www.elastic.co/guide/en/elasticsearch/reference/current/highlighting.html#specify-highlight-query

Did some more testing and it appears that the x...y thing happens less than it first seemed. On occasion, it's slightly annoying (why are there ellipsis there, there's no word between?), but not sure it's easily remedied. If the fragments contained some positional info, we could make a judgement call as to whether to insert the ellipsis or not. But they don't. So, probably ok to merge this in its current more-useful-than-before-but-slightly imperfect state.

Possibly, the issue is fixed in newer versions of Elasticsearch:
https://github.com/elastic/elasticsearch/pull/96068
https://github.com/elastic/elasticsearch/issues/29561


dashboards have no page display

The endpoint (/api/graph/data) cannot obtain data after deployment
k8spacket version: 1.1.1
granfana version: 9.5.3
k8s version :1.21
Endpoint data return：

k8spacket log:

grafana dashboard:

Hi @xzclinux
Sounds similar to this issue: https://github.com/k8spacket/k8spacket/issues/25#issuecomment-1386837140
Could you share logs of the init-k8spacket container:
k -n k8spacket logs <k8spacket-pod-name> -f -c init-k8spacket

Do we have a communication group? I have other needs to communicate with you

@xzclinux
As I see, you were too fast for that container. That's why there weren't any logs, I suppose.
Could you show logs for running pod but for container init-k8spacket? From your screenshot, it will be:
k -n k8spacket logs k8spacket-z52vz -f -c init-k8spacket

No, we don't have any communication group. But, if you have any needs not related to an issue, feel free to write an email<EMAIL_ADDRESS>

I checked the yaml file for the new version and the log was written to /dev/termination-log to see if this is something you need to see

and
kernel version: EulerOS 2.0
system version:  4.18.0-147

Hi @xzclinux
You are using the Huawei cloud. Please see another issue related to EulerOS: https://github.com/k8spacket/k8spacket-helm-chart/issues/6#issuecomment-1217968681
The problem is probably connected to the wrong command to achieve network interfaces.
Go through the related issue and change the command in helm values: https://github.com/k8spacket/k8spacket-helm-chart/blob/master/charts/k8spacket/values.yaml#L71
Additionally, you can share here the response from the command:
kubectl run -i --restart=Never --rm k8s-packet-debug --image=k8spacket/k8spacket:1.1.1 --overrides='{"kind":"Pod", "apiVersion":"v1", "spec": {"hostNetwork": true}}' -- ip address

Then I'll adjust the command to your needs.

It can work normally now. Could you please add comments on the chart? Thank you very much.

I have the same problem...
daemonset logs:
kubectl logs -n k8spacket k8spacket-9vftq
2023/08/05 05:43:07 Refreshing interfaces for capturing...
exit status 1
2023/08/05 05:43:17 Refreshing interfaces for capturing...
exit status 1
2023/08/05 05:43:27 Refreshing interfaces for capturing...
exit status 1
2023/08/05 05:43:37 Refreshing interfaces for capturing...
exit status 1
ip address:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:96:b0:8c brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/22 brd <IP_ADDRESS> scope global dynamic noprefixroute ens160
valid_lft 58512sec preferred_lft 58512sec
inet <IP_ADDRESS>/32 scope global ens160
valid_lft forever preferred_lft forever
inet6 fe80::4ccd:6dd3:e5d7:35b5/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip <IP_ADDRESS> brd <IP_ADDRESS>
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:f9:28:d0:e8 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:f9ff:fe28:d0e8/64 scope link
valid_lft forever preferred_lft forever
7: vxlan.calico: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
link/ether 66:a7:26:f7:25:dd brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/32 scope global vxlan.calico
valid_lft forever preferred_lft forever
inet6 fe80::64a7:26ff:fef7:25dd/64 scope link
valid_lft forever preferred_lft forever
8: cali26afe4700b2@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever
9: cali7fbbc57996d@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever
10: cali0d3ecae97c2@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet6 fe80::ecee:eeff:feee:eeee/64 scope link
valid_lft forever preferred_lft forever
@k8spacket

Hi @andyzheung
Hmm, I don't understand the part of your logs: exit status 1 🤔
Anyway:
What kind of OS are you using under K8S cluster?
Could you check if the plugins were downloaded properly by the below command?
k -n k8spacket get pods k8spacket-9vftq -oyaml | yq .status.initContainerStatuses

If you don't have yq tool, then share .status.initContainerStatuses[0].state.terminated.message part of the response here.
It should look similar to:
        Connecting to github.com (***:443)
        wget: note: TLS certificate validation not implemented
        Connecting to objects.githubusercontent.com (***:443)
        saving to 'nodegraph-x86_64.so'
        nodegraph-x86_64.so   20% |******                          | 13.2M  0:00:03 ETA
        nodegraph-x86_64.so   74% |***********************         | 47.0M  0:00:00 ETA
        nodegraph-x86_64.so  100% |********************************| 63.3M  0:00:00 ETA
        'nodegraph-x86_64.so' saved
        Connecting to github.com (***:443)
        Connecting to objects.githubusercontent.com (***:443)
        saving to 'tls-parser-x86_64.so'
        tls-parser-x86_64.so   0% |                                |  176k  0:06:09 ETA
        tls-parser-x86_64.so  43% |*************                   | 27.4M  0:00:02 ETA
        tls-parser-x86_64.so  95% |******************************  | 61.0M  0:00:00 ETA
        tls-parser-x86_64.so 100% |********************************| 63.7M  0:00:00 ETA
        'tls-parser-x86_64.so' saved

Hi @andyzheung
Hmm, I don't understand the part of your logs: exit status 1 🤔
Anyway: What kind of OS are you using under K8S cluster? Could you check if the plugins were downloaded properly by the below command?
k -n k8spacket get pods k8spacket-9vftq -oyaml | yq .status.initContainerStatuses

If you don't have yq tool, then share .status.initContainerStatuses[0].state.terminated.message part of the response here.
It should look similar to:
        Connecting to github.com (***:443)
        wget: note: TLS certificate validation not implemented
        Connecting to objects.githubusercontent.com (***:443)
        saving to 'nodegraph-x86_64.so'
        nodegraph-x86_64.so   20% |******                          | 13.2M  0:00:03 ETA
        nodegraph-x86_64.so   74% |***********************         | 47.0M  0:00:00 ETA
        nodegraph-x86_64.so  100% |********************************| 63.3M  0:00:00 ETA
        'nodegraph-x86_64.so' saved
        Connecting to github.com (***:443)
        Connecting to objects.githubusercontent.com (***:443)
        saving to 'tls-parser-x86_64.so'
        tls-parser-x86_64.so   0% |                                |  176k  0:06:09 ETA
        tls-parser-x86_64.so  43% |*************                   | 27.4M  0:00:02 ETA
        tls-parser-x86_64.so  95% |******************************  | 61.0M  0:00:00 ETA
        tls-parser-x86_64.so 100% |********************************| 63.7M  0:00:00 ETA
        'tls-parser-x86_64.so' saved

I use ubuntu 18.04 LTS.
state:
terminated:
containerID: docker://da436081a8bc80be33ce5ef9688f3800d1fe9f21f92f4419934edd386538d02a
exitCode: 0
finishedAt: "2023-08-05T02:50:29Z"
message: |
Connecting to github.com (<IP_ADDRESS>:443)
wget: note: TLS certificate validation not implemented
Connecting to objects.githubusercontent.com (<IP_ADDRESS>:443)
saving to 'nodegraph-x86_64.so'
nodegraph-x86_64.so    0% |                                | 15545  1:12:06 ETA
nodegraph-x86_64.so    5% |*                               | 3340k  0:00:36 ETA
nodegraph-x86_64.so   16% |*****                           | 10.3M  0:00:15 ETA
nodegraph-x86_64.so   29% |*********                       | 18.8M  0:00:09 ETA
nodegraph-x86_64.so   39% |************                    | 24.9M  0:00:07 ETA
nodegraph-x86_64.so   48% |***************                 | 31.0M  0:00:06 ETA
nodegraph-x86_64.so   58% |******************              | 37.3M  0:00:04 ETA
nodegraph-x86_64.so   69% |**********************          | 43.8M  0:00:03 ETA
nodegraph-x86_64.so   79% |*************************       | 50.6M  0:00:02 ETA
nodegraph-x86_64.so   90% |****************************    | 57.3M  0:00:01 ETA
nodegraph-x86_64.so  100% || 63.3M  0:00:00 ETA
'nodegraph-x86_64.so' saved
Connecting to github.com (<IP_ADDRESS>:443)
Connecting to objects.githubusercontent.com (<IP_ADDRESS>:443)
saving to 'tls-parser-x86_64.so'
tls-parser-x86_64.so   0% |                                | 85696  0:13:00 ETA
tls-parser-x86_64.so   6% |*                               | 3997k  0:00:30 ETA
tls-parser-x86_64.so  21% |                          | 13.4M  0:00:11 ETA
tls-parser-x86_64.so  34% |                     | 22.1M  0:00:07 ETA
tls-parser-x86_64.so  45% |                  | 29.0M  0:00:05 ETA
tls-parser-x86_64.so  56% |*****************              | 35.9M  0:00:04 ETA
tls-parser-x86_64.so  68% |*********************           | 43.3M  0:00:03 ETA
tls-parser-x86_64.so  79% |*************************       | 50.9M  0:00:02 ETA
tls-parser-x86_64.so  92% |*****************************   | 58.8M  0:00:00 ETA
tls-parser-x86_64.so 100% |********************************| 63.7M  0:00:00 ETA
'tls-parser-x86_64.so' saved
reason: Completed
startedAt: "2023-08-05T02:50:05Z"

Hi @andyzheung
That's great. Plugins are installed properly.
Based on your answer https://github.com/k8spacket/k8spacket/issues/38#issuecomment-1666400407
I think the best command for you will be:
command: "ip address | grep @if | sed -E 's/.*<EMAIL_ADDRESS>| tr '\\n' ',' | sed 's/.$//'"

Change it in values.yaml and reinstall k8spacket

I reinstall the k8spacket..
the daemonset logs like this:
2023/08/10 12:57:58 [nodegraph plugin] Connection: src=<IP_ADDRESS> srcName=pod.vsphere-csi-node-gwtls srcPort=48744 srcNS=vmware-system-csi dst=<IP_ADDRESS> dstName=pod.guestbook-demo-helm-guestbook-7964ff57f6-szcnn dstPort=80 dstNS=argocd-demo closed=true bytesSent=104 bytesReceived=1871 duration=1.6129e-05
2023/08/10 12:58:00 [nodegraph plugin] Connection: src=<IP_ADDRESS> srcName=pod.vsphere-csi-node-gwtls srcPort=41658 srcNS=vmware-system-csi dst=<IP_ADDRESS> dstName=pod.tekton-triggers-core-interceptors-84874b55bb-8mbhq dstPort=8082 dstNS=tekton-pipelines closed=true bytesSent=111 bytesReceived=94 duration=6.192e-06
2023/08/10 12:58:04 [nodegraph plugin] Connection: src=<IP_ADDRESS> srcName=pod.vsphere-csi-node-gwtls srcPort=60044 srcNS=vmware-system-csi dst=<IP_ADDRESS> dstName=pod.argocd-notifications-controller-6f99749496-997hb dstPort=9001 dstNS=argocd closed=true bytesSent=0 bytesReceived=0 duration=2.845e-06
2023/08/10 12:58:04 [nodegraph plugin] Connection: src=<IP_ADDRESS> srcName=pod.vsphere-csi-node-gwtls srcPort=55574 srcNS=vmware-system-csi dst=<IP_ADDRESS> dstName=pod.argocd-repo-server-7cc94f47b7-khbfw dstPort=8084 dstNS=argocd closed=true bytesSent=113 bytesReceived=138 duration=5.252e-06
2023/08/10 12:58:04 [nodegraph plugin] Connection: src=<IP_ADDRESS> srcName=pod.vsphere-csi-node-gwtls srcPort=38622 srcNS=vmware-system-csi dst=<IP_ADDRESS> dstName=pod.argocd-application-controller-0 dstPort=8082 dstNS=argocd closed=true bytesSent=113 bytesReceived=138 duration=5.579e-06
but the node graph panel is still empty:

Hi @andyzheung
Could you check the answer of the endpoint where Grafana expects data?
kubectl run -it --rm --image=curlimages/curl curly -- http://k8spacket.k8spacket.svc.cluster.local:8080/nodegraph/api/graph/data

Additionally, could you check the Grafana datasource for Node Graph API? It should be filled by value
http://k8spacket.k8spacket.svc.cluster.local:8080/nodegraph

Hi @andyzheung
I will close this issue according to the inactive thread from more than 10 days.
Please feel free to reopen it if you have more questions.


add support for xDai sidechain

Added xDai network endpoint, token, and tested :)

Err, I totally missed the contribution guidelines - I see them now. If it's a big deal, feel free to reject this PR and I'll resubmit as in the guidelines.


⚠ Bofrost.com has degraded performance

In de2cd54, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 856 ms

Resolved: Bofrost.com performance has improved in 648cb16 after 6 minutes.


https://protomaps.com/docs/pricing-licensing/ is not fully covering an attribution - license itself should be mentioned/linked

https://protomaps.com/docs/pricing-licensing/

© OpenStreetMap should appear in the corner of your map.

It should be "© OpenStreetMap (ODbL)" or at least link https://www.openstreetmap.org/copyright to fulfil also requirement about stating license

You must include a notice associated with the Produced Work reasonably calculated to make any Person that uses, views, accesses, interacts with, or is otherwise exposed to the Produced Work aware that Content was obtained from the Database, Derivative Database, or the Database as part of a Collective Database, and that it is available under this License.

note "and that it is available under this License"

Updated https://protomaps.com/docs/pricing-licensing/ with example HTML snippet linking to ODbL


Do not consider namespaces when checking for DOM

When testing whether a component is a DOM element, we select the first portion of the name up until : or ., then tests for ^[a-z]|-.
There are many problems with this:

It doesn't test the name but the namespace, which I don't think is what was intended
In effect it only tests the first character; not the full tag
It allows for tags that start with -
In JSX it is not possible to be a DOM element and be in a namespace as well
: is not an allowed character

It may be a dangerous change, but ~the tests are still passing and~ locally it is "more correct".
UPDATE: So this triggers a "chain reaction" in jsx-pascal-case, which if followed solves  #1334.

: is not an allowed character

About that, I saw references to the colon is a couple of places.
My current understanding, which stems from this comment, is clashing with what I see in the code. 🤔

I performed more tests and found this bit of code that explains it: https://github.com/babel/babel/blob/c3a5bf1ff5bd0df437bc20752464d08674d011d3/packages/babel-types/src/validators/react/isCompatTag.js#L2
I'll revert to (almost) the same RegExp and will add a comment.

@ljharb This is ready for review.


Rollback trace end signature if needed

It turns out that for insert Done processing does not show up in the trace log.
To address that we changed it to preparing a result in  https://github.com/scylladb/gocql/pull/241
If it is confirmed to be an scylla issue, let's rollback https://github.com/scylladb/gocql/pull/241 when it is merged.

For inserts it looks like that: "Done preparing on a local shard - preparing a result."

In https://github.com/scylladb/scylladb/blob/5c0f6d461321c4daa66bf3ff83543b9788c5ce72/transport/server.cc#L1045 you can see that for cql_server::connection::process_prepare the last activity in tracing looks like Done preparing on a local shard - preparing a result. and for others (process_execute_internal, process_query_internal and process_batch_internal) it is Done processing - preparing a result. I missed this when writing a condition. So it is non issue

In https://github.com/scylladb/scylladb/blob/5c0f6d461321c4daa66bf3ff83543b9788c5ce72/transport/server.cc#L1045 you can see that for cql_server::connection::process_prepare the last activity in tracing looks like Done preparing on a local shard - preparing a result. and for others (process_execute_internal, process_query_internal and process_batch_internal) it is Done processing - preparing a result. I missed this when writing a condition. So it is non issue

Looking at scylladb/scylla-cqlsh:
here and here
I have figured that it is better to wait till select duration from system_traces.sessions is not nil.

In https://github.com/scylladb/scylladb/blob/5c0f6d461321c4daa66bf3ff83543b9788c5ce72/transport/server.cc#L1045 you can see that for cql_server::connection::process_prepare the last activity in tracing looks like Done preparing on a local shard - preparing a result. and for others (process_execute_internal, process_query_internal and process_batch_internal) it is Done processing - preparing a result. I missed this when writing a condition. So it is non issue

Looking at scylladb/scylla-cqlsh: here and here I have figured that it is better to wait till select duration from system_traces.sessions is not nil.

I am not sure about that, how should I scan the query to get nil, now with
var (
		coordinator string
		duration    int
	)

	iter := t.session.control.query(`SELECT coordinator, duration
		FROM system_traces.sessions
		WHERE session_id = ?`, traceId)

	iter.Scan(&coordinator, &duration)

when the trace is not ready coordinator will be empty string and duration will be 0. But I am not sure if checking that is enough, sometime tracing looks like that:
Tracing session 9dfcdef0650d11efbf3d2ee5378096b2 (coordinator: , duration: 0s):
2024/08/28 07:17:43.135712: Checking bounds [shard 0] (source: <IP_ADDRESS>, elapsed: 1)
2024/08/28 07:17:43.135713: Processing a statement [shard 0] (source: <IP_ADDRESS>, elapsed: 2)
2024/08/28 07:17:43.135743: Creating read executor for token -7012643373428192421 with all: [<IP_ADDRESS>] targets: [<IP_ADDRESS>] repair decision: NONE [shard 0] (source: <IP_ADDRESS>, elapsed: 32)
2024/08/28 07:17:43.135744: Creating never_speculating_read_executor - speculative retry is disabled or there are no extra replicas to speculate with [shard 0] (source: <IP_ADDRESS>, elapsed: 33)
2024/08/28 07:17:43.135747: read_data: querying locally [shard 0] (source: <IP_ADDRESS>, elapsed: 36)
2024/08/28 07:17:43.135752: Start querying singular range {{-7012643373428192421, pk{000400000032}}} [shard 0] (source: <IP_ADDRESS>, elapsed: 41)
2024/08/28 07:17:43.135755: [reader concurrency semaphore user] admitted immediately [shard 0] (source: <IP_ADDRESS>, elapsed: 44)
2024/08/28 07:17:43.13576: [reader concurrency semaphore user] executing read [shard 0] (source: <IP_ADDRESS>, elapsed: 49)
2024/08/28 07:17:43.135772: Querying cache for range {{-7012643373428192421, pk{000400000032}}} and slice [(-inf, +inf)] [shard 0] (source: <IP_ADDRESS>, elapsed: 61)
2024/08/28 07:17:43.135794: Page stats: 1 partition(s), 0 static row(s) (0 live, 0 dead), 1 clustering row(s) (1 live, 0 dead) and 0 range tombstone(s) [shard 0] (source: <IP_ADDRESS>, elapsed: 83)
2024/08/28 07:17:43.135801: Querying is done [shard 0] (source: <IP_ADDRESS>, elapsed: 90)
2024/08/28 07:17:43.135812: Done processing - preparing a result [shard 0] (source: <IP_ADDRESS>, elapsed: 102)

so it is lacking coordinator info and duration is zero, but "Done processing - preparing a result" is there

so it is lacking coordinator info and duration is zero, but "Done processing - preparing a result" is there

I got confused a bit, it should be nor nil, neither 0.

so it is lacking coordinator info and duration is zero, but "Done processing - preparing a result" is there

I got confused a bit, it should be nor nil, neither 0.

I am just guessing that duration info is filled after Done processing - preparing a result is written and we can have a situation when Done processing - preparing a result is written but duration is not filled yet

so it is lacking coordinator info and duration is zero, but "Done processing - preparing a result" is there

I got confused a bit, it should be nor nil, neither 0.

I am just guessing that duration info is filled after Done processing - preparing a result is written and we can have a situation when Done processing - preparing a result is written but duration is not filled yet

Looking at the core code I can tell that it is not the case, only problem that can potentially be is that duration in not set in some cases, say on exception.

regardless the reason should we just wait until duration is not zero and omit this weird case when it is zero but we have tracing activities available?

Yes, let's ommit it, untill we face an issue with it.


Question - Any thoughts to start supporting HBase output?

Hey @enric1985, I'm not too well versed in hbase, but would the existing https://www.benthos.dev/docs/components/outputs/hdfs have any overlap?


Add methods intersect_plane and get_point to Ray

I think it's worth discussing if bevy wants to start adding this kind of math. It's non-trivial, and will balloon in size/scope rapidly.
Maybe counter-intuitively, I think it might be better if bevy sticks to only providing common types, and let people build bindings to fully featured geometry libs. This particular PR is probably fine, we probably need some minimal helper functions even if we do decide to defer the math.

So, my vision in this space is:

Bevy should provide common foundations for more advanced geometry backends that make different performance tradeoffs (or perhaps expose different styles of API).
Critical gameplay-relevant functionality like "select a 2D object" or "convert my cursor position to a 2D world position" must be built into the engine and work correctly (if perhaps not quickly) out of the box.

I know the 3D case is significantly trickier, and I'm largely okay to defer that to 3rd party crates (for now). But the 2D case is a serious barrier for new users, game jams, and building out game templates and gameplay libraries (@bzm3r and I have been talking about adding related functionality to bevy_ecs_tilemap).
cc @cart @superdump @mockersf.

@aevyrie what are the general purpose/fully featured geometry libraries that people should build bindings to? My guesses:

euclid?

geo?

@aevyrie what are the general purpose/fully featured geometry libraries that people should build bindings to? My guesses:

euclid?

geo?

Whatever physics engine the user chooses. It's going to be way more performant, as it will already have acceleration structure built for the entire scene when doing things like ray casts and intersection checks.
Specifically, probably rapier, or bindings to an established C/C++ engine like physx, bullet, havoc, etc.
That's why I suggested we stick to defining interoperable types. These physics engines can get bevy wrappers that convert between the geometry types. This allows the bevy ecosystem to interop regardless of the engine chosen. It has similar problems to rusts async situation, but it's better than committing to a single engine. We could conceivably create traits for common intersection/physics tests, to allow even better compatibly. E.g. a plugin could call an intersection check function without caring about what physics backend is being used.

I think that if we identify a need for a math type or function in Bevy, we should add it (provided glam doesn't already have it and contributing it upstream isn't the right move). General purpose geometry libs are only as useful as the things they interop with, and to my knowledge nothing exists that makes those particularly compelling to adopt (let me know if you have any specific scenarios in mind).
Given the uncertainty around what official Bevy + Physics will look like, I'd rather just add things as needed for now. In the case of this PR, these functions seem useful. We can always do breaking changes later if we find something else in this space that fits our needs better.

bors r+


WYSIWYG: Tidy up styling/positioning of the Edit Controls

Description

Improve the colouring of the buttons in the Edit Controls and confirmation Dialog.
Move the "Actions" to the top of the screen, as they felt a little lost floating in the middle at the bottom.
Remove the "Pencil" icon from the page title, and instead have an "In Edit Mode" note under the actions bar

unrelated test fail - happy to merge.


Update hyper / iron / urlencoded dependencies

Previously, building the latest urlencoded (according to semver) would break.

After this is merged we need to create a new release.

Changes Unknown when pulling de6d5e304b8f7b7870fba0d085405eaa37ecdaf8 on dependencies into ** on master**.

:+1: But this is a "breaking" change on our side because we did update the dependencies to a new major version.

Yep :)


Broken reference to Contributing guideline

The Link to https://zio.dev/about/contributing in the Readme.MD in branch https://github.com/zio/zio-quill/tree/master is not working

duplicate

zio-sbt issue, not zio-quill one


TreeView parent indeterminate mode not working when...

Take a TreeView and specify the ItemContainerStyle using the style from Generic.xaml included in the Nuget package.  I changed nothing in the style and the indeterminate state in the parent nodes stop working.  They remain in the checked state.
FYI: the reason I want to edit a copy of the style is that I want the tree view to take the entire width so I want to use a Grid instead of a StackPanel in the TreeViewItem control template.
Example project attached.
Expected behavior
You should be able to modify the style and keep the indeterminate state functionality.
Version Info

NuGet package version:
Microsoft.UI.Xaml 2.1.181217001-prerelease

April 2018 Update (17134)
\
Desktop
Additional context
Demo project:
TreeViewIndeterminateBug.zip

I just checked generic.xaml file in the latest stable NuGet package (2.2.190917002) and I think it contains the right style now.
Also, #218 removed the internal StackPanel so hopefully you don't need to re-template any more.


ProvisionedPlan Attribute

Get-CsOnlineUser no longer returns the ID of the plans that are provisioned (ProvisionedPlan Attribute). It will only return the following sub-attributes in the ProvisionedPlan attribute of the user:

CapabilityStatus
ProvisioningStatus
Service

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

ID: 7008ec10-a056-d8bb-bb4e-b4690a84adfd
Version Independent ID: 2dcb78d9-7f36-208e-0989-184905d73011
Content: Get-CsOnlineUser (SkypeForBusiness)
Content Source: skype/skype-ps/skype/Get-CsOnlineUser.md
Service: skypeforbusiness-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

@dariomws

@dariomws Please comment

@marmstrong94 Thank you very much for your kind feedback. Considering your valuable feedback, please log this issue as advised. Here we are limited to documentation fixes and improvements only. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.


Add initial eventing machinery

What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds event recorder and emits warning events on errors.
Signed-off-by: hasheddan<EMAIL_ADDRESS>Which issue(s) this PR fixes:

Fixes #41
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Profile controller will emit warning events on failure to get profile path or save profile to disk

/retest


Rate limit ec2:DescribeSubnets

Signed-off-by: Vlad Ungureanu<EMAIL_ADDRESS>
Adds rate limiting to the ec2:DescribeSubnets calls.
Rate limit ec2:DescribeSubnets in the EC2 client

This change is

Coverage decreased (-0.01%) to 46.003% when pulling 5b1e17a9b67e793ecf1cf8594b4e91e51e3e43bc on vladu/rate-limit-describe-subnets into 1230f2b940b81aa143ef5567c087d217944166c5 on master.

test-me-please


RichCommand: Layout Sort Group

Resolved / Related Issues
Add commands Layout Sort Group.
When the option "Sync layout and sorting preferences across directories", the adaptive layout is disable in toolbar but not in context menu. It's fixed.
The layout context menu replaces icons by toggle indicator. This lets you know which layout is active.
Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Can you group related actions together instead of creating separate files for each one?

It's done.

The layout context menu replaces icons by toggle indicator. This lets you know which layout is active.

Doesn't MenuItem have support for icon as well?

Yes, but only a fonticon, not an opacityicon. The columns layout uses opacityicon. I tested with the tool icon + font icon, it's not aesthetic. I'll send a screenshot later.

Here is a screenshot. We can find a trick for the image of columns.

I'm going to be updating the other icons in the flyout as well, do you have any ideas on fixing the issue?

It will probably be necessary to create a UserControl derived from ToggleMenuFlyoutItem (as it was done for the buttons). In the preview, the Columns icon is already missing in this context menu. I propose to deal with this problem in a future pr. I will commit the code with the check + icon.

It's done.

@cinqmilleans can you fix the merge conflict?

It's done.


Extend service provider search

My attempt to implement a suggestion implied in https://github.com/nunomaduro/larastan/issues/273#issuecomment-503291317 , namely getting a list of directories to check for service providers, directly from Composer data.
@szepeviktor , I wasn't sure exactly how to test the load-from-extra-search-directories without polluting production use with test code (such as a dummy service provider).  In lieu of a way to do that cleanly, I added a test that verified my changes didn't break the status quo on Larastan itself.

Thank you for you contribute.
Could you use Composer's mechanisms instead of getcwd().... ?

@szepeviktor , I'll certainly try - I used getcwd() because the existing code did so.

$reflection = new \ReflectionClass(\Composer\Autoload\ClassLoader::class);
$vendorDir = dirname(dirname($reflection->getFileName()));

Thanks - let me try that.

@szepeviktor , thanks for your suggestion - it seems to have worked well.

getFileName() gives you vendor/composer/ClassLoader.php so one dirname() is enough

require_once may not serv us well as this file could be already loaded, please consider include

if it is possible please try to nuke Finder::create()->files()->name('*.php')

@szepeviktor , that should be all of your comments addressed except Finder::create()->files()->name('*.php') and the inherited require_once , both in ApplicationResolver::getProjectClasses.
I'm not sure if they're in this pull req's scope - maybe I should try to clean them up in another pull request after you're otherwise happy with this one?

@szepeviktor I just waited to add my two cents on the removal of the find and require_once.
I have recently tackled a similar issue and had to build a custom class finder. If you want I could either
A) Publish a package to find classes in directory
Or
B) Advise @CyberiaResurrection on how to reproduce similar functionality
What's your preference?

@c-harris We welcome your advise!
Please note that the logic is dangerous not the implementation!! See #284

@szepeviktor i think the danager could be heavily mitigated removing the need to include get declared classes and the require (And exexution) of the files.
If composer/composer was added as a dep then the directory information gained from the new getProjectSearchDirs method added by @CyberiaResurrection could then be piped into
Composer\Autoload\ClassMapGenerator::createMap
That would yield a set of classes (as name) and the files (as key). They would then invoked by the autoloader in the class_parents call.
Thoughts?

@szepeviktor , I was reluctant to expand the dependency list on my own because I've had pull requests rejected for that reason before.
However, adding composer/composer and proceeding as @c-harris suggests seems to be the easiest way forward to defuse your concerns.  I'll welcome a better idea, from anyone.

I would agree any solution that avoids iteration through files.

@nunomaduro Please weigh in with your opinion.

@szepeviktor , @nunomaduro , I've followed @c-harris' suggestion and used the composer ClassMapGenerator's createMap method.  Is this what you were thinking of, @szepeviktor ?

I am just a janitor here!

I am just a janitor here!

Almighty janitor you may be (and an extremely helpful one, to boot), @szepeviktor , is my commit where I introduced ClassMapGenerator::createMap what you had in mind when you were asking me to nuke Finder and require_file?

:)
Yes, it is.
@nunomaduro Please take another look at it.

@nunomaduro , I've just rebased this, for ease of merging, on top of the other pull reqs that have landed since this one did.  Is there anything else you want me to clean up, or can this PR be merged?

This looks good :+1:

Ok, looks like I've missed something here and I hope you can help me, @canvural - do I need to request specific reviewers for this PR, or can anyone with write access jump in and mark it approved?

@nunomaduro No, you didn't miss anything. @nunomaduro is the only one with the write access. And at the end its his decision for merging. I just gave my opinion.

This may be an important change - I will test it out tonight.

@canvural , thanks for your patience and your explanation.
@nunomaduro , thank you for your patience, too - sorry for being a little eager.

@nunomaduro as changes go this one has helped me solve a problem where I had to separate my project into two but required the same service provider (Or specifically fascard) on both.
Just wanted to add my two cents here, I'm keen yo see it incorporated.

@canvural Leaving this one to you. We just need to make sure that Larastan works on:

Laravel packages
Lumen apps
Laravel apps

Sure. I can test it. Then let you know. (I guess I don't have rights to merge)

@canvural You are admin - so you should have rights 👍

@nunomaduro This is good to merge! But I can't merge because it says Required status check "continuous-integration/styleci/push" is expected. :man_shrugging:

Laravel packages

Lumen apps

Laravel apps

A package is tested: Larastan itself
Lumen is tested
The default Laravel app is tested.

@canvural , should I send up a dummy commit to trip the CI infrastructure again?

@CyberiaResurrection I'm not sure how the StyleCI push system works. I've never seen it work.
Or we can wait @nunomaduro to help :smile:

@canvural , if the StyleCI push bitz aren't working, are you able to merge this PR anyway?

No. It doesn't let me.


NavigationService for detail part of MasterDetail page

How must the NavigationService and routes be set to be able to navigate further from the Detail page to another page with additional details ?
I have for instance an application where the Detail page contains an image. When clicking on the image a new "very detailed" page with additional details and a back button should be opened. (something like "/DetailPage/VeryDetailedPage" )

You could use the NavigationParameter in combination with your routing Action. The routing action could either pass on the request or coordinate displaying of the detail page itself.


Unable to start a local server

Describe the bug
So yesterday everything was working fine but today when i tried to start a sever by " npm run dev " i am getting these errors

i also created a new svelte kit project same error showing. but if create a vue.js project the server does run and work just fine
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-8zp2zt?file=README.md&terminal=dev
existing or new project i does not work
Logs
No response
System Info
System:
    OS: Windows 11
    CPU: (4) x64 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
    Memory: 10.91 GB / 15.89 GB
  Binaries:
    Node: 18.16.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1778.0)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.1.0
    @sveltejs/kit: ^1.5.0 => 1.20.4
    svelte: ^3.54.0 => 3.59.1
    vite: ^4.3.0 => 4.3.9

Severity
annoyance
Additional Information
i really need to see what goin on with my code of course

https://github.com/sveltejs/kit/issues/10252

This suddenly started happening for someone else recently - #10252 - it's very peculiar. Their solution ended up being to upgrade Node. I really don't know what's happening here.

Thank fixed by upgrading the node version


[FEATURE] phobos-1.0.0 GUI plugin

Is your feature request related to a problem? Please describe.
i use a different resolution and the normal gui is oversized, so i need to click on the phobosGUI module everytime i enter the clickgui and its getting annoying
Describe the solution you'd like
make it so that i can disable/enable the phobosGUI plugin module anytime i want

just bind the phobosGUI module lol

I don't support the old plugins rn, sorry. Especially not the phobos-gui plugin as it was thrown together quickly.


Update github issue templates

What needs to be done?
Modify the github issue templates in showcase to be used as default templates for all other repositories in the janus-idp organization.

Will backtrack on this in favor for more generic templates


Wish I could use it ..

Hi,
I stumbled on your Grid component for MVC6 (CORE) -- I installed it, but don't understand the instructions -- for example, where do I find: ~/.nuget/packages/NonFactors.Grid.Mvc6/1.3.0/content. ???
Did they install somewhere in my Project when I installed the package?  I cannot find any information on how to get it working properly.   Looks great, but I could use some help using it, it's not intuitive (yet).

It's the global nuget installation folder, back in MVC5 it used to install it in solution folder in packages folder.
Now it's in your user folder under a name of .nuget, which holds all the files.
If you are on windows it's something like this: C:\Users\<user>\.nuget

Did you managed to get it working?

Yes - Thanks for the info about where nuget places the files in MVC6.  It's a well done grid.  I'll test it some more when I get back to my Views and let you know of any problems.  Thanks for your help.

@Muchiachio can you please include this in the Installation guide as I can across this one too. I know it might be obvious for some folks, but not so much for others. Thanks for the great work!

@MiroValchev, this is for core and .net installations, although a sentence about that was already included
Include grid css files, they can be found ~/.nuget/packages/NonFactors.Grid.Mvc6/{version}/content.
But I'm not sure how to specify the path for all the platforms (win, linux, etc), so I wrote
~/.nuget/packages/.... Any suggestions on what you expected but didn't found?
NonFactors.Grid.Core.Mvc6 version only contains the grid dll, all the content is at NonFactors.Grid.Mvc6.

@Muchiachio probably something like this:
Included grid partial views to your Views/Shared folder, they can be found at ~/.nuget/packages/NonFactors.Grid.Mvc6/{version}/content.
(On Windows nuget's path should be something like this: C:\Users<user>.nuget )

Ok, I will try reworking the installation notes.


Issue with adding a new todo

After signing in using your gmail account for 2nd or 3rd time , new todo item is not getting added in the list on clicking the add button , it replaces the previous todo item.  The delete and mark todo completed icon is also not working . Please watch the provided video for reference :-
https://github.com/AKSHAYBHOPANI/cloud-todo/assets/75109574/a575d411-c10b-41fd-9f52-59c2f3228765

It seems Firebase isn't working. Please check the security rules, it should be open to all and date should be of future.


SyntaxError: Bad escaped character in JSON at position 21     at JSON.parse [Bug]

I cannot run the code due to the error:
[2022-12-27 18:46:14] [error] Failed to read config file!
[2022-12-27 18:46:14] [error] SyntaxError: Bad escaped character in JSON at position 21
    at JSON.parse (<anonymous>)
    at ConfigurationParser.parse (file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/configuration_parser.js:57:31)
    at file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/index.js:351:42
    at Generator.next (<anonymous>)
    at file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/index.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/index.js:3:12)
    at main (file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/index.js:348:12)
    at file:///C:/Users/Hasan/OneDrive/Masa%C3%BCst%C3%BC/Twitch-Drops-Bot-dev/dist/index.js:706:5
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Changed the location and the error:
[2022-12-27 18:51:01] [error] Failed to read config file!
[2022-12-27 18:51:01] [error] SyntaxError: Bad escaped character in JSON at position 21
    at JSON.parse (<anonymous>)
    at ConfigurationParser.parse (file:///C:/Twitch-Drops-Bot-dev/dist/configuration_parser.js:57:31)
    at file:///C:/Twitch-Drops-Bot-dev/dist/index.js:351:42
    at Generator.next (<anonymous>)
    at file:///C:/Twitch-Drops-Bot-dev/dist/index.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (file:///C:/Twitch-Drops-Bot-dev/dist/index.js:3:12)
    at main (file:///C:/Twitch-Drops-Bot-dev/dist/index.js:348:12)
    at file:///C:/Twitch-Drops-Bot-dev/dist/index.js:706:5
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Your config file is messed up.
Paste it into there and see if you can fix it: https://jsonformatter.curiousconcept.com


Request to Continue Support and Maintenance

Hi, I love using this extension and noticed a message that it may soon no longer be supported. I think it would be great if the team could continue to maintain or update it.

Apparently, there are no plans to switch to Manifest V3. Too bad :/

Apparently, there are no plans to switch to Manifest V3, so your browser will eventually disable the extension in a few weeks. It was nice while it lasted.

Apparently, there are no plans to switch to Manifest V3, so your browser will eventually disable the extension in a few weeks. It was nice while it lasted :smile:


Find out a way to setting up the database tables/spreadsheet in consistent way

Description:
Currently, we are generating SQL scripts as we only have a DB Client. Since we are supporting spreadsheet support as well. We need to find a consistent way to support setting up the servers for the persistent application.
@sahanHe Can you list down the steps we need with the HTTP endpoint to setup gsheet to startwith.

One option is to create an HTTP Client script like in the plugin [1] for the gsheets API. And keep SQL scripts for the DB Client

https://marketplace.visualstudio.com/items?itemName=humao.rest-client

We can use ballerina google sheets connector to generate a .bal  file containing the required code to create spreadsheets and worksheets to store the data. We can ask the user to run the generated .bal file. A sample .bal file to create spreadsheets/sheets for a single entity would look like following.
import ballerina/io;
import ballerinax/googleapis.sheets;

sheets:ConnectionConfig sheetsClientConfig = {
        auth: {
            clientId: clientId,
            clientSecret: clientSecret,
            refreshUrl: sheets:REFRESH_URL,
            refreshToken: refreshToken
            }
        };

sheets:Client spreadsheetClient = check new (sheetsClientConfig);

public function main() returns error? {
    sheets:Spreadsheet spreadSheet = check spreadsheetClient->createSpreadsheet(worksheetName);
    io:println("SpreadSheet ID :" + spreadSheet.spreadsheetId);
    sheets:Sheet workSheet = check spreadsheetClient->addSheet(spreadSheet.spreadsheetId, "OrderItems");
    _ = check spreadsheetClient->appendRowToSheet(spreadSheet.spreadsheetId, workSheet.properties.title, ["orderId", "itemId", "quantity", "notes"], "A:E", "USER_ENTERED");
    _ = check spreadsheetClient->removeSheet(spreadsheetId, 0);
}

If we use the http endpoint to initialise the spreadsheets, steps would be similar to following.

Create the spreadsheet using create API and return the spreadsheetId to the user.
For each entity, a sheet will be created in the spreadsheet using batchUpdate API.
For each entity, the column headers should be appended using append API

Decided to use app scripts for google sheets and SQL scripts for RDMS. Hence closing the issue


Added Linked_List_Insertion_sort.cpp

Sorting a Linked List using Insertion Sort in C++.

taking up this issue ...

Is the linked list only single linked list ?

@Anshuvats I want to take this issue and will upload PR sortly.

@Panquesito7 hey I would like to work on this!

@Panquesito7 hey I would like to work on this!

I Would also like to work on this

@Panquesito7 hey I would like to work on this!

@vj-codes  assigned

Hello, I want to work over this, please assign it to me.

Hello, I want to work over this, please assign it to me.

I guess someone is already working on this. Thanks

hi can you assign this to me

Hello Maintainer,
I want to solve this problem ,please assign this issue to me.

Hello,
Can u plz assign this issue to me?


Cuml updated

Add cuml

@martinkim0 Can you check how to include an aws workflow to run the cuml version? Installing the cuml version is analog to installing rapids-singlecell and faiss-gpu and supposedly works with: pip install '.[cuml]' --extra-index-url=https://pypi.nvidia.com #CUDA12. Tests are working locally.

Is the reason we need AWS runners for GPU access? I've been using self-hosted runners (Stanley workstations) for running scvi-tools tests on GPU. If we need AWS for another reason, I think the most straightforward way is to use cirun (AnnData uses this).

Self-hosted is completely fine. We just need a server with CUDA.


static_url_path doesn't work if it ends with a slash

https://github.com/pallets/flask/blob/a74864ec229141784374f1998324d2cbac837295/flask/app.py#L560
Urljoin seems like more robust way to join urls. I just tried to set static_url_path = '/' and it failed, but static_url_path = '' succeed. IMHO, this is bad and unexpected behaviour.

I'm pretty sure urljoin always throws away existing path segments on the first arg. .rstrip('/') is probably better here

Making the static url path the root is probably going to give you unexpected behavior.

i will be taking a look at this issue

@davidism wrote:

Aside, making the static url path the root is probably going to give you unexpected behavior.

Could you say more (and should that be documented)? I’ve seen a number of Flask users do this (to serve a SPA that assumes it’s mounted under /) who haven’t yet seen unexpected behavior.

The URL rule is /{static_url_path}/<path:filename>. When static_url_path is empty, it becomes /<path:filename>, which is a catch-all route. Some route sorting that Werkzeug does may alleviate this, but you're just asking for trouble.
There are better ways of serving SPAs than passing it through Flask. In development, SPAs have their own dev server that should be used, and either they or Flask would set up a proxy to keep everything under one domain (Werkzeug has proxy middleware now). In production, Nginx would be configured to serve the static files and leave Flask to do backend things.

Yes, we have it set up so SPA dev servers work in development. And in production we use gunicorn with Whitenoise to serve static files, running behind Waiter.
Since the /<path:filename> static route has been working well for us (perhaps thanks to Werkzeug's route sorting), I'm wondering if there's a concrete example of where this wouldn't work well.
For example, we know that any route /foo we define precludes serving a static file named foo from the static folder, and haven't had any problems with that. (~All the API routes we define end up under a prefix like /api/ thanks to Flask-Rebar, which helps reduce potential for conflict.)
But eager to know if there are any compelling examples of nasty cases I'm missing!

It sounds like you've only been generating the urls, not using Flask to actually serve the files. If you're using a proxy in dev and whitenoise in prod, routes that would be problematic aren't reaching Flask, so you won't see the issue.

Meant to add, this post recommends this, and was referenced in https://github.com/pallets/flask/issues/348#issuecomment-178443482 – so if this recommendation actually comes with caveats it'd be good to have some docs about it – should I open a new issue?

I don't actually have a reproducible example, just a general remembering of old issues and questions. I think there were some changes to Werkzeug that may have addressed it too, but it's been too long for me to remember. If people don't seem to be running into the issue, I wouldn't worry about it for now.

Here's a reproducible example:
from flask import Flask
app = Flask(__name__, static_url_path='')

@app.route('/405/', methods=['POST'])
def hello_world():
    return 'Hello, World!'

For get requests this view should return 405 NotAllowed but instead returns a 404 Not Found.


Add LoggerFactory.mapK

I've been playing around with Natchez and natchez-extras-log4cats. This proved to be a required step to use LoggerFactory rather than instantiating a Kleisli logger and passing around explicitly/implicitly.
I would have applied this to LoggerFactoryGen but with the override type I struggled, I think you would need to lift it into the typeclass signature, but suggestions welcome.

Maybe slightly redundant but I've added a compilation check like the LoggerSyntaxCompilation

This is exactly what I need, thank you! When might we see this included in a new release?

Oh, we really didn't release this. I think it'd be fine to do a new minor release v2.3.2. Will sort out it.

Thank you :heart:


Simplify Extraction-Service Integration within TDS

Simplify the integration of the Extraction Service within the TDS platform to enhance functionality.

@brandomr i assigned you this task because we talk about it. But I will let you figure out if you want to keep this in this GitHub project or just update us on our weekly sync meeting.

Sounds good--will keep you posted on this

This is not worth or ressources


[tracking] Update list code owners in insights-results-aggregator-mock repository

Update list code owners in insights-results-aggregator-mock repository

Implemented in https://github.com/RedHatInsights/insights-results-aggregator-mock/pull/163


Added GLB example with MIG as backend

Hi,
as agreed with Simone I added and example of the GLB module using a MIG as backend.
Thanks

Can you put an actual MIG module and template in the example?

Done!

@eliamaldini what's the status of this? Can you fix the tests and merge?


use the new location for extracting release notes

@chidozieononiwu pointed out that this file has moved on a bit from our other version. The release notes extraction has been extracted for reuse.

@chidozieononiwu if this still needs fixing please go ahead and open another PR, but I believe you fixed it with your other work.


[Feature request] @EqualsAndHashCode Flexibility for rank properties for equal/hashcode method

Given some special cases where we need to explicitly order the comparation fields for performance improvement, I have applied the same idea that we have for @ToString.Include(rank = -1). ie.: @EqualsAndHashCode.Include(rank = -1)
Also, there are some discussions related to this here (#1543) about the Equals algorithm and performance. So, given this flexibility can help me with some special cases and I believe that can be helpful for more people too. Let me know what you think folks.

hello @rspilker , could you take a look at this PR? This improvement would help me given that I use to need to tunning java code and be able to handle those equals configuration through Lombok would be helpful and keep the code clean.

Great job!
I love that you've even added a test case, and added you name the the AUTHORS file.

This also opens the door to give primitives as default rank. We could document them to have a default of 1000 for instance.

I'm nearly done


Add instructions for using a nightly build of the Blazor Language Service VSIX

Fixed by https://github.com/aspnet/Blazor/commit/479c32a0bc349504402cb6eba634ed5088e0747e


Publish edge version to PyPi

Publish the EDGE release to PyPi, i.e. when pushing to the default branch (develop). Having access to the edge version will contribute to accelerate testing of the client.

Publish to https://test.pypi.org/

Be careful when doing this. I'm unsure if there is a way to overwrite a pypi tag

It would have been nice to publish an "edge" version, but PyPi does not allow to overwrite version, which in generate is an excellent best practice. Instead of relying on an edge version, I'm install the "edge" version from the source code after doing docker pull on the branch develop in combination with pip install -e ..


feat: add clearTxn for user testing, update User Guide with clearTxn command

Added clearTxn to parser for testing
Added documentation for the clearTxn command in the User Guide.
Updated the Command Summary for Transactions section.

closes #84

Try squash merge

@Dino-Nuggies Would you like to try to review this PR?


New compute example

Hi again - I've built an example using your API - it does compute properly and I can pass/return CPU buffers but I am having trouble with the storage image type: the shader will call GLSL imageSize() but the results are uninitialized values and vary each execution.
I am not yet sure if this is a misuse of the API or an issue with the beta NVIDIA drivers I'm using to run Vulkan.
If you see anything simple I'm doing wrong I would love to be able to add this to your codebase - I'm continuing to debug it.

Nice!
I guess you used an AttachmentImage because it was the most appropriate type. However an AttachmentImage isn't supposed to be used for anything else than an attachment. The unsafe code knows that and forces the layout of the image to be COLOR_OPTIMAL, which is an invalid use of Vulkan.
As a hack, you could try change this line to Layout::General to see if it works.
Instead the proper way it should be done is by creating a new type named StorageImage.

That's exactly what I tried doing - but I had problems with my implementation: MutableImage. AttachmentImage seemed close enough but no dice. Based on your comments I think I'll investigate that route more now.

The other problem you're probably encountering is this: https://github.com/tomaka/vulkano/blob/master/vulkano/src/descriptor/descriptor_set/pool.rs#L40-L62
You should add a STORAGE_IMAGE entry.

Closing this and my other pull so I can work my changes into branches.


Add attack on PyTorch dep chain (AV-509)

https://pytorch.org/blog/compromised-nightly-dependency/

This solves issue 70


Changing the config file does not update the site

Similar to this closed issue https://github.com/longpdo/neumorphism/issues/18

I deleted index.html under _sites.


JBPM-5708 MapDB implementation of persistence for Drools and jBPM

Implementation of MapDB persistence layer for Drools and jBPM persistence. This requires a set of modifications:

Creating drools-persistence-api and jbpm-persistence-api
SingleSessionCommandService refactors
PersistenceContext and ProcessPersistenceContext refactors:
TaskPersistenceContext refactors
Changes in the current persistence model interfaces
TimerJobFactoryManager / TimerService refactors

Closing this one in favor of #212


Provided bash script does not work on Git Bash on Windows

I feel the provided bash script here should have an alternative that works easily on Windows.  I'm sure this works great on Mac/Linux, but Git Bash has a really hard time parsing this into a valid set of commands.  I'm still working on a work-around.

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

ID: 12009c1f-282d-2632-fac0-64b09c432833
Version Independent ID: 6052d3d4-d295-9340-b16d-4c200e34cd73
Content: Create an HTTP ingress controller with a static IP address in Azure Kubernetes Service (AKS)
Content Source: articles/aks/ingress-static-ip.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

For what it's worth, pasting this code directly into the Cloud Shell does work.

@nibblesnbits that is fair feedback. We design this guides either to work in the Azure Cloud Shell CLI environment or in PowerShell (Both Cloud and Local). You are correct that they commands do not always translate well to Git Bash. One long term issue with developing them for on Git Bash is if the environment changes then the scripts would have to be updated often. Since we have control over the Cloud Shell and PowerShell the updates to the scripts are needed much less often.
At this time we plan to continue to develop the bash scripts to work in Cloud Shell but your feedback is noted.
CC @iainfoulds who is the author of these docs for awareness.


topgrade: 5.5.0 -> 5.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/r-darwish/topgrade/releases.
meta.description for topgrade is: "Upgrade all the things"
meta.homepage for topgrade is: "https://github.com/r-darwish/topgrade"
meta.changelog for topgrade is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.7.0 with grep in /nix/store/6kv8jhm5yiwijlzm3b3wcnrjnaprkhzh-topgrade-5.7.0

directory tree listing: https://gist.github.com/92aa9ad405961c07e5d8f6a4c11a11a4

du listing: https://gist.github.com/6bfa113e55085be623e6c56c451e9394

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
topgrade

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

topgrade

Maintainer pings
cc @filalex77 @hugoreeves for testing.

@GrahamcOfBorg eval


Infinite loop causing OOM when walking stack in minidump-processor

On commit https://github.com/luser/rust-minidump/commit/ebbee33763b4788ef33451a98fd4ecb90ebd91a3, running cargo fuzz run process oom (attached below in a .zip file) will infinitely loop in the following while statement, pushing more stuff to the frames vec until you eventually OOM.
https://github.com/luser/rust-minidump/blob/a32419975ba6f190081a148f04a41fc42aa4eb26/minidump-processor/src/stackwalker/mod.rs#L174-L193
oom.zip
Bailing out if you ever see a frame twice sounds smart.
Are instruction pointers always monotonically increasing/decreasing? If so, we can do this perfectly accurately in O(1) per frame by just checking that the instruction pointer is always increasing or decreasing by at least 1 byte per frame.

We already enforce forward-progress but it appears I forgot to port the Arm fix in #309 to Arm64 and OldArm64

(Arm leaf functions can genuinely not use the stack at all because the link register creates a buffer of one call where you don't even need to push a return pointer, so the unwinder needs to allow forward progress to not occur for the top of the stack, but after that it needs to be strict again)

(So very good catch, this a real annoying bug we've seen in the wild!)


fix(react-appkit): client fallback pending state

copilot:all

Current dependencies on/for this PR:

main

PR #2942   👈

This comment was auto-generated by Graphite.


GitHub default branch should be main not master

When generating a new package folder interactively, you need to manually change the default branch from master to main to comply with GitHub's current default (the latter). This needs to be updated.

I think PkgTemplates is doing everything it can on this side:
https://github.com/JuliaCI/PkgTemplates.jl/blob/8b857be7f1ec51518d47d9464baa7cfa34d3f1f9/src/plugins/git.jl#L1-L15
The problem is likely further upstream, maybe libgit2 is still using master as default?

I always use PkgTemplates via the interactive generate() process. FTR all of my new packages get main instead of master for a long time now. Not that I care.


chore: automated PR to update ReleaseNotes for 000000.00.1 VHD

This is an automated PR to bump ReleaseNotes for the VHD release with image version 000000.00.1

test PR for automation changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3032

Relevant Lines:
3937

💛  - Coveralls


[SPARK-37979][SQL] Switch to more generic error classes in AES functions

What changes were proposed in this pull request?
In the PR, I propose to switch from specific error classes in the AES functions: aes_encrypt()/aes_decrypt() to more generic:

AES_CRYPTO_ERROR -> INVALID_PARAMETER_VALUE
INVALID_AES_KEY_LENGTH -> INVALID_PARAMETER_VALUE
UNSUPPORTED_AES_MODE -> UNSUPPORTED_MODE

The new error classes INVALID_PARAMETER_VALUE and UNSUPPORTED_MODE are made to be re-used from other functions but not only in the AES functions.
Why are the changes needed?

To prevent unlimited inflation of the set of error classes and as a consequence of that inflation of error-classes.json.
To establish rules for other sub-tasks of SPARK-37935

Does this PR introduce any user-facing change?
Yes, but the AES functions aes_encrypt()/aes_decrypt() haven't released yet.
How was this patch tested?
By running the affected test suites:
$ build/sbt "test:testOnly *SparkThrowableSuite"
$ build/sbt "test:testOnly *QueryExecutionErrorsSuite"

@cloud-fan @sarutak @srielau @entong Could you review this PR, please.

Merging to master. Thank you, @cloud-fan .


Add missing get and set in extHostModelView for title and validationErrorMessage

Missed updating this file in #8909 and #13084 so only
projectFilePathTextBox.updateProperty('title', this._projectFile)
worked, but
projectFilePathTextbox.title = this._projectFile
wasn't working (and same for validationErrorMessage)

Pull Request Test Coverage Report for Build 332266604

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 39.679%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/api/common/extHostModelView.ts
0
4
0.0%

Totals

Change from base Build 331658025:
0.01%

Covered Lines:
20614

Relevant Lines:
47708

💛  - Coveralls


Couldn't connect to any seeds

Followed Install Osmosis, then Joining Mainnet, forwarded the p2p port in my router, but when running cosmovisor, this is printed to the log repeatedly -
Jan 29 19:56:42 box cosmovisor[1175835]: 7:56PM INF Ensure peers module=pex numDialing=0 numInPeers=0 numOutPeers=0 numToDial=40
Jan 29 19:56:42 box cosmovisor[1175835]: 7:56PM INF No addresses to dial. Falling back to seeds module=pex
Jan 29 19:56:42 box cosmovisor[1175835]: 7:56PM INF Dialing peer address={"id":"f515a8599b40....b11a668","ip":"...hidden...","port":26659} module=p2p
Jan 29 19:56:43 box cosmovisor[1175835]: 7:56PM ERR Error dialing seed err="dial tcp ...:26659: i/o timeout" module=p2p seed={"id":"f515a8599b40....b11a668","ip":"...","port":26659}
Jan 29 19:56:43 box cosmovisor[1175835]: 7:56PM INF Dialing peer address={"id":"63aba5....60d7561791dca8","ip":"...hidden...","port":2000} module=p2p
Jan 29 19:56:43 box cosmovisor[1175835]: 7:56PM ERR Error dialing seed err="auth failure: conn.ID (21d7539792ee2e0....56ae0cf499e) dialed ID (63aba59a7da51....1791dca8) mismatch" module=p2p seed={"id":"63aba59a7da....561791dca8","ip":"...","port":2000}
Jan 29 19:56:43 box cosmovisor[1175835]: 7:56PM ERR Couldn't connect to any seeds module=p2p

Any idea what could be the issue?

Our (Notional's) seed's node ID has changed.  Also been working to put a seed in akash.  I'll try to get both into init.go and that should resolve this.  Thanks!

So after file has been updated, checkout and rebuild to fix - or should I also osmosisd init NODE_NAME?

Is there any workaround in the meantime, so it would be possible to start a node?

https://github.com/osmosis-labs/osmosis/blob/main/networks/peers.md
:)
Sorry about that!  So what I'm going to do here to make sure that others don't run into this issue is put all of Notional's relay nodes in that file.  Very specifically, what happened is a few weeks ago we had a disk failure on the server that's currently in init.go.
I think it's really important that osmo be very easy to stand up, so I'll get 3-4 nodes in there from here on in.
Cheers!

Going to keep this open until it lands in a release or the installer at get.osmosis.zone

In the mean time, a workaround is to edit ~/.osmosis/config/config.toml, then edit line with seeds = "..." to contain peer IDs with some peers from https://github.com/osmosis-labs/osmosis/blob/main/networks/peers.md
After that restart the node.

The mentioned workaround is not working for me.
I updated the seeds = "..." from the peers.md file, but still I cannot connet to mainnet. The nodes either give timeout or connection refused error.
Also the ufw on ubuntu server is disabled.
I get the following error:
Feb 10 17:41:18 Ubuntu cosmovisor[337259]: 5:41PM INF Ensure peers module=pex numDialing=0 numInPeers=0 numOutPeers=0 numToDial=40
Feb 10 17:41:18 Ubuntu cosmovisor[337259]: 5:41PM INF No addresses to dial. Falling back to seeds module=pex
Feb 10 17:41:18 Ubuntu cosmovisor[337259]: 5:41PM INF Dialing peer address={"id":"23142ab5d94ad7fa3433a889dcd3c6bb6d5f247d","ip":"<IP_ADDRESS>","port":26656} module=p2p
Feb 10 17:41:18 Ubuntu cosmovisor[337259]: 5:41PM ERR Error dialing seed err="dial tcp <IP_ADDRESS>:26656: connect: connection refused" module=p2p seed={"id":"23142ab5d94ad7fa3433a889dcd3c6bb6d5f247d","ip":"<IP_ADDRESS>","port":26656}
Feb 10 17:41:18 Ubuntu cosmovisor[337259]: 5:41PM INF Dialing peer address={"id":"83adaa38d1c15450056050fd4c9763fcc7e02e2c","ip":"<IP_ADDRESS>","port":26656} module=p2p
Feb 10 17:41:19 Ubuntu cosmovisor[337259]: 5:41PM ERR Error dialing seed err="dial tcp <IP_ADDRESS>:26656: i/o timeout" module=p2p seed={"id":"83adaa38d1c15450056050fd4c9763fcc7e02e2c","ip":"<IP_ADDRESS>","port":26656}
Feb 10 17:41:19 Ubuntu cosmovisor[337259]: 5:41PM INF Dialing peer address={"id":"6bcdbcfd5d2c6ba58460f10dbcfde58278212833","ip":"<IP_ADDRESS>","port":26656} module=p2p
Feb 10 17:41:20 Ubuntu cosmovisor[337259]: 5:41PM ERR Error dialing seed err="dial tcp <IP_ADDRESS>:26656: i/o timeout" module=p2p seed={"id":"6bcdbcfd5d2c6ba58460f10dbcfde58278212833","ip":"<IP_ADDRESS>","port":26656}
Feb 10 17:41:20 Ubuntu cosmovisor[337259]: 5:41PM ERR Couldn't connect to any seeds module=p2p

In the mean time, a workaround is to edit ~/.osmosis/config/config.toml, then edit line with seeds = "..." to contain peer IDs with some peers from https://github.com/osmosis-labs/osmosis/blob/main/networks/peers.md
After that restart the node.

Updated seeds got into a v6 point release. Please do encourage more people to contribute seed nodes to it though!


doesn't work when generate with user name and password

Traceback (most recent call last):
File "generate.py", line 175, in
main()
File "generate.py", line 168, in main
SETTINGS['server'], SETTINGS['quality'], SETTINGS['time_shift'], SETTINGS['file'])
File "generate.py", line 104, in create_playlist
credentials = get_service_creds(site, username, password)
File "generate.py", line 51, in get_service_creds
raise Exception('Unknown error')
Exception: Unknown error
PS C:\Users\marca\Desktop\smoothstreams-playlist-generator-master> python generate.py --site  mma-tv -u xxxx  -p xxxx
o -q hd -sv d71 --time-shift 7
Traceback (most recent call last):
File "generate.py", line 175, in
main()
File "generate.py", line 168, in main
SETTINGS['server'], SETTINGS['quality'], SETTINGS['time_shift'], SETTINGS['file'])
File "generate.py", line 104, in create_playlist
credentials = get_service_creds(site, username, password)
File "generate.py", line 51, in get_service_creds
raise Exception('Unknown e


Claimed Land Not Reverting After 2 Months

Hi, I am currently having issues with a town located next to mine. It is my understanding that claims are supposed to revert to unclaimed land after 2 months of inactivity. However, the town next to mine named "Gekkemannen" has 2 members, one of which hasn't been on in 74 days, and the other has not been on for 127 days. With that being said the claim is still active and it is now getting in the way of me expanding my town. I would like to know if someone could either forcibly delete or unclaim the town area.

Duplicate, will have to be tested. Closing in favour of more completed, main ticket.

Duplicate, will have to be tested. Closing in favour of more completed, main ticket.


Fix preview for Pages

Preview doesn't direct us to the correct URL for pages (just /[uid]) and therefore displays a 404.

in prod


Fix replacement of newlines around postfix/prefix operators

Determine whether to replace newlines before/after postfix/prefix operators (++ and --) with semicolons or whitespace by inspecting the tokens immediately before and after and applying the JavaScript rules for valid syntax.
Fixes issues #47 and #49.

Just noticed that pull request #50 also addresses some of the same issues.
Not sure why the build is failing - only the PHP 7 build is, because Class 'PHPUnit_Framework_TestCase' is not found - is PHPUnit not configured correctly?

I'm not able to maintain this project, I'm thus closing this PR before marking the repository as abandoned. Thanks for your understanding.
Feel free to fork the project of course!


🐛 The Swift pod VisionCamera depends upon React-Core, which does not define modules.

What

Hi!
After installing the library on a react native project version: 0.63.2 I get the error below in Logs when running npx pod-install .
If I add  use_modular_headers I get this issue at build time for glog pod. ->  Import of module 'glog.glog.log_severity' appears within namespace 'google'
Any guidance on how to get past this issue is much appreciated.
Logs

The Swift pod `VisionCamera` depends upon `React-Core`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

Reproducable sample
// code here

Environment

Platform(s):

[x] iOS
[ ] Android

react-native version: 0.63.3
react-native-vision-camera version: 2.0.0
react-native-reanimated version: 2.1.0

Hm, I believe the React-Core dependency shouldn't be used since it is an umbrella pod.
I wonder how you could install Reanimated, since they also specify React-Core in dependencies 🤔
Could you try removing the React-Core dependency from VisionCamera.podspec and see if it builds? There might be some things missing that you have to add via another dependency..

@dan10gc 🏓

@mrousavy I apologize for not getting back to you earlier. So I was actually able to successfully install the pod files for vision-camera after I updated my project to  react-native 0.64.0. I think one of the changes was they updated the RCT-Folly pod they were using and that got rid of the error. I then followed all the troubleshooting steps in the documentation and I was able to use the <Camera/> component. :)

Can confirm this error goes away once you update to 0.64.1 or later


[Translation] En la pajarería a las 22.30 h (Korean)

translating more scenarios. When I finish testing, I'll upload it.
What kind of translation do you want to add (mark with an X, e.g. [X] Descent)?

[X] Mansions of Madness
[ ] Descent

Scenario name or url
En la pajarería a las 22.30 h

Translation File
Localization.Korean.txt

Wow, great work translating so many scenarios into Korean. Congratulations!

I want to show you guys a scenario made in Korea. I'll upload it when it's ready.

I want to show you guys a scenario made in Korea. I'll upload it when it's ready.

Awesome. Willing to give it a try!
I've sent a message to this scenario author to notice him about your translation. He was delighted with the translation!

Thanks for the Translation, We're so glad! I uploaded the translation this morning.

Thanks for the Translation, We're so glad! I uploaded the translation this morning.

Wow Very quick update Thank you!
The next scenario is also ready to be translated.
I'm looking forward to it!

@cheeseguyhcl Congrats! You can now close this issue, if you don't mind.


fix typo

There was an area where long taps did not respond when the phone was in landscape mode, so this has been fixed.

Yes, I had seen this problem but I didn't know the reason. Thank you!


README: add MacPorts installation instructions

https://ports.macports.org/port/atuin/

No worries, thank you for Atuin :)

I just realised you're the package maintainer there! That's awesome :) Please do let us know if you have any issues!

I just realised you're the package maintainer there! That's awesome :) Please do let us know if you have any issues!

Of course. Thank you :)


fix(flake): add prover directory

What ❔
add prover directory to rust src in flake.nix
Why ❔
src is filtered, so rebuilds only happen, if actual rust source was changed.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zk fmt and zk lint.
[ ] Spellcheck has been run via zk spellcheck.
[ ] Linkcheck has been run via zk linkcheck.

for testing you have to:
$ nix build -L .

then set the correct cargoHash and build for real:
$ nix build -L .

Oh anybody can test it btw...
$ docker run --rm --privileged -it -v .:/mnt nixos/nix:2.19.2

Inside the container:
# echo 'experimental-features = nix-command flakes' >> /etc/nix/nix.conf
# echo 'sandbox = true' >> /etc/nix/nix.conf
# cd /mnt
# nix build -L
[...]
error: hash mismatch in fixed-output derivation '/nix/store/j88cs8gczb9wa8kjriilbjwwx2zd8vzb-import-cargo-lock.drv':
         specified: sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
            got:    sha256-LloF3jrvFkOlZ2lQXB+/sFthfJQLLu8BvHBE88gRvFc=
error: 1 dependencies of derivation '/nix/store/h93f7xg10b49zmazira84yms0g15a885-zksync-0.1.0pre20240322_6988f77.drv' failed to build
[...]

The build will fail... set the correct cargoHash in flake.nix (here sha256-LloF3jrvFkOlZ2lQXB+/sFthfJQLLu8BvHBE88gRvFc=):
# nix run nixpkgs#vim -- flake.nix

and build in the same container instance again:
# nix build -L


Unable to raw_write single resource to two different offsets

When specifying the same resource to be written to two different offsets it fails with the following message.

fwup: raw_write didn't write anything. Was it called twice in an on-resource for 'rootfs.ext4'?

In my setup both partitions should have the same resource written during factory setup. I would like to avoid having to increase the size of my .fw bundle with a duplicate resource. My config currently looks like this:
    on-resource rootfs.ext4 {
        raw_write(${ROOTFS_A_PART_OFFSET}) # Write to the first rootfs partition
        raw_write(${ROOTFS_B_PART_OFFSET}) # Write to the second rootfs partition
    }

Is this an intentional design decision?

The intentional design decision was to make fwup streamable for updates (i.e. no disk space is required to hold the .fw file on device). Everything flows down from that decision. That's why you can't write a resource twice, since it would either require caching the whole resource or rewinding. In theory, there's nothing preventing a function like raw_write2 that writes the file to two places while it's being streamed through, but it starts getting weird.
I have a couple ideas for you:

Call fwup twice to create the factory image. You'll need two tasks to do this.
Don't write rootfs B in the factory.

In all of my setups, I've convinced myself that if the B partition ever gets loaded from a clean factory install on A, then something is really wrong that needs to be investigated. I actually intentionally write zeros to the beginning of the B partition in the factory image so that I know it is invalid just in case someone is refurbishing a device that didn't make it through manufacturing the first time.
Also, I'm not set against figuring out a way to support a multiple write feature, so let me know your use case and maybe we can figure something out.

That makes complete sense. This would only be need in the factory and so I'm happy to just create two tasks and run fwup multiple times during setup.
Thanks for taking the time to explain.