Introduce queries to avoid problems when performing completion for enums with many variants

This change introduces two new queries to compute:

attributes for all variants of an enum, and
attributes for all fields of a variant.

The purpose of this change is to avoid the current n^2 behavior when rendering completion for variants (which prevents completion for enums with large numbers of variants).

This might fix https://github.com/rust-analyzer/rust-analyzer/issues/5397, but I don't have that test file anymore.

This might fix https://github.com/rust-analyzer/rust-analyzer/issues/5397, but I don't have that test file anymore.

bors r+
Would we cool to add a test here (look at accidentally_quadratic test)

bors r+
Would we cool to add a test here (look at accidentally_quadratic test)


Fímir image is broken

public/images/criaturas/pielverdes/fímir.png

Thanks Arturo, issue solved. 👍


Unexpected error in provider "thesubdb"

Soft/Branch/Commit:
SickBeard Custom / master / d6eb72d4e1019e5d1286ae6ac1d7e4b318229ebe
OS:
Linux-4.4.15+-x86_64-with-glibc2.2.5
What you did:
Automatic search
What happened:
I had this error
What you expected:
Subs search on this provider
Logs:
2018-03-23 15:57:10 WARNING  FINDSUBTITLES :: [d6eb72d] Unexpected error in provider u'thesubdb'
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 134, in list_subtitles_provider
    return self[provider].list_subtitles(video, provider_languages)
  File<EMAIL_ADDRESS>line 80, in list_subtitles
    return [s for s in self.query(video.hashes['thesubdb']) if s.language in languages]
  File<EMAIL_ADDRESS>line 60, in query
    r = self.session.get(self.server_url, params=params, timeout=10)
  File<EMAIL_ADDRESS>line 521, in get
    return self.request('GET', url, **kwargs)
  File<EMAIL_ADDRESS>line 508, in request
    resp = self.send(prep, **send_kwargs)
  File<EMAIL_ADDRESS>line 618, in send
    r = adapter.send(request, **kwargs)
  File<EMAIL_ADDRESS>line 508, in send
    raise ConnectionError(e, request=request)
ConnectionError: HTTPConnectionPool(host='api.thesubdb.com', port=80): Max retries exceeded with url: /?action=search&hash=faf62ce6e47e7797b9508b2bd96720c7 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f00799ea350>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

This is an issue with your network that was temporary unavailable:
Failed to establish a new connection: [Errno -3] Temporary failure in name resolution


[CB-8076] Provide error support for browser platform

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android Mac
Link
Link
Link

Let there be tests

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android Mac
Link
Link
Link

Can one of the admins verify this patch?

Merged


Cancel pending promises on resolution

For example, if one passes three promises and the first resolves, .cancel() the other two if they have such a method on the returned Promise. There should be an option to control this behaviour.
I think the implementation of this could be challenging based on the fact that there's no easy way to synchronously check if a Promise has resolved (https://stackoverflow.com/q/30564053).
Refs:

https://github.com/sindresorhus/is-online/pull/43#issuecomment-348755137
https://github.com/sindresorhus/p-timeout/commit/032432734238d696bb88aeb4a6fc5d4ffc454b17

There should be an option to control this behaviour.

Why? I would say we just add it by default, document it, and wait until/if it causes any problems.

I think the implementation of this could be challenging based on the fact that there's no easy way to synchronously check if a Promise has resolved

Why do you need to synchronously check if a Promise has resolved?

Why do you need to synchronously check if a Promise has resolved?

How else would you know which .cancel methods to call out of the passed promises when the first completes, without calling the one that has completed?

Here, we would just cancel the other promises. To know which one is the current promise, we would just pass it in here to the fulfilled function, together with the resolved value. We would also have to catch them and silence the CancelError. But shouldn't be hard.

Right, as you already keep track of what completed, this should be easy to implement. Sorry for not looking at the code earlier and making wrong asumptions.


Fix futureware mirror

Current locations are broken in 3 ways:
$ wget --spider --no-check https://www2.futureware.at/~nickoe/msys2-mirror/x86_64/mingw64
WARNING: The certificate of ‘www2.futureware.at’ is not trusted.
WARNING: The certificate of ‘www2.futureware.at’ hasn't got a known issuer.
HTTP request sent, awaiting response... 404 Not Found
Remote file does not exist -- broken link!!!

Bad certificates - links need to be HTTP until this is fixed

Location has changed - now ‘x86_64’ rather than ‘mingw64’

Final ‘/’ is needed to avoid a redirect:
$ wget --spider www2.futureware.at/~nickoe/msys2-mirror/x86_64
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www2.futureware.at/~nickoe/msys2-mirror/x86_64/ [following]

https://github.com/Alexpux/MSYS2-packages/issues/296

https://github.com/Alexpux/MSYS2-packages/pull/250

https://github.com/Alexpux/MSYS2-packages/issues/163

https://github.com/Alexpux/MSYS2-packages/issues/221


#134 Bots added

@anmode
Under github automation i have added 2 bots
one who will send proper greetings to who files files a PR and other one will close the issues that are more than 45 days old
i hope this counts as a descent contribution :)
i will try to look for fixing more issues :)

@anmode please add gssoc label and level to this pr :)
i will try to contribute more

@anmode please add gssoc label and level on this PR
this would be necessary to make this count in gssco

:(

@anmode Please add the required labels on all the pull requests so that the Pull Requests that are merged are considered for GSSOC'23 contributions.

@anmode @MohitGupta121 bro please remove these labels as i have added the bots in other repo also
so it will be counted in spam
Happy to contribute , will look for some other issues
just remove the labels thanks :)


devicetree: add DT_INST_FOREACH_CHILD macro

The macro iterates through the list of child nodes in a DT_DRV_COMPAT
instance and invokes provided macro for each node.
Signed-off-by: Gerard Marull-Paretas<EMAIL_ADDRESS>

Marking this TSC as I'd like to see this go in for 2.3, so will look for approval from TSC to merge.

@mbolivar-nordic can you review this as well.


add tags to docker builds

Please tag the images on docker hub. That would make it much easier to get reproducible setups. If you don't want to introduce versioning, something simple like timestamp based tags would be sufficient.

I set up tagged builds on Docker Hub, they should automatically trigger.


Update readme

explain how to get correct variable expansion in command using bash -c
Issues

#41
#31

Thanks for your review! It's much better now :blush: very nice :+1:

This was merged with https://github.com/entropitor/dotenv-cli/commit/f987714663e9716cb04c54b7b47c824366ea24d0 (I merged all the commits into one)


Ayaneo Air 1S fan control

Hey! The ayaneo air 1s that I have does not allow manual fan speed settings with oxp-sensors. I built nfbc and used ec_probe to poke at the registers that HandheldCompanion has documented and things work, so. It seems there's a bug in the oxp-sensors kernel module.
for example:
[gamer@chimeraos ~]$ echo 1 | sudo tee /sys/devices/platform/oxp-platform/hwmon/hwmon6/pwm1_enable
1
[gamer@chimeraos ~]$ echo 99 | sudo tee /sys/devices/platform/oxp-platform/hwmon/hwmon6/pwm1
99
tee: /sys/devices/platform/oxp-platform/hwmon/hwmon6/pwm1: Operation not supported

the fan spins up but is frozen at something around 2k rpm and no matter what I try to set pwm1 to fails.
vs
[gamer@chimeraos ~]$ sudo nbfc/pkg/nbfc-linux-git/usr/bin/ec_probe write 0x4a 0x01 #enable manual control
[gamer@chimeraos ~]$ sudo nbfc/pkg/nbfc-linux-git/usr/bin/ec_probe write 0x4b 0x64 #set to 100

I've looked at the driver and its quite intimidating. It seems like someone assumed the 1s worked the same as a pile of other devices and I'm not sure where to start. Is anyone familiar with that driver that would be interested in collaborating on a patch? I'm going to try and get fancontrol working for now.

Can you link here the registers for the air 1S?

Sure! By registers, you want me to dump the EC memory at runtime? Or is there something else?

Or these? https://github.com/Valkirie/HandheldCompanion/blob/main/HandheldCompanion/Devices/AYANEO/AYANEODeviceCEc.cs
(Inheritance: Ayaneo air 1s -> ayaneo air -> CEc)
Mainline driver: https://github.com/torvalds/linux/blob/master/drivers/hwmon/oxp-sensors.c

Ok, so I went on a hunt. I updated my EC and my bios to the latest, didn't fix things. I then compared the mainline kernel oxp_sensors.c to the 6.9/chimeraos version, and there's quite a few differences, but the biggest thing - air 1s doesn't have a pwm set: mainline vs chimera's 6.9 fork - alas, 6.10 through 6.12 have support. chimera's 9.10 fork chimera's 9.12 fork
I guess that means this is a solved case of all releases of v46 don't support the 1s fan. ☹

