ValidationError: gp3 is invalid

I have issues
GP3 is unsupported in launch configuration
I'm submitting a...

[ x] bug report
[ ] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
The cluster can't be created with gp3 launch configuration
If this is a bug, how to reproduce? Please include a code sample if relevant.
module "eks" {
  source          = "terraform-aws-modules/eks/aws"
  cluster_name    = var.stage
  cluster_version = "1.18"
  subnets         = module.vpc.private_subnets
  vpc_id          = module.vpc.vpc_id

  cluster_endpoint_private_access = true
  cluster_endpoint_public_access  = true

  worker_additional_security_group_ids  = [aws_security_group.bastion-sg.id]
  worker_ami_name_filter                = "amazon-eks-node-1.18-v20201211"
  manage_worker_iam_resources           = true
  enable_irsa                           = true

  map_roles = [
    {
      rolearn = module.eks_devops_user-role.role-arn
      username = "devops"
      groups = ["system:masters"]
    },
  ]

  cluster_encryption_config = [
    {
      provider_key_arn = aws_kms_key.eks_secrets.arn
      resources        = ["secrets"]
    }
  ]

  worker_groups = [
    {
      name                  = "spot-1"
      spot_price            = "0.50"
      instance_type         = "m4.large"
      asg_desired_capacity  = 1
      asg_max_size          = 3
      asg_min_size          = 0
      pre_userdata          = "hostnamectl set-hostname $( cat /etc/hostname ).${var.region}.compute.internal"
      kubelet_extra_args    = "--node-labels=node.kubernetes.io/lifecycle=spot,stage=${var.stage}"
      enable_monitoring     = false
      public_ip             = false
      suspended_processes   = ["AZRebalance"]
      tags = [
        {
          "key"                 = "Stage"
          "value"               = var.stage
          "propagate_at_launch" = true
        },
        {
          "key"                 = "k8s.io/cluster-autoscaler/node-template/label/kubernetes.io/lifecycle"
          "value"               = "spot"
          "propagate_at_launch" = false
        },
        {
          "key"                 = "k8s.io/cluster-autoscaler/enabled"
          "value"               = "true"
          "propagate_at_launch" = false
        },
        {
          "key"                 = "k8s.io/cluster-autoscaler/${var.stage}"
          "propagate_at_launch" = "false"
          "value"               = "true"
        }
      ]
    }
  ]
  tags = {
    Stage = var.stage
  }
}

Environment details

EKS module version: 14.0.0
AWS module version: v3.26.0
Terraform version: v0.14.5

Any other relevant info
Error:
Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
        status code: 400, request id: 9d6826bb-a513-4647-9169-c1b49e2dbbd7

Change:
 ~ root_block_device {
          ~ volume_type           = "gp2" -> "gp3" # forces replacement
            # (4 unchanged attributes hidden)
        }

@ichasco-heytrade What region are you using? Since it's a new volume type it might be that it's not available yet.

@ichasco-heytrade What region are you using? Since it's a new volume type it might be that it's not available yet.

Hi @oscr
The region is eu-west-1
It suppose that every regions support it
https://aws.amazon.com/es/blogs/aws/new-amazon-ebs-gp3-volume-lets-you-provision-performance-separate-from-capacity-and-offers-20-lower-price/
Available Today
The gp3 volume type is available for all AWS Regions. You can access the AWS Management Console to launch your first gp3 volume.

Thanks!! :)

Hi @oscr
The region is eu-west-1
It suppose that every regions support it
https://aws.amazon.com/es/blogs/aws/new-amazon-ebs-gp3-volume-lets-you-provision-performance-separate-from-capacity-and-offers-20-lower-price/
Available Today
The gp3 volume type is available for all AWS Regions. You can access the AWS Management Console to launch your first gp3 volume.

Thanks!! :)

@ichasco-heytrade I just got the same error message in the same region. Even if you can create that volume type via the console.

@ichasco-heytrade I just got the same error message in the same region. Even if you can create that volume type via the console.

@ichasco-heytrade I have found the issue. It looks like the aws provider needs to be updated
https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#3250-january-22-2021

@ichasco-heytrade I have found the issue. It looks like the aws provider needs to be updated
https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#3250-january-22-2021

It sounds like we have to update the aws provider version https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#3250-january-22-2021.
Can you please change the required provider https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/versions.tf#L5 to 3.25.0 ?

It sounds like we have to update the aws provider version https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#3250-january-22-2021.
Can you please change the required provider https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/versions.tf#L5 to 3.25.0 ?

@barryib I'm testing it right now.

@barryib I'm testing it right now.

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

El vie, 29 ene 2021 a las 10:22, oscr<EMAIL_ADDRESS>escribió:

@barryib https://github.com/barryib I'm testing it right now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1205#issuecomment-769685659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASOOX5LIR756WWOUFX5TA7DS4J465ANCNFSM4WYPGLZA
.

--
https://heytrade.com/
Ismael Chasco Villarreal
SRE Engineer - Heytrade
<EMAIL_ADDRESS>heytrade.com | linkedin https://www.linkedin.com/in/ismaelchasco/

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

El vie, 29 ene 2021 a las 10:22, oscr<EMAIL_ADDRESS>escribió:

@barryib https://github.com/barryib I'm testing it right now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1205#issuecomment-769685659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASOOX5LIR756WWOUFX5TA7DS4J465ANCNFSM4WYPGLZA
.

--
https://heytrade.com/
Ismael Chasco Villarreal
SRE Engineer - Heytrade
<EMAIL_ADDRESS>heytrade.com | linkedin https://www.linkedin.com/in/ismaelchasco/

For the time being, setting the workers_group_defaults.root_volume_type to gp2 seems to work:
  workers_group_defaults = {
  	root_volume_type = "gp2"
  }

For the time being, setting the workers_group_defaults.root_volume_type to gp2 seems to work:
  workers_group_defaults = {
  	root_volume_type = "gp2"
  }

This might be an issue with aws launch configuration validation:
https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-launch-configuration.html
VolumeType -> (string)
The volume type, which can be standard for Magnetic, io1 for Provisioned IOPS SSD, gp2 for General Purpose SSD, st1 for Throughput Optimized HDD, or sc1 for Cold HDD. For more information, see Amazon EBS Volume Types in the Amazon EC2 User Guide for Linux Instances .

Valid Values: standard | io1 | gp2 | st1 | sc1

This might be an issue with aws launch configuration validation:
https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-launch-configuration.html
VolumeType -> (string)
The volume type, which can be standard for Magnetic, io1 for Provisioned IOPS SSD, gp2 for General Purpose SSD, st1 for Throughput Optimized HDD, or sc1 for Cold HDD. For more information, see Amazon EBS Volume Types in the Amazon EC2 User Guide for Linux Instances .

Valid Values: standard | io1 | gp2 | st1 | sc1

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

@ichasco-heytrade what are your results ?

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

@ichasco-heytrade what are your results ?

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

@ichasco-heytrade what are your results ?

I have tested with AWS provider 3.26.0 too and getting the same error:
Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
	status code: 400, request id: bc4139d6-d9ce-41fc-8998-1d902bdd3e9d

I have tested with 3.26.0 provider version.

Installing hashicorp/aws v3.26.0...
Installed hashicorp/aws v3.26.0 (signed by HashiCorp)

@ichasco-heytrade what are your results ?

I have tested with AWS provider 3.26.0 too and getting the same error:
Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
	status code: 400, request id: bc4139d6-d9ce-41fc-8998-1d902bdd3e9d

It sounds like the aws api doesn't support gp3 for launch configuration https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_Ebs.html.
Does anyone know if this will change in a near future ?
So for now, launch configuration users must set they root_device_type to gp2 as @GerardoGR suggested. We can update the FAQ with this.

It sounds like the aws api doesn't support gp3 for launch configuration https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_Ebs.html.
Does anyone know if this will change in a near future ?
So for now, launch configuration users must set they root_device_type to gp2 as @GerardoGR suggested. We can update the FAQ with this.

gp3 isn't in launch configs yet. If you switch to launch templates gp3 should work

gp3 isn't in launch configs yet. If you switch to launch templates gp3 should work

gp3 isn't in launch configs yet. If you switch to launch templates gp3 should work. The default for launch configs for this module should be reverted back to gp2 though

@mzupan there is no default config for LC only. So if we rollback, we will rollback for both LC and LT. FWIW, we plan to drop launch configuration soon to let peoples move to launch template.

gp3 isn't in launch configs yet. If you switch to launch templates gp3 should work. The default for launch configs for this module should be reverted back to gp2 though

@mzupan there is no default config for LC only. So if we rollback, we will rollback for both LC and LT. FWIW, we plan to drop launch configuration soon to let peoples move to launch template.

This change breaks launching clusters with the default config shown in the basic example. If launch config is no longer supported, then it should be removed from all docs. Having a default value that breaks the default use of the module seems like a recipe for frustrated users.

This change breaks launching clusters with the default config shown in the basic example. If launch config is no longer supported, then it should be removed from all docs. Having a default value that breaks the default use of the module seems like a recipe for frustrated users.

Just opened this https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1208.

Just opened this https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1208.

For the time being, setting the workers_group_defaults.root_volume_type to gp2 seems to work:
  workers_group_defaults = {
  	root_volume_type = "gp2"
  }

Where do you place this code?

