text:
Export lit-html directives through lit-element

Exports the lit-html directives through the lit-element.ts file to encourage better code quality without users having to resort to dirty imports or duplicate dependencies.
Issue with motivation

@googlebot I signed it!

@googlebot I fixed it.

Thanks for the PR, but see my response in #846

source: gharchive/pull-request

authors: gerarts justinfagnani

repo: Polymer/lit-element

license_type: permissive

license_source: bigquery


text:
Conditional tests should use the value of test when their containing suite is called.

Some tests conditionally disable groups of tests by capturing either test or test.skip from the top-level scope before the tests are run and later calling the captured function instead of test:
https://github.com/Polymer/lit-html/blob/1d0549426df5fc420285812f634970d92a027905/src/test/lib/render_test.ts#L22-L34
However, this can potentially prevent the test runner from associating them with the correct suite, which might be a problem if they are meant to be part of a suite with (e.g.) a setup function.

Yeah, it's pretty strange. I found this while trying to do https://github.com/Polymer/lit-html/pull/937, where the render tests were being run twice: the tests that were using a captured test would run outside of all suites and those that depended on setup / teardown hooks would break.

repo: Polymer/lit-html


text:
paper-dropdown-menu

Is there a way that I could use paper-dropdown-menu in a version 1.0 project?

paper-dropdown-menu is being upgraded to 1.0
You can follow paper-elements roadmap here

source: gharchive/issue

authors: SmokyBob fredpedro

repo: Polymer/polymer


text:
Can anyone look a these issues / pull requests

I'm writing here, because in the other repos no one seems to respond!
Can anyone look at:
https://github.com/Polymer/polymer-cli/pull/878
https://github.com/webcomponents/shadydom/pull/187

ths https://github.com/webcomponents/shadydom/pull/187 is closed

The webcomponents issue has been resolved. I have also pinged the tools team regarding the CLI issue. I hope we can get that PR going as well.
Given the above fact, I am closing this issue for now. Feel free to ping the CLI PR in a week or so if there is still not a response from the team.

thx

can you also ping the team about https://github.com/Polymer/polymer/issues/4859

@TimvdLippe maybe you can also trigger the CLI Team to look at these issues:
https://github.com/Polymer/polymer-cli/issues/886
https://github.com/Polymer/polymer-cli/issues/701
https://github.com/Polymer/polymer-cli/issues/633
I think they are all the same, but not yet solved...

These issues will be addressed when we get to them. Right now the modulizer
is on focus in preparation for Polymer 3.
On Thu, 16 Nov 2017, 21:46 Jochen Kühner, notifications@github.com wrote:

@TimvdLippe https://github.com/timvdlippe maybe you can also trigger
the CLI Team to look at these issues:
Polymer/polymer-cli#886
https://github.com/Polymer/polymer-cli/issues/886
Polymer/polymer-cli#701
https://github.com/Polymer/polymer-cli/issues/701
Polymer/polymer-cli#633
https://github.com/Polymer/polymer-cli/issues/633
I think they are all the same, but not yet solved...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer/issues/4931#issuecomment-345056991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDb7ytxUqsiAnGMk9NL4BjTbBr9WIMks5s3J8XgaJpZM4Qb-yC
.

maybe it‘s possible to help you? where‘s help needed?

I dont manage that repository. However, for this repository I will do
another cleanup and then mark issues which you can help out with. Stay
tuned!
On Fri, 17 Nov 2017, 19:19 Jochen Kühner, notifications@github.com wrote:

maybe it‘s possible to help you? where‘s help needed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer/issues/4931#issuecomment-345321889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDb-HBGGL_Z7X0amuqmKLjozSw2EHAks5s3c4lgaJpZM4Qb-yC
.

@jogibear9988 I believe that issue is related to how babel-preset-minify handles unicode characters. Not sure but it might be this issue.

I‘ve also added a issue at babel already https://github.com/babel/minify/issues/706 ;-)

I think 2 of the issues are fixed in babel-minify (but not yet in a release) and for the 3rd one I created a fix (https://github.com/babel/minify/pull/733). I look that they'll create a release when the 3rd fix is in, so polymer/cli could be updated!

authors: TimvdLippe jogibear9988 web-padawan


text:
Add support for polymer-css-build processing :dir()

There are three decision points to bail early from trying to apply the rather expensive :dir() selector transform.

If ShadyDOM is active, bail

ShadyDOM has a different code path for handling :dir()

If the template is built, check for :host([dir="rtl"])

If styles are built, DirMixin will still do some runtime work for the direction, but will not run the selector transform.

If styles are unbuilt, check if :dir() selector is present

The check for :dir() is much faster than the transform, even when :dir() is not present.

Ripped out the shadow :dir() build for now because it requires copying selectors to support runtime processing of :dir() for the "shadow build run in ShadyDOM" case.

Has been merged into https://github.com/Polymer/polymer/pull/5421.

authors: azakus sorvell


text:
Firefox always opens First Run page instead of tests

For me on OSX, starting with Firefox v43.0.1, whenever I run WCT, it opens up https://www.mozilla.org/en-US/firefox/43.0.1/firstrun/learnmore/ instead of the tests. Same thing happened with v43.0.2 (except the URL is of course https://www.mozilla.org/en-US/firefox/43.0.2/firstrun/learnmore/).
I've tried forcing configuration options on Firefox, but those do not take effect when WCT runs FF for some reason (I confirmed by checking about:config when running $ wct -p)
According to these StackOverflow questions below, it appears it's possible to programatically create a Firefox profile for Selenium/WebDriver to use, but I'm unsure how I can configure this with WCT or if there's a better way to handle it:

Firefox webdriver opens first run page all the time
FirefoxDriver always starting on “firstrun” page, breaking all test scripts

Any ideas?

/sub

+1

Awesome!  So the solution is to downgrade my evergreen browser.  That is fantastic!  (By the way, downgrading worked for me.  But what the heck?)

After a little bit of fiddling around I suspect that the issue is based off the fact that selenium starts Firefox with a anonymous profile. This profile has the preference "startup.homepage_welcome_url.additional" set to the https://www.mozilla.org/nl/firefox/43.0.1/firstrun/learnmore/ url. I'm still figuring out if it is possible to update this preference from selenium.

@JohnRiv sorry about the delayed response. I set this to high priority, but may be critical depending on how bad the impact is and ugly workarounds are.
Does anyone know if there's a command line flag in Firefox to suppress the learn more page? If so, we could easily add that, otherwise we have to look into creating a profile...

Maybe we could ship a profile as in: https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-profile_.22.2Fpath.2Fto.2Fprofile.22
The note about relative paths on OS X is ominous though.

@justinfagnani Could you please update the priority of this issue to critical? This problem causes wct to be unusable on the command line if FireFox is installed.

Thank you andyfinity. I was having same problem with selenium 2.53.0 and Firefox 45.0.2. Downgrading to 41.0.1 brought my tests alive again.

My Firefox was updated to Firefox 46 and it is working once again :tada:

wow, that's awesome, because I hadn't found a good solution!

authors: JohnRiv TimvdLippe ckuiawa gjdenhertog justinfagnani kbalaji83 sandro-k

repo: Polymer/web-component-tester


text:
Export releases for HTML5

The newest release should be exported in HTML5. Ideally, this would be a zip file with an index.html which is the file format sites such as itch.io expect.

HTML5 export works but the 3D falls apart.

repo: Poobslag/turbofat

license: MIT

license_source: github-api


text:
obtain estimated focal length from robust estimator pose/info

Hello!
Pretty much what the title said, how can i get the estimated focal length from a CameraPose struct when enabling https://arxiv.org/abs/2311.16304 ?
plus: is there a way to estimate focal length with a robust estimator for a single camera absolute pose with this library? Or the only viable solution atm is p4pf?
If it matters i'm on pybind
Thank you!

The CameraPose struct does not provide any information on focal lengths. If you have two images with 2d-2d correspondences and want to get focal lenghts you should

If you have two different cameras - run estimate_fundamental -> focals_from_fundamental_iterative for our method or focals_from_fundamental for the Bougnoux formula
If you have the same cameras you should use estimate_shared_focal_relative_pose

In case you have some 2d-3d correspondences then you should use the p4pf solver. You should check out the dev branch it is still in development, but you may find some code there for bundle adjustment for this problem using different cameras.

repo: PoseLib/PoseLib


text:
Valid event names trigger - Error: No spaces allowed in events list

Background
This plug expects the string format "(eventA,eventB),(eventC,eventD)" with no white spaces but there isn't a hard rule that says events name cannot have white spaces. PostHog's own sdk produce events with spaces in their names eg. Application Opened & Application Backgrounded from the reactive native sdk.
Issue
Thus the format "(Application Opened,Application Backgrounded)" should be a valid format but throws Error: No spaces allowed in events list.
This culprit is
https://github.com/PostHog/event-sequence-timer-plugin/blob/5fb1e844bddda680059130a1d24a99216c1cc682/index.js#L2

Hey @emmanuelbuah! Thanks for creating this issue and apologies on the delayed response. Totally agree that this is a game breaker for most people; I'm going to go through and open a PR to fix this that should get merged early next week 👍

authors: emmanuelbuah pjhul

repo: PostHog/event-sequence-timer-plugin


text:
filter on schema extension attribute not working

Filter takes no action, just matches everything. Applies to Enterprise User and custom schema extensions.
See test: when_retrieving_resource_types_error.cs and with_a_filter_and_schema_extension.cs

in latest pull request from me this tests are green

#38

license: mit


text:
task持久化报错

Describe the bug
执行workflow时，执行到TaskPersistenceService#save方法时，hikari尝试获取H2连接时报错：The file is locked: nio:/root/powerjob/worker/h2/xxxxxxxxxx/powerjob_worker_db.mv.db [1.4.200/7]
To Reproduce
执行workflow时偶发
Environment

PowerJob Version: [4.0.1]
Java Version: [OpenJDK 8]

Some issue

repo: PowerJob/PowerJob


text:
Add a linter warning for special quote characters

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues to ensure it has not already been reported.

Summary
Users who copy and paste code may inadvertently grab special quote characters and not normal quote characters. The linter should warn that special quotes were used to surround a string. Otherwise the code will likely error out.
Proposed Design
Add a linting rule to warn when special quote characters are used to surround a string

Thanks for the issue @notgriffin! Do you want " as the default normal quote character? Or maybe this enhancement can allow you to choose which one is correct

@notgriffin Was this something you had a problem with? The PowerShell parser does some work to help manage the different quote characters.

Hi @StevenBucher98! Yes the " U+0022 and/or ' U+0027 should be the default quote character. This was something I had a problem with where the linter did not flag this as an issue even though it was causing code issues. The linter I think should not error on any of the following unicode character values when quoting a string: U+201C, U+201D, U+201F, U+2019, U+301D, U+301E, U+301F, U+FF02, U+201A, U+2018, U+201B, U+2758, or U+275C.

The specific input is useful but me it feels like issue #1436 already covers this

Yeah I guess it covers it to come degree, although I think that issue should then be expanded to include the characters I specified above.

yes, that's what I meant by 'your specific is useful', can you comment this on the other issue please and we close this as a duplicate?

authors: StevenBucher98 bergmeister notgriffin

repo: PowerShell/PSScriptAnalyzer


text:
ExecutionContext is not recognized as a global variable

Repro
Clone https://github.com/TravisEz13/PSScriptAnalyzerExamples.git
open the repo in powershell
Invoke-ScriptAnalyzer .\executioncontext.ps1
Expected
No issues found by the script Analyzer
Actual
Rule Name                           Severity   File Name  Line  Message
---------                           --------   ---------  ----  -------
PSAvoidUninitializedVariable        Warning    executionc 1     Variable 'ExecutionContext' is not initialized. Non-global
                                               ontext.ps1       variables must be initialized. To fix a violation of this
                                                                rule, please initialize non-global variables.

Travis. The fix is available in the BugFix branch
https://github.com/PowerShell/PSScriptAnalyzer/commit/e2e34b577a43cab0b28b0cfcab649ad5921290b6
It will show up in Master in the next couple of days


text:
Test-ModuleManifest allow syntax checking only

This is largely a spin-off of closed issue 7495.
Currently the Test-ModuleManifest will fail if it is unable to find a module listed in requiredmodule. This can be problematic, as some modules can not be dynamically installed from the PSGallery (For example those installed by windows features like "ADFS"). This makes using test-modulemanifest in the scope of an automated test significantly more complicated.
a switch would be nice to be able to set this module to check syntax only in these scenarios.

It's a worthy cause, but note the linked issue is actually still open.

repo: PowerShell/PowerShell


text:
Foreach -parallel does not work when using a PS drive built with my profile

Strange error when attempting a foreach -parallel command while in a PS drive built in my profile.  The error goes away when I switch to my C drive.  Note that my S drive in in C.  Will show definition:
PS [03/24/2020 07:18:32] C:\Users\a_s_p > get-psdrive s | fl
Name            : S
Description     :
Provider        : Microsoft.PowerShell.Core\FileSystem
Root            : C:\Users\a_s_p\Documents\3n
CurrentLocation :
Steps to reproduce
PS [03/24/2020 07:12:02] S:\ > 1..5 | foreach-object -parallel {write-host $_}
Expected behavior
PS [03/24/2020 07:12:03] S:\ > c:
PS [03/24/2020 07:14:56] C:\Users\a_s_p > 1..5 | foreach-object -parallel {write-host $_}
1
2
3
4
5
Actual behavior
PS [03/24/2020 07:12:02] S:\ > 1..5 | foreach-object -parallel {write-host $_}
ForEach-Object: An unexpected error has occurred while processing ForEach-Object -Parallel input. This may mean that some of the piped input did not get processed. Error: System.Ma
nagement.Automation.DriveNotFoundException: Cannot find drive. A drive with the name 'S' does not exist.
at System.Management.Automation.SessionStateInternal.GetDrive(String name, Boolean automount)
at System.Management.Automation.SessionStateInternal.AutomountBuiltInDrive(String name)
at System.Management.Automation.SessionStateInternal.GetDrive(String name, Boolean automount)
at System.Management.Automation.SessionStateInternal.SetLocation(String path, CmdletProviderContext context, Boolean literalPath)
at System.Management.Automation.PSTasks.PSTaskBase.Start()
at System.Management.Automation.PSTasks.PSTaskPool.Add(PSTaskBase task)
at Microsoft.PowerShell.Commands.ForEachObjectCommand.b__63_2(Object _).
Environment data

PS [03/24/2020 07:15:19] C:\Users\a_s_p > $psversiontable
Name                           Value

PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

/cc @PaulHigin

Good find, @aspersram  - can you please update the title of your report to a summary of its content?

We don't currently transfer current runspace state to the foreach parallel runspaces, and instead each loop iteration runs in a default runspace (except for current drive, which we do set).  It is something we are considering as a new feature, which will likely be opt-in since it has perf implications.
For now I'll fix the error, and we can look at initializing loop runspaces from current runspace state in the future.

Done.  Please let me know if the new title is descriptive enough.
-Mobile

On Mar 24, 2020, at 09:02, Michael Klement notifications@github.com wrote:

Good find, @aspersram - can you please update the title of your report to a summary of its content?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you.  One other thing I’ve noticed;  I have a directory called:  ‘3n’  in my documents folder.  In ps7, I cannot cd into it unless I enclose the dir name in quotes.  If I type ‘cd 3n’, the ‘n’ isn’t recognized.  I’m not in a psdrive, just C.
Is this just me?
-Mobile

On Mar 24, 2020, at 09:23, Paul Higinbotham notifications@github.com wrote:

We don't currently transfer current runspace state to the foreach parallel runspaces, and instead each loop iteration runs in a default runspace (except for current drive, which we do set). It is something we are considering as a new feature, which will likely be opt-in since it has perf implications.
For now I'll fix the error, and we can look at initializing loop runspaces from current runspace state in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

That's a known issue: https://github.com/PowerShell/PowerShell/issues/11626
I have a PR open which fixes that issue, which is pending review: https://github.com/PowerShell/PowerShell/pull/11634

Understood, thanks for the heads up.
-Mobile

On Apr 28, 2020, at 16:25, vexx32 notifications@github.com wrote:

That's a known issue: #11626
I have a PR open which fixes that issue, which is pending review: #11634
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


text:
ScriptBlock.InvokeWithContext mutates variable lists passed as arguments

If passed a variable that is (for lack of established term afaik) intrinsic to the scope, the variable entry will be removed from the list passed in variablesToDefine.  This includes vars such as $this, $input, $_ and $PSItem.

Steps to reproduce
$list = [System.Collections.Generic.List[psvariable]]@(
    [psvariable]::new('_', $null),
    [psvariable]::new('something-not-scope-intrinsic', $null))

{}.InvokeWithContext($null, $list, @())
$list

Expected behavior
Name                           Value
----                           -----
_
something-not-scope-intrinsic

Actual behavior
Name                           Value
----                           -----
something-not-scope-intrinsic

Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0-preview.2
PSEdition                      Core
GitCommitId                    7.1.0-preview.2
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

@SeeminglyScience  Correct and by design. Intrinsic variables already have a set of rules for when and how they are bound. This API was not intended to change those rules. What it does is allow you to provide ambient context to the script block when it executes. This is used by DSC internally to define the set of resources (functions) available inside a configuration (function). For example, if you want to make a function available to a scriptblock without setting it in the current scope and thus making it visible to everything you do, you can use this API. It's particularly useful in modules where you can't use dynamic scoping to provision an execution environment. Does that make sense?

@SeeminglyScience  Correct and by design. Intrinsic variables already have a set of rules for when and how they are bound. This API was not intended to change those rules. What it does is allow you to provide ambient context to the script block when it executes. This is used by DSC internally to define the set of resources (functions) available inside a configuration (function). For example, if you want to make a function available to a scriptblock without setting it in the current scope and thus making it visible to everything you do, you can use this API. It's particularly useful in modules where you can't use dynamic scoping to provision an execution environment. Does that make sense?

@bpayette It works, you can set intrinsic variables with this API.  The API iterates the List<PSVariable> looking for intrinsic variables and removes them to be handled separately (through InvokeWithPipe parameters).
This issue is just about the List<> argument getting mutated because of internal logic.  I would have expected a copy of the list to have been made if changes were needed before it passed the list to InvokeWithPipe.

authors: SeeminglyScience bpayette


text:
PowerShell.exe launches profiles WindowsPowerShell based user profile directory

Steps to reproduce
Have a $profile on your system (installing chocolatey via start-psbootstrap is sufficient), download alpha.8 pkg, run powershell.exe
Expected behavior
no error, note that executionpolicy is a different issue
Actual behavior
. : File C:\Users\slee\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be loaded because running
scripts is disabled on this system. For more information, see about_Execution_Policies at
http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3

. 'C:\Users\slee\Documents\WindowsPowerShell\Microsoft.PowerShell_pro ...

+ CategoryInfo          : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess

Environment data

> $PSVersionTable

This is taken care off by #1769. Closing this issue

authors: KrishnaV-MSFT charub


text:
Pasting into powershell is incredibly slow

Steps to reproduce

SSH into a linux machine (I'm running ubuntu 16)
Install powershell
Start powershell (pwsh)
Unload PsReadline (remove-module psreadline)

Copy 10-50 lines of powershell from the host into the session. Witness that each line takes several seconds to paste, and a full script locks the console for several minutes while the paste is "typing"
Expected behavior
It should be fast
Actual behavior
It is incredibly slow
Environment data
Name                           Value
----                           -----
PSVersion                      6.1.1
PSEdition                      Core
GitCommitId                    6.1.1
OS                             Linux 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

This looks way better on a machine running 6.2.0, so closing this. Will re-open if I see it again.


text:
'Get-Command ?' returns % (ForEach-Object alias) and other unrelated CommandInfo objects

This issue is relevant to the new PSSA bug https://github.com/PowerShell/PSScriptAnalyzer/issues/1209 and relates to probably any version of PowerShell
Steps to reproduce
> Get-Command -Name '?'

Expected behavior
> Get-Command -Name '?'

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           ? -> Where-Object

Actual behavior
> Get-Command -Name '?'

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           d -> dotnet.exe
Alias           g -> git.exe
Alias           h -> Get-History
Alias           r -> Invoke-History

Environment data

Windows 10 1809
Any version of PowerShell (6.2, 5.1, etc.)

I'm assuming that's because ? is being interpreted as the single-character wildcard when searching for commands.

This problem is very mild, but it can't solve the cancer i think.
get-alias，get-command support    ？ and *  as wildcard。
the alias of where-object:
1 use w ? same linux command.
2 use wh?
3 use `?    <-----  who vote this?

This seems related to some other things that @mklement0 has brought up in other wildcard-escaping issues. You actually have to escape the wildcard twice to get it to register what you're looking for:
PS C:\Users\Joel> gcm ?

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           h -> Get-History
Alias           r -> Invoke-History

PS C:\Users\Joel> gcm `?

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           h -> Get-History
Alias           r -> Invoke-History

PS C:\Users\Joel> gcm ``?

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           ? -> Where-Object

FYI
PS C:\> gcm "?"

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           h -> Get-History
Alias           r -> Invoke-History

PS C:\> gcm "`?"

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           h -> Get-History
Alias           r -> Invoke-History

PS C:\> gcm "``?"

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           ? -> Where-Object

PS C:\> gcm '?'

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           % -> ForEach-Object
Alias           ? -> Where-Object
Alias           h -> Get-History
Alias           r -> Invoke-History

PS C:\> gcm '`?'

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Alias           ? -> Where-Object

PS C:\> gcm '``?'
# No output

Thanks for the input. You guys are right about it being the single character wildcard, I did not think of this. Unfortunately, as a consumer of Get-Command I do not want to write my own logic depending on what comes in as a user input. Maybe a -LiteralName would be better (and faster) for such cases. I can understand that PowerShell was designed to be as helpful as possible and tries to not have complicated cmdlet parameters but every once in a while this can create annoying issues of PowerShell trying to be too clever.
From an architectural perspective, would it be helpful to have a LiteralString type that derives from System.String and means to PowerShell cmdlets that the string should be interpreted literally as-is?

That would be really nice.

Shall we close this issue after maintainers have seen this and possible create a new issue for the proposal of the LiteralString type

Let me shed some more light on the current situation:

It's clear that we have a problem with treating wildcards consistently, as the sheer number of open issues related to them attests (title search only): https://github.com/PowerShell/PowerShell/issues?utf8=✓&q=is%3Aissue+is%3Aopen+in%3Atitle+wildcard

Also, it's not obvious:

what parameters support wildcards:

#4715 asks for the syntax diagrams to reflect wildcard support.
#4716 asks for reliable programmatic discoverability of parameters with wildcard support
#2490 asks for auto-generated help / syntax diagrams to reflect wildcard support (and default values).

how to use escaping in their arguments.

Currently, all wildcard-supporting parameters are [string]-typed.
The [SupportsWildcards()] attribute is purely informative - no behavior is enforced, no support is provided. Commands can implement wildcard support without indicating that fact via this attribute, which is problematic.
Because wildcard-supporting parameters are [string]-typed, the only way to opt out of interpretation of a value as a pattern (i.e., to opt into treatment as a literal),  is to use escaping embedded in the string value, using embedded ` as the escape character.
Therefore, for escaping to be effective, the ` must reach the target command, i.e., must be embedded in the string.
The conceptually clearest expression of that is the use of single-quoting:
Get-Command '`?' # use of '...' ensure that ` is passed through

What makes this confusing is that PowerShell's expandable-string `-escaping can get in the way:
(In argument mode) `? and "`?" are both treated as expandable strings, and ` is the escape char. in expandable string that has syntactic function and therefore gets removed during parsing, and Get-Command see just ?. In other words: passing `? or "`?" is no different than passing just ?
To put it yet another way: lone ` instances in expandable strings are "eaten" during string parsing, and do not become part of the string.
By contrast, `` does effectively escape an ` in an expandable string, which then becomes part of the string, which is why the following work too:
Get-Command ``?   # string parsing eats 1 ` and Get-Command sees literal `?
Get-Command "``?"  # ditto

As for ensuring the literal treatment of arguments provided via expressions or variables, you must use [WildcardPattern]::Escape()
$name = '?'
Get-Command ([WildcardPattern]::Escape($name)) # OK - the method call yields literal `?

I think that 99% of the time, Get-Command is used with wildcards to search and resolve a command.  I'm not against adding a new parameter or switch for programmatic use.
A side topic, in general, it would be nice if we have some custom types derived off [string] so we have more context of the intended use.  For example, [wildcardedString] or [filesystemPath] so we can have more intelligent tab completion and self documentation.  In the latter case, if we ensure all appropriate parameters have the [SupportsWildCards()] attribute, we could do something with PSReadLine to show that the parameter supports wild cards (for example).

@SteveL-MSFT: indeed, with Get-Command the confusion between a literal and a wildcard pattern is an edge case, and the ability to use wildcards without jumping through syntax hoops is generally a benefit.
With file paths, however, it is a recurring pain point, and it has led to the deplorable -Path / -LiteralPath schism.
The problem hasn't come up often in other contexts - such as with Get-Command here - but it's a generic problem.
Implementing a -<name> / Literal<name> parameter pair everywhere wildcards are supported is not practical.
What is needed is a concise, obvious way to opt out of treating an argument as a wildcard for a single parameter that can accept either a wildcard or a literal, namely for both:

literal use (currently required: embedded `-escaping, e.g.,   '`?')
variable/expression-based used (currently required: ([WildcardPattern]::Escape($name)))

Let me suggest the following way forward, which would only require changes to the parameter binder; however, it would be a breaking change:
In POSIX-like shells such as Bash, it is explicit quoting that disambiguates wildcard patterns from string literals (leaving aside that wildcard handling is fundamentally different there and that unquoted use implies others so-called shell expansions).
Applied to PowerShell:
# WISHFUL THINKING

# Literal syntax
Get-Command ?   # wildcard
Get-Command '?'  # literal
Get-Command "?"  # literal

# Variable/expression-based syntax
$name = '?'
Get-Command $name    # wildcard
Get-Command "$name"  # literal

# Pipeline use
Write-Output ? | Get-Command  # literal - pipeline input is always literal
Write-Output ? | % { Get-Command $_ } # wildcard - if really needed

The parameter binder could then act as follows:

On binding arguments:

If the target parameter has the SupportsWildcards attribute:

If the argument is unquoted, pass it / its evaluated value through as-is.
If the argument is quoted, apply [WildcardPattern]::Escape() to it / its evaluated value and bind that.

Otherwise, no distinction is made between quoted and unquoted use.

On binding from the pipeline:

As implied by the examples above, pipeline inputs would always be treated as literals.

From an implementing cmdlet / function's perspective, all that is needed is to consistently decorate wildcard-supporting parameters with the SupportsWildcards attribute, and the parameter binder would do the rest: literal inputs would arrive automatically escaped.
A potential new hybrid parameter type such as [wildcardedstring] could also tie into this: instead of escaping a literal value, the parameter binder could simply construct the [wildcardedstring] in a way that indicates that the string is a literal, which would make performant implementations simpler: the implementer will easily know whether the argument is a literal, and can skip matching operations (you can currently do the same thing manually with [WildcardPattern]::ContainsWildcardCharacters())
Additionally, parsing of compound tokens as arguments would have to change to allow direct concatenation of quoted and unquoted tokens:
# WISHFUL THINKING

# Quote only the literal parts of a path - those parts that need it.
# The wildcard char. must be unquoted in order to be recognized as such.
Get-ChildItem "/foo/name with spaces"/*

Currently, such a compound token results in two arguments - which, honestly, never made much sense - see #6467):
# CURRENT BEHAVIOR

# Quoted string first:
# !! 2 arguments
PS> Write-Output "foo bar"baz
foo bar
baz

# Unquoted string first:
# !! 1 argument
PS> Write-Output baz"foo bar"
bazfoo bar

As for what would break:

The big issue: wildcard-based paths with explicit quoting would no longer work; e.g., Get-ChildItem "*.txt"
Unlikely to be a problem: Code that relied on compound strings such as "foo"bar getting broken into multiple arguments.

As for what we would gain:

The continued convenience of being able to use wildcards without special syntax - e.g., Get-Command *-Csv, Get-ChildItem *.txt

A simple, consistent opt-out-of-wildcard-matching mechanism - if needed - to ensure literal use.

I agree that some syntactical difference between wildcarded and literal strings is a good idea. I don't think that just forbidding all wildcard patterns in enclosed strings is the answer, however... Rather, I think that this is an opportunity to make a meaningful distinction between the two string parsing modes.
Single-quoted strings are already widely understood to be literal strings, in that they don't expand variables and subexpressions, etc.
Why not simply expand that already-understood behaviour and make single-quoted strings the de facto standard for non-wildcard parameter input?
In other words, in your brief example:
PS> Get-Command ? # wildcard
PS> Get-Command "?" # wildcard
PS> Get-Command '?' # literal

@vexx32

Also, your suggestion @mklement0 would result in being fundamentally unable to pass wildcard patterns via variable

To quote from my proposal above:
# Variable/expression-based syntax
$name = '?'
Get-Command $name    # wildcard

That is, the suggestion was to interpret the values of variables or expressions _that aren't enclosed in "..." as wildcards and, conversely, only treat them as literals when "..."-enclosed.
Conversely, your single-quotes-as-literals-only proposal prevents use of variables / expressions as literals,  which I think is very silly. 😄

Re new sigils / enclosing delimiters such as //...//:
I intentionally tried to avoid introducing those, because PowerShell already has a problem with additional sigils such as @ and { at the start of unquoted arguments having special meaning compared to other shells.
Any additional exceptions to literal parsing are problematic (not just from a backward-compatibility perspective), as you'll always have to be on guard as to whether your unquoted argument will be taken as a literal or as an expression.
Also note that we want to retain wildcard interpretation as the default, which means that the new syntax would have to express opt-in to string-literal interpretation.
Building on your suggestion to leverage the well-established semantics of '...' to mean literal, perhaps the following could work:
$name = "?"
Get-Command ''$name

That is, '' preceding a variable name or expression would signal the intent to use its value literally.
(Currently, this results in two arguments: the empty string, followed by the value of $name - again, it's unlikely that existing code relies on this behavior.)

Conversely, your single-quotes-as-literals-only proposal prevents use of variables / expressions as literals, which I think is very silly. 😄

You can have the parser assign a different type to the string, or an attribute to the variable that stores it, which flags it explicitly as a literal string. 😄

@vexx32: Assign a different type based on what? What signals the distinction between wanting to use $var's value in Get-Command $var as a wildcard vs. a literal?

$literal = 'literal'
$nonliteral = "nonliteral"

If, instead, you did as you mention:
Get-Command $literal # literal
Get-Command "$literal" # converted to non-literal
Get-Command $nonliteral # nonliteral
Get-Command "$nonliteral" # nonliteral

How about making hashtable and string implicitly convertible to WildcardPattern?
Then you could set it up so the parameter binder can handle these:
Get-Command ImplicitlySupportsWildcard*
Get-Command @{ Value = 'Does not support wildcards'; IsLiteral = $true }

# Or with extras in the parser
Get-Command "No wildcards"/@

So then cmdlets could type the parameter as WildcardPattern and handle both literals and wildcards with pattern.IsMatch(string). WildcardPattern already creates a delegate to use for matching, so you could have it create one like (input) => pattern.Equals(input, StringComparison.OrdinalIgnoreCase) for literals.
Maybe also add properties Pattern and IsLiteral to WildcardPattern so the cmdlet author can use them directly if needed.

@vexx32:
What you're proposing is highly obscure and I strongly recommend against it.
Once a string has been created, its content is by definition a literal, and we don't want to create implicit string subtypes that carry information that is entirely unrelated to strings per se.
Instead, we're looking for a syntax form that in the context of wildcard matching only conveys the distinction between something meant to be a pattern and something to be used as-is - because wildcard patterns currently happen to be implemented as strings.
In other words: we're trying to convey information that is unrelated to strings per se, and only matters if strings happen to be used as - potential - wildcard patterns.
Piggybacking on string-quoting semantics is only an option in the context of argument parsing, where use of unquoted strings is permitted and can thus serve as a distinction, but it's important to understand that string-literal parsing and interpretation of a string's content as a wildcard expression are unrelated things.
My own proposal is guilty of blurring these lines too, but only in said constrained scenario - nowhere else, notably not in expression mode.
In short, what we want to express is: "Whatever this string expands to (or not), treat its resulting content either as pattern or use it as-is."

@SeeminglyScience:
Great idea to adapt the existing [WildcardPattern] type and to give it an IsLiteral property (for consistency with -eq, the string-comparison mode should be InvariantCultureIgnoreCase, though)   - doing so obviates the need for a potential [wildcardedstring] type.
As for the literal argument syntax:

@{ Value = 'Does not support wildcards'; IsLiteral = $true } works unambiguously and introduces no new syntax, but it is obviously very verbose.

"No wildcards"/@ strikes me as obscure and would be the first case of a postpositional sigil.

However, conceivably we could take a page out of C#'s book:
# All literal uses
Get-Command @'?'
Get-Command @"?"
$name = '?'; Get-Command @$name
$name = '?'; Get-Command @$($name)

# Note that the following would NOT work:
Get-Command @?  #  reserved for splatting.
Get-Command @($name) #  array subexpression operator

The problem is that @ already has multiple unrelated or only loosely related meanings (splatting, here-strings, array-subexpression operator).
While a separate sigil - @  - potentially makes it clearer that a dimension that is independent of string quoting is being expressed, the fact that the same sigil is used for here-strings again muddies the waters.
As for backward compatibility:

@' and @" are currently interpreted as the start here-strings, whose content must start on the next line, so there'd be no problem there.

@$name is currently the same as "@$name", however, so it's conceivable that existing code relies on that.

At the end of the day I like @vexx32's suggestion in the abstract: to piggyback on '...' semantics, but perhaps only with a special argument-parsing-mode only '' prefix to  a string, irrespective of the latter's own quoting style:
# Pattern - irrespective of string-quoting style
Get-Command name
Get-Command 'name'
Get-Command "name"
Get-Command $name
Get-Command $('name' + '?')

# Literal - only with '' prefix
Get-Command ''name
Get-Command '''name'
Get-Command ''"name"
Get-Command ''$name
Get-Command ''$($name + '?')

@mklement0

"No wildcards"/@ strikes me as obscure and would be the first case of a postpositional sigil.

Oh, to be honest I misread part of one of your comments.  I hastily included that as an example because I thought you proposed it.  I don't actually have any thoughts on what the syntax should be or even whether or not there should be one at all.  That's what I get for skimming 🙂

@SeeminglyScience:

even whether or not there should be one at all.

Indeed we don't need a syntax for that; even with the current behavior, you can always disambiguate with:
Get-Command '`?'  # string-literal: embedded escaping of metachars.
$name = '?'; Get-Command ([WildcardPattern]::Escape($name)) # escape programmatically

Based on what prompted creation of this issue and that the subsequent discussion it's clear that these options are obscure in the former case, and cumbersome in the latter.
In the case of -Path / -LiteralPath, you can sidestep the issue by choosing -LiteralPath for literal input paths, forgoing the convenience of positional argument binding.
In the majority of cases you don't have that option.
Perhaps the need to force literal interpretation rarely arises (I've tripped over Get-Command ? myself, for instance), but when it does, it's currently far from obvious how to handle it, because:

about_Wildcards doesn't talk discuss escaping at all.

Similarly, the [WildcardPattern] class isn't part of the end-user documentation.

As stated, discovering which parameters support wildcards is quite cumbersome at the moment (see #4715, #4716, and #2490).

At the least, these issues should be addressed - even if nothing else changes.
Additionally, I think that a concise syntax that works with both literals and variables/expressions for on-demand treat-as-literal semantics is a worthwhile addition for convenience.

A quick meta note, @vexx32:

which I think is very silly. 😄

Regrettably, I echoed that phrase of yours in my response, but what I should have said is this:
Sticking a 😄 at the end of an insult doesn't nullify it.
(Again, it would be the first instance of a postpositional sigil.)
Perhaps you meant to be playful, but we don't have a personal relationship, and intent is hard to read in its absence and with written communication in general.
I value your helpful contributions to this community and the constructive discussions you and I generally have; please don't sour that with flippant responses such as the above.
To be clear: if there is a problem with a proposal or argument, I absolutely want to hear about it - just not packaged that way (leaving aside the fact that this particular objection was unfounded).

Understood. I'll make an effort to be more clear. 🙂

# Or with extras in the parser. Picture some better form of syntax here instead.
Get-Command "No wildcards"/@

Interesting idea.  I have really disliked the whole Path vs LiteralPath schism from day one.  And what, looks like we'd need a -LiteralCommand to solve this the "PowerShell" way.
I'd love to see the need for a LiteralPath parameter go away in PS 7.  But you'd need a way to indicate to a command that wildcard chars should not be interpreted as wildcards for a parameter.  Perhaps the above suggestion (or one like it) is the way to go but it would need to be able to handle expressions in general:
Get-Command $name/@
Get-ChildItem (Join-Path $PSScriptRoot "foo[bar]")/@  # < Hmm that syntax is problematic I think

I'd venture a guess that there are a ton of latent bugs in PowerShell scripts out in the wild because folks write script like this Test-Path $path not ever thinking that the user might supply a path with [] in it.
So I'm not sure how you solve this exactly but yeah, it would be so nice to be able to write a command for PS7 that doesn't require a LiteralPath parameter.  That would also reduce parameterset complexity by eliminating one parameterset completely.

Agreed on all points, @rkeithhill, except the details of the new syntax (see bottom).

folks write script like this Test-Path $path not ever thinking that the user might supply a path with [] in it.

Yes, it's unfortunate that -Path is the default, but, conversely, if -LiteralPath were, the convenience of Test-path *.txt would go away, because, at least with positional use you would then have to explicitly signal the desire to treat the argument as a pattern.
At least we now have alias -lp to make use of -LiteralPath less verbose.
But I agree that ditching the -Path / -LiteralPath schism and promoting a dedicated treat-this-potential-pattern-as-a-literal syntax is the way forward, not least because it can then be applied to any (existing) wildcard-supporting parameter - such as Get-Command's -Name in the case at hand, without burdening implementers and end users with separate parameter sets.

On to bikeshedding:
As stated, I think that introducing a postpositional sigil is problematic - it differs from all other sigils, and you have to visually scan to the end of the token to discern intent.
Using '' as a prefix is not the prettiest but:

it's unlikely to break existing usage
conveys the notion of literalness better
works equally with string literals (wether with literal or expandable content) and variables / expressions:

Get-Command ''$name
Get-Command ''$(Join-Path $PSScriptRoot "foo[bar]"

P.S.:
I suggest combining the new syntax with @SeeminglyScience's proposed enhancement to the [WildcardPattern] class.
Future cmdlets can then ditch the current combo of [string]-typed parameters with informational-only [SupportsWildcards()] attribute for a [WildcardPattern]-typed parameter that is both self-documenting and provides useful functionality.
The parameter binder would then have to do extra work in both cases when encountering the new syntax:

When binding to [string]-typed parameters with [SupportsWildcards()], bind the result of [WildcardPattern]::Escape()

When binding to [WildcardPattern] parameters, construct an instance appropriately.

A small implementation recommendation:
It's likely that existing cmdlets would be reworked to accept WildcardPattern instead, if this is the case then compatibility with existing scripts could still be kept by implementing LiteralPath parameters like this
public string LiteralPath
{
    get => Path != null && Path.IsLiteral ? Path.Pattern : null; // or string.Empty
    set => Path = new WildcardPattern(value, isLiteral: true);
}

I generally support @mklement0 proposal, but against that using '' as prefix.
Because '' is widely recognized by users as expression of literal strings, the following expressions look very weird to me and may cause confusion.
# Literal - only with '' prefix
Get-Command ''name
Get-Command '''name'
Get-Command ''"name"

If anything, it might be better to use the @ as a prefix.
The @ is also used in C# as a prefix for escape, and I think that we will be familiar with it.
# Literal - only with @ prefix
Get-Command @'?'
Get-Command @"?"

However, it may be a problem in the following situations. It will need to be discussed.
$names = '?', 'gci', '*Firewall*'
Get-Command $names  # All elements as non-literal

# How to express $names as literal?
Get-Command @($names)           # array subexpression
Get-Command @$names             # best way?
$names | % { Get-Command @$_}   # not bad but a bit verbose
$names | % { Get-Command ([WildcardPattern]::Escape($_))}   # current solution

To help with the discussion, let me clear up some potential terminology confusion:
Literal can mean two things:

Literal notation: "Honey, I'm $HOME." and 'Ceci n'est pas une pipe' are both string literals.

Literal content: Only the content of 'Ceci n'est pas une pipe' - a single-quoted string literal - is taken literally, or, to take a page out of C#'s terminology book, only a single-quoted string literal's content is used verbatim.

Therefore, what we're looking for here is a new, concise, bareword-friendly (not requiring quoting) notation for verbatim patterns - i.e., something that when passed to a wildcard-supporting parameter is interpreted not as a pattern, but verbatim.

I think you would need to enhance WildcardPattern dramatically such that:

WildcardPattern would need to store the "OriginalString" somewhere (like URLs do) so it can implement ToString() usefully so that functions or cmdlets using [WildCardPattern] as a parameter can still use it as a string internally when necessary.
This means WildcardPattern would need to store whether it was literal so you could tell the difference between escaped and literal text -- which probably means the WildcardOptions enum needs a IsLiteral value so you can construct a real WildcardPattern
WildcardPattern would need to support casting hashtables (looks for Value and Literal or IsLiteral)
5, WildcardPattern would need to cast non-string objects with respect for a Literal or IsLiteral property...

Good suggestions, @Jaykul; such enhancements could help prevent bugs such as #9475.
Returning to the idea of a syntax for verbatim (escaped) patterns (which the parameter binder could translate into (enhanced) [WildcardPattern] instances for parameters declared with that type):
As an aside: The unquoted (glob) / quoted (verbatim) distinction already is implemented, namely when calling external programs on Unix, to emulate POSIX-like shell behavior; e.g., /bin/echo *.txt results in expansion to all matching filenames, whereas /bin/echo '*.txt' prints *.txt verbatim.
Given that @ already serves many different purposes, we can stick with it as follows and embrace the logic of conceiving of verbatim strings as escaped patterns:

@`...  to create escaped wildcard expressions
@\...  to create escaped regexes (obviates the need for [regex]::Escape() calls.

Note the prettiest, but concise, and I think it suggest the  intent.
Examples:
# Wishful thinking

# With a bareword (wouldn't be supported in expression mode)
Get-Command @`?
Get-Item @`file[1].txt

# With a variable
$file = 'file[1].txt'; Get-Item @`$file

# With a (sub)-expression
$ndx = 1; Get-Item @`('file[{0}].txt' -f $ndx)

# With -replace, in expression mode
'a * is born' -replace @\'*', 'star'
$replace = '*'; 'a * is born' -replace @\$replace, 'star'

This should be easy enough to implement with the code I added for the execution path.  Where we prefer literal matches before wildcard matches.


text:
Change comment and element text to meet MS standards

PR Summary
Change words in code to match MS standards

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

[ ] 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).

What you want me to do bro
On Mon, Dec 9, 2019, 5:00 PM Aditya Patwardhan notifications@github.com
wrote:

@adityapatwardhan approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PowerShell/pull/11304?email_source=notifications&email_token=AN6RWNNAMPZII6A7CMFL4WLQX3EY3A5CNFSM4JYSIEWKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCOREPLY#pullrequestreview-329402287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN6RWNKY6YFGLRUA3IWW2NDQX3EY3ANCNFSM4JYSIEWA
.

authors: JamesWTruher troymoore


text:
Update metadata.json and README.md

PR Summary
Update the metadata json and README for upcoming releases.
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:

LGTM

authors: SeeminglyScience adityapatwardhan


text:
*-PSResource does not throw error on non-existent module

I typo'd the module and found that none of the following cmdlets write an error if it tries to perform an action on a non-existent module. For example, Find-PSResource PSKoanssd. V2 throws an error as expected.

Find-PSResource
Install-PSResource
Save-PSResource
Update-PSresource

This is fixed with the release of 3.0.11-beta.  I’ll add the specific PR where this was fixed as well

authors: ThomasNieto alerickson

repo: PowerShell/PowerShellGet


text:
No way to get content under CommonParameters from MamlCommand

Steps to reproduce
cmdlet markdown:
# Workflow
## SYNOPSIS
## SYNTAX
```
Workflow [<WorkflowCommonParameters>] [<CommonParameters>]
```
## DESCRIPTION
## EXAMPLES
## PARAMETERS
### WorkflowCommonParameters
This cmdlet supports the following workflow common parameters: -PSParameterCollection, -PSComputerName, -PSCredential, -PSConnectionRetryCount, -PSConnectionRetryIntervalSec, -PSRunningTimeoutSec, -PSElapsedTimeoutSec, -PSPersist, -PSAuthentication, -PSAuthenticationLevel, -PSApplicationName, -PSPort, -PSUseSSL, -PSConfigurationName, -PSConnectionURI, -PSAllowRedirection, -PSSessionOption, -PSCertificateThumbprint, -PSPrivateMetadata, -AsJob, -JobName, and -InputObject. For more information, see [about_WorkflowCommonParameters](http://go.microsoft.com/fwlink/p/?LinkID=533952).
### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

var mamlCommand = NodeModelToMamlModelV2(doc).First();

Expected behavior
There's a property that we could get content under CommonParameters
Actual behavior
There's no way to get content under CommonParameters  section, but only a boolean value of  SupportCommonParameters
Environment data

Latest commit in master branch => 457b2905f57253a1bef0eefe4c10ebc8cfd0e2ed

This is intentional, https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_commonparameters?view=powershell-6
The text is standard for the common parameters and should not very. What's the scenario where you want to use it?

Add @sdwheeler to answer the question.

I want OPS to render the markdown as written. PlatyPS creates the markdown with the CommonParameters information. I don't see this as a PlatyPS issue. OPS is not rendering it.

@sdwheeler OPS is using MamlCommand model from PlatyPS, instead of the corresponding source markdown directly.

@qinezh Then OPS is doing the wrong thing.

@sdwheeler No matter the information comes from PlatyPS or OPS, the question still exists:

The text is standard for the common parameters and should not very. What's the scenario where you want to use it?

@qinezh My issue is that the information in the markdown file is not rendered by OPS. So OPS is the problem. That information is important to display to end users and it is missing. We have gotten bug reports from customers about the missing information.

Looks like it's another concern, closed this issue.

authors: qinezh sdwheeler vors

repo: PowerShell/platyPS


text:
xClusterPreferredOwner: The resource is moving cluster group in Set-TargetResource

When setting preferred owner on a cluster group or a cluster resource it moves the cluster group to the first node. In a production environment this could be a bad thing.
See line 98-99
        Write-Verbose -Message "Moving Cluster Group $ClusterGroup to node $($Nodes[0])"
        $null = (Get-ClusterGroup -cluster $ClusterName) | Where-Object {$_.name -like $ClusterGroup} | Move-ClusterGroup -Node $Nodes[0]

Why is it moving the cluster group? And if this is a must, then I think this should be handled differently.

Is it meant to move to the preferred owner, if that owner is not the preferred? But that should not be up to the resource, would it?

I don't think you want a resource to fight with what the cluster service is doing. Just have it configure the setting and leave it alone would be best IMO.

I agree.

authors: bgelens johlju

repo: PowerShell/xFailOverCluster


text:
Update to use template files

Pull Request (PR) description

Update appveyor.yml to use the default template.
Added default template files .codecov.yml, .gitattributes, and .gitignore, and
.vscode folder.

This Pull Request (PR) fixes the following issues

Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

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

@@          Coverage Diff          @@
##             dev     #14   +/-   ##
=====================================
  Coverage       ?   1.28%
=====================================
  Files          ?      10
  Lines          ?     701
  Branches       ?       0
=====================================
  Hits           ?       9
  Misses         ?     692
  Partials       ?       0

Continue to review full report at Codecov.

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

authors: codecov-io johlju

repo: PowerShell/xSCOM


text:
REST API doesn't start; generating stager fails with REST API call

The REST API won’t start due to a bug:
./empire --rest --username "emp" --password "emp"
[*] Loading modules from: /mnt/hgfs/cjones/Empire/lib/modules/

Starting Empire RESTful API on port: 1337
RESTful API token: 2bjmeuwa6pr6yy4x0n88rauyyl1nve7cekdgkefh
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/init.py", line 853, in emit
msg = self.format(record)
File "/usr/lib/python2.7/logging/init.py", line 726, in format
return fmt.format(record)
File "/usr/lib/python2.7/logging/init.py", line 465, in format
record.message = record.getMessage()
File "/usr/lib/python2.7/logging/init.py", line 329, in getMessage
msg = msg % self.args
TypeError: %d format: a number is required, not str
Logged from file _internal.py, line 87

After casting the port from a string to an int, the REST service works.
Also, when calling the API to create a stager, the .dll is not actually
written to disk.

I can't recreate this bug on master or dev. Additionally, for stager generation, we don't want the output to be written to disk for the server, but rather returned in a transport-safe (base64) format caller to keep the responsibility for file ingestion/processing with the REST client. Also, for future pull requests, please submit to the development branch instead of master.
I'm going to close this PR, but if you would like to resubmit to dev with just the "port=int(port)" fix we'll land it.

Thank you for the feedback and the work on this.  I'll use dev from now on.

repo: PowerShellEmpire/Empire


text:
Нет возможности сохранить результаты тестирования (с описаниями ошибок)

Укажите:

Версия Vanessa Automation 1.2.038.1
Версия платформы 8.3.19.1522
Режим совместимости базы, где запускается Vanessa Automation Версия 8.3.17
Операционная система Windows Serwer 2016 Standard

После выполнения тестирования не нашел возможности сохранить таблицу "Дерево тестов" с результатами тестирования (текстами ошибок).
Для себя решил эту проблему следующим образом:

Добавил в выводимые поля поле "Текст ошибки":

Домавил в меню "ГруппаVanessaEditorИнструменты" кнопку со стандартной командой "ВывестиСписок":

Можно что-нибудь более изящное написать, но мне для счастья и этого хватает с головой

@sdemon72
Для сохранения результатов тестирования есть много вариантов отчетности: Allure, jUnit и другие.

repo: Pr-Mex/vanessa-automation


text:
Браузер: заставка с надписью и визуальным эффектом

Пример сценария:
И я показываю заставку "Пример заставки веб-клиента, эффект №5" в браузере
	| 'color'           | 'green' |
	| 'effect'          | '5'     |
	| 'count'           | '10'    |
	| 'backgroundColor' | 'gold'  |
	| 'fontSize'        | '200%'  |
	| 'timeout'         | '3000'  |

Вошло в релиз 1.2.033


text:
Chapter 3 predictions classifying 'dog' all the time.

I'm trying to figure out why the call to validation_generator.class_indicies is always showing a 1 next to dog. Regardless of whether I use a cat or dog.  Prediction is also showing 2 float values rather than one.  During training, my loss and accuracy are both looking good across the board (approx 97/98%), but when I proceed to test I get results similar to those shown below :
[[9.9989903e-01 1.0094591e-04]]
{'cat': 0, 'dog': 1}
I am using Tensorflow-gpu 2.2 under Ubuntu 18.04 Cuda 10.1.  I originally was following with the code in the book, but then verified with your code on git and all seems to look ok to me.  Does anything jump out at you as to what I am doing wrong?
I have attached a screenshot showing the test result.

The validation_generator.class_indices prints out the index of each class in the dataset, so it's always going to show cat as 0 and dog as 1, irrespective of the input image.
If we look at the values printed out by prediction we see that cat has a higher probability (10-1) vs dog at 10-5 which is in line with the input image of cat.jpg

Thank you sidgan!  I've been trying to figure this out for the past couple days lol.  Thought that the 1 represented which it was inferring, but I did notice the probabilities seemed correct.  Thank you and sorry for wasting your time.

No worries! Cell 11 and 12 may be relevant to print out accuracy and class indexes for the correct predictions: chapter-3/2-analyzing-the-results.ipynb


text:
Amber/adding exported models controller to conversations typespec

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

Hi Pranshu, this is the PR to bundle my changes to yours. Could you approve this? Thank you!

Hey Amber - going to close this one - lets make your branch based off mine, then target that branch for merge instead of targetting main

authors: PranshuBansalDev amber-ccc

repo: PranshuBansalDev/azure-rest-api-specs


text:
Allow custom awsvpcConfiguration for ECS Worker

Closes #298
As per the above issue, there are cases where it is necessary to supply specific ECS Worker task configuration. This is an initial attempt to address that. As referenced in the documentation and test updates, a dict that supplies the settings available in the AWS documentation
Example

Difficult to provide a code example here because these settings will likely be taken from the Work Pool configuration.
ECSJobConfiguration.from_template_and_values(
    base_job_template=ECSWorker.get_default_base_job_template(),
    values={
    "aws_credentials:" aws_credentials,
    "vpc_id:" "vpc-sometest123",
    "override_network_configuration:" True,
    "network_configuration:" {
            "subnets": ["sn-sometest123"],
            "assignPublicIp": "DISABLED",
            "securityGroups": ["sg-sometest123"],
        }
    }
)

Screenshots

Checklist

[x] References any related issue by including "Closes #" or "Closes ".

If no issue exists and your change is not a small fix, please create an issue first.

[x] Includes tests or only affects documentation.
[x] Passes pre-commit checks.

Run pre-commit install && pre-commit run --all locally for formatting and linting.

[x] Includes screenshots of documentation updates.

Run mkdocs serve view documentation locally.

[x] Summarizes PR's changes in CHANGELOG.md

Thank you @HughZurname!

authors: HughZurname Jrodseth

repo: PrefectHQ/prefect-aws


text:
Support Application default credentials

For the GCP library it looks like https://prefecthq.github.io/prefect-gcp/credentials/#prefect_gcp.credentials.GcpCredentials we always need to have the credential file. However when running on Google Services you can normally used an attached   Application Default Credential and don't have to pass the credential along which is the recommended way for this in production.  My reading of the docs indicate it only supports the https://googleapis.dev/python/google-auth/1.15.0/user-guide.html#service-account-private-key-files method currently.
It should be easy to support via the SDK.  We normally do it via https://googleapis.dev/python/google-auth/1.15.0/user-guide.html#application-default-credentials.
import google.auth

credentials, project = google.auth.default()

vs
from google.oauth2 import service_account

credentials = service_account.Credentials.from_service_account_file(
    '/path/to/key.json')

scoped_credentials = credentials.with_scopes(
    ['https://www.googleapis.com/auth/cloud-platform'])

Prefect 1.x supported ADC as well (https://github.com/PrefectHQ/prefect/blob/1.x/src/prefect/agent/vertex/agent.py#L73)

We should support this per https://github.com/PrefectHQ/prefect-gcp/blob/main/prefect_gcp/credentials.py#L184 — perhaps we can just clarify the documentation by explicitly mentioning ADC? The blurb with "from the env" and the gcloud command is not particularly clear.

Thanks @madkinsz, the code support looks good. I think the Docs should point to this page about authentication, and then make it clear that it will attempt to use ADC if no credential is provided.

authors: damienrj madkinsz

repo: PrefectHQ/prefect-gcp


text:
BugFix: TypeError: crypto.randomUUID is not a function causes page to break

Description
The storage service used crypto.randomUUID to generate random ids for checkouts. But that isn't safe to use because its only available in secure contexts. Using the randomId utility from prefect-design make sure this works no matter what.
Closes https://github.com/PrefectHQ/prefect-ui-library/issues/1497

Hi there, I'm using 2.10.17 prefect but still have the TypeError: crypto.randomUUID is not a function issue. Is this fix really included in the 2.10.17 version? I saw it from the release note

Actually opening prefect in an insecure context (non-localhost via plain http) still doesn't work in release 2.10.17 which has this fix. Is prefect UI supposed to work in an insecure context? This used to work in prefect<-2.10.13.

@tumluliu and @phill84 you are correct. There was a downstream (but still prefect) occurrence that I had missed. We were able to reproduce and found https://github.com/PrefectHQ/prefect-design/pull/829 which should take care of this. Thanks for reporting and helping debug. We'll get this fix out with the next release on thursday

repo: PrefectHQ/prefect-ui-library


text:
Sort by ID instead of alphabetically

Hi,
I have a problem showing the results of a function in the ps_facetedsearch module
Receives sorted functions by alphabetical name, or it is possible to sort by ID

This change is

Sorry @zafon18 , this PR does not include any contribution from your account. A merge from dev to master should be done manually.
I'm closing it as it can't be accepted as-is.
If you have an issue, please create one in the main repository https://github.com/PrestaShop/PrestaShop/issues/new/choose
Kind regards


text:
Fix wording

Questions
Answers

Description?
Fix wording

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?

Wording ✅

authors: l-delin lartist

repo: PrestaShop/statsbestsuppliers


text:
[BUG] Component Select : value not selected when click on element by search bar

Context
In the component Select with search bar, when we click on a result / element in the list, it's not selected.
Reproduce link
Ask to @luctst
Steps to Reproduce
Ask to @luctst
Expected Behavior
When we select a result, it should be mark as selected
Current Behavior
When we click on a result / element in the list, it's not selected.
Additional comments
Ask to @luctst for more information.

Just in order to give more details:

authors: Nakahiru cnavarro-prestashop

repo: PrestaShopCorp/puik


text:
Support for non-i.i.d. data regime in OpenDiLoCo experiments

Hello again!
The DiLoCo paper by Arthur Douillard et al. explores the non-i.i.d. data regime in comparison to data parallelism. Could you kindly confirm if OpenDiLoCo supports this setup? If it does, could you please provide guidance on how to configure such an experiment? If not, would you recommend an efficient way to organize it in a similar manner to the approach described in the paper?
Thank you!

So it seems in the original paper they did non-i.i.d by doing k-mean clustering on last layer features from a model. Not sure if they disclose what this model is but I imagine it doesnt matter too much and if i were to guess they probably used bert.

You can then have the different workers load different datasets. Each one loading a different cluster split from the k-means

repo: PrimeIntellect-ai/OpenDiloco


text:
[1.12] Tank block containing lava gives off no light.

Version:
1.12.2-0.10.23
A tank (block) full of lava should give off light.  There should be a setting such as setLightLevel that can be called on the block class to set the amount of light it is giving off.  I would assume you could have a check for whether the contents are lava, and if so, set it to whatever.  I've seen many other tanks from other mods do this as well, which is the main reason it stood out to me that this one didn't.

Here is a screenshot of the Mekanism tank with lava on top of the Cyclic tank with lava:

Thats a good idea, great feature to add.

Luckily mek is open source so I could see the line i was missing
https://github.com/aidancbrady/Mekanism/blob/049c78088850eb5bb8415c652923d171b97013d9/src/main/java/mekanism/client/render/tileentity/RenderFluidTank.java#L103
This is what it looks like now.  Not exactly like Mek but much brighter now, its not almost black anymore.

Update again: Even brighter now even with more darkness

Fix version Cyclic-1.12.2-1.10.0

authors: JaSpr PrinceOfAmber

repo: PrinceOfAmber/Cyclic


text:
Pagination design for interaction with members list rolodex

there's no pagination in the old design, so we'll need to come up with something.

The idea I had for this is to just make the rolodex work like a filter, i.e.

when you initially come to the page, you see a list of all the people, and the pagination just pages through them in pages of whatever size we want (say, 50)
if you click one of the letters in the rolodex, you only see people whose last names start with that letter. the pagination pages through those people (there probably won't be more than one or two pages for each letter, in this scenario).
if you click other filters, those get applied on top of the rolodex filter, narrowing down the current list of people even further.
if for some reason we wanted to, it wouldn't be that difficult in this scenario to allow having multiple active rolodex filters that would use OR ("names starting with D or F").

we would need to have a little bit of logic to translate the rolodex's letter into what solr would expect for that filter ("text field must start with this letter"), but I feel like that's probably doable?

I think pagination design is complete now

authors: rlskoeser thatbudakguy

repo: Princeton-CDH/mep-django


text:
Add default module entrypoint

-> Allows invocation with python -m blocklint after installation, following standard conventions for linting tools.
-> If possible, package should be redeployed to PyPI after merging this PR

Looks innocuous enough.  Can you add a test to make sure it's running as intended?  I think something like this in tests/acceptance_test.sh should suffice:
echo "  module entrypoint"
diff <(python -m blocklint tests/sample_files/test.{cc,py,txt}) \
    tests/sample_files/default.txt

I assume argument parsing is identical, but maybe do the same for another test or two.

Looks innocuous enough.  Can you add a test to make sure it's running as intended?  I think something like this in tests/acceptance_test.sh should suffice:
echo "  module entrypoint"
diff <(python -m blocklint tests/sample_files/test.{cc,py,txt}) \
    tests/sample_files/default.txt

I assume argument parsing is identical, but maybe do the same for another test or two.

Also, I need to fix the pre-commit-hooks.yaml (PR soon).  When these 3 PRs are merged I will make a new release to pypi.

Also, I need to fix the pre-commit-hooks.yaml (PR soon).  When these 3 PRs are merged I will make a new release to pypi.

authors: jaedoucette troycomi

repo: PrincetonUniversity/blocklint


text:
global.Prism causes conflict between PrismJs versions

Hi
My vscode extension is using PrismJs ^1.13.0, while another extension is using PrismJs ^1.6.0.
Unfortunately they cannot run together, due to the global.Prism hack

I fixed it by loading prism inside the class rather then globally, will close this issue since its an edge case

Hi. We are aware of this issue. Unfortunately, this won't likely be fixed before the next major release of Prism, since this would be quite BC breaking. Refer to https://github.com/PrismJS/prism/issues/470 for a temporary "wrapper" solution that might fit your need.

authors: CoenraadS Golmote

repo: PrismJS/prism


text:
TypeError: movements.countScaffoldingItems is not a function

Version of mineflayer-pathfinder: latest
code:
const mineflayer = require('mineflayer');
const owner = process.argv[3] || "FedexxedeF"
const pass = process.argv[4];
const pvp = require('./mineflayer-pvp').plugin
const armor_manager = require("./mineflayer-armor-manager")

var isAttackingMobs = "false"

const pathfinder = require('mineflayer-pathfinder').pathfinder
const Movements = class Movements {
    constructor (bot, mcData) {
      this.bot = bot
      this.canDig = false
      this.digCost = 10
    }}
const { GoalNear, GoalBlock, GoalXZ, GoalY, GoalInvert, GoalFollow } = require('mineflayer-pathfinder').goals

const options = {
    host: process.argv[2],
    port: 25565,
    username: "Xbot",
    password: process.argv[4],
}

const bot = mineflayer.createBot(options)

bot.once('spawn', () => {

    bot.loadPlugin(pathfinder)
    bot.loadPlugin(pvp)

    // Once we've spawn, it is safe to access mcData because we know the version
    const mcData = require('minecraft-data')(bot.version)

    const movements = new Movements(bot, mcData)
    movements.canDig = false
    bot.pathfinder.setMovements(movements)

    bot.settings.viewDistance = "tiny"
    bot.chat('/login ' + pass)
    bot.chat('Xbot by Fede!')
    console.log("Connected")

 // We create different movement generators for different type of activity
    const defaultMove = new Movements(bot, mcData)

    //every 1 second go forward
    /*
    setInterval(function(){
        bot.setControlState("back", false)
        bot.setControlState("forward", true)
    },1000)
    setInterval(function(){
        bot.setControlState("forward", false)
        bot.setControlState("back", true)
    },1100)
    */
});

setInterval(() =>{
    if (isAttackingMobs === "false") return
    const mobFilter = e => e.type === "mob"
    const mob = bot.nearestEntity(mobFilter)

    if (!mob) return

    if (mob && mob.kind.toString().toLowerCase().includes('hostile')) {
        bot.pvp.attack(mob)
        }
},1000);

bot.on( "kicked", (reason, loggedIn) => {
    console.log("KICKED! "+ reason)
})
bot.on("chat", function(username, message) {

    const target = bot.players[username] ? bot.players[username].entity : null

    var pmessage = message.split(' ')

    if (message.split('_')[0] != "") { return }

    if (username === bot.username) return
    if (username != owner) {
        console.log("Player " + username + " had not enough permissions to execute command!")
        bot.whisper(username, "You got not enough permissions to execute this command!")
        return
    }

    if (message === "_come") {
        bot.chat('/teleport ' + bot.username + " " + username );
        bot.whisper(username, 'Teleported to ' + username);
        console.log("Teleported to " + username + "'s position");
    };
    if (message === "_follow") {
        if (!target) {
            bot.chat('I don\'t see you !')
            return
          }
        bot.whisper(username, 'Following you!');
        console.log("Following " + username );
        bot.pathfinder.setGoal(new GoalFollow(target, 3), true)
        console.log(bot.players[username].entity.position)
        isAttackingMobs = "false"
    };
    if (pmessage[0] === "_attack") {
        if (pmessage[1] === "hostiles") {
            isAttackingMobs = "true"
            console.log("Attacking Hostiles!")
            bot.chat("Attacking hostiles!")
        }
        else {
            const player = bot.players[pmessage[1]]
            if (!player) {
                bot.chat("I can't see "+ player)
                return
            }
            if (pmessage[1]) {
                bot.pvp.attack(player.entity)
              }
        }

    };
    /*
    if (message === '_fight') {
        const player = bot.players[username]

        if (!player) {
          bot.chat("I can't see you.")
          return
        }

        bot.chat('Prepare to fight!')
        bot.pvp.attack(player.entity)

    }*/
});

error:
TypeError: movements.countScaffoldingItems is not a function     at Object.bot.pathfinder.getPathTo (C:\Users\Toshiba\node_modules\mineflayer-pathfinder\index.js:56:97)     at EventEmitter.monitorMovement (C:\Users\Toshiba\node_modules\mineflayer-pathfinder\index.js:259:42)     at EventEmitter.emit (events.js:327:22)     at Timeout.doPhysics [as _onTimeout] (C:\Users\Toshiba\node_modules\mineflayer\lib\plugins\physics.js:63:13)     at listOnTimeout (internal/timers.js:554:17)     at processTimers (internal/timers.js:497:7)

The problem is here:
const Movements = class Movements {
    constructor (bot, mcData) {
      this.bot = bot
      this.canDig = false
      this.digCost = 10
    }}

That's not how you inherit from a class. This is how: https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/Inheritance#Inheritance_with_class_syntax

The problem is here:
const Movements = class Movements {
    constructor (bot, mcData) {
      this.bot = bot
      this.canDig = false
      this.digCost = 10
    }}

That's not how you inherit from a class. This is how: https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Objects/Inheritance#Inheritance_with_class_syntax

authors: Karang XfedeX

repo: PrismarineJS/mineflayer-pathfinder


text:
Add main components to readme

pviewer
mineflayer

done

repo: PrismarineJS/prismarine-web-client


text:
[DUNGEON] Kistennamen aus TaskContent herausziehen

Der angezeigte Name im HUD (wenn das Inventar geöffnet wird) einer Kiste soll aus dem TaskContentComponent der Kiste gezogen werden. Damit lässt sich dann im HUD darstellen, welchen Index/Wert die Kiste hat.
z.B "Säugetiere" und dann muss der Spieler alle Säugetiere-Items in die Kiste legeb

@malt-r ich glaub das muss im TaskBuilder passieren, oder?

ist done. Wurde nur nicht abgehackt.

repo: Programmiermethoden/Dungeon


text:
True North Position

How can I get the real true north position?
I disable the automatic check of true north and I have created a compass that when its calibrated it start the session. The user , before start the session, should point the true north but how can I determine where is the true north and how can I Pass the calibration to AR?

@Michele404 - if this is fixed by https://github.com/ProjectDent/ARKit-CoreLocation/pull/125, could you please close this issue?

Not fixxed

@Michele404 - this is likely due to the following:

A lack of location accuracy - typically the accuracy is bad when location services start up and get more accurate as a better signal is picked up and your position is triangulated
True north error that's described in the readme and a hardware (or at least OS-level) limitation

repo: ProjectDent/ARKit-CoreLocation


text:
gosop treats passwords as direct parameters (strings) rather than indirect (file references)

The spec refers to both SESSIONKEY and PASSWORD data types as indirect data types, not direct data types, meaning that they're read by reference (by default, as filenames), rather than being placed directly on the command line.
However, I notice that gosop for sop accepts and expects passwords directly on the command line.  For example:
printf abc123 > password.txt
echo test | gosop encrypt --password password.txt

will use the literal string password.txt as the password instead of abc123.
gosop doesn't yet implement session-key input afaict, but when it does, it should also treat that as indirect, to avoid leakage of sensitive data on the command line.
See discussion at https://gitlab.com/dkg/openpgp-stateless-cli/-/issues/45 about how this was never extremely clear in the spec, sorry about that!
The gosop documentation makes it clear that it expects the passphrase as a string on the command line.  An implementation that does this would leak this secret to the process table, which is not great on most multiuser systems:
https://github.com/ProtonMail/gosop/blob/046feea9867a570681c0ebb99ebeb23467ea6aba/README.md?plain=1#L28

Hey :wave: Thanks for the report! Should be fixed in 739d8bbc1abb0f98a21787b1028afb5452254150. I fixed a few other things as well, including expanding and fixing support for session key input and output. (There's still a lot of other things to be done, though..)

authors: dkg twiss

repo: ProtonMail/gosop


text:
Tests for signal module

New API signal module tests.

The Signal module now has substantial unit tests and coverage so I am going to delete this issue.

repo: PsrSigSim/PsrSigSim


text:
Added Py3.8 to Travis CI, and changed astropy version

Adding tests for Python 3.8. Additionally I've updated the astropy versions to match what is allowable by pint-pulsar.

Looks like this astropy update/version requirement in PINT hasn't been updated for version 0.7...

Yeah @bshapiroalbert , I'm going to backoff the astropy changes just to see if Python 3.8 works and go from there.


text:
Add documentation on releasing new data

Overview
There was no documentation on releasing new data. This PR adds documentation on both the data quality assurance and release processes and on configuring PG Admin for use with the project.
Checklist

[x] Description of PR is in an appropriate section of CHANGELOG.md and grouped with similar changes, if possible

Thanks for your feedback! I've made the changes you suggested so this should be ready for re-review.

repo: PublicMapping/districtbuilder


text:
[SMN] Option to replace Emerald Ruin III with Ruin III

Since in some content (most notably Eureka/BA) your GCD is quite a bit lower (2.12s in my case), using Emerald Ruin III ends up being a damage loss over just using Ruin III it would be nice to have an option to just not use ER3.
After level 72 this would not be relevant as it is then replaced by the higher potency Emerald Rite.
[originally submitted as XIVSlothCombo #1857]

I'm not really too fussed about adding sub-max level optimizations for niche content.
You're more than welcome to just use Ruin III manually as that is excluded from ability replacements.

authors: GayPotatoEmma Genesis-Nova

repo: PunishXIV/WrathCombo


text:
[Feature Request] Copy instead of linking to the item

Would it be possible to create a "copy" of the spell within the magic item instead of linking it to the item in the items tab?
So currently, if you import a spell into an item from the items tab, and then the original is deleted (the one in the items tab, not the one on the magic item within the character sheet), then the item in the character sheet stops working, which is a problem.

No, it'd require rewrite of the whole module

authors: GhostwheelX PwQt


text:
Recursion: Fibonacci Numbers

Before jumping into Pr first comment for assign.
Problem statement : The nth Fibonacci number
Probelm Link : https://edabit.com/challenge/BfWjk87JLY5roKzg6
Choose one Cateorgy - Easy
question category : math, recursion

Before submitting a PR please Check some details.

[x] fileName formet should be in camelcase
example- returnTheNextNumber.py
[x]  Choose label for Problem , example- "good first issue", "easy"
[x]  In file there should be problem statement and link to problem

/* Problem-Task : This program will recursively calculate the nth given number in Fibonacci's sequence
 * Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Hello, I'm a newbie c++ programmer, please assign this to me

pls assign this to me.

I can code it in Java, C++ and Python

Do assign. I can do it in any language. Easy category.

please can you assign this to me I can do it any language

please assign me i will do in c language

Please assign me this.

Assign me any problem in CPP or Java I am ready to work on it.

Could you please assign me for this task ?

Please assign this to me.

@BananaMoshpit  can i work on this issue!!

@Zaidtech it's not me who owns the rep, I think you'd be assigned after submitting a pull request linked to an issue that you (may) open.
But there's already a fibonacci function added so there's no use adding another

repo: Py-Droid/Edabit-Solutions


text:
Add bitstream filters

Loosely based on #565
Additional discussion in #489
This adds bindings for AVBSFContext (BitStreamFilterContext)
I decided against adding binding for AVBitStreamFilter, because it seems like a little bit useless API. You can't do anything with such object besides creating a new BSF context. (except checking which codecs are supported for that BSF, I guess)
It makes the code simpler and imo easier to maintain. Let me know if this is a mistake and those bindings should be added as well.
I think it makes sense to force BitstreamFilterContext creation through the string parsing API, since that's the only way I can see how to set filter options and also allows things like filter chains, etc.
Adds tests for 'chomp', 'setts' and 'h264_mp4toannexb' filters. We could also test that filter chains work.
h264_mp4toannexb requires that AVCodecParameters *par_in is set correctly. To that end BitStreamFilterContext takes a Stream as an argument and copies the codec parameters from there.
There are also attributes time_base_in, time_base_out which are probably required for 100% support of setts option constraints. Let me know if those should be hooked up as well. I guess it would require that BitStreamFilterContext takes separate in_stream, out_stream arguments instead of single stream.

Excuse me about the linter stuff. I can't run make lint locally because the flake8 always fails. I think it should work now. Both black and isort are happy

I think the PR is good as it is now.
One thing I changed was inlining def self._recv and def self._send to cpdef filter. This eliminates the overhead in calling Python functions and IMO makes it easier to read. I also add type hints and docstrings.
I'll give you a chance to comment, then it can be merged.

Looks good to me. Thanks!

authors: WyattBlue skeskinen

repo: PyAV-Org/PyAV


text:
add plotting

maybe using plotext?

what should be plotted?
describe and assign.

Good point, we could start with the reporting you see in the Readme, specifically the first "Repo changes (inserts and deletes) per week" one. Does that help?
I am also open to adding more metrics to make this more interesting, any ideas? If so let's open one or more new issues for that.
I wrote this beginner article on plotext the other day btw: https://pybit.es/articles/terminal-plotting-with-plotext/

authors: bbelderbos ishan-nahid

repo: PyBites-Open-Source/git-stats


text:
Remove MFXModule in favor of existing classes

https://discuss.pylabrobot.org/t/mfx-carrier/37 proposal 2
built on top of #280

@biocam could you please provide the pedestal_size_z for MFX_DWP_rackbased_module?

repo: PyLabRobot/pylabrobot


text:
I do not understand the usage of this parameter in oxford.yaml...

train_fea_dir: "/data/features/best_features/paris"  # path of the features for training SVD.
I find this in oxford.yaml, and it is strange that when I run main/index.py, the shell post a error:
[LoadFeature]: loading feature from /mnt/ceph/home/richardzuo/wx_yszm/ft_local/PyRetri-master/features/oxford/query/part_0.json... [LoadFeature] Success, total 55 images,   feature names: dict_keys(['pool5_GAP']) [LoadFeature]: loading feature from /mnt/ceph/home/richardzuo/wx_yszm/ft_local/PyRetri-master/features/oxford/gallery/part_1.json... [LoadFeature]: loading feature from /mnt/ceph/home/richardzuo/wx_yszm/ft_local/PyRetri-master/features/oxford/gallery/part_0.json... [LoadFeature] Success, total 5063 images,   feature names: dict_keys(['pool5_GAP']) Traceback (most recent call last):   File "main/index.py", line 48, in <module>     main()   File "main/index.py", line 36, in main     index_helper = build_index_helper(cfg.index)   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/index/builder.py", line 89, in build_index_helper     dim_processors = build_processors(cfg["feature_names"], cfg.dim_processors)   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/index/builder.py", line 60, in build_processors     processors.append(simple_build(name, cfg, DIMPROCESSORS, feature_names=feature_names))   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/utils/builder.py", line 50, in simple_build     return module(hps=hps, **kwargs)   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/index/dim_processor/dim_processors_impl/svd.py", line 42, in __init__     self._train(self._hyper_params["train_fea_dir"])   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/index/dim_processor/dim_processors_impl/svd.py", line 51, in _train     train_fea, _, _ = feature_loader.load(fea_dir, self.feature_names)   File "/data1/anaconda3/envs/PyRetri/lib/python3.7/site-packages/pyretri-0.1.0+unknown-py3.7.egg/pyretri/index/utils/feature_loader.py", line 67, in load     assert os.path.exists(fea_dir), "non-exist feature path: {}".format(fea_dir)
can you explain it ? thanks~

Besides, I do not find  any dataset named paris in README~

Besides, I do not find any dataset named paris in README~

Look issue three,it will help you

authors: NeekHua hitsz-zuoqi

repo: PyRetri/PyRetri


text:
Add current formation and opponent formation info to event, start with parser for Opta

I want to add current formation and current opponent formation information to events. This would allow us to more easily filter out events of a team or player when they were playing in a certain formation or against a certain formation. E.g. only analyse events where Lionel Messi was playing as a LW in a 4-4-2 against a 4-3-3.

@koenvo @JanVanHaaren sorry to bother, but I'm failing to understand why I'm getting this error:
TypeError: GenericEvent.init() missing 2 required positional arguments: 'formation' and 'opponent_formation'
Why is the error message saying 'formation' and 'opponent_formation' are required, while I label them as Optional in my class?
formation: Optional[FormationType]
opponent_formation: Optional[FormationType]

Thanks for the issue Dries!
In this case the state builder would be a good fit. Have you seen https://kloppy.pysport.org/examples/state/#Add-state---lineup ? Would this work for your case?

I forgot about the state builder. Yes, indeed, the state builder solves my use case.
However, Wyscout doesn't have a formation change event, it rather encapsulates the formation and opponent formation in each event, see: https://github.com/PySport/kloppy/blob/master/kloppy/tests/files/wyscout_events_v3.json#L57-L127. How would you suggest that we pass the current (opponent) formation information to the events for this data provider?
Would you save the formation information of the prior event in the Wyscout deserializer and check for a difference, and if so create an "artificial" formation change event?

The "artificial" formation change event sounds like a great solution.

authors: DriesDeprest koenvo

repo: PySport/kloppy


text:
PyThaiNLP 1.7.4

Fixed #176
removed conllu from requirements.txt  #175

Coverage decreased (-0.03%) to 53.024% when pulling 44afd2a4c4a708a4164e9220c397cec3c17e8c93 on 1.7 into 8035bf261162df2a8d4ce027638eb3fc49da1a05 on master.

Coverage decreased (-0.03%) to 53.024% when pulling 44afd2a4c4a708a4164e9220c397cec3c17e8c93 on 1.7 into 8035bf261162df2a8d4ce027638eb3fc49da1a05 on master.

Coverage decreased (-0.03%) to 53.024% when pulling 44afd2a4c4a708a4164e9220c397cec3c17e8c93 on 1.7 into 8035bf261162df2a8d4ce027638eb3fc49da1a05 on master.

authors: coveralls wannaphongcom

repo: PyThaiNLP/pythainlp