Two typos (trivial, unimportant)

In "Add data source", Step 5:
" [...] and then select then connection when it appears."
>> should be: " [...] and then select the connection when it appears."
In "Identify or change a data source", first paragraph:
"For example, you might need to identify a data source as you update an app that someone else created or you that you created long ago."
>> should be: " [...] an app that someone else created or that you created long ago."

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 171e674b-d11d-ee29-abb3-68ebcdaa7318
Version Independent ID: 155cb306-059f-a86c-9108-54409ea6245b
Content: Add a data connection in a canvas app - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/add-data-connection.md
Service: powerapps
GitHub Login: @lancedMicrosoft
Microsoft Alias: lanced

Fixed. Thanks, @a-zaf!


"Access Tier" should show rehydration status

Version: 1.1.0
Platform: Windows
Architecture: ia32
Build Number: 20180507.1
Commit: bcc8990d
This is a feature request.
Since it can take hours to rehydrate an Archive Tier blob, it would be nice to have the "Access Tier" column to show rehydration status.
For example:
For normal Archive Tier blobs: "Archive"
For blobs being rehydrated to cool: "Archive (Pending to Cool)"
For blobs being rehydrated to hot: "Archive (Pending to Hot)"
The .NET storage API provides this information, haven't checked the Node API but hopefully it does something similar.

This is related to the root cause of #155 which is not a duplicate of #157.

Rehydration status is now available in the properties dialog.


Issue with lua engine...

So basically I don't know how to make lua working with user data and inheritance.
I can however make it working without inheritance is it a problem to have no inheritance ?

Ok, I advanced on this issue. Now I know how I can handle that. However UMod will not narively support inheritance, but you should be able to make your own system.


empty logger output at debug level

Neo4j.Driver Version: 1.6.1
Neo4j Version: 3.4.0
How to reproduce:
    public class Neo4jPersistenceDriver
    {
        public Neo4jPersistenceDriver(string uri, string user, string passwd)
        {
            var loggerFactory = new Microsoft.Extensions.Logging.LoggerFactory();
            loggerFactory.AddProvider(new DebugLoggerProvider((text, logLevel) => logLevel >= Microsoft.Extensions.Logging.LogLevel.Debug));
            logger = loggerFactory.CreateLogger(nameof(Neo4jPersistenceDriver));

            driver = GraphDatabase.Driver(uri, AuthTokens.Basic(user, passwd),
                                          new Config { Logger = new Neo4jPersistenceDriverLogger(Neo4j.Driver.V1.LogLevel.Debug, logger) });
        }
    }
    public class Neo4jPersistenceDriverLogger : Neo4j.Driver.V1.ILogger
    {
        public Neo4jPersistenceDriverLogger(Neo4j.Driver.V1.LogLevel level, Microsoft.Extensions.Logging.ILogger logger)
        {
            this.Level = level;
            this.logger = logger;
        }

        public Neo4j.Driver.V1.LogLevel Level { get; set; }

        private readonly Microsoft.Extensions.Logging.ILogger logger;

        public void Debug(string message, params object[] restOfMessage)
        {
            logger.LogDebug(message, restOfMessage);
        }

        public void Error(string message, Exception cause = null, params object[] restOfMessage)
        {
            logger.LogError(message, cause, restOfMessage);
        }

        public void Info(string message, params object[] restOfMessage)
        {
            logger.LogInformation(message, restOfMessage);
        }

        public void Trace(string message, params object[] restOfMessage)
        {
            logger.LogTrace(message, restOfMessage);
        }
    }

Excepted:
As documented, "When setting log level to Debug, besides all logging recorded by Error and Info, all bolt messages sent between driver and server are also logged in plain text."
Actual:
Neo4jPersistenceDriver:Debug: Trust is established, resuming connection.
Neo4jPersistenceDriver:Debug: ~~ [CONNECT] bolt://localhost:7687/
Neo4jPersistenceDriver:Debug: C: [HANDSHAKE]
Neo4jPersistenceDriver:Debug: S: [HANDSHAKE] 2
Neo4jPersistenceDriver:Debug: C:
Neo4jPersistenceDriver:Debug: S:
Neo4jPersistenceDriver:Debug: C:
Neo4jPersistenceDriver:Debug: C:
Neo4jPersistenceDriver:Debug: S:

Hi @CaulyKan,
The confusion is caused by lack of documentation. Actually, the parameter message passed to logging methods is not a format string and what is expected is to manually concatenate message with contents of restOfMessage.
In DEBUG level, restOfMessage contains object instances that need to be stringified (mostly using ToString() methods).
In TRACE level, restOfMessage contains byte buffers (restOfMessage[0] -> byte[], restOfMessage[1] -> offset, restOfMessage[2] -> count) that needs to be handled appropriately.
It's a bit inconvenient but we're planning a refactor around logging.
Thanks for reporting the issue.

After some inspection into the source I found it quite difficult to get logging working easily. Thank you for your effort on this.
Feel free to close this pr or mark it as a feature.

Hi @CaulyKan
Thanks for bring up this issue. We've improved our logging in 1.7 pre-releases. The new logging used 1.7 series is called IDriverLogger.
Here is an example code that you can use to integrate the new IDriverLogger with Microsoft.Extensions.Logging
using System;
using Microsoft.Extensions.Logging;
using Neo4j.Driver.V1;
using ILogger = Microsoft.Extensions.Logging.ILogger;
using LogLevel = Microsoft.Extensions.Logging.LogLevel;

namespace Neo4j.Driver.Extensions.Logging
{
    public class DriverLogger : IDriverLogger
    {
        private readonly ILogger _delegator;

        public DriverLogger(ILogger delegator)
        {
            _delegator = delegator;
        }

        public void Error(Exception cause, string message, params object[] args)
        {
            _delegator.LogError(default(EventId), cause, message, args);
        }

        public void Warn(Exception cause, string message, params object[] args)
        {
            _delegator.LogWarning(default(EventId), cause, message, args);
        }

        public void Info(string message, params object[] args)
        {
            _delegator.LogInformation(default(EventId), message, args);
        }

        public void Debug(string message, params object[] args)
        {
            // No need to test if debug is enabled or not as we shall not come to here if it is not enabled.
            _delegator.LogDebug(default(EventId), message, args);
        }

        public void Trace(string message, params object[] args)
        {
            // No need to test if trace is enabled or not as we shall not come to here if it is not enabled.
            _delegator.LogTrace(default(EventId), message, args);
        }

        public bool IsTraceEnabled()
        {
            return _delegator.IsEnabled(LogLevel.Trace);
        }

        public bool IsDebugEnabled()
        {
            return _delegator.IsEnabled(LogLevel.Debug);
        }
    }
}

Pls let us know if you have any feedback about the new logging we added for 1.7.
Cheers,
Zhen

@CaulyKan The 1.7 with the new logging is release.

Thank you very much!


Firebase Deployment

Within the firebase.json. The public is set to "target". When I deploy it doesn't appear to find this path or directory. This is a recent issue. I've deployed fine before. Now all of the sudden it can't find the directory or path. Are you still able to deploy or are you having this issue ?

Also npm run build fails even when I started from scratch. Npm start works as well as firebase serve.

Hi @KillerBee05 – I was able to clone, build, and deploy. What kind of errors are you seeing?

Thank you for taking your time to check. Within the Command Prompt I get cannot find public directory. So it can't find the specified "target" within the firebase.json. I change 'target' to 'src' and it deploys just fine, just can't see anything on the page. I change it back to target and I get this error. I tried cloning your repo and starting over, and I ran into the same issue. I updated my firebase tools recently. Im not sure if thats the issue though.

You mentioned that the build was failing as well — what errors are you seeing?
target directory is created by npm run build, so if the build is failing then the directory and build artifacts are probably not being generated.

Oh okay. This is what im getting when I run the build.

Looks like eslint may have found some errors. Try running npm run lint and see if there are any problems reported by eslint.
An error would look something like this:
$ npm run lint

><EMAIL_ADDRESS>lint /Users/rpark/todo-react-redux
> eslint -c .eslintrc.yml *.js src server

/Users/rpark/todo-react-redux/karma.conf.js
  19:5  error  Parsing error: Unexpected token, expected ,

✖ 1 problem (1 error, 0 warnings)

Yeah that was it, holy cow that was a pain to clear out some these errors.

I ended up having to comment these lines out cause I don't know what it wants. I've tried everything to get them to go away. Any pointers to get it Lint to be satisfied?

Have a look at this: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prefer-stateless-function.md

Word, thanks for the help.


fix(CI): unpin mkdocs and plugin versions

Github workflows aren't passing because of an error in mkdocs, one of the plugins requires mkdocs >= 1.4, we're pinning at 1.2.3 I unpinned mkdocs and unpinned all plugins so we can stay up to date.
Tested locally and seems like the docs are working

I will close this for now as it seems the issue got fixed in #196. Please, re-open if the issue arises again.


how to use or add data augmentation while training?

thank you for your framework.
I would like do some data augmentation such as random rotate, random flip, random crop while train the model, how can I do this.

You can just modify ImageTransform or add some extra transforms like what SSD does.

thanks for your response, I get it.

You can just modify ImageTransform or add some extra transforms like what SSD does.


Again - Provider produced inconsistent final plan

I have issues
With a new module version 6.0 we still have an issue with:
Error: Provider produced inconsistent final plan
This issue previously has been address in: https://github.com/terraform-providers/terraform-provider-aws/issues/9882 and https://github.com/terraform-aws-modules/terraform-aws-eks/issues/481 but in version 6.0 of Module it back again
What is the current behavior?
Error: Provider produced inconsistent final plan

When expanding the plan for
module.eks.aws_autoscaling_group.workers_launch_template[0] to include new
values learned so far during apply, provider "aws" produced an invalid new
value for .initial_lifecycle_hook: planned set element
cty.ObjectVal(map[string]cty.Value{"default_result":cty.UnknownVal(cty.String),
"heartbeat_timeout":cty.UnknownVal(cty.Number),
"lifecycle_transition":cty.UnknownVal(cty.String),
"name":cty.UnknownVal(cty.String),
"notification_metadata":cty.UnknownVal(cty.String),
"notification_target_arn":cty.UnknownVal(cty.String),
"role_arn":cty.UnknownVal(cty.String)}) does not correlate with any element in
actual.

