Error Duplicate tag "grug-far.setup()" when updating via lazy.nvim

...hare/nvim/lazy/lazy.nvim/lua/lazy/manage/task/plugin.lua:84: Vim:E154: Duplicate tag "grug-far.setup()" in file /Users/chrisgrieser/.local/share/nvim/lazy/grug-far.nvim/doc//grug-far.txt

I tried uninstalling and reinstalling the plugin, the error seems to persist. This is the only plugin this error occurs with. I have readme.enabled = false in my lazy config, so it's not related to lazy's doc creation.

Ah that looks like it might be the duplicate help tag here
https://github.com/MagicDuck/grug-far.nvim/blob/c7c4285c28c280da5ceb0cb64eb6731f7a30cb18/doc/grug-far.txt#L46
Didn’t know help docs could have such an effect, haha

fixed in https://github.com/MagicDuck/grug-far.nvim/pull/28

lemme know if you still see any issues and I'll reopen

Works fine now - thanks!


Improved Tab Accessibility and Refactored Markup

Fix for #1098
=======
Tabs will now read out two separate times using a screen reader (NVDA):

Tab itself => 'Welcome Tab Button'
Tab close icon => 'Close Welcome Tab Button'

Also significantly refactored the markup for <MDI/> <MultiTabs/> & <TabbedDocument/>
Removed /ui/shell/multiTabs and moved all contents to /ui/shell/mdi/...

Pull Request Test Coverage Report for Build 1464