For the time being, setting the workers_group_defaults.root_volume_type to gp2 seems to work:
  workers_group_defaults = {
  	root_volume_type = "gp2"
  }

Where do you place this code?

Hi @sharjeelsayed, you have to place it in the module:
module "eks" {
  source          = "terraform-aws-modules/eks/aws"
...

  workers_group_defaults = {
  	root_volume_type = "gp2"
  }
...
}

Hi @sharjeelsayed, you have to place it in the module:
module "eks" {
  source          = "terraform-aws-modules/eks/aws"
...

  workers_group_defaults = {
  	root_volume_type = "gp2"
  }
...
}

Hi @sharjeelsayed, you have to place it in the module:
module "eks" {
  source          = "terraform-aws-modules/eks/aws"
...

  workers_group_defaults = {
  	root_volume_type = "gp2"
  }
...
}

What if I am using the eks_example_basic module?
module "eks_example_basic" {
  source  = "terraform-aws-modules/eks/aws//examples/basic"
  version = "14.0.0"
}

Hi @sharjeelsayed, you have to place it in the module:
module "eks" {
  source          = "terraform-aws-modules/eks/aws"
...

  workers_group_defaults = {
  	root_volume_type = "gp2"
  }
...
}

What if I am using the eks_example_basic module?
module "eks_example_basic" {
  source  = "terraform-aws-modules/eks/aws//examples/basic"
  version = "14.0.0"
}

Hey guys
I am still getting this one
`      ~ root_block_device {
delete_on_termination = true
~ encrypted             = false -> (known after apply)
iops                  = 0
volume_size           = 100
~ volume_type           = "gp2" -> "gp3" # forces replacement
}
}
...
Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
status code: 400, request id: 2cf54f3d-de26-47be-a989-e92af332ed17
`
Is there any solution? I am using
provider registry.terraform.io/hashicorp/aws v3.27.0

Hey guys
I am still getting this one
      ~ root_block_device {
            delete_on_termination = true
          ~ encrypted             = false -> (known after apply)
            iops                  = 0
            volume_size           = 100
          ~ volume_type           = "gp2" -> "gp3" # forces replacement
        }
    }
...

Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
        status code: 400, request id: 2cf54f3d-de26-47be-a989-e92af332ed17

Is there any solution? I am using
provider registry.terraform.io/hashicorp/aws v3.27.0

I would recommend you for Switching from aws_launch_configuration to aws_launch_template as it already have support for gp3 instances.

Also still getting this on aws provider 3.27.0 and us-east-1

Hey guys
I am still getting this one
      ~ root_block_device {
            delete_on_termination = true
          ~ encrypted             = false -> (known after apply)
            iops                  = 0
            volume_size           = 100
          ~ volume_type           = "gp2" -> "gp3" # forces replacement
        }
    }
...

Error: Error creating launch configuration: ValidationError: gp3 is invalid. Valid volume types are standard, io1, gp2, st1 and sc1.
        status code: 400, request id: 2cf54f3d-de26-47be-a989-e92af332ed17

Is there any solution? I am using
provider registry.terraform.io/hashicorp/aws v3.27.0

I would recommend you for Switching from aws_launch_configuration to aws_launch_template as it already have support for gp3 instances.

How to switch to 'aws_launch_template'

How to switch to 'aws_launch_template'

Someone correct me if I am wrong but in your module config you just change worker_groups = [...] to  worker_groups_launch_template = [...]

If you switch from worker_groups to worker_groups_launch_template - you might also want to preserve ASG (adjust for location of your module):
terraform state mv module.eks.aws_autoscaling_group.workers[0] module.eks.aws_autoscaling_group.workers_launch_template[0]

For "aws" (2.70.0), using launch templates, still, receive this error:
Error: aws_launch_template.module: expected block_device_mappings.0.ebs.0.volume_type to be one of [standard gp2 io1 sc1 st1], got gp3

I tried this in us-east-1 and it succeeded after making the change I suggested.

What's the fix? I had to change to gp2 for us-west-1

@vbagmar https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1205#issuecomment-780807344

Do we know when gp3 will be available for Launch configuration?

@vsenapathy is there a reason to not switch to launch templates? From what I understand, launch configurations are depreciated.

Oh i can move to Launch templates and test this.

@vsenapathy is there a reason to not switch to launch templates? From what I understand, launch configurations are depreciated.

I was able to get this to work with Launch template.

@innovate-invent ah, thanks. Missed that while skimming.

@vsenapathy is there a reason to not switch to launch templates? From what I understand, launch configurations are depreciated.

At least for me this is the main blocker for moving to launch templates: https://github.com/terraform-aws-modules/terraform-aws-autoscaling/issues/54

I've made an override to default values on my template, with no need to change the values from module.
 worker_groups = [     {      ...       root_volume_type   = "gp2"       ...     }   ]


How to use c/aquery to find the dependents of an anon_target

Given a situation where I have multiple named non-anon targets depending on the same anon_target, is there a way I can find what all those non-anon targets are? I think what I'm looking for are the rdeps of some covering target universe over those named targets on that anon_target. But whenever I try to use an anon target in a query, like something like this:
buck2 cquery "rdeps(//program:lint, anon//:lint_report_single@15ca92b70428afb8)"

buck2 says:
Error evaluating expression:
    rdeps(//program:lin<<omitted>>nt_report_single@15ca92b70428afb8)
    ^--------------------------------------------------------------^

Caused by:
    0: Invalid relative target pattern `anon//:lint_report_single@15ca92b70428afb8` is not allowed
    1: unknown cell alias: `anon`. In cell `root`, known aliases are: ...

I've needed this too in the past and haven't found a good solution. Unfortunately, there's none that's super obvious to me, neither of cquery or aquery is really the appropriate tool here. I'll bring it up in the team's core sync meeting on Monday and see if anyone has any ideas

From the discussion yesterday: We weren't really sure what to do. There was some talk of adding analysis-query for this, but that seemed a bit overkill, since that's mostly identical to cquery and this is more or less the only use case.
The best idea so far is a buck2 audit analysis-graph :target, which would dump the entire analysis graph (id and deps of each node) of the target. That sounds pretty reasonable and wouldn't be too hard to implement I think

Thanks for discussing on your side.
I am in favor of a potential analysis-query. I think our use case is probably different from Meta's in that we often find ourselves making many (dozens) of distinct binaries from slightly different sets of objects but with significant sharing. One use case today is building ~15 firmware binaries with maybe 70% of files shared on average for a ~100 translation unit binary.
This means the naive build without anonymous targets has 1500 .o actions. The anonymous targets build today is more like ~500. Then we also run e.g. several linters over those source files, which we also do anonymously and delivers similar extreme gains.
We are still working on scaling this but it's not difficult for me to imagine this same average ratio (70%) holding but for other bigger projects with ~10^2 configurations and O(10^2) source files.
A full, capable query flavor would be far and away the best option in my mind here. It's not so much a rare debug event for this usage pattern as a common daily occurrence.

Hey, sorry.

I am in favor of a potential analysis-query. I think our use case is probably different from Meta's in that we often find ourselves making many (dozens) of distinct binaries from slightly different sets of objects but with significant sharing

I think, from the perspective of the design of how we would like buck2 to be designed and used, we would prefer that you didn't do this. Now, don't get me wrong, I understand why you're doing it and it probably is the right tradeoff among the options in front of you, but from a slightly more removed perspective, I would prefer putting effort into making that kind of pattern unnecessary, as opposed to putting effort into supporting it better.
That being said, I don't actually think that analysis query is a bad idea, and I think it fits into the model fine. I don't really expect anyone on our side to pick up work in this direction any time soon, but I think we'd accept a PR for either analysis query or something audit analysis-graph like.

Hey,

I think, from the perspective of the design of how we would like buck2 to be designed and used, we would prefer that you didn't do this. Now, don't get me wrong, I understand why you're doing it and it probably is the right tradeoff among the options in front of you, but from a slightly more removed perspective, I would prefer putting effort into making that kind of pattern unnecessary, as opposed to putting effort into supporting it better.

Which part I guess do you mean you prefer would be different? Splitting that up into two:
First - the dozens (make it hundreds for some projects) of distinct binaries is a project requirement rather than a conscious choice on how to structure a build. The use case is building firmware binaries for many different configurations of the target and the artifacts themselves really do have to be hundreds of largely similar but ultimately different programs.
Please correct me if I'm saying something really stupid somewhere but:
Second - sharing objects between the configs is a conscious choice on how to structure the build to save build time. Ultimately though they really are the same action and with something like https://github.com/facebook/buck2/issues/611, they could be deduplicated on RE instead of being anonymous targets.

Second - sharing objects between the configs is a conscious choice on how to structure the build to save build time. Ultimately though they really are the same action and with something like https://github.com/facebook/buck2/issues/611, they could be deduplicated on RE instead of being anonymous targets.

Yes, this. Ideally you would just get the action sharing for free, without having to jump through hoops.

@JakobDegen , do you have anything in the pipeline or any thoughts on how to solve the action sharing problem? As you mentioned, the hoops are numerous to make it all work with anon_targets.


Cloned repo doesn't work on MacOS xor Python v.3.12

App developed on windows machine thus far,
when going to run cloned repo on mac gets a:
Python may not be configure for TK \ no module named '_tkinter'
Since pysimple GUI relies on TKinter, main.py can't run in poetry shell
Ideas to fix

[ ] Trying pip installing all other dependencies and run normally
[x] Try python v3.12 on Windows for same effect
[ ] Go down rabbit hole of Tkinter configuration

Ended up running in mac terminal brew install python-tk
Python v3.12 was not the issue!!!


CoAP server that listens both to IPv4 and IPv6?

Hi!
I am trying to use the (at seems: abandoned) CoAP package for Node-RED, which is based on node-coap, to create a server that can both handle incoming IPv4 and IPv6 request as it is the case with the respective "nodes" (Node-RED's building blocks for applications or "flows") for HTTP. At the moment, the CoAP nodes seem to only handle IPv4 which is a bit unfortunate considering my intented IoT use-case.
I therefore wanted to ask if there is already an existing solution for creating a server that listens to both incoming IPv4 and IPv6 connections and, if not, if such an extension would be desirable.

I just noticed that creating the server with invoking
coap.createServer({ type: 'udp6' })

actually leads to listening to both IPv4 and IPv6 connections. The issue can therefore be closed :)

I just noticed that creating the server with invoking
coap.createServer({ type: 'udp6' })

actually leads to listening to both IPv4 and IPv6 connections. The issue can therefore be closed :)


