Update rustyline to 4.1.0 to fix nightly build

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8359c6e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #989   +/-   ##
=========================================
  Coverage          ?   64.98%
=========================================
  Files             ?       91
  Lines             ?    16500
  Branches          ?     3740
=========================================
  Hits              ?    10723
  Misses            ?     3291
  Partials          ?     2486

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 8359c6e...b9814ce. Read the comment docs.


In Git viewlet Ctrl+Enter doesn't execute the default action anymore

Windows + WSL
Latest Insider
I am pretty sure that this once worked since my muscle memory constantly hits Ctrl+Enter and nothing happens

Duplicate of https://github.com/microsoft/vscode/issues/212857


Bump imgui to v1.90.7 and fix pdb installation step

Description
Hi @giladreich,
Note that whilst building the project with /Z7 linker flag, the installation step failed with missing pdb. This is because it assumes the pdb files will always exists on Debug or RelWithDebInfo builds. Example command:
cmake .. -G "Visual Studio 17 2022" -A Win32 -DIMGUI_WITH_BACKEND=ON -DIMGUI_BACKEND_PLATFORM=WIN32 -DIMGUI_BACKEND_DX9=ON -DCMAKE_INSTALL_PREFIX=pkg -DCMAKE_MSVC_RUNTIME_LIBRARY="MultiThreaded$<$<CONFIG:Debug>:Debug>" -DCMAKE_MSVC_DEBUG_INFORMATION_FORMAT="$<$<CONFIG:Debug,RelWithDebInfo>:Embedded>" -DCMAKE_POLICY_DEFAULT_CMP0141=NEW

Setting it to OPTIONAL will only install the pdb files if they exists, which should work on all scenarios, even if one configures their Release build to generate symbols, which is not so common. I also improved it by using GNU standard installation dirs using the GNUInstallDirs install module.
Additionally I took the courtesy to update the imgui submodule.

Hi @stevewgr, thanks for the update and it also makes sense what you say about the pdb files. Your changes LGTM, but I'll double check once I get home whether any breaking changes or something new added between 1.88 and 1.90.

Hi @stevewgr, thanks for the update and it also makes sense what you say about the pdb files. Your changes LGTM, but I'll double check once I get home whether any breaking changes or something new added between 1.88 and 1.90.

I didn't notice any breaking changes, but as I'm not so familiar with this library, it will probably be a good idea if you double check as well.
Also a small nit-pick: it will be nice to rename this repo from cmake-imgui to imgui-cmake. Why? because if I have both imgui and imgui-cmake in the same dir, it sorts them nicely by name, making them easy to find between bunch of other dirs.


Bone segments rotating when moving the planes

When I move a plane the bone segments also rotate a bit. This should not happen. I only want to make the segments shorter or longer.

Hi mrtig.
You would need to be a bit more specific. When you move the plane in what direction (e.g. normal direction, orthogonal to normal direction, random direction) the bone segments rotate a bit?
This must be an optical illusion because of the pipeline Fibula pieces are created from fibula planes that are transformed to the mandible and fibula planes are created from mandible planes by applying the mandibleFrameToFibulaFrameRegistration transform, that is a linear transform. i.e. a mandible plane moved along a line, will make the fibula plane move along a line also. The linear transform also accounts for rotations of the first mandible plane in curveCrescentOrder of the two that make the boneSegment. That means, rotations to that plane will make the corresponding fibula piece 'rotate' (in reality the fibula cut planes do rotate and generate a new corresponding the fibula piece). No rotation of the fibulaPieces will happen if you just move the origin of the mandiblePlanes, that is not possible (unless you are using the option "make all mandible planes rotate together").
Using "more exact planning" will create a frame for each fibulaPiece. Making the mandible planes origin coincide with centroid of the fibula piece intersection with the mandible plane, that maybe it's more expected behavior. Anyway the software is a what-you-see-is-what-you-get editor and the surgical guides will be accurate on both modes.
I'm not sure if I understand the problem correctly maybe you can add some pictures to illustrate.
Mauro

Before:

After moving the first plane:

After moving the plane once everything was ok, but then I did a smaller movement to fine tune the position. I tried this many times. Sometime happened after first move, sometimes after second.

Please check if the mandible planes do rotate after you make the small adjustment. You can check this by creating a copy of the mandible planes befores moving them and using that to compare (looking at the interaction handles). If you can post a picture of both group of planes. Thank you

Now this happened

The planes didn't rotate.

Thanks Martin for researching on this.
If you find a reliable way to replicate this problems this is definitely solvable.
I suspect it could be because there is an alternative way of calculating the reconstruction when mandible-planes-position-changes are small that is there for performance reasons, may be I could create a new branch without this feature to see if the problem goes away but the best would be to find a reliable way to replicate the bugs.

I'm not being able to replicate this bug myself by hand. @cmfsx has this ever happened to you?
@mrtig when you post screenshots be sure they are of the fullscreen so I can see what reconstruction options you were using. If you cannot get to replicate the bug reliably a screenrecord of this bug before and after happening will be useful. Hope you can help me solve this.
Mauro

@mauigna06 Here's the video https://we.tl/t-kd6xLwS7RG

@mrtig I see. Thank you for researching into this.
Could you assure this happens only with the option "more exact planning" checked?

Sorry for ghosting... Down with COVID-19. Now recovering slowly. This has sometimes happened during various stages of the software. but i cannot say exact way of replication. i will do some research in to it and see too.

Hi Manjula.
Hope you get better
So are you saying this bug has always been there? It would be easier to track down if I would knew since what day it started doing this sometimes.
When you are recoved you may check into this, leave it for now unless you are bored and want to experiment
Mauro

I think this is an issue of the "more exact planning" option. I don't think I have experienced this before.

Ok. That's useful. Thank you.
I'll check. Please give me sometime.
Mauro

Hi @mrtig.
So I'm still not able to replicate the bug. Maybe you can send me your error prone scene and I can check it.
A better idea I have to debug this is that you make update the fibula pieces till you have a good reconstruction then go to the data module and clone the folder "Mandible2Fibula transforms" and rename it "Mandible2Fibula transforms correct" (also do this for the folders "Mandibular planes", "Fibula planes", "Cut Bones", "Bone Pieces Transforms" and "Transformed Fibula Pieces"), then translate with the arrow the first plane of your reconstruction back and forthward slightly till you get the wrong-rotation behavior (it is important that the change of position is small enough to not change the transform so much to make them hard to compare). then save the scene and send it to me. I'll check it and probably find the reason of this problem.
Mauro

@mrtig Another idea: I remade the dentalImplantsPlanning completely from zero when I set up its transforms. Maybe the error that produces this bug is not on that code. You could check that if you want
Mauro

@mrtig I think I found the source of the bug.
First you have selected S0 as fibulaLine which should not be done because it's position changes with each plane recalculaton (because you have a initialSpace greater than zero) that could lead to small changes on the result of the moreExactPlanning algorithm. Secondly, you are used to making the fibula point on Anterior-Posterior direction. This direction is hard-coded (used) to compute one of cross products that create the mandibleToFibulaRegistrationTransform, the second input of the cross product  is a vector with fibulaLine direction. That results in two very similar input unit vectors (have little angle between them) and this causes an instability of the cross-product result causing the change of angle in the transforms sometimes.
Related:
https://github.com/SlicerIGT/SlicerBoneReconstructionPlanner/blob/699c9970f163a14c7289dd8c8a7aa8b7346969d3/BoneReconstructionPlanner/BoneReconstructionPlanner.py#L2319-L2328
If my analysis is correct you should not face this problem by not using any Snumber line (e.g. S0,S1,S2,etc) as fibulaLine and not orienting the fibula on anterior-posterior direction. Please let me know if this is correct

@mauigna06, thank you for looking into this. I will test it with the next case.

@mrtig can you confirm if the diagnostic I did is correct?

@mauigna06 Sorry, there haven't been any cases for a while and I've been busy with some other things. I'll try to look at it when I get some time.

@mauigna06 Sorry, there haven't been any cases for a while and I've been busy with some other things. I'll try to look at it when I get some time.

Hi @mrtig ...
Do you know if the bug was catched? Do you have any other bug to report?
Have you helped in any other surgery using BRP since Febraury?

Hi @mauigna06 ,
It seems that there have been no cases during this time. Just a few days ago I got a new case. I will see if the bug appears with this case. I will let you know soon.

Hi @mrtig ... how is all going?
Did you encounter the bug again?
Mauro


use of the Consul, the configuration of the load is serialized error

fixed#123
use of the Consul, the configuration of the load is serialized error

@hyy829119 I will review this ASAP! Thank you for the PR and the interest in this project!

@hyy829119 which of your two pull requests shall I review? We should close one or are the for different things?


aerc: 0.18.1 -> 0.18.2

Description of changes
https://git.sr.ht/~rjarry/aerc/refs/0.18.2
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 330947 run on x86_64-darwin 1

1 package built:

aerc


[dask] Deterministic rank assignment.

Sort worker entries by dask worker ID. (task_id)

Close https://github.com/dmlc/xgboost/issues/7927 .

https://xgboost-ci.net/blue/organizations/jenkins/xgboost/detail/PR-8018/1/pipeline/
https://xgboost-ci.net/blue/organizations/jenkins/xgboost-win64/detail/PR-8018/1/pipeline

@hcho3 Could you please help look into the CI error? The storage seems full for PR and master branches.

Master branch seems to be fine now.


new ps update

Description of the issue
activity shows idle even after playing game for 2 hours
Addon version
1.3.3
Platform
ps system software 24.02-<IP_ADDRESS>-<IP_ADDRESS>.1
Logs of the issue (if applicable)
No response

i think my npsso expired let me refresh ; read through the other issues

updated the npsso still idle

I see that the code linked now has an option to exchange your npsso token. Does this mean we soon will not need to manually refresh it?
https://psn-api.achievements.app/authentication/authenticating-manually#exchange-your-npsso-token


vadc and vsbc behaviour under EDIV>1

Those instructions reads and writes implicit mask in v0.
EDIV extension defines that the masking is done at the element level and doesn't mention vadc/vsbc in not affected list.
How are those instructons intended to operate when EDIV>1?