51 of 58 (87.93%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 56.772%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/app/client/src/ui/shell/mdi/tabBar/tabBarContainer.ts
7
9
77.78%

packages/app/client/src/ui/shell/mdi/tabBar/tabBar.tsx
28
33
84.85%

Totals

Change from base Build 1461:
0.4%

Covered Lines:
4655

Relevant Lines:
7403

💛  - Coveralls


(MODULES-8352) Don't use empty encoding string on initdb

pgsql 11 no longer allows initdb with an empty encoding string. Only
include the string when $encoding is set.

Thanks @binford2k for supplying a fix. Looking forward to seeing more of the Rangefinder too!


(DO NOT MERGE) - Feature/no events

Changes Unknown when pulling 503e47af297eb920f7be1df5061f26b2e31d7d99 on feature/no-events into ** on develop**.

Changes Unknown when pulling 2d3b1ab66fcf871b4e0e50373ec2f15ac536a0dd on feature/no-events into ** on develop**.

Changes Unknown when pulling 42ddabb174d958b72559650e797f2d3737ef0eda on feature/no-events into ** on develop**.

Ok to merge. PR from develop to master is closed


Add periodic backup mechanism

Uses systemd timers to perform backup at noon, daily. Restic secrets are encrypted using agenix.
How we make sure we are notified if restic fails is to scan journald log every time a new zsh shell is opened.
Reference: https://www.backblaze.com/docs/cloud-storage-integrate-restic-with-backblaze-b2

Note to self:
To check past snapshots
sudo su
source /etc/restic-env
restic snapshots


test partial datetime

replaces #2337 which is failing to set up the test environment properly

@marqh I'm sorry, maybe I'm being daft, but how is this different from https://github.com/SciTools/iris/pull/2337?

I'm sorry, maybe I'm being daft, but how is this different from #2337?

it's remarkably similar, it is not you at all
however, #2337 doesn't seem to be able to run its tests, it was like the merge it had for the test was so far behind, it wouldn't run, so I pinched the test and made a new PR so I could iterate on the issue

I see netcdf4 1.2.7 and the new test is passing. I guess we can unpin netcdf4-python in the conda package then. Thanks @marqh!
@dkillick since you raised this initial can you give us the green to remove the pin?

since you raised this initial can you give us the green to remove the pin?

@ocefpaf do you happen to know what it is that has been changed that means Iris now supports the netcdf4 v1.2.7?
Happy to merge this though :smile:

@ocefpaf do you happen to know what it is that has been changed that means Iris now supports the netcdf4 v1.2.7?

I am guessing that these tests changes: https://github.com/SciTools/iris/pull/2440/files#diff-5cb5e61c3251e6b6db0c1383719cd552

@ocefpaf I think that the pin is on the v1.12.0 build
I am hoping to expedite a 1.13 release, is it worth waiting for that, which will have the changes and this test as part of the release, and removing the pin in the updated recipe for v1.13.0?

I am hoping to expedite a 1.13 release, is it worth waiting for that, which will have the changes and this test as part of the release, and removing the pin in the updated recipe for v1.13.0?

It is worth. Not that the the tests are important to the conda-forge package (we don't run them), and in theory we could unpin b/c there is no actual iris code change regarding netcdf4 compatibility. However, there are two patches in 1.12 conda package already, and a new release would be nice so we can drop them.


[Accessibility]A11y_VSCode_ViewDebug_Keyboard: Tooltip is not visible to keyboard only users but only visible on mouse-hover.

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Additional Details:
MAS Violated : MAS 2.1.1 , MAS1.1.1
Repro Steps:

Launch VS Code.
Navigate to Activity Bar and select "View Debug"(Cntrl+Shift+D) button.
Navigate to "Start Debugging","Open file","Debug console" etc. buttons using "Tab".
Also, mouse hover on all above mentioned buttons.

Actual:
Tooltip information is not available for keyboard only users for "Start Debugging","Open file","Debug console" etc buttons which is available on mouse hover.
Expected:
Tooltip information should be made available for keyboard only users which is available using mouse.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
The keyboard only users will not be able to gain information regarding few controls present on screen which is only available using mouse hover.
MAS Reference:
MAS 2.1.1 - https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
MAS 1.1.1 - https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={d2d2051f-bdc8-4af7-8e18-38aae867e216}
Attachment For Reference:
A11y_VSCode_ViewDebug_Keyboard_TooltipIssue.pptx
Does this issue occur when all extensions are disabled?: Yes

Dup of https://github.com/Microsoft/vscode/issues/52016


WIP: Initial support for async/await

This pull request will add initial support for async/await:

User can write async action handlers.
Receive will not block.

WIP

Related to #63


display certificate start and end date on template

Pre-Flight checklist

[x] Screenshots and design review for any changes that affect layout or styling

[x] Desktop screenshots
[ ] Mobile width screenshots

[ ] Migrations

[ ] Migration is backwards-compatible with current production code

[ ] Testing

[ ] Code is tested
[x] Changes have been manually tested

[ ] Settings

[ ] New settings are documented and present in app.json
[ ] New settings have reasonable development defaults, if applicable
[ ] Opened issue for DevOps regarding necessary configuration changes to deployed environments

What are the relevant tickets?
#967
How should this be manually tested?

Open certificate page
Validate start and end date on certificate template page
If the course run is self-paced the end date should be the created date of certificate

Screenshots
In below screenshot the end date is certificate created date because the course run is self-paced (I've manually set is_self_paced flag as True)

In below screenshot the end date is course run end date because the course run is not self-paced (I've manually set is_self_paced flag as False)

Codecov Report

Merging #973 (fd063fe) into main (ce8e512) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #973      +/-   ##
==========================================
- Coverage   84.46%   84.42%   -0.04%
==========================================
  Files         141      141
  Lines        6727     6729       +2
  Branches     1133     1134       +1
==========================================
- Hits         5682     5681       -1
  Misses        857      857
- Partials      188      191       +3

Impacted Files
Coverage Δ

courses/models.py
89.90% <0.00%> (-0.58%)
:arrow_down:

ecommerce/views/v0/__init__.py
89.61% <0.00%> (-0.44%)
:arrow_down:

ecommerce/models.py
88.69% <0.00%> (ø)

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

@pdpinch please review dates with and without CEUs mobile and desktop

Thank you for the reminder @aliraza-abbasi -- it looks good to me!


please set   it   to  your   cuda   install  root?

In my  ubuntu , I  use  conda  to  create  the  virtual environment，but  the  shell  'conda install  pytorch  torchvision  cudatoolkit=9.0 '   has  been   assembled  cuda  and  cudnn   as  a    python  lib,  it  likes  stored   in  'conda/env/open-mmlab/lib' ,  that  I  don't  need  to    install   cuda  and  cudnn  twice, so  there  is  no   'CUDA_HOME'   in   ./bashrc    any  more   .
The  question  is , when  I  run  compile.sh  ,it  will   tell  me
CUDA_HOME  environment is  not  set, Please  set  it   to your  CUDA  install  root
I  know  the 'compile.sh' program  can't   find  the  CUDA  environment  in  the conda  virtual  environment,but  I  don't know  how  to  solve  it.
Is  there  anyone  who meet  the  same  question  with me ?  Hopes  your  reply.

Yes , I met the same issue and I still don't know how to go around it.
Did you find any solution ?


fixed the emoji from being hardcoded

also reordered the params to reflect config's importance

Won't fix.  The latest code drops the emoji all together in favor of just putting an icon on the bot itself.


Add benchmarks for Alloy

Request
@mattdurham will add details here, placeholder for now
Use case
@mattdurham will add details here, placeholder for now

Hey! Just seen this during iteration planning. Are we still working on this or planning to resume later?


feat: add docs buttons to CLI and Generator landing pages

Description

Added docs button to CLI page #1684 @derberg
Added docs button to Generator page #1684 @derberg
...

Related issue(s)
fixes https://github.com/asyncapi/website/issues/1684

/rtm

@allcontributors please add @rukundob451 for code


Interaction::Hovered never happens on mobile, even when it would make sense.

Bevy version
0.13.1
System information
iPhone 11 and 15
Issue
It makes sense that you never "hover" a UI node without pressing it, on mobile, since the position of your finger is tracked only when it touched the screen, but there is one scenario where it would make sense for a UI node entity to have Interaction::Hovered.
When you press outside a node, and then slide over it while keeping the mouse pressed, on PC, this node would have a Interaction::Hovered. This behavior could be questioned but it makes sense if you compare to the web.
This behavior doesn't happen on mobile though, the node never has the Interaction::Hovered component. I think it should.
My guess is it happens because the hover system only checks for cursor position, and there is no cursor position on mobile.
You can go around it by checking where the finger is and then checks if the node is under it but this requires knowing the node's boundaries, which I am not sure are publicly accessible.
Tangent
If on PC you press on a node and then slide out of it I think it is still marked as Pressed, which means if you want to check that the player started pressing on a node and released still on it before doing something, you need to check that it goes from Pressed to Hovered, which is a bit annoying and doesn't work on mobile either, you also have to know node boundaries for that, and that may also differ from what web browser do?
Maybe there should be a way to check for this kind of interaction? Was a press started on this node? Just released on this node?

When you press outside a node, and then slide over it while keeping the mouse pressed, on PC, this node would have a Interaction::Hovered. This behavior could be questioned but it makes sense if you compare to the web.

Could you confirm that web browser behaves that way?
I just checked a few apps on an iPad that supports hovering (with the Apple Pencil), none react that way. iOS doesn't do that either. I'm not sure this is expected behaviour

With the following code here https://developer.mozilla.org/en-US/play :

.test {
  background-color: lightblue;
}

.test::before {
  content: "None";
}

.test:hover::before {
  content: "Hover";
}

.test:active::before {
  content: "Active";
}

When clicked outside then slide in it displays Hover, when clicked inside then slide out it displays Active. If you remove the Hover CSS rule it would display None and Active respectively.


NO-JIRA: Switch .NET Core targets from 2.2 (no longer supported) back to 2.1 (LTS)

This pull request is not necessarily proposed to merge, but is more for discussion - and also for a test to see what Travis CI does with it.
As .NET Core 2.2 has reached end of life, I tried switching the references back to 2.1 which is still supported at this time (albeit only until August). This affects the test suite, the samples, and the CI config. The main output package, targeting .NET Standard 2.0, is unchanged. As far as I can tell, it didn't cause any problems building and testing locally.
It is noted that this PR is mutually exclusive with #49 which contemplates upgrading to .NET Core 3.0; but that 3.0 is also EOL. I would be happy with bumping that to 3.1, and seeing that merged in lieu of this PR - I don't usually target 2.1 anymore myself. However, there was discussion in that PR about preserving compatibility. So, while the present PR it does not take advantage of any new functionality in later versions of .NET, it does continue to test for backward compatibility, at least.

LGTM too @lukabsent - can you also patch this onto the 2.0 branch?

@brudo thanks!


Debian CloudFoundry key not accessible by typical wget / curl on Ubuntu

Please fill out the issue checklist below and provide ALL the requested information.

[x] I reviewed open and closed github issues that may be related to my problem.
[x] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[ ] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[x] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
I am attempting to use the CF CLI on Ubuntu (in a GitHub action via ubuntu-latest runner, and reproduced locally on Ubuntu 22.04 as well)
What happened

I attempted to use the installation instructions from the CF-CLI but could not get it to work.
I kept seeing that no PGP information was found.
When I broke down the command, I decided to try the wget command first. It was empty. I then tried with curl, and I saw an access denied error message. That's odd...because I had just gone to that URL in my browser a moment ago.

URL in question: https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key

I was able to fix by supplying a user agent with curl's -A option.

Expected behavior
CF8-CLI to install correctly
Exact Steps To Reproduce
On Ubuntu 22.04
curl https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/cloudfoundrycli.gpg
echo "deb https://packages.cloudfoundry.org/debian stable main" | sudo tee /etc/apt/sources.list.d/cloudfoundry-cli.list
sudo apt-get update
sudo apt-get install cf8-cli

What does work (workaround):
curl -A "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1" https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/cloudfoundrycli.gpg
echo "deb https://packages.cloudfoundry.org/debian stable main" | sudo tee /etc/apt/sources.list.d/cloudfoundry-cli.list
sudo apt-get update
sudo apt-get install cf8-cli

It appears that some sort of security tooling or configuration is blocking access to the public key data via typical wget / curl commands, which have a legitimate use case.

Getting the same access denied
`
Access Denied

Access Denied
You don't have permission to access "http://packages.cloudfoundry.org/stable?" on this server.
Reference #18.26701102.1679991638.9dbfd60

`
This was working well until yesterday late afternoon UTC+1

I can confirm. This started failing today. Akamai is returning a 403 when retrieving the GPG key using curl or wget.

This access denied is also returned when trying to download compressed binaries with:
curl -L "https://packages.cloudfoundry.org/stable?release=linux64-binary&version=v7&source=github"

as per https://github.com/cloudfoundry/cli/blob/main/doc/installation-instructions/installation-instructions-v7.md#installers-and-compressed-binaries

It looks like the 403 error is because of the curl user agent. Doing the same request without the user agent (option -A "") works okay for me.
curl -A "" -L "https://packages.cloudfoundry.org/stable?release=linux64-binary&version=v7&source=github"

It is also possible to use a custom user agent like for a standard Chrome browser to be able to retrieve the pgp key.
curl -H "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key

Thanks for all the validation here! I was creating a build process using the CF cli for the first time yesterday. It worked in my first workflow but failed in my second and I couldn't understand what I had done wrong. Bad luck/timing it seems! 😆

Thanks for all the validation here! I was creating a build process using the CF cli for the first time yesterday. It worked in my first workflow but failed in my second and I couldn't understand what I had done wrong. Bad luck/timing it seems! 😆

Haha, yes. Using it also in a couple of pipelines for my customers and they all mentioned the issue.
I've provided a fix on a alternative location from a manually download of the cli files.
This will be used if the endpoint would return a statuscode != 200

We're looking into this issue. CC @ccjaimes

This issue should be resolved by now. The primary reason is a new CDN security rule to fight bots. We will take additional steps to improve monitoring to respond faster to such incidents.


Add toml and pygments to requirements.txt

Really a good project, but it seems that the requirements.txt lost toml.
@rdbende Can you check it out?

Maybe we should, for someone who wants to make a contribution.

That's fine, but I prefer to execute pip install -r requirements.txt and edit on the current path.

So we don't need requirements.txt now?

I honestly do it the same way as white cloud. Not my repo though :).

@rdbende Whether to delete or not, it's up to you to decide

I honestly do it the same way as white cloud. Not my repo though :).

But in a venv?


The accordion close nested problem. I set the settings attribute closeNested true, when I close the outter accordion, the inner accordion doesn't close

The accordion close nested problem. I set the settings attribute closeNested true, when I close the outter accordion, the inner accordion doesn't close.
I appreciate your help.
My html is below:

Title

        the
        Size

                        <input type="radio" name="size" value="small">
                        Small

                        <input type="radio" name="size" value="medium">
                        Medium

                        water

                                        <input type="radio" name="size" value="small">
                                        blue

Hi, please provide a test case as per our contributing guidelines; you can fork this JSFiddle.

Closing the issue until there’s a test case.

Thank you for your follow up, I have changed the code by myself.
On Thu, Mar 9, 2017 at 7:39 AM, Andrew Golubev<EMAIL_ADDRESS>wrote:

Closed #5108 https://github.com/Semantic-Org/Semantic-UI/issues/5108.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Semantic-Org/Semantic-UI/issues/5108#event-993050711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYA8Xxm8q8Kv1FkHvXrVyrBF6qBhoRhNks5rj_LpgaJpZM4MP7dI
.


[Linux] Some error boxes pop up in the lower right corner when opening Blazor Web for Server application with VsCode

Environment data
dotnet --info output:
.NET SDK:
 Version:   8.0.100-rc.1.23416.11
 Commit:    8d3d6d0774

Runtime Environment:
 OS Name:     rhel
 OS Version:  9
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/aapt/dotnet/sdk/8.0.100-rc.1.23416.11/

.NET workloads installed:
There are no installed workloads to display.

Host:
  Version:      8.0.0-rc.1.23414.4
  Architecture: x64
  Commit:       e897946596
  RID:          linux-x64

.NET SDKs installed:
  8.0.100-rc.1.23416.11 [/home/aapt/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.0-rc.1.23414.10 [/home/aapt/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.0-rc.1.23414.4 [/home/aapt/dotnet/shared/Microsoft.NETCore.App]

VS Code version: 1.81.1
C# Extension version: v2.0.376
OmniSharp log
 C# LogUsing dotnet configured on PATH
Dotnet path: /bin/dotnet
Activating C# standalone...
You must install .NET to run this application.
App: /home/aapt/.vscode/extensions/ms-dotnettools.csharp-2.0.376-linux-x64/.roslyn/Microsoft.CodeAnalysis.LanguageServer
Architecture: x64
App host version: 7.0.0-preview.7.22362.8
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=rhel.9-x64&apphost_version=7.0.0-preview.7.22362.8
[Error - 8:21:45 AM] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Info  - 8:21:45 AM] Connection to server got closed. Server will restart.
true
[Error - 8:21:45 AM] Microsoft.CodeAnalysis.LanguageServer client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
Using dotnet configured on PATH
Dotnet path: /bin/dotnet
Activating C# standalone...
You must install .NET to run this application.
App: /home/aapt/.vscode/extensions/ms-dotnettools.csharp-2.0.376-linux-x64/.roslyn/Microsoft.CodeAnalysis.LanguageServer
Architecture: x64
App host version: 7.0.0-preview.7.22362.8
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=rhel.9-x64&apphost_version=7.0.0-preview.7.22362.8
[Error - 8:21:45 AM] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Info  - 8:21:45 AM] Connection to server got closed. Server will restart.
true
[Error - 8:21:45 AM] Microsoft.CodeAnalysis.LanguageServer client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
Using dotnet configured on PATH
Dotnet path: /bin/dotnet
Activating C# standalone...
You must install .NET to run this application.
App: /home/aapt/.vscode/extensions/ms-dotnettools.csharp-2.0.376-linux-x64/.roslyn/Microsoft.CodeAnalysis.LanguageServer
Architecture: x64
App host version: 7.0.0-preview.7.22362.8
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=rhel.9-x64&apphost_version=7.0.0-preview.7.22362.8
[Error - 8:21:45 AM] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Info  - 8:21:45 AM] Connection to server got closed. Server will restart.
true
[Error - 8:21:45 AM] Microsoft.CodeAnalysis.LanguageServer client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 8:21:45 AM] Restarting server failed
Message: Pending response rejected since connection got disposed
Code: -32097
Using dotnet configured on PATH
Dotnet path: /bin/dotnet
Activating C# standalone...
You must install .NET to run this application.
App: /home/aapt/.vscode/extensions/ms-dotnettools.csharp-2.0.376-linux-x64/.roslyn/Microsoft.CodeAnalysis.LanguageServer
Architecture: x64
App host version: 7.0.0-preview.7.22362.8
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=rhel.9-x64&apphost_version=7.0.0-preview.7.22362.8
[Error - 8:21:45 AM] Server initialization failed.
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 8:21:45 AM] Microsoft.CodeAnalysis.LanguageServer client: couldn't create connection to server.
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 8:21:45 AM] Restarting server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 8:21:45 AM] Restarting server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Info  - 8:21:45 AM] Connection to server got closed. Server will restart.
true
Using dotnet configured on PATH
Dotnet path: /bin/dotnet
Activating C# standalone...
You must install .NET to run this application.
App: /home/aapt/.vscode/extensions/ms-dotnettools.csharp-2.0.376-linux-x64/.roslyn/Microsoft.CodeAnalysis.LanguageServer
Architecture: x64
App host version: 7.0.0-preview.7.22362.8
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=rhel.9-x64&apphost_version=7.0.0-preview.7.22362.8
[Error - 8:21:45 AM] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 8:21:45 AM] The Microsoft.CodeAnalysis.LanguageServer server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 8:21:45 AM] Microsoft.CodeAnalysis.LanguageServer client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
Steps to reproduce

