Unable to update / install beta6

Please provide us with the following information:

OS?
Windows 8

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.
λ ng -v
angular-cli: 1.0.0-beta.5
node: 4.2.2
os: win32 x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
I tried to update the cli version from beta 5 to beta 6 by issuing: npm update -g angular-cli

The log given by the failure. Normally this include a stack trace and some
more information.

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\NodeJs\node.exe" "C:\NodeJs\node_modules\npm\bin\npm-cli.js" "install" "-g" "angular-c
li"
npm ERR! node v4.2.2
npm ERR! npm  v3.9.3
npm ERR! path c:\NodeJs\node_modules.staging\abbrev-0137066c
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename 'c:\NodeJs\node_modules.staging\abbrev-0137066c' ->
'c:\NodeJs\node_modules\angular-cli\node_modules\npm\node_modules\abbrev'
npm ERR! enoent ENOENT: no such file or directory, rename 'c:\NodeJs\node_modules.staging\abbrev-0137066c' ->
'c:\NodeJs\node_modules\angular-cli\node_modules\npm\node_modules\abbrev'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Abdel\npm-debug.log
npm ERR! code 1

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

All problems solved after updating in this manner:
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest

On OSX 10.11.4, Node 5.4.1, NPM 3.9.5, NVM 0.31.1 I ran
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest
and hang about 25% of the way through on "loadRequestedDeps"

@olakara glad to hear it's fixed!
@JB-Tellez I will check your problem in the other opened issue, https://github.com/angular/angular-cli/issues/1110


Going back/forward in history fast

If you scroll backwards/forwards through history fast it seems to break things:

I'm using Chrome.

The demo uses Riot 1.0 and is no longer developed. I'll actually remove the demo completely to avoid confusions. There will be Riot 2.0 demos on the website once I start focusing on them. Thanks!

Removed it now :)

Okay, thanks @tipiirai . I thought the demo was using v2.0, I didn't bother checking yet.


[Feature] Control EmulationStation via HDMI CEC remote control

There's this cool feature of HDMI connection that allows to use the same remote control of the tv set to also control an external device. For example on Raspbmc you can use it and it is completely supported.
IMHO It would be super-awesome if on the Raspberry Pi we could use the TV remote control to navigate through the EmulationStation menus... I'm not suggesting that we should use the remote control instead of a joypad to play games, but it would be super handy to be able to move from Kodi (that already support CEC) to EmulationStation, back and forth without having to change the controller.
Maybe EmulationStation could support two different inputs, one from a joypad and one from a CEC enabled remote control.

I like this idea !

I support this idea. Having the exact same thoughts as @fmaida, i would like to navigate from Emulationstation to Kodi without having to switch controllers. Just installing cec-utils doesn't do the trick.

this is a really good idea

+1

Simply install libcec-daemon, and launch it on boot.  Works a treat.

The guy has got it: http://blog.recalbox.com/forums/topic/my-setup-and-perhaps-some-inspiration-for-new-recalbox-functionality/

Hey guys!
I have added native libCEC support to EmulationStation (without any other tools).
You can find it here: https://github.com/CeRiAl/EmulationStation

@CeRiAl Anny chance you can update it for libcec 3.0? It is required for Kodi 15.X.
I get build errors trying to compile it.
/home/tristan202/emulationstation/src/EmulationStation/es-core/src/InputManager.cpp: In member function 'void InputManager::init()':
/home/tristan202/emulationstation/src/EmulationStation/es-core/src/InputManager.cpp:17:28: error: 'CEC_CLIENT_VERSION_CURRENT' is not a member of 'CEC'
#define CEC_CONFIG_VERSION CEC::CEC_CLIENT_VERSION_CURRENT;
^
/home/tristan202/emulationstation/src/EmulationStation/es-core/src/InputManager.cpp:151:28: note: in expansion of macro 'CEC_CONFIG_VERSION'
gConfig.clientVersion  = CEC_CONFIG_VERSION;
^
/home/tristan202/emulationstation/src/EmulationStation/es-core/src/InputManager.cpp:178:72: error: 'cec_server_version' is not a member of 'CEC'
LOG(LogInfo) << "Initialized libCEC version " << gParser->ToString((CEC::cec_server_version)gConfig.serverVersion);
^
distcc[14289] ERROR: compile /home/tristan202/emulationstation/src/EmulationStation/es-core/src/InputManager.cpp on localhost failed
es-core/CMakeFiles/es-core.dir/build.make:192: recipe for target 'es-core/CMakeFiles/es-core.dir/src/InputManager.cpp.o' failed
make[2]: *** [es-core/CMakeFiles/es-core.dir/src/InputManager.cpp.o] Error 1
CMakeFiles/Makefile2:248: recipe for target 'es-core/CMakeFiles/es-core.dir/all' failed
make[1]: *** [es-core/CMakeFiles/es-core.dir/all] Error 2
Makefile:136: recipe for target 'all' failed
make: *** [all] Error 2