If this is a bug, how to reproduce? Please include a code sample if relevant.
  worker_groups_launch_template = [
    {
      instance_type        = "c5.large"
      key_name             = aws_key_pair.worker_management.key_name
      subnets              = var.subnet_ids
      asg_desired_capacity = var.minimal_cluster_size
      asg_min_size         = var.minimal_cluster_size
      asg_max_size         = "5"
      pre_userdata = <<EOFT
     }
  ]

module "eks" {
  source                               = "terraform-aws-modules/eks/aws"
  cluster_name = local.cluster_name
  cluster_version = var.cluster_version
  subnets         = concat(var.subnet_ids, var.underlay_subnet_ids)
  tags            = local.tags
  vpc_id          = var.vpc_id
  worker_groups_launch_template        = local.worker_groups_launch_template
  worker_additional_security_group_ids = [aws_security_group.all_worker_mgmt.id]
  map_roles                            = var.map_roles
  map_users                            = var.map_users
  map_accounts                         = var.map_accounts
  config_output_path                   = "./generated/"
  cluster_endpoint_private_access      = var.private
  permissions_boundary                 = var.private ? <ARN> : ""

}

What's the expected behavior?
With empty list (var.input.asg_initial_lifecycle_hooks), the dynamic block initial_lifecycle_hook must not be created and terraform should finish without panic.
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version: 6.0.0
Terraform version:

Terraform v0.12.6
+ provider.aws v2.29.0
+ provider.local v1.3.0
+ provider.null v2.1.2
+ provider.random v2.2.0
+ provider.template v2.1.2

