window ist not defined

Version

Development Environment
Chrome, MacOS, NodeJs
Current Behavior
I tried to "include" the TUI calender into my WEB Project but is always throws the exception: windoe is not defined when I try to run the Example code
var Calendar = require('tui-calendar');

Exception: }) (window, function(WEBPACK_EXTERNAL_MODULE_tui_code_snippet, WEBPACK_EXTERNAL_MODULE_tui_date_picker) {
^
this is my first issue ever - so hope I gave enough information
thanks

#511 might be helpful for you. And check dependency packages of Calendar if you use package manager(npm, yarn)

I'm encountering the same issue and I installed snippets, date_picker and time_picker

Version
Development Environment
Chrome, Windows 10, nodeJS
Current Behavior
var Calendar = require('tui-calendar'); require("tui-calendar/dist/tui-calendar.css");
C:\Users\Lyle Tingle\Documents\GitHub\SD-D-Project\node_modules\tui-calendar\dist\tui-calendar.js:16
})(window, function(WEBPACK_EXTERNAL_MODULE_tui_code_snippet, WEBPACK_EXTERNAL_MODULE_tui_date_picker) {
^
ReferenceError: window is not defined
at Object. (C:\Users\Lyle Tingle\Documents\GitHub\SD-D-Project\node_modules\tui-calendar\dist\tui-calendar.js:16:4)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
at Module.load (internal/modules/cjs/loader.js:1002:32)
at Function.Module._load (internal/modules/cjs/loader.js:901:14)
at Module.require (internal/modules/cjs/loader.js:1044:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object. (C:\Users\Lyle Tingle\Documents\GitHub\SD-D-Project\server.js:5:16)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)

Thanks!
https://reinaldoamaral.net/galeria/index.php/home/brasil-central
https://reinaldoamaral.net/galeria/index.php/home/brasil-central

Em 11/04/2563 BE, à(s) 03:37, stale[bot]<EMAIL_ADDRESS>escreveu:
Closed #525 https://github.com/nhn/tui.calendar/issues/525.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/nhn/tui.calendar/issues/525#event-3223736568, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKFS5EI6RVPT6G327SOJAALRMAF4HANCNFSM4K5O446A.

Is there anyone who resolved the above issue?
I am facing this issue in remix

@harshith-venkatesh
The calendar does not support SSR yet, so you need to handle browser-only codes by yourself.
There's a documentation about this issue in Remix.
https://remix.run/docs/en/v1/guides/constraints#browser-only-code-on-the-server

Hi Team, I found the solution for the above problem. Basically while @toast-ui/react-calendar package, we can name the file as .client.tsx extension which makes file to render at client end.

Thank you @adhrinae @DeRaowl for the help and support 👍

just use dynamic import like this:
const Calendar = dynamic(() => import('../components/Calendar/Calendar'), {   ssr: false, })

As of today, the dynamic way doesn't work any more with Next.js 13, I got this error when I try to use this package
react-server-dom-webpack-client.browser.development.js:1602 Uncaught TypeError: Cannot redefine property: default
    at Function.defineProperty (<anonymous>)
    at eval (webpack-internal:///(:3000/sc_server)/./node_modules/@toast-ui/react-calendar/dist/toastui-react-calendar.mjs:6:8)


Provide a better error message when ElementWrapperList is passed to a Selector function

Hello there!
Thanks for providing this wonderful library!
I've run in this issue when trying to learn how to write tests with Gauge and Taiko.
I think that a self explainatory message would be helpful to get a better understanding on how to use selector functions.
Expected behavior
Provide a more detailed error message when a wrong argument is passed to a Selector function.
I mean something like:
 * My spec  ...[FAIL]

        Failed Step: My spec
        Specification: specs/my.spec:8
        Error Message: TypeError: You are passing a `ElementWrapperList` to a `dropDown` selector. Refer https://docs.taiko.dev/api/dropdown/  for the correct parameters
        Stacktrace:
        TypeError:  You are passing a `ElementWrapperList` to a `dropDown` selector. Refer https://docs.taiko.dev/api/dropdown/  for the correct parameters
            at xpath (node_modules/taiko/lib/helper.js:143:8)
            at node_modules/taiko/lib/taiko.js:2625:53
            at get (node_modules/taiko/lib/elementWrapper/elementWrapperFactory.js:64:56)
            at node_modules/taiko/lib/elementSearch.js:198:28
            at waitUntil (node_modules/taiko/lib/helper.js:121:17)
            at processTicksAndRejections (internal/process/task_queues.js:93:5)

Actual behavior
In a Gauge+Taiko project when ElementWrapperList is passed to a Selector function the resulting error is:
 * My spec  ...[FAIL]

        Failed Step: My spec
        Specification: specs/my.spec:8
        Error Message: TypeError: s.match is not a function
        Stacktrace:
        TypeError: s.match is not a function
            at xpath (node_modules/taiko/lib/helper.js:143:8)
            at node_modules/taiko/lib/taiko.js:2625:53
            at get (node_modules/taiko/lib/elementWrapper/elementWrapperFactory.js:64:56)
            at node_modules/taiko/lib/elementSearch.js:198:28
            at waitUntil (node_modules/taiko/lib/helper.js:121:17)
            at processTicksAndRejections (internal/process/task_queues.js:93:5)

In the Taiko REPL the resulting error is:
Error: DropDown with label [object Object]  not found

Steps to reproduce

Setup a Gauge + Taiko project
Write a await dropDown($(selector)).select(value); command inside a Gauge spec.
Run the spec

Versions
node v12.13.0, taiko v1.0.13, @getgauge/cli v1.1.1

This seems a valid check to be done. Thanks for reporting and it would be great to have a PR raised.

Wow, thanks for the quick answer! I will try to work on this 😄


fix: Dropdownfield hint fix

Solution description
with flutter 3.19.0, there is an issue with dropdown field hints not being vertically centered. as a work around, users could use hint widget feature that's bounded to the widget itself not the Inputdecoration delegate.
Screenshots or Videos

To Do

[ ] Read contributing guide
[ ] Check the original issue to confirm it is fully satisfied
[ ] Add solution description to help guide reviewers
[ ] Add unit test to verify new or fixed behaviour
[ ] If apply, add documentation to code properties and package readme

Hi @TMadox please resolve pipeline errors to could be merge


python3Packages.resolvelib: 0.5.5 -> 0.8.1

Motivation for this change
Bump resolvelib
I'm not entirely sure how to test ansible.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@FRidh It looks like this will not be compatible with ansible-galaxy per https://github.com/ansible/ansible/blob/devel/requirements.txt.
Should I go ahead an split this into two separate packages (resolvelib-0_5 for ansible, and plain resolvelib for future dependents, pdm being the first one))

in python-packages.nix we do not allow multiple versions of the same package that could end up in the runtime closure. So, if pdm is used as a library (which is why it would go in python-packages.nix) there is no option but having one broken package.

Does the story change if pdm is an application? I think that'll be the primary way it's used.

Actually ansible is already a library, so then it is fine to add a second version of the library. Preferably put the older version it in the ansible folder.
If pdm is packaged as application, then yes, it can have other dependency versions.

@FRidh I split resolvelib into 2 packages, and I'll reopen the pdm PR against master as an application.

Closing, will incorporate this directly into #155390


Add unit tests for pyiron_base

@muh-hassani Can you add the notebooks from https://github.com/pyiron/pyiron_base/tree/master/notebooks to be included in pyiron_base ? And then they should also be included in the tests.

Duplicate issues of https://github.com/pyiron/docker-stacks/issues/27


Revision 1

What's New

Added Azure LAPS handling
Fixed logic bugs and overhauled logical handling and conditions

Squashing and merging


Fix #95: catch OSError when collecting file descriptors.

I also ran into the issue described in #95. It's a show stopper for me right now so I made a PR :)
Cheers!

Thanks!


How to synchronize annotations?

How can I draw annotations in one of the CT/PET/Fusion viewport and synchronize them to the other two viewports?

if they are in volume viewports and share the same frame Of reference it works by design. You can try it here https://v3-demo.ohif.org/tmtv?StudyInstanceUIDs=<IP_ADDRESS>.4.1.145<IP_ADDRESS>.7009.2403.334240657131972136850343327463

I think @abby0127 said synchronize annotations in different viewports of one tthree orthogonal view

Not sure what is the requested feature. Can you guys provide more description (with images, drawings etc. if that helps)

just like this one, annotations can be sychronized in the same orientation in both viewport of Volume and Stack, but it not shows in sagittal orientation.

So is there any api or function can convert the points of annotation in axial to the points can be used in sagittal?

Do you need interaction in the sagittal or just know where is that in general? Interaction is not possible, but you can gran the annotation from the annotationState, cornerstoneTools.annotation.state.getAnnotation then you have the points in the 3D world. We just don't show them there since they will appear as 4 dots

I mean i can get the data that after draw a rectangle annotation in axial. I saw there are points and world poistion. I just need to convert the point to suit for sagittal, then I can create a new annotation and add it to sagittal

Thanks a lot, I'll check it.

I guess we have a lot of filters that we don't show the annotations if camera is not aligned you can take them out if you want, look at packages/tools/src/utilities/planar/filterAnnotationsForDisplay.ts
asd


[youtube] Fixed 'next_link' regular expression

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
The current regular expression used to find the next page link of the search results does not work. As a result, no link is found and there is an unintentional limit to the first page of search results (20 results. If a search is made for with a specified limit of 50, youtube-dl will not find a link to the next page and report that only 20 results were found (even if there were more on any potential next pages).
This PR updates the regular expression in question. Rather than removing the offending part of the regex, I have simply made it optional for backwards compatibility or in case the next page link is changed back.

This is the associated issue: https://github.com/ytdl-org/youtube-dl/issues/26161

This patch doesn't seem to work unfortunately

This patch doesn't seem to work unfortunately

Can you give more information about what isn't working for you? This change is still fixes pagination for me.

No longer actual.


Add caching support to verify-links

Update link checking pipeline to enable caching
Add loading cache file from a http endpoint
Add retry logic when hitting 429

Fixes most of https://github.com/Azure/azure-sdk/issues/2403
Fixes https://github.com/Azure/azure-sdk-tools/issues/1439

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

I assume you are talking about the github.io link checker. I've generally when with scheduled builds for these type of type of things as that is the best option we have short of writing our own scheduler/triggering mechanism. I know we have skirted around that issue for a while and I'm not sure this is enough of a reason to push us over the edge. That said if you want to file an issue on the backlog to track that I'm not opposed to the idea we just need to figure out how we would integrate it.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


BUSCO runs on longest isoforms

For now, we are using the longest isoforms for each gene to run BUSCO. Might or might not be the proper way to run it

https://github.com/orgs/nf-core/projects/76

BUSCO developers recommend filtering the gff files to get the longest isoform of each gene.
See BUSCO protocols.


feat(tls): extends ServerTlsConfig for optional KeyLogFile

Motivation
Tonic no longer allows setting Rustls config directly.
Solution
This PR starts off down the road adding piecemeal configurability into the Tonic TLS config to aim for Rustls config parity from Tonic once more. In this instance a setting to install KeyLogFile, reinstating the possibility of Wireshark TLS decryption.

Why only support a single implementation of KeyLog? Would it be better to support providing the KeyLog implementation as a Arc<dyn KeyLog>, as it's actually exposed in the ServerConfig?
https://github.com/rustls/rustls/blob/5bda754ac18f37eb39132f89fb5522494b6202eb/rustls/src/server/server_conn.rs#L221-L223
Or better yet, what about supporting providing an arbitrary rustls::ServerConfig so we don't need have helpers for each and every option exposed by rustls?

@LucioFranco note that you can't actually build a ServerConfig except through the safe builder API. It would probably best to take the builder-generated ServerConfig directly when rustls is enabled.

@olix0r by take you mean expose it publicly in tonic?

@LucioFranco probably? I'm not sure if it's worth providing a simplified abstraction over TLS configuration, given the finicky nature of TLS configurations, unless the goal is to support multiple TLS implementations...

@olix0r only reason I bring it up is we used to expose it but ended up removing it because we would be forced to release a new version of tonic for new versions of rustls which didn't seem ideal. I wonder if there is a better way forward by extracting the tls part to its own crate similar to what hyper does. There is a lot of overlap here since axum will also need to solve this. cc @davidpdrsn

@LucioFranco another option might be to expose tonic-specific Acceptor/Connector traits with implementations for tokio_rustls::TlsAcceptor/tokio_rustls::TlsConnector?

Yeah that is what I am leaning towards. Though I think there are some complications with acceptors that I outlined in this hyper issue. https://github.com/hyperium/hyper/issues/2321

@LucioFranco the other benefit of that approach is that it could let us support multiple TLS implementations in an --all-features-safe way. While rustls is generally great, it currently has a number of limitations, such as being unable to use TLS certs bound to IPs instead of DNS names. Being able to integrate with tokio_boring, etc, would be nice.

Yeah, I think that is the right solution....will be some work but probably worth it. Over actually moving over to axum.

obsoleted by https://github.com/hyperium/tonic/pull/968


Publish gauge-java nightly package for maven projects

Currently, we are only uploading gauge-java-nightly plugin in bintray, but gauge-java-nightly package is not uploaded for maven projects, so there is no way for maven users to use nightly package.

Maven Gauge-Java nightlies are published in Bintray https://bintray.com/gauge/maven-gauge-java/Nightly/


You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file

🐛 Bug Report

<EMAIL_ADDRESS>105:38
Module parse failed: Unexpected token (105:38)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.webEventResponder = devsupport_1.WebEventResponder.create(this);
|         this.focus = () => {

        this.textInputRef.current?.focus();

|         };
|         this.blur = () => {
<EMAIL_ADDRESS>137:37
Module parse failed: Unexpected token (137:37)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     }
|     scrollToIndex(params) {

    this.tabIndicatorRef.current?.scrollToIndex(params);

|     }
|     scrollToOffset(params) {
<EMAIL_ADDRESS>148:38
Module parse failed: Unexpected token (148:38)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     }
|     componentWillUnmount() {

    this.hardwareBackSubscription?.remove();

|         this.hide();
|     }
<EMAIL_ADDRESS>169:36
Module parse failed: Unexpected token (169:36)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.expandAnimation = new react_native_1.Animated.Value(0);
|         this.show = () => {

        this.popoverRef.current?.show();

|         };
|         this.hide = () => {
<EMAIL_ADDRESS>26:36
Module parse failed: Unexpected token (26:36)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.popoverRef = react_1.default.createRef();
|         this.show = () => {

        this.popoverRef.current?.show();

|         };
|         this.hide = () => {
<EMAIL_ADDRESS>50:33
Module parse failed: Unexpected token (50:33)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.listRef = react_1.default.createRef();
|         this.scrollToEnd = (params) => {

        this.listRef.current?.scrollToEnd(params);

|         };
|         this.scrollToIndex = (params) => {
<EMAIL_ADDRESS>62:27
Module parse failed: Unexpected token (62:27)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         super(props);
|         this.startAnimation = (callback) => {

        this.animation?.start(callback);

|         };
|         this.stopAnimation = () => {
<EMAIL_ADDRESS>90:36
Module parse failed: Unexpected token (90:36)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.popoverRef = react_1.default.createRef();
|         this.show = () => {

        this.popoverRef.current?.show();

|         };
|         this.hide = () => {
<EMAIL_ADDRESS>93:47
Module parse failed: Unexpected token (93:47)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|                 visibleDate: nextVisibleDate,
|             }, () => {

            this.props.onVisibleDateChange?.(this.state.visibleDate, this.state.viewMode.id);

|             });
|         };
<EMAIL_ADDRESS>95:36
Module parse failed: Unexpected token (95:36)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.inputRef = react_1.default.createRef();
|         this.show = () => {

        this.popoverRef.current?.show();

|         };
|         this.hide = () => {
<EMAIL_ADDRESS>99:36
Module parse failed: Unexpected token (99:36)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|         this.popoverRef = react_1.default.createRef();
|         this.show = () => {

        this.popoverRef.current?.show();

|         };
|         this.hide = () => {
To Reproduce
Steps to reproduce the behavior:
Expected behavior

Link to runnable example or repository (highly encouraged)

UI Kitten and Eva version

Package
Version

@eva-design/eva

@ui-kitten/components

Environment information

@rashed-iqbal could you please describe what you are trying to achieve? It's not clear from the error above.

I have the same issue after installing @ui-kitten/components in my project with expo.


what's the  difference between multus-cni and CNI-Genie？

Under what circumstances should CNI-Genie be chosen?

Maybe multus-cni support plugins more than

@woshihaoren

CNI-Genie supports

similar to Multus, reference cni plugins, 3rd party plugins, e.g., Flannel, Calico, Weave Net, Romana, etc., specialized plugins, e.g., SR-IOV
unlike Multus, supports any 'generic' CNI plugin installed on the host

CNI-Genie supports

similar to Multus, multi-NICs per container
unlike Multus, multi-NICs per pod
unlike Multus, assigning any NIC to any plugin of choice in runtime

CNI-Genie supports, unlike Multus, Network isolation, i.e.,

dedicated physical network for a tenant
Isolated logical networks for different tenants on a shared physical network

CNI-Genie supports, unlike Multus, real-time switching between different networks for a given workload

CNI-Genie supports, unlike Multus, network selection based on the user-provided measures (smart selection)

@satyaranjanp @sushanthakumar
Please add any other features that I may be missing above!

@kshafiee  Do you have a demo of
assigning any NIC to any plugin of choice in runtime  and
dedicated physical network for a tenant and
Isolated logical networks for different tenants on a shared physical network


Batch helper methods

Is your feature request related to a problem? Please describe.

Batch operation helper methods for SQS and DynamoDB
Describe the solution you'd like

Helper methods that will automatically chunk a list into specific sizes compatible with sqs SendMessageBatch and dynamodb BatchWriteItem
Describe alternatives you've considered

I end up rewriting this same functionality in multiple projects.
Additional context

Hey @jplock, thanks for the feature request! Could you share an example of what you have at the moment?
That will help clarifying whether this is best placed in the boto3 SDK, or if a helper method as part of SQS/DynamoDB data classes
Thanks!

from typing import List, Any

import boto3

# https://stackoverflow.com/a/1751478
def chunks(l, n):
    n = max(1, n)
    return (l[i:i+n] for i in range(0, len(l), n))

DYNAMODB_BATCH_WRITE_ITEM_LIMIT = 25
SQS_SEND_MESSAGE_BATCH_LIMIT = 10

def dynamodb_batch_write_item(table_name: str, items: List[Any]) -> None:
    dynamodb = boto3.client("dynamodb")

    for chunk in chunks(items, DYNAMODB_BATCH_WRITE_ITEM_LIMIT):
        if not chunk:
            continue

        params = {}
        params[table_name] = chunk

        dynamodb.batch_write_item(**params)

def sqs_send_message_batch(queue_url: str, messages: List[Any]) -> None:
    sqs = boto3.client("sqs")

    for chunk in chunks(messages, SQS_SEND_MESSAGE_BATCH_LIMIT):
        if not chunk:
            continue

        params = {
            "QueueUrl": queue_url,
            "Entries": chunk
        }

        sqs.send_message_batch(**params)

The DynamoDB Batch Write Item call gets more complicated since it can operate across multiple tables, so I'm not sure on the best interface for that, but hopefully this makes sense.  Retry logic would also need to be added into the DynamoDB use-case to handle retrying any items returned in UnprocessedItems.


Add arm64,armv7 - Add version tag - update docker and python req

Adds check to only push docker image when it pushed (not on pr like it currently does)

Adds Dependabot (Checks docker, pip and python requirements)

Adds Ubuntu 18 compatibility checks

Adds the arm architectures (arm64, armv7, armhf) to the build, allowing A.R.M to be run on arm.

Added QEMU
Added step to show platform versions available
Automatically reads the version from the new VERSION file and pushes to the version & latest tags
This significantly increases the build times (Average is 1h)

Added  libzbar-dev libzbar0 scons swig for arm64 dependencies

Build now compiles MakeMKV ensuring the latest version

Updated all links to now use the main arm repo

Bumped version (1.0.3)

Version bumps

Bump beautifulsoup4 from 4.10.0 to 4.11.1
Bump soupsieve from 2.3.1 to 2.3.2.post1 (
Bump cffi from 1.15.0 to 1.15.1 (
Bump flask-wtf from 1.0.0 to 1.0.1 (
Bump xmltodict from 0.12.0 to 0.13.0 (
Bump sqlalchemy from 1.4.32 to 1.4.39 (
Bump psutil from 5.9.0 to 5.9.1 (
Bump apprise from 0.9.7 to 0.9.9 (
Bump urllib3 from 1.26.9 to 1.26.10 (
Bump certifi from 2021.10.8 to 2022.6.15 (
Bump actions/setup-python from 2 to 4 (

Fantastic work!


Orphaned ble scanner?

Version of the custom_component
v0.6.5
Describe the bug
I'm seeing errors in the logs that I believe are related to a BLE proxy that I removed from Home Assistant, but apparently Bermuda is still looking for it? If I am correct, I'm unsure how to remove it. I can't find any related devices/entities in HA.
Debug log
This error originated from a custom integration.
Logger: custom_components.bermuda
Source: custom_components/bermuda/init.py:169
integration: Bermuda BLE Trilateration (documentation, issues)
First occurred: 6:25:48 PM (390 occurrences)
Last logged: 8:51:04 PM
Failed to find config for scanner b84a63eaf58f89218e88c58c06b3dafd, this is probably a bug. (40680 previous messages suppressed)
Failed to find config for scanner b84a63eaf58f89218e88c58c06b3dafd, this is probably a bug. (41276 previous messages suppressed)
Failed to find config for scanner b84a63eaf58f89218e88c58c06b3dafd, this is probably a bug. (40742 previous messages suppressed)
Failed to find config for scanner b84a63eaf58f89218e88c58c06b3dafd, this is probably a bug. (41172 previous messages suppressed)
Failed to find config for scanner b84a63eaf58f89218e88c58c06b3dafd, this is probably a bug. (8038 previous messages suppressed)

Curious!
The value b84a63eaf58f89218e88c58c06b3dafd is coming from BaseHaScanner's source attribute, and we expect it to be a BLE MAC address, but this looks like a UUID, like those used for config entry IDs etc.
I haven't been able to replicate this on my test setup, which is annoying! :)
Can you post your dump_devices service output? You can limit it to just one device using the addresses parameter, I'm mainly interested in what shows up in the scanners block of a device.

Something else that might help is if you can Enable Debug Logging in the Bermuda integration page, reload the integration, then Disable Debug Logging and send me the file it downloads to you. This might give me some logging messages about why it's trying to necro a non-existent proxy.
You can email to me<EMAIL_ADDRESS>if you would rather not upload it here.

Ok, new information, or newly remembered old information actually. I setup this less than alpha integration a while back. https://github.com/kvj/hass_Bluetooth_Proxy_Companion. The goal or purpose of that integration is to turn fixed android devices with Bluetooth scanning capability into Bluetooth proxies, like wall mounted tablets. This is a really great idea actually, especially for me with 4 already mounted Samsung tablets in my home. It uses the tablets Bluetooth connection and makes calls to HA via a webhook. The scanner ID bermuda was picking up was from the one tablet I set the integration up on. Home assistant was storing information from that tablet received via webhook in bluetooth.remote_scanners, for whatever that's worth. I can send that config file if it was interesting to you. I don't know if that integration is going anywhere, but in its current state, bermuda did not pick up and use the information for another scanner, for whatever reason. If something like that was working, it could potentially be an easy way for some people to add ble proxy functionality to existing devices, but its easy enough to install a shelly device or whatever, so I don't think people who didn't already have tablets would be too excited about it. All that to say, not sure if its worth further exploration or not.

Ahh, now that's interesting!
I do a relatively unsophisticated trawl through config entries to find scanners, just looking to see if they enter themselves as having a MAC address we recognise from advertisements. Due to that I suspect the integration you used  was found, but Bermuda grabbed the config entry_id or something like that instead of its mac address, and maybe that's why it's making bad decisions trying to find it (and maybe why it didn't work for you out of the box).
I might try it out if I get a moment, as it would be good to support if it works more-or-less the same way as other proxies - especially once I get the options in to choose which proxies to use for location.

The companion app sends BLE adverts via a webhook to:
https://github.com/kvj/hass_Bluetooth_Proxy
which registers as a bluetooth scanner in HA.
Adding support for this probably requires just being less naive about how Bermuda looks for scanners, and to use the APIs rather than blindly trawling through config entries looking for mac addresses, on the assumption of them being esphome or local BT adaptors.
Note: will need to add docs on how this works and how to diagnose faults, since peeps will have trouble seeing where in the process things are or are not working, and the project is in its early stages of development / experimentation.


Player hangs in between play

Hi,
I am using the latest shaka player from master.
I am using the demo player to play the custom content: https://s3-ap-southeast-1.amazonaws.com/learnyst/schools/151/courses/337/paid/7580/online/tst/V2-No-theory-I-prime-verificationwebTrack.mpd
The content will stop playing(Pauses or hangs) at 2:04. If we seek a little using the seekbar then content will start playing again. Similar behaviour we experience for other videos also.
Note: This content was playing successfully with other players.
How to reproduce this issue: Play the content using the demo player. Wait till 2:04. At 2:04 the player hangs. If we seek a little the play will start again

The same issue is observed with the hosted demo shaka player also

@joeyparrish have you got any chance to check this issue. thanks

This appears to be bad content.  At time 2:04 there is a frame whose time overlaps another frame.  When you play the video and open chrome://media-internals it gives a warning of Generated splice of overlap duration 4000us into new buffer at 124993333us.  I also tried this in the Dash IF player and it failed to play also.
This fails to play in Chrome 55 (current stable).  This plays in Chrome 56 and produces a decoder error in Firefox.  You should file a bug with the packager that generated the content.

ok


Cilium 1.15 too many open unix sockets

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium agent and envoy use so many open unix sockets and it increases overtime. It is because of envoy as restarting envoy fix it. It is visible on both containers because of privileged mode probably.
wc -l /proc/net/* | sort -h
...
...
...
    173 /proc/net/tcp
   1246 /proc/net/nf_conntrack
  12144 /proc/net/unix

And different cluster incl. screenshot
    199 /proc/net/tcp
    738 /proc/net/unix
   1573 /proc/net/nf_conntrack

Cilium Version
1.15.5
1.15.4
Kernel Version
Linux app-worker-dev-d556f601-qfnnq 5.14.0-427.18.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.28.10+rke2r1
Regression
I don't know
Sysdump
File size too big. Please let me know how should I proceed.
Relevant log output
Haven't found anything interesting  in logs

Anything else?
A lot of the unix sockets are /var/run/cilium/envoy/sockets/admin.sock
Cilium Users Document

[ ] Are you a user of Cilium?

The root cause is due to the periodic checks on envoy's version by cilium-agent.
https://github.com/cilium/cilium/blob/2bf8ae746efe113d36811ae36c14e96e527592cb/pkg/envoy/envoyadminclient.go#L78-L85
https://github.com/cilium/cilium/blob/2bf8ae746efe113d36811ae36c14e96e527592cb/pkg/envoy/cell.go#L262-L269
Below is the reproduction code. By executing this code, you can very stably reproduce the problem mentioned above.
package main

import (
	"context"
	"encoding/json"
	"fmt"
	"io"
	"net"
	"net/http"
	"time"
)

// ByteSize expresses the size of bytes
type ByteSize float64

const (
	_ = iota // ignore first value by assigning to blank identifier
	// KB is a Kilobyte
	KB ByteSize = 1 << (10 * iota)
	// MB is a Megabyte
	MB
)

// ErrLimitReached indicates that ReadAllLimit has
// reached its limit before completing a full read
// of the io.Reader.
var ErrLimitReached = fmt.Errorf("read limit reached")

func ReadAllLimit(r io.Reader, n ByteSize) ([]byte, error) {
	limit := int(n + 1)
	buf, err := io.ReadAll(io.LimitReader(r, int64(limit)))
	if err != nil {
		return buf, err
	}
	if len(buf) >= limit {
		return buf[:limit-1], ErrLimitReached
	}
	return buf, nil
}

func main() {
	for true {
		dial()
		time.Sleep(5 * time.Second)
	}
}

func dial() {

	client := &http.Client{
		Transport: &http.Transport{
			DialContext: func(ctx context.Context, _, _ string) (net.Conn, error) {
				return net.Dial("unix", "/var/run/cilium/envoy/sockets/admin.sock")
			},
		},
	}
	resp, err := client.Get("http://envoy-admin/server_info")
	if err != nil {
		fmt.Printf("failed to call ServerInfo endpoint: %w", err)
	}

	defer resp.Body.Close()

	body, err := ReadAllLimit(resp.Body, MB)
	if err != nil {
		fmt.Printf("failed to read ServerInfo response: %w", err)
	}

	serverInfo := map[string]interface{}{}
	if err := json.Unmarshal(body, &serverInfo); err != nil {
		fmt.Errorf("failed to parse ServerInfo: %w", err)
	}

	version, ok := serverInfo["version"]

	if !ok {
		fmt.Println("failed to read version from ServerInfo")
	}

	fmt.Println("version", version)
}


Datatable destroy() (v1.10) and fnDestroy(v1.9) generates Detached Nodes and memory leaks

Destroying and recreating tables in succession, generates memory leaks.
This is caused  by In https://github.com/DataTables/DataTables/blob/master/media/js/jquery.dataTables.js#L9326 (v1.10)
missing a for cycle to set "null" all settings attributes.
for (var sKey in settings) {
settings[sKey] = null;
}
This problem there is in fnDestroy (v1.9) too.
An exhaustive problem's analysis: http://www.mozartrocks.ro/dt-test/patch-1.html.
I hope you'll fix this quickly.
Thanks

Can you give me a link to a page that demonstrates the issue please. If there are events not being tied or DOM elements not being realised, I'd like to understand why that is happening.

At the moment, I cannot show the issue on a public link. I could send you a  timeline of the memory with and without fix.
I found the bug performing a lot of consecutive destroy and reinitialize commands  querying a heavy dataset with over 8000 rows. This bug doesn't appear with lighter datasets or fewer requests.
I tried your live example taken from the URL http://live.datatables.net/ too by executing the $('#example').DataTable().destroy(true)  and then the  "Run with js" commands a number of times. I attached the nodes' curve and the number of detatched nodes (opening the list of detached nodes the page crashed).

Going to close this for the moment. If this is still causing a problem, please link to a test case showing the problem.


Devolo - Smoke Detectors: After switching to node-zwave-js, sometimes they sound their alert

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
Differences between openzwave and node-zwave-js in handling the "Devolo - Home Control Smoke Detector"
What do you observe?
I have three of said devices. After switching from openzwave to node-zwave-js, two of the smoke detectors have been signaling a "warning" - short beep, like if the battery is dead. After getting new batteries, and still having them sound their alert, i looked at the voltages of the batteries, and they are fine - so it is something different.
After manually waking up the smoke detectors (1 second press on button), they will wake up, connect to the controller, and everything will be fine. Until, after some time, they start beeping again.
The two smoke detectors that do beep use other nodes as their hops, the one that does not is near the controller. Looking at the network-graph in the web-ui, there are only two connections to the controller, the others all have only neighbours without a route to the controller - but they work.
My guess is that there is something different in the wakeup communication, and the smoke detector thinks it lost its connection. The alarms have been are around the times of the scheduled wakeup.
What did you expect to happen?
Being able to sleep :(
Steps to reproduce the behavior:

Buy several of those Devolo Smoke Detectors.
Have some far away from the Controller
Sleep
Hear alarm

Device information
Manufacturer: Devolo
Model name: Home Control Smoke Detector | 09813
Node ID in your network: 18, 32
How are you using node-zwave-js?

[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
zwavejs2mqtt: 6.0.3
zwave-js: 8.8.3
home id:<PHONE_NUMBER>
home hex: 0xe3557a22
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Same devices with openzwave did not show the same behaviour
Attach Driver Logfile
zwavejs_2021-12-05.log
Node 18 started beeping around 16:50. Node 25 is the smoke detector that works fine.

This might be a better zwavejs_2021-12-06.log
Today at 6:46 local time, which is 5:46 in the logfile, the smoke detector decided to beep again. I took out the batteries, and reinserted them at ~8:40. Also, the reinsertion was followed by route updates, so thats in there as well.
Thank you for your work, by the way. For my other devices, zwavejs is far more reliable and quite a bit faster than the two other implementations :)

5:46 in the logfile, the smoke detector decided to beep again
I took out the batteries, and reinserted them at ~8:40.

All the device sends then are wakeup notifications, but the driver sends it back to sleep since it has no queued messages.
I see a couple of those commands failing with "NoAck", but that is relatively normal for battery-powered devices, which often go back to sleep before the ACK has reached the controller.
At 2021-12-05T23:03:02.652Z (and some other timestamps), the driver fails to refresh the wakeup interval with the same error though, which might indicate that you do have a range issue here. You can try doing a network heal to let the controller figure out new routes.

So, i did the heal on December 6 and it finished after 6 hours. Everything looked fine, until there were those Warning-Beeps on Node 18 again. I tried to log the timestamps, but since some of those were handled by my wife, and sometimes it was in the middle of the night, i do not have a complete list. There were, at least:
December 11, 23:07 ; December 18, 05:45 ; December 20, 07:27, December 21, 07:10 (after that, node 18 got disabled).
I do know that this looks like a Problem with my Z-Wave Setup, but i never had those problems with a year of running https://github.com/OpenZWave/Zwave2Mqtt . Also, the maximal Distance between the nearest active router or the controller is maybe 5 meters, and after the migration to node-zwave-js i did not change the z-wave network - neither adding new nodes nor moving the current ones around.
Since zwave2mqtt is dead, and i would really like the smoke detectors to stop waking me up, i would really like to help to get the support for those devices better. I however, failed to find reproducable way to get them to beep. Also, i have not found a technical document that describes the behaviour of the smoke alarms that would mention the "lost connection to zwave" beep. What i did try is to remove one of the routers, and then the kitchen smoke alarm had the beeping twice (which did work prevously).
Do you know if ozwd handles failed messages differently than node-zwave-js does? Maybe this might help.
Thank you for your reply, and the whole team of node-zwave-js for the work. My other devices work quite a bit "faster", for example those "active routers" are switchable power outlets. node-zwave-js is quite a lot faster, and works for every "switch". (ozwd needed a second "switch toggle" in 1 of 20 cases)

Since the Danfoss LC-13 thermostats and the Devolo variant require a certain set of commands after waking up, I tried finding a reference to something similar for the smoke detectors in the OZW repo but there seems to be none. Also if there were, I'd expect more users to report this issue - you're the only one so far.
When the nodes wake up, they send a command to the controller. Afterwards this should happen:

The controller itself acknowledges the command.
zwave-js checks if there are pending messages and sends them
zwave-js sends the node back to sleep

There isn't really a lot that zwave-js can be doing wrong here.
1. is handled on the protocol level, initiated by the stick, and we have no control over that.
2. didn't seem necessary in your logs, unless you queued a config change or something
3. also happens as can be seen in your logs above
Honestly, this is a case for the manufacturer support. They should be able to tell you why the sensors start beeping and what's necessary to prevent them from doing so.

First of all, thank you for looking up if there were device specific quirks for the "Devolo Smoke Detector" in OZW.
I reread the Manual, and the only beep they mentioned was the "battery low" beep. So, surely enough, in the homeassistant some of the 3 smoke detectors had "battery low" states in their recent history. This was weird because:

i had several looks inside the zwave2mqtt ui if the battery was empty the first times the smoke detectors started beeping after the migration
the migration to node-zwave-js happened because one of the smoke detectors was empty, and i just changed all batteries because they were all quite old.

I did look at the voltages of the batteries (as stated in the first post). However, according to recent tests i suspect the batteries. if i measure the voltages they are fine (3,0-2,9V). However, once there is the slightest load applied they drop quite a bit. I changed to a new set of batteries in two of the detectors (which is extra annoying, because the CR123 batteries are not really that common and arent cheap either). Also, this would explain why the garage detector was the first to be weird, because the lower temperatures should cause the batteries to drop sooner.
After reading your comments, i am optimistic that this might have been the problem all along. I will close this in a few days if this is indeed the case.
Thank you for your support!

I am happy to report back that i have yet to encounter any issue. Thank you for your work, and have a nice 2022!

You too, glad you figured it out.


Waiting for signal after learning

When I try to learn a code either Rf or IR on my RM4 pro, it does not show me the read code. The process works fine until it has to show the code.
any ideas?
Broadlink Manager Version 3.0.5
RM4 Pro - 0x61a2 - Firmware v52079

i am also having this exact issue.  it just hangs on waiting for signal but status says IR Data Received . .
RM mini 3
by Broadlink
Firmware: 44057

same here - RM Mini 3 (0x5f36)
What is supposed to happen next? I'd be happy if I could just see the code to be fair :)

it is supposed to spit out a code so you can use it in a switch.

haha that would solve all my problems, alas it is not working for me, I suspect its due to the newer hardware/firmware - I cant seem to get anything to extract codes from it - although its just fine at learning them itself :(

gave up and just followed this guide doing it directly in HA.  works a treat.
https://www.youtube.com/watch?v=lWCHZm9xWno&t=49s

I had the same problem. A look at the console showed me an error loading ga (google analytics) in hex.js. After commenting out the two lines with ga in hex.js, it now works as expected.

That has worked for me too -  thanks @tamtam1111 :)


Double REG_DEF/REG_ENTRY submissions

Removed sending and submitting rev_reg definition after calling registry_record.generate_registry. This duplicates activity also called inside generate_registry and creates additional ledger transactions.
Also removed the pending_registry_record, which seems to duplicate the already existing registry_record seemingly without adding any value.

Due to the lack of documentation with the code, I'm unsure about the actual implications: what was the reason for creating a new pending_registry_record based solely on the already created registry_record? Why were manual send_def and send_entry calls added at that spot?
I see that nrempel introduced the additional sending of def and entry on july 21 in f98327704c15dcbe78248f55cdf6cab423844eb0. And then subsequently introduced the pending_registry_record. But the commit comments are very generic, so I probably don't understand the reasoning.

Apparently this is not doing what I first saw, closing this until I can properly fix my issue locally.

Hi @muisit -- not exactly sure what you are seeing, but I suspect it is the initial creation of two rev-regs. The approach we are taking to rev-regs is that we always have one more ready than we are using.  We start with two, fill up the first, switch to the second and create a third.  That way, there is no delay during an issuance for creating a new reg -- we create the "next one" in the background.

I think you're probably spot-on, thanks. I must say this is a strange feature to implement here. The controller application can also decide by itself to create a back-up rev-reg after the initial creation. If time is of the essence at that point already, the initial rev-reg should have been larger in any case.
Plus you'll run into the same problem once the pending rev-reg is activated. The controller app will need to know how to create a new rev-reg from a cred-def in any case.
But it matches the rest of the framework, that seems to supply ready-to-use hooks for specific application-types and less of generic-hooks for generic applications.

Do NOT touch this code.
All the manual stuff is for administrative emergency fixes if and when the network goes out at a bad time and a super-user has to clean up the mess to get it into a workable state.

@muisit -- here is the background.  On the first cut of revocation, we left all of the handling to the controller -- creating the rev reg, managing the tails file, etc.  When we realized how problematic that was, we implemented the (almost) fully automated approach -- tell us you want revocation, how big to make each registry and when you want to revoke credentials, and the framework will do the rest.  Easy!
However, when we did that, we decided to leave in the original APIs so the controller COULD do the handling if necessary -- and in particular, a person running an instance could use the API to "clean up" a RevReg if it got into a bad state.  That's pretty unlikely now -- and with new capabilities we'll eliminate, but out of an abundance of caution, we decided to keep the original API "just in case".
Hope that helps.

This seems like a quite an unwanted functionality that perhaps should have some sort of a feature flag to disable it.
From an end user perspective, I cannot fathom the benefit of having a duplicate REVOC_REG_ENTRY and REVOC_REG_DEF, nor do I see a clear way to explain this as an intended behaviour to users that raise this as an glaring issue which they can clearly observe
What recourse is there to alleviate this bug of a feature besides a fork-and-patch, it doesn't seem there is any or am I missing something here?

This is a very valuable feature and should be automatic.  We know this because we tried to use it without and it's horrible for the controller.  Here is the background:
When you create a revocable cred def, you have to create the rev registry of a give size as well -- separate transactions on the ledger.  You then issue credentials for awhile.    When we first added revocation support in ACA-Py, we just exposed the capabilities, and left it to the controller to handle all of the details.  It was horrible for the controller writer.
The first benefit of what is now in ACA-Py is that the controller does not have to track the size of the rev reg, how many credentials have been issued and execute the revreg transactions to the ledger.  The controller just says to ACA-Py -- "create a cred def with a rev reg of size X", and ACA-Py takes care of all of the details.
The benefit of pre-creating the second rev reg at start time is that there is no delay when the first rev reg runs out of space.  The controller issuing credentials doesn't even know the rev reg was switched, and there is no delay.  ACA-Py detects the filled rev reg, switches to the pre-created but unused rev reg, issues the credential and the controller can continue.  Then, in the background, ACA-Py creates another RevReg, so it is ready when the the second one runs out of credentials.  And so on.
The controller only has to track the ID if the issued credentials (a combination of RevReg ID + Credential Index). When necessary, the controller passes the ID in to have the credential revoked.  The controller also tells ACA-Py when to publish revocations -- when to write "Rev Entries" to the ledger.  ACA-Py tracks all of the RevRegs for which unpublished revocations exist, and writes the necessary transactions to the ledger.  Again -- the controller doesn't have to track all of that detail.
Hope that makes sense, and makes it easier to explain.  Let me know if you have further questions.  If this is not covered in a doc, we need to add it.


Tui

add a tui/ syncing flow

Hey, was working on a personal project, opened a PR here by mistake. Cheers!

No problem :smiley:


Update to typings-core

typings-core is released. So you can consider switching to use it instead of typings to access API.
:smile:

Thanks! I'll have a look tomorrow.

I just published a new version of the task, now relying on typings-core. Thanks for the hint @unional.


Slayer task for which I don't have the slayer level

🐛 Bug Report
Got a 15 Thermonuclear smoke devil task which requires 93 slayer.
I however wasn't 93 slayer.
Got the task from duradel using =st.
Discord user RubenJS#7747
Slayer level at that moment was 86.

This has been corrected.


parent app issues blank screen

i built both of the apps and the child app shows with a botton and the parent app is full blank screen
please can u provide some screens how the apps looks and for the features as well

i built both of the apps and the child app shows with a botton and the parent app is full blank screen
please can u provide some screens how the apps looks and for the features as well

can you provide screenshot ?

Same for me. Parent app issuing blank screen. On opening parent app. getting a notification 'successful' that's it. Then a black screen remains.


Looking forward to trying it

This is very interesting work.
Thank you.
Looking forward to trying it.

Thanks Mkaskov


device class None, state class None and unit thus indicating it has a numeric value;

Logger: homeassistant.components.sensor
Source: components/sensor/init.py:597
Integration: Sensor (documentation, issues)
First occurred: 08:16:39 (77 occurrences)
Last logged: 08:16:40
Sensor sensor.victron_inverter_alarm_lowacoutvoltage_239 has device class None, state class None and unit thus indicating it has a numeric value; however, it has the non-numeric value: OK (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Sensor sensor.victron_inverter_alarm_overload_239 has device class None, state class None and unit thus indicating it has a numeric value; however, it has the non-numeric value: OK (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Sensor sensor.victron_inverter_alarm_ripple_239 has device class None, state class None and unit thus indicating it has a numeric value; however, it has the non-numeric value: OK (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Sensor sensor.victron_inverter_info_state_239 has device class None, state class None and unit thus indicating it has a numeric value; however, it has the non-numeric value: INVERTING (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Sensor sensor.victron_inverter_alarm_lowsoc_239 has device class None, state class None and unit thus indicating it has a numeric value; however, it has the non-numeric value: OK (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

I have Home Assistant 2023.3.5, Supervisor 2023.03.1, Operating System 9.5, Frontend 20230309.1. I too am getting  similar log entries when communicating with my Cerbo GX:
WARNING (MainThread) [homeassistant.components.sensor] Sensor
sensor.victron_dcsystem_alarm_highvoltage_226 has device class None, state class
None and unit  thus indicating it has a numeric value; however, it has the
non-numeric value: OK (<class 'str'>); Please update your configuration if your
entity is manually configured, otherwise report it to the custom integration
author.

WARNING (MainThread) [homeassistant.components.sensor] Sensor
sensor.victron_dcsystem_alarm_lowstartervoltage_226 has device class None, state
class None and unit  thus indicating it has a numeric value; however, it has the
non-numeric value: OK (<class 'str'>); Please update your configuration if your
entity is manually configured, otherwise report it to the custom integration
author.

WARNING (MainThread) [homeassistant.components.sensor] Sensor
sensor.victron_dcsystem_alarm_highstartervoltage_226 has device class None,
state class None and unit  thus indicating it has a numeric value; however, it
has the non-numeric value: OK (<class 'str'>); Please update your configuration
if your entity is manually configured, otherwise report it to the custom
integration author.

WARNING (MainThread) [homeassistant.components.sensor] Sensor
sensor.victron_dcsystem_alarm_lowtemperature_226 has device class None, state
class None and unit  thus indicating it has a numeric value; however, it has the
non-numeric value: OK (<class 'str'>); Please update your configuration if your
entity is manually configured, otherwise report it to the custom integration
author.

WARNING (MainThread) [homeassistant.components.sensor] Sensor
sensor.victron_dcsystem_alarm_hightemperature_226 has device class None, state
class None and unit  thus indicating it has a numeric value; however, it has the
non-numeric value: OK (<class 'str'>); Please update your configuration if your
entity is manually configured, otherwise report it to the custom integration
author.

Hello and thank you for opening this issue.
It has been resolved in version v0.0.10 and the issue is primarily tracked in the thread #69.
Feel free to re-open if upgraden to v0.0.10 doesn't solve your issue


Add auto-configuration that adds EC2 metadata as tags for the Microme…

Add auto-configuration that adds EC2 metadata as tags for the Micrometer metrics.

@maciejwalkowiak Did some research and came up with this pull request. Also run it on an app demo and got the expected results.
The build complains about junit in all modules, however I haven't changed any dependency related code. Could you help me to find what is missing?

Please rebase against master. Spring Boot dropped JUnit 4 in latest snapshots and this is where compilation issues are coming from.

I did not even realise that it will be just about taking values from the environment. Since it's not specific to CloudWatch it could have been a general purpose MeterRegistryCustomizer, like EnvironmentVariablesMeterRegistryCustomizer, potentially added to Spring Boot. What do you think @eddumelendez?

I also found out later that getting the values from the Environment would be a more straight forward solution. Still not related to CloudWatch, however still related to AWS, that is why looks like it makes sense to be on the aws module. But please, let me know if you guys have a different opinion.

I did not even realise that it will be just about taking values from the environment.

In this case looks like is due to properties are loaded by AmazonEc2InstanceDataPropertySource. But, if they are available as a system environments will be loaded by spring-boot too.

Since it's not specific to CloudWatch it could have been a general purpose MeterRegistryCustomizer

Yes, I like the idea to customize but I think it will be general purpose I guess. So, MeterRegistryCustomizer will be better I think.

Hi @eddumelendez, thanks for the feedback.

In this case looks like is due to properties are loaded by AmazonEc2InstanceDataPropertySource. But, if they are available as a system environments will be loaded by spring-boot too.

Yes, the props are loaded by AmazonEc2InstanceDataPropertySource.
Regarding of how the variables are available, when I mentioned Environment I referred to Spring Environment. They are not available as system env variables.

Hi @eddumelendez @maciejwalkowiak, how should we proceed here?

Thank you @renanreismartins for your patience. We needed some time to digest it. We've decided that this should not be a part of Spring Cloud AWS as fetching properties from environment - as much as handy it is - is not Spring Cloud AWS specific. I think you can consider proposing this change to Spring Boot project. For now I believe it will be enough for Spring Cloud AWS to update reference documentation on how to add EC2 metadata to Micrometer using custom MeterRegistryCustomizer. Is this something you would like to do?

Hi @maciejwalkowiak, at first glance it looks like as just getting the properties from the environment. There is more to it, the purpose is to retrieve AWS metadata and add to the metrics, it just turned that the metadata is already in the environment.
Currently, every developer that needs the metadata in the metrics tags, has to write an MeterRegistryCustomizer and inject the metadata there. To balance both points of view, I agree that it is not a big deal, my point is that it is a very common requirement so we could just provide the option of configuring on the properties what metadata they wanted on the metrics tag.
Saving the developer to create the custom MeterRegistryCustomizer, creating property class and wiring everything up.
If after taking it in consideration you still think we should go with the documentation, I will add it after the section
Using instance tags (https://github.com/spring-cloud/spring-cloud-aws/blob/master/docs/src/main/asciidoc/spring-cloud-aws.adoc#using-instance-tags)
Please let me know what is your final decision.

Apologies @renanreismartins for keeping you waiting so long. In the end we've decided to not provide this customizer out of the box.


feat: basic support mobile mode.

including:
navbar show and hide,
similar fade animation,
auto close when select new convo,
mobile title will change with convo,
new chat button.

not sure if it match your expect. but I do really need mobile version🤣

This looks great! I understand, and I haven't gotten to it because mobile styling is not a priority for me. I would like to troubleshoot how the messages seem to re-render upon conversation. I noticed the edit user message button behaves differently on the official site with mobile styling, but I can get around to this when I add that functionality!

yep I agree. For me, make a work anyway is first thing to do, my pr is also not a 100% copy of official looking. but it work🤣

Thanks so much for your contributions!


Connection Refused

I'm using zuul proxy for redirect requests (I use zuul filter to determine what origin server the request go) and load balancer (ribbon). I have 3 pools (or services-ids) on my configuration application.yml, for example:
`hystrix:
command:
default:
execution:
isolation:
thread:
timeoutInMilliseconds: 120000
ribbon:
ReadTimeout: 130000
ConnectTimeout: 130000
eureka:
enabled: false
zuul:
ignoredServices: "*"
routes:
sales:
stripPrefix: false
path: /sales/**
service-id: sales-blue
customer:
stripPrefix: false
path: /customer/**
service-id: customer-blue
filter:
configuration:
blueOrGreen:
enabled: true
regex: '^[\d]+[0]$'
routeMatch: sales-green
routeNoMatch: sales-blue
sales-blue:
ribbon:
listOfServers: <IP_ADDRESS>:8080, <IP_ADDRESS>:8080
ServerListRefreshInterval: 15000
sales-green:
ribbon:
listOfServers: <IP_ADDRESS>:8080, <IP_ADDRESS>:8080
ServerListRefreshInterval: 15000
customer-blue:
ribbon:
listOfServers: <IP_ADDRESS>:8080, <IP_ADDRESS>:8080
ServerListRefreshInterval: 15000
customer-green:
ribbon:
listOfServers: <IP_ADDRESS>:8080, <IP_ADDRESS>:8080
ServerListRefreshInterval: 15000`
The zuul pre filter set a service-id using headers parameters, so the zuul proxy route request for correct origin server.
My problem is when one pool is offline and zuul proxy redirect a request for it then occurrs "Connection Refused" error (it's correct, why the server is down, i know). I want zuul proxy don't redirect when server is offline, is there any way for the zuul proxy to find out that the server is offilne?

Sounds like you might want to take a look into using Ribbon's IPing interface to have Ribbon check on the health of the servers.

Thanks Ryan!
I tried to use IPing interface, but it seems that I will also have to use Eureka to check on the health of the servers. This is a problem for me because my server side application runs with Jboss EAP 5.2, not Spring Boot. Is there anyway to make it work under these conditions?

The IPing interface has nothing to do with eureka.

I implemented this class:
`@Configuration
public class RibbonConfiguration {
    @Autowired
    IClientConfig ribbonClientConfig;

    @Bean
    public IPing ribbonPing(IClientConfig config) {
            return new PingUrl();
    }

    @Bean
    public IRule ribbonRule(IClientConfig config) {
            return new AvailabilityFilteringRule();
    }

}`
However when I started my application I got this log:

APPLICATION FAILED TO START

Description:
Field ribbonClientConfig in com.test.RibbonConfiguration required a bean of type 'com.netflix.client.config.IClientConfig' that could not be found.
Action:
Consider defining a bean of type 'com.netflix.client.config.IClientConfig' in your configuration.
[WARNING]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:506)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ribbonConfiguration': Unsatisfied dependency expressed through field 'ribbonClientCon
fig'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean found for dependency [com.netflix.client.config.IClientConfig]: expected at least 1
bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcess
When I run without @Configuration the application starts but IPing doesn't occur.

Follow the docs on how to configure ribbon beans http://cloud.spring.io/spring-cloud-static/Camden.SR4/#_customizing_the_ribbon_client


new qpter issue (at least on my end!)

After trying the pipx install pter[qt] option, I'm now getting:

Traceback (most recent call last):
File "/home/jason/.local/pipx/venvs/pter/lib/python3.11/site-packages/pter/qtui.py", line 1257, in update_search
self.searcher.parse()
File "/home/jason/.local/pipx/venvs/pter/lib/python3.11/site-packages/pter/searcher.py", line 322, in parse
self.casesensitive.can_lowercase(''.join(self.contexts | self.not_contexts)):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'can_lowercase'
Aborted

Not sure if that's something wrong with my machine or qpter.

Pretty sure it's an issue with qpter. I'll look into it!

There was a problem with qpter's dealing with case-sensitive search option 'smart'. It's fixed in 3.16.3.
Thanks again for pointing this out! Let me know if there are more problems :)

Thank you for jumping on these so quickly!

No problem - I hate to have these types of bugs linger.


Capitalize for Unix/Linux

This morning i found this error when i was installing it. I think it only appears on OS like ubuntu and not on windows OS

Thanks @rricote


Bug in stats colour bar indication

The colour of the stats bar for a character doesn't go green before an imminent promotion.

Simple coding error.


chore(main): release 1.12.2

:robot: I have created a release beep boop
1.12.2 (2024-11-02)
Bug Fixes

build (c187580)
deprecations (99034c7)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.12.2
:sunflower:


[AutoPR] datafactory/resource-manager

Created to accumulate context: datafactory/resource-manager

Build output:

Build output:

Build output:

Build output:

Build output:

Build output:

Build output:

Build output:

Build output:

Build output:

Closing PR that is older than 1 month.


fix command to set tags

I used to wrong function for the localleader binding to set tags in org files. Sorry.

Good catch, thanks!


Debug output to a file

Thank you for the great product!
Is it possible to add option to log debug output to a file while app running as daemon in background?

Please take a look at nohup command


False positive for "Style/HashSyntax" when using a variable as a hash key

If you use the same variable as both a hash key and its value, then ruboсop wants to omit the value. The proposed autocorrection breaks the semantics of the code.
Expected behavior
No offences for the following code:
# frozen_string_literal: true

var = 1
{ var => var }

Actual behavior
For /home/meh/Projects/rubocop-test: Default configuration from /home/meh/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/bundler/gems/rubocop-8ae9e0f2081d/config/default.yml
Inspecting 1 file
Scanning /home/meh/Projects/rubocop-test/hash.rb
Loading cache from /home/meh/.cache/rubocop_cache/da7c0adf3cdca36c6db455c7f909e01abe58503a/0536d18c9eb040c724be8df71fd74a67730b58ef/027b8e17147ee3c7f4fce30a50ffb44ff511b6cb
C

Offenses:

hash.rb:4:10: C: [Corrected] Style/HashSyntax: Omit the hash value.
{ var => var }
         ^^^

1 file inspected, 1 offense detected, 1 offense corrected
Finished in 0.18334346099800314 seconds

The code after autocorrection:
# frozen_string_literal: true

var = 1
{ var: }

Steps to reproduce the problem
See above
RuboCop version
❯ rubocop -V
1.25.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.15.1, running on ruby 3.1.0 x86_64-linux)

This is not a false positive because it is an expected behavior of EnforcedShorthandSyntax: always with Ruby 3.1. If you would not like to omit the hash value, please set EnforcedShorthandSyntax: never or EnforcedShorthandSyntax: either.
https://docs.rubocop.org/rubocop/1.25/cops_style.html#enforcedshorthandsyntax-always-default

@koic hash value omission is only possible then key is a Symbol, otherwise it just breaks the code like in the example above.

I've updated the examples with comments reflecting the result of running the code

Ah, you are right. It's my oversight.


fix for circular structure error when setting ttl - fixes #469

When ttl is enabled on a new collection, you will get a TypeError: Converting circular structure to JSON  error. This PR will fix it.

@dbubs cheers!!


sha1sum breaks the system!

The installation of mbedTLS generate a sha1sum program, the same one provided by coreutils on debian/ubuntu.
When the mbedTLS version of sha1sum is installed (/usr/local/bin/), it generate a lot of conflicts when using the package manager as it claims there is some missing symbols (sha1_file).
PLEASE rename your program, prefix it with "mbed" or something: mbed_sha1sum. I wasted hours running a system with broken packages!, installing a Kernel puts the system very unstable
update-initramfs: deferring update (hook will be called later)
initrd.img(/boot/initrd.img-3.19.0-33-generic
) points to /boot/initrd.img-3.19.0-33-generic
 (/boot/initrd.img-3.19.0-33-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-3.19.0-33-generic.postinst line 491.
vmlinuz(/boot/vmlinuz-3.19.0-33-generic
) points to /boot/vmlinuz-3.19.0-33-generic
 (/boot/vmlinuz-3.19.0-33-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-3.19.0-33-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-33-generic /boot/vmlinuz-3.19.0-33-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.19.0-33-generic /boot/vmlinuz-3.19.0-33-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-33-generic /boot/vmlinuz-3.19.0-33-generic
update-initramfs: Generating /boot/initrd.img-3.19.0-33-generic
sha1sum: symbol lookup error: sha1sum: undefined symbol: sha1_file
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.19.0-33-generic.postinst line 1025.
dpkg: error processing package linux-image-3.19.0-33-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-extra-3.19.0-33-generic:
 linux-image-extra-3.19.0-33-generic depends on linux-image-3.19.0-33-generic; however:
  Package linux-image-3.19.0-33-generic is not configured yet.

Perhaps this is a problem with cmake configuration, because when using regular make these programs were always installed with a prefix in their names. Anyway, there is no sha1sum at all since b327168 but I noticed there are outdated project files for Visual Studio still included in the tree.

ARM Internal Ref: IOTSSL-544

We're going to investigate if we can prefix those programs with CMake too, but in the meantime the workaround is indeed to use plain old Make, whose "install" target correctly prefixes the program names.

sha1sum is no longer part of the main mbed TLS package. It remains part of older versions we still maintain, but for backwards compatibility I wouldn't want to either change the name or remove it from those older versions.
Therefore closing this issue, without a fix.


Digital Miner Auto-Eject not functioning

Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description: I set up a Digital Miner with an logistical transport pipe leading to a sorter, and out of nowhere the auto-eject feature stops working and it begins to fill the Digital miner Item buffer slots.  I broke the digital miner, re-placed it down and set up all new filters and set it to auto-eject again and it still wont eject.
Steps to reproduce: I dont even know what led up to it bugging out

Version (make sure you are on the latest version before reporting):
Forge: <IP_ADDRESS>11
Mekanism: 1.12.2-<IP_ADDRESS>0
As well as
-MekanismGenerators 1.12.2-<IP_ADDRESS>0
-MeknismTools 1.12.2-<IP_ADDRESS>0
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

Show your configurations and the destinations

It works just fine for me


add epd2in13g.py

from: https://github.com/waveshareteam/e-Paper/blob/master/RaspberryPi_JetsonNano/python/lib/waveshare_epd/epd2in13g.py

This one can display black, white, yellow and red, so the interface to display color is slightly difference.
https://www.waveshare.com/wiki/2.13inch_e-Paper_HAT_(G)_Manual#Overview
It maps the input image to the nearest color in its color palette. Previous single color modules require a b&w image and a color image. So it will require some extra changes.

I don't have this this display to test so this is stuck for now.


MAINT: Update n_threads to work with prim. unions

The changes proposed here break the existing signature(s) for the method(s) implicated.

Yeah that's really my only concern with this, how should we handle it? We could leave 0 in for a bit longer, and have a redundant argument set

That could work for me, although I am also not super concerned about breaking API with the start of the 2020 release cycle.


Timeout with a proxy ETIMEDOUT

The action times out when trying using it from a self-hosted node behind a proxy.
It errors out with a timeout as in this workflow.
Any help would be appreciated, and thanks for making this action available.

I was able to resolve this issue by rebuilding the github-status-action-v2 repo and updating the Octokit API calls to use .rest.
See https://github.com/guibranco/github-status-action-v2/pull/60

@Geekdude, big thanks for your outstanding effort on this pull request! I would greatly appreciate your contributions. 🙌
@williamfgc, could you please test the new version and confirm that is now working?

Fixed by #60


Add an event "alexa_media_alarm_dismissal_event"

Closes #1014. This does 4 things:

Add an event "alexa_media_alarm_dismissal_event" any time an alarm is dismissed.
Add a status attribute to notification sensors
Add a dismissed attribute to notification sensors. This includes all notification types. It is updated to the current time any time that sensor has its notification dismissed.
Change the alarm sensor so that a snoozed alarm is classified as "active".

4 is a small change in behavior. It seemed to make sense to me. A snoozed alarm is still active.

When this merges, I know I need to update the wiki to document all of this.
As a side note, I am still working on a way to support multiple alarm sensors and to support on/off actions for alarms. I'm still experimenting to see if I can come up with a nice solution.

Thanks looks good.


Drop NaNs at the start/end of a TimeSeries

Suggested function name: trim()
What do you think @LorenzRychener ?


past, participle verb meaning cut in english dictionary

Examples taken from MultiLanguage-Dictionary application

Fixing in tag "v0.2.4"


meta: move the control of max-deletes from chunk to meta

Codecov Report
Base: 55.62% // Head: 55.47% // Decreases project coverage by -0.15% :warning:

Coverage data is based on head (6ffb220) compared to base (31acc80).
Patch coverage: 28.12% of modified lines in pull request are covered.

:exclamation: Current head 6ffb220 differs from pull request most recent head faf6390. Consider uploading reports for the commit faf6390 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3227      +/-   ##
==========================================
- Coverage   55.62%   55.47%   -0.15%
==========================================
  Files         142      142
  Lines       33067    33144      +77
==========================================
- Hits        18392    18386       -6
- Misses      12729    12807      +78
- Partials     1946     1951       +5

Impacted Files
Coverage Δ

cmd/gc.go
12.41% <0.00%> (ø)

cmd/object.go
40.88% <0.00%> (ø)

pkg/chunk/cached_store.go
73.10% <ø> (+0.19%)
:arrow_up:

pkg/meta/config.go
53.84% <ø> (ø)

pkg/meta/interface.go
49.00% <ø> (ø)

cmd/mount.go
54.67% <25.00%> (-0.34%)
:arrow_down:

pkg/meta/base.go
63.79% <53.33%> (+0.21%)
:arrow_up:

cmd/umount.go
26.51% <0.00%> (-27.73%)
:arrow_down:

pkg/vfs/reader.go
76.26% <0.00%> (-3.01%)
:arrow_down:

cmd/objbench.go
58.67% <0.00%> (ø)

... and 21 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[BUG] no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null] on .opensearch-cluster-control

Describe the bug
Following upgrade to 2.18.0 on a single node cluster the .opensearch-cluster-control has number_of_replicas: "1".
Attempting to change this to number_of_replicas: "0" returns the following error even for the initial admin user.
{
"error": {
"root_cause": [
{
"type": "security_exception",
"reason": "no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"
}
],
"type": "security_exception",
"reason": "no permissions for [] and User [name=admin, backend_roles=[admin], requestedTenant=null]"
},
"status": 403
}
Related component
Indexing:Replication
To Reproduce
curl --location --request PUT 'https:///.opensearch-control-center/_settings'
--header 'Content-Type: application/json'
--header 'Authorization: Basic xxx'
--data '{"index.number_of_replicas":0}'
Expected behavior
The number of replicas should change from 1 to 0.
Additional Details
Host/Environment (please complete the following information):

OS: Container runnning on Docker on Rocky Linux 9.4
Version 2.18.0

Regular users are not able to access system indices and make changes. If you need direct access to a system index, you need to use the admin certificate when making a request: https://opensearch.org/docs/latest/security/configuration/system-indices/
Closing this issue.


gpg check optional

I've checked in my dev env that this patch works fine.
What is the CI doing exactly?

@alvarolmedo The issue with the tests is they are using strict variables, and package_source_check isn't always defined for all branches in params.pp. You'll need to define the variable in the other branches and set to undef.
Some more details about that here for reference https://docs.puppet.com/puppet/latest/lang_variables.html#unassigned-variables-and-strict-mode

What did you mean with the rest of branches?
I should do PRs in the rest of the branch of this repo?

Hey @alvarolmedo. The branches are the case $::osfamily 'RedHat' specifically, and missing in the other osfamily elements. They must be defined in the base docker::params and set to undef. An example is say $storage_config_template.

@alvarolmedo Is this PR still valid? As there has been no update on this since Feb.

So sorry. I can't review the PR the last months.
Please give me a pair of days to reply.


fix fix same sql return wrong result when switch database with use db and enable sql cache

It will return wrong result when running same sql in different db with enable_sql_cache=true
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run build all

run buildall


Artifactory artifact support

This branch provides the ability to use buildkite-agent artifact <upload|download> with an Artifactory instance.
arty_uploader.go and arty_downloader.go are plugged into the artifact_uploader and artifact_downloader to connect to an instance configured through three environment variables:
# point to an artifactory instance like https://artifactory.com/artifactory
# Note that when using the jfrog CLI, this would be expected to include the /artifactory postfix on URL.
# That same expectation follows here
BUILDKITE_ARTIFACTORY_URL
 # a username and password configured in artifactory
BUILDKITE_ARTIFACTORY_USER
BUILDKITE_ARTIFACTORY_PASSWORD

The uploader will store artifacts in the repository under a folder matching the Job ID that uploaded it. for instance, README.md uploaded during job id abcdefgh-ijkl-mnop-qrst-uvwxyz123456 will be in repo/abcdefgh-ijkl-mnop-qrst-uvwxyz123456
Willing to provide more context and documentation if needed!

Ooooh!

This looks really great @GaryPWhite! Super excited! I've got very little critical feedback, gave it a quick look at it looks generally excellent. I'll give it a more in-depth review this evening on the ✈

Worth noting that any documentation should now also include BUILDKITE_JOB_ID as a necessary variable to set if working outside of a BK pipeline

Let's merge this!

Docs: https://buildkite.com/docs/integrations/artifactory
Changelog: https://buildkite.com/changelog/77-new-artifactory-support-and-documentation


Can't connect to my own mosquitto server using arduino

I can't connect to the server using MRK1000. I've managed to connect from my laptop with python and I'm also able to use mosquitto_pub  / sub.
//#include <MQTTClient.h>
//#include <MQTTTest.h>

#include <WiFi101.h>
#include <PubSubClient.h>

/////// Wifi Settings ///////
char ssid[] = "internet";
char pass[] = "pass";

// Update these with values suitable for your network.
IPAddress server(1,1,1,1);
//byte server[] = {37,187,106,16};

void callback(char* topic, byte* payload, unsigned int length) {
  // handle message arrived
  Serial.println("Message received");
}

WiFiSSLClient sslClient;
//MQTTClient client;
PubSubClient client(server, "1883", callback, sslClient);

void setup() {
  Serial.begin (9600);

  // attempt to connect to WiFi network:
  Serial.print("Attempting to connect to WPA SSID: ");
  Serial.println(ssid);

  while (WiFi.begin(ssid, pass) != WL_CONNECTED) {
    // unsuccessful, retry in 4 seconds
    Serial.print("failed ... ");
    delay(4000);
    Serial.print("retrying ... ");
  }

  Serial.println("Connected to WiFi");
//  client.begin("mqtt.mydomain", 1883, sslClient);

  Serial.println("Connecting to cloud");

   char namez[] = "u";
   char passz[] = "p";
   if (client.connect("arduinoClient")) {
        Serial.println("Client connected");
        client.subscribe("/notification/turnlighton");
   }
   else{
          Serial.println("Client not connected");
   }

  client.publish("test", "hello from mkr1000");

}

void messageReceived(String topic, String payload, char * bytes, unsigned int length) {}

void loop() {
//  Mkr1000.poll();

//  Mkr1000.writeProperty("lol", "oh...");

//  delay(1000);
//  Mkr1000.writeProperty("lol", "yeah!");

  delay(1000);
}
////

What output do you get?
What return code does client.connect return with?

I think there may be a problem with my server. I've inspected the logs:
New connection from x.x.x.x on port 1883.
Socket error on client <unknown>, disconnecting.

client.connect returns 0

You are not calling client.loop in your main loop. This prevents the client from ever reading from the network, so will eventually timeout and disconnect without receiving any messages.

I found out what's wrong. You can close the issue.
I've been using WifiSSLClient the whole time, which connects only via SSL. I should have used WifiClient.


Downloading files - 302 Found without Location header

Category

[ ] Question
[x] Documentation issue
[x] Bug

Observed Behavior
Date: Thu, 29 Aug 2019 07:37:58 GMT
request-id: a535cbfd-19dd-4808-8dcd-610bd7b9295c
By making the request:
GET https://graph.microsoft.com/v1.0/me/drive/items/{$itemId}/content
Authorization: Bearer XXXXXX

Received 302 Found response without Location header and without body.
Response headers:
{
  ["Cache-Control"]=>
  array(1) {
    [0]=>
    string(7) "private"
  }
  ["Content-Type"]=>
  array(1) {
    [0]=>
    string(10) "text/plain"
  }
  ["request-id"]=>
  array(1) {
    [0]=>
    string(36) "a535cbfd-19dd-4808-8dcd-610bd7b9295c"
  }
  ["client-request-id"]=>
  array(1) {
    [0]=>
    string(36) "a535cbfd-19dd-4808-8dcd-610bd7b9295c"
  }
  ["x-ms-ags-diagnostic"]=>
  array(1) {
    [0]=>
    string(137) "{"ServerInfo":{"DataCenter":"North Europe","Slice":"SliceC","Ring":"3","ScaleUnit":"001","RoleInstance":"AGSFE_IN_9","ADSiteName":"NEU"}}"
  }
  ["Duration"]=>
  array(1) {
    [0]=>
    string(8) "342.1191"
  }
  ["Strict-Transport-Security"]=>
  array(1) {
    [0]=>
    string(16) "max-age=31536000"
  }
  ["Date"]=>
  array(1) {
    [0]=>
    string(29) "Thu, 29 Aug 2019 07:37:58 GMT"
  }
  ["Connection"]=>
  array(1) {
    [0]=>
    string(5) "close"
  }
}

Expected or Desired Behavior
I expect to receive the file content or 302 Found response with Location header from which I can download the content of the file.
Steps to Reproduce
Just make a request do download a file from oneDrive.
IMPORTANT: I encounter this issue when the request is made from a server located in Ireland(EU west), but when I make request from a server located in Albania (EU South-east) everything is Ok(I get the file content on request GET https://graph.microsoft.com/v1.0/me/drive/items/{$itemId}/content)
Thank you.

I'm self closing this issue since the problem was on my client side. The client was removing Location header.


Dynamically allow/restrict access to public users

Describe the feature you'd like to request
I'd like to dynamically change a model's read authorization based on whether or not the owner permits the model to be public or not. My use case example is a set of Images that an owner can individually set to be privately visible (owner only) or publicly visible (authenticated AND unauthenticated users) on their profile. I was thinking of restricting read access to the Image based on dynamic Cognito Group membership, but it doesn't seem like there is a way by default to specify an unauthenticated user as part of a "public" cognito group.
Describe the solution you'd like
I would like to have the option to specify a field in my graphql schema which could allow for dynamic public authorization based on the value of the field. Here is an example schema for an Image model describing my use case:
type Image
  @model
  @auth(
    rules: [
      { allow: owner, operations: [read, update, delete] }  // owner
      { allow: private, provider: iam }  // admin
      { allow: public, provider: iam, publicField: "isPublic", public: [true], operations: [read] }  // public only if field isPublic == true
    ]
  ) {
  id: ID!
  url: String!
  isPublic: Boolean!
  @auth(
      rules: [
        { allow: owner, ownerField: "user", operations: [read, update] }  // owner can update
        { allow: private, provider: iam }  // admin can update
      ]
    )

}

To elaborate on the above example, it would be nice to be able to specify a whitelist of values that a field can have to enable authorization on the model. So the isPublic field can have the value 'true' to allow public authorization, otherwise if 'false' or any other value don't enable public authorization.
Describe alternatives you've considered
One alternative that I was recommended was to use a custom auth resolver on a field that checks the field's value and enables/disables public access. I did not explore this option as I ended up switching to CDK for my project's backend stack, and implementing custom lambda resolvers for my queries and mutations.
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Any news on this?


#14985: Update the examples for binary backward doc

Ticket
https://github.com/tenstorrent/tt-metal/issues/14985
Problem description
To update the examples for binary backward documentation
What's changed
Updated the examples for the following binary backward ops

concat_bw
addalpha_bw
mul_bw

Checklist

[x] Post commit CI passes

Documentation screenshots

https://github.com/tenstorrent/tt-metal/actions/runs/11876798347 - passed


Added Live Share link

Updated README.md :+1:

Added Live Share link

This link is valid only when author is online.

Easy way to join the collaboration  and code at the same time.

Last Update with no errors!

Updated live share extension of Visual Studio Code for easy work at same time.
👍


Update Yi platform to make use of async/await

Description:
Updates the Yi camera platform to make use of async/await (instead of the old syntax).
Related issue (if applicable): N/A
Pull request in home-assistant.github.io with documentation (if applicable): N/A
Example entry for configuration.yaml (if applicable):
camera:
  - platform: yi
     name: Kitchen Camera
     host: kitchen-camera.phil.lan
     username: !secret yi_username
     password: !secret yi_password
     ffmpeg_arguments: -s 800x450

Checklist:

[x] The code change is tested and works locally.

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

💃 thanks! 🐬


Fix for lexing J operator ?

Fix for #1149
I made the lexer match ? as an operator and also added tests for it.

Merged, thanks!


adds a small unit test suite for chunking

as a small addition to chunking, this would add a few basic tests to test chunking behavior

For me there is a problem when I try to run the the locally.
The test will not run, I think that this has to do something with the working directory.
When I set the working directory to the Testing folder, then it can not find the tokens.env. (At least for me this is under QAChat/tokens.env)
And when I set the working directory to QAChat/Data_Processing then it can find the tokens.env. But then the dummydata is not found.
So a few fixes that should work (for how I placed the tokens.env):

move the tokens.env to the main folder. and then use Testing/ QAChat as a working directory. If we do this then we should update our build process guide.

We move the Testing folder into QAChat (then we have to update the github actions)

We load the relativ path tokens.env or the dummy data differently, such that we can set the working directory to a fixed folder

But do you possibly have another solution there? And what do you use as your working directory and where is your tokens.env to let the test run?

Hey, I wanted to share a friendly tip for documenting your functions and methods. Instead of commenting above the function definition, it's more conventional to use docstrings (""" """).

For me there is a problem when I try to run the the locally.
The test will not run, I think that this has to do something with the working directory. When I set the working directory to the Testing folder, then it can not find the tokens.env. (At least for me this is under QAChat/tokens.env)
And when I set the working directory to QAChat/Data_Processing then it can find the tokens.env. But then the dummydata is not found.
So a few fixes that should work (for how I placed the tokens.env):
1. move the tokens.env to the main folder. and then use Testing/ QAChat as a working directory. If we do this then we should update our build process guide.

2. We move the Testing folder into QAChat (then we have to update the github actions)

3. We load the relativ path tokens.env or the dummy data differently, such that we can set the working directory to a fixed folder

But do you possibly have another solution there? And what do you use as your working directory and where is your tokens.env to let the test run?

Well I basically did option 1, I just thought it was a local problem for me so I left it as is. Sorry I should have mentioned / communicated that. I would also suggest to do it like this, since we only would have to adapt the paths then which seems the easiest way to me personally.

Hey, I wanted to share a friendly tip for documenting your functions and methods. Instead of commenting above the function definition, it's more conventional to use docstrings (""" """).

Personally I think that the functions can be left without comments since its rather obvious what they do. Or would you prefer comments here?


feat: add TLS CA support to wash

Feature or Problem
NATS servers support TLS, which means sometimes you need to be able to provide certificates when instantiating a client.
This adds support for providing a CA certificate to wash with a command line flag. I opted not to add mTLS support by adding flags for a certificate and a key, but it would not be that hard now that the scaffolding is in place. I also chose not to add the same support to the wasmCloud host since you can simply add a CA to a leaf running as a sidecar, which is a understood deployment model. However that would also be a relatively straightforward change by adding the necessary paths to the control and RPC connections.

Related Issues

Release Information

Consumer Impact

Testing
Tested locally with a NATS server using a self-signed CA and certificate.
Unit Test(s)

Acceptance or Integration

Manual Verification

@protochron this must have slipped though the cracks. Did you still want this in wash?

Yes, we still need this in wash