Due to issue #155 , might be redefining adc/sbc, but EDIV issue remains.
Simplest solution is to cause illegal instruction exception for adc with EDIV>1, but needs more thought.


fix Exception while resolving variable 'toolbar' in template

Description
When sending a request using ajax, toolbar.js will send a request at the same time:
GET /__debug__/history_sidebar/?store_id=<id> HTTP/1.1
This request will throw the following exception when rendering the template.
It seems because toolbar is not passed in panel_context.
Fixes # (#1905 )

add toolbar into panel_context.

Checklist:

[x] I have added the relevant tests for this change.
[x] I have added an item to the Pending section of docs/changes.rst.

I think this makes sense, but I'm not 100% sure if you're just fixing an issue with a missing variable or if the functionality of loading panel contents with RENDER_PANELS = True and older requests was broken previously.
If it's the former I'm good with the PR, but if it's the later we'd really want a test to make sure we're not regressing here.

I think this makes sense, but I'm not 100% sure if you're just fixing an issue with a missing variable or if the functionality of loading panel contents with RENDER_PANELS = True and older requests was broken previously.
If it's the former I'm good with the PR, but if it's the later we'd really want a test to make sure we're not regressing here.

My local test was fine. After modification, no exception logs can be seen in the same scenario.
However, I only tested the scenarios I encountered, and I did not conduct a comprehensive test.

Thanks for identifying a solution! Would you be able to include a test that confirms that this is fixed? It's hard to accept a change without being able to see what it's fixing.

Sorry, this test doesn't look easy to add.
According to the Django Template rendering process, the exception django.template.base.VariableDoesNotExist is handled gracefully. This exception is not thrown and is replaced with a default value, which is an empty string if not configured.

This results in an empty string being obtained at the exception and going to the false branch, which is in line with the expected logic.

According to debug-toolbar's code:
if panel_content.html is rendered under a non-ajax request, there will be a toolbar variable in the context, which is normal.
If panel_content.html is rendered under an ajax request, the toolbar variable is missing from the context, eventually leading to the false branch. In ajax request, toolbar.should_render_panels value is always false.
It seems that this exception does not trigger any problems. Only in debug level logs, you will see relevant error logs.
To sum up, it won't hurt if this anomaly is not fixed.

After turning on Debug level logging, VariableDoesNotExist errors appear frequently during use. But it does not affect the use. I think my PR is redundant. It can be closed.

Just curious why you closed this? I don't think your PR was redundant at all. Error should not be thrown unless there is an error.
I just spent half my day trying to figure out this issue, luckily I stumbled on your PR.

@Riskcomplexx would you be able to open a PR with the fix and a test to prevent a regression?

Just curious why you closed this? I don't think your PR was redundant at all. Error should not be thrown unless there is an error.
I just spent half my day trying to figure out this issue, luckily I stumbled on your PR.

@Riskcomplexx
During the subsequent debugging process, I found that this exception did not affect the use. And there is already code to handle this exception. You can refer to the analysis in my comment above.
In addition, the test for this PR is not easy to add. I don’t have much time to complete this test, so I can only close this PR.


Unclear error with LEVENSHTEIN_MATCH

My Environment

ArangoDB Version:        3.7.5
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start in Docker
Configuration:               nothing specific
Infrastructure:               AWS - but issue is currently in local dev env
Operating System:        Ubuntu 20.04
Total RAM in your machine:        16Gb.
Disks in use:        SSD
Used Package:    Docker - official Docker library

Component, Query & Data
Affected feature: I have an unclear error while running the next query, which seems, according to the docs, correct: Query: AQL: collection or view not found: juniors (while instantiating plan)
AQL query (if applicable):
FOR junior IN juniors
    SEARCH LEVENSHTEIN_MATCH(junior.firstname, @firstname, 2, false)
        OR LEVENSHTEIN_MATCH(junior.lastname, @lastname, 2, false)
    SORT BM25(junior) DESC
    RETURN junior

Dataset:
The juniors collection exists (±1200 docs), and have two fulltext indexes on firstname and lastname. Never had issue before, making queries & modifications to the collection without problem.
Just wanted to implement a "fuzzy search" to help reducing duplicates while encoding people in the collection (complex process on our side).

Thanks in advance!

you probably wanted to create a view and use that in this query?
so you would name the view juniors_view, and use that in this context?

Ok, my bad, I understood the feature completely wrong, haha.
Thanks for your help, and sorry for the useless issue.

no issue is useless - it in doubt shows a missing link in the documentation. Which way did you go?


Get-DbaDatabase - NoBackup Params Output Db If Mismatched Case In T-SQL Command

Verified issue does not already exist?
Yes
What error did you receive?
Error wasn't received. Database with a backup was output when when the -No*Backup* params are used. I think this occurs due to the below two lines, namely the -cnotin code. The msdb.dbo.backupset.database_name respects the case used in the T-SQL command.
https://github.com/sqlcollaborative/dbatools/blob/1dfc259c25968d617722ae040018fce5a3fada4b/functions/Get-DbaDatabase.ps1#L317
https://github.com/sqlcollaborative/dbatools/blob/1dfc259c25968d617722ae040018fce5a3fada4b/functions/Get-DbaDatabase.ps1#L324
Steps to Reproduce
New-DbaDatabase -SqlInstance localhost -Database TSQLCASETEST
Invoke-DbaQuery -SqlInstance localhost -Query "BACKUP DATABASE tsqlcasetest TO DISK = '$HOME\tsqlcasetest.bak'"
Get-DbaDatabase -SqlInstance localhost -NoFullBackup

Are you running the latest release?
Yes
Other details or mentions
Not really sure how to handle. It seems like there isn't a perfect solution without getting the case sensitivity of every database, maybe? That would seem like it would get really messy.
In my own environment, my solution was to change the code on the one server that didn't use the correct casing.
What PowerShell host was used when producing this error
PowerShell Core (pwsh.exe)
PowerShell Host Version

Name                           Value
----                           -----
PSVersion                      7.1.5
PSEdition                      Core
GitCommitId                    7.1.5
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

SQL Server Edition and Build number
Microsoft SQL Server 2017 (RTM-CU20) (KB4541283) - 14.0.3294.2 (X64)
        Mar 13 2020 14:53:45
        Copyright (C) 2017 Microsoft Corporation
        Standard Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)

Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64)
        Feb 25 2011 13:56:11
        Copyright (c) 1988-2008 Microsoft Corporation
        Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

.NET Framework Version
.NET 5.0.11

fix is straight forward.  SQL doesn't allow two databases with the exact same characters to be on the same server i.e. [Test] and [TEST]. but [Test] and [ Test] can.
Not sure why cnotin was used, it doesn't need to be case sensitive. and Get-DBABackupHistory explodes when you've got a databses with the same name, but one has a leading space anyways so it would blow up differently.
$array = @(" hello")
"hello" -in $array
returns false
so it's not needed even for that edge case.
$inputObject = $inputObject | Where-Object { $.Name -notin $lastFullBackups.Database -and $.Name -ne 'tempdb' }
I'll make the change and put in a pull request.

If you are in an instance with case sensitive collation you can have a database with the same name but different casing.  That is why we use a case sensitive comparison operator in PowerShell.

get-DbaSqlInstanceCollationStringCompareTools.txt
@wsmelton
that's Not any more Accurate than using in.
Would this be helpful, since it gives you an accurate string comparison for any given Collation

I'm not referring to comparing an array to a single value. I'm only talking about case-sensitive comparison. In that there is a significant difference between using -notin vs -cnotin. By default PowerShell comparison operators in, eq, etc are all non-case comparisons. When you using any of them prefixed with c then it turns it to do a case-sensitive comparison. So there is a strong difference between using -notin vs -cnotin.

If I have a SQL Server instance with case-sensitive collation I can create the 3 databases in this example without errors. Have you tested the change in your PR against an instance of SQL Server that defaults to use a case-sensitive collation?

