IPVS is non-functional in 1.26

Environmental Info:
K3s Version:
k3s version v1.26.3+k3s1 (01ea3ff2)
go version go1.19.7
Node(s) CPU architecture, OS, and Version:
Debian 11, amd64, hetzner cloud VPS
Linux debian-2gb-hil-1 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
Cluster Configuration:
Single node
Describe the bug:
Starting with 1.26 having IPVS enabled completely breaks the cluster's traffic flow. As soon as IPVS is enabled and the firewall rules/ipvsadm policies kick in, the internal cluster communication breaks in addition to external traffic to rather important ports such as port 22 and port 6443
No pods are able to spin up, attempting to install calico results in the pod not being able to communicate with the API server and the cluster is in a largely failed state.
Steps To Reproduce:
Spin up a fresh Debian 11 VPS -- I used hetzner for this test
Install requisites for ipvs:
apt install ipset ipvsadm

Install k3s and enable ipvs all at once
curl -sfL https://get.k3s.io | sh -s - server --kube-proxy-arg proxy-mode=ipvs

Wait for initialization -- as soon as iptables ipvs policies are enacted, the server is now broken an unable to accept new ingress connections.
Expected behavior:
The cluster works.
I can ssh into my machine with ipvs enabled
I can use the kube api externally with ipvs enabled
I can start pods (i.e. Calico) and finish building up my cluster (note, flannel was left enabled for this test to prove how simple the error is to reproduce)
Actual behavior:
No new connections can be created.
Cannot create a new SSH connection.
Cannot connect to the kube api server from an external connection
Cannot ping the external IP from the command line of the server itself or an external IP
Cannot spin up new pods or install calico
Additional context / logs:
I do not have such issues with IPVS in my vanilla k8s cluster running 1.26.1
The issue was not present in 1.25. Downgrading a broken machine to the latest 1.25 branch results in the behavior disappearing.
It appears the difference between 1.25 and 1.26 is coming down to iptables rules
These iptables rules appear new as of 1.26 (they are not present in k3s 1.25.8):
-A KUBE-IPVS-FILTER -m set --match-set KUBE-LOAD-BALANCER dst,dst -j RETURN
-A KUBE-IPVS-FILTER -m set --match-set KUBE-CLUSTER-IP dst,dst -j RETURN
-A KUBE-IPVS-FILTER -m set --match-set KUBE-EXTERNAL-IP dst,dst -j RETURN
-A KUBE-IPVS-FILTER -m conntrack --ctstate NEW -m set --match-set KUBE-IPVS-IPS dst -j REJECT --reject-with icmp-port-unreachable

Removing the rule allows remote connections to once again be initiated:
-A KUBE-IPVS-FILTER -m conntrack --ctstate NEW -m set --match-set KUBE-IPVS-IPS dst -j REJECT --reject-with icmp-port-unreachable

My vanilla 1.26.1 cluster has the same rules and has none of these issues.
Finally, the issue appears to have silently snuck in during my node's automatic update to 1.26 (my mistake). It's curious to note that nginx ingress traffic on port 80 and 443 were unaffected while the server was still running (though ssh/kube api was already dead) -- that is until I rebooted my server and calico was unable to start, which cascaded into a full failure because no services were able to start upon a reboot.

No pods are able to spin up, attempting to install calico results in the pod not being able to communicate with the API server and the cluster is in a largely failed state.
I can start pods (i.e. Calico) and finish building up my cluster (note, flannel was left enabled for this test to prove how simple the error is to reproduce)

I'm confused, are you using both the embedded flannel and calico at the same time?

I'm confused, are you using both the embedded flannel and calico at the same time?

No I have two different clusters. The single node cluster I use for production tasks broke following the update. This instance uses calico.
The POC for reproduction does not use flannel and was kept as simple as possible to remove possibility of conflicting issues as a result of my production instance's more complex configuration. Apologies if that was unclear

These aren't rules we add ourselves, these rules would be managed by kube-proxy. Do you perhaps need to add additional kube-proxy args to accomplish what you're trying to do?

I have wondered this myself; however, all k3s documentation I can find related to ipvs should note that simply enabling the option in kube-proxy is enough

Have you compared the args passed to kube-proxy between k3s and your vanilla (by which I'm assuming you mean kubeadm) cluster? That is probably where I'd start. None of the kube-proxy code itself is modified by this project.

Thanks for the hint in the right direction. Upon closer examination, I was not able to determine any specific configuration settings of kube-proxy responsible for this; however, I did note that the issue seems to come down to the related ipset for KUBE-IPVS-IPS (i.e. the IPSET matched against for rejections).
The ipset for the kubeadm cluster, which has no outward issues:
Name: KUBE-IPVS-IPS
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 1592
References: 1
Number of entries: 29
Members:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

The ipset of the Debian 11 POC k3s instance:
Name: KUBE-IPVS-IPS
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 440
References: 1
Number of entries: 5
Members:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
5.xx.xx.xxx <-- external IP

It seems to me the major config difference is that some process (unknown to me) has determined the external IP should be passed to the KUBE-IPVS-IPS ipset, which gets matched against rejection.
I'm only able to influence the address passed to this ipset by altering the advertise-address of the server (subsequently node-ip and external-node-ip influence this value by being the value advertise-address defaults to. Whatever value ends up here ends up being passed to the IPVS ipset list  and gets blocked by the iptables rule first mentioned.
That said, the external IP of a single-node cluster is the most logical advertise address since no private IPs exist by default in such a setup -- other than <IP_ADDRESS> (for which pinging localhost will then be blocked if we change the advertise address to localhost)
This directly contrasts the behavior of a kubeadm k8s cluster, whereby the advertiseAddress configured to the cluster is not passed to IPVS
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: "<IP_ADDRESS>"
nodeRegistration:
  criSocket: unix:///var/run/crio/crio.sock
  kubeletExtraArgs:
    node-ip: "<IP_ADDRESS>"
    cloud-provider: "external"
---
apiVersion: kubeadm.k8s.io/v1beta3
kind: ClusterConfiguration
apiServer:
  certSANs:
  - "5.external.ip"
  - "<IP_ADDRESS>"
networking:
  podSubnet: "<IP_ADDRESS>/16"
  serviceSubnet: "<IP_ADDRESS>/16"

And all the ipvs managed IPs -- no <IP_ADDRESS> here
kube-ipvs0       DOWN           <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>/32 <IP_ADDRESS>

It may not be an issue with kube-proxy directly, but some process in the spin up of the cluster thinks the external IP should be treated as an internal pod address and ends up passing this IP to IPVS as the ipsets are being created/sync'd

Some further musings (apologies, I keep digging deeper as my understanding of the issue grows and some new things get uncovered).
ipvs adding the node's external IP to the IPVS interface appears a result of the traefik ingress mixed with the servicelb load balancer. Kubernetes is supposed to only listen to services to add to IPVS, which clued me in to go looking for services bound to external IPs.
In the POC instance, that's the traefik load balancer, in my previously working production instance, that's a metallb load balancer for nginx ingress. Curiously, the kubeadm cluster's loadbalancer does not display this behavior. Its loadbalancer is a physical instance, but does have an external IP assigned to it. Curiously the internal/external IP of this load balancer are not discovered by IPVS, despite a load balancer service present, pointing to a DNS entry which resolves to the external IP. So, I'm still confused about this discrepancy between the clusters but am glad to at least have a better handle of the underlying mechanisms at play.
I will have to keep digging though I'm no longer certain this is specific to k3s. I would have to setup a single node kubeadm cluster/metallb to test this, but that is not a task for today.

Do you by any chance have a service on that address, one using ServiceLB or otherwise? Kube-proxy handles routing traffic to service ClusterIP addresses, I wonder if for some reason it is also adding the service's loadbalancer address to the ipset. ServceLB is the primary thing that K3s would have but your kubeadm cluster would not.

Kube-proxy handles routing traffic to service ClusterIP addresses, I wonder if for some reason it is also adding the service's loadbalancer address to the ipset. ServiceLB is the primary thing that K3s would have but your kubeadm cluster would not.

We responded very closely to each other :slightly_smiling_face: That indeed appears to be exactly what's happening. In the POC cluster, the ip assigned to the traefik ingress service via service LB gets discovered by IPVS. This doesn't seem desirable but I'm not familiar enough with the underlying code to know if that is "correct"

I wouldn't expect it to pick up the loadbalancer address; I've not seen it do that nor received reports of problems with ipvs in the past so perhaps this is new behavior from kube-proxy. I'd have to do some research to see if it's expected or configurable.

@rbrtbnfgl @thomasferrandiz do you have any clues on whether or not this is something that might have changed in recent versions? I will admit I haven't ever played with IPVS much. I will say that I wouldn't expect it to add IPVS entries for external loadbalancer service addresses but its possible this is something that's changed upstream?

Seems like this was actually an issue with upstream despite me having issues replicating it in my kubeadm built cluster.
The threads linked here are showing that a PR has been merged and the fix is targeted for the 1.28 release (unless it gets backported).
Thanks for the assistance in helping to track this down.

The original fix was implemented in 1.28 and backported in 1.27.2. A fix hasn't yet made it into 1.26.
This could be closed because it is resolved in newer versions, but it is also still not functional if for some reason you can't upgrade.

Closing as resolved upstream; it'd be nice if they would decide to backport it to 1.26.

Issue is still present in 2.28.3 as far as I can tell.

Look like your issue is relate to : https://github.com/kubernetes/kubernetes/pull/115019#issuecomment-1784984211


Wrong Azure Powershell command RM instead of Az

Hello Microsoft team,
Please update the command on this page, the command Get-AzureRmExpressRouteServiceProvider is not in use anymore, it is a legacy Azure RM, the correct should be Get-AzExpressRouteServiceProvider from Azure Az PowerShell module.
References:
https://docs.microsoft.com/en-us/powershell/module/az.network/get-azexpressrouteserviceprovider?view=azps-5.4.0
https://docs.microsoft.com/en-us/powershell/azure/new-azureps-module-az?view=azps-5.4.0#migrate-existing-scripts-from-azurerm-to-az
The page that should be updated:
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/expressroute#connectivity-providers

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

ID: 61c1b093-200e-8d59-0e6e-98f510dca5f6
Version Independent ID: db6fcf0f-1a88-b216-4c08-a83c4128b4fa
Content: Extend an on-premises network using ExpressRoute - Azure Architecture Center
Content Source: docs/reference-architectures/hybrid-networking/expressroute.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 368488

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 368488

@romulobrandino Thanks for bringing this to our attention. I have submitted a PR to fix the issue that's in review.


[BlobService] Validation for BlockBlob APIs included in July milestone

unit test

done in https://github.com/Azure/azure-sdk-for-cpp/pull/181


Power Users Can Use Redis to Filter Already Downloaded URLs, Use HashSet for URL Matching From File

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[ ] a bug fix (Fix #...)
[ ] a new Ripper
[ ] a refactoring
[ ] a style change/fix
[x] a new feature

Description
This feature adds support to use Redis as the mechanism for skipping already downloaded URLs. If you use RipMe over a longer period of time, to download many, many galleries and albums, the url_history.txt file gets quite large. Doing an O(n) scan through the entire list for every URL in a job becomes VERY expensive. My own url_history.txt file is approaching 3 million lines and 130 MB. Using Redis speeds up the ripping process considerably AND allows power users the ability to coordinate jobs running across multiple machines on a network.
Users can optionally add the following lines to the rip.properties file:
url_history.redis_cache.host = <IP_ADDRESS>  #IP address or domain name for the redis host
url_history.redis_cache.port = 6379 #redis port (optional, rip me defaults to 6379)
url_history.redis_cache.key_prefix = RipMeURL:  #a prefix to give the keys added to redis (optional, will default to an empty string)

If users do not add this configuration, the URL matching algorithm now uses a HashSet. This is memory intensive, but performs faster than the sequential scan.
Note: RipMe will continue to append new lines to the url_history.txt file since this operation does not seem to slow down the job (...at least at the scales that I have encountered)
Note 2: The easiest way to run redis locally is to use docker (Something like docker run --name my-redis -d -p 6379:6379 redis). Alternatively you could download and install redis for your OS.
Testing
Required verification:

[ ] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[x] I've verified that this change works as intended.

[ ] Downloads all relevant content.
[ ] Downloads content from multiple pages (as necessary or appropriate).
[ ] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[ ] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

what a cool pull request. not that i'd ever need it - but the principle is a great show case :)  tried to merge here: https://github.com/ripmeapp2/ripme , but i then wondered how to see within a couple of seconds now and in future if it works. you mind doing a tiny unit test just, maybe in the lines of:
https://www.baeldung.com/spring-embedded-redis


The Client Secrets have expired, then we have renew them, then we have this error

Ooops! An unexpected error seems to have occured. Why not try refreshing your page? Or you can contact your administrator if the problem persists.
Permissions needed. Ask your IT admin to enable this option for you

Hello,
did you find the fix for this issue ?


Filter 2d arrays

Hi, I have been interested to explore the features of Better Array.  It seems to offer some really convenient and powerful capabilities.
Today I was looking to use it for filtering data from a 2d array.  I saw in the documentation I can assign such an array through .Items.  However, I don't see now how I can filter a 2d array.  The method arguments don't seem to include the index of the column that I would filter on, and the examples refer to 1d arrays.
Am I correct that currently these methods only support 1d arrays, and if so is there any intention to expand them to 2d arrays?

Apparently, there is no options to filter 2D arrays. How ever, you can contribute with this great project or to find an alternative one.

I originally had it recursing through each item in 2d arrays to filter entries individually. Why I took that approach IDK. Seems like filtering 2d arrays by column index is probably more useful. Will add now. Docs to be updated shortly... :)

Change included in v1.8.0. Test coverage included by may require more. Will look at adding further coverage tomorrow/this weekend when I update the docs.

Great to hear.  Using an index makes sense to me, as long column names aren't available.
I confirmed that I was able to run a basic filter.  I think a question for next steps is whether it could a.) allow for "like" filtering with wildcards or "contains" filtering (the latter in the style of native VBA filter()), and b.) filtering on multiple columns, but that is tricky to manage intuitively, as full functionality presumably required "and" versus "or" chaining.  Presumably that rabbit hole is why Excel has its standard of no more than 2 criteria.
Without "like" or "contains" filtering, I suppose one can add a helper column (loop through the array using InStr() or Like on  each element in the desired column to create a new column of booleans) and then filter on the helper column.  That approach can also be used for multiple conditions, .  I have not gotten far enough to see whether it would make that easier.
Apologies if this is the wrong place to put it, but I was also confused by the use of "recurse" and "recursive" in several methods.  I understand recursion as calling a function within itself.  There is a reference to nested arrays, and I could also see how dealing with nested arrays might use recursion (say, to list out all elements in an array and any subarrays, like recursive directory listing functions).  Is that the idea?  Personally I can't imagine working much with nested arrays (I kind of love the "tidy data" concept of one-record = 1 row popularized by "tidyverse" in R), but if I did, my intuition  tells me it would be unlikely that I would want to run the same function across nested levels.  Granted: I may have misunderstood, or I may just be unaware of the use cases, but possibly if it is confusing to me it may be to others as well, FWIW.

