Slider is not interactive, can't move it

I followed the simple instructions on this page: https://www.npmjs.com/package/react-native-awesome-slider
I'm using expo sdk v50, I've installed  everything according to instructions on above page, to quickly get going I've just added this in my app:
import { useSharedValue } from 'react-native-reanimated';
import { Slider } from 'react-native-awesome-slider';

export const Example = () => {
  const progress = useSharedValue(30);
  const min = useSharedValue(0);
  const max = useSharedValue(100);
  return (
    <Slider
      style={styles.container}
      progress={progress}
      minimumValue={min}
      maximumValue={max}
    />
  );
};

and also wrapped at relevant place with GestureHandlerRootView.
Finally the Slider would render on my device (Pixel 7 Pro) without errors, but now while it looks "awesome", it's dead, nothing happens when I try to pull it. And I have no clue if its a bug or something else.

Solved

Solved

what was the problem? its happening for me too

Sorry guys I forgot how I solved it. I usually share my solutions when I close the ticket, but I forgot to do it this time. If one of you figures it out, do not forget to share it here for the others! :)


Bikeshedding: ++li

Cc @cgyarvin
I am fond of names like weld, skim, and skip, and the %~ "method call" syntax is at present too unweildy(see #16). Additionally, things like sort, flop, scag/slag, etc. have no clear analogue in trees(except perhaps qeus?), and while this doesn't matter for the principle of |_ cores, it is a consistency of hoon/hoon interface that would be sacrificed.
Homo and limo should definitely go next to silt and milt in the constructor section, and any~li/all~li would be outright better names, but the rest are far too commonly used to move them without coming up with three-letter mnemonics that are significantly better than e.g. the average runic keyword.

pls no change for the sake of change

This has in fact occurred to me as a change to make before, I just didn't
have any idea what to do with the calling convention, and still don't for
the names.
On Sunday, 21 February 2016, Raymond Pasco<EMAIL_ADDRESS>wrote:

pls no change for the sake of change
—
Reply to this email directly or view it on GitHub
https://github.com/urbit/arvo/issues/17#issuecomment-186923894.

Nothing must be done, this is nothing, therefore we must do it

@cgyarvin please weigh in.

Raymond is right.


All Joycons But Last Has 1 Second Delays

If more info needed pls specify

@EdTheDog is it consistently laggy? does it only happen under certain conditions? how many joycons are you connecting?

I am connecting 2 joycons but I have tried 3 and only the last joycon connected responds fast. It seems to happen no matter what I do. Yes, it is consistent. It's always 1 second not more not less. So far I have tried Restarting my computer, connecting the joycon back to the switch and then connecting them back to my PC, and I have also tried updating both the joycon driver and Vjoy. I have checked my pc ram and CPU which are both fine so I don't seem to be paging the data. Still trying though.

Also, I would like to say the work you have been doing is amazing! It is awesome that someone is trying to do this. :)

Oh, I think I know exactly what the problem is, I'll try to fix it around 4

Quick Question, What do you mean by 4? As at Four O'clock? And if so what time zone? I'm PTS and it's 1:30 at the time of this message. Anyway, I hope it's working out so far!

Hello?

Sorry lol, I meant 4pm EST (which it's way past) I ended up being busy with other stuff but will work on it now

OK Thank you Sorry for bothering you. :) Again I think this is incredible!

BTW where do I donate?

it's at the end of the readme: https://github.com/mfosse/JoyCon-Driver
the latest update should fix the bug.

Thank you so much! Will try now! But again I want to show my support! Is there a place to donate? If not then you should make one! :)

thanks! :D

Unfortunately, My Recent attempts have not been going well. The issue still persists on my computer. Reinstalling Vjoy now. Hmmm....

Did more investigating and found out that it doesn't seem to be your program. Right now I'm trying to set up a game the has mouse and button controls and only the joycon controlling the mouse needs to be analog. And since the last joycon connected works fine the Ill only connect that one to the program and it will work, right? Well, I ran the program with (R) joycon and it worked fine then connected the (L) joycon to do the buttons. But then the (R) joycon started going slow even tho I didn't refresh the program! So It seems to be something else. Anyway, that's all I have right now, and at the moment you're probably sleeping so... yeah. Anyway, hope this info might help.

Hello again, Just wanted to confirm that the Joycon Driver is working correctly on your computer?

Idk I didn't test it lol, I'd look into it but I'm packing/about to go home for thanksgiving

I just made some changes that I thought would fix the issue (without testing it) if it still isn't working, it probably isn't your setup / PC

Ok! Anyway, I hope you have fun at Thanksgiving!

Omg, I really wish this would work. I keep doing it over and over again because I just can't wait. Honestly, if you get the delays to work you could sell this is an online product for like 20 dollars. I would save up to buy that for sure. I don't want to pressure you or anything but... I CAN'T WAIT :D

Any updates so far? If you're busy It would be kind to notify for how long.

I'm on break rn and don't have access to my desktop, I won't be back until tomorrow, but I have to and will probably be busy until wednesday.

OK Thank you for the information :)

this should be fixed now

Thank you for putting up with me and thanks for helping me :)


.csv reader initial implementation

We want to add a .csv reader component/utility to our admin, to perform bulk imports. Initially it will be used for the new price list UI.
We will be implementing ways to handle parsing and gathering the required data server side, but for now we want to implement a MVP version where the file is parsed client side, and then makes the necessary requests to the server.
We also want to add this functionality to importing other entities such as products, so keep the component/utility generic so it can be reused for other domains.
Could use something like react-csv for the implementation.
See Figma: https://www.figma.com/file/a5Mb7n6lelmmFU28wqQybY/Customer-Groups%2C-Promotions-%26-Pricing?node-id=494%3A12226

Implementing the csv parser server side will not be that difficult, I think we should go for that directly and created in the parser directory maybe?

Closing since we will be parsing CSV files server-side


mprime 28.7 (new formula)

Great Internet Mersenne Prime Search

This seems to be available from source: http://www.mersenne.org/ftp_root/gimps/p95v287.source.zip

Sure, but trying to build it via included Makefile fails and there appears to be no compilation instructions. Also, it's recommended on the site to download the binary instead of the source.

What is the failure like? We prefer to build from source when possible.

I appear to have figured it out. Kind of tricky because of the missing compile instructions.
You first need to run a Makefile inside the gwnum directory to create a library file which is a dependency, then move back into the macosx64 directory and run the Makefile there.
How would I go about that most elegantly in a formula? A build script running the makes in sequence?

Just run these in the install method. Based on what you wrote something like this should work:
def install
  system "make", "-C", "gwnum"
  system "make", "-C", "macosx64"
  # ...
end

Note that make -C foo is equivalent to cd foo; make; cd -. So running make install in the bar directory can be done with make -C bar install.
Please ask if you have more questions :smiley:

Anything new on this?

Closing as dead. Please feel free to file a fresh PR if you're still interested here. Thank you for the submission to Homebrew! ❤


Override default styles with styles from language

The styles from<EMAIL_ADDRESS>have been updated in #313 (thanks @simmerer!). And due to #305, they are using more nested token styles.
However, they are missing some default styling (eg. JavaScript code blocks should have #9cdcfe as the default color), which I have found to be a limitation of react-syntax-highlighter. The default styles for a theme are not being overridden by those by the current language.
This pull request is a possible solution to that issue.

Looks like a very clean fix, @karlhorky.
Would you consider this "breaking," in the same way that https://github.com/react-syntax-highlighter/react-syntax-highlighter/pull/305 was "breaking" by causing a long-broken thing to start working? Or do you anticipate most users perceiving this as a bugfix?

Good question. I suppose I would see it as a semver minor, because:

it adds a new feature
it doesn't change the public API in a way that causes old code to break (like you mentioned, now themes will be displayed more accurately according to their styles)

What do you think?


[WIP]chore: update azure-sdk and azure cloud provider vendor

What type of PR is this?
/kind flake
What this PR does / why we need it:
The master branch of  azure cloud provider needs github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2019-12-01/compute. So update azure-sdk-for-go to v41.0.0+.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Release note:

azure cloud provider actually use azure-sdk-for-go v40.2.0, you could switch to use  v40.2.0 first.


I am confused about 'SHUFFLE' in mxnet.io.ImageRecordIter

Since my input .rec is not shuffled... So, I set:
def get_iterator(args, kv):
data_shape = (1, 64, 64)
train = mx.io.ImageRecordIter(
path_imgrec = args.data_dir + "train.rec",
mean_img    = args.data_dir + "mean.bin",
data_shape  = data_shape,
batch_size  = args.batch_size,
shuffle     = True,
rand_crop   = True,
rand_mirror = False,
num_parts   = kv.num_workers,
part_index  = kv.rank)
Is this shuffle all the data set? or only batch by batch?

mx.io.ImageRecordIter shuffle data by chunks

@dsqx71 answers the question precisely

@dsqx71 @tqchen Hello, I'm new to mxnet and I find out the shuffle options both in mx.io.ImageRecordIter and im2rec.py are chunk-wise(please correct me if I'm wrong), which makes shuffling inadequate.
Currently I'm shuffling the data list manually before create Record but it's kind of annoying. Is there any way to shuffle within the whole dataset using mxnet API? Thank you in advance!

mx.io.ImageRecordIter shuffle data within chunks

prefect

mx.io.ImageRecordIter shuffle data within chunks
what is chunk？ is it prefetched data？


