Using a "relation" widget as "field" inside of a "list" widget causes problems.

Describe the bug
When using a relation widget inside of a list widget as a single field it causes problems. You can type one character but you can't delete it or find any related items. It also doesn't look right:
To Reproduce
Inside of one of the collections in your config.yml
This works:
      - label: 'Tags'
        name: 'tags'
        widget: 'list'
        field:
          - label: 'Tag'
            widget: 'string'

This causes the problem:
      - label: 'Activities'
        name: 'activities'
        widget: 'list'
        field:
          - label: 'Activity'
            name: 'activity'
            widget: 'relation'
            collection: 'activity'
            displayFields:
              - "slug"
              - "title"
            searchFields:
              - "slug"
              - "title"
            valueField: 'slug'

Expected behavior
Using a list of relation items should work.
Screenshots

The debugger shows this:

Sorry about not having symbols inside of the cms code  (I couldn't figure out how to merge the module-resolver babel plugin to allow me to use the sources directly)
Applicable Versions:

Netlify CMS version: 1.9.3 (I have not re-tried the mono repo)
Git provider: github
OS: Mac OS
Browser version Chrome 68.0.3440.106 (Official Build) (64-bit)

Node.JS version: 9.11.1

CMS configuration

# auto - insert backend config
# <BACKEND_CONFIG>

media_folder: assets/images
public_folder: /static/images
publish_mode: editorial_workflow

collections:
  - name: "page"
    label: "Pages"
    folder: "content/pages"
    create: true
    format: yaml-frontmatter
    extension: md
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - {label: "Title", name: "title", widget: "string", required: false}
      - {label: "Slug", name: "slug", widget: "string", required: true}
      - {label: "Content", name: "body", widget: "markdown"}
      - {label: "Tags", name: "tags", widget: "list", required: false}

  - name: "category"
    label: "Categories"
    folder: "content/categories"
    create: true
    format: yaml-frontmatter
    extension: md
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - {label: "ID", name: "id", widget: "string", required: true}
      - {label: "Title", name: "title", widget: "string", required: true}
      - {label: "Tags", name: "tags", widget: "list", required: false}

  - name: "activity"
    label: "Activities"
    folder: "content/activities"
    create: true
    format: yaml-frontmatter
    extension: md
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - {label: "Title", name: "title", widget: "string", required: false}
      - {label: "Slug", name: "slug", widget: "string", required: true}
      - {label: "Category", name: "category", widget: "relation", collection: 'category', searchFields: ["id", "title"], displayFields: ["id", "title"], valueField: "id"}
      - {label: "Content", name: "body", widget: "markdown"}
      - {label: "Tags", name: "tags", widget: "list", required: false}

  - name: "unit"
    label: "Unit"
    folder: "content/units"
    create: true
    format: yaml-frontmatter
    extension: md
    delete: false
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - {label: "ID", name: "id", widget: "string", required: false}
      - {label: "Code Number", name: "code", widget: "string"}
      - {label: "Active (display and Stripe)", name: "active", widget: "boolean", default: true}
      - {label: "Title (display and Stripe)", name: "title", widget: "string", required: false}
      - {label: "Publish Date", name: "date", widget: "datetime"}
      - {label: "Tags", name: "tags", widget: "list", required: false}
      - {label: 'Price (for display)', name: 'price', widget: "text"}
      - {label: 'Amount (for Stripe in cents)', name: 'amount', widget: "number", valueType: "int", min: 0}
      - {label: 'Currency (for Stripe)', name: 'currency', default: 'USD', widget: 'text'}
      - label: "Interval"
        name: "interval"
        widget: 'select'
        options:
          - label: Day
            value: day
          - label: Week
            value: week
          - label: Month
            value: month
          - label: Year
            value: year
      - {label: 'Interval Count', name: 'interval_count', widget: "number", valueType: "int", min: 0}
      - {label: 'Auto Cancel (during purchase)', name: 'autoCancel', widget: "boolean", default: true}
      - {label: 'Order', name: 'order', widget: "number"}
      - {label: 'Only Offer', name: 'offer', widget: "boolean", required: false, default: false}
      - label: 'Tags'
        name: 'tags'
        widget: 'list'
        field:
          - label: 'Tag'
            widget: 'string'
      - label: "Randomize Activites"
        name: 'randomActivities'
        widget: 'boolean'
        default: true
        required: false
      - label: 'Activities'
        name: 'activities'
        widget: 'list'
        field:
          - label: 'Activity'
            name: 'activity'
            widget: 'relation'
            collection: 'activity'
            displayFields:
              - "slug"
              - "title"
            searchFields:
              - "slug"
              - "title"
            valueField: 'slug'
      - {label: 'Subscriptions', name: 'subscriptions', widget: "list", field: {label: 'Subscription', widget: 'string'}}
      - {label: 'Survey', name: 'survey', widget: 'relation', collection: 'activity', displayFields: ['slug', 'title'], searchFields: ['slug', 'title'], valueField: 'slug'}
      - {label: "Slug", name: "slug", widget: "string", required: true}

Additional context
Sorry that I am stuck on the non-mono-repo version since I have not figured out how to do a live patch of that version.

That bug was likely fixed in #1395, released in 2.0.10.
What problems are you having using the mono-repo version?

Confirmed fixed in 2.0.10.

Awesome, thank you. I will try to merge 2.0.10 into my code. @tech4him1 The monorepo is preventing me from installing npm patches inside of netlify deploy from a git repo. I need to investigate patching the whole mono repo and creating an npm org and installing the modules from a scoped repo.


Update BOM

R: @lostluck

cc: @bvolpato since he's been in this area recently dealing with version conflicts.

Run Java_IOs_Direct PreCommit

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sdks:java:io:debezium:expansion-service:analyzeClassesDependencies'.
> Failed to load cache entry 42b153a82b08aeb70ec268acf6feba34 for task ':sdks:java:io:debezium:expansion-service:analyzeClassesDependencies': Could not load from local cache: Timeout waiting to lock Build cache (/home/jenkins/.gradle/caches/build-cache-1). It is currently in use by another Gradle instance.
  Owner PID: 1831864
  Our PID: 1831552
  Owner Operation:
  Our operation:
  Lock file: /home/jenkins/.gradle/caches/build-cache-1/build-cache-1.lock

Seems like a flake.

Run Java PreCommit

The precommit failure seems unrelated.
[org.apache.beam.runners.spark.translation.streaming.ResumeFromCheckpointStreamingTest.testWithResume](https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/28009/testReport/junit/org.apache.beam.runners.spark.translation.streaming/ResumeFromCheckpointStreamingTest/testWithResume/)

Run Java PreCommit


Backend features needed

Todo

[ ] Order backend

Any other backend stuff we need?
@federico101 @Cpaul777

looks like thats the only one thats left


Update Storage and EventHub SDK t1 to t2

Update Storage and EventHub SDK t1 to t2

Update files:

./livemaps-api/APIFunctions/AtlasUnits.cs
./livemaps-api/APIFunctions/Config.cs
./livemaps-api/APIFunctions/DeviceState.cs
./livemaps-api/APIFunctions/PostState.cs
./livemaps-api/APIFunctions/RoomData.cs
./livemaps-api/APIFunctions/RoomStateSim.cs
./livemaps-api/APIFunctions/SideBar.cs
./livemaps-api/APIFunctions/SiteMap.cs
./livemaps-api/APIFunctions/Warnings.cs
./livemaps-api/ServiceFunctions/FeatureStatePublisher.cs
./livemaps-api/Services/BlobDataService.cs
./livemaps-api/Services/SiteMapBuilder.cs
./livemaps-api/livemaps.api.csproj

@jongio,@annatisch,@scottaddie,@AlexGhiondea,@lilyjma,@ramya-rao-a,@kyle-patterson,@tg-msft,@alzimmermsft for notification.

@jsquire Can you please review this?

@tg-msft I have updated by your comments.

@jsquire I had updated according to your comments, please review.

I would like to close this PR for now as we'll want to work on a new sample in the future that integrates with all of the strengths of the new libs.


[CI] Set Node version to LTS for docker builds

Signed-off-by: suod-NithishKarthik<EMAIL_ADDRESS>Description
This PR fixes sets the node version for docker build to LTS(Node 16), because it causes issues with UI build (ref)
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #4551 (4d28385) into master (8f5bcda) will decrease coverage by 7.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4551      +/-   ##
==========================================
- Coverage   33.16%   25.99%   -7.18%
==========================================
  Files          60       60
  Lines        5044     5044
==========================================
- Hits         1673     1311     -362
- Misses       2935     3409     +474
+ Partials      436      324     -112

Flag
Coverage Δ

gointegrationtests
?

unittests
25.99% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
1.11% <0.00%> (-58.52%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-47.50%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-47.44%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-34.74%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.86% <0.00%> (-27.59%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.29% <0.00%> (-20.88%)
:arrow_down:

Continue to review full report at Codecov.

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

@Revolyssup will you have a quick look here - https://github.com/meshery/meshery/runs/4083090843?check_suite_focus=true#step:6:2364?


Cannot run build on iOS device – TypeError: null is not an object

Hi,
glad to see progress on the library, the Android version is working like a charm.
Unfortunately we've run to an issue running our application using this library on iOS, we're getting the following error when building an running the app on iOS 13.3:

Our Podfile is configured with the line "require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'" and "use_native_modules!".
Have you encountered the same error anywhere on development, or have you gotten the BTEvents working also with iOS on React Native version >= 0.60?
Thank you for the great library!

Hey thanks.  Yes, the BluetoothClassicExample works perfectly (with my environment) on IOS.  The application is setup with the most up to date version of MacOSX, XCode and React Native 0.61.3 (I believe).
The most common issue with IOS is that the MFi protocols are missing in the PLIST file.  Without these, the module will build, but the IOS module will not actually start (the RNBluetoothClassic INIT method will fail).  I could probably clean it up a little to display some better messages, but MFi protocols are required for External Accessory, so they should be the first thing to check.
Let me know if you have issues with the BluetoothClassicExample as I always ensure it's working with my companies scanner before publishing.

https://github.com/kenjdavidson/react-native-bluetooth-classic/tree/master/BluetoothClassicExample#ios-mfi-protocols

Thanks for the quick reply!
We actually got it working now, we had forgotten to add the empty swift file in Xcode. After adding the swift file, the bridging headers were automatically created by Xcode. We also cleaned our node_modules and installed all dependencies and pods again, after which the build started working.

Awesome man. Ill have to create a Lil faq of these things at some point.  Thanks for the update/resolution.


Thift THRIFT-4350 - Upgrade netcore project to netstandard 2.0 & 1.6 + new csproj format

This PR doesn't modify the existing code hence no new tests. I simply upgraded the projects from the obsolete xproj to csproj format and added support for both netstandard 1.6 and 2.0; project now needs dotnet sdk 2.0 to build. I also build a sample at net core sample that I modified from the csharp tutorial.

Closing this in favor of jeking3 pr


Pods of Kube system are stuck in containercreating and prompt no such host

Environmental Info:
K3s Version:
k3s version v1.21.4+k3s1 (3e250fdb)
go version go1.16.6
Node(s) CPU architecture, OS, and Version:
Linux localhost 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
Cluster Configuration:
1 servers 1 agents
Describe the bug:

After executing the get.k3s.io installation script, all pods under Kube system are stuck in the containercreating state. View the status of pods through describe and see the following information：
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "rancher/pause:3.1": failed to pull image "rancher/pause:3.1": failed to pull and unpack image "docker.io/rancher/pause:3.1": failed to resolve reference "docker.io/rancher/pause:3.1": failed to do request: Head "https://registry-1.docker.io/v2/rancher/pause/manifests/3.1": dial tcp: lookup registry-1.docker.io: no such host
I tried to check whether the registry-1.docker.io domain name can be accessed through curl and found no problem

I tried to add the --resolv conf = /etc/resolv conf option, but the problem was not solved.

I tried to bind the registry-1.docker.io domain name through the /etc/host file. After restarting the k3s service, I checked the description of pods. I did not continue to prompt that the registry-1.docker.io domain name could not be resolved, but reported that other domain names could not be resolved

Steps To Reproduce:
After executing the following script:
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig ~/.kube/config --write-kubeconfig-mode 644 --resolv-conf /etc/resolv.conf" sh -
Additional context / logs:
 Warning  FailedCreatePodSandBox  15h (x414 over 17h)   kubelet  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "rancher/pause:3.1": failed to pull image "rancher/pause:3.1": failed to pull and unpack image "docker.io/rancher/pause:3.1": failed to resolve reference "docker.io/rancher/pause:3.1": failed to do request: Head "https://registry-1.docker.io/v2/rancher/pause/manifests/3.1": dial tcp: lookup registry-1.docker.io: no such host   Warning  FailedCreatePodSandBox  4m2s (x161 over 39m)  kubelet  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "rancher/pause:3.1": failed to pull image "rancher/pause:3.1": failed to pull and unpack image "docker.io/rancher/pause:3.1": failed to resolve reference "docker.io/rancher/pause:3.1": failed to do request: Head "https://registry-1.docker.io/v2/rancher/pause/manifests/3.1": dial tcp: lookup registry-1.docker.io: no such host

Can you share more information about your environment? Do you have a private DNS server, firewall, or proxy in your environment that is blocking your access when attempting to reach registry-1.docker.io? I've seen cases where the DNS server can't be reached and you get timeout errors, but something in your environment is claiming that registry-1.docker.io does not exist.

Can you share more information about your environment? Do you have a private DNS server, firewall, or proxy in your environment that is blocking your access when attempting to reach registry-1.docker.io? I've seen cases where the DNS server can't be reached and you get timeout errors, but something in your environment is claiming that registry-1.docker.io does not exist.

My environment is vagrant + VirtualBox. The virtual machine operating system is Debian 10. The VirtualBox is configured with
--natdnsproxy1 option as on
--natdnshostresolver1 option as on
Vagrant version:2.2.18
Virtualbox version:6.1.26 r145957
Debian version:Linux version 5.10.0-8-amd64<EMAIL_ADDRESS>(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110
My VirtualBox environment is configured with two virtual network cards, one is NAT and the other is host only. The virtual network card of NAT is used as the gateway in the virtual machine, while the network card of host only cannot be used as the gateway to request to the public network

There is no problem running docker + docker compose in my environment. I also try to set k3s to use docker, but Debian 11 does not support docker of version 19.03. So I can only use container as the runtime. I try to modify the /etc/ranger/k3s/registers.yaml file and replace the domain name of registry-1.docker.io with docker.mirrors.ustc.edu.cn. After restarting the k3s service, check the description of pods and prompt
dial TCP: lookup docker.mirrors.ustc.edu.cn: no such host.
However, if I request the domain name of docker.mirrors.ustc.edu.cn through curl, there is no problem

The problem was solved when I turned off both options of the virtual box
--natdnsproxy1
--natdnshostresolver1

No more no such host errors have occurred

However, in some scenarios where vagrant is used, the -- natdnsproxy1 and -- natdnshostresolver1 options need to be set to on to solve the problem of DNS parsing exceptions in some scenarios
https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working


License?

Hi Samuel,
What is the license for this code? Is it CC0?
May you add a LICENSE file to clarify this?
Thanks!

People keep complaining about CC0, so I'm not sure if I'm going with that. Either way, you can safely assume it's something permissive.

There's a license now: CC0.


Display provisioned IOPs for GP3 volumes

Summary
See https://github.com/rancher/dashboard/pull/6243, GP3 should show the Provisioned IOPs field.
###Screencapture
From AWS console create volume UI:

@catherineluse Sorry I missed this in the last PR. Hopefully the logic I added is correct - I don't have an environment set up to test this.

LGTM
I tested this PR locally and confirmed that when GP3 is selected as the StorageClass, the Provisioned IOPS input is displayed:

Filling out that field also updated the StorageClass YAML in the proper format:


fix(dbm-services): dbha do ssh detect should with timeout

关联研发信息
dev_branch: fix/dbha-ssh-timeout/#8254
target_branch: v1.5.0


FAQ on GDPR-compliant log processing

I see it's already been merged, but I am not a huge fan, since "GDPR compliance" is not the only thing we are going for here. I see what we're doing here, but this answer ignores e.g. support/on-prem and thus "do whatever you want" scenarios.

I see it's already been merged, but I am not a huge fan, since "GDPR compliance" is not the only thing we are going for here. I see what we're doing here, but this answer ignores e.g. support/on-prem and thus "do whatever you want" scenarios.

Could you suggest how to incorporate "do whatever you want" scenarios?


Add run constraint to avoid co-installation with unaffected pyarrow versions

The pyarrow-hotfix situation bemuses me. Wow, untrusted data might lead to an exploit, news at 11. The way this was deployed across pyarrow and pandas is quite unusual as well - using a third-party package to retroactively shout warnings at users to install a random package (complete with the option to disable it again in code...).
And now that the hotfix package is out there, it will just hang around indefinitely (e.g. it's used in a bunch of recipes in conda-forge already). I consider this an embarrassment from the POV of packaging (rather than, say, backporting the fix to supported versions), and we should not let it persist indefinitely.
As such, we should just disable installation of pyarrow-hotfix wherever pyarrow >=13 is present. In a few months, pyarrow 13 will be the oldest supported version in conda-forge, then we can archive this feedstock. From the POV of the resolver, it'll probably be easier to attach this to pyarrow itself, because otherwise the presence of pyarrow-hotfix would just force the selections old builds, rather than conflict obviously.
Xref https://github.com/conda-forge/arrow-cpp-feedstock/pull/1237
CC @conda-forge/arrow-cpp
PS. The sheer amount of busywork caused by one essentially frivolous CVE is just mindboggling to me.

Can you please tone down the rhetoric and focus on the concrete proposal here? I understand you disagree with us PyArrow maintainers on the severity and the appropriate handling of this security issue (we already had a couple of colourful private exchanges about it), but hammering on this in such terms is not exactly kind, friendly and welcoming.
Thanks in advance.

Focusing on the concrete proposal:

we should just disable installation of pyarrow-hotfix wherever pyarrow >=13 is present

I am not familiar enough with the details and nuances of conda (how a run-constraint will impact solving of environment and potentially create conflicts), but my first worry is that this might just make things more complex instead of being helpful.
The pyarrow-hotfix package being installed in your environment does not do any harm. Yes, if you have a more recent pyarrow, it's completely unneccessary, but it still doesn't do anything wrong except of being installed.
If adding a constraint might trigger the solver to pick an older version of pyarrow to satisfy the constraint if you already have the hotfix package installed (or are installing another package that depends on it), that might actually be annoying or make things worse (but again, I don't know if that's how it will work).

And now that the hotfix package is out there, it will just hang around indefinitely (e.g. it's used in a bunch of recipes in conda-forge already).

That doesn't need to be the case. All the cases that are listed by that search have a minimum version of pyarrow set. For example, dask has pyarrow >=7.0. Once this is bumped to pyarrow >= 13.0 (in a year and a half, or so), the pyarrow-hotfix dependency can be removed.
Of course, that requires someone to remember this and actually do it, and I know that doesn't happen by itself. But so it certainly doesn't need to be kept indefinitely (and e.g. we could open an issue in those feedstocks to track this as a reminder, and I would also be happy to do that).

Of course, that requires someone to remember this and actually do it, and I know that doesn't happen by itself. But so it certainly doesn't need to be kept indefinitely (and e.g. we could open an issue in those feedstocks to track this as a reminder, and I would also be happy to do that).

Thanks for the offer. Though the longer this percolates in requirement files (both pip & conda), the harder it will be to eventually remove it.

Once this is bumped to pyarrow >= 13.0 (in a year and a half, or so), the pyarrow-hotfix dependency can be removed.

It's possible that this is the least painful transition, all things considered. Conda-forge will arrive at >=13.0 after arrow 16 already (we support the last 4 major versions).

Before discussing creative solutions to the problem, it would be good to understand what the problem actually is.
The issue description talks about an "embarrassment", which is not really descriptive or insightful.
The pyarrow-hotfix package is a pure Python package with virtually zero dependencies (except for Python and PyArrow). It has a tiny footprint and does not have any impact unless explicitly imported from Python.

but hammering on this in such terms is not exactly kind, friendly and welcoming.

I think there is a substantial part of my OP that wrongly got "received" by the arrow team personally, where that part was actually aimed at the (to me) obnoxious culture imposed by CVE scanners setting people's hair on fire across the ecosystem, especially if it's for things that can only really be addressed by users (like not loading untrusted data/binaries).
I did a bad job at communicating this distinction though, and I apologise for any offence caused. I've also been in situations where people are screaming to get a CVE resolved, no matter how pointless, so I know that dealing with this can be stressful.
The small part of the context setting that is critical of the handling of the situation by the arrow has already been discussed at length (I do believe things could have been handled better in various ways), but that's in the past and I'm happy to leave it there.

The issue description talks about an "embarrassment", which is not really descriptive or insightful.

I've modified the OP to replace that word. The underlying point is that a "hotfix" should be something fast and temporary ("hot"), and the continued presence of *-hotfix packages creates the impression that we don't know what we're doing.

It has a tiny footprint and does not have any impact unless explicitly imported from Python.

At issue is the social impact (hard to quantify, obviously), rather than a technical one. That and the fact that it grows rather than shrinks the enormous pile of technical debt we have scattered through conda-forge.


cv2.resize provide different results in x86 and aarch64

Expected behaviour

x86_result = cv2.resize(same_image_numpy, (600,600), interpolation=3)  # running on x86 platform ubuntu server
aarch64_result = cv2.resize(same_image_numpy, (600,600), interpolation=3)  # running on jetson nano
(x86_result == aarch64_result ).all()
True

Actual behaviour

x86_result = cv2.resize(same_image_numpy, (600,600), interpolation=3)  # running on x86 platform ubuntu server
aarch64_result = cv2.resize(same_image_numpy, (600,600), interpolation=3)  # running on jetson nano
(x86_result == aarch64_result ).all()
False

Steps to reproduce
pip install  opencv_python-<IP_ADDRESS>-cp36-cp36m-manylinux2014_x86_64.whl  # on x86 ubuntu18.04 server
pip install  opencv_python-<IP_ADDRESS>-cp36-cp36m-manylinux2014_aarch64.whl # on aarch64 ubuntu18.04 jetson nano
call cv2.resize

operating system

x86-server:~$  lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.5 LTS
Release:        18.04
Codename:       bionic
x86-server:~$ uname -r
4.15.0-144-generic
nano:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.5 LTS
Release:        18.04
Codename:       bionic
nano:~$ uname -r
4.9.201-tegra
ubuntu18.04

architecture (e.g. x86)
opencv-python version

interpolation=3
3

Avoid using of magic numbers. Use cv.INTER_AREA instead.
Only _EXACT (bitexact) modes provide the same result on different platforms.


PlayBack Sensor

HI, I'm using an Amazon Firestik configured with homebridge-adb and I appreciated the PlayBack sensor. But I've noticed an issue.
The sensor is working fine if you play a movie (it become active) and if you pause (it become inactive).
But if you are playing a movie and you decide to stop it pressing the button Back (instead of home) the Sensor remain active and the firestick do not respond anymore: if you tray to turn it of from homebridge you receive an error:
[Homebridge UI] [HapClient] [<IP_ADDRESS>:41283 (0F:27:15:6A:E0:B2)] Failed to set value for FireStick B436.
Again: all is working fine if you use the Home button on the firestick remote control. If you press "back" on the remote control the sensor remain active and the forested doesn't work anymore
Thanks

Thank you for the bugs report, will fix this soon.

Could you provide more information: like what apps causing it if it's only in one app? what other output before the output you mention before? It seems like I can't recreate your error right now.

I notice it using Amazon Prime on the FireStick. It happens:

If I press back button while playing to come back to home instead of pressing pause+home or just home
If I turn off the firestik via remote control without pausing the movie or coming back to home. In this case the accessory Firestick become grey (turned off) while the sensor remain active

I didn't test other app for the moment

The latest update might solve this problem, please try it and let me know the result.

Yes the problem is solved with Amazon Prime
With the app Disney+ the sensor never became active

Yes the problem is solved with Amazon Prime
With the app Disney+ the sensor never became active

OK, it seems that your Disney+ might output different messages then mine.  Do you mind to run this command in your computer when you're playing video in Disney+ app?
adb -s your-device-ip shell "dumpsys media_session | grep state=PlaybackState"
Send the output here, so I can examine the output.

here it is:
state=PlaybackState {state=2, position=0, buffered position=0, speed=0.0, updated=347585832, actions=38, custom actions=[], active item id=-1, error=null}
state=PlaybackState {state=3, position=25966, buffered position=83082, speed=1.0, updated=409092734, actions=2360175, custom actions=[], active item id=1, error=null}
state=PlaybackState {state=3, position=25966, buffered position=83082, speed=1.0, updated=409092734, actions=2360175, custom actions=[], active item id=1, error=null}
state=PlaybackState {state=2, position=0, buffered position=0, speed=0.0, updated=347585832, actions=38, custom actions=[], active item id=-1, error=null}

I was looking to understand if the problem was related to Disney+ only and I payed video on youtube app. when I did that the sensor turned on correctly. Then I pause the video and the sensor remains on, I came back home and the sensor remains on.
MEDIA SESSION SERVICE (dumpsys media_session)
3 sessions listeners.
3 Sessions:
Vizzini_2.0.10900.0:MediaButtonController com.amazon.vizzini/Vizzini_2.0.10900.0:MediaButtonController
ownerPid=31828, ownerUid=32092, userId=0
package=com.amazon.vizzini
launchIntent=null
mediaButtonReceiver=null
active=true
flags=2
rating type=0
controllers: 0
state=null
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=0, description=null
queueTitle=null, size=0
starboard_media com.amazon.firetv.youtube/starboard_media
ownerPid=5185, ownerUid=10025, userId=0
package=com.amazon.firetv.youtube
launchIntent=null
mediaButtonReceiver=null
active=false
flags=2
rating type=0
controllers: 0
state=PlaybackState {state=3, position=0, buffered position=0, speed=0.0, updated=410850228, actions=4, custom actions=[], active item id=-1, error=null}
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=4, description=null, null, null
queueTitle=null, size=0
PrimeVideo-MediaSession com.amazon.avod/PrimeVideo-MediaSession
ownerPid=5633, ownerUid=32047, userId=0
package=com.amazon.avod
launchIntent=null
mediaButtonReceiver=PendingIntent{1f490cd4: PendingIntentRecord{28785b0e com.amazon.avod broadcastIntent}}
active=false
flags=2
rating type=0
controllers: 2
state=PlaybackState {state=2, position=15712, buffered position=0, speed=0.0, updated=410700034, actions=173350, custom actions=[], active item id=-1, error=null}
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=12, description=Episodio 8, null, null
queueTitle=null, size=0
Global priority session is null
Sessions Stack - have 3 sessions:
Vizzini_2.0.10900.0:MediaButtonController com.amazon.vizzini/Vizzini_2.0.10900.0:MediaButtonController
ownerPid=31828, ownerUid=32092, userId=0
package=com.amazon.vizzini
launchIntent=null
mediaButtonReceiver=null
active=true
flags=2
rating type=0
controllers: 0
state=null
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=0, description=null
queueTitle=null, size=0
PrimeVideo-MediaSession com.amazon.avod/PrimeVideo-MediaSession
ownerPid=5633, ownerUid=32047, userId=0
package=com.amazon.avod
launchIntent=null
mediaButtonReceiver=PendingIntent{1f490cd4: PendingIntentRecord{28785b0e com.amazon.avod broadcastIntent}}
active=false
flags=2
rating type=0
controllers: 2
state=PlaybackState {state=2, position=15712, buffered position=0, speed=0.0, updated=410700034, actions=173350, custom actions=[], active item id=-1, error=null}
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=12, description=Episodio 8, null, null
queueTitle=null, size=0
starboard_media com.amazon.firetv.youtube/starboard_media
ownerPid=5185, ownerUid=10025, userId=0
package=com.amazon.firetv.youtube
launchIntent=null
mediaButtonReceiver=null
active=false
flags=2
rating type=0
controllers: 0
state=PlaybackState {state=3, position=0, buffered position=0, speed=0.0, updated=410850228, actions=4, custom actions=[], active item id=-1, error=null}
audioAttrs=AudioAttributes: usage=1 content=0 flags=0x0 tags=
volumeType=1, controlType=2, max=0, current=0
metadata:size=4, description=null, null, null
queueTitle=null, size=0
User Records:
Record for user 0
MediaButtonReceiver:PendingIntent{1f490cd4: PendingIntentRecord{28785b0e com.amazon.avod broadcastIntent}}
3 Sessions:
com.amazon.vizzini/Vizzini_2.0.10900.0:MediaButtonController
com.amazon.firetv.youtube/starboard_media
com.amazon.avod/PrimeVideo-MediaSession

Android ADB document said that the fist state=PlaybackState should indicate playback status. We're looking for first state=PlaybackState with state=3 as a sign of media is playing.
Your dumpsys media_session  output with the first result of state=PlaybackState is state=3  meaning current media is playing.
While, your  dumpsys media_session | grep ...  output with the first result of state=PlaybackState is state=2 meaning current media is pausing.
If this is the same output, then we found the culprit that cause wrong reading by the plugins. The plugins use the output from  dumpsys media_session | grep ... because it's shorter, so the plugins doesn't have to download large data.

Hi Dwaan, with the last update 1.4.3 the sensor doesn’t work anymore nor with Prime nor with Disney +. Installing back the 1.4.2 Prime start to work again

I'm using a new ADB command to detect playback, it's work properly for app like Disney+ or Cartoon Network that  didn't report their status to dumpsys media_session, at least in some of device that I test.
What I use right now is a command like this dumpsys audio | grep 'player piid' | tail -10, it report any audio playback. But maybe different devices output differently. if you can share your output for that command with those two apps, I'll be gladly to examine that.

can you please give me the exact command ?

pi@homebridge:/var/lib/homebridge $ adb shell "dumpsys audio"
Audio Focus stack entries (last is top of stack):
source:android.os.BinderProxy@e67d9b8 -- pack: com.amazon.avod -- client: com.amazon.media.AmazonAudioManager@314ebd8dcom.amazon.avod.playbackclient.feature.audiofocus.AudioFocusManager$GlobalAudioFocusChangeListener@2455db42 -- gain: GAIN -- flags:  -- loss: none -- uid: 32047 -- attr: AudioAttributes: usage=1 content=2 flags=0x0 tags=
Notify on duck: true
Remote Control stack entries (last is top of stack):
Remote Control Client stack entries (last is top of stack):
Current remote control generation ID = 0
Remote Volume State:
has remote: false
is remote active: false
rccId: -1
volume handling: PLAYBACK_VOLUME_VARIABLE(1)
volume: 15
volume steps: 15
Remote Control Display list entries:
Stream volumes (device: index)

STREAM_VOICE_CALL:
Mute count: 0
Max: 5
Current: 2000 (usb_accessory): 5, 1000 (digital_dock): 5, 800 (analog_dock): 5, 400 (hdmi): 5, 40000000 (default): 5, 40 (bt_sco_carkit): 5, 80 (bt_a2dp): 5, 100 (bt_a2dp_hp): 5, 200 (bt_a2dp_spk): 5, 2000000 (proxy): 5, 400000 (speaker_safe): 5, 8000 (remote_submix): 5, 4000 (usb_device): 5, 1 (earpiece): 5, 10000 (telephony_tx): 5, 2 (speaker): 5, 20000 (line): 5, 4 (headset): 5, 40000 (hmdi_arc): 5, 80000 (spdif): 5, 8 (headphone): 5, 10 (bt_sco): 5, 100000 (fm_transmitter): 5, 20 (bt_sco_hs): 5, 200000 (aux_line): 5

STREAM_SYSTEM:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7

STREAM_RING:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7

STREAM_MUSIC:
Mute count: 0
Max: 15
Current: 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 400 (hdmi): 15, 800 (analog_dock): 15, 1000 (digital_dock): 15, 2000 (usb_accessory): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 8 (headphone): 15, 80000 (spdif): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15

STREAM_ALARM:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7

STREAM_NOTIFICATION:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7

STREAM_BLUETOOTH_SCO:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15

STREAM_SYSTEM_ENFORCED:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7

STREAM_DTMF:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15

STREAM_TTS:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15

mute affected streams = 0x2e

Ringer mode:

mode (internal) = NORMAL
mode (external) = NORMAL
ringer mode affected streams = 0x80
ringer mode muted streams = 0x0
delegate = ZenModeHelper

Audio routes:
mMainType=0x8
mBluetoothName=Device NOT Connected
Other state:
mVolumeController=VolumeController(android.os.BinderProxy@153463d0,mVisible=false)
mSafeMediaVolumeState=SAFE_MEDIA_VOLUME_ACTIVE
mSafeMediaVolumeIndex=100
mPendingVolumeCommand=null
mMusicActiveMs=0
mMcc=0
mHasVibrator=false
Audio policies:

Hi.
Can you run this instead adb shell "dumpsys audio | grep 'player piid' | tail -10"
the log seem truncated.

pi@homebridge:/var/lib/homebridge $ adb shell "dumpsys audio | grep 'player piid' | tail -10"
/system/bin/sh: tail: not found

pi@homebridge:/var/lib/homebridge $ adb shell "dumpsys audio | grep 'player piid'"
pi@homebridge:/var/lib/homebridge $

pi@homebridge:/var/lib/homebridge $ adb shell "dumpsys audio"
Audio Focus stack entries (last is top of stack):
source:android.os.BinderProxy@e67d9b8 -- pack: com.amazon.avod -- client: com.amazon.media.AmazonAudioManager@314ebd8dcom.amazon.avod.playbackclient.feature.audiofocus.AudioFocusManager$GlobalAudioFocusChangeListener@2455db42 -- gain: GAIN -- flags: -- loss: none -- uid: 32047 -- attr: AudioAttributes: usage=1 content=2 flags=0x0 tags=
Notify on duck: true
Remote Control stack entries (last is top of stack):
Remote Control Client stack entries (last is top of stack):
Current remote control generation ID = 0
Remote Volume State:
has remote: false
is remote active: false
rccId: -1
volume handling: PLAYBACK_VOLUME_VARIABLE(1)
volume: 15
volume steps: 15
Remote Control Display list entries:
Stream volumes (device: index)
STREAM_VOICE_CALL:
Mute count: 0
Max: 5
Current: 2000 (usb_accessory): 5, 1000 (digital_dock): 5, 800 (analog_dock): 5, 400 (hdmi): 5, 40000000 (default): 5, 40 (bt_sco_carkit): 5, 80 (bt_a2dp): 5, 100 (bt_a2dp_hp): 5, 200 (bt_a2dp_spk): 5, 2000000 (proxy): 5, 400000 (speaker_safe): 5, 8000 (remote_submix): 5, 4000 (usb_device): 5, 1 (earpiece): 5, 10000 (telephony_tx): 5, 2 (speaker): 5, 20000 (line): 5, 4 (headset): 5, 40000 (hmdi_arc): 5, 80000 (spdif): 5, 8 (headphone): 5, 10 (bt_sco): 5, 100000 (fm_transmitter): 5, 20 (bt_sco_hs): 5, 200000 (aux_line): 5
STREAM_SYSTEM:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7
STREAM_RING:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7
STREAM_MUSIC:
Mute count: 0
Max: 15
Current: 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 400 (hdmi): 15, 800 (analog_dock): 15, 1000 (digital_dock): 15, 2000 (usb_accessory): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 8 (headphone): 15, 80000 (spdif): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15
STREAM_ALARM:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7
STREAM_NOTIFICATION:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7
STREAM_BLUETOOTH_SCO:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15
STREAM_SYSTEM_ENFORCED:
Mute count: 0
Max: 7
Current: 2000 (usb_accessory): 7, 1000 (digital_dock): 7, 800 (analog_dock): 7, 400 (hdmi): 7, 40000000 (default): 7, 40 (bt_sco_carkit): 7, 80 (bt_a2dp): 7, 100 (bt_a2dp_hp): 7, 200 (bt_a2dp_spk): 7, 2000000 (proxy): 7, 400000 (speaker_safe): 7, 8000 (remote_submix): 7, 4000 (usb_device): 7, 1 (earpiece): 7, 10000 (telephony_tx): 7, 2 (speaker): 7, 20000 (line): 7, 4 (headset): 7, 40000 (hmdi_arc): 7, 80000 (spdif): 7, 8 (headphone): 7, 10 (bt_sco): 7, 100000 (fm_transmitter): 7, 20 (bt_sco_hs): 7, 200000 (aux_line): 7
STREAM_DTMF:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15
STREAM_TTS:
Mute count: 0
Max: 15
Current: 2000 (usb_accessory): 15, 1000 (digital_dock): 15, 800 (analog_dock): 15, 400 (hdmi): 15, 40000000 (default): 15, 40 (bt_sco_carkit): 15, 80 (bt_a2dp): 15, 100 (bt_a2dp_hp): 15, 200 (bt_a2dp_spk): 15, 2000000 (proxy): 15, 400000 (speaker_safe): 15, 8000 (remote_submix): 15, 4000 (usb_device): 15, 1 (earpiece): 15, 10000 (telephony_tx): 15, 2 (speaker): 15, 20000 (line): 15, 4 (headset): 15, 40000 (hmdi_arc): 15, 80000 (spdif): 15, 8 (headphone): 15, 10 (bt_sco): 15, 100000 (fm_transmitter): 15, 20 (bt_sco_hs): 15, 200000 (aux_line): 15
mute affected streams = 0x2e
Ringer mode:
mode (internal) = NORMAL
mode (external) = NORMAL
ringer mode affected streams = 0x80
ringer mode muted streams = 0x0
delegate = ZenModeHelper
Audio routes:
mMainType=0x8
mBluetoothName=Device NOT Connected
Other state:
mVolumeController=VolumeController(android.os.BinderProxy@153463d0,mVisible=false)
mSafeMediaVolumeState=SAFE_MEDIA_VOLUME_ACTIVE
mSafeMediaVolumeIndex=100
mPendingVolumeCommand=null
mMusicActiveMs=0
mMcc=0
mHasVibrator=false
Audio policies:
pi@homebridge:/var/lib/homebridge $

Ah. Thank you.  Will update the plugins soon.

Hi
Just update to version 1.4.4 --> playback sensor does not work: it never become active

I tried to uninstall and reinstall, to move to a child bridge and come back, to remove the accessory and the sensor from Home, to change their name... nothing seems to work: the sensor never turn on with any application.
Strange thing is that seems that also the previous 1.4.2 version has stop to work: with this version also the the sensor doesn't turn on...
do you need any specific log ?
Thanks

Yes, thank you. I need to formulated how to properly submit log message so everyone can help with this. Because so far, in my experience there is no exact way to detect playback status, some device output different log format.

ok, just tell me the command you want I launch to obtain the log you need.
Do you think is possible to use different way/commands to detect the playback status depending on the "category" selected in the config.json ?

Merge into issue #46


fill ref operator

Implements a fill operator that sets the values in an output buffer to a given value
Will be used when parsing ONNX ConstantOfShape
Can also be used when a buffer needs to be filled with a value that is determined at runtime

There's a problem with checking if the default_value is a scalar. Scalar in MIGX is if all the strides = 0. I think this ONNX op rather wants there to be only one element. Hitting into a problem with how ConstantOfShape is parsed.


Add modules.md

After some more consideration while designing the interface, I think this description is slightly outdated and I need another way to explain the structure. Let me revisit this issue soon.


Added the possibility to add Future events

In this pull request I've:

Added a Future Events section
Added Combine 2023 event as a Future Event
Changed the Readme to explain the Future Events user_groups

Thanks @Fontanapink - this looks great. Just a quick question... if we use https://co.mbine.org/author/combine-2023/ as a URL to start promoting and linking to the meeting, will it be possible to automatically redirect that page to https://co.mbine.org/events/ once it becomes the current event? Just wondering as currently the page https://co.mbine.org/author/harmony-2023/ is very different to https://co.mbine.org/events/

No, it will not. That is a VERY good point. Let me look into this.


Can't compile the TS

The instructions say npm build: i think they mean npm run build
Then:
sierra:matrix-fb-chat matthew$ npm run build

><EMAIL_ADDRESS>build /Users/matthew/workspace/matrix-fb-chat
> tsc

src/facebook.ts(27,33): error TS2339: Property 'includes' does not exist on type 'string[]'.
src/facebook.ts(29,27): error TS2339: Property 'includes' does not exist on type 'any[]'.
src/matrix-fbook.ts(32,20): error TS2339: Property 'includes' does not exist on type 'any[]'.
src/matrix.ts(42,21): error TS2339: Property 'includes' does not exist on type 'string[]'.

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.4.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `tsc`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the matrix-fb-chat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs matrix-fb-chat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls matrix-fb-chat
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/matthew/workspace/matrix-fb-chat/npm-debug.log

Do I need a newer tsc?

Ah...it used to be contains() didn't it. I think I might have jumped the gun with includes which is fairly modern. I'll see what I can do to make both v6.4 and v6.9 (mine) happy.

f300cc446ae0f375c37a110a077d86f3c32d3993 updates the type definition file to something actually recent in the hopes it will include the right stuff.

Same for me, although my package.json includes "@types/node": "^6.0.52".

#2 will fix the issues above.


Week 0 Review Ticket

Individual Deployed Github Pages

[ ] GitHub page for Test Prep study, requiring 5.1, 5.2 notes and actions( See "GitHub pages actions" at the bottom of each TPT page

[ ] GitHub page that documents Data Structures project, using code snippets for key learnings, and links to  GitHub for code and Replit for runtime

[ ] GitHub page that documents intended Create Task project for College Board, snippets, and links to Runtime

Score: 2.9/3

Menu works on replit
Ship animation does not work >> -0.1 points
-create task, test prep, and tech talk documented on github pages


Add ability to provide additional folders in the stylesPath for SASS compilation

We use the bourbon SASS library in our application (which is installed via Bower). However, there isn't a means by which we can add additional folders to the stylesPath on https://github.com/glimmerjs/glimmer-application-pipeline/blob/master/src/broccoli/glimmer-app.ts#L331 without extending the GlimmerApp class. It would be nice to be able to pass in an array of additional style paths (so that we can add bourbon scss assets from its bower_components folder) that could be concat'ed to the stylesPath.

We are in the process of updating the  build a pipeline to call hooks much more similar to a standard ember apps pipeline.  This would allow ember-cli-sass to continue to function without needing to modify the build pipeline manually.


WinUI incremental building not working causing a disastrous full build experience

There are a couple of unfortunate things I have noticed over the past weeks and months working on WinUI when it comes to the incremental build process of WinUI.

While incremental builds work when on the same local branch, unfortunately, as soon as I switch branches and build the project again, Visual Studio is always doing a full build of the project. In fact, further builds will also always be full builds until I do a clean. Only then will incremental builds work again. What that means for my current workflow? Switch a branch -> do a clean -> enjoy a full build to get incremental building working again,

As soon as I modify an .idl file (like NavigationView.idl) and start a build process, VS always does a full build instead of an incremental build.

WinUI Full build experience is disastrous
Why are full builds a problem here? First, full builds take up to 10 minutes on my Core i7-8750H maxing out my CPU during most of the time. Secondly, and most importantly, the VS build process consistently runs out of memory at some point during the build process. I am particularly dreading the moment the compiler reaches the following files during the build process:
ScrollInputHelper.cpp
ScrollPresenter.properties.cpp
ScrollControllerInteractionRequestedEventArgs.cpp
ScrollControllerScrollByRequestedEventArgs.cpp
ScrollControllerScrollFromRequestedEventArgs.cpp
ScrollControllerScrollToRequestedEventArgs.cpp
ScrollPresenter.cpp

When the VS compiler reaches these files, the RAM consumed by it jumps significantly, so much that VS often runs out of memory here and outright cancels the build task. This happens with me making sure that VS has at least 8 GB if not 9 GB of RAM available before starting a build process. And to be clear, these are not the only files in the build process causing the out of memory issue but that issue does occur more often than not at this stage in the build process.
I think I don't have to tell you that this experience is really frustrating. Especially as VS was already building for a few minutes here until it runs out of memory. In other words: I just completely wasted my time.
Case in point, yesterday, two simple commits took 45 minutes of my time because I just couldn't get VS to finish building the project here (so I could quickly verify their correctness in the MUXControlsTestApp). This is unacceptable and absolutely detrimental to get anything done in WinUI.
While the root cause of the build failure always seems to be VS running out of memory, the reported error messages vary a bit. Here are the three different types of errors I have seen (writing them out of my memory here so those will lack details):

PCH - The compiler ran out of heap space
System.OutOfMemoryException - VS just cancels the task build (that's the one I often see occuring around the Scroll*.cpp files above)
Internal C++ compiler error - Please contact the VS team (seems to happen rather rarely)

Nearly 50% of my full builds end in such failures and when such a failure happens, all bets are off. VS needs to be restarted, and I even had to restart Windows (!) at one point. More time being wasted here getting nothing done...
Note that the specific System.OutOfMemoryException error I mentioned above only started occuring since a few days ago. I am not aware of any VS or Windows update I did over the past week which could have contributed to that. I use VS and Windows in the following versions:

Windows 10 19041
Visual Studio 16.6.2

How to improve the WinUI build story
So, ideally, these issues could be solved and the WinUI development experience significantly improved by achieving the following:

Switching (local) branches won't require a full build of the project. Instead, incremental building will keep working.
Modifying IDL files also won't cause a full build of the project and use incremental building instead.

When incremental building works, building WinUI does not take away the fun of working on it. When it doesn't - especially in common cases like the ones mentioned above - the WinUI development experience is disastrous and takes away all the fun.
I'm not sure if this is something the WinUI team can fix or if we need some VS folks to help out here. If it's the latter, I'd hope that the WinUI team can put some emphasis on these issues internally at MS so that the WinUI build process in VS can be improved in a timely manner. I'm hardly one to press for immediate action on this repo but I have to say these past days have just been incredibly frustrating.

@llongley FYI

and @kmahone FYI

With 16GB of RAM and 8 GB of free HDD space I wasn't able to build. Ram was used up and then the disk space. How do you guys manage this internally? Is this going to get a lot worse with WinUI 3.0?

I agree that having long build times is quite painful for dev loop. @chingucoding and others helped build the inner loop solution which can be used to filter what exactly builds which should drastically reduce build time if you are working on a single feature. More info [here](https://microsoft.visualstudio.com/OS/_workitems/edit/24872104
https://microsoft.visualstudio.com/OS/_workitems/edit/26540032
). You can essentially build a much smaller subset and associated tests and let the lab do the full build and test run.

This issue is one that made me drop trying to make a new control for WinUI, because 8GB of RAM and Ryzen 5 2500U in a 2-in-1 with a puny cooling solution just isn't enough for it.

This is definitely a significant barrier to contributions. This and being written in the strangest mix of C++/IDL/Generated Code I've seen in a long time -- I miss 'pure' architectures and C#.
That said, we really should add minimum and recommended system requirements to the documentation somewhere, I'm still not sure what Microsoft is using internally to make building more reasonable but they must be some pretty powerful systems.
Long-term, a lot of optimizations and changes are needed to improve the build experience across the board.

Regarding the out of memory issues, it might be related to the number of cores on your machine and the multi proc builds.

I have been using the MUXControlsInnerLoop solution consistently in the last 1-2 weeks and that definitely delievers a singificant build improvement. In fact, the past weeks I only once had to deal with VS breaking down during a build due to no more memory available using the inner loop. And I did quite a few builds during that time period. No more breakdown every second full build!
@ranjeshj That said, I noticed that apparantly API tests are not available in the inner loop solution:

Assuming you see that as well on your machine, is this something which could be improved? For now, the missing API tests require me to load the full MUXControls project and start a full build - at which point the API tests can be run again.
There also seem to be some issues with the interaction tests in the InnerLoop solution. For example, while I can start interaction tests, the NunberBox interaction tests constantly fail to find the test numberbox instance and thus the tests fail with a NullReference exception. Is that something you are seeing too and if so, could this be improved as well?

@Felix-Dev can you see if it works for you in the debug-test configuration instead of debug ? I think debug-test ensures that the test app packages are built to enable running tests.

@ranjeshj Nice! That solves the missing API tests:

While the specific NumberBox interaction tests still fail to find the NumberBox instance I have tested other interaction tests just now, like NavView interaction tests, and they work fine. Perhaps I made a recent change to the NumberBox test page which I do not recall right now which is causing the NumberBox issues.


Configure custom HTTP headers

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Desired functionality.
I would like to be able to configure webpack server HTTP headers through the angular cli.  I am interested in configuring security headers so that I can determine their effects on my project.
Mention any other details that might be useful.
It looks like this could be done very similarly to how the proxy config is passed through to the WebpackDevServer config options.  A separate config file could be used or maybe a combined configuration file could be used to hold both proxy and headers settings.
There is an existing request for adding proxy headers (https://github.com/angular/angular-cli/issues/5968) but this request is just for headers in general.
I am interested in contributing this enhancement.  Implementation feedback is welcomed.

This level of configuration is beyond the scope of ng serve. An alternative is to use ng build --watch and serve the contents of dist with a custom server that implements all the setting you need.


CSI-sanity check - should fail when the node does not exist

Fix error code when node does not exist.
    Expected
        <codes.Code>: 13
    to equal
        <codes.Code>: 5

https://github.com/longhorn/longhorn/issues/2076
https://github.com/longhorn/longhorn/issues/2270

ip-172-30-0-21:/home/ec2-user/csi-test/cmd/csi-sanity # ./csi-sanity -csi.endpoint /var/lib/kubelet/obsoleted-longhorn-plugins/driver.longhorn.io/csi.sock -ginkgo.skip="should create volume from an existing source snapshot|should return appropriate values|should succeed when creating snapshot with maximum-length name|should succeed when requesting to create a snapshot with already existing name and same source volume ID|should fail when requesting to create a snapshot with already existing name and different source volume ID"

Ran 42 of 77 Specs in 144.196 seconds
SUCCESS! -- 42 Passed | 0 Failed | 1 Pending | 34 Skipped


pkg: types: Add new field type

The Interface structure needs a new field 'type' so that we can
properly determine the type of interface being described.
This will be helpful for network hotplug, as it will be used to
create the appropriate connection between the VM and the interface.
Fixes #401
Signed-off-by: Sebastien Boeuf<EMAIL_ADDRESS>

Depends on #400

Travis seems to have exploded in flames on this change...?

Related: #400.

@jodh-intel @amshinde @devimc @grahamwhaley @caoruidong  This PR is ready now that #400 has been merged.

/test

lgtm

lgtm

@sboeuf I'm a bit concerned about the new field. It adds an extra field to the grpc message that is not going to be used between runtime and agent. The agent does not care about what type of link is added to the VM. All it sees is a new network device. If the runtime API needs the new linktype field, it should do so by defining a new type in the runtime repo based on agent/pkg/types.Interface (e.g., via embedded types) instead of appending to types.Interface directly.
/cc @gnawux @WeiZhang555 @egernst

@bergwolf yes I see your point. I could define a new packagegithub.com/kata-containers/runtime/pkg/types/types.go. Both kata-netmon, kata-runtime and virtcontainers would rely on this package that would create a new structure Interface:
import "github.com/kata-containers/agent/pkg/types"

type Interface struct {
        types.Interface
        LinkType string
}

Or is it better to define it as github.com/kata-containers/runtime/virtcontainers/pkg/types/types.go ?

@bergwolf problem with embedded struct that I forgot, is that every time a structure Interface is defined like this:
	iface := types.Interface{
		Device:      linkAttrs.Name,
		Name:        linkAttrs.Name,
		IPAddresses: ipAddrs,
		Mtu:         uint64(linkAttrs.MTU),
		HwAddr:      linkAttrs.HardwareAddr.String(),
	}

go build will fail because it won't recognize the field from the structure...
This will imply a lot of changes for such a small thing.

@sboeuf yeah, anonymous fields cannot be used directly in struct literals. You have to create explicit embedded struct:
        iface := types.Interface{
                grpctypes.Interface{
                        Device:      linkAttrs.Name,
                        Name:        linkAttrs.Name,
                        IPAddresses: ipAddrs,
                        Mtu:         uint64(linkAttrs.MTU),
                        HwAddr:      linkAttrs.HardwareAddr.String(),
                },
                "macvtap",
        }

But they can be accessed directly through iface.Device etc.
Are there many places to change? I grepped a bit and only found convertInterface() that needs to be changed (except for *_test.go though and virtcontainers/network.go:generateInterfacesAndRoutes is between runtime and agent).
[macbeth@runtime]$git grep types.Interface\{|grep -v \}
netmon/netmon.go:       iface := types.Interface{
netmon/netmon_test.go:  expected := types.Interface{
netmon/netmon_test.go:  iface := types.Interface{
netmon/netmon_test.go:  expected := types.Interface{
virtcontainers/api_test.go:     inf := &types.Interface{
virtcontainers/network.go:              ifc := types.Interface{
virtcontainers/network_test.go: expectedInterfaces := []*types.Interface{

Another option is to make grpc types internal and define virtcontainers' own types and have a converter to translate them. @WeiZhang555 also suggested it last time we had such a conversation (https://github.com/kata-containers/runtime/issues/758#issuecomment-422707263).

@bergwolf the more I think about it, the more I dislike the fact that we use types from the agent as generic ones. The ideal solution would be to define the exact same types from runtime/virtcontainers/pkg/types to be reused by kata-runtime, kata-netmon, and virtcontainers. The types from the agent does not need to be modified or translated, but it should be only imported from kata_agent.go, as this is the Kata agent implementation. And later we could imagine having the agent relying on virtcontainers types.
But clearly, the way it is designed right now does not seem right. virtcontainers being the core of the Kata API, it should define the generic types everybody might need. On the other hand, the agent is specific to the kata_agent.go implementation, and should not be the reference for generic structures.

@sboeuf Yes, I agree. We have two requirements here:

The kata runtime APIs are between kata-runtime/kata-netmon/kata-shim-v2 and virtcontainers. And virtcontainers being the core of the API, should be the one defining types used by every one.
The agent APIs are between virtcontainers and kata-agent. And kata-agent should be the one defining the types.

So it comes back to @WeiZhang555's initial suggestion, we define two types packages one in runtime/virtcontainers/pkg/types and another in kata-agent/pkg/types.

The types from the agent does not need to be modified or translated, but it should be only imported from kata_agent.go, as this is the Kata agent implementation.

The types from agent are used in kata-agent APIs. So runtime still need some kind of translation if it wants to talk to the agent. OTOH, runtime/virtcontainers/pkg/types does not need to import agent/pkg/types so that other components (kata-runtime/kata-netmon/kata-shimv2 etc) doesn't need to be aware of the agent types.

@bergwolf

The types from agent are used in kata-agent APIs. So runtime still need some kind of translation if it wants to talk to the agent. OTOH, runtime/virtcontainers/pkg/types does not need to import agent/pkg/types so that other components (kata-runtime/kata-netmon/kata-shimv2 etc) doesn't need to be aware of the agent types.

Oh yes of course we'll need a tiny translation function in the kata_agent.go to be able to translate virtcontainers types (Interface, Route, IPAddress) into agent types.
I thought we were talking about a translation at the structure level that would run outside of run-time.
Anyway, I'm glad we agree on this one, I'll take care of it!

Once https://github.com/kata-containers/runtime/pull/867 gets merged, let's revert this PR!

@sboeuf Yes, I agree. We have two requirements here:

The kata runtime APIs are between kata-runtime/kata-netmon/kata-shim-v2 and virtcontainers. And virtcontainers being the core of the API, should be the one defining types used by every one.
The agent APIs are between virtcontainers and kata-agent. And kata-agent should be the one defining the types.

Yes, I agree with @bergwolf , we have to do our best to keep agent protocol unchanged, because one tiny change can also bring big damage!
Some duplicate codes with a translation layer is necessary, agent protocol stability is worth some duplicated code and extra effort.


Can't connect to LDAP server - Using SSL

Laravel Version: 6
Adldap2-Laravel Version: 6
PHP Version: 7.3

I keep getting error message when trying to connect with SSL. I works perfectly fine without, but when I try to attach my Cert and connect, I just get "Can't contact LDAP server in C:\laragon\www\webmaster\vendor\adldap2\adldap2\src\Auth\Guard.php:107"
ldap.php
'connections' => [

    'default' => [

        'auto_connect' => true,

        'connection' => Adldap\Connections\Ldap::class,

        'schema' => Adlap\Schemas\ActiveDirectory::class,

        'settings' => [
            'hosts' => explode(' ', env('LDAP_HOST')),
            'port' => env('LDAP_PORT', 389),
            'base_dn' => env('LDAP_BASE_DN'),
            'username' => env('LDAP_USERNAME'),
            'password' => env('LDAP_PASSWORD'),
            'use_ssl' => true,
            'use_tls' => false,
            'account_suffix' =><EMAIL_ADDRESS>
            'custom_options' => [
                LDAP_OPT_X_TLS_CACERTFILE => "c:/Users/jba/certs/ca.cert"
            ]
        ],
    ],
],

Hi @ZuggieTM,
You must use port 636 to connect to your LDAP server via SSL.
Also, to my knowledge, SSL LDAP connections do not require a client certificate. Only TLS connections do (hence LDAP_OPT_X_TLS_CACERTFILE)

It is using 636. setting 'use_ssl' sets it to 636 and doesn't look at 'port' => env('LDAP_PORT', 389)
[2020-02-24 14:06:35] local.WARNING: LDAP (ldaps://domain.local:636) - Connection: default - Operation: Failed - Username: user - Reason: Can't contact LDAP server

You're right - though unfortunately there isn't any assistance I can give you if your web server is reporting that it can't contact your LDAP server over SSL. You will need to login to your AD server and ensure it's configured and accessible.
If you're using Windows 10 Pro, you can enable ADSI edit and attempt connecting over SSL to ensure it is working properly.

LDAP is running on windows 2012 server and I'm connecting from my local machine running windows 10.
I tried using ldp.exe to test the connection and it seems to work just fine as long as the certificate from my ldap server is installed. As soon as i remove it from "Trusted" in my windows 10 certificates, it stops working. This is Why I'm trying to send the certificate from ADLDAP2 on my laravel application.
If this is not doable, would you know if I can disable the cert requirement on the ldap server?

In ldp.exe are you specifying port 636? Just ticking the boxes to make sure I'm on the same page as you.

Port is set to 636 and SSL is ticked.

ld = ldap_sslinit("domain.local", 636, 1);
Error 0 = ldap_set_option(hLdap, LDAP_OPT_PROTOCOL_VERSION, 3);
Error 81 = ldap_connect(hLdap, NULL);
Server error:
Error <0x51>: Fail to connect to domain.local.

Hmm okay let's try this. Create the following file on your computer:
C:\OpenLDAP\sysconf\ldap.conf

Edit it, and paste in:
TLS_REQCERT never

Then, restart your local web server and try connecting again in your Laravel application. Let me know how it goes!

Dude! I love you man! You seriously saved me from getting a ton of gray hair (more than I already have). It works!
I have no idea what that tiny files does, but it works!
Thank you so much! I need something to celebrate with now!

Haha I'm glad you're up and running! ❤  Thanks so much for your kind words!
 Only TLS connections do (hence LDAP_OPT_X_TLS_CACERTFILE)

By default, PHP will look at this location for an ldap.conf file. This file configures LDAP TLS / SSL connectivity. In the file you can specify a certificate file path so you're sure you're connected securely.
In regards to your second question - I've written about this on the new LdapRecord library:
https://ldaprecord.com/docs/configuration/#ssl-amp-tls

The ldap.conf file is located in the following default locations:
Windows: C:\OpenLDAP\sysconf\ldap.conf (The directories will not exist, create them and add the file)
Linux: /etc/ldap/ldap.conf

However, using TLS_REQCERT never can be a bit of a security risk as it will ignore invalid certificates.
It's recommended to copy your domain CA cert to:
Windows: C:\OpenLDAP\sysconf
Linux: /etc/ssl/certs
Then, reference it in your ldap.conf with the full file path using (replace my-custom-path with the location of the file):

TLS_CACERT my-custom-path/ca.pem
TLS_REQCERT hard

I'll close this for now but if you encounter any further issues feel free to create an issue and I'd be glad to help you out further. :smile:


A new error when fitting automl with X_val and y_val specified: 'TypeError: transform() takes 2 positional arguments but 3 were given'

Hi FLAML team:
After upgrading the FLAML to the latest version, there is an error when I ran automl.fit() with X_val and y_val specified. Using your notebook on automl as an example:
from flaml.data import load_openml_dataset
X_train, X_test, y_train, y_test = load_openml_dataset(dataset_id=1169, data_dir='./')
from flaml import AutoML
automl = AutoML()
settings = {
"time_budget": 240,  # total running time in seconds
"metric": 'accuracy',  # can be: 'r2', 'rmse', 'mae', 'mse', 'accuracy', 'roc_auc', 'roc_auc_ovr',
# 'roc_auc_ovo', 'log_loss', 'mape', 'f1', 'ap', 'ndcg', 'micro_f1', 'macro_f1'
"task": 'classification',  # task type
"log_file_name": 'airlines_experiment.log',  # flaml log file
"seed": 7654321,    # random seed
}

automl.fit(X_train=X_train, y_train=y_train, X_val=X_test, y_val=y_test,**settings)
TypeError: transform() takes 2 positional arguments but 3 were given

Request if you could look into it.
Thank you!

@flippercy Could you show me the trace of error? Thanks.

Here you go.

TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_4757/550052602.py in
----> 1 automl.fit(X_train=X_train, y_train=y_train, X_val=X_test, y_val=y_test, **settings)
~/.local/lib/python3.7/site-packages/flaml/automl.py in fit(self, X_train, y_train, dataframe, label, metric, task, n_jobs, log_file_name, estimator_list, time_budget, max_iter, sample, ensemble, eval_method, log_type, model_history, split_ratio, n_splits, log_training_metric, mem_thres, pred_time_limit, train_time_limit, X_val, y_val, sample_weight_val, groups_val, groups, verbose, retrain_full, split_type, learner_selector, hpo_method, starting_points, seed, n_concurrent_trials, keep_search_state, early_stop, append_log, auto_augment, min_sample_size, use_ray, **fit_kwargs)
1468
1469         self._validate_data(
-> 1470             X_train, y_train, dataframe, label, X_val, y_val, groups_val, groups
1471         )
1472         self._search_states = {}  # key: estimator name; value: SearchState
~/.local/lib/python3.7/site-packages/flaml/automl.py in _validate_data(self, X_train_all, y_train_all, dataframe, label, X_val, y_val, groups_val, groups)
589             if self._label_transformer:
590                 self._state.y_val = self._label_transformer.transform(
--> 591                     y_val, self._state.task
592                 )
593             else:
TypeError: transform() takes 2 positional arguments but 3 were given

Thanks. This problem has been fixed by #274
You can either wait for the release of v0.7.1 or clone the latest version and do "pip install -e".

Update: v0.7.1 is released.


Create a cache for files

Library path don't change too much. It's possible to create a cache of the processed items to it, to do not be necessary to process the items every time we open the Delphi Ide.

maybe cache based on file hash? if file hash not changed reparsed is not required

yes, this is the idea.

done


Plain Object and IObject are not compatible anymore?

I didn't use the latest version of Closure Compiler for some time but I've upgraded to the latest version a I'm surprised by these warnings in my projects:
/** @type {!IObject<string,string>} */
var a = {};

/** @type {!IObject<string,string>} */
var b = {
	'foo' : 'bar'
};

test.js:2: WARNING - initializing variable
found   : {}
required: IObject<string,string>
var a = {};
        ^^

test.js:5: WARNING - initializing variable
found   : {foo: string}
required: IObject<string,string>
var b = {
        ^

0 error(s), 2 warning(s), 100.0% typed

But if I force the type, warnings disapear.
/** @type {!IObject<string,string>} */
var a = /** @type {!IObject<string,string>} */ ({});

/** @type {!IObject<string,string>} */
var b = /** @type {!IObject<string,string>} */ ({
	'foo' : 'bar'
});

0 error(s), 0 warning(s), 100.0% typed

Command line params:
	--compilation_level ADVANCED \
	--language_in ECMASCRIPT6_STRICT \
	--language_out ECMASCRIPT5_STRICT \
	--new_type_inf \
	--source_map_format V3 \
	--summary_detail_level 3 \
	--use_types_for_optimization \
	--warning_level VERBOSE

I've found the commit after which warnings appeared: cb0069aac5e743a9d450dd2c0de411c5055043b8
Why can't be NTI used anymore?

I've just updated our wiki page for NTI with an explanation for why it is gone.
https://github.com/google/closure-compiler/wiki/[OBSOLETE]-Using-NTI-(new-type-inference)

@brad4d Thank you for that! What about this issue? Will it be fixed?

This was implemented incorrectly in NTI.   IObject is used to declare the "computed property operator".  It can't be inferred.   "Object<string,string>" is what you want here.


How to fix  " is not a valid value for "ACCEPT_EULA"?

I executed below.
docker-compose -f docker-compose.yml -f components/openvino/docker-compose.openvino.yml build --build-arg http_proxy=http://(server):(port) --build-arg https_proxy=(server):(port)
The error is below.
Processing triggers for man-db (2.7.5-1) ...
" is not a valid value for "ACCEPT_EULA"
/tmp/components/openvino/l_openvino_toolkit_p_2019.1.144/silent.cfg has errors
Service 'cvat' failed to build: The command '/bin/sh -c if [ "$OPENVINO_TOOLKIT" = "yes" ]; then         /tmp/components/openvino/install.sh;     fi' returned a non-zero code: 2
I decompressed the l_openvino_toolkit_p_2019.1.144.org.tgz file using the winzip, edited the silent.cfg file to change the value of ACCEPT_EULA from decline to accept and recompressed them. But another error happened.
How to fix it?

@otsukaoly
Hi, I suppose you use windows. If it is true, than there is a related issue #534:
git checkout develop
git pull origin develop
git rm --cached -r .
git reset --hard
# Now you can build container

I will close the issue. If you will have any problems with the solution, you can reopen it.

Thanks a lot!
Now I can see the "Model Manager" button.

I have a simple question.
I clicked Model Manager button.
But I cannot see any model in the Uploaded Models list.
Should I download any model below?
https://github.com/opencv/open_model_zoo/tree/2018/intel_models

@otsukaoly
Yes, You need to upload a model before you can use it.
It can be models from Open Model Zoo, or your custom models, converted to OpenVINO Inference Engine format.

Thank you for your reply.
I'm trying to execute the open_model_zoo module.
Now I have other problems about OpenSSL.
https://stackoverflow.com/questions/49302516/where-to-get-and-install-crypto-dll-on-64-bit-windows/56945015#56945015
It is not related to original issue.
So the status 'closed' is O.K.


fix pipe UV_HANDLE_EMULATE_IOCP implementation

UV_HANDLE_EMULATE_IOCP was missing a bit of code, and any tests.
Fixes: #629
CI: https://ci.nodejs.org/job/libuv-test-commit/1709/

OK, new changes are in separate commits (some style fixes, some fixup to squash on merge). new CI: https://ci.nodejs.org/job/libuv-test-commit/1736/

@vtjnash Want me to land this one for you?

That'd be great, I haven't had time recently to be able to devote to libuv.

Squashed the fixups and landed. Cheers @vtjnash !


Add health percentage to inotify_views for teams

Just so we can have some more information shared in teams.
-- Calculates the current health percent based on max health and current health
local health = (player:get_hp() / player.max_hp) * 100
And include this into some table probably to track players health values

This will be in yet another separated lua file so we can have some async updating.
Include coloring for noticeable visibility.

Todo:

[ ] Make health.lua and add a dofile in init.lua
[ ] Add the essential code to collect that information and update it only if needed
[ ] Add code to render it onto the HUD and update only if needed
[ ] Merge it into a function where we pass in position and offset, and alignment (So we can make it customizable)

I have removed the idea of this being a modpack.


Can It be this be upgraded to current factorio version 1.1

It would be nice if it could be upgraded to current factorio version

I have no idea, as I haven't played Factorio in a few years. However if anyone would like to modify/update it, they can feel free to do so. I will have to add a permissive license before so, so hang tight.

I added the MIT license, so feel free to do whatever with it :)


#375 - Allow option to select by partial text in the selectByVisiblePartialText…

#375 - Allow option to select by partial text in the selectByVisiblePartialText method.

Replaced by #391 . Thanks @cryptton2004 for your contribution 👍


Add BuyCoinNow.com to the bitcoincash.org

Sorry we aren't adding more exchanges at this time unless they are extremely well used and reviewed.


Dialog being read twice

Each dialog is being read by TTT twice, didn't happen yesterday, perhaps a small glitch that isn't consistent.

That typically happens when you have NPC dialogue checked in channel settings tab in the plugin settings.
Try turning unchecking that box and see if that helps. This is usually caused by the plugin reading dialogue posted in the chat and also reading the on screen dialogue box.

Has that always happened? It's supposed to track the last NPC text so that the chat handler can skip it.

It's been around as long as I can remember. I assume the chat handler has been catching most of them, but they must make it through sometimes.
Maybe differences of punctuations, or text continuing on a second text box.

It's been around as long as I can remember. I assume the chat handler has been catching most of them, but they must make it through sometimes.
Maybe differences of punctuations, or text continuing on a second text box.

I got a separate bug report about this in Discord saying the same thing, but it should have been fixed ever since #40 was closed. I thought this was something new 😵💫

I got a separate bug report about this in Discord saying the same thing, but it should have been fixed ever since #40 was closed. I thought this was something new 😵💫

TBH I used the addon for a few weeks without it happening, updated to the newest version, didn't change any settings, and it started doing it.  Even with 'cancel voice if new lines start' enabled it still happens, I can cancel the dialog and sometimes still get double voice.

TBH I used the addon for a few weeks without it happening, updated to the newest version, didn't change any settings, and it started doing it.  Even with 'cancel voice if new lines start' enabled it still happens, I can cancel the dialog and sometimes still get double voice.

And that option I mentioned earlier was already unselected?

I am having the same problem with some of my text, specifically green NPC dialogue in combat instances. My friend was helping me go through the settings and I found multiple instances of the NPC Dialogue option checked. If I uncheck the top one, the bottom one also unchecks. If I try to uncheck the bottom one, nothing happens. There are also multiple instances of NPC Announcement in that list. If I click on either instance of NPC Announcement, both toggle.

The duplicate options are fixed in the testing versions I think, that's just because Dalamud added them at some point and TTT combines that with its own list. That part shouldn't be causing issues since the settings are synchronized.


Cognito change password feature required

Is your feature request related to a problem? Please describe.
It is necessary to have a "change password" feature in sourceloop Cognito API. When a logged-in user tries to change their password, they should be able to change it both within the system and on the Cognito platform.
Currently, if the password is changed using the internal "change password" API, the user who interacts with the Cognito page first will not see the updated password. This means that although the user has changed their password by logging into the system and using the feature, it will not be updated in the Cognito platform.
Describe the solution you'd like
use cognito.changePassword method provided by CognitoIdentityServiceProvider as we  don't have direct API of change password  available in documentation.
Although there is provision of doing same through API as well but end point is not directly available.
So you can opt for any approach if you are able to find end point that will be better approach.
Describe alternatives you've considered
We have used currently cognito.changePassword method
Additional context
This action should be either independent so any BL can be implemented around it or it should be performed first than internal system change password, As we have to make sure internal system password only change when we are able to successfully update password on cognito

I dont agree with this request. Since we are using cognito as IDP, so we intentionally dont want to manage its passwords. You should redirect user to cognito  to change his own password there.

Yes cognito allow change password through UI , when you are on login or forget password screen of cognito.
But in case when already know your password and want change it after login into your profile and by change password feature.
In that case you cannot redirect user to cognito screen again as change password based on existing password cognito either allow through cli or API for that user-pool.
Also in the scenario like : tomorrow for xy reason I change my idp from cognito to other one or remove even the idp and directly use sourceloop authentication APIs , so in that case do we have to send every registered user temporary password again to reset and login

But in case when already know your password and want change it after login into your profile and by change password feature.
This is anti pattern and is a security issue. You should never store password if you are not IDP.

This is anti pattern and is a security issue. You should never store password if you are not IDP.
Agreed if we are not IDP we should not store , but we should change password at IDP when user request or that is also not correct?
And currently the reference we had for this was through the api provided by cognito or through CLI.
Do we have any UI reference as well where we can redirect user to UI for this particular part

No @sumit-singhania we should not manage passwords at all when we are not IDP. We should simply redirect user to IDP for these actions.

closing this as well.. this is an anti-pattern


Factor lost latency packets into packet loss calculations

I no longer think this is broken.  Lost latency packets appear to be getting tracked in the bulk packet loss counters.  Maybe they are also being tracked in the received packet counters as well.  This would mean there is no need to account for them when doing throughput calculations.  Need to investigate further.  Leaving this issue open until the behavior is completely understood.

Actually the lost latency packets should not be accounted for in the bulk network test.  Here is an example:
[Histogram port 0 to port 1] Samples: 4241, Average: 8726.3 ns, StdDev: 1069.2 ns, Quartiles: 8381.0/8557.0/8740.0 ns
[INFO]  Saving histogram to 'hist:0-1.csv'
[WARN]  [Histogram port 0 to port 1] Lost 316 samples (6.93%)!
[Histogram port 1 to port 0] Samples: 4228, Average: 8605.5 ns, StdDev: 940.2 ns, Quartiles: 8282.0/8470.0/8672.0 ns
[INFO]  Saving histogram to 'hist:1-0.csv'
[WARN]  [Histogram port 1 to port 0] Lost 328 samples (7.20%)!
[Device: id=0] RX: 0.00 Mpps, 0 Mbit/s (0 Mbit/s with framing)
[Device: id=1] RX: 0.00 Mpps, 0 Mbit/s (0 Mbit/s with framing)
[Device: id=0] RX: 9.70 (StdDev 3.55) Mpps, 4968 (StdDev 1817) Mbit/s (6520 Mbit/s with framing), total 329887235 packets with<PHONE_NUMBER>6 bytes (incl. CRC)
[Device: id=1] RX: 9.70 (StdDev 3.55) Mpps, 4968 (StdDev 1819) Mbit/s (6520 Mbit/s with framing), total 329877723 packets with<PHONE_NUMBER>4 bytes (incl. CRC)
[PARAMETERS] startRate: 11.000000 nrFlows: 1024 frameSize: 64 runBidirec: true latencyRunTime: 30 ports: 1,2
[REPORT]Device 0->1: Tx frames: 329877723 Rx Frames: 329877723 frame loss: 0, 0.000000% Rx Mpps: 10.996740
[REPORT]Device 1->0: Tx frames: 329887235 Rx Frames: 329887235 frame loss: 0, 0.000000% Rx Mpps: 10.996740
[REPORT]      total: Tx frames: 659764958 Rx Frames: 659764958 frame loss: 0, 0.000000% Tx Mpps: 21.993479 Rx Mpps: 21.993479
However, I don't think the lost latency packets should be counted as lost by the device-under-test.  The  problem is that the lost latency packets are usually not lost at all.  The MoonGen latency code seems to have problems in accounting for all packets, so we can distinguish between truly lost packets and packets that are not received properly.


Remove call to external commands.

Replace the call to find, by Find.find function.

Replace diff equivalent on Windows.
Note: there isn't -u/--label option on Windows, we just do the diff
without this extra arguments.

@facebook-github-bot import


fix routeEntryComplete state leakage (#543).

I think you can remove the test as it doesn't really test anything anyways.

Removed the test.

I think it's better to store this in a property of the application route that in the local variable anyway. That way we can also have a simple method in setup.js that unsets it and don't need the extra export in application-route-mixin.js. Sorry for the change in mind.

I think as a property on the application route there's no need to reset it during setup because the route object should be created fresh for each acceptance and unit test, no?
I've pushed a new version to my branch.

You're right of course and that makes it even simpler. Can you add a test?

Okay. Updated the tests and fixed the export statement.

:+1:


[bots] Do not invoke pub global run concurrently

dev/bots/analyze_sample_code.dart freezes intermittently on the Dart Flutter HHH bot.
Follow up of #90447 #90880, and #91024.
It turns out pub global run does not enjoy being invoked concurrently at the moment https://github.com/dart-lang/pub/issues/3165. (Thanks @cskau-g @sigurdm @szakarias for the help!) Invocations of pub global run were introduced in #87231 two months ago.
We have multiple options:

Wait for pub global run to be fixed https://github.com/dart-lang/pub/issues/3165 (but we have recurring failures on the HHH bot right now).
Reduce the concurrency to 1 task at the time for now (this PR). And revert it back when pub is patched.
Invoke import 'package:snippets/snippets.dart'; instead of using pub global run. However, a bunch of the logic is in bin/snippets.dart we would have to duplicate that logic or move it to the lib folder.
A good solution that didn't come to my mind...

Background info: go/flutter-hhh-analyze-freezes
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

I still believe pub global run should be thread safe for this task (as long as the snapshot has not been deleted I don't see how a race can occur). But I might be overlooking something...

But I might be overlooking something...

@sigurdm The first flutter analyze failure is 15th of august, the mentioned PR starting to use pub global run was merged 12th of august. Also, we can see that the crashes are from pub global run. So, I would be very surprised if this is not due to pub global run. We must be overlooking something.

First, obviously, we should definitely fix dart pub global run if it is broken. It's mainly useful for software tools, and software tools will be run concurrently.

Invoke import 'package:snippets/snippets.dart'; instead of using pub global run. However, a bunch of the logic is in bin/snippets.dart we would have to duplicate that logic or move it to the lib folder.

I actually think this is the best option. Dartdoc has a built-in ability to snapshot dart tools. I wrote that when I added tools to Dartdoc, because otherwise it's too slow to be practical. If we refactor the snippets tool so that the main logic is in the package, and then create a .dart file in the flutter repo that just invokes that main by passing in the arguments, Dartdoc will take care of snapshotting it and running it concurrently. This could serve as a temporary solution until global run is fixed.
My goals were to 1) speed up Dartdoc invocation by running tools concurrently, and 2) move the snippets code out of the Flutter repo. I'd rather not backtrack on those by switching back to serial execution or by moving logic back into the Flutter repo.
 One would think that if there is a race, it would be far more likely to happen there than on a 4-core bot. We should try creating a pathological case (dart pub run snippets --help) and run a bunch of jobs concurrently and see if we can get it to fail.

Me too. I'm also not able to make it fail locally.

Invoke import 'package:snippets/snippets.dart'; instead

I actually think this is the best option.

That's fine with me. Do you want to take a shot at that? Otherwise I can take a look after the weekend.

Do you want to take a shot at that? Otherwise I can take a look after the weekend.

Sure, I can do that.

Actually, @dcharkes how about this: Now that we know that it is related to the first-run executable building, we just add a dart pub global run snippets --help > /dev/null into the Flutter docs.sh script right after activating the tool. That should prevent this issue, and be very low-impact (and also not a lot of work: I'm all for lazy evaluation! :-) ).

Closing in favor of

#91110


Add factorio types from FactorioLab to the monorepo.

Add factorio types from FactorioLab to the monorepo.

should definitely be using https://github.com/factoriolab/factoriolab/tree/4ac80cb416e779819a73b871dd3e32ab7e0cda0c/src/app/models


Short solution needed: "Get current time" (lua)

Please help us write most modern and shortest code solution for this issue:
Get current time (technology: lua)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Get current time