[feat] support passing extra args to kind create

What does this PR do?

Allows passing arbitrary extra arguments to kind. This is useful for several debugging scenarios and edge cases, described in the kind_extra_args.yaml file I included.

thanks for the contribution!
high-level question - the docs say "Extra command line arguments passed to Kind CLI" -- but then you only pass arguments to kind create, not other kind cli invocations (e.g., kind delete).  I'm not sure how to resolve this though?

high-level question - the docs say "Extra command line arguments passed to Kind CLI" -- but then you only pass arguments to kind create, not other kind cli invocations (e.g., kind delete).  I'm not sure how to resolve this though?

That's a good call out! At least for my purposes, I only need to pass CLI flags to kind create.  I can rename the property accordingly.
Before I refactor: does this data model make sense to you, or should I be thinking about a more generic interface (I could imagine that other providers would want to have a similar interface).

ya, i'd be fine if it was KindCreateExtraArguments


Define ownership of the Velero package

Maintainer Request
We need to define who is owning the Velero package. Right now, in the metadata.yaml fiile:
  maintainers:
    - name: Carlisia Thompson

https://github.com/vmware-tanzu/community-edition/blob/main/addons/packages/velero/metadata.yaml#L10-L11
We can also take this opportunity to update the pkg-velero-owners github team to the correct people: https://github.com/orgs/vmware-tanzu/teams/pkg-velero-owners
cc @nrb @carlisia

Let me see if I can add folks into @vmware-tanzu/pkg-velero-owners.

The maintainer is already updated to me
  maintainers:
    - name: Xun Jiang

https://github.com/vmware-tanzu/community-edition/blob/main/addons/packages/velero/metadata.yaml#L10-L11
I'm also added into https://github.com/orgs/vmware-tanzu/teams/pkg-velero-owners

@blackpiglet Yeah, it can! Thanks for reminding us.


looking forward to your fantastic work

We are looking forward to your fantastic work!!

