No response from pbpctrl

Hi,
No matter what I try it seems that when I perform any pbpctrl command e.g., pbpctrl show battery, any pbpctrl get [...] command, even when specifying -d 24:29:34:AC:9F:D1, the program just sits with no output until I CTRL+C it.
I tried both the AUR version of pbpctrl and I also tried building with Cargo as instructed. My Pixel Buds Pro are definitely connected via Bluetooth. I can listen to music and use the microphone. bluetoothctl starts with the earbuds connected. My issue occurs with the Experimental option both on and off in Bluez' config.
Is there any way to increase the verbosity of pbpctrl or is that not implemented (potential feature suggestion)?
Thanks for making this project, I appreciate it. Thanks for taking the time to read through these issues as well.
Here's the info from bluetoothctl:
Device 24:29:34:AC:9F:D1 (public)
	Name: Olivia's Pixel Buds Pro
	Alias: Olivia's Pixel Buds Pro
	Class: 0x00240404 (2360324)
	Icon: audio-headset
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (25e97ff7-24ce-4c4c-8951-f764a708f7b4)
	UUID: Vendor specific           (25e97ff7-24ce-4c4c-8951-f764a708f7b5)
	UUID: Vendor specific           (74c34f02-a774-4f6d-ae2e-dab5030b5842)
	UUID: Vendor specific           (81c2e72a-0591-443e-a1ff-05f988593351)
	UUID: Vendor specific           (df21fe2c-2515-4fdb-8886-f12c4d67927c)
	UUID: Vendor specific           (f8d1fbe4-7966-4334-8024-ff96c9330e15)
	Modalias: bluetooth:v00E0p3004d0001
	Battery Percentage: 0x4c (76)

Any chance you could check the firmware version? This change fixed a similar issue with v5.9 firmware, but might have broken it on older ones. Can you also post the log from when you run it with the RUST_LOG environment variable set to trace (e.g. env RUST_LOG=trace pbpctrl show battery)

I have no idea what happened -- last night I suspended my laptop (did not shut it off), this morning I woke up, opened the laptop back up, started trying to do the steps you recommended, only to find out that the pbpctrl commands work.
The only thing that I think really changed is the fact that as I went into the settings of the Pixel Buds Pro (to check firmware version) I had to go through a 'Your Pixel Buds just got better' screen, prompting me to try out the new voice detection music pause feature.
Firmware says release_5.9_signed. My hypothesis is that something about the 5.9 firmware update did not trigger until I visited that screen and now it's fine. I don't do any development in this area so I can only speculate. Just in case I'll send a report with trace turned on below. Feel free to close the issue, but I'm happy to help if you'd like any more info on my devices or setup for diagnosis.
oweston@Tanheku  ~  env RUST_LOG=trace pbpctrl show battery
2023-10-24T09:42:23.536665Z TRACE bluer::session: Connected to D-Bus with unique name :1.142
2023-10-24T09:42:23.537479Z TRACE bluer::session: Starting event loop for :1.142
2023-10-24T09:42:23.539607Z DEBUG pbpctrl: no device specified, searching for compatible one
2023-10-24T09:42:23.542011Z TRACE bluer::device: /org/bluez/hci0/dev_20_DF_B9_3D_26_A2: org.bluez.Device1.Class = 2884608
2023-10-24T09:42:23.542342Z TRACE bluer::device: /org/bluez/hci0/dev_CC_98_8B_1B_48_67: org.bluez.Device1.Class = 2360324
2023-10-24T09:42:23.542688Z TRACE bluer::device: /org/bluez/hci0/dev_CC_98_8B_1B_48_67: org.bluez.Device1.UUIDs = ["00000000-deca-fade-deca-deafdecacaff", "00001108-0000-1000-8000-00805f9b34fb", "0000110b-0000-1000-8000-00805f9b34fb", "0000110c-0000-1000-8000-00805f9b34fb", "0000110e-0000-1000-8000-00805f9b34fb", "0000111e-0000-1000-8000-00805f9b34fb", "00001200-0000-1000-8000-00805f9b34fb", "00001800-0000-1000-8000-00805f9b34fb", "00001801-0000-1000-8000-00805f9b34fb", "0000fe03-0000-1000-8000-00805f9b34fb", "5b833e05-6bc7-4802-8e9a-723ceca4bd8f", "5b833e06-6bc7-4802-8e9a-723ceca4bd8f", "69a7f243-e52f-4443-a7f9-cb4d053c74d6", "7b265b0e-2232-4d45-bef4-bb8ae62f813d", "81c2e72a-0591-443e-a1ff-05f988593351", "91c10d9c-aaef-42bd-b6d6-8a648c19213d", "931c7e8a-540f-4686-b798-e8df0a2ad9f7", "96cc203e-5068-46ad-b32d-e316f5e069ba", "b9b213ce-eeab-49e4-8fd9-aa478ed1b26b", "f8d1fbe4-7966-4334-8024-ff96c9330e15", "fe59bfa8-7fe3-4a05-9d94-99fadc69faff"]
2023-10-24T09:42:23.543053Z TRACE bluer::device: /org/bluez/hci0/dev_24_29_34_AC_9F_D1: org.bluez.Device1.Class = 2360324
2023-10-24T09:42:23.543406Z TRACE bluer::device: /org/bluez/hci0/dev_24_29_34_AC_9F_D1: org.bluez.Device1.UUIDs = ["0000110b-0000-1000-8000-00805f9b34fb", "0000110c-0000-1000-8000-00805f9b34fb", "0000110d-0000-1000-8000-00805f9b34fb", "0000110e-0000-1000-8000-00805f9b34fb", "0000111e-0000-1000-8000-00805f9b34fb", "00001124-0000-1000-8000-00805f9b34fb", "00001200-0000-1000-8000-00805f9b34fb", "25e97ff7-24ce-4c4c-8951-f764a708f7b4", "25e97ff7-24ce-4c4c-8951-f764a708f7b5", "74c34f02-a774-4f6d-ae2e-dab5030b5842", "81c2e72a-0591-443e-a1ff-05f988593351", "df21fe2c-2515-4fdb-8886-f12c4d67927c", "f8d1fbe4-7966-4334-8024-ff96c9330e15"]
2023-10-24T09:42:23.543457Z DEBUG pbpctrl::bt: found compatible device address=24:29:34:AC:9F:D1
2023-10-24T09:42:23.543471Z DEBUG pbpctrl::bt: registering maestro profile
2023-10-24T09:42:23.543540Z TRACE bluer::rfcomm::profile: Publishing profile at /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2
2023-10-24T09:42:23.543565Z TRACE bluer::rfcomm::profile: Registering profile at /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2
2023-10-24T09:42:23.544463Z DEBUG pbpctrl::bt: connecting to maestro profile
2023-10-24T09:42:23.544487Z TRACE bluer::device: /org/bluez/hci0/dev_24_29_34_AC_9F_D1: org.bluez.Device1.ConnectProfile ("25e97ff7-24ce-4c4c-8951-f764a708f7b5",)
2023-10-24T09:42:23.721944Z TRACE bluer: /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2: org.bluez.Profile1.NewConnection (Path("/org/bluez/hci0/dev_24_29_34_AC_9F_D1\0"), File { fd: 12, path: "socket:[109470]", read: true, write: true }, {"Version": Variant(258)})
2023-10-24T09:42:23.722000Z DEBUG pbpctrl::bt: received new profile connection request address=24:29:34:AC:9F:D1
2023-10-24T09:42:23.722009Z DEBUG pbpctrl::bt: accepting profile connection request address=24:29:34:AC:9F:D1
2023-10-24T09:42:23.722035Z TRACE bluer: /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2: org.bluez.Profile1.NewConnection (...) -> Ok(())
2023-10-24T09:42:23.722895Z TRACE bluer::device: /org/bluez/hci0/dev_24_29_34_AC_9F_D1: org.bluez.Device1.ConnectProfile (...) -> Ok(())
2023-10-24T09:42:23.722918Z DEBUG pbpctrl::bt: maestro profile connected address=24:29:34:AC:9F:D1
2023-10-24T09:42:23.722952Z TRACE maestro::protocol::utils: resolving channel
2023-10-24T09:42:23.722981Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x12, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.722990Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x13, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.722997Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x15, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.723003Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x17, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.723011Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x18, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.723017Z TRACE maestro::pwrpc::client: opening rpc: channel_id=0x1a, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.723034Z TRACE bluer::rfcomm::profile: Unregistering profile at /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2
2023-10-24T09:42:23.723947Z TRACE bluer::rfcomm::profile: Unpublishing profile at /org/bluez/bluer/profile/832bdd15fda944f39d882cefc13acfc2
2023-10-24T09:42:23.747717Z TRACE tokio_util::codec::framed_impl: attempting to decode a frame
2023-10-24T09:42:23.747755Z TRACE tokio_util::codec::framed_impl: frame decoded from buffer
2023-10-24T09:42:23.747765Z TRACE maestro::pwrpc::client: received packet: type=0x01, channel_id=0x15, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.747779Z TRACE maestro::pwrpc::client: completing rpc: channel_id=0x15, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff
2023-10-24T09:42:23.747795Z TRACE tokio_util::codec::framed_impl: attempting to decode a frame
2023-10-24T09:42:23.747827Z TRACE maestro::protocol::utils: channel resolved channel=21
2023-10-24T09:42:23.747859Z TRACE maestro::pwrpc::client: cancelling active rpc with code: channel_id=0x12, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, code=1
2023-10-24T09:42:23.747868Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x12, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, update=error, error=1
2023-10-24T09:42:23.747881Z TRACE maestro::pwrpc::client: cancelling active rpc with code: channel_id=0x13, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, code=1
2023-10-24T09:42:23.747890Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x13, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, update=error, error=1
2023-10-24T09:42:23.747901Z TRACE maestro::pwrpc::client: cancelling active rpc with code: channel_id=0x17, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, code=1
2023-10-24T09:42:23.747911Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x17, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, update=error, error=1
2023-10-24T09:42:23.747923Z TRACE maestro::pwrpc::client: cancelling active rpc with code: channel_id=0x18, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, code=1
2023-10-24T09:42:23.747932Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x18, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, update=error, error=1
2023-10-24T09:42:23.747943Z TRACE maestro::pwrpc::client: cancelling active rpc with code: channel_id=0x1a, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, code=1
2023-10-24T09:42:23.747953Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x1a, service_id=0x7ede71ea, method_id=0x7199fa44, call_id=0xffffffff, update=error, error=1
2023-10-24T09:42:23.747965Z TRACE maestro::pwrpc::client: starting rpc: channel_id=0x15, service_id=0x7ede71ea, method_id=0xe61e8290, call_id=0x00
2023-10-24T09:42:23.747979Z TRACE tokio_util::codec::framed_impl: flushing framed transport
2023-10-24T09:42:23.747987Z TRACE tokio_util::codec::framed_impl: writing; remaining=22
2023-10-24T09:42:23.748008Z TRACE tokio_util::codec::framed_impl: framed transport flushed
2023-10-24T09:42:23.771116Z TRACE tokio_util::codec::framed_impl: attempting to decode a frame
2023-10-24T09:42:23.771146Z TRACE tokio_util::codec::framed_impl: frame decoded from buffer
2023-10-24T09:42:23.771151Z TRACE maestro::pwrpc::client: received packet: type=0x07, channel_id=0x15, service_id=0x7ede71ea, method_id=0xe61e8290, call_id=0x00
2023-10-24T09:42:23.771159Z TRACE maestro::pwrpc::client: pushing server stream packet to caller: channel_id=0x15, service_id=0x7ede71ea, method_id=0xe61e8290, call_id=0x00
2023-10-24T09:42:23.771169Z TRACE tokio_util::codec::framed_impl: attempting to decode a frame
case:      95% (not charging)
left bud:  79% (charging)
right bud: 93% (not charging)
2023-10-24T09:42:23.771202Z TRACE pbpctrl: task terminated successfully
2023-10-24T09:42:23.771209Z TRACE maestro::pwrpc::client: terminating client
2023-10-24T09:42:23.771214Z TRACE maestro::pwrpc::client: cannot send call update, caller is gone: channel_id=0x15, service_id=0x7ede71ea, method_id=0xe61e8290, call_id=0x00, update=error, error=1
2023-10-24T09:42:23.771224Z TRACE maestro::pwrpc::client: sending client error packet: status=1, channel_id=0x15, service_id=0x7ede71ea, method_id=0xe61e8290, call_id=0x00
2023-10-24T09:42:23.771233Z TRACE tokio_util::codec::framed_impl: flushing framed transport
2023-10-24T09:42:23.771238Z TRACE tokio_util::codec::framed_impl: writing; remaining=26
2023-10-24T09:42:23.771277Z TRACE tokio_util::codec::framed_impl: framed transport flushed
2023-10-24T09:42:23.771286Z TRACE tokio_util::codec::framed_impl: flushing framed transport
2023-10-24T09:42:23.771292Z TRACE tokio_util::codec::framed_impl: framed transport flushed
2023-10-24T09:42:23.771311Z TRACE pbpctrl: client terminated successfully

