digital state read to test for If or While loop

This issue has been tested using the target Micro:bit in Make Code
https://makecode.microbit.org/
Currently, in Blocks, a user cannot add a digital state read to the test for if or while loop. You can find a picture of the attempt to place Digital State Read for If. Here is example code in JavaScript below:

basic.forever(() => {
    if (true) {
        music.beginMelody(music.builtInMelody(Melodies.Dadadadum), MelodyOptions.Once)
    }
})

Using Blocks, it appears a user can add a digital state read to test for if or while loop. So you can find a logic fix that was tried using Digital Read Pin. However, this attempt was not successful on the physical device. You can find the JavaScript below:

basic.forever(() => {
    if (pins.digitalReadPin(DigitalPin.P1) == 0) {
        music.beginMelody(music.builtInMelody(Melodies.Dadadadum), MelodyOptions.Once)
    }
})

It appears that the only way to resolve this logic issue (Digital State Read to test for If or While loop) is with a more complicated implementation using Blocks. You can find the fix below:

control.onEvent(EventBusSource.MICROBIT_ID_IO_P1, EventBusValue.MICROBIT_BUTTON_EVT_UP, () => {
    music.beginMelody(music.builtInMelody(Melodies.Dadadadum), MelodyOptions.Once)
})

Can you implement digital state read to test for If or While loop?

Issue discovered by Richard Albritton

I think we should remove the check on if/else and while blocks or at least let numbers and strings be dragged in. My only concern is that it might be weird with Scratch blocks, where different types are different shapes.

@Riknoll, so will the digital read pin return to a string and not an int or bool? If so, that should probably be what changes. The only possible outcomes from a digital read will be 1 or 0 and that should resolve as True or False in the test.
If the currant test looks for an int, making digital read pin return as an int should fix it unless there is a reason digital read pin needs to return another data type.

