[Issue-1283] - adds export/import profile functionality to TP and basically just lev…

…erages exisitng export/import server side functionality but ports it to the API namespace.
fixes #1283

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/705/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/706/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/718/
Test PASSed.


Update the pollSince time based on latest activation start time

Change the pollSince time for each loop by basing it on the latest Start time seen in activation result
See #390 for background details
Testing Approach
While the fix is small it was tricky to validate the change. This PR add a test HTTP rever proxy which is used to intercept the calls between the cli client and the controller. The test then intercepts the request to check if since time gets changed or not

@csantanapr @rabbah @dubee Please review

Hi, about this change: https://github.com/apache/incubator-openwhisk-cli/pull/396/files#diff-ad777399e121d471d84d4fd5bf456bceR390
@chetanmeh I believe it affects nested cloud functions. I’m experiencing activation logs missing while running activation poll and invoking a cloud function that triggers others. Actually, I can see inner cloud functions logs but never the logs of the main function than executed them.
We’ve discussed this with @mdeuser (thanks him for pointing me to this PR). I’ve reported the issue before here: https://ibm-cloud-tech.slack.com/team/UGVBSBWGH)

the activation polling scenario in question is:

activation A starts and continues to run
activation B starts and quickly completes
activation poll reports B completed and updates the since time
activation A completes
activation poll does not report activation A as being completed.
i believe the GET /activations api's since parameter is based off the start time, not the end time...  but @rabbah will know for sure

It’s possible to miss activations because there’s no guarantee the activations are committed to the datastore in order. The cursor is the cli advances based on the last fetched activations. The polling doesn’t back fill.

@rabbah - thanks fr the input.  does the backend use the activation start time or end time when processing the activation list since parameter?
while not a guarantee, i'm thinking the activation order will likely be maintained most of the time - especially for activations completing in sequence and seconds apart.  a polled-for, long running sequence action will probably run into this same issue.

The activations in the database are indexed using the activation start time. The controller queries the database using the start key equal to the since parameter, and the end key equal to the upto parameter.


Translate one sentence into Japanese and fix minor errors on setup/best-practices/multiple-zones

This PR contains two small fixes:

Translate the first sentence which remains English
Fixes and improves several errors in the translation

/assign @nasa9084

/lgtm

/approve


Show description when throwing exceptions because of no invocations

This resolves #380
Before:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '** Cannot handle or verify invocations. This error usually occurs when a mock object is used after stopMocking has been called on it. In most cases it is not necessary to call stopMocking. If you know you have to, please make sure that the mock object is not used afterwards.'

After:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '** Cannot handle or verify invocations on OCMockObject(CLLocationManager). This error usually occurs when a mock object is used after stopMocking has been called on it. In most cases it is not necessary to call stopMocking. If you know you have to, please make sure that the mock object is not used afterwards.'

This deserves a test to validate the exception message. A number of tests already trigger this exception:
Test Case '-[OCMockObjectInternalTests testRaisesWhenAttemptingToUseAfterStopMocking]' started.
Test Case '-[OCMockObjectInternalTests testRaisesWhenAttemptingToUseAfterStopMocking]' passed (1.926 seconds).
Test Case '-[OCMockObjectInternalTests testRaisesWhenAttemptingToVerifyInvocationsAfterStopMocking]' started.
Test Case '-[OCMockObjectInternalTests testRaisesWhenAttemptingToVerifyInvocationsAfterStopMocking]' passed (1.684 seconds).
Test Case '-[OCMockObjectVerifyAfterRunTests testThrowsWhenVerificationIsAttemptedAfterStopMocking]' started.
Test Case '-[OCMockObjectVerifyAfterRunTests testThrowsWhenVerificationIsAttemptedAfterStopMocking]' passed (2.046 seconds).

So updating one or more of those tests to validate the message seems like a good way to ensure this doesn't regress.

Will update, thanks!

Updated, maybe good to go now?

IMO yes but I don't own that.

To be honest, I'm hesitating to merge this. On the one hand I see the value. On the other hand, hopefully tests are reproducible and it's not hard to set a breakpoint on the exception; something you'll likely want to do anyway when figuring out how the mock is used, right?

@erikdoe I'm requesting this because in my recent migration from OCMock 3.4 to OCMock 3.5, I have seen hundreds of tests failing in a large codebase due to all the exceptions. It's very hard to go through one by one and figure out which object is not mocked properly. So I added it locally and it indeed saved me a lot of time.
Given this, I feel this brings value to user, and would be good to be merged :)

FWIW I second this. The more context a failure message can give the better. For individual developers debugging inline / reproducing at desk is easy, but for teams with screeners / large CI infrastructures the additional context can help a lot when trying to correlate failures.

Thanks @erikdoe!


Native epoll channels/sockets take longer to shutdown/close?

This is neither a bug report nor feature request. I figured I use Github issues to solicit peoples experience and knowledge about Netty's native epoll transports. We've been running Finagle with native epoll (on Linux) for quite a while internally and finally decided to switch our OSS version to it.
To our surprise, switching over to a native epoll caused out showdown tests to fail. Turns out, our previous graceful timeout (order of a couple of seconds) didn't do it for native epoll socket/channel (shutting down an HTTP server running with epoll=true). We had to bump our timeouts significantly to ensure the test passes: think of going from 2s to 30s.
Before we start digging into why closing epoll channels (server channels if that matters) takes so much longer I decided to ask around if somebody has seen this before. Any pointers would be totally appreciated!
I will try to post with thread with the updates should we know more.

I am not aware of anything like this @vkostyukov

@vkostyukov did you find out anything ?

@normanmaurer Nope - we haven't really made any progress there yet. We've only seen this problem in our tests and were keeping an eye on complains coming from out users. Nobody really complained about slower shutdown yet thus we haven't really invested into it.

k ok :)

@vkostyukov would be interesting to know if #9616 resolves this (assuming it still happens for you).

I think this should be fixed by #9616 . Closing.


[DO NOT MANUAL MERGE] Release Qualification

Trigger release qualification jobs
none

@silverdev: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-no_auth.sh
1313104f6b602ff892905b7739123dd7cc761f45
link
/test daily-e2e-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@silverdev: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-no_auth.sh
1313104f6b602ff892905b7739123dd7cc761f45
link
/test daily-e2e-rbac-no_auth

prow/daily-e2e-rbac-no_auth-default.sh
1313104f6b602ff892905b7739123dd7cc761f45
link
/test daily-e2e-rbac-no_auth-default

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Asset files are not loading after a fresh Laravel Sail installation on MacOS

Laravel Vite Plugin Version: 0.2.4
Laravel Version: 9.19.0
Node Version: 16.15.1
NPM Version: 8.12.1

Description:
After a fresh installation of Laravel Sail and Laravel Breeze, css and js files are not loading in the browser
Steps To Reproduce:
curl -s "https://laravel.build/example-app" | bash

cd example-app

./vendor/bin/sail up

sail composer require laravel/breeze

sail artisan breeze:install

sail npm install && sail npm run dev

vite v2.9.13 dev server running at:

Local:    http://localhost:5173/
Network:  http://<IP_ADDRESS>:5173/

When I visit localhost/login, the console shows "Failed to load resource: bad URL" and these are the locations where the browser is looking for the resources:
http://<IP_ADDRESS>:5173/resources/css/app.css
http://<IP_ADDRESS>:5173/@vite/client
http://<IP_ADDRESS>:5173/resources/js/app.js
This is how the login page looks like

me too

curl -s "https://laravel.build/example-app" | bash
cd example-app
./vendor/bin/sail up
sail composer require laravel/breeze
sail artisan breeze:install
sail npm install && sail npm run dev

I've just followed these steps verbatim and the site is running as expected on my MacOS machine...

Can you confirm the following:

You are running on MacOS (as discussed on Twitter).

The vite.config.js file contains only the following...

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel([
            'resources/css/app.css',
            'resources/js/app.js',
        ]),
    ],
});

Your docker-composer.yml contains the following...

        ports:
            - '${APP_PORT:-80}:80'
            - '${VITE_PORT:-5173}:${VITE_PORT:-5173}'

You are not running npm run dev on your local machine as well as in Sail? i.e. two running instances.

I can confirm all of the above. Also, it appears the issue is limited to Safari. I tested the same address on Firefox and Chrome and the assets load fine. I haven't tested on Edge but I'm guessing it will work as well.

Another interesting development. When I turn off "Prevent cross-site tracking" in Safari's privacy preferences. The error message changes to this

I'm unable to replicate this in Safari. Everything is working as expected in Safari on my end. Toggling "Prevent cross-site tracking" on / off also has no impact for me.
Are you accessing localhost over HTTP or HTTPS?

I'm accessing localhost over HTTP. I don't know if it's relevant but I'm using an M1 Mac mini. Although, blaming it on apple silicon it's quite a leap.

The only way I could get things to work on Valet/Safari/SSL is with the following.
It would be nice not to have to explicitly set a domain path however.
import {
    defineConfig
} from 'vite';
import laravel from 'laravel-vite-plugin';

const domain = "test.test";
const homedir = require("os").homedir();

export default defineConfig({
    plugins: [
        laravel({
            input: "resources/js/app.js",
            ssr: "resources/js/ssr.js",
        }),
    ],
    server: {
        https: {
            key: homedir + "/.config/valet/Certificates/" + domain + ".key",
            cert: homedir + "/.config/valet/Certificates/" + domain + ".crt",
        },
        host: domain,
        hmr: {
            host: domain,
        },
    },
});