+1

#600

I would find this feature really useful. It's annoying when I click on the wrong menu entry in Kodi and launch emulation station by mistake, then have to hunt down my game pad before I can close out and go back to Kodi!

any progress so far?

Emulationstation isn't being maintained any more, so no.

What's the progress?
expect very much

Status of this repo:
https://github.com/retropie/retropie-setup/wiki/emulationstation#development-status
https://github.com/Aloshi/EmulationStation/issues/563#issuecomment-198787794
Some of the forks are being actively developed:
https://github.com/Aloshi/EmulationStation/network

Hi all. I wrote a program to do this at https://github.com/dillbyrne/es-cec-input
it is light on resources and only acts on remote presses when kodi or retroarch are not running.  It can run on boot as a non root user and has 2 dependencies in the repositories. I figured I'd share for others who are interested.
I only needed a,b,up,down,left,right,start and select for my purposes but it is easily extendible if you need more

@dillbyrne , @fieldofcows is doing a lot of work on RetroPie's Emulationstation branch, perhaps you could submit a pull request to him so others can test? :D I think CEC support is probably the third most requested thing after removing the Emulationstation splashscreen (now implemented!) and a fix for the white screen of death!


Update the endpoints

Some of the endpoints are not there anymore in the new KTHCloud.

https://k8s.cloud.cbh.kth.se
https://k8s.prod.cloud.cbh.kth.se
https://k8s.dev.cloud.cbh.kth.se
https://se-flem-probe.app.cloud.cbh.kth.se
https://se-kista-probe.app.kista.cloud/

Some of the other services should probably be managed by individual users. Or do we want a publish service which collects and toots based on the service.

https://taiga.prod.cloud.cbh.kth.se

I had to take emergency action and I have removed the above mentioned CSV. If this is acceptable then we can close this issue.
We should add the dancer to this list if possible.

These should definitely stay:
https://se-flem-probe.app.cloud.cbh.kth.se/
https://se-kista-probe.app.kista.cloud/
See https://github.com/kthcloud/go-deploy/issues/673 for why Kista is down

+1 for taiga not being our problem :)

Completed. But pushed directly to main branch.


[TS] SelectAction on Actions do not take precedence over body SelectAction

I am trying to make the whole card clickable by having selectAction on "body". I do have Actions (selectAction). When I click on the Action element then it also opens the selectAction url on body.
Below is the example. As you can see when clicking on the comment. The link on the body is triggered as well.
{
	"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
	"type": "AdaptiveCard",
	"version": "1.0",
	"body": [
		{
			"type": "Container",
			"items": [
				{
					"type": "ColumnSet",
					"columns": [
						{
							"type": "Column",
							"width": "stretch",
							"items": [
								{
									"type": "TextBlock",
									"text": "Matt Hidinger",
									"weight": "bolder",
									"wrap": true
								}
							],
                            "selectAction": {
                                "type":"Action.OpenUrl",
                                "title": "Profile",
                                "url": "example.com/member/123"
                            }
						}
					]
				}
			]
		}
	],
	"actions": [
		{
			"type": "Action.ShowCard",
			"title": "Comment",
			"card": {
				"type": "AdaptiveCard",
				"body": [
					{
						"type": "Input.Text",
						"id": "comment",
						"isMultiline": true,
						"placeholder": "Enter your comment"
					}
				],
				"actions": [
					{
						"type": "Action.Submit",
						"title": "OK"
					}
				]
			}
		}
	],
    "selectAction": {
        "type": "Action.OpenUrl",
        "title": "Card Details",
        "url": "example.com/card/123"
    }
}

@sravanthialuri can you please clarify what platform you are seeing this issue on? Thanks.

I confirmed it repro's on TS.

Fixed


Fix async external filter on typing falling back to sync