@Richard1 I'm not suggesting that we change the digital read API, it will still return a number. I'm just suggesting that we change the if/else and while blocks so that you can drag numbers and strings into them without them bouncing out (the current behavior only let's you drag in variables and booleans)

Ah, so if we first assigned the digital read pin to a variable, then added that variable to the test, would that work?
Is there a reason why digital read pin it not returning a boolean?

Is there a reason why digital read pin it not returning a boolean?

Mostly historical and backward compat reasons.


Improve ddev config --web-working-dir and friends.

Describe the bug
ddev config --web-working-dir=junk is not a valid command (because working dir must be rooted full path in container).

Sadly, ddev config --web-working-dir=/var/www/html/junk doesn't work either, because it uses filepath.Join() to create a windows path so you end up with the evil

working_dir:
  web: C:/Program Files/Git/var/www/html/junk

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version and configuration information (please complete the following information):

Host computer OS and Version: [e.g. Windows 10, macOS High Sierra]
Docker version information (use docker version) and insert it here.
ddev version information (use ddev version)
config.yaml contents for the misbehaving project
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?

Additional context
Add any other context about the problem here. Thanks!

Closing as it is not likely to get love after all this time.


Revert encoding update

Current coverage is 64.60% (diff: 100%)

Merging #451 into master will decrease coverage by 0.16%

@@             master       #451   diff @@
==========================================
  Files            45         44     -1
  Lines          1978       1969     -9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1281       1272     -9
  Misses          568        568
  Partials        129        129

Powered by Codecov. Last update b58f7f5...04a1364


How to get the previous and the next message??

I have an specific message, so I want to know the id of the previous and the next message..

Hi @familiaorlando100 ,
I'm not sure what you are asking. Are you looking for a threaded conversation?
If so, you can try something like this:
/** @var \Webklex\PHPIMAP\Message $message */
/** @var \Webklex\PHPIMAP\Support\MessageCollection $messages */

$messages = $message->thread($sent_folder = null);

Please visit https://www.php-imap.com/api/message for some additional documentation..
Best regards,

Nope… I would refer when you get the list of messages and see the information of a specific message to get the message received before that message. For example: In the image If I click on the message  :
Inkpact  how to get  the MESSAGE ID of  the New York Times and Stephanie at Copy blo

Ah I see,
you can use the UID or SequenceID (depending on your configuration: https://github.com/Webklex/php-imap/blob/master/src/config/imap.php#L147).
For example:
/** @var \Webklex\PHPIMAP\Message $message */
/** @var \Webklex\PHPIMAP\Folder $folder */

$other_message = $folder->query()->getMessageByMsgn($message->getMsgn() + 1)
$other_message = $folder->query()->getMessageByUid($message->getUid() + 1)

However you should also surround either of these operations with a try catch block, since you don't know if the message exists. Increasing / Decreasing the  UID or SequenceID could fail if any of those has changed during the session or simply doesn't exist in the first place.
I would suggest to use the email date instead and work with a range.. But this would also come with some implications as well. I guess it depends on the actual use case and using UID or SequenceID might works just fine :)
Best regards & happy coding,

Thank you for your answer! How can I verify if the message exists through the UID

You're welcome :)
There is no method to test if a message exists. But like I mentioned above, you can utilize a try catch block:
try {
    /** @var \Webklex\PHPIMAP\Folder $folder */
    /** @var \Webklex\PHPIMAP\Message $message */
    $other_message = $folder->query()->getMessageByUid($message->getUid() + 1);
} catch (\Webklex\PHPIMAP\Exceptions\MessageNotFoundException $e) {
    // Message doesn't exist
}

Best regards,


An already freed Object evaluates to true when used as a condition in if

Godot version:
3.2.4 beta 4
OS/device including version:
Windows 7
Issue description:
Godot sends an error even when I make precaution that target doesn't Null.
 First missile crashes the target and target is queue_freed. Because of that other missiles receive null, but I got an error.
Steps to reproduce:
Minimal reproduction project:

@rakun99 Please upload a minimal reproduction project to make this easier to troubleshoot.

@rakun99 Please upload a minimal reproduction project to make this easier to troubleshoot.

You are supposed to use is_instance_valid() to avoid this error. So it should be either
if is_instance_valid(target):
    stuff

or
if not is_instance_valid(target):
    target = null

if target:
    stuff

That said, this error used to report [deleted object] instead of null. Not sure if the new behavior is intended.

You are supposed to use is_instance_valid() to avoid this error. So it should be either
if is_instance_valid(target):
    stuff

or
if not is_instance_valid(target):
    target = null

if target:
    stuff

That said, this error used to report [deleted object] instead of null. Not sure if the new behavior is intended.

IIRC is_instance_valid() can be a fake positive too, so it isn't a fix...

IIRC is_instance_valid() can be a fake positive too, so it isn't a fix...

No, fake positives were fixed in the newest 3.2 releases.

No, fake positives were fixed in the newest 3.2 releases.

@rakun99 Please upload a minimal reproduction project to make this easier to troubleshoot.

Well, I used a steering behavior form KidsCanCode demo.

You are supposed to use is_instance_valid() to avoid this error. So it should be either

Wow, it worked. Thanks. So problem is solved.

@rakun99 Please upload a minimal reproduction project to make this easier to troubleshoot.

Well, I used a steering behavior form KidsCanCode demo.

You are supposed to use is_instance_valid() to avoid this error. So it should be either

Wow, it worked. Thanks. So problem is solved.

The same in v4.0.beta10.official [d0398f62f]:

Related: #59816.
It's GDScript specific issue, right? :thinking:

@kleonc The screenshot you posted looks correct. The error reports the object as 'previously freed'.

@kleonc The screenshot you posted looks correct. The error reports the object as 'previously freed'.

Oh, so the only issue in here is the error message saying "null instance" instead of something like "previously freed"?

Well, the behavior is unintuitive, but the idea is that you have to use is_instance_valid() to make sure whether the object is freed or not. I think the fact that checking the object directly is inconsistent is due to performance reasons.

This is not a bug and from the discussion on #59816, it is expected behavior that if freed_object: evaluates to true. In general you should check why you are getting a freed object and if it is expected you should use is_instance_valid().


Add SourceClear [#72]

Add enable line to Travis YAML
to verify look for a new PR check

Coverage remained the same at 92.823% when pulling ec9a5f97a02f38bca0b606d72259e3c4ba3675b3 on sourceclear into 4044182f089c37dc4d61f57aa9cb65838e6943e9 on master.

Coverage remained the same at 92.823% when pulling ec9a5f97a02f38bca0b606d72259e3c4ba3675b3 on sourceclear into 4044182f089c37dc4d61f57aa9cb65838e6943e9 on master.

Coverage remained the same at 92.823% when pulling ec9a5f97a02f38bca0b606d72259e3c4ba3675b3 on sourceclear into 4044182f089c37dc4d61f57aa9cb65838e6943e9 on master.

Coverage remained the same at 92.823% when pulling 15dc85ff995a9ea504a5df5deacd1c325cd296bb on sourceclear into 4044182f089c37dc4d61f57aa9cb65838e6943e9 on master.


Add Swift Package Manager Support for Xcode 11

Checklist for this pull request

[x] I have read the guidelines for contributing.
[x] I have updated README.md, describing the new feature I'm adding (if applicable).
[x] I have checked that my code additions did fail neither code linting checks nor unit/UI test.

Description
Updates Package.swift in order to work as a iOS dependency via SPM in Xcode 11

Thanks a lot for the PR @netspencer!
I have a couple of questions:

Does the package manager support resources now? Are xcassets bundles correctly imported?
Is it compulsory to remove the license header from Package.swift, for swift-tools-version:5.1 to be picked up?

@netspencer what is the status of this feature? It would be absolutely great to have it in the project.

@hodovani i need to just address the questions above and make a change or two and then i believe it would be eligible to be merged in


Fix: Font size picker calls on change on each rerender.

Currently, the FontSizePicker component makes an onChange call each time the component is rerendered.
The story I'm adding shows the issue in action.
This PR fixes the issue by making sure we are not generating new options on each rerender.
This PR fixes part of the end to end tests failures on https://github.com/WordPress/gutenberg/pull/27594.
Currently each time a block rerenders, the font size picker rerenders, and then we dispatch update block attribute actions.
I think that we also have an issue on the SelectDropdown component  (it is the one throwing onChange calls), but I did not manage to replicate this issue using that component in isolation after multiple tries where on each rerender I passed different objects.
I verified using the developer tools and the story I proposed that on each rerender we are not making on Change calls.

Haii! I made an update in this PR for the duplicate SelectDropdown callback:
https://github.com/ItsJonQ/g2/pull/206
Would you be able to verify if it resolves the issue?

Haii! I made an update in this PR for the duplicate SelectDropdown callback:
https://github.com/ItsJonQ/g2/pull/206
Would you be able to verify if it resolves the issue?

Hi @ItsJonQ,
The issue is still present,
I included a user story to test the issue http://localhost:6006/?path=/story/components-fontsizecontrol--periodic-rerender.
If we revert:
packages/components/src/font-size-control/font-size-control-utils.js
packages/components/src/font-size-control/use-font-size-control.js
And just keep the story. We can see on the console that on each rerender on change is being called. So I guess we still need to merge this fix.
Regarding the select dropdown double callback, I think we still have part of the issue, on the same storybook during the first change from default to another value the double callback still happens. But now it is only the first time, in the changes after it does not happen.

Hi @ItsJonQ,
The issue is still present,
I included a user story to test the issue http://localhost:6006/?path=/story/components-fontsizecontrol--periodic-rerender.
If we revert:
packages/components/src/font-size-control/font-size-control-utils.js
packages/components/src/font-size-control/use-font-size-control.js
And just keep the story. We can see on the console that on each rerender on change is being called. So I guess we still need to merge this fix.
Regarding the select dropdown double callback, I think we still have part of the issue, on the same storybook during the first change from default to another value the double callback still happens. But now it is only the first time, in the changes after it does not happen.

@jorgefilipecosta Thanks for catching this 🙏 .
I was able to identify the issue in SelectDropdown, specifically in the part where it syncs props and state value:
	// Sync incoming value.
	useUpdateEffect(() => {
		if (
			!store.getState().isOpen
		) {
			store.getState().setCommitValue(value);
		}
	}, [value, store]);

I think FontSizeControl is passing in a new object (value) into SelectDropdown. This is because FontSizeControl remaps its options in getSelectOptions.
Although the shape of the value is identical, it fails the useEffect check because it's a new object.
The solution was to add an equality check in the if statement:
	useUpdateEffect(() => {
		if (
			!store.getState().isOpen &&
			!simpleEqual(store.getState().commitValue, value)
		) {
			store.getState().setCommitValue(value);
		}
	}, [value, store]);

I think we can keep your memoized options update for extra safety.

I'm going to look adjusted getSelectOptions so that new objects aren't created every time

@jorgefilipecosta Thanks for catching this 🙏 .
I was able to identify the issue in SelectDropdown, specifically in the part where it syncs props and state value:
	// Sync incoming value.
	useUpdateEffect(() => {
		if (
			!store.getState().isOpen
		) {
			store.getState().setCommitValue(value);
		}
	}, [value, store]);

I think FontSizeControl is passing in a new object (value) into SelectDropdown. This is because FontSizeControl remaps its options in getSelectOptions.
Although the shape of the value is identical, it fails the useEffect check because it's a new object.
The solution was to add an equality check in the if statement:
	useUpdateEffect(() => {
		if (
			!store.getState().isOpen &&
			!simpleEqual(store.getState().commitValue, value)
		) {
			store.getState().setCommitValue(value);
		}
	}, [value, store]);

I think we can keep your memoized options update for extra safety.

I'm going to look adjusted getSelectOptions so that new objects aren't created every time

Update! Spreading the option in the options.map of getSelectOptions() helped!
	return options.map((option) => {
		const fontSize = is.number(option.size)
			? createUnitValue(option.size, 'px')
			: option.size;

		return {
			...option,
			key: option.slug,
			style: {
				fontSize: `min( ${fontSize}, ${MAX_FONT_SIZE_DISPLAY} )`,
			},
		};
	});

Update! Spreading the option in the options.map of getSelectOptions() helped!
	return options.map((option) => {
		const fontSize = is.number(option.size)
			? createUnitValue(option.size, 'px')
			: option.size;

		return {
			...option,
			key: option.slug,
			style: {
				fontSize: `min( ${fontSize}, ${MAX_FONT_SIZE_DISPLAY} )`,
			},
		};
	});


Update backup-dpm-automation.md

Correct some minor errors mentioned by customers.

Hi @AnuragMehrotra, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (anuragm). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Node Discovery often drops pings

py-evm Version: c4e38746

What is wrong?
My log file is full of triplets like this:
   DEBUG  01-07 11:38:42     DiscoveryProtocol  unexpected v4 pong from <Node(0x6a2c@<IP_ADDRESS>)> (token == 0x3e72df0d5fd08ea0a476ca1047aa8db586ae58a94bf8cee060dc312b17ffc0b8)
   DEBUG  01-07 11:38:49     DiscoveryProtocol  timed out waiting for pong from <Node(0x6cd0@<IP_ADDRESS>)> (token == 0x3e72df0d5fd08ea0a476ca1047aa8db586ae58a94bf8cee060dc312b17ffc0b8)
   DEBUG  01-07 11:38:49     DiscoveryProtocol  bonding failed, didn't receive v4 pong from <Node(0x6cd0@<IP_ADDRESS>)>

In fact, I've dug into all instances of "unexpected v4 pong from" and nearly all of them are part of a triple of messages like the above one. We receive a pong from the node (with the wrong public key), throw it away, and then time out the node. For each node that this happens with we seem to repeat the process about every 9 minutes.

Maybe this is the fault of the nodes we're talking with, and this log spam could be reduced by remembering which nodes we've previously rejected and not talking to them for a while?
Maybe we're... incorrectly parsing the public key? This seems unlikely but it's possible.
Maybe these nodes aren't meant to be part of the network, they're just here to monitor the network, and they intentionally continually change their public keys?

ISTM there's nothing we can do about this, so I'll just add a comment to where we log the unexpected pong (so that the next person who notices them will know it's nothing to worry about) and close this. Feel free to reopen if you think we should do something else


Revert "log: support dynamically change log level via sql (#13019)"

This reverts commit cfe62ba99d073893839d357c6d3770ceb3f60107.

What is changed and how it works?

Issue Number: Close #xxx
What's Changed:

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

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

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with None.
If this PR will be picked to release branch, then a release note is probably required.

/build

/run-build-x86 comment=true


Youtube Extraction Error

It does this error for almost every song in the autoplaylist. It also does this when I try to load in a playlist from youtube and the individual videos that don't work. I even re-downloaded the bot. They were working till a few days ago.
https://pastebin.com/NW5609Zk

Update youtube-dl:
# Ubuntu 14.04(.*) LTS
python3.5 -m pip install -U -r requirements.txt

# Ubuntu 16.04 LTS or higher
python3 -m pip install -U -r requirements.txt

You need to update ytdl using our dependency update scripts:

Windows: Open update_deps.bat
Linux: Run python3.5 -m pip install --upgrade -r requirements.txt
Mac: Open update_macdeps.command in Terminal

You can also update ytdl manually using the command sudo pip install -U youtube-dl.


Spark chart

Adapted from https://github.com/kubernetes/charts/tree/master/stable/spark to our needs

Moved worker to DaemonSet to match HDFS deployment
Removed zeppelin deployment
Added NodeSelectors
Moved to ClusterIPs as we're not in a cloud provider
Adapted to 2.2.0
Added spark ui proxy integration

Working on https://github.com/src-d/backlog/issues/831

Awesome! Let me get back to it after running Berserker Spark jobs on our cluster tomorrow!

Every chart I've seen so far has separated files for deployments and services (skeleton generated by helm create is this way too). Is there a reason for having both things together in the same file here? Maybe we could split the deployment files.

I adapted the chart from the official repo that had the services and deployments together. Since we have four services, I think it is clearer to have them together with the deployments they belong to...

Corrected as per @smeruelo suggestions

@smeruelo I've arranged commits to keep them at minimum. You can merge this when you want ;-)


Weird "idpiframe_initialization_failed" only on chrome.

Chrome: 64.0.3282.167（Official Build） （64 bit）
I have a very strange idpiframe_initialization_failed issue only on Google Chrome. This happens after the GAPI load but before / during the GAPI init.

error: "idpiframe_initialization_failed"
details: "Not a valid origin for the client: https://listo-dev.firebaseapp.com has not been whitelisted for client ID myid.apps.googleusercontent.com. Please go to https://console.developers.google.com/ and whitelist this origin for your project's client ID."

I have double checked:

There is no adblock for the domain
The domain has definitely been whitelisted
Have tried hard reload with clearing cache

When I try to login I will always get the error: popup_closed_by_user
I think these problems might be related.
Here is where it gets weirder:

I set the browser to "offline".
I reload the page.
I receive the console.log that GAPI was loaded. (I don't receive the log that it's initiated, but also not the error).
I disable "offline".
I click the login button and it will log me in correctly.
HOWEVER, I will still see in the console the error: popup_closed_by_user only this time it does log me in correctly even though the console logs that error...

After waiting a few hours & restarting google chrome the problem went away. I have no idea what that was...

@mesqueeb it probably was HTTP caching issues. If you add the new origin to the authorized origins of the Client ID, it can take up to an hour before the browser sees the change (unless you clear the cache)

How to add an authorized origin if it's a Chrome Extension?


Update redis-py.

I couldn't get the docker-compose workflow to work without upgrading redis-py in the base image. I don't have the exact error message off-hand, but it when running the scheduler/worker i was getting error messages about a redis-py version mismatch which caused the containers to stop entirely.

Ha! I just noticed this PR. I have merged in one that addresses this and other old dependency issues as well.


Support new attributes in CosmosDB annotations

Support new attributes in CosmosDB annotations, for issue #420

Codecov Report

Merging #449 into develop will decrease coverage by 0.07%.
The diff coverage is 53.84%.

@@             Coverage Diff             @@
##           develop     #449      +/-   ##
===========================================
- Coverage    49.24%   49.16%   -0.08%
===========================================
  Files           64       64
  Lines         2041     2048       +7
  Branches       233      235       +2
===========================================
+ Hits          1005     1007       +2
- Misses         968      971       +3
- Partials        68       70       +2

Impacted Files
Coverage Δ

...azure/maven/function/bindings/CosmosDBBinding.java
53.48% <53.84%> (-4.85%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b52bd60...f33fbb6. Read the comment docs.

@pragnagopa
The generated function.json has been verified according to https://github.com/Azure/azure-functions-templates/blob/1e4c65a5a9db8e1b2f2d87a7c7d03463f4e626f3/Functions.Templates/Bindings/bindings.json#L2122. Now the function plugin could package and deploy cosmos db function, but i tried to write something with CosmosDBOutput, it shows
2018-10-29T09:07:38.129 [Error] Executed 'Functions.HttpTrigger-Java' (Failed, Id=ebbfaf1b-4816-4314-b62b-6c98c3f139a8)

Message: {"Errors":["One of the specified inputs is invalid"]}

ActivityId: c70f9511-031c-4ac4-abea-095a7b85f849, Request URI: /apps/c2ab109d-a398-4eec-b7aa-7b6c4ce540dd/services/d04992c4-96ae-40bf-82e4-e969510ecf5d/partitions/38719f72-36de-4870-b1ab-3b9a463cf859/replicas/131835576035187869p/, RequestStats:

RequestStartTime: 2018-10-29T09:07:38.0522210Z, Number of regions attempted: 1

, SDK: Microsoft.Azure.Documents.Common/<IP_ADDRESS>, Windows/10.0.14393 documentdb-netcore-sdk/2.0.0

And here is the trigger
    @FunctionName("HttpTrigger-Java")
    @CosmosDBOutput(name = "output", databaseName = "ToDoList", collectionName = "Items", connectionStringSetting = "AzureCosmosDBConnection", dataType="string")
    public String run(
            @HttpTrigger(name = "req", methods = {HttpMethod.GET, HttpMethod.POST}, authLevel = AuthorizationLevel.ANONYMOUS) HttpRequestMessage<Optional<String>> request,
            final ExecutionContext context) {
        context.getLogger().info("Java HTTP trigger processed a request.");

        // Parse query parameter
        String query = request.getQueryParameters().get("name");
        String name = request.getBody().orElse(query);

        String result = "{ id: " + System.currentTimeMillis() + ", Description: " + name + " }";
        context.getLogger().info(result);
        return result;

    }

Do you have any suggestion about this issue?

You are receiving a valid error. CosmosDB expects an Id to be set to a GUID.
Following works
String result = "{\"id\":\""+UUID.randomUUID()+ "\",\"Description\":\""+name+"\"}";

For cosmosDb a better example would be to use POJO as specifying
dataType="string"

is not very useful as inserting into documentdb needs an id
Please see example here for reference: https://github.com/Azure/azure-functions-java-worker/blob/dev/endtoendtests/src/main/java/com/microsoft/azure/functions/endtoend/CosmosDBTriggerTests.java#L115

@pragnagopa  For now we add attributes according to  binding.json here, add there are lots of new attributes add on your pr#https://github.com/Azure/azure-functions-java-library/pull/54, so should we add all new attributes to function.json, is there any new example here? For the C# example hasn't been updated for a long time.

Unit test that verifies function.json is created with all the values
Specified in the annotation is enough. I don’t have a sample that uses all the attributes. Will look for it.

Hi @pragnagopa,
Currently the CosmosDB annotation in azure-functions-java-library has more attributes than we have in the plugin: https://github.com/Microsoft/azure-maven-plugins/blob/develop/azure-functions-maven-plugin/src/main/java/com/microsoft/azure/maven/function/bindings/CosmosDBBinding.java
Should we add these newly added attributes as @Flanker32 listed in the CosmosDBBinding.java first?


PyList: fix segfault on get_item with negative indices

See #1667.

Sure. Looks like I also unintentionally relied on IntoIter for arrays :)

Benchmark looks completely flaky so don't worry about that.


showAsLink() links to wrong resource

showAsLink() is linking to /nova/resources/products/111130 where the id is correct but the resource segment of the url is wrong, it should be /nova/resources/comments/111130.
Is there a way for it to know which resource it should be linking to (is something set during the make() call that ->showAsLink() chains off of could use)? If not, maybe we make that an optional param you can pass to showAsLink()? eg. ->showAsLink(true, Comment::class)

Extended in Release v1.5

Awesome, thanks @koss-shtukert!


[Device Support Request] Xiaomi Smoke Detector

I am trying to get some additional functionality out of the smoke detector if possible please. There is already a handler which can be found at https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/xiaomi/mija/smoke.py
Would it be possible to get the additional entities presented?
https://zigbee.blakadder.com/Xiaomi_JTYJ-GD-01LM_BW.html
This lists Detector Sensitivity and Smoke Density
https://www.youtube.com/watch?v=EdezXlPoc4U
This video shows the app initiating a self test. It would be nice to be able to issue a self test, and potentially set the sensitivity.
I've put the pairing debug log below. If I start viewing the clusters within Home Assistant, it looks like the information might be there, but I am not 100% sure. Things like the smoke density, I would be interested to see if I can have a pre-warning that the alarm will go off when density is say 0-10, then when it hits 11, presumably the alarm would go off.
Thank you in advance
2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e41000700aa00 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1741000800010001 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x17410025001e0022020000010272bc0b04010000070018700a0100204200afff219d2c00d8 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [30, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xbc72>, 11, 260, 0, b'\x18p\n\x01\x00 B', 0, 175, 255, 33, 157, 44, 0, -40] 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy.zcl] [0xbc72:11:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=112 command_id=Command.Report_Attributes> 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy.zcl] [0xbc72:11:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=<TypeValue type=uint8_t, value=66>)]] 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy.zcl] [0xbc72:11:0x0000] Attribute report received: app_version=66 2021-03-05 15:52:26 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xbc72>, ep: 11, profile: 0x0104, cluster_id: 0x0000, data: b'18700a01002042' 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c420012000b00039dd78705008d1500ffd1 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c43000c00050002eb37ffd1 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e44000700aa00 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1742000800010001 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1742002a0023002202fdff0002eb3700000013000c00fdeb379dd78705008d15008000afff219d2c00d2 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [35, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 0, 0, 19, b'\xfd\xeb7\x9d\xd7\x87\x05\x00\x8d\x15\x00\x80', 0, 175, 255, 33, 157, 44, 0, -46] 2021-03-05 15:52:27 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0x37eb, 00:15:8d:00:05:87:d7:9d 2021-03-05 15:52:27 INFO (MainThread) [zigpy.application] Device 0x37eb (00:15:8d:00:05:87:d7:9d) joined the network 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.zdo] [0x37eb:zdo] ZDO request ZDOCmd.Device_annce: [0x37EB, 00:15:8d:00:05:87:d7:9d, 128] 2021-03-05 15:52:27 INFO (MainThread) [zigpy.device] [0x37eb] Requesting 'Node Descriptor' 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.util] Tries remaining: 2 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.device] [0x37eb] Extending timeout for 0x38 request 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 56 under 57 request id, data: b'38eb37' 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'fdeb379dd78705008d150080' 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (18, 57, 0, <DeconzAddressEndpoint address_mode=2 address=0x37EB endpoint=0>, 0, <ZDOCmd.Node_Desc_req: 0x0002>, 0, b'8\xeb7', 2, 0) 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x12430019001200390002eb37000000020000030038eb370200 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x124300090002002239 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 57] 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e44000700aa00 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1744000800010001 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1744003a003300220200000102eb3701040100001c0018000a050042116c756d692e73656e736f725f736d6f6b650100200100afffae9c2c00d2 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [51, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x00\n\x05\x00B\x11lumi.sensor_smoke\x01\x00 \x01', 0, 175, 255, 174, 156, 44, 0, -46] 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.application] Received frame on uninitialized device 00:15:8d:00:05:87:d7:9d (Status.NEW) for endpoint: 1 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.device] [0x37eb] Received ZCL while uninitialized on endpoint id 1, cluster 0x0000 id, hdr: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=0 command_id=Command.Report_Attributes>, payload: b'\x05\x00B\x11lumi.sensor_smoke\x01\x00 \x01' 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.device] [0x37eb] Uninitialized device command 'Command.Report_Attributes' args: [[Attribute(attrid=5, value=<TypeValue type=CharacterString, value=lumi.sensor_smoke>), Attribute(attrid=1, value=<TypeValue type=uint8_t, value=1>)]] 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.device] [0x37eb] Found 'MijiaHoneywellSmokeDetectorSensor' quirk for 'lumi.sensor_smoke' model 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.device] Canceling old initialize call 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.sensor_smoke (00:15:8d:00:05:87:d7:9d) 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'> 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy.quirks.registry] Found custom device replacement for 00:15:8d:00:05:87:d7:9d: <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'> 2021-03-05 15:52:27 INFO (MainThread) [zigpy.device] [0x37eb] Was quickly initialized from 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor' quirk 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x37EB:00:15:8d:00:05:87:d7:9d entering async_device_initialized - is_new_join: True 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x37EB:00:15:8d:00:05:87:d7:9d has joined the ZHA zigbee network 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): started configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:ZDO](lumi.sensor_smoke): 'async_configure' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18000a050042116c756d692e73656e736f725f736d6f6b6501002001' 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0000]: skipping channel configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0001]: skipping channel configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: skipping IASZoneChannel configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0019]: skipping channel configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0000]: 'async_configure' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0001]: 'async_configure' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: 'async_configure' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0019]: 'async_configure' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): completed configuration 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): stored in registry: ZhaDeviceEntry(name='LUMI lumi.sensor_smoke', ieee='00:15:8d:00:05:87:d7:9d', last_seen=1614959547.8274348) 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): started initialization 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:ZDO](lumi.sensor_smoke): 'async_initialize' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0000]: 'async_initialize' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0001]: 'async_initialize' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: 'async_initialize' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0019]: 'async_initialize' stage succeeded 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): power source: Battery or Unknown 2021-03-05 15:52:27 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x37EB](lumi.sensor_smoke): completed initialization 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e45000700aa00 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1745000800010001 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1745004c004500220200000102eb3701040100002e0018010a01ff42280121ef0b03281e0421a80105211000062401000000000a2100000821041064200096230000000000afff279d2c00c3 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [69, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x01\n\x01\xffB(\x01!\xef\x0b\x03(\x1e\x04!\xa8\x01\x05!\x10\x00\x06$\x01\x00\x00\x00\x00\n!\x00\x00\x08!\x04\x10d \x00\x96#\x00\x00\x00\x00', 0, 175, 255, 39, 157, 44, 0, -61] 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=1 command_id=Command.Report_Attributes> 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ValueError exception for: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=1 command_id=Command.Report_Attributes> payload: b'01ff42280121ef0b03281e0421a80105211000062401000000000a21000008210410642000962300000000' 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] new data: b'18010a01ff42270121ef0b03281e0421a80105211000062401000000000a21000008210410642000962300000000' 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=1 command_id=Command.Report_Attributes> 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�!>)]] 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] Attribute report received: 65281=!�(!�! 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3055 < [Max]:3100, Battery Percent: 84.0 2021-03-05 15:52:28 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18010a01ff42280121ef0b03281e0421a80105211000062401000000000a21000008210410642000962300000000' 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e46000700a600 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0] 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c47000c00050002eb37ffd0 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,) 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x04460007000000 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x04460013000c00223902eb3700000000000000 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 57: 00 2021-03-05 15:52:29 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 57, Status: TXStatus.SUCCESS 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x39 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x37eb endpoint=0>, status: 0x00 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e47000700aa00 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c48000c00050002eb37ffd0 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1747000800010001 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1747002f002800220200000002eb37000000028011003800eb3702408037107f6400000064000000afff279d2c00cf 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [40, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 0, 0, 32770, b'8\x00\xeb7\x02@\x807\x10\x7fd\x00\x00\x00d\x00\x00', 0, 175, 255, 39, 157, 44, 0, -49] 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy.zdo] [0x37eb:zdo] ZDO request ZDOCmd.Node_Desc_rsp: [<Status.SUCCESS: 0>, 0x37EB, NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4151, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=0, maximum_outgoing_transfer_size=100, descriptor_capability_field=0)] 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy.zdo] [0x37eb:zdo] Unsupported ZDO request:ZDOCmd.Node_Desc_rsp 2021-03-05 15:52:29 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 0, profile: 0x0000, cluster_id: 0x8002, data: b'3800eb3702408037107f64000000640000' 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e48000700aa00 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c49000c00050002eb37ffd2 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1748000800010001 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c4a000c00050002eb37ffd2 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x17480036002f00220200000102eb370104010000180018020a050042116c756d692e73656e736f725f736d6f6b6500afff279d2c00d2 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [47, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x02\n\x05\x00B\x11lumi.sensor_smoke', 0, 175, 255, 39, 157, 44, 0, -46] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=2 command_id=Command.Report_Attributes> 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=5, value=<TypeValue type=CharacterString, value=lumi.sensor_smoke>)]] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] Attribute report received: model=lumi.sensor_smoke 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18020a050042116c756d692e73656e736f725f736d6f6b65' 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e49000700aa00 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1749000800010001 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x17490027002000220200000102eb3701040100050900190300000000ff000000afff279d2c00d2 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [32, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 1280, b'\x19\x03\x00\x00\x00\x00\xff\x00\x00', 0, 175, 255, 39, 157, 44, 0, -46] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=3 command_id=0> 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL request 0x0000: [<ZoneStatus.0: 0>, <bitmap8.0: 0>, 255, 0] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] No handler for cluster command 0 2021-03-05 15:52:32 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: Updated alarm state: ZoneStatus.0 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0500, data: b'190300000000ff0000' 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e4a000700aa00 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174a000800010001 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174a004c004500220200000102eb3701040100002e0018040a01ff42280121ef0b03281e0421a80105211000062402000000000a2100000821041064200096230000000000afff279d2c00d2 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [69, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x04\n\x01\xffB(\x01!\xef\x0b\x03(\x1e\x04!\xa8\x01\x05!\x10\x00\x06$\x02\x00\x00\x00\x00\n!\x00\x00\x08!\x04\x10d \x00\x96#\x00\x00\x00\x00', 0, 175, 255, 39, 157, 44, 0, -46] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=4 command_id=Command.Report_Attributes> 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ValueError exception for: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=4 command_id=Command.Report_Attributes> payload: b'01ff42280121ef0b03281e0421a80105211000062402000000000a21000008210410642000962300000000' 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] new data: b'18040a01ff42270121ef0b03281e0421a80105211000062402000000000a21000008210410642000962300000000' 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=4 command_id=Command.Report_Attributes> 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�!>)]] 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] Attribute report received: 65281=!�(!�! 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3055 < [Max]:3100, Battery Percent: 84.0 2021-03-05 15:52:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18040a01ff42280121ef0b03281e0421a80105211000062402000000000a21000008210410642000962300000000' 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e4b000700aa00 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174b000800010001 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174b0026001f002202000001022f0c01040100030800184f0a0700211b0100afff279d2c00c6 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [31, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0c2f>, 1, 260, 768, b'\x18O\n\x07\x00!\x1b\x01', 0, 175, 255, 39, 157, 44, 0, -58] 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy.zcl] [0x0c2f:1:0x0300] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=79 command_id=Command.Report_Attributes> 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy.zcl] [0x0c2f:1:0x0300] ZCL request 0x000a: [[Attribute(attrid=7, value=<TypeValue type=uint16_t, value=283>)]] 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy.zcl] [0x0c2f:1:0x0300] Attribute report received: color_temperature=283 2021-03-05 15:52:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0c2f>, ep: 1, profile: 0x0104, cluster_id: 0x0300, data: b'184f0a0700211b01' 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c4c000c00050002eb37ffd6 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e4d000700aa00 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174c000800010001 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174c0027002000220200000102eb3701040100050900190500000000ff000000afff279d2c00d7 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [32, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 1280, b'\x19\x05\x00\x00\x00\x00\xff\x00\x00', 0, 175, 255, 39, 157, 44, 0, -41] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=5 command_id=0> 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL request 0x0000: [<ZoneStatus.0: 0>, <bitmap8.0: 0>, 255, 0] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] No handler for cluster command 0 2021-03-05 15:52:35 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: Updated alarm state: ZoneStatus.0 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0500, data: b'190500000000ff0000' 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e4d000700aa00 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174d000800010001 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174d004c004500220200000102eb3701040100002e0018060a01ff42280121ef0b03281e0421a80105211000062403000000000a2100000821041064200096230000000000afff279d2c00d6 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [69, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x06\n\x01\xffB(\x01!\xef\x0b\x03(\x1e\x04!\xa8\x01\x05!\x10\x00\x06$\x03\x00\x00\x00\x00\n!\x00\x00\x08!\x04\x10d \x00\x96#\x00\x00\x00\x00', 0, 175, 255, 39, 157, 44, 0, -42] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=6 command_id=Command.Report_Attributes> 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ValueError exception for: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=6 command_id=Command.Report_Attributes> payload: b'01ff42280121ef0b03281e0421a80105211000062403000000000a21000008210410642000962300000000' 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] new data: b'18060a01ff42270121ef0b03281e0421a80105211000062403000000000a21000008210410642000962300000000' 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=6 command_id=Command.Report_Attributes> 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�!>)]] 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] Attribute report received: 65281=!�(!�! 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3055 < [Max]:3100, Battery Percent: 84.0 2021-03-05 15:52:35 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18060a01ff42280121ef0b03281e0421a80105211000062403000000000a21000008210410642000962300000000' 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e4e000700aa00 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174e000800010001 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174e0025001e0022020000010247520104010000070018510a0100205000afff279d2c00d8 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [30, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x5247>, 1, 260, 0, b'\x18Q\n\x01\x00 P', 0, 175, 255, 39, 157, 44, 0, -40] 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy.zcl] [0x5247:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=81 command_id=Command.Report_Attributes> 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy.zcl] [0x5247:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=1, value=<TypeValue type=uint8_t, value=80>)]] 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy.zcl] [0x5247:1:0x0000] Attribute report received: app_version=80 2021-03-05 15:52:36 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x5247>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18510a01002050' 2021-03-05 15:52:38 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c4f000c00050002eb37ffd7 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e50000700aa00 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x174f000800010001 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0e51000700aa00 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x174f00270020002a0200000102eb3701040100050900190700000000ff000000afff279d2c00d7 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [32, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 42>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 1280, b'\x19\x07\x00\x00\x00\x00\xff\x00\x00', 0, 175, 255, 39, 157, 44, 0, -41] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=7 command_id=0> 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] ZCL request 0x0000: [<ZoneStatus.0: 0>, <bitmap8.0: 0>, 255, 0] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0500] No handler for cluster command 0 2021-03-05 15:52:39 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x37EB:1:0x0500]: Updated alarm state: ZoneStatus.0 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0500, data: b'190700000000ff0000' 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1) 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x1750000800010001 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1750004c004500220200000102eb3701040100002e0018080a01ff42280121ef0b03281e0421a80105211000062404000000000a2100000821041064200096230000000000afff279d2c00d6 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [69, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, 1, 260, 0, b'\x18\x08\n\x01\xffB(\x01!\xef\x0b\x03(\x1e\x04!\xa8\x01\x05!\x10\x00\x06$\x04\x00\x00\x00\x00\n!\x00\x00\x08!\x04\x10d \x00\x96#\x00\x00\x00\x00', 0, 175, 255, 39, 157, 44, 0, -42] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=8 command_id=Command.Report_Attributes> 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ValueError exception for: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=8 command_id=Command.Report_Attributes> payload: b'01ff42280121ef0b03281e0421a80105211000062404000000000a21000008210410642000962300000000' 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] new data: b'18080a01ff42270121ef0b03281e0421a80105211000062404000000000a21000008210410642000962300000000' 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=8 command_id=Command.Report_Attributes> 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] ZCL request 0x000a: [[Attribute(attrid=65281, value=<TypeValue type=CharacterString, value=!�(!�!>)]] 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0000] Attribute report received: 65281=!�(!�! 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy.zcl] [0x37eb:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3055 < [Max]:3100, Battery Percent: 84.0 2021-03-05 15:52:39 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x37eb>, ep: 1, profile: 0x0104, cluster_id: 0x0000, data: b'18080a01ff42280121ef0b03281e0421a80105211000062404000000000a21000008210410642000962300000000' 2021-03-05 15:52:42 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c51000c00050002eb37ffd6 2021-03-05 15:52:45 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c52000c00050002eb37ffd7 2021-03-05 15:52:48 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c53000c00050002eb37ffd4 2021-03-05 15:52:51 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1c54000c00050002eb37ffd3

Apparently this is a really good Hubitat driver:
https://raw.githubusercontent.com/markus-li/Hubitat/release/drivers/expanded/zigbee-xiaomi-smoke-detector-expanded.groovy
I can see test within this although I am not sure on Groovy and how to convert to Python/zigpy

Doing more digging, I can see what looks like the correct cluster to issue the test command to when using Manage Clusters option on the device. But when I attempt to issue the command it errors with ValueError: Wrong number of parameters for request, expected 2 argument(s).

I don't know if ui handles multiple commands parameters. You would need to use service call, that can send multiple command params

I have managed to get the test to work:
service: zha.set_zigbee_cluster_attribute     data:       ieee: 00:15:8d:00:05:87:d7:9d       endpoint_id: 1       cluster_id: 1280       attribute: 65521       value: 50397184       manufacturer: 4447
A few moments after issuing this command it beeps, same as pressing the manual test button.

I would very much like this too. The relevant Zigbee2MQTT code is here:
https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices/xiaomi.js#L792-L804
https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/converters/fromZigbee.js#L5335-L5364
https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/converters/toZigbee.js#L1993-L2013
The sigpy/ZHA code is, apparently, here:
https://github.com/zigpy/zha-device-handlers/blob/9c278b8f9c42a8d8f0c1d1b8dc3b137992f19981/zhaquirks/xiaomi/__init__.py#L185-L217
I've been suggested to add a PM2.5 cluster a la:
https://github.com/zigpy/zigpy/blob/dev/zigpy/zcl/clusters/measurement.py#L332
I'm just not sure where to start

Checked with the a test version. The capability is not there. Since this is one of the more afordable zigbee smoke detectors the capabilities described and researched in this thread has high value. Smart muting of alarms and using using multiple wireless smoke alarms as sirens for home alarm comes to mind.
Would prefer to keep this open. Unsure how I can assist in progressing the issue though.

I am seeing more and more people in general asking questions about this smoke alarm.  Have had a couple on my YouTube video where I unboxed and added it to Home Assistant. It would be good to get this sorted. Like @LinusT and @nashant I am unsure how to work with the files etc. I have read and read but struggling to get head around it all


Don't import historic WOF neighbourhoods

Migration to add inception, cessation, is_visible columns to WOF neighbourhoods. Update to queries to use the visibility information.
Requires and is required by mapzen/tilequeue#63. Connects to mapzen/tilequeue#59.
@nvkelso could you review, please?

Other than the is_visible question above, LGTM


Icon Update - v1.6.0

New Icon Added: src/icons/0166_pause_a.svg
New Icon Added: src/icons/0127_bell_a_outline.svg
This outlined version will be utilized as an off state for
“reminders”
Icon Updated: src/icons/0020_curvedDoubleArrowLeft_a.svg
Accessibility concerns with previous icon version. New icon version
includes more space between the arrow shape and the second arrow.

Please make the following updates to the file names:
For src/icons/0127_bell_a_outline.svg:

change 'outline' to 'light' per the documentation
add in the state variant to indicate the on/off state per the documentation

Also, based off the new updates to the state concept to indicate on/off, and the 'a' now being used for all toggle icons, many different icons will need updated, including the pin icons.
This will be a very important note to engineers once the changes are made.

@Slothjams
A few adjustments needed.  For the following icons, please make sure to specify the statehood of intended use for "on/off" at the end of the file name, similar to how you indicated in for the bell icon (src/icons/0127_bell_a_heavy_on.svg)

star
pin

Changes all look good, @Slothjams please be sure to send out some messaging of the changes in naming strategy to prepare the consumers of these new and existing icons.


Test against PHP 8.1

Codecov Report

Merging #90 (71a011c) into main (a40be2a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #90   +/-   ##
=========================================
  Coverage     99.87%   99.87%
  Complexity      349      349
=========================================
  Files            17       17
  Lines           775      775
=========================================
  Hits            774      774
  Misses            1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a40be2a...71a011c. Read the comment docs.


quota exeeded

Hello
When I go there : https://pwa-directory.appspot.com/pwas/newest
I get this message :
{"code":8,"metadata":{"_internal_repr":{}},"details":"Quota exceeded.","note":"Exception occurred in retry method that was not classified as transient","status":500,"response":"8 RESOURCE_EXHAUSTED: Quota exceeded."}
Is your site too successful ;-) ?

