chore: cleanup .eslintrc & fix ESLint warnings

This makes the .eslintrc file clearer + removes unnecessary rules (as they were already fixed)

This PR is for main branch

#2247 Is already changing internal ESLint config


Use default CAs if neither cert or cert path is provided

Fixes #81

Do we have any timeline for when this fix is going to be released?


Breaking Change: Insecure HTTP connections are disabled by default on iOS and Android.

There are some breaking changes in the flutter's network policy : https://flutter.dev/docs/release/breaking-changes/network-policy-ios-android
Because of these changes, the app even on putting a right URL in the location field gives a "Invalid" toast.
In general the local host runs on HTTP. So we need to allow the use of http connections in debug builds.

@PaRaDoX50 can you assign this to me?? As far as I've understood this issue, all I need to do is
<meta-data android:name="io.flutter.network-policy"
             android:resource="@xml/network_security_config"/>

Add this above line to network_security_config.xml for the android app.

@PaRaDoX50 @harchani-ritik can you assign this to me?? As far as I've understood this issue, all I need to do is
<meta-data android:name="io.flutter.network-policy"
             android:resource="@xml/network_security_config"/>

Add this above line to network_security_config.xml for the android app.

Actually, there are couple of ways to do it. We can either edit the Network Config file and add the code you sent above to the manifest file,  if we want to allow HTTP connection for  some specific domains or we can add one single attribute to the application tag to the manifest file if we want it for every address.
We need to edit the debug manifest file since we should only allow unsecure connection in debug mode.
Actually I was going to send a PR. I hope you don't mind.

@PaRaDoX50 ya no issue, please go ahead🙂

@PaRaDoX50  Thanks for pointing out and fixing this.


Throw expressions

Summary of the new feature/enhancement

As a user I want throw expressions so that I can chain them with operators such as && and ||. This enables me to have more concise throw statements when a command fails.
Right now we can do (taken from Powershell documentation):
$result = Write-Output 'Value' && $(throw 'Bad')

I propose only to simplify it to
$result = Write-Output 'Value' && throw 'Bad'

For reference, right now it throws (different) error stating:
throw: The term 'throw' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

My idea is based on what C# has https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-7.0/throw-expression.
Proposed technical implementation details (optional)

I believe just allowing the syntax parser to parse this would make this work as expected as the throw statement would be executed at that point and nothing else would be including any potential usage or assignment of the value that is expected to be returned from the expression.
If this is seriously considered I think it would be best to reach out to a C# team member to ask if there were any issues with this.

First  $result = Write-Output 'Value' && $(throw 'Bad')
Is a dreadful example for the help.

Nothing should ever use   $variable = write-output <<some_constant>>
$result = 'Value' && <<anything which doesn't throw>> puts "value" into $result and the puts a second value in if there is one,   throw leaves$ result empty.

There's a much wider constrain to do with language keywords.  You can't , for example, do
foreach ($x in $Y) {$x +1 } | some-command
for / foreach / while / if / throw / break / continue  are not pipelines and as the help says  under "Operator syntax and precedence"

Unlike other operators, && and || operate on pipelines, rather than on expressions like + or -and, for example.

$result =  'Value' && while ($x -lt 3) {$x ++} won't work either. nor will.
$result =  'Value' && if ($true) {"boo"}

@mladedav, I empathize and certainly wish the $(...) wasn't needed, but this has been discussed at length in #10967; specifically, @rjmholt explains here and here why the fundamentals of PowerShell's current grammar prevent a solution.

The short of it: throw is a statement, as are constructs such as if and foreach, and the only way to nest statements inside a statement is via $(...).
@jhoneill's examples, such as foreach ($x in $Y) {$x +1 } | some-command, therefore do not work for the same reason - even though I wish they did (#6817).

As an aside: The curious thing is that statements are allowed without $(...) if they are the standalone RHS of an assignment; e.g.:
$var = foreach ($i in 1..3) { $i }  # $(...) NOT required in this case.

P.S.: Here I've made a proposal to modify the grammar slightly, in order to at least allow using exit , return, throw as-is in pipeline chains (with && and ||), but my knowledge isn't deep enough to know whether (a) that is technically feasible and (b) without breaking backward compatibility.


Sounder approach to parsing CSS attribulte selectors

One way to address #1080. Breaks BW compat though, since m('[foo="b"a"r"]') no longer sets attrs.foo to 'b"a"r'.
If you agree with the approach, this also probably mandates a docs update... Or maybe we keep this for the rewrite?

Actually, I have an idea to better preserve backwards compat...

Updated (the test pass, Travis had a NPM glitch). Now it first tries to match a real string, and otherwise falls back on the old behavior.
So it will affect attribute selectors with embedded quotes and backslashes.
m('[foo="wa\\t"]') must be updated to m('[foo="wa\\\\t"]') otherwise "\t" is interpreted as a tab.
m('[foo="wa"t"]') still sets foo to 'wa"t'.
m('input.[required][pattern="[a-zA-Z0-9\\"]{56}"]') (@wedancedalot's pattern with a twist) produces pattern: '[a-zA-Z0-9"]{56}' as desired.
Most strings must be parsed, though, with a perf cost. Since the | operator for JS RegExps is ordered (like PEGs, unlike CFGs), you must first try the "valid" pattern, since a shorter, invalid match would take precedence otherwise.

@pygy That would've been a failed PhantomJS install that Travis borked over...

I reran the build, and Travis is now happy.

@lhorie That's where the merge conflicts came from... (I was confused about that.)

I'm closing this in favor of 80349b3c740d0111e67874e3addd8f3cc3b88ac4

The fix looks pretty good :-) Much better than what I offered, as eschews double parsing while allowing arbitrary strings.
Actually, it still accepts the ill-formed strings as well.
I'm a bit puzzled by the presence of \] in the escape sequence set \\["'\]] of the first regexp, especially since you don't unescape it further down, and it can be left unescaped.
m('[foo="\\"]"]').attrs.foo returns '"]', and m('[foo=a\\]a]').attrs.foo returns 'a\]a'.
In CSS, unquoted values must be valid CSS selectors (matching /-[\w][-\w]*/ plus non-ascii characters). It's IMO nice that you accept a broader range of values unquoted, but you shouldn't bend over backwards to support non-standard characters in bare values.

@pygy I agree that prop="\\]" should compile down to prop: "]". It's an escaped character.


Cannot select nested component if parent has @mouseover.stop

If a component has a @mouseover.stop handler defined, no child components can be selected via the devtools components tab. However, it works as expected using the component inspector tool.
Here's a reproduction: https://stackblitz.com/edit/vitejs-vite-j4abqj?file=src%2Fcomponents%2FHelloWorld.vue

It's might a bug of vite-plugin-vue-inspector

Just using vite-plugin-vue-inspector on its own seems to work fine. Try it here: https://stackblitz.com/edit/vitejs-vite-7ujp2h?file=src%2FApp.vue
Do both ways of selecting a component use this plugin?

We need to find a way to force ignore stopPropogation

So after a little digging around, vite-plugin-vue-inspector uses mousemove for highlighting components. This can be replicated by adding @mousemove.stop to a component, which will then stop the highlighting of nested components. See: https://stackblitz.com/edit/vitejs-vite-cufj5x?file=src%2Fcomponents%2FHelloWorld.vue
We could have devtools-next use mousemove to be consistent with vite-plugin-vue-inspector, but going with the suggestion by @alexzhang1030 would be more robust.


[4.6.1] Windows Multimedia Keys

OS: Windows 10 Home 64-bit
GPMDP Version: 4.6.1
Issue Descriptions: Multimedia track navigation keys misbehaving.
Steps to Reproduce: Pressing multimedia key forward on the keyboard will result in two tracks skipped. Pressing multimedia key backward on the keyboard will result in two tracks skipped. Example: assume you're listening to track 4 of a playlist/album. Pressing forward will go to track 6 instead of 5.
Note: Similar to closed #2107 from version 4.1.1.

I've come across this issue as well.

I am unable to reproduce this issue. The multimedia keys work exactly as expected. On Win 10 64, GPMDP 4.6.1 as well.

I, too, have this issue on WIndwos 10.
If it matters, my keyboard is the Logitech G910.
Also, in GPMDP (using YouTube Premium Music), I have the Windows 10 System Media Service (with song information) enabled.
What I have also noticed is that sometimes, when skipping songs, the playback gets paused.
It also happens both when the program is open in the fore gorund or in the back ground.

Adding a little bit more information: I've reinstalled and it initially did not present the problem. However, I remembered that I like to have the song info on the "Windows 10 Volume Control" and "Windows 10 Media Server". Enabling the Windows 10 Media Server option brought the bug back.  Disabling it made the bug go away again.

Yeah, it seems that disabling the Win10 media service gets rid of the issue, but it also gets rid of the nice volume overlay.

Double of: #2364
This is mainly due to Windows Media Service + GPMDP Still both picking up on the Next Media Key it seems.

With the Windows 10 media service disabled in settings, how do I get GPMDP to capture the media key events so I can control it while in a fullscreen game?

I have this same issue as well.

Same issue on 4.6.1 with Media Service enabled, Win 10 Pro 64-bit.

It seems like you may already be aware of this, but at least for me, this same thing is happening with the play/pause button too.  Semi-frequently it will trigger twice, causing my music to stutter but keep playing.
It's consistently happening with both back and forward skipping every time.
These only happen using this application and my keyboard is a Logitech G910 Orion, if it helps.

This doesn't seem to be getting any attention from @MarshallOfSound but figured I'd add my experience too.
I am having the same issue with Windows 10 64-bit, a logitech g910, and the Windows Media Service enabled much like @Klorkson . Happens regardless of if GPMDP is focused or not.