When using external async filters vim-clap will revert back to the sync internal filter unless the provider returns more than 10000 entries.
From what I could tell internally what is happening is that vim-clap is storing some cache in memory and if there is cache it will always run synchronously. This results in losing fuzzy matching when using external filters(unless you have the internal one written in phyton).
With this PR if there is a external filter set then even if there is cache the filtering will be done async.

Merged, thanks! By the way, once #147 is merged, vim-clap will be able to handle 200,000+ items decently using the built-in fuzzy filter. If the rust extension is installed, then you don't have to use the external filter. I believe people will have more motivations to install Python and Rust :(.


Sorting by "oldest" kata shows newest first instead

Selecting "Sort by: Oldest" on the kata search page instead shows the newest kata first.  Here's the URL:
http://www.codewars.com/kata/search/?q=&order_by=published_at+desc

I think this was meant to be asc instead of desc.  Otherwise it's approximately the same ordering as "Sort by: Latest".  The only difference is that "latest" seems to sort by modification date for approved kata instead of publication date.  For beta kata the ordering is the same either way so it's easier to see the bug if we filter for beta kata only, as below.
http://www.codewars.com/kata/search?q=&beta=true

http://www.codewars.com/kata/search?q=&beta=true&order_by=published_at+desc

Sorting by "oldest" should be the opposite of "latest", not the same.

Fixed


EKS Node Group should ignore_changes on status

Description
It seems like Terraform/OpenTofu wants to report changes to the status of an EKS node group as diffs, even though this is state managed AWS-side that Terraform can't directly affect:
Note: Objects have changed outside of OpenTofu

OpenTofu detected the following changes made outside of OpenTofu since the
last "tofu apply" which may have affected this plan:

# module.sandbox.module.eks.module.eks_managed_node_group["spot"].aws_eks_node_group.this[0] has changed
~ resource "aws_eks_node_group" "this" {
     id                     = "sandbox-eks:spot-k8s-nodes-20240125181518727500000013"
   ~ status                 = "DEGRADED" -> "ACTIVE"
     tags                   = {
         "Name" = "spot-k8s-nodes"
     }
     # (15 unchanged attributes hidden)

     # (4 unchanged blocks hidden)
 }

(This is part of a much larger configuration, but we see this diff sometimes when one terraform run happens when spot instances are being replaced and then the next plan happens once the node group is fully up to strength.)

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: 20.24.0

Terraform version:

tofu version
OpenTofu v1.8.1
on darwin_arm64

Provider version(s):

OpenTofu v1.8.1
on darwin_arm64
+ provider registry.opentofu.org/hashicorp/aws v5.64.0
+ provider registry.opentofu.org/hashicorp/helm v2.15.0
+ provider registry.opentofu.org/hashicorp/kubernetes v2.32.0
+ provider registry.opentofu.org/hashicorp/null v3.2.2
+ provider registry.opentofu.org/hashicorp/time v0.12.0
+ provider registry.opentofu.org/hashicorp/tls v4.0.5
+ provider registry.terraform.io/hashicorp/aws v5.64.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.3.4
+ provider registry.terraform.io/hashicorp/helm v2.15.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.32.0
+ provider registry.terraform.io/hashicorp/null v3.2.2
+ provider registry.terraform.io/hashicorp/time v0.12.0
+ provider registry.terraform.io/hashicorp/tls v4.0.5

Reproduction Code [Required]
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "20.24.0"

  cluster_name    = "${var.cluster_name}-eks"
  cluster_version = var.eks_version

  vpc_id                         = module.vpc.vpc_id
  subnet_ids                     = module.vpc.private_subnets
  cluster_endpoint_public_access = true

  # Allow the default policy so users other than the cluster creator can
  # describe the cluster's KMS key
  kms_key_enable_default_policy = true

  eks_managed_node_groups = {
    spot = {
      name   = var.k8s_node_params.name
      create = var.k8s_node_params.use_spot

      instance_types = var.k8s_node_params.instance_types
      capacity_type  = "SPOT"

      min_size     = var.k8s_node_params.min_size
      max_size     = var.k8s_node_params.max_size
      desired_size = var.k8s_node_params.desired_size
    }
}

Steps to reproduce the behavior:
We are running terraform plan and terraform apply from GitHub Actions on PRs / submit.
Expected behavior
No reported diffs even when EKS node groups using spot instances are being cycled.
Actual behavior
We sometimes see the above diff, with no real way to avoid it.
Terminal Output Screenshot(s)
See above
Additional context
I suspect this mostly happens with spot instances, as on-demand / reserved instances won't disappear out from under the node pool in the same way.

