cmd/compile: constant inlining happens even when disabling inlining and optimizations

What version of Go are you using (go version)?
go1.13.4
Does this issue reproduce with the latest release?
I haven't tried with Go 1.14 yet
What operating system and processor architecture are you using (go env)?
windows/amd64
What did you do?

use the code at https://github.com/dlsniper/democonstdbg
use the latest Delve version from master
place a breakpoint on line 23
evaluate the following expression:

ot == AnotherConst

What did you expect to see?
A boolean result
What did you see instead?
could not find symbol value for AnotherConst

Non-integer constants are never exported to debug_info, it doesn't have anything to do with whether they are inlined or not. Also, I'm not sure it's worth the executable bloat costs, since IIRC there was no way to reuse t
@gopherbot please add label Debugging

Thanks for the explanation.
The problem was reported to GoLand by a user that had a similar code like the one above.
It's rather common to run a compare operation like this. For example, I use this to setup conditional breakpoints. Also, not everyone will know ahead of time that one is a constant or not when making the comparison, nor suggesting to change the code would be possible.
I'm not sure if https://github.com/go-delve/delve/issues/1753 is related or not.

@aclements

When I debug this code:
https://github.com/adonovan/gopl.io/blob/65c318dde95e3b46a0add461ccf681bd5345b67c/ch1/lissajous/main.go#L69
and hover at the constant variables, the value doesn't appear.
I have to find the definitions what exactly the value is.

@kzhui125 that doesn't have anything to do with this issue and should be reported to GoLand.

I am using VSCode, I have reported this issue in vscode-go extension. I was told this is upstream issue. @aarzilli
https://github.com/microsoft/vscode-go/issues/3226

You're right, I was confusing this with a different issue.

