No executable found matching command "dotent-newconsole"

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relev

ant.

The command is dotnet new console -o myApp, there's a whitespace between new and console.

Thanks @KexyBiscuit for catching that.
Closing as resolved.


Bump up client-go and apimachinery.

client-go 0ec10d4351f32832ab60d381d15e6d9e1f858bd3
apimachinery 28d5d926c7c976d5885f31ace03d4a9b3ad8abd2
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

lgtm! thanks


Duplicated Date for Last Day of Month

Tested in Firefox, Chrome and Edge
The last day of the month is duplicated. I just downloaded this calendar to try out yesterday but I'm pretty sure this problem wasn't there yesterday...

jsfiddle: http://jsfiddle.net/duck/aEwNt/
Edited to add: Yes, the problem wasn't there yesterday. I'm guessing someone is updating the code base right now :+1:

I wonder if this is related to #196. Either way the last day of the month is duplicated for every month here. I'll check this out.

@c-ni I can't recreate this in the test file. Can you pull down and run tests/test.html to verify that it's happening? I'd like to verify if it's moment or clndr.

@c-ni Your fiddle is using CLNDR version 1.2.4, loaded from the test page. Can you please try running this with the latest version of CLNDR to confirm the error?

Hi Mike,
I'm not at home right now, but will try it when I get home. I'm currently on my iPhone and noticed the same issue on your demo site.

@c-ni Hm, I think the problem is with that demo site, but I'll have to test it out fully later. The demo site hasn't been updated in a while and I think it uses a static copy of v1.2.4.

@mikegioia That was the issue -- it explained why it worked in my app (was using the latest version), and not on the demo site nor jsfiddle (which was an old one I found on stackoverflow). I updated to the latest version and it works great. Thanks for the amazingly fast responses!

Sure thing @c-ni Thanks for following up on that.


add issue forms for various issues

Fixes #3474
I have added

bug_report.yml
feature_request.yml
documentation.yml and
other.yml
issue form template file to .github/ISSUE_TEMPLATE folder.

Also added a config.yml file to stop users from opening blank issue. I have also provided the link for 24PullRequests community on Gitter.

Thanks!


Added tax symbol

I am new to open source, so hopefully this is added correctly. Not sure how to test the website/program locally on my machine.

Welcome to open source, and thanks for contributing!
Yep, the format's correct. I'd describe it as 'percentage', to be more general. Well done :D


Enable KOTS configuration on bootstrap and updates to increase max pod per node

There is no option to increase maxpods 110 per node for kots.
Provide a feature in kots to do this in kubelet config.

We have an internal issue (SC-35062) tracking this request. There's no firm ETA for when this might be supported, but I'll note this request for follow-up later. Thanks!


Add/reorganize contributor documentation

Zero functional code. I (hopefully) wasn't too dogmatic about these changes, but I think it could help cut down the volume of issues. I scanned through a few pages and referenced 5 that would be closed automatically via a301e2c. See expanded commit messages for more information. Also note, I added an empty PR template; not sure how (or if) you want that.
Along the lines of #4734, I'd like to see as many people adopt this as possible. And, the Is it maintained? page isn't doing this excellent project justice.
Thanks!

Sure thing!

Thanks @allanbreyes 👍


Removing the MaterializeCSS dependency

There isn't much use of MaterializeCSS, so it's better to remove it.

Hi! I'll take this issue :)

Alright, thanks for the help. I added travis ci for auto-deployment, I hope it'll help.

Hi, Can I take this issue?

Yeah @nuwan94

@nuwan94 still on it?

Will it be better to use .css files or better go with styled-components?

I dont know

@nuwan94 still on it?
EDIT: If not can I take it?

Still asking @nuwan94

Repo isn't even forked by him, so you can do it @CmdEngineer

Alright

@GermaVinsmoke
Apparently MaterialCSS does have a big usage:

Buttons and the graph are unaffected

The main thing is materialize-css grid -
className="container"
className="row"
className="col "
I think we can use flexbox instead of this.
A lot of things will be solved with the help of flexbox.
The other thing is className="card". So, for this, I think it'll be better to use styled-components coz reusable Card component.
Removing materialize-css as it is having some security issues and I think we don't need it as it is having a size of 175kB (minified) and styled-components is having a size of 45kB (minified).

materialize-css as it is having some security issues
how does css introduce security issues?

Suggestion: maybe use Spectre?

materialize-css as it is having some security issues
how does css introduce security issues?

Three of its javascript component are having vulnerabilities and there's no patch fix for that 🤔. So, if we're not using any of the JS Components then why to keep a module of that big size. I think that Spectre.css is cool and it'll work.


Cannot connect JK BMS

Hi - sorry if I'm missing something obvious here, but I would really like to get this working.
First it appears to connect ok (it has the correct bt address & correct Pin)
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
INFO     [main.py:68] BT Discovery:
INFO     [main.py:73] BT Device   JKbms   address=C8:47:8C:E5:02:41
INFO     [main.py:73] BT Device   6C-A6-94-6C-7B-04   address=6C:A6:94:6C:7B:04
INFO     [main.py:73] BT Device   5A-A1-02-59-86-96   address=5A:A1:02:59:86:96
INFO     [main.py:73] BT Device   N09XA   address=E1:2F:A1:F9:CA:62
INFO     [main.py:73] BT Device   Tile   address=FE:04:2B:6C:AF:EC
INFO     [bt.py:126] BMS JKBt(C8:47:8C:E5:02:41) keep alive enabled
INFO     [main.py:195] connecting mqtt mosquitto@core-mosquitto
INFO     [main.py:232] Fetching 1 BMS + 0 others concurrently, period=1.00s, keep_alive=True
INFO     [sampling.py:61] connecting bms JKBt(C8:47:8C:E5:02:41)
INFO     [main.py:106] mqtt watchdog loop started with timeout 120.0s
But then I get an error message:
asyncio.exceptions.TimeoutError
ERROR    [sampling.py:125] battery1 error: <class 'asyncio.exceptions.TimeoutError'>
INFO     [sampling.py:51] bms debug data: %s
ERROR    [main.py:85] Error (num 6) reading BMS:
ERROR    [main.py:86] Stack: Traceback (most recent call last):
File "/usr/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/app/main.py", line 81, in fetch_loop
await fn()
File "/app/bmslib/sampling.py", line 47, in call
return await self.sample()
File "/app/bmslib/sampling.py", line 69, in sample
sample = await bms.fetch()
File "/app/bmslib/jikong.py", line 167, in fetch
await self._fetch_futures.wait_for(0x02, self.TIMEOUT)
File "/app/bmslib/init.py", line 44, in wait_for
return await asyncio.wait_for(self._futures[name], timeout)
File "/usr/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
Do you have an idea what the cause of this could be? I have added the pin in the configuration pin:  "1234" - I believe it needs the "" or it doesn't work. Or should I be adding the pin some other way? Thanks for your help.

Hi, i have no help for you unfortunately as im in the same boat, but, do you need to enter a pin when you connect with your phone? As i dont, just the first time if i remember? And only when changing settings..

Thanks for the suggestion. I've tried removing the password & also deliberately putting in an incorrect password and it seems it comes up with the same error. So not sure if it's just not reading the password correctly or if there's another problem.

I have the same problem but for the jbd bms
Traceback (most recent call last):
  File "/app/main.py", line 81, in fetch_loop
    await fn()
  File "/app/bmslib/sampling.py", line 47, in __call__
    return await self.sample()
  File "/app/bmslib/sampling.py", line 69, in sample
    sample = await bms.fetch()
  File "/app/bmslib/jbd.py", line 75, in fetch
    buf = await self._q(cmd=0x03)
  File "/app/bmslib/jbd.py", line 69, in _q
    return await self._fetch_futures.wait_for(cmd, self.TIMEOUT)
  File "/app/bmslib/__init__.py", line 44, in wait_for
    return await asyncio.wait_for(self._futures[name], timeout)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

So I've double checked MQQT connection. This is definitely working - all ok in the MQQT log. I've tried both the correct pin, the incorrect pin, and no pin at all, and I'm getting the same error message each time. Which makes me think it's not reading the pin correctly? Can I check the pin format should be
pin: "1234"
?

batmon doesn't use the pin for JK. Actually JK password protection is fake, as authentication is done within the app (the BMS just sends the password in clear text). So I doubt that this issue is related to password.
Did you try to toggle keep_alive ?

TimeoutErrors can occur when there is an issue with the driver. Reboot, restart BMS. Try another Bluetooth adapter


Drop Python3.4

Python 3.4 has become EOL on March 18, 2019.
https://www.python.org/dev/peps/pep-0429/

Codecov Report

Merging #127 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #127   +/-   ##
=======================================
  Coverage   92.84%   92.84%
=======================================
  Files          13       13
  Lines        1328     1328
=======================================
  Hits         1233     1233
  Misses         95       95

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 5c03b3b...ef672a3. Read the comment docs.

3.4.10 final: March 18, 2019
the last release was 3/18/2019.
I think it's better to wait for a bit longer before dropping it.

/hold
Let's keep this open and merge this after a few months then.

@yliaog can this be moved forward. It's not a good service for the community to support python3.4.

@micw523 what do you think?

@yliaog It's probably fine. I see Matplotlib has already dropped Python 3.4.
/cc @roycaihw

@micw523 sounds good to me. could you please cancel the hold then?

/hold cancel

/lgtm
/approve


No indication a warning is inconclusive

Environment

IDE Version (e.g. CLion 2016.3.2): CLion 2020.3 EAP
Cppcheck executable version (cppcheck --version): 2.1
Cppcheck plugin version: 1.4.2
Exact strings used in cppcheck plugin options:

cppcheck options: --enable=all --inconclusive

Expected behaviour
Warning shown as tooltips should indicate they are inconclusive.
I ran into analyzing a suspected false negative which turned out to be a inconclusive warning. I could confused since one nstallation showed the warning and one didn't. It turned out one was configured with --inconclusive.
Actual behaviour

test.cpp:14:22: warning:inconclusive: Access of moved variable 'a'. [accessMoved]
  std::string name = a.s_;
                     ^
test.cpp:13:8: note: Calling std::move(a)
  func(std::move(a));
       ^
test.cpp:14:22: note: $symbol:a
Access of moved variable '$symbol'.
  std::string name = a.s_;
                     ^

Steps to reproduce the behaviour

I seem to recall in IntelliJ there are different kinds of warning levels. Perhaps we could use "weak warning" or something similar to categorize inconclusive warnings.

I don't think they should have a different level since inconclusive could be warnings or errors. Just having it visible in the tooltip might be enough I think.

While at it... I also think it is not necessary to show the Cppcheck severity since that is already reflected by the CLion severity with the new Problems view that feel quite redundant:

Adding the "inconclusive" in braces instead would make sense though.


Add support for preview features in PmdExtension

