text:
Expose PreRelease label in PSModuleInfo formatter

PR Summary
Add PreRelease script property to PSModuleInfo table and list formatters to easily get PreRelease info.  Also update ModuleInfoGrouping formatter so -ListAvailable also shows it.
PS> gmo psreadline

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     2.0.0      beta4      PSReadLine                          {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PSReadLineKeyHandler, Set-PSReadLineKeyHandler…}

[67.67ms] /Users/steve/repos/PowerShell [origin/module-info-psdata]
PS> gmo psreadline | fl

Name              : PSReadLine
Path              : /Users/steve/.local/share/powershell/Modules/PSReadLine/2.0.0/PSReadLine.psm1
Description       : Great command line editing in the PowerShell console host
ModuleType        : Script
Version           : 2.0.0
PreRelease        : beta4
NestedModules     : {Microsoft.PowerShell.PSReadLine2}
ExportedFunctions : PSConsoleHostReadLine
ExportedCmdlets   : {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PSReadLineKeyHandler, Set-PSReadLineKeyHandler…}
ExportedVariables :
ExportedAliases   :

PR Context
Got tired of asking people to run (gmo psreadline).privatedata.psdata to find out which version of 2.0.0 they have, so exposing this as part of formatting in PSModuleInfo.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@iSazonov there's lots more work needed to properly support SemVer.  Current thinking is to wait for .NET Core to close on their SemVer type.


text:
Run dotnet-format

PR Summary
Reformat code according to EditorConfig rules.
The following rules were temporarily disabled as they resulted in a high number of changes:
dotnet_sort_system_directives_first = true
csharp_preserve_single_line_statements = false
csharp_new_line_before_open_brace = all

PR Context
Follow-up: #11681
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[NA] Experimental feature(s) needed

[NA] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[NA] Documentation needed

[NA] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[NA] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@adityapatwardhan CodeFactor violations are fixed.

Build failures are due to PowerShell Gallery unavailability, see #13946.

source: gharchive/pull-request

repo: PowerShell/PowerShell

license: MIT

license_type: permissive

license_source: github-api


text:
Remove unnecessary using in singleshell folder

PR Summary
This PR removes unnecessary using statements in the singleshell folder.
PR Context
Code cleanup
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

xUnit tests fail after some restarts - @ThomasNieto please look the issue.

authors: ThomasNieto iSazonov


text:
Move bypass execution policy check after AppLocker Deny check

PR Summary
Move bypass execution policy check after AppLocker Deny check
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@PaulHigin can you refresh your review?

This seems like it would be a breaking change....

This seems like it would be a breaking change

It is a bug fix - no one can disable the lock set by a system administrator.

Does this being a bugfix effect whether it's a breaking change?
https://github.com/PowerShell/PowerShell/blob/master/docs/dev-process/breaking-change-contract.md

It doesn't matter if the existing behavior is "wrong", we still need to think through the implications. PowerShell has been in broad use for over 10 years so we be must be extremely sensitive to breaking existing users and scripts.

@strawgate Any bug fix could be considered as a breaking change :-)
This is a security related bug fix - such things are never discussed publicly.

@strawgate I've marked the issue a breaking change.  As @iSazonov has said, AppLocker is considered the security feature with the stronger promise here.  Execution policy was never intended as a bypass.
See our security policy:  https://github.com/PowerShell/PowerShell/security/policy

Security issues are treated very seriously and will, by default, takes precedence over other considerations including usability, performance, etc... Best effort will be used to mitigate side effects of a security change, but PowerShell must be secure by default.

authors: TravisEz13 iSazonov rjmholt strawgate


text:
Add New Commandlet Set and Get Windows EnvironmentVariable

PR Summary

The addition of a cmdlet that allows the user to retrieve, modify, and append process, user, and system environment variables in a Windows environment.
PR Context

To add Set-WinEnvironmentVariable and Get-WinEnvironmentVariable cmdlets that only work in a Windows environment and to be able to manipulate environment variables from the terminal.
The existing ones require the use of setx.exe, which is inconvenient and not very compatible with powershell.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Protip: If you write Fixes <Link to issue> you can link this PR to an issue (like the one you created earlier this week).
Anyway, like I said in that issue environment variable manipulation with .NET is broken so the documentation for these commands should probably mention that. Here's a link that describes the bad behavior: https://github.com/dotnet/runtime/issues/1442

Protip: If you write Fixes <Link to issue> you can link this PR to an issue (like the one you created earlier this week). Anyway, like I said in that issue environment variable manipulation with .NET is broken so the documentation for these commands should probably mention that. Here's a link that describes the bad behavior: dotnet/runtime#1442

@MartinGC94
Thank you for sharing with me.


text:
Jameswtruher/travisdaily2

continued attempts to reduce output size so we can get a daily build in travis-ci
this sets progress preference on the help and package management tests to SilentlyContinue to reduce output. This is done for all test execution, including dev and CI

Maybe progress should be opt-in instead of opt-out. In other words, disable globally, turn on in the progress tests.

I thought about disabling progress universally but thought it would be better for each test to control this behavior. My concern is reviewing/rewriting existing tests which may be relying on progress in ways that I don't know.

Which seems more likely?

Adding new progress tests?
Adding new functionality or tests that write progress?

With code coverage data, I feel comfortable that 1 won't be a big problem. Also, when progress doesn't work correctly, because it's UI, folks tend to notice and complain.
I think 2 will be less hassle in the long run.

oh, we know we'll be adding a number of progress tests - right now we are only doing the minimum amount of progress tests. As soon as we have better support on non-windows we'll be doing even more. I don't agree that #2 is less hassle

also, i don't know that this will even solve the problem with Travis-CI, but I have no other way to test it - i would much rather make targeted changes to determine if it will solve the daily build in Travis-CI issue than whole scale changing the way our tests work

Isn't this really just a bug in PowerShell?  Shouldn't we be detecting that we're not running interactively and not show progress?

That I don't know - I recall that we had difficulties with running (historical) tests because some host APIs would throw when in that mode. This code base is different, of course, but I still would rather avoid tracking down extraneous issues when all I'm trying to do is find the right incantation to get daily builds in Travis-CI to work.
The advice I've gotten so far from the Travis-CI folks is to redirect all output from build/test into a file and not emit it to stdout, but I'm reluctant to try that first, so I am attempting to reduce output in this way.

Current solution solved the Travis full log problem. It is very good!
As regards global disable progress bar. On the one hand testing should be performed with the default values as users get them. On the other hand any default parameter changes must not lead to the collapse of the tests, nor to the collapse of the real-world scripts.
Hm... If the progress bar would be turned off by default, then we wouldn't have caught a problem with "debris" and performance.

Please remove the formatting changes from the code changes, it unnecessarily makes it harder to see the logical code changes.
We have a different PR to remove trailing spaces, so we don't need to do that file by file.

authors: JamesWTruher iSazonov lzybkr


text:
Use correct win32 console mode w/ external commands

At startup, we need to save the current console mode before potentially
enabling VT100 support.
Then, when running an external command, we should use that initial
console mode instead of whatever mode we changed it to.
An application can't rely on the shell enabling VT100 because enabling
by default can cause problems for some applications, therefore
Windows applications must enable VT100 themselves.
Fixes #1177

Don't merge yet - this doesn't seem to fix all the issues.

This is good to merge now.


text:
Clean up workflow logic in the module loading component

PR Summary
Clean up workflow logic in the module loading component.
Workflow module is not supported in PSCore.
Currently, Import-Module throws a terminating error when seeing .xaml modules. After the change, Import-Module throws a non-terminating error when seeing .xaml modules.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[x] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

[x] Add [feature] if the change is significant or affects feature tests

@TravisEz13 Two Save-Help and Update-Help tests failed for the PackageManagement module. This is due to the timeout on the Microsoft download center. It's a known issue. /cc @adityapatwardhan
I restarted the CI run again. Hopefully, it will pass this time.


text:
BlobCacheSettings Issue when trying to declare same URL with different zone;

Details of the scenario you try and problem that is occurring:
Imagine the case where you have a DSC configuration that declares two different BlobCacheSettings, for the same Web Application, but for a different Zone. Trying to compile such a resource gives an error similar to the following:
Test-ConflictingResources : A conflict was detected between resources
'[SPBlobCacheSettings]5daeca26-879d-4f5b-be9f-7270aa6551d1 (C:\temp\SP-Farm.DSC.ps1::584::9::SPBlobCacheSettings)' and '[SPBlobCacheSettings]ef14ea31-4cd6-41ad-8920-f7fd9de1aee4 (C:\temp\SP-Farm.DSC.ps1::595::9::SPBlobCacheSettings)' in node 'MVA-APP'. Resources have identical key properties but there are differences in the following non-key properties:
'Zone'. Values 'Default' don't match values 'Intranet'. Please update these property values so that they are identical in both cases.
when looking at the *.schema.mof file, I off course see that while the Zone parameter is marked as required, that only the WebAppUrl parameter is identified as a Key. Can't we also make the Zone a Key parameter to solve this issue?
The DSC configuration that is using the resource:
[...]
SPBlobCacheSettings 5daeca26-879d-4f5b-be9f-7270aa6551d1
{
MaxSizeInGB = 10;
PsDscRunAsCredential = $Credssp_farm;
FileTypes = ".(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$";
EnableCache = $False;
Location = "C:\BlobCache\14";
MaxAgeInSeconds = 0;
Zone = "Default";
WebAppUrl = "http://mva-wfe/";
}
SPBlobCacheSettings ef14ea31-4cd6-41ad-8920-f7fd9de1aee4
{
MaxSizeInGB = 10;
PsDscRunAsCredential = $Credssp_farm;
FileTypes = ".(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$";
EnableCache = $False;
Location = "C:\BlobCache\14";
MaxAgeInSeconds = 0;
Zone = "Intranet";
WebAppUrl = "http://mva-wfe/";
}
[...]
Version of the Operating System and PowerShell the DSC Target Node is running:
Win Server 2016/WMF 5.1
Version of the DSC module you're using:
1.7.0.0

Agree that zone should be a key as well, adding to the backlog

Will be changed in my next Rollup PR

This has been rolled in to dev and will be included in our next release. Closing this issue.

source: gharchive/issue

authors: BrianFarnhill NikCharlebois ykuijs

repo: PowerShell/SharePointDsc


text:
SqlSetup: SQLSvcAccount failing on domain account

