text:
CIV-6825 Apply Date Formatter

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-6825
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

repo: hmcts/civil-ccd-definition


text:
NFDIV 2705 - Withdrawn notification updates

Change description

App2 should only receive withdraw notification if they have already been linked.

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/NFDIV-2705
Before merging a pull request make sure that:

[ ] tests have been updated / new tests has been added (if needed)
[ ] README and other documentation has been updated / added (if needed)

If this ticket will have any visible impact on users and is not behind a feature toggle, make sure that:

[ ] this ticket been reviewed by QA
[ ] the user story been signed off by the PO

Note that bug fixes, dependency updates and technical tasks do not directly impact the user experience and can be merged without QA and PO review.
If this user story cannot be immediately merged find a way to put it behind a feature toggle and get it merged.

Moved to #2563

source: gharchive/pull-request

repo: hmcts/nfdiv-case-api

license: MIT

license_type: permissive

license_source: github-api


text:
[FEAT]: Database Setup

Description
Set up a database for the chosen framework’s ORM, allowing configuration for any database but defaulting to Postgres. Follow migrations, models, and service patterns to ensure a robust and flexible database setup.
Acceptance Criteria

Database Configuration:

Set up the database for the chosen framework’s ORM.
The setup should allow configuration for any database, with Postgres as the default.
Follow migrations, models, and service patterns.

Validation:

Create the following tables and constraints:

Users: A user has one profile.
Profiles: A user has one profile.
Organisations: A user belongs to many organisations. An organisation has many users.
Products: A user has many products.

Seed the tables with the following data:

At least 2 users.
At least 2 products per user.
At least 3 organisations.
User one belongs to 2 of the organisations.
User two belongs to all 3 organisations.

Example Data

Tables and Constraints:

Users table
Profiles table
Organisations table
Products table
Relationships:

A user has one profile.
A user has many products.
A user belongs to many organisations.
An organisation has many users.

Table Seeding:

Users: At least 2 users.
Products: At least 2 products per user.
Organisations: At least 3 organisations.
User one belongs to 2 of the organisations.
User two belongs to all 3 organisations.

Example Endpoints

[GET] api/v1/users/user_one_id

Sample Response:

{
  "name": "John Doe",
  "id": "some-user-id",
  "email": "johndoe@example.com",
  "profile": {
    "first_name": "John",
    "last_name": "Doe",
    "phone": "1234567890",
    "avatar_url": "http://example.com/avatar.jpg"
  },
  "organisations": [
    {
      "org_id": "some-org-id-1",
      "name": "Some Org",
      "description": "Some Org Description"
    },
    {
      "org_id": "some-other-org-id-2",
      "name": "Some Other Org",
      "description": "Some Other Org Description"
    }
  ],
  "products": [
    {
      "product_id": "some-product-id",
      "name": "Some Product",
      "description": "Some Product Description"
    },
    {
      "product_id": "some-other-product-id",
      "name": "Some Other Product",
      "description": "Some Other Product Description"
    }
  ]
}

[GET] api/v1/users/user_two_id

Sample Response:

{
  "name": "John Doe",
  "id": "some-user-id",
  "email": "johndoe@example.com",
  "profile": {
    "first_name": "John",
    "last_name": "Doe",
    "phone": "1234567890",
    "avatar_url": "http://example.com/avatar.jpg"
  },
  "organisations": [
    {
      "org_id": "some-org-id-1",
      "name": "Some Org",
      "description": "Some Org Description"
    },
    {
      "org_id": "some-other-org-id-2",
      "name": "Some Other Org",
      "description": "Some Other Org Description"
    },
    {
      "org_id": "some-other-org-id-3",
      "name": "Some Other Org",
      "description": "Some Other Org Description"
    }
  ],
  "products": [
    {
      "product_id": "some-product-id",
      "name": "Some Product",
      "description": "Some Product Description"
    },
    {
      "product_id": "some-other-product-id",
      "name": "Some Other Product",
      "description": "Some Other Product Description"
    }
  ]
}

Implementation

Clone the boilerplate for your framework.
Create a branch named chore/database-setup from the base branch.
Implement the database setup as described above.

Expected Outcome

The database is set up with the required tables and relationships.
The tables are seeded with the provided sample data.
The specified endpoints return the expected responses.

Testing

Validate the database setup by ensuring the tables and relationships are correctly created.
Verify the data seeding by querying the database.
Test the endpoints to ensure they return the correct data.

Notes

Ensure compliance with security standards for data handling.
Write unit tests and integration tests to validate the database setup and endpoints.

DB setup tasks will not be accepted as tickets

source: gharchive/issue

authors: markessien nadduli


text:
Process No defined on terminal app  pear dev

Following the p2p file sharing doc
ReferenceError: process is not defined
at pear://dev/node_modules/pear-stdio/index.js:7:15
at Module._extensions..cjs (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:549:117)
at Module._extensions..js (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:519:51)
at Module.load (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:321:36)
at Module._onimport (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:202:25)
at Module._evaluate (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:126:13)
at Module._transform (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:117:12)
at Module.load (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/node_modules/bare-module/index.js:325:19)
at Crank.run (file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/ipc/crank.js:51:14)
at async file:///Users/saransh/Library/Application%20Support/pear/by-dkey/7216eeac5c879a2ca1dcff14bb8c1ad47d188a8c17b13e66f36d354ea8bd3b28/1/boot.bundle/cmd/iface.js:60:39

