Change the publication frequency of the topic : camera / depth_registered / ?

Hello ! First of all, I wanted to thank you for sharing ROS# as an opensource and to respond in the forum!
I am currently a young beginner in ROS and Unity and I have been working for a few weeks on a project where there is need to model on unity in VR a surface present in front of a camera.
What I already did:
In the project, a computer (ubuntu) is connected to an intel realsense2 camera. Another computer (windows) is connected via a network cable to the previous computer and has a subscriber of topic / camera / depth_registered / points on Unity. I use these points in real time to create a mesh thanks to the triangulation method. That leaves me with a rectangle that looks like this:

The problems related to my method:

The main concern of my method is that the system takes a lot of time to update (~ 50s ,my program is not optimized either I guess). As part of the project I do not need to have a lot of Fps (1 uptdate of the pointclouds per 3 seconds could be enough since the object is not supposed to move). So in front of this flow of information that unity does not seem to manage I could see that it would surely be necessary to compress the pointClouds, but I wanted to know first of all if it was possible to lower the frequency of publication of the topic?

I don't care about the colors so I ignore them in the data from sensor_msgs/PointCloud2 Message, can you confirm that this is the optimal topic?

Question Unity: Once the mesh is created I need to automate the creation of a collider. Since I did not find a simple way to create it, I wanted to create a terrain, is it a good idea?

Thank you and Have a good Day ! :)

Hello @YannRodriguez
In order to generate a custom mesh out of point clouds without using color information, please keep in mind that you do not have to subscribe to "camera / depth_registered / points", which I assume is a pointcloud2 type of messages. You can just subscribe to 2D depth images so that communication and processing take less time. Please see the similar discussion here #211.
It is possible to lower the frequency of publication on the ROS side, to do that please search it here. Yet, it is possible to lower the frequency of subscription on Unity side. If your subscriber script implements the base class Subscriber.cs, you can see that there is a variable called TimeStep which controls the rate of subscription.
For Unity related questions please refer to here.
I hope it helps.


Rust support

It might even share some code with C/C++ checkers I believe.

No plans for this right now.

You may want to have a look at https://github.com/facebookexperimental/MIRAI


Horizontal Lines appear on GridMap Elements

Godot version:
Godot Engine v3.1.1.stable.flathub
OS/device including version:
Fedora 30 64 bit
Intel® Core™ i7-8550U CPU @ 1.80GHz × 8
OpenGL ES 3.0 Renderer: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)
MacOs Mojave 10.14.5
Intel® Core™ i7-6700HQ
AMD Radeon Pro 450
Issue description:
Some horizontal lines are appearing on the gridmap elements while the camera is moving.
When the camera is not moving there is no problem at all.
Another thing I've noticed is that if I increase the distance to the Character more lines start appearing.
What could be causing this?
Minimal reproduction project:
horizontal_lines.zip

Try making each tile "bleed" into the next one slightly (by scaling the floor plane).

@Calinou Thanks for your answer.
So you're telling me to try and scale it a little bigger so it would cover the area of the next floor pane, is that it?
I will try scaling it a little and mess with the rotations and see if it gets any better.

So you're telling me to try and scale it a little bigger so it would cover the area of the next floor pane, is that it?

Yes :slightly_smiling_face:

I've set the Scale of all tiles to 1.1 and the Rotation of the GridMap to 0.5 and it worked just fine!
Thanks so much for your help @Calinou :+1: :smile:

@andrevenlibretrend No problem! It seems like the issue is resolved, so I'll close this.


Can not curl some Pod endpoints from some nodes after performing Node drain on unrelated nodes.

Expected Behavior
All the endpoints should be reachable from all the nodes
Current Behavior

Drain multiple nodes in a short time
Some endpoints, not necessarily the endpoints belonging to the pods which were on the drained nodes, suddenly become unreachable from some of the worker nodes - even if those workers were not drained / left untouched

Possible Solution
So far restarting either of the nodes is the only workaround that I am aware of. Or explicitly deleting the pod, so that a new endpoint gets created.
Steps to Reproduce (for bugs)
This is difficult to reproduce as I couldn't find a deterministic pattern. I have seen this on a cluster with 1000+ endpoints

Make a list of all the endpoints in the cluster
Have at least 2-3 nodes with ~20 endpoints
Drain these nodes around the same time
Curl all the endpoints in (1) except those in (2) from ALL the nodes
You will notice that curl fails with Failed to connect to <endpoint> port 80 after X ms: Couldn't connect to server on some of the nodes for some of the endpoints
You will also notice that on the nodes curl pails, other endpoints belonging to the Pods running on the same node are reachable. It's only some endpoint(s) belonging to that node not reachable.

Context
Take the following example, where myapp-stg-c8ccd55b6-2jld6 (<IP_ADDRESS>) Pod on mynodezonea1 is not reachable from mylinuxnodezoneb9.
k get pods -A --cluster=test -o wide | grep myapp-stg
app                                     myapp-stg-c8ccd55b6-2jld6                               1/1     Running                      1 (16d ago)        30d     <IP_ADDRESS>   mynodezonea1             <none>           <none>
app                                     myapp-stg-c8ccd55b6-g554x                               1/1     Running                      1 (16d ago)        30d     <IP_ADDRESS>   mynodezonea2             <none>           <none>
app                                     myapp-stg-c8ccd55b6-jn5tg                               1/1     Running                      1 (16d ago)        30d     <IP_ADDRESS>    mynodezoneb1             <none>           <none>

avinesh@mylinuxnodezoneb9:/$ curl <IP_ADDRESS>
curl: (28) Failed to connect to <IP_ADDRESS> port 80 after 132207 ms: Couldn't connect to server

kubectl describe output of mynodezonea1:
PS C:\> k describe node mynodezonea1 --cluster=test
Name:               mynodezonea1
Roles:              worker
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=windows
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=mynodezonea1
                    kubernetes.io/os=windows
                    node-role.kubernetes.io/worker=worker
                    node.kubernetes.io/windows-build=10.0.20348
                    topology.kubernetes.io/region=myregion
                    topology.kubernetes.io/zone=zonea
Annotations:        node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/22
                    projectcalico.org/IPv4VXLANTunnelAddr: <IP_ADDRESS>
                    projectcalico.org/VXLANTunnelMACAddr: <trimmed>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  <trimmed>
Taints:             os=windows:NoSchedule
Unschedulable:      false
Lease:              Failed to get lease: leases.coordination.k8s.io "mynodezonea1" is forbidden: User "username" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-node-lease"
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sat, 19 Oct 2024 02:17:50 -0400   Sat, 19 Oct 2024 02:17:50 -0400   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Mon, 18 Nov 2024 14:01:24 -0500   Sat, 19 Oct 2024 02:17:49 -0400   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Mon, 18 Nov 2024 14:01:24 -0500   Sat, 19 Oct 2024 02:17:49 -0400   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Mon, 18 Nov 2024 14:01:24 -0500   Sat, 19 Oct 2024 02:17:49 -0400   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Mon, 18 Nov 2024 14:01:24 -0500   Sat, 19 Oct 2024 02:17:49 -0400   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    mynodezonea1
Capacity:
<trimmed>
Allocatable:
<trimmed>
System Info:
  Machine ID:                     mynodezonea1
  System UUID:                    <trimmed>
  Boot ID:                        <trimmed>
  Kernel Version:                 <trimmed>
  OS Image:                       Windows Server 2022 Standard
  Operating System:               windows
  Architecture:                   amd64
  Container Runtime Version:      containerd://1.6.26
  Kubelet Version:                v1.27.12
  Kube-Proxy Version:             v1.27.12
PodCIDR:                          <IP_ADDRESS>/24
PodCIDRs:                         <IP_ADDRESS>/24
Non-terminated Pods:              (18 in total)
  Namespace                       Name                                           CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                       ----                                           ------------  ----------  ---------------  -------------  ---
  <trimmed>
  app                          myapp-prod-6c94f965f8-6pvhg               250m (1%)     1 (7%)      512M (0%)        1G (1%)        30d
  app                          myapp-stg-c8ccd55b6-2jld6                 250m (1%)     1 (7%)      512M (0%)        1G (1%)        30d
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests     Limits
  --------           --------     ------
