reduction_ops_gpu_complex128.cu.pic.o was not created

System information

Ubuntu 18.04.2
https://github.com/VLOGroup/tensorflow-icg
CUDA 10
cudNN 7
Python 3.6.8 |Anaconda, Inc.|
GCC 7.3.0
Bazel version 0.11.1

While building Tensorflow-icg (https://github.com/VLOGroup/tensorflow-icg) on a Slurm Cluster occurred the error
 #warning "host_defines.h is an internal header file and must not be used directly.  This file will be removed in a future CUDA release.  Please use cuda_runtime_api.h or cuda_runtime.h instead."
  ^~~~~~~
./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(271): error: initializer not allowed for __shared__ variable

./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(320): error: initializer not allowed for __shared__ variable

./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(271): error: initializer not allowed for __shared__ variable

./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(320): error: initializer not allowed for __shared__ variable

./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(271): error: initializer not allowed for __shared__ variable

./tensorflow/core/kernels/reduction_gpu_kernels.cu.h(320): error: initializer not allowed for __shared__ variable

6 errors detected in the compilation of "/tmp/tmpxft_00005f84_00000000-7_reduction_ops_gpu_complex128.cu.compute_52.cpp1.ii".
ERROR: /cluster/ty00gyna/tensorflow-icg/tensorflow/core/kernels/BUILD:2709:1: output 'tensorflow/core/kernels/_objs/reduction_ops_gpu/tensorflow/core/kernels/reduction_ops_gpu_complex128.cu.pic.o' was not created

ERROR: /cluster/ty00gyna/tensorflow-icg/tensorflow/core/kernels/BUILD:2709:1: not all outputs were created or valid
Target //tensorflow/tools/pip_package:build_pip_package failed to build

https://github.com/tensorflow/tensorflow/commit/3c245f52912612ed9d8e20245ddb5de055680969
and :
Modify "./tensorflow/core/kernels/reduction_gpu_kernels.cu.h"
replace:
shared value_type partial_sums[32 * 33];
by:
shared align(
alignof(value_type)) char partial_sums_raw[32 * 33 * sizeof(value_type)];
value_type* partial_sums = reinterpret_cast<value_type*>(partial_sums_raw);

@Tayseer-bme Could you provide more details on the issue and context? Thanks!

@jvishnuvardhan
while building tensorflow, we can solve this error by following this steps:
1- Modify "tensorflow/core/platform/macros.h" as same as in the link
https://github.com/tensorflow/tensorflow/commit/3c245f52912612ed9d8e20245ddb5de055680969
2- Modify "./tensorflow/core/kernels/reduction_gpu_kernels.cu.h"
replace:
shared value_type partial_sums[32 * 33];
by:
shared align(
alignof(value_type)) char partial_sums_raw[32 * 33 * sizeof(value_type)];
value_type* partial_sums = reinterpret_cast<value_type*>(partial_sums_raw);
the problem is solved

@Tayseer-bme would you like to send a pull request with the fixes you proposed?

@gunan I don't know a lot about a pull request !

Automatically closing this out since I understand it to be resolved, but please let me know if I'm mistaken. If anyone interested in creating PR, please feel free to create a PR. Thanks!

I have still the exact same issue, has it been resolved?


Fix #to_rack to handle non-array response bodies.

When using #to_rack with a Rails endpoint, such as:
stub_request(:any, %r{api.example.com/.*}).to_rack(Rails.application)

...you receive the following error:
NoMethodError: undefined method `join' for #<ActionDispatch::Response:0x007ffd06e6f540>

Turns out ActionDispatch::Response is in the right. A Rack response body
is only required to implement #each, not #join.
This patch fixes #to_rack to build the body using the #each method.

Thank you for the patch!


Fix typo

Change "klass" to "class".

Hi @fengzee-me,
Thanks for the PR. In this case, this isn't a typo. This is actually a common convention, when you have a local variable of type Class. The convention comes from other languages like Java & Ruby where the type is class (note the lowercase c) which means it's a reserved keyword that can't be used as a variable name. Anyways, it's not strictly necessary in Objective-C here, but I've chosen to write it this way to follow the convention and indicate that the variable's type is a Class.

Hi @smileyborg,
Thank you for telling me this. I am a beginning developer and was unaware of this convention. Your code is beautiful. I hope you don't mind me taking them as a learning resource. Thank you.


[BUG] Doesn't pick up @Context parameter annotations from interface

Q
A

Bug or feature request?
BUG

Which Swagger-Core version?
2.0.0

Which Java version?
1.8.0_144

Which JAX-RS framework & version?
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Repro
Create a endpoint like this:
public interface MyController {
    @GET
    @Path("doober/{param1}")
    @Operation(summary = "Doober doo")
    Response doober(@Context MyContext context,
        @Parameter(description = "Stuff about param1") @PathParam("param1") String param1);
}

public class MyControllerImpl implements MyController {
    @Override
    public Response doober(MyContext context, String param1) {
        return Response.ok().build();
    }
}

Actual Result
The following is at paths['/doober/{param1}']:
{
  "get": {
    "summary": "Doober doo",
    "operationId": "doober",
    "requestBody": {
      "content": {
        "*/*": {
          "schema": {
            "$ref": "#/components/schemas/MyContext"
          }
        }
      }
    },
    "responses": {
      "default": {
        "description": "default response",
        "content": {
          "application/json": {}
        }
      }
    }
  }
}

Expected Result
{
  "get": {
    "summary": "Doober doo",
    "parameters": [
      {
        "name": "param1",
        "description": "Stuff about param1",
        "in": "path",
        "required": true,
        "schema": {
          "type": "string"
        }
      }
    ],
    "responses": {
      "default": {
        "description": "default response",
        "content": {
          "application/json": {}
        }
      }
    }
  }
}

Looks like this actually a change from how 1.5 worked. You have to place the parameter annotations (@Parameter and @PathParam) on the implementing class in order for it to work. In 1.5, it would pick up the parameter annotations from the interface.

This doesn't seem to be reproducible, your latest version of the resources in a Jersey2 env produces your expected result, when using 2.0.0 release version. In case you're indeed using 2.0.0 release version, please share some more details, e.g. how you're registering the resources and any significant data.

Definitely using 2.0.0:
$ mvn dependency:tree -Dverbose | grep -i swagger
[INFO] +- io.swagger.core.v3:swagger-jaxrs2:jar:2.0.0:compile
[INFO] |  +- io.swagger.core.v3:swagger-models:jar:2.0.0:compile
[INFO] |  +- (io.swagger.core.v3:swagger-annotations:jar:2.0.0:compile - omitted for duplicate)
[INFO] |  +- io.swagger.core.v3:swagger-integration:jar:2.0.0:compile
[INFO] |  |  +- io.swagger.core.v3:swagger-core:jar:2.0.0:compile
[INFO] |  |  |  +- (io.swagger.core.v3:swagger-annotations:jar:2.0.0:compile - omitted for duplicate)
[INFO] |  |  |  +- (io.swagger.core.v3:swagger-models:jar:2.0.0:compile - omitted for duplicate)
[INFO] |  |  \- (io.swagger.core.v3:swagger-models:jar:2.0.0:compile - omitted for duplicate)
[INFO] +- io.swagger.core.v3:swagger-annotations:jar:2.0.0:compile

We use dropwizard (0.9.3) and register our controllers with jersey through Spring annotations:
    public void run(MyConfiguration configuration, Environment environment) throws Exception {
        JerseyEnvironment jersey = environment.jersey();

        // Register controllers.
        for (Map.Entry entry : applicationContext.getBeansWithAnnotation(Controller.class).entrySet()) {
            jersey.register(entry.getValue());
        }

Our implementation classes are the ones with the Controller Spring annotation.

Ok, I managed to pin it down to the use of a @Context parameter. I updated my repro steps above.

I am still not able to reproduce, registering your latest version of resources in the dropwizard sample (environment.jersey().register(new MyControllerImpl());) produces your expected result. If you can test your resources in a similar env and see if you get the same issue, we could restrict the troubleshooting area..


Localization for default (entityframework) validators

At the moment I have a working situation for localizing my custom (and default) attributes.
In general I do it like this:
[OnlyValidCharacters] // my own validator
[MaxLength(40, ErrorMessageResourceName = "MaxLength", ErrorMessageResourceType = typeof(MyProject))]
public string LastName { get; set; }

// my custom validator sets ErrorMessage like so (in its constructor)
public static readonly string InvalidCharacters = @"<>!@#$%^&*()";
...
ErrorMessage = string.Format(MyProject.FormInvalidCharacters, InvalidCharacters);

I have a myproject.en.resx and a myproject.resx file (with an equivalent MyProject.Designer.cs file.
However, I feel that for the default validators (like MaxLength) it should be easier to override their default translation.
I would expect my code to be like this:
[OnlyValidCharacters] // my own validator
[MaxLength(40)] // do not use my own 'maxLength' thing but the default key 'MaxLengthAttribute_ValidationError'
public string LastName { get; set; }

And let the default key for validating being overridden in my project. (in this case, the key is MaxLengthAttribute_ValidationError).
I found a resources.resx file in the EntityFramework project and I tried to override the key MaxLengthAttribute_ValidationError.
I have tried to override this as following (non where successful):

add MaxLengthAttribute_ValidationError to my own resource file (myproject.en.resx)
create a file resources.resx in my project (root level), add MaxLengthAttribute_ValidationError` to override
tried also with filename resource.resx - since a few MVC 4/5 projects where referring to such a filenaming structure.

None of this seems to work.
I feel this ought to be fairly easy to override. I can't seem to find anything using my google voodoo (neither on github, wiki's, asp.net documentation, etc). So perhaps anyone can enlight me?

ErrorMessageResourceName  ErrorMessageResourceType don't work with this localization...
You're meant to use the new style.

Correct, the old style and new style are both fine, but they don't talk to each other.
We have a complete sample of localizing a simple MVC app, including localizing Data Annotations validation attributes: https://github.com/aspnet/Entropy/tree/dev/samples/Mvc.LocalizationSample.Web

The model: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Models/Product.cs
A localized resource: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Resources/Models.Product.fr.resx
The setup code: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Startup.cs

This is not exactly the same. As i have to localize per model.
I want to localize on validator level and override defaults.
If I understand correctly this seems to be not possible.
Btw the examples I posted are working scenario's. So messagetype/name do work there.
Any way to override on validator level? (Ie the resources.resx file of entityframework) without the need to override per model, nor providing "errorMessage" as key? Even that sollution is still requiring me to duplicate keys.
Thx for any advice.

Op 3 aug. 2016 om 19:36 heeft Eilon Lipton<EMAIL_ADDRESS>het volgende geschreven:
Correct, the old style and new style are both fine, but they don't talk to each other.
We have a complete sample of localizing a simple MVC app, including localizing Data Annotations validation attributes: https://github.com/aspnet/Entropy/tree/dev/samples/Mvc.LocalizationSample.Web
The model: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Models/Product.cs
A localized resource: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Resources/Models.Product.fr.resx
The setup code: https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.LocalizationSample.Web/Startup.cs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@stefanhendriks perhaps I'm not understanding what isn't working then? I'm pretty sure there was never a way to change the global default validation messages for the built-in data annotations validation attributes...