Thanks! I guess it might not have been on the latest version before. Let me know if that happens again. I'll try to make the part that broke more robust.


Run a replica in each zone of us-central1

This is repeating some of the information in #78.  I think we should run at least one VM in each zone of us-central1, but my attempts failed. Leaving this as a reminder and anchor for the TODO comment.

From @BenWhitehead : https://cloud.google.com/compute/docs/instances/use-spread-placement-policies#rest_5


ignore errors reading dir

related: LookPath from https://go.dev/src/os/exec/lp_unix.go
https://github.com/terrastruct/d2/issues/991

no, we don't. big swaths of it are, but this one was slightly customized


chore: Create account-abstraction.mdx

Do you want to merge this into chain abstraction?
chain abstraction may be the narrative we're looking for, rather than people thinking we're just an account abstraction wallet

Do you mind if we merge this into chain abstraction?
chain abstraction may be the narrative we're looking for, rather than people thinking we're just an account abstraction wallet
Would love your thoughts

agreed very much so. Will make that update when i get the chance

Do you mind if we merge this into chain abstraction?
chain abstraction may be the narrative we're looking for, rather than people thinking we're just an account abstraction wallet
Would love your thoughts

agreed very much so. Will make that update when i get the chance

new PR: https://github.com/LightDotSo/LightDotSo/pull/1885

should i close?

closing in favor of https://github.com/LightDotSo/LightDotSo/pull/1885


RHEL 8.8 compatibility (container-selinux-2:2.205.0-2)

Hi,
The current and testing versions create errors with container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch
Tested versions:
k3s-selinux-1.2-2.el8.noarch.rpm
k3s-selinux-1.3-9.el8.noarch.rpm
Both show the same error
# dnf update
Last metadata expiration check: 0:26:52 ago on Wed 24 May 2023 09:00:09 AM UTC.
Dependencies resolved.
==============================================================================================================================================================================================================
 Package                                 Architecture                 Version                                                          Repository                                                        Size
==============================================================================================================================================================================================================
Upgrading:
 container-selinux                       noarch                       2:2.205.0-2.module+el8.8.0+18438+15d3aa65                        rhui-rhel-8-for-x86_64-appstream-rhui-rpms                        64 k

Transaction Summary
==============================================================================================================================================================================================================
Upgrade  1 Package

Total download size: 64 k
Is this ok [y/N]: y
Downloading Packages:
container-selinux-2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch.rpm                                                                                406 kB/s |  64 kB     00:00
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                402 kB/s |  64 kB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Running scriptlet: container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch                                                                                1/2
  Upgrading        : container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch                                                                                1/2
  Running scriptlet: container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch                                                                                1/2
Conflicting name type transition rules
Binary policy creation failed at /var/lib/selinux/targeted/tmp/modules/200/k3s/cil:135
Failed to generate binary
/usr/sbin/semodule:  Failed!

  Cleanup          : container-selinux-2:2.189.0-1.module+el8.7.0+17824+66a0202b.noarch                                                                                2/2
  Running scriptlet: container-selinux-2:2.189.0-1.module+el8.7.0+17824+66a0202b.noarch                                                                                2/2
  Running scriptlet: container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch                                                                                2/2
  Verifying        : container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch                                                                                1/2
  Verifying        : container-selinux-2:2.189.0-1.module+el8.7.0+17824+66a0202b.noarch                                                                                2/2
Installed products updated.

Upgraded:
  container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch

Complete!

Hello! Thank you for the report. This update in el8 happened while we were working on changes for the same update in el9 (and other distros). However, it has not yet been made across the board for el8 distros, so the approach we took in resolving this involved requiring a version less than container-selinux-2:2.191.0-1. I wrote some more details in https://github.com/k3s-io/k3s/issues/7307#issuecomment-1562078486, but this should be available now in the testing channel with the latest install script that was just merged.

Hi @rancher-max
I tested the latest k3s-selinux-1.3-9.el8.noarch.rpm as well. I'd guess you need to make it a stronger dependency (so that container-selinux does not get updated) or support the current rhel 8.8 version container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65

ah I see you also released a  k3s-selinux-1.3-10.el8.noarch.rpm -- I'll give it  a try next week

As feedback k3s-selinux-1.3-1.el8.noarch works with container-selinux-2:2.205.0-2.module+el8.8.0+18438+15d3aa65.noarch, but I had to delete k3s-selinux, upgrading it was not enough.

The install script should handle most of that, but yeah you're right -- there's a chicken:egg problem between k3s-selinux and container-selinux during an upgrade if you're just pulling binaries. This is the section of the install script that handles that problem: https://github.com/k3s-io/k3s/blob/master/install.sh#L618-L626.


Cache groups on dashboard is broken

Component: TP - dashboard
Version: 3.0.0-10156.528dd745.el7
Build Date: 2019-07-12 04:25:00OURCE
The list of cache group on dashboard is empty while there are 13 CGs
(image removed)

This seems specific to the environment. 2/3 of the environments I checked properly display the cachegroups dashboard. The 3rd environment is returning no cachegroups from the api/1.2/cdns/health endpoint, which I believe is the issue in that specific environment.


is python3.6 ok?

We did not check this version. If you have problems, we suggest you switch to python3.5.


Update en-US.json

Trying to improve some i18n, still need further work.

It's better for us to unify the plural form of the word vertex. Vertices is preferred.
For sentences, we need to add a period at the end of the sentence.

Thank you @abby-cyber , this pr was merged before your comments, allow me to move your comments into a new trackable place an issue: https://github.com/vesoft-inc/nebula-studio/issues/59


produce enable_services not actually enabling

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I tell produce to enable 'Data Protection complete'.  It says it successfully creates the appId, but when I check the dev center (and compile) it didn't actually enable Data Protection complete.

Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

Fastfile command (shortened)
   newId = "com.a.a" //removed sensitive info
   newName = "a" //removed sensitive info
   appFeatures = { "data-protection" => "complete" }
   produce(app_identifier: newId, app_name: newName, skip_itc: true, enabled_features: appFeatures)

[12:12:00]: ---------------------
[12:12:00]: --- Step: produce ---
[12:12:00]: ---------------------