Currently it is not possible to run the PMD task on code that uses java preview features and is compiled using --enable-preview. The PMD task will not fail, but will also not run the rules on those classes. The following error is displayed:  Error during type resolution of field '{redacted}' in class {redacted} due to: java.lang.UnsupportedClassVersionError: Preview features are not enabled for {redacted} (class file version 61.65535). Try running with '--enable-preview'.
PMD supports a way to enable preview features by defining the java version as documented here.
Expected Behavior
The PMD task runs the rules on java files that use preview features.
Current Behavior
The PMD task fails to run the rules on java files that use preview features.
Context
We currently can not rely on PMD to verify our rules on classes where we use preview features.
Related issues
#11107 and #15280.
Proposed change

Adding a new field Propery<String> javaVersion to Pmd.java
Adding a mapping from the javaVersion field to the sourceLanguage from PMDTask in PmdInvoker.groovy

ant.pmd(antPmdArgs) {
  sourceLanguage(name: "java", version: javaVersion)
}

Note: There currently exists a TargetJdk enum that is used for PMD versions < 5.0.0. I would not use/extend that enum with more versions, because PMD only supports the preview language features for the latest two java versions and that would mean updating that enum for each java release or when PMD changes it's mind. Keeping it a String is the most flexible solution.

Or maybe make the source language fully customizable by defining a languageName and a languageVersion? The language name can default to java, but defining a default for the version is not possible I think.

@JD-CSTx
PMD needs 2 things to correctly analyse java code that uses preview features:

--enable-preview needs to set, either using PMD_JAVA_OPTS or passing it to the jvm running the PMD code

when this is not set PMD will log: Error during type resolution of field '{redacted}' in class {redacted} due to: java.lang.UnsupportedClassVersionError: Preview features are not enabled for {redacted} (class file version 61.65535). Try running with '--enable-preview'

a language version with the -preview suffix needs to be selected.

when this is not set PMD will log: Caused by: net.sourceforge.pmd.lang.java.ast.ParseException: Line 24, Column 73: Pattern Matching in Switch is only supported with JDK 17 Preview. (an example of a preview feature)

Your solution fixes the first problem, but I don't see how it allows for PMD to parse preview features.

Your solution fixes the first problem, but I don't see how it allows for PMD to parse preview features.
@DavidOpDeBeeck You're right, in the end it doesn't fix anything at all. We really need an "enable-preview" feature.


