🐞 reference to the private npm registry

Remove any reference to the other privare npm registry in the lock file

Any reference has been removed properly


[Feature Request] Make page preload work alongsider chapter preload for smoother streaming

Why/User Benefit/User Problem
If all pages of a chapter are preloaded, then the next chapter will also preload.
What/Requirements
Restrict chapter preload to 1 chapter so that it only preloads the next chapter, and not load all chapters.

Feature doesn't work the way I thought it did, so closing


[TACHYON-1610] User thread safety annotation in the common module

Addressed: https://tachyon.atlassian.net/browse/TACHYON-1610

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8148/
Test PASSed.

thanks for the improvement, I left a few comments!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8163/
Test PASSed.

+1 LGTM

LGTM


net/mail: ParseAddress may be incorrectly flagging valid values as errors

I expect that<EMAIL_ADDRESS><EMAIL_ADDRESS>will parse to
&mail.Address{
    Name<EMAIL_ADDRESS>    Address<EMAIL_ADDRESS>}

It's weird, granted, but I am guessing that the RFC for email parsing allows email-like things to be present in the Name field?
Noticed when using maintner to parse Gerrit emails. I also found this one:
Author: Author: Kevin Burke<EMAIL_ADDRESS>
(actual person's name withheld) which choked on the second Author: call.
It seems like it would be good to have a tool to validate the commit name/email before merge.

According to RFC 5322, given a string like<EMAIL_ADDRESS><EMAIL_ADDRESS>the first<EMAIL_ADDRESS>can only be parsed as a display-name.  An unquoted display-name can only contain what RFC 5322 calls "atoms", which can be alphanumeric characters or various special characters, but the list of special characters does not include '@'.  So I think that is not a valid address specification, and mail.ParseAddress is correct to reject it.
Similarly ':' is not permitted so I think your second string is also correctly rejected.

Gah, ignore me.


Add cern ohl v2

This PR contains all the commits from #854 adding the CERN-OHL v2 family of licenses. (See also the discussion in issue #853)
This remains a draft whilst we check and tweak the "how" field
Requirements
1. The license must have an SPDX identifier. If your license isn't registered with SPDX, please request that it be added.

CERN-OHL-P-2.0
CERN-OHL-S-2.0
CERN-OHL-W-2.0

2. The license must be listed on one of the following approved lists of licenses:

CERN-OHL-P-2.0
CERN-OHL-S-2.0
CERN-OHL-W-2.0

3. The license must be used in at least 1,000 public repositories. This may be documented, for example, with a GitHub code search.
As noted in #853,  there are a considerable number of projects using the CERN-OHL family of licenses.
This requirement appears to be to show the license is notable enough for inclusion. As the Open Hardware community is still settling on how best to share hardware, this increases the number of platforms that need to be searched. We provide the following further considerations:

The CERN OHL family is recommended by the Open Source Hardware Association
The CERN OHL family is recommended by journals such as HardwareX and Journal of Open Hardware
Inclusion of CERN OHL as the first OSI approved hardware specific licenses was deemed newsworthy by a major tech news website

4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by licensee if it knew about the license.
As discussed in #854 this PR updates the projects.

FWIW, this project took special care to properly apply the guidelines to use the S variant of the license (see discussion). The guidelines are quite long. I will try to extract the main features for the how field of the YAML files.

Some proposed changes here. In general, I like the way @nytpu used the note field to refer the the user guide of each variant. I just added a quick reference to the disclaimer of warranties which can be important for hardware, and the source location which ultimately can help the recipient of a piece of hardware find the design for that object. I also propose to avoid using the term "viral" which can have a negative connotation.

@j-sp your proposed changes look fine to me. I'd recommend shortening a bit by making the word "recommends" be link text (with the link being the one in the next sentence) and deleting the next sentence.

Thanks @mlinksva, done. @julianstirling, tell me if there is anything else I can help with.

Thanks @j-sp I have added your commits to the PR. I think this should be ready once the checks complete.

I get lots of errors when I run locally but I fixed the specific one that seemed to fail on the CI

I think this is ready to go? :tada:

For the W variant, I'd propose:

The weakly-reciprocal variant of the CERN OHL v2 was drafted with hardware in mind, using language which hardware designers can easily relate to. It covers rights other than copyright, features two-way patent licensing and provides methods to ensure the recipient of a piece of hardware can find the original design files. It was carefully drafted to achieve a weakly-reciprocal effect for hardware, taking into account the specificities of typical hardware design tools and workflows.

And for the P variant:

The permissive variant of the CERN OHL v2 was drafted with hardware in mind. It covers rights other than copyright, and features two-way patent licensing. It was carefully drafted to achieve an effect similar to that of permissive software licenses, using language hardware designers can unequivocally relate to.

@mlinksva, I am happy to add the text that @j-sp has suggested to each of the three licenses if we are all agreed.
On the point of if "with hardware in mind" is redundant... it largely is but it is also a point I think that is worth stressing and it is hard to stress well without redundancy. In the open hardware community we see many people new to the field applying software licenses to hardware, even ones with software in the name!

...drafted to achieve a strongly-reciprocal effect...

...drafted to achieve a weakly-reciprocal effect for hardware...

...drafted to achieve an effect similar to that of permissive software licenses...

If these new paragraphs are meant to replace the current description field, I'd like to point out that repeating the expressions "strongly reciprocal" and "weakly reciprocal" and "permissive" is not very useful, since those terms are already present at the start of each paragraph. I think the current wording is much clearer and more explicit:

...applies to a complete design, so if a CERN-OHL-S-2.0 file is used in a project then the full project must be released under the CERN-OHL-S-2.0 (or a compatible license).

...applies to individual designs but does not spread to the entire project it is included in.

...allows people to take your code, relicense it and use it without any obligation to distribute the sources when they ship a product; however, it does have an attribution requirement.

I understand you are trying to condense the text, but I believe in this case the additional length might be worth the clarity that describing these properties explicitly brings.

Thanks @waldyrious, I fully see your point. If clarity is key and space is not an issue, how about this for the S variant?

The strongly-reciprocal variant of the CERN OHL v2 was drafted with hardware in mind, using language which hardware designers can easily relate to. It covers rights other than copyright, features two-way patent licensing and provides methods to ensure the recipient of a piece of hardware can find the original design files. It was carefully drafted to achieve a strongly-reciprocal effect even in cases where the use of proprietary design tools and components, quite frequent in hardware design, would make a strong copyleft software license not usable (e.g. in HDL/FPGA design). This variant applies to a complete design, so if a CERN-OHL-S-2.0 file is used in a project then the full project must be released under the CERN-OHL-S-2.0 (or a compatible license).

I'm not a maintainer of this project, but IMHO I'd rather have the information. My only suggestion would be to connect the last sentence with what comes before, e.g.

This variant therefore applies to a complete design...

or

As such, this variant applies to a complete design...

(or some variant thereof). But that's a minor point — let's see what @mlinksva thinks about the overall expansion before bikeshedding the text :)

Small refinements to the proposed texts, hopefully capturing the suggestions of @waldyrious and @mlinksva except for brevity. We should be able to shorten them if needed.
S variant:

The strongly-reciprocal variant of the CERN OHL v2 was drafted with hardware in mind, using language which hardware designers can easily relate to. It covers rights other than copyright, features two-way patent licensing and provides methods to ensure the recipient of a piece of hardware can find the original design files. It was drafted to achieve a strongly-reciprocal effect even in cases where the use of proprietary design tools and components, quite frequent in hardware design, would make a strong copyleft software license not usable (e.g. in HDL/FPGA design). This variant therefore applies to a complete design, so if a CERN-OHL-S-2.0 file is used in a project then the full project must be released under the CERN-OHL-S-2.0 (or a compatible license).

W variant:

The weakly-reciprocal variant of the CERN OHL v2 was drafted with hardware in mind, using language which hardware designers can easily relate to. It covers rights other than copyright, features two-way patent licensing and provides methods to ensure the recipient of a piece of hardware can find the original design files. It was drafted to achieve a weakly-reciprocal effect for hardware, taking into account the specificities of typical hardware design tools and workflows. It therefore applies to individual designs but does not spread to the entire project it is included in.

P variant:

The permissive variant of the CERN OHL v2 was drafted with hardware in mind. It covers rights other than copyright, and features two-way patent licensing. It was drafted to achieve an effect similar to that of permissive software licenses, using language hardware designers can unequivocally relate to. It therefore allows people to take your design, relicense it and use it without any obligation to distribute the sources when they ship a product; however, it does have an attribution requirement.

The metadata looks ok, though I wonder if W variant's "external material" is closer to same-license--file than same-license--library given that it may only be combined using the covered source's documented interfaces.
The text looks identical to the versions on the CERN site, which I imagine it is from. Not to address here, but noting there are some very small differences between that text and what is recorded in SPDX, particularly the capitalization of modifying in  section 3 (all), the spelling of licen[cs]e in 7.1 (S and W, 6.1 in P), and in P the placement of You in 3.4. Might make sense to correct in SPDX.

The descriptions in the comment above are longer than any currently; I should add a test limiting to 500 characters, which is longer than any in the repository now.  The ones in committed are closer. I don't really care about whether things are worked out in comments or commits, but I'll go ahead and make suggestions as a review.

Thanks for all the pointers @j-sp. I think this is ready to merge and will do so soon, but feel free to propose further tweaks either before or after.

Thanks @mlinksva, I just noticed an extra space after the comma in the file for the P variant of the licence: "A permissive license for hardware designs,  with". All the rest looks good to me.

Great to see this merged! Thanks all!


Feature request: add prefix for downloaded library to avoid same version number conflict with other library

Currently downloaded library using jb, i.e
jb install github.com/jsonnet-libs/k8s-libsonnet/1.21@main
jb install github.com/jsonnet-libs/istio-libsonnet/1.13@main

will download the library in vendor folder as following
vendor
|- 1.21
|- 1.13
This convention will one day result in conflict when there are same version number for different library i.e kubernetes 1.21 with istio 1.21.
To avoid such conflict, suggest the folder to add prefix
vendor
|- k8s-1.21
|- istio-1.21

I agree this is an annoying consequence of naming and how jsonnet-bundler handles the "legacy" naming.
Personally I see this as a problem with jsonnet-bundler and ideally should be fixed there. Changing the naming upstream (here) would be a workaround for a downstream problem. Perhaps a jb install --name <name> <url> pattern would be a nice feature for jb.
As a quick workaround, you can set the 'name' attribute in jsonnetfile.json:
...
    {
      "source": {
        "git": {
          "remote": "https://github.com/jsonnet-libs/istio-libsonnet.git",
          "subdir": "1.13"
        }
      },
      "version": "main",
      "name": "istio-lib"  <--- set name here
    },
