Motion Blur fixes

Implement 2 fixes on the Motion blur: 1) for Sprite and 2) for Instances + instanced bones. Fix in prepass PBR + standard and in the Gbuffer

For you @CraigFeldspar :-)

I would love to help!
Is it limited to prepass? Or is geometry buffer renderer should support it as well? The problem will still be visible using the geometry buffer renderer if not fixed

Thanks @julien-moreau! @CraigFeldspar is on it (and I believe this includes the geometry buffer renderer)

hi @julien-moreau , to allow the default clear color (0, 0, 0, 0) to be a neutral value for velocity, I was considering removing the mapping (-1, 1) => (0, 1) that we are performing on velocity values, since the velocity texture is already a FLOAT or HALF_FLOAT. Do you happen to think about any problem that may arise with that breaking change ?

Hey @CraigFeldspar that would be awesome to allow the clear color and remove the known limitation.
Anyway, I can't really answer now as I have to test it. This was added to ensure more precision in velocity values to avoid artifacts especially when the velocity has a small value.
I'm testing right now :)

@CraigFeldspar I can see some artifacts, including in large scenes. Filtering using the alpha value of the velocity buffer may do the trick, what do you think? like:
...
vec4 velocityColor = texture2D(velocitySampler, vUV);

 vec2 velocityxy = (velocityColor.rg * 2.0 - 1.0) * velocityColor.a;

vec2 velocity = vec2(pow(velocityxy.r, 3.0), pow(velocityxy.g, 3.0));
velocity *= motionScale * motionStrength;

...

actually @julien-moreau this is a really good solution, since we already use alpha channel to discriminate prepass-compatible pixels
Thanks a lot !

Fixed with https://github.com/BabylonJS/Babylon.js/pull/10180


monir: 添加国际化

Codecov Report

Merging #743 (94709dd) into v2.6.x_develop (45b872e) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop     #743   +/-   ##
===============================================
  Coverage           61.60%   61.60%
===============================================
  Files                 445      445
  Lines               28380    28380
===============================================
  Hits                17483    17483
  Misses              10897    10897

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45b872e...94709dd. Read the comment docs.


Temporary solution for FW uploading in windows

platformio.ini
[env:pico]
platform = raspberrypi
board = pico
framework = arduino
upload_protocol = mbed
upload_port = E:
platforms/raspberrypi/builder/main.py
`
if upload_protocol == "mbed":
upload_actions = [
    env.VerboseAction(env.AutodetectUploadPort, "Looking for upload disk..."),
    env.VerboseAction(env.UploadToDisk, "Uploading $SOURCE")
]`

must be replaced to
`
if upload_protocol == "mbed":
target_firm = join("$BUILD_DIR", "${PROGNAME}.uf2")
env.Replace(
    UPLOADER="copy",
    UPLOADERFLAGS=target_firm,
    UPLOADCMD="$UPLOADER $UPLOADERFLAGS $UPLOAD_PORT >NUL")
upload_actions = [env.VerboseAction("$UPLOADCMD", "Uploading $SOURCE")]

`
now uploading works!..

Thanks, but now I gave to unplug and hold the button. Is there any way to join both actions: forcing the board into bootsel from picotool and copying the file as you described?

upload_protocol = mbed upload is fixed by #36.

Is there any way to join both actions: forcing the board into bootsel from picotool and copying the file as you described?

Once a firmware from the Arduino core has been uploaded, it accepts a 1200bps reset-to-bootloader through the USB Serial interface it creates. Just delete any upload_protocol = .. line from the platformio.ini after, it's the default protocol.


Added base_url support for init_ol

Added the ability to specify the base_url for the OllamaLocal model, using default value of http://<IP_ADDRESS>:11434

@waywardspooky thanks for the change.


[BUG] GITHUB_TOKEN not working for GH Enterprise

🐛 Bug 描述 Bug description

All the actions are failing in GH Enterprise. Althought all the permissions are working for other github actions. We even add all the permissions for a PAT token.
  - name: Update Issue title
    uses<EMAIL_ADDRESS>    with:
      actions: 'update-issue'
      repo: ${{ github.repository }}
      token: ${{ secrets.GITHUB_TOKEN }}
      issue-number: ${{ github.event.issue.number }}
      state: 'open'
      title: "TEST: ${{ github.event.issue.title }}"
      update-mode: 'replace'
      labels: 'New-Label'

🏞 期望结果 Desired result
New title assigned.

New title assigned.
🚑 其他信息 Other information

