gulp.watch(...) not working on Windows

gulp.watch doesn't seem to work for me, and I think it's a Windows-related issue. If I use the example gulpfile.js from the readme, create the directory structure (client/js, client/img, build/js, build/img), and a dummy js file in the client/js folder, the gulp scripts task runs normally and minifies the script, but gulp watch fails to update the minified file when the original changes.
The console output:
>gulp watch
[gulp] Using file C:\Users\JP\Documents\gulptest\gulpfile.js
[gulp] Working directory changed to C:\Users\JP\Documents\gulptest
[gulp] Running 'watch'...
[gulp] Finished 'watch' in 17 ms

There is no prompt afterwards, it continues "running", but it doesn't do anything.

I have a similar problem too
node v7.2.1
gulp v3.9.1
Windows 10 64-bit

I downgraded to node 6.9.2 and that seems to have fixed the problem.

Looks like this is the issue that some google search results will lead to (how I got here). For reference, and if you still can't reopen the issue, could we get a link to the currently open issue that does regard this, if any exists? Still a problem.  Similar specs as @justindra
node v6.9.1
gulp: CLI v1.2.2
gulp: Local v3.9.1
Windows 10 (x64)

Same issue happening here:
node v6.11.4
gulp -g: 3.4.1
Windows 10 (x64)

Hey guys I find a possible solution to us:
Within your CMD settings uncheck the "Quick Edit mode" box and watch/batch processes should work properly.

Interestingly @jungleBadger I just noticed that the Windows built-in CLI (cmd.exe) worked fine for me regardless of the Quick Edit mode setting :thinking: Then it stopped working again.
I've normally been having this problem consistently when utilizing Jet Brain's (or specifically: PhpStorm) integrated terminal window. Maybe this is some kind of race condition where gulp skips a few cycles and misses the change hooks/notifications coming in from the file system due to slowdowns or some kind of interference in the terminal window (e.g. cmd.exe or otherwise) executing gulp?

@patricknelson it does happen to me in any cmd (git bash, cmd, powershell) that I use.
And in fact I do use jetbrains (webstorm) IDE.

🎉 Alright, I've fixed my issue.
Turns out it wasn't related to  gulp.watch(...), I was using watchify this entire time (oops 🤕). That said, @jungleBadger I think we might have the same problem (judging from your screenshot which revealed you may be using browserify/watchify as well). I believe the issue we were having may be related to https://github.com/browserify/watchify/issues/312.
I fixed my issue by converting my code to gulp-bro which has a much simpler syntax and works like a regular gulp plugin. That way I simply use the native gulp.watch(...) API to watch for changes and trigger rebuilds 👍

hey @patricknelson I will change it and give it a try.
Without the "edit mode" option my browserify/watchify routine ran much better and consistent but it stills does not recognize properly sometimes, and to bypass those situations I need go to code and put a new line anywhere then the build is triggered just fine.
I will give a try to gulp-bro later and let you know if it worked (working on macbook right now).
Thanks!!

I resolved this problem after the renamed name of the task from "watch" to "watch-all" looks like gulp doesn't like a name "watch".
My working example:
 gulp.task('watch-all', function () {      gulp.watch(paths.scripts, ['scripts']);      gulp.watch(paths.images, ['images']);      gulp.watch(paths.sass, ['sass']);  });

Gulp.watch() isn't working for me either. I am using Git Bash & Window 10 (64-bits).
Another related info:
Node v10.15.3
NPM 6.4.1
Gulpjs 3.9.1
Does anybody knows if this issue was resolved or there is any workaround? Thanks in advance!


Hot Fix: Pinning Python Packages

This PR solves issue #7 and #11
Pip is installing the latest version of llvmlite and numba which is creating conflicts. I've pinned both the packages to the ONLY version docker-compose build executed to its completion.

Thank you for fixing the bug! I'll check in my environment.

Looks good to me! Awesome! ✅

@meokz You're welcome. :)
My fix will break after a few months. Pip is going to stop support for python3.5 soon.

@xlabd
Actually, I like static type systems, so I want to upgrade to python3.6 or higher.
However, due to the strong restrictions of libraries such as Cuda, it does not work when changing the python version😂


Merge branch feature/spring-cloud-azure-passwordless-connection to main branch

As title.
Follow-up task:

[ ] We need to update changelogs after the PR is merged.

/azp run java - spring - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-identity-providers-core

/azp run java - spring - tests

/azp run java - spring - tests

/check-enforcer override


Uploaded Image Check

$ipfs->add(Utils::tryFopen('ipfs.png', 'r'), 'ipfs.png', ['pin' => true]);
After upload image, I get Result Hash QmWyLdiujgReZVDisA..........
When I check the uploaded image, I am seeing like this C:\xampp\tmp\php59DB.tmp
https://ipfs.infura.io/ipfs/QmWyLdiujgReZVDisA..........
Can you please explain about this action?
Thank you in advance

@BestSilverTiger Can you tell me a bit more about your problem?
I'm not really understanding the question


update dotnet-install script and use beta channel

/cc @victorhurdugaci @davidfowl
This is using the install script from https://github.com/dotnet/cli/pull/1228 optimistically :). If that gets changed before merging I'll update it here.
Both scripts default the CHANNEL value to beta. But it can be overridden by an environment variable (CHANNEL ;))

ping?

pong

:shipit:


RTL placement of custom procedure definitions onto workspace

Expected Behavior
Custom procedure blocks in RTL should be placed similarly to blocks in LTR except in the top-right corner of the visible workspace instead of the top-left corner.
Actual Behavior
#1677 helps with this issue a bit as the first block (without scrolling the workspace) gets placed in the top-right corner of the workspace, but subsequent custom procedure blocks are placed far away off screen (possibly around/more than the width of the visible workspace view).
Steps to Reproduce
Add a custom procedure block to a sprite's workspace when in RTL mode.

/cc @paulkaplan

See https://github.com/LLK/scratch-gui/pull/4542/commits/ceb19b7561c3e4a94444fb5f84cee566841142cf for my fix in "share the love"; this math change can probably be implemented in scratch-blocks too.


Redundant Class_Name Error

Please paste the output from your clipboard## Issue Description ##
Steps to Reproduce

Create a project with namespace e.g: BLA_BLA.Lib
Create a file named X.cs either the terminal or vscode built-in Add new file button
Write your using statements, and namespace
type de word class and press "TAB" for auto completion
The result, is a class, also named X

Expected Behavior

No syntax highlight errors

Actual Behavior

A syntax error, which is NOT an actual compiling error around the class name, and the class members
The error says, that an existing class is already in the namespace, which isnt true, at all.

Logs
The namespace 'BLA_BLA.Lib,' already contains a definition for 'X' [ BLA_BLA.Lib,  BLA_BLA.Lib] csharp(CS0101)
OmniSharp log
Post the output from Output-->OmniSharp log here
C# log
Post the output from Output-->C# here
The namespace 'BLA_BLA.Lib,' already contains a definition for 'X' [ BLA_BLA.Lib,  BLA_BLA.Lib] csharp(CS0101)
Environment information
VSCode version: 1.72.2
C# Extension: 1.25.0
Mono Information
        There is a problem with running OmniSharp on mono: Error: Unable to find Mono. Ensure that Mono's '/bin' folder is added to your environment's PATH variable.
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   6.0.110
 Commit:    ce0a42998a