Hi @hugues-koolsol
Thank you for reporting it, I don't see many errors in our logs. I will double check but it seems it was something isolated.
Cheers,
Julian.

Hello Julian.
I had the same message this morning.

Hello Julian
This morning on : https://pwa-directory.appspot.com/
I had a reply : 502 Bad Gateway


Add package.yaml to autofill other-modules.

Thank you Phil. Yes you are right as the polar regions south of 80°S and north of 84°N are excluded from UTMRef (not needed for longitude as 60 part of 6° each one). Can you please add a test to verify the correct behaviour of the code you have added?
https://github.com/danfran/hcoord/blob/master/test/UTMRef/Tests.hs

Closing in favour of the fix for #6.


Add simple jest test for component render

react-tools is deprecated but in webpack we're already using jsx-loader, which uses react-tools, so I'm using the same for compatibility. I added this test because it's simple and isolated but as app.jsx is broken up more, it should be easy to add new tests.
Test Plan: npm test

I used jest because I'm familiar with it, though it's not the most popular.

Thanks!

FYI I was aparently on a super old version of node and this PR caused npm install to crash until I upgraded.
node --version
v0.12.7

:grimacing:

Oops. Glad you got it to work!

Awesome stuff adding tests and fixtures!


[DevOps Center] Merge WI-000002 to Staging

