Facing build error while installing package on RN 0.64.2

Describe the bug
I am not able to add the package to my rn project.
To Reproduce
Steps to reproduce the behavior:

After following the steps listed here link
Add in android/gradle/wrapper/gradle-wrapper.properties
distributionUrl=https://services.gradle.org/distributions/gradle-7.0.2-all.zip

I am getting this error
BUILD FAILED in 9s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/kailashuniyal/Desktop/work/cwings-delivery-app/android/app/build.gradle' line: 271

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not get unknown property 'compile' for configuration container of type org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 9s

    at makeError (/Users/kailashuniyal/Desktop/work/cwings-delivery-app/node_modules/execa/index.js:174:9)
    at /Users/kailashuniyal/Desktop/work/cwings-delivery-app/node_modules/execa/index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (/Users/kailashuniyal/Desktop/work/cwings-delivery-app/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:5)
    at async Command.handleAction (/Users/kailashuniyal/Desktop/work/cwings-delivery-app/node_modules/@react-native-community/cli/build/index.js:186:9)

Additional context
Add any other context about the problem here.
info Fetching system and libraries information...
System:
    OS: macOS 12.0.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 70.92 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.4.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.19.1 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>86908
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.13 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.2 => 0.64.2
    react-native-macos: Not Found
  npmGlobalPackages:

Hi @Kailash23, did you add these extra configurations ?
In android/build.gradle:
buildscript {
    ext {
        ...
        kotlin_version = '1.5.10'
    }
   dependencies {
         ...
        classpath("com.android.tools.build:gradle:7.0.2")
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version")
        ...
    }

In android/app/build.gradle:
  ...
  apply plugin: "kotlin-android"
  apply plugin: "kotlin-android-extensions"
  ...

In android/app/src/main/AndroidManifest.xml:
      <application
        ...
        ...
      >
        <activity
         ...
         android:exported="true"
         ...
        >
        ...
       </activity>
    </application>

Yes @DibyajyotiMishra
Followed all the steps in this link

@Kailash23
Did you add this  in AndroidManifest ?
android:exported="true"


pointerAtBeginning is not part of Arrow constructor parameters

Attempting to create an Arrow with the property pointerAtBeginning will throw a TypeScript error that the property does not exist.
The method is listed as a property in the Arrow class on konva.d.ts however it is not listed on the ArrowConfig constructor.
The property still exists on vanilla Konva according to the docs: https://konvajs.github.io/api/Konva.Arrow.html

Fixed with https://github.com/konvajs/konva/commit/7400977f50672bea99b56e8cf6a95433634e410b.
I will publish later. Thanks for the report.


Issue1677

When a file is added, the default option of AUTO is enable but not showing checking mark.

This change is too extreme, in that it will cause the function to always force a reload.  What you need to do is add a true to the caller in the particular spot where navigation is happening, which I linked to in the previous discussion.

I changed the file as below.

force = true

reload(true)
But, I couldn't commit it again because of the error message.
git push -u upstream issue1677
remote: Permission to mozilla/brackets.git denied to tonypark0403.
fatal: unable to access 'https://github.com/mozilla/brackets.git/': The requested URL returned error: 403

You can't push to Mozilla's upstream repo, since you don't have write permissions.  You need to push to your origin, and it will automatically add it to this pull request.

I did it. Thank you very much.

The code you have now will do the exact same thing as before, just indirectly: you're checking if force is null, and if so calling the same function again with true.  That's not what I'm suggesting you do.
Instead, I want you to change the code as described here: https://github.com/mozilla/thimble.mozilla.org/issues/1677#issuecomment-276840542.  Specifically, change https://github.com/mozilla/brackets/blob/master/src/extensions/default/bramble/lib/PostMessageTransport.js#L164 to use reload(true);.

Thank you for helping to find out what you want me to do.
But, during the git processing, I got the non-fast-forward problem.
Can you  delete my previous pull request or please let me know other way in this case.
$ git push origin issue1677
To https://github.com/tonypark0403/brackets.git
! [rejected]            issue1677 -> issue1677 (non-fast-forward)
error: failed to push some refs to 'https://github.com/tonypark0403/brackets.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
From: David Humphrey<EMAIL_ADDRESS>Sent: Wednesday, February 8, 2017 9:30 PM
To: mozilla/brackets<EMAIL_ADDRESS>Cc: Heetai Park<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [mozilla/brackets] Issue1677 (#579)
The code you have now will do the exact same thing as before, just indirectly: you're checking if force is null, and if so calling the same function again with true. That's not what I'm suggesting you do.
Instead, I want you to change the code as described here: mozilla/thimble.mozilla.org#1677 (comment)https://github.com/mozilla/thimble.mozilla.org/issues/1677#issuecomment-276840542. Specifically, change https://github.com/mozilla/brackets/blob/master/src/extensions/default/bramble/lib/PostMessageTransport.js#L164 to use reload(true);.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mozilla/brackets/pull/579#issuecomment-278528876, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANrzz6oulx9l9Xhir294cpygxl_pe3Egks5ranoagaJpZM4L7Ue3.

You can make that push work by doing git push origin issue1677 -f (note the -f, which will force it to overwrite what's already there).  Make sure this is what you want, though, since it will overwrite the commit(s) on Github.

I recommit it again after fixing it by your instruction.
But, even though the commit is finished, it didn't show anything on mozilla/brackets.

amended by request

@humphd I'm not sure when the Page.reload event is triggered. But shouldn't we force reload only for Page.navigate events?

Yes, only for Page.navigate.

Thanks for the contribution @tonypark0403!


update username and claims on each login

added support for updating the username for the user on login.
refactored some stuff around the user login flow (UserLoginManager specifically)
regenerate the claims on each login for the user

This change is

Looks good outside of the few minor comments I made.  One other general comment, I think we still need a better way to deal with the test users. It would be nice if we didn't have to branch our logic based on that.

Reviewed 10 of 10 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Fabric.Identity.API/DocumentDbStores/DocumentDbUserStore.cs, line 46 at r1 (raw file):

            var encodedSubjectId = UrlEncodeString(user.SubjectId);
            _documentDbService.AddDocument($"{encodedSubjectId}:{encodedProvider}", user);
            _logger.Debug($"added user: {user.SubjectId}");

it might be helpful to add some more information to the debug log when adding a user, perhaps the claims would be good to write out here.

Fabric.Identity.API/Management/UserLoginManager.cs, line 154 at r1 (raw file):

        }

        //private ICollection<Claim> UpdateClaims(ICollection<Claim> existingClaims, ICollection<Claim> updatedClaims)

Can we remove this commented code?

Fabric.Identity.API/Models/User.cs, line 36 at r1 (raw file):

    }

    public static class TestUserExtensions

Should we move this class to its own file?

Comments from Reviewable

@michaelvidal24 thanks for the feedback. Ahh yeah i forgot to delete the commented out code, thats what I get for rushing before lunch. I will also extend the logging for a new user and put the TestUserExtension class in its own file

Reviewed 4 of 4 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable


Email being sent from unpublished IP ranges

The web service which publishes the Exchange Online Protection IP ranges found here:
https://docs.microsoft.com/en-us/office365/enterprise/office-365-ip-web-service
Currently reports the latest worldwide version as<PHONE_NUMBER> which reports the following ranges for inbound connections on port 25.  I have firewalls configured based on this information.
...
{
"id": 10,
"serviceArea": "Exchange",
"serviceAreaDisplayName": "Exchange Online",
"urls": [
"*.mail.protection.outlook.com"
],
"ips": [
"<IP_ADDRESS>/15",
"<IP_ADDRESS>/16",
"<IP_ADDRESS>/14",
"<IP_ADDRESS>/17",
"2a01:111:f400::/48",
"2a01:111:f403::/48"
],
"tcpPorts": "25",
"expressRoute": true,
"category": "Allow",
"required": true
}
...
On 19th March I found email being sent from an IP address not listed in the ranges above (I have anonymised the log message):
Mar 19 21:30:17<EMAIL_ADDRESS>relay=mail-am6eur05rlyn2067.outbound.protection.outlook.com [<IP_ADDRESS>]
Can someone confirm what I'm seeing and/or update the documentation, I have multiple customers reporting emails missing and/or not being received and they configure their firewalls based on the IP ranges published via the web service.

Adding @pandrew1

The web service referenced here is for configuring network perimeter devices for client machine outbound to Office 365 service filtering. It is not provided as a comprehensive list of all Office 365 IP Addresses.

Thanks for the reply. I've slightly mis-understood then.  And in which case where is the list of IP ranges or URIs that can be referenced in order to configure network perimeter devices for inbound connections from EOP on port 25?

You can run this command to get the current IP Addresses for inbound SMTP validation: nslookup -type=TXT spf.protection.outlook.com
Please review this article for more information on Sender Policy Framework: https://docs.microsoft.com/microsoft-365/security/office-365-security/how-office-365-uses-spf-to-prevent-spoofing

Well that does make perfect sense, thank you.  However that nslookup does return the exact same IP ranges as the web service.
Also it doesn't explain why on March 19th as per my original message, mail was reported by customers as missing or not received.  I investigated and could see connection attempts on port 25 from other unpublished IP addresses in the 40.95.x.x range.  Once unblocked the missing email was delivered.
My guess is this is some sort of overflow or capacity issue as a result of the recent additional load on Office365 (Teams etc)?
However now I don't know how to configure the network perimeter devices for fear of email being missed, delayed or even lost.
(Please note I am grateful for your responses, I fully appreciate you have answered my original question and this may now be outside the scope of the Office Docs Enterprise)

@jimjimbojimbob I got an answer for you. These IP Addresses should not be in the SPF detail.
These IPs are used to send very specific type of mail: outbound messages where sender domains do not belong to the customers who sent them. We cannot block that mail altogether because of some legit auto-forwarding scenarios, but we cannot make that mail look authenticated from the receivers’ POV because that opens up a cross-customer spoofing vulnerability.

@jimjimbojimbob - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by pandrew1 so we will close this issue.
Thank you for your contribution to make the docs better! Much appreciated!


No control of MEC unit & unusual current state

Build, flash and Wifi capture portal OK.
HomeKit setup from iPhone OK.
Gets unusually low current temperature reading when I 'turn on' from Home app.
Can't change modes or any other controls.
Some control changes in Home app appear to cause a crash?
Partial extract of serial log below.
[Jan 12 13:47:24.692] Main.c:179              Tock uptime: 37.36, RAM: 35536, 25216 free
[Jan 12 13:47:25.208] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling write handler.
[Jan 12 13:47:25.219] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateWrite: 2
[Jan 12 13:47:25.225] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.228] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.234] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.237] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.244] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.250] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.253] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.259] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:25.268] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:25.277] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:25.286] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:25.297] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:47:25.303] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:25.312] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:47:25.318] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:25.329] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:47:25.335] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:25.347] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:25.350] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:25.361] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:25.368] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:25.380] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:25.384] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:25.395] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:25.415] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:25.423] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:25.432] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:25.443] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:47:25.450] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:25.458] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:47:25.465] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:25.476] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:47:25.482] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:25.493] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:25.497] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:25.508] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:25.515] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:25.526] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:25.530] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:25.541] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:25.562] mgos_mongoose.c:66      New heap free LWM: 21896
[Jan 12 13:47:25.692] Main.c:179              Tick uptime: 38.36, RAM: 35536, 25216 free
[Jan 12 13:47:26.692] Main.c:179              Tock uptime: 39.36, RAM: 35536, 25216 free
[Jan 12 13:47:27.692] Main.c:179              Tick uptime: 40.36, RAM: 35536, 25216 free
[Jan 12 13:47:28.660] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling write handler.
[Jan 12 13:47:28.671] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempWrite: 22.0
[Jan 12 13:47:28.676] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:28.680] heap integrity broken: block links don't match: 769 -> 772, but 772 -> 16816
[Jan 12 13:47:28.688]
[Jan 12 13:47:28.688] abort() @ 0x402634c0
[Jan 12 13:47:28.688]  A0: 0x402634c0  A1: 0x3ffffa50  A2: 0x00000023  A3: 0x3fff2c29
[Jan 12 13:47:28.693]  A4: 0x00000000  A5: 0x000000ff  A6: 0x3fff5b34  A7: 0x00000000
[Jan 12 13:47:28.699]  A8: 0x3fff3ba0  A9: 0x00000190 A10: 0x00000001 A11: 0x0000000a
[Jan 12 13:47:28.705] A12: 0x3fff2dd8 A13: 0x3ffee408 A14: 0x0000000c A15: 0x0000000c
[Jan 12 13:47:28.710]
[Jan 12 13:47:28.713] (exc SP: 0x3ffffa20)
[Jan 12 13:47:28.713]
[Jan 12 13:47:28.713] --- BEGIN CORE DUMP ---
[Jan 12 13:47:28.716] mos: catching core dump
[Jan 12 13:47:31.561] ....
[Jan 12 13:47:40.200] ---- END CORE DUMP ----