I confirmed that I was able to run a basic filter

To achieve this goal, you need a specialized piece of code that provides a source of expression evaluation. Therefore, you can achieve your goal by combining VBA Better Array and the selected expression evaluator.
This way you can filter arrays by multiple columns with a relatively infinite amount of filtering levels/conditions.


[Colab] jaxlib.xla_extension.XlaRuntimeError: INTERNAL: RET_CHECK failure

Description
Running a Colab notebook that was working on Colab GPU last month, getting INTERNAL: RET_CHECK failure all of sudden.
Tried: https://github.com/google/jax/issues/13504, which is !export XLA_PYTHON_CLIENT_MEM_FRACTION=0.7
Did not work.
GPU: Tesla T4 on Colab
Not sure if this is a Jax issue, any help?

  File "/usr/local/lib/python3.9/dist-packages/jax/_src/numpy/lax_numpy.py", line 2088, in copy
    return array(a, copy=True, order=order)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/numpy/lax_numpy.py", line 2047, in array
    out = _array_copy(object) if copy else object
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/lax/lax.py", line 4359, in _array_copy
    return copy_p.bind(arr)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/core.py", line 343, in bind
    return self.bind_with_trace(find_top_trace(args), args, params)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/core.py", line 346, in bind_with_trace
    out = trace.process_primitive(self, map(trace.full_raise, args), params)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/core.py", line 789, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/lax/lax.py", line 4400, in _copy_impl
    return xla.apply_primitive(prim, *args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/dispatch.py", line 123, in apply_primitive
    compiled_fun = xla_primitive_callable(prim, *unsafe_map(arg_spec, args),
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/util.py", line 253, in wrapper
    return cached(config._trace_context(), *args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/util.py", line 246, in cached
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/dispatch.py", line 202, in xla_primitive_callable
    compiled = _xla_callable_uncached(lu.wrap_init(prim_fun), device, None,
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/dispatch.py", line 355, in _xla_callable_uncached
    return computation.compile(_allow_propagation_to_outputs=allow_prop).unsafe_call
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/interpreters/pxla.py", line 3254, in compile
    executable = self._compile_unloaded(
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/interpreters/pxla.py", line 3225, in _compile_unloaded
    return UnloadedMeshExecutable.from_hlo(
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/interpreters/pxla.py", line 3512, in from_hlo
    xla_executable = dispatch.compile_or_get_cached(
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/dispatch.py", line 1095, in compile_or_get_cached
    return backend_compile(backend, serialized_computation, compile_options,
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/profiler.py", line 314, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/jax/_src/dispatch.py", line 1040, in backend_compile
    return backend.compile(built_c, compile_options=options)
jaxlib.xla_extension.XlaRuntimeError: INTERNAL: RET_CHECK failure (external/org_tensorflow/tensorflow/compiler/xla/service/gpu/gpu_compiler.cc:627) dnn != nullptr

What jax/jaxlib version are you using?
jax 0.3.25
Which accelerator(s) are you using?
GPU
Additional system info
Python 3.9.16
NVIDIA GPU info
GPU: Tesla T4 on Colab

This typically means you've installed the jaxlib GPU wheel for the wrong CUDA version. Colab comes with a compatible JAX version pre-installed, so if you reset your runtime JAX should work out-of-the-box. That said, if you want to update you should be sure to use the cuda11_cudnn82 version of jaxlib (see https://github.com/google/jax#pip-installation-gpu-cuda for installation instructions).

I am also having the exact same issue with any jax version newer than 0.3.13, using a 187Gb GPU, and having tried all CUDA compatible sub-versions of JAX and JAXLIB with my CUDA version. Would help if there is any solution to this issue. (note I have this error whenever I try to create a jax object, jax numpy array even of dimension 1x1)

Hey, any solution to this?


Pipeline producer overflowed

Hi
As an experiment, I tried running the beta UR ROS2 driver on an Nvidia Xavier AGX (ARM processor), both in a docker container as well as standalone. In both cases, I get a runtime warning that "no realtime capabilities found", and then once the external node on the robot starts up, I get an alternating " Pipeline producer overflowed!" from line 412 of Universal_Robots_Client_Library/include/ur_client_library/comm/pipeline.h followed by an attempt to reconnect, and then the overflow and so on.
Is this the expected behavior when not running with a real time kernel? In the absence of installing a realtime kernel is there a setting that can be set? Or does this not have anything to do with the realtime performance.
I assume this is a client library issue and not associated with the ROS2 driver itself, although I did note that it seemed like jointstates and io states were being published. The JointStateTrajectory controller was publishing commands, but the robot wasn't moving.
This was with the master branch of the client library
Thanks
bb

This is indeed a problem with the ROS2 driver.
The client library stores packages received from the robot inside a queue which has to be emptied (consumed) by a second party. If the queue fills up without being emptied, the mentioned warning is printed.
It is the driver's job to empty the queue, which should happen here. I'll close this, as it looks like a ROS2 driver issue. Please open an issue inside the ROS2 driver repo linking to this issue. If any news concerning the library come up hunting this down, feel free to comment or reopen this one.

Thanks. Posted on the ROS2 driver page as you suggested.
bb
On Sat, May 15, 2021 at 4:00 PM Felix Exner @.***>
wrote:

This is indeed a problem with the ROS2 driver.
The client library stores packages received from the robot inside a queue
which has to be emptied (consumed) by a second party. If the queue fills up
without being emptied, the mentioned warning is printed.
It is the driver's job to empty the queue, which should happen here
https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/blob/5f49e74741c809a2568ea839326cf4026b1c847f/ur_robot_driver/src/hardware_interface.cpp#L405.
I'll close this, as it looks like a ROS2 driver issue. Please open an issue
inside the ROS2 driver repo linking to this issue. If any news concerning
the library come up hunting this down, feel free to comment or reopen this
one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/UniversalRobots/Universal_Robots_Client_Library/issues/59#issuecomment-841716704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWPS2WESTB7YTPE6JHDGFLTN3HHDANCNFSM44BALXYQ
.

For reference: The ROS2 driver issue is here


License please?

Hi,
great job on web3t,
what is the license of this repo?

MIT License
https://github.com/ethnamed/web3t/blob/master/LICENSE


y_loc and y_scale should be on the same device as y_hat

Issue will occur when using loss=DistributionLoss(distribution='Poisson') on a GPU machine. The reason is that the variables are not on the same device.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry, I did not go through the guidelines. I have not used the nbdev
before. Do I need to do anything for now? Or I can leave it as is?
Kin @.***>于2023年6月15日 周四17:14写道：

Hey @FCMeng https://github.com/FCMeng,
Thanks a lot for catching this bug and solving it.
I replicated your contribution in this #667
https://github.com/Nixtla/neuralforecast/pull/667
NeuralForecast is constructed using nbdev. To contribute, you must modify
the nbs/common.base_windows.ipynb notebook that automatically creates
neuralforecast/common/_base_windows.py. Here is the contributing guide
https://github.com/Nixtla/neuralforecast/blob/main/CONTRIBUTING.md.
—
Reply to this email directly, view it on GitHub
https://github.com/Nixtla/neuralforecast/pull/666#issuecomment-1593731986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATY5MCEWIMMAFW7NWG5ERGTXLN3JXANCNFSM6AAAAAAZIJC6IQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Fanchen Meng
Now affiliated at: CFN, Brookhaven National Lab
Used to be: GTA, Department of P&A, Clemson University

Sorry, I did not go through the guidelines. I have not used the nbdev before. Do I need to do anything for now? Or I can leave it as is? Kin @.>于2023年6月15日 周四17:14写道：
Hey @FCMeng https://github.com/FCMeng, Thanks a lot for catching this bug and solving it. I replicated your contribution in this #667 <#667> NeuralForecast is constructed using nbdev. To contribute, you must modify the nbs/common.base_windows.ipynb notebook that automatically creates neuralforecast/common/_base_windows.py. Here is the contributing guide https://github.com/Nixtla/neuralforecast/blob/main/CONTRIBUTING.md. — Reply to this email directly, view it on GitHub <#666 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATY5MCEWIMMAFW7NWG5ERGTXLN3JXANCNFSM6AAAAAAZIJC6IQ . You are receiving this because you were mentioned.Message ID: @.>
-- Fanchen Meng Now affiliated at: CFN, Brookhaven National Lab Used to be: GTA, Department of P&A, Clemson University

I fixed the PR in https://github.com/Nixtla/neuralforecast/pull/667, but stopped the PR for you to take merit on this one.
It is fairly simple to use nbdev.

Hi @FCMeng, thank you for finding the error and contributing to the library! Also thanks for using nbdev, the file looks good!
There are a couple more details that are missing to merge your PR; here are the steps:

Sign the CLA (you can use the button in the conversation above).
run nbdev_export to export the changes to the neuralforecast/ library. You should see that the neuralforecast/common/_base_windows.py will change.
Clean the notebooks: first run nbdev_clean --clear_all and then git checkout nbs/examples.
Push your changes again.

Thank you again for contributing!

I thought I signed it, no? It says "You have agreed to the CLA for Nixtla/neuralforecast" when I go to the signing page again.

Perfect. The issue is you are using two different accounts. But don't worry, just write:
"I hereby sign the CLA" in one comment, and that would be enough.

I hereby sign the CLA.
I am working on a old computer with an old account I think. Sorry about the confusion.

We just merged the PR; thanks for contributing!
We have several issues opened with the help wanted label if you want to make more changes!


Add Bicep version requirements to bicepconfig.json to ensure build reproducibility

If you're looking to ensure reproducible builds, it's important to make sure you're using a consistent version of tools locally and on build systems.
As a user, I should able to set something like the following in my bicepconfig:
{
  "bicepVersion": "v0.22.6"
}

If I'm using AzureCLI then the expectation is that the install process will be able to read this file and install the correct version - meaning that my CI & CD systems (as well as developers working locally) will get the exact same validation and produce the exact same JSON output.
If I use Bicep CLI manually, then the build command should fail to compile if a strict requirement has been added to the bicepconfig.

It would also be useful to support some sort of wildcard syntax (e.g. v0.*.* -> any release where the major version is 0, or v0.22.* -> any release where the major & minor versions are 0 & 22).
This is somewhat related to #12202 - basically the end goal is that for users who want it, the Bicep build is 100% reproducible (including same warnings/errors).
Other notes:

Suggestion from @alex-frankel. If we allow users to specify a "minimum version" for compatibility, we can use this for validation - e.g. blocking functions or behavioral changes that were introduced after the minimum version.

Would be nice also if there is some capability where I could have several bicep CLI versions installed/available on the machine and bicepconfig.json to be able to pick the correct version to use. That could allow side by side usage when doing CI/CD. It is also useful for troubleshooting scenarios where you can test if the bug is present in older version than the current.

Also maximum version would be useful in case you encounter some breaking change that prevents you from using the latest version.

If we are going to allow for version ranges, we could consider the npm version range syntax

https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept
Or the nuget version range syntax
https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges

If we are considering pulling using OCI definition or ORAS  (using container registries) we should also consider support for pulling by tag, the most common tag would be latest but in the future we may want to also support LTS , in the design we could only allow pulling via defined tags or could allow for any tag. We may want to consider differentiating between version range syntax and tags-- this may be simpler if we only support known enums


jade => jade-legacy

jade legacy is jade with security patches.
https://github.com/jnordberg/jade-legacy
Upgrading this would help us removing the npm shrinkwrap from OC 🎉

^ Snyk vulnerabilities check on each PR! 💘 this /cc @mattiaerre @nickbalestra


Can this only activate 365? Or can all series be activated?

Can this only activate 365? Or can all series be activated?
I hope the more authors, the better, looking forward to it

Ohook activation method can activate all kinds of Office versions on Windows 8 and higher and their Server equivalent except Office 2010 and Office UWP apps.

Ohook activation method can activate all kinds of Office versions on Windows 8 and higher and their Server equivalent except Office 2010 and Office UWP apps.
That's great, thank you for your answer

Readme.md only lists blank keys for O365HomePrem and O365ProPlus.
To activate other Office skus, just find a blocked key that belongs to the SKU you want to use.
The application will be activated with that key and the function of this patch.

To activate other Office skus, just find a blocked key that belongs to the SKU you want to use.

You can find the keys here https://massgrave.dev/ohook.html#Supported_Products


Canonical form

Codecov Report

Merging #68 into 0.6.6-release will increase coverage by 0.10%.
The diff coverage is 99.48%.

@@                Coverage Diff                @@
##           0.6.6-release      #68      +/-   ##
=================================================
+ Coverage          96.55%   96.66%   +0.10%
=================================================
  Files                 37       37
  Lines               5866     5999     +133
=================================================
+ Hits                5664     5799     +135
+ Misses               202      200       -2

Impacted Files
Coverage Δ

BezierKit/Library/BezierCurve.swift
100.00% <ø> (ø)

BezierKit/Library/BezierCurve+Intersection.swift
96.26% <98.14%> (+1.57%)
:arrow_up:

BezierKit/BezierKitTests/BezierCurveTests.swift
100.00% <100.00%> (ø)

BezierKit/BezierKitTests/CubicCurveTests.swift
100.00% <100.00%> (ø)

BezierKit/BezierKitTests/LineSegmentTests.swift
99.45% <100.00%> (ø)

BezierKit/BezierKitTests/UtilsTests.swift
100.00% <100.00%> (ø)

BezierKit/Library/CubicCurve.swift
100.00% <100.00%> (ø)

BezierKit/Library/QuadraticCurve.swift
100.00% <100.00%> (ø)

BezierKit/Library/Utils.swift
98.70% <100.00%> (-0.02%)
: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 cb763f8...dcaf615. Read the comment docs.


test e2e comment

Signed-off-by: zhy76<EMAIL_ADDRESS>
Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

/test all

/test run

/test run

/test run


Fix #721 Passing a global dict object without channel prop can cause issues among requests

This pull request resolves #721
Category (place an x in each of the [ ])

[x] slack_bolt.App and/or its core components
[x] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Adapters in slack_bolt.adapter
[ ] Document pages under /docs
[ ] Others

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've run ./scripts/install_all_and_run_tests.sh after making the changes.

@WilliamBergamin Thanks for your review! Indeed, using a shallow copy works as of today but for safety with any future changes, I prefer a deep copy this time.


API v3 and Python 3

Moved to the Have I Been Pwned v3 API, which does require an API-key for some of its actions. For example you must private an API-key to check if an account has been breached. With these commits you can provide the API-key either through the --api_key command line argument or set it in the HIBP_API_KEY environment variable.
Have also adjusted code for Python 3, mostly by using print('abc') instead of print abc.
The code has also been slightly formatted. Some adjustments to reported errors. There are no actual adjustments to the --passwd command line argument.

Pushed some changes based on your review @lucifercr07.

Would you also like to publish v3 of this on pip ? Please add yourself as co-author for module.


Upcasters not autoconfigured when using Spring Boot Autoconfiguration

When defining Upcasters in the application context, they are not automatically picked up by the autoconfigured Event Store.

Resolved in 12b4946, thus closing.


THORN-2413: thorntail.https.port default port is 8443

Motivation
The documentation is describing the default port as being 8483. However, the documentation has to reflect the action default https port.
Modifications
A simple change in the documentation from 8483 -> 8443.
Result
The documentation will now correctly describe the default port as 8443.

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you created a JIRA and used it in the commit message?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

I wonder why I didn't notice this PR when submitting #1294 :-/ Thanks for the report, though!


Issue #484: Changing the base OS of mngmnt network container

Signed-off-by: shubhangi_srivastava<EMAIL_ADDRESS>

Ansible lint changes are already done


MINOR: Add raft resigned state metric name

More detailed description of your change

Add resigned state metric
Update doc for raft state metrics

Summary of testing strategy (including rationale)
QA
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang @hachikuji , Hello, PTAL.


Access the event id from a binary_sensor.*_occupancy state change

I would like to access the event_id so I can build an image URL.
I am triggering now on the state change of binary_sensor.*_occupancy from off to on.
But after that I am not able to access the event_id (Or maybe I am overlooking things...).
Is this a new feature?
Am I overlooking things?
Or is it a bug?

We recommend using the MQTT topic for this, the binary sensor / frigate doesn't have this info and I think it would be quite difficult especially in cases where multiple objects enter at the same time and also for different zone binary sensors.
If you just want an image you can use /api/<camera>/<label>/thumbnail.jpg

I'll try that. But I thought I was doing /api///snapshot.jpg and that lagged just one event behind. I'll report back if this still happens

Unfortenately the /api/<camera>/<label>/snapshot.jpg lags one event behind.

Just tested with /api/<camera>/<label>/thumbnail.jpg that also lags one event behind.

You likely need to give it some delay, it takes time after the object is first detected before a snapshot / thumbnail is saved. But it will return a snapshot / thumbnail for in progress events. The same would happen if trying to get the thumbnail via event id
In any case, if you want granular control using MQTT topics is the way to go.


misdirected link at end of engine/swarm/how-swarm-mode-works/services.md page

In the "Learn more" section at the end of the engine/swarm/how-swarm-mode-works/services.md page
it mentions:

"Read about how swarm mode nodes work."
with the word "nodes" as a link.
Unfortunately it links back to the services.md page, not the nodes.md page.

I can make a pull request with a fix if desired. Let me know: peter at mentad dot com

@workybee Would love a pull request! :) Sent a note.

Fixed in c03bb7f90c68a067a435720db0174db4378cfb98


MGMT-2330 Adapt logs download to new API

New cluster/host states were added to swagger.
Depends on:

[ ] #244 Update API

Please make sure that if u deployed to prod while AI is still old, that we dont break anything

New API changes separated to #244.
Merging of log-related changes is blocked until backend implementation reaches production.


Piwik plugin doesn't work

Hello,
I'm running Matomo on Nginx, and I've spent many hours investigating the issue, but no luck.
I'm using NC v13. Matomo is running fine, but the tracker doesn't work at all.
I've entered the Site ID, and the tracking url in NC settings: //abc.mydomain.com:8443/ .
Need help.

WARNING: Bug reports which don't use this template will be closed immediately!


⚠ Samsung has degraded performance

In dba502a, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2341 ms

Resolved: Samsung performance has improved in c11500d.


Honour DEPTH_TO configuration value

Credit @antchan2

The CI error looks unrelated to this change.

this is a more serious problem. I use a clone of ConfigManager class in HeaderManager, so the custom config was not affected on the generated TOC.

Is a fix for that planned right now?

I already published the fix as beta. Can you check again?

Beta branch changes seem to be working. Thank you.


Add postman import spec

This PR focuses on having the Postman Collection import functionality. The following is how one can use this functionality:
Flags

Flag
Values
Description

-t/--type
openapi, postman
Pick which API spec to import

-o/--output

Select the directory to output the generated posting requests and variables. If this isn't supplied then the directories and request files will be created where the spec_file is located.

Usage:
posting -t postman postman.collection.json

posting -t postman -o requests postman.collection.json

I wrote a test for it but I am not sure how to include it in the test workflow, the test passes when I run
uv run pytest -d tests/test_postman_import.py

NOTE: I have tested it with Postman API Collection and my company's postman collection, seems to all work.

Thanks for this very important feature! I'm on a break at the moment but will try to take this for a spin within the next couple of weeks.

Pushed a fix for a crash I got when I downloaded a sample Postman collection - PostmanCollection.info and PostmanCollection.variable were optional.

Pushed a fix for a crash I got when I downloaded a sample Postman collection - PostmanCollection.info and PostmanCollection.variable were optional.
Also from testing it seems like the directory structure is not being respected?

Sorry been quite busy lately, will work on this when I get time


Remove temp file after successful Store write and not only in case of…

… an error.
I realised that the write method is not cleaning up the temp files after a successful write and only in the error branch. I added the fs.unlink(tmpFile) to make sure that files do not pile up in the temp directory.

Thank you @rockhouse !


Add schema for 3D rotations.

This looks good.  Eventually, we'll probably want to include a really explicit definition of the math, something like:
http://mathworld.wolfram.com/EulerAngles.html
But that shouldn't hold up the PR.  Nothing else, other than the polynomial stuff, really has that yet, anyway...


Strides of transposes differ between CUDA target and Numpy

[X] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[X] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Spotted whilst working on a fix for #4832 - there is a further deviation from Numpy in the strides of transposes of views. Example:
from numba import cuda
import numpy as np

a = np.arange(120).reshape((10, 12))
a_view = a[::2, ::2]
a_view_t = a_view.T

d_a = cuda.to_device(a)
d_a_view = d_a[::2, ::2]
d_a_view_t = d_a_view.T

h_a_view_t = d_a_view_t.copy_to_host()

print(a_view_t)
print(h_a_view_t)

print(d_a_view.strides)
print(d_a_view_t.strides)

assert np.all(a_view_t == h_a_view_t)

prints:
[[  0  24  48  72  96]
 [  2  26  50  74  98]
 [  4  28  52  76 100]
 [  6  30  54  78 102]
 [  8  32  56  80 104]
 [ 10  34  58  82 106]]
[[  0  24  48  72  96]
 [  2  26  50  74  98]
 [  4  28  52  76 100]
 [  6  30  54  78 102]
 [  8  32  56  80 104]
 [ 10  34  58  82 106]]
(192, 16)
(40, 8)

with no assertion - i.e. the transpose is correctly computed, but the result has different strides to Numpy. This could fall into the "half-bug" category as @stuartarchibald mentioned for #4832 in that it's not necessarily incorrect, but a little surprising. It might be nice as a user to be able to choose whether the transpose kernel will run and create a new array, or whether a new array pointing at the same data with modified strides is returned.

I see the duplicate tag, but I didn't see a similar issue - can you point me to the issue this one duplicates please?

I was going for https://github.com/numba/numba/issues/4832, which seems like it's part of the same problem, feel free to remove the tag if they are independent.

I think they're independent - even after fixing #4832 to make device_array_like create contiguous arrays (in #4975), the transposes have different shape and this issue still persists.
I don't think I have the permissions to edit labels on PRs in this repo - could you remove the label please? (or allow me the permission to do so :-) )

Done!


Let user choose from standardized linguistic features

http://linguistics-ontology.org/info/about - server seems down at the moment :(

Revisit if this version is workable https://triplydb.com/none/gold/, or if we add missing terms from Clarin concept registry.


Fixes #634: Revert "Run Fedora GHA test jobs with -j12 threads again" and use -j6 instead

Reverts and modifies skupperproject/skupper-router#563

Codecov Report
Base: 27.44% // Head: 27.44% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (95e931a) compared to base (afd6aa1).
 Consider uploading reports for the commit 378b577 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #793      +/-   ##
==========================================
- Coverage   27.44%   27.44%   -0.01%
==========================================
  Files         132      132
  Lines       31625    31625
  Branches     5058     5058
==========================================
- Hits         8681     8679       -2
  Misses      21841    21841
- Partials     1103     1105       +2

Flag
Coverage Δ

unittests
27.44% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/router_core/address_watch.c
88.50% <0.00%> (-1.15%)
:arrow_down:

src/router_core/route_tables.c
16.16% <0.00%> (-0.28%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


replace Sirupsen to sirupsen for compile

#8
just for compile

@tiny1990
what's version of your go that used for compile.
and can you try compile again after clear up go mod file($GOPATH/pkg)
by the way, i haven't come across this compile error.

switch to github.com/googleapis/gnostic v0.3.1 or v0.4.0 should be able to fix the compile error.  I was able to run  docker run -it --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:1.13 make with either version.

This should be fixed by PR #12.  closed


fix(link): fix link typescript declaration file

What You're Solving

Fixes the TypeScript declaration file for the Link component.

This fixes the appearances reference described in the docs, eg. Link.appearances.subtle

Design Decisions
The current declaration file does not include a reference to appearances in the Link export and should have the Component updated to FunctionComponent to allow children props.
How to Verify
Import Link into a .tsx file and use with a React component. TypeScript should no longer throw the following error:
Type '{ children: Element; appearance: any; }' is not assignable to type 'IntrinsicAttributes & LinkProps'.
  Property 'children' does not exist on type 'IntrinsicAttributes & LinkProps'.ts(2322)```

For the appearances, I think the best that TS would infer is {default: string, subtle: string}. Might be better to just do:
type Appearances = { default: 'default', subtle: 'subtle' };
export type Appearance = keyof Appearances;
export const appearances: Appearances;


Add optional custom UFO out path appended names and extensions

Closes #10
Adds two new command line options that are not mutually exclusive:

--out-name: takes a string argument that is appended to the base UFO dir path name(s) before the .ufo extension

--out-name _FMT ==> somepath_FMT.ufo

--out-ext: takes a string argument that replaces the .ufo extension on the UFO dir paths.

--out-ext FMT.ufo ==> somepath.FMT.ufo

The executable accepts multiple UFO directory path requests and supports parallel execution when multiple paths are requested.  You want to use multiple dir path args when you need to process multiple UFO dirs with this tool.  Multiple dir processing limits full base dir name replacements from the command line.  This approach allows a user to modify parts of the inpath to support writes on different paths as an alternative to the in-place write default.

@madig Useful? Best approach?

Seems useful to me.  Let's go with this for now.  We can change it if there is a better way to do it.


[BEAM-6952]Fixes the version number for concat compressed files fix

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @mxm @dlesco

Run Python PreCommit

Run Python PreCommit


UWM Theme / Branding

Opening a PR here to document the UWM theme changes in the application.
Fixes #1
Homepage

Search Results

Show Page

Made the application title black. Merging PR now.


[8.x] Add hasSlot Blade conditional tag

This PR aims to implement a new hasSlot conditional tag for Blade components. I was looking for a smarter way to check if a slot is provided and tried to implement it. Please see below for some important considerations.

@hasSlot('title')
    {{ $title }}
@endif

    {{ $slot }}

Considerations

I used max(0, $this->currentComponent()) because on using "standard" components (class or anonymous) $this->currentComponent() would return -1, but on tests with $factory->make('component') it would return the correct index, therefore had to write this little check.
This currently does not work if you use nested components. For example, if inside alert.blade.php you put another component like <x-small-tag>{{ $title }}</x-small-tag>, hasSlot would not detect the given slot because variables like $this->slots will contain the child data. I don't much about the flow here, sorry.
2.1. About that, maybe hasSlot could be moved where you can access the actual $slots of the component and not inside the CompilesConditionals?
Is this actually better than just checking for the variable existance with @isset? Because I tried to replace all the hasSlot method with just the following code and it works with nested components too, but it would return "true" also for variables not declared within a slot (e.g. from the view or global variables), so I don't know...

protected function compileHasSlot($name)
{
    $slotName = trim($this->stripParentheses($name), "'");

    return "<?php if (isset(\${$slotName})): ?>";
}

I don't see a need for this at the moment. You can just use @isset directly:


iOS: Fix AirPods routing when Play and Record category is used.

So after the changes merged on https://github.com/godotengine/godot/pull/89006, the Play and Record audio session category is almost perfect on iOS (this means normal volume both on speakers and headphones!). However, I decided to try it out with my AirPods and, surprisingly, Godot didn't change the route to them. :(
This pull request does what SDL does, it adds two extra options when Play and Record is used to fix the issue:
AVAudioSessionCategoryOptionAllowBluetoothA2DP
AVAudioSessionCategoryOptionAllowAirPlay

Thanks!


will it work again?

Hey, is it possible that this project will work again soon?
Kind regards

If toofake doesn‘t work for you, you can use beunblurred.co, works for me (german number)

thank you, but sadly it doesn’t work for me. How did you manage to make it work?


fix(extract): able to extract from a object a list of attribute. allow to use regex.

:tada: This PR is included in version 2.5.1 :tada:
The release is available on:

v2.5.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0-beta.1 :tada:
The release is available on:

v2.6.0-beta.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0-beta.2 :tada:
The release is available on:

v2.6.0-beta.2
GitHub release

Your semantic-release bot :package::rocket:


Error while bootstrapping windows node

Description
Error while bootstrapping windows node via winrm method
Chef Version
$ chef -v
Chef Development Kit Version: 0.14.25
chef-client version: 12.10.24
berks version: 4.3.3
kitchen version: 1.8.0
Platform Version
Windows 8.1
Replication Case
$ chef gem list | grep windows
knife-windows (1.4.1)
windows-api (0.4.4)
windows-pr (1.2.4)
Please fire the below command to replicate the issue:
chef exec knife bootstrap windows winrm -N <IP_ADDRESS> -r 'role[production]' -x Administrator -P 'XXXXXXXX' -p 5985 -VV
Client Output
INFO: Using configuration from C:/Users/kolge/learn-chef/chef-repo/.chef/knife.rb
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key ca_trust_file and found value
DEBUG: Looking for key winrm_user and found value Administrator
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key winrm_transport and found value plaintext
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key winrm_password and found value XXXXXXX
DEBUG: Looking for key winrm_port and found value 5985
DEBUG: Looking for key session_timeout and found value 30
DEBUG: Looking for key session_timeout and found value 30
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key winrm_transport and found value plaintext
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key winrm_transport and found value plaintext
DEBUG: Looking for key winrm_authentication_protocol and found value negotiate
DEBUG: Looking for key ca_trust_file and found value
DEBUG: Looking for key ssl_peer_fingerprint and found value
DEBUG: Looking for key ca_trust_file and found value
C:/Users/kolge/AppData/Local/chefdk/gem/ruby/2.1.0/gems/knife-windows-1.4.1/lib/chef/knife/winrm_knife_base.rb:69:in resolve_target_nodes': undefined method split' for nil:NilClass (NoMethodError)
from C:/Users/kolge/AppData/Local/chefdk/gem/ruby/2.1.0/gems/knife-windows-1.4.1/lib/chef/knife/winrm_knife_base.rb:62:in configure_session'         from C:/Users/kolge/AppData/Local/chefdk/gem/ruby/2.1.0/gems/knife-windows-1.4.1/lib/chef/knife/bootstrap_windows_winrm.rb:51:in run'
from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/lib/chef/knife.rb:421:in block in run_with_pretty_exceptions'         from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/lib/chef/local_mode.rb:44:in with_server_connectivity'
from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/lib/chef/knife.rb:420:in run_with_pretty_exceptions'         from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/lib/chef/knife.rb:219:in run'
from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/lib/chef/application/knife.rb:148:in run'         from C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.24-universal-mingw32/bin/knife:25:in <top (required)>'
from C:/opscode/chefdk/bin/knife:61:in load'         from C:/opscode/chefdk/bin/knife:61:in '
The relevant output of the chef-client run or a link to a gist of the entire run, if there is one.
The debug output (chef-client -l debug) may be useful, but please link to a gist, or truncate it.
Stacktrace
NA
NOTE: CHEF CLIENT BUGS ONLY
This issue tracker is for the code contained within this repo -- chef-client, base knife functionality (not
plugins), chef-apply, chef-solo, chef-client -z, etc.

Server issues
ChefDK issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

Just walked into the same problem, so any clues and hints would be gratefully received.  Only difference in my case is trying to bootstrap Windows 10, and WinRM is enabled/validated by 'knife wsman test'

you need to pass the address as the argument:
you have:
chef exec knife bootstrap windows winrm -N <IP_ADDRESS> -r 'role[production]' -x Administrator -P 'XXXXXXXX' -p 5985 -VV

you need:
chef exec knife bootstrap windows winrm <IP_ADDRESS> -N <IP_ADDRESS> -r 'role[production]' -x Administrator -P 'XXXXXXXX' -p 5985 -VV

although you're probably mixed up the node name argument and the server to login to -- you probably want to give it a more useful node name than its IP address...

knife-windows could have a more useful error message here when the host argument is missing, but this is the wrong repo to file that ticket...
http://github.com/chef/knife-windows/issues/new


Mapping with  or "|" doesn't work

Please complete the following information:

OS or distro: Linux Mint
neoray version: 0.1.0

Describe the bug
Any mapping that contains <bar> (VimScript) or "|" (Lua) doesn't work. I use <leader>| to split the current window vertically.
I use a keyboard with Brazilian layout, don't know if that is causing the issue.
Steps to reproduce
Just create any mapping with a vertical bar on the left-hand side, as in the examples below.
Your neoray config in init.vim (Only the part that concerns neoray!)
nnoremap <Leader><Bar> <C-W>v

" OR:

lua <<EOF
vim.api.nvim_set_keymap('n', '|', '<c-w>v', { noremap = true })
EOF

Crash log if available (may be generated by neoray after crash)
Debug output (you can generate starting neoray with --verbose option)

1- Open an empty file, press  and press bar key. If it prints something send me it.
2- I looked brazilian layout and bar key is above the windows key, are you pressing Ctrl-Alt or Altgr or alone for typing bar?

If I enter insert mode and press <c-v>|, it prints <S-Bar>. In the terminal (kitty and terminator), it just prints |.
Yes, it's above the windows key, but behaves just like any other key. To type a vertical bar, I press Shift+/

I checked and this issue happens also in neovide: it also prints <S-Bar>. It doesn't happen in nvui or neovim-gtk, which are UIs I've used recently.

I've tried the latest release and it works now after the fix. Thanks for looking into this!


App download - Tab does not close after tapping "x" on download popup

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:  1.4.51-2
Reproducible in staging?: y
Reproducible in production?: y
Issue found when executing PR: https://github.com/Expensify/App/pull/38032
Issue reported by: Applause - Internal Team
Action Performed:

Access staging.new.expensify.com on Safari (PR asks for Safari) or on MAC Desktop app
Sign into a valid account
Go to Settings >> About >> App download links >> macOS
Close the download prompt

Expected Result:
According to the PR, the new tab should close. The tab closes on mweb and on the iOS app
Actual Result:
The tab does not close after download prompt is closed on mac browser and on mac desktop app
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/f8f20d9a-75b8-49f8-a335-9966b074060e
View all open jobs on GitHub

@kadiealexander I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

That's not the case i.e. the new tab is closing for me.
https://github.com/Expensify/App/assets/158435970/e4dc3ab1-053f-43aa-89ac-4e578a9818ba

Yeah I can't repro this either, closing.
https://github.com/Expensify/App/assets/59587260/fa01f018-4a4d-4ee7-82e0-177dee793a9a


[Lake] Fix show create table bug

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Problem Summary(Required) ：

Use starrocks as engine name.
Use GsonPostProcessable to process TableProperty deserialization.

[FE PR Coverage check]
:heart_eyes: pass : 11 / 12 (91.67%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
5
6
83.33%

:large_blue_circle:
com/starrocks/catalog/TableProperty.java
6
6
100.00%


SQL CREATE TABLE command does not work when destination is S3

Bug
SQL CREATE TABLE command fails when destination is S3
Describe the problem
When simply defining a table without populating it, spark throws an error when attempting to write to an s3 bucket.  The same command works fine when writing to the local filesystem.  Also, I am able to write to s3 without trouble when doing a CREATE TABLE AS... command.  I am not sure if this is the intended behavior or a bug.  I searched both open and closed issues and wasn't able to find one that matched the error I encountered, so I am creating a bug report.
Steps to reproduce
A command such as this one:
CREATE OR REPLACE TABLE delta.`s3a://<bucket_name>/people10m' (
      id INT,
      firstName STRING,
      middleName STRING,
      lastName STRING,
      gender STRING,
      birthDate TIMESTAMP,
      ssn STRING,
      salary INT
    ) USING DELTA;

fails, whereas the following command does work:
CREATE OR REPLACE TABLE default.people10m (
      id INT,
      firstName STRING,
      middleName STRING,
      lastName STRING,
      gender STRING,
      birthDate TIMESTAMP,
      ssn STRING,
      salary INT
    ) USING DELTA;

As does this one:
CREATE TABLE delta.`s3a://<bucket_name>/delta-table` USING DELTA AS SELECT col1 as id FROM VALUES 0,1,2,3,4;"
Observed results
Syntax error at or near '`': extra input '`'(line 2, pos 36)

== SQL ==

    CREATE OR REPLACE TABLE delta.`s3a://<bucket_name>/people10m' (...

Expected results
No Error
Environment information

Delta Lake version: 2.3
Spark version: 3.3.2
Scala version: using PySpark (Python 3.10.11)

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[x] No. I cannot contribute a bug fix at this time.

Nevermind, saw and fixed the syntax error.  My apologies.


K3S Version Reporting Incorrect

Describe the bug
When running kubectl get nodes the master node is not reporting the correct kubernetes version.
To Reproduce
Starting with a multi node cluster install the master version with  v1.14.5-k3s.1 using the following systemd file.
[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
After=network-online.target

[Service]
Type=notify
EnvironmentFile=/etc/systemd/system/k3s.service.env
ExecStartPre=-/sbin/modprobe br_netfilter
ExecStartPre=-/sbin/modprobe overlay
ExecStart=/usr/local/bin/k3s \
    server --write-kubeconfig-mode 644 \
    --no-deploy traefik \
    --no-deploy=servicelb \
    --disable-agent \
KillMode=process
Delegate=yes
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
TimeoutStartSec=0
Restart=always

[Install]
WantedBy=multi-user.target

Then stop the master service using:
sudo systemctl stop k3s

Get the arm64 version from git releases for v0.9.1 and copy it over top of the
/usr/local/bin/k3s

Then start the k3s service, it still reports
kube-master   NotReady   <none>   138d   v1.14.5-k3s.1
Rather than  v1.15.4-k3s.1
Expected behavior
Correct reporting of the kubernetes version.

I just updated to 1.0 and this is still an issue.  Can someone point me in the general direction to look for the problem?  I'm more than willing to attempt a fix.

The --disable-agent flag should be avoided unless you are a developer and understand the repercussions. Please try removing that flag and restarting the k3s process.

Also, the line continuation on that service file will probably have unintended consequences for some versions of systemd, might be worth re-running the install script.

Is there a better configuration options to ensure the master doesn't join as a node that can have pods scheduled on it?  It's easy enough to cordon it off, but I'm using that with the intention of forcing the master to only be a master rather than a combined master/worker.

If you start the server with the no schedule taint I think that should have the desired effect, essentially cordoning it on start:
--kubelet-arg register-with-taints=kubernetes.io/unschedulable:NoSchedule

I started the cluster with this:
--no-deploy=servicelb \
    --node-taint key=value:NoSchedule```

But it appears to not be working

kubectl get nodes -o json | jq '.items[].spec'
{
"podCIDR": "<IP_ADDRESS>/24",
"podCIDRs": [
"<IP_ADDRESS>/24"
]
}
{
"podCIDR": "<IP_ADDRESS>/24",
"podCIDRs": [
"<IP_ADDRESS>/24"
]
}
{
"podCIDR": "<IP_ADDRESS>/24",
"podCIDRs": [
"<IP_ADDRESS>/24"
]
}
{
"podCIDR": "<IP_ADDRESS>/24",
"podCIDRs": [
"<IP_ADDRESS>/24"
]
}```
This very much could be operator headspace and timing though.

Ah nm, it says right in the doc it can't be added later.


翻译错误

原文：Note that this is what webpack-dev-middleware, used by webpack-dev-server and many other packages, uses to mysteriously hide your files but continue serving them up to the browser!
我认为应该是webpack-dev-server依赖了webpack-dev-middleware
describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
[ ] Do not abandon your Pull Request: Stale Pull Requests.
Remove these instructions from your PR as they are for your eyes only.

谢谢


Lack of distanceFilter

I couldn't find distanceFilter so I've open a question https://stackoverflow.com/questions/51872946/distancefilter-disappeared-from-positionoptions. Then I saw that here: https://github.com/facebook/react-native/blob/e1577df1fd70049ce7f288f91f6e2b18d512ff4d/Libraries/Geolocation/RCTLocationObserver.m#L273 is the distanceFiler.
After adding it into the ts file watchPosistion starts to work properly accepting the distanceFilter prop.

Fixes #

This is not the proper way to contribute to these files.
As mentioned in the README in this directory:

Read This!
These files are not meant to be edited by hand.
If you need to make modifications, the respective files should be changed within the repository's top-level src directory.
Running jake LKG will then appropriately update the files in this directory.

And in the CONTRIBUTING.md:

Contributing lib.d.ts fixes
The library sources are in: src/lib
Library files in built/local/ are updated by running
jake

The files in lib/ are used to bootstrap compilation and usually do not need to be updated.
src/lib/dom.generated.d.ts and src/lib/webworker.generated.d.ts
These two files represent the DOM typings and are auto-generated. To make any modifications to them, please submit a PR to  https://github.com/Microsoft/TSJS-lib-generator

It looks like this is a React Native specific property? It's not listed in
https://developer.mozilla.org/en-US/docs/Web/API/PositionOptions or https://w3c.github.io/geolocation-api/


Navigation completely breaks if you switch pages while another is loading

Observed/problematic behavior
When you navigate between pages too fast navigation breaks completely. The url still changes in the browser navigation bar (and the 'selected page' thing also updates in the site navbar), but the page stays the same, see video below:
https://user-images.githubusercontent.com/44026893/210782359-26f58a18-e8ab-4576-8114-1e9ba07e8581.mov
Expected behavior
Navigation should work
Steps to reproduce
Click on a page, then while that page is loading click to another.
Other
The account settings navigation at the end did work, I just cut off the response since it might contain sensitive information.

I enabled source maps now, if you can repro, please open the JS console and copy the stack trace you see there.


Fix splitting of patterns

Now works for e.g. patterns="bash -c 'echo \"$USER\"'" -> 3 args
This came up when stubbing ssh

@jasonkarns I can confirm that this also fixes issues while stubbing yq and jq.


feat: expose loki retention-period config

Issue
Currently the cos-lite-bundle does not offer any way to configure Loki retention.
Solution
Charm loki-k8s-operator offers since few months ago a new config key named retention-period that allows to configure Loki to the specified retention and activates the compactor in Loki. It'd be great if we can expose this setting in the cos-lite-bundle.
Context
When deploying the bundle, an operator typically wants some retention policy for the logs, and as the bundle is currently there is no way to configure any.
Testing Instructions
Render the bundle with loki_retention_period=30.
Observe Loki configuration to contain these two settings:
retention_enabled: True

and in the limits_config there should be
retention_period: 30d

Adjusted ruff syntax
It was not in the scope of this PR but for the linter in the CI to work I fixed the ruff syntax, which now expects the keyword check after ruff and before the path. Let me know if you prefer I do that in a separate PR.

Close after discussing with @ca-scribner the goal of the bundle is showcase a light-weight COS deployment. I think nevertheless is very informative to have an example extra setting.


⚠ Bofrost.fr has degraded performance

In 8227e63, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 892 ms

Resolved: Bofrost.fr performance has improved in 230fdf0 after 6 minutes.


Add a wiki: The Infosphere, the Futurama Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://futurama.fandom.com
Link to destination (independent) wiki: https://theinfosphere.org

This has been added and will be released in v1.3.0


Handle the case where an iterable, or a Set or Map is used in array.from

This is my first PS PR so I hope it's okay. I've tried to avoid touching anything beyond the most basic syntax.

Fixes https://github.com/Financial-Times/polyfill-service/issues/420 ?

Could you add some tests for the feature?
I'd recommend looking at other Array.from polyfills which support iterators such as https://github.com/studio-b12/array-from

I don't know enough about the mechanics of array-like objects in ES6 but as long as the concerns raised in #420 are addressed and we add some tests for the cases that this polyfill seeks to cover, that's all fine with me.
Also - a lingering concern: are there any browsers that ship support for Set but not Array.from?  If not, this polyfill is pointless.

Also - a lingering concern: are there any browsers that ship support for Set but not Array.from? If not, this polyfill is pointless.

Mathias Bynens has explained a need for this in the past -- https://github.com/mathiasbynens/Array.from/issues/4#issuecomment-51221192

Chrome 44 has this issue, and it is the version of Chrome about to be shipped with Samsung's browser for GS6 and GS7.

What is the environment for tests can I use native Sets and Maps to test it?

The environment for tests is every browser that polyfill service supports.

The test authoring guidelines should hopefully explain everything -- https://cdn.polyfill.io/v2/docs/contributing#test-authoring-guidelines

Ahh I see, i'll look at 'Map' and 'Set' in this. Thanks Jake.

I am getting an error when I run the tests locally so I am relying on circle CI.

Got the tests running by running the service directly. It seems to me by reading the spec I shouldn't use write tests for Map and Set since that particular part is not testable in all browsers.

It's now checking for Map and Set in window as it seems some of the other tests are doing that too.

Tests are now passing, btw the tests on 'android 4.4.4' seem flakey.
I have seen tests for Promise and URL spontaneously fail.

One thing it does is to check that Iterators have a .next function before trying to b=polyfill because Safari 7/8 does not have this.
I tried to make it fall back to for (i of iterator) for that specific case, but that won't compile under uglify and doesn't work when transpiled.

That also wouldn't work for an endless iterator such as an iterator for even numbers.

Array.from isn't supposed to work on an endless iterable. It is expected to try to go forever.

Ok, this is good. With the tests, it's sensible to test for features that might not be supported, if those are not features we're trying to polyfill. The alternative is to make this polyfill depend on Map and Set but if they are only used in tests, that's hugely wasteful. So this approach is fine.

@AdaRoseEdwards, can you explain, what you if on arraylike.hasOwnProperty('next') === false inside parseIterable? It prevents working "fake" iterators (like ones defined inside es6-collections package). I'm not sure if was strict requirement or "just-in-case" condition. As far as I see, there is no test case defined to check exactly this.


School pc setup: Guest account disappears

When I create a guest account with school pc (or even WCD), the guest account disappears...
First login I can choose user or guest, next login only users is available.
We need this guest account for the youngest kids.
Can you help me out?

Can you explain what it is that you are trying to accomplish by using a guest account?

Hi
As I said, that account would be used by the youngest kids in our schools.
Van: Ed Gallagher<EMAIL_ADDRESS>Verzonden: maandag 20 augustus 2018 3:30
Aan: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>CC: Luk Van den Bossche<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Onderwerp: Re: [MicrosoftDocs/windows-itpro-docs] School pc setup: Guest account disappears (#1487)
Can you explain what it is that you are trying to accomplish by using a guest account?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-itpro-docs/issues/1487#issuecomment-414173638, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AogdjOmhmR1Jh7yHkpyPb1ZeO_ShN7qmks5uShD9gaJpZM4WB0Z4.

I understand that. My question is what are you trying to accomplish by doing that? What is the reasoning?

@bozzl Is there group policy interacting with Guest accounts on the local system?
The behavior sounds like it is matching the symptom.
Or interacting with members of Guest Users on the local system.

No gpo’s as a school pc setup or provisioning package starts from an usb-stick
Van: OftKilted<EMAIL_ADDRESS>Verzonden: maandag 20 augustus 2018 19:09
Aan: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>CC: Luk Van den Bossche<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Onderwerp: Re: [MicrosoftDocs/windows-itpro-docs] School pc setup: Guest account disappears (#1487)
@Bozzlhttps://github.com/Bozzl Is there group policy interacting with Guest accounts on the local system?
The behavior sounds like it is matching the symptom.
Or interacting with members of Guest Users on the local system.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-itpro-docs/issues/1487#issuecomment-414391694, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AogdjHY8j-N3p7xGs_PHrK9zf7dmiSSvks5uSu0tgaJpZM4WB0Z4.


pinch to zoom

Viewing an image where you need to use pinch to zoom gesture for more detailed view seems impossible.

Yep, this isn't ideal atm. sorry. It's on my todo-list...

There are two workarounds to support better zooming of images:

Make the underlying content non-scrollable:
.lity-active,
.lity-active body {
    overflow: hidden;
}

Use a plugin to allow zooming of the image, eg. jquery.panzoom
$(document).on('lity:ready', function(e, lightbox) {
    lightbox.find('img').panzoom();
});

.lity-active, .lity-active body {     overflow: hidden; }
Why is this not part of the default CSS ? It seems useful to remove scroll bars to allow more space for large (wide) images and to prevent scrolling issues with inline and iframe content on iOS mobile devices.

I might consider this for the next version. 👍

It disables background scrolling too, which seems to bother some people...


TDD Project

Highlights

[ ] Create a class called Solver
[ ] Create and implement the factorial method
[ ] Create a method called reverse
[ ] Write for all these necessary methods
[ ] Ensure linters pass

Below is an image of the test result

Issue raised by the previous reviewer has been resolved as evident in the images below
We have resolved this issue. This can be seen in the images below.
Testing fizzbuzz in solver_spec.rb

fizzbuzz and other methods in solver.rb

the test result

@Felix45 Thank you for reviewing and approving the PR


Jobs Run Only Once After Device Reboot

Hello,
I was able to run scheduled job. The problem is right after device reboot, the job only run  once.

waiting for device -
--------- beginning of main
--------- beginning of system
12-01 06:40:41.690  4014  4014 D ReactNative: ReactInstanceManager.ctor()
12-01 06:40:42.016  4014  4014 D ReactNative: ReactInstanceManager.createReactContextInBackground()
12-01 06:40:42.017  4014  4014 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundInner()
12-01 06:40:42.033  4014  4014 D ReactNative: ReactInstanceManager.onJSBundleLoadedFromServer()
12-01 06:40:42.034  4014  4014 D ReactNative: ReactInstanceManager.recreateReactContextInBackground()
12-01 06:40:42.034  4014  4014 D ReactNative: ReactInstanceManager.runCreateReactContextOnNewThread()
12-01 06:40:42.039  4014  4061 D ReactNative: ReactInstanceManager.createReactContext()
12-01 06:40:42.643  4014  4061 D ReactNative: Initializing React Xplat Bridge.
12-01 06:40:42.651  4014  4061 D ReactNative: Initializing React Xplat Bridge before initializeBridge
12-01 06:40:42.743  4014  4061 D ReactNative: Initializing React Xplat Bridge after initializeBridge
12-01 06:40:42.743  4014  4061 D ReactNative: CatalystInstanceImpl.runJSBundle()
12-01 06:40:42.756  4014  4102 D ReactNative: ReactInstanceManager.setupReactContext()
12-01 06:40:42.756  4014  4102 D ReactNative: CatalystInstanceImpl.initialize()
12-01 06:40:45.318  4014  4101 I ReactNativeJS: Exact started
12-01 06:40:45.356  4014  4101 I ReactNativeJS: Regular started
12-01 06:40:45.635  4014  4101 I ReactNativeJS: The job exactJobKey was successfully scheduled.
12-01 06:40:45.636  4014  4101 I ReactNativeJS: The job exactJobKey was successfully scheduled.

There's no more log after that.

Try setting exactJob to false

yes
also check app is battery optimized by OS.
Use this to check weather battery optimization is enabled ?
https://www.npmjs.com/package/react-native-disable-battery-optimizations-android


Filter work items by users not assigned to anyone

How about using nil as the value to get work items not assigned to no one. e.g., /workitems?filter[assignee]=nil

@baijum I'll rather use none instead of nil.


Cause kaleido to explicitly fail if no chromium:

Before we were letting choreographer handle it.

Hey Greg, this error will be more clean for users that they need to have chrome installed!

Not sure if it solves https://github.com/plotly/Kaleido/issues/223 but it may

While running jobs in Azure Databricks if Kaleido is installed during the job run, any plotly fig.show() will show the error message just added by this PR.
The only way to circumvent this is to set the rendering like this:
fig.show(renderer='databricks')

Again this error will not show if the notebooks in Azure databricks are run automatically, and may be due to how enviroment is handled by Databricks and not how Kaleido interacts with plotly.
Dropping this comment here because I know someone will pop their head soon...

Not sure how to circumvent this new requirement in a serverless compute on Azure Databricks...
It seems chromium cannot be access in those conditions and will always end up in error if trying to save plotly plots as static images.


Silence warnings

What I did
Run tests of a project depending on phony.
What happened
There were warnings from the phony dependency in the output:
/Users/lloeki/.gem/ruby/2.3.4/gems/phony-2.15.47/lib/phony/country_codes.rb:80: warning: assigned but unused variable - trunk

What I expected to happen and why
No warnings
Suggested cause and approach
This is because with a recent rake (>=11.0), ruby warnings are now on by default.
What do you think about fixing those warnings as well as running the test suite with ruby -w / $VERBOSE = true / t.warning = true ?

Hi @lloeki – sorry for the late response! When using rake, the test suite already runs with warnings on. As there are numerous warnings from used libraries, I must have missed the one from Phony. Thanks for the pointer! Not showing up anymore in the latest version. Also, thanks for the nice writeup 😊


Handling hyphen/minus inside param name

Hi everybody,
using squiggly in a spring-boot web app I got errors when I try to filter by fields that have a hyphen inside (e. g. test-name).
I know that it's a little bit out of standards have the hyphen in the param name but in my case, it's a customer's requirement.
I have the following configuration:
pom.xml
 <dependency>
      <groupId>com.github.bohnman</groupId>
      <artifactId>squiggly-filter-jackson</artifactId>
      <version>1.3.15</version>
 </dependency>

ExampleObject.java
public class ExampleObject {
    @JsonProperty("id")
    String id;

    @JsonProperty("area")
    String area;

    @JsonProperty("sub-area")
    String subArea;
}

Application.java
@SpringBootApplication
public class Application {

    @Bean
    public FilterRegistrationBean squigglyRequestFilter() {
        FilterRegistrationBean filter = new FilterRegistrationBean();
        filter.setFilter(new SquigglyRequestFilter());
        filter.setOrder(1);
        return filter;
    }

    public static void main(String[] args) throws Exception {
        ConfigurableApplicationContext context = SpringApplication.run(Application.class, args);

        Iterable<ObjectMapper> objectMappers = context.getBeansOfType(ObjectMapper.class)
            .values();

        Squiggly.init(objectMappers, new RequestSquigglyContextProvider() {
        });

        ObjectMapper objectMapper = Iterables.getFirst(objectMappers, null);

        // Enable Squiggly for Jackson message converter
        if (objectMapper != null) {
            for (MappingJackson2HttpMessageConverter converter : context.getBeansOfType(MappingJackson2HttpMessageConverter.class).values()) {
                converter.setObjectMapper(objectMapper);
            }
        }
    }

}

So, when I call the API with "fields" valorized as "area" or "sub*", everything works fine, but if I use "sub-area" I got the following error:

2019-02-04 17:48:33.264  WARN 19359 --- [nio-8080-exec-1] .m.m.a.ExceptionHandlerExceptionResolver : Resolved exception caused by Handler execution: org.springframework.http.converter.HttpMessageNotWritableException: Could not write JSON: line 1:3 mismatched input '-' expecting {, ','}; nested exception is com.fasterxml.jackson.databind.JsonMappingException: line 1:3 mismatched input '-' expecting {, ','} (through reference chain: java.util.ArrayList[0]->com.example.model.ExampleObject["id"])

Going through the process I noticed that the exception is generated by antlr:

org.antlr.v4.runtime.misc.ParseCancellationException: line 1:3 mismatched input '-' expecting {, ','}

Can anyone help me, please?
Thank you in advice

@bohnman the new version works perfectly! Thank you very much!


Xdebug 3 & PHP 8.1 - Could not connect to debugging client

Version of Den
1.0.0-beta.13
Image
den-php-fpm-magento2-debug:8.1-node12
Describe the bug
Trying to run Xdebug with PHP 8.1 results in the log:
NOTICE: PHP message: Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:9003 (fallback through xdebug.client_host/xdebug.client_port).
Debugging through the CLI den debug does work correct and hits the breakpoint in the IDE.
When downgrading to PHP 7.4 this issue is no longer present.
To Reproduce
Steps to reproduce the behavior:

Install fresh Magento 2.4 install with PHP 8.1 and Xdebug 3
Setup PHP Storm following docs
Enable debugger
Breakpoint is not hit

Expected behavior
Breakpoint should be hit in IDE.

I've tried to recreate, using images:
    image: ghcr.io/swiftotter/den-php-fpm-magento2-debug:8.1-node12
    image: ghcr.io/swiftotter/den-php-fpm-magento2:8.1-node12

I'm using PhpStorm and Xdebug Helper.
I'm setting breakpoint at pub/index.php on $bootstrap = Bootstrap::create(BP, $_SERVER);
Configurations:

The breakpoint is hit as expected.

@navarr Are you running Linux by any chance? Strange one if so...

@mattgrul I'm on Mac OS X

Potentially a Linux issue then.
I've noticed when using the PHP 7.4 image it routes through to the IP XXX.XXX.XX.X:90003.
However when on 8.1 its attempting to connect to localhost:90003
PHP message: Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:9003 (fallback through xdebug.client_host/xdebug.client_port).
Any help would be greatly appreciated.

@navarr This may help seems to be more too it, when running the PHP 7.4 image this is the log however the breakpoints does get hit and run correct
"PHP message: Xdebug: [Step Debug] Could not connect to debugging client. Tried: <IP_ADDRESS>:9003 (from HTTP_X_FORWARDED_FOR HTTP header), localhost:9003 (fallback through xdebug.client_host/xdebug.client_port) :-(" while reading response header from upstream, client: <IP_ADDRESS>, server: , request: "GET /uk/en/?heh HTTP/1.1", upstream: "fastcgi://<IP_ADDRESS>:9000", host: "app.augustinusbader.test"

@navarr Not sure on the issue however I have managed to get it working, if you need detailed OS versions etc  let me know.
So I noticed that the XDEBUG_CONNECT_BACK_HOST variable was set to " e.g. XDEBUG_CONNECT_BACK_HOST=". This must be some sort of error during installation.
After changing that to the private IP XDebug is now working again with PHP 8.1

Hmm, wardenenv/warden#200 indicates that it should be blank for Linux (at least, when wardenenv/warden#200 was being investigated).
I wonder if something has changed

Unfortunately well out of my remit, but I can narrow it down to anything that is different between the PHP 7.4 and 8.1 images

@sprankhub For me updating the XDEBUG_CONNECT_BACK_HOST ENV var on the nginx box to the docker network bridge gateway IP seemed to fix the issue for me.

@mattgrul, thanks. Considering I am a very simple, inexperienced dev, could you explain a bit more detailed how I retrieve the necessary IP and how I permanently set the env variable? 😅🙏

Okay, under Linux, this is what worked for me:

Find out the Docker network IP via the following command:
 docker run -it --rm ubuntu:22.04 bash -c "apt-get update > /dev/null && apt-get install iproute2 -y > /dev/null && ip -4 route show default | cut -d' ' -f3"

In many if not all cases, this seems to be <IP_ADDRESS> under Linux. See https://stackoverflow.com/a/60740997/719023.

Permanently set an environment variable XDEBUG_CONNECT_BACK_HOST on the nginx container with the IP from step 1. Therefore, create a file under .warden/warden-env.yml with the following contents:
 version: "3.5"
 services:
   nginx:
     environment:
       - XDEBUG_CONNECT_BACK_HOST=<IP_ADDRESS>

Run warden env up --force-recreate.

Enjoy debugging.

Even though this workaround works, XDEBUG_CONNECT_BACK_HOST seems to not be required in older images. On 7.4 projects, this env variable is empty and debugging still works... :thinking:

@sprankhub Thank you for the detailed information.  I do not have easy access to Linux to test.  Do you know if this workaround is required for PHP 8.0?  (Also: if it breaks if you run a den env pull - warning, Nodejs is reportedly broken on newer images)

I could only try on 8.1 for now. Since M2 does not support 8.0 at all, I am not sure how easy I am able to test this :-/ However, if I can somehow help with some Linux testing, do let me know and I see what I can do.

@navarr I found out that the wrong xdebug php configuration file is getting copied in this docker script https://github.com/swiftotter/den/blob/main/images/php-fpm/xdebug3/Dockerfile
@sprankhub you can fix the issue by overriding the /usr/local/etc/php/conf.d/15-xdebug.ini file with the content of /usr/local/etc/php/conf.d/15-xdebug3.2.ini.template.

@werfu @mattgrul this should be fixed in the latest images. Please perform a den env pull;den env up in your environments to use them


Add maven and pom instructions

Codecov Report

:exclamation: No coverage uploaded for pull request base (contribution-roadmap@0d84b23). Click here to learn what that means.
The diff coverage is n/a.

@@                   Coverage Diff                   @@
##             contribution-roadmap   #13432   +/-   ##
=======================================================
  Coverage                        ?   23.57%
  Complexity                      ?     4495
=======================================================
  Files                           ?     1362
  Lines                           ?    78667
  Branches                        ?     9548
=======================================================
  Hits                            ?    18542
  Misses                          ?    58752
  Partials                        ?     1373

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 0d84b23...9613d67. Read the comment docs.

@yuzhu  do you plan to finish this PR?

@yuzhu i will merge this PR and solve the comments in next PR

alluxio-bot, merge this please

@apc999 @Xenorith @HelloHorizon @yuzhu for contribution roadmap, I prefer to go with fast iteration instead of asking for a really high-quality roadmap. Will be much more efficient in a way that similar to google docs: everyone can modify the roadmap concurrently, no need to be perfect in the beginning.
For faster iteration, I will prefer to leave TODOs for some bigger scope review comments in the contribution roadmap just like https://github.com/Alluxio/alluxio/pull/13780
what's your thoughts?
I am asking for this because I found a small section in the contribution roadmap can take me or David or other people a really long period to finish and thus ... the contribution roadmap will forever in the beginning state.


Update master branch to release 1.0.1

This PR is to update the master branch from the 0.2.4 version of the msal library to the newly released General Availability version and additional patch 1.0.1.

LGTM


dataset

can you share the dataset folder for the audio_vectors and csv file

You can access the preprocessed data files here: https://www.dropbox.com/scl/fo/jdzz2y9nngw9rxsbz9vyj/h?rlkey=bji7zcqclusagzfwa7alm59hx&dl=0


Issue with super parameters, generics, and multiple levels of inheritance

class StringProperty extends DiagnosticsProperty<String> {
  StringProperty({
    // 🔥 error: The type 'dynamic' of this parameter isn't a subtype of the type 'bool' of the associated super constructor parameter. (super_formal_parameter_type_is_not_subtype_of_associated at [test] lib/pure_dart.dart:3)
    super.showName,
  });
}

class DiagnosticsProperty<T> extends DiagnosticsNode {
  DiagnosticsProperty({super.showName});
}

abstract class DiagnosticsNode {
  DiagnosticsNode({this.showName = true});
  final bool showName;
}

See code above. I believe this is valid code, but it produces the error shown in the comment.

/cc @johnniwinther

I can't repro this on bleeding edge. What version did you use?

@chloestefantsova Do you if this issue might have been fixed recently?

The inference does appear to work as expected on the bleeding edge for the CFE, but the Analyzer emits the error mentioned in the comment.

Yeah, building (which calls CFE) works:
$ flutter build apk

💪 Building with sound null safety 💪
Running Gradle task 'assembleRelease'...                           97.9s
✓  Built build/app/outputs/flutter-apk/app-release.apk (16.0MB).

But analyzing doesn't:
mit-macbookpro5:superissue mit$ flutter analyze .
Analyzing superissue...

  error • The type 'dynamic' of this parameter isn't a subtype of the type 'bool' of the associated super constructor
         parameter • lib/main.dart:6:11 • super_formal_parameter_type_is_not_subtype_of_associated

1 issue found. (ran in 13.1s)

cc @bwilkerson @scheglov

https://dart-review.googlesource.com/c/sdk/+/239460


Disallow async constructors

Describe the Bug
wasm_bindgen allows you to create an async constructor even though this is not supported by typescript.
Steps to Reproduce

#[wasm_bindgen]
pub struct MyStruct {
	data: u32
}

#[wasm_bindgen]
impl MyStruct {
  #[wasm_bindgen(constructor)]
  pub async fn new(data: u32) -> Self {
     // do something async
     Self { data }
  }
}

This compiles and actually works, however seems like undefined behavior and should just fail to compile
Expected Behavior
Unknown, probably fail to compile
Actual Behavior
Works

We considered removing support for this in #3562, since it was originally a bug, but discovered that people had started relying on it and so left it to avoid breakage.
You can see lots of instances of people doing this with https://github.com/search?q=%2F%23\[wasm_bindgen\(constructor\)\][+\n]*pub+async+fn%2F&type=code.

Do you know what actually ends up happening under the hood, is it safe?

Do you know what actually ends up happening under the hood, is it safe?

Yes; wasm-bindgen treats constructors nearly the same way as regular associated functions, and so it generates code based on the return type of the constructor (which for async functions is a JsValue after desugaring) rather than the type it's attached to.
This is what the generated JS code ends up looking like:
export class MyStruct {
    // ...
    constructor(data) {
        const ret = wasm.mystruct_new(data);
        return takeObject(ret);
    }
}

JS actually supports returning from constructors, and if the returned value is something other than this then new MyStruct() just returns that value instead of actually making a MyStruct.

Maybe we should investigate if we can emit a warning in this case (with the help of deprecated).


update to 4ece6c5 of iovisor to pull in iovisor/gobpf#139

I updated the vendored bits from gobpf in order to pull in the latest, https://github.com/iovisor/gobpf/pull/139 in particular (which brings more clarity in terms of licensing). For the update, I ran
$  gvt update github.com/iovisor/gobpf/elf
$  gvt update github.com/iovisor/gobpf/pkg/bpffs
$  gvt update github.com/iovisor/gobpf/pkg/cpuonline

A local test-build still passes. I wasn't quite sure how else to test this.

To test this, I did a local test with scope (using a new vendored copy of tcptracer-bpf) and it built and ran just fine.

Thanks!


inconsistency: top-level setTimeout, others

Simple test case:
setTimeout(() => {}, 0)

This works in cloudworker but fails in CF workers, with this error:

Some functionality, such as asynchronous I/O, timeouts, and generating random values, can only be performed while handling a request

We should disallow the same behavior and add tests for all cases we can think of.

It fails in the preview but I'm sure it works in production, have you tried it?

Hmm. Just tossing a single setTimeout(() => {}, 0) into an existing worker script seems to not break, but actually relying on a top-level timeout to do anything doesn't seem to work. I deployed this with wrangler and it didn't work, for example:
addEventListener("fetch", event => {
  event.respondWith(handleRequest(event.request));
});

const prom = new Promise(resolve =>
  setTimeout(() => {
    resolve("hello from async");
  }, 0)
);

async function handleRequest(request) {
  const data = await prom;
  return new Response(data, { status: 200 });
}