Hi, thanks for your interest :)
You can find the LLM2Vec paper on Arxiv (https://arxiv.org/pdf/2404.05961.pdf). You can also check out our webpage (https://mcgill-nlp.github.io/llm2vec/) for more information.


FormatException: Trying to read yyyy from 1999 at position 0

Code
print(intl.DateFormat('yyyy').parse('1999'));
intl version
  intl:
    dependency: transitive
    description:
      name: intl
      url: "https://pub.dartlang.org"
    source: hosted
    version: "0.17.0"

Exception
I/flutter (21756):  FormatException: Trying to read yyyy from 1999 at position 0


setState when using default Select value

Closes #2384

This PR generates errors when the dialog is opened:
warning.js:36 Warning: Failed prop type: The prop `value` is marked as required in `_type`, but its value is `null`.
    in _type (created by CreatePersonalAccessToken)
    in CreatePersonalAccessToken
    in div (created by _type)
    in div (created by _type)
    in div (created by _type)
    in _type (created by Layout)
    in div (created by Layout)
    in div (created by Layout)
    in Layout (created by Connect(Layout))
    in Connect(Layout) (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in div
    in Provider

warning.js:36 Warning: Failed prop type: The prop `value` is marked as required in `Select`, but its value is `null`.
    in Select (created by _type)
    in _type (created by CreatePersonalAccessToken)
    in div (created by _type)
    in div (created by _type)
    in _type (created by _type)
    in _type (created by CreatePersonalAccessToken)
    in div (created by CreatePersonalAccessToken)
    in form (created by _type)
    in _type (created by FormModalBody)
    in FormModalBody (created by CreatePersonalAccessToken)
    in CreatePersonalAccessToken
    in div (created by _type)
    in div (created by _type)
    in div (created by _type)
    in _type (created by Layout)
    in div (created by Layout)
    in div (created by Layout)
    in Layout (created by Connect(Layout))
    in Connect(Layout) (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in div
    in Provider

warning.js:36 Warning: `value` prop on `input` should not be null. Consider using the empty string to clear the component or `undefined` for uncontrolled components.
    in input (created by Select)
    in span (created by Select)
    in Select (created by _type)
    in _type (created by CreatePersonalAccessToken)
    in div (created by _type)
    in div (created by _type)
    in _type (created by _type)
    in _type (created by CreatePersonalAccessToken)
    in div (created by CreatePersonalAccessToken)
    in form (created by _type)
    in _type (created by FormModalBody)
    in FormModalBody (created by CreatePersonalAccessToken)
    in CreatePersonalAccessToken
    in div (created by _type)
    in div (created by _type)
    in div (created by _type)
    in _type (created by Layout)
    in div (created by Layout)
    in div (created by Layout)
    in Layout (created by Connect(Layout))
    in Connect(Layout) (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in div
    in Provider

@displague those are not errors, those are just warnings. Can safely be ignored.

@displague you must not have rebuilt the components package after you switched to this branch. npm run rebuild-components.

Coverage remained the same at 71.772% when pulling 3fa76df1d4454243c80c6ac4cb5b309a049006d8 on eatonphil:fix-expiration-select into<PHONE_NUMBER>e833c0ebc670cf6610c88b32dbc36f on linode:master.


Some v.redd.it videos have visual issues every 6 seconds.

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2019.04.30
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

PS D:\Downloads> .\youtube-dl.exe -v https://v.redd.it/mmrx3kz5d2x21
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://v.redd.it/mmrx3kz5d2x21']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2019.04.30
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg 4.0.2, ffprobe 4.0.2
[debug] Proxy map: {}
[Reddit] mmrx3kz5d2x21: Downloading m3u8 information
[Reddit] mmrx3kz5d2x21: Downloading MPD manifest
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://v.redd.it/mmrx3kz5d2x21/HLS_360_v4.m3u8'
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 9
[download] Destination: mmrx3kz5d2x21-mmrx3kz5d2x21.mp4
[download] 100% of 6.46MiB in 00:02

Description

Some v.redd.it videos have strange visual issues at around 6 seconds, 12 seconds, 18 seconds, etc (I have uploaded some examples in which you can see that the problems occur at practically the same time in each video).
Here are ffprobe results on 3 v.redd.it videos I downloaded today and that have issues and 1 v.redd.it video that I downloaded today and has no issues:
Input #0, mpegts, from '.\bad1.mp4':
  Duration: 00:00:09.69, start: 1.471233, bitrate: 2169 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
    Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(progressive), 432x768 [SAR 1:1 DAR 9:16], 28.08 fps, 28.08 tbr, 90k tbn, 56.15 tbc

Input #0, mpegts, from '.\bad2.mp4':
  Duration: 00:00:53.70, start: 1.466667, bitrate: 1009 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
    Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(progressive), 640x396 [SAR 3201:3200 DAR 97:60], 30 fps, 30 tbr, 90k tbn, 60 tbc

Input #0, mpegts, from '.\bad3.mp4':
  Duration: 00:00:29.94, start: 1.466600, bitrate: 1034 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
    Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, progressive), 476x432 [SAR 7020:7021 DAR 65:59], 30 fps, 30 tbr, 90k tbn, 60.06 tbc

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\good1.mp4':
  Metadata:
    major_brand     : iso5
    minor_version   : 1
    compatible_brands: avc1iso5dsmsmsixdash
    encoder         : Lavf57.71.100
  Duration: 00:00:12.77, start: 0.000000, bitrate: 4821 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 608x1080 [SAR 2205:2204 DAR 49:87], 1490 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
    Metadata:
      handler_name    : VideoHandler

As you can see, all of the broken videos specify mpegts and are missing metadata.
The videos that have problems after downloaded came from: https://v.redd.it/mmrx3kz5d2x21, https://v.redd.it/jh36uwq0b7x21, and https://v.redd.it/va1hxr74i2x21

@dstftw Can you tell me which issue this is a duplicate of so that I may follow it?

@AaronV-T Check out the new issue: #21270

@dstftw Please tell us what issue this is a duplicate of.


'conda activate' lines generated in slurm script even if conda_env is set to None

Environment

Covalent version: Release version 0.220.0
Python version: Python 3.9.5
Operating system: Ubuntu 20.04.6 LTS
**Slurm plugin:  0.12.1

What is happening?
When using a slurm executor, the generated slurm-dispatchId.sh file always includes lines for conda although one has specified conda_env=None.
How can we reproduce the issue?
Have a look at the code of slurm.py:
lines 395 and 396:
# assemble script
return "".join([slurm_preamble, slurm_conda, slurm_python_version, slurm_body])

This is where the slurm-.sh script is created. Then I looked at the 'slurm_conda' string in line 337-346:
# sets up conda environment
        slurm_conda = f"""
source $HOME/.bashrc
conda activate {conda_env_str}
retval=$?
if [ $retval -ne 0 ] ; then
  >&2 echo "Conda environment {conda_env_str} is not present on the compute node. "\
  "Please create the environment and try again."
  exit 99
fi

"""

It seems that the conda lines are generated independent of 'conda_env_str' having the value "". I think that if 'conda_env_str = ""' the conda lines should not be generated.
What should happen?
When conda_env=None or conda_env="" no lines related to conda environment should be generated in the slurm-dispatchid.sh scripts.
Any suggestions?
No response

@JackSleuters: Could you try it with pip install covalent-slurm-plugin --pre to install the v0.16.0 pre-release? It's likely that my PR here https://github.com/AgnostiqHQ/covalent-slurm-plugin/pull/61 fixed the issue. If you still get the error, let me know and I can debug.
Tagging @wjcunningham7. If this does fix the issue, it's probably worth minting a new "regular" release to avoid confusion.

Dear Andrew,
I tried pip install covalent-slurm-plugin –pre in my covalent_pre virtual environment. However, I get a build erron in ‘Building wheel for aiohttp (setup.py)…
I’m using python 3.9.5. Any ideas?
Kind regards,
Jack
Building wheels for collected packages: aiohttp, multidict
Building wheel for aiohttp (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /home/username/covalent/covalent_pre/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-tcicr_n2/aiohttp/setup.py'"'"'; file='"'"'/tmp/pip-install-tcicr_n2/aiohttp/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-elsqdh63
cwd: /tmp/pip-install-tcicr_n2/aiohttp/
Complete output (9 lines):

Accellerated build *

usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for aiohttp
Running setup.py clean for aiohttp
Building wheel for multidict (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: /home/username/covalent/covalent_pre/bin/python /tmp/tmp6rjlbas4_in_process.py build_wheel /tmp/tmpss8p07mj
cwd: /tmp/pip-install-tcicr_n2/multidict
Complete output (89 lines):

Accellerated build *

running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-39
creating build/lib.linux-x86_64-cpython-39/multidict
copying multidict/_multidict_py.py -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/_multidict_base.py -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/_abc.py -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/init.py -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/_compat.py -> build/lib.linux-x86_64-cpython-39/multidict
running egg_info
writing multidict.egg-info/PKG-INFO
writing dependency_links to multidict.egg-info/dependency_links.txt
writing top-level names to multidict.egg-info/top_level.txt
reading manifest file 'multidict.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '.pyc' found anywhere in distribution
warning: no previously-included files found matching 'multidict/_multidict.html'
warning: no previously-included files found matching 'multidict/.so'
warning: no previously-included files found matching 'multidict/.pyd'
warning: no previously-included files found matching 'multidict/.pyd'
no previously-included directories found matching 'docs/_build'
adding license file 'LICENSE'
writing manifest file 'multidict.egg-info/SOURCES.txt'
/tmp/pip-build-env-5sxje5tv/overlay/lib/python3.9/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'multidict._multilib' is absent from the packages configuration.
!!
      ********************************************************************************
      ############################
      # Package would be ignored #
      ############################
      Python recognizes 'multidict._multilib' as an importable package[^1],
      but it is absent from setuptools' `packages` configuration.

      This leads to an ambiguous overall configuration. If you want to distribute this
      package, please make sure that 'multidict._multilib' is explicitly added
      to the `packages` configuration field.

      Alternatively, you can also rely on setuptools' discovery methods
      (for example by using `find_namespace_packages(...)`/`find_namespace:`
      instead of `find_packages(...)`/`find:`).

      You can read more about "package discovery" on setuptools documentation page:

      - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

      If you don't want 'multidict._multilib' to be distributed and are
      already explicitly excluding 'multidict._multilib' via
      `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
      you can try to use `exclude_package_data`, or `include-package-data=False` in
      combination with a more fine grained `package-data` configuration.

      You can read more about "package data files" on setuptools documentation page:

      - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

      [^1]: For Python, any directory (with suitable naming) can be imported,
           even if it does not contain any `.py` files.
            On the other hand, currently there is no concept of package data
            directory, all directories are treated like packages.
      ********************************************************************************

!!
check.warn(importable)
copying multidict/init.pyi -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/_multidict.c -> build/lib.linux-x86_64-cpython-39/multidict
copying multidict/py.typed -> build/lib.linux-x86_64-cpython-39/multidict
creating build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/defs.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/dict.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/istr.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/iter.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/pair_list.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
copying multidict/_multilib/views.h -> build/lib.linux-x86_64-cpython-39/multidict/_multilib
running build_ext
building 'multidict._multidict' extension
creating build/temp.linux-x86_64-cpython-39
creating build/temp.linux-x86_64-cpython-39/multidict
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/home/username/covalent/covalent_pre/include -I/usr/include/python3.9 -c multidict/_multidict.c -o build/temp.linux-x86_64-cpython-39/multidict/_multidict.o -O2 -std=c99 -Wall -Wsign-compare -Wconversion -fno-strict-aliasing -pedantic
multidict/_multidict.c:1:10: fatal error: Python.h: No such file or directory
1 | #include "Python.h"
|          ^~~~~~~~~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
ERROR: Failed building wheel for multidict
Failed to build aiohttp multidict
ERROR: Could not build wheels for multidict which use PEP 517 and cannot be installed directly
Kind regards,
Jack
[cid:canon-logo-email_70d9ca90-c358-4f81-8813-a2ad1f096963.png]https://cpp.canon/
Canon Production Printing Netherlands B.V.
P.O. Box 101, 5900 MA Venlo
Van der Grintenstraat 10, 5914 HH Venlo
The Netherlands | Trade register: 12002662
www.cpp.canonhttps://www.cpp.canon
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or with a 'reply' message and delete the message and its attachment(s), if any, from your system(s). Thank you for your co-operation.
From: Andrew S. Rosen @.>
Sent: Saturday, August 19, 2023 6:35 AM
To: AgnostiqHQ/covalent @.>
Cc: Sleuters, Jack @.>; Mention @.>
Subject: Re: [AgnostiqHQ/covalent] 'conda activate' lines generated in slurm script even if conda_env is set to None (Issue #1755)
@JackSleutershttps://github.com/JackSleuters: Could you try it with pip install covalent-slurm-plugin --pre to install the v0.16.0 pre-releasehttps://github.com/AgnostiqHQ/covalent-slurm-plugin/releases? It's likely that my PR here AgnostiqHQ/covalent-slurm-plugin#61https://github.com/AgnostiqHQ/covalent-slurm-plugin/pull/61 fixed the issue. If you still get the error, let me know and I can debug.
Tagging @wjcunningham7https://github.com/wjcunningham7. If this does fix the issue, it's probably worth minting a new "regular" release to avoid confusion.
—
Reply to this email directly, view it on GitHubhttps://github.com/AgnostiqHQ/covalent/issues/1755#issuecomment-1684800185, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBYRB5XQCN6OYFJNEQJSIOTXWA7AVANCNFSM6AAAAAA3VNKIJM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Dear Andrew,
I looked at your code changes for v0.16.0 pre-release and I think your changes should fix the problem. If self.conda_env == None the slurm_conda lines are empty which means they are not generated.
Kind regards,
Jack
[cid:canon-logo-email_70d9ca90-c358-4f81-8813-a2ad1f096963.png]https://cpp.canon/
Canon Production Printing Netherlands B.V.
P.O. Box 101, 5900 MA Venlo
Van der Grintenstraat 10, 5914 HH Venlo
The Netherlands | Trade register: 12002662
www.cpp.canonhttps://www.cpp.canon
This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or with a 'reply' message and delete the message and its attachment(s), if any, from your system(s). Thank you for your co-operation.
From: Andrew S. Rosen @.>
Sent: Saturday, August 19, 2023 6:35 AM
To: AgnostiqHQ/covalent @.>
Cc: Sleuters, Jack @.>; Mention @.>
Subject: Re: [AgnostiqHQ/covalent] 'conda activate' lines generated in slurm script even if conda_env is set to None (Issue #1755)
@JackSleutershttps://github.com/JackSleuters: Could you try it with pip install covalent-slurm-plugin --pre to install the v0.16.0 pre-releasehttps://github.com/AgnostiqHQ/covalent-slurm-plugin/releases? It's likely that my PR here AgnostiqHQ/covalent-slurm-plugin#61https://github.com/AgnostiqHQ/covalent-slurm-plugin/pull/61 fixed the issue. If you still get the error, let me know and I can debug.
Tagging @wjcunningham7https://github.com/wjcunningham7. If this does fix the issue, it's probably worth minting a new "regular" release to avoid confusion.
—
Reply to this email directly, view it on GitHubhttps://github.com/AgnostiqHQ/covalent/issues/1755#issuecomment-1684800185, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBYRB5XQCN6OYFJNEQJSIOTXWA7AVANCNFSM6AAAAAA3VNKIJM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@JackSleuters: I haven't seen that error before. Could you try pip install aiohttp==3.8.1 and see if you still get a build error?

@santoshkumarradha: Looks like this can be closed.

Thanks for this update @arosen93  ! 🙏


Anyone needs to design home UI

Anyone needs to design home UI
How to perform contributions?

Focus on only solving one problem at a time.
You must have to run your project to make sure it doesn't have any problems.
Only touch those files which have some connection with that problem.
You must have to know which problem you are going to solve.
Don't try to edit or remove any code if it is not connected with your problems.
Push & Commit only when if the problem is solved.

Ok completed


Task name IDLE not same as in the documentation (IDFGH-11021)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello everyone,
I found a little difference between the documentation and the actual code.
According to the IDF Programming guide, two IDLEs task with different numbers should be started.

Otherwise, the task information cannot be requested from the operating system. (as you can see on this picture with IDLE)

The task list was queried with this function: vTaskList(taskList)
As we can see, the two IDLE tasks have the same name.
I am using IDF Version 4.4.2
What is also not optimal is that a task has a space Tmr Svc in its name instead of being separated by an underscore Tmr_Scv.
Thank you in advance.
Best regards,
Botond

Yeah, seems like this got changed back in a3c90bf59add3 during a freertos kernel upgrade.
We'll take a look at it!

Can I second the comment on ‘Tmr Svc” becoming “TmrSvc” or similar.
We use the task name as part of our Syslog support and a space in the name breaks the RFC standard!!
Took the issue up with Richard Barry many years ago, he agreed to resolve but probably forgot….
On 23/09/07, 11:20, "ESP-Marius"<EMAIL_ADDRESS>wrote:
Yeah, seems like this got changed back in a3c90bfhttps://github.com/espressif/esp-idf/commit/a3c90bf59add307d3a41f5fb4c17385ee67dcf20 during a freertos kernel upgrade.
We'll take a look at it!
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/12204#issuecomment-1709795631, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYT7GDPXAISMJI34NYEMRDXZGGUXANCNFSM6AAAAAA4ORTFNE.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The fact that the Tmr Svc has a space in the name is only a small problem, but the two "IDLE" tasks have the same name, in my opinion it is a bug.
With the same name "IDLE" you are not able to get some separately Task info to the two tasks. You can always query information about the last started task.

FWIW there is xTaskGetIdleTaskHandleForCPU which should allow you to get each of the idle task handles.


Why volar add a import type?

Versions

vscode 1.83.1
vscode plugin: Vue Language Features (Volar) 1.8.19
vscode plugin: TypeScript Vue Plugin (Volar) 1.8.19

Reproduction
Takeover mode. In create-vue cli project.

Add aaa-bbb-ccc.vue file

<template>

</template>

Write aaa codes in App.vue file, vscode will show import suggestions

Press Enter, vscode will add a line import type

Press Command + Z, will undo import type line

Delete the letter a, and rewrite the letter a, vscode will show import suggestions again

Press Enter, vscode will add a line, but just import

Screen record

Please check if this issue has been resolved in version 2.x. If not, feel free to create a new one.


SyncVar hooks and Sync[Collection] handlers firing during initial spawn

Currrently for initial spawn payload this happens:

OnObjectSpawnStarted
SyncVar hooks fire as objects are spawned
SyncList / SyncDictionary / etc. callbacks are fired as objects are spawned
OnObjectSpawnFinished

Would be better to defer the calling of hooks and callbacks until OnObjectSpawnFinished instead of firing them randomly during the spawn phase.
Additionally, in OnObjectSpawnFinished, we have this, but I think CheckForLocalPlayer should be first for any given object, not last.
foreach (NetworkIdentity identity in spawned.Values.OrderBy(uv => uv.netId))
{
    identity.NotifyAuthority();
    identity.OnStartClient();
    CheckForLocalPlayer(identity);
}

And finally, it would be ideal if we waited until end-of-frame before running OnObjectSpawnFinished so that Awake on everything we just spawned has had a chance to fire, where callback handlers can get wired up before we invoke them.
public readonly SyncList<SomeStruct> structData = new SyncList<SomeStruct>();

void Awake()
{
    // this needs to fire before OnObjectSpawnFinished runs
    structData.Callback += OnDataUpdated;
}

One more thing...
Now that we have Client To Server, SyncVars don't fire the hook on the owner.  It may be that the owner gets the update, but since it already matches the value owner has, the hook would be suppressed as "not changed".  I think if Client To Server is set and hasAuthority is true, we should fire the hook on the owner. Otherwise we need to document that it won't fire so users know what to expect.

This issue introduces all kinds of undesirable side effects. For example, when hooks are fired for initial spawn isClient & isServer variables are not set and will always be false, which is not very intuitive.
Current workaround I use to fix execution order and all side effects (perhaps it will help while this is not fixed):
[SyncVar(hook = nameof(TestHook))] private int hookedSyncVar = 0;

private bool muteHooks = true;

private void TestHook(int oldVal, int newVal) {
    if (muteHooks) return;

    // Hook logic goes here
}

public override void OnStartClient() {
    base.OnStartClient();

    muteHooks = false;
    if (hookedSyncVar != 0)
        TestHook(0, hookedSyncVar);
}

All of the observations and suggested workaround are from version 66.0.9.

https://github.com/MirrorNetworking/Mirror/pull/3961


[Input] A bug on disable labels AND

In the disable state, the label has a white background which cuts off the default input.
Solution to be explored:

A: Make the label floating and ensure consistency across all inputs.
B: Review input disable
C: Others

We can't do that on Android side. Feedbacks shared with Jere. Waiting for an answer.


Update descripton class, to validate only empty descriptions.

Changed from using regrex to just a simple isEmpty() call. To check if the given description is indeed empty.

Codecov Report

Merging #104 (77ff2ab) into master (137b94d) will decrease coverage by 3.24%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #104      +/-   ##
============================================
- Coverage     60.98%   57.74%   -3.25%
- Complexity      417      448      +31
============================================
  Files            90       93       +3
  Lines          1520     1704     +184
  Branches        149      184      +35
============================================
+ Hits            927      984      +57
- Misses          547      662     +115
- Partials         46       58      +12

Impacted Files
Coverage Δ

...c/main/java/manageezpz/model/task/Description.java
70.00% <100.00%> (ø)

...in/java/manageezpz/logic/commands/FindCommand.java
15.78% <0.00%> (-84.22%)
:arrow_down:

...in/java/manageezpz/logic/commands/ListCommand.java
62.96% <0.00%> (-37.04%)
:arrow_down:

src/main/java/manageezpz/model/AddressBook.java
24.40% <0.00%> (-35.21%)
:arrow_down:

src/main/java/manageezpz/logic/LogicManager.java
60.00% <0.00%> (-15.00%)
:arrow_down:

...ava/manageezpz/logic/parser/FindCommandParser.java
88.46% <0.00%> (-11.54%)
:arrow_down:

src/main/java/manageezpz/model/ModelManager.java
72.50% <0.00%> (-1.86%)
:arrow_down:

src/main/java/manageezpz/model/Model.java
100.00% <0.00%> (ø)

...ain/java/manageezpz/model/util/SampleDataUtil.java
0.00% <0.00%> (ø)

...java/manageezpz/logic/parser/ArgumentMultimap.java
100.00% <0.00%> (ø)

... and 7 more

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 137b94d...77ff2ab. Read the comment docs.


add(cauliflower with meat cover)

This PR adds:

Cauliflower with meat cover to the 80's delicacies category

How to prepare for test:
How to test:

deploy to stage

Expected outcome:

[ ] Cauliflower with meat cover is displayed

Review:

[ ] Code approved by
[ ] Tests executed by
[ ] "Merge and deploy" approved by

This version is a:

[ ] MAJOR - when you make incompatible API changes
[x] MINOR - when you add functionality in a backwards compatible manner
[ ] PATCH - when you make backwards compatible bug fixes or documentation/instructions

I think this one is good to merge @karlnyr

I have to admit that the recipe is a good idea, but the fact is that I winged all the timers in this recipe. I will close this PR - to avoid food poisoning of CG staff.

Ok! :)


Extend the auto-completion endpoint to provide auto-completion suggestions for metrics

Currently the autocompleter does not autocomplete metrics. An autocompleter should be added which suggests key words for the metrics section.

Especially, for metric attributes in a rule block.
Example:
inspectit:
  instrumentation:
    rules:
      'r_test':
        metrics:
          'my_metric':
            ...
            <missing autocompletion>


[do not merge] Test PR to test the build workflow

Purpose
Fixes:
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the specification
[ ] Updated the changelog
[ ] Added tests
[ ] Checked native-image compatibility

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


how do i get this to work on arch?

hello!
i read a solved issue about getting this to work on arch, so i know it does work, but im looking for pointers on how to do it. im new to linux so im a little lost.
when i tried using dpkg, i get these issues:

[🔴] × sudo dpkg -i linux-shimeji_0.0.1-4_all.deb
(Reading database ... 18 files and directories currently installed.)
Preparing to unpack linux-shimeji_0.0.1-4_all.deb ...
Unpacking linux-shimeji (0.0.1-4) over (0.0.1-4) ...
dpkg: dependency problems prevent configuration of linux-shimeji:
linux-shimeji depends on openjdk-11-jre; however:
Package openjdk-11-jre is not installed.
linux-shimeji depends on jarwrapper; however:
Package jarwrapper is not installed.

dpkg: error processing package linux-shimeji (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-shimeji

i used my package manager to download jre11-openjdk. when that didnt work i tried to instead use jdk11-openjdk, but that didnt work, either. installing both is a no go, as well since they are in conflict.
also, i dont know where to get jarwrapper. any help would be appreciated!

Hi,
if you already have Java 11 installed (jre is fine) try to use this: Executable only. deb . This package expects java 11 to be installed in /usr/lib/jvm/java-11-openjdk-amd64.
I don't use Arch so I am not sure on how to package stuff for it, I hope this works.
Cheers

hi again!
so i decided to install distrobox so i could install the package in ubuntu, but when i run it, i get the error line 8: java: command not found
when i tried to do it via dpkg, i got a whole lot of code vomit that repeats this over and over:

java.lang.IllegalAccessException: class com.sun.jna.platform.WindowUtils$X11WindowUtils cannot access class sun.awt.X11GraphicsConfig (in module java.desktop) because module java.desktop does not export sun.awt to unnamed module @6328d34a
at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:398)
at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:709)
at java.base/java.lang.reflect.Method.invoke(Method.java:571)
at com.sun.jna.platform.WindowUtils$X11WindowUtils.getVisualID(WindowUtils.java:1629)
at com.sun.jna.platform.WindowUtils$X11WindowUtils.getAlphaCompatibleGraphicsConfiguration(WindowUtils.java:1650)
at com.sun.jna.platform.WindowUtils.getAlphaCompatibleGraphicsConfiguration(WindowUtils.java:1974)
at com.group_finity.mascot.x11.X11TranslucentWindow.(X11TranslucentWindow.java:49)
at com.group_finity.mascot.x11.NativeFactoryImpl.newTransparentWindow(NativeFactoryImpl.java:31)
at com.group_finity.mascot.Mascot.(Mascot.java:53)
at com.group_finity.mascot.Main.createMascot(Main.java:187)
at com.group_finity.mascot.Main.run(Main.java:71)
at com.group_finity.mascot.Main.main(Main.java:57)

however, i did see that java's path was /usr/lib/jvm/java-11-openjdk. I can't rename the folder or anything. any ideas?

Hi, I can run the program using distrobox.
These are the steps I used
# Create container
distrobox create --name shimeji-test -i ubuntu:20.04 --additional-packages openjdk-11-jre
# Enter the container
distrobox enter shimeji-test
# Inside the container install the package
su -
cd /path/to/shimeji/deb
dpkg -i linux-shimeji_0.0.1-4_all_nodep.deb

After that I can execute the program with distrobox enter shimeji-test -- linux-shimeji

thank you so much! its working perfectly!


Nodejs 7 - Unhandled promise rejection

I'm submitting a ...  (check one with "x")
[X ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior
Angular seed works well with Nodejs 6.x.x but with version 7.3 I am getting Unhandled Promise rejection error when I run npm start command

[12:20:56] Deleted gulpfile.js.map
[12:20:56] Deleted gulpfile.js
[12:20:56] Deleted tools**.js.map
[12:20:56] Deleted tools**.js
(node:16116) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: done is not a function
(node:16116) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[12:21:02] Finished 'check.tools' after 8.08 s
[12:21:02] Starting 'clean.dev'...
[12:21:02] Deleted dist/dev
[12:21:02] Finished 'clean.dev' after 292 ms
[12:21:02] Starting 'clean.coverage'...
Expected behavior

No errors running Angular seed with Nodejs 7.3
Minimal reproduction of the problem with instructions

Install Nodejs 7.3 and run Angular Seed (npm start)
What is the motivation / use case for changing the behavior?

Installed Nodejs latest version to take advantage of latest features
Please tell us about your environment:

Window 10, Chrome,
Window 10, Chrome,

Angular Seed Version: aaaaf75

Node: node --version = 7.3

Thanks for the catch!

Thank you !! You are the best


bootkube cannot recover from full control plane loss

Background
When a self-hosted cluster experiences full control plane loss, i.e. all master nodes cannot be recovered, it's desirable to:

Launch a new controller node
Reboot bootkube's temporary control plane on that node
Have a new API server deployed to the k8s cluster and resume operation.

Issue
When bootkube starts on a new control plane node, it reads from etcd and its StatusController reports that the self-hosted components are already deployed. The bootkube-provided temporary control plane then exits.
-- Logs begin at Sun 2017-02-26 18:52:39 UTC. --
Feb 26 18:54:46 ip-10-0-19-18 systemd[1]: Started Bootstrap a Kubernetes control plane with a temp api-server.
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: pubkey: prefix: "quay.io/coreos/bootkube"
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: key: "https://quay.io/aci-signing-key"
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: gpg key fingerprint is: BFF3 13CD AA56 0B16 A898  7B8F 72AB F5F6 799D 33BC
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]:         Quay.io ACI Converter (ACI conversion signing key<EMAIL_ADDRESS>Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: Trusting "https://quay.io/aci-signing-key" for prefix "quay.io/coreos/bootkube" without fingerprint review.
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: Added key for prefix "quay.io/coreos/bootkube" at "/etc/rkt/trustedkeys/prefix.d/quay.io/coreos/bootkube/bff313cdaa560b16a8987b8f72abf5f6799d33bc"
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: Downloading signature:  0 B/473 B
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: Downloading signature:  473 B/473 B
Feb 26 18:54:46 ip-10-0-19-18 bootkube-start[2222]: Downloading signature:  473 B/473 B
Feb 26 18:54:47 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  0 B/29.6 MB
Feb 26 18:54:47 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  16.3 KB/29.6 MB
Feb 26 18:54:48 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  5.73 MB/29.6 MB
Feb 26 18:54:49 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  11 MB/29.6 MB
Feb 26 18:54:50 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  16.2 MB/29.6 MB
Feb 26 18:54:51 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  25.3 MB/29.6 MB
Feb 26 18:54:52 ip-10-0-19-18 bootkube-start[2222]: Downloading ACI:  29.6 MB/29.6 MB
Feb 26 18:54:52 ip-10-0-19-18 bootkube-start[2222]: image: signature verified:
Feb 26 18:54:52 ip-10-0-19-18 bootkube-start[2222]:   Quay.io ACI Converter (ACI conversion signing key<EMAIL_ADDRESS>Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.925815] bootkube[5]: Running temporary bootstrap control plane...
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.926412] bootkube[5]: E0226 18:55:01.163799       5 server.go:78] unable to register configz: register config "componentconfig" twice
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.927320] bootkube[5]: E0226 18:55:01.164747       5 leaderelection.go:228] error retrieving resource lock kube-system/kube-scheduler: Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/endpoints/kube-scheduler: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.927575] bootkube[5]: E0226 18:55:01.164747       5 leaderelection.go:228] error retrieving resource lock kube-system/kube-controller-manager: Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.927854] bootkube[5]: Waiting for api-server...
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.928388] bootkube[5]: I0226 18:55:01.165811       5 config.go:498] Will report <IP_ADDRESS> as public IP address.
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.931134] bootkube[5]: E0226 18:55:01.168559       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/pkg/bootkube/status.go:86: Failed to list *v1.Pod: Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods?labelSelector=k8s-app: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.931676] bootkube[5]: E0226 18:55:01.168619       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:481: Failed to list *extensions.ReplicaSet: Get http://<IP_ADDRESS>:8080/apis/extensions/v1beta1/replicasets?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.932181] bootkube[5]: E0226 18:55:01.168657       5 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.PersistentVolumeClaim: Get http://<IP_ADDRESS>:8080/api/v1/persistentvolumeclaims?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.932660] bootkube[5]: E0226 18:55:01.168698       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:473: Failed to list *api.ReplicationController: Get http://<IP_ADDRESS>:8080/api/v1/replicationcontrollers?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.933185] bootkube[5]: E0226 18:55:01.168732       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:470: Failed to list *api.Service: Get http://<IP_ADDRESS>:8080/api/v1/services?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.933661] bootkube[5]: E0226 18:55:01.168764       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:466: Failed to list *api.PersistentVolume: Get http://<IP_ADDRESS>:8080/api/v1/persistentvolumes?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.934164] bootkube[5]: E0226 18:55:01.168796       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:463: Failed to list *api.Node: Get http://<IP_ADDRESS>:8080/api/v1/nodes?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.934653] bootkube[5]: E0226 18:55:01.168844       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:460: Failed to list *api.Pod: Get http://<IP_ADDRESS>:8080/api/v1/pods?fieldSelector=spec.nodeName%21%3D%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded&resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.935154] bootkube[5]: E0226 18:55:01.168880       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:457: Failed to list *api.Pod: Get http://<IP_ADDRESS>:8080/api/v1/pods?fieldSelector=spec.nodeName%3D%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded&resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.935632] bootkube[5]: E0226 18:55:01.169837       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:119: Failed to list *api.Secret: Get http://<IP_ADDRESS>:8080/api/v1/secrets?fieldSelector=type%3Dkubernetes.io%2Fservice-account-token&resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  141.936139] bootkube[5]: E0226 18:55:01.169878       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:103: Failed to list *api.ServiceAccount: Get http://<IP_ADDRESS>:8080/api/v1/serviceaccounts?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.018658] bootkube[5]: E0226 18:55:01.256079       5 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.Namespace: Get http://<IP_ADDRESS>:8080/api/v1/namespaces?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.030305] bootkube[5]: [restful] 2017/02/26 18:55:01 log.go:30: [restful/swagger] listing is available at https://<IP_ADDRESS>:443/swaggerapi/
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.030846] bootkube[5]: [restful] 2017/02/26 18:55:01 log.go:30: [restful/swagger] https://<IP_ADDRESS>:443/swaggerui/ is mapped to folder /swagger-ui/
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.078901] bootkube[5]: I0226 18:55:01.316306       5 serve.go:93] Serving securely on <IP_ADDRESS>:443
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.079323] bootkube[5]: I0226 18:55:01.316426       5 serve.go:107] Serving insecurely on <IP_ADDRESS>:8080
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.106556] bootkube[5]: W0226 18:55:01.343960       5 controller.go:392] Resetting endpoints for master service "kubernetes" to &TypeMeta{Kind:,APIVersion:,}
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.143070] bootkube[5]: I0226 18:55:01.380479       5 log.go:19] http: TLS handshake error from <IP_ADDRESS>:46285: EOF
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.143685] bootkube[5]: I0226 18:55:01.381125       5 log.go:19] http: TLS handshake error from <IP_ADDRESS>:46287: EOF
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.147567] bootkube[5]: I0226 18:55:01.385001       5 log.go:19] http: TLS handshake error from <IP_ADDRESS>:46289: EOF
Feb 26 18:55:01 ip-10-0-19-18 bootkube-start[2222]: [  142.148550] bootkube[5]: I0226 18:55:01.385991       5 log.go:19] http: TLS handshake error from <IP_ADDRESS>:46313: EOF
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.027821] bootkube[5]: I0226 18:55:02.265235       5 trace.go:61] Trace "Create /api/v1/namespaces/default/events" (started 2017-02-26 18:55:01.460345638 +0000 UTC):
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.028237] bootkube[5]: [55.79µs] [55.79µs] About to convert to expected version
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.028779] bootkube[5]: [125.32µs] [69.53µs] Conversion done
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.029009] bootkube[5]: [801.892451ms] [801.767131ms] About to store object in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.029570] bootkube[5]: [804.80633ms] [2.913879ms] Object stored in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.029965] bootkube[5]: [804.828972ms] [22.642µs] Self-link added
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.030421] bootkube[5]: [804.862649ms] [33.677µs] END
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.038381] bootkube[5]: I0226 18:55:02.275802       5 trace.go:61] Trace "Create /api/v1/namespaces/kube-system/events" (started 2017-02-26 18:55:01.470736422 +0000 UTC):
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.038727] bootkube[5]: [32.135µs] [32.135µs] About to convert to expected version
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.039042] bootkube[5]: [89.235µs] [57.1µs] Conversion done
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.039273] bootkube[5]: [802.728711ms] [802.639476ms] About to store object in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.039507] bootkube[5]: [805.007352ms] [2.278641ms] Object stored in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.039729] bootkube[5]: [805.011614ms] [4.262µs] Self-link added
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.039910] bootkube[5]: [805.037798ms] [26.184µs] END
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.111676] bootkube[5]: I0226 18:55:02.349090       5 trace.go:61] Trace "GuaranteedUpdate etcd3: *api.Endpoints" (started 2017-02-26 18:55:01.344871675 +0000 UTC):
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.112546] bootkube[5]: [37.589µs] [37.589µs] initial value restored
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.112738] bootkube[5]: [1.002992467s] [1.002954878s] Transaction prepared
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.112915] bootkube[5]: [1.004149931s] [1.157464ms] Transaction committed
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.113106] bootkube[5]: [1.004196598s] [46.667µs] END
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.113498] bootkube[5]: I0226 18:55:02.349168       5 trace.go:61] Trace "Update /api/v1/namespaces/default/endpoints/kubernetes" (started 2017-02-26 18:55:01.344776001 +0000 UTC):
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.113688] bootkube[5]: [12.003µs] [12.003µs] About to convert to expected version
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.113867] bootkube[5]: [55.746µs] [43.743µs] Conversion done
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.114039] bootkube[5]: [59.883µs] [4.137µs] About to store object in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.114237] bootkube[5]: [1.004336913s] [1.00427703s] Object stored in database
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.114408] bootkube[5]: [1.004340117s] [3.204µs] Self-link added
Feb 26 18:55:02 ip-10-0-19-18 bootkube-start[2222]: [  143.114578] bootkube[5]: [1.004375587s] [35.47µs] END
Feb 26 18:55:04 ip-10-0-19-18 bootkube-start[2222]: [  145.380459] bootkube[5]: I0226 18:55:04.617862       5 leaderelection.go:247] lock is held by kube-controller-manager-3004739813-0nd5x and has not yet expired
Feb 26 18:55:05 ip-10-0-19-18 bootkube-start[2222]: [  146.186535] bootkube[5]: I0226 18:55:05.423951       5 leaderelection.go:247] lock is held by kube-scheduler-2947727816-czclv and has not yet expired
Feb 26 18:55:06 ip-10-0-19-18 bootkube-start[2222]: [  146.926584] bootkube[5]: All self-hosted control plane components successfully started
Feb 26 18:55:06 ip-10-0-19-18 bootkube-start[2222]: Waiting for Kubernetes API...
Feb 26 18:55:11 ip-10-0-19-18 bootkube-start[2222]: Waiting for Kubernetes API...

The only way I've been able to get the api-server to redeploy, is to remove it from the registry (in etcd) manually.
etcdctl get --prefix=true --keys-only /registry | grep kube-apiserver- | xargs -L1 etcdctl del

I've also found the same must be done for the kube-scheduler and kube-controller-manager.
On a related note, I've found that when Tectonic's thirdparty resources are present in the etcd registry, bootkube panics and exits due to invalid memory address or nil pointer dereference. Details can be found in #334.
Versions
k8s [hyperkube] version: 1.5.2_coreos.2
version: v0.3.7
os:
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1235.12.0
VERSION_ID=1235.12.0
BUILD_ID=2017-02-23-0222
PRETTY_NAME="Container Linux by CoreOS 1235.12.0 (Ladybug)"

I wonder if a band-aide solution could be a --recover flag which assumes the state of all control plane components in etcd in wrong, and proceeds to remedy the issue.

@joshrosso I'm a little unclear on the exact situation that needs resolving, and/or how one gets into this specific failure scenario. If you've lost the full control-plane, would we not consider this a scenario for "restore from etcd backup"?
Or is this specifically "we have etcd data, but all control plane nodes no longer exist & never will again?" -- this is a pretty drastic scenario, and a little unclear how you get here without really trying. Maybe by forcibly deleting all master nodes at the same time? Something we still need to cover - but I wonder if "restore from backup" is a sufficient near-term answer to this scenario.
Also, bootkube, in its current form, is expected to be used to bootstrap the first node - and then never used again (not even for disaster recovery). So using it in this way (on an existing cluster) is more or less out of scope for its current functionality.
Easily resolving disaster scenarios is obviously something we need to cover - so if you have reproduction steps for how a user might end up in this situation, we can start adding a matrix of scenarios we need to cover (e.g. restore from etcd backup, restore full/partial control-plane failure, etc.) - and how we plan to resolve those (bootkube, or separate tool, or documentation, etc.)

Actually, maybe "restore from etcd backup" and "restore from target etcd" are the two scenarios here that we need to resolve? I could see the latter being helpful, maybe in cases where we aren't self-hosting etcd?

Actually, maybe "restore from etcd backup" and "restore from target etcd" are the two scenarios here that we need to resolve?

Yes, exactly. I agree, it's a hard situation to get yourself in, but control plane recovery when all 'master' nodes are lost and new master node(s) must be spun up seems reasonable.

Also, bootkube, in its current form, is expected to be used to bootstrap the first node - and then never used again (not even for disaster recovery).

Make sense. This makes this issue more of a design / feature request then. At least to me, it would make sense that in the case of full control plan loss (where new nodes are needed and checkpointing can't help you, bootkube could take on the responsibility of once again providing a 'temporary control plane' in order to recover.
A key challenge is, the etcd data bootkube is restoring from could still state the control plane components are healthy. Thus needing some kind of feature, assuming this is an appropriate concern for bootkube to take on, where, through the temp api server, bootkube removes all kube-* deployments / daemonsets from etcd and attempt to redeploy on the newly available controller nodes.
What are your thoughts @aaronlevy? Is this a reasonable thing for bootkube to take on?

For bootkube to operate as a recovery tool - there are some behavior changes we would need to take into account. For example, the "temporary" control plane needs to source all data from etcd (component flags / tls assets / etc) - not necessarily pre-generated files (the temp control plane needs to exactly mimic the last known state of the cluster - last rendered state is likely stale/wrong).
This has been briefly discussed before (in regards to recovering from etcd backup):
1) ./bootkube recover --etcd-data-dir=foo (or --existing-etcd?)
2) starts temp etcd as static pod (skip if existing etcd)
3) extracts information about api-server directly from etcd (including necessary secret data) and starts temp api as static pod (with hostMounts for secret assets).
4) extracts podspec of scheduler and controller-manager from api-server, then creates pods using those specs pre-scheduled to local node (see https://github.com/kubernetes-incubator/bootkube/issues/112#issuecomment-250337461 for example process).
5) the temp scheduler and controller-manager pods will schedule replacements for themselves (and api-server), then we can kill them
6) We now have a functioning control plane.

--existing-etcd, covering steps 3-6, would be a good starting point. It should be enough for people to get out of trouble in most cases.
--etcd-data-dir would make a nice addition too.

@aaronlevy, are you open to PRs on this functionality? Or do you think we need more design discussion?

I would be open. I know @xiang90 was thinking about this tooling from a "recover self-hosted etcd from backup" perspective - where steps 1-3 would start a new "seed" etcd - then use etcd-operator to pivot into a working cluster.
But if we wanted to recover from existing / running etcd as well, could likely be developed side by side (--existing-etcd or some flag, VS --etcd-data-dir).
Thoughts @xiang90 ?
My requests might be that:

Design doc PR would be helpful - just to make sure everyone is on the same page. (We may need to start a /Proposals top level directory).
the code initially live in its own sub-command so we don't intermix the two modes (bootstrap vs recovery) in case we want to break these tools apart later (for example, bootkube vendors very specific versions of kubernetes - where a recover tool needs to be less opinionated and might be better served using client-go).

But if we wanted to recover from existing / running etcd as well

This could be achieved same as "recover from backup". It adds another step to "backup first".

Design doc PR would be helpful - just to make sure everyone is on the same page. (We may need to start a /Proposals top level directory).

I'll take this on. Let me know if you change your mind on it living in a top level /proposals directory.

the code initially live in its own sub-command so we don't intermix the two modes

ack

@joshrosso If we move to a fully self hosted world, I would expect most cases human operator needs to do --with-etcd-dir when the entire control panel fails since etcd will be part of it.

@xiang90 Fair point. It would make sense then to prioritize the design and implementation of --etcd-data-dir (or --with-etcd-dir) over --existing-etcd described above.

related to https://github.com/kubernetes-incubator/bootkube/issues/658

Closing, as a recovery subcommand was implemented


cloudapi: Add ability to skip uploading and save image locally

During development it can be very useful to store the results locally instead of uploading to a remote system. This implements a development only option to help with that.
To use it you need to add CLOUD_LOCALSAVE to the server's environment. This can be done by editing /usr/lib/systemd/system/osbuild-composer.service and adding:
Environment="CLOUD_LOCALSAVE=1"
You can then use an 'upload_options' object to skip trying to upload to the default service for the type of image, eg:
"image_requests": [
{
  "architecture": "x86_64",
  "image_type": "guest-image",
  "upload_options": {
      "local-save": true
  },
  ...
}]

The results will be saved to /var/lib/osbuild-composer/artifacts/UUID/ using the default filename for the image type.
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[X] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

I chose not to try to add testing for this since it is meant as developer only, and any bugs that crop up will be caught in use by someone who can then fix it.

CLOUD_ is the namespace I randomly picked over OSBUILD_ :) IMAGEBUILDER_ seems pretty awkward though. I considered a cmdline option (plumbing that into the cloud v2 module would be a pain), and buildtime option but I can see a situation where I would want to just switch this on without rebuilding to examine something. Checking an environmental variable is safe and fast so I think it's ok.

I wonder if we want to have a generic mechanism for these type of developer features to avoid them becoming API by accident (shipped in RHEL, discovered and relied upon by a customer).
A compile time option is one way, another might be to introduce an option in the API that you have to specify to indicate you understand you can't rely on the behavior. "unstable": true or something like that.
Specifically for this option (for the future), I wonder if there is a way to make this useful outside of development. On prem the worker API allows you to upload the image to composer, in the cloud we clearly can't support that (composer has no state). Though would it make sense to support a generic HTTP POST target and on prem it just happens to point to composer itself, but we could point it at anything? I'm not sure if that's useful or how to make it generic enough / deal with authentication, but if there is a way to make it work similarly to the generic S3 target I think that might be neat.

I agree that we don't want this to become implicit API. As far as extending it to do HTTP POST, etc. I think that's a different issue that could be addressed later along with removing all the state of the weldr API.
I think the requirement for an environmental variable is enough to avoid users depending on it, unless they really know what they are doing. You need local access, and need to edit the .service file and need to re-edit it after upgrading. FWIW I'll change the 'namespace' to OSBUILD to make it more specific to our use.

Out of curiosity, the adequate documentation informing people about the change such as is checked, but I'm not sure where is this feature documented :thinking: Do you plan to open a PR for the guides repo?

LGTM. Good to merge since guides are external, right?

Yup... :wink:


How do you change version?

The website description says

tryjshell.org is a web terminal to try and test Java 9 through 15's JSHELL

But only 15 appears to be available...

Hehe, 15 covers from Java 1 to Java 15 :) So all Java 9 features are already included.

That's just misleading then. I was specifically trying to test something with JDK 14 vs JDK 11.

Sorry, tryjshell.org doesn't target to provide multiple JDKs.


Unhandled promise rejection if tag exists

Problem
When running action we get unhandled promise rejection when tag already exist
fatal: tag '1.51.0' already exists (node:1595) UnhandledPromiseRejectionWarning: Error: The process '/usr/bin/git' failed with exit code 128     at ExecState._setResult (/home/runner/work/_actions/lidofinance/conventional-changelog-action/v3.11.0/node_modules/@actions/exec/lib/toolrunner.js:592:25)     at ExecState.CheckComplete (/home/runner/work/_actions/lidofinance/conventional-changelog-action/v3.11.0/node_modules/@actions/exec/lib/toolrunner.js:575:18)     at ChildProcess.<anonymous> (/home/runner/work/_actions/lidofinance/conventional-changelog-action/v3.11.0/node_modules/@actions/exec/lib/toolrunner.js:469:27)     at ChildProcess.emit (events.js:314:20)     at maybeClose (internal/child_process.js:1022:16)     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
At the same time action completes successfully with no outputs set.
Possible solution
We can add
process.on('unhandledRejection', (reason, promise) => {   console.log('Unhandled Rejection at:', promise, 'reason:', reason);   core.setFailed(reason); });
So that all unhandled rejections will result in action failure

@TriPSs Should I submit PR?

Yes that would be a good one, thanks!


[Product Note] Improve property pane v2

Problem statement

Allow it to be dragged and placed anywhere
It should open in the same location where it was placed
It should scroll with the screen.
Opening the property pane should be one click

@areyabhishek Also, shortcut for opening the property pane of a selected widget.

Either double click or even bring back single click to open.
Single click might not be so annoying.
If the property pane floats and stays in the same location as last time, then we can actually open the property pane automatically for every selected widget. The previous experience of property pane opening up on its own was annoying because it would keep opening up and interrupt what you were trying to do.

More notes on the property pane that we have today when I try to open the property pane by clicking on the setting button often the resize is triggered so I think the double click wud be a great interaction. we can have the pane floating on a corner of the canvas and have a minimize button to minimize the pane, we can give an option to dock it on the side if people prefer the right side docked property pane. thoughts?

At the risk of repeating myself, why not enable a right-click interaction to open the property pane? Isn't that a more intuitive way to open settings for any particular widget?

We'll consider the right click too. We've discussed this before, we need a moveable property pane for it.

With right click, the property pane needs to open up in the same location as the click. That could cover up the widget. Right click-->move property pane-->then make changes.
Right click generally works as a menu, so there's potential to use it for something else.

It should be possible to resize the pane, when we need to write js code... more than one function is complicated view the all code


Update get-started.md

Noticed while reading the getting started that the anchor has changed

Nice spot! Thanks @teonbrooks 😃


I would like to be part of your community

Thanks for letting me be a part of your community!

Yes of course! Invitation sent 👍


Foreign Exchange

As a commodity, but with a specific variable name.
Does it always balance trade automatically, so has more specific definition that just a commodity?

There's no monetary system, and all changes are relative to benchmark prices/value, so while exchange rates can be included in CGE models (and would be necessary if SAM data includes multiple currencies), MPSGE doesn't have or need any specific functionality, and international trade is modelled by specificying the transactions within standard productions, costs and demands etc.


Update StdIOTransport.cs

Adds _process.Dispose() to release other resources such as Node.exe

Thank you for your contribution! Closing since a proper fix has been implemented, see https://github.com/microsoft/playwright-dotnet/pull/1864 for more information.


Time Out when waiting to get a heart beat from kernel process

Similar to the problem #14082，same error occurred.
Environment:
VScode Version: 1.49.2 (user setup)
Commit: e5e9e69aed6e1984f7499b7af85b3d05f9a6883a
Date: 2020-09-24T16:29:41.983Z
OS: Windows_NT x64 10.0.18362
Python: 3.8.3
Expected behaviour:
Executing cells in jupiter notebook
Actual Behaviour:
Timed out waiting to get a heartbeat from kernel process.
Log from the python output:
vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
Error 2020-09-25 14:33:09: Failed to start the Daemon, StdErr:  E:\Programmes\Anaconda3\python.exe: can't open file '"c:/Users/Alex King/.vscode/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py"': [Errno 22] Invalid argument
Error 2020-09-25 14:33:09: Failed to start the Daemon, ProcEndEx [Error: Timeout waiting for daemon to start
at Timeout._onTimeout (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:24:225838)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)]
Error 2020-09-25 14:33:09: Failed  to start the Daemon, Ex [Error: Timeout waiting for daemon to start
at Timeout._onTimeout (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:24:225838)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-25 14:33:09: Pinging Daemon Failed, Class name = h, completed in 5006ms, has a falsy return value, Arg 1: {}, Return Value: undefined [Error: Timeout waiting for daemon to start
at Timeout._onTimeout (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:24:225838)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-25 14:33:09: Failed to create daemon, Class name = h, completed in 5023ms, has a falsy return value, , Return Value: undefined [Error: Timeout waiting for daemon to start
at Timeout._onTimeout (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:24:225838)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-25 14:33:09: Failed to create the daemon service, defaulting to activated environment [Error: Timeout waiting for daemon to start
at Timeout._onTimeout (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:24:225838)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-25 14:33:33: Timed out waiting to get a heartbeat from kernel process.
Error 2020-09-25 14:33:33: Failed to connect raw kernel session: Error: Timed out waiting to get a heartbeat from kernel process.
Error 2020-09-25 14:33:33: DataScience Error [Error: Timed out waiting to get a heartbeat from kernel process.
at f.waitForHeartbeat (c:\Users\Alex King.vscode\extensions\ms-python.python-2020.9.111407\out\client\extension.js:56:573516)] {
vslsStack: [ CallSite {} ]
}

Thanks for logging. This is a dupe of  #14082. It looks like a space in the user name is the common part of both.


CI: Add rustfmt and cargo clippy to CI

This PR follows the discussion from https://github.com/containerd/runwasi/pull/93

I made a PR (https://github.com/Mossaka/runwasi/pull/2) for amending to this PR for marking all the existing clippy issues as "allowed". We can fix them later and we will get the CI to catch any new clippy issues.

I made a PR (Mossaka#2) for amending to this PR for marking all the existing clippy issues as "allowed". We can fix them later and we will get the CI to catch any new clippy issues.

Thanks for your contribution! Merged it in

Needs a rebase.

Rebased, PTAL @cpuguy83

LGTM

Looks like a fmt error:

Alright, should be passing now as cargo clippy passed on my local env.


Readme.md not updated in apim-apps

Describe your problem(s)
https://github.com/wso2/apim-apps#readme
When we are trying to build the repo by following the readme.md in apim-apps, the files explained there are not available.
Ex:
Open the portals/ directory (where the lerna.json is located)
Cannot find a file called lerna.json .
Also when we perform the step, Run npm run bootstrap to install the dependencies for all 3 portals it gives below error
saying stack Error: Missing script: "bootstrap".
Also we can update the copyright licence year.
Describe your solution
Update the readme.md to match with latest updates in the repo.
How will you implement it

Optional Fields
Related Issues:
Suggested Labels:
Suggested Assignees:

This is updated now.


Methods like provide are lost when implementing Higher Level Actor Logic

Bug or feature request?
It would be great to have a more robust way of extending existing machines/actors.
Description:
Hello :wave: , something we noticed in the doc for higher-level-actor-logic
The spread operator is used to preserve the original actor logic.
Doing this seems to drop the original prototype information so methods like provide  go missing.
(Bug) Expected result:
When using a higher-order function to extend a machine, I would expect all types and original prototype methods to pass through.
i.e this should type correctly, and the function should be present.
withExtendedLogic(machine).provide({})

(Bug) Actual result:
provide is not a function
(Bug) Potential fix:
Instead of this
function withLogic(logic) {
  return {
    ...logic,
    transition() {}
  }
}

We ended up with this to preserve those methods.
Also, shout out to @wfischer42 on our team at Discern.
He's the one who implemented this fix.
export const cloneInstance = <T extends object>(input: T): T => {
  const prototypeDescriptors = Object.getOwnPropertyDescriptors(
    Object.getPrototypeOf(input),
  )
  const protoClone = Object.create(null, prototypeDescriptors)
  return Object.create(protoClone, Object.getOwnPropertyDescriptors(input)) as T
}

function withLogic(logic) {
  const logicClone = cloneInstance(logic)
  logicClone.transition = () => {}

  return logicClone
}

@davidkpiano we ran across another issue that seems related.
It appears that calling provide after extending with a higher-level machine function reverts to the previous machines' logic.
const machine = createMachine()
const machineWithLogginc = withLogging(machine)
machineWithLogging.provide() // returns to old behavior without logging


This is not really a bug, need guidance on a proper dockerfile for .net 8 preview 6 aot build for linux

Hello,
I have created a native aot build on the windows side and have it working using the the new api project template in .net 8 preview 6. I also managed to get a native build using visual studio code in the terminal after installing dotnet 8 preview 6 and the suggested clang install in my wsl2 distribution. My next goal was to get a linux docker container built for the application but am having trouble getting my docker file right as i am using the .net8 preview 6 linux build but it of course doesnt have the clang installed to compile the native binary. Here is my docker file its a feeble attempt to get clang installed the aspnetcore image and put it in the PATH
FROM debian:latest AS temp
# Install clang and zlib1g-dev
RUN apt-get update && \
    apt-get install -y clang zlib1g-dev

FROM mcr.microsoft.com/dotnet/aspnet:8.0-preview AS base

WORKDIR /app
EXPOSE 5500

ENV ASPNETCORE_URLS=http://+:5500
USER app
FROM mcr.microsoft.com/dotnet/sdk:8.0-preview AS build
COPY --from=temp /usr/lib/x86_64-linux-gnu/libclang* /usr/lib/x86_64-linux-gnu/
COPY --from=temp /usr/include/clang* /usr/include/
COPY --from=temp /usr/lib/x86_64-linux-gnu/libz* /usr/lib/x86_64-linux-gnu/
ENV PATH="/usr/lib/llvm-7/bin:${PATH}"
ARG configuration=Release
WORKDIR /src
COPY ["MyFirstAotWebApi.csproj", "./"]
RUN dotnet restore "MyFirstAotWebApi.csproj"
COPY . .
WORKDIR "/src/."
RUN dotnet build "MyFirstAotWebApi.csproj" -c $configuration -o /app/build

FROM build AS publish
ARG configuration=Release
RUN dotnet publish "MyFirstAotWebApi.csproj" -c $configuration -o /app/publish /p:UseAppHost=true

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "MyFirstAotWebApi.dll"]

I believe the last part is also wrong as we dont need "dotnet" to run it and I dont think a dll is being produced, what should the ENTRYPOINT be and how do i get apt-get install -y clang zlib1g-dev installed on the image for the native compile?

@richlander I think you've been looking into this scenario, right?

Lots of options to consider at https://github.com/dotnet/dotnet-docker/pull/4742

Hello I looked at that link am I am still not understanding what my docker file should like to make this work.Thank you,Jason DurnilOn Aug 4, 2023, at 5:27 PM, Rich Lander @.***> wrote:
Lots of options to consider at dotnet/dotnet-docker#4742
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Here's an example: https://github.com/richlander/dotnet-docker/blob/dotnet-8-samples/samples/releasesapi-aot/Dockerfile.ubuntu

Is this in a working state yetFROM mcr.microsoft.com/dotnet/aot-sdk:8.0-jammy AS buildARG TARGETARCHWORKDIR /source# copy csproj and restore as distinct layersCOPY .csproj .RUN dotnet restore -a $TARGETARCH# copy and publish app and librariesCOPY . .RUN dotnet publish -a $TARGETARCH --no-restore -o /app releasesapi.csprojRUN rm /app/.dbg /app/.Development.json# final stage/imageFROM mcr.microsoft.com/dotnet/aot-deps:8.0-jammy-chiseledWORKDIR /appCOPY --from=build /app .USER $APP_UIDENTRYPOINT ["./releasesapi"]Thank you,Jason DurnilOn Aug 5, 2023, at 4:58 PM, Rich Lander @.**> wrote:
Here's an example: https://github.com/richlander/dotnet-docker/blob/dotnet-8-samples/samples/releasesapi-aot/Dockerfile.ubuntu
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hey Rich I get this when running your example
=> ERROR [build 2/8] RUN <<EOF (apt-get update...)
2.8s

[build 2/8] RUN <<EOF (apt-get update...):
0.676 E: Invalid operation update
0.698 Reading package lists...
0.738 Building dependency tree...
0.739 Reading state information...
0.740 E: Unable to locate package build-essential
0.740 E: Unable to locate package clang
0.740 E: Unable to locate package libz-dev

On Mon, Aug 7, 2023 at 7:52 AM Jason Durnil @.***> wrote:

Is this in a working state yet
FROM mcr.microsoft.com/dotnet/aot-sdk:8.0-jammy AS build
ARG TARGETARCH
WORKDIR /source
copy csproj and restore as distinct layers
COPY *.csproj .
RUN dotnet restore -a $TARGETARCH
copy and publish app and libraries
COPY . .
RUN dotnet publish -a $TARGETARCH --no-restore -o /app releasesapi.csproj
RUN rm /app/.dbg /app/.Development.json
final stage/image
FROM mcr.microsoft.com/dotnet/aot-deps:8.0-jammy-chiseled
WORKDIR /app
COPY --from=build /app .
USER $APP_UID
ENTRYPOINT ["./releasesapi"]
Thank you,
Jason Durnil
On Aug 5, 2023, at 4:58 PM, Rich Lander @.***> wrote:

Here's an example:
https://github.com/richlander/dotnet-docker/blob/dotnet-8-samples/samples/releasesapi-aot/Dockerfile.ubuntu
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8663#issuecomment-1666603806, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7DCFZMIDG6ZOKWJAD5P53XT2XXPANCNFSM6AAAAAA3ENRMHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Do you have buildkit enabled? These samples require it.
https://docs.docker.com/build/buildkit/

hmm no i dont, ill install it

I actually i have docker desktop installed with wsl2 support, it says there is nothing more i need to do to enable buildkit

I tried
docker buildx build .
I am still getting
[stage-1 1/3] FROM mcr.microsoft.com/dotnet/runtime-deps:8.0-preview-jammy-chiseled@sha256:833c72f664dfa4e98ee66eab93e8a67ab  0.0s
=> CACHED [stage-1 2/3] WORKDIR /app                                                                                0.0s
=> ERROR [build 2/8] RUN <<EOF (apt-get update...)                                                                               0.4s

[build 2/8] RUN <<EOF (apt-get update...):
0.364 E: Invalid operation update
0.369 Reading package lists...
0.376 Building dependency tree...
0.376 Reading state information...
0.377 E: Unable to locate package build-essential

Very odd. I haven't tried that Dockerfile in WSL. Which distro (and version) were you using. I successfully built that Dockerfile in Ubuntu 22.04.

It’s Ubuntu 22.04 distro but it completely rejected that <<EOF
On Mon, Aug 7, 2023 at 2:40 PM Rich Lander @.***> wrote:

Very odd. I haven't tried that Dockerfile in WSL. Which distro (and
version) were you using. I successfully built that Dockerfile in Ubuntu
22.04.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8663#issuecomment-1668403721, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7DCF25DHKOOFHDF36O5FLXUEZDNANCNFSM6AAAAAA3ENRMHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I wrote the file in vscode in windows with with wsl support
On Mon, Aug 7, 2023 at 2:50 PM Jason Durnil @.***> wrote:

It’s Ubuntu 22.04 distro but it completely rejected that <<EOF
On Mon, Aug 7, 2023 at 2:40 PM Rich Lander @.***>
wrote:

Very odd. I haven't tried that Dockerfile in WSL. Which distro (and
version) were you using. I successfully built that Dockerfile in Ubuntu
22.04.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8663#issuecomment-1668403721, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7DCF25DHKOOFHDF36O5FLXUEZDNANCNFSM6AAAAAA3ENRMHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

But everything is running like a charm now
On Mon, Aug 7, 2023 at 2:52 PM Jason Durnil @.***> wrote:

I wrote the file in vscode in windows with with wsl support
On Mon, Aug 7, 2023 at 2:50 PM Jason Durnil @.***> wrote:

It’s Ubuntu 22.04 distro but it completely rejected that <<EOF
On Mon, Aug 7, 2023 at 2:40 PM Rich Lander @.***>
wrote:

Very odd. I haven't tried that Dockerfile in WSL. Which distro (and
version) were you using. I successfully built that Dockerfile in Ubuntu
22.04.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8663#issuecomment-1668403721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7DCF25DHKOOFHDF36O5FLXUEZDNANCNFSM6AAAAAA3ENRMHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

One last thing i wanted to mention that might be of interest when creating docker files for this is in the aot project
<InvariantGlobalization>false</InvariantGlobalization> gets set to true automatically. Microsoft.data.sqlclient will not work with this set to true. However my container wouldnt build when i set it to false so i had to add
RUN apt-get install libicu70
to get it to build. Hopefully it will now all work with my sql connections. If so you guys have something amazing here,

We set this value to true by default in AOT project files.

Yes I’ve tried it with the Microsoft.data.sqlclient package and using that
package fails in at if that is set to true.
On Mon, Aug 7, 2023 at 4:44 PM Rich Lander @.***> wrote:

We set this value to true by default in AOT project files.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8663#issuecomment-1668553472, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7DCF5WGFJUXCRDKEDFAR3XUFHRHANCNFSM6AAAAAA3ENRMHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yup. You can change the default.

This appears to be why the Dockerfile failed on your machine.
https://github.com/moby/buildkit/issues/3329#issuecomment-1385336309

Hello Richard I am really close to a solution but i need apt-get install libicu70 to be installed on mcr.microsoft.com/dotnet/runtime-deps:8.0-preview-jammy-chiseled. Ive noticed it is a slim build and exactly what i want but of course i cant run apt-get update or apt get install on their. In my build image I am using
FROM mcr.microsoft.com/dotnet/sdk:8.0-preview-jammy AS build ARG TARGETARCH RUN apt-get update RUN apt-get install libicu70 RUN apt-get install -y build-essential clang libz-dev
I just want to get the libicu70 install and wgatever path env variables it might need. Is there anything you could recommend.
when i use the build image as the main final image it ends up being like 843 mn insteade of 23 mb and that is not desirable.

Documented at https://github.com/dotnet/dotnet-docker/blob/main/samples/enable-globalization.md#ubuntu-chiseled-images

I tried this because the other one gave me errors from the beginning
`FROM golang:1.18 as chisel
RUN git clone --depth 1 -b main https://github.com/canonical/chisel /opt/chisel
WORKDIR /opt/chisel
RUN go build ./cmd/chisel
FROM mcr.microsoft.com/dotnet/sdk:8.0-preview-jammy AS build
RUN apt-get update
RUN apt-get install clang zlib1g-dev -y
COPY --from=chisel /opt/chisel/chisel /usr/bin/
RUN mkdir /rootfs
&& chisel cut --release "ubuntu-22.04" --root /rootfs
libicu70_libs
WORKDIR /source
copy csproj and restore as distinct layers
COPY *.csproj .
RUN dotnet restore -r linux-arm64
copy and publish app and libraries
COPY . .
RUN dotnet publish -r linux-arm64 --no-restore -o /app MySecondAotWebApi.csproj
RUN rm /app/.dbg /app/.Development.json
final stage/image
FROM mcr.microsoft.com/dotnet/runtime-deps:8.0-preview-jammy-chiseled
COPY --from=build /rootfs /
WORKDIR /app
COPY --from=build /app .
ENTRYPOINT ["./MySecondAotWebApi"]`
I get this globalization error when trying to build the native code part
`91.40 clang : error : linker command failed with exit code 1 (use -v to see invocation) [/source/MySecondAotWebApi.csproj]
91.42 /root/.nuget/packages/microsoft.dotnet.ilcompiler/8.0.0-preview.7.23375.6/build/Microsoft.NETCore.Native.targets(357,5): error MSB3073: The command ""clang" "obj/Release/net8.0/linux-arm64/native/MySecondAotWebApi.o
" -o "bin/Release/net8.0/linux-arm64/native/MySecondAotWebApi" -fuse-ld=bfd /root/.nuget/packages/runtime.linux-arm64.microsoft.dotnet.ilcompiler/8.0.0-preview.7.23375.6/sdk/libbootstrapper.o /root/.nuget/packages/runtime.linux-arm64.microsoft.dotnet.ilcompiler/8`

figured out my issue, for some reason i had labeled the linux builds asr arm64 instead of amd064 since with this script the #TARGETARCH variable was not coming through it builds now

Cool. The chisel pieces should all be in the chisel stage.

Is there anything pending here or can we close this issue?

If this continues to be a problem, please raise the issues in dotnet/docker (assuming they are container related).


test(controller): Ensure resubmitted workflows have correct labels

We rely on this label so it's good to include this in the tests.
Signed-off-by: terrytangyuan<EMAIL_ADDRESS>Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[x] My builds are green. Try syncing with master if they are not.
[x] My organization is added to USERS.md.

thank you!


flutter web canvaskit change local cache？

<EMAIL_ADDRESS><EMAIL_ADDRESS>in china ，this cnd speed very slow ，how to join local cache？

@1124863805
Your question is better suited for StackOverflow, as this doesn't sounds like a bug or feature request. Please see https://flutter.dev/community for resources and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


elem2d from brep unit

Codecov Report

Merging #237 (d968d5c) into main (dd4a8db) will decrease coverage by 0.49%.
The diff coverage is 55.77%.

@@            Coverage Diff             @@
##             main     #237      +/-   ##
==========================================
- Coverage   56.60%   56.10%   -0.50%
==========================================
  Files         221      222       +1
  Lines       27274    27198      -76
==========================================
- Hits        15439    15260     -179
- Misses      11835    11938     +103

Flag
Coverage Δ

gsagh
42.65% <28.31%> (-0.10%)
:arrow_down:

integration
43.34% <46.02%> (-0.46%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

GsaGH/Components/1_Properties/CreateProfile.cs
80.00% <ø> (-0.08%)
:arrow_down:

GsaGH/Components/2_Geometry/EditElement3d.cs
25.37% <0.00%> (ø)

GsaGH/Components/5_Results/GetResults.cs
80.19% <ø> (ø)

GsaGH/Components/5_Results/NodeContourResults.cs
29.13% <0.00%> (ø)

...aGH/Components/5_Results/SelectResults_OBSOLETE.cs
38.58% <ø> (ø)

...mponents/5_Results/TotalLoadsAndReactionResults.cs
93.26% <ø> (ø)

GsaGH/Components/GraveyardComp/BaseReader.cs
0.00% <0.00%> (ø)

...omponents/GraveyardComp/CreateMember3d_OBSOLETE.cs
41.09% <0.00%> (ø)

.../Components/GraveyardComp/CreateProp2d_OBSOLETE.cs
23.63% <0.00%> (ø)

...Components/GraveyardComp/EditElement1d_OBSOLETE.cs
39.71% <0.00%> (ø)

... and 53 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Mod not showing nor working in the gane

Mod Version:
DynamicSurroundings-1.12.2-<IP_ADDRESS> (latest)
Forge Version:
Forge 36.1.0 (latest)
Description:
I downloaded the mod and put it into my Forge mods folder, but when I launch the game, Dynamic Surroundings does not appear in the list of loaded mods and so it does not work. I only have Terra and this mod in my mods folder (which are known to be compatibles.
I don't know why your mod won't load. Can you help me please. Thx

Your using a version of Forge that is for 1.16... Clearly explains why.
1.12.2 uses <IP_ADDRESS>55. Forge 36.1.0 (Which is very outdated) is for 1.16.5.