Also having this issue. It only happens for the skip forward/skip backward buttons (play/pause seem fine). As others have mentioned, it definitely appears to be the fact that the button is controlling the Windows Media Service and GPMDP, so it receives the skip forward/backward signal twice. Don't think the specific keyboard I have matters, but it's a Logitech MK710.

Looking into it a little more, it seems that the media hotkeys on keyboardshortcut.js need to be disabled when the W10 media service is enable, because it gets handled at win10.js.
This commit seems like it would fix the issue, but I know that there was some hesitation because not all users have this issue. Is it possible to add a setting for "Media Key Bug Fix", so that users with the issue could choose to enable it?

Can you make a pull request for this?

...
This commit seems like it would fix the issue, but I know that there was some hesitation because not all users have this issue. Is it possible to add a setting for "Media Key Bug Fix", so that users with the issue could choose to enable it?

Can you make a pull request for this?

I doubt it. @Kytech previously forked the repo and fixed the issue here which was over a year ago and we still have the bug. See his comment on the issue. Shouldn't this issue be closed for #2364

@indefiniteben, so is this a won't fix?

You'd have to ask @MarshallOfSound I guess (you're a contributor so probably know better than me)? But #2364 has a won't fix from him, but that just means someone else needs to make a complete fix. See this quote from that issue:

I don't really have time to go chasing patches 😆 If someone has a fix it would be good to submit as a PR here so I can review and potentially merge to get everyone on the right track.

I take it that if that commit fixes the problem without introducing more issues, if a PR is approved it'll be implemented? But then I thought a fix was about to land a year ago when Kytech made his fix.
As a user: I take it that this change would not be a "fix" but a toggle between current style and Windows style media control. I don't know if it's acceptable from a dev PoV, but it is from mine.

It's acceptable from mine. I've only contributed to documentation, you know
about as much as me for the rest.
On Mon., 17 Sep. 2018, 10:10 pm Ben Pyman<EMAIL_ADDRESS>wrote:

You'd have to ask @MarshallOfSound https://github.com/MarshallOfSound I
guess (you're a contributor so probably know better than me)? But #2364
https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/2364
has a won't fix from him, but that just means someone else needs to make a
complete fix. See this quote from that issue:
I don't really have time to go chasing patches 😆 If someone has a fix it
would be good to submit as a PR here so I can review and potentially merge
to get everyone on the right track.
I take it that if that commit fixes the problem without introducing more
issues, if a PR is approved it'll be implemented? But then I thought a fix
was about to land a year ago when Kytech made his fix.
As a user: I take it that this change would not be a "fix" but a toggle
between current style and Windows style media control. I don't know if it's
acceptable from a dev PoV, but it is from mine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/3293#issuecomment-421988907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG_nCHw8zxU9jbCRBGwV8mIX1iQwi6EVks5ub5E6gaJpZM4VhQr6
.

I actually have an issue where my track skip media keys only work intermittently. Anyone know any fixes? Does this for me even with app in foreground and no change if I have a fullscreen app up (still works, but intermittently). No other media apps seem to have this issue so I can only assume it's something with how this one handles media keys?

This issue still occurs for me when I enable Windows 10 System Media Service in the options.
Disabling it does fix everything, but as mentioned above, there's no track info without it.

I noticed this issue a while ago, and was surprised it hasn't been fixed... I can reliably toggle the issue by turning on/of "Show track information in Windows 10 volume overlay"; when that setting is checked media keys register twice, when that setting is unchecked media keys register once.
I also have a G910, but I tested it with another keyboard (some generic Dell one) and the issue persisted.

At this point I am just adding to the list of people saying they are having the issue. I too am experiencing this.
It seems that if the in app track skip feature was killed when the Windows 10 media setting was enabled it would resolve this issue.
Settings on: Enable the Windows 10 System Media Service, Show track information in Windows 10 volume overlay.
Troubleshooting steps: After disabling the "Show track information in Windows 10 volume overlay" The issue subsided. I noted that the "Enable the Windows 10 System Media Service" is supposed to show info on the lock screen but does not. Issue no longer exists and skipping works fine. Enable that option again and the skipping action is happening twice again.
OS: Windows 10 Pro x64 (1803)
I love the app and the Discord integration. Great work!

Same issue here.
As previously mentioned, clicking Next/Previous track using Media Keys with "Enable the W10 System Media Service" causes GPMP to skip two tracks instead of a single on.
Disabling it causes normal behavior, but shows no "Volume Overlay" due to being disabled.
App Version: 4.6.1
OS: Windows 10 Pro x64 Version 1809 (OS Build 17763.475)

@IndefiniteBen, I'll be starting up work again on this fix towards the end of the month. I haven't had access to a PC for a while and have been unable to update and test my fix for a more recent version before I submitted the pull request. I'll have my progress updated on #2364 as I make progress.


New repository state is unreliable

Current
When I add new repository first observed state after creation is Active, then eirther:

state stays Active
state changes to In Progress

then changes back to Active
or stays in In Progress

I recorded problem on third retry (15s):
Screencast from 2023-11-24 14-18-27.webm
Expected

New repository initial state should be In Progress
After initialization it changes to Active

Env:

Rancher 2.8.0-rc3
local cluster
k3d v1.26.9+k3s1

We tried to reproduce the issue and it does not set to In Progress status.

Very few times it shows an In Progress status for a few milliseconds but then it changes to Active.
Please could you confirm what you see for metadata.state in the response to the HTTP POST request made when creating the repo resource.
or if there are any websocket updates for the resource.

When I add repository and state stays In Progress I see this in chrome dev-tools network:

There is a warning in response headers: Warning: 299 - unknown field "type"
I don't see any websocket updates, metadata state seems fine:

        "state": {
            "error": false,
            "message": "Resource is current",
            "name": "active",
            "transitioning": false
        },

I noticed state changes from In Progress to Active after 5 minutes.
I tried on chrome and firefox, it behaves the same


compoentWillRecievenewProps is not available

Its does not check for new props. It is making this things difficult to handle things on props changeS

@TonyFrancis there are a lot computations that happens on an initial load and we'll have to be smart about filtering those computations on componentWillRecieveProps, however it is an enhancement I'm currently looking into.


Memorize the width of the right sidebar or make the default width configurable

This is about the default width of the element #red-ui-sidebar that is applied on the initial Node Red interface reload.
After reading the discussion here:
https://discourse.nodered.org/t/is-there-a-way-to-set-a-minimum-size-for-the-sidebar/41320
it comes to these two points:

It is somehow "accepted" that the "open width of the sidebar is stored in the users browser local storage" - wrong, it is reset to a default setting every time browser window with Node Red main UI is reloaded and that "default setting" is too narrow for most modern desktop display resolutions.

it has been suggested that it should be "ok to resize the side bar manually whenever needed" - clearly written by those who don't use the Node Red for what it has been actually designed for (developing your own flows and dashboards).

It quickly becomes a chore to resize the right side bar from it's default width and make it bigger every single time because by default it is too narrow to contain the essential buttons such as "Context Data" and "Dashboard" that lead to the relevant tabs directly (with a single click).
I understand that user screens and viewports can be very different depending on the device and the use case, but for those with reasonably wide desktop monitors (pretty much a standard on a desktop these days) the constant manual resizing becomes total nuisance very quickly.
Proposal: either memorize the width of the right sidebar properly in a browser local storage, so that it is applied on the next UI reload, or make it possible to set a default min-width for the sidebar easily (at the moment it is set dynamically because of the drag event for the red-ui-sidebar-separator element).

Closing in favour of #3431


brew install

making this installable via brew would be fantastic, i could possibly help just haven't done it before

I'm open to accepting a PR but not interested in doing this myself. I'm not sure brew can install something in the Applications folder. I've only ever used brew for command line utilities.

By the way, there is an installer package in the releases tab.

Looks like this project is able to install an app via brew so it might be possible to copy what they've done with their brew cask.


Tk 8.4.20

Create releases for Tk 8.4.20. It fails to build.

Fixed by 3ebf4aebc7b2511489b485698b2926749c415c27


Project config file at path app/code/Vendor/Module does not exist.

I have installed the phpstan-magento on
composer require phpstan/phpstan ~1.7.2
composer require --dev phpstan/extension-installer

After running the phpstan command to analyze the code
vendor/bin/phpstan analyse -c app/code/Vendor/Module --level 0

is giving error

Project config file at path app/code/Vendor/Module does not exist.

@MagePsycho do you have a module called 'Vendor_Module'? The directory you're pointing it to probably does not exist, it needs to be pointed to a valid module.

@MagePsycho maybe you can find some guidance in this repo https://github.com/hivecommerce/magerun2-list-api-endpoints

IIRC correctly our conversation on LinkedIn the problem is solved. If you run into further issues, feel free to open another issue. Thanks for giving this extension a try! Hopefully, you'll find it useful.


Pearl

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes # <243>

Mark the task you have completed ✅

[✅] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[✅] I have performed a self-review of my own code or work.
[✅] I have commented my code, particularly in hard-to-understand areas.
[✅] My changes generates no new warnings.
[✅] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[✅] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[✅] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[✅] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @pearlrathour ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@pearlrathour Also send a Demo vedio after making changes

Hey @pearlrathour 👋!
@kunjgit here,
We have this annoucement to make 📢!!
During the time of PR don't alter main index file ! 🙂
In main Readme file just use * as a game number during the time we are merging we will add number !! 👀
Make sure you join our Discord🕹 if you haven't 😇
Thank you 💗!

Thank you  @pearlrathour , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Android: Right to Left menu does not animate first time

I'm targeting XF 3.6.x in my project and have noticed that on Android when the menu first opens it does not animate and just appears in position. When closed it animates and on any further opening animates as expected.
The Sample app behaves as expected on the same Android device but targets XF <IP_ADDRESS>0555.
Is anyone else experiencing the same issue?

I tested on Xamarin.Forms Version="<IP_ADDRESS>4457" and could not reproduce this issue
do you have any sample project  that reproduces the behaviour you mentioned?

Hi Gonz,
I have exactly the same issue. Did you manage to find a solution as yet?


feat: Add Drive Picker samples (Fixes #9)

feat: Add Drive Picker samples (Fixes #9)
Copied from https://developers.google.com/picker/docs/

Adds 2 HTML files for Drive Picker (not the Java files)
Adds region tags
Fixes htmllint issues mentioned below

drive/picker/driveitems.html: line 20, col 5, tag attributes are malformed
drive/picker/helloworld.html: line 20, col 5, tag attributes are malformed

Thanks Grant!


Group by support for Query expression / Query action

$title. Ref: https://github.com/ballerina-platform/ballerina-spec/issues/441

Duplicate of https://github.com/ballerina-platform/ballerina-lang/issues/36810


refactor: update blas/ext/base/snansumors to follow current project conventions

Resolves #1531
Description

What is the purpose of this pull request?

This pull request:

refactors blas/ext/base/snansumors package

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #
fixes #

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@Pratik772846 This PR includes changes from any-in-by. I believe you branched from the wrong base branch. Would you mind cleaning up this PR to only include the changes for snansumors?
Also, would you mind checking the box in the OP that you've read the contributing guidelines? Thanks!

@kgryte As we have discussed in here, we donot require Julia benchmark in any-in-by , thats why i have removed them.


feat(controller): disable swap usage if there is a memory limit

This change requires docker 1.5.0
closes #3205

CoreOS 607.0.0 with Docker 1.5.0 landed in the stable channel just now. We are prepping a PR and then we can revisit this.

#3316 was merged, so we're on Docker 1.5.0 now.

Code LGTM!
@aledbf would you mind rebasing this, please? :)

My only concern is with older CoreOS clusters running deis v1.5. Is that supported or are we suggesting users to upgrade to CoreOS 607 with the latest release>

My only concern is with older CoreOS clusters running deis v1.5 which won't have docker 1.5 installed. Is that supported or are we suggesting users to upgrade to CoreOS 607 with the latest deis release?

We'll need to support upgrades. This PR will have to be upgrade-proof, and fail silently on Docker < 1.5.

#3319 is similarly going to support older CoreOS versions.

@carmstrong ok.
Check the CoreOS version in the node using the values in /etc/os-release and if that is < 591.0.0 then docker < 1.5.x?

Check the CoreOS version in the node using the values in /etc/os-release and if that is < 591.0.0 then docker < 1.5.x?

I'm not sure the clean way to do this in the controller yet, unfortunately. I'd really rather not bind-mount that file just for this one use.

I'd really rather not bind-mount that file just for this one use.

Me neither, but I don't see an easier way (and this never happened before)

IMO I'd prefer the "Heroku way" of configuration through environment variables. How about we set $COREOS_VERSION in deis-controller.service and disable mem swap if the envvar's unset or higher than 607.0.0? e.g. if I were running the controller locally on boot2docker I won't have COREOS_VERSION set, therefore memswap should be disabled

though we shouldn't be reading the envvar directly... Instead we should be reading from django.settings.COREOS_VERSION or w/e seems relevant

Instead we should be reading from django.settings.COREOS_VERSION or w/e seems relevant

I suppose that's probably the cleanest approach, although I'd prefer getting the Docker version directly rather than inferring it from CoreOS version.
Having the controller know about what the CoreOS version is seems like a leaky abstraction, but I can't see another way.

Maybe if fleet actually leaked information about the host through the api, we could figure out the docker version... swarm would have that information, I'd think, but fleet != swarm :sob:

I'd prefer getting the Docker version directly

I agree--COREOS_VERSION seems indirect. I can't think of a cleaner way than setting a DOCKER_VERSION env var and/or django.setting though.

Code LGTM pending requirements change to get it passing Jenkins.

This needs the semantic_version==2.3.1 line added to docs_requirements.txt as well so make -C docs/ test will pass.

Code LGTM.

I think this is as clean as we can get for detecting the cluster's docker version (with Fleet, at least).
Code LGTM!

I just found this https://github.com/docker/docker/pull/10633

This is the error in the tests right now:
Mar 22 03:28:56 deis-01 systemd[1]: Started configsample_v9.cmd.1.
Mar 22 03:28:56 deis-01 sh[10200]: docker: invalid size: '-1'. See 'docker run --help'.

The strange thing is that the test suite pass in many places where memory limits are applied

That is confusing. The invalid size: message isn't a warning but an error, I would assume. We need to revert this for now and follow up on the test inconsistency.

We can revisit this change now that CoreOS stable has Docker 1.7.1. Maybe after #4581 we can use the docker-py library that's already in controller to infer the Docker version.
@aledbf I'd be glad to do that unless you're already on it--let me know.


Unhandled Exception: MissingPluginException(No implementation found for method startHeadlessService on channel xyz.luan/audioplayers)

I keep getting the following error when using the player widget.
[ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: MissingPluginException(No implementation found for method startHeadlessService on channel xyz.luan/audioplayers)

I saw that it is already fixed in a PR so I will close this issue.


don't use lodash

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary.
[ ] I've tagged the changelog entry with [EAS BUILD API] if it's a part of a breaking change to EAS Build API (only possible when updating @expo/eas-build-job package).

Why
Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests.
How
How did you build this feature or fix this bug and why?
Test Plan
Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.

@ide I know that function-specific packages exist but they are deprecated. See https://lodash.com/per-method-packages


Checking for long project names

Duplicate PR. Please close.  https://github.com/Microsoft/containerized-microservices-pipeline/pull/103


[KBM] Allow for "typed" item to trigger shortcut

关于加强组合键功能的建议
更加自由的组合按键，在其他应用甚至游戏中可以使用。
比如，连续按两次A，代表以下依次按下了ASDFGHJ
连续按两次D，代表依次按下了↑↓←→
以下是Google翻译给的文字
Suggestions on strengthening the function of combination keys
More free combination of buttons can be used in other applications and even games.
For example, pressing A twice in succession means pressing ASDFGHJ in turn
Press D twice in succession, it means press ↑↓←→

定义连续按键代表什么功能

I would group this in with the key cord stuff but honestly, i'm very wary of allowing non-cord style execution like this.
https://github.com/microsoft/PowerToys/issues/6976 would be tracking item


missing raise

https://github.com/ArjanCodes/2023-fastapi/blob/8964fdec016606551c8a0e3f630ae0143ce42d21/2_creating_get_route_query.py#L40C3-L40C3
needs to be "raise HTTPEx....". The raise keyword is missing.

Thank you - it's been fixed!


Fix possible typo

uc_locs was otherwise unused, and this seems like the right thing to do.

Yep, that is what I meant. Thanks!


Diversify colors of multi-nested tags more

Hello! I have a tagging system that relies of nested tags, i.e. tag1/subtag1/subsubtag2/subsubsubtag3 etc.  And this results in unfortunately boring and hard-to-glance coloring (they are all the same under tag1, or very similar).
I would love a feature where I would be able to basically ignore a base tag for coloring purposes. I am imagining a list of tags that get ignored as prefixes.  For my use case, I would enter tag1 as the ignored prefix tag, to get more individuality between buckets.
Maybe this is more an issue I have with the variance of the tags when they are bucketed like this, as it is not super effective after 3 groups of tags it seems.
Thanks!
Note:
Here is a reproduction of what I'm talking about.  The colors only really significantly change for the first bucketing

Hello! Good point!
I'm thinking about reducing the total number of colors and also mixing in groups. Even 16 is not very distinguishable.


Top Bottom - The first item is right at the battery indicator

Hi all,
Thanks for this awesome library.
I just started using it today and got pretty much everything setup.
The problem is that the first cell of my menu is right on top of the battery indicator. What can I do to fix this?

Hi @felipecaldas. Thanks for your interest to our component!
You have two options:

Show/hide status
Play with windowLevel
Both options should be handled when the menu appears/dissapears

I suppose, it'd be better to implement the component via custom view controller with modal presenting.


Updated Audiocodes firmware version

Updated Audiocodes firmware version Supported 7.20A.250 (Recommended 7.20A.256)

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Connecting from normal WebSocket

Hi everybody,
I have socket cluster up and everything is working perfectly. I can also connect my app and the website to the socketcluster using socketcluster.ja client.
But I also do have a node server which has to be connected to socketcluster. How can I achieve this? There is no nodejs client for socketcluster. I tried using WS and Socket.io-client but I can’t establish a connection.
I need to send data from the node ja Server to my socketserver but there is no way I could connect it. Any advice?

The easy way is to send the data from the external app directly to a MQTT or Redis cluster or whatever else brokers of your socketcluster app are listening to. So, you don't have to connect as a client to your SocketCluster server at all.
If the easy way doesn't work for you, feel free to join Gitter

I have a redis server running, but how can socketcluster get triggered doing something if any action happened on redis? Is there kinda redis watch? I worked with MQTT long time ago using raspberry and home automation (lmao), but not sure how to listen for mqtt events inside my worker or broker js. Is there any documentation ?

Ok, if I get this right, I just need to install a Mosquitto Server inside my worker.js listening for MQTT messages. Should be easy.

Since you have redis already, you could subscribe sc-app to a channel in redis, then from external app publish to that channel the data.
But there is a better solution: https://github.com/SocketCluster/sc-redis

Sounds good, thanks @MegaGM

@Hirbod @MegaGM I don't think MQTT is needed here really. ScServers can act as message brokers. Also sc-redis is not scalable. The best approach, I think, is to use the ScClient in your node.js servers as well. So you have a message broker through which your nodes can communication with each other (pub/sub). You might want to include special secret tokens as well, so only trusted clients can do particular stuff.

@amin-mir merci, but how can I include ScClient inside node? I can’t require anything and I have to include the socketcluster.js file. Scaleabillity isn’t a big deal though at this stage (I’m only sending “signals” to the socket for initiating some stuff inside the app). But I would love to know how to use scClient inside node.

First, install socket cluster client in your node.js server:
npm install socketcluster-client
The rest is as simple as the code snippet below:
const socketCluster  = require('socketcluster-client');
const scOptions = {
    hostname: 'localhost',
    port: 3000
};
const scClient = socketCluster.connect(scOptions);
// ...

Also, this will become handy when testing your code. Let me know if it works.

Hi @Hirbod, I think you have some wrong assumption. You can use socketcluster js client in both node and browser. That way you do not have to worry about platform you are running. It can either be browser or node environment.

Thanks everbody, I have sc-client fully working inside nodejs and I can communicate as I wish. It works flawlessly :)
Very happy now! Thanks for your help.

Hey guys,
If you want, you can look through the SC-Client code and see how it works. WebSocket is used client-side by SC-Client to connect so you can just follow that if you want to connect without using SC-Client I guess. Not sure how much help that is but you can do it.

@amin-mir this node js client you have specified can only connect with another socket cluster server regardless of whether that server is on the same domain or on a different domain, what if you want to connect to a completely third party API that provides data via a websocket stream such as the GDAX API, I am assuming it wont work then

@slidenerd Yeah you are right. If you still want to connect to a third party library that uses pure websocket protocol, then you have to use pure websocket client in your SocketCluster application to connect to it. The idea is the same; only do you need to use a different client library.

So a highly related question, lets say I have 4 workers running and I have a separate file lets call it api.js that connects to an external websocket api and receives stream, I want to forward this stream data to the connected clients

If I include the file api.js inside the worker file, obviously it gets called 4 times which is not desirable
One way I can fix the issue is to use the worker id and require("api.js") only in a worker with say id 0
Is there any other way of doing this?

How about using the broker process and forwarding events through that one? You dont need to spawn too many broker processes, so you could effectively reduce those, while keeping the amount of worker processes higher.


Links behave unexpectedly in the Example - ExampleSettings on the readthedocs

this looks like a great package!
I was just looking at the documentation and when you hit "source":

it behaves as expected taking you to the source code... but then when you hit the equivalent "docs" link to go back:

it takes you to the "Usage" section rather than the "Examples" section you came from:

otherwise looks great - can't wait to use it in my next package

@jgunstone Thanks for reporting this. It is indeed a weird behavior. Perhaps that's even a bug in sphinx sphinx.ext.viewcode. I will come back to it soonish.

@jgunstone This bug is fixed with the upcoming release which will be released soonish. You can see the update docs already here.
The issue arose because the same source code was auto-documented multiple times by different doc pages and sphinx.ext.viewcode can only use a single back-reference to the doc pages.

@all-contributors please add @jgunstone for bug


try to make test more robust

Scope & Purpose
This is an attempt to make the "abort all write transactions" test more robust.
It adds an extra delay, which still is not 100% reliable, but should improve things.

[ ] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] Bug-Fix for a released version (did you remember to port this to all relevant release branches?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)
[x] The behavior change can be verified via automatic tests

Testing & Verification
This change is already covered by existing tests, such as scripts/unittest shell_client --cluster true --test shell-transaction.js.
https://<IP_ADDRESS>/view/PR/job/arangodb-matrix-pr/7807/

Tests blue.


If the inline partial is indented, generation fails with "result.split is not a function". }}