fix #871: call check_spark only when necessary

Why are these changes needed?

Currently check_spark will be called when use_spark=False and n_concurrent_trials=1 . Which creates unnecessary spark session. With this PR, only when use_spark=True or (n_concurrent_trials>1 and ray is not available) will check_spark be called.
Related issue number

Closes #871
Checks

[x] I've used pre-commit to lint the changes in this PR, or I've made sure lint with flake8 output is two 0s.
[ ] I've included any doc changes needed for https://microsoft.github.io/FLAML/. See https://microsoft.github.io/FLAML/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[x] I've made sure all auto checks have passed.

@thinkall Thanks for the quick fix!

@thinkall When will this fix be released?

@thinkall When will this fix be released?

We have a few other fixes in progress, I think they will be released together in version 1.1.1. I'm not sure about the ETA, maybe in a week or two? @sonichi may have more info on this.

@thinkall When will this fix be released?

We have a few other fixes in progress, I think they will be released together in version 1.1.1. I'm not sure about the ETA, maybe in a week or two? @sonichi may have more info on this.

We can release as soon as #871 and #869 are merged. The soonest is this weekend. Otherwise next week.


Update install-rpdp.sh

Adding missing dependencies to let all sessions run on Ubuntu in WSL and VMs that do not have them compared to Raspian

this will fix #4

Closing this one and adding a new PR with more changes


"Show costs by" in report shows : comparison of String with 0 failed [report/form_field_changed]

