[Hidden] css implementation handle custom className

Add support for provided className on Hidden component when implementation is css
Closes #10161

@Vincz thank you, you did a great job!

@Vincz @oliviertassinari
FYI typescript errors when adding className to <Hidden> as the definition has not been updated:
export interface HiddenProps {
  implementation?: 'js' | 'css';
  initialWidth?: Breakpoint;
  lgDown?: boolean;
  lgUp?: boolean;
  mdDown?: boolean;
  mdUp?: boolean;
  only?: Breakpoint | Breakpoint[];
  smDown?: boolean;
  smUp?: boolean;
  xlDown?: boolean;
  xlUp?: boolean;
  xsDown?: boolean;
  xsUp?: boolean;
}

The documentation also does not mention this:
https://material-ui.com/api/hidden/
As a temporary workaround:
          {/* note: needs the newline here to work
            // @ts-ignore */}
          <Hidden smUp implementation="css"
            className={classes.someClass}
          >
             Hello
          </Hidden>


add wandb workflow

create wandb workflow to trigger when add pr comment with /wandb prfix followed by a experiment id , automated replay will be generated with the wandb comparison report and model registry url

/wandb 2acwxb8n

/wandb 2acwxb8n

/wandb 2acwxb8n


Update cross-media-measurement-api for maximum_frequency move.

This change is

@renjiezh for Duchy changes


link to CONTRIBUTING.md is broken on homepage of https://thethingsstack.io/

Summary
Change link, e.g. to https://github.com/TheThingsNetwork/lorawan-stack/blob/v3.10/CONTRIBUTING.md
Current link https://github.com/TheThingsNetwork/lorawan-stack/blob/default/CONTRIBUTING.md doesn't appear to work.
Why do we need this ?
Fix link on homepage, so it's easier to find the document.
What is already there? What do you see now?
I get a HTTP 404 GitHub page when following the link.
What is missing? What do you want to see?

How do you propose to document this?

Can you do this yourself and submit a Pull Request?
could create a pull request to make it link to v3.10, but there might be better alternatives to link to the default branch?

Closed by https://github.com/TheThingsIndustries/lorawan-stack-docs/commit/58f41ec8dc416312ba83aec01f00f0d8c75e1811


revert using -S to configure source directory

related to: https://github.com/microsoft/vscode-cmake-tools/issues/2053

I don't understand this reversion. The code comments state that it's using the CMake File API for versions 3.15+, while -S has been in CMake since 3.13. The CMake File API itself was introduced in version 3.14, so there has never been a point in time where the File API worked, but -S did not.
See here:
https://github.com/microsoft/vscode-cmake-tools/blob/a6cbd3598acd908b34e9aa8b3b535a35d567f853/src/drivers/cmfileapi-driver.ts#L37-L39
In fact, it seems this class is protected by a check that cmake.isFileApiModeSupported is true, which is already guarded by a version check.
https://github.com/microsoft/vscode-cmake-tools/blob/a6cbd3598acd908b34e9aa8b3b535a35d567f853/src/cmake/cmake-executable.ts#L37
https://github.com/microsoft/vscode-cmake-tools/blob/a6cbd3598acd908b34e9aa8b3b535a35d567f853/src/cmake-tools.ts#L689-L699

You are correct. Because this was done in only one place I had assumed the file being edited was the base driver, but clearly this is not the case.  The other instance of this which should not be changed is here:
https://github.com/microsoft/vscode-cmake-tools/blob/a6cbd3598acd908b34e9aa8b3b535a35d567f853/src/drivers/legacy-driver.ts#L79
I assume that when this driver was added, it copied from there.  It is safe to make the change in the cmake-file-api driver without a version check.


[CLOSED] Replace document repository

 Issue by evilstreak
Thursday 24 July 2014 at 14:46 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/183

These commits move from storing document editions as standalone records to storing them embedded in a document record.
This will allow us to do more sane queries against the data, which will make providing features like pagination so we can handle 10,000 imported documents much simpler.
Tasks

[x] Write a migration to copy data from the old collection into the new collection
[x] Remove the unused repository and model
[ ] Tests for the new repository and model

evilstreak included the following code: https://github.com/alphagov/specialist-publisher/pull/183/commits

 Comment by bestie
Thursday 31 July 2014 at 14:13 GMT

The repository and persistence code is well tested by our acceptance tests at present and there are still some hacks in there to support transitioning to documents behaving more like manuals.
I suggest we don't write the unit tests until the next refactor.

 Comment by evilstreak
Friday 01 August 2014 at 08:14 GMT

:+1: This looks good. It needs a rebase, and then I think we should do a branch deploy to preview early next week and wail on the existing data a bit.

 Comment by bestie
Tuesday 12 August 2014 at 15:08 GMT

I believe this PR does not degrade functionality as it is currently impossible to roll back a document's attachments.

 Comment by kalleth
Wednesday 17 September 2014 at 15:35 GMT

I think I've just performed a successful rebase on branch https://github.com/alphagov/specialist-publisher/compare/replace-document-repository-rebased -- but it could use a review before force pushing to this branch @evilstreak @bestie

 Comment by evilstreak
Thursday 25 September 2014 at 08:34 GMT

Closing until we make time to revisit this work.


Release 1.6.5 is missing Module Folder

I'm using Carthage to pull down TrustKit and noticed that in the 1.6.5 release has a different layout of the .framework folder than the 1.6.4 release before it.
I've created a test with 1.6.4 to switch to 1.6.5

Create a new xcode project
Create a Cartfile
Add github "datatheorem/TrustKit" == 1.6.4 to the Cartfile
Add $(PROJECT_DIR)/Carthage/Build/iOS to the FRAMEWORK_SEARCH_PATHS
Run carthage update --platform iOS --new-resolver
Go back to xcode, open a swift file and add import TrustKit
and perform clean build of the project
Open up the Cartfile and change it github "datatheorem/TrustKit" == 1.6.5
remove the Carthage folder
Run carthage update --platform iOS --new-resolver
Go back to xcode, and perform clean build of the project

What happens:

After step 5 the contents of Carthage/Build/iOS/TrustKit.framework appears as:

$ ls -al Carthage/Build/iOS/TrustKit.framework
total 4704
drwxr-xr-x  7 developer  staff      224 Mar 19 20:01 .
drwxr-xr-x  6 developer  wheel      192 Mar 19 20:01 ..
drwxr-xr-x  8 developer  staff      256 Mar 19 20:01 Headers
-rw-r--r--  1 developer  staff      740 Mar 19 20:01 Info.plist
drwxr-xr-x  3 developer  staff       96 Mar 19 20:01 Modules
-rw-r--r--  1 developer  staff        8 Mar 19 20:01 PkgInfo
-rwxr-xr-x  1 developer  staff  2398200 Mar 19 20:01 TrustKit

At step 6, the TrustKit.framework is found via the FRAMEWORK_SEARCH_PATHS and import TrustKit works

After step 9:
$ ls -al Carthage/Build/iOS/TrustKit.framework
total 4704
drwxr-xr-x  6 developer  staff      192 Mar 19 20:10 .
drwxr-xr-x  6 developer  wheel      192 Mar 19 20:10 ..
-rw-r--r--  1 developer  staff      740 Mar 19 20:10 Info.plist
-rw-r--r--  1 developer  staff        8 Mar 19 20:10 PkgInfo
-rwxr-xr-x  1 developer  staff  2398188 Mar 19 20:10 TrustKit
drwxr-xr-x  8 developer  staff      256 Mar 19 20:10 public

After step 10:

Xcode now reports No such module 'TrustKit' as the Modules/module.modulemap is missing

Details:

carthage 0.34.0
Xcode 11.1 (11A1027)
Swift 5.1

Attachment:
I'm attaching my demo code where I got to step 9 in the reproduction steps: TrustKit_Test_1.6.5.zip
Steps to test

Download the binary;
Run carthage update --platform iOS --new-resolver (this will download 1.6.5);
Open the A.xcworkspace and perform clean build of the project.

Question:
Could you please advice how to import TrustKit 1.6.5 without module.modulemap?
I'm happy to provide additional feedback.
Cheers,
Willem

Same problem here: version 1.6.5 does not work with carthage and causes a "No such module 'TrustKit'" error in Xcode.
I am running carthage 0.34.0 and Xcode 11.3.1 (11C504) on macOS Mojave 10.14.6.
Version 1.6.4 works just fine.

+1

+1

+1

I tried setting up Carthage after merging #230 (commit ec7cc7599559517d479265c9bf223e477ae5f88f) and it seemed to work.

Released as v1.7.0.


<For> panics when no parent is found

The following error (originating from each.rs:689:45)
ok-14eeb0630fba0fef.js:316 panicked at 'called `Result::unwrap()` on an `Err` value: JsValue(InvalidNodeTypeError: Failed to execute 'setStartBefore' on 'Range': the given Node has no parent.
Error: Failed to execute 'setStartBefore' on 'Range': the given Node has no parent.
    at http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef.js:552:21
    at handleError (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef.js:241:18)
    at imports.wbg.__wbg_setStartBefore_8e6e0f57eb922e33 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef.js:551:73)
    at web_sys::features::gen_Range::Range::set_start_before::h46a1bcc0e6acd02c (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[6477]:0x6164ad)
    at leptos_dom::components::each::apply_cmds::h36201b78da8b02bd (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[273]:0xc2850)
    at <leptos_dom::components::each::Each<IF,I,T,EF,N,KF,K> as leptos_dom::IntoView>::into_view::{{closure}}::ha10796ab77ff0069 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[190]:0x52a29)
    at <leptos_reactive::effect::Effect<T,F> as leptos_reactive::effect::AnyComputation>::run::heb8296b5f041a68b (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[217]:0x794e3)
    at leptos_reactive::runtime::Runtime::update::{{closure}}::hf0b6181b95189308 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[6997]:0x638eaf)
    at leptos_reactive::runtime::Runtime::with_observer::he70bc21b3d6648b9 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[4561]:0x578d68)
    at leptos_reactive::runtime::Runtime::update::h607d508bb92482a6 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[828]:0x2c488f))', /home/lukas/.cargo/registry/src/github.com-1ecc6299db9ec823/leptos_dom-0.2.5/src/components/each.rs:689:45

Stack:

Error
    at imports.wbg.__wbg_new_abda76e883ba8a5f (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef.js:319:17)
    at console_error_panic_hook::Error::new::hfdaedaff5aed9273 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[17751]:0x7a5a5d)
    at console_error_panic_hook::hook_impl::hd09abaec27218d55 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[4538]:0x57699a)
    at console_error_panic_hook::hook::ha3d03e0aeec5abef (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[19642]:0x7bf546)
    at core::ops::function::Fn::call::h57386142573e6411 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[17186]:0x79cbde)
    at std::panicking::rust_panic_with_hook::h560812122b50d13d (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[8583]:0x695479)
    at std::panicking::begin_panic_handler::{{closure}}::h444de343e52388a7 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[10566]:0x6f06fe)
    at std::sys_common::backtrace::__rust_end_short_backtrace::hfd641dea4342d358 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[21070]:0x7d1333)
    at rust_begin_unwind (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[15298]:0x779acc)
    at core::panicking::panic_fmt::hfa9ae79d6c4dc316 (http://<IP_ADDRESS>:4001/book-14eeb0630fba0fef_bg.wasm:wasm-function[18828]:0x7b4ccf)

was observed when using the following markup
<Show when=my_non_changing_signal fallback=|_cx| view! { cx,  }>
    <For
        each=my_changing_signal
        key=|my_entry| my_entry.id
        view=move |cx, my_entry| view! { cx,

"seems irrelevant"

        }
    />
</Show>

The error no longer appeared after wrapping the <For> element in an explicit
. This should probably not be required in this situation.
It seems that the calls to set_start_before and set_end_before
    range.set_start_before(opening).unwrap();
    range.set_end_before(closing).unwrap();

both require that opening and closing have a parent? This is at least is not checked right now.

Thanks. Agreed that it should not be required. The <For/> component is currently being rehabbed with some associated tests and clean-up due to an off-by-one error in a particular case (#533) so I'll keep this on my list to check when that work is done.

Sounds great!

This has tripped me up as well.
Here's a sample project to demonstrate the problem.

I'm no longer able to reproduce this against either of the provided examples. It may have been related to #1078. In any case, I'm going to close this as fixed... Let me know if you're still encountering this issue against latest git main and I can reopen it.

This error still occurs for me. Although I can't quite explain when it happens
When pressing enter in the input, from the markup below, everything works fine and the tag is added.
When the tags signal is updated from somewhere else, one of two things happen:

First time update (For was empty until now) Everything works as expected. Tags are added
Update after previous update (either by button click or input enter) The error occurs, and then For is not usable anymore

I am not 100% sure if this is still an error in Leptos or if I am using the For wrong in any way.
The markup:

    <For
        each=tags
        key=|item: &String| item.clone()
        view=|cx, item: String| {
            view! { cx,
                <span class="rounded-md border p-1 hover:bg-metroid cursor-pointer mx-1 text-xs flex items-center"
                    on:click=move |ev| {
                        let d = ev.target().expect("No target").dyn_into::<web_sys::HtmlSpanElement>().unwrap().inner_text();
                        // set_tags1.update(|s|{ //this also does not work, but that's a topic for another discussion
                        //     s.0.retain(|t| t != &d);
                        // });
                    }
                >
                    {item}

            }
        }
    />
    <input
        class="text-white placeholder-gray-400 bg-black border-0 focus:outline-none flex-grow ml-1"
        type="text"
        prop:placeholder=move || {if tags().0.len() > 0 { "Tags separated by <enter>" } else { "Tags separated by <enter> (required)" }}
        on:keydown=move |ev| {
            if ev.key() == "Enter" {
                let value = event_target_value(&ev);
                if value.len() > 0 {
                    set_tags2.update(|s|{
                        s.0.push(value);
                    });
                    ev.prevent_default();
                    ev.target().unwrap().dyn_into::<HtmlInputElement>().unwrap().set_value("");
                }
            }
        }
    />

The error

panicked at 'called `Result::unwrap()` on an `Err` value: JsValue(InvalidNodeTypeError: Failed to execute 'setStartBefore' on 'Range': the given Node has no parent.
Error: Failed to execute 'setStartBefore' on 'Range': the given Node has no parent.
    at http://localhost:3000/pkg/snac.js:655:17
    at handleError (http://localhost:3000/pkg/snac.js:295:38)
    at imports.wbg.__wbg_setStartBefore_16768752de106d95 (http://localhost:3000/pkg/snac.js:654:73)
    at web_sys::features::gen_Range::Range::set_start_before::h96f942a4e2a14dcb (http://localhost:3000/pkg/snac.wasm:wasm-function[4449]:0x58461c)
    at leptos_dom::components::each::apply_cmds::he3cc9519592ff309 (http://localhost:3000/pkg/snac.wasm:wasm-function[284]:0x10eb87)
    at  as leptos_dom::IntoView>::into_view::{{closure}}::h6036959e2e067b24 (http://localhost:3000/pkg/snac.wasm:wasm-function[279]:0x103fdf)
    at  as leptos_reactive::effect::AnyComputation>::run::hcb3fb0c0d1a5e9f2 (http://localhost:3000/pkg/snac.wasm:wasm-function[417]:0x206bd1)
    at leptos_reactive::runtime::Runtime::update::{{closure}}::h1a1429a704e6a2fb (http://localhost:3000/pkg/snac.wasm:wasm-function[5303]:0x5b8388)
    at leptos_reactive::runtime::Runtime::with_observer::hb8ef2bfe4199d859 (http://localhost:3000/pkg/snac.wasm:wasm-function[5563]:0x5c6586)
    at leptos_reactive::runtime::Runtime::update::h5b55679c2787f923 (http://localhost:3000/pkg/snac.wasm:wasm-function[854]:0x3943db))', /home/dikka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_dom-0.3.0/src/components/each.rs:692:45
Stack:
Error
at imports.wbg.__wbg_new_abda76e883ba8a5f (http://localhost:3000/pkg/snac.js:370:13)
at console_error_panic_hook::Error::new::h53975328d482b6c9 (http://localhost:3000/pkg/snac.wasm:wasm-function[12113]:0x683c8a)
at console_error_panic_hook::hook_impl::hc406df7ae9167657 (http://localhost:3000/pkg/snac.wasm:wasm-function[2841]:0x501116)
at console_error_panic_hook::hook::h2f56a5219f622277 (http://localhost:3000/pkg/snac.wasm:wasm-function[13112]:0x691583)
at core::ops::function::Fn::call::h49a136941c8dd361 (http://localhost:3000/pkg/snac.wasm:wasm-function[11617]:0x67c1b0)
at std::panicking::rust_panic_with_hook::h6ad5e2625393b2cc (http://localhost:3000/pkg/snac.wasm:wasm-function[5670]:0x5cbfc6)
at std::panicking::begin_panic_handler::{{closure}}::h93e72541ffd61b32 (http://localhost:3000/pkg/snac.wasm:wasm-function[7115]:0x60d67b)
at std::sys_common::backtrace::__rust_end_short_backtrace::h9d1952ad96bb3372 (http://localhost:3000/pkg/snac.wasm:wasm-function[15250]:0x6a5b6c)
at rust_begin_unwind (http://localhost:3000/pkg/snac.wasm:wasm-function[10093]:0x66019f)
at core::panicking::panic_fmt::h93b49f36550e1ecf (http://localhost:3000/pkg/snac.wasm:wasm-function[12844]:0x68dedd)

Are you using the master branch or the released version of Leptos (0.3)? The For component of 0.3 still has many problems.

That's it. I didn't check if any of the fixes mentioned here made it into a release yet.


fix: strip leading */*. from routes when deducing a host for dev

When given routes, we use the host name from the route to deduce a zone id to pass along with the host to set with dev session. Route patterns can include leading */*., which we don't account for when deducing said zone id, resulting in subtle errors for the session. This fix strips those leading characters as appropriate.
Fixes https://github.com/cloudflare/wrangler2/issues/1002

@JacobMGEvans @petebacondarwin What's happening here, I think, is that node_modules is being restored from cache, which blows away the symlinks that npm install has setup for workspaces. I dunno why it hasn't happened for mac/ubuntu. But this seems like a blocker. Can we revert the actions caching changes until we figure that out? (unless you have a better solution for my problem?)

Ah yes. I think when linux-like OSes zip up files they keep the symlinks but these are lost on Windows.
Maybe this didn't come up when we were testing, because re-running jobs might have just used the same workspace?
One option might be to run npm i if the node_modules were recovered from cache, since that might re-instantiate the links without actually doing any new installation?

omg I added npm install and look at this error 😳😳😳 https://github.com/cloudflare/wrangler2/runs/6453430257?check_suite_focus=true

Ok, looks good now!

I have regex101.com open every day lol


TextField isFocused on first enter page switches false/true then back to false

Problem description
When first entering page I click on TextField and the underline goes focused then goes off.  I have to click a second time on the TextField to maintain focus.  I can see the state isFocused: switches from false to true and back to false.  After the second click it stays at true.
I tested by simply adding  to a page.
Versions

Material-UI: 0.16.1
React: 15.3.2
Browser: All

Solved.


arm architecture?

I guess this is not for arm?
container,info,debug does not match this architecture

Initially image was build only for linux/arm64, because I've used it on RB5009.
Fixed in efa1fb0, please try now.

It works, thanks so much for the update.


Cutting a new Spark 2.1 release

This is a prerequisite to announcing upstream.
Steps:

[ ] Build a distribution with and without hadoop
[ ] Tag the commit, draft a github release, and upload the tar.gz files in (1)
[ ] Build and upload the images (appropriately tagged) to the kubespark repo
[ ] Fill in the release description on GitHub

@apache-spark-on-k8s/contributors
"blocking" PRs:

[x] https://github.com/apache-spark-on-k8s/spark/pull/415
[ ] https://github.com/apache-spark-on-k8s/spark/pull/412

Maybe we also want the bug fix #416, which seems almost ready to merge? The bug may impact many large jobs even when they don't use HDFS.

You mean https://github.com/apache-spark-on-k8s/spark/pull/412? Yeah, I think that's a good one to include as well!

Correct. #412.

PSA: Need an owner from the community for cutting this release. @erikerlandson is doing the 2.2 one, any volunteers for this? @apache-spark-on-k8s/contributors

@foxish I can help on cutting a new 2.1 release.

@foxish I don't seem to have permission to create a release.

Still need to build and upload the new images.

Published all images tagged with v2.1.0-kubernetes-0.3.1.


feat: Add static getter for TableDefinition in KafkaTools

This issue was auto-generated
PR: https://github.com/deephaven/deephaven-core/pull/5956
Author: robbcamera
Original PR Body
null

Worth noting that the dev work for this ticket has not yet been wired up in Python. Not sure if we want to wait for that or just forge ahead with this and then cover the Python when it's done.

No Python equivalent for the Java code has been requested. There is no timeline for a Python implementation/wrapping.


#690026: Replace deprecated unsubscribe method

Update version to 4.3.0

Change turns out not to do what we thought it does. Closing.

But then again, it is better to use mx.data.unsubscribe than this.unsubscribe. This is something I try to implement everywhere. What were you trying to solve?

We were trying to solve an error related to loading an image. It turned out
that the URL for the image was wrong, it pointed to the wrong port.
If you think mx.data.unsubscribe is still the better solution, please go
ahead and merge. But this.unsubscribe seems still to be a supported API.
Out of interest, why is mx.data.unsubscribe better?
2016-04-25 16:53 GMT+02:00 Jelte Lagendijk<EMAIL_ADDRESS>
But then again, it is better to use mx.data.unsubscribe than
this.unsubscribe. This is something I try to implement everywhere. What
were you trying to solve?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/mendix/DynamicImageViewer/pull/5#issuecomment-214372882

--
Reinout van Schouwen


M3-2887 Linode plan details

Description
Adding the plan details to be part of the Linode Summary heading (under the tabs) and removing the paper component from the sidebar.
Type of Change

Non breaking change ('change')

@johnwcallahan @alioso feedback has been addressed, thank you!


Install "create-react-native-app" failed on Windows NPM

I could not install "create-react-native-app" on Windows.

Environment info:

OS: Windows 10
Node: v8.1.3 (node v6.x also showed the same error)
NPM: 5.0.3
CMD as adminstrator

Error:

npm ERR! code EACCES
npm ERR! errno EACCES
npm ERR! FetchError: request to https://registry.npmjs.org/create-react-native-app failed, reason: connect EACCES <IP_ADDRESS>:443
npm ERR!     at ClientRequest.req.on.err (C:\Users\mathselse\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\node_modules\make-fetch-happen\node_modules\node-fetch-npm\src\index.js:68:14)
npm ERR!     at emitOne (events.js:115:13)
npm ERR!     at ClientRequest.emit (events.js:210:7)
npm ERR!     at TLSSocket.socketErrorListener (_http_client.js:400:9)
npm ERR!     at emitOne (events.js:115:13)
npm ERR!     at TLSSocket.emit (events.js:210:7)
npm ERR!     at emitErrorNT (internal/streams/destroy.js:62:8)
npm ERR!     at _combinedTickCallback (internal/process/next_tick.js:102:11)
npm ERR!     at process._tickCallback (internal/process/next_tick.js:161:9)
npm ERR!  { FetchError: request to https://registry.npmjs.org/create-react-native-app failed, reason: connect EACCES <IP_ADDRESS>:443
npm ERR!     at ClientRequest.req.on.err (C:\Users\mathselse\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\node_modules\make-fetch-happen\node_modules\node-fetch-npm\src\index.js:68:14)
npm ERR!     at emitOne (events.js:115:13)
npm ERR!     at ClientRequest.emit (events.js:210:7)
npm ERR!     at TLSSocket.socketErrorListener (_http_client.js:400:9)
npm ERR!     at emitOne (events.js:115:13)
npm ERR!     at TLSSocket.emit (events.js:210:7)
npm ERR!     at emitErrorNT (internal/streams/destroy.js:62:8)
npm ERR!     at _combinedTickCallback (internal/process/next_tick.js:102:11)
npm ERR!     at process._tickCallback (internal/process/next_tick.js:161:9)
npm ERR!   message: 'request to https://registry.npmjs.org/create-react-native-app failed, reason: connect EACCES <IP_ADDRESS>:443',
npm ERR!   type: 'system',
npm ERR!   errno: 'EACCES',
npm ERR!   code: 'EACCES' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR!      C:\Users\mathselseAppData\Roaming\npm-cache\_logs\2017-07-08T19_12_10_784Z-debug.log

Please help!
Thanks,

npm 5 isn't supported. the error message that you mention here is in the npm docs as a common problem :)

@brentvatne so, what's the solution? o.O

It's in getting started inside the readme, sorry not at a computer atm

why doesnt it have a solution.


Update documentation on how to add new ops

Updated the doc to include verifiers and a few tips on how to locate info.
Doc only update.
Signed-off-by: Alexandre Eichenberger<EMAIL_ADDRESS>

Jenkins Linux amd64 Build #2185 [push] update add new ops (#907... started at 23:44


Allow adding/deleting/renaming files from the tree view

In order to make scratch swings more usable, we need to allow users to add/delete/rename files. Since we already expose the CodeSwing tree while you're in a swing, that would be the natural place to enable it.

This is now shipped! 🚀


Can't detect hard-coded reference with - in name

Describe the bug
In BigQuery, table references can contain - in them. Test find_all_hard_coded_references.sql does not detect this because regex (\w+) does not include the hyphen (-) character.
Steps to reproduce
Sample model with hard-coded reference
SELECT
  *
FROM
  `project-name.dataset_name.table_name`

Expected results
09:17:43  19 of 25 FAIL 1 is_empty_fct_hard_coded_references_ ............................ [FAIL 1 in 0.82s]

Actual results
09:20:45  19 of 25 PASS is_empty_fct_hard_coded_references_ .............................. [PASS in 0.95s]

Screenshots and log output
This is after changing all regex from (\w+) to (\w+-?\w+) in find_all_hard_coded_reference.sql macro. Elswise, everything passes.

System information
packages:
  - package: dbt-labs/dbt_utils
    version: 1.1.1
  - package: dbt-labs/codegen
    version: 0.12.1
  - package: elementary-data/elementary
    version: 0.13.1
  - package: calogica/dbt_expectations
    version: 0.10.1
  - package: dbt-labs/dbt_project_evaluator
    version: 0.8.1

Which database are you using dbt with?

[ ] postgres
[ ] redshift
[x] bigquery
[ ] snowflake
[ ] trino/starburst
[ ] other (specify: ____________)

The output of dbt --version:
Core:
  - installed: 1.7.5
  - latest:    1.7.6 - Update available!

Plugins:
  - bigquery: 1.7.3 - Up to date!
  - postgres: 1.6.1 - Not compatible!

Are you interested in contributing the fix?
Tested locally and replaced all regex from (\w+) to (\w+-?\w+) which makes - optional. After the change, test started detecting hard-coded references with hyphen (-) character. I don't know if this will affect something else, but in my case, it worked.
https://github.com/dbt-labs/dbt-project-evaluator/blob/main/macros/find_all_hard_coded_references.sql

hey @simmartynas! are you willing to open a PR with this change? I think it's a good one!

Fix has been merged


[BUG] X Axes time scale (hour format) in chart.js not working

Expected Behavior
Graph should be displayed with same representation except with the labels that should be in intervals
Expected -

Current Behavior
By providing the type time and unit hour in x axes label for the bar type chart, Graph behaves incorrectly
Current Behaviour

Possible Solution
Graphh shoul displayed correctly
Steps to Reproduce (for bugs)

Refer attached snapshot and jsfiddle

Environment

Chart.js version: 2.7.2
Browser name and version:
Link to your project:

time.format is deprecated. Use time.parser instead.
As 'HH' is specified as (a parsing format)[https://momentjs.com/docs/#/parsing/string-format/], 24 hour time (0..23) must be used.
In order to offset grid lines and prevent bars on the edges from being hidden, you can use gridLines.offsetGridLines: true and offset: true.
If you want to show a grid line per hour, use time.stepSize: 1.

data: {
  labels: ['0','1','2','3','4','5','6','7','8','9','10','11','12','13','14','15','16','17','18','19','20','21','22','23'],
  ...
},
options: {
  scales: {
    xAxes: [{
      time: {
        parser: 'HH',
        stepSize:1,
        ...
      },
      gridLines: {
        offsetGridLines: true
      },
      offset: true,
      ...

Closing as solved


Expand the Observables guide page

It’s currently lacking in as much content as was in the original version.
Related to #1615

Added the page in this commit: https://github.com/bitovi/canjs/commit/d8aed495332561167f4c9628701b0b41db62a8e8
A preview can be seen here: http://canjs.com/2.3-pre/guides/Observables.html


Cli supports zset data structures

i do it

This issue seems to be incomplete; I think I can handle it.

https://github.com/ByteStorage/FlyDB/pull/310 In this PR, I have addressed this issue and would appreciate it if you could take a look.


feat(charts): etcd-cluster

The idea of 3 pods comes from this example.
The pods are replaced by ReplicationControllers.

It seems not so stable on our cluster after just one day. I'm closing this PR to debug it more thoroughly.

Thanks for putting it through its paces and testing it thoroughly, @remohammadi! :smile:

@remohammadi I don't know if you've seen https://github.com/deis/etcd, but that might give you a few ideas on setting up an etcd cluster inside k8s. We decided to add an in-cluster discovery service to get around some of the stability issues.

@technosophos Thank you. It's working for us. We used the deis etcd to manage vulcand load balancer for our cluster. So the written chart for vulcand is dependent on deis-etcd-1.
So, which of these options do you recommend?

Creating a pull request for vulcand, commenting the dependency, noting the deis etcd in Readme, and waiting for the time the deis etcd is in stable phase.
Creating a pull request for the current status of deis-etcd (with heavy development warning in its Readme) + another pull request for vulcand

Or any other suggestions?

Here's a crazy idea on decoupling that you might find interesting, @remohammadi: In your Vulcand chart, add a service called something like vuldcand-etcd, and make it a clone of the deis-etcd service (so it uses the same label selector and all). Then you can swap different etcd implementations in and out without having to hard-code deis-etcd-1 into your own code (code in vulcan-etcd instead). Then you can set up defaults to, say, the Deis etcd or to a stand-alone etcd instance, or whatever.
Based on all of that, I think option 1 is the right approach. FWIW, we're about to mark the etcd alpha1 release, at which point all we'll be working on from here is stability, recovery, and fault tolerance.


Deno

Hi, is there an option to swap the SWC internal with wasm version instead of the default node addon?
Something like
import { rollup } from "npm:rollup"
import { swc } from "npm:rollup-plugin-swc3"

const build = await rollup({
  input: ["main.ts", "lib.mts"],
  plugins: [
    swc({
      wasm<EMAIL_ADDRESS>    }),
  ],
})
await build.write({ dir: "dist", format: "es" })

Just got an error with the default one since Deno doesn't support Node native addons

Error: Failed to convert napi value into rust type `Option<T>`
    at Compiler.<anonymous> (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/@swc/core/1.3.24/index.js:216:33)
    at (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/@swc/core/1.3.24/index.js:34:71)
    at __awaiter (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/@swc/core/1.3.24/index.js:30:12)
    at Compiler.transform (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/@swc/core/1.3.24/index.js:202:16)
    at transform (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/@swc/core/1.3.24/index.js:344:21)
    at Object.transform (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/rollup-plugin-swc3/0.8.0/dist/index.mjs:129:20)
    at (file:///home/wildan/.cache/deno/npm/registry.npmjs.org/rollup/3.9.1/dist/es/shared/rollup.js:23660:40)

I've done some experiment to integrate @swc/wasm with es-module-shims in the past.
Hope that can help.


Add Little Falls, NY

Original issue :
https://twitter.com/bitandbang/status/954343396130336769
Add these manually if website was not updated

Added


feat(api-common-fields): create doc

Why not a doc just about the taxID field?

we also had questions about the value field


Provide an API to gather entropy to be used in cryptography

This issue was originally filed by<EMAIL_ADDRESS>
Just so that we can one day implement true random number generators and full cryptography, we need some API to access things like /dev/random to gather true random bits.
Thanks ;-P.

This is a duplicate of issue #1746 .  The support comes from the embedder, so it will be in dart:io in the standalone vm, and in dart:html in the browser.  It is already supported in dart:html Crypto.getRandomValues, so we just need dart:io support.
Providing more cryptographic operations, beyond the secure RNG, is now the job of package:crypto, at https://github.com/dart-lang/crypto

See also https://github.com/dart-lang/sdk/issues/1746


Direwolves should drop wolf skin

primal:wolf_pelt

I also added <primal:wolf_meat_raw> to the drop list. Both have a 100% chance to drop from 0 to 2 items (so a 33% chance that nothing drops from each list).


out-of-date sail ocaml version in read-the-docs

Hi,
https://riscof.readthedocs.io/en/stable/installation.html#install-plugin-models says
opam switch create ocaml-base-compiler.4.06.1
https://github.com/rems-project/sail/blob/sail2/INSTALL.md says:
Use ocaml -version to check your OCaml version. If you have OCaml 4.08.1 or newer, that's fine, otherwise you can use opam switch to install a newer version:
opam switch create 5.1.0
Can you update the readthedocs directions to use the newer OCaml version?  Otherwise my generation of the SAIL model has errors.
thanks

I've just run into the same issue.  When compiling sail-riscv I get:
Syntax error:
[model/riscv_sys_regs.sail]:182:25-25
182 |    else [m with F = v[F], D = v[D] & v[F]]


Fix #1126: Check if album art file actually exists

Part of #1679 by @reiv.

This can be reproduced by simply deleting cover.jpg (or equivalent album art file) and then running beet fetchart. With this change, when invoking fetchart as a command, it will also check if the actual file given by artpath  exists in that directory.

This one is obviously the most straightforward of the three, and a good idea regardless of the eventual diagnosis of #1679. A test would be nice, and we also need a changelog entry, but beyond that this is ready.

Added a simple test. Is this sufficient?

Looks perfect to me; thanks! Feel free to hit that green button if you like.

Lovely! Thanks again. :sparkles:


Simple_nlp_example notebook launcher fails mutli gpu Accelerate only defined in training function

Sorry to bring this up, I've looked for a solution all over and couldn't find one, any help would be greatly appreciated.
I'm not sure if this notebook is set up to allow multiple GPU training.  It was written for Colab with TPU, so, that might be the entire issue, but....  just wanted to check with the experts :-)

I'm on a local machine, not in colab.  I'm using Jupyter notebooks to run these examples.

The CV notebook from hugging face works with multi GPU, very minor tweaks but it works, 3 GPUs on my on prem host, they all get used.  It's really cool!

https://github.com/huggingface/notebooks/blob/main/examples/accelerate_examples/simple_cv_example.ipynb

The simple_nlp_example Jupyter notebook fails however on the last cell where notebook launcher is called to do the distributed training.

https://github.com/huggingface/notebooks/blob/main/examples/accelerate_examples/simple_nlp_example.ipynb

The training function has not been modified, it is the ONLY place the Accelerator is defined.

I've edited the notebook only to make it run locally and not call any google colab stuff, otherwise it is exactly as it was downloaded.

#! pip install cloud-tpu-client==0.10
#! pip install https://storage.googleapis.com/tpu-pytorch/wheels/colab/torch_xla-2.0-cp310-cp310-linux_x86_64.whl

The error that is throw is:
ValueError: To launch a multi-GPU training from your notebook, the `Accelerator` should only be initialized inside your training function. Restart your notebook and make sure no cells initializes an `Accelerator`.

It will train on 1 single gpu even though it is requested to train on 3:
100%
1377/1377 [04:03<00:00, 6.49it/s]
epoch 0: {'accuracy': 0.7671568627450981, 'f1': 0.848966613672496}
epoch 1: {'accuracy': 0.8333333333333334, 'f1': 0.889967637540453}
epoch 2: {'accuracy': 0.8455882352941176, 'f1': 0.8930390492359932}

Here is the training function, unmodified from the example on huggingface:
def training_function(model):
    # Initialize accelerator
    accelerator = Accelerator()

    # To have only one message (and not 8) per logs of Transformers or Datasets, we set the logging verbosity
    # to INFO for the main process only.
    if accelerator.is_main_process:
        datasets.utils.logging.set_verbosity_warning()
        transformers.utils.logging.set_verbosity_info()
    else:
        datasets.utils.logging.set_verbosity_error()
        transformers.utils.logging.set_verbosity_error()

    train_dataloader, eval_dataloader = create_dataloaders(
        train_batch_size=hyperparameters["train_batch_size"], eval_batch_size=hyperparameters["eval_batch_size"]
    )
    # The seed need to be set before we instantiate the model, as it will determine the random head.
    set_seed(hyperparameters["seed"])

    # Instantiate optimizer
    optimizer = AdamW(params=model.parameters(), lr=hyperparameters["learning_rate"])

    # Prepare everything
    # There is no specific order to remember, we just need to unpack the objects in the same order we gave them to the
    # prepare method.
    model, optimizer, train_dataloader, eval_dataloader = accelerator.prepare(
        model, optimizer, train_dataloader, eval_dataloader
    )

    num_epochs = hyperparameters["num_epochs"]
    # Instantiate learning rate scheduler after preparing the training dataloader as the prepare method
    # may change its length.
    lr_scheduler = get_linear_schedule_with_warmup(
        optimizer=optimizer,
        num_warmup_steps=100,
        num_training_steps=len(train_dataloader) * num_epochs,
    )

    # Instantiate a progress bar to keep track of training. Note that we only enable it on the main
    # process to avoid having 8 progress bars.
    progress_bar = tqdm(range(num_epochs * len(train_dataloader)), disable=not accelerator.is_main_process)
    # Now we train the model
    for epoch in range(num_epochs):
        model.train()
        for step, batch in enumerate(train_dataloader):
            outputs = model(**batch)
            loss = outputs.loss
            accelerator.backward(loss)

            optimizer.step()
            lr_scheduler.step()
            optimizer.zero_grad()
            progress_bar.update(1)

        model.eval()
        all_predictions = []
        all_labels = []

        for step, batch in enumerate(eval_dataloader):
            with torch.no_grad():
                outputs = model(**batch)
            predictions = outputs.logits.argmax(dim=-1)

            # We gather predictions and labels from the 8 TPUs to have them all.
            all_predictions.append(accelerator.gather(predictions))
            all_labels.append(accelerator.gather(batch["labels"]))

        # Concatenate all predictions and labels.
        # The last thing we need to do is to truncate the predictions and labels we concatenated
        # together as the prepared evaluation dataloader has a little bit more elements to make
        # batches of the same size on each process.
        all_predictions = torch.cat(all_predictions)[:len(tokenized_datasets["validation"])]
        all_labels = torch.cat(all_labels)[:len(tokenized_datasets["validation"])]

        eval_metric = metric.compute(predictions=all_predictions, references=all_labels)

        # Use accelerator.print to print only on the main process.
        accelerator.print(f"epoch {epoch}:", eval_metric)

No where else is Accelerator initialized...
Any ideas, looks like a false positive.
I have restarted the kernel several times and cleared the cache.
Thanks so much for any help

Hi @texasdave2 , thanks for reporting. Which version of accelerate are you using ? cc @muellerzr when you will be back

Hi @SunMarc , thanks for the reply, the accelerate version I'm using is:
! pip install git+https://github.com/huggingface/accelerate

## version of accelerate:
! accelerate env

Copy-and-paste the text below in your GitHub issue

- `Accelerate` version: 0.24.0.dev0
- Platform: Linux-5.15.0-83-generic-x86_64-with-glibc2.35
- Python version: 3.9.17
- Numpy version: 1.25.2
- PyTorch version (GPU?): 2.0.0+cu117 (True)
- PyTorch XPU available: False
- PyTorch NPU available: False
- System RAM: 62.79 GB
- GPU type: Tesla T4
- `Accelerate` default config:
	- compute_environment: LOCAL_MACHINE
	- distributed_type: MULTI_GPU
	- mixed_precision: no
	- use_cpu: False
	- debug: False
	- num_processes: 3
	- machine_rank: 0
	- num_machines: 1
	- gpu_ids: all
	- rdzv_backend: static
	- same_network: True
	- main_training_function: main
	- downcast_bf16: no
	- tpu_use_cluster: False
	- tpu_use_sudo: False
	- tpu_env: []

Stupid question, new to LLMs but would loading the tokenizer have anything to do with this?  I'm trying to find any places where the model would be getting loaded but not sure.  This snippet occurs near the beginning of the notebook.
from transformers import AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained(model_checkpoint)

No I don't think that loading the tokenizer have anything to do with it. I will try to reproduce the error

@texasdave2 where is Accelerator being defined? In the training function? What are your imports you are using? Are you initializing Accelerator, PartialState, or AcceleratorState from outside the training function? If possible a full reproducer notebook with everything would be phenomenal as a github gist.

Here is a link to a public gist:
simple_nlp_example.ipynb
https://gist.github.com/texasdave2/ab3720476c4b68cc6ce081bc137bc1fb
Accelerator is defined in the training function.
def training_function(model):
    # Initialize accelerator
    accelerator = Accelerator()

imports are:
import torch
from torch.utils.data import DataLoader

from accelerate import Accelerator, DistributedType
from datasets import load_dataset, load_metric
from transformers import (
    AdamW,
    AutoModelForSequenceClassification,
    AutoTokenizer,
    get_linear_schedule_with_warmup,
    set_seed,
)

from tqdm.auto import tqdm

import datasets
import transformers

import datasets
import random
import pandas as pd
from IPython.display import display, HTML

def show_random_elements(dataset, num_examples=10):
    assert num_examples <= len(dataset), "Can't pick more elements than there are in the dataset."
    picks = []
    for _ in range(num_examples):
        pick = random.randint(0, len(dataset)-1)
        while pick in picks:
            pick = random.randint(0, len(dataset)-1)
        picks.append(pick)

    df = pd.DataFrame(dataset[picks])
    for column, typ in dataset.features.items():
        if isinstance(typ, datasets.ClassLabel):
            df[column] = df[column].transform(lambda i: typ.names[i])
    display(HTML(df.to_html()))

show_random_elements(raw_datasets["train"])

from transformers import AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained(model_checkpoint)

from transformers import AutoModelForSequenceClassification

model = AutoModelForSequenceClassification.from_pretrained(model_checkpoint, num_labels=2)

from accelerate import notebook_launcher

notebook_launcher(training_function(model), num_processes=3)
#notebook_launcher(training_function, (model,), num_processes=3)

As far as I can tell only Accelertor is initialized, and only inside the training function.
thanks!

Hi @texasdave2, the problem lies in the model. By calling notebook_launcher(training_function(model), num_processes=3) , it will use only one gpu. The right syntax to pass args is notebook_launcher(training_function, (model,), num_processes=3). However, from my test, it will somehow trigger CUDA if you initialize the model outside of training_function. It should work if you define it inside of the training launcher. . You can find the gist here. I was able to successfully launch it.

Yes @SunMarc and @muellerzr ,  thank you both so much for the help, this version works now.  Thank you for responding so quickly!

solved


fixFix the compatibility issue with show_view_priv when replaying editLog

What problem does this PR solve?
The previous version showed an index of 9 for show_view_priv, while the new version has an index of 14
The previous logic was only compatible with the playback logic of images, not with the playback logic of editLog
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Fix the compatibility issue with show_view_priv when replaying editLog
Release note
Fix the compatibility issue with show_view_priv when replaying editLog
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[x] Manual test (add detailed scripts or steps below)
- use doris2.1 create user and grant show_view_priv on xx.xx to userxxx;
- use doris master revoke show_view_priv on xx.xx from userxxx;
- show grants for userxxx; show_view_priv has been disappear
[ ] 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

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

run buildall

run buildall

run p0

run p0

run p0


Copy blackbox_exporter's support of basic_auth for targets

Blackbox_exporter supports basic_auth block for targets.
  # The HTTP basic authentication credentials for the targets.
  basic_auth:
    [ username: <string> ]
    [ password: <secret> ]
    [ password_file: <filename> ]

Json_exporter should too.

Edit: just noticed that 2nd option is actually not viable at all (didn't notice errors in the log).
Feel free to close this ticket if it's local just to json_exporter and needs to be fixed there.

This is already implemented in the configuration file under http_cient_config.


new outline tree-view item wrapping

Version: 1.32.0-insider (user setup)
Commit: 69249882e8717cf111e04330390107282e337559
Date: 2019-02-27T21:19:19.351Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18343
Steps to Reproduce:

Use a file able to provide outline items, from which those outline items may contain special characters.
View the outline

In this case, this is PowerShell.   PowerShell allows some pretty elaborate function names which are then picked up and put in the outline.  The new treeview appears to not be suited for this:

These particular function names are created from the following code:
function `"" $any name$(hello$a)" {}

& hello$a-somemoretext & if (.. hello) {}

${local`:`}
function local:' any name
    $(hello$a)'hello `{}::hello($world)

function local:' any name
    $(hello$a)'hello ($a, $Bmans ) {}

function :"  any name$(hello$a)" {}

function `"" $any name$(hello$a)" {}
function `"` any` name$(hello$a)" {}
function `" any name$(hello$a)" {}

` `"` any`	name$(hello$a)" {}
function `" any name$(hello$a)" {}

function `a {}

function ` a {}

FYI, the PowerShell/EditorSyntax syntax file will not display this code correctly.  Not all function names seen in the image may be included in this code example, but the ones that are wrapping are included.   The function names include newline characters that are picked up from the way PowerShell parses the text.   While not practical, its possible.
This issue report is really just to make you aware of a change the new tree-view has made, but I do not know what likelihood other people would run in to this is.  I have been working to improve the PowerShell syntax file and so have been stress testing by creating the above patterns.

For reference, how the code looks with an improved syntax, to help in understanding it.  Line 27 shows an invocation of the function on line 24.  (the backtick at the start of the line has no value, and now I realized I hadn't noticed it isn't correctly scoped. :) )


Enhancement Use update time of hive to avoid cache miss through multi fe nodes.

Proposed changes
Now the update time of hms table is generated by every FE node (Use System.currentTimestamp() separately), so the update time of a hms table may be different between FE nodes, always the same query can not hit the sql-cache if we submit it more than one times through different FE nodes. This pr mainly do following changes to avoid this problem.

Use the transient_lastDdlTime instead of System.currentTimestamp as the schemaUpdateTime of hms tables
Use the eventTime in hms event instead of System.currentTimestamp as the update time when processing hms events

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

run buildall

run buildall

run feut

run p0

run tpch

run feut

run feut

run feut


New example app with manual initialization is added.

Could you also include README files inside of each App folder?
Just with quick references to most important parts of the code.
For example:
See MyAuthenticationService for example on how to perform authentication.
Disabling automatic initialisation can be found in the Manifest.xml file


"Anything Everywhere?" Not rendering inputs

After updating Comfy today it seems the Anything Everywhere? nodes no longer render the input boxes for filtering.

Yes, just discovered the same.

This seems to be caused by the autocomplete code; it was a bit of a hack and I think the new Comfy front end expects cleaner custom widgets! I've disabled the autocomplete for the time being.


Non-global recentering KSamplers

Disclaimer, I don't know anything about torch, diffusion, python, or even how ComfyUI really works. I just want to use recentering without polluting all samplers with unpredictable behavior.
For example, if you have a non-trivial workflow with several steps, and you use fixed seeds, it's often the case that only part of the graph executes on any given queue. This is my OCD workflow, which has several stages.
So because the Recenter nodes modify a global value on evaluation, it only updates when changes are made to Recenter nodes. That means for any given workflow unless Recenter always occurs after a randomizing node in the Latent graph, the configuration of the Recenter override callback will be stuck on whichever Recenter node executed last.
I tried a version where Recenter inserts a callback into the Latent but that's not picked up by Comfy. Supporting callback injection into latents might be another approach to broaden support in Comfy, since this KSampler wrapper approach only works for the basic KSampler and probably will fail in future versions of Comfy.

Yeah... That's what I used to do before...
But copying the entire block of code just to add one line is... not elegant.
Not to mention, ComfyUI has the normal KSampler, a KSampler Advanced node, and a KSampler Custom node, not counting any more added in the future, etc.
So now you're looking at 3 x 2 = 6 huge blocks of copy-pasted codes just to add 1 line each...

Then, I think the only other way forward is to patch ComfyUI core to add something like latents['LUT'] to the sampler_common or whatever method so that a node can inject the LUT into the latents, and the sampler can pick it up and, if present, apply the differences.


[FEATURE] Add features to improve maintainability of plugin in managed service

Circuit breaker
Settings
Stats

@JohannesDaniel
Can you add more details based on the issue template ? In the current form the context is missing and raises more questions.
(@epugh mentioned you missed joining the Wed session on Search community meeting on Zoom, so sharing my comments here)
My first impression was that you were looking for a way to expose the settings for LTR for users to configure. APIs are the right way to do this, but if one doesn't have direct access to the physical hosts, dashboards is a natural way to go. Whether it makes sense for LTR to spin its own dashboard or piggy back of something more generic in that space (e.g. Search Relevancy) is somethign worth considering.
As a glance through the code, you also appear to be introducing stats for the LTR plugin. If so, I would suggest keeping the two separate as the former (e.g. configuring via dashboard) builds on the latter (existing stats APIs). This way your code will get easier to review and you can also test for backward compatibility between versions that support your feature and those that don't.


Fix path for activation_server link in models readme

Add missing ../ to link for /neuron_explainer/activation_server/README.md

thanks!


Update CONTRIBUTERS.MD

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[x] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Add Link of GitHub Profile

Hello there this is the very first open source contribution of mine


menu-item is not a valid aria role

Hello!
Looking at the implementation of https://github.com/Khan/tota11y/blob/master/plugins/base.js#L80 I found that this may be breaking an accessibility rule related to aria roles after I ran an accessibility audit using Google Chrome:

According to w3.org menu-item is not correct and it should be menuitem (without the dash) https://www.w3.org/TR/wai-aria/roles#roles_categorization.

[clabot:check]

Anyone around?

So, nobody maintain this?

:+1: No problem! Thanks for approving this ^^


[5.5] Add retries to delete reserved on jobs table to fix dead lock issues on heavy queue loads

I have had issues for days, first about the redis driver because it has exhausted my server RAM then with the database driver which produced many deadlocks. I work for a customer that really needs to keep track of pending queues and failed_jobs. Everything works as perfect with the database driver except when I have a lot of jobs.
The php artisan queue:work command would hangs after 100/200 jobs because of deadlocks and those commands would then never process the job. My queue processing logic stops and I have to restart everything manually. The issue is really well explained by @micmania1 in https://github.com/laravel/framework/issues/7046 (end of the issue).
Big thanks to @micmania1 for the solution that helped me put all the work I've done to production! I would love this to be merged as it would solve one big issue of the database driver for heavy loads.

Link to the comment; https://github.com/laravel/framework/issues/7046#issuecomment-343016056
I dislike this change just because it has a mentality of "try it again" instead of figuring out the actual problem. Could you describe your table structure and what indexes you have? What in your show engine innodb status indicates that this solution is appropriate? What types of locks are involved in your deadlocks?
This change sounds like something you guessed at, and the verification is doubtful. The code comments (and code) that $conn->transaction($callback, $retries) uses implies that it does not in fact retry anything in case of deadlocks.
https://github.com/laravel/framework/blob/de561cb0c3de5d793a2bf93c5353dcec00c9544b/src/Illuminate/Database/Concerns/ManagesTransactions.php#L61-L69
I run the database queue driver myself with spikes of 25k waiting jobs, processed by ~40 workers on ~16 machines without any issues. I mention this slightly for bragging, but mostly to tell you that if you have deadlock problems at your numbers you need to look into what actually caused it, and if you have appropriate indexes.
The next step to debug your problem and find a proper solution would be to tell us the structure of your jobs table (a create table to reproduce it would suffice), and the output of show engine innodb status when the deadlocks occur.

I've reread the code again, and I now see that the code I linked in the previous comment is about nested transactions which isn't the case here.

Taylor has said in many other threads/issues that database queue driver should not be used in heavy production, and to use a proper queue driver like Redis or Beanstalkd. If your Redis queue is running out of memory, it sounds like you might need a bigger server.

The database driver will never be a good solution at scale. It's just fundamentally not the right solution, as many articles on the Internet can tell you about relational databases and queues.
A better approach is figuring out why Redis is filling up your memory. Or maybe using Beanstalkd?

Ok thank you all for your answers and taking the time to look into it. I'll try to use Beanstalkd then!

@victorboissiere I never got the table structure from you. We just had a deadlock report in https://github.com/laravel/framework/issues/7046 and https://github.com/laravel/framework/pull/22394 that is about a gap lock on an index that isn't part of the default 5.5 jobs table. Can you verify if you have that index from an earlier upgraded Laravel version, or if you have a "pure" 5.5 jobs table without the index?

@sisve I used a pure 5.5 jobs table using php artisan queue:table. I'm now using Beanstalkd with no issue at all.


gallery 01-03 release

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @kangsun-ctrl  permissions  does not contain community(link), Could you please fix it

/azp run

Hi @kangsun-ctrl & @PARADISSEEKR, If you want to generate SDK according to 2022-01-03, please add the corresponding tag in readme and readme.python, thanks.

Hi @kangsun-ctrl & @PARADISSEEKR, If you want to generate SDK according to 2022-01-03, please add the corresponding tag in readme and readme.python, thanks.

hey @BigCat20196 , I think it is already in readme, I pushed another iteration to add it to readme.python, let me know if i need to add anything else, thanks!

Hi @kangsun-ctrl, package-2022-01-03-only tag needs to be configured in readme before it can takes effect in readme.python.md. I have submitted the update.^^

Hi @kangsun-ctrl, package-2022-01-03-only tag needs to be configured in readme before it can takes effect in readme.python.md. I have submitted the update.^^

Thanks a lot, Jiefeng! @BigCat20196

@kangsun-ctrl - Couple of things needed before your PR is ready for ARM review:

This is a new API version for Microsoft.Compute, so your submission form should check [ ] new API version instead of [ ] new service onboarding. Fixing that will drive automation and correct handling of your PR.
Please study the materials described in the submission form and attest to that by checking the box:
[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

@ArcturusZhang , we would like this to be merged ASAP. We are working on resolving the enum error and have approval for the breaking change.
Please review this and be ready to merge it soon.


Cannot disable posframe?

Hi,
Probably a silly question related to my own config, but I've hunted and hunted to find what changed re: completion using what looks like posframe. Is it actively enabled somewhere? I can't find anything that would indicate it's in use, including variables, but the completion sure looks like it's using it. Any tips appreciated or a quick - "that's on you!" would be great too.
Thanks again for such an awesome configuration !

Hello @jonathanwilner ,
I'm not sure if I've understood your question. If you can provide a screenshot or a GIF, it would be helpful.
If you are looking for the package responsible for MinEmacs' completion in a child frame (the built-in feature used by posframe), it is corfu. There are 2 modes directly involved, corfu-mode and corfu-popinfo-mode:

These are configured in me-completion. By default, corfu-mode is enabled globally. If you want to enable it only in some modes, let's say, prog-mode, you can add something like this to your config:
(remove-hook 'minemacs-after-startup-hook #'global-corfu-mode)
(add-hook 'prog-mode-hook #'corfu-mode)

You can also leave corfu enabled globally and tweak the corfu-exclude-modes customization variable (for example, to exclude org-mode).
(with-eval-after-load 'corfu
  (push 'org-mode corfu-exclude-modes))

i love this framework, thanks for your work!

Thanks @xanmodlouis , Happy you've found it useful!

@jonathanwilner did my comment answers your question?

Yes, it put me on the right track re corfu and corfu-terminal . Thank you !
On Fri, May 5, 2023 at 19:43 Abdelhak Bougouffa @.***>
wrote:

@jonathanwilner https://github.com/jonathanwilner did my comment
answers your question?
—
Reply to this email directly, view it on GitHub
https://github.com/abougouffa/minemacs/issues/54#issuecomment-1536971229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEOIBZSYFM32IVD2XGLJ4TXEWUDDANCNFSM6AAAAAAXNIN5DA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Heatit Thermostat Z-TRM3 lost Multilevel Sensor capability

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 Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
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
Since updating to latest version (11.13.0), all my Heatit Z-TRM3 thermostats stopped reporting multilevel sensor values, ie thermostat floor and air temperatures. Log is showing "[Node nnn] does not support CC Multilevel Sensor - discarding received command", which seems to relate to change #6178.
All thermostats had multilevel sensor shown in node, they were just not updating due to this change. Now that I re-interviewed two of these thermostats, multilevel sensor is lost in UI as well.
What might be the reason zwave-js now thinks these devices don't support this? Attached driver log has interview of node 024, and for me it seems to say it does, for example
2023-08-25T07:42:48.693Z DRIVER « [Node 024] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 81
                                    │ security class:  S2_Authenticated
                                    └─[VersionCCCommandClassReport]
                                        CC:      Multilevel Sensor
                                        version: 5
2023-08-25T07:42:48.694Z CNTRLR   [Node 024]   supports CC Multilevel Sensor (0x31) in version 5    [Endpoint 2]

In version 11.6.0 there was no problems, and with another zwave-js instance running with older version, Z-TRM3 still operates without problems.
Device information
Manufacturer:
Model name:
Node ID in your network:
How are you using node-zwave-js?

[X] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly 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: 11.13.0
Did you change anything?
yes (please describe)
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
In earlier version 11.6.0
Attach Driver Logfile
zwave-driver.log

The endpoint that sends the reports does support Multilevel Sensor CC:
2023-08-25T07:42:48.621Z CNTRLR « [Node 024] received secure commands (S2_Authenticated)            [Endpoint 2]
                                  supported CCs:
                                  · Association
                                  · Association Group Information
                                  · Multi Channel Association
                                  · Multilevel Sensor

...

2023-08-25T07:42:48.841Z CNTRLR   [Node 024] does not support CC Multilevel Sensor - discarding received command...
2023-08-25T07:42:48.843Z DRIVER « [Node 024] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 83
                                    │ security class:  S2_Authenticated
                                    └─[MultiChannelCCCommandEncapsulation]
                                      │ source:      2
                                      │ destination: 0
                                      └─[MultilevelSensorCCSupportedSensorReport]
                                          supported sensor types:
                                          · Air temperature

I'm having the same issue with Z-Wave JS UI and a Fibaro Universal Binary Sensor
CNTRLR does not support CC Multilevel Sensor - discarding received command

Same problem as described above with 2 Fibaro universal binary sensor (2 ch on/off + 1 temp) in Z-Wave JS UI v1.15.7
Downgrade to  Z-Wave JS UI v1.15.6 solves the problem.

+1

I updated to ZWave JS UI 8.23.2 to get the fix, but my temperature sensor on the FGK101 immediately stopped updating.
I reverted to 8.23.0 and the temperature has been updated, I'll monitor it to see if it reports correctly.

8.23.2 doesn't include the fix yet: https://zwave-js.github.io/which-version/

Latest version:
v8.23.2
Driver version:
v11.13.0

That is in v11.13.1

Oh ! My mistake. I saw a node release before an UI release and thought it was included 😂

I'm getting the same with a Fibaro FGS221.
Logs are being spammed with:
CNTRLR [Node 054] does not support CC Meter - discarding received command...
Here are the logs on an include:
023-09-26T03:46:30.337Z CNTRLR [Node 054] Beginning interview - last completed stage: None 2023-09-26T03:46:30.337Z CNTRLR [Node 054] new node, doing a full interview... 2023-09-26 13:46:30.338 INFO Z-WAVE: [Node 054] Interview started 2023-09-26T03:46:30.338Z CNTRLR » [Node 054] querying protocol info... 2023-09-26T03:46:30.372Z CNTRLR « [Node 054] received response for protocol info: basic device class: Routing Slave generic device class: Binary Switch specific device class: Binary Power Switch node type: End Node is always listening: true is frequent listening: false can route messages: true supports security: false supports beaming: true maximum data rate: 40000 kbps protocol version: 3 2023-09-26 13:46:30.373 INFO Z-WAVE: [Node 054] Interview stage PROTOCOLINFO completed 2023-09-26T03:46:30.374Z CNTRLR [Node 054] Interview stage completed: ProtocolInfo 2023-09-26T03:46:30.375Z CNTRLR » [Node 054] querying node info... 2023-09-26T03:46:30.530Z CNTRLR « [Node 054] node info received supported CCs: · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation · No Operation · No Operation · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation 2023-09-26T03:46:30.531Z CNTRLR « [Node 054] node info received supported CCs: · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation · No Operation · No Operation · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation 2023-09-26 13:46:30.532 INFO Z-WAVE: [Node 054] Interview stage NODEINFO completed 2023-09-26T03:46:30.532Z CNTRLR [Node 054] Interview stage completed: NodeInfo 2023-09-26T03:46:30.533Z CNTRLR [Node 054] Interviewing Binary Switch... 2023-09-26T03:46:30.533Z CNTRLR » [Node 054] querying Binary Switch state... 2023-09-26 13:46:30.729 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-currentValue 2023-09-26 13:46:30.731 INFO Z-WAVE: [Node 054] Value added: 37-0-currentValue => false 2023-09-26 13:46:30.731 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-targetValue 2023-09-26 13:46:30.732 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-duration 2023-09-26T03:46:30.732Z CNTRLR « [Node 054] received Binary Switch state: current value: false 2023-09-26 13:46:30.732 INFO Z-WAVE: [Node 054] Interview stage COMMANDCLASSES completed 2023-09-26T03:46:30.733Z CNTRLR [Node 054] Interview stage completed: CommandClasses 2023-09-26 13:46:30.733 INFO Z-WAVE: [Node 054] Interview stage OVERWRITECONFIG completed 2023-09-26T03:46:30.733Z CNTRLR [Node 054] Interview stage completed: OverwriteConfig 2023-09-26 13:46:30.733 INFO Z-WAVE: [Node 054] Interview stage COMPLETE completed 2023-09-26T03:46:30.734Z CNTRLR [Node 054] Interview completed 2023-09-26 13:46:30.734 INFO Z-WAVE: [Node 054] Value added 54-37-0-currentValue => false 2023-09-26 13:46:30.735 INFO Z-WAVE: [Node 054] Value added 54-37-0-targetValue => undefined 2023-09-26 13:46:30.735 INFO Z-WAVE: [Node 054] Value added 54-37-0-duration => NaNs 2023-09-26 13:46:30.735 INFO Z-WAVE: [Node 054] Ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX) 2023-09-26T03:46:30.737Z CNTRLR [Node 054] The node is ready to be used 2023-09-26 13:46:30.739 INFO Z-WAVE: [Node 054] Interview COMPLETED, all values are updated 2023-09-26 13:47:04.244 INFO Z-WAVE: [Node 054] Value added: 119-0-name => Bedroom TV 2023-09-26 13:47:04.244 INFO Z-WAVE: [Node 054] Value added: 119-0-location => Bedroom 2023-09-26T03:47:04.245Z CNTRLR [Node 054] Beginning interview - last completed stage: None 2023-09-26T03:47:04.245Z CNTRLR [Node 054] new node, doing a full interview... 2023-09-26 13:47:04.245 INFO Z-WAVE: [Node 054] Interview started 2023-09-26T03:47:04.245Z CNTRLR » [Node 054] querying protocol info... 2023-09-26T03:47:04.261Z CNTRLR « [Node 054] received response for protocol info: basic device class: Routing Slave generic device class: Binary Switch specific device class: Binary Power Switch node type: End Node is always listening: true is frequent listening: false can route messages: true supports security: false supports beaming: true maximum data rate: 40000 kbps protocol version: 3 2023-09-26 13:47:04.261 INFO Z-WAVE: [Node 054] Interview stage PROTOCOLINFO completed 2023-09-26T03:47:04.262Z CNTRLR [Node 054] Interview stage completed: ProtocolInfo 2023-09-26T03:47:04.262Z CNTRLR » [Node 054] querying node info... 2023-09-26T03:47:04.388Z CNTRLR « [Node 054] node info received supported CCs: · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation · No Operation · No Operation · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation 2023-09-26T03:47:04.388Z CNTRLR « [Node 054] node info received supported CCs: · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation · No Operation · No Operation · No Operation · No Operation · Z-Wave Protocol · No Operation · No Operation 2023-09-26 13:47:04.389 INFO Z-WAVE: [Node 054] Interview stage NODEINFO completed 2023-09-26T03:47:04.391Z CNTRLR [Node 054] Interview stage completed: NodeInfo 2023-09-26T03:47:04.392Z CNTRLR [Node 054] Interviewing Binary Switch... 2023-09-26T03:47:04.393Z CNTRLR » [Node 054] querying Binary Switch state... 2023-09-26 13:47:04.557 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-currentValue 2023-09-26 13:47:04.559 INFO Z-WAVE: [Node 054] Value added: 37-0-currentValue => false 2023-09-26 13:47:04.560 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-targetValue 2023-09-26 13:47:04.560 INFO Z-WAVE: [Node 054] Metadata updated: 37-0-duration 2023-09-26T03:47:04.561Z CNTRLR « [Node 054] received Binary Switch state: current value: false 2023-09-26 13:47:04.561 INFO Z-WAVE: [Node 054] Interview stage COMMANDCLASSES completed 2023-09-26T03:47:04.562Z CNTRLR [Node 054] Interview stage completed: CommandClasses 2023-09-26 13:47:04.562 INFO Z-WAVE: [Node 054] Interview stage OVERWRITECONFIG completed 2023-09-26T03:47:04.563Z CNTRLR [Node 054] Interview stage completed: OverwriteConfig 2023-09-26 13:47:04.563 INFO Z-WAVE: [Node 054] Interview stage COMPLETE completed 2023-09-26T03:47:04.564Z CNTRLR [Node 054] Interview completed 2023-09-26 13:47:04.565 INFO Z-WAVE: [Node 054] Value added 54-37-0-currentValue => false 2023-09-26 13:47:04.565 INFO Z-WAVE: [Node 054] Value added 54-37-0-targetValue => undefined 2023-09-26 13:47:04.565 INFO Z-WAVE: [Node 054] Value added 54-37-0-duration => NaNs 2023-09-26 13:47:04.565 INFO Z-WAVE: [Node 054] Ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX) 2023-09-26T03:47:04.568Z CNTRLR [Node 054] The node is ready to be used 2023-09-26 13:47:04.571 INFO Z-WAVE: [Node 054] Interview COMPLETED, all values are update

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).
That log should include a re-interview.

I turned the driver log to log level 'debug'  before I did my re-interview with the debug log open, but as I am using the built in Z-Wave JS  in home assistant, I can't find where the actual logs are.

The log you posted above looks a lot like Z-Wave JS UI though? The link I posted also explains how to retrieve the files at the bottom. Make sure to put the driver log on debug, the snippet above isn't.
If you're really not using Z-Wave JS UI, check https://www.home-assistant.io/integrations/zwave_js#how-to-access-the-z-wave-logs

If you're really not using Z-Wave JS UI, check https://www.home-assistant.io/integrations/zwave_js#how-to-access-the-z-wave-logs

Thank you, that's were it was. :)
zwave_js(1).log

I found another debug log that hopefully is of use as well:

{
  "id": 54,
  "name": "Bedroom TV",
  "loc": "Bedroom",
  "values": [
    {
      "id": "54-37-0-currentValue",
      "nodeId": 54,
      "toUpdate": false,
      "commandClass": 37,
      "commandClassName": "Binary Switch",
      "endpoint": 0,
      "property": "currentValue",
      "propertyName": "currentValue",
      "type": "boolean",
      "readable": true,
      "writeable": false,
      "label": "Current value",
      "stateless": false,
      "commandClassVersion": 2,
      "list": false,
      "value": false,
      "isCurrentValue": true,
      "targetValue": "37-0-targetValue",
      "lastUpdate":<PHONE_NUMBER>331,
      "newValue": false
    },
    {
      "id": "54-37-0-duration",
      "nodeId": 54,
      "toUpdate": false,
      "commandClass": 37,
      "commandClassName": "Binary Switch",
      "endpoint": 0,
      "property": "duration",
      "propertyName": "duration",
      "type": "duration",
      "readable": true,
      "writeable": false,
      "label": "Remaining duration",
      "stateless": false,
      "commandClassVersion": 2,
      "list": false,
      "value": {
        "value": 41,
        "unit": "minutes"
      },
      "lastUpdate":<PHONE_NUMBER>136,
      "newValue": {
        "value": 41,
        "unit": "minutes"
      }
    },
    {
      "id": "54-37-0-targetValue",
      "nodeId": 54,
      "toUpdate": false,
      "commandClass": 37,
      "commandClassName": "Binary Switch",
      "endpoint": 0,
      "property": "targetValue",
      "propertyName": "targetValue",
      "type": "boolean",
      "readable": true,
      "writeable": true,
      "label": "Target value",
      "stateless": false,
      "commandClassVersion": 2,
      "list": false,
      "lastUpdate":<PHONE_NUMBER>143
    }
  ],
  "groups": [],
  "neighbors": [],
  "ready": true,
  "available": true,
  "hassDevices": {},
  "failed": false,
  "inited": true,
  "eventsQueue": [
    {
      "time": "2023-09-28T05:17:26.873Z",
      "event": "alive",
      "args": [
        0
      ]
    },
    {
      "time": "2023-09-28T05:17:26.876Z",
      "event": "ready",
      "args": []
    },
    {
      "time": "2023-09-28T05:29:00.030Z",
      "event": "value added",
      "args": [
        {
          "commandClassName": "Node Naming and Location",
          "commandClass": 119,
          "property": "name",
          "newValue": "Bedroom TV",
          "propertyName": "name"
        }
      ]
    },
    {
      "time": "2023-09-28T05:29:00.031Z",
      "event": "value added",
      "args": [
        {
          "commandClassName": "Node Naming and Location",
          "commandClass": 119,
          "property": "location",
          "newValue": "Bedroom",
          "propertyName": "location"
        }
      ]
    },
    {
      "time": "2023-09-28T05:29:00.032Z",
      "event": "interview started",
      "args": []
    },
    {
      "time": "2023-09-28T05:29:00.052Z",
      "event": "interview stage completed",
      "args": [
        "ProtocolInfo"
      ]
    },
    {
      "time": "2023-09-28T05:29:03.895Z",
      "event": "interview stage completed",
      "args": [
        "NodeInfo"
      ]
    },
    {
      "time": "2023-09-28T05:29:04.136Z",
      "event": "value added",
      "args": [
        {
          "commandClassName": "Binary Switch",
          "commandClass": 37,
          "property": "currentValue",
          "endpoint": 0,
          "newValue": false,
          "propertyName": "currentValue"
        }
      ]
    },
    {
      "time": "2023-09-28T05:29:04.137Z",
      "event": "value added",
      "args": [
        {
          "commandClassName": "Binary Switch",
          "commandClass": 37,
          "property": "duration",
          "endpoint": 0,
          "newValue": {
            "value": 41,
            "unit": "minutes"
          },
          "propertyName": "duration"
        }
      ]
    },
    {
      "time": "2023-09-28T05:29:04.138Z",
      "event": "interview stage completed",
      "args": [
        "CommandClasses"
      ]
    },
    {
      "time": "2023-09-28T05:29:04.139Z",
      "event": "interview stage completed",
      "args": [
        "OverwriteConfig"
      ]
    },
    {
      "time": "2023-09-28T05:29:04.140Z",
      "event": "interview stage completed",
      "args": [
        "Complete"
      ]
    },
    {
      "time": "2023-09-28T05:29:04.145Z",
      "event": "ready",
      "args": []
    },
    {
      "time": "2023-09-28T05:29:04.152Z",
      "event": "interview completed",
      "args": []
    },
    {
      "time": "2023-09-28T05:29:04.332Z",
      "event": "value updated",
      "args": [
        {
          "commandClassName": "Binary Switch",
          "commandClass": 37,
          "property": "currentValue",
          "endpoint": 0,
          "newValue": false,
          "prevValue": false,
          "propertyName": "currentValue"
        }
      ]
    }
  ],
  "status": "Alive",
  "interviewStage": "Complete",
  "priorityReturnRoute": {},
  "customReturnRoute": {},
  "prioritySUCReturnRoute": false,
  "customSUCReturnRoutes": [],
  "hexId": "0xXXXX-0xXXXX-0xXXXX",
  "dbLink": "https://devices.zwave-js.io/?jumpTo=0xXXXX:0xXXXX:0xXXXX:0.0",
  "productLabel": "Unknown product 0xXXXX",
  "productDescription": "0xXXXX",
  "manufacturer": "Unknown manufacturer 0xXXXX",
  "protocolVersion": 3,
  "nodeType": 1,
  "endpointsCount": 0,
  "endpoints": [
    {
      "index": 0,
      "label": "Root Endpoint"
    }
  ],
  "isSecure": false,
  "security": "None",
  "supportsSecurity": false,
  "supportsBeaming": true,
  "isControllerNode": false,
  "isListening": true,
  "isFrequentListening": false,
  "isRouting": true,
  "keepAwake": false,
  "maxDataRate": 40000,
  "deviceClass": {
    "basic": 4,
    "generic": 16,
    "specific": 1
  },
  "lastActive":<PHONE_NUMBER>021,
  "firmwareCapabilities": {
    "firmwareUpgradable": false
  },
  "deviceId": "undefined-undefined-undefined",
  "hasDeviceConfigChanged": false,
  "statistics": {
    "commandsTX": 2,
    "commandsRX": 385,
    "commandsDroppedRX": 0,
    "commandsDroppedTX": 0,
    "timeoutResponse": 0,
    "rtt": 451.3,
    "lastSeen": "2023-09-28T05:33:43.021Z",
    "rssi": -70,
    "lwr": {
      "protocolDataRate": 2,
      "repeaters": [],
      "rssi": -72,
      "repeaterRSSI": []
    }
  },
  "supportsTime": false,
  "_name": "Bedroom TV (Bedroom)",
  "applicationRoute": false,
  "lastReceive":<PHONE_NUMBER>021,
  "errorReceive": false,
  "errorTransmit": false
}

The communication from the device seems completely off - like the capability reports don't make any sense whatsoever.
I'd start by power cycling the thermostat, if that doesn't work power cycle the stick (pull out, put back),
If that doesn't work either, exclude the thermostat, factory reset it, include it again.

sorry, I think I've given you a misdirection. I found this error by googling the same error message, but it's not the same device. It's actually a  Fibaro binary switch, but I'm not sure of the model, because it's in the wall, and it no longer identifies properly: it just gives "unknown device".
Should I open a new issue, despite the same error?

Doesn't matter which device it is, the troubleshooting steps from my previous post still apply


Can't add anything to dashboard.

Installed Mongo
Downloaded Hygieia V1.2.0
Successfully ran mvn clean compile install package
Created application.properties in corresponding config folders for Hudson Collector and Subversion Collector
Run both hudson and subversion collector with java -jar
Run gulp serve in the UI folder
Everything appears to come up ok
I see data has been created in mongo
I can add a dashboard in the UI
But, I can not succesffuly add any widgets via the UI.
For subversion the dialog box comes up and and can select subversion and provide a url, but it will not save.
Debugging the JS I see
    function submitForm(valid, url, repoType) {
        ctrl.submitted = true;
        if (valid && ctrl.collectors.length) {

ctrl.collectors.length is 0
For the build widget, it comes up but there are no options avaible in the "Select a build job" drop down.
I've reviewed the documentation several time, but I feel like I'm missing some simple step.
Thanks,
Tony Perkins
Fidelity Investments

Tony,
Great progress looks like you are almost there  , can you make sure the collectors are running against your Hudson/Jenkins instance and same for Subversion, the collectors help populate the drop downs in the screen shot you have sent .

The collector seems to be running ok. If found the jobs initially.

I see data in mongo.

Not sure why it says "enabled":false tho

You can now select the build job in the Build Widget config. This will turn the HudsonCollectorItem's enabled (your screen shot above) to true.
The idea is this: Gather all the build job names and URLs so that the drop down can be populated- but don't collect build data yet. Collect build data only for the jobs that have been configured on dashboards.
Let us know how it goes.

This is where the problem is. Even though I see the collector running and the data in mongo, but the drop down in the widget still does not populate.

Do you get a json back from this: localhost:8080/api/dashboard?

Yep
[{"id":"55cb3dab5b6660b9e4bedf21","template":"capone","title":"My first dashboard","application":{"name":"Jumbo","components":[{"id":"55cb3dab5b6660b9e4bedf20","name":"Jumbo","collectorItems":{}}]},"widgets":[],"owner":"admin"}]

I am on gitter now - join me on gitter - (badge right below the Hygieia logo on GH)

mmm I think I found something ...
In API mongoconfig the mongo credentials are hardcoded:
databaseName = properties.getProperty("dbname", "dashboard");
host = properties.getProperty("dbhost", "localhost");
port = Integer.parseInt( properties.getProperty("dbport", "27017") );
userName = properties.getProperty("dbusername", "");
password = properties.getProperty("dbpassword", "").toCharArray();
System.out.println("dbusername=" + userName + ", password=" + password.toString());
I used 'dashboarddb' as database as I followed the api REAME example [dashboarddb].

@asperkins reported he had two databases in Mongo: dashboard and dashboarddb.
He removed the dashboard database things worked. I will check what created the dashboard database.

Actually I changed my collectors to use dashboard instead of dashboarddb. I think the api component may not be reading the properties file.

I got the Github collector and widget working.
The api component uses hard-coded properties in the  com.capitalone.dashboard.config.MongoConfig. So, I changed application.properties of the Github collector so it uses the same database ('dashboard') as MongoConfig. During startup, the collector is registered in the dashboard collection. Then I could add a Github widget in the UI.
It would help if there is a simple step-by-step tutorial which shows all the steps needed from building to create a new widget. The dashboard.properties example  '[dashboarddb]' in the README in API module put me on the wrong foot.

agreed - we need a better getting started guide

I am facing problem with my Github collector and the data it should show on the dashboard.
Please see it once -

Now  I have tried to add repo link to get a representation on the Dashboard UI, but I am not able -

In addition to that, The drop down boxes are empty ,, help me out please

How to get this github collector working ?

Unable to configure my github collector:
When I tried to enter my URL and click "SAVE", nothing happens.
I changed my db to "dashboard" and used the same in the collector.properties file and tried again but didn't work.  This is my api contents. Please help with your inputs in configuring the same.

Hurray.. I was able to configure the GIT dashboard.  This is what I did:

Switched to "dashboard" db.
Created the user in "dashboard" db.
Changed my application.properties file and dashboard.properties file to point to "dashboard" db.
Ran my API , gulp serve, and my collector again.
Deleted my cookies and browsing history and temp files and logged into my dashboard.
Configured the scm widget and it worked.

The tutorial should be updated with proper steps. I was going round and round with API, collector and DB for the past 2 days. Thank you all for your help !!! :) :) :) 👍


Expose dandiarchive as webdav service

To facilitate integration in various external projects (e.g., OSDF with Pelican underneath) which can interface to webdav services.  Treat it as unification of our API to a standard API for file access.
TODOs:

[x] decide on how to map our versions for dandisets within the path or some webdav supported mechanism for versioning (if there is any)
[x] double-check if webdav supports "redirection" so we do not need to tunnel all bytes from S3 through the webdav service but rather just redirect.
[x] implement mapping/endpoint: I wonder even if it somehow could be just the /paths endpoint, but likely not since that one is dandiset specific, but may be it could be at the top level of API
[x] decide on implementation

could be internal to dandi-archive.  pros:   more efficient since would operate directly on DB/within Python, likely minimizing flood of the logs; it would come "included" by default with any dandi-archive installation; would not require another web server to provide it;  as our API still in 0.x and adds breakages from time to time -- would be easier to keep consistent; cons: it would be easier/faster to develop/fix as independent service likely
could be some additional external service. pros: faster/easier to develop; would stress test our API more to see what it is missing;  cons: solution would need to provide yet another webserver

[ ] deploy as webdav.dandiarchive.org or at some other end-point (discussion below)

may be it could be implemented as independent service, not part of API.
attn @jwodder -- how much did you play with webdav?
edits:

https://github.com/mar10/wsgidav looks very promising and already has (non-production) backends for various things, e.g. for mercurial: https://wsgidav.readthedocs.io/en/latest/addons-mercurial.html .
re structure - I think we at large should mimic our S3, just adding a little more of consistency and have dandisets/ and zarrs/ (not zarr/) folders (problem for zarr/ though -- heavy folder listing).
on the best way to expose versions, possibilities, assuming that we do have some global prefix which ends with {dandiset_id}.

following mercurial example above -- have draft/, released/ (or latest/ - most recent release), releases/{VERSION}.  It kinda makes it to require draft/ or other prefix folder to get to content but it is consistent so I like it most.
have draft/, released/ (or latest/) and then all versions at the same level. kinda ok, but since numbered releases would most likely sort first and oldest first -- I think it would be not that convenient of a default view...
"smarty pants" version -- kinda making versioning optional and reacting to the regex for version at the top level and if not - giving the tree of the draft or most recent version... too smarty - don't like it
following our URL schema dandi://INSTANCE/DANDISET_ID[@VERSION][/PATH] and thus incorporating version into the folder name for dandiset  -- IMHO ugly

FWIW: filed https://github.com/mar10/wsgidav/issues/303

Side note: I'd appreciate it if the deployment procedure preserved enough of the Git history for it to be possible to run git rev-parse --short HEAD in order to embed the current Git commit in the binary.

may be also @kabilar and @aaronkanzer could help on this end since they are replicating DANDI infrastructure setup ?

I don't have the bandwidth for a few days, but I might suggest doing a proof-of-concept outside of dandi-infrastructure first since dandi-infrastructure is quite coupled with the Girder Terraform submodule (which, fortunately/unfortunately not overridable in Terraform land) -- feel free to correct me @waxlamp @mvandenburgh
@yarikoptic @jwodder perhaps just provisioning a Heroku dyno and including a Procfile with your Rust app and pushing it to the corresponding Heroku dyno would be good enough? (Just expanding on https://github.com/dandi/dandi-infrastructure/issues/166#issuecomment-1958516864)
Then you could have observability and stress-testing in the short-term in a more production-ish setting -- Heroku fortunately provisions an HTTPS-ready API URL (which eventually we would CNAME in Route53 to webdav.dandiarching.org) with the dyno. If successfully, we could append or easily build out more IaC in dandi-infrastructure.
Just some thoughts...

I don't have the bandwidth for a few days, but I might suggest doing a proof-of-concept outside of dandi-infrastructure first alone in Heroku since dandi-infrastructure is quite coupled with the Girder Terraform submodule (which, fortunately/unfortunately not overridable in Terraform land) -- feel free to correct me @waxlamp @mvandenburgh

Thanks @aaronkanzer, I definitely agree it makes sense to do an initial proof of concept outside of Terraform.

@yarikoptic @jwodder perhaps just provisioning a Heroku dyno and including a Procfile with your Rust app and pushing it to the corresponding Heroku dyno would be good enough? (Just expanding on #166 (comment))
Then you could have observability and stress-testing in the short-term in a more production-ish setting -- Heroku fortunately provisions an HTTPS-ready API URL (which eventually we would CNAME in Route53 to webdav.dandiarching.org) with the dyno. If successful, we could append or easily build out more IaC in dandi-infrastructure.

Agreed, I think this is the approach we should take - I'll start out by trying to set this up.

Side note: I'd appreciate it if the deployment procedure preserved enough of the Git history for it to be possible to run git rev-parse --short HEAD in order to embed the current Git commit in the binary.

@jwodder Heroku provides these values as environment variables at runtime - https://devcenter.heroku.com/articles/dyno-metadata#dyno-metadata. Is using the HEROKU_SLUG_COMMIT environment variable sufficient here?

@mvandenburgh I've created a PR to fetch the Git commit from HEROKU_SLUG_COMMIT if no normal Git information is available: https://github.com/dandi/dandidav/pull/95


magic plugin rankup.

Hey Nathan.
I have a problem. i did whit my wand /wand enchant and become Wizzard. there is a way to get Conduit but how i do that? i already bought al the spells in the enchantment table. and is there a command to rankup from Wizzard to Engineer?

The real way:
https://github.com/elBukkit/MagicPlugin/wiki/Progression#engineering-magic
Otherwise these commands should get you maxed out:
/wand add rollback
/wand add absorb
/wand add backup
/wand enchant 1000

I hope this answered your question! If not, please re-open.