[bug]: Install Error After Power Cut

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
No response
What happened?
During initial installation, I had a power cut before installation could finish. The power cut happened after installing all requirements during the Model download phase. On attempting to resume the installation, I started getting an error (see below).
Building wheels for collected packages: InvokeAI
Building wheel for InvokeAI (setup.py) ... done
Created wheel for InvokeAI: filename=InvokeAI-2.2.5-py3-none-any.whl size=2049642 sha256=b8c4b672da0c37edfdd56521fab9cbe67f3a27e6e2e19fadca71f70121011ba7
Stored in directory: C:\Users\username\AppData\Local\Temp\pip-ephem-wheel-cache-x9y55u0d\wheels\05\d1\14\7329c9dd2ba9b671a7a0c88268926239feea8ba165fd4bf269
Successfully built InvokeAI
Installing collected packages: InvokeAI
Successfully installed InvokeAI-2.2.5
Installation successful.
.\templates\rootdir\configs\INITIAL_MODELS.yaml
.\templates\rootdir\configs\models.yaml.example
.\templates\rootdir\configs\sd-concepts.txt
.\templates\rootdir\configs\stable-diffusion\v1-finetune.yaml
.\templates\rootdir\configs\stable-diffusion\v1-finetune_style.yaml
.\templates\rootdir\configs\stable-diffusion\v1-inference.yaml
.\templates\rootdir\configs\stable-diffusion\v1-inpainting-inference.yaml
.\templates\rootdir\configs\stable-diffusion\v1-m1-finetune.yaml
8 File(s) copied
Loading Python libraries...
Traceback (most recent call last):
File "d:\invokeai.venv\Scripts\configure_invokeai.py", line 24, in
from transformers import CLIPTokenizer, CLIPTextModel
File "d:\invokeai.venv\lib\site-packages\transformers_init_.py", line 30, in
from . import dependency_versions_check
File "d:\invokeai.venv\lib\site-packages\transformers\dependency_versions_check.py", line 17, in
from .utils.versions import require_version, require_version_core
File "d:\invokeai.venv\lib\site-packages\transformers\utils_init_.py", line 59, in
from .hub import (
File "d:\invokeai.venv\lib\site-packages\transformers\utils\hub.py", line 1087, in
cache_version = int(f.read())
ValueError: invalid literal for int() with base 10: '\x00'
Configuration failed. See above for error messages and check https://invoke-ai.github.io/InvokeAI/installation/INSTALL_AUTOMATED/#troubleshooting for potential solutions.
The installer will exit now.
Press any key to continue . . .
I have attempted to delete the whole folder and start over, continue the installation from where it is, and delete and reinstall only the specific module in the error. None of the above have worked.
I'm out of ideas on how to fix this.
Screenshots
No response
Additional context
No response
Contact Details
No response

I "fixed" my own problem but am not happy with doing it this way. I had to change the code in transformers to get past the error.
By changing the site-package at the position indicated below,
yadayada.venv\lib\site-packages\transformers\utils\hub.py", line 1087, in
cache_version = int(f.read())
to the following,:
cache_version_file = os.path.join(TRANSFORMERS_CACHE, "version.txt")
if not os.path.isfile(cache_version_file):
cache_version = 0
else:
with open(cache_version_file) as f:
try:
cache_version = int(f.read())
except ValueError as e:
print("This is where I was getting a weird value error. "
"Converting the odd value to 0 base 10 instead of 0 base 16")
cache_version = 0
I caught the error and got past the point where it broke the install and it finished running.
Code in Bold is what I added.
tl;dr
Somewhere, there is a hex zero being used where there should be a decimal zero and it causes problems sometimes.

Sorry to be responding to this late, but you should have been able to fix the problem by removing the invokeai directory and its .venv subdirectory. .venv contains all the libraries that are installed, and apparently one of them became corrupted during your power cut.


Monitoring v2 - disable default exporters does not work

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Launch the Rancher-Monitoring-v2 app without Default Exporters

Result:

all exporters related deployments are deployed, which is the opposite of what we expect

It looks like setting Configure Default Exporters False makes all sub-settings applied as True.

Closing this issue out as we're moving in favor of Custom UIs for launching Monitoring V2


Offset of top level tree items changes with icon them change

From here by @LazarusX

I think that is the expected result. The whitespace you see is there for twisties.

@aeschli Why is the twisty behavior different when switching the file icon theme between Seti and Minimal? In addition, I think the file icon theme setting is not supposed to affect the appearance of extension tree views (see the screen cast in comment: https://github.com/Microsoft/vscode/issues/42097#issuecomment-363645303)

In general, the goal is to have all labels of the same hierarchy level aligned.
The VSCode Set theme does not have any folder icons. In that case, the file icons are shifted to the left, and align with the twisties of folders at the same level. Best is to try it out with files and folders at the same level.
@sandy081 is looking into the custom trees. which can have user-provided icons as well as file icons from the file icon theme.
IMO, again, the custom tree should make sure, that all labels are aligned.
To do so, the custom tree provider will have to provide placeholder icons for file and folders in case that the current file icon theme does not provide these.
The custom tree provider should also be able to indicate whether

the tree should always show icons for all items: Placeholders icons have to be used for file/folder/items that don't provide any
the tree should follow the style of the current file icon theme: No icons, icons only for leafs ('seti' style) or show icons for all items. Again placeholders icons are required for non-file/folder items.

Your point regarding the icons in the file explorer makes sense to me.
But for custom trees, it seems that currently there is no way for extensions to respond to file icon theme style changes.

Agreed that custom views should not be concerned about file icon themes. Reopening it

Fixed by ea787762dbbc9e9fbcce7556117957cb763124cd

Reopening it because #28974 (ea787762dbbc9e9fbcce7556117957cb763124cd) is reverted

Fixed by 11a262ea52ede4dfdd36e4a8ee29e86f2947097b


libsigsegv: add enableSigbusFix option (fix bug related to old kernels)

Motivation for this change
An old (< 3.18.6) kernel bug keeps biting people (#28464, #6028): tests fail because the kernel wrongly emits a SIGBUS upon stack overflow. On systems with old kernels, this makes nix unusable.
Work has already been done to remove libsigsegv from stdenv bootstrapping process (https://github.com/NixOS/nixpkgs/commit/8137a8cb73833432e8da8281663b56ac01d3ba0b), however it does not solve the problem when libsigsegv is still required by a package and the kernel cannot be updated.
Things done

Added a simple patch file: sigbus_fix.patch.
Added a new enableSigbusFix attribute defaulting to false.
Added a condition on enableSigbusFix to apply the patch.

I couldn't use a full-fledged Nix environment for tests, however the default behaviour (i.e. no patch, no new explicit value) is strictly unchanged.

Travis kills the building job because the log is too long (> 4MB) in the first two cases. In the 3rd, Travis errors even before trying to build libsigsegv.

Don't worry about travis.


build: update windows toolchain

Commit Message: bump CI image
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:

/retest

Looks like a genuine failure with absl/synchronization failure in a Windows system call: The system cannot find the file specified. I can't proceed further since I need a windows dev enviornment to debug.

I can't proceed further since I need a windows dev enviornment to debug.

yeah, this is a recurring issue
probs we should back out the upstream change until we have resolved
cc @davinci26 @wrowe @sunjayBhatia

sorry, not really working too much on Windows at the moment so i don't have a workstation handy but this might be relevant to the attempted bump: https://learn.microsoft.com/en-us/visualstudio/releases/2022/system-requirements#microsoft-visual-studio-build-tools-2022-system-requirements

I see. @phlax we can revert my change until we can test run the container somehow, since the container didn't build correctly.


Bug when downcasting Proc

I'm playing with type inference in the Crystal Playground. This code:
a = 1
echo_a = ->{ a }

a = "hello"
echo_a.call

produces this:
BUG: trying to downcast (Proc((Int32 | String)) | Proc(Int32)) <- Proc((Int32 | String))

The strange thing is this just happens in the playground. When I download the code and compile it natively, it runs well, and I can print a, it is "hello".

compiler:

 Crystal 0.30.1 (2019-08-13)

 LLVM: 8.0.1
 Default target: x86_64-pc-linux-gnu

OS: Manjaro Linux x86_64 on Kernel 4.19.69

The strange thing is this just happens in the playground

The playground modifies the code you feed it by adding instrumentation, essentially making it a different program that can exhibit different bugs.


Add scenario tags in the scenario selector

Description
having scenario tags displayed in the scenaro slector help spotting a specific scenario. Can be hard.
Each tag value must have one color. Like github labels

In particular when they are defined as authorized_tags as specified in the documentaion.
A similar improvement also for generic labels and not only tags. If scenario has label key in the property dictionary with a set of strings as value, the selector will display.
For tags we should provide a noolean to activate the property
import taipy.gui.builder as tgb

tgb.scenario_selector("{scenario}", tags=True)

For generic labels we should provide the dict key
import taipy.gui.builder as tgb

tgb.scenario_selector("{scenario}", label=label)

I can help on python only. Please.
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

I like this idea. It makes the scenario selector a lot more practical and with a better UX. We should find a way to design it

Hello @rohan011001
Thank you for your proposal.
Can you have a look to the issue #1075. This is somehow related to improve user experience and to make it easier to select one scenario in a long list.
Do you believe it can solve your issue as well?

@jrobinAV
Yes I think filter and sort is better than display tags. Not exclusive. If I have filter, I don't need tags.
But can you show me the documentation? I can't find it. How can I use filters and sort?

filter is coming in the next version and will be documented then
Would you like to close this issue @rohan011001  ?

hey there, I would like to pick this as my first issue to contribute to Hacktoberfest. I am completely new to open source contributions. Please guide me along the way.

Great, let me assign this to you @mohammed-anwar404. You can ask @jrobinAV and @FredLL-Avaiga for more information.
Here is documentation on contributing to Taipy.
Thank you for your contribution!

Thanks, @FlorianJacta for assigning me this issue. I am looking forward to learn and to contribute.
If I get stuck I will reach out to the Taipy team for help.

So are u saying that we need to add the colour to the scenarios tags?

To add these tags inside the scenario selector like GitHub does for labels. For example, in this app, we have a scenario selector and it does not contain the tags that scenarios have. https://supply-chain.taipy.cloud/scenario

Hello @mohammed-anwar404, Are you working on this issue?

Hello @jrobinAV, Currently, I am not working on this issue. You can assign this issue to anyone who likes to take it up. I do need some time to understand and contribute.

OK, Thank you.


Added example jupyter notebook into the examples folders

As there are some example .py scenes, I think a notebook example is a good addition.

yep, good point, I will remove it.

As it is convenient to store jupyter notebooks in the manim project folder, I added the jupyter/ folder to the gitignore which ensures that the notebooks are not version controlled.

Can this be merged @behackl ?

Here is how the binder link looks now in the docs: https://manimce--1029.org.readthedocs.build/en/1029/installation.html

Depends on #1013.
I just tried it, and without #1013 this is not working currently:

Depends on #1013

I'm generally unsure what the appropriate label for this PR is. Maybe documentation?


[BUG]: Doesn't work as expected

Description of the bug
At first I tried it on a local News site and got blocked by Cloudflare. So I thought I'd use a Medium article and got the same blocked by Cloudflare page.
Link 1
Link 2
Do you have your instance running as per your GitHub ReadMe?
I have installed this as a Docker app on my unRAID server. Will play around with it a bit more and see if I can figure anthing out.
Steps To Reproduce
Use links above and see if they can be accessed.
Additional Information
No response

The same thing for me. The error says "Please enable cookies"

Yeah, I've yet not found a fix for this issue. If anyone wants to help or has any ideas please say.

Mine worked as long as I include the http:// in the domain name. But it doesnt block ads like 12ft.io . so it does have the benefit of being self hosted but does not block ads but so far plage load for me
OK yeah medium did block me :(

I always get the Cloudflare block too.

When trying to access WSJ, I get "Please enable JS and disable any ad blocker." Links from The Atlantic load, but style sheets are broken, which makes it difficult to read. Other news sites with paywalls also didn’t work well; styles are stripped and/or the content doesn't expand as expected. These all seem to work on archive.today for comparison.

The larger sites are probably verifying the crawler https://developers.google.com/search/docs/crawling-indexing/verifying-googlebot


Added Bill, and BillingServices logic

Yeah please fix all the white space changes, this project adheres to the internal Vultr Standard which uses tabs with the size of 4


Update switch-statements-practice-answers.md

Reformatted the answer that had an issue. Put the answer in a code block.

The code for the answer doesn't have newlines, you might want to edit that so it matches with the output

The changes in this issue may want to be split into a separate PR, as outside of the changes made to the formatting, there seems to be additional in-progress developments being made to the switch statements page.


Support for dynamic imports of ES modules

Hey, nice tool you've got here. I'm using it in a project I'm working on. I was trying to see if I could use the new dynamic imports in the demo jsbin but got an error:
SyntaxError: 'import' and 'export' may appear only with 'sourceType: module'.
Do I need to do something special to get it to work? Or is it the environment setup I should be looking at? (since I believe it needs me to use a <script type="module"></script>)

Unfortunately, Sval don't support ES6 module as well as dynamic import. I think you could use webpack to support dynamic import, and pass the import promise to Sval instead, like:
const importPromise = import('xxx')
const interpreter = new Sval
interpreter.import('getSomeModule', importPromise)
interpreter.run(`
    getSomeModule.then(module => {
        // use the module
    })
`)

Thanks for letting me know. I am not sure using webpack would work for my use case, since I want to import the modules via a HTTP URL, rather than a local file (making use of the pika.dev CDN)


Outdated Google Cloud Platform logo (again!)

This was fixed in #1 but has reverted.
Could you please fix this again? High-resolution asset here. Thank you!

Hi @craigbox please find in 0.9.4 under Infrastructure https://github.com/cncf/landscape/blob/master/landscape/CloudNativeLandscape_v0.9.4.jpg


Dynamic content creation

Addresses Issue #10

[x] Related GitHub issue(s) linked in PR description
[x] Destination branch merged, built and tested with your changes
[x] Code formatted and follows best practices and patterns
[x] Code builds cleanly (no additional warnings or errors)
[x] Manually tested
[x] Automated tests are passing
[x] No decreases in automated test coverage
[ ] Documentation updated (readme, docs, comments, etc.)

After further conversation, we are closing this PR and the associated issue for now and potentially revisiting it at some point in the future.


Mqtt5 unsubscribe

Unsubscribe op and tests
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The swiftlint change looks good to me, while I feel we should call it out and have Waqar have a quick look on it.
Other than that, the PR looks good to me.


Report Aura Equivocations to runtime

Following #911, we have an Aura consensus engine embedded in substrate. And while its verifier rejects unverified blocks, it does not issue misbehavior checks on the wire nor chain yet. Unlike with other block production mechanisms, these aren't happening in messages between one another but at the level where the new block would be attempted to be imported.
The main type of misbehavior to check for is equivocating, or signing multiple blocks in the same slot. Other types of misbehavior, like signing a bad block or signing a block out-of-turn have intrinsic economic penalties associated with them, either by skipping out on rewards or losing reliability with peers in the p2p network.
A proof-of-equivocation is just two headers (the body may be valid or invalid), both signed by the same voter, with seal mentioning the same slot. A runtime module should be created for checking equivocations.
This can be tracked by keeping track of the last N ( = 1000) slots we've seen blocks for per author. We add to this after checking the header. If there is ever one in that position already, we will issue a report to the runtime with our proof. See https://github.com/paritytech/substrate/issues/2181 for a rough outline on how to do such reports.

Neither Kusama nor Polkadot use AuRa.  Can we close this?

@bkchr


jx-secret heath check pod crashes

On a new AKS cluster, I've got this error:

time="2021-01-12T12:49:05Z" level=info msg="Found instance namespace: kuberhealthy"
time="2021-01-12T12:49:05Z" level=info msg="Kuberhealthy is located in the kuberhealthy namespace."
starting jx-webhooks health checks
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x12080b4]
goroutine 1 [running]:
main.Options.findErrors(0x15b0f80, 0xc000341430, 0x0, 0x22, 0x0, 0x0, 0x0)
    /workspace/source/cmd/jx-secrets/main.go:68 +0x114
main.main()
    /workspace/source/cmd/jx-secrets/main.go:32 +0x107
stream closed

(commit ref for the cluster: jx3-gitops-repositories/jx3-terraform-azure@8688dcb)

No missing external secret:

$ kubectl get externalsecrets -n jx
NAME                             LAST SYNC   STATUS    AGE
jenkins-maven-settings           16s         SUCCESS   60m
jenkins-release-gpg              2s          SUCCESS   60m
jenkins-x-chartmuseum            14s         SUCCESS   60m
jx-basic-auth-htpasswd           13s         SUCCESS   60m
jx-basic-auth-user-password      1s          SUCCESS   60m
lighthouse-hmac-token            11s         SUCCESS   60m
lighthouse-oauth-token           6s          SUCCESS   60m
nexus                            7s          SUCCESS   60m
tekton-container-registry-auth   10s         SUCCESS   60m
tekton-git                       4s          SUCCESS   60m

No missing external secret:

$ kubectl get externalsecrets -n jx
NAME                             LAST SYNC   STATUS    AGE
jenkins-maven-settings           16s         SUCCESS   60m
jenkins-release-gpg              2s          SUCCESS   60m
jenkins-x-chartmuseum            14s         SUCCESS   60m
jx-basic-auth-htpasswd           13s         SUCCESS   60m
jx-basic-auth-user-password      1s          SUCCESS   60m
lighthouse-hmac-token            11s         SUCCESS   60m
lighthouse-oauth-token           6s          SUCCESS   60m
nexus                            7s          SUCCESS   60m
tekton-container-registry-auth   10s         SUCCESS   60m
tekton-git                       4s          SUCCESS   60m

I've then manually deleted this failing pod, all the next ones are "completed" without any problem.

I've then manually deleted this failing pod, all the next ones are "completed" without any problem.

I've got other health checks crashing.
deployment:
time="2021-01-13T21:10:14Z" level=info msg="Found instance namespace: kuberhealthy"
time="2021-01-13T21:10:14Z" level=info msg="Kuberhealthy is located in the kuberhealthy namespace."
time="2021-01-13T21:10:14Z" level=info msg="Found pod namespace: kuberhealthy"
time="2021-01-13T21:10:14Z" level=info msg="Performing check in kuberhealthy namespace."
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_DEPLOYMENT\_REPLICAS: 4"
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_SERVICE\_ACCOUNT: default"
time="2021-01-13T21:10:14Z" level=info msg="Check time limit set to: 14m45.119966409s"
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_DEPLOYMENT\_ROLLING\_UPDATE: true"
time="2021-01-13T21:10:14Z" level=info msg="Check deployment image will be rolled from \[nginxinc/nginx-unprivileged:1.17.8\] to \[nginxinc/nginx-unprivileged:1.17.9\]"
time="2021-01-13T21:10:14Z" level=info msg="Kubernetes client created."
time="2021-01-13T21:10:14Z" level=info msg="Waiting for node to become ready before starting check."
time="2021-01-13T21:10:15Z" level=error msg="Failed to check node age: nodes \\"aks-default-15766151-vmss000002\\" is forbidden: User \\"system:serviceaccount:kuberhealthy:deployment-sa\\" cannot get resource \\"nodes\\" in API group \\"\\" at the cluster scope"
time="2021-01-13T21:10:15Z" level=info msg="Starting check."
time="2021-01-13T21:10:15Z" level=info msg="Wiping all found orphaned resources belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Attempting to find previously created service(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Did not find any old service(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Attempting to find previously created deployment(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Did not find any old deployment(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Successfully cleaned up prior check resources."
time="2021-01-13T21:10:15Z" level=info msg="Creating deployment resource with 4 replica(s) in kuberhealthy namespace using image \[nginxinc/nginx-unprivileged:1.17.8\] with environment variables: map\[\]"
time="2021-01-13T21:10:15Z" level=info msg="Creating container using image \[nginxinc/nginx-unprivileged:1.17.8\] with environment variables: map\[\]"
time="2021-01-13T21:10:15Z" level=info msg="Created deployment resource."
time="2021-01-13T21:10:15Z" level=info msg="Creating deployment in cluster with name: deployment-deployment"
time="2021-01-13T21:10:16Z" level=info msg="Watching for deployment to exist."
time="2021-01-13T21:10:31Z" level=info msg="Deployment is reporting Available with True."
time="2021-01-13T21:10:31Z" level=info msg="Created deployment in kuberhealthy namespace: deployment-deployment"
time="2021-01-13T21:10:31Z" level=info msg="Creating service resource for kuberhealthy namespace."
time="2021-01-13T21:10:31Z" level=info msg="Created service resource."
time="2021-01-13T21:10:31Z" level=info msg="Creating service in cluster with name: deployment-svc"
time="2021-01-13T21:10:31Z" level=info msg="Watching for service to exist."
time="2021-01-13T21:10:31Z" level=info msg="Cluster IP found: <IP_ADDRESS>"
time="2021-01-13T21:10:31Z" level=info msg="Created service in kuberhealthy namespace: deployment-svc"
time="2021-01-13T21:10:31Z" level=info msg="Found service cluster IP address: <IP_ADDRESS>"
time="2021-01-13T21:10:31Z" level=info msg="Looking for a response from the endpoint."
time="2021-01-13T21:10:31Z" level=info msg="Beginning backoff loop for HTTP GET request."
time="2021-01-13T21:11:01Z" level=info msg="Retrying in 5 seconds."
time="2021-01-13T21:11:06Z" level=info msg="Successfully made an HTTP request on attempt: 2"
time="2021-01-13T21:11:06Z" level=info msg="Got a 200 with a GET to http://<IP_ADDRESS>"
time="2021-01-13T21:11:06Z" level=info msg="Got a result from GET request backoff: 200 OK"
time="2021-01-13T21:11:06Z" level=info msg="Successfully hit service endpoint."
time="2021-01-13T21:11:06Z" level=info msg="Rolling update option is enabled. Performing roll."
time="2021-01-13T21:11:06Z" level=info msg="Creating deployment resource with 4 replica(s) in kuberhealthy namespace using image \[nginxinc/nginx-unprivileged:1.17.9\] with environment variables: map\[\]"
time="2021-01-13T21:11:06Z" level=info msg="Creating container using image \[nginxinc/nginx-unprivileged:1.17.9\] with environment variables: map\[\]"
time="2021-01-13T21:11:06Z" level=info msg="Created rolling-update deployment resource."
time="2021-01-13T21:11:06Z" level=info msg="Performing rolling-update on deployment deployment-deployment to \[nginxinc/nginx-unprivileged:1.17.9\]"
time="2021-01-13T21:11:06Z" level=info msg="Rolled deployment in kuberhealthy namespace: deployment-deployment"
time="2021-01-13T21:11:06Z" level=info msg="Looking for a response from the endpoint."
time="2021-01-13T21:11:06Z" level=info msg="Beginning backoff loop for HTTP GET request."
time="2021-01-13T21:11:06Z" level=info msg="Successfully made an HTTP request on attempt: 1"
time="2021-01-13T21:11:06Z" level=info msg="Got a 200 with a GET to http://<IP_ADDRESS>"
time="2021-01-13T21:11:06Z" level=info msg="Got a result from GET request backoff: 200 OK"
time="2021-01-13T21:11:06Z" level=info msg="Successfully hit service endpoint after rolling-update."
time="2021-01-13T21:11:06Z" level=info msg="Cleaning up deployment and service."
time="2021-01-13T21:11:06Z" level=info msg="Attempting to delete service deployment-svc in kuberhealthy namespace."
time="2021-01-13T21:11:11Z" level=info msg="Attempting to delete deployment in kuberhealthy namespace."
time="2021-01-13T21:11:16Z" level=info msg="Attempting to delete deployment in kuberhealthy namespace."
time="2021-01-13T21:11:21Z" level=info msg="Finished clean up process."
time="2021-01-13T21:11:21Z" level=info msg="Reporting success to Kuberhealthy."
time="2021-01-13T21:12:40Z" level=info msg="Recovered panic: runtime error: invalid memory address or nil pointer dereference"
panic: runtime error: invalid memory address or nil pointer dereference \[recovered\]
   panic: interface conversion: interface {} is runtime.errorString, not string
\[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11ea333\]
goroutine 1 \[running\]:
main.main.func1(0xc0001f9f00)
   /build/cmd/deployment-check/main.go:189 +0x175
panic(0x130e480, 0x2000ab0)
   /usr/local/go/src/runtime/panic.go:679 +0x1b2
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.sendReport(0x2039aa8, 0x0, 0x0, 0x1, 0x0, 0xc0001f9638)
   /build/pkg/checks/external/checkclient/main.go:99 +0x4e3
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.ReportSuccess(0xc0001f9658, 0x46983c)
   /build/pkg/checks/external/checkclient/main.go:44 +0x7e
main.reportToKuberhealthy(0xc000113101, 0x2039aa8, 0x0, 0x0)
   /build/cmd/deployment-check/main.go:260 +0x33
main.reportOKToKuberhealthy()
   /build/cmd/deployment-check/main.go:253 +0x92
main.runDeploymentCheck(0x166ed60, 0xc00031d4a0)
   /build/cmd/deployment-check/run\_check.go:243 +0x149d
main.main()
   /build/cmd/deployment-check/main.go:194 +0x36e
stream closed

dns-status-internal:
time="2021-01-13T21:10:11Z" level=info msg="Found instance namespace: kuberhealthy"
time="2021-01-13T21:10:11Z" level=info msg="Kuberhealthy is located in the kuberhealthy namespace."
time="2021-01-13T21:10:11Z" level=info msg="Check time limit set to: 14m47.427936725s"
time="2021-01-13T21:10:11Z" level=info msg="Check pod is running on node: aks-default-15766151-vmss000000"
time="2021-01-13T21:10:11Z" level=debug msg="Getting pod: dns-status-internal-1610572204 in order to get its node information"
time="2021-01-13T21:10:11Z" level=error msg="Error waiting for node to reach minimum age: pods \"dns-status-internal-1610572204\" is forbidden: User \"system:serviceaccount:kuberhealthy:default\" cannot get resource \"pods\" in API group \"\" in the namespace \"kuberhealthy\""
time="2021-01-13T21:10:11Z" level=debug msg="Checking if the kuberhealthy endpoint: http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready."
time="2021-01-13T21:10:11Z" level=debug msg="http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready."
time="2021-01-13T21:10:11Z" level=debug msg="Kuberhealthy endpoint: http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready. Proceeding to run check."
time="2021-01-13T21:10:11Z" level=debug msg="Getting pod: dns-status-internal-1610572204 in order to get its node information"
time="2021-01-13T21:10:11Z" level=error msg="Error waiting for kube proxy to be ready: error getting kuberhealthy pod: pods \"dns-status-internal-1610572204\" is forbidden: User \"system:serviceaccount:kuberhealthy:default\" cannot get resource \"pods\" in API group \"\" in the namespace \"kuberhealthy\""
time="2021-01-13T21:10:11Z" level=info msg="Running DNS status checker"
time="2021-01-13T21:10:11Z" level=info msg="DNS Status check testing hostname: kubernetes.default"
time="2021-01-13T21:10:11Z" level=info msg="DNS Status check determined that kubernetes.default was OK."
2021/01/13 21:10:11 checkClient: DEBUG: Reporting SUCCESS
2021/01/13 21:10:11 checkClient: DEBUG: Sending report with error length of:0
2021/01/13 21:10:11 checkClient: DEBUG: Sending report with ok state of:true
2021/01/13 21:10:11 checkClient: INFO: Using kuberhealthy reporting URL:http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus
2021/01/13 21:10:11 checkClient: DEBUG: Making POST request to kuberhealthy:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11f1473]
goroutine 1 [running]:
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.sendReport(0x202a688, 0x0, 0x0, 0x1, 0xc0003265e8, 0xc0002edd74)
   /build/pkg/checks/external/checkclient/main.go:99 +0x4e3
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.ReportSuccess(0xc0002eddf0, 0xc0003265a0)
   /build/pkg/checks/external/checkclient/main.go:44 +0x7e
main.reportKHSuccess(0xc0002eddc8, 0xc0002edd70)
   /build/cmd/dns-resolution-check/main.go:182 +0x2d
main.(*Checker).Run(0xc0002f5ee0, 0xc00026fe40, 0xc0002eded0, 0x2)
   /build/cmd/dns-resolution-check/main.go:161 +0x204
main.main()
   /build/cmd/dns-resolution-check/main.go:119 +0x3ce
stream closed

I've got other health checks crashing.
deployment:
time="2021-01-13T21:10:14Z" level=info msg="Found instance namespace: kuberhealthy"
time="2021-01-13T21:10:14Z" level=info msg="Kuberhealthy is located in the kuberhealthy namespace."
time="2021-01-13T21:10:14Z" level=info msg="Found pod namespace: kuberhealthy"
time="2021-01-13T21:10:14Z" level=info msg="Performing check in kuberhealthy namespace."
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_DEPLOYMENT\_REPLICAS: 4"
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_SERVICE\_ACCOUNT: default"
time="2021-01-13T21:10:14Z" level=info msg="Check time limit set to: 14m45.119966409s"
time="2021-01-13T21:10:14Z" level=info msg="Parsed CHECK\_DEPLOYMENT\_ROLLING\_UPDATE: true"
time="2021-01-13T21:10:14Z" level=info msg="Check deployment image will be rolled from \[nginxinc/nginx-unprivileged:1.17.8\] to \[nginxinc/nginx-unprivileged:1.17.9\]"
time="2021-01-13T21:10:14Z" level=info msg="Kubernetes client created."
time="2021-01-13T21:10:14Z" level=info msg="Waiting for node to become ready before starting check."
time="2021-01-13T21:10:15Z" level=error msg="Failed to check node age: nodes \\"aks-default-15766151-vmss000002\\" is forbidden: User \\"system:serviceaccount:kuberhealthy:deployment-sa\\" cannot get resource \\"nodes\\" in API group \\"\\" at the cluster scope"
time="2021-01-13T21:10:15Z" level=info msg="Starting check."
time="2021-01-13T21:10:15Z" level=info msg="Wiping all found orphaned resources belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Attempting to find previously created service(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Did not find any old service(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Attempting to find previously created deployment(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Did not find any old deployment(s) belonging to this check."
time="2021-01-13T21:10:15Z" level=info msg="Successfully cleaned up prior check resources."
time="2021-01-13T21:10:15Z" level=info msg="Creating deployment resource with 4 replica(s) in kuberhealthy namespace using image \[nginxinc/nginx-unprivileged:1.17.8\] with environment variables: map\[\]"
time="2021-01-13T21:10:15Z" level=info msg="Creating container using image \[nginxinc/nginx-unprivileged:1.17.8\] with environment variables: map\[\]"
time="2021-01-13T21:10:15Z" level=info msg="Created deployment resource."
time="2021-01-13T21:10:15Z" level=info msg="Creating deployment in cluster with name: deployment-deployment"
time="2021-01-13T21:10:16Z" level=info msg="Watching for deployment to exist."
time="2021-01-13T21:10:31Z" level=info msg="Deployment is reporting Available with True."
time="2021-01-13T21:10:31Z" level=info msg="Created deployment in kuberhealthy namespace: deployment-deployment"
time="2021-01-13T21:10:31Z" level=info msg="Creating service resource for kuberhealthy namespace."
time="2021-01-13T21:10:31Z" level=info msg="Created service resource."
time="2021-01-13T21:10:31Z" level=info msg="Creating service in cluster with name: deployment-svc"
time="2021-01-13T21:10:31Z" level=info msg="Watching for service to exist."
time="2021-01-13T21:10:31Z" level=info msg="Cluster IP found: <IP_ADDRESS>"
time="2021-01-13T21:10:31Z" level=info msg="Created service in kuberhealthy namespace: deployment-svc"
time="2021-01-13T21:10:31Z" level=info msg="Found service cluster IP address: <IP_ADDRESS>"
time="2021-01-13T21:10:31Z" level=info msg="Looking for a response from the endpoint."
time="2021-01-13T21:10:31Z" level=info msg="Beginning backoff loop for HTTP GET request."
time="2021-01-13T21:11:01Z" level=info msg="Retrying in 5 seconds."
time="2021-01-13T21:11:06Z" level=info msg="Successfully made an HTTP request on attempt: 2"
time="2021-01-13T21:11:06Z" level=info msg="Got a 200 with a GET to http://<IP_ADDRESS>"
time="2021-01-13T21:11:06Z" level=info msg="Got a result from GET request backoff: 200 OK"
time="2021-01-13T21:11:06Z" level=info msg="Successfully hit service endpoint."
time="2021-01-13T21:11:06Z" level=info msg="Rolling update option is enabled. Performing roll."
time="2021-01-13T21:11:06Z" level=info msg="Creating deployment resource with 4 replica(s) in kuberhealthy namespace using image \[nginxinc/nginx-unprivileged:1.17.9\] with environment variables: map\[\]"
time="2021-01-13T21:11:06Z" level=info msg="Creating container using image \[nginxinc/nginx-unprivileged:1.17.9\] with environment variables: map\[\]"
time="2021-01-13T21:11:06Z" level=info msg="Created rolling-update deployment resource."
time="2021-01-13T21:11:06Z" level=info msg="Performing rolling-update on deployment deployment-deployment to \[nginxinc/nginx-unprivileged:1.17.9\]"
time="2021-01-13T21:11:06Z" level=info msg="Rolled deployment in kuberhealthy namespace: deployment-deployment"
time="2021-01-13T21:11:06Z" level=info msg="Looking for a response from the endpoint."
time="2021-01-13T21:11:06Z" level=info msg="Beginning backoff loop for HTTP GET request."
time="2021-01-13T21:11:06Z" level=info msg="Successfully made an HTTP request on attempt: 1"
time="2021-01-13T21:11:06Z" level=info msg="Got a 200 with a GET to http://<IP_ADDRESS>"
time="2021-01-13T21:11:06Z" level=info msg="Got a result from GET request backoff: 200 OK"
time="2021-01-13T21:11:06Z" level=info msg="Successfully hit service endpoint after rolling-update."
time="2021-01-13T21:11:06Z" level=info msg="Cleaning up deployment and service."
time="2021-01-13T21:11:06Z" level=info msg="Attempting to delete service deployment-svc in kuberhealthy namespace."
time="2021-01-13T21:11:11Z" level=info msg="Attempting to delete deployment in kuberhealthy namespace."
time="2021-01-13T21:11:16Z" level=info msg="Attempting to delete deployment in kuberhealthy namespace."
time="2021-01-13T21:11:21Z" level=info msg="Finished clean up process."
time="2021-01-13T21:11:21Z" level=info msg="Reporting success to Kuberhealthy."
time="2021-01-13T21:12:40Z" level=info msg="Recovered panic: runtime error: invalid memory address or nil pointer dereference"
panic: runtime error: invalid memory address or nil pointer dereference \[recovered\]
   panic: interface conversion: interface {} is runtime.errorString, not string
\[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11ea333\]
goroutine 1 \[running\]:
main.main.func1(0xc0001f9f00)
   /build/cmd/deployment-check/main.go:189 +0x175
panic(0x130e480, 0x2000ab0)
   /usr/local/go/src/runtime/panic.go:679 +0x1b2
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.sendReport(0x2039aa8, 0x0, 0x0, 0x1, 0x0, 0xc0001f9638)
   /build/pkg/checks/external/checkclient/main.go:99 +0x4e3
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.ReportSuccess(0xc0001f9658, 0x46983c)
   /build/pkg/checks/external/checkclient/main.go:44 +0x7e
main.reportToKuberhealthy(0xc000113101, 0x2039aa8, 0x0, 0x0)
   /build/cmd/deployment-check/main.go:260 +0x33
main.reportOKToKuberhealthy()
   /build/cmd/deployment-check/main.go:253 +0x92
main.runDeploymentCheck(0x166ed60, 0xc00031d4a0)
   /build/cmd/deployment-check/run\_check.go:243 +0x149d
main.main()
   /build/cmd/deployment-check/main.go:194 +0x36e
stream closed

dns-status-internal:
time="2021-01-13T21:10:11Z" level=info msg="Found instance namespace: kuberhealthy"
time="2021-01-13T21:10:11Z" level=info msg="Kuberhealthy is located in the kuberhealthy namespace."
time="2021-01-13T21:10:11Z" level=info msg="Check time limit set to: 14m47.427936725s"
time="2021-01-13T21:10:11Z" level=info msg="Check pod is running on node: aks-default-15766151-vmss000000"
time="2021-01-13T21:10:11Z" level=debug msg="Getting pod: dns-status-internal-1610572204 in order to get its node information"
time="2021-01-13T21:10:11Z" level=error msg="Error waiting for node to reach minimum age: pods \"dns-status-internal-1610572204\" is forbidden: User \"system:serviceaccount:kuberhealthy:default\" cannot get resource \"pods\" in API group \"\" in the namespace \"kuberhealthy\""
time="2021-01-13T21:10:11Z" level=debug msg="Checking if the kuberhealthy endpoint: http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready."
time="2021-01-13T21:10:11Z" level=debug msg="http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready."
time="2021-01-13T21:10:11Z" level=debug msg="Kuberhealthy endpoint: http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus is ready. Proceeding to run check."
time="2021-01-13T21:10:11Z" level=debug msg="Getting pod: dns-status-internal-1610572204 in order to get its node information"
time="2021-01-13T21:10:11Z" level=error msg="Error waiting for kube proxy to be ready: error getting kuberhealthy pod: pods \"dns-status-internal-1610572204\" is forbidden: User \"system:serviceaccount:kuberhealthy:default\" cannot get resource \"pods\" in API group \"\" in the namespace \"kuberhealthy\""
time="2021-01-13T21:10:11Z" level=info msg="Running DNS status checker"
time="2021-01-13T21:10:11Z" level=info msg="DNS Status check testing hostname: kubernetes.default"
time="2021-01-13T21:10:11Z" level=info msg="DNS Status check determined that kubernetes.default was OK."
2021/01/13 21:10:11 checkClient: DEBUG: Reporting SUCCESS
2021/01/13 21:10:11 checkClient: DEBUG: Sending report with error length of:0
2021/01/13 21:10:11 checkClient: DEBUG: Sending report with ok state of:true
2021/01/13 21:10:11 checkClient: INFO: Using kuberhealthy reporting URL:http://kuberhealthy.kuberhealthy.svc.cluster.local/externalCheckStatus
2021/01/13 21:10:11 checkClient: DEBUG: Making POST request to kuberhealthy:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11f1473]
goroutine 1 [running]:
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.sendReport(0x202a688, 0x0, 0x0, 0x1, 0xc0003265e8, 0xc0002edd74)
   /build/pkg/checks/external/checkclient/main.go:99 +0x4e3
github.com/Comcast/kuberhealthy/v2/pkg/checks/external/checkclient.ReportSuccess(0xc0002eddf0, 0xc0003265a0)
   /build/pkg/checks/external/checkclient/main.go:44 +0x7e
main.reportKHSuccess(0xc0002eddc8, 0xc0002edd70)
   /build/cmd/dns-resolution-check/main.go:182 +0x2d
main.(*Checker).Run(0xc0002f5ee0, 0xc00026fe40, 0xc0002eded0, 0x2)
   /build/cmd/dns-resolution-check/main.go:161 +0x204
main.main()
   /build/cmd/dns-resolution-check/main.go:119 +0x3ce
stream closed


[cloudflare-docs] Add Let's Encrypt to backup-certificates.md

Add Let's Encrypt as backup certificate authority

Hello! Thanks for flagging this.
Addressed in #9744


PLAT-128519: Support any valid CSS duration for any type prop in ui/Transition

Enact-DCO-1.0-Signed-off-by: YB Sung<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
The ui/Transition with fade or slide type prop supports only preset duration (short, medium, and long).  It is needed to support any valid CSS duration for them.
Resolution
Support any valid CSS duration for any type prop in ui/Transition
Additional Considerations
Links
PLAT-128519
Comments

@ybsung I just realized that you added a change log to a wrong file. :) Please move your log to the proper change log file.

@ybsung I just realized that you added a change log to a wrong file. :) Please move your log to the proper change log file.