this is normal Terraform behavior - nothing that we can control here


Add tests for kubectl command on forbidden verbs and resources

ISSUE TYPE

Bug fix Pull Request

SUMMARY

Added a e2e test kubectl command with forbidden verb and forbidden resource. Another one for kubctl command with allowed verb and forbidden resource

Fixes #350

Thanks for the PR @anoopmsivadas :pray:

@anoopmsivadas Could you please rebase with develop and push again?

Hello @anoopmsivadas ,
Thanks again for the PR!
Thank you for contributing to BotKube. Could you please fill out this form, so we can send the well deserved awesome swags :slightly_smiling_face:
Team BotKube


Allow node >=6

Ran in to this error while trying to install with yarn
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "> 6".

Ran with
Node: 6.11.2
Yarn: 1.3.2

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[2024a] sync 2024a branch with main branch commits

Description
[2024a] sync 2024a branch with main branch commits
How Has This Been Tested?

Pre-tested
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Merging to get the build ready.


Update internships page for new cycle

Trello card
https://trello.com/c/LerGsCzZ
Context
We need to update the internships page to support the opening of applications for the new cycle.
Changes proposed in this pull request
Guidance to review

One further comment @philspray - did we not want to add this to the Train to teacher category page? Happy to discuss if you disagree!

One further comment @philspray - did we not want to add this to the Train to teacher category page? Happy to discuss if you disagree!

Do we want to move the page now as it moves again to 'Is teaching right for me' as part of the navigation changes?


Changing logger config to relative path

Changing to relative path since we don't use Docker directly. Otherwise, we would bump into a permission error when it will try to access logger files.

 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.

My bad, wrong directory for the pull request.


Add missing headers for gcc v12.

A tiny fix for failing gcc v12 series.
Thank you.
~cristian.

Hi Cristian,
Thanks for your contribution, please read https://arm-software.github.io/ComputeLibrary/latest/contribution_guidelines.xhtml
Here on github we only publish a snapshot of the main development branch for each release, that's the reason why we don't accept pull requests.
The development repository is https://review.mlplatform.org/admin/repos/ml%2FComputeLibrary
Please submit your patch for review to review.mlplatform.org.


Cleanup simulation

remove excess flexibility and add it where needed

There's also a neverworld implementation in ClimaOcean

We decided on Friday to go ahead with this setup since the people using it are already familiar, and we have results we deem plausible.
I guess in the meantime we can make sure that the same results are obtained in ClimaOcean


Adding make staticcheck