Create a chargeback report and under Filter menu select "Show cost by" .
"Choose' word has some strings .
Select Owner
Error is shown.
In Logs
[----] F, [2015-02-18T18:46:04.653951 #31244:36feac] FATAL -- : Error caught: [ArgumentError] comparison of String with 0 failed
/var/www/miq/vmdb/app/views/report/_form_filter_chargeback.html.haml:22:in >' /var/www/miq/vmdb/app/views/report/_form_filter_chargeback.html.haml:22:in sort'
/var/www/miq/vmdb/app/views/report/_form_filter_chargeback.html.haml:22:in _app_views_report__form_filter_chargeback_html_haml__4178035968206758333_285679960' /opt/rubies/ruby-2.0.0-p598/lib/ruby/gems/2.0.0/bundler/gems/rails-8f014fba21f9/actionpack/lib/action_view/template.rb:145:in block in render'

Bugzilla link - https://bugzilla.redhat.com/show_bug.cgi?id=1201531


Doesn't compile

gcc-10 -O3 cpu_rec.c -o ./cpu_rec
cpu_rec.c: In function ‘read_corpus’:
cpu_rec.c:96:13: error: ‘struct dirent’ has no member named ‘d_namlen’; did you mean ‘d_name’?
   96 |     if ((f->d_namlen<7) || strcmp(f->d_name+f->d_namlen-7,".corpus")) continue;
      |             ^~~~~~~~
      |             d_name
cpu_rec.c:96:48: error: ‘struct dirent’ has no member named ‘d_namlen’; did you mean ‘d_name’?
   96 |     if ((f->d_namlen<7) || strcmp(f->d_name+f->d_namlen-7,".corpus")) continue;
      |                                                ^~~~~~~~
      |                                                d_name
cpu_rec.c:100:38: error: ‘struct dirent’ has no member named ‘d_namlen’; did you mean ‘d_name’?
  100 |     s[h].arch = strndup(f->d_name,f->d_namlen-7);
      |                                      ^~~~~~~~
      |                                      d_name

clang-12 -O3 cpu_rec.c -o ./cpu_rec
cpu_rec.c:96:13: error: no member named 'd_namlen' in 'struct dirent'; did you mean 'd_name'?
    if ((f->d_namlen<7) || strcmp(f->d_name+f->d_namlen-7,".corpus")) continue;
            ^~~~~~~~
            d_name
/usr/include/x86_64-linux-gnu/bits/dirent.h:33:10: note: 'd_name' declared here
    char d_name[256];           /* We must not include limits.h! */
         ^
cpu_rec.c:96:48: error: no member named 'd_namlen' in 'struct dirent'; did you mean 'd_reclen'?
    if ((f->d_namlen<7) || strcmp(f->d_name+f->d_namlen-7,".corpus")) continue;
                                               ^~~~~~~~
                                               d_reclen
/usr/include/x86_64-linux-gnu/bits/dirent.h:31:24: note: 'd_reclen' declared here
    unsigned short int d_reclen;
                       ^
cpu_rec.c:100:38: error: no member named 'd_namlen' in 'struct dirent'; did you mean 'd_name'?
    s[h].arch = strndup(f->d_name,f->d_namlen-7);
                                     ^~~~~~~~
                                     d_name
/usr/include/x86_64-linux-gnu/bits/dirent.h:33:10: note: 'd_name' declared here
    char d_name[256];           /* We must not include limits.h! */
         ^
3 errors generated.

Yes indeed. d_namlen is not available everywhere.

Yes indeed. d_namlen is not available everywhere.


Pushsync retry next peer after error

Updates pushsync.PushChunkToClosest function with the change where it will attempt multiple peers if one fails.
Previous code only ever attempted to push to same peer (that was deemed as "closest"), even in the face of problems with that host. This change adds loop which attempts closest peer, and if there are some problems with that peer tries some other closest peer (from the available ones). Depending on the error, it may blocklist the peer for some time (one minute). It will try to maximum of 5 peers. If each of them fails it will return last error that was encountered.

/run beekeeper

/run beekeeper

/run beekeeper


Add homepage update about logs working group

Fits under the beta box, though I'd prefer if this and the "Discover Integrations" box could sit side by side. @austinlparker is that possible?

Yeah, it's possible. Do you want to merge this and have me make another PR to fix it, or do you want to try to and change it yourself? You'd need to edit the beta column as well to make it not extend across the window.

Let's merge and then followup with another PR if that's ok

kk


Failed to build from release 0.3.1 sources

The buid script failed on git repository missing if I use source code tarball from  release page.

Oh, yeah, that makes sense that that would fail. Sorry about that. I'll make a fix for that.

+1. Still happening for 0.4.0


[Bug] Error adding entities for domain sensor with platform smart_irrigation

Describe the bug
Error Log Messages:
Error adding entities for domain sensor with platform smart_irrigation
Error while setting up smart_irrigation platform for sensor
To Reproduce
Steps to reproduce the behavior:

Install Smart Irrigation
Used my own sensors rather than OWM
Restart HA

Expected behavior
No error message. Not sure if is affecting the evapotranspiration calculation.
Screenshots

Installed version
Latest Integration on HA 2020.12
Additional context
I have been using Smart Irrigation (a great product) with OWM. I changed to my own sensors a week ago. All the calculations seem to be happening, so it is possible I hadn't noticed this error. I am not sure if the error is affecting results.

It looks like it is still trying to parse your own sensor data as if it is OWM.

I deleted the OWM and Smart Irrigation installation. I stopped the AppDaemon which references some of the entities. I then restarted and installed Smart Irrigation.
The error message is still there.

Confirming that I leave a tick on the first page that says 'remove tick if you provide your own Evapotranspiration sensor'.
I notice that when you delete the SI integration the code remains in the custom components folder.

hmm, 2 is not supposed to happen. Can you please uninstall and remove the folder by hand, reboot and then reinstall?

Error has gone. Thx for your help. I had not appreciated that an uninstall needs to happen at the HACS interface not just the HA Integration page.

The error is back. It appears after an uninstall and reinstall it runs cleanly. After a 2nd restart the program goes looking for OWM data. I have looked at the program logic but it is a bit sophisticated for me.  Any thoughts?

I am using cytech/Home-Assistant-wundergroundpws to create my sensors. Could it be that the sensors aren’t being created in time for smart irrigation to pick them up. If so, how could I introduce a a delay for smart irrigation to run?

can you share your config? what are the settings you made?

can you share your config? what are the settings you made?

Hi @jeroenterheerdt
I have a similar issue - I think that it is the same bug, here is the error log:
Logger: homeassistant.components.sensor
Source: custom_components/smart_irrigation/sensor.py:684
Integration: Sensor (documentation, issues)
First occurred: January 4, 2021, 8:46:07 AM (2 occurrences)
Last logged: January 4, 2021, 8:46:07 AM

Error adding entities for domain sensor with platform smart_irrigation
Error while setting up smart_irrigation platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 531, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    sstate = self.state
  File "/config/custom_components/smart_irrigation/sensor.py", line 551, in state
    self._state = self.update_state()
  File "/config/custom_components/smart_irrigation/sensor.py", line 510, in update_state
    self.evapotranspiration = self.get_evapotranspiration(data)
  File "/config/custom_components/smart_irrigation/sensor.py", line 684, in get_evapotranspiration
    pressure = data["pressure"]
KeyError: 'pressure'

and here is an extract of the config:
        {
            "entry_id": "0f170c17ae3adea1e16dae650350e11c",
            "version": 1,
            "domain": "smart_irrigation",
            "title": "Smart Irrigation",
            "data": {
                "number_of_sprinklers": 1.0,
                "flow": 21.59,
                "area": 50.0,
                "api_key": null,
                "reference_evapotranspiration": [
                    6.2,
                    5.7,
                    5.02,
                    4.34,
                    3.36,
                    3.1,
                    3.3,
                    4.0,
                    5.21,
                    5.78,
                    6.29,
                    6.47
                ],
                "name": "Smart Irrigation",
                "sources": {
                    "use_owm_precipitation": false,
                    "use_owm_temperature": false,
                    "use_owm_min_temperature": false,
                    "use_owm_max_temperature": false,
                    "use_owm_dewpoint": false,
                    "use_owm_pressure": false,
                    "use_owm_humidity": false,
                    "use_owm_windspeed": false,
                    "calculate_solar_radiation": false,
                    "calculate_ET_value": true
                },
                "sensors": {
                    "sensor_precipitation": "sensor.rain_daily",
                    "sensor_temperature": "sensor.weather_station_temperature",
                    "sensor_min_temperature": "sensor.daily_min_temp",
                    "sensor_max_temperature": "sensor.daily_max_temp",
                    "sensor_dewpoint": "sensor.weather_station_dewpoint",
                    "sensor_pressure": "sensor.pressure",
                    "sensor_humidity": "sensor.weather_station_humidity",
                    "sensor_windspeed": "sensor.weather_station_wind_speed",
                    "sensor_solar_radiation": "sensor.solar_radiation"
                }
            },
            "options": {},
            "system_options": {
                "disable_new_entities": false
            },
            "source": "user",
            "connection_class": "cloud_poll",
            "unique_id": "Smart Irrigation"
        },

I think that it is to do with the startup process as my weather station reports pressures and solar radiation every 5 min and doesn't return a value until the first mqtt post from the weather station.  I suspect this error occurs since there is not value for pressure when it starts up.

Hi @jeroenterheerdt
I have a similar issue - I think that it is the same bug, here is the error log:
Logger: homeassistant.components.sensor
Source: custom_components/smart_irrigation/sensor.py:684
Integration: Sensor (documentation, issues)
First occurred: January 4, 2021, 8:46:07 AM (2 occurrences)
Last logged: January 4, 2021, 8:46:07 AM

Error adding entities for domain sensor with platform smart_irrigation
Error while setting up smart_irrigation platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 531, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    sstate = self.state
  File "/config/custom_components/smart_irrigation/sensor.py", line 551, in state
    self._state = self.update_state()
  File "/config/custom_components/smart_irrigation/sensor.py", line 510, in update_state
    self.evapotranspiration = self.get_evapotranspiration(data)
  File "/config/custom_components/smart_irrigation/sensor.py", line 684, in get_evapotranspiration
    pressure = data["pressure"]
KeyError: 'pressure'

and here is an extract of the config:
        {
            "entry_id": "0f170c17ae3adea1e16dae650350e11c",
            "version": 1,
            "domain": "smart_irrigation",
            "title": "Smart Irrigation",
            "data": {
                "number_of_sprinklers": 1.0,
                "flow": 21.59,
                "area": 50.0,
                "api_key": null,
                "reference_evapotranspiration": [
                    6.2,
                    5.7,
                    5.02,
                    4.34,
                    3.36,
                    3.1,
                    3.3,
                    4.0,
                    5.21,
                    5.78,
                    6.29,
                    6.47
                ],
                "name": "Smart Irrigation",
                "sources": {
                    "use_owm_precipitation": false,
                    "use_owm_temperature": false,
                    "use_owm_min_temperature": false,
                    "use_owm_max_temperature": false,
                    "use_owm_dewpoint": false,
                    "use_owm_pressure": false,
                    "use_owm_humidity": false,
                    "use_owm_windspeed": false,
                    "calculate_solar_radiation": false,
                    "calculate_ET_value": true
                },
                "sensors": {
                    "sensor_precipitation": "sensor.rain_daily",
                    "sensor_temperature": "sensor.weather_station_temperature",
                    "sensor_min_temperature": "sensor.daily_min_temp",
                    "sensor_max_temperature": "sensor.daily_max_temp",
                    "sensor_dewpoint": "sensor.weather_station_dewpoint",
                    "sensor_pressure": "sensor.pressure",
                    "sensor_humidity": "sensor.weather_station_humidity",
                    "sensor_windspeed": "sensor.weather_station_wind_speed",
                    "sensor_solar_radiation": "sensor.solar_radiation"
                }
            },
            "options": {},
            "system_options": {
                "disable_new_entities": false
            },
            "source": "user",
            "connection_class": "cloud_poll",
            "unique_id": "Smart Irrigation"
        },

I think that it is to do with the startup process as my weather station reports pressures and solar radiation every 5 min and doesn't return a value until the first mqtt post from the weather station.  I suspect this error occurs since there is not value for pressure when it starts up.

ok, you can go into optional settings and set an initial update delay: see the readme: https://github.com/jeroenterheerdt/HAsmartirrigation#step-4-configuring-optional-settings

ok, you can go into optional settings and set an initial update delay: see the readme: https://github.com/jeroenterheerdt/HAsmartirrigation#step-4-configuring-optional-settings

OK, thanks - I had it on 300s already which should be enough time, I bumped it up to 900s but it still gives errors (sometimes for t_min as well as pressure).  This only seems to be an issue at startup as, from what I can tell it still provides working calulations.

OK, thanks - I had it on 300s already which should be enough time, I bumped it up to 900s but it still gives errors (sometimes for t_min as well as pressure).  This only seems to be an issue at startup as, from what I can tell it still provides working calulations.

I have the same results i.e. had 300 increased to 600 second delay but the error remained. Here is my configuration as requested:
{
"entry_id": "337de23b856ecf0c5342924a0a996e89",
"version": 1,
"domain": "smart_irrigation",
"title": "Smart Irrigation",
"data": {
"number_of_sprinklers": 23.0,
"flow": 5.0,
"area": 328.0,
"api_key": null,
"reference_evapotranspiration": [
7.49,
5.64,
3.84,
2.54,
1.61,
1.19,
1.41,
1.8,
2.75,
3.55,
5.06,
8.1
],
"name": "Smart Irrigation",
"sources": {
"use_owm_precipitation": false,
"use_owm_temperature": false,
"use_owm_min_temperature": false,
"use_owm_max_temperature": false,
"use_owm_dewpoint": false,
"use_owm_pressure": false,
"use_owm_humidity": false,
"use_owm_windspeed": false,
"calculate_solar_radiation": false,
"calculate_ET_value": true
},
"sensors": {
"sensor_precipitation": "sensor.wupws_preciptotal",
"sensor_temperature": "sensor.wupws_temp",
"sensor_min_temperature": "sensor.low_temperature_today",
"sensor_max_temperature": "sensor.high_temperature_today",
"sensor_dewpoint": "sensor.wupws_dewpt",
"sensor_pressure": "sensor.wupws_pressure",
"sensor_humidity": "sensor.wupws_humidity",
"sensor_windspeed": "sensor.wupws_windspeed",
"sensor_solar_radiation": "sensor.wupws_solarradiation"
}
},
"options": {
"lead_time": 0,
"maximum_duration": -1,
"force_mode_duration": 0,
"show_units": true,
"auto_refresh": true,
"auto_refresh_time": "23:00",
"initial_update_delay": 300,
"coastal": false,
"estimate_solrad_from_temp": true
},
"system_options": {
"disable_new_entities": false
},
"source": "user",
"connection_class": "cloud_poll",
"unique_id": "Smart Irrigation"
}

I have the same results i.e. had 300 increased to 600 second delay but the error remained. Here is my configuration as requested:
{
"entry_id": "337de23b856ecf0c5342924a0a996e89",
"version": 1,
"domain": "smart_irrigation",
"title": "Smart Irrigation",
"data": {
"number_of_sprinklers": 23.0,
"flow": 5.0,
"area": 328.0,
"api_key": null,
"reference_evapotranspiration": [
7.49,
5.64,
3.84,
2.54,
1.61,
1.19,
1.41,
1.8,
2.75,
3.55,
5.06,
8.1
],
"name": "Smart Irrigation",
"sources": {
"use_owm_precipitation": false,
"use_owm_temperature": false,
"use_owm_min_temperature": false,
"use_owm_max_temperature": false,
"use_owm_dewpoint": false,
"use_owm_pressure": false,
"use_owm_humidity": false,
"use_owm_windspeed": false,
"calculate_solar_radiation": false,
"calculate_ET_value": true
},
"sensors": {
"sensor_precipitation": "sensor.wupws_preciptotal",
"sensor_temperature": "sensor.wupws_temp",
"sensor_min_temperature": "sensor.low_temperature_today",
"sensor_max_temperature": "sensor.high_temperature_today",
"sensor_dewpoint": "sensor.wupws_dewpt",
"sensor_pressure": "sensor.wupws_pressure",
"sensor_humidity": "sensor.wupws_humidity",
"sensor_windspeed": "sensor.wupws_windspeed",
"sensor_solar_radiation": "sensor.wupws_solarradiation"
}
},
"options": {
"lead_time": 0,
"maximum_duration": -1,
"force_mode_duration": 0,
"show_units": true,
"auto_refresh": true,
"auto_refresh_time": "23:00",
"initial_update_delay": 300,
"coastal": false,
"estimate_solrad_from_temp": true
},
"system_options": {
"disable_new_entities": false
},
"source": "user",
"connection_class": "cloud_poll",
"unique_id": "Smart Irrigation"
}

For each of the sensors that give errors can you share a screenshot that shows values and attributes
Get Outlook for Androidhttps://aka.ms/ghei36

From: David Bryant<EMAIL_ADDRESS>Sent: Monday, January 4, 2021 5:10:29 PM
To: jeroenterheerdt/HAsmartirrigation<EMAIL_ADDRESS>Cc: Jeroen ter Heerdt<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] (#49)
I have the same results i.e. had 300 increased to 600 second delay but the error remained. Here is my configuration as requested:
{
"entry_id": "337de23b856ecf0c5342924a0a996e89",
"version": 1,
"domain": "smart_irrigation",
"title": "Smart Irrigation",
"data": {
"number_of_sprinklers": 23.0,
"flow": 5.0,
"area": 328.0,
"api_key": null,
"reference_evapotranspiration": [
7.49,
5.64,
3.84,
2.54,
1.61,
1.19,
1.41,
1.8,
2.75,
3.55,
5.06,
8.1
],
"name": "Smart Irrigation",
"sources": {
"use_owm_precipitation": false,
"use_owm_temperature": false,
"use_owm_min_temperature": false,
"use_owm_max_temperature": false,
"use_owm_dewpoint": false,
"use_owm_pressure": false,
"use_owm_humidity": false,
"use_owm_windspeed": false,
"calculate_solar_radiation": false,
"calculate_ET_value": true
},
"sensors": {
"sensor_precipitation": "sensor.wupws_preciptotal",
"sensor_temperature": "sensor.wupws_temp",
"sensor_min_temperature": "sensor.low_temperature_today",
"sensor_max_temperature": "sensor.high_temperature_today",
"sensor_dewpoint": "sensor.wupws_dewpt",
"sensor_pressure": "sensor.wupws_pressure",
"sensor_humidity": "sensor.wupws_humidity",
"sensor_windspeed": "sensor.wupws_windspeed",
"sensor_solar_radiation": "sensor.wupws_solarradiation"
}
},
"options": {
"lead_time": 0,
"maximum_duration": -1,
"force_mode_duration": 0,
"show_units": true,
"auto_refresh": true,
"auto_refresh_time": "23:00",
"initial_update_delay": 300,
"coastal": false,
"estimate_solrad_from_temp": true
},
"system_options": {
"disable_new_entities": false
},
"source": "user",
"connection_class": "cloud_poll",
"unique_id": "Smart Irrigation"
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F49%23issuecomment-754321632&data=04|01||3ab5bc8e42eb4149c86508d8b116b2b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637454058329146659|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6up9WiJH8J7XduLdPgfxTbgBPgz8ON9wSABvGHOr5ms%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPX7GWLRQ5U5QYCVECDSYJRILANCNFSM4U2AOADA&data=04|01||3ab5bc8e42eb4149c86508d8b116b2b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637454058329156654|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=arDK6g4vrId2LbpGeUTbv0WSZNHpHzzgnyZGfMOZoSA%3D&reserved=0.

For each of the sensors that give errors can you share a screenshot that shows values and attributes
Get Outlook for Androidhttps://aka.ms/ghei36

From: David Bryant<EMAIL_ADDRESS>Sent: Monday, January 4, 2021 5:10:29 PM
To: jeroenterheerdt/HAsmartirrigation<EMAIL_ADDRESS>Cc: Jeroen ter Heerdt<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] (#49)
I have the same results i.e. had 300 increased to 600 second delay but the error remained. Here is my configuration as requested:
{
"entry_id": "337de23b856ecf0c5342924a0a996e89",
"version": 1,
"domain": "smart_irrigation",
"title": "Smart Irrigation",
"data": {
"number_of_sprinklers": 23.0,
"flow": 5.0,
"area": 328.0,
"api_key": null,
"reference_evapotranspiration": [
7.49,
5.64,
3.84,
2.54,
1.61,
1.19,
1.41,
1.8,
2.75,
3.55,
5.06,
8.1
],
"name": "Smart Irrigation",
"sources": {
"use_owm_precipitation": false,
"use_owm_temperature": false,
"use_owm_min_temperature": false,
"use_owm_max_temperature": false,
"use_owm_dewpoint": false,
"use_owm_pressure": false,
"use_owm_humidity": false,
"use_owm_windspeed": false,
"calculate_solar_radiation": false,
"calculate_ET_value": true
},
"sensors": {
"sensor_precipitation": "sensor.wupws_preciptotal",
"sensor_temperature": "sensor.wupws_temp",
"sensor_min_temperature": "sensor.low_temperature_today",
"sensor_max_temperature": "sensor.high_temperature_today",
"sensor_dewpoint": "sensor.wupws_dewpt",
"sensor_pressure": "sensor.wupws_pressure",
"sensor_humidity": "sensor.wupws_humidity",
"sensor_windspeed": "sensor.wupws_windspeed",
"sensor_solar_radiation": "sensor.wupws_solarradiation"
}
},
"options": {
"lead_time": 0,
"maximum_duration": -1,
"force_mode_duration": 0,
"show_units": true,
"auto_refresh": true,
"auto_refresh_time": "23:00",
"initial_update_delay": 300,
"coastal": false,
"estimate_solrad_from_temp": true
},
"system_options": {
"disable_new_entities": false
},
"source": "user",
"connection_class": "cloud_poll",
"unique_id": "Smart Irrigation"
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F49%23issuecomment-754321632&data=04|01||3ab5bc8e42eb4149c86508d8b116b2b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637454058329146659|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6up9WiJH8J7XduLdPgfxTbgBPgz8ON9wSABvGHOr5ms%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPX7GWLRQ5U5QYCVECDSYJRILANCNFSM4U2AOADA&data=04|01||3ab5bc8e42eb4149c86508d8b116b2b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637454058329156654|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=arDK6g4vrId2LbpGeUTbv0WSZNHpHzzgnyZGfMOZoSA%3D&reserved=0.

Here are some screenshots of the errors.  effectively it is the hourly run time sensor that doesn't update on a Home assistant restart.  Here is a history card showing the states after a reboot:

there are several reboots here which you can see when the netto precipitation goes to zero.  The hourly run time is unavailable:

but after a few about 5 minutes, it comes back again and appears to work normally:

hope that helps to track down the issue. It looks like it is throwing the error when it can't pick up the values after the reboot but then all is good when it finally sees the appropriate sensors.

Here are some screenshots of the errors.  effectively it is the hourly run time sensor that doesn't update on a Home assistant restart.  Here is a history card showing the states after a reboot:

there are several reboots here which you can see when the netto precipitation goes to zero.  The hourly run time is unavailable:

but after a few about 5 minutes, it comes back again and appears to work normally:

hope that helps to track down the issue. It looks like it is throwing the error when it can't pick up the values after the reboot but then all is good when it finally sees the appropriate sensors.

It looks like that for the pressure sensor the issue is with the sensor not reporting a value (notice there is a tiny gap in the graph at about the same time). That's why hourly adjusted run time fails to work. It will try again after the initial update delay however. I can make the code more resilient to these kind of errors, but in essence it is out of my control.

It looks like that for the pressure sensor the issue is with the sensor not reporting a value (notice there is a tiny gap in the graph at about the same time). That's why hourly adjusted run time fails to work. It will try again after the initial update delay however. I can make the code more resilient to these kind of errors, but in essence it is out of my control.

Jeroen, I raised this issue initially as I was concerned it could affect results.  It appears the results are correct, so I am comfortable to close this issue.

Jeroen, I raised this issue initially as I was concerned it could affect results.  It appears the results are correct, so I am comfortable to close this issue.

It looks like the system assumes I am using OWM in the following routine when it checks for data. If I replace this test with 'if self.coordinator.api' the logic is the same but the error is removed. For your consideration.
def get_evapotranspiration(self, data):
"""Calculate Evantranspiration info from OWM data."""
if self.coordinator.api:
# if data is not None:
day_of_year = datetime.datetime.now().timetuple().tm_yday
if "temp" in data:
t_day = data["temp"]["day"]
t_min = data["temp"]["min"]
t_max = data["temp"]["max"]
else:
return 0.0

Thanks, which version of the component are you on?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: David Bryant @.>
Sent: Thursday, August 5, 2021 6:21:13 PM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Mention @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] Error adding entities for domain sensor with platform smart_irrigation (#49)
It looks like the system assumes I am using OWM in the following routine when it checks for data. If I replace this test with 'if self.coordinator.api' the logic is the same but the error is removed. For your consideration.
def get_evapotranspiration(self, data):
"""Calculate Evantranspiration info from OWM data."""
if self.coordinator.api:
if data is not None:
day_of_year = datetime.datetime.now().timetuple().tm_yday
if "temp" in data:
t_day = data["temp"]["day"]
t_min = data["temp"]["min"]
t_max = data["temp"]["max"]
else:
return 0.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F49%23issuecomment-893932769&data=04|01||a4afa97eb0504b81b12908d958787b5b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637638096757870877|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OkqB6i1HxpN7moFrHOARrO5CHCcDlGXqMN0F3ez4ZCs%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPWF67DYOZV63K4PVCLT3M2ITANCNFSM4U2AOADA&data=04|01||a4afa97eb0504b81b12908d958787b5b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637638096757880874|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=hihiQlZ4xqDz4C3rUbmFPbjPiLa3t2OulN6VphD%2FeQI%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||a4afa97eb0504b81b12908d958787b5b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637638096757880874|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=vzhsWapHJztn2qgKX0GZTacQnZGoyNZ8lZhuHAytlLc%3D&reserved=0 or Androidhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01||a4afa97eb0504b81b12908d958787b5b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637638096757890863|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2BgCD3goKs0SKUPn6KMgcV8EBwSvbznemjbTeGFk6Vc%3D&reserved=0.

"version": "0.0.69"

do you see any errors? or is everything working as expected? The component just uses the same data structure if the data came OWM or sensors or a mixture of both. So unless you are seeing errors I am confident this works as expected. If the comment let you to the conclusion that the component assumes you are using OWM then I can easily fix the comment. The code does not assume any of the sorts.

Yes, the program assumes I am using OWM, when I am not. When the code gets to 'get_evapotranspiration(self, data)' it does a check just to confirm I am not using OWM. It does this check by querying 'if data is not None'. In my case the code must find some data and carries on as if I have OWM. When I replace the test of data with 'if self.coordinator.api:' the code does not proceed and I do not see the error 'Error adding entities for domain sensor with platform smart_irrigation'.

Can you please share the error log?

Here is the log up to the error messages.
2021-08-13 15:14:32 INFO (MainThread) [custom_components.smart_irrigation]
Smart Irrigation
Version: 0.0.73
If you have any issues with this you need to open an issue here:
https://github.com/jeroenterheerdt/HASmartIrrigation/issues
2021-08-13 15:14:32 INFO (MainThread) [custom_components.smart_irrigation] Smart Irrigation sensors: {'sensor_windspeed': 'sensor.wind_speed_2', 'sensor_precipitation': 'sensor.daily_rain_rate_2', 'sensor_temperature': 'sensor.outdoor_temperature', 'sensor_min_temperature': 'sensor.low_temperature_today', 'sensor_max_temperature': 'sensor.high_temperature_today', 'sensor_dewpoint': 'sensor.dewpoint', 'sensor_pressure': 'sensor.relative_pressure', 'sensor_humidity': 'sensor.humidity'}
2021-08-13 15:14:32 INFO (MainThread) [custom_components.smart_irrigation] Auto refresh is enabled. Scheduling for 23:00.
2021-08-13 15:14:32 INFO (MainThread) [custom_components.smart_irrigation] Initial update scheduled for 2021-08-13 15:19:32.337681+10:00
2021-08-13 15:14:32 INFO (MainThread) [custom_components.smart_irrigation] Updating Smart Irrigation Data
2021-08-13 15:14:32 INFO (MainThread) [custom_components.auto_backup.config_flow] Importing config entry from configuration.yaml
2021-08-13 15:14:32 INFO (MainThread) [hass_nabucasa.iot] Connected
2021-08-13 15:14:32 INFO (MainThread) [snitun.utils.aiohttp_client] AioHTTP snitun client started on <IP_ADDRESS>:53845
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setup of domain media_source took 5.4 seconds
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 5.4 seconds
2021-08-13 15:14:32 INFO (SyncWorker_4) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setting up tplink
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setup of domain tplink took 0.0 seconds
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setting up network
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 5.0 seconds
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setting up hacs
2021-08-13 15:14:32 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 0.0 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up smartthings
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up energy
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain energy took 0.0 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up script
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 1.2 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up camera
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain ffmpeg took 6.2 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tasmota
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.tasmota
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.switch] Setting up switch.tasmota
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain tag took 1.2 seconds
2021-08-13 15:14:33 INFO (SyncWorker_4) [homeassistant.loader] Loaded stt from homeassistant.components.stt
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.smart_irrigation
2021-08-13 15:14:33 INFO (MainThread) [custom_components.auto_backup] Setting up Auto Backup config entry 67c8c53062882439c791c979faa4d44d
2021-08-13 15:14:33 INFO (SyncWorker_1) [homeassistant.loader] Loaded fan from homeassistant.components.fan
2021-08-13 15:14:33 INFO (SyncWorker_4) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2021-08-13 15:14:33 INFO (SyncWorker_2) [homeassistant.loader] Loaded light from homeassistant.components.light
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.cloud
2021-08-13 15:14:33 INFO (MainThread) [custom_components.smart_irrigation.sensor] sensor init for current_adjusted_run_time. bucket_delta=0
2021-08-13 15:14:33 INFO (MainThread) [custom_components.smart_irrigation.sensor] sensor init for adjusted_run_time. bucket=0
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.energy
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up stt
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain stt took 0.0 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 6.6 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain network took 1.2 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up fan
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain fan took 0.0 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up cover
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setup of domain cover took 0.0 seconds
2021-08-13 15:14:33 INFO (MainThread) [homeassistant.setup] Setting up light
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain counter took 6.5 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 6.5 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 2.1 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain smartthings took 1.0 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 1.0 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain script took 1.1 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.fan] Setting up fan.tasmota
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.cover] Setting up cover.tasmota
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain light took 0.4 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.setup] Setup of domain group took 2.4 seconds
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.camera] Setting up camera.foscam
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.camera] Setting up camera.foscam
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation] registering: type: Base Schedule Index, entity: sensor.smart_irrigation_base_schedule_index
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Base Schedule Index state: 1386.2, attributes: {'number_of_sprinklers': 23.0, 'flow': '5.0', 'throughput': '115.0', 'reference_evapotranspiration': '[7.49, 5.64, 3.84, 2.54, 1.61, 1.19, 1.41, 1.8, 2.75, 3.55, 5.06, 8.1]', 'peak_evapotranspiration': '8.1', 'area': '328.0', 'precipitation_rate': '21.04', 'base_schedule_index_minutes': 23.1, 'auto_refresh': True, 'auto_refresh_time': '23:00', 'initial_update_delay': 300, 'coastal': False, 'estimate_solrad_from_temp': True, 'unit_of_measurement': 's', 'friendly_name': 'Base Schedule Index', 'icon': 'mdi:sprinkler'}
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state for type: Base Schedule Index
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state for type: Base Schedule Index
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation] registering: type: Hourly Adjusted Run Time, entity: sensor.smart_irrigation_hourly_adjusted_run_time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time state: 0, attributes: {'rain': '0.0', 'snow': '0.0', 'precipitation': '0.0', 'evapotranspiration': '0.0', 'netto_precipitation': '0.0', 'water_budget': 0.0, 'adjusted_run_time_minutes': 0.0, 'unit_of_measurement': 's', 'friendly_name': 'Hourly Adjusted Run Time', 'icon': 'mdi:sprinkler'}
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: evapotranspiration, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: netto_precipitation, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_to_hass restoring state, setting netto precipitation / bucket_delta to: 0.0
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: precipitation, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: rain, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: snow, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: water_budget, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Hourly Adjusted Run Time, attribute: adjusted_run_time_minutes, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state for type: Hourly Adjusted Run Time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_windspeed, entity: sensor.wind_speed_2, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_precipitation, entity: sensor.daily_rain_rate_2, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_temperature, entity: sensor.outdoor_temperature, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_min_temperature, entity: sensor.low_temperature_today, sensor_state: <state sensor.low_temperature_today=unknown; unit_of_measurement=°C, friendly_name=Low Temperature Today @ 2021-08-13T15:14:25.530598+10:00>
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_max_temperature, entity: sensor.high_temperature_today, sensor_state: <state sensor.high_temperature_today=unknown; unit_of_measurement=°C, friendly_name=High Temperature Today @ 2021-08-13T15:14:25.530097+10:00>
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_dewpoint, entity: sensor.dewpoint, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_pressure, entity: sensor.relative_pressure, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state USING A SENSOR for instance Smart_Irrigation, type: Hourly Adjusted Run Time, sensor: sensor_humidity, entity: sensor.humidity, sensor_state: None
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] rain: 0.0, snow: 0.0
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation] registering: type: Daily Adjusted Run Time, entity: sensor.smart_irrigation_daily_adjusted_run_time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Daily Adjusted Run Time state: 0, attributes: {'water_budget': 0.0, 'bucket': '313.83', 'lead_time': 0, 'maximum_duration': -1, 'adjusted_run_time_minutes': 0.0, 'force_mode_duration': 0, 'force_mode_enabled': False, 'unit_of_measurement': 's', 'icon': 'mdi:sprinkler', 'friendly_name': 'Daily Adjusted Run Time'}
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Daily Adjusted Run Time, attribute: water_budget, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Daily Adjusted Run Time, attribute: bucket, attribute_value: 313.83, numeric_part: 313.83, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_to_hass restoring state, settting bucket to: 313.83
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] async_added_t_hass type: Daily Adjusted Run Time, attribute: adjusted_run_time_minutes, attribute_value: 0.0, numeric_part: 0.0, show_units: False, a_val was str or contained ' ': False
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state for type: Daily Adjusted Run Time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] Calculated water_budget = 0 and adjusted_run_time: 0 for type: Daily Adjusted Run Time. Bucket value was: 313.83, and base schedule index is: 1386.1565217391305, force mode is: False, force mode duration is: 0, lead_time is: 0, maximum_duration: -1, change percentage: 1.0, type: Daily Adjusted Run Time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] calculating wb and art for daily adjusted run time, result: {'wb': 0, 'art': 0}
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] update_state for type: Daily Adjusted Run Time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] Calculated water_budget = 0 and adjusted_run_time: 0 for type: Daily Adjusted Run Time. Bucket value was: 313.83, and base schedule index is: 1386.1565217391305, force mode is: False, force mode duration is: 0, lead_time is: 0, maximum_duration: -1, change percentage: 1.0, type: Daily Adjusted Run Time
2021-08-13 15:14:34 INFO (MainThread) [custom_components.smart_irrigation.sensor] calculating wb and art for daily adjusted run time, result: {'wb': 0, 'art': 0}
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.light] Setting up light.tasmota
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.speedtestdotnet
2021-08-13 15:14:34 INFO (MainThread) [custom_components.hacs]
HACS (Home Assistant Community Store)
Version: 1.13.2
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/hacs/integration/issues
2021-08-13 15:14:34 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.WEBSOCKET
2021-08-13 15:14:34 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.FRONTEND
2021-08-13 15:14:34 INFO (MainThread) [custom_components.hacs] LovelaceMode.STORAGE mode, cache for /hacsfiles/: True
2021-08-13 15:14:34 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.auto_backup
2021-08-13 15:14:34 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform smart_irrigation
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 587, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 711, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 464, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 498, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in _stringify_state
state = self.state
File "/config/custom_components/smart_irrigation/sensor.py", line 557, in state
self._state = self.update_state()
File "/config/custom_components/smart_irrigation/sensor.py", line 516, in update_state
self.evapotranspiration = self.get_evapotranspiration(data)
File "/config/custom_components/smart_irrigation/sensor.py", line 684, in get_evapotranspiration
t_day = data["temp"]["day"]
KeyError: 'day'
2021-08-13 15:14:35 INFO (MainThread) [homeassistant.setup] Setting up automation
2021-08-13 15:14:36 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.CATEGORIES
2021-08-13 15:14:36 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up smart_irrigation platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 257, in _async_setup_platform
await asyncio.gather(*pending)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 587, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 711, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 464, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 498, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in _stringify_state
state = self.state
File "/config/custom_components/smart_irrigation/sensor.py", line 557, in state
self._state = self.update_state()
File "/config/custom_components/smart_irrigation/sensor.py", line 516, in update_state
self.evapotranspiration = self.get_evapotranspiration(data)
File "/config/custom_components/smart_irrigation/sensor.py", line 684, in get_evapotranspiration
t_day = data["temp"]["day"]
KeyError: 'day'
2021-08-13 15:14:36 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 4.0 seconds
2021-08-13 15:14:36 INFO (MainThread) [custom_components.hacs] HACS is enabled