@0x64

I just realized that you added a change log to a wrong file. :) Please move your log to the proper change log file.
I fixed it. Thanks for letting me know it.

@0x64

I just realized that you added a change log to a wrong file. :) Please move your log to the proper change log file.
I fixed it. Thanks for letting me know it.


fix(dropDownColour)added transparent colour

https://www.loom.com/share/6754255b426c40d592617c90f32d34e1

Closed as its merged into IconPicker already


chore: Prevent test suite artifact creation in work directory

Also remove a few other stale test assets while I'm here.
Fixes #4020
Fixes #3520

@rjsparks

CRITICALS:
?: (datatracker.E0006) A directory used by the I-D submission tool does not
exist at the path given in the settings file.  The setting is:
IDSUBMIT_REPOSITORY_PATH = /assets/ietfdata/doc/draft/repository

There are a ton of directories that are being created in docker/scripts/app-create-dirs.sh - it's unclear to me how many of them are actually needed to run a dev instance and the CI.

@rjsparks I think I made all the changes you requested?

Yes, I'm holding this for more work post the feat/rfc merge.

This didn't get returned to post feat/rfc. We should review it fresh to see if it's still the right thing to do.
cc: @jennifer-richards

I left a couple comments - cleaning up after the tests, even in /tmp or wherever those paths end up, would be nice but also tricky. If the tests pass against modern main, I would be inclined to accept this as an improvement and treat those future work.