This finds (but I haven't corrected yet) errors like 'err' being
assigned and then ignored.
I'd like to add this to our CI routine, in an effort to end-run certain simple
problems.

Codecov Report

Merging #351 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #351      +/-   ##
==========================================
- Coverage    61.6%   61.57%   -0.03%
==========================================
  Files         162      162
  Lines        8805     8805
==========================================
- Hits         5424     5422       -2
- Misses       2945     2947       +2
  Partials      436      436

Impacted Files
Coverage Δ

lib/auto_resolver.go
88.05% <0%> (-1.5%)
:arrow_down:

Continue to review full report at Codecov.

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


Submit a model for Sound Demixing Challenge

For now I cloned repository and figured out how to do a submit but for now we don't have model other than demucs, so this doesn't make much sense for me to submit it.

Done


fix url parse error when port specified

Thank you! Unfortunately this was already fixed in #252. Will be released soon.


Add support for Visual Studio 2019

Closes #9
This PR covers the following changes

Widen range of InstallationTarget
Widen range of Prerequisite
Bump version one minor unit

Dear mniak, thanks a lot for your contribution!!!
Unfortunately, I cannot approve it, since it does allow the installation on VS2019 RC. The current version I'm using of the RC, is 16.0.0 RC.2 .
Did you tried it and worked? Which version were you using?
Again,thanks a lot.
P.

BTW,  after updating the source.extension.vsixmanifest, it still does not work...

Reading this article, maybe the <Prerequisite> has to be open ended?  I woudln't think so but maybe?

Dear contributors, I already achieved that the installer allowed me to install the extension on VS2019. Unfortunately, after installing it, it was not available anywhere in the VS... not even in the extensions section, though it didn't allow me to reinstall it again... So extrange!!
Any of you have any clue on what can be happening?

Hello mniak, I've already approved a PR that I could test successfuly.
I'm so sorry to approve the other one before yours. I just realized (after approving), that the checks I made with your PR were completly wrong, and that's the main reason it didn't work for me...
Anyway, I want to specially thank you for your effort, and I hope you will do tons of more PR.
Regards,
P.

No problem, @pauer24.
The important thing is that the fix/update was made.
Thanks for the nice project. ✋


Can you call net.train multiple times to add new data

What is wrong?

Documentation Confusion
Where does it happen?

Can you call net.train multiple times on the same net to add new learned data
How do we replicate the issue?

I could write the code for the neural network, but I'm unsure how to test if it retains data.
How important is this (1-5)?

4ish, but really great as we are using it on a hydraulic machine and would like to retrain with real time data.
Expected behavior (i.e. solution)

I think you are so intelligent that you don't need intelligience, but no.  I think it would be nice if this is a feature, if not its not a deal breaker.
Other Comments

Thank You for this.  Solves my problem as I do expect historical data to be accurate.
I will check with management on how much info I can provide.

Added image.


Option to use the old clipboard history feature

Description of the new feature / enhancement
Option to use the clipboard history feature developed by powertoys and not the windows one.
Scenario when this would be used?
Same times you would use it when windows's is used, but also when you want to use the paste something as text from clipboard history.
Supporting information
Theres no idea when they will implement this feature, but the tool already exsists and this would bridge the gap of windows's version having same functionality.

Why would PowerToys have a clipboard history separate from the Windows clipboard history? Also Paste as Plain Text is already a PowerToy. What am I missing here? /needinfo

Atleast my version of windows 10 does not have a clipboard history where you could copy something from past as text, so not the most recent copied thing - which paste as plain text does cover, but something you copied like two ctrl+v's back.

to that point I believe this issue is a duplicate of another issue.
/dup #671


5.1 initial support

Display date, state, and election type for 5.1 feeds in the feeds list, and create a bare bones feed overview page for 5.1 feeds which only include a link to the error report.
Pivotal stories: 122156869, 123266571

LGTM. 🐧


cmd/compile: unnamed functions missing FuncInfo

Context: I am adding additional information to runtime.inlinedCall (function start line), which I am plumbing via the FuncInfo. In the linker, this FuncInfo.Valid() got me thinking that (IMO) inlined functions ought to always have a FuncInfo, since they must be Go functions, so I switched the check to panic if it is missing.
This program fails that check:
package main

func main() {
        var i int
        fn := func() { i++ }
        fn()

        func() { i++ }()
}

panic: inlined function main.main.func2 missing func info

goroutine 1 [running]:
cmd/link/internal/ld.genInlTreeSym(0xc000510000?, 0x200000010?, {0xc000510000, 0xc000166080, {0xc00016888d, 0x48, 0x48}, {0x1, 0x10, 0x2, ...}}, ...)
        /usr/local/google/home/mpratt/src/go/src/cmd/link/internal/ld/pcln.go:172 +0x419
cmd/link/internal/ld.makeInlSyms(0xc000158000, {0xc000a5a000, 0x40c, 0x40c?}, 0x20?)
        /usr/local/google/home/mpratt/src/go/src/cmd/link/internal/ld/pcln.go:194 +0x245
cmd/link/internal/ld.(*Link).pclntab(0xc000158000, {0xc000105900?, 0x1?, 0xf?})
        /usr/local/google/home/mpratt/src/go/src/cmd/link/internal/ld/pcln.go:786 +0x1e6
cmd/link/internal/ld.Main(_, {0x20, 0x20, 0x1, 0x7, 0x10, 0x0, {0x0, 0x0}, {0x6886dd, ...}, ...})
        /usr/local/google/home/mpratt/src/go/src/cmd/link/internal/ld/main.go:328 +0x144a
main.main()
        /usr/local/google/home/mpratt/src/go/src/cmd/link/main.go:72 +0xedb

The first closure (fn) has a FuncInfo, but the second does not. This seems like a bug to me, though it probably had low impact before because FuncID would default to FuncID_normal anyways.
I am still digging, but it looks like this is somewhere in the compiler, as func2 never makes it to ssagen.InitLSym, which sets up the FuncInfo.
cc @golang/compiler @cherrymui

Note to self: enqueueFunc skips both func1 and func2 because they aren't trivial closures. The later loop prepares func1, but for some reason func2 never ends up in next.Closures.

@prattmic Without looking too closely, I think it's because the directly called closure gets inlined and then we know there won't be any other references to it, so we intentionally drop references to it from the AST because we know we don't need to compile its function body on its own. (Contrast that the indirectly called closure gets inlined too, but we don't do any frontend analysis to realize that was the only possible use.)