ok, so I tried unstable, 6.10 kernel, lacks the ability to enable manual fan control, but can disable manual fan control. :(
I tested, manually set the bit for manual control, and I can use oxp-sensors for setting pwm1, so its something.

What register and value did you use to enable it?

same as before [gamer@chimeraos ~]$ sudo nbfc/pkg/nbfc-linux-git/usr/bin/ec_probe write 0x4a 0x01 #enable manual control

Odd that the driver isn't working, that's the same value.

Nvm, I see the issue. Older patch on our 6.10 kernel with a missing entry. Easy fix.

ok, but there's bugs in both drivers. the older kernel can enable manual control but can't set the pwm value, and the new driver cant enable manual but can set the pwm value. ideally 6.10 would be able to both set the pwm value as well as enable manual control.


support dynamic properties from index signature

Currently there is a false positive reported
(smth like ERROR: cannot find 'icon' in type 'RouteConfig')
when the type(class or interface) allows dynamic properties because of index signature syntax:
    export interface RouteConfig {
      route: string | string[];
      [x: string]: any; // dynamic properties can be used with index signature
    }

and You use smth like
${routeConfig.icon}

I'll send a PR shortly


Automated cherry pick of #5705: Add Hairpin traffic limitation doc

Cherry pick of #5705 on release-1.14.
#5705: Add Hairpin traffic limitation doc
For details on the cherry pick process, see the cherry pick requests page.

/skip-all


Fetaure: Deploy as Layer Script

Were you able to get this pushed up as a custom runtime via Lambda layer? I think I'm understanding how that workflow goes to create a custom runtime.
They say that runtimes have a size limit of 250MB but when I run and compile this:
$ du -hs /var/lang
461M    /var/lang

That seems pretty big!
If you were able to get this fully working, mind sharing your zip/deploy script?
Thanks a lot, this is really neat
EDIT:
These guys have a layer deploying version of pypy: https://github.com/iopipe/lambda-runtime-pypy3.5

Thanks, this is a good idea. I'll take a look at it when I have some time.


Improving setup.py for local development

@basepi We should merge this forward to develop branch as well.


add go 1.16 postsub

Issue #, if available:
https://github.com/aws/eks-distro-internal/issues/207
Description of changes:
add go 1.16 post-submit
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


WIP: Event consumer

Or for filtering we can just collect the sources in a HashSet and check if the node has activity:
for (id, node) in self.nodes.iter().filter(|(pk, _)| {
            self.activity
                .iter()
                .map(|a| a.source)
                .collect::<HashSet<PublicKey>>()
                .contains(pk)
        })


MONDO:0014849 autosomal recessive nonsyndromic deafness 105[Merge]

Mondo term (ID and Label)
MONDO:0014849 autosomal recessive nonsyndromic deafness 105
Reason for deprecation
OMIM 616958 has been moved to MIM:608653 ; UMLS CUI C4310777 no longer exists.
Term to be merged with
MONDO:0012091 ,
autosomal recessive nonsyndromic deafness 32
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

Hello @kanems
I'm Sabrina, a new curator who recently joined the Mondo team.
We will address your issue as soon as possible. Thank you for your patience.
If this is a high priority, please let me know and we can prioritize it. Thank you!


Fixing the PR issue

Thanks for fixing the windows part and the optimization on the id
Actually I was stucked at the ioThreadPoolPtr previously.

@ihmc3jn09hk Please recreate this PR and I merged it by mistake.

@ihmc3jn09hk This PR was closed by my mistake, please recreate it again! thx!

Lol, sometimes git is a little bit cocky.
Lets redo it


Tags are not available in galaxy

There are tags which are being made against this project that are not also being made available on galaxy. For instance, this project has the tag v1.0.2 but the highest version made available in galaxy is 0.1.4 which was published 3 years ago. Please make the tags made available in this project also available in galaxy.
https://github.com/ansible-lockdown/RHEL7-CIS/tree/v1.0.2
https://galaxy.ansible.com/mindpointgroup/rhel7-cis

jlosito,
I wanted to give you a heads up that we are working on getting that fixed. I'll close this ticket once things are adjusted.
George

We have figured out the issue and it was related to how we are tagging the versions. We changed the formatting of the version numbers to have the leading "v" which is not supported by galaxy. With that on the first release in May we will address the formatting issue with the versioning. I will close this ticket, please keep an eye out for that first release in May. I'm hoping it will be in early May for this repo.
George


[SPARK-16250][PYSPARK] Can't use escapeQuotes option in DataFrameWriter.csv()

What changes were proposed in this pull request?
This PR corrects DataFrameWriter.csv() to use correct value for the option, escapeQuotes. This is using nullValue for this.
How was this patch tested?
N/A

Test build #61374 has started for PR 13942 at commit 88aefd4.

Test build #61374 has finished for PR 13942 at commit 88aefd4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61374/
Test PASSed.

Fixed in https://github.com/apache/spark/commit/1aad8c6e59c1e8b18a3eaa8ded93ff6ad05d83df


when attempting to start a pod, "range set 0 overlaps with 1"

I've followed kelseyhightower's 'kubernetes the hard way' tutorial and have a k8s 1.12.10 cluster running on ubuntu 18.10 as VM's on a baremetal machine. I am trying to now start a pod and am receiving the following error:
Nov 16 18:49:00 deva-controller0 containerd[347]: time="2018-11-16T18:49:00.792267817Z" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:kubernetes-dashboard-77fd78f978-qb46r,Uid:4e9dc28d-e9cf-11e8-b614-525400d5f439,Namespace:kube-system,Attempt:0,} failed, error" error="failed to setup network for sandbox "4c400bdb0db186bda34d760c4b3bba5aa8d054a45f3bbb1186ef9d4fc00392a7": range set 0 overlaps with 1"
This bubbles up to the kubelet as well and the Pod does not not run as expected.
Steps to reproduce the issue:
1. /mnt/localdump1/kubernetes-deva/bin/kubectl --kubeconfig /mnt/localdump1/kubernetes-deva/admin/admin.kubeconfig apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml
Describe the results you received:
The pod to come up and operate.
Describe the results you expected:
See above error
Output of containerd --version:
$ /bin/containerd --version
containerd github.com/containerd/containerd v1.2.0-rc.0 99fc40fd6088baebe3c18b8f8093cd50d58815d6

@jforman can you post your CNI and IPAM config ? Its possible that the IP ranges might be overlapping.

@abhi
Looking on disk, the config is NOT the one I've deployed via my automated deployment script.
The version on disk in use by containerd:
ubuntu@deva-worker0:~$ cat /etc/cni/net.d/10-bridge.conf
{"bridge":"cnio0","cniVersion":"0.3.1","ipMasq":true,"ipam":{"ranges":[[{"subnet":"<IP_ADDRESS>/24"}]],"routes":[{"dst":"<IP_ADDRESS>/0"}],"subnet":"<IP_ADDRESS>/24","type":"host-local"},"isGateway":true,"name":"bridge","type":"bridge"}

The version I thought I had deployed:
{
"cniVersion": "0.3.1",
"name": "bridge",
"type": "bridge",
"bridge": "cnio0",
"isGateway": true,
"ipMasq": true,
"ipam": {
"type": "host-local",
"ranges": [
[{"subnet": "<IP_ADDRESS>/24"}]
],
"routes": [{"dst": "<IP_ADDRESS>/0"}]
}
}
Note the duplicate subnet specification in the initial version. Is containerd doing some on-disk rewriting of my config?

Note the duplicate subnet specification in the initial version. Is containerd doing some on-disk rewriting of my config?

No, containerd doesn't do that. Containerd doesn't generate cni config, it only watches and load the config.
The only case that containerd may write a cni config itself is when you set plugins.cri.cni.conf_template in /etc/containerd/config.toml, but it doesn't seem to be your case.
This is most likely a problem in your cni config deployment tool.

I can't explain it, but magically things work now. I blew away the cluster and rebuilt it, and redeployed k8s using my deployment script (https://github.com/jforman/kubify) and all is good now. I want to dig into why....But for now, sorry for the noise!

Seems this issue is back. I had to reboot the host containing my k8s VMs (ubuntu cloud images) and now some of the nodes are exhibiting the below behavior, and some aren't. The downstream effect of this is that no pods can start on those nodes. Status shows up as 'unknown'.
Nov 21 13:52:41 deva-controller0 containerd[318]: time="2018-11-21T13:52:41.905343973Z" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:nginx-ingress-release-controller-7f795769bf-g8tsp,Uid:ce54465c-eb9d-11e8-83b4-525400f57ed2,Namespace:default,Attempt:2,} failed, error" error="failed to setup network for sandbox "b004cb4583738bc992fdd3b00021a8dd408dd85c375e4edd5a747580da6f126a": range set 0 overlaps with 1"
For completeness sake, my CNI configs:
ubuntu@deva-controller0:~$ ls /etc/cni/net.d/
10-bridge.conf  99-loopback.conf

ubuntu@deva-controller0:~$ cat /etc/cni/net.d/10-bridge.conf
{"bridge":"cnio0","cniVersion":"0.3.1","ipMasq":true,"ipam":{"ranges":[[{"subnet":"<IP_ADDRESS>/24"}]],"routes":[{"dst":"<IP_ADDRESS>/0"}],"subnet":"<IP_ADDRESS>/24","type":"host-local"},"isGateway":true,"name":"bridge","type":"bridge"}

ubuntu@deva-controller0:~$ cat /etc/cni/net.d/99-loopback.conf
{
    "cniVersion": "0.3.1",
    "type": "loopback"
}

Any help debugging this is greatly appreciated.

Is this a controller node or a worker node? Each worker node, where the pods will be run, should have a different pod CIDR range. ks the hard way shows setting up the control plane for high availability.

Hi @mikebrow , both controller and worker nodes seem to exhibit the behavior. Note that not ALL of the nodes of each type exhibit it, but only some. To answer your question, I am running pods on both the controller and worker nodes, though I have a taint on the controller nodes that only some pods (kube-router for example) will schedule and run on there.
In terms of having pod CIDRs for each node, each node does:
kubectl get nodes -o json | jq '.items[] | .metadata.name,.spec.podCIDR'
"deva-controller0.obfuscated.localdomain"
"<IP_ADDRESS>/24"
"deva-controller1.obfuscated.localdomain"
"<IP_ADDRESS>/24"
"deva-controller2.obfuscated.localdomain"
"<IP_ADDRESS>/24"
"deva-worker0.obfuscated.localdomain"
"<IP_ADDRESS>/24"
"deva-worker1.obfuscated.localdomain"
"<IP_ADDRESS>/24"
"deva-worker2.obfuscated.localdomain"
"<IP_ADDRESS>/24"

Showing pod status, where some pods schedule on some of each node type.
$ kubectl get pods -o wide --all-namespaces
NAMESPACE     NAME                                                    READY   STATUS              RESTARTS   AGE     IP            NODE                                               NOMINATED NODE
default       binder-5d66bbbb59-c48wc                                 1/1     Running             1          3d20h   <IP_ADDRESS>   deva-worker1.obfuscated.localdomain       <none>
default       cert-manager-release-594486447f-ns7fl                   0/1     Unknown             1          46h     <none>        deva-worker0.obfuscated.localdomain       <none>
default       grafana-release-5b4d8774db-d6xkq                        0/1     ContainerCreating   0          17h     <none>        deva-worker0.obfuscated.localdomain       <none>
default       grafana-release-64757cc89b-hpkkg                        1/1     Running             1          22h     <IP_ADDRESS>   deva-worker1.obfuscated.localdomain       <none>
default       grafana-release-64757cc89b-mbr69                        1/1     Running             3          22h     <IP_ADDRESS>   deva-worker2.obfuscated.localdomain       <none>
default       nginx-ingress-release-controller-7f795769bf-g8tsp       0/1     Unknown             1          2d17h   <none>        deva-controller0.obfuscated.localdomain   <none>
default       nginx-ingress-release-controller-7f795769bf-r6b27       0/1     Unknown             1          2d17h   <none>        deva-controller1.obfuscated.localdomain   <none>
default       nginx-ingress-release-default-backend-8597454bc-lfdtj   1/1     Running             1          2d17h   <IP_ADDRESS>   deva-worker1.obfuscated.localdomain       <none>
kube-system   coredns-5d5db6c9c-k57kl                                 1/1     Running             1          4d17h   <IP_ADDRESS>   deva-worker1.obfuscated.localdomain       <none>
kube-system   coredns-5d5db6c9c-sfkrc                                 0/1     Unknown             1          4d17h   <none>        deva-controller1.obfuscated.localdomain   <none>
kube-system   kube-router-9h7zp                                       1/1     Running             5          4d18h   <IP_ADDRESS>   deva-worker0.obfuscated.localdomain       <none>
kube-system   kube-router-j9ztq                                       1/1     Running             3          4d18h   <IP_ADDRESS>   deva-controller1.obfuscated.localdomain   <none>
kube-system   kube-router-np7dz                                       1/1     Running             1          4d18h   <IP_ADDRESS>   deva-worker1.obfuscated.localdomain       <none>
kube-system   kube-router-npzpw                                       1/1     Running             1          4d18h   <IP_ADDRESS>   deva-worker2.obfuscated.localdomain       <none>
kube-system   kube-router-nwl2q                                       1/1     Running             2          4d18h   <IP_ADDRESS>   deva-controller2.obfuscated.localdomain   <none>
kube-system   kube-router-w7kzp                                       1/1     Running             3          4d18h   <IP_ADDRESS>   deva-controller0.obfuscated.localdomain   <none>
kube-system   kubernetes-dashboard-77fd78f978-58mzp                   0/1     Unknown             1          4d17h   <none>        deva-worker0.obfuscated.localdomain       <none>
kube-system   tiller-deploy-6f6fd74b68-bvl2b                          1/1     Running             1          3d18h   <IP_ADDRESS>   deva-worker2.obfuscated.localdomain       <none>