Are there any known issues around installing with a domain account? I did it this same exact way with this same account on xSqlServer and now it fails with this new package.
The account is valid and I can RDP to the server with that account and creds.
Error:

2018-02-02 11:26:30 Slp: Validation for setting 'SQLSVCACCOUNT' failed. Error message: The SQL Server service account login or password is not valid. Use SQL Server Configuration Manager to update the service account.

Log File:
SQLSVCACCOUNT:                 Dev2x.Azure.aon.net\svc-sqlserverxx
SQLSVCPASSWORD:                *****

I tried changing to this format. No difference.
SQLSVCACCOUNT:                 Dev2x\svc-sqlserverxx
SQLSVCPASSWORD:                *****

No that should work. I just did an install a couple of hours ago using a domain account, and the integration tests installs using a local account (to mimic installing as a domain account).

ya this one is throwing me. I can run in xSqlServer and it works perfect. When I use the newest SqlServerDsc it fails.

That sound strange.
Can ypu post your configuration?
What version of SQL Server are you installing?
Are you using SQLPS or SqlServer?

SQL Server 2014 right now.
I had to put xxx for some entries, but nothing important for the install. If I did not give enough let me know!
SqlSetup SqlServerSetup {
BrowserSvcStartupType = 'Automatic'
Features = $environmentNode.sqlInstallFeatures
InstallSharedDir = $roleNode.installSharedDir
InstallSharedWOWDir = $roleNode.installSharedWowDir
InstallSQLDataDir = $roleNode.installSqlDataDir
InstanceName = $environmentNode.sqlInstanceName
InstanceDir = $roleNode.sqlInstanceDir
SAPWd = $sqlSaAccountCreds
SecurityMode =  $roleNode.securityMode
PsDscRunAsCredential = $adminCreds
SourcePath = $roleNode.sourcePath
# SourceFolder = $roleNode.sqlSourceFolder
SQLBackupDir = $roleNode.sqlBackupDir
SQLCollation = $roleNode.sqlCollation
SQLSvcAccount = $SQLServiceCreds
SQLSysAdminAccounts = $environmentNode.sqlSysAdminAccounts
SQLTempDBDir = $roleNode.sqlTempDbDir
SQLTempDBLogDir = $roleNode.sqlTempDbLogDir
SQLUserDBDir = $roleNode.sqlUserDbDir
SQLUserDBLogDir = $roleNode.sqlUserDbLogDir
UpdateSource = $roleNode.updateSource
UpdateEnabled = $roleNode.updateEnabled
SuppressReboot = $False
ForceReboot = $False
#TODO: Need to come up with non hard coded solution
DependsOn = '[WaitForVolume]WaitForISO','[Disk]CreateDrivesSQLTemp','[Disk]CreateDrivesSQLLog','[Disk]CreateDrivesSQLSystem','[Disk]CreateDrivesSQLData'
}
PSD1:
@{
environment = 'infra'
diskDrives = @(
@{
diskFriendlyName = 'SQLData'
driveLetter = 'F'
driveSize = 2100GB
},
@{
diskFriendlyName = 'SQLLog'
driveLetter = 'L'
driveSize = 1500GB
},
@{
diskFriendlyName = 'SQLSystem'
driveLetter = 'E'
driveSize = 25GB
},
@{
diskFriendlyName = 'SQLTemp'
driveLetter = 'T'
driveSize = 1500GB
}
)
domainName = 'Dev2x.Azure.xxx.net'
octopusEnvironment = 'Infrastructure'
ouPath = 'OU=SQL,OU=USA,OU=Servers,OU=NA,OU=Regions,DC=dev2x,DC=azure,DC=xxx,DC=net'
remoteUsers = @('NAAG-xxx-Deploy', 'NAAG-xxx-dba')
sqlCred1 = 'dbmaintlrs'
sqlIdentity1 = 'xxxdbmaintlrs'
sqlCred2 = 'dbmaintragrs'
sqlIdentity2 = 'xxxdbmaintstdrgrs'
sqlCred3 = 'dbmaintzrs'
sqlIdentity3 = 'xxxbackupsstdzrs'
sqlInstallFeatures = 'SQLENGINE,SSMS,ADV_SSMS,IS,FULLTEXT,BC,CONN'
sqlInstanceName = 'INFRA01'
sqlIso = 'en_sql_server_2014_developer_edition_with_service_pack_1_x64_dvd_6668542.iso'
sqlSysAdminAccounts = @('NAAG-xxx-Admin','NAAG-xxx-Deploy','NAAG-xxx-DBA','NT AUTHORITY\SYSTEM','NT SERVICE\Winmgmt','Svc-SQLServerFA1','svc-WinServerFA1')
sqlServerDomainAccounts = @('Dev2i\NAAG-xxx-Deploy', 'Dev2i\svc-xxxIIS')
tcpPort = 'xxx'
VaultName = "xxx-weu-infra"
virtualDiskLayoutType = 'Simple'
},

Role = @(
@{
Role = 'SqlServer'
installSharedDir = 'C:\Program Files\Microsoft SQL Server'
installSharedWOWDir = 'C:\Program Files (x86)\Microsoft SQL Server'
installSqlDataDir = 'E:\TRPMSINFRA01'
octopusListenPort = '10933'
octopusRole = 'New-DB'
octopusServerUrl = 'https://deploy.xxx.com'
RequiredDirectories = @('T:\BatchFiles','T:\MSSQLJobLogs','T:\SSISPackages')
saUserName = 'sa'
securityMode = 'SQL'
sqlSourceFolder = ""
sourcePath = "G:"
sqlAuthUsers = @(
@{
userName = 'xxx'
keyVaultKey = 'SQL-xxx'
roleName = 'sysadmin'
},
@{
userName = 'Hangfire'
keyVaultKey = 'SQL-Hangfire'
roleName = 'sysadmin'
},
@{
userName = 'OctopusDeploy'
keyVaultKey = 'SQL-OctopusDeploy'
roleName = 'sysadmin'
},
@{
userName = 'TDE-Local-Principal'
keyVaultKey = 'SQL-TDE-Local-Principal'
roleName = 'sysadmin'
},
@{
userName = 'TDE-Prod-Principal'
keyVaultKey = 'SQL-TDE-Prod-Principal'
roleName = 'sysadmin'
}
)
sqlBackupDir = 'T:\Backups'
sqlCollation = 'SQL_Latin1_General_CP1_CI_AS'
sqlInstanceDir ='E:\Microsoft SQL Server'
sqlIsoDriveAssignment = 'G'
sqlServiceUserName = 'svc-sqlserverxx'
sqlTempDbDir = 'd:\TRPMSINFRA01'
sqlTempDbLogDir = 'd:\TRPMSINFRA01'
sqlUserDbDir = 'F:\TRPMSINFRA01'
sqlUserDbLogDir = 'L:\TRPMSINFRA01'
storageSpaceName = 'MS-SQL-Drives'
SoftwareList = (
@{
Type = 'SelfInstall'
Key = 'vcredist_x64'
Name = "Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501"
Archive = 'vcredist_x64.zip'
},
@{
Type = 'SelfInstall'
Key = 'DLMAutomation'
Name = "RedGate DLM Automation Suite"
Archive = 'DLMAutomation.zip'
},
@{
Type = 'SelfInstall'
Key = 'curl'
Name = "curl"
Archive = 'curl.zip'
},
@{
Type = 'MsiPackage'
Key = 'AzureKeyVaultConnector'
Name = "SQL Server Connector for Microsoft Azure Key Vault"
Archive = 'SQLServerConnectorforMicrosoftAzureKeyVault.msi'
File = 'SQLServerConnectorforMicrosoftAzureKeyVault.msi'
Args = '/passive'
ProductId = "2F17A369-AE10-4D0A-B897-D432C257A0CA"
}
)
updateEnabled = 'False'
updateSource = 'MU'
virtualDiskProvisioningType = 'Thin'
}
);

Still trying to figure this one out....
I generate my SVC creds with this:
$sqlServicePw = (Get-AzureKeyVaultSecret -VaultName $vaultName -Name $nonNodeData.sqlServiceSecretName).SecretValue
$sqlServiceCreds = New-Object System.Management.Automation.PSCredential("$($environmentNode.DomainName)$($roleNode.sqlServiceUserName)", $sqlServicePw)
Which I than pass into:
SqlSetup SqlServerSetup {
SQLSvcAccount = $SQLServiceCreds
}
Which gives this Error:
2018-02-02 11:26:30 Slp: Validation for setting 'SQLSVCACCOUNT' failed. Error message: The SQL Server service account login or password is not valid. Use SQL Server Configuration Manager to update the service account.
Log File:
SQLSVCACCOUNT: Dev2x.Azure.xxx.net\svc-sqlserverxx
SQLSVCPASSWORD: *****
Everything seems correct when I run the commands in powershell and verify the results. This is the same process I used in xSqlServer which zero changes, which worked. I am kind of at a loss right now.

it seems my PsDscRunAsCredential was causing this. Not sure why it worked before, but I changed this to a network account and it is working. Having the RunAs as a local account and the installer as a network account was not working :)

repo: PowerShell/SqlServerDsc


text:
Integration test for xDscWebService are Broken and do not meet current practices

Details of the scenario you tried and the problem that is occurring
Integration tests fail when executed due to not being updated to meet current parameters in xDscWebService.
They are also destructive and don't use recent DSC Resource kit integration test practices.
Verbose logs showing the problem
N/A
Suggested solution to the issue
Fix the integration tests and use test drive. Ideally these should be able to work in AppVeyor.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
N/A
Version of the DSC module that was used ('dev' if using current dev branch)