...

I've made a quick PR for jsonnet-bundler for this: https://github.com/jsonnet-bundler/jsonnet-bundler/pull/158 (not sure if they will take it as it is a legacy feature)

That PR got merged ^^ ✨

Yeah, I just saw that too! Many Thanks @Duologic :grin:


Windows 10 notification

There is no notification about successfull or failed build as it was in bobril-build.

I will try to do it.

Alright, I've found how to do it via PowerShell, do we have some specific needs how it should look like? I mean the template of the notification.
Initial proposal:

"Build was successful" + check mark icon
"Build failed" + cross icon

There could be also notification at least for failed tests.

I guess this one can be closed?


Named property binding

Before this change we only evaluated the special case for scripts. For everything else we always used the value property. But for some cases e. g. class-based execution listeners we need actually need to set the "class" attribute instead. Also, this align with the json schema definition.
Closes https://github.com/bpmn-io/bpmn-js-element-templates/issues/13
Note: I had to reopen, because I deleted my fork when cleaning up my repos... Forgot about the open pull request. See #15

Hi, thanks for the PR. In order to make the feature complete, we'd also need to:

[ ] prepare a documentation update (https://docs.camunda.io/docs/next/components/modeler/desktop-modeler/element-templates/c7-defining-templates/#camundaexecutionlistener)
[ ] update the schema to enforce either scriptFormat or name, but not both

Hi,
I am happy that you want to complete the loop :)
Both repos are the ones where we'd need to implement the changes. For the documentation, you'd need to look into this file specifically: https://github.com/camunda/camunda-platform-docs/blob/main/docs/components/modeler/desktop-modeler/element-templates/c7-defining-templates.md

Hi again @barmac ,
sorry for coming back to you again.
I just attempted to write documentation and realized that while name totally makes sense from the implementation side, it is not as intuitive for using it.
Once again name aligns with the attribute that is used for defining properties with a binding and basically that is what we do.
On the other side, from user perspective, it rather is the implementationType or shorter the type of this listener. Available types besides script are class, expression and delegateExpression.
So my question to you is, should we stick to name as I initially proposed because it works the same as already known for property bindings or should be more specific to this use-case?
I am fine with both approaches. I would appreciate your opinion on this, before I finalize my contribution.
Kind regards
Alexander Skrock

Hi,
Thanks for coming back. I looked into this more deeply, and indeed implementationType sounds like a more reasonable choice. I'd suggest to have the following rules in the JSON schema:

If implementationType is set on the binding, it has to have one of the values: [ 'script', 'class', 'expression', 'delegateExpression' ].
If implementationType=script is set, scriptFormat is required.

So let's keep the backwards compatibility, but also enforce correct values in the future templates.

Now, everything should be ready for review:

[x] Handling of the new attribute when applying element templates
[x] Documentation update to reflect the new behaviour
[x] JSON schema update to reflect new structure while preserving legacy templates

Thanks for the heads-up. I will look into these items today.

We will probably need to release a new version of bpmn-io/element-templates-validator for this.

What the matter with the current version? Maybe, I could do necessary changes.

It's OK. The validator depends on the JSON schema, so I need to update the JSON schema there in order to update it. I am in the process of merging your changes ^^. Thank you so much for your contributions

Validator update for reference: https://github.com/bpmn-io/element-templates-validator/pull/24

So once that PR is merged and validator is released, I will incorporate the update into this PR and merge it.

Thank you a lot for the effort!

OK this is now merged and I will publish it soon. Thank you @AlexanderSkrock for your amazing contribution!

Thanks indeed for this contribution. Well done :clap:


Enable buildkite for bors, and remove checks & tests from Travis

Issue Number

Overview