Runtime Environment:
OS Name:     ubuntu
OS Version:  22.04
OS Platform: Linux
RID:         ubuntu.22.04-x64
Base Path:   /usr/lib/dotnet/dotnet6-6.0.110/sdk/6.0.110/
global.json file:
Not found
Host:
Version:      6.0.10
Architecture: x64
Commit:       5a400c212a
.NET SDKs installed:
6.0.110 [/usr/lib/dotnet/dotnet6-6.0.110/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.10 [/usr/lib/dotnet/dotnet6-6.0.110/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.10 [/usr/lib/dotnet/dotnet6-6.0.110/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info

Visual Studio Code Extensions

Extension
Author
Version

cmake
twxs
0.0.17

cmake-tools
ms-vscode
1.12.27

cpptools
ms-vscode
1.12.4

cpptools-extension-pack
ms-vscode
1.3.0

cpptools-themes
ms-vscode
2.0.0

csharp
ms-dotnettools
1.25.0

dotnet-test-explorer
formulahendry
0.7.8

jupyter
ms-toolsai
2022.9.1202862440

jupyter-keymap
ms-toolsai
1.0.0

jupyter-renderers
ms-toolsai
1.0.10

makefile-tools
ms-vscode
0.6.0

python
ms-python
2022.16.1

sqlite-viewer
qwtel
0.1.5

vscode-docker
ms-azuretools
1.22.2

vscode-jupyter-cell-tags
ms-toolsai
0.1.6

vscode-jupyter-slideshow
ms-toolsai
0.1.5

vscode-pylance
ms-python
2022.11.10

vscode-thunder-client
rangav
1.20.1

I had same issue, its highlight error "already contains a definition" but project builds wia CLI

Unable to reproduce with the current release. If you are still having problems, please open a new issue at https://github.com/omnisharp/omnisharp-roslyn/issues


Add option to use full-infinite (4x4) environment in CTMRG

In the supplemental material of arXiv 1402.2859, it is stated that using half-infinite (2 x 4) environment to find projectors in CTMRG is "less accurate":

A computationally cheaper variant of this (but less accurate) is to compute the QR decomposition shown in Fig. 1(b) only based on the upper left corner (made of 4 tensors), and lower left corner (made of 4 tensors), instead of the upper and lower half of the 4 × 4 network.

Although #73 claims that full-infinite (4 x 4) environment can be less stable for differentiation, in full update (involving only the forward pass) it can still be a useful option. I suggest the following changes:

Add an attribute half_infinite::Bool to struct CTMRG;
The 4x4 environments can be obtained by further contracting QQ with two more enlarged corners in the function ctmrg_projectors in src/algorithms/ctmrg.jl. Alternatively, you can also write a lot of overloaded fullinfinite_environment functions, but I'm not sure this approach is better for future maintenance...

Hi Yue,
This is definitely a good idea. We had some pre-planning on how we would like to achieve something like this, utilizing the projector_alg defined here. The idea would be that we define a separate "full" from the "half" struct, on which we can then specialize.

Thank you for the idea. I will try to add full-infinite environment projectors in the coming days. I should be able to get the PR done by the end of this week (hopefully) :)

This is now merged into master with #99. Feel free to try this out @Yue-Zhengyuan!


False Positive on io.jsonwebtoken:jjwt

False positive on library jjwt.jar - reported as cpe:2.3:a:json-jwt_project:json-jwt:0.9.1:*:*:*:*:*:*:*)
      <dependency>
        <groupId>io.jsonwebtoken</groupId>
        <artifactId>jjwt</artifactId>
        <version>0.9.6</version>
      </dependency>

The CVE is for a Ruby library (nov/json-jwt): https://nvd.nist.gov/vuln/detail/CVE-2018-1000539
NOTE: I have not tried the newer versions of this library which split the monolithic jar into multiple sub-projects.

It is worth noting that the multi-module io.jsonwebtoken JJWT library (0.10.6) does not trigger a false positive.


Better diagnostic output for Publish-Module

Sadly most of my day was exhausted by resolving this issue. As it worked in some PowerShell modules and not others, and lack of diagnostic output obfuscated the cause. Eventually I resolved it by what I mentioned here.
Using the Debug switch in an addition to Verbose didn't help.
Steps to reproduce
Apparently have an outdated version of PowerShellGet and/or Nuget
> Publish-Module -Path 'E:\marckassay\XAz' -NuGetApiKey 'XXXXXXXX-XXXX-XXXX-XXXX-XX...XX' -Verbose

Expected behavior
Successfully publish to repository. At the very least, output a warning about outdated PowerShellGet (or dependency).
> Publish-Module -Path 'E:\marckassay\XAz' -NuGetApiKey 'XXXXXXXX-XXXX-XXXX-XXXX-XX...XX' -Verbose
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'True'; IsRegistered = 'True'.
. . .
VERBOSE: Successfully published module 'XAz' to the module publish location 'https://www.powershellgallery.com/api/v2/package/'. Please allow few minutes for 'XAz' to show up in the search results.
>

Actual behavior
After executing Publish-Module, it just hangs on the last verbose line below.
> Publish-Module -Path 'E:\marckassay\XAz' -NuGetApiKey 'XXXXXXXX-XXXX-XXXX-XXXX-XX...XX' -Verbose
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Publish Location:'https://www.powershellgallery.com/api/v2/package/'.
VERBOSE: Loading module from path 'E:\marckassay\XAz\XAz.psm1'.
VERBOSE: Module 'XAz' was found in 'E:\marckassay\XAz'.
VERBOSE: Loading module from path 'C:\Users\marck\AppData\Local\Temp\694162021\XAz\XAz.psm1'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: Using the specified source names : 'PSGallery'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/items/psscript' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/items/psscript/FindPackagesById()?id='XAz'' for ''.
VERBOSE: Total package yield:'0' for the specified package 'XAz'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: Using the specified source names : 'PSGallery'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='XAz'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'XAz'.
VERBOSE: Performing the operation "Publish-Module" on target "Version '1.0.0' of module 'XAz'".

Environment data
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Microsoft Windows 10.0.19013
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

>  Get-Module -ListAvailable PowerShellGet,PackageManagement

    Directory: C:\Users\marck\OneDrive\Documents\PowerShell\Modules

ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     1.4.5      PackageManagement                   Desk      {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource…}
Script     2.2.1      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find-RoleCapability…}

    Directory: C:\program files\powershell\6\Modules

ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     1.3.2      PackageManagement                   Desk      {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource…}
Script     2.1.3      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find-RoleCapability…}

>  Get-PackageProvider -ListAvailable

Name                     Version          DynamicOptions
----                     -------          --------------
NuGet                    <IP_ADDRESS>          Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, Contains, AllowPrereleaseVersions, ConfigFile, SkipValidate
PowerShellGet            <IP_ADDRESS>          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, InstallUpdate, NoPathUpdate, AllowPrereleaseVersions, Filter, Tag, Includes, Ds…
PowerShellGet            <IP_ADDRESS>

@marckassay thanks for opening this issue, that is a very frustrating experience--unfortunately we cannot make changes to older versions of PowerShellGet with these warning so people would know they are running an outdated version but it is something we should likely update going forward


"Tomșani", "Loloiasca", "Magula" and "Sătucu" villages are listed in the drop-down menu

The villages are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Type "Tomșani" in the search bar.

Expected results
The location is listed in the drop-down menu as "SatTomșani, PRAHOVA (Tomșani)".

Step 2
Type "Loloiasca" in the search bar.

Expected results
The location is listed in the drop-down menu as "SatLoloiasca, PRAHOVA (Tomșani)".

Step 3
Type "Magula" in the search bar.

Expected results
The location is listed in the drop-down menu as "SatMagula, PRAHOVA (Tomșani)".

Step 4
Type "Sătucu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Sătucu, PRAHOVA (Tomșani)".


fixed issue 1561

What are you trying to achieve?
I want to test if the exact text "Authentication failed." appears in the p subelement of

Let's say now there is no value in p.
So I.seeTextEquals("Authentication failed.", ".error.message"); should fail.

Thank you!


[Feature request] Dark theme

As title says. After a long night of VRChat, opening VRCX with its bright theme really burns your eyes, so a dark theme for all of us vampires would be great.

ive added my own to this jusst by editing the HTML but havent touched the actual CSS tables

@Murkur Care to share the modifications so we can put them in a collab PR?

No exactly proud of the method I did it as I just replaced the HTML colors within index.HTML and theirs no toggle for it as I sleep in vrchat and I wouldn't need a light mode

if you want the CSS file that I edited you could just swap it out
app.css.txt
just rename app.css.text to app.css and add it to the HTML folder in VRCX tho I only edited it for my own use so i doubt you will continue to use it itts only simple edits you can compare for yourself

I'm sorry to help you. I think it will take more time.

Hi, as an update, I have slowly started working on a Dark Theme in my  spare time, its not completed yet but this is how it currently looks like.

Its unfinished with things like this still being white in some main areas

aye nice ive just been using a simple CSS edit for my darktheme i do plan on adding a data-theme to vrcx when I get the time

Ready to use app.css dark theme replacement: http://xor.meo.ws/KW5sbpwr9ZZu155hgRsK7Z8abBgsn1id/app.css @pypy-vrc feel free to use, only the buttons need to be fixed.

Ready to use app.css dark theme replacement: http://xor.meo.ws/KW5sbpwr9ZZu155hgRsK7Z8abBgsn1id/app.css @pypy-vrc feel free to use, only the buttons need to be fixed.