then tries to send core dump to docker(?) then reboots:
[Jan 12 13:47:40.200] rebooting
�
[Jan 12 13:47:40.200]  ets Jan  8 2013,rst cause:2, boot mode:(3,6)
[Jan 12 13:47:40.206]
[Jan 12 13:47:40.206] load 0x40100000, len 1544, room 16
[Jan 12 13:47:40.209] tail 8
[Jan 12 13:47:40.209] chksum 0xb6
[Jan 12 13:47:40.212] load 0x3ffe8000, len 748, room 0
[Jan 12 13:47:40.215] tail 12
[Jan 12 13:47:40.215] chksum 0x62
[Jan 12 13:47:40.215] csum 0x62

[Jan 12 13:47:40.218] rBoot v1.2.1-cesanta1 -<EMAIL_ADDRESS>[Jan 12 13:47:40.221] Flash Size:   32 Mbit
[Jan 12 13:47:40.223] Flash Mode:   DIO
[Jan 12 13:47:40.226] Flash Speed:  80 MHz
[Jan 12 13:47:40.226] rBoot Option: Big flash
[Jan 12 13:47:40.230]
[Jan 12 13:47:40.247] Booting rom 0 (0x100000).
[Jan 12 13:47:40.267] V2
[Jan 12 13:47:40.267] Mo
[Jan 12 13:47:40.307] ph����o��;��o<�$ddl`#��|r�l�n��n�d`��{�l�l�$`��r�d�l�l ��s�l���ld`{$��sl����c�
[Jan 12 13:47:40.319] esp_main.c:157          mel-ac-homekit 1.0.3 (20220111-065536)
[Jan 12 13:47:40.324] esp_main.c:159          Mongoose OS<PHONE_NUMBER>07 (20220111-065536/2.20.0-8-ga5af91af-master)
[Jan 12 13:47:40.333] esp_main.c:160          CPU: ESP8266EX, 160 MHz, RAM: 35536 total, 32900 free
[Jan 12 13:47:40.338] esp_main.c:164          SDK 3.0.5-dev(81bde69); flash: 4M
[Jan 12 13:47:40.344] esp_exc.c:240           Reset cause: 4 (soft reset)
[Jan 12 13:47:40.350] mongoose.c:15765        Mongoose 6.18, LwIP 1.4.0
[Jan 12 13:47:40.352] mongoose.c:4932         mbed TLS 2.16.11-cesanta1
[Jan 12 13:47:40.359] mgos_vfs_dev.c:72       sfl0: sysflash (), size 4194304
[Jan 12 13:47:40.365] mgos_vfs_dev.c:72       root: part ({"dev": "sfl0", "offset": 32768, "size": 262144}), size 262144
[Jan 12 13:47:40.374] mgos_vfs.c:173          /: SPIFFS @ root, opts {"bs":4096,"ps":256,"es":4096}
[Jan 12 13:47:40.425] mgos_vfs.c:344          /: size 233681, used: 22841, free: 210840
[Jan 12 13:47:40.521] mgos_sys_config.c:470   MAC: 52:02:91:c3:4a:00
[Jan 12 13:47:40.524] mgos_sys_config.c:478   WDT: 30 seconds
[Jan 12 13:47:40.527] esp_main.c:137          SDK: del if0
[Jan 12 13:47:40.530] esp_main.c:137          SDK: usl
[Jan 12 13:47:40.533] esp_main.c:137          SDK: mode : null
[Jan 12 13:47:40.538] mgos_wifi.c:360         WiFi mode: STA
[Jan 12 13:47:40.542] mgos_dns_sd.c:543       DNS-SD initialized, host esp8266-C34A00.local, adv intvl 29693
[Jan 12 13:47:40.551] mgos_http_server.c:370  HTTP server started on [80]
[Jan 12 13:47:40.557] Main.c:399              Starting services...
[Jan 12 13:47:40.566] HAPPlatformLog.c:55     AccessoryServer Version information:
[Jan 12 13:47:40.569] libhap: https://github.com/mongoose-os-libs/homekit-adk
[Jan 12 13:47:40.574]   - Version: 1.0.1 (Jan 11 2022 06:55:32) - compatibility version 7
[Jan 12 13:47:40.580] Using platform: Mongoose OS
[Jan 12 13:47:40.583]   - Version: 1.0.3 (20220111-065536) - compatibility version 7
[Jan 12 13:47:40.588]   - Available features:
[Jan 12 13:47:40.591]     - Key-Value store
[Jan 12 13:47:40.594]     - Accessory setup manager
[Jan 12 13:47:40.598]     - Service discovery
[Jan 12 13:47:40.598] HAPPlatformLog.c:55     HAP AppCreate
[Jan 12 13:47:40.607] HAPPlatformLog.c:55     AccessoryServer Accessory server starting.
[Jan 12 13:47:40.672] HAPPlatformTCPStrea:187 Listening on 9000
[Jan 12 13:47:40.675] HAPPlatformLog.c:55     IPServiceDiscovery Registering _hap._tcp service.
[Jan 12 13:47:40.681] reset_btn.c:79          Factory reset button: pin 0, pull up, hold_ms 5000 (long press)
[Jan 12 13:47:40.690] mgos_init.c:33          Init done, RAM: 35536 total, 28284 free, 27784 min free
[Jan 12 13:47:40.697] HAPPlatformLog.c:55     HAP Accessory Server State did update: Running.
[Jan 12 13:47:40.707] mgos_wifi_sta.c:608     Trying A11 AP 78:8a:20:2d:0f:ce ch 11 RSSI  0 cfg 0 att 1
[Jan 12 13:47:40.713] esp_wifi.c:123          WiFi mode: STA
[Jan 12 13:47:40.717] esp_main.c:137          SDK: mode : sta(50:02:91:c3:4a:00)
[Jan 12 13:47:40.723] esp_main.c:137          SDK: add if0
[Jan 12 13:47:40.726] esp_main.c:137          SDK: sleep disable
[Jan 12 13:47:40.735] mgos_mongoose.c:66      New heap free LWM: 26888
[Jan 12 13:47:40.739] Main.c:146              WiFi STA connecting 0x0
[Jan 12 13:47:40.746] mgos_net.c:89           WiFi STA: connecting
[Jan 12 13:47:40.748] Main.c:121              Net connecting...
[Jan 12 13:47:40.855] esp_main.c:137          SDK: scandone
[Jan 12 13:47:41.743] esp_main.c:137          SDK: state: 0 -> 2 (b0)
[Jan 12 13:47:41.749] Main.c:179              Tock uptime: 1.54, RAM: 35536, 28216 free
[Jan 12 13:47:41.755] esp_main.c:137          SDK: state: 2 -> 3 (0)
[Jan 12 13:47:41.766] esp_main.c:137          SDK: state: 3 -> 5 (10)
[Jan 12 13:47:41.769] esp_main.c:137          SDK: add 0
[Jan 12 13:47:41.771] esp_main.c:137          SDK: aid 2
[Jan 12 13:47:41.774] esp_main.c:137          SDK: cnt
[Jan 12 13:47:41.788] esp_main.c:137          SDK:
[Jan 12 13:47:41.788] esp_main.c:137          SDK: connected with A11, channel 11
[Jan 12 13:47:41.794] esp_main.c:137          SDK: dhcp client start...
[Jan 12 13:47:41.801] mgos_mongoose.c:66      New heap free LWM: 26712
[Jan 12 13:47:41.804] mgos_wifi.c:83          WiFi STA: Connected, BSSID 78:8a:20:2d:0f:ce ch 11 RSSI -77
[Jan 12 13:47:41.813] Main.c:149              WiFi STA connected 0x0
[Jan 12 13:47:41.819] mgos_net.c:93           WiFi STA: connected
[Jan 12 13:47:41.822] Main.c:124              Net connected
[Jan 12 13:47:42.566] Main.c:179              Tick uptime: 2.36, RAM: 35536, 27520 free
[Jan 12 13:47:43.566] Main.c:179              Tock uptime: 3.36, RAM: 35536, 27520 free
[Jan 12 13:47:44.347] esp_main.c:137          SDK: ip:<IP_ADDRESS>,mask:<IP_ADDRESS>,gw:<IP_ADDRESS>
[Jan 12 13:47:44.354] Main.c:152              WiFi STA IP acquired: <IP_ADDRESS>
[Jan 12 13:47:44.360] mgos_net.c:103          WiFi STA: ready, IP <IP_ADDRESS>, GW <IP_ADDRESS>, DNS <IP_ADDRESS>, NTP <IP_ADDRESS>
[Jan 12 13:47:44.369] Main.c:127              Net got IP address
[Jan 12 13:47:44.376] mgos_mdns.c:143         Listening on udp://:5353... 0x3fff526c
[Jan 12 13:47:44.384] mgos_mongoose.c:66      New heap free LWM: 25584
[Jan 12 13:47:44.566] Main.c:179              Tick uptime: 4.36, RAM: 35536, 27232 free
[Jan 12 13:47:45.545] HAPPlatformTCPStrea:121 0x3fff5744 <IP_ADDRESS>:50035 Incoming HAP connection, ns 0/0/16
[Jan 12 13:47:45.551] HAPPlatformTCPStrea:276 0x3fff5744 <IP_ADDRESS>:50035 Accepted HAP connection, ns 0/1/16 ts 0x3fff5524
[Jan 12 13:47:46.316] mgos_mongoose.c:66      New heap free LWM: 24752
[Jan 12 13:47:46.324] Main.c:179              Tock uptime: 6.11, RAM: 35536, 26476 free
[Jan 12 13:47:46.531] HAPPlatformLog.c:55     PairingPairVerify Pair Verify procedure completed (pairing ID 0).
[Jan 12 13:47:46.542] mgos_mongoose.c:66      New heap free LWM: 24400
[Jan 12 13:47:46.566] Main.c:179              Tick uptime: 6.36, RAM: 35536, 26232 free
[Jan 12 13:47:46.583] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000003 manufacturer] Calling read handler.
[Jan 12 13:47:46.593] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000004 model] Calling read handler.
[Jan 12 13:47:46.620] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000005 name] Calling read handler.
[Jan 12 13:47:46.654] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000006 serial-number] Calling read handler.
[Jan 12 13:47:46.680] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000007 firmware.revision] Calling read handler.
[Jan 12 13:47:46.689] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000008 hardware.revision] Calling read handler.
[Jan 12 13:47:46.719] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000009 adk-version] Calling read handler.
[Jan 12 13:47:46.771] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000001012 version] Calling read handler.
[Jan 12 13:47:46.798] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:46.810] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 0
[Jan 12 13:47:46.831] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling read handler.
[Jan 12 13:47:46.842] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateRead: 0
[Jan 12 13:47:46.866] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000134 temperature.current] Calling read handler.
[Jan 12 13:47:46.878] HAPPlatformLog.c:55     HAP HandleThermostatCurrentTempRead: 2.0
[Jan 12 13:47:46.905] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:46.914] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:46.954] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [000000000000013A temperature.units] Calling read handler.
[Jan 12 13:47:46.963] HAPPlatformLog.c:55     HAP HandleThermostatTemperatureDisplayUnitsRead: 0
[Jan 12 13:47:46.989] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [000000000000013B status-active] Calling read handler.
[Jan 12 13:47:46.998] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:47.021] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:47.029] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 0
[Jan 12 13:47:47.057] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:47.065] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 0
[Jan 12 13:47:47.566] Main.c:179              Tock uptime: 7.36, RAM: 35536, 26280 free
[Jan 12 13:47:47.654] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:47.662] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:47.695] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:47.703] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:47.733] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000437 status-active] Calling read handler.
[Jan 12 13:47:47.742] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:47.776] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000332 name] Calling read handler.
[Jan 12 13:47:47.804] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000333 slat.state.current] Calling read handler.
[Jan 12 13:47:47.812] HAPPlatformLog.c:55     HAP HandleVaneHorizCurrentStateRead: 0
[Jan 12 13:47:47.837] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000334 type.slat] Calling read handler.
[Jan 12 13:47:47.845] HAPPlatformLog.c:55     HAP HandleVaneHorizTypeRead: 0
[Jan 12 13:47:47.875] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000335 tilt.current] Calling read handler.
[Jan 12 13:47:47.883] HAPPlatformLog.c:55     HAP HandleVaneHorizCurrentTiltAngleRead: 0
[Jan 12 13:47:47.914] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000336 tilt.target] Calling read handler.
[Jan 12 13:47:47.922] HAPPlatformLog.c:55     HAP HandleVaneHorizTargetTiltAngleRead: 0
[Jan 12 13:47:47.949] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000337 swing-mode] Calling read handler.
[Jan 12 13:47:47.957] HAPPlatformLog.c:55     HAP HandleVaneHorizSwingModeRead: 0
[Jan 12 13:47:47.983] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000338 status-active] Calling read handler.
[Jan 12 13:47:47.992] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:48.033] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000232 name] Calling read handler.
[Jan 12 13:47:48.042] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000233 slat.state.current] Calling read handler.
[Jan 12 13:47:48.053] HAPPlatformLog.c:55     HAP HandleVaneVertCurrentStateRead: 0
[Jan 12 13:47:48.082] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000234 type.slat] Calling read handler.
[Jan 12 13:47:48.091] HAPPlatformLog.c:55     HAP HandleVaneVertTypeRead: 1
[Jan 12 13:47:48.123] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000235 tilt.current] Calling read handler.
[Jan 12 13:47:48.131] HAPPlatformLog.c:55     HAP HandleVaneVertCurrentTiltAngleRead: -90
[Jan 12 13:47:48.155] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000236 tilt.target] Calling read handler.
[Jan 12 13:47:48.163] HAPPlatformLog.c:55     HAP HandleVaneVertTargetTiltAngleRead: -90
[Jan 12 13:47:48.187] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000237 swing-mode] Calling read handler.
[Jan 12 13:47:48.195] HAPPlatformLog.c:55     HAP HandleVaneVertSwingModeRead: 0
[Jan 12 13:47:48.217] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000238 status-active] Calling read handler.
[Jan 12 13:47:48.226] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:48.259] HAPPlatformTCPStrea:121 0x3fff5a3c <IP_ADDRESS>:49856 Incoming HAP connection, ns 0/1/16
[Jan 12 13:47:48.264] HAPPlatformTCPStrea:276 0x3fff5a3c <IP_ADDRESS>:49856 Accepted HAP connection, ns 0/2/16 ts 0x3fff5884
[Jan 12 13:47:49.052] mgos_mongoose.c:66      New heap free LWM: 23792
[Jan 12 13:47:49.062] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000532 name] Calling read handler.
[Jan 12 13:47:49.076] Main.c:179              Tick uptime: 8.87, RAM: 35536, 25648 free
[Jan 12 13:47:49.101] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:49.110] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:49.116] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000534 status-active] Calling read handler.
[Jan 12 13:47:49.127] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:49.296] HAPPlatformLog.c:55     PairingPairVerify Pair Verify procedure completed (pairing ID 0).
[Jan 12 13:47:49.307] mgos_mongoose.c:66      New heap free LWM: 23440
[Jan 12 13:47:49.336] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000003 manufacturer] Calling read handler.
[Jan 12 13:47:49.346] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000004 model] Calling read handler.
[Jan 12 13:47:49.362] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000632 name] Calling read handler.
[Jan 12 13:47:49.388] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:49.396] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:49.403] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000634 status-active] Calling read handler.
[Jan 12 13:47:49.414] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:49.456] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000005 name] Calling read handler.
[Jan 12 13:47:49.479] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000007 firmware.revision] Calling read handler.
[Jan 12 13:47:49.502] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000006 serial-number] Calling read handler.
[Jan 12 13:47:49.569] mgos_mongoose.c:66      New heap free LWM: 22448
[Jan 12 13:47:49.576] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000007 firmware.revision] Calling read handler.
[Jan 12 13:47:49.586] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000008 hardware.revision] Calling read handler.
[Jan 12 13:47:49.604] Main.c:179              Tock uptime: 9.39, RAM: 35536, 25268 free
[Jan 12 13:47:49.631] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000009 adk-version] Calling read handler.
[Jan 12 13:47:49.710] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000001012 version] Calling read handler.
[Jan 12 13:47:49.759] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:49.771] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 0
[Jan 12 13:47:49.830] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling read handler.
[Jan 12 13:47:49.841] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateRead: 0
[Jan 12 13:47:49.888] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000134 temperature.current] Calling read handler.
[Jan 12 13:47:49.900] HAPPlatformLog.c:55     HAP HandleThermostatCurrentTempRead: 2.0
[Jan 12 13:47:49.939] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:49.947] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:50.059] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [000000000000013A temperature.units] Calling read handler.
[Jan 12 13:47:50.067] HAPPlatformLog.c:55     HAP HandleThermostatTemperatureDisplayUnitsRead: 0
[Jan 12 13:47:50.136] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [000000000000013B status-active] Calling read handler.
[Jan 12 13:47:50.144] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:50.178] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:50.186] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 0
[Jan 12 13:47:50.249] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:50.257] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 0
[Jan 12 13:47:50.355] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:50.363] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:50.414] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:50.423] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:50.461] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000437 status-active] Calling read handler.
[Jan 12 13:47:50.470] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:50.526] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000332 name] Calling read handler.
[Jan 12 13:47:50.566] Main.c:179              Tick uptime: 10.36, RAM: 35536, 25272 free
[Jan 12 13:47:50.576] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000333 slat.state.current] Calling read handler.
[Jan 12 13:47:50.585] HAPPlatformLog.c:55     HAP HandleVaneHorizCurrentStateRead: 0
[Jan 12 13:47:50.620] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000334 type.slat] Calling read handler.
[Jan 12 13:47:50.629] HAPPlatformLog.c:55     HAP HandleVaneHorizTypeRead: 0
[Jan 12 13:47:50.692] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000335 tilt.current] Calling read handler.
[Jan 12 13:47:50.700] HAPPlatformLog.c:55     HAP HandleVaneHorizCurrentTiltAngleRead: 0
[Jan 12 13:47:50.776] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000336 tilt.target] Calling read handler.
[Jan 12 13:47:50.784] HAPPlatformLog.c:55     HAP HandleVaneHorizTargetTiltAngleRead: 0
[Jan 12 13:47:50.838] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000337 swing-mode] Calling read handler.
[Jan 12 13:47:50.847] HAPPlatformLog.c:55     HAP HandleVaneHorizSwingModeRead: 0
[Jan 12 13:47:50.902] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000338 status-active] Calling read handler.
[Jan 12 13:47:50.910] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:50.961] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000232 name] Calling read handler.
[Jan 12 13:47:50.970] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000233 slat.state.current] Calling read handler.
[Jan 12 13:47:50.982] HAPPlatformLog.c:55     HAP HandleVaneVertCurrentStateRead: 0
[Jan 12 13:47:51.019] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000234 type.slat] Calling read handler.
[Jan 12 13:47:51.027] HAPPlatformLog.c:55     HAP HandleVaneVertTypeRead: 1
[Jan 12 13:47:51.089] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000235 tilt.current] Calling read handler.
[Jan 12 13:47:51.097] HAPPlatformLog.c:55     HAP HandleVaneVertCurrentTiltAngleRead: -90
[Jan 12 13:47:51.148] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000236 tilt.target] Calling read handler.
[Jan 12 13:47:51.157] HAPPlatformLog.c:55     HAP HandleVaneVertTargetTiltAngleRead: -90
[Jan 12 13:47:51.218] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000237 swing-mode] Calling read handler.
[Jan 12 13:47:51.226] HAPPlatformLog.c:55     HAP HandleVaneVertSwingModeRead: 0
[Jan 12 13:47:51.272] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000238 status-active] Calling read handler.
[Jan 12 13:47:51.280] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:51.404] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000532 name] Calling read handler.
[Jan 12 13:47:51.451] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:51.459] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:51.465] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000534 status-active] Calling read handler.
[Jan 12 13:47:51.477] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:51.550] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000632 name] Calling read handler.
[Jan 12 13:47:51.566] Main.c:179              Tock uptime: 11.36, RAM: 35536, 25272 free
[Jan 12 13:47:51.635] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:51.644] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:51.650] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000634 status-active] Calling read handler.
[Jan 12 13:47:51.661] HAPPlatformLog.c:55     HAP HandleStatusActiveRead: true
[Jan 12 13:47:51.777] esp_main.c:137          SDK: pm open,type:0 0
[Jan 12 13:47:51.848] mgos_mongoose.c:66      New heap free LWM: 22400
[Jan 12 13:47:51.885] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling write handler.
[Jan 12 13:47:51.897] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempWrite: 21.0
[Jan 12 13:47:51.903] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:51.913] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:51.921] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:52.566] Main.c:179              Tick uptime: 12.36, RAM: 35536, 25224 free
[Jan 12 13:47:53.566] Main.c:179              Tock uptime: 13.36, RAM: 35536, 25224 free
[Jan 12 13:47:54.566] Main.c:179              Tick uptime: 14.36, RAM: 35536, 25224 free
[Jan 12 13:47:55.210] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling write handler.
[Jan 12 13:47:55.221] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateWrite: 2
[Jan 12 13:47:55.227] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.230] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.236] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.239] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.245] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.251] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.255] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.261] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:47:55.270] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:55.279] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:55.288] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:55.299] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:47:55.305] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:55.314] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:47:55.320] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:55.331] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:47:55.337] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:55.349] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:55.352] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:55.363] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:55.370] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:55.382] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:55.386] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:55.397] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:55.417] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:47:55.425] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:47:55.434] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:47:55.446] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:47:55.452] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:47:55.460] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:47:55.467] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:47:55.478] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:47:55.484] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:47:55.495] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:47:55.499] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:47:55.510] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:47:55.517] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:47:55.528] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:47:55.532] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:47:55.544] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:47:55.564] mgos_mongoose.c:66      New heap free LWM: 21896
[Jan 12 13:47:55.574] mgos_mongoose.c:66      New heap free LWM: 20376
[Jan 12 13:47:55.578] Main.c:179              Tock uptime: 15.37, RAM: 35536, 22516 free
[Jan 12 13:47:56.566] Main.c:179              Tick uptime: 16.36, RAM: 35536, 25224 free
[Jan 12 13:47:57.566] Main.c:179              Tock uptime: 17.36, RAM: 35536, 25224 free
[Jan 12 13:47:58.566] Main.c:179              Tick uptime: 18.36, RAM: 35536, 25224 free
[Jan 12 13:47:59.566] Main.c:179              Tock uptime: 19.36, RAM: 35536, 25224 free
[Jan 12 13:48:00.566] Main.c:179              Tick uptime: 20.36, RAM: 35536, 25224 free
[Jan 12 13:48:01.566] Main.c:179              Tock uptime: 21.36, RAM: 35536, 25224 free
[Jan 12 13:48:02.566] Main.c:179              Tick uptime: 22.36, RAM: 35536, 25224 free
[Jan 12 13:48:02.578] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling write handler.
[Jan 12 13:48:02.586] HAPPlatformLog.c:55     HAP HandleModeDryOnWrite: true
[Jan 12 13:48:02.592] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.595] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.601] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.607] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.611] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.617] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.620] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.626] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.629] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:02.640] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:48:02.649] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:48:02.658] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:48:02.669] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 0
[Jan 12 13:48:02.675] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling read handler.
[Jan 12 13:48:02.686] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateRead: 0
[Jan 12 13:48:02.693] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:48:02.701] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:48:02.707] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:48:02.719] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:48:02.725] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:48:02.736] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:48:02.740] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:48:02.751] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:48:02.758] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:48:02.769] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:48:02.773] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:48:02.784] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: true
[Jan 12 13:48:02.805] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:48:02.814] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:48:02.823] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:48:02.834] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 0
[Jan 12 13:48:02.840] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling read handler.
[Jan 12 13:48:02.851] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateRead: 0
[Jan 12 13:48:02.858] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:48:02.866] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:48:02.872] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:48:02.883] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:48:02.890] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:48:02.901] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:48:02.905] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:48:02.916] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:48:02.923] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:48:02.934] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:48:03.566] Main.c:179              Tock uptime: 23.36, RAM: 35536, 25224 free
[Jan 12 13:48:04.566] Main.c:179              Tick uptime: 24.36, RAM: 35536, 25224 free
[Jan 12 13:48:05.566] Main.c:179              Tock uptime: 25.36, RAM: 35536, 25224 free
[Jan 12 13:48:06.565] Main.c:179              Tick uptime: 26.36, RAM: 35536, 25224 free
[Jan 12 13:48:07.566] Main.c:179              Tock uptime: 27.36, RAM: 35536, 25224 free
[Jan 12 13:48:08.565] Main.c:179              Tick uptime: 28.36, RAM: 35536, 25224 free
[Jan 12 13:48:09.482] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000137 heating-cooling.target] Calling write handler.
[Jan 12 13:48:09.493] HAPPlatformLog.c:55     HAP HandleThermostatTargetHCstateWrite: 2
[Jan 12 13:48:09.498] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.501] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.508] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.511] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.517] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.523] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.526] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.533] HAPPlatformLog.c:55     HAP Accessory Notification
[Jan 12 13:48:09.542] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:48:09.550] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:48:09.559] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:48:09.571] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:48:09.577] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:48:09.585] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:48:09.592] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:48:09.603] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:48:09.609] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:48:09.620] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:48:09.624] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:48:09.635] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:48:09.642] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:48:09.653] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:48:09.657] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:48:09.669] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:48:09.688] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000135 temperature.target] Calling read handler.
[Jan 12 13:48:09.697] HAPPlatformLog.c:55     HAP HandleThermostatTargetTempRead: 16.0
[Jan 12 13:48:09.706] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000136 heating-cooling.current] Calling read handler.
[Jan 12 13:48:09.717] HAPPlatformLog.c:55     HAP HandleThermostatCurrentHCstateRead: 2
[Jan 12 13:48:09.724] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000433 active] Calling read handler.
[Jan 12 13:48:09.732] HAPPlatformLog.c:55     HAP HandleFanActiveRead: 1
[Jan 12 13:48:09.738] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000434 fan.state.current] Calling read handler.
[Jan 12 13:48:09.749] HAPPlatformLog.c:55     HAP HandleFanCurrentStateRead: 2
[Jan 12 13:48:09.756] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000435 fan.state.target] Calling read handler.
[Jan 12 13:48:09.767] HAPPlatformLog.c:55     HAP HandleFanTargetStateRead: 0
[Jan 12 13:48:09.771] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000436 rotation.speed] Calling read handler.
[Jan 12 13:48:09.782] HAPPlatformLog.c:55     HAP HandleFanRotationSpeedRead: 0.000000
[Jan 12 13:48:09.789] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000533 on] Calling read handler.
[Jan 12 13:48:09.800] HAPPlatformLog.c:55     HAP HandleModeFanOnRead: false
[Jan 12 13:48:09.804] HAPPlatformLog.c:55     Characteristic [0000000000000001 MEL-4A00] [0000000000000633 on] Calling read handler.
[Jan 12 13:48:09.815] HAPPlatformLog.c:55     HAP HandleModeDryOnRead: false
[Jan 12 13:48:09.840] Main.c:179              Tock uptime: 29.63, RAM: 35536, 23568 free
[Jan 12 13:48:10.566] Main.c:179              Tick uptime: 30.36, RAM: 35536, 25224 free
[Jan 12 13:48:11.565] Main.c:179              Tock uptime: 31.36, RAM: 35536, 25224 free
[Jan 12 13:48:12.566] Main.c:179              Tick uptime: 32.36, RAM: 35536, 25224 free
[Jan 12 13:48:13.565] Main.c:179              Tock uptime: 33.36, RAM: 35536, 25224 free
[Jan 12 13:48:14.565] Main.c:179              Tick uptime: 34.36, RAM: 35536, 25224 free
[Jan 12 13:48:15.565] Main.c:179              Tock uptime: 35.36, RAM: 35536, 25224 free
[Jan 12 13:48:16.565] Main.c:179              Tick uptime: 36.36, RAM: 35536, 25224 free
[Jan 12 13:48:17.565] Main.c:179              Tock uptime: 37.36, RAM: 35536, 25224 free

