Cannot close a terminal with no tab

Windows Terminal version
1.17.12191.0
Windows build number
25941.1000
Other Software
No response
Steps to reproduce
There's no routine to easily reproduce it. It happens occasionally when I use some command line tools (like npm) that will invoke another terminal/cmd console. When the process is done, the invoked terminal will not close successfully (only the tab is closed, which results in an empty terminal with no tab), and you are unable to close it manually (because there's no tab).
Expected Behavior
A terminal losing any tabs should not exist.
Actual Behavior

There's no routine to easily reproduce it. It happens occasionally when I use some command line tools (like npm) that will invoke another terminal/cmd console.

I don't think anyone on the team has encountered this before. Are there some steps we could follow to attempt to reproduce it? (For instance if you list the tools that cause the issue for you.)

I happened to hit this bug many times. The strange terminal window (without any tabs on it) is invoked with -Embedding arg in the background by something, not sure what but I've a feeling that it's VS.

More Info:
It seems to be invoked by wininit.exe?

This is quite funny, but we have a repro right in our test suite 😂 (So I was correct, VS was related in this, maybe indirectly)
Step to reproduce:

Set Windows Terminal as the "Default Terminal application".
Open VS and run the test named "WindowsTerminal.UIA.Tests".
You should see a blank WT window pop up in the background.

video demo: https://youtu.be/lNJOSjXioOY

My theory is that if the client application exits fast enough, we start a defterm window, but we never get it to the point of making an actual tab.
I see this sometimes (but usually only when I have a horribly busted defterm install).
I wonder if this repros after the process model changes in 1.18

My repro case:

Run npm run dev to start a server.
Force close it by pressing ctrl+c once, and no need to confirm the ensued prompt Terminate batch job (Y/N)?.
Normally, a terminal window pops up and closes itself quickly. Sometimes there's a second window following, but it will stay and it contains no tab.

I can also reproduce with:

Set Windows Terminal as the "Default Terminal application".
Add a pretty short running Task To Task Scheduler executing a .cmd file on logon.
At every Logon you are greeted by a terminal window with no body (see the background of the picture)

For me it looks even more odd, as the windows don't even have a fill:

@DanielHabenicht I suppose you're Win10, and the fill we can see on other repros is Mica which isn't available on Win10. Therefore, no fill? 🤔

Yes, I am on windows 10. You can see the version in the issue linked above.

Here is another repro. Steps inside: https://github.com/microsoft/terminal/issues/16281
I noticed that sometimes when this happens, in addition to Windows Terminal launching without a tab (the reported bug) it does also start the classic shell that then runs the actual PowerShell command/script.

Hi, are there any updates on this?

I'm investigating this currently. I could have swore I used to have a minimal repro for this, but I'm having a hard time currently 😕

If someone who's seeing this consistently could Capture a Debug ETL Trace and share it here, that would help immensely. I'm guessing there's one of two things going on:

We're failing to initialize the intermediate OpenConsole, after starting the terminal for handoff.

In this case, I'd expect to see the following on the Microsoft.Windows.Console.Host provider

SrvInit_PrepareToCreateDelegationTerminal
SrvInit_CreatedDelegationTerminal
but then not a SrvInit_DelegateToTerminalSucceeded, nor a ReceiveTerminalHandoff_Failed (this would be logged to Microsoft.Windows.Terminal.Connection)

We're failing to accept the handoff from the Terminal.

this is like the above, but we would actually log a ReceiveTerminalHandoff_Failed

If we for whatever reason see a ReceiveTerminalHandoff_Success, then that would be surprising to me.

notes
First things first:

Conhost starts up. It finds that it's got a delegation console, and it starts that. (we can assume this works, because a terminal does get started)
OpenConsole starts up, as the target of a defcon handoff.
ConsoleEstablishHandoff:

It finds the target terminal to also delegate to.
Does quite a bit of pipe manipulation, to get ready to call the terminal. (we can assume this works, because a terminal does get started)
We open a handle to the target client process. We hang onto that handle until after the end of ConsoleEstablishHandoff.
Calls CoCreateInstance(g.delegationPair.terminal,.... (this instantiates terminal, below.)
gets our connection info: Icon, lnk, settings.

⚠ yikes there's a RETURN_IF_NTSTATUS_FAILED(ConsoleInitializeConnectInfo(...)) in here. If that does fail, we've started terminal, but failed to do a handoff.

We call handoff->EstablishPtyHandoff

This will get handled in CTerminalHandoff::EstablishPtyHandoff, which is broken down below.

now, over in the terminal, our registered default terminal handoff target. The following occurs when the terminal is launched as a COM server
These paths to _StartInboundListener take care of both glomming and non glomming.

In the glomming scenario, the monarch tells the MRU window to ExecuteCommandline, and that will start the inbound listener
in the non-glomming, TerminalWindow::Initialize sets the inbound listener.

In both cases, the inbound listener is started immediately if the page already
laid out, or we set a flag and wait till the first layout to accept the handoff.

TerminalWindow::Initialize, if _appArgs.IsHandoffListener OR TerminalWindow::ExecuteCommandline, again, if _appArgs.IsHandoffListener

TerminalPage::SetInboundListener

sets _shouldStartInboundListener=true
If we were already laid out the first time, immediately calls _StartInboundListener

TerminalPage::_OnFirstLayout called when the page first lays out

process startup actions
call _StartInboundListener to possibly start accepting handoff

So here, we're already laid out, and we know this window wants to accept the handoff.

TerminalPage::_StartInboundListener if _shouldStartInboundListener...

registers the ConptyConnection::NewConnection callback
calls ConptyConnection::StartInboundListener

CTerminalHandoff::s_StartListening passes the ConptyConnection::NewHandoff function as the callback to:

CoRegisterClassObject(CTerminalHandoff, us, as a local server, single-use)

returns

later, when conpty is ready....

CTerminalHandoff::EstablishPtyHandoff

THROWS if it fails, for ANY reason

⚠ Throwing would also just never call the callback, nor signal an error.

STOPS listening
duplicates handles
calls it's registered callback

ConptyConnection::NewHandoff raises the handoff, which is handled in

TerminalPage::_OnNewConnection accepts the connection from conpty

possibly co_awaits to get onto the window thread.
Creates the tab _CreateNewTabFromPane(MakePane(..., existingConnection))

Leonard: if you use the debug version, set a breakpoint during handoff, or just put a Sleep(10000) on the Terminal side, then the conhost will fail out and the close events will fire before the close events get set up

Hi, I think I'm facing a similar issue and was able to reproduce it consistently. Not sure if it's related to this bug specifically, but I hope it helps somehow. For the purposes here, I am using Terminal v1.21.2361.0.

Close all Terminal windows.
Open a Terminal window. (Window 1)
Use a command* to launch a second Terminal window, (Window 2) with the command exiting automatically.
Use mouse to hold on Window 2 as the command exits. (i.e dragging the window)
Press the close button on Window 2 and Window 1 gets closed instead.
We are now left with Window 2.

Pressing the close button again won't do anything.
Launching a new tab on Window 2 works fine but will also not close the window when all tabs are closed, or the close button is pressed.
To exit out of this "buggy" state, you would need to end the Terminal process or launch a new Terminal window. (either from external methods, or from within the bugged window itself)

*In my case, I initially used the command wt pwsh -wd "C:\Users" -c {Write-Host "test";} but since I was not sure if this was a PowerShell issue or Terminal issue, I also tested the command wt ping github.com and it worked as well.
Several observations:

This does not happen if you have more than 1 Terminal window running prior to executing the command.
If you have another window (Window 0) alongside the other 2 windows mentioned above, everything works just fine on step 5 and Window 2 gets closed properly.
This also does not work if you use the command above on a "buggy window".
Terminal Preview (v1.22.2702.0) does not close Window 1 when the close button on Window 2 is pressed.


[VS Code] Sharing Terminal: Unable to start WinPTY terminal 'C:\Program Files\Git\bin\bash.exe': The directory name is invalid (267)

Error:
Sharing Terminal: Unable to start WinPTY terminal 'C:\Program Files\Git\bin\bash.exe': The directory name is invalid (267)
Steps to Reproduce:
1.Start a shared terminal

Version Data

extensionName
VSLS

extensionVersion
1.0.869

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.38.1

platformName
Windows

platformVersion
10.0.14393

@unional Thanks for reaching out. Can you give us more details about your scenario? Also, your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

@IlyaBiryukov can you take a look once more info is provided ?

Sorry, I don't have the log yet as this time I can't reproduce it.
Last time I have two people connected to the live share beside the host.
Will do the same tomorrow to see if I can reproduce the issue.

Closing due to age. If you are still seeing the issue, please feel free to re-activate and we'll take a look!


Added a utility contract and a JS script for upkeep interactions.

Changes

Added a solidity file named as UpkeepInteractions.sol, showcasing the interaction with AutomationRegistrar and KeeperRegistry contracts, for registration of Custom Logic Upkeep and performing other operations like pause upkeep, unpause upkeep, cancel upkeep, add funds to upkeep, withdraw funds from upkeep, and edit gas limit of upkeep.

Added a script (upkeepInteractions.js) containing the functions to interact with the registered Custom Logic Upkeep.

Motive
Initially, I've created that as a utility contract and shared as a gist with the devs on Chainlink Discord, that are facing problems while registering and interacting with upkeep via contract.
Here are some of screenshots for the same:

So, on Bharath's suggestion, I've decided to create this PR. The contract code could possibly be added into the Register Upkeeps Programmatically section of the documentation, as it's a kind of extension of the same contract.
Kindly please review the PR, and let me know if any changes or add-ons are required from my end.
Thanks.

Thanks for the appreciation, @andrejrakic!
I've done the changes in the new commit, as you've mentioned. Kindly please review and let me know if any further changes are required from my end.
Thanks.


[Question] Disable or configure PVName

For my use-case, would it be possible to either disable PVName in the Hostpath path or manually configure a consistent value?
Currently, PVName (random UID) is used in the path, ideally the name should be: pvc_<namespace>_<pvc_name>
Thanks!

No, it is not supported.
The name is actually from the PVC's uid.


send_telegram: fix bug with str() call on unicode text

thanks!

@stevezau I think you meant to merge this PR, so I'm gonna go ahead and do that :P


Fix styling of two-state view buttons.

https://bugzilla.redhat.com/show_bug.cgi?id=1305423
https://bugzilla.redhat.com/show_bug.cgi?id=1305668
There are 2 ways view buttons states are rendered:
a) enabled/disabled
b) two state selected/not selected
This should be unified in a separate PR.