Hi @timacdonald,
I'm getting very similar issues to the other users, and I'm running on an Intel Mac, with Docker Desktop 4.10+
As I prefer to use MariaDB over MySQL, I used the steps:
curl -s "https://laravel.build/l9-vite?with=mariadb,redis,memcached,meilisearch,minio,selenium,mailhog" | bash
cd example-app
./vendor/bin/sail up
sail composer require laravel/breeze
sail artisan breeze:install
sail npm install && sail npm run dev

The vite.config.js file reads:
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel([
            'resources/css/app.css',
            'resources/js/app.js',
        ]),
    ],
});

Docker compose file docker-compose.yml has the lines:
        ports:
            - '${APP_PORT:-80}:80'
            - '${VITE_PORT:-5173}:${VITE_PORT:-5173}'

Tested using Chrome, Safari, Edge and Firefox.

http://localhost:5173

Safari: BLANK
Chrome: No web page was found for the web address: http://localhost:5173/
Firefox: see Chrome
Edge: see Chrome

http://localhost

Safari: Default welcome screen
Chrome: Default welcome screen
Firefox: Default welcome screen
Edge: Default welcome screen

http://localhost/register

Safari: No assets loaded, as per @tuto1902
Chrome: Assets load
Firefox: Assets load
Edge: Assets load

On everything except Safari, I've managed to view the content as it should be for the default layout.
I use multiple browsers for testing to make sure that things are as I expect, so the fact that Safari is failing for some reason is a mild concern.
More of a concern is also that the http://localhost:5173/ is not rendering anything.
I have had no problems in the past with Mix.

Facing a similar issue, blank page on port 3000.
I'm not using docker.
npm run dev

UPDATE:
If I run php artisan serve on another terminal + npm run dev and I access http://<IP_ADDRESS>:8000/ I get HMR working when I change any .vue file content :)

@AdyGCode @Fedeorlandau Accessing the Vite dev server directly (http://localhost:3000 or http://localhost:5173, depending on whether you're running it inside Sail) is expected to return a blank screen at the moment as that's just where Vite serves assets for HMR. This has been improved with #57 as we'll now be outputting a default help screen to instruct users to run a dev server for Laravel.

@AdyGCode @tuto1902 are either of you utilising and ad blocking plugins or anything? Can you confirm if the issue persists if you have Safari in a "vanilla" state with no extra plugins or configuration?

@timacdonald

I'm not running valet at all.
Also, not running any other web services other than using docker.
Only have the Laravel site running inside docker.
Safari is in 'vanilla' mode - same result
Safari, reset the experimental features - same result
Played with the settings as requested, including clearing cache between each test - no effect

I have little snitch running, but turned off filtering as a test, no effect.
HMR mode runs with assets compiled, the pages render as expected.

@jessarcher
That's good to hear - someone who comes straight from mix to vite would not be familiar with that little idiosyncrasy.
May I suggest adding the message to the npm command results as well?

@timacdonald
Tim, I modified the URIs for the vite on the rendered page to localhost from <IP_ADDRESS> on Safari, and it rendered.
I know this as I had purposely published the Breeze assets and modified the Login page.

@AdyGCode @tuto1902 are either of you using any ad blocking plugins or anything in Safari?
Could you confirm that the problem only exists in HMR mode? i.e. kill the dev server and run npm run build.
If you have valet installed could you try runnning valet stop and confirm the issue persists.
And finally, can you confirm if the issue persists when you have Safari in a "vanilla" state with no extra plugins or configuration? Please also try resetting the experimental features...

and then, if you have space, could you also try playing with these settings in Safari to see if you can make anything happen / get any further meaningful information from the console / requests.

After trying out your suggestions:

The issue only exists on HMR mode. After killing the dev server and running sail npm run build, the assets load without problem
I have no extensions running on safari
I Safari on vanilla mode (reset experimental features to default) and it had no effect. Same issue, no changes
I Tried enabling/disabling all the suggested develop features (disable images, styles, etc). Same issue, no changes

@timacdonald A small development. Just like @AdyGCode, if I manually change the href value of the link in the head from <IP_ADDRESS> to localhost (Ctr+Cmd+C > right click > edit attribure). The page suddenly loads fine.

@tuto1902, @jessarcher, @timacdonald
OK - I have found a workaround thanks to #42 plus the Spatie/Freek blade refresh settings.
Edited the vite.config.js file, and added the following before the 'plugins' settings:
    server: {
        hmr: {
            host: 'localhost',
        },
    },

Also, added  the Freek/Spatie 'fix' for auto-reload on blade file updates, in the plugins array, after the laravel entry:
     {
            name: 'blade',
            handleHotUpdate({ file, server }) {
                if (file.endsWith('.blade.php')) {
                    server.ws.send({
                        type: 'full-reload',
                        path: '*',
                    });
                }
            },
        }

Full Code for the vite.config.js is:
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    server: {
        hmr: {
            host: 'localhost',
        },
    },
    plugins: [
        laravel([
            'resources/css/app.css',
            'resources/js/app.js',
        ]),
        {
            name: 'blade',
            handleHotUpdate({ file, server }) {
                if (file.endsWith('.blade.php')) {
                    server.ws.send({
                        type: 'full-reload',
                        path: '*',
                    });
                }
            },
        }
    ],
});

Results are the page rendering as expected in Safari (logo colour changed in this test):

@AdyGCode I tried your workaround but still doesn't work for me. I even tried setting server.host to localhost, which changed the address from <IP_ADDRESS> to localhost but the resources didn't load, which is all kind of confusing since changing the value manually in the rendered page to localhost actually loads the asset

s

This is a small video to demonstrate what I mean
https://user-images.githubusercontent.com/2152532/178182547-29438cba-8177-46ce-937a-35c021464081.mov

@AdyGCode I tried your workaround but still doesn't work for me. I even tried setting server.host to localhost, which changed the address from <IP_ADDRESS> to localhost but the resources didn't load, which is all kind of confusing since changing the value manually in the rendered page to localhost actually loads the assets

@tuto1902
I know I'll probably be teaching you to suck eggs, but did you sail down and then sail up after the changes - I tend to do that if I am not sure if something will truly pick up changes correctly.
The server.host (from what I read and recall) will not help when working with a sail/docker container - I believe the server.host needs to be <IP_ADDRESS> for docker/containers. The host, in this case, is the HMR (hot module reload?) and I set that to localhost and that seemed to work for me.
I also did force my cache to be cleared in Safari [CMD+OPT+E]. May also need to clear the Laravel cache as well [sail artisan cache:clear].

Ok, so I think this is just a problem with my Mac mini, or the Mac OS version, or the version of Safari, or maybe an ancient curse passed down by generations... In any case, I just ran my own steps to reproduce in an old MacBook Air with Mac OS Big Sur and sure enough, everything worked fine out of the box.

That happens, and given my configuration is a bit wild, I was wondering the same.
If you get the chance to re-build the Mini then you may find it clears up the issue.
If not it, you have your answer for now.

@timacdonald if there's no objection from anyone else, I think we can close this issue. 🤷🏻♂

@timacdonald  and @tuto1902 - No problems closing, but it may be worth adding a note that in some situations, the HMR option under server may be required.


[Feature] Supports llama.cpp

Is your feature request related to a problem? Please describe.
No response
Solutions
Provide instructions on how your models might be converted to ggml and used with https://github.com/ggerganov/llama.cpp
Additional context
llama.cpp is a fast CPU-optimized inference tool which supports various (LLaMa and non-LLaMa based models)

+1

There might be more information in ggml, since they have conversion scripts that can convert model weights from HuggingFace format to ggml format, located in examples/gpt-j and examples/gpt-2.

hey @PenutChen, did you have a successful try?  some keys in config.json required for gpt-j did not exist in  config.json of chatglm, so error occured when writing data info into ggml-model-f16.bin:
fout.write(struct.pack("i", hparams["n_embd"]))
fout.write(struct.pack("i", hparams["n_head"]))
fout.write(struct.pack("i", hparams["n_layer"]))
fout.write(struct.pack("i", hparams["rotary_dim"]))

do you know what are coresponding keys in config.json of chatglm? seems the model format is not h5...

this feature has supported in https://github.com/MegEngine/InferLLM

Now llama.cpp has gpu support, will chatglm-6b continue to be updated to support gpu inference？

+1 I think it's useful because I find that the current quantization int4 somehow decrease the inference speed on my GPU, while I always see speed improvement with llama.cpp quantization

Maybe you can try https://github.com/li-plus/chatglm.cpp. It's written in the same way as llama.cpp based on GGML. Quantization does help to improve inference speed.

@li-plus  Great thing, is there a plan to support gpu inference？

@li-plus Great thing, is there a plan to support gpu inference？

Sure there is. I'll make it infer-able on a consumer GPU.


Use CONF_RECIPIENT for default recipient in config

Description:
Use the new deprecated vol validator to replace ATTR_TARGET with CONF_RECIPIENT in tpklink_lte.
Breaking Change: target has been deprecated and replaced with recipient in the tplink_lte configuration. This is a soft deprecation in this release and will automatically become a hard breaking change in Home Assistant version 0.91.0.
Related issue (if applicable): fixes #20671
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8460
Example entry for configuration.yaml (if applicable):
tplink_lte:
  - host: IP_ADDRESS
    password: SECRET
    notify:
      - name: sms1
        recipient: "+15105550123"
      - name: sms2
        recipient: "+55520525252"

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

When should we announce the breaking change? Now here, or later when we hit invalidation?

It feels like we need a new section of the release notes for future breaking changes. Because we should announce now that this migration is necessary and will be required when we hit invalidation.

if a user can postpone, he will postpone... by all means, a breaking change must be announced ASAP, and not wait for the final version.

I think we need it mentioned in every set of release notes between now and invalidation or at the very least once now and once at invalidation.

Tagged as breaking change and breaking change note added.