I found issue, it was previously created by @barryib in 489 and somehow missed in version 6.x. So i created diff (cant create PR - no permissions). Can these changes be added to current code.
diff --git a/workers.tf b/workers.tf
index 45db1e4..f89511b 100644
--- a/workers.tf
+++ b/workers.tf
@@ -75,7 +75,7 @@ resource "aws_autoscaling_group" "workers" {
   )

   dynamic "initial_lifecycle_hook" {
-    for_each = lookup(var.worker_groups[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"])
+    for_each = length(lookup(var.worker_groups_launch_template[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"])) > 0 ? lookup(var.worker_groups_launch_template[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"]) : []
     content {
       name                    = lookup(initial_lifecycle_hook.value, "name", null)
       lifecycle_transition    = lookup(initial_lifecycle_hook.value, "lifecycle_transition", null)
diff --git a/workers_launch_template.tf b/workers_launch_template.tf
index 258d536..320b62f 100644
--- a/workers_launch_template.tf
+++ b/workers_launch_template.tf
@@ -151,7 +151,7 @@ resource "aws_autoscaling_group" "workers_launch_template" {
   }

   dynamic "initial_lifecycle_hook" {
-    for_each = lookup(var.worker_groups_launch_template[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"])
+    for_each = length(lookup(var.worker_groups_launch_template[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"])) > 0 ? lookup(var.worker_groups_launch_template[count.index], "asg_initial_lifecycle_hooks", local.workers_group_defaults["asg_initial_lifecycle_hooks"]) : []
     content {
       name                    = lookup(initial_lifecycle_hook.value, "name", null)
       lifecycle_transition    = lookup(initial_lifecycle_hook.value, "lifecycle_transition", null)

Thanks in advance

@timota weird. i'm gonna have a look.

maybe this comes from

I have the same issue. key_name is supposed to be optional. eks hosts dont need a key to be brought up.

How it related to this block dynamic "initial_lifecycle_hook"  ?

because of https://github.com/terraform-aws-modules/terraform-aws-eks/issues/481#issuecomment-524817067

The issue: if a variable or local contains an unknown value then the whole variable/local is tagged as unknown in the diff state. Fine for simple variables but really annoying when dealing with collections. This makes terraform do weird things in dynamic blocks. It assumes it can't use anything from the collection until apply time. When it turns out that the referred to list is in fact empty and.. oops.

but this doesnt explain why after fix #483 - everything starts working.
Anyway - let me try apply with vanilla module without key.

could you tell me the vanilla module version which was working? I can use the same. I am using the folloiwing definition and it still giving error no key_name here
module "eks" {
source                          = "terraform-aws-modules/eks/aws"
version                         = "6.0.0"
cluster_name                    = var.eks_cluster.name
subnets                         = concat(module.vpc.public_subnets,module.vpc.private_subnets)
vpc_id                          = module.vpc.vpc_id
cluster_create_security_group   = true
cluster_endpoint_private_access = true
cluster_log_retention_in_days   = 7
write_kubeconfig                = true
worker_groups = [
{
instance_type               = var.eks_cluster.instance_type
asg_max_size                = var.eks_cluster.autoscaling_group_max_size
tags                        = [ for key,value in var.tags: {
key                       = "${key}"
value                     = "${value}"
propagate_at_launch       = true
}]
}
]
tags                            = var.tags
}

The  key_name is mandatory. For tests, can you please create your key before and apply your eks module with the key created previously.
I'm gonna have a look also on a new cluster with your configuration.

`
Error: Provider produced inconsistent final plan
When expanding the plan for module.eks.aws_autoscaling_group.workers[0] to
include new values learned so far during apply, provider "aws" produced an
invalid new value for .initial_lifecycle_hook: planned set element
cty.ObjectVal(map[string]cty.Value{"default_result":cty.UnknownVal(cty.String),
"heartbeat_timeout":cty.UnknownVal(cty.Number),
"lifecycle_transition":cty.UnknownVal(cty.String),
"name":cty.UnknownVal(cty.String),
"notification_metadata":cty.UnknownVal(cty.String),
"notification_target_arn":cty.UnknownVal(cty.String),
"role_arn":cty.UnknownVal(cty.String)}) does not correlate with any element in
actual.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
with my configmodule "eks" {
source                          = "terraform-aws-modules/eks/aws"
version                         = "6.0.0"
cluster_name                    = var.eks_cluster.name
subnets                         = concat(module.vpc.public_subnets,module.vpc.private_subnets)
vpc_id                          = module.vpc.vpc_id
cluster_create_security_group   = true
cluster_endpoint_private_access = true
cluster_log_retention_in_days   = 7
write_kubeconfig                = true
worker_groups = [
{
instance_type               = var.eks_cluster.instance_type
asg_max_size                = var.eks_cluster.autoscaling_group_max_size
tags                        = [ for key,value in var.tags: {
key                       = "${key}"
value                     = "${value}"
propagate_at_launch       = true
}]
}
]
tags                            = var.tags
}
`

Also according to module documentation only mandatory options are
cluster_name
subnets
vpc_id

Also according to module documentation only mandatory options are
cluster_name
subnets
vpc_id

Maybe the default should be null and not ""

 # module.eks.aws_autoscaling_group.workers[0] will be created
  + resource "aws_autoscaling_group" "workers" {
      + arn                       = (known after apply)
      + availability_zones        = (known after apply)
      + default_cooldown          = (known after apply)
      + desired_capacity          = (known after apply)
      + enabled_metrics           = (known after apply)
      + force_delete              = (known after apply)
      + health_check_grace_period = 300
      + health_check_type         = (known after apply)
      + id                        = (known after apply)
      + launch_configuration      = (known after apply)
      + load_balancers            = (known after apply)
      + max_size                  = 10
      + metrics_granularity       = "1Minute"
      + min_size                  = (known after apply)
      + name                      = (known after apply)
      + name_prefix               = (known after apply)
      + placement_group           = (known after apply)
      + protect_from_scale_in     = (known after apply)
      + service_linked_role_arn   = (known after apply)
      + suspended_processes       = (known after apply)
      + tags                      = [
          + {
              + "key"                 = "Name"
              + "propagate_at_launch" = "true"
              + "value"               = "project-k8s-cluster-0-eks_asg"
            },
          + {
              + "key"                 = "kubernetes.io/cluster/project-k8s-cluster"
              + "propagate_at_launch" = "true"
              + "value"               = "owned"
            },
          + {
              + "key"                 = "k8s.io/cluster/project-k8s-cluster"
              + "propagate_at_launch" = "true"
              + "value"               = "owned"
            },
          + (known after apply),
          + {
              + "key"                 = "k8s.io/cluster-autoscaler/project-k8s-cluster"
              + "propagate_at_launch" = "false"
              + "value"               = "project-k8s-cluster"
            },
          + (known after apply),
          + {
              + "key"                 = "environment"
              + "propagate_at_launch" = "true"
              + "value"               = "qa"
            },
          + {
              + "key"                 = "environment"
              + "propagate_at_launch" = "true"
              + "value"               = "qa"
            },
        ]
      + target_group_arns         = (known after apply)
      + termination_policies      = (known after apply)
      + vpc_zone_identifier       = (known after apply)
      + wait_for_capacity_timeout = "10m"

      + initial_lifecycle_hook {
          + default_result          = (known after apply)
          + heartbeat_timeout       = (known after apply)
          + lifecycle_transition    = (known after apply)
          + name                    = (known after apply)
          + notification_metadata   = (known after apply)
          + notification_target_arn = (known after apply)
          + role_arn                = (known after apply)
        }
    }

Just a note with 6.0.0 I'm hitting this every time I apply.  2nd time it gets past it.

Same here, terraform-aws-eks version v6.0.1. Have to rollback to v5.1.0.
When expanding the plan for
module.eks.aws_autoscaling_group.workers_launch_template[1] to include new
values learned so far during apply, provider "aws" produced an invalid new
value for .initial_lifecycle_hook: planned set element
cty.ObjectVal(map[string]cty.Value{"default_result":cty.UnknownVal(cty.String),
"heartbeat_timeout":cty.UnknownVal(cty.Number),
"lifecycle_transition":cty.UnknownVal(cty.String),
"name":cty.UnknownVal(cty.String),
"notification_metadata":cty.UnknownVal(cty.String),
"notification_target_arn":cty.UnknownVal(cty.String),
"role_arn":cty.UnknownVal(cty.String)}) does not correlate with any element in
actual.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Ok, i have tested with "vanilla" module version 6.0.1 and with key_name explicitly defined:
TF plan
 # module.eks.aws_launch_template.workers_launch_template[0] will be created
  + resource "aws_launch_template" "workers_launch_template" {
      + arn             = (known after apply)
      + default_version = (known after apply)
      + ebs_optimized   = (known after apply)
      + id              = (known after apply)
      + image_id        = (known after apply)
      + instance_type   = (known after apply)
      + key_name        = "ansible"
      + latest_version  = (known after apply)
      + name            = (known after apply)
      + name_prefix     = (known after apply)
      + tags            = {
          + "Environment" = "test"
          + "Workspace"   = "default"
        }
      + user_data       = (known after apply)

      + block_device_mappings {
          + device_name = (known after apply)

          + ebs {
              + delete_on_termination = "true"
              + encrypted             = (known after apply)
              + iops                  = (known after apply)
              + kms_key_id            = (known after apply)
              + volume_size           = (known after apply)
              + volume_type           = (known after apply)
            }
        }

      + credit_specification {
          + cpu_credits = (known after apply)
        }

      + iam_instance_profile {
          + name = (known after apply)
        }

      + instance_market_options {
          + market_type = (known after apply)
        }

      + monitoring {
          + enabled = (known after apply)
        }

      + network_interfaces {
          + associate_public_ip_address = (known after apply)
          + delete_on_termination       = (known after apply)
          + security_groups             = (known after apply)
        }

      + placement {
          + group_name = (known after apply)
          + tenancy    = (known after apply)
        }

      + tag_specifications {
          + resource_type = "volume"
          + tags          = (known after apply)
        }
    }

where key_name        = "ansible"
and got the same error
Error: Provider produced inconsistent final plan

When expanding the plan for
module.eks.aws_autoscaling_group.workers_launch_template[0] to include new
values learned so far during apply, provider "aws" produced an invalid new
value for .initial_lifecycle_hook: planned set element
cty.ObjectVal(map[string]cty.Value{"default_result":cty.UnknownVal(cty.String),
"heartbeat_timeout":cty.UnknownVal(cty.Number),
"lifecycle_transition":cty.UnknownVal(cty.String),
"name":cty.UnknownVal(cty.String),
"notification_metadata":cty.UnknownVal(cty.String),
"notification_target_arn":cty.UnknownVal(cty.String),
"role_arn":cty.UnknownVal(cty.String)}) does not correlate with any element in
actual.

second run - i defined key inside module, just in case
  # key_name = lookup(
  #   var.worker_groups_launch_template[count.index],
  #   "key_name",
  #   local.workers_group_defaults["key_name"],
  # )

  key_name = "ansible"

Result the same.
Now, i guess this means that issue not with local key at all.

Thanks all for your feedbacks. The issue is not about local keys, but the unknown (known after apply) not handled correctly by the AWS provider or Terraform core for initial_lifecycle_hooks.
There are already issues on the aws provider or terraform core repository for inconstant plans :

https://github.com/terraform-providers/terraform-provider-aws/issues/9882
https://github.com/terraform-providers/terraform-provider-aws/issues/10088
https://github.com/terraform-providers/terraform-provider-aws/issues/10107
https://github.com/hashicorp/terraform/issues/22409

More info on inaccurate plans https://www.terraform.io/docs/extend/terraform-0.12-compatibility.html#inaccurate-plans
To workaround on this, I'm going to add new variable asg_create_initial_lifecycle_hooks to use as switch for lifecycle hooks. And let users who want to use lifecycle hooks to provide consistent values across Terraform plans.
I'm going to have a look on the AWS provider side if a customization diff will help to solve this issue.

@timota @marcecaro @davisford @manpreetsnehra Is this PR work for you https://github.com/terraform-aws-modules/terraform-aws-eks/pull/532

@barryib I was having same issue when I just picked one example and ran it. I can confirm this patch in #532 solved it.

@barryib I was also having the same issue and your PR works as intended. :+1:

@poush @mfin thanks for your feedbacks.
closing since #532 is now merged. Feel free to re-open this issue if the provided solution doesn't work for you.

@barryib will there be a 6.0.2 release soon?

Thanks @barryib,  Same question here. Any ETA for the release with the fix?

Yes... In the next couple of days.

This is causing ongoing issues for us, is there any update on when it is likely to be fixed?

This fix has been released in v6.0.2 https://github.com/terraform-aws-modules/terraform-aws-eks/pull/553

The issue continues , the first time it triggers:
Provider produced inconsistent final plan

When expanding the plan for
module.eks.aws_autoscaling_group.workers_launch_template[0] to include new
values learned so far during apply, provider "aws" produced an invalid new
value for .initial_lifecycle_hook: planned set element
cty.ObjectVal(map[string]cty.Value{"default_result":cty.UnknownVal(cty.String),
"heartbeat_timeout":cty.UnknownVal(cty.Number),
"lifecycle_transition":cty.UnknownVal(cty.String),
"name":cty.UnknownVal(cty.String),
"notification_metadata":cty.UnknownVal(cty.String),
"notification_target_arn":cty.UnknownVal(cty.String),
"role_arn":cty.UnknownVal(cty.String)}) does not correlate with any element in
actual.

This error gets triggered for any single launch_template. But if y do an apply again then it works fine.
It seem like a race condition or something similar.
Some additional information:
Downloading terraform-aws-modules/eks/aws 6.0.2 for eks...
- eks in .terraform/modules/eks/terraform-aws-modules-terraform-aws-eks-1be1a02
Downloading terraform-aws-modules/vpc/aws 2.17.0 for vpc...
- vpc in .terraform/modules/vpc/terraform-aws-modules-terraform-aws-vpc-5358041

- Checking for available provider plugins...
- Downloading plugin for provider "template" (hashicorp/template) 2.1.2...
- Downloading plugin for provider "local" (hashicorp/local) 1.4.0...
- Downloading plugin for provider "null" (hashicorp/null) 2.1.2...
- Downloading plugin for provider "random" (hashicorp/random) 2.2.1...
- Downloading plugin for provider "aws" (hashicorp/aws) 2.31.0...

Any clue if there is a workaround?

@marcecaro Can you please share your configuration and plan output ?

@barryib I can confirm the issue is still happening.

Also can confirm that the issue still present.

@barryib Did you get a chance to look into it ?

Not yet. I have to figure out why #532 is not working as expected for everyone.

@aLekSer @timota can you please share your configuration ? I would like to reproduce this locally.

@barryib  I can share part of it, I think you will be able to figureout the variables meaning  (I am extracting this form other tools that uses terraform, that is the reason that i don't have access to all the files). I hope you can reproduce the issue with this configuration.
locals {
  worker_groups = [
    ## three autoscale groups  for regular instance type
    {
      instance_type         = "${var.node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 0)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.protect_from_scale_in))}"
      root_volume_type      = "${var.root_volume_type}"
      root_volume_size      = "${var.root_volume_size}"
      root_encrypted        = "${tobool(lower(var.root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 1)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.protect_from_scale_in))}"
      root_volume_type      = "${var.root_volume_type}"
      root_volume_size      = "${var.root_volume_size}"
      root_encrypted        = "${tobool(lower(var.root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 2)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.protect_from_scale_in))}"
      root_volume_type      = "${var.root_volume_type}"
      root_volume_size      = "${var.root_volume_size}"
      root_encrypted        = "${tobool(lower(var.root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    ## three autoscale groups  for high cpu instance type
    {
      instance_type         = "${var.high_cpu_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 0)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_root_volume_type}"
      root_volume_size      = "${var.high_cpu_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_cpu_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 1)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_root_volume_type}"
      root_volume_size      = "${var.high_cpu_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_cpu_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 2)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_root_volume_type}"
      root_volume_size      = "${var.high_cpu_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    ## three autoscale groups  for high memory instance type
    {
      instance_type         = "${var.high_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 0)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_memory_root_volume_type}"
      root_volume_size      = "${var.high_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 1)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_memory_root_volume_type}"
      root_volume_size      = "${var.high_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 2)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_memory_root_volume_type}"
      root_volume_size      = "${var.high_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    ## three autoscale groups  for high cpu and memory instance type
    {
      instance_type         = "${var.high_cpu_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 0)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_memory_root_volume_type}"
      root_volume_size      = "${var.high_cpu_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_cpu_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 1)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_memory_root_volume_type}"
      root_volume_size      = "${var.high_cpu_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
    {
      instance_type         = "${var.high_cpu_memory_node_instance_type}"
      subnets               = ["${element(module.vpc.private_subnets, 2)}"]
      asg_desired_capacity  = "${max(ceil(tonumber(var.high_cpu_memory_desired_machines) / 3), 0)}"
      asg_max_size          = "${max(ceil(tonumber(var.high_cpu_memory_max_machines) / 3), 0)}"
      asg_min_size          = "${max(ceil(tonumber(var.high_cpu_memory_mim_machines) / 3), 0)}"
      autoscaling_enabled   = true
      protect_from_scale_in = "${tobool(lower(var.high_cpu_memory_protect_from_scale_in))}"
      root_volume_type      = "${var.high_cpu_memory_root_volume_type}"
      root_volume_size      = "${var.high_cpu_memory_root_volume_size}"
      root_encrypted        = "${tobool(lower(var.high_cpu_memory_root_volume_encrypted))}"
      root_kms_key_id       = "${data.aws_kms_key.default.arn}"
    },
  ]
}

module "eks" {
  source                        = "terraform-aws-modules/eks/aws"
  cluster_name                  = "${var.namespace}"
  subnets                       = "${concat(module.vpc.private_subnets, module.vpc.public_subnets)}"
  vpc_id                        = "${module.vpc.vpc_id}"
  worker_sg_ingress_from_port   = "0"
  workers_additional_policies   = ["${aws_iam_policy.eks_alb_policy.arn}"] ## Policy for ALB management
  worker_groups_launch_template = [
    for asg in local.worker_groups :
    asg
    if asg.instance_type != "none" && asg.instance_type != ""
  ]

  worker_create_initial_lifecycle_hooks = false

  tags = {
    "KubernetesCluster"                      = "${var.namespace}"
    "Start_Stop"                             = "NO"
    "kubernetes.io/cluster/${var.namespace}" = "owned"
  }
}

@barryib Can you advice on what can we change to make it work and avoid this issue ?

I was getting a similar error message, except that my inconsistancy was attached to an aws_lambda_function that had a source_code_hash = filebase64sha256(local.lambda_zipfilename) directive.
Part of my terraform script was a local-exec provisioner to create a lambda-deployment.
resource "null_resource" "pip_requirements" {
  provisioner "local-exec" {
    command = "rm -rf venv && python3 -m venv ./ && . ./bin/activate && python3 -m pip install -r requirements.txt"
    working_dir = local.lambda_sourcepath
  }
}

So it makes a certain amount of sense that the return value of filebase64sha256 would be one value at the beginning of the run, and a completely different value later, after my zip file got updated.
I was able to get it to work by running terraform plan -out plan.tfplan followed by terraform apply -auto-approve plan.tfplan, instead of just terraform apply without doing a plan first.
Is there a better way I could have handled it?

@timbaileyjones this repo is for an EKS module. Please find a general terraform support forum for your issue.

I have an issue with inconsistent plan as well, but am unsure if this is the same reason as being discussed here. Potentially I am doing wrong, if not I am curious for workarounds.
With following configuration:
module "eks" {
  source                    = "terraform-aws-modules/eks/aws"
  cluster_name              = var.cluster_name
  cluster_version           = "1.16"
  cluster_enabled_log_types = ["audit", "authenticator"]
  subnets                   = module.vpc.private_subnets
  vpc_id                    = module.vpc.vpc_id
  enable_irsa               = true
  map_users                 = var.eks_map_users
  worker_groups = [
    {
      name          = "worker-group-1"
      instance_type = var.eks_node_ec2_type
      # changes to asg sizing will have no effect, see here:
      # https://github.com/terraform-aws-modules/terraform-aws-eks/blob/6c42d23c23d501c62bac6d8f0d9039f7c46a8307/docs/faq.md#why-does-changing-the-worker-groups-desired-count-not-do-anything
      asg_desired_capacity = 2
      asg_min_size         = 2
      asg_max_size         = 4
      additional_security_group_ids = [
        aws_security_group.worker_group_mgmt_one.id
      ]
      tags = [
        {
          key                 = "k8s.io/cluster-autoscaler/enabled"
          propagate_at_launch = "false"
          value               = "true"
        },
        {
          key                 = "k8s.io/cluster-autoscaler/${var.cluster_name}"
          propagate_at_launch = "false"
          value               = "true"
        }
      ]
    }
  ]
  worker_additional_security_group_ids = [
    aws_security_group.all_worker_mgmt.id
  ]
  tags = {
    Cluster     = var.cluster_name
    Environment = var.environment
    Terraform   = "true"
  }
}

I am getting on each run differences in tag ordering. I am using latest EKS module version v12.

Click to expand for details
Terraform will perform the following actions:

  # module.eks.aws_autoscaling_group.workers[0] will be updated in-place
  ~ resource "aws_autoscaling_group" "workers" {
        arn                       = "arn:aws:autoscaling:eu-west-1:MYACCOUNT:autoScalingGroup:f99f4afd-e8c2-4219-a7cf-0b7de7df061a:autoScalingGroupName/cf-tf-eks-worker-group-120200508085635599200000001"
        availability_zones        = [
            "eu-west-1a",
            "eu-west-1b",
            "eu-west-1c",
        ]
        default_cooldown          = 300
        desired_capacity          = 2
        enabled_metrics           = []
        force_delete              = false
        health_check_grace_period = 300
        health_check_type         = "EC2"
        id                        = "cf-tf-eks-worker-group-120200508085635599200000001"
        launch_configuration      = "cf-tf-eks-worker-group-120200512081006828300000001"
        load_balancers            = []
        max_instance_lifetime     = 0
        max_size                  = 4
        metrics_granularity       = "1Minute"
        min_size                  = 2
        name                      = "cf-tf-eks-worker-group-120200508085635599200000001"
        name_prefix               = "cf-tf-eks-worker-group-1"
        protect_from_scale_in     = false
        service_linked_role_arn   = "arn:aws:iam::MYACCOUNT:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling"
        suspended_processes       = [
            "AZRebalance",
        ]
      ~ tags                      = [
          + {
              + "key"                 = "Name"
              + "propagate_at_launch" = "true"
              + "value"               = "cf-tf-eks-worker-group-1-eks_asg"
            },
          + {
              + "key"                 = "kubernetes.io/cluster/cf-tf-eks"
              + "propagate_at_launch" = "true"
              + "value"               = "owned"
            },
          + {
              + "key"                 = "k8s.io/cluster/cf-tf-eks"
              + "propagate_at_launch" = "true"
              + "value"               = "owned"
            },
            {
                "key"                 = "Cluster"
                "propagate_at_launch" = "true"
                "value"               = "cf-tf-eks"
            },
            {
                "key"                 = "Environment"
                "propagate_at_launch" = "true"
                "value"               = "test"
            },
          - {
              - "key"                 = "Name"
              - "propagate_at_launch" = "true"
              - "value"               = "cf-tf-eks-worker-group-1-eks_asg"
            },
            {
                "key"                 = "Terraform"
                "propagate_at_launch" = "true"
                "value"               = "true"
            },
          - {
              - "key"                 = "k8s.io/cluster-autoscaler/cf-tf-eks"
              - "propagate_at_launch" = "false"
              - "value"               = "true"
            },
            {
                "key"                 = "k8s.io/cluster-autoscaler/enabled"
                "propagate_at_launch" = "false"
                "value"               = "true"
            },
          - {
              - "key"                 = "k8s.io/cluster/cf-tf-eks"
              - "propagate_at_launch" = "true"
              - "value"               = "owned"
            },
          - {
              - "key"                 = "kubernetes.io/cluster/cf-tf-eks"
              - "propagate_at_launch" = "true"
              - "value"               = "owned"
            },
          + {
              + "key"                 = "k8s.io/cluster-autoscaler/cf-tf-eks"
              + "propagate_at_launch" = "false"
              + "value"               = "true"
            },
        ]
        target_group_arns         = []
        termination_policies      = []
        vpc_zone_identifier       = [
            "subnet-053e8b0b5c54b3316",
            "subnet-090ae11ad7538c381",
            "subnet-0bd52ba6f6dbb034b",
        ]
        wait_for_capacity_timeout = "10m"
    }

And in debug output:
2020/05/28 07:25:18 [WARN] Provider "registry.terraform.io/-/aws" produced an invalid plan for aws_security_group.worker_group_mgmt_one, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .ingress: planned value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_blocks":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8")}), "description":cty.StringVal(""), "from_port":cty.NumberIntVal(22), "ipv6_cidr_blocks":cty.ListValEmpty(cty.String), "prefix_list_ids":cty.ListValEmpty(cty.String), "protocol":cty.Stri
ngVal("tcp"), "security_groups":cty.SetValEmpty(cty.String), "self":cty.False, "to_port":cty.NumberIntVal(22)})}) does not match config value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_blocks":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8")}), "description":cty.NullVal(cty.String), "from_port":cty.NumberIntVal(22),
"ipv6_cidr_blocks":cty.NullVal(cty.List(cty.String)), "prefix_list_ids":cty.NullVal(cty.List(cty.String)), "protocol":cty.StringVal("tcp"), "security_groups":cty.NullVal(cty.Set(cty.String)), "self":cty.NullVal(cty.Bool), "to_port":cty.NumberIntVal(22)})}) nor prior value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_block
s":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8")}), "description":cty.StringVal(""), "from_port":cty.NumberIntVal(22), "ipv6_cidr_blocks":cty.ListValEmpty(cty.String), "prefix_list_ids":cty.ListValEmpty(cty.String), "protocol":cty.StringVal("tcp"), "security_groups":cty.SetValEmpty(cty.String), "self":cty.False, "to_port":cty.NumberIn
tVal(22)})})
2020/05/28 07:25:18 [WARN] Provider "registry.terraform.io/-/aws" produced an invalid plan for aws_security_group.all_worker_mgmt, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .ingress: planned value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_blocks":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8"), cty.StringVal("<IP_ADDRESS>/12"), cty.StringVal("<IP_ADDRESS>/16")}), "description":cty.StringVal(""), "from_port":cty.NumberIntVal(22), "ipv6_cidr_blocks":cty.ListValEmpty(cty.String), "p
refix_list_ids":cty.ListValEmpty(cty.String), "protocol":cty.StringVal("tcp"), "security_groups":cty.SetValEmpty(cty.String), "self":cty.False, "to_port":cty.NumberIntVal(22)})}) does not match config value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_blocks":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8"), cty.String
Val("<IP_ADDRESS>/12"), cty.StringVal("<IP_ADDRESS>/16")}), "description":cty.NullVal(cty.String), "from_port":cty.NumberIntVal(22), "ipv6_cidr_blocks":cty.NullVal(cty.List(cty.String)), "prefix_list_ids":cty.NullVal(cty.List(cty.String)), "protocol":cty.StringVal("tcp"), "security_groups":cty.NullVal(cty.Set(cty.String)), "self":cty.NullVal(c
ty.Bool), "to_port":cty.NumberIntVal(22)})}) nor prior value cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cidr_blocks":cty.ListVal([]cty.Value{cty.StringVal("<IP_ADDRESS>/8"), cty.StringVal("<IP_ADDRESS>/12"), cty.StringVal("<IP_ADDRESS>/16")}), "description":cty.StringVal(""), "from_port":cty.NumberIntVal(22), "ipv6_cidr_blocks":cty
.ListValEmpty(cty.String), "prefix_list_ids":cty.ListValEmpty(cty.String), "protocol":cty.StringVal("tcp"), "security_groups":cty.SetValEmpty(cty.String), "self":cty.False, "to_port":cty.NumberIntVal(22)})})