Can you please share this in Swift only not Swift UI

Hi! Unfortunately this library supports only SwiftUI and it won't change in the foreseeable feature, as it would require too many changes in the code.


Make TestExternalities implement Send

Fixes: https://github.com/paritytech/substrate/issues/4013
CC @geigerzaehler

Awesome. Thanks!


No mocha

Recommend walking commit by commit.
There are a few hacky things I had to do to workaround some of the differences between rspec-mocks and mocha, namely https://github.com/ajm188/factory_girl/commit/356c974e09af6dd92c73b98eafe09d9377d2c867 and https://github.com/ajm188/factory_girl/commit/153a7f796cec688d76acef849553c9dbf05aa60a

Oh I can probably remove mocha from the Gemfile/gemspec, too 🚀

Going to let hound run again, then fix all the violations in a single commit.
Then I'll nuke bourne and mocha from the gemspec.

So the build seems to consistently broken on jruby-1.9mode for rails 3.2. This seems consistent across many other PRs/branches, so it's likely unrelated to my changes.
I've fixed all the hound violations, and so now I'll remove mocha/bourne from the gemspec

Thanks for the contribution @ajm188.
I've added one commit to avoid toggling #verify_partial_doubles & rebased on master to get the updated Travis config which no longer has jruby-1.9mode with Rails 3.2.
Hopefully once this build is green I can merge this in!

@odlp cool, thanks! Let me know if there's anything you need from me here :)


Manually boot checkup VMIs

The current checkup's approach to waiting until the VMI is "booted", i.e. the guest-agent service is ready. It relies on the fact that the service running the tuned-adm + reboot runs before the guest-agent service starts running. This assumption however is incorrect.
In order to make sure that the tuned-adm commands are run before the setup decalres the VMIs ready, moving to a new approach: polling the existence of the marker file, added only after the tuned-adm is properly configured.
This PR introduces this new approach, using guest-agent-ping probe in order to wait for the VMI to be ready.
Additionally, it changes the Setup so that the two VMIs are being setup and polled in parallel.

Passes e2e on a CNV4.15 cluster:
make test/e2e
podman run --rm \
           --volume /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup:/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup:Z \
           --volume /home/ralavi/.kube/sno01-cnvqe2-rdu2:/root/.kube:Z,ro \
           --workdir /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup \
           -e KUBECONFIG=/root/.kube/kubeconfig \
           -e TEST_CHECKUP_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup:latest \
           -e TEST_NAMESPACE=dpdk-checkup-ns-1 \
           -e NETWORK_ATTACHMENT_DEFINITION_NAME=dpdk-sriovnetwork-ns-1 \
           -e TRAFFIC_GEN_CONTAINER_DISK_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup-traffic-gen:latest \
           -e VM_UNDER_TEST_CONTAINER_DISK_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup-vm:latest \
           docker.io/library/golang:1.20.12 go test ./tests/... -test.v -test.timeout=1h -ginkgo.v -ginkgo.timeout=1h
=== RUN   TestKubevirtDpdkCheckup
Running Suite: KubevirtDpdkCheckup Suite - /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests
==============================================================================================================
Random Seed:<PHONE_NUMBER>

Will run 1 of 1 specs
------------------------------
[BeforeSuite]
/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests/test_suite_test.go:56
[BeforeSuite] PASSED [0.002 seconds]
------------------------------
Execute the checkup Job should complete successfully
/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests/checkup_test.go:83
• [332.155 seconds]
------------------------------

Ran 1 of 1 Specs in 332.157 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestKubevirtDpdkCheckup (332.16s)
PASS
ok  	github.com/kiagnose/kubevirt-dpdk-checkup/tests	332.168s

logs (verbose false as it has no value for this PR):
$ oc logs -f job/dpdk-checkup
2024/01/18 20:19:11 kubevirt-dpdk-checkup starting...
2024/01/18 20:19:11 Using the following config:
2024/01/18 20:19:11 "timeout": "1h0m0s"
2024/01/18 20:19:11 "networkAttachmentDefinitionName": "dpdk-sriovnetwork-ns-1"
2024/01/18 20:19:11 "trafficGenContainerDiskImage": "quay.io/ramlavi/kubevirt-dpdk-checkup-traffic-gen:latest"
2024/01/18 20:19:11 "trafficGenTargetNodeName": ""
2024/01/18 20:19:11 "trafficGenPacketsPerSecond": "8m"
2024/01/18 20:19:11 "TrafficGenEastMacAddress": "50:db:3e:a2:cf:01"
2024/01/18 20:19:11 "TrafficGenWestMacAddress": "50:06:52:cb:dd:02"
2024/01/18 20:19:11 "vmUnderTestContainerDiskImage": "quay.io/ramlavi/kubevirt-dpdk-checkup-vm:latest"
2024/01/18 20:19:11 "vmUnderTestTargetNodeName": ""
2024/01/18 20:19:11 "VMUnderTestEastMacAddress": "60:a5:41:dd:99:01"
2024/01/18 20:19:11 "VMUnderTestWestMacAddress": "60:58:b0:c2:88:02"
2024/01/18 20:19:11 "testDuration": "1m0s"
2024/01/18 20:19:11 "portBandwidthGbps": "10"
2024/01/18 20:19:11 "verbose": false
2024/01/18 20:19:11 Creating ConfigMap "dpdk-checkup-ns-1/dpdk-traffic-gen-config-z7jg8"...
2024/01/18 20:19:11 Creating VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8"...
2024/01/18 20:19:11 Creating VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8"...
2024/01/18 20:19:11 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" first boot...
2024/01/18 20:19:11 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" first boot...
2024/01/18 20:20:21 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" had successfully booted
2024/01/18 20:20:21 Login to VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8"...
2024/01/18 20:20:31 VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" had successfully booted
2024/01/18 20:20:31 Login to VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8"...
2024/01/18 20:20:56 Performing boot for tuned-adm profile to take affect on VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8"...
{"component":"","level":"info","msg":"SoftReboot VMI","pos":"vmi.go:268","timestamp":"2024-01-18T20:20:56.329833Z"}
2024/01/18 20:20:56 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" second boot...
2024/01/18 20:20:56 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" had successfully booted
2024/01/18 20:21:00 Performing boot for tuned-adm profile to take affect on VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8"...
{"component":"","level":"info","msg":"SoftReboot VMI","pos":"vmi.go:268","timestamp":"2024-01-18T20:21:00.129203Z"}
2024/01/18 20:21:00 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" second boot...
2024/01/18 20:21:00 VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" had successfully booted
2024/01/18 20:21:00 Login to VMI under test...
2024/01/18 20:22:20 Login to traffic generator...
2024/01/18 20:22:37 Starting traffic generator Server Service...
2024/01/18 20:22:37 Waiting until traffic generator Server Service is ready...
2024/01/18 20:23:03 trex-server is now ready
2024/01/18 20:23:03 Starting testpmd in VMI...
2024/01/18 20:23:11 Clearing testpmd stats in VMI...
2024/01/18 20:23:11 Clearing Trex console stats before test...
2024/01/18 20:23:13 Running traffic for 1m0s...
2024/01/18 20:23:15 Monitoring traffic generator side drop rates every 10s during the test duration...
2024/01/18 20:24:15 finished polling for drop rates
2024/01/18 20:24:15 traffic Generator Max Drop Rate: 0.000000Bps
2024/01/18 20:24:19 traffic Generator port 0 Packet output errors: 0
2024/01/18 20:24:19 traffic Generator port 1 Packet output errors: 0
2024/01/18 20:24:19 traffic Generator packet sent via port 0: 480000004
2024/01/18 20:24:19 get testpmd stats in VM-Under-Test...
2024/01/18 20:24:19 VMI-Under-Test's side packets Dropped: Rx: 0; TX: 0
2024/01/18 20:24:19 VMI-Under-Test's side test packets received (including dropped, excluding non-related packets): 480000004
2024/01/18 20:24:19 Trying to delete VMI: "dpdk-checkup-ns-1/vmi-under-test-z7jg8"
2024/01/18 20:24:19 Trying to delete VMI: "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8"
2024/01/18 20:24:19 Deleting ConfigMap "dpdk-checkup-ns-1/dpdk-traffic-gen-config-z7jg8"...
2024/01/18 20:24:19 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" to be deleted...
2024/01/18 20:24:34 VMI "dpdk-checkup-ns-1/vmi-under-test-z7jg8" was deleted successfully
2024/01/18 20:24:34 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" to be deleted...
2024/01/18 20:24:34 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-z7jg8" was deleted successfully

We had an offline discussion:

We are not interested in making the setup part more complex than it has to be.
We are not interested in logging in to the serial console from Checkup.Setup().
It was raised that we could try to explore the KubeVirt readiness probes.
The new custom service introduced by #215 could potentially be removed, and its content could be moved to cloud-init.

Passes e2e on a CNV4.15 cluster:
make test/e2e
podman run --rm \
           --volume /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup:/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup:Z \
           --volume /home/ralavi/.kube/sno01-cnvqe2-rdu2:/root/.kube:Z,ro \
           --workdir /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup \
           -e KUBECONFIG=/root/.kube/kubeconfig \
           -e TEST_CHECKUP_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup:latest \
           -e TEST_NAMESPACE=dpdk-checkup-ns-1 \
           -e NETWORK_ATTACHMENT_DEFINITION_NAME=dpdk-sriovnetwork-ns-1 \
           -e TRAFFIC_GEN_CONTAINER_DISK_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup-traffic-gen:latest \
           -e VM_UNDER_TEST_CONTAINER_DISK_IMAGE=quay.io/ramlavi/kubevirt-dpdk-checkup-vm:latest \
           docker.io/library/golang:1.20.12 go test ./tests/... -test.v -test.timeout=1h -ginkgo.v -ginkgo.timeout=1h