+----------------------------------+---------------------------------------------------------------+
|                                    Summary for produce 2.9.0                                     |
+----------------------------------+---------------------------------------------------------------+
| app_identifier                   | com.a.a |
| app_name                         | a                  |
| skip_itc                         | true                                                          |
| enabled_features.data_protection | complete                                                      |
| username                         |<EMAIL_ADDRESS>                                  |
| sku                              | 14851*****                                                    |
| platform                         | ios                                                           |
| language                         | English                                                       |
| skip_devcenter                   | false                                                         |
| team_id                          | JLT78*****                                                    |
+----------------------------------+---------------------------------------------------------------+

[12:12:02]: Creating new app 'a' on the Apple Dev Center
[12:12:03]: Your app name includes non-ASCII characters, which are not supported by the Apple Developer Portal.
[12:12:03]: To fix this a unique (internal) name 'a' has been created for you. Your app's real name 'a'
[12:12:03]: will still show up correctly on iTunes Connect and the App Store.
[12:12:03]: Created app 3N7Z9*****
[12:12:03]: Finished creating new app 'a' on the Dev Center
[12:12:03]: ------------------

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.3.1

Bundler?
true

Git
git version 2.10.2

Installation Source
~/a/vendor/bundle/ruby/2.3.0/bin/fastlane

Host
Mac OS X 10.11.6 (15G1108)

Ruby Lib Dir
/opt/rubies/ruby-2.3.1/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode-8.1.app/Contents/Developer/

Xcode Version
8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.9.0
✅ Up-To-Date

Loaded fastlane plugins:
Loaded gems

Gem
Version

did_you_mean
1.0.2

bundler
1.13.6

io-console
0.4.6

CFPropertyList
2.3.4

i18n
0.7.0

json
1.8.6

minitest
5.10.1

thread_safe
0.3.5

tzinfo
1.2.2

activesupport
<IP_ADDRESS>

public_suffix
2.0.5

addressable
2.5.0

rubyzip
1.2.0

apktools
0.7.1

aws-sigv4
1.0.0

jmespath
1.3.1

aws-sdk-core
2.6.49

aws-sdk-resources
2.6.49

aws-sdk
2.6.49

babosa
1.0.2

claide
1.0.1

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.1.1

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.7.8

cocoapods-trunk
1.1.2

cocoapods-try
1.1.0

colored
1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.5.5

nanaimo
0.2.3

xcodeproj
1.4.2

cocoapods
1.1.1

highline
1.7.8

commander
4.4.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

dotenv
2.1.2

excon
0.54.0

multipart-post
2.0.0

faraday
0.11.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.11.0

fastimage
2.0.1

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

hurley
0.2

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.0.15

representable
2.3.0

retriable
2.1.0

google-api-client
0.9.20

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.2.0

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

word_wrap
1.0.0

rouge
1.11.1

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

proxies
0.2.1

s3
0.3.25

generated on: 2017-01-22

@MaximusMcCann thx for the report. infact this is a bug! (i did a PR to fix it - #7955, once merged it should be in one of the next releases )
but in addition to the bug, you have to supply the features using symbols.
e.g:
newId = "com.a.a" # removed sensitive info
newName = "a" # removed sensitive info
appFeatures = { :data_protection => "complete" }
produce(app_identifier: newId, app_name: newName, skip_itc: true, enabled_features: appFeatures)

cheers @hjanuschka 👍

Hi there.
This seems to be re-introduced in version 2.117.1.
If the app has already been created then produce says

[DevCenter] App 'au.com.commbank.acoe_mobile.test1' already exists, nothing to do on the Dev Center
And doesn't proceed with enabling/disabling services.

If, however, I run it from command line like
bundle exec fastlane produce enable_services -a APP_ID --access-wifi, then it works as expected and output is:

[DevCenter] App found 'ACOEMobileTest1'
Done! Enabled 1 services.

My bad, missed the fact that there is this action available: https://docs.fastlane.tools/actions/modify_services/


Need to handle iCloud account changes

If the user switches iCloud accounts their local data will no longer match the server's data.  In that case you would need initiate a complete two-way sync of all records stored both locally and on the server.  In iOS 9 there is a notification you can subscribe to so you know when the account change happens, but in iOS 8 I believe the only option is to record the user's iCloud ID and poll it for changes periodically (like at startup?).  Alternatively, providing a button to manually initiate a complete sync might be acceptable.

Yes you are right. But I think that can be left to user of this library to handle. Like at the end of the day it's a store added to your app's NSPersistentStoreCoordinator. In case of this you can remove the store and add a new one and start fresh ?

Ok I looked int the project and its actually fairly straight forward. I was just overwhelmed by the “CKSIncrementalStoreCloudStoreSetupOperation” and the “CKSIncrementalStoreSyncOperation” files but it seems the implementation itself is fairly straight forward. You use the two notifications to fetch your data again.
Can you explain when you use
NSNotificationCenter.defaultCenter().addObserver(self, selector: "syncFinished:", name: CKSIncrementalStoreDidStartSyncOperationNotification, object: self.cksIncrementalStore)
I’m guessing we can add this observer so that we can get notified when sync is being performed on one device to prohibit sync on our device for the time being? If so the selector name is misleading.
I’m still waiting for your go ahead to download the updated code.
Cheers
Ace

On Aug 3, 2015, at 4:02 AM, Nofel Mahmood<EMAIL_ADDRESS>wrote:
Yes you are right. But I think that can be left to user of this library to handle. Like at the end of the day it's a store added to your app's NSPersistentStoreCoordinator. In case of this you can remove the store and add a new one and start fresh ?
—
Reply to this email directly or view it on GitHub https://github.com/nofelmahmood/CKSIncrementalStore/issues/11#issuecomment-127155523.

I am actually decoupling the code. It will then be more easy to find bugs and fix them and it looks clean too.
The selector name was for the demo project. It's your choice, name it whatever you like. These two notifications are posted to notify the start and end of the sync operation.

Decoupling what from what?
How heavy is your code? And does it adapt to any core data store as long as we setup the correct Coordinator info?
Sent from my iPad

On Aug 3, 2015, at 10:47 AM, Nofel Mahmood<EMAIL_ADDRESS>wrote:
I am actually decoupling the code. It will then be more easy to find bugs and fix them and it looks clean too.
The selector name was for the demo project. It's your choice, name it whatever you like. These two notifications are posted to notify the start and end of the sync operation.
—
Reply to this email directly or view it on GitHub.

Don't worry man ! The decoupling of code would not have any impact on the user side. It's all to make code look clean, readable and of course testable.
You'l only have to add the store with CKSIncrementalStore type to your app's NSPersistentStoreCoordinator as usual to use it :)

I'm not worried, just curious.
So I see its swift 2.0 ready?
Sent from my iPad

On Aug 4, 2015, at 1:27 AM, Nofel Mahmood<EMAIL_ADDRESS>wrote:
Don't worry man ! The decoupling of code would not have any impact on the user side. It's all to make code look clean, readable and of course testable.
You'l only have to add the store with CKSIncrementalStore type to your app's NSPersistentStoreCoordinator as usual to use it :)
—
Reply to this email directly or view it on GitHub.

Did you try this with Apple Watch? I noticed that CloudKit is not available on WatchOS2

On Aug 4, 2015, at 10:18 AM, Ace Green<EMAIL_ADDRESS>wrote:
I'm not worried, just curious.
So I see its swift 2.0 ready?
Sent from my iPad
On Aug 4, 2015, at 1:27 AM, Nofel Mahmood<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Don't worry man ! The decoupling of code would not have any impact on the user side. It's all to make code look clean, readable and of course testable.
You'l only have to add the store with CKSIncrementalStore type to your app's NSPersistentStoreCoordinator as usual to use it :)
—
Reply to this email directly or view it on GitHub https://github.com/nofelmahmood/CKSIncrementalStore/issues/11#issuecomment-127482845.

Sorry I didn't because of my busy schedule :(
You can check out the master branch right now btw.

Yea I saw the branch but I’m wondering what to do with about the Apple Watch store. I’m surprised Apple made us use dedicated stores for Apple Watch with no iCloud access.

On Aug 5, 2015, at 10:03 AM, Nofel Mahmood<EMAIL_ADDRESS>wrote:
Sorry I didn't because of my busy schedule :(
You can check out the master branch right now btw.
—
Reply to this email directly or view it on GitHub https://github.com/nofelmahmood/CKSIncrementalStore/issues/11#issuecomment-128007522.

Are you sure 0.5.2 is swift ready?
I ran it and got 34 error messages and 39 warnings

On Aug 5, 2015, at 10:22 AM, Ace Green<EMAIL_ADDRESS>wrote:
Yea I saw the branch but I’m wondering what to do with about the Apple Watch store. I’m surprised Apple made us use dedicated stores for Apple Watch with no iCloud access.

On Aug 5, 2015, at 10:03 AM, Nofel Mahmood<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Sorry I didn't because of my busy schedule :(
You can check out the master branch right now btw.
—
Reply to this email directly or view it on GitHub https://github.com/nofelmahmood/CKSIncrementalStore/issues/11#issuecomment-128007522.


[Business Approvals Kit - BUG] Requestor detail is incorrect in the approval action

Describe the issue
The approval action always has Rafael Fowler as the Requestor instead of the actual requestor who requested which leads to wrong requestor being sent in the Approval Email.
Expected Behavior
The Approvals action should have correct requestor email.
What solution version are you using?
1.0.20231222.1
What app or flow are you having the issue with?
BACore | Runtime - Start Approval
Steps To Reproduce

Create an approval request using a user(Shrikant).
The approval email received at the Approver's end always contains requestor name as Rafael Fowler instead of the original requestor(Shrikant).

