Add support for wt.exe to run commands in an existing Terminal Window

Description of the new feature/enhancement
I have been playing around with Jetbrains Rider, and when i start a console app with that IDE, it runs the console window inside a docked window in the IDE.
So what i was thinking. How cool would it be, if Windows Terminal allows external applications to start a new Console window in the currently running Windows Terminal instance.
That way whether its VisualStudio or Rider, those IDE's can be configured to start a new Console window inside the Windows Terminal instance.
The way i see this working is: I press F5/ctrl-F5 in visual studio, and instead of opening a new cmd console window, a new tab appears in my running Windows Terminal instance.

Yes, please. There's a Visual Studio extension, that lets you open command line in the current project folder. I set it to launch wt.exe, and it always creates a new window, but I'd love if I could pass a parameter to wt.exe, so that if Terminal is already running, it would be activated a new tab would open there instead.

Thanks for the request! I thought we had a backlog item for "allow remote control of a terminal" (like: wt.exe could --remote to control another open instance and add tabs or whatever), but it looks like we don't.
This is now that issue. Triaged into backlog.
/cc @zadjii-msft: I may be wrong in not finding a "remote control" issue

Partially supported by #2080.

This was briefly mentioned in this spec

Future considerations

These are some additional argument ideas which are dependent on other features
that might not land for a long time. These features were still considered as a
part of the design of this solution, though their implementation is purely
hypothetical for the time being.