gmp: fix multiplier with leading zero

Fixes #286

So is it actually something which can be fixed? Not a limitation of GMP, like in the referenced issue?

@sagikazarmark In the case of issue #278, there was an example that could never be the case inside Money. Why would you want to compare non-integers? That is simply impossible with Money because Money requires the amount to be integer. We never compare non-integers.
But issue #286 is different. One should be able to multiply an amount with decimal leading zero value. As you can see in the multiply method I created a workaround the limitation of GMP.
My point with the calculators is: they are Money internals. Anything inside the calculators that causes bugs inside Money should be fixed. Every other case should be ignored.

@sagikazarmark Decimals within Money are only relevant when multiplying or with divisions. That is why I only created the workaround inside the GMP calculator for multiply and divide. Decimals are irrelevant when adding, subtracting and comparing because Money will always require integers for those methods.

@frederikbosch okay, agreed.


SSW Rules - Do you know when to use Modular Monoliths?

Partially covered by https://www.ssw.com.au/rules/modular-monoliths/.  Will consider this when adding more generic advice around 'choosing an architecture'.


Add API Sprout to new mock server section

Adds my new OpenAPI 3 mock server to the implementations list.

Just for consistency, is there a reason for having CLI / Docker as the language rather than Go ?

@MikeRalphson it wasn't clear to me whether the language should describe what a tool is written in or what language you as an end-user would use to interact with it. It might be interesting that it's written in Go, but it's really just a CLI tool anybody can easily install and run.

@MikeRalphson @darrelmiller any chance this could get merged in? Thanks :+1:

@MikeRalphson updated to show that it is written in Go now :smile:

Thanks for the contribution.


No version information shown

Goldstone should expose its version number so that bugs can be reported more accurately.
Perhaps the bottom of the page could have the current version number installed.

@lexjacobs plz branch and update base.html and login.html templates to center the Copyright statement, and left align a Version: {{ goldstone_version }} statement.

client fix pushed to saved-search-client PR as commit 4ee7cb1 "Add 'Version: {{ goldstone_version }}' to footer for login and base.html"

maybe put the details in a tooltip/hover


Updated Styled Components to 4.0.2, Babel to 7.1.2

First of all, great module, I really like using it with Styled Components!
In preparation for writing the tests with jest, it came to me, that some dependencies were
quite outdated - especially now that styled-components is @ 4.0.2.
So I did the following:

[x] updated styled-components ^3.1.5 to ^4.0.2
[x]<EMAIL_ADDRESS>to<EMAIL_ADDRESS>&<EMAIL_ADDRESS>[x] updated rollup ^0.45.2 to ^0.66.6 - and it's plugins accordingly
[x] changed rollup.config.js to newest config styles (no warnings with yarn build anymore)
[x] removed .babelrc in favor of .babelrc.js

And some smaller changes, as you can see in the commits.
With all this I wanted to:

Bump all to the latest versions
Prepare for writing the tests in jest

I tested the build process and integrated it in a gatsby page with no problems occuring.
This will prepare for:
Tackling Issue #1 - If it's at your convenience.

Thanks : ). And if they want to use the latest styled-components, they should be, cause there react / react-dom is a dev-Dependency: https://github.com/styled-components/styled-components/blob/master/package.json - so I guess, we are in the clear.

Good job @timhagn , I'm waiting this merge with trepidation :)

@aureliome Thanks : )! Did you choose the word "trepidation" for Halloween? Cause translated to German it would mean something like "anxiety", "fearfulness" or the like ^^. One never stops learning.
But @morajabi, did you already get the chance to look into merging it (or the tests in #14, for what it's worth). I'm already using the updated versions in a soon to be production environment with no issues
(putting "styled-media-query": "https://github.com/timhagn/styled-media-query#th-jest-tests" in my package.json for the time being ; ).

I'm really interested in this merge as well ! I'm using styled-components v4 with TypeScript, I'll give this branch a go in the mean time.

@timhagn Could you please change the version range like @ApacheEx commented above? Otherwise LGTM :)

For all waiting for an answer, my main workstations Motherboard crashed yesterday and I'm just trying to get back on track with my Dev-Laptop -.-
Sorry for the inconvenience, will try to resolve the requested changes as soon as possible % ).

I have removed package-lock.json and remove unnecessary blank line in .babelrc.json, now it looks good for me. Thank you a lot 🥇
p.s. @morajabi I think it's ready to merge

@ApacheEx Nice!
@timhagn Thanks a lot for the hard work, I'm excited to merge this :D

Any updates on this merge? Just asking ; ).

Nice! That's greats news on the merge and me now being a contributor. Thanks a lot, gonna use it responsibly : ). And so happy, that I now don't have to integrate my repo in my package.json ^^.

@morajabi,
I get this error after upgrading, seems github release is missing.

@ApacheEx Forgot to push the GH tags, but how does that make the build fail? I thought NPM doesn't depend on these.

Nope, it isn't only you, @ApacheEx, I just tried it and getting the same result -.-
Shouldn't there be a dist folder in the npm package, or how do you finalize the
build process, @morajabi? Hope I didn't break it % ).

Wait, I think I found the cause.

@timhagn @ApacheEx it should be fixed 🙈

yeah, works now. Thank you guys

@morajabi @ApacheEx Yup 2.1.1 is working and has a dist folder ^^. Thanks!
P.S.: What was the problem's source, if you'd indulge, @morajabi?

@timhagn Someone forgot to run yarn build before publishing 😅 (me)


feat: upgrade go-scheduler, implement db conn pooling config

Automated changes triggered by pull requestupgrades the go-scheduler to include these changes: https://github.com/catalystsquad/go-scheduler/pull/12
implements configuration to be able to override the defaults of the go-scheduler.
upgrades to go 1.20.

:tada: This PR is included in version 1.1.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Wrong screenshot

This section posted a wrong screenshot from visual studio code, which is supposed to be visual studio.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
AB#45948351

Notes:
The linked article section is:
"Open DevTools using an approach other than F12" in "Debug WebView2 apps with Visual Studio".
https://learn.microsoft.com/en-us/microsoft-edge/webview2/how-to/debug-visual-studio#open-devtools-using-an-approach-other-than-f12
There's no screenshot in that linked section.
@HO-COOH - What is the .png filename?

@mikehoffms

https://learn.microsoft.com/en-us/microsoft-edge/webview2/how-to/debug-visual-studio-images/console.png

Public preview of article section from PR 3233: bottom screenshot (Visual Studio 2022, not VS Code), along with the specific steps and screenshots that produce it:
https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/png-wv2-debug-vs/microsoft-edge/webview2/how-to/debug-visual-studio.md#debug-your-webview2-app
@HO-COOH @captainbrosset

Fixed by #3233.


Printout the whole stacktrace for CI jobs

It would be useful to have the whole stack trace of failed CI jobs
GitHub Actions (see) and Buildkite (see) set CI = true. Use the ENV["CI"] to set default VERBOSE

Locally, on 1.6, the UndefVarError didn't print the VERBOSE_MSG, however MethodError, BoundsError did.


psycopg2.DataError fails entire dbt run [postgres]

psycopg2.DataError: invalid input syntax for integer: ""

This is fixed in development. Example output:
dbt run --model one two
Found 4 models, 0 tests, 0 archives, 0 analyses, 37 macros, 0 operations

11:35:43 | Concurrency: 1 threads (target='dev')
11:35:43 |
11:35:43 | 1 of 2 START view model dbt_dbanin.one............................... [RUN]
11:35:43 | 1 of 2 ERROR creating view model dbt_dbanin.one...................... [ERROR in 0.02s]
11:35:43 | 2 of 2 START view model dbt_dbanin.two............................... [RUN]
11:35:43 | 2 of 2 OK created view model dbt_dbanin.two.......................... [CREATE VIEW in 0.01s]
11:35:43 |
11:35:43 | Finished running 2 view models in 0.22s.

Completed with 1 errors:

Database Error in model one (models/one.sql)
  invalid input syntax for integer: ""
  LINE 2:     select ''::integer as idk
                     ^
  compiled SQL at target/run/my_project/one.sql

Done. PASS=1 ERROR=1 SKIP=0 TOTAL=2


Sound level in MakeCode never reaches high values

Creating this issue here first for discussion in case there was something that has changed in CODAL to cause this.
Simple MakeCode programme to print to serial the sound level:
basic.forever(function () {
    serial.writeLine("" + (input.soundLevel()))
})

With the current MakeCode live (non-beta), using CODAL v0.2.40, it never returns a value higher that 131

Okay, I've been going back through MakeCode version and it looks like it was never possible to get values larger than 200 😱
CODAL v0.2.37 to v0.2.40, MakeCode v4.1.41 to v5.1.1:

Sound Level max value: 131
https://makecode.microbit.org/v4.1.41
https://makecode.microbit.org/v5.1.1
https://github.com/microsoft/pxt-microbit/blob/v4.1.41/libs/microphone/microphonehw.cpp
microbit-sound-v0237-v0240.zip

CODAL v0.2.35, MakeCode v4.1.34:

Sound Level max value: 195
https://makecode.microbit.org/v4.1.34
https://github.com/microsoft/pxt-microbit/blob/v4.1.34/libs/microphone/microphonehw.cpp
microbit-sound-v0235.hex.zip

At this point I noticed all versions behaved the same, so didn't collect additional data, but tried each MakeCode release that updated CODAL all the way back to MakeCode v3.1.21 with CODAL v0.2.12:

Sound Level max value: 195
29 Oct 2020
https://makecode.microbit.org/v3.1.21
https://github.com/microsoft/pxt-microbit/blob/v3.1.21/libs/microphone/microphonehw.cpp
microbit-sound-v0212.hex.zip