<trimmed>

As you can see there is myapp-prod-6c94f965f8-6pvhg and other endpoints that I trimmed, on this node which are reachable from mylinuxnodezoneb9. Only the endpoint belonging to myapp-stg-c8ccd55b6-2jld6 is not.
Here is kubectl describe node for mylinuxnodezoneb9:
k describe node mylinuxnodezoneb9 --cluster=test
Name:               mylinuxnodezoneb9
Roles:              worker
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=mylinuxnodezoneb9
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/worker=worker
                    topology.kubernetes.io/region=myregion
                    topology.kubernetes.io/zone=zoneb
Annotations:
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/24
                    projectcalico.org/IPv4VXLANTunnelAddr: <IP_ADDRESS>
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  <trimmed>
Taints:             <none>
Unschedulable:      false
Lease:              Failed to get lease: leases.coordination.k8s.io "mylinuxnodezoneb9" is forbidden: User "username"  cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-node-lease"
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Sun, 03 Nov 2024 21:45:53 -0500   Sun, 03 Nov 2024 21:45:53 -0500   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Mon, 18 Nov 2024 14:11:26 -0500   Sun, 03 Nov 2024 21:45:50 -0500   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Mon, 18 Nov 2024 14:11:26 -0500   Sun, 03 Nov 2024 21:45:50 -0500   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Mon, 18 Nov 2024 14:11:26 -0500   Sun, 03 Nov 2024 21:45:50 -0500   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Mon, 18 Nov 2024 14:11:26 -0500   Sun, 03 Nov 2024 21:45:50 -0500   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    mylinuxnodezoneb9
Capacity:
<trimmed>
Allocatable:
<trimmed>
System Info:
  Machine ID:                         <trimmed>
  System UUID:                        <trimmed>
  Boot ID:                            <trimmed>
  Kernel Version:                     <trimmed>
  OS Image:                           Red Hat Enterprise Linux 8.10 (Ootpa)
  Operating System:                   linux
  Architecture:                       amd64
  Container Runtime Version:          cri-o://1.27.4
  Kubelet Version:                    v1.27.12
  Kube-Proxy Version:                 v1.27.12
PodCIDR:                              <IP_ADDRESS>/24
PodCIDRs:                             <IP_ADDRESS>/24
Non-terminated Pods:                  (37 in total)
  Namespace                           Name                                                CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                           ----                                                ------------  ----------  ---------------  -------------  ---
<trimmed>
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests           Limits
  --------           --------           ------
<trimmed>

And the PodCIDR range is correctly registering in iptables on mylinuxnodezoneb9
avinesh@mylinuxnodezoneb9:/$ /usr/sbin/ip route | grep "<IP_ADDRESS>"
<IP_ADDRESS>/26 via <IP_ADDRESS> dev vxlan.calico onlink

And, as mentioned earlier, myapp-prod-6c94f965f8-6pvhg endpoint which is also running on the very same node is reachable from
k get pods -A --cluster=test -o wide | grep myapp-prod-6c94f965f8-6pvhg
app                                     myapp-prod-6c94f965f8-6pvhg                             1/1     Running                      0                  30d     <IP_ADDRESS>   mynodezonea1             <none>           <none>

avinesh@mylinuxnodezoneb9:/$ curl <IP_ADDRESS>
avinesh@mylinuxnodezoneb9:/$

So it's not like node-to-node networking is completely broken.
I do not use any networking policy, nor are there firewall restrictions at the host level.
Your Environment

Calico version: 3.28.0
Calico dataplane: iptables & windows
Orchestrator version (e.g. kubernetes, mesos, rkt): Kubernetes 1.27
Operating System and version: Linux & Windows Server 2022
Link to your project (optional):

Hi @avin3sh, could you please share more logs with us, specifically the calico windows-node logs and kube-controllers logs. For more context please update the log level to debug. You can change the log level by running kubectl patch felixconfiguration default --type merge --patch='{"spec":{"logSeverityScreen":"Debug"}}'

@avin3sh do you have any extra info?

Hi folks, Sorry for keep you waiting - I haven't been able to reproduce this in our standard setup - the problem is inconsistent. I don't have access to a lab environment until later this month - please give me some time so that I can simulate some scenarios  and hopefully reproduce the problem and capture the logs.


Add support to the NO_COLOR Manifest

Add support to the NO_COLOR manifest.

When NO_COLOR is set, chalk won't display any colors FORCE_COLORS=0
When NO_COLOR is unset, chalk displays all possible colors FORCE_COLORS=3

CLI developers no longer need to create their own env variable to remove ansi colors from their command outputs. You can then include Heroku and SFDX CLIs in the NO_COLOR manifest opening a PR in this repo https://github.com/jcs/no_color

@AllanOricil I like the intent of this but I don't think it's something we want to add at the moment. A few reasons:

I agree with chalk's rationale for not adding NO_COLOR support

https://github.com/chalk/supports-color/issues/105#issuecomment-542271445
https://github.com/chalk/supports-color/issues/74

If we merge this we still couldn't say that we adhere to the NO_COLOR standard since we couldn't guarantee that all colors would be disabled - someone could have a CLI plugin that uses a different color library that doesn't respect either FORCE_COLOR or NO_COLOR
In order to actually adhere to the standard oclif/core would need to know about every color related environment variable. Maybe that wouldn't be that difficult but it sets a bad precedence
I think this is a scenario where I prefer oclif to be un-opinionated and allow CLI developers to make up their own mind. Especially since it would be trivially easy for someone to set the env var themselves in their bin/run.js

I understand that there could exist plugins using other color libs, but wouldnt this mean that they are not conforming with Oclif's core? Shouldnt all plugins and CLIs use Oclif's UX object to log? If they are not using it, why care about these plugins/CLIS? They chose not to use oclif core packages for outputs. It is their problem, and oclifs for allowing them to not follow the "framework".
I also can't understand why not enforcing this on ALL CLIs and plugins made with oclif's core.  Leaving colors optional for cli builders just contributes to people not following the NO_COLOR manifest.
If all tools out there that are used to build CLIs enforce NO_COLOR, over the years there would exist less need for a NO_COLOR manifest.

obs: I did not check if this information is true. There may exist other libraries that were not included.
According to chat gpt these are the most used libs that developers use to style their terminal outputs with ansi colors:

Package Name
Link

Kleur
https://www.npmjs.com/package/kleur

Colorette
https://www.npmjs.com/package/colorette

Colors
https://www.npmjs.com/package/colors

Blessed
https://www.npmjs.com/package/blessed

Ok, I give up on this. According to chalk's maintainer, there are already lots of different "standards"


Update Package.json

bumps the uglifier to 2.6.0

Consolidated in https://github.com/leapmotion/leapjs/commit/31b00723f98077304acda3200f9fbcbaaf29294a


[VL] Link shared jemalloc lib to work with LD_PRELOAD

What changes were proposed in this pull request?
<>
How was this patch tested?
<>

[100%] Linking CXX shared library ../releases/libvelox.so
Checking ld result of libvelox.so
ld: warning: cannot find entry symbol _start; not setting start address
Checking ldd result of libvelox.so
	linux-vdso.so.1 =>  (0x00007ffef44ea000)
	libgluten.so => /__w/incubator-gluten/incubator-gluten/cpp/build/releases/libgluten.so (0x00007f4fb1a8a000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f4fb1870000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f4fb166c000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f4fb1464000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4fb1248000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f4fb0f46000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f4fb0b78000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4fb9bbf000)

Log doesn't show libjemalloc.so as libvelox.so's dependency, which is good to me but is it expected?

@zhztheplayer, there is an extra option --build_jemalloc (OFF by default) to control whether to link this lib. It's still OFF in CI build.

@PHILO-HE I have a doubt about the PR title. What does this PR have to do with LD_PRELOAD? All I see is that we're building jemalloc as a shared library in /usr/local/lib