Have successfully used this MEC unit, ESP8266 (Wemos D1) and wiring with SwiCago's heat pump code to control, so unlikely hardware is the problem?
If it is preferred this is not created as an issue, but should be discussed elsewhere, let me know and I will delete.

Hi
I guess the UART number is the problem
Check mos.yml file for mel_ac.uart_no and change to 0
Enjoy it

Yes, that worked. Tested and working, many thanks!


Add support for fetching ways from overpass and save as fetaure in db

Currently localizer only supports fetching nodes form the overpass query. Add support for ways and relations (if required)

closed by #39


cpprestsdk Failed massage

i didn't found solution for this. Always gave to me  this error.
PS C:\vcpkg-master> .\vcpkg.exe install cpprestsdk cpprestsdk:x64-windows
Computing installation plan...
The following packages will be built and installed:

brotli[core]:x86-windows
brotli[core]:x64-windows
cpprestsdk[brotli,compression,core,default-features,websockets]:x64-windows
cpprestsdk[brotli,compression,core,default-features,websockets]:x86-windows
websocketpp[core]:x64-windows
websocketpp[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/6: brotli:x86-windows
Building package brotli[core]:x86-windows...
-- Using cached C:/vcpkg-master/downloads/google-brotli-v1.0.7.tar.gz
-- Using source at C:/vcpkg-master/buildtrees/brotli/src/v1.0.7-bf01b84227
-- Configuring x86-windows
-- Building x86-windows-dbg
-- Building x86-windows-rel
-- Installing: C:/vcpkg-master/packages/brotli_x86-windows/share/brotli/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package brotli[core]:x86-windows... done
Installing package brotli[core]:x86-windows...
Failed at [C:\vcpkg-master\toolsrc\src\vcpkg\vcpkglib.cpp(216)] with message:
no such file or directory

@RageLog Thanks for posting this issue. Do you can install other ports successfully?

No, i couldnt install but i found a solution that, remove all instalition of vcpkg(and of course api) and install again.

Thanks for your issue. This issue has been solved, so I am closing this issue for now.


Easy fuzz

Copies and adapts the fuzzer setup from rust-bitcoin. Updates our fuzzing CI. Fixes #117.
There are some open problems (see wip commits):
Readme

[x] Should we remove the section on weak cryptography if it breaks our Merkle roots? We use a fork of bitcoin-hashes so that part is already impossible to weaken.
[x] HFUZZ_BUILD_ARGS='--features honggfuzz_fuzz' cargo hfuzz run <target> doesn't work on my machine. I have to drop the HFUZZ_BUILD_ARGS part.

error: Package simplicity-fuzz v0.0.1 does not have the feature honggfuzz_fuzz
Is that outdated documentation, or do I have to change my local setup?

[x] I cannot reproduce failures as shown. When a fuzz test fails it merely increments the error counter and continues. The files in hfuzz_workspace/ look like the expected output, but there is no hex value below the == line

Generate CI

[x] Anything that needs to be changed to work with Simplicity?
[x] Test unit tests in fuzz crate? (Was disabled by generate-fuzz.sh)

Should we remove the section on weak cryptography if it breaks our Merkle roots? We use a fork of bitcoin-hashes so that part is already impossible to weaken.

Yes, we should remove it. When the ability to weaken the crypto returns we still won't want to do it.

￼ HFUZZ_BUILD_ARGS='--features honggfuzz_fuzz' cargo hfuzz run  doesn't work on my machine. I have to drop the HFUZZ_BUILD_ARGS part.

Yeah, this is probably outdated in rust-bitcoin and has never applied to this crate.

￼ I cannot reproduce failures as shown. When a fuzz test fails it merely increments the error counter and continues. The files in hfuzz_workspace/ look like the expected output, but there is no hex value below the == line

What fuzztests are failing right now? In any case, if you are just running cargo hfuzz run you are not going to get the nice hex output. You need to run fuzz.sh for this. To get the hex output you need to find the crash files in hfuzz_workspace/<test>/SIG* and run them through xxd.

Fuzzing and error reports work for me now. I updated the README accordingly. (There are no fuzz tests that fail. I artificially made them fail.)
We could even push some of these updates to rust-bitcoin. I've separated the simplicity commits from the general ones.
I will open this for review.

Please confirm that the CI looks as it should.
One nuisance that we might want to fix is that checkReport kills the nix shell when it exists with an error. Has this even come up in rust-bitcoin?

I added getReport as a safe way to generate reports in the nix shell, and sorted the target in alphabetical orders.
File names with null characters and the like will not work, but those will probably be caught by the checkWindowsFiles check.
For me generate-files.sh is still clean. I could not reproduce your error. If this happens again, we need to debug this in more depth.

Done reviewing b50ad1c516789f64716b55529143471f4f0aff40

Rebased and addressed the comments:
No more fuzzing gates, fixed README, a better nix shell that installs honggfuzz, getReport for generating error reports without crashing the shell.

Could you rebase this so that

the new README is in one commit (ok to split this into 3, one that copies rust-bitcoin, one that tweaks it in upstreamable ways, and one that does rust-simplicity-specific stuff)
the new scripts are in one commit (ok to make this two, one that copies rust-bitcoin and one that tweaks it, if that makes it easier to upstream)
Then the 'unify duplicate_crash` commit could go anywhere.
Then deleting CI and running the the new scripts could be one commit, or two, your choice.

Right now this PR feels like it's updating the same files repeatedly in an unclear order, and it's hard to say, for any given problem, whether it's going to be fixed later or what.
In any case, #[cfg(fuzzing)] still appears in several places and in the README.

Done. Originally I kept the commits separate for upstream cherry picks, but I feel the upstream commits will require a lot of changes, so it's not worth the effort.

Done reviewing 38937d17d058cf6ebbb3477808ef2f0d126bba88. The rest looks good.

Addressed the comments.

Updated the README.

CI failure is unrelated serde stuff.


Faker Deprecation Warnings showing up in Rails Console

Describe the bug
Faker deprecation warnings show up in Rails console when trying to autocomplete DateTime.now.
Faker::Pokemon.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::ElderScrolls.name is deprecated; use Faker::Games::ElderScrolls.name instead. It will be removed on or after 2019-01-01.
Faker::ElderScrolls.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::Cat.name is deprecated; use Faker::Creature::Cat.name instead. It will be removed on or after 2019-01-01.
Faker::Cat.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::Dog.name is deprecated; use Faker::Creature::Dog.name instead. It will be removed on or after 2019-01-01.
Faker::Dog.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::RockBand.name is deprecated; use Faker::Music::RockBand.name instead. It will be removed on or after 2019-01-01.
Faker::RockBand.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::Pokemon.name is deprecated; use Faker::Games::Pokemon.name instead. It will be removed on or after 2019-01-01.
Faker::Pokemon.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::ElderScrolls.name is deprecated; use Faker::Games::ElderScrolls.name instead. It will be removed on or after 2019-01-01.
Faker::ElderScrolls.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::Cat.name is deprecated; use Faker::Creature::Cat.name instead. It will be removed on or after 2019-01-01.
Faker::Cat.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::Dog.name is deprecated; use Faker::Creature::Dog.name instead. It will be removed on or after 2019-01-01.
Faker::Dog.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.
NOTE: Faker::RockBand.name is deprecated; use Faker::Music::RockBand.name instead. It will be removed on or after 2019-01-01.
Faker::RockBand.name called from /home/aaron/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/irb/completion.rb:174.

To Reproduce
Should be easy to reproduce. Create a Rails application with Faker and run rails c then try to autocomplete DateTime.now. (to get beginning_of_hour method for example)
Expected behavior
This shouldn't be happening or possibly the deprecation warnings should be removed in next release?
Additional context
I'm using the current version (v 1.9.3)

These exact same warnings (ElderScrolls, Cat, Dog etc) show up when we run rspec tests.


don't parse an undefined message or body

Fixes #918
Fixes #919
We previously were trying to parse a non-existent response message and body. No more!

:dancer:


Update spsdk to 1.6.0

This patch updates the spsdk dependency to v1.6.0.  This leads to the
following changes:

spsdk now includes type annotations.
cryptography is bumped to 3.4.4 and now includes type annotations.
Slow firmware update on Linux is fixed.
Firmware update now shows a progress bar.

Fixes: https://github.com/Nitrokey/pynitrokey/issues/142

I would assume that it is about one minute faster, but no big improvement.  Not tested though.

spsdk v1.6.0 is not compatible with v1.5.0, so we should soon make a release that either contains this PR or changes the version requirement to ~= 1.5.0 to avoid pulling in v1.6.0.


Auth host mode and Traefik 2 without global intercept

I'm trying to test out the specific mix of:

Auth host mode
With Traefik 2.0
With the forwardauth middleware configured on a per-ingress level

The symptom is a redirect loop, when the IdP returns to /_oauth, that is seen as an unauthenticated request and so the response is to bounce back to the IdP. From looking through the code, it seems like AuthCallbackHandler is installed on the forward-auth router, rather than the top-level one. So the incoming URI is erased and replaced by X-Forwarded-Uri which doesn't exist since this request is coming through natively rather than via forwardauth itself. It seems like the best fix would be to move the callback handler to the top-level handler, but if not that then a simple fix would be to make RootHandler only do the X-Forwarded-Uri behavior if the header actually exists?
Does that sound reasonable?

I tested things out with this:
	if r.Header.Get("X-Forwarded-Method") != "" {
		r.Method = r.Header.Get("X-Forwarded-Method")
	}
	if r.Header.Get("X-Forwarded-Host") != "" {
		r.Host = r.Header.Get("X-Forwarded-Host")
	}
	if r.Header.Get("X-Forwarded-Uri") != "" {
		r.URL, _ = url.Parse(r.Header.Get("X-Forwarded-Uri"))
	}

and it seems much happier (though this can be rewritten to be faster, just wanted to check functionality).

I think this is the same issue as #81 and functionally the same solution.

So the solution to this is to ensure you're applying authentication to your tfa ingress, for example:
https://github.com/thomseddon/traefik-forward-auth/blob/c63fd738d698be0ac5ceebb803a67a6930d7bc48/examples/traefik-v2/kubernetes/advanced-separate-pod/traefik-forward-auth/ingress.yaml#L10-L20
(As a side note, this is documented in the README, but was missing from some of the examples, which was just fixed in #130 - thanks for pointing me to this!)
As an aside, I understand this is a slightly confusing setup when using selective authentication and it seems to have tripped quite a few people up. As such, I think it would actually make sense to gracefully support requests directly against the service, so I will leave this open to track that tweak.

PR open in #217


Behave like a shell

I'm wondering if I could make rtx behave like a shell, maybe if I detect it's being run as something like /usr/local/bin/rtx-bash.
That way in IDEs people don't need to figure out how to configure it to work with rtx beyond setting that as their shell which is generally easy to configure. It also provides an alternate way to use rtx via chsh.

It might be possible here to detect if it's interactive (I think it'll just be send the -i flag), and choose whether to go with shims or rtx activate


Tests in //tensorflow/core/distributed_runtime/... sometimes time out

Some of the tests in this directory (in particular, master_test and rpc/grpc_session_test) spawn subprocesses containing TensorFlow servers that listen on unused ports. There is a potential TOCTOU bug in this code because the process is:

Pick unused ports in the parent.
Fork processes and instruct them to bind to the picked ports. (At this point another process can bind the same ports.)
Connect to subprocesses from the parent.

Running these tests in exclusive mode is a workaround for the problem.

Nobody has complained about this for some time, so I'm going to close this bug. Famous last words....


Detail Pages Post Launch

[ ] Add VPC details to networking, disk details to storage
[ ] feat: Filter by EBS or only EBS + Dedicated but they are all still in same instance class so they should be displayed within
[x] feat: add ElastiCache
[x] Style homepage
[x] Style main pages with new navbar
[x] investigate main page layout shift
[x] feat: percentage discount from ondemand
[ ] feat: Instance release dates
[x] add query params to URL as pricing selector changes
[ ] feat: optionally reveal attribute key as it appears in the AWS API
[x] feat: comparable/similar instances
[x] feat: compare to button
[x] feat: add regions where spot is not available to region list
[ ] Move service_attributes CSV to yaml for simplification and link to same editing flow as links
[ ] 'attribute not supported' callout with option to open issue
[x] links should be per-variant, not per size
[x] bug: check for reserved availability in pricing widget js. Should be N/A instead of NaN
[x] find the closest matching variant to link to
[x] don't hide 'submit a link', rework copy based on Rishi feedback in the Vantage Slack
[x] make entire table cell clickable
[x] add back instance availability

hi @EverettBerry , I see that the percentage discount from on demand is marked as shipped however I cannot figure out how to display it on the website. Am I missing something? Thanks!


Patch *.sdk paths from pkgConfig files to the current SDK

This fixes #6439 by replacing all *.sdk paths obtained from pkgConfigs with the current SDK.
Motivation:
Using Homebrew-packaged libraries such as Cairo in a system library target on macOS currently causes build failures if the user compiles the Swift package with an Xcode toolchain (see swift-systemlib-demo and its CI builds for a minimal example), the build output often looks similar to this:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.0.sdk/usr/include/ffi/module.modulemap:1:8: error: redefinition of module 'FFI'
module FFI [system] [extern_c] {
       ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/ffi/module.modulemap:1:8: note: previously defined here
module FFI [system] [extern_c] {

The problem is that Homebrew's pre-compiled libraries sometimes bake the Command Line Tools-paths (/Library/Developer/CommandLineTools/SDKs/...) into their pkgConfig files, which can clash with the current SDK's headers.
See #6439 for details.
Modifications:
As per @neonichu's suggestion in https://github.com/apple/swift-package-manager/issues/6439#issuecomment-1511658768, this patches the include (-I) and library (-L) paths parsed from pkgConfig files by replacing any *.sdk path with the current SDK.
Thus a flag such as
-I/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/ffi

would be mapped to
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.3.sdk

when compiling with the macOS 13.3 SDK.
Result:
The swift-systemlib-demo package now compiles on macOS.

@fwcd sorry about the delay with the review, would you mind resolving the conflicts?

Sure, I've rebased it onto main!

@swift-ci test

@swift-ci test windows

@swift-ci test windows


change tracing implemented

Archiving documents on non-metadata field changes.
Capturing remote_user from admin panel.

#14 #13


Can't get to the description page of some locations in map domain

Hi there,
Recently I met a problem with map domain.
For example, if I type "Cafe near Hunt Library" in the map search domain. And enter the first choice, but the description page does not show up as the trace of 58.
Search:

After entering it:

However this is the screenshot from your playwright trace:

Could you kindly please check if there is problem with your aws server?
Best wishes.

I meet a same problem, as I click the choice, it turns out to be 'Not Found'. Have you solved it?

I meet a same problem, as I click the choice, it turns out to be 'Not Found'. Have you solved it?

Actually no. This kind of restricts the theoritical performance upper limit.


network: Always bind back physical interfaces

In case of physical network interfaces, we explicitly
pass through them to the VM. We need to bind them back to
the host driver when the sandbox is stopped, irrespective if
the network namespace has been created by virtcontainers or not.
Fixes #384
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>

PSS Measurement:
Qemu: 163786 KB
Proxy: 4747 KB
Shim: 10936 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  1996268 KB

PSS Measurement:
Qemu: 158018 KB
Proxy: 6685 KB
Shim: 11009 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  1996872 KB

@amshinde thanks for the PR, looks very good, and I agree the logic related to the fact that we have created or not the network namespace should be only affecting the removal of this network namespace.

@amshinde could you try to look into those CI issues ? They don't look like random issues, the patch might be the cause here.

@sboeuf I was seeing these unit tests failing in the last CI build for this PR:
=== RUN   TestStartStopSandboxHyperstartAgentSuccessfulWithCNINetwork
--- FAIL: TestStartStopSandboxHyperstartAgentSuccessfulWithCNINetwork (0.01s)
	cc_proxy_mock.go:80: [CCProxyMock] listening on /tmp/cc-proxy-test869276064/cc-proxy-test.sock
	api_test.go:1425: missing network name
	cc_proxy_mock.go:80: [CCProxyMock] Client connection already closed
	cc_proxy_mock.go:80: [CCProxyMock] Stopped
=== RUN   TestStartStopSandboxHyperstartAgentSuccessfulWithCNMNetwork
--- FAIL: TestStartStopSandboxHyperstartAgentSuccessfulWithCNMNetwork (0.00s)
	cc_proxy_mock.go:80: [CCProxyMock] listening on /tmp/cc-proxy-test430518911/cc-proxy-test.sock
	api_test.go:1463: sandbox 7f49d00d-1995-4156-8c79-5f5ab24ce138 exists
	cc_proxy_mock.go:80: [CCProxyMock] Client connection already closed
	cc_proxy_mock.go:80: [CCProxyMock] Stopped

This was introduced by this change in the CNI plugins repository:
https://github.com/containernetworking/plugins/commit/1f6e6ef198812a9a1257c43e314f9b1c92467767
This introduces a change requiring network name to be provided by the plugins, but the loopback plugin that we use in our tests has been been updated yet to include this as seen here :
https://github.com/containernetworking/plugins/commit/1f6e6ef198812a9a1257c43e314f9b1c92467767#diff-5a9f4821dfcce9f8ad9b7f8e616eeb7b
Since we we use the latest master in our virtcontainers setup script, our CI is failing with the error "missing network name".  So I introduced a change to use plugin binaries with the same version that we vendor in our runtime. Once this has been fixed upstream, we can update the vendoring and the setup script.

Tests issue raised for the CNI version issue: https://github.com/kata-containers/tests/issues/42.

@sboeuf @jodh-intel I have opened an issue upstream  to address the failure on latest master for CNI plugins:
https://github.com/containernetworking/plugins/issues/167
We can pull in the latest CNI plugins once the above issue is solved.
Meanwhile, can this PR be merged?


exact duplicates in annotations to term list

It isn't every term....
I can't remember which term I was looking at but you can see it from here
http://pombase2.aska.gen.nz/term/GO%3A0030989

here http://pombase2.aska.gen.nz/term/GO%3A0010971
(only affects nod1)

here the  deactivation of spindle checkpoint terms
http://pombase2.aska.gen.nz/term/GO%3A0045842
I can't see a pattern....

Definitely a bug in the web code as the duplicates aren't in Chado.  My guess is that there are multiple paths through the ontology from those descendant terms to whatever term you were viewing.  I'll investigate.

Should be fixed now.

I think there are still exact duplicates (or for phenotype maybe)

forgot to note the gene page

That example came from http://pombase2.bioinformatics.nz/gene/SPBC11B10.09
The alleles are identical too:

We think this is
Cell growth assay	cdc2	cdc2-M63 (G227C)	Not assayed	high temperature

cdc2	nmt::T167E (T167E)	Overexpression
Gould KL et al. (1998)
(multi allele cdc2 but both alleles are cdc2)


Fixes #311 - Fix improper null checking in FileParametersPlugin.getEnv()

This PR should fix #311. I would greatly appreciate a sanity check of my understanding of the problem, as described in that issue.

I think your change addresses the problem, but I think the problem should not have existed in the first place - at least, the test should not have gotten as far as executing getEnv().
Looking at the unit test itself, getEnv() should be getting mocked.  So the code you fixed should not even be getting executed.  https://github.com/manheim/terraform-pipeline/blob/master/test/FileParametersPluginTest.groovy#L69
It looks like there's a subtle problem in setting up the mock.  plugin is actually a spy and not a mock.  Mockito has a slightly different syntax for stubbing calls on a spy instead of a mock - because spies actually execute the underlying code.
https://www.javadoc.io/doc/org.mockito/mockito-core/1.10.19/org/mockito/Mockito.html#13
That means if the test itself it fixed to mock correctly, using the spy syntax of doReturn, the underlying method won't get called (and it shouldn't), and the mocked values will simply be returned:
doReturn([ OTHER_VARIABLE: 'VALUE1']).when(plugin).getEnv()

There's an additional problem of non-determinism here.  The fact that it didn't break when I ran it locally, means that some other test is setting Jenkinsfile.original to non-null, and not blanking that value out afterwards.

Codecov Report

Merging #312 (49f0b6d) into master (f80fbe1) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #312   +/-   ##
=======================================
  Coverage   78.98%   78.98%
=======================================
  Files          41       41
  Lines        1061     1061
  Branches      247      247
=======================================
  Hits          838      838
  Misses         99       99
  Partials      124      124

Impacted Files
Coverage Δ

src/FileParametersPlugin.groovy
18.75% <0.00%> (ø)

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 f80fbe1...49f0b6d. Read the comment docs.

I'm going to close this since the failure has been fixed by #313, though I'm still vaguely concerned (or confused) that we're performing the null check on the wrong object.


[EPIC] User experience

The NLP demo is to be transitioned into a public tool and it should have a user friendly workflow around selection of input files, and model parameters. Following issues should be completed:

[X] Setting up a new experiment #164
[x] Introduce a settings file #191
[x] Define a PDF selection process #192

Addressed in #164, #191, #192


Remove bundled copy of os_volume module

The relevant PR is included in Ansible 2.3

This effectively means that our OS roles would be 2.3+ though, correct?

I think this is the only one. It should continue to work with Ansible 2.1/2.2 since the new parameter is optional: https://github.com/manics/ansible-role-openstack-volume-storage/blob/2b7f724ced202a0c9263f4cd0a493a99b021eb68/tasks/main.yml#L10

So release as 1.1.0 and if someone on ansible 2.2 + volume copy complains we say, "bump to ansible 2.3"?

Sounds fine to me

:+1:


Add Chennai website as a submodule

PyLadies Pull Request
Please document the following. We will aim to be as timely as possible in processing your pull request, however as this is a volunteer staffed project anticipate at least a week for pull requests to start to be reviewed.
Does this PyLadies previously exist in the main PyLadies repo?

[ ] Yes
[x] No

If you marked yes, have you deleted it from the the main PyLadies repo?

[ ] Yes, and here is the pull request: [Insert pull request url here]
[x] No

Is this pull requesting adding a PyLadies chapter website?

[x] Yes
[ ] No

If you marked yes, is this chapter registered in the PyLadies Chapter Directory?

[x] Yes
[ ] No

If you marked no, please register your chapter using the following form here. The form can only be accessed by being logged into your official PyLadies email account. Were you able to complete the registration?

[ ] Yes
[ ] No, I could not because [add response below]:

Is this pull request updating a PyLadies website?

[ ] Yes
[x] No

Pull Request Checklist

[x] Fill out all sections above

/cc @pyladies/tech-and-infra-admins

/cc @pyladies/chennai

We're so close! @niharikakrishnan can you rebase for us following the directions here:

We're so close! @niharikakrishnan can you rebase for us following the directions here:

Done @lorenanicole !! :)

@lorenanicole Please let me know if I need to make any changes!

Is there anything left to do to close this?


Trouble viewing Logs

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp log download
Errors:
HTTPSConnectionPool(host='dungeonmaster.scm.pgprod.p.azurewebsites.net', port=443): Max retries exceeded with url: /dump (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))
Traceback (most recent call last):
site-packages/urllib3/contrib/pyopenssl.py, ln 485, in wrap_socket
    cnx.do_handshake()