I am currently having this problem:

provider 2.70.0
eks module 12.2.0
terraform 0.13.0

Everything was already applied with no changes in plan. Then I needed to add this:
worker_additional_security_group_ids = [module.eks_nodes_custom_security_group.this_security_group_id]

And ran into:
Error: Provider produced inconsistent final plan

When expanding the plan for module.eks.random_pet.workers_launch_template[0]
to include new values learned so far during apply, provider
"registry.terraform.io/hashicorp/random" changed the planned action from
CreateThenDelete to DeleteThenCreate.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for module.eks.random_pet.workers_launch_template[2]
to include new values learned so far during apply, provider
"registry.terraform.io/hashicorp/random" changed the planned action from
CreateThenDelete to DeleteThenCreate.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Provider produced inconsistent final plan

When expanding the plan for module.eks.random_pet.workers_launch_template[1]
to include new values learned so far during apply, provider
"registry.terraform.io/hashicorp/random" changed the planned action from
CreateThenDelete to DeleteThenCreate.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

After a couple of re-tries this is the only thing remaining in diff:
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+/- create replacement and then destroy

Terraform will perform the following actions:

  # module.eks.random_pet.workers_launch_template[0] must be replaced
+/- resource "random_pet" "workers_launch_template" {
      ~ id        = "creative-roughy" -> (known after apply)
      ~ keepers   = { # forces replacement
          ~ "lt_name" = "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-03ed27ff8fe41e75d20200812074859681300000021-1" -> "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-03ed27ff8fe41e75d20200812074859681300000021-2"
        }
        length    = 2
        separator = "-"
    }

  # module.eks.random_pet.workers_launch_template[1] must be replaced