DevOps Center created this pull request. It will be merged automatically upon promotion in DevOps Center. If you merge it outside of DevOps Center, DevOps Center provides you the option to deploy the changes to complete the promotion.

This PR was automatically converted from https://github.com/suvikram/apex-recipes/pull/97 submitted by suvikram


updated testcase  update please

from sayanmondal2098

@sayanmondal2098 , create a new branch, fetch latest changes there and do your intended changes. Send the PR, that should resolve the issue. :)


Can only download English patch

Description
I thought I had all the necessary files. What is going wrong?

Steps to Reproduce

Open WA2_patch.exe
Accept agreement
Next
Browse Downloads\WHITE ALBUM2 folder
Next
Custom installation
Check audio-only subs and Subbed videos
Next
Next
Install
Download failed: 404 Not Found

Possible Fix
No response
Log File
No response

Duplicate of #8

I already downloaded the files mentioned in #6. I'm still getting the error
message.
On Sat, Mar 12, 2022 at 2:32 PM ObserverOfTime @.***>
wrote:

Duplicate of #8 https://github.com/TodokanaiTL/WA2EnglishPatch/issues/8
—
Reply to this email directly, view it on GitHub
https://github.com/TodokanaiTL/WA2EnglishPatch/issues/10#issuecomment-1065949008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYGF6EVEYLIN43KIN2EG7SDU7TWMHANCNFSM5QSGMQNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