Hopefully not stepping on @larseggert's toes, but just pushed changes that address my concerns. I think it's ready for @rjsparks to re-review?

No toes in the area :-) I won't get to this any time soon, so please do what you need to!

I am a little nervous at the "clean up on exit" vs "clean up as you go" approach as it adds to the recovery for the developer if the process goes away via kill -9 or the like, but am willing to try it.

I'm sympathetic. The kill -9 doesn't worry me terribly because it's rare and the impact is just a couple of directories in /tmp left over and atexit is robust against most normal exits.
I'd much rather create the temp dir separately for each test to maintain isolation. Before adding the atexit business I tried using the temp directory mechanism we have in our TestCase class and it kinda sorta worked, but ran into bad interactions with the test startup sequence. It definitely interacted with our checks for the directories existing, but IIRC the statics serving for tests was also broken by this because it's only set up once for the entire test run.


Update README.md

Updated README.md based on config.yml generated by the plugin.

Why does nobody care about this repo?

Unfortunately:

my other life commitments and desire to have a healthy lifestyle do not allow for 24/7/365 monitoring of my GitHub notifications
the quantity of messages & notifications I get per day often means it is not possible to (immediately) reply - I have to prioritise the important things and catch up on everything else when I occasionally get time to

I'm sorry if this falls short of your expectations, but it's the best I can do.
I urge you to try to be more sympathetic and understanding in the future - I am sure the people you interact with will appreciate it.
Thank you for the pull request.


