chore(superchain): maven version, docs: CONTRIBUTING.md

This PR resolves Issue #4080 and bumps version of the maven from 3.9.2 to 3.9.3.

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

note:
My Environment: Ubuntu 22.04.2 LTS x86_64
The build command exists in following
https://github.com/aws/jsii/blob/877cdf8e09f79a0c09debbb67856a651bdacc318/.github/workflows/docker-images.yml#L134-L145

Sorry I forgotten option --target.
Pushed it.


Rename updates Formrecognizer

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-formrecognizer


Feature/models

I stubbed out these models and I figured it was better to get these into master soon so that others can start using them.

Looks good to me!


Adding pie chart and testing it for various meal ingredients

Check pie chart for all ingredients and varying number of ingredients


docs: add testing guide for Tegel and link in README

Describe pull-request
I have written documentation for how we do testing within Tegel. Please have a look at this and let me know what you think.
Issue Linking:
CDEP-2939

Looks good, but seems as though some additional files where added that should not be in this PR?

Looks good, but seems as though some additional files where added that should not be in this PR?

I think rebase will sort it out.


update set value description

thank you @adhrinae

@kotarella1110 I will merge this PR in, you can translate the Japanese version whenever you have time :) and thank you 👍

@bluebill1049 OK! I will translate when i have time :muscle:


Cannot read property 'Annotation' of undefined     at Object.6../annotation.js?please find some solution for this i am struck in that error after give its reference

Uncaught TypeError: Cannot read property 'Annotation' of undefined
at Object.6../annotation.js (chartjs-plugin-annotation.js:451)
at s (chartjs-plugin-annotation.js:10)
at e (chartjs-plugin-annotation.js:10)
at chartjs-plugin-annotation.js:10

Do you have a test case for this?

Closing since there is no test case. @heenaMahajan please provide a CodePen reproducing your issue and then we can re-open this.


Python 3 fixes for GCP auth and Avro IO

This change fixes some issues encountered when running batch Beam Python 3 pipelines on Dataflow.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


ref #1569 -- more thorough check for menu children

Ticket: #1569
Scrutinizer flagged an ambiguous conditional to clarify ...

Coverage remained the same at 94.061% when pulling 4791dfa023561eab65518ab57161d6e0962bc9bf on 1569/menu_check into<PHONE_NUMBER>c4d041023b1496c0335ac5f43d487d on master.


Don't throw error on unused function parameter

annoying af

Fixed in my fork, which is getting close to ready.


Support array of strings as output

Github actions support array type. It would be nice to be able to have urls output field that is an array of strings = uploaded URLs. Such approach makes it easier to refer to specific URL by index later in workflow. Currently the url output field is a single string that requires preprocessing to split it into array - that makes it usable in a real life workflow. Otherwise without conversion to array first - working with url is troublesome.

Good to know, I will looks into it soon ;)

Thank you! It seems you only need to add a new variable here:
https://github.com/McCzarny/upload-image/blob/49930cb706f8556a3c6c238d972a76b430d82086/uploadImgbb.js#L49
Something like:
return {url: response.data.data.url, urls: response.data.data.url.split(","), expiration: response.data.data.expiration};

I can make a PR for that, if this approach is OK?

Of course, if you have a problem, you can bring it here. To run tests you need an env variable API_KEY with the API key for imgbb.


Fix tensorboard requirements

The recent tensorboard builds had a wrong list of requirements. This fixes it in addition to the PRs that update the meta.yaml for the respective versions:

https://github.com/conda-forge/tensorboard-feedstock/pull/54
https://github.com/conda-forge/tensorboard-feedstock/pull/55
https://github.com/conda-forge/tensorboard-feedstock/pull/56

% python show_diff.py --use-cache --subdirs noarch
noarch::tensorboard-2.4.0-pyhd8ed1ab_0.tar.bz2
-    "google-auth-oauthlib 0.4.1",
+    "google-auth-oauthlib >=0.4.1,<0.5",
-    "wheel >=0.26"
+    "wheel >=0.26",
+    "google-auth >=1.6.3,<2",
+    "requests >=2.21.0,<3",
+    "setuptools >=41.0.0"
noarch::tensorboard-2.4.1-pyhd8ed1ab_0.tar.bz2
-    "google-auth-oauthlib 0.4.1",
+    "google-auth-oauthlib >=0.4.1,<0.5",
-    "wheel >=0.26"
+    "wheel >=0.26",
+    "google-auth >=1.6.3,<2",
+    "requests >=2.21.0,<3",
+    "setuptools >=41.0.0"
noarch::tensorboard-2.5.0-pyhd8ed1ab_0.tar.bz2
-    "google-auth-oauthlib 0.4.1",
+    "google-auth-oauthlib >=0.4.1,<0.5",
-    "wheel >=0.26"
+    "wheel >=0.26",
+    "google-auth >=1.6.3,<2",
+    "requests >=2.21.0,<3",
+    "setuptools >=41.0.0"
noarch::tensorboard-2.6.0-pyhd8ed1ab_0.tar.bz2
-    "google-auth-oauthlib 0.4.1",
+    "google-auth-oauthlib >=0.4.1,<0.5",
-    "wheel >=0.26"
+    "wheel >=0.26",
+    "google-auth >=1.6.3,<2",
+    "requests >=2.21.0,<3",
+    "setuptools >=41.0.0"

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/core This is ready for review/merge as CI has passed: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=366775&view=results


Change Header to Black Python Devs

Currently it reads BPDevs while we're waiting on an official logo some of our partners wants to include us on the website.
If we can just have the website have "Black Python Devs" instead of "BPDevs" we can just have them grab a clip from there.

I've attached an SVG. I think it may need to be cleaned up a bit

I testing the logo in a dark theme and look darker, but for starting good job 👏🏾

Black Python Devs on dark themes

Do you know if there is a way to have two images and alternate them with it being an svg can we apply a stroke to it in dark-mode to change the color?

I see a workaround similar idea and solution to the issue for the Textualize/rich logo: https://github.com/Textualize/rich/blob/master/assets/logo.svg


Suggestion - Add Dodgy Necklace to Jewellery Count

dodgy necklaces having a counter on them would make thieving much nicer

I'm not sure a counter would be right for this amulet however, I would like to see dodgy necklaces have a notification and/or the screen flash when it uses it's last charge to notify me that it's turned to dust and I need to equipped another one.


Traffic light module with "build_prof"

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo installed from (source or binary): source (docker)
Apollo version (3.5, 5.0, 5.5, 6.0): pre6

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

./apollo.sh build_prof
Supporting materials (screenshots, command lines, code/script snippets):
Hello,
I'm using pre6 version Apollo.
I built the Apollo with build_prof (./apollo.sh build_prof) because I want to profile the performance.
However, when I built that with build_prof, traffic light module cannot be executed.
(when I built that with build_opt_gpu, traffic light module can be executed.)
Although I looked up data/log log messages, I cannot find the fail message about traffic light module.
Thank you.

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo installed from (source or binary): source (docker)
Apollo version (3.5, 5.0, 5.5, 6.0): pre6

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

./apollo.sh build_prof
Supporting materials (screenshots, command lines, code/script snippets):
Hello,
I'm using pre6 version Apollo.
I built the Apollo with build_prof (./apollo.sh build_prof) because I want to profile the performance.
However, when I built that with build_prof, traffic light module cannot be executed.
(when I built that with build_opt_gpu, traffic light module can be executed.)
Although I looked up data/log log messages, I cannot find the fail message about traffic light module.
Thank you.

By traffic light module, you mean modules/perception/camera/lib/traffic_light ?

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo installed from (source or binary): source (docker)
Apollo version (3.5, 5.0, 5.5, 6.0): pre6

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

./apollo.sh build_prof
Supporting materials (screenshots, command lines, code/script snippets):
Hello,
I'm using pre6 version Apollo.
I built the Apollo with build_prof (./apollo.sh build_prof) because I want to profile the performance.
However, when I built that with build_prof, traffic light module cannot be executed.
(when I built that with build_opt_gpu, traffic light module can be executed.)
Although I looked up data/log log messages, I cannot find the fail message about traffic light module.
Thank you.

By traffic light module, you mean modules/perception/camera/lib/traffic_light ?

Yeah, I mean that.
In Dreamview, it means that the traffic light module does not turn on properly.

By traffic light module, you mean modules/perception/camera/lib/traffic_light ?

Yeah, I mean that.
In Dreamview, it means that the traffic light module does not turn on properly.

With -lprofiler issue resolved as described in https://github.com/ApolloAuto/apollo/issues/11881#issuecomment-662451882 ,
./apollo.sh build_prof and
bazel build --config=cpu_prof --cxxopt=-DCPU_ONLY  //modules/perception/camera/lib/traffic_light/... should both be OK.
Have you make GPU enabled ?


Automated cherry pick of #4873: Stop exporting KUBECONFIG in ci/test-conformance-gke.sh
#4983: Fix GKE CI job
#5298: Fix GKE conformance job

Cherry pick of #4873 #4983 #5298 on release-1.11.
#4873: Stop exporting KUBECONFIG in ci/test-conformance-gke.sh
#4983: Fix GKE CI job
#5298: Fix GKE conformance job
For details on the cherry pick process, see the cherry pick requests page.

GKE conformance job succeeded: http://jenkins.antrea-ci.rocks/view/cloud/job/cloud-antrea-gke-conformance-net-policy/557/


starrocks-sink doesn't support array

failed to validate sink: Starrocks error: Column type don't match,
column name is "c_boolean_array". starrocks type is "array<boolean>" risingwave type is List(Boolean)

closed by #16221


Backend state inconsistencies and missing states

[ ] Metal doesn't seem to have a scissor-test-enabled state, consider removing this from the sokol API (scissor test would always be enabled, and the scissor rect would be reset in sg_begin_pass)
[ ] texture anisotropy
[ ] depth bias / polygon offset
[ ] D3D11 doesn't have signed 10-10-10-2 vertex format, but unsigned version

closing this, bundled now in #24


Weak typings for Array.prototype.map

TypeScript Version:  2.4.0
Code
The following blows up nicely as expected:
type A = {
    foo: string;
};

/** 'baz' does not exist in type 'A' */
const test1: A[] = [{ foo: 'foo', baz: 42 }];