=== RUN   TestKubevirtDpdkCheckup
Running Suite: KubevirtDpdkCheckup Suite - /home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests
==============================================================================================================
Random Seed:<PHONE_NUMBER>

Will run 1 of 1 specs
------------------------------
[BeforeSuite]
/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests/test_suite_test.go:56
[BeforeSuite] PASSED [0.002 seconds]
------------------------------
Execute the checkup Job should complete successfully
/home/ralavi/go/src/github.com/kiagnose/kubevirt-dpdk-checkup/tests/checkup_test.go:83
• [315.344 seconds]
------------------------------

Ran 1 of 1 Specs in 315.346 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestKubevirtDpdkCheckup (315.35s)
PASS

logs (verbose false as it has no value for this PR):
2024/01/24 12:55:25 kubevirt-dpdk-checkup starting...
2024/01/24 12:55:25 Using the following config:
2024/01/24 12:55:25 "timeout": "1h0m0s"
2024/01/24 12:55:25 "networkAttachmentDefinitionName": "dpdk-sriovnetwork-ns-1"
2024/01/24 12:55:25 "trafficGenContainerDiskImage": "quay.io/ramlavi/kubevirt-dpdk-checkup-traffic-gen:latest"
2024/01/24 12:55:25 "trafficGenTargetNodeName": ""
2024/01/24 12:55:25 "trafficGenPacketsPerSecond": "8m"
2024/01/24 12:55:25 "TrafficGenEastMacAddress": "50:dc:ef:91:3b:01"
2024/01/24 12:55:25 "TrafficGenWestMacAddress": "50:f8:c5:e3:0a:02"
2024/01/24 12:55:25 "vmUnderTestContainerDiskImage": "quay.io/ramlavi/kubevirt-dpdk-checkup-vm:latest"
2024/01/24 12:55:25 "vmUnderTestTargetNodeName": ""
2024/01/24 12:55:25 "VMUnderTestEastMacAddress": "60:15:8b:11:54:01"
2024/01/24 12:55:25 "VMUnderTestWestMacAddress": "60:f6:f1:12:aa:02"
2024/01/24 12:55:25 "testDuration": "1m0s"
2024/01/24 12:55:25 "portBandwidthGbps": "10"
2024/01/24 12:55:25 "verbose": false
2024/01/24 12:55:25 Creating ConfigMap "dpdk-checkup-ns-1/dpdk-traffic-gen-config-pwr7x"...
2024/01/24 12:55:25 Creating ConfigMap "dpdk-checkup-ns-1/vmi-under-test-config-pwr7x"...
2024/01/24 12:55:25 Creating VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x"...
2024/01/24 12:55:25 Creating VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x"...
2024/01/24 12:55:25 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" to boot...
2024/01/24 12:55:25 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" to boot...
2024/01/24 12:56:35 VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" had successfully booted
2024/01/24 12:56:35 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" ready condition...
2024/01/24 12:56:40 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" had successfully booted
2024/01/24 12:56:40 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" ready condition...
2024/01/24 12:57:10 VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" has successfully reached ready condition
2024/01/24 12:57:10 Performing boot for tuned-adm profile to take affect on VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x"...
{"component":"","level":"info","msg":"SoftReboot VMI","pos":"vmi.go:268","timestamp":"2024-01-24T12:57:10.802933Z"}
2024/01/24 12:57:10 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" has successfully reached ready condition
2024/01/24 12:57:10 Performing boot for tuned-adm profile to take affect on VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x"...
{"component":"","level":"info","msg":"SoftReboot VMI","pos":"vmi.go:268","timestamp":"2024-01-24T12:57:10.830319Z"}
2024/01/24 12:57:11 Login to VMI under test...
2024/01/24 12:58:22 Login to traffic generator...
2024/01/24 12:58:34 Starting traffic generator Server Service...
2024/01/24 12:58:34 Waiting until traffic generator Server Service is ready...
2024/01/24 12:59:00 trex-server is now ready
2024/01/24 12:59:00 Starting testpmd in VMI...
2024/01/24 12:59:05 Clearing testpmd stats in VMI...
2024/01/24 12:59:05 Clearing Trex console stats before test...
2024/01/24 12:59:07 Running traffic for 1m0s...
2024/01/24 12:59:07 Monitoring traffic generator side drop rates every 10s during the test duration...
2024/01/24 13:00:07 finished polling for drop rates
2024/01/24 13:00:07 traffic Generator Max Drop Rate: 0.000000Bps
2024/01/24 13:00:12 traffic Generator port 0 Packet output errors: 0
2024/01/24 13:00:12 traffic Generator port 1 Packet output errors: 0
2024/01/24 13:00:12 traffic Generator packet sent via port 0: 480000004
2024/01/24 13:00:12 get testpmd stats in VM-Under-Test...
2024/01/24 13:00:14 VMI-Under-Test's side packets Dropped: Rx: 0; TX: 0
2024/01/24 13:00:14 VMI-Under-Test's side test packets received (including dropped, excluding non-related packets): 480000004
2024/01/24 13:00:14 Trying to delete VMI: "dpdk-checkup-ns-1/vmi-under-test-pwr7x"
2024/01/24 13:00:14 Trying to delete VMI: "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x"
2024/01/24 13:00:14 Deleting ConfigMap "dpdk-checkup-ns-1/dpdk-traffic-gen-config-pwr7x"...
2024/01/24 13:00:14 Deleting ConfigMap "dpdk-checkup-ns-1/vmi-under-test-config-pwr7x"...
2024/01/24 13:00:14 Waiting for VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" to be deleted...
2024/01/24 13:00:29 VMI "dpdk-checkup-ns-1/vmi-under-test-pwr7x" was deleted successfully
2024/01/24 13:00:29 Waiting for VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" to be deleted...
2024/01/24 13:00:29 VMI "dpdk-checkup-ns-1/dpdk-traffic-gen-pwr7x" was deleted successfully

broke this PR into multiple PRs #218, #219, #220, #221, #223, #224. Closing this PR


Cassandra Ticket Registry

@mmoayyed could you please help me here with the missing dependency?
Also do not forget to review the expirationCalculation.

Sure. Will do. I'll try to get to this before this Friday.

I am not sure I see a missing dependency. Failures are styling-related? More to come shortly.

Hi @mmoayyed, any news here?

I did respond a while back that I think the build failures are not dependency related. They seem like styling issues. We still need to look into the log4j dependency issue nonetheless as well as the dynamic creation of the schema.

You can see the failures at the bottom of this page here https://travis-ci.org/apereo/cas/builds/243155462?utm_source=github_status&utm_medium=notification

That's what I meant, could you please look at the remaining bits shortly?
I'll push a fix for the checkstyle errors today

Sure.

I made a number of suggestions. Sorry about the noise.
I recommend that you:

Close this pull request
Merge with master
Handle/review the comments posted here
Post a fresh PR for us to continue reviewing and improving.

As always, thanks.


Show current month full  name in the datepicker header

No option to customize the month name (min, short and full) in the header of datepicker

Yes, I suggest you to fork one and implement it by yourself.


Update privacy policy & h2/h3 tag readability

This PR updates the Privacy Policy page and increases the size of h2 tags for better outline readability.
Addresses #350 and #377.
These changes can be previewed here: https://critzo.github.io/m-lab.github.io/privacy/

This change is

One comment re: Updated Date, but LGTM.

@georgiamoon I wondered about leaving that in. The draft document did not include it, so I removed. I agree though, we should keep it.

@georgiamoon updated. PTAL?


Question: Unable to access elasticsearch container using cerebro container OR reg install