Create a folder and create a BlazorServer project in it:

mkdir Blazor
cd Blazor
dotnet new blazor --use-server

Navigate to the folder you created Blazor and open VS Code using Terminal Emulator
 code .

Note:

This issue does not reproduce on lower versions of C# v2.0.357
This issue does not repro on Windows/Mac

Actual behavior
some error boxes pop up in the lower right corner

This issue does not reproduce on latest versions of C# v2.0.413

This issue does not reproduce on latest versions of C# v2.0.436, So closed this issue.


Means extraction

Hi i would like to extract the means for creating of supervectors from my models using python, how can i do this?

You can access the "_means" attribute after loading the model.
http://scikit-learn.org/stable/modules/generated/sklearn.mixture.GaussianMixture.html#sklearn.mixture.GaussianMixture


Update dependency ts-node to v10

This PR contains the following updates:

Package
Type
Update
Change

ts-node (source)
devDependencies
major
9.1.1 -> 10.9.1

Release Notes

TypeStrong/ts-node (ts-node)
v10.9.1
Compare Source
Fixed

Workaround nodejs bug introduced in 18.6.0 (#1838) @cspotcode

Only affects projects on node >=18.6.0 using --esm
Older versions of node and projects without --esm are unaffected

https://github.com/TypeStrong/ts-node/milestone/18?closed=1
v10.9.0
Compare Source
Added

--project accepts path to a directory containing a tsconfig.json (#1829, #1830) @cspotcode

previously it required an explicit filename

Added helpful error message when swc version is too old to support our configuration (#1802) @cspotcode
Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented except for API docs) (#1815) @cspotcode

Fixed

Fixed bug where child_process.fork() would erroneously execute the parent's entrypoint script, not the intended child script (#1812, #1814) @devversion
Fixed support for jsx modes "react-jsx" and "react-jsxdev" in swc transpiler (#1800, #1802) @cspotcode
Fixed support for import assertions in swc transpiler (#1817, #1802) @cspotcode
Fixed bug where calling repl.evalCode() with code not ending in a newline would not update the typechecker accordingly (#1764, #1824) @cspotcode

https://github.com/TypeStrong/ts-node/milestone/16?closed=1
v10.8.2
Compare Source
Fixed

Revert "Use file URL for source map paths" (#1821) @cspotcode

Fixes #1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
Fixes #1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging

Allow JSON imports in node 16.15 and up (#1792) @queengooborg

JSON imports were already supported in v17.5 and up
this change extends support to >=16.15.0,<17.0.0
These version ranges match vanilla node's support for JSON imports

https://github.com/TypeStrong/ts-node/milestone/15?closed=1
v10.8.1
Compare Source
Fixed

Fixed #1769: source URLs in source map cache were malformed on Windows, affecting code coverage reports (#1769, #1771) @PaperStrike
Fixed #1778: typechecker was erronously resolving imports from ESM files as if they were from CJS files (#1778, #1782) @cspotcode

https://github.com/TypeStrong/ts-node/milestone/14
v10.8.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1767
Added

Added support for module=NodeNext, module=Node16, .mts, .cts, .mjs, and .cjs file extensions (#1414, #1694, #1744, #1745, #1727, #1717, #1753, #1757) @cspotcode

For best results, enable experimentalResolver (docs)
See TypeScript's official documentation: https://www.typescriptlang.org/docs/handbook/esm-node.html
enables mixed-mode projects with both ESM and CommonJS
enables all supported file extensions in TypeScript 4.7
Obeys package.json "type"

Added ability to include file extensions in CommonJS imports (#1727, #1753) @cspotcode

Enables consistency with ESM, where file extensions are often mandatory

Resolves from emitted to source file extensions (#1727, #1753) @cspotcode

Must enable experimentalResolver, will be enabled by default in a future version (docs)
Typechecker requires importing the emitted file extension; ts-node resolves correctly to the source file.  E.g. import "./foo.js" will execute foo.ts See also: TypeScript issue #37582
If typechecking is disabled, you can also use source file extensions.  E.g. import "./foo.ts"

Added experimentalSpecifierResolution (#1727, #1753) @cspotcode

the same as Node's --experimental-specifier-resolution (Node docs)
can also be specified in tsconfig.json for convenience, to avoid the CLI flag
allows omitting file extensions in ESM imports, plus a few other CommonJS-style conveniences

Adds diagnostics property to TSError, with array of TypeScript diagnostic objects from the compiler (API docs) (#1705, #1706) @paulbrimicombe

Changed

Renames option experimentalResolverFeatures to experimentalResolver (docs) (#1727) @cspotcode
Internal change to ESM loader for compatibility with forthcoming node versions: returns shortCircuit: true (#1714, #1715) @cspotcode
Performance: Optimize filesystem stat calls in ESM loader and new CommonJS resolver (#1758, #1759) @cspotcode
Performance, maintenance: Upgrade source-mapper dependency "@cspotcode/source-map-support"

Switches to "trace-mapping" for underlying source-map parsing (#1729) @cspotcode

Fixed

Fixed bug where REPL .type command was not showing any type information when using TypeScript nightly builds (#1761, #1762) @cspotcode
Correctly suppress "Custom ESM Loaders" warning on newer node versions where the warning's prose changed (#1701) @cspotcode
Fixed REPL bug where function signatures could not be entered across multiple lines (#1667, #1677) @d9k
REPL treats unparenthesized object literals as objects, instead of as block scopes (#1697, #1699) @jhmaster2000
Fixed bug where preferTsExts combined with third-party transpiler hooks could disrupt nyc code coverage (#1755) @cspotcode
Fixed bug where file:// URLs in stack traces did not always use percent-encoding (#1738, #1726, #1729) @cspotcode
Fixed bug where v8-compile-cache-lib did not correctly unhook itself (#1717, #1718, #1719) @cspotcode

This internal dependency is used to speed up loading the TypeScript compiler

Docs

Many docs improvements (#1682) @cspotcode
Options page: each option its own linkable header w/usage example (#1606) @cspotcode
Categorize APIs in typedoc, make entrypoints more prominent (#1456) @cspotcode
Clarify that the shorthand for --project is -P, not -p (#1731, #1734) @lobsterkatie
Add common ESM errors to Troubleshooting page (#1607) @cspotcode

https://github.com/TypeStrong/ts-node/milestone/12
v10.7.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1680
Added

Adds --esm flag, option, and ts-node-esm binary (#1258, #1655)

Enables full esm support; no need for --loader nor NODE_OPTIONS
Use shebang #!/usr/bin/env ts-node-esm, run ts-node --esm, or add to your tsconfig.json: "ts-node": {"esm": true}

Changed

Unflag ESM json modules on node >=17.5.0 (#1661, #1665) @Jamesernator

no longer requires --experimental-json-modules

Lazy-load dependencies to improve startup responsiveness. (#1676)

Fixed

Fixed bug where "compiler", "transpiler", and swc backend would not resolve relative to the tsconfig.json that declared them (#1662, #1655)

Enables reusable tsconfig.json shared via node module to include necessary dependencies

https://github.com/TypeStrong/ts-node/milestone/11
v10.6.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1666
Added

Adds workaround for extensionless entrypoints with ESM loader (#1649, #1654)

You can now combine tools such as mocha with --loader ts-node/esm, where previously node would throw [ERR_UNKNOWN_FILE_EXTENSION]
node has a bug where combining --loader with an extensionless entrypoint causes this error nodejs/node#33226
Some tools, for example mocha, have an extensionless entrypoint. (source, source)
Combining NODE_OPTIONS=--loader ts-node/esm with these tools causes this error.  mochajs/mocha#4645
node intends to fix this bug in a future release: nodejs/node#41711
In the interim, we have implemented a workaround in ts-node.

Adds support for target "ES2022" in moduleTypes overrides (#1650)

Fixed

Fixed bug where --swc and other third-party transpilers did not respect moduleTypes overrides (#1651, #1652, #1660)
Fixed bug where node flags were not preserved correctly in process.execArgv (#1657, #1658)

This affected child_process.fork(), since it uses process.execArgv to create a similar child runtime.
With this fix, child_process.fork() will preserve both node flags and ts-node hooks.

Fixed compatibility TypeScript 4.7's API changes (#1647, #1648)

https://github.com/TypeStrong/ts-node/milestone/9
v10.5.0
Compare Source

Questions about this release? Ask in the official discussion thread: #1634
Added

Eliminate "Emit Skipped" errors (#693, #1345, #1629)

Avoids all "Emit Skipped" errors by performing a fallback transpileOnly-style transformation.
Does not affect typechecking.  Type errors are still detected and thrown.
Fallback has the same limitations as isolatedModules. This will only affect rare cases such as using const enums with preserveConstEnums disabled.
Fixes #693

Graduate swc transpiler out of experimental; add swc: true convenience option (docs) (#1487, #1536, #1613, #1627)

"swc": true or --swc will use swc for faster execution
This feature is no longer marked "experimental."  Thank you to everyone who filed bugs!

swc transpiler attempts to load @swc/core or @swc/wasm dependencies from your project before falling-back to global installations (#1613, #1627)

global fallback only occurs when using a global installation of ts-node

Add support for TypeScript's traceResolution output (docs) (#1128, #1491) @TheUnlocked
Support import assertions in ESM loader (docs) (#1557, #1558, #1559, #1573) @Pokute, @geigerzaehler

Allows importing JSON files from ESM with the requisite flag (docs)

ts-node -vvv also logs absolute paths to ts-node and typescript, to make it more obvious when you're accidentally using globally-installed versions (#1323, #1620)
Add swc target "es2022" (#1535, #1540)

When you have target es2022 in tsconfig, will use swc's es2022 target

Changed

Initialize TypeScript compiler before starting REPL prompt (#1498) @TheUnlocked

Improves responsiveness for first line of REPL input

Use v8-compile-cache-lib to load typescript

improves startup time (#1339, #1603)

Support both --camelCase and --hyphen-case for all CLI flags; update documentation to use --camelCase (#1598, #1599)

Not a breaking change; CLI continues to accept both forms

Make TSError diagnosticText property non-enumerable to prevent it from being logged below the stack (#1632)

Fixed

Fix #1538: REPL inputs fail to transpile via swc (#1538, #1541, #1602)
Fix #1478: REPL erroneously logged undefined for all inputs after the first when using swc transpiler (#1478, #1580, #1602)
Fix #1389: In --showConfig output, emit accurate moduleTypes paths resolved relative to the tsconfig.json which declared them (#1389, #1619)
Fix: Remove indentation from ts-node --help output (#1597, #1600)
Fix #1425: Merged definitions correctly into tsconfig.schemastore-schema.json (#1425, #1618)
Fix: Allow disabling "use strict" emit in SWC transpiler (#1531, #1537)
Fix: Add missing ERR_UNKNOWN_FILE_EXTENSION constructor; was throwing ERR_UNKNOWN_FILE_EXTENSION is not a constructor (#1562) @bluelovers
Fix #1565: entrypoint resolution failed on node v12.0.x and v12.1.x (#1565, #1566) @davidmurdoch

Docs

Explain env -S flag for shebangs (docs) (#1448, #1545) @sheeit, @chee
Suggest skipIgnore when you want to compile files in node_modules (docs) (#1553) @webstrand
Fix typo in moduleTypes on options page (docs) (#1630, #1633)

Misc

Adds experimental experimentalResolverFeatures option, but it does not do anything yet (#1514, #1614)

https://github.com/TypeStrong/ts-node/milestone/4
v10.4.0
Compare Source
Added

Adds support for targets "es2020" and "es2021" to swc transpiler (#1521)
Adds automatic target downgrade when using older versions of swc (#1521)

If tsconfig specifies es2020, but your version of swc only supports up to es2019, ts-node will automatically switch to es2019 instead of throwing an error

Changed

Improves types and API docs for creatEsmHooks (API docs) (#1506, #1529)

Fixed

Fix #1526: data URL handling in new ESM loader hooks API (#1526, #1529)

https://github.com/TypeStrong/ts-node/milestone/8
v10.3.1
Compare Source
Fixed

Add version check to use new loader hooks API for node >=16.12.0 (#1522) @shrujalshah28

https://github.com/TypeStrong/ts-node/milestone/7
v10.3.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1507
Added

Declare types for node builtin modules within REPL so you do not need to import them (#1424, #1500)

Node REPL exposes builtin modules as globals; typechecker now understands this
Typechecking should no longer raise errors when using builtins without first importing
For example: util.promisify(setTimeout)(1000) or fs.readFileSync('example.txt')

Add createEsmHooks() function to create ESM loader hooks (API docs) (#1439) @nonara

Can be used to compose our loader hooks with another loader or additional logic

register() accepts a ts-node Service (API docs) (#1474)

register(options) is still supported; no breaking changes

Add support for Node.js's new loader hooks API (#1372, #1457, #1007) @jonaskello

Node.js has changed their loader hooks API
ts-node is compatible with all node versions, detects your node version and exposes the correct hooks API
Node's new API currently only available in node v17 nightly builds
Node will eventually backport the changes to node 16, and may also be backport to 14 and 12

Add --emit to --help output (#1400, #1484) @markbradley27

Changed

When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support

See complete description in Fixed section below

Fixed

Fix #1440, #1441, #1438, #1495: Incorrect stack traces when third-party libraries use source-map-support instead of @cspotcode/source-map-support (#1440, #1441, #1438, #1495, cspotcode/node-source-map-support#23, #1496, #1497) @ejose19

When ts-node is registered and other libraries require('source-map-support'), they will be redirected to @cspotcode/source-map-support
ts-node uses @cspotcode/source-map-support for the fixes and enhancements listed here: @cspotcode/source-map-support changelog
To ensure correct stack traces, all libraries must share a compatible sourcemap support implementation

Fix #1363: REPL may erroneously combine previous input with next input, eval both as a single statement (#1363, #1480) @TheUnlocked

For example, entering 100 on first line and * 2 on second line would erronously be interpreted as 100 * 2
REPL now ensures both lines are separate statements, both when typechecking and when evaluating

Fix #1488: Node may log "circular dependency" warning when using allowJs (#1488, #1489)
Fix #1301: Filter empty strings from TS_NODE_IGNORE and TS_NODE_IGNORE_DIAGNOSTICS; treat empty environment variable as empty array (#1301, #1483) @ValeriaVG

TS_NODE_IGNORE= ts-node ./example.ts will disable default ignore rules; will compile files in ./node_modules

Docs

Update VSCode debug configuration (Docs) (#1466)
Update ESM-related messaging to clarify that experimental status is due to Node.js, not ts-node (#1455)
Refer to ts-node consistently (#1481) @animafps

https://github.com/TypeStrong/ts-node/milestone/5
v10.2.1
Compare Source
Fixed

Fixes #1426: Do not import typescript outside of configuration/project loading (#1433, #1426) @Songkeys

We take care to load your project's version of typescript, falling back to a globally-installed version if necessary.
10.2.0 introduced a bug where we did not do this consistently, causing global or npx installations of ts-node to attempt loading typescript relative to themselves, not your project.
This failed if typescript was not globally installed or npx did not install peer dependencies.

https://github.com/TypeStrong/ts-node/milestone/6
v10.2.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1423
Added

Adds top-level await support to REPL (#1383, #245) @ejose19

can be disabled with --no-experimental-repl-await, experimentalReplAwait, or TS_NODE_EXPERIMENTAL_REPL_AWAIT (CLI docs, API docs)

Setting "pretty": false disables pretty formatting of diagnostics even when stdout is a TTY (#1418, #1420) @elevatebart

Applies to ts-node's pretty option, not to be confused with TypeScript's pretty option

Ignores diagnostics which are annoying in an interactive REPL (#1396, #1120, #729, #850, #469)

For example, when you input const foo = 1 in the REPL, foo is unused.  We ignore the resulting diagnostic foo is declared but its value is never read
Diagnostics are only ignored in the REPL
Diagnostics for non-REPL files imported by the REPL will still be shown

Logged stack traces are colorized to match vanilla node's behavior (#1412, #1405)

Fixed

Fix #1397: SWC transpiler should emit ECMAScript imports and exports when configuration dictates (#1409, #1397)

Enables SWC transpiler to be used alongside --loader

Fix #1403: source-map-support breaks rendering of node errors (#1405, #1403)
Fix #1410: rendering of async stack frames should include async annotations (#1405, #1410)
Fix #1411: wrong order of process 'exit' event and logging unhandled exception (#1405, #1411)
Fix #1419: Should not throw require.resolve error when @types/node peerDependency is missing (#1419, #1422)

https://github.com/TypeStrong/ts-node/milestone/2
v10.1.0
Compare Source
Questions about this release? Ask in the official discussion thread: #1390
Added

Add "moduleType" option to override module type -- CommonJS or ECMAScript -- on select files. (docs) (#1342, #1371, #1376)

Useful when a configuration file, for example webpack.config.ts, must execute as CommonJS but the rest of the project is ESM
selectively overrides package.json "type" and tsconfig.json "module"
akin to .cjs and .mjs extensions, but for .ts and .tsx files
thanks to @jayaddison for help on test coverage

Implement "extends" support for "ts-node" options in tsconfig.json (#1328, #1356)

"ts-node": {} options will be parsed from extended tsconfigs
allows sharing and deduplicating ts-node configuration

Un-deprecate scope and scopeDir; add both to CLI and tsconfig.json options; un-deprecate TS_NODE_SCOPE env var; add TS_NODE_SCOPE_DIR env var (docs) (#1346, #1367)

Changed

Improve error messages thrown by native ESM loader hooks (#1357, #1373) @tars0x9752

messages more closely match node; are more descriptive

Emit "ts-node" object at the top of --showConfig output instead of the bottom (#1355)

Fixed

Fix #1282: Set correct globals in [stdin], [eval], and <repl> contexts (#1333)

More closely align ts-node's behavior with vanilla node
Affects the interactive REPL, piping to stdin, and ts-node -e
Matches node's behavior for globals __filename, __dirname, module and sub-fields of module, exports, and builtin module aliases fs, etc

Fix #1343: Set swc option keepClassNames to true (#1344)
Fix: #1387: REPL outputs 'use strict' after first empty line of input (#1388) @ejose19

Docs

Update ESM docs to say that env vars are supported with node --loader ts-node/esm (docs) (#1379)

https://github.com/TypeStrong/ts-node/milestone/3
v10.0.0
Compare Source
Questions about this release?  Ask in the official discussion thread: #1337
Breaking changes are prefixed with [BREAKING]
Added

Adds --show-config to log the resolved configuration (docs) (#1100, #1243)
Bundle and re-export @tsconfig/node* configurations for convenience (docs) (#1202, #1236, #1313)
Default to appropriate @tsconfig/node* configuration based on node and typescript versions (docs) (#1202, #1236, #1313)
Automatically reference @types/node; use globally-installed @types/node if not locally installed (#1240, #1257)
Add swc integration and new --transpiler option to use third-party transpilers for a massive speed boost on large codebases (docs) (#779, #1160)
Add scopeDir API option (docs) (#1155)
Add projectSearchDir API option (docs) (#1155)
Add --cwd-mode and ts-node-cwd to resolve config file relative to cwd, not entrypoint script (#1155)

Changed

[BREAKING] Make --script-mode default behavior; resolve tsconfig relative to entrypoint script instead of cwd (#949, #1197, #1155)

In most cases this change will have no noticeable effect
Primarily benefits portable shell scripts on your $PATH, because ts-node will respect the script's local tsconfig.json
Use --cwd-mode or ts-node-cwd if you need legacy behavior

[BREAKING] ignore rules evaluate relative to tsconfig.json directory, otherwise cwd (#1155)
[BREAKING] Remove support for node 10.  Minimum supported version is node 12 (#1312)
Rename --dir to --cwd; rename TS_NODE_DIR to TS_NODE_CWD (#1155)

--dir and TS_NODE_DIR are deprecated but still parsed for backwards-compatibility
--dir effectively changed the working directory of ts-node; renaming makes this behavior more obvious

Deprecated

Deprecate TS_NODE_SCOPE (#1155)
Deprecate --dir and TS_NODE_DIR (#1155)

Removed

[BREAKING] Internal APIs removed from type declarations (#1242)

Removed DEFAULTS, normalizeSlashes, parse, split
No features were removed
This will only affect consumers of ts-node's programmatic API

Fixed

[BREAKING] Fix #1229 and #1235: always throw ERR_REQUIRE_ESM when attempting to execute ESM as CJS, even when not using --loader ts-node/esm (#1232)

This aligns our behavior with vanilla node

[BREAKING] Fix #1225: compiler is loaded relative to tsconfig.json instead of entrypoint script (#1155)

In most cases this change will have no noticable effect

Fix #1217: REPL not always using passed stdout and stderr (#1224)
Fix #1220: ts-node ./index may execute the wrong file extension because tsconfig search poisons the require.resolve cache (#1155)
Fix #1322: Sourcemaps fail for filenames with spaces or other characters which are percent-encoded in URLs (#1160, #1330)
Fix #1331: Resolution of node builtin modules in ESM loader fails on node >=12.20.0, <13 (#1332)

Docs

New documentation website: https://typestrong.org/ts-node

README is generated to match the website
Added page explaining CommonJS vs ESM
Added page with Performance advice
Added Troubleshooting page
Organized and added to "Recipes" section with third-party tool integrations
Added TypeDoc-generated API docs
Work was spread across multiple tickets: #1207, #1213, #1221, #1228, #1244, #1250, #1294, #1295, #1296, #1297
Thanks to these contributors for PRs which improved our documentation

add troubleshooting tip for syntax errors (#1201) @jedwards1211
Clarify handling of tsx/jsx file extensions (#1179) @NaridaL

Added CONTRIBUTING.md to document the codebase and our development workflow

https://github.com/TypeStrong/ts-node/milestone/1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Install Role Error: unable to recognize "": no matches for kind "Role" in version ""

Trying to install a Role using Helm and I keep getting the error unable to recognize "": no matches for kind "Role" in version "". I can apply the Role manually but ushing helm it won't.

Output of helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"g
c", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:34:22Z", GoVersion:"go1.9.3", Compiler:"
gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): Openstack
The tiller logs with the error is:
[tiller] 2018/10/15 01:01:10 failed install perform step: unable to recognize "": no matches for kind "Role" in version ""

The Template is:
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: leader-election
rules:
- apiGroups:
  - "" # "" indicates the core API group
  resources:
    - endpoints
  # only giving access to these operations on the resource objects
  verbs:
    - get
    - create
    - update

nvm it was a template error not the role error.


Update AboutViewController to Xcode 8 and Swift 3

Sorry, I thought that the Xcode 8 branch was in Swift 3 syntax !

@fethica if you want to convert it to Swift 3, that would be welcomed and appreciated! I've been slammed at work... Thanks much!

So, what I'm saying is that I'm not tied to making a Swift 2.3 release. We could skip to Swift 3.

Ok thanks ! I will open a new PR with Swift 3 when the conversion is finished.


[bug] settings.set with dotted notation limit key names that can be used

you cannot set a deeper entry with the same key as higher entry.
settings.set('a.b', 1)
settings.set('a.c', 2)
settings.set('a.c.k', 22)
--> {'c': {'k': 22}, 'b': 1}
settings.set('a.c.b', 3)
--> {'c': {'b': 3, 'k': 22}}
the higher entry 'a.b' was removed
the problem lie within _dotted_set and the use of 'tail' and merge
tries to find a quick solution, but i a don't have the time now, will bypass by using different keys :(

This is related to the merging strategies #241 (ths issue is closed but we can reopen the discussion)
Do we want set to replace an existing key or to contribute to existing keys? I can't find a good solution for this problem.
maybe introduce a new merge_set?

I figured out the problem now and it is a real bug.
We are passing tail to object_merge as a keyname and it is wrong, we should change that to accumulate the whole path.
for a.b.c instead of passing tail=c we really need to recursively accumulate it and compare whole path a on first call, a.b on second, a.b.c on the tail call.
Also we should invert the order that dicts are merged on object_merge and instead of taking the new as the definitive object use the old which will keep all existing keys.

Fixed in #415 thanks @NoamGraetz2


check if method belongs to singleton_class before removing it, fixes #1906

This looks good, @rupurt.  I'd like a spec for it, though; we rely extremely heavily on our test suite during refactorings and generally remove code that can be removed w/o any specs failing.  To prevent a future regression a spec would help.  It's a tricky one to write, though, because Kernel#it has to be defined before rspec gets loaded.   Here's one I wrote up that can go in spec/rspec/core_spec.rb at the bottom:
it "does not blow up if some gem defines `Kernel#it`", :slow do
  code = 'Kernel.module_eval { def it(*); end }; require "rspec/core"'
  out, err, status = run_ruby_with_current_load_path(code)

  expect(err).to eq("")
  expect(out).to eq("")
  expect(status.exitstatus).to eq(0)
end

It shells out and starts a new process and is kinda slow, but does the trick.

:+1:
Cool thanks for doing the work for us :grin:

Thanks, @rupurt!


[Python] How to get get_distance() to work on a depth image?

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
Gazebo

SDK Version
{ legacy / 2.. }

Language
python

Segment
Drone

Issue Description
Hello, sorry if this question has already been asked, but I haven't been able to find anything yet. I have a drone in a Gazebo simulation with the D435 on it. In a Python file, I have a subscriber to /camera/depth/image_raw. In the callback, I used imgmsg_to_cv2 to convert it to an image. How do I get the get_distance() function to work on this image? I've pasted my code below:
#!/usr/bin/env python2

import rospy
from cv_bridge import CvBridge, CvBridgeError
from sensor_msgs.msg import PointCloud2 as sensor_msgs_pc2
import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import Image
import pyrealsense2 as rs
import cv2

class CameraFeed(object):

    def __init__(self):
        print('[INFO] Initialized object')
        self.image_sub = rospy.Subscriber("/camera/depth/image_raw",
                                          Image,
                                          self.depth_camera_callback)
        self.bridge_object = CvBridge()

    def depth_camera_callback(self, data):
        try:
            original_image = self.bridge_object.imgmsg_to_cv2(
                data,
                desired_encoding="passthrough"
            )  # bgr8 is the default OpenCV encoding
        except CvBridgeError as e:
            print(e)
        print('[INFO] Got callback')
        cv2.imshow('Image', original_image)
        cv2.waitKey(3)
        rs.depth_frame.get_distance()
        raw_input()
        print('[INFO] Finished callback')

def main():
    print('[INFO] Running file')
    camera_feed_object = CameraFeed()
    rospy.init_node("camera_feed_node", anonymous=True)
    try:
        rospy.spin()
    except KeyboardInterrupt:
        print("Shutting down")

if __name__ == '__main__':
    main()

Any kind of help would be greatly appreciated!

You can output the image to a text file with:
np.savetxt(filepath, depth_image, fmt='%d', newline='\n', delimiter=' ')
Each pixel will have a value of depthunits. (default for d435 is 0.001m and the L515 is 0.00025m)

Hi @kadhirumasankar   The approach that I usually see is to set up a 'depth' variable whose value is the depth value multiplied by the depth scale, and then calculate distance this way:
dist,,,_ = cv2.mean(depth)
Intel's Python distance_to_object tutorial for displaying the depth of an object on-screen uses this method.
https://github.com/IntelRealSense/librealsense/blob/jupyter/notebooks/distance_to_object.ipynb
Another way in which this distance calculation technique is used by a RealSense community member in a simpler form is here:
https://github.com/IntelRealSense/librealsense/issues/3473

Hi @MartyG-RealSense, thanks for your reply. I had seen that tutorial before, but I couldn't use it because I can't set up a pipeline since my RealSense camera is on a drone in a Gazebo simulation environment. I have to subscribe to ROS topics and use their callbacks. I found out that subscribing to the /camera/depth/image_raw topic gave me an image which I could index with my coordinates of interest, and it seems to output the depth in mm. I verified this by seeing what the max range of the camera was set to and the output cutoff at the same number.
Is that correct? Does indexing the image indeed give you the depth in mm? If so, I'll close the issue once I get your reply

According to Doronhi the RealSense ROS wrapper developer, depth is in the ROS standard scale of mm.
https://github.com/IntelRealSense/realsense-ros/issues/277#issuecomment-525676873

Great, looking like just indexing the depth image works then. Thank you!


How to use copy and paste

How to use copy and paste,
Copy the existing SQL script into the query box for execution
thanks

shift+ins


updatePivot vs detach/attach on a simple join table

Wondering if anyone can suggest a better implementation of the updatePivot method vs attach / detach when attempting to update a model and a relation in a join table (model_relation).
Current implementation (below) is from a PUT route which takes changes to the model itself plus an array of relation checkbox options whose ids are updated in the model_relation join table.
Finally, while the following does work, in the last .then we only seem to get the relation returned, is there a way to return the whole model object with it's updated relation or does this require a separate query?
Business logic

A post has many categories and a category can belong to many posts
A user can update a title and description of a post and they can also assign multiple categories (many-to-many) by way of checkboxes in the form.
The categories_posts join table has 2 columns category_id and post_id with the relationships established in the model

Models
Post model
var Post = Bookshelf.Model.extend({
    tableName: "posts",
    idAttribute: "id",

        categories: function() {
        return this.belongsToMany('Category', 'categories_posts', 'post_id');
    }
});

Category model
var Category = Bookshelf.Model.extend({
    tableName: 'categories',
    idAttribute: 'id',

        posts: function() {
        return this.belongsToMany('Post', 'categories_posts', 'category_id');
    }
});

Request body payload
{
id: "302",
title: "Lorem ipsum dolor sit amet",
description: "Phasellus bibendum convallis tempor. In id aliquam est",
user_id: 2,
created_date: "2014-07-09T17:22:39.343Z",
last_updated_date: "2014-07-09T17:22:39.343Z",
status_id: 1,
categories: [10, 1, 2, 5, 9],
user: {
  id: 2,
  user_name: "juliusss",
  email_address<EMAIL_ADDRESS>  full_name: "John Doe" }
}

PUT Route
router.put('/:id', function(req, res) {

    var categoryIds = req.body.categories;

    new Post({id: req.params.id})
    .fetch({withRelated: 'relation'})
    .then(function(post) {
        post.set({
            title: req.body.title,
            description: req.body.description
        });
        return post.save();
    })
    .then(function(updatedPost) {
        return updatedPost.relation().detach();
    })
    .then(function(updatedPost) {
        return updatedPost.attach(categoryIds);
    })
    .then(function(updatedPost) {
        res.json(200, updatedPost)
    })
    .catch(function(errors) {
        res.json(500, errors.toJSON());
    })
});

Any help greatly appreciated as I tried the updatePivot without success but perhaps I was implementing it incorrectly.

also curious as to a cleaner solution for this, brief sample of my current implementation similar to @juliussss's
export async function update(ctx) {
  const story = ctx.body.story

  await story.save(ctx.request.body.story, { patch: true })
  await story.celebrities().detach()
  await story.celebrities().attach(ctx.request.body.celebrities)

  const response = await story.load('celebrities')

  ctx.body = { story: response }
}

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again


The game crashes when I use /txt edit!

The game crashes when I use /txt edit!

Hi @MateusBlackyOFC,
Can you show me a crash dump or a log of when the error occurred?

Oi@MateusBlackyOFC, Você pode me mostrar um despejo de memória ou um log de quando o erro ocorreu?

What crashes is the game not the server!

Watch the video.
link: https://youtu.be/EN9po_f_Ixk

Watch the video. link: https://youtu.be/EN9po_f_Ixk

If possible, can you test it out without the texture pack and possibly on a completely freshly set up server without plugins? Write us then if it worked or if your client still crashes. Texter has nothing to do with it as far as I know.

@fuyutsuki i think this issue can be closed because it isn‘t an fault from Texter.


Improve the "Browse Packages" page

[ ] Display the search results in tabular form.
[ ] Extend search results to include vote counts.
[ ] Implement sorting functionality for returned results
[ ] Implement filtering capabilities on returned results.
[ ] Ensure other links around the site point to appropriate search result pages.

Proposed mockup: http://dzackgarza.com/mockup/browse.html


Gamepad Input (under Bluetooth) no longer works while Steam is running in the background

Describe the bug
If Steam is currently running in the background, all Gamepad inputs under Bluetooth mode do not work. This doesn't affect USB mode. Most likely, this is probably due to the way Steam Input and GLFW handle Bluetooth Gamepad devices.
To Reproduce

Steam must be launched first before launching with the Midnight Controls mod.
Connect your Game Controller of choice under Bluetooth. For my case: I use both DualShock 4 and DualSense Controller.
Launch Minecraft Fabric
Try to press any buttons
[Optional] Open a new or existing world
Gamepad Inputs no longer work

Alternatively: you can also reproduce this issue by launching Steam during your Minecraft gaming section. That also means the last Button/Joystick press is going to be active until you reconnect your controller (under USB mode)
Workarounds

Close Steam
Disconnect your Controller of choice and then reconnect it.
Now Gamepad inputs work as intended.

Expected behavior
Gamepad Inputs under Bluetooth mode should always work while Steam is currently running in the background.
 It likes to take it all for itself. Sometimes I had issues with gamepads not working unless Steam was open, which is insanely weird.


Could i know ip-adress of remote client?

I use Titanium Proxy as proxy server in local network, All works fine. But i want to know which ip adreses use proxy. Is it possible?

Just added the property inside SessionEventArgs
 Console.WriteLine(e.ClientIpAddress);


Container image for octavia and designate predictable IPs support

Jira: OSPRH-10551

/test all

looks good to me


tty regression from 3.4 to 3.5

3.4 works as expected:
docker run -it --rm alpine:3.4 sh                                                                                [ruby-2.3.3]
/ # tty
/1

3.5 fails:
docker run -it --rm alpine:3.5 sh                                                                                [ruby-2.3.3]
/ # tty
not a tty

Any workarounds for this?

I'm not sure what is going on here. I'll do some more research.

This could be related to docker#8755.

This is still present in alpine:3.6.

Running tty in an alpine 3.6 container with docker 17.07, it returns succesfully - /dev/pts/0. I imagine that it's not due to Alpine or the image being updated with a fix, but rather docker itself fixing the bug @geraldlai pointed out.

It seems that way.  I can't reproduce this on alpine 3.7 with docker 17.09.1-ce.


Not working on heroku

Hi
I installed this gem. Works like a charm in dev but not in production on heroku.
I have
config.consider_all_requests_local       = false
in my production.rb file, full config file below.
Your help is appreciated
Thanks
Youssef
  # Settings specified here will take precedence over those in config/application.rb.

  # Code is not reloaded between requests.
  config.cache_classes = true

  # Eager load code on boot. This eager loads most of Rails and
  # your application in memory, allowing both threaded web servers
  # and those relying on copy on write to perform better.
  # Rake tasks automatically ignore this option for performance.
  config.eager_load = false

  # Full error reports are disabled and caching is turned on.
  config.consider_all_requests_local       = false
  config.action_controller.perform_caching = true

  # Disable serving static files from the `/public` folder by default since
  # Apache or NGINX already handles this.
  config.public_file_server.enabled = ENV['RAILS_SERVE_STATIC_FILES'].present?

  # Compress JavaScripts and CSS.
  config.assets.js_compressor = :uglifier
  # config.assets.css_compressor = :sass

  # Do not fallback to assets pipeline if a precompiled asset is missed.
  config.assets.compile = false

  # `config.assets.precompile` and `config.assets.version` have moved to config/initializers/assets.rb

  # Enable serving of images, stylesheets, and JavaScripts from an asset server.
  # config.action_controller.asset_host = 'http://assets.example.com'

  # Specifies the header that your server uses for sending files.
  # config.action_dispatch.x_sendfile_header = 'X-Sendfile' # for Apache
  # config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect' # for NGINX

  # Mount Action Cable outside main process or domain
  # config.action_cable.mount_path = nil
  # config.action_cable.url = 'wss://example.com/cable'
  # config.action_cable.allowed_request_origins = [ 'http://example.com', /http:\/\/example.*/ ]

  # Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
  config.force_ssl = true

  # Use the lowest log level to ensure availability of diagnostic information
  # when problems arise.
  config.log_level = :debug

  # Prepend all log lines with the following tags.
  config.log_tags = [ :request_id ]

  # Use a different cache store in production.
  # config.cache_store = :mem_cache_store

  # Use a real queuing backend for Active Job (and separate queues per environment)
  # config.active_job.queue_adapter     = :resque
  # config.active_job.queue_name_prefix = "testapp_#{Rails.env}"
  config.action_mailer.perform_caching = false

##### Config for sending emails
  config.action_mailer.smtp_settings = {
    address: "smtp.xxx.com",
    port: 587,
    domain: Rails.application.secrets.domain_name,
    authentication: "plain",
    enable_starttls_auto: true,
    user_name: Rails.application.secrets.email_provider_username,
    password: Rails.application.secrets.email_provider_password
  }
  # ActionMailer Config
  config.action_mailer.default_url_options = { :host => Rails.application.secrets.domain_name }
  config.action_mailer.delivery_method = :smtp
  config.action_mailer.raise_delivery_errors = true
  # Send email in development mode?
  config.action_mailer.perform_deliveries = true

  config.action_mailer.default_options = {
    from: 'xxx<EMAIL_ADDRESS>  }

##############

  # Ignore bad email addresses and do not raise email delivery errors.
  # Set this to true and configure the email server for immediate delivery to raise delivery errors.
  # config.action_mailer.raise_delivery_errors = false

  # Enable locale fallbacks for I18n (makes lookups for any locale fall back to
  # the I18n.default_locale when a translation cannot be found).
  config.i18n.fallbacks = true

  # Send deprecation notices to registered listeners.
  config.active_support.deprecation = :notify

  # Use default logging formatter so that PID and timestamp are not suppressed.
  config.log_formatter = ::Logger::Formatter.new

  # Use a different logger for distributed setups.
  # require 'syslog/logger'
  # config.logger = ActiveSupport::TaggedLogging.new(Syslog::Logger.new 'app-name')

  if ENV["RAILS_LOG_TO_STDOUT"].present?
    logger           = ActiveSupport::Logger.new(STDOUT)
    logger.formatter = config.log_formatter
    config.logger = ActiveSupport::TaggedLogging.new(logger)
  end

  # Do not dump schema after migrations.
  config.active_record.dump_schema_after_migration = false

end```

Hi Youssef, thanks for using the gem!
Do you have a link to your Heroku app I could look at please? I need to know if the gem isn't working at all, or whether its assets are not loading correctly.
Looking forward to your response!

Hi Richard
Thanks for your reply.
What is your email address so I can create a login for you
Youssef
On Tue, May 23, 2017 at 2:06 AM, Richard Peck<EMAIL_ADDRESS>wrote:

Hi Youssef, thanks for using the gem!
Do you have a link to your Heroku app I could look at please? I need to
know if the gem isn't working at all, or whether its assets are not loading
correctly.
Looking forward to your response!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/richpeck/exception_handler/issues/50#issuecomment-303299269,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACeEHV_mCf2fBzAWToM39xqa7PCdYSIrks5r8ndigaJpZM4NjBZQ
.

<EMAIL_ADDRESS>
On 23 May 2017 at 19:12 yislah<EMAIL_ADDRESS>wrote:
Hi Richard

Thanks for your reply.
What is your email address so I can create a login for you

Youssef

On Tue, May 23, 2017 at 2:06 AM, Richard Peck<EMAIL_ADDRESS>wrote:

> Hi Youssef, thanks for using the gem!
>
> Do you have a link to your Heroku app I could look at please? I need to
> know if the gem isn't working at all, or whether its assets are not loading
> correctly.
>
> Looking forward to your response!
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/richpeck/exception_handler/issues/50#issuecomment-303299269>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACeEHV_mCf2fBzAWToM39xqa7PCdYSIrks5r8ndigaJpZM4NjBZQ>
> .
>

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/richpeck/exception_handler/issues/50#issuecomment-303486136 , or mute the thread https://github.com/notifications/unsubscribe-auth/ABDaL6hTpjR8KkvLtNetca0PlcvmUNdzks5r8yGbgaJpZM4NjBZQ .

Hi Richard
It is working now in production. I found the culprit.
I commented out these lines in config/production.rb and then it worked
#config.exception_handler = {
email<EMAIL_ADDRESS>#}
Do you see anything wrong with that. I thought it could send email when
there is an error ?
Thanks
Youssef
On Tue, May 23, 2017 at 2:26 PM, Richard Peck<EMAIL_ADDRESS>wrote:

<EMAIL_ADDRESS>
On 23 May 2017 at 19:12 yislah<EMAIL_ADDRESS>wrote:
Hi Richard
Thanks for your reply.
What is your email address so I can create a login for you
Youssef
On Tue, May 23, 2017 at 2:06 AM, Richard Peck<EMAIL_ADDRESS>wrote:

Hi Youssef, thanks for using the gem!
Do you have a link to your Heroku app I could look at please? I need to
know if the gem isn't working at all, or whether its assets are not
loading
correctly.
Looking forward to your response!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/richpeck/exception_handler/issues/50#
issuecomment-303299269>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACeEHV_
mCf2fBzAWToM39xqa7PCdYSIrks5r8ndigaJpZM4NjBZQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/richpeck/exception_handler/issues/50#
issuecomment-303486136 , or mute the thread https://github.com/
notifications/unsubscribe-auth/ABDaL6hTpjR8KkvLtNetca0PlcvmUN
dzks5r8yGbgaJpZM4NjBZQ .

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/richpeck/exception_handler/issues/50#issuecomment-303489888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACeEHcF-QgezbGUV1Tq15K_CukH3G928ks5r8yTqgaJpZM4NjBZQ
.

Hmm never had this before. Did you have any errors returned by Heroku when you deployed?

No at all
Thanks]
Youssef
On Tue, May 23, 2017 at 3:44 PM, Richard Peck<EMAIL_ADDRESS>wrote:

Hmm never had this before. Did you have any errors returned by Heroku when
you deployed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/richpeck/exception_handler/issues/50#issuecomment-303510725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACeEHXgmg1XK3xlmI2XTFnKjQZQNwLvSks5r8zcdgaJpZM4NjBZQ
.

That's strange. I'm going to have to check this email bug because it worked for me some time ago. Do you have a repo I could look at for it?

I am using this
https://github.com/projectblacklight/blacklight
On May 23, 2017 3:54 PM, "Richard Peck"<EMAIL_ADDRESS>wrote:

That's strange. I'm going to have to check this email bug because it
worked for me some time ago. Do you have a repo I could look at for it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/richpeck/exception_handler/issues/50#issuecomment-303513386,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACeEHUQo4l4Ht652a89_AVUveFqupfewks5r8zmMgaJpZM4NjBZQ
.


resource version reset default when event object resource version inv…

Watch an API resource and stream the result back via a generator, when resource_version specified,  may be cause "too old resource version" error, then result would be:
{     "type":"ERROR",     "object":{         "kind":"Status",         "apiVersion":"v1",         "metadata":{         },         "status":"Failure",         "message":"too old resource version: 38081900 (64845263)",         "reason":"Gone",         "code":410     } }
In this case, the func unmarshal_event can not parse the right  resource version, actually is None,
the stream while loop continue, the next request will get ApiException: (500) error:
HTTP response headers: HTTPHeaderDict({'Content-Length': '186', 'Content-Type': 'application/json', 'Date': 'Fri, 19 Jun 2020 06:21:06 GMT'}) HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"resourceVersion: Invalid value: \\"None\\": strconv.ParseUint: parsing \\"None\\": invalid syntax","code":500}\n'

@yliaog

Codecov Report

Merging #199 into master will increase coverage by 0.42%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #199      +/-   ##
==========================================
+ Coverage   92.23%   92.66%   +0.42%
==========================================
  Files          13       13
  Lines        1481     1554      +73
==========================================
+ Hits         1366     1440      +74
+ Misses        115      114       -1

Impacted Files
Coverage Δ

watch/watch.py
100.00% <100.00%> (ø)

config/kube_config.py
83.29% <0.00%> (-0.20%)
:arrow_down:

config/kube_config_test.py
95.76% <0.00%> (+0.16%)
:arrow_up:

config/incluster_config_test.py
97.84% <0.00%> (+0.55%)
:arrow_up:

config/incluster_config.py
95.45% <0.00%> (+10.34%)
:arrow_up:

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 b87a5fe...8b57234. Read the comment docs.

kubernetes version：v1.14.6

/cc


Generate human-readable IDs for elements of LIonCore/M3

The IDs of (a self-definition of) LIonCore/M3 should be stable (so they can be used consistently) and human-readable (so the serialization of a metamodel can be inspected meaningfully on its own).

Done by PR #25


Nohive WIP

nice find. looks good, do we need to run the cq script?

Good call.  Doing that now.....

did the build pass the first time? I'll merge if so, if we're not sure I'll wait for travis. @jnh5y I'll add a sign-off by you, if that's ok

@elahrvivaz it looks like it did build both times.  Feel free to add the sign-off and shippit!


Visual Studio theme

I suggest adding a theme from Visual Studio in the themes for the editor. Because a lot of people are used to working there!

I think I already have a look!


React publish 404

I'm trying to publish to my local IIS the initial react app that is generated with dotnet new react and I am getting 404 not found for the static files. The index.html loads but is blank. Looking at the index.html that is generated it is pointing to /static/js/main.5aa7d1c0.js which seems weird to me because they are within ClientApp\build\ directory. Can anyone help point me in the right direction? Thanks in advance.
I am running dotnet core 2.0 and using the latest react template found here: Microsoft.DotNet.Web.Spa.ProjectTemplates::2.0.0

Could you provide repro steps? Example: what sequence of steps in the command line or VS UI are you using to publish the app to your local IIS instance?


Issues with installation one-liners

I'm having issues with the Curl one-liners:
▶ sudo curl -L  "https://github.com/redhat-developer/odo/releases/download/v0.0.6/odo-linux-amd64.gz" | gzip -d > /usr/local/bin/odo; chmod +x /usr/local/bin/odo

zsh: permission denied: /usr/local/bin/odo
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   609    0   609    0     0   2009      0 --:--:-- --:--:-- --:--:--  2009
  0 7759k    0 16360    0     0  28802      0  0:04:35 --:--:--  0:04:35 80990
curl: (23) Failed writing body (0 != 16360)
chmod: cannot access '/usr/local/bin/odo': No such file or directory

I've removed /usr/local/bin/odo (old odo).
I've google'd around and found people with similar issues (https://github.com/kubernetes/helm/issues/2802)
Why do we have to download tarballs and worry about using gzip? Can we just download the binaries directly from GitHub?

For someone with slow internet, 28 MB vs 8 MB can mean a huge difference.
The problem with the command is that the pipe is not executed as root, it is performed in the users shell.
We have to run the whole command in the same shell under sudo.
sudo sh -c 'curl -L  "https://github.com/redhat-developer/odo/releases/download/v0.0.6/odo-linux-amd64.gz" | gzip -d > /usr/local/bin/odo; chmod +x /usr/local/bin/odo'

Interesting is that on macOS original command works. But in Linux you have to wrap it whole in the shell as I mentioned.

Could we instead include options for downloading either the binary or a tarball? @kadel

Fixed in https://github.com/redhat-developer/odo/pull/526

I think this can be closed since we merged #526


ngx-translate is not working  in *ngfor

Current behavior
ngx-translate is not working in ng-for
Expected behavior
it has to work
Minimal reproduction of the problem with instructions
if i use like below it won't work:
<e-column *ngFor="let a of array"         field="ImplantationDate"         headerText="{{ a | translate }}">       </e-column>
where arry valyue is
array = ['one,'two,'three'];
but if i use one value it is working fine
<e-column         field="ImplantationDate"         headerText="{{ a | translate}}">       </e-column>
sample
download this sample and run below commands

npm i
ng serve

sample:  http://www.syncfusion.com/downloads/support/directtrac/general/ze/SAMPLE_FOR_SYNCFUSION-1886628965
Environment
"@ngx-translate/core": "10.0.1",
"@ngx-translate/http-loader": "3.0.1",
"ngx-bootstrap": "2.0.5",
"ngx-infinite-scroll": "6.0.0",
Angular version: 6.0.0

Browser:

[ ] Chrome (desktop) version XX
[ ] Chrome (Android) version XX
[ ] Chrome (iOS) version XX
[ ] Firefox version XX
[ ] Safari (desktop) version XX
[ ] Safari (iOS) version XX
[ ] IE version XX
[ ] Edge version XX

For Tooling issues:

Node version: XX  <!-- run node --version -->
Platform:

Others:

Hi
Any update on this?

Hello,
is there anybody working on this organization????

bump


fix requirements

Related to issue #7
This  won't fix the issue (not yet, at least)

I just noticed this was marked as a  "work in progress", but it's ready to be merged.
The linked issue states the needed steps, which include merging this PR, releasing a new minor, and then applying other needed changes (which need to be in a separate PR)


Possibility of changing the key

Hey I'm french so I have an AZERTY keyboard that make my "z" key the key for move forward is it possible to make a thing that allows you to change the keybind please ?

Hey @Henonnnn,
I haven't played Raft in years.  @made-by-traxam maintains a more up-to-date fork here:
https://github.com/made-by-traxam/RaftModSortInventory
You may want to create an issue there.  If you have VisualStudio and have the ability to compile it yourself, you could change the keybind on this line:
https://github.com/made-by-traxam/RaftModSortInventory/blob/cfe4026881535912c27dbeffeaba67d9fb4a1df4/SortInventory/SortInventoryMod.cs#L16
Hope this helps!


Fix scroll offset in paging sample

Updates paging to stable release from rc + adds a workaround which fixes the scroll offset addressing #659

The observer for posts in RedditActivity is called only once when Activity opens (submitList is called only once). If network is not available and activity is opened, clicking on retry won't execute the fix for scroll.


Add Fine tune option + refactoring

Add fine-tune options and refactor the action such that it takes arguments for rasa test nlu and rasa test core separately. We want this because rasa test alone could not pick up the core and nlu specific arguments.

[X] Add fine-tune argument fine-tune and default to true
[X] Add train_type argument
Now we can set the types for training and testing separately. For example, we can train core and nlu, but test on nlu alone.
[X] Deprecate test_args -> Now we have test_nlu_args and test_core_args
[X] Update README.md about all the changes
[X] Update CI

@tczekajlo this PR is ready for review 🥳. I documented all changes that I made in the very first comment. Please 👀 when you have time.


NVS from un-encrypted to encrypted Flash (IDFGH-12566)

Answers checklist.

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

General issue report
I want to migrate my currently installed ESP32-S3 based devices from un-encrypted flash to encrypted flash. It is not feasible to do this manually, I need the procedure to happen in a single OTA update process.
What I achieved in tests so far:

working flash encryption in general
bootloader update

Problem:
NVS partition with existing custom data needs to be migrated as well. Once the NVS partition is initialised encrypted it cannot read the previously stored data (un-encrypted) anymore.
What is the best process for this?

you cannot update the partition table remotely, hence it will be hard to add the nvs keys partition, also flash encryption must be enabled for bootloader too, if I'm not mistaken.

We already implemented the OTA update for partition table and bootloader. That works fine. The only missing is the migration of the NVS partition, in particular, its content.

Hi @mgoeller,
Update an NVS partition from non-encrypted state to encrypted state via OTA is not supported. As if you need to encrypt the NVS partition, you need to read all the entries and then write them in another NVS partition which has been initialised with nvs_secure_flash_init_partition() ( which initialises the partition as encrypted).
So I think the workflow to update the encrypted partition from non-encrypted would be as follows:

Update the partition table to add one more nvs_partition and one nvs_keys partition.

We shall first store the NVS encrypted data in this new partition and then use this new partition as the default NVS partition by updating the partition table.

There shall be 2 OTA, first OTA shall add a new NVS partition, initialise it with nvs_secure_flash_init_partition() ( which initialises the partition as encrypted) and then copy all the contents from the current NVS partition into the new NVS partition. For copying the contents from non-encrypted to encrypted NVS partition, the API nvs_entry_next could be used

The second OTA shall update the partition table once again to make this new NVS partition as the default one and erase the non-encrypted one.
(Could also be done in a single OTA but I think it would be less reliable.)

It seems like it's possible to encrypt the NVS partitions with the same key as the rest of the flash. Why is this not advised / no-where mentioned by Espressif? See here: https://www.esp32.com/viewtopic.php?t=28715

Hi @mgoeller, I checked the forum post. Technically it may be possible to use flash encryption key directly for NVS encryption but it is not as straightforward as it seems. As explained in the thread NVS contains some data that must not be encrypted and some data that needs to be encrypted.
It would require following conditions for it to work.

Flash encryption is enabled on the device
While enabling flash encryption the data in NVS which must not be encrypted is kept as it is kept as plaintext and only other data is encrypted or NVS partition is completely empty.
NVS partition is marked as encrypted so esp_partition* APIs directly utilise flash encryption key for writing and reading the data.

However this is not directly supported in esp-idf.
In esp-idf when flash encryption is enabled through bootloader, the bootloader encrypts all the partitions which are marked as encrypted. So if an NVS partition exists then we somehow need to tell the bootloader to only encrypt the necessary data and keep the data that must not be encrypted as plaintext. This part is not currently present in the bootloader. This part may add additional complexity in the bootloader which may not be required at the moment.
Additionally this would cause an issue when one wants to generate the encrypted NVS partition outside of the device. For this they would need to use the Flash Encryption key outside of the chip which is not recommended. Usually it is generated internally and then stored with R/W protection enabled.
As this deviates from the standard workflow that are in place for NVS. It has not integrated in esp-idf at the moment.
For your case, the NVS partition already contains the data. If you plan to use the FE key for NVS then following things would change

You would need to first read the plaintext NVS and then write then write that data into a new NVS partition which has been marked as encrypted. This way the non-encrypted data should be handled internally by NVS
Make the new nvs partition as the default NVS through updating the partition table.
This would remove the requirement of nvs_encryption keys and thus save 1 flash sector size of 4K.

But as I see this is pretty much the same compared to the above just with the addition of a new key. So I would recommend using the standard NVS encryption mechanism.
CC @igrr

Hi @mgoeller Have you had time to go through the suggestions?

Hi @mgoeller,
Closing this issue since the question seems to be answered, please feel free to re-open if required.
Thanks,
aditya


The example infinite-scroll loads page 1 from github 3 times instead loading it once.

Bug report
Description / Observed Behavior
The example infinite-scroll loads page 1 from github 3 times.
Edit: Also loads page 1 again and again on scroll.
Expected Behavior
The example infinite-scroll loads page 1 from github exactly once.
Repro Steps / Code Example
https://github.com/vercel/swr/tree/main/examples/infinite-scroll
https://jjlkjlkjkl.vercel.app/
Additional Context
https://github.com/vercel/swr/blob/main/examples/infinite-scroll/package.json

Probably not a bug. revalidateFirstPage = true


Custom $PATH for a specific machine

Hi, I put the custom directory under VCS.
The problem is that I have several machines which are set up differently.
So I would like to custom the PATH on different machines. So I don't want to directly modify the .zshrc file.
But the customization of PATH I introduced under custom directory would be overwritten by .zshrc due to the order.
I can get around this issue by moving PATH=blah blah  before setting the path to the custom directory.
May I know whether this would introduce any side effects?
Thanks!

Hey can you close this? Did I solve your doubts?

Yes, sure. Thanks!


Stuck on infinite look upon revoked refresh_token

This needs better error handling

fixed in https://github.com/rocktimsaikia/spotify-mini/commit/8a266dcc2c0dad88f137dd5cca22546a422ae755


Doesn't build on sparc64 anymore

error[E0573]: expected type, found function `statfs64`
   --> /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.30/src/unix/notbsd/mod.rs:880:54
    |
880 |     pub fn statfs64(path: *const ::c_char, buf: *mut statfs64) -> ::c_int;
    |                                                      ^^^^^^^^ did you mean `stat64`?
error[E0573]: expected type, found function `statfs64`
   --> /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.30/src/unix/notbsd/mod.rs:882:45
    |
882 |     pub fn fstatfs64(fd: ::c_int, buf: *mut statfs64) -> ::c_int;
    |                                             ^^^^^^^^ did you mean `stat64`?
error[E0573]: expected type, found function `statvfs64`
   --> /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.30/src/unix/notbsd/mod.rs:883:55
    |
883 |     pub fn statvfs64(path: *const ::c_char, buf: *mut statvfs64) -> ::c_int;
    |                                                       ^^^^^^^^^ did you mean `statvfs`?
error[E0573]: expected type, found function `statvfs64`
   --> /cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.30/src/unix/notbsd/mod.rs:884:46
    |
884 |     pub fn fstatvfs64(fd: ::c_int, buf: *mut statvfs64) -> ::c_int;
    |                                              ^^^^^^^^^ did you mean `statvfs`?

Travis Job

Looks like it's fixed on master.


Animating the tooltip

I love the animation of the tooltip you have, where it comes from the last known position to the current mouse position. Could you share how you did that?
I implemented a similar tooltip for a chart I made which uses d3-force simulation to generate the animated tooltip moving from the last known position to the current mouse position
http://marketdepth.reactstockcharts.org.s3-website-us-east-1.amazonaws.com/index.html
but here, the tooltip moves like an elastic, where it moves beyond the mouse position and then dampens  back to the right position. Just curious to see what you have used.

I am using the opensource EChart , you can find its repo for more detail. :)

@rrag I have updated a minimal demo for it , tooltip-demo repo.


New version of preact signals for react not working with React Native

In my RN apps, preact signals not working. Previous implementation wasn't working because of navigation.
 ERROR  TypeError: Cannot read property 'alternate' of null

This error is located at:
    in NativeStackNavigator (created by App)
    in EnsureSingleNavigator
    in BaseNavigationContainer
    in ThemeProvider
    in NavigationContainerInner (created by App)
    in QueryClientProvider (created by PersistQueryClientProvider)
    in PersistQueryClientProvider (created by CacheProvider)
    in CacheProvider (created by App)
    in App (created by gestureHandlerRootHOC(App))
    in RNGestureHandlerRootView (created by GestureHandlerRootView)
    in GestureHandlerRootView (created by gestureHandlerRootHOC(App))
    in gestureHandlerRootHOC(App)
    in RCTView (created by View)
    in View (created by AppContainer)
    in RCTView (created by View)
    in View (created by AppContainer)
    in AppContainer
    in oone_drive(RootComponent), js engine: hermes

However its working in expo snack: https://snack.expo.dev/@xantregodlike/funny-pretzel?platform=android
This issue is not reproducing event in pure react native starter. I think it can be related with some external libraries. When i will detect which one is causing this issue - it will add reproduce steps

@andrewiggins

Signals is working in pure repo. So we will investigate more about it

I'm having the same issue

The solution for it is to roll back to 1.2.1 and apply a little patch (if you are using react-navigation) #257

#257

same here

I get the same error in a plain React app with vite -m production build. Works fine with vite

Same for me with fresh Expo project, signals v1.2.2 works though

I'm checking diff between 1.2.2 and 1.3.0 and... I'm not exactly sure yet but it might be related that signals >=v1.3.0 started to use __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED from react package
https://github.com/preactjs/signals/compare/%40preact/signals-react%401.2.2...%40preact/signals-react%401.3.0

Hint, hint? __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED Fired!

Seems to be one of the reason - wrong function serialization
 LOG  useCallbackImpl function throwInvalidHookError() { [bytecode] }
 LOG  useCallbackImpl function useCallback(a0, a1) { [bytecode] }
 LOG  useCallbackImpl function useCallback(a0, a1) { [bytecode] }
 LOG  useCallbackImpl function useCallback(a0, a1) { [bytecode] }
 LOG  function bebe() { [bytecode] }
 LOG  useCallbackImpl function useCallback(a0, a1) { [bytecode] }

This is not bug - this the feature
https://github.com/facebook/hermes/issues/114
They are added 'show source' to actually check function code

We actually can actually patch react-native, but there are many renderers (react-native-skia, three-fiber). I think its blocker in terms of React Native support.
Can we give user opportunity to select auto tracking method, because old auto tracking via wrapping each component with proxy working very well in case of react native.
@andrewiggins What do you think?

I'm currently pursuing a method that would use a babel transform on components to track signals instead of patching internals. That should hopefully work better for all renderers. PR for feedback should be out soon (a couple days).

It would be really interesting. Appreciate your work

@andrewiggins
Can i create PR to add information for docs how to use preact signals in react native?

I couldn't even get v1.2.0 to work with my Expo setup, so I ended up just going with Jotai just to get something that works right now:
https://jotai.org/docs/guides/react-native
It's not ideal and not as clean, but it works for now, especially since it's a new project, and you can't wait for an official patch.

@andrewiggins when real way to use babel transform will be provided?

Initial version of babel transform is available at https://npm.im/@preact/signals-react-transform Give it a try and lemme know how it goes.

But how to use it?). We should install @preact/signals-core and write useSignal, useComputed..., manually? If we will use @preact/signals-react it will patch react and broke the app. In case of pnpm we can produce preact signals runtime duplication, because we should install @preact/signals-react and @preact/signals-react-transform will have its own version of @preact/signals-react

The documentation for @preact/signals-react-transform implies that it's not possible to opt into the "bypass VDOM" optimization. Yes?
Perhaps a step back to a simplified approach where there's no patching React? Instead, provide a simple component that can do the optimization? <Signal $={mySignal} />? Add yet another library: @preact/signals-react-plain?

Perhaps a step back to a simplified approach where there's no patching React? Instead, provide a simple component that can do the optimization? <Signal $={mySignal} />?

How would this work? The issue resides in React's reconciler, any special component you make is subject to the reconciler just as every other component is.

@andrewiggins what do you think about my concerns?


Support custom package name

Add support for setting a custom package name.

@tdevelioglu official puppetserver package name is the same on all supported platforms. Are you rebuilding your own packages?

@mcanevet you are correct. In this case we rebuild because we need modified dependencies.

@tdevelioglu ok. Could you please squash your commits?

@mcanevet sure, done

@tdevelioglu thanks