[GoS] Consider providing information on a variety of interventions

It would be great if we could show what restrictions were active at what times in what regions of the united states.

Link to sources of when restrictions were announced
Mask-wearing guidelines
Maximum group size for gatherings
Types of businesses that must be closed
School in-person/remote/closed status
Rate of businesses with WFH status
Paid leave under the Coronavirus Act
Sports, arenas, event venue policies
Social distancing guidelines (dine in vs takeout vs outside seating only)

Data details
This is an open-ended data request -- no idea if there is a uniform data source available or if this would need to be scraped from regional websites.
This information would need to be encoded to fit within our API, or a new API would be necessary. Because this is not quantitative data, we'd need some mapping.

One possible source (with weird licensing terms): https://github.com/COVID19StatePolicy/SocialDistancing


Dark and Light Theme

Good evening,
so far I made my app when I had dark mode enabled by default.
Now I switched to light mode and everything except the modal switches properly.
Why is the modal black by default and how do I change it?
I assumed it was backdrop, but changing that has no effect.

@thehairy Can you share a screen cap of what you are experiencing?

@thehairy Can you share a screen cap of what you are experiencing?

https://imageing.eu/shared/9vh56mt.jpg
Even tho I have disabled darkmode and I do not change the colors or anything by myself.

Have you resolved the issue you are experiencing @thehairy? What did you use to setup theming?

Issue is present in 0.72.6 of react native. I have not confirmed latest version. I have a community dattime picker and am noticing that when the picker is used outside of a modal it is correctly themed. But a modal is using the system theme. By default expo apps will use the light theme, but the modals appear to be using system theme

So, how did you resolve the issue?


Master public key support?

Does this library support a master public key like electrum? This allows for a watch only wallet.

Sorry, not sure what you mean by a master public key.


Log Validator Indices and Active Validators

#1192  👈
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tholonious and the rest of your teammates on  Graphite


Android Support

This library does not seem to support android, will it be supported in near future?

Hi - yep, would be great to add Android support - haven't had a chance to look into it yet. Would gladly accept a Pull Request :)

I am just starting out with react native and mobile development at the moment, so don't know how I can be helpful in this project.

I'll need android support too, and will gladly help out but it'll be a couple months from now.

This library is nice. Looks like SimpleAuth doesn't support Android, but I found something that might be like it for Android. Is this the one?
https://github.com/3pillarlabs/socialauth-android

Yes, that looks like it shares many of the features for Android that SimpleAuth does for iOS

If we decide to use the social auth android plugin in this project then that makes the naming of this package not make sense. It might need to be changed to something more generic perhaps?
Otherwise, I was thinking that making a separate package would make more sense but someone  had already taken react-native-social-auth.

@rclai @adamjmcgrath are you guys giving it a go? I dont know Java AT ALL, so I can't help. But excited if you are indeed gonna implement it for android :)

Hi @dmbrowne
Not currently, but I think a friend of mine @jimenglish81, said he was going to take a look - so watch this space

Hi @adamjmcgrath , @jimenglish81 Thanks for this awesome library, It would be helpful if u provide android support.

Hi, this is still in the works, I expect we'll have an update soonish

+1 Would love to see this feature.

1

+1

+1

+1

+1 for android support

+1

+1 for android support

+1

Any alternate until this library support android?

+1

+1

+1

1

Update? :D

I've been looking at this recently, I'll try and share something in the next week or two

+1

+1

+1

Any news on Android support cheers!

I'm away on holiday at the moment and didn't get a chance to finish it before I left.
Have raised a pr #48 where you can follow the progress, I'll be picking it up again next week some time

Android support added in 2.0.0
Take a close look at the install instructions, the library no longer uses the native iOS library or Pods so should be easier to set up.
Raise another issue if you run into any problems

@adamjmcgrath Thanks for all of the effort you put into making this happen!


Some questions to reproduce this work

@Ray0089
Hi Chenrui,
　Thanks for sharing this so nice work. There are several  questions to reproduce your code.
1  I find you do not use the data synthetic in your training process form this published version in ycbv_pbr.py(real_syn_gen not be used). However, you have presented that "For both datasets, we use both real and synthetic data for training and testing as in He et al." in your Experiments of 4.1. Implementation details.
2 Your provided links of Data preparation of step 3 and Test the model of step 1 are same, maybe one of link is wrong.
3 Could you mind sharing your trained models in terms of YCB and LineMOD dataset to test the network?

Hi Chenrui,
Thank you for publishing this repository. I agree with @ZJU-PLP, if you could share pre trained models that would be awesome, in adittion, if would be easier if you shared your models using a different method rather than Baidu as european researchers as me have trouble with it.
Thanks in advance :)


Use WIF encoding for private keys in Go SDK

This PR depends on PR #670

Split the commit into more focused commits and added the dependency to vagrant.

We are already using https://github.com/btcsuite/btcd which has the same license.  Additionally, https://github.com/tendermint/go-crypto is using that library but is licensed with Apache 2.0 https://github.com/tendermint/go-crypto/blob/master/LICENSE. I think the license is okay based on that.

Used a private key generated from sawtooth keygen for all the tests.

@vaporos, @TomBarnes found that the ISC license is okay.


Time to mark as deprecated?

Given that there are stale issues, PR's, no updates, and it doesn't work without possibility for corruption on almost all modern filesystems (eg ext4), is it time to mark this project as deprecated?

It's stable. If you are using it within operating parameters then it works fine and will continue to work fine.

Thank you @JakeWharton!  Do you know if it should be used on F2FS devices?  I'm trying to figure out if F2FS supports "atomic segment writes", as I am not seeing much information on that concept on the web.

I personally do not. I've only worked on and maintained the higher-level APIs surrounding the low-level behavior on the file system. I was not involved in the research that went into guaranteeing the correct semantics were available. This library is something like 13 years old at this point.

@eburke - do you have any knowledge of any other file systems besides YAFFS/YAFFS2 that support "atomic segment writes"?  Does that concept have another or more encompassing name?  I'm not seeing much information on that concept on the web.
cc @jaegeuk - do you know if F2FS supports "atomic segment writes"?

Eric is retired. I can only hope he has disabled all notifications from GitHub and will never see this.

IIRC @crazybob would be better to ask.  Honestly I'm not sure any of us ever followed up on that, we just noticed it was likely not as valid under ext4 but it still functioned so we left it.


webcord: pass --enable-wayland-ime to electron under wayland session with NIXOS_OZONE_WL=1

Description of changes
Pass --enable-wayland-ime flag to electron for better virtual keyboard and input method support under wayland sessions when NIXOS_OZONE_WL=1.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I gave my thoughts here: https://github.com/NixOS/nixpkgs/pull/311937#issuecomment-2112756777

oops, totally missed that! Had the idea weeks ago before that draft was posted but only authored this commit today.
my main rationale for this is to be able to easily use --enable-wayland-ime, which is crucial for getting virtual keyboard support on electron apps, and makes it consistent with the way I do it with chrome, brave, and all the other electron apps I use. Without that override, the virtual keyboard is never summoned, making the app totally inaccessible for anyone who needs a touch keyboard.
In my opinion it's a far more flexible and consistent solution when you are doing small overrides like this for several applications, or want to easily configure it with options in your own modules.

I wonder if instead of introducing this argument which could be a bit of extra work in the future if we need to remove, we should just copy vesktop and always add the wayland ime flag...

I'm fine with adding the wayland-ime flag as long as it's gated behind some arg or envvar. Most likely NIXOS_OZONE_WL itself, same as the existing flags.

I'm fine with adding the wayland-ime flag as long as it's gated behind some arg or envvar. Most likely NIXOS_OZONE_WL itself, same as the existing flags.
That being said I don't really have a setup to test it, as I only use sway

I can update my PR after testing this. That should work for tablet and virtual keyboard use (tested on sway, hyprland, and plasma), and should also work for fctx users as well, per their wiki.

afaik --enable-wayland-ime only works with zwp_text_input_v1, while sway was specifically called out as an example here of a compositor that only supports v3, and chromium devs have explicitly said (due to some design decisions and usecases around ChromiumOS) that they intend to stick to v1 for the foreseeable future.
I don't know how up-to-date this other (unofficial) site (wayland.app) is, but you can see the support tables for zwp_input_method_v1 and zwp_text_input_manager_v3. If that's still the case, I don't see how this would work in sway.

afaik --enable-wayland-ime only works with zwp_text_input_v1, while sway was specifically called out as an example here of a compositor that only supports v3, and chromium devs have explicitly said (due to some design decisions and usecases around ChromiumOS) that they intend to stick to v1 for the foreseeable future.
I don't know how up-to-date this other (unofficial) site (wayland.app) is, but you can see the support tables for zwp_input_method_v1 and zwp_text_input_manager_v3. If that's still the case, I don't see how this would work in sway.
And fwiw, I've never gotten Fcitx5 to work in any Ozone Wayland app, ever (again, only tested on sway).

This works perfectly fine for me with squeekboard running in the background, it summons the keyboard as expected and I'm able to type text. It also works with kwin, and it's been part of my workflow on sway for a couple weeks now. That said, I haven't got it working with Qt apps on Sway (just GTK/Electron), but maliit does work with Qt/GTK/Electron apps on plasma.
PR has been updated to pass --enable-wayland-ime if NIXOS_OZONE_WL=1 is set.


Bluetooth: controller: Fix memq_dequeue function