@jforman Can you go to one of the bad node, and run crictl info? The cni setting there will be useful.
And the range set 0 overlaps with 1 error comes from CNI IPAM plugin https://github.com/containernetworking/plugins/blob/696b1f9ab1022c34e1514e0e29bf84bb9179899f/plugins/ipam/host-local/backend/allocator/config.go#L151.
Somehow, your containerd seems to be using a different cni config. Does restart containerd fix the issue?

Well this is obviously not good (though I will say, I ran that same command on another node and it also returned the same error).
FATA[0010] failed to connect: failed to connect: context deadline exceeded
root@deva-controller1:~# crictl info
NAME:
   crictl info - Display information of the container runtime

USAGE:
   crictl info [command options] [arguments...]

OPTIONS:
   --output value, -o value  Output format, One of: json|yaml (default: "json")

FATA[0010] failed to connect: failed to connect: context deadline exceeded

I restarted containerd on one of the affected nodes (deva-controller1) , but that does not seem to resolve the issue.

@jforman You need "sudo".

@Random-Liu I dont have a /etc/crictl.yaml.
The only configuration I have is a config.toml, referenced as the value to the --config param to /bin/containerd
root@deva-controller1:~# cat /opt/kubernetes/conf/config.toml
[plugins]
  [plugins.cri.containerd]
    snapshotter = "overlayfs"
    [plugins.cri.containerd.default_runtime]
      runtime_type = "io.containerd.runtime.v1.linux"
      runtime_engine = "/usr/local/bin/runc"
      runtime_root = ""
    [plugins.cri.containerd.untrusted_workload_runtime]
      runtime_type = "io.containerd.runtime.v1.linux"
      runtime_engine = "/usr/local/bin/runsc"
      runtime_root = "/run/containerd/runsc"
    [plugins.cri.containerd.gvisor]
      runtime_type = "io.containerd.runtime.v1.linux"
      runtime_engine = "/usr/local/bin/runsc"
      runtime_root = "/run/containerd/runsc"
root@deva-controller1:~#

This is interesting, even though the containerd.sock exists, there is no output with your command:
root@deva-controller1:/var/run/containerd# ls
containerd.sock  io.containerd.grpc.v1.cri  io.containerd.runtime.v1.linux  io.containerd.runtime.v2.task  runc
root@deva-controller1:/var/run/containerd# crictl config runtime-endpoint unix:///var/run/containerd/containerd.sock
root@deva-controller1:/var/run/containerd#

crictl config runtime-endpoint unix:///var/run/containerd/containerd.sock is only to configure the endpoint. Now you should have /etc/crictl.yaml correctly configured, and sudo crictl info should work.

Your CNI config is wrong. Remove "ranges":[[{"subnet":"<IP_ADDRESS>/24"}]], and it will work.
Where did you get the CNI config?
Look at this line, the subnet field and ranges field are merged, and then check overlap.
In you config, both ranges and subnet have the same subnet "<IP_ADDRESS>/24", so eventually the ranges become: [[{RangeStart:<IP_ADDRESS> RangeEnd:<IP_ADDRESS> Subnet:{IP:<IP_ADDRESS> Mask:ffffff00} Gateway:<IP_ADDRESS>}] [{RangeStart:<IP_ADDRESS> RangeEnd:<IP_ADDRESS> Subnet:{IP:<IP_ADDRESS> Mask:ffffff00} Gateway:<IP_ADDRESS>}]]
And of course there is an overlap.

he probably got the cni config from here:
https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/09-bootstrapping-kubernetes-workers.md#configure-cni-networking

he probably got the cni config from here:
https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/09-bootstrapping-kubernetes-workers.md#configure-cni-networking

That one is correct. :)

silly unformatted I missed that subnet with the same CIDR was used twice...
{"bridge":"cnio0",
"cniVersion":"0.3.1",
"ipMasq":true,
"ipam":{
  "ranges":[[{"subnet":"<IP_ADDRESS>/24"}]],
  "routes":[{"dst":"<IP_ADDRESS>/0"}],
  "subnet":"<IP_ADDRESS>/24",
  "type":"host-local"
},
"isGateway":true,"name":"bridge","type":"bridge"}

there should be a tool to create these cni configs