this area is triggering my ocd XD
its from line 210 (from your app.css Fusl)
.x-friend-list>.x-friend-group { 	border-bottom: 5px solid #606060; }
a fix is just changing the #606060 to #171717 or just removing it entirely.

looking at Index.HTML someone could try adding a button in MORE that just swaps which CSS the app uses
so for
<script> (() => { 	var link = document.createElement('link'); 	link.rel = 'stylesheet'; 	link.href = app.css?=${Date.now()}; 	document.getElementsByTagName('head')[0].appendChild(link); 	var script = document.createElement('script'); 	script.src = app.js?=${Date.now()}; 	document.getElementsByTagName('body')[0].appendChild(script); })(); </script>
replace app.css to have it point to another css file with the dark theme settings and have it quick reload Cerfsharp


team_name hardcoded in team_name.webhook.office.com

Hi,
In the following line, do I misinterpret the line or is team_name wrong there and should be a regex?
https://github.com/Checkmarx/kics/blob/a546d9adfaa808ea05192988c075e105155a3f0a/assets/queries/common/passwords_and_secrets/regex_rules.json#L103

Hello, @skorpy2009 I believe this is indeed a bug and team_name should be a Regex and not hardcoded, I will make the change to regex.
Thank you


🎉 2.0.6

ℹ About this release

Version: 2.0.6
Type: patch
Last Release: 2.0.5 (5/14/2022, 6:34:18 PM) [?]
Commits to merge: 53 [?]

↩ Reverts

Revert "ci: Remove docker setup" (14a5226)
Revert "ci: Remove docker setup" (655068b)

📦 Dependencies

Update puppeteer from ^13.6.0 to ^14.1.1

📦 Development Dependencies

Update @amanda-mitchell/semantic-release-npm-multiple from ^3.2.0 to ^3.2.1
Update @qiwi/semantic-release-gh-pages-plugin from ^5.2.0 to ^5.2.2
Update eslint from ^8.13.0 to ^8.15.0
Update rollup from ^2.70.2 to ^2.74.1

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

v2.0.6
GitHub release
Docker container (sebbo2002/fileee-backup-downloader:2.0.6)
v2.0.6

Your semantic-release bot :package::rocket:


IUrlHelper behave strange for new version of .net core 2.2

IUrlHelper behave strange for new version of .net core 2.2
Helper method that is working for all early version
    public static string AbsoluteRouteUrl(
    this IUrlHelper url,
    string routeName,
    object routeValues = null)
    {
        return url.RouteUrl(routeName, routeValues, url.ActionContext.HttpContext.Request.Scheme);
     }

    string serviceUrl = Url.AbsoluteRouteUrl("default");

about one line of code return the Url of the executing MVC controller, in my case here it should return DNS + /Login/SSO and this code has been working for .core 1.1 and 2.1
After I updated to 2.2 this  serviceUrl return DNS + /Contact/SSO when I call it from Login controller method SSO. This is really weird.

This issue was moved to aspnet/AspNetCore#4549


python312Packages.apollo-fpga: 1.1.0 -> 1.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.apollo-fpga is: microcontroller-based FPGA / JTAG programmer
meta.homepage for python312Packages.apollo-fpga is: https://github.com/greatscottgadgets/apollo
meta.changelog for python312Packages.apollo-fpga is: https://github.com/greatscottgadgets/apollo/releases/tag/v1.1.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1 with grep in /nix/store/257mcr5z6qbajfxi4gdnscc7fk36vfl5-python3.12-apollo-fpga-1.1.1
found 1.1.1 in filename of file in /nix/store/257mcr5z6qbajfxi4gdnscc7fk36vfl5-python3.12-apollo-fpga-1.1.1

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

10 package rebuild(s)

First fifty rebuilds by attrpath

cynthion
python311Packages.apollo-fpga
python311Packages.cynthion
python311Packages.luna-soc
python311Packages.luna-usb
python312Packages.apollo-fpga
python312Packages.cynthion
python312Packages.luna-soc
python312Packages.luna-usb

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/257mcr5z6qbajfxi4gdnscc7fk36vfl5-python3.12-apollo-fpga-1.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.apollo-fpga https://github.com/r-ryantm/nixpkgs/archive/fe61d5b377bcd169d9dfe41398e2b2dbedf48ce5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fe61d5b377bcd169d9dfe41398e2b2dbedf48ce5#python312Packages.apollo-fpga

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/257mcr5z6qbajfxi4gdnscc7fk36vfl5-python3.12-apollo-fpga-1.1.1
ls -la /nix/store/257mcr5z6qbajfxi4gdnscc7fk36vfl5-python3.12-apollo-fpga-1.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:fast_forward: 12 packages marked as broken and skipped:

python311Packages.cynthion
python311Packages.cynthion.dist
python311Packages.luna-soc
python311Packages.luna-soc.dist
python311Packages.luna-usb
python311Packages.luna-usb.dist
python312Packages.cynthion
python312Packages.cynthion.dist
python312Packages.luna-soc
python312Packages.luna-soc.dist
python312Packages.luna-usb
python312Packages.luna-usb.dist

:white_check_mark: 6 packages built:

cynthion
cynthion.dist
python311Packages.apollo-fpga
python311Packages.apollo-fpga.dist
python312Packages.apollo-fpga
python312Packages.apollo-fpga.dist

Maintainer pings
cc @carlossless for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Allowing custom constraints?

Hey! I love the idea of this gem and would love to use it in our app at work. After playing around with it for a bit, I noticed that it doesn't allow you to place custom constraints on a table. It seems that when using check_constraint, you can only specify that a column must be one of a number of values. However, Postgres already provides this capability in the form of the ENUM type. Constraints are designed to be more powerful than this, as you can use any expression you want to check any column you want.
So, I have three questions:

What was the use case you were trying to solve in making this gem?
What do you think about making it possible to add custom constraints?
If I were to submit a PR, how should I extend your gem to do this?

you can only specify that a column must be one of a number of values.

Incorrect.  You can specify any condition as a String.  See https://github.com/on-site/active_record-postgres-constraints/blob/afb3277ca42ddd786a4702e99d27adb40aab1cd2/spec/active_record/postgres/constraints/types/check_spec.rb#L43 for example.

I should be able to infer this from readme, please mention this possibility on the readme as well and save people like me a few minutes of searching. Thanks.

@ziaulrehman40 PR welcome.


Size & Cutoff

Hi. Thanks for sharing your script.
On my 11 Pro the Widget looks a bit cutoff. What do i need to change in the script to make it fit?
Thanks

Hi there,
Move to Line 307:
widget.setPadding(3, 10, -3, 10)
widget.spacing = -1.2
Set widget.spacing to 0,
And widget.setPadding(3, 10, -5, 10)
And inform me, tnx.

Hi. With your suggestion the text was more cut off. I changed:
widget.spacing = -2.5
Now the text fit in the widget.
Thank you

Good to hear that resolved.
Did you set widget.setPadding(3, 10, -5, 10) as well?

Im playing around with the settings.
Now i have:
widget.setPadding(3, 10, -2, 10)
widget.spacing = -2.5
With this settings it looks okay on my phone. It also would be nicht to center the update time on the widget.

Glad you got along with but you have to update it. New version has been added.

I have a similar issue on my iPhone 12 Mini. Is there an overview of specific settings for specific devices (sizes)? Do you need a screenshot to determine the correct settings, or should I just tinker around on the mentioned lines and inform you, what suits best?
thanks in advance for this beautiful widget!


newBitmapContainerwithRange should be removed

I think that newBitmapContainerwithRange is no longer used.

this seems super useful code; I think it should be kept.

Ok.

Closed.

added call to this function as an optimization in newBitmapContainerFromRun()


Feature request: Make horizontal accuracy 'required' for geospatial data

Is your feature request related to a problem? Please describe.
Horizontal accuracy should be mandatory for all collections where there is geospatial data.
Options to determine if data is Geospatial:

Use some other STAC metadata, i.e linz:geospatial_type or the spatial object?
Scan the data to determine if it has a geospatial element

Describe the solution you'd like
Add the two horizontal accuracy fields to this (+ some tests).
https://github.com/linz/stac/blob/beb807944836c3b9a215239efc46d762ba889986/extensions/quality/schema.json#L16
Describe alternatives you've considered
Part of LINZ metadata review decisions

Creasted draft PR here https://github.com/linz/stac/pull/77

Check if this makes sense for all datasets.

Duplicate of #100 . Closing.


Error while executing automation ... Unknown error for call_service at pos 1

Home Assistant release with the issue:

0.92.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Docker
Component/platform:

https://www.home-assistant.io/components/konnected
Description of problem:
My automation beep_on_door_window_open_close was the first automation I ever set up with Home Assistant/Konnected, and has been working unchanged since HA 0.7x. Recently, it stopped working, and produces the following traceback any time a door/window is opened/closed. Door/window open/close sensors still indicate their status correctly in the frontend, but the beep automation no longer works.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Excerpts from configuration.yaml:
automation: !include_dir_merge_list automation
konnected: !include includes/konnected.yaml

automation/doors.yaml:
- alias: Beep on Door/Window Open/Close
  initial_state: true
  hide_entity: true
  trigger:
    platform: state
    entity_id:
    - binary_sensor.front_kitchen_doors
    - binary_sensor.back_laundry_doors
    - binary_sensor.master_bedroom_doors
    - binary_sensor.kitchen_dining_windows
    - binary_sensor.living_room_windows
    - binary_sensor.office_craft_bath_windows
  action:
  - service: switch.turn_on
    entity_id: switch.beep_beep

includes/konnected.yaml:
access_token: !secret konnected_access_token
devices:
  - id: bcddc2fdedc6
    binary_sensors:
      - zone: 3
        type: window
        name: 'Upstairs Windows'
      - zone: 4
        type: window
        name: 'Office/Craft/Bath Windows'
      - zone: 5
        type: door
        name: 'Front/Kitchen Doors'
      - zone: 6
        type: door
        name: 'Back/Laundry Doors'
    switches:
      - zone: out
        name: 'Siren'
  - id: 68c63aab35a8
    binary_sensors:
      - zone: 1
        type: window
        name: 'Kitchen/Dining Windows'
      - zone: 2
        type: window
        name: 'Garage Windows, Storage Doors'
      - zone: 3
        type: window
        name: 'Living Room Windows'
      - zone: 4
        type: door
        name: 'Unknown Door'
      - zone: 5
        type: door
        name: 'Master Bedroom Doors'
      - zone: 6
        type: smoke
        name: 'Smoke Detectors'
        inverse: true
    switches:
      - zone: out
        name: 'Beep Beep'
        momentary: 65
        pause: 55
        repeat: 2
      - zone: out
        name: 'Warning'
        momentary: 65
        pause: 55
        repeat: -1

Traceback (if applicable):
2019-04-28 08:13:18 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.beep_on_door_window_open_close. Unknown error for call_service at pos 1:
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/automation/__init__.py", line 378, in action
    await script_obj.async_run(variables, context)
  File "/usr/src/app/homeassistant/helpers/script.py", line 131, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/src/app/homeassistant/helpers/script.py", line 210, in _handle_action
    action, variables, context)
  File "/usr/src/app/homeassistant/helpers/script.py", line 299, in _async_call_service
    context=context
  File "/usr/src/app/homeassistant/helpers/service.py", line 89, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context)
  File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/usr/src/app/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/app/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/konnected/switch.py", line 71, in turn_on
    resp = self.client.put_device(
AttributeError: 'NoneType' object has no attribute 'put_device'

Additional information:

If you turn on beep beep directly does this cause the exception?

Turned on switch.beep_beep directly using HA developer services:

Resulted in a similar exception:
2019-04-29 10:27:50 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140687024991200] 'NoneType' object has no attribute 'put_device'
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/helpers/entity_component.py", line 194, in handle_service
    required_features
  File "/usr/src/app/homeassistant/helpers/service.py", line 316, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/app/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/konnected/switch.py", line 71, in turn_on
    resp = self.client.put_device(
AttributeError: 'NoneType' object has no attribute 'put_device'

@heythisisnate

Maybe close and reopen the issue with the more specific error. This is nothing to do with automations.

I have the same errors with notify.html5 automation.
Op di 30 apr. 2019 23:38 schreef Penny Wood<EMAIL_ADDRESS>
Maybe close and reopen the issue with the more specific error. This is
nothing to do with automations.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/23510#issuecomment-488124638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJR36PWNUYNEOCLWV2XAQLPTC35DANCNFSM4HI6QJ7A
.

The only bit of the stack trace that's important is this bit
  File "/usr/src/app/homeassistant/components/konnected/switch.py", line 71, in turn_on
    resp = self.client.put_device(
AttributeError: 'NoneType' object has no attribute 'put_device'

It's an issue with the konnected integration, nothing to do with automations or the html5 notifier.
I'm going to close this one, please resubmit as as per this part

This means that HA doesn't know the IP address of the Konnected device. Most likely because discovery is not working in your setup. Are you running HA on a separate subnet or in a VM/container that is isolated from your wifi network? See:
https://help.konnected.io/support/solutions/articles/32000023644-device-discovery-troubleshooting
Not a bug ... just poor error handling.

I'm fairly certain HA is communicating properly with the konnected boards, as all door/window sensors are still working properly. They are both located on the same subnet, and no networking or automation changes have been made since I originally installed HA/konnected almost a year ago. Any other tests you suggest?
--
Tom Hoover
On May 1, 2019, 6:37 AM -0500, Nate Clark<EMAIL_ADDRESS>wrote:

This means that HA doesn't know the IP address of the Konnected device. Most likely because discovery is not working in your setup. Are you running HA on a separate subnet or in a VM/container that is isolated from your wifi network? See:
https://help.konnected.io/support/solutions/articles/32000023644-device-discovery-troubleshooting
Not a bug ... just poor error handling.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Binary sensors work in the opposite direction than switches -- when the sensor state changes, the device makes a HTTP PUT request to the Home Assistant API.
The problem you are having with switches is that every time HA reboots it must re-discover the IP address of the Konnected device(s). If this does not happen, then HA will not know the address to send a turn_on/turn_off signal to the switch.
Try debugging discovery by running NetDisco manually:
https://help.konnected.io/support/solutions/articles/32000023681-debugging-device-discovery-with-netdisco


Enable object handler for Event Consumption Model (EEEC)

This PR implements an AFF object handler for the Event Consumption Models (EEEC). This object type was already announced in issue 6079 and issue 5912
In addition, this PR also contains slight adjustments for the zcl_abapgit_object_common_aff to provide a more generic approach for the AFF object handler retrieval.

welcome to abapGit as a contributor 🎉

Please create a small test case in https://github.com/abapGit-tests/EEEC. Thanks


Cleaned up temp_dir function in test/simulate (branch renamed)

Cleaned up test code from #1245.
Duplicate for #1275. Renamed the branch, just in case it's the reason Travis doesn't run the tests.

It seem to run it now. Nice :)

Thanks for the audit. But I hoped for you to be able to get rid of the @is_writeable decorator to. :)