@Eilon perhaps this is a feature request then? ;-) - it would be very handy to have (from a maintenance standpoint).
I try to give a bit background information, write down a suggestion and perhaps this is something for the future. I hope it would be considered. It would make life really easier.
So, my use case is as following
I have a bunch of models (quite a lot). They have a custom validators and default validators. I want to localize messages for both of them. For my custom validators I can set the ErrorMessageResourceName and ErrorMessageResourceType in my constructor and it works fine. (personally I find using the new way, ie errorMessage as a key for translations, an ugly hack tbh).
At this moment, it means when I add a validation attribute to a new property I have to explicitly set the ErrorMessageResourceName and ErrorMessageResourceType . This is not required for my custom validators. Even with the 'new' way of doing things I still have to explicitly set the errorMessage, which is the same thing maintenance-wise.
This means whenever I forget to do so I get a different (non-translated) error message.
From a maintenance standpoint I would expect to not even have to set the localization properties, because there are ways to figure out the keys instead of having the 'set' them.
But lets say you want this for all custom validators, it would not make sense to enforce this for the default validator attributes - from the moment you want to deviate from the default translations.
I think it is not nescesary to enforce this, because I think this is accommodated for using the resources.resx file in the EntityFramework repository.
I have worked in several languages and different MVC frameworks, and what I found very pleasing to use was this 'hierarchy' that was offered in some localization packages. But for this scenario it boils down to 2 levels:

you have a model level (ie, myModel.myField.MaxLength=Your myField cannot be longer than {0} chars)
there is an attribute level: (ie string.maxLength=Your string cannot be longer than {0} chars)

In the current situation, regardless of using the 'new' or the 'old' way: I always need to be very specific on the model level. This makes it very tedious to maintain the code, and it also feels very redundant, because the validator itself is not changed, and I only set the ErrorMessageResourceType and ErrorMessageResourceName because there does not seem to be a way to override in a more elegant way (see suggestion below).
In short:
It would be very handy to have an attribute level for localization.
In my case, I would expect to have the key MaxLengthAttribute_ValidationError to be defined in my own <project>.resx file, and whenever it is found it overrides the default one in the EntityFramework package.
This is because within EntityFramework itself there is a resources.resx file, and it contains a key MaxLengthAttribute_ValidationError with a value.
And to make it play nice with the current 'new' way of working, I would suggest:
Once the code figures out what key to look for. Look in the following order (in the resources);