RESULTS:
Run<EMAIL_ADDRESS>with:
actions: update-issue
repo: org/repo
token: ***
issue-number: xxxx
state: open
title: TEST: sddsdsd
update-mode: replace
labels: New-Label
[📝 AC] [Init] [org/repo => [4]
Error: [🚨 AC] Bad credentials

@Wxh16144 @ajuner try?


test-ibmcloud-rhel7-x64-1: MBCS_Tests_pref_ja_JP_linux_0 Can't locate Test/Simple.pm in @INC

Failing job link: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_special.functional_x86-64_linux_xl/19/consoleFull
Failing test targets:
MBCS_Tests_pref_ja_JP_linux_0
MBCS_Tests_pref_ko_KR_linux_0
MBCS_Tests_pref_zh_CN_linux_0
MBCS_Tests_pref_zh_TW_linux_0
MBCS_Tests_coin_ja_JP_linux_0
MBCS_Tests_coin_ko_KR_linux_0
MBCS_Tests_coin_zh_CN_linux_0
MBCS_Tests_coin_zh_TW_linux_0

Some tests are failing to run successfully on test-ibmcloud-rhel7-x64-1 because the Simple.pm perl module cannot be found:
09:41:49  ===============================================
09:41:49  Running test MBCS_Tests_pref_ja_JP_linux_0 ...
09:41:49  ===============================================
09:41:49  MBCS_Tests_pref_ja_JP_linux_0 Start Time: Wed Jan 20 03:41:49 2021 Epoch Time (ms):<PHONE_NUMBER>416
09:41:49  "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:destroyAll; "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:groupAccess,destroyAll; echo "cache cleanup done";
09:41:50  JVMSHRC005I No shared class caches available
09:41:50  JVMSHRC005I No shared class caches available
09:41:50  cache cleanup done
09:41:50  variation: NoOptions
09:41:50  JVM_OPTIONS:
09:41:50  { itercnt=1; \
09:41:50  mkdir -p "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../TKG/test_output_16111356913510/MBCS_Tests_pref_ja_JP_linux_0"; \
09:41:50  cd "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../TKG/test_output_16111356913510/MBCS_Tests_pref_ja_JP_linux_0"; \
09:41:50  LANG=ja_JP.UTF-8 bash /home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/test.sh; \
09:41:50  if [ $? -eq 0 ] ; then echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_PASSED"; echo ""; cd /home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/..; rm -f -r "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../TKG/test_output_16111356913510/MBCS_Tests_pref_ja_JP_linux_0"; else echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_FAILED"; echo ""; fi; } 2>&1 | tee -a "/home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../TKG/test_output_16111356913510/TestTargetResult";
09:41:50  Linux_ja_JP.UTF-8
09:41:52  Can't locate Test/Simple.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
09:41:52  BEGIN failed--compilation aborted at /home/jenkins/workspace/Test_openjdk8_j9_special.functional_x86-64_linux_xl/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
09:41:52
09:41:52  MBCS_Tests_pref_ja_JP_linux_0_FAILED

The tests run OK on other machines - e.g. test-aws-rhel8-x64-1 ( https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_special.functional_x86-64_linux_xl/18/consoleFull )

Also an issue for Hotspot 8 run: IBM RHEL 6 machine missing some prereqs for language tests.
[2021-01-18T14:16:48.058Z] Running test MBCS_Tests_pref_ja_JP_linux_0 ...
[2021-01-18T14:16:48.703Z] ===============================================
[2021-01-18T14:16:48.703Z] MBCS_Tests_pref_ja_JP_linux_0 Start Time: Mon Jan 18 08:16:48 2021 Epoch Time (ms):<PHONE_NUMBER>049
[2021-01-18T14:16:48.703Z] Nothing to be done for setup.
[2021-01-18T14:16:48.703Z] variation: NoOptions
[2021-01-18T14:16:48.703Z] JVM_OPTIONS:
[2021-01-18T14:16:48.703Z] { itercnt=1; \
[2021-01-18T14:16:48.703Z] mkdir -p "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/MBCS_Tests_pref_ja_JP_linux_0"; \
[2021-01-18T14:16:48.703Z] cd "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/MBCS_Tests_pref_ja_JP_linux_0"; \
[2021-01-18T14:16:48.703Z] LANG=ja_JP.UTF-8 bash /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/test.sh; \
[2021-01-18T14:16:48.703Z] if [ $? -eq 0 ] ; then echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_PASSED"; echo ""; cd /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/..;  else echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_FAILED"; echo ""; fi; } 2>&1 | tee -a "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/TestTargetResult";
[2021-01-18T14:16:48.703Z] Linux_ja_JP.UTF-8
[2021-01-18T14:16:50.029Z] Can't locate Test/Simple.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
[2021-01-18T14:16:50.029Z] BEGIN failed--compilation aborted at /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
[2021-01-18T14:16:50.029Z]
[2021-01-18T14:16:50.029Z] MBCS_Tests_pref_ja_JP_linux_0_FAILED
[2021-01-18T14:16:50.029Z]
[2021-01-18T14:16:50.029Z] Nothing to be done for teardown.
[2021-01-18T14:16:50.029Z] MBCS_Tests_pref_ja_JP_linux_0 Finish Time: Mon Jan 18 08:16:49 2021 Epoch Time (ms):<PHONE_NUMBER>627

Originally posted by @karianna in https://github.com/AdoptOpenJDK/TSC/issues/195#issuecomment-764545199

Also an issue for Hotspot 8 run: IBM RHEL 6 machine missing some prereqs for language tests.
[2021-01-18T14:16:48.058Z] Running test MBCS_Tests_pref_ja_JP_linux_0 ...
[2021-01-18T14:16:48.703Z] ===============================================
[2021-01-18T14:16:48.703Z] MBCS_Tests_pref_ja_JP_linux_0 Start Time: Mon Jan 18 08:16:48 2021 Epoch Time (ms):<PHONE_NUMBER>049
[2021-01-18T14:16:48.703Z] Nothing to be done for setup.
[2021-01-18T14:16:48.703Z] variation: NoOptions
[2021-01-18T14:16:48.703Z] JVM_OPTIONS:
[2021-01-18T14:16:48.703Z] { itercnt=1; \
[2021-01-18T14:16:48.703Z] mkdir -p "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/MBCS_Tests_pref_ja_JP_linux_0"; \
[2021-01-18T14:16:48.703Z] cd "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/MBCS_Tests_pref_ja_JP_linux_0"; \
[2021-01-18T14:16:48.703Z] LANG=ja_JP.UTF-8 bash /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/test.sh; \
[2021-01-18T14:16:48.703Z] if [ $? -eq 0 ] ; then echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_PASSED"; echo ""; cd /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/..;  else echo ""; echo "MBCS_Tests_pref_ja_JP_linux_0""_FAILED"; echo ""; fi; } 2>&1 | tee -a "/home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../TKG/test_output_16109794004215/TestTargetResult";
[2021-01-18T14:16:48.703Z] Linux_ja_JP.UTF-8
[2021-01-18T14:16:50.029Z] Can't locate Test/Simple.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
[2021-01-18T14:16:50.029Z] BEGIN failed--compilation aborted at /home/jenkins/workspace/Test_openjdk8_hs_special.functional_x86-64_linux/openjdk-tests/TKG/../../jvmtest/functional/MBCS_Tests/pref/tap_compare.pl line 16.
[2021-01-18T14:16:50.029Z]
[2021-01-18T14:16:50.029Z] MBCS_Tests_pref_ja_JP_linux_0_FAILED
[2021-01-18T14:16:50.029Z]
[2021-01-18T14:16:50.029Z] Nothing to be done for teardown.
[2021-01-18T14:16:50.029Z] MBCS_Tests_pref_ja_JP_linux_0 Finish Time: Mon Jan 18 08:16:49 2021 Epoch Time (ms):<PHONE_NUMBER>627

Originally posted by @karianna in https://github.com/AdoptOpenJDK/TSC/issues/195#issuecomment-764545199

Ive installed the Test::Simple module onto the failing machine, test-ibmcloud-rhel7-x64-1. Rerunning at https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_special.functional_x86-64_linux_xl/22/console to see if it solves it. If so, ill add the module to the playbooks

The previous job failed due to a compilation error. Ive rebuilt this in a grinder https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/6735/console @lumpfish Could you double check the parameters of my grinder. Im sure theyre fine, but I always have trouble recreating nighly test runs in a grinder

Grinder passed. I also recreated the error on the failing machine @karianna mentioned, test-ibmcloud-rhel6-x64-1.
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/6736/tapTestReport/

15:13:14  FAILED test targets:
15:13:14  	MBCS_Tests_pref_ja_JP_linux_0
15:13:14  	MBCS_Tests_pref_ko_KR_linux_0
15:13:14  	MBCS_Tests_pref_zh_CN_linux_0
15:13:14  	MBCS_Tests_pref_zh_TW_linux_0
15:13:14  	MBCS_Tests_coin_ja_JP_linux_0
15:13:14  	MBCS_Tests_coin_ko_KR_linux_0
15:13:14  	MBCS_Tests_coin_zh_CN_linux_0
15:13:14  	MBCS_Tests_coin_zh_TW_linux_0

Then after installing Test::Simple, https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/6737/console. No failed targets

Ive added the perl module to the playbooks. Closing this issue


cc reward harvesting

View and interact with CC vesting contract from staking page.

Access like kwenta.eth.limo/dashboard/staking/?ccAddress=<VESTING_CONTRACT_ADDR>
Click claim to harvest rewards
And use stake escrow with any amount set to stake all of your available escrowed Kwenta

Works perfectly, would just like to have the two GitHub code scanning issues addressed before merging (if relevant).


Expose nested namespace as standalone route does not work in swagger ui 2.1.4 and grape-swagger 0.20

See documentation at https://github.com/ruby-grape/grape-swagger#expose-nested-namespace-as-standalone-route.
Functionality was added by #220.
The original code snippet is still enabled and the documentation also describes this feature, but all the tests were not migrated to version 0.20.

@stefan-kolb as I understand it right, the nickname key has to be re-added, right?

I don't really know what is needed to reenable/fix this functionality as I didn't write it before. But I cannot see any nickname key inside this functionality or code, so I'm not sure if this is related or the cause for this issue.

@stefan-kolb … I see it here #220/files and this has nothings to do with the nickname …
but I think your referenced issue could be solved be re-adding it

You should probably re-add the tests api_with_standalone_namespace_spec.rb, so you can debug whats going wrong here. As far as I know the tests were removed between the transition from 0.11 to 0.20.

Hi, any update on this? It is not working for us.

This is causing major pain for us as well

feel free to make a PR to fix it


Add load commandclass test and compat file

I added a test to check if management command classes can be loaded in every environment.
To fix import errors revealed by this new test I added a compat.py file to gather compatibility code between python versions(and maybe also between django versions ). With this it could be simpler to remove unused compatibility code in the future.

Coverage increased (+13.93%) to 28.65% when pulling ca5ed6c920c3ed3fa0766e328963e635be81ff2a on benjaminabel:add-load-commandclass-test into 25a8fd7ff88db093aead012bc60e0fdfd981cb70 on django-extensions:master.

Thanks you rocking it man :)

It seems that coveralls liked the for loop;)


Add more options when the program create the Application on CF