python3.8/site-packages/OpenSSL/SSL.py, ln 1934, in do_handshake
    self._raise_ssl_error(self._ssl, result)
...
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='dungeonmaster.scm.pgprod.p.azurewebsites.net', port=443): Max retries exceeded with url: /dump (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp log download --log-file {} --name {} --resource-group {} --subscription {}

Expected Behavior
Environment Summary
macOS-10.16-x86_64-i386-64bit
Python 3.8.1

azure-cli 2.2.0

Additional Context

@rkentmc Apologies for delay in getting back, thanks for reporting. If you update to the latest CLI version (with az upgrade), do you still get the error?


Broken examples

Hi I tried to check examples at https://pixijs.io/examples/#/demos-advanced/star-warp.js but there are some errors, see screen

Dev is currently broken. We are on it. Duplicate of https://github.com/pixijs/examples/issues/66
Please use a release, for example:
https://pixijs.io/examples/?v=v5.2.4#/demos-advanced/star-warp.js

Oh, thanks!


[API] AutoRange type

This pull-request is linked to:

engine: For docker collector patch, contains more information about why and how
cli: For the docker-compose.yml parsing and $ docker container stats format

This PR contains the necessary change to the api to enable autorange functionality.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:vdaviot/swarmkit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Is modin worth it

https://github.com/modin-project/modin
They claim a lot, let's see what we get with the actual data.
I feel like the only thing which really makes the difference (100x times) is numpy and CPython. That's covered in fastai ML 2018, perhaps in fastai Computational Algebra too.

I tried it a kaggle kernel, and it just didn't work.


ros2_controllers: 2.13.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros2_controllers to 2.13.0-1:

upstream repository: https://github.com/ros-controls/ros2_controllers.git
release repository: https://github.com/ros2-gbp/ros2_controllers-release.git
distro file: humble/distribution.yaml
bloom version: 0.10.7
previous version for package: 2.12.0-1

diff_drive_controller

No changes

effort_controllers

No changes

force_torque_sensor_broadcaster

No changes

forward_command_controller

No changes

gripper_controllers

No changes

imu_sensor_broadcaster
* Fix undeclared and wrong parameters in controllers. (#438 <https://github.com/ros-controls/ros2_controllers/issues/438>)
  * Add missing parameter declaration in the joint state broadcaster.
  * Fix unsensible test in IMU Sensor Broadcaster.
* Contributors: Denis Štogl

joint_state_broadcaster
* Generate parameters for Joint State Broadcaster (#401 <https://github.com/ros-controls/ros2_controllers/issues/401>)
* Fix undeclared and wrong parameters in controllers. (#438 <https://github.com/ros-controls/ros2_controllers/issues/438>)
  * Add missing parameter declaration in the joint state broadcaster.
  * Fix unsensible test in IMU Sensor Broadcaster.
* [JointStateBroadcaster] Reset internal variables to avoid duplication of joints (#431 <https://github.com/ros-controls/ros2_controllers/issues/431>)
* Contributors: Denis Štogl, Gilmar Correia, Tyler Weaver, Bence Magyar

joint_trajectory_controller
* Generate Parameter Library for Joint Trajectory Controller (#384 <https://github.com/ros-controls/ros2_controllers/issues/384>)
* Fix rates in JTC userdoc.rst (#433 <https://github.com/ros-controls/ros2_controllers/issues/433>)
* Fix for high CPU usage by JTC in gzserver (#428 <https://github.com/ros-controls/ros2_controllers/issues/428>)
  * Change type cast wall timer period from second to nanoseconds.
  create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage.
  * Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer.
  node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request.  The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution.  Althougth the previous timer does nothing but still get fired.
* Contributors: Arshad Mehmood, Borong Yuan, Tyler Weaver, Andy Zelenak, Bence Magyar, Denis Štogl

position_controllers

No changes

ros2_controllers

No changes

ros2_controllers_test_nodes
* Enable definition of all fields in JointTrajectory message when using test node. (#389 <https://github.com/ros-controls/ros2_controllers/issues/389>)
* Contributors: Denis Štogl

rqt_joint_trajectory_controller

No changes

tricycle_controller

No changes

velocity_controllers

No changes

I will revert this to try to fix errors in the ur packages. You can see here for more information: https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/issues/522#issuecomment-1288081581

When is the new sync? I'll have a new release ready with the issue fixed


Argument error in Tzdata.ReleaseReader

Hey @lau, was updating Timex's tzdata dependency to 0.5.1 and hit the following error when calling Tzdata.canonical_zone_list:
Erlang/OTP 18 [erts-7.0.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Interactive Elixir (1.0.5) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> Tzdata.canonical_zone_list
** (ArgumentError) argument error
    (stdlib) :ets.lookup(:tzdata_current_release, :release_version)
    (tzdata) lib/tzdata/release_reader.ex:41: Tzdata.ReleaseReader.current_release_from_table/0
    (tzdata) lib/tzdata/release_reader.ex:13: Tzdata.ReleaseReader.simple_lookup/1
    (tzdata) lib/tzdata/release_reader.ex:5: Tzdata.ReleaseReader.zone_list/0
iex(1)>

Hi @bitwalker Did you put :tzdata in the applications list?

Ah I still had it just in :included_applications. Sorry about that!

No worries. Also keep in mind that users of Timex will have to have their app start Tzdata if it is ~> 0.5.1. For instance
by adding :tzdata to the applications: list in their mix.exs file. This is not required for ~> 0.1.7, but it won't hurt to add it.
That's why I added this to the Calendar readme. Maybe you want to add that (or something similar) too:
--
Also add tzdata to the list of applications in the mix.exs file:
  def application do
    [applications: [:logger, :tzdata]]
  end

Thanks @lau. I made the same mistake too.

Hey,
I'm getting the same error when trying to use Tzdata 0.5.12 (e.g. Tzdata.canonical_zone_list) in a module attribute. It is present in the applications list. Taken from the getting started guide:

Any functions may be called when defining a module attribute.

Any idea what the issue might be?

Hi @thisismydesign
Please update to the newest version of Tzdata (currently 0.5.16).
Which version of Elixir are you using? Tzdata needs to be started somehow. In certain versions of Elixir Tzdata (or a library using it, such as Calendar), needs to be in the applications list.

@lau thanks for the quick reply!
I'm using Tzdata  natively and it's already in the applications list.
Elixir version:
Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.4.5

My usage is like this:
defmodule Module do
  @timezones Tzdata.canonical_zone_list

I am also getting the same, with a different call.
I have this piece of code:
    case Timex.Timezone.get(data) do
      {:error, _} = error ->
        error

      data ->
        {:ok, data}
    end

to put timezones that are saved in the database into a struct.
Well when running a migration that gets some data through an Ecto Query I get this error:
** (ArgumentError) argument error
    (stdlib) :ets.lookup(:tzdata_current_release, :release_version)
    lib/tzdata/release_reader.ex:47: Tzdata.ReleaseReader.current_release_from_table/0
    lib/tzdata/release_reader.ex:14: Tzdata.ReleaseReader.simple_lookup/1
    lib/tzdata/release_reader.ex:7: Tzdata.ReleaseReader.zone_and_link_list/0
    lib/tzdata.ex:40: Tzdata.zone_exists?/1
    lib/timezone/timezone.ex:152: Timex.Timezone.name_of/1
    lib/timezone/timezone.ex:180: Timex.Timezone.get/2
    lib/common/ecto/timezone.ex:27: Common.Ecto.Timezone.load/1
    (ecto) lib/ecto/type.ex:661: Ecto.Type.process_loaders/3
    (ecto) lib/ecto/schema.ex:1490: Ecto.Schema.load!/5
    (ecto) lib/ecto/schema.ex:1442: Ecto.Schema.safe_load_zip/4
    (ecto) lib/ecto/schema.ex:1443: Ecto.Schema.safe_load_zip/4
    (ecto) lib/ecto/schema.ex:1430: Ecto.Schema.__safe_load__/6
    (ecto) lib/ecto/repo/queryable.ex:282: Ecto.Repo.Queryable.process_source/6
    (ecto) lib/ecto/repo/queryable.ex:170: Ecto.Repo.Queryable.preprocess/5
    (postgrex) lib/postgrex/query.ex:77: DBConnection.Query.Postgrex.Query.decode_map/3
    (postgrex) lib/postgrex/query.ex:64: DBConnection.Query.Postgrex.Query.decode/3
    (db_connection) lib/db_connection.ex:1019: DBConnection.decode/6
    (ecto) lib/ecto/adapters/postgres/connection.ex:73: Ecto.Adapters.Postgres.Connection.prepare_execute/5
    (ecto) lib/ecto/adapters/sql.ex:256: Ecto.Adapters.SQL.sql_call/6

Which has that code in the stack trace and doing some Inspects can verify that that's indeed the call that triggers the error, although doing:
iex(1)> Timex.Timezone.get("America/Los_Angeles")
#<TimezoneInfo(America/Los_Angeles - PDT (-07:00:00))>

What's interesting is that if I run the same code iex -S mix works.

You need to execute Application.ensure_all_started(:timex) in your migrations, the problem is that the :tzdata application is not running, and so that ETS table is missing. This doesn't happen when you run iex -S mix because Mix is starting :tzdata

Makes sense @bitwalker, thanks!


Changed access modifiers in Employee on private, and created properti…

…es in Employee

Btw, who are you?

Ah sorry, my name is Ondřej Šanko (st43344).


Add missing instance options environment variables

Related spec: https://github.com/meilisearch/specifications/pull/190
There are some missing environment variables in the instance options, and it would be really helpful if you could add them 🙏
I'm thinking of the one corresponding to the following CLI options:

--import-dump -> MEILI_IMPORT_DUMP
--ignore-missing-dump -> MEILI_IGNORE_MISSING_DUMP
--ignore-dump-if-db-exists -> MEILI_IGNORE_DUMP_IF_DB_EXISTS
--import-snapshot -> MEILI_IMPORT_SNAPSHOT
--ignore-missing-snapshot -> MEILI_IGNORE_MISSING_SNAPSHOT
--ignore-snapshot-if-db-exists -> MEILI_IGNORE_SNAPSHOT_IF_DB_EXISTS

Edit from @curquiza
TODO

[X] Apply changes in PR
[X] Update the specification -> https://github.com/meilisearch/specifications/pull/190

Contributing
All the environment variables need to be added in a single PR. Once activated, they should involve the exact same behavior as the corresponding flag.
Example: MEILI_IMPORT_DUMP is the env variable corresponding to the --import-dump flag already present in Meilisearch.
Priority: if the env variable and the corresponding flag are set, the priority is for the flag.
Feel free to ask any question to implement this issue, the core team is available to guide you through this contribution, even if it's your first one.
We recommend referring to the CONTRIBUTING.md guidelines, especially if it's your first contribution to this repository.
Thanks in advance for your involvement ❤

is this for v0.29? @gmourier @curquiza

Nope, we don't add new features to v0.29.0, it's for v0.30.0 or later. I put it for v0.30.0 for the moment, it's fast to implement if I'm correct, should be ok for v0.30.0

Pinging @meilisearch/docs-team

The spec has been updated and has been added to the issue description
https://github.com/meilisearch/specifications/pull/190