Older versions of MakeCode didn't compile:

MakeCode v3.1.5 with CODAL v0.2.9 doesn't work
MakeCode v3.1.4 with CODAL v0.2.1 doesn't work

The suggestion here is to keep the existing API, and create a new scaled API for extensions, etc. to use moving forward.
Do we want to actively deprecate the old calls for this, and/or rename them to ...dB() calls for clarity?

I believe we agreed to keep the old APIs as they are, and add new ones to returned a scaled value, which can then be used by MicroPython and MakeCode directly rather than scale the values on their side.

New APIs added as discussed.
Default behaviour is unchanged, but there is now an optional method to used an unsigned 8 bit range rather than S.I. dB units in the SPLLevelDetector class:  https://github.com/lancaster-university/codal-core/blob/master/inc/streams/LevelDetectorSPL.h#L170
The following example code will drop the level detector into this new 8 bit mode:
uBit.audio.levelSPL->setUnit(LEVEL_DETECTOR_SPL_8BIT);
By default the 8 bit range is linearly mapped to the 35db...100db range, and can be configured with the two CONFIG options defined here via config.json :
https://github.com/lancaster-university/codal-core/blob/master/inc/streams/LevelDetectorSPL.h#L53
https://github.com/lancaster-university/codal-core/blob/master/inc/streams/LevelDetectorSPL.h#L58
I also took the opportunity to improving the low end the sensitivity of the level detector by adding in a low pass filter (it's now about 35db rather than 52db, which is much more useful). Finally, I also calibrated the various parameters in the pipeline to calibrate the sensor more accurately.
A good shout into the microphone can now hit a value of 255 @microbit-carlos, so should address the MakeCode bug described above.
@abchatra @dpgeorge - suggest we adopt this functionality as a common calibration for both micropython and MakeCode when convenient so that users can benefit from consistent behaviour across both languages?

Sounds good. @riknoll - fyi

suggest we adopt this functionality as a common calibration for both micropython and MakeCode when convenient so that users can benefit from consistent behaviour across both languages?

Yes we will do that.

New APIs added as discussed.

@finneyj Can we safely close this now? Has this lot been PR'd and merged?

Thanks @JohnVidler. Yep, all changes are now in main branch. Closing.


Consider optional "name" setting

If "name" option is not defined, dts-bundle does not wrap output with module definition:
instead of
// Generated by dts-bundle v0.4.3

declare module 'MyBundle' {
    module Module1 {
        function validateGuid(guid: any): boolean;
    }
    module Module2 {
        function validateGuid(guid: any): boolean;
    }
}

generate just
// Generated by dts-bundle v0.4.3

module Module1 {
    function validateGuid(guid: any): boolean;
}
module Module2 {
    function validateGuid(guid: any): boolean;
}

Can you explain me a case of use where you need it?
Thanks.

Now I feel like I've used wrong tool. I have a set of .ts file with internal modules. I combine them into a single resulting file, say "result.ts". I'd like to create a single corresponding "result.d.ts" file. And, in the "result.d.ts" I need no references ("/// <reference path=...") completely as well as simply combine internal modules.
I've been expected "dts-bundle" as a tool for solving my tasks. May be I was wrong, and this is not your scenario. In this case you can simply close this issue.
Thanks

Yes, this is not the scenario of dts-bundle.
When I need it I usually create "result.ts" file manually exporting the others modules. I usually have a "result.ts" file for each folder, see this example https://github.com/tolemac/ngts/blob/master/ngts.ts
It's exporting "decorators/decorators" and this is the code that module https://github.com/tolemac/ngts/blob/master/decorators.ts


Possible project use

Hello All,
I am developing on new type of OS basically from the ground up and is not based upon Linux, Windows, or others and is more akin to a Microkernel Hypervisor for which I have the kernel now and a limited Userland implementation that will be expanded going forward. For applications on existing platforms, there will be application compatibility layers for each application OS type.
In any case, I want to make some very unique features a and one of them is a type of database filesystem which is "sort of" along the lines of the old Novell mapping filesystem but not exactly.
What I am thinking about is to use a specialized performant Key-Value approach for that and the compatibility layers will translate the needed call to get the date from the KV database that services the whole system That's the idea at least.
I have been researching many possibilities and think that perhaps embedding RoseDB into a filesystem service could be a possible solution but I have some questions about what it can, and cannot, currently do so that I can determine what may need to be implemented.
Outstanding Questions:

Does rosedb support binary, blob, and similar data types?

Can it store/retrieve nested multiple key-values:

For example:

set person1
         first = "john"
         last = "doe"
        address:
            city = "a town"
            state = "MD"

and then using a "get" (or similar)

get person1->address->state  (results in "MD")

Basically, the question is about nesting multiple KV's

Can rosedb append/delete KV's to something like above (2), for example to add:

append person1->address->zip = 12345

Maybe "delete" nested KV would be similar.

Not sure about this idea, but perhaps being able to add some type of "pointer" KEY so that for example you could say something like:

point person2->person1

which then could be navigated to get the same information from the original person1 since there are now 2 instances pointing to the same structure.

get person2->address->state  (results in "MD")

of course we might have a "copy" command as well:

copy person1->person2

which would make a complete copy of the whole structure.

and

delete person2 just removed the pointer to the structure.

The idea is that a pointer approach would not make multiple copies of the same structure.

These are just some of the ideas that I was thinking about which rosedb might already have some type of implementation for some of these.
Any thoughts would be greatly appreciated.
Thanks in advance

Thanks for your attention.

rosedb is a key/value storage engine that only supports simple k/v structure. But the value can be anything you want to store. You can transfer the binary or blob data into byte array that rosedb can accept.
2 3 4. I guess no, the same reason as the previous one.


Closing VS with remote workspace open messes up local workspace defaults

Open remote workspace
Quit VS
Restart VS
Open R project/solution

Result: no active workspace; when local R engine is selected, an error is printed indicating RTVS tried to change to previous (remote) working directory

We do not reconnect to remote on restart so this is by design. However, code should not be trying to set directory when there is no connection.

Would it be possible to display either:

a dialog asking to reconnect to the remote; or
a message saying to reconnect manually?

Right now, the experience is a bit abrupt. I thought at first that something was preventing RTVS from reconnecting.

Generally we've been trying to avoid too many modal boxes. Also, we don't necessarily know why connection was terminated (could be user action). Perhaps it could be an option... @AlexanderSher - what do you think?


Deconstruct / Unbuild a completed build

I am trying to figure out how to deconstruct an item to reclaim the parts into inventory. Is this possible? I have not found it in the docs or by playing around with the InvenTree application.

Currently this is not possible. It would be a great addition to the build order workflow, although it would require a lot of careful consideration.
For example there would have to be support for the end user to dictate (very specifically) which consumed items are to be returned to stock, and which are to be "scrapped".

Would be a nice thing; A bit more precise feature description would be nice to have something to work of.

My current use case is as a hobbyist beekeeper where I would "construct" a hive to take into the field. I do not use trackable parts to make this easier. When a hive has a dead-out or is no longer needed it is transferred inside and the parts become available for use in other hives as necessary.
I imagine an implementation would look the same as a build order but in reverse. The same screens could likely be utilized:

I'm unsure of what industry standard naming would be. I would use: Deconstruct Order
Allocate Stock would allow you to do the same as a build order, but in reverse.
Incomplete and Completed outputs instead parts moving to a whole, would be a whole moving towards parts. Probably viewable via a tree view dropdown on the whole part if trackable.
Child Deconstruct Orders if desired could be added to take it even further apart.
Attachments and Notes are the same as a build order.

Hope this helps. Thanks for looking at it.

@biker2000on thank you for the explaination!

@matmair I may be able to take a stab at coding this feature. I read somewhere that you are in the midst of a migration to API-first and React. Should the implementation be for django templating or skip that altogether and just do the backend code and separate React frontend?

@biker2000on the react rework is still a ways off. I'd concentrate first on the backend logic required to perform this process. If you can conceive a workflow, discuss with us first, before we jump into implementation.
Second step would be exposing functionality to the API.
Third is UX

not stale


Plotting the spatial distribution of light

I am currently working on simulating SHG of low pulse energy, tightly focused light. Due to the presence of group velocity mismatch and spatial walk off in the system, the generated SH should exhibit signficant pulse front tilt and a distorted SH beam profile. I am trying to use python to plot the spatial profile of the output of a simulation to characterise this (e.g. a heatmap of the electric field over the x-y axes). However I am having trouble deciphering the way the electric fields are stored in a python lightwaveExplorer object. Do you have any sample code that I could use to get started, or just some tips on the way the electric field is stored in the lightwaveExplorer object?
Any help would be greatly appreciated!

Thank you for the swift response! This is a lot more than I expected and perfect for what I need. I will have a play with this for my results.


Fix: Stop throwing IllegalStateException upon invalid WatchKey

Context
This PR changes the FileSystemWatcherCache so that it stops throwing an IllegalStateException upon encountering a WatchKey that is invalid.
Instead, a WARNING will be logged (exception is printed to the DEBUG log) and the service bindings will get re-loaded from the file system.
This issue has explicitly been observed when running an application inside a Docker container that is based on openjdk:17-jdk-alpine.
Feature Scope

[x] Refactor the FileSystemWatcherCache implementation

Release Notes
Module: java-sap-service-operator

The internal file system-based cache no longer throws an IllegalStateException if it is not able to check whether entries in a directory have been changed. Instead, it will log a warning and re-load the service bindings from disk.

Note: This might result in slightly reduced performance. By default, however, there is still a 5 minute cache that prevents the accessor to read from disk over and over again.

Definition of Done

[x] Feature scope is implemented
[x] Feature scope is tested
[x] ~Feature scope is documented~ (this is just an implementation detail)
[x] Release notes are created

Could you, by any chance, identify why the key was invalid in the setup you produced?

I'm not familiar with WatchKey behavior and available API. But I also wonder whether the error state can be anticipated without catching an exception.

@cschubertcs wrote:

Could you, by any chance, identify why the key was invalid in the setup you produced?

But the issue seemed to be non-deterministic - sometime everything was working just fine and in other occasions, the mentioned error occurred.
I'm suspecting it to be an issue with how mounting in K8s works... Maybe even in combination with the base OS my containers were built upon and some unlucky timing...? As you see, no real clue unfortunately.

@newtork wrote:

I'm not familiar with WatchKey behavior and available API. But I also wonder whether the error state can be anticipated without the need to throw and catch the exception.

Maybe... I think we could ask the FileSystem whether it has been closed. If so, I'd expect the corresponding WatchService instance to be closed as well (unfortunately, there is no API to ask the WatchService directly) and, as a consequence, all WatchKey instances that were produced using the FileSystem should also be invalid / closed.

I'm currently considering some sort of reconciliation logic where we could re-assemble the entire cache (including getting the FileSystem, creating a WatchService for that FileSystem and throwing away all cached ServiceBindings), if we find the FileSystem to be closed. (maybe we try this strategy for up to three times and, if that still doesn't work, give up and just re-load the bindings with every request)
I'm a bit hesitant to go that route since it would blow up the implementation by quite a bit IMO.
What do you think about such an approach, @cschubertcs and @newtork ?