check the <resourcesBasePath>/models/<mymodel namespace>/<mymodelname>.resx file if key is present (which basically is what it does now)
when not found, go one level up in hierarchy of namespace until found (don't know if this is already working). Example, you go from com.mycompany.models.account.registration to com.mycompany.models.account to com.mycompany.models.account until com.mycompany.models
when still not found, fall back to <projectname>.resx and check for defaults.
when still not found, fall back to existing default behavior (fetch it from the library that offered this, in this case EntityFramework - whatever it always was doing)

This only applies when nothing is specified, meaning all the current scenario's (when specifying errorMessage or ErrorMessageResourceType and ErrorMessageResourceName) will still work.
I can imagine you don't want to be a default behavior (since it is 'new'), so perhaps a flag should be set when setting up the webapp. (ie, UseDefaultHierarchyTraversingLocalization thingy?)
one more (other) thing
Above that all, one thing that would be elegant (for the 'new' way of doing things):

If errorMessage is not given, and ErrorMessageResourceType and ErrorMessageResourceNameare also not given, then assume the name of thevalidate attributeclass (minus the wordattribute). So MaxLengthAttributeis used asMaxLengthon property, so I would assumeMaxLengthas key in myresx` files.

I hope this clears a few things up. Sorry for the lengthy post. Thanks for the quick responses so far!

@stefanhendriks that's an interesting idea, but it's more of a feature request, would you mind creating a new issue to that effect?
In the mean time, you could prevent the repetitive ErrorMessage entering by sub-classing the attributes in question and setting the ErrorMessage to whatever you want. If you do that you'll have to implement IValidationAttributeAdapterProvider in such a way that it finds the new attributes.
Another option here would be for the more than the English resource to be included here so that at least in some languages you wouldn't need to localize these built-in's yourself if you were fine with the default phrasing.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Jamie new logo

Just replacing the SVG files for the icon & logo, and the PNG file for the favicon. We can probably delete the "old" versions, I don't know. I'm just renaming them with the -old extension for now.

Could you just delete the old version please?


Incorrect null pointer check

CLA: trivial
There is an incorrect null pointer check and this ccommit resolves it.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

This pull request is ready to merge

Merged to master, openssl-3.1 and openssl-3.0. Thank you for your contribution!


Fix Google Sans font breaking in Custom DC

Adds alternate body fonts to the tools, because Google Sans is not an open source font. This will allow other fonts to render in custom DC instead of the default serif font of the browser.

Thanks for the review! Will add Poppins as followup PR.


Minor code cleanup

Added some comments to log prob function, deleted some extraneous code

lgtm, thanks @mikeshwe!


feat: Support the group column being a string

Fixes https://github.com/Azure/mmlspark/issues/710

/azp run

@chris-smith-zocdoc are you able to see the style check errors?  it looks like some lightgbm tests failed also.  I will be traveling to Seattle the rest of this week and responses may be delayed.

/azp run

@chris-smith-zocdoc are you able to see the style check errors? it looks like some lightgbm tests failed also. I will be traveling to Seattle the rest of this week and responses may be delayed.

I think I fixed them in the latest commit. I am able to see https://app.codacy.com/manual/mhamilton723/mmlspark/pullRequest?prid=4318322 if that is the one you're referring to

/azp run

nope there's another one, it's this style check here:
https://msazure.visualstudio.com/Cognitive Services/_build/results?buildId=25855827&view=logs&jobId=3f85e25b-fb23-5eb7-8385-51966a33df73
maybe you don't have access

I do not have access to that one, it takes me to a microsoftonline login (login.microsoftonline.com)

@chris-smith-zocdoc  thanks for this PR heres the style lines:
2019-10-15T20:28:42.6317794Z [error] /home/vsts/work/1/s/src/main/scala/com/microsoft/ml/spark/lightgbm/TrainUtils.scala:68:8: Redundant braces after class definition
2019-10-15T20:28:42.6318682Z [error] /home/vsts/work/1/s/src/main/scala/com/microsoft/ml/spark/lightgbm/TrainUtils.scala:72:20: Redundant braces after class definition
2019-10-15T20:28:42.6319558Z [error] /home/vsts/work/1/s/src/main/scala/com/microsoft/ml/spark/lightgbm/TrainUtils.scala:74:20: Redundant braces after class definition
2019-10-15T20:28:42.6320413Z [error] /home/vsts/work/1/s/src/main/scala/com/microsoft/ml/spark/lightgbm/TrainUtils.scala:76:20: Redundant braces after class definition

Thanks @mhamilton723 I was able to see the scalastyle warnings locally. I pushed a fix

/azp run


Does it support annotation?

@liangge013 Maybe not, I don't have that type of PDF, so I didn't test it. Pdf.js seems to be supported, but you need to implement it yourself


Function not invokable at specified path; returns 404 (nginx)

Expected Behaviour
The function deployed in the steps below should be invokable at http://example.kube/api/v1/test/.
Current Behaviour
The function deployed is not reachable at http://example.kube/api/v1/test/ but rather a 404 (by Nginx) is returned. Visiting http://example.kube/api/v1/test/(.*) also returns a 404 (OpenFaaS). While the function works as intended at http://gw.example.kube/function/test-fn
Are you a GitHub Sponsor (Yes/No?)

Check at: https://github.com/sponsors/openfaas

[ ] Yes
[x] No

List All Possible Solutions and Workarounds
The only workarounds I can think of right now. Are to either call the gateway path (i.e., not using the ingress-operator) or manually compose and maintain ingresses.
Which Solution Do You Recommend?

I'd prefer it if I got ingress-operators working as intended.
Steps to Reproduce (for bugs)

Start with a clean kubernetes cluster.
Add <IP_ADDRESS> example.kube and <IP_ADDRESS> gw.example.kube to your hosts file.
Execute the following shell script

GW_HOST="http://gw.example.kube"
FN_NAME="test-fn"

# Create namespaces
kubectl create namespace ingress-nginx
kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml

# Update chart repos
helm repo add nginx-stable https://helm.nginx.com/stable
helm repo add openfaas https://openfaas.github.io/faas-netes/

helm repo update

# Apply charts
helm install example-ingress nginx-stable/nginx-ingress \
    -n ingress-nginx \
    --set rbac.create=true

helm install openfaas openfaas/openfaas \
    -n openfaas  \
    --values openfaas.yml

# Wait for OpenFaaS to start
sleep 60

# Login to gateway
echo $(kubectl -n openfaas get secret basic-auth -o jsonpath="{.data.basic-auth-password}" | base64 --decode) | faas-cli login -g $GW_HOST -u admin --password-stdin

# Get and host base node14 template
faas-cli template store pull node14
faas-cli new $FN_NAME --lang node14 -g $GW_HOST
faas-cli build -f "$FN_NAME.yml"
faas-cli deploy -f "$FN_NAME.yml"

# Apply FunctionIngress for test-fn
kubectl apply -f test-fi.yml

with the following files:
# openfaas.yml
functionNamespace: openfaas-fn
generateBasicAuth: true
ingressOperator:
  create: true
ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
  hosts:
    - host: gw.example.kube
      serviceName: gateway
      servicePort: 8080
      path: /
faasnetes:
  imagePullPolicy: IfNotPresent

# test-fi.yml
apiVersion: openfaas.com/v1alpha2
kind: FunctionIngress
metadata:
  name: test-fn
  namespace: openfaas
spec:
  domain: "example.kube"
  function: "test-fn"
  ingressType: "nginx"
  path: "/api/v1/test/(.*)"

Go to http://example.kube/api/v1/test/

Context
I'm trying to create a more REST-like path for my api. As well as, replace existing apis with functions.
Your Environment

FaaS-CLI version ( Full output from: faas-cli version ):

  ___                   _____           ____
 / _ \ _ __   ___ _ __ |  ___|_ _  __ _/ ___|
| | | | '_ \ / _ \ '_ \| |_ / _` |/ _` \___ \
| |_| | |_) |  __/ | | |  _| (_| | (_| |___) |
 \___/| .__/ \___|_| |_|_|  \__,_|\__,_|____/
      |_|

CLI:
 commit:  72816d486cf76c3089b915dfb0b66b85cf096634
 version: 0.13.13

Docker version docker version (e.g. Docker 17.0.05 ):
20.10.7
What version and distriubtion of Kubernetes are you using? kubectl version
I'm using Docker Desktop's Kubernetes at version 1.21.2
Operating System and version (e.g. Linux, Windows, MacOS):
Windows 10, kubectl reports that the cluster is running on Linux
Helm version
3.5.3

/msg: enduser

@HighCrit and @alexellis  I could not reproduce this.
I had to modify the instructions a little bit to work in kind, but this is the process i used which shows a working function ingress:

Create the file cluster.yaml
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  kubeadmConfigPatches:
  - |
    kind: InitConfiguration
    nodeRegistration:
      kubeletExtraArgs:
        node-labels: "ingress-ready=true"
  extraPortMappings:
  - containerPort: 80
    hostPort: 80
    protocol: TCP
  - containerPort: 443
    hostPort: 443
    protocol: TCP
  - containerPort: 31112
    hostPort: 8080
    protocol: TCP

This configures kind to bind the ports 80:80, 443:443, and 31112:8080. Which makes the ingress available on localhost an the gateway available on 8080 (the default cli value).
Now create the cluster
kind create cluster --config=cluster.yaml

Next create the required namespaces
# Create namespaces
kubectl create namespace ingress-nginx
kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml

Then install nginx-ingress using the instructions from kind https://kind.sigs.k8s.io/docs/user/ingress/#ingress-nginx
VERSION=$(curl https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/stable.txt)
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/${VERSION}/deploy/static/provider/kind/deploy.yaml

The manifests contains kind specific patches to forward the hostPorts to the ingress controller, set taint tolerations and schedule it to the custom labelled node.

Now we can install openfaas,
first create the file openfaas.yaml
# openfaas.yaml
functionNamespace: openfaas-fn
generateBasicAuth: true
ingressOperator:
  create: true
ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
  hosts:
    - host: gw.example.kube
      serviceName: gateway
      servicePort: 8080
      path: /
faasnetes:
  imagePullPolicy: IfNotPresent

and then run
helm repo add openfaas https://openfaas.github.io/faas-netes/
helm repo update

helm install openfaas openfaas/openfaas \
    -n openfaas  \
    --values openfaas.yaml

Wait for the gateway to startup
kubectl wait --namespace openfaas \
  --for=condition=ready pod \
  --selector=app=gateway \
  --timeout=90s

Now we can authenticate the CLI
echo $(kubectl -n openfaas get secret basic-auth -o jsonpath="{.data.basic-auth-password}" | base64 --decode) | faas-cli login -u admin --password-stdin

Deploy a test function
faas-cli store deploy nodeinfo

Wait a moment and then verify the function is running by using
faas-cli invoke nodeinfo

We can now create the FunctionIngress
apiVersion: openfaas.com/v1alpha2
kind: FunctionIngress
metadata:
  name: test-fn
  namespace: openfaas
spec:
  domain: "example.kube"
  function: "nodeinfo"
  ingressType: "nginx"
  path: "/api/v1/test/(.*)"

Apply the FunctionIngress
kubectl apply -f test-fi.yml

Wait a moment and test the ingress is working
$ curl -v http://example.kube/api/v1/test/
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to example.kube (<IP_ADDRESS>) port 80 (#0)
> GET /api/v1/test/ HTTP/1.1
> Host: example.kube
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Sat, 10 Jul 2021 14:17:28 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 105
< Connection: keep-alive
< Etag: W/"69-hQd9Fsiq+ZlCoMo3qufaUyrnJ44"
< X-Call-Id: 535b3b84-b71d-4b78-94b8-f11f83c400d2
< X-Duration-Seconds: 0.021057
< X-Start-Time:<PHONE_NUMBER>979244691
<
Hostname: nodeinfo-7547c56bbb-zdj2f

Arch: x64
CPUs: 8
Total mem: 15702MB
Platform: linux
Uptime: 107548
* Connection #0 to host example.kube left intact

You can see it in the nginx access logs
$ kubectl -n ingress-nginx logs deploy/ingress-nginx-controller
// truncated
<IP_ADDRESS> - - [10/Jul/2021:14:06:13 +0000] "GET /api/v1/test/ HTTP/1.1" 200 105 "-" "curl/7.68.0" 88 0.025 [openfaas-gateway-8080] [] <IP_ADDRESS>:8080 105 0.024 200 cde4d1118c0d49df78b81fd8dc2ae0fd
<IP_ADDRESS> - - [10/Jul/2021:14:17:28 +0000] "GET /api/v1/test/ HTTP/1.1" 200 105 "-" "curl/7.68.0" 88 0.031 [openfaas-gateway-8080] [] <IP_ADDRESS>:8080 105 0.032 200 473f95b3949a3fc102fdfe29d5e4e06d

I made two important changes to the instructions

i change the cluster config so that the required ports were immediately bound to localhost
i did not use the nginx-ingress helm chart. I tried this several times but it had various issues even starting. Once i switched to the install manifest prepared by the kind team, it started working immediately.

I think this shows that  the reported issue is mostly a configuration problem in the cluster or nginx-ingress.
@HighCrit  Getting the logs directly from nginx-ingress-controller would be very helpful to further debug the problem.

Thank you for your time @LucasRoesler, I started with a clean cluster again and re-ran the script.
$ curl -v http://example.kube/api/v1/test/
VERBOSE: GET http://example.kube/api/v1/test/ with 0-byte payload
curl : 404 Not Found
nginx/1.21.0
At line:1 char:1
+ curl -v http://example.kube/api/v1/test/
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

$ curl -v http://gw.example.kube/function/test-fn/
VERBOSE: GET http://gw.example.kube/function/test-fn/ with 0-byte payload
VERBOSE: received 41-byte response of content type text/html; charset=utf-8

StatusCode        : 200
StatusDescription : OK
Content           : {"body":"{}","content-type":"text/plain"}
RawContent        : HTTP/1.1 200 OK
                    Connection: keep-alive
                    X-Call-Id: 0ebb24d4-ac52-47fa-b1bc-4783bd3e7e87
                    X-Duration-Seconds: 0.005746
                    X-Start-Time:<PHONE_NUMBER>691038900
                    Content-Length: 41
                    Content-Type: text/html; ...
Forms             : {}
Headers           : {[Connection, keep-alive], [X-Call-Id, 0ebb24d4-ac52-47fa-b1bc-4783bd3e7e87], [X-Duration-Seconds, 0.005746], [X-Start-Time,<PHONE_NUMBER>691038900]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : mshtml.HTMLDocumentClass
RawContentLength  : 41

Here is the log of the nginx controller for both requests:
$ kubectl -n ingress-nginx logs deploy/example-ingress-nginx-ingress
// truncated
2021/07/10 15:21:08 [error] 174#174: *16 "/etc/nginx/html/api/v1/test/index.html" is not found (2: No such file or directory), client: <IP_ADDRESS>, server: example.kube, request: "GET /api/v1/test/ HTTP/1.1", host: "example.kube"
<IP_ADDRESS> - - [10/Jul/2021:15:21:08 +0000] "GET /api/v1/test/ HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.19041.1023" "-"
<IP_ADDRESS> - - [10/Jul/2021:15:23:12 +0000] "GET /function/test-fn/ HTTP/1.1" 200 41 "-" "Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.19041.1023" "-"

@HighCrit can you share the portion of the logs your truncated? it should say something about trying to configure nginx in response to the ingress definition
it is clearly misconfigured, because nginx is trying to respond to the request as if it were a static folder and not an upstream server, that is clear from this line in the logs
2021/07/10 15:21:08 [error] 174#174: *16 "/etc/nginx/html/api/v1/test/index.html" is not found

The truncated portion might be helpful to understand what the nginx-ingress operator is doing

@HighCrit your original script showed using helm to install nginx-ingress. The nginx-ingress team provide a Docker for Desktop specific manifest file that will probably resolve this issue for you https://kubernetes.github.io/ingress-nginx/deploy/#docker-desktop

@LucasRoesler when using the Docker Desktop specific manifest instead of helm the issue appears to be fixed. Although I find it strange that the helm chart doesn't work as it otherwise operates as expected.
Here is the entire log of the nginx controller (when using helm):
I0711 20:26:31.585826       1 main.go:271] Starting NGINX Ingress controller Version=1.12.0 GitCommit=c9d3618da566b158a53a6da098ff677aac28b7ff Date=2021-06-30T10:34:29Z PlusFlag=false
W0711 20:26:31.599961       1 main.go:310] The '-use-ingress-class-only' flag will be deprecated and has no effect on versions of kubernetes >= 1.18.0. Processing ONLY resources that have the 'ingressClassName' field in Ingress equal to the class.
W0711 20:26:31.601871       1 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList
I0711 20:26:31.604390       1 main.go:413] Using nginx version: nginx/1.21.0
2021/07/11 20:26:31 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:31 [notice] 17#17: nginx/1.21.0
2021/07/11 20:26:31 [notice] 17#17: built by gcc 8.3.0 (Debian 8.3.0-6)
2021/07/11 20:26:31 [notice] 17#17: OS: Linux 4.19.128-microsoft-standard
2021/07/11 20:26:31 [notice] 17#17: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2021/07/11 20:26:31 [notice] 17#17: start worker processes
2021/07/11 20:26:31 [notice] 17#17: start worker process 18
2021/07/11 20:26:31 [notice] 17#17: start worker process 19
2021/07/11 20:26:31 [notice] 17#17: start worker process 20
2021/07/11 20:26:31 [notice] 17#17: start worker process 21
2021/07/11 20:26:31 [notice] 17#17: start worker process 22
2021/07/11 20:26:31 [notice] 17#17: start worker process 23
2021/07/11 20:26:31 [notice] 17#17: start worker process 24
2021/07/11 20:26:31 [notice] 17#17: start worker process 25
2021/07/11 20:26:31 [notice] 17#17: start worker process 26
I0711 20:26:31.617295       1 listener.go:55] Starting Prometheus listener on: :9113/metrics
2021/07/11 20:26:31 [notice] 17#17: start worker process 27
I0711 20:26:31.617663       1 leaderelection.go:243] attempting to acquire leader lease ingress-nginx/example-ingress-nginx-ingress-leader-election...
2021/07/11 20:26:31 [notice] 17#17: start worker process 29
2021/07/11 20:26:31 [notice] 17#17: start worker process 30
2021/07/11 20:26:31 [notice] 17#17: start worker process 31
2021/07/11 20:26:31 [notice] 17#17: start worker process 32
2021/07/11 20:26:31 [notice] 17#17: start worker process 33
W0711 20:26:31.620141       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
2021/07/11 20:26:31 [notice] 17#17: start worker process 34
W0711 20:26:31.624703       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
I0711 20:26:31.626922       1 leaderelection.go:253] successfully acquired lease ingress-nginx/example-ingress-nginx-ingress-leader-election
W0711 20:26:31.718563       1 controller.go:3048] Using the DEPRECATED annotation 'kubernetes.io/ingress.class'. The 'ingressClassName' field will be ignored.
W0711 20:26:31.718638       1 controller.go:2157] Error retrieving endpoints for the service gateway: No endpoints for target port 8080 in service gateway
2021/07/11 20:26:31 [notice] 17#17: signal 1 (SIGHUP) received from 40, reconfiguring
2021/07/11 20:26:31 [notice] 17#17: reconfiguring
2021/07/11 20:26:31 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:31 [notice] 17#17: start worker processes
2021/07/11 20:26:31 [notice] 17#17: start worker process 41
2021/07/11 20:26:31 [notice] 17#17: start worker process 42
2021/07/11 20:26:31 [notice] 17#17: start worker process 43
2021/07/11 20:26:31 [notice] 17#17: start worker process 44
2021/07/11 20:26:31 [notice] 17#17: start worker process 45
2021/07/11 20:26:31 [notice] 17#17: start worker process 46
2021/07/11 20:26:31 [notice] 17#17: start worker process 47
2021/07/11 20:26:31 [notice] 17#17: start worker process 48
2021/07/11 20:26:31 [notice] 17#17: start worker process 49
2021/07/11 20:26:31 [notice] 17#17: start worker process 50
2021/07/11 20:26:31 [notice] 17#17: start worker process 51
2021/07/11 20:26:31 [notice] 17#17: start worker process 52
2021/07/11 20:26:31 [notice] 17#17: start worker process 53
2021/07/11 20:26:31 [notice] 17#17: start worker process 54
2021/07/11 20:26:31 [notice] 17#17: start worker process 55
2021/07/11 20:26:31 [notice] 17#17: start worker process 56
2021/07/11 20:26:31 [notice] 18#18: gracefully shutting down
2021/07/11 20:26:31 [notice] 19#19: gracefully shutting down
2021/07/11 20:26:31 [notice] 20#20: gracefully shutting down
2021/07/11 20:26:31 [notice] 21#21: gracefully shutting down
2021/07/11 20:26:31 [notice] 22#22: gracefully shutting down
2021/07/11 20:26:31 [notice] 20#20: exiting
2021/07/11 20:26:31 [notice] 19#19: exiting
2021/07/11 20:26:31 [notice] 18#18: exiting
2021/07/11 20:26:31 [notice] 23#23: gracefully shutting down
2021/07/11 20:26:31 [notice] 21#21: exiting
2021/07/11 20:26:31 [notice] 22#22: exiting
2021/07/11 20:26:31 [notice] 24#24: gracefully shutting down
2021/07/11 20:26:31 [notice] 23#23: exiting
2021/07/11 20:26:31 [notice] 24#24: exiting
2021/07/11 20:26:31 [notice] 25#25: gracefully shutting down
2021/07/11 20:26:31 [notice] 26#26: gracefully shutting down
2021/07/11 20:26:31 [notice] 27#27: gracefully shutting down
2021/07/11 20:26:31 [notice] 31#31: gracefully shutting down
2021/07/11 20:26:31 [notice] 25#25: exiting
2021/07/11 20:26:31 [notice] 26#26: exiting
2021/07/11 20:26:31 [notice] 30#30: gracefully shutting down
2021/07/11 20:26:31 [notice] 27#27: exiting
2021/07/11 20:26:31 [notice] 31#31: exiting
2021/07/11 20:26:31 [notice] 29#29: gracefully shutting down
2021/07/11 20:26:31 [notice] 30#30: exiting
2021/07/11 20:26:31 [notice] 29#29: exiting
2021/07/11 20:26:31 [notice] 18#18: exit
2021/07/11 20:26:31 [notice] 22#22: exit
2021/07/11 20:26:31 [notice] 24#24: exit
2021/07/11 20:26:31 [notice] 19#19: exit
2021/07/11 20:26:31 [notice] 23#23: exit
2021/07/11 20:26:31 [notice] 21#21: exit
2021/07/11 20:26:31 [notice] 25#25: exit
2021/07/11 20:26:31 [notice] 27#27: exit
2021/07/11 20:26:31 [notice] 31#31: exit
2021/07/11 20:26:31 [notice] 26#26: exit
2021/07/11 20:26:31 [notice] 29#29: exit
2021/07/11 20:26:31 [notice] 30#30: exit
2021/07/11 20:26:31 [notice] 32#32: gracefully shutting down
2021/07/11 20:26:31 [notice] 33#33: gracefully shutting down
2021/07/11 20:26:31 [notice] 32#32: exiting
2021/07/11 20:26:31 [notice] 20#20: exit
2021/07/11 20:26:31 [notice] 33#33: exiting
2021/07/11 20:26:31 [notice] 34#34: gracefully shutting down
2021/07/11 20:26:31 [notice] 34#34: exiting
2021/07/11 20:26:31 [notice] 33#33: exit
2021/07/11 20:26:31 [notice] 34#34: exit
2021/07/11 20:26:31 [notice] 32#32: exit
W0711 20:26:31.852527       1 controller.go:2157] Error retrieving endpoints for the service gateway: No endpoints for target port 8080 in service gateway
I0711 20:26:31.852690       1 event.go:282] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"openfaas", Name:"openfaas-ingress", UID:"ee1293b9-04b0-4cec-8f0a-48c99dfa93f1", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"770", FieldPath:""}): type: 'Normal' reason: 'AddedOrUpdated' Configuration for openfaas/openfaas-ingress was added or updated
2021/07/11 20:26:31 [notice] 17#17: signal 1 (SIGHUP) received from 58, reconfiguring
2021/07/11 20:26:31 [notice] 17#17: reconfiguring
2021/07/11 20:26:31 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:31 [notice] 17#17: start worker processes
2021/07/11 20:26:31 [notice] 17#17: start worker process 59
2021/07/11 20:26:31 [notice] 17#17: start worker process 60
2021/07/11 20:26:31 [notice] 17#17: start worker process 61
2021/07/11 20:26:31 [notice] 17#17: start worker process 62
2021/07/11 20:26:31 [notice] 17#17: start worker process 63
2021/07/11 20:26:31 [notice] 17#17: start worker process 64
2021/07/11 20:26:31 [notice] 17#17: start worker process 65
2021/07/11 20:26:31 [notice] 17#17: start worker process 66
2021/07/11 20:26:31 [notice] 17#17: start worker process 67
2021/07/11 20:26:31 [notice] 17#17: start worker process 68
2021/07/11 20:26:31 [notice] 17#17: start worker process 69
2021/07/11 20:26:31 [notice] 17#17: start worker process 70
2021/07/11 20:26:31 [notice] 17#17: start worker process 71
2021/07/11 20:26:31 [notice] 17#17: start worker process 72
2021/07/11 20:26:31 [notice] 17#17: start worker process 73
2021/07/11 20:26:31 [notice] 17#17: start worker process 74
2021/07/11 20:26:31 [notice] 41#41: gracefully shutting down
2021/07/11 20:26:31 [notice] 42#42: gracefully shutting down
2021/07/11 20:26:31 [notice] 43#43: gracefully shutting down
2021/07/11 20:26:31 [notice] 42#42: exiting
2021/07/11 20:26:31 [notice] 43#43: exiting
2021/07/11 20:26:31 [notice] 44#44: gracefully shutting down
2021/07/11 20:26:31 [notice] 45#45: gracefully shutting down
2021/07/11 20:26:31 [notice] 41#41: exiting
2021/07/11 20:26:31 [notice] 44#44: exiting
2021/07/11 20:26:31 [notice] 46#46: gracefully shutting down
2021/07/11 20:26:31 [notice] 45#45: exiting
2021/07/11 20:26:31 [notice] 46#46: exiting
2021/07/11 20:26:31 [notice] 47#47: gracefully shutting down
2021/07/11 20:26:31 [notice] 47#47: exiting
2021/07/11 20:26:31 [notice] 48#48: gracefully shutting down
2021/07/11 20:26:31 [notice] 49#49: gracefully shutting down
2021/07/11 20:26:31 [notice] 50#50: gracefully shutting down
2021/07/11 20:26:31 [notice] 48#48: exiting
2021/07/11 20:26:31 [notice] 49#49: exiting
2021/07/11 20:26:31 [notice] 51#51: gracefully shutting down
2021/07/11 20:26:31 [notice] 43#43: exit
2021/07/11 20:26:31 [notice] 42#42: exit
2021/07/11 20:26:31 [notice] 46#46: exit
2021/07/11 20:26:31 [notice] 53#53: gracefully shutting down
2021/07/11 20:26:31 [notice] 44#44: exit
2021/07/11 20:26:31 [notice] 56#56: gracefully shutting down
2021/07/11 20:26:31 [notice] 55#55: gracefully shutting down
2021/07/11 20:26:31 [notice] 50#50: exiting
2021/07/11 20:26:31 [notice] 53#53: exiting
2021/07/11 20:26:31 [notice] 56#56: exiting
2021/07/11 20:26:31 [notice] 55#55: exiting
2021/07/11 20:26:31 [notice] 51#51: exiting
2021/07/11 20:26:31 [notice] 54#54: gracefully shutting down
2021/07/11 20:26:31 [notice] 49#49: exit
2021/07/11 20:26:31 [notice] 47#47: exit
2021/07/11 20:26:31 [notice] 48#48: exit
2021/07/11 20:26:31 [notice] 52#52: gracefully shutting down
2021/07/11 20:26:31 [notice] 53#53: exit
2021/07/11 20:26:31 [notice] 50#50: exit
2021/07/11 20:26:31 [notice] 52#52: exiting
2021/07/11 20:26:31 [notice] 55#55: exit
2021/07/11 20:26:31 [notice] 51#51: exit
2021/07/11 20:26:31 [notice] 54#54: exiting
2021/07/11 20:26:31 [notice] 52#52: exit
2021/07/11 20:26:31 [notice] 54#54: exit
2021/07/11 20:26:31 [notice] 17#17: signal 17 (SIGCHLD) received from 25
2021/07/11 20:26:31 [notice] 17#17: worker process 19 exited with code 0
2021/07/11 20:26:31 [notice] 41#41: exit
2021/07/11 20:26:31 [notice] 17#17: worker process 21 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 22 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 24 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 25 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 26 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 29 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 33 exited with code 0
2021/07/11 20:26:31 [notice] 45#45: exit
2021/07/11 20:26:31 [notice] 56#56: exit
2021/07/11 20:26:31 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:31 [notice] 17#17: signal 17 (SIGCHLD) received from 29
2021/07/11 20:26:31 [notice] 17#17: worker process 30 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:31 [notice] 17#17: signal 17 (SIGCHLD) received from 32
2021/07/11 20:26:31 [notice] 17#17: worker process 18 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 20 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 23 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 27 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 31 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 32 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: worker process 34 exited with code 0
2021/07/11 20:26:31 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:31 [notice] 17#17: signal 17 (SIGCHLD) received from 18
I0711 20:26:31.985228       1 event.go:282] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"example-ingress-nginx-ingress", UID:"29cfebb2-1a8f-40d7-b082-88d8888ef530", APIVersion:"v1", ResourceVersion:"667", FieldPath:""}): type: 'Normal' reason: 'Updated' Configuration from ingress-nginx/example-ingress-nginx-ingress was updated
I0711 20:26:31.985259       1 event.go:282] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"openfaas", Name:"openfaas-ingress", UID:"ee1293b9-04b0-4cec-8f0a-48c99dfa93f1", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"770", FieldPath:""}): type: 'Normal' reason: 'AddedOrUpdated' Configuration for openfaas/openfaas-ingress was added or updated
W0711 20:26:31.990581       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0711 20:26:31.991200       1 controller.go:2157] Error retrieving endpoints for the service gateway: No endpoints for target port 8080 in service gateway
2021/07/11 20:26:31 [notice] 17#17: signal 1 (SIGHUP) received from 76, reconfiguring
2021/07/11 20:26:31 [notice] 17#17: reconfiguring
2021/07/11 20:26:31 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:31 [notice] 17#17: start worker processes
2021/07/11 20:26:31 [notice] 17#17: start worker process 77
2021/07/11 20:26:31 [notice] 17#17: start worker process 78
2021/07/11 20:26:31 [notice] 17#17: start worker process 79
2021/07/11 20:26:31 [notice] 17#17: start worker process 80
2021/07/11 20:26:31 [notice] 17#17: start worker process 81
2021/07/11 20:26:31 [notice] 17#17: start worker process 82
2021/07/11 20:26:31 [notice] 17#17: start worker process 83
2021/07/11 20:26:31 [notice] 17#17: start worker process 84
2021/07/11 20:26:31 [notice] 17#17: start worker process 85
2021/07/11 20:26:31 [notice] 17#17: start worker process 86
2021/07/11 20:26:31 [notice] 17#17: start worker process 87
2021/07/11 20:26:31 [notice] 17#17: start worker process 88
2021/07/11 20:26:31 [notice] 17#17: start worker process 89
2021/07/11 20:26:31 [notice] 17#17: start worker process 90
2021/07/11 20:26:31 [notice] 17#17: start worker process 91
2021/07/11 20:26:31 [notice] 17#17: start worker process 92
2021/07/11 20:26:32 [notice] 59#59: gracefully shutting down
2021/07/11 20:26:32 [notice] 60#60: gracefully shutting down
2021/07/11 20:26:32 [notice] 60#60: exiting
2021/07/11 20:26:32 [notice] 61#61: gracefully shutting down
2021/07/11 20:26:32 [notice] 59#59: exiting
2021/07/11 20:26:32 [notice] 62#62: gracefully shutting down
2021/07/11 20:26:32 [notice] 63#63: gracefully shutting down
2021/07/11 20:26:32 [notice] 62#62: exiting
2021/07/11 20:26:32 [notice] 61#61: exiting
2021/07/11 20:26:32 [notice] 64#64: gracefully shutting down
2021/07/11 20:26:32 [notice] 63#63: exiting
2021/07/11 20:26:32 [notice] 65#65: gracefully shutting down
2021/07/11 20:26:32 [notice] 64#64: exiting
2021/07/11 20:26:32 [notice] 65#65: exiting
2021/07/11 20:26:32 [notice] 67#67: gracefully shutting down
2021/07/11 20:26:32 [notice] 66#66: gracefully shutting down
2021/07/11 20:26:32 [notice] 67#67: exiting
2021/07/11 20:26:32 [notice] 68#68: gracefully shutting down
2021/07/11 20:26:32 [notice] 69#69: gracefully shutting down
2021/07/11 20:26:32 [notice] 66#66: exiting
2021/07/11 20:26:32 [notice] 71#71: gracefully shutting down
2021/07/11 20:26:32 [notice] 68#68: exiting
2021/07/11 20:26:32 [notice] 69#69: exiting
2021/07/11 20:26:32 [notice] 71#71: exiting
2021/07/11 20:26:32 [notice] 70#70: gracefully shutting down
2021/07/11 20:26:32 [notice] 59#59: exit
2021/07/11 20:26:32 [notice] 60#60: exit
2021/07/11 20:26:32 [notice] 64#64: exit
2021/07/11 20:26:32 [notice] 63#63: exit
2021/07/11 20:26:32 [notice] 65#65: exit
2021/07/11 20:26:32 [notice] 70#70: exiting
2021/07/11 20:26:32 [notice] 62#62: exit
2021/07/11 20:26:32 [notice] 61#61: exit
2021/07/11 20:26:32 [notice] 67#67: exit
2021/07/11 20:26:32 [notice] 66#66: exit
2021/07/11 20:26:32 [notice] 69#69: exit
2021/07/11 20:26:32 [notice] 68#68: exit
2021/07/11 20:26:32 [notice] 71#71: exit
2021/07/11 20:26:32 [notice] 70#70: exit
2021/07/11 20:26:32 [notice] 72#72: gracefully shutting down
2021/07/11 20:26:32 [notice] 73#73: gracefully shutting down
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 44
2021/07/11 20:26:32 [notice] 73#73: exiting
2021/07/11 20:26:32 [notice] 72#72: exiting
2021/07/11 20:26:32 [notice] 74#74: gracefully shutting down
2021/07/11 20:26:32 [notice] 17#17: worker process 41 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 42 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 44 exited with code 0
2021/07/11 20:26:32 [notice] 74#74: exiting
2021/07/11 20:26:32 [notice] 17#17: worker process 46 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 47 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 48 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 50 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 51 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 52 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 53 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 54 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 55 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 56 exited with code 0
2021/07/11 20:26:32 [notice] 74#74: exit
2021/07/11 20:26:32 [notice] 72#72: exit
2021/07/11 20:26:32 [notice] 73#73: exit
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 49
2021/07/11 20:26:32 [notice] 17#17: worker process 49 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 43
2021/07/11 20:26:32 [notice] 17#17: worker process 43 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
W0711 20:26:32.128055       1 warnings.go:70] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0711 20:26:32.128234       1 controller.go:2157] Error retrieving endpoints for the service gateway: No endpoints for target port 8080 in service gateway
2021/07/11 20:26:32 [notice] 17#17: signal 1 (SIGHUP) received from 94, reconfiguring
2021/07/11 20:26:32 [notice] 17#17: reconfiguring
2021/07/11 20:26:32 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:32 [notice] 17#17: start worker processes
2021/07/11 20:26:32 [notice] 17#17: start worker process 95
2021/07/11 20:26:32 [notice] 17#17: start worker process 96
2021/07/11 20:26:32 [notice] 17#17: start worker process 97
2021/07/11 20:26:32 [notice] 17#17: start worker process 98
2021/07/11 20:26:32 [notice] 17#17: start worker process 99
2021/07/11 20:26:32 [notice] 17#17: start worker process 100
2021/07/11 20:26:32 [notice] 17#17: start worker process 101
2021/07/11 20:26:32 [notice] 17#17: start worker process 102
2021/07/11 20:26:32 [notice] 17#17: start worker process 103
2021/07/11 20:26:32 [notice] 17#17: start worker process 104
2021/07/11 20:26:32 [notice] 17#17: start worker process 105
2021/07/11 20:26:32 [notice] 17#17: start worker process 106
2021/07/11 20:26:32 [notice] 17#17: start worker process 107
2021/07/11 20:26:32 [notice] 17#17: start worker process 108
2021/07/11 20:26:32 [notice] 17#17: start worker process 109
2021/07/11 20:26:32 [notice] 17#17: start worker process 110
2021/07/11 20:26:32 [notice] 77#77: gracefully shutting down
2021/07/11 20:26:32 [notice] 78#78: gracefully shutting down
2021/07/11 20:26:32 [notice] 79#79: gracefully shutting down
2021/07/11 20:26:32 [notice] 78#78: exiting
2021/07/11 20:26:32 [notice] 79#79: exiting
2021/07/11 20:26:32 [notice] 77#77: exiting
2021/07/11 20:26:32 [notice] 80#80: gracefully shutting down
2021/07/11 20:26:32 [notice] 81#81: gracefully shutting down
2021/07/11 20:26:32 [notice] 82#82: gracefully shutting down
2021/07/11 20:26:32 [notice] 81#81: exiting
2021/07/11 20:26:32 [notice] 80#80: exiting
2021/07/11 20:26:32 [notice] 83#83: gracefully shutting down
2021/07/11 20:26:32 [notice] 82#82: exiting
2021/07/11 20:26:32 [notice] 83#83: exiting
2021/07/11 20:26:32 [notice] 84#84: gracefully shutting down
2021/07/11 20:26:32 [notice] 85#85: gracefully shutting down
2021/07/11 20:26:32 [notice] 84#84: exiting
2021/07/11 20:26:32 [notice] 88#88: gracefully shutting down
2021/07/11 20:26:32 [notice] 85#85: exiting
2021/07/11 20:26:32 [notice] 87#87: gracefully shutting down
2021/07/11 20:26:32 [notice] 88#88: exiting
2021/07/11 20:26:32 [notice] 86#86: gracefully shutting down
2021/07/11 20:26:32 [notice] 87#87: exiting
2021/07/11 20:26:32 [notice] 79#79: exit
2021/07/11 20:26:32 [notice] 78#78: exit
2021/07/11 20:26:32 [notice] 86#86: exiting
2021/07/11 20:26:32 [notice] 82#82: exit
2021/07/11 20:26:32 [notice] 83#83: exit
2021/07/11 20:26:32 [notice] 77#77: exit
2021/07/11 20:26:32 [notice] 80#80: exit
2021/07/11 20:26:32 [notice] 81#81: exit
2021/07/11 20:26:32 [notice] 84#84: exit
2021/07/11 20:26:32 [notice] 85#85: exit
2021/07/11 20:26:32 [notice] 87#87: exit
2021/07/11 20:26:32 [notice] 88#88: exit
2021/07/11 20:26:32 [notice] 86#86: exit
2021/07/11 20:26:32 [notice] 89#89: gracefully shutting down
2021/07/11 20:26:32 [notice] 90#90: gracefully shutting down
2021/07/11 20:26:32 [notice] 90#90: exiting
2021/07/11 20:26:32 [notice] 89#89: exiting
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 45
2021/07/11 20:26:32 [notice] 91#91: gracefully shutting down
2021/07/11 20:26:32 [notice] 92#92: gracefully shutting down
2021/07/11 20:26:32 [notice] 91#91: exiting
2021/07/11 20:26:32 [notice] 17#17: worker process 45 exited with code 0
2021/07/11 20:26:32 [notice] 92#92: exiting
2021/07/11 20:26:32 [notice] 17#17: worker process 66 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 67 exited with code 0
2021/07/11 20:26:32 [notice] 90#90: exit
2021/07/11 20:26:32 [notice] 89#89: exit
2021/07/11 20:26:32 [notice] 92#92: exit
2021/07/11 20:26:32 [notice] 91#91: exit
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 59
2021/07/11 20:26:32 [notice] 17#17: worker process 59 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 60 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 61 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 62 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 68 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 69 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 70 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 71 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 73 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 74 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 70
I0711 20:26:32.260951       1 event.go:282] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"openfaas", Name:"openfaas-ingress", UID:"ee1293b9-04b0-4cec-8f0a-48c99dfa93f1", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"770", FieldPath:""}): type: 'Normal' reason: 'AddedOrUpdated' Configuration for openfaas/openfaas-ingress was added or updated
2021/07/11 20:26:32 [notice] 17#17: signal 1 (SIGHUP) received from 112, reconfiguring
2021/07/11 20:26:32 [notice] 17#17: reconfiguring
2021/07/11 20:26:32 [notice] 17#17: using the "epoll" event method
2021/07/11 20:26:32 [notice] 17#17: start worker processes
2021/07/11 20:26:32 [notice] 17#17: start worker process 113
2021/07/11 20:26:32 [notice] 17#17: start worker process 114
2021/07/11 20:26:32 [notice] 17#17: start worker process 115
2021/07/11 20:26:32 [notice] 17#17: start worker process 116
2021/07/11 20:26:32 [notice] 17#17: start worker process 117
2021/07/11 20:26:32 [notice] 17#17: start worker process 118
2021/07/11 20:26:32 [notice] 17#17: start worker process 119
2021/07/11 20:26:32 [notice] 17#17: start worker process 120
2021/07/11 20:26:32 [notice] 17#17: start worker process 121
2021/07/11 20:26:32 [notice] 17#17: start worker process 122
2021/07/11 20:26:32 [notice] 17#17: start worker process 123
2021/07/11 20:26:32 [notice] 17#17: start worker process 124
2021/07/11 20:26:32 [notice] 17#17: start worker process 125
2021/07/11 20:26:32 [notice] 17#17: start worker process 126
2021/07/11 20:26:32 [notice] 17#17: start worker process 127
2021/07/11 20:26:32 [notice] 17#17: start worker process 128
2021/07/11 20:26:32 [notice] 95#95: gracefully shutting down
2021/07/11 20:26:32 [notice] 96#96: gracefully shutting down
2021/07/11 20:26:32 [notice] 97#97: gracefully shutting down
2021/07/11 20:26:32 [notice] 96#96: exiting
2021/07/11 20:26:32 [notice] 97#97: exiting
2021/07/11 20:26:32 [notice] 98#98: gracefully shutting down
2021/07/11 20:26:32 [notice] 98#98: exiting
2021/07/11 20:26:32 [notice] 99#99: gracefully shutting down
2021/07/11 20:26:32 [notice] 95#95: exiting
2021/07/11 20:26:32 [notice] 99#99: exiting
2021/07/11 20:26:32 [notice] 100#100: gracefully shutting down
2021/07/11 20:26:32 [notice] 100#100: exiting
2021/07/11 20:26:32 [notice] 101#101: gracefully shutting down
2021/07/11 20:26:32 [notice] 102#102: gracefully shutting down
2021/07/11 20:26:32 [notice] 102#102: exiting
2021/07/11 20:26:32 [notice] 101#101: exiting
2021/07/11 20:26:32 [notice] 103#103: gracefully shutting down
2021/07/11 20:26:32 [notice] 104#104: gracefully shutting down
2021/07/11 20:26:32 [notice] 106#106: gracefully shutting down
2021/07/11 20:26:32 [notice] 105#105: gracefully shutting down
2021/07/11 20:26:32 [notice] 104#104: exiting
2021/07/11 20:26:32 [notice] 103#103: exiting
2021/07/11 20:26:32 [notice] 106#106: exiting
2021/07/11 20:26:32 [notice] 105#105: exiting
2021/07/11 20:26:32 [notice] 95#95: exit
2021/07/11 20:26:32 [notice] 97#97: exit
2021/07/11 20:26:32 [notice] 99#99: exit
2021/07/11 20:26:32 [notice] 96#96: exit
2021/07/11 20:26:32 [notice] 98#98: exit
2021/07/11 20:26:32 [notice] 100#100: exit
2021/07/11 20:26:32 [notice] 102#102: exit
2021/07/11 20:26:32 [notice] 101#101: exit
2021/07/11 20:26:32 [notice] 103#103: exit
2021/07/11 20:26:32 [notice] 105#105: exit
2021/07/11 20:26:32 [notice] 106#106: exit
2021/07/11 20:26:32 [notice] 104#104: exit
2021/07/11 20:26:32 [notice] 107#107: gracefully shutting down
2021/07/11 20:26:32 [notice] 108#108: gracefully shutting down
2021/07/11 20:26:32 [notice] 107#107: exiting
2021/07/11 20:26:32 [notice] 108#108: exiting
2021/07/11 20:26:32 [notice] 109#109: gracefully shutting down
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 65
2021/07/11 20:26:32 [notice] 109#109: exiting
2021/07/11 20:26:32 [notice] 110#110: gracefully shutting down
2021/07/11 20:26:32 [notice] 17#17: worker process 63 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 64 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 65 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 72 exited with code 0
2021/07/11 20:26:32 [notice] 110#110: exiting
2021/07/11 20:26:32 [notice] 17#17: worker process 85 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 88 exited with code 0
2021/07/11 20:26:32 [notice] 107#107: exit
2021/07/11 20:26:32 [notice] 108#108: exit
2021/07/11 20:26:32 [notice] 110#110: exit
2021/07/11 20:26:32 [notice] 109#109: exit
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
W0711 20:26:32.393543       1 controller.go:3048] Using the DEPRECATED annotation 'kubernetes.io/ingress.class'. The 'ingressClassName' field will be ignored.
I0711 20:26:32.393590       1 event.go:282] Event(v1.ObjectReference{Kind:"Secret", Namespace:"ingress-nginx", Name:"example-ingress-nginx-ingress-default-server-tls", UID:"bed2a2db-0afb-45e4-8b58-a78fbb4b3615", APIVersion:"v1", ResourceVersion:"664", FieldPath:""}): type: 'Normal' reason: 'Updated' the special Secret ingress-nginx/example-ingress-nginx-ingress-default-server-tls was updated
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 77
2021/07/11 20:26:32 [notice] 17#17: worker process 77 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 78 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 80 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 83 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 84 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 86 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 87 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 89 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 90 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 83
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 92
2021/07/11 20:26:32 [notice] 17#17: worker process 79 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 81 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 91 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 92 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 81
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 82
2021/07/11 20:26:32 [notice] 17#17: worker process 82 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 104
2021/07/11 20:26:32 [notice] 17#17: worker process 98 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 104 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 103
2021/07/11 20:26:32 [notice] 17#17: worker process 96 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 99 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 100 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 102 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 103 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 105 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 107 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 108 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 102
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 101
2021/07/11 20:26:32 [notice] 17#17: worker process 97 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 101 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: worker process 109 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 95
2021/07/11 20:26:32 [notice] 17#17: worker process 95 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 106
2021/07/11 20:26:32 [notice] 17#17: worker process 106 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:26:32 [notice] 17#17: signal 17 (SIGCHLD) received from 110
2021/07/11 20:26:32 [notice] 17#17: worker process 110 exited with code 0
2021/07/11 20:26:32 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:12 [notice] 17#17: signal 1 (SIGHUP) received from 130, reconfiguring
2021/07/11 20:27:12 [notice] 17#17: reconfiguring
2021/07/11 20:27:12 [notice] 17#17: using the "epoll" event method
2021/07/11 20:27:12 [notice] 17#17: start worker processes
2021/07/11 20:27:12 [notice] 17#17: start worker process 131
2021/07/11 20:27:12 [notice] 17#17: start worker process 132
2021/07/11 20:27:12 [notice] 17#17: start worker process 133
2021/07/11 20:27:12 [notice] 17#17: start worker process 134
2021/07/11 20:27:12 [notice] 17#17: start worker process 135
2021/07/11 20:27:12 [notice] 17#17: start worker process 136
2021/07/11 20:27:12 [notice] 17#17: start worker process 137
2021/07/11 20:27:12 [notice] 17#17: start worker process 138
2021/07/11 20:27:12 [notice] 17#17: start worker process 139
2021/07/11 20:27:12 [notice] 17#17: start worker process 140
2021/07/11 20:27:12 [notice] 17#17: start worker process 141
2021/07/11 20:27:12 [notice] 17#17: start worker process 142
2021/07/11 20:27:12 [notice] 17#17: start worker process 143
2021/07/11 20:27:12 [notice] 17#17: start worker process 144
2021/07/11 20:27:12 [notice] 17#17: start worker process 145
2021/07/11 20:27:12 [notice] 17#17: start worker process 146
2021/07/11 20:27:13 [notice] 113#113: gracefully shutting down
2021/07/11 20:27:13 [notice] 114#114: gracefully shutting down
2021/07/11 20:27:13 [notice] 114#114: exiting
2021/07/11 20:27:13 [notice] 113#113: exiting
2021/07/11 20:27:13 [notice] 116#116: gracefully shutting down
2021/07/11 20:27:13 [notice] 115#115: gracefully shutting down
2021/07/11 20:27:13 [notice] 117#117: gracefully shutting down
2021/07/11 20:27:13 [notice] 116#116: exiting
2021/07/11 20:27:13 [notice] 115#115: exiting
2021/07/11 20:27:13 [notice] 118#118: gracefully shutting down
2021/07/11 20:27:13 [notice] 119#119: gracefully shutting down
2021/07/11 20:27:13 [notice] 117#117: exiting
2021/07/11 20:27:13 [notice] 118#118: exiting
2021/07/11 20:27:13 [notice] 120#120: gracefully shutting down
2021/07/11 20:27:13 [notice] 121#121: gracefully shutting down
2021/07/11 20:27:13 [notice] 119#119: exiting
2021/07/11 20:27:13 [notice] 122#122: gracefully shutting down
2021/07/11 20:27:13 [notice] 123#123: gracefully shutting down
2021/07/11 20:27:13 [notice] 120#120: exiting
2021/07/11 20:27:13 [notice] 122#122: exiting
2021/07/11 20:27:13 [notice] 121#121: exiting
2021/07/11 20:27:13 [notice] 125#125: gracefully shutting down
2021/07/11 20:27:13 [notice] 124#124: gracefully shutting down
2021/07/11 20:27:13 [notice] 123#123: exiting
2021/07/11 20:27:13 [notice] 124#124: exiting
2021/07/11 20:27:13 [notice] 125#125: exiting
2021/07/11 20:27:13 [notice] 118#118: exit
2021/07/11 20:27:13 [notice] 117#117: exit
2021/07/11 20:27:13 [notice] 113#113: exit
2021/07/11 20:27:13 [notice] 116#116: exit
2021/07/11 20:27:13 [notice] 115#115: exit
2021/07/11 20:27:13 [notice] 120#120: exit
2021/07/11 20:27:13 [notice] 119#119: exit
2021/07/11 20:27:13 [notice] 123#123: exit
2021/07/11 20:27:13 [notice] 121#121: exit
2021/07/11 20:27:13 [notice] 122#122: exit
2021/07/11 20:27:13 [notice] 125#125: exit
2021/07/11 20:27:13 [notice] 124#124: exit
2021/07/11 20:27:13 [notice] 114#114: exit
2021/07/11 20:27:13 [notice] 126#126: gracefully shutting down
2021/07/11 20:27:13 [notice] 127#127: gracefully shutting down
2021/07/11 20:27:13 [notice] 126#126: exiting
2021/07/11 20:27:13 [notice] 127#127: exiting
2021/07/11 20:27:13 [notice] 128#128: gracefully shutting down
2021/07/11 20:27:13 [notice] 128#128: exiting
2021/07/11 20:27:13 [notice] 127#127: exit
2021/07/11 20:27:13 [notice] 126#126: exit
2021/07/11 20:27:13 [notice] 128#128: exit
2021/07/11 20:27:13 [notice] 17#17: signal 17 (SIGCHLD) received from 115
2021/07/11 20:27:13 [notice] 17#17: worker process 114 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 115 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 116 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 120 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 121 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 122 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 123 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 125 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 126 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 127 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 128 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:13 [notice] 17#17: signal 17 (SIGCHLD) received from 125
2021/07/11 20:27:13 [notice] 17#17: signal 17 (SIGCHLD) received from 113
2021/07/11 20:27:13 [notice] 17#17: worker process 113 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 117 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: worker process 118 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:13 [notice] 17#17: signal 17 (SIGCHLD) received from 124
2021/07/11 20:27:13 [notice] 17#17: worker process 124 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:13 [notice] 17#17: signal 17 (SIGCHLD) received from 119
2021/07/11 20:27:13 [notice] 17#17: worker process 119 exited with code 0
2021/07/11 20:27:13 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:14 [notice] 17#17: signal 1 (SIGHUP) received from 148, reconfiguring
2021/07/11 20:27:14 [notice] 17#17: reconfiguring
2021/07/11 20:27:14 [notice] 17#17: using the "epoll" event method
2021/07/11 20:27:14 [notice] 17#17: start worker processes
2021/07/11 20:27:14 [notice] 17#17: start worker process 149
2021/07/11 20:27:14 [notice] 17#17: start worker process 150
2021/07/11 20:27:14 [notice] 17#17: start worker process 151
2021/07/11 20:27:14 [notice] 17#17: start worker process 152
2021/07/11 20:27:14 [notice] 17#17: start worker process 153
2021/07/11 20:27:14 [notice] 17#17: start worker process 154
2021/07/11 20:27:14 [notice] 17#17: start worker process 155
2021/07/11 20:27:14 [notice] 17#17: start worker process 156
2021/07/11 20:27:14 [notice] 17#17: start worker process 157
2021/07/11 20:27:14 [notice] 17#17: start worker process 158
2021/07/11 20:27:14 [notice] 17#17: start worker process 159
2021/07/11 20:27:14 [notice] 17#17: start worker process 160
2021/07/11 20:27:14 [notice] 17#17: start worker process 161
2021/07/11 20:27:14 [notice] 17#17: start worker process 162
2021/07/11 20:27:14 [notice] 17#17: start worker process 163
2021/07/11 20:27:14 [notice] 17#17: start worker process 164
2021/07/11 20:27:15 [notice] 131#131: gracefully shutting down
2021/07/11 20:27:15 [notice] 132#132: gracefully shutting down
2021/07/11 20:27:15 [notice] 132#132: exiting
2021/07/11 20:27:15 [notice] 133#133: gracefully shutting down
2021/07/11 20:27:15 [notice] 134#134: gracefully shutting down
2021/07/11 20:27:15 [notice] 134#134: exiting
2021/07/11 20:27:15 [notice] 131#131: exiting
2021/07/11 20:27:15 [notice] 133#133: exiting
2021/07/11 20:27:15 [notice] 136#136: gracefully shutting down
2021/07/11 20:27:15 [notice] 136#136: exiting
2021/07/11 20:27:15 [notice] 137#137: gracefully shutting down
2021/07/11 20:27:15 [notice] 135#135: gracefully shutting down
2021/07/11 20:27:15 [notice] 135#135: exiting
2021/07/11 20:27:15 [notice] 137#137: exiting
2021/07/11 20:27:15 [notice] 138#138: gracefully shutting down
2021/07/11 20:27:15 [notice] 138#138: exiting
2021/07/11 20:27:15 [notice] 139#139: gracefully shutting down
2021/07/11 20:27:15 [notice] 143#143: gracefully shutting down
2021/07/11 20:27:15 [notice] 141#141: gracefully shutting down
2021/07/11 20:27:15 [notice] 143#143: exiting
2021/07/11 20:27:15 [notice] 140#140: gracefully shutting down
2021/07/11 20:27:15 [notice] 139#139: exiting
2021/07/11 20:27:15 [notice] 141#141: exiting
2021/07/11 20:27:15 [notice] 142#142: gracefully shutting down
2021/07/11 20:27:15 [notice] 140#140: exiting
2021/07/11 20:27:15 [notice] 136#136: exit
2021/07/11 20:27:15 [notice] 132#132: exit
2021/07/11 20:27:15 [notice] 131#131: exit
2021/07/11 20:27:15 [notice] 142#142: exiting
2021/07/11 20:27:15 [notice] 134#134: exit
2021/07/11 20:27:15 [notice] 133#133: exit
2021/07/11 20:27:15 [notice] 138#138: exit
2021/07/11 20:27:15 [notice] 137#137: exit
2021/07/11 20:27:15 [notice] 135#135: exit
2021/07/11 20:27:15 [notice] 143#143: exit
2021/07/11 20:27:15 [notice] 141#141: exit
2021/07/11 20:27:15 [notice] 139#139: exit
2021/07/11 20:27:15 [notice] 142#142: exit
2021/07/11 20:27:15 [notice] 140#140: exit
2021/07/11 20:27:15 [notice] 144#144: gracefully shutting down
2021/07/11 20:27:15 [notice] 145#145: gracefully shutting down
2021/07/11 20:27:15 [notice] 144#144: exiting
2021/07/11 20:27:15 [notice] 146#146: gracefully shutting down
2021/07/11 20:27:15 [notice] 145#145: exiting
2021/07/11 20:27:15 [notice] 146#146: exiting
2021/07/11 20:27:15 [notice] 144#144: exit
2021/07/11 20:27:15 [notice] 146#146: exit
2021/07/11 20:27:15 [notice] 145#145: exit
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 134
2021/07/11 20:27:15 [notice] 17#17: worker process 131 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 132 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 134 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 135 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 137 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 140 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 145 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 135
2021/07/11 20:27:15 [notice] 17#17: worker process 144 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 141
2021/07/11 20:27:15 [notice] 17#17: worker process 136 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 138 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 141 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 142 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: worker process 146 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 146
2021/07/11 20:27:15 [notice] 17#17: worker process 133 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 143
2021/07/11 20:27:15 [notice] 17#17: worker process 143 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:15 [notice] 17#17: signal 17 (SIGCHLD) received from 139
2021/07/11 20:27:15 [notice] 17#17: worker process 139 exited with code 0
2021/07/11 20:27:15 [notice] 17#17: signal 29 (SIGIO) received
<IP_ADDRESS> - admin [11/Jul/2021:20:27:22 +0000] "GET /system/functions HTTP/1.1" 200 2 "-" "Go-http-client/1.1" "-"
<IP_ADDRESS> - admin [11/Jul/2021:20:27:46 +0000] "PUT /system/functions HTTP/1.1" 404 91 "-" "Go-http-client/1.1" "-"
<IP_ADDRESS> - admin [11/Jul/2021:20:27:46 +0000] "POST /system/functions HTTP/1.1" 202 0 "-" "Go-http-client/1.1" "-"
W0711 20:27:48.249194       1 controller.go:3048] Using the DEPRECATED annotation 'kubernetes.io/ingress.class'.  The 'ingressClassName' field will be ignored.
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 152
2021/07/11 20:27:48 [notice] 17#17: worker process 152 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 154 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 157 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 161 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 163 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 154
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 149
2021/07/11 20:27:48 [notice] 17#17: worker process 149 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 158
2021/07/11 20:27:48 [notice] 17#17: worker process 150 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 156 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 158 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 160 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 162 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 151 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: worker process 164 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 164
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 153
2021/07/11 20:27:48 [notice] 17#17: worker process 153 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 155
2021/07/11 20:27:48 [notice] 17#17: worker process 155 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
2021/07/11 20:27:48 [notice] 17#17: signal 17 (SIGCHLD) received from 159
2021/07/11 20:27:48 [notice] 17#17: worker process 159 exited with code 0
2021/07/11 20:27:48 [notice] 17#17: signal 29 (SIGIO) received
<IP_ADDRESS> - - [11/Jul/2021:20:28:46 +0000] "GET /api/v1/test/ HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.19041.1023" "-"
2021/07/11 20:28:46 [error] 170#170: *16 "/etc/nginx/html/api/v1/test/index.html" is not found (2: No such file or directory), client: <IP_ADDRESS>, server: example.kube, request: "GET /api/v1/test/ HTTP/1.1", host: "example.kube"
<IP_ADDRESS> - - [11/Jul/2021:20:28:49 +0000] "GET /function/test-fn/ HTTP/1.1" 200 41 "-" "Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.19041.1023" "-"

@HighCrit thanks for trying it. Clearly there is some important difference between KinD and other clusters like GKE, or at least some important differences in the most recent nginx-ingress helm chart. I know i have used it with kind in the past, but not recently.
I think we can safely close this for now.

@LucasRoesler thank you for all the help!

Just wondered if @justincormack had time to comment here. It seems like the chart for ingress-nginx doesn't work as expected on Docker Desktop, but a static manifest does?


Dynamic versioning via dynver

Seems JFrog is having maintenance - Idk if it is related to the failure on downloading sbt
https://status.jfrog.io/


Add GitHub Actions Windows CI - Ruby 2.4 thru master/trunk.

Description

No CI testing is done using Ruby master/trunk.  Add a windows workflow file.

Ruby master/trunk is currently failing.  Added a test for one issue. See https://github.com/lsegal/yard/pull/1290.  If that pr is merged, Ruby master will pass.

Completed Tasks

[x] I have read the Contributing Guide.
[x] The pull request is complete (implemented / written).
[x] Git commits have been cleaned up (squash WIP / revert commits).
[x] I wrote tests and ran bundle exec rake locally (if code is attached to PR).

Coverage decreased (-0.03%) to 93.725% when pulling 815f365c172ab89a5b115738774987895bf42a0b on MSP-Greg:github-actions-void into 4b5c875c307ae029c27024bfe56a98c899f1685e on lsegal:master.

Thanks for this PR!


Added Boilercode to the list

Please add these to the list @Anil-matcha

Please add chatdox & habitloop in the list @Anil-matcha


Keyboard shortcuts fail after /, Esc in Firefox

In Firefox (but not Chrome), if you press / to open the search bar, then press Esc to close it, most other keyboard shortcuts (those not involving Ctrl, I think) stop working until a second Esc press or a mouse click.
For example, / Esc / opens the Firefox quick find bar instead of our search bar.

@zulipbot claim

@zulipbot  claim


Release Google.Cloud.WebSecurityScanner.V1 version 2.1.0

Changes in this release:
Bug fixes

Added fix to return a list of the endpoints that encountered errors during crawl, along with the specific error message when the starting URL returns Http errors (commit 241ecd9)
GoogleAccount is deprecated (commit 241ecd9)

New features

Added NO_STARTING_URL_FOUND_FOR_MANAGED_SCAN to ScanRunWarningTrace.Code (commit 241ecd9)

Documentation improvements

Publish Scan Run logging proto for documentation (commit 77e3503)

Created release for Google.Cloud.WebSecurityScanner.V1-2.1.0


Introduce sanity checks for IDs and fix overriding its type

Fixes #857 (and by the way fixes #1178), closes #1183 and closes #819.

To be honest, I don't know why we have the generatorOptions type at all. In the end, it does exactly the same as the field mapping but it just introduces complexity and mistakes along the way. I'm not sure about BC here, but IMO the best option would be to drop generatorOptions.type, always use type from the field mapping and setting it to id or custom_id depending on the generator strategy only if no type was given. As it is now, writing a generator that generates a MongoId still requires specifying a generatorOptions.type mapping because the field mapping of id will be overwritten (which, incidentally, needed a trip through the debugger to figure out why it wouldn't work when I first tried it without generatorOptions.type).
Either way we do this, we need to write some documentation about this feature.

I'm not sure about BC here, but IMO the best option would be to drop generatorOptions.type

Maybe trigger deprecation?

writing a generator that generates a MongoId

What is the point of such generator?

Either way we do this, we need to write some documentation about this feature.

I'll create a ticket for this later

What is the point of such generator?

The use case is a bit special: we needed predictable identifiers to trigger upserts but wanted to keep MongoId values. So we assigned a specific time identifier (the first 4 bytes of MongoId) and added a hash based on document settings. Weird, but it works ;)

@alcaeus I've commited a change we discussed on IRC :)

@malarzm Looks good. This way we ensure using MongoId with AUTO strategy but don't overly complicate the mapping. I've also created #1197 to track documentation changes.


V0.4.0

I am still working on v0.4.0, I opened this PR to just show the progress. Also, binaries of stream enrich and stream collector are placed in the repo for now because their new versions with NSQ support are not published yet. After publish them, binaries will be removed from repo.

Are you ready for a review yet @aldemirenes ?

I am not finished with the all the issues in the milestone yet, I will let you know when I am done.@alexanderdean

Cool - I am on holiday next week, please assign @jbeemster as a reviewer when you are ready!

@jbeemster  v0.4.0 is mostly complete, only thing left to do removing binaries of the Stream Enrich and Stream Collector  from the repo. This will be done after NSQ added versions of the Stream Enrich and Stream Collector is published.
Also, there are two problematic issues right know.First one is starting Kibana takes too much time. It changes 2 to 10 min. This related with server.basePath setting of the Kibana, more information for the reason of the problem can be found in here. However,  since kibana will be started only in reboot, I think this problem can be tolerated.
Second issue is Elasticsearch 5.x is very memory hungry. It causes some problems. For example, it is not starting in the 'vagrant up' and this problem requires starting "configure ansible role" manually after vagrant machine up and running. But this is problem does not occur in the provisioning of the AMI with Packer. Another problem with Elasticsearch 5.x is that when EC2 instance has less than 8 gb ram, it is not starting in the first time after creation of the Snowplow Mini instance from the AMI. And this problem requires rebooting the machine or SSHing to the machine and starting ES manually. But this problem does no occur when EC2 instance has 8gb or more ram. It seems that this problem is related with memory but I could not find the exact reason yet. I will continue investage and try to find a solution.

@aldemirenes on the ES issue you should be able to configure the amount of Java Heap to give it:

https://stackoverflow.com/questions/41120925/ubuntu-16-04-install-elasticsearch-5-x-failed-to-start/41354969

Its likely that the newer versions do need a lot more ram... didn't realise it was this much however!

If the new ES is that memory hungry, is this going to restrict our options to deploy Snowplow Mini (i.e. by increasing the cost of each Snowplow Mini instance)? Should we stick with the older version?

Thanks, would be good to understand the TCO impact of this ES change from @jbeemster in due course

If we need 8 or more GB of RAM for Snowplow Mini the TCO cost will double or quadruple.  So if we cannot get it running reliably on a t2.medium I think we need to keep it using the old version of Elasticsearch.

I create new branch for es and kibana are not upgraded. I created AMI for it in the eu-central-1 region of the Snowplow Engineering Sandbox. There is some problem while adding kibana index automatically in that version, therefore automatically created indexes need to be removed  in the beginning, indexes need to be added manually after removing them.This issue is not very big problem, it should be solved in a short time but I could not look at it yet. Other than that "es kibana not upgraded" version working just fine. "es kibana upgraded" version is still giving memory related errors in the t2.medium

I think let's strip out the ES upgrade altogether - @jbeemster ?

Hey @aldemirenes @alexanderdean - yep lets push that back for the moment - if it cannot run reliably then we do not want it!
Do keep that commit in a branch somewhere though so we can sample it as we will likely need to revisit this at some point in the future.

Any chance we could include the latest version of the scala stream collector in this release? It'd be good to get all the fixes and updates in so there's close parity between mini and R93.

Any chance we could include the latest version of the scala stream collector in this release?

0.4.0 will embed all the R95 Zeugma applications - R95 being needed because it introduces the NSQ support.

Makes sense - that's great news!

Can you cross-check against the milestone @BenFradet ? It feels like this git history versus the milestone are rather divergent.


Release 0.1.0 broke HMR

Hi @neighborhood999 and thank you for this plugin.
There is a small issue I encountered in release 0.1.0: after upgrading, HMR stopped working for me. I downgraded to 0.0.96 and it started working again.
I use Nuxt 1.4.0 in my project.
Thanks!

Hi @eidellev! Did you have try to reinstall node_modules?


Required php version raised to 7.3?

Directory Lister Version

3.7.2+
PHP Version

7.2.24 on centos 8
PHP Extensions

[PHP Modules]
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gd
gettext
hash
iconv
json
libxml
mbstring
openssl
pcntl
pcre
Phar
readline
Reflection
session
SimpleXML
sockets
SPL
standard
tokenizer
wddx
xml
xmlreader
xmlwriter
xsl
zlib
HTTP Server

nginx 1.18
Describe the bug

``Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.3.0".
Steps To Reproduce

unzip and place directory lister in webroot
try to navigate to url
Expected behavior

Directorylister loads normally
Additional context

Versions below 3.7.2 seems to work fine.

Fixed with v3.7.9


New RWD: lack of consistency with stylesheet type attribute

Describe the Issue
One challenge asked for the type attribute and one doesn't. Given the current best practice is to not include it for CSS I'd suggest removing it from "building a cafe menu - step-17".
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-basic-css-by-building-a-cafe-menu/step-17
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-the-css-box-model-by-building-a-rothko-painting/step-7

type
This attribute is used to define the type of the content linked to. The value of the attribute should be a MIME type such as text/html, text/css, and so on. The common use of this attribute is to define the type of stylesheet being referenced (such as text/css), but given that CSS is the only stylesheet language used on the web, not only is it possible to omit the type attribute, but is actually now recommended practice. It is also used on rel="preload" link types, to make sure the browser only downloads file types that it supports.

Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-the-css-box-model-by-building-a-rothko-painting/step-7
Your code
<link rel="stylesheet" href="styles.css" />

Expected behavior
Consistency between the two challenges and the likely removal of the type attribute.
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
Forum: https://forum.freecodecamp.org/t/step-7-rothko-painting/511284

I honestly had no idea it wasn't best practise anymore.
I agree, we should remove this from the instructions and the following steps' seed code.
However, we should still allow it in the tests (not require it) as it is technically valid HTML.


subnet tagging

I'm searching tagging for subnet, can you please confirm if it's documented here, either support or not support?

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

ID: 66769e1b-720b-f1b1-a5e3-ed5cb24cd233
Version Independent ID: b6272e61-58c1-3e2f-3e36-a9ee920c0915
Content: Tag support for resources - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/tag-support.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@RonnieQuan Thanks for your comment. We will review the issue and get back to you.

@RonnieQuan  AFAIK, subnet tagging isn't currently supported. The same feedback shown here was shared directly with the responsible Azure feature team. I recommend navigating to the above link and clicking the vote button to raise visibility and priority on this.

The update should get published this afternoon.
#please-close


Add configuration to turn off warn/log messages

Fix #721
Signed-off-by: Ricardo Leitão<EMAIL_ADDRESS>

@letz I know that it's been a long time since your pull request, but has #806 helped solved your issue? Wondering if that is enough for @alexreisner to close this PR. If there's anything more you require for logging, please let us know.

@TrangPham thanks for fixing this issue :+1:


[GSSoC'21] Index Page

@mksharma1 @yash982000 @ChetnaNSharma
I would like to make the index page using HTML CSS and javascript with awesome animations and user experience.
Can you assign this to me...I want to build the site from scratch.

@avinashjha1320 We are currently designing the screens. Will get back to you soon.
CC:- @ChetnaNSharma

@avinashjha1320 I have uploaded the design screens in the folder.
You have to make it similar in HTML, CSS, and JavaScript.
Making it responsive will be a great thing and we will mark your contribution with proper points and label if you are able to do it nicely.

Assign me, please. I would like to work on it.

Assign me, please. I would like to work on it.

@tripathi-abhishek You will get different tasks. Head over to open to ideas issue listed and bring in some creative ideas you want to work on. Meanwhile, we are preparing the exact requirements and featured to be needed for this application. You can come to us with your ideas in the issue thread of Open for Ideas.
CC:- @ChetnaNSharma

@tripathi-abhishek I am assigning you these screens if you can do it in a couple of next days let me know so that I can assign to you.
https://github.com/ChetnaNSharma/Alumni-Connect/blob/main/Alumni Connect Design Screens/Alumni Connect Home-Feed Page - 1.png
https://github.com/ChetnaNSharma/Alumni-Connect/blob/main/Alumni Connect Design Screens/Alumni Connect Home-Feed Page - 2.png

ok i will do my best!! Please assign.

ok i will do my best!! Please assign.

Done!!

Hey! @yash982000 , I would like to contribute to this project, Please assign me any page if it's not been assigned to anyone.

ok i will do my best!! Please assign.

@tripathi-abhishek Any updates??

Hey! @yash982000 , I would like to contribute to this project, Please assign me any page if it's not been assigned to anyone.

@Shagufta08 There are some designs to be done yet. Please open a new issue and I will assign you there.

ok I will do my best!! Please assign.

@tripathi-abhishek Any updates??

yeah. I'm building the pages as requested. The design is kinda vague. I have worked on Figma so I had this habit of getting precise details. BTW I'm using HTML, CSS for now. So, In the future, if u need ejs, gatsby, or such for full website development it would just need some additional modules/components.

@tripathi-abhishek  They are actually not vague. It is made in Figma only. But, this is a screenshot so. No worries, do it in HTML and CSS only and connect it via Javascript if needed.

hey! @yash982000, I would like to contribute to this project ,please assign me the designing task ,if not assigned to anyone

@samgarg7009 What designs are you talking about?
We do have that ready.

@yash982000 If would like to do the frontend work .If you have any designs ready can you assign me?

@yash982000 I would like to work on this issue as part of GSSOC'21. Please assign it to me,

@CMELAKKIA @Mukta-Sawant There are certain designs in the design folder. You can check from the open and closed Pr's and issues and work on those which are left.

I would like to contribute to this issue as a GSSOC'21 participant. Please assign it to me, hoping for a positive reply soon.

@ShrutiKhatri826 Can you open a new issue?
You can contribute with your ideas or look for the remaining work from the repo
:)


Erro Fatal error. Include ZCLE_EXCEL_WORKSHEET =============CCAU should have been created previously

When I'm importing the repository this error below happen
Fatal error. Include ZCLE_EXCEL_WORKSHEET =============CCAU should have been created previously

@ivanfemia I don't know what's rappening, could you help me?

see https://github.com/ivanfemia/abap2xlsx/issues/517


Add support for Metal VRF on Metal Billed Interconnections

Community Note

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.

Description
The following new (beta) capabilities should be surfaced in the provider:

VRF on Metal Billed Fabric VCs
Setting of VRF Static Route
Support for BGP Dynamic Neighbors (available on VRF Metal Gateways)
(non-VRF) Adding a static/elastic IP address to a Gateway

Identified changes (there may be others):

equinix_metal_connection: should support vrfs as a mutually exclusive option to vlans
[TODO]

Packngo will not be getting these new capabilities so metal-go (#353) (which already includes support for these API endpoints, parameters, and attributes) will need to be used.

New or Affected Resource(s)
The following resources and datasources should be updated (including their documentation and expamples) to reflect the new capabilities:
•	Connection (Example Use-Cases): https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_connection
•	Virtual Circuit: https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_virtual_circuit
•	VRF (Example Use-Cases):
https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_vrf
•	IP Reservation (VRF Example Use-Cases):
https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_reserved_ip_block#type
•	Metal + Fabric Guide: https://registry.terraform.io/providers/equinix/equinix/latest/docs/guides/equinix_fabric_cloud_providers
•	Metal VRF Module: https://github.com/equinix-labs/terraform-equinix-metal-vrf
Potential Terraform Configuration

resource "equinix_metal_connection" "example" {
    name            = "tf-port-to-metal-legacy"
    project_id      = local.my_project_id
    metro           = "SV"
    redundancy      = "redundant"
    type            = "shared"
    contact_email   =<EMAIL_ADDRESS>
    # Similar to the VLANs feature which is for Shared Interconnection only, expose a VRF parameter
    # vlans = []
    vrf_id = equinix_metal_vrf.example.id
}

resource "equinix_metal_vrf" "example" { ... }

References

https://deploy.equinix.com/developers/docs/metal/interconnections/vrf/
https://feedback.equinixmetal.com/network/p/virtual-routing-forwarding-vrf-for-overlapping-ip-space-on-dedicated-and-shared
https://feedback.equinixmetal.com/network/p/bgp-dynamic-neighbor-feature-parity-for-metal-gateways
https://feedback.equinixmetal.com/network/p/metal-gateway-elastic-ip
https://github.com/equinix/terraform-provider-equinix/issues/309 may have relevant changes identified

Docs link for adding an Elastic (Reserved) IP address to a Metal Gateway - https://deploy.equinix.com/developers/docs/metal/layer2-networking/metal-gateway/#adding-an-ip-address-to-a-metal-gateway

Closed by #607