Adding my notes from a duplicate Issue I opened:
Details of the scenario you tried and the problem that is occurring
As best as I can tell, Continuous Integration is not executing script Tests\Integration\MSFT_xDSCWebService.xxx.ps1 (although I'm not sure why). As an example, in this job, the automation executes the tests in the following script:
[00:00:51] Executing script C:\projects\xpsdesiredstateconfiguration\Tests\Integration\MSFT_xArchive.Integration.Tests.ps1

then skips to:
[00:00:58] Executing script C:\projects\xpsdesiredstateconfiguration\Tests\Integration\MSFT_xEnvironmentResource.EndToEnd.Tests.ps1

After that it continues to execute scripts in alphabetical order.
Further, I've tried to manually Invoke-Pester against this script on two different lab servers (Win 2016 / PS 5.1 and Win 2012 R2 / PS4), and they both fail with the following:
PS C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration> Invoke-Pester .\MSFT_xDSCWebService.xxx.ps1
Executing all tests in '.\MSFT_xDSCWebService.xxx.ps1'

Executing script .\MSFT_xDSCWebService.xxx.ps1

  Describing xDSCWebService
WARNING: The configuration 'InstallingService' is loading one or more built-in resources without explicitly importing associated modules. Add Import-DscResource –ModuleName 'PSDesire
dStateConfiguration' to your configuration to avoid this message.
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root
/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer E16-3 with user sid S-1-5-21-4227124094-3448144961-1010909551-500.
VERBOSE: [E16-3]: LCM:  [ Start  Set      ]
VERBOSE: [E16-3]: LCM:  [ Start  Resource ]  [[WindowsFeature]DSCServiceFeature]
VERBOSE: [E16-3]: LCM:  [ Start  Test     ]  [[WindowsFeature]DSCServiceFeature]
VERBOSE: [E16-3]:                            [[WindowsFeature]DSCServiceFeature] The operation 'Get-WindowsFeature' started: DSC-Service
VERBOSE: [E16-3]:                            [[WindowsFeature]DSCServiceFeature] The operation 'Get-WindowsFeature' succeeded: DSC-Service
VERBOSE: [E16-3]: LCM:  [ End    Test     ]  [[WindowsFeature]DSCServiceFeature]  in 0.2750 seconds.
VERBOSE: [E16-3]: LCM:  [ Skip   Set      ]  [[WindowsFeature]DSCServiceFeature]
VERBOSE: [E16-3]: LCM:  [ End    Resource ]  [[WindowsFeature]DSCServiceFeature]
VERBOSE: [E16-3]: LCM:  [ End    Set      ]
VERBOSE: [E16-3]: LCM:  [ End    Set      ]    in  0.3680 seconds.
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.396 seconds
    [+] Installing Service 1.65s
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root
/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer E16-3 with user sid S-1-5-21-4227124094-3448144961-1010909551-500.
VERBOSE: [E16-3]: LCM:  [ Start  Set      ]
VERBOSE: [E16-3]: LCM:  [ Start  Resource ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]: LCM:  [ Start  Test     ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]:                            [[xDSCWebService]PSDSCPullServer] Check Ensure
VERBOSE: [E16-3]:                            [[xDSCWebService]PSDSCPullServer] The Website TestPSDSCPullServer is not present
VERBOSE: [E16-3]: LCM:  [ End    Test     ]  [[xDSCWebService]PSDSCPullServer]  in 0.0110 seconds.
VERBOSE: [E16-3]: LCM:  [ Start  Set      ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]: LCM:  [ End    Set      ]  [[xDSCWebService]PSDSCPullServer]  in 0.0290 seconds.
    [-] Creating Sites 398ms
      Expected no exception to be thrown, but an exception "PowerShell DSC resource MSFT_xDSCWebService  failed to execute Set-TargetResource functionality with error message: Error:
 Cannot use best practice security settings with unencrypted traffic. Please set UseSecurityBestPractices to $false or use a certificate to encrypt pull server traffic. " was thrown
from C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\MSFT_xDSCWebService.xxx.ps1:84 char:17
          + ...             Start-DscConfiguration -Path $creatingSitesMofPath -Wait  ...
          +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
      85:             } | Should -Not -Throw
      at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\MSFT_xDSCWebService.xxx.ps1: line 63
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root
/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer E16-3 with user sid S-1-5-21-4227124094-3448144961-1010909551-500.
VERBOSE: [E16-3]: LCM:  [ Start  Set      ]
VERBOSE: [E16-3]: LCM:  [ Start  Resource ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]: LCM:  [ Start  Test     ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]:                            [[xDSCWebService]PSDSCPullServer] Check Ensure
VERBOSE: [E16-3]:                            [[xDSCWebService]PSDSCPullServer] The Website TestPSDSCPullServer is not present as requested
VERBOSE: [E16-3]: LCM:  [ End    Test     ]  [[xDSCWebService]PSDSCPullServer]  in 0.0040 seconds.
VERBOSE: [E16-3]: LCM:  [ Skip   Set      ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]: LCM:  [ End    Resource ]  [[xDSCWebService]PSDSCPullServer]
VERBOSE: [E16-3]: LCM:  [ End    Set      ]
VERBOSE: [E16-3]: LCM:  [ End    Set      ]    in  0.0410 seconds.
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.065 seconds
    [+] Removing Sites 1.43s
    [-] CreatingSitesWithFTP 742ms
      Expected no exception to be thrown, but an exception "Invalid class string (Exception from HRESULT: 0x800401F3 (CO_E_CLASSSTRING))" was thrown from C:\Program Files\WindowsPowe
rShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\MSFT_xDSCWebService.xxx.ps1:144 char:21
          + ...                   (Get-Website -Name 'DummyFTPSite').ftpserver.stop()
          +                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
      168:             }  | Should -Not -Throw
      at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\Tests\Integration\MSFT_xDSCWebService.xxx.ps1: line 137
Tests completed in 4.22s
Tests Passed: 2, Failed: 2, Skipped: 0, Pending: 0, Inconclusive: 0

Suggested solution to the issue
Fix or re-write Integration tests for MSFT_xDSCWebService and make sure they are invoked by Continuous Integration.
Version of the DSC module that was used ('dev' if using current dev branch)
dev

Marking this one as high priority. Until we get this fixed, we can't check in code for the xDscWebService resource with confidence. As an example, I'm considering putting #506 on hold until this is complete.
Is anyone planning on volunteering for this one? If not I can take a crack at it.

Alright, I AM working on this one.

authors: PlagueHO mhendric

repo: PowerShell/xPSDesiredStateConfiguration

license: mit

license_source: bigquery


text:
Fix bug in xDiskAccessPath and xMountImage and enabled Integration Tests - Fixes #102, #105

This PR primarily fixes #102.
However during investigation of #102, I found a way to enable the integration tests to run in AppVeyor by using DISKPART to create a new VHD. I decided to enable these to ensure that this module is being effectively tested on Windows Server 2012 R2.
This highlighted issue #105 as the integration tests failed on the AppVeyor build agent (but passed on Windows 10 and Windows Server 2016). I identified the cause of the problem and fixed it as well so that I could commit this fix.
The PR changes are as per:

xDiskAccessPath:

Fix error when used on Windows Server 2012 R2 - See Issue 102.

Removed requirement on Hyper-V PowerShell module to execute integration tests.
xMountImage:

Fix error when mounting VHD on Windows Server 2012 R2 - See Issue 105

This change is

Codecov Report

Merging #106 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff         @@
##           dev   #106    +/-   ##
===================================
+ Coverage   92%    92%   +<1%
===================================
  Files        5      5
  Lines      645    650     +5
===================================
+ Hits       594    599     +5
  Misses      51     51

Great reasoning to make use of DiskPart to enable the integration tests in appveyor!!

Reviewed 14 of 14 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Modules/xStorage/DSCResources/MSFT_xMountImage/MSFT_xMountImage.psm1, line 80 at r1 (raw file):

            # Find the first 'Basic' partition
            $partitions = $disk | Get-Partition
            $partition = $partitions | Where-Object -Property Type -EQ 'Basic'

it's -eg lowercase.
Why the breakup and not?
$partition = $disk | Get-Partition | Where-Object -Property Type -eq 'Basic'

Or
$partition = $disk | Get-Partition |
    Where-Object -Property Type -eq 'Basic'

Modules/xStorage/DSCResources/MSFT_xMountImage/MSFT_xMountImage.psm1, line 558 at r1 (raw file):

        # Find the first 'Basic' partition to mount
        $partitions = $disk | Get-Partition
        $partition = $partitions | Where-Object -Property Type -EQ 'Basic'

same comments as before