I wonder if that's the issue I'm experiencing...
$ git clone https://github.com/docker/compose
$ cd compose
$ dlv debug github.com/docker/compose/v2/cmd -- up
Type 'help' for list of commands.
(dlv) b /home/yuri/go/pkg/mod/github.com/compose-spec/compose-go/v2@v2.0.0-beta.2/cli/options.go:260
Breakpoint 1 set at 0x199cc8e for github.com/compose-spec/compose-go/v2/cli.WithEnvFiles.func1() /home/yuri/go/pkg/mod/github.com/compose-spec/compose-go/v2@v2.0.0-beta.2/cli/options.go:260
(dlv) c
> github.com/compose-spec/compose-go/v2/cli.WithEnvFiles.func1() /home/yuri/go/pkg/mod/github.com/compose-spec/compose-go/v2@v2.0.0-beta.2/cli/options.go:260 (hits goroutine(1):1 total:1) (PC: 0x199cc8e)
   255:         return func(o *ProjectOptions) error {
   256:                 if len(file) > 0 {
   257:                         o.EnvFiles = file
   258:                         return nil
   259:                 }
=> 260:                 if v, ok := os.LookupEnv(consts.ComposeDisableDefaultEnvFile); ok {
   261:                         b, err := strconv.ParseBool(v)
   262:                         if err != nil {
   263:                                 return err
   264:                         }
   265:                         if b {
(dlv) p consts.ComposeDisableDefaultEnvFile
Command failed: could not find symbol value for consts

Are there any workarounds?

@aarzilli (I didn't remember the part about non-integer constants when I was posting the message.)
Can you possibly explain why non-integer constants are not exported? C for one doesn't seem to have problems with them.

Can you possibly explain why non-integer constants are not exported?

They just aren't.

I've retitled this issue because it's unrelated to inlining. Really this is a feature request for the compiler to include non-integer constants in the debug info. Once we do that, debuggers will be able to access them.


No rendering at all

Each time I try to open a PDF file, I receive this exception
Erreur : localStorage is null
Fichier Source : chrome://pdf.js/content/web/viewer.js
Ligne : 93

Hi, can you please specify your browser version?

Hi, I tried with :
FF 9.0.1
Aurora 11.0a2
Nightly (x64) 12.0a1
Win7 X64 Sp1

Maybe you have local storage disabled? check about:config, the dom.storage values

You were right, the dom.storage.enabled value was false.

Maybe it would have been nice to have this issue for the devs to know pdf.js does not warn users about the local storage requirement?

Definitely. I'm looking into this.


[FEATURE REQUEST] Implement Active CMA-ES

Description
Currently, the CMA-ES implementation doesn't support negative weights. Implement this feature.
Note: some thought is required for filter-based selection.

Does this relate to parameter "weight_rule" (either "truncation" or "active") in the CMA-ES-based emitters? I am trying to determine the implications of setting it to "active", but could not understand the limited documentation or make sense of the code. It looks like these emitters can generate negative values even with "weight_rule" set to "truncation", so what is the purpose of it?

Correct, this relates to setting weight_rule="active". This would correspond to leveraging active CMA-ES https://hal.archives-ouvertes.fr/hal-00503250/document such that we update the covariance matrix based both on solutions that were inserted into the archive and solutions that were not inserted into the archive. Currently, weight_rule="active" is actually not implemented (I think you will eventually get an error if you use this option) -- hence why we raised this issue.


:bug: Update the "new bug" template

Remove the old instructions for specific KS info collection, these instructions are not suitable for the new KS. For now, the general template asking for bug description, logs, and expected behavior is good enough.

Summary
Related issue(s)
Fixes #

This should fix issue #2224


My Skyblock Map - question

hello sorry if I write you here but I don't know where I can contact you.
I need help with my map and datapack. basically I would need a system that detects players (I have if there is a server) when I enter the world. but there are some problems:

the first problem is that I used scoreboards to manually "generate" islands or structures in the world. so I have to block (by setting -1 in all scores) in the various scores.
the second problem is that the map must work both in singleplayer and in multiplayer. so it's the datapack that needs to figure out if you're into singleplayer or multiplayer.
I tried to use some tags but it doesn't solve the second problem, I hope you help me and ask me anything that interests you.
Thank you

this is the affected function:
`
##Multiplayer Setup
execute as @a[gamemode=spectator,scores={multiplayer=1}] run gamemode survival @a
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_install -1
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_islands -1
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_id 14000
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_islands 1
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_islands 2
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_islands 3
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_large 1400
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_default 1400
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_small 1400
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a SkyblockCE_structures 14000
execute as @a[scores={multiplayer=1..}] run scoreboard players set @a PSN_OLD -1
execute as @a[scores={multiplayer=5}] run setblock 0 62 0 minecraft:black_concrete
execute as @a[scores={multiplayer=5}] run tp @s 0 65 0 0 0
execute as @a[scores={multiplayer=5}] run gamemode survival @s
execute as @a[scores={multiplayer=5}] run fill 0 63 0 0 64 0 minecraft:air destroy
execute as @a[scores={multiplayer=5}] run spawnpoint @s 0 63 0
execute as @a[scores={multiplayer=5}] run setworldspawn 0 63 0
execute as @a[scores={multiplayer=6..}] run scoreboard objectives remove multiplayer_popup
execute as @a[scores={multiplayer_popup=200}] run tellraw @a ["",{"translate":"skyblock_classic_edition.multiplayer.popup","italic":true},{"text":""Skyblock Classic Edition\datapacks\Skyblock Classic Edition\data\skyblock\functions\multiplayer.mcfunction"","italic":true,"underlined":true,"clickEvent":{"action":"copy_to_clipboard","value":""Skyblock Classic Edition\datapacks\Skyblock Classic Edition\data\skyblock\functions\multiplayer.mcfunction""}}]
execute as @a[scores={multiplayer_popup=5000000..}] run scoreboard players set @a multiplayer_popup 0
##Server or Multiplayer (Only activate if you are in multiplayer: here below)
#scoreboard objectives add multiplayer dummy`

#scoreboard objectives add multiplayer dummy
must be manually removed otherwise the function does not work.

Sorry, I don't really have time to look into your issue, nor is this supposed a place to ask for command help :)
I recommend the MinecraftCommands Discord, it's a great place to get help with all kinds of mapmaking problems: https://discord.gg/QAFXFtZ

OK thanks anyway


pwsh 7.20 fails to start on Windows 11 Pro Insider Preview Build

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Install PowerShell 7.20 using the MSI package on Windows 11.
Try to start PowerShell 7.20 either by executing pwsh or by using Windows Terminal.
Expected behavior
PowerShell 7.2.0
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

Actual behavior
Failed to create CoreCLR, HRESULT: 0x80004005

[process exited with code<PHONE_NUMBER> (0x80008089)]

Error details
PowerShell 7.20 does not start.

Environment data
Windows 11 Insider Preview Build 22489.
PowerShell 7.20 release version.

Visuals
Launch pwsh after installing PowerShell 7.20.

Did you try to run as admin?
I am having similar issue on windows 10, after installing pwsh 7.2.
My pwsh doesn't show anything as a normal user (except the blinking cursor). But works fine when it's run as admin.

It works fine on Windows 10 release and Windows 10 insider builds.
On the Windows 11 build mentioned above, I executed pwsh from a cmd window running as administrator (the account I am using is a local administrator as well) and still get the same error.

Insider Preview Build

I think it is better to report with Feedback tool to Windows team as a bug in Windows 11 Preview.

Insider Preview Build

I think it is better to report with Feedback tool to Windows team as a bug in Windows 11 Preview.

Disagree with the recommendation.
As we are using artifacts from this github repo, then why to report issues via Windows Feedback tool?
That's ok if the update were to come in via Windows update.
Please help in addressing this issue.
Thank you

error on win10 pro
Environment
PSReadLine: 2.2.0-beta2
PowerShell: 7.2.0
OS: Microsoft Windows 10.0.19043
BufferWidth: 120
BufferHeight: 30
Last 0 Keys

Exception
System.TypeLoadException: Could not load type 'System.Management.Automation.Subsystem.PredictionResult' from assembly 'Microsoft.PowerShell.PSReadLine.Polyfiller, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
   at Microsoft.PowerShell.PSConsoleReadLine.PredictionViewBase.Reset()
   at Microsoft.PowerShell.PSConsoleReadLine.PredictionInlineView.Reset()
   at Microsoft.PowerShell.PSConsoleReadLine.Prediction.Reset()
   at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics)
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)

@IoTFier @micahgoodreau You say about another issue - you should update PSReadline to latest Beta4 version.

@IoTFier @micahgoodreau You say about another issue - you should update PSReadline to latest Beta4 version.

I tried to follow steps outlined here - https://github.com/PowerShell/PowerShell/issues/16422#issuecomment-965204089
But, powershell doesn't show the command prompt.
Any steps that your recommend for updating PSReadline to latest Beta4 ?
I thought Powershell 7.2 is not in the beta any more. This is has messed up stable 7.1.x environment on my couple of PCs.
Please help.

@IoTFier and @micahgoodreau, the issue you reported here is unrelated to the original issue opened by @mazhar10, so I hided your comments as "Off Topic".
For your issues, please see https://github.com/PowerShell/PSReadLine/issues/3001#issuecomment-965569302 for fixes, and https://github.com/PowerShell/PSReadLine/issues/3001#issuecomment-966568775 for why it happened to you.

@iSazonov Let's keep this one open for now, and keep an eye on any incoming similar reported.

Failed to create CoreCLR, HRESULT: 0x80004005

@daxian-dbw I guess it is known issue - pwsh cannot create a named pipe or something else in user temp folder.

Did you try to run as admin? I am having similar issue on windows 10, after installing pwsh 7.2. My pwsh doesn't show anything as a normal user (except the blinking cursor). But works fine when it's run as admin.

Same here. On Windows 10, I just updated to 7.20 - I just get a blinking cursor as a normal user but it works fine when run as admin. This is a big breaking change.

Did you try to run as admin? I am having similar issue on windows 10, after installing pwsh 7.2. My pwsh doesn't show anything as a normal user (except the blinking cursor). But works fine when it's run as admin.

Same here. On Windows 10, I just updated to 7.20 - I just get a blinking cursor as a normal user but it works fine when run as admin. This is a big breaking change.

I did try it on Windows 11 as admin, same issue with "Failed to create CoreCLR" message.

@asishm-wk from your description, it doesn't seem to be same issue reported here -- what @mazhar10 observed is that pwsh crashed with a CLR exception.
Can you open a new issue with detailed information of what you observed? Please also provide screenshot if possible.

@mazhar10 This CLR exception happens usually when CLR failed to create the named pipes for debugging and profiling in the TMP folder, see details in https://github.com/PowerShell/PowerShell/issues/13166#issuecomment-660358397.
Can you try disabling CoreCLR diagnostics by setting the environment variable export COMPlus_EnableDiagnostics=0 (as instructed here), and then try running your repro step again to see if that helps?

@mazhar10 This CLR exception happens usually when CLR failed to create the named pipes for debugging and profiling in the TMP folder, see details in #13166 (comment).
Can you try disabling CoreCLR diagnostics by setting the environment variable export COMPlus_EnableDiagnostics=0 (as instructed here), and then try running your repro step again to see if that helps?

I tried that with no joy. Here is what I did:
open a command window.
Execute: set COMPlus_EnableDiagnostics=0
Execute: start pwsh.
pwsh fails with the reported error.
The results are the same if the cmd window is opened as an administrator..

@mazhar10 What is temp directory in the user session? Can you confirm the user has full permissions to the directory and there is no security application blocking operations on the temp directory?

@mazhar10 What is temp directory in the user session? Can you confirm the user has full permissions to the directory and there is no security application blocking operations on the temp directory?

The temp directory for the user session is %appddata%..\Local\temp.
There is nothing blocking operations to this directory - as the user, I can edit, delete files and subdirectories under temp just fine.

@mazhar10 Can you collect .NET startup traces and share the trace file here?
From CMD.exe
set COREHOST_TRACE=1
set COREHOST_TRACEFILE=host.txt
<Run pwsh 7.2>
set COREHOST_TRACE=0

This should produce host.txt with lot of detailed tracing. Please note that the file may contain information about the machine, local paths and env. variables. Make sure you're OK to share it first. I think the interesting part will be the few lines around the failure (should be near the end of the file).

Opened https://github.com/dotnet/runtime/issues/61740. We will see what the .NET team say about this crash.

I think they need the process dump. And I assume it's because of an unsupported CPU.

7.2.1 works fine.

@mazhar10 Thanks for reporting back. It could be something fixed in .NET 6.0.1, which is what PS 7.2.1 based off.


Pre-define namespaces in config

Is your feature request related to a problem? Please describe.
It's a pain to have to remember all my available namespaces when I lack access to see available nasespaces.
Describe the solution you'd like
Add a config option to input available namespaces which will be available to select from. Extra bonus if it's possible to override these values for specific contexts, also through the config.
Describe alternatives you've considered
kubectl.nvim can remember previously input namespaces inside of a certain context and show them the next time the user changes namespace.
Additional context
With a quick additional config, "Only show user-defined namespaces", which should obviously be toggleable in the config, this feature can also be useful to users with access to view all namespaces but who only use a fraction of the available namespaces.

Yea that works well enough for my setup, thank you!


[1.5pt] Create the navigation pannel - GROUP TASK

In the navigation panel, the user can see links to:

Items that you selected as a theme.
"Reserve" form.
"My reservations".
" Add item" that you selected as a theme (the link is visible to everybody).
"Delete the item" that you selected as a theme (the link is visible to everybody).


build: builders for alternate buildmodes?

For -buildmode=shared on linux/386, @mwhudson's current set of patches would borrow the CX register. This seems reasonable to me, but means that assembly that works under -buildmode=exe will not work under -buildmode=shared (see the discussion on http://golang.org/cl/16385).
Should we have a builder that runs the standard library tests compiled with -buildmode=shared? What about c-shared and c-archive?
cc @ianlancetaylor @bradfitz

More automated testing of this sort of thing would definitely be a good thing. You can't just run "go test -buildmode=shared std" though because -buildmode=shared doesn't make an executable. I guess it would make sense to build a minimal libruntime.so and run tests for all std library things apart from runtime (you can't really say go test -linkshared foo when foo is built into a shared library).
Running go -test -buildmode=pie would be useful.
Something like https://go-review.googlesource.com/#/c/16343/ would be nice too.

I have no objections. Any concrete proposal for x/build/dashboard/builders.go etc?


Updated scripts to include WarmStorage configuration.

connects to #98

Hi @hveiras, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


Iteration Plan for September 2017

This plan captures our work in September. This is a 4 week iteration. We will ship early October. It's almost getting boring, but the main focus still remains on providing support for multi-root-folder workspaces #396. However, we're getting into the home stretch, and we'll wrap up the work in the core. We'll also work with extension authors on getting their extensions ready for multi-root-folder support.
Other than that, most of the team is back from vacation. We are approaching our full capacity.
Endgame

Sept 26th: Code freeze for the endgame
Sept 29th: Endgame done

The endgame details for this iteration are tracked in TBD
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:

Mark
Description

:runner:
work in progress

:hand:
blocked task

:muscle:
stretch goal for this iteration

:large_blue_circle:
more details required

:red_circle:
missing issue reference

Workbench

[ ]  :runner: Avoid window reload when transitioning to multi-root-folder setup #32945 @sandy081 @bpasero
[x] Explore using ripgrep for file quick-open #24074 @chrmarti
[ ] :runner: Explore touchbar support for OS X @bpasero
[x] :runner: Improve editor history navigation (go back/go forward) #29027 @bpasero
[x] :runner: code --wait returns when the editor tab is closed #24327 @bpasero

Editor

[ ] :runner: Support for user-defined folding regions #12146 @aeschli
[ ] Refine indent based folding for python style languages #3353 @aeschli
[ ] :runner: Can't create breakpoint on current line because light bulb is in the way #25174 @jrieken
[x] :runner: Add support for transformations in snippet placeholders #6920 @jrieken
[x] :runner: Allow to specify file encoding per language #19890 @bpasero
[ ] :muscle: Explore drawing optimization in minimap #34170 @tyriar @alexandrudima

Debug

[ ] Link origin of messages in the Debug Console #24490 @isidorn
[x] :runner: Improve WSL support in node debugger adapter https://github.com/Microsoft/vscode-node-debug/pull/158 @weinand
[x] Debt: Adapt debug adapters to new DebugConfigurationProvider #33835 @weinand
[x] Switch to official "loaded scripts" debug API #33834 @weinand

Terminal

[x] Optimize terminal drawing performance #34169 @tyriar

SCM

[ ] :runner: Refine UI when using multiple repositories in a workspace #33363 @joaomoreno

Tasks

[ ] :runner: Support Task configuration in the multi-root-folder setup #29454 @dbaeumer
[ ] :runner: Multi-root-folder support for gulp, grunt, npm task runner #34228 @dbaeumer @egamma

Languages
Language Server Support (vscode-languageclient, vscode-languageserver)

[x] :runner: :red_circle: Document proposed protocol changes (ColorProvider) @aeschli

Emmet

[ ] Support for choices in Emmet snippets #33994 @ramya-rao-a

JavaScript/TypeScript

[ ] :runner:  Explore how to get syntax highlighting in template strings #34260 @mjbvz
[ ] :runner: Explore improve UX for when to surface Extract Method to users #34261 @mjbvz
[ ] :runner: Automatically show suggestions when entering an import statement #21543 @mjbvz @jrieken

Extensions

[ ] Adapt workspace extension recommendations to multi-root-folder workspaces #29242 @sandy081
[ ] Improve relevance of prompted extension recommendations #34233 @ramya-rao-a
[ ] Support to attach debugger to an electron-spawned node process #25618 @weinand

Extension Contributions

[ ] :red_circle: Docker: Support multi-root-folder workspaces @bpasero @chrisdias
[ ] :muscle: Vetur: Explore support for multi-root-folder workspaces https://github.com/vuejs/vetur/issues/424 @octref
[ ] Go: Ship support for multi-root-folder workspaces https://github.com/Microsoft/vscode-go/issues/1142 @ramya-rao-a
[x] :GitHub issues: Support multi-root folder workspaces https://github.com/Microsoft/vscode-github-issues-prs/issues/21 @chrmarti

API

[ ] Broader support for  WorkspaceFolder in the API (glob, doc filter) #34157 @bpasero
[ ] Provide a picker UI for WorkspaceFolders #32936 @bpasero
[x] Support formatted parameter hints and suggest items using MarkedString #11877 @jrieken
[ ] :runner: Promote Open/Save dialog API to stable #13807 @jrieken
[ ] Support to contribute a menu item for a resource suffix (e.g. *.zip) #26044 @jrieken
[ ] Debug: Expose debug status such as started/stopped #30810 @weinand
[ ] Debug: Add "breakpoint created/deleted" notifications #8642 @weinand @isidorn
[ ] Debug: Allow access to current launch configuration in an extension #23564 @weinand
[ ] :red_circle: :runner: Promote Color Provider API to stable @rebornix @jrieken

Engineering

[x] Adopt Electron 1.7.7 #33953 @tyriar
[ ] :runner: Improve stability and performance of smoke test #34203 @joaomoreno @isidorn @sandy081
[x] Explore bot support in component repositories #32238 @chrmarti
[x] Adopt new CLA bot on GitHub #34239 @kieferrm

Documentation

[x] :red_circle: Publish extension guide for multiple-root-folder support @bpasero @dbaeumer @sandy081
[x] :red_circle: Publish sample extension with multi-root-folder support @bpasero
[ ] 🏃 Move Tips and Tricks to code.visualstudio.com @gregvanl
[ ] Add Multi-root workspace topic @gregvanl
[ ] 🏃 Review and update keyboard cheatsheets @gregvanl
[ ] Review debugging docs, and link up existing vscode-recipies to new debugging sections @auchenberg

Explorations

[ ] :runner: Provide FileSystemProvider API including searching support  #34218 @jrieken
[ ] :runner::red_circle: Support root folders populated by a FileSystemProvider (see API) @isidorn @jrieken
[x] Provide FtpFileSystemProvider sample #34218 @jrieken
[ ] :runner: Explore ways how to make Electron adoptions less painful #34395 @Tyriar

中国人民送来贺电(The Chinese have send message of congratulation)！

同祝~

The C# region folding thing is finally seeing some lights?

what about a Windows Store port? It's under consideration?

在git环境下，对修改的文件进行跟踪标记，像webstorm那样修改过的文件名的颜色发生变化

@DongLee0504
See #178. And this issue is for tracking the iteration plan, please comment on the appropriate place with English next time.

@manuelelucchi Take a look at this screenshot. https://github.com/Microsoft/vscode/issues/33362#issue-253591569. You can see Visual Studio Code (Centennial) in the All apps list on the left. So it seems like they're at least testing it 😊

Closing 1.17 has shipped.


Split out a new category for running commands.

Running commands and scripts makes it possible to do the work of many other MCP servers, with a single tool call. Definitely deserves its own category

Thank you!


fix(cargo): fix linking on OSX 10.10

On OSX 10.10, attempting to run cargo test will yield a
linker error.
Just removing the feature fixes the issue, even though I am not
sure if it is breaking something further down the line.

This doesn't break anything, for two reasons:

solicit has no "openssl" feature :)
Even the "tls" feature, which is what was meant here, I'm sure, isn't used anywhere

I mentioned before that we don't need it here for anything... :)


[ts-codegen] Generated SSE procedures should have a return type annotation

Environment
arri v0.45.4
node 20.12.2
Reproduction
N/A
Describe the bug
Generated clients with SSE procedures produce this TS error
The inferred type of '<procedure-name>' cannot be named without a reference to<EMAIL_ADDRESS>This is likely not portable. A type annotation is necessary.

Additional context
The fix is to have generated code add a return type annotation and import from event-source-plus

fix in v0.45.5


Upgrade WinRM Gem version to 1.7.2

WinRM Gem Version 1.7.2 fixes a BOM regression issue in 2008R2
Requested by @djberg96.  Simply a gem version update.
@djberg96 @jrafanie @Fryguy please review and merge.  Gracias.

:+1:

:+1: :tada:


Update open-the-exchange-management-shell.md

Added Windows 2019 Core instructions per #5993.

Docs Build status updates of commit 4eb8bde:
:clock10: Full build: the average full build time is 17 min(s) 52 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 4eb8bde:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/open-the-exchange-management-shell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8990e87:
:clock10: Full build: the average full build time is 17 min(s) 52 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 8990e87:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/open-the-exchange-management-shell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f2a8109:
:clock10: Full build: the average full build time is 17 min(s) 52 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit f2a8109:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/open-the-exchange-management-shell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Move controller config to the spec package

Moving config to the spec package will help us avoiding cyclic dependencies

👍

Coverage increased (+0.03%) to 9.227% when pulling 58572bb43f83d28922700ac6d13dc65c549ff84b on move-config into 13bf0c6bea452732a1d30a502a935a259fac7095 on master.

👍


task 1 issue

how did you guys find the frequency is it after fft?

Yet to be done. Have you done? any idea?

Ya we should be using fft to find the peak frequency. You can check on ours file from group 2.

I have included all the tasks under Task 1 folder please check.


Rename README.md to github.txt

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

Thanks for the change. Why are we doing this?


RKI covid numbers are not updated

Hello,
is it only me who has the problem that the RKI covid numbers are not updated? Or is this a general problem? Has RKI changed something?
Until about shortly before Christmas everything ran fine, I have not changed anything in the configuration since then. However, the data is not being updated. Sensors are available.

HASS
Version core-2021.12.5
Installation type Home Assistant OS
Development false
Supervisor true
Docker true
User root
Virtual environment false
Python version 3.9.7
Operating system family Linux
Operating system version 5.10.63-v7l
CPU architecture armv7l
Time zone Europe/Berlin
Host operating system Home Assistant OS 7.0
Update channel stable
Supervisor version supervisor-2021.12.2
Docker version 20.10.9
Total disk space 109.3 GB
Disk space used 32.8 GB
Healthy true
Supported true
Board rpi4
Supervisor API ok
Version API ok
Thanx and BR,
Ralf

It happens to me every couple of weeks. Do not know why.
Delete All RKI Integrations

Restart HA and than add it again.

@LuckyTriple7
thank you for the quick reply! 👍

@seiferrtalle Could you add logfile so I can have a closer look on this issue. Haven't seen it myself yet.
Anyway the integration will be part of Home-Assistant soon. So we can ensure, it has nothing to do with HACS.

@thebino below are the log entries since the last restart on 2021-12-25.
I'll do a restart again in a minute and see what he speaks to us then .... 😉
Zeile 3: 2021-12-25 13:41:44 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration rki_covid which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Zeile 25: 2021-12-25 13:42:29 WARNING (MainThread) [homeassistant.setup] Setup of rki_covid is taking over 10 seconds.
Zeile 132: 2021-12-25 13:42:56 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error reading data from rki-covid-parser timed-out:
Zeile 132: 2021-12-25 13:42:56 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error reading data from rki-covid-parser timed-out:
Zeile 132: 2021-12-25 13:42:56 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error reading data from rki-covid-parser timed-out:
Zeile 231: 2021-12-25 13:43:32 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds
Zeile 232: 2021-12-25 13:43:32 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds
Zeile 233: 2021-12-25 13:43:32 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds
Zeile 234: 2021-12-25 13:43:32 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds
Zeile 235: 2021-12-25 13:43:32 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds
Zeile 6315: 2021-12-25 13:49:40 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: fritzbox_callmonitor, switch, rest_command, sensor.hacs, daikin, notify.mobile_app, sensor.miflora, meross_cloud, config, energy, weather.met, media_player, network, light.fritzbox, default_config, number, device_tracker.bluetooth_tracker, sensor.pi_hole, updater, kia_uvo, yamaha_musiccast, auth, dlna_dmr, tado, cover, sensor.anniversary, homeassistant, light, sensor.dwd_weather_warnings, notify, binary_sensor.zha, binary_sensor.pi_hole, homematicip_cloud, sensor.mobile_app, input_boolean, binary_sensor.kia_uvo, usb, timer, calendar.google, sensor.broadlink, cover.tradfri, cover.zha, sensor.energy, sensor.systemmonitor, sensor.home_connect, tts, binary_sensor.shelly, switch.somfy, switch.meross_cloud, analytics, rpi_power, input_text, switch.wake_on_lan, light.home_connect, system_log, webhook, map, device_tracker, history, lock.kia_uvo, switch.switchbot, sensor.waste_collection_schedule, switch.broadlink, sensor.mitemp_bt, sensor.shelly, waste_collection_schedule, sensor.tado, api, recorder, light.tplink, media_player.cast, http, home_connect, input_number, binary_sensor.rpi_power, sensor.zha, netatmo, sensor.tradfri, sensor.rest, lovelace, blueprint, cast, harmony, media_player.spotify, lock.zha, dhcp, water_heater.tado, select, sensor.moon, wake_on_lan, somfy, device_automation, switch.tplink, template, counter, sun, met, siren, binary_sensor.updater, script, sensor.somfy, binary_sensor.home_connect, tplink, camera.generic, my, device_tracker.zha, camera, climate, person, lock, climate.somfy, notify.pushover, fan, tag, tankerkoenig, group, binary_sensor, scene.homeassistant, calendar.waste_collection_schedule, search, sensor.fritzbox_callmonitor, cover.meross_cloud, climate.meross_cloud, number.zha, frontend, water_heater, sensor.time_date, lig ...
Zeile 147934: 2021-12-29 11:04:50 WARNING (SyncWorker_9) [homeassistant.loader] We found a custom integration rki_covid which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Zeile 149026: 2021-12-29 11:46:17 WARNING (MainThread) [homeassistant.components.sensor] Platform rki_covid not ready yet: Data coordinator could not be initialized!; Retrying in background in 30 seconds

@thebino and here some new log entries after a fresh restart, hope that helps?
Zeile 4: 2021-12-29 13:28:27 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration rki_covid which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Zeile 143: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 143: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 144: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 144: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 145: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 145: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 146: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 146: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 147: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 147: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 148: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 148: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 149: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 149: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 150: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 150: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 151: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 151: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 152: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 152: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 153: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 153: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 154: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 154: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 155: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 155: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 156: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 156: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 157: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 157: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_schweinfurt_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 158: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 158: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 159: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 159: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 160: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 160: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 161: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 161: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 162: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 162: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 163: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 163: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 164: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 164: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 165: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 165: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_schweinfurt_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 166: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 166: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 167: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 167: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 168: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 168: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 169: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 169: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 170: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 170: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 171: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 171: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 172: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 172: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 173: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 173: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.lk_wurzburg_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 174: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 174: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 175: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 175: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_deaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 176: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 176: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_recovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 177: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 177: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_weekincidence (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 178: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 178: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_casesper100k (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 179: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 179: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newcases (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 180: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 180: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newdeaths (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 181: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 181: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.sk_wurzburg_newrecovered (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 202: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform rki_covid is taking over 10 seconds.
Zeile 203: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform rki_covid is taking over 10 seconds.
Zeile 204: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform rki_covid is taking over 10 seconds.
Zeile 205: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform rki_covid is taking over 10 seconds.
Zeile 206: 2021-12-29 13:29:54 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform rki_covid is taking over 10 seconds.
Zeile 259: 2021-12-29 13:30:13 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.
Zeile 259: 2021-12-29 13:30:13 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.bl_bayern_count (<class 'custom_components.rki_covid.sensor.RKICovidNumbersSensor'>) implements device_state_attributes. Please report it to the custom component author.

Fascinating! I did nothing - except the last restart on 13:29 - and now the values were updated - without further action from my side! 🙃

Looks like the rki-parser got no response from the rki servers within 10 seconds. As you can see in the logs home-assisstant will retry it in background. Perhaps the rki servers where busy.

I also have the problem that the parser does not update
After a System-Restart i see in the logfile:
2022-02-08 04:05:01 ERROR (MainThread) [custom_components.rki_covid] Error fetching rki_covid data: Error reading data from rki-covid-parser timed-out:
Thats all.
No more Log-Entries with rki_covid.
It seems, the component does't restart himself if the RKI-Api not reach ... possible?


Suggestion: Show maintenance tunnel overlay of all maintenance tunnels.

Just so I know what is covered and what is not.

Added a checkbox at the bottom to show the range of any structure. ie. BMS Foreman Stacker & Maintenance Tunnel. 👍


Update Pull Request flow diagram

Update Pull Request flow diagram in the presentation

Code review cycle has been added and also animated


Formatting document fails in monorepo

Extension version: 1.7.6 (latest master)
The Format document feature uses the bsc.exe binary:
https://github.com/rescript-lang/rescript-vscode/blob/877f874c52ab51e88dacc73524ca4e5c16912eef/server/src/server.ts#L740-L742
The location of the bsc.exe binary is determined as follows:
https://github.com/rescript-lang/rescript-vscode/blob/877f874c52ab51e88dacc73524ca4e5c16912eef/server/src/server.ts#L112-L121
It is "reverse engineered" from the location of the rescript binary:
https://github.com/rescript-lang/rescript-vscode/blob/877f874c52ab51e88dacc73524ca4e5c16912eef/server/src/server.ts#L107-L110
https://github.com/rescript-lang/rescript-vscode/blob/877f874c52ab51e88dacc73524ca4e5c16912eef/server/src/utils.ts#L56-L60
The node_modules/.bin/rescript symlink exists both at the monorepo top level node_modules and the subdir node_modules, which makes findRescriptBinary return src/monorepo/subdir/node_modules/.bin/rescript.
However, the node_modules/rescript directory usually exists only at the monorepo top level, so when the path of the rescript binary is used to derive the location of bsc.exe, this results in the non-existent path src/monorepo/subdir/node_modules/rescript/linux/bsc.exe. It should actually return src/monorepo/node_modules/rescript/linux/bsc.exe (without subdir).
To make things more complicated, if node_modules/rescript does exist in the subdir, that directory should be used. This may be the case when multiple rescript versions are used in the same monorepo.

I will create a PR that uses the correct algorithm for finding bsc.exe.

Note that a lot of the complexity comes from this guideline:
https://github.com/rescript-lang/rescript-vscode/blob/master/CONTRIBUTING.md?plain=1#L159
We want to use bsc.exe (ocaml binary) instead of bsc (nodejs wrapper). ``bsclives innode_modules/.bin, while bsc.exe` does not, so a different algorithm is needed.

See the forum discussion first.
Some agreement should be reached first.
Then documenting the agreement and implement it.
Turns out there are many opinions in what is a monorepo.

@cristianoc I think #573 may be a good candidate to merge even before consensus is reached about monorepos, because:

Formatting worked in my monorepo in a previous version, and was broken recently
This syncs the mechanism for finding bsc.exe to the mechanism for finding rescript, which is more logical
It adds rescript.settings.platformPath, which can be used to fix formatting if you have a non-standard setup which is not automatically supported, while currently there is no easy way to fix formatting

Hi, I'm on macos and I also got an issue about formatting on a monorepo (yarn v1 workspaces).
"format on save" or command "document format" don't format at all on a monorepo project (no issue on a normal project, with the exact same vs code config) with 1.6.0 version, I downgraded to 1.4.2 and it work.

We also have the same issue at work on our monorepo, it used to work fine before.


Add Code of Conduct

Add code of conduct for the repository and hence its documentation can be enhanced !

Hi @aswathcm29 I want to work on this issue. Kindly assign this issue to me

Okay @Itachii27 I'd assign it to you ! Make sure it is proper and suitable for the repo and application

Hi @aswathcm29 I have done. Kindly review the PR and please add the labels of gssoc-extd, hacktoberfest, hacktoberfest-accepted and level in the issue

Hi @aswathcm29 Kindly modify the label name to gssoc-extd and level-1. As it merged, please close this issue as well

@aswathcm29 Could you kindly modify the labels to gssoc-extd. As i'm working under that and you have mentioned gssoc-etd which won't be counted


Hotkeys for Lower Thirds

Hotkeys will be added only for the first lower third. If more than one is active, the second will have to be triggered manually.

 Hotkeys for lower thirds


.ignore functionality

To shorten deployment time, I'd like to be able to mark node_modules folder in a .ignore file, and later install the npm dependencies using the Kudu tools.
Is there such a functionality - similar to .gitignore, .npmignore, etc.?

Probably related to https://github.com/Azure/azure-functions-core-tools/issues/341

Should we honor the .funcignore file as well or use a workspace setting (how we handle this in the other extensions)?
I'm thinking that if there's already a common practice, we adopt that.

I think the .funcignore option.

There are workspace settings that you can set to ignore the node_modules for now.
"azureFunctions.zipGlobPattern": {
                        "scope": "resource",
                        "type": "string",
                        "default": "**/*",
                        "description": "Defines which files in the workspace to deploy. This applies to Zip deploy only, has no effect on other deployment methods."
                    }
                    "azureFunctions.zipIgnorePattern": {
                        "scope": "resource",
                        "type": [
                           "string",
                            "array"
                       ],
                        "default": "",
                       "description": "Defines which files in the workspace to ignore for Zip deploy. This applies to Zip deploy only, has no effect on other deployment methods."
                    },
But I agree with @fiveisprime that we should adopt a common practice rather than leveraging workspace settings.


Handle search filter when no results are found

Pull Request Title: ✨ Handle search filter when no results are found ✨
Description:
This Pull Request proposes a code modification to handle empty search results in a more user-friendly way. When the search yields no results, instead of displaying an empty list, the text "Oops!, No results found" is now displayed in the center of the screen to inform the user of the absence of results. 🚀
Details of Changes:

I added a new CSS class called "no-results" to style the text displayed when the search yields no results. The CSS class centers the text, sets the font size to 2rem, and adds a top margin of 50px for better presentation. 🎨

I introduced a new state variable noResults that is updated based on the search result. If the search yields no results, noResults is set to true, otherwise, it's set to false. 🔄

I modified the component structure to conditionally display the filtered movie list or the text "Oops!, No results found" based on the value of noResults. 🧐

Tests:

I tested this change by performing searches with empty results and ensured that the text "Oops!, No results found" is displayed correctly instead of an empty list. ✔

@mitchiemt11  Please review this PR when you have a chance 🙂

@Mogoww PR is correct. I'm merging it now.
Would you mind if I assign this to you --->> https://github.com/mitchiemt11/trailers-trove/issues/24? It's kinda related to this one.


This mostly fixes a segfault on the command line

Current coverage is 60.58% (diff: 100%)

Merging #210 into master will increase coverage by 0.01%

@@             master       #210   diff @@
==========================================
  Files           128        128
  Lines          6807       6810     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           4123       4126     +3
  Misses         2327       2327
  Partials        357        357

Powered by Codecov. Last update da7c14d...be1e62e


Fix typo: depreciated -> deprecated

See https://www.merriam-webster.com/dictionary/deprecate
This change only affects comments, documentation,
and RPC Help messages.

Thanks Sean!


Implement listing of open ports

Hi team,
Thanks for the tool! It's really easy to use and covers a lot of Docker misconfigurations!
I've noticed that check 5.8 is implemented as a text note. I suggest to make it more actionable: to list open ports in the tool output. It'll allow us to reduce the amount of repetitive work.

Nikita Stupin
Advanced Software Technology Lab
Huawei

Thanks again @nikitastupin, will do a couple of tests before merge.

Looks good!
And so sorry yet again for this delay @nikitastupin


Ambiguous call with integer parameter for YAML::Any.new

Calling YAML::Any with an untyped integer literal (or since #11431 an integer value that is not of type Int64) fails to compile because autocasting refuses to resolve an ambiguous call.
The reason for that the parameter to YAML::Any.new is restricted to YAML::Type which is a union that includes Int64 | Float64 (among others).
require "yaml"
YAML::Any.new(1) # Error: ambiguous call, implicit cast of 1 matches all of Float64, Int64

# This works, however
YAML::Any.new(1.0)

The literal/value needs to be typed/casted as Int64. YAML::Any uses these types internally to represent all integer values, so that's what it expects.
require "yaml"
YAML::Any.new(1i64)

This is annoying. I think it should be clear that when I pass an integer value to YAML::Any, that I want to express an integer value. I don't care what type is used to represent that. And likewise, when I pass a float value, I want to express a float value, no matter the type.
This should be relatively easy to resolve for YAML::Any by adding an overload for Int which casts to Int64.
But I believe this could very well be implemented as a general rule in the compiler: When faced with a choice between integer and float types, autocasting should pick the type that matches the nature of the origin type. The same could probably work between signed and unsigned integer types.
#7752 is a related discussion about resolving autocasting between multiple similar target types.
EDIT: Originally I mentioned this would also affect float literals, but that's not correct. I expect this is because Float64 is the default type.

If this was fixed in #13618, this issue can be closed, right?

https://github.com/crystal-lang/crystal/pull/13618 is just a workaround to counter the symptoms in Any.new.
It doesn't fix the underlying issue with autocasting.


[4.2] [Type checking] A declaration in an overlay can shadow an imported declaration.

If a declaration provided in a Swift overlay has the same signature as
a declaration imported from the Clang module it overlays, or some
private framework that re-exports its interface through that Clang
module, the declaration provided in the Swift overlay shadows the one
imported from Clang.
To make this work for unqualified lookup, allow the shadowing rules to
kick in there as well. Make this a very narrow fix, because the
underlying problems that prevented us from doing this shadowing still
persist.
Fixes rdar://problem/35691030 and its several dupes.

@swift-ci please test and merge


Enable IPv6 NF_MATCH kernel parameters

Description of changes
This ensures that systems with IPv6 configured can successfully start their firewall.services (at least on master nixpkgs).
Testing
I built a system with networking.enableIPv6 and checked systemctl status firewall which is now successful.

I was able to successfully test this with an Orin AGX, and the firewall service seems to work correctly with this kernel.


Check type before using them like obj/array

lgtm lol.

Hmm
I was afraid it could be an array

obj = []
[]
obj && typeof obj === 'object'
true

Though I guess it wouldn't crash even if were an array

Object(obj) === obj is true for arrays as well. You’ll need to && !Array.isArray(obj)


Get unique id of the visual?

Is there any way to get a unique id of a visual that would change on copy/paste/new visual/etc?

@powerbilayeredmap
we support only unique quid for every visual.
Always it is written in pbiviz.json visual project's file.


403 error

Can anyone lead me in a way to fix error 403 forbidden? I had to reinstall everything and when I try to log on the web ui I get this error? Thanks so much. David Klein

@astroisme, what URL are you using?  Have you tried using the Pi's IP address instead?

Hi Eric. I tried http://allsky.loal and also http:// cameras ip number. Same results 403 forbidden

Hi Eric. I tried  http://allsky.local and also http:// cameras ip. Same results. 403 forbidden. strange

Sorry Eric. Not cameras ip but the pi ip and same results

Is there anything in /var/log/lighttpd/error.log?
I assume you have never been able to view the WebUI?

I figured it out. Bookworm wont work causing that error. Went back to bullseye and working again.

I am surprised you got that far with Bookworm. It normally kills the installation.
We are working on a Point Release to support Bookworm.


"Log in with Basic Auth" doesn't work with custom port

Dear,
Thank you for this great project. I'm excited with it. But it seemed to me it has a one small issue when we start ATC on custom ports (not 80):

Everything is OK when I set EXTERNAL_URL. I will close it.


Improve characters#new feature specs

Fixes #1093
I encountered some problems around icon selection and template selection b/c the js isn't getting loaded; fixing that may require #1146

Can you leave an explicit TODO in the codebase around the things we currently have commented out? That way we know what the comments are for directly.

I like these tests! My comments are just to be surer that this is testing correct behavior, instead of accidentally-correct behavior, but it's a significant improvement! :D


Pizza Model

Summary
Mongoose requires a model for every type of object represented in the database. There is not currently a model for pizza.
Fix

Create a model for pizza.

The model should have applicable attributes like size, crust, sauce, toppings.

See PR: #5


content property block

Because you can't style pseudo-content without declaring content innit.

Nice one bud! I'll add this version of the reset to a few bits I'm on over the next few weeks then get it merged if nothing terrifying happens. I'm p sure because yes, suddenly every element will have two pseudo-elements, they will be inline, so shouldn't cause issues.

I'm wondering if this can have a rendering performance impact on documents with a lot of DOM elements, at least on low end mobile devices.
Probably very small, but might be worth testing.

I am with @nhoizey I am not sure if this will have an impact on performance. If you inspect the DOM, all elements will have those pseudo elements when this is applied.


Add pre-commit

Use pre-commit to run luacheck and luaformatter

The existing pre-commit hooks rely on the system time and don't install the relevant tools. I'll try to get Lua support added to pre-commit so that I can improve this situation for other users (and myself).
Here's the relevant PR: https://github.com/pre-commit/pre-commit/pull/2158

Now that Lua support is merged. I need to add hooks for Luacheck and LuaFormatter.
The Luacheck PR is open at https://github.com/lunarmodules/luacheck/pull/48

The LuaFormatter PR is at https://github.com/Koihik/LuaFormatter/pull/236

Yay, all merged!


Datatable actions files not generating correct $id name

When you run the scaffold command with the option --primary=key the datatables actions files are not generating with the correctly named $id variable.
Example:
User table with a user_id primary should generate with $user_id but still generates as $id.

@Shadow2004 issue is fixed.


Add paginations to the items/index page

Summary
We recently added the kaminari gem for pagination in #1254. This PR added pagination to the donations/index page. We should add this to the other places where we have records that could end up with unwieldy page scrolling. This issue is to add this to the items/index page. You should be able to look at PR #1254 for an example of how to accomplish this with Kaminari.
Criteria for completion

[ ] Pagination present on the items/index page

Note
This page will likely not need paginations for most organizations, but it would be a best practice to have it everywhere that it could be needed.

Hey, I'm looking to work on this right now and hopefully we'll have a PR soon!


Adorama False Positives

Description
In the long standing tradition of constantly updating EVGA, Newegg, and Amazon to ensure we don't get spammed with False Positives, an error message on Adorama.com is triggering something similar. Below will by a gyazo screenshot of the error, and it can be easily added to the list of blacklisted text in the filer.
https://gyazo.com/685290a5c08de225c2cb3396772dde3f

False positives should be solved by https://github.com/jef/nvidia-snatcher/pull/141, are you up-to-date with the latest changes?


Add asciidoc

Why:

ngrok is not documented on quarkiverse.io

This change addreses the need by:

Fix the partial adoc build adn have it have the bare minimum
needd documented.

Thanks for all the work @maxandersen !

i've submitted https://github.com/quarkiverse/quarkiverse-docs/pull/138 so the docs will eventually show up on https://docs.quarkiverse.io/quarkus-ngrok too


Deployment failed without any reason

I was new to Solana Programming after the program build successfully, when I clicked deploy it failed due to this error, I am using Devnet. is anyone know how to fix this?

Did it fail at the end? Would be great if you could you share the logs in the browser console. You can open it with Ctrl+Shift+I or F12 or right click -> Inspect -> Console.

owh okay I opened the console, I noticed that it said "Failed to load resource: net::ERR_NAME_NOT_RESOLVED"
is it the code error ? but the code has already build successfully

The error is invalid account data for instruction which I'm guessing the error only failed at the last instruction. This is most likely because there is a connection error to the devnet RPC(which can be seen from the screenshot as well). Are you able to reproduce this issue for example after refreshing the page or creating a new workspace with the same program?

not sure how to reproduce but I m still having the same issue and my code is just basic program following turorial since I m new to solana programming, but below is my code:
use anchor_lang::prelude::*;
use anchor_lang::solana_program::entrypoint::ProgramResult;
use anchor_spl::token::{self, Token};
use std::mem::size_of;
//pub mod constant;
//pub mod states;
// // crate = npm (like a package)
//use crate::{constant::, states::};
// our program's publickey (will update automatically when build project)
declare_id!("5eVMMxzdFuZKw3Yz5nQ3d5sf3cZbwpo4RrMzhzCAakrV");
// define program
pub mod funding_platform {
use super::*;
pub fn accept_payment(ctx: Context<PayerContext>, data: u64) -> ProgramResult {
    // ctx is type (Context<PayerContext>) PayerContext comes from below

    // see usecase (Entry PAYMENT FOR APP)
    let payer_wallet = &mut ctx.accounts.payer_wallet;
    payer_wallet.wallet = ctx.accounts.authority.key(); // value of the PayerAccount, .wallet comes from payerAccount Struct

    let ix = anchor_lang::solana_program::system_instruction::transfer(
        &ctx.accounts.authority.key(),
        &ctx.accounts.receiver.key(),
        10000000,
    ); // how much should pay

    anchor_lang::solana_program::program::invoke(
        &ix,
        &[
            ctx.accounts.authority.to_account_info(),
            ctx.accounts.receiver.to_account_info(),
        ],
    )
}

}
#[derive(Accounts)]
pub struct PayerContext<'info> {
#[account(
init,
seeds = [b"payer".as_ref(), authority.key().as_ref()],       // generate unique hash based on the seed
bump,                                                       // bump will increment the hash to create unique (like id += 1)
payer = authority,                                          // whos paying for the smart contract => authority
space = size_of::()+8
)] // in Rust, is a must to know the space
pub payer_wallet: Account<'info, PayerAccount>,
#[account(mut)]
pub receiver: AccountInfo<'info>,

// Authority (signer who paid transaction fee, authority = signer)// let it become mut, this authority can change (mut = not constant)
#[account(mut)]
pub authority: Signer<'info>,

pub system_program: UncheckedAccount<'info>,

// Token Program
#[account(constraint = token_program.key == &token::ID)]
pub token_program: Program<'info, Token>,

// Clock to save time
pub clock: Sysvar<'info, Clock>,

}
#[account]
pub struct PayerAccount {
pub wallet: Pubkey,
}

This is because the program module doesn't have a program attribute so the program is not being created.
Instead of
// define program
pub mod funding_platform {

should be
// define program
#[program]
pub mod funding_platform {

i think it fix the issue, alright Thank you so very much!!


ZipException in ClassUtil

Just got this exception while fiddling with the editor. Unfortunately, I don't have a step-by-step procedure to reproduce it.
java.util.zip.ZipException: zip file is empty
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(ZipFile.java:225)
	at java.util.zip.ZipFile.<init>(ZipFile.java:155)
	at java.util.jar.JarFile.<init>(JarFile.java:166)
	at java.util.jar.JarFile.<init>(JarFile.java:103)
	at org.scijava.ui.swing.script.autocompletion.ClassUtil.findAllClasses(ClassUtil.java:249)
	at org.scijava.ui.swing.script.autocompletion.ClassUtil.ensureCache(ClassUtil.java:77)
	at java.lang.Thread.run(Thread.java:748)

(pinging @acardona)

The error is innocuous in that the try/catch is inside the for loop, therefore, it tests each jar file (aka a zip file) independently. Regardless of a jar file being invalid, the method ClassUtil.findAllClasses will succeed.
Most likely what happened: you were still running a mvn build and one jar file was a .part file or something, still empty.


lsm6dso: Add FIFO and LPF capabilities

Add LSM6DSO_ENABLE_FIFO to Kconfig to enable fifo output in prj.conf
New dts variables for fifo batch mode config:

accel and gyro batch data rate: rate of data written to fifo
batch count threshold: interrupt triggered when threshold reached

New public API for lsm6dso sensor specific triggers and attributes:

Trigger SENSOR_TRIG_LSM6DSO_CNT_BDR for bdr count threshold reached
Attribute SENSOR_ATTR_LPF_FREQ for setting low pass filter cut-off
frequency for either accel or gyro

Ability to enable LPF for accel and gyro by configuring cut-off via
sensor attribute set API
Function to fetch all data in fifo:

Only handles accel and gyro data with tagged with LSM6DSO_GYRO_NC_TAG
and LSM6DSO_XL_NC_TAG
Called with channel SENSOR_CHAN_ALL if fifo enabled

Initialise FIFO with optional batch mode:

Threshold, accel and gyro batch data rate configured in devicetree

Rename interrupt GPIO pin to be more generic term
New trigger and handler for fifo bdr count threshold reached:

Initialise interrupt on either int1 or 2 line
Clear FIFO when trigger gets enabled
Use accel or gyro for batch counter based on trigger channel

Signed-off-by: Linus Reitmayr<EMAIL_ADDRESS>

@MaureenHelm and @gmarull could you take a look?

See #44302 this is closer to what I was expecting to see here with the FIFO using the existing API myself

See #44302, it's closer to what I was expecting using the device FIFO with the existing API myself

I think that @LeeNuss was proposing something similar with current APIs here:
https://github.com/zephyrproject-rtos/zephyr/pull/43429#discussion_r835446681
I like the ring buffer approach as well. So, why not replicating it here also.

See #44302, it's closer to what I was expecting using the device FIFO with the existing API myself

I think that @LeeNuss was proposing something similar with current APIs here: #43429 (comment)
I like the ring buffer approach as well. So, why not replicating it here also.

Thanks for linking this, yes I was thinking off a similar approach, I'm happy to add the ring buffer into this PR. However for the LSM6DSO the FIFO won't have a fixed number of entries, hence there must be some way of sharing the number buffer entries with the application. I don't think misusing the current sensor API is ideal, so I'll request a change to either treat positive return values as the number of data entries or add a separate function for specifically fetching fifo data

Thinking more about the positive return its probably better to add an API call that returns the number of samples in the local sensor buffer. A lot of code likely expects fetch() to return 0 on success, meaning a return of 1 sample breaks everyone's code built on top.
Don't forget there's 100+ drivers in sensors now
Agreed it's not a good solution.
Instead of adding a fully new API call, could that not just be done through a private sensor channel, which the app can fetch via sensor_channel_get?
That'd be possible without any API changes :)


move the task definitions to their own file to segregate local form …

Changed the 08_device_subclassing to move the remote tasks into their own file that could be used in either example.  Tested on windows both programs with two RP2040 boards.
Changed the LED for the RP2040 to be board independent.  Pin25 is the LED pin only on the non-wifi board.  This assumes you are using a version of MicroPython 1.19 from the last month.
Not sure what line endings you are using but GIT says it coerced them to the original format whatever that means.

Thanks for the interest in Belay and for opening up this PR!
I have some opinions on the changes here:

For Example 01, your code is more robust, but as the first example I'd rather keep it as simple and barebones as possible to be more welcoming to all skill-levels.
We could move the class definition into it's own file to share between the examples, but I'd rather keep each example fully self-contained to make the code more clear and beginner-friendly.

Example 01 doesn't flash the light on the Pico-W. The LED is on the wifi chip GPIO.  They are moving to that LED construct as a standard but I don't know how many distributions have that yet.  Maybe remove the try-and-catch part.
Device subclassing is already a little advanced. Anyone using it knows about classes and initiations. The comingling is actually kind of confusing. A single file contains code that actually runs in two different places with two different sets of libraries. It has some global code and an embedded class that actually runs somewhere else. The MCU libraries have to be installed on the device and not in the file where they are actually referenced.
In addition, the two examples in the same project had different behavior. One flashed the light and the other flashed the light and read the temperature. Now they both do the same thing. I think extracting the tasks/class out shows that you can re-use the class. in a variety of different situations.
Good structure helps people understand what is happening.
Your call of course.

For example 1, I think we should maybe just have a comment to help out near the Pin declaration to assist users of different boards. I've never seen the Pin.board.LED attribute; googling it I found you over on the Micropython discussions 😄 . Considering how recent the Pin.board.LED change is, I'd wait to add it here until there's a tagged micropython release.
As for the differing behaviors in example 8, the main.py example was to show both manipulating an actuator as well as reading in new data from a sensor. Since it's already been demonstrated, I didn't include the temperature reading in example main_multiple_devices.py to keep it more terse.

Abandoning this pull request and creating one with a copy of example 8 that contains this change.  That makes it easier for me to track any changes in 08 and leaves 08 untouched fo retain the author's style.


Refactor Subscribers API to conform to new design

We want to refactor the Subscribers API to address compatibility issues with Micronaut and Quarkus arising from the library's reliance on Spring framework.
We would like to have the Events API migrated to the new REST dependency and ensure the on going updates to the unit tests to validate the modifications and uphold code quality.
For guidance on the expected changes, kindly refer to this pull request #54.

The Novu.java class
seems to have compilation errors because of new FeedsHandler(restHandler, novuConfig); and new MessageHandler(restHandler, novuConfig);. These constructors are missing in the class.

It should be fine now

@debanjanc01 there seems to be no traction on this issue. Are you still working on it?

Hey @mayorJAY , yes I'm working on it. :)
Couldn't build the branch because of the compilation failures.

Hey @mayorJAY , I've raised the PR for the same.


New Project Proposal - Open Mainframe Education (name TBD)

Name of project (must be unique within OMP)

Suggested names:
Open Mainframe Education
Open Mainframe Learning System
Mainframe Skills Solutions
Open Education for Z

Project description (what it does, why it is valuable, origin and history)

A project that aims to eliminate the roadblocks in mainframe education, by providing high-quality free education materials.
We want to provide an easy to contribute platform that through the OMP will have a broad reach, the ability to scale, and offer quality and innovative curriculum as not everyone learns in the same way.
3 main points
Reach, Scale, Quality

Statement on alignment with OMP charter mission

This project aligns with all the mission topics, but is an expansion of the OMP to include the Mainframe Education Community. This is to invite new talent to the Mainframe Community.
Partner with the Mainframe community in order to increase the number of mainframe-focused educational programs and ease the path for anyone seeking  industry-relevant mainframe skills

Sponsor from TAC (sponsor helps mentor projects)

We've discussed with the following TAC members:
Enyu Wang
Gregory MacKinnon
Robert Dahlberg

Preferred maturity level (see project stages)

Incubation stage

License and contribution guidelines (refer to the OMP guidelines)

Minimal license: Creative Commons
Other licensing needs will be discussed/defined at a later stage

Source control (GitHub by default)

Github

External dependencies (including licenses)

TBD (Internal discussion/process from IBM and Broadcom)

Initial committers (how long working on project)

Guilherme Cartier (IBM)
Deborah Carbo (Broadcom)
Viviane de Padua (IBM)
Yvette LaMar (IBM)
John Mertic (OMP)
Lauren Valenti (Broadcom)

Infrastructure requests (CI / OMP Cluster)

TBD, but probably no infrastructure request at this moment.

Communication channels (slack, irc, mailing lists)

Slack channel
#omp-education-project

Issue tracker (GitHub by default)

Github

Website

None yet

Release methodology and mechanics

Basic methodology:
->Reviews to ensure accuracy
->Define submissions
->Define standards
But will require further planning

Social media accounts

None yet

Community size and any existing sponsorship

None yet

All things IBM Z, hw/sw, or is the plan to start with any specific IBM Z technical discipline, or TBD?

Will this be similar to the cobol course or interskill? Will it include OMP projects like Zowe Education?

Hi @paulnewt - The idea is to provide education for all things Z. But to start we will probably provide very fundamental materials for z/OS beginners.
Hi @jellypuno, at least at the beginning, the project will focus only on basic Mainframe concepts for new professionals. From that, we want to increasingly introduce more advanced concepts for more mature students. But the idea is not only to focus on the core Z technologies (ISPF, TSO, REXX, JCL, COBOL, etc..) but also educate on the new technologies as well like Zowe  :)

This is perfect - numerous participants in the OMP COBOL for beginners are repeatedly requesting z/OS skills beyond anything related to Enterprise COBOL such as GDG's, etc. etc.

We should provide an overall framework to organize the core Z technology curriculum by subject/topic modules.  This would create an outline of the areas we want to develop and flesh them out over time.

some idea's --- a bit dated now http://ibm.biz/zosintro

I think elevating mainframe education/training to higher level is goodness. There's so much to learn about the Z platform, both on the application side and the IT administration side.
While there's already some good material on learning Z, it's all over the place and not well structured. If this project can take a structured approach in managing education targeting various subtopics on Z, I'm all for it!!

Sujay, I agree!  If we can get IBM's permission to look or even take their materials and map it to an outline of topics we can see where the state of Z education is at.   We can then start fleshing out what's lacking.

@solsu01 @bobdahlberg Since Mainframe skills can be quite intimidating for people that are just beginning, one of the approaches we are studying to go for is to create a roadmap of study topics, similar from whar this project have:
https://github.com/kamranahmedse/developer-roadmap

I remember seeing the web developer roadmap on Reddit and was internally crafting a mainframe one in my head! This is awesome :)

some idea's --- a bit dated now http://ibm.biz/zosintro

The videos are under my favorite list! I really believe we should invest more and more in easy and simple videos to make Z consumable for the next generation

Agreed, it's really easy to do videos in PowerPoint use voice over slides and screen recordings.  Plus you can embed videos.  My students and I had to do a lot of this when the university had to go virtual in March and April.  Our university will be using a combination of virtual and classroom tools from now on.

We intend to start this by providing existing assets already spread across our ecosystem today, we want MF vendors contributing content from what once was internal use only.   This of this as MF100 level courses.  This will lead to creation of new learning assets, a single source (vendor agnostic) combination of multiple contributors.  The outcome to the market is a clear pathway that will support any company, of any size, region or industry, to train new or retrain existing staff to take on mainframe job roles.  At no to low cost, but to also support (and not alienate) the many wonderful education companies out there who provide for fee services.
The vision is a single place to shop for MF foundations, with learning paths that make sense for a job role, Sys Prog, Security Admin, DBA, Operations, MF Application Developer, at some point the content will get more complex in the MF200 or MF300 level education, maybe there are vendor, services or product specific content branching that will occur.  The key is that we jointly contribute to the base, collaborate and advise the market on how to grow a mainframer in the hybrid datacenter.

This was approved by the TAC on 2020-05-15.


Slider align vertical

How to slides items in vertical direction? not in horizontal direction

⚠ You did not follow the contributing guidelines!
As stated in these:

You need to fill out the issue template. This step is mandatory! Not doing so will result in your issue getting closed. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.

Please read the doc, there is a dedicated prop for that: vertical.


feat(next-css): Separate CSS files

I think combining styles per page makes sense. Currently, my initial page (login) loads all css for the app including a ton of css for draftjs which is only used on a couple of pages.

Got merge conflicts @sayuti-daniel

@aequasi Fixed. I haven't tested this again.

This has to be re-implemented against canary

more merge conflicts.

I’m still figuring out how to better implement this

It would be interesting Next to have this option of separating css per page would be a great optimization of initial loading. I hope that in the future when I need this behavior this pull request has already been merged.

I tried implementing a similar feature in my nextjs app with a custom webpack config. I got the initial loading for the first page running, however I can't find a good way to load subsequent css when the route changes (on the client side).
My current approach of loading needed css with next/head unfortunately leads to flickering while loading the next page (my guess here is that the css is only put into the head, after the component already rendered the new children).
I think it would be best, if there was some way for packages/next/lib/page-loader.jsto take care of loading the new css, before changing the route, similar to how the js files are currently loaded.

Whats holding this back? Would love to see this.

Does this work? Would be useful to have it published to npm under a namespace for now if so.
I'm hoping to implement path splitting for CSS modules (loaded via npm) in this project - https://github.com/penx/govuk-frontend-react-example-next would be great if I can do so via this.
Also would like to hear what further work is needed on this and if there's anything I could help with.

Also much needed. I have a large site in next.js and the css loaded on every page is now 730k! Should be about 30k per page.

Looks like this was auto-closed when removing the canary branch. We're currently discussing how to solve this issue in a different way, I've sent you a dm on spectrum @sayuti-daniel

@timneutkens please could you reopen or put a status update here for the rest of us?

or raise a new issue (don't think there's an existing one)?

@timneutkens any updates?

Does it work for SASS ?

This will hopefully be covered by https://github.com/zeit/next.js/issues/8626


test(app): attestation mobile int test.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.18%. Comparing base (8baf56a) to head (c9f0046).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #750   +/-   ##
=======================================
  Coverage   89.18%   89.18%
=======================================
  Files         104      104
  Lines        4504     4504
=======================================
  Hits         4017     4017
  Misses        315      315
  Partials      172      172

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.