Hm, I'm a bit torn here right now.
I would like to better understand the underlying reason to add a fix that is "minimal" for the problem.
Your proposed solution sounds good in the sense that it should fix that problem, but feels a bit "oversized" (without deeper experience in the area/API).
So, I see three approaches:

Spending more time to understand the issue to provide a "minimal" fix ( -> creating a BLI and putting focused work on it)
Merging this PR and creating a follow up BLI to understand the issue ( -> will most likely never be touched, so that this temporary fix will become a permanent fix)
Building and mergingyour proposed solution ( -> basically the same as 2, just bigger)

My preference would be 1., but I don't know how soon we could focus on understanding the problem (and whether it makes sense, from a pragmatical point of view).

Continued in #132


crypto/tls: RequireAndVerifyClientCert is not working as intended.

What version of Go are you using (go version)?
$ go version
go1.21.1 darwin/amd64
Does this issue reproduce with the latest release?
Yes i tried with latest and older releases as well
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
manikishore.s$ go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/manikishore.s/Library/Caches/go-build'
GOENV='/Users/manikishore.s/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/manikishore.s/go/pkg/mod'
GONOPROXY='github.com/Manikishore-S'
GONOSUMDB='github.com/Manikishore-S'
GOOS='darwin'
GOPATH='/Users/manikishore.s/go'
GOPRIVATE='github.com/Manikishore-S'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='go1.21.1'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/q0/chzy5trn5s17x4d7k4mg38qhw1k3zr/T/go-build3453854944=/tmp/go-build -gno-record-gcc-switches -fno-common'
What did you do?
Start a crypto/tls-based webserver with mtls config as show below.
tlsConfig := &tls.Config{
		ClientCAs:                caCertPool,
		ClientAuth:               tls.RequireAndVerifyClientCert,
	}

What did you expect to see?
You may expect to see a client certificate is getting exchanged for verification.
What did you see instead?
A TLS handshake without client certificate exchange.

I have tried with other option requestClientCertificate etc but none of them worked. seems a bug.

Please fill out the complete issue template. What program did you run? What did you expect to see? What actually happened instead?

Update with necessary info. Thanks for pointing it out

@Manikishore-S It is a TLS 1.3 spec point, not specific to Go. See RFC 8446.

All handshake messages after the ServerHello are now encrypted.
The newly introduced EncryptedExtensions message allows various
extensions previously sent in the clear in the ServerHello to also
enjoy confidentiality protection.

@rittneje @seankhliao Thanks a lot!!


add "Homepage" field to cabal file

Sorry to bother you on an old project, but currently there's no link to this repo from Hackage and I'm hoping we can fix that :)

I'm probably going to do some more work on this library. Do you still have any interest in maintaining it if I submit some other, less trivial, pull requests? If not, would you mind letting me take over as a maintainer?

Hi Chris!
Please take over as a maintainer, I already forgot how to C. Is there anything I should do for that?
Thanks for using my code!

Yeah, can you add me to the project on Hackage? https://hackage.haskell.org/package/pam/maintainers/ Thanks!

Hey, any update on this?

I was trying to remember my password and I finally got it.
What's your user name on hackage?

Oh, right, that's important :D
It's chris_martin

Thanks!


webapp error

when i try to run "nxbt webapp" i get 'ImportError: cannot import name 'BaseResponse' from 'werkzeug.wrappers' " (Traceback (most recent call last):
File "/usr/local/bin/nxbt", line 10, in
sys.exit(main())
File "/usr/local/lib/python3.7/dist-packages/nxbt/cli.py", line 321, in main
from .web import start_web_app
File "/usr/local/lib/python3.7/dist-packages/nxbt/web/init.py", line 1, in
from .app import start_web_app
File "/usr/local/lib/python3.7/dist-packages/nxbt/web/app.py", line 9, in
from flask import Flask, render_template, request
File "/usr/local/lib/python3.7/dist-packages/flask/init.py", line 21, in
from .app import Flask
File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 32, in
from werkzeug.wrappers import BaseResponse
ImportError: cannot import name 'BaseResponse' from 'werkzeug.wrappers' (/usr/local/lib/python3.7/dist-packages/werkzeug/wrappers/init.py))

this is after i tried to fix the jinja2 escape error, and downgrading werkzeug prompts the jinja 2 escape error to appear again

never mind, just had to install the downgrades with sudo commands

Hi, could you give instructions on how to do this?
My error is a little different, but maybe your steps can help me.
Traceback (most recent call last):
  File "/usr/local/bin/nxbt", line 33, in <module>
    sys.exit(load_entry_point('nxbt', 'console_scripts', 'nxbt')())
  File "/vagrant/nxbt/cli.py", line 321, in main
    from .web import start_web_app
  File "/vagrant/nxbt/web/__init__.py", line 1, in <module>
    from .app import start_web_app
  File "/vagrant/nxbt/web/app.py", line 9, in <module>
    from flask import Flask, render_template, request
  File "/usr/local/lib/python3.8/dist-packages/flask/__init__.py", line 14, in <module>
    from jinja2 import escape
ImportError: cannot import name 'escape' from 'jinja2' (/usr/local/lib/python3.8/dist-packages/jinja2/__init__.py)

Thank you. I tried each line but I keep getting the same error with a different package name and version.
install: missing destination file operand after 'jinja2==3.0.3'

maybye try sudo apt-get install jinja2==3.0.3?

related to #61 ?

duplicate of/related to #61 ?

Thank you, this works great. Replaced the three files in your pull request and having no issues connecting now.

maybe try sudo apt-get install jinja2==3.0.3?

Tried it too, didn't work. Forgot to report back here but thank you for trying to help.

fixed these error by downgrading:
jinja2 to 3.0.3
itsdangerous to 2.0.1
werkzeug to 2.0.3
sudo pip3 install jinja2==3.0.3
sudo pip3 install itsdangerous==2.0.1
sudo pip3 install jinja2==2.0.3


Adding functionality to call KnowBe4's User API, as well as basic tes…

…ting. Why add this functionality? The Users API gives us phishing-prone percentage on a per-user basic, as well as department and other useful information.

Sounds good, I'll merge the go fmt'd code.


fix(cli): command timing out without showing info

Proposed changes
The analytics hook is ending the program execution, which makes the handleSnapshotError method unreachable. The issue has something to do with the analyticsClient.sendCustomEvent method.
Since the root cause is still unknown, I am moving all the CLI logic before sending analytics.
I also replaced cli.info with cli.log since log basically calls info (link).
Testing

[ ] Unit Tests:

[ ] Functionnal Tests:

[x] Manual Tests:
I packed a version of the cli in which I moved the analytic hooks at the end.

CDX-502

Did you open a ticket for the analytics failure (and add it to CDX-505)


riscv: hpm6750: add option to select hpmicro toolchain

Summary
For boards/risc-v/hpm6750/hpm6750evk2,  add option to select hpmicro GNU riscv32 toolchain.
Default, using generic GNU riscv64 Toolchain.
Impact
Don't impact others.
Testing
hpm6750evk2:nsh

@chenzhihong007 so why not remove HPM_GNU_TOOLCHAIN from the first patch?

I removed HPM_GNU_TOOLCHAIN from the first patch, used /common/Toolchain.defs to select riscv32 toolchain.


Support applications and profiles with dashes in its names in properties, json & yml endpoints.

At my organization ( @serenity-devstack ), we make use of the spring configuration server.
Some of our applications contain dashes as part of its name and unfortunately we got problems when making use of the below services in the class EnvironmentController (module spring-cloud-config-server),

GET /{name}-{profiles}.properties
GET /{label}/{name}-{profiles}.properties
GET /{name}-{profiles}.json
GET /{label}/{name}-{profiles}.json
GET /{name}-{profiles}.yml
GET /{label}/{name}-{profiles}.yml or /{label}/{name}-{profiles}.yaml

These services don't work as we expected due to the method validateNameAndProfiles(name, profiles) throw an Error.
Are you planning to support application and profiles which contain dashes as part of their names? If so,  could you provide us with some work around to take in the meanwhile?
Would you consider creating  new endpoints in order to support applications with dashes?
Thanks in advance
Cheers