Reviewed & tested, changes look good, view buttons work as expected now.

ping @dclarizio


SymPyExpression

Implemented SymPyExpression and SymPyInterpreter's eval() method.

the above commits are me merging my forked branch to origin/main

Fixes


Fix packaging in i586

Signed-off-by: Otavio Salvador<EMAIL_ADDRESS>

Yes, saw with your last pull request. Thanks for the patch


tour: russian translation

Context: I'd like to translate the tour into the Russian language.
Hello, I have just started my way to "go" programming. For the practice, I'd like to translate the tour into the Russian language. Is it possible, and if yes, what is the procedure of translation acceptance? Thanks.

@zhanbaur look at https://github.com/golang/tour/blob/master/TRANSLATE for the rules.
The Russian translate is here https://go-tour-ru-ru.appspot.com
It seems it was reviewed https://github.com/golang/tour/commit/cd978b761ea990975ef36825a6a1831b0c2f29c1
The issue should be closed.

Thanx a lot.

There is also another translation: https://go-tour-russian.appspot.com/, source: https://github.com/golang-ru/tour-ru.

@AlekSi , It seems that the title of this translation doesn't correspond the requirements https://github.com/golang/tour/blob/master/TRANSLATE

Sign up to App Engine and create an app named go-tour-LL

go-tour-ru was squatted years ago. go-tour-ru-ru does not match that naming scheme too. :)


Error importing the solution

Hey there,
I am getting the below error:
"The solution file is invalid. The compressed file must contain the following files at its root: solution.xml, customizations.xml, and [Content_Types].xml. Customization files exported from previous versions of Microsoft Dynamics 365 are not supported."
I am using the latest version published here. Any advise?
Thank you

Resolved


/test should be renamed to /tests/ansible in README.md

See https://github.com/ElektraInitiative/libelektra/issues/1887

Should it be called user:/tests/ansible/example/fruit or user:/tests/ansible/fruit?

Everything below /tests/ansible is arbitrary. I would go for the shorter version. Btw. if what is written in the README could be a test that is at least executed before uploading to Galaxy, it would be amazing.