Tests/TestHelpers/CommonTestHelper.psm1, line 105 at r1 (raw file):

    $tempScriptPath = Join-Path -Path $ENV:Temp -ChildPath 'DiskPartVdiskScript.txt'
    Write-Verbose -Message ('Creating DISKPART script {0}' -f $tempScriptPath)
    Set-Content -Path $tempScriptPath -Value "create vdisk file=`"$Path`" type=expandable maximum=$SizeInMB"

From experience, this file needs to have Ascii encoding. Recommend adding -Encoding Ascii
The text is also expected to be uppercase if I remember correctly.
create vdisk FILE="" TYPE=EXPANDABLE MAXIMUM=1024

---

*Comments from [Reviewable](https://reviewable.io:443/reviews/powershell/xstorage/106#-:-KnOPzFkJm0IHZDegcLq:bfqnwry)*
<!-- Sent from Reviewable.io -->

Thanks for reviewing @bgelens ! Appreciate the work and detail as always! Changes made and questions answered.

Review status: 13 of 14 files reviewed at latest revision, 3 unresolved discussions.

Modules/xStorage/DSCResources/MSFT_xMountImage/MSFT_xMountImage.psm1, line 80 at r1 (raw file):
Previously, bgelens (Ben Gelens) wrote…
it's -eg lowercase.
Why the breakup and not?
$partition = $disk | Get-Partition | Where-Object -Property Type -eq 'Basic'

Or
$partition = $disk | Get-Partition |
    Where-Object -Property Type -eq 'Basic'

Good question. A couple of reasons:

When I was debugging this problem I found it much easier to track down the problem by splitting up statements so I could find out and compare the different outputs on the different OS's.
This best practice https://github.com/PowerShell/DscResources/blob/master/BestPractices.md#use-variables-rather-than-extensive-piping

However, I realize this wouldn't really be excessive piping. So I'm OK to reassemble if you'd prefer - as hopefully I'll not need to do any further debugging on this (but never say never). Your call :grin:

Modules/xStorage/DSCResources/MSFT_xMountImage/MSFT_xMountImage.psm1, line 558 at r1 (raw file):
Previously, bgelens (Ben Gelens) wrote…
same comments as before

See above.

Tests/TestHelpers/CommonTestHelper.psm1, line 105 at r1 (raw file):
Previously, bgelens (Ben Gelens) wrote…
From experience, this file needs to have Ascii encoding. Recommend adding -Encoding Ascii
The text is also expected to be uppercase if I remember correctly.
create vdisk FILE="" TYPE=EXPANDABLE MAXIMUM=1024

Good catch. Done.

Comments from Reviewable

 No need to change further :smile:

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Thanks @bgelens - really appreciate your help! Things are really beginning to move around the repos now!

authors: PlagueHO bgelens codecov-io

repo: PowerShell/xStorage


text:
Not working with the new patch

The addon is not working with the new patch
It doesn't appear in the settings and it doesn't populate the previously saved bars anymore
Error:
398x UniversalBar/UniversalBarSettings.lua:132: attempt to call global 'InterfaceOptions_AddCategory' (a nil value)
[string "@UniversalBar/UniversalBarSettings.lua"]:132: in function `InitializeSettings'
[string "@UniversalBar/UniversalBar.lua"]:229: in function <UniversalBar/UniversalBar.lua:226>
Locals:
self =  {
eventFrame = Frame {
}
L =  {
}
}
title = FontString {
}
autoLoadAtLoginCheckbox = UniversalBarCheckAutoLoadAtLogin {
Text = UniversalBarCheckAutoLoadAtLoginText {
}
text = UniversalBarCheckAutoLoadAtLoginText {
}
label = UniversalBarCheckAutoLoadAtLoginText {
}
}
clearUnsavedActionSlots = UniversalBarCheckClearUnsavedActionSlots {
Text = UniversalBarCheckClearUnsavedActionSlotsText {
}
text = UniversalBarCheckClearUnsavedActionSlotsText {
}
label = UniversalBarCheckClearUnsavedActionSlotsText {
}
}
AutosaveSlotChangesCheckbox = UniversalBarCheckAutosaveSlotChanges {
Text = UniversalBarCheckAutosaveSlotChangesText {
}
text = UniversalBarCheckAutosaveSlotChangesText {
}
label = UniversalBarCheckAutosaveSlotChangesText {
}
}
unibar1 = UniversalBarCheckunibar1 {
Text = UniversalBarCheckunibar1Text {
}
text = UniversalBarCheckunibar1Text {
}
label = UniversalBarCheckunibar1Text {
}
}
unibar2 = UniversalBarCheckunibar2 {
Text = UniversalBarCheckunibar2Text {
}
text = UniversalBarCheckunibar2Text {
}
label = UniversalBarCheckunibar2Text {
}
}
unibar3 = UniversalBarCheckunibar3 {
Text = UniversalBarCheckunibar3Text {
}
text = UniversalBarCheckunibar3Text {
}
label = UniversalBarCheckunibar3Text {
}
}
unibar4 = UniversalBarCheckunibar4 {
Text = UniversalBarCheckunibar4Text {
}
text = UniversalBarCheckunibar4Text {
}
label = UniversalBarCheckunibar4Text {
}
}
unibar5 = UniversalBarCheckunibar5 {
Text = UniversalBarCheckunibar5Text {
}
text = UniversalBarCheckunibar5Text {
}
label = UniversalBarCheckunibar5Text {
}
}
unibar6 = UniversalBarCheckunibar6 {
Text = UniversalBarCheckunibar6Text {
}
text = UniversalBarCheckunibar6Text {
}
label = UniversalBarCheckunibar6Text {
}
}
unibar7 = UniversalBarCheckunibar7 {
Text = UniversalBarCheckunibar7Text {
}
text = UniversalBarCheckunibar7Text {
}
label = UniversalBarCheckunibar7Text {
}
}
unibar8 = UniversalBarCheckunibar8 {
Text = UniversalBarCheckunibar8Text {
}
text = UniversalBarCheckunibar8Text {
}
label = UniversalBarCheckunibar8Text {
}
}
saveBarConfigButton = UniversalBarSaveBarConfigButton {
Right = Texture {
}
Left = Texture {
}
fitTextWidthPadding = 40
Text = UniversalBarSaveBarConfigButtonText {
}
Middle = Texture {
}
fitTextCanWidthDecrease = true
}
loadBarConfigButton = UniversalBarLoadBarConfigButton {
Right = Texture {
}
Left = Texture {
}
fitTextWidthPadding = 40
Text = UniversalBarLoadBarConfigButtonText {
}
Middle = Texture {
}
fitTextCanWidthDecrease = true
}
clearBarConfigButton = UniversalBarClearBarConfigButton {
Right = Texture {
}
Left = Texture {
}
fitTextWidthPadding = 40
Text = UniversalBarClearBarConfigButtonText {
}
Middle = Texture {
}
fitTextCanWidthDecrease = true
}
(*temporary) = nil
(*temporary) = Frame {
name = "UniversalBar"
}
(*temporary) = "attempt to call global 'InterfaceOptions_AddCategory' (a nil value)"
defaultOptions =  {
AutosaveSlotChanges = false
ClearUnsavedActionSlots = true
Bars =  {
}
AutoLoadAtLogin = true
BarConfig =  {
}
}
frame = Frame {
name = "UniversalBar"
}
addonName = "UniversalBar"
L =  {
Bars =  {
}
Settings =  {
}
Errors =  {
}
}
UniversalBar =  {
eventFrame = Frame {
}
L =  {
}
}

Sorry for the delay on this. Been held up with work and had no time to keep up with patch changes. Version 1.1.4 should be available shortly on Curseforge, WoWInterface and Wago to address this.


text:
specify region in NGROK ssh connection

specify the NGROK region with default region as "us" and add an option to change the region.
so that it work fast in onother reagion as well.

I recommend using Agro because ngrok is very slow but I will try to complete your request.

repo: PradyumnaKrishna/Colab-Hacks


text:
Wisdom upgrades

"Keeper of Wisdom" feature from original game.

Closed by 0ef7bf4bdbe21774880f9a6ac7f6beade36927e1 and prev commits


text:
Adapt to recent PRs

Questions
Answers

Description?
Autoupgrade PR for recent PRs - https://github.com/PrestaShop/PrestaShop/pull/37236/ and https://github.com/PrestaShop/PrestaShop/pull/36873/ and added a comment about https://github.com/PrestaShop/PrestaShop/pull/35843/ (in dev branch)

Type?

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company

How to test?

How to test

Upgrade from 8.1 to 9.0
Open phpmyadmin
See that:

A) meta_keywords columns is removed from all tables.
B) There is PS_DEFAULT_LANGUAGE_URL_PREFIX record in ps_configuration.
C) There is PS_SEPARATOR_FILE_MANAGER_SQL record in ps_configuration.

No need to test anything else, not in the scope of this PR

@Hlavtox PR https://github.com/PrestaShop/autoupgrade/pull/1010 will fix CI

@M0rgan01 Ok I will rebase after it's merged. :-)

@M0rgan01 Ready to go, tests should be green. :-)

@AureRita You are rebasing to wrong branch, this PR targets 6.x

Yes Indeed, sorry didn't see that this parameter change

authors: AureRita Hlavtox M0rgan01

repo: PrestaShop/autoupgrade


text:
switch the request

Questions
Answers

