How to delete a complex graph?

Hello!
I have three tables (Sqlite):

Authors (id, name)
AuthorsPosts (author_id, post_id) - many to many
Posts (id, content)

class Post extends Model {
	static get tableName() {
		return "t_posts";
	}
}

class Author extends Model {
	static get tableName() {
		return "t_authors";
	}

	static get relationMappings() {
		return {
			posts: {
				relation: Model.ManyToManyRelation,
				modelClass: Post,
				join: {
					from: "t_authors.id",
					through: {
						from: "t_authors_posts.author_id",
						to: "t_authors_posts.post_id"
					},
					to: "t_posts.id"
				}
			}
		};
	}
}

Please give an example of deleting the graph Authors -> AuthorsPosts -> Posts or write how to gracefully delete this graph?
Thank you so much.

My code:
const author = await Author.query()
  .skipUndefined()
  .findById(req.params.id)
  .debug(true);

if (author) {
  let post_ids = [];

  const posts = await author.$relatedQuery("posts").map(async post => {
	await post_ids.push(post.$id());
  });

  if (post_ids.length > 0) {
	await author
	  .$relatedQuery("posts")
	  .unrelate()
	  .then(async () => {
		await post_ids.map(async post_id => {
		  await Post.query()
			.deleteById(post_id)
			.debug(true);
		});
	  });
  }

  await author
	.$query()
	.delete()
	.debug(true);
}

First of all, you need to add a onDelete('CASCADE') for your foreign keys t_authors_posts. See the example projects' migration files. That way the rows in t_authors_posts get autmatically deleted when either end of the relation (either the author or the post) gets deleted. That saves you from doing a separate unrelate an a separate delete.
Second of all, you don't need to loop through you relation and delete them individually. Instead of this
  // You need to use `Promise.all` by the way.
  const posts = await Promise.all(author.$relatedQuery("posts").map(async post => {
	await post_ids.push(post.$id());
  }))

you can just do this:
await author.$relatedQuery("posts").delete()

So your example gets reduced to this:
const author = await Author.query()
  // You definitely shouldn't use `skipUndefined` here. It will cause the
  // first author from the db (with arbitrary order) to be returned
  // `params.id` is undefined.
  .findById(req.params.id)
  .debug(true);

if (author) {
  await author
        .$relatedQuery('posts')
        .delete()

  await author
	.$query()
	.delete()
	.debug(true);
}

Excellent thanks!


Logical control type support

Hi Team,
I am trying to find the option, how can i fit  IF  ELSE control.
We have SWITCHand FOR LOOP already.
Please advise.
Thanks in advance.
Sreenadh.

@sreenadhvp Everything you can do with a "if / else" statement can be done with a "switch" statement in piper.
Do you have an example?

Quick question on this - can expression in switch take a comparator? e.g.
type: switch
expression: ${rating} < 50
If yes, i guess the key would be true or false.
Is my assumption correct? Thanks.

closing due to inactivity


[libigl] Fix feature imgui's dependency imguizmo

Fixes #39864. Fix the error that the dependency imguizmo cannot be found:
CMake Error at /Users/leanderSchulten/git_projekte/vcpkg/scripts/buildsystems/vcpkg.cmake:857 (_find_package):
  Could not find a package configuration file provided by "imguizmo" with any
  of the following names:

    imguizmoConfig.cmake
    imguizmo-config.cmake

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the fix!


update pdm / pdm lockfile to 2.8.0

Change Summary
I noticed that we had pinned to an old pdm version in CI, I think this may not be necessary any more.
I also ran pdm lock --refresh with 2.8.0 installed.
Related issue number
Pin was introduced in #6014
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review


Fix NMI handling for P9 witherspoon

Change-Id: I86692cd06b288933023baffc0e27ed0f24723a0e
Signed-off-by: Lakshminarayana R. Kammath<EMAIL_ADDRESS>Fix NMI handling for P9 witherspoon

Use SBEFIFO as backend
Processor and PIB targets are probed before triggering stop all and sreset all to initiated NMI
Use thread_stop_all() and thread_sreset_all() library calls instead of doing using pdbg CLI

@spinler please review


Manually switching the konnected siren on gives error

Home Assistant release with the issue:
0.89.2

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

Component/platform:
konnected:
entity swith.siren

Description of problem:
'NoneType' object has no attribute 'put_device'
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Configuration.
  devices:
    - id: bcddc29d30c5
      binary_sensors:
        - zone: 1
          type: door
          name: '1 door'
      switches:
        - zone: out
          name: siren

I manually switch the siren on and get this

