About the hardware setting.

Thank you so much for open sourcing such great code, it is very helpful. But I have some questions about the hardware.

How much memory did you use? According to the paper I know you used only one NVIDIA 3090 (actually I'm not sure), but I didn't find a description of memory.

INN is very consume memory, and I find you used the resolution of 448×256 with batch size is 16 to train in this paper, how about more huge resolution video like 480P or 720P? and the memory is enough? or does fewer INN blocks have an effect on the neural network's ability to fit?(I find you used 4 INN, if I feed 1080P video to the network, the memory consume is very costly).

Thank you again and look forward to your reply.

Hi Mesks,

In our training, we only use one NVIDIA 3090 GPU. I remember that it takes about over 10 GB GPU memory in the training.

Perhaps the memory-consuming problem in INN is caused by the dense blocks inside. As you can see in our paper, in training we crop the original image on Vimeo90K training dataset to 144144 for generating the ground truth. In testing, we mainly use 3 datasets, including Vid4, Vimeo90K testing dataset and UDM10. The resolution of UDM10 is 1272720, which is about 720P. We also find that when the resolution is relatively high, the GPU memory is not enough. The exact maximum resolution is not measured. One solution is to divide the image into two or more parts for the separate processing. Or you can replace the dense blocks in INN with residual blocks. I think you can also use less invertible blocks.

Hi Mesks,

In our training, we only use one NVIDIA 3090 GPU. I remember that it takes about over 10 GB GPU memory in the training.

Perhaps the memory-consuming problem in INN is caused by the dense blocks inside. As you can see in our paper, in training we crop the original image on Vimeo90K training dataset to 144×144 for generating the ground truth. In testing, we mainly use 3 datasets, including Vid4, Vimeo90K testing dataset and UDM10. The resolution of UDM10 is 1272×720, which is about 720P. We also find that when the resolution is relatively high, the GPU memory is not enough. The exact maximum resolution is not measured. One solution is to divide the image into two or more parts for the separate processing. Or you can replace the dense blocks in INN with residual blocks. I think you can also use less invertible blocks.

Hi Mesks,

In our training, we only use one NVIDIA 3090 GPU. I remember that it takes about over 10 GB GPU memory in the training.

Perhaps the memory-consuming problem in INN is caused by the dense blocks inside. As you can see in our paper, in training we crop the original image on Vimeo90K training dataset to 144×144 for generating the ground truth. In testing, we mainly use 3 datasets, including Vid4, Vimeo90K testing dataset and UDM10. The resolution of UDM10 is 1272×720, which is about 720P. We also find that when the resolution is relatively high, the GPU memory is not enough. The exact maximum resolution is not measured. One solution is to divide the image into two or more parts for the separate processing. Or you can replace the dense blocks in INN with residual blocks. I think you can also use less invertible blocks.

Hi Mesks,

In our training, we only use one NVIDIA 3090 GPU. I remember that it takes about over 10 GB GPU memory in the training.

Perhaps the memory-consuming problem in INN is caused by the dense blocks inside. As you can see in our paper, in training we crop the original image on Vimeo90K training dataset to 144144 for generating the ground truth. In testing, we mainly use 3 datasets, including Vid4, Vimeo90K testing dataset and UDM10. The resolution of UDM10 is 1272720, which is about 720P. We also find that when the resolution is relatively high, the GPU memory is not enough. The exact maximum resolution is not measured. One solution is to divide the image into two or more parts for the separate processing. Or you can replace the dense blocks in INN with residual blocks. I think you can also use less invertible blocks.

Hi Mesks,

In our training, we only use one NVIDIA 3090 GPU. I remember that it takes about over 10 GB GPU memory in the training.

Perhaps the memory-consuming problem in INN is caused by the dense blocks inside. As you can see in our paper, in training we crop the original image on Vimeo90K training dataset to 144×144 for generating the ground truth. In testing, we mainly use 3 datasets, including Vid4, Vimeo90K testing dataset and UDM10. The resolution of UDM10 is 1272×720, which is about 720P. We also find that when the resolution is relatively high, the GPU memory is not enough. The exact maximum resolution is not measured. One solution is to divide the image into two or more parts for the separate processing. Or you can replace the dense blocks in INN with residual blocks. I think you can also use less invertible blocks.

Thank you very much for your valuable suggestions. I apologize for the delayed response. I wanted to take some time to summarize my new questions so I could ask them all at once, in hopes of avoiding inefficient communication. However, I realize the gap between my messages may have become a bit too long.
The issue I’m encountering concerns the PredictiveModuleMIMO2 module. Specifically, during repeated calls to this module, I’ve noticed that the network fails to converge. In my work, I’ve designed a module similar to your PredictiveModuleMIMO2 and followed your approach by reusing a module. However, it seems that this reuse is causing the network to diverge.
I noticed that in your implementation of PredictiveModuleMIMO2 (with the variable name pm2), you create new tensors by cloning the output of PredictiveModuleMIMO2 and using the cloned output as one of the inputs for the next call (i.e., the output of call A is cloned and used as input to call B). I’m wondering if this might prevent the gradient from flowing back from B to A. Does this mean that within each GOP, the training for each non-reference frame is independent, and the gradient does not need to propagate from B to A?
If my question isn’t entirely clear, I’m essentially asking whether the extensive use of tensor cloning in the reverse process of the Net class in the Inv_arch.py file is necessary. Would the absence of cloning lead to network divergence?
Since the training process in my work is quite time-consuming, I would greatly appreciate any insight you could offer. Your guidance could save me a significant amount of time, and I am very grateful for your help.
Thank you again, and I look forward to your response.

Hi Mesks,
In my memory, I have to use the "clone" function to avoid errors. Our "pm2" takes parts of "out_x" and generates "out_x2". Then we use "out_x2" to modify parts of "out_x". If ".clone()" is removed, it may cause error.
Best Regards.

Hi Mesks,
I remember that the "clone" function is used to avoid errors. Our "pm2" takes parts of "out_x" and generates "out_x2". Then we use "out_x2" to modify parts of "out_x". If ".clone()" is removed, it may cause error.
Best Regards.

Hi Mesks,
I remember that the "clone" function is used to avoid errors. Our "pm2" takes parts of "out_x" and generates "out_x2". Then we use "out_x2" to modify parts of "out_x". If ".clone()" is removed, it may leads to an error.
Best Regards.

Hi Mesks,
I remember that the "clone" function is used to avoid errors. Our "pm2" takes parts of "out_x" and generates "out_x2". Then we use "out_x2" to modify parts of "out_x". If ".clone()" is removed, it may leads to an error.
Best Regards.

Thank you for your response. It was still very insightful for me.


Add YmVoice.toFile method

For consistency, I've added methods for OPL and OPLL, but I am not aware of any standard file formats for OPL(L) voices.
A few open questions:

Most instrument file types are binary, but OPM files are plaintext. I've had toFile return a union type, with the idea that the consuming could would have to check the return type to determine whether to write it as plaintext or a binary file. Alternatives I considered are having separate methods for this division, or stuffing OPM in toMML (but I think that's probably incorrect).
I wasn't sure what to do with the the instrument index for 'opm' conversion. Options: leave out the header (consuming code will need to insert the instrument number & title), or have optional parameters argument in toFile (e.g. toFile(type, parameters?: { [key: string]: any }), where parameters are file type-specific), or just hardcode index 0 and let consuming application fix it.

Thank you! It's great.
As for the toFile argument, I also thought that this would be fine for the current situation.


Unable to complete unless password writeback has been enabled

No mention for the requirement within this article of Password writeback being required and this does not flow well if going through the identity features page: https://docs.microsoft.com/en-us/microsoft-365/enterprise/m365-enterprise-test-lab-guides#identity as writeback comes after this. So I would either mention or switch up the order or both

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

ID: f7bd31b7-34a7-82ad-da52-8d6dcfaa7b12
Version Independent ID: 51b0435d-96fa-917a-6278-187769d0c95c
Content: Password reset for your Microsoft 365 test environment
Content Source: microsoft-365/enterprise/password-reset-m365-ent-test-environment.md
Service: o365-solutions
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@officedocsbot assign @mypil

@henryphillipsid - Thank you for submitting feedback.
I will get this issue over to the Microsoft 365 writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@henryphillipsid The content has been corrected to require password writeback before password reset. Thanks for letting us know.

@mypil This has been closed when I was trying to work on.


Coding Tech added to YouTube Channels

Coding Tech partners with the tech conferences around the world that provided Coding Tech with their EXPLICIT permissions to republish videos

This request has been made before previous (https://github.com/MarkoDenic/web-development-resources/commit/6aa36a76628aedc4aa94f136de7e806f04e512ac) was merged. I'll close this one and open another.


Allow application/jwk-set+json JSON response type

The jwks_uri endpoint returns a JSON Web Key Set which is specificed as
content type application/jwk-set+json in
https://tools.ietf.org/html/rfc7517. This change adds this content type
to the response validation logic so that jwks responses from providers
which actually return the correct content type work again.
Fixes: #609

Ah well you fixed it already - no never mind - the patch here fixes the problem for me and i use it until a newer version is released. Thanks!


session cookie is being set even if request fails

this is the code of my controller
 public async register(ctx: HttpContextContract) {
    await ctx.request.validate(RegisterUserValidator)
    const user = new User()
    user.email = ctx.request.input('email')
    user.username = ctx.request.input('username')
    user.password = ctx.request.input('password')
    user.rol = Rol.SUPERUSER
    const organization = new Organization()
    organization.name = ctx.request.input('organization')
    await user.save()
    await user.related('organization').associate(organization)
    await ctx.auth.use('web').login(user)
  }

Sessions and auth are two different things. You can use session without auth as well and hence the session cookie is created when your app is using the session module. https://docs.adonisjs.com/guides/session


In loop, json is recognized as string

When I try to test bellow runn contents,  in roop, json is recognized as string

runn contents

desc: xxxx xxxxx xxxx
vars:
  xxxxx_req:
    - "json://../../json/req/200/normal1.json"
    - "json://../../json/req/200/normal2.json"
  xxxxx_res:
    - "do some magic"
    - "do some magic"
steps:
  normal:
    desc:  xxxx xxxx xxxx xxxx
    loop:
      count: len(vars.xxxxx_req)
    req:
      /xxx/xxx/xx/xxxxx:
        post:
          headers:
            accept: "{{ vars.header.accept }}"
            Content-Type: "{{ vars.header.content_type }}"
            Host: "{{ vars.header.host }}"
            X-API-KEY: "{{ vars.header.x_api_key }}"
          body:
            application/json: "{{ vars.xxxxx_req[i] }}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains vars.xxxxx_res[i]

log

-----START HTTP REQUEST-----
POST xxx/xx/xxx/xx HTTP/1.1
Host: xxxxx
Accept: application/json
Content-Type: application/json
X-Api-Key: xxxxxxx

"json://../../json/req/200/normal2.json" <- not json but string

-----END HTTP REQUEST-----

In no roop, json is recognized correctly.

runn contents

desc: xxx xxxx xxxx
vars:
  xxx_req: "json://../../json/req/200/normal1.json"
 steps:
  normal:
    desc:  xxx xxx xxx
    req:
      /xxx/xxx/xxx/xx:
        post:
          headers:
            accept: "{{ vars.header.accept }}"
            Content-Type: "{{ vars.header.content_type }}"
            Host: "{{ vars.header.host }}"
            X-API-KEY: "{{ vars.header.x_api_key }}"
          body:
            application/json: "{{ vars.xxx_req }}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains "do some magic"

log

-----START HTTP REQUEST-----
POST xxx/xxx/xxx/xx HTTP/1.1
Host: xxxx
Accept: application/json
Content-Type: application/json
X-Api-Key: xxxxxx

{"session": ${ normal1.json contents } <- json is json
-----END HTTP REQUEST-----

The json:// and yaml:// schemes are only allowed in the root of the vars: section.

I think it will be recognized as JSON if set as follows
https://github.com/k1LoW/runn/blob/f1038665a50f256571cb09d0346b0e8000d339d5/testdata/book/httpbin.yml#L22-L25
https://github.com/k1LoW/runn/blob/f1038665a50f256571cb09d0346b0e8000d339d5/testdata/book/httpbin.yml#L107

Thank you for advice.
But., still recognized json as string.

runn book yaml

desc: xxxx xxxxx xxxx
vars:
  xxxxx_req:
    - "../../json/req/200/normal1.json"
    - "../../json/req/200/normal2.json"
  xxxxx_res:
    - "do some magic"
    - "do some magic"
steps:
  normal:
    desc:  xxxx xxxx xxxx xxxx
    loop:
      count: len(vars.xxxxx_req)
    req:
      /xxx/xxx/xx/xxxxx:
        post:
          headers:
            accept: "{{ vars.header.accept }}"
            Content-Type: "{{ vars.header.content_type }}"
            Host: "{{ vars.header.host }}"
            X-API-KEY: "{{ vars.header.x_api_key }}"
          body:
            application/json: "json://{{ vars.xxxxx_req[i] }}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains vars.xxxxx_res[i]

Avobe yaml is imported one.
Bellow yaml is importing yaml.
In order to be recognized json in loop, do I declare json list vars in importing yaml?
If so, it might be hard a little in my usecase.
Because test case is many,   vars will be fat. Also it is hard to find certain test case vars in importing one.
Than that, I want to summarize vars to imported yaml.
I think that way is view better for seeing the details individually.
importing runn book yaml (root)
  xxx xxx xx:
    desc: xxx xxxx xxxx
    include:I
      path: xx/xx/xxx/yamls/200/normal.yaml
      vars:
        header:
          accept: "{{ vars.header.accept }}"
          content_type: "{{ vars.header.content_type }}"
          host: "{{ vars.header.host }}"
          x_api_key: "{{ vars.header.x_api_key }}"

fmm...
I do not know what you want to achieve.
If possible I would be glad to get the smallest example I can try.
You shouldn't need to have a test server by using the API on httpbin.org or github.com.

In order to be recognized json in loop, do I declare json list vars in importing yaml?

You can manage the path of the json file in the runbook from which you are importing

root.yaml

desc: xxxx xxxxx xxxx
vars:
  xxxxx_req:
    - "../../json/req/200/normal1.json"
    - "../../json/req/200/normal2.json"
  xxxxx_res:
    - "do some magic"
    - "do some magic"
 headers:
   accept: 'application/json'
   Content-Type: 'application/json'
   Host: 'xxxx'
   X-API-KEY: 'xxxxxx'

steps:
  normal:
    desc:  xxxx xxxx xxxx xxxx
    loop:
      count: len(vars.xxxxx_req)
    include:
      path: xx/xx/xxx/yamls/200/normal.yaml
      vars:
        headers: '{{ vars.headers }}'
        request: 'json://{{ vars.xxxxx_req[i]}}'
        response: '{{ vars. xxxxx_res[i] }}'

xx/xx/xxx/yamls/200/normal.yaml

vars:
  request: null
  response: null
  headers: null

steps:
  normal:
    desc:  xxxx xxxx xxxx xxxx
    req:
      /xxx/xxx/xx/xxxxx:
        post:
          headers: "{{ vars.headers }}"
          body:
            application/json: "{{ vars.request }}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains vars.response

I want to recognize json as json in impoted yaml.
In runn, Is it  impossible to bellow yaml ?
desc: xxxx xxxxx xxxx
vars:
  xxxxx_req: <- json list
    - "json://../../json/req/200/normal1.json"
    - "json://../../json/req/200/normal2.json"
  xxxxx_res:
    - "do some magic"
    - "do some magic"
steps:
  normal:
    desc:  xxxx xxxx xxxx xxxx
    loop:
      count: len(vars.xxxxx_req)
    req:
      /xxx/xxx/xx/xxxxx:
        post:
          headers:
            accept: "{{ vars.header.accept }}"
            Content-Type: "{{ vars.header.content_type }}"
            Host: "{{ vars.header.host }}"
            X-API-KEY: "{{ vars.header.x_api_key }}"  <- json  as json
          body:
            application/json: "json://{{ vars.xxxxx_req[i] }}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains vars.xxxxx_res[i]

In runn, Is it impossible to make bellow yaml ?

No, it cannot.
The json:// scheme only works for root in the vars: section.

I want to recognize json as json in impoted yaml.

Do you want the list of json file paths in the root runbook to be specified in the vars of the include and expanded as a json request?
I would be able to give you better advice if I could get a more concrete image of the test you want to achieve.

What  is include.vars ?
The json:// scheme only works for root in the vars: section ( or include.vars: ).

With this, the root yaml vars will be fat, right?
if many test is written in root yaml.

What is include.vars ?

vars: section of include runner.

How about xxxxx_req and yyyyy_req and zzzz_req and wwww_req and all responses in one JSON?
desc: xxxx xxxxx xxxx
vars:
  reqres: "json://../../json/reqres.json"
   .
   .
   .
 headers:
   accept: 'application/json'
   Content-Type: 'application/json'
   Host: 'xxxx'
   X-API-KEY: 'xxxxxx'

steps:
  normal-x:
    desc:  xxxx xxxx xxxx xxxx
    loop:
      count: len(vars.reqres.xxxxx)
    req:
      /xxx/xxx/xx/xxxxx:
        post:
          headers:
            accept: "{{ vars.header.accept }}"
            Content-Type: "{{ vars.header.content_type }}"
            Host: "{{ vars.header.host }}"
            X-API-KEY: "{{ vars.header.x_api_key }}"
          body:
            application/json: "{{ vars.reqres.xxxxx[i].req}}"
    test: steps.normal.res.status == 200
      && steps.normal.res.body contains vars.reqres.xxxxx[i].res
.
.
.

With this, the root yaml vars will be fat, right?

I don't know if this is what you want, but at least all requests and responses can be externalized to reqres.json.

With this, the root yaml vars will be fat, right?

How to divide the scenario to solve the problem of large root yaml? It would be better to consider how to divide the scenario.

Define the steps of a repeating scenario as a single scenario itself.
Define several steps as a single scenario.
For example, split the yaml as one scenario with normal-x and normal-y steps (Have normal-z and normal-w processed in a separate file)

Hi @t-kitamura-axel
runn now support wildcards in json:// and yaml://.
I think this will be one way to solve your problem.


[3.x] Fix GDNativeLibrary::get_current_library_path()

Return a const String reference to make sure that when its address
is used as a handle in NativeScriptLanguage::init_library(),
it refers to the heap instead of a temporary object on the stack.

Thanks!


匯狀況

Pull Request Test Coverage Report for Build 60

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

Totals

Change from base Build 59:
0.0%

Covered Lines:
179

Relevant Lines:
223

💛  - Coveralls

Pull Request Test Coverage Report for Build 60

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

Totals

Change from base Build 59:
0.0%

Covered Lines:
179

Relevant Lines:
223

💛  - Coveralls


updated peerDependencies instead of devDependencies

https://github.com/kellyselden/eslint-mocha/issues/87
https://github.com/kellyselden/eslint-mocha/compare/greenkeeper/mocha-3.3.0

This should be resolved with https://github.com/greenkeeperio/greenkeeper/pull/465

#465 is merged & deployed. Thanks for reporting this and have a great day!

Thanks for fixing!


Add basic CI

It should now be possible (#3 #4) to add basic CI (github actions) to the repository.
For now, this will be CPU-based and running on a DIAG private runner.
Steps for doing so:

[ ] Add the test resources tar file (28MB) under git-lfs in the repo
[ ] Create the Github actions CI script
[ ] Configure the private runner
[ ] Make sure it works and the tests pass
[ ] Add a nice CI badge to the main README.md

The first issue with this is that github does not support pushing git-lfs objects to a forked repository:
https://github.com/git-lfs/git-lfs/issues/1906.
The file is relatively small, so we could just check it in normally, or alternatively install it on the private runner.
My preference is for the first option.
I'll continue with the subsequent steps.


[http-client-csharp] Bump typespec version to 0.63.0

Fixes https://github.com/microsoft/typespec/issues/5347

API change check
APIView has identified API level changes in this PR and created following API reviews.
@typespec/http-client-csharp


Make functional breakpoints system

http://susydocs.oddbird.net/en/latest/toolkit/#breakpoint
https://github.com/Team-Sass/breakpoint

Some (maybe) useful links:

http://stackoverflow.com/questions/16813622/nested-grids-with-breakpoints

substituted breakpoint for include-media

substituted breakpoint for include-media


[5.9] [benchmark] bump minimum OS versions

(cherry picked from commit 942ea60af4fd69f13a618c6756e1b9c41bc5e888)
When building Swift benchmark suite with Xcode 15 beta, we are seeing error due to wrong OS deployment target.
/Users/ec2-user/jenkins/workspace/test-new-xcode-oss-swift-pr-test-macos-5.9/swift/benchmark/single-source/CharacterProperties.swift:90:21: error: 'CharacterSet' is only available in macOS 10.10 or newer
let alphanumerics = CharacterSet.alphanumerics
                    ^

@swift-ci test


Create unmanaged kubernetes cluster on CloudStack

Issue #, if available:
Description of changes:
Creates an unmanaged kubernetes cluster on Cloudstack. This provides a nice view of CAPC managed kubernetes cluster in CloudStack UI.
Depends on: https://github.com/apache/cloudstack/pull/7515 https://github.com/apache/cloudstack-go/pull/59 (go.mod needs to be updated once this is merged)
Testing performed:
Tested locally by creating a kubernetes cluster using cluster api.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @chrisdoherty4
This creates an entry for a kubernetes cluster in CloudStack. This helps provide a good view of CAPC managed clusters on CloudStack and the VMs associated with the cluster in the CloudStack UI. This PR is dependent on apache/cloudstack-go PR merge and release. So, it will be some time before this PR can be merged.

@vishesh92 So populating this value would bind VMs to an Apache CloudStack Cluster ('cluster' is hyperloaded in this context)?
Am I right in saying we expect users to have pre-created the cluster?

cluster has a different meaning when it comes to cloudstack infrastructure. In context of this PR, cluster == kubernetes cluster.
We are doing two operation when the CAPC managed kubernetes cluster comes up:

Create an entry in CloudStack's kubernetes dashboard. This is just a simple insert into db and cloudstack doesn't do anything else on this resource.
When the machine deployments get created or deleted, we link or de-link the VM created by CAPC on cloudstack with kubernetes cluster (on CloudStack) entry created earlier.

In short, we are just adding some information about the kubernetes cluster which is managed by CAPC on CloudStack.

ping @vishesh92 is this up to date?

Codecov Report
Patch coverage: 6.34% and project coverage change: -0.45% :warning:

Comparison is base (b860d9f) 24.95% compared to head (d640335) 24.51%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #250      +/-   ##
==========================================
- Coverage   24.95%   24.51%   -0.45%
==========================================
  Files          59       60       +1
  Lines        5558     5687     +129
==========================================
+ Hits         1387     1394       +7
- Misses       4035     4156     +121
- Partials      136      137       +1

Files Changed
Coverage Δ

api/v1beta3/cloudstackcluster_types.go
100.00% <ø> (ø)

controllers/cloudstackcluster_controller.go
16.66% <0.00%> (-4.63%)
:arrow_down:

controllers/cloudstackfailuredomain_controller.go
61.00% <ø> (ø)

pkg/cloud/client.go
48.29% <ø> (ø)

pkg/cloud/cluster.go
0.00% <0.00%> (ø)

controllers/cloudstackmachine_controller.go
54.87% <87.50%> (+0.56%)
:arrow_up:

pkg/cloud/isolated_network.go
58.89% <100.00%> (ø)

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

Tests were aborted.

Tests were aborted.

/run-e2e -c 4.18

@vishesh92 a jenkins job has been kicked to run test with following paramaters:

kubernetes version: 1.27.2
CloudStack version: 4.18
hypervisor: kvm
template: ubuntu-2004-kube
Kubernetes upgrade from: 1.26.5 to 1.27.2

Test Results : (tid-298)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.18
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-298.zip
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
[PASS] When the specified resource does not exist Should fail due to the specified account is not found [TC4a]
[PASS] When the specified resource does not exist Should fail due to the specified domain is not found [TC4b]
[PASS] When the specified resource does not exist Should fail due to the specified zone is not found [TC3]
[PASS] When the specified resource does not exist Should fail due to the public IP can not be found

Summarizing 24 Failures:

[Fail] When testing machine remediation [It] Should replace a machine when it is destroyed
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing node drain timeout [It] A node should be forcefully removed if it cannot be drained in time
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing multiple CPs in a shared network with kubevip [It] Should successfully create a cluster with multiple CPs in a shared network
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing with custom disk offering [It] Should successfully create a cluster with a custom disk offering
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster with network interruption [ToxiProxy] [It] Should be able to create a cluster despite a network interruption during that process
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing Kubernetes version upgrades [It] Should successfully upgrade kubernetes versions when there is a change in relevant fields
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster with slow network [ToxiProxy] [BeforeEach] Should be able to download an HTML from the app deployed to the workload cluster
/jenkins/workspace/capc-e2e-new/test/e2e/toxiproxy/toxiProxy.go:203

[Fail] When testing affinity group [It] Should have host affinity group when affinity is pro
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing affinity group [It] Should have host affinity group when affinity is anti
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing subdomain [It] Should create a cluster in a subdomain
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster [TC1][PR-Blocking] [It] Should be able to download an HTML from the app deployed to the workload cluster
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] with two clusters [It] should successfully add and remove a second cluster without breaking the first cluster
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] [It] Should successfully scale machine replicas up and down horizontally
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing with disk offering [It] Should successfully create a cluster with disk offering
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When the specified resource does not exist [It] Should fail due to the specified control plane offering is not found [TC7]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified template is not found [TC6]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offering is not found
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the compute resources are not sufficient for the specified offering [TC8]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offer is not customized but the disk size is specified
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offer is customized but the disk size is not specified
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist When starting with a healthy cluster [BeforeEach] Should fail to upgrade worker machine due to insufficient compute resources
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When the specified resource does not exist When starting with a healthy cluster [BeforeEach] Should fail to upgrade control plane machine due to insufficient compute resources
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing resource cleanup [It] Should create a new network when the specified network does not exist
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing MachineDeployment rolling upgrades [It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

Ran 28 of 29 Specs in 7147.886 seconds
FAIL! -- 4 Passed | 24 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (7147.90s)
FAIL

/run-e2e -c 4.18

@vishesh92 a jenkins job has been kicked to run test with following paramaters:

kubernetes version: 1.27.2
CloudStack version: 4.18
hypervisor: kvm
template: ubuntu-2004-kube
Kubernetes upgrade from: 1.26.5 to 1.27.2

Test Results : (tid-299)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.18
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-299.zip
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest

Summarizing 28 Failures:

[Fail] When testing node drain timeout [It] A node should be forcefully removed if it cannot be drained in time
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing MachineDeployment rolling upgrades [It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] [It] Should successfully scale machine replicas up and down horizontally
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing with custom disk offering [It] Should successfully create a cluster with a custom disk offering
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing multiple CPs in a shared network with kubevip [It] Should successfully create a cluster with multiple CPs in a shared network
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing machine remediation [It] Should replace a machine when it is destroyed
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When the specified resource does not exist [It] Should fail due to the specified account is not found [TC4a]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified domain is not found [TC4b]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified control plane offering is not found [TC7]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified template is not found [TC6]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified zone is not found [TC3]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offering is not found
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the compute resources are not sufficient for the specified offering [TC8]
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offer is not customized but the disk size is specified
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the specified disk offer is customized but the disk size is not specified
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist [It] Should fail due to the public IP can not be found
/jenkins/workspace/capc-e2e-new/test/e2e/invalid_resource.go:253

[Fail] When the specified resource does not exist When starting with a healthy cluster [BeforeEach] Should fail to upgrade worker machine due to insufficient compute resources
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When the specified resource does not exist When starting with a healthy cluster [BeforeEach] Should fail to upgrade control plane machine due to insufficient compute resources
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster with network interruption [ToxiProxy] [BeforeEach] Should be able to create a cluster despite a network interruption during that process
/jenkins/workspace/capc-e2e-new/test/e2e/toxiproxy/toxiProxy.go:203

[Fail] When testing affinity group [It] Should have host affinity group when affinity is pro
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing affinity group [It] Should have host affinity group when affinity is anti
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing subdomain [It] Should create a cluster in a subdomain
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing Kubernetes version upgrades [It] Should successfully upgrade kubernetes versions when there is a change in relevant fields
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing resource cleanup [It] Should create a new network when the specified network does not exist
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] with two clusters [It] should successfully add and remove a second cluster without breaking the first cluster
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster with slow network [ToxiProxy] [BeforeEach] Should be able to download an HTML from the app deployed to the workload cluster
/jenkins/workspace/capc-e2e-new/test/e2e/toxiproxy/toxiProxy.go:203

[Fail] When testing with disk offering [It] Should successfully create a cluster with disk offering
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

[Fail] When testing app deployment to the workload cluster [TC1][PR-Blocking] [It] Should be able to download an HTML from the app deployed to the workload cluster
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

Ran 28 of 29 Specs in 7944.351 seconds
FAIL! -- 0 Passed | 28 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (7944.36s)
FAIL

/run-e2e -c 4.18

@vishesh92 a jenkins job has been kicked to run test with following paramaters:

kubernetes version: 1.27.2
CloudStack version: 4.18
hypervisor: kvm
template: ubuntu-2004-kube
Kubernetes upgrade from: 1.26.5 to 1.27.2

Test Results : (tid-301)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.18
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-301.zip
[PASS] with two clusters should successfully add and remove a second cluster without breaking the first cluster
[PASS] When testing resource cleanup Should create a new network when the specified network does not exist
[PASS] When the specified resource does not exist Should fail due to the specified account is not found [TC4a]
[PASS] When the specified resource does not exist Should fail due to the specified domain is not found [TC4b]
[PASS] When the specified resource does not exist Should fail due to the specified control plane offering is not found [TC7]
[PASS] When the specified resource does not exist Should fail due to the specified template is not found [TC6]
[PASS] When the specified resource does not exist Should fail due to the specified zone is not found [TC3]
[PASS] When the specified resource does not exist Should fail due to the specified disk offering is not found
[PASS] When the specified resource does not exist Should fail due to the compute resources are not sufficient for the specified offering [TC8]
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is not customized but the disk size is specified
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is customized but the disk size is not specified
[PASS] When the specified resource does not exist Should fail due to the public IP can not be found
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade worker machine due to insufficient compute resources
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade control plane machine due to insufficient compute resources
[PASS] When testing affinity group Should have host affinity group when affinity is pro
[PASS] When testing affinity group Should have host affinity group when affinity is anti
[PASS] When testing app deployment to the workload cluster with slow network [ToxiProxy] Should be able to download an HTML from the app deployed to the workload cluster
[PASS] When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
[PASS] When testing multiple CPs in a shared network with kubevip Should successfully create a cluster with multiple CPs in a shared network
[PASS] When testing with custom disk offering Should successfully create a cluster with a custom disk offering
[PASS] When testing node drain timeout A node should be forcefully removed if it cannot be drained in time
[PASS] When testing app deployment to the workload cluster [TC1][PR-Blocking] Should be able to download an HTML from the app deployed to the workload cluster
[PASS] When testing machine remediation Should replace a machine when it is destroyed
[PASS] When testing app deployment to the workload cluster with network interruption [ToxiProxy] Should be able to create a cluster despite a network interruption during that process
[PASS] When testing subdomain Should create a cluster in a subdomain
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
[PASS] When testing with disk offering Should successfully create a cluster with disk offering
[PASS] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] Should successfully scale machine replicas up and down horizontally
[PASS] When testing Kubernetes version upgrades Should successfully upgrade kubernetes versions when there is a change in relevant fields

Ran 28 of 29 Specs in 8531.751 seconds
SUCCESS! -- 28 Passed | 0 Failed | 0 Pending | 1 Skipped
PASS

/run-e2e -c 4.17

@weizhouapache a jenkins job has been kicked to run test with following paramaters:

kubernetes version: 1.27.2
CloudStack version: 4.17
hypervisor: kvm
template: ubuntu-2004-kube
Kubernetes upgrade from: 1.26.5 to 1.27.2

Test Results : (tid-302)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.17
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-302.zip
[PASS] When testing Kubernetes version upgrades Should successfully upgrade kubernetes versions when there is a change in relevant fields
[PASS] When testing app deployment to the workload cluster with network interruption [ToxiProxy] Should be able to create a cluster despite a network interruption during that process
[PASS] When testing resource cleanup Should create a new network when the specified network does not exist
[PASS] When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
[PASS] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] Should successfully scale machine replicas up and down horizontally
[PASS] When testing machine remediation Should replace a machine when it is destroyed
[PASS] When testing node drain timeout A node should be forcefully removed if it cannot be drained in time
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
[PASS] When testing subdomain Should create a cluster in a subdomain
[PASS] When testing affinity group Should have host affinity group when affinity is anti
[PASS] When testing multiple CPs in a shared network with kubevip Should successfully create a cluster with multiple CPs in a shared network
[PASS] When testing with disk offering Should successfully create a cluster with disk offering
[PASS] When testing with custom disk offering Should successfully create a cluster with a custom disk offering
[PASS] with two clusters should successfully add and remove a second cluster without breaking the first cluster
[PASS] When the specified resource does not exist Should fail due to the specified account is not found [TC4a]
[PASS] When the specified resource does not exist Should fail due to the specified domain is not found [TC4b]
[PASS] When the specified resource does not exist Should fail due to the specified control plane offering is not found [TC7]
[PASS] When the specified resource does not exist Should fail due to the specified template is not found [TC6]
[PASS] When the specified resource does not exist Should fail due to the specified zone is not found [TC3]
[PASS] When the specified resource does not exist Should fail due to the specified disk offering is not found
[PASS] When the specified resource does not exist Should fail due to the compute resources are not sufficient for the specified offering [TC8]
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is not customized but the disk size is specified
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is customized but the disk size is not specified
[PASS] When the specified resource does not exist Should fail due to the public IP can not be found
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade worker machine due to insufficient compute resources
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade control plane machine due to insufficient compute resources

Summarizing 3 Failures:

[Fail] When testing affinity group [It] Should have host affinity group when affinity is pro
/jenkins/workspace/capc-e2e-new/test/e2e/common.go:331

[Fail] When testing app deployment to the workload cluster [TC1][PR-Blocking] [It] Should be able to download an HTML from the app deployed to the workload cluster
/jenkins/workspace/capc-e2e-new/test/e2e/deploy_app.go:111

[Fail] When testing app deployment to the workload cluster with slow network [ToxiProxy] [It] Should be able to download an HTML from the app deployed to the workload cluster
/jenkins/workspace/capc-e2e-new/test/e2e/deploy_app_toxi.go:134

Ran 28 of 29 Specs in 8818.848 seconds
FAIL! -- 25 Passed | 3 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (8818.86s)
FAIL

/run-e2e -c 4.18

@vishesh92 a jenkins job has been kicked to run test with following paramaters:

kubernetes version: 1.27.2
CloudStack version: 4.18
hypervisor: kvm
template: ubuntu-2004-kube
Kubernetes upgrade from: 1.26.5 to 1.27.2

Test Results : (tid-303)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.18
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-303.zip
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
[PASS] When testing machine remediation Should replace a machine when it is destroyed
[PASS] with two clusters should successfully add and remove a second cluster without breaking the first cluster
[PASS] When testing app deployment to the workload cluster [TC1][PR-Blocking] Should be able to download an HTML from the app deployed to the workload cluster
[PASS] When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
[PASS] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] Should successfully scale machine replicas up and down horizontally
[PASS] When testing app deployment to the workload cluster with slow network [ToxiProxy] Should be able to download an HTML from the app deployed to the workload cluster
[PASS] When testing with custom disk offering Should successfully create a cluster with a custom disk offering
[PASS] When the specified resource does not exist Should fail due to the specified account is not found [TC4a]
[PASS] When the specified resource does not exist Should fail due to the specified domain is not found [TC4b]
[PASS] When the specified resource does not exist Should fail due to the specified control plane offering is not found [TC7]
[PASS] When the specified resource does not exist Should fail due to the specified template is not found [TC6]
[PASS] When the specified resource does not exist Should fail due to the specified zone is not found [TC3]
[PASS] When the specified resource does not exist Should fail due to the specified disk offering is not found
[PASS] When the specified resource does not exist Should fail due to the compute resources are not sufficient for the specified offering [TC8]
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is not customized but the disk size is specified
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is customized but the disk size is not specified
[PASS] When the specified resource does not exist Should fail due to the public IP can not be found
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade worker machine due to insufficient compute resources
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade control plane machine due to insufficient compute resources
[PASS] When testing subdomain Should create a cluster in a subdomain
[PASS] When testing affinity group Should have host affinity group when affinity is anti
[PASS] When testing with disk offering Should successfully create a cluster with disk offering
[PASS] When testing multiple CPs in a shared network with kubevip Should successfully create a cluster with multiple CPs in a shared network
[PASS] When testing app deployment to the workload cluster with network interruption [ToxiProxy] Should be able to create a cluster despite a network interruption during that process
[PASS] When testing node drain timeout A node should be forcefully removed if it cannot be drained in time

Summarizing 3 Failures:

[Fail] When testing resource cleanup [AfterEach] Should create a new network when the specified network does not exist
/jenkins/workspace/capc-e2e-new/test/e2e/resource_cleanup.go:101

[Fail] When testing affinity group [It] Should have host affinity group when affinity is pro
/jenkins/workspace/capc-e2e-new/test/e2e/common.go:331

[Fail] When testing Kubernetes version upgrades [It] Should successfully upgrade kubernetes versions when there is a change in relevant fields
/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.12/framework/cluster_helpers.go:143

Ran 28 of 29 Specs in 9073.198 seconds
FAIL! -- 25 Passed | 3 Failed | 0 Pending | 1 Skipped
--- FAIL: TestE2E (9073.21s)
FAIL

@vishesh92 This PR looks good, and you've added unit tests as well. Can you add a check in one of the e2e tests to ensure that the resources are created on ACS ?

cluster has a different meaning when it comes to cloudstack infrastructure. In context of this PR, cluster == kubernetes cluster.

I think it would be better to rename any reference to an ACS cluster as an unmanaged cluster (the interface, method names, etc) to avoid any confusion similar to how the API has CloudStackClusterID and not ClusterID

@rohityadavcloud
a) It shouldn't be an issue if the CKS plugin is not enabled or is on an older version.
b) I have introduced a cluster type field which is used to differentiate between the clusters.

Tests were aborted.

Tests were aborted.

/run-e2e -c 4.18

Test Results : (tid-325)
Environment: kvm Rocky8(x3), Advanced Networking with Management Server Rocky8
Kubernetes Version:  v1.27.2
Kubernetes Version upgrade from:  v1.26.5
Kubernetes Version upgrade to:  v1.27.2
CloudStack Version:  4.18
Template:  ubuntu-2004-kube
E2E Test Run Logs: https://github.com/blueorangutan/capc-prs/releases/download/capc-pr-ci-cd/capc-e2e-artifacts-pr250-sl-325.zip
[PASS] When testing app deployment to the workload cluster with network interruption [ToxiProxy] Should be able to create a cluster despite a network interruption during that process
[PASS] When testing resource cleanup Should create a new network when the specified network does not exist
[PASS] When testing horizontal scale out/in [TC17][TC18][TC20][TC21] Should successfully scale machine replicas up and down horizontally
[PASS] When testing with custom disk offering Should successfully create a cluster with a custom disk offering
[PASS] When testing creation of unmanaged CKS cluster in ACS Should create a workload cluster
[PASS] When testing multiple CPs in a shared network with kubevip Should successfully create a cluster with multiple CPs in a shared network
[PASS] When testing machine remediation Should replace a machine when it is destroyed
[PASS] When testing MachineDeployment rolling upgrades Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
[PASS] When testing K8S conformance [Conformance] Should create a workload cluster and run kubetest
[PASS] When testing affinity group Should have host affinity group when affinity is pro
[PASS] When testing affinity group Should have host affinity group when affinity is anti
[PASS] When testing node drain timeout A node should be forcefully removed if it cannot be drained in time
[PASS] When the specified resource does not exist Should fail due to the specified account is not found [TC4a]
[PASS] When the specified resource does not exist Should fail due to the specified domain is not found [TC4b]
[PASS] When the specified resource does not exist Should fail due to the specified control plane offering is not found [TC7]
[PASS] When the specified resource does not exist Should fail due to the specified template is not found [TC6]
[PASS] When the specified resource does not exist Should fail due to the specified zone is not found [TC3]
[PASS] When the specified resource does not exist Should fail due to the specified disk offering is not found
[PASS] When the specified resource does not exist Should fail due to the compute resources are not sufficient for the specified offering [TC8]
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is not customized but the disk size is specified
[PASS] When the specified resource does not exist Should fail due to the specified disk offer is customized but the disk size is not specified
[PASS] When the specified resource does not exist Should fail due to the public IP can not be found
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade worker machine due to insufficient compute resources
[PASS] When the specified resource does not exist When starting with a healthy cluster Should fail to upgrade control plane machine due to insufficient compute resources
[PASS] When testing app deployment to the workload cluster [TC1][PR-Blocking] Should be able to download an HTML from the app deployed to the workload cluster
[PASS] When testing Kubernetes version upgrades Should successfully upgrade kubernetes versions when there is a change in relevant fields
[PASS] When testing subdomain Should create a cluster in a subdomain
[PASS] with two clusters should successfully add and remove a second cluster without breaking the first cluster
[PASS] When testing with disk offering Should successfully create a cluster with disk offering

Summarizing 1 Failure:

[Fail] When testing app deployment to the workload cluster with slow network [ToxiProxy] [It] Should be able to download an HTML from the app deployed to the workload cluster
/jenkins/workspace/capc-e2e-new/test/e2e/deploy_app_toxi.go:134

Ran 28 of 30 Specs in 8968.702 seconds
FAIL! -- 27 Passed | 1 Failed | 0 Pending | 2 Skipped
--- FAIL: TestE2E (8968.71s)
FAIL

It seems like this could be done by anything with access to the cloudstack API and the kube api server, right? We don't need special information that is only available inside the capc controller or to hook into particular events that are hidden in the reconcilers. This just needs to watch the CloudstackCluster resources and possibly the CloudstackMachines's?

I want to make the integration a part of the CAPC controller since it has enough information about all the resources and the account and domain it needs to be part of. In future we might add even more information regarding the CAPC cluster in CKS as well and having it as part of the controller would help.

I might be missing the point of this feature but it feels a little bit like unnecessary complexity. It's not only just adding this feature, now we need to maintain it and test it and the benefits seem dubious to be.
Given that the CAPI API is our pane of glass to describe k8s clusters, adding a second one that works in parallel and not built on top of it appears like duplicated functionality.

I'm with you, this is adding a lot of CKS-specific logic to the controller, whose only task it should be to reconcile CAPI based clusters. I think there are bigger fish to fry (keeping up-to-date with CAPI and k8s versions, releasing more often etc.)

Hi @g-gaston @hrak I see your points and completely understand why would anybody want to make CAPC complex. But hear us out.
Apache CloudStack has always been a community-led, turnkey IaaS platform. The emphasis on turn-key, easy to use, setup and deploy, with a great UI and that it just works (out of the box). While CAPC can be used as a building-block, such as for EKS-A, we think this is also used directly as a first-class tool in itself with clusterctl.
Before CAPC, CloudStack's only supposed Kubernetes integration was in the form of CKS (CloudStack Kubernetes Service) wherein CloudStack orchestrates k8s clusters for its users. However, the CKS built clusters make some assumption and deploy specific CNIs to make this work out of the box - easy to deploy k8s cluster for most users. And CKS is available for all user account types, if the service providers, operator or enterprise admin enables and configures CKS in their environment.
With CAPC, there is more flexibility but this isn't available for all user types (currently, domain and root admins) and a group of contributors think it would be good idea if an end user can simply deploy a CAPC cluster and there is just a linked-resource created in the form of unmanaged CKS cluster (for example, to give you an idea head over to https://qa.cloudstack.cloud/simulator/#/kubernetes to see such a resource, this shoudn't be confused with a CloudStack Cluster of a zone).
To address these, we've created a general mechanism via https://github.com/apache/cloudstack/pull/7515 and series of fixes such the ability for normal user accounts to pick/use a public IP say in a shared network with https://github.com/apache/cloudstack/issues/7817. This could help fix https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/issues/303 in future releases. The final lacking piece if a normal user account deploy a CAPC cluster, can we give him a control plane view to say there exists a k8s cluster in CloudStack but it's externally (CAPC) managed - that's where this feature comes in.
Now, you're both right - we don't need this PR to do that, there could be an external script and tool for this, however, it would make it complex for users and operators to set this up and the overall solution wouldn't be turnkey. Such an external tool/script would need to be aware of CloudStack and aware/access of the CAPC cluster and do that for all accounts would just introduce multiple competing control plane paths.
So, here's my proposal - @vishesh92 can introduce an new optional/parameter in the CAPC cluster generated yaml (or via a support cmd-line arg that generate the same) to enable/disable the feature. By default, this is kept enabled so any CAPC user deploying a k8s cluster see an unmanaged CKS cluster in the UI. And downstream tools and users who don't want this behaviour can turn it off via the option/setting in the generated yaml. This way you can control that the new code introduced in this PR doesn't get into the operational path in downstream use-cases, and upstream CAPC and ACS releases are turnkey.
Thoughts?

Hi @rohityadavcloud,
Thanks for sharing your thoughts and elaborating on intent. I do have reservations about this feature. Maintaining the scope outlined in the Cluster API documentation for infrastructure providers ensures we don't feature creep and have an easier time maintaining CAPC. Additional functionality, such as this PR, can be added through auxiliary components, as you highlighted, which would honor the single responsibility principle. Furthermore, considering the roadmap for CKS integration is somewhat unclear to the CAPC community, having a best effort integration doesn't feel like the right path forward.

With CAPC, there is more flexibility but this isn't available for all user types ... it would be good idea if an end user can simply deploy a CAPC cluster and there is just a linked-resource created in the form of unmanaged CKS cluster

This sounds like 2 different asks:

"I want to deploy CAPC clusters using any user type"
"I want a cluster to appear in my CKS plugin UI"

On (1), I think we need to ask why said user types are required and broaden the scope we're considering. For example, perhaps a more flexible permissions model in Apache CloudStack would enable finer permission control so users can create whatever kind of user they wish?
On (2), I empathize with this desire, but I question what a user can do with an unmanaged CKS cluster (not to mention it isn't a CKS cluster) -  it's read-only if I'm not mistaken? Have we established why this is needed? In any case, it feels like it falls outside the scope of CAPC.

however, it would make it complex for users and operators to set this up and the overall solution wouldn't be turnkey

I think that's dependent on how you create a solution. Cluster API in itself isn't turnkey: you have to deploy Cluster API, then you can create your clusters. There's nothing preventing building a solution that wraps deployment of all the necessary components, including a component that embodies the integration in this PR, which would be truly turnkey; though I don't think that's a concern for CAPC.

Such an external tool/script would need to be aware of CloudStack and aware/access of the CAPC cluster and do that for all accounts would just introduce multiple competing control plane paths.

That seems like an appropriate set of dependencies for this kind of component, though I don't understand the "do it for all accounts" or "competing control plane paths" parts; perhaps you could elaborate?
I think its worth pointing out that all existing components built for Kubernetes have this kind of dependency set. Monitoring tools like Jaeger and Prometheus come to mind.

Hi @vishesh92. It sounds like you may have tried gathering feedback prior to completing the upstream CloudStack work and the work in this PR. I'm sorry I missed that and have provided feedback late in the day including leaving this PR untouched for a prolonged period. We should be aiming to avoid this again, lets chat in the Kubernetes CAPC Slack on how to best address the communication inefficiencies.


HELP ME

Describe your problem here.
why does the source code build give an error when compiling, it says its missing mspdbcore.dll
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

pretty sure it got something to do wit your PATH


SC-6053: Composer. Retry download if error 55 is encountered

PR Description
Fixes

Updated the version of the Composer to solve an issue with retry download if error 55 is encountered.

Checklist

[x] I agree with the Code Contribution License Agreement in CONTRIBUTING.md

Please remove me from this org.
Regards,
Sanyam
On Thu, 5 Oct 2023 at 6:38 PM, Artem Stromets @.***>
wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/spryker/docker-php/pull/80#pullrequestreview-1659819645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRZYFCYNJTQDRFNFY6XKNTX52WMBAVCNFSM6AAAAAA5UG7QPCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMNJZHAYTSNRUGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add Pipeline button wrong color and format

Rancher versions: v2.0.0-alpha17
Steps to Reproduce:

Go to Pipeline list page

Results:  The Add pipeline button is light blue with a + image in front of it.  + should not be there and the button should be the darker blue.
Add Pipeline

Example of new correct button look - Add Ingress

Version - 2.0 master 3/19
Verified fixed


Relationship with com.sun.xml.ws?

Multiple jaxws-maven-plugin artifacts can be found on Maven Central, three of which have been updated recently. Here are the group ids and the developers as mentioned in the respective poms.

org.codehaus.mojo (this project), by Lukas Jungmann (Oracle), Rama Pulavarthi (@Sun), Kohsuke Kawaguchi (@Sun), Guillaume Nodet (@Apache, LogicBlaze, Inc), Dan Tran
com.sun.xml.ws (source possibly here), by Lukas Jungmann (Oracle), Roman Grigoriadi (@Oracle), Zheng Jun Li (@Oracle)
com.helger.maven (source), by Lukas Jungmann (Oracle), Rama Pulavarthi (@Sun), Kohsuke Kawaguchi (@Sun), Guillaume Nodet (@Apache, LogicBlaze, Inc), Dan Tran

The two older ones have these group ids.

org.jvnet.jax-ws-commons
net.trajano.mojo

The website indicates that this project used the org.jvnet.jax-ws-commons group id previously, but does not mention the other three.
It would be useful to relate this project especially to the two other ones which seem to be developing in parallel and using totally different version schemes. com.sun.xml.ws published version 2.3.3-b01 last December, whereas this project already had a version 2.5 published since 2017, and published a 2.6 version in 2020. com.helger.maven published version 2.6 in 2018, and published version 2.6.2 in 2019. It seems currently difficult to know, for example, if all these versions have the same issues, or if it is worth trying another one when one suspects a bug; or know if one of these plugins is more “official”.
It seems that the com.helger.maven one started as a fork of the org.codehaus.mojo at a time where the latter was unmaintained, published a com.helger.maven:jaxws-maven-plugin:2.6 version in 2018 (continuing with the numbering scheme of org.codehaus.mojo:jaxws-maven-plugin), then 2.6.1 and 2.6.2; and meanwhile, org.codehaus.mojo came back to life and published its own 2.6 version in 2020. But I ignore whether, for example, the patches in the com.helger.maven fork in the 2.6.x versions have been integrated back into the org.codehaus.mojo:jaxws-maven-plugin:2.6 version…
Some words of clarification would help many developers, I suspect!

Just found this.


Error 500 Internal server error after declaration signing PROD

After declaration signing user gets at error 500 Internal server error.
{
"meta": {
"url": "http://api-svc.il/api/declaration_requests/2aca86da-9212-417b-9944-fd36e2a39363/actions/sign",
"code": 500,
"type": "object",
"request_id": "96f3d8f4-5b64-42b8-9635-3e7196769368#153295"
},
"error": {
"errors": {
"detail": "Internal server error"
}
}
}
Please see files: request.json, request_body.json, response.json here:
https://drive.google.com/drive/u/0/folders/1C_wkXMdDHKOrswHI1ZE4VjanR2YotFsN

the same problem from other user:
{"meta":
{"url":"http://api-svc.il/api/declaration_requests","type":"object","request_id":"4a9af8e3-f56f-4566-9124-45c4fdfcef63#102410","code":500}
,"error":{"errors":{"detail":"Internal server error"}},"code":500}

this kind of issues might happen 13.07.2018  only between 12:55-13:10. Was related to the index rebuilding.


Fix io.stat parsing errors

What does this PR do?
Closes https://github.com/elastic/beats/issues/32345
This makes the parsing of io.stat cgroup files much more defensive; and also skips over errors that can happen while looking for device names.
Why is it important?
This is causing lots of non-fatal yet annoying errors.
Checklist

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added an entry in CHANGELOG.md

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-03-10T18:45:23.951+0000

Duration: 10 min 33 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
188

Skipped
7

Total
195

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

Elastic agent and fleet-server will still have this bug, they are using the previous v0.4.4 version of the package:

https://github.com/elastic/fleet-server/blob/b67d3a0031201d36565aa24e49060821bccb7335/go.mod#L11
https://github.com/elastic/elastic-agent/blob/main/go.mod#L18

This should be fixed in the elastic agent process itself in the upcoming 8.7.1 release.

I confirm, this is OK from v8.7.1, nice work!

@ebuildy  Is it added in 8.7.1 only reason for asking its not listed in release notes.
https://www.elastic.co/guide/en/beats/libbeat/8.7/release-notes-8.7.1.html and PR has 8.8 candidate label https://github.com/elastic/beats/issues/32345
I have customer waiting so just wanted to pass info if this is indeed release in 8.7.1

yes that I said, I can confirm this is working from v8.7.1


Update link to simple example

The current Ellie example for a simple datepicker is using date-picker 3.0.0. I refactored that Ellie example to use 7.2.3, here is the link to the updated version.

Fab! Thanks so much.


Add Support for Laravel 10

Fix LaraBugHandler.php
Add Github action test for laravel 10

Maybe we can drop support for old PHP and Laravel versions in this PR. What do you think @Cannonb4ll ?

Yes, much better, to be as easy to maintain this package

Closing, already done by @Cannonb4ll https://github.com/LaraBug/LaraBug/commit/01014a1bc912bad99b442615e5232f5c427affdf

when will this be tagged?

when will this be tagged?

you can you this update by changin in conposer.json to
dev-master


Cow: Watch thriveread.com

Cow requests the watch of the watch_keyword thriveread\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thriveread\.com has been seen in 3 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Mongo timeouts not handled

For some reason, I am not sure why, but the Centos boxes I am installing on have a 2 minute timeout on mongo connections. When mongo times out, the rest api cannot recover and just hangs. I spent hours trying to fix this problem by adjusting various timeouts to no avail. The way I fixed it is by listening for the timeout and then closing and reconnecting. You must close any open db connections or you will leak them. You cannot just forget about them. I am providing my fix. Here you go....
In mongoHandler.js
/**
 Initialise gets invoked once for each resource that uses this handler.
 */
MongoStore.prototype.initialise = function(resourceConfig) {
  var self = this;
  if (!self._config.url) {
    return console.error("MongoDB url missing from configuration");
  }
  self.resourceConfig = resourceConfig;
  self.relationshipAttributeNames = MongoStore._getRelationshipAttributeNames(resourceConfig.attributes);
  mongodb.MongoClient.connect(self._config.url, {
    server: {
      reconnectTries: 999999999,
      reconnectInterval: 5000
    }
  }).then(function(db) {
    self._db = db;
    self._db.on("timeout", function() {
      self.ready = false;
      self._db.close();
      console.error("mongodb connection timeout.");
      self.initialise(resourceConfig);
    });
    self._db.on("close", function(err) {
      console.error("mongodb connection closed: ", err === undefined ? "timeout" : err.message);
      self.ready = false;
      self._db.collection("Nope").findOne({ _id: 0 }, { _id: 0 }, function() {
        console.error("mongodb connection is back");
        self.ready = true;
      });
    });
  }).catch(function(err) {
    console.error("mongodb connection failed:", err.message);
    setTimeout(function() {
      self.initialise(resourceConfig);
    }, 5000);
  }).then(function() {
    var resourceName = resourceConfig.resource;
    var collection = self._db.collection(resourceName);
    self._createIndexesForRelationships(collection, self.relationshipAttributeNames);
    self.ready = true;
  });
};

Handling the timeout is the right thing to do. I'll look into creating a PR to include this. Thank you for your report.


Clab shouldn't change dir permissions for /home/admin of SR Linux

Can you explain in more detail what the issue is?

/home/admin directory on srlinux container running in clab is owned by root. And it should be admin owned


HELP

I injected the dll file with process hacker and pressed insert in menu but nothing happen. Wut to do now?

It might have been your anti virus. Try disabling it before injecting, you can enable it right after the menu pops up. If not you can try another injector like ExtremeInjector with manualmap and secure mode.

Since the last update, process hacker can't inject osiris into CS:GO anymore. You should have used loadlib injector instead.

Thank you guys.. it worked by changing injector


momentjs.cn resource error

fonts.useso.com has stop the service, you may change to cdn.baomitu.com. Or you may can use the fonts directly.

That site appears to belong to a third party.


Add support for python 3.13

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

Project coverage is 100.00%. Comparing base (c0d221c) to head (62e8769).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #314   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          178       178
  Branches        12        12
=========================================
  Hits           178       178

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


[Snyk] Upgrade @typescript-eslint/parser from 7.7.0 to 7.8.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @typescript-eslint/parser from 7.7.0 to 7.8.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 22 versions ahead of your current version.

The recommended version was released on a month ago.

Release notes

Package name: @typescript-eslint/parser

7.8.0 - 2024-04-297.8.0 (2024-04-29)
🚀 Features

rule-tester: assert suggestion messages are unique (#8995)
typescript-estree: add maximumDefaultProjectFileMatchCount and wide allowDefaultProjectForFiles glob restrictions (#8925)

🩹 Fixes

eslint-plugin: [no-unsafe-argument] handle  tagged templates (#8746)
eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check (#8717)
eslint-plugin: [consistent-type-assertions] handle tagged templates (#8993)
eslint-plugin: [no-unsafe-return] handle union types (#9001)
eslint-plugin: [no-unused-vars] clear error report range (#8640)
utils: export ESLint backwards-compat functions (#8976)

❤  Thank You

auvred @ auvred
Josh Goldberg ✨
jsfm01 @ jsfm01
Kim Sang Du @ developer-bandi
YeonJuan @ yeonjuan

You can read about our versioning strategy and releases on our website.

7.7.2-alpha.13 - 2024-04-28

7.7.2-alpha.12 - 2024-04-28

7.7.2-alpha.11 - 2024-04-27

7.7.2-alpha.10 - 2024-04-26

7.7.2-alpha.9 - 2024-04-26

7.7.2-alpha.8 - 2024-04-26

7.7.2-alpha.7 - 2024-04-26

7.7.2-alpha.6 - 2024-04-26

7.7.2-alpha.5 - 2024-04-25

7.7.2-alpha.4 - 2024-04-24

7.7.2-alpha.3 - 2024-04-23

7.7.2-alpha.2 - 2024-04-23

7.7.2-alpha.1 - 2024-04-23

7.7.2-alpha.0 - 2024-04-22

7.7.1 - 2024-04-227.7.1 (2024-04-22)
🩹 Fixes

eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment (#8800)
eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type (#8809)
eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish (#8559)
eslint-plugin: [no-for-in-array] refine report location (#8874)
eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type (#8912)

❤  Thank You

Abraham Guo
Kirk Waiblinger @ kirkwaiblinger
YeonJuan @ yeonjuan

You can read about our versioning strategy and releases on our website.

7.7.1-alpha.5 - 2024-04-20

7.7.1-alpha.4 - 2024-04-20

7.7.1-alpha.3 - 2024-04-19

7.7.1-alpha.2 - 2024-04-19

7.7.1-alpha.1 - 2024-04-19

7.7.1-alpha.0 - 2024-04-15

7.7.0 - 2024-04-157.7.0 (2024-04-15)
🚀 Features

eslint-plugin: replace no-new-symbol with no-new-native-nonconstructor (#8895)
typescript-estree: add defaultProject for project service (#8815)

❤  Thank You

Dave @ reduckted
Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

    from @typescript-eslint/parser GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing, addressed in #670


[New Port Request]

Library name:Cachelot
Library description:a fast c++ cache library
Source repository URL:https://github.com/cachelot/cachelot
Project homepage (if different from the source repository):https://cachelot.io/index.html
Anything else that is useful to know when adding (such as optional features the library may have that should be included):https://cachelot.io/index.html

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.


Failed to get resource when kind is in two different api versions

Description
I am using Traefik for routing, and they recently switched from traefik.containo.us to traefik.io as their apiVersion. The CRDs are currently duplicated if you install Traefik v2, with a recommendation that users use traefik.io instead of traefik.containo.us (the latter is removed in the upcoming Traefik v3). That said, it looks like helm dashboard ignores the apiVersion of the object and instead just looks up the resource under the first matching CRD.
The /resources endpoint returns the correct apiVersion on the resource, so I'm guessing it could be possible to send that along when fetching the resource vs just depending on the Kind to be unique.
Screenshots

Additional information
No response

@josegonzalez Can you compose me a detailed instruction on how to reproduce this in my cluster? Which charts of which version to install?

If you setup a server via k3s as shown here, you'll get the same CRD under two different groups. Then I would create a helm chart with something like the below as a template:
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: redirect-to-https
spec:
  redirectScheme:
    scheme: https
    permanent: true

The helm dashboard will then query the CRD with the wrong apiVersion (traefik.containo.us/v1alpha1).
This is probably also an issue for anyone upgrading across CRDs, where the version increases but the older CRD might be used instead.


Remove old Android workaround

This pull request removes an old workaround that prevents the focus condition to work properly on contemporary devices. On pointer event devices, the interaction-options.html example does not allow page srcolling when touching the map, even when the map does not have the focus.

https://257-4974939-gh.circle-artifacts.com/0/examples/interaction-options.html shows the fixed bahavior on touch devices.


Add Limited Reviewers group with delayed reviews

Fixes #1443

Just a minor point but the way I've been linking to issues is not to mention the issue number in the commit but to mention it like "Fixes #1443" in the description of the pull request. This accomplishes a few things. First, it doesn't create multiple links to each commit when you rebase them on master after fixups. Secondly, it makes a clickable link in the PR description which is nice for reviewers.

There are a lot of test failures, most if not all of them are due to the migration that hasn't run. How to mitigate?

There are a lot of test failures, most if not all of them are due to the migration that hasn't run. How to mitigate?

Migrations aren't run on the test suite. What you would typically do is add the group in the setUp() of the test like:
Group.objects.create(...)
GroupUser.objects.create(...)

However, I think you'll get a lot of passing tests after you switch to GroupUser.objects.filter(group__name='Limited Reviewers', user=...) because that won't rely on the group object existing (which is unimportant for tests that do not cover the group logic).

r- so far because of the missing tests. Let me know if you need help on the tests. The most important logic to cover in a test is limiting the queue results.

Added tests.

All checks have passed \o/

Could you do a follow-up commit to clean things up? I think it's good to go otherwise so I'm merging it to make the tag.


fix(client): inline schema

Sorry I don't know the best way to contribute to the PR but I'm very excited about it!
I ran some of the failing pipeline tests locally and was able to fix some by changing a line in binaryEngine.test.ts
current
datamodelPath: path.join(__dirname, './runtime-tests/blog/schema.prisma'),

to
datamodelPath: '',


WIP: Dashboard View

WIP yet, this is the work towards building a Dashboard view for the components of the circuit maintenance.
Outstanding:

[ ] Complete planned dashboard metrics
[ ] Integrate functions/methods into Capacity Metrics

I think this is a great addition to the plugin and agree with @glennmatthews  that it would make a good plugin landing/home page.

I'm currently waiting on #195 before I continue on.

I create a CM for the next 30 Days, and is not showing up in the dashboard (this circuit is not associated to a Device)

This one looks like it is a caching issue. I was able to replicate it in my environment. I was able to get it to show up by canceling out of the development environment and restarting it. Showed up immediately.

Resolved the division by zero as well, it stemmed from a query with 0 results in the list.

Accessing the overview view with a CircuitMaintenance without circuits, trigger a ZeroDivisionError exception
ZeroDivisionError at /plugins/circuit-maintenance/maintenance/overview/
division by zero
Request Method:	GET
Request URL:	http://localhost:8080/plugins/circuit-maintenance/maintenance/overview/
Django Version:	3.2.15
Exception Type:	ZeroDivisionError
Exception Value:
division by zero
Exception Location:	/source/nautobot_circuit_maintenance/views.py, line 69, in setup
Python Executable:	/usr/local/bin/python
Python Version:	3.7.13
Python Path:
['/source',
 '/usr/local/lib/python3.7/site-packages/git/ext/gitdb',
 '/source',
 '/usr/local/bin',
 '/usr/local/lib/python37.zip',
 '/usr/local/lib/python3.7',
 '/usr/local/lib/python3.7/lib-dynload',
 '/root/.local/lib/python3.7/site-packages',
 '/usr/local/lib/python3.7/site-packages',
 '/source',
 '/usr/local/lib/python3.7/site-packages/gitdb/ext/smmap']
Server time:	Wed, 24 Aug 2022 07:09:54 +0000

Resolved.

"Average Duration of Maintenances" is always 0? I added some future circuit maintenances, and always show as 0

Corrected. The seconds property was initially giving good results. But the proper method to use was total_seconds() to get the duration within seconds on a timedelta object.

Done @chadell


Missing letters

There are the W's missing in fraktur and in the Double-Struck style.
Kapital mathfrak w : 𝔚
Small mathfrak w:  𝔴
Double-struck capital: 𝕎
Small: 𝕨

Fixed


feat: enable release of binaries for of s390x architecture

This change enables the release of admin-helper binaries for the s390x architecture, which is a prerequisite for CRC to run on this platform.

@nestoracunablanco Hi, as of now we are not building crc binary for s390x since we don't have infra to test it and also engineer to maintain it. I think you are building it yourself crc on this arch, you can do that for this library also and use it accordingly?

@praveenkumar, thank you so much for your response! I'll go ahead and close this PR now and revisit it with you at a later point if needed.

I am reopening this one because @nestoracunablanco wants to put effort on that side (infra + testing) and we will schedule a meeting after holiday.

I am reopening this one because @nestoracunablanco wants to put effort on that side (infra + testing) and we will schedule a meeting after holiday.


[Feature Request] Add PatchFusion Depth Estimation

Would be cool to have this added:
https://github.com/zhyever/PatchFusion
I've been running it locally on it's own. Would be nice to have it incorporated into this extension.
https://huggingface.co/spaces/zhyever/PatchFusion
However a couple of modifications may need to be made to get it to work, same ones I had to make. Found here:
https://github.com/Fannovel16/comfyui_controlnet_aux/issues/2#issuecomment-1763579485
to fix this: file /comfyui_controlnet_aux/src/controlnet_aux/zoe/zoedepth/models/base_models/midas.py replace line 176 with

return nn.functional.interpolate(x, (int(height), int(width)), mode='bilinear', align_corners=True)

file /comfyui_controlnet_aux/src/custom_midas_repo/midas/backbones/beit.py replace line 47 with

new_sub_table = F.interpolate(old_sub_table, size=(int(new_height), int(new_width)), mode="bilinear")

The line location was different on mine and so was the path to the two files but their paths showed up in the errors that came up. Once I found this solution, it was simple to implement.

I too hope somebody can implement this :)

Do you have an estimate on your local memory usage? I was kind of hoping they would make some memory optimisations before we implemented it. I'm thinking about doing some cloud gpu stuff next week so might have some time to implement it.

Do you have an estimate on your local memory usage? I was kind of hoping they would make some memory optimisations before we implemented it. I'm thinking about doing some cloud gpu stuff next week so might have some time to implement it.

Running it right now, Task Manager is showing Python using 1.7GB of RAM.

That can be right while the algorithm is running? I'm pretty sure it should be at least 10GB.

It BRIEFLY got up to 2.4GB, but as you can see from this screenshot, my GPU is maxed out while the system RAM is at 1.7GB.

Oh no that's the RAM I meant the VRAM. I'll just try with a big gpu.

Oh no that's the RAM I meant the VRAM. I'll just try with a big gpu.

 I've got MSI afterburner installed but I'm not sure if I can use that for this since it's not using a graphics API window. My GPU is a 4090 with 24GB of VRAM.

Ok, the first image is without it running, my GPU VRAM is at 11GB. Then with it running it goes up to just over 15GB, then briefly at the end it jumps up to just over 20GB. So you were correct. Around 10GB of VRAM it seems.

Nice thank you!

https://github.com/graemeniedermayer/stable-diffusion-webui-normalmap-script/tree/patchfusion
I have the start of it here but there's a uprising amount of compatibility issues.


Consolidate API information into yaml file

What type of PR is this?
Add one of the following kinds:

cleanup
documentation

What this PR does / why we need it:

Include missing documentation from md files into yaml file
Remove deprecated files under API_documentation folder
Fix UML image path

Which issue(s) this PR fixes:

Fixes (https://github.com/camaraproject/NumberVerification/issues/55) UML link in YAML is faulty
Fixes (https://github.com/camaraproject/NumberVerification/issues/54) Add documentation into API definition before release
Special notes for reviewers:
N/A
Changelog input
N/A
Additional documentation
N/A

Just one thing before we approve (or perhaps I need to create a new PR?).
In the current Yaml (3.0.3) reference is made to a number of security mechanims without explaination.
In the "resources and operations overview" a reference is made to "3-legged token".
The sequence diagram refers to "standard OAuth2 Authorization Code grant".
In the "securitySchemes" a reference is made to OIDC "three_legged: type: openIdConnect openIdConnectUrl: https://example.com/.well-known/openid-configuration".
It is difficult for the consumer / user to understand what security mechanims are recommeded. Is is OIDC (and if so do we recommend the use of identity tokens?), will OAuth access token suffice?
A specific directive for this API would help (perhaps the flows can be updated?).

Just one thing before we approve (or perhaps I need to create a new PR?).
In the current Yaml (3.0.3) reference is made to a number of security mechanims without explaination.
In the "resources and operations overview" a reference is made to "3-legged token". The sequence diagram refers to "standard OAuth2 Authorization Code grant". In the "securitySchemes" a reference is made to OIDC "three_legged: type: openIdConnect openIdConnectUrl: https://example.com/.well-known/openid-configuration".
It is difficult for the consumer / user to understand what security mechanims are recommeded. Is is OIDC (and if so do we recommend the use of identity tokens?), will OAuth access token suffice?
A specific directive for this API would help (perhaps the flows can be updated?).

@fernandopradocabrillo can you please provide fixes according to @ECORMAC comment? thx! (have OpenId connect instead of three-legged)

Hi Again,
I would be more inclined to state what we originally stated (or at least I think we originallly stated??) - we go with 3-legged (using access tokens). However this may now be touching upon discussion ongoing in the identity&Consent group (#55).

Just one thing before we approve (or perhaps I need to create a new PR?).
In the current Yaml (3.0.3) reference is made to a number of security mechanims without explaination.
In the "resources and operations overview" a reference is made to "3-legged token". The sequence diagram refers to "standard OAuth2 Authorization Code grant". In the "securitySchemes" a reference is made to OIDC "three_legged: type: openIdConnect openIdConnectUrl: https://example.com/.well-known/openid-configuration".
It is difficult for the consumer / user to understand what security mechanims are recommeded. Is is OIDC (and if so do we recommend the use of identity tokens?), will OAuth access token suffice?
A specific directive for this API would help (perhaps the flows can be updated?).

@fernandopradocabrillo can you please provide fixes according to @ECORMAC comment? thx! (have OpenId connect instead of three-legged)

@DT-DawidWroblewski  Yes! I was gonna do the same as in Sim swap and create a different PR, but I didn't have time on friday.
I will create a new one and cover these comments


[Simulator] Resize graph with the window

Resize the graph horizontally & vertically
Video:
https://github.com/bancorprotocol/carbon-app/assets/8143464/0c0a9751-e8ef-4797-b586-32cba0c87248

[ ] for screen heigh below min height, you cannot scroll to view the bottom of the chart
https://github.com/bancorprotocol/carbon-app/assets/40430285/0e15c0ec-f5f6-4cb8-a494-c9ca1a630628

I've open an issue for that: https://github.com/bancorprotocol/carbon-app/issues/1052

I noticed some flickering when toggling between summary and animation tabs.
https://github.com/bancorprotocol/carbon-app/assets/7262066/cfd11351-75ef-476d-a541-e54c64f31b95


Usage of remote:vllm

What I understand about this is actually deploy a model (e.g Llama3.1-70B-Instruct) by using 'vllm serve Llama3.1-70B-Instruct ... ' and then config the url and model name to llama-stack for LLM capability, but it seems that there is not much information about this part on doc and I would like to ask about what can I do once I finished deployment of my model? Thanks

I would agree with this in general. This might even be the solution for everyone wanting AMD support (or Gaudi or TPU). This gives you maximum flexibility to serve the model with speculative decoding, multi-node, quantization, lora adapters, and more. But it is very much undocumented and several bugs need to be fixed before it is ready for general use. I am trying to pave the way so that this is supportable. With remote vllm, you can offload the inference to a beefy machine and run the API server on your laptop to develop software.


Disqus threads for http and https sites separate

Is there a way to have the https site forward to the http site? I've just noticed that if people comment on a post reached using the http address and others do the same using the https address, the threads only show up on one or the other, as if there were two different sites.
Example: this post http://bewuethr.github.io/installing-fltk-133-under-visual-studio/ and the same under https, https://bewuethr.github.io/installing-fltk-133-under-visual-studio/, has two different comment threads.

This is a possible solution:
https://gist.github.com/konklone/9968713

That's the exact problem, thanks @Koxzi95. I'll use that – maybe Jekyll Now could add it to the default template?

It would depend on how the site is configured. For example I cannot access my site with: https://koxzi.me because of the hosting.

I don't use a custom domain name, so it should work, but good to know that it doesn't work with custom ones.

Glad you got a fix for this, @bewuethr.
I'm confused as to why some people were going to an https:// link on your site at all? I've never ran into that problem. Wondering if it's an issue that many people are having?


Metric

I am assuming that the following metric is filtered and the average of head and tail correct?

Thanks!

Correct.


add 'kubectl cert-manager version'

What this PR does / why we need it:
For debugging purposes, determine what cert-manager version we are using.
This logic can be reused for uninstalling/ upgrading in later PRs.
Release note:

add the deployed cert-manager version to 'kubectl cert-manager version' command

/ok-to-test

/retest

/retest

Doing a bit of a drive-by here, but how come this PR involves committing every single version of cert-manager's deployment manifests into the repository at HEAD? 🤔 can we not use something like labels on certain resources to determine the version installed, rather than a complete comparison of everything? This adds almost 1 millions lines of code to the repo 😅 (and also it isn't clear to me how we'd actually add the newest YAML files when performing a release, e.g. prior to tagging a release, how do we commit these generate YAML files as the tag does not exist yet?)

Doing a bit of a drive-by here, but how come this PR involves committing every single version of cert-manager's deployment manifests into the repository at HEAD? 🤔 can we not use something like labels on certain resources to determine the version installed, rather than a complete comparison of everything? This adds almost 1 millions lines of code to the repo 😅 (and also it isn't clear to me how we'd actually add the newest YAML files when performing a release, e.g. prior to tagging a release, how do we commit these generate YAML files as the tag does not exist yet?)

I added the release manifests only for testing, the hack/scrape-release-manifests.sh file downloads the manifests from github based on the tags. Maybe, it should be .gitignored; but that means that there will be a lot of github api requests (eg. when doing CI).

/kind feature


Add secondary telemetry to MessageProvider

Test plan
run extension in debug mode
check test eventlogs on dotcom for event emission
check bigquery for event reception

Moved source in metadata into Feature and moved contextSummary into metadata from privateMetadata