Description?
Here we set a custom request for performance

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes {http://forge.prestashop.com/browse/EMKTG-210}.

Thanks @pablopolyte

authors: NeOMakinG pablopolyte

repo: PrestaShop/blockwishlist


text:
Comet Virtual Method Error

Hi all,
Has anyone run into problems running athena++ on SDSC's Comet?  When compiled with their intel compiler ( intel 2018.1.163) the code crashes after initialization with the following error:
pure virtual method called
terminate called without an active exception
It seems that this happens for any input file and configuration with the unedited public version.  When compiled with gcc the code runs fine.  Strangely, when using the same intel 2018.1.163 compiler on a different cluster the code also runs fine, so this seems to be a Comet-specific problem.  Also, the previous version of the code works well on Comet.

Known problem with certain Intel compilers from 2017 (and I guess early 2018) that affect versions of Athena++ after I rewrote the boundary values classes and added passive scalars. @tomidakn and I were the only ones to encounter it, I believe.

Is there a work around?
On Tue, Jul 7, 2020 at 6:16 PM Kyle Gerard Felker notifications@github.com
wrote:

Known problem with certain Intel compilers from 2017 (and I guess early
2018) that affect versions of Athena++ after I rewrote the boundary values
classes and added passive scalars. @tomidakn https://github.com/tomidakn
and I were the only ones to encounter it, I believe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PrincetonUniversity/athena-public-version/issues/55#issuecomment-655164742,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6S4RT3LUFXHIVLSK3C22LR2ONB5ANCNFSM4OTWLHLQ
.

No. Newer Intel compiler.

Right, I hit this last year (#29) with Intel v18 and there was no issue with Intel v19.

Got it, thanks.  I'll probably just transfer the comet time since they only
have the one version.
On Tue, Jul 7, 2020 at 7:15 PM Tim Waters notifications@github.com wrote:

Right, I hit this last year (#29
https://github.com/PrincetonUniversity/athena-public-version/issues/29)
with Intel v18 and there was no issue with Intel v19.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PrincetonUniversity/athena-public-version/issues/55#issuecomment-655186998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6S4RWFNFYB5MLMM3U6VZTR2OUCPANCNFSM4OTWLHLQ
.

authors: felker smressle trwaters


text:
Minified CSS?

Currently working on #134, and wow, my file has surpassed 8kB, and I'm still not done! (Though to be fair, I have several lines' worth of comments at the top.) I was wondering if we could provide the minified versions of the CSS. While most of the themes weigh less than 5kB, I still think it'll be helpful overall, especially as Prism prides itself on being small.
I have seen #70 which was unfortunately closed by the OP due to unresponsiveness, as well as https://github.com/PrismJS/prism/pull/2553 which has been pending for over eight months now.
I am also aware of the earlier https://github.com/PrismJS/prism/issues/956 but I really don't think that "most people modify the CSS at least to a degree"... Even if this were the case, providing the minified CSS does not necessarily mean that we have to stop providing the non-minified ones.
I guess what I want to say overall is, we should give users the convenience of having the minified files ready to go (which is in line with Prism's selling point of being really small), while also letting them have the non-minified one if they would rather modify it directly for their own uses.

I'll make a PR adding minified themes.
Regarding themes over at Prism: PrismJS/prism#2553 seems to have gone stale. I'll try to finish it today.

Whoa, that's fast! Thank you so much for all your efforts :)

authors: RunDevelopment hoonweiting

repo: PrismJS/prism-themes


text:
prism@1.6.0 extremely slow with JS snippet with comments (~8s on Chrome/macbookpro)

This seems to be related to the comments because if I remove all of them, it no longer hangs for 8 seconds!
//@flow
import React from "react";
import { Uniform, Shaders, Node, GLSL, NearestCopy } from "gl-react";
import { Surface } from "gl-react-dom";
import timeLoop from "../../HOC/timeLoop";

export const shaders = Shaders.create({
  InitGameOfLife: {
    // returns white or black randomly
    frag: GLSL`
precision highp float;
varying vec2 uv;
float random (vec2 uv) {
  return fract(sin(dot(uv, vec2(12.9898,78.233))) * 43758.5453);
}
void main() {
  gl_FragColor = vec4(vec3(step(0.5, random(uv))), 1.0);
}`
  },
  GameOfLife: {
    // implement Game Of Life.
    frag: GLSL`
precision highp float;
varying vec2 uv;
uniform float size;
uniform sampler2D t; // the previous world state
void main() {
  float prev = step(0.5, texture2D(t, uv).r);
  float c = 1.0 / size;
  float sum =
  step(0.5, texture2D(t, uv + vec2(-1.0, -1.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2(-1.0,  0.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2(-1.0,  1.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2( 0.0,  1.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2( 1.0,  1.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2( 1.0,  0.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2( 1.0, -1.0)*c).r) +
  step(0.5, texture2D(t, uv + vec2( 0.0, -1.0)*c).r);
  float next = prev==1.0 && sum >= 2.0 && sum <= 3.0 || sum == 3.0 ? 1.0 : 0.0;
  gl_FragColor = vec4(vec3(next), 1.0);
}`
  }
});

const refreshEveryTicks = 20;

export const GameOfLife = ({ tick }) => {
  // Changing size is "destructive" and will reset the Game of Life state
  const size = 16 * (1 + Math.floor(tick / refreshEveryTicks));
  // However, we can conditionally change shader/uniforms,
  // React reconciliation will preserve the same <Node> instance,
  // and our Game of Life state will get preserved!
  return tick % refreshEveryTicks === 0
    ? <Node
        shader={shaders.InitGameOfLife}
        width={size}
        height={size}
        backbuffering // makes Node holding 2 fbos that get swapped each draw time
        sync // force <Node> to draw in sync each componentDidUpdate time
      />
    : <Node
        shader={shaders.GameOfLife}
        width={size}
        height={size}
        backbuffering
        sync
        uniforms={{
          t: Uniform.Backbuffer, // Use previous frame buffer as a texture
          size
        }}
      />;
};

const GameOfLifeLoop = timeLoop(GameOfLife, { refreshRate: 20 });

export default () => (
  <Surface width={384} height={384}>
    <NearestCopy>
      <GameOfLifeLoop />
    </NearestCopy>
  </Surface>
);

Thanks for reporting, the performance issue should be fixed now. (Though the Node tags are still not highlighted since Prism does not support comments in those.)

woo, cool thanks

authors: Golmote gre

repo: PrismJS/prism


text:
Use css variables in themes

Motivation
When writing a dark mode for my application I wanted to use css variables to switch the colours when pressing a button.
Description
This would look something like this:
/**
 * prism.js tomorrow night eighties for JavaScript, CoffeeScript, CSS and HTML
 * Based on https://github.com/chriskempson/tomorrow-theme
 * @author Rose Pritchard
 */

code[class*="language-"],
pre[class*="language-"] {
	color: var(--prism-maintext, #ccc);
	background: none;
	font-family: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
	font-size: 1em;
	text-align: left;
	white-space: pre;
	word-spacing: normal;
	word-break: normal;
	word-wrap: normal;
	line-height: 1.5;

	-moz-tab-size: 4;
	-o-tab-size: 4;
	tab-size: 4;

	-webkit-hyphens: none;
	-moz-hyphens: none;
	-ms-hyphens: none;
	hyphens: none;

}

/* Code blocks */
pre[class*="language-"] {
	padding: 1em;
	margin: .5em 0;
	overflow: auto;
}

:not(pre) > code[class*="language-"],
pre[class*="language-"] {
	background: var(--prism-background, #2d2d2d);
}

/* Inline code */
:not(pre) > code[class*="language-"] {
	padding: .1em;
	border-radius: .3em;
	white-space: normal;
}

.token.comment,
.token.block-comment,
.token.prolog,
.token.doctype,
.token.cdata {
	color: var(--prism-text, #999);
}

.token.punctuation {
	color: var(--prism-punctuation, #ccc);
}

.token.tag,
.token.attr-name,
.token.namespace,
.token.deleted {
	color: var(--prism-names, #e2777a);
}

.token.function-name {
	color: var(--prism-punctuation, #6196cc);
}

.token.boolean,
.token.number,
.token.function {
	color: var(--prism-functions, #f08d49);
}

.token.property,
.token.class-name,
.token.constant,
.token.symbol {
	color: var(--prism-symbol, #f8c555);
}

.token.selector,
.token.important,
.token.atrule,
.token.keyword,
.token.builtin {
	color: var(--prism-keywords, #cc99cd);
}

.token.string,
.token.char,
.token.attr-value,
.token.regex,
.token.variable {
	color: var(--prism-strings, #7ec699);
}

.token.operator,
.token.entity,
.token.url {
	color: var(--prism-url, #67cdcc);
}

.token.important,
.token.bold {
	font-weight: bold;
}
.token.italic {
	font-style: italic;
}

.token.entity {
	cursor: help;
}

.token.inserted {
	color: var(--inserted, green);
}

And switching using a theme attribute on the root element.
:host([theme="dark"])  {
  --prism-maintext: #ccc;
  --prism-background: #2d2d2d;
  --prism-text: #999;
  --prism-keywords: #cc99cd;
  --prism-punctuation: #ccc;
  --prism-functions: #f08d49;
  --prism-strings:  #7ec699;
  --prism-namespace:  #e2777a;
  --prism-names: #6196cc;
  --prism-symbol: #f8c555;
  --prism-url: #9a6e3a;
}

:host(:not([theme="dark"])) {
  --prism-maintext: black;
  --prism-background: #f5f2f0;
  --prism-text: #999;
  --prism-keywords: #07a;
  --prism-punctuation: #999;
  --prism-functions: #f08d49;
  --prism-strings:  #690;
  --prism-namespace:  #e2777a;
  --prism-names: #6196cc;
  --prism-symbol: #DD4A68;
  --prism-url: #67cdcc;
}

Alternatives
At the moment I copied a theme to my project and modified it to use the variables. It would be great to be able to use this out of the box. Your themes could look like setting the variables instead of a copy of the styling.
This solution should be available next to the current themes as not all browsers support this yet.

For a similar reason, I recently made this:
https://github.com/antfu/prism-theme-vars
With a playground where you can preview and customize the theme. Hope it could be useful :)

For a similar reason, I recently made this:
https://github.com/antfu/prism-theme-vars
With a playground where you can preview and customize the theme. Hope it could be useful :)

authors: antfu richardwerkman


text:
Bot never goes under layer 0

with bot.pathfinder.setGoal(new GoalNear(1, -10, 0, 1)) the bot never goes under the layer 0.
It just stops from going where I want, and stops few layers above 0

I don't see why it would not be able to go below 0. I don't have to time to test right now. But I will look into it.

This should be fixed now with version 2.4.2

authors: IceTank mevenG

repo: PrismarineJS/mineflayer-pathfinder


text:
Add a Rate Us Option

Hello, my name is A.A.D.Sailaja. I am a Tech Enthusiastic and i'm looking forward to contribute in open source projects. Here in this project i would like to add a rate us option it will allow the user to rate our website and also he can suggest us to improve if any
Can you please assign me this issue under gssoc'24 @priyaaa1

@Priyaaa1 can you assign me this issue under GSSOC'24

@sailaja-adapa feedback page has been implemented in the website in which user can give rating to the StartConnect Hub.


text:
推理服务代码

有无这块的例子

直接用predict就行了呀

authors: ProHiryu xxllp

repo: ProHiryu/albert-chinese-ner


text:
Change readthedocs URL

We want to change all URLs to use the new ppafm name. The Github URL and project name can be changed on ReadTheDocs, but apparently they do not allow changing the doc page URL except by a written request: https://docs.readthedocs.io/en/stable/faq.html#how-do-i-change-my-project-slug-the-url-your-docs-are-served-at. But we can probably achieve the same by just making a new project page, so I'll try that first.

Ok, I created a new project at https://readthedocs.org/dashboard/ppafm/users/ and the new doc page URL is https://ppafm.readthedocs.io/en/latest/, and I deleted the old project. I sent invitations to @ProkopHapala and @yakutovicha to be maintainers for the new readthedocs project.
I'll also make a PR to change the URL in the README.

repo: Probe-Particle/ppafm


text:
[Dungeon] Update auf Java 21 LTS

Lt. https://openjdk.org/projects/jdk/21/ [^1] kommt am 19.09.2023 die neue LTS-Ausgabe von Java-SE raus: Java 21 LTS.
Bitte (dann) das Projekt updaten.
[^1]: auch hier: https://www.java.com/releases/ und hier: https://www.oracle.com/java/technologies/java-se-support-roadmap.html

@Lena241 hat mir heute mitgeteilt, dass ein einfaches hochziehen der Version auf Java 21 (auf Windows 11) nicht ausreicht. Vermutung liegt nahe dass der Gradlew-Wrapper ein update braucht.

Aktuell unterstützt Gradle Java 21 nur so halb.
Compiling & Testing geht, jedoch lässt sich Gradle nicht mit Java 21 ausführen, dafür muss eine Java Version zwischen 8 und 20 installiert sein. Siehe https://docs.gradle.org/current/userguide/compatibility.html

Aktuell unterstützt Gradle Java 21 nur so halb. Compiling & Testing geht, jedoch lässt sich Gradle nicht mit Java 21 ausführen, dafür muss eine Java Version zwischen 8 und 20 installiert sein. Siehe https://docs.gradle.org/current/userguide/compatibility.html

@fwatermann Danke für die Recherche! Irgendwie verstehe ich das noch nicht ganz: Warum kann Gradle selbst nicht auf Java 21 laufen? Gradle wird irgendwelche Features nutzen aus früheren Versionen, aber die sollten ja auch in Java 21 vorhanden sein (Abwärtskompatibilität)?

Das verstehe ich auch nicht so ganz. Ich spiele damit gleich mal ein bisschen rum.

Ich würde vor allem bei libGDX Probleme erwarten, weil die irgendwelche Sonderspielchen machen mit nativem Code und so. Hmmm. Naja, vielleicht ist es überzogen, jetzt schon auf JDK21 zu schielen und das kann dann erst im Januar/Februar passieren.

@fwatermann Schau mal https://docs.gradle.org/current/release-notes.html:

"... Java 21 is now supported for compiling, testing, and running such projects. ..."

Gradle 8.5 unterstützt JDK21: https://docs.gradle.org/8.5/release-notes.html

authors: AMatutat cagix fwatermann

repo: Programmiermethoden/Dungeon


text:
Add Basic Auth

in a secure environment (On prem in k8s) we would like to use a simpler authorization system such as basic Auth, a simple singular username and password is fine in our case for inter-service api calls.

fixed with relase

repo: Project-MONAI/monai-deploy-security


text:
update artifact verification logic

Signed-off-by: Jack Schofield jack.schofield@answerdigital.com

@jackschofield23 why does the verify objects exist function need to receive a dictionary instead of only the path?

I figured it was just easier to take the existing dictionary and filter out any non existent ones

repo: Project-MONAI/monai-deploy-storage


text:
[Tic 475] Implement useActiveOrg hook + minor repo refactoring

https://propelauth.atlassian.net/browse/TIC-475

Updated the useActiveOrg hook
Put hooks in own folder
Add @deprecated docstrings to deprecated functions
Added eslint to the repo

Updated recording:
https://github.com/PropelAuth/react/assets/36497022/72f7e9f2-6fb2-4ce8-99b5-67a1e031e57f

repo: PropelAuth/react


text:
Waters DDA changes

The Waters DDA changes discussed on a call with Matt and Brendan.
Waters DDA data is now processed with the DDAProcessor in the MassLynxSDK. This handles:

Lock mass corrected precursor mass (in future this will be expanded to use peak picking, rather than lock mass correcting the set mass)
Merging of adjacent MS2 scans which relate to the same set mass. The id of such scans is expanded with merged=23-25, though for compatibiltiy the scan=23 is still present, which indicates the first scan in the group.
Omitting the lock mass function

The biggest difference is that in 'DDA mode' SpectrumList_Waters creates each index entry 'on the fly' as the scan is retrieved. This avoids looking up the values twice in the index.
Currently this uses a beta version of the MassLynx SDK, therefore I have made this a draft pull request, so not to be merged now. We plan to have a new release version in the next couple of weeks, at which point I'll update the PR.

Look to be a couple of issues with the build/checks. I think both are a result of the MassLynxSDK being built a different way to previous releases, presumably with different versions of the C++ runtime.

We no longer have an x86 build. Is there a way to disable Waters raw support for the x86 build? Out of interest, is anyone still using x86?
There are some tiny changes in floating point numbers in the expected test results. Would you be happy with updating the expected results, provided we confirm all the changes are very small (they look to be in the 6th significant figure or thereabouts)?

Yes we can disable Waters for x86.

Don't suppose you could give me a hint on where to do this?

Yes we can disable Waters for x86.

Don't suppose you could give me a hint on where to do this?

Don't worry about it, I'll take care of it if you remove the x86 binaries from the 7z. BTW did you add the password to encrypt the 7z?

Well, that was weird. I used GitHub's CLI to checkout this PR. I made my change, tested it, committed it, and then tried to push it. I figured it would either fail to push to your fork or maybe work if it realized it was for a PR to our repo. I did NOT expect it to push to pwiz's master and apparently count this PR as merged. Oops! I had to force reset master to what it was at. And I guess this PR needs to be reissued? Here's a patch for the 32-bit disabling code. Which GitHub requires me to zip for no good reason!
disable-32bit-test.zip

authors: chambm pete-reay-waters

repo: ProteoWizard/pwiz


text:
Spanish Translate

The language Spanish is ready for their use to 100%.
By Sr. E

Hey there,
Thank you so much for your effort!
Did you get to check the current Spanish interface? It is already translated and available for webmail and apps. You can make the language changes in your ProtonMail account.
If this is a better version, would you be interested in bringing your contribution to our localization platform?
Please email me at contact@protonmail.ch
Best,
Irina

repo: ProtonMail/WebClient


text:
the program already is great. i just want to add Some suggestions

Description
the program already is great. i just want to add Some suggestions
1- can you pls add dark mode
2 -  can you stop the app to navigate to saved or pinned tap when user click save or pin request
some times you cheek for request and save them for later and when the app navigate your lose current focus on all request you examine
3- add method to save tap when user edit and reply request should be able to save the edited request
4- it there any news about scripting tool in win version that tool is really helpful

Hi @unknowen700, thank you for the suggestions.
For the dark mode, we already have the ticket Support Dark Theme, it's already in our To-Do list.
For the numbers two and three, I will suggest those to the founder and implement them if he accepts.
About the scripting tool, it will be implemented after the Network Condition Tool is released.

repo: ProxymanApp/proxyman-windows-linux


text:
Remove govuk-header overrides from index.scss

Remove govuk-header overrides from index.scss to fix the header alignment, and make the blue border the width of the page.

 Remove govuk-header overrides from index.scss


text:
Security For PufferTeam!!! VERY IMPORTANT!!!!

Hi everyone!
I'm Michael and user and "Web Developer" (Not in the team of PufferPanel).
Today i want to report this very huge security problem to the PufferTeam!
When a user Login or Change his profile settings, if you don't use SSL all information, also the password, are sent to the daemon without any encryption.... (See the media attached after)
So i want to suggest to make a encryption between daemon and WebUI, for SECURITY REASON!
ps. the string hidden in the screen isn't encrypted -_-
Thx

This is normal and the PufferPanel team can do nothing but recommend the use of SSL as they point out in the documentation.
Just set up a reverse proxy with SSL like anyone else to solve this problem.

Apeuova triggered

That's a scam....
Why not make a ENCRIPTYON.... it's not so difficult

Contributions are welcome in an open source project, so you can do so

There are multiple ways to go about encryption and problems with every one of them, not problems that prevent using a security mechanism, but problems making it hard or even impossible to do so generically for any user
Option 1: RTFM
This is the current approach
Expect the user to read the docs and not stumble around the world blindfolded, the docs provide a detailed guide on setting up a reverse proxy to handle TLS termination in a solid and reliable manner
Making the necessity of using TLS more visible to the unaware by adding a warning box similar to the one @Romitou mentioned to the install page of the docs would probably be a good idea though
Surely this approach has its own shortcomings in that a user can choose to ignore such a warning and at least to me it seems quite close to impossible to prevent ignoring warnings, but in my opinion, even with its shortcomings, this is the only sane approach I'm aware of
Option 2: Have the integrated webserver do TLS by default
Sounds like a good idea, right? But that falls short when it comes to certificates, sure, Let's Encrypt offers free certificates, but not every user has a domain and you won't see an authority giving you a cert for an IP, even if they did, PufferPanel has no clue what domain or IP it is running on and couldn't ask for a cert for your domain/IP on its own
Option 3: Build your own transport layer security
TLS as supported by your average webserver is usually provided through the use of libraries like openssl that are widely used, tested and in case of problems quickly fixed, implementing even just one encryption algorithm on your own to encrypt requests with you expose yourself to bugs in that implementation which are often hard to find or notice plus you need to manage key transfer yourself which can again be subject to bugs plus all the code becomes much more complex and thereby more prone to bugs and harder to maintain, and we haven't even touched on how it is necessary to have a trustable authority in the mix to prevent man in the middle attacks, so this option is completely out of the question
Another thing some might propose is to hash the password on the frontend before sending it out, but that doesn't help with anything as an attacker would still be able to catch whatever is sent to the API and just send a similar request themselves, so this one is dead in the water from the start
And just as a little sidenote: even if your request is sent over HTTPS your browsers devtools will show the unencrypted request as the browser knows what it sent to the server anyways (it does the client side TLS handling after all) and debugging requests with encrypted blobs you don't have the decryption key for is not really helpful
As @Romitou already said, contributions are welcome, so feel free to contribute, be it with a pull request or through pointing out/ discussing how this could be achieved, I'd assume everyone would be excited about a reasonable way of providing encryption in any context, I know I would be, but just yelling "make an encryption" won't get us there

authors: MichaelDevC Romitou nepcore tommasobenatti

repo: PufferPanel/PufferPanel


text:
rectangle

implement a rectangle that implements x, y, width, height as template

done


text:
[BUG] Unable to change any numbers.

Module Version: v1.4.1
Describe the bug
Unable to change number of charges on item, or charges consumed by spell, or cost/lvl
To Reproduce
Steps to reproduce the behavior:
attempt to enter a whole number into any of those fields. Field reverts back to default/already existing value.
Expected behavior
Number to change to input
Screenshots

Browser:
multiple
Foundry Version:
v11.315
Game System:
DnD5e - Fifth Edition System v2.4.1

Should be fixed on 1.4.2


text:
🛑 Overseerr is down

In c290b96, Overseerr (https://request.pxlbuzzard.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Overseerr is back up in a08b9f1.

repo: PxlBuzzard/upptime


text:
Add support for Python 3.10

Thanks for submitting a PR!
Please make sure to check for the following items:

[x] Add unit tests and integration tests where applicable.
If you've added an error code or changed an error code behavior,
you should probably add or change a test case file under tests/test_cases/ and add
it to the list under tests/test_definitions.py.
If you've added or changed a command line option,
you should probably add or change a test in tests/test_integration.py.
[x] Add a line to the release notes (docs/release_notes.rst) under "Current Development Version".
Make sure to include the PR number after you open and get one.

Please don't get discouraged as it may take a while to get a review.

Bump pytest to 6.2, the min version supporting 3.10.

Maybe use modern

Ditch pytest-pep8 from tests, it's unmaintained (last release 2014) and doesn't support pytest 6.2.
Drop the dot in py.test https://twitter.com/pytestdotorg/status/753767547866972160

Thanks for the PR! Will cut a release next week :)

repo: PyCQA/pydocstyle


text:
API surface to 'build' pyo3 and pyo3-ffi

For my use case, I would like to statically embed the python interpreter during the build time of my crate that uses PyO3. I am creating an InterpreterConfig within my crate's build.rs and I'm looking for a programmatic way to supply this as input to pyo3 and pyo3-ffi - this is not possible right now because both rely solely on pyo3-build-config's build set up. Per the documentation, the only way to currently override the interpreter config is to set the PYO3_CONFIG_FILE environment variable.
Some issues I'm having with environment variables being the only way to do this:

If my crate generates all resources needed for embedding the python interpreter, there is currently no way for me to use this in PyO3 (unless I take a complex multi-step approach wherein I build a crate that generates python embedding resources first, dump out a PyO3 config file, set the PYO3_CONFIG_FILE environment variable and then trigger the build of my crate that uses PyO3)
Requiring end-users set environment variables is quite cumbersome, especially when some of these need to be set to values generated in another crate.

One way I can think of to work around this is to provide a no-build feature that no ops the current build of pyo3 and pyo3-ffi and provides API surface (meant for usage within another crate's build.rs) to manually 'build'  the crate with a supplied InterpreterConfig argument.
Either way, I think it would be useful to have a programmatic way to supply the InterpreterConfig when building pyo3, since the config file is just the contents of that struct in a text file.

A no-build feature sounds extremely complex. To be comfortable merging such a thing I'd probably need convincing that your use case is common enough, and the simplification it brings warrants the additional maintenance burden. Sure the multi-step approach is a touch cumbersome, but at least it's using a relatively simple mechanism (the config file) which is useful in a lot of cases downstream.
Have you investigated the way PyOxidizer works? I suspect it has a similar solution.

I wonder - rather than making this a PyO3-specific thing, maybe there's a generic tool which could add any crate into another crate via a build.rs? That's at least got more flexibility than baking a no-build feature into the target crate.

I see this problem being applicable to anyone interested in creating standalone, distributable binaries that have some usage of PyO3 (there is also some related discussion in Issue #416.) . For our specific use case, we’re trying to create a standalone application that uses the bumble crate. Currently the crate requires you to have python + the python bumble library installed - instead, we’d like to generate all the resources needed and embed this ‘custom’ python interpreter during the build time of our crate.
I did take a look at how PyOxidizer does things and don’t know if that approach is applicable to every use-case that requires embedding of the python interpreter. For more context, PyOxidizer uses pyo3_ffi in a fairly complex manner to initialize the python interpreter through a MainPythonInterpreter struct - any subsequent python operation needs to go through this MainPythonInterpreter object. It looks like we are re-doing all the work that PyO3 already does on build + need to now be careful to use this new object (and not pyo3::Python), for any python usage. If there was a way to trigger the build of pyo3 with a programmatically supplied InterpreterConfig, any use case that needs to embed the python interpreter wouldn't need to repeat the above steps!
There are ways around this - a multi-step build that sets environment variables etc ( + passing around environment variables between dependencies poses its own set of challenges, assuming we circumvent those issues).. but it would be great to have native support for building with a supplied InterpreterConfig! If you think that there is value in this, I could create a draft of a no-build feature.

I still fear that there is a lot of complexity in such a feature, and it circumvents cargo's normal model of how dependencies work. If you can demonstrate that this is a relatively self-contained diff which is easy to maintain, I can possibly be persuaded to house it in pyo3. If it's very complex, my reservation that the maintenance/value tradeoff is not worth it may hold.
I still wonder if a generic tool which can apply this transformation to any crate is a better way to build such a feature, if it's possible.

Regarding PyOxidizer being unsuitable, I see this comment in the docs:

If you use pyo3 APIs like Python::with_gil() directly, you may inadvertently attempt to operate on a finalized interpreter. Therefore it is recommended to always go through a method on an MainPythonInterpreter instance in order to interact with the Python interpreter.

Cc @indygreg, was this a common problem? Maybe PyO3 should change Python::with_gil to check the interpreter is initialized (and not in the process of finalizing). Xref #3386 #3412

There may be room to improve PyO3's APIs. But I think my note on operating on finalized interpreter has more to do with bad API design on my part.
There are also some quirks where CPython relies too heavily on static variables and interpreter finalization leaves bad state, preventing spawning new interpreters in the same process. I spent way too much time fighting CPython and gave up, eventually running all interpreter tests in separate processes. I want to say these problems are getting cleaned up in CPython as part of making the GIL optional.
And having spent several days worth of time figuring out how to reliably embed Python in a [Rust] process, I suspect the amount of effort involved to support this in a turnkey way in PyO3 is non-trivial. There are also limitations in Cargo that stand in your way. There's a lot of hackiness in pyembed's build.rs and the way pyoxidizer invokes Cargo to get the binaries to build just right. Most of the magic is in https://github.com/indygreg/PyOxidizer/blob/main/pyoxidizer/src/project_building.rs and https://github.com/indygreg/PyOxidizer/blob/main/pyoxidizer/src/py_packaging/embedding.rs. I've long thought about extracting this functionality to a standalone crate because empowering people to more easily embed Python in Rust binaries without encumbering them with PyOxidizer would likely be valuable.

Thanks!
@luketpeterson @nandita-v perhaps a good way forward is to collaborate with @indygreg to extract into a standalone crate as suggested?

Given this issue has been inactive for over a year and I don't think there's a clear action here in PyO3, will close this for now.

authors: davidhewitt indygreg nandita-v


text:
Replace FromPyObject with std::convert::TryFrom

@messense objections?

That would be awesome. Utilize std traits should reduce learning curve.

It is not possible to implement TryFrom for Vec<T> where T: TryFrom<PyObjectRef>
So it is pretty useless.

add added TryFrom implementation, but we can not drop FromPyObject because of sequence conversion.


text:
buffer: tidy up exceptions

Motivated by https://github.com/PyO3/pyo3/pull/1128#discussion_r605227220

Could you please some tests where construction fails?

authors: davidhewitt kngwyu


text:
release: 0.17.2

Puts live all of the fixes since 0.17.1.
I'll push this out on Saturday.

With apologies I'll push this in the morning.

Release is live!


text:
make it possible to suppress solver output when running CBC and GLPK

Currently, the solver output is printed all the time to stdout using print when using CBC or GLPK.
This should be fixed, by also using the logging module.
I did set this to INFO, so that users relying on this output can still use it without going to debug logs.
It would be very cool to have release with this change afterwards

It does not look like I can do anything about 3.9-macos and 3.11-macos failing - it says Fatal Python error: Illegal instruction coming from pyscipopt solving with scip

Great! thanks @maurerle, would you mind putting a short note to the release notes? CI problem seemed to be due to a wrong installation (is working now).

Sure, is it fine like this @FabianHofmann ?

awesome, thanks!

@FabianHofmann could you please publish a release with this version soon?

@maurerle already happened :) conda should be available within the next hour

Would you also add the release here:
https://github.com/PyPSA/linopy/releases
This is also missing for 0.3.3
This would make it possible to easily see the changes since the last release :)

authors: FabianHofmann maurerle

repo: PyPSA/linopy


text:
Data import for inference with Speech Recognition Task only accepts filepath

🐛 Bug
SpeechRecognition Task predict() can not operate on raw tensor input.
To Reproduce
Steps to reproduce the behavior:

Load a wav2vec2  pytorch model
Load in audio data for inference and put in a tensor.
Run model.predict([input_tensor]) or model.predict({"input_values": input_tensor}
See error

 return filename.lower().endswith(extensions)
AttributeError: 'Tensor' object has no attribute 'lower'

or for the dictionary input:
"..\lib\site-packages\flash\core\data\auto_dataset.py" line 98, in __getitem__
return self._call_load_sample(self.data[index])
KeyError: 0

Code sample
import torchaudio

from flash.audio import SpeechRecognition

data = torchaudio.datasets.LIBRISPEECH(".\\data",url="test-clean", download=True)

model = SpeechRecognition(backbone="facebook/wav2vec2-base-960h")

# both of the following will fail
res = model.predict({"input_values": data[0][0]})
res = model.predict(data[0][0])
print(res)

Expected behavior
It was expected that the model.predict() function would accept a tensor or input dictionary since that is the "raw data" referencing how "predict" is documented to work:
https://github.com/PyTorchLightning/lightning-flash/blob/4b24b445ce9a65b21ab3fc0361d95d879f01cedf/flash/core/model.py#L466
Environment

PyTorch Version:  1.9.1
OS: Windows 11 Education (dev release)
How you installed PyTorch: conda-forge::pytorch (from enviornment.yml)
Python version: 3.7.1
CUDA/cuDNN version: CUDA version 11.4
GPU models and configuration:  NVIDIA GeForce 2060
Any other relevant information: pytorch lightnting was installed with pip after conda environment was established

Additional context
It is possible to bypass this error by:

Sanitizing the input by subclassing the SpeechRecognition task

class W2v2_model(SpeechRecognition):
 def _apply_batch_transfer_handler(self, batch: Any, device: Optional[torch.device] = None, dataloader_idx: Optional[int] = None) -> Any:
        if isinstance(batch, torch.Tensor):
            return super()._apply_batch_transfer_handler(batch={DefaultDataKeys.INPUT: batch}, device=device, dataloader_idx=dataloader_idx)[DefaultDataKeys.INPUT]
        else:
            return super()._apply_batch_transfer_handler(batch, device=device, dataloader_idx=dataloader_idx)

and 2) declaring a default datapipeline  to pass to the predict stage.
pipeline = model.build_data_pipeline("default")
model.predict({"input_values":data[0][0]},data_pipeline=pipeline)

This works, but it seems to me that this is a bug for the following reasons:

passing a data pipeline to the predict function shouldn't change the interface of the function itself
The docs suggest that either a filepath or raw data should work with predict (this may be a misreading on my part)
The way predict() works (creating a pipeline on every call) is too slow for my purposes (benchmarking), which is why I couldn't use the default behavior of creating a csv so I can load a datamodule in the first place.

I would advice you to use trainer.predict and provide a DataLoader for speed concerns

authors: marischu tchaton

repo: PyTorchLightning/lightning-flash


text:
Let IDE(s) know public symbols

🚀 Feature (or Bug?)
I'm using Pylance on VSCode, and it doesn't autocomplete, for example, Accuracy even if I typed the following:
from torchmetrics import Ac

This is because imported symbols are considered private by default (by at least pylance (pyright) as documented here).
Motivation
For better coding experience (autocomplete + docstring reference) :]
Pitch
As stated in https://github.com/microsoft/pyright/blob/main/docs/typed-libraries.md#library-interface, we have the following options to explicitly make symbols public.
1. Add __all__ to __init__.py files.
# torchmetrics/__init__.py
from torchmetrics.classification import (
    Accuracy,
    ...
)
__all__ = [
    "Accuracy",
    ...
]

2. Use wildcard imports.
# torchmetrics/__init__.py
from torchmetrics.classification import *

# torchmetrics/classification/__init__.py
__all__ = [
    "Accuracy",
]

3. Use redundant symbol aliases.
# torchmetrics/__init__.py
from torchmetrics.classification import (
    Accuracy as Accuracy,
    ...
)

Additional context
https://github.com/microsoft/pylance-release/issues/1032
https://github.com/microsoft/pyright/pull/1877

@akihironitta sounds good to me :]
I would prefer option 1 but have no strong opinions here.

authors: SkafteNicki akihironitta

repo: PyTorchLightning/metrics


text:
How do you use the hidden state from the previous training step in the next step?

I want to train an LSTM Language Model using Lightning, but I need to pass the previous step's hidden state to the next training step. The raw training loop looks something like this:
model.train()
hidden = model.init_hidden(batch_size)
for data in train_iter:
  text, target = data.text, data.target
  model.zero_grad()
  output, hidden = model(text, hidden)
  hidden = detach_tensors(hidden)  # for truncated bptt
  loss = criterion(output.view(-1, vocab_size), target.view(-1))
  loss.backward()

  optimizer.step()

How can I achieve this with Lightning? Thanks!

Would it be fair to say that this advice has been superseded by the bptt argument in Trainer?

yes! 0.9.0 makes this very clear. check out the latest master docs

Thanks for the clarity!

authors: n2cholas shivdhar williamFalcon

repo: PyTorchLightning/pytorch-lightning


text:
add boring script for development, debugging, and reproduction

What does this PR do?
An extremely minimal Lightning script. No license, docstrings, doctests, ads etc.
This is meant for

quickly sharing reproducible code and Trainer settings
quickly test and develop an idea
easy copy-paste to and from GitHub/Slack

Why not use pl_examples/bug_report_model.py?
Because bug_report_model.py is meant for users. It has plenty of instructions that are not desired for local development and sharing. It unfortunately also contains some method/class names that make PyCharm believe it is a unittest file.
We need an uncomplicated, easy to use script for internal use.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs) SLACK INTERNAL
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Why not delete pl_examples/bug_report_model.py?
The boring model notebook is meant for users.
IMO no point keeping this and that one

authors: awaelchli carmocca


text:
NFT Sale Price in Pylons Points Should Display an Approximate Price in USD

Currently, an NFT cannot be easily repriced if the seller makes a mistake.  (I accidentally priced my first NFT at 200 points ($20) when I meant to do 20 points ($2)).  This will be a recurring problem that degrades the user experience.
After discussion with Michael, the simplest solution is to have the UI display an approximate USD value next to the Pylons Points when pricing an item.
For example, pricing an item for 10 Pylons Points would have the UI say 10 Pylons Points ≈ Approximately $1 USD.

Sure i will consult with the design team and then will solve this issue.

This issue should've been resolved with the implementation of the For Sale toggle for the NFT owner's view:

we originally did not want to associate an approximate USD value since we hadn't set the conversion rate between pylon points & usd.. but if we now have that conversion rate then we will incorporate it into the buy button for NFTs denominated in pylon points and ensure that this USD equivalent is displayed in Easel as well.

For now, we can safely use 10 cents USD as the approximate value of Pylons
Points.
On Mon, Aug 22, 2022 at 10:45 AM StefanB90 @.***> wrote:

This issue should've been resolved with the implementation of the For Sale
toggle for the NFT owner's view:
[image: Screen Shot 2022-08-22 at 10 42 00 AM]
https://user-images.githubusercontent.com/97635071/185949220-f1d1fb2d-4d98-4bba-b8e2-154ec4ca3266.png
we originally did not want to associate an approximate USD value since we
hadn't set the conversion rate between pylon points & usd.. but if we now
have that conversion rate then we will incorporate it into the buy button
for NFTs denominated in pylon points and ensure that this USD equivalent is
displayed in Easel as well.
—
Reply to this email directly, view it on GitHub
https://github.com/Pylons-tech/easel_flutter/issues/113#issuecomment-1222462914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2R2JATJJQS4DTXD6BFB4S3V2OG6XANCNFSM56XAFDIA
.
You are receiving this because you authored the thread.Message ID:
@.***>


text:
How to use target="_blank" in link item

With Pandoc shell command line no problem.
With markdown python program it's impossible.
I use several tests without success.
A solution ?
Markdown syntaxe:
[Markdown Python](https://github.com/Python-Markdown/markdown/issues){:target="_blank"}
Thanks

Could you please provide us with the options you are passing to Python-Markdown (including any extensions you are using) as well as the actual output and the output you are expecting?

Good evening.
My python prog (where file is my markdown file)
                with open (file, 'r') as f:                     Html = markdown.markdown(f.read())
A simple markdown file
`
target test
Markdown Python{:target="_blank"}
The Html result....

target test
Markdown Python{:target="_blank"}  <
...`
Is it enough for checking ?
Thanks

Good evening
The python file
                with open (file, 'r') as f:                     Html = markdown.markdown(f.read())
I gave the markdown syntax previously.
Is it enough for you ?
Thanks

As a reminder, the {:target="_blank"} syntax is not part of Markdown's standard syntax. Therefore, we do not support it by default. However, with the attr_list extension we do provide support. If you enable the extension, then your input would presumably work as desired. I say "presumably" because you did not provide me with an example of the output you expect. Therefore, I can only assume the extension will match your expectations. If it doesn't then you may want to explore other third-party extensions and/or build your own extension.

Thank you for your explanation. The extension will apply target to ALL links; it's not what I want.
I will use a python instruction.
On MD link line ( if I want open the link on a new page) I will add {:target="_blank"} at the end of the address
[Markdown Python](https://github.com/Python-Markdown/markdown/issues {:target="_blank"})
and after convertinf md to html the python instruction
FinalHtml = FinalHtml.replace('{:target="_blank"}">','" target="_blank">')
Thank you

I'm confused as to what you want. Isn't this the desired behavior?
>>> import markdown
>>> src = '''
... [blank](http://example.com){:target="_blank"}
... [no blank](http://example.com/no_blank)
... '''
>>> print(markdown.markdown(src, extensions=['attr_list']))

blank
no blank

Exactly what I want.
Thanks very much from France.

authors: VanilleAngeles waylan

repo: Python-Markdown/markdown


text:
Scrape algo trading articles from quant finance websites

Description
Implemented scraper to get top algo trading and mathematical finance articles.
Fixes #(373)
Replace issue_no in the above line, with the issue related to this PR.
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

NOTE: These boxes can be checked using [X]

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

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[X] My code follows the style guidelines of this project.
[X] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[X] I have commented on my code, particularly in hard-to-understand areas.
[X] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[X] I have included a requirements.txt file (if external libraries are required.)
[X] My changes do not produce any warnings.
[X] I have added a working sample/screenshot of the script.

Hey, @shivanshsinghal107 thanks for the contribution but can you change the branch name from which you contributed cause it might cause some conflicts with the all-contributors bot, that kind of branch naming is used by the bot.

Hey, @shivanshsinghal107 thanks for the contribution but can you change the branch name from which you contributed cause it might cause some conflicts with the all-contributors bot, that kind of branch naming is used by the bot.
Everything else is good 👍🏽

Okay, so should I create another branch or just do it in the master

The script works well! 👍🏻
Changes:

Please describe what your script does in the README.
Describe the terms like quantopian and quantocracy for better understanding.

Suggestion:

Instead of printing it on the terminal, save it in a file, probably a .txt file.
If you do so, add a sample .txt file in the folder as well.

Okay

The script works well! 👍🏻
Changes:

Please describe what your script does in the README.
Describe the terms like quantopian and quantocracy for better understanding.

Suggestion:

Instead of printing it on the terminal, save it in a file, probably a .txt file.
If you do so, add a sample .txt file in the folder as well.

All changes done, you can review then at pull 384.


text:
Email validation is not Done properly and it must be Done on backend also because  HTML,js can be edited too

@engineerscodes how's going can you please share some updates ?

I would like to work on this issue under LGMSOC'21 if no one is working. Please assign this issue to me.

Created pr plz check #288

@engineerscodes how's going can you please share some updates ?

I had my exam's

authors: RituCs engineerscodes nlok5923


text:
Footer link should redirect to actual sites

Describe the bug

Currently the footer links under government of india section redirect to #

To Reproduce
Steps to reproduce the behavior:

Head over to footer
Click on any link under goverment of india section

Expected behavior

It should redirect to actual sites

Logs
this links i am talking about

Environment (please complete the following information):

OS: all
Browser: all

Sir @QAZIMAAZARSHAD I would like to do work on it


text:
覆盖安装插件不生效

app 覆盖安装后，杀死进程，切换到后台，都是加载的旧的插件，必须把app卸载重新安装才生效，不知道为什么？

您好，我们目前“覆盖安装插件”仅支持升级（也即——版本必须+1）。
我们已有App反馈这么做不太方便（虽然也能调试，只不过每次都要+1而已）。我们会在2.1.2解决这个事儿，在保证稳定的前提下，允许App覆盖安装插件。

这个已经在2.1.5及以上版本解决了。请升级到最新版本试试。

我的2.2.4  还是遇到同样的问题

内直插件版本更新，新的版本覆盖老的版本，但插件的内容还是老的内容

authors: 13621877812 Hiram-Y jiongxuan


text:
Change test_array_backends mixin classes to subclass QiskitDynamicsTestCase

Summary
Changes the classes utilized by test_array_backends to be subclasses of QiskitDynamicsTestCase. The arraylias module tests have also been updated (this is the only test folder that currently uses this).
Details and comments

A modification where Arraytest inherits QiskitDynamicsTestCase  caused a no-member error in the existing tests that inherits QiskitDynamicsTestCase since the method of QiskitDynamicsTestCase is not found in the tests.(e.g. self.assertAllClose()). At least, I believe we have to acknowledge this error.
It might be good to provide a means of Arraylais to make tests for some arrays work.

repo: Qiskit-Extensions/qiskit-dynamics


text:
Bug: typos in traveling salesman problem section

Where does the issue happen?
https://qiskit.org/textbook/ch-paper-implementations/tsp.html
What is the content issue?

[ ] The sentence below appears in the text

Lets construct the unitarie for j = 1, 2, 3, & 4:
Lets should be Let's and unitarie should be unitary

[ ] Lets is misspelled throughout the page

[ ] Further down the page, the sentences copied below need changing for consistency for singular/plural agreement

U_j are diagonal unitary matrices. It will be  ...
Proposed change could be
Each U_j is a diagonal unitary matrix and it will be...

[ ] "only the (n−1)contain length" is missing a space in between (n-1) and contain

[ ] "But, keep in mind, Finding" shouldn't have a capital in Finding

[ ] A more thorough editing of the grammar and style on this page would improve it and make it more consistent with the language in the rest of the qiskit textbook

Working on this

This repository is no longer maintained. It has been superseded by IBM Quantum Learning.

authors: micpap25 vabarbosa vandieren

repo: Qiskit/platypus