Oh but sadly the tests don't pass on py27-nonhdfs without it, and I really haven't found a better way.

Hmm. OK


Test adapter tests not passing under pytest 6

Make sure you are running against pytest 6 and not another version due to build/test-requirements.txt.
Here is an example failure. They all seem to be similar.
---------------------------------------------------------------------------------------------------------------- Captured stdout call ----------------------------------------------------------------------------------------------------------------
The Python extension has run into an unexpected situation
while processing a pytest node during test discovery.  Please
Please open an issue at:
  https://github.com/microsoft/vscode-python/issues
and paste the following output there.

nodeid: X/Y/Z/test_Eggs.py::SpamTests::test_spam
kind: ('function', False)
class: StubFunctionItem
name: pytest.Item
fspath: <function StubPytestItem.__getattr__.<locals>.func at 0x7fef2eb2ae50>
location: ('X\\Y\\Z\\test_Eggs.py', 12, 'SpamTests.test_spam')
function: <tests.testing_tools.adapter.pytest.test_discovery.FakeFunc object at 0x7fef2eb5c850>
markers: ()
user_properties: []
attrnames: ['_ALLOW_MARKERS', '__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattr__', '__getattribute__', '__gt__', '__hash__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__slots__', '__str__', '__subclasshook__', '__weakref__', '_debugging', '_getobj', '_hasfunc', '_initrequest', '_nodeid', '_prunetraceback', '_pyfuncitem', '_repr_failure_py', '_store', 'add_call', 'add_marker', 'add_report_section', 'addfinalizer', 'calls', 'cls', 'config', 'from_parent', 'fspath', 'funcargnames', 'function', 'get_closest_marker', 'getmodpath', 'getparent', 'ihook', 'instance', 'iter_markers', 'iter_markers_with_node', 'listchain', 'listextrakeywords', 'listnames', 'location', 'module', 'name', 'nextitem', 'nodeid', 'obj', 'own_markers', 'parent', 'reportinfo', 'repr_failure', 'runtest', 'session', 'setup', 'stub', 'teardown', 'user_properties', 'warn']

extra info:
fspath:   <function StubPytestItem.__getattr__.<locals>.func at 0x7fef2eb2ae50>
fileid:   ./X/Y/Z/test_Eggs.py