I already downloaded the files mentioned in #6. I'm still getting the error message.
…
On Sat, Mar 12, 2022 at 2:32 PM ObserverOfTime @.> wrote: Duplicate of #8 <#8> — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYGF6EVEYLIN43KIN2EG7SDU7TWMHANCNFSM5QSGMQNA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.>

You need to manually copy the downloaded files into the game folder.


don't configure consul-template with empty tokens.

defining the tokens as empty strings in the consul-template config then makes consul-template ignore the CONSUL_TOKEN and VAULT_TOKEN environment variables.

Hi, as this PR hasn't seen any activity in a number of months, I'm closing it. Please do feel free to fix the bug mentioned above and re-open.


Feature: Option to keep fields that is not marked with decorators

class-transformer is keeping unknown fields by default and it has an option to disable this behavior. Is it possible to implement something similar?
https://github.com/typestack/class-transformer#enforcing-type-safe-instance

This is by design not possible, also because it would be a security risk. I'd recommend you to add dynamic fields into a map field
class MyType {

     @f.any().asMap()
     dynamicFields: {[name: string]: any} = {};
}

Thanks for quick reply. I agree that default behavior is secure. But an option for keeping extra fields would be awesome.

No problem. Unfortunately, that's not possible and would decrease performance. I recommend you to not do thi, if not possible work around it by using any type.