Put it through the map method though, and any extra fields will be silently accepted:
/** no error */
const test2: A[] = ['foo'].map(val => ({ foo: val, baz: 42 }));

Expected behavior:
Both examples blow up w/ 'baz' does not exist in type 'A'
Actual behavior:
Only the compilation of the first example fails.

Duplicate of #11152.
Currently we can't determine a contextual type for the returned expression, so extra properties aren't checked.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


indenation

There is a problem with indentation. When I like to indent to 3 spaces, it will become the indentation of 2 spaces.

@ChessonTsin can you give an example?


[Bug]: Responsive Search bar

PR Description 📜
By follow given guidelines resolve issue ,create responsive navbar if u want any changes please tell my mistakes I will correct it again
Fixes #116

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

Thank you soo much for contributing to our repository 💗

ok i will check once and resolve conflicts


The concept of conservative regridding method

I'm curious of the concept of conservative regridding: area weighted or distance weighted?
It seems that's area weighted in #17, right?

Yes it's area weighted. See https://climatedataguide.ucar.edu/climate-data-tools-and-analysis/regridding-overview and https://journals.ametsoc.org/doi/full/10.1175/1520-0493(1999)127<2204%3AFASOCR>2.0.CO%3B2

@JiaweiZhuang Thanks!


increase links per page?

Is it anyhow possible to adjust the number of links being shown per page? My list of tags is so long, that i could easily get more links listed.
please see my screenshot for what i mean.

As far as I can tell it's hard-coded here:
https://github.com/sissbruecker/linkding/blob/e83d519cab9b4ace997d9cdc385a1ff133e8be2f/bookmarks/views/partials/contexts.py#L13

Is this something that might get merged in the near future? It seems like krzysztofjeziorny has resolved the issue and it just needs a style check and merge?


Not always...

This document says "Some enums require the elements to have a certain order or value, and cannot be made extensible. This could be status enums, where the values represent a logical progressive sequence...", however, both WHSExpeditionStatus and ProdStatus were made extensible in Dynamics 8.1 release.  The enums represent a clear logical progression and even have 'Status' in their names.
Not only does this go against what is written here, but is a breaking change as discussed here.
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/extensibility/breaking-changes

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

ID: fc4f7135-87e3-67c0-6bb1-a5ce88a7a909
Version Independent ID: 473aea55-658c-84a5-2b02-70cc53a6b480
Content: Write extensible enums - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/extensibility/extensible-enums.md
Service: dynamics-ax-platform
GitHub Login: @smithanataraj
Microsoft Alias: smithanataraj

@smithanataraj, can you fix this topic?

This issue is being tracked by bug 261740.

Hi Brian,
Enums with progressive sequential values when made extensible, can break consumers using them in comparisons. For 8.1, a recompile was required and hence making such enums like status enums extensible, was a conscious decision that was made, in order to provide extensibility on those. This will not be the case with monthly updates.


License?

Any chance you could release this under a more permissive license? As is, I don't think it can be used by any commercial closed-source game.

What. The MIT license? Assuming that's what you mean. Before I sent another update it used to be Gplv3.

Looks back at LICENSE.md
Woops! Forgot about that license.
It's fixed now. Same goes for the asset store. It hasn't been updated yet though.


CM-24180 support zip scan for repository

Cm 24180 support zip scan for repository
enable to scan files for secreats using the Cycode-cli

@galdavidi , this PR is still relevant?

@galdavidi , this PR is still relevant?

that's duplicate of #136. im waiting for BE chabges first. not merged yet


Tab bar not following theme colors

After changing the theme to any light theme the tab bar continues being black as if no theme change happened.

I though that changing the theme will change the UI elements, but nor system theme nor settings/appearance made the change to UI elements.

In the older Electron version of Extraterm, some of the UI elements like the background colours did respond to the current terminal coour scheme. This is not the case in the Qt version. It could be done of course, but that is quite low on the list of priorities.


Initial support for R pakcages.

Ideally we should do a proper "light-weight" re-write of the conda-skeleton cran as it was done for conda-skeleton pypi but as a first iteration having something for R is better than nothing and here is what I'm thinking:

add conda-build as an optional dependency
if a user calls "cran" run conda-skeleton cran (or warn about the missing optional dep)
run the conda_r_skeleton_helper

@marcelotrevisani this would improve the user experience b/c it will be a single package to create both recipes and help reviews b/c the conda_r_skeleton_helper would be applied already. What do you think?
xref.: step 2 from https://conda-forge.org/docs/maintainer/adding_pkgs.html?highlight=cran#getting-started

@ocefpaf, I think this is a good plan.

"a first iteration having something for R is better than nothing"
This makes sense. Implementing this would mean that the user doesn't need to use two separate recipe generators for Python and R recipes. And although this will be an enhancement in user experience, Grayskull would be using conda-skeleton (which is integrated with conda-build) under the hood to generate the recipe. And this, as I realized after a discussion with @marcelotrevisani, would, unfortunately, defeat the purpose of creating Grayskull (a stand alone, conda-build independent application) in the first place.
Perhaps, when the user runs "cran", displaying a message like: Grayskull doesn't support CRAN packages yet. You might want to try conda-skeleton for generating R recipes. might be good idea while we work on implementing the R support in Grayskull.

Closing this as it is duplicated with https://github.com/conda-incubator/grayskull/issues/266 and https://github.com/conda-incubator/grayskull/pull/349


Capability to filter the API-Specification (Operation/Method)

User story
It should be possible to filter the given API-Specification so that, for example, certain HTTP methods or individual operations are not registered with the API. A user can configure includes and/or excludes
For example, to register an existing API based on a generated API-Specification, but without for instance the DELETE methods.
Currently the API-Specification is defined as a simple property apiDefinition which is a String. To support filters for an API specification, the APIM-CLI should be changed so that the API specification can be defined as an Object with the following structure. The path to the API-Specification itself, will be registered as a resource and is the only mandatory field. It works in the same way as the apiDefinition.
{
  "name": "Filtered API",
  "path": "/api/which/is/filtered",
  "state": "unpublished",
  "version": "1.0.0",
  "apiSpecification": {
    "resource": "../petstore.json",
    "filter": {
      "include": {
        {
          "GET": "*"
        },
        {
          "PUT": "updatePet"
        },
        {
          "POST": "createPet, createUser"
        }
      },
      "exclude": {
        {
          "DELETE": "*"
        }
      }
    }
  },
  "organization": "API Development"
}

Additional notes

filters are optional

in case of duplicated definitions, excludes take precedence over includes

to avoid for instance the DELETE-Method to be included accidentally

if a method or operation is not explicitly excluded, it is included by default

even if not declared as included

apiDefinition should still be supported
filtering should not be supported with command line parameter -a
exporting API will not contain the filters anymore, as the information cannot be stored in API-Manager

export will contain the already filtered API
beginning with that version the API-Config will contain the apiSpecification object instead of the apiDefinition

compare between Actual- vs. Desired-API should happen, after the filter have been applied

this results for instance in a No-Change, when the same filters are applied

Interesting feature. Is the filtering done against operation name or path ? Currently , i plan to use Swagger Combine in order to do such filtering

Hi @ftriolet, the plan is use API-Filtering based on the HTTP-Methods and operationId's. This might esp. help for generated API-Specs that contain too many HTTP-Methods and/or operations.
Do you think the issue describes it entirely?

What about adding a specific file for the filter configuration and a new command line parameter ? API config file will be the same for the import/export and the filtering configuration  will be separate.

Hi @cwiechmann , I'm still wondering if operationId is the best option for filtering as it's not a required parameter. I have some APIs from external providers which not using operationId. I would prefer filtering on the path.

Hi @cwiechmann ,
I kept thinking about it. My proposal is to add a filter field in app-config file :
{   "name": "Filtered API",   "path": "/api/which/is/filtered",   "state": "unpublished",   "version": "1.0.0",   "apiDefinition": "./petstore.json",   "filter" : "./filter.json"   "organization": "API Development" }
And a new file for the filter :
filter.json
{   "filter": [     {       "paths": {         "exclude": [           "*.delete"         ]       }     },     {       "paths": {         "include": [           "/pet.put",           "*.get"         ]       }     }   ] }
Further operations could be add later like renaming path

@ftriolet, but why do you think it is better to have an external file instead of putting it directly into the API-Config file?
{
  "name": "API with API-Specification object",
  "path": "/api/v1/Some.Services/XmlApi",
  "state": "published",
  "version": "1.0.0",
  "organization": "API Development",
  "apiSpecification": {
  	"resource": "petstore.json",
  	"filter": {
  		"include": {
  			"GET": "*",
  			"PUT": "operation1, operation2"
  		},
  		"exclude": {
  			"DELETE": "*"
  		}
  	}
  }
}

I have another question:
I would like to make the filter configuration as simple as possible. As you can see in the example above, I would implement the filters based on the HTTP-Verb followed by the path, as I believe this is what customers more often need. For example: "Include all GET-Operations no matter which operation." Or: "Don't include DELETE-Operation".
I see, you expected it differently based on your example. Do you see any specific benefit configuring it the other way around?

Hello  @cwiechmann,
For the first question, it was to keep the api config file as identical as possible  for the import and the export. If we have an unique file, export will no longer contains filtering configuration. This configuration could be huge in case of big swagger files ( i have some  > 9mb)
Second question, I'm agree with you, it's just another syntax where path is before http verb as in swagger file . Maybe if you want to keep all operations of an identical path, you can do it in a more concive way with "/my_path.*"

Thanks for the feedback @ftriolet. You mean, you Swagger-Files might be up to 9MB big and you would need that many filtering rules?
I have slightly adjusted the filter config again like so:
"apiSpecification":{
      "resource":"../petstore.json",
      "filter":{
         "include":{
            "paths":[
               "/pet.PUT",
               "/user.*",
               "*.GET"
            ]
         },
         "exclude":{
            "paths":[
               "/pet/{petId}.DELETE"
            ]
         }
      }
   }

This allows us to add other filters like tag-groups at the same level as path without the need to repeat include/exclude. Would it help to simplify you use-case when having the option to filter for tags?
Besides that, I completely followed your recommendation. You can configure combinations of wildcards as shown in the example above.