+/- resource "random_pet" "workers_launch_template" {
      ~ id        = "liked-egret" -> (known after apply)
      ~ keepers   = { # forces replacement
          ~ "lt_name" = "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-0dd51036e98e5befa2020081207485967580000001f-1" -> "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-0dd51036e98e5befa2020081207485967580000001f-2"
        }
        length    = 2
        separator = "-"
    }

  # module.eks.random_pet.workers_launch_template[2] must be replaced
+/- resource "random_pet" "workers_launch_template" {
      ~ id        = "present-buzzard" -> (known after apply)
      ~ keepers   = { # forces replacement
          ~ "lt_name" = "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-039f7a3983b29c6a620200812074859682800000023-1" -> "us-prod-eks-cluster-us-prod-eks-worker-spot-subnet-039f7a3983b29c6a620200812074859682800000023-2"
        }
        length    = 2
        separator = "-"
    }

Because I use worker_groups_launch_template only for spot instances and I could live without them for a while, the only option was to comment it out, apply, add it back, apply again.
Plan is consistent now.

Same environment like @lebenitza

eks module 12.2.0
terraform 0.13.0

Same error.

Error: Provider produced inconsistent final plan

When expanding the plan for module.eks.random_pet.workers_launch_template[1]
to include new values learned so far during apply, provider
"registry.terraform.io/hashicorp/random" changed the planned action from
CreateThenDelete to DeleteThenCreate.

I was able to make this error disappear by removing TF state (instead of comment out->apply-> add back ->apply).
terraform state rm module.eks.aws_launch_template.workers_launch_template[0] \
      module.eks.aws_launch_template.workers_launch_template[1] \
     module.eks.random_pet.workers_launch_template[0] \
     module.eks.random_pet.workers_launch_template[1]

# if you want to know how i get the full name of the same, you can do this :
terraform state list | grep launch

Note that when you terraform apply after this removal, expect that all autoscaling groups will be replaced.
I don't have issue because i have 5 groups and each group has set of machines.
This means if a one or two group(s) is deleted during terraform apply, the cluster will not be throttled

Estou com o mesmo problema
2020/10/16 11:52:44 [WARN] Provider "registry.terraform.io/hashicorp/aws" produced an unexpected new value for module.eks.aws_autoscaling_group.workers_launch_template[0], but we are tolerating it because it is using the legacy plugin SDK.
The following problems may be the cause of any confusing errors from downstream operations:
- .launch_configuration: was null, but now cty.StringVal("")
- .placement_group: was null, but now cty.StringVal("")

Estou com o mesmo problema
2020/10/16 11:52:44 [WARN] Provider "registry.terraform.io/hashicorp/aws" produced an unexpected new value for module.eks.aws_autoscaling_group.workers_launch_template[0], but we are tolerating it because it is using the legacy plugin SDK.
The following problems may be the cause of any confusing errors from downstream operations:

.launch_configuration: was null, but now cty.StringVal("")
.placement_group: was null, but now cty.StringVal("")

module "eks" {
 source          = "terraform-aws-modules/eks/aws"
 cluster_name    = local.cluster_name
 cluster_version = "1.18"
 subnets         = module.vpc.public_subnets
 vpc_id          = module.vpc.vpc_id
 enable_irsa     = true

 worker_groups_launch_template = [{
   name                    = "mixed-demand-spot"
   override_instance_types = ["t3.small", "t3.medium", "t3.large"]
   root_encrypted          = true
   root_volume_size        = 30

   asg_min_size                             = 1
   asg_desired_capacity                     = 3
   on_demand_base_capacity                  = 2
   on_demand_percentage_above_base_capacity = 25
   asg_max_size                             = 20

   kubelet_extra_args = "--node-labels=node.kubernetes.io/lifecycle=`curl -s http://<IP_ADDRESS>/latest/meta-data/instance-life-cycle`"
 }]
}

error version!!


[nlohmann-json] Update to 3.5.0

Update to 3.5.0
Use upstream CMake script to configure and provide targets

I think this upgrade was taken care of as part of #5258. Let me know if there's anything left here and thanks for the PR!


Minor copy changes to commit(s)/branch(es) tab

Gitea version (or commit ref): - Git version: d8d38ed

Description
If there is one commit or branch, the copy should be 1 Commit instead of 1 Commits, and same for branch.
Screenshots

@mmarif4u I've just created a PR for this change.


Couldn't build android C++ .so libs with bazel and tensorflow as a remote dependency.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): Source, current master branch (23.03.2021)
TensorFlow version: Current master branch(23.03.2021), latest tag v2.4.1
Python version: 3.8
Bazel version (if compiling from source): 4.0.0
GCC/Compiler version (if compiling from source):  7.5.0
CUDA/cuDNN version: Not Used
GPU model and memory: Not Used