Loading plugins from sourced vim config?

Is there a way to load some plugin from a config file that you source at runtime?
Doing:
call plug#begin('~/.local/share/nvim/plugged')
Plug <something>
call plug#end()

Will unload all already loaded plugins and will just load <something>.

I figured, just calling call plug#end() helps. I.e. in the sourced config, do this (skip plug#begin):
Plug <something>
call plug#end()


binary-search visualizer added

Visualization for binary search added!

Try to reduce the animation speed.

LGM


Tree View Selection lost it's branch active state

While fixing #563, we lost the state to notify if children of a node has been selected

Should be:

This is handled in assistance by Team D

I have a suggested soulution, PR will  be submitted soon, just have to go through the solution with @proand first


Test Optimization for Display Update and Event Filters

Here, I tried to do some micro adjustments. Listing the things I did, that is:

Removed repeated calls for time.time() by using a pygame.Clock
Filtered the event.get list to only get pg.QUIT event.
Switched from pg.display.update() to pg.display.flip()

Some optimizations I didn't include:

display: pg.display = pg.display.set_mode((WIN_SIZE, WIN_SIZE), pg.HWSURFACE|pg.DOUBLEBUF)

Hi,
Sorry for the delay, but I was in the middle of exam week.
Some changes you have made I already had implemented but not pushed.
I would have merged earlier if there wasn't a merge conflict.
Would you like to pull and then resubmit the request?

It's okay if you already implemented some of these edits. Actually, I forgot to actually see the master branch and determine what changes was made.
But I think you can use the pg.Clock as a replacement for your FPS counter, and to implement a control for your game speed (as the pygame engine tends to run as fast as it can, given that there's enough resources to use).
I'll just close this pull request now.


get value from ListFormBuilderTypeAhead

hi , i got some problem , i have List<dynamic> from backend service that return on FormBuilderTypeAhead (ex : data = [{label:"camera",value:001 , label:"iphone",value:002}] , i want to get label show for user and value insert to database , how can i do that ?

This still an issue?

@deandreamatias yes , solved.


Include all core Elixir apps in PLT

Seems like all the apps from the core Elixir distribution should be in the PLT?

Shouldn't core erlang apps like :kernel, :compiler and :stdlib be included as well? Also I'm not sure if :iex is rely needed.

Shouldn't core erlang apps like :kernel, :compiler and :stdlib be included as well? Also I'm not sure if :iex is rely needed.

It seems to me that the core erlang stuff is already included by dialyzer itself, but maybe not? :iex does have an API though (https://hexdocs.pm/iex) and can be called by code that is analyzed by the language server.

I'm not sure about that given the recent elixir PR https://github.com/elixir-lang/elixir/pull/9975/files
Regarding :iex and other optional apps, it probably won't hurt but IMO if an app uses other app's api, it should list it in the dependences. In fact elixir 1.11 will emit a warning in that case.

Removing :iex is a good point. Although it seems like we should we just match the updated list from that PR.


No dead keys with us(intl) keymap on Arch

I just installed from AUR (git) and I cannot type any characters that need dead keys, for example ã, which should be typed by pressing SHIFT+"~"+"a" prints ~a instead.
If you can give me some pointers where I should look I can definitely dive down a bit in the source.

Hi, yes this is something I forgot to do. I've added a patch that should handle key composition well. I've tested on a french keyboard (^+E => Ê, ...).
Please let me know if the recent master does not handle composition properly.

Just confirming it's fixed! Tested on us(intl).


Tell user what format Space ID should be in

Hey, so I've tried to generate types for storyblok components and it asked me to specify my space id . So I went to storyblok and copied #XXXXXX and put it inside [ ] like --space=[#XXXXXX]. It let me input that there, but created a file components.[#XXXXXX].json , but ofcourse this didn't work, the json was empty of components (none were there).
It took me a minute to realize that the cli tool maybe wants a different format of space id, so I've tried without # like [XXXXXX] , didn't work either.
So another approach was without those brackets like --space=XXXXXX and it finally worked. I'm not saying that I wasn't dumb for not realizing it on the first try, but your tool probably should notify user that the space id needs to be in particular format. It should even reject the wrong format.
Anywas, apart from this small issue, thanks for an awesome tool :)

Hey after all the years this plugin is online you are the first person raising this issue. Feel free to create a PR for the README.md to make clear that space ID is just a numeric number.


How to bind left+right mouse clic to do Expose on mac

Thx for your help :)

I don't think this is possible yet :(


resources2 Cross Platform Issue

I've been taking a look at porting the changes I made in #159 to the resources2 branch.
The main issue I've discovered (which is quite pervasive) relates to the get_repository method of the PackageRepositoryManager class.  As this splits on :, it trips up on any Windows path.  For example, it thinks the repository type of c:\users\markst\packages is c.
Based on the code docstrings I've workaround this by qualifying the rez configuration so that the path becomes filesystem:c:\users\markst\packages.  And for the most part this works well - although I've had to sprinkle it quite liberally through the test cases that defined their own packages path.
The main stumbling block is the build process code.  Here we are passing paths around which are detached from any repository plugin (and, depending on the configuration any repository identifier such as filesystem:).  Some methods (for example _build_variant_base on LocalBuildProcess and pre_release on BuildProcessHelper) need both representations.
Either I have to assume they are filesystem: based and so hardcode this prefix onto internal calls to iter_packages etc but so far this is resulting in a lot of changes.  This results in lots of code like:
release_path = "filesystem:" + self.package.config.release_packages_path

Or, configure rez such that filesystem: is always included (in rezconfig) and then use the following to get the actual file path in these methods:
release_path = self.package.config.release_packages_path # "filesystem:..."
repo = package_repository_manager.get_repository(release_path)
if not os.path.exists(repo.location):
    raise ReleaseError("Release path does not exist: %r" % release_path)

The former feels wrong so I am leaning towards the latter.  Is that the right thing to do?  It means doing it in a couple of places though which feels a bit untidy however.
I think it's easy to replicate this on linux too - if you update your configuration to include filesystem: in rezconfig and then try and build/release you should hit the same issues (although I haven't actually tried that).

Hey Mark,

Shouldn't packages_path be splitting on os.pathsep, thus ';' on Windows? Is that not the case?

I hadn't put a lot of thought into this because I'd considered that adding a new package repo type would be a fair way off - but the Windows port has unexpectedly bought this to the fore. My vote is to simply avoid the problem completely by choosing a different repo/path delimiter - I think '@' is the best candidate.

Thus:
filesystem@/srv/packages
What do you think?
A

Yes.  C:\path\a;C:\path\b is correctly split to ['C:\path\a', 'C:\path\b'].  It's when the repository manager than tokenises 'C:\path\a' to work out the repository type that things break.

Yes.  I did consider that.  And it is definitely the easiest solution.  I'll go with @ and update my changes/code appropriately.

I was thinking about this wrt a database repository - presumably this would be something like database:mongodb://username:password@host:port.  This is fine for the metadata repository, but not the code that is installed.  At the moment we lump the two together and assume the metadata repository is the same as the code (install?) repository.  For a database backend though we have to separate those concerns a little.

Yeah I'd realised that also. You may have noticed in resources2 that 'base' has become a package attribute - that's why. I anticipated that a database backend would need to explicitly specify 'base', since it can't be implied in that case.
Probably enough hasn't been done yet for this to actually work when adding a database backend. I figured that would become evident when I actually try to do that. Which might actually be happening soon... more news on that later.

We should start thinking about what the various repository uris might look like. It's actually going to be a pain when storing these in REZ_PACKAGES_PATH, since we want to avoid pathsep (and yet host:port is a common pattern as shown in your last comment).
When specifying release path, we're going to have to list both repo uri, and physical path, since as you mentioned a database uri doesn't tell rez where to actually install the package payload to.
So for eg, here's an example mongo uri for releasing, which avoids pathsep, and specifies install path (not that I like it):
mongodb@uname=uname,pwd=pwd,host=host,port=port,path=/svr/packages
Actually, it's not so bad?
A

Further to this. I think the release path doesn't have to be part of the package repo uri - to do a release, we need an install path (currently REZ_RELEASE_PATH) and optionally a pkg repo URI (currently implied as 'filesystem' repo that matches release path). So all we need is another setting - REZ_RELEASE_PACKAGE_REPOSITORY. If set, the package metadata goes there (but does it also go to the filesystem repo?).
REZ_PACKAGES_PATH stays as-is - a list of package repos, where a filepath indicates a 'filesystem' type repo matching that path.

Closing as we've switched to '@' delimiter.


Implement KEMTLS based on Delegated Credentials

This PR implements KEMTLS based on @claucece's DC branch (#28). There are a few minor fixes included in the DC stuff, surrounding the negotiation of DC supported algorithms.
This branch is targeted at the cf because that makes this PR reviewable: otherwise all of circl is included on top of my changes to the DC implementation and crypto/tls in general.
The following is currently implemented

[x] KEMTLS
[x] crypto/kem ergonomic KEM api

This package implements:

Kem25519: a KEM-variant of X25519. Useful for testing, but should be deleted before merge.
SIKEp434 provided via circl
Kyber512 provided via circl

[ ] KEMTLS client authentication

New TLS options
New supported signature algorithms (for DC):

[x] KEMTLSwithSIKEp434
[x] KEMTLSwithKyber512

New supported keyshare types (these can be negotiated independently in TLS 1.3):

[x] SIKEp434
[x] Kyber512

Testing

[ ] Unit tests

