feat(world): allow registration of function selectors in the World, split out RegisterSystem from World

This PR adds two new methods to IWorld (registerFunctionSelector, registerRootFunctionSelector) and refactors the World contract to move all registration methods to an internal RegistrationSystem, for which we then register root function selectors in the World.
The two new methods in detail:
1.:
function registerFunctionSelector(
    bytes16 namespace,
    bytes16 file,
    string memory systemFunctionName,
    string memory systemFunctionArguments
  ) external returns (bytes4 worldFunctionSelector);

This function allows the registration of a world function selector for a system function at the given namespace/file/function. The resulting world function selector is world.<namespace>_<file>_<systemFunctionName><systemFunctionArguments>. (Note - systemFunctionParameters needs to include parentheses).
Registering such a function selector only requires ownership of the namespace.
2.:
function registerRootFunctionSelector(
    bytes16 namespace,
    bytes16 file,
    bytes4 worldFunctionSelector,
    bytes4 systemFunctionSelector
  ) external returns (bytes4);

This function allows the registration of a custom worldFunctionSelector for the given namespace/file/systemFunctionSelector.
Registering such a function selector requires ownership of the ROOT_NAMESPACE (automatically granted to the deployer of the World).
Note: both functions allow the registration of an empty system function selector, in which case the call is routed to the system's fallback function.
Moving the internal registration methods into its own ResourceSystem, which is then registered in the World (including root function selectors) has multiple advantages:

It slims down the World contract's bytecode and prevents us from going over the contract size limit. Just like all Systems, the RegistrationSystem is stateless (writes on the state of it's caller) and can therefore be deployed once and then just linked to the World during the deploy process (this is not set up yet, currently we deploy a new RegistrationSystem every time)
It allows registration functions to be called from the upcoming callFrom entry point (not implemented yet, see #393 for details)

It slightly increases the gas cost of all calls to registration methods, but this is fine because they are only called once during deployment, so the runtime cost stays the same.

Is there an example of what the difference is between registerRootFunctionSelector and registerFunctionSelector? I am not following the distinction if you use e.g. ROOT_NAMESPACE.

Is there an example of what the difference is between registerRootFunctionSelector and registerFunctionSelector? I am not following the distinction if you use e.g. ROOT_NAMESPACE.

The difference is in registerRootFunctionSelector you can pass any function selector you want to register in the World (eg registerTable). The function selector will not be prefixed by anything. In registerFunctionSelector you can't freely decide the selector to register but instead if will consist of namepace, file, and function selector of the underlying system.

As a small note, it would have been nice to review this as two separate PRs (e.g. RegisterSystem in its own PR) to keep scope limited (both in terms of code and having to potentially revert later, and also for easier reviewing)

Good point!


nix: Remove hash for rust-toolchain.toml

Including the hash of the rust-toolchain.toml file in the Nix shell configuration leads to additional maintenance effort and does not provide significant benefits as the toolchain file is tracked by version control.

No significant changes.

Insignifcant changes

metric
value

change

binary-size-nk3am
1,439,761
:white_circle:
+0 (+0.00%)

binary-size-nk3am-test
2,047,853
:white_circle:
+0 (+0.00%)

binary-size-nk3xn
516,308
:white_circle:
+0 (+0.00%)

binary-size-nk3xn-test
590,504
:white_circle:
+0 (+0.00%)

binary-size-nkpk
746,395
:white_circle:
+0 (+0.00%)


How to disable playback on click?

Hello!
I made a poster-plugin extension that shows the countdown before the broadcast starts.
But the player starts playback on the click, which is undesirable during the countdown
Please advise how to temporarily disable this behavior

you can override the built-in poster plugin with yours without this functionality, as mentioned in this just merged new docs: https://github.com/clappr/clappr/blob/master/doc/TROUBLESHOOTING.md#how-can-i-disable-or-override-a-plugin

Thanks!
I've already successfully overrided built-in poster. But playback on click is implemented somewere else AFAIK.

ah, you can try to player.getPlugin('click_to_pause').disable(); then

It only affects on Pause during playback ))

There isn't any special code. Just like that player.getPlugin('click_to_pause').disable();
test player
When the player is already playing this prevents of pause/play, but it does not block the very first click.

I was inattentive, sorry.
I only needed to override the clicked() method of poster.


PHP Notice :     Undefined index: request_header

On Mailchimp:220
$this->last_request['headers'] = $response['headers']['request_header'];

I'm going to need more information if you want me to help.

Same here. Class doesn't work anymore.. :(

Provide me with some information so I can help.

We do nothing more than the regular get(list) but get the above Warning and no response:
$MailChimp = new MailChimp('APIKEY-us12');
$result = $MailChimp->get('lists');
print_r($result);

same as TimE90.

Which version of PHP are you using? Which version of curl?

I just had the same error on my Windows Env - PHP 5.5.
I juste use echo $mailChimp->getLastError(); and found it was because of SSL Verification.
You can disable if you're on dev and windows by :
$MailChimp = new MailChimp('APIKEY-us12');
if (strtoupper(substr(PHP_OS, 0, 3)) === 'WIN') {
    $MailChimp->verify_ssl = false;
}

@drewm - Would you like to add this feature in the construct of your Class ? Do you want me to create a pull request ?

@Sudei Thank you so much. I think @drewm should include this on the constructor

I think about it and I have concluded the following :
This error is due to a misconfiguration of our environment (Windows in this case).
I think the best approach shouldn't be to alter the current Class to avoid this kind of bug.
We just should inform dev. about that know issue.
Maybe @drewem should add a #know issues section on the readme and add this case as a warning and give a solution to avoid it.
What do you think about it ?

Please see the Troubleshooting section in the readme, which covers this.
https://github.com/drewm/mailchimp-api#troubleshooting


Fix a race condition in Derived Field parsing from search request

Description
flaky test was introduced because of a race condition in derived fields when defined within search request.
Since derived fields are created per QueryShardContext and QueryShardContext instance can be created multiple times for a search request, there is a race condition hitting here. Since we are reusing the parsing logic of mapper for derived fields defined in search requests too, it tries to modify the map passed to it where it tries to remove all keys it has parsed.
  1> Caused by: java.util.ConcurrentModificationException
  1>    at java.base/java.util.HashMap$HashIterator.remove(HashMap.java:1619)
  1>    at org.opensearch.index.mapper.ParametrizedFieldMapper$Builder.parse(ParametrizedFieldMapper.java:732)
  1>    at org.opensearch.index.mapper.ParametrizedFieldMapper$TypeParser.parse(ParametrizedFieldMapper.java:769)
  1>    at org.opensearch.index.mapper.ParametrizedFieldMapper$TypeParser.parse(ParametrizedFieldMapper.java:754)
  1>    at org.opensearch.index.mapper.ObjectMapper$TypeParser.parseDerived(ObjectMapper.java:384)
  1>    at org.opensearch.index.mapper.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:298)
  1>    at org.opensearch.index.mapper.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:184)
  1>    at org.opensearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:143)
  1>    at org.opensearch.index.mapper.DefaultDerivedFieldResolver.getAllDerivedFieldTypeFromObject(DefaultDerivedFieldResolver.java:194)
  1>    at org.opensearch.index.mapper.DefaultDerivedFieldResolver.initDerivedFieldTypes(DefaultDerivedFieldResolver.java:181)
  1>    at org.opensearch.index.mapper.DefaultDerivedFieldResolver.<init>(DefaultDerivedFieldResolver.java:64)
  1>    at org.opensearch.index.mapper.DefaultDerivedFieldResolver.<init>(DefaultDerivedFieldResolver.java:45)
  1>    at org.opensearch.index.mapper.DerivedFieldResolverFactory.createResolver(DerivedFieldResolverFactory.java:49)
  1>    at org.opensearch.search.SearchService.createSearchContext(SearchService.java:1121)
  1>    at

Related Issues
Resolves https://github.com/opensearch-project/OpenSearch/issues/14444

Check List

[x] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hey @rishabhmaurya based on the past issue here https://github.com/opensearch-project/opensearch-build/issues/2292, force push will not work to trigger the gradle check with commit as github is not able to give the .pull_request.head.sha for the job
Error
+ set +x
Git clone: https://github.com/rishabhmaurya/OpenSearch.git with ref: e80ddbab5f324b449a2363f64493f02a16acbc4f
Cloning into 'search'...
fatal: reference is not a tree: e80ddbab5f324b449a2363f64493f02a16acbc4f

Adding @getsaurabh02


⚠ Bofrost.com has degraded performance

In a1f84f8, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 2234 ms

Resolved: Bofrost.com performance has improved in f71fdc1 after 6 minutes.


Fix strings that say "search by prefix" to be "filter by prefix"

@MRayermannMSFT
On the rel build 20230131.13. The string is 'Search by prefix'.

Verified this issue on the build 20230202.3. Fixed.


How to deal with slots in tunnels?

Hi,
I've been struggling to find a solution to pass the slots into a Tunnel.Consumer.
The following is not working (with is expected?):
<Tunnel.Consumer>
  {(state: State) => {
    console.log(state);
    return (

        <slot />

    );
  }}
</Tunnel.Consumer>

I did not find a documentation, how passing elements to the consumer can be achieved. What would be the straightforward solution to something like this?

@fanick-ber I had the same issue and from what I can tell this is not possible, although I am not the developer. However I found somewhat of a way around it.
I wanted to render certain things differently based off of render so instead of using Tunnel.Consumer I used the Tunnel.injectProps method as seen in this issue #7. This allowed me to use a conditional statement inside my child component.
The main cause of issue seems to be that the <Tunnel.Consumer> loses the scope of slots. So in your case:
export class YourComponent {
   // ...
  @Element() el: HTMLElement; // is required for injectProps
  @Prop() myProp: string;
  // ...
  render () {
      console.log(myProp); // can do whatever you want with the passed on prop from here
      return (

          <slot />

      );
  }
}

Tunnel.injectProps(YourComponent, ['myProp']);

Thanks a lot for your help!
I did not get it running, yet. Somehow the linter already complains about the wrong type for the injection (type string is not assignable to type State) for the myProp injected prop.
I'll test further.

@fanick-ber Before you get too far there is a partial problem, if you plan on using multiple "instances" of your custom element, this whole module doesn't seem to work instance by instance, prop-wise, see issue #8 still waiting on the developer for a response on that.

oh okay, thanks again!
I would love to see that solved :-)

I am going to mark this as resolved.


ENH: Support BSLookbackOption put

from pfhedge.nn import BSLookbackOption

m = BSLookbackOption(call=False)

Traceback (most recent call last):
  File "/private/tmp/tmp.py", line 3, in <module>
    m = BSLookbackOption(call=False)
  File "/usr/local/lib/python3.9/site-packages/pfhedge/nn/modules/bs/lookback.py", line 51, in __init__
    raise ValueError(
ValueError: BSLookbackOption for a put option is not yet supported.

Hi @simaki,
Is this still open? If yes, I would like to work on it.
Regards,


All basic matchers should have corresponding validators

For example we have:
expect.stringMatching(...)  but not expect().toBeAStringMatching(...)

Do you want to preserve a strict naming scheme like expect().toBeXXX() based on expect.XXX() or should we possibly try to make them more concise (e.g. expect(actual).toMatch(pattern))?

I think we should be consistent. So if we want to change the naming for validator we should rename matcher to.
I like stringMatching b/c it's obvious what it does and with what types it works. And we already have bunch of patterns names like this: toBeAContainerWith(...expectedItems)

Closing this as this is exactly what we are doing for v0.3


Multiple share links library

[X] New method to update Share link with new parameter sharelink
[x] New method to create a share link with all options needed
[x] Create new Test update share
[x] Create new Test create share
[x] Update old tests

@davivel new tests needed. if you want to check it, the update method ready :)

All changes requested made, take a look @davivel and I will merge

:+1:

🎉


Static middleware tries to serve directory and server dies

Ran into an interesting issue. Ideally clean routes shouldn't need to worry about conflicting with folder structure. For example:
+ dist
  + dashboard
    + home
  - index.html

Static route like:
{ "/**!(.*)": "index.html" }

Angular route like:
$routeProvider.when('/dashboard', {
  templateUrl: '/dashboard/home/home.html'
})

I want GET /dashboard to serve index.html and for angular to take it from there. Unfortunately the static server tries to serve the dashboard directory, and it blows up.
Error: EISDIR, read

What version are you running?

The reason I ask is because I am unable to replicate with that code. There was a bug like this that got fixed in version 2.1.2 in commit https://github.com/divshot/superstatic/commit/ea00359f24946c9757eb48a029c7f351d1008a83.

My bad, it's fixed in latest. I reverted to avoid the etag situation.


Markdown not rendering correctly on quandl4j.org

It's a little messed up around the section:
Add the following fragment to your Maven POM file ```xml
com.jimmoores quandl 1.4.2

Needed an extra LF, thanks.


SwiftUI have some offset on iOS 14.4 simulator

Hello everyone,
I noticed today that the snapshots produced by the iOS 14.4 simulator have an incorrect offset on the top.
To test this I created a completely new project with minimum deployment target of iOS 13, added the SnapshotTesting package via the swift package manager to the test target and copied the testSwiftUIView_iOS test from SnapshotTestingTests.swift. The results are as following:

With the simulator running iOS 14.4:

With the simulator running iOS 13.7:

Can it be that I am missing some configuration in the project? I am asking because running the tests from the cloned repo seems to work just fine.
An other observation I made is that the offset is dependent on the simulated device. For the iPod touch (7th generation) simulator running iOS 14.4 the offset is smaller then for the above tested iPhone 11.

I'm also seeing this issue, have you found a workaround?

No sadly I have not found a workaround, beside using the 13.7 simulator for now.

So it looks like the issue here is the ignoresSafeArea: property on UIHostingController. The built-in SwiftUI view snapshotting strategy wraps the SwiftUI view in a hosting controller but does not set this property to false. I have been able to get rid of this offset by explicitly wrapping my SwiftUI view in a hosting controller with ignoresSafeArea: set to true. Can you see if this works for you?

Am I missing something or why do I not have the UIHostingController initializer with the ignoreSafeArea: property?
But it also works by adding the .ignoreSafeArea() view modifier. Thanks a lot.

Ah, it looks like that's a custom extension we have within our project. I can't share the exact code but it seems to be based on this: https://gist.github.com/b8591340/97a8fb48822ac83e9e1cbbc746b258ef
If .ignoresSafeArea() works for you that's less hacky, it didn't work for me unfortunately.

Since this doesn't appear to be an issue with the library, I'm going to convert it to a discussion for now. If you believe this kind of thing can/should be addressed in the strategy, we'd be happy to discuss potential fixes there!


bump staging CLI release triggers for release v0.8.0

Issue #, if available:
Description of changes:
bump staging CLI release triggers for release v0.8.0
Why 8, you may ask? See https://github.com/aws/eks-anywhere/blob/release-0.7/release/triggers/eks-a-release/development/RELEASE_NUMBER
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/override eks-anywhere-attribution-files-presubmit
/override eks-anywhere-presubmit
/override eks-anywhere-release-tooling-presubmit


[WBCAMS-447] fix indexing of benefits

Thanks @jonathan-longe I am asking @sunanditasahu to review the PR because she's more familiar with the code than I am.


Withdrawal problem in Sollet.io

I made a transaction on Sollet.io to withdraw my sol from Sollet.io to other exchange. By the way transaction went fail but it still doesn't reflect in my Sollet.io account.
Please someone help me to solve my problem and also help me how to get refund.

Please post more info, tx signature, sollet screenshot

The above screenshot is of my sollet account in which my transaction gets failure but still it not credited back in my wallet

Please post more info, tx signature, sollet screenshot

This screenshot tx is a serum cancel order tx not withdrawal tx .
your fund may be in serum dex . Check if there has any unsettled fund.

This screenshot tx is a serum cancel order tx not withdrawal tx .
your fund may be in serum dex . Check if there has any unsettled fund.

I have seen in serum also but there is no transaction details.

Any other option to get my amount back in my wallet.


Multiple event listing on single day

Hi, Congrats on a great calendar. I've a question though, when you have more than one event on a day each successive event appears to the right of the previous, this look OK on a computer, but on a mobile device the second event appears at the bottom of the calendar as there is no room to appear to the right. Is there a tweak to make events appear immediately below each other?

I think what he meant was, all the event was on one row by itself. Is there anyway to left align everything?

Into something like this?

<EMAIL_ADDRESS>

i have same problem of ErathiaChia, is possible to align events to the left?

Play with css...
Something like
#cal-day-box .day-highlight {
  position: absolute;
  /*width: 94.5%;*/
  min-height: 30px;
}

#cal-day-box .day-event {
	max-width: none;
	width: 94.5%;
}

Should be nice...

#cal-day-box .day-highlight {
position: absolute;
}

its worked fine for me, thank you!

As @crankharder nave already mentioned it is not a trivial task. And I do not think it is worth doing with what we have now.  I mean with all those underscore, jquery dependencies. The purpose of this calendar was to be light and simplistic. I have long going dream to create new one (based on this one) but built on web components standards so it could be used without dependencies with any modern framework like Aurelia, Angular, ..
SO this feature is for the future version, totally refactored calendar.


Add a Toolbar based on iTwinUI button group

Changes
...
Testing
...

@mayank99 we are trying to add a surface below a button group to style the toolbar. However, the surface is either filling the parent (width: 100%)

OR not growing after the overflow (width: fit-content)

Would it make sense to enhance the ButtonGroup to provide a different container based on which the overflow would be calculated (or have it nested by default)?
Alternatively, could we avoid using ButtonGroup.overflowButton and implement custom overflow logic?

@mayank99  we are trying to build this component to navigate the group toolbar items (nested menus):

After clicking on Group 2_1:

It would need to support multiple columns as well:

Would it make sense to use DropdownMenu or we'd have to build it from basic iTwinUI components?
The only issues I've noticed so far are related to keyboard navigation:

After changing the group (click on a group item OR back button) the auto-focus is not kicking in
It would probably make sense to support ArrowLeft/ArrowRight keyboard navigation in multi-column mode

we are trying to add a surface below a button group to style the toolbar. However, the surface is either filling the parent (width: 100%)
OR not growing after the overflow (width: fit-content)

This makes sense because the ButtonGroup itself is normally "invisible", i.e. it does not have any background or border (unlike Surface). With 100%, it always fills the parent container, and then the buttons inside it will leave some space left over for overflow. With fit-content it never has the chance to grow, because it only looks at the "current" items. (In iTwinUI, we only use 100% for overflow)

Would it make sense to enhance the ButtonGroup to provide a different container based on which the overflow would be calculated (or have it nested by default)?

Depending on what you have in mind, you could contribute it to iTwinUI. The overflow logic was done a long time ago so probably needs improvement anyway.

Alternatively, could we avoid using ButtonGroup.overflowButton and implement custom overflow logic?

From your screenshot it looks like you don't even need ButtonGroup because you have completely different visuals. So you could just put buttons inside a Surface if you want.

@mayank99 we are trying to build this component to navigate the group toolbar items (nested menus)

This looks like a separate task that you probably shouldn't tackle in the same PR as the base toolbar?
We have had an open feature request for nested menus for a while. There was an attempt to work on it, but it's quite difficult to get right, so it was abandoned. https://github.com/iTwin/iTwinUI/issues/653

It would need to support multiple columns as well:

Obviously, this isn't supported in our DropdownMenu currently.

Would it make sense to use DropdownMenu or we'd have to build it from basic iTwinUI components? The only issues I've noticed so far are related to keyboard navigation:

After changing the group (click on a group item OR back button) the auto-focus is not kicking in
It would probably make sense to support ArrowLeft/ArrowRight keyboard navigation in multi-column mode

I don't think it makes sense to shoehorn DropdownMenu into this scenario. Is your component even a menu? Generally speaking, a menu should consist of clear actionable items.

Even then, you might want to start with a simpler implementation where you don't implement arrow key navigation. Make it a list of regular buttons.

 {/* or
 */}

 {/* or
 */}
    <button>Item 1</button>

    <button>Item 2</button>

    <button>Group 3</button>

 {/* submenu */}

        <button>Item 3.1</button>

The only thing you'll need to do after this is to move focus when moving back and forth between different menu levels. The regular Tab key navigation will allow the user to focus buttons within a list.
Also you can use our Popover, which will take care of Esc key handling and outside clicks.

we are trying to add a surface below a button group to style the toolbar. However, the surface is either filling the parent (width: 100%)
OR not growing after the overflow (width: fit-content)

This makes sense because the ButtonGroup itself is normally "invisible", i.e. it does not have any background or border (unlike Surface). With 100%, it always fills the parent container, and then the buttons inside it will leave some space left over for overflow. With fit-content it never has the chance to grow, because it only looks at the "current" items. (In iTwinUI, we only use 100% for overflow)

Would it make sense to enhance the ButtonGroup to provide a different container based on which the overflow would be calculated (or have it nested by default)?

Depending on what you have in mind, you could contribute it to iTwinUI. The overflow logic was done a long time ago so probably needs improvement anyway.

Alternatively, could we avoid using ButtonGroup.overflowButton and implement custom overflow logic?

From your screenshot it looks like you don't even need ButtonGroup because you have completely different visuals. So you could just put buttons inside a Surface if you want.

@mayank99 we are trying to build this component to navigate the group toolbar items (nested menus)

This looks like a separate task that you probably shouldn't tackle in the same PR as the base toolbar?
We have had an open feature request for nested menus for a while. There was an attempt to work on it, but it's quite difficult to get right, so it was abandoned. iTwin/iTwinUI#653

It would need to support multiple columns as well:

Obviously, this isn't supported in our DropdownMenu currently.

Would it make sense to use DropdownMenu or we'd have to build it from basic iTwinUI components? The only issues I've noticed so far are related to keyboard navigation:

After changing the group (click on a group item OR back button) the auto-focus is not kicking in
It would probably make sense to support ArrowLeft/ArrowRight keyboard navigation in multi-column mode

I don't think it makes sense to shoehorn DropdownMenu into this scenario. Is your component even a menu? Generally speaking, a menu should consist of clear actionable items.

Even then, you might want to start with a simpler implementation where you don't implement arrow key navigation. Make it a list of regular buttons.

 {/* or
 */}

 {/* or
 */}
    <button>Item 1</button>

    <button>Item 2</button>

    <button>Group 3</button>

 {/* submenu */}

        <button>Item 3.1</button>

The only thing you'll need to do after this is to move focus when moving back and forth between different menu levels. The regular Tab key navigation will allow the user to focus buttons within a list.
Also you can use our Popover, which will take care of Esc key handling and outside clicks.

Thanks, that's very helpful. I've noticed some quirks in the iTwinUI overflow logic, because even if the overflow is disabled, the layout hooks still run and the button group is rendered w/ fewer items in between frames (that caused some issues in my custom overflow logic). I'll try to remove the button group, as suggested and replace the drop-down menu with a custom component.


Disable webserver logging for dump1090

When reading the logs from Docker, it is full with lines like this:
[07/Jun/2019 22:54:46] "GET ..............
Those are webserver logs from dump1090.
Any way to disable webserver logs?

I think you can modify supervisord.conf and change the log output.
[program:python]
command=/usr/bin/python -m SimpleHTTPServer 8080
directory=/usr/lib/fr24/public_html
stdout_logfile=/dev/null
stdout_logfile_maxbytes=0
stderr_logfile=/dev/null
stderr_logfile_maxbytes=0

Thanks that worked.
Because no vi text editor is present I copied the original file from terminal, edited it and injected it back via echo.


Enhance the placement schedule time when add a new cluster

The placement schedule time is too long when add a new cluster.
steps:

create 100 managedclusters
create 100 placements which select these managedclusters
create a new managedcluster which should also be selected by all the placements
watch the placement schedule time(placement.Status.NumberOfSelectedClusters  PlacementDecisions.Status.Decisions)

/remove-stale


Merge master into live-based

Docs Build status updates of commit 2e87b4f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

reference/3.0/Microsoft.PowerShell.Core/About/About.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Aliases.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Methods.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_PSSnapins.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_Ise_exe.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Preference_Variables.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Prompts.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_FAQ.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Requires.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Signing.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Split.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Types.ps1xml.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_WMI_Cmdlets.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_WS-Management_Cmdlets.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_pipelines.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.WsMan.Management/About/about_WS-Management_Cmdlets.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.WsMan.Management/About/about_WSMan_Provider.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_InlineScript.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Suspend-Workflow.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_WorkflowCommonParameters.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Workflows.md
:warning:Warning
View (powershell-3.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/About.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Aliases.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Methods.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_PSSnapins.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_PowerShell_Ise_exe.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Preference_Variables.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Prompts.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Remote_FAQ.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Requires.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Signing.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Split.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Types.ps1xml.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_WMI_Cmdlets.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_WS-Management_Cmdlets.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md
:warning:Warning
View (powershell-4.0)
Details

This comment lists only the first 50 files in the pull request.

reference/3.0/Microsoft.PowerShell.Core/About/About.md

[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md

reference/3.0/Microsoft.PowerShell.Core/About/about_Aliases.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Methods.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_PSSnapins.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_Ise_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Prompts.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_FAQ.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Requires.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Signing.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Split.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Types.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_WMI_Cmdlets.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_WS-Management_Cmdlets.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_pipelines.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.WsMan.Management/About/about_WS-Management_Cmdlets.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.WsMan.Management/About/about_WSMan_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_InlineScript.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Suspend-Workflow.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_WorkflowCommonParameters.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Workflows.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/About.md

[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md

reference/4.0/Microsoft.PowerShell.Core/About/about_Aliases.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions_CmdletBindingAttribute.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Hash_Tables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Methods.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_PSSnapins.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_PowerShell_Ise_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Prompts.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Remote_FAQ.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Requires.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Signing.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Split.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Types.ps1xml.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_WMI_Cmdlets.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_WS-Management_Cmdlets.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Windows_PowerShell_ISE.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


push error: (413) Request Entity Too Large.

I have Chocolatey Simple Server (2019, IIS10) running successfully with a few small packages, but I cannot get it to accept packages of any size.  I have been able to push/import a 4.7MB .nupkg, but when I try a 6.7MB .nupkg (my next smallest) or larger, I get:
Failed to process request. 'Request Entity Too Large'.
The remote server returned an error: (413) Request Entity Too Large..

Except for the API Key, I don't think I've changed anything in the web.config file (I wouldn't know what I was doing.) from when it was set up.  Specifically, maxRequestLength:
<system.web>
    <compilation debug="false" targetFramework="4.6" />
    <!-- maxRequestLength is specified in Kb -->
    <httpRuntime targetFramework="4.6" executionTimeout="1200" maxRequestLength="2147482548" />

and the maxAllowedContentLength:
<requestFiltering>
        <!-- maxAllowedContentLength is specified in Bytes -->
        <requestLimits maxAllowedContentLength="2147482548" />
      </requestFiltering>

are as they came and appear to be sufficient.  Where else can there be a problem causing this error?  I'm an IIS noob, but I figured that between the instructions and the chocolatey.server install, it would be all ready for "normal" use without esoteric tweaking required.  Given that, I can't be the only person to have this problem.
Help is appreciated.

It's likely a misconfiguration and the web.config is being ignored. Change it to add something that breaks it.
And it works fine for most people. Probably something small being missed.

Assuming you can push something, but once you try to push anything slightly bigger it falls down tells me you have ASP.NET hooked up properly in IIS with the right app pool set up. So trying to look at other areas

Well, I've narrowed down the size limit.  I am able to push packages with a nupkg of 4,766,523 bytes or less, but I get the error on a package that is 4,842,218 bytes or more.  I haven't searched for anything between those values, but I also don't think it would matter much.
Otherwise, I have no answer so far.  I am NOT a web master, so a lot of IIS is a mystery to me.

No worries. I think that something is misconfigured somewhere. I can definitely submit packages bigger than 4MB to an instance of Chocolatey.Server with no issue.
It might be a good idea to revisit the instructions at https://chocolatey.org/docs/how-to-set-up-chocolatey-server#setup-manually. (maybe start over - copy the packages you do have off somewhere first).
The chocolatey packages folder will contain chocolatey.server, but the actual implementation is likely at c:\tools\chocolatey.server - make sure the web.config there is good.

I think I found the solution... (from:  https://forums.iis.net/t/1239202.aspx?413+Request+Entity+Too+Large)

Launch “Internet Information Services (IIS) Manager”
Select the site that you are hosting your web application under it.
In the Management section, double click Configuration Editor
In the Section dropdown select: system.webServer  then serverRuntime
Modify the uploadReadAheadSize section to be like 20MB (so, 20971520 -- the value there is in Bytes)
Click Apply

The value on my system was 1048576.  I have no idea why a 1MB setting like that would cause a failure around the 4.6MB range, but with that change I have now successfully pushed a ~23MB package.
Hope this helps someone.  (Maybe it it should be added to the wiki?)

Well, back to the drawing board.  I am now getting the same error for a 158MB package.  I increased the uploadReadAheadSize indicated above to 50MB without success.  When I tried 100MB, I get an error that it is outside the bounds of a uint32 value.
Clearly, this isn't the solution, and somehow I got lucky previously.

So, I screwed up because the error about the uint32 value was because I cut and pasted the number (in bytes) and I didn't remove the commas from the number.
Once I change the value to the byte equivalent of 160MB (without commas!), it works.

More weirdness:
I created an embedded package that was 233MB.  I dropped the .nupkg into the "packages" folder, and maybe a day later (not sure exactly), it was still sitting there and Choco server didn't ingest it.
It's not clear to me how often the server checks for these .nupkg files, so I thought I would just push it to the server.  When I attempted that, I got the "(413) Request Entity Too Large" error.  This has been the same problem as all along since this package is larger than the 160MB I set the uploadReadAheadSize to (as above).  It was the end of the day on Friday, so I left it as is for the weekend and didn't change anything.
Today, I thought I'd again change that uploadReadAheadSize to accommodate my larger package.  However, I noticed that the .nupkg file was no longer in the "packages" folder.  Instead, there was a new sub-folder with the package name.  At some point over the three days, Chocolatey had ingested the same package it had just told me was too big!
How do I make sense of what is going on here?  I can accept that pushing has a size limit which internal ingestion does not (although it would be nice for that to be documented somewhere), but how long should I expect a .nupkg file to sit in the "Packages" folder before it gets ingested?  Where is that time configured/adjusted?
Thanks.


Undefined variable: "$input-border-color" in awesome-bootstrap-checkbox.scss

<EMAIL_ADDRESS>Error: Undefined variable: "$input-border-color".

If you're in the same position as me, you got this error because you're using bootstrap 3. Change your awesome-bootstrap-checkbox npm version to 0.3.7 (i.e. change package.json then npm update) to get bootstrap 3 compatible version.

Same issue here: https://github.com/flatlogic/awesome-bootstrap-checkbox/issues/131
But is there any mention somewhere, that the new versions are bootstrap 4 only and are incompatible with bootstrap 3?


Function argument Type-assertion does not work correctly

TypeScript Version:  3.6.0-dev.20190601

Search Terms:

Function argument
Type-Assertion
Argument-Types
promisify
Function-overloads
Overloads

Code
declare function sourceMaps(): NodeJS.ReadWriteStream;
declare function sourceMaps(path: string): NodeJS.ReadWriteStream;
declare function sourceMaps(path: string, options: object): NodeJS.ReadWriteStream;
declare function sourceMaps(options: object): NodeJS.ReadWriteStream;

declare function queue<TArgs extends any[]>(fn: (...args: TArgs) => NodeJS.ReadWriteStream, ...args: TArgs): any;

declare function altQueue(fn: () => NodeJS.ReadWriteStream): any;
declare function altQueue<TArg1>(fn: (arg1: TArg1) => NodeJS.ReadWriteStream, arg1: TArg1): any;
declare function altQueue<TArg1, TArg2>(fn: (arg1: TArg1, arg2: TArg2) => NodeJS.ReadWriteStream, arg1: TArg1, arg2: TArg2): any;

queue(sourceMaps);              // Reports an error
queue(sourceMaps, "");          // Reports an error
queue(sourceMaps, "", {});      // Reports an error
queue(sourceMaps, {});

altQueue(sourceMaps);
altQueue(sourceMaps, "");       // Reports an error
altQueue(sourceMaps, "", {});   // Reports an error
altQueue(sourceMaps, {});

Expected behavior:
TypeScript should recognize there is a function-overload which matches the TArgs- or TArg1- and TArg2-type.
Actual behavior:
TypeScript reports an error expecting the argument-types to match the last declaration of the function.
Playground Link:
Link to Playground
This issue is, for example, affecting the promisify-function of node.js' util-module:
import { promisify } from "util";

declare function test(callback: (error: Error, result: any) => any): void;
declare function test(name: string, callback: (error: Error, result: any) => any): void;
declare function test(options: { name: string, author: string }, callback: (error: Error, result: any) => any): void;

promisify(test)();
promisify(test)("");                        // Reports an error
promisify(test)({ name: "", author: "" });  // Reports an error

Related to or duplicate of #30369, #29312 ?

I'm not that sure whether this is the same issue but it sure does look a little similar, that's true

We can't yet support higher-order overload resolution, which is what all of these would require. The linked issues go into more detail


make the armor header and footer inline

@maxtaco @malgorithms
(There's a good chance this will fail a test somewhere.)
Before
BEGIN SALTPACK MESSAGE.
kYM5h1pg6qz9UMn j6G7KB2OUinEheb Gu4oiGFwXwPiASu HGKGly3ND6HxSqG M1oyIAfmkRnh63t KTEruYC9SvgnpXF PjADlbCB6EWkEgS 3xW0vQABZtDH7cb KU94goDCE734rbk VV4Sqo7YXtK4HJ5 vfAweQ0Hry9qPUU 3RfWU0zYAkHOTQa 0YN8ZtC8n08hyYq qXGp8oQuRr5Yx9A tn6f0heVErJHvSs DJupDic0L4E3r30 2rFXxWleft71Lc8 Ec2Kqd7Lpusilhi qM40oQeqzOxHCcQ erNuweI9zNaQveM u00.
END SALTPACK MESSAGE.
After
BEGIN SALTPACK MESSAGE. kYM5h1pg6qz9UMn j6G7KB2OUXnrO4U jxfvGbcfFn5zKNm KO7M8wGKChqAEn3 ZQ0UdHpjLbgaAa0 hOzeDbGdAnSCScz EYTmj5CLyqkmCJM yx4U2G8Dc0P23fP Fg9vodhYUS0s9Wr PgLtZDugm1Ta5su iC0Vxvi9YJfv6Rr 0o0MW6YvJFdhnXf lGdT9A098puYiZl WmJP4zOjfi2umcl niAd0ApQakZXWMS 994fdChBkVU50B1 588Cnmqsbn9t6Hs dZrkZvWl3lRWLql hznTg1vxpxSqvKR o0pJukffBy7tplM y00. END SALTPACK MESSAGE.

Looks good but yeah, fix up the tests.

@maxtaco looks like everything's passing. Weren't there some checked in armor blobs in a test somewhere though? I was expecting something to fail...

See stream_classifer_test.go.  Those are the old style armored-messages, which still pass the currently parser.  I'd just reformat them so that they're in the new style.

We'll need to completely replace those example blobs when we remove the old codepath from the classifier function. Will take care of that in a separate PR.


Since version 1.0.12 the language server runs out of memory

Since version 1.0.12 the language server runs out of memory. So maybe this is caused by an internal loop.
I already increased the memory limit to 6095M, but the same result.
Command:
DEBUG     Running<EMAIL_ADDRESS>'-n' '-c' '/private/var/folders/__/mpdnyh613959vmhfbl19gl700000gq/T/eO0DcQ' '/Users/eddy/.vscode/extensions/zobo.php-intellisense-1.0.12/vendor/felixfbecker/language-server/bin/php-language-server.php' '--tcp=<IP_ADDRESS>:51312' '--memory-limit=6095M'
After parsing 20 files:
PHP Fatal error:  Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 262144 bytes) in /Users/eddy/.vscode/extensions/zobo.php-intellisense-1.0.12/vendor/felixfbecker/language-server/src/DefinitionResolver.php on line 910

Hi! Thanks for the report. This could be it yes. Can you look at the output while it is indexing and try to "guess" what file it happens in. Do you think you have a class or set of classes, interfaces, traits that could form an endless loop?
I can probably add some code to prevent this.
You can enable additional logging in settings

setting php-intellisense.trace.server
Thanks!

I'll probably need a stack trace. Ideally you'd enable xdebug in your php installation and change a line of code in the source:
php-language-server.php, line 43 $xdebugHandler->check(); and comment that out. Source is in /Users/eddy/.vscode/extensions/zobo.php-intellisense-1.0.12/vendor/felixfbecker/language-serve/bin/php-language-server.php
I'll probably add a setting to allow switching this on or off.
If you can do that, you should get a back trace when the problem happens.
Also, the last Parsing .... line should indicate which file triggered the error.
If you can, consider sharing it with me, or if you can, try to isolate in what part of the file the error happens.
Thanks.

I found the loop  and made a quick fix by checking the length of the debug_backtrace result (see below) But it is better to keep track of the depth by adding another parameter to the resolveExpressionNodeToType method. See also the debug_backtrace in JSON format.
DefinitionResolver.php
    /**
     * Given an expression node, resolves that expression recursively to a type.
     * If the type could not be resolved, returns Types\Mixed_.
     *
     * @param Node\Expression $expr
     * @return \phpDocumentor\Reflection\Type|null
     */
    public function resolveExpressionNodeToType($expr)
    {
        if(count(debug_backtrace()) > 1000) {
            throw new \Exception("Endless recursive loop detected");
        }

        // PARENTHESIZED EXPRESSION
        // Retrieve inner expression from parenthesized expression
        while ($expr instanceof Node\Expression\ParenthesizedExpression) {

39 - debug_backtrace.json.zip

Thanks so much for the dump. I think I can get what I need from it. I think I already know where the problem came from I just need to find the right way to implement what I need. Will get back as soon as I can,

Thanks for the fix. Version 1.0.13 works fine now


Improve Unit Test Coverage of MapArrayReader

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
There is no unit test coverage of MapArrayReader that I can find
Describe the solution you'd like
We should have some unit tests

@tustvold I guess I can help, could you assign it to me?

Thank you, FWIW I think MapArrayReader may currently be incorrect, see #1699, but up to you if you want to tackle that - Dremel encoding is very head hurty


BluePillDemo_Flash example, write val too large

The data you're writing to flash is truncated.
https://github.com/miniwinwm/BluePillDemo/blob/master/BluePillDemo_Flash/Core/Src/main.c#L127
0xBADD10DE4 is not 32-bit.

Thanks, that's a typo that I will fix.

Fixed to remove typo


Image loading

Optimize it. Potential things to explore:

Progressive images (with fade)
Skeleton loading
File format

Started using next/image


[RESTEASY-1794] JAX-RS 2.0 backward compatibility mode

A mechanism for building resteasy-jaxrs and resteasy-client with jaxrs 2.0 dependency instead of jaxrs 2.1. This is off by default ('-Djaxrs20' flag required) and when enabled produces alternative maven artifacts with '-jaxrs20' classifier.

@psakar @Skullman EE7 vs EE8 stuff, please look at the changes to be able to build and use '-jaxrs20' artifacts too

@asoldano Can you please document on related JIRA ? Do you suppose build will produce only single set of artifacts (jaxrs 2.0 compatible ()) or both at the same time (eg. other consumers (products) may require jaxrs 2.1) ?

@psakar the build will create new (jaxrs21) artifacts by default. Given this is a temporary measure, for a temporary wfly need, the expectation is that whoever will build resteasy from sources, he will manually re-build resteasy-jaxrs and resteasy-client modules (only!) with -Djaxrs20 option enabled.
I'm adding this to the jira too.

I noticed that commit has bad id in the message - RESTEASY-1784 instead of RESTEASY-1794


Feature request: Option to show page schema from HTML

It would be great if the tool had an option for including the page's schema (which is contained inside the HTML). The same way I can select onlyMainContent, includeHtml, etc...
Example
Here's a simple example of how I currently extract schema from a page's HTML
async function getSchemaData(html) {
    const $ = cheerio.load(html);
    const schemaScripts = $('script[type="application/ld+json"]');
    let schemaData = null;

    schemaScripts.each((index, element) => {
        try {
            const jsonContent = $(element).html();
            schemaData = JSON.parse(jsonContent);
            return false
        } catch (error) {
            console.error("Error parsing JSON:", error);
        }
    });

    return schemaData;
}

It usually looks like this:
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "@id": "https://mentalmathpro.com",
  "description": "Master mental math and become a human calculator with ease! Our user-friendly website offers 14 and lots of practice to help you.",
  "name": "Mental Math Pro",
  "url": "https://mentalmathpro.com"
}

Benefits
This would provide additional information that could be valuable for various use cases (like SEO analysis and structured data extraction).

Thanks for creating the issue @richardreeze !
This would be a great addition to the tool. The meta-data has semantic value and would definitely benefit some use-cases (like search engines).
Researching this, I think it makes sense to include all the meta-data level parts in the output, like:

meta-tags (title, description, keywords, author, og:.., twitter,)
jsonld data

As some of the data (especially social network related tags) might overlap with other meta-data, I'm considering having two levels under the option of "includeMetaData"

basic level that includes meta-tags
extended level that includes social tags, jsonld data and possibly other formats (like rdfa) down the road..

As for the output format, I would prefer to avoid pure JSON (though we could add a flag to choose the wanted formatting for the meta-data block), I am preferring YAML for this, so something along the lines of:
---
title: "Page Title"
description: "Page description here."
schema:
  "@context": "https://schema.org"
  "@type": "WebPage"
  # ... rest of the schema
---

# H1 tag ...

Thoughts?

This would be great! And yes much cleaner than what I suggested.
I hope this becomes a feature! 🙂

@richardreeze hot from the compiler-
> npx d2m -u https://example.com -meta standard
---
title: "Example Domain"
---

# Example Domain

This domain is for use in illustrative examples in documents. You may use this
    domain in literature without prior coordination or asking for permission.

 [More information...](https://www.iana.org/domains/example)


Query parameter decoding error in server rendering

Versions

nuxt: 2.14.12
node: 14.15.0

Reproduction
Query parameter decoding error in SSR created hook and asyncData hook
Steps to reproduce
https://vvw9q.sse.codesandbox.io/?str=%26&str2=%2526
What is Expected?
Output:
In the asyncData hook on the server
str: &
str2: %26
In the mounted hook of the client
str: &
str2: %26

What is actually happening?
Output:
In the asyncData hook on the server
str: &
str2: &
In the mounted hook of the client
str: &
str2: %26

this breaks with me only on the server when i reload the page, can you explain the problem for me please?

this breaks with me only on the server when i reload the page, can you explain the problem for me please?

this breaks with me only on the server when i reload the page, can you explain the problem for me please?

I'm not very sure, it may be that the server has a problem with the processing of query parameters

this breaks with me only on the server when i reload the page, can you explain the problem for me please?

I'm not very sure, it may be that the server has a problem with the processing of query parameters

This is caused by the decoding of each query - so it's possible to fix this issue but not without breaking this test:
https://github.com/nuxt/nuxt.js/blob/fc51ca333062519d8376262eff93362e3a5739f9/test/dev/encoding.test.js#L24-L28
@pi0 - what do you think? As long as we've decoded the entire URL, I think it should be safe not to re-decode each query separately, but I'd need to tweak the test.


www: Add SIWG-CTC version for SVT-AV1

Basically $title
Tested in VLC12,

Backend Change: https://github.com/xiph/rd_tool/pull/161


Multiple-window menu bug on Windows

On Windows only, when I open multiple Atom windows, then jump from one window's menu to the other window's menu, the menu actions affect the former window.  It should affect the latter window.
Steps to reproduce:

Open two windows in Atom.
In Window 1, click the "View" menu.  Leave it open.
In Window 2, click the "View" menu.  The menu in Window 1 will close when you click it.
Click something like, say, "View -> Developer -> Toggle Developer Tools".  The tools are toggled on Window 1, even though you clicked the item in Window 2.

I noticed this problem while looking at https://github.com/atom/atom-shell/issues/802.  In that case, I noticed that I could open two Atom windows, launch "File -> Open File..." in Window 2, then apparently open Window 2's menu by first clicking on Window 1's menu.  Selecting something in Window 2's apparent menu actually affects Window 1.

This is still an issue in master today.


Memory issues after using a small svga

We have a svga-file at work, I check the svga with svga-online-player and it’s memory is very fine(0.7M), but when I use it at my project, the page memory is increased by dozens of MB, I want to know what went wrong.
Here are the information about this svga-file from svga-online-player
{
  "version": "2.0",
  "FPS": 30,
  "frames": 90,
  "videoSize": {
    "width": 1500,
    "height": 1624
  }
}
内存占用：0.7 M
img_249 --- {"width":186,"height":116}
img_250 --- {"width":186,"height":116}
img_251 --- {"width":186,"height":116}
img_252 --- {"width":186,"height":116}
img_253 --- {"width":186,"height":116}
img_254 --- {"width":186,"height":116}
img_392 --- {"width":50,"height":54}
img_393 --- {"width":50,"height":54}
img_394 --- {"width":50,"height":54}
img_395 --- {"width":50,"height":54}
img_461 --- {"width":41,"height":50}
img_462 --- {"width":41,"height":50}
img_463 --- {"width":41,"height":50}
img_464 --- {"width":41,"height":50}
shenzi --- {"width":153,"height":224}

This is the svga-file
1575884910782-mhzy3d (1).svga.zip
Thanks, have a nice day.

Can you provide a demo? And how much memory used?


Initial mouse detection

Thanks for a cool lib!
Is there a reason why a touch device is identified on the first touch event (e.g. using your finger to scroll a page) but a mouse isn't identified the first time the user moves the cursor over the page?

Thanks @jareware!
My initial feeling is that the events touchstart, mousedown and keydown that are used to detect interactions are all somewhat individually fired. Even when scrolling with touch, touchstart only happens once at the beginning.
On the other hand, mousemove (and similarly, scroll) fire continuously as the event happens. My concern is that this could be more processor "expensive" than a small utility script like What Input deserves. Even with debouncing, the function is trying to fire continuously as the mouse moves about the page but the full execution is stopped.
A good debouncing strategy might do the trick and my theory on performance is completely untested. I do agree that earlier mouse detection would be a benefit! I'll keep this ticket open and look into it.

You're right, the mousemove suggestion was rather naive...
What about mouseenter, though?

That could work! I just whipped up this Pen as a  proof of concept.
It looks like, even if the mouse is already over the body, it'll fire the mouseenter event when the page loads, but never again unless the mouse leaves and re-enters the browser window. I'll do some additional browser testing to confirm that this works.

Really neat, looking forward to setting this up!


Add html rendering of Markdown tables

I think this was just overlooked. The Table method is from Markdown/src/GitHub/table.jl while all the others are from Markdown/src/render/html.jl
Closes #220.

Is there something else to be done in order for this bugfix to be merged?

Any chance you could add a test for this?

I see what I can do.
P.S.: Did this repository just move?

Thanks!
And yes, it did :)

Added the test.


ObservableListView: incorrect ScrollState from time to time.

Hello.
Lib version: 1.4.0
I'm experiencing strange behavior of onUpOrCancelMotionEvent method in ObservableListView.
From time to time, ScrollState passed to method is wrong. Different than actual swipe.
This problem exists only on 5.0.2, on 4.4.4 is working fine.

Hi,
thank you for the feedback.
I'll check that later but could you tell me more details?
(e.g. when over-scrolling, when using ViewPagerTabActivity sample, or whatever.)
Does it happen on my samples?

Hello.
Yes, it is happening in your demos.
For example, in ActionBarControlListViewActivity where you continuously swipe up and down, from time to time ActionBar wan't react. It will stay on his position. When you swipe again, it will react.

the title can scroll with the content parallax?
if the content scroll to the top, then you continue scrolling bottom to up,the title must scroll to top with the content, but in your example,when you scroll a little,the result is,the title can not scroll to the top

@pawelantczak
Thank you for your information and sorry for my late reply.
I've also confirmed a similar behavior in ActionBarScrollViewActivity.
I'll investigate that later.

Have anyone solved this?
I'm getting a weird behavior when scrolling sometimes: the actionbar might not change its size, and sometimes when it does, the scrolling of the ListView stops for as long as the actionbar changes its size.

Guess not


Conditional breakpoint not hit

Hi,
I am testing the conditional breakpoint feature but can't get it working.
I am using the raft TLA spec for testing purpose.
Ideally, what I'd like is:
when setting up a break point as follow:

I'd like to hit that block of code when the expression state[i] = Leader is satisfied (defined in isLeader). Instead of that, it stops each time BecomeLeader is called without satisfying the expression (it behaves as a normal breakpoint).
Looking at this video though, I managed to get a different result.
This time I did this:

this time it stopped with the expression state[i] = Leader satisfied but in the next state (the prime one). I am a bit confused by this behaviour.
Is there is a simple way to get the behaviour I described in the beginning?
Thanks for you help!

Thanks for the tip! That's useful.


add PocoCpp example

This commit will add an example as requested in pull request #445.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.504
https://travis-ci.org/ingenue/hunter/builds/138040011

Testing

@aarnchng mingw failed on windows, analyze failed on linux/osx:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.510
https://travis-ci.org/ingenue/hunter/builds/138071786

feel free to fix or exclude from testing

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.582
https://travis-ci.org/ingenue/hunter/builds/139271050

Testing

Looks good. Merging.

Uploading binaries:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.587
https://travis-ci.org/ingenue/hunter/builds/139448904

Uploading binaries

Done. Released: https://github.com/ruslo/hunter/releases/tag/v0.14.28
PS I've excluded newly created msys toolchain since MinGW is not supported.