Anything else?
No response
AB#1922

Closing as the issue was fixed with the Jan-24 release


Wrong install link from OSF

binaries are fetched from a wrong URL, as shown below:
Trying URL: https://osf.io/u79sr/?pid=6zbyf/?action=download
Unexpected: link doesn't provide a filename

Trying URL: https://www.neuro.polymtl.ca/_media/downloads/sct/20191029_PAM50.zip
Downloading 20191029_pam50.zip...
Status: 70.8MB [00:13, 5.20MB/s]

details here: http://forum.spinalcordmri.org/t/unable-to-install-v4-2-1/295/16?u=jcohenadad

Fixed by https://github.com/neuropoly/spinalcordtoolbox/pull/2671


Use FQDN when comparing node name

This uses the FQDN when comparing the node name. Node names can be either IP address or FQDN names. The must resolve across the whole cluster. This code handles the case when there are 2 nodes with the same hostname in different subnets.

Curious, why FQDN? By default the kubelet uses the value of hostname, which isn't the FQDN. In order for it to use that value you'd have to:

Have DNS enabled in your VCN (not a requirement in OCI)
Set --override-hostname=$(hostname -f) on the kubelet.

This would require custom setup for installers like kubeadm if i'm not mistaken. Also, existing OCI cloud tools, like the CCM, would differ in their approach.

One of the requirements for nodename is that they are all resolvable and reachable from all other nodes. If you don't have DNS enabled in you VCN then you are either going to have to write a hosts file or use IPs as the node name.

This isn't true. Curious why you think that? You can set the preferred address the API server uses to communicate with nodes; typically in clouds that is set to InternalIP because of this exact problem. I don't have DNS in our VCN right now and I'm using the flex volume driver :)

I'd say we just keep the same logic that we have in the CCM until OCI solutions have better tagging support (terraform at least). I.e. Nodes across clusters need to have unique names and when there are multiple nodes returned with the display name you error.
IMO, the best long term solution is filter by a known cluster tag, which is what AWS does. Then duplicate hostnames wouldn't matter because that wouldn't work in the same cluster anyway because of node registration conflicts. If there are duplicates across clusters we can pick the resource for the current cluster by that tag.

I'm also Curious why I thought that and I couldn't find the docs I thought I read. Maybe this was outdated 1.6 information.
I was talking about 2 different k8s clusters in the same VCN with the same hostnames but differing subnets.

https://kubernetes.io/docs/concepts/architecture/nodes/#management
 and validate the node by health checking based on the metadata.name field (we assume metadata.name can be resolved).

Cool. I fully endorse the wait for tags

That documentation is outdated afaik. https://github.com/kubernetes/kubernetes/issues/22063


Add coordination number flag

We need a flag on the ::Valid method making it possible to turn of validation for coordination number (+60 on day). The flag should default to enabling them as that is how it is currently working.
See https://github.com/personnummer/meta/issues/9 for meta discussion.

Implemented in #8 .


ng build -prod errors with 1.7.0-RC.0

Versions
Angular CLI: 1.7.0-rc.0
Node: 9.5.0
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
@angular/cdk: 5.1.0
@angular/cli: 1.7.0-rc.0
@angular/flex-layout: 2.0.0-beta.10-4905443
@angular/material-moment-adapter: 5.1.0
@angular/material: 5.1.0
@angular-devkit/build-optimizer: 0.3.1
@angular-devkit/core: 0.3.1
@angular-devkit/schematics: 0.3.1
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.0-rc.0
@schematics/angular: 0.3.1
@schematics/package-update: 0.3.1
typescript: 2.4.2
webpack: 3.10.0
Repro steps

ng build -prod

Observed behavior
<!-- Normally this includes a stack trace and some more information. -->
..\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:40
                callbacks[i](err, result);
                            ^

TypeError: callbacks[i] is not a function

### Desired behavior
Application compiled without any error

### Mention any other details that might be useful (optional)
It was working fine with 1.7.0-beta.3

I am the same. The same problem with 1.6.8 too

I have the same problem.
.../node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:40
		callbacks[i](err, result);
		            ^
TypeError: callbacks[i] is not a function

Versions
@angular/core": "^5.2.4
@angular/cli": "^1.6.8
Node 9.4.0
Dependencies
"webpack": "3.10.0",
"enhanced-resolve": "3.4.1",

Duplicate of  #9550

npm install<EMAIL_ADDRESS>is solved the problem

npm install<EMAIL_ADDRESS>is solved the problem
not working form me

npm install<EMAIL_ADDRESS>also worked for me


Console error: Invalid prop inputStyle

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

Action Performed:

Refresh the site
Press CMD + Shift + K to open the New Group Page.