[x] I have removed Travis from bors, and instrumented it to now use buildkite instead
[x] I have kept Travis only for documentation and release builds, everything else now goes through buildkite (except code coverage being finalized in #695)

Comments

I have kept Travis only for documentation and release builds,

Is it temporary? It could be done with buildkite also I suppose...
(Maybe it's too much precaution, but it feels... weird having release binaries going from one CI and all the tests going on on other CI...)

@Anviking Would it be desirable to move these remaining things to buildkite too, eventually
@piotr-iohk Is it temporary? It could be done with buildkite also I suppose...

Not necessarily. We could do it from Buildkite though there's no built-in support for github deployments like we have in Travis, so that'll be extra work to do so. Since it's already easily done in Travis, we are leveraging it.
It's not necessarily weird but can be actually useful. Note Jörmungandr has a similar setup:


[1.10] Replace artisanal docer version detect script

Backports: https://github.com/dcos/dcos/pull/5993

High-level description
Fix problems with docker version > 1.19 which added new entries to docker version output.
Latest docker hase more entries in docker version output. See folowing examples
Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.35 (downgraded from 1.40)
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:07 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          17.12.1-ce
  API version:      1.35 (minimum version 1.12)
  Go version:       go1.9.4
  Git commit:       7390fc6
  Built:            Tue Feb 27 22:20:43 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:07 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:19:36 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

The previous script instead of Engine: Version: took docker-init: Version: and then took lowest version from client and server. This PR removes AWK script and replace it with sort -V which can correctly sort versions and docker version -f which allow us to use go template to get version in desired output`. Here we are interested only in client and server versions and choosing the lowest.
Corresponding DC/OS tickets (required)

DCOS-56831
DCOS-57154
DCOS-57676

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot request-review @drewvanstone @br-lewis @makkes @bamarni @rgo3

:wave: @drewvanstone @br-lewis @makkes @bamarni @rgo3  Can you review, please?

@mesosphere-mergebot label Ready For Review

@janisz please check out the CI failures.

@makkes Fixed

Closing in favor of https://github.com/dcos/dcos/pull/6131


Look into a pure Rust alternative for libkatatsuki, or CoreRT building on Linux.

TagLib on C++ is a mess, and exporting that to Rust will be too much of a hassle to be worth the maintenance cost. Look into pure Rust alternatives, or CoreRT libraries on Linux.
Rust Alternative Prerequisites

[x] FLAC Vorbis Comment
[x] ID3
[x] MP3 Specific
[ ] MP4 Atoms
[x] APE V2
[x] Ogg Opus
[x] Ogg Vorbis
[x] Ogg AudioProperties

All of these work with Vec<u8> for image data, which can be loaded into https://crates.io/crates/imagesize
Note that Vorbis and Opus are Base64 encoded image data. Need to convert Base64 String into Vec<u8>

mp4parse doesn't support meta tags.

Parsing meta tags is a whole lot of yak-shaving that I'm unwilling to implement. For the time being, we'll stick with the weird packaging of .NET code in Rust to use TagLibSharp, unless an MP4 meta parser appears some day.

porting over to use taglib2...

#8 will fix this


Track usage of extension via GA

Collect some basic information to get some insights about how the extension is used.
What we collect
We do not collect any personal identification information about Users whenever they interact with the OctoLinker.
We do collect non-personal identification information about Users whenever they interact with the OctoLinker. Non-personal identification information include the OctoLinker preferences from the option page, the link resolver name which is used to redirect you and if the redirect was succesful or not.
Please note that we use the Analytics extension ga('set', 'anonymizeIp', true); to ensure that IP addresses are collected anonymously.
Tracking example
{
"category": "resolver",
"action": "invoke",
"label": "javascriptUniversal"
}
{
"category": "fetch",
"action": "success"
}
{
"category": "options",
"action": "newWindow",
"label": "false"
}
{
"category": "options",
"action": "showLinkIndicator",
"label": "true"
}
{
"category": "options",
"action": "doTrack",
"label": "true"
}
{
"category": "options",
"action": "debugMode",
"label": "false"
}
{
"category": "options",
"action": "highlightLinks",
"label": "false"
}
{
"category": "options",
"action": "version",
"label": "4.6"
}

How we use collected information
The collected information are only used to improve the OctoLinker, nothing else.
Opt-out
To provide you with the ability to prevent data from being tracked by us, we have added an opt-out option in the settings. If you want to opt-out,  go the extension settings page and uncheck the Send anonymous usage reports to Google Analytics checkbox.

No, there is nothing left, but thanks for asking. I created a "Do not merge" label to communicate such things if needed.

That sounds great, thanks. I can't wait to see how the analytics look once they start coming in!

Me too. I'll take a look on #225 and after that we can do the next release.


[Bug] Heatmap value overflow: 'truncate' not dynamic

Version
5.3.3
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=heatmap-cartesian
Steps to Reproduce

Copy this code into the example

// prettier-ignore
const hours = [
    '12a', '1a', '2a', '3a', '4a', '5a', '6a',
    '7a', '8a', '9a', '10a', '11a',
    '12p', '1p', '2p', '3p', '4p', '5p',
    '6p', '7p', '8p', '9p', '10p', '11p'
];
// prettier-ignore
const days = [
    'Saturday', 'Friday', 'Thursday',
    'Wednesday', 'Tuesday', 'Monday', 'Sunday'
];
// prettier-ignore
const data = [[0, 0, 5], [0, 1, 1], [0, 2, 0], [0, 3, 0], [0, 4, 0], [0, 5, 0], [0, 6, 0], [0, 7, 0], [0, 8, 0], [0, 9, 0], [0, 10, 0], [0, 11, 2], [0, 12, 4], [0, 13, 1], [0, 14, 1], [0, 15, 3], [0, 16, 4], [0, 17, 6], [0, 18, 4], [0, 19, 4], [0, 20, 3], [0, 21, 3], [0, 22, 2], [0, 23, 5], [1, 0, 7], [1, 1, 0], [1, 2, 0], [1, 3, 0], [1, 4, 0], [1, 5, 0], [1, 6, 0], [1, 7, 0], [1, 8, 0], [1, 9, 0], [1, 10, 5], [1, 11, 2], [1, 12, 2], [1, 13, 6], [1, 14, 9], [1, 15, 11], [1, 16, 6], [1, 17, 7], [1, 18, 8], [1, 19, 12], [1, 20, 5], [1, 21, 5], [1, 22, 7], [1, 23, 2], [2, 0, 1], [2, 1, 1], [2, 2, 0], [2, 3, 0], [2, 4, 0], [2, 5, 0], [2, 6, 0], [2, 7, 0], [2, 8, 0], [2, 9, 0], [2, 10, 3], [2, 11, 2], [2, 12, 1], [2, 13, 9], [2, 14, 8], [2, 15, 10], [2, 16, 6], [2, 17, 5], [2, 18, 5], [2, 19, 5], [2, 20, 7], [2, 21, 4], [2, 22, 2], [2, 23, 4], [3, 0, 7], [3, 1, 3], [3, 2, 0], [3, 3, 0], [3, 4, 0], [3, 5, 0], [3, 6, 0], [3, 7, 0], [3, 8, 1], [3, 9, 0], [3, 10, 5], [3, 11, 4], [3, 12, 7], [3, 13, 14], [3, 14, 13], [3, 15, 12], [3, 16, 9], [3, 17, 5], [3, 18, 5], [3, 19, 10], [3, 20, 6], [3, 21, 4], [3, 22, 4], [3, 23, 1], [4, 0, 1], [4, 1, 3], [4, 2, 0], [4, 3, 0], [4, 4, 0], [4, 5, 1], [4, 6, 0], [4, 7, 0], [4, 8, 0], [4, 9, 2], [4, 10, 4], [4, 11, 4], [4, 12, 2], [4, 13, 4], [4, 14, 4], [4, 15, 14], [4, 16, 12], [4, 17, 1], [4, 18, 8], [4, 19, 5], [4, 20, 3], [4, 21, 7], [4, 22, 3], [4, 23, 0], [5, 0, 2], [5, 1, 1], [5, 2, 0], [5, 3, 3], [5, 4, 0], [5, 5, 0], [5, 6, 0], [5, 7, 0], [5, 8, 2], [5, 9, 0], [5, 10, 4], [5, 11, 1], [5, 12, 5], [5, 13, 10], [5, 14, 5], [5, 15, 7], [5, 16, 11], [5, 17, 6], [5, 18, 0], [5, 19, 5], [5, 20, 3], [5, 21, 4], [5, 22, 2], [5, 23, 0], [6, 0, 1], [6, 1, 0], [6, 2, 0], [6, 3, 0], [6, 4, 0], [6, 5, 0], [6, 6, 0], [6, 7, 0], [6, 8, 0], [6, 9, 0], [6, 10, 1], [6, 11, 0], [6, 12, 2], [6, 13, 1], [6, 14, 3], [6, 15, 4], [6, 16, 0], [6, 17, 0], [6, 18, 0], [6, 19, 0], [6, 20, 1], [6, 21, 2], [6, 22, 2], [6, 23, 6]]
    .map(function (item) {
    return [item[1], item[0], item[2]*100 || '-'];
});
option = {
  tooltip: {
    position: 'top'
  },
  grid: {
    height: '50%',
    top: '10%'
  },
  xAxis: {
    type: 'category',
    data: hours,
    splitArea: {
      show: true
    }
  },
  yAxis: {
    type: 'category',
    data: days,
    splitArea: {
      show: true
    }
  },
  visualMap: {
    min: 0,
    max: 10,
    calculable: true,
    orient: 'horizontal',
    left: 'center',
    bottom: '15%'
  },
  series: [
    {
      name: 'Punch Card',
      type: 'heatmap',
      data: data,
      label: {
        show: true,
        width:30,
        overflow:'truncate'
      },
      emphasis: {
        itemStyle: {
          shadowBlur: 10,
          shadowColor: 'rgba(0, 0, 0, 0.5)'
        }
      }
    }
  ]
};

Pull the Heatmap view smaller
Play around with series[0].label.width property

Current Behavior
Currently we have to set a fixed width for truncating the value of each cell. This results in the following behaviour:
Either the value is smaller than the width and it is displayed. Or the value is larger than the width. Then ellipsis is displayed.
Expected Behavior
I would expect that the width can be dynamic so that the value is truncated if there is not enough space and not truncated if there is enough space.
Environment
- OS: Windows
- Browser: Chrome
- Framework: Angular

Any additional comments?
No response

I didn't seem to find a problem when I tried it, was this problem solved?
Is this the expected effect?

(English is not my native language; please excuse typing errors.😁)


Error when viewing 404

Hi @letrunghieu,
Thanks for creating this! When visiting a 404 page, I get the following error:
TypeError
in_array(): Argument #2 ($haystack) must be of type array, string given (View: navbar.blade.php)

Any chance you could fix this please, only happens for if_route_pattern

This issue is old but I made #56 for this


Preload 1st segment and store for offline playback

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
If the question is related to FairPlay, have you read the tutorial?

Not related
What version of Shaka Player are you using?
4.11.0
What browser and OS are you using?
Android Webview & Chrome
Please ask your question
I have an infinite video feed (m3u8 videos) and I start loading a video once it comes into focus. But I would like to know if there's a way to preload just the 1st segment of the next video and store it in IndexedDB for offline playback. Once user comes on this video, then it should start download from 2nd segment onwards.
I tried to achieve this by using shaka.offline.Storage class, but it was downloading the entire video. So, I made some changes in the shaka player code and was able to download only 1st segment. But is there a way to load the video from 2nd segment onwards using player.load()?

What you are looking for is the preload API https://shaka-player-demo.appspot.com/docs/api/tutorial-preload.html :)

But can we store this segment as well in IndexedDB for offline playback using preload API? Basically what I'm looking for is like a combination of both preload and offline APIs.

Right now that's not possible and no one on the maintenance team will be working on this in the future. Sorry...


[ENH] Added providers to onnx runtime session

Refs:  https://onnxruntime.ai/docs/api/python/api_summary.html
Refs: #1004
Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

In multi-provider envs Onnyx Runtime requires that providers are specified (with order of preference) as input to the InferrenceSession

Test plan
Ideally, we'll need a GPU runners for testing - https://github.com/github/roadmap/issues/505
Documentation Changes
No change to docs is required.

Note: Sorry for the unsigned commit, I tried using GH Codespaces for this one.

I think if we are adding this, we should allow the constructor of the EF to consume the providers. That way, users can configure if they explicitly want to use a specific one.

Shall we also have sensible defaults e.g. if the user does not supply such providers then issue a warning log message and default to available ones?

Yep. Defaults can be as is and then we should just allow them to be
overridden.
On Sun, Aug 20, 2023 at 9:44 AM Trayan Azarov @.***>
wrote:

I think if we are adding this, we should allow the constructor of the EF
to consume the providers. That way, users can configure if they explicitly
want to use a specific one.
Shall we also have sensible defaults e.g. if the user does not supply such
providers then issue a warning log message and default to available ones?
—
Reply to this email directly, view it on GitHub
https://github.com/chroma-core/chroma/pull/1006#issuecomment-1685315604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKW32OHTXK4HVTXTBRRC4DXWIWD5ANCNFSM6AAAAAA3XECVLA
.
You are receiving this because you commented.Message ID:
@.***>

--
Hammad Bashir
EECS | Cal

@HammadB, I think it looks ok now.

Order of providers is important, we should check and error but not destroy user ordering.
[TA] OK, done. Added some checks on the preferred_providers list
Let's not warn for the default behavior so the majority of users don't experience a warning that will confuse them.
[TA] OK, done.
In the error message for subset, lets log the available providers.
[TA] OK, done.

@HammadB I think this is ready for merge


$matcher->createMatcher() capturing brackets

file ''Illuminate\View\Compilers\BladeCompiler.php"
The current 'createMatcher( ... )' function is matching all including the brackets.
i.e:
/*
 * @hello('world')
 * expected: world
 * captured: ('world')
 */

$compiler->createMatcher('hello');

Is this capture intended?
Because on Blade documentation, there's an example where you're extending Blade with the 'datetime' keyword, and it expects to capture the text within the brackets, not the text plus the brackets.
´´The following example creates a @datetime($var) directive which simply calls ->format() on $var:´´
I attach you the patched function below:
/**
 * Get the regular expression for a generic Blade function.
 *
 * @param  string  $function
 * @return string
 */
public function createMatcher($function)
{
	return '/(?<!\w)(\s*)@'.$function.'\s*\(\s*(.*)\)/';
}

Cheers, Jairo Tylera

According to tests it looks like intended behavior, but everyone admits that it's pretty confusing.
Taylor even removed that section from the docs.
So this is probably gonna be reworked in 5.1 (see #8425).
I don't think this method should be changed in 5.0 because many 3rd party packages are already adapted to the current behaviour.


[stable/kube-state-metrics]: Fix link to metric docu

What this PR does / why we need it:
I've fixed the link to the metric docu in the NOTES.txt of the kube-state-metrics chart
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

@florianrusch Could you rebase this PR?

@davidkarlsen FYI

@tariq1890 done

@florianrusch Thanks for your patience with this PR. Looks the following things need to be done.
i) Rebase with master and resolve merge conflicts.
ii) Fix the last review comment
iii) Squash the commits into one. The squash commit also needs to be signed off.

@tariq1890 Sorry, it's late here in germany. Hope everything is fine now :-)

/ok-to-test

/lgtm
/approve

/ok-to-test


Streamline error messages

Feature Description

We are returning the errors that we get from a database or any third-party service. Instead, we would like to streamline this process and make sure error messages can be easily translated for i18n purposes.
Describe the solution you'd like

Create common util to throw errors for incorrect data
Create common util to throw errors for server error

Describe alternatives you've considered

Additional context

Hi @lakhansamani
This looks like an interesting yet easy refactor. Is this open to contribution? If so I would want to contribute.


Channel query validation & tests

Closes: #148
Closes: #118
Closes: #164
Description

For contributor use:

[x] Unit tests written
[x] Added test to CI if applicable
[x] Updated CHANGELOG_PENDING.md
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Updated relevant documentation (docs/) and code comments
[x] Re-reviewed Files changed in the Github PR explorer

Ah, one more thing! If you merge master into your branch, you can get rid of the nightly coverage error. If others are picky about it, it's an easy solution.


Path aliasing doesn't work in +config.ts files

Description
I'm trying to use absolute import with path aliasing that I successfully enabled (it works properly in regular components):
import type { Config } from 'vike/types';
import { SITE_NAME } from '~/constants.js';

export default {
    title: SITE_NAME
} satisfies Config;

But it doesn't work in +config file:
> vite build

error during build:
Error: Cannot find package '~' imported from /src/pages/_error/[build-v1zeowuwiuuj]+config.ts.mjs
    at new NodeError (node:internal/errors:406:5)
    at packageResolve (node:internal/modules/esm/resolve:789:9)
    at moduleResolve (node:internal/modules/esm/resolve:838:20)
    at defaultResolve (node:internal/modules/esm/resolve:1043:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:228:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36)

As a workaround I've switched to relative imports, but itsnot convenient honestly :)

Define your path aliases at package.json#imports as described in https://vike.dev/path-aliases.
Also see https://github.com/vikejs/vike/issues/1547.

Can you create a minimal reproduction?


Users can create, read, update, and delete a profile in the database

User Stories

As a user, I can create my own profile that stores information about me

As a user, I can retrieve my profile data or another user's profile data

As a user, I can update my profile data

As a user, I can delete my profile

Set up and tested: it functions as intended.


Undefined reference to dnn in my package using ROS

Hello, I am trying to figure out a problem related to undefined reference to cv::dnn i am sure that i have not linked any dnn ibrary or does not set up the cmake flag. I have made a seperate repository for my project based in ROS framework and set up my CmakeLists.txt and doing the project for mysef. I have successfuy stream the intel camera in ROS package and now want to use open cv wrappers dnn modue in my project but not abe to add dnn library.
The error is
grasp_object_detection.cpp:(.text+0x870): undefined reference to cv::dnn::experimental_dnn_v2::readNetFromCaffe(cv::String const&, cv::String const&)' grasp_object_detection.cpp:(.text+0xbac): undefined reference to cv::dnn::experimental_dnn_v2::blobFromImage(cv::InputArray const&, double, cv::Size const&, cv::Scalar_ const&, bool, bool)'
grasp_object_detection.cpp:(.text+0xbe0): undefined reference to cv::dnn::experimental_dnn_v2::Net::setInput(cv::_InputArray const&, cv::String const&)' grasp_object_detection.cpp:(.text+0xc14): undefined reference to cv::dnn::experimental_dnn_v2::Net::forward(cv::String const&)'
grasp_object_detection.cpp:(.text+0x1304): undefined reference to cv::dnn::experimental_dnn_v2::Net::~Net()' grasp_object_detection.cpp:(.text+0x1690): undefined reference to cv::dnn::experimental_dnn_v2::Net::~Net()'
collect2: error: ld returned 1 exit status
For the successful libreasense streaming my CmakeLists are
cmake_minimum_required(VERSION 2.8.3)
project(pickplace)
*****************************CmakeLists,txt888888888888888888888888888888888888888888888
add_compile_options(-std=c++11)
find_package(realsense2 2.22.0)
find_package(catkin REQUIRED COMPONENTS
roscpp
std_msgs
cmake_modules
cv_bridge
ddynamic_reconfigure
diagnostic_updater
geometry_msgs
image_transport
message_generation
nav_msgs
nodelet
roscpp
sensor_msgs
tf
trajectory_msgs
dynamixel_workbench_msgs
dynamixel_workbench_toolbox
dynamixel_workbench_controllers
dynamixel_sdk
)
if(BUILD_WITH_OPENMP)
find_package(OpenMP)
if(NOT OpenMP_FOUND)
message(FATAL_ERROR "\n\n OpenMP is missing!\n\n")
else()
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${OpenMP_CXX_FLAGS} -fopenmp")
set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} ${OpenMP_EXE_LINKER_FLAGS}")
endif()
endif()
if(SET_USER_BREAK_AT_STARTUP)
message("GOT FLAG IN CmakeLists.txt")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DBPDEBUG")
endif()
if(NOT realsense2_FOUND)
message(FATAL_ERROR "\n\n Intel RealSense SDK 2.0 is missing, please install it from https://github.com/IntelRealSense/librealsense/releases\n\n")
endif()
if (CMAKE_BUILD_TYPE EQUAL "RELEASE")
message(STATUS "Create Release Build.")
set(CMAKE_CXX_FLAGS "-O2 ${CMAKE_CXX_FLAGS}")
else()
message(STATUS "Create Debug Build.")
endif()
set(CMAKE_CXX_FLAGS "-fPIE -fPIC -std=c++11 -D_FORTIFY_SOURCE=2 -fstack-protector -Wformat -Wformat-security -Wall ${CMAKE_CXX_FLAGS}")
find_package(Boost REQUIRED COMPONENTS thread)
set(OpenCV_DIR "/usr/local/share/OpenCV/")
find_package(OpenCV 3.4.3 REQUIRED)
add_subdirectory(dynamixel-workbench-master/dynamixel_workbench)
add_subdirectory(dynamixel-workbench-master/dynamixel_workbench_controllers)
add_subdirectory(dynamixel-workbench-master/dynamixel_workbench_toolbox)
include_directories(
include
${OpenCV_INCLUDE_DIRS}
${catkin_INCLUDE_DIRS}
${realsense_INCLUDE_DIR}
)
catkin_package(
INCLUDE_DIRS include
LIBRARIES pickplace
CATKIN_DEPENDS
cmake_modules
cv_bridge
ddynamic_reconfigure
diagnostic_updater
geometry_msgs
image_transport
message_generation
nav_msgs nodelet
roscpp
sensor_msgs
std_msgs
tf
trajectory_msgs
dynamixel_workbench_msgs
dynamixel_workbench_toolbox
dynamixel_workbench_controllers
dynamixel_sdk
DEPENDS Boost OpenCV
DEPENDS system_lib
)
add_executable(grasp_object_detection src/grasp_object_detection.cpp)
add_executable(grasp_app_robot src/grasp_app_robot.cpp)
add_executable(grasp_app_camera src/grasp_app_camera.cpp)
add_dependencies(grasp_object_detection ${${PROJECT_NAME}_EXPORTED_TARGETS}  ${catkin_EXPORTED_TARGETS} grasp_object_detection_generate_message_cpp)
add_dependencies(grasp_app_robot ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
add_dependencies(grasp_app_camera ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
target_link_libraries(grasp_object_detection
${catkin_LIBRARIES}
${OpenCV_LIBS}
${realsense2_LIBRARY}
${Boost_INCLUDE_DIRS}
)
target_link_libraries(grasp_app_robot
${catkin_LIBRARIES}
${OpenCV_LIBS}
${realsense2_LIBRARY}
${Boost_INCLUDE_DIRS}
)
target_link_libraries(grasp_app_camera
${catkin_LIBRARIES}
${OpenCV_LIBS}
${realsense2_LIBRARY}
${Boost_INCLUDE_DIRS}
)
set(PROTOTEXT_FILE "MobileNetSSD_deploy.prototxt")
set(PROTOTEXT_URL "https://raw.githubusercontent.com/chuanqi305/MobileNet-SSD/f5d072ccc7e3dcddaa830e9805da4bf1000b2836/MobileNetSSD_deploy.prototxt")
set(PROTOTEXT_PATH "${CMAKE_CURRENT_BINARY_DIR}/${PROTOTEXT_FILE}")
set(MODEL_FILE "MobileNetSSD_deploy.caffemodel")
set(MODEL_URL "https://drive.google.com/uc?export=download&id=0B3gersZ2cHIxRm5PMWRoTkdHdHc")
set(MODEL_PATH "${CMAKE_CURRENT_BINARY_DIR}/${MODEL_FILE}")
if(NOT EXISTS "${PROTOTEXT_PATH}")
message("Downloading ${PROTOTEXT_FILE} into ${CMAKE_CURRENT_BINARY_DIR}")
file(DOWNLOAD "${PROTOTEXT_URL}" "${PROTOTEXT_PATH}")
endif()
if(NOT EXISTS "${MODEL_PATH}")
message("Downloading ${MODEL_FILE} into ${CMAKE_CURRENT_BINARY_DIR}")
file(DOWNLOAD "${MODEL_URL}" "${MODEL_PATH}")
endif()

but not able to use this with dnn. I have tried many solutions. write the Cmake fies according ti wrappers open cv Cmake but all in vain. I am aso wondering if there any soution ies in adding the flag
"-lopencv-dnn"  anywhere

Finally I solved it. The issue is with the mismatched version of open cv. The ROS version has opencv 3.3.1 and i am using opencv 3.4.
Basically the error is cv::dnn::experimental_dnn_v2
The dnn is included when i link the open cv library but the experimental_dnn_v2 header has different names for different opencv version.
The solution is:

Uninstall the ros-opencv version by
sudo apt-get remove ros-kinetic-opencv
and then do
source /opt/ros/kinetic/setup.bash

Comment the cv_bridge from CmakLists.txt file (from find package and catkin_package)

Remove the cv_bridge dependencies from package.xml file

include the directory of the installed open cv from your pc in CMakeLists.txt. See my CmakeLists.txt above

Build
I used ROS so i used catkin_make
if catkin_make does not work you can try
catkin_make VERBOSE=1 -j4 -DCMAKE_BUILD_TYPE=Release --cmake-args -DOpenCV_DIR= /usr/local

At /usr/local i have opencv installed
Thanks


作者你好，我这面在运行nms_demo.py时出现了以下问题

2019-04-24 16:07:03.921095: I tensorflow/core/common_runtime/gpu/gpu_device.cc:971] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-04-24 16:07:03.921129: I tensorflow/core/common_runtime/gpu/gpu_device.cc:977]      0
2019-04-24 16:07:03.921135: I tensorflow/core/common_runtime/gpu/gpu_device.cc:990] 0:   N
2019-04-24 16:07:03.921337: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1103] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10136 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:02:00.0, compute capability: 6.1)
2019-04-24 16:07:08.222893: E tensorflow/stream_executor/cuda/cuda_dnn.cc:343] Loaded runtime CuDNN library: 7.1.4 but source was compiled with: 7.2.1.  CuDNN library major and minor version needs to match or have higher minor version in case of CuDNN 7.0 or later version. If using a binary install, upgrade your CuDNN library.  If building from sources, make sure the library loaded at runtime is compatible with the version specified during compile configuration.
段错误 (核心已转储)

知道是版本问题，有降低tf的版本的解决方案，这种方案会不会影响后续实现，会的话是不是要升级cudnn

已升级

已升级

我也遇到这个问题，请问是怎么解决的


Evaluate facebook/llm-compiler-13b

Looks like this model is hyper-specialized and only understands LLVM IR and ASM.


Stop Sphinx from forcing alphabetical order

E.g. relaxation.py needs to start with LiouvilleRelaxationBase

Add autodoc_member_order = 'bysource' to docs/conf.py.
Source: https://stackoverflow.com/questions/37209921/python-how-not-to-sort-sphinx-output-in-alphabetical-order
Moving this to milestone v1.0.0 so we sort by alphabetical order until then.


[Question] Imgur ID

I'm sorry but what is the Imgur ID that I can supply.  Can you point me in the right direction?

The Imgur ID is the identifier that the program uses when contacting Imgur, which is how they apply rate-limits to our requests. The program has an imgur ID embedded for general use so you dont need to supply one.
However, if you expect to use the downloader heavily then switching to your own ID where you dont have to share the rate-limits with all the other users of the program is possible. To get your own ID do the following:

Login to Imgur
Go to this page: https://api.imgur.com/oauth2/addclient
Fill out the form.

For Authorization type select Anonymous usage without user authorization.
The Authorization callback URL must be filled out but isn't used by the program.
Fill out the rest as desired.

Copy the resulting client id (not the client secret)
Paste the id into the Imgur ID box and press Save settings
Then restart the program.

If you forget the client id or want to delete it from your account, see this page: https://imgur.com/account/settings/apps

Ok.  Thank you.  I thought that is what it was but for some reason it was telling me it was invalid before.  Looks like it is working now.  Thanks for clarifying.


Unknown manufacturer, 0xXXXX, Unknown product

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
Checklist

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

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

Describe the bug
What causes the bug?
Not sure what is causing it
What do you observe?
Devices keep going to "Unknown manufacturer, 0xXXXX, Unknown product 0xXXXX" ?
This is the third time it's happened, very annoying. Everything in HA fails when this happens.
I end up having to remove them and add them again to get them to work.
zWave stick info HUSBZB-1 (Silicon Labs Z-Wave 500 Series Controller ACC-UZB3)
What did you expect to happen?
Once added I expect them to stay remembered and not go to unknown
Steps to reproduce the behavior:

Add zWave devices
Wait for them to turn up as unknown (not specific time)
I do reboot my HA device (NUC) daily
Maybe rebooting will make it repro

Device information
Manufacturer:
Model name:
Node ID in your network:
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] 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)
[X] Other (please describe)

Which branches or versions?
snap install
store-url: https://snapcraft.io/zwavejs2mqtt
installed:          v6.2.0            (315) 137MB
snap-id:      k26XpW9UYHL1HNh20isi5MHoazqHZ8br
tracking:     latest/edge
refresh-date: yesterday at 05:25 PST
zwavejs2mqtt: 6.2.0.fa6b2ab
zwave-js: 8.9.3-0-pr-4011-940427a
home id:<PHONE_NUMBER>
home hex: 0xfee18213
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Yes, it works for a while before this issue appears
Attach Driver Logfile
zwavejs_2022-01-03.log

Hi. Please note that the edge channel uses experimental versions. You should use the channel latest/candidate for rolling releases and latest/stable for stable release. The latter one mainly only releases the final release for each major version, while candidate for each minor and/or patch.
The edge branch you're on got updated yesterday with a test of a certain branch of zwjs, to test a feature that was specific for a device. It can be updated x amount of times in a row and causes stability issues such as this.
Leaving your network running should re-interview the nodes, but that can take time.

Also sometimes i helps to just restart if the interview process finishes with an unknown device.
sudo snap stop zwavejs2mqtt
sudo reboot

If it doesn't help. Re-interview node by node, and make sure each finish before starting a new interview.

I saw the same behavior on the latest/stable release, which is why I moved the edge release hoping it might resolve or fix my issue
I've also tried rebooting...doesn't fix it
It's been sitting for most of the day and hasn't re-found, re-identified the devices correctly

Have you tried to solve it for just one device? Interviewing your whole network will cause a very high load on your network.

I've tried re-interviewing individual ones multiple times
I've tried just about everything multiple times...not sure what is causing this
.
It will be fine for weeks and then one day it just does this (nothing changed)

It's only happening on these are newer Eaton devices
https://devices.zwave-js.io/?jumpTo=0x001a:0x4449:0x0501:0.0
https://devices.zwave-js.io/?jumpTo=0x001a:0x534c:0x0503:0.0

Node 22 is included securely:
2022-01-03T22:41:42.380Z CNTRLR « [Node 022] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Transport Service
                                  · Security
                                  · Security 2
                                  controlled CCs:

and the driver thinks it is NOT included with Security S2, so it only checks S0 but that yields an empty list of CCs:
2022-01-03T22:41:54.843Z DRIVER « [Node 022] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[SecurityCCCommandsSupportedReport]
                                        reportsToFollow: 0
                                        supportedCCs:
                                        controlledCCs:

Its the same with Node 21.
I'm not sure how that happened, but somehow the driver must have not been able to figure out which S2 classes the nodes support... Incorrect keys, timeouts during initial interview, broken cache during upgrade, ...
I don't think you're able to reset this information via the UI yet. You can try this, but the procedure to get to the cache file is going to be a little different for Snap. @jmgiaever?
Make sure to only remove this section for the problematic nodes.

Thank you for looking into this and the "try this" info :-)
I went ahead and removed and re-added the devices
I added them this time with S2_Authenticated only...we'll see how it goes.
I'm also not going to reboot my system for awhile.
If I have problems again I will look at the "security classes"
This is how it looks when it's working
"dsk": "47256-00133-11506-53356-41327-05514-24302-42460",
"securityClasses": [
"S2_Authenticated"
],
Here's how they look after being re-added

Thanks again

Z2M has this "reset security classes" option when you want to re-interview anything. Guess that's doing the same as you linked to @AlCalzone ?

Not sure when/why the security class is resetting or changing to the "S2_Authenticated": false.
It's NOT because of a re-interview.
The only thing that might have caused it was a reboot, I reboot the machine my zwavejs2mqtt/HA is on daily
But it rebooted for weeks before the "unknown" or security class change showed up

It's NOT because of a re-interview.

Yeah, but a re-interview with that option enabled should fix the problem without excluding and including again. I expect this to go away once I've reworked how the JSON cache file gets written.

That would be great if you can fix it...it sounds like you know what the problem might be
Do you need anything more from me at the moment?

Nope, thanks!

Once you've reworked this...will I be able to reboot my system without loosing my devices?

You should be able to already now, just make sure to shut down z2m first.
sudo snap stop zwavejs2mqtt


added exportmacro identifier in for loop

Description of the change
Adding functionality to be able to define and import macro within a for loop to be used in the rest of the template. Key is using exportmacros as an identifier in for loop. In the below template abc = [1,2]
{% for x in abc exportmacros %}
    {% if x == 1 %}
        {% import "x.template" m4 %}
    {% else %}
        {% macro m5() export %}
            m5 value
        {% endmacro %}
    {% endif %}
{% endfor %}
--
{{m5()}}
{{m4()}}

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

Fix #1

Checklists
Development

[ ] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[ ] All tests related to the changed code pass in development

Code review

[ ]  This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers mentioned in a comment
[ ] Changes have been reviewed by at least one other engineer
[ ] Issue from task tracker has a link to this pull request

This seems like it will be very easy to overwrite macros and difficult to define multiple ones.  Why do we want this?  Seems like you could just define a macro you want and pass in the item you're looping over and it's key and get the same functionality.  Without dynamic macro names, I don't really see the point?

This seems like it will be very easy to overwrite macros and difficult to define multiple ones. Why do we want this? Seems like you could just define a macro you want and pass in the item you're looping over and it's key and get the same functionality. Without dynamic macro names, I don't really see the point?

We want to loop over feature YAML contents and define and possibly reuse macros contained there.

You added the exec keyword already, wouldn't you just loop over the user defined macros and create a macro template based on them, then add it to the template as exec userMacros or something?

To define macros in the feature yaml, you would need the macro name to be dynamic based on the name the user gave to it.  So, you would need to set the macro name based on a variable.  Could you do that?

The issue with forloop is that pongo creates a child execution context and the macros defined in for loop stay in the scope of that forloop only.. in order to be able to use that macro outside the forloop we have to export the macro to parent context. That is what is targeted in this PR.
Dynamic naming of macro is not possible. can we use string formatting to define the macro name prior to parsing it by pongo? that will fulfil the requirement of dynamic naming i suppose.

The issue with forloop is that pongo creates a child execution context and the macros defined in for loop stay in the scope of that forloop only.. in order to be able to use that macro outside the forloop we have to export the macro to parent context. That is what is targeted in this PR.
Dynamic naming of macro is not possible. can we use string formatting to define the macro name prior to parsing it by pongo? that will fulfil the requirement of dynamic naming i suppose.

That is why it seems like this won't support the idea of defining the macros defined in a feature table in pongo.  I think you would need to create a userMacros template or something by using pongo to create a pongo template, then import it using exec.

If you do need to do this for some reason I'm not seeing, could you make it so that by default all macros could be exported from a loop, but to do so need the global keyword on them?  That would match more closely to a programming language expectation.  Note that Jinja - which is very similar to pongo2 and is the templating language dbt uses - also scopes loops (and other blocks) and does not allow exporting variables inside them to outside their scope:
https://jinja.palletsprojects.com/en/3.0.x/templates/ - look at Scoping Behavior


Fix README content and its formatting

Hello there, I noticed that there were some minor formatting issues in the README and also that the initial sentence didn't quite read well so I decided to modify it a little bit.
I welcome feedback and amendment request if necessary.
Cheers,
Debo

@debo  Thank you for the contribution!


Dynamic Villagers doesn't support Enchantented Machinery

If you use enchanted machinery with dynamic villagers the villagers won't do their job because enchanted machinery seperates the normal drill for their enchantable ones (this can be seen if you use Jade). It would be nice if you could add support for this if possible and more drill heads if possible.

Noted, will take a look. Great issue, thank you!


Changing temp/mode in HA change Carrier to Hold Indefinitely, even when unchecked.

System Health details
System Information

version
core-2024.10.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.31-haos-raspi

arch
aarch64

timezone
America/New_York

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4983

Installed Version
2.0.1

Stage
running

Available Repositories
1459

Downloaded Repositories
26

Home Assistant Cloud

logged_in
true

subscription_expiration
January 28, 2025 at 7:00 PM

relayer_connected
true

relayer_region
us-east-1

remote_enabled
true

remote_connected
true

alexa_enabled
false

google_enabled
true

remote_server
us-east-1-1.ui.nabu.casa

certificate_status
ready

instance_id

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 13.2

update_channel
stable

supervisor_version
supervisor-2024.10.3

agent_version
1.6.0

docker_version
27.2.0

disk_total
28.0 GB

disk_used
20.7 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
yellow

supervisor_api
ok

version_api
ok

installed_addons
Terminal & SSH (9.15.0), Studio Code Server (5.17.2), Z-Wave JS (0.8.1), ESPHome (2024.10.2), Mosquitto broker (6.4.1), Piper (1.5.2), Whisper (2.2.0), openWakeWord (1.10.0), Matter Server (6.6.0)

keymaster

zwave_integration
zwave_js

network_status
on

Dashboards

dashboards
6

resources
13

views
16

mode
storage

Recorder

oldest_recorder_run
October 28, 2024 at 11:41 PM

current_recorder_run
October 31, 2024 at 1:29 PM

estimated_db_size
259.43 MiB

database_engine
sqlite

database_version
3.45.3

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Whenever I adjust the thermostat in HA, carrier sets the thermostat to manual hold indefinitely instead of "hold until next scheduled profile." I have "Holds are infinite, when off holds are until next scheduled activity" currently unchecked. -- Apologies on the lack of some diagnostic data. I was having difficulty with the logging. I can gather more specific info as needed. Thank you for this project.
Reproduction steps

Set carrier to run on schedule from app or HA
Change temperature in HA.
See in app it's set to hold indefinitely.
...

Debug logs
N/A

Diagnostics dump
NA Too Long

I’ve seen this issue consistently since I installed this component a couple months ago.  I haven’t taken any steps to document or debug, but I can confirm this is an issue.

It looks like that setting only applies to when you change the preset mode:
https://github.com/dahlb/ha_carrier/blob/1e2f46e2a204841bb4f3b7a28f4887c1c44449ac/custom_components/ha_carrier/climate.py#L278-L283
and not when you change the temperature:
https://github.com/dahlb/ha_carrier/blob/1e2f46e2a204841bb4f3b7a28f4887c1c44449ac/custom_components/ha_carrier/climate.py#L335-L341
It would need an update to the carrier_api pypi library as well as this component, but I would also like to see this behavior implemented.

1.23.0 was just released and it should respect the hold preference for manual activities too :) thanks for writing this up

Thanks @dahlb! I tested it and it seems to work as expected.


Higher resolutions in Bing imagery not showing in iD

Came across a lot of offset building footprints create in iD, while editing in JOSM. When looking into the area in iD, I noticed that the imagery was overzoomed and was not switching the the higher resolution imagery I was seeing in JOSM.
Not sure if this is a bug, but having users of JOSM and iD seeing different imagery at the same zoom level can lead to inconsistent data like this.
OSM link: https://www.openstreetmap.org/#map=19/16.81692/81.53699

GIF comparing the switching of imagery in JOSM and iD (9mb)

Yeah JOSM is definitely switching imagery beyond z19.. I don't know what they are doing, but I'm pretty sure that imagery is not coming from Bing.
I did try requesting tiles from Bing for this area, but they are not returning anything for z19, so iD overzooms.
For example, this request returns a 200 response but X-VE-Tile-Info: no-tile.

Cross posted on JOSM trac for further details https://josm.openstreetmap.de/ticket/11431


feat: Refactor the directory sturcture of model bundle

What this PR does / why we need it:

Add an example for PMML
Refactor the directory structure of the model bundle

Mainly move the ormbfile.yaml to the upper directory

Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #7
Reference to #

Special notes for your reviewer:
/cc @supereagle @ddysher @codeflitting

Release note:

NONE

/lgtm
@gaocegege  I'll pair with you before folks are ready to jump into the project.

/hold

/hold cancel


COMPAT: numpy compat with NaT != NaT, #12049

closes #12049

cc @shoyer
so just a minor change actually. So ok from me to leave numpy as is I think. (though you still might want to deprecate / do next release in any event)

I think that people will be unhappy if numpy issues a release that breaks the latest release of pandas.... so I think numpy needs to wait either way.

ok should be good now.
if its changed to a DeprecationWarning I think we shouldn't show it, but will have to see

LGTM

now if Travis-CI would just work :< notice its been red all day


feat: Element locking

Closes #1976

Excited for this to land!
Some notes:

[ ] selectAll action should omit locked elements to align with other apps out there (figma, miro...).

[ ] you should be able to box-select over a locked element. Meaning, if you start dragging over a locked element, right now it prevents box-selection. Here's Miro:

If this proves too hard, we can leave it for another PR.

[ ] cursor shouldn't update for locked elements (right now it shows move cursor when hovering over a locked element)

I've taken the approach right now to only implement locking for single elements, ignoring locking of groups. I think to implement group locking you would need to track the lock state of groups in the app state, unless there is a different way?

I think the way to go is to lock all the elements within a group, and when selecting a group we'd check if all elements within a group are locked → if yes, then prevent group selection.

I think the way to go is to lock all the elements within a group, and when selecting a group we'd check if all elements within a group are locked → if yes, then prevent group selection.

Oh that's a good idea, I'll take a look at this.

re

you should be able to box-select over a locked element. Meaning, if you start dragging over a locked element, right now it prevents box-selection.

If box/drag-selecting shapes/elements over a locked ("background") element does not work, what is the workaround - I guess shift selecting the individual elements...?

@chipbite As it is right now you can absolutely box select over a locked element, you just have to deselect it first after locking it. In other words, you can't start a box selection over a selected locked element. This is the behaviour in tldraw but I can see that miro works differently.

@chipbite As it is right now you can absolutely box select over a locked element, you just have to deselect it first after locking it. In other words, you can't start a box selection over a selected locked element. This is the behaviour in tldraw but I can see that miro works differently.

Really? Doesn't work for me when I try:

The big use case I'm thinking of is you have a large background locked and you want to select items on top of it (indicated by the dashed rectangle below):

Ah, it appears that you can't start a selection if you start within the hitbox of locked element, that isn't intended
https://user-images.githubusercontent.com/9257001/159976647-282840a3-8cb4-4a20-8fe0-0830b89eb1e8.mov

I've fixed the box-select issue 👍

I've noticed that box select can select elements underneath locked elements
https://user-images.githubusercontent.com/9257001/160027057-694e6712-ea06-4b83-bb23-fa744b1a791d.mov
This is a little confusing but I don't think a massive deal for UX, what do you think?

I think the way to go is to lock all the elements within a group, and when selecting a group we'd check if all elements within a group are locked → if yes, then prevent group selection.

@dwelle Just thinking about this some, I think this might lead to some confusing behaviour... I can group two elements and then lock one of them. What you describe would allow movement of the locked sibling in the canvas which I don't think is correct.
Miro solves this by removing the element from it's group when it goes into a locked state. It can do this without being confusing because Miro doesn't allow nested groups. An excalidraw element would need to "pop out" of all ancestor groups which seems confusing.

I think the way to go is to lock all the elements within a group, and when selecting a group we'd check if all elements within a group are locked → if yes, then prevent group selection.

@dwelle Just thinking about this some more, I think this might lead to some confusing behaviour... I can group two elements and then lock one of them.

Not sure at all, just an idea, but maybe this should not be possible...? If you lock an element the entire group is locked..? I wonder how that would pan out...
What would be an example situation where you would want to lock one element in a group?

Put a bit differently, what would be an example situation where you would want to lock one element in a group?

I think yes. You have a library item or something where it's composed of a background (happens a lot for white-background things) that you don't want moved when editing the group elements.
More generally, I'm not seeing the UX issues. We should follow what Figma is doing:

when an element in a group is locked but there are other elements, the group can be selected
if such a group is moved, all elements in the group are moved, even the locked ones
if all elements in a group are locked, the group can't be selected

Ok that sounds simple enough to implement, I'll have a crack 👍

Alright think I got that working, let me know what you think!
If we're happy then there are two outstanding items:

Shortcut: see the thread above
Arrow head connections on locked elements. Really struggling to find the relevant code for this - could you point me in the right direction please?

If we're happy then there is only the outstanding item of shortcuts, see the above thread for that 👍

I can take a look at the shortcuts in a bit.
I've noticed a bug around group locks: if you start box-selecting over a group element that's locked, from the moment the box selection selects a non-locked element from that group, the group is selected and dragged, jumping around.
I think the issue stems from the group thinking you've started dragging because you initially clicked on a group member even if it was locked. I don't recall our implementation exactly, but it'll likely be related to pointerDownState and how we determine if drag has occurred.
Below, the blue rectangle is locked and both are in a group:

Pushed 3 commits:

fix for the shortcut. Haven't checked on Mac yet.
I've rewritten how we disable arrow binding: what you were doing was mostly disabling just the visual clues, but not the binding itself
I've done the same for text:container binding

Nice, thanks. I think I know how to fix the group box selection issue you mentioned but feel free to push something up if you get there before me.

@dwelle The shortcut doesn't work for me now. I'm on Macos, are you on linux/windows? I wonder if it's an OS thing

I've now tested both on Windows and MacOS and it works for me. Can some extension/app be blocking it on your end? Does it work for you in Figma (they use Cmd-Shift-L)?

Nice, thanks. I think I know how to fix the group box selection issue you mentioned but feel free to push something up if you get there before me.

Haven't looked into it, so if you already have an idea how to solve it, go for it!

That shortcut definitely works in tldraw, I'll check figma too.
Won't be back at my desk until tomorrow but will check back in then 👍

Great comment, I agree on the whole. 👍

I think yes. You have a library item or something where it's composed of a background (happens a lot for white-background things) that you don't want moved when editing the group elements.

I may be old school, but if the use case ( not sure if that is what you mean) is to edit a library item or similar, I would expect to have to explode/ungroup, do edits and then regroup. Given this POV, I still think that it would also make sense to make locking per group. But maybe I am not seeing this UC clearly.
Anyhow, again - I agree with what you said below, good approach. The benefit of the figma approach below is that it may even be more intuitive; I think my expectation above is colored by using other packages.

More generally, I'm not seeing the UX issues. We should follow what Figma is doing:

when an element in a group is locked but there are other elements, the group can be selected
if such a group is moved, all elements in the group are moved, even the locked ones
if all elements in a group are locked, the group can't be selected

👍

Did some testing of this today. A great addition and everything is behaving as I would expect in a locked state. Although I am not able to get the keyboard shortcut to work. I'm on a Windows Surface Laptop 2 and my Windows keyboard settings are English (United Kingdom). This is reproducible for me even in Incognito (no extensions). Shorcute works fine on MacOS for me.

I tested this on Android (Note 8) and iOS (iPad). Overall works well I was able to lock and unlock elements, but the context menu is a bit clunky. Could we not add lock under actions? next to link? at least on the mobile menu?

@zsviczian Great idea! I'd vote putting it there too, should be simple to do

the context menu is a bit clunky. Could we not add lock under actions? next to link? at least on the mobile menu?

The placement of lock between duplicate and delete can be improved, I feel. Moving it above duplicate would be better, IMO. Maybe there are other alternative placements.

I'm not sure it's a good idea to put the lock in the actions menu, because for unlocking you must go through contextMenu anyway.
As such, keeping it symmetrical is better in terms of UX — if users don't already know that unlocking is done via contextMenu and they mistakenly lock an item from the sidebar (and deselect the element) as part of trying out what the button does, they won't know how to unlock.
But, I agree the contextMenu placement isn't great due to being too close to delete. I think we should add another separate between Delete and the other items.

since we have the eraser do we still need delete in the context menu?

I'm not sure it's a good idea to put the lock in the actions menu, because for unlocking you must go through contextMenu anyway.

I am ignorant wrt UI policy for this "actions menu" panel/palette, but would not a possible approach to including lock in that panel be to have an state / property icon? Locked vs unlocked, like in a properties panel or layers panel? That would atleast make it symmetrical, right?

I am ignorant wrt UI policy for this "actions menu" panel/palette, but would not a possible approach to including lock in that panel be to have an state / property icon? Locked vs unlocked, like in a properties panel or layers panel? That would atleast make it symmetrical, right?

Right, but to select a locked element you still need to right-click (i.e. open a contextMenu).

since we have the eraser do we still need delete in the context menu?

Eraser is a different workflow. I've checked analytics for deleting (which we've started tracking just yesterday), and people delete via contextMenu in around 2% of cases (desktop UI). Let's make the call whether we remove it from contextMenu later.

Right, but to select a locked element you still need to right-click (i.e. open a contextMenu).

Duh, yes of course. Monday morning.... 😊

I feel as if this PR is ready to be merged. Are there still any outstanding actions? What is holding us back?

I think there is just the one group selection big remaining as mentioned here https://github.com/excalidraw/excalidraw/pull/4964#issuecomment-1079138095
I did look at this briefly but couldn't figure it out, would be great if someone could take a stab at it 👍

While I guess the solution will be somewhere in App.tsx I think this is a good debug point to start understanding what is going on. This is triggered right before the jump. I will look into this a bit more in the evening, but if some finds the solution earlier, that would be even better :)
https://github.com/tom-sherman/excalidraw/blob/058fb4b8b7752e339ff6a83d72a49d9907da63eb/src/groups.ts#L90

Found it!
https://github.com/excalidraw/excalidraw/blob/b9e928088591c5e6da943e20d0780c620398ff52/src/components/App.tsx#L2151-L2165
https://github.com/excalidraw/excalidraw/blob/b9e928088591c5e6da943e20d0780c620398ff52/src/components/App.tsx#L3448-L3453

I've changed the excludeLockedElements to includeLockedElements (inverted), IOW default to not selecting locked elements, which aligns it with the includeBoundTextElement arg, and fixes other cases as well.
Before we merge I want to do a proper review and refactor, as this is a larger change.
We should also write some tests for this, such as:

[ ] click-selecting or box-selecting locked elements is disabled
[ ] dragging locked elements is disabled
[ ] selectAll ignores locked elements
[ ] opening contextmenu on selected element that's covered by a locked element prefers the selected element
[ ] opening contextmenu on a locked element prefers the locked element even if there's an unlocked element below it
[ ] selecting a group containing locked element(s) selects all including the locked elements
[ ] locked text element is not considered in any of the cases around text-bindable containers (creating/editing bound text)

@tom-sherman alright, once we address the two comments above we can merge! 🚀

@tom-sherman alright, once we address the two comments above we can merge! 🚀

Ok, I'm removing them for now and let's merge.

@tom-sherman alright, once we address the two comments above we can merge! 🚀

Ok, I'm removing that code for now and let's merge.

@dwelle sorry I didn't get around to this in time, great news! 🚀


Nest 7.6 -> GetManyAsync methos -> throw UnexpectedElasticsearchClientException

Using latest version 7.6 we have few problems on tests that use GetManyAsync call.
For example:
var response = await this.Context.Client.GetManyAsync<TEntity>(ids, this.IndexName);
Just generate exception:
 Elasticsearch.Net.UnexpectedElasticsearchClientException : Index name is null for the given type and no default index is set. Map an index name using ConnectionSettings.DefaultMappingFor<TDocument>() or set a default index using ConnectionSettings.DefaultIndex().
    ---- System.ArgumentException : Index name is null for the given type and no default index is set. Map an index name using ConnectionSettings.DefaultMappingFor<TDocument>() or set a default index using ConnectionSettings.DefaultIndex().
  Stack Trace:
    Transport`1.RequestAsync[TResponse](HttpMethod method, String path, CancellationToken cancellationToken, PostData data, IRequestParameters requestParameters) line 149
    GetManyExtensions.GetManyAsync[T](IElasticClient client, IEnumerable`1 ids, IndexName index, CancellationToken cancellationToken) line 68

Actually I could give you a more precise reproduction of the problem but not in a short time.
Tell me if necessary.
Ps: i reverted version to 7.5.1 and tests pass again.

Can reproduce this as well, will get a fix up shortly

@meriturva this should be fixed as per #4463
Are you able to give the following canary build a try?
NEST.7.6.0-ci20200226T122106
From this nuget feed:
https://ci.appveyor.com/nuget/elasticsearch-net
Thanks a ton for reporting this!

Thanks @Md right now I'm not able to change CI pipeline to include new feed source and really no time to test it locally (big project here).
If it is really necessary I will try tomorrow!

Not necessary :), was just curious if you could give it a quick spin.
We'll release new versions soon to nuget.org

I'm encountering the same bug. I'm glad it has already been corrected. When is a bugfix version planned to work? It prevents me to update to the latest, sweetest version for now.

This fix will be going into 7.6.1 and 6.8.5

Hello @codebrain & @Mpdreamz , I've tried to update to 7.6.1 but it does not fix the issue for me.
Here is the code that I do to reproduce it:
var esResponse = await elasticClient.MultiGetAsync(m => m.Index(_fullIndexName).GetMany<EsSdMetadataProfile>(fqns));
Do you need somethings else? Here is the exception I have:
System.ArgumentException: 'Index name is null for the given type and no default index is set. Map an index name using ConnectionSettings.DefaultMappingFor<TDocument>() or set a default index using ConnectionSettings.DefaultIndex().'
Here is the callstack

On my side it is fixed with 7.6.1 using: Client.GetManyAsync<TEntity>(ids, this.IndexName);

I could try to do that. So what would you recommend @codebrain  & @Mpdreamz  what's the best way to multi get documents with a specify index name?
MultiGet with a get many inside (like I this in my example), or calling directly the GetManyAsync at the root level?

@TheFireCookie thanks for raising this can confirm the fix does not apply to MultiGet and the workaround @meriturva listed should work in 7.6.1 (thanks @meriturva 👍 )
We'll work on fixing this ASAP

Coming back to this I don't think this is a bug albeit a very very subtle nuance:
var esResponse = await elasticClient.MultiGetAsync(m => m.Index(_fullIndexName).GetMany<EsSdMetadataProfile>(fqns));

Means do an _mget on /{_fullIndexName}/_mget and give me all the EsSdMetadataProfile objects where each get operation will be seeded with IndexName<EsSdMetadataProfile>(). However unless you configure EsSdMetadataProfile default index we have no way of knowing whether that is the default object from the index.
var esResponse = await elasticClient.MultiGetAsync(m => m
    .Index(_fullIndexName)
    .GetMany<EsSdMetadataProfile>(fqns)
    .GetMany<OtherObject>(fqns)
);

Is equally valid where we don't know if both objects are intended to live in _fullIndexName or one of them is. The index in the url of the API only serves as a default e.g if you do an /blah/_mget individual gets within the body can still do gets outside of blah.
The fix is as the exception describes, configure a default index name on connection settings for the type or be explicit:
var esResponse = await elasticClient.MultiGetAsync(m => m
    .Index(_fullIndexName)
    .GetMany<EsSdMetadataProfile>(fqns, (g, id) => g.Index(_fullIndexName))
    .GetMany<OtherObject>(fqns, (g, id) => g.Index("someotherindex"))
);

Which is exactly what the helper client.GetMany() does for you.

Hello,
Thank you for your fast analysis.
The weird thing is that this exact code is working in NEST 7.5.1.
But I can change my code if it seems like the better approach to use GetManyAsync instead of multiget :) What do you think?
Matthias.

I think that's the best course of action. With 8.0 we will very likely remove this special routine to try and clean up index on the get operations which will cause the same behaviour.

Hi there. I'm still seeing this bug in version 6.8.9. I also tried 6.8.5. Rolling back to 6.8.3 works for me, but I wanted to let you know since it seems like the fix didn't get rolled out to version 6 clients.


Survey - Number and type of flowers in patch

Please BRING THIS PAGE BEFORE THE TARGET FLOWER COVER PAGE
Edit top title text to say “What are the type and number of flowers in your patch?
Put the number slider at the bottom, bring the 4 types up the screen.
Type – can this be pre-populated IF the selected flower is from the target flower list to ensure consistency? See list below.
Flower number – can we leave the slider with a max up to 200 BUT cap the free text entry at 5000? (about 5% of counts so far are over 200)
Please add the following text behind the i info tab at the top: [is this too much? note to edit IF flower TYPE cannot be pre-populated by default]
"The number of flowers in a patch can strongly relate to the number of insect visitors recorded, so it is important to provide this information! Only count flowers that are reasonably fresh and likely to attract insects – ‘dead-head’ flowers and seedheads should not be counted. Flowers need to be counted in different ways depending on their structure. If you have chosen a target flower from our list, the flower type is shown by default. If you have chosen “Other” target flower, please count:
individual flowers - each flower counts as one unit
flower heads (where there are lots of tiny flowers within a larger flower head, e.g. dandelion or daisy) – each flower head counts as one unit
umbels (for flowers that have small flowers grouped into ‘umbels’, like inside-out umbrellas, e.g. hogweed) – each umbel counts as one unit
spikes (where a number of small flowers are arranged along a stem, e.g. lavender) – each spike counts as one unit "
Main flowering time | Target flower name | Flower   type
Apr   to Sep | Buttercup   – Ranunculus species | individual   flowers
Apr   to Sep | Dandelion   - Taraxacum officinale | flower   head
Apr   to Jun | Hawthorn   – Crataegus | individual   flowers
Apr   to Sep | White   Dead-nettle - Lamium album | flower   spike
May   or Jun to Sep | Bramble   (Blackberry) - Rubus fruticosus | individual   flowers
Jun   to Aug | Lavender   (English) - Lavandula angustifolia | flower   spike
Jun   to Sep | Hogweed   - Heracleum sphondylium | umbel
Jun   to Sep | Knapweed   (Common or Greater) - Centarea nigra   or scabiosa | flower   head
Jun   to Sep | Ragwort   - Senecio jacobaea and relatives | flower   head
Jun   to Sep | White   Clover - Trifolium repens | flower   head
Jul   to Sep | Buddleja | flower   spike
Jul   to Sep | Heather   - Calluna vulgaris or Erica species | flower   spike
Jul   to Sep | Thistle   - Cirsium or Carduus | flower   head
Sep | Ivy   - Hedera helix | flower   head

Flower number – can we leave the slider with a max up to 200 BUT cap the free text entry at 5000? (about 5% of counts so far are over 200)

The slider component is tightly coupled to the manual entry and +/- buttons at the moment and it works logarithmically for large numbers - allowing for precise sliding initially but then makes bigger increases the more you slide. Most of the times the user wouldn't be counting over 1000 flowers manually but estimating.
We can customise the component if this isn't good enough but I wonder if there is an easier way here by using a max number that is somewhere in the middle? Maybe up to 500 or 1000 instead?

The problem is that in previous years some FIT Counts have reported up to 5,000 individual flowers. In some cases this is likely to be a result of users misinterpreting what they are being asked to count, but there do seem to be genuine counts up to around 2,500 at least.
If we cap below that amount, what will users do if they do encounter a situation that genuinely has a larger number? I guess they would either abandon the survey or provide an erroneously low count, neither of which are good options.
A cap of 3,000 would likely be okay for all but the most exceptional of circumstances.

I see, I can make it 5000 if you are expecting numbers that hight.

I'm inclined to go for 3000 I think.


\footcite command implementation needed

How much time till the \footcite implementation? I need it so bad for my thesis. Thanks for all the hard work!

You can directly use \cite with a note style which actually creates a footnote. CSL's \cite is more like biblatex's \autocite. It chooses whether to use \footnote or not depending on the class (=note/in-text) attribute of the <style>.
BTW, \footcite is already added as an alias of \cite, though it might not be documented yet.

Yeah, FWIW, from the beginning, CSL was designed to be agnostic on output style, and so have the notion of automatic footnoting of relevant citations. It's similar to the biblatex autocite commands in that respect.

I've tried using a footnote style with this and it still showed the citations inline. Am I missing something?

I've tried using a footnote style with this and it still showed the citations inline. Am I missing something?

Which version of the package are you using? Can you provide a minimal example as in the bug report issue template?


How to solve the problem that could not install in windows 10 verison 1709 professional ？instead of update System verison

How to solve the problem that could not install in windows 10 verison 1709 professional ？

Please read README: https://github.com/microsoft/Terminal#prerequisites

You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal

Windows Terminal base Xaml Islands and Not support 1709

There is no fix for this as the readme clearly states what build you need.


[FR]

Now I want to develop more to Container manager System from this source code it ok?

ok , no problem

Thank so much
Vào Th 5, 7 thg 7, 2022 vào lúc 13:47 GreaterWMS @.***>
đã viết:

ok , no problem
—
Reply to this email directly, view it on GitHub
https://github.com/GreaterWMS/GreaterWMS/issues/218#issuecomment-1177159153,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANVBW3TI7VSW3CGR7CQFWRDVSZ4QJANCNFSM5236V62A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Don't worry about Commercial License. You will get Free Commercial License while you download the source code .

Thank so much

I saw the database in Python no a relationship in it? so how tables connect with each other?

Django ORM, You can change to other database

Thank you


Multiple Texture

Multiple texture change with the direction of the block is placed.Just like ic2 machines.

http://www.hakugyokurou.net/wordpress/?page_id=126

?

...

I don't understand ， what should i do?

好吧……先看教程?

😂 然而教程并没有关于多面材质的

我的密码重置了⁽⁽◝( ˙ ꒳ ˙ )◜⁾⁾

I think I found a way to solve the problem of the Multiple Texture, but i need time.

@BestOwl @Java0 Is there still anything wrong?

Fixed


⚠ Roblox has degraded performance

In d6e5926, Roblox (https://www.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 784 ms

Resolved: Roblox performance has improved in 992f013.


Updated cron expression to 1 hour for auto deployment

Why are we doing it every hour?

Why are we doing it every hour?

Because of [ARC-1462]. It's just a temporary solution.

The issue is pipeline took around 40 mins to deploy to prod and lambda again runs in that timeframe and triggers the pipeline again.  Need to update the lambda to add check for triggering pipeline only if no pipeline is running for prod deployment.
Created ticket for this issue and  will work on it next week.


Install elemental-operator from Rancher Markeplace chart

Fixes #139

Use v-clean-html instead of v-html
Bump shell version used to 0.3.27
Breakdown of pkg/elemental/pages/index.vue main view into components such as DashboardView and InstallView
Create InstallView which enables user to install Elemental Operator from Rancher Marketplace

To test:

You will need to have Rancher backend version 2.8.0 (2.8-head, 2.8.0-rc3, etc)
Make sure you don't have already installed elemental operator
Run this branch and go to elemental extension and follow the steps

Preview:
https://github.com/rancher/elemental-ui/assets/97888974/6b8781de-80ea-4b92-8d82-14994869ea8c

FYI @fgiudici @juadk @davidcassany
@juadk this will change the e2e tests. Added a preview for you guys to check how it will now work.

Looks good but one remark because I'm working on this, is it possible to deploy the dev operator version if I use the dev ui?
I mean, I can easily test installing stable operator but the purpose of the CI is to test the latest dev operator.
Without speaking about the UI extension, I'm trying to host the dev operator locally to expose it and be able to add a custom repository in the Rancher apps.

Looks good but one remark because I'm working on this, is it possible to deploy the dev operator version if I use the dev ui? I mean, I can easily test installing stable operator but the purpose of the CI is to test the latest dev operator. Without speaking about the UI extension, I'm trying to host the dev operator locally to expose it and be able to add a custom repository in the Rancher apps.

I'll have to do a bit of digging to see what's the best way to achieve it, but I think it's doable @juadk .
Question:

Do you test a built version of the elemental-ui or do you "run" the project locally when doing the e2e tests @juadk ?

@jordojordo one final review, please 🙏  I really want a double-check here, as I've seen a bit of weirdness in my system (which disappeared after I uninstalled and re-installed again both the elemental-ui and operator). Thanks


Lets describe the project

The idea here is that Diaspora for Venezulano's data is needed to help make better decisions about where refugees are going and where they are. Goal is to find ways to collect and visualize the data.
Can we get confirmation on this description :up:

Some break down ideas

[ ] we could use a google sheet to start collecting the data
[ ] would be great to have a way to consume data from a google sheet to transfer into a mysql db or big query so we can visualize the data
[ ] we need a google form to start capturing the data
[ ] idea for using an sms bot for asking Venezolanos for the data, could we do the same with slack or whatsapp?

we have a challenge description here too https://github.com/wenlock/vinotinto-project/blob/master/README.md

We need to add that we are providing a way to match through geolocation available "social services" with migrants, with the individuals that register in our app according to the updated challenge description here https://docs.google.com/document/d/1ZWRcEFOENBHolVRuOpjI8Co_g3BGgUGA9v3m-dK4cGA/edit?usp=sharing
Basically to report and match according to location demand and supply of social services for the Venezuelan diaspora

We're on our way with starting to create an application, it seems to have two components.  Data capture and user interaction. Reposting here from slack
Sub team work items

:checkered_flag: Team 1: is working on forms and how we collect information from our Personas, atm there are immigrants and services.
:checkered_flag: Team 2: Is testing geo location api’s to identify cities so we can perform a bridge lookup with interactions and services, we also are working on how we get data from google sheet for longer term storage
:checkered_flag: Team 3: Is working on an interactive facebook app that will allow us to collect and ask additional question


Create Jasmin.j

Hello world in Jasmin, the JVM assembler.

There are other updates to push first...

Changes made, reopening


Clean up the filesystem stuff and add support for HF ckpt downloading

This works fine for SD2.1 but I've noticed an issue downloading the safetensors file for clip for SD1.5. There's still some more cleanup necessary here, so I'd appreciate a second pair of eyes on it. I'm also not sure if the way I'm centralizing all the filesystem logic (just using the args and calling os.path.join at each usage) is the right thing to do or if we want to have everything go through, say, functions in file_utils.py.

Thanks @gpetters-amd. I left a few comments, but looks better for the most part.


.htpasswd plugin

I prefer protecting my dev area with oldschool htaccess/htpasswd files.
I therefore created a plugin: https://github.com/joernschellhaas/codiad/tree/master/Auth-Basic
It syncs the contents of a .htpasswd file with the codiad user accounts.
However I was not able to always adhere to best coding practice, so it would be nice if someone could review my code.
It would also be possible to take parts of this code an create a plugin which can generate arbitrary htpasswd files and is not synced to the codiad user db.

Interesting idea of an plugin. I would really appreciate if you can add a readme and create a seperate repository for it. Something like "Codiad-Auth-Basic"

Here you are: https://github.com/joernschellhaas/Codiad-Auth-Basic


Unexpected Property PWSH

When i specify that an Azure PowerShell task should use PowerShell Core, it is flagged in vsCode as a warning.  Pasting the below test yaml shows the warning "Unexpected property pwsh"
trigger: none
stages:

stage: Deployment
jobs:

job: deploy
timeoutInMinutes: 240
pool: 'windows-latest'
steps:

task: AzurePowerShell@4
inputs:
azureSubscription: 'AzureSponsorship'
ScriptType: 'FilePath'
ScriptPath: '.\test.ps1'
azurePowerShellVersion: 'LatestVersion'
pwsh: true

##########################
Version: 1.41.0-insider (system setup)
Commit: 87c2e0be5d7359ce110c4c9ec9f6df71be996f8a
Date: 2019-12-06T21:36:11.793Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363
Azure Pipelines extension version: 1.157.4

see PR 288

I see this is in the schema now: https://github.com/microsoft/azure-pipelines-vscode/blob/f7d0079da837b27c88bdf24059b7722efd0513b1/service-schema.json#L6002
Please leave a comment with the extension version you're using if it's still appearing as an unknown property :).

I see this is in the schema now: https://github.com/microsoft/azure-pipelines-vscode/blob/f7d0079da837b27c88bdf24059b7722efd0513b1/service-schema.json#L6002
Please leave a comment with the extension version you're using if it's still appearing as an unknown property :).


feat: wrapper option

Add a simple wrapper option to encapsulate the template in a div.
I find it useful to manage dynamic modal based on routes (like my own use case), and not have to manage a third part element with appendElement option.
I'm open to discussions (since it's my first contact with you 🤗)

Looks good! Seems like a useful option. It would be good to include a couple of tests, maybe one to assert that when wrapper is true, the element is wrapped, and another to test that if wrapperClass is provided, it is set on the element, WDYT?

Yeah that's a great idea, I've made a quick fix for my own purposes. And, finally, I have  rewrite the whole service to integrate the component feature. It's still in progress work (you can check it here : https://github.com/HollyPony/angular-modal-service) .
I'll look for unit test and a document.createElement approach.