docs: document ddp_find_unused_parameters_true in lightning fabric

What does this PR do?
Add document for ddp_find_unused_parameters_true in lightning Fabric.

Fixes #19548

Before submitting

Was this discussed/agreed via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
Did you list all the breaking changes introduced by this pull request?
Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--19564.org.readthedocs.build/en/19564/

Seems the PyTorch doc fail is not caused by this PR?

Thanks @leng-yue!


Vectorized load/store is unsound when indices are not contiguous

torch.flip() was returning incorrect results, so I investigated. Here's a stripped-down version of the generated code for flipping a 1-D tensor of two elements:
import triton
import triton.language as tl
import torch

torch.manual_seed(0)

@triton.jit
def triton_poi_fused_flip_0(in_ptr0, out_ptr0):
    x0 = tl.arange(0, 2)
    tmp0 = tl.load(in_ptr0 + (1 - x0))
    tl.store(out_ptr0 + x0, tmp0)

x = torch.randn([2], device='cpu')
y = torch.empty_like(x)
triton_poi_fused_flip_0[(1, )](x, y)
print(x)
print(y)

flip basically uses pointer arithmetic to swap elements around. For a 1D vector of size 2, flip essentially loads (and then stores) a tensor with values [in_ptr[1], in_ptr[0]]. However, our load/store lowering assumes that the pointers are always contiguous and monotonically increasing, thus leading to incorrect results.

Thanks for reporting this! I'll have a look. I suspect AxisInfo might make no difference between monotonically increasing and decreasing sequences and report contiguous access in both cases. Or we might misuse the info.

I could reproduce the problem on CUDA. Proposed fix: https://github.com/triton-lang/triton/pull/4871

@int3 The fix is in upstream Triton. Do we need to merge it into our repo as well, or fix through the next rebase is good enough?

Thanks for the fix!
I am having PyTorch pull from our origin/legacy branch since it doesn't work with the tip of the upstream Triton repo, so I'll just cherry-pick your fix into that branch too. The main branch can just pick up the fix in the next rebase.


tool tips

This example doesn't quite do what i want.  http://jsfiddle.net/6n5r6vyb/13/
It looks like because of the first parameter to addSeries, the chart is rendering each data point as a separate series.  What i want to do is draw a line series, but have the additional info appear in the tool tip only (i.e. not used for grouping or categorization, but simply additional info).
Any help would be appreciated.

Unfortunately you can't add extra details to a line chart tooltip in that way because (as you rightly concluded) it causes the line to be split by each value.  The best approach instead is to use a custom tooltip to pick the values from the data for the relevant point.  Here's an updated fiddle:
http://jsfiddle.net/6n5r6vyb/14/

That works! Thank you!


Basic machine learning - v0.0.2

This will allow JARVIS to learn new commands and compare those commands to given current commands

BiologicalMath, how is this coming along?

This was too broad.


go.etcd.io/etcd migration?

https://github.com/micro/go-micro/blob/45ee5e9ad18bb993cb6ff7963744e908f4a50e15/registry/etcd/etcd.go#L16
I'm bumping into issues like
https://github.com/etcd-io/bbolt/issues/211
Is it possible that the import lines should all be replaced from github.com/coreos/etcd to go.etcd.io/etcd ...? since it seams that there is some import conflicts with those projects

This is my proposed solution basically.
cd ~/go/src/github.com/micro/go-micro
find -name *.go -exec perl -p -i -e 's@github.com/coreos/etcd@go.etcd.io/etcd@g' {} \;
go mod tidy

We're using go modules so this shouldn't really be an issue. The reason we can't move is because the etcd concurrency package still references the old path.

Are you sure of this ....?
My very small example is the following https://github.com/nicocesar/tokenplay
please make sure that you start from scratch (as in rm ~/go/{src,pkg} ) and you use go 1.14 with modules on
$ go version
go version go1.14.1 linux/amd64
$ env | grep GO
GO111MODULE=on

this gave me the following result:
$ make build
protoc --proto_path=/home/nico/go/src:. --micro_out=. --go_out=. proto/tokenplay/tokenplay.proto
/home/nico/go/src: warning: directory does not exist.
go build -o tokenplay-srv *.go
# github.com/coreos/etcd/clientv3/balancer/picker
../../go/pkg/mod/github.com/coreos/etcd@v3.3.18+incompatible/clientv3/balancer/picker/err.go:37:44: undefined: balancer.PickOptions
../../go/pkg/mod/github.com/coreos/etcd@v3.3.18+incompatible/clientv3/balancer/picker/roundrobin_balanced.go:55:54: undefined: balancer.PickOptions
# github.com/coreos/etcd/clientv3/balancer/resolver/endpoint
../../go/pkg/mod/github.com/coreos/etcd@v3.3.18+incompatible/clientv3/balancer/resolver/endpoint/endpoint.go:114:78: undefined: resolver.BuildOption
../../go/pkg/mod/github.com/coreos/etcd@v3.3.18+incompatible/clientv3/balancer/resolver/endpoint/endpoint.go:182:31: undefined: resolver.ResolveNowOption
make: *** [Makefile:12: build] Error 2

because they not released fixed version
after redhat acquire coreos etcd continually breaks things

The simplest thing you can do

Check out go-micro
Run your command
Run go test -v ./...

If it compiles and tests pass submit a PR

For the record: commit 8282e781e46062c98c9cf8feaf1c015d4259d026, test wont pass with my proposed change. (as @asim pointed out.)
I'm closing this ticket because it seems that is a bigger problem in the ecosystem, and not a simple search and replace quick fix.
Thanks for the time taken to explain me this.


Explorer information is updated too slow

Something makes Explorer info load slow: explorer eval, gambits, show opening or a combination of the above. This should work just as fast as Lichess native and if anything to refresh, do it async in the background.
Also, the show opening in Explorer changing the height of the header gets old really fast. Find a solution.

hackish fix in v2.3.133


Detect rate limiting, no network and errors on API calls

Currently we are logging out user when there is a problem with request :sob:

Related #69


Black screen for minutes and very slow boot/logon

Edit.. oh well.. ofc i only changed the file path to the script.. not the "Start in (optional)".
My VM does not have a D: drive so it couldnt find the folder..
everything works as expected..
i feel so stupid right now.. -.- xD

@backamblock Hey, lets see if we can solve but I'm pretty sure we can. I would recommend to execute the script manually first and then report back. You can also should enable the debug parameter in the script file and check what the output is. However if the preparing screen is what I have in mind I'm pretty sure it doesn't relate to the script. Ping has to be supported by your machine Bootnas or you have to disable the ping support of the script. Otherwise you won't get the desired results. Because typically it won't be executed at that stage on bootup. If you used the default scheduler task file
    <LogonTrigger>
      <Enabled>true</Enabled>
      <Delay>PT15S</Delay>
    </LogonTrigger>

The execution trigger is delayed by 15 seconds. So it won't even be triggered until you are seeing desktop except you have a terrible slow machine.
Your configuration looks fine, as far as I see. It also points to \\<IP_ADDRESS>\Botnas which you indicated in the comment below the config. However I have to say that I never tried the script on LTSB 2016 but it should basically work. But let's see try what I have written and report back.

So my comment was useless because I already wrote it :D nevermind! I'm glad that it works and you got it working.

Wow, that is a quick answer :D
Sorry for the time haha

Wow, that is a quick answer :D
Sorry for the time haha

I saw it right in the moment you posted it in my mail because I'm getting rid of email backlog :P.

Edit.. oh well.. ofc i only changed the file path to the script.. not the "Start in (optional)".
My VM does not have a D: drive so it couldnt find the folder..
everything works as expected..
i feel so stupid right now.. -.- xD

Don't be too harsh because things like that can always happen nothing to worry about :P

Wow, that is a quick answer :D
Sorry for the time haha

I saw it right in the moment you posted it in my mail because I'm getting rid of email backlog :P.

Edit.. oh well.. ofc i only changed the file path to the script.. not the "Start in (optional)".
My VM does not have a D: drive so it couldnt find the folder..
everything works as expected..
i feel so stupid right now.. -.- xD

Don't be too harsh because things like that can always happen nothing to worry about :P

@backamblock

Wow, that is a quick answer :D
Sorry for the time haha

I saw it right in the moment you posted it in my mail because I'm getting rid of email backlog :P.

Edit.. oh well.. ofc i only changed the file path to the script.. not the "Start in (optional)".


API to select range of dates

Is there an API to enable the user to select a range (start and end date)? Have read the docs and browsed the source code, just wondering if I am missing anything.

Unfortunately not @gbih at this time.


Remove the AST structures

These are difficult to maintain as an external API because of the array parameter mapping and they are basically just JSON generators that can be moved into the parser without much loss in fidelity or API functionality.
Filing issue to see if community has any input prior to making these changes.
/cc @mmun

As an example, most use of the AST methods would be converted to follow patterns like this:
 content
-  : CONTENT -> new yy.ContentStatement($1, yy.locInfo(@$))
-  ;
+  : CONTENT {
+    $$ = {
+      type: 'ContentStatement',
+      original: $1,
+      value: $1,
+      loc: yy.locInfo(@$)
+    };
+  };

This would be nice.


Changefeed implementation

Packages impacted by this PR
@azure/cosmos
Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/18062
Describe the problem that is addressed by this PR
This PR implements changefeed pull model in JS SDK.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
This PR implements changefeed as an infinite feed which keeps on checking if there are any new changes
Changefeed pull model has 3 types.

Changefeed for Entire Container.
Changefeed for an Epk Range.
Changefeed for a partition key.

Based on the options passed in changefeedIteratorOptions, one of these is selected.
Eg. {startFromNow: boolean, epkRange: someEpkRange } -> Changefeed for an epk range.
Eg. {startFromNow: boolean,  partitionKey: somePartitionKey} -> Changefeed for a partition key.
If none of epkRange and partitionKey is specified, changefeed is fetched for entire container.
Four type of start points:

continuationToken(string) : starts fetching changes from the provided continuation token.
startFromBeginning(boolean) : starts fetching changes allthe changes from time of creation of container.
startFromNow(boolean) : start fetching any new changes that will happen from the current timestamp
startTime(Date) : starts fetching any changes from a custom time stamp.

Only one of the above can be true/specified at a time.
Eg. ChangefeedIteratorOptions:
{ startFromNow: true/false, maxItemCount: number, epkRange: PartitionKeyRange ... }
Changefeed for entire container and Epk ranges implements a queue consisting of all the feed ranges overlapping and keeps checking for new changes for each feed range.
Once we reach the feed range for which last positive was fetched, and there are no new changes present, 304 is returned to the user and whole process starts again.
Continuation Token format for example:
{"rid":"containerRid","Continuation":[{"minInclusive":"","maxExclusive":"05C1E7FFFFFFFE","continuationToken":" value of continuation token for this feed range"},{"minInclusive":"05C1E7FFFFFFFE","maxExclusive":"FF","continuationToken":" value of continuation token for this feed range"}]}
Continuation Token for a partition Key:
{"rid":"containerRid", "partitionKey": "somePartitionKey", Continuation: "some continuation value string" }
Custom Epk ranges are also supported i.e. minInclusive and maxExclusive need not to overlap exactly with epk range of a physical partition.
More detailed comments are present in the code.
Are there test cases added in this PR? (If not, why?)
Still working on it.
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-cosmos


Adding issue management workflows

We can now add the below labels to issues
And the workflow will automatically add the required text that will be instructions to the issue submitter.

needs-sample
question
help-wanted

These labels should be added to the repository
And we can perhaps get rid of the other labels
that intend to convey the same thing.
More details available at: https://github.com/peaceiris/actions-label-commenter

Summary by CodeRabbit

New Features

Introduced a Label Commenter tool to automatically add specific comments to issues based on their labels, enhancing communication on issues labeled as needing more information, questions, and help-wanted.

Good idea 👍

I saw this being used in selenium ( I commit there as well) and found it to be useful. So decided to borrow it from there 😁


FATAL EXCEPTION: main java.lang.NoClassDefFoundError: android.support.v7.internal.widget.TintManager

Because of dynamic dependency:
com.android.support:appcompat-v7:23.+

i have been release v1.2.0 by re-implement the animation, please have a try
dependencies {
    implementation 'pub.hanks:smallbang-library:1.2.0'
}


Is the "remoteContracts" config option working?

I've been trying to use hardhat-gas-reporter for contracts already deployed on rinkeby, which I pull in through the forking method. The forking works but the gas reporter doesn't print the imported contracts.
I found out that you're supposed to be able to get this to work using  the remoteContracts config as mentioned here: https://github.com/cgewecke/hardhat-gas-reporter/issues/46 But I am not sure if it's actually working. The issue sounds like it's all resolved but it never works for me, and when I looked into the code, the remoteContracts array is ignored when it's passed to eth-gas-reporter at https://github.com/cgewecke/hardhat-gas-reporter/blob/master/src/index.ts#L186 - You can see that the InternalReporterConfig initialization code at https://github.com/cgewecke/eth-gas-reporter/blob/master/lib/config.js#L6 does not include the remoteContracts attribute, and therefore the remoteContracts is always undefined after initializing, even though the options object did have the remoteContracts attribute defined.
Am i missing something? I can't find anyone complaining about this so I am thinking maybe I'm doing something wrong, but at the same time the code doesn't look like it's supposed to work. Would appreciate any pointers.
By the way I can get it to work if I manually go into node_modules/eth-gas-reporter/lib/config.js at https://github.com/cgewecke/eth-gas-reporter/blob/master/lib/config.js#L7 and add a line: this.remoteContracts = options.remoteContracts, it works, which proves my theory above. But maybe I am looking at this completely wrong, any clue? Would like to be able to use this without these monkey patching.
cc: @cgewecke

@skogard Thanks for opening. Do you have a repo & branch where I could reproduce this / investigate?

Thanks for the workaround @skogard. I too could not get remoteContracts to work against a mainnet fork out of the box.
Adding this.remoteContracts = options.remoteContracts; to the Config constructor in node_modules/eth-gas-reporter/lib/config.js did the trick.
FYI, here's the remoteContracts I'm using
remoteContracts: [
    {
        abi: ICurve3Pool__factory.abi,
        address: "0xbEbc44782C7dB0a1A60Cb6fe97d0b483032FF1C7",
        name: "Curve3Pool",
    },
],

i also ran into this. @naddison36 's fixup worked. it seems that the internal reporter config is not quite up to date
options = new InternalReporterConfig(options);
options are overridden and remoteContracts does not come along for the ride
i also see the following printed out:
Warning: failed to fetch bytecode for remote contract: ContractName
Error was: TypeError: sha1 is not a function

Also what about remote contracts that are deployed during the test, so they do not have an address to be specified in remoteContracts in hardhat.config?


Install Node-sass isn't working anymore in a fresh new project

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.
4.4.2

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
did a fresh ng new then did npm install node-sass --save-dev and i got an error and sass isn't added.

The log given by the failure. Normally this include a stack trace and some
more information.
13422 verbose stack Error: The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\lib\install.js:125:32
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\lib\install.js:268:7
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-installed\read-installed.js:142:5
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-installed\read-installed.js:263:14
13422 verbose stack     at cb (C:\Program Files\nodejs\node_modules\npm\node_modules\slide\lib\async-map.js:47:24)
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-installed\read-installed.js:263:14
13422 verbose stack     at cb (C:\Program Files\nodejs\node_modules\npm\node_modules\slide\lib\async-map.js:47:24)
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-installed\read-installed.js:263:14
13422 verbose stack     at cb (C:\Program Files\nodejs\node_modules\npm\node_modules\slide\lib\async-map.js:47:24)
13422 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-installed\read-installed.js:263:14
13423 verbose cwd C:\Repos\test
13424 error Windows_NT 10.0.10586
13425 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "node-sass" "--save-dev"
13426 error node v4.4.5
13427 error npm  v2.15.5
13428 error code EPEERINVALID
13429 error peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
13429 error peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>13429 error peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>13429 error peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>13429 error peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>13430 verbose exit [ 1, true ]

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

So then I installed Node 6.2.2 and the install was going good, but when i change a .css file to .scss it doenst generate an .css file at the same location.
I've runned ng serve.

If I may add my findings. With the default npm install -g angular-cli (version <IP_ADDRESS>-beta.6) adding scss compilation works as described in README.md.  After removing angular-cli as described in upgrade and then installing the latest npm install -g angular-cli@latest (version 1.0.0-beta.9) and creating a new project followed by npm install node-sass scss compilation does not work. Oddly, after doing a build with the --watch flag, the console seems to indicate it is working??
file changed app\app.component.scss
Build successful - 3859ms.
however there is no output.
Windows 10
Node 5.4
npm 3.8
angular2 2.0.0-rc.4
mterial2 2.0.0-alpha.6

I am having issues where nested scss is not compiling
.sidebar {
	height: calc(100vh - 180px);
	margin-top: 30px;
	padding-right: 10px;
	font-size: 20px;
	border-right: solid 1px #ccc;
	#smList {
		position: absolute;
		bottom:150px;
	}
}

This does not work. I have to break smList out of sidebar to get it to work.

Guys, this does work for me. Try updating node-sass (that's what I've done). Also, @relevantmedia, your example works in my case.

I can verify this bug too, ng build no longer writes out .scss files into the dist/app directory.


Unable to compile after all libraries are installed.

In file included from C:\Users\win7\Desktop\EE\WS2812LED\McLighting-master\Arduino\McLighting\McLighting.ino:97:0:
sketch\request_handlers.h: In function 'char* listStatusJSON()':
sketch\request_handlers.h:84:8: warning: address of local variable 'json' returned [-Wreturn-local-addr]
char json[255];
    ^

C:\Users\win7\Documents\Arduino\libraries\WebSockets\src\WebSocketsClient.cpp: In member function 'void WebSocketsClient::begin(const char*, uint16_t, const char*, const char*)':
C:\Users\win7\Documents\Arduino\libraries\WebSockets\src\WebSocketsClient.cpp:69:16: error: 'RANDOM_REG32' was not declared in this scope
 randomSeed(RANDOM_REG32);

            ^

What does it mean? How can I solve it?
Is "RANDOM" function not available?
Please help. Thank you.

Hi @Fireflaker,
these error messages seem to be related with older versions of the Arduino core: https://goo.gl/Ktw1QY. What version do you use? Is there a update available in the board manager?
Regards
Tobias

Thank you so much. Problem solved.

You're welcome


How to find what icons I can use?

I keep trying things like:
fas-fa-dog
fas-fa-wrench
and any variation of those (like fal-fa-wrench)
But, I keep getting the following error:
Svg by name "fa-wrench" from set "fontawesome-solid" not found.
How do I know what to use/put?

Nevermind, I think I found the problem, and I also see where the icons are. Thank you


Update mead docs for 2.0

2.0 changes a large number of things, and though the day-to-day use-cases havent changed much the underlying code has.  Some places where the documentation needs updating

using 8 mile as an API
adding a custom task_module
writing and publishing an addon to mead-hub
multi-worker training
custom fit_funcs

I think the docs are good enough for now.  I will add more documentation to the site after release (because of the new layout, this wont affect the launch page)


[bug] Python replacement indentation wrong in indented class

⏯ Playground Link

Playground link with relevant code
💻 Code

Code:
class A(object):
    # comment
    def replace(self, *args, **kwargs):
        print(selfa)

class C(object):
    ''' doc string '''
    def replace(self, *args, **kwargs):
        print(selfa)

if something:
    class B(A):
        """ class docstring """
        def replace(self, *args, **kwargs):
            """ sfgsfd self """
            print(self1)
else:
    class B(A):
        def replace(self, *args, **kwargs):
            """ sfgsfd self """
            print(self1)

Pattern:
id: batch-mode-pattern
message: Class "$CN" can be batch mode pattern
severity: info
# Add batch_mode=True as a class variable (after any docstrings)
rule:
  kind: class_definition
  pattern: |-
    class $CN($$$CBS):
      $$$CBS1
utils:
  is-docstring:
    kind: expression_statement
    has:
      kind: string
    not:
      has:
        nthChild: 2
    inside:
      kind: block
      inside:
        any:
          - kind: class_definition
          - kind: function_definition
    nthChild: 1
transform:
  CBS1R:
    rewrite:
      rewriters:
        - add_batch_mode_no_docstring
        - add_batch_mode_with_docstring
      source: $$$CBS1
rewriters:
  - id: add_batch_mode_no_docstring
    rule:
      pattern: $A
      inside:
        inside:
          kind: class_definition
      not:
        matches: is-docstring
      nthChild: 1
    fix: |-
      batch_mode = True
      $A
  - id: add_batch_mode_with_docstring
    rule:
      pattern: $A
      inside:
        inside:
          kind: class_definition
      matches: is-docstring
    fix: |-
        $A
        batch_mode = True
fix: |-
  class $CN($$$CBS):
      $CBS1R

🙁 Actual behavior

class A(object):
    # comment
    batch_mode = True
    def replace(self, *args, **kwargs):
        print(selfa)

class C(object):
    ''' doc string '''
    batch_mode = True
    def replace(self, *args, **kwargs):
        print(selfa)

if something:
    class B(A):
        """ class docstring """
            batch_mode = True
            def replace(self, *args, **kwargs):
                """ sfgsfd self """
                print(self1)
else:
    class B(A):
        batch_mode = True
            def replace(self, *args, **kwargs):
                """ sfgsfd self """
                print(self1)

Indentation of 2nd and subsequent lines is incorrect in the indented classes within if something and else
🙂 Expected behavior

class A(object):
    # comment
    batch_mode = True
    def replace(self, *args, **kwargs):
        print(selfa)

class C(object):
    ''' doc string '''
    batch_mode = True
    def replace(self, *args, **kwargs):
        print(selfa)

if something:
    class B(A):
        """ class docstring """
        batch_mode = True
        def replace(self, *args, **kwargs):
            """ sfgsfd self """
            print(self1)
else:
    class B(A):
        batch_mode = True
        def replace(self, *args, **kwargs):
            """ sfgsfd self """
            print(self1)

sadly ast-grep does not support this use case.
the problem is that the meta variable captures $A captures like this
def test():
        pass # note this indentation is 8 instead of 4

The fix string
BATCH = True
$A

will preserve the 8 whitespace.

Check out this message thread from the ast-grep Discord for some additional info trying to work around indentation issues. @HerringtonDarkholme does this issue imply that ast-grep has a serious limitation when it comes to writing rules for Python?

@StevenLove I feel the problem may be caused by wrong indentation in rewrite. If the fix above is applied without using rewrite, that is, rewriting directly in the fix, the indentation works fine.
I will investigate more in this issue and hopefully it can be fixed. Meanwhile, the indentation issue can imply that rewriter may not work well with Python atm.

Minimal reproduction:
if something:
    class B(A):
        def replace(self, *args, **kwargs):
            print(self1)

id: batch-mode-pattern
language: python
rule:
  kind: class_definition
  pattern: |-
    class $CN($$$CBS):
      $A
fix: |-
  class $CN($$$CBS):
      test = 123
      $A

Here is a playground link that shows how adding a rewriter changes indentation even if the rewriter is doing nothing.

I have a even simpler reproduction:
id: demonstrate-transform-indentation
language: python
rule: { pattern: $A, kind: function_definition }
transform:
  AR: { substring: { source: $A } }
fix: $A

https://ast-grep.github.io/playground.html#eyJtb2RlIjoiQ29uZmlnIiwibGFuZyI6InB5dGhvbiIsInF1ZXJ5IjoiY2xhc3MgJCQkQ0JTOlxyXG4gICAgJycnJERTJycnXHJcbiAgICAkJCRDQlxyXG4iLCJyZXdyaXRlIjoiY2xhc3MgJCQkQ0JTOlxyXG4gICAgXCJcIlwiJERTXCJcIlwiXHJcbiAgICBiYXRjaF9tb2RlID0gVHJ1ZVxyXG4gICAgJCQkQ0IiLCJzdHJpY3RuZXNzIjoic21hcnQiLCJzZWxlY3RvciI6IkVSUk9SIiwiY29uZmlnIjoiaWQ6IGRlbW9uc3RyYXRlLXRyYW5zZm9ybS1pbmRlbnRhdGlvblxubGFuZ3VhZ2U6IHB5dGhvblxucnVsZTogeyBwYXR0ZXJuOiAkQSwga2luZDogZnVuY3Rpb25fZGVmaW5pdGlvbiB9XG50cmFuc2Zvcm06XG4gIEFSOiB7IHN1YnN0cmluZzogeyBzb3VyY2U6ICRBIH0gfVxuZml4OiAkQSIsInNvdXJjZSI6ImlmIHNvbWV0aGluZzpcbiAgY2xhc3MgQihBKTpcbiAgICBkZWYgcmVwbGFjZShzZWxmLCAqYXJncywgKiprd2FyZ3MpOlxuICAgICAgcHJpbnQoc2VsZjEpIn0=

fixed in 0.26.3

Does the ast-playground use the latest version? (Maybe it is a good idea to show the version number there somewhere).
The result for my original issue still isn't fully correct. The replace() functions have moved out of the class.


Bolt.new open in editor won't link to existing github integration

Describe the bug
When returning from the AI code edit, the project linkage displays a "create repository" option in the project section vs opening with the github project - meaning it isn't possible to push the generated code changes back to github.
Link to the blitz that caused the error
https://stackblitz.com/edit/sb1-azvuuj?file=index.html
https://stackblitz.com/~/github.com/ujcs/sb1-azvuuj
Note, there seems to be an open from github then shifts to linking to a local project from other spots.
Steps to reproduce

click edit with bolt.net
click open it stackblitz
no option to push to existing repository, only create new (and name already exists)

Expected behavior
Expect to bring up the existing project and option to push to repository.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
NA
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 90716412,
  "usedJSHeapSize": 88393964,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 34c588ed

Additional context
NA

Same for me


refactor(rust): strategy to enable/disable logs in ockam_command

Previously, we had the arguments verbose, quiet, spawned + the OCKAM_LOG env variable to
control how logs were enabled. The OCKAM_LOG was the highest priority parameter, making it
impossible to override with any of mentioned command arguments.
Also, the quiet argument was ignored.
Now, the spawned argument has been removed and the priority has been reversed. That is, if
quiet is set, logs are not enabled. If verbose is set, its value will be used to define
the log level; if not, it will try to read the log level from the OCKAM_LOG env variable.
Logs won't be enabled if both verbose and OCKAM_LOG are not set.
Some examples:
$ OCKAM_LOG=debug ockam node create -q # Logs not enabled because `quiet` is set
$ OCKAM_LOG=debug ockam node create -vvv # Logs enabled to INFO because of `verbose` preference
$ OCKAM_LOG=debug ockam node create # Logs enabled to DEBUG because of `OCKAM_LOG` value
$ ockam node create # Logs not enabled because neither `verbose` nor `OCKAM_LOG` are set

All comments reviewed @spacekookie, thanks for your feedback!


Add tls scheme to HTTP::Server#bind and rename HTTP::Server#bind_ssl

This adds tls:// scheme for HTTP::Server#bind and makes it default in documentation. It also renames HTTP::Server#bind_sslto HTTP::Server#bind_tls.
Follow-up on #6500 (discussion starting at https://github.com/crystal-lang/crystal/pull/6500#issuecomment-412087373)

Do we want to make such a minimal breaking change to an API just introduced?
Yes, I think its fair. People using it should still be actively working on their projects.

Yeah, it's too bad 0.26.0 is already done.
Maybe something breaks and we need to ship 0.26.1 right away, then this could be included in the bug fix ;)

Kemal already update it's api to use bind_ssl.
We should add bind_ssl for 0.26.x so we can ship master as it and remove bind_ssl in 0.27

You mean to temporarily re-add bind_ssl as alias for bind_tls?

Yes.


translate iceTransportPolicy to iceTransports

until https://code.google.com/p/webrtc/issues/detail?id=4869 is fixed I don't want to write code that works around the wrong name if I can just get it fixed in adapter.
The two things using this are the candidate gathering sample and apprtc (?it=relay)
The test is indirect. If the policy is set and we try to gather candidates without a TURN server, we will not get any candidates.
Firefox is not supported yet so the test passes. @jan-ivar I failed to find a bugzilla id for this?

the test failure is rather interesting. It seems that ICE gathering never completes on travis? Works for me locally...
boo... such a nice test! But I think we can go without it

https://bugzil.la/1187775

LGTM.
Filed #96 to investigate why the test fails.


feat: Allow fractional uakt for settlement

Stuff I changed

For escrow accounts, use a decimal coin
For bid pricing and deployment max price, use a decimal coin
Rework some of the settlement code, since with decimal types it isn't really as complex
Migrate all of our types to v1beta2
Keep the v1beta1 code for now, in a package called typesv1beta where appropriate
Make some of the logic around provider attribute types code use an interface instead, so they can run on any version
Add a migration that reads the binary values, parses them, and writes them back as v1beta2 version
In our examples, lower the proposal time down to 15 seconds so we can actually do proposals when testing

bump

refs #1174

Looking good. Sorry for the delay. Is there any chance that we can only upgrade the package versions for proto defs that need to be updated for this?
Note: we'll need to revive the mainnet/main branch and release from there before merging this.

If we stagger versions like that, how would we know what versions of what types to use?

If we stagger versions like that, how would we know what versions of what types to use?

import xv1beta1 "akash/proto/v1beta1"
import yv1beta2 "akash/proto/v1beta2"

Ok I will work on figuring out how to stagger the versions then

superseded by #1394


GoMod considers the entire graph of dependencies without checking if the code uses them

currently the logic relies on go mod graph to extract the dependency tree.
For example if you are using viper as a dependency ORT will report the crypt package as a dependency and an input for scan and download.
This is only true, if the code uses the remote provider in viper and not the local implementation. To avoid this issue, we could use go mod why <package> to verify whether a dependency from the graph is actually used within the application or not, since by default the graph doesnt consider this.
Suggestion:
After building the dependency graph , verify each element through go mod why as explained here
 Basem Vaseghi<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

since by default the graph doesnt consider this.

Doh, that's quite a bummer. Thanks for pointing this out.
So taking go mod why into account should also help to address #3860.

yes the pseudo code would be:

get the dependency tree using go mod graph which should print the module requirements
run each entry through go mod why to verify whether that dependency is part of the compilation or an unused dependency

run each entry through go mod why to verify whether that dependency is part of the compilation or an unused dependency

That bit unfortunately sounds very involving when you have hundreds or thousands of dependencies in the graph. But at least go mod why seems to accept multiple packages, so we can probably do one huge bulk-request, or at least go through the graph's nodes in chunks.

thats true, luckily even in the kubernetes project we dont come anywhere near that many dependencies. Most larger projects converge anywhere between 100-500 deps. If the we know of an optimized way, the better!

@dlorenc pointed out in his [Tweet|https://twitter.com/lorenc_dan/status/1397879783078379522] that go list -deps -json ./... is the only right way to get the dependencies for a Go project yet in OSS Review Toolkit we use we go mod vendor -v  and go mod graph. It was not clear to me from reading GoMod.kt why we use graph and vendor and not list.

It was not clear to me from reading GoMod.kt why we use graph and vendor and not list.

See https://github.com/oss-review-toolkit/ort/pull/2430.

So the current implementation is correct? I would like to start working on this ticket.

So the current implementation is correct?

I have no indication that it's not correct. When looking at the test asset changes in Martin's PR where he switched from go list to go mod, only two changes were made to the expected results, and it was discussed here. So unless there is proof otherwise, I regard the current implementation to be correct (modulo this very bug you intend to work on).
But maybe @vbasem can also comment on the go list vs. go mod issue, and which one should preferably be used to get the dependency tree?


Bug register

Hello, so when I log in with the login system it works I can log in but when I create an account it does not create it in the database why?

It's requete sql is false


Fix Safari

nsec.app login isn't working, probably because it tries to window.open without a user action.

Apparently nsec.app isn't working on Safari either


implement Job.ReclaimablePods for AppWrappers

In the cases where the appwrapper contains resources that are managed by Kueue and the component implemented ReclaimablePods, we should monitor the workload instances and flow that information through to Kueue.

This is somewhat related to #74 in that it relies on some level of understanding of the wrapped GVK's semantics.

In Kueue 0.7 only Job, JobSet, and Pod (for PodGroups) implement this optional interface.  Until the interface is more widely adopted, there is limited value to recognizing this situation and flowing it through the AppWrapper to Kueue.

While support for Ray jobs seems problematic given #174, we should be able to implement this interface for wrapped PyTorchJobs, in the following sense: if a PyTorchJob status is failed then we can assume no more pods will be created by the Training operator for this job.


MAINTAINERS: update collaborator list

glaubermaroto is no longer working on Zephyr.
uLipe isn't maintaining the support.
Signed-off-by: Sylvio Alves<EMAIL_ADDRESS>

@stephanosio, for some reason, I can't add @marekmatej as reviewer (same happened in hal_espressif, which is now working). Would you send a new request for him?

Would you send a new request for him?

done

Would you send a new request for him?

done

Thank you!

Nervermind the comment above, I misread the PR description

Thanks guys!


Add more build options to get a separate lib, and the official release of 1.0

TODO:
Separate Photon lib to thread, net, rpc ... libs.

Add more build options, for example, get thread lib alone
Add a build option for C++ standard. Photon now hardcoded C++14. Users with C++17 might fail because of std::string_view
Rename BUILD_TESTING to PHOTON_BUILD_TESTING option, in case of being overwrite by parent project
Hide symbols, for example, aio and curl . Expose libc and libc++ only
Support changing submodule URL in option, for example, a gitee repo instead of the github repo
Publish the official 1.0 release

Why the separation?

I would suggest that:

We provide build options to allow for output as static or dynamic lib, whether build individual modules, whether link dependencies, and whether hide their symbols.
We release official pre-built binary libphoton.so that links together all dependencies (e.g. libcurl, libaio, etc.) statically, and hide their symbols inside libphoton.so to avoid potential conflicts with other libs.

I would suggest that:

We provide build options to allow for output as static or dynamic lib, whether build individual modules, whether link the modules together, whether link dependencies, and whether hide the symbols of the dependencies.

We release official pre-built binary libphoton.so that links together all dependencies (e.g. libcurl, libaio, etc.) statically, and hide their symbols inside libphoton.so to avoid potential conflicts with other libs.

These would be great indeed.

@beef9999 @Coldwings  Let's split the goal and achieve the sub-goals gradually.


Add Q10 function

Could we have the Q10 function in the rate law, for now, we could read the air "temperature" from "Results.txt".

Last time we discussed, Lili said to drop temperature control. Let's discuss on Wednesday.

Last time we discussed, Lili said to drop temperature control. Let's discuss on Wednesday.

o ~ I guess she changed her mind today and said we can use air temperature for now. Better to keep all functions there.


Dependencies update

I didn't do rigourous testing of the module, but in whatever test i did, the module worked fine.
Also added index.d.ts for TypeScript linters

Why's it closed?

Why's it closed?

I had committed some irreversible changes to the codebase, which could potentially break the module.
Hence closed it.
Also I had no way of reliably testing the module after dependencies update.


do errors better, capturing line numbers/context

Thanks for looking into this - as discussed this is really useful as unclear parser errors slow down development.


Cannot evaluate the variable in template when extra space appear

you will see the extra space is after the lp.selectedIndex
and for UI displays "{{lp.selectedIndex" rather than the index value.
import {Component, ViewChild, ElementRef} from "angular2/core";
import {Color}  from "color";
import {SearchBar} from "ui/search-bar";
import {TextField} from "ui/text-field";
import {Switch} from "ui/switch";
import {Slider} from "ui/slider";
import {Progress}from"ui/progress";
import {PropertyChangeData} from "data/observable";
import {Observable} from 'data/observable';

@Component({
    selector: "my-app",
    template: `
      <StackLayout>
    <ListPicker #lp [items]='model.listPickerItems' [(ngModel)]='model.selectedIndex'></ListPicker>

	      </StackLayout>
`,
    styleUrls: ["app.css"]
})
export class AppComponent {
    public model: Observable;
    constructor() {
        this.model = new Observable({
            'test': 'Jack',
            'testBoolean': false,
            'deliveryDate': new Date(),
            'deliveryTime': new Date(),
            'mydate': new Date(),
            'sliderTest': 0,
            'search': null,
            'selectedIndex': 3,
            'listPickerItems': [
                1, 2, 3, 4, 5
            ]
        });
    }

    ngAfterViewInit() {

    }
}

I thing the problem is that   is not a valid syntax. Try with

@vakrilov but lp.items can be displayed on screen 1,2,3,4 correctly.

@dreambo8563
You are right. The text={{lp.items}}  may work in some cases, but the recommended way to do that is with the binding syntax: [text]='lp.items'.
Here is the whole markup just for reference:
<StackLayout>
    <ListPicker #lp [items]='model.listPickerItems' [(ngModel)]='model.selectedIndex'></ListPicker>

</StackLayout>

@dreambo8563
Just a quick followup:

Will also work (even with the space) as long as you include the opening and closing quotes around the attribute value.

@vakrilov  thanks


CupertinoSearchTextField

Steps to Reproduce

import 'package:flutter/cupertino.dart';
import 'package:parent_app/ui/styles/colors.dart';
///
class NoticeHeader extends StatefulWidget {
  ///
  const NoticeHeader({Key? key}) : super(key: key);

  @override
  _NoticeHeaderState createState() => _NoticeHeaderState();
}

class _NoticeHeaderState extends State<NoticeHeader> {
  late TextEditingController _textController;

  @override
  void initState() {
    super.initState();
    _textController = TextEditingController(text: 'initial text');
  }

  @override
  Widget build(BuildContext context) {
    return CupertinoSearchTextField(
        itemColor: LColors.black,
        backgroundColor: LColors.black,
        controller: _textController);
  }
}

Expected results:
Actual results:

flutter: The following assertion was thrown during performLayout():
flutter: RenderBox was not laid out: RenderPointerListener#ade8a relayoutBoundary=up6 NEEDS-PAINT
flutter: NEEDS-COMPOSITING-BITS-UPDATE
flutter: 'package:flutter/src/rendering/box.dart':
flutter: Failed assertion: line 1940 pos 12: 'hasSize'
flutter:
flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
flutter: more information in this error message to help you determine and fix the underlying caus

@ashish12s3
Can you provide flutter doctor -v and a complete minimal reproducible code sample that shows this issue ?
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


zcommand: Rename night->dark and day->light in the color scheme backend.

As a follow up for f49a11c810632cce6a94e679b2fb847dd2291c42, this PR standardizes the naming of the day and night themes to light and dark, respectively in the backend. This makes the backend consistent with the naming used in the frontend and UI.
This also solves a regression introduced in f49a11c810632cce6a94e679b2fb847dd2291c42, where the frontend was sending /light and /dark commands to the backend, but the backend was expecting /day and /night commands.

Fixes: Issue reported on CZO

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @sayamsamal! @amanagr FYI.


All send attempts fail after aborting SendData with timed out callback

https://gist.github.com/robarnold/c94d61f91fa4c78002e87e4805c4ca95 has a log that shows this. We should consider soft-resetting the controller when this happens for a longer stretch of time.

I have this exact problem.
I have been strugeling for days trying to solve this my zwave-js crashes multiple times a day so i really cant use it.
I have tried changing from a pc to Rpi4 a new z stick lon and short usb cables and powered usb hub.
My log files looks exactly like this one.
Do you know of a fix or do i need to restart zwave js multiple times a day?
Many Thanks Jonas

@Qwerty1979Swe can you share your log? On second look the controller in the log above actually failed to send a callback before the infinite loop.

Another log: https://github.com/home-assistant/core/files/12593063/zwavejs_current.log
Again, controller got stuck and failed to callback. After that, all send attempts fail immediately.

This could be the same issue I've had since the beginning of August as well.

I just wanted to update this thread with my specs since I'm still having the problem...
Home Assistant is running in a VM on UnRAID version 6.12.4
Home Assistant 2023.9.2
Supervisor 2023.09.2
Operating System 10.5
Frontend 20230911.0 - latest
zwave-js-ui: 8.25.1
zwave-js: 11.14.2
Aeotec Z-Stick 7 - firmware version 7.19.3

I have a plan on how to work around this in node-zwave-js, but I'm not sure it will work first try. Also it's entirely possible that the 7.19.3 firmware is bugged.

I have a plan on how to work around this in node-zwave-js, but I'm not sure it will work first try. Also it's entirely possible that the 7.19.3 firmware is bugged.

I'm up for testing anything I need to at this point since mine has been broken since at least the beginning of August.
It would have also had to have the same bug in older firmware as well. I had the issue on my original z-stick which was running a different version (honestly can't remember what the exact numbers were at this point) when this started. I upgrade the firmware on it at that point during some of my troubleshooting. Then when I first got this stick to replace it thinking maybe the stick itself was failing, it was running another older version as well. Then I upgraded it to the current version available, and still have the issue. There's a possibility that there's a firmware bug, but I hadn't upgraded the old z-stick any time in probably years when this issue first popped up for me.
I do have one question. Is it possible to back up the z-stick and restore to a different brand stick? Like if I picked up another 700 series stick, could I restore to that? That might be a last ditch effort if we can't find a fix. I'd rather not buy yet another stick, but if there is no software fix, I'd probably try more physical troubleshooting.

Yeah. With zwave-js you can even go back to 500 series, as long as the SDK version of the target firmware is 6.61 or higher.

@wljohnson05 I have the exakt same problem and the exact same setup and versions. Tried updating the stick to firmware 7.19.4 today but that didn't fix the problem...
Have you guys made any progress?

It seems to be a version <IP_ADDRESS> available but according to the dates that version was released before the one marked as "latest" wich is <IP_ADDRESS>.
I don't get it? worth trying?
https://github.com/SiliconLabs/gecko_sdk/releases

It seems to be a version <IP_ADDRESS> available but according to the dates that version was released before the one marked as "latest" wich is <IP_ADDRESS>.
I don't get it? worth trying?
https://github.com/SiliconLabs/gecko_sdk/releases

I just stuck with the newest guide on the aeotec site that I could find. That had the 7.19.3 on it.
https://aeotec.freshdesk.com/support/solutions/articles/6000263744-update-z-stick-7-with-z-wavejs-ui

True but are we sure the problem is in the sticks firmware?
I would gladly buy another stick and backup and move if I knew i would work, is there a better stick out there without this problem?
Or is it just waiting för the Z-wave JS UI to update? Been havin trouble for several weeks now and really sick of it😃

True but are we sure the problem is in the sticks firmware?
I would gladly buy another stick and backup and move if I knew i would work, is there a better stick out there without this problem?
Or is it just waiting för the Z-wave JS UI to update?  That was just a potential issue. Mine has been acting up since before August. I have z-wave for every switch in my house with tons of automation built into double/triple taps that is basically unusable now after an hour or so. WAF has basically gone to zero on that. I definitely feel your pain on it not working. My z-stick is actually a new one that I bought while doing my initial troubleshooting (same as my original stick). Yesterday I went ahead and ordered the zooz stick that I'm going to try as well. At least if I'm still having the issues, we'll have more evidence towards it being a software issue with the plugin instead of the stick. Then I'll just have to figure out how to use the extra ones somewhere else.

I have had it about the same but I didnt realize it because I rebuilt my z-wave network from the beginning with a new stick. I was having some problems with my old one but I walk right in to bigger trouble apparently...
Please tell me right away if the new stick works for you and if the backup/restore process from one stick to another works or gives you pain...
When the other issue similar to this got closed, is there no work being done to solve this?

I have had it about the same but I didnt realize it because I rebuilt my z-wave network from the beginning with a new stick. I was having some problems with my old one but I walk right in to bigger trouble apparently...
Please tell me right away if the new stick works for you and if the backup/restore process from one stick to another works or gives you pain...
When the other issue similar to this got closed, is there no work being done to solve this?

Will do. The only one I've been in any correspondence with is @AlCalzone, but I don't know if he's on the zwave js UI side or the zwave js side of development. He said it should be fine to restore to a different 700 series stick.

Ok thanks! To get closer quicker, do you want me to test with yet another stick?
You went for the zooz, I dont really know wich are avalible except theese two?
Only positive with this problem is that my network have never been faster(when it works). All the troubleshooting have lead to perfecting everything...to bad it ceashes all tje time😂😂

Ok thanks! To get closer quicker, do you want me to test with yet another stick?
You went for the zooz, I dont really know wich are avalible except theese two?
Only positive with this problem is that my network have never been faster(when it works). All the troubleshooting have lead to perfecting everything...to bad it crashes all the time😂😂

I'd say probably just wait. If a different stick shows the same issue, I'd say that proves more that it's a plugin related issue and not the sticks. If the zooz stick works fine, then we'll know it's a firmware issue that aeotec will have to fix.

zooz stick showed up today. I got my backup restored to it and everything has been up an running for about 80 minutes. We'll see how it is later tonight after it's been up and running for a few hours.

Well...300 minutes of home assistant being up, z-wave has stopped working again. I'm seeing the same jammed messages in the log, so I'd say we've proved that two different sticks are running into the same symptoms. @AlCalzone, did you find a fix in the code?

With the last thing I can try, I've stood up a bare metal home assistant server and restored a backup to it. I'm going to run that for the day and see if I have the same issues.

@wljohnson05 is this also on firmware 7.19.3? So far all reports of this that I've seen were on that version.
I was on vacation the last 7 days, will try to implement a workaround soon.

@wljohnson05 is this also on firmware 7.19.3? So far all reports of this that I've seen were on that version.
I was on vacation the last 7 days, will try to implement a workaround soon.

This stick is running 7.19.2. I looked, but I couldn't find a version of 7.19.3 for that stick. Closest thing I could see to the other is a file with "7.18.3" in the name. Not sure if that's a typo or what, so I didn't try to push that.
https://www.support.getzooz.com/kb/article/931-how-to-perform-an-ota-firmware-update-on-your-zst10-700-z-wave-stick/

This stick is running 7.19.2

Oh man, then the entire 7.19 release line is just fucked.

This stick is running 7.19.2

Oh man, then the entire 7.19 release line is just fucked.

Oh so you're thinking that was intentional, and that 7.19 has a major bug that's so bad that they are rolling back to 7.18?

Not sure, but I don't think Zooz ever officially recommended 7.19

Not sure, but I don't think Zooz ever officially recommended 7.19

That's what they shipped it out with, so you wouldn't think it would be too bad, unless it's something they uncovered after putting out that supply of sticks.

@AlCalzone , My new physical HA instance I stood up is having the same issue now as well, so I'd say I'm almost positive it's a software issue...whether that be the plugin or the firmware used on these sticks, I don't know, but I've run several firmware versions in duration of this troubleshooting, so it could be that the entire 7.19 line is screwy for z-wave in general (I can't remember if I ran any 7.18 or not), or there's a bad bug in the z-wave js codebase that has popped up. Anything else I can do to test/help? I'm not much help on javascript, I work mainly in perl in python, so I can't help you with the zwave js stuff.

I have implemented a possible workaround. Unfortunately it depends on changes I did for the upcoming 12.x release, which are too big to backport, so it might be 1-2 weeks until it comes into effect.

I have implemented a possible workaround. Unfortunately it depends on changes I did for the upcoming 12.x release, which are too big to backport, so it might be 1-2 weeks until it comes into effect.

2 weeks is better than never. Thanks for working on it.
So, does this pretty effectively fix the issue from what you can see?

I tried to reproduce the behavior from the logs in a test case, but I don't know if the affected controllers actually behave the same (return to normal behavior after soft-reset), especially since the expected behavior after recovery isn't included in the logs. So there's a chance this doesn't work.
Hard to test without being able to reproduce reliably.

I tried to reproduce the behavior from the logs in a test case, but I don't know if the affected controllers actually behave the same (return to normal behavior after soft-reset), especially since the expected behavior after recovery isn't included in the logs. So there's a chance this doesn't work.
Hard to test without being able to reproduce reliably.

So it will essentially act the same way as if when mine stops working, I go in and do a soft reset on it? Do you need logs of that whole process of me doing that?
I guess the only downside to a soft reset is that it will take the z-wave network down for a minute or two while it loads everything back up, but I guess if it's already unresponsive at that point, it will at least get it going again.
Any idea what is causing it to lock up in the first place all of sudden recently? I mean my network worked fine before all this started. I hadn't updated my stick firmware for probably years. So I tend to think there was an update somewhere in either zwavejs or home assistant that caused this to start happening in the first place.

So it will essentially act the same way as if when mine stops working, I go in and do a soft reset on it? Do you need logs of that whole process of me doing that?

Would be nice.

I guess the only downside to a soft reset is that it will take the z-wave network down for a minute or two

Normally, this should take in the order of a few seconds. Soft-reset just restarts the stick, not the entire stack. There's a command for this in Z-Wave JS UI in the advanced panel.

I hadn't updated my stick firmware for probably years

Unlikely, since 7.19 came out in December 22: https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.2.0 and the likely first release breaking this in March 23: https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.2.2

there was an update somewhere in either zwavejs [...]

I recently added detection for a jammed stick with retries. Before that, the node would just be marked dead when in reality the controller was the issue. What you're seeing now is an unfortunate infinite loop because transmitting is retried when the controller is considered jammed. The assumption here is that it eventually stops being jammed / is able to transmit again, but in this case the controller is just in a state it never recovers from on its own.

So it will essentially act the same way as if when mine stops working, I go in and do a soft reset on it? Do you need logs of that whole process of me doing that?

Would be nice.

I guess the only downside to a soft reset is that it will take the z-wave network down for a minute or two

Normally, this should take in the order of a few seconds. Soft-reset just restarts the stick, not the entire stack. There's a command for this in Z-Wave JS UI in the advanced panel.

I hadn't updated my stick firmware for probably years

Unlikely, since 7.19 came out in December 22: https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.2.0 and the likely first release breaking this in March 23: https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.2.2

there was an update somewhere in either zwavejs [...]

I recently added detection for a jammed stick with retries. Before that, the node would just be marked dead when in reality the controller was the issue. What you're seeing now is an unfortunate infinite loop because transmitting is retried when the controller is considered jammed. The assumption here is that it eventually stops being jammed / is able to transmit again, but in this case the controller is just in a state it never recovers from on its own.

I just got debug logging to a file set back up on it, and next time it acts up, I'll  try just doing a soft reset from the GUI and see how that reacts and logs.
I hadn't updated that original stick I had until after I ran into issues. I honestly don't remember what it was on before that though. I hadn't had any reason to update it probably since I bought it when I moved to home assistant from homeseer running a z-net device (probably the best move I decided to do in the home automation world). That hasn't been years, but probably at least early last year I believe.
That makes sense. I had actually been running an automation that I found that kept track of any dead nodes and pings them if that number of devices changes, so I guess that's why I never really had an issue before.

Should I be able to manually soft reset for now on 11.x when this occurs? Because that hasn't worked for me - I can leave the stick plugged in and restart ZUI to get it to start working again.

I recently updates my Zooz ZAC93 controller from FW 1.0 (SDK 7.18.?, I think) to 1.2 (SDK 7.19.3) and I belive I've begun to see this same issue. I opened #6300 before I saw this issue and have attached logs and other details there. Zooz recently released the 1.2 (7.19.3) firmware at https://www.support.getzooz.com/kb/article/1352-zst39-800-long-range-z-wave-stick-change-log/, so I expect a number of folks will be upgrading and hitting this issue. I can try to roll back to 1.1 (7.18.3) to see if that fixes it.

I can try to roll back to 1.1

Sadly, you can't.

Should I be able to manually soft reset for now on 11.x when this occurs?

I'm not sure if Z-Wave JS actually performs the soft-reset in that case, since it is still busy trying to get the other command done.

@AlCalzone , I'm seeing it work with the soft reset using the UI. It takes a little bit of time for it to actually reset, but eventually it came back to working, and any commands I had put it, caught up. It should be near the bottom of the log since I just did the fix this morning.

zwavejs_current.zip

Thanks for the test. Looks like the soft-reset helped for about an hour, so the workaround will at least do something.

Thanks for the test. Looks like the soft-reset helped for about an hour, so the workaround will at least do something.

Yeah, and when the code is handling the resets, it might not even be noticeable that it's happening since that would catch it before a human would most likely.

Apologies if this isn't helpful but I am not having any of these issues on a 36-node network controlled by a Zooz ZST39 running firmware 1.20 SDK 7.19.3.  HA 2023.9.2, Supervisor 10.5 on a Home Assistant Blue.  Also, no problems on a 23-node network controlled by a Zooz ZAC93 (same firmware/SDK) on a Home Assistant Yellow. Both locations running Z-Wave-JS UI.  Pretty much rock solid for over 2 months in both locations.  My experience would indicate that this is not an issue with 7.19.3 on Zooz 800 sticks.

@txwindsurfer I'm using a Zooz ZAC93 (with is the serial version of your ZST39) with a 95-node network and the issue is definitely present. It started as soon as I upgraded to the 1.20 (7.19.3) firmware from the stock 1.0 firmware. So the issue does impact Zooz 800-series sticks. There's likely some other variable at play here (perhaps certain types of messages being sent across the network) that triggers the controller to enter this state, and that must not occur in your setup. But I don't think it's because the Zooz 800 gear is immune to the problem.

I don't suppose there's a way to trigger the soft reset from within HA that anyone knows of? I have a script the currently power cycles my HA Yellow when this starts to occur, but it would be faster to just soft reset the controller as a stop gap if there's a way to do that from within HA.

Also, has anyone reported the issue to Zooz?

FWIW, I have this issue with an Aeotec Z-Stick 700 on 7.19.2, using Zwave JS addon in HA. The stick had been flashed to 7.19 last December and the network had been stable until early August when this issue was first noticed. I rolled back the HAOS Zwave JS addon to 0.186 (which I think uses ZWave JS 11.9.2) and haven't seemed to have the issue since.

Also, has anyone reported the issue to Zooz?

Yep

I'm having this problem on a ZST39 800LR with FW: v1.20, SDK: v7.19.3 .
I can trigger the condition at will by trying to flash my most distant ZEN76 800LR switch. The flashing never completes, and the stick ends up in a bad state.

See my comment here, Z-Wave JS v12 includes a workaround, HA and Z-Wave JS UI will pick this version up very soon.
The actual fix needs to happen in the controller firmware - I'm told Silabs are on it.
If this continues to be an issue after updating, please open a new issue.

@AlCalzone not sure if this is the same issue I'm having? https://github.com/home-assistant/addons/issues/3230 I've got an Aotec Stick Gen5 though. Kinda feels like a borked firmware update to me but I'm running HA OS and ZWaveJS from the add-on store so I don't know how to get into the guts of it. Any idea how I check which version of the firmware I'm running?

@AlCalzone , sorry to report...This didn't fix the issue for me. About the same amount of time before everything just stops getting commands. I've attached the log where it includes where I upgraded zwave js ui earlier today up through a few minutes ago. Looking at the log, it does have times where it said it was jammed, and then no longer jammed. I'm not sure if that is your workaround doing it's job or what, but eventually every command becomes a fail. Even manually triggering a soft reset in the gui doesn't fix it.
zwavejs_current.zip

@wljohnson05 looks like the recovery mechanism isn't working properly if there are still commands on the queue --> https://github.com/zwave-js/node-zwave-js/issues/6342

Looks like with the latest release of HA there was a z-wave js update that came along with it. Since yesterday my z-wave network has been running fine.


Windows 08-2020 update seems to have deassociated all of scoop's shims

All of my apps are still installed and functional if I run them from the scoop directory, but searching for them from the windows menu doesn't work. Reinstalling an app fixes this, but I would like to avoid resetting data on dozens of apps. Is there any workaround for this?
Thanks!

Solved my own problem -- 'scoop reset *' did the trick.


startArmLanguageServer

Does this occur consistently?
Repro steps:

Action: startArmLanguageServer
Error type: Error
Error Message: This extension requires .NET Core for full functionality, but we were unable to download and install a local copy for the extension. If this error persists, please see https://aka.ms/vscode-armtools-dotnet for troubleshooting tips.
Details: dotnet.acquire returned undefined
Version: 0.11.0
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.47.2
Language: en

Call Stack
Object.wrapError extension.bundle.js:393:92108
Object.<anonymous> extension.bundle.js:484:768397
fulfilled extension.bundle.js:484:767293

Did the troubleshooting tips at https://aka.ms/vscode-armtools-dotnet help?


New Streamlit update today breaks st-pages

Install and try - gets an error @blackary

hey, what error do you get?

@sfc-gh-trichards
Traceback (most recent call last):
  File "/usr/local/python/3.10.13/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 589, in _run_script
    exec(code, module.__dict__)
  File "/workspaces/BPhO-Computational/streamlit_app.py", line 18, in <module>
    show_pages_from_config()
  File "/usr/local/python/3.10.13/lib/python3.10/site-packages/streamlit/runtime/metrics_util.py", line 408, in wrapped_func
    result = non_optional_func(*args, **kwargs)
  File "/home/codespace/.local/lib/python3.10/site-packages/st_pages/__init__.py", line 308, in _show_pages_from_config
    show_pages(pages)
  File "/usr/local/python/3.10.13/lib/python3.10/site-packages/streamlit/runtime/metrics_util.py", line 408, in wrapped_func
    result = non_optional_func(*args, **kwargs)
  File "/home/codespace/.local/lib/python3.10/site-packages/st_pages/__init__.py", line 252, in _show_pages
    rt._sources_watcher = LocalSourcesWatcher(rt._main_script_path)
  File "/usr/local/python/3.10.13/lib/python3.10/site-packages/streamlit/watcher/local_sources_watcher.py", line 51, in __init__
    self._main_script_path = os.path.abspath(self._pages_manager.main_script_path)
AttributeError: 'str' object has no attribute 'main_script_path'

Actually nevermind I just updated st-pages and it works fine again


Error on check_md5 with folder

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

just add some folder in data and add documents to these folders (e.g.: \data\SomeFolder\someDocument.pdf)

Any log messages given by the failure

Traceback (most recent call last):
File "\scripts\prepdocs.py", line 256, in
loop.run_until_complete(main(file_strategy, azd_credential, args))
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\asyncio\base_events.py", line 649, in run_until_complete
return future.result()
File "\scripts\prepdocs.py", line 131, in main
await strategy.run(search_info)
File "\scripts\prepdocslib\filestrategy.py", line 54, in run
async for file in files:
File "\scripts\prepdocslib\listfilestrategy.py", line 82, in list
if not self.check_md5(path):
File "\scripts\prepdocslib\listfilestrategy.py", line 92, in check_md5
with open(path, "rb") as file:
PermissionError: [Errno 13] Permission denied: 'rootPath/data\SomeFolder'

Mention any other details that might be useful

A possibile fix is to add a check for directory like this on line 85 in listfilestrategy.py file:
def check_md5(self, path: str) -> bool:
# if path is a folder skip it
if os.path.isdir(path):
return True

Thanks! We'll be in touch soon.

Thanks for report, will send PR with fix soon.


Port application to melodic

update deb packages and  catkin build, remove ABB dependency in godel.
runtime issues in sim
runtime issues with real robot
check updates of repos in .rosinstall

IKFast plugin for UR5 as built with OpenRAVE. But it is provided in pilz_robot already. The API has changed.

/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp: In member function ‘virtual bool ikfast_kinematics_plugin::IKFastKinematicsPlugin::initialize(const string&, const string&, const string&, const string&, double)’:
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:324:86: error: ‘virtual void kinematics::KinematicsBase::setValues(const string&, const string&, const string&, const string&, double)’ is deprecated [-Werror=deprecated-declarations]
   setValues(robot_description, group_name, base_name, tip_name, search_discretization);
                                                                                ^
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:344:31: note: declared here
   [[deprecated]] virtual void setValues(const std::string& robot_description, const std::string& group_name,
                               ^~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp: In member function ‘virtual bool ikfast_kinematics_plugin::IKFastKinematicsPlugin::searchPositionIK(const Pose&, const std::vector<double>&, double, const std::vector<double>&, std::vector<double>&, const IKCallbackFn&, moveit_msgs::MoveItErrorCodes&, const kinematics::KinematicsQueryOptions&) const’:
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:885:67: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_positive_increments = (int)((max_limit - initial_guess) / search_discretization_);
                                                                   ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:885:67: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_positive_increments = (int)((max_limit - initial_guess) / search_discretization_);
                                                                   ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:886:67: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_negative_increments = (int)((initial_guess - min_limit) / search_discretization_);
                                                                   ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:886:67: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_negative_increments = (int)((initial_guess - min_limit) / search_discretization_);
                                                                   ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:890:86: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_positive_increments = (joint_max_vector_[free_params_[0]] - initial_guess) / search_discretization_;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:890:86: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_positive_increments = (joint_max_vector_[free_params_[0]] - initial_guess) / search_discretization_;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:891:86: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_negative_increments = (initial_guess - joint_min_vector_[free_params_[0]]) / search_discretization_;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:891:86: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     num_negative_increments = (initial_guess - joint_min_vector_[free_params_[0]]) / search_discretization_;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:983:32: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     vfree[0] = initial_guess + search_discretization_ * counter;
                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;
                         ^~~~~~~~~~~~~~~~~~~~~~
/home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:983:32: error: ‘kinematics::KinematicsBase::search_discretization_’ is deprecated [-Werror=deprecated-declarations]
     vfree[0] = initial_guess + search_discretization_ * counter;
                                ^~~~~~~~~~~~~~~~~~~~~~
In file included from /home/hsd/tmp/snp_demo_ws/src/pilz_robots/prbt_ikfast_manipulator_plugin/src/prbt_manipulator_ikfast_moveit_plugin.cpp:50:0:
/opt/ros/melodic/include/moveit/kinematics_base/kinematics_base.h:597:25: note: declared here
   [[deprecated]] double search_discretization_;

https://github.com/rosin-project/automatica18_scan_and_plan_demo/issues/21

IKFast plugin for UR5 was built with OpenRAVE. But it is provided in pilz_robot already. The API has changed.

Solved by changing pilz_robot and pilz_industrial_motion to melodic-devel, which also partly works on 4.
Descartes is using automatica18 branch which is very outdated from melodic-devel.
In file included from /home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/src/planning_graph.cpp:28:0:
/home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/include/descartes_planner/planning_graph_edge_policy.h: In member function ‘void descartes_planner::DefaultEdgesWithTime::consider(const double*, const double*, size_t)’:
/home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/include/descartes_planner/planning_graph_edge_policy.h:37:22: error: ‘accumulate’ is not a member of ‘std’
     auto cost = std::accumulate(delta_buffer_.cbegin(), delta_buffer_.cend(), 0.0);
                      ^~~~~~~~~~
make[2]: *** [CMakeFiles/descartes_planner.dir/src/planning_graph.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/src/dense_planner.cpp: In member function ‘bool descartes_planner::DensePlanner::updatePath()’:
/home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/src/dense_planner.cpp:88:96: error: no matching function for call to ‘std::vector<std::shared_ptr<descartes_core::TrajectoryPt> >::push_back(boost::detail::sp_if_not_array<descartes_trajectory::JointTrajectoryPt>::type)’
       path_.push_back(boost::make_shared<descartes_trajectory::JointTrajectoryPt>(std::move(p)));
                                                                                ^
In file included from /usr/include/c++/7/vector:64:0,
                 from /usr/include/eigen3/Eigen/StdVector:15,
                 from /opt/ros/melodic/include/eigen_stl_containers/eigen_stl_vector_container.h:42,
                 from /home/hsd/tmp/snp_demo_ws/src/descartes/descartes_core/include/descartes_core/trajectory_pt.h:30,
                 from /home/hsd/tmp/snp_demo_ws/src/descartes/descartes_core/include/descartes_core/path_planner_base.h:11,
                 from /home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/include/descartes_planner/dense_planner.h:11,
                 from /home/hsd/tmp/snp_demo_ws/src/descartes/descartes_planner/src/dense_planner.cpp:8:
/usr/include/c++/7/bits/stl_vector.h:939:7: note: candidate: void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = std::shared_ptr<descartes_core::TrajectoryPt>; _Alloc = std::allocator<std::shared_ptr<descartes_core::TrajectoryPt> >; std::vector<_Tp, _Alloc>::value_type = std::shared_ptr<descartes_core::TrajectoryPt>]
       push_back(const value_type& __x)
       ^~~~~~~~~
/usr/include/c++/7/bits/stl_vector.h:939:7: note:   no known conversion for argument 1 from ‘boost::detail::sp_if_not_array<descartes_trajectory::JointTrajectoryPt>::type {aka boost::shared_ptr<descartes_trajectory::JointTrajectoryPt>}’ to ‘const value_type& {aka const std::shared_ptr<descartes_core::TrajectoryPt>&}’
/usr/include/c++/7/bits/stl_vector.h:953:7: note: candidate: void std::vector<_Tp, _Alloc>::push_back(std::vector<_Tp, _Alloc>::value_type&&) [with _Tp = std::shared_ptr<descartes_core::TrajectoryPt>; _Alloc = std::allocator<std::shared_ptr<descartes_core::TrajectoryPt> >; std::vector<_Tp, _Alloc>::value_type = std::shared_ptr<descartes_core::TrajectoryPt>]
       push_back(value_type&& __x)

Can it be rebased? Need to look into the source-code.

Makes sense to combine 1. and 4.

any update on this issue?

@kvnptl quite a bit of API has changes, especially for Descartes. Looks like it is going to be an effort of more than one person. There has been some interest from companies in this application, but it might take some considerable time before we have new updates.


Added aka.ms to point to specific BF Emulator release

added https://aka.ms/bot-framework-emulator-download

@yochay - the aka link does not work.


GDscript function "free()" doesn't show up in the built-in help nor the auto-complete

So I know now that it's a real function, but you might not get the impression it is because the auto-complete doesn't have it when you start typing it and searching for it in the built-in help doesn't give any results.
Right now, with remove_and_delete_child() gone, people might otherwise end up wondering if there's no way to remove individual nodes in Godot.
Should be an easy one to fix.

great point, will add it
On Thu, Apr 9, 2015 at 2:51 PM, Ace-Dragon<EMAIL_ADDRESS>wrote:

So I know now that it's a real function, but you might not get the
impression it is because the auto-complete doesn't have it when you start
typing it and searching for it in the built-in help doesn't give any
results.
Should be an easy one to fix.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1664.


genewise fails to build

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[ ] If you're seeing permission errors tried running sudo chown -R $(whoami) $(brew --prefix)?

You can erase any parts of this template not applicable to your Issue.
Bug reports:
I am trying to install genewise via brew install homebrew/science/cegma and brew install genewise but they both give the same error.
Last 15 lines from /home/ubuntu/.cache/Homebrew/Logs/genewise/01.make:
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_add_pair_HSPmanager_score':
hsphandler.c:(.text+0x1022): undefined reference to `g_hash_table_lookup'
hsphandler.c:(.text+0x1183): undefined reference to `g_hash_table_insert'
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_add_pair_HSPmanager':
hsphandler.c:(.text+0x12d2): undefined reference to `g_hash_table_lookup'
hsphandler.c:(.text+0x1443): undefined reference to `g_hash_table_insert'
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_new_HSPmanager':
hsphandler.c:(.text+0x1764): undefined reference to `g_direct_equal'
hsphandler.c:(.text+0x1769): undefined reference to `g_direct_hash'
hsphandler.c:(.text+0x1776): undefined reference to `g_hash_table_new'
collect2: error: ld returned 1 exit status
make[1]: *** [genewise] Error 1
make[1]: Leaving directory `/tmp/genewise20160414-23397-fdy5zm/wise2.4.1/src/models'
make: *** [realall] Error 2
make: Leaving directory `/tmp/genewise20160414-23397-fdy5zm/wise2.4.1/src'

READ THIS: https://github.com/Linuxbrew/linuxbrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting
If reporting this issue please do so at (not Homebrew/homebrew):
  https://github.com/Homebrew/homebrew-science/issues

and
Last 15 lines from /home/ubuntu/.cache/Homebrew/Logs/genewise/01.make:
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_add_pair_HSPmanager_score':
hsphandler.c:(.text+0x1022): undefined reference to `g_hash_table_lookup'
hsphandler.c:(.text+0x1183): undefined reference to `g_hash_table_insert'
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_add_pair_HSPmanager':
hsphandler.c:(.text+0x12d2): undefined reference to `g_hash_table_lookup'
hsphandler.c:(.text+0x1443): undefined reference to `g_hash_table_insert'
../dynlibsrc//libdyna_glib.a(hsphandler.o): In function `Wise2_new_HSPmanager':
hsphandler.c:(.text+0x1764): undefined reference to `g_direct_equal'
hsphandler.c:(.text+0x1769): undefined reference to `g_direct_hash'
hsphandler.c:(.text+0x1776): undefined reference to `g_hash_table_new'
collect2: error: ld returned 1 exit status
make[1]: *** [genewise] Error 1
make[1]: Leaving directory `/tmp/genewise20160414-24284-7chs7s/wise2.4.1/src/models'
make: *** [realall] Error 2
make: Leaving directory `/tmp/genewise20160414-24284-7chs7s/wise2.4.1/src'

READ THIS: https://github.com/Linuxbrew/linuxbrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting
If reporting this issue please do so at (not Homebrew/homebrew):
  https://github.com/Homebrew/homebrew-science/issues

Is there a chance that genewise can't be installed using Linuxbrew?
Does anyone have an idea what is going wrong or how I can fix this?

Please include the link from:
brew gist-logs <formula>
(where <formula> is the name of the formula that failed to build).

I am sorry, this is the link I got: https://gist.github.com/5ed55a7589a494f032ff82c6dcc9fec3

No worries.
cc -o genewise genewise.o geneparser21.o geneparameter.o genestats.o genewisehsp.o geneutil.o geneoutput.o threestatemodel.o genefrequency.o splicesitemodeler.o genewise4.o genewise6.o genestretch6.o genewise21.o geneloop21.o geneloop6.o genephase6.o gwlite.o gwlitemodel.o gwrap.o matchsum.o estwrap.o genewisemodel.o phasemodel.o cdparser.o genedisplay.o estwise3.o estslim3.o estloop3.o estfrag3.o estslimloop.o gwquickdb.o threestatedb.o pfamhmmer1db.o pwmdna.o wise2xhmmer2.o genewisemodeldb.o seqhit.o standardout.o geneparser4.o sw_wrap.o abc.o pba.o seqaligndisplay.o dbadisplay.o proteinsw.o estquick3.o  -L../base/ -L../dynlibsrc/ -L../HMMer2/ -lpthread `pkg-config glib-2.0 --libs` -lhmmer -ldyna_glib -ldyna_glib -ldyna_glib -ldyna -lwisebase  -lm
../dynlibsrc//libdyna_glib.a(subseqhash.o): In function `Wise2_free_subseqhash_ghash':
subseqhash.c:(.text+0x4c): undefined reference to `g_hash_table_foreach_remove'

https://gist.github.com/anonymous/5ed55a7589a494f032ff82c6dcc9fec3#file-01-make-L684
There appears to be a bug in the genewise Makefile. The libraries -l… are specified in the wrong order. Either brew install gcc or brew install binutils may work around your issue.
I'm reassigning this issue to Homebrew-science.

This issue was moved to Homebrew/homebrew-science#3567


LIBS-264

Pull Request Test Coverage Report for Build 62

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 22.222%

Totals

Change from base Build 10:
0.0%

Covered Lines:
4

Relevant Lines:
18

💛  - Coveralls


CentOS 6/7/8 - Enable additional repositories to match CentOS equivalent

The converter enables the minimum base Oracle Linux repositories. Users may be using additional CentOS repositories so we should automatically enable the Oracle Linux equivalent.
We should not automatically enable all Oracle Linux repositories, just the equivalent of those already enabled. This may take some research and testing e.g. CodeReady Builder vs PowerTools.

Started working in fork https://github.com/oracle/centos2ol/compare/main...mark-au:feature-automatically-enable-repos
Code can currently read out enabled repos.
Starting to map out equivalent repos names.
An easy way to get started is:
podman run -ti centos:6 /bin/bash
podman run -ti centos:7 /bin/bash
podman run -ti centos:8 /bin/bash
podman run -ti oraclelinux:6 /bin/bash
podman run -ti oraclelinux:7 /bin/bash
podman run -ti oraclelinux:8 /bin/bash


Allow twister to natively specify additional config files and dts overlay files

Currently, in order to specify additional .conf files and DTS overlays, projects need to do something like:
    extra_args: CONF_FILE="first.conf;second.conf" DTC_OVERLAY_FILE="first.overlay;second.overlay"
    extra_configs:
      - CONFIG_SAMPLE=y

I would like to add something similar to extra_configs for both DTC overlays and CONF_FILE so it would look more yaml native:
extra_configs:
  - CONFIG_SAMPLE=y
extra_conf_files:
  - first.conf
  - second.conf
extra_dtc_overlay_files:
  - first.overlay
  - second.overlay

Long term, I would like to be able to specify a parent config similar to how we can specify a common. The parent would be a relative path and would include the parent's project fully. This would look like:
my.test.case:
  parent: ../common.test.case
  extra_configs:
...

@aaronemassey @tristan-google @asemjonovs @PerMac

I think this is a nice solution to a common problem we need to deal with and would make testcase.yaml files much more readable. I haven't looked closely but implementable entirely within TwisterConfigParser

lgtm for the configs/overlays. Anyone working in this already?
Regarding parents, need some more thinking, but makes sense in general.

Allow twister to naively specify

I guess you meant natively? :-)

lgtm for the configs/overlays. Anyone working on this already?
Regarding parents, need some more thinking, but makes sense in general.

I asked @tristan-google to look at this once he has our migration to twister underway. I'm hoping he'll be able to start on it by the end of the week or early next week.

Long term, I would like to be able to specify a parent config similar to how we can specify a common. The parent would be a relative path and would include the parent's project fully. This would look like:

my.test.case:
  parent: ../common.test.case
  extra_configs:
...

The tricky part is to be able to make sure that, at least for .overlays, the files are taken in the expected logical order.
For instance, today,
common:
    timeout: 5
    extra_args: DTC_OVERLAY_FILE="foo.overlay"
tests:
  drivers.stuff_1:
    extra_args: DTC_OVERLAY_FILE="bar.overlay"

is different from:
common:
    timeout: 5
tests:
  drivers.stuff_1:
    extra_args: DTC_OVERLAY_FILE="foo.overlay;bar.overlay"

As the second version allows to ensure foo.overlay is applied before bar.overlay, while this is not guaranteed in the first version.
This would be nice to allow this with this new change.

I will start work on the first half of this proposal (extra conf files/overlays) this week.

done


[Suggestion] Making Item quantities clearer in 2x2 and 1x2 drawers

Description:
When having large quantites of items in 2x2 or 1x2 drawers, the numbers become a jumbled mess and are hard to distinguished. A simple fix for this would be to simply make use of the empty space in drawer UI.

Also, it could move the numbers to be bellow each slot, soi they are clearer.


feat: update base token rate on L1

Currently base token to ETH ratio is always locked to 1:1 on the L1. This PR changes that and adds functionality to update L1 numerator and denominator as soon as they get updated on the L2. Updates are done by calling IChainAdmin.setTokenMultiplier function. The function can only be called by a new role - tokenMultiplierSetter.
This PR introduces the following changes:

new wallet for tokenMultiplierSetter, provisioned with ETH on network initialisation;
updates to old and new tooling to fully support this new role;
updates to base_token_ratio_persister to do the L1 updates;

What is not included:

Conditional updates - to save gas cost if numerator / denominator hasn't changed since the last time;
Support for fluctuating numerator / denominator in EN - that will be added in a separate PR.

PR to update tolling on the era-contracts side.

What's the plan if max_attempts is reached for sending l1 tx?

Good point - currently the server is going to halt, which shouldn't be the case. Updated the logic so that it's going to be just retried on the next iteration.


No longer works in chrome

The plugin no longer works in chrome. It loads a blank tab in the developer tools. I disabled all of my other plugins to ensure there were no conflicts.

nm - this was an iframe issue :face_palm:


k8s recommended labels

I have a nitpicking question regarding label best practices: What about using the k8s recommended labels AKA common labels instead of (or in addition to) the private label app?
The current configuration triggers this kubescape warning: C-0077 - K8s common labels usage
Maybe kustomize/kustomization.yaml could be extended like this:
+commonLabels:
+  app.kubernetes.io/name: "podinfo"
+  app.kubernetes.io/managed-by: "kustomize"
...

Podinfo is used by many project for e2e testing and docs (CNCF Flux, Flagger, Linkerd, etc), changing the labels is not something I would consider as they are immutable.