false

https://github.com/project-chip/connectedhomeip/blob/f0f5de0d79ae1c51d7fddbf70900ebac0acd899a/src/controller/java/templates/partials/encode_value.zapt#L70-L75

This issue was generated by todo-issue based on a TODO comment in f0f5de0d79ae1c51d7fddbf70900ebac0acd899a.

Recommend converting to a pure comment. This is not a TODO, but rather a warning.


Story Editor: Added List 1 Text Sets

Summary
Adds text sets under List 1 category in this design file:
https://www.figma.com/file/bMhG3KyrJF8vIAODgmbeqT/Design-System?node-id=837%3A3585
User-facing changes
NA
Testing Instructions
Enable the text sets flag in experiments and see the new text sets in the story editor.

Partial for #4078

One more note: List 1 and List 2 are separately in Figma but these would still be one category AFAIK and would be good to keep it in one file under just "list".

@miina

There are 3 lists (the first three) where only the font differs, only one is currently implemented:

Yea so the first three of every set use roboto, then the iOS & Windows system font which we don't currently have access to so I've just implemented the roboto set. (I'm not sure how one even sets a font to the system font in the editor rn)

There is one light line that differs from others (Is this the dotted lines set? Would be good to confirm with Sam if we should skip this for now or opt for using solid lines):

Awesome. yup can't do dotted lines in editor so just used solid lines. will confirm it's cool with sam.
As for lines looking different, I think this is just an issue of rendering subpixel lines in the editor. They're all set to 1px (CSS px) wide in story space, but I think when that gets interpreted to actual screen space it can be less than 1 CSS pixel which the browser doesn't consistently render. This is a good case for building some notion of borders/outlines/stroke in stories that maintain line width regardless of element scale.

The margins between the title and the content differ a bit in some cases, for example:

Yea this is the same issue that was brought up in the other PR. I'll go through these again with whatever approach we settle on here, let me know if you've decided on a certain approach or want to discuss it more.

The + marks are a bit off in terms of vertical centering based on the text, for example:

Yea since these are text and the + is not vertically centered relative to it's bounding box, there's no way to automate centering these and had to do it manually. Can try and tighten these up some more

The - markers look a bit different, e.g. the second last looks thinner compared to the previous ones:

Yeaup. this is that same subpixel issue mentioned above.

Looks great! Just two details found:

In this case the heading is "Regular" font-weight in Figma, it seems to be "light" in the editor. About the checkboxes -- the box that is checked is wider than the others. Also, it's all black shapes instead of what's in Figma but I assume that's a workaround until we have it available?

In this text set, currently, the background is set to solid gray color, however, in Figma, it's black with 0.05 opacity -- we could also do the same here -- use black with 0.05 opacity -- might look better in the preview, too!

Ah good catches. And yea, those are the temporary styles for the checkboxes sam recommended so far

Yea, opacity on the text box fill made the preview look much nicer:


To test host state heartbeat and target work on reset reload

Currently this is related to Andrew work, We need to automate the same and test it.
Expect to come this in the second half of Mar.

Yeah.. I had a discussion on this a bit with Andrew. There are few infra-structure ready for it, hope it should be useful to automate it.. Will keep posted on this..

As discussed in today's scrum, Will be assigning this to Rahul.

Equivalent Development story is https://github.com/openbmc/openbmc/issues/1274

@sivassrr : Here is the progress on this story. There are two development story which need to be taken care for below RR design.

Handle a BMC reset while Chassis is powered on - openbmc/openbmc#1094
: Status : Dev code is merged for this. Manual testing is also completed. Test automation is in progress.

Handle a BMC reset while Host is running - openbmc/openbmc#1274
: Status : Dev code in progress. Current development plan is to get this completed in this sprint.

Do we want to handle it separately, Or do you want to drop the code together.

@sivassrr : Lets this story be only for "Handle a BMC reset while Chassis is powered on".
I have also pushed code for it - https://gerrit.openbmc-project.xyz/#/c/3214/.
Code for other story will come little later.


Extract PropertiesTool (etc.) to a separate file

Extract the PropertiesTool class from the properties.py script (and the same for the other scripts) to a separate file (properties_tool.py?)

working on this in the i37 branch...

oh dear... the tools are broken since #99!

This issue was addressed in issue #102  after properties tool was modified in issue #99

Right. I found the issue and assigned it to myself.
Philosophy discussion:
I think this should have been part of #99, as otherwise #99 breaks the
tool, right? so each time an issue is resolved, the whole project must be
left in a state where it still works.
On Thu, Mar 31, 2016 at 11:34 AM, JIMENOFONSECA<EMAIL_ADDRESS>wrote:

This issue was addressed in issue #102
https://github.com/architecture-building-systems/CEAforArcGIS/issues/102
after properties tool was modified in issue #99
https://github.com/architecture-building-systems/CEAforArcGIS/issues/99
—
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub
https://github.com/architecture-building-systems/CEAforArcGIS/issues/37#issuecomment-203850636

ok. extracted to toolbox.py.


Single capture at regular intervals

What's the best approach to do a single capture at regular intervals.
There is an example for snapshot, but that one closes the device once it finishes storing the image.
In a scenario where we want to regularly capture, sometimes with a couple seconds difference, others with minutes, should the device be closed or kept open?
If open, what is the best approach to ensure getting the latest frame without causing any issues or large memory footprint?
Thanks

Hi @ruidscampos
Thanks for your interest in the project.  So, based on your question, I think the most important thing is to have a long-running process that intermittently open the device, take a pic, then close the device.
You can do this in Go by creating a program that does the following:

Start a loop that runs forever (or until shutdown is signaled)
Use a time.Sleep, with specified interval value to wait
Once time has elapsed, then open the device, take picture, close device.
Then go back at start of loop.

Hope that helps.

Thank you @vladimirvivien for your quick reply and suggestion.
As per my previous reply to another issue, really appreciate all the work you've done with this project.
Regarding the open+close, is this heavy on the processing?
My use case has a dynamic cadence, and in some cases the cadence could be 1 frame every two seconds, or even 1fps, for a short period of time, say 20 seconds, and then be different.
So does it make sense to use a straight capture and supply 1fps, or do the open close?
Ran some tests with v0.0.3 when I was doing some initial testing and with the cameras I'm using, if I select an fps or resolution that is not natively supported (as reported by v4l), the usb bus will consume a lot more bandwidth than if I select an fps and resolution that is natively supported.
Thus my questions, trying to understand constraints and best way to use it for my scenario, given you have a lot more knowledge of it than me.
In regards to time.Sleep, I tend to use a for with a ticker within a select case.
This allows me to have a closing channel and not wait for the sleep to finish when I want to terminate thread.
It also ensures a more accurate interval, if my execution is faster than the interval.
Here's a pseudo-example of how I tend to approach it:

// Start separate thread for regular interval execution
closeChan := chan bool
myTicker := time.NewTicker(Duration.Seconds * 2)
go IntervalExecution()

// Stop the execution
myTicker.Stop()
closeChan <- true

func IntervalExecution() {
for {
// Wait for the first channel to have something
select {
case <- closeChan:
return
case <- myTicker.C:
// Do something here
// Execution here should be faster than ticker duration
}}}

@ruidscampos Thanks for elaborating your scenario.
There are two cases to consider

If this is running on a dedicated machine and no other process will open the camera device, then I don't see the harm in keeping the device open
If, on the other hand, other processes may need the device, then you should close after using.

It sounds like this will be dedicated. So, I think you should be ok with keeping the device open.
Also, the pseudo example looks Ok and should work.  Please let me know how it turns out.

@vladimirvivien thanks.
I'll keep it open and see how it behaves, will let you know of any findings.


Use http instead of https

Their site doesn't yet have a working SSL certificate.

I think it did at one point, but in any case the problem doesn't look like it's getting solved quickly.


Android: Hexa wallet fail to communicate with swan

On Dev app v1.7.0 (293): Hexa wallet fails to communicate with swan when we redirect and login into the app after completing swan authorization.

-Verified this issue on dev app v1.7.5(298)


example.com and www.example.com site are different

Updated by @rahul286
2 cases:
ee site create example.com 		# www should redirect to non-wwww
ee site create www.example.com		# non-www should redirect to wwww
New -www flag:
Possible values

-www=auto
-www=off

If example.com already exist then www.example.com should be allowed to create.
too many values to unpack (expected 2)
O_O[root@example.com:/var/www]# ```

<!---
@huboard:{"order":443.0,"milestone_order":0.1025390625,"custom_state":""}
-->

Lets add a new flag to ee site create command called ---www
It will take values

auto (default value) - current behavior
off - for site only specified domain will be created. This means if example.com created no www.example.com will be creared. Also for www.example.com, no example.com.

@radhe In most general case we are accessed same site with and without www.
For example: https://www.rtcamp.com and https://rtcamp.com are same site.
Can you give us more details why this is needed. So other users also know why we do this in future.

We have 2 different SSL certificates for www.rtcamp.com and rtcamp.com
So for ease of maintenance and to make it future-proof when EE starts managing SSL certificates, such an option will help.
As of we now we have add both SSL under same folder and manually coded different server{..} blocks inside nginx config.
Also default behavior will stay same. We will be adding a flag to stop this behavior.

If user wants to create both version, he needs to run:
ee site create www.example.com --www=off
ee site create example.com --www=off

so does this mean that two sites need to be managed?  that is quite cumbersome

i love your product, it has server pilot beat to the ground on speed as there is no apache, but the non www and www versions is getting me here, i could write a redirect, which is the simplest method, however you know how google feels about redirects :-)

