Add Super Admin functions to Admin area

Currently this is not part of DMPonline UI. Need to add something like DMPTool "DMP Administration" tab to Admin area.
Super Admins need to be able to:

add organizations
assign privileges to other users
copy and edit funder templates; full view of Org templates
change plan visibility (remove public DMPs) - triggers email
administer themes (update name, add new); view of guidance by theme
administer languages (define language options for an installation); possibly remove language selection?
...

UX wireframe @rhu001 : http://h90c3m.axshare.com/#g=1&p=dmp_templates__admin_view_
Pivotal ticket: https://www.pivotaltracker.com/story/show/121675903
Screenshots of DMPTool DMP admin UI

Adding a new Institution (note: revise fields, not all of these are necessary)

reevaluate this global issue post MVP and identify any remaining work. many things have already been completed.

just making some notes here for the languages screen: We should generate the list of languages based on the translation folders present in config/locale so that an admin can simply enable/disable them.
|  Language     |  abbreviation  | enabled  | default  |
---------------------------------------------------
|  English (GB) |   en_GB           |   true       |    true    |
|  Japanese      |   ja                   |  false      |    false   |

Where enabled means that the app.po is available and the language appears in the languages table. Disabling would remove the entry from the table (which is what drives the language selection box) but not remove the app.po.
We could also add a button to 'Add a language' that could kick off the gettext:add_language[xx] rake task which will generate the app.po file. We should also include a link to an ISO-639 language code reference so that admins use a valid code

@sjDCC - reviewing this catch-all Super Admin issue and the only thing we didn't address yet is administering languages. do we still want/need to be able to do this? I think it could just be something we ask devs to configure for each installation. I don't necessarily need to add/remove languages myself.


"Open file..." should remember previous directory

Using "Open file..." (Cmd-O on macOS), qStudio always seems to start at the user's home directory.
This is reasonable default behavior when the program is first opened, but highly annoying when opening another file that's nearby, but buried multiple directories down.
Two suggestions:

qStudio could return to the directory that contained the previous file on the next "Open file..."

qStudio could use the native file picker for the underlying operating system. This would allow straightforward, familiar navigation, and allow people to take advantage of any "file picker enhancements" they have installed.

Thanks

Strange, the logic to use last folder has been there for a long time:
https://github.com/timeseries/qstudio/blob/master/tscore/src/main/java/com/timestored/docs/DocumentActions.java#L418
I tested just now on windows and ubuntu, both it worked as expected.
Please can you double check?

I can confirm that 3.07 does return to the last opened directory, as desired. I don't know why my earlier test didn't show that.
I still would be delighted to have a native file picker, even if qStudio needed to support multiple - different one for one platform. (But I ain't gonna write the code... :-) Thanks again


Use serde_url_params to write URLs with query params

Currently building the URL manually which is unsightly and not scalable.  We can use https://docs.rs/serde_url_params/latest/serde_url_params/ to easily serialize the struct.  The flatten option is really nice too.

It is such a simple task I may do it myself, as I can handle parsing vectors my own way.


homebridge-playstation-login command not sending sign in link.

Describe The Bug:

Homebridge WebUI Terminal setup using homebridge-playstation-login. Results no link just the message:
Result: Did not authenticate to any consoles.
Ubuntu 20.04 WebUi Terminal does not allow NPM package installs or sudo use either.
Could be an operator error but:
Tried this tutorial but to no avail since on Ubuntu.
https://github.com/dhleong/playactor/discussions/22
Ubuntu 20.04 apt installed method does not allow
NPM installing nor Sudo commands via webUI with Ubuntu.
To Reproduce:

Ubuntu 20.04 (APT install https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Debian-or-Ubuntu-Linux )
Install Homebridge
Install homebridge-playstaion
run:  homebridge-playstation-login (from web UI)
result:  "Did not authenticate to any consoles."
Expected behavior:

Link to pair PlayStation account sign in, but does not link.  WebUI gives results with:
Did not authenticate to any consoles.
Logs:
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:

        "pollInterval": 2000,
        "platform": "playstation"
    },

Screenshots:

Environment:

Plugin Version:  v1.4.1
Homebridge Version:   v1.4.1
Node.js Version:   v16.15.1
NPM Version:
Operating System:  Ubuntu 20.04

Notes: Installed on top of ubuntu 20.04.

I have the same issue on my raspberry pi 4.

i am having the same exact issue listed above. ver-batim. for months!!! i cant figure it out!

i got the same issue

same exact issue

Hello; this looks like an issue in discovering the Playstations; do you have them turned on with Remote Play enabled?

Il giorno 15 apr 2023, alle ore 14:13, Flavio De Stefano @.***> ha scritto:
Closed #39 https://github.com/kopiro/homebridge-playstation/issues/39 as completed.
—
Reply to this email directly, view it on GitHub https://github.com/kopiro/homebridge-playstation/issues/39#event-9014014171, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5LFH2G42U4LUYGEBRJ5UZTXBKGFLANCNFSM5Y4KP64A.
You are receiving this because you commented.

Ciao Flavio, penso tu sia Italiano vedendo il nome ed il cognome.
La mia situazione con il plugin è questa.
Installo, il plugin, esegue ( homebridge-playstation-login ) ma mi dice che non sono un utente root e che non ho i permessi.
Nella tua nuova guida ho visto che hai aggiunto una risoluzione dei problemi, eliminato il plugin, riavviato homebridge, preinstallato tutto ma nulla.
Riguardo  eliminare playactor, nella directory da te menzionata non trovo quel file o cartello.
Io uso homebridge su Raspberry 4. Grazie del tuo aiuto￼

I see - can you try su root (put root password), then call again homebridge-playstation-login ?
This won't work out of the box as you need to move the configuration to homebridge user but we can try to check if this is a good start.

Il giorno 15 apr 2023, alle ore 15:48, Flavio De Stefano @.***> ha scritto:
I see - can you try su root (put root password), then call again homebridge-playstation-login ?
This won't work out of the box as you need to move the configuration to homebridge user but we can try to check if this is a good start.

i ran homebridge.playstation-login as root user. ￼

And, what's the output?

Il giorno 15 apr 2023, alle ore 16:08, Flavio De Stefano @.***> ha scritto:
And, what's the output?
—
Reply to this email directly, view it on GitHub https://github.com/kopiro/homebridge-playstation/issues/39#issuecomment-1509848155, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5LFH2GUNOPUYUFTOV7ABXDXBKTWVANCNFSM5Y4KP64A.
You are receiving this because you commented.

I see this writing, uìil link doesn't reach me and if I open the second screen app I don't get the notification of playactor who would like to connect

Il giorno 15 apr 2023, alle ore 16:08, Flavio De Stefano @.***> ha scritto:
And, what's the output?
—
Reply to this email directly, view it on GitHub https://github.com/kopiro/homebridge-playstation/issues/39#issuecomment-1509848155, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5LFH2GUNOPUYUFTOV7ABXDXBKTWVANCNFSM5Y4KP64A.
You are receiving this because you commented.

sorry for my inconvenience, but I've been trying to make this plugin work on my ps for 1 year I think.

i can't find this directory on my homebridge.￼

i have the same issue, terminal doesn't give the link to verify my PS4, so I can't connect it to homebridge

still happening for me.


Option to run Smithy CLI without isolated classpath?

Thanks for this plugin! I've been using it without issue on OS X and Linux environments, but a colleague on Windows is getting classpath errors from the smithyBuildJar task. A typical error looks like this:
> Task :model:smithyBuildJar FAILED
Running smithy build
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-openapi\1.0.8\cbebc91325ac824ccc71a0738aeeab6a3b828b12\smithy-openapi-1.0.8.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-build\1.0.8\1943056b6e6d61e51b16396d4343b9d6fcf3c9a5\smithy-build-1.0.8.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-jsonschema\1.0.8\969868b1cc2c693001f33093f46d07df597ed362\smithy-jsonschema-1.0.8
.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-aws-traits\1.0.8\4c75784ac723e64b88f7f8ce39b9633582a48444\smithy-aws-traits-1.0.8
.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-model\1.0.8\97ec736517441a7ea61e505b6fea5c555e3c4685\smithy-model-1.0.8.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-utils\1.0.8\27d4c21862631385c91749c228cff090e8bafffd\smithy-utils-1.0.8.jar
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-gradle-plugin\0.5.1\4ed8279d17a81f9f9fbbc30789d8dd23ea85694c\smithy-gradle-plugin
-0.5.1.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-cli\1.0.8\de64615e551d89ce77649d37d2d72cbc73a5791c\smithy-cli-1.0.8.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-linters\1.0.8\57410fcb69eeb9e9fdae26dbf5219262d0bdde1\smithy-linters-1.0.8.jar;C
CLI classpath JAR does not exist: C:\Users\tooth\Workspaces\psf-api\model\Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-diff\1.0.8\5fc218b017f3737695d4ac724f61257afe02e414\smithy-diff-1.0.8.jar;C
software.amazon.smithy.cli.Cli

FAILURE: Build failed with an exception.

Gradle seems to be prepending the module root (C:\Users\tooth\Workspaces\psf-api\model) to the enumerated classpath when those entries start with a backslash. I ran the plugin in a debugger and saw that the fileset stored by the collection passed to executeCliThread is correct (e.g., the entries look like \Users\tooth\.gradle\caches\modules-2\files-2.1\software.amazon.smithy\smithy-aws-traits\1.0.8\4c75784ac723e64b88f7f8ce39b9633582a48444\smithy-aws-traits-1.0.8 .jar;C), but when getFiles is called, the classpath entries get the unwanted prefix of the module root path, and when the CLI is invoked with that classpath, it of course can't find any files. I don't think this is due to anything in the plugin itself (at least not as far as I could tell) but may be a more general bug in how classpath entries get translated into a FileCollection in Gradle's plugin support classes.
My ask here is, could you add a configuration flag to the plugin to not run the Smithy CLI in an isolated manner? I see I can choose between a forked process or a Java thread, but both of those options use an incorrect classpath on Windows.