@surnaik, this pr simply allows some profiling log printed when jemalloc is used with LD_PRELOAD (set by user in runtime env.), e.g., shows memory size allocated by jemalloc. It requires linked jemalloc lib is as same as the one set by LD_PRELOAD.

Enabling this now, will add libjemalloc as a dependency of libvelox. Is this to force users to provide jemalloc using LD_PRELOAD?

Not exactly. With the related build option turned on, it does not require LD_PRELOAD must be set by user. But without the use of LD_PRELOAD, turning on the option is useless since the profiling log has no helpful info (e.g., 0 byte allocated by jemalloc).


Step 5: CSS optimisation breaks the grid

Step 5: CSS optimisation breaks the grid
Detailed description

Describe in detail the issue you're having.

After the CSS optimisation the footer grid is broken.

Is this a feature request (new component, new icon), a bug, or a general issue?

no

Is this issue related to a specific component?

yes, Carbon grid.

What did you expect to happen? What happened instead? What would you like to see changed?

Grid should use the 16 columns.

What browser are you working in?

Chrome 75.0.3770.100 (Official Build) (64-bit)

What version of the Carbon Design System are you using?

10.3.0

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

no
Steps to reproduce the issue

Work through tutorial step 5

Additional information
See pull request:
https://github.com/carbon-design-system/carbon-tutorial/pull/1447#discussion_r299597080
With the feature the footer looks good again:

Overseen the instruction to keep the feature flags. Sorry...


[WFLY-11339] FilePermission, read only, granted to ALL FILES because …

…the failing jar reference is dependent on user's mvn repo dir and the jar version.
https://issues.jboss.org/browse/WFLY-11339

Per this comment, it sounds like this is a regression so fixing the test doesn't seem quite right. However I think the only way to really fix would be in CXF.

retest this please


Add "merge and deploy" command

This PR adds a new command "{prefix} merge and deploy" to Hoff.
This command also approves a PR for rebase and merge, and currently triggers the same merge behaviour as "{prefix} merge".
Changes:

A new value MergeAndDeploy is added to ApprovedFor.
parseMergeCommand now searches for the "{prefix} merge and deploy" infix before searching for "{prefix} merge", returning Just MergeAndDeploy if found.
The web interface will show which merge command was used to approve a PR:

Approved PRs show the text "Approved by {user}" in the current version of Hoff,
PRs approved with "{prefix} merge and deploy" now show "Approved for merge and deploy by {user}",
PRs approved with "{prefix} merge" now show "Approved for merge by {user}".

The approval acknowledgement message now echoes the command that was used to approve the PR, i.e. Hoff will comment "Pull request was approved (for merge | for merge and deploy) by {user}, …" depending on which command was used.
The tests were updated to adjust to the new expected messages and to include a use of "merge and deploy" in the testcases.

@OpsBotPrime merge

@OpsBotPrime merge

Pull request approved by @maartenberg, rebasing now.

Pull request approved by @maartenberg, rebasing now.

Rebased as 5364d96a5bc16a1fcd6b05231924dd5fc7f7450e, waiting for CI …

Rebased as 5364d96a5bc16a1fcd6b05231924dd5fc7f7450e, waiting for CI …


does the mel_fmax matter ？

I saw “please set to 8000 for HiFi-GAN vocoder, set to null for MelGAN vocoder” about mel_fmax in preprocess.yaml
But I didnt change it when using MelGAN, it seems not bad.
Why mel_fmax is different in hifigan and melgan？

@yileld It's a parameter of the mel filters. This parameter is set to different values since the preprocessing settings of MelGAN and HiFi-GAN are different. While the resulted mel-spectrogram may not differ a lot, you can try to compute the mel-spectrogram of a ground-truth wav with mel_fmax=8000 and convert it back to the waveform with MelGAN, and you should notice that the pitch will be slightly different.


[Docs] Lists of implemented formats not compiling

These section links point to the two lists of implemented formats in the version 0.9.0 docs:

https://neo.readthedocs.io/en/0.9.0/io.html#module-neo.io
https://neo.readthedocs.io/en/0.9.0/rawio.html#module-neo.rawio

These appear to be no longer compiling in the latest version of the docs:

https://neo.readthedocs.io/en/latest/io.html#module-neo.io
https://neo.readthedocs.io/en/latest/rawio.html#module-neo.rawio

There are just section headers with nothing in the section.

Oops, I submitted the issue to GitHub twice. See #930. I'll close this one.

Oops, I submitted the issue to GitHub twice. See #930. I'll close this one.


Version of ChatGPT 3.5 for evaluation.

Thank you for your excellent work!
I have some confusion regarding the evaluation process. In this file, it appears that you use ChatGPT-turbo-0327 as the default setting. However, in this script, a different version is specified.
Since the evaluation results vary significantly between versions (by about 10%), I am curious which version is ultimately used. I attempted to reproduce the results by inference alone and found that I only achieved scores similar to your report when using ChatGPT-turbo-0327, not ChatGPT-turbo-0613.
Could you please clarify which version is used for the final evaluation?
Thank you!

ChatGPT-turbo-0613


Wrong latte.exe cmdline example for latency test

The cmdline example for the receiver with latte.exe is wrong:
latte -c -a <IP_ADDRESS>:5005 -i 65100
the -c option flag must used only at the sender's location, the correct example should be instead:
latte -a <IP_ADDRESS>:5005 -i 65100

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

ID: c5a77eb3-1f6d-0fee-7d77-44a56fdb78b0
Version Independent ID: 66f67a40-fcb3-9549-63fc-295e330a9c56
Content: Validate VPN throughput to a Microsoft Azure Virtual Network - Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-validate-throughput-to-vnet.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: radwiv

@rossanov, Thanks for reaching out. We will investigate and update this thread.

Hello, the page still contains wrong information after 20 days. Can you pls check?


Calculator

Project title
Calculator
Project Description
I want to add a project of calculator.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript

@gurjeetsinghvirdee please assign


Dates and times

Does this library handle the comparison or date, and times?
for example
var context = {
    birthdate: "01-01-1975',
    todaysdate: '25-03-2017'
}
jexl.eval('birthdate < todaysdate', context).then(function(res){ });

In this case, you are comparing strings because there's nothing in the expression to indicate you'd rather treat it as a time. However, this is quite easy to add :) Please test before using, but I'd suggest something like this:
jexl.addTransform('toEpoch', (dateStr) => {
  return new Date(dateStr).getTime()
})

Now this will work:
var context = {
    birthdate: "01-01-1975',
    todaysdate: '03-25-2017'
}
jexl.eval('birthdate|toEpoch < todaysdate|toEpoch', context).then(function(res){ });

Note that, for that specific solution, you'd need to provide dates that the javascript Date object can parse -- so I had to change todaysdate to MM-DD-YYYY format rather than DD-MM-YYYY. But you can support your own format just by splitting on the - and instantiating Date however you want.
If you don't like the syntax of having to apply a transform to every date, you could also add a binary operator that assumes that both the left and right sides are dates.  If you wanted the symbol for "date less than" to be <d< (just picking something out of thin air for example -- make that whatever you want), you could do this:
jexl.addBinaryOp('<d<', 20, function(left, right) {
  return new Date(left).getTime() < new Date(right).getTime()
})

And now you can do this:
var context = {
    birthdate: "01-01-1975',
    todaysdate: '03-25-2017'
}
jexl.eval('birthdate <d< todaysdate', context).then(function(res){ });

Personally, I think the transform option, while more verbose, is the cleaner option here, but it's up to you :)

Thanks for pointing out the transform, I never considered that.
Regarding the custom binary operator, is there any restriction or rules we must follow when adding our own?  For instance in your example above you created one like <d<, but does the parser know to treat the entire unit as an operator and not stop at the first < and treat that as a less than operator which is registered already?
At first I thought custom operators had to start with underscore like _= because of the example on the main page.

Oh, nope! The _= was completely arbitrary. It could have been =_ or =< or *** and it would have worked all the same. Jexl performs longest-first tokenization, meaning that it will check for <d< before checking for <.

I'm a bit unclear on the use of transform (i.e. the syntax for passing parameters.
So from your example

jexl.addTransform('toEpoch', (dateStr) => {
return new Date(dateStr).getTime()
})