ok, so let me explain again: we use the same data structure for the OWM and the sensor data. If you have only sensors that data is put into the OWM data structure so we don't have to handle it differently. The function that fails now is just parsing the data, and does not know (and does not have to know) if the data come from OWM or from sensors or a mixture. Changing the if statement as you did does not do the right thing as it will disable the calculation of the ET value all together.
What is the real issue here is that the day temperature is not included in the data structure provided as input into the get_evotranspiration function.
I am seeing a couple of interesting things in the logs:

multiple show_units: False, a_val was str or contained ' ': False, which I cannot explain.
the temperature sensors have a state of None, that probably explains why the day temperature is not present in the data structure when calling get_evotranspiration. Can you verify that at reboot these sensors are available and providing an actual value? We have a setting callied initial update delay to deal with this situation - it allows you to push back the initial update after reboot so these sensors can get a value other than None. As soon as they have a value this should start working without a hitch.

The initial update delay is set to 300s. I have confirmed the day temperature is available (it displays on Lovelace), however the max & min temperatures may not be available initially as they are calculated by a template on the day temperature.
I appreciate your efforts and feedback. This is a great app and works well for me. I will close this issue.

Thanks for the kind words. You might want to check out Daily Sensor, a component I made as well. Link is in the readme. It is built to give you the max and min and works fine with this component.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: David Bryant @.>
Sent: Monday, August 16, 2021 5:29:22 PM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Jeroen ter Heerdt @.>; Mention @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] [Bug] Error adding entities for domain sensor with platform smart_irrigation (#49)
The initial update delay is set to 300s. I have confirmed the day temperature is available (it displays on Lovelace), however the max & min temperatures may not be available initially as they are calculated by a template on the day temperature.
I appreciate your efforts and feedback. This is a great app and works well for me. I will close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjeroenterheerdt%2FHAsmartirrigation%2Fissues%2F49%23issuecomment-899905223&data=04|01||3a73798edae046eff96008d961160f9c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637647569644544213|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=fQInom0fbg4nza40jXsyvCKb9Lj1fEXSVDqDPrP9pxs%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB6PIPQIZGVQHIWDUFSWZ7TT5GUOFANCNFSM4U2AOADA&data=04|01||3a73798edae046eff96008d961160f9c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637647569644544213|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ECbklBN%2FoSS1pB067XJ7igbzEsO4Qr0xbRVxvboAok4%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||3a73798edae046eff96008d961160f9c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637647569644554210|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=q6vr6kVkl4ScEObEM8LnXfbl%2FUZY7ImL2fxVeLZTQOY%3D&reserved=0 or Androidhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01||3a73798edae046eff96008d961160f9c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637647569644554210|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=FvT42gwmteVtU6%2FvyvTrueWoA8%2B%2BCzBwRB0uRyV0Ewo%3D&reserved=0.


Cannot see 1 of 2 Ring Cameras

Describe Your Problem:
Removed one of my Ring Cameras off Home app while troubleshooting. Unable to add camera back to Homekit
Logs:
Homebridge log does show second camera when loading accessories but does not show in Home App and cannot add as new accessory.
Show the Homebridge logs here.
Remove any sensative information.

Homebridge Config:
{
    "server": {
        "port": 8080,
        "origin": "*",
        "autostart": 0,
        "home_setup_id": "X-HM://xxxxxxxxxxx",
        "polling_seconds": 5
    },
    "client": {
        "default_route": "status",
        "inactive_logoff": 30,
        "theme": "hoobs-dark",
        "locale": "en",
        "temp_units": "fahrenheit",
        "country_code": "US",
        "postal_code": "32824"
    },
    "bridge": {
        "name": "Homebridge",
        "username": "xxx.xxx.xxx",
        "port": 51826,
        "pin": "xxx.xxx.xxx"
    },
    "description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
    "ports": {
        "start": 52100,
        "end": 52150,
        "comment": "This section is used to control the range of ports that separate accessory (like camera or television) should be bind to."
    },
    "accessories": [
        {
            "accessory": "DummySwitch",
            "name": "Garage Hub",
            "stateful": true,
            "plugin_map": {
                "plugin_name": "homebridge-dummy",
                "index": 0
            },
            "reverse": false,
            "time": 1000
        },
        {
            "accessory": "DummySwitch",
            "name": "Master Hall",
            "stateful": true,
            "plugin_map": {
                "plugin_name": "homebridge-dummy",
                "index": 0
            },
            "reverse": false,
            "time": 1000
        },
        {
            "accessory": "DummySwitch",
            "name": "Arrival",
            "stateful": true,
            "plugin_map": {
                "plugin_name": "homebridge-dummy",
                "index": 0
            },
            "reverse": false,
            "time": 1000
        },
        {
            "accessory": "DummySwitch",
            "name": "Dogs",
            "stateful": true,
            "plugin_map": {
                "plugin_name": "homebridge-dummy",
                "index": 0
            },
            "reverse": false,
            "time": 1000
        },
        {
            "accessory": "DummySwitch",
            "name": "Guest Hallway Light",
            "stateful": true,
            "plugin_map": {
                "plugin_name": "homebridge-dummy",
                "index": 0
            },
            "reverse": false,
            "time": 1000
        }
    ],
    "platforms": [
        {
            "platform": "Camera-ffmpeg",
            "cameras": [
                {
                    "name": "Garage Camera",
                    "manufacturer": "Wyze, Inc.",
                    "model": "Wyze Cam v2",
                    "serialNumber": "xxxxxxx",
                    "firmwareRevision": "<IP_ADDRESS>",
                    "videoConfig": {
                        "source": "-re -i<EMAIL_ADDRESS>                        "stillImageSource": "-i<EMAIL_ADDRESS>                        "maxStreams": 2,
                        "maxWidth": 1280,
                        "maxHeight": 720,
                        "maxFPS": 12
                    }
                }
            ],
            "plugin_map": {
                "plugin_name": "homebridge-camera-ffmpeg"
            },
            "name": "Camera ffmpeg"
        },
        {
            "name": "Alexa",
            "username": "xxxxxxx"
            "password": "xxxxxxxx",
            "pin": "xxx.xxx.xxx",
            "routines": true,
            "platform": "Alexa",
            "plugin_map": {
                "plugin_name": "homebridge-alexa"
            }
        },
        {
            "platform": "HarmonyHubWebSocket",
            "name": "Living_Room",
            "hubIP": "xxx.xxx.xxx",
            "otherPlatforms": [
                {
                    "name": "Master_Bedroom",
                    "hubIP": "xxx.xxx.xxx",
                    "mainActivity": "Watch TV"
                }
            ],
            "publishAllTVAsExternalAccessory": true,
            "mainActivity": "Watch TV",
            "plugin_map": {
                "plugin_name": "homebridge-harmony"
            },
            "cleanCache": true,
            "publishGeneralVolumeSlider": true,
            "publishGeneralMuteSwitch": true
        },
        {
            "platform": "Ring",
            "hideDoorbellSwitch": true,
            "plugin_map": {
                "plugin_name": "ring"
            },
            "hideUnsupportedServices": true,
            "refreshToken": "eyJhbGciOiJIUzUxMiIsImprdSI6Ii9vYXV0aC9pbnRlcm5hbC9qd2tzIiwia2lkIjoiZGVmYXVsdCIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1ODk2NDQyMTUsInJlZnJlc2hfY2lkIjoicmluZ19vZmZpY2lhbF9hbmRyb2lkIiwicmVmcmVzaF9zY29wZXMiOlsiY2xpZW50Il0sInJlZnJlc2hfdXNlcl9pZCI6MzU0NzY4OSwicm5kIjoiQ3dwQzJZRTQ0NVItMVEiLCJ0eXBlIjoicmVmcmVzaC10b2tlbiJ9.lDOJCzOQAD4xVlrGdneq-2v1jGrpnkOfaErNo1cWt8_c8KULUv--_hIwRNiF67fUeadQqtIbRJlhd1BSKjnUNQ",
            "hideCameraMotionSensor": true,
            "hideInHomeDoorbellSwitch": true
        },
        {
            "platform": "DACP",
            "devices": [
                {
                    "name": "AppleTV",
                    "pairing": "EF2A0AB3912FAB6F",
                    "serviceName": "DA92C525A6D0C7FA",
                    "features": {
                        "no-volume-controls": false,
                        "input-controls": true
                    }
                }
            ],
            "plugin_map": {
                "plugin_name": "homebridge-dacp"
            }
        }
    ]
}

Screenshots:

Environment:

Node.js Version:  10.16.0
NPM Version:  6.13.6
Homebridge Version:  0.4.50
Homebridge Camera FFmpeg Version: 1.1.1
Homebridge Config UI X Plugin Version:
Operating System:  HOOBS

@sdorilas are you having issues with your camera with this plugin or with the ring plugin? Also what version of the ring plugin are you using?

I believe it’s with my camera and this plugin. I’m Running latest version of 8.1.0.
Sent from my iPhone.

On May 16, 2020, at 4:58 PM, Donavan Becker<EMAIL_ADDRESS>wrote:

@sdorilas are you having issues with your camera with this plugin or with the ring plugin? Also what version of the ring plugin are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

The ring plugin after 8.0 went to bridged cameras. I don’t believe HOOBS supports that. Also this wouldn’t be an issue with this plugin.
I would recommend checking out the How to migrate from HOOBS to HomebridgeWiki. The latest homebridge supports bridged cameras and is what homebridge-ring was created to work with.

Thank you!

On May 16, 2020, at 8:29 PM, Donavan Becker<EMAIL_ADDRESS>wrote:
The ring plugin after 8.0 went to bridged cameras. I don’t believe HOOBS supports that. Also this wouldn’t be an issue with this plugin.
I would recommend checking out the How to migrate from HOOBS to Homebridge https://github.com/homebridge/homebridge-raspbian-image/wiki/How-to-migrate-from-HOOBS-to-HomebridgeWiki. The latest homebridge supports bridged cameras and is what homebridge-ring was created to work with.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/homebridge-plugins/homebridge-camera-ffmpeg/issues/503#issuecomment-629724408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEWI62WSXRSSMP35QQGNKMDRR4VWPANCNFSM4NDCFWTA.

Thank you!

Did you get it to work?

I did. I used the link you provided and was able to convert my homebridge system from HOOBS. Al is well!
Sent from my iPhone.

On May 17, 2020, at 7:10 AM, Donavan Becker<EMAIL_ADDRESS>wrote:

Thank you!
Did you get it to work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I did. I used the link you provided and was able to convert my homebridge system from HOOBS. Al is well!

Good to know! I will close this issue. Just as a reminder we have a discord server for Homebridge if you want/need more support.


Crash on MiniControllerFragment click

Hi,
I am using cast framework library version 15.0.1. I have added MiniControllerFragment like this:
  <fragment         android:id="@+id/cast_mini_controller"         class="com.google.android.gms.cast.framework.media.widget.MiniControllerFragment"         android:layout_width="match_parent"         android:layout_height="wrap_content"         android:layout_alignParentBottom="true"         android:visibility="gone"         app:castShowImageThumbnail="true" />
Casting is working properly, but when I click on MiniControllerFragment, app is getting crashed with log mentioned below:
java.lang.NoSuchFieldError: No field ad_skip_text of type I in class Lcom/google/android/gms/cast/framework/R$id; or its superclasses (declaration of 'com.google.android.gms.cast.framework.R$id' appears in /data/app/com.balaji.alt-2/base.apk)         at com.google.android.gms.cast.framework.media.widget.ExpandedControllerActivity.onCreate(Unknown Source)
Can someone please help me with this?

Please file a bug against the Cast SDK: https://issuetracker.google.com/issues?q=componentid:190205 status:open&s=modified_time:desc


MSID: 91002 Version: 3 DOI: 10.1101/2<IP_ADDRESS>6394

MSID: 91002
Version: 3
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6394
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91002
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6394

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91002v3
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6394
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91002/v3/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c19) has a publication-type='other'. Is that correct?