Traceback (if applicable):
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/websocket_api/commands.py", line 148, in handle_call_service
    connection.context(msg))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1133, in async_call
    self._execute_service(handler, service_call))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1155, in _execute_service
    await handler.func(service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_component.py", line 188, in handle_service
    self._platforms.values(), func, call, service_name
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 278, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 292, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/switch.py", line 67, in turn_on
    resp = self.client.put_device(
AttributeError: 'NoneType' object has no attribute 'put_device'

Additional information:

posted too soon..  need to redo

Turns out my Konnected board appears bad..

Turns out my Konnected board appears bad..

I have the same problem.  Did Konnected replace your board?


It ignores my prompt, generates random images

What the hell i feel like total noob, i did not changed anything at all just input my own prompt into main prompt window, is there a video on how to use it for various txt2img img2img inpaint modes cause theyre really a must , this node setup is damn scary and big
No clue how to go to img2img
No clue how to go to inpaint
No clue why theres not a single info about it  next to install instructions , i mean explain it like were 5 years old, this might be comfortable for you but not for newcomers, i do know how nodes work but i have no clue what to do anways, and on top of that it ignores my prompts
Ok looks like most recent json file is borked
I got older one and it works , still i would like to know how to use img2img or inpaint , that info should be on mainpage

This is not a bug. There is going to be more documentation in the future, for now it's all provided as-is. And if you want simpler prompting, switch the prompting style to "simple" and you only have to care about the main prompt and negative prompt.


Fixed badge page URL

Fixes #129
Brings the badges guide URL back to /guide/badges so it is consistent with all the other guide pages, and fixes two links in guides that were causing 404s.
Attempt 2 - The first attempt was closed as the working branch was based on the wrong branch.

@testkil is fixing this along with another issuse.


[GHSA-gc66-2jq6-66c6] An issue was discovered in Matrix libolm (aka Olm)...

Updates

Affected products
CVSS
Description
Severity
Summary

Comments
"Olm" is a protocol, not the software library with the vulnerability.
The CVSS score was inaccurate.
I am a member of the Matrix.org Foundation security team.
I was forced to select an "ecosystem" even if this advisory is for a C++ project.

Thank you very much @shelbyc.


*: rename cover file to update code coverage

What problem does this PR solve?

Issue Number: close #427
Problem Summary:
Currently, the code coverage file is different from that of CI, so the file is not uploaded.
What is changed and how it works:

Rename coverage file
Add -race to go test

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[x] No code

Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

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

/retest

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Concat relation fields

Hi there,
interesting package, thanks!
I have a feature request.. here's my use case :

A post is related to a user
I want to search post.title, post.content but also a concat of post.user.firstname+post.user.lastname

Is there any way to search concatenated fields of a relation ?

Hey @jp-gauthier, Currently the package does not support concatenated search on a relation. That might be a nice thing to add to the package. I will try to add this as soon as I get some time, most probably this weekend. If you want feel free to create a PR for the same.

Hello @akki-io, excellent, really appreciated!
I'll let you add this by yourself, so keep me in the loop.
Thanks again.


Zwave lock is not recognized by OZW

Home Assistant release with the issue:

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

Hass.io
Integration:

Zwave
Description of problem:
My lock (Yale Keyfree with Zwave plus addon) is not being recognized by Zwave integration in HA. Ive tried filling in a bug report on OZW github, but they dont support HA fork of OZW.
Traceback (if applicable):
Z-Wave entity Unknown Node 52 Battery Level (node_id: 52) not ready after 30 seconds, continuing anyway
9:37 AM components/zwave/__init__.py (WARNING)
Z-Wave entity Unknown Node 52 Locked (node_id: 52) not ready after 30 seconds, continuing anyway
9:36 AM components/zwave/__init__.py (WARNING)
Z-Wave node 52 not ready after 30 seconds, continuing anyway
9:36 AM components/zwave/__init__.py (WARNING)

Additional information:
OZW log: https://pastebin.com/Mz9fJR1H

When adding the lock using "Add secure node", the lock reports inclusion error
OZW log shows:
2019-11-25 21:29:14.184 Detail, Queuing (Controller) Add Device
2019-11-25 21:29:14.184 Info, Add Device
2019-11-25 21:29:14.184 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1c, 0x6d
2019-11-25 21:29:14.184 Detail, Notification: ControllerCommand - Starting
2019-11-25 21:29:14.185 Detail,
2019-11-25 21:29:14.185 Info, contrlr, Sending (Command) message (Callback ID=0x1c, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1c, 0x6d
2019-11-25 21:29:14.187 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x1c, 0x07, 0x00, 0x00, 0xa9
2019-11-25 21:29:14.187 Detail,
2019-11-25 21:29:14.187 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:29:14.187 Info, contrlr, ADD_NODE_STATUS_FAILED
2019-11-25 21:29:14.187 Detail, contrlr, Removing current message
2019-11-25 21:29:14.187 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-25 21:29:14.187 Detail, Notification: ControllerCommand - Failed
2019-11-25 21:29:14.187 Detail,
2019-11-25 21:29:14.187 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-25 21:29:14.238 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x1c, 0x06, 0x34, 0x00, 0x9c
2019-11-25 21:29:14.238 Detail,
2019-11-25 21:29:14.238 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:29:14.238 Detail, Node006,   Expected reply was received
2019-11-25 21:29:14.238 Detail, Node006,   Message transaction complete
2019-11-25 21:29:14.238 Detail,
2019-11-25 21:29:14.238 Detail, contrlr, Removing current message
2019-11-25 21:29:14.238 Detail, Notification: ControllerCommand - Completed

When adding the lock using "Add node" , the lock reports successful add:
2019-11-25 21:31:13.794 Info, Add Device
2019-11-25 21:31:13.795 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1d, 0x6c
2019-11-25 21:31:13.795 Detail, Notification: ControllerCommand - Starting
2019-11-25 21:31:13.795 Detail,
2019-11-25 21:31:13.795 Info, contrlr, Sending (Command) message (Callback ID=0x1d, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1d, 0x6c
2019-11-25 21:31:13.798 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x1d, 0x01, 0x00, 0x00, 0xae
2019-11-25 21:31:13.798 Detail,
2019-11-25 21:31:13.798 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:31:13.798 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2019-11-25 21:31:13.798 Detail, Node001,   Expected callbackId was received
2019-11-25 21:31:13.798 Detail, Node001,   Expected reply was received
2019-11-25 21:31:13.798 Detail, Node001,   Message transaction complete
2019-11-25 21:31:13.798 Detail,
2019-11-25 21:31:13.798 Detail, contrlr, Removing current message
2019-11-25 21:31:13.798 Detail, Notification: ControllerCommand - Waiting
2019-11-25 21:31:13.798 Info, WriteNextMsg Controller nothing to do
2019-11-25 21:31:20.488 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x1d, 0x02, 0x00, 0x00, 0xad
2019-11-25 21:31:20.488 Detail,
2019-11-25 21:31:20.488 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:31:20.488 Info, ADD_NODE_STATUS_NODE_FOUND
2019-11-25 21:31:20.488 Detail, Notification: ControllerCommand - InProgress
2019-11-25 21:31:20.809 Detail,   Received: 0x01, 0x0e, 0x00, 0x4a, 0x1d, 0x03, 0x42, 0x07, 0x04, 0x40, 0x03, 0x5e, 0x55, 0x98, 0x9f, 0xab
2019-11-25 21:31:20.809 Detail,
2019-11-25 21:31:20.809 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:31:20.809 Info, ADD_NODE_STATUS_ADDING_SLAVE
2019-11-25 21:31:20.809 Info, Adding node ID 66 - Non-Secure
2019-11-25 21:31:20.809 Detail, Notification: ControllerCommand - InProgress
2019-11-25 21:31:28.460 Detail, Node019,   Received: 0x01, 0x0c, 0x00, 0x04, 0x10, 0x13, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xb7, 0x52
2019-11-25 21:31:28.460 Detail,
019-11-25 21:31:44.809 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:31:44.809 Info, ADD_NODE_STATUS_PROTOCOL_DONE
2019-11-25 21:31:44.809 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-25 21:31:44.809 Detail, Notification: ControllerCommand - InProgress
2019-11-25 21:31:44.809 Detail,
2019-11-25 21:31:44.809 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-25 21:31:44.861 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x1d, 0x06, 0x42, 0x00, 0xeb
2019-11-25 21:31:44.861 Detail,
2019-11-25 21:31:44.861 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-25 21:31:44.861 Info, contrlr, ADD_NODE_STATUS_DONE
2019-11-25 21:31:44.864 Info, Node066,   Basic device class    (0x04) - Routing Slave
2019-11-25 21:31:44.864 Info, Node066,   Generic device Class  (0x40) - Entry Control
2019-11-25 21:31:44.864 Info, Node066,   Specific device class (0x03) - Secure Keypad Door Lock
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_DOOR_LOCK
2019-11-25 21:31:44.864 Info, Node066,   Mandatory Command Classes for Node 66:
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_BASIC
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_DOOR_LOCK
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_USER_CODE
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_VERSION
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_SECURITY
2019-11-25 21:31:44.864 Info, Node066,   Mandatory Command Classes controlled by Node 66:
2019-11-25 21:31:44.864 Info, Node066,     None
2019-11-25 21:31:44.864 Info, Node066,   Optional command classes for node 66:
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_ZWAVEPLUS_INFO
2019-11-25 21:31:44.864 Info, Node066,   CommandClass 0x55 - NOT REQUIRED
2019-11-25 21:31:44.864 Info, Node066,     COMMAND_CLASS_SECURITY (Existing)
2019-11-25 21:31:44.864 Info, Node066,   CommandClass 0x9f - NOT REQUIRED
2019-11-25 21:31:44.864 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2019-11-25 21:31:44.864 Detail, Node066, QueryStage_ProtocolInfo
2019-11-25 21:31:44.864 Detail, Node066, Queuing (Query) Get Node Protocol Info (Node=66): 0x01, 0x04, 0x00, 0x41, 0x42, 0xf8
2019-11-25 21:31:44.864 Detail, Node066, Queuing (Query) Query Stage Complete (ProtocolInfo)
2019-11-25 21:31:44.864 Info, Node066, Initializing Node. New Node: true (true)
2019-11-25 21:31:44.864 Detail, Node006,   Expected reply was received
2019-11-25 21:31:44.864 Detail, Node006,   Message transaction complete
2019-11-25 21:31:44.864 Detail,
2019-11-25 21:31:44.864 Detail, contrlr, Removing current message
2019-11-25 21:31:44.864 Detail, Node066, Notification: NodeAdded
2019-11-25 21:31:44.866 Detail, Node066, Notification: NodeProtocolInfo
2019-11-25 21:31:44.868 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.889 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.909 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.934 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.956 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.974 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:44.991 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.031 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.051 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.077 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.103 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.130 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.152 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.190 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:45.219 Detail, Notification: ControllerCommand - Completed
2019-11-25 21:31:45.224 Detail,
2019-11-25 21:31:45.224 Info, Node066, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=66): 0x01, 0x04, 0x00, 0x41, 0x42, 0xf8
2019-11-25 21:31:45.226 Detail, Node066,   Received: 0x01, 0x09, 0x01, 0x41, 0x53, 0xdc, 0x01, 0x04, 0x40, 0x03, 0x7f
2019-11-25 21:31:45.226 Detail,
2019-11-25 21:31:45.226 Info, Node066, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2019-11-25 21:31:45.226 Info, Node066,   Protocol Info for Node 66:
2019-11-25 21:31:45.226 Info, Node066,     Listening     = false
2019-11-25 21:31:45.226 Info, Node066,     Frequent      = true
2019-11-25 21:31:45.226 Info, Node066,     Beaming       = true
2019-11-25 21:31:45.226 Info, Node066,     Routing       = true
2019-11-25 21:31:45.226 Info, Node066,     Max Baud Rate = 40000
2019-11-25 21:31:45.226 Info, Node066,     Version       = 4
2019-11-25 21:31:45.226 Info, Node066,     Security      = false
2019-11-25 21:31:45.226 Detail, Node220,   Expected reply was received
2019-11-25 21:31:45.226 Detail, Node220,   Message transaction complete
2019-11-25 21:31:45.226 Detail,
2019-11-25 21:31:45.226 Detail, Node066, Removing current message
2019-11-25 21:31:45.226 Detail, Node066, Query Stage Complete (ProtocolInfo)
2019-11-25 21:31:45.226 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2019-11-25 21:31:45.226 Detail, Node066, QueryStage_Probe
2019-11-25 21:31:45.226 Info, Node066, NoOperation::Set - Routing=true
2019-11-25 21:31:45.226 Detail, Node066, Queuing (NoOp) NoOperation_Set (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x00, 0x00, 0x25, 0x1e, 0x9e
2019-11-25 21:31:45.226 Detail, Node066, Queuing (Query) Query Stage Complete (Probe)
2019-11-25 21:31:45.226 Detail,
2019-11-25 21:31:45.226 Info, Node066, Sending (NoOp) message (Callback ID=0x1e, Expected Reply=0x13) - NoOperation_Set (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x00, 0x00, 0x25, 0x1e, 0x9e
2019-11-25 21:31:45.236 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:31:45.236 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:31:46.384 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x1e, 0x00, 0x00, 0x73, 0x86
2019-11-25 21:31:46.384 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x1e received (expected 0x1e)
2019-11-25 21:31:46.384 Info, Node066, Request RTT 1157 Average Request RTT 1157
2019-11-25 21:31:46.384 Detail,   Expected callbackId was received
2019-11-25 21:31:46.384 Detail,   Expected reply was received
2019-11-25 21:31:46.384 Detail,   Message transaction complete
2019-11-25 21:31:46.384 Detail,
2019-11-25 21:31:46.384 Detail, Node066, Removing current message
2019-11-25 21:31:46.384 Detail, Node066, Notification: Notification - NoOperation
2019-11-25 21:31:46.385 Detail, Node066, Query Stage Complete (Probe)
2019-11-25 21:31:46.385 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2019-11-25 21:31:46.385 Detail, Node066, QueryStage_WakeUp
2019-11-25 21:31:46.385 Detail, Node066, QueryStage_ManufacturerSpecific1
2019-11-25 21:31:46.385 Detail, Node066, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2019-11-25 21:31:46.385 Detail, Node066, Queuing (Query) ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x1f, 0xe9
2019-11-25 21:31:46.385 Detail, Node066, Queuing (Query) Query Stage Complete (ManufacturerSpecific1)
2019-11-25 21:31:46.385 Detail,
2019-11-25 21:31:46.385 Info, Node066, Sending (Query) message (Callback ID=0x1f, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x1f, 0xe9
2019-11-25 21:31:46.394 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:31:46.394 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:31:46.415 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x1f, 0x00, 0x00, 0x03, 0xf7
2019-11-25 21:31:46.415 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x1f received (expected 0x1f)
2019-11-25 21:31:46.415 Info, Node066, Request RTT 29 Average Request RTT 593
2019-11-25 21:31:46.415 Detail,   Expected callbackId was received
2019-11-25 21:31:56.386 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:31:56.386 Detail, Node066, Removing current message
2019-11-25 21:31:56.386 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:31:56.388 Detail, Node066, Query Stage Complete (ManufacturerSpecific1)
2019-11-25 21:31:56.388 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodeInfo live=1
2019-11-25 21:31:56.388 Detail, Node066, QueryStage_NodePlusInfo
2019-11-25 21:31:56.388 Detail, Node066, Queuing (Query) ZWavePlusInfoCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x5e, 0x01, 0x25, 0x20, 0xff
2019-11-25 21:31:56.388 Detail, Node066, Queuing (Query) Query Stage Complete (NodePlusInfo)
2019-11-25 21:31:56.388 Detail,
2019-11-25 21:31:56.388 Info, Node066, Sending (Query) message (Callback ID=0x20, Expected Reply=0x04) - ZWavePlusInfoCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x5e, 0x01, 0x25, 0x20, 0xff
2019-11-25 21:31:56.396 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:31:56.396 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:31:56.416 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x20, 0x00, 0x00, 0x03, 0xc8
2019-11-25 21:31:56.416 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x20 received (expected 0x20)
2019-11-25 21:31:56.416 Info, Node066, Request RTT 27 Average Request RTT 310
2019-11-25 21:31:56.416 Detail,   Expected callbackId was received
2019-11-25 21:31:56.436 Detail, Node066,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x42, 0x09, 0x5e, 0x02, 0x01, 0x07, 0x00, 0x03, 0x00, 0x03, 0x00, 0xe5
2019-11-25 21:31:56.436 Detail,
2019-11-25 21:31:56.436 Info, Node066, Response RTT 48 Average Response RTT 48
2019-11-25 21:31:56.437 Info, Node066, ZWave+ Info Received from Node 66
2019-11-25 21:31:56.437 Info, Node066,   Zwave+ Node Type  (0x00) - Z-Wave+ node. Mandatory Command Classes:
2019-11-25 21:31:56.437 Info, Node066,     NONE
2019-11-25 21:31:56.437 Info, Node066,   Zwave+ Device Type  (0x300) - Door Lock Keypad. Mandatory Command Classes:
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_DEVICE_RESET_LOCALLY
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_ZWAVEPLUS_INFO
2019-11-25 21:31:56.437 Info, Node066,     0x59 (Not Supported)
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_POWERLEVEL
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_ASSOCIATION
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_VERSION
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_DOOR_LOCK
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_USER_CODE
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_BATTERY
2019-11-25 21:31:56.437 Info, Node066,   ZWave+ Role Type  (0x40) - Listening Sleeping Slave
2019-11-25 21:31:56.437 Info, Node066,     COMMAND_CLASS_DEVICE_RESET_LOCALLY
2019-11-25 21:31:56.437 Detail, Node066, Initial read of value
2019-11-25 21:31:56.437 Detail, Node066, Initial read of value
2019-11-25 21:31:56.437 Detail, Node066, Initial read of value
2019-11-25 21:31:56.437 Detail, Node066,   Expected reply and command class was received
2019-11-25 21:31:56.437 Detail, Node066,   Message transaction complete
2019-11-25 21:31:56.437 Detail,
2019-11-25 21:31:56.437 Detail, Node066, Removing current message
2019-11-25 21:31:56.437 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.455 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.473 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.491 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.513 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.530 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.547 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.561 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.575 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.589 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.604 Detail, Node066, Notification: ValueAdded
2019-11-25 21:31:56.626 Detail, Node066, Notification: ValueChanged
2019-11-25 21:31:56.633 Detail, Node066, Notification: ValueChanged
2019-11-25 21:31:56.641 Detail, Node066, Notification: ValueChanged
2019-11-25 21:31:56.648 Detail, Node066, Query Stage Complete (NodePlusInfo)
2019-11-25 21:31:56.648 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=SecurityReport live=1
2019-11-25 21:31:56.648 Detail, Node066, QueryStage_SecurityReport
2019-11-25 21:31:56.648 Detail, Node066, Queuing (Security) SecurityCmd_SupportedGet (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x98, 0x02, 0x25, 0x21, 0x3b
2019-11-25 21:31:56.648 Detail, Node066, Queuing (Query) Query Stage Complete (SecurityReport)
2019-11-25 21:31:56.648 Detail,
2019-11-25 21:31:56.648 Info, Node066, Processing (Security) Nonce Request message (Callback ID=0x21, Expected Reply=0x04)
2019-11-25 21:31:56.648 Info, Node066, Sending (Security) message (Callback ID=0x21, Expected Reply=0x04) - Nonce_Get(SecurityCmd_SupportedGet) - 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x98, 0x40, 0x05, 0x02:
2019-11-25 21:31:56.655 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:31:56.655 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:31:56.675 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x03, 0xea
2019-11-25 21:31:56.675 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2019-11-25 21:31:56.675 Info, Node066, Request RTT 27 Average Request RTT 168
2019-11-25 21:31:56.698 Detail, Node066,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x42, 0x0a, 0x98, 0x80, 0xc4, 0xf3, 0xfe, 0xc1, 0x9f, 0x9e, 0xe5, 0x17, 0x40
2019-11-25 21:31:56.698 Info, Node066, Received SecurityCmd_NonceReport from node 66
2019-11-25 21:31:56.698 Info, Node066, Sending (Security) message (Callback ID=0x22, Expected Reply=0x04) - SecurityCmd_SupportedGet (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x98, 0x02, 0x25, 0x22, 0x38
2019-11-25 21:31:56.708 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:31:56.708 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:31:56.734 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x22, 0x00, 0x00, 0x04, 0xcd
2019-11-25 21:31:56.734 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x22 received (expected 0x22)
2019-11-25 21:31:56.734 Info, Node066, Request RTT 85 Average Request RTT 126
2019-11-25 21:32:06.648 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:06.648 Detail, Node066, Removing current message
2019-11-25 21:32:06.648 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:06.650 Detail, Node066, Query Stage Complete (SecurityReport)
2019-11-25 21:32:06.650 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=ManufacturerSpecific2 live=1
2019-11-25 21:32:06.650 Detail, Node066, QueryStage_ManufacturerSpecific2
2019-11-25 21:32:06.650 Detail, Node066, Queuing (Query) ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x23, 0xd5
2019-11-25 21:32:06.650 Detail, Node066, Queuing (Query) Query Stage Complete (ManufacturerSpecific2)
2019-11-25 21:32:06.650 Detail,
2019-11-25 21:32:06.650 Info, Node066, Sending (Query) message (Callback ID=0x23, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x23, 0xd5
2019-11-25 21:32:06.658 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:06.658 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:07.938 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x23, 0x00, 0x00, 0x81, 0x49
2019-11-25 21:32:07.938 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x23 received (expected 0x23)
2019-11-25 21:32:07.938 Info, Node066, Request RTT 1288 Average Request RTT 707
2019-11-25 21:32:07.939 Detail,   Expected callbackId was received
2019-11-25 21:32:16.651 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:16.651 Detail, Node066, Removing current message
2019-11-25 21:32:16.651 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:16.652 Detail, Node066, Query Stage Complete (ManufacturerSpecific2)
2019-11-25 21:32:16.652 Detail, Node066, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Versions live=1
2019-11-25 21:32:16.652 Detail, Node066, QueryStage_Versions
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_NO_OPERATION
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_BASIC
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_DEVICE_RESET_LOCALLY
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_ZWAVEPLUS_INFO
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_DOOR_LOCK
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_USER_CODE
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_POWERLEVEL
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_BATTERY
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_ASSOCIATION
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_VERSION
2019-11-25 21:32:16.652 Info, Node066, Requesting Versions for COMMAND_CLASS_SECURITY
2019-11-25 21:32:16.652 Detail, Node066, QueryStage_Instances
2019-11-25 21:32:16.652 Info, Node066, Essential node queries are complete
2019-11-25 21:32:16.652 Detail, Node066, QueryStage_Static
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) DoorLockCmd_Configuration_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x62, 0x05, 0x25, 0x24, 0xc3
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) UserNumberCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x63, 0x04, 0x25, 0x25, 0xc2
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x26, 0xd0
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) AssociationCmd_GroupingsGet (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x85, 0x05, 0x25, 0x27, 0x27
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) VersionCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x86, 0x11, 0x25, 0x28, 0x3f
2019-11-25 21:32:16.652 Detail, Node066, Queuing (Query) Query Stage Complete (Static)
2019-11-25 21:32:16.652 Detail, Node066, Notification: EssentialNodeQueriesComplete
2019-11-25 21:32:16.653 Detail,
2019-11-25 21:32:16.654 Info, Node066, Sending (Query) message (Callback ID=0x24, Expected Reply=0x04) - DoorLockCmd_Configuration_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x62, 0x05, 0x25, 0x24, 0xc3
2019-11-25 21:32:16.661 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:16.661 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:17.897 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x24, 0x00, 0x00, 0x7c, 0xb3
2019-11-25 21:32:17.897 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x24 received (expected 0x24)
2019-11-25 21:32:17.897 Info, Node066, Request RTT 1243 Average Request RTT 975
2019-11-25 21:32:17.897 Detail,   Expected callbackId was received
2019-11-25 21:32:26.654 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:26.654 Detail, Node066, Removing current message
2019-11-25 21:32:26.654 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:26.655 Detail,
2019-11-25 21:32:26.655 Info, Node066, Sending (Query) message (Callback ID=0x25, Expected Reply=0x04) - UserNumberCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x63, 0x04, 0x25, 0x25, 0xc2
2019-11-25 21:32:26.662 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:26.662 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:27.942 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x25, 0x00, 0x00, 0x80, 0x4e
2019-11-25 21:32:27.942 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x25 received (expected 0x25)
2019-11-25 21:32:27.942 Info, Node066, Request RTT 1287 Average Request RTT 1131
2019-11-25 21:32:30.171 Detail, Node019, Notification: ValueChanged
2019-11-25 21:32:36.654 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:36.654 Detail, Node066, Removing current message
2019-11-25 21:32:36.654 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:36.655 Detail,
2019-11-25 21:32:36.655 Info, Node066, Sending (Query) message (Callback ID=0x26, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x72, 0x04, 0x25, 0x26, 0xd0
2019-11-25 21:32:36.663 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:36.663 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:37.928 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x26, 0x00, 0x00, 0x7f, 0xb2
2019-11-25 21:32:37.928 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x26 received (expected 0x26)
2019-11-25 21:32:37.928 Info, Node066, Request RTT 1272 Average Request RTT 1201
2019-11-25 21:32:37.928 Detail,   Expected callbackId was received
2019-11-25 21:32:46.656 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:46.656 Detail, Node066, Removing current message
2019-11-25 21:32:46.656 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:46.657 Detail,
2019-11-25 21:32:46.657 Info, Node066, Sending (Query) message (Callback ID=0x27, Expected Reply=0x04) - AssociationCmd_GroupingsGet (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x85, 0x05, 0x25, 0x27, 0x27
2019-11-25 21:32:46.665 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:46.665 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:47.930 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x27, 0x00, 0x00, 0x7f, 0xb3
2019-11-25 21:32:47.930 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x27 received (expected 0x27)
2019-11-25 21:32:47.930 Info, Node066, Request RTT 1272 Average Request RTT 1236
2019-11-25 21:32:56.657 Error, Node066, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-11-25 21:32:56.657 Detail, Node066, Removing current message
2019-11-25 21:32:56.657 Detail, Node066, Notification: Notification - TimeOut
2019-11-25 21:32:56.658 Detail,
2019-11-25 21:32:56.658 Info, Node066, Sending (Query) message (Callback ID=0x28, Expected Reply=0x04) - VersionCmd_Get (Node=66): 0x01, 0x09, 0x00, 0x13, 0x42, 0x02, 0x86, 0x11, 0x25, 0x28, 0x3f
2019-11-25 21:32:56.666 Detail, Node066,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-11-25 21:32:56.666 Detail, Node066,   ZW_SEND_DATA delivered to Z-Wave stack
2019-11-25 21:32:57.916 Detail, Node066,   Received: 0x01, 0x07, 0x00, 0x13, 0x28, 0x00, 0x00, 0x7e, 0xbd
2019-11-25 21:32:57.916 Detail, Node066,   ZW_SEND_DATA Request with callback ID 0x28 received (expected 0x28)
2019-11-25 21:32:57.916 Info, Node066, Request RTT 1257 Average Request RTT 1246

I believe that removing this line from OZW config may fix the problem:

But the lock runs with generic configuration, without many functionalities.


defaults/main.yml is overwritten by vars/main.yml

Attempting to install s3 deps, the following error is displayed:
task path: /private/etc/ansible/roles/Aplyca.s3fs/tasks/setup.yml:11
fatal: []: FAILED! => {"failed": true, "msg": "'dict object' has no attribute 'source'"}
This is due to vars being of a higher prescedence to defaults.

@pbrooks Thanks for trying this role and reporting issues.
You should use merge hash behaviour for variables (like dictionaries in Python). You can set this configuration by adding the setting hash_behaviour=merge to the ansible.cfg file which should be placed in the same directory where you are executing ansible-playbook command.
See the docs for more info: http://docs.ansible.com/ansible/intro_configuration.html#hash-behaviour or see the example here: https://github.com/Aplyca/ansible-role-s3fs/blob/master/ansible.cfg

@mauricios Thanks for this information and for amending the docs. I've just got round to improving my playbook to reflect your advice :)


Changed exception to warning for NumpyIterator

Right now NumpyIterator wont let us use multichannel data but it's common in satellite datasets such as Kaggle's Dstl Satellite Imagery Feature Detection or spacenet. This changes the exception to a warning.

This UserWarning keeps turning up too often for me and others who work with multichannel data. Can the warning be removed completely? I understand that this warning is to potentially spot channels_first/channels_last mixups, but the false positives are causing problems.


Experiment with SSH_KEY for excavator

If repository contains protected master it will need to provide ssh key as secret.
if ($env:SSH_KEY) {
    Set-Content "$HOME\.ssh\id_rsa" $env:SSH_KEY -Encoding ASCII
} else {
    git config remote-url ... $user:$token
}

If it will work. Note, example and instructions how to add have to be added into Readme.

https://github.community/t5/GitHub-Actions/How-to-push-to-protected-branches-in-a-GitHub-Action/m-p/30710/highlight/true#M526
Maybe some workaround with SSH / machine user / whatever could work. Need to investigate

Try with workaround without hub first and then hacky way with hub
    $remote = "https://${env:GITHUB_ACTOR}:${env:GITHUB_TOKEN}@github.com/${env:GITHUB_REPOSITORY}.git"
    git push $remote


ctr: implement CDI support

Implement support of the Container Device Interface (CDI) in ctr.
CDI goal is to update device-related information (devices, mounts, hooks, environment variables etc) in the OCI spec from the JSON files provided by device vendors. That would allow workloads to access properly configured devices.
The plan is to have CDI support in at least containerd, cri-o and podman. It's already implemented in podman: https://github.com/containers/podman/pull/10081
Here is a typical usage scenario:

vendor provides a spec update in the CDI JSON format, e.g:

$ cat /etc/cdi/test.json
{
  "cdiVersion": "0.2.0",
  "kind": "vendor.com/device",
  "devices": [
    {
      "name": "myDevice",
      "containerEdits": {
        "deviceNodes": [
          {"path": "/dev/device1", "type": "b", "major": 7, "minor": 0, "fileMode": 432, "permissions": "rw", "uid": 1000, "gid": 1000}
        ]
      }
    }
  ],
  "containerEdits": {
    "env": [
      "FOO=VALID_SPEC",
      "BAR=BARVALUE1"
    ],
    "deviceNodes": [
      {"path": "/dev/device1", "type": "b", "major": 7, "minor": 0, "fileMode": 432, "permissions": "rw", "uid": 1000, "gid": 1000}
    ],
    "mounts": [
       {"hostPath": "/bin/vendorBin", "containerPath": "/bin/vendorBin", "options": ["bind"]}
    ],
    "hooks": [
       {"hookName": "startContainer", "path": "/bin/vendorHook", "args": ["/bin/vendorHook", "param1", "param2"]}
    ]
  }
}

OCI spec gets updated by the ctr/containerd/other runtime and passed to the OCI runtime
workload can access the device inside a container

I can't reproduce any of above CI failures locally. Can anybody point me out how to fix those?

/cc @mikebrow @kad @klihub

Please explain the goal and usage

@AkihiroSuda done, please review.

https://github.com/containerd/containerd/pull/6195

this is an alternative approach to NRI: https://github.com/klihub/nri/blob/5f41c0fbfab8c026f94db5e3f3dc91ce9ff509bf/v2alpha1/plugins/cdi-resolver/cdi-resolver.go#L48-L60

@bart0sh
Could you explain why we can't use NRI?

We can, but it's much longer term plan, I'd say.

@AkihiroSuda More details on this.
This code https://github.com/klihub/nri/blob/5f41c0fbfab8c026f94db5e3f3dc91ce9ff509bf/v2alpha1/plugins/cdi-resolver/cdi-resolver.go#L48-L60 is not merged yet and it would take some time to get it merged.
Even if it's merged it would cover only CRI use case. Covering other types of clients (ctr, Docker, etc) would require even more work and there is no guarantee when/if it will be done.

I can't reproduce any of above CI failures locally. Can anybody point me out how to fix those?

Isn't at least one of those failures related to cross-builds (darwin) not finding the newly added WithCDIdevices() function because it is put in spec_opts_linux.go ?

Isn't at least one of those failures related to cross-builds (darwin) not finding the newly added WithCDIdevices() function because it is put in spec_opts_linux.go ?

Moved it to the spec_opts_unix.go, but it didn't help for some reason.

Isn't at least one of those failures related to cross-builds (darwin) not finding the newly added WithCDIdevices() function because it is put in spec_opts_linux.go ?

Moved it to the spec_opts_unix.go, but it didn't help for some reason.

Yes, but now it fails on linux because spec_opts_unix.go is tagged // +build !linux,!windows. I guess you need to have a real implementation in both spec_opts_{linux,unix}.go, and then probably have a stub that just  errors out for spec_opts_windows.go.

@AkihiroSuda More details on this. This code https://github.com/klihub/nri/blob/5f41c0fbfab8c026f94db5e3f3dc91ce9ff509bf/v2alpha1/plugins/cdi-resolver/cdi-resolver.go#L48-L60 is not merged yet and it would take some time to get it merged.

The cdi-resolver PR seems marked as "ready for review" recently. https://github.com/containerd/nri/pull/16

Even if it's merged it would cover only CRI use case. Covering other types of clients (ctr, Docker, etc) would require even more work and there is no guarantee when/if it will be done.

We can easily extend ctr (and/or nerdctl) to support NRI.
I'm not sure when Docker/Moby can support NRI, but that question applies to CDI too :)

I didnt find any related issue in containerd to support CDI just this PR to comment so posting here.
Just wanted to add a +1 for adding support for CDI in containerd.
we have a use-case to inject RDMA [1] resources to containers to allow applications to use RDMA.
using CDI we could provide additional mounts to expose those resources (linux character devices)
[1] https://community.mellanox.com/s/article/What-is-RDMA

Both #6654 and this PR adds CDI into containerd's dependencies. We probably should review one of them first. Maybe #6654?

@kzys yes, #6654 is more important. I'm closing this one to avoid confusion.


Play a sound when mic is muted/unmuted

Description of the new feature / enhancement
Play a sound when the microphone and/or camera is muted or unmuted.
User can enable or disable this feature.
Scenario when this would be used?
In certain scenarios, such as while playing a video game, (a) it may not be possible for the user to observe the layout, or (b) the layout may have to be switched off altogether (e.g., while streaming).
I find a similar feature very useful in Discord.
Supporting information
No response

Duplicate of #6332

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.


Added Apple Silicon support to WoA

Added support for Apple Silicon.

How do you differentiate M1/M1 Pro/M2/etc?

How do you differentiate M1/M1 Pro/M2/etc?

Great question, not so great answer ... 😕
I tried to preserve compatibility with current code and from that perspective all M1s are identical - they have same frequency and same types of high/low efficiency cores. This is not optimal, but if I did not miss something, returning more information - like amount of cores - would require breaking changes and this change at least prevents failures on M1s.
About distinguishing between M1 & M2, honestly I don't know. I don't have M2 to test it and did not find what string will be shown in Windows Registry for M2. I was hoping for different string or somebody updating it when it will become problem.

The current solution would likely produce wrong results on M2, which is a big no for cpuinfo. I'd rather have it report unknown that report wrong data. Please borrow an M2 Mac and try to figure out the answer. I found that SYSTEM_INFO::wProcessorLevel returned by GetSystemInfo seems to contain the "Part" component of the MIDR. Maybe this would be sufficient to distinguish M1, M2, and later cores.

@Maratyszcza I checked SYSTEM_INFO::wProcessorLevel and unfortunately it has value 0 on both M1 and M2. This could be due to running in VM as that is only way how to run Windows on M1 & M2 at this moment.
I tried to check also other attributes, but as far as I am aware of, there is no way how to distinguish M1 & M2 at this moment 😕 (you can check attached screenshots of Windows Registry + output of wmic cpu get which provides same value as SYSTEM_INFO::wProcessorLevel in Level field and more ...).
I am not sure how to follow up on this due to inability to distinguish between those CPUs. Do we need distinction between M1 & M2? I mean they are both Apple Silicon, so reporting Apple Silicon would be technically correct in all cases and it's more question of if we need distinction between them for something? What do you think?

WMIC M1
WMIC M2

Without the ability to distinguish variants of Apple Silicon all we can do is set vendor to cpuinfo_vendor_apple, as all other information is unreliable. Narrowing down this change to just the vendor setting would be acceptable, although not very useful.
I'd like to encourage you to check within Microsoft what other ways there can be to retrieve information about the cores. In particular, if you could get MIDR data for the cores, we could decode the microarchitecture and use them for ISA feature detection (e.g. Apple M2 supports BF16 and I8MM while Apple M1 doesn't).

One hint might be the CP4020...CP5801 values reported in the registry. They are evidently different across M1 and M2, but it is unclear what they represent. CP4020 looks like MIDR, albeit a fake one, probably others are different system registers.

This source snippet suggest that CP NNN these are indeed system registers.


disable automatic insertion of using directives

I wanted to ask if it is possible to disable the automatic insertion of "using" directives.
In summary, when you select a class from code completion, the editor automatically adds the "using" directive if it is missing. Is it possible to disable this option?

There is such an option in Roslyn but it's not exposed in RP - https://github.com/dotnet/roslyn/blob/33f853a8638d9254a04a5830870067f51f8dd63c/src/Features/Core/Portable/Completion/CompletionOptions.cs#L23

Thanks for the quick response. I don't understand though, is Roslyn adding the "using..." line? If I understand correctly, the option you highlighted should limit the elements of the completion. I didn't ask for that, I asked that the system not add the "using" line.

It's the same feature. If Roslyn shows unimported items in the completion menu, it will add the using when it commits such an item.

thanks @aelij, is there a way to set ShowItemsFromUnimportedNamespaces to false by recompiling RP?

Yeah, but wouldn't you prefer posting a PR and adding a setting?

Hi,
I'm not sufficiently familiar with the code base to know where the best place would be to connect a setting, but I was able to remove the unwanted completion items by 1) adding the below as RoslynPad.Roslyn/Completion/CompletionProviderExtensions.cs :
using System.Collections.Immutable;
using Microsoft.CodeAnalysis;
using Microsoft.CodeAnalysis.Completion;
using Microsoft.CodeAnalysis.Options;

namespace RoslynPad.Roslyn.Completion;

public static class CompletionProviderExtensions
{
    public static Task<CompletionList> GetCompletionsImportedOnlyAsync(
        this CompletionService service,
        Document document,
        int caretPosition,
        CompletionTrigger trigger = default,
        ImmutableHashSet<string>? roles = null,
        OptionSet? options = null,
        CancellationToken cancellationToken = default
        )
    {
        var completionOptions = CompletionOptions.Default with { ForceExpandedCompletionIndexCreation = true, ShowItemsFromUnimportedNamespaces = false };
        var passThroughOptions = options ?? document.Project.Solution.Options;

        return service.GetCompletionsAsync(document, caretPosition, completionOptions, passThroughOptions, trigger, roles, cancellationToken);
    }
}

And then 2) by changing RoslynPad.Editor.Windows/Shared/RoslynCodeEditorCompletionProvider.cs to use the above in place of GetCompletionsAsync() :
            var data = await completionService.GetCompletionsImportedOnlyAsync(
                document,
                position,
                completionTrigger
                ).ConfigureAwait(false);

@MatthewB05, I think it's a good solution, thank you very much.


Fix convert_path_to_posix for mixed paths

Fixes the regex used in the convert_path_to_posix method for forward slashed paths (C:/foo/bar).
This fix should be released for V4 and V5 of the package.

Will be fixed with: https://github.com/jantimon/css-variable/pull/46


Include partitionId in AzureBlobLeaseInfo

This addresses an issue where partitionId would be undefined causing the host to fail. The response from blob.getContent() looked something like this:
{"owner":"js-host-0826076f-42f3-4129-b1fb-6695733d532d","epoch":22,"sequenceNumber":0,"token":"174f6f89-e253-4fd2-ae6d-210aad163c41"}
On a side note, I also tried the C# event hub processor and it had no issues. I inspected the web traffic, and the response from azure looks almost identical and doesn't contain the partition id.
Here's some console output that shows error:
azure:eph:partitionScanner [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [0] Acquired unowned/expired lease.undefined +201ms
azure:eph:completeLease [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [undefined] Lease info is: { partitionId: undefined, owner: 'js-host-0826076f-42f3-4129-b1fb-6695733d532d', epoch: 18 } +42ms
azure:eph:azurebloblease [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [undefined] Lease info is: { partitionId: undefined, owner: 'js-host-0826076f-42f3-4129-b1fb-6695733d532d', epoch: 18, sequenceNumber: 0, token: '59746238-4501-459e-a585-bd8f4fb39038', offset: undefined } +41ms
azure:eph:pumpManager [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [N/A] Creating a new pump with lease { partitionId: undefined, owner: 'js-host-0826076f-42f3-4129-b1fb-6695733d532d', epoch: 18, sequenceNumber: 0, token: '59746238-4501-459e-a585-bd8f4fb39038', offset: undefined }. +0ms
azure:eph:partitionPump [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [N/A] Getting the initial offset. +0ms
azure:eph:error [js-host-0826076f-42f3-4129-b1fb-6695733d532d] [N/A] An error occurred while adding/updating a pump for partitionId 'undefined': TypeError: partitionId is required. Given value: undefined. Hence it cannot be null or undefined.
at Object.validateType (C:\sources\git\spew\SpewSocketIO\node_modules@azure\event-processor-host\dist\lib\util\utils.js:24:15)
at AzureStorageCheckpointLeaseManager. (C:\sources\git\spew\SpewSocketIO\node_modules@azure\event-processor-host\dist\lib\azureStorageCheckpointLeaseManager.js:394:21)
at Generator.next ()
at C:\sources\git\spew\SpewSocketIO\node_modules\tslib\tslib.js:107:75
at new Promise ()
at Object.__awaiter (C:\sources\git\spew\SpewSocketIO\node_modules\tslib\tslib.js:103:16)
at AzureStorageCheckpointLeaseManager.getCheckpoint (C:\sources\git\spew\SpewSocketIO\node_modules@azure\event-processor-host\dist\lib\azureStorageCheckpointLeaseManager.js:393:24)
at PartitionContext. (C:\sources\git\spew\SpewSocketIO\node_modules@azure\event-processor-host\dist\lib\partitionContext.js:108:78)
at Generator.next ()
at C:\sources\git\spew\SpewSocketIO\node_modules\tslib\tslib.js:107:75. +0ms
Description
Brief description of the changes made in the PR. This helps in making better changelog

Reference to any github issues

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

processor/lib/azureStorageCheckpointLeaseManager.ts
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add Apache license header

All source files written by us MUST include the Apache license header.
Need to add Apache license header to https://github.com/apache/singa/tree/dev/examples/cifar_distributed_cnn/run-rtx.sh

Added Apache license header to https://github.com/apache/singa/tree/dev/examples/cifar_distributed_cnn/run-rtx.sh


Problem in simde_mm512_xor_si512 in avx512f.h

See the two lines lines following SIMDE__VECTORIZE.
SIMDE__FUNCTION_ATTRIBUTES
simde__m512i
simde_mm512_xor_si512 (simde__m512i a, simde__m512i b) {
  #if defined(SIMDE_AVX512F_NATIVE)
    return _mm512_xor_si512(a, b);
  #else
    simde__m512i_private
      r_,
      a_ = simde__m512i_to_private(a),
      b_ = simde__m512i_to_private(b);

  #if defined(SIMDE_ARCH_X86_AVX2)
    r_.m256i[0] = simde_mm256_xor_si256(a_.m256i[0], b_.m256i[0]);
    r_.m256i[1] = simde_mm256_xor_si256(a_.m256i[1], b_.m256i[1]);
  #elif defined(SIMDE_ARCH_X86_SSE2)
    r_.m128i[0] = simde_mm_xor_si128(a_.m128i[0], b_.m128i[0]);
    r_.m128i[1] = simde_mm_xor_si128(a_.m128i[1], b_.m128i[1]);
    r_.m128i[2] = simde_mm_xor_si128(a_.m128i[2], b_.m128i[2]);
    r_.m128i[3] = simde_mm_xor_si128(a_.m128i[3], b_.m128i[3]);
  #elif defined(SIMDE_VECTOR_SUBSCRIPT_OPS)
    r_.i32f = a_.i32f ^ b_.i32f;
  #else
    SIMDE__VECTORIZE
    for (size_t i = 0 ; i < (sizeof(r_.i64) / sizeof(r_.i64[0])) ; i++) {
      r_.i32f[i] = a_.i32f[i] ^ b_.i32f[i];
    }
  #endif

  return simde__m512i_from_private(r_);
#endif
}
#if defined(SIMDE_AVX512F_ENABLE_NATIVE_ALIASES)
#  define _mm512_xor_si512(a, b) simde_mm512_xor_si512(a, b)
#endif

Git blames me for this but I am sure I used i64 in both lines.
Maybe you changed the second line to i32f.
Should I avoid i64?
Is i32f faster?
(Or perhaps some of your machines don't support 64-bit operations.)
So would you prefer that I correct the loop count to i32f or the operation to i64?

Maybe you changed the second line to i32f.
Should I avoid i64?
Is i32f faster?

Sorry, yes, I probably did.  IIRC I was merging several patches there, I thought that was part of a different one.
You shouldn't avoid i64 if that's the type you actually need to operate on, but when we don't care about the element size yes, i32f is better since it may be faster on some architectures.  For x86_64 it should be the same since IIRC int_fast32_t  in 64 bits, but on x86 it's 32 bits.  Basically, for most *_si* functions i32f is the correct choice.
I pushed a commit to staging to fix this, I'll merge it into master as soon as CI finishes.


help request: Fluentbit intermittent 404 issues on /api/v2/metrics/prometheus endpoint

Describe the issue
We have installed 3.2.0 version of fluent operator helm chart and have enabled fluentbit to ship logs from k8s containers to opensearch in aws. When we turn on servicemonitor we see 404 on /api/v2/metrics/prometheus on different fluentbit pods at different times.
at t1:

at t2:

How did you install fluent operator?
helm chart version 3.2.0
Additional context
No response

this looks more like a fluent-bit issue. Please raise the issue there. https://github.com/fluent/fluent-bit/issues
It's possible that your fluent-bit pods are not running healthy at that time.

ok Thanks. The metrics buffer is not getting populated and the server sends a 404.  https://github.com/fluent/fluent-bit/blob/master/src/http_server/api/v2/metrics.c#L181

similar issue while using prometheus exporter https://github.com/fluent/fluent-bit/issues/9366


[release-1.26] [all] Add dulek and kayrus as approvers

Cherry pick of https://github.com/kubernetes/cloud-provider-openstack/pull/2318.
NONE

/lgtm
/approve


CombinedLoader takes a long time when num_workers > 0

Bug description
I am currently using CombinedLoader (https://lightning.ai/docs/pytorch/stable/api/lightning.pytorch.utilities.combined_loader.html#lightning.pytorch.utilities.combined_loader.CombinedLoader) to combine multiple datasets. It works fine but I noticed that setting the dataloader with num_workers > 0 causes it to run extremely slow. Is there a logical explanation for this? Feel like this could be a bug otherwise. I attached a chunk of my code to show what I am doing.
What version are you seeing the problem on?
v2.0
How to reproduce the bug
import pytorch_lightning as pl
from lightning.pytorch.utilities.combined_loader import CombinedLoader

class CollectiveDataloader(pl.LightningDataModule):
    def __init__(self, datasets, num_workers=8, batch_size=10, shuffle=True):
        super().__init__()
        self.train_set = CollectiveDataset(
            datasets, num_workers, batch_size, shuffle
        ).datasets

    def train_dataloader(self):
        return CombinedLoader(self.train_set, "sequential")

class CollectiveDataset:
    def __init__(self, datasets, num_workers, batch_size, shuffle):
        # datasets is a dictionary of {dataset_name : Dataset object}
        loaded_datasets = {
            name: DataLoader(
                dataset,
                batch_size=batch_size,
                shuffle=shuffle,
                ### SETTING THIS > 0 RUNS REALLY SLOW ###
                num_workers=num_workers,
            )
            for name, dataset in datasets.items()
        }
        self.datasets = loaded_datasets

Environment

Current environment
#- PyTorch Lightning Version: 2.0.7
#- PyTorch Version: 2.0.1
#- Python version: 3.10.12
#- OS: Linux
#- CUDA/cuDNN version: 12.0

cc @borda

Same issue here


(example): basic example via Xorm

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe): Example

What is the current behavior?
Issue Number:
What is the new behavior?
Other information

Codecov Report
Patch coverage has no change and project coverage change: -23.83 :warning:

Comparison is base (e663076) 65.02% compared to head (af64419) 41.20%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #752       +/-   ##
===========================================
- Coverage   65.02%   41.20%   -23.83%
===========================================
  Files         229      172       -57
  Lines       22698    18711     -3987
===========================================
- Hits        14759     7709     -7050
- Misses       7186    10670     +3484
+ Partials      753      332      -421

Flag
Coverage Δ

?

go-1.17.x
40.86% <ø> (-23.94%)
:arrow_down:

go-1.19.x
41.20% <ø> (-23.43%)
:arrow_down:

go-1.20.x
41.17% <ø> (-23.66%)
:arrow_down:

integration
?

macOS
?

ubuntu
41.14% <ø> (-0.07%)
:arrow_down:

unit
41.20% <ø> (-0.10%)
:arrow_down:

windows
41.17% <ø> (-0.06%)
:arrow_down:

ydb-22.5
?

ydb-23.1
?

ydb-23.2
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 172 files with indirect coverage changes

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


Button action vs link-to

Would it be desirable for the btn component to be able to transition to routes instead of utilizing its action?
Why? Actions are not SEO friendly. Convenience.
eg.
{{#md-btn action='link-to' actionArg='some.route' icon='fa fa-sign-in'}}go somewhere{{/md-btn}}

or
{{#md-btn linkTo='some.route' icon='fa fa-sign-in'}}go somewhere{{/md-btn}}

or possibly, which would do the action ping and then transition with a post model
{{#md-btn action='ping'  linkTo='some.route' linkToArgs='post' icon='fa fa-sign-in'}}go somewhere{{/md-btn}}

Just checking if that's doable without to much problems? Perhaps the md-btn could extend the link-to helper easely?

maybe we need a new component like {{md-btn-to}} or something? I'm a little wary of trying to make one component usable in too many ways.
What are your thoughts?

i agree, becomes complicated quickly

This is handled in #292


Unable to set WP standards along side Drupal standards

I am struggling to install both WP standards and Drupals (extracted from the Coder module)
They live in two different folders, so I am doing the following:
phpcs --config-set installed_paths ~/A_Folder/wpcs,~/Another_Folder/coder/coder_sniffer
When I do phpcs -i I get:

PHP Fatal error:  Uncaught UnexpectedValueException: DirectoryIterator::__construct(~/Another_Folder/coder/coder_sniffer): failed to open dir: No such file or directory in /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer.php:2250
Stack trace:
#0 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer.php(2250): DirectoryIterator->__construct('~/Another_Folder/code...')
#1 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(1404): PHP_CodeSniffer::getInstalledStandards()
#2 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(495): PHP_CodeSniffer_CLI->printInstalledStandards()
#3 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(468): PHP_CodeSniffer_CLI->processShortArgument('i', 0)
#4 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(403): PHP_CodeSniffer_CLI->setCommandLineValues(Array)
#5 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(911): PHP_CodeSniffer_CLI->getCommandLineValues()
#6 /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer/CLI.php(113 in /usr/local/Cellar/php71/7.1.8_20/lib/php/PHP/CodeSniffer.php on line 2250

I can set either individually, but not both!
I also can't seem ot set one, and then use phpcs --standard=path/to/standard path/to/file - it simply states the standard isn't installed.

That's a new one.
Ok, first off, before I can even begin to answer this, I need more information:

Am I correct in that you are using PHP 7.1.8 ?
What version of PHPCS are you using ?
What version of WPCS are you using ?
Where can I find a copy of the Drupal coding standard you are using to run some tests myself ?

Ok, so I've found the git repo for Coder, cloned it and added it to my installed_paths and phpcs -i works fine, both when using PHPCS 2.x as well as 3.x (both latest versions).
To run the Drupal standards, I switched PHPCS to 2.x as the Drupal standards are not compatible with PHPCS 3.x yet, ran both the Drupal standards against a random file and both work fine without any exceptions or fatal errors.
So...  please provide detailed steps on how to reproduce the error you are getting, as otherwise, there nothing I can do to help.

PHP 7.1.8, PHPCS 2.9.1, WPCS 0.13.1

Tried with that same combination, again working fine.
Without detailed steps to reproduce, there's nothing I can do.

Can you show how you added the two standards?

I cheated - I just edited the CodeSniffer.conf file in the root of my PHPCS install. I got quite a large number of standards installed, so manually typing all the paths in on the command line gets tiresome ;-)

@paulcanning Just checking - did you get it working ? And if so, how ? (for other people who come across the issue)

@jrfnl I have not looked at it since sorry, other things have taken priority. I might try going your route and editing the conf file. Could you provide an example of yours?

@paulcanning No worries, just checking.
This is what my CodeSniffer.conf file looks like (paths adjusted to protect the innocent - oh and based on Windows as you can see):
<?php
$phpCodeSnifferConfig = array (
  'installed_paths' => 'X:/path/to/PHPCS/WordPress,X:/path/to/PHPCS/PHPCompatibility,X:/path/to/PHPCS/QA-WP-Projects,X:/path/to/PHPCS/DrupalCoder/coder_sniffer',
  'report_width' => '90',
)
?>

@paulcanning Did you get this working ? Can the issue be closed ?


Fix for repo issue due to extra (/) slash

Fix for repo issue due to extra (/) slash
Signed-off-by: Rajan Mishra<EMAIL_ADDRESS>

I'm afraid that I don't fully understand this change. My understanding was that we'd prefer the following syntax:
{{ scale_install_repository_url }}/gpfs_rpms

Explanation: an extra slash / in a give path / URL shouldn't cause any harm. e.g. the following URL is still valid (just tested):
http://infraserv//gpfs_rpms

However, if users forget to add the slash / to the end of scale_install_repository_url then this would lead to invalid URLs. e.g. the following does NOT work:
http://infraservgpfs_rpms

Hence, my understanding is that we want to add an extra slash / every time we compute an URL based on scale_install_repository_url. This is documented in #242, which is on my list... Looks like this change here is now going in the opposite direction - can you elaborate?


Port #368 to release 8

Two remarks upfront:

There is a commit in the PR that shouldn't be there 360c77ce5ae989585addab940f1b7f8c9527f83e
I see that there is a Rebase release/6 commit, however the PR is against dev. Please clean that up (i.e squash the commit with the actual one) and target release/6 with the MR (the merge in dev would be something that will be done with a port-PR)
Thanks!

If you add Closes #XXX keywords to the description of the PR you should be able to link the dependabot PRs that are resolved by this PR (and close them directly) 😊

If you add Closes #XXX keywords to the description of the PR you should be able to link the dependabot PRs that are resolved by this PR (and close them directly) 😊

I could merge this and we trigger recheck


:memo: Docs: Update lots of jsdocs

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1446  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


docs introduce .github/CODEOWNERS for eclipse-tractusx/eclipse-tractusx.github.io

As this PR is not introduceing branch protection and required review count to the GH Org but to the eclipse-tractusx/eclipse-tractusx.github.io repo only, I would like to require 2 reviewers. For this repository enough stakeholders should be available doing reviews.
Maybe we should also think about to introcude .github/CODEOWNERS (for eclipse-tractusx/eclipse-tractusx.github.io). Code owners are automatically assigned to new PRs:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
Originally posted by @carslen in https://github.com/eclipse-tractusx/.eclipsefdn/pull/43#discussion_r1410429486

IMHO, CODEOWNERS won't add a lot of value or improvement to our current collaboration workflow.
Currently it is as follows:

Everyone can open a PR (contribute)
Before being able to merge, TWO approvals from reviewers are required
The approvals have to be given by people with the committer role
Only committers can merge an approved PR

Potential things a CODEOWNERS file could be used for:

Path specific permissions (i.e. /docs/release or KITs)
Auto-Assign reviewers on new PRs

Things that we are limited in my opinion:

We do only have a committer group, so assigning permissions on group level might be difficult (individual assignments would be needed i guess)

I would vote for a CODEOWNERS file. Especially for the KITs, there are some specific persons and responsibilities.
If someone creates a PR or an Issue for your KIT, you as a KIT developer don't get information that someone wants to change your KIT. You could subscribe to the repository, but in this case, you get notifications for every PR and Issue. Thus, a CODEOWNERS file would be beneficial.

I think CODEOWNERS could help on the margins but I don't expect any big changes for the challenges we have. Would be open for a PR (and to be responsible for the DT Kit) though.

will close this issue but the general idea seems still valid at least from my perspective.


Changelog

Hello,
Do you have a wiki page or similar with versioned changes documented? I just need to know the differences between Meshblu server's versions, but I can't seem to find it...
Thanks in advance!

+1, I'm using an older version and would like to be able to understand what has changed.

+1

+1

+1

+1

We don't currently. We can do a much better job of this. Frankly, it was so quiet I didn't think anyone cared.
We are also working on Meshblu 2.0 with a cleaner and more scalable architecture. I'll do some write ups on that as well.

Thanks @iamruinous for your comment!
We're using Meshblu on a large-scale project, for Smart Cities, and we've noticed that our instance's performance decreases after processing thousands of events. Since we're using one of the earliest versions, we need to plan the update procedure quite thoroughly.
We've tried to use the latest version but, for example, it's no longer possible to send the device UUID as a parameter when registering a device. Therefore, we need a detailed changelog with all the version changes.
We're also very curious about the 2.0 version! ;)

@rjfv I have been working with keeping up with Meshblu changes for +12 months now.  And depending on how you have implemented and what behavior assumptions you are depending upon, you could have many issues when you approach upgrading.
During my time there have been significant changes that we have had to accommodate. Device registration is one of the smaller ones, the change in the message security model is the big one that I anticipate you will hit first.

Thanks @brianehlert! Those are the sort of things I need to know in order to estimate correctly!

@rjfv unfortunately you'll have to look through the commit log if you want a detailed list of changes.
We have overcome many scaling issues with Meshblu and I'm happy to help you in any way that I can. Like @brianehlert a lot will depend on how you are using it. We have a gitter channel if you want to chat over there https://gitter.im/octoblu/meshblu.

As @iamruinous mentioned, you can chat with the team directly on Gitter.  And I am open to answering questions directly if you want to message me as well.

One of the things I'm considering at the moment is to disable the use of data.db and events.db databases, @iamruinous @brianehlert, is that a simple way to do that and avoid ruining everything in Meshblu? :)

@rjfv I would love to learn more about your smart city project and Meshblu's role in it!  Can you hit me up on email<EMAIL_ADDRESS>

@rjfv BTW, we have been thinking about deprecating the data and events APIs.
Data may still exist but we would route its data through the data forwarders to your own data store rather than ours.
Events was implemented before our pubsub capabilities.  We're not aware of anyone still using these endpoints...
We would love to get your feedback.

I've started to document Meshblu 2.0 in the wiki, there is still a long ways to go, but feedback is welcome.
https://github.com/octoblu/meshblu/wiki/Overview

Thank you both @iamruinous and @chrismatthieu and sorry for the late reply! I'll write you with a bit more details and some feedback on your solution, please keep up the good work!
Happy holidays :)


Mute error messages - ETIMEDOUT

I'm having a problem with ETIMEDOUT on slack messages. I know its probably my connection with binance api but bot works just fine.
The question- Is there a way to turn off error messages? I would like to recive messages on open orders or closed orders etc. For now using slack with flodge of errors is just pointless.
Moving app to different location/cloud is not a solution for me.

Hmm, right.
Currently, don't have a config for that, but I will add in.

Thank you


Install the MultiApps Cloud Foundry CLI Plugin

Tutorial URL: https://developers.sap.com/tutorials/cp-cf-install-cliplugin-mta.html
Please specify the step you are referring to
STEP 3:
PS C:\WINDOWS\system32> cf install-plugin multiapps
Searching CF-Community for plugin multiapps...
Plugin multiapps 2.4.1 found in: CF-Community
Attention: Plugins are binaries written by potentially untrusted authors.
Install and use plugins at your own risk.
cf : The handle is invalid.
En línea: 1 Carácter: 1

cf install-plugin multiapps

  + CategoryInfo          : NotSpecified: (The handle is invalid.:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

FAILED
PS C:\WINDOWS\system32>

I haven't seen this error before. Are you using the most recent version of the CF tool? Are you able to install other plugins like cf install-plugin -r CF-Community "html5-plugin"

Seems like this issue is not active anymore, please reopen if needed.


Refactor some registry client and auth code

Adds NewClient() method to registry.Endpoint objects to make it much
simpler to create and use a http client for the registry package.
Switched registry.Session to use a single http client for reuse and
connection pooling.
Refactored the newClient() logic which configured custom server and
client certs for registry endpoints.
Updated registry package unit tests to use two different HTTP test servers,
one with a valid certificate configured by the test and another without.
Added checks to ensure that the registry session DOES NOT send auth
credentials over an insecure connection.
Docker-DCO-1.1-Signed-off-by: Josh Hawn<EMAIL_ADDRESS>(github: jlhawn)

ping @tiborvass @dmcgowan

I also tried some refactoring at https://github.com/tiborvass/docker/compare/docker:master...fix-login-secure-registry, and the biggest problem is that you need the request object to check if you are able to send creds securely (https://github.com/tiborvass/docker/compare/docker:master...fix-login-secure-registry#diff-7025b8c38be826dd40b8f9f14310b7c1R75)
Another thing to keep in mind, is that we actually do want to create a client almost every single time, so that new certs get caught in /etc/docker. An improvement would be to reuse the same client for each registry command exposed by the API. A major improvement would be to use http://godoc.org/github.com/howeyc/fsnotify and watch the /etc/docker/certs.d subtree.

@tiborvass I've tried to address the points you brought up in the latest update.

the biggest problem is that you need the request object to check if you are able to send creds securely

This change makes any registry session instance use a custom http client wrapper which knows whether InsecureSkipVerify is true or not and checks for an Authorization header before making any requests. If the request is found to be insecure, then it refuses to make the request with any non-empty value for the Authorization header.

Another thing to keep in mind, is that we actually do want to create a client almost every single time, so that new certs get caught in /etc/docker. An improvement would be to reuse the same client for each registry command exposed by the API.

This change makes it so that each call to registry.NewSession() gets a new client instance that is used for the remainder of the session.

A major improvement would be to use http://godoc.org/github.com/howeyc/fsnotify and watch the /etc/docker/certs.d subtree.

It looks like we already vendor go-fsnotify which is awesome! I've updated this patch to use this for setting up a global CA Pool and set of client certificates. I've also added some unit tests for this and made some other improvements to the registry package unit tests in general.

Since this has refactoring and new features from your PR description Added checks to ensure that the registry session DOES NOT send auth credentials over an insecure connection.  I would suggest breaking this PR up and if you want to do the refactor work, do that first and get it merged in before changing the functionality.
Please break this PR up and reopen when you are ready for review if you still want to add these changes.  This helps the diff to be smaller, making it easier to review, and we can focus on the added feature or the refactoring and not both at the same time.

@crosbymichael thanks, I think I can add the registry client refactor, certs dir watching, and unsafe auth header each as separate PRs, in that order.


Support serverId defined in settings.xml

At the moment usename and password needs to be provided in pom.xml or read from properties. In addition it should be possible to provide a server reference specified in the settings.xml.
pom.xml
  <configuration>
        ...
        <serverId>myServerId</serverId>
       ....
 </configuration>

settings.xml
<settings>
...
  <servers>
...
    <server>
      <id>myServerId</id>
      <username>myusername</username>
      <password>myEncryptedPassword</password>
    </server>
...
  </servers>
...
</settings>

@cstettler is there a chance to get the PR merged? Or do you need more information? Would be really helpful to have this feature. Thanks.

Hi @jomu78, sorry for the delay. I will have a look at your contribution today.

Hi @jomu78, I added some integration tests for reading credentials (plain text or encrypted) from settings.xml and merged the pull request. The feature is available on the latest 0.0.0-SNAPSHOT build and will be part of the next release. Thank you again for your work!

@cstettler : do you already have an idea when the next version including this feature will be released?

Hi @jomu78, this feature is now part of version 0.11.0 released just a few minutes ago. Thank you for your patience.


[core] Get data from nodes table

fixes: https://github.com/dust-tt/dust/issues/8516
fixes: https://github.com/dust-tt/dust/issues/8519
Description
Join with nodes tables to fetch mimetype and title when querying documents or tables.
If entries are missing in nodes tables, fallback to the default values.
Risk
Issues on document/table read, can be rolled back.
This includes listing / searching nodes in data source, but also query-less retrieval action ( "include" )
Deploy Plan
deploy core

LGTM modulo the typing topic, thanks 🙏 Also, the cards marked fixed indicated that parents[] were to be read in data_source_nodes by the PR so this is why the backfills were required here We can move forward but can you keep in mind to update the code once the backfills are done?

yes I was planning to do that after the backfill - but this can be done here if we wait for the backfill to be done before  merging , as originally planned

LGTM modulo the typing topic, thanks 🙏 Also, the cards marked fixed indicated that parents[] were to be read in data_source_nodes by the PR so this is why the backfills were required here We can move forward but can you keep in mind to update the code once the backfills are done?

yes I was planning to do that after the backfill - but this can be done here if we wait for the backfill to be done before merging , as originally planned

I updated to read the parents from nodes table. All documents and tables must be backfilled and have an entry in nodes. Now using inner join instead of outer join, and always upsert to nodes table.

Risk should be updated to include: "all query-less retrieval actions (include)"

Backfill is done so this one is ready to be merged.
We're still upserting parents in the 2 tables, in case something goes wrong and that we need to revert.


path argument with default value wrongly interpreted as aparameter type body

WCF supports defining optional path variables (i.e. path variable with an optional argument), however this appears to be incorrectly interpreted as a 'body' parameter type instead of an optional 'path' parameter type.  Also, the generated URL is incorrect.
MSDN refrence.. https://msdn.microsoft.com/en-us/library/bb675245(v=vs.110).aspx
Example..
        [WebGet(UriTemplate = "/race/{raceKey}/silks/{acceptorKey=null}?width={width}&height={height}", ResponseFormat = WebMessageFormat.Json)]
        Task<Stream> GetRaceSilks(string raceKey, string acceptorKey = null, string width = null, string height = null);

Issues marked in red..

wrong parameter type.  should be type=path and string
wrong generated url.  should be http://localhost:30295/racing/race/1/silks?width=3&height=4 or http://localhost:30295/racing/race/1/silks/null?width=3&height=4

added some changes to make sure parameter shows with correct type
I decided to remove the default value from the URL as I don't see from the swagger spec how to do it
let me know your thoughts on this

assuming it's fixed... please reopen if you have any issue


Why should num_shard be a fraction of the shape of model?

I want to use polyglot-ko-12.8b (https://huggingface.co/EleutherAI/polyglot-ko-12.8b) with num_shard=2.
AutoModelForCasualLM.from_pretrained('model-path', device_map='auto') break it up into almost half and correctly loads the model onto 2 GPUs (2x RTX 4090).
But in TGI, AssertionError: The choosen size 30003 is not compatible with sharding on 2 shards (".../text_generation_server/utils/weights.py", line 77)
What is the difference between them?
Why should num_shard be a fraction of the shape of model?

Have you figured it out ?


Cats Effect 3 support

It would be great to have a version of this library supporting CE3

PRs welcome! :)

Any updates will be appreciated, now that there's a PR out 🙂

Version 0.16.0 with CE3 support is out now!


How to run epfviewer Can you upload photos or videos?

help me,,
https://github.com/DizzyThermal/TKViewer/issues/30

Instructions are in the README to this repo. If you don't know what Godot is, there are plenty of YouTube tutorials you can watch to learn.

--- Debugging process stopped ---
how to run?


Steelseries Sensei 310 brightness not supported

I believe this mouse should support brightness settings for led as previous versions of this mouse (for example steelseries sensei raw), but it reports it's not supported.
ratbagctl "SteelSeries SteelSeries Sensei 310 eSports Mouse" led 0 capabilities
Modes: breathing, cycle, off, on
It would be nice to have the led on but with lower brightness.

It does support brightness, black is 0 brightness, white is 100% brightness. It's the same implementation as the official software.


Error while loading sharded meshes

Hello,
I have noticed an error in the web console that I can barely debug, for which I need a bit of help with.
Because we have a big data set, we have sharded (draco compressed) the data, in order to be fed to Neuroglancer. Some cell meshes still exceed a certain size and need to have a truncated requests/responses. I have noticed some of these meshes end up in an error in the console:

Their data is being fetched by Neuroglancer.
First request:

Second request:

But the mesh is not shown in the Viewer. I have tried to debug the chunk manager, but I had no luck. Also, the shard files seem to work, as I've loaded the problematic meshes with cloud-volume.
Do you have any idea where I could start debugging?
Best,
Andrei Mancu

proc_exit 1 indicates an unexpected error decoding the mesh, but I will have to investigate more what the issue is.

@Mencu Running into the same issue with large draco mesh shards, did you ever figure this one out? CloudVolume/DracoPy is decoding the mesh just fine - 16,128,411 vertices, 31,662,220 faces, 0 vertex normals.


on macos sometimes current tab is used for chat

this bug is similar to bug in cuda_hotspots: https://github.com/veksha/cuda_hotspots/issues/22
because we use ed.cmd(cmds.cmd_FileNew) and we assume that we now can use ed var that will point to new tab editor, but this is not always the case on macOS.
fixed. (workaround)
@Alexey-T, can you update cuda_codeium in addon manager, please?

updated: Codeium, Hotspots.


X-Forwarded-Proto

For a SSL request, Glimpse accurately injects a https request to its injection script.
However, if a load balancer terminates a SSL request, thereby having the local IIS receive a normal HTTP request, there is no manner in which to force Glimpse to request its injection script via https. Consequently, it's injection script fails from the client browser due to it being request in an insecure manner.
There should be either one of two mechanisms:

Inspect for X-Forwarded-Proto which many clouds use to indicate a terminated SSL request.
Add a setting to the Glimpse configuration to force HTTPs request for the injection script.

Shifted this to the task list. Will track from there.


Add Math ops to TTNN

Is your feature request related to a problem? Please describe.
We need a new operation to perform math functions on two input tensors similar to what was implemented in torch.
ex. hypot, lerp, atan2
Following are the ops needed
atan2, hypot, lerp, squared_difference, isclose
Describe the solution you'd like
This will apply math function on the two input tensors and return one output tensor
Describe alternatives you've considered
It's possible that ttnn tensors could be converted to a Pytorch tensors and then apply math operations with Pytorch function. The result would then be returned using ttnn.from_torch operation.
Additional context
The reference implementation of a binary math function.
import torch

tensor1 = torch.tensor([4.0, 9.0, 7.0])
tensor2 = torch.tensor([1.0, 2.0, 3.0])

result_tensor = torch.hypot(tensor1, tensor2)
print(result_tensor)

merged to main #5465


Add pr labeler workflow

Copied from https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/workflows/label-prs.yml (cc @pichlermarc) to enable auto-labeling of PRs additionally.

Nice! Could we also add a label for code related work (CSS, templates, etc.)?

probably yes, I have not looked into all the details but we can start with the labeling for SIGs and then work from there


Rotate Matrix using c++

Problem statement : Given a matrix, clockwise rotate elements in it.
Probelm Link : https://www.geeksforgeeks.org/rotate-matrix-elements/
Choose one Cateorgy - Very Easy, Easy, Medium, Hard, Very Hard, Expert
question category : Easy

Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py
[ ]  Choose label for Problem , example- "good first issue", "easy"
[ ]  In file there should be problem statement and link to problem

/* Problem-Task : This program will add two numbers
 * Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Please assign to me

please assign me this ! thanks

Please assign this issue to me.


WIP: Add sorting functions

Incomplete.
This is missing documentation and tests.
@iwburns What do you think about this implementation?

Changes discussed in https://github.com/iwburns/id-tree/issues/3#issuecomment-267186883 are added via ca5aac3

Alright, I like this solution very much!  Good call on using mem::swap!
This is just a nitpick (and it's partially targeted at myself), but how do you feel about the name sort_children_by_data?  I just named it that earlier because I was in a hurry and it sounded alright, but now I'm thinking sort_children would be better since it follows the pattern here a bit better with sort, sort_by_key, and sort_by.
What do you think?

I actually had(!) this function named sort_children at first.
But I felt, that this would not make absolutely clear what key we are sorting.
NodeIds / Indices? Oldest Node first? data()?
I think sort_children_by_data is a little bit more declarative, if you encounter it in the code, but I have no strong feelings about this. sort_children is also perfectly fine, just not my personal preference.

Yeah, those are fair points.
Let's keep it as sort_children_by_data then.  I think that's clearer as well.

Added some documentation with tests.
Is this sufficient, or do you want failure tests for the sorting functions as well?

If you don't mind adding the failure tests as well I would appreciate it.
Otherwise, this looks great to me!

Sure thing

Rebased and tests added.

@Drakulix v0.2.7 is up on crates.io


Large file downloads using _stream_to_file are slow

Problem
Our Python code for downloading files from Walden does not seem capable of saturating the internet connection.
On my local machine and network:

walden.files.download(): 0.5M/s
wget: 21.5M/s

Impact
To build garden involves downloading >5G of data. The biggest files are probably the Hyde baseline, and perhaps WPP. This makes it much slower for a cold ETL to run for the first time and rebuild everything. Fortunately we don't do this very often, so it's more a quality-of-life thing than a major blocker.
Possible solutions

Use wget instead via sh module (but... does it still work ok on WSL?)

In this piece of code
https://github.com/owid/walden/blob/6227cf89f8c9740e99e2fc8861ff5219edc29c14/owid/walden/files.py#L62-L66
the md5.update() call seems to be slowing things down by a bit. We could potentially increase download speeds by using a larger chunk size.

Ah, interesting. It doesn't seem to be CPU-bound. I also seem to be getting a widely varying data rate.

I agree that changing the chunk size is the most obvious thing to try first.

It varies a lot for me too, but it's always at least >3M/s which is ok (usually it's in the 5-10M/s range).

I tried upping the chunk size from 16k to 1M, it didn't have much effect at all.


Directory reorganization

Re-organize files based on the module system:
src -> es6
dist -> amd

Implemented in f006d3fc3c67f9362dda8853b245cf75f333d540


DiagnosticFeature not working after upgrade

Hey again,
We recently upgraded the monaco-languageclient package from version 4.0.3 to version 6.3.0-next.2, & since then the LSP DiagnosticFeature stopped working.
After spending some time on trying to understand the source of the issue, i noticed that it was due to some vscode api changes, i'll try to explain my conclusions below:

The vscode/dist/api.js file has considerably changed & more exactly the tabs getter which has been moved to a separate file, below the old implementation:

& here is the new one, which is now located at vscode/dist/vscode/vs/workbench/api/common/extHostEditorTabs.js:

As a result to the above change(s), the tabs property is now always empty even when having opened monaco editor tabs:

The diagnostic feature does verify if the current TextDocument matches with a visible tab & since the tabs list is always empty in our case the check always fails & the diagnostic requests are not sent to the LSP server:

I think that providing a way to override the tabs getter would fix the issue, still i'm not sure if that's doable on this package side or on the vscode api side, what do you think @kaisalmen ?

Edit: I tried to modified the vscode api from the node_modules but it still didn't work, i'm unable to get the models:

@kaisalmen @CGNonofr Any help on this please?

Thanks for the investigation, I will have a look at it!

The issue is still persisting in<EMAIL_ADDRESS>

I'm... confused ! Are you sure there is no cache issue? Do you use the editor service override or the views?

I completely deleted the node_modules folder & the package-lock.json file & reinstalled all the dependencies.
Yes, i'm using the codeEditorService override to register a custom open handler:

Also, i'm using react & @monaco-editor/react to create my editors.

Ok. For it to work you need to use either the editor service override or the views service override

@CGNonofr I'm not sure if i get you well, do i need to override a specific function of the editor service? maybe the getEditors callback?

I'm not sure to understand your screenshots either
What does that mean to override by something from StandaloneServices which mean the services are already initialized?
I was talking about using vscode/service-override/editor or vscode/service-override/views

@CGNonofr Nevermind, i think that i get you now, actually i just needed to add the following config:

The diagnostics works now! Thanks a lot & sorry for the confusion :pray: .

You probably shouldn't use the view service except if you need it as it pulls a lot of code, but the editor service instead

Alright, thanks again of the fix!

@AXeL-dev I need to release a new version of monaco-languageclient (probably 6.4.6) that contains the latest version (1.81.7 once it is available).


Scene lighting support?

Are there any plans to release a new version of the library to pub.dev with lighting support available?
I would like to use it in my project but the latest published package version (0.0.5) does not include it yet, though it is in the master branch of the repository.

0.0.6 has been published to pub.dev

Thank you for updating the package!
Much appreciated for all the work you've put into this library 🙂


Client-side service Rust SDK

The idea is that client-side services should be written in systems languages and compiled to wasm for execution in the browser, rather than written in pure javascript. It should be the responsibility of the backend service developer to write the security-conscious code that interfaces directly with the service, rather than a front-end developer who is not used to dealing with security-critical infrastructure.
SDKs can be provided such that it becomes trivial for back-end developers to write "actions" that are executed on the client-side, are given client-side context details (url information, client-side state, etc.) and which can themselves call actions on their own services, or call other client-side actions defined in other applications.
Also as part of this SDK there must be a js library which can provide imports for front-ends to call into the client-side services to execute the operations.
For example, imagine that a service action requires a user to first credit 10 tokens to the service, then call an action on it. The service developer should define a simple client-side action that calls tokensys::credit with the appropriate amounts, followed by calling their application service action. If done correctly, front-end application developers should be able to easily import a javascript library function and simply call one client-side action that facilitates sending the sequence of actions (tokensys::credit + service:action) from the currently logged-in-user automatically.

Subsumed by plugin infra


Make running pycodestyle slightly more ergonomic.

The same change was made to the pylint script a while back.

Pull Request Test Coverage Report for Build 1904

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

Totals

Change from base Build 1877:
0.0%

Covered Lines:
2070

Relevant Lines:
3850

💛  - Coveralls

@zenhack I can merge this as soon as it gets a rebase

Done.