The place where the direct call closure is replaced: https://cs.opensource.google/go/go/+/refs/tags/go1.19.1:src/cmd/compile/internal/inline/inl.go;l=596


SetRecords: update records when an existing ID was specified

fixes #1

I manually tested that:

Records are created when they are not present.
Records are updated when you specify an ID.
The ID is fetched and records are updated when you do not specify an ID.


Polygon tooltip out of place (after zooming in) when map in initialized with a low zoom level

Steps to reproduce

Initialize a map with a low zoom level (1, 2, or 3)
Add a few polygons close to each other, that spans across a city somewhere in the world
Add a permanent tooltip to the polygons (issue seems to be with permanent tooltips)
Now zoom down to the polygons to see all of them
You will see the tooltips are out of place

Expected behavior
The tooltips should be inside the polygon bounds
Current behavior
They are not within the body/bounds of the polygon
Environment

Leaflet version: 1.7.1
Browser (with version): Chrome Version 88.0.4324.192
OS/Platform (with version): Mac 10.15.7

Minimal example reproducing the issue
https://codesandbox.io/s/friendly-solomon-s71um?file=/src/App.vue

Duplicate of #5216


Running multiple queries at once

Is your feature request related to a problem? Please describe.
It is quite frustrating not being able to run multiple queries at once. When writing a full sql script, it is often a requirement to build tables as you go before arriving at the final product. Running queries one by one is very inefficient and slows down any updates
Describe the solution you'd like
I would like to be able to highlight multiple queries, separated by a semi-colon (;), hit run queries once in order to run the highlighted queries sequentially

Which database driver are you using?

Hi @gjsjohnmurray - thanks for getting back quickly. I'm using the snowflake driver. Thanks, Freddie

Please raise this at https://github.com/koszti/sqltools-snowflake-driver


Add in two new properties to the TEXT node to sync with Figma Official API

Fixes https://github.com/didoo/figma-api/issues/42

Released in 1.10.0 .
Please @brandon-pereira let me know if everything is fine.

@didoo I noticed one small issue, will open a new issue and PR

@brandon-pereira released a patch: 1.10.1


Acro: SuperExpo Stick Input

To do actual acrobatic moves you need to have high rotation rate inputs available which was until now achieved by setting high MC_ACRO_X_MAX parameters (X being R,P,Y). The problem with this is that you very fast loose sensitivity around the stick center to keep the vehicle stable and smooth with your small corrections.
That's why people flying model helicopters and race quads like to use a so called exponential curve.
https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/19890199/Expo+setup
It's nothing else than rescaling your stick input depenting on the stick deflection. What it does mathematically is a linear combination of a linear function and a cubic function between your -1 to 1 stick values.
For more details refer to https://github.com/PX4/Firmware/pull/6440 and https://github.com/PX4/Firmware/pull/6625 where the expo input curve was already introduced for position controlled flight.
My tests so far are using jmavsim on very low resolution to reduce delay and a ***** xbox controller and it seems to work as far as it's possible to tell with bugging sticks and input delay. Looking forward to test this on the racer build https://dev.px4.io/en/airframes_multicopter/qav-r-5-kiss-esc-racer.html tomorrow.
@bkueng I plan to use this for further FPV performance tests.
mc_att_control: use expo input for acro mode to allow for high input rates without loosing input sensitivity

Today while studying my current input rate settings I fly with in a tool I realize there's more to the very good control feel than just expo. Flyduino uses an additional f(x) = 1/(1-abs(x)*g) function to further enhance the input curve. While I totally see why they do this because the resulting curve feels very intuitive to fly I don't like the functions parameter g adjusting the maximal anglular output rate. I have to come up with a good way to parameterize the input function such that maximum and shape can be easily tuned.

I added a so called SuperExpo function for further stick input curve shaping which makes it in my opinion much more intuitive.

Reference implementations