@jeskew ,
Happened to be playing around with Smithy over the weekend, and ran into this too. I've managed to get past the specific issue by commenting out the inclusion of protocol tests in the main settings file because all i wanted was a built smithy binary. That might not work for your friend temporarily, but if it does, there you go.
@JordonPhillips
I wonder if the issue itself is because of smithy-gradle-plugin's does this in SmithyBuildJar:
        builder.libClasspath(SmithyUtils.getClasspath(getProject(), RUNTIME_CLASSPATH).getAsPath());
        builder.buildClasspath(SmithyUtils.getBuildscriptClasspath(getProject()).getAsPath());

...which is passed to smithy-cli's BuildParameterBuilder that does this:
`
    this.buildClasspath.addAll(splitAndFilterString(":", buildClasspath));

`
getAsPath returns a platform-specific string, and splitting by ":" doesnt work on Windows, likely? This might need fixing even if it's not the cause of this issue, btw, since it's reading in platform-specific strings and splitting them by a unix-only delimiter.
Just a suggestion, I couldnt get all the repos building to local maven and gradle repos/caches to actually repro/confirm.

Update: I did get the local repos/caches working and after changing all use of ":" with System.getProperty("path.separator") in the two classes mentioned above, I'm past the CLI classpath JAR does not exist problem.
However, re-enabling protocol tests still fails with tons of errors like pasted below, dont know enough of Smithy's model resolution logic in smithy-build to understand if my fix caused it, or if its unrelated.
ERROR: aws.protocoltests.json10#NoInputAndNoOutput (Model)
     @ C:\Users\vinoddin\Documents\Official\projects\smithy\smithy-aws-protocol-tests\model\awsJson1_0\empty-input-output.smithy
     |
  17 | apply NoInputAndNoOutput @httpRequestTests([
     |                                            ^
     = Unable to resolve trait `smithy.test#httpRequestTests`. If this is a custom trait, then it must be defined before it can be used in a model.

DANGER: - (SyntacticShapeIdTarget)
     @ C:\Users\vinoddin\Documents\Official\projects\smithy\smithy-aws-protocol-tests\model\awsJson1_0\empty-input-output.smithy
     |
  21 |         protocol: awsJson1_0,
     |                   ^
     = Syntactic shape ID `awsJson1_0` does not resolve to a valid shape ID: `aws.protocols#awsJson1_0`. Did you mean to quote this string? Are you missing a model file?

<snip>
Validation result: 228 ERROR(s), 444 DANGER(s), 0 WARNING(s), 0 NOTE(s)
Validated 1090 shapes in model
The model is invalid: 228 ERROR(s), 444 DANGER(s)
Error executing Smithy CLI (ReflectiveOperationException)
java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at software.amazon.smithy.gradle.SmithyUtils.lambda$executeCliThread$2(SmithyUtils.java:279)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: software.amazon.smithy.cli.CliError: The model is invalid: 228 ERROR(s), 444 DANGER(s)
	at software.amazon.smithy.cli.commands.Validator.validate(Validator.java:86)
	at software.amazon.smithy.cli.commands.CommandUtils.buildModel(CommandUtils.java:47)
	at software.amazon.smithy.cli.commands.BuildCommand.execute(BuildCommand.java:109)
	at software.amazon.smithy.cli.Cli.run(Cli.java:144)
	at software.amazon.smithy.cli.SmithyCli.run(SmithyCli.java:93)
	at software.amazon.smithy.cli.SmithyCli.run(SmithyCli.java:78)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at software.amazon.smithy.gradle.SmithyUtils.lambda$executeCliThread$2(SmithyUtils.java:279)

Update: I did get the local repos/caches working and after changing all use of ":" with System.getProperty("path.separator") in the two classes mentioned above, I'm past the CLI classpath JAR does not exist problem.

That would explain the trailing ;C on the classpath entries.
In the meantime, I’ve been using the Smithy CLI directly as a Gradle task so that the project will build on Windows:
configurations {
    smithy
}

dependencies {
    smithy("software.amazon.smithy:smithy-cli:1.0.8")
    smithy("software.amazon.smithy:smithy-model:1.0.8")
    smithy("software.amazon.smithy:smithy-openapi:1.0.8")
}

task build(type: JavaExec) {
    classpath configurations.smithy
    main = "software.amazon.smithy.cli.SmithyCli"
    args("build",
        "--config",
        file("$project.projectDir/smithy-build.json").toString(),
        "--output",
        file("$project.buildDir/smithyprojections/model").toString(),
        "--discover",
        file("$project.projectDir/src/main/smithy").toString())
}

The main drawback of this approach is that the model will be recompiled every time the build target is invoked (as opposed to only when the model files change as happens with the smithy Gradle plugin).

Thanks for the help on this, @vinoddin.
I've got two PRs that address this. After merging them, I'll fire it up in Windows to see if I can fix any remaining issues:

https://github.com/awslabs/smithy/pull/575
https://github.com/awslabs/smithy-gradle-plugin/pull/28

After that, we'll see if we can set our tests up to automatically run on Windows too.

Both the main smithy repo and this repo now have windows ci runnning. As mentioned above, there were a few more things that needed touching up on the main smithy repo. If you have any other problems, don't hesitate to open up another issue!


Exporting to dashboard functionality

This implements what was required in #104

Codecov Report

Merging #108 (09b24e0) into devel (edf2135) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            devel     #108      +/-   ##
==========================================
+ Coverage   75.85%   75.98%   +0.13%
==========================================
  Files         114      116       +2
  Lines        6986     7026      +40
==========================================
+ Hits         5299     5339      +40
  Misses       1687     1687

Impacted Files
Coverage Δ

openghg/util/__init__.py
100.00% <100.00%> (ø)

openghg/util/_export.py
100.00% <100.00%> (ø)

tests/util/test_export.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Schroedinger Wave Equation

There is some interest in Decapodes for applications concerning quantum mechanics. There is interest in Decapodes for which differential forms are complex-valued.
This PR will allow users to specify using of Complex over Float input data, and provide an example of the Schroedinger Wave Equation written as a Decapode.

TODO: Plot magnitude as the probability amplitude and LGTM

Here is the plot using the extrema of |Psi|*|Psi| at each time step.
According to some quick reading, it is expected for Psi to go to infinity unless given "exactly the right initial conditions".
https://galileo.phys.virginia.edu/classes/751.mf1i.fall02/OneDimSchr.htm
So, this PR will be good to merge once we update it to use the appropriate method of specifying ComplexF64 as the type.


List Routes/Ingresses created by odo deploy in odo describe component

What type of PR is this:
/kind feature

What does this PR do / why we need it:
Which issue(s) this PR fixes:

Fixes #5990
PR acceptance criteria:

[ ] Unit test

[x] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

Use the devfiles in this PR to deploy the component with odo deploy.
Run odo describe component to see if the URLs are printed.

/retest-required

(But this can be done in a subsequent PR if you prefer to have this merged first).

Yes, please. I'll open a separate PR for this.

(But this can be done in a subsequent PR if you prefer to have this merged first).

Yes, please. I'll open a separate PR for this.

Ok. I created this issue for the record: https://github.com/redhat-developer/odo/issues/6319

/override ci/prow/v4.11-integration-e2e
Tests passing on IBM Cloud.


When a marker/pattern is visible, does it return a value?

My question is when the marker is visible, is there a property or method that can return whether or not the marker is visible?
For instance, in the multiple pattern example, if one of the markers is not detected, does it return a value that you can use to script with?
I am currently playing video on one marker, and I want to play a video on another marker, but I need to mute the sound when one of the markers is not detected.
Cheers

yes, the marker object3d will be .visible or not. This is directly inherited directly by three.js
When you attach a object3d to a marker, you attach it to a THREE.Group. it is called markerRoot in most of my sources
if markerRoot.visible === false then the marker isnt seen
if markerRoot.visible === true then the marker isnt seen
There are some events too, but it is still unclear - see event markerFound
https://github.com/jeromeetienne/AR.js/blob/master/three.js/threex-armarkercontrols.js#L166
i hope this helps

Thanks!
Lastly though, how would I access the markerRoot from <a-marker> ?

Thanks! Great work by the way!


forkexec: close all inherited fds

Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

Testsuite passed


fix error

Problem
In testing the current viewer on main, I get an undefined error on the heartbeatPing
Solution
I just added a check, but I don't understand why this would be undefined, so if someone has a better idea, let me know
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

I think this is actually the right fix:  https://github.com/simularium/simularium-viewer/pull/315/commits/368425fa91fa1cb6d5397093e323e83ccd4b441b


Fix for recent (incoming) MOTECH changes

Fixes that will be needed after http://review.motechproject.org/#/c/5416/ merge.

ok to test

ok to test

test this please


Refactor: Buffer

Ref: #27
Fix's: #26

This is a very impressive rework!
After a glance it looks like this is ready to replace the old bufferer, whats your thoughts on this? If there isn't much to say I could start working on it (as we discussed over the Discord server that I could make the transition).

Yeah it looks good to me as far as i have looked, Im happy to handover the PR to you

@CosminPerRam 1 thing though, do we keep with bufferer.rs or rename to `buffer.rs. Its only internally used

We could rename it to buffer.


Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json

After installing got issue "Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in"
Further details:

Runtime:

Node.js version: 16.10.0

Priority this issue should have – please be realistic and elaborate if possible:

Not sn error, your imports must be versioned


DPI/display scaling

Seems like Lapce isn't handling a different display scale than 1.0 very well (at least on macOS):

Resizing the window leaves only a small viewport in the corner, the rest of the window does not get redrawn at all.
Line spacing is off, especially noticeable with box drawing characters like what nushell uses to draw its tables.

Hi, can you share a screenshot of the issue?
I thought macOS always scale at 2.0 for HiDPI.

Thanks for the screenshot.
Maybe can you let me know your OS version and which hardware?

The same happens for me

macOS Big Sur 11.6.1
Intel HD Graphics 530 / Radeon Pro 460
(it's a MacBook Pro 2016, 15-inch model)
Lapce seems to be using the Intel integrated GPU here.

Have this issue as well:
macOS Big Sur 11.6
AMD Radeon Pro 5300M 4 GB
2.6 GHz 6-Core Intel Core i7
MacBook Pro (16-inch, 2019)

Can you also let me know the display settings?

2880x1800 Retina, and alacritty (which uses winit) reports a device pixel ratio of 2.0

Similar/same issue on Windows where different monitors have different scaling applied
100% scaling

125% scaling

I got the same issue as OP, but only when compiling lapce in debug mode. In release mode it is fine.

Same issue with 0.0.2 on macOS 10.15.7.

Same behaviour as OP. Intel MacBook Pro 16" with macOS 12.0.1 installed from .dmg

                    'c<EMAIL_ADDRESS>                 ,xNMM.          -------------------
               .OMMMMo           OS: macOS 12.1 21C52 x86_64
               OMMM0,            Host: MacBookPro15,1
     .;loddo:' loolloddol;.      Kernel: 21.2.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 23 hours, 26 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 283 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: bash 5.1.12
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 1920x1200@2x
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Light)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: kitty
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   CPU: Intel i7-9750H (12) @ 2.60GHz
    kMMMMMMMMMMMMMMMMMMMMMMd     GPU: Intel UHD Graphics 630, Radeon Pro 560X
     ;KMMMMMMMWXXWMMMMMMMk.      Memory: 16793MiB / 32768MiB
       .cooc,.    .,coo:.

I actually seem to get something simliar with scaling turned on in Ubuntu 21.10 (using wayland).
This is what it looks like with scaling at 100%:

and this the very same running instances window dragged over to a second monitor with scaling enabled (at 200%):

lapse debug build of main branch at 93737031

Should be fixed by the latest release. https://github.com/lapce/lapce/releases/tag/v0.0.3

Yeah,, fixes the problem for me with Windows.
Many thanks

Thank you for working on this so quickly! On Linux I can now see the expected UI but unfortunately this doesn't yet fix the issue on Linux wayland for scaled displays or resizing on a non scaled display.
Here is what it looks like (correct) on a 100% scaled display:

But as soon as I try to resize the window I get:

And when I move the window over onto a scaled monitor display (at 200%) I get:

This is all with Ubuntu 21.20 Gnome (wayland) and happens with using both "standard" scaling and the experimental fractional scaling.

@maks which commit is it running on?

its:
>git log --oneline
a61d3b2 Updte piet-wgpu

I'm trying lapce 176fbd8 (current master branch) on Linux with Xorg. With "XFCE settings -> appearance -> settings -> window scaling" set to 2x, lapce GUI is rendered very small.
Changing the setting after running lapce also doesn't make any difference. It seems like the setting is ignored.

On latest release, this is what I have on GNOME 42/Wayland:

My screen is 2880/1800 at 200% zoom.

Ah, it actually works on master! My bad!


Dwarves having   noRot: true

Description
Almost every single unique feature of dwarves is great, they have next to none weaknesses, besides carrying somebody and being disarmed due to their mass. Turns out, they also have   noRot: true
Dionas also have   noRot: true, but they have so many negatives, that it's almost fine and a unique ability of theirs.
The only reason I can see dwarves having   noRot: true is that they drank so much alcohol in their lives, that they are essentially alcohol itself. Then change their bloodstream to ethanol.

By noRot: true, do you mean that the sprites do not rotate with the camera?

By noRot: true, do you mean that the sprites do not rotate with the camera?

I think I made quite a fool of myself, I thought that answers whether the body rots or not. My bad.
Then the actual bug is that dwarves just don't rot, at all. Launched local server, alt-tabbed for 30+ minutes and they were still fresh to clone.

This is a prime example of why abbreviations are confusing.

its not dwarf specific happens to everyone, dupe of 15968


feat(io): add streaming function

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

32 of 43 (74.42%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 99.234%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/IO/streaming.php
26
37
70.27%

Files with Coverage Reduction
New Missed Lines
%

src/Psl/Shell/execute.php
2
93.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
3498

Relevant Lines:
3525

💛  - Coveralls


Panic while using a proc_macro2 type across crates

Hi! I'm building a library for common transformations on proc_macro2 types, to be used by crates that implement procedural macros. However, on a simple example I get a "procedural macro API is used outside of a procedural macro" panic while running the procedural macros that use my library. On rustc stable the stacktrace is this:
thread '<unnamed>' panicked at 'procedural macro API is used outside of a procedural macro', src/libproc_macro/bridge/client.rs:315:17
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
thread '<unnamed>' panicked at 'procedural macro API is used outside of a procedural macro', src/libproc_macro/bridge/client.rs:315:17
stack backtrace:
   0:     0x7f82cd65bc63 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h39625934646a062b
                               at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1:     0x7f82cd6585db - std::sys_common::backtrace::_print::h5ed439e79e04d188
                               at src/libstd/sys_common/backtrace.rs:71
   2:     0x7f82cd65b1c6 - std::panicking::default_hook::{{closure}}::h13bf33e40bf761d8
                               at src/libstd/sys_common/backtrace.rs:59
                               at src/libstd/panicking.rs:197
   3:     0x7f82cd65af59 - std::panicking::default_hook::h7e24c700cb9d2623
                               at src/libstd/panicking.rs:211
   4:     0x7f82cd65b85f - std::panicking::rust_panic_with_hook::h37915b26028fb081
                               at src/libstd/panicking.rs:474
   5:     0x7f82cd644c54 - std::panicking::begin_panic::hcdc903573ebd5923
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libstd/panicking.rs:408
   6:     0x7f82cd646fe7 - proc_macro::bridge::client::BridgeState::with::{{closure}}::{{closure}}::h3382c8e11e482293
                               at src/libproc_macro/bridge/client.rs:315
                               at src/libproc_macro/bridge/client.rs:285
   7:     0x7f82cd64fa6e - <proc_macro::bridge::client::TokenStream as core::ops::drop::Drop>::drop::h8e51ee09467cd1a5
                               at src/libproc_macro/bridge/scoped_cell.rs:73
                               at src/libproc_macro/bridge/client.rs:283
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libstd/thread/local.rs:299
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libstd/thread/local.rs:245
                               at src/libproc_macro/bridge/client.rs:282
                               at src/libproc_macro/bridge/client.rs:313
                               at src/libproc_macro/bridge/client.rs:229
                               at src/libproc_macro/bridge/client.rs:54
   8:     0x7f82cd4868ee - core::ptr::real_drop_in_place::hf2445d86ec525323
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libcore/ptr.rs:193
   9:     0x7f82cd4843ed - core::ptr::real_drop_in_place::ha7ade299302c3d13
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libcore/ptr.rs:193
  10:     0x7f82cd481996 - core::ptr::real_drop_in_place::h43791beb06c742c8
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libcore/ptr.rs:193
  11:     0x7f82cd485c4d - core::ptr::real_drop_in_place::hd775cf35fc1bb319
                               at /rustc/e68bf8ae15ee6c052d0bcc9252386c5c5ee86de2/src/libcore/ptr.rs:193
  12:     0x7f82cd48a9ff - rust_contracts_plugin::add_print_statement::h7dfb1243dcb5f90e
                               at src/lib.rs:45
  13:     0x7f82cd48ade4 - <rust_contracts_plugin::ExamplePlugin as rust_contracts_common::Plugin>::requires::he0ade53953999f6a
                               at src/lib.rs:49
  14:     0x7f82cd94afd5 - rust_contracts::requires::hb06e7b0e59ece6e3
                               at src/lib.rs:20
  15:     0x7f82db5846c3 - std::panicking::try::do_call::he0cfe2347b79c08b
                               at src/libproc_macro/bridge/client.rs:412
                               at src/libproc_macro/bridge/scoped_cell.rs:78
                               at src/libproc_macro/bridge/scoped_cell.rs:73
                               at src/libproc_macro/bridge/scoped_cell.rs:78
                               at src/libproc_macro/bridge/client.rs:309
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/thread/local.rs:299
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/thread/local.rs:245
                               at src/libproc_macro/bridge/client.rs:309
                               at src/libproc_macro/bridge/client.rs:404
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/panic.rs:315
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/panicking.rs:293
  16:     0x7f82dfc8f169 - __rust_maybe_catch_panic
                               at src/libpanic_unwind/lib.rs:85
  17:     0x7f82db589964 - proc_macro::bridge::client::__run_expand2::h06efd32edc9bf6c0
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/panicking.rs:272
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/panic.rs:394
                               at src/libproc_macro/bridge/client.rs:403
  18:     0x7f82d8efa2db - proc_macro::bridge::server::run_server::h5ad2e1d5ca69ae92
  19:     0x7f82d8f41bf6 - proc_macro::bridge::server::<impl proc_macro::bridge::client::Client<fn(proc_macro::TokenStream, proc_macro::TokenStream) .> proc_macro::TokenStream>>::run::hc54f284a62bead95
  20:     0x7f82d8f40ae4 - <syntax_ext::proc_macro_impl::AttrProcMacro as syntax::ext::base::AttrProcMacro>::expand::hc796c23e0e298b84
  21:     0x7f82dc450e81 - syntax::ext::expand::MacroExpander::expand_invoc::h83e74a69b56716b3
  22:     0x7f82dc44aaa2 - syntax::ext::expand::MacroExpander::expand_fragment::hde21eab708be7bea
  23:     0x7f82dc449a34 - syntax::ext::expand::MacroExpander::expand_crate::hbae5c9f93d7abb65
  24:     0x7f82deec5e2a - rustc_interface::passes::configure_and_expand_inner::{{closure}}::h6d6c401c52c50a09
  25:     0x7f82deebf85c - rustc::util::common::time::he70e5592d51735a8
  26:     0x7f82dee7ecf1 - rustc_interface::passes::configure_and_expand_inner::hbcddd9e6c04bcc13
  27:     0x7f82def2161d - rustc_interface::passes::configure_and_expand::{{closure}}::heb783aa758c77f92
  28:     0x7f82deeeb541 - rustc_data_structures::box_region::PinnedGenerator<I,A,R>::new::h94ef77888478da3f
  29:     0x7f82dee7bd15 - rustc_interface::passes::configure_and_expand::h55ccdb31ace0623b
  30:     0x7f82dee6893b - rustc_interface::queries::Query<T>::compute::h02f8b9980061120d
  31:     0x7f82dee6b2f2 - rustc_interface::queries::Query<T>::compute::hd767ea13615a6983
  32:     0x7f82dee68195 - rustc_interface::queries::Query<T>::compute::h02d0256bb419922a
  33:     0x7f82def71633 - rustc_interface::queries::<impl rustc_interface::interface::Compiler>::prepare_outputs::h1fedf977dc567849
  34:     0x7f82dff689f3 - rustc_interface::interface::run_compiler_in_existing_thread_pool::h01017a6213536cb6
  35:     0x7f82dffe6da5 - std::thread::local::LocalKey<T>::with::h57e4e9c51937ccb9
  36:     0x7f82dff89eb4 - scoped_tls::ScopedKey<T>::set::h581b66761e86975e
  37:     0x7f82dffd5801 - syntax::with_globals::h7a79417414defd1b
  38:     0x7f82dff37414 - std::sys_common::backtrace::__rust_begin_short_backtrace::h81c9d6a59d8e80cf
  39:     0x7f82dfc8f169 - __rust_maybe_catch_panic
                               at src/libpanic_unwind/lib.rs:85
  40:     0x7f82dff62e58 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hd1b720554dd4145a
  41:     0x7f82dfc6036e - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h805c3cc89d534c05
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/liballoc/boxed.rs:704
  42:     0x7f82dfc8dddf - std::sys::unix::thread::Thread::new::thread_start::h6f10b78f26c98dc6
                               at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/liballoc/boxed.rs:704
                               at src/libstd/sys_common/thread.rs:13
                               at src/libstd/sys/unix/thread.rs:79
  43:     0x7f82df9ff6b9 - start_thread
  44:     0x7f82df32941c - clone
  45:                0x0 - <unknown>
thread panicked while panicking. aborting.

Is this an expected limitation of proc_macro2 or a bug? In the procedural macro implementation I'm just converting a proc_macro::TokenStream to a proc_macro2::TokenStream, passing it to the library that I'm building.

Could you share the code that leads to this? It's expected to get one of these panics, but the double panic causing an abort is a bug. (I'm not sure how that's happening though)

Sure, the code is here: https://github.com/viperproject/rust-contracts/tree/eea10fae8a7b97a5b64ca3f9efb3038e4a6d9246
To see the crash:
cargo build --all --examples
cargo build --manifest-path example_plugin/Cargo.toml
LD_LIBRARY_PATH=example_plugin/target/debug/ RUST_CONTRACTS_PLUGIN=example_plugin/target/debug/ cargo test --all --examples -- --nocapture

The crate in example_plugin is called rust_contracts_plugin and is linked as a native library to rust_contracts (the main crate).

Ok thanks for the info! This is indeed something not supported by this library nor really something that can be supported. This is basically what's not valid because it's not valid for TokenStream to cross dynamic library boundaries as-is.

I have the same questions, while I had upgrade rustlib(libstd, libcore, proc_macro...)，then I recompile fuchsia system, I got the infos:
./host_x64/configc rust --cm obj/src/diagnostics/sampler/cml/sampler-manifest/sampler.cm --output obj/src/diagnostics/sampler/sampler-component-config_rust_config_lib_source.rs --fidl-library-name cf.sc.internal.samplercomponentconfig --rustfmt ../../prebuilt/third_party/rust/linux-x64/bin/rustfmt --rustfmt-config ../../rustfmt.toml
Illegal instruction (core dumped)
I tracking my code found the reason is,
fn with(f: impl FnOnce  --> panic!("procedural macro API is used outside of a procedural macro");
How do I resolve this build error?   Could you please help me！


windows compiling

Adding conditions and libs needed for compiling in windows envs

@Maaarcocr wdyt about shipping the gem with pre-compiled binaries?


Add tooltips to glossary terms

It would be nice to add tooltips to glossary terms, so that people don't have to navigate away from the page to find a definition.
Resources include:

https://sphinx-hoverxref.readthedocs.io/en/latest/usage.html#tooltip-on-glossary-terms
https://myst-parser.readthedocs.io/en/latest/syntax/roles-and-directives.html#roles-an-in-line-extension-point
https://sphinx-hoverxref.readthedocs.io/en/latest/configuration.html#confval-hoverxref_roles

As this issue also addresses the glossary in a similar way to this one, maybe it would be best to close it and rename the other one.


Custom characters & v1.001 DATA.WIN

So, I have two issues:
1: I know it's possible, but I find it very unclear. How do I get my custom glyphs to show up in the app?
2: The app fails to extract the v1.001 data.win file.
Thanks for any help

You need to extract data.win, create folder FONT_new and lay new fonts there.

After that you need to change fontnames.txt. In my case it will be look so:
fnt_papyrus.gmx
fnt_comicsans.gmx
fnt_maintext.gmx
fnt_plain.gmx

Lines must contain new font names:
Fonts:
1) Papyrus
2) Sans
3) Main
4) Plain

Hmm, I tested it now. Everything is ok... Did you download binary or built by yourself? Did you put extraction utilities there?


Add Alexendoo and dswij to Clippy's reviewing rotation :tada:

And welcome to the reviewing rotation @Alexendoo and @dswij :upside_down_face:
r? @flip1995 or @Manishearth
cc: https://github.com/rust-lang/team/pull/767

Hey @Mark-Simulacrum, would you mind merging this? :upside_down_face:


Safer version of StandardToken. Fix #442

I found it difficult to find a good name for it. If you have suggestions... 👍

I agree that SaferStandardToken sounds a bit generic.
Alternatives: NonHoldingStandardToken? It's actually hard to think of other alternatives.
If we really want this feature to be widely adopted, I think that this feature should be native to StandardToken and having it inherit from a StandardTokenBase that doesn't have the limitation of not being able to hold stuff.

I would changed the StandardToken instead of adding another version of it, IMO if it is safer and does not change the capabilities/behavior of the StandardToken it should be consider as the standard version.

Also down to put this in StandardToken and a breaking change. People like Request Network have already added this functionality themselves ad-hoc.

Closing as stale.


sbt universal:packageZipTarball generating line that is too long for windows

steps
sbt version: 1.3.2
sbt universal:packageZipTarball
problem
APP_CLASSPATH in generated .bat file is too long for windows
windows error
The input line is too long.
The syntax of the command is incorrect.

expectation
runnable bat
notes
editing the line beggining with
set "APP_CLASSPATH..

(https://gist.github.com/npersad/8b25e79141a6753f048cc037d5ede5c4#file-bad-bat-L83)
to use  set "APP_CLASSPATH=%APP_LIB_DIR%\*"
is a workaround

my fault this is detailed in the article
https://sbt-native-packager.readthedocs.io/en/stable/recipes/longclasspath.html#long-classpaths


Adds check to see if heading element is empty. If it is, just leave it.

A log-awaited bugfix!

This should fix #1


Remove lib folder to get ready for v2.13.1 template merge

Description of feature
Remove lib folder to get ready for v2.13.1 template merge

Done in #391


Parse json 19

This includes the frontend and the ToolModule. This makes accessing all the functionality of tool straightforward from the frontend.
The next step will be incorporating the new tool modules as well as the make bed files in the frontend.

Looks good, working as expected. Changes to introduce new functionality may be added in the future


Signed-off-by: amolmote<EMAIL_ADDRESS>

I have successfully made the Contributor License Agreement check it again


DEPENDENCIES: version of caddy in go.mod has vulns

What are the steps to reproduce this issue?

the version of caddy in the local go.mod has vluns

NOTE our go.mod is not used for building, so it has no affect on the output CoreDNS binary, but its bad form
Update the code here to remove the versions of caddy in our go.mod

https://github.com/gravwell/coredns/pull/14


Shared mailbox

Any way to have multiple account accessing same mailbox?

No, that's not possible at the moment.
It's not trivial to add that. Mox currently only keeps mailboxes in an account (in per-account db files). Sharing mailboxes could be implemented in the future by having a separate place to share mailboxes and give access to multiple accounts. Or to give one account access to mailboxes of another account, which would require quite pervasive changes (multiple account handles in an IMAP/webmail/etc connection).
I can think of two workarounds at the moment, which may work depending on your use-case.

Create a new account and give two people access to it.
Create an alias for incoming mail and add two existing accounts as members.

I'm curious how you're plan to use shared mailboxes. Insights into needs/requirements can help with a future implementation.

@mjl- This is basically a business use case, several people communicate with customers, sure there could be single mailbox, but each time person leaves, the password would need to be reset etc., not very good for security, multiple credentials for a single account solves it. Alias doesn't solve it, because then you don't see the previous communication.
I actually have the same model in bank, several people have access to same bank account under different credentials. There could also be read-only credentials for apps and API like purposes.

Thanks, yeah, this use-case makes sense. It's also pretty common in
businesses with assistents having access to other people's mailboxes (whole
accounts). IMAP has a mechanism around namespaces for making other mailbox
hierarchies (of other people's accounts) available in an account. Even with
ACLs for configuring access.
I hope to implement this at some point, but it's not easy, which is a good
part of the reason it's not high on the priority list...


Subscribe via email

I like your writes, consider creating a mail subscription, I'd like your writes to land my inbox.

Maybe it's worthwhile to add ability for email subscription. I don't know how difficult it would be to add, also considering that it should be scoped to a single author.

Shouldn't there be a feed client which can redirect our Atom feed to email? We already have a feed, so I think it's an overkill to have a newsletter as well.

Yeah, probably.


SAK-41843 - CKEditor: Replace movieplayer plugin (Flash) by an HTML5 …

…alternative

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

Thanks @ottenhoff !


Maintenance Question

Is there any intent to keep this maintained? I know it's not ACME, but I find your library incredibly entertaining, as well as well-written and comprehensible.

Hey, I've been a little busy lately but when find the time ill work on this. I appreciate your interest 😃


UI: Do not show the user and TestSuite entities in data insight graph

Today we are showing the user and test suite entities in data insight graphs, so for now from the UI we should filter out those and not show the user and TestSuite entity in the data insight graph.
cc: @TeddyCr

Handled by https://github.com/open-metadata/OpenMetadata/pull/8699


migrate notebooks from whitenoise-core to whitenoise-samples

The notebooks demonstrating the Python bindings move to whitenoise-samples/analysis and get removed from this repo, along with the accompanying datasets.

@Shoeboxam Are you using the PUMS dataset in /bindings-python/data for other tests or code examples?

I'm currently using it, but would like to move to synthetic data.

I'd be happy to work on this if I can get a better sense from @Shoeboxam about his needs for the data.

We can move data to another issue.


Keep headers and don't duplicate similar authors

Fixes #49
Fixes #82
Fixes #93

hi @Klap-in these changes look reasonable to me. Can you merge them and apply them on the server?

Thanks for the feedback. At the moment I'm firstly testing and fine tuning them with a check out of this branch at the server.


Focus next input with floating label property

I have gone through these following points
[ yes ]  Check latest documentation: https://docs.nativebase.io/
[ yes ]  Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[ yes ]  Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[ yes ]  Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
Issue Description

Hello guys! At this moment I faced with a problem with focusing inputs. I found that focusing don't work if you have a nested Input inside an Item with floating label. Fortunately, everything works fine without floating label.
Dependencies

Expo ^32.0.0

Native Base ^2.12.1

React 16.5.0

React Native (https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz)

React Navigation ^3.0.9

Node 11.11.0

Yarn 1.13.0

Expected behaviour
Focus next Input onSubmitEditing using <Item floating label />.
Actual behaviour
Focus next Input using <Item floating label /> return an Error 'Cant focus undefined'.
Steps to reproduce

Imagine this simple Component:
export default class HomeScreen extends React.Component {
  static navigationOptions = {
    header: null,
  };

  constructor(props) {
    super(props);

    this.state = {
      login: '',
      password: ''
    };
  };

  changeLogin(text) {
    this.setState({ login: text })
  };

  changePassword(text) {
    this.setState({ password: text })
  };

  render() {
    return (
      <View style={styles.container}>

          <Item floatingLabel>
            Login
            <Input value={ this.state.login }
                   onChangeText={ () => this.changeLogin(text) }
                   autoFocus={true}
                   ref='login'
                   onSubmitEditing={ () => this.refs.password.focus() } />
          </Item>

          <Item floatingLabel>
            Password
            <Input value={ this.state.password }
                   onChangeText={ () => this.changePassword(text) }
                   ref='password'
                   onSubmitEditing={ () => this.refs.login.focus() } />
          </Item>

      </View>
    );
  }
}

Focus next Input in onSubmitEditing method dont work properly. In output we have this:

If we will remove floating label property from Item everything will work as expected.
Working example on Dropbox:
https://www.dropbox.com/s/hcduic2uqjqc64l/ReactInput.zip?dl=0
Steps to reroduce:

Unzip archive;
cd ReactInput;
yarn install;
yarn start;

Is the bug present in both iOS and Android or in any one of them?
Tested on Android only.
Any other additional info which would help us debug the issue quicker.
Message me.

Seems like focus() don't work without floating label too...

blur() also doesn't seem to work.

I wasted a whole day, due to this problem.
Any update on this issue :(

Update: Changing ref to getRef solves the issue,
Check out this answer:
https://stackoverflow.com/questions/52523092/native-base-input-refs-not-being-set/52523488#52523488

Hi @dreamchasersuon, you can follow solution provided by @AmeerHamzaRiaz .
<Item floatingLabel>
  First Name
 <Input
    getRef={input => {
    this.firstNameRef = input;
 }}
   onSubmitEditing={() => {
      this.lastNameRef._root.focus();
    }}
   returnKeyType={"next"}
/>
</Item>
And
<Item fixedLabel>
  First Name
  <Input
    ref={input => {
      this.lastNameRef = input;
    }}
    onSubmitEditing={() => {
      this.lastNameRef._root.focus();
   }}
    returnKeyType={"next"}
  />
</Item>
In the case of floatingLabel, getRef works, while ref does not. On the other hand, in the case of fixedLabel, ref works, while getRef does not.

Hi @dreamchasersuon , closing for now due to inactivity. Let us know if the issue still persists.

can you try this library?


bazel: update rules_apple and rules_swift

rules_apple diff: https://github.com/bazelbuild/rules_apple/compare/d04edf4136b4818662d7126582ec257aee372339...a0f8748ce89698a599149d984999eaefd834c004
rules_swift diff: https://github.com/bazelbuild/rules_swift/compare/1.1.1...1.2.0

These will be needed to update to the latest version of rules_xcodeproj which will fix some issues we've had until now.

/retest


CORS error occurred when fetching access token

Issue and Steps to Reproduce
I tried to do a login action with the Google Auth api but the below error occurred when the authorization callback trying to fetch the access token from google token endpoint
Access to fetch at 'https://accounts.google.com/o/oauth2/v2/token' from origin 'http://localhost:4001' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
const googleConfig: OidcConfiguration = {
  authority: 'https://accounts.google.com/o/oauth2/v2',
  client_id:
    {client_id}
  redirect_uri: 'http://localhost:4001/dev/auth/oauth_redirect',
  scope: 'openid',
  service_worker_only: false,
  token_request_extras: {
    client_secret: {client_secret}
  },
  authority_configuration: {
    issuer: 'https://accounts.google.com/o/oauth2/v2',
    authorization_endpoint: 'https://accounts.google.com/o/oauth2/v2/auth',
    token_endpoint: 'https://accounts.google.com/o/oauth2/v2/token',
    end_session_endpoint: '',
    revocation_endpoint: '',
  },
};

Versions
NextJS
Screenshots
Expected
success response returned from token endpoint
Actual
CORS error occurred
Additional Details

Installed packages: 6.10.9-alpha0

Hi @fungcheukyin-TeamLab,  i did not manage to make google api work with localhost. You may configure you host.config in order to get a real domain name in local.

I am using that configuration which is working https://github.com/AxaGuilDEv/react-oidc/blob/2ef1d14f9f7cd88130e592d31c08d02a0e44ff44/packages/react/src/configurations.ts#L61

@guillaume-chervet
Thank you for your advise!
I will try out that configuration later on.


Refactor some coding style

Coverage increased (+1.09%) to 23.881% when pulling 360bf4b3b3de1ef02cd394a29094ab29a6dd1e55 on fwininger:coding_style into b339d1e18801c9ecd5f1be99cfad1b940a1c64fb on Cyberwatch:master.

Coverage increased (+1.09%) to 23.881% when pulling 360bf4b3b3de1ef02cd394a29094ab29a6dd1e55 on fwininger:coding_style into b339d1e18801c9ecd5f1be99cfad1b940a1c64fb on Cyberwatch:master.

Coverage increased (+3.5%) to 26.316% when pulling 5967af7488a1edee402edaa6ab527feff9fe9539 on fwininger:coding_style into b339d1e18801c9ecd5f1be99cfad1b940a1c64fb on Cyberwatch:master.


Enhancement Request: Add per-partition node state metrics

Hi - really appreciate the effort you've put in to this project - great work so far!
Would it be possible to add support for per-partition node state metrics, so that for partition X, you'd see a count of nodes in DRAIN/DOWN/ALLOC/... etc.?  This would be really useful in tracking the relative usage of partitions in a heterogeneous cluster.  This might be similar to tracking the output of a command like:
sinfo -h -o %D,%T -p
There may be some trickiness in deciding how to track node state for non-responsive nodes as sinfo will produce duplicate lines for non-responding nodes, e.g.
10,drained*
2,drained
showing that 10 nodes are drained and unresponsive, 2 are drained but responsive.  Ideally the total number of nodes in the partition would be recorded, so ideally the metric would track all nodes in drained state, not just responsive ones (-r option to sinfo)

Howdy! Appreciate the detailed feature request. I definitely think this could be useful. That would seem to be a pretty simple addition to the following function as well as off course adding the metric description and collection. I do not believe we have a node that get replicated for multiple states. After doing a couple experiments and checking the docs, I anticipate the following cardinality from command line: # of nodes * # partition per each node So this should be as simple as:
func fetchNodePartitionMetrics(nodes []NodeMetric) map[string]*PartitionMetric {
	partitions := make(map[string]*PartitionMetric)
	for _, node := range nodes {
		for _, p := range node.Partitions {
			partition, ok := partitions[p]
			if !ok {
				partition = &PartitionMetric{
					StateAllocMemory: make(map[string]float64),
					StateAllocCpus:   make(map[string]float64),
					StateNodeCount: make(map[string]float64),
				}
				partitions[p] = partition
			}
			partition.StateAllocCpus[node.State] += node.AllocCpus
			partition.StateAllocMemory[node.State] += node.AllocMemory
			partition.StateAllocMemory[node.State] += 1
			// ...
		}
	}
	return partitions
}

Let call our new metric slurm_partition_state_node_count for now. Lets say our cluster has 12 nodes in the state you described and all of them are part of 2 partitions (hw-a and hw-b), we should expect the exporter to emit the following metrics on collect:
slurm_partition_state_node_count{partition="hw-a",state="drained*"} 2
slurm_partition_state_node_count{partition="hw-a",state="drained"} 10
slurm_partition_state_node_count{partition="hw-b",state="drained*"} 2
slurm_partition_state_node_count{partition="hw-b",state="drained"} 10

With the above modification and some other modification, I believe that's what the exporter will output.
Let me know if you'd like to give this a go. Otherwise, I can get this in in the next couple of day/weeks. :)

Wow!  That's a fast response!  Yes, let me take a look and confirm, but looks exactly what's needed.

Good catch, thanks. I'll update the thread once this is done :)

@AndyMcVey Let me know how #87 is.


Return dtype for fftfreq and rfftfreq

The specs for fftfreq and rfftfreq say
"The returned array must have a real-valued floating-point data type determined by Type Promotion Rules."
But there is no type promotion here, since none of the input arguments are arrays. Presumably it should say that the return type should have the default real floating-point dtype.
But that also begs the question of whether these functions should have a dtype argument like the other array creation functions.

Actually all the fft functions have this "type promotion" line, except for fftshift and ifftshift, which say "The returned array must have the same data type as x." But each of these functions only have one array argument, so the "same data type" line is more appropriate.

Actually all the fft functions have this "type promotion" line, except for fftshift and ifftshift, which say "The returned array must have the same data type as x." But each of these functions only have one array argument, so the "same data type" line is more appropriate.

Oh I see it's because it's promoting from real to complex. It's a bit odd to call this type promotion, though, and it's even more awkward for functions like irfft that go from complex to real. It would be better to say something like "a complex floating-point dtype with the same bit width as x" (I don't know if we already have some wording like that).

That sounds like an improvement - although I'd clarify the "same bit width" phrase a bit, since it'd be float64 -> complex128 (so the dtype has double the number of bits).

Sorry, Aaron, for some reason I missed this issue. My bad.
For all applications that I know of (mainly in signal processing where fftfreq is used to prepare signal filters/windows), they must stay real. I think if (r)fftfreq were to return complex arrays, they'd break SciPy and Matplotlib in some unexpected ways.
IIRC @oleksandr-pavlyk raised the same question about how return real types should be determined, and the argument back then involved viewing these two functions as constructors. I think one could argue the dtypes can be determined by the argument d that specifies the step size, but adding an extra dtype argument to offer explicit control seems reasonable to me.

My point for adding a dtype argument wasn't to allow the user to specify a complex dtype. That should probably disallowed (or unspecified?). It was to allow the user to specify 32-bit vs. 64-bit, for consistency with the remaining creation functions in the spec.
I don't think we can get the dtype from d, which is only specified as a float. The only option is to return the default real floating dtype, which is what is specified at https://github.com/data-apis/array-api/pull/720/files#diff-31eaf0d090ecc4df2af89ab3d3a33b91ff8846925b579fd64bf065aea146a230R612 (prior to that PR it was just an ambiguous "a real-valued floating-point data type").
Given that this would be a new API, and no one has requested this, I would suggest making this change for 2024. We are already close to tagging 2023. And furthermore, this would not be compatible with the current NumPy API, which does not have a dtype argument in fftfreq or rfftfreq. If we were to squeeze this in for 2023, we would also want to get that added to NumPy for numpy 2.0 (which is probably possible, but again, no one has actually requested this yet, so it's not a priority).

Sounds good to me, I have no concern for either v2023 or v2024.


fix: Improve cluster connection pool logic when disconnecting

Motivation and Background
This is an attempt to fix errors occurring when a connect() call is made shortly after a disconnect(), which is something that the Bull library does when pausing a queue.
Here's a relatively minimal way to reproduce an error:
import IORedis from "ioredis";

const cluster = new IORedis.Cluster([{ host: "localhost", port: 6380 }]);

await cluster.set("foo", "bar");

const endPromise = new Promise((resolve) => cluster.once("end", resolve));
await cluster.quit();
cluster.disconnect();
await endPromise;

cluster.connect();
console.log(await cluster.get("foo"));
cluster.disconnect();

Running that script in a loop using
#!/bin/bash

set -euo pipefail

while true
do
    DEBUG=ioredis:cluster node cluster-error.mjs
done

against the main branch of ioredis quickly results in this output:
/Code/ioredis/built/cluster/index.js:124
                    reject(new redis_errors_1.RedisError("Connection is aborted"));
                           ^

RedisError: Connection is aborted
    at /Code/ioredis/built/cluster/index.js:124:28

Node.js v20.11.0

My debugging led me to believe that the existing node cleanup logic in the ConnectionPool class leads to race conditions: upon disconnect(), the this.connectionPool.reset() call will remove nodes from the pool without cleaning up the event listener which may then subsequently issue more than one drain event. Depending on timing, one of the extra drain events may fire after connect() and change the status to close, interfering with the connection attempt and leading to the error above.
Changes

Keep track of node listeners in the ConnectionPool class and remove them from the nodes whenever they are removed from the pool.
Issue -node / drain regardless of whether nodes disconnected or were removed through a reset() call.
Within reset(), add nodes before removing old ones to avoid unwanted drain events.
Fix one of the listeners by using an arrow function to make this point to the connection pool instance.
Try to fix the script for running cluster tests and attempt to enable them on CI. If this doesn't work out or isn't useful, I'm happy to revert the changes.
Add a test around this issue. The error thrown in the test on main is seemingly different from the error shown above but it still seems related to the disconnection logic and still gets fixed by the changes in this PR.

I now created a separate repository that (hopefully) makes it easy to reproduce the bug.
We have been using the fix in this branch in production throughout the last roughly 3 months and it has considerably reduced the error rates we are seeing when shutting down Bull queue clients.

I just pushed the fixes identified in https://github.com/valkey-io/iovalkey/pull/5.


No such file or directory: 'data-bin/iwslt14.tokenized.de-en/dict.de.txt'

Hi! I want to run the code in https://fairseq.readthedocs.io/en/latest/tutorial_simple_lstm.html, and in step 3 it needs iwslt14 dataset.
I use the script in https://github.com/pytorch/fairseq/blob/master/examples/translation/prepare-iwslt14.sh to download the dataset, and run the following command:
fairseq-train data-bin/iwslt14.tokenized.de-en \
  --arch tutorial_simple_lstm \
  --encoder-dropout 0.2 --decoder-dropout 0.2 \
  --optimizer adam --lr 0.005 --lr-shrink 0.5 \
  --max-tokens 12000

it turns out Exception: Could not infer language pair, please provide it explicitly. I look at previous issue and add --source-lang de --target-lang en arguments, then turns out the following:
FileNotFoundError: [Errno 2] No such file or directory: 'data-bin/iwslt14.tokenized.de-en/dict.de.txt'
However, there is no such file which will be generated from this script. Where should I find this dict.de.txt?

What was the solution to this issue? I am facing the same right now

What was the solution to this issue? I am facing the same right now

prepare-iwslt14.sh only download the dataset, you need to pre-process and binarize it. Please refer to https://fairseq.readthedocs.io/en/latest/getting_started.html#data-pre-processing


Error opening MKV. Demux error

Notes Before Posting

Only Open an issue if it's tied to Staxrip, If issues is tied to external program or filter. Head to Resp page for that project and open an issue there.
Beta Releases are Not Covered, Beta Are Pre-Releases and Could Contain Bugs. This is the Risk Your Willing to Take When using Beta releases. Beta Concerns should be posted in the forums.
If you Require Help with one of the FrameServers, Programs or Scripting Post in the Forums, Rather then opening a ticket here.
Link: https://forum.doom9.org/showthread.php?t=175845
Check your CPU Specs as Well. Many newer Filters are AVX2 Enabled with no AVX1 support(This is espeically True on VapourSynth side. Which will crash the software if your CPU doesn't support it.
Lastly, Only Files that are Released with StaxRip are fully supported, This is done to make debugging easier. Also since all filters have been tested before release. Newer versions can have changes which have not been added to StaxRip yet.

Describe the bug or Issue
A clear and concise description of what the bug is.
Add The Proper Label
Step To Reproduce the Problem

Go to '...'
Click on '....'
Using '...' Encoder
'Avisynth or VapourSynth' Being Used
Filter(s) x is being Used.
Any Major External Files tied to the Error.
Post Both your Log file & AVS/VS Script.
It it's Tied to Hardware Encoder Post your Hardware Specs along with the Following.

Screenshots
If possible, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 10 Build 1803]
Version [e.g. 1.9]
FrameServer Being Used [e.g. Avisynth]
Version of External Application / Filter Being Used [e.g. 2.9+10]
List of Filters Being Used [e.g. QTGMC]
Post your Logs, There Tell contain Allot of Information that Could Help.
The More Information Posted, The Easier it will be to Debug.

Additional context
Add any other Information or additional context that can be Helpful.
Please be Clear and as Detailed as Possible
Any Issues left unattended to for Length of Time will automatically be Closed Due and or Locked to inactivity
This Is The LOG:
------------------------- System Environment --------------------------
StaxRip    : <IP_ADDRESS>
Windows    : Windows 7 Ultimate
Language   : Italian (Italy)
CPU        : Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz
GPU        : AMD Radeon R9 200 Series
Resolution : 1280 x 1024
DPI        : 96
------------------------ MediaInfo Source File ------------------------
F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4
General
ID                       : 1 (0x1)
Complete name            : F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4
Format                   : MPEG-TS
File size                : 3.24 GiB
Duration                 : 1 h 29 min
Overall bit rate mode    : Variable
Overall bit rate         : 5 211 kb/s
FileExtension_Invalid    : ts m2t m2s m4t m4s tmf ts tp trp ty
Video
ID                       : 258 (0x102)
Menu ID                  : 1 (0x1)
Format                   : AVC
Format/Info              : Advanced Video Codec
Format profile           : High@L4
Format settings          : CABAC / 4 Ref Frames
Format, CABAC            : Yes
Format, ReFrames         : 4 frames
Codec ID                 : 27
Duration                 : 1 h 29 min
Width                    : 1 920 pixels
Height                   : 1 080 pixels
Display aspect ratio     : 16:9
Frame rate               : 25.000 FPS
Color space              : YUV
Chroma subsampling       : 4:2:0
Bit depth                : 8 bits
Scan type                : Progressive
Writing library          : x264 core 148
Color range              : Limited
Color primaries          : BT.709
Transfer characteristics : BT.709
Matrix coefficients      : BT.709
Audio
ID                       : 257 (0x101)
Menu ID                  : 1 (0x1)
Format                   : AAC LC
Format/Info              : Advanced Audio Codec Low Complexity
Format version           : Version 4
Muxing mode              : ADTS
Codec ID                 : 15-2
Duration                 : 1 h 29 min
Bit rate mode            : Variable
Channel(s)               : 2 channels
Channel layout           : L R
Sampling rate            : 48.0 kHz
Frame rate               : 46.875 FPS (1024 SPF)
Compression mode         : Lossy
Delay relative to video  : -40 ms
----------- Error Demux audio using MP4Box 0.7.2-DEV-rev1009 -----------
Demux audio using MP4Box 0.7.2-DEV-rev1009 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Funzione non corretta.
-------------- Demux audio using MP4Box 0.7.2-DEV-rev1009 --------------
"C:\Program Files (x86)\StaxRip\Apps\Support\MP4Box\MP4Box.exe" -single 257 -out "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007)_temp\Una Bionda A New York (2007) ID1 -40ms.mka" "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4"
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
[iso file] Incomplete box UNKN
[iso file] Incomplete file while reading for dump - aborting parsing
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
Truncated file - missing<PHONE_NUMBER> bytes
Error opening file F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4: IsoMedia File is truncated
-------------- Demux audio using MP4Box 0.7.2-DEV-rev1009 --------------
"C:\Program Files (x86)\StaxRip\Apps\Support\MP4Box\MP4Box.exe" -single 257 -out "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007)_temp\Una Bionda A New York (2007) ID1 -40ms.mka" "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4"
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
[iso file] Incomplete box UNKN
[iso file] Incomplete file while reading for dump - aborting parsing
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
Truncated file - missing<PHONE_NUMBER> bytes
Error opening file F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4: IsoMedia File is truncated
Start:    20:32:51
End:      20:32:52
Duration: 00:00:01
------------------------------ Exception ------------------------------
StaxRip.ErrorAbortException: Demux audio using MP4Box 0.7.2-DEV-rev1009 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Funzione non corretta.
-------------- Demux audio using MP4Box 0.7.2-DEV-rev1009 --------------
"C:\Program Files (x86)\StaxRip\Apps\Support\MP4Box\MP4Box.exe" -single 257 -out "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007)_temp\Una Bionda A New York (2007) ID1 -40ms.mka" "F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4"
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
[iso file] Incomplete box UNKN
[iso file] Incomplete file while reading for dump - aborting parsing
[iso file] Unknown box type ....
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type .{..
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type C..f
[iso file] Unknown box UNKN (0x554E4B4E) with payload larger than 1 MBytes, ignoring
[iso file] Unknown box type Lp.7
Truncated file - missing<PHONE_NUMBER> bytes
Error opening file F:\Da Convertire in MKV\OK\Da Comprimere\Una Bionda A New York (2007).mp4: IsoMedia File is truncated
in StaxRip.Proc.Start()
in StaxRip.MP4BoxDemuxer.Demux(String sourcefile, AudioStream stream, AudioProfile ap, Project proj)
in StaxRip.MP4BoxDemuxer.Run(Project proj)
in StaxRip.MainForm.Demux()
in StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding)

MP4Box can't reach � characters, Nothing I can do about that since I don't have control over that piece of software.
Also make sure your command window is set to format that can read the output format.


[DRAFT] (Japanese) Support construction order

Description

Related links
This PR is copied into:
https://github.com/tier4/CARET_doc/tree/draft_support_construction_order

Notes for reviewers

Pre-review checklist for the PR author

[ ] I've confirmed the contribution guidelines.
[ ] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

related: https://github.com/tier4/CARET_analyze/pull/249/files

Change to support construction order is made in https://github.com/tier4/CARET_doc/pull/183
This draft PR is closed now.
(CC: @miyakoshi-dev )


修改 css.build.js

Translation:
Modified css.build.js

But you just simply added a new line.

Closing as invalid. Not sure what's the purpose of the PR.


Git worflow

This PR implements a custom git worfklow that should work as follows:

Before running linters, it should git stash --keep-index to remove all files that aren't in the index (staged) from the working copy
Run commands (linters)
Adds changes (if any) to the commit
Allows you commit the changes
Do git stash pop to revert to the previous working copy state

This PR should solve #62 when done.
Right now I'm facing an issue with the last step since when running lint-staged in a pre-commit hook it will perform all tasks before committing. This can lead to a merge conflict if any of linters updated file contents. In order to fix it, I'll try to perform the last step in the post-commit hook. This isn't ideal since it might require more setup but I can't find any other solution ATM.
One possible solution that comes to mind is to have 2 tasks: lint-staged itself and the post task that will be called as a post-commit hook. This works well now but fails if the commit was aborted (for example, due an empty commit message).
It is still unclear how to handle git stash pop conflicts that will occur if the file has been auto-fixed during the lint. See #73

Hey @okonet. Is this branch safe to test out? ie. are there any glaring issues where I might lose data if I wanna check out this branch and maybe help test since I'm really excited about this feature 😊

Unfortunately, it is still a WIP but you can try it out and report issues. I would not use on your project's code though since it still may loose some data AFAIK.

Ok I'll see if I can use it some side projects rather than code at work 💃

@okonet , more detailed description: https://github.com/okonet/lint-staged/issues/62#issuecomment-299525019
Solution with npm scripts and bash scripts
  "scripts": {
    "stash-unstaged": "git stash save -k --include-untracked 'unstaged-stash' >> /dev/null",
    "pop-if-gst-clean": "./tools/pop-if-gst-clean.sh",
    "lint-staged": "lint-staged || (npm run pop-stash >> /dev/null && exit 1)",
    "pop-if-gd-clean": "./tools/pop-if-gd-clean.sh",
    "stash-linted": "git stash save 'linted-stash' >> /dev/null",
    "stash-pop-unstaged": "git stash pop stash@{1}",
    "stash-pop-linted": "git read-tree stash && git stash drop",
    "clean-lint-staged": "lint-staged >> /dev/null"
  },
  "//pre-commit": {
    "//reference-links": {
      "github": "https://github.com/okonet/lint-staged/issues/62#issuecomment-286830310",
      "stackoverflow": "http://stackoverflow.com/questions/13889242/26685296#26685296"
    },
    "//stash-pop-linted": "use `git read-tree` to resolve conflicts",
    "//clean-lint-staged": [
      "Re-run `lint-staged` for fixable style errors mistakenly recovered to be unstaged by `read-tree`",
      "NOTICE: Although they are fixed, you will see them when input a commit-message",
      "Side effect is it will auto-fix unstaged part in these staged files",
      "Feel free to remove this cmd if you don't want the side effect or just feel adventurous",
      "If so, don't be surprised when you see unstaged&fixable style errors after commit"
    ]
  },
  "pre-commit": [
    "stash-unstaged",
    "pop-if-gst-clean",
    "lint-staged",
    "pop-if-gd-clean",
    "stash-linted",
    "stash-pop-unstaged",
    "stash-pop-linted",
    "clean-lint-staged"
  ]

Wowsers, I had no idea this was going to be such a massive headache-issue! Still, it looks like there's been some really decent progress, what's the status of this at the moment? It's working with Linux and macOS, but not Windows (is that the gist of it?).
Also, you guys are now responsible for the 1 recommended integration strategy with Prettier.io (https://prettier.io/docs/en/precommit.html)

It's not that simple. You can't git stash pop without conflicts if you've modified index. Please take a look at the implementation.

@okonet  Please see https://github.com/okonet/lint-staged/issues/62#issuecomment-411964870, git stash pop just works.
Sure, We should take care the conflicts ourselves after popped.

git stash pop just works.

I have a different experience with it.

@sudo-suhas @luftywiranda13 this is shaping out well. Do you mind testing and reviewing it? At this point I would consider it done but I'd like to clean up code a bit more. Also, it feels like before we restore working copy we need a more robust way of detecting the need to do so. Thoughts?

@sudo-suhas should we remove Node v6 support as a separate PR so tests for this one won't be affected? I'd like to release this as v8.0 though...

(continuing from https://github.com/okonet/lint-staged/issues/62#issuecomment-420022062)

Not sure what you trying to achieve but you didn’t try to commit partially staged files so it worked as expected

Yes, if you see my output there:
❯ git status
On branch use-jss
Your branch and 'origin/use-jss' have diverged,
and have 3 and 1 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	modified:   src/components/Footer.tsx
	modified:   src/components/Header.tsx
	modified:   src/components/HeaderMobileNavModal.tsx
	modified:   src/components/RootLayout.tsx

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   package.json
	deleted:    src/App.vue
	deleted:    src/names.js
	modified:   src/pages/_document.tsx
	modified:   src/styles/theme.ts

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	src/App.vuee src/namess.js

The Changes to be committed are my staged changes (whole files in this case, I haven't tried partially staged files).
There are deleted unstaged changes there too, which are somehow reset by lint-staged after the commit completes.
Let's test this by combinations of the following:

have unstaged deleted files
unstaged renamed files (has both deleted and untracked)
untracked files (are not a rename)
modified files

and with those changes, do one of each

add all changes
add some changes
add only changes of one type
etc

This is how I'm finding that it isn't working like I've described in the other thread.

In the simple case where I have only modified changes, this seems to work fine so far. Just try the other cases above.

In the described above case it won’t do anything different from before so I’m not sure why you experiencing it. Please make sure you’re at beta1 but I think you are.
Also I will try to add your cases as test cases but feel free to jump on and modify tests yourself so we aren’t playing broken phone game.

I just ran into a commit leaving a header.tsx.rej file behind, containing
diff a/src/components/Header.tsx b/src/components/Header.tsx	(rejected hunks)
@@ -478,4 +483,6 @@ function styles(theme: Theme) {
-                  background: Color(navyBlue).darken(0.1).string(),
-                },
-              },
-            },
+                  background: Color(navyBlue)
+                    .darken(0.1)
+                    .string()
+                }
+              }
+            }

What does that mean? I haven't tried the latest beta yet.

I hit this one once myself. This probably means that the hunk was reformatted although it was also edited but not selected for commit. During the restoration process it could not cleanly apply both edits so it put it into rej file. I’m not sure yet how to detect such cases. Can you provide me with exact actions you did so I could try creating a test case?

Can you provide me with exact actions you did so I could try creating a test case?

I'm flying through commits at the moment, but I'll see if I can make a small reproduction the next time I encounter it.
On another note, I just tried beta.2, but I still see the confusing message in the output:
  ↓ Stashing changes... [skipped]
    → No unstaged files found...

I'm confused because my expectation is that it will tell me it found unstage changes to stash (in fact this is what it does and is working), but the message makes it seems like I have no unstaged changes to stash (which isn't what actually happens).

I'm confused because my expectation is that it will tell me it found unstage changes to stash

I see why you're confused and I'll update the copy to match the behavior. Which is at the moment: if there are no partially staged files, do not perform stash / restore.

Have you considered solving the requirement of linting/formatting only staged files without stashing? This tool might serve as a showcase: https://github.com/hallettj/git-format-staged/blob/master/git-format-staged

There is #62 with related discussions. Let’s keep comments here related to the work in this PR please.

@sudo-suhas latest Windows tests fail with some strange snapshot differences. Could you please try running locally? https://ci.appveyor.com/project/okonet/lint-staged/builds/19651280/job/71b9px4salpqsokj

@trusktr I've resolved this in fa492abb931043a5ebf8dc2f93ff89a928c60d99

I am able to see the same behavior on my Windows system.  The error message is coming from here - https://github.com/okonet/lint-staged/blob/fa492abb931043a5ebf8dc2f93ff89a928c60d99/src/resolveTaskFn.js#L63-L65

Hmm, I’m not sure how to test it then. Ideas?

Could we reduce the scope of changes introduced? I know that's easier said than done but in all fairness, this PR does a lot of changes.

It does only required changes. There is no way we can reduce the scope I’m afraid.

Finally all tests are green on both linux and Windows!

@sudo-suhas can you please test the beta version on Windows? I believe your comment regarding git ops is concerting with tests and I'm able to run tests on CI and my local windows machine. Although I'm struggling the CRLF issues on it so I couldn't yet test the package in real life scenario (BTW what's the setup you're using to deal with CRLF issue?)

@trusktr I've added a few tests cases for handling of renamed and untracked files in https://github.com/okonet/lint-staged/pull/75/commits/da2adf9a066749bcea74910a86d9de9791f602e5.
Can you please take a look and let me know if this is what you'd expect? It looks right to me.


Add getting started section to readme

Readme Update
adding getting started section to readme

Added getting started section on readme file


Nesting Rule Validation

Hello,
Regarding the commit for version 4.0.1, the nesting rule validation had an impact on the verification of selectors that start with -
Version 4.0.0
/^&([^A-z]|$)/.exec(selector)
Version 4.0.1
/&([^\w-]|$)/.exec(selector)
Considering this change, the first one ignored all letters, while the new one ignores all Word Character. However, the new regex also ignores the -.
As a consequence of the  - being ignored, the postcss-nexting cannot be used with a CSS Loader containing the camelCase option dashes (for the mapping between the className and the selector).  For example:
.list {
    list-style-type: none;

    &-item {
        display: flex;
        justify-content: space-between;
    }
}

Taking into consideration the example, the css classname list-item is ignored.
Therefore, is there any reason for ignoring the - character? If not, I would recommend changing the regex for the following one:
/&([^\w]|$)/.exec(selector)

@vasco-santos because it is not possible by spec (http://tabatkins.github.io/specs/css-nesting/)
You can use https://github.com/postcss/postcss-nested if you want this behaviour.

Neverthless, this is a huge breaking change from the consumer perspective. This should have been a major and is causing some of our projects to fail. Please follow the semver semantics next time.

https://github.com/jonathantneal/postcss-nesting/blob/master/CHANGELOG.md#400-may-20-2017
It was a bug. I’m sorry you found a way to exploit the bug.

The major breaking change in v4 was to only respect valid nesting. It seemed against the spirit of semver to push major releases for fixing exploitable bugs.


Allow Signup

On the auth0 hosted login widget, allow signups. Point signup link to the signup page produced in #396

 Self signup


Migrate the CEP Invisible Extension Panel to UXP

Take this sample CEP panel
Make use of our CEP Getting Started Guide
Migrate the panel to UXP
Write a guide and/or blog post about the experience

@ErinFinnegan I can handle this one. Please let me know if no one else is already have started this.

Go for it!

@ErinFinnegan Sure, I have 2 pull requests waiting, I will start this right after finished those:)

Are your other two PRs waiting for approval? If so provide the links and I’ll see what I can do…

@pklaschka @ErinFinnegan im staring working on this. Please let me know if you have any suggestion or tip.

I have assigned the issue to you now :-)
I don't have any particular suggestions, but please let us know if you need anything or have any questions!
Thanks,
Pablo

@pklaschka Sure Thanks :)

@pklaschka @ErinFinnegan
Hi There,
I have already done this and made a pull request . Please let me know if a blog post or guide is needed.
Thanks


Fix typo in Czech translation

Summary of the Pull Request
This PR fixes the typo in Czech translation mentioned in #17752.
References and Relevant Issues
#17752
Detailed Description of the Pull Request / Additional comments
Correct translation for the word "Terminal" is "Terminál". See the Google Translate result.
Also, this word is already translated as "Terminál" in other strings. For example the app name:
<data name="AppShortName" xml:space="preserve">
  <value>Terminál</value>
  <comment>{Locked=qps-ploc,qps-ploca,qps-plocm}</comment>
</data>

Validation Steps Performed
None.
PR Checklist

[x] Closes #17752
[ ] Tests added/passed
[ ] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[ ] Schema updated (if necessary)

<data name="AppDescription" xml:space="preserve">
  <value>Nová Terminál Windows</value>
</data>

By the way, this string also looks suspiciously incorrect, but I did not fix it as a part of this PR.

Thanks for the initiative trying to fix this! Alas, our localization story is still a little painful. We can't just fix localizations directly in our repo yet, since they're still generated by an internal pipeline. I'm pretty sure we still need to submit these proposed fixes through that pipeline, and then wait for them to ingest those updates.
I bet that having an exact diff of what to fix should make this a lot easier for the loc team. Thanks!


Action and attack input get stuck

Not sure if this is related to my peripherals (magic keyboard and MX master 3s), but whenever I do an activity in quick succession, the actions feel like they get in a queue of some sorts and it's impossible to stop. Some examples:

The worst one by far - Attacking. If I get into a fight and press the attack button quickly, the character gets stuck attacking exactly how many times I pressed the attack button and cannot stop it.
Another clear one is repairing equipment. On Windows I was smashing the repair button quickly, but on Mac everything gets stuck for a couple of seconds when I do that.

Anyone else encountered this before? I wonder if it has something to do with how input is handled on MacOS

I briefly tested this last night on regular laptop setup (keyboard/trackpad) and could not reproduce this in 0.215.24 (latest stable)
Did this start happening recently or has it always been like this for you? Is there anything of note in the log files?

@razvanilin are you using a tiling manager like rectangle or magnet? they tend to interact badly with games like this. I was slowly going mad with the same issue until i added valheim to the exclusion list.

@stvnksslr omg that's it! I was using magnet and I just tried closing it. Works super nicely now 👌
I'll close this as it doesn't seem to be related to the game


0.8.0 runs the sketch twice

Updated to 0.8.0 on debian jessie (bunsenlabs hydrogen).
alt-ctrl-b or through the menu runs the sketch twice.

had the same problem, reinstall works!


fix(explore): Edit dataset save button position

SUMMARY
Closes #12587
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
BEFORE:

AFTER:

TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue: #12587
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12604 (2f3749a) into master (9771b82) will decrease coverage by 3.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12604      +/-   ##
==========================================
- Coverage   66.76%   63.11%   -3.65%
==========================================
  Files        1015      486     -529
  Lines       49642    29969   -19673
  Branches     4970        0    -4970
==========================================
- Hits        33141    18915   -14226
+ Misses      16378    11054    -5324
+ Partials      123        0     -123

Flag
Coverage Δ

cypress
?

javascript
?

python
63.11% <ø> (-0.86%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-11.48%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/schemas.py
93.40% <0.00%> (-6.05%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
86.55% <0.00%> (-5.47%)
:arrow_down:

... and 550 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #12604 (2f3749a) into master (9771b82) will decrease coverage by 3.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12604      +/-   ##
==========================================
- Coverage   66.76%   63.11%   -3.65%
==========================================
  Files        1015      486     -529
  Lines       49642    29969   -19673
  Branches     4970        0    -4970
==========================================
- Hits        33141    18915   -14226
+ Misses      16378    11054    -5324
+ Partials      123        0     -123

Flag
Coverage Δ

cypress
?

javascript
?

python
63.11% <ø> (-0.86%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.24%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/presto.py
70.56% <0.00%> (-11.48%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/schemas.py
93.40% <0.00%> (-6.05%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
86.55% <0.00%> (-5.47%)
:arrow_down:

... and 550 more

Continue to review full report at Codecov.

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

tested manually 🟢

tested manually 🟢


An app opened from inside Terminal stays behind Terminal (but above other apps)

Windows Terminal version
1.19.11213.0
Windows build number
10.0.19045.4412
Other Software
tmux 3.4 inside bash 5.2.21(1)-release (x86_64-pc-linux-gnu) inside Ubuntu 24.04 WSL (wsl.exe version 10.0.19041.4355)
windows terminal set to maximized focus
~/.tmux.conf containing
set -g prefix F1
set -g mouse on
set -g allow-rename off
set -g status off
bind-key -T prefix  M-7  resize-pane -x 72
bind-key -T prefix  M-8  resize-pane -x 80
bind-key % set-environment -F PWD "#{pane_path}" \; split-window -h -c "#{pane_path}"
bind-key '"' set-environment -F PWD "#{pane_path}" \; split-window -c "#{pane_path}"

Steps to reproduce
run any app, such as '/mnt/c/Program Files/Sublime Text 3/sublime_text.exe'
Expected Behavior
the app opens in front. this works correctly if the command is run in bash directly.
Actual Behavior
the app opens in front of windows other than windows terminal, but behind windows terminal

i fixed this by blanking ~/.tmux.conf, reloading tmux source, and then replacing the contents. various restarts (of tmux, windows terminal, windows) did not fix this. modifying launch mode from maximized focus to normal did not fix this.

it did not stay fixed

Does this only happen in WSL /?

this happens specifically in tmux in wsl. for example, i open command prompt, run mpv.exe file; this bug does not occur. i open command prompt, run bash, then run mpv.exe file; this bug does not occur. i open command prompt, run bash, run tmux, then run mpv.exe file; this bug does occur.
this bug also occurs if i use windows terminal instead of command prompt.
i file this bug here instead of https://github.com/tmux/tmux - this is an issue with windows, not tmux.
maybe i should file in https://github.com/microsoft/WSL? but they state to please file UI/UX related issues here.

maybe i should file in microsoft/WSL? but they state to please file UI/UX related issues here.

Generally, yes, but because WSL interop is involved, let's file the bug over there. Could you file the bug on their repo? Thanks