Add option to allow APIs app is interested in

Description
Another API discovery improvement which allows application to list api it is interested in. API discovery will watch only for these API endpoints and would further limit the number of requests.
Caveats
Once this is merged and hac-core app starts to send in the list apps might not be able to watch for some resources, unless they specifically list them. We should communicate this change to apps and prepare them for this change (adding the apiAllowed to their config) before we roll this feature fully.
Example
Usage of this new feature can be seen at https://github.com/openshift/hac-core/pull/119

Thanks! For the general review I would expect that someone else will do it, but thanks for the naming change! :+1:

Thanks! For the general review I would expect that someone else will do it, but thanks for the naming change! :+1:
/uncc

@karelhala this PR build isfailing due to missing generated API report docs for lib-core and lib-utils. When you run a local build you should see a warning with instructions to copy the modified API doc into version control under the reports dir.
I've create a commit with those changes if you rather cherry pick it: https://github.com/openshift/dynamic-plugin-sdk/commit/1d79ec6207ad66b24a04900519c234076f1ce44a

@florkbr aaah, good point! I didn't read the warnings. Updated the PR with those changes.

@karelhala now prettier is angry :(
openshift/dynamic-plugin-sdk/packages/lib-utils/src/app/api-discovery/index.ts
  149:7  error  Insert `··`  prettier/prettier

Do we still need this PR with your PR to move api-discovery to hac-core?

@florkbr I didn't even tuched that line. I don't think so. I'm keeping it open just in case we decide to merge it in dynamic plugin SDK as well.

/uncc
/unassign

/uncc

Closing in favor of https://github.com/openshift/dynamic-plugin-sdk/pull/204


Direct Loading via composer

Hi,
Is it possible to use Eden/Sqlite as "standalone", requiring it via composer, calling it via a standard include, or composer autoload ?
It would be a great feature.

https://packagist.org/packages/eden/sqlite

The eden function is undefined if you just require eden/sqlite via composer and call autoload.

The eden function is undefined if you just require eden/sqlite via composer and call autoload.php.

@bactisme - I know it's a long time to respond to this, but you need to call Eden\Core\Control::i() before doing anything with the libraries.

Had the same problem, thanks!

@mikerockett
I've tried to call Eden\Core\Control::i() before calling eden() but I still end up with the following error messages:
Undefined variable: code in /vendor/eden/core/src/Argument.php on line 54 Undefined variable: message in /vendor/eden/core/src/Argument.php on line 54
Any suggestion?


Make feelin a peer dependency

What should we do?
Ideally we should not have a hard dependency on feelin. Switching over to peer dependency should be the right thing to do here
Why should we do it?
There are multi angles here, but first and foremost, feelers is a templating structure built around feelin, not a direct consumer of it. It in theory should work for any somewhat similarly structured expression language. It certainly should always work with newer versions of feelin. We mainly rely on feelin for the syntax highlighting which again, is feelin's business not this library's. Furthermore, the scenarios in which we (and presumably others) use this library often have us depending on feelin as well directly.
So, in the interest of simplicity, I think we should just move this to a peer dependency, check this doesn't cause any issues in integrations and just stop having to worry about version matches and such.

@Skaiir Another angle to consider here:
Can we ensure that feelin is going to be used anyway, wherever feelers is used? If that is the case, it is fine to be a peer dependency (or no dependency at all).
If that is not the case then we can resort to de-duplication being done by bundlers. They do a great job at that, nowadays.


Question about data preprocessing

Hi, I have a question about the data preprocessing (data_preprocessor.py) and want to seek some help:
When calling the rm_blank of grounding, why the is_shorten is set as True?
Thanks!

Hi,
Thanks for the question!
In some rare cases, we found that certain grounding content couldn't be matched with a passage even though we could find one when searching manually. Then, it seemed that shorten the grounding content by a little bit could help with the odd issue. So, it is sort of a not-so-elegant workaround that we applied.
Best,
Song


Add base: './' to the vite configuration

I'm hosting ComfyUI on the subpath, like domain.dev/comfyui. It works fine because of handling such cases in the base_path in scripts/api.js, but after installing this plugin, I found an absence of the plugin UI and a lot of error messages in the development console inside the browser.
After digging this down, I found that vite doesn't preserve base path and attempt to load files from the root. It looks like all we need to fix that is to add base: './' in the configuration object, so vite would use relative paths.
I wanted to apply fix locally, but I didn't manage to build UI by myself, at first because of https://github.com/11cafe/comfyui-workspace-manager/issues/439 and then (after moving to the revision right before an addition of encryptUtils.ts) because of some weird error inside browser saying that it cannot find JSZip global object.

many plugins are same

oh wow i didn't know that you can do this base: './'  in vite
and i just fixed this issue: encryptUtils.ts
so u should be able to npm build this project no problem now

could you please build and test if this works for you now?

https://github.com/11cafe/comfyui-workspace-manager/pull/455
i added it in beta branch

could you please build and test if this works for you now?

not work.
You can test it by WSL2 and code-server.
export VSCODE_PROXY_URI=./proxy/{{port}}/ &&  code-server --disable-workspace-trust --disable-telemetry --auth none ~ --bind-addr <IP_ADDRESS>:8080
and run the ComfyUI

Can you F12 Console and screenshot the errors? It would be very helpful for debugging. Thanks!

From: LP @.>
Sent: Sunday, August 4, 2024 11:30:39 PM
To: 11cafe/comfyui-workspace-manager @.>
Cc: Weixuan Fu @.>; Comment @.>
Subject: Re: [11cafe/comfyui-workspace-manager] Add base: './' to the vite configuration (Issue #449)
could you please build and test if this works for you now?
not work.
You can test it by WSL2 and code-server.
export VSCODE_PROXY_URI=./proxy/{{port}}/ && code-server --disable-workspace-trust --disable-telemetry --auth none ~ --bind-addr <IP_ADDRESS>:8080
and run the ComfyUI
—
Reply to this email directly, view it on GitHubhttps://github.com/11cafe/comfyui-workspace-manager/issues/449#issuecomment-2267581386, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEMEEONORLUIHMB7QNWBGWLZPZCJ7AVCNFSM6AAAAABLZ2KZ32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRXGU4DCMZYGY.
You are receiving this because you commented.Message ID: @.***>

the input.js get css from host not host+baseUrl

@Weixuanf
comfyui-workspace-manager.tar.gz


saving all objects  not just last object

Hi,
Thank you for this plugin.
In my project containing many different objects, each using a different mesh, only the last object mesh filenames was added to the asset list. This fixes it.
Here's my exemple blender 3.2 file. I used geometry nodes to generate mujoco terrain, then a script to export them to mujoco.
This fix allows this conversion to work correctly when multiple objects are selected

(here's the blender file)
terrain4.zip

Thanks for the contribution! In my tests I only ever tried scenes with a single hierarchy of meshes so I missed this issue.


[Grid] Fix flex-direction inheritance on column grid

Consider the following code:

grid item

grid item

grid item

Since there are two columns inside a column of a two column grid, one would expect to get three grid item blocks, where the third is as wide as the first two combined. However, in this specific case, this doesn't happen, and the two items in the nested grid appear one below the other.
I've created a fiddle to demonstrate this, as well as two examples where this doesn't happen - it only happens when the parent grid is middle aligned and when the nested grid has a given column width, i. e. two column wide.

This is a bug, caused by flex-direction: column being inherited on grid.
In this line.
It should read
.ui.grid > [class*="middle aligned"].column:not(.row):not(.grid)

As a side note from your example, the keyword for column sizing is (x) column not (x) column wide.
http://jsfiddle.net/ng49ebq1/

Fixed in 2.1


feat: init table in mysql and postgres

Describe the pull request
Add InitTable flag in Config to determines whether create a default cache table while initializing.
Link to the issue: https://github.com/flamego/flamego/issues/82
Checklist

[x] I agree to follow the Code of Conduct by submitting this pull request.
[x] I have read and acknowledge the Contributing guide.
[x] I have added test cases to cover the new code.

https://github.com/flamego/cache/releases/tag/v1.1.0 has been tagged for this merge.


Fetching data from Vuex store in component

Hello, I'm running into an issue where when I initially load the page, my data isn't being loaded, however if I navigate to another page, and then click back to the home page, the data is loaded into the component. I'm not sure what I'm doing wrong either in my component or store, any tips appreciated. Relevant files below..
// store/index.js
const createStore = () => {
    return new Vuex.Store({
        state: {
            repos: []
        },
        actions: {
            LOAD_REPOS: function({ commit }) {
                axios.get('repourl').then((res) => {
                    commit('SET_REPOS', res.data)
                })
            }
        },
        mutations: {
            SET_REPOS: (state, repos) => {
                state.repos = repos
            }
        }
    })
}

export default createStore

// pages/index.vue
<template>

{{ repo.name }}

</template>

For those wondering, here is the solution..
async fetch ({ store }) {
    if (store.state.repos.length === 0) {
        const data = await store.dispatch('LOAD_REPOS')
    }
}

actions: {
    LOAD_REPOS: async function({ commit }) {
        const res = await axios.get('repourl')
        commit('SET_REPOS', res.data)
    }
}

How does it work though when I want to use an action from a component that is not a page component? :/

@nop33 What do you mean an action from a component? The action should always be stored in the vuex store, and you can call the action from any component

Fatch function don't work in DIR components. How use Vuex store (data) in DIR components?


@hxrts - Cleanup merge

Cleans up latest PR, fixes indentation, fixes style loading and removes button.js.

Well done. Found two minor issues indicated above, those could just as easily be resolved in a later PR. Tested this on my machine and everything works beautifully.

going to merge for now. can address the minor points above as individual issues which I've added.


Feature Request: Shared and overridable variables (globals?)

Background
For most of our terraform projects, we prefer to keep the remote state in the same region as the resources that are being created.  This allows us to manage resources in other regions when S3/DynamoDB is down in a particular region.
We also have a pretty standard directory structure for services:
terraform
├── terragrunt.hcl
└── <account>
    └── <region>
        └── <environment>
            └── terrgrunt.hcl

With the addition of terraform functions, it was simple to get the region from the directory name and use that in the backend configuration.
However, we also have a separate structure containing all of the infrastructure that doesn't belong to a single application - and this structure is much less predictable.  Some resources have multiple directories before the region, and some don't have a region directory at all.  Since many of these resources don't (and shouldn't) conform to the structure above, it would be very convenient to specify a region variable in the parent terragrunt.hcl that can be overridden in the child terragrunt.hcl.
There are certainly ways to work around this right now, but what I would love to be able to do is:
globals {
  region = "us-east-1"
}
terraform {
  source = ...
}
include {
  path = find_in_parent_folders()
}

Proposed Solution
I would like to implement something similar to locals, except keys in the block would be merged with the parent config (with child definitions overwriting parent definitions).  Thus, the config resolution order would be:

locals
include
globals
Everything else

This would accomplish three things:

Defining variables in parent config that can be used in every child config
Defining variables that the child configs can use to affect the behavior of the parent config
Allowing for intermediate variables that would otherwise go in locals but need the relative path to the parent config

Questions

Is this something that seems like a good idea?  Should I create a PR for this?
Is globals the correct name, or is there something better?

This is a result of https://github.com/gruntwork-io/terragrunt/pull/802#discussion_r310202282 and possibly related to #132.

Since I suggested this, I am on board with this idea! Although, I am curious to hear others' opinions about separating globals (temporary common vars that are auto merged across include) from locals (temporary common vars that are scoped to the current config).
I am a bit confused by what you mean by the config resolution order in the proposed config. If globals works exactly like locals, then the access to it should be explicit (e.g global.region). Can you elaborate a bit more on this?

By the config resolution order, I mean the order that the blocks in the terragrunt HCL file are are evaluated.  I was assuming the include block depends on locals being interpolated (which I didn't verify), but regardless globals would need to depend on the include block being evaluated if globals are merged across includes.

If you wanted to make it even more complicated, in reality locals could depend on globals as long as those locals aren't used in the include block.  I'm not sure if that confusion is worth it, though.

After some more thought, I have an alternate proposal:

include is a new variable "group" that gets set when the include block is evaluated:

include.relative would replace the function path_relative_to_include()
include.parent would replace the function get_parent_terragrunt_dir()
include.child would replace the function get_terragrunt_dir()
Another function could be added to get the path to the file that the expression is in, e.g. get_current_file()

locals are variables that are only usable within the context of this terragrunt.hcl file.  They can reference other local or include variables, as long as they don't cause a reference loop (i.e. a local can't reference an include, and also be used in the include block).
globals are variables that are merged with the child terragrunt.hcl file before being evaluated.  By nature, they can use include variables but cannot be used in include blocks.

Both globals and locals can reference each other, as long as they don't cause a dependency loop.  A local referenced from a global would refer to the local from the file that the global expression is in - i.e. if a child overrides a global with an expression that includes a local, that would be the child's local.
This strategy would accomplish a few things:

It would remove the requirement of only being able to use the "include" functions (relative path, etc) in globals, simplifying the semantics of global and local ("should this variable be shared or not shared?")
It would disambiguate the "include" functions - right now they're available everywhere, but their behavior changes depending on which part of the config they're called from.
It would make the config a lot more terraform-like, which would probably be more intuitive for new terragrunt users coming from terraform.  Instead of defined resolution phases, any variable can be used anywhere as long as it doesn't cause a loop.

As far as implementation goes, looking through the terraform code it doesn't seem incredibly complicated to copy the variable discovery, graph creation, graph verification, and evaluation.  Some code from the terraform project could even be imported and re-used.
Thoughts?

One minor issue I have with the current implementation of locals is that I cannot use the path_relative_to_include in a local definition. This limits a chunk of my use cases and I guess the above proposal fixes that.. But I'm not entirely sure why it's necessary to change the well known and documented path-discovery function calls to an include group? Seems like a huge change.
As for the original proposal, a lot of my locals are being passed down to the underlying child modules using inputs, so yeah I would say this seems like a good idea in general.

One minor issue I have with the current implementation of locals is that I cannot use the path_relative_to_include in a local definition

Ah that is a good point and an oversight on my part. The original proposal for globals would indeed address that!

include is a new variable "group" that gets set when the include block is evaluated

While I understand where you are going with this, I think this could overcomplicate the implementation. Right now the path functions are implemented as simple go functions, which makes them fairly easy to maintain. Having to fold them into the include block requires adding additional custom parsing logic while the include is being created, that then needs to be passed down throughout the code to each execution contexts. I can see this being unintuitive and a pain to maintain.
I'd say that for now, start by implementing the basic version of globals, which are locals that get auto merged across include blocks. Since locals are relatively new, I'd wait for it to be tested in the wild for a little bit longer before we start optimizing the implementation with complex execution orders that allow interdependencies between locals, include, and globals. My hunch is that the basic globals will cover 90% of use cases that require referencing the include paths.

And it might turn out that we don't need locals once globals is implemented.

Thanks for going through this thought exercise by the way! Very helpful in understanding why you need it, and your thought process on approaching the implementation!

What's the difference between globals and inputs = { ... } in the root config?

globals can be referenced in the children inputs. E.g if you had:
globals {
  region = "us-west-1"
}

You can have a child config that is:
include {
  path = find_in_parent_folders()
}

inputs = {
  s3_url = "com.amazonaws.${global.region}.s3"
}

Would that be different than adding support for inputs referencing other inputs? E.g., s3_url = "com.amazonaws.${inputs.region}.s3"?
Or how does this compare with a get_input([<FILE>], <INPUT>) helper? We know we want to add get_output, and it seems like get_input is a natural analog. You can either specify an explicit a FILE to read inputs from, or if you omit it, it uses the current inputs, merged with parent inputs.

I think get_input makes sense, but independent of globals. In fact, we should probably also have get_local and get_global, or even a full import_input/local/global function that imports the full map to make it less verbose.
The benefit of globals is: What if you don't want it to be passed in as an input to terraform? globals gives you a space to specify variables that you don't intend to pass to any module, but use to build up the other inputs. It seems clean to have these temporary variables built up there instead of as inputs which will be converted to TF_VAR_xyz env vars.

Oh, I was thinking get_input could read values out of other .hcl or even .yml files.  Perhaps get_input makes it sound like it only reads the inputs = { ... } block, but that's not really the goal.
BTW, I'm not 100% set on any approach here and am just thinking out loud. My main goal is to find the minimal set of tools we could expose for defining, sharing, reusing, and passing variables around. So the question is whether locals / globals provides a more flexible toolset than get_input (and get_output)? Or if some other option is even more effective? Might be worth listing out all use cases we want to support (e.g., local var usage, sharing vars from parent, getting vars from other modules, getting vars from var files, etc).

Sorry, I was away for a few days and didn't get a chance to respond.

Re: replacing the path functions with static variables:
On the contrary, I think using functions for this is actually the unintuitive way to do it.  In terraform, functions are available and idempotent no matter where they're used.  If globals are added, the behavior of these functions would differ between usage in the local and global blocks.  In local, they would resolve to ., and in global they would be a real path.  To me, that doesn't seem like an ideal solution.  We can still forego complicated dependency logic for now by just erroring if the include variables (or functions) are used in a local variable.

Re: globals replacing locals entirely:
It would definitely be possible to replace globals with locals, but I see two issues with that (assuming simple dependency logic):

You wouldn't be able to use any variable in an include block, since that block would need to be interpreted before globals could be.  Right now, you could use a local.
Encapsulation is generally accepted as a good practice, i.e. you shouldn't expose information that you don't need to.  This keeps your code simple and reduces the chance of bugs.  Removal of locals would cause every variable you use in your parent config to be available from your child config, and you could accidentally override those variables from the child if you re-use the name accidentally.  If something doesn't need to be global, it should be kept local.

Re: get_input
What's the use-case for this?  It seems to me all of those cases would be covered by good local and global system.  Would this be a way to share variables between different terragrunt projects?

I'm definitely willing to whip up a PoC even if it needs significant changes before being merged.

On the contrary, I think using functions for this is actually the unintuitive way to do it.

I wasn't talking about the end user UX. I was talking about the code that actually implements it. So it isn't about whether or not it is intuitive to users of terragrunt or terraform, but rather whether or not it can be implemented in a way that is easy to maintain and has few bugs. In other words, will the implementation be intuitive to the golang developer?
This is why I mentioned this should be addressed independent of the globals implementation, because I expect globals would be fairly easy to implement (and thus can be released sooner), while the path parsing stuff might be difficult and tying the globals implementation to that might delay the implementation of the feature.

What's the use-case for this?

The main use case for this is if you want to fragment the globals across multiple HCL files that are nested across the tree. Right now terragrunt doesn't allow more than one include, so there is only one level of depth even for globals. get_input is a way to import and reference multiple HCL files, replacing the yaml based system of merging multiple variable files.

I wasn't talking about the end user UX. I was talking about the code that actually implements it.

Ah, sorry, I completely misunderstood that.  I think it should be just as easy to implement - just remove those functions and add a variable group to the evaluation context when evaluating everything but locals and include.  It definitely can be separated from the initial globals implementation if you think that would be better.

The main use case for this is if you want to fragment the globals across multiple HCL files that are nested across the tree.

Cool, thanks for the explanation.  Is multi-include being considered, and if so would get_input just be a quick stopgap until that gets figured out?  Or have you decided that multi-include isn't a good idea?

add a variable group

I think you are underestimating the complexity of interjecting something to the parsing pipeline to add this. But who knows! I might be missing some clever way to do this.

It definitely can be separated from the initial globals implementation if you think that would be better.

Yes let's keep that separate.

Is multi-include being considered, and if so would get_input just be a quick stopgap until that gets figured out? Or have you decided that multi-include isn't a good idea?

You can see https://github.com/gruntwork-io/terragrunt/issues/303 for past thoughts on this, as well as some current thoughts. In general, multi-include is not something we want to add and if possible would like to use other primitives to achieve the same effect. get_input is one of those proposed primitives.

By the way, you might want to hold off on implementation until I am done with https://github.com/gruntwork-io/terragrunt/pull/828. globals will almost certainly conflict with that feature. Also, the new partial parsing pipeline might help make the include path variable context implementation easier.

I think you are underestimating the complexity of interjecting something to the parsing pipeline to add this.

I don't think so, unless I'm missing something.  It should be just as easy as adding locals to the evaluation context:
	if locals != nil {
		ctx.Variables = map[string]cty.Value{"local": *locals}
	}

In fact this function definition already has the value of the include block available to it:
func CreateTerragruntEvalContext(
	filename string,
	terragruntOptions *options.TerragruntOptions,
	include *IncludeConfig,
	locals *cty.Value,
) *hcl.EvalContext {

By the way, you might want to hold off on implementation until I am done with #828.

Thanks for the heads up, it definitely looks that way.  I'll do some initial exploration but I won't spend too much time on it till that's complete.

Ok #828 is now merged. Also, I've refactored the eval context parameters into a struct EvalContextExtensions which should make it easier to pass through the include vars all the way down.
So @apottere , feel free to start working on this! Be sure to think through where globals fits in the parsing pipeline and update the docs accordingly. Here are two places where we document the parsing pipeline:

In the README: https://github.com/gruntwork-io/terragrunt#configuration-parsing-order
In the code: https://github.com/gruntwork-io/terragrunt/blob/master/config/config.go#L270

Sounds good, thanks!

@yorinasub17 I got really busy, but I finally had some time to put together a POC of this in #858.  Let me know what you think.
I decided to go for the more complicated approach because I was pretty sure I could make it work and it was more fun to try and figure out.  I can definitely implement a simpler approach if you want.

Any news on this one?

Wanted to ask for any update on this, thanks!

This would be nice to have

I do something a little like this, but with recursion hell. Not sure how interested people would be to use it.
terragrunt.hcl ( I don't use inputs, in terragrunt.hcl I generate a vars file since I hit the system limit for commandline length )
# This will load all the locals from root.hcl and inject them here.
include "root" {
  path   = find_in_parent_folders("root.hcl")
  expose = true
}

locals {
  merged_locals = include.root.locals.merged_locals
}

terraform {
  source = include.root.locals.merged_locals
}

root.hcl -  I read the top most level here
vars = read_terragrunt_config("${local.og_tg_dir}/instance.hcl")

In instance.hcl I read and merge all lower levels
locals {
  merged_locals = merge(
    local.global_vars.locals,
    local.environment_vars.locals,
    local.subscription_vars.locals,
    local.region_vars.locals,
    local.service_vars.locals,
  )
  og_tg_dir = get_original_terragrunt_dir()

  service_vars      = read_terragrunt_config("${local.og_tg_dir}/../service.hcl")
  region_vars       = read_terragrunt_config("${local.og_tg_dir}/../../region.hcl")
  subscription_vars = read_terragrunt_config("${local.og_tg_dir}/../../../subscription.hcl")
  environment_vars  = read_terragrunt_config("${local.og_tg_dir}/../../../../environment.hcl")
  global_vars       = read_terragrunt_config("${local.og_tg_dir}/../../../../../globals.hcl")
}

Note: This is just snippets so it doesn't tell the whole story or describe the entire solution, but hopefully you get the gist of it.
And I do the same for service, region, sub, env. While also in each lower namespace I subtract those files that are higher up.
In service.hcl I do not load instance.hcl for example.
I do this because I want to gain access to all the variables and use them in a higher namespace.
An alternative could have been to merge it all the end instead of this in every single level. It takes like 40 seconds to parse everything.
I use the same approach for modules, so that I can override terraform module versions per instance, service, region, sub, env.. etc..
I've done this for quite a few of my projects.. if you know a better way or if you think I'm crazy for doing it this way, I'm always open to learn.

I came up with something very similar, but instead of using locals {} am using inputs = {} everywhere. This causes a bit less cognitive load and makes specifying inputs is a bit less verbose. The root module then merges all inputs from all layers.
Example of root module with this and a few more ideas:
locals {
  path_parts         = concat(split("/", path_relative_to_include()), ["", "", "", ""])
  common_config      = read_terragrunt_config("${get_parent_terragrunt_dir()}/common_config.hcl", { inputs = {} })
  environment_config = read_terragrunt_config("${get_parent_terragrunt_dir()}/${local.path_parts[0]}/environment_config.hcl", { inputs = {} })
  ...
  inputs = merge(
    {
      terraform_tag    = path_relative_to_include()
      environment_name = local.path_parts[0]
      ....
    },
    local.common_config.inputs,
    local.environment_config.inputs,
    ...
  )
}
inputs = local.inputs

@gw0 - is the above possible using yaml files instead of hcl files? We've already got the necessary configuration in yaml files which is already being used by other things? Making a hcl specific config file just for terraform would be a pain

@gw0 - is the above possible using yaml files instead of hcl files? We've already got the necessary configuration in yaml files which is already being used by other things? Making a hcl specific config file just for terraform would be a pain

Sure, a similar approach could be used with YAML. For YAML there is yamldecode() which is much more straightforward to use (kind-of-related https://terragrunt.gruntwork.io/docs/reference/built-in-functions/#sops_decrypt_file).

I came up with something very similar, but instead of using locals {} am using inputs = {} everywhere. This causes a bit less cognitive load and makes specifying inputs is a bit less verbose. The root module then merges all inputs from all layers.
Example of root module with this and a few more ideas:
locals {
  path_parts         = concat(split("/", path_relative_to_include()), ["", "", "", ""])
  common_config      = read_terragrunt_config("${get_parent_terragrunt_dir()}/common_config.hcl", { inputs = {} })
  environment_config = read_terragrunt_config("${get_parent_terragrunt_dir()}/${local.path_parts[0]}/environment_config.hcl", { inputs = {} })
  ...
  inputs = merge(
    {
      terraform_tag    = path_relative_to_include()
      environment_name = local.path_parts[0]
      ....
    },
    local.common_config.inputs,
    local.environment_config.inputs,
    ...
  )
}
inputs = local.inputs

The reason I don't use input is because of this issue: https://github.com/gruntwork-io/terragrunt/issues/2132

The reason I don't use input is because of this issue: #2132

Instead of cramming everything into inputs (meaning env vars), have you considered:

Passing just the file path and use Terraform to read the file?
Putting *.tf files that do one-off jobs next to terragrunt.hcl?

I don't cram everything into inputs :) hence I said The reason I don't use input is because of this issue: https://github.com/gruntwork-io/terragrunt/issues/2132
The ticket I referered to has a solution proposed by denis which I use.


Show deprecated stacks on website

Is your feature request related to a problem? Please describe.
Display deprecated stacks clearly on website.
Describe the solution you'd like
Could replace the stack description with the deprecated message.
Additional context
Related to PR #923

@ddunn2 @KyeMaloy97 @Bazif-Khan Would like to get your thoughts on how we might be able to best show this on the stacks page.

Assigning to Kye to work with David and Bazif and put a design proposal/screenshot of ideas into this issue.

Here is a first pass at the design me and Neeraj have spoken about, open for opinions, improvements or alternatives.

Thanks @KyeMaloy97 !
My first thoughts on the proposed design:
I like the use of an icon for indicating this stack is different from others.
I also like having a key to explain what the icon is for, but dont think hte current design gels with the checkbox lists in other sections. It seems a little out of place.
Lastly, not sure what is the equivalent for hover text on a mobile view.

@neeraj-laad we've just discussed this and Kye is going to try making the icon orange so it stands out a bit more.
Bazif thinks we can use on click for the hover text on mobile.
We've also agreed to remove the key and see how it looks, as you're right the key doesn't fit with the checkbox lists in the other sections.
So look out for an updated screenshot...

I have made the icon orange, one option for showing the message on mobile could that clicking the triangle shows an alert. This is how it would look on iOS:

Have also added some logic so the alert doesn't show on Desktop, only on mobile. On desktop hovering works as it did before.

This looks good enough to me.

@neeraj-laad  @helenmasters
Another point relevant to this discussion is the fact that java-microprofile features prominently in the "Most Popular" four stacks on the  https://appsody.dev/ homepage.
If that's calculated dynamically from downloads I realize it's non-trivial to change, but...  would be nice to not be pointing to this when we'd rather promote java-openliberty to any user.
Anything else we could do here?   Separate issue?  Thanks

+1 for deprecated stacks to drop off the "Most Popular" list on the front page and for the replacement stack to take its place.

It would be simple to remove the deprecated stack from that element, using something like a filter on the list that is retrieved from docker hub (how we get the pull counts at the moment) but I am not sure how complex it would be to replace the deprecated stack with the replacement stack as it would require working out what stack replaces the deprecated one, AFAIK that might not even always be the case (in cases where a stack is simply deprecated and theres no replacement).
Also, the text that goes in the deprecated field has no forced structure so working out if it contained a replacement stack, and working out what that stack is would be an issue in itself haha

+1 for deprecated stacks to drop off the "Most Popular" list on the front page and for the replacement stack to take its place.

Most popular means most popular and I would hope that OL would naturally replace MP over time. As Kye says, we can filter deprecated stacks out, but I don't think we should be trying to replace them.  That's is a whole different discussion where we would now be deciding what we want to showcase.

Having deprecated stacks removed from the "Most Popular" list is a start.
Can/will we redirect users from java-microprofile to java-openliberty too somehow?  This will be helpful to ensure that users pick up the replacement stack.

There is no mechanism in place for that at the moment as AFAIK, the stacks deprecation field i just a message and a date, so theres no defined place where a URL or stack name goes to define a replacement

Can/will we redirect users from java-microprofile to java-openliberty too somehow? This will be helpful to ensure that users pick up the replacement stack.

@yeekangc - not sure I understand what you are suggesting here. Please can you open a new issue for this and provide more of an explanation as to what you would like to see happen. At a minimum the MP stack README should have a clear message to use OL instead, which should be down to the stack owner.

For what we are designing here in this issue, besides marking a card (stack) as deprecated, can we at least provide an indication of the strategic replacement/alternative i.e. the next step?
Cc @awisniew90.

Agreed - perhaps in the warning message, instead of saying "Please use an alternative stack" we could suggest which stack to use or provide a link to it.

^^ @CameronMcWilliam @neeraj-laad  - please see comments for implementation considerations. Kye can pull whatever data you put in. If there is a strongly adhered to format for specifying a replacement stack, he can probably code to pull that out. Otherwise he can just print whatever is in there  ... and stack owners can decide what they want to say.

This is just a prototype. The warning message will actually be the message you put in stack.yaml and should contain the reason for deprecation and the recommended alternative.
This will be the same warning that CLI will show users' while working with a deprecated stack.

The website should not have to do any transformation. It should just spit out the deprecation message from the index.
@KyeMaloy97  I know we're facing some gatsby issues with merging this PR, so wanted to know if there is a simpler design we could go with as a first pass to get this in?

@neeraj-laad  So our options are what we discussed before this PR was opened, with having one stack at all times having a deprecated field on it because Gatsby pre v2.9 does not allow you to have a field referenced in the query that doesn't exist on any of the items its looking through, there is an API for it in post 2.9 but we can't use it.
So we either have to make sure there is always a deprecated stack, not the end of the world for now as you are about to deprecate one but for the future it may cause issues if you want to remove a stack from the website, leaving no deprecated ones. As soon as the updated YAML is built into the website, probably the following morning, the site will fail to build.
Another option is having the sample stack display on the site, with a deprecated field at all times but hide the stack so it never shows to an end user. That means it wont matter if any of the normal stacks lack deprecated fields as the sample one will always have the field available to satisfy the query.
The latter option will take longer as it is something new that hasn't been done yet whereas the first option should be faster as I had that working originally.


Error during migration: Bad state: Unrelated types

Bad state: Unrelated types: class Object and abstract class FutureOr  in (readData ?? (req, res) {if (req.bodyAsObject is! Data) {throw GalileoHttpException.badRequest(message: 'Invalid request body. Expected $Data; found ${req.bodyAsObject} instead.');} else {return req.bodyAsObject as Data;}})
dart migrate
Migrating D:\MyDartProjects\galileo\packages\framework

See https://dart.dev/go/null-safety-migration for a migration guide.

Analyzing project...
[-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\]No analysis issues found.

Generating migration suggestions...
[---------------------------------------/                                                                                ]Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:

https://github.com/dart-lang/sdk/issues/new
Please include the SDK version (2.12.4) in your bug report.

To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.

Exception details:

Bad state: Unrelated types: class Object and abstract class FutureOr<T> at offset 2391 in D:\MyDartProjects\galileo\packages\framework\lib\src\core\service.dart (readData ?? (req, res) {if (req.bodyAsObject is! Data) {throw GalileoHttpException.badRequest(message: 'Invalid request body. Expected $Data; found ${req.bodyAsObject} instead.');} else {return req.bodyAsObject as Data;}})

#0      DecoratedClassHierarchy.getDecoratedSupertype (package:nnbd_migration/src/decorated_class_hierarchy.dart:67:10)
#1      DecoratedClassHierarchy.asInstanceOf (package:nnbd_migration/src/decorated_class_hierarchy.dart:38:18)
#2      EdgeBuilder._decorateUpperOrLowerBound (package:nnbd_migration/src/edge_builder.dart:2108:18)
#3      EdgeBuilder._decorateUpperOrLowerBound (package:nnbd_migration/src/edge_builder.dart:2070:14)
#4      EdgeBuilder._decorateUpperOrLowerBound (package:nnbd_migration/src/edge_builder.dart:2154:26)
#5      EdgeBuilder.visitBinaryExpression (package:nnbd_migration/src/edge_builder.dart:495:26)
#6      BinaryExpressionImpl.accept (package:analyzer/src/dart/ast/ast.dart:967:49)
#7      EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#8      EdgeBuilder._handleAssignment (package:nnbd_migration/src/edge_builder.dart:2329:20)
#9      EdgeBuilder.visitAssignmentExpression (package:nnbd_migration/src/edge_builder.dart:409:26)
#10     AssignmentExpressionImpl.accept (package:analyzer/src/dart/ast/ast.dart:715:49)
#11     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#12     EdgeBuilder.visitExpressionStatement (package:nnbd_migration/src/edge_builder.dart:801:25)
#13     ExpressionStatementImpl.accept (package:analyzer/src/dart/ast/ast.dart:3676:49)
#14     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#15     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#16     GeneralizingAstVisitor.visitStatement (package:analyzer/dart/ast/visitor.dart:517:39)
#17     GeneralizingAstVisitor.visitBlock (package:analyzer/dart/ast/visitor.dart:165:31)
#18     BlockImpl.accept (package:analyzer/src/dart/ast/ast.dart:1083:49)
#19     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#20     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#21     GeneralizingAstVisitor.visitFunctionBody (package:analyzer/dart/ast/visitor.dart:324:45)
#22     GeneralizingAstVisitor.visitBlockFunctionBody (package:analyzer/dart/ast/visitor.dart:168:55)
#23     BlockFunctionBodyImpl.accept (package:analyzer/src/dart/ast/ast.dart:1038:49)
#24     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#25     EdgeBuilder._handleExecutableDeclaration (package:nnbd_migration/src/edge_builder.dart:2488:7)
#26     EdgeBuilder.visitConstructorDeclaration (package:nnbd_migration/src/edge_builder.dart:712:5)
#27     ConstructorDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:2566:15)
#28     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#29     EdgeBuilder._dispatchList (package:nnbd_migration/src/edge_builder.dart:2229:7)
#30     EdgeBuilder.visitClassOrMixinOrExtensionDeclaration (package:nnbd_migration/src/edge_builder.dart:607:7)
#31     EdgeBuilder.visitClassDeclaration (package:nnbd_migration/src/edge_builder.dart:574:5)
#32     ClassDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:1536:49)
#33     EdgeBuilder._dispatch (package:nnbd_migration/src/edge_builder.dart:2207:24)
#34     EdgeBuilder.visitNode (package:nnbd_migration/src/edge_builder.dart:1340:9)
#35     GeneralizingAstVisitor.visitCompilationUnit (package:analyzer/dart/ast/visitor.dart:202:51)
#36     CompletenessTracker.visitCompilationUnit.<anonymous closure> (package:nnbd_migration/src/utilities/completeness_tracker.dart:52:24)
#37     PermissiveModeVisitor.reportExceptionsIfPermissive (package:nnbd_migration/src/utilities/permissive_mode.dart:26:24)
#38     CompletenessTracker.visitCompilationUnit (package:nnbd_migration/src/utilities/completeness_tracker.dart:43:5)
#39     CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2134:49)
#40     NullabilityMigrationImpl.processInput (package:nnbd_migration/src/nullability_migration_impl.dart:244:12)
#41     NonNullableFix.processUnit (package:nnbd_migration/src/front_end/non_nullable_fix.dart:164:15)
#42     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1154:19)
#43     _FixCodeProcessor.runLaterPhases.<anonymous closure> (package:nnbd_migration/migration_cli.dart:1152:28)
#44     _FixCodeProcessor.processResources (package:nnbd_migration/migration_cli.dart:1081:30)
<asynchronous suspension>
#45     _FixCodeProcessor.runLaterPhases (package:nnbd_migration/migration_cli.dart:1152:5)
<asynchronous suspension>
#46     MigrationCliRunner.run (package:nnbd_migration/migration_cli.dart:749:24)
<asynchronous suspension>
#47     MigrateCommand.run (package:nnbd_migration/migration_cli.dart:185:7)
<asynchronous suspension>
#48     CommandRunner.runCommand (package:args/command_runner.dart:196:13)
<asynchronous suspension>
#49     DartdevRunner.runCommand (package:dartdev/dartdev.dart:199:18)
<asynchronous suspension>
#50     runDartdev (package:dartdev/dartdev.dart:53:16)
<asynchronous suspension>
#51     main (file:///C:/b/s/w/ir/cache/builder/sdk/pkg/dartdev/bin/dartdev.dart:11:3)
<asynchronous suspension>

PS D:\MyDartProjects\galileo\packages\framework>

* Dart SDK version: 2.12.4 (stable) (Thu Apr 15 12:26:53 2021 +0200) on "windows_x64"
* Windows

@stereotype441
I didn't make any progress in the migration of this package (https://pub.dev/packages/galileo_framework), because after using the tool I have many errors and problems, and it doesn't run the tests

I think a duplicate of https://github.com/dart-lang/sdk/issues/45663

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Leek website not working

on website receiving following error
This site can’t be reached tryleek.com’s DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE

The issue is fixed, the website is back online.


XLSX formula errors read as strings

Same with CSV, but is unavoidable. XLS OK.
Example:
ExcelNA.xlsx
ExcelNA.zip (zipped xls)
https://stackoverflow.com/questions/49857097/exceldatareader-reading-values-like-n-a-as-string-instead-of-null-or-missing-wh

Cells containing strings matching errors are now read as those errors. E.g. a cell value of "#N/A" will be read as null.
A little weird, I know, but shouldn't a string that just happens to look like an error still be read as a string?

@sporifolous Hi, the intended behaviour should be like you expect. I.e a cell with an error should be returned as null, whereas a cell with f.ex the string  "#N/A" should be returned as a string with the value "#N/A". The XLSX XML has a flag per cell whether the contents is an error or a string, and the reader returns null only for the errors:
https://github.com/ExcelDataReader/ExcelDataReader/blob/e5b7d41b580603c866b9097496139080c0bba105/src/ExcelDataReader/Core/OpenXmlFormat/XlsxWorksheet.cs#L579-L580
Are you experiencing something different?

I created a new spreadsheet in Excel, and manually input the string "#N/A" into a cell, and the saved XML looks like this:
<c r="A1" t="e"><v>#N/A</v></c>

Apparently Excel recognizes the string and automatically sets t="e", which basically means the datatype for the cell is "Error", which always returns as null in ExcelDataReader.
(The "Text" cell formatting is set separately from the cell type and shouldn't have any effect on this)
So that explains what's going on. Looks like some kind of edge case. Not sure how to best handle this, maybe some kind of GetCellError(i) method to get the error string for a cell.


2600hz changes

some changes that fix/enhance jesse

fixes mixing draft3/draft4 schemas
export current_schema_id
allows extra validator
explicit error for enum
allow a setter_fun in options
set defaults

would you care give some detailed rationale for

allow a setter_fun in schema validator
defaults

thanks

@andreineculau
for defaults
if you give an empty object {} for a schema with defaults in its properties, it will fill up the object with the defaults and continue validation.
for setter_fun
when applying default, setter_fun will allow to actually set the value and return the value as part of validation.
example below for getting defaults for a schema
Options = [{'schema_loader_fun', fun kz_json_schema:fload/1}
                 ,{'allowed_errors', 'infinity'}
                 ,{'extra_validator', fun kz_json_schema_extensions:extra_validator/2}
                 ,{'setter_fun', fun kz_json:set_value/3}
                 ],
{ok, JObj} = kz_json_schema:validate(<<"system_config.conferences">>, kz_json:new(), Options),
io:format("~s~n", [kz_json:encode(JObj, ['pretty'])]).

{
  "entry_tone" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,659);v=-7;>=3;+=.1;%(800,0,659,783)",
  "exit_tone" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,440);v=-7;>=3;+=.1;%(800,0,349,440)",
  "moderator_entry_tone" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,659);v=-7;>=3;+=.1;%(800,0,659,783)",
  "moderator_exit_tone" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,440);v=-7;>=3;+=.1;%(800,0,349,440)",
  "number_timeout" : 5000,
  "pin_timeout" : 5000,
  "profiles" : {
    "default" : {
      "alone-sound" : "prompt://system_media/conf-alone/en-us",
      "caller-controls" : "default",
      "comfort-noise" : 1000,
      "deaf-sound" : "prompt://system_media/conf-deaf/en-us",
      "energy-level" : 20,
      "enter-sound" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,659);v=-7;>=3;+=.1;%(800,0,659,783)",
      "exit-sound" : "tone_stream://v=-7;>=2;+=.1;%(300,0,523,440);v=-7;>=3;+=.1;%(800,0,349,440)",
      "interval" : 20,
      "locked-sound" : "prompt://system_media/conf-max_participants/en-us",
      "max-member" : 200,
      "max-members-sound" : "prompt://system_media/conf-max_participants/en-us",
      "member-enter-sound" : "prompt://system_media/conf-joining_conference/en-us",
      "moh-sound" : "$${hold_music}",
      "muted-sound" : "prompt://system_media/conf-muted/en-us",
      "rate" : 8000,
      "undeaf-sound" : "prompt://system_media/conf-undeaf/en-us",
      "unmuted-sound" : "prompt://system_media/conf-unmuted/en-us"
    },
    "page" : {
      "caller-controls" : "default",
      "comfort-noise" : 1000,
      "energy-level" : 20,
      "enter-sound" : "",
      "interval" : 20,
      "moh-sound" : "",
      "rate" : 8000
    }
  },
  "review_name" : false,
  "route_win_timeout" : 3000,
  "support_name_announcement" : true
}

@lazedo thanks for the clear explanation!
I can only think of two requests:

can you add an option for this behaviour e.g. use_default, which would be on by default
setter_fun maybe renamed to default_setter_fun ?!

Wdyt?

@andreineculau i'm ok with adding the use_default and we can default it to false to preserve current behaviour. thoughts?
as for the the setter_fun, why the rename ? if its not provided, there's no default to set the values, and since the library can act on different json implementations (jsx and other) there's really no easy way to set a default_setter_fun

@andreineculau i ended up adding a 'validator_options' to control the defaults behaviour.
use_defaults -> to control applying defaults
'apply_defaults_to_empty_objects' -> to control if we should iterate object shcema properties and apply defaults.
this last is to bypass a recursive default {} with {$ref, #}
let me know if you agree or if there's anything else needed to wok on.
Thanks

@andreineculau hi, anything else required here ?

yes, I'm required :( and I'm finding it hard to get time on my hands
On Mon, Mar 27, 2017 at 7:08 PM, lazedo<EMAIL_ADDRESS>wrote:

@andreineculau https://github.com/andreineculau hi, anything else
required here ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/for-GET/jesse/pull/42#issuecomment-289518813, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArOQWLNfrnhFCMw7ENPjjsfCkP99pF_ks5rp-0QgaJpZM4MLSoq
.

--
andreineculau.com http://www.andreineculau.com

@andreineculau ping. we would love to create a 1.5 release after this merge

closing in favour of #51 and #52 (other commits already merged onto master). it was impossible for me to review properly as a mash


fix unique route in http_request_duration_seconds_bucket metric

fix unique route in http_request_duration_seconds_bucket metric

Coverage increased (+0.6%) to 92.92% when pulling 9469a40e7fcdcfcb5ff9fa1fd1b14689e1d063b6 on fix-unique-path-metrics into cd74075c0e54d3bd6dfdff3dc73d835b69922d72 on master.

Coverage increased (+0.6%) to 92.92% when pulling 9469a40e7fcdcfcb5ff9fa1fd1b14689e1d063b6 on fix-unique-path-metrics into cd74075c0e54d3bd6dfdff3dc73d835b69922d72 on master.


Collect extractors into request module

Motivation and Context
In axum there is a definitive module which exports extractors.
https://docs.rs/axum/latest/axum/extract/index.html
With pub FromParts being released shortly we might want to collect extractors as well.
Description

Move ConnectInfo and its associated Layer into request::connect_info.
Move Extension into request::extension.

Notes

This is technically not a breaking change as long as it's merged prior to 0.52. We re-export Extension from extensions and ConnectInfo API has not been released yet.

This should be merged before https://github.com/awslabs/smithy-rs/pull/1886


Setup ci for apiserver

Why are these changes needed?
CI doesn't cover new components, since we plan to cut a v0.2.0 release soon, this should be definitely improved.
Related issue number
Address https://github.com/ray-project/kuberay/issues/117
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

/LGTM


Backport Eventing StackDriver metrics to release-0.10 (#846)

Updating StackDriver metrics for eventing.

/assign @Harwayne
/assign @yanweiguo to approve once @Harwayne lgtms

/test pull-knative-pkg-unit-tests

Some cluster creation problem:
2019/11/07 18:11:12 Error during cluster creation: 'timed out waiting'. Retry another region "us-west1" for cluster creation
rerunning UTs

Discussed this with @nachocano
I'm going to:
/lgtm
/approve
For now, but all this Stackdriver/Google-specific metrics stuff living in pkg is not what was intended, and we should aim for 0.11 to have a properly pluggable metrics subsystem so that "knative.dev/internal/..." stuff for Google integration can be done in a Google-specific repo rather than at the font of all waters.

/test pull-knative-pkg-unit-tests

/test pull-knative-pkg-unit-tests

/lgtm


ci: add yuth to mergify

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Mergifyio refresh


Add option to download the AASX file with concept descriptions

Is your feature request related to a problem? Please describe.
When downloading the AASX, the concept descriptions are not exported by default.
Describe the solution you'd like
An option to choose whether to export the concept descriptions or not.

This actually seems to be a backend problem (AAS Environment serialization endpoint). The AAS Web UI already has this feature:
https://github.com/eclipse-basyx/basyx-applications/blob/319d484c01f51266cbd4c8eb00bb2a6045492a8a/aas-gui/Frontend/aas-web-gui/src/components/AppNavigation/AASList.vue#L369

This is now fixed here: https://github.com/eclipse-basyx/basyx-java-server-sdk/pull/320
Feel free to close this issue.


Homework Kalpan Bhalsod

Name: KALPAN BHALSOD
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/kalmax/

Attach the homework screenshots below for both step II and step III:

Hey KALPAN BHALSOD, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/tB6Sqyk0QeGVpB2PdF7Zvw


Unable to generate build files for Linux

Issue
My app used to compile/build without any issues on all platforms. A few weeks back, my operating system, Pop OS, upgraded from 21.10 to 22.04. Other than that, I do not remember anything else changing within my local machine where I code. Since then, I have been unable to build/run my app in linux. Keep in mind that my app still builds and runs perfectly fine on other platforms.
Below, you can find two methods. One is simple "run without debugging" and the other is the build command for the terminal. Both produce the same output but I have mentioned both of them here. I do not suspect any issue in my code as it ran flawlessly before. But if you need me to share it, I can.
Furthermore, I do a completly fresh install of my OS every couple months. I did one yesterday and installed all necessary SDKs, etc. hoping that maybe a fresh install of Flutter might fix this. I am still getting the exact same error.
Steps to Reproduce
Case A

Press CTRL + F5

Case B

Execute flutter build linux

Logs
Case A (from the debug console)
Launching lib/main.dart on Linux in debug mode...
lib/main.dart:1
CMake Error at /snap/flutter/111/usr/share/cmake-3.10/Modules/CMakeTestCXXCompiler.cmake:45 (message):
  The C++ compiler

    "/snap/flutter/current/usr/bin/clang++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/abdulmuezz/Documents/flutter_projects/franchise_manager/build/linux/x64/debug/CMakeFiles/CMakeTmp

    Run Build Command:"/snap/flutter/current/usr/bin/ninja" "cmTC_f7ee3"
    [1/2] Building CXX object CMakeFiles/cmTC_f7ee3.dir/testCXXCompiler.cxx.o
    [2/2] Linking CXX executable cmTC_f7ee3
    FAILED: cmTC_f7ee3
    : && /snap/flutter/current/usr/bin/clang++    -L/snap/flutter/current/usr/lib/gcc/x86_64-linux-gnu/8 -L/snap/flutter/current/usr/lib/x86_64-linux-gnu -lblkid -lgcrypt -llzma -lpthread -ldl -L/snap/flutter/current/usr/lib/ CMakeFiles/cmTC_f7ee3.dir/testCXXCompiler.cxx.o  -o cmTC_f7ee3   && :
    /snap/flutter/current/usr/bin/ld: warning: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/crt1.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0008002
    /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libgcc_s.so.1: undefined reference to<EMAIL_ADDRESS>    //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>    //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)

Exception: Unable to generate build files
Exited (sigterm)

Case B (from the terminal output)
abdulmuezz@pop-os:~/Documents/flutter_projects/franchise_manager$ flutter build linux

💪 Building with sound null safety 💪

CMake Error at /snap/flutter/111/usr/share/cmake-3.10/Modules/CMakeTestCXXCompiler.cmake:45 (message):
  The C++ compiler

    "/snap/flutter/current/usr/bin/clang++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/abdulmuezz/Documents/flutter_projects/franchise_manager/build/linux/x64/release/CMakeFiles/CMakeTmp

    Run Build Command:"/snap/flutter/current/usr/bin/ninja" "cmTC_5628c"
    [1/2] Building CXX object CMakeFiles/cmTC_5628c.dir/testCXXCompiler.cxx.o
    [2/2] Linking CXX executable cmTC_5628c
    FAILED: cmTC_5628c
    : && /snap/flutter/current/usr/bin/clang++    -L/snap/flutter/current/usr/lib/gcc/x86_64-linux-gnu/8 -L/snap/flutter/current/usr/lib/x86_64-linux-gnu -lblkid -lgcrypt -llzma -lpthread -ldl -L/snap/flutter/current/usr/lib/ -L/snap/flutter/current/usr/lib/gcc/x86_64-linux-gnu/8 -L/snap/flutter/current/usr/lib/x86_64-linux-gnu -lblkid -lgcrypt -llzma -lpthread -ldl -L/snap/flutter/current/usr/lib/ CMakeFiles/cmTC_5628c.dir/testCXXCompiler.cxx.o  -o cmTC_5628c   && :
    /snap/flutter/current/usr/bin/ld: warning: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/crt1.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0008002
    /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libgcc_s.so.1: undefined reference to<EMAIL_ADDRESS>    //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>    //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)

Building Linux application...
Unable to generate build files

Executing flutter run --verbose
[  +66 ms] executing: uname -m
[  +33 ms] Exit code 0 from: uname -m
[        ] x86_64
[   +6 ms] executing: [/home/abdulmuezz/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +6 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] ee4e09cce01d6f2d7f4baebd247fde02e5008851
[        ] executing: [/home/abdulmuezz/snap/flutter/common/flutter/] git tag --points-at ee4e09cce01d6f2d7f4baebd247fde02e5008851
[  +16 ms] Exit code 0 from: git tag --points-at ee4e09cce01d6f2d7f4baebd247fde02e5008851
[        ] 3.0.0
[  +12 ms] executing: [/home/abdulmuezz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +5 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/abdulmuezz/snap/flutter/common/flutter/] git ls-remote --get-url origin
[   +6 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +119 ms] executing: [/home/abdulmuezz/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[   +7 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +75 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +93 ms] executing: /home/abdulmuezz/Android/Sdk/platform-tools/adb devices -l
[  +45 ms] List of devices attached
[   +6 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +91 ms] Multiple devices found:
[ +881 ms] Linux (desktop) • linux  • linux-x64      • Pop!_OS 22.04 LTS 5.17.5-76051705-generic
[        ] Chrome (web)    • chrome • web-javascript • Chromium 101.0.4951.64 snap
[        ] [1]: Linux (linux)
[        ] [2]: Chrome (chrome)
[   +1 ms] Please choose one (To quit, press "q/Q")
[        ] :
[+8560 ms] 1
[  +37 ms] Skipping pub get: version match.
[  +89 ms] Found plugin move_to_background at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/move_to_background-1.0.2/
[  +12 ms] Found plugin path_provider at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.10/
[   +3 ms] Found plugin path_provider_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_android-2.0.14/
[   +2 ms] Found plugin path_provider_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_ios-2.0.9/
[   +2 ms] Found plugin path_provider_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.1.6/
[   +4 ms] Found plugin path_provider_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.6/
[   +4 ms] Found plugin path_provider_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.6/
[  +29 ms] Found plugin uni_links at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links-0.5.1/
[   +4 ms] Found plugin uni_links_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links_web-0.1.0/
[   +5 ms] Found plugin url_launcher at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-6.1.2/
[   +2 ms] Found plugin url_launcher_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_android-6.0.17/
[   +2 ms] Found plugin url_launcher_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_ios-6.0.16/
[   +4 ms] Found plugin url_launcher_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_linux-3.0.1/
[   +4 ms] Found plugin url_launcher_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-3.0.1/
[   +5 ms] Found plugin url_launcher_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-2.0.11/
[   +2 ms] Found plugin url_launcher_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_windows-3.0.1/
[  +99 ms] Found plugin move_to_background at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/move_to_background-1.0.2/
[   +3 ms] Found plugin path_provider at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.10/
[   +1 ms] Found plugin path_provider_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_android-2.0.14/
[        ] Found plugin path_provider_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_ios-2.0.9/
[        ] Found plugin path_provider_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.1.6/
[        ] Found plugin path_provider_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.6/
[   +1 ms] Found plugin path_provider_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.6/
[  +10 ms] Found plugin uni_links at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links-0.5.1/
[   +1 ms] Found plugin uni_links_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links_web-0.1.0/
[   +1 ms] Found plugin url_launcher at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-6.1.2/
[   +1 ms] Found plugin url_launcher_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_android-6.0.17/
[   +1 ms] Found plugin url_launcher_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_ios-6.0.16/
[        ] Found plugin url_launcher_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_linux-3.0.1/
[   +2 ms] Found plugin url_launcher_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-3.0.1/
[   +3 ms] Found plugin url_launcher_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-2.0.11/
[   +1 ms] Found plugin url_launcher_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_windows-3.0.1/
[  +85 ms] Generating /home/abdulmuezz/Documents/flutter_projects/franchise_manager/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +133 ms] Initializing file store
[  +12 ms] Skipping target: gen_localizations
[   +4 ms] gen_dart_plugin_registrant: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents:
/home/abdulmuezz/Documents/flutter_projects/franchise_manager/.dart_tool/package_config_subset,/home/abdulmuezz/Documents/flutter_projects/franchise_manager/.dart_tool/flutter_build/dart_plug
in_registrant.dart}
[  +43 ms] Found plugin move_to_background at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/move_to_background-1.0.2/
[   +2 ms] Found plugin path_provider at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.10/
[   +1 ms] Found plugin path_provider_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_android-2.0.14/
[   +1 ms] Found plugin path_provider_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_ios-2.0.9/
[   +1 ms] Found plugin path_provider_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.1.6/
[   +1 ms] Found plugin path_provider_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.6/
[   +1 ms] Found plugin path_provider_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.6/
[  +19 ms] Found plugin uni_links at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links-0.5.1/
[   +2 ms] Found plugin uni_links_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/uni_links_web-0.1.0/
[   +2 ms] Found plugin url_launcher at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-6.1.2/
[   +1 ms] Found plugin url_launcher_android at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_android-6.0.17/
[   +1 ms] Found plugin url_launcher_ios at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_ios-6.0.16/
[   +3 ms] Found plugin url_launcher_linux at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_linux-3.0.1/
[   +4 ms] Found plugin url_launcher_macos at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_macos-3.0.1/
[   +4 ms] Found plugin url_launcher_web at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_web-2.0.11/
[   +1 ms] Found plugin url_launcher_windows at /home/abdulmuezz/snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_windows-3.0.1/
[  +31 ms] gen_dart_plugin_registrant: Complete
[   +2 ms] Skipping target: _composite
[   +6 ms] complete
[  +11 ms] Launching lib/main.dart on Linux in debug mode...
[  +11 ms] /home/abdulmuezz/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/abdulmuezz/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/snapshots/frontend_server.dart.snapshot --sdk-root
/home/abdulmuezz/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names --experimental-emit-debug-metadata
-DFLUTTER_WEB_AUTO_DETECT=true --output-dill /tmp/flutter_tools.PVCZLC/flutter_tool.NGNQRP/app.dill --packages
/home/abdulmuezz/Documents/flutter_projects/franchise_manager/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation
--filesystem-scheme org-dartlang-root --initialize-from-dill build/c075001b96339384a97db4862b8ab8db.cache.dill.track.dill --source
/home/abdulmuezz/Documents/flutter_projects/franchise_manager/.dart_tool/flutter_build/dart_plugin_registrant.dart --source package:flutter/src/dart_plugin_registrant.dart
-Dflutter.dart_plugin_registrant=file:///home/abdulmuezz/Documents/flutter_projects/franchise_manager/.dart_tool/flutter_build/dart_plugin_registrant.dart
--enable-experiment=alternative-invalidation-strategy
[  +48 ms] Building Linux application...
[  +32 ms] <- compile package:franchise_manager/main.dart
[   +3 ms] executing: [build/linux/x64/debug/] cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64 /home/abdulmuezz/Documents/flutter_projects/franchise_manager/linux
[ +209 ms] -- The CXX compiler identification is Clang 6.0.0
[   +5 ms] -- Check for working CXX compiler: /snap/flutter/current/usr/bin/clang++
[ +149 ms] -- Check for working CXX compiler: /snap/flutter/current/usr/bin/clang++ -- broken
[   +1 ms] CMake Error at /snap/flutter/111/usr/share/cmake-3.10/Modules/CMakeTestCXXCompiler.cmake:45 (message):
[   +2 ms]   The C++ compiler
[        ]     "/snap/flutter/current/usr/bin/clang++"
[        ]   is not able to compile a simple test program.
[        ]   It fails with the following output:
[        ]     Change Dir: /home/abdulmuezz/Documents/flutter_projects/franchise_manager/build/linux/x64/debug/CMakeFiles/CMakeTmp
[        ]     Run Build Command:"/snap/flutter/current/usr/bin/ninja" "cmTC_e9d5e"
[        ]     [1/2] Building CXX object CMakeFiles/cmTC_e9d5e.dir/testCXXCompiler.cxx.o
[        ]     [2/2] Linking CXX executable cmTC_e9d5e
[        ]     FAILED: cmTC_e9d5e
[        ]     : && /snap/flutter/current/usr/bin/clang++    -L/snap/flutter/current/usr/lib/gcc/x86_64-linux-gnu/8 -L/snap/flutter/current/usr/lib/x86_64-linux-gnu -lblkid -lgcrypt -llzma
-lpthread -ldl -L/snap/flutter/current/usr/lib/ CMakeFiles/cmTC_e9d5e.dir/testCXXCompiler.cxx.o  -o cmTC_e9d5e   && :
[        ]     /snap/flutter/current/usr/bin/ld: warning: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/crt1.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0008002
[        ]     /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libgcc_s.so.1: undefined reference to<EMAIL_ADDRESS>[        ]     //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>[        ]     //lib/x86_64-linux-gnu/libgpg-error.so.0: undefined reference to<EMAIL_ADDRESS>[        ]     clang: error: linker command failed with exit code 1 (use -v to see invocation)
[        ]     ninja: build stopped: subcommand failed.
[        ]   CMake will not be able to correctly generate this project.
[        ] Call Stack (most recent call first):
[        ]   CMakeLists.txt:3 (project)
[        ] -- Configuring incomplete, errors occurred!
[        ] See also "/home/abdulmuezz/Documents/flutter_projects/franchise_manager/build/linux/x64/debug/CMakeFiles/CMakeOutput.log".
[        ] See also "/home/abdulmuezz/Documents/flutter_projects/franchise_manager/build/linux/x64/debug/CMakeFiles/CMakeError.log".
[  +23 ms] Building Linux application... (completed in 418ms)
[+13966 ms] Exception: Unable to generate build files
[        ] "flutter run" took 24,928ms.
[   +6 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:699:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1183:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:94:3)
           <asynchronous suspension>

[ +247 ms] ensureAnalyticsSent: 245ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

Executing flutter analyze
Analyzing franchise_manager...

   info • Depend on referenced packages • lib/pages/page_add/widgets/fields/field_date.dart:4:8 • depend_on_referenced_packages
   info • Depend on referenced packages • lib/pages/page_add/widgets/fields/field_date_range.dart:4:8 • depend_on_referenced_packages

2 issues found. (ran in 1.9s)

Executing flutter doctor -v
[✓] Flutter (Channel stable, 3.0.0, on Pop!_OS 22.04 LTS 5.17.5-76051705-generic, locale en_US.UTF-8)
    • Flutter version 3.0.0 at /home/abdulmuezz/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ee4e09cce0 (10 days ago), 2022-05-09 16:45:18 -0700
    • Engine revision d1b9a6938a
    • Dart version 2.17.0
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /home/abdulmuezz/Android/Sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /snap/android-studio/121/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /snap/bin/chromium

[✓] Linux toolchain - develop for Linux desktop
    • clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
    • cmake version 3.10.2
    • ninja version 1.8.2
    • pkg-config version 0.29.1

[✓] Android Studio (version 2021.2)
    • Android Studio at /snap/android-studio/121/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.67.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.40.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Pop!_OS 22.04 LTS 5.17.5-76051705-generic
    • Chrome (web)    • chrome • web-javascript • Chromium 101.0.4951.64 snap

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @muezz, Did you install flutter via snap? if yes this is very likely an issue with flutter_snap. This is a duplicate of https://github.com/flutter/flutter/issues/102678 (closed)
Closing as per the response here https://github.com/flutter/flutter/issues/102678#issuecomment-1114103944

@maheshmnj  Thanks for the response. I came from discord where a couple other people were also having this issue. At least now its clear that it isnt a flutter issue and its only because of the snap packaging system. Hopefully they fix it soon (I went to their repo and saw that someone else has already opened this issue).


update ray cmake build process

What do these changes do?

use cmake to build ray project instead of build.sh script.
remove the src/common/cmake/Common.cmake file, which added a lot of useless produces in cmake.

cmake supports build (add thirdparty dependency) concurrently, which improves the build performance. And for IDE, it has better integration with cmake.
Related issue number

@guoyuhong
besides, I push the pr just to make the ray cmake better. you can still use build.sh to build the project.
It still lacks of credis/redis support. we can add it later in ray if needed.

thanks for working on this. Do you have any numbers that compare the perf impact? (how much time does it takes for a clean build before and now?)


How to compile the library libblst.a for iOS platform

Hello, we need to compile your library for ios platform. We tried many ways, we do not understand how to do it. We would be grateful if you could explain. As I understand it, you need to compile under arm64

blst/build.sh 'CC="xcrun -sdk iphoneos cc -arch arm64"'

@dot-asm Thank you, I success managed to compile for the device, but for some reason error for the simulator, the compiler. May be do have a some idea, for fix this problem?

Accept command:
./build.sh 'CC="xcrun -sdk iphonesimulator cc -arch arm64"'
But now I need the need to have the possibility in one file for both the device and the simulator, any ideas?

Here is the secret. My experience with iOS is relatively limited, and non-existent with simulator. I've managed to test the Rust build on an iPad at an earlier point, so I know it works in principle. Then I simply recognized that spaces in arguments to build.sh don't work as intuitively expected, for example as build.sh CFLAGS="-arch arm64" and figured how to make them, spaces, work. That is all, I have nothing left to give. I see no reason for why you can't figure out the rest by yourself.


Typos + english wording

Ok I merge that manually because of conflicts with other PR. Hope I didn't mess it up :) Thanks a lot for your contribution. Do you want to be added to a CONTRIBUTORS file, and if yes, under which name ?


Fix formatting

Description
Fix formatting
Checklist:

[ ] I've made sure that tests/test_cookiecutter_generation.py is updated accordingly (especially if adding or updating a template option)
[ ] I've updated the documentation or confirm that my change doesn't require any updates

Rationale
Page was not rendered properly.

Thanks!


OC-26.1 | remove deviation and fix verification

Made below changes:

Remove deviation
In verification for ntpServer NI , right now got and want are switched, so fixed it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


colmena: init at 0.2.0

Motivation for this change
Colmena is a simple, stateless NixOS deployment tool.
This is the first stable release of the tool, submitted here so it can be easily installed from Nixpkgs.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Added testVersion test in passthru.tests.version. Thanks @0x4A6F.

🎉


Add "Copy to clipboard" button to message action sheet

This leaves some TODOs in the tests, for testing code that calls into a Flutter plugin. Greg is working on a good way to do that; see https://github.com/zulip/zulip-flutter/pull/204#discussion_r1253664445.
Empirically, the relevant calls here return Futures that never resolve, which will be fine until we want to stub out the native-code functionality.
Fixes: #132

Thanks for the review! Revision pushed, with:

tests of copyWithPopup
clipboard checks in the message-action-sheet tests for "Copy message text"

Thanks for the review! Revision pushed.

Thanks for the revision! Sorry for the delayed review. All looks good; merging.


Improvement of the visualization code

Major changes

visualization of SlidingWindowResults changed to one indicator = one row. Gives the following:

visualization now supports SegmentedWindowResults and gives the following:
. Note that the visualisation of the surrogate change metrics is a bit tricky here, since it is a single value per segment. Suggestions to improve the current solution (scatterplot) are welcome!
visualization for SlidingWindowResults and SegmentedWindowResults rely on same functions so that maintenance easier

Minors

tutorial.jl adapted to make use of the new visualization
tutorial.jl adapted to include segmented windows in the description
TITvisualization.jl changed for less ambiguous name TransitionVisualizations.jl
fix references in docs

Codecov Report
Attention: 89 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (main@9943887). Click here to learn what that means.

Files
Patch %
Lines

ext/TransitionVisualizations.jl
0.00%
89 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage        ?   36.17%
=======================================
  Files           ?       18
  Lines           ?      445
  Branches        ?        0
=======================================
  Hits            ?      161
  Misses          ?      284
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

also, please add a top-level codecov.yml file that ingores the files with plotting from the test coverage so that we don't get reports of low coverage, similar to here: https://github.com/JuliaDynamics/Attractors.jl/blob/main/codecov.yml

My answer above points out that I was missing the use of contents instead of content, which you did not comment. But ok, now it is implemented and should be looking good.


train ssdlite mobilenetv2, enconter the name error

raise ValueError('Cannot find output that matches name \"%s\"' % index)

ValueError: Cannot find output that matches name "mobilenetv20_features_relu61_relu6"
but i visualize the  pretrained mobilenetV2 structure, it does has the name.

I solve it myself


Feat/kyverno

Description of the change
Brings the kyverno to the cluster
Benefits or applicable issues
makes the gatus monitoring much easier

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by