A workaround is to create a controller of a form you like that doesn't have a dash in it and wire in an EnvironmentController and delegate to it.

Thanks for that, but unfortunately If we do that we still have the same problem since the methods in class EnvironmentController invoke validateNameAndProfiles..
Since we need to skip the above validation, a possible solution we found it would be to make some refactor in the EnvironmentController class  and implement a strategy pattern  that allows us to customize the validation to apply.

Would you consider creating  new endpoints in order to support applications with dashes?

No, probably not. If you want to contribute a fix, I would say that you have to choose whether to accept application names or profiles with embedded dashes. I expect whatever you propose will involve parsing the HttpServletRequest (which is ugly and I wish it were not necessary, see https://jira.spring.io/browse/SPR-14193).

Please consider adding a new endpoint to resolve the ambiguity here. Not being able to have dashes in application names is a big drawback. (is it at least stated in the documentation somewhere?)

You can have dashes in application names. It just doesn't necessarily work with the .properties and .yml endpoints.

Suggestion:

Keep the same endpoints but allow dashes in application names with all the endpoints (included the .properties and .yml endpoints). The profile names with dashes would keep failing with some endpoints but at least app names would work.
Document the drawback, as @otrosien suggests.

If dashes are needed for profile names too, maybe it could be addressed at a different issue asking for new endpoints...

@jorgenota sounds reasonable. We'd want a PR in the next couple of days if it is to make it into 1.1.0.

So will @ivancorrales patch make it to 1.1.0.RELEASE?
We would really like to keep the convention of artifactId = spring.application.name but artifactId standard is to use dashes.

It did not make it.

will you plan to add it to the next release?


Tasks using "runOn": "folderOpen" are broken

have a task with "runOn": "folderOpen", like https://github.com/microsoft/vscode-github-issue-notebooks/blob/e017704a5eb4bb6080322a3d489c76d421089111/.vscode/tasks.json#L18
make sure it ran once
reload/reopen folder
🐛 task doesn't run

do you have task reconnection enabled?

@meganrogge Not sure if this is related but Google Cloud Code's terminal contribution stopped working at the same time as this issue. Please guide me on how I can validate if the issues are unrelated (in which case, I'll open an issue on the extension repo).

You can test it in tomorrow's insider's.


exFAT not accessible

I have found that an exFAT USB will mount and is usable on the device when ChromeOS is running but NOT when running Breath/Ubuntu.  Ubuntu requires exfat-utils and exfat-fuse (Ubuntu 21.10) or exfatprogs (Ubuntu 22.04) for reading exFAT devices and those are installed.  The same bundles installed on my Ubuntu build system enable it to mount and use this same exFAT USB.  It is only under Breath/Ubuntu that it is not accessible.
When I insert the USB, it is listed in the Files app (in nautilus, left-hand pane) but attempts to access it report: "Unable to access, Error mounting: unknown filesystem type 'exFat'.  When I open "Disks", it does not see the device at all; it is not listed.
Given it works under ChromeOS and we're using the ChromeOS kernel, it seems strange that it wouldn't work under Breath/Ubuntu.  Ideas?

The kernel config is different between those systems. CONFIG_EXFAT_FS is not part of the kernel config.

Yeah, I'm pretty sure I built the latest kernel with exFAT support.


bump kubernetes to 1.8

This PR will bump client-go/api/metrics/apimachinery/kubernetes to 1.8.
As node-problem-detector depends on heapster in some pkgs, we need firs to update heapster to support Kubernetes 1.8 first.
Main changes:

remove source apiVersion config as Cluster has no APIVersion field for now.
remove usage of NodeLegacyHostIP as it has been deprecated.
deprecate heapster/metrics/metrics and use metrics/pkg/apis/metrics.
udpate metrics from v1alpha1 to v1beta1.

/cc @DirectXMan12 @loburm @fgrzadkowski

This change is

@andyxning is there any chance to split this PR into smaller chunks? Or all changes are dependent on each other?

@loburm I have tried to do so. But api&&apimachinery&&metrics&&client-go are referencing each other. It is hard or impossible to only update one.

OK, I see could you please resolve conflicts first and then I'll check what we can do.

@loburm Thanks.
Some significant changes are documented in the PR description.

/test pull-heapster-e2e

@andyxning I think that we also need to change supported_kube_version in Makefile.

@loburm Done.

Makefile: https://github.com/kubernetes/heapster/pull/1849/files#diff-b67911656ef5d18c4ae36cb6741b7965
integration/.jenkins.sh: https://github.com/kubernetes/heapster/pull/1849/files#diff-ee3c240603fa28e187c659a556bb782b

LGTM in general. Huge thanks @andyxning for doing this super grungy work.
E2e are failing
I1018 02:50:00.002] --- FAIL: TestHeapster (591.37s)
I1018 02:50:00.003] 	assertions.go:203:

	Error Trace:	heapster_api_test.go:1159
I1018 02:50:00.003]
	Error:		Received unexpected error "failed to parse heapster controller - no kind \"ReplicationController\" is registered for version \"v1\""

The PR also needs to be rebased. Will you find some time to take a look into this?

@piosz Will handle this in about 3 days.

@andyxning thanks. I'll release v1.5.0 then and include this in v1.5.0.

for future reference, why does node-problem-detector depend on Heapster?

@piosz Sorry for the delay. But too busy these days. In case you have a schedule for releasing v1.5.0 for heapster, i may have not enough time to make this happen this week. I will make this happen later.

@andyxning now worries. As I wrote, we will include those changes in a patch release.

@piosz @loburm @DirectXMan12 Sorry for the late and finally i got it. For now the ci and e2e test are both green. PTAL.

@DirectXMan12

for future reference, why does node-problem-detector depend on Heapster?

This is used to add running NPD in standalone mode. FYI: https://github.com/kubernetes/node-problem-detector/pull/49

@piosz @DirectXMan12

Two comments:

please revert change bumping metrics api from v1alpha1 to v1beta1
consider removing support for aggregated apiserver in Heapster
Otherwise LGTM

please revert change bumping metrics api from v1alpha1 to v1beta1. Done with using k8s.io/metrics/pkg/apis/metrics/v1alpha1.
consider removing support for aggregated apiserver in Heapster. Pending as i am not familiar with this. I think we can do this in another PR. :)

Ping @jingxu97 for reviewing this PR. :)

/retest

The integration failed. Can anyone see it and give me some advise? Too complicated. :(

/retest

/test pull-heapster-e2e

cc @piosz @kawych

@jingxu97 @andyxning
I've debugged the integration test for a bit, it's an issue in your deployment files that causes heapster pod not to be created. I've left some comments, after applying these changes, heapster pod is created and tests are running, so you should be fine.

@kawych Thanks for the diagnose and suggestions. After all, there are still some problems. Could you please help to take a look at this?

Finally ping @loburm @piosz @DirectXMan12 @x13n @jingxu97
Sorry for the quite long time delay but with the help from @kawych we finally make all the ci green. PTAL.

Yay! Looks good to me, deferring to others who previously had comments to apply lgtm label.

@piosz @DirectXMan12 - Please take a look and re-apply LGTM label if it looks fine
@andyxning - Note #1980 Consider bumping it one more version - to 1.9.4. Alternatively we can get this merged and bump it again later.

I'm against bumping the version again - there is already too much happening in this PR.

@x13n @kawych I am also suggest we first review and merge this PR.
/cc @piosz @DirectXMan12 PTAL ASAP. :)

@loburm @kawych @x13n Can anyone of you give piosz a DM since you are both Googlers. :)

@loburm @piosz @DirectXMan12 Could you please take a look and see whether this PR is ready to be merged? Thanks a lot!

Co-ping. Given that there are other PRs queued after this one, can we speed up the review on this PR?

/lgtm


H.112 tutorial for graphviz (check if in the old book)

always put urls in when you close such issues ;-)

https://github.com/cybertraining-dsc/reu2022/blob/main/project/graphs/graphs-graphviz/graphviz.md

Fig 2 is wrong

sorry one more thing. please remove reu2022 in fig 3 and replace with workflow or graph, or job or something like that

Replace reu2022 w/ cloudmesh-alex
https://github.com/cybertraining-dsc/reu2022/blob/main/project/graphs/graphs-graphviz/graphviz.md

I still see the image having reu2022 in it

see
import graphviz
s = graphviz.Digraph('files in directories', filename='structure-graphviz.gv')
s.node_attr={'shape' : 'record'}
s.node('s1', ' cloudmesh-cc |  reu2022')
s.node('s2', '{ cloudmesh |  tests}')
s.node('s3', ' contribute | { graphs |{ graphviz |  networkx}}')
s.edges([('s1:d1', 's2:d2'), ('s1:d2', 's3:d4')])
s.view()
should be
import graphviz
s = graphviz.Digraph('files in directories', filename='structure-graphviz.gv')
s.node_attr={'shape' : 'record'}
s.node('s1', ' cloudmesh-cc |  workflow')
s.node('s2', '{ cloudmesh |  tests}')
s.node('s3', ' contribute | { graphs |{ graphviz |  networkx}}')
s.edges([('s1:d1', 's2:d2'), ('s1:d2', 's3:d4')])
s.view()
Then put in new image

Replaced reu2022 w/ workflow
https://github.com/cybertraining-dsc/reu2022/blob/main/project/graphs/graphs-graphviz/graphviz.md


Damianedwards/channels

Hi @seraphshine, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

Was this PR created by mistake? @DamianEdwards ?


RACSubject generics

Lightweight generics for RACSubject, giving us some autocompletion and helping us bridge with Swift.
Solves #58.
Unfortunately I couldn't find a nice way of extending the generics to sendNext:, for the reason that ObjC protocols don't support generics (sendNext: is declared in RACSubscriber).