I am running the graylog stack as well as Cerebro as containers on Ubuntu server. I have explicitly exposed the ES container port 9200 to the host. I have set the Cerebro container web gui port to 9100 (as graylog is 9000 as well).
I can go to the Cerebro web gui port (<IP_ADDRESS>:9100) just fine. As for attaching to the node if I enter http://localhost:9200 the connection can't be made (container). If I go to http://<IP_ADDRESS>:9200 it says that it is trying to connect, but never does.
Is there a setting in the container that need to be changed so that this can work with ElasticSearch being run in a container?
If I d/l the repo for the latest version, and execute it with "./cerebro -Dhttp.port=9100 -Dhttp.address=<IP_ADDRESS>" I can access the web page, as well as enter the node (http://localhost:9200), however once in the cerebro page it doesn't have any data (and there is a red warning box saying so).
What am I doing incorrectly?
Thank you

Created a new setup, and new information for Cerebro response.


"Racer returned a non-zero exit status" doesn't show racer failure message

I keep getting "Racer returned a non-zero exit status: 1" messages. Obviously, the problem is my Racer install, not this plugin, but Racer works fine from the command line. Since this message doesn't display the message Racer failed with, it's difficult to figure out what's going on. Is there a way to get Racer failure messages out of the plugin?

+1

I too have run into this problem. I initially thought that my RUST_SRC_PATH was not configured, and it wasn't, but fixing that didn't stop the errors. I restarted Atom and that did not fix it either.

Can confirm this on my end as well.

Same here.

Has anyone been able to replicate the issue/figure out what causes it? It seems to be random for me.

+1

+1

Restart the Atom, it can be used

it's unfortunate but I'm not using either Rust or Atom anymore so it is difficult for me to find and fix these types of issues. I'd happily take a pull request though.

Okay, I went and made a quick fork; it now caches the last message that went to stderr and adds that to the message in the alert when it receives a non-zero exit code.
If anybody wants to have a look at it, I'd appreciate a quick sanity check before I open a PR; I have basically no experience with CoffeeScript whatsoever.

@hawkw looks fine, except I had a question about if you meant return instead of preturn ?

Yeah, that was a typo, I've since fixed it.

Hopefully 3f5e66a387564d619356db364329569b7a2a4f43 will help some folks figure out what errors they're having.

yeah I'm not sure if there's anything left to do in this particular issue. Let's close it and if people encounter more specific errors they can open a new issue.

I ran into the same problem. I have all pereferences configured but I get only keyword autocomplete from 'language-rust' plugin.


Schema Protraction Does not work when a sub-entity is selected

Version: (e.g. 3.4.7)
Module: (e.g. quill-sql)
Database: (e.g. ALL)
  val ctx = new SqlMirrorContext(PostgresDialect, Literal)
import ctx._
case class Emb(name: String) extends Embedded
case class Parent(id: Int, emb: Emb)

implicit val parentMeta = schemaMeta[Parent]("Parent", _.emb.name -> "theName")

val q = quote { query[Parent].map(p => p.emb).distinct.map(e => (e.name)) }
run(q)
// SELECT p.embname FROM (SELECT DISTINCT emb.name AS embname FROM Parent p) AS p
// where as it should be "p.embtheName" and "emb.theName as embtheName"

Workaround
Do not select sub-entities from a super-entity until the final point in the query.
@getquill/maintainers

This is happening because EntitySchema needs to be munged around into a auto-genereated EntitySchema("anonymous-entity", _.name -> "theName").


Import mutations.

No significant performance differences

No significant performance differences

No significant performance differences

@y-zeng: you'll need this first.

WARNING: You are making changes in the Bazel subdirectory. Please get explicit approval from @nicolasnoble before merging.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[qps] No significant performance differences

Is this still needed?

@ctiller: yes.

Please address @y-zeng's comment

Yep, done.

All green, changed requested applied, merging.


Switch to immersive reader in Edge, Japanese and English alternate

The comments below were machine-translated
@cweuphoria commented on Thu May 28 2020
When you switch to immersive reader in Edge, Japanese and English are mixed alternately.

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: cf328b1f-6bc5-dff2-619f-82b95030c3cf
Version Independent ID: 4c7bd8b7-5ebb-5b1e-010b-2acd7fdcec0f
Content: Azure IoT 参照アーキテクチャ - Azure Reference Architectures
Content Source: docs/reference-architectures/iot.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @MikeWasson
Microsoft Alias: pnp

@srvbpigh commented on Fri May 29 2020
Hello, @cweuphoria
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#228620

Thank you for taking care of this.  Just a side note to the issue itself, it might be smarter not to cross out to change the subject as users may feel disrespected reporting with their local languages.  Please note that the reporting form presented was in their languages.

Thank you for submitting this.
We're tracking this issue internally and have it on our backlog to review.


Add an example of using dump()

The best way to make this nice function easily discoverable :)

@nicolas-grekas, do you mean the Twig's dump function: http://twig.sensiolabs.org/doc/functions/dump.html?

@voronkovich sort of - but in the Symfony Framework, you can use dump() in php code as well - it's from the VarDumper component. That's what Nicolas is talking about here:
dump($someVar);

@weaverryan, thanks for the explanation! I think we could just dump a list of posts to the web toolbar in a homepage's controller and add a comment explaining this feature


YT Music - Artist/SongTitle Not Correct

OS:
MacOS Version: 10.12.6
GPMDP Version:
Version 4.6.0 (4.6.0)
Issue Descriptions:
When listening to a song from a list, in the title bar of the application.
It appears that the song title is correct for the current song, however the artist is selecting the name from the previous one in the list.
See attached screen shot for example

Ah damn @jostrander sorry about that.
I looked in the Issues and didnt even notice this one.
Glad someone else found it already.


[web] Golden "canvaskit_picture_texture_toimage" isn't uploaded to Gold

For some reason, the following golden isn't uploaded to Gold:
https://github.com/flutter/engine/blob/02a379db1d384cc108d0dad295504456a01eb6bd/lib/web_ui/test/canvaskit/image_golden_test.dart#L781-L784
The test is passing, but the image is no where to be found on Gold.

Making it a P2 because this may apply to other goldens. We may be missing some important golden tests.

I'll be taking a look at this as I get goldens up and running with the Skwasm renderer.


[Message] icons are differently sized when the message text is longer

Fiddle here: http://jsfiddle.net/6zyornbb/
With "differently sized" I don't mean visually, but something is clearly wrong because the text that comes after it is very close to the icon, and when inspecting the element I found no difference except the size of the icons.

It looks like this might be resolved by changing icon flex to flex: 0 0 auto;
I'll investigate

Fixed in 2.0.5


Add BREAK command, useful for CISCO router to break into rommon

Hi,
I work with Cisco routers. When I would like to break the boot process and switch to rommon mode, I need to send BREAK signal on the serial line. This command is missing in node-serialport, so I added it.
Kind Regards,

Heh, Break was in my commit you added yesterday :)
On Fri, Mar 6, 2015 at 7:52 AM, Chris Williams<EMAIL_ADDRESS>wrote:

Merged #476 https://github.com/voodootikigod/node-serialport/pull/476.
—
Reply to this email directly or view it on GitHub
https://github.com/voodootikigod/node-serialport/pull/476#event-247538991
.


[WIP] Feat(CompilerBase-Error): Add 'One-Sentence', text rendering and error handler to CompilerError.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix https://github.com/KusionStack/KCLVM/issues/115
2. What is the scope of this PR (e.g. component or file name):
kclvm/compiler_base
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

In /kclvm/compiler_base/diagnostic/, the basic structure of One-Sentence is implemented in compiler-base-diagnostic, which includes 'Pendant', 'Sentence' and 'Diagnostic'.
In /kclvm/compiler_base/style/, the basic structure of text-rendering is implemented in compiler-base-style, which includes 'Style', and 'StyleBuffer'.
In /kclvm/compiler_base/macros/, Macro attributes 'DiagnosticBuilderMacro' is created to support generation of 'Diagnostic' from 'error/warning structs'.

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

The unit test cases in
/kclvm/compiler_base/diagnostic/src/tests.rs
/kclvm/compiler_base/style/src/tests.rs
6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 58.919%

Totals

Change from base Build<PHONE_NUMBER>:
-0.6%

Covered Lines:
21295

Relevant Lines:
36143

💛  - Coveralls

Delete KCL related content in CompilerBase, considering generality

Important things:

All error submodules should belong to the compiler-base-error crate.
Need to describe how to use Handler, how to define user own errors, and what the default errors are in lib.rs of compiler-base-error crate.

Split large WIP PRs into smaller ones


Current price for opened positions?

After buy script could check current price. I would not have to use other tools then your sheet if it had these features.
And if it was still showing the moment of purchase and sale on the chart, then it would be a cosmos at all :)
https://jbuty.com/how-to-get-crypto-currencies-rates-and-more-in-google-sheet-1a57e571bc14

Just considering how's best to implement this... The issue I see is that it would need to be periodically updated to be useful. I can either trigger it from google sheet opening, or periodically. If I do it periodically it calls the function every x seconds 24/7 regardless of whether the sheet is open or not and I'll just be spamming the API...


silder disappear on IOS device.

Hi,
I am using swiper.js to implement coverflow effect. slider working fine in web and android devices but in IOS device slider disappear on the first slide. please help me..
here is the js code.
HTML  I have use the same as mentioned in the swiper js document.
var swiper = new Swiper('.swiper-container', {
    effect: 'coverflow',
    loop: true,
    centeredSlides: true,
    slidesPerView: 4,
    initialSlide: 0,

    coverflowEffect: {
      rotate: 0,
      stretch: 0,
      depth: 200,
      modifier: 1,
      slideShadows: true,
    },

    autoplay: {
      delay: 1500,
      disableOnInteraction: false,
    },
    pagination: {
      el: '.swiper-pagination',
      clickable: true,
    },
    navigation: {
      nextEl: '.swiper-button-next',
      prevEl: '.swiper-button-prev',
    },
    breakpoints: {
      320: {
        effect: 'fade',
        slidesPerView: 1,
        fadeEffect: {
          crossFade: true,
          slideShadows: false,
        },

      },
      480: {
        effect: 'fade',
        slidesPerView: 1,
        fadeEffect: {
          crossFade: true,
          slideShadows: false,
        },
      },
      640: {
        slidesPerView: 2,
      },
      1000: {
        slidesPerView: 3,
      },
      1250: {
        slidesPerView: 4,
      }

    }

  });

Hi,
I also have a problem with IOS. Swiper doesn't work.
I can see navigation arrows, but nothing happen when I click on them and pagination is just gone.
I can only see first slide, but can't see the others.
Thank you

I have the same issue.
I am using swiper on my cordova app, and it really works fine on android but on ios it will blink for the first second of scrolling the items to the left.
I must tell that i am using RTL slider if that is relevant.