traceback:
---------------------------------------------------------------------------------------------------------------- Captured stderr call ----------------------------------------------------------------------------------------------------------------
  File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/tests/__main__.py", line 44, in <module>
    ec = main(pytestargs, **mainkwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/tests/__main__.py", line 38, in main
    ec = pytest.main(pytestargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/config/__init__.py", line 157, in main
    ret = config.hook.pytest_cmdline_main(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 84, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/main.py", line 289, in pytest_cmdline_main
    return wrap_session(config, _main)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/main.py", line 240, in wrap_session
    session.exitstatus = doit(config, session) or 0
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/main.py", line 296, in _main
    config.hook.pytest_runtestloop(session=session)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 84, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/main.py", line 321, in pytest_runtestloop
    item.config.hook.pytest_runtest_protocol(item=item, nextitem=nextitem)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 84, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 100, in pytest_runtest_protocol
    runtestprotocol(item, nextitem=nextitem)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 117, in runtestprotocol
    reports.append(call_and_report(item, "call", log))
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 207, in call_and_report
    call = call_runtest_hook(item, when, **kwds)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 246, in call_runtest_hook
    return CallInfo.from_call(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 294, in from_call
    result = func()  # type: Optional[_T]
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 247, in <lambda>
    lambda: ihook(item=item, **kwds), when=when, reraise=reraise
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/manager.py", line 84, in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/runner.py", line 153, in pytest_runtest_call
    item.runtest()
  File "/home/brettcannon/Repositories/microsoft/vscode-python/.venv/lib/python3.8/site-packages/_pytest/unittest.py", line 278, in runtest
    self._testcase(result=self)  # type: ignore[arg-type]
  File "/usr/lib/python3.8/unittest/case.py", line 736, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib/python3.8/unittest/case.py", line 676, in run
    self._callTestMethod(testMethod)
  File "/usr/lib/python3.8/unittest/case.py", line 633, in _callTestMethod
    method()
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py", line 1151, in test_windows
    collector.pytest_collection_finish(session)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/testing_tools/adapter/pytest/_discovery.py", line 107, in pytest_collection_finish
    test, parents = self.parse_item(item)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py", line 284, in _parse_item
    return pytest_item.parse_item(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 168, in parse_item
    testroot, relfile = _split_fspath(str(item.fspath), fileid, item)
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py", line 247, in _split_fspath
    return pytest_item._split_fspath(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 244, in _split_fspath
    raise should_never_reach_here(
  File "/home/brettcannon/Repositories/microsoft/vscode-python/pythonFiles/testing_tools/adapter/pytest/_pytest_item.py", line 132, in should_never_reach_here
    traceback.print_stack()
============================================================================================================== short test summary info ===============================================================================================================
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_doctest - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_finish - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_imported_test - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_modifyitems - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_mysterious_parens - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_nested_brackets - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_nested_suite - NotImplementedError: Unexpected pytest node (see printed output).
FAILED tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_windows - NotImplementedError: Unexpected pytest node (see printed output).

FYI, at this point (pytest 6.2.2), I'm only seeing 1 kind of failure on linux with Python 3.7:
~/projects/work/vscode-python$ ../venvs/pytest-6/bin/python pythonFiles/tests/run_all.py
================================================ test session starts =================================================
platform linux -- Python 3.7.5, pytest-6.2.2, py-1.10.0, pluggy-0.13.1
rootdir: /home/esnow/projects/work/vscode-python/pythonFiles
collected 69 items

pythonFiles/tests/test_normalize_for_interpreter.py .....                                                        [  7%]
pythonFiles/tests/test_normalize_selection.py ..........                                                         [ 21%]
pythonFiles/tests/debug_adapter/test_install_debugpy.py .                                                        [ 23%]
pythonFiles/tests/testing_tools/adapter/test___main__.py ........                                                [ 34%]
pythonFiles/tests/testing_tools/adapter/test_discovery.py .......                                                [ 44%]
pythonFiles/tests/testing_tools/adapter/test_functional.py s......                                               [ 55%]
pythonFiles/tests/testing_tools/adapter/test_report.py .....                                                     [ 62%]
pythonFiles/tests/testing_tools/adapter/test_util.py .........                                                   [ 75%]
pythonFiles/tests/testing_tools/adapter/pytest/test_cli.py ..                                                    [ 78%]
pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py .......FFFFFFFF                                 [100%]

===================================================== FAILURES =====================================================
___________________________________________ CollectorTests.test_doctest ____________________________________________
Direct construction of StubDoctestItem has been deprecated, please use StubDoctestItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
____________________________________________ CollectorTests.test_finish ____________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
________________________________________ CollectorTests.test_imported_test _________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
_________________________________________ CollectorTests.test_modifyitems ____________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
______________________________________ CollectorTests.test_mysterious_parens _______________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
_______________________________________ CollectorTests.test_nested_brackets ________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
_________________________________________ CollectorTests.test_nested_suite _________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
___________________________________________ CollectorTests.test_windows ____________________________________________
Direct construction of StubFunctionItem has been deprecated, please use StubFunctionItem.from_parent.
See https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent for more details.
============================================= short test summary info ==============================================
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_doctest
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_finish
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_imported_test
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_modifyitems
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_mysterious_parens
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_nested_brackets
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_nested_suite
FAILED pythonFiles/tests/testing_tools/adapter/pytest/test_discovery.py::CollectorTests::test_windows
===================================== 8 failed, 60 passed, 1 skipped in 30.49s =====================================

Note that it is all the same failure, referring to https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent.

fixed by #15341


Adding utility for a passive listen service

Dear team,
I am trying to adapt the current application to support a passive listen service. While I managed to make the app work while OnPause (screen locked), I am having issues when OnDestroy (quitting the app) is called. Maybe someone who has a better understanding of the app can help me on this.
Best

Please reduce the amount of code changes and number of commits. Also, please do not change minSDK, that is a whole different can of worms.
Please look at https://developer.android.com/guide/components/activities/activity-lifecycle to understand the activity lifecycle on Android.


Panda abstraction layer in boardd

Too bad this doesn't use libusb if it ends up extremely similar
https://github.com/commaai/panda/blob/master/drivers/windows/panda_shared/panda.cpp


Make import status messages more meaningful

User Story

So that I can quickly understand the status of my import, as a Data Maintainer, I want to clear and relevant import status messages.
This message:
{
  "statusCode": 200,
  "body": {
    "step function": {
      "status": "SUCCEEDED"
    },
    "validation": {
      "status": "Failed",
      "errors": [
        {
          "check": "checksum",
          "result": "Failed",
          "url": "s3://xxxxxx/data_lake_test/checksum_validation_fails/empty_file.tif",
          "details": {
            "message": "Checksum mismatch: expected e3bcc44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, got e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
          }
        }
      ]
    },
    "metadata upload": {
      "status": "Pending",
      "errors": []
    },
    "asset upload": {
      "status": "Pending",
      "errors": []
    }
  }
}

Would be more meaningful it it was something like this:
{
  "statusCode": 200,
  "body": {
    "step function": {
      "status": "Completed"        <-- Lower case and 'Completed' rathe than 'Suceeded'
    },
    "validation": {
      "status": "Failed",
      "errors": [
        {
          "check": "checksum",
          "result": "Failed",
          "url": "s3://xxxxxx/data_lake_test/checksum_validation_fails/empty_file.tif",
          "details": {
            "message": "Checksum mismatch: expected e3bcc44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, got e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
          }
        }
      ]
    },
    "metadata upload": {
      "status": "Cancelled",       <-- "Cancelled" instead of "Pending"
      "errors": []
    },
    "asset upload": {
      "status": "Cancelled",      <-- "Cancelled" instead of "Pending"
      "errors": []
    }
  }
}

Acceptance Criteria

[ ] Given [a pre-condition], when [an event happens], then [an expected outcome occurs]
[ ] Given [a pre-condition], when [an event happens], then [an expected outcome occurs]

Additional context

Tasks

[ ] ...
[ ] ...

Definition of Ready

[ ] This story is ready to work on, according to the team's definition

Definition of Done

[ ] This story is done, according to the team's definition

"SUCCEEDED" is the literal value the AWS API reports. We can easily lowercase or Title-Case it. As for changing it to "completed", that is less informative, since it doesn't say whether the stage was successful.
"Cancelled" instead of "Pending" - completely agree; we need to be able to distinguish them.

There's also this one which seems to have a few isssues:
{
  "statusCode": 200,
  "body": {
    "step function": {
      "status": "FAILED"                 <-- Why not 'SUCCEEDED', like the one above?
    },
    "validation": {
      "status": "Pending",                <-- Should be 'Failed'?
      "errors": [
        {
          "check": "JSON schema",
          "result": "Failed",
          "url": "s3://data-lake-test-bn/data_lake_test/tasman_invalid_metadata/collection.json",
          "details": {
            "message": "'' does not match '^[\\\\w\\\\-\\\\.\\\\+]+$'\n\nFailed validating 'pattern' in schema['allOf'][1]['properties']['license']:\n    {'pattern': '^[\\\\w\\\\-\\\\.\\\\+]+$',\n     'title': 'Collection License Name',\n     'type': 'string'}\n\nOn instance['license']:\n    ''"
          }
        }
      ]
    },
    "metadata upload": {
      "status": "Pending",            <-- Again, 'Cancelled'?
      "errors": []
    },
    "asset upload": {
      "status": "Pending",         <-- Again, 'Cancelled'?
      "errors": []
    }
  }
}

"SUCCEEDED" is the literal value the AWS API reports. We can easily lowercase or Title-Case it. As for changing it to "completed", that is less informative, since it doesn't say whether the stage was successful.

Okay, thanks. I didn't realise the STEP Function can be 'SUCCEEDED' while data copying processes are still happening. Can probably leave that bit for now then, until we have a proper API etc.


Debug build stops (like #387)

Same as the topic Build stops (like #387) #492
vector-of-bool.cmake-tools-unresponsive.cpuprofile.txt

Issue Type: Performance
Extension Name: cmake-tools
Extension Version: 1.1.3
OS Version: Linux x64 4.15.0-43-generic
VSCode version: 1.30.1

:warning: Make sure to attach this file from your home-directory: /home/sania/vector-of-bool.cmake-tools-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Trying to compile debug config with gcc 7.3 in Ubuntu 16.04 LTS, but extension is unresponsive, occupies all CPU cores, build process progresses very slowly. No problems with release config though.

We did not have this exact symptom in the repros we worked on while going through our extension GitHub issues but there were several fixes in this area. Please upgrade to latest CMake Tools and reopen if this problem is not solved.


default_balancer_in_writer

Normal expected behaviour with kafka is messages with same key should go to same partition. So changing the default behaviour of balancer to balancerHash.

Hey @vishaldeshmukh3011,
Thanks for your contribution, but this is superfluous, since it can be set via the script. Look at the balancer property of WriterConfig. And these values are supported, which you can import as constants and pass them to the balancer property:

BALANCER_CRC32
BALANCER_HASH
BALANCER_LEAST_BYTES
BALANCER_MURMUR2
BALANCER_ROUND_ROBIN

I'll close this ticket.


Weirdly different approach to Unpin vs Drop

Looking at these two examples
use std::fmt::Debug;
use pin_project::pin_project;
use std::pin::Pin;

pin_project! {
    #[pin_projectable]
    pub struct Foo<T: Debug, U: Debug> {
        #[pin] pinned_field: T,
        unpin_field: U
    }

    #[pinned_drop]
    fn my_drop_fn<T: Debug, U: Debug>(foo: Pin<&mut Foo<T, U>>) {
        let foo = foo.project();
        println!("Dropping pinned field: {:?}", foo.pinned_field);
        println!("Dropping unpin field: {:?}", foo.unpin_field);
    }
}

fn main() {
    Foo { pinned_field: true, unpin_field: 40 };
}

use pin_project::{pin_projectable, UnsafeUnpin};
use std::pin::Pin;

#[pin_projectable(unsafe_Unpin)]
struct Foo<T, U> {
    #[pin]
    future: T,
    field: U,
}

impl<T, U> Foo<T, U> {
    fn baz(self: Pin<&mut Self>) {
        let this = self.project();
        let _: Pin<&mut T> = this.future; // Pinned reference to the field
        let _: &mut U = this.field; // Normal reference to the field
    }
}

unsafe impl<T: Unpin, U> UnsafeUnpin for Foo<T, U> {} // Conditional Unpin impl

it is odd that for a very similar situation (let the user "hook" into the auto-generated trait impl), this crate uses two totally different approaches: one time it is an attribute at the type, and one time it is a block around the entire thing plus an attribute at the impl.
To make the crate easier to use, it would be much better if the same approach could be used both times.

pin_project! block was removed in #33, so the current Drop impl is as follows:
use std::fmt::Debug;
use pin_project::{pin_project, pinned_drop};
use std::pin::Pin;

#[pin_project(PinnedDrop)]
pub struct Foo<T: Debug, U: Debug> {
    #[pin] pinned_field: T,
    unpin_field: U
}

#[pinned_drop]
fn my_drop_fn<T: Debug, U: Debug>(foo: Pin<&mut Foo<T, U>>) {
    let foo = foo.project();
    println!("Dropping pinned field: {:?}", foo.pinned_field);
    println!("Dropping unpin field: {:?}", foo.unpin_field);
}

So how does it look like when combining a manual drop impl and an UnsafeUnpin override?

It is as follows:
use pin_project::{pin_project, pinned_drop, UnsafeUnpin};
use std::pin::Pin;

#[pin_project(UnsafeUnpin, PinnedDrop)]
pub struct Foo<T, U> {
    #[pin] pinned_field: T,
    unpin_field: U
}

#[pinned_drop]
fn do_drop<T, U>(this: Pin<&mut Foo<T, U>>) {
    // ..
}

unsafe impl<T: Unpin, U> UnsafeUnpin for Foo<T, U> {}

I feel this is easier to read/write than the previous one.

However, I think it is more consistent to use attributes to impl.
use pin_project::{pin_project, pinned_drop};
use std::pin::Pin;

#[pin_project(UnsafeUnpin, PinnedDrop)]
pub struct Foo<T, U> {
    #[pin] pinned_field: T,
    unpin_field: U
}

#[pinned_drop]
impl<T, U> PinnedDrop for Foo<T, U> {
    fn drop(self: Pin<&mut Foo<T, U>>) {
        // ..
    }
}

unsafe impl<T: Unpin, U> UnsafeUnpin for Foo<T, U> {}


[docs] Sidenav size in some cases makes scroll needed in tables on API pages

The contents drawer is great for navigation. However, I think it needs a collapse button so that you can hide it in some cases. I noticed it obscures the "Props" table on the right hand side. Forcing you to scroll all the way down the table so you can use the scrollbar to reveal the hidden contents. It is not a major issue but I think a fix can improve the user experience slightly.
Website URL: https://mui.com/api/dialog/

Hey, @RaymondMwaura thanks for the suggestion!
This behavior actually already is implemented but only in smaller breakpoints than the one you seem to be seeing the docs in. We briefly touched on the discussion of whether using a table to display props and CSS classes on API pages is the best option. There might be other ways of doing that which would avoid any scroll whatsoever.
For the time being, not sure if we'd need to change anything but I'll keep your suggestion close by. Let me know if you have any other ones!

Thank you @danilo-leal. I reduced the zoom on my browser slightly and the table was rendered fully.
I also tried it out on a mobile device and the drawer was hidden so that's all good.

Thanks though for contributing and leaving you suggestions, we appreciate it!


astro dev support

Is it possible to get this to work with astro dev?
I use a project called code-server which proxies ports through a '/proxy/portnumber' url.  So when running the url of the homepage would look something like http://localhost:4080/proxy/4321/.  Since the proxy port can change relative paths are needed.
This project works fine when doing astro build then astro preview, however astro dev doesn't work at all.  All of the asset's ignore the relative paths ans use absolute paths such as  http://localhost:4080/node_modules when it should be http://localhost:4080/proxy/4321/node_modules

Hello,
I think a base path should help you:
https://docs.astro.build/en/reference/configuration-reference/#base


Create separate resource quotas for CPU vs RAM vs Storage

At this moment CPU/RAM and Storage resources in Openshift 4 Platform are all bundled together into resource quota as described here. However, it became obvious that CPU and storage resource needs for projects are not correlated as often projects need an increase in just one resource category.
We need to split the CPU/RAM/Storage resource quotas into the CPU/RAM and Storage resource quotas and enable projects to request an increase in either quota separately.
DoD:

Support for CPU/RAM and Storage quotas (the amount of resources in each small/medium/large quota size will stay the same) is added to the Project Registry and in the provisioner. Teams are able to request increase either in CPU/RAM resource category or Storage separately.

@mitovskaol @juhewitt It might be better to go ahead and split quotas for all resources and all environments like we had in the early days of the Registry.
If you'd still like to group CPU / Mem into one bundle I think that's fine, however the technical implementation should support the splitting of all resources even if the business login displayed on the front end is grouped. This also makes it easier to add custom quota support to the registry later if it's needed. It would be great to eventually support an admin interface to set quotas outside of the T-Shirt sizes so that the Registry can remain the single source of truth, and so that the provisioner does not have hardcoded quotas for select project sets. (Right now these custom quotas can not be displayed in the report generated by the Registry)

@mitovskaol @juhewitt @j-pye I agree with Mr. Pye that we should maintain some flexibility in the resource allocation, even if the front end simplifies the selection.  There will always be special cases.

@j-pye @IanKWatts  I agree with splitting the current quotas into 3 separate quotas for CPU, RAM and Storage so that each resource can be increased independently.

Hi @marthaedwards, @mitovskaol , do you guys like this UI?

Can  you please add "Quota Size" label to all 3 dropdowns and remove it from the top of the section where it is now under Quota information.

Maybe like this?

Yes, this looks much better. Let's just remove the word "Current" and it will look perfect :)

Completed and in production


[BUG REPORT] cant download or cant strip audio

Describe the bug
when i try to strip audio from video, i get this error:
down() is not in the list of choices. Please update the list of choices to include: Deneme or set allow_custom_value=True.
warnings.warn(
Traceback (most recent call last):
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\queueing.py", line 407, in call_prediction
output = await route_utils.call_process_api(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\route_utils.py", line 226, in call_process_api
output = await app.get_blocks().process_api(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\blocks.py", line 1550, in process_api
result = await self.call_function(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\blocks.py", line 1185, in call_function
prediction = await anyio.to_thread.run_sync(
File "C:\dene\audio-webui\venv\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "C:\dene\audio-webui\venv\lib\site-packages\anyio_backends_asyncio.py", line 2144, in run_sync_in_worker_thread
return await future
File "C:\dene\audio-webui\venv\lib\site-packages\anyio_backends_asyncio.py", line 851, in run
result = context.run(func, *args)
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\utils.py", line 661, in wrapper
response = f(*args, **kwargs)
File "C:\dene\audio-webui\webui\modules\implementations\ffmpeg_utils.py", line 71, in strip
result = run_command(f'ffmpeg -y -i "{a.name}" "{out_file}"')
File "C:\dene\audio-webui\webui\modules\implementations\ffmpeg_utils.py", line 14, in run_command
return subprocess.run(command)
File "C:\Users\atlas\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 501, in run
with Popen(*popenargs, **kwargs) as process:
File "C:\Users\atlas\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 969, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\atlas\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1438, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] Sistem belirtilen dosyayı bulamıyor
Other Bug
when i try to download from youtube, i get this error:
Traceback (most recent call last):
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\queueing.py", line 407, in call_prediction
output = await route_utils.call_process_api(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\route_utils.py", line 226, in call_process_api
output = await app.get_blocks().process_api(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\blocks.py", line 1550, in process_api
result = await self.call_function(
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\blocks.py", line 1185, in call_function
prediction = await anyio.to_thread.run_sync(
File "C:\dene\audio-webui\venv\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "C:\dene\audio-webui\venv\lib\site-packages\anyio_backends_asyncio.py", line 2144, in run_sync_in_worker_thread
return await future
File "C:\dene\audio-webui\venv\lib\site-packages\anyio_backends_asyncio.py", line 851, in run
result = context.run(func, *args)
File "C:\dene\audio-webui\venv\lib\site-packages\gradio\utils.py", line 661, in wrapper
response = f(*args, **kwargs)
File "C:\dene\audio-webui\webui\modules\implementations\audio_download.py", line 14, in download_audio
ffmpeg
File "C:\dene\audio-webui\venv\lib\site-packages\ffmpeg_run.py", line 313, in run
process = run_async(
File "C:\dene\audio-webui\venv\lib\site-packages\ffmpeg_run.py", line 284, in run_async
return subprocess.Popen(
File "C:\Users\atlas\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 969, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\atlas\AppData\Local\Programs\Python\Python310\lib\subprocess.py", line 1438, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] Sistem belirtilen dosyayı bulamıyor

Install ffmpeg on a system path. (The same dir as audio-webui might work as well)
Download an ffmpeg release (you probably want ffmpeg-master-latest-win64-gpl-shared.zip)
Same dir as audio-webui (ffmpeg will not be available from other programs)
Open the zip, and drag the contents of the bin folder into your audio-webui directory.
System-wide (windows path) (NOT RECOMMENDED)
Open the zip, and drag the contents of the bin folder into your C:/windows/ folder, this is not recommended because it is harder to uninstall.
System-wide (new value in path)
Create a folder anywhere that you want to make available to all programs.
Add this folder to your path
Open the zip, and drag the contents of the bin folder into your folder you added to the path.
After installing ffmpeg
Relaunch the webui.


Flow for nominating a project you don't control?

I'm doing a little work this afternoon to set up an app that that hasn't had a release in 4 years. It seems to work for my purpose, but it makes use of a popular platform API and there are some open issues about pieces of functionality have become non-functional without significant hoop-jumping due to platform security changes.
I could see a sad dance in a lot of issue comments there, where people were wishing out loud that someone would fork and maintain the project (but, obviously, none willing/able to make the jump themselves). When I saw them, I thought of how many times I've seen an ASK HN thread that boils down to, "I'd like to work on a project for experience or resume-building, but I don't have any green-field ideas of my own."
I found your project while searching around to see who all is actively picking at this issue, but it seems like your flows/wording/UI are very focused on a project-owner finding additional maintainers. (I don't mean to suggest this is the wrong emphasis--I think stabilizing useful projects before the maintainer becomes completely unresponsive is both simpler and more useful for the OSS community.)
If you aren't already considering it, I think there may be additional value to add here with a flow for project users (or prospective users) to nominate projects that are (or appear) to be unmaintained. This task would probably need its own interface and rules/procedures since it's more uncertain/delicate than the owner seeking help.

Thanks, @abathur for opening the issue. That’s a very interesting idea!
I think I’ll need to think more about it, and I will come back to you very soon.

I thought a bit about that nomination feature, and whereas I first thought, it might be too much outside the scope of what I thought Adoptoposs would be, I like certain aspects of the idea more and more.
As mentioned in #92, it would extend the target group from active maintainers and people interested in becoming (co-)maintainers to the actual users of a project that lacks maintenance. I.e. way more people could potentially be included in keeping projects mainained and generating attention for projects in need of maintenance.
There are several question coming to my mind, when I think about a concrete flow.
If we assume the basic feature would be that any users can nominate projects (by submitting a url or searching for e.g. a GitHub repo):

How would we make sure that a nominated project is actually not actively maintained anymore?
Some projects appear to be abandonned or their maintainer seem to be inactive, because of too many incoming requests and issues. The project would still be a candidate for finding co-maintainers in order to handle the work load, but a nomination would maybe not make too much sense here.
The first step for that project should still be to open an issue directly on the project's GitHub page and offer help/ask for the maintenance state.
Technically, however, you could only allow nomination for projects that have open issues/PRs and didn't receive any updates on their main branch for a certain amount of time (a year?)

Is it important to ensure that?

Whould it make sense to let users vote on nominated projects?
...maybe in order to make them more visible to potential future maintainers, show the importance of a further maintenance? (see https://github.com/adoptoposs/adoptoposs/issues/80#issue-642467102, point 2.)

What happens if a nominated projects received lots of votes?
I.e. Is there sth like a "successful nomination"? What would a typical action after a "successful nomination" be?
What is the role of Adoptoposs here - would it just be generating visibility for most wanted to-be-maintained projects?

Why could you not just open a "Let's find new maintainers" issue on the repo?...
..., share it on social media and let people vote via 👍s in the issue?
I'd assume that people who are interested in the project would also know where its issue tracker lives, hence, would know were to go to offer help and e.g. discuss the further procedure of a community take-over?

There are several question coming to my mind, when I think about a concrete flow.

The details do matter, here, and I agree they're less straightforward. I'm not sure this will help, but I wanted to map out  the possibility-space a little first without worrying about process.
I guess the big positive outcomes, wrt to the goal of Adoptoposs, would be if it:

helps the project's existing maintainers find additional help at the project's current home
helps kickstart a transfer of the repo to prospective maintainers
helps users identify and coalesce around an existing fork
helps kickstart a successful new fork

It seems like the potential "bad" outcomes are things like:

It "sets off" a maintainer by doing something they don't like, such as

It encourages an unwelcome attempt to fork their project
It nags about project activity more often than they like

It wastes an unjustified amount of time/effort (for this project, and nominated ones) relative to the number of "big positive" outcomes it yields
Community blowback if a maintainer gives access or transfers a project to someone who does something disruptive (i.e., empty force-push, adds malware/backdoor, pushes out a patch that breaks systems or eats user data).

Other outcomes I can imagine (more ambiguous or conditional whether they're net good/bad):

Might help maintainers avoid some fraction of "Is this dead?" queries.
Might help some people curious if a project is dead get a more reliable signal than they could by manually trawling issues or opening their own.
Maybe nominations don't directly yield "big positive" outcomes, but generate enough traffic/reach/awareness that they still end up being a net positive (aside from going viral, perhaps the pages for them get ranked high for queries like "replacement for/alternative to/fork of [dead project]").

Whould it make sense to let users vote on nominated projects? What happens if a nominated projects received lots of votes? I.e. Is there sth like a "successful nomination"? What would a typical action after a "successful nomination" be?

I imagined something more like nominations instead of votes, and that it might take a few nominations before there would be any "action". I say nominations instead of votes because I worry that a UI asking for votes on "nominated" projects would encourage people who have no opinion to express one anyways, while an unprompted nomination is hopefully a stronger signal (obviously, an interested party can still ask everyone on Twitter to go nominate project X...)

What is the role of Adoptoposs here - would it just be generating visibility for most wanted to-be-maintained projects?

When I first posted this, I was imagining the list/signal would be something like, "A maintained fork is in demand for these projects."

Why could you not just open a "Let's find new maintainers" issue on the repo?...
..., share it on social media and let people vote via 👍s in the issue?
I'd assume that people who are interested in the project would also know where its issue tracker lives, hence, would know were to go to offer help and e.g. discuss the further procedure of a community take-over?

No disagreement with this from a community-takeover perspective (and it may be a strong case against it?) But I think the case for Adoptoposs here is roughly unchanged--it's the prospect that someone not already aware/entangled with the project will take interest in adopting it (it'd just be by fork, instead of by invite).
The above said, while thinking through this again now to answer you, I guess there are some additional places to add value, here?

If it gets to the point where organizing a fork is merited, it could (and probably should, to avoid a particular bad outcome) open an issue on the repo where maintainers have a chance to object, and where 👍 s get ported back to Adoptoposs as part of the interest/demand signal.
Helping answer the existing/new fork question. Others may already doing this with "active-fork-finder" sorts of tools; I'm not sure how up-to-the-task they are. Some of this is stats, but it might entail opening an issue to clarify whether it's a maintained fork, or if they're just using it as a base to customize/repurpose.
Playing a sort of dating-site role if multiple people express willingness to help maintain a project, but no single person is willing to fork it outright. This can start very simple, but I can also imagine a lot of room to refine it. For starters: try to connect these people in chat and give them a few topics to talk through. Bootstrapping an org/team/fork for them would be a nice touch once a few people agree to jump in together, if the API can handle it?
Once a fork is established, redirect people to it (or maybe only after they cut a release?
If a project has been inactive for a long time, there may be many forks with small fixes. GH doesn't make it terribly easy to get a bird's-eye view of these, but a good first task for a fresh fork is surveying them for signals to both emphasize and de-emphasize:

multiple people making the same change
commits that mention specific open issues on the parent repo
things that smell like maintenance: new releases/tags, README/CHANGELOG/HISTORY updates, authorship updates, doc/homepage links changing, new stars/issues/PRs
whether a given change is mergeable or conflicted
things that smell like someone just personalizing; fiddling CI/config/preference files, changing whitespace, changing line-endings, reformatting the whole repo, repathing hard-coded executables...

mmh,
reading over this, my very short two cents are: "enabling the community around a project to make sure the project stays maintained is a good idea for starters".
For the most part, I share the same concerns as @abathur with regards to making sure that the original authors regain a degree of control. One quick idea would be to allow opting in to this flow, e.g. per project a maintainer shows on adoptoposs you'd have a setting like:

Do you want this project to be recommendable?
Grace period in days to confirm a recommendation - this would be something like "Hey, if somebody starts to nominate this project, wait X days for me to confirm/deny the recommendation. if I am unresponsive, auto confirm it."

It's not 100% on-topic here, but it's close enough that linking it here feels more appropriate than opening a new thread...
The HN thread about Moment.js calling their project "done" has a fair amount of germane commentary :)

It's not 100% on-topic here, but it's close enough that linking it here feels more appropriate than opening a new thread...
The HN thread about Moment.js calling their project "done" has a fair amount of germane commentary :)

Interesting, thanks for sharing!

At this moment you cannot even list a project where you have ownership rights if you do not have ownership over the entire organization hosting it. I tried to list https://github.com/ansible-community/ansible-lint but I am hopeless and there is not way to add it.

Hey @ssbarnea, I think that might have sth. to do with the access rights on organizations one grants when authenticating with GitHub oauth. Could you try to cinfirm by revoking authorization of the Adoptoposs Oauth app in your GitHub users account settings --> "Authorized OAuth apps", and then log into Adoptoposs again and if possible select the respective organization?


Advancing to a completed non-looping animation state with reset = false does not perform the final key frame's changes.

Godot version
v4.1.2.stable.official [399c9dc39]
System information
Godot v4.1.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GT 730 (NVIDIA; <IP_ADDRESS>14) - Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 Threads)
Issue description
I have an AnimationTree state machine with two states: falling and attack.  Both are non-looping animations.
What I want to do is have a falling animation where the final key frame values are held until the player hits the ground.
The attack state can interrupt the falling state at any point and after playing completely through (switch mode = At End), returns to the falling animation state where it left off (reset = false).
However, if the falling state has reached its end when the attack state is started, returning to the falling state does not process the final key frame values.  I would expect the final key frame state to be set.
Steps to reproduce

Run the attached project.
When the falling animation finishes and top text says to press Space, press Space,
Note that the attack animation is performed.
When the final attack frame displays, note that the text stays the same and does not return to the "falling 2" text despite the fact that the state machine transitions to the "falling" state.

Note: I used a TextEdit control instead of a Label by accident.  The behavior is the same though.
Minimal reproduction project
AnimationTreeTest.zip

This is simply because there is nothing left to play there anymore, so there is no transition. I understand that there needs to be a case where the transition takes place even though the animation has stopped.
It is not impossible to implement that behavior and I agree with making it the default behavior, but conversely, is there a case where we do not want to transition? (an option needs to be added) How do you think? @SaracenOne

I've had a look at this, and I agree, it is very strange and unexpected that the transition occurs but no animation occurs. At present, I can't think any scenarios where this behaviour might be desirable, but I understand wanting to exercise caution when making a change like this. I'll think about this some more and maybe even take a look at what other engines do in this situation to get some more grounding on what would be considered the most correct behaviour.

I thought again about it, but if there is nothing to play there, skipping the transition is most desirable. However, there is use case where the anyone want to continue to show last frame, so I believe that a correct way would be to implement an option like keep_last_frame that explicitly displays and processes (like looping) the last frame.

I believe I've only halfway demonstrated the issue.  It is not just the final frame.
In general, transitioning to a new state does nothing visually until a key frame is reached, if ever.  This is not always the desired behavior.

In general, transitioning to a new state does nothing visually until a key frame is reached, if ever. This is not always the desired behavior.

This is just your problem with InterpolationMode being Discrete. You should set it to Continuous.

I was just getting ready to say that, but I think using an interpretation mode of Nearest messed with the timing.  Will have to see whether I can duplicate.

FYI also keep in mind there is PR related to Discrete mode with blending.

https://github.com/godotengine/godot/pull/86629

Ah, that looks interesting.  Thanks for mentioning it.
Apologies, but despite my best intentions, this is looking like a noob problem.

Heh, I can't seem to edit the text to add a new key frame while the track is in continuous mode.  Keeps reverting back to the previous frame's text.

I expect that in most of such cases, you forgot to deactivate the AnimationTree.

It appears that using Continuous update mode with Nearest interpolation produces the expected behavior and resolves the original "issue".  I remember trying this when I first created the issue, but I think it looks correct now.
Thank you for looking into this and the help.
I'm going to close this.


Update source_gen version to ^1.0.0 for retrofit_generator 2.0.0-beta1

Describe the bug
When using retrofit_generator and injectable_generator together, pub get fails due to a lower version of source_gen (^0.9.10+4) specified for retrofit_generator.

To Reproduce
Steps to reproduce the behaviour:

Add the following dev_dependencies to a null safe pubspec file

dev_dependencies:
flutter_test:
sdk: flutter
injectable_generator: ^1.2.1
build_runner: ^1.12.2
retrofit_generator: ^2.0.0-beta1

run pub get
See error mentioned above

Expected behavior
Both null safe generators should use the null safe version of source_gen and be able to run with out dependency_overrides.
injectable_generator uses source_gen ^1.0.0 which is the null safe version.
Please let me know if you need any more details. Thanks for all your work.

@rugemo I have the same issue with json_serializable package.

I have the implementation finished but we are waiting for #319 to be fixed and merged

I got same issue with freezed package. Is there any temporary solution please?

See #323. Until this is merged you could use git references in your pubspec.yaml


Update README.md

Made instructions clear so it can run on linux

@ioandev Thank you to identify this [#2]  small mistake in instructions. Actually in Windows machine it's never makes any problem.
Please update to  latest version v2.1.1. Everything  is now improved and corrected.


Instance does not belong in ASG when scaling down

Under specific circumstances, Escalator isn't able to terminate nodes in an ASG. This is due to the DeleteNodes() function in the AWS cloud provider returning the following error:
node ip-10-153-110-221.ec2.internal belongs in a different asg than <asg>

The cloud provider Belongs() function is responsible for determining if a node belongs in the target ASG and in this situation it is returning that the node isn't in the ASG.
The Belongs() function uses the results from an AWS DescribeAutoScalingGroups API call in the current run, so it could potentially be an issue with AWS returning invalid ASG information.
The problem seems to fix itself by restarting the pod that Escalator is running in, which may mean it is a problem with Escalator.
Some possible causes:

The Belongs() function does not work properly
AWS is returning incorrect information on the DescribeAutoScalingGroups API call

We've seen this occur in the past with Autoscaling API outages with AWS which leads me to believe it is a problem with AWS
Maybe Escalator is using a problematic Autoscaling API endpoint and by restarting the pod it uses a newer, working one

@mwhittington21 has just noticed a similar situation to this one occurring, but with other information retrieved from AWS - the ASG size and target size.
The AWS cloud provider node groups become stale with the incorrect values, even after running .Refresh() on the node group on each run.
This is causing situations where Escalator goes to increase the target size of the ASG, but believes the ASG target size is set to 3, but is actually set to 4. It then tries to increase the target size from 3 -> 4, which does nothing because the ASG target size is already 4.
We can also see that the size of the ASG (number of instances) does not match the number of Kubernetes nodes in the node group in the cluster in the metrics that Escalator exposes.
Logs from Escalator:
time="2018-09-09T04:10:58Z" level=debug msg="**********[START NODEGROUP default]**********"
time="2018-09-09T04:10:58Z" level=info msg="pods total: 4" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="nodes remaining total: 7" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="cordoned nodes remaining total: 0" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="nodes remaining untainted: 2" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="nodes remaining tainted: 5" nodegroup=default
time="2018-09-09T04:10:58Z" level=warning msg="There are less untainted nodes than the minimum" nodegroup=default
time="2018-09-09T04:10:58Z" level=warning msg="There are no tainted nodes to untaint" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="increasing cloud provider node group by 1" drymode=false nodegroup=default
time="2018-09-09T04:10:58Z" level=debug msg="IncreaseSize: 1" asg=nodes
time="2018-09-09T04:10:58Z" level=debug msg="SetDesiredCapacity: 4" asg=nodes
time="2018-09-09T04:10:58Z" level=debug msg="CurrentSize: 3" asg=nodes
time="2018-09-09T04:10:58Z" level=debug msg="CurrentTargetSize: 3" asg=nodes
time="2018-09-09T04:10:58Z" level=debug msg="Locking scale lock"
time="2018-09-09T04:10:58Z" level=debug msg="Scaling took a total of 133.774555ms"

Note the following values from the logs:

CurrentSize: 3
CurrentTargetSize: 3
nodes remaining total: 7

Screenshots from metrics graphs at the same time as the logs:

Note the following from the graphs:

Number of Kubernetes nodes matches the "nodes remaining total" value: 7
Target size: 4

It seems that the TargetSize and Size (and possibly MinSize + MaxSize) in the following file are using incorrect/stale values: https://github.com/atlassian/escalator/blob/master/pkg/cloudprovider/aws/aws.go#L129-L149
As with the parent issue, it fixes itself after restarting Escalator's pod.
What's also interesting, Escalator didn't try to untaint the already tainted nodes to solve the "there are less untainted nodes than the minimum" issue:
time="2018-09-09T04:10:58Z" level=info msg="nodes remaining untainted: 2" nodegroup=default
time="2018-09-09T04:10:58Z" level=info msg="nodes remaining tainted: 5" nodegroup=default
time="2018-09-09T04:10:58Z" level=warning msg="There are less untainted nodes than the minimum" nodegroup=default
time="2018-09-09T04:10:58Z" level=warning msg="There are no tainted nodes to untaint" nodegroup=default