Responding to #5585: Check for syscall errors

Responding to https://github.com/prometheus/prometheus/issues/5585
I try to log an Error, instead of a warning, if there's a syscall error in scrape.go. Please let me know wherever I can improve.

Can you explain what you're trying to do?

Thanks so much for reviewing this. I'm trying to log an Error (rather than Warning) if the application catches a syscall error--that is, something like a ENOMEM (enough memory) error.

It's already a warning, and this seems to be tackling things at the wrong level. What exact syscall is returning this?

I changed it to Error as this seemed to be a wanted/requested feature (instead of silently failing when the application is out of memory). I chose syscall errors to generate Error as I think most seem to warrant that.
I'm not sure which syscall (any call which asks for more memory when there is none could generate it), but would definitely be ENOMEM which has error code 12.
errno 12
>>ENOMEM 12 Cannot allocate memory

This matches the error message that @woodsaj reported: write /prometheus/data/wal/00002922: cannot allocate memory.
Do you have any suggestions on how to go about this (I'm still new to open source, so I would love to learn more)? Also, let me know what further information you need.

Changing the severity of a log message doesn't solve any problems. The question here is why this isn't either panicing or OOMing.

Oh I see what you are saying, yes that's definitely a better approach. Maybe this weirdness is due to using:
func yoloString(b []byte) string {
	return *((*string)(unsafe.Pointer(&b)))
}

Do you think a good approach would be replacing this with the safer golang construct string([]byte)? Let me know if this is something you'd welcome and I can implement this. Otherwise, please feel free to close this PR as I completely agree with your logic and thoughts.

That's nothing to do with it, that'd cause different problems.


Karpenter reports provisioner status wrong

Description
Observed Behavior:
After upgrading to latest karpenter version (0.30.0) we've noticed somethimes the provisioner is reporting wrong status for cores ,ephemeral-storage, memory pods.
We have an example provisioner:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  annotations:
    karpenter.sh/provisioner-hash: "17279383624591743851"
  creationTimestamp: "2023-04-16T13:23:03Z"
  generation: 6
  labels:
    karpenter.sh/capacity-type: on-demand
  name: r6i-reserved
spec:
  consolidation:
    enabled: true
  kubeletConfiguration:
    clusterDNS:
    - <IP_ADDRESS>
    containerRuntime: containerd
  labels:
    karpenter.sh/capacity-type: on-demand
  limits:
    resources:
      cpu: "0"
  providerRef:
    name: default-node-template
  requirements:
  - key: karpenter.k8s.aws/instance-family
    operator: In
    values:
    - r6i
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - on-demand
  - key: karpenter.k8s.aws/instance-generation
    operator: Gt
    values:
    - "4"
  - key: karpenter.k8s.aws/instance-generation
    operator: Lt
    values:
    - "8"
  - key: karpenter.k8s.aws/instance-cpu
    operator: Lt
    values:
    - "20"
  - key: karpenter.k8s.aws/instance-cpu
    operator: Gt
    values:
    - "0"
  - key: kubernetes.io/arch
    operator: In
    values:
    - amd64
  - key: kubernetes.io/os
    operator: In
    values:
    - linux
  weight: 48
status:
  resources:
    cpu: "2"
    ephemeral-storage: 104845292Ki
    memory: 16098260Ki
    pods: "29"

As you can see status is reported as 2 cores, 29 pods
However we have no nodes created by this provisioner. The following command returns:
kubectl get machine -l karpenter.sh/provisioner-name=r6i-reserved
No resources found

Expected Behavior:
Provisioner status should be accurate
Reproduction Steps (Please include YAML):
We didn't fine a way to reproduce since its not happening immediately . We noticed this a day or two after upgrading from version 0.28.0 - rollback to 0.28.0 solves the issue
Versions:

Chart Version:  0.30.0
Kubernetes Version (kubectl version):  1.26

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

This is very surprising to me. Do you have any logs from the event? Is it possible that the controller did not have permission to update the status?

Hi @ellistarn this problem persist after karpenter pod restart and I still see this issue in my cluster however when i search the logs for this provisioner name I can't find any mention for it
this is our cluster role
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
    app.kubernetes.io/instance: karpenter
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: karpenter
    app.kubernetes.io/version: 0.30.0
    helm.sh/chart: karpenter-0.30.0
    rbac.authorization.k8s.io/aggregate-to-admin: 'true'
  name: karpenter-admin
rules:
  - apiGroups:
      - karpenter.sh
    resources:
      - provisioners
      - provisioners/status
      - machines
      - machines/status
    verbs:
      - get
      - list
      - watch
      - create
      - delete
      - patch
  - apiGroups:
      - karpenter.k8s.aws
    resources:
      - awsnodetemplates
    verbs:
      - get
      - list
      - watch
      - create
      - delete
      - patch

I have the same issue.
{"resources":{"cpu":"8","ephemeral-storage":"115294128Ki","memory":"21982388Ki","nvidia.com/gpu":"1","pods":"98"}}

Its showing that there are GPUinstances provisioned. They were provisioned earlier and then destroyed.
Below are the running nodes,

Hi @ellistarn
I found a way to reproduce the issue (also in version 0.31.0 )
It looks like the status is not able to go to zero. If I add a test provisioner with a test pod and then removing the node the status should be updated to show zero core & pods and its not the case. It looks like the status is remaining the same as before the node was remove

i think the RC is that resourceCountsFor https://github.com/aws/karpenter-core/blob/main/pkg/controllers/nodepool/counter/controller.go#L78 returns an empty map when the last node is removed, but because the Reconcile method https://github.com/aws/karpenter-core/blob/main/pkg/controllers/nodepool/counter/controller.go#L71 uses a patch status, thus this empty map is combined with the previous map where there were still resources, resulting in an erroneous status report


WIP: Improve README

Could you have a look, @AustinT. I would add a simple notebook (see Tutorials) to clarify how to access the dataset with pandas.

Closing because this is out of date; will replace with new PR soon.


Use cached FhirContext everywhere to improve performance

Describe the Issue
Fixes Use cached FhirContext everywhere to improve performance
Description
FhirContext.forR4 initializes FhirContext every time. It is recommended to use Cached version to prevent heavy operation every time
Would you like to work on the issue?
@maimoonak

Issue tracking PR https://github.com/google/android-fhir/pull/1106/


Disable collision between relatives bodies

How to disable collision between relatives bodies? For example, I have a lot of balls, they fall and collide by walls, but they should not collide with themselves. Please someone explain how to make it?

It looks like you're looking for "Collision Filtering"...
https://brm.io/matter-js/demo/#collisionFiltering
https://github.com/liabru/matter-js/blob/master/examples/collisionFiltering.js
I haven't tried it. But if I'm understanding this correctly, it looks like you'd create a "walls" category, then set a "collisionFilter" on the balls, where the mask would be the "walls".

It looks like you're looking for "Collision Filtering"...
https://brm.io/matter-js/demo/#collisionFiltering
https://github.com/liabru/matter-js/blob/master/examples/collisionFiltering.js
I haven't tried it. But if I'm understanding this correctly, it looks like you'd create a "walls" category, then set a "collisionFilter" on the balls, where the mask would be the "walls".

No, it not works for me. Because relatives bodies collide between themselves, cause they gonna have the same mask.

 If it's 30 or less, why not create a group for each ball, one for walls and one general group?

I think you could set the balls all to have a negative group e.g. -1 and the walls a positive group (default is 0 so that's fine).
Would that work? You can combine these with masks too. If you need something really custom, you could patch Detector.canCollide with your own logic.


Renamed a save folder and don't know what to do

So i accidentally renamed one of my save folders for the Gib Save Editor. I haven't played Borderlands 2 in a while so i forgot changing the names of things screwed things in game over. I deleted Borderlands 2 to maybe get the regular folder back, but that didn't work. Is there any way for me to get my old save folder back or at least get a new one that links to my Borderlands account so i can just re-create my characters?

That would depend on what you ended up renaming it to.
To my knowledge, the correct location for save files is:
Documents\My Games\Borderlands 2\WillowGame\SaveData


Error when running the 1.16.5 installer on Ubuntu 20.04.2 LTS

When I run the 1.16.5 installer from the terminal (./FoliClientInstaller-Linux), it gives me the error
"[2540] Error loading Python lib '/tmp/_MEIVnMPxV/libpython3.9.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/_MEIVnMPxV/libpython3.9.so.1.0)"
I also tried double clicking the file to run in the file manager but it said "There is no application installed for shared library files".

Have you tried to run it from the source? (python3 FoliClientInstaller.py)

No, but I just tried and it worked thank you! Does this work for the 1.17 installer too?

I think so.

Sorry I didn't see this earlier, yeah the compatibility of the Linux binaries can be very hit or miss, I'll look into possibly distributing as an AppImage for future releases. As vXtrenius said above, the best move is to run the python source.


Several non-descript cases of "core::Error" while compiling with GCC 10.3 in MSYS2

Environment

Tesseract Version: HEAD
Commit Number: 5.0.0-beta-20210916-63-g0d57
Platform: media-autobuild suite = MSYS2 + MinGW64 + GCC 10.3 Win32 cross-compiler (ccache enabled) on Windows 7 SP1 x64

Current Behavior:
Several non-descript cases of "core::Error" while compiling with GCC 10.3:
...
  CXX      src/dict/libtesseract_la-dawg_cache.lo
terminate called after throwing an instance of 'core::Error'
terminate called recursively
make[1]: *** [Makefile:5779: src/cutil/libtesseract_la-oldlist.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/build/tesseract-git/build-32bit'
make: *** [Makefile:8149: all-recursive] Error 1
Making all in .
make[1]: Entering directory '/build/tesseract-git/build-32bit'
  CXX      src/cutil/libtesseract_la-oldlist.lo
  CXX      src/dict/libtesseract_la-dict.lo
  CXX      src/dict/libtesseract_la-stopper.lo
  CXX      src/dict/libtesseract_la-trie.lo
terminate called after throwing an instance of 'core::Error'
terminate called recursively
make[1]: *** [Makefile:5821: src/dict/libtesseract_la-trie.lo] Error 1
make[1]: Leaving directory '/build/tesseract-git/build-32bit'
make: *** [Makefile:8149: all-recursive] Error 1

See more verbose log files in logs.zip collected by media-autobuild_suite
I am a bit confused why it does not contain verbose C/C++ compiler errors with references to source lines. 🤔
Expected Behavior:
successful compilation
Suggested Fix:
none; I am not a C/C++ developer

So I did, but it still produced such an error.
logs.zip

Disabling the ccache might also help.


HSEARCH-2079 Improve OSGi header generation with properties and revie…

…w some stale definitions

https://hibernate.atlassian.net/browse/HSEARCH-2079

Looks good apart from that one comment.

thanks @gunnarmorling for catching that. Fixed it, I'll push now if the tests pass on CI.

merged


MAINT: adding testing matrix for CI and tox to handle environments

This PR adds new infrastructure to test notebooks in the pytest fashion and to receive meaningful tracebacks from the cells rather than a generic sphinx error.
The PR also sets up tox to easily handle different environments, we use it in CI, but it also provides super easy ways to reproduce those locally.
I expect this to pass. It it does I'll temporarily will cherry-pick commits from other PRs that we know should not pass with e.g. both dev and released pyvo.
This closes #63

The one thing that we don't do here is to raise errors on each and every warnings the notebooks generate but otherwise the testing will be much more rouboust when this gets merged in.

Unfortunately, the allow-to-fail feature (and its workarounds) doesn't really work for github yet, so adding the comment that "Temporarily allowed to fail" is the best thing I could do here. I feel it's still better to have it the tests with the development pyvo version run, than not run at all.


Missing license in npm package for v6.2.0

Expected Behavior
Hi @marionebl, thank you for this package. Would you mind adding the license file to the npm packages? Without it we're not really able to use it, because it makes the npm package a distribution of proprietary code.
Affected packages
<EMAIL_ADDRESS><EMAIL_ADDRESS>Many thanks!

This should be fixed in the 7 version range via https://github.com/marionebl/commitlint/issues/426. Could you update your commitlint version and check again?


Added threadId to Feedback

Added threadId to Feedback. This will allow for getting the associated threadId easily. Plan to use this in adding document database data layers to chainlit like Dynamo. Discussed with @willydouhard

I think this is great! This does not update the data layers but this is probably out of scope. I assume you are using a custom data layer yourself?

Yes I wanted to keep this PR small. The literal and sql data layers also don't need to use the threadId property so there was no reason to update them.


Added support for verity flag

Added support for verity feature flag.

Verity requires some special image, right?
If so, it should be useful to also add image seeds with verity enabled here:
https://github.com/google/syzkaller/blob/master/tools/syz-imagegen/imagegen.go#L238-L272
The fuzzer is unlikely to come up with proper verity images on its own, so verity won't be tested.


TX OFS save error

After setting TX OFS, press M to save. The saved frequency will decrease the frequency of STEP, with 5mhz - step (1khz)=4.999mhz

Fixed it now, let me know if it's still not quite right.

fixed


v0.10.6 this repo vs v0.10.7 on NPM?

Why does this repo master branch list WebChat at 0.10.6 when NPM is showing the latest version as 0.10.7?
This repo, package.json:

NPM:

It means that the version was bumped on @GeekTrainer 's local machine package.json when it was published, and this wasn't checked in.

This should now be resolved.


A way to terminate the main loop

Currently there are webview_init and webview_exit`, which are basically a constructor and a descructor for the webview object.
I suggest to add something like void webview_terminate(struct webview *w) that would terminate and break out of the main loop.

Implemented webview_terminate as described above.


Updated free-courses-en.md > Added Three.js subcategory + course

What does this PR do?
Added Three.js subcategory and course.
For resources
Description
Three.js Tutorial Crash Course
Why is this valuable (or not)?
It is the one of the few detailed courses on three.js on YouTube
How do we know it's really free?
It is uploaded on YouTube.
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


Update weaver-cats, weaver-scalacheck to 0.7.8

Updates

com.disneystreaming:weaver-cats
com.disneystreaming:weaver-scalacheck

from 0.7.7 to 0.7.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming" } ]

labels: library-update, early-semver-minor, semver-spec-patch

Superseded by #101.


Handling unstable clusters

Hi!
Firstly, just wanted to say thanks for a great tool, it's really helped me in getting stuck into elasticsearch as there are so many features and options having the basics in something easy to use made a big difference!
Onto my query:
Something that really causes issues for me is when the cluster is in a 'bad state', to be fair this mostly occurs for me during early development when I am restarting nodes and adjusting settings constantly to tweak bits and pieces.
 Now if I shutdown or restart one of the master nodes the cluster goes into 503. As far as I can tell this breaks kopf, as to return any info seems to rely on a 200 OK response upon initial connection. This makes it difficult to use kopf to diagnose an issue in the case where the problem has happened independently e.g. power failure to a pool or a failure of a significant enough proportion of the master nodes. However, if you have at least one operational master and you point your browser at it you can still read the _nodes path, it would be nice if kopf could still pull this on a 503 error as it would be really useful in fault resolution (rather than having to read reams of json output to figure out which node needs kicking). You can also read the cluster status detail, albeit by forcing local e.g. _cluster?local.
I was thinking it could do some logic:

if a 503 is reported, set the ui to red (rather than grey as now)
try pulling the _cluster?local from the master you are connected to
if that works (indicating at least the master you are connected to is in good order) pull the nodes data.

Although 2 doesn't offer much I'd definitely like to see 3.
I should say I am a software developer but I've spent so much time as a manager that I only have a little JavaScript knowledge and the Angular (despite looking) I can't make heads nor tails of, otherwise I'd offer to prototype it myself :-)
Appreciate any thoughts (other than stop being a manger and go learn code :P)

@up-town-down sounds reasonable, but I will have to check what I can actually get from a cluster reporting 503. Will let you know as soon as I have some time to look into it :)

@lmenezes - thanks, I've experimented with the logic a fair bit and I think it looks sound, though I appreciate you'll want to test it properly in case it has any undesired effects!
For completeness sake:

Currently when connecting and the master node you are trying to connect to is dead error returned by kopf is "Error connecting to [node url]"
if node is up and cluster is 200 ok, but shards are unassigned (_cluster/state readable) banner is yellow/amber
200 ok and all shards assigned (green banner)
currently if cluster goes 503 (tested by setting minimum master nodes to 2 and starting 1 node) kopf reports "Error refreshing cluster state", banner is grey and clicking on the detail shows 503. _cluster/state will not respond, _nodes/stats/nodes repsonds. _cluster/state?local responds

So if a 503 is thrown it's still possible to get nodes and (local) cluster state. The only problem I foresee is if the cluster is split because 2 pools (assume different data centres/sites) are disconnected as kopf will be reporting local cluster status not the whole cluster, but I think the benefits i.e. some node status vs. nil will most likely outweigh the cost.
I'm worried it might be a lot of logic changing and I'm sorry I'm too stupid to help, but would love it if you could :)

This is awesome, thanks for doing it, it's making my life so much easier!

no problems :)
Currently is still very very basic what it does, but I suppose this can be improved little by little.

Sorry @lmenezes but I think this might have busted in the latest release, I'm seeing the "no master node" message and the tab switch to the nodes tab, but there is no data :(

@up-town-down sorry about that :) should be fixed in 1.4.9 which i just pushed. This handling a broken cluster workflow is still quite brittle, but will try to find sometime to add some tests to it. thanks for letting me know.

Heh, I know what you mean, any code I write is pretty brittle! I'll give 1.4.9 a go and post back if there are any issues. Cheers!


Integration tests

Pull Request Test Coverage Report for Build 88

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

Totals

Change from base Build 87:
0.0%

Covered Lines:
93

Relevant Lines:
97

💛  - Coveralls


License

Would you consider attaching either the MIT or BSD license to this project?
I'd like to be able to use this plugin but my company has strict requirements about open source in our environment. Simply adding a 'LICENSE' file to the repo containing either of the above licenses would be awesome.

I don't really maintain this repository anymore but if you create a PR with the MIT or BSD license I'm happy to merge it.

I've submitted https://github.com/fstab/cifs/pull/12
Thank you!


Feat/add support for rpop count parameter

Description:

Add support for optional COUNT parameter with RPOP command similar to Redis.

@Kripu77 can you please fix lint and build issues.

@Kripu77 can you please fix lint and build issues.

HI @lucifercr07, please let me know if you see any further issue.


Trigger CI release

What type of PR is this?
(bug/feature)
What this PR does / Why we need it?
Trigger CI release for testing

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 44.54%. Comparing base (d49bfa2) to head (a12514e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #455   +/-   ##
=======================================
  Coverage   44.54%   44.54%
=======================================
  Files          63       63
  Lines        5296     5296
=======================================
  Hits         2359     2359
  Misses       2617     2617
  Partials      320      320

/lgtm


Confusing Tutorial

The tutorial is very confusing. There are lines of code but not clear instructions on what to do with the code. Do we always have to refer to GitHub code to figure out what the author is talking about?

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

ID: 948bdbcf-e49f-bd3a-89c4-d83f86cfddc5
Version Independent ID: 5c6e688e-7afa-1201-2887-e3cae35abe54
Content: Microservices hosted in Docker - C#
Content Source: docs/csharp/tutorials/microservices.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

That tutorial is outdated.  I'm going to remove it and re-direct the link to our Docker section under the .NET Core guide. That content is more up to date.


cpu load retrieval must be fixed

Describe the bug
cpu load retrieval must be fixed
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

root@proxmox:~# tail -f /var/log/lxc_autoscale.log
2024-11-30 10:06:51 - INFO - Starting resource allocation process...
2024-11-30 10:06:51 - INFO - Ignoring LXC Containers: set()
2024-11-30 10:06:51 - INFO - Initial resources before adjustments: 6 cores, 11785 MB memory
2024-11-30 10:06:51 - INFO - Current resource usage for all containers:
2024-11-30 10:06:51 - INFO - Container 204: CPU usage: 45.0%, Memory usage: 30.2MB (99.16% free of 3584MB total), Initial cores: 1, Initial memory: 3584MB
2024-11-30 10:06:51 - INFO - Container 203: CPU usage: 0.0%, Memory usage: 12.94MB (98.74% free of 1024MB total), Initial cores: 1, Initial memory: 1024MB
2024-11-30 10:06:51 - INFO - Container 202: CPU usage: 0.0%, Memory usage: 11.56MB (99.55% free of 2560MB total), Initial cores: 1, Initial memory: 2560MB
2024-11-30 10:06:51 - INFO - Container 201: CPU usage: 8.0%, Memory usage: 16.44MB (99.54% free of 3584MB total), Initial cores: 1, Initial memory: 3584MB
2024-11-30 10:06:51 - INFO - Final resources after adjustments: 6 cores, 11785 MB memory
2024-11-30 10:06:51 - INFO - Resource allocation process completed. Total loop duration: 5.48 seconds.


Added super approvers

Super approvers are automatically added to the project as approvers. They have to be added into "roles" table with a privilege 'super_approve'.
There are some undefined edge cases though (maybe not that relevant for the MVP):

Is it allowed for a project to be submitted with only 1 approver (the super approver) and nobody else?

Can the super approver also be an editor? I imagine super approvers to be someone very experienced
in the domain, so I suppose we shouldn't prevent them from editing the project if the owner decides
they need their help?

Can the super approver also be the owner of a project? Should we in this case prevent them to submit their own project with only 1 approver (themselves?)

They're also working on getting a list of super approvers set- to be followed up on after holiday break.

Updated super approver behavior for 1, 2, 3 cases.


Browser 'back arrow icon' problem

Instinctually pressing the back arrow on my browser is ineffective right after creating a new project. A 'rename' feature could be nice too from a user perspective if the back button doesn't work so that you don't have to copy,delete, and recreate the project with a new name.

Any update here? 😉

Haha, I have been more focused on v2.0.0 stuff atm. If it is pressing, let me know and I can prioritize it more :)
Are you in the slack channel? If not, feel free to join if you are interested. Although I have been pretty busy finishing up my dissertation, I will post more updates and stuff there once v2 is ready for use!

Haha no I was just skimming through the open issues, found this and thought it was funny.  Although, I'll definitely join the slack channel when I can find a little more time to contribute.  It's awesome to see how far the project has come.  Best of luck on finishing up your dissertation!


Increase kube-controller-manager VPA minAllowed

How to categorize this PR?

/area control-plane
/area auto-scaling
/priority normal
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Increase kube-controller-manager VPA minAllowed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/invite @timebertt
CLA needs to be signed.


Switched to node-package-release-action Action for release Workflow

Current dependencies on/for this PR:

main

PR #1287

PR #1288   👈

This comment was auto-generated by Graphite.


Use ECFlow as the workflow engine

Short description of the issue
In executing workflows, interTwin's WP6 is investigating interfaces to workflow composition and engines for workflow execution.
The Common Workflow Language (CWL) has been chosen as the common interface for workflow composition.
Here we executed a CWL workflow from ECFlow to explore interoperability.
It has been communicated to us that using ECFlow on DestinE is only really required when running large (global) models on EuroHPC. For limited area models like we use in DT Flood Early Warning and DT Flood Climate Impacts, we can rely on VMs in the cloud to run the models which also gives us more flexibility in terms of the workflow engine we are using.
Hence this issue is considered to be beyond the scope of the work being undertaken here for interTwin.

Using ecFlow to monitor CWL workflows sounds really interesting! Short notice, but we are having the CWL Conference 2024 in a few days. I think there is not much time to submit a talk on this, but registrations for the hybrid Online/Amsterdam conference are still open - https://www.commonwl.org/conferences/2024/ :+1:


Asset upload from within front-end entry form

Question
Hi @bencroker , as per the other issue, I'm trying to get a front end entry form that contains a file input working with Sprig.
Stripped down code is here...
{% set entry = entry ?? create('craft\\elements\\Entry') %}

{% if success is defined and success %}

The entry was successfully created!

{% else %}

<form sprig s-method="post" s-action="entries/save-entry" enctype="multipart/form-data">

    {{ hiddenInput('sectionId', 7) }}
    {{ hiddenInput('entryId', entry.id ?? '') }}

    Full name
    {{ input('text', 'fields[fullName]', fields.fullName ?? false, {
        id: 'fullName',
        placeholder: 'Name',
        class: ['input', entry.hasErrors('fullName') ? 'mb-2' : 'mb-6']|filter,
    }) }}

    {% if entry.hasErrors('fullName') %}

{{ entry.getFirstError('fullName') }}

    {% endif %}

    Document

    {{ input('file', 'fields[document]', fields.document ?? false, {
        id: 'document',
        class: [ 'input', entry.hasErrors('document') ? 'mb-2' : 'mb-6']|filter,
    }) }}

    {% if entry.hasErrors('document') %}

{{ entry.getFirstError('document') }}

    {% endif %}

    <input type="submit" value="Create Entry">

</form>

{% endif %}

Sure I'm missing something, but fullName field works as expected, but the file input always errors with 'Cannot be blank',

You should be using s-encoding, see https://putyourlightson.com/plugins/sprig#s-encoding

You should be using s-encoding, see https://putyourlightson.com/plugins/sprig#s-encoding

Nice! That's got it working now and submitting through 👍
The only issue I'm left with is that if the form doesn't validate, it doesn't retain the file that was added. Currently adding fields.document ?? false as the value. Should that work?

No, it will not, since fields.document will be the file object rather than the file path. You'll have to look for a workaround, perhaps putting s-preserve on the file input field to preserve its value?
https://putyourlightson.com/plugins/sprig#s-preserve

s-preserve does the job 👍 Many thanks for your help and such a useful plugin.

Glad to hear it!


Release version 0.0.1

Codecov Report
Patch and project coverage have no change.

Comparison is base (f44603f) 100.00% compared to head (520e87a) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          308       308
  Branches        51        51
=========================================
  Hits           308       308

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[database] Development project

Form selection is done. What's left is to send form data to db.

need testing

tested and working.


fix: add missing awaits for super.beforeEach()

:tada: This PR is included in version 7.0.164 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Custom poll interval

not sure if this makes sense for anyone else or if this is the correct/best way of implementing this, but this adds support for specifying a custom throttling interval for the command sensor.

I don't want to implement it like this because it is a shortcut. It should be implemented on the EntityComponent level. There is a PR out there to actually implement it but it is broken and has to be fixed.

Ah, a generic implementation makes sense. I think I just found the PR here: https://github.com/balloob/home-assistant/pull/583 Closing this, thanks!

This has been implemented now in #1059

:thumbsup:!


"finalize" should set funding_decision even if emails don't get sent

currently nothing happens

OK, the ruby isn't getting called properly: ERROR bad URI `/admins/%3C%=%20escape_javascript(send_fund_emails_admins_grant_submissions_path)%20%%3E?ids=1&send_email=false'.
I think this needs to be index.js.erb...

do we also need this? https://github.com/railsware/js-routes

found a workaround for now


Add "void" as a keyword

This will let us specify that a proc has no return type, for when we try to infer the return type of procs.

Note: this issue only means to add it as a keyword to the TokenType enum, not anywhere else yet


Protocol fee doesn't always show up in all the places in the trade confirmation widget

Overview
When completing a non 0x trade, the protocol fee doesn't always populate in the "expected amount" drop down list. The protocol fee is shown at the bottom of the widget but not always in the mid section. Sometimes it shows in the drop down menu but more often than not, it is not there.
References and additional details

Log into app.shapeshift and connect to mm/kk/native
In the trade widget proceed to create a non 0x trade and 'Preview Trade'
Notice the protocol fee at the bottom of the widget.
Drop down the menu in the Expected Amount and notice the protocol fee often states it being 0.00 even tho it shows a fee for this at the bottom of the widget.

Acceptance Criteria
If there is a protocol fee, the fee amount should be shown in all places it is listed
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

Closed by https://github.com/shapeshift/web/pull/2881.
CowSwap had special logic to show protocol fees, but now we've made this generic and the fee shows up in the receive amounts component.


add_retina() is replacing strings inside JSON encoded AJAX responses

The output buffer should have an wp_doing_ajax() check to prevent injecting lazy load tags into json encoded AJAX responses.

Turns out this was a client mod. Sorry!


Workspace - Attachment is hidden under footer message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Create a new workspace from an account that's on the policyExpenseChat beta (e.g @expensifail.com)
Add a new member to the workspace via Manage Members > Invite
Log-in as the member and send a message and and Attachment in the member's workspace chat
Log back in again to the admin account and remove the member from the workspace via Manage Members > Remove
Verify the row chat (in LHN and search bar) should display the default subtitle (workspace name)
Now log-in as the member again
Verify the row chat (in LHN and search bar) includes the workspace name
Verify the footer message displays the workspace

Expected Result:
Attachment should be fully visible
Actual Result:
Attachment is hidden under footer message
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/162203329-e1bf1951-c68d-4bdc-b2e7-4206659f1c1b.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Closing https://github.com/Expensify/App/issues/8532


coral(feat): Add pagination with functionality my-schema-requests

About this change - What it does

adds pagination to My Schema Request view
adds missing mocks to tests in SchemaApprovals (they caused a console.error that only showed up when running test in separation due to async nature)

Resolves: #809

PR is based on https://github.com/aiven/klaw/pull/831 so will stay DRAFT until the first one is merged.


Fixed crash on iOS

The code was crashing on iOS due to spaces in message parameter.
trimmingCharacters(in:) was obviously not working because only trims characters on both ends.
I also changed NSUrl with URL.

This is working well. Please merge.
It can be tested like this:
pubspec.yml
  flutter_open_whatsapp:
    git:
      url: git://github.com/quetool/flutter_open_whatsapp.git
      ref: 4246caf # https://github.com/rohit1814/flutter_open_whatsapp/pull/7

Hey @rohit1814 ! Can you please merge this fixes or allow @fdietze or @quetool to have write access to merge?


Possible to remove "configured" variable?

In the simple_window example there is some Code duplication going on in line 88 and 236:
examples/simple_window.rs#L88
examples/simple_window.rs#L236
My guess is, this is to ensure the buffer gets attached regardless of whether the surface or the buffer get created first, depending on whether the wl_shm or the xdg_wm_base global event is received first.
If instead of initializing the xdg_surface directly in the xdg_wm_base global event handler L101, we first request all globals, and then do an event_queue roundtrip in main we could get rid of this race condition.
Code:
fn main() {
    let conn = Connection::connect_to_env().unwrap();
    let display = conn.display();
    let mut event_queue = conn.new_event_queue();
    let qh = event_queue.handle();

    display.get_registry(&qh, ());

    let mut app = App {
        running: true,
        compositor: None,
        buffer: None,
        wm_base: None,
        surface: None,
        xdg_surface: None,
        top_level: None,
    };

    // use roundtrip to process this event synchronously
    event_queue.roundtrip(&mut app).unwrap();

    // initialize surface after globals are registered
    let compositor = app.compositor.as_ref().unwrap();
    app.surface = Some(compositor.create_surface(&qh, ()));
    let wm_base = app.wm_base.as_ref().unwrap();
    app.xdg_surface = Some(wm_base.get_xdg_surface(&app.surface.as_mut().unwrap(), &qh, ()));
    app.top_level = Some(app.xdg_surface.as_ref().unwrap().get_toplevel(&qh, ()));
    app.top_level.as_ref().unwrap().set_title("LAN Mouse".into());
    app.surface.as_ref().unwrap().commit();

    while app.running {
        event_queue.blocking_dispatch(&mut app).unwrap();
    }
}

Am I missing something? Does this not work for any reasons I'm not aware of?

Yes indeed, this organization works as well.
Actually, once https://github.com/Smithay/wayland-rs/pull/554 is merged it'll be possible to simplify this example quite a bit.

Ah that's awesome :+1:. Guess not worth a PR then so I'm closing this.


leap: Add variable to stub solution's signature.

Considering that leap is the first exercise of the track, this small change may help a beginner, because (he|she) may think that the part before = should not be changed.
More experienced students will certainly already know that they can eta-reduce the functions, so I think there is no harm.
To make the exercises more accessible to newcomers, I believe it is in general a good think to have a stub solution that:

Includes the simplest type signature acceptable by the test suite.
Includes a eta-abstracted fake implementation with reasonable variable names. I have been using undefined as the function body.
Compiles and fails the tests, if possible without ruining the challenge.

What do you think about it, @petertseng?

I think these are good ideas. I had hoped the meaning of the argument would be self-evident, but the note about beginners not thinking to change the part before = seems important. Did you observe this difficulty? Perhaps did someone submit a solution of the form leapYear = \y -> ... ?

Did you observe this difficulty?

Not really!
It's just that , now that you reordered the exercises, I'm  trying to lower the bar a little and make everything clear and easy in the first ones, to avoid anyone giving up too soon. Also, sometimes the variable name helps documenting the functions to be implemented.


Asp.net Core Identity Reset Token Not Url Safe? Leads to 404 Error

Hi
I am trying to use asp.net core identity and am running asp.net core 2.2
I am using the default implementation of asp.net identity core and use this line of code
 var token = await userManager.GeneratePasswordResetTokenAsync(employee);
I then url encode it like this
  token = HttpUtility.UrlEncode(token)
then send it via email and would look like this
https://www.example.com/forgotPassword/CfDJ8BocAWQJpDVCswirwjHYLWRCG6zZTSxopJgdO3DDm4aO3g3PDFOjmENf6aTbq4qNUF6lMQuOot%2f1e1xZYdkM%2fV9%2bvatM6UBYNBJsZRBuiNnvnX2dPnMv8ANqg56Q2jaCXfVvW4Q%2fwGDDud28NJsFPQIBcb%2bsTnnu%2f22qwfEODpXk4e1BB8VdJWXwzEy8r1F9dq4iptdVEAf5thdUn4lMMpxsKW5r63QLCnn19GPhUcQA
however when this link it clicked and redirected to my website I get a 404 error as iis seem to think this is a file on the system.
If I shorten the url down to something like this
CfDJ8BocAWQJpDVCswirwjHYLWRCG6zZTSxopJgdO3DDm4aO3g3PDFOjmENf6aTbq4qNUF6lMQuOot
which excludes the %2 it works fine.
This seems like a bug to me as this token should be able to work in a url.

@HaoK did the fix for this go in?

Not yet Eilon didn't like the quick and dirty regen when the token contains a '+' we will need to do something slightly less hacky (probably a shared helper in the UI code that does the html/token cleanup for all the code methods

@HaoK  @blowdart
Do you guys have an eta of when this will be fixed? When it is fixed which package would I need to update?

It should be fixed in 3.0, and the fix would be in the Identity.UI package

@HaoK
Ok so I will have update to core 3.0? Can you give an eta like will this be a month sort of thing or a week?

The fix for the other issue is just with our default templates/UI, you could adopt somthing similar in your code, but its not necessarily going to help your issue if you are generating tokens and sending emails yourself.
If you include the full code of generating the token + sending the email we can provide suggestions for you

@HaoK
My code is pretty simple, it pretty much is generate the token via built in command then send it via email.
        public async Task ForgotPasswordAsync(string email)
        {
            var employee = await userManager.FindByEmailAsync(email);
            if (employee != null)
            {
                var token = await userManager.GeneratePasswordResetTokenAsync(employee);
                if (token != null)
                {
                    var sent = await SendForgottenPassword(email, token);
                }

            }
        }

        public async Task<bool> SendForgottenPassword(string email, string token)
        {
            var msg = new SendGridMessage();
            msg.SetFrom(from);
            msg.AddTo(email);

            var dynamicTemplateData = new
            {
                token = HttpUtility.UrlEncode(token)
            };

            msg.SetTemplateData(dynamicTemplateData);

            var response = await sendGridClient.SendEmailAsync(msg);
        }

So the change we made to the templates was just to url encode the token before html encoding the full link, and then url decoding the token before checking it against identity.  You should be able to do the same thing in your code.  Hope that helps

@HaoK
So I have to do?
token = HttpUtility.UrlEncode(token)
token = WebUtility.HtmlEncode(token);

Yup, and then make sure you url decode the token on the way back

@HaoK
Hmm I am still having problems
Raw Token
CfDJ8IWFAz1gD91Pqn/zn4L4Op6X/4lessN26aG//jLLzOKnKFesBaKl+I5M+zXETVZexrHc8cl0zCSJhISZu5JKGT/i3AThLGwrICSzdqOkzDYFnx+2zR4tr2fUdT9Kc2QQ0kGKZaWA9Tf3bMJID6IaMnjXdbG2UKi+GYH7/YqVqW+HVCXopXHNXtxWIiqiY+/ltZ+ecDA5DlvY4+SwzeWu2UeOkHH5q8ZbShshLvAD53jU
now I added this line of code
 token = HttpUtility.HtmlEncode(HttpUtility.UrlEncode(token))

which results to
CfDJ8IWFAz1gD91Pqn%2fzn4L4Op6X%2f4lessN26aG%2f%2fjLLzOKnKFesBaKl%2bI5M%2bzXETVZexrHc8cl0zCSJhISZu5JKGT%2fi3AThLGwrICSzdqOkzDYFnx%2b2zR4tr2fUdT9Kc2QQ0kGKZaWA9Tf3bMJID6IaMnjXdbG2UKi%2bGYH7%2fYqVqW%2bHVCXopXHNXtxWIiqiY%2b%2fltZ%2becDA5DlvY4%2bSwzeWu2UeOkHH5q8ZbShshLvAD53jU
It still has %2f what still leads me to getting a 404.
as if I would shorten down to before the first %2f
CfDJ8IWFAz1gD91Pqn
it works.
I am using IIS btw.

Its not the token you need to html encode, you need to html encode the entire link that contains the url encoded token that you are emailing, so they can click on a link that works.

@HaoK
Well when I send out my email, I pass it to a send grid template which has
<a href="http://www.example.com/{{token}}">Reset Password </a>
what gets converted to
Reset Password
So why do I need to url encode the entire link?

Try sending the token as a query string

@HaoK
That will probably work, I just would have rather to used it as in a param as it is easy to get at(via react router).
Why do these tokens use unsafe symbols in the first place?

These are tokens and opaque to identity, in this case the tokens are generated using Base64 encoding which is not safe, the app is responsible for round tripping the tokens correctly to identity

@HaoK
But from what I can tell IIS does not like % stuff in the url, and as shown in my case no amount of encoding will make it accept it.
I would think this would be taken in consideration seeing it is all MS products.

@chobo2
this is due to segments default size limit to 255 in http.sys => IIS.
when %2F ( / ) is encoutred in a URL, a new segment is considered and then you can have another 255 chars
you can change the default size in the registry as described here
https://support.microsoft.com/en-us/help/820129/http-sys-registry-settings-for-windows


Streamline error codes

How to categorize this PR?

/area ops-productivity
/kind enhancement
What this PR does / why we need it:

Deprecates ERR_INFRA_INSUFFICIENT_PRIVILEGES error code.
Adds ERR_INFRA_UNAUTHENTICATED error code.

Which issue(s) this PR fixes:
Fixes #2469
Special notes for your reviewer:
@BeckerMax
Release note:

NONE

Please add changes after you opened the PR in separate commits. This makes it easier for reviewers to track the changes you make in response to feedback.

/lgtm
/hold until it is clarified if we first need changes in the dashboard merged, see  https://github.com/gardener/gardener/pull/5221#pullrequestreview-846245707

/lgtm
/unhold


feat(@schematics/angular): extend tslint:recommended

Updates the tslint.json file to extend to the tslint:recommended set.
Removes the rules that have the same value as the recommended one and explicitely deactivates some rules that are activated in the recommended set, but were not in ours.
Fixes #6179
cc @mgechev this is to start the discussion, feedback welcome

object-literal-key-quotes should be also disabled.

@mgechev good catch: I added object-literal-key-quotes: false 👍


Simpler getting started

@duftler @rbuskens ptal

I think this is a big improvement. LGTM.
@dstengle @dpeterka fyi

Sorry @tomaslin, missed your comment. I'll revert so it can be addressed.


22 initiate an xcode swift project for a single view iphone app

 Initiate an Xcode swift project for a single view iPhone app


fix: return SOC as INT instead of FLOAT

@Kolbi if you're good with the changes I made, feel free to merge.


Call to undefined function Edofre\Fullcalendar\JsExpression()

Hi, I just followed the README file.

When I run the following, nothing happens.

php artisan vendor:publish --tag=config
php artisan vendor:publish --tag=fullcalendar

When I go to calendar page I get the following error.

Call to undefined function Edofre\Fullcalendar\JsExpression()

The package put the following css and js, but links are not working. How can I modify the link?

Calendar

<link href="/css/fullcalendar.print.css" rel="stylesheet" media="print">
<link href="/css/fullcalendar.css" rel="stylesheet">

Hello @shinokada
Did you add the ServiceProvider and Facade? After that run the following commands
php artisan vendor:publish --tag=config php artisan vendor:publish --tag=fullcalendar
The files should be generated.

@shinokada There is mistake in the README exmaple, which causes that error.
Assuming you copied the exmaple as is:
Inside $calendar->setOptions() method, go to eventClick array key, and add new  before \Edofre\Fullcalendar\JsExpression(",
Before:
 'eventClick' => \Edofre\Fullcalendar\JsExpression("
After:
'eventClick' => new \Edofre\Fullcalendar\JsExpression("
@Edofre Please notice I created a pull request for fixing this issue: https://github.com/Edofre/laravel-fullcalendar/pull/24


Introduce contentless pages

See https://discourse.gohugo.io/t/templates-without-content-files-like-the-homepage-template/16660/
I first reacted negatively to this thread thinking Hugo is not the right tool and author should either cope or move along.
Yet the more I'm thinking about it, and the more people write about securing easier entry points to "learning the web" in 2019 (Rachel Andrew, Betsy Haibel), the more I think Hugo could help satisfy this need for a web 101 entry course level "framework".
People could and should of course introduce "content" in their slack later but why not being able to do without?
For example, what Marco is trying to achieve here is use Go Template and Hugo to teach students how to build websites. Starting with simple HTML files, partials, baseof etc... and not necessarily any content structure.
I wonder if there is an easy solution to spec and implement (maybe easier after #5583) that would allow that. Maybe by introducing a special layout directory and limiting those special layouts to the .Site context etc...
This issue is here to start a conversation about broadening Hugo's to more simplistic yet educational needs if that does not hamper the original mission.
Beside couldn't we all live without those:
---
title: contact
layout: contact
# that's it.
---

I still think this is a valid case.
It's already working for the homepage: the layouts/index.html gets rendered without a file in content/_index.md. Why can't we have the same mechanism for other layout files like layouts/about/index.html?
For more reasons about this see Templates without content files

This is still relevant. I've laid out some reasons in the thread Templates without content files. And I think @regisphilibert summed it up very nice in his issue description above. He mentions that it might be easier when we have a page interface and #5583 is implemented in the meantime.
Just imagine how much easier tutorials would be if we could start by just explaining the layouts folder and Hugo would work. I think it is even legitimate to keep quite a few pages without content files and just combine them with partials. Then, once you get to multiple pages having the same layout (for example a blog) it really makes sense to introduce the content folder.


reload protector should defer deletion of cookie.

https://github.com/komuw/ong/blob/07606656415a32bfc40c6f5e8737bd0187251b6b/middleware/reload_protect.go#L18-L28
		defer func() {
			cookie.Delete(
				w,
				theCookie,
				o.Domain,
			)
		}()

There's a bug where all second legitimate submissions of from fail

I don't think there's a bug. I had a html form like;
<form>
<button id="resetButton">Reset</button>
</form>

And everytime I would press the button it would submit an empty form, which I would presume to be a bug in ong.
But what I needed is;
<button id="resetButton" type="button">Reset purchase</button>
<!-- Make sure the button has a type==button so that it doesn't submit which is the default action for butoons. -->

https://en.wikipedia.org/wiki/Post/Redirect/Get


Finish mobile version

Build the "Works" section
Build the "About myself" section (placed after the projects and before the contact form)

new pull will be initiated


host-local should use /run and not /var for persistance

There's no reason for the IP assignments on the host to survive a reboot.

That is not actually obvious. Since (exited) containers might survive reboots, losing the IP <--> ContainerID mapping will cause the DEL command to fail.

So what's the plan?

Keeping as is.


Feature Idea: I suggest adding a folder for shared application data (log files, for example)

On Windows, shared data is c:\ProgramData\YourApp. I am not sure on other platforms. It would be great if your library provided a path that would be appropriate for a log file that is shared among all users.

Other operating systems does not offer a shared writable directory.
Even worse. *nix based systems requires special handling when writing to shared files to prevent security issues.
I want the folders returned to be safe by default.


Functional level discrepancy

This article says that Server 2008 is supported, yet the List of prerequisite checks says Server 2008 R2 is the minimum.

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

ID: 4c40b1d1-a46d-9e33-8bd5-f79e420d5d9c
Version Independent ID: d90820d6-bd8f-34d9-68ac-5300bf4fb516
Content: Supported Active Directory domains - Configuration Manager
Content Source: sccm/core/plan-design/configs/support-for-active-directory-domains.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @mestew
Microsoft Alias: mstewart

@aczechowski Which article would need to be updated? I'm guessing the "prereqs article" since the end of support date for 2008/2008R2 has not been reached yet.

Hi @jpcast88, sorry I missed this response! I checked with the engineering team, and our prereq check is still for 2003. 😮 So I suppose technically both articles should be updated to state 2003 domain functional level. (That seems a little weird to do, but it's honest and accurate.)
There was also a recent email thread about forest functional level. I honestly don't think it matters, but suppose we could add that as well in the same context.
@mestew any opinions?


Add cargo and rust fmt to the toolchain build

Hi,
I've been experimenting with my own build of the toolchain for a while now
https://github.com/esp-rs/rust
One of the things I've discovered is a unique bug associated with windows when using a linked / custom toolchain such as esp
Typically some tools such as "cargo make" or "rust-analyser" under visual studio code
tend to run cargo multiple times at the same time (similar to running it multithreaded)
If cargo isn't installed as part of the custom toolchain, then it tends to try and use the cargo native to the host.
But because of the way it does this, it tends to fail under windows when you try to run it more than once at the same time.

https://github.com/rust-lang/rustup/issues/2889

The best workaround I've found is to just install cargo into the custom toolchain
# Fixes VSCode Issues with rust-analyser / cargo-make
x.py build --stage 2 cargo

I also tend to add rustfmt for reformatting code
# Add rustfmt for reformatting code
x.py build --stage 2 rustfmt

Would there be any issues in adding these to the workflows script?
I think it would solve a lot of problems associated with rust-analyser and cargo make which are quite useful.

Just to add I've recently been doing a rather big re-write of the github workflows
I've gotten everything split into composite actions to make it easier to handle / read so that the top level workflow isn't massive.
I've also found a workaround for the path issue under windows, and fixed some build related issues as well.
and split the build into multiple jobs to avoid disk space issues.
Currently doing some tweaking for ubuntu then I'll test out macos since it should have the same unix based paths.

rustfmt is being built as part of the toolchain. Let me double check.

@grbd Which toolchain do you use as default?
Former instructions were written in that way that toolchain esp is set as default.
We changed the instructions to leave original default toolchain installed on the system and add option +esp to cargo command when building.
The build command looks like this: cargo +esp build
This command should result in using tools which are not part of custom toolchain directly from default toolchain.

I'm using it from a windows platform at the moment.
But it doesn't work if you try and run cargo multiple times at the same time while using a custom toolchain.
(which some dev tools such as rust-analyser, or cargo make do)
I think it's a wider issue with rust / rustup in the way they make cargo visible while using the custom toolchain
I think it's also only a windows issue.

@grbd I'm running build with esp-rs/rust branch esp-<IP_ADDRESS> - Ubuntu 18 rustc fails on this error:
Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
thread 'main' panicked at 'fs::read(stamp) failed with No such file or directory (os error 2) ("/home/runner/work/rust-build/rust-build/rust/build/x86_64-unknown-linux-gnu/stage2-rustc/x86_64-unknown-linux-gnu/release/.librustc.stamp")', src/bootstrap/lib.rs:1296:24

https://github.com/esp-rs/rust-build/runs/4394875515?check_suite_focus=true#step:8:7911
Any idea what might be wrong?

Hmm,
not sure at this point although I think a few things have been updated
The failure seems to be at
Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)

I think it's searching for the following but can't find it
/home/runner/work/rust-build/rust-build/rust/build/x86_64-unknown-linux-gnu/stage2-rustc/x86_64-unknown-linux-gnu/release/.librustc.stamp

I'll try pulling in the changes to a fork then run it on github workflows

I'm running some builds now to see if I can figure out where it is
my suspicion is that it's something ether in the esp rust src itself or something related to the runner
I did spot that you've changed .github/actions/util/checkout-esp-rust/action.yaml
from rust_version to release_version
Originally the way I had it setup was:

rust_version - the tag / branch checked out from esp-rs/rust such as 1.56.0
release_version - the name given to the final archive such as <IP_ADDRESS> (to indicate changes via rust-build)

@grbd Thank you very much for testing the build.
Here is explanation of action.yaml change: I've changed one occurrence of rust_version to release_version, because @MabezDev marked new branch as esp-<IP_ADDRESS>. In 1.56 it was marked as esp-1.56.0. Having build number at the end matching the release_version is better, because it's easier to recognize changes if multiple build of same Rust toolchain occurs.
Meanwhile I'm building all the versions locally, just to have working reference until we resolve mystery of GitHub runners. Rust builds are pretty complex and we encountered several strange issues like this before.

Ok that makes sense.
I'm testing the original build first (just to check github hasn't changed anything
then I'm going to slowly add the changes in from 1.57 to see where it fails

Hm, the issue seems to be related to .stamp on GitHub Runners.
I can recall some other project which was pushed to repo with timestamp "in-the-future" and GitHub Runner clocks were in different time zone which looks like "past" to cmake, and cmake was stuck in infinite loop of refresh. The solution was to touch all files before running cmake.

So I updated my own workflows to be identical to these but using 1.56.0 and that seemed to work fine
then I switched just the version from 1.56.0 to <IP_ADDRESS> and thats when it failed (on github's native runner)
So the difference I suspect is somewhere within https://github.com/esp-rs/rust
I might try and give this a quick go just to see if it makes any difference
https://github.com/szenius/set-timezone

@MabezDev @jessebraham  Any idea which change in Rust 1.57.0 bs 1.56.0 might caused build behavior described above as mentioned by @grbd ?

after a bit more testing it looks like it fails during the build of compiler/rustc
# Works ok here
python3 src/bootstrap/configure.py  --experimental-targets=Xtensa --enable-extended --dist-compression-formats='xz'
# Fails during the build of compiler/rustc
python3 x.py build --exclude src/doc --stage 2 compiler/rustc

The error shows up at
Assembling stage2 compiler (x86_64-unknown-linux-gnu)
Uplifting stage1 std (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
Copying stage2 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Uplifting stage1 rustc (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Assembling stage3 compiler (x86_64-unknown-linux-gnu)
thread 'main' panicked at 'fs::read(stamp) failed with No such file or directory (os error 2) ("/home/runner/work/rust-build/rust-build/rust/build/x86_64-unknown-linux-gnu/stage2-rustc/x86_64-unknown-linux-gnu/release/.librustc.stamp")', src/bootstrap/lib.rs:1296:24
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Build completed unsuccessfully in 2:01:59
Error: Process completed with exit code 1.

Maybe you get different results if you try building everything at once.
The workflows just build compiler/rustc as part of a job to get around disk space issues.
I think the separate build of the tools and library/std works ok
So maybe it's some form of build dependency related issue, might try building library/std first before hand to see what happens.

With RUST_BACKTRACE=1 enabled
thread 'main' panicked at 'fs::read(stamp) failed with No such file or directory (os error 2) ("/home/runner/work/rust-build/rust-build/rust/build/x86_64-unknown-linux-gnu/stage2-rustc/x86_64-unknown-linux-gnu/release/.librustc.stamp")', src/bootstrap/lib.rs:1296:24
stack backtrace:
   0: rust_begin_unwind
             at /rustc/59eed8a2aac0230a8b53e89d4e99d55912ba6b35/library/std/src/panicking.rs:517:5
   1: core::panicking::panic_fmt
             at /rustc/59eed8a2aac0230a8b53e89d4e99d55912ba6b35/library/core/src/panicking.rs:101:14
   2: bootstrap::Build::read_stamp_file
             at ./src/bootstrap/lib.rs:1296:24
   3: <bootstrap::compile::Assemble as bootstrap::builder::Step>::run
             at ./src/bootstrap/compile.rs:1107:27
   4: bootstrap::builder::Builder::ensure
             at ./src/bootstrap/builder.rs:1574:23
   5: bootstrap::builder::Builder::compiler
             at ./src/bootstrap/builder.rs:627:9
   6: <bootstrap::compile::Assemble as bootstrap::builder::Step>::make_run
             at ./src/bootstrap/compile.rs:1034:30
   7: bootstrap::builder::StepDescription::maybe_run
             at ./src/bootstrap/builder.rs:175:13
   8: bootstrap::builder::StepDescription::run
             at ./src/bootstrap/builder.rs:231:21
   9: bootstrap::builder::Builder::run_step_descriptions
             at ./src/bootstrap/builder.rs:619:9
  10: bootstrap::builder::Builder::execute_cli
             at ./src/bootstrap/builder.rs:599:9
  11: bootstrap::Build::build
             at ./src/bootstrap/lib.rs:624:13
  12: bootstrap::main
             at ./src/bootstrap/bin/main.rs:33:5
  13: core::ops::function::FnOnce::call_once
             at /rustc/59eed8a2aac0230a8b53e89d4e99d55912ba6b35/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

@grbd Thank you for the analysis.
I've tried to switch the order of rustc and std, but it does not help.
https://github.com/esp-rs/rust-build/runs/4429880343?check_suite_focus=true#step:9:84

Yep I tried the same thing myself without much luck

Components were added to artifacts. Thank you @grbd for the contribution. Code is on main.
GitHub runner limitation for 1.57 will be addressed as separate issue.


✨ [REQUEST] Paperless NGX add Tika and Gotenborg to process emails (eml files)

Currently Paperless NGX comes without Tika and Gotenberg. This leads to the Unsupported mime type message/rfc822 failure when importing emails from a mailbox (IMAP), through the consumer or the dashboard.
There is an example for docker compose in the paperless docs: https://docs.paperless-ngx.com/configuration/#tika
I will try to delve into a possible configuration but as you may have noticed already with my last pull request I am quite new to the HASS addon world, so if you have a starting point I'll be happy.

Hi! Indeed I see that it doesn't come with the image itself... I see three possible way forward: either add variables to the addons options (through modifying the "schema" with an optional "str?" type), that each user adds them to their config.yaml (that are then exported as env variable to the app), or the last (and best) option would be that we manage to add them to the dockerfile and start the services within the addon ... Not sure of the complexity though ;-)

Btw I'm not sure to remind your PR but for sure any PR is more than welcome! Maintaining those addons (especially those I don't use) take a lot of time so if you have any proposal on how to achieve that it would be great :-) (and significantly decrease the time it will take for the features to be implemented ;-) )
As a starting point, the best would probably that we :

Implement Tika & Gotenberg servers in the dockerfile (no idea how to do that)
create all those ENV variables as "optional options" (as here https://developers.home-assistant.io/docs/add-ons/configuration/#options--schema : they use yaml but globally it's the same idea with json)
then we create a script that looks if those variables are there, or use default values that will allow to use the embedded servers

Hope this makes sense ; actually I'm quite new to the dev scene (self learned what was useful to make the addon works) but I've spend a lot of time tweaking those addons so I've developed a few tricks to implement such options in the addons

I was wondering if it does not make more sense to add Tika and Gotenberg as their own independent containers, because other apps also may make use of it (e.g. Drupal).
There is a public Tika instance available underhttps://okfnlabs.org/projects/tika-server, it seems there I can start with a working dockerfile and try to convert it.
I also found that German guy running it all together in docker https://deployn.de/blog/setup-paperless/ and this compose collection https://github.com/abhilesh/self-hosted_docker_setups so let's see how those together with your existing addons may enlighten me to create a PR.
I especially like the trick with the external config files for advanced settings :-)

Hi, usually to build addons i try to base myself on existing containers and adapt them with the logic i follow in all my dockerfile. Either its based on s6 and a good example is emby, or not and a good example is filebrowser. Another alternative is to start from scratch based on a hassio base image (as the bitwarden or spotweb addons). Good luck :)

I've another trick in that my addons can execute a custom script if placed in /config/addons_autoscripts with the correct  name :) quite useful for debugging

Hi Alex,
Sorry to let you know my final approach was to migrate to the paperless ngx official docker compose on a more powerful device with a more sophisticated SSO function.
But thank you very much, without your add on I would not have jumped on the paperless train ;-)
Cheers,
Alex

Hi,
Thanks for the feedback! Glad you found a way forward for you. I really don't have much time for the moment due to a new job so I wouldn't have much time anyway to implement anything in a short timeframe. Indeed paperless is a great app!
Wishing you the best,
Cheers,
Alex

Addon deprecated, I recommend to use this one : https://github.com/BenoitAnastay/home-assistant-addons-repository


Fix PR doc generation

What does this PR do?

This PR fixes the issue where the PR doc cannot be pushed to the remote server.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Merging since the failed tests are not related to this PR.


CSS Networking - Removed sentence re creating a DNS record

Removed the misleading sentence stating that there needs to be a DNS record created for the private origin hostname.

@duongau
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Documentation / Tutorial

I believe the documentation of this project is extremely sparse (sorry, I know its not the fun part of a project ;) ). I'm not able to fully understand the code, even though the underlying concepts are slightly familiar (took some CQRS/event sourcing) work shops. Especially the sample is a bit of a mystery since it doesn't seem to use NEventStore but a XmlDocument for storage, (isn't the whole idea of NES to use NEventStore?). I'm also having trouble understanding from the sample why so much code needs to be duplicated (the create commands and events seem to do almost the same).
Now this all is probably due to a gap in knowledge, but without at least something resembling a tutorial I'm afraid I can't get much further (in a time efficient manner that is ;) ).
Is there any more documentation, or better: a tutorial, for the NES project? Or are there other resources that I should read first (maybe some NEventStore and NServiceBus manuals that I should read first, though the NEventStore documentation doesn't seem to be much more comprehensive :( ). So that its easier to get into NES? Or maybe NES isn't the right CQRS/Event Sourcing framework to start off with? I'm open to suggestions?

The framework is just a technical implementation of the CQRS. DDD is the part the people should focus on. So in this case I would suggest this book https://vaughnvernon.co/?page_id=168
If you look in the real word the command contains clear instructions what you should do. When the job is done you will write down all the things you have done and report it using the event. Between the command and report there will not be a huge gap, in the normal case. The event is the part which will be persisted into eventstore. In the NES example the denormilizer takes the reported event and persists the data into the database or in this sample into xml to use it as readmodel.
So we have here all parts you learned. Command, Domain, Eventstore, Denormilizer and Readmodel. You just need to identify them in the sample.

I understand (I've read Vernon's book). I think it would help if the sample actually used NEventStore, since wiring NEventStore with NEventBus is what this project is for ;). I'll see if I can get everything to work now (have slept on it, that always helps). Maybe I can contribute to the sample?

You are right. You can make a pull request :-) Thanks

The NES sample uses NServiceBus and NEventStore, it's what NES is for after all. Basically:

Website sends a command.
Endpoint handles the command.
Aggregate creates an event.
Event is persisted to the event store.
Endpoint publishes the event.
Endpoint handles the event.
Dto is persisted to XML file.

There's a few Q&As on stackoverflow that might be useful.
I hope this helps.

@elliotritchie
I've cloned the samples, and there isn't even a reference to NEventStore in it. So I'm still pretty sure its not using NEventStore ;). However, the Q&A you mentioned and the overview of order of events/commands is helpful :).
@marinkobabic cool, I'll see what I can do. Got a busy work week ahead so it might take some time.

https://github.com/elliotritchie/NES/blob/master/samples/NES.Sample/EndpointConfig.cs#L24-L28

@elliotritchie
It seems I'm having a bad day
No NEventStore: https://github.com/elliotritchie/NES/tree/master/samples/packages
NEventStore: https://github.com/elliotritchie/NES/blob/master/samples/NES.Sample/packages.config
:/ apologies.