It is necessary to improve the options to create an App.
http://apidocs.cloudfoundry.org/218/apps/creating_an_app.html
A good improvement, could be if the method accept this new parameters:
memory	1024 512
instances	2 6 10
disk_quota 1204 2048
```

it is necessary to update the method:
Apps.prototype.createApp = function (token_type, access_token, name, space_guid, buildPack) {
In the next release, the method will accept a option var which add the following options:
memory  1024 512
instances   2 6 10
disk_quota 1204 2048
the rest of parameters are optionals

The developer should know the rights values:
https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#disk-quota
https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#instances
https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#memory

Finally, the syntaxis is:
Apps.prototype.create = function (token_type, access_token, appOptions) {


Changing an exported skill before finalizing it in another project breaks the skill's connection

How to recreate:

Create two projects, Proj 1 and Proj 2
Create a skill in Proj 1, then export it to the Catalog
In Proj 2, import the skill, but do not finalize
Return to Proj 1 and go to the Skill
Edit the Skill's point value and save
Return to Project 2

Finalization message will now be gone, the imported skill will still be present but won't retain the linked info from the original project (such as user completion), but will still say that it's an imported skill

PR #2060

:+1:


configs/config.json absent from installation instructions

Hi,
When doing a run, if the configs/config.json is not done, this is faced:
Traceback (most recent call last):
  File "/progs/all/opensource/reinvent/3.0/source/input.py", line 20, in <module>
    manager = Manager(configuration)
  File "/progs/all/opensource/reinvent/3.0/source/running_modes/manager.py", line 13, in __init__
    self._load_environmental_variables()
  File "/progs/all/opensource/reinvent/3.0/source/running_modes/manager.py", line 22, in _load_environmental_variables
    with open(os.path.join(project_root, '../configs/config.json'), 'r') as f:

It is mentioned on the README.md, but only on the Tests section, which can be misleading when installing Reinvent. Very minor, but thought I should mention it.

Thanks, yeah I realized this isnt very clear as I got quite the number of related issues.

Same error happens to me. Seems there's an error with the defult config file.
The question is where is the corrent path?

I found a same issue, which has a solution.
https://github.com/MolecularAI/Reinvent/issues/35


[BUG] AI | hide 3 dots, fix input field mode for not logged in user

Describe the bug

[ ] hide the three dots icon, until we will add functionality

[ ] fix input field -  it doesn't respond when user is not logged in. When user clicks / focus on it open existing window of login

The window that asks the user to login:

To Reproduce
Go to AI page
Expected Behavior
No response
Screenshot/ Video
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi can i be assigned?

@ArkadiK94 can i look at it ?

@SandipGyawali Yeah sure, if you have any questions don't hesitate to ask :)

Can I look at it ??

@dev-px someone is already assigned to it.

@dev-px you can try one of the other issues which no one is assigned to.

@dev-px https://github.com/thecyberworld/TheCyberHUB/issues/560
would you like to work on issue 560?


Form loses font format

I've got a pdf with a form and custom fonts and colors.
When I convert the file to jpg or png, the form is losing the format.
What's wrong?

@psjavi Could you elaborate a bit?

Is it not carrying over the fonts, the colors, or both?
Is this within the form, or throughout the document?
Is it just when converting to jpg or png, or also webp?

Thanks for reporting the issue! :+1:

Hi,
I discovered that is a problem with imagick command directly. I've had to change the package and use directly pdftoppm instead of imagick.

pdftoppm works. If there is garble in the text, use fc-list :lang=xxx to check that the system has installed the corresponding font.


Single VM Dev: Provide absolute path

Provide absolute path for all ciao* commands. If this is not
done the OS environment path will be picked up, potentially picking
up a stale version of ciao* commands
Signed-off-by: Manohar Castelino<EMAIL_ADDRESS>

Coverage decreased (-0.007%) to 60.834% when pulling d2c7968ffbee8a583242a0e78a592c0b7844e035 on mcastelino:topic/bugfix into 502703f8aa63a1ba6098a2afe4029bd98f2587ab on 01org:master.

Coverage increased (+0.02%) to 60.863% when pulling 51709bcff0600f86ee91a1e9c54d60c8782eaffc on mcastelino:topic/bugfix into 502703f8aa63a1ba6098a2afe4029bd98f2587ab on 01org:master.

Coverage increased (+0.02%) to 60.863% when pulling f10b1e472095730aa35f49c0aa0cf83fed16e304 on mcastelino:topic/bugfix into 502703f8aa63a1ba6098a2afe4029bd98f2587ab on 01org:master.


(PDOC-25) Fix mangled puppet namespaces

Prior to this commit, puppet namespaces would be totally mangled when
processed by YARD since YARD is looking for Ruby namespaces where the
first letter of each segment must be uppercase.
In order to fix this, patch the relevant regular expression constants
in YARD so that they will accept segments that begin with uppercase
and lowercase letters.
An upstream pull request has been accepted into YARD to add another
regex constant which is necessary to complete this patch. However until
the next version of the YARD gem is released, we must include a temporary
hack to fix the problematic method in question (as it is not yet using
the added variable). Once the new version is released, the conditional
statement in code_ext/yard.rb can be removed entirely and all we will
need to do is patch the two regex constants.

Actually, please don't merge this just yet. I want to add a quick test to prevent regressions.

Okay, this is ready for review! :+1:


Mod UI freeze up

First, thanks, great job. Found this right when I started Duna and immediately fired 4 sat payload to map it and Ike, fun mission, and scans work well.
Adding a waypoint after scan complete causes all mod GUIs except the map to stop responding, this is also for other mods, and this persists until reloading the game.
Also can't delete waypoint because of this.
Mod ver 0.9.4
Game ver <IP_ADDRESS>

Suddenly started working, not sure what changed, didn't update anything, maybe mod reset in menus.

If it happens again please see if you can determine what exact steps are needed to produce that as I haven't noticed this behavior again. Except that sometimes, on a rare occasion, interracting with textfield controls can cause the entire UI to lock up. But I couldn't reproduce that consistently.

I did get it one more time, it's something with right clicking an existing waypoint, I still don't know what the situation is, but when it happens, right clicking the waypoint, the remove button is missing, and then the ui gets stuck in unresponsive.


tipAttribute is not working properly

tipAttribute is not working when it takes value other then htmlooltip.
For example,
<core-tooltip tipAttribute="abcd">

Example of a rich information tooltip

       ...

</core-tooltip>

This issue was moved to Polymer/core-tooltip#26

@ebidel thanks :-)


bugfix: 'sealos run' cannot scale cluster

close #2352

test : (success to scale cluster)
root@lmaster:~# sealos run labring/kubernetes:v1.24.0 labring/calico:v3.22.1 --masters <IP_ADDRESS> --nodes <IP_ADDRESS>
2023-01-10T13:19:53 info Start to create a new cluster: master [<IP_ADDRESS>], worker [<IP_ADDRESS>], registry <IP_ADDRESS>
2023-01-10T13:19:53 info Executing pipeline Check in CreateProcessor.
2023-01-10T13:19:53 info checker:hostname [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-10T13:19:54 info checker:timeSync [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-10T13:19:54 info Executing pipeline PreProcess in CreateProcessor.
Resolving "labring/kubernetes" using unqualified-search registries (/etc/containers/registries.conf)
Trying to pull docker.io/labring/kubernetes:v1.24.0...
Getting image source signatures
Copying blob 1c9329ccec9f skipped: already exists
Copying blob bdd36b01a648 done
Copying blob cd1ebf8dc46e skipped: already exists
Copying blob 657efefb3eac skipped: already exists
Copying config 945b186831 done
Writing manifest to image destination
Storing signatures
2023-01-10T13:20:21 info Executing pipeline RunConfig in CreateProcessor.
2023-01-10T13:20:21 info Executing pipeline MountRootfs in CreateProcessor.
2023-01-10T13:20:44 info Executing pipeline MirrorRegistry in CreateProcessor.
2023-01-10T13:20:44 info Executing pipeline Bootstrap in CreateProcessor
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:45] >> check root,port,cri success
 INFO [2023-01-10 13:20:54] >> check root,port,cri success
chmod: cannot operate on dangling symlink '/usr/bin/rust-clang'
chmod: cannot operate on dangling symlink '/usr/bin/rust-lld'
chmod: cannot operate on dangling symlink '/usr/bin/rust-llvm-dwp'
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
 INFO [2023-01-10 13:20:56] >> Health check containerd!
 INFO [2023-01-10 13:20:56] >> containerd is running
 INFO [2023-01-10 13:20:56] >> init containerd success
chmod: cannot operate on dangling symlink '/usr/bin/rust-clang'
chmod: cannot operate on dangling symlink '/usr/bin/rust-lld'
chmod: cannot operate on dangling symlink '/usr/bin/rust-llvm-dwp'
Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> Health check containerd!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> containerd is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> init containerd success
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
 INFO [2023-01-10 13:20:56] >> Health check image-cri-shim!
 INFO [2023-01-10 13:20:56] >> image-cri-shim is running
 INFO [2023-01-10 13:20:56] >> init shim success
<IP_ADDRESS> localhost
::1 localhost ip6-localhost ip6-loopback
* Applying /etc/sysctl.d/10-console-messages.conf ...
kernel.printk = 4 4 1 7
* Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
* Applying /etc/sysctl.d/10-kernel-hardening.conf ...
kernel.kptr_restrict = 1
* Applying /etc/sysctl.d/10-magic-sysrq.conf ...
kernel.sysrq = 176
* Applying /etc/sysctl.d/10-network-security.conf ...
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.all.rp_filter = 2
* Applying /etc/sysctl.d/10-ptrace.conf ...
kernel.yama.ptrace_scope = 1
* Applying /etc/sysctl.d/10-zeropage.conf ...
vm.mmap_min_addr = 32768
* Applying /usr/lib/sysctl.d/50-default.conf ...
kernel.core_uses_pid = 1
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.default.accept_source_route = 0
sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
net.ipv4.conf.default.promote_secondaries = 1
sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument
net.ipv4.ping_group_range = 0<PHONE_NUMBER>
net.core.default_qdisc = fq_codel
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
fs.protected_regular = 1
fs.protected_fifos = 1
* Applying /usr/lib/sysctl.d/50-pid-max.conf ...
kernel.pid_max = 4194304
* Applying /etc/sysctl.d/99-cloudimg-ipv6.conf ...
net.ipv6.conf.all.use_tempaddr = 0
net.ipv6.conf.default.use_tempaddr = 0
* Applying /usr/lib/sysctl.d/99-protect-links.conf ...
fs.protected_fifos = 1
fs.protected_hardlinks = 1
fs.protected_regular = 2
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.conf.all.rp_filter = 0
* Applying /etc/sysctl.conf ...
net.ipv4.ip_forward = 1
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> Health check image-cri-shim!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> image-cri-shim is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:56] >> init shim success
Firewall stopped and disabled on system startup
<IP_ADDRESS>:22: <IP_ADDRESS> localhost
<IP_ADDRESS>:22: ::1 localhost ip6-localhost ip6-loopback
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-console-messages.conf ...
<IP_ADDRESS>:22: kernel.printk = 4 4 1 7
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 2
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-kernel-hardening.conf ...
<IP_ADDRESS>:22: kernel.kptr_restrict = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-magic-sysrq.conf ...
<IP_ADDRESS>:22: kernel.sysrq = 176
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-network-security.conf ...
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ptrace.conf ...
<IP_ADDRESS>:22: kernel.yama.ptrace_scope = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-zeropage.conf ...
<IP_ADDRESS>:22: vm.mmap_min_addr = 32768
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-default.conf ...
<IP_ADDRESS>:22: kernel.core_uses_pid = 1
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.default.accept_source_route = 0
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
<IP_ADDRESS>:22: net.ipv4.conf.default.promote_secondaries = 1
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument
<IP_ADDRESS>:22: net.ipv4.ping_group_range = 0<PHONE_NUMBER>
<IP_ADDRESS>:22: net.core.default_qdisc = fq_codel
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 1
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-pid-max.conf ...
<IP_ADDRESS>:22: kernel.pid_max = 4194304
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-cloudimg-ipv6.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 0
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 0
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/99-protect-links.conf ...
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 2
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-sysctl.conf ...
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/k8s.conf ...
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-ip6tables = 1
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-iptables = 1
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 0
<IP_ADDRESS>:22: * Applying /etc/sysctl.conf ...
<IP_ADDRESS>:22: net.ipv4.ip_forward = 1
<IP_ADDRESS>:22: Firewall stopped and disabled on system startup
 INFO [2023-01-10 13:20:57] >> init kube success
 INFO [2023-01-10 13:20:57] >> init rootfs success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:57] >> init kube success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:20:57] >> init rootfs success
chmod: cannot operate on dangling symlink '/usr/bin/rust-clang'
chmod: cannot operate on dangling symlink '/usr/bin/rust-lld'
chmod: cannot operate on dangling symlink '/usr/bin/rust-llvm-dwp'
Created symlink /etc/systemd/system/multi-user.target.wants/registry.service → /etc/systemd/system/registry.service.
 INFO [2023-01-10 13:20:58] >> Health check registry!
 INFO [2023-01-10 13:20:58] >> registry is running
 INFO [2023-01-10 13:20:58] >> init registry success
2023-01-10T13:20:58 info Executing pipeline Init in CreateProcessor.
2023-01-10T13:20:58 info start to copy kubeadm config to master0
2023-01-10T13:20:59 info start to generate cert and kubeConfig...
2023-01-10T13:20:59 info start to generator cert and copy to masters...
2023-01-10T13:20:59 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local lmaster:lmaster localhost:localhost] map[<IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS>]}
2023-01-10T13:20:59 info Etcd altnames : {map[lmaster:lmaster localhost:localhost] map[<IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> ::1:::1]}, commonName : lmaster
2023-01-10T13:21:00 info start to copy etc pki files to masters
2023-01-10T13:21:00 info start to copy etc pki files to masters
2023-01-10T13:21:00 info start to create kubeconfig...
2023-01-10T13:21:01 info start to copy kubeconfig files to masters
2023-01-10T13:21:01 info start to copy static files to masters
2023-01-10T13:21:01 info start to init master0...
2023-01-10T13:21:01 info registry auth in node <IP_ADDRESS>:22
2023-01-10T13:21:01 info domain sealos.hub:<IP_ADDRESS> append success
2023-01-10T13:21:02 info domain apiserver.cluster.local:<IP_ADDRESS> append success
W0110 13:21:02.181775    2269 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
W0110 13:21:02.181832    2269 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
[init] Using Kubernetes version: v1.24.0
[preflight] Running pre-flight checks
	[WARNING SystemVerification]: missing optional cgroups: blkio
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[certs] Using the existing "sa" key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/kubelet.conf"
W0110 13:21:12.556602    2269 kubeconfig.go:249] a kubeconfig file "/etc/kubernetes/controller-manager.conf" exists already but has an unexpected API Server URL: expected: https://<IP_ADDRESS>:6443, got: https://apiserver.cluster.local:6443
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
W0110 13:21:12.880629    2269 kubeconfig.go:249] a kubeconfig file "/etc/kubernetes/scheduler.conf" exists already but has an unexpected API Server URL: expected: https://<IP_ADDRESS>:6443, got: https://apiserver.cluster.local:6443
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 5.512987 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node lmaster as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node lmaster as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

You can now join any number of control-plane nodes by copying certificate authorities
and service account keys on each node and then running the following as root:

  kubeadm join apiserver.cluster.local:6443 --token <value withheld> \
	--discovery-token-ca-cert-hash sha256:d87523b9f05fba690bc881a20143d19304fad6dce0ca91f5b45f1ca896bffffa \
	--control-plane --certificate-key <value withheld>

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join apiserver.cluster.local:6443 --token <value withheld> \
	--discovery-token-ca-cert-hash sha256:d87523b9f05fba690bc881a20143d19304fad6dce0ca91f5b45f1ca896bffffa
2023-01-10T13:21:20 info Executing pipeline Join in CreateProcessor.
2023-01-10T13:21:20 info [<IP_ADDRESS>:22] will be added as worker
2023-01-10T13:21:20 info start to get kubernetes token...
2023-01-10T13:21:23 info start to join <IP_ADDRESS>:22 as worker
2023-01-10T13:21:23 info start to copy kubeadm join config to node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:21:25 info domain apiserver.cluster.local:<IP_ADDRESS> append success
<IP_ADDRESS>:22: 2023-01-10T13:21:25 info domain lvscare.node.ip:<IP_ADDRESS> append success
2023-01-10T13:21:25 info registry auth in node <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:21:26 info domain sealos.hub:<IP_ADDRESS> append success
2023-01-10T13:21:26 info run ipvs once module: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:21:26 info Trying to add route
<IP_ADDRESS>:22: 2023-01-10T13:21:26 info success to set route.(host:<IP_ADDRESS>, gateway:<IP_ADDRESS>)
2023-01-10T13:21:26 info start join node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: W0110 13:21:26.973895    6689 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
<IP_ADDRESS>:22: [preflight] Running pre-flight checks
<IP_ADDRESS>:22: 	[WARNING SystemVerification]: missing optional cgroups: blkio
<IP_ADDRESS>:22: [preflight] Reading configuration from the cluster...
<IP_ADDRESS>:22: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
<IP_ADDRESS>:22: W0110 13:21:39.486807    6689 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22: [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: This node has joined the cluster:
<IP_ADDRESS>:22: * Certificate signing request was sent to apiserver and a response was received.
<IP_ADDRESS>:22: * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
<IP_ADDRESS>:22:
2023-01-10T13:21:53 info succeeded in joining <IP_ADDRESS>:22 as worker
2023-01-10T13:21:53 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443]
<IP_ADDRESS>:22: 2023-01-10T13:21:54 info generator lvscare static pod is success
2023-01-10T13:21:54 info Executing pipeline RunGuest in CreateProcessor.
customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/caliconodestatuses.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/ipreservations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io created
customresourcedefinition.apiextensions.k8s.io/imagesets.operator.tigera.io created
customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io created
customresourcedefinition.apiextensions.k8s.io/tigerastatuses.operator.tigera.io created
namespace/tigera-operator created
Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
podsecuritypolicy.policy/tigera-operator created
serviceaccount/tigera-operator created
clusterrole.rbac.authorization.k8s.io/tigera-operator created
clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created
deployment.apps/tigera-operator created
installation.operator.tigera.io/default created
2023-01-10T13:21:58 info succeeded in creating a new cluster, enjoy it!
2023-01-10T13:21:58 info
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website :https://www.sealos.io/
                  Address :github.com/labring/sealos
		BuildVersion: latest-

root@lmaster:~# kubectl get nodes
NAME      STATUS   ROLES           AGE    VERSION
lmaster   Ready    control-plane   107s   v1.24.0
node1     Ready    <none>          72s    v1.24.0
root@lmaster:~# sealos run labring/helm:v3.8.2 --masters <IP_ADDRESS> --nodes <IP_ADDRESS>
2023-01-10T13:23:07 info start to install app in this cluster
2023-01-10T13:23:11 info Executing pipeline MountRootfs in InstallProcessor.
2023-01-10T13:23:11 info Executing pipeline MirrorRegistry in InstallProcessor.
2023-01-10T13:23:11 info Executing UpgradeIfNeed Pipeline in InstallProcessor
2023-01-10T13:23:11 info succeeded install app in this cluster
2023-01-10T13:23:11 info start to scale this cluster
2023-01-10T13:23:11 info Executing pipeline JoinCheck in ScaleProcessor.
2023-01-10T13:23:12 info checker:hostname [<IP_ADDRESS>:22 <IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-10T13:23:12 info checker:timeSync [<IP_ADDRESS>:22 <IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-10T13:23:13 info Executing pipeline PreProcess in ScaleProcessor.
2023-01-10T13:23:13 info Executing pipeline PreProcessImage in ScaleProcessor.
2023-01-10T13:23:13 info Executing pipeline RunConfig in ScaleProcessor.
2023-01-10T13:23:13 info Executing pipeline MountRootfs in ScaleProcessor.
2023-01-10T13:23:36 info Executing pipeline Bootstrap in ScaleProcessort/s)
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:36] >> check root,port,cri success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:36] >> check root,port,cri success
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> Health check containerd!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> Health check containerd!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> containerd is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> init containerd success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> containerd is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:38] >> init containerd success
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> Health check image-cri-shim!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> image-cri-shim is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> Health check image-cri-shim!
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> init shim success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> image-cri-shim is running
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:39] >> init shim success
<IP_ADDRESS>:22: <IP_ADDRESS> localhost
<IP_ADDRESS>:22: ::1 localhost ip6-localhost ip6-loopback
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-console-messages.conf ...
<IP_ADDRESS>:22: kernel.printk = 4 4 1 7
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 2
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-kernel-hardening.conf ...
<IP_ADDRESS>:22: kernel.kptr_restrict = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-magic-sysrq.conf ...
<IP_ADDRESS>:22: kernel.sysrq = 176
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-network-security.conf ...
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ptrace.conf ...
<IP_ADDRESS>:22: kernel.yama.ptrace_scope = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-zeropage.conf ...
<IP_ADDRESS>:22: vm.mmap_min_addr = 32768
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-default.conf ...
<IP_ADDRESS>:22: kernel.core_uses_pid = 1
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.default.accept_source_route = 0
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
<IP_ADDRESS>:22: net.ipv4.conf.default.promote_secondaries = 1
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument
<IP_ADDRESS>:22: net.ipv4.ping_group_range = 0<PHONE_NUMBER>
<IP_ADDRESS>:22: net.core.default_qdisc = fq_codel
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 1
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-pid-max.conf ...
<IP_ADDRESS>:22: kernel.pid_max = 4194304
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-cloudimg-ipv6.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 0
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 0
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/99-protect-links.conf ...
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 2
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-sysctl.conf ...
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/k8s.conf ...
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-ip6tables = 1
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-iptables = 1
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 0
<IP_ADDRESS>:22: * Applying /etc/sysctl.conf ...
<IP_ADDRESS>:22: net.ipv4.ip_forward = 1
<IP_ADDRESS>:22: <IP_ADDRESS> localhost
<IP_ADDRESS>:22: ::1 localhost ip6-localhost ip6-loopback
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-console-messages.conf ...
<IP_ADDRESS>:22: kernel.printk = 4 4 1 7
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 2
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-kernel-hardening.conf ...
<IP_ADDRESS>:22: kernel.kptr_restrict = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-magic-sysrq.conf ...
<IP_ADDRESS>:22: kernel.sysrq = 176
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-network-security.conf ...
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ptrace.conf ...
<IP_ADDRESS>:22: kernel.yama.ptrace_scope = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-zeropage.conf ...
<IP_ADDRESS>:22: vm.mmap_min_addr = 32768
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-default.conf ...
<IP_ADDRESS>:22: kernel.core_uses_pid = 1
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.default.accept_source_route = 0
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
<IP_ADDRESS>:22: net.ipv4.conf.default.promote_secondaries = 1
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument
<IP_ADDRESS>:22: net.ipv4.ping_group_range = 0<PHONE_NUMBER>
<IP_ADDRESS>:22: net.core.default_qdisc = fq_codel
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 1
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-pid-max.conf ...
<IP_ADDRESS>:22: kernel.pid_max = 4194304
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-cloudimg-ipv6.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 0
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 0
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/99-protect-links.conf ...
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 2
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-sysctl.conf ...
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/k8s.conf ...
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-ip6tables = 1
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-iptables = 1
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 0
<IP_ADDRESS>:22: * Applying /etc/sysctl.conf ...
<IP_ADDRESS>:22: net.ipv4.ip_forward = 1
<IP_ADDRESS>:22: Firewall stopped and disabled on system startup
<IP_ADDRESS>:22: Firewall stopped and disabled on system startup
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:40] >> init kube success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:40] >> init rootfs success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:40] >> init kube success
<IP_ADDRESS>:22:  INFO [2023-01-10 13:23:40] >> init rootfs success
2023-01-10T13:23:40 info Executing pipeline Join in ScaleProcessor.
2023-01-10T13:23:40 info [<IP_ADDRESS>:22] will be added as master
2023-01-10T13:23:40 info start to init filesystem join masters...
2023-01-10T13:23:40 info start to copy static files to masters
2023-01-10T13:23:40 info start to copy kubeconfig files to masters
2023-01-10T13:23:41 info start to copy etc pki files to masters/1, 6 it/s)
2023-01-10T13:23:45 info start to get kubernetes token...
2023-01-10T13:23:45 info start to copy kubeadm join config to master: <IP_ADDRESS>:22
2023-01-10T13:23:46 info start to join <IP_ADDRESS>:22 as master1, 6 it/s)
2023-01-10T13:23:46 info registry auth in node <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:23:47 info domain sealos.hub:<IP_ADDRESS> append success
2023-01-10T13:23:47 info start to generator cert <IP_ADDRESS>:22 as master
<IP_ADDRESS>:22: 2023-01-10T13:23:48 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local lmaster1:lmaster1 localhost:localhost] map[<IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS>]}
<IP_ADDRESS>:22: 2023-01-10T13:23:48 info Etcd altnames : {map[lmaster1:lmaster1 localhost:localhost] map[<IP_ADDRESS>:<IP_ADDRESS> <IP_ADDRESS>:<IP_ADDRESS> ::1:::1]}, commonName : lmaster1
<IP_ADDRESS>:22: 2023-01-10T13:23:48 info sa.key sa.pub already exist
<IP_ADDRESS>:22: 2023-01-10T13:23:50 info domain apiserver.cluster.local:<IP_ADDRESS> append success
<IP_ADDRESS>:22: W0110 13:23:50.256521    7568 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
<IP_ADDRESS>:22: [preflight] Running pre-flight checks
<IP_ADDRESS>:22: 	[WARNING FileExisting-socat]: socat not found in system path
<IP_ADDRESS>:22: 	[WARNING SystemVerification]: missing optional cgroups: blkio
<IP_ADDRESS>:22: [preflight] Reading configuration from the cluster...
<IP_ADDRESS>:22: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
<IP_ADDRESS>:22: W0110 13:23:50.427170    7568 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
<IP_ADDRESS>:22: [preflight] Running pre-flight checks before initializing the new control plane instance
<IP_ADDRESS>:22: [preflight] Pulling images required for setting up a Kubernetes cluster
<IP_ADDRESS>:22: [preflight] This might take a minute or two, depending on the speed of your internet connection
<IP_ADDRESS>:22: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
<IP_ADDRESS>:22: [download-certs] Downloading the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
<IP_ADDRESS>:22: [certs] Using certificateDir folder "/etc/kubernetes/pki"
<IP_ADDRESS>:22: [certs] Using the existing "front-proxy-client" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "etcd/server" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "etcd/peer" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "etcd/healthcheck-client" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "apiserver-etcd-client" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "apiserver" certificate and key
<IP_ADDRESS>:22: [certs] Using the existing "apiserver-kubelet-client" certificate and key
<IP_ADDRESS>:22: [certs] Valid certificates and keys now exist in "/etc/kubernetes/pki"
<IP_ADDRESS>:22: [certs] Using the existing "sa" key
<IP_ADDRESS>:22: [kubeconfig] Generating kubeconfig files
<IP_ADDRESS>:22: [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
<IP_ADDRESS>:22: [kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
<IP_ADDRESS>:22: W0110 13:24:02.309558    7568 kubeconfig.go:249] a kubeconfig file "/etc/kubernetes/controller-manager.conf" exists already but has an unexpected API Server URL: expected: https://<IP_ADDRESS>:6443, got: https://apiserver.cluster.local:6443
<IP_ADDRESS>:22: [kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
<IP_ADDRESS>:22: W0110 13:24:02.407099    7568 kubeconfig.go:249] a kubeconfig file "/etc/kubernetes/scheduler.conf" exists already but has an unexpected API Server URL: expected: https://<IP_ADDRESS>:6443, got: https://apiserver.cluster.local:6443
<IP_ADDRESS>:22: [kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
<IP_ADDRESS>:22: [control-plane] Using manifest folder "/etc/kubernetes/manifests"
<IP_ADDRESS>:22: [control-plane] Creating static Pod manifest for "kube-apiserver"
<IP_ADDRESS>:22: [control-plane] Creating static Pod manifest for "kube-controller-manager"
<IP_ADDRESS>:22: [control-plane] Creating static Pod manifest for "kube-scheduler"
<IP_ADDRESS>:22: [check-etcd] Checking that the etcd cluster is healthy
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22: [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22: [etcd] Announced new etcd member joining to the existing etcd cluster
<IP_ADDRESS>:22: [etcd] Creating static Pod manifest for "etcd"
<IP_ADDRESS>:22: [etcd] Waiting for the new etcd member to join the cluster. This can take up to 40s
<IP_ADDRESS>:22: The 'update-status' phase is deprecated and will be removed in a future release. Currently it performs no operation
<IP_ADDRESS>:22: [mark-control-plane] Marking the node lmaster1 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
<IP_ADDRESS>:22: [mark-control-plane] Marking the node lmaster1 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule node-role.kubernetes.io/control-plane:NoSchedule]
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: This node has joined the cluster and a new control plane instance was created:
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: * Certificate signing request was sent to apiserver and approval was received.
<IP_ADDRESS>:22: * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22: * Control plane label and taint were applied to the new node.
<IP_ADDRESS>:22: * The Kubernetes control plane instances scaled up.
<IP_ADDRESS>:22: * A new etcd member was added to the local/stacked etcd cluster.
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: To start administering your cluster from this node, you need to run the following as a regular user:
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: 	mkdir -p $HOME/.kube
<IP_ADDRESS>:22: 	sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
<IP_ADDRESS>:22: 	sudo chown $(id -u):$(id -g) $HOME/.kube/config
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: Run 'kubectl get nodes' to see this node join the cluster.
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: 2023-01-10T13:24:26 info domain apiserver.cluster.local delete success
<IP_ADDRESS>:22: 2023-01-10T13:24:26 info domain apiserver.cluster.local:<IP_ADDRESS> append success
2023-01-10T13:24:26 info succeeded in joining <IP_ADDRESS>:22 as master
2023-01-10T13:24:26 info [<IP_ADDRESS>:22] will be added as worker
2023-01-10T13:24:27 info start to get kubernetes token...
2023-01-10T13:24:27 info start to join <IP_ADDRESS>:22 as worker
2023-01-10T13:24:27 info start to copy kubeadm join config to node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:24:29 info domain apiserver.cluster.local:<IP_ADDRESS> append success
<IP_ADDRESS>:22: 2023-01-10T13:24:29 info domain lvscare.node.ip:<IP_ADDRESS> append success
2023-01-10T13:24:29 info registry auth in node <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:24:30 info domain sealos.hub:<IP_ADDRESS> append success
2023-01-10T13:24:30 info run ipvs once module: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-10T13:24:30 info Trying to add route
<IP_ADDRESS>:22: 2023-01-10T13:24:30 info success to set route.(host:<IP_ADDRESS>, gateway:<IP_ADDRESS>)
2023-01-10T13:24:30 info start join node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: W0110 13:24:30.886892    6002 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
<IP_ADDRESS>:22: [preflight] Running pre-flight checks
<IP_ADDRESS>:22: 	[WARNING FileExisting-socat]: socat not found in system path
<IP_ADDRESS>:22: 	[WARNING SystemVerification]: missing optional cgroups: blkio
<IP_ADDRESS>:22: [preflight] Reading configuration from the cluster...
<IP_ADDRESS>:22: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
<IP_ADDRESS>:22: W0110 13:24:31.100025    6002 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22: [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: This node has joined the cluster:
<IP_ADDRESS>:22: * Certificate signing request was sent to apiserver and a response was received.
<IP_ADDRESS>:22: * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
<IP_ADDRESS>:22:
2023-01-10T13:24:44 info succeeded in joining <IP_ADDRESS>:22 as worker
2023-01-10T13:24:45 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443 <IP_ADDRESS>:6443]
2023-01-10T13:24:45 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443 <IP_ADDRESS>:6443]
<IP_ADDRESS>:22: 2023-01-10T13:24:45 info generator lvscare static pod is success
<IP_ADDRESS>:22: 2023-01-10T13:24:46 info generator lvscare static pod is success
2023-01-10T13:24:46 info succeeded in scaling this cluster
2023-01-10T13:24:46 info
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website :https://www.sealos.io/
                  Address :github.com/labring/sealos
		BuildVersion: latest-

root@lmaster:~# kubectl get nodes
NAME       STATUS   ROLES           AGE     VERSION
lmaster    Ready    control-plane   3m48s   v1.24.0
lmaster1   Ready    control-plane   50s     v1.24.0
node1      Ready    <none>          3m13s   v1.24.0
node2      Ready    <none>          21s     v1.24.0


return blockId in transation.wait()

resolved https://github.com/joticajulian/koilib/commit/8f211a9734dcc2ba58ebd00c8567da941bf045dc


Fix issue when telemetry is not enabled

Issues Resolved by this Pull Request
When telemetry is not enabled in software_config.json, prometheus_gaudi_support is undefined.
Fixes #
Check if telemetry is in the config first
Description of the Solution
Please describe the solution provided and how it resolves the associated issues.
Suggested Reviewers
@priti-parate  @abhishek-sa1

ok closing this one too


Large Graphs

Currently the graph (or some subset of it) is held entirely in memory, but as it becomes larger we need to be able to page out parts of it.
Look into a safe way to have parts of the graph exist only on disk while some parts exist in working memory and on disk.

To be superseded by the 秘密 update as discussed in our internal core development meeting.


Buildkite/publish-debs

Thank you for contributing to Coda! Please see CONTRIBUTING.md if you haven't
yet.
Explain your changes here.
This work intends to migrate the publish-deb job from CircleCI to BuildKite. Specific changes:

make publish_debs now runs ./buildkite/scripts/publish-deb.sh (the buildkite version of ./scripts/publish-deb.sh)
./scripts/rebuild-deb.sh updated to use buildkite environment variables. Making the script compatible with both would be easy enough, but this was not listed as a requirement.
make publish_debs is executed once at the end of build-artifact.sh as opposed to make publish_deb being executed twice

Explain how you tested your changes here.

According to the verification instructions in https://github.com/CodaProtocol/coda/issues/5282#issuecomment-655790733

Checklist:

[x] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them:

Closes #5282

(as long as the build passes on buildkite)


Is android-async-http deprecated?

Is this library deprecated?
No update or commit for long time.

See #1312


请问一下流式传输时，如果client端关闭请求，Server端会停止生成嘛？

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[X] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.

Describe the bug
因为存在client终止流式传输的请求，想知晓Server端会如何处理请求中断的情况。
Reproduction
client
Environment
RT

Error traceback
No response

会终止生成。


Could you add Javascript Lambda functions?

I moved the question to the community instead and am waiting for approval

Answered in https://community.rubyonjets.com/t/could-you-add-javascript-lambda-functions/180


Redesign opportunities page

Hey, can I work on it, might take a little bit more time?

Ok I will do my best

@nirban256  let me know about the updates

ok


Package latest version of python-psphere for Fedora.

vSphere plugin requires python-psphere 0.5.2.  Fedora repositories currently house 0.1.4.  Need to make 0.5.2 available for Fedora.

python-psphere 0.5.2 is available for F21+,  I assume this can be closed?

I agree with tflink - This can be closed :-)


Question regarding curly bracket position in function definition

Is it intentional that
main = fun()
{
    //Body
}

throws an error whereas
main = fun() {
    //Body
}

does not?

Yes, each new line character is considered a statement termination. I might try and see if I can figure out a way to make this syntax work, but no promises.

If that's the syntax that's the syntax, I think it's ok to be opinionated here.
If possible, it would be good to slide a helpful comment into the error message to point people to the right syntax.


Nodepool should have a minimum-size of nodes for applications requiring HA.

Description
What problem are you trying to solve?
We want our nginx controller to always be on two different nodes. We can't afford packet loss if the current node goes down while the provisioner is setting up another node.
How important is this feature to you?
Critical

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

If you put an inter-pod anti-affinity constraint by hostname on the pod spec, Karpenter will launch one node per pod and the scheduler will only ever schedule one pod per node. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#scheduling-a-group-of-pods-with-inter-pod-affinity-to-themselves for details.

Going to close this out since this is a known way to spread pods across nodes using kube-scheduler.

Going to close this out since this is a known way to spread pods across nodes using kube-scheduler.


Is defineProperties() description correct?

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

Object.defineProperties, in essence, defines all properties corresponding to the enumerable own properties of props on the object obj object.

obj.a enumerable is false,but obj.a can be defined. is the description correct?

Page in question: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperties

I've removed this section. I don't think it adds any benefit and it seems to rather confuse.


Can I do multi-class segmentation with this repo??

Hi! I'm really interested in this repo, because Seggpt's concept will be good for satellite image and, dataset of yours was satellite image also!
and I want to do segmentation on argriculture area,  building, road(paved, dirt), water area.
can I make multi-class segmentation using this repo?
singe class segmentation will be good for preformence  but using many of gpu will be risk for our system.
thanks!

Hi, sorry for the late reply.
I believe that the current code already supports segmentation for multiple class. Could you clarify your usage?


[PAY-1790] Create Backing With Setup Intent Client Secret

📲 What
This PR wraps up the major portion of work to use a newly created card from the Stripe Payment Sheet to complete a backing within the iOS app.
🤔 Why
Part of the ongoing Epic to include Stripe in our payments systems so we can offload much of the complexity of payment processing to an expert vendor.
🛠 How
...tbd..
👀 See
Before 🐛
...coming...
After 🦋
...coming...
✅ Acceptance criteria

[x] Ensure create backing works with newly created card from payment sheet.

⏰ TODO

[x] Fix happy path (vanilla CreateBacking with setupIntentClientSecret)
[ ] Ensure other contexts besides .pledge never see the Payment Sheet
[ ] Ensure the 3DS flow and Apple Pay still work as expected (in code)
[ ] Ensure cards used to pledge are retained in both settings and in the manage pledge page.
[ ] Ensure change payment methods, updating reward, updating pledge amount, (fix is kinda hard to test, it should work -- see if I can spoof it) are all working
[x] Write unit tests

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


OCPBUGS-19784: Update capi agent version for CRD label

What this PR does / why we need it:
This was missed on the initial PR to upgrade the agent APIs to v1beta1 and is required for correctly picking up and labeling Agent CRDs.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes OCPBUGS-19516
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/cc @enxebre

/approve

/retitle OCPBUGS-19784: Update capi agent version for CRD label

/lgtm

/retest


[beta] Backend challenges do not work

Challenge using-packagejson-the-core-of-any-nodejs-project-or-npm-package has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

"author": "Jane Doe",

I tried the code with "author": "Laura Veee", and it did not work. I reset the challenge as well.

Me too

Hi @Cyclokitty! Thank you for reporting this issue.
The new backend challenges do indeed not work yet. I believe this is waiting for https://github.com/freeCodeCamp/freeCodeCamp/pull/11058

If you're reading this, you saw that the issue was closed, which means that this issue has been fixed! 🎉

I tried it today and it didn't work for me.

@nealthom Hi! There were some more issues with them, so that's absolutely possible. I think they have been resolved but need to be deployed to the beta. They should be working on the next deploy 👍
Do keep in mind that this is the beta, so there may still be broken tests and other bugs, even after the deploy. If you do stop any, please let us know!


support for multicast networkpolicy

Describe the problem/challenge you have
Antrea has implemented multicasr traffic support, but currently there is no networkpolicy for multicast, all multicast packet will be passed as long as the pod enters the group. For security consideration, it is better to implement networkpolicy for multicast to allow or reject multicast packet.
This proposal is to define networkpolicy for multicast, here are the requirements:

block IGMP queries and reports from and towards Pods

block IGMP queries towards pods
block IGMP reports from pods

limits sources (in Pods) to send multicast traffic to specific multicast IPs

Describe the solution you'd like
0. changes in pipeline
IGMP -> MulticastEgress -> MulticastEgressMetric -> Multicast -> MulticastIngress -> MulticastIngressMetric -> MulticastOutput

IGMP handles with IGMP query and report
multicastEgress handles multicast egress traffic
multicastEgressMetric collects metric for multicast egress metric
multicastIngress handles multicast ingress traffic
multicastIngressMetric collects metric for multicast ingress metric
1. crd defination
since there is Ingress/Egress in ACNP, it is better to reuse the existing crd defination, and extend with a member in Rule：
protocol string
to indicate what kind of protocol it is.
2. Block IGMP query and reports from and towards Pods
It needs to be possible to define Antrea Cluster Network Policies that block IGMP queries and reports from and towards Block IGMP query to pods.
2.1 Block IGMP query
for example, to block IGMP query to pod which matches label app=app1
Ingress:
- action: Drop
  appliedTo:
  - podSelector:
    matchLabels:
      app: app1
  enableLogging: false
  from: []
  name: "1000"
  protocol: IGMP

Antrea-agent creates a group for <IP_ADDRESS> in table multicast, which is the multicast address to send group query:

cookie=0x4, duration=8609.772s table=IGMP, n_packets=70, n_bytes=965, priority=200, igmp, nw_dst=<IP_ADDRESS> actions=group:7

When there is new pod created, antrea-agent will added the pod into the IGMP query group, while there is pod deleted, anra-agent removes the pod from IGMP query group
When there is rule to block group query, antrea-agent will block the port number for matches pod to send IGMP query to the matched pod

group_id=7,type=all,bucket=bucket_id:0,actions=load:0x1->NXM_NX_REG0[8],load:0x2->NXM_NX_REG1[],resubmit(,MulticastEgress),bucket=bucket_id:1,actions=drop

4.When the rule is deleted, antrea-agent will allow the port number to send IGMP query
group_id=7,type=all,bucket=bucket_id:0,actions=load:0x1->NXM_NX_REG0[8],load:0x2->NXM_NX_REG1[],resubmit(,MulticastEgress),bucket=bucket_id:1,actions=load:0x1->NXM_NX_REG0[8],load:0x2->NXM_NX_REG1[],resubmit(,MulticastEgress)

2.2 Block IGMP report
Egress:
- action: Drop
  appliedTo:
  - podSelector:
    matchLabels:
      app: app2
  enableLogging: false
  name:""
  protocol:
  - IGMP
     - dstMcastAddr: <IP_ADDRESS>

Antrea should block IGMP report from specific pods to any multicast address or specific multicast address
antrea-agent add rule in table IGMP. But since ovs can not read multicast address in IGMP v2/v3, maybe blocking in antrea-agent is a solution to make the behavior same. For the IGMP report message, ovs should redirect to antrea-agent if the packet if from pod (reg0=0x2/0xf), and antrea-agent will send query to ANP to check if report from pod should be blocked.
func queryAction(podRef, multicastAddr string) (RuleAction, type.UID), types.UID is the uuid for policy.
here is the rule to send packet to antrea-agent:
cookie=0x0, duration=738.660s, table=IGMP, n_packets=12, n_bytes=552, priority=210,igmp,nw_dst=<IP_ADDRESS>,reg0=0x2/0xf,action=controller

Limit specific pod to send multicast to specific multicast Ips
Egress:
- action: Drop
  appliedTo:
  - podSelector:
    matchLabels:
      app: app2
  enableLogging: false
  To:
  - IPBlock:
    - <IP_ADDRESS>
  name:""
  ports
    protocol: "udp"

here is the rule to drop multicast traffic from pod that matches label app=app2 to multicast address <IP_ADDRESS>:
cookie=0x10050000000000, duration=7516.682s, table=MulticastEgress, n_packets=0, n_bytes=0, idle_age=7516, hard_age=8, priority=64180,ip,nw_src=<IP_ADDRESS> actions=conjunction(2,1/2)
cookie=0x10050000000000, duration=7516.682s, table=MulticastEgress, n_packets=0, n_bytes=0, idle_age=7516, hard_age=8,priority=64180,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/2)
//load:0x1->NXM_NX_REG4[25] means this deleted by np
cookie=0x10050000000000, duration=148.512s, table=MulticastEgress, n_packets=0, n_bytes=0, priority=64180,conj_id=2 actions=load:0x2->NXM_NX_REG3[],load:0x1->NXM_NX_REG4[25],controller,resubmit(,MulticastEgressMetric)
//MulticastIngressMetric
cookie=0x10050000000000, duration=322.933s, table=MulticastEgressMetric, n_packets=0, n_bytes=0, priority=200,reg0=0x1000/0x1000,reg3=0x2 actions=drop

Anything else you would like to add?
thing need to be discussed is that do we need to define ingress that pod (label app=app1) does not receive multicast traffic from specific IP address (for example <IP_ADDRESS>) to multicast address <IP_ADDRESS>?
If yes, we need to introduce a new member to store the multicast address. something like:
Ingress:
- action: Drop
  appliedTo:
  - podSelector:
    matchLabels:
      app: app1
  enableLogging: false
  from:
  - IPBlock:
     - <IP_ADDRESS>
  name: "1000"
  protocol: "udp"
 to:
 - IPBlock:
     - <IP_ADDRESS>

I think we can put ingress for multicast traffic in low priority

I have a question about how to represent an Ingress rule for multicast traffic? What should be the "appliedTo" value, multicast address or Pods? If it is multicast address, the existing ANP API doesn't support using IPBlock as AppliedTo field, and AntreaController might not able to calculate the ANP span. If the appliedTo is a Pod, how would you identify this is a rule for multicast but not for a general unicast traffic?

From my understanding, Antrea should support 3 scenarios for multicast: 1) Pods only work as multicast sender, 2) Pods only work as multicast receiver, 3) Pods work as both multicast sender and receiver.  If we only support Egress rule with multicast, I don't think we can satisfy the security requirement for senario 2.

I have a question about how to represent an Ingress rule for multicast traffic? What should be the "appliedTo" value, multicast address or Pods? If it is multicast address, the existing ANP API doesn't support using IPBlock as AppliedTo field, and AntreaController might not able to calculate the ANP span. If the appliedTo is a Pod, how would you identify this is a rule for multicast but not for a general unicast traffic?

I 'd like to introduce a field IPBlock to indicate the multicast address or other IP address. And for "appliedTo" we should use the existing implementation, for example, pod selector, clustergroup and so on.

close as https://github.com/antrea-io/antrea/pull/3660 is merged


Adding Docker support.

Topic
I wanted to discuss if we should add docker support to the project to make the development experience better, although this project doesn't require many entities, unlike the web editor which needs a Mongo instance.
I can work on this if greenlit by the maintainers.

Per #1452 we will have a new website with new development setup so we won't be considering this at the moment. I also don't think a Docker image will help with the development setup of what is essentially a static website (there are no backends, node.js or otherwise, to the p5.js website).


[ThorSwap/ETH] Change to using depositWithExpiry

Is your feature request related to a problem? Please describe.
When switching from ERC-20 token (on Ethereum), the new depositWithExpiry function should be used instead of deposit.
"Announcement: update to the ETH router contract that inbound ETH swaps are executed against. We will deprecate the deposit func in the next version of the router, in favor of the depositWithExpiry function. This protects users from their inbound tx getting hung up and potentially getting dropped if it ends up hitting an old vault after taking a long time to confirm:
Reminder - unprotected deposit() will get deprecated in next Router Update

All interface devs should be using router.depositWithExpiry(Params, +15minsInUNIXSeconds)

This reverts the tx if it takes more than 15mins to process. The unprotected deposit function will be set to private on the next router upgrade.

Relevant call: https://github.com/trustwallet/wallet-core/blob/master/src/THORChain/Swap.cpp#L260

https://etherscan.io/address/0xD37BbE5744D730a1d98d8DC97c42F0Ca46aD7146#code  line 69

We'd be happy to look into this for you. Kindly file a support ticket here
https://forms.gle/zVGLP7GATPsDHdkH9

We'd be happy to look into this for you. Kindly file a support ticket here
https://forms.gle/zVGLP7GATPsDHdkH9


why leethub serial number is different from leetcode question number

          why leethub serial number is different from leetcode question number

Originally posted by @Deathwear in https://github.com/QasimWani/LeetHub/issues/461#issuecomment-1742490850

after submission the the leethub assigned serail no. is different from leetcode question number therefore facing difficulty in finding these questions if I needed to look them again


Dotnet PE binary cataloger is detecting false positives

What happened:
Originally reported https://github.com/anchore/vulnerability-match-exclusion-database/issues/240#issuecomment-2489341204
syft -q ~/Downloads/jruby-exec.zip
NAME   VERSION  TYPE
JRuby  1.0      dotnet

What you expected to happen:
Jruby is not a .NET application, thus should not be detected as so (should find no packages)
Steps to reproduce the issue:
Download jruby binary and scan it with syft.
Anything else we need to know?:
Proposed fix: scan the PE binary for indications of the .NET framework.
Partial fix implemented: https://github.com/anchore/syft/compare/filter-dotnet-pe

Hey Alex! CBP also went on to note that the same issue affects jrubyw.exe.

Hey @wagoodman @joshbressers ! I see that this item was added as a bug from vulnerability match exclusion that I filed. Is there any idea when this will be added to enterprise? This is something that CBP reported.


What is the suggested repository for using bitsandbytes with a ROCm backend?

AMD has forked bitsandbytes here. There was a bit of confusion regarding the installation and usage of this fork and its rocm_enabled branch; I have not tested this fork/branch within a week or so, but it seems that it is still unclear if this will work out of the box, or even if this is the correct fork/branch to be using.
The developers at the upstream branch have recently released the bitsandbytes/multi-backend-refactor branch (link) that is in the testing phase for supporting AMD GPUs and Intel GPUs.
Which of these two, between ROCm/bitsandbytes and bitsandbytes-foundation/bitsandbytes should be considered the go-to? Is AMD contributing to the upstream branch? If not, why? What has been developed for the ROCm branch that is not in the multi-backend-refactor upstream branch?

@garrettbyrd Internal ticket is created to assist with your issues. Thanks!

Hi @garrettbyrd, I reached out to the internal team handling ROCm/bitsandbytes. Changes to the AMD fork are also pushed to the multi-backend-refactor upstream branch, so you should be able to use either. I can see from your linked open issue (https://github.com/ROCm/ROCm/issues/3132) that you're having install or configuration issues with ROCm/bitsandbytes. If you decide to try the multi-backend-refactor upstream branch and experience similar issues, please comment on this in your existing issue or open a new issue.
If this answers your question, you can close this issue. If not or if there are any additional items you'd like clarified, you can reach out to me here or to @pnunna93 in your existing issue. Thanks!

@schung-amd can you check where this will be documented for posterity? This question may be repeated by others.

@saadrahim Great suggestion, thanks. Incorporation of the ROCm fork to the upstream branch was noted here, but this isn't the most visible; I'm reaching out to @pnunna93 to see if we can get something added to the description of the ROCm fork.

@schung-amd Thanks for the information. I will be happy to close if/once something is added to the description of the ROCm fork, as you suggested.

I have updated our fork to reflect this. Thanks for the feedback @garrettbyrd!

@pnunna93 Lovely! Thanks for the addition.


🐛 Change ChengYi.jpg to seeksaveserve.png

Previously the naming convention was not followed
Let's fix that 🔥

👦 Handsome boi! LGTM! (as requested by seeksaveserve)


Run tests against both S3 and NFS backupstores.

This PR will fix
https://github.com/longhorn/longhorn/issues/1802
https://github.com/longhorn/longhorn/issues/1803

Affected tests:
test_backup_block_deletion
test_backup_volume_list
test_backup_metadata_deletion
test_restore_inc_with_expansion
test_dr_volume_with_last_backup_deletion
test_rebuild_with_restoration
test_rebuild_with_inc_restoration
test_inc_restoration_with_multiple_rebuild_and_expansion
test_restore_volume_with_invalid_backupstore
test_all_replica_restore_failure
test_single_replica_restore_failure
test_dr_volume_with_restore_command_error
test_engine_crash_for_restore_volume
test_engine_crash_for_dr_volume
test_backup_kubernetes_status
test_recurring_job
test_recurring_job_in_volume_creation
test_recurring_job_in_storageclass
test_recurring_job_kubernetes_status

@meldafrawi can you rebase.

@joshimoo Thank you for your comments, I've fixed and re-based the PR.

@meldafrawi once you have time can you rebase and mount via nfsv4.1 ?

@meldafrawi Can you follow up?

@joshimoo I've added one more comment to update Longhorn test image
https://github.com/longhorn/longhorn-tests/pull/417/commits/a7c76b3746524f7a655269f48d6ba345e1677ceb
please review that as well.

@PhanLe1010 can you help to review this? @joshimoo is on vacation.


toolchain: alias restrict to __restrict for GNUC

restrict keyword is not supported in C++, however
GNUC does support __restrict so we can use that.
Signed-off-by: Nicholas Lowell<EMAIL_ADDRESS>

I'm not sure it's a scalable solution to patch each and every prototype using "restrict" to be in 2 duplicated versions.
Instead, some common header should define something like ZRESTRICT, and define it to either supported version of "restrict" keyword, or to nothing.

Understood.  Any location suggestions? kernel.h? toolchain.h?

Understood. Any location suggestions? kernel.h? toolchain.h?

toolchain.h sounds like a good idea, as this feature (supporting restrict for C++) may be inherently toolchain-specific, and there're talks/work on supporting more toolchains beyond GCC/LLVM. The best idea would be to look up a few committers to that file and invite them to the discussion.

Actually found a much simpler solution, let me know what you think.

Sorry. I changed the commit message, forgot about the open pull request title.

@nslowell: As you can see from the build failures, it's not as simple as that. I also would do it like that for a personal project of me, but for a project the scale of Zephyr, I'm afraid the only sustainable solution is to indeed define a Zephyr-private (namespaced) preprocessor symbol, and use that throughout the codebase.

             from /workdir/zephyr/lib/open-amp/resource_table.c:30:

modules/libmetal/libmetal/lib/include/metal/compiler/gcc/compiler.h:19: error: "restrict" redefined [-Werror]
19 | #define restrict restrict

Thanks for the continued help.  Hopefully this solves the issue.  Note there are now two different commits.

Not sure what is needed to get this merged.

@nashif: re: your comment https://github.com/zephyrproject-rtos/zephyr/pull/27245#pullrequestreview-467267334 :

this should be defined in the respective toolchain header file, not in this top-level header.

This comment was addressed. Now, respective toolchain files define ZRESTRICT, though there's still a fallback in include/toolchain.h, where ZRESTRICT is defined to "natural default". So, if someone drops in a new toolchain-specific file without ZRESTRICT, they still will get a good-enough default. IMHO, that's reasonable approach. Can you please re-review?
Additional note about PR "assignees". The original idea behind that was that assigned person will "help to drive a patch to the completion/inclusion". But soon after it was launched, turned out, it works rather differently. How it works is that other merge-drivers (i.e. people with merge rights) start to bypass it. Certainly that's done from good motives of "not stomping on somebody else's feet". But the end result we see here (and I saw similar cases elsewhere (of course, not just with you)) is that you self-assigned this ticket on Aug 14, and since then, there was no further review activity happening on it. So IMHO, the process of PR assignees might use some adjustment.
Thanks.

Retriggering CI.

@nslowell: Actually, if you could rebase on the latest master, that would be helpful, as I don't really see Buildkite to running a new build (and if it does, dunno if it tries to apply a PR on the latest master, or uses whatever branch was there originally.)

@nashif please confirm change request fulfilled. @pfalcon this was updated as requested but no action was taken.

@nslowell :

@nashif please confirm change request fulfilled. @pfalcon this was updated as requested but no action was taken.

I myself +1'ed this PR. I don't have merge permission to merge it, and it can't be, until there's even a single -1 vote, as still presented from @nashif. So pinging him to lift it is the right thing. (And thanks for not dropping this PR, it's worth being merged IMHO.)

@nashif Can you take a look at this PR again and see if you can remove your -1?

Should update/get rid of _MLIBC_RESTRICT now that a global macro is available:
https://github.com/zephyrproject-rtos/zephyr/blob/21d1ad3762302b3e461953df59430c77e0709274/lib/libc/minimal/include/bits/restrict.h#L19-L23

@stephanosio Can you give more explanation about what you mean? What global macro? _MLIBC_RESTRICT is used in a lot of places so it be safer to leave it alone.

The "Coding Guidelines" test failure is a false positive.  All other comments have been addressed.


Set Swift ABI bit variable when creating a SwiftRuntime

The Swift metadata for classes uses a different bit to identify themselves in the pre-
and post-stable ABI eras. We need to be able to debug both, so the code in the MetadataReader
needs to be configured at runtime.
Companion to https://github.com/apple/swift/pull/23064.
rdar://problem/47935062

https://github.com/apple/swift/pull/23064
@swift-ci please test

apple/swift#23064
@swift-ci please test


Log Spam Causing World Tick

New Paste 1.txt

@Shadows-of-Fire Thanks for the assist at least i have some general direction now and can check my mods.


[Question] How to set keybindings?

I'm trying to add simple keybind to launch eshell, here is how look my ~/.doom.d/bindings.el file:
;;; ~/.doom.d/bindings.el -*- lexical-binding: t; -*-

(map!
 "C-;" #'eshell)

But even after I reload emacs and do make, it says C-; is undefined.
What I did wrong?

Have you loaded this file from ~/.doom.d/config.el?
;; in ~/.doom.d/config.el
(load! "bindings")

Only init.el and config.el are loaded automatically. You'll have to do load other files manually.


Capture all root views

allows the compositing of multiple root views e.g.:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Chris Mathew seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix: too many request issue

Watsonx.ai SaaS only allows 8 requests per second, but when doing some load tests simulating real user scenarios we can easily get to this issue, I suggest remediating this by applying some retry with backoff with jittering to handle large amounts of simultaneous requests.

@h0rv if possible we could discuss this on Slack to see other possible remediations :)

I have seen this module from Avast, https://pkg.go.dev/github.com/avast/retry-go, it seems pretty good

Hi @PabloSanchi, this package is striving to be a 0 dependencies watsonx client (see go.mod).
We are trying to keep it lightweight and not bring any 3rd party dependencies. Due to this, we should create our own solution, even if its not as sophisticated as a pkg like retry-go

Perfect, you are right. Then I will try to make a module for it. Thanks :)

Merged the PR adding retries with backoff and jitter. Thanks for the contribution!


Respond to a contact request

Create espond-to-a-contact-request.md
minor update
Ready for review
Add article link to add-a-contact-in-status.md

Need to add contact request option.

Thank you @jorge-campo. I have applied your comments and merged the content.


Native ads do not trigger AD_RENDER_SUCCEEDED / AD_RENDER_FAILED

Describe the bug
Rendering a native ad does not trigger the AD_RENDER_SUCCEEDED event like banner ads do.
To Reproduce
Steps to reproduce the behavior:
Render any ad through the PUC native-render.js.

Aside: succeeded is rather misleading, we may want to rename 'attempted' or similar