Describe the problem
I am trying to build on C++ .so on top of tensorflow with bazel. I am trying to add tensorflow as a remote repository just like tensorflow_serving ( https://github.com/tensorflow/serving ).
I can build for native targets(linux x86_64) all fine, when I tried to build for --config android I got errors that android is not defined, so I copy/pasted the .bazelrc file from tensorflow, and updated .tf_configure.bazelrc. Than the build started but it is failing
for this target:
ERROR: /home/flamur/.cache/bazel/_bazel_flamur/8aff49c09e177f51e03fa24b3bf8aaa8/external/org_tensorflow/tensorflow/lite/delegates/gpu/cl/BUILD:486:22: Generating flatbuffer files for serialization_cc_fbs_srcs: @org_tensorflow//tensorflow/lite/delegates/gpu/cl:serialization_cc_fbs_srcs failed: (Exit 1): bash failed: error executing command
  (cd /home/flamur/.cache/bazel/_bazel_flamur/8aff49c09e177f51e03fa24b3bf8aaa8/execroot/this_repo && \
  exec env - \
    ANDROID_BUILD_TOOLS_VERSION=30.0.0-rc4 \
    ANDROID_NDK_API_LEVEL=24 \
    ANDROID_NDK_HOME=/home/flamur/Android/Sdk/ndk-bundle \
    ANDROID_SDK_API_LEVEL=30 \
    ANDROID_SDK_HOME=/home/flamur/Android/Sdk \
    PATH=/home/flamur/anaconda3/envs/flamxi/bin:/home/flamur/anaconda3/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/flamur/bin:/home/flamur/.cargo/bin:/snap/bin:/home/flamur/anaconda3/envs/flamxi/bin:/home/flamur/anaconda3/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/flamur/bin:/snap/bin:/home/flamur/Documents/CLion-2020.2.4/clion-2020.2.4/bin:/home/flamur/Documents/CLion-2020.2.4/clion-2020.2.4/bin \
    PYTHON_BIN_PATH=/home/flamur/anaconda3/envs/flamxi/bin/python3 \
    PYTHON_LIB_PATH=/home/flamur/anaconda3/envs/flamxi/lib/python3.7/site-packages \
    TF2_BEHAVIOR=1 \
    TF_CONFIGURE_IOS=0 \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; for f in external/org_tensorflow/tensorflow/lite/delegates/gpu/cl/serialization.fbs; do bazel-out/host/bin/external/flatbuffers/flatc --scoped-enums -I ./  -c -o bazel-out/armeabi-v7a-opt/bin/external/org_tensorflow/tensorflow/lite/delegates/gpu/cl $f; done')
Execution platform: @local_execution_config_platform//:platform
error: /home/flamur/.cache/bazel/_bazel_flamur/8aff49c09e177f51e03fa24b3bf8aaa8/external/org_tensorflow/tensorflow/lite/delegates/gpu/cl/serialization.fbs:15: 75: error: unable to load include file: tensorflow/lite/delegates/gpu/common/task/serialization_base.fbs
Target //skeleton:centernet failed to build
INFO: Elapsed time: 0.131s, Critical Path: 0.01s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully

I checked that file serialization.fbs and it seems like having a relative path for this include:
include "tensorflow/lite/delegates/gpu/common/task/serialization_base.fbs";

I am guessing this could be the problem! As the error says that cannot find this file.
If you want more files like WORKSPACE or .bazelrc please mention that, I don't know if they are required at this state!
For the target that I get this error I tested it with tensorflow as local dependency it works all fine, also with the remote dependency the non android targets are builded succesfully!

Hi Flamur,
It would be great if you can provide more information on how the BUILD file was written and how your .tf_configure.bazelrc looks like.
Reading the error message above, it seems that bazel can find tensorflow/lite/delegates/gpu/cl/serialization.fbs but not tensorflow/lite/delegates/gpu/common/task/serialization_base.fbs ?
Hi Juhyun,
Any thoughts on this or could you help re-assign to someone with more context?
Thanks,
Tiezhen

Hi @wangtz
Thanks for your reply.
This is my BUILD file content:
package(default_visibility = ["//visibility:public"])
#load("@org_tensorflow//tensorflow:tensorflow.bzl", "tflite_cc_shared_object", "tflite_copts", "tflite_linkopts")

cc_library(
    name = "centernet",
    srcs = glob([
        "foo.cpp",
    ]),
    hdrs = glob([
        "foo.hpp",
    ]),
    copts = [
        "-std=c++14",
    ] + select({
        "@org_tensorflow//tensorflow:android": [
            "-D__ANDROID__",
        ],
        "@org_tensorflow//tensorflow:android_arm64": [
            "-D__ANDROID__",
        ],
        "//conditions:default": [
        ]
    }),
    linkopts = [

    ] + select({
        "@org_tensorflow//tensorflow:android": [
            "-lEGL",
            "-lGLESv3",
            "-pie",
            "-lm",
        ],
        "//conditions:default": [],
    }),
    deps = [
        "@org_tensorflow//tensorflow/lite/delegates/nnapi:nnapi_delegate",
        "@org_tensorflow//tensorflow/lite:framework",
        "@org_tensorflow//tensorflow/lite:string_util",
        "@org_tensorflow//tensorflow/lite/kernels:builtin_ops",
        "@org_tensorflow//tensorflow/lite/tools/evaluation:utils",
        "@com_google_absl//absl/memory",
    ] + select({
        "@org_tensorflow//tensorflow:android_arm": [
            "@org_tensorflow//tensorflow/lite/delegates/gpu:gl_delegate",
             "@opencv//:opencv_arm",
        ],
        "@org_tensorflow//tensorflow:android_arm64": [
            "@org_tensorflow//tensorflow/lite/delegates/gpu:gl_delegate",
             "@opencv//:opencv_arm64",
        ],
        "//conditions:default": [
            "@native_opencv//:opencv",
        ],
    }),
)

And my tf_configure.bazelrc is:
build --action_env PYTHON_BIN_PATH="/home/$USER/anaconda3/envs/$USER/bin/python3"
build --action_env PYTHON_LIB_PATH="/home/$USER/anaconda3/envs/$USER/lib/python3.7/site-packages"
build --python_path="/home/$USER/anaconda3/envs/$USER/bin/python3"
build --config=xla
build:opt --copt=-march=native
build:opt --copt=-Wno-sign-compare
build:opt --host_copt=-march=native
build:opt --define with_default_optimizations=true
build --action_env ANDROID_NDK_HOME="/home/$USER/Android/Sdk/ndk-bundle"
build --action_env ANDROID_NDK_API_LEVEL="24"
build --action_env ANDROID_BUILD_TOOLS_VERSION="30.0.0-rc4"
build --action_env ANDROID_SDK_API_LEVEL="30"
build --action_env ANDROID_SDK_HOME="/home/$USER/Android/Sdk"
test --flaky_test_attempts=3
test --test_size_filters=small,medium
test:v1 --test_tag_filters=-benchmark-test,-no_oss,-gpu,-oss_serial
test:v1 --build_tag_filters=-benchmark-test,-no_oss,-gpu
test:v2 --test_tag_filters=-benchmark-test,-no_oss,-gpu,-oss_serial,-v1only
test:v2 --build_tag_filters=-benchmark-test,-no_oss,-gpu,-v1only
build --action_env TF_CONFIGURE_IOS="0"

For my case, I have to configure the Bazel build process to specify Android SDK and NDK path before running the bazel build ... commands.
More detailed https://github.com/cuongvng/TF-Lite-Cpp-API-for-Android

I guess the problem can be fixed by modifying the following file.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/delegates/gpu/cl/BUILD
flatbuffer_cc_library(
    name = "serialization_cc_fbs",
    srcs = ["serialization.fbs"],
    flatc_args = [
        "--scoped-enums",
        "-I ./",
    ],
    includes = [
        "//tensorflow/lite/delegates/gpu/common/task:serialization_base_cc_fbs_includes",
    ],
)

flatc_args need to have additional "-I" option to find serialization_base.fbs file. Could you try?

I tried a lot of combination to pass that flag as you mentioned @terryheo but since I am not familiar with flatbuffer bazel macros, I can not find a proper way that should work, what I tried is to update the -I with just the first directory of the repository meaning -I //tensorflow, -I // but that seems like a syntax error, also tried to find and check this content:  "//tensorflow/lite/delegates/gpu/common/task:serialization_base_cc_fbs_includes" but could not find it, in current master I cannot find a lib name of that package, only serialization_base_cc_fbs at this point I don't know if  flatbuffers bazel defs, have this "feature" to include only by adding _includes at the end of package or not! Can I expect more guides from you in this area? Thanks

@cuongvng thanks for your suggestions, but I already mentioned that when it comes to clone the repo locally I managed to add as a local_repository and than build against it, I am trying to build with tensorflow repo directly cloned from bazel! Thanks

It worth to provide absolute path to the serialization_base.fbs with "-I" option. (later we could find proper relative path)
FYI, "//" path only works Bazel and flatc_args is directly used by flatbuffer compiler.

exactly, // works only for bazel, and thats why I don't know how to begin writing the absolute path, since the repository comes from remote !

Did you search $HOME/.cache/bazel ?
https://docs.bazel.build/versions/master/output_directories.html

uh nice, so there will be the repository, I'll try it asap! thanks ;)

It works all flawlessly now! @terryheo  thanks!
Even though I got to type hard-coded absolute paths, since $HOME and $USER were not recognized there :S.
May I ask if you have any idea how would the proper solution would be, I would gladly contribute that!

That's good to hear.
Could you try if the following also works for you?
flatbuffer_cc_library(
    name = "serialization_cc_fbs",
    srcs = ["serialization.fbs"],
    flatc_args = [
        "--scoped-enums",
        "-I $(location //tensorflow/lite/delegates/gpu/common/task:serialization_base_cc_fbs_includes)",
    ],
    includes = [
        "//tensorflow/lite/delegates/gpu/common/task:serialization_base_cc_fbs_includes",
    ],
)

Please let me know if it works.
BTW, you can check the actual build command with "-s" option to Bazel. It will help to debug build issues.
$ bazel build -s //target

I tried, and no it doesn't work, still the error message for the missing include!
Also wanted to ask, I couldn't find this package declaration serialization_base_cc_fbs_includes anywhere inside the repository, it is only used in this file we are changing!

I see. I also thought it's strange.
It looks bit dirty... but could you try the following?
flatbuffer_cc_library(
    name = "serialization_cc_fbs",
    srcs = ["serialization.fbs"],
    flatc_args = [
        "--scoped-enums",
        "-I $$(dirname $(location //tensorflow/lite/delegates/gpu/common/task:serialization_base.fbs))/../../../../../..",
    ],
    includes = [
        "//tensorflow/lite/delegates/gpu/common/task:serialization_base.fbs",
    ],
)

@terryheo
I tried, I got this error:
ERROR: /home/flamxi/.cache/bazel/_bazel_flamur/8aff49c09e177f51e03fa24b3bf8aaa8/external/org_tensorflow/tensorflow/lite/delegates/gpu/cl/BUILD:490:22:
in cmd attribute of genrule rule @org_tensorflow//tensorflow/lite/delegates/gpu/cl:serialization_cc_fbs_srcs: label '@org_tensorflow//tensorflow/lite/delegates/gpu/common/task:serialization_base.fbs'
in $(location) expression is not a declared prerequisite of this rule.
Since this rule was created by the macro 'flatbuffer_cc_library', the error might have been caused by the macro implementation.

@terryheo Do you have any other idea we can try here!

@flamxi I believe this issue has been fixed in r2.6 by using workspace_root.
Here is the patch.
https://github.com/heeh/tensorflow/commit/bbdafc9f7e2a2564d8412dd1df7c1f0e5c3c0c05

Hi @flamxi, did the above solution https://github.com/tensorflow/tensorflow/issues/48014#issuecomment-1027399549 worked for you?


WIP: Fix operand error when calculating the price

Fix error which occurs when multiplying cost and liters because "*" is not defined for 'decimal.Decimal' (cost) and 'float' (liters). @feeds I hope you didn't use decimal on purpose.

There is still an error
ERROR:root:can't multiply sequence by non-int of type 'decimal.Decimal'
Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 676, in na_op
    result = expressions.evaluate(op, str_rep, x, y, **eval_kwargs)
  File "/usr/lib64/python3.4/site-packages/pandas/core/computation/expressions.py", line 204, in evaluate
    return _evaluate(op, op_str, a, b, **eval_kwargs)
  File "/usr/lib64/python3.4/site-packages/pandas/core/computation/expressions.py", line 64, in _evaluate_standard
    return op(a, b)
TypeError: unsupported operand type(s) for *: 'decimal.Decimal' and 'float'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 700, in safe_na_op
    return na_op(lvalues, rvalues)
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 686, in na_op
    result[mask] = op(x[mask], y)
TypeError: unsupported operand type(s) for *: 'decimal.Decimal' and 'float'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/root/informatiCup2018/src/serving/server.py", line 95, in get_prediction
    start_fuel_l=fuel)
  File "/root/informatiCup2018/src/serving/route_prediction.py", line 97, in get_fill_instructions_for_google_path
    positions_df['payment'] = positions_df.price * result.fill_liters
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 739, in wrapper
    result = wrap_results(safe_na_op(lvalues, rvalues))
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 710, in safe_na_op
    lambda x: op(x, rvalues))
  File "pandas/_libs/algos_common_helper.pxi", line 1212, in pandas._libs.algos.arrmap_object
  File "/usr/lib64/python3.4/site-packages/pandas/core/ops.py", line 710, in <lambda>
    lambda x: op(x, rvalues))
TypeError: can't multiply sequence by non-int of type 'decimal.Decimal'

#45 fixes this


Simulate trades