I've currently tested it by hard-coding the type of DC that the DC tests use. Unfortunately, those tests still need to be refactored a bit before it's easy to add more types of supported DC — but I'm sure that was on @claucece's list :smiley:

Stuff to do still:

Expand the number of KEMs based on newer versions of Circl (~Kyber, hopefully, soon~)

People who may be interested: @claucece, @bwesterb, @chris-wood

Hi, @thomwiggers ! This is great! I have some time this week.. so I'll review and also update the DC branch. I was going to add DC support for client auth if it is useful for you as well. Let me know ;)

That would be great for KEMTLS client auth as well

@thomwiggers I'm starting a new branch with this changes and refactors, as this will be too difficult to merge.

Yeah, I'd wondered if that would be necessary.

Closing in favour of #44


Undo/Redo history messed up with dnd and file copy

Testing #111015
Prerequisite: have a folder structure like below
- github
  - a.txt
- sample
  - b.txt

Now follow below steps:

Drag b.txt to gitHub folder
cmd+z moves b.txt back to sample folder
cmd+c on b.txt, cmd+v will create a file sample/b copy.txt
cmd+z will remove file sample/b copy.txt
now press cmd+shift+z

Expected behavior: sample/b copy.txt comes back
Actual behavior: sample/b.txt moves into gitHub folder

Yes, I can reproduce this.
I believe the issue is that the redo operation is a move which overwrites the original file name b.txt.
No plans to fix this in endgame.


Conda install?

First of all.... this package is amazing! Well done. I've been trying to figure out this issue for awhile and this is a great solution. I've got a project which is mostly conda so a conda package for jupyterlab scenes would be very helpful. Any chance of this?

Thanks. Good to hear you like it. I haven't thought about conda yet, to be honest. Let me check how this works.


Can you integrate SEEM algorithm into CVAT?

SEEM has a better way of interacting than SAM。It would be great if CVAT could inherit SEEM。

What is SEEM? Quick googling didn't show anything.

Quick

SEEM: Segment Everything Everywhere All At Once
github: https://github.com/UX-Decoder/Segment-Everything-Everywhere-All-At-Once
hugging face: https://huggingface.co/spaces/xdecoder/SEEM


Import HealthCheckOptions?

This comes from the Microsoft.Extensions.Diagnostics.HealthChecks package.
Related reading: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/monitor-app-health

Remember to also install the AspNetCore.HealthChecks.SqlServer package from AspNetCore.Diagnostics.HealthChecks.
var hcBuilder = services.AddHealthChecks();

hcBuilder
    .AddSqlServer(
        configuration["ConnectionString"],
        name: "CatalogDB-check",
        tags: new string[] { "catalogdb" });

The diagnostics package actually contains health checks for several services. We need to install a few more packages:

AspNetCore.HealthChecks.AzureStorage (AddAzureBlobStorage())
AspNetCore.HealthChecks.AzureServiceBus (AddAzureServiceBusTopic())
AspNetCore.HealthChecks.Rabbitmq (AddRabbitMQ())


Add asset to your texture

Is it possible to add your files to the asset bundle?

No. Right now ripper supports only extracting. You can try UABE for that purpose.


[wasmparser] Reduce the size of TypeId for better validation performance

Hey! First of all, thank you for maintaining wasm-tools :D
While upgrading our wasmer fork from wasmparser 0.78 to 0.94, I noticed a significant performance degradation on one of our benchmarks. Unfortunately, this benchmark is currently related to a security vulnerability, so I cannot share it yet.
My understanding is that it is related to TypeId becoming significantly bigger in 0.94 compared to 0.78, as all the metadata to identify different types that are basically isomorphic otherwise was added. TBH I don't really understand why this metadata is required, but I guess it's required indeed as otherwise #775 probably wouldn't have made it in.
So I'm submitting this PR, that at least reduces the amount of extra information: TypeId was just an 8-bytes integer in 0.78, and became a huge 40-bytes struct in 0.94, of which 8 are the previous TypeId, 8 are for type size monitoring, and 24 are for the type metadata used just for disambiguating types. With this PR, the last 24 bytes get reduced to 8 bytes, by bitpacking everything together and assuming there won't be more than 2⁶² types in a module, which sounds like a reasonable assumption to me. So TypeId becomes a 24-bytes struct.
(It'd be even better if we could assume a max type size of 2³² and a max number of types of 2³⁰, as this would allow us to reduce further the size of TypeId to 16-bytes, but I'm not sure this would be reasonable limits for wasmparser? Also, my benches don't show significant performance changes reducing the size further, though I'm not really sure why)
I have tried running our internal bench through wasmparser's benchmarks, and I can say that the before/after difference with this is a ~12% performance gain in validation, thanks to reduced memory pressure most certainly.
WDYT? :)

Thanks! Have you been able to see the difference from the benchmarks in this repository? If not would you be up for adding a benchmark?
I think this could also be made smaller as well. The type_size and index values don't need to be larger than 32 bits so could be hardcoded as u32. Additionally type_hash could be shrunk to 4-bytes as well since the type index won't ever go so big as to need the full 32-bits. That would bring this down to 12 bytes which might improve things further?

I sent https://github.com/Ekleog/wasm-tools/pull/1 which further shrinks the type to 8 bytes, but locally doesn't show a huge impact in the benchmarks for this repository. Would you be up for testing that to see whether it further improves the benchmark you're looking at? (which if possible would still be great to add here)

Thank you for your answer as well as further size reduction PR!
However, it turns out that the further reduction is actually worsening performance, maybe because often-used values now need to be unpacked?
What I’m seeing on the repro I can’t share is:

main -> first commit of this PR: 10% improvement (the repro had taken a ~15% perf hit when upgrading wasmparser, so it’s likely ~back to previous performance, though I’m not measuring in the same way)
main -> tip of your further size reduction: 5% improvement
main -> second commit of this PR, that reduces to 16 bytes by reducing type_size and type_hash while keeping index: usize: still only 10% improvement

These results are roughly consistent with the bench I just pushed on top of this branch.
WDYT? I’m thinking we could either keep this as is or do the further reduction to 16 bytes, whichever you think best, but I’d argue against reducing to 8 bytes given the numbers above. (So I’m also pushing both commits right now, but feel free to let me know if you think removing the second one would be better)

Awesome, thank you! :)


CUDA 11

Hi! Is it possible to run your code on machine with CUDA 11? I get this error:
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal: Could not satisfy explicit device specification '' because the node {{colocation_node hourglass_stack_fused_depth_prediction/conv1/weights/Initializer/truncated_normal/TruncatedNormal}} was colocated with a group of nodes that required incompatible device '/device:GPU:0'. All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_CPU:0].
and I suspect that it's connected to difference in CUDA version with the version mentioned in README.

Hi. Thanks for your message. I have not tried CUDA 11 but it is possible to get error with another version of cuda for some specific functions.


Mondo master: ServerTests StaticFiles and Session

Can you also update the Directory.Build.props files to use the right url? This impacts sourcelink and symbols generation, so we should fix this when merging to new repos. We can go back and fix this later in release/2.1 and 2.2 which isn't impacted by this yet.
-    <RepositoryUrl>https://github.com/aspnet/AADIntegration</RepositoryUrl>
+    <RepositoryUrl>https://github.com/aspnet/AspNetCore</RepositoryUrl>

Are you running the tests? We're expecting issues with ServerTests similar to https://github.com/aspnet/AspNetCore-Internal/issues/1320#issuecomment-440336006

@natemcmaster: updated.
@Tratcher: We're letting the PR checks check for breaks for us, but if we know this is going to happen is someone working on a fix already?

They're still designing a fix.

Also, let's resolved this first: https://github.com/aspnet/AspNetCore-Internal/issues/1411

:up::date:


fix: add support to .ogg files with audio/opus mime type which is supported by AWS Transcribe

Overview
Got this error while trying the tool with an *.ogg audio file :

⠐ Using bucket region us-west-2
⠈ Submitting transcription jobError:
Unsupported media format: audio/opus

a mime type audio/opus is probably just an opus file without a wrapper ogg container
ref: https://wiki.xiph.org/MIME_Types_and_File_Extensions
AWS Transcribe supports ogg files, an audio file with audio/opus mime type is successfully transcribed
ref: https://docs.aws.amazon.com/transcribe/latest/dg/how-input.html#how-input-audio
This change adds the mapping audio/opus to MediaFormat::Ogg.
Testing:
Tested successfully with an *.ogg file with audio/opus mime type

Thanks @sergiolibe for your contribution. Tested with https://commons.wikimedia.org/wiki/File:Example.ogg, looks good to me. Merging.


Add connection status check example and documentation.

Adds an example script showing client.isReady and client.isOpen, adds reference to isReady in the top level README.  Closes #2337

Codecov Report
Base: 95.85% // Head: 95.85% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (e4e242b) compared to base (9398e5d).
Patch coverage: 82.14% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##           master    #2340    +/-   ##
========================================
  Coverage   95.85%   95.85%
========================================
  Files         433      449    +16
  Lines        4002     4224   +222
  Branches      451      471    +20
========================================
+ Hits         3836     4049   +213
- Misses        102      107     +5
- Partials       64       68     +4

Impacted Files
Coverage Δ

packages/client/lib/client/socket.ts
77.77% <80.76%> (-2.23%)
:arrow_down:

packages/client/lib/client/index.ts
91.12% <100.00%> (-0.29%)
:arrow_down:

packages/client/lib/commander.ts
95.45% <100.00%> (ø)

packages/client/lib/errors.ts
100.00% <0.00%> (ø)

packages/graph/lib/commands/QUERY.ts
100.00% <0.00%> (ø)

packages/graph/lib/commands/QUERY_RO.ts

packages/graph/lib/graph.ts
96.29% <0.00%> (ø)

packages/bloom/lib/commands/t-digest/QUANTILE.ts
100.00% <0.00%> (ø)

... and 16 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

#2339


child is wrapped in _struct

Though the issue was closed, I'm still having the same issue as https://github.com/geckosio/typed-array-buffer-schema/issues/9

Can you share your model with some example data?

something like this
const hero = BufferSchema.schema('heroes', {
  id,
  x: int16,
  y: int16,
  vx: int16,
  vy: int16,
  l: boolean,
  n: string8,
  a: string8,
  b: boolean,
  d: boolean,
  p: uint8,
});

const gameDataSchema = BufferSchema.schema('main', {
  heroes: [hero]
});

const snapshotSchema = BufferSchema.schema('snapshot', {
  heroes: [hero]
});

result looks like
{
  id: '',
  time: 0,
  state: {
    _struct: {
       heroes: []
    }
  }
}

The boolean type does not exist. It's bool8 or bool16.
bool8 is 1 byte in size, so it is better to combine multiple boolean in one bool8.
Try:
const hero = BufferSchema.schema('heroes', {
  x: int16,
  y: int16,
  vx: int16,
  vy: int16,
  lbd: bool8,
  n: string8,
  a: string8,
  p: uint8
})

const gameDataSchema = BufferSchema.schema('main', {
  heroes: [hero]
})