Ah ya, docs aren't super clear on this but the terminal apps are a Bare process. This means you have to provide the apis you want to use.
To use process simply npm install bare-process (https://github.com/holepunchto/bare-process)
and do
const process = require('bare-process')

For fullish Node.js compat see
https://github.com/holepunchto/bare-node

I ran into the same trying to get the p2p file sharing demo (terminal) to work.
The problem was in a module, pear-stdio which could not find process. I changed the demo to use bare-tty for input and it seems to work better:
import Hyperswarm from "hyperswarm";
import Hyperdrive from "hyperdrive";
import Localdrive from "localdrive";
import Corestore from "corestore";
import debounce from "debounceify";
import b4a from "b4a";
import tty from "bare-tty";
import readline from "bare-readline";

// create a Corestore instance
const store = new Corestore(Pear.config.storage);
const swarm = new Hyperswarm();
Pear.teardown(() => swarm.destroy());

// replication of the corestore instance on connection with other peers
swarm.on("connection", (conn) => store.replicate(conn));

// A local drive provides a Hyperdrive interface to a local directory
const local = new Localdrive("./writer-dir");

// A Hyperdrive takes a Corestore because it needs to create many cores
// One for a file metadata Hyperbee, and one for a content Hypercore
const drive = new Hyperdrive(store);

// wait till the properties of the hyperdrive instance are initialized
await drive.ready();

// Import changes from the local drive into the Hyperdrive
const mirror = debounce(mirrorDrive);

const discovery = swarm.join(drive.discoveryKey);
await discovery.flushed();

console.log("drive key:", b4a.toString(drive.key, "hex"));

// start the mirroring process (i.e copying) of content from writer-dir to the drive
// whenever somebody enters a line into the terminal
const rl = readline.createInterface({
  input: new tty.ReadStream(0),
  output: new tty.WriteStream(1),
});

rl.input.setMode(tty.constants.MODE_RAW);
rl.on("data", async (line) => {
  await mirror();
  rl.prompt();
});
rl.prompt();

// this function copies the contents from writer-dir directory to the drive
async function mirrorDrive() {
  rl.write("started mirroring changes from './writer-dir' into the drive...\n");
  const mirror = local.mirror(drive);
  await mirror.done();
  rl.write(`finished mirroring: ${JSON.stringify(mirror.count, null, 2)}\n`);
}

cc @subashsn lets get the docs updated to not use pear-stdin - we stopped supporting that

Sure

authors: mafintosh mattdesl saranshisatgit subashsn

repo: holepunchto/pear


text:
🛑 Bun Loyal is down

In c520984, Bun Loyal (https://bun.loyal.sh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bun Loyal is back up in c1e33a9 after 12 minutes.

repo: hollydotpw/magical-services-status


text:
Limit number of rows displayed by UI at once

Don't want to blow up peoples browser accidentally

Coverage increased (+2.6%) to 71.293% when pulling 9fad09d6ed20b213e010f102eac9deedd5ad887a on ui_max_rows into 68f874de156df0a400b8b7f9307c8a008ee1e0f5 on master.

authors: coveralls philippjfr

repo: holoviz/hvplot


text:
Add a shortcut for setting download format in a view

It makes it possible to just paste a string into a View for the download option.
import lumen
import panel as pn
import yaml
from lumen.layout import Layout
from lumen.pipeline import Pipeline
from lumen.sources import FileSource
from lumen.views import Table

pn.extension("tabulator")

data_url = "https://datasets.holoviz.org/penguins/v1/penguins.csv"

pipeline = Pipeline(source=FileSource(tables={"penguins": data_url}), table="penguins")
pipeline.add_filter("widget", field="species")

view = Table(pipeline=pipeline, download="csv")
# Before: Table(pipeline=pipeline, download=Download(format="csv")) and this import from lumen.views.base import Download

specification = lumen.state.to_spec(
    config={"title": "test"},
    layouts=[Layout(views=[view])],
)

print(yaml.dump(specification))

Looks good to me!

authors: Hoxbro philippjfr

repo: holoviz/lumen


text:
Supports keys converted to atom type

It can look like this:
XmlToMap.naive_map(xml_text, keys: :atoms) and XmlToMap.naive_map(xml_text, keys: :atoms!)
Refer to the related design of the Jason library: https://hexdocs.pm/jason/Jason.html#decode/2

Well I guess I'm fine with that feature if there is a precedent for it.  I don't have time to code this up, but a PR with a test would be welcome!

OK I will open a PR when I have time!

@homanchou Using a internal xml in test file selftitled as sample_xml, can you confirm if the expected result is equals to the result bellow ?
 ```elixir
  %{
  orders: %{
    order: [
      %{
        billing_address: "My address",
        id: "123",
        items: %{
          item: [
            %{
              "#content": %{
                description: "Hat",
                price: "5.99",
                quantity: "1",
                sku: %{"#content": "ABC", "-lang": "en"}
              },
              "-currency": "USD"
            },
            %{
              "#content": %{
                description: "Bat",
                price: "9.99",
                quantity: "2",
                sku: "ABC"
              },
              "-currency": "USD"
            }
          ]
        }
      },
      %{
        billing_address: "Uncle's House",
        id: "124",
        items: %{
          item: %{
            "#content": %{
              description: "Hat",
              price: "5.99",
              quantity: "2",
              sku: "ABC"
            },
            "-currency": "USD"
          }
        }
      }
    ]
  }
}```

Yes it looks correct by my eyeballing it.  But I'm confused why you are you asking me here when ... doesn't the very first test in the test file already assert something like this?

Thanks for your reply @homanchou . In fact, the structure of the first test returns exactly this value that I left as an example above, but I made all the keys to be converted to atom type. I built a helper module so that when I insert %{keys: :atoms} into the naive_map function, all keys can be returned in the requested format. I want to send a pull request with greater accuracy and I left the example above just to see if this is the expected return.

closing for now.  can be re-opened if someone wants to make a PR.  otherwise folks can use an external lib to make atom keys out of strings if they want to.

authors: Hentioe LeandroFigueredo homanchou

repo: homanchou/elixir-xml-to-map


text:
feature request: state with raw data

 -  was noch cool wäre:
in info, ein Objekt JSON, in den du einfach hart das letzte empfangene JSON schreibst. das man damit recht einfach sehen kann was er aktuell empfängt. also komplett ohne weitere Bearbeitung.

Test okay
RAW data will be written into object rawJSON
Thanks.

0.2.0 released to NPM

authors: Enno-von-Schwerin hombach


text:
Unexpected zwave entity ID

Home Assistant release (hass --version): dev branch @ 9d5dee574a07297e6017a34c722be481be01936f
Python release (python3 --version): Python 3.5.2
Component/platform: zwave
Description of problem: zwave switch has an unexpected entity ID. The entity ID uses the manufacturer and product name instead of the assigned node name. The associated zwave. entity ID is correct.
Expected: zwave switch to use assigned node name.
What I have now: switch.homeseer_hsws100_wall_switch_switch
What it should be: switch.zwave_switch_1_switch
Additional info:

The zwave entity ID is correct: zwave.zwave_switch_1.
The node is named zwave_switch_1
The entity attribute new_entity_id on the switch is correct (switch.zwave_switch_1_switch).
The device in question is a HomeSeer HS-WS100+ Wall Switch.
I have multiple switches of this type; only one exhibits this behavior (renamed after upgrade to python-openzwave 0.4.3)

hmm, I the entity IDs were not supposed to change.
I've added an Entity Registry to Home Assistant in the dev branch. It means that devices that include a unique ID (like Z-Wave), will always get the same entity ID after each restart. No other devices will be able to get the registered entity ID. It's reserved.
You can change the entity ID in <config>/entity_registry.yaml. For now it will require a restart for Home Assistant to pick up the changes.

That was the problem. Somehow the entity registry will have to handle excluding/including/renaming zwave nodes.

The idea is to make a UI so people can see which devices are remembered and remove entity ID reservations that are no longer necessary. Only at registration is an integration able to suggest a possible entity ID. After that, it is assigned one and that one is used.

authors: balloob happyleavesaoc

repo: home-assistant/home-assistant


text:
docker build fails to find ffmpeg on dev

Home Assistant release with the issue:
0.72.0 and dev
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Description of problem:
I was trying to build a custom docker image to test a development fix, but docker build . is failing with an unrelated error. I confirmed it happens on 0.72.0 tag and dev branch.
Traceback (if applicable):
Sending build context to Docker daemon  15.98MB
Step 1/11 : FROM python:3.6
 ---> 79e1dc9af1c1
Step 2/11 : LABEL maintainer "Paulus Schoutsen <Paulus@PaulusSchoutsen.nl>"
 ---> Using cache
 ---> c331fddb954a
Step 3/11 : VOLUME /config
 ---> Using cache
 ---> 7a7c9e426f8f
Step 4/11 : RUN mkdir -p /usr/src/app
 ---> Using cache
 ---> 0b1b2ce96f0e
Step 5/11 : WORKDIR /usr/src/app
 ---> Using cache
 ---> afeeb20390eb
Step 6/11 : COPY virtualization/Docker/ virtualization/Docker/
 ---> Using cache
 ---> 608d3b333929
Step 7/11 : RUN virtualization/Docker/setup_docker_prereqs
 ---> Running in 89357389e80c
Get:1 http://security.debian.org jessie/updates InRelease [94.4 kB]
Ign http://deb.debian.org jessie InRelease
Get:2 http://deb.debian.org jessie-updates InRelease [145 kB]
Get:3 http://security.debian.org jessie/updates/main amd64 Packages [624 kB]
Get:4 http://deb.debian.org jessie Release.gpg [2420 B]
Get:5 http://deb.debian.org jessie Release [148 kB]
Get:6 http://deb.debian.org jessie-updates/main amd64 Packages [23.0 kB]
Get:7 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Fetched 10.1 MB in 3s (3301 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Package ffmpeg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package libsodium18
E: Package 'ffmpeg' has no installation candidate
The command '/bin/sh -c virtualization/Docker/setup_docker_prereqs' returned a non-zero code: 100

Additional information:
It doesn't seem that jessie includes ffmpeg, but jessie-backports has it. It looks like there had been some changes to the build recently.
https://github.com/home-assistant/home-assistant/pull/5322/files originally introduced the addition of the jessie backports, but https://github.com/home-assistant/home-assistant/pull/14626 removed it.
https://github.com/home-assistant/home-assistant/pull/14624 looks in this area too.

I read https://github.com/home-assistant/home-assistant/pull/14624 a little more closely, and it suggests that the underlying python:3.6 docker image changed from jessie to stretch. I did a docker pull python:3.6, and that fixed the problem.
Does that mean the Dockerfile should specify a more specific image? Switching to python:3.6-stretch would make sure that anyone that has pulled python:3.6 gets on the right image.


text:
Google assistant not able to connect to home-assistant cloud

Home Assistant release with the issue:

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

Raspbian:- Hass installed as systemd service
Component/platform:

https://www.home-assistant.io/components/google_assistant/
Description of problem:
The google assistant does not sync with the home assistant cloud instance, I can login to the home assistant cloud instance and it shows that the account is linked.
But the callback to google home app fails and it shows "Could not update setting, please check your connection". I have tried doing the same flow with both wifi and 4g networks.
Dont know whether there is some issue with hass cloud backend or with google oauth flow or my manual config error
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

```cloud: !include cloud.yaml

logbook:
  include:
    entities:
      - device_tracker.nirmit
      - device_tracker.pavan
      - device_tracker.nirmit
      - sensor.state
      - sun.sun
      - sensor.laststate
      - light.lifx_241141
      - switch.fan
      - light.table_lamp
  exclude:
    domains:
      - automation
      - script
      - input_boolean
      - group
      - zone

logger:
  default: warning
  logs:
    homeassistant.components.mqtt: debug
history:
  include:
    domains:
      - sensor
      - switch
      - light
      - binary_sensor

recorder:
  purge_keep_days: 2
  purge_interval: 2

config:
conversation:
dialogflow:
discovery:
frontend:
map:
sun:
updater:

cloud.yaml:

google_actions:
  filter:
   exclude_domains:
     - group
     - automation
     - input_boolean

Traceback (if applicable):

Additional information:

shouldnt it just be cloud:
or if you wanted to include a seperate config file cloud: !include cloud.yaml

authors: IxsharpxI sriramsv


text:
Warning message about [names] in HA 0.88.0

Home Assistant release with the issue:
0.88.0
Last working Home Assistant release (if known):
0.87.1
Operating environment (Hass.io/Docker/Windows/etc.):
hassio
Component/platform:
home assistant
Description of problem:
since HA 0.88.0 I get a warning message regarding [names] (and [friendly_name]) in configuration.yaml. I eliminated all friendly names (and did it now via customize,yaml) but if I tried to delete [name] it leads in a lot of problems. e.g my mqtt sensors got with every new start of HA new numbers like sensor.mqtt_sensor_1 next time same sensor sensor.mqtt_sensor_2 what confused my complete lovelace UI. Is there a way to avoid this? How shall I do this for example with notify componenet?
Additional information:

and BTW in line is nothing with [name]:

Do you have some includes in your config ? I guess includes just add new lines by including the other file in you configuration.yaml resulting in wrong line number.  => not sure of this but worth a try :)

Does the platform just below that have a name field?  The line in the error isn’t always accurate.  Most likely a platform a few lines below has a name field.

authors: Obicom SNoof85 bryeartem


text:
Abode Light, Humidity and Temperature Sensor Not Reporting Data for Temperature Entity

Home Assistant release with the issue:
0.102
Last working Home Assistant release (if known):
0.100.3
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Integration:
Abode
Description of problem:
The fix in #28481 re-exposed the three functions sensor entities properly, and light and humidity seem to be reporting data properly, but temperature does not.  There are no errors in the logs, but I have provided a snipet of the logs for a specific sensor setup below if that helps.  I'm also including screenshots of the Device setup as well as the different between humidity and temperature entities.  Note that the presets for automations do not include the temperature entities as options which leads me to believe there is some sort of setup issue, potentially a device type or unit of measure mismatch?  In the logs the temperature sensor is missing a unit of measurement where the other two are set.  I have attempted to set this manually through customization but that doesn't appear to resolve the issue.
Additional details:
Image of device:

Image of working humidity entity:

Image of non working temperature:

Setup lot for sensor shown in screenshots:
2019-11-21 10:36:11 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.abode entity: sensor.guest_sensor_temperature 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event entity_registry_updated[L]: action=create, entity_id=sensor.guest_sensor_temperature> 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.guest_sensor_temperature, old_state=None, new_state=<state sensor.guest_sensor_temperature=unknown; attribution=Data provided by goabode.com, device_id=ZB:d42d01, battery_low=False, no_response=False, device_type=LM, friendly_name=Guest Sensor Temperature, device_class=temperature @ 2019-11-21T10:36:11.941376-08:00>> 2019-11-21 10:36:11 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.abode entity: sensor.guest_sensor_humidity 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event entity_registry_updated[L]: action=create, entity_id=sensor.guest_sensor_humidity> 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.guest_sensor_humidity, old_state=None, new_state=<state sensor.guest_sensor_humidity=40.0; attribution=Data provided by goabode.com, device_id=ZB:d42d01, battery_low=False, no_response=False, device_type=LM, unit_of_measurement=%, friendly_name=Guest Sensor Humidity, device_class=humidity @ 2019-11-21T10:36:11.947053-08:00>> 2019-11-21 10:36:11 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.abode entity: sensor.guest_sensor_lux 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event entity_registry_updated[L]: action=create, entity_id=sensor.guest_sensor_lux> 2019-11-21 10:36:11 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.guest_sensor_lux, old_state=None, new_state=<state sensor.guest_sensor_lux=0.0; attribution=Data provided by goabode.com, device_id=ZB:d42d01, battery_low=False, no_response=False, device_type=LM, unit_of_measurement=lux, friendly_name=Guest Sensor Lux, device_class=illuminance @ 2019-11-21T10:36:11.952759-08:00>>

@shred86 FYI, I believe this might also impact the occupancy sensor you put a fix in for, but I do not have one to verify.

@gregorymartin Would you be able to test this change I made to sensor.py in a custom_component (will need all of the files associated with the abode component in addition to this new sensor.py)?
https://github.com/shred86/home-assistant/blob/abode_fix/homeassistant/components/abode/sensor.py

@shred86 just tested that file as part of a custom component in the same instance I took the screenshots from and it appears to be working as expected now.  Thanks for the quick turn!  Sorry I didn't catch this in the last round of testing.  Hopefully we can get this pushed into the 0.102.1 release.

Thanks for testing that. I figured that was the issue. Pull request created and I added a request to add it to the 102.2 milestone (102.1 is already released).


text:
First start of 0.105.5 produces error

The first start after installing HA 0.105.5 on MacOS 10.15.3 produces error shown below:
2020-02-26 11:31:23 INFO (SyncWorker_4) [homeassistant.loader] Loaded tradfri from homeassistant.components.tradfri
Exception in thread zeroconf-ServiceBrowser__hap._tcp.local.:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1483, in run
    handler(self.zc)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1422, in <lambda>
    lambda zeroconf: self._service_state_changed.fire(
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1301, in fire
    h(**kwargs)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/homeassistant/components/zeroconf/__init__.py", line 89, in service_update
    info = info_from_service(service_info)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/homeassistant/components/zeroconf/__init__.py", line 166, in info_from_service
    address = service.addresses[0]
IndexError: list index out of range

This does not seem particular to Tradfri. On the second start I get a similar error for homekit:

2020-02-26 11:52:42 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of homekit[IP]==0.15.0
Exception in thread zeroconf-ServiceBrowser__hap._tcp.local.:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1483, in run
    handler(self.zc)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1422, in <lambda>
    lambda zeroconf: self._service_state_changed.fire(
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/zeroconf/__init__.py", line 1301, in fire
    h(**kwargs)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/homeassistant/components/zeroconf/__init__.py", line 89, in service_update
    info = info_from_service(service_info)
  File "/Users/gebruiker/homeassistant/lib/python3.8/site-packages/homeassistant/components/zeroconf/__init__.py", line 166, in info_from_service
    address = service.addresses[0]
IndexError: list index out of range

Could you please use the issue template provided? Thanks!

Please fill out the issue template, you can find it by clicking on New Issue and then selecting Report a bug with Home Assistant. Copy and paste the provided template into this already created issue, click preview to take a look at the empty template and then fill out as much as you can. Any additional information can be helpful!
Thanks for understanding :)

But first first, start by upgrading to 0.106.1

Two releases later and no update from author...

authors: Kane610 ahartman frenck springstan


text:
setting up bluetooth tracker fails on macOS

Home Assistant release (hass --version): 0.49.1
Python release (python3 --version): 3.6.2
Component/platform: bluetooth_tracker
Description of problem: setup fails on macOS
Traceback (if applicable):
17-07-28 18:46:30 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform bluetooth_tracker
Traceback (most recent call last):
  File "/lib/python3.6/site-packages/homeassistant/components/device_tracker/__init__.py", line 159, in async_setup_platform
    disc_info)
  File "/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 60, in setup_scanner
    for dev in discover_devices():
  File "/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 38, in discover_devices
    lookup_class=False)
  File "/usr/local/lib/python3.6/site-packages/PyBluez-0.22-py3.6.egg/bluetooth/osx.py", line 12, in discover_devices
    devices = lightblue.finddevices(getnames=lookup_names, length=duration)
  File "/usr/local/lib/python3.6/site-packages/PyBluez-0.22-py3.6.egg/lightblue/_lightblue.py", line 48, in finddevices
    inquiry.run(getnames, length)
  File "/usr/local/lib/python3.6/site-packages/PyBluez-0.22-py3.6.egg/lightblue/_lightblue.py", line 349, in run
    _macutil.waituntil(lambda: not self._inquiring)
  File "/usr/local/lib/python3.6/site-packages/PyBluez-0.22-py3.6.egg/lightblue/_macutil.py", line 152, in waituntil
    e = app.nextEventMatchingMask_untilDate_inMode_dequeue_(NSAnyEventMask, NSDate.dateWithTimeIntervalSinceNow_(min(endtime - currtime, WAIT_MAX_TIMEOUT)), NSDefaultRunLoopMode, True)
objc.error: NSInternalInconsistencyException - nextEventMatchingMask should only be called from the Main Thread!

Additional info:
I verified that the PyBluez installation works by running their example script:
# simple inquiry example
import bluetooth

nearby_devices = bluetooth.discover_devices(duration=8, lookup_names=True, flush_cache=True, lookup_class=False)
print("found %d devices" % len(nearby_devices))

for addr, name in nearby_devices:
    print("  %s - %s" % (addr, name))

This prints the mac address and name of my phone.

After digging through the code, the issue seems to be that, within Home Assistant, the component is set up in a separate thread which is not compatible with the way PyBluez is implemented. The waitUntil function in https://github.com/karulis/pybluez/blob/master/osx/_macutil.py#L118 uses nextEventMatchingMask_untilDate_inMode_dequeue_ to wait until the scan is complete. This function can only be called from the main thread.
I think there are only a few solutions to get this working:

spawn a separate process instead of just a thread to run the PyBluez code
run this component from the main thread: this is probably not an option because of the Home Assistant architecture
modify the PyBluez code: not trivial because of the Cocoa bindings
switch to another bluetooth library with better cross platform support: the current lib is no longer maintained and the version on Pypi severely lags behind the code on github. Unfortunately I could find an alternative in my initial search.

@pvizeli do you have a suggestion?

Still an issue


text:
Add support for specifying custom headers for rest_command

Description:
Add support for passing custom headers for rest_command similar to rest sensor.
Pull request in home-assistant.github.io with documentation: home-assistant/home-assistant.github.io#4747
Example entry for configuration.yaml:
  turn_off_sony_television:
    url: 'http://192.168.1.100/IRCC'
    method: post
    headers:
      X-CERS-DEVICE-ID: abcdef
    payload: '<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:X_SendIRCC xmlns:u="urn:schemas-sony-com:service:IRCC:1"><IRCCCode>AAAAAQAAAAEAAAAvAw==</IRCCCode></u:X_SendIRCC></s:Body></s:Envelope>'

Checklist:

[x] The code change is tested and works locally.
[x] Documentation added/updated in home-assistant.github.io
[x] Local tests with tox run successfully.
[x] Tests have been added to verify that the new code works.

Thank you! 🎆
In the future just keep pushing new commits, we squash all PRs on merge in any case and it makes review easy if you can see what changed.

authors: doctorjames kellerza


text:
Migration of Foobot component from sensor to air quality

Description:
I've migrated the Foobot component to use the new air_quality platform.
It is a breaking change, of course configuration-wise but also because the separate sensors are now one unified sensor with attributes.
I'll provide shortly a configuration sample using sensor templates to mitigate breakage for existing users.
I've also included a function to convert pm 2.5 levels to AQI using US EPA's formula, this could be useful for other components.
Related issue (if applicable): https://github.com/home-assistant/architecture/issues/109
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8243
Example entry for configuration.yaml (if applicable):
air_quality:
  - platform: foobot
    token: FOOBOT_SECRET_KEY
    username: FOOBOT_USERNAME

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

This PR seems to have gone stale. Closing it.

authors: balloob reefab


text:
Improved local ip

Description:
I am aware this issue was closed, but the same issue does not only occur with homekit, but also when using the zeroconf component. When a VPN is running on my Mac, and I start home assistant, the zeroconf component will advertise itself on the network with my VPN's outbound IP address, not the local ip. This essentially breaks zeroconf, as the correct IP address of home assistant cannot be discovered by anyone then.
Related issue: fixes #14107
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox.
[X] There is no commented out code in this PR.

This PR is breaking Windows support, which is not allowed. It is also not clear to me what the goal is. It seems like quite an edge case that people run Home Assistant on their main computer and are on a VPN with that and are not always on that VPN with all their devices.

It is an edge case for sure. But you can be on VPN with all devices and it still doesn't work as expected.
I live in a country with restrictions on the internet and am on VPN 24/7
My local network is in the range 10.2.1.0/24
When I turn on my VPN on my mac it creates a new interface utun1, and assigns itself a random local IP in 169.254.0.0/16 or 192.168.0.0/16....
The current get_local_ip returns the IP address of my utun1 interface. The zeroconf component uses this function to broadcast it's IP.... Other devices that search for home assistant using mdns will then try to connect to the local ip of the VPN on my home assistant machine which is not reachable. I need zeroconf to broadcast the IP of the machine running home assistant....
I didn't test this on Windows though, I could try to rewrite it using netifaces.

Found another workaround here.... still think this isn't the best solution to get local IP, but to support Windows I need to introduce the netifaces package.

authors: balloob brouwer


text:
Fire restarted event on restarting active timer

Breaking Change:
Can break automations that should trigger on every timer start event.
Description:
Currently, the restart event is only triggered for paused timers, which is not ideal.
Related issue (if applicable): fixes #30448

As a sidenote:
We should probably add a the option to have not restartable timers.


text:
Isy fixes

Description:
A couple of small issues, nothing too major.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

🐬

@Teagan42 - not sure why, but my lamp dimmers still aren't showing up as entities when running the latest dev branch.
16-09-20 13:59:07 homeassistant.components.isy994: ISY Update Received:
<?xml version="1.0"?><Event seqnum="7" sid="uuid:92"><control>ST</control><action uom="51" prec="0">0</action><node>ZW002_1</node><eventInfo></eventInfo></Event>
16-09-20 13:59:07 homeassistant.components.isy994: ISY Updated Node: ZW002_1
16-09-20 13:59:07 homeassistant.components.isy994: ISY Update Received:
<?xml version="1.0"?><Event seqnum="8" sid="uuid:92"><control>ST</control><action uom="51" prec="0">0</action><node>ZW003_1</node><eventInfo></eventInfo></Event>
16-09-20 13:59:07 homeassistant.components.isy994: ISY Updated Node: ZW003_1

But no entities for these show up (under light or any other domain)

I think it may be due to the fact that those are not returning a
<property> element - are you up to date on ISY firmware?
On Tue, Sep 20, 2016 at 1:26 PM, Bryce Edwards notifications@github.com
wrote:

@Teagan42 https://github.com/Teagan42 - not sure why, but my lamp
dimmers still aren't showing up as entities when running the latest dev
branch.
16-09-20 13:59:07 homeassistant.components.isy994: ISY Update Received:
ST0ZW002_1
16-09-20 13:59:07 homeassistant.components.isy994: ISY Updated Node: ZW002_1
16-09-20 13:59:07 homeassistant.components.isy994: ISY Update Received:
ST0ZW003_1
16-09-20 13:59:07 homeassistant.components.isy994: ISY Updated Node: ZW003_1
But no entities for these show up (under light or any other domain)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248406651,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZbxEKeWpft1SA0epuMZL5AKreD4Wks5qsDN8gaJpZM4KBLUV
.

Yes, I was actually running the latest RC release, but I reverted to the latest official release to be sure & same behavior.
I'm not seeing a  element in the XML on any of the nodes (logged in debug mode for the component)

I will try to look tonight.
On Tue, Sep 20, 2016 at 3:04 PM, Bryce Edwards notifications@github.com
wrote:

Yes, I was actually running the latest RC release, but I reverted to the
latest official release to be sure & same behavior.
I'm not seeing a element in the XML on any of the nodes (logged in debug
mode for the component)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248433872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZS0gMtw2ZUqsUaYCtW0XtQLK81Wpks5qsEpqgaJpZM4KBLUV
.

Can you add these lines in components/isy994.py line 97

if node.name == 'ZW_001' or node.name == 'ZW_002':
    _LOGGER.debug(str(node.name) + ' ' + str(node.uom))

On Tue, Sep 20, 2016 at 4:21 PM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

I will try to look tonight.
On Tue, Sep 20, 2016 at 3:04 PM, Bryce Edwards notifications@github.com
wrote:

Yes, I was actually running the latest RC release, but I reverted to the
latest official release to be sure & same behavior.
I'm not seeing a element in the XML on any of the nodes (logged in debug
mode for the component)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248433872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZS0gMtw2ZUqsUaYCtW0XtQLK81Wpks5qsEpqgaJpZM4KBLUV
.

OK, here's some details.  I tweaked your code a bit as I didn't get any debug output (the node names were not as I expected, so I added another log line)
Code (starting line 96)
    for (path, node) in ISY.nodes:
        _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
        if node.name == 'ZW002' or node.name == 'ZW003':
            _LOGGER.debug('FOUND: ' + str(node.name) + ' ' + str(node.uom))

        hidden = hidden_identifier in path or hidden_identifier in node.name

Log output:
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/ping
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/config
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Configuration
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/nodes?members=false
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Nodes
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/programs?subfolders=true
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded/Updated Programs
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/1
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/2
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/1
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/2
16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Variables
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Opener ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Binary Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Multilevel Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Pulse Meter {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Power Management {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Tamper Sensor ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Back Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Garage Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.bootstrap: Error during setup of component isy994
Traceback (most recent call last):
  File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/bootstrap.py", line 102, in _setup_component
    result = component.setup(hass, config)
  File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 181, in setup
    _categorize_nodes(hidden_identifier, sensor_identifier)
  File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 97, in _categorize_nodes
    _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
AttributeError: 'Group' object has no attribute 'uom'

OK, I seem to have had luck by changing line 38 of homeassistant/components/light/isy994.py to:
if node.dimmable or node.uom == '51' or '51' in node.uom:

In debugging this further I'm noticing that ISY entities are added for nodes as the state is changing (which happens soon after startup) and not (only) like I would expect via the setup_platform() method.  As a result, I see two behaviors that I think are an issue/problem:

nodes that should be filtered are not (the below node has a name that contains the hidden_string)

16-09-21 01:04:43 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=switch.gate_binary_sensor_hide, new_state=<state switch.gate_binary_sensor_hide=on; friendly_name=Gate Binary Sensor {HIDE} @ 2016-09-21T01:04:43.979757-05:00>, old_state=None>

nodes are added to the wrong domain since the setup_platform() logic was not followed.  In the above example you see an item that the ISY says is a binary sensor added to the switch domain.

These two are the ones not showing up?
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living
Room Lamp ['51']16-09-20 21:19:44 homeassistant.components.isy994: ISY
NODE: Media Room Lamp ['51']
On Tue, Sep 20, 2016 at 11:04 PM, Bryce Edwards notifications@github.com
wrote:

OK, here's some details. I tweaked your code a bit as I didn't get any
debug output (the node names were not as I expected, so I added another log
line)
Code (starting line 96)
for (path, node) in ISY.nodes:
    _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
    if node.name == 'ZW002' or node.name == 'ZW003':
        _LOGGER.debug('FOUND: ' + str(node.name) + ' ' + str(node.uom))

    hidden = hidden_identifier in path or hidden_identifier in node.name

Log output:
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/ping
16-09-20 http://isy.local:80/rest/ping16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/config
16-09-20 http://isy.local:80/rest/config16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Configuration
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/nodes?members=false
16-09-20 http://isy.local:80/rest/nodes?members=false16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Nodes
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/programs?subfolders=true
16-09-20 http://isy.local:80/rest/programs?subfolders=true16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded/Updated Programs
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/1
16-09-20 http://isy.local:80/rest/vars/definitions/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/2
16-09-20 http://isy.local:80/rest/vars/definitions/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/1
16-09-20 http://isy.local:80/rest/vars/get/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/2
16-09-20 http://isy.local:80/rest/vars/get/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Variables
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Opener ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Binary Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Multilevel Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Pulse Meter {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Power Management {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Tamper Sensor ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Back Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Garage Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.bootstrap: Error during setup of component isy994
Traceback (most recent call last):
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/bootstrap.py", line 102, in _setup_component
result = component.setup(hass, config)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 181, in setup
_categorize_nodes(hidden_identifier, sensor_identifier)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 97, in _categorize_nodes
_LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
AttributeError: 'Group' object has no attribute 'uom'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248512526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZd8nvKy41cbdYfHD587wj9PdKkmyks5qsLrvgaJpZM4KBLUV
.

To answer your questions:

The default hidden string is {HIDE ME} - this should be the same as it
was before the changes. This can be changed via the hidden_string
configuration value).

That's designed behavior - if you want it to show as a binary sensor it
needs to have sensor string in the node name or the folder. The default
sensor identifier string is sensor (As of now I believe this is case
sensitive - you can change it by setting the config value sensor_string)

On Wed, Sep 21, 2016 at 7:01 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

These two are the ones not showing up?
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
On Tue, Sep 20, 2016 at 11:04 PM, Bryce Edwards notifications@github.com
wrote:

OK, here's some details. I tweaked your code a bit as I didn't get any
debug output (the node names were not as I expected, so I added another log
line)
Code (starting line 96)
for (path, node) in ISY.nodes:
    _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
    if node.name == 'ZW002' or node.name == 'ZW003':
        _LOGGER.debug('FOUND: ' + str(node.name) + ' ' + str(node.uom))

    hidden = hidden_identifier in path or hidden_identifier in node.name

Log output:
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/ping
16-09-20 http://isy.local:80/rest/ping16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/config
16-09-20 http://isy.local:80/rest/config16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Configuration
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/nodes?members=false
16-09-20 http://isy.local:80/rest/nodes?members=false16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Nodes
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/programs?subfolders=true
16-09-20 http://isy.local:80/rest/programs?subfolders=true16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded/Updated Programs
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/1
16-09-20 http://isy.local:80/rest/vars/definitions/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/2
16-09-20 http://isy.local:80/rest/vars/definitions/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/1
16-09-20 http://isy.local:80/rest/vars/get/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/2
16-09-20 http://isy.local:80/rest/vars/get/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Variables
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Opener ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Binary Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Multilevel Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Pulse Meter {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Power Management {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Tamper Sensor ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Back Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Garage Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.bootstrap: Error during setup of component isy994
Traceback (most recent call last):
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/bootstrap.py", line 102, in _setup_component
result = component.setup(hass, config)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 181, in setup
_categorize_nodes(hidden_identifier, sensor_identifier)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 97, in _categorize_nodes
_LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
AttributeError: 'Group' object has no attribute 'uom'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248512526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZd8nvKy41cbdYfHD587wj9PdKkmyks5qsLrvgaJpZM4KBLUV
.

Nodes are categorized by their units of measure or available states. It
will only categorize a node as a sensor (binary_sensor or sensor) if it has
the sensor string identifier; these are then further categorized into
binary_sensor (if the sensor state is on/off, true/false) or sesnor (all
other units of measure/states).
On Wed, Sep 21, 2016 at 7:20 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

To answer your questions:

The default hidden string is {HIDE ME} - this should be the same as
it was before the changes. This can be changed via the hidden_string
configuration value).

That's designed behavior - if you want it to show as a binary sensor it
needs to have sensor string in the node name or the folder. The default
sensor identifier string is sensor (As of now I believe this is case
sensitive - you can change it by setting the config value sensor_string)

On Wed, Sep 21, 2016 at 7:01 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

These two are the ones not showing up?
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
On Tue, Sep 20, 2016 at 11:04 PM, Bryce Edwards <notifications@github.com

wrote:

OK, here's some details. I tweaked your code a bit as I didn't get any
debug output (the node names were not as I expected, so I added another log
line)
Code (starting line 96)
for (path, node) in ISY.nodes:
    _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
    if node.name == 'ZW002' or node.name == 'ZW003':
        _LOGGER.debug('FOUND: ' + str(node.name) + ' ' + str(node.uom))

    hidden = hidden_identifier in path or hidden_identifier in node.name

Log output:
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/ping
16-09-20 http://isy.local:80/rest/ping16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/config
16-09-20 http://isy.local:80/rest/config16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Configuration
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/nodes?members=false
16-09-20 http://isy.local:80/rest/nodes?members=false16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Nodes
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/programs?subfolders=true
16-09-20 http://isy.local:80/rest/programs?subfolders=true16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded/Updated Programs
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/1
16-09-20 http://isy.local:80/rest/vars/definitions/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/2
16-09-20 http://isy.local:80/rest/vars/definitions/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/1
16-09-20 http://isy.local:80/rest/vars/get/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/2
16-09-20 http://isy.local:80/rest/vars/get/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Variables
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Opener ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Binary Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Multilevel Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Pulse Meter {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Power Management {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Tamper Sensor ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Back Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Garage Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.bootstrap: Error during setup of component isy994
Traceback (most recent call last):
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/bootstrap.py", line 102, in _setup_component
result = component.setup(hass, config)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 181, in setup
_categorize_nodes(hidden_identifier, sensor_identifier)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 97, in _categorize_nodes
_LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
AttributeError: 'Group' object has no attribute 'uom'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248512526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZd8nvKy41cbdYfHD587wj9PdKkmyks5qsLrvgaJpZM4KBLUV
.

Thanks for this line if node.dimmable or node.uom == '51' or '51' in node.uom: I'll add it to the project here shortly.
On Wed, Sep 21, 2016 at 7:23 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

Nodes are categorized by their units of measure or available states. It
will only categorize a node as a sensor (binary_sensor or sensor) if it has
the sensor string identifier; these are then further categorized into
binary_sensor (if the sensor state is on/off, true/false) or sesnor (all
other units of measure/states).
On Wed, Sep 21, 2016 at 7:20 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

To answer your questions:

The default hidden string is {HIDE ME} - this should be the same as
it was before the changes. This can be changed via the hidden_string
configuration value).

That's designed behavior - if you want it to show as a binary sensor
it needs to have sensor string in the node name or the folder. The default
sensor identifier string is sensor (As of now I believe this is case
sensitive - you can change it by setting the config value sensor_string)

On Wed, Sep 21, 2016 at 7:01 AM, Teagan Glenn teagan.m.glenn@gmail.com
wrote:

These two are the ones not showing up?
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
On Tue, Sep 20, 2016 at 11:04 PM, Bryce Edwards <
notifications@github.com> wrote:

OK, here's some details. I tweaked your code a bit as I didn't get any
debug output (the node names were not as I expected, so I added another log
line)
Code (starting line 96)
for (path, node) in ISY.nodes:
    _LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
    if node.name == 'ZW002' or node.name == 'ZW003':
        _LOGGER.debug('FOUND: ' + str(node.name) + ' ' + str(node.uom))

    hidden = hidden_identifier in path or hidden_identifier in node.name

Log output:
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/ping
16-09-20 http://isy.local:80/rest/ping16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/config
16-09-20 http://isy.local:80/rest/config16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Configuration
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/nodes?members=false
16-09-20 http://isy.local:80/rest/nodes?members=false16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Nodes
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/programs?subfolders=true
16-09-20 http://isy.local:80/rest/programs?subfolders=true16-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded/Updated Programs
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/1
16-09-20 http://isy.local:80/rest/vars/definitions/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/definitions/2
16-09-20 http://isy.local:80/rest/vars/definitions/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/1
16-09-20 http://isy.local:80/rest/vars/get/116-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Request: http://isy.local:80/rest/vars/get/2
16-09-20 http://isy.local:80/rest/vars/get/216-09-20 21:19:44 homeassistant.components.isy994: ISY Response Recieved
16-09-20 21:19:44 homeassistant.components.isy994: ISY Loaded Variables
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Living Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Media Room Lamp ['51']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Opener ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Binary Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Multilevel Sensor {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Pulse Meter {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Gate Power Management {HIDE} ['on', 'off']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Front Door Tamper Sensor ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Back Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.components.isy994: ISY NODE: Garage Door Lock ['unlocked', 'locked']
16-09-20 21:19:44 homeassistant.bootstrap: Error during setup of component isy994
Traceback (most recent call last):
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/bootstrap.py", line 102, in _setup_component
result = component.setup(hass, config)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 181, in setup
_categorize_nodes(hidden_identifier, sensor_identifier)
File "/usr/local/home-assistant-dev/lib/python3.4/site-packages/homeassistant/components/isy994.py", line 97, in _categorize_nodes
_LOGGER.debug('ISY NODE: ' + str(node.name) + ' ' + str(node.uom))
AttributeError: 'Group' object has no attribute 'uom'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3457#issuecomment-248512526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2fZd8nvKy41cbdYfHD587wj9PdKkmyks5qsLrvgaJpZM4KBLUV
.

authors: Teagan42 balloob hoopty


text:
Fix flaky group notify test

Fix the flaky group notify test, once and for all.

:tada:


text:
Fix broken docker build

python3 branch
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Thanks 🐬

authors: balloob turbokongen


text:
Add support for custom stream queries for media_extractor

Description:
This PR adds support for custom stream queries per device and media type to media_extractor.
Example entry for configuration.yaml (if applicable):
media_extractor:
  default_query: worst
  customize:
    media_player.kd55x8507c:
      video: bestvideo
      music: bestaudio
      playlist: worstaudio[ext=mp4]

Default query if no settings provided is  best.
User can override default value or set custom query per device and media type.
Examples:

bestvideo - best video only stream
best - best video + audio stream
bestaudio[ext=m4a] - best audio stream with m4a extension
worst - worst video + audio stream
bestaudio[ext=m4a]/bestaudio[ext=ogg]/bestaudio - best m4a audio, otherwise best ogg audio and only then any audio

More about format queries https://github.com/rg3/youtube-dl/blob/master/README.md#format-selection
BUT:
My settings:
media_extractor:
  default_query: best
  customize:
    media_player.kd55x8507c:
      video/videoonly: bestvideo
      video/best: best
      audio/best: bestaudio[ext=m4a]

My chromecast device (Sony Bravia with Android TV) does not support these media content types https://home-assistant.io/components/media_player/#service-media_playerplay_media
It supports media_content_type attributes like:

video/blablabla
audio/blablabla

My service call data is:
{"entity_id": "media_player.kd55x8507c", "media_content_id": "https://www.youtube.com/watch?v=VZMfhtKa-wo", "media_content_type": "audio/best"}

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[ ] New dependencies are only imported inside functions that use them ([example][ex-import]).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Could you add a config schema for this component please?

Still getting soco.exceptions.SoCoUPnPException: UPnP Error 714 received: Illegal MIME-Type for Sonos, sadly. Potentially more hackery required, but as this stands it looks good :+1:

Is it possible to send any stream to Sonos from HA using media_player.play_media service?

I've done it before with a stream of PC audio, so it is possible, just not easy.

Could you provide service data?

Same as your example.

But what was the value of "media_content_type" with working example?

Ah, I mean the stream was setup outside of hass.

Looks like sonos support only MP3, AAC and WMA for that kind of streaming. And unfortunately youtube does not support these formats.( https://sonos.custhelp.com/app/answers/detail/a_id/80/~/supported-audio-formats

Gotcha, it's a shame we can't add support for transcoding without serving the stream through hass.

Can you check your sonos devices with this url - https://soundcloud.com/bruttoband/brutto-11 and audio/mp3: bestaudio[ext=mp3]

Can anyone rerun this build as it failed because of ConnectionResetError

@minchik restarted the build for you.
{"entity_id": "media_player.sonos_bedroom", "media_content_id": "https://soundcloud.com/bruttoband/brutto-11", "media_content_type": "audio/mp3"} worked for me.

As expect it depends on whether the owner of the media contains supported streams for your device

Thanks! :crocodile:

@minchik can you update the docs for this please? Provide a link to https://github.com/rg3/youtube-dl#format-selection

ok

https://github.com/home-assistant/home-assistant.github.io/pull/3012

authors: lwis minchik


text:
Adds swedish as sv

Adds swedish. Adds minor improvements to readme(s).

Thanks @lellky!

Thanks @lellky!

No worries! Let me know if I can do more!

authors: lellky synesthesiam

repo: home-assistant/intents


text:
@homer0/prettier-plugin-jsdoc@6.0.5: shebang is removed with prettier@3.0.0

Steps to reproduce in a empty folder run:
npm install prettier@3.0.0

npm install @homer0/prettier-plugin-jsdoc@6.0.5

Create index.js with the following content:
#!/usr/bin/env node
console.log("hello world");

Running just prettier returns the correct result:
npx prettier index.js

#!/usr/bin/env node
console.log("hello world");

Running with @homer0/prettier-plugin-jsdoc removes the shebang:
npx prettier --plugin "@homer0/prettier-plugin-jsdoc" index.js

console.log("hello world");

Not sure if this is a bug in @homer0/prettier-plugin-jsdoc or in prettier.
It works when using prettier@2.8.8.

Tested also other plugins like @prettier/plugin-php@0.19.6 where this works correctly with both versions of prettier.

@campersau Hey 👋
I wasn't aware that Prettier 3 was out! I'll check this today, regardless which package cause the issue, it should be an easy fix.

@campersau 👋
It took more than I expected, but after adding support for V3, it seems like the shebang issue is gone. I added a test for it, and, just in case, here's a video:
https://github.com/homer0/packages/assets/6949310/11b4a3f8-c16d-4585-b608-d97eb98a412f
Have fun!


text:
cpu mode for android

Feature Description
Hello, considering that Raspberry 4 doesn't have gpu, do you develop a version for cpu mode on android operating system?
Current Behaviour/State
No response
Additional Context
No response

I believe the Task API can run on both CPU and GPU.
https://github.com/homuler/MediaPipeUnityPlugin/blob/bd417bfd463d2da9cae0d9f9f7d29dd9ef4fabe6/Packages/com.github.homuler.mediapipe/Runtime/Scripts/Tasks/Vision/FaceDetector/FaceDetectorOptions.cs#L33-L36
In the sample app, see
https://github.com/homuler/MediaPipeUnityPlugin/blob/bd417bfd463d2da9cae0d9f9f7d29dd9ef4fabe6/Assets/MediaPipeUnity/Samples/Scenes/Tasks/Face Detection/FaceDetectionConfig.cs#L19-L24

I need it to run on android OS on cpu, in the description also written for android on gpu.
am i wrong and it works on android with cpu?

The sample app is written using a legacy API, and to run it on Android, you need to enable the GPU (although it is probably possible to build it for the CPU, we do not currently support this).
On the other hand, I believe the Task API can run on both GPU and CPU. There are also sample scenes using the Task API.

repo: homuler/MediaPipeUnityPlugin


text:
readable dash.all.min.js

Hi,
I was wondering if you could share a readable version of //pensieve/video_server/dash.all.min.js so I could make some modifications to the Pensieve player.
Thanks!

After you install the grunt dependencies (https://github.com/hongzimao/pensieve/blob/master/dash_client/README.md), you can edit the dash.js source code. For example, we updated the ABR algorithm used by the dash player by modifying this file: https://github.com/hongzimao/pensieve/blob/master/dash.js/src/streaming/controllers/AbrController.js.
After you make your edits to the source code, you will have to recompile the code to generate a new dash.all.min.js file. To do this, run ./compile.sh in the pensieve/dash.js directory.

Thanks! I will try this out.

I installed the grunt dependencies as documented in the README, and but when I run ./compile.sh in //pensieve/dash.js, I get the warning "Cannot find module 'browserify-derequire'", and the rest of the pipeline fails.
I tried installing grunt-browserify and browserify-derequire through npm, but I'm getting the same error. It seems like the browserify-derequire package has out-of-date dependencies (https://github.com/rse/browserify-derequire).
I'd appreciate it if you could give me some pointers to resolve this issue. Thanks!

We didn't hit this package installation before. Did you use python setup.py?

Yes, I ran setup.py in the //pensieve root directory. It doesn't seem to install any grunt packages, but I did install all dependencies in the dash.js source code README (https://github.com/hongzimao/pensieve/blob/master/dash_client/README.md), linked above.

I ran into a similar set of issues. I tried a few different installations in the sense that I installed many packages individually as I saw errors. I installed grunt separately, grunt-cli separately, jsdoc separately (it seems like the jsdoc-plugin is no longer the right package for higher versions of grunt), the jasmine-istanbul package, etc. I'm not entirely sure what solved it because I struggled to replicate this myself a second time, but I eventually got it to compile. Also, if it helps, the compiled dash.all.min.js will be found in dash.js/build/temp/. Sorry for not being more specific.

Thanks a lot Vibhaa. Hope this helps @arjunvb!

Thanks @vibhaa, @hongzimao. I also had to manually separately install grunt, grunt-cli, jasmine-istanbul, and several other packages. I also had to modify settings in .jshintc and .jscsrc so the existing source code met passed lint and code style checks.
I've been stuck at the browserify stage (https://github.com/hongzimao/pensieve/blob/master/dash.js/Gruntfile.js#L244). It's saying the 'browserify-derequire' module is not found even though I've installed with npm. I'm seeing a similar issue for the 'babelify' package as well. Did you ever have an issue with either of these two packages?
Thanks for your help.

@hongzimao, I got it to compile successfully! I'm not too sure what the problem was, but, to resolve the 'browserify-derequire' module issue, I went back and re-installed the dependencies listed in the README. It's possible something failed earlier that I didn't catch, but installing 'browserify-derequire' didn't help. To get the rest of it to work, I had to do several other package installs, as @vibhaa noted above.
Here's a summary of the issues I ran into when compiling dash.js from source:

Lint and code style checks failed due to warnings (e.g. variable defined but not used). I modified settings in .jshintc and .jscsrc to suppress these warnings so they didn't interfere with the rest of the compilation.
For any module that's not found, I ran npm install <module name> and re-started the compile script.
The uglify task failed several times due to memory issues. To fix this, I increased the allocated memory, by updating line 2 in compile.sh as follows: grunt --config Gruntfile.js --force --max-old-space-size=16384

Thanks!

authors: arjunvb hongzimao ravinet vibhaa

repo: hongzimao/pensieve


text:
镜像重启失效

在docker里面重启images，就失效了

可以可以访问web，但是不能用，超时

status

这个manager.sh 重启也报错：
ERROR:systemctl:the ExecStartPre control process exited with error code
docker安装如下：

重启 docker 服务试试

b不知道为啥 还是不行

说实话，我网上都查不到这个报错，我也没办法确认是什么问题了，建议源码安装使用看看吧

好吧 我删了重装的images 先用着 不知道重启后报不报错 感谢大佬

repo: honmashironeko/ARL-docker


text:
Add component evaluation for inactive sections

Now filename component updates on inactive_status .
closes #157

Note: this relies on a week old nightly https://github.com/neovim/neovim/pull/14558
So this can probably be delayed for adoption.
@hoob3rt you can directly push the changes you need to my branch and merge these prs If you like the feature.

Merged in https://github.com/shadmansaleh/lualine.nvim

Part of #311


text:
🛑 FWB is down

In 16e8d9d, FWB ($FWB_SITE) was down:

HTTP code: 403
Response time: 374 ms

Resolved: FWB is back up in 0dde06b after 49 minutes.

repo: hoopybe/uptime


text:
🛑 FWB is down

In 29d8d4c, FWB ($FWB_SITE) was down:

HTTP code: 403
Response time: 405 ms

Resolved: FWB is back up in 1091bfa after 13 minutes.


text:
🛑 FWB is down

In bf3da3e, FWB ($FWB_SITE) was down:

HTTP code: 403
Response time: 488 ms

Resolved: FWB is back up in 9b3b7e4 after 1 hour, 51 minutes.


text:
初始项目执行 pnpm run lint:stylelint 报错

$ pnpm run lint:stylelint

> fantastic-admin@0.1.0 lint:stylelint D:\Project\_Display\civicint_colud_client\fantastic-admin
> stylelint src/**/*.{css,scss,vue} --fix

src/assets/styles/resources/themes.scss
 39:25  ✖  Unexpected unknown function "darken"  function-no-unknown
 45:31  ✖  Unexpected unknown function "darken"  function-no-unknown

 ELIFECYCLE  Command failed with exit code 2.

已修复，.stylelintrc 里增加了一条规则
        "function-no-unknown": [
            true,
            {
                "ignoreFunctions": [
                    "lighten",
                    "darken"
                ]
            }
        ],

repo: hooray/fantastic-admin


text:
Update Grafana to 7.0

This PR contains changes to use v7 of Grafana.

Ubuntu version left untouched (metrics did not reach the statsd or graphite when upgrading to ubuntu 18.04)
Resolves #100, resolves #101

@hopsoft any plans on getting this reviewed?

ok, I see that there is https://github.com/graphite-project/docker-graphite-statsd

ok, I see that there is https://github.com/graphite-project/docker-graphite-statsd

But on that repo looks like there is not Grafana integrated :?

authors: birdmod fguillen vcvitaly

repo: hopsoft/docker-graphite-statsd

license: mit

license_source: bigquery


text:
[SAC-45] Record the Spark ML model and pipeline directory in the …

What changes were proposed in this pull request?
This PR record the directory for Atlas record of Spark ML model and pipeline.
How was this patch tested?
Pass Travis CI, and add the records later.

send other pr later

repo: hortonworks-spark/spark-atlas-connector


text:
🛑 Console is down

In 8073927, Console (https://console.planetary-quantum.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Console is back up in 5d06fcf after 5 minutes.


text:
update: adds npm badge, annotation for code block

Overview
This PR,

adds npm package badge for @hotjar/browser.
adds javascript label for code-blocks in README

This is mostly a formatting update in the README.
Changes Introduced

Formatting changes  in README.md

Thanks!

cc @arrwhidev

Thank you for the PR :)

repo: hotjar/hotjar-js


text:
Implement Quick Access to OMS on Home Page for Logged-in Users

What is the motivation for adding/enhancing this feature?
Currently, accessing the Order Management System (OMS) requires users to navigate through multiple pages, which can be time-consuming and inefficient.
Implement a dedicated section or button on the Home page that provides seamless access to the OMS for users who are already logged in.
What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information

would you please assign this issue to me

Sure @Saiyam-Kumawat go ahead

Mockup

repo: hotwax/launchpad


text:
建议添加通过共享链接添加文件的功能

不知道是否可能，但是如果能把别人发布的共享链接所指向的文件（或者文件夹）添加到网盘中bypy的文件夹下面，再下载下来就好了。

感谢建议。
应该不会加这个实现了：

貌似pcs没开放这个api接口
项目已经放到维护模式，除了修严重bug基本不会增加新功能了
个人觉得这个需求不是特别有用，添加别人网盘链接只是一次性操作，在网页上很容易就完成了，命令行优势不大。

authors: houtianze oscar-c

repo: houtianze/bypy


text:
Error 31066 上传大文件失败

最近出现的，上传任何一个大文件必现失败（大于1G左右），在最后上传100%结束的时候失败
bypy v1.6.7
bypy upload xxx.tar.gz
[===_________________] 17% (380.0MB/2.1GB) ETA: 1h5m (474kB/s, 13m40s gone)  [15:48:47] Waiting 10 seconds before retrying...
 [15:48:57] Request Try #2 / 5
 [15:53:57] Waiting 20 seconds before retrying...
 [15:54:17] Request Try #3 / 5
 [15:54:58] Waiting 30 seconds before retrying...
 [15:55:28] Request Try #4 / 5
 [15:56:09] Waiting 40 seconds before retrying...
 [15:56:49] Request Try #5 / 5
 [15:57:30] Maximum number (5) of tries failed.
 [15:57:30] Slice MD5 mismatch, waiting 10 seconds before retrying...
 [15:57:40] Retrying #2 / 5
[====================] 100% (2.1GB/2.1GB) ETA:  (400kB/s, 1h33m gone) Combining the following MD5 slices:
21e65d36f295e651dc2e05d14e9e92dd
3f96d0ee38fc021c2acfe8715bc0df83
d46d185a247798ac55d88196d010fe19
7f537c31af269b13113b3d451c36e515
44a0da32e061bdd44469f85374211855
c222cf7a62672847b744c042ec7e04b5
155eb335074247325c762ba881ccfe28
f5e9e83693d2299c367b979b1afd63a4
070ba7181458528e5bf8aca388493f54
746452c007ab7d3829cb2dd76b724cad
31612fc98949557c5a2a33b51393d48c
d727ef9736cf1c5de957f0efce1f2df6
8b39e3befa7326db0d8c1fb54ee1db2e
4d405d38835ebb3a75970f27e63f7276
a129542acc7308839d6113ec8dc47294
4203f03e615d8ba6a44a36604387c4eb
f4003f5ba8ab336c9b044cad05419069
1b128bf4682f9d73299b3afb0d83159a
277878f09d7d63e2167002e10a1b9bd3
5f008435bb5a71330a405cf92e5a28f8
5a52a3c9b624ad91227e818a5882594d
d6d6826ec8a67957444f138dd275f502
451fe0efa0f4132c6ae85e8d9dee31d9
5d204527bf9181decaa492d62ee40848
d813a0c5edddbec53b43d4253808fe6f
571a43b50f754cb69045f17c28d1685b
5b1bbfde9d95cdb9cff02a7db2bcb5f5
cd7c404957c9fd12a4a6a16f02f31e54
4c406909f37cc19293175346317721f9
380b13bacefdaef6ff5b915704f486c7
5eee90acdcc6ab355b3aabf4b1804318
b4b11243791f6f34002d7d1d155caf5d
24715e1205c2365e0b35d5dfd1a04b99
7ddb1eeeacf1a8ae07fc10a559b09764
b03b67a21920a6b9c7fe41d3a1eb88c9
937ddb51450eaebccd7a75c98fef023a
bf84fb70a1ce35cf65debf5fdfb05838
66b4d0bdb458b2e9bb1c87d9b4b183ab
79575b31637b9e8701b1f2e4f024e93b
1cccddcfc63433b9c3debc24ca4f1cec
5ccdd5b2a05c83a512f45cb01aa689aa
9d10c7739d0a2755db0d502357ca02d6
abb36afea5798cd92dd39a84549ccc94
2db4554bc1439dd773d35eb01dc7ffe4
65d7c00379794188921e274ad5426627
5a3fd5454b717ec2123f1abde53545e3
dcbce690181fb1e0571f816940893d2d
a62ffd3dbf805350ea8fc30f33c47823
fd8426454d5e30ffbcfe1085c2fd63f0
e5aeeeaddbfa4e6335e78edbe30a84cb
be5c2403a43057c7b8d4ca901ed98148
22980d279ecc13553e7804bf0e204cf4
23239e372d6a1464b68921ad0ca098d7
86024c7d88d98357036acd8d4ad9718d
498ba92e9be4c7b15d06f7dda28108c2
674664a337ac7c4198a31d8c727a921d
cce4b3a5dc645bfd5ffe882689a6f8c9
6c97554d627a7e690fcfa552157ac19b
6ce8095fd51fb97dcc18a784840e6d46
d7636ad6cd21d0548b8b5182ce8484a0
1f691f23a9a8e67bd9b410beeedbae42
9f885ea169efd67896ab235e24a2c4b5
5de6110834a42b198569f654b699cd67
9a43c2f4a5d3e6a7ee5bc456271abf39
e03e54702dbb98c11b690e31f2f5a1f5
c2686919f62f054177634b41b5a5c8e2
0b4c30458a380ff6a56df9000f5047e5
bc7114db2cf3c9a5eea793ba58f5ddb3
fafc45ec527fcdfe91c221fe6f505106
7a6c357ce55e28e0020ebe861bd764d5
b715ac65ae82d182db50b2d1e73dc836
b3ce55e3164def64d01a215ffd684890
656bf7cbb93fa6433bd1b9dd850556d7
1eab278b99cc4292484207f8427788f2
dc6cf4c535cd23e6de610f8f24f4564f
c7641654059775666634239366d607f7
e7f0a76d0d63b9672dbbf44213e8f773
0a03a422a9e63a61af011d70add6f9e3
95b6860321fbbfa611c1761cbfe46127
7c1f260c9c16dae616e4a6b39b5b8665
9dc5684252bbe0fc437a4776373bd511
ed32a243e00e59119db56a9a3893caaf
f9e58d0daa62899ebed9e9e708a4582f
509c936f9771cc06bb49086fc5376930
fe38d02387110a6f0fe5fe365f8a4e77
75136ea3cf85373fb8519c64ffb2d4a6
522cde27d4a46824969c9fd5ecb37bae
edc73ac5bbd54fe969c1eee7fc5c70e2
f40793a30b54d0c2ecaf2244363817e7
21eaa12f231254b68e4aec38ba69a55d
36b6b2c953a8be679ce907f716fc053e
ad986aa6823766177b6a5daf947c5330
6f91689bb3afc84ee0dbe2ac8456513c
0fcddb9ffefdc1556bb0e9843728481a
b8f3316f4a3be4b909b6e63742b9b6b1
f3a391fe68761ae5bba6868ab458566d
178685d37a71e33c038a03c9b45e9ae0
246970abeed54b1b315d6890a06b5e02
1aae97f648c2e0d5223f76590a292ef2
d7d17c30b119fe498afc081c57bea8d7
2f1a4f77d6b0aa7f9e88dfe4d163acda
b77797d1f7d41e435d35edc9997c6caa
0bb35fe8ce047dc0dfe092691a49195c
938a2e6e63c52a0a28906bb583adbd68
501d6867c2078f4c05243d210b552c96
ee8457bbeaeaa4dbbb013777f59601e5
5d7b73be34931344a26568b7aebe077d
3230c56e6961d3a8f8de90da073c182d
546733fe77ff48081d15699f1194d49c
a56c6fd501db7ad0d768fb260fe6358d
 [17:03:17] ----------------------------------------------------------------
Error 31066

我这才35M，上传也出错，肯定和大文件无关。
ming@raspberrypi:~/Videos$ ls -al
total 34904
drwx------  2 ming ming     4096 Mar 30 23:00 .
drwx------ 26 ming ming     4096 Mar 30 23:02 ..
-rwxr-xr-x  1 ming ming 35731768 Mar 30 22:37 News.mp4
ming@raspberrypi:~/Videos$ bypy upload News.mp4
Combining the following MD5 slices:
f91c11cb0a1ded58bea7d5f8176d971f
649bd3961f04806f5f97567db00feee6
 [23:03:30] ----------------------------------------------------------------
Error 31066

参考编号#522的临时性方法绕过去吧，但是请作者尽快找到问题，做到代码里去。

@ModernCrusade 确实可以，谢谢了。

加 ”-s 1T“ 参数即可

@bg4uvr -s1T 测试过，无法上传超过2G的文件，一上来就失败并重试直到重试用完

@bg4uvr -s1T 测试过，无法上传超过2G的文件，一上来就失败并重试直到重试用完

那我试试 -s 2G吧，哈哈

@bg4uvr -s1T 测试过，无法上传超过2G的文件，一上来就失败并重试直到重试用完

那我试试 -s 2G吧，哈哈

唉，经测试不行，出现其实错误。现在这个完全用起来了。

authors: ModernCrusade bg4uvr milabobo


text:
需要更多的广告样本

为了提升模型的识别准确率，我希望大家能尽力贡献一些广告样本，请看样本文件：.files/datasets/ads.csv，我设定格式如下：

title
url

广告文章标题
广告文章连接

来个实例：

一般广告会重复在多个公众号投放，填写的时候麻烦查一下是否存在此条记录，真的真的希望大家能一起合力贡献，亲，来个PR贡献你的力量吧！

基于wechat-feeds项目，我对将近5500个公众号进行最近更新的文章进行爬取，差不多获取10万条样本数据。
接下来要做的就是从其中挑选广告文作为反面样本。


text:
问题

问您个问题，就是minio 是如何改变单个文件的权限的，  ossClient.getS3Client().setObjectAcl(ossProperties.getBucketName(), key, CannedAccessControlList.Private); 这样改变权限接口会报错。
错误信息
A header you provided implies functionality that is not implemented (Service: Amazon S3; Status Code: 501; Error Code: NotImplemented; Request ID: 1718A7B48A0094A0; S3 Extended Request ID: 3df21bb4-f73d-43a4-8e88-a3fa012464a4)
bucket策略用的是csdn上您写的那个，我看minio sdk 也没有改变单个文件访问权限的 api 接口啊 ，您知道吗  谢谢

打扰了，用您这个还是实现不了对应的权限修正，我用了另一种方式。修正相对路径上的访问权限（修改策略）来控制文件的显隐，一个路径下就一个文件，不知道我这样的处理方式是否有问题。代码如下：
` BucketPolicy bucketPolicy = ossClient.getS3Client().getBucketPolicy(ossProperties.getBucketName());
// {"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"AWS":[""]},"Action":["s3:GetBucketLocation"],"Resource":["arn:aws:s3:::bucket"]},{"Effect":"Allow","Principal":{"AWS":[""]},"Action":["s3:ListBucket"],"Resource":["arn:aws:s3:::bucket"],"Condition":{"StringEquals":{"s3:prefix":["22/1","22/2"]}}},{"Effect":"Allow","Principal":{"AWS":[""]},"Action":["s3:GetObject"],"Resource":["arn:aws:s3:::bucket/22/1","arn:aws:s3:::bucket/22/2*"]}]}
JSONObject jsonObject = JSON.parseObject(bucketPolicy.getPolicyText());
if (jsonObject == null){
log.error("上线发生错误【{}】",key);
return;
}
JSONArray statement = jsonObject.getJSONArray("Statement");
statement.forEach( e -> {
if (e.toString().contains("s3:prefix")) {
JSONObject sub = JSON.parseObject(e);
JSONObject condition = sub.getJSONObject("Condition");
JSONObject stringEquals = condition.getJSONObject("StringEquals");
JSONArray jsonArray = stringEquals.getJSONArray("s3:prefix");
String substring = key.substring(0, key.lastIndexOf("/"));
if (jsonArray.contains(substring)){
return;
}
jsonArray.add(substring);
}
        if (e.toString().contains("s3:GetObject")) {
            JSONObject sub = JSON.parseObject(e);
            JSONArray resource = sub.getJSONArray("Resource");
            String substring = key.substring(0, key.lastIndexOf("/"));
            // "arn:aws:s3:::bucket/22/1*",
            String word = "arn:aws:s3:::" + ossProperties.getBucketName() +"/"+substring + "*";
            if (resource.contains(word)){
                return;
            }
            resource.add(word);
        }
    });
    // ossClient.getS3Client().setObjectAcl(ossProperties.getBucketName(), key, CannedAccessControlList.PublicRead);
    ossClient.bucketPolicy(ossProperties.getBucketName(), jsonObject.toJSONString());`

第一个回复的意思是 在minio没有实现对于文件对象的权限控制, 并没有说能实现权限控制

authors: hp-coder wahowaho

repo: hp-coder/common-starters


text:
Add additional categories

Is it possible to start training with additional categories such as: heading2, heading3, ..., image description?

If you have sufficient labeled data for these categories, then you can finetune this model for your need.


text:
connection failure

🐛 Describe the bug
I found a runtime error while running the code:
The client socket has failed to connect to any network address of (hcp-bb-03, 52873). The client socket has failed to connect to hcp-bb-03:52873 (errno: 110 - Connection timed out)
using command line :colossalai run --nproc_per_node 4 --master_port 29505 train.py
Environment

Can you try this
colossalai run --nproc_per_node 4 --master_port 29505 --master_addr 127.0.0.1 train.py

Thx for your reply. But I found the problem still unsolved.
However, I found the following command could help:
python3.8 -m torch.distributed.launch --nproc_per_node 4 --master_addr localhost --master_port 29500 train.py
The network starts training and gets target accurancy.
The question is, what is the difference between the two commands?

authors: FrankLeeeee lhj-git

repo: hpcaitech/ColossalAI-Examples


text:
ZeRO compatibility with gradient accumulation

🐛 Describe the bug
ZeRO cannot work with gradient accumulation now due to multiple reduction of gradients.
Environment
No response

@ver217 I suppose we have fixed it now.

Yes, it's fixed

authors: FrankLeeeee feifeibear ver217

repo: hpcaitech/ColossalAI