Add/Optimize current documents

Task description:
Add/Optimize current documents. See reasons in #401
Solution:
TODO-LIST:

[ ] How to develop and deploy kmesh from scratch(use kind/ use vmware to utilize openEuler 23.03 enhanced kernel)
[ ] How to check logs(ebpf and user-space), and set/get logger level
[ ] Build Flags about Enhanced Kernel

Who can join or take the task:
The good first issue is intended for first-time contributors to get started on his/her contributor journey.
After a contributor has successfully completed 1-2 good first issue's,
they should be ready to move on to help wanted items, saving the remaining good first issue for other new contributors.
How to join or take the task:
Just reply on the issue with the message /assign in a separate line.
Then, the issue will be assigned to you.
How to ask for help:
If you need help or have questions, please feel free to ask on this issue.
The issue author or other members of the community will guide you through the contribution process.

/assign


Warning: Module 'cross-fetch/polyfill' Not ESM in Angular Build

Description:
During the Angular build process, a warning is issued regarding the module cross-fetch/polyfill being used by node_modules/meilisearch/dist/bundles/meilisearch.esm.js.
Expected Behavior:
The expectation is that meilisearch.esm.js is compliant with ESM standards.
Current Behavior:
Currently, the module cross-fetch/polyfill appears to be either a CommonJS or AMD module, which could potentially cause optimization bailouts and hinder the build performance. The specific warning is as follows:
▲ [WARNING] Module 'cross-fetch/polyfill' used by 'node_modules/meilisearch/dist/bundles/meilisearch.esm.js' is not ESM. CommonJS or AMD dependencies can cause optimization bailouts.
Environment:

instant-meilisearch version: v1.0.0

This is a cross-fetch issue. Doesn't directly support ESM, in fact even uses an older node-fetch because latest is ESM only, at some point might even stop getting security updates (if it didn't already). Not sure how much this impacts tree shaking on browser builds or if it matters at all.
Tangent: As long as we want to support decade old end of life browsers, and fringe use cases, problems like these are unavoidable. If we'd only develop libraries for bundlers and not directly for every use case in existence.

If we'd drop support for EOL Node.js versions, we could drop cross-fetch. Even though it's marked as experimental, undici fetch is built into Node.js 18 (Maintenece version, not even LTS at this point https://github.com/nodejs/Release), it's officially supported, and it has matured enough I'd say.

There are a few issues related to ESM on cross-fetch. These are not getting fixed, I don't think so. Package is not very active, questionably maintained. We have three options:

keep using cross-fetch despite this
switch to axios or something similar (that would mean no support for deno theoretically as it doesn't implement XHR, however I'm not sure how they solve this with node compat)
use proper fetch, since everything in maintenance or LTS supports it at this point (this would mean dropping support for end of life decade old browsers and runtimes)


r2.9 cherry-pick: 2d9de8e62c3 "Insert new blurb for new release notes."

Refer to the original commit: https://github.com/tensorflow/tensorflow/commit/2d9de8e62c30e606e817d1dec9ee1f546dcf19ba

Good, looks like the workflow works. This was just a test.


Add periodic jobs to build and push new images

What would you like to be added:
Add Periodic jobs to build new images
Why is this needed:
Continuous integration to reflect current code changes

/sig test-infra

/area dev-ex

/area maintenance

Complete


docker-machine: 0.9.0 -> 0.10.0

Motivation for this change
docker-machine was updated
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

LGFM