PR  andreas approved uses collation Check, to decide whether or not to do -cin  or -in
it's still wrong though.
waiting for it to be merged or for them to tell me to do it the way that handles all collations correctly.
Prior to pull it handled CS_WS_AS  Correctly only Maybe the KS ones too , but I don't have any of those.
as currently approved  handles CI_WS_AS, CS_WS_AS correctly
But it's still wrong
Doesn't do anything for AI,WI
and most instance collations used are probably WI
that's why I asked if we should just use the String Compare SMO gives us for any collation we want. that way it's always right and you don't have to write a bunch of if else stuff
so this bit doesn't grow to be like 1k lines long trying to replicate string comparisons that SMO gives us for free
"""
if ( $server.Collation -like "_CS" -or $server.Collation -like "_BIN"  ) {
# Collation Check, when Case Sensitive collation use cnotin for database name comparision
$inputObject = $inputObject | Where-Object { $.Name -cnotin $lastFullBackups.Database -and $.Name -ne 'tempdb' }
} else {
$inputObject = $inputObject | Where-Object { $.Name -notin $lastFullBackups.Database -and $.Name -ne 'tempdb' }
}
""
it would instead be
"""
$x = get-DbaSqlInstanceCollationStringCompareTools $server
$inputObject = $inputObject | Where-Object { $x.notin( $.Name,$lastFullBackups.Database) -and $.Name -ne 'tempdb' }
"""
and that handles any collation the instance has correctly

If it is still wrong why are you not submitting a PR to completely fix it?

well I've never submitted a new Module Is what I have fine?

get-DbaSqlInstanceCollationStringCompareTools
$inputObject = $inputObject | Where-Object { $x.notin( $_.Name,$lastFullBackups.Database) -and $_.Name -ne 'tempdb'

The above, looking at your text file, is excessive and won't scale with large environments.

is it the in function or equals, or that they're Methods on a PscustomObject?
Or just that the names terrible?
Function

The problem with using SMO's StringComparer is that depends on Microsoft.SqlServer.Management.SqlParser I believe which was not ported to dotnet core. So not sure if using that will end up getting different results based on culture and dotnet version running on a given machine.
I'm also not fond of using collation checks // @potatoqualitee @andreasjordan // because those are going to give different results for any given server and possibly in Azure SQL too (if they limit the collations you can use compared to on-premises).
What is the issue with using PowerShell native string comparison again?

The function you have @chightow is performant in it is creating a new object based on the input. Get-DbaDatabase is already a function that has performance issues natively from SMO enumeration. I think newer versions of SMO they are improving this but there are some environments I've touched it just can't be used.
If you have an internal function that has to iterate over each input and then use a script method on that object it is a performance hit from PowerShell side. Array comparison in PowerShell is more efficient as-is.

My point of view:
On case insensitive instances (should be most cases) users can run the backup command with different case for the same database, so data in msdb has different (case) values for the same database. So comparing should be case insensitive too.
On case sensitive instances (probably edge case) users might be creating two databases with the "same" name - or don't they? (Don't have a case sensitive instance today) so we should compare case sensitive as well. That was my idea when I used "-cin" in my last change some months ago.
The current change should work for both cases.

@wsmelton  I'll check, I think it's in .net core got to start up wsl.

The library we depend upon for SMO is packaged with the module. You can find them in the bin\smo directory.

I was playing with Get-StringComparer() in pwsh and it was working. I've got .NET 6.0.0.

@wsmelton
So basically this is the reason
"""
create table #Collations
( [name] varchar(255), [ceq works] bit, [eq works] bit, [neither work] bit default 0  )
insert into #Collations
( [name], [ceq works], [eq works] )
SELECT name, case when name like '%_BIN%'
or (name like '%_CS%' and name like '%_AS%' and name like '%_KS%' and name like '%_WS%') then 1 else 0 end as [ceq works],
case when name like '%_CI%' and name like '%_AS%' and name like '%_KS%' and name like '%_WS%' then 1 else 0 end as [eq works]
FROM sys.fn_helpcollations()
update #Collations
set [neither work] = 1
where [ceq works] = 0
and [eq works] = 0
Declare @CollationCount float = ( select count(1) from #Collations )
declare @Ceq float,
@eq float,
@neither float
select @ceq = count(1) / @CollationCount  from #Collations where [ceq works] = 1
select @eq = count(1) / @CollationCount  from #Collations where [eq works] = 1
select @neither = count(1) / @CollationCount  from #Collations where [neither work] = 1
select @ceq100 as [ceq works percentage], @eq100 as [eq works percentage], @neither*100 as [neither works percentage]
"""
even with collation check we're leaving ~80% of possible collations returning incorrect results at least on windows hosting sql 2019

Don't think I even need a real instance for it to work
would this be better?
Function Get-DbaCollationEquals
{
param( [string]$Collation, [string]$String1, [string]$string2,[Microsoft.SqlServer.Management.Smo.Server]$SqlInstance )
if ( -not $SqlInstance ) {
$SqlInstance = New-Object -TypeName Microsoft.SqlServer.Management.Smo.Server
}
return $SqlInstance.getStringComparer($Collation).Compare($string1, $string2) -eq 0
}
Function Get-DbaCollationNotEquals
{
param( [string]$Collation, [string]$String1, [string]$string2 )
return -not (Get-DbaCollationEquals -Collation $Collation -String1 $string1 -string2 $String2)
}
Function Get-DbaCollationIN
{
param( [string]$Collation, [string]$String, [string]$array )
$SqlInstance = New-Object -TypeName Microsoft.SqlServer.Management.Smo.Server
foreach ( $x in $array ) {
        if (Get-DbaCollationEquals -SqlInstance $SqlInstance -Collation $Collation -String1 $string1 -string2 $x) {
            return $true
        }
    }
    return $false

}
Function Get-DbaCollationNotIN
{
param( [string]$Collation, [string]$String, [string]$array )
return -not (Get-DbaCollationIN -Collation $Collation -String $String -array $array )
}
example:
$Collation = 'SQL_Latin1_General_CP1_CI_AI'
Get-DbaCollationEquals -Collation $Collation -String1 'a' -string2 'Á'
true
'a' -eq 'Á'
false
'a' -ceq 'Á'
false

We are trying to solve something that is a non-issue here. Just revert the comparison operator back to -notin and we fix this issue. Collation is irrelevant for this direct issue because the comparison is being done in PowerShell, not in SQL Server.
We have no reason to try and perform string comparisons based on collation in SQL Server when the data is being compared within PowerShell's processing.
Summary of points:

If we are using PowerShell comparison operators the collation of SQL Server is irrelevant.
SMO class Server.Databases will return a list of database names, irrelevant of the collation.
Users that rename a database and then try to get the last backup date are on their own; nothing we can do about bad data in their backup history.
We are calling Get-DbaDbBackupHistory which is running a T-SQL statement to pull the data. We don't control what casing that data comes out as so whether you have Test, TEST, or TEst use of -notin will cover it.
We cannot be expected to compare Test with Test  (or Test It with TestIt), that is a data issue that the user will have to address or account for by use of other command(s) to get the last backup date.

So then the case of having two databases where one is named Test and one is TEST on a CS Collation wouldn't be covered? I would assume this situation is mostly impractical in a production instance.

Don't think I even need a real instance for it to work
would this be better?
Function Get-DbaCollationEquals
...

To your point @chightow, I would assume you wouldn't derive the functions and use the already derived $server object in the function Get-DbaDatabase.

@mattcargile
Just depends on what you want to work
-in  is faster than Get-DbaCollationIn by about 130ms on comparing an array with 32767k elements
`
$start = [long] 1
$end = [long] 32767
$number = @()
while ($start -lt $end){
$Number = $number + @('1')
$start = $start + 1
}
Measure-Command { '0' -in $number }
measure-command { Get-DbaCollationIN '0' -in $number }
`
probably can make it go faster, but it'll be more confusing to read.

@mattcargile Just depends on what you want to work
-in is faster than Get-DbaCollationIn by about 130ms on comparing an array with 32767k elements
` $start = [long] 1 $end = [long] 32767 $number = @()
while ($start -lt $end){ $Number = $number + @('1') $start = $start + 1 } Measure-Command { '0' -in $number } measure-command { Get-DbaCollationIN '0' -in $number } ` probably can make it go faster, but it'll be more confusing to read.

I think we are missing each other. I'm just talking about how to incorporate the spirit of your functions into Get-DbaDatabase as opposed to general performance of the comparison outside of the applicable dbatools function.

So then the case of having two databases where one is named Test and one is TEST on a CS Collation wouldn't be covered?

If we change it back to -notin then we cover both, again collation is irrelevant.

So then the case of having two databases where one is named Test and one is TEST on a CS Collation wouldn't be covered?

If we change it back to -notin then we cover both, again collation is irrelevant.

Well wouldn't it give inconsistent results between these databases if one was backed up and one wasn't. It would remove both of them from the output when only one of them was backed up.

Well wouldn't it give inconsistent results between these databases if one was backed up and one wasn't. It would remove both of them from the output when only one of them was backed up.

You are not going to resolve nor should we be responsible for every possible variation. If a DBA chose to build a SQL Server instance with case-sensitive collation and then chose to create a database as TEST and one as Test...that is on them and they should have known better.
I see no justification for adding in overly complex string comparison to something that is a bad practice from the start. (Referencing duplicate database names at different casing)

If we find more than one database when trying to gather the last backup date we should throw out a warning and not include the data at that point. If we cannot consistently pull a last backup date it should not be provided at all.
We are talking about a single property on the Database SMO object, that we are adding for convenience to try and match the functionality in SSMS. If we cannot do that on a given run because of data inconsistency then we should not include unverified data in the output. The user can always just run Get-DbaDbBackupHistory on their on to get the same details (and be much more efficient/performant compared to using Get-DbaDatabase).

https://github.com/sqlcollaborative/dbatools/pull/7945/commits/53494e30fd3c192836968667b1b100a6f161d6a9
is just the change from cin to In, Added the Collation check, because of @andreasjordan's points about _CS collations.
thought about why it wasn't giving correct results for _AS collations or  _WI collations
started playing with getstringcomparer() and it gave the expected results which is why I asked if we wanted to use it.

If it is still wrong why are you not submitting a PR to completely fix it?

So I asked how to approach it
just trying to help
You can roll it back

I always prefer considering all use-cases if possible. If technology such as case sensitivity allows a DBA to create a database named TEST and a database named test, that is a valid use-case that we can aim to support, especially if we have contributors who are eager to discuss and address the problem.
While I agree that matching in PowerShell can be a suitable solution, it seems that there is a desire for a more specific, more encompassing solution. If that's possible and there's a willingness to solve this in a way that does not break current functionality, I'd like for us to continue exploring that. This seems like a fun problem to solve.


Add Nong Song:

Song Name
Christmas kids
Artist Name
Roar
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=9o0pXI5jkyg
Direct File Link
https://www.mediafire.com/file/csglus02prp63j7/Roar_-_Christmas_Kids_%2528Lyrics%2529.mp3/file
Song ID
1001
Start Offset [ms]
No response
Extra
I am trying to get this song in as a NONG this is my second time doing this and i saw that you could use this id.

accept


Stress-test and variables

Hello,
Sorry for my bad english, i hope you understand my question.
I used few days agos cypress-utils stress-test.
But i can't find any solution for use variable.
For exemple i want to call one test X times but for X differents  customers and X differents users.
It's not possible.
I would like to be able to pass some kind of array with environment variables URL, User, PWD for example
thank's

Hey @Cedric-Brunel 👋🏻
I understand your request. I think it's a great idea. Perhaps cypress-utils can pass the run index as an environment variable. In your Cypress spec you could use this value to index the mock data corresponding with each run.
I'm not sure this is something I can take the time to implement, but I'd be happy to help get a PR merged if someone wants to contribute this feature.


decodeFrame is slow on Android with MediaCodec

I'm using H264Decoder to decode the first H264 key frame from MediaCodec's output. As soon as the first time this if condition (info.flags & MediaCodec.BUFFER_FLAG_KEY_FRAME) != 0 is true, I allocate a new ByteBuffer to generate a complete key frame data for H264Decoder. Here is my partial code,
final MediaFormat mf = codec.getOutputFormat();
final ByteBuffer SPS = mf.getByteBuffer("csd-0");
final ByteBuffer PPS = mf.getByteBuffer("csd-1");

SPS.position(0);
PPS.position(0);

final ByteBuffer outputBuffer = codec.getOutputBuffer(index);
final ByteBuffer newOutputBuffer = ByteBuffer.allocate(SPS.remaining() + PPS.remaining() + info.size);
outputBuffer.position(info.offset);
outputBuffer.limit(info.offset + info.size);
newOutputBuffer.put(SPS);
newOutputBuffer.put(PPS);
newOutputBuffer.put(outputBuffer);
outputBuffer.position(info.offset);
newOutputBuffer.position(0);
final H264Decoder decoder = new H264Decoder();
final Picture out = Picture.create(videoWidth, videoHeight, ColorSpace.YUV420);
final Picture real = decoder.decodeFrame(newOutputBuffer, out.getData()); // this line takes a lot of time (>30sec)
final Bitmap bitmap = AndroidUtil.toBitmap(real);

Perhaps I'm wrong about the usage, but how to do this correctly?

you are using the api correctly as far as i can see
what is the resolution of the image you are trying to decode?
anything above 480p should be very slow
bear in mind the following: https://github.com/jcodec/jcodec#performance--quality-considerations
it basically says: "it's written in pure Java so dont expect the highest performance"
this is especially true for Android implementations of jvm which are not known for the highest performance
try running the same code on a desktop jdk - it should be considerably faster
we do have renderscript/opencl implementation of decoder on the roadmap but haven't really started working on it.
things you can do to help

profile the code and find the most performance critical part
spend some of your time to discover renderscript/opencl and how it can be used to optimize decoder performance

things we can promise in return if your renderscript/opencl code speeds up decoder on android:

put your name on jcodec project page like this  "eternal respect to jedi master of hardcore codec development goes to @magiclen "
warm and fuzzy feeling of sense of accomplishment


fix deployment to only run on master and Cog branch, and not for pull requests

@fniephaus: can you check my bash foo?


removing old test code

#8

Hi @svwielga4, thanks for this! Looks good.
Was there a reason the package-lock.json changed, or is that just that you had different versions for some reason?

Sorry if it caused any confusion = (, I wasn't exactly sure how I changed it. I'll make sure to throw away any unwanted changes in the future. Also thank you for putting this up on the Mozilla sprint, very cool of you = )

No problem, thanks for helping :+1:


Config dashboard

Description
It would be useful to have a config/monitoring dashboard setup to use with lake. In the MVP version the user can add their config for the plugins (api keys, project ids etc) easily via browser inputs, and with easy guidance. Then in future versions the goal would be to integrate more configuration elements such as global config, grafana config, process monitoring, and maybe some other things like running server commands.
Describe the solution you'd like
Potential idea for the best flow of this dashboard:

We store executable files on github for each os
user runs it, it starts docker container + opens up browser with this interface
users can shut it down via ui commands when done (as an option)

Describe alternatives you've considered
We have considered a CLI tool also for config settings. This may still be a good thing to build (for a focus on devs). But at least for now, devs can navigate config files directly just fine. This proposed UI for non-dev users is more important.
Screenshots
Plugins (would be integrated something like this, in a minimal way at first)

Couple other ones we could do after

Closing this as the first version has been implemented and we're working on the improvements.


Use caching to speed up example builds

We used to have caching for this purpose, but found out that it was causing beta and nightly to fail to build. It was removed in https://github.com/acmcarther/cucumber/pull/24 but should be readded (in a functional way) to get reasonable build times again.

It might be possible to manage this by using the new cargo workspaces feature.
https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md
The jist is that it lets everything use the same target directory, which is what #24 used to do (but badly).


Update l2tscaffolder to use new reporting

The Turbinia Task templates in https://github.com/log2timeline/l2tscaffolder need to be updated to use the new Task report templating.

I'm not sure if anyone is really using l2tscaffolder anymore, but it does look like it's been updated (for Timesketch) within the last year.
@hacktobeer I know you have plans on working on the developer experience for Tasks, do you think it's worth incorporating l2tscaffolder into that, or should we just close this out?

Was not aware that this existed. I am not that much of a fan, seems overkill for us and another thing (outside of the Turbinia repo) to maintain.

Sounds good, let's just close this out then for now.


Create index for performance amelioration on database

After a load average incident on our appliance we applied those indexes on the vmdb_production database :
create index on event_streams (type,target_id,target_type);
create index on miq_schedules (updated_at);
create index on blacklisted_events (ems_id,enabled);
create index on key_pairs_vms (vm_id);
create index on miq_requests (tenant_id,approval_state);
create index on miq_roles_features (miq_user_role_id);
create index on miq_queue (state,handler_type,handler_id);
create index on network_ports (device_id,device_type);
create index on vms (tenant_id);
create index on entitlements (miq_group_id );
create index on endpoints (resource_id,resource_type);

It would be great if those could be integrated by default in the appliance.
Thanks

@dmetzger57 please review

@kbrock here's the index issue we spoke about, please review

not ready to let this go yet

@miq-bot remove_label stale

@miq-bot add_label pinned

@kbrock what is the status of this issue?

@chessbyte the indexes look incomplete.
I could add all of these (except event_streams - those indexes would be too expensive if it was wrong).
I unfortunately don't have a way of knowing if these indexes help all customers, or even hurt some


Docs: remove irrelevant text

🛠 Fixes Issue #2
👨💻 Changes proposed

Removed languages not in a table

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

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


No reminders after Pie upgrade

Samsung Galaxy S8, Android 9.0 Pie
Tasks, versionCode=74807, versionName=1.1.18-7-g7fce3d72
Been using this for years and it worked fine before the Pie upgrade, without having battery optimization disabled. Seeing other older tickets in here, I disabled battery optimization, but it still doesn't work, even with the app still open when the reminder time hits. I got several crashes in the background not long after upgrading, which I submitted via Google, but I stopped getting those. I suspect it's just suppressing them now.

No clue what triggered it in the first place, but I appear to have gotten it working again by deleting the app data then removing and readding my CalDAV account.


Hello. Which step in the second image does the portion marked in the red box in the first image refer to? The third step in the second image does not use it as a condition.

@jesuisalexjamet


Issue on page /notebooks/05-Python_I.html

typo under "Errors that cannot be debugged"
Run this block of code yourself in the ipython console using %cpaste -> %paste.

It should be %cpaste - not  a typo.


Masonry overscanByPixels no effect

Hey, I'm using the masonry and it works great.  As far as I understand, overscanByPixels should virtually enlarge the viewport so the images should already be loaded when I scroll to the next rows, but it doesn't. Even if I set a value like 1000, neither vertical side (top/bottom) will be loaded in advance, only when scrolled into the actual view, the images are loaded and pop up.
Is this a bug?

Hm... it looks like you're right. Masonry uses overscanByPixels to scan ahead and behind but looking at the DOM, I don't see any more elements being rendered if I crank up overscanByPixels and the unit tests for this are super weak.

Ah, I think this was caused by passing the position cache a negative number.

Fixed in 9.11.1


Batoto: Fix popular/latest in English (United States)

Closes #208
It is not possible to differentiate between en and en_US in searching, however, because both results do not include a country flag.
Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio

imo should just remove the en_US version

There are a few entries specific to en_US though ¯\_(ツ)_/¯ it's not much but it's more than Esperanto, which we also support

There are a few entries specific to en_US though ¯_(ツ)_/¯ it's not many but it's more than Esperanto, which we also support

wouldn't they appear in the en version?

There are a few entries specific to en_US though ¯_(ツ)_/¯ it's not many but it's more than Esperanto, which we also support

wouldn't they appear in the en version?

Only when searching.

Only when searching.

Can merge them.
siteLang="en_US,en" for en


add me

Added myself :)

Leaving a note for future if needed - this PR removed the redundant use of "Feature" across that column for several miners. Thanks @Eliovp


MH-12622, Surefire Versions Should Not Diverge

There are different versions of the Maven's surefire plugin specified in
the main pom.xml. This patch updates all versions to the newest
version specified.

@gregorydlogan This seems to be the oldest open pull request. Is there anything preventing you from merging it?

Nope, just forgot it was here.  Testing now, will merge once it's done.


refactor(auth2): More smoothing out of auth screens

Description
This cleans things up a bit more:

Avoid the use of useFormik hooks per the docs, and instead rely on standard <Formik>, which has performance benefits
On submit, collapse the keyboard, wait, then show keyboard again when the next screen appears. This is pretty standard UX, and the only way we can get around the UI jank involving the keyboard QuickType bar (suggestions)

@iskounen - this one is pretty uncontroversial so gonna merge to get a beta out before monday but happy to follow up on any comments 👍
cc @artsy/diamond-devs

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 3ed3bc67357e071b2afba1625112520987a06268


[Feature]: Update notebook for Image animation

Is there an existing issue for this?

[X] I have searched the existing issues.

Is your feature request related to a problem? Please describe.
There are some notebooks for reverse image search with the gradio showcase and deploy fastapi with towhee.api, can you update the notebook for Image animation?
Describe the solution you'd like.

Build an image animation engine
Run Animegan or Cartoongan to change the style of the image and release the Gradio showcase.

Deep dive image animation
Set up running pipelines in parallel and deploy fastapi services using towhee.api, it would be better if video animations could be supported.

Describe an alternate solution.
No response
Anything else? (Additional Context)
No response

Hey, I wanna take up this issue

Welcome to contribute :)
Feel free to contact me if you have any questions, or join slack in the development channel to discuss.

Hi @harivamsi9, any progress to share? One thing is that there is a simple notebook about anime-style transformers you can refer to.

Is this issue available?
Can I work on this issue?

Hey, I am still working on this issue

ok

any uodate?

/reopen

/reopen


Add Python Poetry test to flowzone.

Add python_versions to inputs.
Add Python info to README.
Add Python poetry test project to tests.
Change-type: minor
Signed-off-by: Genadi Naydenov<EMAIL_ADDRESS>

Summary:

Add Python Poetry test to flowzone.
Deduce suitable Python versions (=>3.7,<3.11) for the test.
Add Python (Poetry) test project to flowzone tests.
Update the README.md accordingly.


about IUnknown

Hi kenny,
first , thanks for this great tool . I'm learning this tool these days and got a confusion :
Is IUnknow belongs to Windows namespace ? if so , how does following line(from base.h/2293) work ?
...
namespace ABI::Windows {
struct __declspec(uuid("af86e2e0-b12d-4c6a-9c5a-d7aa65101e90")) __declspec(novtable) IInspectable : IUnknown
...
many thanks!!!

Oh, I know it's in fact ::IUnknown


Source suggestions cluster direct from DB

Allow SuggestionsSource to use system property and env var for db url
Have db and suggestionsFrom as class-level fields

suggestionsFrom takes a slick SQL string and adds obj marshalling

Re-impl similarTo to find similar suggestions from db, not in-mem

@xkjyeah - can you give this a read too?


A FORK TO CONTINUE THE DEVELOPMENT IS OPEN NOW

Since the future of this repository is unclear I created a fork to continue the development as an interim solution. For now, the plan is to merge any changes into this repository eventually. If that doesn't work a permanent solution must be found.
Pull requests are welcome!
plot-rs/plotters

Thanks for the initiative @AaronErhardt . Since there are multiple crates involved, perhaps it would make sense to maintain the fork under an organisation?
That way there'd also be a unification, as right now plotters is here and the other crates are under https://github.com/plotters-rs .
I think ideally all related/dependent crates would be under one organization on GitHub.

(I wonder if it is so wise to split all the crates in many repository. Perhaps it would be easier to merge them all in one workspace repository. But maybe that's just because i'm a fan of mono-repos)

I've created a new organization now and updated the link. A monorepo could have some advantages but if we want to reunite the repositories eventually, this might make things complicated. If that becomes the permanent solution we can think about this again.

I noticed you haven't changed the crate name. Do you not plan to publish the fork to crates.io?

plot-rs is already reserved as a name, but I want to wait a little bit for things to settle. I still hope we can continue under the name plotters. Also, we first need a reasonable amount of improvements before a new release makes sense.

It's great to see some progress here. Thanks for setting things in motion!
I'm aware that this is supposed to be an interim solution, but, in many cases, there's "nothing more permanent than a temporary solution". Just in case no neat resolution is found (i.e. the original repo remains inactive), I would like to suggest to consider adding the fork to the Rust Bus project, as I mentioned in https://github.com/38/plotters/issues/333#issuecomment-1097921841. It would be a shame to eventually end up in a situation where another fork of this new fork is needed.

Thank you so much fro stepping in, after close to one year since the last sign of life (on this repo) from the maintainer.
It's unfortunate that the community is left to deal with it, with no real guidance from someone who would know the ins and out of the codebase.
But again, thank god for FOSS that we can have a shot at keeping it rolling.

Hi Thanks everyone, I don't have bandwidth to maintain the package currently due to some personal issues.
I am very sorry for the inconvenience of you guys during my absence.
I think it's better for the package to have a development team, not only me. Actually I have an organization for https://github.com/orgs/plotters-rs. And I think I am going to transfer the ownership of the package to that organization. And I am calling for participation: I am looking for who want to help me to provide better support for this crate.
Please let me know if you are interested in such a role. Thanks in advance.
Hao

@38 thanks for your response! You've really done an awesome job with this crate and it would have been a shame if we had use a fork permanently.
I hope it wasn't a bit too eager trying to get your attention and I wish you best of luck regarding your personal situation.
Btw. I could write a small blog post we can post on Reddit and TWIR for example to get more people on board.

Btw. I could write a small blog post we can post on Reddit and TWIR for example to get more people on board.

That's awesome, also once this project is under community maintenance, I think we need to at least setup a place for discussion, like gitter or slack.
After that I will keep on an eye on how the community maintenance approach goes. Then I think I would like to focus on less development and maintenance but more testing, publishing and versioning, as I don't think I will be as active as past.
Hope this would work for everyone. And I am glad there are people want to help.
Cheers!

I opened a call for participation issue and closes this one.

I opened a call for participation issue and closes this one.

Pretty late here-- where is this call for participation?


maybe(Bool) support

Thanks for the great library! I'm working on an editor to author documents compliant with IEEE 1685-2014 (IPXACT). This means I have to work with an existing schema. This schema contains conditional Boolean elements, e.g. an element named "volatile". The value of this element is either undefined, true or false. The undefined value can be interpreted as false only if the volatile elements in all child elements are undefined as well. Long story short. There is an actual use case for conditional Boolean fields.
Are you planning to support this in the future? What would be a good workaround right now?
I tried using an Enum, rendered it as radio (so far so good) and tried to use a Transformer to convert betweeen Str and Bool. However I could not get the Transformer to work - I suspect it might only work with 'Textbox'?
Please advise.
Thanks, Bernd

I just made a commit on master branch adding transformers to all components.
In your case something like this should work:
var MyModel = t.struct({
  mybool: t.maybe(t.Bool)
});

var options = {
  fields: {
    mybool: {
      factory: t.form.Select, // render as a select since null is a valid value
      options: [
        {value: '0', text: 'No'},
        {value: '1', text: 'Yes'}
      ],
      transformer: {
        format: function (value) {
          return value === false ? '0' : value === true ? '1' : null;
        },
        parse: function (value) {
          return value === '0' ? false : value === '1' ? true : null;
        }
      }
    }
  }
};

var App = React.createClass({

  save: function () {
    var value = this.refs.form.getValue();
    if (value) {
      console.log(value);
    }
  },

  render: function() {
    return (
      <div>
        <Form ref="form"
          type={MyModel}
          options={options}
        />
        <button className="btn btn-primary" onClick={this.save}>Save</button>
      </div>
    );
  }

});

Let me know if it's ok

Thanks for the quick response. I switched to version 0.4.8 and tried it out. Works well!
Thanks, Bernd

Great, thanks for the feedback
Giulio


fix: update S3 uri regex for AWS sessions

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[ ] I have read the CONTRIBUTING doc
[ ] I used the commit message format described in CONTRIBUTING
[ ] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Functional changes are on https://github.com/amazon-braket/amazon-braket-sdk-python/pull/860/files#diff-79a00bf9d7a1839ba578a239aab1091ab7e4bcf16a2d022aeadd24b5378beee2R690. Linters started complaining and reformatted the rest.


New feature or package google translate package possible?

Is it possible to make package for atom for translation like this

Something like this:
url = "https://translate.google.com/?en=en#en/ru/#{cased}"
        # Shell.openExternal url
      xmlHttp = new XMLHttpRequest()
      xmlHttp.open( "GET", url, false )
      xmlHttp.onreadystatechange = ->
          if this.readyState == 4
              parser = new DOMParser()
              doc = parser.parseFromString(xmlHttp.responseText, "text/html")
              resultbox = doc.getElementById("result_box")
              alert(resultbox.innerHTML)
      xmlHttp.send( null )
      console.log(xmlHttp.responseText)

We're trying to control the amount of Issues that we have to triage and track. For general questions, the Atom message board is where you'll probably be able to find answers faster.


DB changes by /docker-entrypoint-initdb.d/*.sh not saved

Hi there,
when launching your image postgres:10-alpine with a script in /docker-entrypoint-initdb.d/*.sh, that seems to be applied. It looks like this:
psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "$POSTGRES_DB" <<-EOSQL
    CREATE USER micm;
    CREATE DATABASE micm;
    GRANT ALL PRIVILEGES ON DATABASE micm TO micm;
EOSQL

zcat "/docker-entrypoint-initdb.d/cmdb.dump.gz" | psql -v -U "${POSTGRES_USER}" micm

Logging in to that PostgreSQL image shows that the user and database named micm exists, but is empty:
$ docker-enter cmdb
/ # psql -U postgres micm
psql (10.5)
Type "help" for help.

micm=# \l
                                 List of databases
   Name    |  Owner   | Encoding |  Collate   |   Ctype    |   Access privileges
-----------+----------+----------+------------+------------+-----------------------
 micm      | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres         +
           |          |          |            |            | postgres=CTc/postgres+
           |          |          |            |            | micm=CTc/postgres
 postgres  | postgres | UTF8     | en_US.utf8 | en_US.utf8 |
 template0 | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres          +
           |          |          |            |            | postgres=CTc/postgres
 template1 | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres          +
           |          |          |            |            | postgres=CTc/postgres
(4 rows)

micm=# \dt
Did not find any relations.
micm=# \q
/ #

When I apply that very same dump manually once more, the DB is filled:
/ # zcat /docker-entrypoint-initdb.d/cmdb.dump.gz | psql -U postgres micm
SET
SET
SET
...
/ # echo $?
0
/ # psql -U postgres micm
psql (10.5)
Type "help" for help.

micm=# \dt
                              List of relations
 Schema |                       Name                       | Type  |  Owner
--------+--------------------------------------------------+-------+----------
 public | datacenter                                       | table | micm_adm
 public | device                                           | table | micm_adm
...

Am I missing something here or is this a bug?

PS: Somehow, creating the database like CREATE DATABASE micm WITH OWNER micm; and applying the dump as this user works.

Using the environment variables would also handle user creation and database owner
$ docker run --rm -dit -e POSTGRES_USER=micm --name postgres postgres:10-alpine
$ docker exec -it postgres sh
/ # psql -U micm
psql (10.5)
Type "help" for help.

micm=# \l
                             List of databases
   Name    | Owner | Encoding |  Collate   |   Ctype    | Access privileges
-----------+-------+----------+------------+------------+-------------------
 micm      | micm  | UTF8     | en_US.utf8 | en_US.utf8 |
 postgres  | micm  | UTF8     | en_US.utf8 | en_US.utf8 |
 template0 | micm  | UTF8     | en_US.utf8 | en_US.utf8 | =c/micm          +
           |       |          |            |            | micm=CTc/micm
 template1 | micm  | UTF8     | en_US.utf8 | en_US.utf8 | =c/micm          +
           |       |          |            |            | micm=CTc/micm
(4 rows)

Closing since the issue is resolved


SQL Syntax error on Web platform

Describe the bug
I get SQL syntax error on web platform with my create database schema. On Android it works.
error messsage: "Execute: ExecuteSQL: ExecuteSQL: Execute: near "DROP ": syntax error"
When I remove all DROPS then the error mesages says near "CREATE": syntax error"
Here a sample of my SQL command:
DROP TABLE IF EXISTS [SystemFlag]; CREATE TABLE IF NOT EXISTS [SystemFlag] (          [Key] NVARCHAR(50) UNIQUE NOT NULL PRIMARY KEY,          [Value] NVARCHAR(255) NULL          );
To Reproduce
Expected behavior
Screenshots
Desktop (please complete the following information):

OS: Windows 10
Browser chrome

@hschindler
try
DROP TABLE IF EXISTS SystemFlag;
CREATE TABLE IF NOT EXISTS SystemFlag]( Key NVARCHAR(50) UNIQUE NOT NULL PRIMARY KEY, Value NVARCHAR(255) NULL );

@hschindler
i mean
CREATE TABLE IF NOT EXISTS SystemFlag ( Key NVARCHAR(50) UNIQUE NOT NULL PRIMARY KEY, Value NVARCHAR(255) NULL );

I found a missing semicolon in my original 'create schema' that I didn't notice on Friday. It now works.
So sorry for wasting time.


Please invite me to the community

Name
hi-tech-AI
Additional Context
Hello, I hope everything is doing well.
I'm a python developer and I'd like to join this organization.
My GitHub username is hi-tech-AI.
Please invite me to your organization.
Thank you so much.

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is a remarkable open-source solution tailored for serverless platforms, aimed at empowering creators to craft their infrastructure solutions. 💻 We're thrilled to welcome you into our vibrant community! ✨ We eagerly anticipate your valuable contributions! 🤓 Don't forget to explore our community on Github and connect with us on LinkedIn 💜 Feel free to spread the word about our community to like-minded individuals interested in development, DevOps, technology, and collaborative contributions. 👉💜👈


Problem with new HW acceleration and stream buffering

If we want to make our new native HW acceleration the new default, we will have a problem with streaming. The problem is this: Currently, we rely on the MSS buffer to get stable playback in streaming scenarios. The MSS buffer works by buffering our output samples. With the old HW acceleration (passthrough to system decoder), the output are compressed samples in system memory, so that works reasonably well (besides some general bugs in MSS buffering). But with the new HW acceleration, we output decoded frames in GPU memory. Using a buffer on that will quickly blow up GPU memory usage.
If we want to make our approach work with streaming as well, we'd have to provide our own internal buffering implementation.
One approach how this could be done: Instead of reading packets on demand, we could have an async read-ahead packet reader. It would read packets and fill stream buffers until a certain time limit or binary size limit is exceeded. Instead of having streams pull packets on demand, they have to wait until packets are made available.

I wonder if we could get the OS to do the buffering for us, by loading ahead in the stream.

I wonder if we could get the OS to do the buffering for us, by loading ahead in the stream.

The problem is that FFmpeg does all the stream creation and handling. And none of the buffering options seem to do any effect. There is no general read-ahead mechanism in FFmpeg.

The problem is that FFmpeg does all the stream creation and handling. And none of the buffering options seem to do any effect. There is no general read-ahead mechanism in FFmpeg.

This sounds like a consumer-producer problem.
Take a look at this, looks promising...
https://github.com/cameron314/concurrentqueue

This sounds like a consumer-producer problem.
Take a look at this, looks promising...
https://github.com/cameron314/concurrentqueue

That one could be helpful indeed

That one could be helpful indeed

Unfortunately I won't have much time to look into this in the following weeks...
In the mean time we could do a work around and force system codes when we create a stream source from URL.

Unfortunately I won't have much time to look into this in the following weeks...
In the mean time we could do a work around and force system codes when we create a stream source from URL.

Same for me. I will be very busy the next 5-6 weeks. Been building a house since summer 2020, and it's almost finished now! ^^

Same for me. I will be very busy the next 5-6 weeks. Been building a house since summer 2020, and it's almost finished now! ^^

Sounds cool ^^. Congratulations!

Sounds cool ^^. Congratulations!

Thank you. Really looking forward to moving in, maybe in March!! :D But first we need to do the painting and floors ourselves, that will keep us busy for the next weeks...

Thank you. Really looking forward to moving in, maybe in March!! :D But first we need to do the painting and floors ourselves, that will keep us busy for the next weeks...

Solved by using new stream buffer approach #270


Demo?

Can you give me a working live demo?
Just wanna see it in action xD

Hello jdc20181,
Thanks for contacting us.
Yes, a live working demo can be seen on the Fluid Player website: https://www.fluidplayer.com/
You can also download the project and open the /examples folder.
Kind Regards,
Marin Yotovski

Thanks!


Build error: Received '\x00__vite-browser-external?commonjs-proxy'

Describe the bug
I am seeing a build error when working on a project of Inertia + Svelte using Vite. The code works fine in development mode with HMR, but shows this error when doing a production build.
2022-06-03T07:28:49.338Z vite:vite-plugin-svelte error trying to resolve __vite-browser-external from __vite-browser-external?commonjs-proxy via package.json svelte field  TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received '\x00__vite-browser-external?commonjs-proxy'
    at new NodeError (node:internal/errors:372:5)
    at createRequire (node:internal/modules/cjs/loader:1220:13)
    at resolveViaPackageJsonSvelte ($DIR/vite-plugin-svelte-bug/node_modules/@sveltejs/vite-plugin-svelte/dist/index.cjs:1476:59)
    at Object.resolveId ($DIR/vite-plugin-svelte-bug/node_modules/@sveltejs/vite-plugin-svelte/dist/index.cjs:1728:28)
    at $DIR/vite-plugin-svelte-bug/node_modules/rollup/dist/shared/rollup.js:22974:37 {
  code: 'ERR_INVALID_ARG_VALUE'
}

Assets are produced in the dist dir, but the build is broken.  The run-time error is actually in the object-inspect package.
The run-time error may simply be a consequence of the build error (I don't know), but in case it's relevant, the run-time error is:
Cannot read properties of undefined (reading 'custom')

and points to the line https://github.com/inspect-js/object-inspect/blob/2cba8e119af13ff9648d5160871c3da22948ca8a/index.js#L69 where require('./util.inspect') is resulting in undefined.
This run-time error is pretty much identical to #2598 but that was closed as resolved a year ago and I'm using all-up-to-date packages.
For the build error, I have tried substituting redaxios in place of axios, but the error message remained the same.
The repo has a strange name because I originally reported this under https://github.com/sveltejs/vite-plugin-svelte/issues/362 but it looks like this is not a svelte problem but perhaps how vite handles cjs.
Reproduction
For the build error I have a minimal repro repo at https://github.com/niczero/vite-plugin-svelte-bug
System Info
System:
    OS: Linux 5.13 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
    Memory: 25.71 GB / 30.96 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.3.0 - /usr/bin/node
    npm: 8.11.0 - /usr/bin/npm
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 100.0.2
  npmPackages:
    vite: ^2.9.9 => 2.9.9

Used Package Manager
pnpm
Logs
[$DIR is just where I have redacted the path prefix]

> vite-build-bug@ build $DIR/vite-plugin-svelte-bug
> vite build --debug

2022-06-04T19:58:00.383Z vite:config bundled config file loaded in 57.23ms
2022-06-04T19:58:00.384Z vite:vite-plugin-svelte svelte inspector path: $DIR/vite-plugin-svelte-bug/node_modules/.pnpm/@sveltejs+vite-plugin-svelte@1.0.0-next.47_svelte@3.48.0+vite@2.9.9/node_modules/@sveltejs/vite-plugin-svelte/src/ui/inspector/
2022-06-04T19:58:00.385Z vite:vite-plugin-svelte no svelte config found at $DIR/vite-plugin-svelte-bug
2022-06-04T19:58:00.385Z vite:vite-plugin-svelte findSvelteDependencies: searching svelte dependencies in $DIR/vite-plugin-svelte-bug
2022-06-04T19:58:00.386Z vite:vite-plugin-svelte additional vite config {
  resolve: {
    mainFields: [ 'svelte', 'module', 'jsnext:main', 'jsnext' ],
    dedupe: [
      'svelte/animate',
      'svelte/easing',
      'svelte/internal',
      'svelte/motion',
      'svelte/ssr',
      'svelte/store',
      'svelte/transition',
      'svelte',
      'svelte-hmr/runtime/hot-api-esm.js',
      'svelte-hmr/runtime/proxy-adapter-dom.js',
      'svelte-hmr'
    ]
  },
  optimizeDeps: { extensions: [ '.svelte' ], esbuildOptions: { plugins: [Array] } },
  ssr: { noExternal: [] }
}
2022-06-04T19:58:00.394Z vite:vite-plugin-svelte resolved options {
  hot: false,
  compilerOptions: { css: false, dev: false },
  extensions: [ '.svelte' ],
  emitCss: true,
  experimental: { prebundleSvelteLibraries: true },
  root: '$DIR/vite-plugin-svelte-bug',
  isBuild: true,
  isServe: false,
  isDebug: true,
  isProduction: true
}
2022-06-04T19:58:00.396Z vite:config using resolved config: {
  build: {
    target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
    polyfillModulePreload: true,
    outDir: 'dist',
    assetsDir: 'assets',
    assetsInlineLimit: 4096,
    cssCodeSplit: true,
    cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
    sourcemap: false,
    rollupOptions: { input: [Array] },
    minify: 'esbuild',
    terserOptions: {},
    write: true,
    emptyOutDir: null,
    manifest: false,
    lib: false,
    ssr: false,
    ssrManifest: false,
    reportCompressedSize: true,
    chunkSizeWarningLimit: 500,
    watch: null,
    commonjsOptions: { include: [Array], extensions: [Array] },
    dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  },
  plugins: [
    'vite:build-metadata',
    'alias',
    'vite-plugin-svelte',
    'vite:modulepreload-polyfill',
    'vite:resolve',
    'vite:html-inline-proxy',
    'vite:css',
    'vite:esbuild',
    'vite:json',
    'vite:wasm',
    'vite:worker',
    'vite:asset',
    'vite:define',
    'vite:css-post',
    'vite:build-html',
    'vite:worker-import-meta-url',
    'vite:watch-package-data',
    'commonjs',
    'vite:data-uri',
    'rollup-plugin-dynamic-import-variables',
    'vite:asset-import-meta-url',
    'vite:build-import-analysis',
    'vite:esbuild-transpile',
    'vite:terser',
    'vite:reporter',
    'vite:load-fallback'
  ],
  resolve: {
    dedupe: [
      'svelte/animate',
      'svelte/easing',
      'svelte/internal',
      'svelte/motion',
      'svelte/ssr',
      'svelte/store',
      'svelte/transition',
      'svelte',
      'svelte-hmr/runtime/hot-api-esm.js',
      'svelte-hmr/runtime/proxy-adapter-dom.js',
      'svelte-hmr'
    ],
    mainFields: [ 'svelte', 'module', 'jsnext:main', 'jsnext' ],
    alias: [ [Object], [Object] ]
  },
  optimizeDeps: {
    extensions: [ '.svelte' ],
    esbuildOptions: {
      keepNames: undefined,
      preserveSymlinks: undefined,
      plugins: [Array]
    }
  },
  ssr: { noExternal: [] },
  configFile: '$DIR/vite-plugin-svelte-bug/vite.config.js',
  configFileDependencies: [
    '$DIR/vite-plugin-svelte-bug/vite.config.js'
  ],
  inlineConfig: {
    root: undefined,
    base: undefined,
    mode: undefined,
    configFile: undefined,
    logLevel: undefined,
    clearScreen: undefined,
    build: {}
  },
  root: '$DIR/vite-plugin-svelte-bug',
  base: '/',
  publicDir: '$DIR/vite-plugin-svelte-bug/public',
  cacheDir: '$DIR/vite-plugin-svelte-bug/node_modules/.vite',
  command: 'build',
  mode: 'production',
  isWorker: false,
  isProduction: true,
  server: {
    preTransformRequests: true,
    fs: { strict: true, allow: [Array], deny: [Array] }
  },
  preview: {
    port: undefined,
    strictPort: undefined,
    host: undefined,
    https: undefined,
    open: undefined,
    proxy: undefined,
    cors: undefined,
    headers: undefined
  },
  env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  assetsInclude: [Function: assetsInclude],
  logger: {
    hasWarned: false,
    info: [Function: info],
    warn: [Function: warn],
    warnOnce: [Function: warnOnce],
    error: [Function: error],
    clearScreen: [Function: clearScreen],
    hasErrorLogged: [Function: hasErrorLogged]
  },
  packageCache: Map(0) { set: [Function (anonymous)] },
  createResolver: [Function: createResolver],
  worker: {
    format: 'iife',
    plugins: [
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object], [Object], [Object],
      [Object]
    ],
    rollupOptions: {}
  }
}
vite v2.9.9 building for production...
transforming...
2022-06-04T19:58:00.524Z vite:vite-plugin-svelte transform returns compiled js for $DIR/vite-plugin-svelte-bug/node_modules/.pnpm/@inertiajs+inertia-svelte<EMAIL_ADDRESS>2022-06-04T19:58:00.557Z vite:vite-plugin-svelte transform returns compiled js for $DIR/js/vite-plugin-svelte-bug/node_modules/.pnpm/@inertiajs+inertia-svelte<EMAIL_ADDRESS>2022-06-04T19:58:00.683Z vite:vite-plugin-svelte transform returns compiled js for $DIR/vite-plugin-svelte-bug/node_modules/.pnpm/@inertiajs+inertia-svelte<EMAIL_ADDRESS>2022-06-04T19:58:00.894Z vite:vite-plugin-svelte error trying to resolve __vite-browser-external from �__vite-browser-external?commonjs-proxy via package.json svelte field  TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received '\x00__vite-browser-external?commonjs-proxy'
    at new NodeError (node:internal/errors:377:5)
    at createRequire (node:internal/modules/cjs/loader:1220:13)
    at resolveViaPackageJsonSvelte ($DIR/vite-plugin-svelte-bug/node_modules/.pnpm/@sveltejs+vite-plugin-svelte@1.0.0-next.47_svelte@3.48.0+vite@2.9.9/node_modules/@sveltejs/vite-plugin-svelte/dist/index.cjs:1476:59)
    at Object.resolveId ($DIR/vite-plugin-svelte-bug/node_modules/.pnpm/@sveltejs+vite-plugin-svelte@1.0.0-next.47_svelte@3.48.0+vite@2.9.9/node_modules/@sveltejs/vite-plugin-svelte/dist/index.cjs:1728:28)
    at $DIR/vite-plugin-svelte-bug/node_modules/.pnpm/rollup@2.75.5/node_modules/rollup/dist/shared/rollup.js:22974:37 {
  code: 'ERR_INVALID_ARG_VALUE'
}
‚úì 56 modules transformed.
rendering chunks...
dist/assets/main.02a1e324.js   69.45 KiB / gzip: 23.97 KiB

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I got a different error for both dev and build.
X [ERROR] [plugin vite:dep-pre-bundle] Failed to resolve entry for package "object-inspect". The package may have incorrect main/module/exports specified in its package.json: Failed to resolve entry for package "object-inspect". The package may have incorrect main/module/exports specified in its package.json.

[commonjs] Failed to resolve entry for package "object-inspect". The package may have incorrect main/module/exports specified in its package.json: Failed to resolve entry for package "object-inspect". The package may have incorrect main/module/exports specified in its package.json.

And this error is true because util_inspect.js does not exist.
https://github.com/niczero/object-inspect/blob/e0bb215b068952a8276fc068f97fa435d1ba57ca/package.json#L75

The branches had got mixed up -- I've fixed the main branch on the repro repo so it does not contain the experiment with object-inspect.
Please try again.

It seems these issues are related.
https://github.com/inspect-js/object-inspect/issues/38
https://github.com/inertiajs/inertia/issues/447

@niczero Would you provide a reproduction for the runtime error? I was not able to reproduce it.

Not really practical -- an inertia app requires a backend as well as a frontend -- so best to ignore the runtime error and treat it as a side memo on the build error.

@dominikg @bluwy May I ask you some questions about this issue? (https://github.com/sveltejs/vite-plugin-svelte/issues/362, https://github.com/sveltejs/vite-plugin-svelte/pull/363)

Speaking of the error during build

vite-plugin-svelte is enforce: 'pre' so it runs before Vite's internal resolver plugin.
https://github.com/sveltejs/vite-plugin-svelte/blob/b714afd98b777f79f809b4ef3580c4cf339cbed5/packages/vite-plugin-svelte/src/index.ts#L59, https://github.com/vitejs/vite/blob/fba82d0ff66d2a13393b052dd95df9e180db663c/packages/vite/src/node/plugins/index.ts#L46-L57
So this error is something vite-plugin-svelte needs to handle.
Or are you suggesting things like __vite-browser-external should be handled before enforce: 'pre' plugins?

Speaking of the runtime error, it is hard to find the reason from the build error.

Am I right about these?

No, vite-plugin-svelte logged an error, but didn't actually resolve __vite-browser-external. We have since released a new version that does not log this error anymore. The behavior described by this report has not been caused/altered by that log statement.
As mentioned in https://github.com/sveltejs/vite-plugin-svelte/issues/362#issuecomment-1145800239 i suspect a combination of commonjs and browser field as a cause for this, but am not sure.
A clean reproduction with vite's vanilla template would be great. npm init vite -- --template vanilla

Status update:

You're right, the runtime error appears to be independent from the build error.  I have avoided the build error (detail below) but with no build error I still get the runtime error, so I need to find a reproduction of the runtime error so we can get to the bottom of that.

I made a local hacked version of @inertiajs/inertia to produce an ESM build of that, using the patch attached here:
inertia_package.json.txt
When I swap from the official Inertia to the ESM Inertia, my repo has no build error.  I think that shows the build error is not caused by vite-plugin-svelte and not caused by Axios.  I am happy to use a hacked Inertia until the team there are able to resolve https://github.com/inertiajs/inertia/issues/447
So the runtime error remains and I will try to build a mini reproduction.


TOMEE-2699-Translate to portugue the Example.

Link to Jira : https://issues.apache.org/jira/browse/TOMEE-2699

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

done, thanks .


gradle 3.5.3

Good day guys , I updated my flutter environment to 1.12
I have the following configuration on gradle
ext.kotlin_version = '1.3.41'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.3'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }

. but I tried the command flutter run --verbose I get this error

[+619883 ms] AAPT2 aapt2-3.5.3-5435860-windows Daemon #0 Failed to shutdown within timeout
[+3788 ms] java.util.concurrent.TimeoutException: AAPT2 aapt2-3.5.3-5435860-windows Daemon #0: Failed to shut down within 30 seconds. Forcing shutdown
[  +66 ms]      at com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopProcess(Aapt2DaemonImpl.kt:224)
[        ]      at com.android.builder.internal.aapt.v2.Aapt2Daemon.shutDown(Aapt2Daemon.kt:140)
[   +1 ms]      at com.android.builder.internal.aapt.v2.Aapt2Daemon.handleError(Aapt2Daemon.kt:175)
[   +1 ms]      at com.android.builder.internal.aapt.v2.Aapt2Daemon.handleError$default(Aapt2Daemon.kt:160)
[   +1 ms]      at com.android.builder.internal.aapt.v2.Aapt2Daemon.link(Aapt2Daemon.kt:120)
[  +39 ms]      at com.android.builder.internal.aapt.v2.Aapt2DaemonManager$LeasedAaptDaemon.link(Aapt2DaemonManager.kt:175)
[ +165 ms]      at com.android.build.gradle.internal.res.Aapt2ProcessResourcesRunnableKt.processResources(Aapt2ProcessResourcesRunnable.kt:80)
[  +35 ms]      at
com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$AaptSplitInvoker.invokeAaptForSplit(LinkApplicationAndroidResourcesTask.kt:840)
[ +155 ms]      at com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$AaptSplitInvoker.run(LinkApplicationAndroidResourcesTask.kt:722)
[   +3 ms]      at com.android.build.gradle.internal.tasks.Workers$ActionFacade.run(Workers.kt:335)
[  +66 ms]      at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:39)
[   +1 ms]      at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.execute(NoIsolationWorkerFactory.java:61)
[  +31 ms]      at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)
[  +30 ms]      at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
[  +61 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
[   +3 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
[  +89 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
[  +58 ms]      at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
[   +1 ms]      at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)
[   +1 ms]      at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:55)
[   +2 ms]      at org.gradle.workers.internal.DefaultWorkerExecutor$1.call(DefaultWorkerExecutor.java:105)
[  +61 ms]      at org.gradle.workers.internal.DefaultWorkerExecutor$1.call(DefaultWorkerExecutor.java:99)
[   +1 ms]      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[        ]      at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:215)
[   +1 ms]      at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:164)
[  +28 ms]      at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:131)
[   +2 ms]      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[   +1 ms]      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[  +45 ms]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
[  +16 ms]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
[   +3 ms]      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[ +167 ms]      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[   +2 ms]      at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
[  +31 ms]      at java.lang.Thread.run(Thread.java:748)
[   +1 ms] FAILURE: Build failed with an exception.
[  +50 ms] * What went wrong:
[   +9 ms] Execution failed for task ':app:processDebugResources'.
[   +1 ms] > A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
[   +1 ms]    > AAPT2 aapt2-3.5.3-5435860-windows Daemon #0: Link timed out, attempting to stop daemon.
[   +1 ms] > Task :app:processDebugResources FAILED
[        ] 78 actionable tasks: 6 executed, 72 up-to-date
[   +1 ms]      This should not happen under normal circumstances, please file an issue if it does.
[   +1 ms] * Try:
[   +8 ms] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

what could it be?
thank you!
cheers.

I included in gradle file this
android.enableR8=true
and now the console shows:
Unsuported Android Plugin version: 3.5.3.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      getGradleVersionFor (package:flutter_tools/src/android/gradle_utils.dart:203:3)
#2      getGradleVersionForAndroidPlugin (package:flutter_tools/src/android/gradle_utils.dart:150:10)
#3      _exitWithExpectedFileNotFound (package:flutter_tools/src/android/gradle.dart:821:7)
#4      findApkFiles (package:flutter_tools/src/android/gradle.dart:765:5)
#5      buildGradleApp (package:flutter_tools/src/android/gradle.dart:451:35)
#6      _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#7      _rootRunUnary (dart:async/zone.dart:1134:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#12     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#13     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#14     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#15     _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart)
#16     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#17     _rootRunUnary (dart:async/zone.dart:1134:38)
#18     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#19     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#20     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#21     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#22     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#23     Future._asyncComplete. (dart:async/future_impl.dart:554:7)
#24     _rootRun (dart:async/zone.dart:1126:13)
#25     _CustomZone.run (dart:async/zone.dart:1023:19)
#26     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#27     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:965:23)
#28     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#29     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#30     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#31     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

Hi @darasat
could you please try running
flutter clean
flutter pub cache repair
let me know if it fixes the issue
thank you

I am thinking that it´s a flutter framework problem
I tried to:

Repair pub cache
Migrate to android x with visual studio
Upgrade - Downgrade flutter framework
Change gradle config (3.5.3 to 3.5.2 and 3.5.0)
Flutter clean
Make another project and see what happens (with this project without plugins the framework runs, but with some third party the framework crashes)

Gradle build failed to produce an .apk file. It's likely that this file was generated under "PATH"\build, but the tool couldn'tfind it.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      _exitWithExpectedFileNotFound (package:flutter_tools/src/android/gradle.dart:827:3)
#2      findApkFiles (package:flutter_tools/src/android/gradle.dart:765:5)
#3      buildGradleApp (package:flutter_tools/src/android/gradle.dart:451:35)
#4      _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#5      _rootRunUnary (dart:async/zone.dart:1134:38)
#6      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#7      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#8      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#9      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#10     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#11     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#12     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#13     _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart)
#14     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#15     _rootRunUnary (dart:async/zone.dart:1134:38)
#16     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#17     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#18     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#19     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#20     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#21     Future._asyncComplete. (dart:async/future_impl.dart:554:7)
#22     _rootRun (dart:async/zone.dart:1126:13)
#23     _CustomZone.run (dart:async/zone.dart:1023:19)
#25     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:965:23)
#26     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#27     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#28     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#29     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)
When google will to review this? it's supossed to be the version 1.12 will be stable..
thanks for your help.

I fix it creating a new project and checking plugin by plugin.

Why was this closed? I'm not sure I understand what you meant by "checking plugin by plugin". Did you just avoid using the plugins causing your errors?
I'm having this exact issue at the moment. Builds fine with gradle, but fails when using the flutter tools.

Hi @arnemolland
I believe the author of the issue
is entitled to close it anytime.
Please note that some plugins, in particular 3rd party plugins, aren't "1.12 ready"
in that case the possible solutions are:

waiting for the plugin to be update;
avoid using the plugin;
downgrade Flutter.

Did you try the proposed solution?
If the issue persist please provide your updated
flutter doctor -v and flutter run --verbose
together with a a minimal code sample to reproduce the problem
thank you

Fixed by downgrading to plugin version 3.5.0 — maybe the error message should describe that the error is with the Flutter build tools, along with the latest supported Gradle + Android plugin version? At the moment it’s unclear where the error is coming from.
Found the fix by browsing the Flutter build tools source.

@arnemolland getting the same issue and been looking for solution for couple of days know. thank you for finding the problem

I suspect it’s more work than just bumping the version, and Gradle just had a major release (6.0) that might be a little more comprehensive to support. I might be completely wrong though, as I’m not familiar with the toolchain.

the plugin version 3.5.3 also supports '5.6.2' so don't think if its going to cause any damage

There's a PR open here. Tested locally by bumping max version to 3.5.3 (and Gradle to 6.0), works perfectly fine. You can do so yourself on a fork if you need it before the PR lands.

when i meet this, and i create a new project that meet the same problem, now i don't know how to fix it when has passed one week,(i am in china maybe firewall influnce network runs)

if app/build.gradle code
  splits {
        abi {
            enable true
            reset()
            include "x86","x86_64", "armeabi-v7a","armeabi-v8a"
            universalApk true
        }
    }

delete it

Weirdly @kouxinhong 's comment worked in my case.
But that's probably shouldn't be the case.
And also flutter build apk --split-per-abi does not generate apks with version number defined in android/app/build.gradle

I'm not really sure what issue this bug is tracking. The original filled issue is an internal Gradle failure so I'm closing it.

I got this solution from here I hope someone will get help.


Not working with iQR and SQRC

Hi,
thankyou for the wonderful plugin, ive noticed the library isnt compatible with certain qr-codes.
the plugin is not working with iQR code.
Please find attached images.

Best Regards
Daryl

Hi,
It works for me if resolution is good for decoding.
Tested Win10, Chrome latest.

Regards


Dev Restructure Proposal

- Summary
Develop using example/site/admin structure in development.
- Test plan
Run through all development tests with a new clone.
Run yarn , yarn start to make sure all is compiling well.
Run local server tests.
- Description for the changelog
First step in creating a cohesive solution for running a cli and development.
Cleans up the development builds and loaders to stop asset errors.

@erquhart mentioned a root deploy. This should be simple with a deploy of the /example/site/admin path after the copy.

The branch config.yml in #554 is setup to point to a different branch for backend. This is due to keeping clutter from the PR branch. For consistency, backend branches created for the sole purpose of testing should be created as a branch of the PR submitted for merge.
I feel we should consider this in this Dev Restructure proposal.
I fixed all the asset path errors with this PR, It should have a check for NODE_ENV=development to change asset paths to a deploy preview site path for testing *WHEN there is a deploy-site-path in the config.yml or maybe in process.env.TESTING_SITE
I will test the configuration and see how easy it would be.
Thoughts?

@talves good thoughts here. Cleaning up errors is awesome, thank you for that! I also totally agree on using a branch off of the PR branch for testing backends, that's a much better approach.

@talves I like this restructure, and I think your idea about PR backend branches is a good one.

@Benaiah and @erquhart I am glad you guys agree on the PR backend branches.
Question; Can we test a backend branch with a folder path in the CMS?
In example test/fix-pr-000
I also feel we need to folder path test branches, so we can easily identify and clean them out of the repository and they do not clutter. Just a thought.

@talves is this still relevant in light of your more recent work on the file system backend?

Yeah, I will close this now. A restructure of dev is not as imperative with the file system backend as an option.


iOS8, Safari when using Regex pattern is forcing caps lock

I am using version 3.2.0 and I have the following regex pattern for an input field
"^[a-zA-Z '\\\\-]*$"

This being added via the 'Regex' property to a text field.  It seems on the iPhone that this is forcing the field to always being capitalized.  You can lowercase it manually, however it is ignoring the "autocapitalize" attribute and by default every character entered is capitalized. Has anyone else run into this problem?

@SomethingSexy ,
Can you create a jsfiddle with the exact mask used to make it more clear.

https://jsfiddle.net/g85gtfLx/6/


Riemann integration

Send a Riemann event

per refresh
per creation
per modifcation
per destruction
per node refresh, with details about the list

Config will look like
{:riemann {:protocol :tcp
                  :host "<IP_ADDRESS>"
                  :port 5555
                  :tls? true
                  :key "...PKCS8 key..."
                  :cert "..PEM cert..."
                  :ca-cert "...signing CA cert..."
                  :cache-dns? false}}

Details we want to easily extract:

what does the current session pool look like?
** size?
** reserved %?
** browser distribution?
error rate
some idea of session contention
the last time we heard from shale

@chris-martin anything to add here?

Maybe an alert if a session has stayed reserved for too long (like >20 minutes) because something has probably failed to unreserve it?

Session reservation length would be handy as well - average and per session.