Docs: Remove typo

The flag -n <name> is not needed in the docs

 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.

Asking @VineethReddy02  and @paulfantom to review instead


Anchor/Querystring value not persisting?

We're trying to create navigation items that include links to anchors on various pages.  However, none of the links are reflecting the anchors we're specifying.  When we reload the page in the back office where we're setting the links the Anchor field is blank (even though Save and Publish was successful).  See attached files: the first shows the setting we're trying to save.  The second is shows the blank field after reloading the page.

We have the same issue since upgrading from v2 to v4. Even if you directly append #anchor-name to the path in the Link field it gets removed. There is no way to add an anchor - a major problem for us.

Hey,
This is still an issue for me. Have installed the package v4.1.0 on Umbraco 13.4.1.
@callumbwhyte The package works like a treat, easy and simple implementation. Well done!
Would definitely want to get this resolved as its one of the major issues currently. Can I please ask if you're already working on it or its in your pipeline? When can be expect the next release please?
Thanks


Add-on breaks quite often.

Hello, I find this add-on very useful and I appreciate the work you are doing. I have this issue that seems to pop up quite often, where the Add-on timeouts during sampling and even stop working after it has been working for a while. I use the JBD-SP16S020-L8S
Paste log output between BEGIN and END:
BEGIN
21:06:12 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_DD_6D_73_D1_05_01): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -40)>}, []]
21:06:12 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -64)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -47)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -58)>}, []]
21:06:13 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -40)>}, []]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_C4_82_E1_B4_41_AF): ['org.bluez.Device1', {}, ['RSSI']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved (/): ['/org/bluez/hci0/dev_C4_82_E1_B4_41_AF', ['org.freedesktop.DBus.Properties', 'org.freedesktop.DBus.Introspectable', 'org.bluez.Device1']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {}, ['RSSI']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved (/): ['/org/bluez/hci0/dev_00_DE_B5_40_E1_29', ['org.freedesktop.DBus.Properties', 'org.freedesktop.DBus.Introspectable', 'org.bluez.Device1']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_DD_6D_73_D1_05_01): ['org.bluez.Device1', {}, ['RSSI']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesRemoved (/): ['/org/bluez/hci0/dev_DD_6D_73_D1_05_01', ['org.freedesktop.DBus.Properties', 'org.freedesktop.DBus.Introspectable', 'org.bluez.Device1']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {}, ['RSSI']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {}, ['TxPower', 'RSSI']]
21:06:14 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0): ['org.bluez.Adapter1', {'Discovering': <dbus_fast.signature.Variant ('b', False)>}, []]
21:06:14 INFO [bt] BT 6C:EE:61:81:05:8F          6C-EE-61-81-05-8F
21:06:14 INFO [bt] BT C4:82:E1:B4:41:AF                         TY
21:06:14 INFO [bt] BT 00:DE:B5:40:E1:29          00-DE-B5-40-E1-29
21:06:14 INFO [bt] BT CB:4E:FC:7C:48:83          CB-4E-FC-7C-48-83
21:06:14 INFO [bt] BT DD:6D:73:D1:05:01          DD-6D-73-D1-05-01
21:06:14 ERROR [sampling] JbdBt(70:3E:97:EB:2E:B7,battery1) device not found, retry in 7 seconds
21:06:15 DEBUG [sampling] retry in 7 sec
21:06:20 DEBUG [sampling] retry in 2 sec
21:06:25 INFO [sampling] connecting bms JbdBt(70:3E:97:EB:2E:B7,battery1)
21:06:25 INFO [bt] connecting battery1 (70:3E:97:EB:2E:B7) adapter=default timeout=20
21:06:25 DEBUG [client] Connecting to device @ 70:3E:97:EB:2E:B7
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0): ['org.bluez.Adapter1', {'Discovering': <dbus_fast.signature.Variant ('b', True)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_00_DE_B5_40_E1_29', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_fast.signature.Variant ('s', 00:DE:B5:40:E1:29)>, 'AddressType': <dbus_fast.signature.Variant ('s', random)>, 'Alias': <dbus_fast.signature.Variant ('s', 00-DE-B5-40-E1-29)>, 'Paired': <dbus_fast.signature.Variant ('b', False)>, 'Bonded': <dbus_fast.signature.Variant ('b', False)>, 'Trusted': <dbus_fast.signature.Variant ('b', False)>, 'Blocked': <dbus_fast.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_fast.signature.Variant ('b', False)>, 'RSSI': <dbus_fast.signature.Variant ('n', -68)>, 'Connected': <dbus_fast.signature.Variant ('b', False)>, 'UUIDs': <dbus_fast.signature.Variant ('as', [])>, 'Adapter': <dbus_fast.signature.Variant ('o', /org/bluez/hci0)>, 'ManufacturerData': <dbus_fast.signature.Variant ('a{qv}', {6: <dbus_fast.signature.Variant ('ay', bytearray(b'\x01\t "\x81\xcf\xeb\xfe\xbc\xd3k\x82\x07<\xd9!Y\xa0\x91m\xb0\xb2\xb6\x8e$\xdd\x89'))>})>, 'ServicesResolved': <dbus_fast.signature.Variant ('b', False)>, 'AdvertisingFlags': <dbus_fast.signature.Variant ('ay', bytearray(b'\x00'))>}, 'org.freedesktop.DBus.Properties': {}}]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -67)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>, 'TxPower': <dbus_fast.signature.Variant ('n', 7)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -67)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -40)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:25 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -59)>}, []]
21:06:26 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:26 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -53)>}, []]
21:06:26 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -40)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_C4_82_E1_B4_41_AF', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_fast.signature.Variant ('s', C4:82:E1:B4:41:AF)>, 'AddressType': <dbus_fast.signature.Variant ('s', public)>, 'Name': <dbus_fast.signature.Variant ('s', TY)>, 'Alias': <dbus_fast.signature.Variant ('s', TY)>, 'Paired': <dbus_fast.signature.Variant ('b', False)>, 'Bonded': <dbus_fast.signature.Variant ('b', False)>, 'Trusted': <dbus_fast.signature.Variant ('b', False)>, 'Blocked': <dbus_fast.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_fast.signature.Variant ('b', False)>, 'RSSI': <dbus_fast.signature.Variant ('n', -47)>, 'Connected': <dbus_fast.signature.Variant ('b', False)>, 'UUIDs': <dbus_fast.signature.Variant ('as', [])>, 'Adapter': <dbus_fast.signature.Variant ('o', /org/bluez/hci0)>, 'ServicesResolved': <dbus_fast.signature.Variant ('b', False)>, 'AdvertisingFlags': <dbus_fast.signature.Variant ('ay', bytearray(b'\x00'))>}, 'org.freedesktop.DBus.Properties': {}}]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -64)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -39)>}, []]
21:06:27 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>}, []]
21:06:28 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -39)>}, []]
21:06:28 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>}, []]
21:06:28 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:28 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -45)>}, []]
21:06:29 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:29 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -61)>}, []]
21:06:29 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -40)>}, []]
21:06:29 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -51)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -45)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -58)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_C4_82_E1_B4_41_AF): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -47)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -47)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_DD_6D_73_D1_05_01', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_fast.signature.Variant ('s', DD:6D:73:D1:05:01)>, 'AddressType': <dbus_fast.signature.Variant ('s', random)>, 'Alias': <dbus_fast.signature.Variant ('s', DD-6D-73-D1-05-01)>, 'Paired': <dbus_fast.signature.Variant ('b', False)>, 'Bonded': <dbus_fast.signature.Variant ('b', False)>, 'Trusted': <dbus_fast.signature.Variant ('b', False)>, 'Blocked': <dbus_fast.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_fast.signature.Variant ('b', False)>, 'RSSI': <dbus_fast.signature.Variant ('n', -46)>, 'Connected': <dbus_fast.signature.Variant ('b', False)>, 'UUIDs': <dbus_fast.signature.Variant ('as', [])>, 'Adapter': <dbus_fast.signature.Variant ('o', /org/bluez/hci0)>, 'ManufacturerData': <dbus_fast.signature.Variant ('a{qv}', {76: <dbus_fast.signature.Variant ('ay', bytearray(b'\x12\x02\x00\x01'))>})>, 'ServicesResolved': <dbus_fast.signature.Variant ('b', False)>, 'AdvertisingFlags': <dbus_fast.signature.Variant ('ay', bytearray(b'\x00'))>}, 'org.freedesktop.DBus.Properties': {}}]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -66)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:30 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -60)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -68)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:31 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -53)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -53)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>}, []]
21:06:32 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -59)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_C4_82_E1_B4_41_AF): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -45)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -60)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -75)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -69)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded (/): ['/org/bluez/hci0/dev_E0_15_D5_68_EC_D2', {'org.freedesktop.DBus.Introspectable': {}, 'org.bluez.Device1': {'Address': <dbus_fast.signature.Variant ('s', E0:15:D5:68:EC:D2)>, 'AddressType': <dbus_fast.signature.Variant ('s', random)>, 'Alias': <dbus_fast.signature.Variant ('s', E0-15-D5-68-EC-D2)>, 'Paired': <dbus_fast.signature.Variant ('b', False)>, 'Bonded': <dbus_fast.signature.Variant ('b', False)>, 'Trusted': <dbus_fast.signature.Variant ('b', False)>, 'Blocked': <dbus_fast.signature.Variant ('b', False)>, 'LegacyPairing': <dbus_fast.signature.Variant ('b', False)>, 'RSSI': <dbus_fast.signature.Variant ('n', -57)>, 'Connected': <dbus_fast.signature.Variant ('b', False)>, 'UUIDs': <dbus_fast.signature.Variant ('as', [])>, 'Adapter': <dbus_fast.signature.Variant ('o', /org/bluez/hci0)>, 'ManufacturerData': <dbus_fast.signature.Variant ('a{qv}', {76: <dbus_fast.signature.Variant ('ay', bytearray(b'\x12\x02\x00\x02'))>})>, 'ServicesResolved': <dbus_fast.signature.Variant ('b', False)>, 'AdvertisingFlags': <dbus_fast.signature.Variant ('ay', bytearray(b'\x00'))>}, 'org.freedesktop.DBus.Properties': {}}]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -47)>}, []]
21:06:33 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -53)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -71)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -53)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_DD_6D_73_D1_05_01): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -67)>}, []]
21:06:34 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -54)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -46)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -55)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_CB_4E_FC_7C_48_83): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -60)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_00_DE_B5_40_E1_29): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -57)>}, []]
21:06:35 DEBUG [manager] received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0/dev_6C_EE_61_81_05_8F): ['org.bluez.Device1', {'RSSI': <dbus_fast.signature.Variant ('n', -52)>}, []]
END