KISS FC rc curve http://ultraesc.de/KISSFC/rates.html (see javascript source for formula)
betaflights implementation (thanks @bkueng for showing me)
https://github.com/betaflight/betaflight/blob/master/src/main/fc/fc_rc.c#L128

KISS uses exactly the following formula: y = r * 200 * (x*x*x*e + x* (1-e)) * 1/(1-abs(x)*g);
interactive plot: https://www.desmos.com/calculator/zuqgbayd9g
and betaflight almost the same just with x^4 as expo which is a small difference in stick feel.
r*200 is basically to set your linear range of setpoints
(x*x*x*e + x* (1-e)) is the basic cubic expo
1/(1-abs(x)*g) is the superexpo term
The problem with this formula in my eyes is that it's not intuitively clear what maximal setpoint you'll have from the function parameters r, g and e. That's also why they have to supply users with the tools to thinker around https://kiss.flyduino.net/dwkb/ratetool/ . r changes the linear stpoint range in their formula as a factor of 200deg/sec, g changes the scale in a non-linear way which is horrible to tune and e does not change the scale when operating in [-1,1].

Adjustments
Hence I adjusted the superexpo term to preserve scale and only change curve shape which is what the user wants to achieve: (1-g)/(1-abs(x)*g) and made r*200 adjust to our maximal rate setpoint parameters. Which means that the maximal rate setpoints are defined by MC_ACRO_X_MAX and only the shape of the curve is adjusted by e - MC_ACRO_EXPO and g - MC_ACRO_SUPEXPO.
interactive plot: https://www.desmos.com/calculator/yty5kgurmc
The branch is only tested in jmavsim with an xbox controller yet. The feel enhanced a lot even with this **** quality gamepad. We should consider to also test this for position control input in the future to make manouvering easy but still have a high maximal velocity setpoint.

CI fixed, ready for outdoor test.

outdoortest went wrong... the RC curve worked, I did a roll flip and ~10 seconds later the racer dropped out of the sky and crashed...
Log: https://logs.px4.io/plot_app?log=b641202a-d22c-4556-964f-cd136a96cb9c
It's not accidental disarm and you can see the motors stop one second before the log stops...

@MaEtUgR For the spike in the thrust output, it should not be related to the mixer since the spikes comes before it. In rate control, isn't the thrust directly a scaled version of the throttle stick?
However, the motor disarm part is most likely from the mixer and looks induced by the spike.

@bresch I assumed the same, the thrust should come directly from the stick and also the yaw did not command such a peek, while I touched yaw in this pr I did not touch thrust at all. I know the torque logging is before the mixer...
How coan the mixer disarm?? That's new for me.

I'm pretty sure that the problem you encountered is unrelated to this PR nor the mixer PR. Since everything happens at the exact same time, it looks more like a glitch deeper in the autopilot.

@bresch I agree.
@bkueng found a plausible scenario that I would also assume happened:
I configured the arm switch, it reacts on a switch transition because in position control you cannot diarm and I wanted to still allow stick arming. For the flight I let the switch on disarmed and armed by stick. We had two FrSky Taranis both correctly bound to their respective vehicle (we are sure about that). The other Taranis could have been turned on in this moment and caused a twitch in the arm switch channel. The twitch first caused a transition to armed and then one back to disarmed (in which state the switch still was). The resulting state is disarmed.
That would explain everything and that's why I quickly tried to reproduce in a bench test. What I got is a message in QGC (while turning the other Taranis on and off) that transition from ARMING_STATE_ARMED to ARMING_STAT... is not allowed, sadly the rest of the message was cut and it seems to be not easy to reproduce... We need to be cautious with kill switch and armed switch if RC is not reliable. And see how we can reproduce the issue for safety measures.
It has most likely noting todo with this pr and as I repaired the vehicle I can test again without risking the same issue.