I have orderbook data that looks like this:
timestamp, price, side, volume
2023-02-10 23:59:49.789,21637.48,ask,0.67350
2023-02-10 23:59:49.789,21630.66,ask,0.03474
2023-02-10 23:59:49.789,21619.44,bid,0.00000
(0 volume here means cancel order/match order, doesn't matter)
I want to simulate trades on secondly basis. In each second I can potentially place an order (a market order or a limit order) so that they can be processed by your package. Is that possible?
Regards

In order to backtest more accurately, you need trade data and two types of timestamps: local_timestamp and exch_timestamp. But, still, it's possible to backtest only based on order book data and one side of timestamps if you assume your latency and generate the other side of timestamps artificially.
Firstly, you need to compose Pandas DataFrame based on your data.
Please see the example of conversion: https://github.com/nkaz001/collect-binancefutures/blob/master/convert/convert.py
columns: 'event', 'exch_timestamp', 'local_timestamp', 'side', 'price', 'qty'
event:
DEPTH_EVENT = 1
TRADE_EVENT = 2
DEPTH_CLEAR_EVENT = 3
DEPTH_SNAPSHOT_EVENT = 4
side:
BUY (BID) = 1
SELL (ASK) = -1

Will give it a try, thanks!


[FEAT] Support Right-to-Left scroll in Hebrew locale

Is your feature request related to a problem? Please describe.
After adding Hebrew to Supported Localization, I noticed that the scrolling will scroll in the opposite direction of where I am swiping. So if I try to swipe to the card on the left, it actually scrolls to the right. If I swipe to the card on the right, it scrolls to the left.
It's nice that it correctly places the items with the first item at the very right. 2nd item to its left. etc. However, the dragging animation is flipped around and may be counter-intuitive for users.
Describe the solution you'd like
Support scrolling in the correct direction for right-to-left locales.
Describe alternatives you've considered
N/A
Additional context

should be done in 2.5.0-beta.1, do you mind giving me some feedback @sdavidliu please?

Hi @fermoya , thanks for the quick turnaround! It is mainly working as expected; however, on some of my swipes (especially when I reach the end) it still scrolls to the opposite direction. Not sure if it's happening when I scroll fast enough, but it seems a bit random. I attached a video in Arabic locale:
2.5.0-beta.1-arabic.mov.zip


[Toolkit feature]: ComfyUI Rest API batch ingest textures from capture

Contact Details (Optional)
No response
What is the context of the feature/improvement?
The New ComfyUI nodes for rest api were just released
But im having a problem with its practicality with my tool,
With 10GB of vram my workflow hangs while running the toolkit as well, as there isnt enough VRAM to go around
The only thing i can think of to make this better is
People usually want a scene done in batch, so would there be a way to headlessly run the toolkit and get all the assets in the capture sent to my workflow?
Please describe the feature/improvement?
Without rendering viewport in toolkit a way to send all textures to be batch processed from a capture
What would be your solution? (optional)
...
Version
2024.4.1
Media
No response

Hey @Night10999 ,
Are you talking about the GetTextures node?
Questions:

How much VRAM does the Toolkit take with your stage?
How much VRAM does your ComfyUI workflow take when processing 1 image?

There are ComfyUI nodes to convert a list of images to batch ( https://github.com/ltdrdata/ComfyUI-Impact-Pack, "Image List to Image Batch" ), but our GetTextures nodes is outputting all the textures as a list.
We could create another node that output all the textures "in batch mode".

Thanks for filing @Night10999. Let us know if you've got the above info to help guide our efforts ^.
We've created an internal ticket for tracking: https://jirasw.nvidia.com/browse/REMIX-3445


Caching?

Your blog post says you cache your build dependencies for faster builds. I'm using up-to-date versions of dh_virtualenv and pip, but a simple project with requests as the only dependency still takes 30s to build, because pip needs to re-download it on every build.
How did you configure make-deb/dh_virtualenv to cache your dependencies?

Looks like virtualenv was using an older version of pip.


Admin panel - pagination : it is nice to have two arrow mark which takes the user to the last and first page on the project list

moved to the impact graph


Some cleanup in secure session manager code

Problem
SecureSessionMgr::SendMessage() function has grown too big in size, and needs some refactoring.
Summary of Changes

Moved code to encrypt message to its own function
Moved code to extract packet header from an pre-encrypted message out of the common function
Reorganized code to reduce conditional statements and blocks
Fixed a memory leak (if mTransportMgr->SendMessage failed, it could have leaked the retained buffer)

@saurabhst, @jelderton, @BroderickCarlin, do you have any comments?

@saurabhst, @jelderton, @BroderickCarlin, do you have any comments?


xml2js does not preserve element order within a level

Here's the input XML
<nj:entitySection>
    <nj:entity entityName="Student">
        <nj:subEntity subEntityName="Contact" >
            <nj:fieldGroup displayName="group1">
                <nj:inModelField displayName="field1"  />
                <nj:foobar>x</nj:foobar>
                <nj:inModelField  displayName="field2"  />
            </nj:fieldGroup>
            <nj:fieldGroup displayName="group2">
                <nj:inModelField displayName="field3"/>
            </nj:fieldGroup>
        </nj:subEntity>
    </nj:entity>
</nj:entitySection>
</nj:ReportingStandard>

And here's what xml2js reads in:
{ 'nj:entitySection':
  [ { 'nj:entity':
       [ { '@': { entityName: 'Student' },
           'nj:subEntity':
            [ { 'nj:fieldGroup':
                 [ { 'nj:foobar': [ 'x', [length]: 1 ],
                     '@': { displayName: 'group1' },
                     'nj:inModelField': [ [Object], [Object], [length]: 2 ] },
                   { '@': { displayName: 'group2' },
                     'nj:inModelField': [ [Object], [length]: 1 ] },
                   [length]: 2 ],
                '@': { subEntityName: 'Contact' } },
              [length]: 1 ] },
         [length]: 1 ] },
    [length]: 1 ],

The key thing to notice is that in the xml its:
Originally the order was:

inModelField
foo
inModelField

but in the result, it's more like:

foo
inModelField
inModelField

it basically combines all tags with the same element name at a particular level, and in so doing, BLOWS away the (XML proscribed) preservation of tag order. And there's no way to re-establish the original order.

Note: I'm not trying to read in XHTML - i just used those tags as an example of why it might be a problem for some schemas.
xml2js does have this sexy sounding option:
explicitArray (default: false): Always put child nodes in an array if true;    otherwise an array is created only if there is more than one.

While it does indeed "put child nodes in an array", it doesn't preserve the document order.

Any update on this issue?
This is a very common issue in a lot of XML docs. I would think the solution here could be as simple as changing the object model to add a _children_ array to all nodes, which populates in order of child node occurrence... and yes, probably as an optional behavior.

Currently no work is being done, but if you feel like submitting a PR that changes the current behaviour to something more sane (a.k.a preserving the order), I'd definitely be interested.

OK, I'll make a fork and take a look at the code to see if I can come up with something. No promises of course :)

OK, so, the above PR provides us with what I view is a viable workaround for this issue. In this configuration the parser behaves like normal (still collects nodes in named properties for convenience) with the "children" field now becoming and ordered array. The nodes all keep the #name field now so the children array can be iterated and node names checked if needed (very common case).
Note: both explicitChildren and preserveChildrenOrder must be true, and it does modify the behavior of explicitChildren in a way that will break code that relied on it previously ($$ is no longer a single object but the actual array of children) -- this breakage is why I made the preserveChildrenOrder an explicit option to override the behavior of explicitChildren instead of simply changing how explicitChildren works.

@ryedin @Leonidas-from-XIV Is it already published in the latest release, i.e. 0.4.8? To me it still looks like the $$ property is an object rather than an array even though I am using both explicitChildren and 'explicitChildren' modifiers. Maybe I am doing something wrong.

@apendua As the README says, these options are only available starting with 0.4.9 (when it will be released) and git master.

@apendua if you need the feature right away, you can change your package.json to point to Leonidas-from-XIV/node-xml2js which will tell npm to pull directly from the github repo instead of the last published npm package.

@ryedin Thanks for response. I was confused because for some reason I thought that your latest PR ended up in 0.4.8 - probably because of the commit date. I can see now that in fact it's the other way around:
https://github.com/Leonidas-from-XIV/node-xml2js/compare/0.4.8...master
This said I also thought 0.4.9 was a typo error in your README.md @Leonidas-from-XIV because such a release does not even exists. But anyway, thanks for explanation. A lot of confusion but everything seems to be clear now.

This said I also thought 0.4.9 was a typo error in your README.md @Leonidas-from-XIV because such a release does not even exists.

The master version will be released as 0.4.9, so the README.md is correct. If it references a version that is in the future, it means that it will be part of a future release.
I released 0.4.8 before merging @ryedin's patch, to make sure there is a recent release in case things will break, so there is a version to quickly roll back to. I suppose since there have't been many complaints, I'll release 0.4.9 soon.

While rebuilding this ordered js to xml, the builder doesn't rebuild it in the ordered form. The order gets messed up again while building it back. Is there any workaround for that ?

This is still an issue. At the moment, a one to one bi-directional conversion is guaranteed only for default configuration" (from the README) is therefore not correct.

Yes, I should remove the note about that for now until I have time to rewrite it.

It is also weird that it is still the default behavior to mess up the order. That is not what one expects an XML parser does, because in XML order matters. A bit of an annoying gotcha to default to something that doesn't make sense with XML.


Outlined text field shows line through label

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
When the TextField or Select renders with input in it, the label is rendered above the input and the line moves away.
Current Behavior
The label does move up, but the line remains, going through the text.

Steps to Reproduce
I am unable to reproduce this issue consistently. It does happen the majority of the time in the project I'm working. The outline does update as soon as interaction has taken place with the page like clicking on an element, opening a dropdown, etc. or anything that manipulates the state of the current component.
I've seen this happen in v3.2.x, I have never used the variant="outline" in prior versions so am unaware if this bug existed prior to v3.2.
Link: https://codesandbox.io/s/q361rzjpy4
Context
N/A
Your Environment

Tech
Version

Material-UI
v3.2.x

React
v16.5

Browser
Edge, Firefox, Chrome

@Studio384 We would love to have a way to consistently reproduce the issue. It's very hard to work on this type of issue without.

The code sandbox does reproduce it most often in Edge 18y. Other browsers appear to be less consistent in reproducing the issue or are only showing it for a short time (Chrome) before updating the view again to move the line away from the label.

I'm also experiencing this issue when a OutlinedSelect is mounted with a prefilled value. The label corrects itself after a re-render. I suspect it has something to do with the labelRef from the <InputLabel> being unavailable at initial render, since it's offsetWidth is used to control the width of the gap.
Version: 3.2.2 (latest at writing time)
Browser: Chrome  69.0.3497.100

I'm closing for #13297. I could reproduce the issue on Edge. The issue disappears as soon as I hover the input. It's a rendering glitch

It's not the same issue as #13297. In Firefox you have to interact with the page for it to go away and when you do it will animate the line (which shouldn't happen if this was a rendering glitch).

Outline text field look terrible in Firefox but working in Chrome. When clicking the textfield in Chrome there's also a color change, not happening in Firefox.

Hi, I've had this issue too. It occured whenever I changed the label of the Textfield dymically at runtime (I needed to switch languages).
I would write the new label to state, and even though the Textfield showed the new label, it didn't update the outline. However it updated the outline once a rerender was triggered anywhere else.
So in my case I had a function to merge my new labels into current state. My solution was to promisify this function and then force an update. I think this is very ugly, but not as much as the linethroughs ;)
I did:
`let update = new Promise((resolve, reject)=>{
this.setState(state => ({
formFields: currentStateFormFields
}), resolve(true) )
});
update.then(result =>{
  if(result) {
    this.forceUpdate();
  } else {
    throw new Error("MERGING LANGUAGE FAILED");
  }
})`

Fixed in v4.4.0: https://codesandbox.io/s/material-ui-text-field-bug-m4ujq.
-- credits to @oliviertassinari

This does not appear to be fully fixed on v4.4.0.

I'm having the same problem the original poster explained. I mean, this happens when any change to the state that contains the field is done. Re-rendering the field by changing any of its properties makes this problem disappear, but I'm not sure how to "force" such thing.

@danielo515 You could update the key, which would cause a re-render of the component.

@danielo515 You could update the key, which would cause a re-render of the component.

Yes, that is what I ended doing. Thanks for your answer in any case.

Does anyone has a reproduction?

It is tricky to reproduce. Can't say what triggers it. For example on my case it only happens on 2 out of 3 elements in the same parent component. The only difference is that those two are inline while the other is full width.

Hello,
I have this bug too and I don't find how to solve it. It appeared on a form when I used tabs component (I took "simple tabs" example).
 <TabPanel value={value} index={0}>         <ProductInfos           selectedInfos={selectedInfos}           onChange={onChange}         />       </TabPanel>       <TabPanel value={value} index={1}>         <OrderInfos           selectedInfos={selectedInfos}           onChange={onChange}         />       </TabPanel>       <TabPanel value={value} index={2}>         <SupplierInfos           selectedInfos={selectedInfos}         />       </TabPanel>
The form displayed by  is good, the render of  is ok. But this isn't good in the 2 other tabs. I have the same problem with  labels' as discribed above, for my forms displayed by  and .
Is there a temporary solution to fix it and make labels override the outlined borders?
Sorry for my bad english and thanks in advance for help.

@rikku28 This sounds like a duplicate of #17355.

@rikku28 This sounds like a duplicate of #17355.

Hola,
también tengo este error y no encuentro cómo solucionarlo. Apareció en un formulario cuando utilicé el componente de pestañas (tomé el ejemplo de "pestañas simples").
 <TabPanel value={value} index={0}> <ProductInfos selectedInfos={selectedInfos} onChange={onChange} /> </TabPanel> <TabPanel value={value} index={1}> <OrderInfos selectedInfos={selectedInfos} onChange={onChange} /> </TabPanel> <TabPanel value={value} index={2}> <SupplierInfos selectedInfos={selectedInfos} /> </TabPanel>
El formulario que se muestra es bueno, el renderizado es correcto. Pero esto no es bueno en las otras 2 pestañas. Tengo el mismo problema con las etiquetas 'como se describe anteriormente, para mis formularios mostrados por y.
¿Existe una solución temporal para arreglarlo y hacer que las etiquetas anulen los bordes delineados?
Perdón por mi mal inglés y gracias de antemano por la ayuda.

I have exactly this problem, I have tried many things without obtaining an effective result ... I have even copied the form of the first Tab and this happens ...

It seems that the TabPanel demos we have are a common source of the observation of the problem. In this context, I would propose the following diff in the demos:
diff --git a/docs/src/pages/components/tabs/SimpleTabs.js b/docs/src/pages/components/tabs/SimpleTabs.js
index 02e6d8ce3..0ce8c959d 100644
--- a/docs/src/pages/components/tabs/SimpleTabs.js
+++ b/docs/src/pages/components/tabs/SimpleTabs.js
@@ -19,7 +19,7 @@ function TabPanel(props) {
       aria-labelledby={`simple-tab-${index}`}
       {...other}
     >
-      <Box p={3}>{children}</Box>
+      {value === index ? <Box p={3}>{children}</Box> : null}
     </Typography>
   );
 }