const gameState = {
  time: new Date().getTime(),
  tick: 32580,
  heroes: [{ x: 1, y: 2, vx: 3, vy: 4, lbd: [true, false, true], n: 'string8', a: 'string8', p: 1 }]
}

const mainModel = new Model(gameDataSchema)
const buffer = mainModel.toBuffer(gameState)
const data = mainModel.fromBuffer(buffer)

console.log(JSON.stringify(data, null, 2))

Result:
{
  "heroes": [
    {
      "a": "string8     ",
      "lbd": [
        true,
        false,
        true
      ],
      "n": "string8     ",
      "p": 5,
      "vx": 3,
      "vy": 4,
      "x": 1,
      "y": 2
    }
  ]
}

sorry the boolean was a custom type I declared
const boolean = { type: uint8, digits: 1 };
that aside, I am using it with snapshot-interpolation so please try to wrap it in state to reproduce the issue

Where in your code do you wrap it in state?
I don't think you can just wrap your model in a custom object. You should probably send the data and modify it after receiving.

The snapshot-interpolation library wraps it in state, and then I convert it to buffer before sending.

But, I guess, then you need to add a state object in your schema just like in this example:
https://github.com/geckosio/snapshot-interpolation#compression

hmm that's what I did. I apologize I provided wrong example on the first post. However what I did now to solve it, is to just convert the state and manually insert it into the snapshot before sending.


Using custom output files doesn't work

When using a custom output file I always get the error 1168.
I use Apache on Mac. GoAccess is called as admin. All rights on the target directory are granted. I tried with and without existing report.html file in the destination directory.
GoAccess is called by "sudo goaccess /var/log/apache2/access_log -a > /Library/WebServer/Documents/stats/report.html --real-time-html" on the local server.
This is my config:
goaccess.conf.txt
The console output works well.

Strange, are you running this as root? Also have you tried writing to a file using the same user you are running goaccess? e.g.,
$ touch /Library/WebServer/Documents/stats/file.txt

Also what's the output of ls -lath /Library/WebServer/Documents/stats/?

Closing this. Feel free to reopen it if needed.


HTTP code is 500 which indicates error: server error - {"message":"Get https://registry-1.docker.io/v2/library/redis/manifests/latest: read tcp <IP_ADDRESS>:43544-\u003e<IP_ADDRESS>:443: read: connection reset by peer"}

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing


Clarify usage with namespaced controllers

Hi,
i am trying to use active_link_to for the index and show action of a namespaced controller.
/admin/documents => true
/admin/documents/1 => true
/admin/documents/new => false
My code:
<%= active_link_to "Dokumente zur Freigabe (5)", admin_documents_path(published: false), class_active: "is-active", active: [['admin/documents'], [:index, :show]] %>

Any ideas why this is not working? Thank you! :)

For everyone that is looking for this: Thats what worked for me:
, active: [['admin/documents'], [:index, :show]]

For everyone that is looking for this: Thats what worked for me:
, active: [['admin/documents'], [:index, :show]]


No cert generated

Hi guys,
I did a fresh install of acme-dns.
I am unable to connect using https. If I change the config to 80/none, the curl request is good.
With 443/letsencrypt(staging) I always receive error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error.
Shouldn't the required cert being generated automatically? Or what do I have to do?
I cannot find anything concerning this, what helps.
Regards,
Marcel

Hi, I have the same problem with a33c09a, the cert is never be created.
Below is my config, configured ports are open and and reachable.
Every time I restart the service, I get this message in the log, but it never ever tries to get a certificate. At least I can't see anything bout it in the log.
Apr 01 02:38:44 flux acme-dns[232945]: time="2022-04-01T02:38:44+02:00" level=info msg="2022/04/01 02:38:44 [INFO][FileStorage:api-certs] Lock for 'issue_cert_flux.rc5.de' is stale (created: 2022-04-01 00:10:01.08155592 +0200 CEST, last update: 2022-04-01 02:38:34.943066241 +0200 CEST); removing then retrying: api-certs/locks/issue_cert_flux.rc5.de.lock"
Config:
[general]
listen = ":53"
protocol = "udp"
domain = "flux.rc5.de"
nsname = "flux.rc5.de"
nsadmin = "some.email.de"
records = [
    "flux.rc5.de. A <IP_ADDRESS>",
    "home.astrastudio.de. A <IP_ADDRESS>",
    "home.astrastudio.de. NS flux.rc5.de.",
]
debug = true

[database]
engine = "sqlite3"
connection = "/var/lib/acme-dns/acme-dns.db"

[api]
ip = "<IP_ADDRESS>"
disable_registration = false
port = "9988"
tls = "letsencrypt"
acme_cache_dir = "api-certs"
notification_email =<EMAIL_ADDRESS>corsorigins = [
    "*"
]
use_header = false
header_name = "X-Forwarded-For"

[logconfig]
loglevel = "debug"
logtype = "stdout"
logformat = "text"

What can I do to hunt this bug? Where do I get more info/more debug output?

I had the same problems.
My DNS/NS entries in my main zone were wrong, and additionally I ran into a rate limit on the letsencrypt server.

While configuring the tools, it is highly recommended to use the staging environment.

While configuring the tools, it is highly recommended to use the staging environment.

I did this and received a valid staging cert, but one of my DNS servers was out of sync and had other/old records. Looks like I got luck with the staging environment, just asked the correct nameserver and the production server did ask the outdated one. ;-)

While configuring the tools, it is highly recommended to use the staging environment.

I did this and received a valid staging cert, but one of my DNS servers was out of sync and had other/old records. Looks like I got luck with the staging environment, just asked the correct nameserver and the production server did ask the outdated one. ;-)

How fast did you get banned from Let's Encrypt?
I remember my first attempts with cert-manager, whithout knowing staging environment, and I was banned in... few seconds :D

Thanks, @saschaludwig ... I got this wrong... I like Win & Mac ;) I will try with journalctl...

Thank you @saschaludwig ... it was a DNS config issue, I overlook many times...


Use the random reader passed as argument to GenerateED25519Key.

Rather than the global source.
Signed-off-by: David Calavera<EMAIL_ADDRESS>

Makes sense, although this won't fix any entropy issues, just FYI :)

LGTM


[Feature Request] Rework Block Quote styling

It's very cool that the block quote styling in journals matches the Shadowdark design, but it makes them hard to read. I specificially dislike that the white text bleeds into the white edge on the left and right sides.

Can confirm this can get a little out of hand.

As a workaround you can always just add a few more line breaks so the text isn't as long...


Add test for dynamic filter materialization on coordinator

Fixes: https://github.com/prestosql/presto/issues/4032

Merged, thanks!


⚠ Samsung has degraded performance

In a020a9a, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2208 ms

Resolved: Samsung performance has improved in 2094f71.


Version 116 causes Overwatch to crash

2023-01-28 16.57.06.log
2023-01-28 15.48.04.log
2023-01-28 16.55.28.log
Expected Behaviour

The game to work
Actual Behaviour

The game crashes 15~30 seconds into a match

Reproduction steps

Upgrade to v116
Launch overwatch
Join a match
Game crashes 15~30 seconds in
Frequency

100%. You cannot play the game while running aurora v116.
Aurora Version:

v116
Previously an Issue?

No, version 115 does not crash.
Downgrading from v116 to v115 instantly resolves the crashing.

I assumed crash was because of broken audio detection from previous version. Can you try last version?
https://github.com/Aurora-RGB/Aurora/releases/tag/v117

Sorry for the delay. The crash is still occurring on v118

Narrowed it down to being caused by having G.SKILL Trident Z Lighting Control (lighting control software for my RAM) open at the same time as Aurora. I can have either Aurora or the gskill lighting open and no ctd, but both of them open results in a ctd.
https://www.gskill.com/download/1502180912/1551690847/Trident-Z-Family-RGB,-Neo,-Royal,-Royal-Elite,-Z5-RGB
It occurs in all gamemodes for me, even practice / firing range.

only possible relevant change with v116 looks like steelseries (rgb.net) controller. Can you try with that disabled?

Got everything but Logitech and both Corsair controllers disabled, no joy.

I installed G.SKILL Trident Z Lighting Control and it didn't crash for me. It is probably Chroma SDK related. I suggest installing latest version


wildcard support?

Is it possible to create wildcard certificate for domain?

Has anyone figured this out? I'm trying to configure my free runcloud instance to use SSL. Since certbot doesn't work, I may have to bail on runcloud if this script can't make https://www.(domain).com certificates as well as https://(domain).com.

It is supported according to them.
https://runcloud.io/docs/guide/account/3rd-party-api-key
Overview
This is where you can register a third-party API Key. The API Key will be used to authorize the Let's Encrypt challenge for dns-01 authorization.
Currently we only support API Keys from Cloudflare, Linode, Vultr and Digital Ocean.

It is supported according to them.
https://runcloud.io/docs/guide/account/3rd-party-api-key
Overview
This is where you can register a third-party API Key. The API Key will be used to authorize the Let's Encrypt challenge for dns-01 authorization.
Currently we only support API Keys from Cloudflare, Linode, Vultr and Digital Ocean.


Set scm.PR.Sha to scm.PR.Head.Sha when loading from disk.

Changes
This guarantee is made when retrieving a PR from a provider, but we do not persist
that guarantee when roundtripping from disk.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

/lgtm
/cc @afrittoli This might be another 0.9.x cherrypick candidate :sob:

So, this is a regression too, right?


Make menu item "attach rule" behave similar as switching RPK in node editor

If the menu item "Attach rule..." is applied on an already generated PRT model, Serlio should switch the RPK, not apply the rule on the generated model (which likely results in huge resource consumption and brings maya to standstill).

(internal issue CE-6911)

Fixed in v2.0


fix: conflicting rules when using loops

:tada: This PR is included in version 1.17.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG] Radio cannot RX after 2 minutes idle with battery saver and NOAA enabled

Describe the bug
When NOAA is enabled in firmware, and battery saver is turned on the radio will stop receiving after about 2 minutes.
To Reproduce

Set ENABLE_NOAA := 1 in makefile, build, flash to radio.
Enable battery saver in the radio settings menu (default, 80%).
Wait about 2 minutes (I use the backlight timeout of 2 minutes as a time, but it is NOT tied to backlight timeout as turning it off at 5 seconds it still takes about 2 minutes to stop receiving)
Transmit from another radio tuned to the same frequency
No RX
Press any key on the receiving radio, and it will RX again for 2 minutes.

Expected behavior
Radio should receive :)
Details:

Firmware version: Latest main
Bandwidth: 12.5k
NOAA-S: on or off
BatSav: 80%

ENABLE_NOAA is unsupported and likely should be removed.
Would you be willing to post a PR removing that flag?

I could do that. I dont't need the alerts and can just put the channels in memory anyway.

See #147

Hey,
I just compiled NOAA back into my firmware.
Is there a way to set the 1050 Hz tone when saving the NOAA channel to the radio? I don't want to constantly listen to the weather, but I need the emergency alerts to activate. Any guidance on configuring this would be greatly appreciated!
Thanks!