Update minimum version of azure-core-cpp

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Follow up to #9

@conda-forge-admin, please rerender


If to drag and drop Folder_parent into Folder_child both folders disappears. Applicable for chat and prompt folders.

If to drag and drop Folder_parent into Folder_child both folders disappears. Applicable for chat and prompt folders.

Create a structure:

Folder_parent
--Folder_child

Drag Folder_parent and drop it in Folder_child -> both folders disappears from UI -> bug

Expected result: not allow to move parent folder in child folder

Verified on staging server successfully


REPORTTIME

Hi,
I am using Arch linux
I use REPORTTIME feature my zshrc using export REPORTTIME=0 ( want every command to get reported )
using zsh 5.2-1 and oh-my-zsh-git from aur
my zshrc

ZSH=/usr/share/oh-my-zsh/
REPORTTIME=0
ZSH_THEME="agnoster"
DISABLE_AUTO_UPDATE="true"
ENABLE_CORRECTION="true"
COMPLETION_WAITING_DOTS="true"
HIST_STAMPS="yyyy-mm-dd"
plugins=(git command-not-found)
export LANG=en_US.UTF-8
export EDITOR="vim"
export ARCHFLAGS="-arch x86_64"
ZSH_CACHE_DIR=$HOME/.oh-my-zsh-cache
if [[ ! -d $ZSH_CACHE_DIR ]]; then
mkdir $ZSH_CACHE_DIR
fi
source $ZSH/oh-my-zsh.sh
source /usr/share/zsh/plugins/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

