Upstream response time metric

I haven't been able to find any metric in Prometheus that gives me the upstream response time for a certain service in Istio. According to the documentation, only istio_request_duration_milliseconds (request duration) is available. But this also includes the client request time, and will be high if there is a network delay on the public internet, for example, or if the client is uploading a big file. We wanna use this metric to configure alerts if our services in Istio are responding slowly.
Actually the name istio_request_duration_milliseconds doesn't match with what I found in Prometheus which is istio_request_duration_seconds_bucket, but maybe that can differ.
An alternative I considered was to scrape the Envoy request logs for more information there, but it would not be nearly as convenient as having the metrics in Prometheus just like the request duration.
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[X] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

istio_request_duration_milliseconds is captured at both client side and server side. See the Reporter label which tells you whether this time series is from source or destination.
Which istio version are you using? The metric used to be istio_request_duration_seconds but the name and unit has been updated to istio_request_duration_milliseconds for quite a while (maybe two or three releases ago) after we migrated to telemetry v2.

istio_request_duration_milliseconds is captured at both client side and server side. See the Reporter label which tells you whether this time series is from source or destination.
Which istio version are you using? The metric used to be istio_request_duration_seconds but the name and unit has been updated to istio_request_duration_milliseconds for quite a while (maybe two or three releases ago) after we migrated to telemetry v2.

I don't think the istio_request_duration_milliseconds reported by destination is the same as X-ENVOY-UPSTREAM-SERVICE-TIME. The metric could be much higher than upsteam service time in access log.
We actually need to send a alert when X-ENVOY-UPSTREAM-SERVICE-TIME is high.

The metric could be much higher than upsteam service time in access log.

Can you share more about your observation? How much difference did you see? request_duration metric tracks the duration between downstream request stream establishment and completion, which should be really close to the upstream request stream duration, since we'd expect that sidecar adds very little latency (1 to 2 milliseconds at tail).

The metric could be much higher than upsteam service time in access log.

Can you share more about your observation? How much difference did you see? request_duration metric tracks the duration between downstream request stream establishment and completion, which should be really close to the upstream request stream duration, since we'd expect that sidecar adds very little latency (1 to 2 milliseconds at tail).

when the upstream service time is 2ms, the istio_request_duration_milliseconds reported by destination could be 1023ms.

It surprises me that upstream service time and duration would have such a big difference. upstream service time tracks the time between downstream request finishes and upstream response received. the duration metric tracks duration of the whole downstream request (from stream established to stream destroyed). The network has to be really slow to introduce such a big difference (1ms vs 1000ms). Does it always happen on every access log entry that you captured?
Alternative is that envoy generates an upstream_rq_time metrics, which should be close to upstream_service_time. You could probably consider make envoy expose that (https://istio.io/latest/docs/ops/configuration/telemetry/envoy-stats/) and build alerts based on that.


GH-460 Avoid variable panel exponential updates

Fixes #460

Applied to main (=2.1) and branch 2.0.


Three RFPs for "easy" crypto implementation

I think https://github.com/arkworks-rs/curves/issues/17 should be straightforward if you know both the substrate wasm boundary and elliptic curves, but probably nobody knows both.

I think https://github.com/kobigurk/aggregatable-dkg/issues/1 should be easy, but it'd fall more to the original authors, but if someone were interested..

I implemented deliniearized witness multi-signatures in https://github.com/w3f/schnorrkel/blob/master/src/musig.rs in the commit https://github.com/w3f/schnorrkel/commit/fa6c35f832a4ae6f45e9c8e6858d90d1e2789fc7#diff-6ed16ffe933791b81e8340007a820ced7a47171ced9ce5378262d152951ec20d but at that time I'd no security proof so I kept the code encouraging the three round trip version.
We now have a security proof in https://eprint.iacr.org/2020/1245 and Isis Lovecruft did a nice implementation of the two round trip version in https://github.com/isislovecruft/frost-dalek/ so we should really rip out my code and replace it with theirs.  I could do this but so could many other people.
A second implementation seems to be progressing in https://github.com/ZcashFoundation/redjubjub but its further from ristretto

I'd suspect generous gitcoin level bounties suffice for the all three of these.

This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/implement-crypto-primitives-and-confidential-transfer-pallet/2569/1

I'm closing this issue since it has been open for a very long time.


[BUG] OpenID: Global logout does not disconnect Opensearch Dashboards

What is the bug?
When using OpenID, the user is not automatically disconnected form Opensearch Dashboards when the user disconnects from the SSO in another application.
How can one reproduce the bug?
Steps to reproduce the behavior:

Connect to an application using OpenID
Connect to Opensearch Dashboards using OpenID (Token is retrieved and connection is automatic)
Do some interesting things
Disconnect from the first application. This invalidates the SSO token and propagates the logout request to any applications
=> User can still use Opensearch Dashboards.

What is the expected behavior?
The user should be disconnected from Opensearch Dashboards. Dashboards should display the OpenID login page.
What is your host/environment?

OS: RHEL 8.4
Opensearch 2.5.0

[Triage] @RyanL1997 could you look into this issue, I don't think logic is supported in this way and it would be good to confirm - thanks

[Triage] Marking as triaged since @RyanL1997  is dealing with several interconnected issues related to OIDC.

Hi, @51CGO Thank you for filing this issue. I have confirmed this behavior. Yes, at least for now, this is an expected behavior.
This behavior is due to the fact that the logout process is not synchronized between the IdP and OpenSearch Dashboards. In the OIDC flow, after a user is authenticated by the IdP, OpenSearch Dashboards receives an access token. The access token is then used to authenticate requests to OpenSearch. However, OpenSearch Dashboards does not continuously communicate with the IdP after the initial authentication. As a result, it is not aware of any subsequent logout events initiated by the user or by the IdP.
According to some research I did, this is behavior can be improved by implement a Single Logout feature which can be provided by some IdPs that allows users to log out from all the Service Providers that they have logged into with a single action. But, not all IdPs support SLO.  So do you mind to provide some specific reasons and use cases with some details of which IdP you are using and after that maybe we can convert this issue into a feature request?


Request for Steelseries Apex 7 support

Please add support for the following device:
Device Name: SteelSeries Apex 7
Device Website: https://steelseries.com/gaming-keyboards/apex-7?switch=red
Currently works best through generic keyboard (preferred keyboard: none), however the ? and the ` keys cant seem to be controlled and stay locked to their previous colour. I did try the currently supported steelseries layouts however the closest one, Apex M750, results in the steelseries (APP/FN key) also becoming disabled.
OpenRGB appears to have support for this keyboard already, and I have it installed, but I do not use it for my keyboard lighting. I am specifically using Aurora to steelseries GG direct.

Did you try different "Preferred Keyboard Layout" options?
Also that part is a bit bugged and some selections may need restart of Aurora to work best

United States is what matches my layout correctly. However I have run through others and it still makes no difference. I have also gone through all the keyboard layouts too, with no luck. In all cases the "?" and "~" keys still fail to be recognized.
Trying the RGB.net device seems to have all keys light up including the steelseries one. But then no further animation, just what the initial setting was.
OpenRGB works fine except the steelseries key and I do have to disable any lighting via SteelSeriesGG or it will flicker between them.
I don't know if this is any help but the below is what appears in the RGB.net remapper (although no remaping can be done)

Revisiting this I have managed to get openRGB working by remapping the steelseries key to the app key for the layout, and this seems to work with having all keys light up now.

I also noticed that the steelseries (rgb.net) also works with all keys by default and animates, although that one also makes the mouse bright orange for some reason. openRGB does not support the rival 5 yet (despite an issue with all the info seemingly open for a year now).

looking at the screenshot, you are on outdated version. An old version had updater issue. You should update Aurora manually

Will be doing that. on an older version currently that has everything working i want. Latest version doesnt have official support, but likely i can do the same adjustment to get it to work.

what is the removed feature?

I am currently sitting at v266 due to the Elite Dangerous profile not working after that version https://github.com/Aurora-RGB/Aurora/issues/237

Thanks to recent updates I am now on the latest version.
Using the Apex M750 layout it now seems that all keys function correctly without remapping. I am using openRGB, but the steelseries devices seem to work as well - just that they also try to control the mouse I have as it is also steelseries (not supported by anything)
Happy for this on to be considered closed


Example script for showing flag on slack status

Tested via webcam (spot the green dot!)

Haha this is a very smart testing system


Execution time for retrieval a message

Good morning,
I have an application where I would like to retrieve my mails, but I noticed that the ->getMessageByMgsn() or ->getMessageByUid() function can take a long time to run with mails with attachments. The execution time is proportional to the size of the mail and so I have mails that can take more than 30 seconds.
Here is an example below, each item is a mail with its size first following recovery time.
$t1 = microtime(true);
$executionTime = array();
for($i = $info['exists']; $i > $info['exists']-5 && $i > 0; $i--){
   $message = $query->getMessageByMsgn($i);
   $t2 = microtime(true);
   $executionTime[$i] = array($message->getSize(), $t2 - $t1);
   $t1 = $t2;
}
var_dump($executionTime);

Is that a problem you noticed?
Is there a way to solve this problem?

Hi @frizzcarambar ,
many thanks for your report. I'm afraid there isn't much I can do about it - the mail server itself as well as your connection to the server are the bottlenecks. You could speed things up for sure, by working with the protocol directly. But requesting and fetching data still takes some time.
However, please feel free to prove me wrong. Pull requests are always welcome :)
Best regards & happy coding,


OpenCV: FFMPEG: tag 0x44495658/'XVID' is not supported with codec id 12 and format 'mp4 / MP4 (MPEG-4 Part 14)' OpenCV: FFMPEG: fallback to use tag 0x7634706d/'mp4v'

anyone like me can't output video properly?
default setting, the error shows
OpenCV: FFMPEG: tag 0x44495658/'XVID' is not supported with codec id 12 and format 'mp4 / MP4 (MPEG-4 Part 14)' OpenCV: FFMPEG: fallback to use tag 0x7634706d/'mp4v'
I also tried the following
v2.VideoWriter_fourcc(*'mp4v)
still can't yield  video properly.

This seems an opencv issue. Make sure you installed opencv by pip install opencv-python. If that's the case, can you load a video correctly using openCV?

This seems an opencv issue. Make sure you installed opencv by pip install opencv-python. If that's the case, can you load a video correctly using openCV?
Thanks for the reply @xingyizhou

We can forget about the problem above
but there is another error happend
here is my command code
python demo.py tracking --load_model ../models/coco_tracking.pth --demo ../videos/nuscenes_mini.mp4 --save_video
it seems like the loading was correct for the first 40 frames, but in the last maybe not the last frame, opencv loads NoneType.
I am pretty sure I installed opencv through pip install opencv-python and the version is 4.2
what do you think ?
<class 'numpy.ndarray'>
<class 'dict'>
frame 39 |tot 0.036s |load 0.000s |pre 0.011s |net 0.021s |dec 0.002s |post 0.001s |merge 0.000s |display 0.003s |
write is ok
<class 'numpy.ndarray'>
<class 'dict'>
frame 40 |tot 0.036s |load 0.000s |pre 0.011s |net 0.021s |dec 0.002s |post 0.001s |merge 0.000s |display 0.003s |
write is ok
<class 'NoneType'>
Traceback (most recent call last):
  File "demo.py", line 122, in <module>
    demo(opt)
  File "demo.py", line 66, in demo
    ret = detector.run(img, input_meta)
  File "/home/workplace/centertrack/src/lib/detector.py", line 69, in run
    image = image_or_path_or_tensor['image'][0].numpy()
TypeError: 'NoneType' object is not subscriptable

and I tried skipping all the last frame, no errors but the yielded video is blank, the file is only 258B which means output incorrectly. Could you provided me the opencv-python version you tested on ?

add this --resize_video  .mp4.mp4 is ok

add this --resize_video .mp4.mp4 is ok

yup, thanks I just though the default setting will be fine ....

add this --resize_video .mp4.mp4 is ok

add this：
--resize_video

Hello, were you able to solve this problem? I tried specifying video_h and video_w as well as the resize option, but both don't seem to work. I also get a .mp4.mp4 file - did you change this to .mp4?

添加这个 --resize_video .mp4.mp4 就可以了

添加这个： --resize_video

您好，这个在哪里添加啊


Development plan for voyage-4

I'd like to store a development plan in a separate issue. :page_with_curl:
We can collect, add, and discuss our ideas here until we will finally end up with MVP form.  :framed_picture:
Here is my insight on what we are able to accomplish. :muscle:

PS.
Also, I'd like to add a small change to our workflow - I want everyone to pick up a most attractive for him/her feature from the MVP and work on it.
This will help to ensure an unblocking behavior of our work. So that, everyone can continue of his/her own speed without waiting for a teammate to complete a piece of the app.
Of course, everyone support each other and help as needed.
For example, I'd like to do a migration from a state in containers to the Redux architecture. We agreed about this and I'm going re-factor the code for this migration, make PR, then you will review it.
If I'm stack at some point, I'm going to ask for help.
I expect that this voyage will be a challenge for us. We are going to work with more advanced instruments and we are in job search. (yes, me too)
I highly appreciate our clear and friendly communications and will be very happy to congratulate you with a new job. :smile: :star2: :fireworks:

As we agreed , our first step includes:

moving the app state to Redux,
discovering the capabilities of the free tier of Contentful,
setting up the environment for UI testing (Jest, Enzyme)


Refactor to use pytest

In particular, get rid of all the test-classes and use simple module-level functions.
http://pytest.org/

Nice idea. I'll look up the site.


Virtual DSM in a Docker container inside an unprivileged LXC container

I wanted to share insights into why "virtual-dsm" encounters challenges running within an unprivileged Proxmox LXC container by default and how the provided script addresses these issues.
Core Challenges:

Device Access: The default setup assumes access to certain device nodes, a luxury not available (by default) in the constrained environment of an unprivileged LXC container.
mknod Operations: "virtual-dsm" relies on mknod operations during its setup process, which is problematic within the restricted context of an unprivileged LXC.
LXC Configuration: Certain LXC configurations need adjustment to accommodate the specific requirements of "virtual-dsm."

Script Solutions:

Device Configuration: The script creates essential device nodes within the LXC container, overcoming device access limitations.
mknod Operations Bypass: The script modifies the "virtual-dsm" code to circumvent mknod errors, ensuring a smoother setup within the unprivileged LXC environment.
LXC Configuration Adjustments: The script fine-tunes the LXC container configuration to align with the expectations of "virtual-dsm."

Executing the script below on your Proxmox host (not within the LXC container) will pave the way for a more seamless "virtual-dsm" experience within an unprivileged LXC on Proxmox.
bash -c "$(wget -qLO - https://raw.githubusercontent.com/databreach/virtual-dsm-lxc/main/virtual-dsm-lxc.sh)"
Feel free to delve into the script for a detailed understanding, and don't hesitate to share your insights or report any observations.
Best,
databreach

It would be highly advantageous if you could devise a method to ensure seamless execution of "virtual-dsm" within an unprivileged LXC container, requiring no specific preconditions. The errors encountered when running the script under an unprivileged LXC container are as follows:
Reproducible Steps:
With a fresh installation of a Debian 12 Standard LXC container and default installation of Docker:
docker: Error response from daemon: error gathering device information while adding custom device "/dev/net/tun": no such file or directory.
After adding lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file 0 0" to the LXC configuration:
docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory.
After adding lxc.mount.entry: /dev/kvm dev/kvm none bind,create=file 0 0" to the LXC configuration:
docker: Error response from daemon: error gathering device information while adding custom device "/dev/vhost-net": no such file or directory.
After adding lxc.mount.entry: /dev/vhost-net dev/vhost-net none bind,create=file 0 0 to the LXC configuration:
Install: Downloading installer...
cpio: dev/net/tun: Cannot mknod: Operation not permitted
36797 blocks
ERROR: Failed to cpio /storage/dsm.rd, reason 2

After changing cpio -idm <"$TMP/rd" code of install.sh to ignore mknod errors:
Install: Extracting system partition...
tar: dev/net/tun: Cannot mknod: Operation not permitted

After changing tar xpfJ "$HDA.txz" code of install.sh to ignore mknod errors:
Install: Installing system partition...
ERROR: KVM acceleration not detected (no write access), see the FAQ about this.

After chown 100000:100000 /dev/net/tun + /dev/kvm + /dev/vhost-net on the Proxmox host:
Success!
Note: The script does not make use of the Proxmox host device nodes. Instead, new device nodes are created (using mknod) to secure the Proxmox host. The "virtual-dsm" device nodes can be found on the Proxmox host in the "/dev-CT ID" folder. These device nodes are also used in the lxc.mount.entry of the LXC configuration.
Docker Commands:
docker run -it --rm -p 5000:5000 --cap-add NET_ADMIN --device-cgroup-rule='c *:* rwm' --device /dev/net/tun --device /dev/kvm --device /dev/vhost-net --stop-timeout 60 -e ALLOCATE=N virtual-dsm:latest
version: "3" services:     vdsm:         container_name: vdsm         image: virtual-dsm:latest         environment:             CPU_CORES: "2"             DISK_SIZE: "6G"             RAM_SIZE: "4096M"             ALLOCATE: "N"         devices:             - /dev/kvm             - /dev/vhost-net             - /dev/net/tun         device_cgroup_rules:             - 'c *:* rwm'         cap_add:             - NET_ADMIN         ports:             - 5000:5000         volumes:             - /storage:/storage         restart: on-failure         stop_grace_period: 1m         tty: true

The initial script was a quick fix, altering the source code to enable "virtual-dsm" to operate within an unprivileged LXC container. However, a more refined solution has been developed, eliminating the need for such workarounds and ensuring compatibility with diverse use cases. A pull request for this improved version has been submitted.
Enhancements:
The pull request introduces a crucial enhancement: the ability to control the creation of device nodes. This feature empowers users to run "virtual-dsm" seamlessly within a Docker container inside an unprivileged LXC container, all without the necessity of modifying the source code.
Usage Note:
If users prefer or need to create the device nodes manually (e.g., in the case of an unprivileged LXC container), they can utilize the Docker environment variable DEV="N". This flexibility ensures a more versatile application of the script.
Device Configuration:
Please note that for successful execution, the tun, kvm, and vhost-net devices must be established on the Proxmox host. These devices should be granted LXC ownership and subsequently added as mount entries to their respective LXC containers. The initial script has been updated to simplify and streamline this process.
bash -c "$(wget -qLO - https://raw.githubusercontent.com/databreach/virtual-dsm-lxc/main/virtual-dsm-lxc.sh)"

Thank you for merging the improved version, and I appreciate your keen observation. You're correct; the workaround for /dev/tap devices in network.sh was not included in this pull request. After extensive testing, it became apparent that the DHCP mode is currently non-functional inside an unprivileged LXC container.
Even with the previously employed workaround, I encounter a persistent issue marked by the following error message:
char device redirected to /dev/pts/0 (label charserial0) qemu-system-x86_64: -netdev tap,id=hostnet0,vhost=on,vhostfd=40,fd=30: Unable to query TUNGETIFF on FD 30: Inappropriate ioctl for device.
Regrettably, this indicates that DHCP (macvlan) remains non-operational for the time being when the application runs within an unprivileged LXC container. I will try to identify and resolve the issue, but your expertise on this front (qemu) would be invaluable to pinpoint the root cause of this matter. If you have any insights or suggestions, they would be greatly appreciated.

Hi,
Sorry for the noob question here, what is the right process to make this work?
1: Create a LXC container with debian 12 + docker installed.
2: On the proxmox node run this: bash -c "$(wget -qLO - https://raw.githubusercontent.com/databreach/virtual-dsm-lxc/main/virtual-dsm-lxc.sh)"
3: Install virtual-dsm via docker and add "DEV="N" and then run it?
Again, sorry for the noob question.

Usage

Create a LXC container in Proxmox with your preferred distribution (e.g. template Debian 12 Standard).
On the Proxmox node/host execute the virtual-dsm-lxc script (requires root privileges).
Install Docker and run virtual-dsm within the LXC container using the DEV=N parameter.

Example
In this example we will setup virtual-dsm using multiple storage locations. The LXC disk will be used for installing Debian OS and storing the virtual-dsm Docker image. The first mount point will be used for installing virtual-dsm and is using the fast storage pool named nvme. The second mount point will be used for storing data within virtual-dsm and is using the slow storage pool named sata. Change the storage pools and disk sizes based on your own environment and preferences.
1. Create LXC container using Proxmox UI

General: Ensure Unprivileged container and nesting are enabled.
Template: Select debian-12-standard_12.2-1_amd64.tar.zst.
Disks: Allocate 8 of Disk size (GiB) for rootfs.
Disks: Press Add and allocate at least 16 of Disk size (GiB). In Path set /vdsm/storage1.
Disks: Press Add again and allocate 2048 of Disk size (GiB). In Path set /vdsm/storage2.
CPU: Allocate 2 Cores.
Memory: Allocate 4096 of Memory (MiB) and 512 of Swap (MiB).
Network: Set Static IPv4 or use DHCP for the router assign an IP address to the LXC container.
DNS: Leave as is or adjust to your requirements.
Confirm: Ensure Start after created is disabled. Press Finish.

2. Execute the virtual-dsm-lxc script

Access the shell of the Proxmox node/host via the Proxmox UI or SSH. Ensure you have root privileges.
Execute bash -c "$(wget -qLO - https://raw.githubusercontent.com/databreach/virtual-dsm-lxc/main/virtual-dsm-lxc.sh)"
Press Y to continue.
Enter the LXC Container ID of the container created above (e.g. 101).

3. Install Docker and run virtual-dsm

Start the LXC Container created above and login to its console via the Proxmox UI or SSH.
Install Docker (e.g. Install Docker Engine on Debian)
Run virtual-dsm in docker using the mount points created: docker run -it --rm -p 5000:5000 --cap-add NET_ADMIN --device-cgroup-rule='c *:* rwm' --device /dev/net/tun --device /dev/kvm --device /dev/vhost-net --stop-timeout 60 -v /vdsm/storage1:/storage -v /vdsm/storage2:/storage2 -e CPU_CORES=2 -e RAM_SIZE=4096M -e DISK_SIZE=16G -e DISK2_SIZE=2T -e ALLOCATE=N -e DEV=N vdsm/virtual-dsm:latest.

4. Verify installation of virtual-dsm

Access virtual-dsm via the Internet browser of your choice: <IP address of LXC container:5000>.
Complete the DSM on-screen configuration.
Open Storage Manager from the main menu.
There should be a volume 1 (reported as ~15.3 GB) and a volume 2 (reported as ~1.9 TB).

Wow! Thanks! Great doc! :-). I enabled GPU passtrough and added the right things to the conf within proxmox to enable passtrough. But, I'm running to the error that card128 chmod 666 can't be executed because of some permissions. Any fix for that?

If I follow your step by step instructions, I get this message:
sysctl: permission denied on key "net.ipv4.ip_forward"
❯ ERROR: Please add the following docker setting to your container: --sysctl net.ipv4.ip_forward=1

If I follow your step by step instructions, I get this message:
sysctl: permission denied on key "net.ipv4.ip_forward"
❯ ERROR: Please add the following docker setting to your container: --sysctl net.ipv4.ip_forward=1

Thank you for reporting this. Missed that one as I have IP forwarding enabled on my test Proxmox host.

If I follow your step by step instructions, I get this message:
sysctl: permission denied on key "net.ipv4.ip_forward"
❯ ERROR: Please add the following docker setting to your container: --sysctl net.ipv4.ip_forward=1

Thank you for reporting this. Missed that one as I have IP forwarding enabled on my test Proxmox host.

No problem. I hope you can also help me with this?
root@Synology-Docker:~# docker run -it --rm -p 5000:5000 --cap-add=NET_ADMIN --device-cgroup-rule='c *:* rwm' --device /dev/net/tun --device /dev/kvm --device /dev/vhost-net --device /dev/dri --sysctl net.ipv4.ip_forward=1 --stop-timeout 60 -v /vdsm/storage1:/storage -v /vdsm/storage2:/storage2 -e CPU_CORES=3 -e RAM_SIZE=4096M -e DISK_SIZE=25G -e DISK2_SIZE=1125G -e ALLOCATE=N -e DEV=N -e GPU=Y vdsm/virtual-dsm:latest
❯ Starting Virtual DSM for Docker v4.40...
❯ For support visit https://github.com/vdsm/virtual-dsm/
chmod: changing permissions of '/dev/dri/card0': Operation not permitted
❯ ERROR: Status 1 while: chmod 666 /dev/dri/card0 (line 18/13)

Extra info:
features: nesting=1
hostname: Synology-Docker
memory: 8192
mp0: local-lvm:vm-105-disk-1,mp=/vdsm/storage1,backup=1,size=25G
mp1: local-lvm:vm-105-disk-2,mp=/vdsm/storage2,backup=1,size=1125G
net0: name=eth0,bridge=vmbr0,gw=<IP_ADDRESS>,hwaddr=BC:24:11:4B:11:42,ip=<IP_ADDRESS>/24,type=veth
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=8G
swap: 0
unprivileged: 1
lxc.mount.entry: /dev-105/net/tun dev/net/tun none bind,create=file 0 0
lxc.mount.entry: /dev-105/kvm dev/kvm none bind,create=file 0 0
lxc.mount.entry: /dev-105/vhost-net dev/vhost-net none bind,create=file 0 0
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.mount.entry: /dev/fb0 dev/fb0 none bind,optional,create=file
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file
lxc.cgroup2.devices.allow: c 120:0 rwm

GPU passtrough doesn't work for me because I can't find:
/dev/dri
GPU=Y and it's passtrough via Proxmox. If you know something to fix this, let me know.
arch: amd64
cores: 4
features: nesting=1
hostname: Synology-Docker
memory: 8192
mp0: local-lvm:vm-105-disk-1,mp=/vdsm/storage1,backup=1,size=25G
mp1: local-lvm:vm-105-disk-2,mp=/vdsm/storage2,backup=1,size=1125G
net0: name=eth0,bridge=vmbr0,gw=<IP_ADDRESS>,hwaddr=BC:24:11:4B:11:42,ip=<IP_ADDRESS>/24,type=veth
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=8G
swap: 0
unprivileged: 1
lxc.mount.entry: /dev-105/net/tun dev/net/tun none bind,create=file 0 0
lxc.mount.entry: /dev-105/kvm dev/kvm none bind,create=file 0 0
lxc.mount.entry: /dev-105/vhost-net dev/vhost-net none bind,create=file 0 0
lxc.mount.entry: /dev-105/dri/card0 dev/dri/card0 none bind,create=file 0 0
lxc.mount.entry: /dev-105/dri/renderD128 dev/dri/renderD128 none bind,create=file 0 0

Alright, got the card within the container:
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics] (rev 0c)
Then it's not possible what I thought. I need /dev/dri for Jellyfin within docker. But yeah, not possible :)

Alright, got the card within the container:
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics] (rev 0c)
Then it's not possible what I thought. I need /dev/dri for Jellyfin within docker. But yeah, not possible :)

To rule out a non-working GPU inside DSM, you could check if face recognition and/or video thumbnails are working.

The guides have been updated. Thank you!

cant access smb from my local windows client...
WebUI is reachable http://<IP_ADDRESS>:5000/
But inside the DSM there is a different IP <IP_ADDRESS> so i cant access to it from my Computer, only the Webinterface is available under <IP_ADDRESS>:5000...
I just started the Docker Container with the Command above.

However, this macvtap device is only needed to passthrough the network adapter to make DHCP possible. But you can still use macvlan via the tuntap bridge device. So it's still possible to give the container it's own separate IP address. Its just that the traffic will be tunneled via NAT instead of the more direct approach that macvtap offers.

If I want to use macvlan how would I create the network using tuntap?
Currently I create the network on the LXC debian 12 with:
docker network create -d macvlan --subnet=<IP_ADDRESS>/24 --gateway=<IP_ADDRESS> -o parent=eth0 macvlan1
In my compose I have
version: "3"
services:
    virtualdsm02:
        container_name: virtualdsm02
        image: vdsm/virtual-dsm:latest
        environment:
            DISK_SIZE: "16G"
            CPU_CORES: "2"
            RAM_SIZE: "1024M"
            ALLOCATE: "N"
            DISK_FMT: "qcow2"
            DHCP: "Y"
        device_cgroup_rules:
            - 'c *:* rwm'
        sysctls:
            - net.ipv4.ip_forward=1
        devices:
            - /dev/kvm
            - /dev/vhost-net
            - /dev/net/tun

        networks:
          macvlan1:
        cap_add:
            - NET_ADMIN
        ports:
            - 5000:5000
            - 5001:5001
        volumes:
            -  /virtualdsm02/storage1:/storage
        restart: on-failure
        stop_grace_period: 2m
        labels:
           - "com.centurylinklabs.watchtower.enable=true"
networks:
    macvlan1:
        external: true

This currently fails with the mknod /dev/tap2 error.

Okay, so the only drawback is no DHCP assigned address then?
And I have to specify an address in the compose like so?
     networks:
          macvlan1:
            ipv4_address: <IP_ADDRESS>

This works very well. Splendid project!

i follow instructions, all is ok. a problem only ... proxmox backups and proxmox backup server dont work. i cant backups the CT when dsm is running.
please , can someone confirm this?

For backups I sometimes had it with other LXC, my solution was to do a backup in stop/start instead of snapshot, recreating the LXC several months later solved my issue somehow...
I see people are getting it working inside LXC, I was wondering if any of you were able to use mountpoints inside DSM. I was looking for virtual DSM to keep using hyper backup but it seems it refuses to use mounted filesystems as source of the backup and as such I only have one option left which is to pass the data from my PvE host to the LXC as mountpoint and then hopefully pass it on to DSM making it believe it is local storage. I fear that's going to be impossible but I wanted to ask the LXC DSM specialists here...

I have a server without KVM support. I only use LXC. I get an error when starting the container:
root@DSM1:~# docker run -it --rm -p 5000:5000 --cap-add NET_ADMIN --device-cgroup-rule='c : rwm' --sysctl net.ipv4.ip_forward=1 --device /dev/net/tun  --device /dev/vhost-net --stop-timeout 60 -v /vdsm/storage1:/storage -v /vdsm/storage2:/storage2 -e CPU_CORES=2 -e RAM_SIZE=4096M -e DISK_SIZE=16G -e DISK2_SIZE=100G -e DISK_FMT=qcow2 -e ALLOCATE=N vdsm/virtual-dsm:latest KVM=NO
❯ Starting Virtual DSM for Docker v7.01...
❯ For support visit https://github.com/vdsm/virtual-dsm
❯ ERROR: KVM acceleration not available (device file missing), this will cause a major loss of performance.
❯ ERROR: See the FAQ on how to enable it, or continue without KVM by setting KVM=N (not recommended).

try:
docker run -it --rm -p 5000:5000 --cap-add NET_ADMIN --device-cgroup-rule='c : rwm' --sysctl net.ipv4.ip_forward=1 --device /dev/net/tun --device /dev/vhost-net --stop-timeout 60 -v /vdsm/storage1:/storage -v /vdsm/storage2:/storage2 -e CPU_CORES=2 -e RAM_SIZE=4096M -e DISK_SIZE=16G -e DISK2_SIZE=100G -e DISK_FMT=qcow2 -e ALLOCATE=N -e KVM=NO vdsm/virtual-dsm:latest

Everything works inside the container. I can connect to [local address]:5000. I installed Plex and Emby - they are installed, but I can't connect - address [local address]:8096/web/index.html - ERR_CONNECTION_REFUSED. I have enabled the Samba server, but on Windows PC the address \[local address] - is not detected. The Proxmox firewall is disabled. Is there anything else that needs to be done?

A great job! I encountered a problem where DSM disappeared after restarting LXC. Why? Thank you.

A great job!
But I encountered a problem where DSM disappeared after restarting LXC. Why? Thank you！
I am a beginner.


Added option to supply a css file to style the webpage, included test.

The default styling of the resulting webpage may not be to everyones liking so have added the option to supply a user css file.

Problem with branch and hence this pull request due to badly set up git configuration.


Initialize instruction should unroll to reset + gates

What is the expected enhancement?
Make initialize a gate element that can be used directly in Aer simulators, and unrolled into reset + gates by the transpiler for devices and noisey simulations.
Current version
The (current) format for initialize as a QuantumCircuit method is circ.initialize(statevec, qr) to initialise a quantum register in a fixed state.
Proposed changes

Change intialize it to accept either single-qubits or a list (or register) of qubits and to be treated as an explicit reset operation followed by gates to prepare the input state.
On simulators and devices that support reset this would allow initialize to be placed anywhere in a circuit acting on a subset of qubits.
To simplify the transpiler could remove unneeded reset operations.

If a qubit has more than 1 reset operation in a row
If reset is determined to be the first operation on a given qubit (Note: but for noisy simulations one might want to leave explicit reset operations at the start of a circuit to allow for reset errors)

Circuit method
The circuit method could be initialize(state, qubits), where state is a list/ndarray that is a valid statevector, and qubits can be either a full quantum register, single-qubit, or list/tuple of qubits that match the dimension of the state vector.
Qobj serialization
A suggestion for how this could be directly serialized to qobj (if the backend supports the "initialize" instruction in its basis gates) is
{"name": "initialize", "qubits": list[int], "params": complex_vector}

Example:
Consider a 2-qubit circuit, where I want to initialize both qubits into the |1> state, the following should all be equivalent:
qr = QuantumRegister(2)

# Method 1
circ1 = QuantumCircuit(qr)
circ1.initialize([0, 0, 0, 1], qr)

# Method 2
circ2 = QuantumCircuit(qr)
circ2.initialize([0, 0, 0, 1], (qr[0], qr[1]))

# Method 3
circ3 = QuantumCircuit(qr)
circ3.initialize([0, 1], qr[0])
circ3.initialize([0, 1], qr[1])

# Implementation
circ0 = QuantumCircuit(qr)
circ0.reset(qr[0])
circ0.x(qr[0])
circ0.reset(qr[1])
circ0.x(qr[1])

circ1.initialize([0, 0, 0, 1], qr)
This wouldn't work because you have to pass a list of qubits, and qr is a QuantumRegister type.

But this would work:

circ1.initialize([0, 0, 0, 1], qr[:])

There is a proposal to make QuantumRegister be a list of Qubits (#1647), but the implementation and implications are not trivial when I started doing it.

This is done via #1816. But I'll keep it open because the reset part is not done yet.

I think https://github.com/Qiskit/qiskit-terra/pull/2139 is that part that was missing in this issue. Feel free to reopen otherwise.


feat: support replicate chat models

功能
支持 replicate chat models，暂时只支持了 stream 模式。
相关 Issue: #798

ibm-granite/granite-20b-code-instruct-8k
ibm-granite/granite-3.0-2b-instruct
ibm-granite/granite-3.0-8b-instruct
ibm-granite/granite-8b-code-instruct-128k
meta/llama-2-13b
meta/llama-2-13b-chat
meta/llama-2-70b
meta/llama-2-70b-chat
meta/llama-2-7b
meta/llama-2-7b-chat
meta/meta-llama-3.1-405b-instruct
meta/meta-llama-3-70b
meta/meta-llama-3-70b-instruct
meta/meta-llama-3-8b
meta/meta-llama-3-8b-instruct
mistralai/mistral-7b-instruct-v0.2
mistralai/mistral-7b-v0.1
mistralai/mixtral-8x7b-instruct-v0.1

依赖

https://github.com/songquanpeng/one-api/pull/1954

自测

Thx~

我的xAI呢？你这也太不仔细了吧？

Thank you @Laisky for this great improvement! I'm wondering about your plans regarding the Replicate models integration. Are you planning to add all the supported models from Replicate's website? Also, I'm curious if there's a way to automatically detect and integrate newly released models from Replicate into one-api? This would be extremely helpful for keeping the system up-to-date.

I currently support the public models offered by Replicate. The one-api requires hard-coding each adapter's supported models within the code, meaning that any changes to models from upstream providers necessitate code updates.


Text selection bug when typing on iOS

When entering text after a selection is made on iOS, the text sporadically becomes selected again for a few seconds. Could not repro on an Android device
[✓] Flutter (Channel master, 1.22.0-10.0.pre.318, on Mac OS X 10.15.6 19G2021 x86_64,
    locale en-DE)
    • Flutter version 1.22.0-10.0.pre.318 at /Users/plg/development/flutter-dev
    • Framework revision 6b39acdc53 (3 hours ago), 2020-09-23 08:27:04 -0400
    • Engine revision 3e7ca5b869
    • Dart version 2.10.0 (build 2.10.0-156.0.dev)

Duplicate of #63130. The selection highlight is in fact autocorrect highlight.  On iOS it has the same base color as the selection color (but different opacity IIRC).


Frequent register and unregister of services using Redis registry

I have searched the issues of this repository and believe that this is not a duplicate.
I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment
本人第一次在GitHub发issue，如有不妥请大佬见谅

Dubbo version: 2.6.2
Operating System version: cent os 6
Java version: 1.8

Step to reproduce this issue
redis event: /dubbo/com.wehotel.rpcApi.ValidateApi/providers = register, dubbo version: 2.6.2,
redis event: /dubbo/com.wehotel.rpcApi.ValidateApi/providers = unregister, dubbo version: 2.6.2,
redis event: /dubbo/com.wehotel.rpcApi.ValidateApi/providers = register, dubbo version: 2.6.2,
redis event: /dubbo/com.wehotel.rpcApi.ValidateApi/providers = unregister, dubbo version: 2.6.2,

Expected Result
请教大佬这个问题的可能原因是什么
Actual Result
What is actually happen?
If there is an exception, please attach the exception trace:
Just put your stack trace here!

本来想添加一下label但是不知道怎么加

本人第一次在GitHub发issue，如有不妥请大佬见谅

@Vensence Welcome to dubbo community. That's good. Nothing to worry about.
Could u pls. provide a demo to reproduce this problem? U could attach u github repo here.

本来想添加一下label但是不知道怎么加

Maybe u have no permission to label until becoming a committer. :)

@Vensence hi, does your service interface is end with * ?
I have check the code, and find that when subscribe service interface is end with *，the expireExecutor will clean all registed service!

@playaround88 well...nope, it seems like the problem is from the network. Cause the service goes fine in my local machine, but not in the remote machine. What Really strange is when I deploy it in the machine(like<IP_ADDRESS>), everything is fine, but when I deploy it in <IP_ADDRESS> the problem comes out, and the monitor can't get the provider either

FYI:  the registry address is redis://<IP_ADDRESS>:6379

I‘ve tried , well...problem still exists

@playaround88 @diecui1202 I am wondering if the machine time isn't correct, would it cause the frequently register and unregister?

guys, I've changed the machine time and the application went fine. But I still don't understand what cause the problem, apparently the service expired is according to the System.currentTimeMillis()

yes it use System.currentTimeMillis() to determin the service is expired or not. According to the code the RedisRegistry has a expireFuture to check the service is expired or not every 30000ms(by default, and I use the default value), no matter the machine time is correct or not it should check every 30s, it couldn't be so frequently. I am really confusing now, these things flying around in my head for several days

it looks like there are two machines with the different time providing the same service.


Saving custom editors marks file as non-edited before CustomDocument#save promise returns

VSCode Version: 1.46.1
OS Version: macOS Catalina 10.15.3

Steps to Reproduce:

Install the BPMN Editor https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-bpmn-editor
Create a new BPMN file (e.g. example.bpmn)
Insert a Start node (Green circle)
Leave a dangling arrow (attached on the rear end on the green node, dangling on the pointy end)
Notice how the file is marked as edited
Save the file
Notice how the file is now not marked as edited
Close the file and open it
Notice how it is does not contain the edits you've made

Does this issue occur when all extensions are disabled?: No

Detailed explanation:
When a dangling arrow is present on a diagram, it's not possible to save it, because it is considered a validation error. We currently don't have a good error-treatment tool, but even if we did, the file would be marked as non-edited by VS Code and if someone accidentally closed the editor before fixing the validation problems, their work would be lost.
My understanding is that VS Code should wait for the return of CustomDocument#save to decide if the file should be marked as non-edited. If the promise resolves normally, the file should be marked as non-edited, if the promise rejects, no change should be made.
This would prevent users from accidentally closing the editor and losing their work. If they really want to quit, VS Code's native confirmation popup should appear and provide the customary choices to the user.

@mjbvz FYI

The unsaved/saved marking works nicely now, but if I close VS Code while the save promise is still happening I don't get the "Do you want to save this" dialog.

@alexr00 Were you testing in extension development mode? Many of the prompts on on close are disabled when you are developing an extension. Here's what I see after installing a packaged extension that takes 10 seconds to save:

(note that there's a separate issue where if you click save, we trigger a second save which cancels the first)

agh. yes I was testing in extension development mode.


test on 3.11

Codecov Report

Merging #80 (d64b694) into main (033874e) will decrease coverage by 0.65%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
- Coverage   58.76%   58.10%   -0.66%
==========================================
  Files          38       38
  Lines        2224     2220       -4
  Branches      264      223      -41
==========================================
- Hits         1307     1290      -17
- Misses        888      903      +15
+ Partials       29       27       -2

Impacted Files
Coverage Δ

src/dvc_objects/fs/system.py
60.29% <0.00%> (-23.53%)
:arrow_down:

src/dvc_objects/fs/utils.py
41.48% <0.00%> (-0.44%)
:arrow_down:

src/dvc_objects/executors.py
31.11% <0.00%> (+0.67%)
:arrow_up:

src/dvc_objects/fs/path.py
38.20% <0.00%> (+0.83%)
:arrow_up:

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 033874e...d64b694. Read the comment docs.


build(tools): colorization options and other improvements

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (bf6181e) to head (f284229).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           76        76
  Lines         1328      1328
=========================================
  Hits          1328      1328

Flag
Coverage Δ

gi
100.00% <ø> (ø)

optional
100.00% <ø> (ø)

result
100.00% <ø> (ø)

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

coverage: 100.0%. remained the same
when pulling f284229b33a2855b0da43e4f861dde48abaab158 on feature/build-tools
into bf6181e3ef0c7293c500e79a79dae8e8117b980a on main.


Error when using path like param/value in url

In config file, I have
'urlManager' => [
            'class' => 'yii\web\UrlManager',
            'enablePrettyUrl' => true,
            'showScriptName' => false,
            'rules' => []

Request are getting rendered by this url

http://localhost/mywebs9/web/main/getregions/?id=3

Note, here, param/value is ?id=3

But, I want to use following type of url

http://localhost/mywebs9/web/main/getregions/id/3

Note, here, param/value is /id/3
Error I am getting using 2nd url is

@cebe Suppose there exists a scenario where you enter controller:\w+/action:\w+/page/page:\+d/limit/limit:\+d but you would like the rule to be flexible to accept controller:\w+/action:\w+/limit/limit:\+d/page/page:\+d without setting two rules, how would you achieve this?
I remember in yii 1.1 this could be achieved by either using controller:\w+/action:\w+/* or controller:\w+/action:\w+?(/page/page:\+d)?(/limit/limit:\+d)?

can you open a new issue for that please?


Correction for raw affiliation CIRAD, UMR AGAP, Avenue Agropolis, F‐34398 Montpellier Cedex 5, France

Correction needed for raw affiliation CIRAD, UMR AGAP, Avenue Agropolis, F‐34398 Montpellier Cedex 5, France
raw_affiliation_name: CIRAD, UMR AGAP, Avenue Agropolis, F‐34398 Montpellier Cedex 5, France
new_rors: 05kpkpg04;00txxwv34;02w4exq36
previous_rors: 05kpkpg04;00txxwv34
works_examples: W1549258270
contact: 1a399a99fe1fa4c96d7b8c3e4131a88e:1f2968967a961f9fa042770669ba156f5073 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Add option to save standalone model

Added an additional option --standalone-output-path to convert.py to produce standalone models using TensorFlow's freeze_graph tool. It addresses #23. There is probably a cleaner way to do this, but I didn't want to change the kaffe source code.

This sounds awesome.  I'm going to try it out.

Hello! I just wanted to mention that --standalone-output-path would be super useful to me as well. Thanks for writing this PR, @d4nst!
I also noticed this blog post where someone else found it helpful. :)


made more readable match function and made minor style fixes

Sorry but this is the style of writing code I want to promote. I almost never use returns because they are alien to functional programming and I find end, rather ugly. YMMV

Okay


NBAI is wrong

Hi,
I was doing some correlation analysis when I found out that NBAI was the exact opposite of NSDS which is not the case in the original paper. There is an error in NBAI formulation in your CSV file.
You defined it like this : ((S2 - S1)/G)/((S2 + S1)/G)
But the original paper formulated it like this :
NBAI = (TM7 – TM5/TM2)/ (TM7 + TM5/TM2)
You put extra parenthesis before dividing by the green band.
Hope this correction can help others not to make any mistakes.
(also FYI some indices are redundant :
NDBI = - NDMI
NDWI = VgNIRBI
VrNIRBI = - NDVI
)
Thanks for this gathering of spectral indices though, it helps to know what exists in the litterature !

Hey @RaphaelDELAIR!
You are right, I will correct the NBAI index now! Thank you for spotting it!
Regarding the redundant indices: That's fine, there are a lot. The idea of the catalogue is to have them all with their respective reference, even if duplicated or redundant.
Cheers!

Index corrected! Thank you very much again!
Cheers!
David


updated cppcheck recipe branch to main

Main is the current active branch name from cppcheck in Github. I am getting a branch error with master and changing it to main fixed it.

Don't add .DS_Store  files.

Should I create a new branch without .DS_Store files?

I've already updated it and included in https://github.com/ros/meta-ros/pull/724 which should be merged soon.


Reference update - small irregulars

The reference has been updated based on pedroJ's and my idea in Discord: Put albedo sources in reference list and order them by the name of the author. The citation comment for albedo is kept but now uses the shortened name of the paper in the reference list instead.
I'd like opinions of whether the current layout is fine.

I'd like opinions of whether the current layout is fine.

Yes, everything is fine. Thank you!


[BUG][API] Links from  RTE are not translated as a valid links

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
TBA
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS:
- Node:
- pnpm:

Anything else?
No response

Could you link the core issue here? Is that task blocked now?

Solution for that can be found here
https://github.com/shopware/shopware/commit/3dfe23d832f0459e0903004550620baf384e893f


Release/1.6.0

Coverage increased (+0.3%) to 92.632% when pulling 73b447b0c53b25a7d75dfca870d8b15ce426fa62 on release/1.6.0 into 6232d3c82bec87165986f25c45615009b478bba4 on master.


Update 4n6 scripts

Fixing the issue with the previous PR

Trying, but it's not working for some reason. The rebase looks like it works, but then doesn't acknowledge the updates.

I don't think it worked the way it should have. Can you confirm?

Looks ok. Tests are running. Will let you know.


[AIRAVATA-2728] Refactoring Experiment Catalog Implementation

Implementation of Repository classes for the Experiment Catalog.
Changes made -
Added the necessary entity classes.
Included all the methods for the repository class.
Pending work -
Included tests for the repository class.
Made necessary changes to the RegistryServerHandler.java class.
Note: This PR includes Workspace Catalog modules as well.

@tilaks26 Do you want me to review this or are you still working on it?

@machristie I'm still working on the tests. Will request for review once I'm done.

Sounds good, thanks
On Apr 13, 2018, at 2:33 PM, Sneha Tilak <notifications<EMAIL_ADDRESS>wrote:
@machristiehttps://github.com/machristie I'm still working on the tests. Will request for review once I'm done.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/apache/airavata/pull/191#issuecomment-381224058, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA3O_ZpIpm7Y1aPtE9PqHA3e0YyLMKqjks5toO9kgaJpZM4TPKgI.

@machristie I have updated the PR.


Support React Native 0.57.4

React Native 0.57.4 is out (release, changelog).
PS. It looks a bit cumbersome to introduce those trivial changes and go through a cocoapods-fix-react-native release cycle for every patch release of RN. Will you accept a PR which introduces pre/post patches for a minor version of RN (like 0.57-post.rb) and attempts to load them if there's no patch for the exact version?

Yep 👍

FWIW - I ported our app to 57.4 today https://github.com/artsy/emission/pull/1210 , and it's been working fine without running the fixer ( though it's static frameworks, and it's not been deployed to our app which uses frameworks )

I was thinking just of this today as well @nebolsin ^
To start decreasing the minor in order to find a fallback if current doesn't exist


Forget removing debug information?

The server keep spaming: "HERE HERE HERE!!!!! "

    public void randomTick(BlockState state, ServerLevel worldIn, BlockPos pos, RandomSource random) {
        BrewinAndChewin.LOGGER.error("HERE HERE HERE!!!!! " + worldIn.getRandom().nextFloat());

lmao

Issue still occurs in 2024.


regen: Refactor log migrate functions to avoid needing azure keys

This isn't really the right fix, as there's nothing guaranteeing this won't happen again. A potential, more correct fix would be to move these lines into a function so they don't run at import time.


Convergence question

Hi team,
Thank you for all your work. I managed to successfully run Robyn. But I need help understanding this result from the pareto plot.

DECOMP.RSSD NOT converged<EMAIL_ADDRESS>0.11 > 0.064 &<EMAIL_ADDRESS>0.25 > 0.22
NRMSE converged<EMAIL_ADDRESS>0.00031 <= 0.022 &<EMAIL_ADDRESS>0.093 <= 0.14
I assume we're dealing with standard deviations (sd) and confidence intervals (qt) here. Can you elaborate on how these numbers are interpreted? I would appreciate any external sources that provide an explanation. Thank you.

Hi @Da5413lions,
In Robyn, we consider the model to be converged when:
Criteria #1: Last quantile's standard deviation < first 3 quantiles' mean standard deviation
Criteria #2: Last quantile's absolute median < absolute first quantile's absolute median - 2 * first 3 quantiles' mean standard deviation
The quantiles are ordered by the iterations of the model, so if we ran 1000 iterations, the first 200 iterations would make up the first quantile. These two criteria represent an effort to demonstrate that both the standard deviation and the mean for both NRMSE and DECOMP.RSSD have improved relative to where they began, and they are not as variable. Both mentioned criteria have to be satisfied to consider MOO convergence.
This is under revision as we believe that the main score that should be considered for convergence is NRMSE (Model error, which in your case actually converged), this is because not necessarily the fact that DECOMP.RSSD is converging to small values means that the model quality is better, it is just providing less radical recommendations in terms of differences on the share of spend and share of effect. E.g. if you have 50/50 investment in channel A and B respectively, then a model that tels you the effect is 100% for channel A would be of very high DECOMP.RSSD, where a model closer to that 50%/50% in terms of effect would have very low DECOMP.RSSD.
Hope it helps :)

Thank you @Leonelsentana . Very helpful.

Hi @Da5413lions, glad it helped,
Please check that is Last quantile's absolute median < absolute first quantile's absolute median - 2 * first 3 quantiles' mean standard deviation now, we changed that, it used to be 3 before to make the rule a bit less strict, please have in mind this is just an indication proxy for convergence and the model will always run the same way no matter what the convergence scores give as a result. The reasoning behind is that if the last quantile median is 2 SDs away or more from the first quantile's median as a result of the optimization process, it should be converging to a significantly lower median value for the score.


Use the local branch name by default on remote-source deployment too

Have a config option for remote-source deployment deployment.use_local_git_ref
When deployment.use_local_git_ref is true it should use the local git branch with fab <stage> deploy instead of having to do fab <stage> deploy:<local-branch>
Use the local branch name by default on remote-source deployment too

Done in https://github.com/kabirbaidhya/boss/pull/145


Add dependent operator CRDs to scheme

Since the dataplane operator relies on multiple other operators to perform its duties. We need to register those CRDs with the envtest k8s scheme.
This change adds dependent operators to the scheme to allow for extended testing within the envtest framework.

recheck

/test images


⚠ Bofrost.at has degraded performance

In 22c103b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2170 ms

Resolved: Bofrost.at performance has improved in aa6b911 after 13 minutes.


Added BsonDocument and BsonValues

Apologies for such a large review but this is the initial BsonValue conversion to multiplatform.
Things to note are:

Nested Bson types just store the core values: For example there is no ObjectId or Decimal128 type so BsonObjectId and BsonDecimal128 store the raw values.
There is no KMP (Kotlin Multi Platform) support for: BigDecimal - so BsonDecimal128 is simplified for now. Please add new tickets to the KBson project if further integration support is required.
There is no KMP support for AtomicInt or current time in ms classes, methods - required for BsonObjectId. So platform specific handlers have been added.
Most tests are just common tests - meaning they run on JVM, JS and Native platforms.
There are Java specific API tests - that focus on API differences between the original BsonValues and this Kotlin port.
Main item to note is the lack of Kotlin Constructor support - In Kotlin primary and secondary constructors are supported but cannot contain much logic. So BsonObjectId utilizes companion object and invoke support for hex strings and byteArrays.

KBSON-2

@cmelchior - let me know if there are any other updates required for this.  Otherwise, I'll merge and we can change any unidiomatic code in a later PR.


Failed to cut chunks of code

When a piece of code is cut there is an empty space, as is logical, if those blank spaces are erased by pressing the shift key shift + delete, what had been cut and then pasted in another part of the file is deleted.

@dannyjavi can you please share a recording of what happened to help understand what's going on?

Sorry for taking time to answer, I hope it is a little clearer and can be used to help correct what I believe is a mistake.
Thank you


Selectize Support

Myself and a colleague are currently working on integrating json-editor into an application with many complex views being driven off the output of the JSON schema.
The decision to use Selectize instead of Select2 was made a long time ago in this project and thus we're looking into supporting Selectize in json-editor, beginning with the select and array types.
Here is a screenshot of our work in progress (obviously this is in development, the array type is side-by-side with the originial for comparison).

Would there be an interest in a pull request to add Selectize support back into master? I prefer if we would (1) contribute back and (2) side step the need for us to maintain a forked version just for Selectize support.
Thoughts?

Yeah, I would definitely be interested in a pull request.  An array tag editor would be awesome.

Great! We've actually got a fully working version now with Selectize support for the select and array types. We just need to clean up the code a little before starting a PR.
Now there is the option of being able to use Select2 or Selectize, how would you prefer that choice be made? In our version, @radioisradio has introduced a boolean flag to decide whether to use Selectize whereas I am taking the approach of priority, Select2 first, then look for Selectize etc... Thoughts?

Closing as Pull Request is now open for Selectize suport #399


Add Atlassian logo to 'Used By' section on the main page

Hi folks,
Happy to put our logo on the site to show our support :)
Envoy is working magic for us so far and all the support via github and slack have been amazing.
Also I noticed in #114 that perhaps this won't be merged until a policy has been made for adding logos. Feel free to close this and notify me at a more appropriate time.

@caniszczyk can you please help us define a formalized logo policy? Thank you!

Awesome thanks @caniszczyk

@caniszczyk @cetanu
Thanks for helping with the logo policy draft. Are there any updates on this yet?

Amye has a draft here, let me get her to review it with @mattklein123 and I... and we will get it done.

I'm not part of CNCF @agrawroh :)


Add Termux setup page

See discord thread(s?) by axmanalax

Page draft is done and pushed.  Waiting for deployment to https://luteorg.github.io/lute-manual/intro.html

Done, out there ok.


Rename makefile to Makefile

Although makefile is properly working and it's part of the standard.
https://www.gnu.org/software/make/manual/make.html#Makefile-Names
GNU recommends naming it as Makefile

(We recommend Makefile because it appears prominently near the beginning of a directory listing, right near other important files such as README.)

Thanks for the recommendation, change is now applied to the master.


Add python_requires to help pip, and version classifers

Based on the versions tested by .travis.yml, which match the supported CPython versions.
https://en.wikipedia.org/wiki/CPython#Version_history
And here's the pip installs for terminado from PyPI for May 2018:

python_version
percent
download_count

2.7
41.87%
136,449

3.6
26.07%
84,967

3.5
18.60%
60,618

3.4
13.15%
42,869

3.7
0.27%
876

3.3
0.03%
103

2.6
0.00%
15

3.8
0.00%
1

Total

325,898

Source: pypinfo --start-date 2018-05-01 --end-date 2018-05-31 --percent --markdown terminado pyversion

The Travis failure is unrelated, latest master is failing in the same way:
https://travis-ci.org/jupyter/terminado/builds/361105398

Thanks. I'll give other people a chance to opine on the use of the requires-python field here.

The test failure on Py 2.7 seems to be reproducible. :-/

Close/reopen to rerun tests


deploy --sourcepath different behavior than --manifest or --metadata for large deploys

@EgorBosolyho @zankoav
Hello, I have same problem.
With-p- work fine, but with -m or -x -failing.
sfdx force:source:deploy -p ./force-app/main/default/classes/Test.cls - worke fine
Our project has a lot of meta files more then 5k, that is why (sfdx force:source:deploy) doesn't work with deployment by -m or -x.
In small projects - all works fine, but not in large.
My logs:
sfdx force:source:deploy -m ApexClass:ETEAssets --loglevel=debug --json { "status": 1, "name": "TypeError", "message": "Cannot read property 'id' of undefined", "exitCode": 1, "commandName": "Deploy", "stack": "TypeError: Cannot read property 'id' of undefined\n at ComponentSet.simpleKey (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:303:116)\n at ComponentSet.has (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:237:58)\n at MetadataResolver.getComponentsFromPathRecursive (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:81:49)\n at MetadataResolver.getComponentsFromPathRecursive (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)\n at MetadataResolver.getComponentsFromPathRecursive (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)\n at MetadataResolver.getComponentsFromPathRecursive (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)\n at MetadataResolver.getComponentsFromPathRecursive (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)\n at MetadataResolver.getComponentsFromPath (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:43:25)\n at Function.fromSource (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:67:46)\n at Function.build (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/lib/componentSetBuilder.js:74:74)\nOuter stack:\n at Function.wrap (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/node_modules/@salesforce/core/lib/sfdxError.js:171:27)\n at Deploy.catch (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/lib/sfdxCommand.js:248:67)\n at async Deploy._run (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/lib/sfdxCommand.js:85:13)\n at async Config.runCommand (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/config/lib/config.js:173:24)\n at async SfdxMain.run (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/main.js:27:9)\n at async SfdxMain._run (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/command.js:43:20)\n at async Object.run (/Users/aleksandrzanko/.local/share/sfdx/client/7.112.1-b99fa53/dist/cli.js:162:47)", "warnings": [] }

https://github.com/forcedotcom/cli/issues/1112#issuecomment-896123479
I'm getting the similar issue when I'm trying to use:
sfdx force:source:deploy -m ApexClass:MyApexClass OR sfdx force:source:deploy -x path/to/package.xml
After some research, I found that it works if I delete most of the objects in the Objects folder. So I think this may be a problem related to large projects. This also works well if I use a deployment with a direct file path
sfdx force:source:deploy -p path/to/file
TypeError: Cannot read property 'id' of undefined
    at ComponentSet.simpleKey (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:303:116)
    at ComponentSet.has (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:237:58)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:81:49)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPath (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:43:25)
    at Function.fromSource (/Users/user1/.local/share/sfdx/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:67:46)
    at Function.build (/Users/user1/.local/share/sfdx/node_modules/@salesforce/plugin-source/lib/componentSetBuilder.js:74:74)\nOuter stack:
    at Function.wrap (/Users/user1/.local/share/sfdx/node_modules/@salesforce/core/lib/sfdxError.js:171:27)
    at Deploy.catch (/Users/user1/.local/share/sfdx/node_modules/@salesforce/command/lib/sfdxCommand.js:248:67)
    at async Deploy._run (/Users/user1/.local/share/sfdx/node_modules/@salesforce/command/lib/sfdxCommand.js:85:13)
    at async Config.runCommand (/Users/user1/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/config/lib/config.js:173:24)
    at async SfdxMain.run (/Users/user1/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/main.js:27:9)
    at async SfdxMain._run (/Users/user1/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/command.js:43:20)
    at async Object.run (/Users/user1/.local/share/sfdx/client/7.112.1-b99fa53/dist/cli.js:162:47)

Yes, it is.
-m and -x will fail unless I remove a lot of objects from the objects folder or whole folder.
And it doesn't depend on which objects I left, because I thought I had "bad" objects, and tried different cases
-p works well
unfortunately, I can't provide you with our metadata, but I can do any local testing you need.
We have 442 entries in our objects folder. Here we store standard and custom objects.
objects folder info - 11 035 091 bytes (36,7 MB on disk) for 8 358 items
It seems like there's something else that's wrong with deploying with the-x flag. I can deploy all the other source (except the Objects) in my project without errors using VS Code (right click + Deploy Source to Org) or with the sfdx force:source:deploy -p path/to/folder.
When I deploy with sfdx force:source:deploy -x path/to/package.xml I get same error as before after removing the CustomObject from the package.xml file.
*** Deploying with SOAP API ***
ERROR running force:source:deploy: Cannot set property 'content' of undefined
Here's the --dev-debug error:

*** Internal Diagnostic ***

TypeError: Cannot read property 'id' of undefined
    at ComponentSet.simpleKey (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:303:116)
    at ComponentSet.has (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:237:58)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:81:49)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPathRecursive (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:96:37)
    at MetadataResolver.getComponentsFromPath (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/metadataResolver.js:43:25)
    at Function.fromSource (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:67:46)
    at Function.<anonymous> (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/source-deploy-retrieve/lib/src/collections/componentSet.js:95:49)
Outer stack:
    at Function.wrap (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/node_modules/@salesforce/core/lib/sfdxError.js:171:27)
    at Deploy.catch (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/lib/sfdxCommand.js:248:67)
    at async Deploy._run (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@salesforce/plugin-source/node_modules/@salesforce/command/lib/sfdxCommand.js:85:13)
    at async Config.runCommand (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/config/lib/config.js:173:24)
    at async SfdxMain.run (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/main.js:27:9)
    at async SfdxMain._run (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/node_modules/@oclif/command/lib/command.js:43:20)
    at async Object.run (/Users/bpete/.local/share/sfdx/client/7.112.1-b99fa53/dist/cli.js:162:47)
******

closing based on comment
and lots of the SDR registry errors have been fixed


Refactor differenced processes, random walks, and AR processes

Closes #328

If needed, I can review after the conflicts have been solved.

Ready for re-review @damonbayer

@dylanhmorris looks like your latest commit caused a test failure

@dylanhmorris looks like your latest commit caused a test failure

Should be fixed now. Issue was that rtperiodicdiffar.py wants to be able to sample differenced processes for durations shorter than the differencing order. I go back and forth on whether we should allow this, but if we're going to, it should just return the appropriate initial values.

@dylanhmorris This is very close. Documentation needs a further look. For example, :fun: is not valid in Sphinx.

@dylanhmorris This is very close. Documentation needs a further look. For example, :fun: is not valid in Sphinx.

Fixed in 94131ce


[add-resource] New Plugin - Facebook posts

I would like to add my new plugin/theme to the Grav Repository.
Here are the project details: https://github.com/mikahanninen/grav-plugin-facebook
Plugin allows embedding Facebook page posts into Grav site.

Added!


Please add line numbers.

Description of the new feature/enhancement

As https://bugs.kde.org/show_bug.cgi?id=485923#c0 describes:

STEPS TO REPRODUCE
Invoke Konsole, and use a command like cat or https://github.com/MicrosoftDocs/PowerShell-Docs/blob/04dac6ae6b2abcb91006b6a515cc26c72219ffd5/reference/7.4/Microsoft.PowerShell.Management/Get-Content.md#example-2-limit-the-number-of-lines-get-content-returns to output the content of a file to the terminal.
OBSERVED RESULT
Without using cat's -b or -n flags, the content cannot be numbered. For others, like the aforecited Get-Content, it's impossible to output line numbers without writing code for every interaction to iterate over the lines.

Konsole has since gained the ability to display line numbers, as https://discuss.kde.org/t/how-to-enable-line-numbers-in-konsole/14435?u=rokejulianlockhart#always-3 depicts:

It's been invaluable for me, when reading long logs via the terminal. Consequently, I propose the same for Windows Terminal.
Proposed technical implementation details (optional)

I'd rather that they be in a permanent separator following the text direction, or on the opposite of the text direction, still separated regardless (to prevent overlap). Specifically, as https://bugs.kde.org/show_bug.cgi?id=485970#c3 describes:

I want it to be like a Konsole/Dolphin panel, so that it can be moved to the left or right. However, I'd like it to work like a plasmoid on a PlasmaShell panel does - when a new session is invoked (like when a new tab or window is created) it should be static, and not overlay, like any other panel does. However, I should be able to set a toggle (like PlasmaShell's pin feature) and have it then able to temporarily resize over the session until I pin it again, where it returns to its original size. It should also have a horizontal scrollbar for when the user accidentally sets it shorter than they need at the start of a session.
Does that make sense?

I expected that this implementation wouldn't be possible due to wt's apparent lack of comparable "panel" support, but https://github.com/microsoft/terminal/issues/997#issue-448313575 demonstrates otherwise.

relevant notes:

PR that added it to konsole: https://invent.kde.org/utilities/konsole/-/merge_requests/730
PR for docs: https://invent.kde.org/utilities/konsole/-/merge_requests/988

Why is less -N (or similar) insufficient for this/?

https://github.com/microsoft/terminal/issues/17490#issuecomment-2234379836

@zadjii-msft, because that's solely usable when piping command output. It doesn't operate retroactively.


Ability to override resolv.conf DNS servers

Is your feature request related to a problem? Please describe.
When we are working on the hybrid migration we have placed a second DNS server in front of the bosh-dns so that we can manage dual DNS lookups.
Quarks always sets the spec.dnsConfig like this ...
{
  "nameservers": [
    "<IP_ADDRESS>"
  ],
  "options": [
    {
      "name": "ndots",
      "value": "5"
    }
  ],
  "searches": [
    "kubecf.svc.cluster.local",
    "svc.cluster.local",
    "cluster.local"
  ]
}

Where <IP_ADDRESS> is the ip of the bosh-dns server.  we would like to be able to override that and set it to a different static IP.
Describe the solution you'd like
Have the ability to set a parameter in the manifest that quarks will accept to use as an override of the server values.  if not set it should default to the standard configuration.
Describe alternatives you've considered
We are currently forced to manually update the /etc/resolv.conf and we also need customer configuration on the dns server so we cannot add new config into the current bosh-dns to support the use case.
Additional context
See initial discussion in slack here https://cloudfoundry.slack.com/archives/C1BQKKNP4/p1602782923025400

@andrew-edgar we've been discussing this. If we allow to override the server, clients won't be able to resolve domains that are configured in bosh-dns anymore, won't that break things?
Unless the server you put in front of bosh-dns is doing conditional forwarding to the bosh-dns?

https://github.com/cloudfoundry-incubator/quarks-operator/pull/1229

@manno yes that's exactly right you need to have the dns in front of the bosh-dns.  which is what we are doing but a warning about this override is clear that yes you must also somehow front the existing dns.

Confirming it works. For example:
  - type: replace
    path: /instance_groups/name=diego-api/env?/bosh/agent/settings/dns
    value: <IP_ADDRESS>


Feature request - Add a new group in dataset model for BL staffs

Issue Name
Add a new group in dataset model for BL staffs
Summary
At MAX IV we always add beamline group to accessGroup field in each datasets. This allows the beamline staff to see all the datasets produced from the beamline they works on.
At the moment accessGroup has read access but not write access. We have sometimes remote experiments which means that the user doesn't have to come to MAXIV to do the experiment but our beamline staffs run the experiment for the user. Therefore it is useful for them to be able to for example write a comment in the datasets (Like this one is good or bad) so that the user knows which datasets to check.
Request
We would like to add an extra group in the dataset for BL staff and this group should have write permission. Something like instrumentGroupbut if you have a better name it works too.

@stephan271, @nitrosx , @henrikjohansson712

At PSI we use beamline accounts (functional accounts) for this. Would this be an alternative for MAxIV ?

@stephan271 This means all BL staffs using the same functional account? At MAXIV each BL has a group and all the staff work at a given BL will be add to that BL group in AD so when they works they usually log in with their own MAXIV account in AD. A functional account might works but that means the BL staffs need to remember an extra account and if the password is passed around and leaked anyone could do whatever they want.

The main reason for having functional accounts is to allow for automation of the ingest. If in your case the ingest is somehow "manual" would another option be to add the members of the BL group to the ownerGroup (temporarily) ?

Which account do you use for the first step in your list ?

I used the one called ingestor

@nitrosx & @henrikjohansson712 What do you think about adding an extra group with right permission for BL staffs?

@nguyenlinhlinh let us brainstorm on the request and get back to you. Thanks

After looking to the second alternative which is to append globalaccess to ctx.options.currentGroups I still think adding a new field called instrumentGroup in the dataset model is better because using globalaccess means we need to have a list of beamlines in our local configuration and then in the code iterate through it and check if the user belongs to the BL group and then check if the dataset is produced from that BL. This means we add a lot more code that is unnecessary for other facility. If we introduce instrumentGroup we just need to add one more check in this line https://github.com/SciCatProject/backend/blob/18008dbf091ab16de8525b43d27f5c18b6fdaefb/common/models/mongo-queryable.js#L614
if ((groups.indexOf("globalaccess") < 0) && !ctx.isNewInstance && groups.indexOf(ctx.currentInstance.ownerGroup) < 0 && groups.indexOf(ctx.currentInstance.instrumentGroup) < 0))
I have also considered the third option suggested by Fredrik that we add the BL staff to that proposal in AD. It doesn't work in our case because the BL staff then must ask someone that have permission to modify the group in AD to that.

For me adding an instrumentGroup would be fine. However this should be an optional field and all existing queries should continue to work as before, if no such field is provided.

@nitrosx @henrikjohansson712  Is it also ok for you that I introduce another field called intrumentGroup? Our beamline asked again today and they are thinking to give up SciCat because we are too slow on making decision :(.

Just as a hint: you do not need to wait for a decision, feel free to use your branch already now. I am sure it will be added eventually in the main branch, but in this way you can fulfill the needs of your customers earlier ;-)

Ah, I see thanks @stephan271 . Will do that.

@nguyenlinhlinh: please go ahead if that address your use case and makes your staff happy. I think I would follow @stephan271  suggestion to make it an optional feature, so makes your change more appealing, easier to merge in master and we do not force other facilities to use it :)
I apologize for the slow reply.
Regarding the general solution here what we came up with the possible solutions that are SciCat centric:

Ad-hoc group and logic to address this specific use case. Like the one that you proposed
Implement a generalized solution like a rule based access permission logic which allows us to address this use-case. This solution is more involved, but will leverage nestjs functionalities of the new implementation of SciCat
Example:
▪ Group: BeamLine - Can: View - What: Dataset
▪ Group: BeamLine – Can: Add – What: Dataset.ScientificMetadata -When: Instrument is…

The issue was discussed in our December meeting and it was decided to not include these changes in the main backend branch for now, but take up the topic again within the new nestjs based backend.

@stephan271 I think the decision was to add an extra field to the dateset called "instrumentGroup" as  a temporary solution.

Okay, then I had a different understanding of what we wanted to do. Anyhow, I am fine with doing what you suggest. Are you opening a PR for this ?


[Feature Request] Declutter menu using roles

Is your feature request related to a problem? Please describe
All menu items should have a way to be hidden or disabled, given the rapid expansion of features.
Menu items still show for things that are unused by certain roles or cant work because underlying permissions the plugin requires are denied, leading to many of the features looking "broken" when they are just disabled.
This behaviour already exists for the Security plugin, where "Security" menu only shows when "security_manager" role is assigned.
Describe the solution you'd like
Have each menu item map to a role, like the "security_manager" role.
Introduce inheritance/composition for roles/permissions, so meta roles can be created that reference other roles, effectively giving the administrator the ability to centralize without having to manage "Mapped users" for every granular role.
A nice to have alongside this would be a way to see what each plugin requires for permissions to enable each of it's features, so enabling a particular menu item won't be crippled from the start, like "Reporting" where write access is required but not explained:Reporting Documentation
Related component
Plugins
Describe alternatives you've considered
No response
Additional context
No response

@opensearch-project/admin Can you transfer this to https://github.com/opensearch-project/OpenSearch-Dashboards?


Passing parameters to get Timezone using Google API module

Hello,
I am new to programmation and I would like to pass the latitude and the longitude as parameters to the timezone to get the result.
I didn't find a solution. Do yo have a solution that I could try?
Thank you,
Sam.
function giveTimeZone(lat,lng){
var loc="'"+lat+","+lng+"'";
timezone({
    location: loc
}).then( function( result ) {
    console.log( result );
}).catch( function( err ) {
    console.log( err );
});
}

Hey @MBenoli,
There's no need for the "'". The string your passing to the api would look like "'43.7182713,-79.3777061'" when it should be "43.7182713,-79.3777061".
Maybe this will help:
function giveTimeZone(lat,lng){
	var loc=lat+","+lng;

	return timezone({
	    location: loc
	});
}

// how youd use
giveTimeZone(43.7182713, -79.3777061)
.then( function(result) {
	//received the data
	console.log('do something with result here', result);
})
.catch( function(err) {
	//there was an error somewhere
	throw err;
});

Your function should return something most likely so its not bad to just return the promise.

Thank you very much for your answer!


Return 1 from duk_push_boolean() and variants

Currently duk_push_boolean() returns void; change it to return (duk_ret_t) 1 so that one can:
return duk_push_boolean(ctx, x == y);

This allows tailcalls to also be used internally which should reduce footprint. It's also convenient in user code, so the change could be added to the public API. At least the following API functions which now return void could return 1 to facilitate tail calls:

duk_push_undefined()
duk_push_null()
duk_push_boolean()
duk_push_true()
duk_push_false()
duk_push_number()
duk_push_nan()
duk_push_int()
duk_push_uint()
duk_push_pointer()

A corresponding change has already been made for duk_error() and throwers:
return duk_error(ctx, ...);

The downside of the change is some additional compiler output for loading the (often unused) result. The result values of the pusher API calls will also be a little bit inconsistent in that some return a value related result (for example, a const char * for a pushed string) while others return a dummy tailcall-facilitating value. The result values are thus driven by convenience rather than being strictly consistent.
This pull is a small test in what the impact of making such a change is. If it works internally to reduce footprint, the API change can be avoided by simply using an API macro and casting to void. So the API decision is separate.

Moving to 3.0.0 for consideration. The most important change is for duk_error() and variants to allow the return duk_error(...) idiom; that's already in master for 2.0.0 release.


DO NOT MERGE [wip] starting the porting to semantic math

this is a complete work in progress, but here's what I got done tonight
The basic idea was to replace the bodies of Node.Type and Node.Creator with their semantic-math equivalents, and see if the rest of the code would just work. I've found a bunch of things that need updating in this repo or in semantic-math repos and added TODOs, and will keep investigating why various things are failing to find more TODOs.
This isn't linted and the commit names aren't very descriptive, so I'll try to get that done. If you see something here and want to fix it in semantic-math or help me fix something please yes help! :)
My goal is to in the next week (or so?) get a better idea of what we need to do, clean up this PR, and then make this a base branch with a bunch of TODOs and disabled tests, and people can make PRs off of it to help fix various issues. (Let me know if you think that won't work)
WOOOO porting :)
cc @kevinbarabash
More things, not mentioned in this PR's code:

[ ] when printing in math-parser I got throw new Error('unrecognized node'); -- can it show what the node looks like? easier to debug that
[ ] we should make sure we don't need flatten and then get rid of it
[ ] once this is stable, we should look into getting rid of paren nodes when not needed now that math-parser handles printing them by tree structure

I can definitely add better debug messages to the math-parser.  Please open issues in that repo.

I got to
 426 passing (4s)
  35 pending
  221 failing

pending means I know why it's failing and don't want to fix it in this PR (for the most part)
the failing ones I haven't looked into all of them, but I think at least half are more printing things
one is that nthroots need to be updated to explicitly show that the root is 2 (which I think is fine to change on mathsteps side)
another is to get rid of the space between coefficient and symbol when the symbol is also of the form x^2, so I'll make a PR to math-parser for that this weekend hopefully

eeeek it's getting close! just a few more things to clean up!
my plans are:

get all the tests passing or skipped
return to skipped tests and decide if I want to deal with them in this PR or leave as a TODO
address all the semantic math and porting related TODOs
go through all these changes and self-review and cleanup while cleaning them into more reviewable commits
see if folks from the community will review this for me?? (fingers crossed)
merge the new tree!!

down to 10 failing tests :o

600 passing (1s)
82 pending
and the linter passes!
🎉
next steps:

return to skipped tests and decide if I want to deal with them in this PR or leave as a TODO
go through the semantic-math related TODOs - some of them @kevinbarabash has already fixed and I can update already, some are left to be done
go through everything myself to see if it's in an okay state for other folks to review, do some cleanup on rough edges
ask around for anyone interested in taking a look - I can also go through and put the code into cleaner isolated commits if that helps! but that'll take some work so I'll only do it if it makes things a lot easier to review. I know Ahmed already said he could take a look, hopefully Kevin is willing as well!


[bug]FormBody charset

https://github.com/square/okhttp/blob/c273b3be385383842e44d25d6b7ca137ff6b1076/okhttp/src/main/java/okhttp3/FormBody.java#L50
https://github.com/square/okhttp/blob/c273b3be385383842e44d25d6b7ca137ff6b1076/okhttp/src/main/java/okhttp3/FormBody.java#L58
code
FormBody.Builder utf8FormBodyBuilder = new FormBody.Builder(StandardCharsets.UTF_8).add("name", "中");
FormBody utf8FormBody = utf8FormBodyBuilder.build();
System.out.println(utf8FormBody.value(0));
FormBody.Builder gbkFormBodyBuilder = new FormBody.Builder(Charset.forName("GBK")).add("name", "中");
FormBody gbkFormBody = gbkFormBodyBuilder.build();
System.out.println(gbkFormBody.value(0));

output
中      // right
��   // error, should be 中

Yep. Unfortunately the charset is used for encoding only. We don’t retain it in the FormBody object. We should figure out if application/x-www-form-urlencoded accepts a charset.
Also – you should consider switching to UTF-8. It’s the only charset anyone should use.

Yep. Unfortunately the charset is used for encoding only. We don’t retain it in the FormBody object. We should figure out if application/x-www-form-urlencoded accepts a charset.
Also – you should consider switching to UTF-8. It’s the only charset anyone should use.

Has this bug been fixed? I really need the framework support:
Content-Type: application/x-www-form-urlencoded; charset=UTF-8

@andrew-qiu default is "UTF-8",( if you use other charset, that will be bug...

@andrew-qiu default is "UTF-8",( if you use other charset, that will be bug...

Could you give me an alternative solution? I found almost all of web servers working in my corp only support the explicit format:
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
'Content-Type: application/x-www-form-urlencoded' would lead to apparently unreadable Chinese code.

@swankjesse https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

@swankjesse https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

It's Ok. I think I had just used an inappropriate framework.

Closing, no plans to change and we have closed other related issues https://github.com/square/okhttp/issues?q=is%3Aissue+charset+formbody


git submodule object doesn't exist

I can't seem to build the latest version due to "Server doesn't allow request for unadvertised object":
$ git clone --recurse-submodules https://github.com/bjz/gl-rs
Cloning into 'gl-rs'...
remote: Counting objects: 3773, done.
remote: Total 3773 (delta 0), reused 0 (delta 0), pack-reused 3773
Receiving objects: 100% (3773/3773), 2.37 MiB | 1.16 MiB/s, done.
Resolving deltas: 100% (2080/2080), done.
Submodule 'khronos_api/api' (https://github.com/capnm/Khronos_XML_API) registered for path 'khronos_api/api'
Cloning into '/Users/engstad/Src/Misc/gl-rs/khronos_api/api'...
remote: Counting objects: 1779, done.
remote: Total 1779 (delta 0), reused 0 (delta 0), pack-reused 1779
Receiving objects: 100% (1779/1779), 2.27 MiB | 808.00 KiB/s, done.
Resolving deltas: 100% (1534/1534), done.
error: Server does not allow request for unadvertised object 035f76ad3fe49cd928f073673f80e8247425b5c7
Fetched in submodule path 'khronos_api/api', but it did not contain 035f76ad3fe49cd928f073673f80e8247425b5c7. Direct fetching of that commit failed.

Same here, installing through Cargo:
error: failed to load source for a dependency on `gl`

Caused by:
  Unable to update https://github.com/bjz/gl-rs#e4a3bb70

Caused by:
  failed to update submodule `khronos_api/api`

Caused by:
  [9/-3] object not found - no match for id (035f76ad3fe49cd928f073673f80e8247425b5c7)

Update: the fix is simply to use the new repo URL: https://github.com/brendanzab/gl-rs.git

Things do seem to work (at least I can build, but then hit an unrelated issue) if I just clone the repository (without --recursive) and then do
mv .gitmodules .gitmodules.old
rm -fr khronos_api/api/
git add khronos_api/api
git commit -m "Test"
git submodule add https://github.com/capnm/Khronos_XML_API.git khronos_api/api


Upgrade DirectML version to 1.8.2(latest)

With https://github.com/microsoft/DirectML/issues/234 fixed, we can upgrade DML to latest 1.8.2 version now. @huningxin @fujunwei @BruceDai

Merge it.


Release after Release

Is it possible to trigger a release after another release has completed successfully?
for example: release to prod after release to test was successful

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

ID: d9e313c5-9120-9172-bc27-c21d10fcd5ae
Version Independent ID: 1a837182-591f-3cbc-1632-7b50d857b13c
Content: Release triggers for stages, branches, and pipelines - Azure Pipelines
Content Source: docs/pipelines/release/triggers.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

After stage trigger does that. Are you looking to trigger some other pipeline based on stage completion

Thanks, for the quick reply. "after stage trigger" is not good for me, I'll explain: I have a multi-stage release pipeline for my Test environment and I have another multi-stage release pipeline for my Production environment. What I want is to make sure the Production release can be initiated only if a Test release had been successful. The way I thought I could achieve that is by using the "New Release Triggers" like when a Build pipeline finishes than a new release is created, so do the same but with another Release pipeline instead of a Build pipeline.

My wish list: I want to deploy Test project (Smoke Test) Release after API from another pipeline Release successful deployment. Release triggered by another Release.

Thanks for your question. It looks like your question isn't an issue with the documentation, but an issue or question specific to your implementation or a bug in the product itself.
For help with a specific task, here are a couple of options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot

If you've encountered an issue with the product itself, to make sure it gets in front of the right people, please submit your bug here.
If you have an idea for improving the product, please submit your idea here.