When testing memq implementation used by controller, a
missing check on NULL pointer return could lead to NULL
pointer deferencing.
Current implementation of controller and mayfly do not
by design lead to NULL pointer dereferencing, this fix
is only for correct-ness and complete-ness.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

@cvinayak besides the minor issue I commented on, this patch looks otherwise good - will you be sending an updated version soon so that we could get it merged?


Add support for llvm-objdump to applocal.ps1

This fixes #11467 and together with #11466 seems to be everything needed to have clang support under windows for x64 builds.

tested file.exe
https://github.com/julian-r/file-windows/releases
https://github.com/brechtsanders/pedeps/releases

portable across different platforms (Windows, macOS, *nix)
no dependencies

small one file listpedeps

listpedeps.exe "file.exe" | ? { $_ -match "[^ ].dll" }
libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

 llvm-objdump -p "file.exe" | ? { $_ -match "^ {4}DLL Name: .*\.dll" } | % { $_ -replace "^ {4}DLL Name: ","" }
libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

dumpbin /DEPENDENTS "file.exe" | ? { $_ -match "^    [^ ].*\.dll" } | % { $_ -replace "^    ","" }
libmagic.dll
VCRUNTIME140.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
KERNEL32.dll

/azp run

/azp run

@ras0219-msft Is there anything I can do here? This obviously needs x64 windows clang, so testing this on the current CI is not feasible?

very interesting pr for people like me that use clang on windows

This obviously needs x64 windows clang

We currently install whichever version Visual Studio installs, which I think is an x86 version; is that acceptable?
https://github.com/microsoft/vcpkg/blob/5a97bb2f576f951959e26baa377afcd2777acb48/scripts/azure-pipelines/windows/provision-image.txt#L119-L120

@BillyONeal Thanks for taking time for this issue. I will try to have a look at end-to-end-tests on Monday.

We currently install whichever version Visual Studio installs, which I think is an x86 version; is that acceptable?

I see no reason why x86 wouldn't be fine. I honestly can't quite remember why I wrote x64 back then – probably just because that's the architecture we are using. But it's very good to know that there is a clang available on the CI machines.

I'm merging, since we have people who are waiting on this. @Chronial, could you look at the e2e tests and open a new PR?

@strega-nil thanks for merging. It got a bit busy this week – I'll see to the test when I find time.


Invalid value "/dev/xvdb" for unix device. Attachment point /dev/xvdb is already in use

I am getting this error which is weird because I do not think the device is in use:
rexray volume create --size 10 --volumename=test --volumetype=gp2
INFO[0000] [linux]
INFO[0000] [docker]
INFO[0000] [ec2]
INFO[0000] os driver initialized                         moduleName= provider=linux
INFO[0000] docker volume driver initialized              availabilityZone= iops= moduleName= provider=docker size=5 volumeRootPath=/data volumeType=gp2
INFO[0000] storage driver initialized                    accessKey= moduleName= provider=ec2 secretKey=
INFO[0000] sdm.CreateVolume                              IOPS=0 availabilityZone= driverName=ec2 moduleName= runAsync=false size=10 snapshotID= volumeID= volumeName=test volumeType=gp2
INFO[0000] waiting for volume creation to complete       driverName=ec2 moduleName= resp.VolumeId=0xc820551b08 runAsync=false snapshotID= volumeID=
name: test
volumeid: vol-ecad1947
availabilityzone: us-east-1b
status: available
volumetype: gp2
iops: 30
size: "10"
networkname: ""
attachments: []