but everytime I execute command get reported with

ali@Dell  ~   echo Hi
Hi
0.00s user 0.00s system 0% cpu 0.003 total
0.00s user 0.00s system 0% cpu 0.002 total

after using the default zshrc I dont get reported with 2 outputs
using the method from http://superuser.com/questions/735660/whats-the-zsh-equivalent-of-bashs-prompt-command to execute time before every command I got

ali@Dell  ~  echo Hi
Hi
shell  0.60s user 0.09s system 0% cpu 9:58.11 total
children  0.20s user 0.03s system 0% cpu 9:58.11 total

How do I remove the shell reported time shell  0.60s user 0.09s system 0% cpu 9:58.11 total  or in the first example 0.00s user 0.00s system 0% cpu 0.003 total
thank you .

This is likely because you're seeing literally every command run on the shell, including the pre-/post-commands that are run behind the scenes by oh-my-zsh. For example, in a git directory you'll possibly end up with six reports (as I did) as it tries to figure out which branch I'm in and what the commit is. In other words, you probably do not want it set to zero.

thank you
after setting REPORTTIME=5 problem solved

thank you
after setting REPORTTIME=7 problem solved


Distinguish test package dependencies versus library package dependencies

Motivating example
Consider this scenario:
I have two packages:

BigTest is a testing library developed to script long-running tests with a DSL
BigMap is a data structure library developed for simple databases that get really large

Each package has a test suite, in its test subdirectory; when master advances for this package repo, we want to run CI using this test suite.
BigTest solving a problem that the test suite of BigMap needs to solve.  So, the test suite of BigMap depends on BigTest.
BigMap is a service that BigTest tests, as a regression test for its own revision management.  So, the test suite of BigTest depends on BigMap.
Unless we distinguish library dependencies from test dependencies (e.g., cargo for Rust does this), we have a problem: There is a cyclic dependency between these two packages, apparently.
Today
Today, vessel packages conflate the dependency information of package's library code and that of its test suite code, in the sense that there is only one place to specify this information, even though the dependency structure we want is really more fine-grained.
This issue proposes that this information be distinguished.
Proposal
I propose we distinguish library and test packages (two kinds of packages):

Libraries depend on other libraries.
Test suites depend on libraries.
By default: Libraries do not depend on test suites (because test suites are either not possible to name as packages themselves, or they are distinct with distinct names from the corresponding library package).

Initially, we need not name or import test suite packages.
But we do need to identify their dependencies, and permit them to include more than the libraries that they test.

I'm tracking this in #26 which is a little more general. Thanks for the description, this definitely provides lots of motivation for the design we'll come up with.


monitoring: making alert firing timeout and the doc timeout same

Signed-off-by: Arun Kumar Mohan<EMAIL_ADDRESS>(cherry picked from commit 054d009af6a345d65c882a6b352dba3054abf91e)

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
[ ] Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.
[ ] Pending release notes updated with breaking and/or notable changes, if necessary.
[ ] Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
[ ] Code generation (make codegen) has been run to update object specifications, if necessary.

/approve /lgtm


Failed test sometimes does not appear in the allure report

Hello,
I'm using allure together with testng to generate test reports. I've noticed that in some cases, when a test fails, it is not displayed in the report.
Context:
I'm running appium tests on a jenkins machine. I've noticed the problem when jenkins marked a build as failed, but the allure report did not show any failed tests. Looking at the logs I saw that testng did indeed detect the failure, but in the resulted allure xml file that specific test case was missing entirely.
Unfortunately I cannot provide any kind of logs but I'm attaching a screenshot that shows my problem:

In this case you can see 3 runs of the same exact suite, with 2 of them having 19 test cases and 1 of them having only 18.
This issue seems to appear at random times, on random test cases, regardless if I run multiple test suites in parallel (as in the screenshot) or just one.
I realize this is not much information to go by, but unfortunately I cannot provide any more at the moment. If you have any questions or ideas that might help with better understanding this issue, shoot.
Thanks!

Closing as I can no longer see this behaviour after an update.


map not showing up

Hi,
it's partially working - i got geocomplete, but no map and marker (however I see that map div changes in html from empty div). May you pls help?
router.js
Router.onBeforeAction(function (){
GoogleMaps.load({libraries: 'places' });
this.next();   }, {only:['userProfile']});

template.js
Template.userProfile.events({
  'click #find': function (){
       event.preventDefault();
       $("#geocomplete").trigger('geocode');
    }
});

Template.userProfile.rendered=function () {
   $("#geocomplete").geocomplete({map:".map_canvas"});
};

html.html

                <input class="form-control" id="geocomplete" type="text" autocomplete="off">

                  <button class="btn btn-primary" id="find">FIND</button>

Try something like:
Template.userProfile.rendered = function () {
  this.autorun(function() {
    if (GoogleMaps.loaded())
      $("#geocomplete").geocomplete({map:".map_canvas"});
  });
};

On second read, I don't see any code for actually displaying the map. Have a look at the docs and it may help to try the demo app.

Thank you @dburles you've pointed me into the right way. Will change the code in the issue to the right one & close it.


temp size check in mpi_montmul is incorrect

https://github.com/ARMmbed/mbedtls/blob/84a1107818aaddfd2abe4c5a3478cf84ab2e26b4/library/bignum.c#L1571
T needs to be about 2x as big as N, but here the size check referenced above only enforces that T is about as big as N.
Notice how d is initialized to T->p:
https://github.com/ARMmbed/mbedtls/blob/84a1107818aaddfd2abe4c5a3478cf84ab2e26b4/library/bignum.c#L1576
and incremented n = N->n times:
https://github.com/ARMmbed/mbedtls/blob/84a1107818aaddfd2abe4c5a3478cf84ab2e26b4/library/bignum.c#L1591
and then after incrementing d[0] through d[n] are copied into A->p
https://github.com/ARMmbed/mbedtls/blob/84a1107818aaddfd2abe4c5a3478cf84ab2e26b4/library/bignum.c#L1594
This means that the copy reads up to T->p[2*n-1] (actually, because of the line where d[n+1] is set to 0, T->p needs to have size at least 2*N->n + 1).
This is not currently a safety issue because only modular exponentiation actually calls mpi_montmul, and that function always ensures that T has sufficient size. So the defensive check is useless, but it isn't dangerous (until someone else decides to start using mpi_montmul).

ARM Internal Ref: IOTSSL-2525

@RonEld Why is this being closed without a single note?


Math expression parser to be added to flib?