Expected Result:
No console error
Actual Result:
Console error occurs:
react_devtools_backend.js:4026 Warning: Failed prop type: Invalid prop `inputStyle[2]` of type `boolean` supplied to `BaseTextInput`, expected `object`.
    at BaseTextInput (webpack-internal:///./src/components/TextInput/BaseTextInput.js:86:81)
    at TextInput (webpack-internal:///./src/components/TextInput/index.js:46:81)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at ArrowKeyFocusManager (webpack-internal:///./src/components/ArrowKeyFocusManager.js:52:81)
    at OptionsSelector (webpack-internal:///./src/components/OptionsSelector.js:208:81)
    at withOnyx (webpack-internal:///./node_modules/react-native-onyx/dist/web.development.js:1992:73)
    at withLocalize(Component)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at KeyboardAvoidingView (webpack-internal:///./src/components/KeyboardAvoidingView/index.js:16:16)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at ScreenWrapper (webpack-internal:///./src/components/ScreenWrapper.js:107:81)
    at withOnyx (webpack-internal:///./node_modules/react-native-onyx/dist/web.development.js:1992:73)
    at WrappedComponent (webpack-internal:///./node_modules/@react-navigation/compat/lib/module/withNavigation.js:12:5)
    at NewChatPage (webpack-internal:///./src/pages/NewChatPage.js:113:81)
    at withOnyx (webpack-internal:///./node_modules/react-native-onyx/dist/web.development.js:1992:73)
    at WithWindowDimensions (webpack-internal:///./src/components/withWindowDimensions.js:72:83)
    at withLocalize(Component)
    at NewGroupPage
    at StaticContainer (webpack-internal:///./node_modules/@react-navigation/core/lib/module/StaticContainer.js:10:16)
    at EnsureSingleNavigator (webpack-internal:///./node_modules/@react-navigation/core/lib/module/EnsureSingleNavigator.js:15:5)
    at SceneView (webpack-internal:///./node_modules/@react-navigation/core/lib/module/SceneView.js:21:5)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at CardSheet (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Stack/CardSheet.js:14:3)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at AnimatedComponent (webpack-internal:///./node_modules/react-native-web/dist/vendor/react-native/Animated/createAnimatedComponent.js:135:37)
    at AnimatedComponentWrapper
    at Dummy (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/GestureHandler.js:12:3)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at AnimatedComponent (webpack-internal:///./node_modules/react-native-web/dist/vendor/react-native/Animated/createAnimatedComponent.js:135:37)
    at AnimatedComponentWrapper
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at Card (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Stack/Card.js:54:5)
    at CardContainer (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Stack/CardContainer.js:20:3)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at NativeScreen (webpack-internal:///./node_modules/react-native-screens/lib/module/index.js:54:1)
    at AnimatedComponent (webpack-internal:///./node_modules/react-native-web/dist/vendor/react-native/Animated/createAnimatedComponent.js:135:37)
    at AnimatedComponentWrapper
    at MaybeScreen (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Screens.js:31:3)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at MaybeScreenContainer (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Screens.js:19:3)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at Background (webpack-internal:///./node_modules/@react-navigation/elements/lib/module/Background.js:13:3)
    at CardStack (webpack-internal:///./node_modules/@react-navigation/stack/lib/module/views/Stack/CardStack.js:199:5)
    at div
    at eval (webpack-internal:///./node_modules/react-native-web/dist/exports/View/index.js:90:25)
    at SafeAreaProviderCompat (webpack-internal:///./node_modules/@react-navigation/elements/lib/module/SafeAreaProviderCompat.js:32:3)
    at div
    at eval (webpack-internal:/

Workaround:
n/a – no workaround needed
Platform:
Where is this issue occurring?

Web (only verified on web, may occur elsewhere)

Reported by: @sobitneupane
Version Number: 1.1.82-4
Reproducible in staging?: n/a
Reproducible in production?: n/a
View all open jobs on GitHub

I had reported this issue here : https://expensify.slack.com/archives/C01GTK53T8Q/p1649048261994809

I had reported this issue here : expensify.slack.com/archives/C01GTK53T8Q/p1649048261994809

Fair's fair – you beat me to it 😄
Added you as the issue reporter so you'll get the reporting bonus for this 🤑

@parasharrajat I didn't verify but I'll take your word for it :D

@JmillsExpensify I assigned this to @parasharrajat as the contributor, not the C+. I can just review the PR myself – no need for a C+ on this one since it will be easy to verify.

Got it, thanks!

Upwork job is here for @parasharrajat: https://www.upwork.com/jobs/~01541e5cd8fb2fc88f

Not going to apply the Exported label since all parties are already present.

@sobitneupane Mind applying to the Upwork job for reporting? It's here: https://www.upwork.com/jobs/~01541e5cd8fb2fc88f.

@sobitneupane Mind applying to the Upwork job for reporting? It's here: https://www.upwork.com/jobs/~01541e5cd8fb2fc88f.

Applied.

Looking at the linked PR from @parasharrajat, that hit production 5 days ago. I'm not super sure why we're not seeing the normal automated comment so I'm going to add one manually. Please correct me if I've misunderstood something, thanks!

Payments issued to contributors and linked PR is past the regression period. Closing this out. Thanks everyone!


Tab navigation of header Container is broken

OpenUI5 version:
1.98.0
Browser/version (+device/version):
Chrome 98
URL (minimal example if possible):
https://jsfiddle.net/charlesbourasseau/9nqukz1a/2/
Steps to reproduce the problem:

Open the link, "Item 1" is selected
Press tab

What is the expected result?
I would expect that the link "Bottom link" would be selected.
What happens instead?
The focus stays on "Item 1" and only goes to "Bottom link" if you press tab a second time.
https://user-images.githubusercontent.com/611389/154691827-b5408579-1104-4f32-a8d6-860360737f08.mov
Any other information? (attach screenshot if possible)
Moreover if you press left after the first tab, a javascript error will be thrown.

Hello @cbou,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Dobrin

Hello Colleagues,
Once the Tab reaches the first header item we should use Left/Right arrow keys to navigate on the same header container, which will be a standard behaviour.
On the other hand, the console error is not presented anymore, so I am closing the incident.
Kind Regards,
Niya


Stuck on identifying network

With the hosts in my windows 11 hosts file after waking/booting network will be stuck on identifying for a random amount of time like 30 minutes.

Hi Chayton @Chaython.  Please see Warning: Using this hosts file in Windows may require disabling DNS Cache service in the repo readme.
Closing.


Added store gateway e2e test.

Changes

Added minio to test deps
Added flag for store e2e to adjust sync interval
Fixed s3 test config creation from env
Added debug log for querier query
Added thanos store gateway e2e

Verification
local make test + CI

ERROR Unable to start the server: Port :20291 is already in use. wasn't minio server  closed after the previous tests 🤔

https://circleci.com/gh/improbable-eng/thanos/1254?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link


Add documentation on borough, census places to the "what places are available here?" text

@MikeDelue @kyleredilla Do we have URLs that we want to be pushed to the "What places are available here?" for Census and Borough information in Alaska?


Add inject req and pressure spec and reconcile logic

add spec to specify inject pressure and job
add reconcile logic to control

Codecov Report

Merging #303 (0ed2452) into main (46be6a7) will decrease coverage by 13.31%.
The diff coverage is 49.06%.

:exclamation: Current head 0ed2452 differs from pull request most recent head f6414ac. Consider uploading reports for the commit f6414ac to get more accurate results

@@             Coverage Diff             @@
##             main     #303       +/-   ##
===========================================
- Coverage   62.36%   49.06%   -13.31%
===========================================
  Files           2        8        +6
  Lines         279      856      +577
===========================================
+ Hits          174      420      +246
- Misses        103      368      +265
- Partials        2       68       +66

Impacted Files
Coverage Δ

pitr/cli/internal/pkg/shardingsphere-proxy.go
0.00% <0.00%> (ø)

pitr/cli/internal/pkg/local-storage.go
42.73% <42.73%> (ø)

pitr/cli/internal/cmd/restore.go
44.58% <44.58%> (ø)

pitr/cli/internal/cmd/show.go
56.09% <56.09%> (ø)

pitr/cli/internal/cmd/backup.go
58.87% <58.87%> (ø)

pitr/cli/internal/pkg/agent-server.go
72.54% <72.54%> (ø)

pitr/cli/pkg/gsutil/conn.go
76.47% <76.47%> (ø)

pitr/cli/pkg/stringutil/rand_string.go
91.30% <91.30%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Return Sequences

Set Return sequences equal to True whenever multiple layers are selected

Completed auto setting of return sequences depending upon no. of layers

Set


Use open router for ai bot

We are replacing the AI "backend" from OpenAI to OpenRouter so that we can track $ cost for our AI generations (needed for tracking user credit spending), and be more flexible about which AI model to use in case we'll want to change it later.
This depends on https://github.com/cardstack/infra/pull/561 - need to deploy that one first.

@IanCal yeah you were right, needed to update the model, if I use model: 'openai/gpt-4o' then I am able to see this model is actually used for generating responses:

However I am having difficulties using the latest version of gpt-4o. Here's what happens if I use openai/chatgpt-4o-latest (which is the codename from your link):

I tried using openai/gpt-4o-latest which works but it actually falls back to GPT-4:

@jurgenwerk I think the one you've found is the correct one, ignore the one I got


Icon request: mini carets

Describe the requested icon(s)
I'd like to see mini versions of the caret icons, specifically for use in buttons, dropdown buttons, and select UIs. The current caret-down -up -left -right have their place I'm sure. But when used as an ornament within a button, dropdown button, or select they just look a little oversized. Of course one could size down and up the weight of the icon in these particular use cases, but I think most folks typically use icons at the same size/weight across a site or app, and adjusting for specific cases would cause some unnecessary complexity.
References
I've included a screenshot using the caret-down icon from a variety of sets within a dropdown button (all at 20px x 20px), and you can see the Phosphor icon appears quite a bit larger. I would argue that Google Material's is too small, while Feather and Heroicons feel pretty nice.

Additional context
Heroicons actually includes a "mini" version of their entire icon set (the mini version of the caret-down is what you see in that screenshot above). I'm not suggesting that, but I think the carets would really benefit from mini versions.

You can adjust the size of the icon

Adjusting the size of the icon in this way is absolutely an option. The issue is that you then aren't able to exactly match the weight of the icon with that of other icons in your application that are being used at the default size.

Adjusting the size of the icon in this way is absolutely an option. The issue is that you then aren't able to exactly match the weight of the icon with that of other icons in your application that are being used at the default size.
Also, sometimes an element will depend on the overall (outer) size of the icon being consistent (an icon-only button, for example). If the size of the icon is changed, the overall size of the button changes as well.

      {/* or inline-flex */}

@lavinejames agree with you there, and I can see the need for a smaller set of carets that retains appropriate stroke width. Something we'll look at in the next release.


React 18 <StrictMode> tweaks and bug fixes

This PR fixes some issues with @dnd-kit when used with React 18 <StrictMode>

Any progress here?

Will this cover adding support to other packages like<EMAIL_ADDRESS>

It would be nice if this is going to be merged. It solves a lot of problems for react 18 installs.

Any updates?

Look's like no one cares about it, I probably need to switch to react-beautiful-dnd

Look's like no one cares about it, I probably need to switch to react-beautiful-dnd

same here.

I'm planning to work on this over the holiday break. Please keep in mind that this is an open source project, and if you want things to move faster, feel free to open a PR or sponsor the project.

Look's like no one cares about it, I probably need to switch to react-beautiful-dnd

there is also https://react-spectrum.adobe.com/react-aria/dnd.html maybe it has what you need.

I'm planning to work on this over the holiday break. Please keep in mind that this is an open source project, and if you want things to move faster, feel free to open a PR or sponsor the project.

I have no problem becoming a sponsor if it can help toy make the sortable tree example work properly. https://github.com/clauderic/dnd-kit/issues/860
Does this PR fix that issue described?

@Eduard-Hasa Yes, it's the same bug

@Eduard-Hasa Yes, it's the same bug

If it's the same bug then does that mean strict mode in react 18 is causing my issue? My issue occurs in the dnd-kit storybook tree example as well. O tried turning off strict mode on my project and still seeing the issue.
I have literally looked at every other library and this one is amazing. Not sure how this project is dying without any support.

I can confirm that the code in this pull request fixes the issues in https://github.com/clauderic/dnd-kit/issues/860
@clauderic I can say that after weeks of desperation to find a good drag and drop library and desperately trying to find a better one due to this issue... I can preach that nothing comes remotely close to dnd kit.
Coming from a user perspective I would so much rather pay a monthly fee for a actively maintained library then see this go. Please try to start some discussions with the community to see what we as users can do to help you maintain it and keep the library alive.

@clauderic any updates?


fix: Updated for section-to-collection changes

... and a bit of polish.

Most of the section-to-collection changes was centered in the utils/index.ts file around variablesFromPath.
I renamed vote-for-pedro.md to voteForPedro.md and changed its links because vote-for-pedro.md is actually not a valid content name.
I fixed an annoying React warning related to unkeyd elements in the landing-page.tsx.
I also better handled an issue when creating a new item in the posts collection that would result in an unhandled error because author had not been defined.

Also...
I set a resolutions for<EMAIL_ADDRESS>due to a bug that appeared when attempting to add a new document through the content-creator related to how final-form handles Field Arrays and async validate() methods:
https://github.com/final-form/final-form/issues/408
This is actually an issue in final-form and we'll probably lock the version in tinacms (I've already spoken with DJ about it).

I'm sort of unclear about why we needed the resolutions - if our yarn.lock was fixed on a working version of final form. Did you have to wipe out the yarn.lock at any point during this?
Overall I think it's probably best to stick with the resolutions because if a user removed the lock file things would break on them


is char a valid WordType?

The standard doesn't specify if char is signed or not.
Wondering if char shouldn't be removed as bool from binary_digits in the case it is unsigned.

Fixed.


AVRO-2594: Use JAVA env when building local docker.

It currently takes some manual intervention to create a "local user" docker image based on Java 11.
This PR enables the user to create one by doing:
JAVA=11 ./build.sh docker

N.B. The docker image tag that is generated always has the unchanged form avro-build-rskraba:latest.
Jira

[ ] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-XXX
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Still thinking about this -- I'd like to make some more changes and change the default CMD.  It's weird that it refers to a script that isn't available until a volume is mounted in the build.sh script.

Hello @Fokko @kojiromike !  I updated the Dockerfile to have both JDKs available (truly an ubertool container -- ~3GB).  There's almost no impact on the build time, adding about a dozen seconds.
To minimize impact on the existing container, I used the openjdk:11 image as the base (== debian:buster-slim).  I ran into issues trying centos, ubuntu:16.04, ubuntu:18.04, and both debian:stretch and debian:buster...
As a consequence, we have to pass the JAVA=11 environment into the docker container, both for local dev and Yetus builds.  I chose to select the JDK at the start of the main build script.
What do you think?  It's slightly cleaner than the sed solutions!

Would update-alternatives java be a more Ubuntu-idiomatic way to set the default jre then using a symlink directly?

Unfortunately, it's not ideal with this set-up: openjdk:11 + apt-get install openjdk-8-jdk.

JDK8 (as an apt-get package) is already the default alternative for /usr/bin
The openjdk:11 package has already fiddled with the PATH to make sure it's before that.
In a running container process, update-[java-]alternatives would need to be run as root.

The link is to simplify mapping the JAVA environment variable to a consistent location (it's also where openjdk:8 would have installed it).

(Rebased on master).
I added a function to the script change_java_version -- if you're running in bash or docker then you can source build.sh to get this function on your command line.

$ java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-8u232-b09-1~deb9u1-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
michael@0b0c224621e6:~/avro$ . build.sh
michael@0b0c224621e6:~/avro$ change_java_version 11
----------------------
Java version switched:
  JAVA_HOME=/usr/local/openjdk-11
  PATH=/usr/local/openjdk-11/bin:/usr/local/openjdk-8/bin:/usr/local/openjdk-11/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment 18.9 (build 11.0.5+10)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10, mixed mode)
michael@0b0c224621e6:~/avro$ java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment 18.9 (build 11.0.5+10)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10, mixed mode)

LGTM 👏


fixSemiJoinSemiJoinTransposeProject rule didn't handle mark join correctly

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Updates to use RBT::CreateKinematicsCache()

Constructor for KinematicsCache from a list of bodies will no longer be available to break the dependency of KinematicsCache on RigidBody. Per RobotLocomotion/drake#4378, RigidBodyTree manages the creation of a proper cache.
This PR updates director to use that new API.

@patmarion, PTAL. Thanks!

let me know when you want to merge it

@patmarion, RobotLocomotion/drake#4378 was reviewed and LGTM'd. This is therefore ready to merge now. Thanks!


Separators are nearly invisible with One Dark and One Light

Separators are nearly invisible with One Dark and One Light:

But work fine with virtually all other UI themes:

Perhaps an idea of how to solve this would be to use full white and full black colours with added alpha to the separator top/down and left/right sides. The alpha should take care to make it adapt to any background colour.

I played around with mix-blend-mode to make the separator always brighter than the background. screen mode does work but it doesn't look nice IMO:

I think the best way is to add an override in the theme-one-dark-ui.less and create one for any other theme that might need it.
@simurai do you have any thoughts on this perhaps?

Thank you for taking a look at this.

but it doesn't look nice IMO

That PR I had initially opened had virtually the same exact results, which is why I closed it; it's definitely better than the current One Dark and One Light result, but it makes all other UI themes look worse, transforming their separators into a single bright line without shadow.

I think the best way is to add an override in the theme-one-dark-ui.less and create one for any other theme that might need it.

I think that would be a good solution. From my tests, One Dark and One Light are the only ones showing this problem so having an override for them make sense.


Instance is now checked on other during eq to allow for other.eq...

Instance is now checked on other during eq to allow for other.eq() a chance of being executed. This fixes a bug where it raises an error when attempting to compare a Color object with None.
This fixes a bug when the Color class is used in Sqlalchemy-Utils and a Color object is compared with a Null value in the database.

This makes sense. I was wondering if we'd like to tackle this in the equality callable to let more choices to the user of the library. But I'm not sure this is a big deal. And I'm inclined to merge this quite quickly.
Do not bother about Travis saying it doesn't pass the test. They have updated recklessly there VM infrastructure to some very recent version of setuptools which breaks d2to1. The bug was reported.
I'll take care of that.
Thanks for your PR. I should include it soon.

Happy to help!

Hmm, I was in the process of reviewing it, and I dislike the fact that you are using an Exception as a return value, and actually I don't understood why you do that. I guess I'll move the implementation in the equality relation, or simply return False.
I'd like to make sure although that I'll address correctly your issue, and I'm now unsure to have correctly understood your concerns. Would you be able to show me a simple test that fails with the current master and that passes with your corrections ? That would clarify more what you need.

Vaab,
The proposed eq method does not return an exception, it returns the NotImplemented singleton. This singleton is used to signal that the classes eq method cannot be used for the current comparison, since the two objects being compared do not belong to the same instance. This allows for the other objects eq to be called instead.
See the following URL for an explanation of the NotImplemented singleton: http://shahriar.svbtle.com/python-notimplemented-type
Your code breaks in the following example:
newColor = Color()
newColor == None
(EXCEPTION)
newColor == "Hello"
(EXCEPTION)
This is because the current eq compares self.hex with other.hex , but it is not safe to assume that the other object has a hex attribute.
With the new example, the above will try newColor.eq, get the NotImplemented singleton since they are not the same instance, then it will use the None singleton's eq that presumably checks if the two objects share the same reference (Not sure what None's eq looks like TBH).

This really is the correct way to handle the eq so that your class plays well with others.

You are definitively right, sorry about that. I didn't know about the specifics of NotImplemented (which I obviously mistake for NotImplementedError exception). I've learned something new, many thanks.
I've pushed a new version of your commit (mostly some tests and docs, and formatted the commit message). Can I ask you to take a quick glance and check I've correctly documented and tested your issue ?

Vaab, I read through your documentation. Why would it be the case that red == blue would resolve as True?
They are both Color objects with different hex values? +Note that these instance would compare as equal to any other color::
+

red == blue

True

If both objects are Color, it will use your lambda function that compares self.hex to other.hex.

Should I add the following bold text to make it clearer ?
| As a side note, whatever your custom equaltiy function is, it won't be
| used if you compare to anything else than a Colour instance::
|
|    >>> red = Color("red", equality=lambda c1, c2: True)
|    >>> blue = Color("blue", equality=lambda c1, c2: True)
|
| Note that with such equality method, any color will compare equal to any other color... which is
| pretty useless as is, but nice to showcase what follows, so don't be astonished if:
|
|    >>> red == blue
|    True

Ah, okay I understand. You changed the equality function of those colour objects. Yes, sure that's fine, I suppose.


dunfell: Fix raspberrypi-cm3 boot when u-boot is used

@agherzan pls see #748

It will come in through https://github.com/agherzan/meta-raspberrypi/pull/754 (your commit was cherrypicked there).


Fix GridSpace and GridMatrix sort=False

Fixes #3462
Previously, sorted(set(...)) implicitly sorted grid keys, now passing sort=False has the intended effect:
import numpy as np
import holoviews as hv
hv.extension('matplotlib')

data = hv.Image(np.random.rand(10,10))
imgs = [
    (('C', 'dummy'), data),
    (('D', 'dummy'), data),
    (('A', 'dummy'), data),
    (('B', 'dummy'), data)
]
hv.GridSpace(imgs, sort=False, kdims=['dim1','dim2'])

#3770 is vaguely related (this PR highlights some code duplication) in the (non-) sorting of dimension values.

There does seem to be a real failure in the Python 2 tests. Presumably something to do with dict ordering? Can't wait to drop py2 support.

Bizarre,
print(sorted(set(('c', 'b'))))
print(list(dict.fromkeys(('c', 'b'))))

print(sorted(set(('b', 'c'))))
print(list(dict.fromkeys(('b', 'c'))))

Yields
['b', 'c']
['c', 'b']
['b', 'c']
['b', 'c']

in python 3
but
['b', 'c']
['c', 'b']
['b', 'c']
['c', 'b']

in python 2!

So, that should do the trick I hope...


Hardware acceleration

Hey! Can this use hardware instructions for conversion? Intel CPUs support hardware conversion since 2013, and the new 12-th gen also has support for arithmetic (I think?). Other architectures had that a while ago.
This might be possible without compiler support using embedded C code, but wouldn't that be out of scope for this?

Nvm, 12-th gen had this for a brief moment added by accident, but then got removed from later revisions. This probably means it is going to be in other upcoming Core series CPUs. It was already a thing for Sapphire Rapids Xeons.
I also opened an upstream issue.

In my use case we have float16 tensor outputs from a NPU on the RK3588 (Arm processor).   ARM does have NEON SIMD instructions to hardware accelerate the conversion from fp16 to fp32.  We can't make use of those extensions with Go as the compiler does not support SIMD instructions.
Via CGO you can interface with the ARM Compute library to make use of these instructions, however for our use case which involves converting 856,800 bytes from uint16->fp32 per video frame this is much slower than sticking with pure Go in this library.
However better performance is still attainable by using a precalculated lookup table for the uint16->fp32 conversion.
On the RK3588 we get a 35% performance improvement.
BenchmarkF16toF32NormalConversion-8<PHONE_NUMBER> ns/op 1720348 B/op 1 allocs/op
BenchmarkF16toF32LookupConversion-8<PHONE_NUMBER> ns/op 1720342 B/op 1 allocs/op

And on a Threadripper workstation we get a 69% improvement.
BenchmarkF16toF32NormalConversion-20 1302 916041 ns/op 1720322 B/op 1 allocs/op
BenchmarkF16toF32LookupConversion-20 3919 275437 ns/op 1720335 B/op 1 allocs/op

To create such a lookup table we are simply precalculating it in our application with.
import "github.com/x448/float16"

var f16LookupTable [65536]float32

func init() {
	// precompute float16 lookup table for faster conversion to float32
	for i := range f16LookupTable {
		f16 := float16.Frombits(uint16(i))
		f16LookupTable[i] = f16.Float32()
	}
}

Then converting our output buffer from uint16 to fp32 with.

func convertBufferToFloat32(float16Buf []uint16) []float32 {
float32Buf := make([]float32, len(float16Buf))
for i, val := range float16Buf {
	float32Buf[i] = f16LookupTable[val]
}

return float32Buf

}

@swdee Thanks for the suggestion!  I will try this and see how it goes.

@x448 We have a CGO version as worked with @TailsFanLOL and discussed here.

Golang declined the request to add this type to the language itself.
@swdee, perhaps we should improve what you have slapped together and merge it here, adding stuff from this project's wishlist while we are at it. My current concern in your fork is that -march=native -mtune=native only works properly on GCC with GNU/Linux. On other libcs (Alpine, Android) often only -mtune works therefore the hardware isn't utilized to the full potential, and in my experience when containerized it does nothing at all. Perhaps one could use inline assembly for each architecture, but I don't know Assembly. I might or might not be able to look into it on the weekends.

Here is one for x86 using AVX2.

#include <immintrin.h>
#include <math.h>  // For INFINITY

void float16_to_float32_buffer_avx2(const uint16_t* input, float* output, size_t count) {
    size_t i = 0;

    // AVX2 processes 8 float32 values at a time
    for (; i + 8 <= count; i += 8) {
        // Load 8 x uint16_t values into a 128-bit register
        __m128i in = _mm_loadu_si128((const __m128i*)(input + i));

        // Convert 8 float16 values to float32 (F16C intrinsic)
        __m256 result = _mm256_cvtph_ps(in);

        // Store the resulting 8 float32 values
        _mm256_storeu_ps(output + i, result);
    }

    // Handle remaining elements if count is not a multiple of 8
    for (; i < count; i++) {
        uint16_t f16 = input[i];
        uint32_t sign = (f16 & 0x8000) << 16;
        uint32_t exp = (f16 & 0x7C00) >> 10;
        uint32_t mant = f16 & 0x03FF;

        if (exp == 0) {
            if (mant == 0) {
                output[i] = sign ? -0.0f : 0.0f;
            } else {
                output[i] = (float)((sign ? -1 : 1) * (mant * (1.0 / 1024.0)) * (1.0 / (1 << 24)));
            }
        } else if (exp == 0x1F) {
            output[i] = sign ? -INFINITY : INFINITY;
        } else {
            output[i] = (float)((sign ? -1 : 1) * (mant + 1024) * (1.0 / 1024.0) * (1 << (exp - 15)));
        }
    }
}

// F16toF32BufferAVX2 converts float16 to float32 using SIMD on x86 platforms
func F16toF32BufferAVX2(float16Buf []uint16, float32Buf []float32) {
	C.float16_to_float32_buffer_avx2(
		(*C.uint16_t)(unsafe.Pointer(&float16Buf[0])), // Pointer to the input buffer
		(*C.float)(unsafe.Pointer(&float32Buf[0])),    // Pointer to the output buffer
		C.size_t(len(float16Buf)),                     // Number of elements to convert
	)
}

func BenchmarkF16toF32AVX2Conversion(b *testing.B) {
	// Load the buffer outside the loop to avoid reloading it during each iteration.
	float16Buf := loadBuffer()

	b.ResetTimer()

	for i := 0; i < b.N; i++ {
		float32Buf := make([]float32, len(float16Buf))

		// Use the AVX2-accelerated function
		float16.F16toF32BufferAVX2(float16Buf, float32Buf)
	}
}

With results on my workstation:
$ go test -bench=^BenchmarkF16toF32 -run=^$
goos: linux
goarch: amd64
pkg: github.com/x448/float16
cpu: AMD Ryzen Threadripper PRO 5975WX 32-Cores
BenchmarkF16toF32LookupConversion-20                        3188            358243 ns/op
BenchmarkF16toF32NormalConversion-20                        1249            920966 ns/op
BenchmarkF16toF32CGOSingleConversion-20                       69          17451686 ns/op
BenchmarkF16toF32CGOVectorConversion-20<PHONE_NUMBER> ns/op
BenchmarkF16toF32CGOBufferSingleConversion-20               3459            289367 ns/op
BenchmarkF16toF32CGOBufferVectorConversion-20               5122            227647 ns/op
BenchmarkF16toF32AVX2Conversion-20                          6366            182427 ns/op
PASS
ok      github.com/x448/float16 8.530s

I actually did an Assembly version using NEON instructions for ARM.

That's great. Unfortunately NEON isn't IEEE compatible as it handles handles subnormals as equal to zero (with some other minor differences).
As far as I am aware, the armv8's FPU offers IEEE compatible instructions.


Fix installation instructions

Thank you for this, but I think we shouldn't be selecting a specific binary (in this case haskell-language-server) as I stated in my comment here. I think this branch ( multi-version ) is still WIP until we find a way to expose both binaries.
On the other hand, I'm not using NixOS so it looks like packages.haskell-language-server.components.exes doesn't work ( it does work with nix-env -iA), so I guess the correct equivalent would be something like:
environment.systemPackages = [
  (import (builtins.fetchTarball "https://github.com/korayal/hls-nix/tarball/master") {}).hls-ghc865.haskell-language-server
  (import (builtins.fetchTarball "https://github.com/korayal/hls-nix/tarball/master") {}).hls-ghc865.haskell-language-server-wrapper
];


fix path to random service

Just tried again with a fresh build
http://localhost:8786/build/services/random.js is loaded from
whitelisted.js
On Fri, Jun 21, 2019 at 5:53 PM Paul Lindner<EMAIL_ADDRESS>wrote:

@lindner approved this pull request.
so weird, it worked for me...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PolymerLabs/arcs/pull/3219?email_source=notifications&email_token=AAAXTS64TBRAJ46B5OMCHPLP3VZXDA5CNFSM4H2VPAKKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB4KZZHY#pullrequestreview-253074591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAXTS6HVMRG5TQOW4242Q3P3VZXDANCNFSM4H2VPAKA
.

I believe the extra '..' is ignored for your URL after it hits root.
[host]/shells/configuration/whitelisted.js imports from '../../../build/services/random.js', so
[host]/shells/configuration/../../../build/services/random.js
[host]/shells/../../build/services/random.js
[host]/../build/services/random.js

At this point [host]/.. is the same as [host] (root of host).
On my test system, arcs lives in [host]/arcs/.... The extra folder revealed the problem.


WORKING GOOD in CENTOS7/RHEL7

Good news! everything working smoothly in both CENTOS7 and RHEL7. Just make sure that if you want to port those Linux Distro, make sure to pull the official images in their respective repos
I am having problem using genie as I am using incorrect LINUX DISTRO as i created it by myself. It is much easier to pull official LINUX Distro in their respective official images repositories.
THANK YOU TO THE AUTHOR! SUCH A GREAT WORK!
I am arranging my github profile, and will push/upload all the LINUX DISTRO images I am using!

as it is working good in CentOS7 and RHEL7, the Cloudera Manager 6.2.0 is working smoothly in the CentOS7 with subsystemctl. if it is working in CentOS7, there is no reason why it would not work in RHEL7 as well.


fixing a small format thing

🍃

Thanks!
On Tue, Apr 19, 2016 at 11:45 AM, ShyArmadillo8<EMAIL_ADDRESS>wrote:

Merged #990 https://github.com/silshack/spring2016/pull/990.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/silshack/spring2016/pull/990#event-633149229


last_green Bazel failure with Rules Scala proto rules

@comius could you help us understanding if we can do anything about this failure?
ERROR: Traceback (most recent call last):
--

<span class="term-fg31 term-fg1">ERROR: </span>error
 loading package '': at /workdir/scala_proto/scala_proto.bzl:3:5:
initialization of module 'scala_proto/private/scala_proto.bzl' failed

Buildkite link: https://buildkite.com/bazel/rules-scala-scala/builds/4142#0186c3b6-6329-4d9a-b651-d4d341472bdd

Similar report https://github.com/bazelbuild/bazel/issues/17713


Update gonzales-pe to a newer version

Update gonzales-pe to 3.4.4 and make the dependency less strict

Strict gonzales-pe dependency is intended. Upgrading gonzales-pe has been a sensitive issue in the past @varya what do you think?

I have no problems so far


Add ClusterGroup CRD resource to antrea-network-policy doc

/skip-all

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@606b161). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1803   +/-   ##
=======================================
  Coverage        ?   34.68%
=======================================
  Files           ?      194
  Lines           ?    16545
  Branches        ?        0
=======================================
  Hits            ?     5739
  Misses          ?     9963
  Partials        ?      843

Flag
Coverage Δ

kind-e2e-tests
34.68% <0.00%> (?)

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


Metriculous+Bokeh Out of range float values are not JSON compliant

I believe this is a bug with the Metriculous Bokeh integration but I'm not sure what is triggering it.
Here is a a code snippet to reproduce it:

import metriculous
import numpy as np

predictions = [np.array([[0.02651198, 0.31270504, 0.04171027, 0.08619863, 0.16541226,
        0.11558858, 0.12004455, 0.13182868],
       [0.0636719 , 0.18429258, 0.08450789, 0.1157857 , 0.21399513,
        0.08028985, 0.09965403, 0.15780292],
       [0.03115291, 0.30915564, 0.04554546, 0.11180063, 0.11298609,
        0.12809892, 0.12540455, 0.1358558 ],
       [0.07111797, 0.12305891, 0.07020132, 0.15796672, 0.24655697,
        0.0836428 , 0.07912376, 0.16833155],
       [0.07959884, 0.12210452, 0.06945297, 0.15947734, 0.2427768 ,
        0.08263489, 0.07852125, 0.16543338],
       [0.01766902, 0.33444592, 0.0312464 , 0.304933  , 0.07606831,
        0.11432294, 0.0662983 , 0.05501606],
       [0.07516593, 0.09484643, 0.14125083, 0.06031764, 0.25438443,
        0.09057547, 0.12231521, 0.16114406],
       [0.01725348, 0.2626249 , 0.03184433, 0.09360438, 0.28739157,
        0.14218643, 0.07242204, 0.09267287],
       [0.06459036, 0.16860159, 0.06819151, 0.10878273, 0.24783328,
        0.08361257, 0.08607707, 0.17231087],
       [0.02426506, 0.35321227, 0.0365901 , 0.10876535, 0.19372101,
        0.11075294, 0.07755516, 0.09513812],
       [0.01334525, 0.40144277, 0.02168825, 0.2738081 , 0.07262825,
        0.11011887, 0.06275296, 0.04421557],
       [0.05111578, 0.18965946, 0.06345861, 0.10171634, 0.29270712,
        0.06656697, 0.06664741, 0.16812828],
       [0.03433737, 0.35056743, 0.04554536, 0.1223052 , 0.14757192,
        0.10423103, 0.08725566, 0.10818605],
       [0.02045722, 0.36372438, 0.06161968, 0.20598333, 0.07393774,
        0.13290711, 0.06163201, 0.07973854],
       [0.06024894, 0.17526025, 0.0700492 , 0.11108048, 0.20588736,
        0.11613052, 0.08757272, 0.17377052],
       [0.06320383, 0.11961269, 0.07309992, 0.13411018, 0.21522452,
        0.12376933, 0.09002887, 0.18095064],
       [0.06320383, 0.11961269, 0.07309992, 0.13411018, 0.21522452,
        0.12376933, 0.09002887, 0.18095064],
       [0.02111111, 0.37781438, 0.03542091, 0.15676846, 0.07582452,
        0.11120252, 0.07607654, 0.14578155],
       [0.01435957, 0.56506133, 0.02622501, 0.10991825, 0.05670529,
        0.09522142, 0.05140135, 0.08110777],
       [0.01447272, 0.56697184, 0.02637914, 0.11005513, 0.05682856,
        0.09225151, 0.05152839, 0.08151273],
       [0.04570318, 0.11008076, 0.06587777, 0.09217358, 0.25748935,
        0.1264705 , 0.11295175, 0.1892531 ],
       [0.01105192, 0.43763763, 0.02243476, 0.25057724, 0.07013009,
        0.1070659 , 0.06017836, 0.04092411],
       [0.01105192, 0.43763763, 0.02243476, 0.25057724, 0.07013009,
        0.1070659 , 0.06017836, 0.04092411],
       [0.06399985, 0.12088028, 0.09812263, 0.13254756, 0.2368868 ,
        0.06306084, 0.07799452, 0.20650752],
       [0.02580354, 0.2912477 , 0.0452958 , 0.10479757, 0.19409011,
        0.11631037, 0.07928232, 0.14317259],
       [0.02394   , 0.28100577, 0.06761745, 0.10079238, 0.18286197,
        0.11120233, 0.07584769, 0.15673243],
       [0.02859701, 0.12345824, 0.02452153, 0.12446079, 0.10724279,
        0.30250114, 0.14545403, 0.14376447],
       [0.01763562, 0.26390415, 0.02797072, 0.09410465, 0.33519107,
        0.09990271, 0.07291644, 0.08837461],
       [0.05719835, 0.11961728, 0.06110419, 0.09842541, 0.23005427,
        0.12413418, 0.10744236, 0.20202397],
       [0.01512977, 0.44863623, 0.02352207, 0.09241457, 0.1371182 ,
        0.1376256 , 0.06627141, 0.07928215],
       [0.13617955, 0.11844175, 0.06990904, 0.09725405, 0.2089029 ,
        0.14193644, 0.07938706, 0.14798921],
       [0.05659495, 0.12756449, 0.09210333, 0.12443028, 0.23832083,
        0.0680717 , 0.0928731 , 0.20004131],
       [0.04699743, 0.17098074, 0.06562918, 0.06444676, 0.25861254,
        0.0523265 , 0.10781392, 0.23319292],
       [0.06176807, 0.17528789, 0.07962973, 0.06739685, 0.2270808 ,
        0.06453936, 0.11641537, 0.20788196],
       [0.05633127, 0.11881155, 0.07823401, 0.1879416 , 0.19890387,
        0.10915504, 0.08803149, 0.16259117],
       [0.03467053, 0.3494804 , 0.06560414, 0.08256355, 0.11014081,
        0.13175112, 0.10785011, 0.11793937],
       [0.02571611, 0.4676369 , 0.0442673 , 0.14291236, 0.07799932,
        0.12573668, 0.0587831 , 0.05694821],
       [0.02525828, 0.40146384, 0.05145144, 0.11157996, 0.12324058,
        0.10363442, 0.07611745, 0.10725403],
       [0.04221298, 0.05616246, 0.05433249, 0.09642576, 0.26045817,
        0.10190966, 0.18601942, 0.20247905],
       [0.04178631, 0.1104403 , 0.0894035 , 0.09241916, 0.2568906 ,
        0.10427111, 0.11317873, 0.19161028],
       [0.04844856, 0.16488735, 0.082458  , 0.10612834, 0.23859234,
        0.09024726, 0.09954155, 0.1696966 ],
       [0.12209805, 0.05936319, 0.22111115, 0.08510352, 0.09670409,
        0.0603577 , 0.21275316, 0.14250913]], dtype='float32')]
ground_truth = [3, 4, 3, 5, 7, 1, 7, 1, 2, 5, 3, 6, 0, 6, 4, 6, 5, 4, 1, 6, 0, 4, 7, 2, 6, 6, 5, 7, 1, 3, 4, 5, 1, 3, 7, 3, 1, 1, 4, 0, 5, 7]

reporter = metriculous.compare_classifiers(
    ground_truth=ground_truth,
    model_predictions=predictions
)

reporter.save_html('./metriculous_out.html')

I was able to reproduce this on the latest version and the develop branch.

Hi @jgreene, thanks for reporting the issue.
On a first attempt to reproduce it, I don't run into the "Out of range float values are not JSON compliant" when I try your example on develop (https://mybinder.org/v2/gh/metriculous-ml/metriculous/develop?filepath=notebooks). I've seen the error before, but it shouldn't really come up as long as all the NaNs are in Numpy arrays (as opposed to plain lists) when they are fed into Bokeh. This seems to be the case in the _bokeh_confusion_matrix function on develop.
However, @magnusja ran into a very similar issue recently (https://github.com/metriculous-ml/metriculous/pull/3#discussion_r550153975) and I also had trouble reproducing it.
I'd love to find out what's going on and reproduce it. Are you sure that you get the error on develop? Would you mind sharing the Numpy and Bokeh versions you are on when the issue comes up?

Hi @jgreene, thanks for reporting the issue.
On a first attempt to reproduce it, I don't run into the "Out of range float values are not JSON compliant" when I try your example on develop (https://mybinder.org/v2/gh/metriculous-ml/metriculous/develop?filepath=notebooks). I've seen the error before, but it shouldn't really come up as long as all the NaNs are in Numpy arrays (as opposed to plain lists) when they are fed into Bokeh. This seems to be the case in the _bokeh_confusion_matrix function on develop.
However, @magnusja ran into a very similar issue recently (https://github.com/metriculous-ml/metriculous/pull/3#discussion_r550153975) and I also had trouble reproducing it.
I'd love to find out what's going on and reproduce it. Are you sure that you get the error on develop? Would you mind sharing the Numpy and Bokeh versions you are on when the issue comes up?

I forgot to mention, please note that the latest release (0.2.1) does not yet contain the fix committed in 38e1619. So I would expect the error to come up with version 0.2.1, but not with develop.

I forgot to mention, please note that the latest release (0.2.1) does not yet contain the fix committed in 38e1619. So I would expect the error to come up with version 0.2.1, but not with develop.

New release 0.3.0 is now on PyPI. Do you still run into the problem?

New release 0.3.0 is now on PyPI. Do you still run into the problem?

My mistake, it appears 0.3.0 does resolve the issue.  Thank you for your help.

My mistake, it appears 0.3.0 does resolve the issue.  Thank you for your help.

No worries, the release was overdue, and this was a good reminder. Thanks again for reporting the issue.

No worries, the release was overdue, and this was a good reminder. Thanks again for reporting the issue.


Component to get your Paypal order information

Hi :)
I would like to share my component were you can enter a Paypal order number and then you get some order informations. I used axios to do some external API calls. :)
Thanks!

Hey @23Thom - I've created https://github.com/NowComponents/paypal-order for you :)

Thanks a lot😊👍🏻


#error file not found

Sir, it shows error after selecting options.
As
auto.sh: line 35:instagram.py :command not found

not found me too, did you know how?


Update ama-migrate.md

Change status of IIS and custom logs to collection only.

@NoamLandress : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi and thanks for your contribution to docs! I've moved off the team and am tagging a current team member. @yelevin , can you take a look here?

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @batamig

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @batamig

I re-created this PR in the private repo (azure-docs-pr) as #203698.
#please-close


Apexcharts with Pjax

Solved

How to solve it, can you share.thanks

@augusl
I embedded the chart as an iframe from a separate page, a bit dirty but it works lol.

@augusl
I embedded the chart as an iframe from a separated page, a bit dirty but it works lol.

ok.thanks