I have opened a new issue for the testing ( #5 ).


First feature:  dogecoin address handling

Perhaps it's easiest to start with a small vertical slice which is fairly well understood, and define some functions, write some code, write some tests, get some bindings working and ship a useful 0.1.0 version with a functional dogecoin address feature.
Keen to discuss what that would look like:

Address validation (all types)
Basic address generation
HD parent/child address generation / validation
Address identification (documentation in the spec? all the options etc)
test fixtures: a bunch of various addresses
bindings for golang / python / node?

Noting it might be worth looking at https://github.com/bitcoinj/bitcoinj/blob/master/core/src/main/java/org/bitcoinj/core/Address.java to inspire ideas.

Thoughts on what the final API should cover:

Parse from text (requires some sort of "What to expect" object which contains the prefixes for the network the address belongs to)
Generate from public key
Generate from script
Generate text (base 58) format address
Get type (pay to key, pay to key hash, pay to script hash)

Bitcoinj extends Address into LegacyAddress and SegwitAddress, as we don't handle segwit I think we're safe enough to have a single address type.
HD is something a wallet component would track, when generating keys, typically the addresses contain the hash of a key rather than the key.


Recipe card - a11y

It's not super good to have that many elements in a link tag.
Only the title should be the link and the link can expand the whole card with a pseudo element for example.
Also, I don't think a h3 for the name makes sense as there is no section/article/aside parent.

Fixed in https://github.com/maeligg/my-online-cookbook/commit/c8082fc32cd3313586cebfdf92bc187db9e12530


Total coverage calculation method is not correct

Example:
Source with 3 files:
File 1 - 1 executable line, 1 covered line
File 2 - 1000000 executable lines, 500000 covered lines
File 3 - 1 executable line, 1 covered line
Expected total coverage: (500000 + 1 + 1) / (1000000 + 1 + 1) = ~50%
Actual total coverage: (500000 / 1000000 + 1 / 1 + 1 / 1) / 3 = ~83.33%
Here is the line that does the calculation:
https://github.com/fastlane-community/xcov/blob/e5138422c9555c9eb8fe5a79be685e2bf95390f1/lib/xcov/model/target.rb#L13
I could make a PR but I'd have to modify JSON structure that xcov-core creates by crating a PR in https://github.com/fastlane-community/xcov-core and then update the binary here.
But I'm not sure if this is the fastest way.

Ok so I couldn't wait (lol)
Here are the PRs:
https://github.com/fastlane-community/xcov/pull/175
https://github.com/fastlane-community/xcov-core/pull/17

Hey @imaginaris , for me there is a difference between the coverage results reported when I run the results in XCode, from what xcov reports.
17.4% in XCode coverage
19% using xcov
could this be the reason?
Have you checked the XCode coverage calculation? Is it different?

Hey @asimparvez. Yes that was one of the reasons. In my case coverage from Xcode was around 15% lower that xcov's. The number of files and their respective coverage were the same.


[otbn,sw] Fix initialization of WDRs in barrett384

w14 and w15 get initialized later by loading from memory, so they don't have to be initialized with XORs.  w17 and w18, on the other hand, are first used in mulqacc.so operations, which update only half of the destination WDR.  Not initializing them causes mismatches compared to the ISS.

CI timed out, so I've rebased this on master to include a fix that reduces FPGA build time


Fix peer dep warnings

Yarn will warn about some implicit transitive dependencies. This can be fixed by making them actual dependencies of Fusion
This PR has private changes as well
Reopening from https://github.com/fusionjs/fusionjs/pull/509

!merge


Restore WWT nudges in intro slideshow

This PR fixes #603. I took the duration to wait before nudging (which is 2 minutes, in ms), from the voila version. All of this was handled Python-side in the old setup, but since we're using setTimeout client-side to do the timing, I just moved all of the logic into the Vue template as we only need to store a few different values.
Note that this is still Vue 2, so to update an array reactively we need to use this.$set.

@johnarban, I adjusted the nudge values and wanted to see if you think what I put in was reasonable. The original value was 2 minutes for each slide, but using the audio reader on the default speed takes almost a full minute for some of the text, so I figured if someone were trying to read all the text before the explore, that would only give them ~a minute to explore. I made the first slide length longer for people who really get into it, but we can change it if you think that's too much time total for the intro.


[1.x] Remove nunomaduro/larastan

This PR removes nunomaduro/larastan from dependencies. The package larastan/larastan is now being used instead.

@alecritson This gets added automatically by the monorepo-builder.php script. What's the difference between the packages defined in there and the ones defined directly in composer.json?

@alecritson This gets added automatically by the monorepo-builder.php script. What's the difference between the packages defined in there and the ones defined directly in composer.json?

@alecritson this looks like a mistake. It should have been updated here https://github.com/lunarphp/lunar/blob/1.x/monorepo-builder.php#L44


Missing colon (:) for Phone numbers and Fax on service listing

On Production V1.0.13, server v 1.2.3 there's a colon (:) for Phone numbers and Fax. At some point, the colon disappeared (see screenshots below):
Production:

Staging V1.2.0, server 1.3.8:

Tested on staging v1.4.0, server 1.3.9 on iOS:
Colon (:) appears after the labels Phone and Fax as they should be


nixos/postgresql: replace extraConfig option with settings option

Motivation for this change
https://github.com/NixOS/nixpkgs/pull/94231
ping @jappeace
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thank you!
The RFC this PR follows: https://github.com/NixOS/rfcs/pull/42
The idea is to only support essential options an upstream program provides, the other options can be set in an easy to use attribute set.

Feedback addressed.

@GrahamcOfBorg test postgresql postgresql-wal-receiver

Merge conflict resolved. Anyone keen on merging?

It would be kinder to users to have a smooth upgrade path.
Is it possible to deprecate extraConfig for one release then remove it in the next release?

It would be kinder to users to have a smooth upgrade path.
Is it possible to deprecate extraConfig for one release then remove it in the next release?

While I hate making changes that instantly force users to adapt without prior notice, in the case of extraConfig it is "worth it", at least in my opinion.
When asked about keeping both a settings and extraConfig option @Infinisil had this to say, which I think is quite relevant:

I'd rather not if possible, because then we have problem of not being able to merge values set in extraConfig with all other values, there are essentially two incompatible ways of specifying configuration then.

Further to this I would argue that migrating from extraConfig to settings is very trivial so it shouldn't take more than a minute or two.
Have I sufficiently addressed your concerns? I'm happy to continue the discussion and consider this further if not.

I suspect that users with existing nixos configurations may resent this as a gratuitous change providing no benefit to them, especially if they need to modify multiple services, or if option merging semantics change. Just my 2c.

Related to this PR itself, I have
services.postgresql.extraConfig = ''
  session_preload_libraries = 'auto_explain'
  auto_explain.log_min_duration = '5s'
'';

Should the postgesql settings option support nested attrsets? E.g.
services.postgresql.settings.auto_explain.log_min_duration = "5s";

I suspect that users with existing nixos configurations may resent this as a gratuitous change providing no benefit to them, especially if they need to modify multiple services, or if option merging semantics change. Just my 2c.

I would highly encourage you to express your opinions on this in the https://github.com/NixOS/rfcs/pull/42 thread. The more feedback an RFC gets (constructive criticism included) the better the end result.

Should the postgesql settings option support nested attrsets? E.g.

I'm not much of a postgresql user. I was unaware that such options existed. Documentation should be updated to reflect this and explain values like that should be quoted, like so:
services.postgresql.settings."auto_explain.log_min_duration" = "5s";

As a postgresql user would you have any motivation to contribute to this module by enhancing the documentation?

I just posted another comment about backwards compatibility in the RFC (saying it's up to the module writer to decide how to handle backwards compatibility). I guess the original comment by me that @aanderse linked is still relevant, but I think I mostly wrote that in relation to new NixOS modules. So if you create a new module, it should definitely not have an extraConfig if it can instead be settings. The RFC was mainly just intended for new modules because I knew backwards compatibility could be a problem.
While I'd love for all existing modules to eventually adapt the settings approach, I think backwards compatibility is still important, and for popular modules like postgresql it might make sense to keep supporting extraConfig for a while before deprecating it, even though it won't be ideal during that time.

@rvl NixOS is a pretty bleeding edge distro. Unfortunately inconvenient changes happen. I really like the welcoming and collaborative nature of the NixOS community so when I ask: "is this migration really that big of a hassle?" I'm just trying to better understand your perspective.
Here is my perspective: I manage upwards of 40 NixOS machines, each of which has a number of changes required to migrate to 20.09. Out of all the changes required to migrate to 20.09 I personally see extraConfig to settings as one of the least impacting and quickest to manage.
So now that we have had this discussion what can you do if you're still not satisfied with the situation? I would be disappointed if you made a PR add extraConfig back, but I wouldn't discourage it. If you see this as a breaking which isn't acceptable then we can quickly talk to the module maintainers and release managers to get your PR into 20.09. I hope you don't feel this way still, but I'll respect your opinion and try to support your efforts the best I can.

I think I have already made my perspective clear, thanks.
Please make sure you put something in the 20.09 release notes about this.


mysql: add references priv in AllColumnPrivs

Signed-off-by: unconsolable<EMAIL_ADDRESS>What problem does this PR solve?
ref pingcap/tidb#28531
What is changed and how it works?
add references priv in AllColumnPrivs
Check List
Tests

Unit test

Code changes

Has exported variable/fields change

Side effects
Related changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/cc @morgo
PTAL

/merge


[Enhancement] Test (and modify) all our components to make them support or handle i18n and l10n.

Feature Request
We need to make sure all our components either handle i18n and l10n, or atleast are flexible enough so the text could be replaced.
Covalent Modules:

[ ] Common (Pipes)

[ ] Digits
[ ] Bytes
[ ] TimeAgo
[ ] TimeDifference

[x] Chips
[ ] Data Table
[x] Dialogs
[ ] Expansion Panel
[x] File
[x] Json Formatter
[x] Layout
[x] Menu
[x] Notifications
[x] Paging
[x] Search
[x] Steps
[ ] Dynamic Forms
[x] Highlight
[x] Markdown

One thing (I work a lot outside the US) that I really appreciate is either opting in to localized text or having a message letting me know that i am seeing translated content with a prominent link to the default language.

Would this only support i18n the Angular2 native way or would it be possible to override labels via @Input parameters to use frameworks like https://github.com/ngx-translate/core ?

@forrest-lyman that is more of an issue on implementation on the product side, but its a nice feature we can implement in our internal products.
@crain For the most part we want every piece of text to be provided on consumption through inputs/templates to allow that flexibility. Maybe only a few might have hardcoded english strings that can be overridden by those inputs.
We are probably gonna start using ngx-translate ourselves, so we want to work well with it.

@emoralesb05 Why are you going to use ngx-translate? I can see one showstopper to use native Angular i18n - that is translating text inside source files. But @ocombe, the creator of ngx-translate is now a core contributor in Angular and going to solve this issue soon https://github.com/angular/angular/issues/11405
PS: I do think native angular i18n is more efficient since it produce no runtime penalty and all hard work is done is compilation stage that can be significant for big enterprise apps.

I am working on this right now, there is currently a blocker because I need to wait for the implementation of TypeScript transformers into tsc_wrapper for Angular (the team is working on this), but if everything goes well, this should land around 4.2 (maybe 4.3). This is a rough estimate since the blocker is not up to me :-)

@quanterion Yes, i've been following the progress of ngx-translate and @ocombe transition as contractor for the angular core team and i am super excited about that feature.
you answered in that statement the reason why angular's native i18n doesnt work for me. I dont want to have n builds for n languages to be honest, but when that feature is available we will migrate to it. This however is for our internal products, covalent should stay agnostic of this.
@ocombe Awesome man! Looking forward to all that, and using ngx-translate in the meantime for our internal products so hopefully its not gonna be a big leap jumping from one to the other? (fingers crossed haha)

I'll try to help with the migration by updating ngx-translate to support i18n tags, but there will be a bit of "replace in folders" to do :)
I agree that the n builds for n languages is a bit cumbersome, I'd love to have an option to support multiple languages in one build (even if the payload is higher), but it's definitively not for now, I'll have to convince the googlers and that will be hard.

Data Table is marked as able to handle i18n and l10n. I didn't find a proper way to localize labels without using atomic components. There is a tdDataTableTemplate directive that can be used to customize the data cells for a column, but do we have anything like that for the headers(so we can translate the labels)?

@parker-mike you need to use the columns input to set your own labels.

@emoralesb05 That's how I'm working now, but this way I can't use the translation pipe. Sorry, I didn't mention that I'm using the ngx-translate as suggested in the docs. Can you elaborate on this a little bit please?

So i do this in one of the internal products, but you can set they keys as labels and then do something like this
this.columns.forEach(async (col: ITdDataTableColumn) => {
      if (col.label) {
        col.label = await this._translate.get(col.label).toPromise();
      }
    });
    this.dataTable.refresh();


Try / catch not working for SQL transactions

Laravel Version: 5.4
PHP Version: 7.1
Database Driver & Version:
MySql 5.7

Description:
When trying to catch a database error Laravel serves its own error page rather than using the specified catch block.
Steps To Reproduce:

Do a query that you know is going to fail like orderBy('column_that_doesnt_exist')
Place that query inside a try/catch block
Catch \Exception as well as \Illuminate\Database\QueryException $e

For me, Laravel always serves back its default error page rather than using my custom exception handling. It never gets to any of the catch blocks.
Edit: further debugging (via log) shows that it is the QueryException that's being thrown, but for some reason, my catch isn't the one handling it.

This sounds like a syntax problem. Can you show your code that fails to catch it? A common problem is to forgetting to have the appropriate using-statement for the exception class.

@sisve of course - here's what we are doing. At first I thought it was a namespace issue but I believe catching \Exception should take care of that:
if (request()->has('order_by')) {
            try {
                $column = request('order_by');
                if ($column[0] === '-') {
                    $column        = substr($column, 1);
                    $clonedBuilder = $clonedBuilder->orderByDesc($column);
                } else {
                    $clonedBuilder = $clonedBuilder->orderBy($column);
                }
            } catch (\Throwable $exception) {
                throw new InvalidPaginationException();
            } catch (\Illuminate\Database\QueryException $exception) {
                throw new InvalidPaginationException();
            } catch (\PDOException $exception) {
                throw new InvalidPaginationException();
            } catch (\Exception $exception) {
                throw new InvalidPaginationException();
            }
        }

You're only calling the builder at that point, which is okay. The builder doesn't know about your columns and won't throw any exceptions.  Thank you, I'll give it a shot right now!


Introduced the developer dashboard documentation

Also add note not to make use of real users from IdP (e.g. SAP users)


Importer UI: specific error message for missing metadata

In discussion of issue 493 you said "It sounds like you're suggesting a special
message for when no match is found because there seems to be missing metadata,
yes? This is a great suggestion -- would you mind opening a separate bug report
for that improvement?". That's exactly what I'm suggesting, something that
highlights the distinction between "I couldn't find canonical information for
this" and "I have no idea what this is".

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 5 Jan 2013 at 8:48

Do not comment here, but on sampsyo/beets#184


added spotless formatters - used Specimin's implementation for it as …

…a foundation
Ran Spotless and did not see any changes to the code base.
EDIT: Deleted an unnecessary line and it modified the entire project.

We might want to wait until other PR's are merged before moving forward with this branch. Once others are merged, I can merge main into this spotless-formatter and run Spotless again on this PR.

For merging, the best might be (after all other PRs are merged) to make a new branch with just the buildfile changes from this one, and then merge that PR.  Trying to pull master into this PR is likely to lead to vast conflicts.

Closed the PR for simplicity of resolving all of the changes.


MetadataCreated & MetadataUpdated additional checks

[ ] Checking if the NFT is deployed by our factory
[ ] Checking the metadata proofs
[ ] Checking if we have the same txid with the "old" asset
[ ] Checking the block number (transaction block for MetadataUpdated to be greater than the "old" asset.event.block)

Checking the metadata proofs

This one is not mandatory for this task, as @alexcos20 mentioned in Slack, there is a seprate issue for integrating the proofs. Metadata proofs cannot be retrieved from the event itself (such as MetadataCreated or MetadataUpdated).
All being said, the rest of the checks remain valid.


qpwgraph: 0.6.1 -> 0.6.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/qpwgraph/versions.
meta.description for qpwgraph is: Qt graph manager for PipeWire, similar to QjackCtl.
meta.homepage for qpwgraph is: https://gitlab.freedesktop.org/rncbc/qpwgraph
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.2 with grep in /nix/store/1nrhi5rvpd0rvan5sf0mk14x3wz0rr2p-qpwgraph-0.6.2
found 0.6.2 in filename of file in /nix/store/1nrhi5rvpd0rvan5sf0mk14x3wz0rr2p-qpwgraph-0.6.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
qpwgraph

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1nrhi5rvpd0rvan5sf0mk14x3wz0rr2p-qpwgraph-0.6.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/4b0c410a7e8be4ebebf754d12491c27289238b01#qpwgraph

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1nrhi5rvpd0rvan5sf0mk14x3wz0rr2p-qpwgraph-0.6.2
ls -la /nix/store/1nrhi5rvpd0rvan5sf0mk14x3wz0rr2p-qpwgraph-0.6.2/bin

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

1 package built:

qpwgraph

Maintainer pings
cc @kanashimia @exi @Scrumplex for testing.

Result of nixpkgs-review pr 283116 run on x86_64-linux 1

1 package built:

qpwgraph


A strange error on running benchmark to test arangodb3-3.3.milestone2-1.x86_64.rpm

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[ ] 3.2
[ ] self-compiled devel branch
arangodb3-3.3.milestone2-1.x86_64.rpm

Mode:

[ ] Cluster
[Y] Single-Server

Storage-Engine:

[Y] mmfiles
[ ] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[Y] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[Y ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

this is an AQL-related issue:
[ ] I'm using graph features
I'm issuing AQL via:

[ ] web interface with this browser:     running on this OS:
[ ] arangosh
[ ] this Driver:

I've run db._explain("<my aql query>") and it didn't shed more light on this.
The AQL query in question is:
The issue can be reproduced using this dataset:
Your github's benchmark testing data. using npm run to generate the dataset.
Please provide a way to create the dataset to run the above query on; either by a gist with an arangodump, or `db.collection.save({my: "values"}) statements. If it can be reproduced with one of the ArangoDB example datasets, it's a plus.
Foxx
this is a web interface-related issue:
I'm using the web interface with this browser:     running on this OS:

[ ] authentication is enabled?
[ ] using the cluster?
[ Y] _system database?

These are the steps to reproduce:

npm run data
node benchmark arangodb -a <IP_ADDRESS> -t all

...
The following problem occurs: [Screenshot?]
"...
TypeError: Cannot read property 'length' of undefined
at /root/Documents/NimbiLin/Programs/Databases/NoSQL/Install/nosql-tests/node_modules/arangojs/lib/cursor.js:50:33
..."
Instead I would be expecting:
this is an installation-related issue:
Describe which steps you carried out, what you expected to happen and what actually happened.

and I again run this command "arangod  /root/Documents/NimbiLin/Programs/Databases/NoSQL/Install/nosql-tests/data --server.threads 16 --scheduler.threads 8 --wal.sync-interval 1000  --config /etc/arangodb3/arangod.conf --javascript.v8-contexts 17Error while processing command-line options:
unknown option '--scheduler.threads'
"
as the https://github.com/weinberger/nosql-tests 's Arango's start Parameters command, but the error says "unknown option '--scheduler.threads'"

--scheduler.threads has been obsoleted with ArangoDB release 3.0.
The nosql-tests repository above probably refers to an older version of ArangoDB.

Hi, Mr. Jsteemann
Good morning, thank you very much for your solve the 2nd issue.
Then how about the 1st issue? would you like to send a workable nosql-test script to
my mail of<EMAIL_ADDRESS>?
You are so great to write so many complex JS functions and it is not so easy for me to
solve the null self.result:
+++++++++++++++++++++++++++++
var self = this;
self._drain(function (err) {
self._index = self._result.length;
+++++++++++++++++++++++++++++

Hi @gloCalHelp : it seems that the benchmark code in the weinberger/nosql-tests repository is not compatible with recent versions of ArangoDB. It seems to have been written for ArangoDB 2.7 and needs some major overhaul in order to work with more recent versions.
I am sorry but I do not have time to work on this in the near future.

Hi @gloCalHelp,
a new performance benchmark, that is compatible with recent versions has been released about two months ago.

I am closing this issue as solved for now.
Please feel free to comment and reopen in case you have any problems running the latest benchmark.


Elazarl/feature/cuuuid

Expose cuDeviceGetName from device

@coreylowman
Would uuid as the function name be acceptable?
Why do we have get_name when rust getters seems not to have the get_ prefix?


NPM version only has package.json

NPMjs.com reports this package is at version 1.0.0 and when I ran npm install --save, it only came with package.json. :bug: :watermelon:

It's actually not published yet -- I just uploaded package.json to reserve the package name :)


Choose a random value from a fixed list of values

Sorry if this has been asked before but..
Is there any built-in randomizer that does what ConstantRandomizer does but extended to multiple values? Example:
public ConstantListRandomizer(T... values) {
    this.values = values;
}

@Override
public T getRandomValue() {
    return values[random.nextInt(values.length-1)];
}

One solution would be using a lambda expression:
var parameters = new EasyRandomParameters()
        .randomize(FieldPredicates.named("countryIso"), () -> List.of("en", "es").get(new Random().nextInt(2)));

But that looks ugly, doesn't it?

Yes, GenericStringRandomizer is what you are looking for. It allows you to generate a random value from a list of strings.


Tutorial 9 (Research Documentation) is not generating .rad- & .oct-Files

Hello together,
I am still getting to know the program with a lot of gaps in the basics of python. :0
Is this tutorial not working because of an personal issue or is it somehow outdated?
Sincerely Simon

Hi, yes the tutorial 9 should run on the current release 0.3.4.  Could you please paste any error messages that have been generated that don't match the original notebook output?


RFC: Support Sass-like variables

How do you guys feel about this?
// current
const Card = styled.div`
  background: ${props => props.color};
  height: ${props => props.size};
  width: ${props => props.size};
`;

// proposed
const Card = styled.div`
  background: $color;
  height: $size;
  width: $size;
`;

// nested props
const Card = styled.div`
  background: $theme.primary.color;
  height: $size;
  width: $size;
`;

// manipulating props
const LongCard = styled.div`
  background: $theme.primary.color;
  height: ${props => props.size * 1.5}; // sorry, you have to do it this way, any ideas?
  width: $size;
`;

Say hello to my little friend!
// `foo: $bar;` wont really work
// we need to properly identify where the variable starts/ends

// ends with a semicolon
foo: $bar; // works
foo: $bar;px; // meh
foo: rgb($r;, $g;, $b;); // 💩

// ends with a space
foo: $bar ; // prettier removes space, fails
foo: $bar px; // meh
foo: rgb($r , $g , $b ); // prettier removes spaces, fails

// parentheses
foo: $(bar); // not bad
foo: $(bar)px; // not bad
foo: rgb($(r), $(g), $(b)); // not that bad

// takes a template string style and returns it after evaluating it's props
const parse = props => str => {
  // simple regex, not my strongest skill, feel free to improve
  const regex = /\$\((.+)\)/g;

  // not sure if we need to iterate with str.map()
  let style = str[0];

  // access style instance
  style = style.replace(regex, (match, value) => {
    // split it by a dot to allow nested props (if any)
    let path = value.split('.');

    // evaluate props
    path = path.reduce((obj, prop) => {
      // prop exists
      if (obj) return obj[prop];

      return '';
    }, props);

    return path;
  });

  return style;
};

// test
it('works', () => {
  // assuming props is accessible when calling styled()
  const props = {
    color: 'red',
    size: 64,
    theme: {
      largeText: 36
    },
    deeply: {
      nested: {
        objects: {
          work: 'yes!'
        }
      }
    },
    multi: 'lines'
  };

  const parsed = parse(props)`
    background: $(color);
    height: $(size)px;
    width: $(size)px;
    do: $(deeply.nested.objects.work);
    has:
      $(multi);
  `;

  const expected = `
    background: ${props.color};
    height: ${props.size}px;
    width: ${props.size}px;
    do: yes!;
    has:
      lines;
  `;

  expect(parsed).toBe(expected); // passes
});

Will see if it's pluggable to sc without causing a test failure and draft a PR.

We've basically rejected very similar proposals before on the simple basis that we're trying not to introduce any special syntax and I hope that this makes sufficient sense 👍
https://github.com/styled-components/styled-components/issues/590
https://github.com/styled-components/styled-components/issues/560
I think there were more issues like these.
Anyway, to propose an alternative, this would be well suited for a babel plugin that doesn't even require any hacky plugin (we don't support plugins), or a fork (worst-case scenario in my opinion, especially for just a feature). As long as you can write the regex and split the string you can simply transpile your strings into interpolations during transpilation time.

Thanks for the reply. I completely understand why you would turn down such proposals that attempt to introduce new syntax. I actually think that you are doing a great job making things light and intuitive, but let make the case for this one -as if I wasn't the one behind it- at least.
I use sc because it's a tool that I found to make me more productive while working on user interfaces. When it comes to being productive, I think we should always exhaust that area with investigation, anything that can help developers build something better in a more efficient way is probably a career-devoting worthy. I don't use React just because it's a great tool, I don't use styled components just because it's a great tool, I use both because I love using them. There is a significant difference here, there is an abundance of great software, but finding software that you enjoy is rare. The reason these tools are endorsed by the community is that they are supported by the community itself, in a way it shapes them to fit its needs.
First, I would like to point out that you do generously take into consideration feedback from your users, even if it was syntax related. An example of that would be supporting // inline comments in the styles, because it makes out life slightly a bit easier. I would argue that CSS variables would too, and they fit the spirit of React (style as a function of props), and the spirit of styled components (superpowers for CSS). Second, we are not introducing any complex syntax in this case unlike in the proposals you referenced -and I'm sure in many others-. This is new addition (), literarily, there is not learning curve, noting complicated, but it comes with great power behind it.
So why did I propose this in the first place? simple, because I disliked the way I have to write ${props => props.foo} every time, and I write a lot of components. This has nothing with sc, this is JS, but we are allowed to hate on JS aren't we? I saw an area where things can be improved, I saw an area that wasn't covered by sc (Sass variables), and voila! I really think developers would love it and start using it everywhere, all the time. Maybe I'm wrong, but for now I'd have to trust my understanding of how can a developer be lazy and productive at the same time.
Maybe the proposal here isn't perfect -and it doesn't have to be-, but if you are open to this, you will get my commitment to workout an ideal solution as much as possible. I just found out that there is a method in lodash for accessing objects by a string path for example, I would appreciate a chance to continue working on this, or at least keeping the discussion open.

I would appreciate it if you can mention why you think this particular syntax is confusing. Also, would you say that supporting sass-like variables is something that's maybe worth looking into in the future?
Can you provide me with some babel-plugin references for styled-components @mxstbr? maybe it's time for me to learn how to babel.
Link to repo of implementation with tests https://github.com/sonaye/styled-components-variables.

It's not the syntax inherently that is confusing, but it blurs the line of where styled-components starts and ends. Right now it's quite easy for us to say that it does auto-prefixing and handles nested CSS. Most of this is without consequence to anyone who knows CSS, no matter whether they're getting started or have been writing it for a while.
A new syntax simply does not belong in a tool that aims to make styled-components a consequent, minimal idea. It might be that this library seems large after a time of growth and refinement, but the core idea is simple. Explaining unique features is burdensome for beginners although it's not without merits. At the same time we'd then have to determine what ideas do belong in the library. The core and its message would change. This is mainly why we've avoided extendability and custom syntax so far.
No promises but if we ever arrive at a whole CSS-in-JS ecosystem this could become much simpler and an easier question to answer

@kitten is this snippet enough to detect all styled components?
https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/utils/detectors.js#L36-L69
Then we can do something like:
export default function({ types: t }) {
  return {
    visitor: {
      TaggedTemplateExpression(path, state) {
        if (isStyled(path, state)) {
          // do stuff
        }
      }
    }
  };
}

Got it working, not sure if it's enough though.
export default function({ types: t }) {
  // source: https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/utils/detectors.js
  const importLocalName = (name, state) => {
    let localName = name === 'default' ? 'styled' : name;

    state.file.path.traverse({
      ImportDeclaration: {
        exit(path) {
          const { node } = path;

          if (node.source.value === 'styled-components') {
            for (const specifier of path.get('specifiers')) {
              if (specifier.isImportDefaultSpecifier()) {
                localName = specifier.node.local.name;
              }

              if (
                specifier.isImportSpecifier() &&
                specifier.node.imported.name === name
              ) {
                localName = specifier.node.local.name;
              }

              if (specifier.isImportNamespaceSpecifier()) {
                localName = specifier.node.local.name;
              }
            }
          }
        }
      }
    });

    return localName;
  };

  const isStyled = (tag, state) => {
    if (
      t.isCallExpression(tag) &&
      t.isMemberExpression(tag.callee) &&
      tag.callee.property.name !== 'default' /** ignore default for #93 below */
    ) {
      // styled.something()
      return isStyled(tag.callee.object, state);
    } else {
      return (
        (t.isMemberExpression(tag) &&
          tag.object.name === importLocalName('default', state)) ||
        (t.isCallExpression(tag) &&
          tag.callee.name === importLocalName('default', state)) ||
        /**
         * #93 Support require()
         * styled-components might be imported using a require()
         * call and assigned to a variable of any name.
         * - styled.default.div``
         * - styled.default.something()
         */
        (state.styledRequired &&
          t.isMemberExpression(tag) &&
          t.isMemberExpression(tag.object) &&
          tag.object.property.name === 'default' &&
          tag.object.object.name === state.styledRequired) ||
        (state.styledRequired &&
          t.isCallExpression(tag) &&
          t.isMemberExpression(tag.callee) &&
          tag.callee.property.name === 'default' &&
          tag.callee.object.name === state.styledRequired)
      );
    }
  };
  // ..

  return {
    visitor: {
      TaggedTemplateExpression(path, state) {
        if (isStyled(path.node.tag, state)) {
          let { value } = path.node.quasi.quasis[0];
          value.raw = value.raw.toUpperCase();
        }
      }
    }
  };
}

I don't think this is a good idea. Part of the reason why explicit interpolations are better for this sort of thing is syntax issues and missing variables are easy to catch with a linter since at the end of the day, it's vanilla JS that most tooling understands.


upgrade dependencies

https://github.com/coral-xyz/anchor/pull/2318
https://github.com/raydium-io/raydium-frontend/blob/e0a65b860f7ce65d044be295a98f2165f5381fc2/package.json#L38

Thank you for your contribution! Can you please give a quick rundown of what it improves? Thank you!

I think your edits make sense; thank you! I'll take a look and merge it later :)


Origin/umberall fund proposal

Fixed lint
Fixed typos
Updated dictionary

@jaysonmc Please review last changes. Your PR should be merged instantaneously once this one is approved.


Shader code: using global varying in function is broken

Godot version
3.4-beta2
System information
Linux Ubuntu 20.04
Issue description
shader_type spatial;

varying vec3 outer_vec;

void test() {
  vec3 local_vec = outer_vec; // error(6)
}

Shaders are no more happy when global varying is referenced anywhere in functions.
Godot throws error "error(L)". L - is a line number.
3.3 stable works.
Steps to reproduce
Just any shader as described above. Both in editor and runtime.
Minimal reproduction project
No response

Fixed by #50963.


Add derived_class property to forms

Description:

Even though the base_hdr_includes does the same thing, it can be confusing to use one property for forms, and a different property for controls.
Note that this property is used in addition to base_hdr_includes. derived_header would be ignored if derived_class isn't specified.

This has been added, but the issue didn't get closed with the commit.


ERROR: 'scrcpy-server' does not exist or is not a regular file (Aug 20,2020)

OS: Windows 10
scrcpy version: 1.16
installation method: Chocolatey
device model: N/A
Android version: 10

Scrcpy was working fine for me but after i deleted the old version folder(Installed it manually) and installed the new version via chocolatey it wont work anymore and it shows the directory of the old scrcpy that i deleted
The error i was getting:
C:\Windows\system32>scrcpy
INFO: scrcpy 1.16 <https://github.com/Genymobile/scrcpy>
stat: No such file or directory
ERROR: 'C:\scrcpy-win64-v1.14\scrcpy-server' does not exist or is not a regular file
Press any key to continue...

Already read issue #1002 and the other issues that is related to this, but one thing is different.
The directory that scrcpy is looking at is "wrong"
btw im still fairly new to github and command excecutions, only started learning basic java recently-

You probably set SCRCPY_SERVER_PATH environment variable with an old value. Just unset it.

how do i do that?

Found a quick fix to it.
just move all the new version resources to the old scrcpy folder and it all works fine now.

how do i do that?

Random links:
https://docs.oracle.com/en/database/oracle/r-enterprise/1.5.1/oread/creating-and-modifying-environment-variables-on-windows.html
https://support.shotgunsoftware.com/hc/en-us/articles/114094235653-Setting-global-environment-variables-on-Windows

check if "/ usr / local / share / scrcpy / scrcpy-server" is not a folder.
Copy "scrcpy-server" to "/ usr / local / share / scrcpy /" as a file.
I had the same problem and I solved it that way


flipclockjs how come exceeds overhead cpu?

I Use FlipClock http://flipclockjs.com/faces/hourly-counter , but overhead cpu on 20 or 30 % on client side, the same processor should be loaded when you open this link, what can be done?

One option is try to use the new version in the dev branch. The initialization syntax has changed a bit though and I haven't pushed the new docs yet.


runc.v1 and runc.v2 doesn't support ShimCgroup

Description
runc.v1 and runc.v2 doesn't support ShimCgroup yet.
This is fine for the CRI plugin for now, because we haven't put shim into the pod cgroup yet https://github.com/containerd/cri/issues/217.
But it is still worth an issue to note this down.

I'll fix this.


Unable to see multiple results

Please fill in as much of the template as possible.
-->
System information:

Operating system (distribution) and version -Win Server 2012
DBeaver version - 7.1.0

Connection specification:

Database name and version - Netezza

Describe your question:
I am running multiple sql statements like,
select 1;
select 2;
select 3;
select 4;
But, in the results tab, I am getting results from the first statement ONLY.
Instead, I want to have results from all the four statements side-by-side (Horizontally). Do I have to change anything in my Window>Preferences tab?

Hi @techlock77 ,
you could use Execute SQL Script button


Account for the case surface_capabilities.currentExtent is unset

Wayland in particular sets surface_capabilities.currentExtent.width to the special value 0xFFFFFFFF, which is valid per spec. Fixes #98779
It may also fix misc issues when resizing on all platforms.
Superseedes PR #98780 , thanks to user @tdaven for the original patch. PR #98780 would break Android support as it did not account that width and height might need to be swapped.
Replaced manual swap by Godot's SWAP(), which indicates intention much easier.

I can confirm this PR fixes https://github.com/godotengine/godot/issues/98779.  I don't have an android setup so I can't test that behavior. But Fedora 41 Wayland session opens the editor fine with this PR.

Building on Android now to quickly smoke test

Apologies for the late testing. I just tested 2 projects on Android and it looks like it's working fine.
:smile:

Thank you!


Update crossbeam-deque

0.8.0 has been yanked

You can update this in your own Cargo.lock with semver compatibility, but anyway #876 also updated the explicit dependency. Thanks anyway!


Multi agent type support

More about AutoGen GroupChat: https://microsoft.github.io/autogen/docs/tutorial/conversation-patterns#group-chat

Introduces new agent flow (see the diagram above)

New agent flow can be the base for the future specialized agents (like DAI agent)
In the current flow, all the 'If' conditions and checks are piled up in CodeWriterAgent system prompt and weaker models easily struggle with this a lot of ifs even right now.
Current flow llama_3.1_8b example:

looking great!

Want to merge so we can move on and add my changes we discussed.  Let's make new issue for the cost issue.


Change readme.md

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adding ignoreUrlParamsMatching to sw-lib

R: @jeffposnick @addyosmani
This just adds the logic to sw-lib, will hook up with sw-build in a seperate PR.
@jeffposnick could you check my logic isn't crazy different from yours in sw-precache.

I believe @addyosmani's comments were addressed, and I know he's traveling. so I'm going to merge.


local packs file: sort pindex ?

Hi
Do you think it could be easy and nice to sort each pdsc line in .Local/local_repository.pidx ? :-)
Thx

Currently the local .pidx gets new entries concatenated to the end of <pindex>, do you mean sorting as grouping packs from the same Vendor and listing them from newest to oldest version?

Please keep in mind that for this to be useful, we need to extend the specification such that all tools editing the local_repository.pidx would follow the same sorting.
In my opinion we should not require tools to sort XML elements by attribute values.
I rather think that the tools could sort the output when listing the content (e.g. cpackget list packs could sort the output, or even group by public, local and local-repository packs.

This was a quick question to open discussion...
I agree that cpackget.exe list is OK
(except #100 :-))

I am supporting canonical order. It is useful for diff. I would prefer files ordered in standard way by common formatting tool. Same principal should be applied also for *.pdsc and csolution.yml.

Any further discussion/comment on this? Have other tools been updated to support this behaviour? @jeromecoutant

Closing for now.


Something in/around the r0.6.1 release broke most of the link references

There's a huge number of broken links across all specs for some reason, and they were either broken in the most recent release or the one prior. We used to have these working based off titles automatically, which is why we use them, so it's weird that they no longer function at all.

can you give specific examples? I've not spotted that many, other than https://github.com/matrix-org/matrix-doc/issues/2623

Most of the spec appendices, quite a bit of the client-server API. I don't really have specific examples, just a feeling of it being more horrible than usual to navigate.
It looks as though many of the named anchors are in the table of contents instead of in the actual document?

@richvdh A specific example can be found here. The link to Signing Events doesn't work.

@IvoWingelaar thanks. That's another case like #2623 where we should use proper RST internal links rather than using the implicit anchor from the section title.
What I don't really understand is why docutils decided to give the "Signing Events" section an autogenerated anchor id rather than the human-readable one.

I am presuming this is fixed with the new platform. If not, new issues are appreciated.


Added missing dependency to requirements.txt

This MR adds a missing dependency to ensure that anyone who forks or clones is able to install all deps and run the app.


Gh 874 accumulo and hbase serialisers

Codecov Report

Merging #953 into develop will decrease coverage by 1.07%.
The diff coverage is 71.73%.

@@              Coverage Diff              @@
##             develop     #953      +/-   ##
=============================================
- Coverage      63.56%   62.48%   -1.08%
+ Complexity       956      917      -39
=============================================
  Files            480      481       +1
  Lines          13900    13929      +29
  Branches        1577     1580       +3
=============================================
- Hits            8835     8703     -132
- Misses          4428     4596     +168
+ Partials         637      630       -7

Impacted Files
Coverage Δ
Complexity Δ

.../src/main/java/uk/gov/gchq/gaffer/store/Store.java
75.1% <0%> (-4.08%)
0 <0> (ø)

...k/gov/gchq/gaffer/accumulostore/AccumuloStore.java
65.78% <100%> (ø)
0 <0> (ø)
:arrow_down:

...q/gaffer/hbasestore/HBaseSerialisationFactory.java
100% <100%> (ø)
0 <0> (?)

...er/accumulostore/AccumuloSerialisationFactory.java
100% <100%> (ø)
0 <0> (?)

...java/uk/gov/gchq/gaffer/hbasestore/HBaseStore.java
60.52% <100%> (ø)
0 <0> (ø)
:arrow_down:

...alisation/implementation/SerialisationFactory.java
96.66% <95.83%> (-3.34%)
20 <14> (+11)

...chq/gaffer/rest/mapper/GenericExceptionMapper.java
20% <0%> (-80%)
0% <0%> (ø)

...java/uk/gov/gchq/gaffer/proxystore/ProxyStore.java
0% <0%> (-69.5%)
0% <0%> (-30%)

...gov/gchq/gaffer/rest/service/OperationService.java
0% <0%> (-68.52%)
0% <0%> (ø)

...uk/gov/gchq/gaffer/proxystore/ProxyProperties.java
0% <0%> (-44.83%)
0% <0%> (-17%)

... and 10 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 a335a7a...7290585. Read the comment docs.


Chef 13 compliance and npm bugfix

Description
specify a unique resource name for package apt-transport-https and npm_packages because of https://docs.chef.io/deprecations_resource_cloning.html
Issues Resolved
redguide#183
redguide#115
redguide#153
Check List

[x] All tests pass.
[x] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

Thank you for your hard work and this PR, it works great in my environment.


Deployment of metrics

Description
https://www.loom.com/share/18bd39d29cbe48b38cb70cb25501d059
Please include a summary of the change and a link to which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Deployed the metrics end points to AWS
Fixes # (issue)
N/A
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

[x] This change requires a documentation update

Change status

[x] Complete, tested, ready to review and merge

How Has This Been Tested?
Yes
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checked endpoints after deploying and they are functioning on the DS API.

Checklist:
Everything in this checklist is required for each PR.  Please do not approve a PR that does not have all of these items.

[x ] I have pulled from master before submitting this PR
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer (the peer review to approve a PR counts.  The reviewer must download and test the code)
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

Good practice on pushing to AWS. Simple and keeps things up to date.


MNT: Re-rendered with conda-build 3.17.8, conda-smithy 3.3.4, and con…

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


error in def altitude(self) -> float:

** 0.190284 is an error, should be .190294 or .190285, or better yet: "** (1.0 / 5.255)" and let the compiler calculate it.

Solved by https://github.com/jposada202020/MicroPython_BMP581/pull/3


Add shirodeveloper to Contributors list

@shirodeveloper, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I accepted it?

@shirodeveloper, I can suggest projects for you to contribute to but if you're thinking about making a living out of it, you might wanna look in to https://www.fossjobs.net/
I've never looked in to monetizing part of it.


Remove duplicates from external links search results

This is a more simplified version of addressing what https://github.com/cfpb/cfgov-refresh/pull/4611 was attempting to address, by removing duplicates at the time of the search.
See PR above and GHE/CFGOV/enhanced-cms/issues/39 for more context.

@richaagarwal - @nataliafitzgerald and I updated the helper text. I just pushed it up to this branch for you.

Thank you @marteki!  I have incorporated your changes and @chosak's feedback in my latest commits.

@chosak Thank you for the feedback!  I added a couple tests and changed the function to a static method.
I also added an additional filter on the search since it seems unnecessary to search all pages -- just creatable ones -- in this commit: https://github.com/cfpb/cfgov-refresh/pull/4627/commits/479a7099f61561ccec479a35ac18f892795d3194.  Regardless of that, the duplicates are removed, but it seemed to make sense to narrow the scope of the search for performance.
If you could take a look at the tests I added and that change I'd appreciate one final review!

@richaagarwal 👍 tests look good! I have one minor suggestion that doesn't impact the testing logic at all but allows for a shorter and simpler test: instead of constructing the page and then using the  Wagtail StreamValue class to set the StreamField, set it as a constructor argument. See this diff I made on a branch to demonstrate. To my eye this is a little more readable and straightforward about what the content of the StreamField is, and it also avoids using the internal StreamValue creation approach. I know we do it how you've done it here elsewhere in the codebase, though.
Regarding filtering out pages that aren't createable: do you have a sense for the performance benefit? The concern I'd have (especially if this goes undocumented) is that we might encounter a situation in future where we purposefully set is_creatable to false on a page type for the purposes of preventing its creation in the UI. Say we have a singleton page type (like the recent TDP index page) and we only ever want one of these ever, anywhere. So we might use a script to prevent it, and then use is_creatable to hide it from the UI. If we did that, those pages would disappear from the search results (or never appear if we did that from the beginning) and it wouldn't be clear to the user why that was.

@chosak Thanks! I've incorporated your updates to the tests; I agree it's more readable that way.
And good point on is_creatable, I've removed that logic for now and can always revisit later if there's performance reasons to do so.


When it is eaten, the entire stack disappears

Describe the bug
When there is more than one expired food in a stack, when it is eaten, the entire stack disappears.
To Reproduce
Eating foods in stack.
Expected behavior
I understand that I should only consume 1
Screenshots
I have the following 3 expired foods in stack:

When I eat 1, all 3 disappear (screenshot after eating only 1):

Minecraft Version:

1.20.4

Server Version:

Paper 1.20.4

Plugin Version

NoMoreCooked-0.0.9c-RELEASE

Problem solved in version 0.0.96 of NoMoreCooked available on Spigot.
If you encounter other problems, don't hesitate to reopen another issue or reply to this one if it concerns this problem.
Have a nice day !


Account linking does not work if only external registration is allowed

Gitea version (or commit ref): 1.9.4
Git version: 2.22.0
Operating system: GNU/Linux Debian 9
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No (ALLOW_ONLY_EXTERNAL_REGISTRATION not set to true)
[ ] Not relevant

Log gist:

Description
The password input is disabled if only external registration is enabled.
However the form can not be successfully submitted because Gitea requires an input to the password text field.
The following code snippet states, that this is a feature for "second factor"-enabled accounts.
https://github.com/go-gitea/gitea/blob/280f4bebbf5883eef94d8a84b21575393ae5e0e1/routers/user/auth.go#L894-L898
However if the existing user has set a password already, the password field needs to be shown. Otherwise he is unable to authenticate and link the account.
Maybe there should be an additional setting specifically for "second factor"-enabled accounts instead of using ALLOW_ONLY_EXTERNAL_REGISTRATION?
Screenshots

I encountered a similar issue, but I don't think it is related to the ALLOW_ONLY_EXTERNAL_REGISTRATION (we didn't have this option set on our server).
How this looks like:
Prerequisite: I already have an existing Gitea account, and I'm not logged in

I use the "Sign in with Open ID Connect" option and log in with my Open ID Connect authentication server
I get two options now - to register a new account or to link to an existing account, I choose the second one (the "Link to Existing Account" tab), but the tab has only place for username or email (there is no place for the password)
I type e-mail (or username, it doesn't matter - the behavior is the same for the two options) and accept
I am now redirected again to the "Register New Account" tag, but now my e-mails/username is filled in (but I cannot create such a user as it already existed)
Presumably, the problem is the lack of the password, so I check the "Link to Existing Account" tab again - now it looks different: apart from the username/e-mail field it now shows a password field marked in read as if I had forgot to fill it (but it wasn't there at the start)

Here are the screen-shots showing p. 1, 4 and 5

We use version 1.9.3 of Gitea Server. I tried to reproduce it on https://try.gitea.io/ by logging in with GitHub, but there it works correctly (however, once I got a 500 error).

I answer on behalf of @jkocot. We set: ALLOW_ONLY_EXTERNAL_REGISTRATION = false and REQUIRE_EXTERNAL_REGISTRATION_CAPTCHA is not set, but I believe it inherits the value from ENABLE_CAPTCHA, which in our case is set to false. So this results in a hidden password field.
If I set ENABLE_CAPTCHA = true the password field shows up, so this works as expected.

I don't think this issue has been resolved yet. Any further comments @hsiejkowski, @jkocot ?

I don't think this issue has been resolved yet. Any further comments @hsiejkowski, @jkocot ?

For us this works as expected, so we have no further comments.

If I understand correctly you enabled the Captcha option and the password field is shown?
Well shouldn't the password field also be visible without Captcha being enabled?

To test it once again I disabled captcha on gitea 1.10.2 and the password field is visible. Regardless if ALLOW_ONLY_EXTERNAL_REGISTRATION is set to false or true.

I found pull request #9150, which deals with this issue. So I will comment again once I've done the update.

Okay, so after the update from 1.10 to 1.10.2 everything is working as expected. I'll close the issue.


Ability to use a custom color palette

This pull request aims to implement a way for the user to manually edit the colors of the color palette used for coloring the tags.
A new input was created on the plugin's settings screen to receive the customized colors. The user should enter the hex code of the desired colors, separating each one with commas.

Thank you for you suggestion. I'd like to keep plugin simple, so can we hide this option (maybe more options in future) in Advanced toggle?

Hey @pfrankov !
I ended up noticing that there was an issue with my implementation. The way I set it up to ignore the palette settings and use custom colors ended up causing some bugs when the user no longer wanted to use the custom colors. I solved the problem by creating a toggle.
I hope you like how it turned out, but an advanced settings area would also be nice.

Custom colors disabled:

Custom colors enabled:

@HenrryEsposito thank you again for the idea! I've implemented it in https://github.com/pfrankov/obsidian-colored-tags/releases/tag/5.0.0


Some questions about the type of data Mamba can handle.

Mamba is amazing, I wonder if it is suitable for sequence data with interchangeable tokens, for instance, stretching the node data on the graph into a sequence, since it seems to only learn the information of the underlying continuous signal.

Mamba doesn't necessarily operate on continuous signals. Extending it from sequences to graphs is a separate challenge though.


Can't resolve 'child_process'

On importing import {machineId, machineIdSync} from 'node-machine-id' in app component then getting this error. Any work around for the same.
ERROR in ./node_modules/node-machine-id/dist/index.js
Module not found: Error: Can't resolve 'child_process' in 'C:\Users\farhan\Desktop\ Farhan\Projects\BFMC\BFMClient\node_modules\node-machine-id\dist'

I had the same problem, I think. You are probably using machineIdSync in the Electron renderer process? child_process is a node module and can only be accessed from the main process.
Try a request from the renderer process:
this.userId = this.electronService.ipcRenderer.sendSync('UUID_REQUEST')
And in the main process:
ipcMain.on('UUID_REQUEST', async (event, args) => {
    event.returnValue = machineIdSync();
});

Faced with the same problem I did some research. With inspiration from https://stackoverflow.com/questions/54459442/module-not-found-error-cant-resolve-child-process-how-to-fix I solved it by adding following config for webpack.config.js:
    node: {   child_process: "empty" }


Set baseUrl of Jupyter after initialization

Fixes #10510

Codecov Report

Merging #10661 (3cb7a88) into main (e92cac6) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #10661   +/-   ##
======================================
  Coverage     70%      70%
======================================
  Files        475      475
  Lines      28205    28205
  Branches    4736     4736
======================================
+ Hits       19975    19980    +5
+ Misses      6350     6344    -6
- Partials    1880     1881    +1

Impacted Files
Coverage Δ

src/kernels/installer/productInstaller.node.ts
74% <0%> (-5%)
:arrow_down:

src/kernels/raw/session/rawJupyterSession.node.ts
78% <0%> (-2%)
:arrow_down:

src/kernels/kernelDependencyService.node.ts
85% <0%> (-1%)
:arrow_down:

...ommon/process/environmentActivationService.node.ts
72% <0%> (-1%)
:arrow_down:

src/platform/common/utils/localize.ts
75% <0%> (-1%)
:arrow_down:

...lPythonAndRelatedNonPythonKernelSpecFinder.node.ts
70% <0%> (+<1%)
:arrow_up:

src/kernels/helpers.ts
63% <0%> (+<1%)
:arrow_up:

src/kernels/errors/kernelErrorHandler.ts
63% <0%> (+<1%)
:arrow_up:

...ebooks/controllers/notebookIPyWidgetCoordinator.ts
88% <0%> (+1%)
:arrow_up:

...rc/kernels/debugger/debugLocationTrackerFactory.ts
100% <0%> (+3%)
:arrow_up:

... and 1 more


Status response audio and record always 400 Bad request

status response video 200 but  status response audio and record always 400 Bad requestStatus response audio and record always 400 Bad request. Help me!

same here! any suggestion?

what's the setup you have on your server? Last time I was using it with rtmp everything was working fine

what's the setup you have on your server? Last time I was using it with nginx rtmp everything was working fine

My server is working fine with rtsp of phone camera. But not working with usb camera by error 400


Improve UX for delegating votes

Opening this up as a potential "epic" to streamline the work around creating a v2 for the delegation of votes.
This DropBox Paper file contains all research towards accomplishing this epic, however this GitHub issue will hopefully serve as a central point of discussion for moving the accomplishment of the epic forward.

@virgile-dev @santisiri in the white paper there is the concept of Transitive Delegation and the ability for a delegator to restrict the use of their vote by a third party.
I was wondering whether we should concern ourselves with this feature for this iteration, and whether it's it's even possible to implement this feature before we connect the Sovereign front end with a blockchain back end?

The problem you can run into transitive delegation is getting trapped into some circular events (infinite loops). The most simple example is

Alice delegates to Bob, Bob delegates to Charlie, Charlie delegates to Alice. 🤯

There are more complex ones. By treating votes as tokens we can approach it better from a blockchain perspective.
That said: I'm always in favor on figuring out how to improve this key part of the UX.


Datepicker component close my md-dialog

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When use datepicker component inside md-dialog component do not close md-dialog component
What is the current behavior?
I am using datepicker component inside md-dialog component, when I click button to pick date that event close my md-dialog component
What are the steps to reproduce?
CODE:

This is md-dialog component

In this way behaves, displays the calendar at the same time as it hides the dialog and then closes the calendar

What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I am using:
Firefox 52.0.1
Angular 4.0.3,
Angular/material 2.0.0-beta.5-6121fa1  typescript 2.3.2
Is there anything else we should know?

Closing as a duplicate of https://github.com/angular/material2/issues/4530.


Use exec instead of run if possible

Check if the according web service is already running, then use exec as it's faster, otherwise keep using run.

Solved by f47746f7e949a1749d7ad5a87e727bd489c19bd0


Browser support ?

Does the library support browser rendering in future ?

Sorry, I don't really understand your question. This package is specifically designed for server-side rendering. React itself can do everything this module can in the browser already.
Or am I missing the point?

I tried to use renderToStringAsync on a React Component, but in browser, i got error about only-node dependencies is allowed. My React Component contains Suspense component with graphql data so i couldn't use default React's renderToString in this case.

Can't you just use React.render() to render the React component to a DOM element?
Why do you need to render to HTML?

This package's only dependency is react-dom, which works in browser. However this module does call ReactDOM.renderToNodeStream() - I guess that requires Node's native stream module within react-dom, hence the error you're getting.
I don't know how you've set up your browser bundle generation. But possibly you could get around this by telling webpack to use a browser-compatible alternative to Node's stream module e.g. readable-stream.
But, to be honest, I still don't understand what you're trying to achieve here.

@overlookmotel Because i want to retrive html content on browser from async React component. ReactDOMServer is synchronous so i couldn't get the html with async data, that's why i want to use renderToStringAsync on browser. The purpose is to convert html to pdf in my case.

Ah I see. Now I understand.
I suspect the problem is what I said above - react-dom/server's .renderToNodeStream() method, which this package uses internally, will not work in browser, due to reliance on Node's native stream module. The React docs say this is the case.
There's no way to remove the use of ReactDomServer.renderToNodeStream() in this module.
So I think only solution is to tell Webpack to substitute a browser-compatible alternative to Node's stream module e.g. readable-stream.
I can't advise you exactly how to do this, but I believe it's possible. You'd have to consult the docs for Webpack (or whatever other browser bundler you use).
Please let me know if you have success.

Another workaround would be to use ReactDOM.render() to render the component into a hidden div, and then read the HTML from the DOM with .innerHTML. A bit of a hack, but could work.

@overlookmotel Thanks for the feedback, i'll try both ways. I think why not creating another package for browser suppport, like react-async-ssr/browser ?

@revskill Unfortunately, due to the way React is built, it would require a lot of work to make a self-contained browser build.
Your use case is valid, but the core aim of this package is to enable server-side rendering (that's what the "SSR" in the name is), so I'm afraid I'm not willing to undertake that work to support a fairly niche case.
I'm going to close this issue now, but please do shout back with your findings about how you do/don't manage to get this working.


Event Request - Codeunit 10765 "Sales Invoice Header - Edit" - OnBeforeSalesInvoiceHeaderModify

We need a new Event Function in Codeunit 10765 “Sales Invoice Header - Edit”, named OnBeforeSalesInvoiceHeaderModify.
We need this
OnRun(VAR Rec : Record "Sales Invoice Header")
SalesInvoiceHeader := Rec;
SalesInvoiceHeader.LOCKTABLE;
SalesInvoiceHeader.FIND;
SalesInvoiceHeader."Special Scheme Code" := "Special Scheme Code";
SalesInvoiceHeader."Invoice Type" := "Invoice Type";
SalesInvoiceHeader."ID Type" := "ID Type";
SalesInvoiceHeader."Succeeded Company Name" := "Succeeded Company Name";
SalesInvoiceHeader."Succeeded VAT Registration No." := "Succeeded VAT Registration No.";
OnBeforeSalesInvoiceHeaderModify(SalesInvoiceHeader,Rec);
SalesInvoiceHeader.TESTFIELD("No.","No.");
SalesInvoiceHeader.MODIFY;
Rec := SalesInvoiceHeader;
UpdateSIIDocUploadState(Rec);
The event will be:
LOCAL [IntegrationEvent] OnBeforeSalesInvoiceHeaderModify(VAR SalesInvoiceHeader : Record "Sales Invoice Header";FromSalesInvoiceHeader : Record "Sales Invoice Header")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Swipe over iframe element

Hello, I got an issue that I cannot swipe slide with an embedded youtube video in it.
Looks like iframe is eating all touch, click events.
Is there any known workaround that allows us to use swipe to change slides?

Hi, Did you get solution?

Anyone found a solution for this problem?

Anyone found a solution for this problem?

Same problem.

So this is a problem of the iframe. When you trigger any event on it, iframe just swallows them like a black hole. You can't even capture the event, if you have an iframe as an endpoint of clicks and etc.
The only way I see ti solve this problem is to create transparent overlay above the iframe with absolute position, which covers it.  This will allow the swipe to work, but this will block the interaction with the iframe content. So if you want to handle some events in iframe with this solution, you will have to use postMessage API for it. Some discussions of this problem I found here
https://github.com/thebird/Swipe/issues/36


Customization of idea.vmoptions

Editing the idea.vmoptions file is a pretty common thing to do with IntelliJ et al, to do things like increase the JVM's max heap size. It'd be  nice if we could add parameters to the JetBrains packages to let you build a customized derivation specifying what goes into vmoptions.

Also, idea may ask to change the value of the parameters when it feels too cramped and it will try to write a new .vmoptions file. Of course it can not because this file is ro in the store.

@chris-martin can't you edit idea.vmoptions in your home directory instead?

Are there any updates to this issue, please?


Set Rust version to 1.71 and keep crates in sync with workspace

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.21 :warning:

Comparison is base (3a4686f) 90.17% compared to head (b37537e) 89.97%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #744      +/-   ##
==========================================
- Coverage   90.17%   89.97%   -0.21%
==========================================
  Files         113       81      -32
  Lines       16120    14671    -1449
  Branches      565        0     -565
==========================================
- Hits        14536    13200    -1336
+ Misses       1563     1471      -92
+ Partials       21        0      -21

Flag
Coverage Δ

uitests
?

uitests-ios
?

unittests
89.97% <100.00%> (+0.90%)
:arrow_up:

unittests-ios
?

unittests-rust
89.97% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

crates/wysiwyg/src/dom/dom_creation_error.rs
41.66% <ø> (+12.25%)
:arrow_up:

crates/wysiwyg/src/dom/insert_parent.rs
99.62% <ø> (ø)

crates/wysiwyg/src/dom/dom_methods.rs
96.12% <100.00%> (-0.01%)
:arrow_down:

crates/wysiwyg/src/dom/parser/parse.rs
97.90% <100.00%> (ø)

... and 35 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Chromium60.0.3112.50

Update to Chromium 60.0.3112.50

this is already merged into master via another branch so I'm going to close. Thanks!


Adding ':app' to include

I had to add this in order to be able to access the environment variables using Android Studio, if not it doesn't compile & sync.

@hhkaos You should not need to include a module named app, please elaborate on the error you are receiving and steps to reproduce when you do not include :app in settings.gradle.

Closing, please create an issue if you continue to have issues.


[DOM-51856] - costs update lifecycle

Customers who are not interested in extensive kubecost but using long-term storage will have a lot of cost data to the costs bucket anyway, while only the last 15 days of data will be actionable!
Add default lifecycle to limit long-term storage to 17 days.
Jira
https://dominodatalab.atlassian.net/browse/DOM-51856

Validated with jdbudget28539 and
jdbudget27853


[vcpkg_configure/build_make] Fix variable setup

What does your PR fix?
Fixes difficulties to set (environement) variables and make variables.

vcpkg_configure/build_make: Extend CONFIGURE_ENVIRONMENT_VARIABLES setup from windows targets to all platforms.    (Documentation mentions no restrictions.)
vcpkg_build_make: Fix OPTIONS for non-windows hosts. Drop invalid MAKE_OPTIONS.

Which triplets are supported/not supported?  With port x264 (which is not using autotools), I really need to have consistent behaviour if I want to be able improve cross build support.

If anyone does not object to this change, I will mark the reviewed tag later today.

Creating the environment string should probably be moved into its own function. But i don't object the movement just make sure the other make PR gets merged around the same time to minimize world rebuilds.

I found that there is still more Windows-only behaviour going on in with vcpkg_configure_make.
I want to go one step back and fully understand the current intention of CONFIGURE_ENVIRONMENT_VARIABLES (which is behind VCPKG_TARGET_IS_WINDOWS ATM) and z_vcpkg_append_to_configure_environment (which has a CMAKE_HOST_WIN32 ATM).
AFAIU it is related to the following:

For Windows hosts,
vcpkg tool clears most environment variables. This happens before calling CMake.
For Windows targets,
vcpkg_configure_make initializes well-known autotools environment variables by injecting them to the bash command line via z_vcpkg_append_to_configure_environment.
For Windows hosts,
z_vcpkg_append_to_configure_environment allows to override detected toolchain settings with the current environment variable value. (The environment variable is meant to come from the triplet.)
For Windows targets,
CONFIGURE_ENVIRONMENT_VARIABLES is a parameter which allows to inject additional environment variables to the bash command line, with a value from CMake variable (assumed to be set in the portfile),
for Windows hosts
possibly overriden by the environment variable.

Unfortunately, this is quite inconsistent, depending on whether target and/or host are windows.
Example: Targeting ENV{AS} in port x264:
Current master, without CONFIGURE_ENVIRONMENT_VARIABLES:

ENV{AS} in
Target:
android
windows
mingw
mingw
linux

Host:
windows
windows
mingw
linux
linux

unset
ENV{AS} out:
unset
:
:
:
unset

set
ENV{AS} out:
ENV{AS}
ENV{AS}
ENV{AS}
:  :red_square:
ENV{AS}

:red_square: Problem: ENV{AS} still uses the default : for mingw cross builds.
Current master, with CONFIGURE_ENVIRONMENT_VARIABLES AS:

ENV{AS} in
Target:
android
windows
mingw
mingw
linux

Host:
windows
windows
mingw
linux
linux

unset
ENV{AS} out:
unset
AS
AS
AS
unset

set
ENV{AS} out:
ENV{AS}
ENV{AS}
ENV{AS}
AS  :red_square:
ENV{AS}

:red_square: Problem: ENV{AS} still defined by AS for mingw cross builds.
A consistent pattern
I assuming that for setting well-known autotools variables in vcpkg_configure_make, we have to deal with default values, overrides from a portfile, and overrides from a (custom) triplet. A possible consistent pattern is:

The default values for setting a well-known environment variable ENV{<VAR>} is derived from the CMake toolchain, if needed.
An alternative value can be set from the portfile by setting CMake variable <VAR> and passing CONFIGURE_ENVIRONMENT_VARIABLES <VAR>.
An alternative to default values and portfile values can be set from the triplet via ENV{<VAR>}.

Changes
a. Don't override ENV{<VAR>} for windows (mingw) targets on non-windows hosts (:red_square:).
(Required for no. 3. Basically, we can savely assume that if ENV{<VAR>} is meant to be used if it is already set.)
b. Implement CONFIGURE_ENVIRONMENT_VARIABLES also for other targets than Windows (this PR, but incomplete without a.).
(Required for no. 2. Current workaround is to override ENV{<VAR> in the portfile, but this may override triplet settings.)
c. Depending on on what is "needed", set the well-known autotools variables also for other triplets than windows.
(Required for consistency with regard to no. 1. However, we currently do very well without it, and it may come with side effects. For example, x264 can't handle a CC with space in the path.)
d. The current implementation may inject a variable twice into the bash command line (for the default and for CONFIGURE_ENVIRONMENT_VARIABLES). IMO this should be merged.
e. Why do we have to inject the variables into the bash command line at all? I would suggest to just set ENV{<VAR>} directly. If we are concerned about side effects on other CMake code, we may clear what we set before leaving.

Ping @dg0yt for response. Is work still being done for this PR?

I wrote on long text on existing problems and possible directions. I'm still waiting for feedback.

So I stumble over this again now. If it is not possible to get feedback, I have to change my approach.

So I stumble over this again now. If it is not possible to get feedback, I have to change my approach.

I think you aren't getting feedback because this is marked as "draft" which makes it not show up on any lists we look at except the "close really old draft PRs" one.

(And also because this touches a bunch of autotools edge cases for which there is very little understanding among vcpkg's maintainers; as you point out with your tables above a lot of this is 'build and fix until it works' rather than careful design)

A) It is not ready for merge, and ATM I don't ask for a review of the implementation. But if needed, I can mark it "Ready for review".  (I also have ready-for-review PRs which are stuck in review, #26754.)
B) ATM the issue is not  an edge-case autotools particularity but a genuine vcpkg script question:
How to control the environment variables for the point where autotools are actually called?
It is the script which behaves inconsistenly. This can be resolved in various ways. I don't want to open a PR per alternative, but ask which one to choose.

(which has a CMAKE_HOST_WIN32 ATM).

that probably should be a MSVC check instead (or CMAKE_C_COMPILER_FRONTEND_VARIANT)? When the first vcpkg_configure_make was written vcpkg_cmake_get_vars didn't yet exist so compiler checks weren't really an option.

Unfortunately, this is quite inconsistent, depending on whether target and/or host are windows.

--host-triplet didn't exist (and with that VCPKG_CROSSCOMPILING) when vcpkg_configure_make was created. So I mainly cared about native builds and get them working.

prepends the parent dirs of well-known tools

that is a requirement since most stuff cannot handle spaces at all.

injecting them to the bash command

that was required because from testing in seemed like ENV{PROG} wasn't always used which is why CONFIGURE_ENVIRONMENT_VARIABLES was introduced to inject extra stuff in the bash command.
Additionally I didn't want to trash ENV{CC} etc in the environment if the compile wrapper is used.
(Especially since the environment needs to persist beyond vcpkg_configure_make into vcpkg_install_make in some cases; maybe we need to pass the env string around for that)
The real problem is the amount of different make file buildsystem:

pure Makefiles
pure Makefiles using libtool
(the above should probably always be converted to a CMakeLists.txt since ports using that are typically fairly simple)
configure based without using autotools (custom configure)
configure based using only autotools but not libtool/automake
configure based full autotools but with custom m4 scripts
configure based full autotools but with outdated m4 scripts / libtool
configure based proper full autotools

So my advice here is just make it consistent with the smallest change set possible ;) The whole make system needs a general overhaul and be moved into a helper port any way. The env setup needs to be moved into its own little function so that it can be reused more often for other stuff.


Input arguments synchronously

The default implementation of vim.ui.input is synchronously, but the document says it could be potentially asynchronous:

Lots of people uses dressing.nvim to override the default vim.ui.input to have a nice UI, which implementation is asynchronously, then the get_arguments in nvim-dap-go will always empty.
And vim.fn.input is designed to synchronously, which we should use.
So this PR simply change from vim.ui.input to vim.fn.input.

From your explanation, I suspect that the problem isn't related to the vim.ui.input but by the fact that the get_arguments() currently tries to run the input code in a coroutine. I don't use dressing.nvim and can't test this but can you give this a try?
local function get_arguments()
  local args = {}
  vim.ui.input({ prompt = "Args: " }, function(input)
    args = vim.split(input or "", " ")
  end)
  return args
end

I tried, still not wait input, and start debug immediately
https://github.com/leoluz/nvim-dap-go/assets/7448852/58b2b584-3c38-4780-b134-f6748fc1e727

It's because vim.ui.input runs asynchronously, and you return args immediately, which is {}

Makes sense. Thanks for validating this.

I think it's because the default implementation of vim.ui.input is synchronously, and the dressing.nvim override it to asynchronously

@imroc I merged the commit https://github.com/leoluz/nvim-dap-go/commit/a5cc8dcad43f0732585d4793deb02a25c4afb766 which touches the function that you were having problem.
Can you please update the plugin and validate if you still have the issue?

Great job, I have tested the latest commit, problem resolved:
https://github.com/leoluz/nvim-dap-go/assets/7448852/c5626a6f-9230-4f90-8539-ea55cfa39f02

cool! Tks for confirming and recording the video!