Instead of launching a new Windows Terminal window, attach this new
terminal to an existing one. This would require the work outlined in
[#2080], so support a "manager" process that could coordinate sessions
like this.

This would be something like wt --session [some-session-id] [commands], where --session [some-session-id] would tell us that
[more-commands] are intended for the given other session/window.
That way, you could open a new tab in another window with wt --session 0 cmd.exe (for example).

list-sessions: A command to display all the active Windows terminal
instances and their session ID's, in a way compatible with the above
command. Again, heavily dependent upon the implementation of [#2080].

Which yea is part of #2080, but I don't think has it's own issue.

Wow, I was just thinking about "starting a new program/task in any existing windows terminal window" or a "single instance mode" to populate a WT window with multiple tasks via CLI would be great.
But something like sessions would be even better and more flexible.
But I admit that I'd prefer a "quick and dirty" single instance mode in the near future over a flexible session management in the distant future (as I could use it sooner than later).

So, I wanted to report an issue I've found that seems to be the same as "https://github.com/microsoft/terminal/issues/4942"  - it was closed as a duplicate of this issue, but I don't believe that it truly is. Because the docs say (quoted from one of the closure remarks on the other issue)

The docs are correct here:
Opens a new tab with the given customizations. On its first invocation, also opens a new window. Subsequent new-tab commands will all open new tabs in the same window.

However, say I go to start and type "wt", and get myself a new console. Then I type "wt new-tab "PowerShell"", that will start a second wt window with the desired tab, while waiting at the first window for me to close the new window (process starts and the terminal is waiting for process end). So I can't go back to that "first invocation" to issue additional commands. And if I go to the second-launched WT console, and again type in wt.exe new-tab, I will get a third new window, not a second new tab in the already-launched second session. And in no way have I found yet with the command line inputs to split a pane in an existing window. Every time I issue split-pane it behaves the same as new-tab, and I get an additional window.
Replicate:
Start > wt (opens new Windows Terminal window)
wt.exe new-tab (will start a second new Windows Terminal window. If your first terminal was running PowerShell, that session is now waiting for this second new window to close - trying to "start-process" with "-nonewwindow" does not help)
Since first terminal window is now waiting for second to close, we cannot give additional commands there, going to the second window and issuing "wt new-tab" gets a third window. Trying "wt split-pane -H -P "PowerShell" in any existing window, also, does not add a split pane in any current window, it opens yet another window with the split-pane settings requested.
Because of this behavior, at this point, you cannot go back to the initial processor to issue additional WT commands. And if you go to the secondly-launched terminal window, and issue again wt new-tab, you'll get a third new window, and a second window waiting on the third to close.
I tried also starting with Command Prompt. It will start a new window, and will NOT wait for that window to close. So I AM able to return to that initial processor to try issuing additional commands. But, they behave the same. Additional new-tab commands bring new windows, not just new tabs in existing windows.
So I would pose here that as described in the closed issue your "new-tab" and "split-pane" features are operating entirely contrary to their documented conditions. And contrary to your closure remarks on the above-linked issue, it and my comment here I don't believe to be a dupe of this feature request, but an ask to make the feature behave as described in your documentation. That would make this not a feature request but a bug fix. As either the existing feature's behavior is incorrect, or the document is not describing it's expected behavior correctly. By reading your document, I expect that the first time I issue "wt new-tab" I will get a new window. And every subsequent time I issue this same command, it will open in an already-existing window as this is what you tell us it will do right now per the quote from the doc above, and it does not do this that I can verify in any way or make happen whatsoever.
Thanks!
Nathan M

Hey so I literally just went and updated the docs on this. You can check out the PR here.
Basically, every time you run wt, it's going to create a new window first. Always. This thread right here is the thread tracking adding support to allow the user to say something like wt --inTheCurrentWindow split-pane.
These subcommands are all supposed to run as a single commandline invocation. wt new-tab ; split-pane ; new-tab will open one window with two tabs, and the first tab has a split in it. As called out in the spec:

Future considerations

These are some additional argument ideas which are dependent on other features
that might not land for a long time. These features were still considered as a
part of the design of this solution, though their implementation is purely
hypothetical for the time being.

Instead of launching a new Windows Terminal window, attach this new
terminal to an existing one. This would require the work outlined in
[#2080], so support a "manager" process that could coordinate sessions
like this.

This would be something like wt --session [some-session-id] [commands], where --session [some-session-id] would tell us that
[more-commands] are intended for the given other session/window.
That way, you could open a new tab in another window with wt --session 0 cmd.exe (for example).

RE: powershell waiting for a WT window to close - you'd probably be interested in this section of the UsingCommandlineArguments doc that was also recently added.

Awesome! Thanks a bunch!
So, in the current iteration, there's no way in an existing window to split a pane into a new command processor? For example, say I wanted to in my existing powershell window, split-pane and bring up an ubuntu prompt in the horizontal space below? I'd have to chain those commands up to build a new window at command line, essentially?

Yes I have keybindings to do a split-pane, but I've yet to figure out how to split a pane into a particular processor via keybindings.

You can actually do something like
{ "command": { "action": "splitPane", "split": "vertical", "commandline": "powershell.exe" }, "keys": "alt+shift+plus" },

and that'll open your default profile, but with the commandline "powershell.exe" as opposed to whatever the profile's usual commandline is

Here is my feedback about this requested feature. I want to do something like console fork - to start a new pwsh session on a new tab, but I'd like it to have the same current folder ($pwd). Right now when I'm starting a new pwsh tab the Windows Terminal takes some hardcoded initial folder location. If I specify it to use %CD% instead, it doesn't pick up any changes to $pwd anyway. Even if I change [Environment]::CurrentFolder new pwsh session doesn't pick it up.
So I was hoping I could make a workaround script that would start wt.exe passing it working directory = $pwd and argument to open new tab in the same window. And I just found this thread.
Could this new feature allow my use case as well?

@FallenGameR What you're looking for is tracked by #3158

@zadjii-msft it seems @FallenGameR is asking for a command line (wt.exe) solution while #3158 seems to be solely about the CTR+T key combination unless I'm mistaken.

My ask can be implemented in several ways. I don't really have a preference, as long as some solution exists. As of now it looks like wt.exe is not your regular process and calling it has some quirks - e.g. Start-Process wt.exe -Verb RunAs don't work.
But in case wt.exe would behave like a normal callable process and new-tab --inCurrentTerminal was implemented, that would actually do the trick for me. I can script around that. Plus such kind of implementation doesn't seem to require some protocol agreement across third party terminal implementations.

I have been waiting for this feature for a long time. She is necessary.
Cool, if the terminal can be run with administrator rights from any desired folder.

This would be exactly what I need although I could maybe script my way around this issue with AutoIt. Still would make my life easier.
When can we expect this feature to arrive via Windows Update?

@mreymann well, this feature hasn't been implemented yet, so certainly not for a while. It gets a mention in the spec in #7240, but a spec is still a long ways from an implementation.
I'd follow this issue for updates. When we get around to implementing this, we'll close this issue.

In fact my stupid guess was, that wt new-tab should exactly this, but it open every time a new window.
This is especially annoying when using the "Open in Windows Terminal" - every time a new window.

A multi-tab terminal, without the ability to open a new tabs in a running instance of the terminal from outside and no option to move tabs between terminal instances is like a wheel with four edges 🙄

Guys, is there some progress or news? I can't sleep well because I'm still waiting for this feature. Every day I open this page, see it still "Open" and get disappointed. All the features this application has are completely useless without this main one.

This would be brilliant working with vscode as having it spawn a new window is annoying as I have to re-dock it to the side of my screen everytime I start the debugger.
I'm the same with @bmaehr in that I assumed nt/new-tab would do this already.
Browsers do this all the time, so it can't be so hard /s

@xcme The last branch I pushed to  is literally the spec for this feature. It's probably 50% covered by the spec in #7240, and 50% covered by the one I'm working on now. So we'd appreciate patience while we work on hammering out the design, and feedback on the spec (once it's out for review).

To all the folks following this issue losing sleep waiting for updates, the spec is out for review. You may resume losing sleep over (whatever previous thing kept you up at night).

Could this also be used to redirect consoles spawned by AllocConsole() API? Currently, when I need many of them, I have a screen full of cmd windows, which could be easily cleaned up by this terminal. I need to see the title of each console spawned in grid view though.

@ralaul What you're looking for will actually be covered better by #492. That issue covers setting an application as the default terminal emulator on Windows, which should cause AllocConsole calls to spawn that application as a window instead of the vintage console.

I have a kind of a suggestion that may solve at least some of the issues mentioned above, and in related issues and docs. Why not have a command-bar like we have eg in VSCode. It can be hidden by default, but have a keybinding to trigger it, then write in that command box something like new-tab -p MyProfile No need to invoke "wt" again at all, simply send the command via this command box. It woud then trigger same thing that keybinding triggers, but it offers more flexibility, as we can't prepare hundreds of keybindings for every occasion, and we CAN type a slightly different command in this "run box" inside a working WT session.
This does NOT solve opening tab from 3rd party, like from Visual Studio. But it does solve managing tabs and panes from within the already running wt session.

It already exists, as Ctrl-Shift-P (I just found this myself recently).

I have a kind of a suggestion that may solve at least some of the issues mentioned above, and in related issues and docs. Why not have a command-bar like we have eg in VSCode. It can be hidden by default, but have a keybinding to trigger it, then write in that command box something like new-tab -p MyProfile No need to invoke "wt" again at all, simply send the command via this command box. It woud then trigger same thing that keybinding triggers, but it offers more flexibility, as we can't prepare hundreds of keybindings for every occasion, and we CAN type a slightly different command in this "run box" inside a working WT session.
This does NOT solve opening tab from 3rd party, like from Visual Studio. But it does solve managing tabs and panes from within the already running wt session.

@luxzg - what you are describing is a command line mode of command palette - you can read more about it here: https://docs.microsoft.com/en-us/windows/terminal/command-palette#command-line-mode

Well I couldn't wait, so I rolled my own solution.  See https://cadayton.keybase.pub/PSGallery/Scripts/psConsole.html
At work I have over 537 different potential login combinations of ssh/psremote/web interfaces.  So I don't see a hierarchical menu system being useful at this scale.

Checklist of work that needs to be done, taken from TODOs in the code in the current branch:

[ ] Peasant windows need to raise the WindowActivated event when they're activated
[ ] Peasant needs to get it's CWD and pass that to the Monarch in ProposeCommandline
[ ] When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.
[ ] Monarch::ProposeCommandline needs to return a structure of { shouldCreateWindow: bool, givenID: optional<uint> } (names will come in a follow-up)
[ ] The monarch needs a better way of knowing who to default to before the first window is activated. Currently, it just uses "the first peasant in the map" and that's wrong. We need to somehow tell the monarch which peasant they are when they're elected
[ ] Add tracelogging to pretty much every part of the election, commandline proposal and handling
[ ] Add a common header in src/inc/ for windowing constants, like UseNewWindow=-1; UseCurrentWindow=0; etc. It needs to be there, so both remoting.dll, TerminalApp and WindowsTerminal can all reference it.
[ ] If we fail to open the monarch, then they don't exist anymore! Go straight to an election.
[ ] At any point in all this, the current monarch might die. We go straight to a new election, right?
[ ] if the targeted peasant fails to execute the commandline, we should create our own window to display the message box.
[ ] Tests on tests on tests

Punted to a follow-up

[ ] Actually use WT_SESSION to resolve the "current window", not just the MRU window

Just trying to keep track of all the TODOs I have scattered and which ones are relevant to this feature, vs other parts of projects/5.

Checklist of work that needs to be done, taken from TODOs in the code in the current branch:

[ ] Peasant windows need to raise the WindowActivated event when they're activated
[ ] Peasant needs to get it's CWD and pass that to the Monarch in ProposeCommandline
[ ] When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.
[ ] Monarch::ProposeCommandline needs to return a structure of { shouldCreateWindow: bool, givenID: optional<uint> } (names will come in a follow-up)
[ ] The monarch needs a better way of knowing who to default to before the first window is activated. Currently, it just uses "the first peasant in the map" and that's wrong. We need to somehow tell the monarch which peasant they are when they're elected
[ ] Add tracelogging to pretty much every part of the election, commandline proposal and handling
[ ] Add a common header in src/inc/ for windowing constants, like UseNewWindow=-1; UseCurrentWindow=0; etc. It needs to be there, so both remoting.dll, TerminalApp and WindowsTerminal can all reference it.
[ ] If we fail to open the monarch, then they don't exist anymore! Go straight to an election.
[ ] At any point in all this, the current monarch might die. We go straight to a new election, right?
[ ] if the targeted peasant fails to execute the commandline, we should create our own window to display the message box.
[ ] Tests on tests on tests

Punted to a follow-up

[ ] Actually use WT_SESSION to resolve the "current window", not just the MRU window

Just trying to keep track of all the TODOs I have scattered and which ones are relevant to this feature, vs other parts of projects/5.

When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.

Is the use of "peasant" a technical synonym for "user", i'm lost. 😁

When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.

Is the use of "peasant" a technical synonym for "user", i'm lost. 😁

Nope, that's a reference to an implementation detail. You can refer to #5000, #7240, #8135, #8171, #8607 for more details.

Nope, that's a reference to an implementation detail. You can refer to #5000, #7240, #8135, #8171, #8607 for more details.

When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.

Is the use of "peasant" a technical synonym for "user", i'm lost. 😁

We also elect monarchs... it's best to not think too hard ;)

When a peasant is handling a commandline, switch to the provided CWD before running the commandline, then pop back to the starting one.

Is the use of "peasant" a technical synonym for "user", i'm lost. 😁

We also elect monarchs... it's best to not think too hard ;)

Just a taste:

Just a taste:

sweet

sweet

If someone needs the commands to create a new tab (and not open a new window) from a context menu item are:
(if you are already in the directory):
wt -w 0 nt
(and if you click on the directory):
wt -w 0 nt -d %1
You can add these commands in the respective registry of each item (or in a new one)

🎉This issue was addressed in #8898, which has now been successfully released as Windows Terminal Preview v1.7.572.0.🎉
Handy links:

Release Notes
Store Download

When will this be in the stable release?

@zeroxia Probably in about a month.

This is an awesome feature, and I'm really glad to see it land. But one thing from the original request that I was really looking forward to was the ability to run an arbitrary command in its own pane. Not an existing profile, but a one-off console executable.
So, for example, if I start a Jupyter Notebook server using jupyter notebook, it takes over the current console window for its logging. I can put the output in a new pane or tab by opening the pane, cd to the directory I was in in the original pane, then running jupyter notebook. But what I'd really like to be able to do would be something like wt -w 0 split-pane -d $env:CWD -exec jupyter notebook.
Did I miss a way to do this that already exists, or is this something that will be added later (or is it a part of the request that you've rejected? 🙁) Given that this issue has been closed, is there somewhere else I should be following to track progress of that part of the request?

Hmm, as a gross hack, I could add a profile
            {
                "guid": "{ca1cd762-2796-4b95-a2af-a9bf790eb9ca}",
                "name": "Hack",
                "commandline": "%HACK_COMMANDLINE%"
            }

and then do $env:HACK_COMMANDLINE = "my_command"; wt -0 sp -p Hack.
But I really hope this isn't the best option available to me...

I can't seem to run wt commands from bash 🤔

I can't seem to run wt commands from bash 🤔

To run Windows executable from WSL you need to add the .exe extension explicitly. So wt.exe should work

@mveril @lfr

To run Windows executable from WSL you need to add the .exe extension explicitly. So wt.exe should work

That depends. If you have installed Terminal through the Windows Store running wt.exe does not work. And yes, that's even though which wt.exe retuns a valid path to the C: mount point
$ wt.exe
# noting happens, but also no error
$ which wt.exe
/mnt/c/Users/<UserName>/AppData/Local/Microsoft/WindowsApps/wt.exe

Naturally, running cmd.exe /c wt does work, but that was kinda expected and is a really ugly hack...

Thanks, isn't the store the "official" way to install Windows Terminal? What's the other way to install it that wouldn't cause this issue?

I'm alittle confused that it's closed issue; i've discoverd this one after submitting the feedback in https://github.com/microsoft/terminal/issues/9368;  I think it's related and perhaps this should be still open?

[12:14:33][pigpen@box:~]$ which wt.exe /mnt/c/Users/<USER>/AppData/Local/Microsoft/WindowsApps/wt.exe [12:15:03][pigpen@box:~]$ strace wt.exe execve("/mnt/c/Users/<USER>/AppData/Local/Microsoft/WindowsApps/wt.exe", ["wt.exe"], 0x7ffff5c7a1b0 /* 24 vars */) = -1 ENOEXEC (Exec format error) strace: exec: Exec format error +++ exited with 1 +++

@mreymann Yeah, this is caused by this AppContainer isolation layer of Appx Packages (Microsoft Store apps) and how their executables are placed in the %LOCALAPPDATA%\Microsoft\WindowsApps folder. The files in there both are and are not there or at least are not really executable, but the Windows OS does some weird magic trick to actually start the correct binary from wherever the App is actully installed. Which is why starting the exe from a windows-shell starting point works, whereas from a WSL2-starting point it does not.
Would be interesting whether the technology used in WSL1 leads to this actually working, or not...

If someone needs the commands to create a new tab (and not open a new window) from a context menu item are:
(if you are already in the directory):
wt -w 0 nt
(and if you click on the directory):
wt -w 0 nt -d %1
You can add these commands in the respective registry of each item (or in a new one)

this really works it open a new tab, the problem is the directory was reset,.. hoping that I open a new tab, it will be at the same directory in my working project.

@BroJenuel

The first case was a modification.
The second one I had to create.

And what would the commands be to open a new tab from within the terminal itself?

wt -w 0 nt

@zadjii-msft thanks, but it doesn't seem to work from bash (Terminal Preview) 🤷♂

Ah, from WSL you'll need:
cmd.exe /c "wt.exe" -w 0 nt

Execution aliases do not work in WSL distributions. If you want to use wt.exe from a WSL command line, you can spawn it from CMD directly by running cmd.exe. The /c option tells CMD to terminate after running.
Also, you can read this in the docs

wt -w 0 nt

But this works only from with in cmd tab window.. This does not work if you issue this command from say within powershell tabbed window.

But this works only from with in cmd tab window.. This does not work if you issue this command from say within powershell tabbed window.

🤔

Beat me to the punch.  Yes, it does work in a PowerShell tab.  However, it does not work in a Windows Terminal window running as administrator (see #9628).

For those who are kinda new to this: here is how you can do it the easy way.

Open Windows Terminal.
Open Settings.
Checkout this section in the startup menu.

Select as I did.
Test by clicking "Open in Windows Terminal" elsewhere.
Thanks Microsoft for adding this to GUI)

For those who are kinda new to this: here is how you can do it the easy way.
1. Open Windows Terminal.

2. Open Settings.

3. Checkout this section in the startup menu.
   ![image](https://user-images.githubusercontent.com/42899786/153727389-56f004b6-cd7b-4b35-9531-ef2227e28638.png)

4. Select as I did.

5. Test by clicking "Open in Windows Terminal" elsewhere.
   Thanks Microsoft for adding this to GUI)

Neither "Attach to the most recently used window" nor "Attach to the most recently used window on this desktop" work for me on Windows 11.  I am not using the Preview version of Windows Terminal.  Any idea what's up?

For those who are kinda new to this: here is how you can do it the easy way.
1. Open Windows Terminal.

2. Open Settings.

3. Checkout this section in the startup menu.
   ![image](https://user-images.githubusercontent.com/42899786/153727389-56f004b6-cd7b-4b35-9531-ef2227e28638.png)

4. Select as I did.

5. Test by clicking "Open in Windows Terminal" elsewhere.
   Thanks Microsoft for adding this to GUI)

Neither "Attach to the most recently used window" nor "Attach to the most recently used window on this desktop" work for me on Windows 11.  I am not using the Preview version of Windows Terminal.  Any idea what's up?

Sorry, buddy, no idea. Try checking the above comments (like modifying the registry). I'll update my prev comment, cuz I'm on windows 10.

Are there plans to launch a new tab in an existing window, but to choose the window based on MRU order?

choose the window based on MRU order?

that's... already how it's supposed to work?

Are there plans to fix issue #9628 so I can actually use this feature?

choose the window based on MRU order?

that's... already how it's supposed to work?

That's not working for me when calling
wt.exe -w 0 nt
or
wt.exe -w 1 nt
via AutoHotkey when both AutoHotkey and both Windows Terminal windows are running as administrator.  It always opens the new tab in the first wt window opened.

Wondering if that is related to #9628.  Add this information to that bug so when it's evaluated for 1.14 this scenario will be included in that evaluation.


Fixed: iso20 SessionSetupReq payload Type

SessionSetupReq in iso-20 was sent with the incorrect payload type 0x8001

Hi, you mention in the title "SessionSetupReq", but you created a Pull Request related to the SessionStop within the PowerDelivery state. Can you recheck this?


Add nodeSelector and toleration scheduling support for submariner

What would you like to be added:
Add some option to deploy submariner pods on specific nodes using nodeSelectors and tolerations.
Why is this needed:
Some customers want to run infra services like submariner on specific infra nodes. Running all submariner services on specific nodes also makes it easier for customers to secure networking on most nodes.

This was done in https://github.com/submariner-io/submariner-operator/pull/2545, see also https://github.com/submariner-io/enhancements/issues/149. I think this just needs release notes before it can be closed.

It’s a bit late for release notes, closing.


TagGroup/TagItem: Invalid margin

🐛 Bug Report
It seems that the margin between the V3 Tag is not correct.
The margin should be 4px
🤔 Expected Behavior
The margin between tags should be 4px

😯 Current Behavior
The margin between tags is twice 4px making a gap of 8px.
💁 Possible Solution
Make sure the margin doesn't stack or that the total is 4px.
🔦 Context
XD review points out the margin error.
💻 Code Sample

🌍 Your Environment

Software
Version(s)

react-spectrum

Browser

Operating System

🧢 Your Company/Team
Adobe/CJM
🕷 Tracking Issue (optional)

No internal links, this is a public project

Just confirmed that the current margins are correct and match the latest designs.


Taskbar wont go to middle

When opened the task bar will go transparent but wont go to the middle, even when left open for a while. I found a way to fix this by opening taskbarx through the menu at the right side of the taskbar, but why doesn't it do this automatically?

@essakura Can you give the pre-release a try?
https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

Its perfect thank you!
On Thu, 21 May 2020 at 08:59, Chris Andriessen<EMAIL_ADDRESS>wrote:

@essakura https://github.com/essakura Can you give the pre-release a
try?
https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChrisAnd1998/TaskbarX/issues/282#issuecomment-631945163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APRKNEPYWAPF63IKDQWF6LDRSTNPHANCNFSM4M6C5FKA
.

I was also facing the same issue. Pre-release version <IP_ADDRESS> seemed to fix the problem.


Publish to OpenVSX

Hello, could this extension please be publish to Open VSX?
https://open-vsx.org/

Hi @ahussey-redhat - Thanks for your request. At this time, we have no plans to support publishing to 3rd party VS Code extension marketplaces. Our official extension is available at https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare.


⚠ RPC server - Astar has degraded performance

In 79810ac, RPC server - Astar ($ASTAR_RPC_URL) experienced degraded performance:

HTTP code: 429
Response time: 820 ms

Resolved: RPC server - Astar performance has improved in 94bf626.


Map 1403 CSC-UI NPM dependency updates

soem visible changes:

phase banner colour change see this
no yellow+red border in error summary. Now just red only. this
the underline below links is thinner even if the text is large.This is the same as on other dps pages like the 'add casenote' link on prisoner profile

@Michael Willis Thank you for PR-ing. I'm going to wait until everything else  in the pipeline is fully tested and deployed before I merge as it may be difficult to debug any errors if everything goes in together.


Adding extra functionality and refinements to !remind

Possible improvements have been discussed for the reminder command:

Repeating reminders
e.g. !remind "@Admins meeting in 5 minutes" every Sunday at 20:55
More natural time parsing
DM reminders
Allowing reminders in functional channels such as #dev-contribs which currently is disallowed for non-staff.

Adding a couple more enhancements:

Add reminder ID to the confirmation embed
Add the target datetime to the confirmation embed (in addition to the currently provided timedelta)

I seem to have forgotten to add also:

Jump link to original invoke msg

That was added by #466

Oh, very nice.

For scoping I'm going to split this into a couple discrete chunks:
Chunk the first (low hanging fruit)

Reminder ID in confirmation embed
Target datetime in confirmation embed
Expand whitelist for non-staff

Chunk the second (requires backend changes)

Repeating reminders
DM reminders

Chunk the third (converter change has broader implications)

More natural time parsing

For the more language time parsing feature, can we make use of parsedatetime?

we already have arrow as a dependency, so maybe we can make use of that?

we already have arrow as a dependency, so maybe we can make use of that?

That would do it too! Yes 👍

The points here other than "Repeating reminders" and "DM reminders" seem to have been completed or have their own tracking issues. I don't think repeating/dm reminders are super important so i'll close this and let anyone create separate issues for them if they have a use case.


Add sun position

Would you consider adding sun position information to this library, i.e. altitude and azimuth? See the docs at https://github.com/mourner/suncalc for an example. Feel free to close this issue if it's out of scope.

Closing this for the time being as I don't imagine this will be in scope for awhile.


"Comment file" and "Do not update commit status" are not always shown

Early I couldn't find those two options, a restart of Jenkins made them appear again.
See https://github.com/jenkinsci/ghprb-plugin/pull/33#issuecomment-142628889

:+1: Also seeing (or, not seeing, as the case is) this.

:+1:  works for me on one server, disappeared on another. Please fix

Also find for me

I wasted an hour on this.  I saw a reference to it and I thought, "Well, maybe I am not clicking the right place."  (Thanks Jenkins UI for being terrible).
+1 on this.

+1 on this! please!


Error messages: add new guidance on matching error message text to input label

What
Add new guidance on matching error message text to input label.
It'll go in the error message component guidance, just above the 'Be clear and concise' heading.
Other details:

it'll have its own heading
it'll replace the 3rd paragraph in the 'be consistent' section

Why
In a recent DAC audit they noted a usability issue with our error summary link text not matching the labels for inputs.
Here's the preview page that DAC tested:

https://govuk-frontend-pr-3503.herokuapp.com/full-page-examples/what-is-your-address

And here's the GitHub issue that was created based on the DAC audit report:

https://github.com/alphagov/govuk-design-system/issues/2801

While the issue DAC identified had more to do with old content for error messages in our GOV.UK Frontend review app not being updated, it pointed to a bigger gap in our guidance. We decided it would be best to expand our guidance on how exactly to match error messages to input labels.
This issue has a sibling issue that will add examples of error messages to the address pattern:

Update to addresses pattern to include more error examples

Who needs to work on this
David
Who needs to review this
Calvin, Charlotte
Done when

[ ] Content is drafted in this issue
[ ] PR is made with the changes
[ ] PR is reviewed by reviewers and team
[ ] PR is merged

@dav-idc is there anything I can do to move this along?

Here's my draft of the content @CharlotteDowns and @calvin-lau-sig7!
I'm going to re-assign this ticket to Charlotte now. 🙇♂
Add this directly above the 'Be clear and concise' section:

Match up error messages to labels
Error messages should directly include language from the question or fieldset label. This helps match up the error message with the form field for which it applies.
Here are some examples of label and error message pairs.
Example 1:

Label: ‘How many hours do you work a week?’
Error message: ‘Enter how many hours you work a week’
Example 2:
Label: ‘Address line 1’
Error message: ‘Enter address line 1, typically the building and street’

Remove this from the 'Be consistent' section:

~Use the question or form label in the error to provide context. For example, ‘Enter how many hours you work a week’ for ‘How many hours do you work a week?’~


Revert "Merge pull request #48445"

Details

#48445 fixed #47735. After completion of regression period for this PR, these changes were found to be causing #49525 likely due to new code changes from other PRs. Reverting #48445 seems to be the best option to fix #49525.
Fixed Issues

$ https://github.com/Expensify/App/issues/49525
PROPOSAL: https://expensify.slack.com/archives/C02NK2DQWUX/p1727302638734859?thread_ts=1727264968.921709&cid=C02NK2DQWUX
Tests

Test 1:

Log on to ND
"Reply in thread" on a message in a chat with User A
Send a reply in this thread
Click on "From User A" in the header to go back to the parent report action
Verify that there is no unread indicator shown in this parent chat

Test 2:

Log on to ND
Open any chat
Send a message
Mark this message as unread ("Mark as unread")
Delete this message
Send a message again
Verify there is no unread indicator shown in the chat

[x] Verify that no errors appear in the JS console

Offline tests

None
QA Steps

Same as Tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/b9e6b71d-a1eb-4ca2-a0ea-3812f065cf77

Android: mWeb Chrome
https://github.com/user-attachments/assets/3c8c4e27-ab2a-4508-bf42-03c600b1c52d
https://github.com/user-attachments/assets/aa6348ef-75b7-4505-b500-a006047f06be

iOS: Native
https://github.com/user-attachments/assets/1728f7da-124d-4bdc-99c1-466c63b9752a

iOS: mWeb Safari
https://github.com/user-attachments/assets/e08b689c-f6e9-47ab-ab72-36aeddeec0f0

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/b507bbe4-3f45-4a76-ae3f-e424b044b8eb

MacOS: Desktop
https://github.com/user-attachments/assets/c9980b5c-7764-4c54-b1ba-72c5650a9869

Reviewer Checklist

[X] I have verified the author checklist is complete (all boxes are checked off).
[X] I verified the correct issue is linked in the ### Fixed Issues section above
[X] I verified testing steps are clear and they cover the changes made in this PR

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[X] I checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[X] I verified tests pass on all platforms & I tested again on:

[X] Android: Native
[X] Android: mWeb Chrome
[X] iOS: Native
[X] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[X] MacOS: Desktop

[X] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[X] I verified proper code patterns were followed (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I verified that this PR follows the guidelines as stated in the Review Guidelines
[X] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[X] I verified that all the inputs inside a form are aligned with each other.
[X] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/8f1ced55-315f-4ca1-82af-cf95176933bd
https://github.com/user-attachments/assets/fec85072-fe3c-4962-97e4-32d16443fb5a

MacOS: Desktop

Straight revert looks good, two things though:

Can we get videos for Android mWeb confirming that the original bug #47735 isn't reintroduced by this? I see the test steps in the description, but we don't have the video.
Re: the lint errors, are you thinking we should merge with the error, or is there a PR actively in the works that fixes these (and we should HOLD on that)?

Thanks!

Added the video for Android mWeb.
I don't think there is a PR fixing that lint error.

Asking about the lint errors here - https://expensify.slack.com/archives/C01GTK53T8Q/p1727374729163949

Not an emergency, did not fix lint errors to keep this a clean revert. Discussed here - https://expensify.slack.com/archives/C01GTK53T8Q/p1727374729163949

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Detect color support

By using supports-color detects if stdout support ansi colors. This library also supports setting FORCE_COLOR=0 env variable to force not using colors.
Closes https://github.com/probot/probot/issues/551

Ok


Create new collection entry at user-defined path (maybe in a subfolder)

Currently I have path: "{{slug}}" in my collection config. I’d like to be able to do path: "{{fields.folder}}{{slug}}" where folder is an optional form field value that is set by the user. If they don’t specify a folder, it just puts the file in the top level folder of the collection.

@erezrokah
I have a problem with this implementation.
I have my repository with Hugo content. I managed to configure Netlify CMS at self-hosted Gitlab and I'm able to see all content from repository correctly. But whenever I' trying to edit existing entry or create new one inside existing subfolder it throws error "Example path is not a valid path".
As far as my tests go, it seems that path can't be made out of Capital letters, spaces or anything other than just lowercase letters. My configuration of collections:
collections:
  - name: pages
    label: Pages
    label_singular: 'Page'
    folder: content/pages
    create: true
    # adding a nested object will show the collection folder structure
    nested:
      depth: 100 # max depth to show in the collection tree
      summary: '{{title}}' # optional summary for a tree node, defaults to the inferred title field
    fields:
      - label: Title
        name: title
        widget: string
      - label: Body
        name: body
        widget: markdown
    # adding a meta object with a path property allows editing the path of entries
    # moving an existing entry will move the entire sub tree of the entry to the new location
    meta: { path: { widget: string, label: 'Path', index_file: 'index' } }

Could you please advice on how to correctly make configuration in this case.
As a result I just need an ability to create entries in any subfolders by just setting a path, just as described in post topic.
Thanks!

@ValeriyTen, the string widget is quite permissive in what can go into the path.
I recommend to use a pattern to enforce a valid path https://www.netlifycms.org/docs/widgets/#common-widget-options

@erezrokah
I managed to get any symbol into 'path' field to edit existing subfolders by configuring Netlify this way
collections:
  - name: pages
    label: Pages
    label_singular: 'Page'
    folder: content
    create: true
    nested:
        depth: 100
        summary: '{{title}}'
    fields:
        - label: Path
          name: path
          widget: string
          index_file: '_index'
          pattern: ['.*', "Insert"]
        - label: Title
          name: title
          widget: string
        - label: Body
          name: body
          widget: markdown

But I have one more problem. Whenever I need to create a new entry in any subfolder, I specify path for that entry and after publishing it creates in root folder, in my example it's "content" folder. How do I configure it then?

But I have one more problem. Whenever I need to create a new entry in any subfolder, I specify path for that entry and after publishing it creates in root folder, in my example it's "content" folder. How do I configure it then?

The supported way to handle nested collections and editing entries path is via the meta configuration as specified in the docs.
Regular fields (even if they are named path) won't get be regarded as fields for modifying entries path.

The supported way to handle nested collections and editing entries path is via the meta configuration as specified in the docs.

I changed my collection config to this:
collections:
  - name: pages
    label: Pages
    label_singular: 'Page'
    folder: content
    create: true
    nested:
        depth: 100
        summary: '{{title}}'
    fields:
        - label: Title
          name: title
          widget: string
        - label: Body
          name: body
          widget: markdown
    meta: { path: { widget: string, label: 'Path', index_file: '_index', pattern: ['.*', "Error"] } }

I managed to create a new entry in subfolder and to move created entry to another folder, but when I try to edit 'Body' of existing entry it fails with error Failed to persist entry: API_ERROR: A file with this name already exists plus pattern: ['.*', "Error"] parameter gets completely ignored, as it still says that 'path is not a valid path' if path contains special characters(Uppercase letters, dots etc).
Any idea what I did wrong in configs? Because as far as my research go, I can't seem to find any info on meta parameter in Netlify docs or at Netlify forums.
Thanks in advance!

@ValeriyTen, can you please open a new issue with a reproduction scenario? I think it will be easier to find the underlying problem that way.
The docs are here https://www.netlifycms.org/docs/beta-features/#nested-collections, but probably needs some improvements.

@ValeriyTen, can you please open a new issue with a reproduction scenario? I think it will be easier to find the underlying problem that way.

Please have a look - https://github.com/netlify/netlify-cms/issues/4059
Thanks!


Issue in running classroom demo on my local machine

Hi Team,
I am trying to running classroom demo on my local machine as per your Readme File.
So I got this error-
Failed to create bucket: {"status":1,"signal":null,"output":[null,{"type":"Buffer","data":[]},{"type":"Buffer","data":[109,97,107,101,95,98,117,99,107,101,116,32,102,97,105,108,101,100,58,32,115,51,58,47,47,97,119,115,45,99,104,105,109,101,45,99,108,97,115,115,114,111,111,109,45,100,101,109,111,45,112,98,32,85,110,97,98,108,101,32,116,111,32,108,111,99,97,116,101,32,99,114,101,100,101,110,116,105,97,108,115,10]}],"pid":137308,"stdout":{"type":"Buffer","data":[]},"stderr":{"type":"Buffer","data":[109,97,107,101,95,98,117,99,107,101,116,32,102,97,105,108,101,100,58,32,115,51,58,47,47,97,119,115,45,99,104,105,109,101,45,99,108,97,115,115,114,111,111,109,45,100,101,109,111,45,112,98,32,85,110,97,98,108,101,32,116,111,32,108,111,99,97,116,101,32,99,114,101,100,101,110,116,105,97,108,115,10]}}
make_bucket failed: s3://aws-chime-classroom-demo-pb Unable to locate credentials.
Best Regards
Deepanshu Garg

I just cloned the repository and successfully deployed the stack under Option 2: Deploy from your local machine. I ran the script in the following setup:
% node -v
v14.17.0
% npm -v
6.14.13
% sw_vers
ProductName:	macOS
ProductVersion:	11.4

make_bucket failed: s3://aws-chime-classroom-demo-pb Unable to locate credentials.

Could you ensure that you have set up AWS credentials in your local machine? There are several options, such as storing credentials in the config file. See the Configuring the AWS CLI guide for more information about credentials.
https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html
Make sure that your AWS account has read and write access to S3.
Use the unique S3 bucket name. Once you successfully deploy the stack, you can pass the same S3 bucket name to update the existing stack.

Hi @simmkyu ,
I am doing same steps follow as you followed but on ubuntu.
sudo script/deploy.js -r us-east-1 -a aws-class-demo -s aws-chime-classroom-demo-pb -b aws-chime-classroom-demo-pb
I run this command.
And error will be same.
make_bucket failed: s3://aws-chime-classroom-pb-demo Unable to locate credentials.
I am ensure and checked also aws configure on my local system.
Storing credential is present there like accesskey,secretkey,region
Aws Account also have read and write access because i run another chime demo that run successfully.
And the bucket name also unique.But don't know why all time give same error as i mentioned above.
Please help me it's urgent.
Thanks

Close due to inactivity.


marker.isInfoWindowShown just makes marker visible

There is a problem with this method on a marker with hidden info, that when you want to check if it's visible it'll shows the info and then returns true.

Please post with test code.

Actually after encountered the error I changed my code.
So for now I have this code:
marker.isInfoWindowShow(shown => shown? marker.hideInfoWindow(): marker.showInfoWindow());
I tried to toggle info window by clicking on marker but the result was if it's open then close and if closed , open it for a bit (this was because of isInfoWindowShown) and after a blink of eye it hides again ( the value of shown is always true so the function hides the info window).

Um, the infoWindow is toggled clicking on the marker is default action.
So I think you don't need this code.

Is there anyway to disable this default?
Do you have any gitter (or similar live chat channel) to answer questions?

https://github.com/mapsplugin/cordova-plugin-googlemaps/wiki/Marker#disable-auto-pan

@wf9a5m75 This is about auto pan, not show the title.

Ok, your snippet code is not enough to test.
Please provide whole example code, and provide a screen recode(video).

This is fixed in the v2-beta version.
https://github.com/mapsplugin/v2.0-demo/blob/master/www/Marker/isInfoWindowShown.html
Try the new version please.
https://github.com/mapsplugin/v2.0-demo/


MouseHook messing with mousemovement

When I install the mouse hook the mouse movement becomes very very laggy.

same problem here


[DOCFIX] Fix the docs about the KV-store.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17301/
Test PASSed.


Differences between exports and across formats are inconsistent

IDs consistency from run to run.

Export FHIR using seed zero, and then again with seed zero. Do we get different resource IDs or other identifiers?
IDs between CDA, FHIR, and CSV -- are they consistent? Nice for mapping.

Dates consistency from run to run.

Two runs with seed zero, back to back, will produce different date timestamps in the data.

Can we close this with the recent changes to ID generation and reproducibility?