@erwald Is it possible to redeclare sendNext: on objets that implement RACSubscriber with more precise ValueType information? Does the compiler check this?

Yes, that worked beautifully! Don't know why I didn't think of that.
I added just a comment saying it was a redeclaration—it inherits the method documentation from the RACSubscriber header. It does make the RACSubject header look a little weird or incomplete, but I figured it was the least confusing way of doing it.

@erwald Looks good—once you've rebased and resolved conflicts this should be good to go! 🎉

@erichoracek Done, thanks! I'll have a stab at RACChannel/RACChannelTerminal too in the upcoming days.


URL Rewrite

It would be nice if I could rewrite all URLs given to .load() as a promise, the same way I can by adding an interceptor to $httpProvider. Any thoughts?

The version 1.x of ocLazyLoad is modular, you can use decorators to overwrite (or add new) functions.
For example this is how you can define a jsLoader: https://github.com/ocombe/ocLazyLoad/blob/master/src/ocLazyLoad.loaders.jsLoader.js
In your case I'm not really sure what your intention is, do you have a use case for this ?

It's quite simple. I have a client-side rewrite engine, tied to my backend (because of the usage of aggressive-caching). So, 'include/state/topbar.html' becomes '/static/include/state/topbar.html?v=somehash'. It's not needed to rewrite the whole loader :)

Ok, so you want to be able to intercept the url before it gets used.
If it's only for templates, the native template loader uses $http, so you can use interceptors.
If it's for js/css files, you might rewrite the loaders, their code is really short so it shouldn't be really difficult. And if you do so, maybe you could share them for others.
The js & css loaders could probably use $http, it shouldn't be too difficult, I didn't do it like this because you would have CORS issues (since it would use ajax instead of letting the browser load the files by itself).

Yeah, well, let me see if I can make myself clear. I'm already using $http interceptors for templates. They basically talks to the server using a websocket and returns the full URL of my template, which then I return as a promise. Now ... I was wondering how to do that with JS and CSS?
Just to illustrate:
myApp.factory('myHttpInterceptor', ['$q', 'wsocket', function ($q, wsocket) {
    return {
        request : function (config) {
            var deferred = $q.defer();
            wsocket.send({
                method : 'get_static_url', // the command i want to execute in the server side, doesn't matter too much here
                data : config.url // the given url, let's say, 'includes/state/topbar.html'
            }, function (o) { // my callback (completely async)
                config.url = o.result; // o.result is the rewritten url, like '/static/includes/state/topbar.html?v=123456'
                deferred.resolve(config); // go on and make my day
            });
            return deferred.promise;
        }
    };
}]);

that's basically all. i'm trying to figure it out where I can do something similar with ocLazyLoad :)

I just made a fork of your project, let's see if I can add some "extra" modularity (if needed) ;)

Cool, let me know if you need help !

Sure! Thanks a lot :)
On Wed, May 6, 2015 at 9:06 AM, Olivier Combe<EMAIL_ADDRESS>wrote:

Cool, let me know if you need help !
—
Reply to this email directly or view it on GitHub
https://github.com/ocombe/ocLazyLoad/issues/175#issuecomment-99425435.

Impossible for me to be more lamer ...
Before:
        .state('index', {
            url: '/index',
            templateUrl: 'includes/states/main.html',
            controller: 'MainController',
            resolve: {
                loadMyCtrl: ['$ocLazyLoad', function ($ocLazyLoad) {

                        return $ocLazyLoad.load({
                            files:
                            [
                                'vendors/some-plugin.js, // needs to be "rewritten"
                                'vendors/some-plugin.css', // need to be "rewritten" too
                            ]
                        });
                    }]
            }
        })

After:
        .state('index', {
            url: '/index',
            templateUrl: 'includes/states/main.html',
            controller: 'MainController',
            resolve: {
                loadMyCtrl: ['$ocLazyLoad', 'wsocket', '$q', function ($ocLazyLoad, wsocket, $q) {

                        var d = $q.defer();
                        wsocket.send({
                            method : 'get_bulk_static_url',
                            data : [
                                'vendors/some-plugin.js, // needs to be "rewritten"
                                'vendors/some-plugin.css', // need to be "rewritten" too
                            ]
                        }, function (o) {
                            d.resolve($ocLazyLoad.load({files : o.result}));
                        });
                        return d.promise;
                    }]
            }
        })

Done. No tricks needed. IMHO, it could make a good example, specially for ajs noobs like me (started messing around last monday, lol).
Anyway, thanks for your quick responses and help! :)

Cool! So you didn't need to change ocLazyLoad after all :)

Yup, that moment you understand all that's needed for 'resolve' was a
deferred ...
On Wed, May 6, 2015 at 10:05 AM, Olivier Combe<EMAIL_ADDRESS>wrote:

Cool! So you didn't need to change ocLazyLoad after all :)
—
Reply to this email directly or view it on GitHub
https://github.com/ocombe/ocLazyLoad/issues/175#issuecomment-99448382.


K3S  failed in half hour when skip all manifests

Environmental Info:
K3s Version:

k3s version v1.26.0+k3s-6.0 (6.0)
go version go1.19.4
Node(s) CPU architecture, OS, and Version:

Linux deploy-k8s-master 4.19.91-26.5.an8.x86_64 #1 SMP Thu Sep 29 16:53:49 CST 2022 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

1 server, 3 agents
Describe the bug:

I cloned 1.26.0+k3s2 and modified some code that is not important, such as

Certificate Validity
version

but when i try to use these method to avoid manifests, k3s server failed in half hour

comment out manifests's ListFileIn method to avoid deploy
use no_stage build tag to build k3s

Eventually, I gave up on modifying the code， and try to use skip file to skip all manifests,  but k3s still failed in half hour
Steps To Reproduce:

Installed K3s:

Expected behavior:

Actual behavior:

k3s failed in half hour
Additional context / logs:

Jan 13 17:57:34 deploy-k8s-master k3s[11932]: W0113 17:57:34.848895   11932 core.go:221] configure-cloud-routes is set, but no cloud provider specified. Will not configure cloud provider routes.
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: W0113 17:57:34.848902   11932 controllermanager.go:600] Skipping "route"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.849011   11932 pv_controller_base.go:318] Starting persistent volume controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.849018   11932 shared_informer.go:273] Waiting for caches to sync for persistent volume
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: E0113 17:57:34.850165   11932 core.go:207] failed to start cloud node lifecycle controller: no cloud provider provided
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: W0113 17:57:34.850179   11932 controllermanager.go:600] Skipping "cloud-node-lifecycle"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.851524   11932 controllermanager.go:622] Started "endpointslicemirroring"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.851627   11932 endpointslicemirroring_controller.go:211] Starting EndpointSliceMirroring controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.851639   11932 shared_informer.go:273] Waiting for caches to sync for endpoint_slice_mirroring
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.852937   11932 controllermanager.go:622] Started "replicationcontroller"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.853067   11932 replica_set.go:201] Starting replicationcontroller controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.853081   11932 shared_informer.go:273] Waiting for caches to sync for ReplicationController
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865139   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for daemonsets.apps
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865170   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for endpointslices.discovery.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865183   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for endpoints
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865207   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for helmcharts.helm.cattle.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865222   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for addons.k3s.cattle.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865236   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for podtemplates
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865266   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for deployments.apps
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865297   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for rolebindings.rbac.authorization.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865315   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for helmchartconfigs.helm.cattle.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865328   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for ciliumlocalredirectpolicies.cilium.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865369   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for controllerrevisions.apps
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865394   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for cronjobs.batch
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865413   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for poddisruptionbudgets.policy
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865435   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for ciliumenvoyconfigs.cilium.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865452   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for statefulsets.apps
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865471   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for replicasets.apps
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865495   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for roles.rbac.authorization.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865518   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for ciliumnetworkpolicies.cilium.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865571   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for ingresses.networking.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865610   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for horizontalpodautoscalers.autoscaling
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865639   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for csistoragecapacities.storage.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865692   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for serviceaccounts
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865714   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for limitranges
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865735   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for jobs.batch
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865758   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for networkpolicies.networking.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865786   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for leases.coordination.k8s.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865809   11932 resource_quota_monitor.go:218] QuotaMonitor created object count evaluator for ciliumendpoints.cilium.io
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865823   11932 controllermanager.go:622] Started "resourcequota"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865864   11932 resource_quota_controller.go:277] Starting resource quota controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865877   11932 shared_informer.go:273] Waiting for caches to sync for resource quota
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.865893   11932 resource_quota_monitor.go:295] QuotaMonitor running
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868263   11932 controllermanager.go:622] Started "csrsigning"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: W0113 17:57:34.868292   11932 controllermanager.go:587] "tokencleaner" is disabled
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868391   11932 certificate_controller.go:112] Starting certificate controller "csrsigning-kubelet-serving"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868400   11932 shared_informer.go:273] Waiting for caches to sync for certificate-csrsigning-kubelet-serving
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868420   11932 certificate_controller.go:112] Starting certificate controller "csrsigning-kubelet-client"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868426   11932 shared_informer.go:273] Waiting for caches to sync for certificate-csrsigning-kubelet-client
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868443   11932 certificate_controller.go:112] Starting certificate controller "csrsigning-kube-apiserver-client"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868449   11932 shared_informer.go:273] Waiting for caches to sync for certificate-csrsigning-kube-apiserver-client
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868483   11932 certificate_controller.go:112] Starting certificate controller "csrsigning-legacy-unknown"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868489   11932 shared_informer.go:273] Waiting for caches to sync for certificate-csrsigning-legacy-unknown
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868513   11932 dynamic_serving_content.go:132] "Starting controller" name="csr-controller::/var/lib/rancher/k3s/server/tls/server-ca.crt::/var/lib/rancher/k3s/server/tls/server-ca.key"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868611   11932 dynamic_serving_content.go:132] "Starting controller" name="csr-controller::/var/lib/rancher/k3s/server/tls/client-ca.crt::/var/lib/rancher/k3s/server/tls/client-ca.key"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868675   11932 dynamic_serving_content.go:132] "Starting controller" name="csr-controller::/var/lib/rancher/k3s/server/tls/client-ca.crt::/var/lib/rancher/k3s/server/tls/client-ca.key"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.868739   11932 dynamic_serving_content.go:132] "Starting controller" name="csr-controller::/var/lib/rancher/k3s/server/tls/server-ca.crt::/var/lib/rancher/k3s/server/tls/server-ca.key"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.872571   11932 controllermanager.go:622] Started "ephemeral-volume"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.872684   11932 controller.go:169] Starting ephemeral volume controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.872693   11932 shared_informer.go:273] Waiting for caches to sync for ephemeral
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.968956   11932 garbagecollector.go:154] Starting garbage collector controller
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.968975   11932 shared_informer.go:273] Waiting for caches to sync for garbage collector
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.968957   11932 controllermanager.go:622] Started "garbagecollector"
Jan 13 17:57:34 deploy-k8s-master k3s[11932]: I0113 17:57:34.969013   11932 graph_builder.go:291] GraphBuilder running
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.018877   11932 controllermanager.go:622] Started "job"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.018925   11932 job_controller.go:191] Starting job controller
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.018947   11932 shared_informer.go:273] Waiting for caches to sync for job
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.119162   11932 controllermanager.go:622] Started "cronjob"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.119267   11932 cronjob_controllerv2.go:137] "Starting cronjob controller v2"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.119293   11932 shared_informer.go:273] Waiting for caches to sync for cronjob
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.121385   11932 shared_informer.go:273] Waiting for caches to sync for resource quota
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130315   11932 actual_state_of_world.go:541] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="<IP_ADDRESS>" does not exist
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130347   11932 topologycache.go:232] Can't get CPU or zone information for <IP_ADDRESS> node
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130642   11932 actual_state_of_world.go:541] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="<IP_ADDRESS>" does not exist
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130655   11932 actual_state_of_world.go:541] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="<IP_ADDRESS>" does not exist
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130671   11932 topologycache.go:232] Can't get CPU or zone information for <IP_ADDRESS> node
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.130915   11932 topologycache.go:232] Can't get CPU or zone information for <IP_ADDRESS> node
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.137254   11932 shared_informer.go:280] Caches are synced for PV protection
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.138627   11932 shared_informer.go:280] Caches are synced for endpoint_slice
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.139880   11932 shared_informer.go:280] Caches are synced for stateful set
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141175   11932 shared_informer.go:280] Caches are synced for taint
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141231   11932 node_lifecycle_controller.go:1438] Initializing eviction metric for zone:
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.141305   11932 node_lifecycle_controller.go:1053] Missing timestamp for Node <IP_ADDRESS>. Assuming now as a timestamp.
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.141334   11932 node_lifecycle_controller.go:1053] Missing timestamp for Node <IP_ADDRESS>. Assuming now as a timestamp.
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: W0113 17:57:35.141366   11932 node_lifecycle_controller.go:1053] Missing timestamp for Node <IP_ADDRESS>. Assuming now as a timestamp.
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141388   11932 node_lifecycle_controller.go:1254] Controller detected that zone  is now in state Normal.
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141564   11932 taint_manager.go:206] "Starting NoExecuteTaintManager"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141601   11932 taint_manager.go:211] "Sending events to api server"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141797   11932 event.go:294] "Event occurred" object="<IP_ADDRESS>" fieldPath="" kind="Node" apiVersion="v1" type="Normal" reason="RegisteredNode" message="Node <IP_ADDRESS> event: Registered Node <IP_ADDRESS> in Controller"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141812   11932 event.go:294] "Event occurred" object="<IP_ADDRESS>" fieldPath="" kind="Node" apiVersion="v1" type="Normal" reason="RegisteredNode" message="Node <IP_ADDRESS> event: Registered Node <IP_ADDRESS> in Controller"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.141824   11932 event.go:294] "Event occurred" object="<IP_ADDRESS>" fieldPath="" kind="Node" apiVersion="v1" type="Normal" reason="RegisteredNode" message="Node <IP_ADDRESS> event: Registered Node <IP_ADDRESS> in Controller"
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.143800   11932 shared_informer.go:280] Caches are synced for disruption
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.144981   11932 shared_informer.go:280] Caches are synced for certificate-csrapproving
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.146349   11932 shared_informer.go:280] Caches are synced for PVC protection
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.147685   11932 shared_informer.go:280] Caches are synced for service account
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.149466   11932 shared_informer.go:280] Caches are synced for persistent volume
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.152682   11932 shared_informer.go:280] Caches are synced for endpoint_slice_mirroring
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.153772   11932 shared_informer.go:280] Caches are synced for ReplicationController
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.169181   11932 shared_informer.go:280] Caches are synced for certificate-csrsigning-kubelet-serving
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.169192   11932 shared_informer.go:280] Caches are synced for certificate-csrsigning-kube-apiserver-client
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.169180   11932 shared_informer.go:280] Caches are synced for certificate-csrsigning-legacy-unknown
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.169195   11932 shared_informer.go:280] Caches are synced for certificate-csrsigning-kubelet-client
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.172997   11932 shared_informer.go:280] Caches are synced for ephemeral
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.185841   11932 shared_informer.go:273] Waiting for caches to sync for garbage collector
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.194819   11932 shared_informer.go:280] Caches are synced for endpoint
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.198962   11932 shared_informer.go:280] Caches are synced for HPA
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.200022   11932 shared_informer.go:280] Caches are synced for expand
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.202164   11932 shared_informer.go:280] Caches are synced for crt configmap
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.214415   11932 shared_informer.go:280] Caches are synced for namespace
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.219635   11932 shared_informer.go:280] Caches are synced for job
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.223165   11932 shared_informer.go:280] Caches are synced for node
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.223203   11932 range_allocator.go:167] Sending events to api server.
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.223226   11932 range_allocator.go:171] Starting range CIDR allocator
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.223232   11932 shared_informer.go:273] Waiting for caches to sync for cidrallocator
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.223241   11932 shared_informer.go:280] Caches are synced for cidrallocator
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.224497   11932 shared_informer.go:280] Caches are synced for ReplicaSet
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.226608   11932 shared_informer.go:280] Caches are synced for TTL
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.227671   11932 shared_informer.go:280] Caches are synced for TTL after finished
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.228732   11932 shared_informer.go:280] Caches are synced for GC
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.230828   11932 shared_informer.go:280] Caches are synced for daemon sets
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.231928   11932 shared_informer.go:280] Caches are synced for deployment
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.235050   11932 shared_informer.go:280] Caches are synced for attach detach
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.236041   11932 shared_informer.go:280] Caches are synced for ClusterRoleAggregator
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.319797   11932 shared_informer.go:280] Caches are synced for cronjob
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.365977   11932 shared_informer.go:280] Caches are synced for resource quota
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.421932   11932 shared_informer.go:280] Caches are synced for resource quota
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.769267   11932 shared_informer.go:280] Caches are synced for garbage collector
Jan 13 17:57:35 deploy-k8s-master k3s[11932]: I0113 17:57:35.769301   11932 garbagecollector.go:163] Garbage collector: all resource monitors have synced.
-- Subject: Unit k3s.service has begun shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit k3s.service has begun shutting down.
Jan 13 17:58:45 deploy-k8s-master k3s[11932]: I0113 17:58:45.803209   11932 secure_serving.go:255] Stopped listening on <IP_ADDRESS>:10259
Jan 13 17:58:45 deploy-k8s-master k3s[11932]: I0113 17:58:45.803236   11932 tlsconfig.go:255] "Shutting down DynamicServingCertificateController"
Jan 13 17:58:45 deploy-k8s-master k3s[11932]: E0113 17:58:45.803309   11932 scheduling_queue.go:1065] "Error while retrieving next pod from scheduling queue" err="scheduling queue is closed"
Jan 13 17:58:45 deploy-k8s-master k3s[11932]: time="2023-01-13T17:58:45+08:00" level=fatal msg="Tunnel watches failed to wait for RBAC: timed out waiting for the condition, "
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit k3s.service has entered the 'failed' state with result 'exit-code'.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: Stopped Lightweight Kubernetes.
-- Subject: Unit k3s.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit k3s.service has finished shutting down.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Found left-over process 9107 (containerd-shim) in control group while starting unit. Ignoring.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Found left-over process 10577 (containerd-shim) in control group while starting unit. Ignoring.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Found left-over process 10595 (containerd-shim) in control group while starting unit. Ignoring.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: k3s.service: Found left-over process 10610 (containerd-shim) in control group while starting unit. Ignoring.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 13 17:58:45 deploy-k8s-master systemd[1]: Starting Lightweight Kubernetes...
-- Subject: Unit k3s.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--

comment out manifests's ListFileIn method to avoid deploy
Jan 13 17:58:45 deploy-k8s-master k3s[11932]: time="2023-01-13T17:58:45+08:00" level=fatal msg="Tunnel watches failed to wait for RBAC: timed out waiting for the condition, "

You can't remove the RBAC manifest. It contains all the RBAC for the controllers embedded in K3s itself. If you're going to hack it out as you currently are, you are responsible for figure out how to get that same RBAC created by hand.