Does this mean toEpoch is the transform function which takes one parameter called dateStr - and this first (and only) parameter comes from the value preceding the pipe symbol in the expression birthdate|toEpoch
Is that right?
Now if I want to add a second parameter like this

jexl.addTransform('toEpoch', (dateStr, format) => {
return new Date(dateStr).getTime()
})

Then do I have to call the toEpoch like in the example on the main page

// Transform asynchronously, with arguments
jexl.addTransform('getStat', function(val, stat) {
return dbSelectByLastName(val, stat); // Returns a promise
});
jexl.eval('name.last|getStat("weight")', context, function(err, res) {
if (err) console.log('Database Error', err.stack);
else console.log(res); // Output: 184
});

So myDate|toEpoch("MM-DD-YYYY")
Where the first parameter is always assumed to be the value on the left side of the pipe?

You're exactly right. Every transform function will be called with a minimum of one argument, and that first argument is always the subject being transformed (the left of the pipe). Any additional arguments to the transform function are what the user specified in parens after the transform name.


[IMP] Unfortunate consequences of implementing #1278 (current dev)

Current dev version

Implementation of not repeating columns headers - ref #1278  -  introduces an unfortunate effect on boards with many swimlanes.

The "waste of space"-claim/medicine - now has left us with a solution that involves a lot more work.

Now not possible to use the "+" to create new task in the target location (have to create in in the default swimlane and move it)

Also impossible to know which column you are moving the task to (unless you have a special memory in your brain), as column titles are not visible when scrolled down on the board.

Suggest re-considering this change and reverting to the way it was. Less work creating new tasks and knowing where you are moving the task trumps space-waste or alternative with having to collapse/expand all swimlanes to see tasks down the board to keep track of your column headers

I don't know how the new UI looks but from what you write I'd say a + should be there to allow contextual task creation

@sparkles645 I agree with the missing headers on a large board. But if you create a new task, you could select the swimlane in the popover:

@BlueTeck

Personally I could live with defining the swimlane along with the task, but I'm more concerned for our users that are used to / "trained" to the having the "+" button closeby when they are viewing a swimlane... I don't wish to create confusion and frustration by changing their workflow. I recognize that this one isn't a leap, but it is still a change in how it has been working up until now. I believe the majority use the "+" sign when creating new tasks, based on what I've observed.
Still an issue with the column titles coming out of view when scrolling down. Floating column titles sound weird at first though - or is that just me(?)
SIDE-NOTE
The potenial in a custom field / tag possibility - ref #262 , #646, #998  - would probably eradicate the need for so many swimlanes in some of our boards... (some boards have 30+ swimlanes, currently no way around that with our use case at the moment)

Kanbanflow has it like so

Effectively, after using using for a while it's not efficient. To create a task to another swimlane I have 2 more actions to do that I didn't need to do before. So I will change again the user interface, in master we have currently:

So I will do another change later this week to repeat the column header below each swimlane name.
For reference the current layout look like that for the last stable version:

My initial goal was to remove the space wasted on the left by the swimlane column name.
@sparkles645 What is your use case to have so many swimlanes and why tags may be a solution for that?

@fguillot
Description of use case:

Tasks on board organized by and possible to sorted by the following dimensions:

User/assignee responsible - (a given duh!)

Category - determines the type of / nature of the task -

categories are typically across all "global" / interdepartmental boards - and I'm paraphrasing here to express their intention and avoid abbreviations:

administrative (blah blah blah, paperwork, managerial domain)

planned work/operations (things you are supposed to be doing/working on)

interruption/failure (a.k.a. "Oh, Shit", mobilize and fix it - depending on how important it it)

MOM system (software, use what you've learned to prevent the same thing from happening again)

reported deviation/unwanted incident (computer says someone else say'd you have to fix this, HSE related)

We use Complexity to describe the priority of the task.
A "1" task is of highest priority, a "2" task is of lesser priority .... and so on for the (limited) range we use. Since complexity is viewed on the task, it is easy to get a feel for what's important and what can wait when seeing the front of the cards. If you see a "4", then you know it's not that in a hurry to get fixed, some "5"s probably fall into the "won't fix" territory.

The swimlanes are currently being used to gather all tasks that relate to a single objects or asset. Example - all tasks related to factory # 1 is put in the swimlane "Factory # 1 - "

When you need the overview of what to deal with next for that site/asset, you can just review the swimlane.

If tags were available, one could for example easily filter out all open tasks of category "Oh shit" for "Factory #1".

In this way, tags would allow us to keep both the type of task (category) and also the asset/object dimension in the filtering - and we could remove many of the swimlanes without mixing it all.

Some of our users have complained that so many swimlanes make the board large and hard to manage. They'd rather have an (asset/object) "tag" dimension to work with. (we actually did a survey on it) But mixing all the tasks together - (between all the "factories") - would create utter chaos on the board, so we need to keep tasks relating to different objects/assets separated.

Hope this describes the use case in sufficient degree to make it understandable.

We are very grateful for the toggle - removing fixed height - ref #1159 - as people were about to be wearing out their scroll-wheels to move around. Now back in "compact" feel and only see what you've filtered out.

@fguillot
If the plan is to add another header to each swimlane, that change may add more wasted screen space to boards with many swimlanes than will be saved by removing the swimlane column on the left.
Each swimlane would contain a row with the swimlane name and below it a column header row?

I changed again the layout, so now column headers are repeated for each swimlane.
However, I have to keep the column titles at the top for the first swimlane otherwise collapsing column doesn't work (css/html glitch)...
@jtourt that use a little more space vertically but horizontally you can have more columns.


could not get to work for win7 and matlab2017b.

C:\temp42>"C:/Program Files (x86)/Matlab2015a/bin/matlab.exe" -nosplash -nodesktop
C:\temp42>clear 'C:/temp42/test2.m'
'clear' is not recognized as an internal or external command,
operable program or batch file.
C:\temp42>clc
'clc' is not recognized as an internal or external command,
operable program or batch file.
C:\temp42>run 'C:/temp42/test2.m'
'run' is not recognized as an internal or external command,
operable program or batch file.

Matlab 2015 does not support the command line


Fix class to default-route mapping

Decide what to do about default-routes (do they still make sense?)
Ensure that namespaced controllers can have manually-configured routes assigned to them

Add to this to remove the default Controller::Link() behaviour; I'd prefer it was an abstract method, thus ensuring that only explicit routes exist.
For testing we should disable default route registration, which I've found is still turned on. Testing should be the same as live, where controllers aren't automatically available.
Namespaced controllers can have routes. [x]

Consensus is to drop default URL-to-class mapping; it's an unnecessarily lazy & magical relic of SS2.

PR at https://github.com/silverstripe/silverstripe-framework/pull/6692


update js client sdk version

🚀 Deployed on https://62ccb9b47d9c890095c1c8a5--cozy-fox-0defec.netlify.app


fix(plugin-docs,theme): refactor docs plugin routes and component tree

Breaking changes
This refactor significantly changes the docs theme component tree. If you swizzled @theme/DocPage, or doc tags pages, you will likely need to upgrade your theme code a bit.
The tree of theme components rendering doc routes changed from:
Root
├── @theme/DocPage
│   └── @theme/DocPage/Layout
│       ├── @theme/DocPage/Layout/Sidebar
│       └── @theme/DocPage/Layout/Main
│           ├── @theme/DocCategoryGeneratedIndexPage
│           └── @theme/DocItem
├── @theme/DocTagsListPage
└── @theme/DocTagDocListPage

to this new structure
Root
└── @theme/DocsRoot
    └── @theme/DocVersionRoot
        ├── @theme/DocRoot
        │   └── @theme/DocRoot/Layout
        │       ├── @theme/DocRoot/Layout/Sidebar
        │       └── @theme/DocRoot/Layout/Main
        │           ├── @theme/DocCategoryGeneratedIndexPage
        │           └── @theme/DocItem
        ├── @theme/DocTagsListPage
        └── @theme/DocTagDocListPage

@theme/DocPage has been renamed to @theme/DocRoot
@theme/DocRoot (renamed) does not receive a versionMetadata prop anymore. The new @theme/DocVersionRoot receives it (upper in the tree), and makes it available in its subtree with the useDocsVersion() hook.
@theme/DocRoot (renamed),  @theme/DocTagsListPage and @theme/DocTagDocListPage do not apply <Layout> anymore: it's applied in @theme/DocsLayout (parent of all docs plugin routes)
option docPageLayoutComponent has been renamed to docRootComponent

Note there's a clear distinction between:

@theme/DocsRoot: top-level parent layout component that wraps every docs plugin routes (all versions, docs, generated index, docs tags pages...) and apply the <Layout> globally
@theme/DocRoot: single doc layout, responsible for displaying the docs sidebar alongside the docs content (markdown or category generated index)

Motivation
All the versioned docs pages should have a shared parent layout page. This prevents unmounting/remounting the layout when navigating across docs pages, category-generated index pages, tags pages, and even across versions.
New docs plugin options:

docsRootComponent: the component that wraps every route of a single doc plugin instance
docVersionRootComponent: the component that wraps every route of a specific doc version

With this refactor, tags-related pages are able to use the useDocsVersion() hook.
Also fixes a bug in the core route sorting algorithm which was not really recursive.
Test Plan
unit tests + preview
Test links
Prod and deploy preview should look exactly the same.
Doc:

https://deploy-preview-7966--docusaurus-2.netlify.app/docs/installation
https://docusaurus.io/docs/installation

Tags list:

https://deploy-preview-7966--docusaurus-2.netlify.app/tests/docs/tags
https://docusaurus.io/tests/docs/tags

Tag page:

https://deploy-preview-7966--docusaurus-2.netlify.app/tests/docs/tags/some-tag
https://docusaurus.io/tests/docs/tags/some-tag

Does this supercede #6823?

Thanks, good catch 😅 wonder how I'll fix that

Can it be a prop in NotFound to not render Layout?


Mark local variable as const

PR Summary

Fix RCS1118: Mark local variable as const
Inline various constants
Extract various constants

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[NA] Experimental feature(s) needed

[NA] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[NA] Documentation needed

[NA] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[NA] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@iSazonov It seems Roslynator analyzers are not finding diagnostics inside #if UNIX etc.

I'll give some extra time for other reviewers. They're likely to be out next week, so we may have to wait a little whlie

It seems analyzers do not find code fixes inside an #if directive

@xtqqczze It is expected - the analyzers work at compile. You could target an Unix while run analyzers. But it is not critical.

@PoshChan please remind me in 10 days

I checked 99% consts in the repo (local too) is in PascalCase. So we should follow our pattern.

rebased to resolve #13316 conflict

rebased to resolve merge conflicts

@PowerShell/powershell-maintainers reviewed this PR and agreed to accept it for 7.2 preview. We should delay merging this PR until after 7.1 GA is done because the chance of confliction caused by this PR is high.

Set Draft till 7.2 Preview1.

@rjmholt @SteveL-MSFT I think we can merge.

This PR is ready for final review.

@xtqqczze Please resolve merge conflicts.

@xtqqczze Is it still Draft?

@xtqqczze Please resolve merge conflicts.

@xtqqczze Please resolve merge conflicts.


Error after creating new project

I see the fix:
ERROR Internal Server Error: /_/templates/reference_genome_list_controls
Traceback (most recent call last):
File "/Users/gleb/Dropbox/Backup/Projects/churchlab/millstone/venv/lib/python2.7/site-packages/django/core/handlers/base.py", line 115, in get_response
response = callback(request, *callback_args, **callback_kwargs)
File "/Users/gleb/Dropbox/Backup/Projects/churchlab/millstone/genome_designer/main/template_xhrs.py", line 78, in reference_genome_list_controls
context['show_de_novo'] = int(request.GET.get('showDeNovo'))
TypeError: int() argument must be a string or a number, not 'NoneType'

Actually Brian's fix of getting rid of showing de novo assemblies in ReferenceGenome list view is more correct and matches overall development.
Fixed in 39e0564919c5bb56cbfc070cae7bca250a4f1a1d.


kpt fn interface library

The interface library provides common functions that will be used by the krm-functions.

/retest

/ok-to-test

/test all

/test ?

/test presubmit-nephio-golangci-lint

/ok-to-test

Failure is: krm-functions/lib/interface/v1alpha1/interface.go:20: File is not gofmt-ed with -s (gofmt)

I have checked in a new approach. this would be used for all fn: generators, mutators, etc.
@johnbelamaric @gvbalaji @vjayaramrh
We store local all in kubeObject and have some methods around it.
The New would create the interface. You can either supply a go struct or a raw byte which would be yaml.
We have 3 operations to perform on these objects.

initialise the interface:
-> when you generate. We could use New(go struct)
-> any other scenario. We use the []byte

Afterwards we need to:

access data: we could standardise on the go struct and leverage the Get methods it exposes. (this means no specific get methods are needed)
mutate data: we have a gostruct to set the complete object and individual setter methods we need to write (or codeine going fwd)

/retest

/retest

/hold

ok thx. there is a few more changes to be added but we can do this through another PR


Stuck after purchase

1 - Download from App Store
2- Subscribe to the Anual Plan
3 - It will confirm.
4 - Get stuck (I  had to close / open the app)
There was no way to leave this screen (ESC).

Hey, I'll look into it right away, thanks!

4 - Get stuck (I had to close / open the app)

I hope you were able to get access to the app after this?
I'm investigating, but I can't seem to be able to reproduce it with a StoreKit debug environment.

I believe this is addressed in the latest version.
I found a couple of other unrelated issues during testing, and these will also be addressed soon.


Duplo 25436 TF: S3: Replication: Update of 'Delete marker replication' shows no changes

Overview
Removed update context
Summary of changes
Update not supported , removed update context
This PR does the following:

Made rule and sub attribute force new and removed update context
Updated documentation

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ✓] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-25436 TF: S3: Replication: Update of rule name shows update in place instead of 'forces replacement'

Task linked: DUPLO-25447 TF: S3: Replication: Update of 'Delete marker replication' shows no changes


feature request: add task dependency support

Hello!
It would be nice to support the native depends option, which allows one task to be dependent of another. It helps manage a project better.
And if possible, showing dependency diagrams makes it more clear to oversee a project.
:smile:
best regards,
linusboyle

Hello!
Last week I've been working just on this. I'm polishing a set of patches that implements this functionality.
Some changes that I've introduced:

In 'task' view there are three new columns: task numeric 'ID', a 'dependencies' column pointing to blocking tasks ID and (not for this purpose, but my personal use of this app) an 'urgency' column.
Dependencies listed in dependencies column are hyperlinks to trigger a minimal JavaScript couple of functions that displaces the page view to the blocking task clicked, and temporarily changes td's background of tasks ID column's corresponding cell.
-Again, for an effective use of this new functionality there is a new 'tasks' subview showing tasks given by Taskwarrior when queried "+UNBLOCKED status:pending".

I'm a newbie in Ruby, but this code is miraculously cleanly written, so is very easy to patch. I'll tidy up the patch and send it.
__
novdomo

@novdomo great job! can't wait to have a try :+1:

@novdomo Any update on its status?

@novdomo are you still around?


running result

I followed your instructions and ran your code, but the only thing that came out of the run was what is shown in this image below

Hello !
That normal ! if you look at gazebo you're robot is supposed to move at the position (x=3,y=5)
Cheers

May I ask what command should be executed subsequently?

Is this one not visualized in code?

You will first need to launch a gazebo world with turtlebot3.
$ export TURTLEBOT3_MODEL=burger $ roslaunch turtlebot3_gazebo turtlebot3_world.launch
Then you can rosrun the package for potential field.

Could you tell me how to define the end point and how to start the algorithm to plan the path? Sorry to bother you all the time

对不起，我是想问怎么定义起点，当我运行的时候，无论怎么定义终点，小车一直在下面的图片中的位置旋转，不会改变

You can check on Rviz the direction of the force applied (Repulsive and Attractive).
Might be useful :D

I tried to do it yesterday, but I still don't understand how to view the direction of the force applied (Repulsive and Attractive) in Rviz.


[RHCLOUD-21109] Refactor of constants in middleware/headers/headers.go

this PR contains:

rename of constants from headers.go from upper case style into camel case style
replacing strings with existing constants (only related with constants from headers.go)

refactor of rest of constants will be solved in next PRs
JIRA: RHCLOUD-21109

LGTM, although I would vote for removing the *key suffix from the constants.

the idea here was that values in these constants are keys, but I am ok with both options 😁😁😁

I'm kind of with mikel on this one - I would prefer them just h.ParsedIdentity.
The main reason I say that is because like in the net/http standard library the constant status codes are http.StatusOK rather than http.StatusOKCode or something like that. It's just implied that they are codes.

🤔 what about to add to these constants the "Xrh" prefix to distinguish between e.g. account number or org id as constants for "x-rh-sources-account-number" or "x-rh-sources-org-id" from headers and fields e.g. in Identity struct and other places where we are using these names
// Identity is the main body of the XRHID
type Identity struct {
	AccountNumber         string    `json:"account_number,omitempty"`
	EmployeeAccountNumber string    `json:"employee_account_number,omitempty"`
	OrgID                 string    `json:"org_id"`
...

I'm kind of with mikel on this one - I would prefer them just h.ParsedIdentity.
The main reason I say that is because like in the net/http standard library the constant status codes are http.StatusOK rather than http.StatusOKCode or something like that. It's just implied that they are codes.

thinking what about to add to these constants the "Xrh" prefix to distinguish between e.g. account number or org id as constants for "x-rh-sources-account-number" or "x-rh-sources-org-id" from headers and fields e.g. in Identity struct and other places where we are using these names
// Identity is the main body of the XRHID
type Identity struct {
	AccountNumber         string    `json:"account_number,omitempty"`
	EmployeeAccountNumber string    `json:"employee_account_number,omitempty"`
	OrgID                 string    `json:"org_id"`
...

But wouldn't that be covered by the module's name? I mean:
headers.OrgId // I know we're using the x-rh-sources-org-id header here.

In the case of the identity struct...
identity.OrgId // I know we're using the identity field's value here.

Maybe there is a place where we are using both and it is not clear enough?

I believe it is covered by the module's name ...  I wanted to make it clear before I started changing in so many places

constants renamed ("key" suffix removed)

I'm okay with your suggestions :+1: . As per github.com/golang/go/wiki/CodeReviewComments#initialisms:

Words in names that are initialisms or acronyms (e.g. "URL" or "NATO") have a consistent case. For example, "URL" should appear as "URL" or "url" (as in "urlPony", or "URLPony"), never as "Url". As an example: ServeHTTP not ServeHttp. For identifiers with multiple initialized "words", use for example "xmlHTTPRequest" or "XMLHTTPRequest".
This rule also applies to "ID" when it is short for "identifier" (which is pretty much all cases when it's not the "id" as in "ego", "superego"), so write "appID" instead of "appId".
Code generated by the protocol buffer compiler is exempt from this rule. Human-written code is held to a higher standard than machine-written code.


Change doc theme to furo

Preview for the discussion in #73

This looks really nice! I like it much better than the previous theme. One minor comment, can you move the API sentence down on the main page as well? Otherwise LGTM!

And maybe the title could just be "SleepECG" without "documentation"?

Ready to merge?

yes!

Thanks @hofaflo!


Add support for virtual custom biomes

SpongeAPI | SpongeCommon | SpongeForge
This adds support for creating custom biomes which exist only during generation, afterwards they are stored as an existing non-virtual biome. This can be used to support more varied generation easier without creating full blown custom biomes which would require client modifications as well.

I'll be merging this tonight if no issues.


Ability to specify which slack channel Jenkins job sends to

Your checklist for this issue

[ x] Jenkins version

[ x] Plugin version

[x ] OS

Description
Jenkins version - 2.73.2
Plugin version - 2.23
OS Ubuntu
I am currently able to configure my Jenkins to send to a slack channel. What I was wondering is if it is possible to configure multiple channels and specify per Jenkins Job what channel to send to?

Yes in the advanced option for each job you can configure it


Expose KonnectivityTunnel as feature gate in shoot spec

How to categorize this issue?

/kind enhancement
/priority normal
What would you like to be added:
Expose KonnectivityTunnel as a feature gate in the shoot spec configuration.
Why is this needed:
The KonnectivityTunnel is another solution for the seed to shoot communication which has a lot of benefits over the OpenVPN tunnel solution, especially for private setups as is mentioned here. At the moment the  KonnectivityTunnel can be enabled via featureGates in the gardenlet configuration.
Since this feature is not stable and we are depending on the upstream, we can't replace the OpenVPN tunnel solution with it. But it would be good if we can enable it in the shoot spec via a featureGate, to use it for testing or non-productive clusters. This would make setups in private zones much easier and it would not be needed to build provider specific solutions as for example mentioned here for the gcp-provider.
/cc: @stiller-leser, @dkistner

As discussed, let's make it configurable via a shoot annotation, e.g. alpha.konnectivity-tunnel.shoot.gardener.cloud, besides the Gardenlet configuration mentioned in the issue description. (/cc @rfranzke)


Support upsert url parameter in BatchPoster inventory tasks

Add support to BatchPoster to use upsert=true when needed.

Closed by #804


[Search] Revert Beta changes

This change removes beta-only features from the Search client. It's intended to be rebased onto main regularly, and GA releases ship from this search/ga branch. All changes to main should extend to this branch to the extent that they don't change the API surface.
Open questions:

How to prevent this branch from becoming stale/automate merges. Considering a GitHub Workflow to rebase on each commit to main and automatically merge. It could open a PR for manual review in the event that a commit to main modifies the search branch.
How frequently to run CI pipelines on this branch.

Would migrating to core-client break users that depend on core-http?

Would migrating to core-client break users that depend on core-http?

I believe the idea is that core-http-compat takes care of this

/azp js - search - ci

/azp run js - search - ci


Project setup guide

Hey,
I just started using the plugin and wanted to make some changes or fix bugs that I encountered.
Like other people (https://github.com/OpherV/gitflow4idea/issues/63) I encountered a few minor obstacles with setting up the project, so I wrote down what I did to set everything up for development.
It's not perfect but it should get people who are interested running. Some things can certainly be optimized, for instance I'd suspect there is a better way to change the module type besides editing the IML, but I can't find that option in the IDEA UI anywhere (I'm probably just blind ;)).
As far as setup goes: Maybe it would make sense to integrate the git4idea.jar into the project directory? That way the setup can use relative paths (which makes setup easier if you bundle the IML) and everyone has the same JAR (no version conflicts; though I dont think git4idea changes much nowadays).
Alex

That's awesome! Thanks @alextsc  :D
I'll go over the PR soon to intergrate
Regarding bundling the git4idea.jar - I think that's risky. First it layers another burden of keeping the jar  updated in this repo (not to mention the sin of including a binary in the source...) In addition it will create problems further down the road if git4idea DOES happen to change in an EAP and we need to support both the release version as well as the EAP one

Yeah it was just an idea, of course it has drawbacks. Thanks for looking into it. I also sent a few other things and will probably do a few more fixes in the coming days.


[Question]: Self hosted agent can't find java environment variable: JAVA_HOME_17_x64

Task name
Maven@3
Task version
No response
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
azul/zulu-openjdk
Question
Im using self hosted agent with image: azul/zulu-openjdk where is java openJDK 17 preinstalled and environment variables already set:

JAVA_HOME_17_x64=/usr/lib/jvm/zulu17-ca-amd64/
JAVA_HOME=/usr/lib/jvm/zulu17-ca-amd64/

My task looks like this:

    - task: Maven@3
      displayName: 'sonarAnalysis'
      inputs:
          mavenPomFile: 'pom.xml'
          mavenOptions: '-Xmx1024m'
          javaHomeOption: 'JDKVersion'
          jdkVersionOption: '1.17'
          jdkArchitectureOption: 'x64'
          goals: sonar:sonar ............

and it gives me this error:

##[error]Unhandled: Failed to find the specified JDK version. Please ensure the specified JDK version is installed on the agent and the environment variable 'JAVA_HOME_17_X64' exists and is set to the location of a corresponding JDK or use the [Java Tool Installer](https://go.microsoft.com/fwlink/?linkid=875287) task to install the desired JDK.

but the variable JAVA_HOME_17_X64 is already set. What could be wrong?

@ser789654, could you check please that the env variable JAVA_HOME_17_x64 is set?
I noticed that only JAVA_HOME variable is set in Dockerfile
Can you add a step with variable printing?
- task: PowerShell@2
  displayName: Display the environment variable JAVA_HOME_17_X64 value
  inputs:
    targetType: 'inline'
    script: echo $env:JAVA_HOME_17_X64

Create a file .env in the root directory of the runner and add the variable there:
JAVA_HOME_17_X64=/usr/lib/jvm/java-17-openjdk-amd64
I had the same problem with our runners

@ser789654, could you confirm whether the issue is resolved or not?

I'm closing the issue, feel free to open it if it's still relevant to you.


UnifiOS v4.1 - certificate locations and configuration mechanism appear to have changed.

I know it is still in early access, but wanted to give an FYI.
The deployment script is failing silently for me, for at least the frontend - I don't use RADIUS or the hotspot. No error message, but the cert is not put into use.
In doing a little digging, the yaml format and location looks different. I think the frontend certs are now controlled by /data/unifi-core/config/http/local-certs.conf
When I uploaded my certs using the Unifi UI, they were renamed to a GUID and placed in /data/unifi-core/config/ and that's what local-certs.conf I pointing at.
The format of local-certs.conf is different from the overrides too.
Rather than this it looks like this for me.
ssl_certificate     /data/unifi-core/config/<GUID>.crt;
ssl_certificate_key /data/unifi-core/config/<GUID>.key;

I tried hand-editing local-certs.conf to point to the ubios-cert location, but something is resetting it back to the previous guide cert when I restart the frontend.
Model:       UniFi Dream Machine PRO
Version:     <IP_ADDRESS>27
Network App Version: 9.0.106
script output - it did
root@UDMPro:/data/ubios-cert# ./ubios-cert.sh deploy-webfrontend
# Supported firmware: 4.1.11 on UniFi Dream Machine Pro. Moving on.
# Checking for new certificate to be deployed to web frontend.
root@UDMPro:/data/ubios-cert# ./ubios-cert.sh deploy
# Supported firmware: 4.1.11 on UniFi Dream Machine Pro. Moving on.
# Deploying certificates and restarting UniFi OS
# Checking for new certificate to be deployed to web frontend.

Thanks for pointing this out. I stopped running EA firmwares - reasons...
As containment action, the deploy.sh script now checks if the firmware version is 4.1 and will bail out.
I'm a bit on the edge here. I'm getting bored chasing undocumented changes by UI. Maybe I will change the whole approach and just grab certificates via Let's Encrypt and feed them to Glenn's script. Let's see what the Christmas break brings.

I appreciate the work you've put in. I can imagine how frustrating that would be  If it helps, I just noticed that the GlennR scripts now support DNS challenges.

Yep that's true but GlennR removed most of DNS providers on UI hardware only. So the provider I need is not supported.
I'm a hobbyist so I just might live with it.
Merry Christmas, by the way!


Snapshots

This PR:

adds create-snapshot
adds delete-snapshot
adds list-snapshots
adds create-snapshot-schedule
adds delete-snapshot-schedule
adds list-snapshot-schedules
fixes readme by adding the description get-tablets-for-table
restructures readme by moving snapshot command details into a separate section
does not treat responses with errors as errors anymore - error handling for protobuf GetError() needs to be reimplemented
fixes a bunch on unrelated godoc comments

Left to implement:

[x] create-snapshot-schedule
[x] list-snapshot-schedules
[x] restore-snapshot-schedule
[x] restore-snapshot
[x] export-snapshot
[x] import-snapshot

Snapshot support at the most basic level. Ready to merge.


retry rtiddsgen(_server) invocation if it fails with a return code

When the buildfarm rebuilds the majority of the Debian packages of a ROS distro it frequently happens that packages containing messages fail to build.
The invocation of rtiddsgen_server returns with a non-zero code and the following error message (from http://build.ros2.org/view/Ebin_uB64/job/Ebin_uB64__action_msgs__ubuntu_bionic_amd64__binary/35/consoleFull):

ERROR com.rti.ndds.nddsgen.Main Fail:  com.rti.ndds.nddsgen.Main$ArgumentException: File /tmp/binarydeb/ros-eloquent-action-msgs-0.8.0/obj-x86_64-linux-gnu/rosidl_generator_dds_idl/action_msgs/msg/dds_connext/GoalInfo_.idl doesn't exist. Please make sure that you have specified the correct path.

The logic already retries the invocation it finished with a rc 0 but didn't generate the desired files (https://github.com/ros2/rosidl_typesupport_connext/blob/2a56f0661e903fceca8f321ca5a09ebb04d8d146/rosidl_typesupport_connext_cpp/rosidl_typesupport_connext_cpp/init.py#L67-L88). But that doesn't seem to be the problem here. The command fails with a non-zero return code.
The logic already explicitly checks that the IDL file passed to the generator exists (https://github.com/ros2/rosidl_typesupport_connext/blob/2a56f0661e903fceca8f321ca5a09ebb04d8d146/rosidl_typesupport_connext_cpp/rosidl_typesupport_connext_cpp/init.py#L38) but the invocation still results in the above error message.
I can't reproduce the problem locally and newly triggered builds of the same job usually pass. So this patch is mostly an attempt to recover from this error condition and hopefully will make the binarydeb jobs pass reliably on the first attempt.
It could be a race deleting the IDL after the initial check (hence the new additional check after an invocation failed) but it is unclear why the file would be deleted. The other possibility is that the code generator fails for whatever other reason but reports a bogus error message...

I think it would good to open a issue tracking the problem and reference it in the code.

I think it would good to open a issue tracking the problem and reference it in the code.

I added HACK(...) to the new retry logic in f1ff333c730fe8d45fc4c3525a3eefce6773b4b8. I would only open a new ticket after seeing the results of the rebuild depending if they confirm or debunk the hunch.

Ah, I think this is the relevant ticket: https://github.com/ros2/rosidl_typesupport_connext/issues/7

Let's see what happens I suppose.

(Assuming there is no logic bug in this patch) worst case should be a no-op when the generator passes and take extra time when it repeatedly fails.
Sanity check that it still builds on all platforms:

Linux
macOS
Windows

@mjcarroll Can you approve this being backported and released into Eloquent?

Fast forwarded the commit from master to eloquent, released 0.8.3, and fast forwarded the release from the eloquent branch back to master. So both branches are still in sync.

A build where the anticipated failure happened: http://build.ros2.org/view/Ebin_uB64/job/Ebin_uB64__rcl_interfaces__ubuntu_bionic_amd64__binary/42/consoleFull
But all retries failed with the same error message even though they passed the assertion that the passed IDL file does exist between each attempt :worried:


Remove some Nash restrictions

market_pair can be None for account trades and orders
Implement get_all_open_orders

nash-rust PR https://github.com/nash-io/nash-rust/pull/39

LGTM


Old links in descriptions

Issue Description

The short description on the main page of this repo links to .com instead of .org
The organisation page links to http instead of https (sidenote: Should it say fCC is located in SF?)

@QuincyLarson I think that you and Berkeley are the only ones that can change this.
Screenshot

2.

@systimotic Nice catch. Fixed!


Emit prometheus metrics from kuberay control plane

Add kubernetes service for operators and backend service for scratching
Update ServiceMonitor to match service definiton
Add Grafana Dashboards for backend service and operators

Why are these changes needed?
This is used to expose kuberay core component's metrics and it will help user to better monitor healthiness of the components.
Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

Screenshots

Backend

Operator

I got two likes but no code review feedbacks.. Since this is straightforward, let me merge this and prepare the ready to use dashboard. If user has feedbacks later, feel free to cut new issue and mention me to look at it.


python312Packages.sqlalchemy-mixins: add aiosqlite

ZHF: #352882

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352980

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.sqlalchemy-mixins
python311Packages.sqlalchemy-mixins.dist
python312Packages.sqlalchemy-mixins
python312Packages.sqlalchemy-mixins.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352980

aarch64-darwin

:white_check_mark: 4 packages built:

python311Packages.sqlalchemy-mixins
python311Packages.sqlalchemy-mixins.dist
python312Packages.sqlalchemy-mixins
python312Packages.sqlalchemy-mixins.dist


How can I run a notebook non-interactively?

What do you mean non-interactively?

run all cells from the menu (do we need maybe a FAQ entry for this)
we should audit that every notebook can be run all cells and somehow hide/mark any interactive cells where such a run would otherwise stop?

originally meant in a way that would run a long-running notebook without the SMCE culling the user.  Not sure if this has an updated answer, but there was discussion some months ago about adding a button which would take a notebook and automatically convert it to a script and run the script.  Not sure if there is a current plan for users to be able to run long-running notebooks.

Ahh, ok, so then this is both documentation and adding significant technical enhancements

They can be separate issues, for this repo, the issue is need of documentation for current best practice.  I just don't know what that current best practice should be until that button becomes available.


Support Kafka 3+ by upgrading Sarama

[ ] Upgrade Sarama from v1.26.4 to latest.
[ ] Make sure Kafka 3+ is working well.

Works with Kafka version 3.2.0 👍

Thanks for the input @scpsx


Fixed a bug where options was written directly

Had to use Object.assign() to do an actual clone/copy to avoid copy by ref
Fixes #495

Whew. All this time I was missing the obvious. Writing directly to a function argument = bad. And of course, doing simply let o = options wouldn't have been enough as it would've been just a reference.

Actually, let me clean this up so it uses lodash instead of Object. And I'll make the code a little better.

Ok, much better. Take a look and merge at your discretion.

@jagi Any rough idea when this fix will be pushed to Atmosphere?

Ok I will publish it as a bug fix release

Published. Sorry that it took so long time


Reference links are broken

Better description: Sometimes the reference on a variable is not a link. When this happens we shouldn't put it in a <a href.


[1.18-21w43a] Entering portals crash  game

Crash report: https://gist.github.com/kwpugh/b483deba282078c629674a4b57597689
Looks like  Mojang changed a  class name.

beta45v2 was just pushed with a fix for 21w43a

Confirmed, just tested, no crash.  Thank you.


1.39 Release Zip - Errors on npm run build

Download and unzip 1.39, run npm install, then npm run build:
[09:15:11] Error: ENOENT: no such file or directory, open 'Apps/.jshintrc'

Brought up on the forum here: https://groups.google.com/forum/#!searchin/cesium-dev/install|sort:date/cesium-dev/7HnQ7bs9Q88/qZGyGMcwAQAJ

The release zip has never been meant to allow for building Cesium from source.  If it worked in the past it's by accident.
Anyone who wants to build Cesium should either clone our GitHub repository or download the source zip from the release page.
We can always change the policy to support building from the release zip in the future, but I don't think it's worth the extra overhead.

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/#!searchin/cesium-dev/install|sort
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/issues/5967 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:


Add url property to diagnostic

fix #4142
Every diagnostic can now define a url pointing to a documentation with more information on how you might have this diagnostic and how to resolve it

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@typespec/compiler

Show changes

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


ci: Add delay between publishing powerpack-detach before powerpack

powerpack depends on powerpack-detach so if you try to publish powerpack too soon after powerpack-detach it will fail.

Fixed in https://github.com/rossmacarthur/powerpack/commit/9695392445f23b15e9dafcb40d9646aafccab7f4


[low priority] Genrate static website

This is just  crazy (and probably useless) idea. Toto based website is in fact basically static, so we can have a special rake task which will generate "static" version of website, so that would be possible to use with almost any hosting platform :)) and with gh-pages of github as well.

This sounds like an amazing idea.  Publishing a toto site to S3 would definitely be my preference!  I'll be watching!

Why not just use a static site generator then? There's like ten
million if them? Try octopress.
On 19 Oct 2011, at 05:08, Benjamin Charity
<EMAIL_ADDRESS>wrote:

This sounds like an amazing idea.  Publishing a toto site to S3 would definitely be my preference!  I'll be watching!
--
Reply to this email directly or view it on GitHub:
https://github.com/cloudhead/toto/issues/99#issuecomment-2451856

I can't say for everyone, but I feel two opposite feelings about such static generators. So first I would like to anser Andrew's question... I don't want to use Jekyll, because I don't like it's structure. To be honest now I realize that I want a little bit different structure of files even for toto (and I'll repspect my wish in my own blog if I'll have time to sit down and write it) - I can surf them without web and as I use my blog mostly to write down things I don't want to forget - that's pretty useful for me (to have good structure, which is goodlooking as well :)).
Why I might want static site generator? Because it would be possible to deploy static website on any hosting and it will be just faster than anything. On another hand I might want to still have dynamic site and it seems easier to me to modify such code.
After all right now I relized, that either I'm pregnant, or probably got sick. I can't decide what I like more :)) static site seems to me good solution because it requires only plain HTTP server, so it cn be hosted anywhere. Dynamic site seems to me good solution because it fun and keeps directory clean (out of compiled things and so on)...
So, I guess, after all I think that static site generator is good thing. So providing an easy way to call precompiler will be nice thing :)) But I don't think it will be implemented in toto :)) So closing an issue.


Add Corsair iCUE 3.30.89

Microsoft Reviewers: Open in CodeFlow

yeah took me a bit to figure that out as well! here i thought my VM was acting up :)


Cannot have multiple tabs on one page (with fix)

I needed to have multiple tab controls on one page, where each tab contains part of a form bound to a view model using knockout.js.
To make it work, I edited the bootstrap-tabs.js file and changed line 54 from:
$href = $(href)
to:
$href = $ul.parent().find(href);
Thanks,
Scott

this is fixed in 2.0


Context selector placeholder text

Description
The placeholder text in the context selector is too long / The input field is too short / The X crashes with the text

I'm also not able to close the dropdown options when I click outside of the dropdown.

Also the X is hidden, but still clickable?

I have reported the X bug to core


Improve GitHub Actions for pull requests

See https://github.com/Senzing/community-roadmap/issues/71

Pull requests:

https://github.com/Senzing/connector-neo4j/pull/50


Consolidation and consistency in "outer loop" variables

This issue documents a point raised by @rickecon that OG-USA has some inconsistencies in the GE loop variables.
In particular, SS.SS_fsolve() and SS.SS_solver() can have if-statements consolidated and can use T_H in the set of variables used to determine a general equilibrium, except for in the base of baseline_spending=True, in which case, Y will replace T_H in the set of GE variables.
Relatedly, the GE loop in the TPI.run_TPI() includes w in the computation of TPI_dist.  w should be removed from this calculation since it is pinned down by r.

This issue was resolved with PR #455


Updated all TODOs

Description
Updated Todos in the code to point directly to issues in github
Why
I want to make sure we have a full description of the problems and proper discussion, but still track it in the code.

@kefniark This is just comments, I will merge it in.


Typos in age dictionary will lead to "not provided"

Switch to 'raw' view to see the highlighted lines:
https://github.com/monarch-initiative/phenopacket-store/blob/f23540248e6d174242eb2cc3e6e962f0377e8cfc/notebooks/FBXL4/FBXL4-curation.ipynb#L641C10-L644C36
Typos monhts and mohts instead of months e.g.
'10 monhts': "P10M",

@julesjacobsen
The idea of this dictionary was to be able to take original data with all of its warts and convert it into correct phenopackets. In this example, the original data has '10 monhts' and we convert it to "P10M".
In this particular case it would have been easier to fix the original data since it only occurs once. A more common use case is just that somebody is using a correct but idiosyncratic string such as "10 mon. &3d" some something like that.
Not sure if this is exactly what the bug was?

Ahhh! Sorry, I misunderstood the purpose of this. I didn't realise that it was for correcting mistakes.