It would also help with performance, as only rendering the visible nodes, at least, until React improves the handling of hidden. cc @mbrookes and @eps1lon.

@oliviertassinari Thanks for the help. That's working now, with this modification. :)
Best regards

Not sure it helps, but I was still having this issue because a previous dev was using  and  instead of  with label=""
Once I made the change the line went away when typing into the field.

For anyone who found this thread but the suggestions here didn't help, I found that the displayEmpty prop was causing this issue for us. Once we removed it from our Select components it looked as expected.


[SPARK-28481][SQL] More expressions should extend NullIntolerant

What changes were proposed in this pull request?

Make more expressions extend NullIntolerant.
Add a checker(in ExpressionInfoSuite) to identify whether the expression is NullIntolerant.

Why are the changes needed?
Improve query performance. For examples:
CREATE TABLE t1(c1 string, c2 string) USING parquet;
CREATE TABLE t2(c1 string, c2 string) USING parquet;
EXPLAIN SELECT t1.* FROM t1 JOIN t2 ON upper(t1.c1) = upper(t2.c1);

Before and after this PR:
== Physical Plan ==
*(2) Project [c1#5, c2#6]
+- *(2) BroadcastHashJoin [upper(c1#5)], [upper(c1#7)], Inner, BuildLeft
   :- BroadcastExchange HashedRelationBroadcastMode(List(upper(input[0, string, true]))), [id=#41]
   :  +- *(1) ColumnarToRow
   :     +- FileScan parquet default.t1[c1#5,c2#6]
   +- *(2) ColumnarToRow
      +- FileScan parquet default.t2[c1#7]

== Physical Plan ==
*(2) Project [c1#5, c2#6]
+- *(2) BroadcastHashJoin [upper(c1#5)], [upper(c1#7)], Inner, BuildRight
   :- *(2) Project [c1#5, c2#6]
   :  +- *(2) Filter isnotnull(c1#5)
   :     +- *(2) ColumnarToRow
   :        +- FileScan parquet default.t1[c1#5,c2#6]
   +- BroadcastExchange HashedRelationBroadcastMode(List(upper(input[0, string, true]))), [id=#59]
      +- *(1) Project [c1#7]
         +- *(1) Filter isnotnull(c1#7)
            +- *(1) ColumnarToRow
               +- FileScan parquet default.t2[c1#7]

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #123041 has started for PR 28626 at commit c3625ca.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27684/
Test PASSed.

Test build #123041 has finished for PR 28626 at commit c3625ca.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123041/
Test FAILed.

retest this please.

Test build #123053 has started for PR 28626 at commit c3625ca.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27693/
Test PASSed.

Test build #123053 has finished for PR 28626 at commit c3625ca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123053/
Test PASSed.

Test build #123059 has started for PR 28626 at commit 7fe3490.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27698/
Test PASSed.

Test build #123059 has finished for PR 28626 at commit 7fe3490.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123059/
Test FAILed.

also cc: @viirya

Test build #123105 has started for PR 28626 at commit b127c41.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27739/
Test PASSed.

Test build #123105 has finished for PR 28626 at commit b127c41.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123105/
Test FAILed.

retest this please

Test build #123113 has started for PR 28626 at commit b127c41.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27747/
Test PASSed.

Test build #123113 has finished for PR 28626 at commit b127c41.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123113/
Test PASSed.

Test build #123124 has started for PR 28626 at commit 82e97e3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27756/
Test PASSed.

Test build #123124 has finished for PR 28626 at commit 82e97e3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123124/
Test PASSed.

@gatorsmile @cloud-fan

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27856/
Test PASSed.

Test build #123233 has started for PR 28626 at commit 1bdff95.

Test build #123237 has started for PR 28626 at commit 265abd3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27861/
Test PASSed.

Test build #123233 has finished for PR 28626 at commit 1bdff95.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123233/
Test PASSed.

Test build #123237 has finished for PR 28626 at commit 265abd3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/123237/
Test PASSed.

thanks, merging to master!


[CTA - Card] Heading is missing, style error or storybook author error

Web components storybook, React OK https://ibmdotcom-web-components-canary.mybluemix.net/?path=/story/components-cta--card
Both Canary and Prod
Other components like Card group & Card not affected. Only CTA - Card is missing heading.
Need to investigate why Percy didn't catch this.

This regression happened here 2 months ago...

https://percy.io/538fc19a/Carbon-for-IBM.com-Web-Components/builds/12576205/changed/709810010?browser=chrome&browser_ids=16&subcategories=approved&viewLayout=overlay&viewMode=new&width=320&widths=320%2C1280


Template license in README.rst based on user's choice.

Just a simple bugfix. I noticed that the generated README contained LICENSE: BSD despite me choosing MIT. BSD was hard-coded.

Also added missing href for @dsclementsen in CONTRIBUTORS :)

Closed/reopened to rerun the the Travis checks. One had a sporadic failure.

Thanks! 🎉