@jbthechamp no, the default action is to have 1 domain which handles both www and example.com, but if you use the --www=off option, then you could literally create two different sites: example.com and www.example.com

Is there a command to enable this new feature for sites already running?  I
tinkered around trying to run site specific command and couldnt seem to
figure it out.  I just updated to new ee version. This is actually awesome
to know.
There should be an - - ssl flag similar to this or an all around command to
enable all versions so one site can be accessed via ssl,  non ssl,  www,
and non www :-).  That would rock for clients that have that type of need
or desire it. .
On Jul 15, 2015 3:45 PM, "William"<EMAIL_ADDRESS>wrote:

@jbthechamp https://github.com/jbthechamp no, the default action is to
have 1 domain which handles both www and example.com, but if you use the
--www=off option, then you could literally create two different sites:
example.com and www.example.com
—
Reply to this email directly or view it on GitHub
https://github.com/rtCamp/easyengine/issues/443#issuecomment-121724609.

Yes you can do ee site update example.com --www=off I assume. But you can also refer to the docs where all the commands are listed: http://docs.rtcamp.com/easyengine/commands/
the --ssl flag is in the works: https://github.com/rtCamp/easyengine/issues/303

Ty ill give it a whirl.  I believe thats what I tried late last night but I
was tired and could have mistyped it.  Thanks for the reference I need to
bookmark via delicious as its a reference i frequent.
On Jul 15, 2015 7:29 PM, "William"<EMAIL_ADDRESS>wrote:

Yes you can do ee site update example.com --www=off I assume. But you can
also refer to the docs where all the commands are listed:
http://docs.rtcamp.com/easyengine/commands/
the --ssl flag is in the works: #303
https://github.com/rtCamp/easyengine/issues/303
—
Reply to this email directly or view it on GitHub
https://github.com/rtCamp/easyengine/issues/443#issuecomment-121775470.

I could be wrong on the ee site update example.com --www=off - I have
never needed this feature and don't use it.
But, NGINX is fairly easy to configure, and EE is set to pull any config
files you add to /var/www/example.com/conf/nginx/. So you could always do
this manually for the time being.
On Wed, Jul 15, 2015 at 5:04 PM, James Barlow<EMAIL_ADDRESS>wrote:

Ty ill give it a whirl. I believe thats what I tried late last night but I
was tired and could have mistyped it. Thanks for the reference I need to
bookmark via delicious as its a reference i frequent.
On Jul 15, 2015 7:29 PM, "William"<EMAIL_ADDRESS>wrote:

Yes you can do ee site update example.com --www=off I assume. But you
can
also refer to the docs where all the commands are listed:
http://docs.rtcamp.com/easyengine/commands/
the --ssl flag is in the works: #303
https://github.com/rtCamp/easyengine/issues/303
—
Reply to this email directly or view it on GitHub
<https://github.com/rtCamp/easyengine/issues/443#issuecomment-121775470
.

—
Reply to this email directly or view it on GitHub
https://github.com/rtCamp/easyengine/issues/443#issuecomment-121782501.

@rahul286 How about a more flags and a more modular approach?
ee site create domain.com
--protocol= < http | https >  #not required (defaults to http)
--port = < 80 | ... >  #not required (defaults to 80 for http and 443 for https)
--subdomain= < www | any-other-subdomain | ... >  #not required
--subdirectory= < subdirectoryname > #not required
--accessible-by= < domain | subdomain | domain-subdomain | basic-auth | proxy > #required if domain.com is specified with a subdomain

Actually www and non-www subdomain case is different.
Though technically www is just a subdomain, people expect it to be mapped to non-www version or other way round.

@rahul286 for mapping see suggested --accessible-by flag in my above

I think we need to handle first:
Map www.domain.com => domain.com  When user runs:
ee site create domain.com

And map domain.com => www.domain.com  When user runs:
ee site create www.domain.com

So if you want www visible, specify www in domain name.
In both cases, there will be 2 nginx server block - one for www and one for non-www.
Only case I see when people do something with other block is setting up separate SSL.
e.g. https://www.domain.com/ to https://domain.com/ redirect (or vice-versa)


Writing function and test for coordinate_descent

@andyzhangstat please correct the example in the function, the inputs are not updated.


list logging for performance + auto report save