docker run -it --volume-driver=rexray -v test:/test busybox sh
docker: Error response from daemon: VolumeDriver.Mount: {"Error":"InvalidParameterValue: Invalid value '/dev/xvdb' for unixDevice. Attachment point /dev/xvdb is already in use
	status code: 400, request id: 93b1312e-417f-4afc-94a2-2bda63efc679"}.

lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
xvda    202:0    0    8G  0 disk
|-xvda1 202:1    0  128M  0 part /boot
|-xvda2 202:2    0    2M  0 part
|-xvda3 202:3    0    1G  0 part /usr
|-xvda4 202:4    0    1G  0 part
|-xvda6 202:6    0  128M  0 part /usr/share/oem
|-xvda7 202:7    0   64M  0 part
`-xvda9 202:9    0  5.7G  0 part /
xvdf    202:80   0  200G  0 disk /var/lib/docker

Here is the rexray config
cat /etc/rexray/config.yml
rexray:
  logLevel: info
  storageDrivers:
  - ec2
  volumeDrivers:
  - docker
docker:
  size: 5
  volumeType: gp2
aws:
  rexrayTag: rexraydemo

uname -a && docker version && rexray version
Linux ip-10-1-10-233.ec2.internal 4.5.0-coreos-r1 #2 SMP Thu May 5 07:27:26 UTC 2016 x86_64 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz GenuineIntel GNU/Linux
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   8acee1b
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   8acee1b
 Built:
 OS/Arch:      linux/amd64
Binary: /opt/bin/rexray
SemVer: 0.3.3
OsArch: Linux-x86_64
Branch: v0.3.3
Commit: b30fb870b5b94cd8368824460ad020bfcf20be3a
Formed: Thu, 21 Apr 2016 19:41:36 UTC

@fenlix See https://github.com/emccode/rexray/issues/410
There is an outstanding issue with AWS where some AMI's maintain private hidden mounts that RR does not account for today.

@clintonskitson the workaround for now is to actually use the mount point, in this case is an m4.xlarge instance which has a ghost volume xvdb, by adding an ebs volume (even if it is not used, it can be a tiny volume) rexray is not broken anymore.

I'm using Terraform, and my workaround is to add into resource "aws_instance" ec2_istance block.
  ephemeral_block_device {     device_name = "/dev/xvdz"     virtual_name = "ephemeral0"   }
You don't need to attach any ebs volumes.
curl http://<IP_ADDRESS>/latest/meta-data/block-device-mapping/ephemeral0 xvdz


'WebElement' object is not iterable (Exception: Could not sign in to Mint.)

Describe the bug
get an error logging in
What version of MintAPI are you using?
2.5
What command[s] did you run / steps to reproduce?
mintapi -f today --headless --session-path "E:\Server Stuff\sessions" --accounts user pass
Stacktrace/error received:
DevTools listening on ws://<IP_ADDRESS>:62556/devtools/browser/0d89d199-a2ca-4105-8264-0e506192c629
[0714/094018.558:INFO:CONSOLE(1)] "analytics performance metrics [object Object]", source: https://mint.intuit.com/handlebars/common_3.0.1271/common/cms/js/csa-init.js (1)
[0714/094018.604:INFO:CONSOLE(1)] "analytics performance metrics [object Object]", source: https://mint.intuit.com/handlebars/common_3.0.1271/common/cms/js/csa-init.js (1)
[0714/094020.723:INFO:CONSOLE(69)] "before load rule ran", source: https://accounts.intuit.com/iux-tealium/utag/intuit/cg-accounts/prod/utag.js (69)
[0714/094020.841:INFO:CONSOLE(1)] "All core plugins started...", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/5400.js (1)
[0714/094020.841:INFO:CONSOLE(1)] "Plugins registered...", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/5400.js (1)
[0714/094020.857:INFO:CONSOLE(1)] "Application before-ready completed...", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/5400.js (1)
[0714/094020.857:INFO:CONSOLE(1)] "Application ready...", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/5400.js (1)
[0714/094020.857:INFO:CONSOLE(1)] "default delegate action handler  [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/342.js (1)
[0714/094020.878:INFO:CONSOLE(1)] "Shell - successfully initialized RUM module [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094020.894:INFO:CONSOLE(1)] "@ids-ts/theme is being deprecated. Please use @design-systems/theme instead.", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/624.js (1)
[0714/094020.894:INFO:CONSOLE(1)] "widget-request-start [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094020.909:INFO:CONSOLE(1)] "widget-load-start [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094020.928:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.932:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.938:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.941:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.951:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.952:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.954:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.961:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.964:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.965:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.970:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.975:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.977:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.982:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.988:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094020.992:INFO:CONSOLE(2)] "Unsatisfied version 3.5.2 of shared singleton module @design-systems/theme (required =3.5.1)", source: https://plugin.intuitcdn.net/identity-authn-core-ui/remoteEntry.4942e53a409866b36362.js (2)
[0714/094021.223:INFO:CONSOLE(1)] "widget-load-end [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094021.227:INFO:CONSOLE(1)] "widget-mount [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094021.229:INFO:CONSOLE(1)] "widget-first-display [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094021.236:INFO:CONSOLE(1)] "widget-ready [object Object]", source: https://plugin.intuitcdn.net/web-shell/3.258.2/adk/222.js (1)
[0714/094021.370:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
[0714/094021.650:INFO:CONSOLE(0)] "Autofocus processing was blocked because a document already has a focused element.", source: https://accounts.intuit.com/index.html?offering_id=Intuit.ifs.mint&namespace_id=50000026&redirect_url=https%3A%2F%2Fmint.intuit.com%2Foverview.event%3Futm_medium%3Ddirect%26cta%3Dnav_login_dropdown%26ivid%3D9db8b173-9856-4209-b57c-27445650d91b (0)
[0714/094021.863:INFO:CONSOLE(0)] "Access to XMLHttpRequest at 'chrome-extension://ghbmnnjooekpmoecnnnilnnbdlolhkhi/page_embed_script.js' from origin 'https://accounts.intuit.com' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-untrusted, https.", source: https://accounts.intuit.com/index.html?offering_id=Intuit.ifs.mint&namespace_id=50000026&redirect_url=https%3A%2F%2Fmint.intuit.com%2Foverview.event%3Futm_medium%3Ddirect%26cta%3Dnav_login_dropdown%26ivid%3D9db8b173-9856-4209-b57c-27445650d91b (0)
[0714/094022.036:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
[0714/094031.436:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
[0714/094032.129:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
Please enter your 6-digit MFA code: [0714/094041.540:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
[0714/094042.207:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
599688
[0714/094051.625:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
[0714/094052.285:ERROR:stun_port.cc(80)] Binding error response: class=4 number=1 reason=Unauthorized
'WebElement' object is not iterable
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 358, in sign_in
handle_same_page_username_password(driver, email, password)
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 437, in handle_same_page_username_password
email_input = driver.find_element(By.ID, "ius-userid")
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 857, in find_element
return self.execute(Command.FIND_ELEMENT, {
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 435, in execute
self.error_handler.check_response(response)
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
(Session info: headless chrome=103.0.5060.114)
Stacktrace:
Backtrace:
Ordinal0 [0x00286463+2188387]
Ordinal0 [0x0021E461+1762401]
Ordinal0 [0x00133D78+802168]
Ordinal0 [0x00161880+989312]
Ordinal0 [0x00161B1B+989979]
Ordinal0 [0x0018E912+1173778]
Ordinal0 [0x0017C824+1099812]
Ordinal0 [0x0018CC22+1166370]
Ordinal0 [0x0017C5F6+1099254]
Ordinal0 [0x00156BE0+945120]
Ordinal0 [0x00157AD6+948950]
GetHandleVerifier [0x005271F2+2712546]
GetHandleVerifier [0x0051886D+2652765]
GetHandleVerifier [0x0031002A+520730]
GetHandleVerifier [0x0030EE06+516086]
Ordinal0 [0x0022468B+1787531]
Ordinal0 [0x00228E88+1805960]
Ordinal0 [0x00228F75+1806197]
Ordinal0 [0x00231DF1+1842673]
BaseThreadInitThunk [0x774DFA29+25]
RtlGetAppContainerNamedObjectPath [0x77DC7A9E+286]
RtlGetAppContainerNamedObjectPath [0x77DC7A6E+238]
(No symbol) [0x00000000]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 456, in handle_different_page_username_password
raise ElementNotVisibleException()
selenium.common.exceptions.ElementNotVisibleException: Message: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\api.py", line 169, in login_and_get_token
self.status_message = sign_in(
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 365, in sign_in
handle_different_page_username_password(driver, email)
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 467, in handle_different_page_username_password
for username_element in username_elements:
TypeError: 'WebElement' object is not iterable
[0714/094053.154:ERROR:turn_port.cc(866)] Port[98a300:0:1:0:relay:Net[any:0.0.0.x/0:Wildcard:id=0]]: Failed to send TURN message, error: 10053
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 358, in sign_in
handle_same_page_username_password(driver, email, password)
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 437, in handle_same_page_username_password
email_input = driver.find_element(By.ID, "ius-userid")
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 857, in find_element
return self.execute(Command.FIND_ELEMENT, {
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 435, in execute
self.error_handler.check_response(response)
File "C:\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
(Session info: headless chrome=103.0.5060.114)
Stacktrace:
Backtrace:
Ordinal0 [0x00286463+2188387]
Ordinal0 [0x0021E461+1762401]
Ordinal0 [0x00133D78+802168]
Ordinal0 [0x00161880+989312]
Ordinal0 [0x00161B1B+989979]
Ordinal0 [0x0018E912+1173778]
Ordinal0 [0x0017C824+1099812]
Ordinal0 [0x0018CC22+1166370]
Ordinal0 [0x0017C5F6+1099254]
Ordinal0 [0x00156BE0+945120]
Ordinal0 [0x00157AD6+948950]
GetHandleVerifier [0x005271F2+2712546]
GetHandleVerifier [0x0051886D+2652765]
GetHandleVerifier [0x0031002A+520730]
GetHandleVerifier [0x0030EE06+516086]
Ordinal0 [0x0022468B+1787531]
Ordinal0 [0x00228E88+1805960]
Ordinal0 [0x00228F75+1806197]
Ordinal0 [0x00231DF1+1842673]
BaseThreadInitThunk [0x774DFA29+25]
RtlGetAppContainerNamedObjectPath [0x77DC7A9E+286]
RtlGetAppContainerNamedObjectPath [0x77DC7A6E+238]
(No symbol) [0x00000000]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 456, in handle_different_page_username_password
raise ElementNotVisibleException()
selenium.common.exceptions.ElementNotVisibleException: Message: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python310\lib\site-packages\mintapi\api.py", line 169, in login_and_get_token
self.status_message = sign_in(
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 365, in sign_in
handle_different_page_username_password(driver, email)
File "C:\Python310\lib\site-packages\mintapi\signIn.py", line 467, in handle_different_page_username_password
for username_element in username_elements:
TypeError: 'WebElement' object is not iterable
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Python310\Scripts\mintapi-script.py", line 33, in
sys.exit(load_entry_point('mintapi==2.5', 'console_scripts', 'mintapi')())
File "C:\Python310\lib\site-packages\mintapi\cli.py", line 417, in main
mint = Mint(
File "C:\Python310\lib\site-packages\mintapi\api.py", line 96, in init
self.login_and_get_token(
File "C:\Python310\lib\site-packages\mintapi\api.py", line 191, in login_and_get_token
raise Exception(msg) from e
Exception: Could not sign in to Mint. Current page: https://accounts.intuit.com/index.html?offering_id=Intuit.ifs.mint&namespace_id=50000026&redirect_url=https%3A%2F%2Fmint.intuit.com%2Foverview.event%3Futm_medium%3Ddirect%26cta%3Dnav_login_dropdown%26ivid%3D9db8b173-9856-4209-b57c-27445650d91b

this was solved by one of the fixes recently added to main.
But on main, I am now getting the MFA loop timeout issue - I added a comment to that issue

spoke too soon...still getting this error

changed to using the bump-selenium-requests branch, same error.
more digging, turning off headless, the error occurs while chrome is on the "pick which account" page
(I have two...would love to get rid of one, but haven't figured out how yet - i don't need the second, I believe its from quicken which I haven't used in years since i found this api)

the radio button is correct (but i believe it is selected by default).  the error occurs I assume trying to click the button

I just started seeing this as well

@jprouty possibly related to https://github.com/jprouty/mint-amazon-tagger/issues/111?

@burkematthew the linked PR worked for me - fantastic, thanks VERY much

Seems to have resolved the issue for me as well -- thank you @burkematthew!


feat: list available profiles directly

Purpose
Simplify the process to use a custom profile - instead of requiring a local version.json, we can just list the existing files.
What the code is doing
Extracts the profile version from the filename, for files in the raw/{grid_model} folder. We currently assume this folder exists, and the files conform to the current naming convention.
Testing
Ran it locally, added a new profile, got expected result:
In [17]: ProfileHelper.get_profile_version_local("usa_tamu", "demand")
Out[17]: ['vJan2021', 'vFeb2021']

Time estimate
10 min

Any windows users want to do a quick test? @danielolsen? :)

Nice use of fs


[HOLD for payment 2024-10-24] Create workspace when new user signs up via OldDot and selects the "Manage my team's expenses" option

cc @carlosmiceli @anmurali
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:
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Anu
Slack conversation: https://expensify.slack.com/archives/C07HPDRELLD/p1728930765707219
Action Performed:

User signs up via OldDot and selects "Manage my team's expenses"
User is redirected to NewDot
App code redirects them to the step asking them how many employees they have

Expected Result:
When they select "Manage my team's expenses" on OldDot we should create a new workspace for them.
Actual Result:
We currently only create a workspace when they select "Manage my team's expenses" on NewDot.
SOLUTION
Let's investigate moving this to the CreateAccount call that happens on the OldDot side. Strategies where we are creating the workspace via NewDot when completing a specific onboarding step are bug prone because we may move these steps around or remove them in the future.
Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @sonialiap

@danieldoglas I'm working on clearing the deploy blocker here so will remove ya

Removing the blocker after patching the issue temporarily. We will still need to explore creating the policy in the CreateAccount flow.

No payment is required for this and the deploy blocker has been fixed. We should pursue the backend fix for this next.

@marcaaron since the deploy blocker was fixed do we want to keep this issue open for the BE fix or do we have/want a separate issue for the BE?

I think @marcaaron was saying in Slack to just leave this one open since it already has all the information we need.

Yes let's just use this issue please.

hmm I would not prioritize the checklist personally. This is more of a "new feature" that needs to be implemented.

Yeah, that's what I thought, but wanted to check before ignoring the checklist 👍

We will still need to explore creating the policy in the CreateAccount flow so leaving this open.

Am I correct in my understanding that we haven't started this yet?

Initially this issue was created to fix a deploy blocker (now, done). Then left open to address fixing this in the CreateAccount flow. @carlosmiceli any updates for us?

Not yet, couldn't make time last week, but as I mentioned to Anu I think I should be able to start this at some point halfway through this week.

Could we track both the permanent fix for Manage expenses for a small team and Control expenses for a larger organization together here? In both cases we need to create a workspace in CreateAccount flow, right?

Yes to the second question. I'm also fine with closing this and moving both to the new issue.

Ok, sounds good. In that case I will unassign you @carlosmiceli and clean up this issue.

Actually we can close this one since there was no C+ involved.


[SURE-6353]fix: Reconcile ACE

Issue:
https://github.com/rancher/rancher/issues/41832
SURE-6353
Problem
The issue is that enabling ACE on an RKE2 downstream cluster is not functioning as anticipated. While the kube-api-auth pod starts successfully and the kube-apiserver flags are set correctly, the controller within the kube-api-auth pod fails to start. As a result, the necessary Custom Resource Definitions (CRDs) are not created on the downstream cluster, leading to the absence of tokens.
Solution
The solution to the aforementioned problem was identified through troubleshooting. It was observed that there was a discrepancy between the appliedSpec and Spec fields:
spec:
  desiredAgentImage: rancher/rancher-agent:v2.7.3
  desiredAuthImage: rancher/kube-api-auth:v0.1.8
  localClusterAuthEndpoint:
    enabled: true
------------
status:
  appliedSpec:
    localClusterAuthEndpoint:
      enabled: false

Further investigation revealed that the ACE was not being reconciled upon updates. As a result, the status.appliedSpec.localClusterAuthEndpoint.enabled was not updated, preventing the controller from triggering the installation of the necessary CRDs on the downstream cluster. To address this issue, this PR introduces code to reconcile ACE, ensuring that the status.appliedSpec.localClusterAuthEndpoint.enabled is updated appropriately.
Testing

Engineering Testing
Manual Testing
Followed repro steps from JIRA issue SURE-6353
Automated Testing

Test types added/modified:

Unit
Integration (Go Framework)
Integration (v2prov Framework)
Validation (Go Framework)
Other - Explain: EXPLAIN
None
REMOVE NOT APPLICABLE BULLET POINTS ABOVE

If "None" - Reason: EXPLAIN THE REASON

If "None" - GH Issue/PR: LINK TO GH ISSUE/PR TO ADD TESTS

Summary: TODO
QA Testing Considerations

Regressions Considerations

TODO
Existing / newly added automated tests that provide evidence there are no regressions:

TODO

@bfbachmann After reviewing the code above, you may have noticed that the if condition has been removed. If I'm not wrong then this could cause clusterauthtoken.CRDSetup() to run even when ACE is not enabled.
If you refer to the JIRA ticket, the main issue was that the status.appliedSpec.localClusterAuthEndpoint.enabled field of the cluster object was not updated. As a result, the status of the existing cluster object remains the same as the updated cluster object, preventing the change from triggering here: link.
This heppened because the ACE was never reconciled for updated cluster object, so even if change ACE in spec field it was never refelcted in status.AppliedSpec field. So I added the reconcileACE for the imported cluster which is basically RKE2 clusters.

@pratikjagrut Thanks for doing this, I don't see any immediate issues, but I'm curious which test cases you've validated thus far? I think we want to ensure that imported and non-imported clusters with ACE enabled still work, for both RKE1 and RKE2.

@jakefhyde I manually checked issue 6353 with this fix.


Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2022-12-08T01:33:28+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.14
9d4600698403f6d685d0301ed290b806b94d5fb1
link
unknown
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster


Vim-inspired digraph support

Vim has very neat and easy to use feature called digraphs. In short, it allows to insert unicode symbol by pressing two keys in insert mode, after pressing , e.g. to insert ü user needs to press <c-k>u:. Key chords are pretty intuitive and easy to guess, they don't need to be memorized. It would be great to be able to do this on keyboard level. It's not impossible to achieve this functionality with current feature set of KMonad, but I believe it's not practical to define thousands of digraphs e.g. with layers.
Vim defines many of these, so KMonad would be probably best to have them built-in, and as well allowing defining new ones with
(defdigraph
  (u : ü)
)

I think what you're decriping is the current state of our compose key support, no?  We already have a lot of these for usage with a set compose key, e.g. cmps " u would give you ü.

Thank you, I misunderstood what compose is for. I read more on a subject, and indeed something similar can be achieved with compose.
For the posterity:
There is script to generate ~/.XCompose from digraphs here. Additionally, I mapped  in my vim layer into compose key, in my case it's pause to make it as close as possible to vim experience.
So, the issue can be closed, but I would like to ask one unrelated question, if you don't mind. It seems nobody files issue for this which is surprising, but if I am not mistaken, KMonad cannot record dynamic macros (i.e. not static macros that can be specified in .kbd config)? QMK has limited support for this, and vim has full-blown option to record key strokes into register with q<a-z>, where  is name of register (recording is stopped next time q pressed in normal mode), and replay it with @<a-z>.

On Fri, Jan 21 2022 11:45, fenuks wrote:

So, the issue can be closed, but I would like to ask one unrelated
question, if you don't mind. It seems nobody files issue for this
which is surprising, but if I am not mistaken, KMonad cannot record
dynamic macros (i.e. not static macros that can be specified in .kbd
config)?

Indeed, this is not something that we support right now...

QMK has limited support for this, and vim has full-blown option to
record key strokes into register with q<a-z>, where  is name of
register (recording is stopped next time q pressed in normal mode),
and replay it with @<a-z>.

...and this may be one of the reasons for it—I think most people just
use the keyboard macro facilities of their editor to do this

...and this may be one of the reasons for it—I think most people just
use the keyboard macro facilities of their editor to do this

I think the issue there is size of memory in keyboards might be main factor. QMK supports only two predefined registers. Editor macros are fantastic, and surely work better than keyboard-level macros, because they are well-integrated into editor, but on the other hand, 99.99% of apps don't have this feature, and people have to use external utilities, like AutoKey.
Thank you for your help, and since I was able to emulate digraph support, I'm closing the issue.


Order of events being added to the adobeDataLayer array.

Is seems that the ACDL script is adding events to the adobeDataLayer array only after the callbacks of the events have completed. This leads to an odd ordering of the event entries in the adobeDataLayer array.
Consider the following script:
<!doctype html>
<html>
    <head>
        <script src="https://unpkg.com/<EMAIL_ADDRESS>async defer></script>
        <script>
            window.adobeDataLayer = window.adobeDataLayer || [];

            window.adobeDataLayer.push(function (dl) {
                dl.addEventListener("one", function () {
                    logItemEvent("2: ", 0);
                    logItemEvent("2: ", 1);

                    dl.push({ event: "two" });

                    logItemEvent("3: ", 0);
                    logItemEvent("3: ", 1);
                });

                logItemEvent("1: ", 0);
                logItemEvent("1: ", 1);

                dl.push({ event: "one" });

                logItemEvent("4: ", 0);
                logItemEvent("4: ", 1);

                function logItemEvent(prependText, item) {
                    if (dl[item] && dl[item].event) {
                        return console.log(prependText+"adobeDataLayer["+item+"].event = "+dl[item].event);
                    }
                    return console.log(prependText+"adobeDataLayer["+item+"] = "+dl[item]);
                }
            });
        </script>
    </head>
    <body></body>
</html>

The resulting log output is:
1: adobeDataLayer[0] = undefined
1: adobeDataLayer[1] = undefined
2: adobeDataLayer[0] = undefined
2: adobeDataLayer[1] = undefined
3: adobeDataLayer[0].event = two
3: adobeDataLayer[1] = undefined
4: adobeDataLayer[0].event = two
4: adobeDataLayer[1].event = one

But the expected output would have been:
1: adobeDataLayer[0] = undefined
1: adobeDataLayer[1] = undefined
2: adobeDataLayer[0] = one
2: adobeDataLayer[1] = undefined
3: adobeDataLayer[0].event = one
3: adobeDataLayer[1] = two
3: adobeDataLayer[0].event = one
3: adobeDataLayer[1] = two

It would be expected that the ACDL appends the event object to the adobeDataLayer array prior to calling the callbacks that have been registered to that event, and not after. Because otherwise, notice how the events one and two end up in the reverse order.

@adobe

This is indeed the case because the pushed items are processed first before they are pushed to the underlying array.
While reading the code I also mentioned that the [delete filteredArguments[key]]
(https://github.com/adobe/adobe-client-data-layer/blob/master/src/dataLayerManager.js#L116) statements actually mutate the arguments array that is being iterated. This should be done differently to not cause any hard to trace side effects.
Ideally the procedure is reversed the following way:

Filter the given arguments (Array.filter) and push only data and event to the underlying array
Iterate over all the arguments again (no filter) and process the items

@adobe export issue to Jira project SITES as Bug

https://github.com/adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug

@adobe export issue to Jira project SITES as Bug


Location Address displayName typed incorrectly, should be display_name

Describe the bug
A clear and concise description of what the bug is.
@stripe > stripe-terminal-react-native > lib > typescript > src > types > index.d.ts > Location
Using the Node Stripe Terminal SDK, displayName is typed incorrectly than what is coming back from Stripe Node Api
stripe.terminal.locations.list
should be display_name
when this is incorrect, on DiscoverReadersScreen, it won't show the picked location name in the ListItem, and does not show the correct name when selecting a location on LocationsScreen
To reproduce, use the node stripe terminal api, set a location
const address = {
    "display_name": "Home", // this param needs to be display_name
    "address": {
        "line1": "123 street",
        "city": "Somewhere",
        "postal_code": "91210",
        "state": "CA",
        "country": "US"
    }
const location = await stripe.terminal.locations.create(address)

and then retrieving
const locations = await stripe.terminal.locations.list({
      limit: 3,
    });

it will show as display_name
I thought maybe if you post it as displayName the Stripe API would accept it, but it does if fact expect display_name
maybe its just the Node SDK?  I would think all the SDKs would be talking to the same backend, but please let me know if I am incorrect.
thanks!

Unfortunately Stripe's node SDK is typed differently than Stripe and Terminal React Native SDK. For now, we are planning on sticking to parity with Stripe React Native and keep the types camelCase


t is not a function

Node/i18next crashes sporadically (but regularly) when serving 404 pages through a default route.
The route is mounted behind my localized SEO routes in i18n.init's callback.
TypeError: /srv/www/mainsite-live/sites/not-found.jade:4
2| html(lang='en')
3|   include mixins/head
> 4|   +head(t('not-found:title'), 'not-found')
5|   body
6|     include ./partials/navigation
7|     .container
t is not a function
at eval (eval at <anonymous> (/srv/www/mainsite-live/node_modules/jade/lib/index.js:218:8), <anonymous>:62:21)
at eval (eval at <anonymous> (/srv/www/mainsite-live/node_modules/jade/lib/index.js:218:8), <anonymous>:499:22)
at res (/srv/www/mainsite-live/node_modules/jade/lib/index.js:219:38)
at Object.exports.renderFile (/srv/www/mainsite-live/node_modules/jade/lib/index.js:380:38)
at Object.exports.renderFile (/srv/www/mainsite-live/node_modules/jade/lib/index.js:370:21)
at View.exports.__express [as engine] (/srv/www/mainsite-live/node_modules/jade/lib/index.js:417:11)
at View.render (/srv/www/mainsite-live/node_modules/express/lib/view.js:126:8)
at tryRender (/srv/www/mainsite-live/node_modules/express/lib/application.js:639:10)
at EventEmitter.render (/srv/www/mainsite-live/node_modules/express/lib/application.js:591:3)
at ServerResponse.render (/srv/www/mainsite-live/node_modules/express/lib/response.js:961:7)
at /srv/www/mainsite-live/routes.js:64:11
at Layer.handle [as handle_request] (/srv/www/mainsite-live/node_modules/express/lib/router/layer.js:95:5)
at next (/srv/www/mainsite-live/node_modules/express/lib/router/route.js:131:13)
at Route.dispatch (/srv/www/mainsite-live/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/srv/www/mainsite-live/node_modules/express/lib/router/layer.js:95:5)
at /srv/www/mainsite-live/node_modules/express/lib/router/index.js:277:22

Any idea? I know the module is deprecated and I will migrate to version 2 soon, but I need this to work before that. The problem only became apparent when the site went live with a decent amount of requests.

if this issue comes unregular - sounds for me like a memory leak in express...or at least i not see how this could be related to i18next-node - only adds the t function to req.locals in the handle function....
sorry no idea....

Ok, thanks. That was helpful anyway. Seems like logging library (winston) was the culprit.

you found the cause?

more info?

Just looked into it again and I can now reproduce the problem.
As I've said it always occurs inside the middleware handling 404 responses:
app.use(function(req, res, next) {
      res.render('not-found', req.templateData);
});

This works for any non-existing route, but always produces the error when dealing with static content, <host>/css/<some-non-existent-file> for example.
I don't get that. At that point i18next has already been initialized.

did you append that before the i18next.handle?

No.
// ...
i18n.registerAppHelper(app);
app.use(i18n.handle);

require(__basedir + '/routes')(app, i18n);
//...

To be sure, I added the middleware at the end of i18n.init's callback.

so it's not the order...
app.use(i18n.handle) // --> adds t
app.use(function(req, res, next) { // --> t undefined here
      res.render('not-found', req.templateData);
});

really got no idea...best you run through debugger...or add some logs to the i18next.handle fc


HBASE-23254 Release replication buffer quota correctly, when batch includes bulk loaded hfiles

https://issues.apache.org/jira/browse/HBASE-23254

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
10m 51s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

:green_heart:
mvninstall
8m 42s
branch-1 passed

:green_heart:
compile
0m 45s
branch-1 passed with JDK v1.8.0_232

:green_heart:
compile
0m 54s
branch-1 passed with JDK v1.7.0_242

:green_heart:
checkstyle
1m 54s
branch-1 passed

:green_heart:
shadedjars
3m 35s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 40s
branch-1 passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 46s
branch-1 passed with JDK v1.7.0_242

:blue_heart:
spotbugs
3m  9s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
3m  5s
branch-1 passed

_ Patch Compile Tests _

:green_heart:
mvninstall
2m 21s
the patch passed

:green_heart:
compile
0m 47s
the patch passed with JDK v1.8.0_232

:green_heart:
javac
0m 47s
the patch passed

:green_heart:
compile
0m 48s
the patch passed with JDK v1.7.0_242

:green_heart:
javac
0m 48s
the patch passed

:green_heart:
checkstyle
1m 51s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
3m 23s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
5m 41s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

:green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_232

:green_heart:
javadoc
0m 39s
the patch passed with JDK v1.7.0_242

:green_heart:
findbugs
2m 51s
the patch passed

_ Other Tests _

:broken_heart:
unit
125m 17s
hbase-server in the patch failed.

:green_heart:
asflicense
0m 34s
The patch does not generate ASF License warnings.

179m 46s

Reason
Tests

Failed junit tests
hadoop.hbase.replication.TestReplicationKillSlaveRS

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/792

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux b96acf2ef010 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-792/out/precommit/personality/provided.sh

git revision
branch-1 / 3f9ce86

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/1/testReport/

Max. process+thread count
4145 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

I just wanted to add a missing line from the (branch-1) backport of HBASE-18116 to work as intended in HBASE-18116. I don't think a new UT for  branch-1 only.  Here is the region why original author didn't have  a UT. (https://issues.apache.org/jira/browse/HBASE-18116?focusedCommentId=16476668&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16476668)

I can't reproduce the failed test in my local repo. and It seems unrelated to this.

I just added to a test to clarify this issue. @wchevreuil please have a look when you have time.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
12m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
8m 36s
branch-1 passed

+1 :green_heart:
compile
0m 40s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
compile
0m 45s
branch-1 passed with JDK v1.7.0_242

+1 :green_heart:
checkstyle
1m 34s
branch-1 passed

+1 :green_heart:
shadedjars
2m 52s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
0m 42s
branch-1 passed with JDK v1.7.0_242

+0 :ok:
spotbugs
2m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 46s
branch-1 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 58s
the patch passed

+1 :green_heart:
compile
0m 41s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javac
0m 41s
the patch passed

+1 :green_heart:
compile
0m 44s
the patch passed with JDK v1.7.0_242

+1 :green_heart:
javac
0m 44s
the patch passed

+1 :green_heart:
checkstyle
1m 29s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
2m 46s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
5m  5s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
0m 41s
the patch passed with JDK v1.7.0_242

+1 :green_heart:
findbugs
2m 55s
the patch passed

_ Other Tests _

-1 :x:
unit
161m 35s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 35s
The patch does not generate ASF License warnings.

213m 35s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.mapreduce.TestLoadIncrementalHFilesUseSecurityEndPoint

hadoop.hbase.client.TestSnapshotTemporaryDirectory

hadoop.hbase.regionserver.TestCompactionState

hadoop.hbase.client.TestAdmin2

hadoop.hbase.mapreduce.TestLoadIncrementalHFiles

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/792

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 72f9cb6dba0b 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-792/out/precommit/personality/provided.sh

git revision
branch-1 / 248d80b

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/2/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/2/testReport/

Max. process+thread count
4227 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-792/2/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

The following exception were thrown in all failed tests.
These failures has happened since #1010 (JUnit upgrade)
I confirmed all tests passed Without JUnit upgrade.
I'm not sure but it seems to be related to this change https://github.com/junit-team/junit4/pull/1517
ping~ @ndimiduk
java.lang.RuntimeException: java.lang.IllegalThreadStateException

	at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:239)
	at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:273)
	at org.apache.hadoop.hbase.client.ClientScanner.loadCache(ClientScanner.java:434)
	at org.apache.hadoop.hbase.client.ClientScanner.next(ClientScanner.java:308)
	at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:639)
	at org.apache.hadoop.hbase.MetaTableAccessor.getTableRegionsAndLocations(MetaTableAccessor.java:558)
	at org.apache.hadoop.hbase.MetaTableAccessor.getTableRegions(MetaTableAccessor.java:414)
	at org.apache.hadoop.hbase.MetaTableAccessor.getTableRegions(MetaTableAccessor.java:397)
	at org.apache.hadoop.hbase.client.HBaseAdmin.getTableRegions(HBaseAdmin.java:3317)
	at org.apache.hadoop.hbase.client.TestAdmin2.testEnableTableAfterprocessedServersCleaned(TestAdmin2.java:816)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalThreadStateException
	at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867)
	at java.lang.Thread.init(Thread.java:405)
	at java.lang.Thread.init(Thread.java:349)
	at java.lang.Thread.<init>(Thread.java:599)
	at org.apache.hadoop.hbase.util.Threads$2.newThread(Threads.java:220)
	at org.apache.hadoop.hbase.util.Threads$3.newThread(Threads.java:246)
	at java.util.concurrent.ThreadPoolExecutor$Worker.<init>(ThreadPoolExecutor.java:619)
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:932)
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1367)
	at org.apache.hadoop.hbase.client.ResultBoundedCompletionService.submit(ResultBoundedCompletionService.java:171)
	at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.addCallsForCurrentReplica(ScannerCallableWithReplicas.java:330)
	at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:191)
	at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:58)
	at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:231)
	... 21 more

thanks @JeongDaeKim I'll take a look.

FYI #1031


Websocket to localhost?

When reviewing a build status I saw a shield icon in my address bar in Chrome.  It said that "This page is trying to load scripts from unauthenticated sources".  I looked in the javascript console and saw this:

Mixed Content: The page at 'https://readthedocs.org/builds/project/123/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://localhost:8088/websocket'. This request has been blocked; this endpoint must be available over WSS.

WebSocket on localhost???  I thought maybe the server was hacked or something but I then found it in the repo here: https://github.com/rtfd/readthedocs.org/blob/master/readthedocs/templates/builds/build_detail.html#L91  It's been in there for 3 years!  It looks like someone started working on implementing something and forgot about it.  Maybe this should be moved to a branch, tagged with a TODO comment, or stripped out.

Eeeks, yup, that's a whole bunch of test code that shouldn't be there. I'll just remove it.

Good catch, thanks for the report!


failed to receive data from characteristic indication

Hello, I am working on a blood pressure monitor. I followed the example at https://github.com/taks/esp32-nimble/blob/main/examples/ble_client.rs to write my code for it, but it doesn't work. The subscribe_indicate function is called, but the on_notify callback is never triggered.
esp32-nimble version: 0.8.0
My code looks like this:
....
            let mut client = BLEClient::new();
            client.on_connect(|client| {
              client.update_conn_params(120, 120, 0, 60).unwrap();
            });
            client.connect(&device.addr()).await;

            let service = client
              .get_service(uuid128!(self::YUELL_BLOOD_PRESSURE_MONITOR_SERVICE_UUID))
              .await.unwrap();

            let characteristic_uuid = uuid128!(self::YUELL_BLOOD_PRESSURE_MONITOR_CHARACTERISTIC_UUID);
            let characteristic = service.get_characteristic(characteristic_uuid).await.unwrap();
            if !characteristic.can_indicate() {
                log::error!("characteristic can't indicate: {}", characteristic);
                return;
              }

            characteristic
            .on_notify(|data| {
                log::info!("recevied data from characteristic");
                log::info!("received data from bpm：{}", core::str::from_utf8(data).unwrap());
            });

            characteristic.subscribe_indicate(true).await.expect("failed subscribe_indicate");

            log::info!("after subscribe_indicate {}", characteristic);

            time::sleep(time::Duration::from_secs(10000)).await;

.....
Here are the logs output:
I (4326) smart_health_kit::peripheral_client::yuwell_bpm: Yuwell BP-YE670A found, mac addr 44:28:A3:60:87:F8!
I (4326) smart_health_kit::peripheral_client::yuwell_bpm: after device found!
I (4336) NimBLE: GAP procedure initiated: connect;
I (4336) NimBLE: peer_addr_type=0 peer_addr=
I (4346) NimBLE: 44:28:a3:60:87:f8
I (4346) NimBLE:  scan_itvl=16 scan_window=16 itvl_min=24 itvl_max=40 latency=0 supervision_timeout=256 min_ce_len=0 max_ce_len=0 own_addr_type=0
I (4356) NimBLE:
I (4936) NimBLE: GATT procedure initiated: exchange mtu
I (5006) esp32_nimble::client::ble_client: mtu update event; conn_handle=0 mtu=247
I (5006) NimBLE: GAP procedure initiated:
I (5006) NimBLE: connection parameter update; conn_handle=0 itvl_min=120 itvl_max=120 latency=0 supervision_timeout=60 min_ce_len=0 max_ce_len=0
I (5016) NimBLE:
I (5026) NimBLE: GATT procedure initiated: discover all services
I (5256) NimBLE: GATT procedure initiated: discover all characteristics;
I (5256) NimBLE: start_handle=49 end_handle=67
I (5806) NimBLE: GATT procedure initiated: discover all characteristics;
I (5806) NimBLE: start_handle=51 end_handle=67
I (6106) NimBLE: GATT procedure initiated: discover all descriptors;
I (6106) NimBLE: chr_val_handle=51 end_handle=53
I (6406) NimBLE: GATT procedure initiated: write;
I (6406) NimBLE: att_handle=52 len=2
I (6706) smart_health_kit::peripheral_client::yuwell_bpm: after subscribe_indicate BLERemoteCharacteristic[0x2a35]
I tried to output a debug log on ble_client.rs as followed, but no log was output at all:
extern "C" fn handle_gap_event(event: *mut esp_idf_sys::ble_gap_event, arg: *mut c_void) -> i32 {
....
BLE_GAP_EVENT_NOTIFY_RX => {
    let notify_rx = unsafe { &event.__bindgen_anon_1.notify_rx };

    ::log::info!(
      "notify_rx={:#?}",
      notify_rx
    );

===================
by the way, the blood pressure monitor works on micropython program using below code:
async def connection_and_monitor_task(self):
    while True:
        if self.device and (not self.connection or not self.connection.is_connected()):
            try:
                print("YuWellBpMonitorService:Connecting to", self.device)
                self.connection = await self.device.connect()
                beepUtil.ok_notice()
                async with self.connection:
                    try:
                        bp_service = await self.connection.service(self._ENV_BLOOD_PRESSURE_UUID)
                        bp_characteristic = await bp_service.characteristic(self._ENV_BLOOD_PRESSURE_VALUE_UUID)

                        await bp_characteristic.subscribe(notify=False, indicate=True)

                        print("YuWellBpMonitorService:connection done")

                        while self.connection and self.connection.is_connected():
                            try:
                                print("YuWellBpMonitorService:waiting for indication")
                                data = await bp_characteristic.indicated()
                                parsed_data = self._decode_data(data)
                                timestamp = trueTime()
                                print("timestamp:%s"%timestamp)
                                uuid = "%s|%d" % (self.deviceId, timestamp)
                                .....

I am a newbie on ESP32 with Rust. Any help is appreciated, thanks.

I tried to downgrade to version 0.7 with following code, and it works.
let mut client = BLEClient::new();
client.on_connect(|client| {
//client.update_conn_params(120, 120, 0, 60).unwrap();
log::info!("connected to ble server...")
});
client.connect(&device.addr()).await;
        let service = client
          .get_service(uuid128!(self::YUELL_BLOOD_PRESSURE_MONITOR_SERVICE_UUID))
          .await.unwrap();

        let characteristic_uuid = uuid128!(self::YUELL_BLOOD_PRESSURE_MONITOR_CHARACTERISTIC_UUID);
        let characteristic = service.get_characteristic(characteristic_uuid).await.unwrap();
        if !characteristic.can_indicate() {
            log::error!("characteristic can't indicate: {}", characteristic);
            return;
          }

        characteristic
        .on_notify(|data| {
            log::info!("recevied data from characteristic,{:?}",data);
            //log::info!("received data from bpm：{}", core::str::from_utf8(data).unwrap());
        });

        characteristic.subscribe_indicate(true).await.expect("failed subscribe_indicate");

        log::info!("subscribe_indicate called {}", characteristic);

=================================
logs output:
I (3839) smart_health_kit::peripheral_client::yuwell_bpm: connected to ble server...
I (3849) NimBLE: GATT procedure initiated: discover all services
I (4039) NimBLE: GATT procedure initiated: discover all characteristics;
I (4039) NimBLE: start_handle=49 end_handle=67
I (4239) NimBLE: GATT procedure initiated: discover all characteristics;
I (4239) NimBLE: start_handle=51 end_handle=67
I (4339) NimBLE: GATT procedure initiated: discover all descriptors;
I (4339) NimBLE: chr_val_handle=51 end_handle=53
I (4439) NimBLE: GATT procedure initiated: write;
I (4439) NimBLE: att_handle=52 len=2
I (4539) smart_health_kit::peripheral_client::yuwell_bpm: subscribe_indicate called BLERemoteCharacteristic[0x2a35]
I (47589) smart_health_kit::peripheral_client::yuwell_bpm: recevied data from characteristic,[30, 119, 0, 84, 0, 95, 0, 229, 7, 12, 14, 7, 39, 27, 74, 0, 0, 2, 0]

Thanks @ricson-hoo.
I fixed this bug in the fix-multiple-drop branch.
Could you check this?

Instead of rewriting the files in the .cargo directory, please rewrite esp32-nimble = "0.8.0" to
esp32-nimble = { git = "https://github.com/taks/esp32-nimble.git", branch = "fix-multiple-drop" }

in your Cargo.toml.

Hi, taks, thanks.
This time, I removed /Users/ricson/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp32-nimble-0.8.0 and changed the Cargo.toml configuration from esp32-nimble = "0.8.0" to esp32-nimble = { git = "https://github.com/taks/esp32-nimble.git", branch = "fix-multiple-drop" }. However, after running it, the result remains the same.
I noticed that the code has now been pulled to: /Users/ricson/.cargo/git/checkouts/esp32-nimble-fc9d2c54a3bfa7fe/f3e6d96

It appears that the time::sleep code that was in the first attached code is missing
time::sleep(time::Duration::from_secs(10000)).await;

Oh yes, I moved it out of that code block. It seems this caused the characteristic to end its life immediately after subscribe_indicate.
I moved it back, and finally it works.
Now it logs:
I (3795) xite_iot_gateway::peripheral_client::yuwell_bpm: characteristic.subscribe_indicate called: BLERemoteCharacteristic[0x2a35]
I (40745) xite_iot_gateway::peripheral_client::yuwell_bpm: received data from characteristic, [30, 106, 0, 73, 0, 84, 0, 229, 7, 12, 15, 20, 24, 22, 65, 0, 0, 0, 0]
I (158945) esp32_nimble::client::ble_client: Disconnected: Err(Remote User Terminated Connection)
Thank you so much for your help!


🐛 Change LightningLoggerBase to Logger

What does this PR do?
Fix cannot import name 'LightningLoggerBase' from 'pytorch_lightning.loggers'. Since pytorch_lightning.loggers.base.LightningLoggerBase is deprecated over pytorch_lightning.loggers.base.Logger.
Fixes #972
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

If we want to maintain compatibility to older versions, then we could do something like this:
try:
    from pytorch_lightning.loggers import Logger
except ImportError:
    from pytorch_lightning.loggers import LightningLoggerBase
    Logger = LightningLoggerBase

@senarvi I did commit your idea to maintain older version compatibility

Any updates on this? Having to change LightningLoggerBase to Logger every time I re-install the package is kinda tedious.

Are we able to get this merged? I'm willing to help out any way possible. It seems like not being able to use lightning bolts with the latest pytorch lightning seems like a big deal


add tagger plugin

Codecov Report

Merging #10 (9c46c65) into master (a152ab3) will decrease coverage by 0.33%.
The diff coverage is 69.56%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   85.72%   85.39%   -0.34%
==========================================
  Files          50       52       +2
  Lines        1086     1109      +23
  Branches      120      123       +3
==========================================
+ Hits          931      947      +16
- Misses        146      153       +7
  Partials        9        9

Impacted Files
Coverage Δ

vedro/plugins/tagger/_tagger.py
65.00% <65.00%> (ø)

vedro/__init__.py
55.55% <100.00%> (+1.26%)
:arrow_up:

vedro/plugins/tagger/__init__.py
100.00% <100.00%> (ø)

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 a152ab3...9c46c65. Read the comment docs.


Add web Cryptocurrency and order alphabetically

First I order others webs in Cryptocurrency topic and then I add a new web

Add web for beginners to improve skills in solidity language


ICMPv6 Firewall Log Display - Fixes 5933

ICMPv6 logging was not being displayed in firewall log.

thanks @NOYB! I was hoping to get a chance to fix that today, been tied up on other things.


common: setting cgroup resources correctly

fix some cgroups related integration tests.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

/lgtm


style: fixed document references

ref: https://github.com/bbatsov/clojure-style-guide#document-references

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


Question: Generate Pocos

Hello
Do you have or can recommend a generator that can generate Classes based on tables / Views / Stored procedures in the MS Sql Database?
Thanks

Yes, I am in collaboration with @ErikEJ using his EF Power Tools. It is strongly recommended.
Our request has just been completed.

Yes, I am in collaboration with @ErikEJ using his EF Power Tools. It is strongly recommended.
Our request has just been completed.

I will try to create a wiki post  called something like: "Generating pure POCO classes"

I will try to create a wiki post  called something like: "Generating pure POCO classes"

Only remaining issue is to avoid Navigation properties.

Only remaining issue is to avoid Navigation properties.

Latest daily build of EF Core Power Tools includes the following:

Experimental support for nullable reference types, use "UseNullableReferences": true in efpt.config.json to enable #712
Experimental support for entity classes without constructor (so you can manage all constructors in a partial class), use "UseNoConstructor": true in efpt.config.json to enable #692
Experimental support for entity classes without navigations & constructor (for pure POCO classes for use with RepoDB, Dapper etc.), use "UseNoNavigations": true in efpt.config.json to enable #727

https://github.com/ErikEJ/EFCorePowerTools/wiki/Release-notes

Latest daily build of EF Core Power Tools includes the following:

Experimental support for nullable reference types, use "UseNullableReferences": true in efpt.config.json to enable #712
Experimental support for entity classes without constructor (so you can manage all constructors in a partial class), use "UseNoConstructor": true in efpt.config.json to enable #692
Experimental support for entity classes without navigations & constructor (for pure POCO classes for use with RepoDB, Dapper etc.), use "UseNoNavigations": true in efpt.config.json to enable #727

https://github.com/ErikEJ/EFCorePowerTools/wiki/Release-notes

I will try to create a wiki post called something like: "Generating pure POCO classes"
I downloaded v 2.5.454, used the reverse engineer, and received EF type of POCOS.
How can I create PURE POCOs as I am not using EF at all and just need the members?
Thanks

I will try to create a wiki post called something like: "Generating pure POCO classes"
I downloaded v 2.5.454, used the reverse engineer, and received EF type of POCOS.
How can I create PURE POCOs as I am not using EF at all and just need the members?
Thanks

@myalo You need the latest daily build, then follow the release notes in the link above.

@myalo You need the latest daily build, then follow the release notes in the link above.

Published a wiki post: https://github.com/ErikEJ/EFCorePowerTools/wiki/Generate-POCO-classes-for-use-with-micro-ORMs

Published a wiki post: https://github.com/ErikEJ/EFCorePowerTools/wiki/Generate-POCO-classes-for-use-with-micro-ORMs

Thanks a lot @ErikEJ for this support. I will share your tool to PHINUG as well.

Thanks a lot @ErikEJ for this support. I will share your tool to PHINUG as well.

Closing this one now.

Thanks
From: Michael Camara Pendon<EMAIL_ADDRESS>Sent: Saturday, February 6, 2021 12:53 PM
To: mikependon/RepoDB<EMAIL_ADDRESS>Cc: Moshe Yalovsky<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [mikependon/RepoDB] Question: Generate Pocos (#751)
Closing this one now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mikependon/RepoDB/issues/751#issuecomment-774541766, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAF4USDTBPLBXXPMZFPEBZLS5WTY5ANCNFSM4WPEY3YQ.


Linking fbpdf against mupdf may be a copyright violation

Disclaimer: IANAL, *GPL is horribly controversial and I might be wrong (but I don't think I am)
mupdf is licensed under AGPL terms. Per these terms, any program linking against it (either statically or dynamically), must also be released as AGPL. Releasing fbpdf under BSD is a violation of mupdf license. For this reason, Artifex could extort you or your users into buying a commercial mupdf license.
Now, I'm not sure how to fix it. The 'obvious' solution would be to license fbpdf separately as AGPL. However, I'm not sure if AGPL doesn't require covering other files in the package, particularly the Makefile. Since you have poppler-based fbpdf2, removing fbpdf or splitting it to a separate package may be a better option.

Disclaimer: IANAL, *GPL is horribly controversial and I might be
wrong (but I don't think I am)
mupdf is licensed under AGPL terms. Per these terms, any program
linking against it (either statically or dynamically), must also be
released as AGPL. Releasing fbpdf under BSD is a violation of mupdf
license. For this reason, Artifex could extort you or your users
into buying a commercial mupdf license.
Now, I'm not sure how to fix it. The 'obvious' solution would be to
license fbpdf separately as AGPL. However, I'm not sure if AGPL
doesn't require covering other files in the package, particularly the
Makefile. Since you have poppler-based fbpdf2, removing fbpdf or
splitting it to a separate package may be a better option.

That is sad.  Thanks for referring to this issue.
I am not an expert in legal issues.  Two questions:
Is there any problem with releasing the source code (not the
binary package) under ISC?  Note that Fbpdf is under ISC now.
Also, since Fbpdf uses ISC, can binary packages be released
under another license like AGPL?  If so, distributions can
use such licenses to resolve the issue.
Thanks,
Ali

Is there any problem with releasing the source code (not the binary package) under ISC? Note that Fbpdf is under ISC now.

To the best of my knowledge, yes. AGPL explicitly states that anything using it must be AGPL as well. There is some provision for using plain GPL but I'm not sure when or how it applies. Though I don't think AGPL vs GPL makes any real difference for you here.

Also, since Fbpdf uses ISC, can binary packages be released under another license like AGPL? If so, distributions can use such licenses to resolve the issue.

I'm not sure. Technically, I don't think there's a problem in distribution 'forking' this project to relicense it into AGPL. However, it's a bit unclear if you can really relicense something if you don't make any changes. From my experience, Gentoo licenses team has been reluctant to relicense stuff on our end, and instead preferred that licensing issues are resolved upstream.

Maybe a bit more explanation is in place. The idea behind GPL/AGPL is that GPL-ed software must never ever be used in proprietary software. That's why these licenses require that anything forking, incorporating or linking to GPL libraries must also use the same license.
Now, permissive licenses such as BSD/ISC have no similar restriction. It is entirely permitted to fork fbpdf and release its modified version as a proprietary program. This is where a conflict arises. You could basically say that your license is giving your users right that you're not permitted to give because of the underlying license.
As I've said, I'm not a lawyer. I'm not sure if somebody can sue you for doing this. However, there is a real danger that an user (or distro packager) will miss the problem and assume this package is actually entirely fine as ISC, and eventually someone will fall into the trap of not meeting AGPL requirements somewhere.
What's even more worrying is that Artifex is one of the companies that offer commercial licenses in parallel to AGPL. This means that they do have an interest in selling commercial licenses to people who happened to violate AGPL.

Michał<EMAIL_ADDRESS>wrote:

To the best of my knowledge, yes. AGPL explicitly states that
anything using it must be AGPL as well. There is some provision for
using plain GPL but I'm not sure when or how it applies. Though I
don't think AGPL vs GPL makes any real difference for you here.

As far as I can say, the executable that results from linking
is considered a derivative work and not the source code.  If,
for instance, another implementation of mupdf API was available
using a more permissive license, then linking with that library
would have been no problem.

Also, since Fbpdf uses ISC, can binary packages be released under another license like AGPL? If so, distributions can use such licenses to resolve the issue.

I'm not sure. Technically, I don't think there's a problem in
distribution 'forking' this project to relicense it into AGPL.
However, it's a bit unclear if you can really relicense something if
you don't make any changes. From my experience, Gentoo licenses team
has been reluctant to relicense stuff on our end, and instead
preferred that licensing issues are resolved upstream.

Maybe I can add a statement to mention that the code is
dual-licensed?
Ali

Michał<EMAIL_ADDRESS>wrote:

Maybe a bit more explanation is in place. The idea behind GPL/AGPL
is that GPL-ed software must never ever be used in proprietary
software. That's why these licenses require that anything forking,
incorporating or linking to GPL libraries must also use the same
license.
Now, permissive licenses such as BSD/ISC have no similar
restriction. It is entirely permitted to fork fbpdf and release its
modified version as a proprietary program. This is where a conflict
arises. You could basically say that your license is giving your users
right that you're not permitted to give because of the underlying
license.
As I've said, I'm not a lawyer. I'm not sure if somebody can sue you
for doing this. However, there is a real danger that an user (or
distro packager) will miss the problem and assume this package is
actually entirely fine as ISC, and eventually someone will fall into
the trap of not meeting AGPL requirements somewhere.

OK.  I shall add a statement to fbpdf.c.  I do not want to include
AGPL though.  Just a note that binary packages linking fbpdf with
mupdf can be released under AGPL.  Any suggestions?

What's even more worrying is that Artifex is one of the companies
that offer commercial licenses in parallel to AGPL. This means that
they do have an interest in selling commercial licenses to people who
happened to violate AGPL.

That is one reason I prefer not to use *GPL.
Furthermore, if the license of such a library changes or a new
implementation of its API is available with another license, then
ISC would not limit the license of the resulting binaries.
Thanks,
Ali

Well, your previous suggestion of dual-licensing makes sense to me. However, if you go that way, please make it explicitly clear that when linking to AGPL-licensed versions of mupdf (doubt any other will ever happen but sure) only AGPL is applicable.
Also, I'm pretty sure all GNU licenses require you to include the license with sources, and ask people to mail them if you don't. A common layout for this would to have two files, COPYING.ISC, COPYING.AGPL and an explanation in plain COPYING.


Bug: Validate not being passed on redux-form field.

This bug is also visible in the example app, edit a post title (which is required) and remove all text. The validation error will not appear and the post is saved.

Thanks!


Replace admin:admin default credentials

Is your feature request related to a problem? Please describe.
The default admin:admin credential is too weak and a sure-fire way to get hacked. Though the documentation recommends users to change the default passwords, it can be easily missed. Such weak defaults can be very easily exploited and lead to massive data leaks (remember Equifax attack?).
The second gap is, in the existing distribution, there's no default password policy to ensure stronger passwords. It needs to be configured explicitly by users. That is why such weak credentials are able to slip through the cracks.
Describe the solution you'd like
Remove the default passwords provided in internal_users.yml. Instead, have the admin user setup passwords for internal users once the OpenSearch process is up. These passwords can be set up post-installation using a REST API and admin certificates (for authentication). Setting password for admin user would look something like -
PATCH _opendistro/_security/api/internalusers/admin --key admin-key.pem --cert admin.pem --cacert root-ca.pem -d'
{
    "password": "quCn52_8\*N8"
}
'

To make this further easy, OpenSearch distribution could provide a tool such as an OpenSearch shell client to make it easy for admin user to configure all users. This shell client could also help with autogenerating strong passwords and can be further extended to support for more administrative functions in future.
In addition to this, we should also add a default password policy to only allow passwords that match a certain strength criteria. Obv, these policies are overridable depending on the user/enterprise needs. Having a strong default policy will protect against insecure password configurations.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This is related to https://github.com/opensearch-project/OpenSearch/issues/1618

Agreed -- the inability to change the admin password in particular without wiping the internal user database is a problem.

It seems like this is assuming use of the security plugin. It should be optional to use the security plugin.
I believe this should be mobed to the security plugin repo here - https://github.com/opensearch-project/security

@CEHENKLE I don't have permissions to transfer issues to the security plugin repo. Could you pls do that?

This is a super important security issue. Can you please prioritize it?
PS: it seems like there is something that could handle this - but it is 1. not documented and 2. I am not sure how and if it even works.
https://github.com/opensearch-project/OpenSearch/blob/0ba0e7cc26060f964fcbf6ee45bae53b3a9941d0/distribution/docker/src/docker/bin/docker-entrypoint.sh#L58


Encapsulate string/error-parsing logic from StanFileEditor.tsx

A lot of the logic for parsing error messages from stanc is currently located in the editor front-end component. I believe it would be more robust to put it in a separate file or closer to the stanc interface.

I can tackle this. It should be pretty easy for me to write some tests that generate some of the odder types of locations that can occur in a Stan program.


[Feature Request] General Build Instructions for Windows, Linux, Etc.

Is your feature request related to a problem? Please describe.
I'd like to build fvm for my environment using a simple set of instructions.
Describe the solution you'd like
Following the instructions produces a properly built binary of fvm for deployment on an endpoint.

In case this isn't clear; adding these steps, or links to them, to the ReadMe, would be a good idea

Is this information available anywhere right now?  Is this a standard Flutter/Dart practice?

@Greendogo I will create better instructions. For the GUI you just have to run normal flutter build commands.
For the CLI you can use https://dart.dev/tools/pub/cmd/pub-global#activating-a-package-on-your-local-machine to point to the local path after you clone and do a pub get


system hang when run cyphondock

HI
I am new in cyphon.
I set cyphondock up on my kvm virture server(debian 8 16G/6cpu).
The system has hang several times and i found nothing in syslog,kern.log.
I found blew error on my terminor on time.

than i setted the gc log on es and logstash.
I just wonder that is there anyone has same issue with me?
Thanks

We haven't seen any issues reported similar to this before. Are you running cyphondock or did you install cyphon to KVM domains?
If Docker, can you provide which version of Docker you are running?

Hi,fatalglitch
Thanks for your reply.
I run this on my kvm virture host which is installed debian.
By the way it was happened on physical machine first,  I thought it might due to machine too old and low performance,then i change it to a good one(performance is higher).
Docker version is -->
aaaa@jessie:~$ docker --version
Docker version 18.03.1-ce, build 9ee9f40
kernel version is -->
aaaa@jessie:~$ uname -a
Linux jessie 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
aaaa@jessie:~$ cat /etc/debian_version
8.5
Thanks

Hi
I found so many error on es docker.
org.elasticsearch.transport.RemoteTransportException: [hdHiWVZ][<IP_ADDRESS>:9300][indices:data/read/search[phase/query]]
Caused by: org.elasticsearch.index.query.QueryShardException: No mapping found for [sys_timestamp] in order to sort on
at org.elasticsearch.search.sort.FieldSortBuilder.build(FieldSortBuilder.java:262) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.search.sort.SortBuilder.buildSort(SortBuilder.java:156) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:634) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.search.SearchService.createContext(SearchService.java:485) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:461) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:257) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.action.search.SearchTransportService$6.messageReceived(SearchTransportService.java:343) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.action.search.SearchTransportService$6.messageReceived(SearchTransportService.java:340) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69) ~[elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:654) [elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.6.5.jar:5.6.5]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.6.5.jar:5.6.5]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_151]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
this error got so many times(almost over 6000 times).
Is this the problem?


[migration]clean up __from and __to in dashboard json_metadata

In dashboard Superset allows user save default values for filter slice, and saved in json_metadata. So that when the dashboard is loaded, it will be pre-populated with values for the filters. Superset also allows user set charts that immune from filters. For example:
{"filter_immune_slices": [], "timed_refresh_immune_slices": [], "filter_immune_slice_fields": {"255": ["__from", "__to"]}, "expanded_slices": {}, "default_filters": "{\"254\": {\"__from\": \"1 months ago\", \"dim_country\": [\"all\"]}}"}
after recently introduced time_range, __from and __to in json_metadata didn't correctly merge with time_range. It introduces extra __from/__to parameter into Filter control, and cause chart show no data. In airbnb we have about 500 dashboards set __from and __to in json_metadata.

Fix: I wrote this migration script to update __from/__to to __time_range for json_metadata.
@betodealmeida @mistercrunch @john-bodley @timifasubaa @michellethomas

Codecov Report

Merging #6378 into master will increase coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #6378     +/-   ##
=========================================
+ Coverage   77.24%   77.34%   +0.1%
=========================================
  Files          67       67
  Lines        9583     9583
=========================================
+ Hits         7402     7412     +10
+ Misses       2181     2171     -10

Impacted Files
Coverage Δ

superset/connectors/sqla/models.py
80.56% <0%> (+0.74%)
:arrow_up:

superset/db_engine_specs.py
55.03% <0%> (+0.87%)
:arrow_up:

Continue to review full report at Codecov.

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

code is updated per comment. also tested in dev environment...much faster!!