Without Verbose
File "/app/bmslib/bt.py", line 237, in connect
    await self._connect_client(timeout=timeout)
  File "/app/bmslib/bt.py", line 186, in _connect_client
    await asyncio.wait_for(self.client.connect(timeout=timeout), timeout=timeout + 1)
  File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/__init__.py", line 531, in connect
    return await self._backend.connect(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 141, in connect
    async with async_timeout(timeout):
  File "/usr/lib/python3.11/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
21:40:49 INFO [sampling] Bleak version 0.20.2
21:40:49 INFO [sampling] connecting bms JbdBt(70:3E:97:EB:2E:B7,battery1)
21:41:09 ERROR [sampling] battery1 error (#2): <class 'TimeoutError'>
Traceback (most recent call last):
  File "/app/venv/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 204, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/dbus_fast/aio/message_bus.py", line 390, in call
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/bmslib/sampling.py", line 155, in __call__
    s = await self._sample_inner()
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/bmslib/sampling.py", line 227, in _sample_inner
    async with bms:
  File "/app/bmslib/bt.py", line 345, in __aenter__
    await self.connect()
  File "/app/bmslib/models/jbd.py", line 53, in connect
    await super().connect(**kwargs)
  File "/app/bmslib/bt.py", line 237, in connect
    await self._connect_client(timeout=timeout)
  File "/app/bmslib/bt.py", line 186, in _connect_client
    await asyncio.wait_for(self.client.connect(timeout=timeout), timeout=timeout + 1)
  File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/__init__.py", line 531, in connect
    return await self._backend.connect(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 141, in connect
    async with async_timeout(timeout):
  File "/usr/lib/python3.11/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
21:41:09 INFO [sampling] Bleak version 0.20.2
21:41:09 ERROR [main] 1 exceptions occurred fetching BMSs
21:41:09 ERROR [main] Error (num 1, max 200) reading BMS:
21:41:09 ERROR [main] Stack: Traceback (most recent call last):
  File "/app/venv/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 204, in connect
    reply = await self._bus.call(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/dbus_fast/aio/message_bus.py", line 390, in call
    await future
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/main.py", line 36, in fetch_loop
    if await fn():
       ^^^^^^^^^^
  File "/app/main.py", line 319, in fn
    raise exceptions[0]
  File "/app/main.py", line 314, in fn
    await t()
  File "/app/bmslib/sampling.py", line 155, in __call__
    s = await self._sample_inner()
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/bmslib/sampling.py", line 227, in _sample_inner
    async with bms:
  File "/app/bmslib/bt.py", line 345, in __aenter__
    await self.connect()
  File "/app/bmslib/models/jbd.py", line 53, in connect
    await super().connect(**kwargs)
  File "/app/bmslib/bt.py", line 237, in connect
    await self._connect_client(timeout=timeout)
  File "/app/bmslib/bt.py", line 186, in _connect_client
    await asyncio.wait_for(self.client.connect(timeout=timeout), timeout=timeout + 1)
  File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
    return fut.result()
           ^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/__init__.py", line 531, in connect
    return await self._backend.connect(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/venv/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 141, in connect
    async with async_timeout(timeout):
  File "/usr/lib/python3.11/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

21:41:10 INFO [sampling] connecting bms JbdBt(70:3E:97:EB:2E:B7,battery1)


[Engineering Improvement] Updating testEnvironment and keyvalues from connection string

This change adds all the necessary keyvalue pairs for connection string for running HttpRecorder tests.
Simplifies existing connection string the way it is initialized in TestEnvironment.
This checkin only makes all the non-essential fields/properties to either internal or private to avoid any leakage.
This check-in is to figure out if we break any existing test cases.

Can one of the admins verify this patch?

Hi @shahabhijeet, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (abhishah). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci add to whitelist

using Microsoft.Rest.ClientRuntime.Azure.TestFramework;

License header missing.

Refers to: src/TestFramework/Microsoft.Rest.ClientRuntime.Azure.TestFramework/ExtMethods.cs:1 in 07f3b86. [](commit_id = 07f3b86d44b65921acca4a73233346ce3667cd3e, deletion_comment = False)

namespace TestFramework.Tests.TestEnvironment

Missing license header

Refers to: src/TestFramework/TestFramework.Tests/TestEnvironment/ConnectionStringParseTests.cs:1 in 07f3b86. [](commit_id = 07f3b86d44b65921acca4a73233346ce3667cd3e, deletion_comment = False)

namespace TestFramework.Tests.TestEnvironment

license header.

Refers to: src/TestFramework/TestFramework.Tests/TestEnvironment/TestEnvironmentTests.cs:1 in 07f3b86. [](commit_id = 07f3b86d44b65921acca4a73233346ce3667cd3e, deletion_comment = False)

@shahabhijeet
please remove commented code because I'm not able to focus on the changes since on the website/codeflow comments are not grayed

:shipit:

@shahabhijeet you will need to bump up package version to be able to publish new test library to nuget.org.

@abhijeet A few comments.  Mainly these are in three categories:
(1) We can simply use a case-insensitive dictionary for parsing the connection strings, rather than doing so much case manipiulation
(2) It is a little strange to have blocking calls like authentication occurring inside constructors - please leave authentication to the TestEnvironmentFactory static factory methods.  It also seems like the logic for mapping a connection string into a TestEnvironment should be in one place.
(3) If there is a simpler representation than having a ConnectionStringFields class, we should use it  - if it's more convenient to have this class as Dictionary<string, list>, or as a list of key values, and we're not getting any value out of it being a class, then we should use the more convenient representation.  It seems like we're using reflection because the class is an inconvenient representation for the information we get out of it.


Compiling error on Raspberry Pi 5:

error:assuming signed overflow does not occur when simplifying conditional to constant [-Werror=strict-overflow]
Platform:Raspberry Pi 5
Operating System:Linux raspberrypi 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux
Problem description:
Hi, I got this error when compiling with command scons Werror=1 -j8 debug=0 neon=1 opencl=0 os=linux arch=armv8a build=native
In file included from /usr/include/c++/12/array:43,
                 from ./arm_compute/core/Error.h:27,
                 from ./arm_compute/core/Dimensions.h:27,
                 from ./arm_compute/core/Strides.h:27,
                 from ./arm_compute/core/CoreTypes.h:27,
                 from ./arm_compute/core/Types.h:39,
                 from ./arm_compute/core/utils/helpers/tensor_transform.h:27,
                 from src/core/utils/helpers/tensor_transform.cpp:24:
In function ‘constexpr const _Tp& std::min(const _Tp&, const _Tp&) [with _Tp = int]’,
    inlined from ‘DataType arm_compute::utility::clamp(const DataType&, const DataType&, const DataType&) [with DataType = int; RangeType = int]’ at ./arm_compute/core/utils/misc/Utility.h:106:20,
    inlined from ‘int arm_compute::helpers::tensor_transform::calculate_end_on_index(arm_compute::TensorShape, int, int, arm_compute::Coordinates, arm_compute::Coordinates, int32_t, int32_t)’ at src/core/utils/helpers/tensor_transform.cpp:120:41:
/usr/include/c++/12/bits/stl_algobase.h:235:7: error: assuming signed overflow does not occur when simplifying conditional to constant [-Werror=strict-overflow]
  235 |       if (__b < __a)
      |       ^~
cc1plus: all warnings being treated as errors
scons: *** [build/src/core/utils/helpers/tensor_transform.os] Error 1

Hi @wachhu
Could you please let us know

What version of ACL are you compiling?
What toolchain are you using? Could you please share the output of the command g++ --version or aarch64-linux-gnu-g++ --version ?

Hi @wachhu
Could you please let us know

What version of ACL are you compiling?
What toolchain are you using? Could you please share the output of the command g++ --version or aarch64-linux-gnu-g++ --version ?

Hi,  I think it's v24.02.  and the g++ version is:
aarch64-linux-gnu-g++ (Debian 12.2.0-14) 12.2.0

Hi @wachhu
Thanks for the details, the patch below fixes the problem and will be included in 24.05.
https://review.mlplatform.org/c/ml/ComputeLibrary/+/11381
Hope this helps.


Dev/mediation config

@DavidClawson work on configuration for meditation recipient.
Introduces an initialize method to the recipient module(src/modules/routing/RecipientModule.ts).

initialize is called from agent.init() after wallet, ledger, and transport are set up.
recipient.init() checks for provided configurations to automatically set up mediation at the start.

@burdettadam @DavidClawson I updated feature/mediation-rebased with the most recent changes: https://github.com/hyperledger/aries-framework-javascript/tree/feature/mediation-rebased
If you can do more smaller PRs I can make sure the branch stays up to date with changes in main. It'd rather not wait until the end to update it as this was already way too much merge conflicts. Does that sound reasonable?
So if we can use this branch from now on that would really help:
https://github.com/hyperledger/aries-framework-javascript/tree/feature/mediation-rebased


fix: Get Java from GitHub release artifacts directly

What are we solving here?

Installing Java in the Dockerfile by using Adoptium's package repositories is fragile since they've started blocking some IP addresses used by GitHub Actions runners. We see a message like this:
Failed to fetch https://packages.adoptium.net/artifactory/deb/pool/main/t/temurin-17/temurin-17-jdk_<IP_ADDRESS>.0+1_amd64.deb  403  Forbidden [IP: <IP_ADDRESS> 443]

Installing Java via apt also installs other packages like X11 libraries, that aren't really relevant to our usage of Java. Yet, these packages are present in our Docker image, and are the source of several CVEs to be reported by scanners on our Docker image.

This will give us control over trusted CA certificates, which we can now perform under $TMP, which aligns with our move towards supporting readonly root filesystem. Which is essentially not write to anything in the Docker image at runtime, except for under /tmp and /appsmith-stacks. This will help us move in that direction.

/ok-to-test

/ok-to-test


Unable to change name in new thermostat lovelace component

Home Assistant release with the issue: 0.81.0

Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Hassio

Component/platform: Lovelace/thermostat

Description of problem:
I use new lovelace thermostat component. As described in doc only entity property can be set.
Unable to set names inside gauges, all are named "Upstairs".
My climate components has my custom friendly names but lovelace doesn't use it.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
      - id: 4d2a58c1376a4954843f8edfcaee1a75  # Automatically created id
        type: horizontal-stack
        cards:
          - type: thermostat
            entity: climate.obyvak_radiator_thermostat_1
          - type: thermostat
            entity: climate.pracovna_radiator_thermostat_1
          - type: thermostat
            entity: climate.kuchyn_radiator_thermostat_1

Traceback (if applicable):

Additional information:

Same problem here - all cards have missing identity.. only solution was to downgrade HA to previous 0.80.3 version.

Will be fixed in 0.81.1

Is resolved? Can anybody confirm it?

@arsaboo already said: 0.81.1

I see no mention of the string in any of the repos that would have hardcoded it, is it a browers cache issue?
Im not using Lovelace yet, But am just throwing ideas in

No it is not cache. Refreshed page and still the same. I never had entity named "Upstairs".

This is definitely fixed in 0.81.1. Please refresh your browser cache a few times.

It looks like Docker/hass.io has a separate issue with tagging. I can now confirm @arsaboo's comment: this is fixed in 0.81.1.

Unable to install 0.81.1, update still installs something like "0.81.0.dev0". Still broken for me.

Hi
I can change name with a specific name

The fix seems to take the name of the Entity but you are still unable to use a custom name for example:
If the name of the entity is "Family Room" and the config is as follows:
`
    type: thermostat

    entity: climate.family_room

    name: Nest

`
The name will still be called "Family Room" not whatever name was specified.

Created new issue targeting custom naming: https://github.com/home-assistant/home-assistant/issues/18321

Hi, I upgraded my Hass.io to 0.82.1 and my lovelace thermostat card still says "Upstairs".

I use this configuration.
climate:

platform: generic_thermostat
name: Acuario
heater: switch.enchufe_termometro_acuario
target_sensor: sensor.temperature
ac_mode: true
max_temp: 35
target_temp: 26.2
cold_tolerance: 0.3
keep_alive:
minutes: 3
initial_operation_mode: "auto"

El mié., 21 de nov. de 2018 09:43, jorgeleitao<EMAIL_ADDRESS>escribió:

Hi, I upgraded my Hass.io to 0.82.1 and my lovelace thermostat card still
says "Upstairs".
[image: image]
https://user-images.githubusercontent.com/5114388/48841875-a7b92a80-ed8a-11e8-86df-4fd4294df9a4.png
[image: image]
https://user-images.githubusercontent.com/5114388/48841914-c15a7200-ed8a-11e8-90f5-ad6e21bc58d0.png
[image: image]
https://user-images.githubusercontent.com/5114388/48841925-ca4b4380-ed8a-11e8-93a9-bc7e72433419.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/17880#issuecomment-440649646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeVbsgFtzONoaIpU8fFKBBHAiPQ8Yomjks5uxUqMgaJpZM4X9h21
.


Resources with missing schemas not ignored

Hi!
I'm seeing some issues with -ignore-missing-schemas when supplying a JSON schema file ending with .json. There will be many custom resources that we need to be ignored, and listing them under the -skip flag would make it painful to maintain.
$ kubeconform -ignore-missing-schemas -schema-location default -schema-location "https://raw.githubusercontent.com/argoproj/argo-workflows/master/api/jsonschema/schema.json" app.yaml

app.yaml - VaultSecret sample-secret is invalid: For field (root): Must validate one and only one schema (oneOf) - For field apiVersion: apiVersion does not match: "argoproj.io/v1alpha1" - For field kind: kind does not match: "ClusterWorkflowTemplate"

Expected behavior: ignore resources where schemas could not be found.

Hi @seif-raafat ! Unfortunately  you are not correctly using -schema-location, and this being a common occurrence among users points to either a confusing parameter on my part or poor documentation :(
Could you check if this answer helps you out: https://github.com/yannh/kubeconform/issues/81 ?
All the best!

Thank you, it is working as intended now after making the suggested adjustments. I think the documentation is good, I just didn't read it correctly. Great work on the product!


Support for Python 3.11

3.11 support:
Error see below
web3.py has support https://github.com/ethereum/web3.py/issues/2704
eth_abi added support recently https://github.com/ethereum/eth-abi/pull/194
I think it was recently pre-released (https://pypi.org/project/eth-abi/#history) as 4.0, we’re curently using 3.x
I would wait until all packages have proper releases, then update our requirements. Until then use 3.10
Current error:
❯ woke --help
Traceback (most recent call last):
  File "/Users/dteiml/.local/bin/woke", line 5, in <module>
    from woke.cli.__main__ import main
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/woke/cli/__main__.py", line 20, in <module>
    from .fuzz import run_fuzz
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/woke/cli/fuzz.py", line 14, in <module>
    from woke.testing.fuzzer import fuzz
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/woke/testing/fuzzer.py", line 29, in <module>
    from woke.testing.contract import dev_interface
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/woke/testing/contract.py", line 26, in <module>
    import eth_abi
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/__init__.py", line 3, in <module>
    from eth_abi.abi import (  # NOQA
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/abi.py", line 1, in <module>
    from eth_abi.codec import (
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/codec.py", line 16, in <module>
    from eth_abi.decoding import (
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/decoding.py", line 14, in <module>
    from eth_abi.base import (
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/base.py", line 7, in <module>
    from .grammar import (
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/eth_abi/grammar.py", line 4, in <module>
    import parsimonious
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/parsimonious/__init__.py", line 9, in <module>
    from parsimonious.grammar import Grammar, TokenGrammar
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/parsimonious/grammar.py", line 14, in <module>
    from parsimonious.expressions import (Literal, Regex, Sequence, OneOf,
  File "/Users/dteiml/.local/pipx/venvs/woke/lib/python3.11/site-packages/parsimonious/expressions.py", line 9, in <module>
    from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect'<EMAIL_ADDRESS>

Done :white_check_mark:


Cilium pod hangs on alpha-2969.0.0-hvm

Description
Ciilium fails and kubernetes node is in status NotReady
Impact
Node is not usable
Environment and steps to reproduce
cilium version: quay.io/cilium/cilium:v1.9.5
kubernetes version: Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:12:29Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}
Additional information
Setup works on Flatcar-stable-2765.2.6
kubelet error message:
kubelet[13148]: E0823 11:57:14.914922   13148 pod_workers.go:190] "Error syncing pod, skipping" err="network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized" pod="kube-system/npd-v0.8.2-6zt87" podUID=44be878c-e77e-4744-873b-04c77a4e8ffb
kubelet[13148]: E0823 11:57:17.030551   13148 remote_runtime.go:116] "RunPodSandbox from runtime service failed" err="rpc error: code = InvalidArgument desc = failed to create containerd container: create container failed validation: container.Runtime.Name must be set: invalid argument"

containerd error message:
env[5605]: time="2021-08-23T13:00:26.752080774Z" level=info msg="No cni config template is specified, wait for other system components to drop the config."
env[5605]: time="2021-08-23T13:00:29.729055720Z" level=info msg="RunPodsandbox for &PodSandboxMetadata{Name:cilium-wmz87,Uid:079fbd67-21f9-41d6-b72a-294d1bde76be,Namespace:kube-system,Attempt:0,}"
env[5605]: time="2021-08-23T13:00:29.739901277Z" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:cilium-wmz87,Uid:079fbd67-21f9-41d6-b72a-294d1

Hi @pschulten, thanks for testing Alpha releases of Flatcar Container Linux ! :)
In 2969.0.0, we did an update to cgroupsv2 - see the changelog: https://kinvolk.io/flatcar-container-linux/releases/#release-2969.0.0.
You might be interested by reading this documentation: https://kinvolk.io/docs/flatcar-container-linux/latest/container-runtimes/switching-to-unified-cgroups/#kubernetes

Ciilium fails

Is Cilium the only failing deployment ?
For your information, Cilium is tested in our CI with both v1.21 and v1.22 version of Kubernetes - do you have some specific configuration in your cluster ?

Thanks. I will have a look.

Is Cilium the only failing deployment ?

It's kind of required for all other deployments (network)

do you have some specific configuration in your cluster ?

Yes, lots of. Maybe you could point me to something more specific?
Cilium setup is pretty generic: helm template of the original chart with some changes (version/secrets)
The basic setup is: terraform -> infra; terraform ignition -> OS; kubeadm join/init with systemd oneshot script

I have seen this in the past when containerd config was invalid. Are you using dockershim or containerd as CRI? You're using systemd cgroup driver for Kubernetes, correct?
Could you paste the following commands output:
systemctl status kubelet
systemctl cat containerd
systemctl status containerd
crictl info

I'm using containerd.
My tests were on a manually edited nodepool ASG of an existing (stable Flatcar). I'm going to install a new complete new cluster with 2969 and keep you posted.
I'm also going to modify the recommended cgroup settings, sorry for not reading :(

Sorry, I think I found the problem. Our containerd config.toml accidentally zeros out the 'runtime_type' field. If your deployment method supports customizing the containerd config, then you need the following entry:
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"
  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

I'll get this fixed in the closest release.

no problem. I replaced to the whole config.toml with your entry and everything works like a charm:
# crictl --runtime-endpoint unix:///run/containerd/containerd.sock ps | grep cilium
df712162e96fa       933a120da2c51       2 minutes ago        Running             cilium-operator           0                   eab24834e74af
eb479faff48c4       38d6adab1281e       2 minutes ago        Running             cilium-agent              0                   24947ba371cd2

# kubectl get no ip-10-x-x-x.eu-central-1.compute.internal -o wide --no-headers
ip-10-x-x-x.eu-central-1.compute.internal   Ready   <none>   6m55s   v1.21.1   <IP_ADDRESS>   <none>   Flatcar Container Linux by Kinvolk 2969.0.0 (Oklo)   5.10.59-flatcar   containerd://1.5.5

# cat /etc/containerd/config.toml
version = 2
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
  runtime_type = "io.containerd.runc.v2"
  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    SystemdCgroup = true

Lovely! We'll ship a fix in the next alpha minor (2969.1.0).

Thank you so much for reporting this!


Give repo its own conda recipe

Currently conda-forge is being used to build things. There's nothing wrong with that per se. But because the conda package requires post-link and pre-unlink scripts to work properly, they should be part of the source, and included here.
To that end I've pulled those scripts over and a basic conda recipe that builds the package locally. Nothing has been changed w.r.t. the current AppVeyor/Travis builds, but in theory, these should be building and testing the conda packages to fully vet the post-link/pre-unlink scripts.
Future work:

More testing in the conda build process itself
Modify appveyor and travis scripts to use the recipe

Coverage remained the same at 47.985% when pulling 8ec26ea19fb1cb0fa18d43a459348dcb23a6da17 on mcg1969:conda-recipe into f7b468090fc2f7fbf1dd56fe875f3e5c28051aa9 on Anaconda-Platform:master.

Coverage remained the same at 47.985% when pulling 8ec26ea19fb1cb0fa18d43a459348dcb23a6da17 on mcg1969:conda-recipe into f7b468090fc2f7fbf1dd56fe875f3e5c28051aa9 on Anaconda-Platform:master.

Coverage remained the same at 47.985% when pulling 8ec26ea19fb1cb0fa18d43a459348dcb23a6da17 on mcg1969:conda-recipe into f7b468090fc2f7fbf1dd56fe875f3e5c28051aa9 on Anaconda-Platform:master.

I've modified the conda recipe so that it executes all of the tests, and I've updated the AppVeyor and Travis scripts to use conda-build for the testing.

Incorporated #79 in order to get this to work, so if we merge this, #79 can be closed.

The test failures seem to be because nb_conda_kernels don't see the conda-build test environment when running its environment scan. I'm not quite sure why that is.  To rectify for now, I'm just creating an extra dummy conda environment with an R kernel so that the tests will detect it. PR #80 will ultimately fix this more completely.

OK, so the test failures were caused by the fact that conda build environments are created using the --prefix argument with an absolute path, instead of the -n argument with a simple name. This prevents the environment from being listed in the environments output by conda info --envs. This  doesn't prevent the kernels from being seen by Jupyter, because sys.prefix is one of the places it looks by default. But it does prevent it from being seen by the conda-specific kernel search specifically. The fix described above solves that problem for us.

@damianavila can you offer some feedback here? There's a lot in this code but the only functional change is the fix also addressed by #78, to support conda 4.4+. The rest of the changes make conda central to the CI process. The existing test suite has been fully preserved.

I think you meant to mention PR #79, not Issue #78 in the title, and in your last comment ?

@tjd2002 I've added a CONDA_4_4_STYLE test. Do you think that a conda-canary build itself is necessary? Since CI is not re-run unless a package is rebuilt, I don't think this is an effective place to catch breakage caused by a conda change.

LGTM! Using canary was based on @kalefranz’ suggestion to target 4.6, but the actual fixes we’re considering also work against 4.5 (I.e. use of $CONDA_EXE). Your solution is simpler and will not require any updates when 4.6 ships.

@fjcapdevila do you think you can take a look at this, or do we need to wait for @damianavila?
Note that this PR only does the following:

Implements a very simple fix for conda 4.4+, when conda is not necessarily on the PATH
Brings over the post-link and pre-unlink scripts from the conda-forge recipe
Modifies the Travis CI infrastructure to use conda build for testing
Modifies AppveyorCI similarly, but that's not active right now anyway.

The actual package builds are still being handled by conda-forge, and can be kicked off with nothing but a version bump on the feedstock.

@mcg1969 I took a quick review. I looks fine to me but I have never worked on this repo. I would wait for @damianavila in this case.

Thanks @fjcapdevila !

A couple more changes here.

I discovered in my Windows testing that nb_conda_kernels fails with conda <4.4 when installed in a non-root environment. The easiest way to fix this was to use shell=True in the subprocess call to conda info.
I've disabled NPM-based testing altogether on AppVeyor. I'm getting script errors there. Unfortunately this means that nb-conda-run isn't being exercised there. But to be fair, Windows is not being exercised at all right now on this branch (I connected my fork to AppVeyor to do this work).

I'd actually like to remove the NPM testing altogether, if I can come up with a way to do without it.

OK, then let's merge this, and then we can take a more deliberate approach to #80.


Python netifaces.interfaces() returns [Errno 22] when connected with internet on build 14965

I'm having problems with roscore returning Errno 22 on build 14965, while being connected with the internet. However, when I disable the connection, roscore runs just fine. Roscore should work on build 14965, but it doesn't.
Traceback (most recent call last):
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/init.py", line 307, in main
p.start()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/parent.py", line 279, in start
self.runner.launch()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/launch.py", line 654, in launch
self._setup()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/launch.py", line 630, in _setup
self._launch_master()
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/launch.py", line 394, in _launch_master
validate_master_launch(m, self.is_core, self.is_rostest)
File "/opt/ros/indigo/lib/python2.7/dist-packages/roslaunch/launch.py", line 83, in validate_master_launch
if not rosgraph.network.is_local_address(m.get_host()):
File "/opt/ros/indigo/lib/python2.7/dist-packages/rosgraph/network.py", line 176, in is_local_address
local_addresses = ['localhost'] + get_local_addresses()
File "/opt/ros/indigo/lib/python2.7/dist-packages/rosgraph/network.py", line 219, in get_local_addresses
for iface in netifaces.interfaces():
OSError: [Errno 22] Invalid argument
My Windows build is Windows 10 Pro Insider Preview Build 14965

This is a known issue related to ip addr not working.  One way to fix this is to use netsh in windows to disable the teredo tunneling interface.

Just FYI that the teredo issue is fixed and is making its way to the insider build. Thanks @JasonLinMS, who can also provide more information about the issue. Something to do with the fixed size buffer in the 'ip' tool to store the address and the incompatibility with what the 'teredo' interface reports on Windows.

Thanks @sunilmut
Yes, the root cause is that the Teredo network adapter has a 32-byte hardware address, which is not handled well inside WSL (and has just been fixed recently).
We also found that the Linux "ip addr show" tool does not handle 32-byte hardware addresses well either - it will crash when trying to display the HW address due to a string buffer overflow. You will see this crash in "ip" in the next Insider build if you have Teredo enabled.
Note that these are two different issues with the handling of 32-byte HW addresses - one in WSL, and one in "ip". The issue in WSL has been fixed, so in the next Insider build you will see the issue in "ip". (Most other tools handle this correctly)
We think that the fix should be in the "ip" code, and plan to reach out to them. If anyone here is familiar with the standards regarding hardware address (not MAC address) length, please let us know.

Related: #1391?

The teredo issue should be fixed in 15007