@Random-Liu I wrote the deployment tool myself (essentially a python wrapper around kelsey's steps):
Step that rsync's my locally generated file: https://github.com/jforman/kubify/blob/master/kubify.py#L1051
Which is just an rsync of the file I pasted above to /etc/cni/net.d/10-bridge.conf

random thought here did you update to a new docker on these broken machines.. wondering if they might be overlaying cni config when they package install containerd.io along with the docker install package.

If any package got installed/upgraded, it was automatic (as part of some cron job) and not anything I did purposely. I'm going to dig into this more, and see if I can find anything consistent that about those broken machines.

docker version 18.09.0 includes containerd.io package.. is the only thing I can think of that might be messing around with the CNI config..

For completeness, and curiosity's sake, I updated my CNI bridge config to match the 0.3.1 spec (https://github.com/containernetworking/cni/blob/spec-v0.3.1/SPEC.md) as opposed to what was mentioned in kelsey's hard way doc, and containerd now seems happy with it. A redeploy of the following config (with cidr's changed per node), and a restart of the node now shows all the pods Running!
For those who happen to come across this issue, the below config (with unique CIDR per node) works:
ubuntu@deva-controller1:~$ cat /etc/cni/net.d/10-bridge.conf
{
    "cniVersion": "0.3.1",
    "name": "bridge",
    "type": "bridge",
    "bridge": "cnio0",
    "isGateway": true,
    "ipMasq": true,
    "ipam": {
        "type": "host-local",
        "subnet": "<IP_ADDRESS>/24",
        "routes": [{"dst": "<IP_ADDRESS>/0"}]
    }
}


Missing documentation "Connect to your Azure DevOps Services TFVC Repository"

Title is self explanatory - You are missing documentation "Connect to your Azure DevOps Services TFVC Repository".

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

ID: e818c26d-b8fd-e532-95af-7f5654acf7e2
Version Independent ID: d837a5c4-4634-dac2-79e8-c5aa15deaaed
Content: VS Code extension for Java development with Azure DevOps Services
Content Source: docs/java/vscode-extension.md
Product: devops
Technology: devops-cicd
GitHub Login: @DavidStaheli
Microsoft Alias: dastahel

Thanks for reporting this James.  We have insufficient bandwidth to address this for TFVC.


(docs) Remove references to ADS

This is now defunct terminology and should now be referred to as "OSM controller"

ADS reference in design doc: https://github.com/openservicemesh/osm/blob/main/DESIGN.md#aggregated-discovery-service

The appearances of ADS in in the DESIGN doc refer to the aggregated discovery service, which is valid in these cases.


Confusing instructions

[Enter feedback here]
On one page we are told that it important to create a snapshot report before a continuous report and then at the bottom of the https://docs.microsoft.com/en-us/cloud-app-security/discovery-docker page we are told that the next step is to create a snapshot report, this puts us into a loop.
Please clarify the sequential steps
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 83e0555c-41e5-0ba3-4c4b-f9c386644a72
Version Independent ID: 876888bc-8046-0a25-a0b7-67f938cc45c1
Content: Configure automatic log upload for continuous reports in Cloud App Security
Content Source: CloudAppSecurityDocs/discovery-docker.md
Service: cloud-app-security
Product: ****
Technology: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@DeanGross Thanks for your feedback. Please can you provide a little more detail on the issue you raised? Which topic tells you that it is important to create a snapshot report before a continuous report? Thanks

this is the page i was referring to https://docs.microsoft.com/en-us/cloud-app-security/create-snapshot-cloud-discovery-reports

@DeanGross Thanks for the additional information. We've submitted a documentation change to remove the next step in this article based on your suggestion, and the updated article should be live by tomorrow. Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.


Incorrect Types Generated by Sanity TypeGen

Describe the bug
Using sanity-typegen to create GROQ query types results in wrong types.
To Reproduce
Steps to reproduce the behavior:

Add the plugin, create and use it in a field.
Query the field:

  const videoBlockQ = groq`*[_type == "blockVideo" && _id == $blockId][0]{
    _id,
    _type,
    title,
    video{
      asset->{
        playbackId,
        assetId,
        filename,
      }
    }
  }`;

Run typegen:

// Query: *[_type == "blockVideo" && _id == $blockId][0]{    _id,    _type,    title,    video{      asset->{        playbackId,        assetId,        filename,      }    }  }
export type VideoBlockQResult = {
  _id: string;
  _type: "blockVideo";
  title: string | undefined;
  video: {
    asset: null;
  } | undefined;
} | undefined;

Expected behavior
VideoBlockQResult["video"]["asset"] should be of type Partial<MuxVideoAsset> | undefined
Which versions of Sanity are you using?
Run sanity versions in the terminal and copy-paste the result here.
@sanity/cli (global)  3.46.1 (up to date)
@sanity/image-url      1.0.2 (up to date)
sanity                3.46.1 (up to date)

What operating system are you using?
Linux 6.9.4-arch1-1

Which versions of Node.js / npm are you running?
20.9.0

@r0skar can you still reproduce this with the latest version of sanity?

@sgulseth Not the OP but I'm still experiencing this on the latest version (3.57.0).

Still happening as of Sanity 3.62.3

Thanks for the update, and sorry the delay here. I think this is because of a conflicting type name when we serialize the type names to be compatible as a TS identifier.


Weird multi-byte character breaking UTF-8-aware script

src/unix/android-ifaddrs.c contained a weird character in its header comment. I don't know if this is valid UTF-8 or not, but this python tool could not process it otherwise (despite being unicode-ready).

LGTM, can you please reword the commit to say something like "src: remove non ascii character"
FWIW, the script is not really unicode ready. It should use codecs.open instead of open, which will try to decode anything it finds with ascii.

Sure. Also, you are right about the script, it's not very robust.

Landed in b4126dd, thanks!


Did NCNN version impact the result?

I build the latest ncnn on win10, and run extract the cpu-forward code from this github.
But when I try to test it with the two images from this github, the results is very strange, and evey time the results is different.
Init code is just as

the forward code is just the process_cpu part. But the result is not right. The only different thing is the ncnn version.

So, can you give me a help?

I had tried rife-HD and rife-anime model, all can't get the right result.

I run the nanodet with the same ncnn.lib+ncnn.dll, the result is right.

I think I have the same problem. When I change the ncnn code to latest version code in github, the result is not correct (black image). My enviorment is gpu and change code to this github version, the result is corret. I don't know if this problem is the same as yours. So, have you solved this problem already?


perf: extend the overflow detection mask to the right if the bump increment is a power of 2

Trying out the idea in https://github.com/dfinity/motoko/pull/4064/files/4eb3dfeb7fdc10737605c631edff33b3f0976eff#r1250740318.
TLDR: The page-crossing detection mask can be extended for power-of-2 increments by one bit (to the right) which allows for accurate detection of not only HP remaining on-page, but also page boundary crossings. This enables the property that the slow path gets entered only when necessary.
Alas, it is flawed... with a HP that can point exactly to the boundary between pages.
With #4095 merged this cannot happen. Let's prove it with pen and paper...
Assume the allocation increment is N = 8, the smallest possible (byte-)increment that is a power of 2 when allocating objects. In hex N = 0x0008, thus the unextended overflow mask is M = 0xFFF0, and we assume that such a mask guarantees (by #4095) the implication (HP + N) & M > 0 => "i8.store (HP + N) x" won't crash for all HP of the form 0bXX..X11. In this PR we have to strengthen the implication to the extended mask M' = M | N, i.e. one bit to the right. We proceed as follows:
We only need to consider the case where (HP + N) & M = 0, otherwise we are done by the above assumption. This reduces

(HP + N) & M' > 0 => "i8.store (HP + N) x" won't crash
via (HP + N) & (M | N) > 0 => "i8.store (HP + N) x" won't crash
to (HP + N) & (M | N) = N => "i8.store (HP + N) x" won't crash

so the bit under the submask N must be set and under M no bit is set. This gives us a good picture of HP + N, namely 0bPPP..P0000000000001X11 where the 16 P bits are irrelevant and X can be 0 or 1. This also means that HP must have been N less: 0bPPP..P0000000000000X11. Since HP was the result of a previous increment, and thus "i8.store HP x" doesn't crash, writing a byte to 0bPPP..P0000000000001X11 won't crash either (since it is on the same page). This finishes the implication.
Choosing a different N — that is a power of 2 and < 0x8000 — will result in a similar proof, only that there are more X bits.

A the tests reveal, there is a gap here. Whan the HP is at page boundary before and we add a power-of-two, then we technically didn't change pages, but the page wasn't allocated yet in first place. So this experiment has failed, and has shown that the simple things are often the more correct ones! Closing. @luc-blaeser

Reopening to test the combination with #4095! Worth a try...

Okay, let me fool around a bit...
import Data.List
import Data.Bits

split b | a <- b .&. 1, b' <- b `shiftR` 1, b' /= 0 = Just (head $ show a, b')
split b | 1 <- b .&. 1 = Just ('1', 0)
split _ = Nothing

bin = reverse . unfoldr split

Consider increments that are single isle, like 48 (= 0b11_000).


Directory already watched (listen error)

I'm getting errors like this from guard/listen.
** ERROR: directory is already being watched! **

Directory: /Users/my-user/website/tmp/source_map_concat-output_path-zglQTS89.tmp/js

is already being watched through: /Users/my-user/website/tmp/source_map_concat-output_path-zglQTS89.tmp/js

MORE INFO: https://github.com/guard/listen/wiki/Duplicate-directory-errors
** ERROR: directory is already being watched! **

Directory: /Users/my-user/website/node_modules/broccoli-babel-transpiler/node_modules/babel-core

is already being watched through: /Users/my-user/website/node_modules/broccoli-babel-transpiler/node_modules/babel-core

MORE INFO: https://github.com/guard/listen/wiki/Duplicate-directory-errors

My guess would have been that either of these two lines should prevent it:

https://github.com/middleman/middleman/blob/604c0e2b5d2c17a4fee85f8fd80d62cacd1f1652/middleman-core/lib/middleman-core/sources/source_watcher.rb#L179
https://github.com/middleman/middleman/blob/604c0e2b5d2c17a4fee85f8fd80d62cacd1f1652/middleman-core/lib/middleman-core/sources/source_watcher.rb#L53

Out of curiosity, should those two lines be merged into a single list of ignored directories? They differ slightly.
Any thoughts on what may cause this?
Additional information

Ruby version: 2.3.1
Middleman version: 4.1.11
OS version: macOS 10.11.6 (El Capitan)

I'm getting the exact same error.
== The Middleman is loading
        ** ERROR: directory is already being watched! **

        Directory: /home/my_user/website/source/assets/fonts/font-awesome

        is already being watched through: /home/my_user/website/node_modules/font-awesome/fonts

        MORE INFO: https://github.com/guard/listen/wiki/Duplicate-directory-errors
== View your site at "http://localhost:4567", "http://<IP_ADDRESS>:4567"

Things to know in my case, I created a symbolic link from node_modules/font-awesome/fonts  to source/assets/fonts/font-awesome. Is there a way to prevent this error or a better way to do so?
Stack

Ruby version: 2.3.3
Middleman version: 4.2.0
OS version: GNU/Linux Ubuntu 16.04

Up ☝

I'm getting this error too, but it's complaining about the .pnp directory created by Yarn's PnP mode.

I suspect this is always because of symlinks?

This is the ignored list:
https://github.com/middleman/middleman/blob/186bfb9c266b0ffd3f0824a33c614fe9afd3cf5e/middleman-core/lib/middleman-core/sources/source_watcher.rb#L53


ENH: Added analytical formula for dgamma distribution entropy (#17748)

Reference issue

What does this implement/fix?

Additional information

What is the reference for this formula? Should be added as a comment in the code or at least be mentioned here for future maintenance.

What is the reference for this formula? Should be added as a comment in the code or at least be mentioned here for future maintenance.

I had to derive the formula myself. Sadly, there doesn't seem to many good references for any entropy formulas, but it's not terribly hard to verify that the formula is correct.

What is the reference for this formula? Should be added as a comment in the code or at least be mentioned here for future maintenance.

I had to derive the formula myself. Sadly, there doesn't seem to many good references for any entropy formulas, but it's not terribly hard to verify that the formula is correct.

The test against the numerical integration seems to disagree though at the moment:
https://dev.azure.com/scipy-org/SciPy/_build/results?buildId=22918&view=logs&j=7902a2c1-7b88-5b2d-6408-84b88759c642&t=5471a576-12f4-5533-4de4-506800a17112&l=852

These tests run only with additional arguments. To test locally, do
export SCIPY_XSLOW=1
python dev.py -t [yourtest] -m full

Good catch, @dschmitz89. I looked it over, and found that I incorrectly integrated from 0 to infinity, when I should have integrated from -infinity to infinity. Error has been fixed.

What is the reference for this formula? Should be added as a comment in the code or at least be mentioned here for future maintenance.

I had to derive the formula myself. Sadly, there doesn't seem to many good references for any entropy formulas, but it's not terribly hard to verify that the formula is correct.

Could you do provide a rough derivation how you solved that integral here (github markdown supports LateX for a few months now) or upload a PDF with it?

What is the reference for this formula? Should be added as a comment in the code or at least be mentioned here for future maintenance.

I had to derive the formula myself. Sadly, there doesn't seem to many good references for any entropy formulas, but it's not terribly hard to verify that the formula is correct.

Could you do provide a rough derivation how you solved that integral here (github markdown supports LateX for a few months now) or upload a PDF with it?
Dgamma_entropy_derivation.pdf

This implementation is definitely an improvement in terms of speed and accuracy.
Small a

import numpy as np
import matplotlib.pyplot as plt
from mpmath import mp
from scipy import stats
from scipy import special as sc
def entropy_dgamma(a):
return a + np.log(2) + sc.gammaln(a) + (1 - a) * sc.digamma(a)
@np.vectorize
def entropy_dgamma_mpmath(a):
a = mp.mpf(a)
return a + mp.log(2) + mp.loggamma(a) + (1 - a) * mp.digamma(a)
x = np.logspace(5, 15, 100)
plt.semilogx(x, np.asarray(entropy_dgamma_mpmath(x), dtype=np.float64), label="mpmath", ls="dashed")
plt.semilogx(x, entropy_dgamma(x), label="custom", ls="dotted")
#plt.semilogx(x, stats.dgamma.entropy(x), label="main", ls="dashdot")
plt.legend()

Large a
Here, the main branch results in an error (already for ca. a>100) due to intermediate overflow. With this instead we get reasonable values untilt 1e12:

I say, as for #17868 : let's add test cases for 1e-4 and 1e6 and then merge.

let's add test cases for 1e-4 and 1e6 and then merge.

I prefer to add more test cases, since there can be failures in between these 2 values, even if both pass.

Using the asymptotic formulas from https://github.com/scipy/scipy/pull/17868#issuecomment-1416919700 it is possible to get it right for $a>1e12$ (thanks @steppi !):
$$
\begin{align}
\ln(\Gamma(a)) & \sim (a -\frac{1}{2})\ln a - a + \frac{1}{2}\ln(2\pi) & \
\psi(a) & \sim \ln a - \frac{1}{2a}  \
h & = \ln 2 + \ln(\Gamma(a)) + a + (1 -a)\psi(a) \
& \sim \ln 2 + (a -\frac{1}{2})\ln a - a + \frac{1}{2}\ln(2\pi) + a + (1-a)(\ln a - \frac{1}{2a}) \
& = \ln 2 + \frac{1}{2}(1+\ln a + \ln(2\pi))
\end{align}
$$

import numpy as np
import matplotlib.pyplot as plt
from mpmath import mp
from scipy import stats
from scipy import special as sc
def entropy_dgamma(a):
return np.where(a < 1e12,
sc.gammaln(a) + a + np.log(2) + (1 - a) * sc.digamma(a),
np.log(2) + 0.5 * (1. + np.log(a) + np.log(2*np.pi))
)
@np.vectorize
def entropy_dgamma_mpmath(a):
a = mp.mpf(a)
return a + mp.log(2) + mp.loggamma(a) + (1 - a) * mp.digamma(a)
x = np.logspace(11, 14, 1000)
plt.semilogx(x, np.asarray(entropy_dgamma_mpmath(x), dtype=np.float64), label="mpmath", ls="dashed")
plt.semilogx(x, entropy_dgamma(x), label="custom", ls="solid")
plt.legend()
plt.show()

@MatteoRaso : would you prefer to leave this for a follow-up PR? I leave it up to you, does not have to hold up this PR.

The Dgamma test class from in the main branch is not merged into this branch yet. When that is done, we can have a look at that last lint error. :)

The Dgamma test class from in the main branch is not merged into this branch yet.

For some reason, when I try to merge main branch into my local copy of this branch, it causes a whole bunch of errors. Is it necessary to merge the main branch into this one, though? I could be wrong, but I feel like it should be possible to merge this branch without needing to worry about that.

When that is done, we can have a look at that last lint error. :)

I ran python dev.py lint and python runtests.py --pep8, but nothing came up for _continuous_distns.py or the test file. It's possible that the lint error is actually the linter being weird again.

I ran python dev.py lint and python runtests.py --pep8, but nothing came up for _continuous_distns.py or the test file. It's possible that the lint error is actually the linter being weird again.

There have been a lot of changes to the lint infrastructure lately; unless you have merged main in recently it is likely that the check you are running locally is different to what is running on the CI job.

The Dgamma test class from in the main branch is not merged into this branch yet.

For some reason, when I try to merge main branch into my local copy of this branch, it causes a whole bunch of errors. Is it necessary to merge the main branch into this one, though? I could be wrong, but I feel like it should be possible to merge this branch without needing to worry about that.

When that is done, we can have a look at that last lint error. :)

I ran python dev.py lint and python runtests.py --pep8, but nothing came up for _continuous_distns.py or the test file. It's possible that the lint error is actually the linter being weird again.

For the reasons @j-bowhay mentioned, merging main into this branch can become quite messy probably. I do not think we can come around that unfortunately though.

Ok, I've removed the pep8 errors that slipped under the linter and all tests pass. @dschmitz89 @mdhaber does this look good to merge?

@dschmitz89 Please note that the bigger issue here is that import mpmath as mp needs to be from mpmath import mp. Please see https://github.com/scipy/scipy/pull/17874#discussion_r1105067620, mpmath/mpmath#657.

Also, IIUC, the intent of using mp.one is to ensure that quantities that cannot be represented exactly in double precision are not truncated to double precision prematurely; i.e. mp.one/3 or mp.mpf('1/3') would be preferred over 1/3. It is a good thing to watch out for, but I don't think they make a difference here because the quantities they operate against are already mpfs.
@dschmitz89 I'll review/merge this when it looks good to you.

@dschmitz89 I've made the changes that you requested. Does this look ready to merge?

I performed a more thorough error analysis following the discussion in #17930 . Let's change the threshold between regular formula and asymptotic formula to 1e8. A relative error of 1e-9 is not good but should not hold up this PR in my opinion. Follow up could be to check if using more terms in the asymptotic expansion improve the result but I doubt it (did not work for the chi distribution).

Generate the above plot
import numpy as np
import matplotlib.pyplot as plt
from scipy import stats
from scipy import special as sc
from mpmath import mp

mp.dps = 500

def dgamma_entropy(a):
    return a + sc.gammaln(a) + np.log(2) + (1 - a) * sc.digamma(a)

def asymptotic(a):
    return np.log(2) + 0.5 * (1 + np.log(a) + np.log(2 * np.pi))

@np.vectorize
def dgamma_entropy_mpmath(a):
    a = mp.mpf(a)
    two = mp.mpf(2.)
    x_1 = a + mp.log(two) + mp.loggamma(a)
    x_2 = (mp.one - a) * mp.digamma(a)
    h = x_1 + x_2
    return float(h)

x = np.logspace(2, 15, 1000)
reference = np.array(dgamma_entropy_mpmath(x), np.float64)
asymptotic_res = asymptotic(x)
regular_res = dgamma_entropy(x)

plt.loglog(x, np.abs((regular_res - reference)/reference), label="regular", ls='dashed')
plt.loglog(x, np.abs((asymptotic_res - reference)/reference), label="asymptotic", ls='dotted')
plt.axvline(1e8, 0, 1, c='k', label="Threshold")
plt.title("Relative error: dgamma entropy")
plt.legend()
plt.show()

@steppi thanks for your review. Feel free to merge when it looks good to you.


Error on implementation

Hi,
I'm trying to implement your d3-funnel library, but I'm getting "Unexpected token =>" message from the browser for line 1 of the d3-funnel.js file.
I've tried several things already:

Changing order or loading
Changing Jquery version
Removing all other JS from the page

Any ideas what I'm doing wrong?
Wouter

Are you using the /src/d3-funnel.js file? This will not work in most browsers, as it contains ES6 JavaScript. The compiled version to use is /dist/d3-funnel.js.

Yeah, you're right! Thanks!


Invalid response from server for collection live data of windturbine

Checklist

[X] I'm running the latest version of the Windcentrale integration.
[X] I checked if there is not a duplicate issue with the same question.
[X] I have read the README.md page.
[X] This issue is a bug related to the Windcentrale integration.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] I have filled out the issue template to the best of my ability.

The problem
Since two days the live data is no longer updated. My logs are flooded with the following:
What is version of Home Assistant Core did you recieve the bug?
core-2022.4.7
What is version of Home Assistant Supervisor did you recieve the bug?
supervisor-2022.05.0
What is version of Home Assistant Supervisor?
Home Assistant OS 7.6
What is version of the Windcentrale integration?
0.1.4
Example Code snippet
No response
Anything in the logs that might be useful for us?
2022-05-04 12:44:42 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Blauwe Reiger
2022-05-04 12:44:42 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Ranke Zwaan
2022-05-04 12:44:42 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Jonge Held
2022-05-04 12:44:49 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection production data of windturbine De Jonge Held
2022-05-04 12:44:49 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection production data of windturbine De Ranke Zwaan
2022-05-04 12:44:49 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection production data of windturbine De Blauwe Reiger
2022-05-04 12:44:53 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Ranke Zwaan
2022-05-04 12:44:53 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Blauwe Reiger
2022-05-04 12:44:53 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Jonge Held
2022-05-04 12:45:03 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Jonge Held
2022-05-04 12:45:03 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Ranke Zwaan
2022-05-04 12:45:03 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Blauwe Reiger
2022-05-04 12:45:13 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Blauwe Reiger
2022-05-04 12:45:13 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Ranke Zwaan
2022-05-04 12:45:13 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Jonge Held
2022-05-04 12:45:23 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Blauwe Reiger
2022-05-04 12:45:23 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Ranke Zwaan
2022-05-04 12:45:23 ERROR (MainThread) [custom_components.windcentrale.wind] Invalid response from server for collection live data of windturbine De Jonge Held
Additional information
No response

Of course it's very possible the cause is at the Windcentrale's end, but I wouldn't know how to debug this.

When I check the API's for both login and data retrieval, they both give a 503 error. Logging in via the site is also currently unavailable.
I will try to contact the company and ask what the situation is and if the current system is out of order or if there is a new system coming.

I wouldn't be surprised if it is caused by the Windcentrale itself, and also if its correlated with my posted issue: they are working on ( as they call it) a new frontend and I wouldn't be surprised if the api used is end of life.

Indeed they create a new platform https://mijn.windcentrale.nl/. I'm going to try to read the data from this. But this is probably going to take some time as it is a brand new platform with new APIs.

Thanks for the effort Job! I'll buy you a beer if you succeed! :)

For now I can only find this screen with little data. Also in the APIs that are used for this there is not much data.

If anyone can find a screen with more data I'd really appreciate it. I will keep an eye on the site in the near future and hope that more data will become available.

PS: I do have some values again in HA for the moment

S: I do have some values again in HA for the moment

It looks like it's working for now. But I'm still going to look at the new platform because they will switch at some point.

Looks like they are working on it

I'm going to close this issue for now. I have created a new issue #26 for the new platform.

@bliekp The problem is solved in the new version 0.2.x


chore(deps): bump vitest to 1.0.1

Summary
bump vitest to 1.0.1
Related Links

Checklist

[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

👍


Add attribute to limit dragging within a container

This attribute limits the movement within a DOM element. Included test case (try to drag letters M-R to the right/left extremes of the page).
On an unrelated note, the vertical position of the page seems to be wrong. If the page has a non-zero scroll position (i.e: set a really tall chrome console and scroll the page contents down) the drop behavior gets broken.

Thanks a lot for your contribution. I will take a closer look at the scrolling issue too.


helm: tags and versions

(1) Currently, the helm releases create tags named with leading reana-... text:
$ git tag -l
reana-0.7.0-dev20200407
reana-0.7.0-dev20200416
reana-0.7.0-dev20200417

This is not pretty. We should use v0.7.0-... as the tag name, which would give 0.7.0-... as the semver number. See semver FAQ.
Example: Kubernetes project uses leading v for tags, e.g. v1.18.0.
Example: Go uses leading go for tags, e.g. go1.14.3.
(2) Currently, the helm versions such as 0.7.0-dev20200527 are nicely semver-compliant.  However, the usual practice for semver releases is to use dot-separated pre-release identifiers, going like 2.0.0-alpha.1, 2.0.0-alpha.2, etc.  We don't use dot separation, and while our YYYYMMDD numbering is nice, it may not be future-proof for multiple builds in a given day.
Hence some RFCs:

Shall we go for -dev.20200527 as well, including dot?

Since we may be releasing more often than once per day, shall we go far -dev.20200527+build111023 or -dev.20200527.git.0460f28 where the later part could indicate either hh:mm:ss hour or sha1 information? (only from official repos in the latter case)

Since the connection to Python versioning (0.7.0.dev20200224) is a bit broken anyway due to dots/dashes, and since we may be having non-Python components in the future, shall we go for the classical alpha.N where N would be simply auto-incremented, loosing the date information and relying on chart overview to inform about dates?

Example: Kubernetes uses classical alpha/beta/rc denomination, e.g. v1.19.0-alpha.1.
(3) It may be good to look at future-proofing versioning, e.g. regarding Helm Hub. It seems Helm Hub supports semver2, but I have not looked at prevalent common style regarding alpha/beta/rc or dev.

A related issue:
(4) Docker image versioning using git-latest-tag-plus-commits, leading to image numbers such as 0.6.0-31-g35c4fc8 for version such as 0.7.0-dev20200527.  This does not seem coherent, since one is based on past tag and one is based on future tag, as it were. Perhaps we should harmonise this at the same time?

Another consideration: we could abandon YYYYMMDD style and switch Python versions into using 0.7.0a1 style, which would play more nicely with 0.7.0-alpha.1 semver style for Helm releases. And we could use the same base for Docker images released on Docker Hub, followed by sha1. This might give the most coherent (pypi, docker hub, npm, helm) release numbering wherever we may be releasing.

The RFC was agreed and the details were ticketised in #370 and associated r-dev tickets where things will be implemented. I'm therefore closing this RFC.


ML module milestones

Detailed milestones for Issue #285

Note: Decisions taken during community bonding period

Milestone 1

[x] Create UI of model management dashboard

[ ] Add logic to open editor after creating new empty model in database

[ ] Create basic layout for the ML module UI
[ ] Create Redux store structure for the model
[ ] Create Mongoose schema for model
[ ] Create actions and reducers to allow editing of model details in Redux store
[ ] Create module to add training class to the model

[ ] Create UI
[ ] Integrate with Redux

[ ] Create module to choose image pre-processing steps

[ ] Create UI
[ ] Integrate with Redux

[ ] Build a parser in the backend to parse model details stored in Mongoose into a tf.keras.Model
[ ] Create module to perform transfer learning on a Keras Application

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with API endpoint for training a model
[ ] Add needed dependencies for machine learning (tensorflow, etc.)

[ ] Create module to save a model after it has been trained

[ ] Create UI
[ ] Integrate with backend

Milestone 2

[ ] Create module to show accuracy and loss graphs after training

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with back-end

[ ] Create module to build custom model (add/edit/remove layers)

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with API endpoint for training a model
[ ] Integrate with accuracy/loss graphs

[ ] Create module for exporting a trained model in 3 formats

[ ] Create UI
[ ] Integrate with back-end

[ ] Keras .h5
[ ] SavedModel
[ ] ONNX

Milestone 3

[ ] Create module for uploading a model for training

[ ] Create UI
[ ] Integrate with Redux
[ ] Build parser to parse model and extract details about layers
[ ] Integrate with backend

[ ] Modify transfer learning module to also choose and train saved models

[ ] Modify UI
[ ] Integrate with Redux
[ ] Integrate with backend

[ ] Create module for testing a trained model (inside the model builder dashboard)

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with backend

[ ] Add model testing to the model management dashboard

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with backend

[ ] Integrate model deletion with the model management dashboard

[ ] Create UI
[ ] Integrate with Redux
[ ] Integrate with backend

[ ] Complete documentation for installation and usage

Many-many between model and class
Many-one between preprocessing step and model
Many-one between layers and model

Model table
id INT AUTO_INCREMENT,
name VARCHAR,
type VARCHAR, -- classifier, segmentation, object detection, etc.
train_split DECIMAL,
test_split DECIMAL,
validation_split DECIMAL,
epochs INT,
batch_size INT,
learning_rate INT,
loss_type VARCHAR,
optimizer: VARCHAR,
metrics: VARCHAR,
loss_graph_url: VARCHAR, -- URL to access the graph of the training loss
accuracy_graph_url: VARCHAR, -- URL to access the graph of the training accuracy
saved_model_url: VARCHAR -- URL to access the saved model if the model has been trained

Model-Class junction table
class_id INT,
model_id INT

Preprocessing steps table
attributes?,
model_id INT

Not sure how to create this table(attributes section) since the number and names of the fields will depend on the type of preprocessing step chosen and the options available for that step.
Layers table
attributes?,
model_id INT

Similarly to the preprocessing table, the number and names of the fields depends on the layer chosen and the options available for that layer.

Hey @laksh22 I'm not sure about what you exactly want help in working with SQL I hope that you can elaborate that a bit. Also, inorder to help you I can recommend going through this I will be making a PR most probably tomorrow with the models and maybe you can refer that :)

Hey, shall we design an ER for a better clearance? It'll be helpful for future maintenance as well.

Hey, shall we design an ER for a better clearance? It'll be helpful for future maintenance as well.

+1.
Please go with MySQL Workbench.

@carpecodeum My query was regarding the layers and preprocessing_steps tables. Each row in the layers table for example should contain the name of a layer of a sequential model as well as its attributes. For example, a layer of the type Conv2D will have the fields filters, kernel_size, activation while a layer of the type Dense will just have a field named units. What is an ideal way to store such data where each row can have a different number of attributes?
Also thanks for the link, I'll check it out!

@laksh22 I think @UdeshUK @ivantha @Tushar19varshney Might be able to help with that better :)


Clean up plot - add license, line the documentation, cleanup imports

This PR cleans up plot.py

Codecov Report

Merging #509 into master will decrease coverage by 2.85%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #509      +/-   ##
==========================================
- Coverage   93.87%   91.01%   -2.86%
==========================================
  Files          30       30
  Lines        4034     4031       -3
==========================================
- Hits         3787     3669     -118
- Misses        247      362     +115

Impacted Files
Coverage Δ

databricks/koalas/plot.py
93.69% <100%> (-0.08%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
23.58% <0%> (-70.76%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/conftest.py
87.87% <0%> (-9.1%)
:arrow_down:

databricks/koalas/__init__.py
76.31% <0%> (-7.9%)
:arrow_down:

databricks/koalas/utils.py
97.29% <0%> (-2.71%)
:arrow_down:

databricks/koalas/frame.py
93.06% <0%> (-2.15%)
:arrow_down:

databricks/koalas/namespace.py
88.23% <0%> (-1.69%)
:arrow_down:

Continue to review full report at Codecov.

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

Im just merging this - pretty clear.


Change Date Output Value

More of a support request than anything else... I mean, I have seen how the representational view can be changed, but in a form it's always in the ISO-8601 standard. But in the backend I have to send a date formatted more like this.
"31-08-2018"

This is not a part of the picker. The picker would only output Javascript Native Date Object (Moment Object if you use OwlMomentDateTimeModule)


Introduce JSON schema for deny.toml

Status: going through trailing design iterations, there is enough code to start thinking of making it into a separate tool living in a separate repo.

This is the work that is intended to close https://github.com/EmbarkStudios/cargo-deny/issues/632
This PR is not complete yet, it already works nicely, but I want to improve it more. Almost nothing to review. It's just a draft PR that I'll try to finish as soon as I have time.
TODO
The things to do in this PR:

[ ] (WIP) Complete the specification of deny.schema.yml with the remaining shape of deny.toml configs
[x] Implement a custom post-processing for the YML schema definition to add a compat crutch for old JSON schema formats that don't support default annotations and enum documentation (not supported in any version)
[ ] Add tests to CI that validate the freshness of the JSON variant of the schema
[ ] Add code generation of markdown documentation for the mdbook. Reseach jsonschema2md for that or write something custom.
[ ] Add code generation for the Rust type definitions from the JSON schema. Maybe we could use some script that does that and then keep the custom deserialization logic that uses toml_span

TODO after merge
Make a PR to the SchemaStore repo with the entry for deny.toml file association.

I went a bit too far with this, but unfortunately, I don't have capacity to finish this work. I'll close this PR for now to prevent it from hanging. I'll leave the stage open for anyone else.


How to send file with message?

Whatsapp still does not allow sending files with text, only images.

Whatsapp still does not allow sending files with text, only images.

Oke..
So how to send image with text? I did not see it in api docs.
Thanks

this is how to send image with text,
/send-image
body: {
phone: "phone number",
path: "path for the image",
caption: "text messages"
}


some problems about generating after training

Following the guide I successfully train a layoutdm model based on my own dataset, I then use demo.ipynb to test my own layoutdm model.
But I found that it seems like I can only get a result by providing one of the layout from my dataset as one of the inputs, I am not sure if I get this right or not.From my perspective, it exact info from the layout I provide, like its mask, label, bbox, and then I can choose cond such as 'c', and layoutdm will then choose some of the categories from the info he exacted before and generate a layout for me.
If this is really the way it works, then can I just directly tell layoutdm the categories and their number I want and give me a layout?Where can I directly type in the categories I want if I using 'c' condition?
(cause I only see tokenizer = LayoutSequenceTokenizer(data_cfg=data_cfg, dataset_cfg=dataset_cfg) to define the final inputs, and it is for coverting a layout into a sequence)

If I understand correctly, your question is, "is it possible to directly feed the known conditions without referring to a real sample?". It is indeed possible. You might further look at get_cond. GIven a batch size B and token length S, what you only have to do is instantiating two variables, "seq" and "mask".

It is this your previous respond？

You might further look at get_cond. GIven a batch size B and token length S, what you only have to do is instantiating two variables, "seq" and "mask".

I think this may solve my problem, thanks with that, I will try this.
As for the instruction, the input is still a given layout, isn't it? I am actually mean to just input some categories(labels) which the model has learned before, instead of a known layout(bbox).

Thanks a lot !
I still got one more question about choosing the best layout.Since I can choose the number of samples to generate once a time, if I understand correctly, I can use my trained fid_model to evaluate the samples I generate and select the one with highest score right?
And do you have any suggestion to get the best layout?Can I just simply generate as many as possible and use fid_model to score them?


Add wrap-up table for ensemble methods

Adding a wrap-up table to summarize the differences and similarities between bagging vs. boosting methods (ways of training, combining and computation times) may help setting down ideas and improve the success rate of Quiz M6.3 Q1 (which is currently below 70%).
It could be at the end of the Ensemble based on boosting lectures, i.e., inside the ensemble_hist_gradient_boosting notebook.
What do you think?

There is this table for RandomForest vs Bagging https://inria.github.io/scikit-learn-mooc/python_scripts/ensemble_random_forest.html but we don't have a table for comparing bagging and boosting.

I think it's a good idea.

We could have a similar table at the end of this notebook:
https://inria.github.io/scikit-learn-mooc/python_scripts/ensemble_hyperparameters.html
or in a new notebook (without any code) right after this one.

We have such table in the "Intuitions on ensemble models: boosting" slides, which were introduced in https://github.com/INRIA/scikit-learn-mooc/pull/471.

We have such table in the "Intuitions on ensemble models: boosting" slides, which were introduced in #471.
Should we still add it in a notebook?

Only if we expand it a bit, for instance by including extra info about the influence of important hyper-parameters, e.g.:

too many trees can cause overfitting in gradient boosting but not for random forests.

Gradient boosting requires tuning a learning rate parameter while random forests do no have such a parameter.


Next.js version?

Hi there, first of all, thanks for this starter, very cool!
Is your feature request related to a problem? Please describe.
It would be nice to be able to use this template with Next.js
Describe the solution you'd like
A version of the template in Next.js
Describe alternatives you've considered
Having the community create this Next.js version

I'm closing this, since it's not really an issue with this gatsby starter but more of a request for a new project.
Technically there shouldn't be an issue to migrate React components from Gatsby towards Next.js. Even migrating the styling should be mostly copy paste, even though I know that Next.js by defautl rather uses Css-Modules and I'm using emotion.


DatabaseRule "unique" fails quietly when given an incorrect column

Laravel Version
11.20.0
PHP Version
8.3.6
Database Driver & Version
PostgreSQL 16
Description
If I write a validation rule for a non-existent table, for eg:
$validator = Validator::make(request()->all(), [
  'port' => 'required|integer|unique:nonexistent,port',
]);

The validator crashes with SQLSTATE[HY000]: General error: 1 no such table: nonexistent which is good enough. However, if I specify an existing table but a non-existent column, no errors or exceptions are thrown.
Steps To Reproduce
To reproduce this bug:

Create any table
Create a validator that uses the unique: rule
Specify a valid database name but an invalid column name

@woganmay, @crynobone  I have experience this issue several time and this can cause unexpected behavior and  issues. So I opened a pull request which I wanted to do a while ago.

I believe the expected behavior should be to throw an error when an invalid column is specified. I reviewed @Lakshan-Madushanka's pull request #52500, and it seems to address this issue effectively.

I don't think there's any action for us to take here as it's expected you provide a correct column name.


An admin can click on a user within the trip members overview to set him as new admin.

functionality implemented with commit: df78911


Update version for Support library, SDK and Build tool

Create for this issue -> https://github.com/agoda-com/Kakao/issues/31

update SupportLibrary version to 26.1.0
update compileSdkVersion and targetSdkVersion to 26
update buildToolsVersion to 26.0.2

@Alviere  Done


fixed Issue #1080 - fixed interactive window type error due to contex…

Issue #1080
Bug
Interactive Window type error due to context not being returned in node 0.10x
Fix
Context is now being returned

👍looks good to me


zeronet: init at 0.6.2

Motivation for this change
https://zeronet.io
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Is the path correct or should I put it under pkgs/servers?
This probably needs a nixos module too but I won't add it in this pr.

Nice, maybe we'll get ZeroNet here soon.
You can probably for the most part copy this other zeronet commit for the module.

@Chiiruno oh... there was another pr?! I always forget to do a search before writing code and duplicating things >.<

Only now I see the horror that is that lib directory... What is the policy on vendoring here? Should I patch it to use upstream for each of those libraries?

AFAIK you shouldn't have to mess with the lib directory.
See this module for ideas for the zeronet module, it shouldn't have to get more complex than that.
Make sure to add a user/group id to nixos/modules/misc/ids.nix and call your module in nixos/modules/module-list.nix.

This is one of those packages where the authors think its a good idea to bundle everything and do updating from within the application, see HelloZeroNet/ZeroNet#382.

This is likely going to need quite some patching to get rid of vendored dependencies. They also do some sys.path. manipulation in zeronet.py I saw.

From #31910

@Chiiruno The path should be ok, and I think the deps will remain vendored for now

@GrahamcOfBorg  build zeronet

Success on x86_64-darwin (full log)
Attempted: zeronet
Partial log (click to expand)
Listing ./tools ...
Listing ./tools/coffee ...
Listing ./tools/tor ...
Compiling ./update.py ...
Compiling ./zeronet.py ...
installing
post-installation fixup
strip is /nix/store/r5mcn9vqq80v5pfqp45d7290cis7dwp4-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/nwdmga7cyl557la6wjplnilwvfjc2vr9-zeronet-0.6.2
/nix/store/nwdmga7cyl557la6wjplnilwvfjc2vr9-zeronet-0.6.2/share/zeronet.py: interpreter directive changed from "/usr/bin/env python2.7" to "/nix/store/q3ncxyf9ql0wffblk758a2790mjfvan6-python-2.7.15/bin/python2.7"

Success on aarch64-linux (full log)
Attempted: zeronet
Partial log (click to expand)
Compiling ./update.py ...
Compiling ./zeronet.py ...
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hblz98pxggh1w63n2ig1wvd7xsl3a1xi-zeronet-0.6.2
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/hblz98pxggh1w63n2ig1wvd7xsl3a1xi-zeronet-0.6.2
/nix/store/hblz98pxggh1w63n2ig1wvd7xsl3a1xi-zeronet-0.6.2/share/zeronet.py: interpreter directive changed from "/usr/bin/env python2.7" to "/nix/store/1xkxxrd2sd8q78icm687ac8si9miak45-python-2.7.15/bin/python2.7"
checking for references to /build in /nix/store/hblz98pxggh1w63n2ig1wvd7xsl3a1xi-zeronet-0.6.2...
/nix/store/hblz98pxggh1w63n2ig1wvd7xsl3a1xi-zeronet-0.6.2

Success on x86_64-linux (full log)
Attempted: zeronet
Partial log (click to expand)
Listing ./tools/tor ...
Compiling ./update.py ...
Compiling ./zeronet.py ...
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/n5h2ad8jdvpvj63jh2f8ywada4cqs4b5-zeronet-0.6.2
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/n5h2ad8jdvpvj63jh2f8ywada4cqs4b5-zeronet-0.6.2
/nix/store/n5h2ad8jdvpvj63jh2f8ywada4cqs4b5-zeronet-0.6.2/share/zeronet.py: interpreter directive changed from "/usr/bin/env python2.7" to "/nix/store/xlc7ld1xd57ha3x9mbx11c84j290va0f-python-2.7.15/bin/python2.7"
checking for references to /build in /nix/store/n5h2ad8jdvpvj63jh2f8ywada4cqs4b5-zeronet-0.6.2...


Determine Max Game Rom Size

We need to finalize what the max game rom size will be.
I think powers of two are good, and given the feature set we should be able to estimate a good balanced size.
Its good to think about the core motivations of the project as a whole too.
I could see anything from 4mb up to 64mb being realistic. Going below 4mb would potentially limit sound and high res graphics. 32mb or higher will limit the usability of the app since people will need to wait longer to launch new games.
Alternatively, it could instead be possible to split the game rom into multiple sections, such as 8mb for code, 8mb for audio, 8mb for graphics, or something else along these lines.
To put some things into perspective, the SNES had a max size of just around 14.5mb, while the n64 went up to 64mb on some specialized games. CDs are 700mb and way over budget here.
For handhelds, GBA went up to 64mb, DS up to 512mb, while 3ds and PSP was in the multiple GB range.
What do you all think?

Since both N64 and GBA managed with 64mb, to me that feels like a suitable hard ceiling.
For early jams though, the ceiling should be set to the lowest possible, e.g. 4mb.

Right, some other points worth considering here is:

The .gcrom files is already raw binary, and then additionally zstd compression is applied on top of it. So this 64mb limit would be after the compression.
Larger files obviously take more time to download, and also take more time to decompress. More startup delay can be a bad thing (up to a certain point). I don't think its good to expect people to want to wait more than 1 minute to both download the games AND decompress them.
I'll also likely be hosting the games myself on some file repo, such as the one we are discussing in #35 , so here smaller files means less cost.

I could see these reasons to potentially push the number lower to start. I guess it would be easy to later, expand the size, than it would be to shrink it.

For the moment, we're going to stick with 16mb for the max rom size!


Click on map to create a post

See Aaron's design below. Clicking on the Cursor changes to a plus icon.
Clicking on map pops up create dialog with new title.
We will also pass the lat,lng of the location to the create dialog which will appear in the location field for the new post.
(Let's write a click to get coordinate from the map general function.)
The create dialog's title should change to "What would you like to create at this location?"
Remove discussion from the list in the create dialog for now since it does not have a location.
After the post or group is created it should appear on the map immediately.

depending on how this is implemented this could require changes in mobile app to work, make sure it doesnt break the mobile app *

https://www.figma.com/file/aBZ1d4hg1gMW0MR7NhZoqs/Add-posts-to-map?node-id=0%3A1

@Sofacosta has completed most of the work for this feature here: https://github.com/Hylozoic/hylo-evo/pull/1138
Currently though the new Post will not make it to the queryResults for the Map Explorer or Map Explorer Drawer as there is no queryResults reducer handling of the FETCH_POSTS_MAP or FETCH_POSTS_MAP_DRAWER actions. These likely / hopefully can be handled the same as they are with the FETCH_POSTS used on the feed, adding the additional types to store/reducers/queryResults.js. There also may be a case here to re-factor the FETCH_POSTS_MAP... queries into the existent FETCH_POSTS action.

Some questions/issues:

[ ] Right now the way sofia set it up is you just click and hold for a second on the map to add a post, she has not yet added the create post state button in your designs @brodeur . One thing is confusing in your designs though, it says “When map is pressed for 1 second without moving, dragging or scrolling, open post creation modal with the location pressed as the location of the post”, but doesn’t specify if this happens always, or only when the state button is pressed. I could see having both features, without the add post button pressed you can still click and hold for a second to create a post, but with the button pressed then another click instantly creates a post. Or Aaron did you mean that even after clicking the button you still have to click and hold for a second?
[ ] after you create the post should it unselect the create post mode or stay in it?
[ ] I'm seeing a bug where maybe 20% of the time the lat/lng comes up as a 0
[ ] Another bug is that when you create a post it removes all the other query parameters from the URL so if you refresh the map it moves to a different viewport. Those params should be kept in the URL on the redirect to the post
[ ] Also right now we are still showing the Discussion post type which doesn't currently have a location. We should either remove Discussion from the list, or just add location to Discussion! Which is not that much work at all. Decision being made here

ticket to add posts immediately to the map https://github.com/Hylozoic/hylo-evo/issues/1143

Also, we forgot to keep this in PR until someone addresses the queryResolver stuff for map.

fixed the queryResults stuff!


Scrollbar for Samples with Numerous Sources

Added an overflow scrollbar for samples with numerous code sources, such as the deferred rendering, Cornell box, or bitonicSort samples.
https://github.com/webgpu/webgpu-samples/assets/62450112/0674c338-7929-4cc1-92f4-9524868fed2f
Draft is currently in PR because I would like to apply analogous Firefox styling for viewing in Nightly Firefox builds.

Actually, applying scrollbar-width: thin seems to be close enough for now.

Maybe this makes it a bit hard to see that there are more tabs to the right? Right now we flow the tabs onto a new line so they're easy to see.

Maybe this makes it a bit hard to see that there are more tabs to the right? Right now we flow the tabs onto a new line so they're easy to see.

Possibly, but I'd contend that that's only likely if the end of one code "tab" aligns perfectly with the edge of the screen. I think the presence of the scrollbar and a code tab's title going off-screen is enough to clue in the user. Of course, this is a non-essential, subjective change, so it's ultimately just a matter of preference between the stacked and scrolling versions.

Thinking about this further, if someone doesn't have a touchpad and doesn't know shift-scroll then horizontal scrolling is a bit painful. I would prefer a larger scrollbar (it would be more obvious, and easier to click), though I suppose I'm still not a fan of horizontal scrolling in general.
With a larger scrollbar though, I'd be happy enough either way. Thanks for putting up with my opinions :)


use alloy transaction types

the core tx types are quivalent to alloy's:
https://github.com/paradigmxyz/reth/blob/67f617646ce4b68a5096239238aa9209636ff500/crates/primitives/src/transaction/eip1559.rs#L13-L13
the only difference is the codec impl
https://github.com/paradigmxyz/reth/blob/67f617646ce4b68a5096239238aa9209636ff500/crates/primitives/src/transaction/eip1559.rs#L11-L11
we can implement codec by doing the same as for
https://github.com/paradigmxyz/reth/blob/67f617646ce4b68a5096239238aa9209636ff500/crates/storage/codecs/src/alloy/withdrawal.rs#L6-L11
TODO

[ ] replace EIP1559
[ ] replace EIP2930
[ ] replace legacy
[ ] replace EIP4844
[ ] replace 7702
[ ] optimism deposit

This should be done in separate prs and involves

move existing struct def to https://github.com/paradigmxyz/reth/blob/67f617646ce4b68a5096239238aa9209636ff500/crates/storage/codecs/src/alloy/transaction.rs#L1-L1 impl codec for alloy types via into/from
phase out primitive transaction defs

there are likely missing/renamed functions in alloy, so we need to surface those and add to alloy if appropriate

I can take this on.

cool, this will likely be a bit painful, see #9485 for ref
we likely need to do some work on rlp for this

@mattsse Looking into this, it seems I will have to convert from reth Signature to alloy one at many places. Do you think I should work on migrating reth Signature to alloy as a prerequisite to this issue, or converting is ok for now?
For instance in the code below, I would like to call encoded_len_with_signature() on alloy TxLegacy that takes an alloy signature as a parameter:
https://github.com/paradigmxyz/reth/blob/cbe9a7c5cae12e97e53d54f7738852c56e2530d4/crates/primitives/src/transaction/pooled.rs#L303-L306

is the end goal to replace reth_primitives::PooledTransactionsElement with alloy_consensus::TypedTransaction ? if so we'd be more efficient if we tackle this by making types that use reth_primitives::PooledTransactionElement generic over a type T: alloy_consensus::Transaction. do we have a complete list of types we want to replace with its alloy equivalent?

the codec trait, and impl the codec trait for alloy types where we define the codec trait

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello! I am a software engineer with approx 8 years experience in Python, Java and Typescript. I have recently been learning rust and studying the core program with the Privacy and Scaling Explorations team to learn more about applied ZK.
Whilst new to rust, I have a lot of experience in writing maintainable, tested and clean code and know I can contribute positively to your code base!
How I plan on tackling this issue
Since it seems like a fairly straightforward migration, I would check the examples that have been given and ensure that I replicate the methodology.

@tcoratger thank you for working on all PRs from here! would you like to work on TxDeposit migration to close this?

@tcoratger thank you for working on all PRs from here! would you like to work on TxDeposit migration to close this?

Mhh not sure we have all the required methods in alloy TxDeposit no? like stuffs to do encoded_len_with_signature or payload_len_for_signature as SignableTransaction is not implemented for TxDeposit at the moment or did I miss something? (I'm not familiar with the op-alloy codebase so maybe I'm missing something here)

@tcoratger thank you for working on all PRs from here! would you like to work on TxDeposit migration to close this?

Mhh not sure we have all the required methods in alloy TxDeposit no? like stuffs to do encoded_len_with_signature or payload_len_for_signature as SignableTransaction is not implemented for TxDeposit at the moment or did I miss something? (I'm not familiar with the op-alloy codebase so maybe I'm missing something here)

deposit transactions can't be signed, so we won't need those

@tcoratger thank you for working on all PRs from here! would you like to work on TxDeposit migration to close this?

Mhh not sure we have all the required methods in alloy TxDeposit no? like stuffs to do encoded_len_with_signature or payload_len_for_signature as SignableTransaction is not implemented for TxDeposit at the moment or did I miss something? (I'm not familiar with the op-alloy codebase so maybe I'm missing something here)

deposit transactions can't be signed, so we won't need those

And we need to merge this right? https://github.com/alloy-rs/op-alloy/pull/68

@tcoratger thank you for working on all PRs from here! would you like to work on TxDeposit migration to close this?

Mhh not sure we have all the required methods in alloy TxDeposit no? like stuffs to do encoded_len_with_signature or payload_len_for_signature as SignableTransaction is not implemented for TxDeposit at the moment or did I miss something? (I'm not familiar with the op-alloy codebase so maybe I'm missing something here)

deposit transactions can't be signed, so we won't need those

And we need to merge this right? alloy-rs/op-alloy#68

yep

@klkvr Also previously we had a method like:
pub(crate) fn payload_len_without_header(&self) -> usize {
    let payload_length = self.fields_len();
    // 'transaction type byte length' + 'header length' + 'payload length'
    1 + length_of_length(payload_length) + payload_length
}

which calculates basically 'transaction type byte length' + 'header length' + 'payload length' but in op alloy we only have:
fn length(&self) -> usize {
    let payload_length = self.fields_len();
    Header { list: true, payload_length }.length() + payload_length
}

but we lack the 'transaction type byte length' so this is also a method to add in op alloy right?

yeah, I think we can add encoded_len(&self, with_header: bool) and encode(&self, &mut dyn BufMut, with_header: bool)

yes, will track

yes, will track

@mattsse If you open an issue please tag me. If I've time, will have a look

https://github.com/paradigmxyz/reth/issues/10687


Blog about the 2i2c CILogon integration

Closes https://github.com/2i2c-org/team-compass/issues/621
todo:

[x] figure out if a partnership has been officially signed before posting this -> https://github.com/2i2c-org/meta/issues/465

Got confirmation from Jim, so I will go for a merge today 🚀


Fix Nudge Json

The Nudge payload in here ie messed up. Can you add the one from the Nudge GitHub?
https://github.com/macadmins/nudge/blob/main/Schema/jamf/com.github.macadmins.Nudge.json

Please submit manifest change suggestions upstream. Thank you!


Extract Changelog_Release to it's own project.

The Changelog Release script has proven useful enough to extraxt to it's own project. It would also make easier and less confusing for this script repository, as it should not grow to much. There are a few changes that would make sense for that separation (packaging version handling etc) and finally, a go-port could be started in a branch of that while maitaining the original script.

See, https://github.com/janderssonse/changelog-tag


maximum length of audio clip that can be transcribed using en8k model

I tested the en8k model using the demo server. For longer audio clips e.g. 28 seconds of wave file, it seems that only last 10 seconds or so of the wave file got transcribed. The 1st 18 seconds just got discarded. Does anyone know why?

Can you let us know whats the maximum that can be done ?


Update dex.rst

Incorrect command.
Modify this link to include the branch name, and possibly the page this PR modifies:
https://osc.github.io/ood-documentation-test/BRANCH-NAME/
Add your description here

@Shadowphax Thanks for catching that!


Related #2403: cli error message updates Part 1

There are a lot of calls to rlang::abort() that need updating. Best to tackle this in parts.

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Related #2403 into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF version of it to the same folder.
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

Should the class argument be specified in the cli_abort() calls?

How would we name the classes, could use function name, but what if there is more than one check in the function. Would we ever use the class? I can see benefit of having class in assertion functions, so we can just check if check is triggered without checking message. But not sure we would use the class?

Should the class argument be specified in the cli_abort() calls?

How would we name the classes, could use function name, but what if there is more than one check in the function. Would we ever use the class? I can see benefit of having class in assertion functions, so we can just check if check is triggered without checking message. But not sure we would use the class?

Good questions!
The use case I had in mind was where you have a company or study specific function which calls an admiral function and you want to catch the error to provide a more user-friendly error message. However, with a class you could easily catch the error but for the message you still need to parse the original message to get out what went wrong and generate the new message. We have this problem even with our assert_*() functions. In assert_terms() I had to call assert_data_frame() twice (once for checking it's a data frame and again for checking if the required variables are present) to be able to update the error message.
Maybe it does not help much to set the class with our current approach.

I have added the changes suggested by @kaz462 to https://github.com/pharmaverse/admiral/pull/2417.
Should we cancel this PR as the changes are included also in https://github.com/pharmaverse/admiral/pull/2417?

I have added the changes suggested by @kaz462 to #2417.
Should we cancel this PR as the changes are included also in #2417?

Yes lets cancel this one - it is getting a little messy.

@bundfussr do you mind closing as you are close to this process


Problems with isInBrowser() and jsdom

I use jsdom for testing some jQuery functionality using node and when installing source-map-support, I get the problem, that the isInBrowser() function returns true, though I'm really only faking it. And then it can't load the source maps.
I have two suggestions for fixing this:

Only check for browser-capabilities on construction and let isInBrowser be constant. That way I could simply just install jsdom after source-map-support. And I can't think of any other way isInBrowser could change from call to call.

Make an option on install to force either node or browser behavior.

I would be happy to make a PR if any of the above solutions seems ok to you :)
And great project by the way!

There will always be edge cases so I much prefer the second option :)

Perfect. I'll get on it! :)

+1

Hi, I tried to make a pull request to solve the issue.
Then I tried to make another (different strategy, pick what you'd prefer).
https://github.com/evanw/node-source-map-support/pull/106
https://github.com/evanw/node-source-map-support/pull/105
Unfortunately there's a build error concerning some whitespace which I really don't get looking at my changes. =/

@julien-f sorry, I got caught up in some other tasks, so @tugend got it done...
@tugend none of those seem to implement option 2?

@tugend maybe it would be more intuitive to have an environment option that could have the value 'node' | 'browser' | 'auto', with auto as default (as now) and the just forcing the chosen environment.

@asgerhallas good point. Hereby updated https://github.com/evanw/node-source-map-support/pull/105/files

To avoid confusion I removed my alternative and only kept the pull request for specifying the environment as an option. Sorry for confusion. I updated the docs to account. I did not find any existing tests for options and could not run the tests on my machine (possible a win10 issue?). The module it self works fine.

@julien-f, hey friend, we're a couple of people who could use the feature in 106.
If you wouldn't mind having a look at https://github.com/evanw/node-source-map-support/pull/106,
we'd be much obliged.
I have no idea why Travis is failing #62.1NodeJs:IOjs handleUncaughtExceptions, it seems to be some encoding (everything is utf-8) or a whitespace issue, but I haven't been able to figure it out. =(/
If there is something I can improve on the pullrequest please don't hesitate to let me know.
Cheers

Awesome. @julien-f - when can we expect a release?

@electricmonk Published as v0.3.3, let me know if there are any issues.


Change images

Change images of about us page add saome realistic images
you can use ai for that

lets try it

Hey i want to contribute in this issue can you please assign it to me under hacktoberfer-2024

please do this before
git fetch origin
git checkout 31-change-images

ok Thanks sir