Hi,
I saw another mod (cybersyn combinator) that implemented a way to parse math expression (like in a combinator when setting a signal). However, I wanted a safer version of a math expression parser so I wrote one proof of concept. It's kinda basic but it supports parsing the followings operations: -, +, *, /, parenthesis and negative numbers.
So I wanted to know, would you like to integrate this into flib (I'll make a PR for this later, if you choose this)? Or should I spin off my own factorio mod library?

The API actually has a function for this: game.evaluate_expression. It's normally only used for infinite technology costs, but it's pretty general-purpose and could be used elsewhere as well!


Readme Instructions unclear

Forgive me, I am a newbie when it comes to using flavours. You state:

Now using your injector (if you don't have one, check out flavours), and configure it so the template will be built to both ~/.themes/FlatColor/colors3 and ~/.themes/FlatColors/colors2, using the subtemplates gtk-2 and gtk-3, respectively.

If I go to the flavours site, there is no gtk template and it isn't clear what is supposed to happen here. Could you perhaps be more instructive, or point me to an example?

Hey! Flavours config is basically one item per template/subtemplate you want to apply. If you want to theme both gtk3 and gtk2, you should make two entries on ~/.config/flavours/config.toml. One for gtk-flatcolor gtk-2 and one for gtk-flatcolor gtk-3. Here's how to relevant part of my config file looks like:
[[item]]
file = '~/.themes/FlatColor/colors3'
template = 'gtk-flatcolor'
subtemplate = 'gtk-3'
rewrite = true
hook = 'systemctl restart --user xsettingsd &'

[[item]]
file = '~/.themes/FlatColor/colors2'
template = 'gtk-flatcolor'
subtemplate = 'gtk-2'
rewrite = true
hook = 'gtkrc-reload &'

Oh and i use a systemd unit file for xsettingsd as it is a daemon process (it keeps running till restarted). Here's my unit file (~/.config/systemd/user/xsettingsd.service):
[Unit]
Description="Xsettings Daemon"

[Service]
StartLimitBurst=20
StartLimitIntervalSec=5
Type=exec
WorkingDirectory=/home/misterio
ExecStart=/usr/bin/xsettingsd
Restart=no

[Install]
WantedBy=default.target

And here's the hooks i use, just in case you need them:
xsettingsd for reloading gtk3: https://github.com/derat/xsettingsd
gtkrc-reload for reloading gtk2: https://github.com/neeasade/gtkrc-reload
If you use Arch, xsettingsd is in the repositories, and gtkrc-reload is in the AUR

Let me know if you need any more help with it <3

Fantastic, thank you.


About page

Not ready for merging, just for initial review.

For spacing between sections being responsive, if it makes it simpler the 'wider' versions can have excessive spacing. If it's too much Robin will reel it in.
For my title so it's not too long, let's change it to Cofounder, Dev (change it in en.coffee and add the comment # {change} at the end.
For the billion lines of code, hide the br at xs
Also, there should be margin around the text, give the curly brace images some space
Narrow and center the 5,000,000+ total players column at medium sizes and lower, so it looks more like the 200+ countries piece beneath.
For the download assets, try removing the center-block piece, giving the #downloads div auto for side margins, and increasing its column width at sm size.


Expand form to include all fields in the "mega app" prototype

Based on this form: http://www.formstack.com/forms/?1721573-qkkmpdNPHb
The html file can also be downloaded here: https://dl.dropboxusercontent.com/u/36727215/form.html
NB: Some fields might not appear/show up as there's some kind of conditional logic behind, so it's better to play around with the form to see those or look at the code.

Closing out as not current.


HHH-12663 Upgrade gradle-karaf-plugin

https://hibernate.atlassian.net/browse/HHH-12663

I reorganized the commits a bit and merged. We still have to fix the Infinispan feature but it's part of another issue.

Thanks @fax4ever, nice work!


mod_pagespeed strips custom HTML headers on HEAD requests

What steps will reproduce the problem?
1. Make a HEAD request for a resource with custom headers on response.
2. When mod_pagespeed is on the headers will be stripped.

What is the expected output? What do you see instead?
I expect to see headers similar to a GET request on that resource.  This
happens even with ModPagespeedModifyCachingHeaders off.  The issue may be an
edge case of http://code.google.com/p/modpagespeed/issues/detail?id=367.

GET response:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Age: 62
Content-Length: 116191
Content-Type: text/html;charset=UTF-8
Date: Thu, 04 Sep 2014 14:46:01 GMT
Server: Apache
Set-Cookie: MY_COOKIE=874512650.20480.0000; path=/
Via: 1.1 varnish
X-Varnish: 174172375 174172369

HEAD response:
HTTP/1.1 200 OK
Cache-Control: max-age=0, no-cache
Content-Encoding: gzip
Content-Length: 20
Content-Type: text/html;charset=UTF-8
Date: Thu, 04 Sep 2014 14:51:09 GMT
Set-Cookie: MY_COOKIE=874512650.20480.0000; path=/
Vary: Accept-Encoding

What version of the product are you using (please check X-Mod-Pagespeed
header)?
X-Mod-Pagespeed: <IP_ADDRESS>-3847

On what operating system?
RHEL 6.5

Which version of Apache?
2.2.15-30.el6_5

Which MPM?
worker

URL of broken page:
Not public

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 4 Sep 2014 at 2:53

Hello!
any news about this issue?
Thanks

I see I asked a clarifying question 3 years ago and a response came back shortly after.  Now I see that my response should be "Working As Intended", no?
I would not expect mod_pagespeed to rewrite a head request, so X-Mod-Pagespeed should be excluded.  Nor do I expect the Age or varnish headers to be retained.
@sourcedump are you seeing other headers stripped that you don't expect?

Hello!
yes, in my case, when I make an HEAD request (eg using 'curl -I') the 'Link' header is stripped away.
I'm using Ubuntu 16.04.3 LTS with Apache 2.4.18 server.
Thanks


Question about cache option

Feature to document
cache https://github.com/webpack/webpack.js.org/blob/master/src/content/configuration/cache.mdx

Author(s)

Additional information
Sorry not sure if this is a good place to ask the question. I am using the cache option with type: 'filesystem', but is there a way to exclude a folder in node_modules (regex or namespace e.g. @my-componay/folders)?
Something like
cache: {
  type: 'filesystem',
  exclude: /node_modules\/(?!(@mands)\/).*/,
}

Also, I am assuming if I update an npm package, it should invalidate the cache.
[ ] I am willing to work on this issue and submit a pull request.

No way, it is impossible, otherwise cache will be broken, if something will be changed and your build depend on it, please use https://webpack.js.org/configuration/cache/#cachebuilddependencies, also you can use https://webpack.js.org/configuration/cache/#cachemanagedpaths and remove node_modules if you need to do file snapshots (i.e. timestamp/hashing of content), feel free to feedback


ceph-docker-common vars not added to group_vars/all.yml

When you run bash generate_group_vars_sample.sh the contents of roles/ceph-docker-common/defaults/main.yml should be added to group_vars/all.yml.sample.
I attempted a quick fix, but my approach overwrote all of group_vars/all.yml.sample with the values from ceph-docker-common. The correct thing I think should be to have group_vars/all.yml.sample include config options from both ceph-docker-common and ceph-common.

what about https://github.com/ceph/ceph-ansible/blob/master/group_vars/docker-commons.yml.sample?

@leseb docker-commons.yml does not match up with any of our groups, so it won't be used by ansible. This is why ceph-common must put it's vars in all.yml.
See: http://docs.ansible.com/ansible/intro_inventory.html#splitting-out-host-and-group-specific-data

Fixed.


Fix for Firefox deposit buttons not working.

Due some firefox changes i decided to fix this problem of not working buttons.
replace line 149 of script.js: https://github.com/ztizzlegaming/CSGOWinBig/blob/master/src/script.js#L149
with following code:
if(navigator.userAgent.toLowerCase().indexOf('firefox') > -1)
			{
				window.open('your steam trade offer url of your bot', '_blank');
				console.log('firefox');
				}else{
				$('<a>').attr('href', 'your steam trade offer url of your bot').attr('target', '_blank')[0].click();
				console.log('not firefox');
			}

Create a PR?

but is the button deposit dont work in all the cases i think

@krozs  what you mean?

The deposit button dont work, they dont do nothing when some people try to deposit

Fix is working and tested thanks Anthony ;)

#33

@andrewda  ok thanks for the pull request, if i wanted to do that i had to start all over again ( i changed way too much in several files i can't keep track of it anymore).

@TheAnthonyNL hahaha, no problem.


Inconsistency with paper w.r.t spatial gradient & 1x1 convolution

Hi,
In your paper (https://arxiv.org/abs/2003.08061) you mention in formula (2) that your spatial gradient (sobel) filters are applied to the output of the 1x1 convolution in the skip connection. However in your implementation you apply the 1x1 after applying the sobel filters to the res block input:
https://github.com/clks-wzz/FAS-SGTD/blob/9b813b62dcfe4467fd840f39776d3e66f5dd58e1/fas_sgtd_single_frame/util/util_network.py#L68
Could you comment on which implementation is correct please?
Thanks!

We recommend that you can use gradient_type="type0" or "type1" in residual_gradient_conv() for stabler training.

Great, thanks!


chore(master): release 1.35.0

:robot: I have created a release beep boop
1.35.0 (2023-12-20)
Features

clean identity deprecated param (62f83b0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/indykite-sdk-python/releases/tag/v1.35.0 :sunflower: