high CPU usage on one master node since upgrading to 4.6

Describe the bug
After upgrading a cluster to 4.6, I see this on one of the master nodes:
 PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    808 openvsw+  10 -10   55280   9016   5080 R  44.7   0.1   1241:19 ovsdb-server
   2226 root      20   0  281076  25024   6000 R  43.4   0.2   1196:04 ovn-controller
    885 root      20   0  491428  22452  17228 R  39.1   0.1   1079:32 NetworkManager
   2861 root      20   0 2845640   1.6g  36704 S  21.2  10.4 654:54.30 kube-apiserver
   1135 root      20   0 3365296 332860  66300 S  10.3   2.0 523:00.76 kubelet
   3441 root      20   0 9542344   1.1g 173880 S  12.5   7.1 334:20.04 etcd

So the three top CPU (ab)users are network related. Any suggestions what to do?
Version
4.6 20201127
How reproducible
I have upgraded three clusters to 4.6 so far. I see the problem on all three clusters.
On one of the two other clusters it is affecting two of the three master nodes.
This is not good. It is going to become a serious problem (wasting so much of the available CPU capacity).
Log bundle
Can provide if needed.

Please provide journal logs for the three services in question

Is this OKD specific? I'd rather have OVN issues tracked in bugzilla

@LorbusChris you mean journalctl output?
@vrutkovs I don't know, I have no experience with OCP 4.6 yet.
But I'm right now deploying a new OKD 4.6 cluster from scratch to see if it affects new clusters as well or only upgraded ones.

@LorbusChris you mean journalctl output?
yes. Please also consider opening bugs against those components on bugzilla.redhat.com as Vadim suggested (in product Fedora)

Sure, NetManager is a FCOS component. But the main issue is OVN which is an OKD issue.

All of these are coming from the fedora repos and are thus Fedora components
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=openvswitch-ovn-kubernetes

I had a fresh deployed 4.6 OKD cluster now up for a couple of hours and did not see the problem there.
So it could be a problem for updated clusters only.
On the cluster in question I just saw such high CPU abuse by the same components also on one of the worker nodes.

ovsdb-server is a systemd unit (will look for log soon).
ovn-controller is actually a container running on that node, controlled by the ovnkube-node daemonset of OKD.

The "journalctl -u ovsdb-server.service" actually yields exactly nothing.

Well, I rebooted the two nodes and after the reboot it seems to be better.
So perhaps only a transient issue? I'll keep an eye on it.

The problem is coming back. On one master and one worker I had the problem again.
On the other mentioned clusters as well.
On a cluster installed from scratch with OKD 4.6 two days ago, two of three masters and three of six workers have the problem, too.

A must-gather of that freshly installed cluster is available here:
https://domino.ars.de/file/must-gather.local.6497755030432361477.tar.gz (163 MB)
The file is available there for one week.

I've hit this myself (NetworkManager
It seems putting
* hard nofile 524288
* soft nofile 4096

in /etc/security/limits.conf worked (increased soft open file limit to 4096 from default 1024).
However there is no definite way to reproduce this, so I'm not sure if the case.
If its still an issue, please check dmesg - there might be a message about open files limit

I'll give this a try.

Unfortunately, the nofile increase does not help with the problem on my clusters.

I am seeing a similar CPU issue with my cluster I upgraded from 4.5 -> 4.6.  My new 4.6 cluster seems fine.
I am not seeing any open file limit issue and I did not make any changes to /etc/security/limits
I am linking the must-gather

The OKD 4.6 2020-12-12 update did not help against this problem. I did not expect this, but updated the cluster, anyway (with --force).

Nobody reacted on Bugzilla so far ... :-(
https://bugzilla.redhat.com/show_bug.cgi?id=1905579

@vrutkovs, do you know of anyone working on this?

@vrutkovs, do you know of anyone working on this?

Possibly related, I have a vSphere UPI cluster which failed upgrading 4.5 -> 4.6 and along the way one of the compute nodes CPU went up by 10x what was normal and triggered a CPU alert in vSphere, becoming non responsive and did not update.  Eventually it became ready again, but was marked nonschedulable.
After a clean install of 4.6 with OVNKubernetes and running for several days, another compute node suddenly started using 10x CPU (and the cluster was essentially "idle" with no active users) I did a must-gather and there was nothing gathered from the problem node's machine-config-daemon (current log zero bytes).  I could also not ping or ssh into it.  Rebooting the. node brought it back to ready state.  From the machine-config-daemon's viewpoint after the fact, kubelet was failing health checks.  Looking at journalctl after the fact, there was no obvious cause.

Possibly related, I have a vSphere UPI cluster which failed upgrading 4.5 -> 4.6 and along the way one of the compute nodes CPU went up by 10x what was normal and triggered a CPU alert in vSphere, becoming non responsive and did not update.  Eventually it became ready again, but was marked nonschedulable.
After a clean install of 4.6 with OVNKubernetes and running for several days, another compute node suddenly started using 10x CPU (and the cluster was essentially "idle" with no active users) I did a must-gather and there was nothing gathered from the problem node's machine-config-daemon (current log zero bytes).  I could also not ping or ssh into it.  Rebooting the. node brought it back to ready state.  From the machine-config-daemon's viewpoint after the fact, kubelet was failing health checks.  Looking at journalctl after the fact, there was no obvious cause.

I have UPI cluster, freshly installed with 4.6.0-0.okd-2020-12-21-142926 and OpenshiftSDN with no applications. After every couple of days one of the worker (compute) nodes would display exactly same characteristics noted above by @bdlink . No ping / ssh, on the console of the server, there are some iptables-restore related journal log messages. After force reboot, there are no logs and machine behaves normally, so nothing much to look back at to find the problem..

I have UPI cluster, freshly installed with 4.6.0-0.okd-2020-12-21-142926 and OpenshiftSDN with no applications. After every couple of days one of the worker (compute) nodes would display exactly same characteristics noted above by @bdlink . No ping / ssh, on the console of the server, there are some iptables-restore related journal log messages. After force reboot, there are no logs and machine behaves normally, so nothing much to look back at to find the problem..

Any workaround or fix here

Any workaround or fix here

I am anxiously waiting as well ... but no response from anyone, unfortunately. :-(

I am anxiously waiting as well ... but no response from anyone, unfortunately. :-(

Any news on the topic? We're facing the same issue on all nodes of the cluster.

Nobody reacted on Bugzilla so far ... :-(

It should be filed against OCP -> Networking -> ovn-kubernetes, not Fedora's openswitch

add your problems there too if you have them, also must-gather are appreciated
https://bugzilla.redhat.com/show_bug.cgi?id=1925475

Nobody reacted on Bugzilla so far ... :-(

It should be filed against OCP -> Networking -> ovn-kubernetes, not Fedora's openswitch

@vrutkovs could you tell me exactly the product? I cannot find what you suggest.
I can either choose (under "Red Hat Products") either "OpenShift Container Platform" or "OKD".
But under neither I can find ovn-kubernetes as a component.

@kai-uwe-rommel i think he was talking about the section i posted it (https://bugzilla.redhat.com/show_bug.cgi?id=1925475)
Feel free to add to it

You may be right. I linked the there to the older Bugzilla item that I created in December.
I thought that Vadim meant me since he was quoting from my comment.

@vrutkovs in the meantime ( i do not think that the ovn team will fix this any time soon ) is it suggested to roll back to OpenShift-SDN?
https://docs.openshift.com/container-platform/4.6/networking/ovn_kubernetes_network_provider/rollback-to-openshift-sdn.html

@vrutkovs in the meantime ( i do not think that the ovn team will fix this any time soon ) is it suggested to roll back to OpenShift-SDN?
https://docs.openshift.com/container-platform/4.6/networking/ovn_kubernetes_network_provider/rollback-to-openshift-sdn.html

As noted earlier in this thread, my cluster has openshift SDN and still had the exact same issue..

@adarshaj do you even have ovn pods with openshift SDN or are the comparable pods with high CPU?

don't know what we did, but with force upgrading of some etcd members (our master nodes), like hart killing them and fixing with docs https://docs.openshift.com/container-platform/4.6/backup_and_restore/replacing-unhealthy-etcd-member.html#restore-replace-stopped-etcd-member_replacing-unhealthy-etcd-member we got it back to very less CPU usage... seems odd and still not the right

Stay tuned and monitor your cluster ... the problem (in my experience) keeps coming back no matter what I do ... :-(

Given the investigation on the OVS bug https://bugzilla.redhat.com/show_bug.cgi?id=1905579 it seems something is making ovn-controller add/remove GENEVE ports to other nodes. We recently fixed a similar issue that was related to hostnames, because hostnames are used as the chassis record index. This was fixed in upstream ovn-kubernetes in https://github.com/ovn-org/ovn-kubernetes/pull/1653 and fixed downstream in OpenShift via https://github.com/openshift/ovn-kubernetes/pull/279
Is each machine's hostname the same as the node name in the Kube API?

Yes, in our clusters the node name is always exactly the FQDN.

We have the exact same problem with a fresh install of OKD  v4.6.0-0.okd-2021-01-23-132511 with OVN
One afer the other, the cpu % of nodes goes very high (60%+) due to very high cpu consumption of theovn-controllerandovsdb-server processes eating most of the cpu
Rebooting the node seems to "reset" the problem but it comes back after a while. always
Some logs from anovnkube-nodepod that went wild:
2021-02-12T03:56:24Z|00359|poll_loop|INFO|wakeup due to [POLLIN] on fd 15 (<->/var/run/openvswitch/db.sock) at lib/stream-fd.c:157 (53% CPU usage)
2021-02-12T03:56:24Z|00360|poll_loop|INFO|wakeup due to [POLLIN] on fd 15 (<->/var/run/openvswitch/db.sock) at lib/stream-fd.c:157 (53% CPU usage)
2021-02-12T03:56:24Z|00361|poll_loop|INFO|wakeup due to [POLLIN] on fd 15 (<->/var/run/openvswitch/db.sock) at lib/stream-fd.c:157 (53% CPU usage)
2021-02-12T03:56:30Z|00362|poll_loop|INFO|Dropped 2720 log messages in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
2021-02-12T03:56:30Z|00363|poll_loop|INFO|wakeup due to [POLLIN] on fd 15 (<->/var/run/openvswitch/db.sock) at lib/stream-fd.c:157 (54% CPU usage)

I am seeing this issue as well with a fresh install of OKD 4.6.0-0.okd-2021-02-14-205305.

So many users are experiencing this problem. Yet progress on the solution is slow ... :-(
https://bugzilla.redhat.com/show_bug.cgi?id=1905579

@Reamer I know. I opened the Bugzilla ticket and probably did this wrong. Unfortunately, I cannot find out how to make it public now, later.

@Reamer I opened up permisisons on the BZ, PTAL

@LorbusChris, thanks. Somehow I was not able to "unselect" the selected groups in the ticket.

Can someone from OKD team please check the latest comments in the Bugzilla item and advise how to update this in OKD? Thanks! @LorbusChris @vrutkovs

OKD is using the same OVN images as in OCP. When the bug is fixed in OCP it would automatically land in OKD nightly

I do also have an OCP 4.6 cluster here and there we don't see the problem - yet. Probably because that still runs with OpenshiftSDN ... as probably many (if not most) OCP customers still do.
So even if the same problem applies to OCP it will take much more time until it surfaces there and will take even more time until pressure is high enough so that someone will fix this (hopefully by just updating that component).
So it would still be a long time that OKD users will have to wait and will be plagued by the problem.
Can we somehow give this issue higher priority at Red hat?

I see that there is no migration path from OpenshiftSDN to OVN-Kubernetes for UPI clusters.
So many customers of OCP will stay with OpenshiftSDN for a longer time until they can reinstall the entire clusters.

I just quickly installed an OCP 4.7.0 cluster with OVNKubernetes networking.
So far (it runs now for only about two hours) I don't see the issue yet ...

The bug does not occur in recent 4.6 and 4.7 versions of OCP.
So there still is the problem as the OCP folks may not see a need to quickly get this fix out of the door.

Definitely occurs in latest stable OKD 4.7

So,
a) we need to get the OCP folks to quickly deploy this fix into the product stream so that we also get it into OKD
b) cross our fingers that it actualy fixes the problem (currently it is only "this should probably fix it" thing)

we are experiencing the same problem, OVN components using an absurd amout of cpu

I have updated to 4.7.0-0.okd-2021-03-15-222638 and can confirm that  https://bugzilla.redhat.com/show_bug.cgi?id=1925475 has solved this problem.

Resolved in 4.7.0-0.okd-2021-03-21-094146


How do you specify plugins from local directories on windows?

I am trying to create a plugin for local additions to my vim config that are not tracked by my repository and I figured the easy way to do that would be to add the path that would be local to my vim runtime path.  Unfortunately expressing the path: $HOME\vimfiles\local or $HOME/vimfiles/local makes Plug think that I am trying to source a github repository.  What is the proper syntax for this? Is there a proper syntax for this on windows?

I don't use windows, so I'm not perfectly sure if it's appropriate but anyway this is the checker function on windows:
  function! s:is_local_plug(repo)
    return a:repo =~? '^[a-z]:\|^[%~]'
  endfunction

So it should be either an absolute path starting with a drive letter, or path starting with an environment variable in %VAR% form.

Thanks! I will let you know if that works.

One thing to consider. Drive letters should be case insensitive right? Other than that using ~ worked perfectly.

Yeah, =~? is a vim operator for case-insensitive match. So everything okay?

I did not know that. If that is the case then we are good to go.

@jimmyharris It wasn't obvious to me when I started writing vimscript either. It's an old language, with some incredibly dated ideas.

Thanks again for your help!


Code availability

Hi.
Is the code for CloneTracker XP barcode retrieval available paper.
Thanks

Sorry for late response.. but the email associated to this repo is a mail that a never use. Anyway, I just added the code, although I have no time to comment it more than this.
Regards,
GG


Massive iOS App Size avoidable via non-bitcode debug framework.

The Problem
I’m currently maintaining an old dead application for iOS and when upgrading from ancient frameworks, realized the output file size jumped from 12MB to about 500MB.
After chatting with some developers who are familiar with this project, and after some static analysis due to confusion, it seems to me that the reason for the very large size is Flutter.framework being composed almost entirely of LLVM bitcode generated for the App Store.
After thorough research on that topic it’s become clear to me that this size issue can be mitigated, **and should be,**for the following reasons:

Poor routers, such as mine, mean debug builds can take upwards of 10 minutes to install, due to slow transfer.
A portion of your community, including myself, has no intention of submitting created apps to the App Store.

I would like to propose the following non-destructive changes:

Adding a phase to the Flutter.framework build process that allows creation of Flutter.framework for iOS without bitcode.

Bundling the generated, much smaller, library labeled as a “Debug” framework.

Linking the “debug” framework whenever a debug build is initiated, instead of the large one.

Potentially: allowing a method of using the debug framework when creating release builds.

I apologize if this feature request is misinformed. It’s been very  difficult for me to find accurate information about Flutter on the topic.
While this is a minor issue for most developers, the changes specified here would allow a performance increase for all users, and it would make it possible for me to rely on flutter without having to use several Mach-O tools by hand to manually remove a massive unneeded portion of the the framework.

I would like to add as a P.S. that although, I’m assuming given the determination, I could compile Flutter without bitcode, that solution does not work for developers targeting the App Store.

Related: https://github.com/flutter/flutter/issues/46707

This was probably a duplicate of https://github.com/flutter/flutter/issues/56750 considering the timing, though it's impossible to know since we didn't get the template flutter doctor -v output.  It was a pretty narrow few builds where this happened, if I recall.
Can you confirm your debug builds aren't that large on the current stable version?

Closing, let us know if it's still happening and we'll reopen and investigate.


Optical Flow Simulation Broken

#3701 is not functional on master
It seems that inav isn't getting any data. Also QGC isn't working. I did a diff on a regular sim with gazebo_iris and gazebo_iris_opt_flow, and here is the diff
--- successful	2016-02-10 04:22:17.223721291 -0500
+++ failure	2016-02-10 04:22:24.623721208 -0500
@@ -1,4 +1,6 @@
-init] task name: mainapp
+Built target rotors_gazebo_mavlink_interface
+[init] shell id:<PHONE_NUMBER>4016
+[init] task name: mainapp

 ______  __   __    ___
 | ___ \ \ \ / /   /   |
@@ -28,34 +30,35 @@
 [Msg] Waiting for master.
 [Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
 [Msg] Publicized address: <IP_ADDRESS>
+[Wrn] [gazebo_lidar_plugin.cpp:77] [gazebo_lidar_plugin] Please specify a robotNamespace.
+[Wrn] [gazebo_opticalFlow_plugin.cpp:85] [gazebo_optical_flow_plugin] Please specify a robotNamespace.
 Publishing to: motors
 INFO  Sending initial controls message to simulator
 dataman: Unknown restart, data manager file 'rootfs/fs/microsd/dataman' size is 103090 bytes
+[Wrn] [RaySensor.cc:312] ranges not constructed yet (zero sized)
 INFO  TONE_SET_ALARM 0
 INFO  GYROSIM::init
 INFO  GYROSIM_gyro::init base class ret: 0
-WARN  baro IOCTL 94631
+WARN  baro IOCTL 150523
 Command failed, returned 1
 pwm_out_sim MODE_8PWM
-[Wrn] [Publisher.cc:140] Queue limit reached for topic motors, deleting message. This warning is printed only once.
-[Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/0, deleting message. This warning is printed only once.
 [Msg] Connected to gazebo master @ http://<IP_ADDRESS>:11345
 [Msg] Publicized address: <IP_ADDRESS>
+[Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/0, deleting message. This warning is printed only once.
+[Err] [InsertModelWidget.cc:298] Missing model.config for model "/home/jgoppert/git/Firmware/Tools/sitl_gazebo/models/rotors_description"
+[Wrn] [Publisher.cc:140] Queue limit reached for topic motors, deleting message. This warning is printed only once.
+INFO  simulator is slow. Delay added: 10853 us
 [Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/1, deleting message. This warning is printed only once.
 [Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/2, deleting message. This warning is printed only once.
-[Err] [InsertModelWidget.cc:298] Missing model.config for model "/home/jgoppert/git/Firmware/Tools/sitl_gazebo/models/rotors_description"
-[Wrn] [Publisher.cc:140] Queue limit reached for topic imu, deleting message. This warning is printed only once.
-[Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/3, deleting message. This warning is printed only once.
-[Wrn] [Publisher.cc:140] Queue limit reached for topic gazebo/command/motor_speed, deleting message. This warning is printed only once.
 WARN  pwm_out_sim: No valid fds
-WARN  baro IOCTL 1096073
+WARN  baro IOCTL 1124823
 INFO  GYROSIM::_set_sample_rate 1000003 Hz
 INFO  GYROSIM: Changed sample rate to 500Hz
 INFO  GYROSIM::_set_sample_rate 1000003 Hz
 INFO  GYROSIM: Changed sample rate to 500Hz
-WARN  baro IOCTL 1096373
-WARN  baro IOCTL 1096557
-WARN  baro IOCTL 1096980
+WARN  baro IOCTL 1126289
+WARN  baro IOCTL 1126532
+WARN  baro IOCTL 1127551
 INFO  TONE_SET_ALARM 1
 ERROR px4_task_spawn_cmd: failed to set name of thread 34 0

@@ -80,15 +83,14 @@
 WARN  log buffer size: 8192 bytes
 telem> [log] log dir: rootfs/fs/microsd/log/2016-02-10
 WARN  sdlog2: failed setting sched params
-telem> [log] start: 09_20_39.px4log
-pxh> WARN  changing partner IP to: <IP_ADDRESS>
-WARN  pwm_out_sim: No valid fds
-WARN  [inav] GPS signal found
-WARN  init ref: lat=47.3977420, lon=8.5455940, alt=  0.0540
-INFO  home: 47.3977420, 8.5455940, 0.06
-INFO  TONE_SET_ALARM 15
-INFO  TONE_SET_ALARM 0
-INFO  TONE_SET_ALARM 4
-INFO  TONE_SET_ALARM 0
+[Wrn] [Publisher.cc:140] Queue limit reached for topic motor_speed/3, deleting message. This warning is printed only once.
+[Wrn] [Publisher.cc:140] Queue limit reached for topic gazebo/command/motor_speed, deleting message. This warning is printed only once.
+[Wrn] [Publisher.cc:140] Queue limit reached for topic imu, deleting message. This warning is printed only once.
+telem> [log] start: 09_21_40.px4log
+WARN  changing partner IP to: <IP_ADDRESS>
+pxh> WARN  pwm_out_sim: No valid fds
+WARN  INAV poll timeout
+WARN  Q POLL TIMEOUT
+[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/pose/local/info, deleting message. This warning is printed only once.

My guess is that the vehicle name is different or something similar. Also, there is a warning about specifying a namespace for the sensors:

[Wrn] [gazebo_lidar_plugin.cpp:77] [gazebo_lidar_plugin] Please specify a robotNamespace.
[Wrn] [gazebo_opticalFlow_plugin.cpp:85] [gazebo_optical_flow_plugin] Please specify a robotNamespace.

@jgoppert I just did a new clone of master and the simulation works. I get the two warnings with the robotNamespace but that has no effect on the simulation

Gazebo starts up. No errors.  Just no communication with qgc.

It works for normal gazebo sim, notice how inav works for that build and gets a simulated gps lock, do you get this with opt flow?

Doing a fresh clone myself to confirm.

Yes I do get "WARN  [inav] GPS signal found" with the opt flow simulation

The bug is still there for me. I'm running ubuntu 14.04, ros jade, gazebo 1.6.
I'm guessing you are probably running ros indigo?

Hm strange... I'm running ubuntu 14.04, ros jade, gazebo 6.5.1. Are you in a network where others are running a simulation as well?

@ChristophTobler no, just using my laptop here. I followed install guidelines for ros with gazebo6 here: http://gazebosim.org/tutorials?tut=ros_wrapper_versions

Using build command: make posix_sitl_default gazebo_iris_opt_flow

I use: make posix gazebo_iris_opt_flow. not sure if it makes a difference

I just did a normal installation of gazebo I think

Build command didn't make a difference. So instead of apt install you built from source, or installed a binary directly?

I'm running 6.5.1 via apt. Going to try a computer restart.

I think I did it like this: http://gazebosim.org/tutorials?tut=install_ubuntu& (Alternative installation: step-by-step). But it still was gazebo 6 back then

what qgc version are you running? I'm running 2.9.2

@ChristophTobler I was running it from ppa which as outdated at 2.8.0. Upgrading to 2.9.2 fixed it, thanks!

It also seems to require that I start qgc before the sitl.

In fact, I have to shut down qgc and start it again before each run for it to connect, which is kind of weird.

I always have to press Disconnect (upper right corner in qgc) before I run a new simulation. Maybe that works for you as well

is the issue fix ? I am having trouble as well with making the optical flow display data from the gazebo simulator.


Support on Xcode 17 and iOS 15

Are there any plans to update this framework to work with the new versions of xcode, swift and iOS? I noticed that trying to build on latest xcode and OS it gives an error:
ReMVVMRxSwift/Sources/ReMVVM+Rx.swift:75:19 Type 'Reactive<Base>.ReactiveObserver2' does not conform to protocol 'StateObserver'

It looks like it's just missing an explicit typealias State = Base.State.Wrapped

Hey Jan, change is pushed to the repo, thanks


1865 audit org user

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 [M] add/revoke god users with mcb


Add projects

To display what I have done add some projects with samples and explanations.
Note: inspiration came from https://www.braxtonhuff.com/

Page made.
Best is to make tiles with only the image and transition to modal when clicked on to show more detail about the project. (Not that there are a lot of projects....)


Compilation error: 'Can only use .str accessor with string values!'

Error message:
length of df before:0
Traceback (most recent call last):
File "script.py", line 36, in
df = df[~df["Name"].str.contains("undefined")]
File "/usr/local/lib/python3.8/site-packages/pandas/core/generic.py", line 5135, in getattr
return object.getattribute(self, name)
File "/usr/local/lib/python3.8/site-packages/pandas/core/accessor.py", line 187, in get
accessor_obj = self._accessor(obj)
File "/usr/local/lib/python3.8/site-packages/pandas/core/strings.py", line 2100, in init
self._inferred_dtype = self._validate(data)
File "/usr/local/lib/python3.8/site-packages/pandas/core/strings.py", line 2157, in _validate
raise AttributeError("Can only use .str accessor with string values!")
AttributeError: Can only use .str accessor with string values!
I will try to fix the bug and come back to you with a pull request.

Okay, great no problem.
Thank you.


Rename "Change Language Mode" to "Change Syntax Highlighting"

I was looking for a way to change the highlighting of my code and found it confusing that it was named "Change Language Mode". Most other editors I've used in the past at least included the word 'Syntax'.
I don't seem to be the only person that couldn't easily find this feature; https://stackoverflow.com/questions/30775551/how-to-manually-set-language-for-syntax-highlighting-in-visual-studio-code
Is this something that could be re-named? It would definitely make it easier to transition between editors!

It's not just about syntax highlighting, it also affects all language-specific features like IntelliSense, Navigation, Refactoring...

The language mode picker gets one of the most proeminent spots in our UI in the status bar and that is the primary way to change the language:

I would not rename it to "Change Language Syntax" as syntax highlighting is only part of it. VS Code offers intellisense, hover, refactorings, etc. so the scope of changing the language is more than just the syntax highlighting.


Pep8 all the things

Automatic pep8-ifiers cannot change class-, object-, variable- or constant-names, only complain about them.

[x] Update all code with an automatic checker/changer (ruff? black?)
[ ] Manually update names

Manually update names is a very breaking change and might warrant a 1.0-release.


[Fabric] Crash on open crafting terminal

When i open crafting terminal my game crashes.
fabric, minecraft 1.19, mod version 1.3.5
https://crashy.net/M6DhonydmWCrjKS4wSpK

Normal terminal works.


[STORM-1217] - making small fixes in RAS

The bug fixes look good, but could you file a JIRA just to track that these fixes went in?

@revans2 will fill a JIRA to track

+1

+1

still +1

@kishorvpatil can we merge it now?

Merging this since comments are address, >= 2 +1's, one by PMC.


Overview of Deployment on an Existing Kubernetes Cluster

https://www.kubeflow.org/docs/started/k8s/overview/
There is no Kubeflow 1.2 and no Kubernetes Versions 1.19 in the table.
Also the oldest versions may be marked as deprecated.

Duplicated.


Pike's USS Enterprise Schematics shows up under Items, not Schematics

Title says it all. When looking through the "Unneeded Items" tab, these Schematics show up in the wrong spot.

@AdmiralMemo Do they also show under the schematic section? Also, I'm assuming that you have the ship max level?

@AdmiralMemo This should be fixed now - let us know if you still encounter any issues.


cower fails to install

cower fails to install due to a missing dependency, yajl.

AUR packages are installed via makepkg using the -s option, which uses pacman to install missing dependencies. Dependencies which are AUR packages can't be installed with pacman, so we do have to explicitly install those, but yajl is in the official repos. So your pull request should be unnecessary.
Can you share the exact error you encountered on the cower task?
It may have been a networking issue, where pacman just temporarily failed to find the yajl package. We used to have a similar issue where the macchiato task would cause networking services to bounce. Ansible would move on to the next package installation task before networking was brought back up, causing pacman to error out. I don't think there is anything like that in the base role currently, but I'm not sure what else would cause the cower install to fail.

I was actually in a bit of a rush that morning, and didn't think to log the error. I re-ran the role a couple times, and after repeated failures, simply installed the dependency myself. I'll see if I can recreate that this evening.

I've confirmed that this was due to a temporary network connectivity issue.


[Broker] Preventing extra dispatch when entries will make permits negative

I noticed that the broker currently does not consider the number of entries when determining if it should dispatch messages to the consumer. Due to the missing check, the broker can send more messages than available permits.
This PR prevents that from happening for persistent topics.
Related to #6054

@rdhabalia @codelipenghui @merlimat @sijie Anything else I should add to this PR?

The reason for this is that we want to avoid having to re-read messages again from storage. The number of permits going to negative is "fine", in the sense that the next round will adjust.

@merlimat If the permits go negative when the subscription is stuck, then the approach by @rdhabalia to unblock the subscription won't work. See https://github.com/rdhabalia/pulsar/blob/df5195475edd2b6938849e7b2e5bc52aabad207d/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentDispatcherSingleActiveConsumer.java#L587

I'm closing this because there are a number of areas that expect permits to be <= 0 to control message flow, and this PR doesn't address the root issue behind subscriptions getting stuck.


Browsers can't access sites since upgrade to 10.13.3

I've just upgrade my machine to 10.13.3 and both Safari (11.03) and Chrome (64.0.3282.140) can no longer access my sites served up by pow.
Error :

Safari can’t open the page “https://wrap-scraper.dev” because Safari can’t establish a secure connection to the server “wrap-scraper.dev”.

And...

This site can’t be reached wrap-scraper.dev refused to connect.

Note I have tried both http:// and https:// with the same outcome.
Firefox (57.01) and curl -H host:wrap-scraper.dev localhost/  both still work as expected.
Any ideas on what is happening?

@dwkns Try to uninstall/reinstall it just worked for me.
I'm launching/stopping Pow from http://anvilformac.com


Added support for jenkins github pull request builder environment variables

Some of them override existing variables, some of them add new fields

Thanks for the PR. Do you have documentation showing these variables off? Thanks

Yup, https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin#GitHubpullrequestbuilderplugin-EnvironmentVariables

Thanks @fracmak for the contribution!

Thanks for quickly merging the PR :-)


Correct the comments

You probably forgot to edit the _includes/comments.html file.
Create an account in Disqus and change this file so the comments work correctly.
Only edit this part of the code in  _includes/comments.html:

Por favor, ative o JavaScript para ver os comentários powered by Disqus.

Any questions, I am available to help!

@mateussmedeiros Thanks for reviewing code!


Deprecation Warning in Ember 2.18

I'm experimenting with PWA, thanks for the great work! I thought I'd share this deprecation I got on a fresh install:
DEPRECATION: An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules. Instead, consider doing: require("resolve").sync(something, { basedir: project.root }). Accessed from:   new NPMDependencyVersionChecker (/.../node_modules/ember-service-worker/node_modules/ember-cli-version-checker/src/npm-dependency-version-checker.js:11:33)

Fixed


Remove retrying actor tests on CI and get to the bottom what fails

Flaky tests are annoying, but just retrying them is a 🩹 that can be dangerous, because we might actually have bugs that only sometimes happen but get obfuscated by retries.
We should create a more stable test framework and not rely on retries.

Related to https://github.com/itchysats/itchysats/issues/2815

Related to #2825

I duplicated this with https://github.com/itchysats/itchysats/issues/2916
😅


As/tv os

Summation of pull request
This PR is intends to add tvOS support to ConsistencyManager-iOS (which may have a confusing naming scheme if made multi-platform?)
Project additions
ConsistencyManager project:

Adds appletvos and appletvsimulator as supported platforms
Adds TARGETED_DEVICE_FAMILY 3 (for tvOS) in project file

SampleApp / ConsistencyManagerDemo project:

Adds ConsistencyManagerDemo-tvOS target to ConsistencyManagerDemo project
Ports ConsistencyManagerDemo to ConsistencyManagerDemo-tvOS
Adds ConsistencyManagerDemoTests files to ConsistencyManagerDemo-tvOSTests target membership

Cocoapods:

Suggests 5.1.0 pod release in podspec
Adds tvos requirements to podspec

Misc:

Some xibs opened with Xcode 8.2.1; automatically modified xib files

Demo app for tvOS:

Cool tidbits
Per http://promisekit.org/news/2016/08/Multiplatform-Single-Scheme-Xcode-Projects/, including tvOS support in the ConsistencyManager target.

So first of all, thanks for the PR. Good point with -iOS. Created https://github.com/linkedin/ConsistencyManager-iOS/issues/50.

Going to pull this down locally and take a look at the changes.

👌

Going to look over the code. Mostly looks good but a couple of comments so far:

In the demo app, there's still a scheme for ConsistencyManager which doesn't do anything anymore (UI shows it as a cog). Can we delete that?
In the demo app, there's some code which is exactly the same. Can we move that to a shared folder or something and just add it to both targets? I think just the models and the Network folder.

Left a couple of comments on the code too, but all minor stuff. Then can merge this in. :D

All patch these up and push 👍

I'm not seeing the empty scheme for ConsistencyManager in the SampleApp project. Is it still in there after this push?

I'll check on the empty scheme, but don't worry about that either way. It may be a local thing, and we can delete that later. Checking changes.

Yep. LGTM. Merging.

🎉 Thanks!


Request URL Your URL didn't respond with the value of the challenge parameter.

Rasa version:
rasa-core                          0.14.4
rasa-core-sdk                      0.14.0
rasa-nlu                           0.15.0
Python version:
python 3.7
Operating system (windows, osx, ...):
windows10
Issue:
When i try to integrate my rasa bot to slack , I try to do Event Subscriptions  it does not work.
so i try to view the log using  heroku logs --tail
i get this message. Any help?
Error (including full traceback):
019-06-04T00:11:49.465060+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=POST path="/webhooks/slack/webhook" host=jabu1234.herokuapp.com request_id=a66010d7-1918-4c52-aad9-e72bee75d540 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

Command or request that led to error:
when i try to enable event in slack api it give me this error

Request URL Your URL didn't respond with the value of the challenge parameter.
https://jabu1234.herokuapp.com/webhooks/slack/webhook

Content of configuration file (config.yml) (if relevant):

pipeline: "tensorflow_embedding"
training_data,
            augmentation_factor=50,
            epochs=500,
            batch_size=10,
            validation_split=0.2

Content of domain file (domain.yml) (if relevant):
slots:
  group:
    type: text

intents:
 - greeting
 - get_jabu

entities:
 - product
 - jabuinfo

templates:
  utter_greet:
    - "Hello! What can I do for you?"
  utter_JABU:
   - "The Joseph Ayo Babalola University (JABU) is a private Nigerian university located in Ikeji-Arakeji in Osun State, established by the Christ Apostolic Church (CAC) Worldwide. The university is named after the first Spiritual leader of Christ Apostolic Church, Joseph Ayo Babalola (1904–1959); it is located at the place where he was called by God to slay the Ogobungo ogre in 1928. Joseph Ayo Babalola University is a fully residential institution. The university offers courses in the following colleges; Agricultural Sciences, Environmental Sciences, Humanities, Law, Management Sciences, Natural Sciences and Social Sciences. Due to its Christian foundations, male and female in the school are enjoined to adopt an extremely modest mode of dressing while on campus"
actions:
 - utter_greet
 - utter_JABU

Screen shot of my log

Screenshot of my slack event sub

pls help @akelad @rasa

what does your credentials.yml look like?

facebook:
verify: "horoscope-bot"
secret: "28651269458eef5dd17d6460b506b6d2"
page-access-token:
"EAAJiUznmFTcBAJCx99XQc3UZBFvpaMGWYzq50p6yp8uXapRF2jJs9sSGMEMCYicrnXNhIDGmCfMMWnMN6FG3CzPNiPs53jDVqGfLgJ3Py7tWYaAzLBZC8Qip4Hr5jM4ohh63TiCaVukNGHo8XYjv3HvYZCUQLKeFY8EC8HF8gZDZD"
am new am using a book i got online to do this please this is
credentials.yml please correct me please
On Tue, Jun 4, 2019 at 9:24 AM Akela Drissner-Schmid <
<EMAIL_ADDRESS>wrote:

what does your credentials.yml look like?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RasaHQ/rasa/issues/3690?email_source=notifications&email_token=AHG4DAVGKITI2TR4RPIPPFTPYYRCNA5CNFSM4HSWDOOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW3Z7LQ#issuecomment-498573230,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHG4DAR7RGUC3O4OVRWZOOLPYYRCNANCNFSM4HSWDOOA
.

This is a facebook access token, that's not the configuration for the slack channel. Please take a look here about how to set it up: http://rasa.com/docs/rasa/user-guide/connectors/slack/
And please post any future usage questions you have in the forum


allow_abbrev error

Hello
Whenever I try to run it, it shows the following error:
Traceback (most recent call last):
File "safaribooks.py", line 983, in
allow_abbrev=False)
TypeError: init() got an unexpected keyword argument 'allow_abbrev'
My python version:    Python 3.4.3

This is a duplicate issue.
Please read #14


Sam/metrics grid tweaks

change metrics view css styling from flex to grid to allow for different sizing of charts in display. exctracted from metrics view to dashboard component the dashboard div containers and adjusted conditional rendering logic of components to be displayed inside the container.

Reviewed and approved Metrics/Grid Tweaks


EM-473: Convert the rest to TypeScript

could you try to run 'npm run lint'? I see some linting changes there

All good, no issues found


Wrong behaviour when showing Context Menu

Hey, I'm currently facing an issue with context menu which I'm not able to find the reason or solution. I hope you are able to give me some lights on this issue.
Behaviour
When I click anywhere in the spreadsheet for the first time, the browser's context menu appears. Following clicks show the Spreadsheet's context menu correctly.

Expected behaviour
Show Spreadsheet context menu every time the user right clicks anywhere in the spreadsheet.
Browser
It seems to happen with Edge and Chrome
Operating system
Windows 11 Enterprise

Hey @lbozzo ,
I cannot reproduce the issue (Mac OS, multiple browsers), so I am assuming it is a windows thing?
Is the window in focus when you first right-click?

Hey @nick-keller , I managed to replicate it consistently. Yes, it seems to happen only on Windows and it happens when the cursor is moved right after the right-click. It's more common for example with a trackpad, as it is normal to move the fingers a bit after clicking.
I might be wrong, but I created a sandbox with a normal div and I used both event.preventDefault() and event.stopImmediatePropagation() with the idea of blocking any other listeners (and maybe even the browser) of that same event and it seemed to work.

Hey @lbozzo can you help me please. I know this isn't the place to ask for help but I will really appreciate your kind response. Those images you shared, I can see you used select many times. Can you please explain how you did that or share code snippet ?
I have followed there documentation https://react-datasheet-grid.netlify.app/docs/examples/implementing-select but I got stuck because there final version was missing something. I am also creating similar app like yours.

@zaryabdev sure, I would like to help you but I'm not able to share code snippets as this is confidential. We might discuss it outside this thread or in the Discussion section.


Added some docs to result type

@lihaoyi Can you please check if these are correct?

Looks good to me. Note the difference between Failed which generally is intentionally used, and Exception which refers to things that blow up generally-unintentionally

With Failed you mean Failure, don't you?

yea


Code cleaning

Some cleaning operations to prepare the 0.4 release:

version updatting in setup.py
some useless modules deletion, some module renaming
code reading (in processing)
update README.md

Fixes the issue #63 .

Some new commits fits your remarks. If everything is OK, we can merge, and release the new code version.


Update README.md typo "lastest" to "latest"

Typo which I noticed in the readme. "lastest" should be written "latest"

Merged. Thank you!


Update links to legacy docs for new site structure

@petehamilton Here you go!

@timrogers looks good! Rebase?

@harrison On it


Cookbook HTTP Requests update scalaj-http to work with scala 2.12.x

Updated docs to make sure that HTTP Requests example compiles with Scala 2.12

lgtmthx


Add linux-arm64 RID builds

The normal approach is to take the oldest OS supported and use that to make linux-$ARCH RID packages. Here, we use ubuntu 16.04.
This commit makes the following changes:
Add a new dockerfile for linux-arm64, which is actually just a copy of Dockerfile.ubuntu.16.04-arm64. This is so we can build linux-arm64 RID packages in CI.
Add a dllmap for mapping from armv8 (which is what mono calls arm64/aarch64 - see https://www.mono-project.com/docs/advanced/pinvoke/dllmap/) to the linux-arm64 RID.
Also fix build.libgit2.sh to handle building natively on arm64. I used this to build libgit2, using ./build.libgit2.sh, on RHEL 8 on arm64.

Some open questions:

Is there a way I can verify the built libgit2 works end-to-end?

What is the process of getting this released?

Once CI systmes (eg https://github.com/Microsoft/azure-pipelines-agent/issues/1521#issuecomment-424466976) start supporting arm64, maybe we might want to do native builds on arm64 instead of cross compilation?

Closing because https://github.com/libgit2/libgit2sharp/pull/1714 does it much better.


WIP : Integrating Birdman dependency

This is first iteration of getting the Birdman dependency integrated into this package.
Note that this is work in progress - we had to reimplement the base class in order to make things work.
Ideally, all of the boilerplate code (i.e. BaseModel or NegativeBinomialCaseControl) would be in Birdman instead of this package. So we probably won't merge this PR in until those logistics are sorted out.
Other TODO

[x] Get unittests to confirm that the parameters are estimated ballpark correctly
[ ] Get tests in place to confirm that diagnostics are working properly.  Diagnostics include effective sample size, Bayesian R2, posterior predictive checks, Rhat and E-BFMI.
[x] Make plugin output qiime2 Artifacts (likely bypassing q2cli until those networking issues are resolved).  We want to do this so that we can easily pass qiime2 Artifacts to qurro / gneiss / empress
[ ] Confirm that SLURM still works

CC @gibsramen

A couple of things.  First, I had to modify the parallelism using dask.Client in the base class in order to allow slurm to spawn Stan processes.
Also, I'm running into issues aggregating information from the fits.  Here is an example of one of these issues
======================================================================
ERROR: test_cc_slurm (__main__.TestNegativeBinomialCaseControl)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_stan.py", line 146, in test_cc_slurm
    inf = nb.to_inference_object()
  File "/mnt/home/jmorton/software/q2-differential/q2_differential/_stan.py", line 565, in to_inference_object
    **args
  File "/mnt/home/jmorton/software/q2-differential/q2_differential/_stan.py", line 409, in to_inference_object
    inference = fit_to_inference(self.fit, **args)
  File "/mnt/home/jmorton/software/BIRDMAn/birdman/model_util.py", line 169, in multiple_fits_to_inference
    all_vars = fits[0].stan_variables().keys()
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py", line 968, in stan_variables
    result[name] = self.stan_variable(name)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py", line 945, in stan_variable
    self._assemble_draws()
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py", line 719, in _assemble_draws
    with open(self.runset.csv_files[chain], 'r') as fd:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpylqag5nj/nb_case_control_single-202104281725-1-phztvt88.csv'

There is something weird going on with the intermediate files.
My current suspicion is that Stan is deleting the intermediate files in tmp after the session is over; which is not good for Birdman since we need those files.
When I specify the output directory, I now get a different error
======================================================================
ERROR: test_cc_slurm (__main__.TestNegativeBinomialCaseControl)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_stan.py", line 146, in test_cc_slurm
    nb.fit_model(dask_cluster=cluster)
  File "/mnt/home/jmorton/software/q2-differential/q2_differential/_stan.py", line 245, in fit_model
    sampler_args=sampler_args)
  File "/mnt/home/jmorton/software/q2-differential/q2_differential/_stan.py", line 324, in _fit_parallel
    all_fits = dask.compute(futures)[0]
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/dask/base.py", line 563, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/client.py", line 2655, in get
    results = self.gather(packed, asynchronous=asynchronous, direct=direct)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/client.py", line 1970, in gather
    asynchronous=asynchronous,
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/client.py", line 839, in sync
    self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/utils.py", line 340, in sync
    raise exc.with_traceback(tb)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/utils.py", line 324, in f
    result[0] = yield future
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/tornado/gen.py", line 762, in run
    value = future.result()
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/distributed/client.py", line 1829, in _gather
    raise exception.with_traceback(traceback)
  File "/mnt/home/jmorton/software/q2-differential/q2_differential/_stan.py", line 314, in _fit_single
    **sampler_args
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/model.py", line 791, in sample
    mcmc = CmdStanMCMC(runset, validate_csv, logger=self._logger)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py", line 384, in __init__
    self.validate_csv_files()
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py", line 650, in validate_csv_files
    thin=self._thin,
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/utils.py", line 464, in check_sampler_csv
    meta = scan_sampler_csv(path, is_fixed_param)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/utils.py", line 520, in scan_sampler_csv
    lineno = scan_sampling_iters(fd, dict, lineno)
  File "/mnt/home/jmorton/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/utils.py", line 781, in scan_sampling_iters
    lineno, num_cols, len(line.split(','))
ValueError: line 463: bad draw, expecting 137 items, found 37

Ok, now this is really messed up.
So I'm able to get fits, but things crash when I try to convert them to arviz objects.
az.from_cmdstanpy(posterior=nb.fit[0])
---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
<ipython-input-28-4370c5f5c682> in <module>
----> 1 az.from_cmdstanpy(posterior=nb.fit[9])

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/arviz/data/io_cmdstanpy.py in from_cmdstanpy(posterior, posterior_predictive, predictions, prior, prior_predictive, observed_data, constant_data, predictions_constant_data, log_likelihood, coords, dims, save_warmup)
    669         coords=coords,
    670         dims=dims,
--> 671         save_warmup=save_warmup,
    672     ).to_inference_data()

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/arviz/data/io_cmdstanpy.py in to_inference_data(self)
    333             save_warmup=self.save_warmup,
    334             **{
--> 335                 "posterior": self.posterior_to_xarray(),
    336                 "sample_stats": self.sample_stats_to_xarray(),
    337                 "posterior_predictive": self.posterior_predictive_to_xarray(),

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/arviz/data/base.py in wrapped(cls, *args, **kwargs)
     44                 if all([getattr(cls, prop_i) is None for prop_i in prop]):
     45                     return None
---> 46             return func(cls, *args, **kwargs)
     47
     48         return wrapped

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/arviz/data/io_cmdstanpy.py in posterior_to_xarray(self)
     85             self.posterior,
     86             items,
---> 87             self.save_warmup,
     88         )
     89

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/arviz/data/io_cmdstanpy.py in _unpack_fit(fit, items, save_warmup)
    490             num_warmup = fit.num_draws_warmup
    491
--> 492     draws = np.swapaxes(fit.draws(inc_warmup=save_warmup), 0, 1)
    493     sample = {}
    494     sample_warmup = {}

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py in draws(self, inc_warmup, concat_chains)
    590
    591         if self._draws is None:
--> 592             self._assemble_draws()
    593
    594         if inc_warmup and not self._save_warmup:

~/miniconda3/envs/qiime2-2021.2/lib/python3.6/site-packages/cmdstanpy/stanfit.py in _assemble_draws(self)
    717                 )
    718         for chain in range(self.chains):
--> 719             with open(self.runset.csv_files[chain], 'r') as fd:
    720                 # skip initial comments, up to columns header
    721                 line = fd.readline().strip()

FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpwomsz3ar/nb_case_control_single-202104282125-1-_xc2vklb.csv'

But here is the weird part -- if I run the exact same command in the same python session, it works fine.
Now I've added a for / try loop and the tests pass.
I have no idea why this works, but I'm going to have to swing it in the meantime.

Ok, we got more problems.
Below are some outputs of the posterior predictive checks.
And the weirdest part here is that all of the fits are also returning non-sensible values.
         Estimate       SE
elpd_loo      nan      nan
p_loo         nan        -

There has been a warning during the calculation.   I'm going to merge this in since it is such a huge pull request.  Will add CI support along with slurm tests in a bit.


Need better visual feedback of area lights in viewport.

Particularly the size/shape.

with a BGL overlay drawing?

Perhaps.  Where's the entrypoint for doing that?
Part of the issue is that we write the rib for area lights based on the transform alone.  The area lights in RIB geometry wise are all 1 unit, and to make a 4x4 rectangular light you would scale it.  ex:
Scale 4 4 4
Geometry "rectlight"
So we're using the objects transform to set the size.
Now, what could be done is add to the light object properties a shape (rectangle, sphere, etc) and a size property.  Use those for size, and base the drawing overlay on that property.

I have adjusted the area light to display the correct size in the viewport. This only works for the rectangle and square shapes. Any other shapes must be drawn by the plugin.

I'm going to call this "closed" for now.  Also I made it so that when you add the renderman node tree it switched from point type to area.


Adding deno.config

Adding a deno.config file provides:

A recognizable file for the deno lsp to reference when working in editors other than VSCode
A set of tasks to build and test with all flags with deno task build and deno task test

At this time the "fmt" section of the config is set to ignore all files since the current style deviates from deno's default style.

Do we still need tsconfig.json?

We don't really need tsconfig.json anymore, I can remove it and update the PR. And yeah we could update the README with the new task commands.

Any particular reason why this is a .json and not a .jsonc? I don't think it matters yet but if we ever want to add comments to it I think it would be valuable to have.

At this time the "fmt" section of the config is set to ignore all files since the current style deviates from deno's default style.

A better question is: "should we codify our deviations and enable formatting?"

deno-config.json is now deno-config.jsonc to allow for future comments. The README has been updated to use the more succinct deno task syntax for local development


Improved README.md

Removed redundant instructions (Exporting variables doesn't seem to be necessary in order for compiling to work)
Improved wording

The variables have to be set if it can't guess them automatically, I wouldn't remove that section.

The variables have to be set if it can't guess them automatically, I wouldn't remove that section.

I mean, is there any other option that could be chosen over instead?

I mean, is there any other option that could be chosen over instead?

Elaborate.

I mean, is there any other option that could be chosen over instead?

Elaborate.

There are options such as BL60X and BL606 for hal_drv, but they are not projected to be used due to the way that the Makefile's are written under customer_app. There's no way that any other option other than BL602, without the user explicitly desiring to do so.
For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.

For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.

It assumes the examples are inside the SDK folder, this would break when someone copies an example out and doesn't set the variable. The documentation would be better if it mentioned this nuance.

For the same reason, I wouldn't understand why guessing the directory could go wrong under a Unix-like environment either.

It assumes the examples are inside the SDK folder, this would break when someone copies an example out and doesn't set the variable. The documentation would be better if it mentioned this nuance.

Will correct in a bit.

Fixed the conflict.


Single app.yml file doesn't work.

I have a single app.yml file in locales folder like this:
Settings:
  en: Settings
  tr: Ayarlar
Country:
  en: Country
  tr: Ülke
City:
  en: City
  tr: Şehir

I initialized with i18n!() and I set the labels of the program like t!("Settings").
But the strings I got on the labels like:
en.Settings
en.Country
en.City

Which is not I expected:
Settings
Country
City

Also tried running the app with LANG=tr_TR.UTF-8 myapp and I still see en.Settings not tr.Settings or translated Ayarlar.
Also:
The output of the println!("{:?}", rust_i18n::available_locales!()); is ["app"]
It seems single file is not supported yet in version = "2"

Add version: 2 in this file.
_version: 2

Yeah that solved, Thanks!


Custom verifier with public key fetching based on KID

Dear Ophir,
I hope it’s ok I contact you like this. The issue management for the cosette repository is disabled, so this is the best way I could think of.
Like you, I am working on verifying EUDCC/DGC signatures, and I am wondering if it is possible to use cosette to get the kid before calling the verify method, or if you know of a better way to verify & decode it given a set of keys (like the one you posted in the EUDCC github thread today).
Great job with posting the keys and the bot by the way. I think a lot of people will find that useful. I am still waiting for a reply from the Swedish authorities to see if they can provide another list for backup/double-verification purposes.
Piotr

by  @piotrblasiak
initially received by email

Hello,
I just enabled issues in cosette :)
You can pass an array of verifiers with a kid for each to the verify function: https://github.com/lovasoa/cosette/blob/master/lib/sign.ts#L116-L151
I understand that this is not optimal, and a PR adding a new verifier type (with an async callback that would let the user fetch the public key for a KID however they want) would be welcome.
And even better, if you are interested in verifying dgc in javascript, let's not duplicate work ! We have a full implementation in sanipasse

https://github.com/lovasoa/sanipasse/blob/master/src/lib/digital_green_certificate.ts
https://github.com/lovasoa/sanipasse/blob/master/src/lib/digital_green_certificate_types.ts

Would you like to work with us on extracting that to a library and publishing it to npm ?

That's great! Looks like you're a bit further ahead than me. I'd love to help. What can I do?

First, in cosette : make sign accept a callback as its verifier argument. The callback is async, takes a kid as argument and returns a verifier (with a public key that cosette can use).
Second, I'll create a new repository with the dgc verification code from sanipasse, and add you to it.

I'm actually not sure it's needed. At least for my use-case, first downloading all the verifiers and having them in-memory would be better for speed and I don't see that becoming a big problem with too many verifiers. Don't you agree? So on-demand fetching sounds a bit unnecessary to me. But perhaps I've missed something?

If we implement a callback , we will support BOTH use cases: ahead-of-time fetching, and just-in-time fetching of public keys. This will let users implement their trust store however they want. It may be in a simple js object, in indexedDB, or online. And all we have to do to support all these usecases is just to make the function take a callback.

If we implement a callback , we will support BOTH use cases: ahead-of-time fetching, and just-in-time fetching of public keys. This will let users implement their trust store however they want. It may be in a simple js object, in indexedDB, or online. And all we have to do to support all these usecases is just to make the function take a callback.

Alright, you're probably right that it can't hurt. I'm on it.

I see the tests don't pass as the test/Examples directory is empty. Is this on purpose? Also, the more I look at this the more I wonder if this shouldn't be something done with the cose-js library instead as it clearly duplicates work as you say...

It is not empty. Looks like you cloned the repository without subrepositories.
https://git-scm.com/book/en/v2/Git-Tools-Submodules
just clone with --recursive

Ok, sorry. But question still remains why not work together with the authors of the original cose-js. They apparently put in a lot of work already.

There is an open PR : https://github.com/erdtman/cose-js/pull/45
They have multiple open issues and PRs, I don't think they are interested...

Ok I just commented on that one to see what me fellow Swede has to say.


i18n: Make Message Translation plugable

This allows users to override the Message function in revel with their
own. It defaults to the existing Message function, so there should be no
compatibility issues.

The use case was replacing i18n with an auto-reloading one as well as setting locale through url path.

I see some potential improvements to i18n.go, like renaming messages to messageConfigs and making a messages map[string]map[string]string set to the parsed values.
For now, this PR is backwards compatible, so it looks great!
Thanks @klauspost!


Rename controls -> controller

Rename all controls to controller.
Introduce OrbitOrthoController that is a OrbitController with zoom_changes_distance=False.

LGTM.
Can you make sure to pull main in now that #239 is merged? :)


Improve zoom transitions from the +, - buttons

Improves https://github.com/CartoDB/support/issues/1362
CARTO.js PR: https://github.com/CartoDB/carto.js/pull/2178

In production :rocket:


Chat -  The keyboard disappears and appears again when the expanded composer is scrolled

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

Version Number: 9.0.10-2
Reproducible in staging?: Y
Reproducible in production?: Y
Found when validating PR : https://github.com/Expensify/App/pull/45664
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Open the app
Log in with any account
Navigate to FAB - Start chat
Open a conversation with any account
Insert more text into the composer than can be displayed
Expand the composer
Swipe down a few times inside the composer until you reach the top
Swipe up a few times inside the composer until you reach the bottom

Expected Result:
The keyboard shouldn't disappear.
Actual Result:
The keyboard disappears and appears again when the expanded composer is scrolled. Also repro when the composer isn't expended but it takes more effort to make it happen.
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
https://github.com/user-attachments/assets/b412b3de-74d6-4c2f-b179-e49fb31e3569

View all open jobs on GitHub

We think this issue might be related to the #vip-vsb

Proposal
Please re-state the problem that we are trying to solve in this issue.
The keyboard disappears when scrolling down the composer.
What is the root cause of that problem?
The composer is wrapped with a SwipableView which will close the keyboard if we swipe down further than the threshold.
https://github.com/Expensify/App/blob/637796d13d0bb6571a9ff198412f170ff609f7c3/src/pages/home/report/ReportFooter.tsx#L199-L200
https://github.com/Expensify/App/blob/637796d13d0bb6571a9ff198412f170ff609f7c3/src/components/SwipeableView/index.native.tsx#L7-L21
The current swipe-down distance threshold is 125.
What changes do you think we should make in order to solve the problem?

Increase the threshold to a bigger value when the composer is expanded (isComposerFullSize) or set it based on the container height and subtract by any number needed.
https://github.com/Expensify/App/blob/637796d13d0bb6571a9ff198412f170ff609f7c3/src/components/SwipeableView/index.native.tsx#L27
const containerHeightRef = useRef(0);
...
onLayout={e => containerHeightRef.current = e.nativeEvent.layout.height}


ReadableStream response terminates early...

Describe the bug
Please bear with me as this may well be to spec, but I find it very confusing. I am currently sending a Response that contains a readable stream in its body... it has inconsistent chunk sizes as its just html being streamed.
new Response(readableStream);

The following code is called on the response to pipe it into a node ServerResponse. According to the documentation for node, when .write() returns false it just means that the write could not be flushed all in one go, and some data was queued in user memory. The result of a false here cancels the readable stream as it breaks out of the loop.
https://github.com/ardatan/whatwg-node/blob/54a411446650275bb552dfc848bd7dda966d7d22/packages/server/src/utils.ts#L287-L295
To Reproduce
The following code will reproduce the issue, we should not see a log of a cancelled stream here and it should pull 5 times...
import { createServer } from 'node:http';
import { createServerAdapter } from '@whatwg-node/server';

const server = createServer(createServerAdapter((request) => {
  let i = 0, t = 5;
  const stream = new ReadableStream({
    pull(controller) {
      i++;
      console.log('pull ', i);
      if (i === t) {
        controller.close()
      } else {
        controller.enqueue('x'.repeat(20480));
      }
    },
    cancel(reason) {
      console.log('cancel ', reason);
    }
  });
  return new Response(stream, { status: 200 })
}));

server.listen(3001);

Expected behavior
I'm not sure I consider this a completed state, it should in theory wait for a drain before iterating again. It could be done like this...
for await (const chunk of asyncIterable) {
  if (
    !serverResponse
      // @ts-expect-error http and http2 writes are actually compatible
      .write(chunk)
  ) {
    await new Promise(resolve => serverResponse.once('drain', resolve));
  }
}

I'm happy to open a PR, but please let me know if I am doing something stupid here.
Environment:

OS: MacOS
@whatwg-node/server: latest
NodeJS: v20.9.0

We'd love to see a failing PR first :) Thanks for the issue

ok no problem, will tackle this shortly

@ardatan it appears the test harness does not encounter the same issue, which is very odd. the simple reproduction above does however, you can see an example of the issue running in codesandbox: https://codesandbox.io/p/devbox/frosty-bell-22cckf
whilst adding a test i noticed the following, which seems like a whoopsie:
https://github.com/ardatan/whatwg-node/blob/54a411446650275bb552dfc848bd7dda966d7d22/packages/server/test/node.spec.ts#L11
removing that only, and implementing a test against my change outlined above produces passing tests under the assumption that in the test harness, a readable stream is always cancelled, which doesn't seem to happen in real usage (see codesandbox).
i have opened a PR #1088, but again, it appears i could not get a failing test.

You are using Node's global ReadableStream which we don't recommend.
We recommend "@whatwg-node/fetch" for WHATWG API

You are using Node's global ReadableStream which we don't recommend. We recommend "@whatwg-node/fetch" for WHATWG API.

bit confused here, I noticed the only place where ReadableStream wasn't imported from @whatwg-node/fetch was the server/src/utils.ts file which was already using it from the global.

We ran into this same issue when running graphql-yoga 5.6.2 (with @whatwg-node/server 0.9.44), koa 2.13.4, in bun 1.1.20 - responses were being cut off short.
Setting up the koa, yoga integration like this:
appRouter.all('/graphql', ctx => yoga(ctx.req, ctx.res, ctx))
Making the change in the linked PR fixed the issue.


update dependencies

Description
Please summarise the changes.
Related issues
Please mention any github issues addressed by this PR.
Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented hard-to-understand parts of my code.
[ ] I have made corresponding changes to the public API documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the changelog with any user-facing changes.

I am not fully sure is the change to string is fully intentional, the old enum is still used in some parts?


CUDA unified memory fail to increase on demand in r1.10 on PPC64le

Description
Based on the commit to introduce an option to allocate CUDA unified memory, theoretically we could expect a memory swap between CPU and GPU while running datasets with high memory demands.
However, my tensorflow build still hits OOM.
I was training official resnet with cifar10 dataset, with also a large batch ---- 48*128.
I built another version without CUDA unified memory from commit fixed ppc64le compile failure libpng,
Both tensorflow build hits OOM when I try to increase batch size from 47*128 to 48*128.
Based on this comparision, I was convinced that CUDA unified memory is not functioning in my build.
However, I tried to set per_process_gpu_memory_fraction to 200 and pass the config to the tf.Session, it worked for much larger batches.
Then I realized that the UVM cannot grow on demand. Setting allow_growth to True won't help.
In a word, can we make the CUDA unified memory allocation grow on demand?
Could you possibly suggest a reason?
Did I miss out any configurations?
Thank you in advance!
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):  no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Linux Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):  source
TensorFlow version (use command below):  r1.10
Python version:  3.5.2
Bazel version (if compiling from source):  0.15.0
GCC/Compiler version (if compiling from source):  gcc (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
CUDA/cuDNN version:  9.2/7.1
GPU model and memory:   4 x Tesla P100, each has 16G memory; 1T RAM

@smit-hinsu
Thank you for the commit  introduce an option to allocate CUDA unified memory!
Could you possibly suggest a reason?
Thank you in advance!

You could try to switch to PoolAllocator if you suspect it's the problem of BFCAllocator.

As @zheng-xq have mentioned, TF has systematically switched to BFCAllocator since TF 1.10. You could checked out v1.9 and [here] (https://github.com/tensorflow/tensorflow/blob/r1.9/tensorflow/core/common_runtime/gpu/process_state.cc#L190) to see how to reenable PoolAllocator in TF with UVM.

Nagging Assignee @smit-hinsu: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @smit-hinsu: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @smit-hinsu: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

If I understand the experiment correctly, you are seeing that total memory usage does not go above per_process_gpu_memory_fraction with UVM. Is that correct? That seems to be working as intended and consistent with the mode without UVM.
could you describe your use-case requiring total memory to go above per_process_gpu_memory_fraction? wouldn't it be enough to set per_process_gpu_memory_fraction to a very high number and enable allow_growth option?

@smit-hinsu
Thank you for your reply.
True. Total memory usage does not go above per_process_gpu_memory_fraction with UVM.
In my experiments, it would be faster when per_process_gpu_memory_fraction is smaller.
Setting per_process_gpu_memory_fraction to a very high number would make training much much slower which is not applicable.
That means I have to find the best per_process_gpu_memory_fraction with many times of trying and failing.
Can you possibly make the total memory allocation(GPU+CPU) grow automatically when we need more memory?
In addition, could you possibly suggest:

Which memory(CPU or GPU memory) would be first used when we set per_process_gpu_memory_fraction  to a high number?

As I recognized, gpu memory would not be fully utilized when we set per_process_gpu_memory_fraction  to a high number

What is allow_growth doing?

Thank you in advance!

Did you try setting per_process_gpu_memory_fraction to a high number along with enabling allow_growth option?
It should make the total memory allocation(GPU+CPU) to grow automatically when more memory is required as you requested. See allow_growth documentation at https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/protobuf/config.proto#L36.
Memory is first allocated on CPU and migrated to GPU on demand. It is expected that training will become slower with unified memory as size of the working memory increases. It would generate many faults and stall the training process until memory is moved to GPU.
See cuda unified memory documentation for more details:
https://devblogs.nvidia.com/maximizing-unified-memory-performance-cuda/
http://on-demand.gputechconf.com/gtc/2017/presentation/s7285-nikolay-sakharnykh-unified-memory-on-pascal-and-volta.pdf
Hope this helps!

@smit-hinsu
Problem solved. Thank you very much!


Regulate top-level arrays

Starting with the initial implementation (and later with the second one), we had a special/hidden feature called 'top-level arrays':
$ http --offline --print=B pie.dev/post []:=1 []:=2 []:=3

[
    1,
    2,
    3
]

This is a powerful syntasx, since there weren't a way of creating/sending arrays in the past (without sending them as raw data). One thing that we skipped between two different implementations was to make this more stricter.
@ducaale previously started a discussion but we did not made a resolution back then due to worries over this would block the empty-key usage. Now that those are answered in #1286, I think we should be able to make the handling of top-level lists more seriously.
New handling

This patch forbids the usage of key-paths without a preceding key [foo]=bar (and variants of this)
If you need to embed such a structure, you can still continue to use :={"foo": "bar"}.
Mixing top-level list usage with other keys is now forbidden. E.g:

$ http --offline --print=B pie.dev/post a:=1 []:=2
{
    "": [
        2
    ],
    "a": 1
}

Codecov Report

Merging #1292 (91e5abd) into master (4d7d6b6) will decrease coverage by 0.77%.
The diff coverage is 95.03%.

:exclamation: Current head 91e5abd differs from pull request most recent head cdb7e66. Consider uploading reports for the commit cdb7e66 to get more accurate results

@@            Coverage Diff             @@
##           master    #1292      +/-   ##
==========================================
- Coverage   97.28%   96.50%   -0.78%
==========================================
  Files          67       85      +18
  Lines        4235     6009    +1774
==========================================
+ Hits         4120     5799    +1679
- Misses        115      210      +95

Impacted Files
Coverage Δ

tests/test_binary.py
100.00% <ø> (ø)

httpie/compat.py
31.11% <27.90%> (-68.89%)
:arrow_down:

tests/conftest.py
77.14% <58.33%> (-9.82%)
:arrow_down:

httpie/output/lexers/http.py
59.09% <59.09%> (ø)

tests/test_ssl.py
91.01% <66.66%> (-3.93%)
:arrow_down:

httpie/manager/__main__.py
82.35% <82.35%> (ø)

httpie/output/lexers/metadata.py
82.35% <82.35%> (ø)

httpie/models.py
94.23% <90.00%> (-3.14%)
:arrow_down:

tests/test_uploads.py
97.70% <92.59%> (-2.30%)
:arrow_down:

httpie/manager/core.py
92.85% <92.85%> (ø)

... and 71 more

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 d45f413...cdb7e66. Read the comment docs.

Thanks for all your done . You don’t need to many this my usb already
ดาวน์โหลด Outlook for iOShttps://aka.ms/o0ukef

จาก: Batuhan Taskaya @.>
ส่ง: Thursday, February 3, 2022 9:54:09 PM
ถึง: httpie/httpie @.>
สำเนาถึง: Subscribed @.***>
ชื่อเรื่อง: [httpie/httpie] Regulate top-level arrays (PR #1292)
Starting with the initial implementation (and later with the second one), we had a special/hidden feature called 'top-level arrays':
$ http --offline --print=B pie.dev/post []:=1 []:=2 []:=3
[
1,
2,
3
]
This is a powerful syntasx, since there weren't a way of creating/sending arrays in the past (without sending them as raw data). One thing that we skipped between two different implementations was to make this more stricter.
@ducaalehttps://github.com/ducaale previously started a discussionhttps://discord.com/channels/725351238698270761/801485021016752208/929057887685324821 but we did not made a resolution back then due to worries over this would block the empty-key usage. Now that those are answered in #1286https://github.com/httpie/httpie/issues/1286, I think we should be able to make the handling of top-level lists more seriously.
New handling

This patch forbids the usage of key-paths without a preceding key [foo]=bar (and variants of this)
If you need to embed such a structure, you can still continue to use :={"foo": "bar"}.
Mixing top-level list usage with other keys is now forbidden. E.g:

$ http --offline --print=B pie.dev/post a:=1 []:=2
{
"": [
2
],
"a": 1
}

You can view, comment on, or merge this pull request online at:
https://github.com/httpie/httpie/pull/1292
Commit Summary

91e5abdhttps://github.com/httpie/httpie/pull/1292/commits/91e5abd9bb5b808e09fed8ace055e7bab62df4e0 Redesign the starting path

File Changes
(5 fileshttps://github.com/httpie/httpie/pull/1292/files)

M docs/README.mdhttps://github.com/httpie/httpie/pull/1292/files#diff-0b5ca119d2be595aa307d34512d9679e49186307ef94201e4b3dfa079aa89938 (40)
M httpie/cli/constants.pyhttps://github.com/httpie/httpie/pull/1292/files#diff-7aec9bacddebffb59304ef2d44c00d0aac8a8aee4056e7dd810dbe8c63e8cbf0 (1)
M httpie/cli/nested_json.pyhttps://github.com/httpie/httpie/pull/1292/files#diff-f77e23da56b0779c85d0b4e1cc4365e92ec2646b724775175fe24151f3945d6e (75)
M httpie/client.pyhttps://github.com/httpie/httpie/pull/1292/files#diff-b3273e8417e9579741debf0a2ffbf781f1ed6bb9728ce412e2f8a19fd0285cb0 (3)
M tests/test_json.pyhttps://github.com/httpie/httpie/pull/1292/files#diff-5c84f15471db58e86c919d922881b8d8d31f4f6710063cc293bdbdd740d8aca0 (67)

Patch Links:

https://github.com/httpie/httpie/pull/1292.patch
https://github.com/httpie/httpie/pull/1292.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/httpie/httpie/pull/1292, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ART5UILXL3YLPCY6KSU3FVTUZKJJDANCNFSM5NPEXIPA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Try to make the test more resilient

Coverage remained the same at 84.596% when pulling c827377d7378fd38e7e119adb4e960aedffbb5ac on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.

Coverage remained the same at 84.596% when pulling 75c960e37538238f8ed7245103510483f29326fa on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.

Coverage remained the same at 84.596% when pulling 75c960e37538238f8ed7245103510483f29326fa on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.

Coverage remained the same at 84.596% when pulling 75c960e37538238f8ed7245103510483f29326fa on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.

Coverage remained the same at 84.596% when pulling 75c960e37538238f8ed7245103510483f29326fa on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.

Coverage remained the same at 84.596% when pulling 75c960e37538238f8ed7245103510483f29326fa on hotfix/test into 9817f481cfd4dfc1433d51ac6f2825753459f35a on master.


Access to this resource is denied

http://go.microsoft.com/fwlink/?linkid=35807

This link is found on this page: https://docs.microsoft.com/en-us/previous-versions/iis/6.0-sdk/ms525331(v=vs.90)


Badge Cannot Be Generated

I could be doing something wrong, but I followed the instructions in the README, installed the prerequisites, gems, and added the code to my test_helper.rb file. Here is my output after rake test:

Not exactly sure if this is an issue on Homebrew's ImageMagick's or your side, but I would love any help I can get to make it work. Thanks.

Looks like ImageMagick didn't start. Make sure you can run ImageMagick's 'convert' command first.

Yeah it looks like I can run the commands. Is there something in particular I need to run beforehand?

What OS are you on? Simplecov-badge is acting like convert is returning a non-zero exit code.

I'm currently running on OS X Yosemite 10.10.2. Could this be a problem with the OS since it was recently updated from 10.10.1?

The issue is the convert exits with a 1, not 0, when no parameters are passed to it.
output = convert returns #<Process::Status: pid 83651 exit 1>

Fix merged - thanks @jreinert!

Please update and push the gem.


DOCS-Add-skip-links

Links failing consistently.
Product Version(s):
Issue:
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

Fixed in another PR. Closing out.


Global shortcuts

What I want to do:
Have shortcuts from anywhere in windows to go to the next/previous video in a playlist.
How I currently acieved this:
Force Flash via Youtubecenter (y)
Sending {Home} and {end} keys via autohotkey to the GeckoFPSSandboxChildWindow1 (latest flash windowclass) on a global hotkey press
My question:
I would like to use HTML5 instead of flash. Is this possible somehow? (HTML5 doesn't use an own windowclass)

Huh? Why did you remove the request label?

@F43nd1r Most likely because the feature already exists? Your ticket is months old, so I suspect you are still using an older version and haven't updated.

I'm using the latest developer version, and the feature does not exist in it. You can use shortcuts on the page, but not globally.
And, if the feature would exist, that would be still no reason to remove the label. Instead, the issue should be closed.

Sorry for that, i was merging request: Feature to Feature Request and i've lost some of the issues.


refactor(linter): migrate eslint-plugin-jest(no-alias-method)

Current dependencies on/for this PR:

main

PR #1208

PR #1225

PR #1226   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 11, 10:15 PM: @Boshen started a stack merge that includes this pull request via Graphite.


[refactor/tls] TypeError when sending file attachment

Summary
when trying to DM a user with the send() method I get a type error
Reproduction Steps
-using refactor/tls branch
-try to DM .jpg to user with their user ID
Code
import discord

client = discord.Client()

@client.event
async def on_ready():
    user = await client.fetch_user(userID) #user ID as an int
    with open('cat.jpg', 'rb') as f:
        await user.send(file=discord.File(f))

client.run('token') #my token

Expected Results
send jpg to user
Actual Results
t.py", line 592, in _run_event
t.py", line 592, in _run_event
await coro(*args, **kwargs)
File "c:\Users\Desktop\discord pybot\main.py", line 9, in on_ready
await coro(*args, **kwargs)
File "c:\Users\Desktop\discord pybot\main.py", line 9, in on_ready
File "c:\Users\Desktop\discord pybot\main.py", line 9, in on_ready
await user.send(
File "C:\Users\Desktop\venvs\venv3.12\Lib\site-packages\discord\abc.py", line 1883, in send
data = await state.http.send_message(channel.id, params=params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Desktop\venvs\venv3.12\Lib\site-packages\discord\http.py", line 808, in request
response = await self.__session.request(method, url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Desktop\venvs\venv3.12\Lib\site-packages\curl_cffi\requests\session.py", line 899, in request
req, buffer, header_buffer, q, header_recved, quit_now = self._set_curl_options(
^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Desktop\venvs\venv3.12\Lib\site-packages\curl_cffi\requests\session.py", line 238, in _set_curl_options
raise TypeError("data must be dict, str, BytesIO or bytes")
TypeError: data must be dict, str, BytesIO or bytes
System Information

Python v3.12.2-final
discord.py-self v2.1.0-alpha

discord.py-self metadata: v2.1.0a4855+g72c6a593

curl_cffi v0.6.0b7
aiohttp v3.11.2
system info: Windows 10 10.0.19045

Checklist

[X] I have confirmed I am using unmodified discord.py-self and not the upstream discord.py.
[X] I have searched the open issues for duplicates.
[X] I have shared the entire traceback.
[X] I am using a user token (and it isn't visible in the code).

Additional Information
I'm not sure if this error has to do with this module or if its just a problem with how I'm implementing the code in general so sorry in advance if its the latter. I saw someone mention issues with curl_cffi after using the refactor/tls branch so I wanted to ask.

I want to add that when using get_user() for the user object rather than fetch_user() then the attachment works.

The refactor/tls branch is alpha and very unfinished. Regardless, thanks for the bug report because I didn't know about this and it needs to be fixed before the branch is merged into master.

Hey @hotapmfhypo, does this still occur using the latest version of the refactor/tls branch with the latest version of curl_cffi?

hey this is OP. sorry I got locked out of my other account. im still getting the same error even using the new branch when trying to send files.
File "c:\Users\user\Desktop\venvs\venv3.12\Lib\site-packages\discord\client.py", line 596, in _run_event
await coro(*args, **kwargs)
File "c:\Users\user\Desktop\discord pybot\discordbot.py", line 40, in on_ready
await c.send(file=discord.File('cat.jpg'))
File "c:\Users\user\Desktop\venvs\venv3.12\Lib\site-packages\discord\abc.py", line 1883, in send
data = await state.http.send_message(channel.id, params=params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Users\user\Desktop\venvs\venv3.12\Lib\site-packages\discord\http.py", line 817, in request
response = await self.__session.request(method, url, **kwargs, stream=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Users\user\Desktop\venvs\venv3.12\Lib\site-packages\curl_cffi\requests\session.py", line 899, in request
req, buffer, header_buffer, q, header_recved, quit_now = self._set_curl_options(
^^^^^^^^^^^^^^^^^^^^^^^
File "c:\Users\user\Desktop\venvs\venv3.12\Lib\site-packages\curl_cffi\requests\session.py", line 238, in _set_curl_options
raise TypeError("data must be dict, str, BytesIO or bytes")
TypeError: data must be dict, str, BytesIO or bytes


HIVE-26411 Fix TestReplicationMetricCollector flakiness

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Nice catch @ghanko


"Your IT Administrator has limited access to some areas of this app" pop up when opening windows defender after running script.

I went through all of the "disabled apps" in the readme and not a single word talking about removing windows defender. I'm on a personal computer and with only one user and it has admin permissions. How do I revert this??

Heya,
Win11Debloat doesn't touch anything related to Windows defender. And I cannot reproduce this on my machines.
What area of windows defender are affected/disabled?
Additionally, have you used any other scripts/programs that could affect windows defender?

Interesting situation, I believe it has nothing to do with the script. I did a fresh install of Windows 11, upon installation skipped Windows Login, and unchecked all tracking boxes. With this setup it immediately showed this error without even running the script.

(I'm not the creator of the original issue)
My advice would be to let Windows Update do its thing


Switch to using Cppcheck XML output instead of command line

Cppcheck supports an --xml version that would be much more reliable to parse than the current regex-ing of strings.

Will take a look at this.


New release

Last gem release was on 23 feb. After that thing has been added, but not released as gem update.
So mby it's time for 1.6.4?

Done :)


isStaticExport logic fails if the build command doesn't contain "next export"

This is borderlining between a bug and feature request :)
Describe the bug
We had the plugin start failing recently. What ended up happening is that the isStaticExport wasn't detected anymore.
const isStaticExport = usesBuildCommand({ build, scripts, command: "next export" })

To Reproduce
Steps to reproduce the behavior:

Add "build: next build" and "export: next export" to your package.json.
Specify this as your Netlify build command as "netlify:build": "npm run build && npm run export"
Run build and notice that the static export wasn't detected.

This is due to "next export" not found in the build command string.
Expected behavior
This could be a fragile way of detecting whether the plugin should run or not. Since there doesn't seem to be a way to opt out of the plugin install, I think it's worth reviewing the approach here.
Option 1: Provide more flexibility to detect the static build
Option 2: Provide a way to opt out of having the plugin to auto-install at all (I think many will prefer having this option in an env var or something)
Versions

Next.js: 11.0.1
plugin (if installed at fixed version): 3.6.3

Well found! That's a really good point: we need a more robust way of detecting which scripts are run. I'll look at that today. The addition of an env var to disable all plugin auto install is a really good idea too. I'll raise that with the team.

hi @ascorbic, looks like the issue is back for us in 4.0.0, breaking all our sites :)
We are using SSG mode and a custom npm run export script:
[build]
  command = 'npm run export'
  publish = 'out'

package.json:
 "export": "next build && next export",

The problem is that the next.js plugin is auto-installed and breaks the build with this:
4:35:37 PM: ────────────────────────────────────────────────────────────────
4:35:37 PM:   4. @netlify/plugin-nextjs (onBuild event)
4:35:37 PM: ────────────────────────────────────────────────────────────────
4:35:37 PM:
4:35:38 PM:
4:35:38 PM: ────────────────────────────────────────────────────────────────
4:35:38 PM:   Plugin "@netlify/plugin-nextjs" failed
4:35:38 PM: ────────────────────────────────────────────────────────────────
4:35:38 PM:
4:35:38 PM:   Error message
4:35:38 PM:   Error: The directory "out" does not contain a Next.js production build. Perhaps the build command was not run, or you specified the wrong publish directory.
4:35:38 PM:   Your publish directory is set to "out", but in most cases it should be ".next".
4:35:38 PM:   If you are using "next export" then the Essential Next.js plugin should be removed. See https://ntl.fyi/remove-plugin for details.

Is there a way to make sure that the plugin doesn't auto-install?

Good point. There isn't a way to disable auto-install, but I could add an env var to disable everything except caching. Would that work for you?

@ascorbic that would be amazing, thanks, Matt!
as a workaround, I had to pin the version of the plugin to v3, which is not a good long term solution :)


helm update doesn't update the pods of rc's or daemonset's

when we do a helm upgrade the deployment, rc and daemon set are updated and since deployment take care of the pods to be updated they are fine but rc and daemon set pods are not upgraded.

Does Kubernetes itself automatically re-deploy pods on update of RC/DS?

no..it doesn't...i think this more sort of an enhancement request than an issue.

This was implemented with the --restart-pods flag.

With a newer version of helm, use --recreate-pods flag to achieve the same result.


Set Enabled in StaticHelper to afect all instances

Background for this PR. Having a few experiments running without using the Static Helper, was trying to disable all experiments at once, by using the Enabled method. Turns out it wasn't possible.
To achieve this Had to create a implementation of Scientist and override the IsEnabledAsync.
This PR aims to allow the set of the Enabled func globally, for experiments using the helper and for the implementations.
The IsEnabledAsync remains virtual so that we can still override the enabled behaviour for a specific one

I am not sure how the changes accomplish the stated goal, could you maybe provide some code samples to show the difference in use between the current code, and the code you are proposing?

Sure, so right now we have two ways of starting an Experiment, either by using the Static helper like
Experiment<bool>(ExperimentName, experiment =>             {                 experiment.Use(() => true);                 experiment.Try(() => false);             });
or by  creating a new Scientist object like this
var scientist = new Scientist(resultPublisher);             scientist.Experiment<bool>("", experiment =>             {                 experiment.Use(() => true);                 experiment.Try(() => false);             });
Given this, if we have multiple experiments on both formats and we want to use the Enabled function to disable or enable all of the experiments the current implementation doesn't allow it. The current Enabled function only affects experiments created using the static helper.
My changes allow the Enabled to affect all of the esperiments regardless if they are being create using the static helper or the instance

One change that could be helpful in evaluating this would be to revert the naming change of _sharedScientist to SharedScientist
Do you think you could write a test that will only pass with this change?

Yeah sure, I'll write the test and update the PR.
Will revert the name change also

Thank you!
(also, you might to keep this in mind: https://github.com/scientistproject/Scientist.net/pull/108#issuecomment-390773865)

I do have a few more ideas to make it more IoC firendly, but I wanna do them in a different PR

@M-Zuber did you had time to review the latest changes?