Thanks for the update @MaEtUgR. I agree, I don't see a way how this, or the mixer PR could have caused it.
I see an RC glitch, which happened between 2 logged messages (since we don't log all RC messages) as the most likely cause.


Booster meta data belongs into catalog

Currently the booster meta data resides with each booster, but from my point of view it belongs into the catalog:
name: HTTP CRUD - Wildfly Swarm
description: A simple CRUD application using Wildfly Swarm
versions:
  - id: community
    name: 2017.9.5 (Community)
  - id: redhat
    name: 7.0.0.redhat-6 (RHOAR)

All of the above has to kept redundantly in the each booster branch (community/prod) while it's  really an overarching concern. I suggest we move this data into the catalog, rather then keeping it with each booster.

The reasoning for this is documented here: https://docs.google.com/document/d/19o6UXVykkCqp2ZxBcS8ZS5AyEz8nIyoNx9liQjCG7AQ/edit#heading=h.z1z4cdkqs18w
But perhaps it's unreasonable to assume that within a single runtime boosters could be using different versions of that runtime? So perhaps we could move them to the metadata file as sub-items of the runtimes?

I think there can be different versions. But why would that prevent us from moving the meta data to the catalog itself? I.e. in [1] it could read:
githubRepo: wildfly-swarm-openshiftio-boosters/wfswarm-rest-http
gitRef: master
id: community
name: 2017.9.5 (Community)

Or am I missing something here?
[1] https://github.com/openshiftio/booster-catalog/blob/master/rest-http/wildfly-swarm/community/wildfly-swarm-rest-http-community.yaml

Ah, I thought the main thing was to get rid of the redundancy, because doing it that way you'd still have multiple "name: 2017.9.5 (Community)" entries in the different .yaml files, right?

Yes, you would still have the entries in different yaml files. The main difference (and motivation) is to keep it close to the catalog, which seems to be the only client to that information. And to me  it seems that the point in time when this meta data changes, is when the catalog is updated to new versions of a booster.

In a near future we want to automate the booster-catalog repository maintenance. This would include creating PRs when boosters are tagged but that would make things more difficult if the version is specified inside the catalog, no?

I'm not sure @gastaldi , you mean because you could be upgrading the code to upgrade from eg "name: 2017.9.5 (Community)" to "name: 2017.10.2 (Community)" which then would only mean a change to the booster itself (because you can change the name in the booster.yaml itself) while putting it in the catalog would mean updating the catalog as well, right?

@quintesse yes, that's my point

I think there are two use cases:
a) catalog references boosters that reside within a tag
b) catalog references boosters that reside within a branch
For a) a new release of a booster leads to change to the catalog. For b) not necessarily.

I think @gastaldi point is only valid for b), no?

Yeah, that's why I think it is much easier to have this information in a single place (the booster repository) instead of in the catalog.

Easier depends on the point of view.  As I said: For people using tagged boosters it's not the case. Here you need to update the catalog anytime you release a new booster. And I am arguing the main case is tagged releases.
See I release rest-http v12 and now have to  update both the catalog to reference the tag v12 but also make sure the booster tag contains the meta data that says v12

But I get your point. There are arguments for both cases. Feel free to close this issue

Yes, when we introduce webhooks to the booster repositories we can make the booster-catalog updates automatically, but we would be missing context if the version is another parameter to be changed in the catalog.

I'll close it for now and revisit this if the scenario changes

Thanks for the thoughts @heiko-braun @quintesse


Editor freeze on opening html file

Lenovo G550. 4gb ram. Intel graphics.
Atom 0.999.
Opening small html 41kb. On opening html editor freeze for for few minutes and showing one popup()

@sumanparia Can you reproduce the problem in the latest version of Atom (0.201.0) in safe mode? If so, can you share a link to the file in question? Does the file perhaps have a very long line in it?

Closing since no information about reproducing this was provided in over 3 months, and I'm guessing this is a duplicate of https://github.com/atom/atom/issues/979. @sumanparia If you can still reproduce this with Atom 1.0.11 -- it would be great if you could provide the file which causes this for you.


Updated Form translations

This PR services this issue: https://github.com/VueVixens/website/issues/70
for historical purposes I want to link here the original PR that we worked over and ultimately @alexandriaroberts re-created in this new PR. Previous PR found here: https://github.com/VueVixens/website/pull/87

Thank you very much @MicheleCynowicz ! 😊🎉


update samples to use npm

currently the samples reference the client directly via the  please consider updating the samples to use the published npm package and give guidance on using the npm package within a project

:+1:


Duplicate Content on Commit Message Standardization

https://github.com/microsoft/code-with-engineering-playbook/blob/master/code-reviews/pull-requests.md
has content on commit message standardization - so does https://github.com/microsoft/code-with-engineering-playbook/tree/master/source-control - we should consolidate them to one

Commit Message  belongs to Source code section and suggest to move it there from code reviews with relevant content. @TessFerrandez  let me know what you think - I can create appropriate PR suggestion then.