logging is done by append on a list rather than np.concatenate which was O(N) and caused massive slowdown during the simulation. `append is amortized O(1), which yield much faster simulations.

to manage the array logging, I added a typecheck when _appendData and convert the array to a list with np.tolist()

added an autosave on the Stats.report method

The GPU logging doesnt work because np.tolist() creates memory errors that freeze the computer.

ready for review @JLBegin


Recursive Folder Download

When I press Download a Folder it only downloads the folder itself. It would be a lot more faster and intuitive if this download the Folder recursivly.

Id like to get this in also.

Indeed. When I do download a folder, it cuts off the first letter of the name of any sub-files or sub-directories and places them in the root. So if I have
images
    ~ hello
      ~ bluebird.png

and download the images directory, I end up with
~ images
~ ello
~ luebird.png

Folder download is currently broken.... See #115


Bad state: Unexpected diagnostics: sky_engine\lib\ui\channel_buffers.dart - This requires the 'non-nullable' language feature to be enabled

Steps to Reproduce

I created a new code generation project, following different resources

https://www.youtube.com/watch?v=mYDFOdl-aWM&list=WL&index=17&t=2149s
https://www.youtube.com/watch?v=H4HWB2Pmgcw
https://medium.com/flutter-community/part-1-code-generation-in-dart-the-basics-3127f4c842cc

Create a flutter app to test code generation
Run flutter pub run build_runner build

Expected results:
Since no annotation is present inside the flutter app (only original main.dart), the generation process should complete without any code generated and without any failure.
Actual results:
The build process is unsuccessful and fails with the following result (from flutter pub run build_runner build --verbose):
[INFO] Generating build script...
[INFO] Generating build script completed, took 466ms

[INFO] Initializing inputs
[INFO] Reading cached asset graph...
[INFO] Reading cached asset graph completed, took 71ms

[INFO] Checking for updates since last build...
[INFO] Checking for updates since last build completed, took 697ms

[WARNING] Invalidating asset graph due to build script update!
[INFO] Cleaning up outputs from previous builds....
[INFO] Cleaning up outputs from previous builds. completed, took 3ms

[INFO] Generating build script...
[INFO] Generating build script completed, took 99ms

[INFO] Creating build script snapshot......
[INFO] Creating build script snapshot... completed, took 12.9s

[INFO] Initializing inputs
[INFO] Building new asset graph...
[INFO] Building new asset graph completed, took 1.3s

[INFO] Checking for unexpected pre-existing outputs....
[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms

[INFO] Running build...
[INFO] Generating SDK summary...
[SEVERE] repo_case_generator:repo_case on lib/main.dart:

Bad state: Unexpected diagnostics:
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:119:41 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:152:17 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:88:62 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:153:38 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:186:51 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:133:32 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:154:25 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:18:17 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:64:4 - This requires the 'non-nullable'
language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:168:32 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:47:14 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:159:38 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:132:37 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:118:48 - This requires the 'non-nullable' language feature to be enabled.
C:\Users\Sandro Maglione\flutter\flutter\bin\cache\pkg\sky_engine\lib\ui\channel_buffers.dart:19:11 - This requires the 'non-nullable' language feature to be enabled.
[INFO] Running build completed, took 1.4s

[INFO] Caching finalized dependency graph...
[INFO] Caching finalized dependency graph completed, took 48ms

[SEVERE] Failed after 1.5s
pub finished with exit code 1

The flutter app contains only the default main.dart created after running flutter create.

build_runner: ^1.10.0
analyzer: ^0.39.16
build: ">=0.12.6 <2.0.0"
sdk: ">=2.6.0 <3.0.0"

[√] Flutter (Channel stable, 1.20.0, on Microsoft Windows [Version 10.0.18362.959], locale en-US)
    • Flutter version 1.20.0 at C:\Users\Sandro Maglione\flutter\flutter
    • Framework revision 840c9205b3 (2 days ago), 2020-08-04 20:55:12 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\Sandro Maglione\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[!] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.47.3)
    • VS Code at C:\Users\Sandro Maglione\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.13.2

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

May be related to #56779, #41820

I'm having the same issue. It is due to the inclusion of the non-nullable Dart 2.9 feature in Flutter 1.20 stable channel.
I tried updating my pubspec.yaml with the lines
environment:
  sdk: ">=2.9.0 <3.0.0"
  flutter: ^1.20.0

to try to force Flutter to use the most recent versions of both tools, but it doesn't seem to be working even if my flutter doctor shows as having the newest versions, as shown bellow.
[√] Flutter (Channel stable, 1.20.0, on Microsoft Windows [versÃ£o 10.0.19041.388], locale pt-BR)
    • Flutter version 1.20.0 at V:\flutter
    • Framework revision 840c9205b3 (2 days ago), 2020-08-04 20:55:12 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\caios\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 48.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.47.3)
    • VS Code at C:\Users\caios\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.13.0

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

If there is no guide as to migrate the code or how to activate non-nullable support, I think the way is to downgrade Flutter as of now.

Hey, I'm back with a better answer. After the last comment I kept searching.
According to issues #62996 and #62240 the problem lies in the 'analyzer' package version '0.39.15' and '0.39.16'. Adding the override bellow to pubspec seems to solve the issue.
dependency_overrides:
  analyzer: '0.39.14'

I tried your solution.
It worked on one of my project, in which I am using code generation for third party packages.
However, the solution does not work on my own code generator project. The same error occurs.
I tried to upgrade build_runner to 1.10.1, but this version requires sdk >=2.10.0-0.0. In fact, in the pubspec.yaml of build runner is stated:
environment:
  # The min sdk can be reduced once analyzer releases a fix for
  # https://github.com/dart-lang/build/issues/2763
  sdk: ">=2.10.0-0.0 <3.0.0"

#2763 from dart-lang.

I see. Maybe downgrading Flutter, Dart and packages versions of your generator project is your best option now until they fix the analyzer.

Hi @SandroMaglione
I see there's an open issue addressing the case you described. https://github.com/flutter/flutter/issues/62240
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you

Upgrading the sdk version to a min of 2.9 also solved the issue for me.
environment:
  sdk: ">=2.9.0 <3.0.0"


On Visual Formalisms by David Harel

https://dl.acm.org/doi/abs/10.1145/42411.42414

Other higraph papers

Algorithmics of Higraphs
Measuring the Complexity of a Higraph-based System Model: Formalism and Metrics
Using HiGraph to define a Formal Integrated System Modeling Framework that ensures Complete System Consistency
System Modeling and Traceability Applications of the Higraph Formalism
Zooming-out on Higraph-based diagrams: Syntactic and Semantic Issues


Start/stop charging buttons andset charging speed.

Enhancement:
COuld we have a control to start/stop charging and also to set the AC charging speed - or am I missing something?

These options are already available! :) see the integration page in Homeassistant.

There is an option to toggle the charging speed, but I can’t see a way to set it to one or the other.


build(codepush) : codepush ci scripts + sentry handling

This PR resolves PHIRE-157
Description

Part 3 of 3 of codepush integration: https://www.notion.so/Adopt-CodePush-Over-the-air-updates-in-Eigen-cb95950057e34f259c801a3359cefe7c
Depends on https://github.com/artsy/eigen/pull/9203 which should be merged first. ✅
Adds ci jobs:

check if native code has changed in prs, if it has and the native code version has not been incremented fail the PR
on merge to main if a native code change has happened deploy a new beta
on merge to main if a native code change hasn't happened (just js) deploy to codepush staging

Follow-ups

Our scripts folder, ci config, and fastlane scripts are getting pretty messy and unwieldy, time for some love

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Codepush sentry integration, deployment scripts + ci config - Brian

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (Codepush sentry integration, deployment scripts + ci config - Brian)

  Generated by :no_entry_sign: dangerJS against 3c36aad634ba577cc2fc9bac0d6d1344e9b4a3af

sentry still not quite working as I expect, not matching releases properly, will look into tmrw: https://artsynet.sentry.io/issues/4439709125/?project=5867225&query=is%3Aunresolved&referrer=issue-stream&stream_index=14

sentry stack traces still not cooperating with codepush, opened issue here: https://github.com/getsentry/sentry-react-native/issues/3279

Sentry working, silly mistake on my part: https://github.com/getsentry/sentry-react-native/issues/3279#issuecomment-1721180563
Android working but we need to have a separate code push app as per the docs: https://learn.microsoft.com/en-us/appcenter/distribution/codepush/cli
Ready for review finally!

🔥🔥🔥🔥 so excited for this one!
Looks great! Added a question around where we get this hashes file from, and another one:
(non-blocking): Will integrating codepush affect the ability for OS contributors to run the app?

good point, I'll pull it down and check!

We can merge I guess and we can fix the OSS on another PR 👏

We can merge I guess and we can fix the OSS on another PR 👏

I pulled it down and it seems to work fine!


VM: PCIe addressing take two

This PR fixes an issue introduced in https://github.com/lxc/lxd/pull/7185 that caused PCIe addressing conflicts due to qemu 9p devices assigning their own PCIe addresses that conflicted with the statically assigned NIC device addresses. This PR also now statically assigns 9p disk devices a PCIe address in a separate range to NICs, which will also be separate independent of the order the devices are configured in LXD config.
Fixes #7175

I tested this by adding 8 ethernet devices and a 9p share in addition to the normal 9p config drive.
This was the result:
Note: I also tried remove the addr setting in qemu and using a single chassis per device type and then using the slot number derived from nicIndex or diskIndex, which worked, except that it caused the consistent device names inside the VM for the ethernet devices to change to:
root@v1:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:16:3e:85:e1:ec brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp5s0
       valid_lft 3100sec preferred_lft 3100sec
    inet6 fd42:be3f:a937:9505:216:3eff:fe85:e1ec/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 3102sec preferred_lft 3102sec
    inet6 fe80::216:3eff:fe85:e1ec/64 scope link
       valid_lft forever preferred_lft forever
3: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:b6:bf:c6 brd ff:ff:ff:ff:ff:ff
4: enp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:0c:5b:9d brd ff:ff:ff:ff:ff:ff
5: enp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:94:a9:ff brd ff:ff:ff:ff:ff:ff
6: enp9s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:85:dc:d6 brd ff:ff:ff:ff:ff:ff
7: ens5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:72:e8:f5 brd ff:ff:ff:ff:ff:ff
8: ens6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:9a:0b:5e brd ff:ff:ff:ff:ff:ff
9: ens7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:68:aa:70 brd ff:ff:ff:ff:ff:ff

The last three devices changed their prefixes to ensX which according to https://en.wikipedia.org/wiki/Consistent_Network_Device_Naming means their slot numbers where considered hot pluggable.
So I reverted back to using a different chassis number for each device, and effectively making each device slot 0 in that chassis. Thus restoring the original naming scheme.
root@v1:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:16:3e:85:e1:ec brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp5s0
       valid_lft 3582sec preferred_lft 3582sec
    inet6 fd42:be3f:a937:9505:216:3eff:fe85:e1ec/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 3583sec preferred_lft 3583sec
    inet6 fe80::216:3eff:fe85:e1ec/64 scope link
       valid_lft forever preferred_lft forever
3: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:b6:bf:c6 brd ff:ff:ff:ff:ff:ff
4: enp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:0c:5b:9d brd ff:ff:ff:ff:ff:ff
5: enp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:94:a9:ff brd ff:ff:ff:ff:ff:ff
6: enp9s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:85:dc:d6 brd ff:ff:ff:ff:ff:ff
7: enp10s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:72:e8:f5 brd ff:ff:ff:ff:ff:ff
8: enp11s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:9a:0b:5e brd ff:ff:ff:ff:ff:ff
9: enp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:68:aa:70 brd ff:ff:ff:ff:ff:ff

root@v1:~# lspci  -tvvvvm
-[0000:00]-+-00.0  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
           +-01.0  Red Hat, Inc. Virtio console
           +-02.0-[01]----00.0  Red Hat, Inc. Virtio SCSI
           +-02.1-[02]----00.0  Red Hat, Inc. Virtio memory balloon
           +-02.2-[03]----00.0  Red Hat, Inc. Virtio RNG
           +-02.3-[04]----00.0  Red Hat, Inc. Device 1053
           +-03.0  Red Hat, Inc. Virtio filesystem
           +-03.1  Red Hat, Inc. Virtio filesystem
           +-04.0-[05]----00.0  Red Hat, Inc. Virtio network device
           +-04.1-[06]----00.0  Red Hat, Inc. Virtio network device
           +-04.2-[07]----00.0  Red Hat, Inc. Virtio network device
           +-04.3-[08]----00.0  Red Hat, Inc. Virtio network device
           +-04.4-[09]----00.0  Red Hat, Inc. Virtio network device
           +-04.5-[0a]----00.0  Red Hat, Inc. Virtio network device
           +-04.6-[0b]----00.0  Red Hat, Inc. Virtio network device
           +-04.7-[0c]----00.0  Red Hat, Inc. Virtio network device
           +-1f.0  Intel Corporation 82801IB (ICH9) LPC Interface Controller
           +-1f.2  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
           \-1f.3  Intel Corporation 82801I (ICH9 Family) SMBus Controller

dmesg
...
[    0.889725] pciehp 0000:00:02.0:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.891902] pciehp 0000:00:02.1:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.894122] pciehp 0000:00:02.2:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.896296] pciehp 0000:00:02.3:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.898454] pciehp 0000:00:04.0:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.900628] pciehp 0000:00:04.1:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.902811] pciehp 0000:00:04.2:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.905037] pciehp 0000:00:04.3:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.907209] pciehp 0000:00:04.4:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.909426] pciehp 0000:00:04.5:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.911611] pciehp 0000:00:04.6:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
[    0.914014] pciehp 0000:00:04.7:pcie004: Slot #0 AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Interlock+ NoCompl- LLActRep-
...

Thank you!


docs(api.md): clarify on HTTP error responses

Is this closing a bug?

Is this closing a bug?

It does not.


Failed to install the app. Please accept all necessary SDK licenses using SDK Manager: "$ANDROID_HOME/tools/bin/sdkmanager --licenses". Run CLI with --verbose

React Native version:

Steps To Reproduce

Describe what you expected to happen:
Snack, code example, screenshot, or link to a repository:

@wojtek2313 This doesn't seem to be a bug with RN. Please ask this over at StackOverflow.


fix : fix frozen camera in LivePreview

@samtstern This should fix #720, I tested it on my local devices and the LivePreview activity in Kotlin works without issues now!

@samtstern Works well now, apparently the kotlinized VisionProcessorBase was the culprit here for frozen preview.
Fixing that fixed the issue for all the LivePreview demo :)
P.S. I went ahead and made some fixes in the code to follow Kotlin style guidelines

@the-dagger
./build.sh: line 34: /Users/harshitdwivedi/Library/Android/sdk/tools/bin/sdkmanager: No such file or directory

Build failure implies some of your local setup snuck into this PR.

Accidental commit 🤦♂
I edited that file as I was running it locally to ensure that the travis test will pass.
Looks like being extra careful can bite you in the back too! 😆

@the-dagger thanks for solving this one!

Anytime!


PB-4786: Add backup size check in ValidateBackup()

What this PR does / why we need it:
In the past we have seen customer issues like PB-4193 where size was coming up as blank to avoid such issues in the feature adding the below check:

[x] Add backup size check in ValidateBackup()

Dashboard link:
https://aetos.pwx.purestorage.com/resultSet/testSetID/459970
https://aetos.pwx.purestorage.com/resultSet/testSetID/460006
https://aetos.pwx.purestorage.com/resultSet/testSetID/461405 (1 failure due to PWX-31227)
https://aetos.pwx.purestorage.com/resultSet/testSetID/463127
https://aetos.pwx.purestorage.com/resultSet/testSetID/466635  (Latest Single Testcase Run)
https://aetos.pwx.purestorage.com/resultSet/testSetID/466652  (Latest full run)
Which issue(s) this PR fixes (optional)
Closes #PB-4786
Special notes for your reviewer:

Run after addressing @sn-px's comments https://aetos.pwx.purestorage.com/resultSet/testSetID/463127

Latest run with just BasicBackupCreation:  https://aetos.pwx.purestorage.com/resultSet/testSetID/466635

Latest full run with @mkoppal-px 's comment fix: https://aetos.pwx.purestorage.com/resultSet/testSetID/466652


Line number anonymization in snapshots?

Does line number anonymization help minimize snapshot changes in PRs?
Example:
---
source: crates/ruff/src/rules/flake8_pytest_style/mod.rs
---
PT012.py:L:L: PT012 `pytest.raises()` block should contain a single simple statement
   |
LL |   def test_error_multiple_statements():
LL |       with pytest.raises(AttributeError):
   |  _____^
LL | |         len([])
LL | |         [].size
   | |_______________^ PT012
   |

I like the idea personally. Curious for others' thoughts!

How I got the snapshot above:
diff --git a/crates/ruff/src/message/diff.rs b/crates/ruff/src/message/diff.rs
index c665578c2..1dba0222d 100644
--- a/crates/ruff/src/message/diff.rs
+++ b/crates/ruff/src/message/diff.rs
@@ -90,6 +90,10 @@ impl Display for Diff<'_> {
                     let old_index = change.old_index().map(OneIndexed::from_zero_indexed);
                     let new_index = change.new_index().map(OneIndexed::from_zero_indexed);

+                    #[cfg(test)]
+                    write!(f, "L L |{}", line_style.apply_to(sign).bold())?;
+
+                    #[cfg(not(test))]
                     write!(
                         f,
                         "{} {} |{}",
diff --git a/crates/ruff/src/message/text.rs b/crates/ruff/src/message/text.rs
index ee27ae28f..2acfa7314 100644
--- a/crates/ruff/src/message/text.rs
+++ b/crates/ruff/src/message/text.rs
@@ -101,6 +101,18 @@ impl Emitter for TextEmitter {
                 start_location
             };

+            #[cfg(test)]
+            writeln!(
+                writer,
+                "L{sep}L{sep} {code_and_body}",
+                sep = ":".cyan(),
+                code_and_body = RuleCodeAndBody {
+                    message,
+                    show_fix_status: self.flags.intersects(EmitterFlags::SHOW_FIX_STATUS)
+                }
+            )?;
+
+            #[cfg(not(test))]
             writeln!(
                 writer,
                 "{row}{sep}{col}{sep} {code_and_body}",
@@ -284,6 +296,8 @@ impl Display for MessageCodeFrame<'_> {
                 color: false,
                 #[cfg(not(test))]
                 color: colored::control::SHOULD_COLORIZE.should_colorize(),
+                #[cfg(test)]
+                anonymized_line_numbers: true,
                 ..FormatOptions::default()
             },
         };

I really like the idea! Most of the times I try to add the test cases at the end of the file to avoid confusing diffs unless the test case belongs to a "group" of related cases.
I think the row:col pair in the diagnostic message should be present. Also, instead of anonymous line numbers we could just eliminate them? Not sure if they're actually useful.
Any other thoughts are appreciated!

@dhruvmanila Thanks for the comment!

I think the row:col pair in the diagnostic message should be present

to make sure the error location is correct?

Also, instead of anonymous line numbers we could just eliminate them? Not sure if they're actually useful.

We could if the annotate-snippets crate supports this :)

I generally like the idea because it makes reviewing changes easier but there are a few things that are unclear to me / need to be tested differently:

Our infrastructure for computing line indices, line numbers, relevant diff windows, and printing the diagnostics is mainly tested with the rule tests. Removing/Anonymizing the line numbers from the snapshots would reduce the coverage to like 2 tests...
One of my long-term quests is to add support for multi-frame diagnostics. Meaning you can add multiple code frames to a single diagnostic. Having line numbers can then be useful to understand the different frames (that could even be from different files)

What I understand is that the main problem is that the line numbers change every time we add a new test case to a file. Would it be possible to better isolate individual tests cases instead?

I also like the idea but I have a similar reaction to Micha. Separately, the line numbers make for bad diffs on-change but they actually are useful when interpreting the snapshot outside of a code review.

Would it be possible to better isolate individual tests cases instead?

This seems like it would help a lot, but is also challenging to achieve.

I've also thought about this a bit more and I think we probably won't want to make this change. Retaining test coverage and ease of interpreting snapshots seems important. I've opened a discussion to talk about this problem in general: https://github.com/astral-sh/ruff/discussions/6129
I hope you don't mind if I close this so we can keep the issue tracker actionable. Thanks for starting this discussion!


New Firefox bug

From<EMAIL_ADDRESS>on October 16, 2012 15:23:20
What steps will reproduce the problem? 1. Use my data in Firefox
2. use toObjects
My new data looks like this.
resNum,DataCol,ColorCol
16S:(1-8),4,purple
16S:(9-25);16S:(913-920),1,red
I use toObjects. This runs perfectly fine on my website and on the test website in Chrome. It fails in Firefox. Firefox produces an all empty array. I need all these punctuation marks.
Actually, I tried something simpler
w,r,t
2,4,purple
4,1,red
This isn't working in Firefox either. It's failing in 0.64 and it fails on the Basic Usage Demo.
OK, I did some more testing for you. Firefox is requiring all data to be in quotes.
toy,test,kelp
1,2,3
4,5,6
will not work, but
"toy","test","kelp"
"1","2","3"
"4","5","6"
will work
Quotes should be optional. I only put quotes around my data if the data contains a comma.
Original issue: http://code.google.com/p/jquery-csv/issues/detail?id=14

From<EMAIL_ADDRESS>on October 16, 2012 16:05:26
This is also an issue with IE (tested in IE9 on win7), like the above adding quotes fixes the issue.

From<EMAIL_ADDRESS>on October 16, 2012 20:52:06
Damn... I thought we had this bug nailed already. You can see the details in bug 5 .
Chrome marks empty values as undefined while FireFox and IE use an empty string instead. So, both need to be tested for.
I may have changed something along the way that broke it again. Let me see if I can back-track to see if the previous fix was implemented properly and passes all the tests.
Give me a little time to get another test collection up and running the full gamut of RFC 4801 rules.

From Thanpolas on October 24, 2012 05:27:59
+1 I have the same issue, glad you are on it Evan.
I'd fix it but i am not sure what exceptional cases you are handling by examining the first match (m1) on the replace callback function...
It looks like m2 is what we need in both cases, why not use that?

From<EMAIL_ADDRESS>on October 24, 2012 09:30:28
@-Thanpolas According to the tests, m2 should be working fine in its current state. As a temporary stopgap, I'll try releasing a fix to handle it the same way as m1 was patched previouslyI get the feeling that it will still fail under some circumstances.
 Long story short, just simply evaluating a match (ie using an 'if statement') mutates it somehow. As soon as I can isolate it completely, I'll be filing a bug upstream for their devs.
It is literally not possible to get all test cases to bass in both Chrome and Firefox (believe me, I've tried). Not without adding  browser detection kludge. For the sake of quality in the long term I'd rather not go that route.
To avoid future problems and provide a parser that is more stable and easier to fine-tune I sill be ditching the monolithic regex match and replacing it with a FSM much like the one used in the line splitter.
Either way, I'll let you know when I have some code available to test.

From<EMAIL_ADDRESS>on October 24, 2012 19:22:37
OK, screw using a monolithic regex for parsing CSV entries. Amazingly, I was able to roll out a new ND-FSM (Non-Deterministic Finite State Machine) entry parser with a quickness.
No more browser inconsistency pain...
It doesn't provide support for custom delimiter/separator characters yet and custom escape char support is no longer an option (it was kinda pointless to begin with). As soon as I have them working again, I'll drop the 0.65 release.
In the mean time, if you aren't using non-default delimiter/separator chars, feel free to pull the latest from the repository.
Note: The online testing and examples run the source directly from the repository, so that's another good place you can try it out.
Status: Fixed

From<EMAIL_ADDRESS>on October 26, 2012 22:40:22
Owner<EMAIL_ADDRESS>Labels: -Priority-Medium Priority-Critical

From<EMAIL_ADDRESS>on November 01, 2012 21:14:27
This issue was closed by revision df79574a5f6d .


Add a CLI flag for disabling memory leak detection

It may be useful to conditionally disabled or enable memory leak detection when running a command like ember test on the command line. In particular this will be useful for setting up CI, where users may wish to only run memory leak detection as part of a certain CI command but not every time their tests are run.
Unsure if memory leak detection should be opt-in (--detect-memory-leaks=true) or opt-out (--disable-memory-leak-detection=true) 🤔

A few thoughts:

It might make more sense to use an environment variable rather than command-line switch. I think it would be a little easier to read from the addon, and in my experience friendlier to the scenario you describe where maybe it might be configured in CI -- then I can just set the env var rather than having to add a whole extra script to package.json and/or extra command-line arguments to my CI config file's invocation of ember-cli.
I'd definitely go for opt-in. This is a pretty significant change to the runtime test environment, and not something I'd really want to "accidentally" happen. I'm thinking of various test frameworks that have support for code coverage like jest -- none of them run coverage by default, it's something you opt in to. In this case you've arguably already opted in by installing the addon in the first place, but especially with large teams, one person opting in so they can run some specific tests probably shouldn't opt everyone in all cases in.

Also, since you can enable/disable it via the config, I would assume the cli option/env var would override that, so teams could really set it up however they want -- on by default, and the env var can turn it off, or off by default and the env var can turn it on. So maybe it's more of a setup-time config question of whether consumers set it to enabled/disabled by default in config/environment.js, knowing that they can toggle it either way at "runtime" using an environment variable.

@bendemboski Thanks for your thoughts. Env var seems like the way to go.


Can you update the jest version to 26.0?

Describe the bug
mocks doesn't work under jest 25.5, version 26 fixes this problem.
So Can you update the jest version to 26.0?
(Write your answer here.)
Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)
Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Its in progress already. There are a couple of PRs for it and its on the roadmap

Thank you very much since I find that you have not released a new version for 2 months.


List components for QueryEntityError::QueryDoesNotMatch

Objective
Make it easier to debug why an entity doesn't match a query.
Solution
List the entities components in QueryEntityError::QueryDoesNotMatch's message, e.g. The query does not match the entity 0v1, which has components foo::Bar, foo::Baz.
This covers most cases as expected components are typically known and filtering for change detection is rare when assessing a query by entity id.
Testing
Added a test confirming the new message matches the entity's components.
Migration Guide

QueryEntityError now has a lifetime. Convert it to a custom error if you need to store it.

Thank you to everyone involved with the authoring or reviewing of this PR! This work is relatively important and needs release notes! Head over to https://github.com/bevyengine/bevy-website/issues/1697 if you'd like to help out.


Is there good way to get current focused window info in lua script?

Hi, I'm using autokey to achieve macOS keymap under Linux, take "cmd + c" as example, I need to map it into "ctrl + c" in most programs, but in terminal I may need to map it into "ctrl + shift + c", the script for autokey will be like:
window_class = window.get_active_class()

if window_class in ['xfce4-terminal.Xfce4-terminal', 'tilix.Tilix']:
    keyboard.send_keys('<ctrl>+<shift>+c')
elif window_class == 'Atom':
    keyboard.send_keys('<ctrl>+<insert>')
else:
    keyboard.send_keys('<ctrl>+c')

Currently the only way I could find is use os.execute to run some external program similar to xprop to get window info, but that may be low efficient, so is there any better way to achieve this? Thanks.

This is difficult to support as there currently isn't any widely deployed standard for these sorts of queries, if you run sway you can use swaymsg -t get_tree | jq and look for an entry with {"focused: true}.
If you run a different WM/DE then you need to refer to their respective documentation, it looks like you already have a lead here with the window.get_active_class() function, you should probably investigate to see how that function works.
PS: Is this X11 or Wayland? On X11 this should be easier.

I'm using Awesome WM and autokey, both only work in X11, actually I'm looking for replacement under wayland for future. Thanks for your advice and I will try when migrating :)


github_repo_open_issues and github_repo_pull_request_count separately

we needed github_repo_open_issues and github_repo_pull_request_count separately, so I added it
(GitHub REST API returns all open issues + pull requests count, not issues only, so we have to use the pull requests API to get the PR count and then subtract it to get issues)
please consider merging it upstream in case other people need it
if it's accepted, we can use infinityworks' version rather than maintaining our own
thanks

I will have a look at this at some point in the next 12 hours and confirm before merging

looks like it was a requested feature already:
https://github.com/infinityworks/github-exporter/issues/12

LGTM - @iamtgray ?

Thank you!


Consider updating SA1308 (VariableNamesMustNotBePrefixed) to handle 't_'

Currently the prefix t_ (used by some projects for thread-local variables) is not treated as a "special prefix" for rule SA1308. It is instead reported as SA1310 (FieldNamesMustNotContainUnderscore). I believe we should update rule SA1308 to handle this special case in addition to its current treatment of m_ and s_.

I agree, t_ should trigger SA1308, not SA1310.


Establish a pipeline for feeding ledger ops data to P&T analysis

Required for https://github.com/input-output-hk/ouroboros-consensus/issues/223

[ ] Generate input data for the benchmark-ledger-ops analysis.
[ ] Agree on the output format.
[ ] Have the benchmark-ledger-ops analysis to output data in said format.
[ ] Feed the output data to the P&T toolchain for variance analysis.

Next steps, as discussed with @mgmeier.

[ ] Consider adding deepseq to this line.
[ ] DataPoint should be output as JSON.
[ ]DataPoint should be imported as a library so that the P&T tooling can use it.
[ ] We will use a synthesized chain as input data.
[ ] We need to annotate the output file with metadata:

RTS flags used.
Compiler version.
Package versions (cardano-ledger and ouroboros-consensus) or the git commit hash that correspond to the db-analyser version built.

[ ] We need to set the same RTS flags as cardano-node (to constraint resources in the same way).

We'll pass the result of running the ledger-ops analysis to @mgmeier for variance analysis. We'll output a JSON file in the following format:
{ metadata: { ... }
, datapoints: [ ... ]
}

We do not want to add deepseq to this line because:

it would inflate the measured time because we would be traversing the whole structure (r in the snippet above), and crucially, we do not use deepseq in our actual code.
our types should be fully strict (with the exception of fingertree-like internal lazyness) such that deepseq would be a no-op (sematically, not performance-wise).

As discussed with @mgmeier, the variance analysis shows that db-analyser gives reproducible results. A PR with further improvements to beacon will be submitted by @mgmeier.


EPSG:3763 not supported

We've git pull'ed MapLoom and now it stopped working properly, returning the error
----[ addLayer, looking up projection:  EPSG:3763
MapLoom-1.2.0.js:165773 ----[ projection not found:  EPSG:3763
MapLoom-1.2.0.js:165785====[ NOTE: proj file is downloaded and added to proj4 but we need to either do syncronous call or make sure it is resolved before we continue on or return a promis and make sure all invokaction of addLayer user the promise properly  EPSG:3763

Is there something I can do to solve this?
Thanks,
David

Now it is working correctly in Firefox.
Thanks!


Completely overhaul socket and incoming command handling

See if we could pull stuff from there back into this to clean up how it works, ensure we prevent races, etc.

I've started this with<PHONE_NUMBER>68f88f010590621a82a959f33cdc3b and using my updated, and I think cleaner, socker.go code from gircbnc. From the looks of how it's all hanging together internally, we probably are somewhat vulnerable to races and all that fun stuff as a result of how we process commands and incoming lines. Migrating the socketreactor.go stuff over and changing the commands to use that method instead should clean that up and let that work quite a bit more nicely.

I am deep into this. It's essentially a very big rewrite of how incoming commands get handled and replies get dispatched to users.

Which should be good enough for now. We don't need 100% protection against races yet, we can deal with that later when we make all this use a single main ircd thread.

I consider this done