Live Share session not reachable when hosting from WSL2 via Direct mode

Describe what happened:
When developing within WSL2 via https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl and a live session is shared, others are not able to reach the session. If shared from Windows, it is reachable. If shared via Relay mode, it is reachable. However "Direct" mode is required for data security reasons and does not work.
The problem appears to be because the live session shares the IPv6 address for eth0 within WSL, which others cannot connect to externally as it is a local interface to Windows. If IPv6 is disabled, it will share the IPv4 address of eth0 instead (e.g. 172.17.X.Y) with the same problem. At first glance this makes sense, as WSL2 does not know the Windows IP which is accessible on the network, but it is unclear how this is intended to work. Behavior which would work is if Live Share provided the Windows IP.
Port forwarding and being able to access the required sites have already been accounted for. My main assumption is that it is expected to run WSL2 in bridged mode, however this is not always recommended so I am surprised by the lack of similar reports.
Is there any advice on how Live Share, Remote - WSL, and Direct mode are intended to work together?
What was your system configuration?
Product and Version [VS/VSCode]: VSCode 1.73.1
OS Version[macOS/Windows]: Windows 11 (Windows 10 also tested)
Live Share Extension Version: v.1.0.5788
Target Platform or Language [e.g. Node.js]: N/A
Steps to Reproduce / Scenario:

Install Remote - WSL
Use WSL: Open Folder in WSL
Change connection mode to Direct
Live Share: Share
Connect to given link from other PC on same network --> no connection

Please attach logs to this issue:
For confidentiality reasons only an extract of the log is attached. It represents the (Windows) client trying to connect to a WSL2 host.
LiveShare_WSL2_direct_connect.txt

Hi @Zachary-Kramer - Please attempt to use the Auto or Relay mode. Also, see https://learn.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#connection-modes for further details on Live Share Connectivity.

Hi @derekbekoe that is unfortunately not an option due to data security concerns from non-direct modes.

Hi - Unfortunately we’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it is for you.


Food MIxS package

Opening ticket to keep track of comments, helpful suggestions for the FDA development team.
Cheers,
Lynn

Development complete.

@lschriml  Is this package to be included in the v6 release? i.e. should the items in this package be added to the "MIxSv6 package - to edit" tab?


Add shx to make npm scripts run on Windows CMD and PowerShell

This PR adds shelljs/shx to make project scripts platform independent instead of requiring a bash shell.  Them primary purpose of this is to it easier to run the project on Windows.  The only Windows requirement after this should be to install Node.js (and git obviously).

I don't have Windows, so unless we need to test that it works on Linux, there's nothing I can do.

Yup just wanting to make sure the change doesn't cause any problem for other platforms

Build is successful on Linux.


duplicate entry: permissions/dispatcher/GrantableRequest.class

I am getting this error when i build using gradle
Full stacktrace:
Caused by: org.gradle.api.UncheckedIOException: java.util.zip.ZipException: duplicate entry: permissions/dispatcher/GrantableRequest.class
        at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:43)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:78)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:227)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
        ... 14 more

Can you share the except of your build.gradle files where you include PermissionsDispatcher?

Sorry My bad, I declared permission-dispatcher wrongly. I was using 'compile' instead of apt like below
compile 'com.github.hotchemi:permissionsdispatcher:2.0.3'
compile  'com.github.hotchemi:permissionsdispatcher-processor:2.0.3'
instead of
compile 'com.github.hotchemi:permissionsdispatcher:2.0.3'
apt 'com.github.hotchemi:permissionsdispatcher-processor:2.0.3'
Changed to 'apt it worked fine. Thanks

@john1jan Alright, thanks for your adopting.

Thanks for developing this great library it makes life easier with Marshmallow.


Unknown Video Info Key "dbtype"` fix

Description
ListItem setInfo function has 'infoLabels' dictionary argument.
But this dictionary doesn't have 'dbtype' key.
This is why there was error of:
ERROR <general>: NEWADDON Unknown Video Info Key "dbtype"
The 'dbtype' only exist when getting the infoLabels from a ListItem.
Fix: Added a function for removing this 'dbtype' field before using the ListItem's 'setInfo' function
For more information:

ListItem setInfo:
https://alwinesch.github.io/group__python__xbmcgui__listitem.html#ga0f1e91e1d5aa61d8dd0eac90e8edbf18

ListItem info labels:
https://kodi.wiki/view/InfoLabels#ListItem

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Translation

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

By the way, it's strange but git shows also differents in lines 450, 459 and 486 while they are identical between my fork and yours.

@burekas7 Thanks for your contribution!


Question/Feature Request: Ability to configure tracking of new "To-Do Lists"

Hi,
I searched through the documentation and GitHub issues, but didn't find anything.
Is there a way to prevent the tracking of new To-Do Lists, similar to the "track_new_calendar" configuration variable? If not, would that be a possible future enhancement?
Thanks!

I'll look to add the capability over the next couple of weeks.

Updated docs - https://rogerselwyn.github.io/O365-HomeAssistant/installation_and_configuration.html#todo_sensors


Making presentational components functional

I would suggest to make presentational components functional instead of class based. Functional components are not “dressed up” with any of the capabilities of React component objects and hence there may be performance advantages.

I've done a massive update to this project and converted almost all the components to functional. They are a lot cleaner now since the hooks are less verbose than classes. The Apollo hooks are easier to reason about than the graphql HoC too.
Wasn't able to use hooks for next router since in withData it passes the router when doing SSR. Maybe I'll be able to think of a solution for this later.


[ENH] GroupedForecaster

Reference Issues/PRs
What does this implement/fix? Explain your changes.
Let's say we want to forecast daily worldwide sales for company X. We have daily sales data per country where X operates: our dataset contains three columns: date, sales, and country. Now we could consider three modelling options:

Aggregate all daily sales and estimate with a single model
Cluster countries with similar patterns or characteristics, aggregate per cluster and model per cluster
Model all countries separately

Currently, sktime only supports option 1. For 2 and 3, it is still necessary to write a custom framework to try different aggregations of X and y and compare performance of strategy 1,2, and 3. In this draft PR I'd like to propose a meta-estimator that removes the need for such custom frameworks.
This PR basically imitates the GroupedEstimator meta-estimator from the scikit-lego such that it is compatible with sktime. For further understanding of the approach I'd recommend to take one minute to read through scikit-lego's documentation:
https://scikit-lego.readthedocs.io/en/latest/meta.html#Grouped-Prediction
Does your contribution introduce a new dependency? If yes, which one?
What should a reviewer concentrate their feedback on?
Any other comments?
Very interested in your feedback!
PR checklist

[ ] Finish GroupedForecaster
[ ] Writing tests for GroupedForecaster
[ ] Adjustment of forecasting.model_evaluation.evaluate to support aggregation of y (and X)
[ ] Adjustment of check_y_X to support duplicate datetimeindex when isinstance(forecaster, GroupedForecaster)

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Hi, thank you for pointing out the current efforts on hierarchical forecasting and inviting me to the dev slack!
FYI: I just pushed a functioning (albeit with workarounds wrt check_X_y) implementation of the GroupedTargetForecaster how I had imagined it. A snippet of the interface and how to use it can be found below.
I'll follow up later with the main takeaways of problems I ran into and their solutions.
import pandas as pd
import numpy as np
from sktime.forecasting.compose import TransformedTargetForecaster
from sktime.forecasting.model_selection import ExpandingWindowSplitter, ForecastingGridSearchCV
from sktime.forecasting.naive import NaiveForecaster
from sktime.transformations.series.compose import OptionalPassthrough
from sktime.performance_metrics.forecasting import MeanAbsolutePercentageError
from sktime.forecasting.meta.grouped_forecaster import GroupedForecaster
from sktime.transformations.series.adapt import TabularToSeriesAdaptor
from sklearn.preprocessing import StandardScaler

data = {
    'index':['2020-01-01', '2020-02-01', '2020-03-01', '2020-04-01', '2020-05-01', '2020-06-01', '2020-07-01', '2020-08-01', '2020-09-01'],
    'y':[0,2,4,6,8,10,12,14,16],
}

def flatten_index(df):
    df.columns = ['__'.join(col).strip() for col in df.columns.values]
    return df

def long_to_wide(df, hierarchy:list) -> pd.DataFrame:
    return (df.set_index(hierarchy, append=True).unstack(hierarchy))

def aggregate_to_top(df) -> pd.DataFrame:
    levels = list(range(len(df.columns.names)))
    return pd.concat([
        df.groupby(axis=1, level=levels[:i+1]).sum().pipe(flatten_index) for i in levels
    ], axis=1)

levels=["country", "sector"]

df_wide = (pd.concat([pd.DataFrame(data).assign(country="England", sector="agri"), pd.DataFrame(data).assign(country="Wales", sector="industry")])
    .assign(y = lambda x: x.y + np.random.uniform(0,0.20,len(x.y)))
    .assign(index = lambda x: pd.to_datetime(x["index"]))
    .set_index(["index"])
    .pipe(long_to_wide, hierarchy=levels)
    .pipe(aggregate_to_top)
    .resample('1M').sum()
)
y_train = df_wide.y
X_train = df_wide.copy()

n_rows=y_train.shape[0]
cv = ExpandingWindowSplitter(initial_window=n_rows-3, step_length=1, fh=[1,2])

# CONFIGS
depth = 1

forecaster = NaiveForecaster()
param_grid = [
        {'forecaster__strategy': ['last'],  "scaler__passthrough": [False]},
        {'forecaster__strategy': ['mean'], 'forecaster__sp':[1], 'forecaster__window_length':[None, 2,3,4], "scaler__passthrough": [False]},
]

pipe = TransformedTargetForecaster([
    ("scaler", OptionalPassthrough(TabularToSeriesAdaptor(StandardScaler()))),
    ("forecaster", forecaster)
])

grid = ForecastingGridSearchCV(
    forecaster = pipe,
    cv = cv,
    param_grid = param_grid,
    n_jobs=-1,
    scoring=MeanAbsolutePercentageError(symmetric=False),
)
grouped_forecaster = GroupedForecaster(grid, depth=depth)

grouped_forecaster.fit(y_train, X_train)

cv_final = grouped_forecaster._get_cv_results_agg(y_train, X_train)
cv_clusters = grouped_forecaster._get_cv_results_clustered()

mape = cv_final.mean().test_MeanAbsolutePercentageError

This is a diagram of the modelling done within GroupedForecaster :

These are the steps I wanted to execute, which required some extra work:
1. First perform gridsearch per group.
2. Register each grid's best models and hyperparameters
3. When reusing the model (by using .fit(), and evaluate()): only use best models + hyperparameters from
step 2, don't refit grid search (computationally expensive).
To get this behavior, I needed to implement a different fitting strategy for when the estimator given to GroupedForecaster was of type BaseGridSearch, see .__fit_single_ts()
Furthermore, some rework was required to inspect CV results from both lower hierarchies (country) and upper hierarchies (total). See ._get_cv_results_agg() and ._get_cv_results_clustered().
Is this behavior regarding hierarchical Grid Search within the scope of the STEP you mentioned? Would the design of your new BaseForecaster be compatible with this behavior?


Release/azure communication common/1.2.5

Description
azure-communication-common patch release - 1.2.5
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - azure-communication-common - ci

/azp run java - azure-communication-common - ci

API change check
API changes are not detected in this pull request.

@AikoBB done


Added in missing ReactProp in TextInput for Android

The missing autoComplete is the reason why some Samsung and HTC can't turn off autoSuggestion/autoCompletion successfully.

While testing a mobile application that prioritizes security, it was noted that on some Samsung and HTC devices the TextInput component (username field) would still auto-suggest even with autoCorrect and autoComplete props set to false.
Here is a link to a SO question that had the same issue.
Test Plan
This solution was tested on a Samsung phone that was previously auto-suggesting with props set.
Planning to test this on more HTC and Samsung phones.

Didn't fix all keyboards.


Automated cherry pick of #3431: feat & fix: Add batch operator and fix some bugs for instance group

Cherry pick of #3431 on release/2.12.
#3431: feat & fix: Add batch operator and fix some bugs for instance group

/lgtm
/approve

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@4d2fb41). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #3481   +/-   ##
==============================================
  Coverage                ?   6.99%
==============================================
  Files                   ?     498
  Lines                   ?   83032
  Branches                ?       0
==============================================
  Hits                    ?    5809
  Misses                  ?   76729
  Partials                ?     494

Flag
Coverage Δ

#aFlag
6.99% <0%> (?)

Impacted Files
Coverage Δ

pkg/mcclient/options/servers.go
0% <ø> (ø)

pkg/compute/models/groups.go
8.65% <0%> (ø)

pkg/compute/models/hosts.go
0.34% <0%> (ø)

pkg/compute/models/groupguests.go
1.96% <0%> (ø)

pkg/compute/models/guest_actions.go
0% <0%> (ø)

pkg/compute/models/guests.go
0.6% <0%> (ø)

Continue to review full report at Codecov.

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


Release 0.21.0

related to #823
close #836
This PR is related to two issues, since #836 and #823 cannot be easily split into separate PRs, mainly because #836 could be considered as a subset task of #823.

@sophie-cluml, thanks for working on the new release of Giganto (and the migration optimization—that was a good catch!). I noticed that this PR is using a version of giganto-client that's a few commits behind the latest release (0.20.0). Since @petabi plans to migrate its applications to giganto-client 0.20.0, I'm concerned about potential compatibility issues with Giganto 0.21.0. Would it be possible to update the giganto-client dependency in this PR to the latest release to ensure compatibility?

https://github.com/aicers/giganto/blob/100798454e55fc4c77304167962e883fac136113/src/storage/migration.rs#L436-L438
Could you please change it to migrate_0_19_to_0_21_0?


shouldn't need to specify m::any() for optional parameters

If I have a method as follows:
public function doThis($that, array $options = [])
{
    //do stuff
}

and want to declare an expectation of a call onto it where I don't care about the optional second parameter with:
$foo->shouldReceive('doThis')->with('that')->once();

it breaks because the argument list does not match. Yet:
$foo->shouldReceive('doThis')->with('that', m::any())->once();

succeeds, which seems redundant.
Can we do something sensible here like infer in the case of an optional parameter that null is being passed? Or is there an issue with this? Given that optional parameters are akin to overloading in, say, Java, where method definitions with the same name but different numbers of args are actually separate, I don't see a theoretical issue with this.

No additional feedback from the audience, so going with Dave's thumbs down.


Hello i have find a issue

Swap failed: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"Internal Error - Error: nonce retries exceeded for transaction. This usually means there are too many parallel requests with the same access key.. Please report a bug at https://github.com/aurora-is-near/aurora-relayer/issues","data":{"host":"mainnet.aurora.dev","cf-ray":"6a3856ee034d2362-ORD"}}}}'

Duplicate issue https://github.com/aurora-is-near/aurora-relayer/issues/72


add community packages page

Proposed changes

Unreleased product version (optional)

Related issues (optional)

One thing is that I don't think I'd go looking for page/section like this under Reference. We could start here and move it somewhere else later, but we could also just carve out a new Community section and position this page underneath it, as a start. Something to consider.
I agree we should list more here than just one thing here, though. Would it be a bad idea to augment with a few we’ve built ourselves, to get things going? I realize “community”, but as a reference for the kinds of contributions we want to encourage, might not be a bad idea, to give others more to work by.
Also yeah, we need an introduction explaining what this page is, what forms these contributions can take, and then each listing should have a good title and description of its own as well — again just so folks know what they’re looking at when they arrive and whether it’d make sense for them to click through to a particular package/project/example.
One example that came to mind of what we might do with a page like this is Netlify templates: https://templates.netlify.com/

@jaxxstorm If you want to keep working on this, would you mind moving it over to https://github.com/pulumi/pulumi-hugo?


"@angular-devkit/build-angular" Package upgradation from v12.1.2 to 12.2.1 gives an error

Upgraded Angular version from v12.1.2 to v12.2.1.
Updated other packages to latest version as below:

Before update:
 "dependencies": {
"@angular/animations": "^12.1.2",
"@angular/cdk": "^12.1.2",
"@angular/common": "^12.1.2",
"@angular/compiler": "^12.1.2",
"@angular/core": "^12.1.2",
"@angular/forms": "^12.1.2",
"@angular/localize": "^12.1.2",
"@angular/material": "^12.1.2",
"@angular/platform-browser": "^12.1.2",
"@angular/platform-browser-dynamic": "^12.1.2",
"@angular/router": "^12.1.2",
"applicationinsights": "^2.1.4",
"core-js": "^3.15.2",
"html2canvas": "^1.1.4",
"material-icons": "^1.0.0",
"ngx-toastr": "^14.0.0",
"pdfmake": "^0.2.0",
"rxjs": "~7.2.0"

},
"devDependencies": {
"@angular-devkit/build-angular": "~12.1.2",
"@angular/cli": "~12.1.2",
"@angular/compiler-cli": "^12.1.2",
"@angular/language-service": "^12.1.2",
"@types/jasmine": "~3.8.1",
"@types/node": "^16.4.0",
"@typescript-eslint/eslint-plugin": "^4.28.4",
"@typescript-eslint/parser": "^4.28.4",
"eslint": "^7.31.0",
"ts-node": "~10.1.0"
}
After Update:
 "dependencies": {
"@angular/animations": "^12.2.1",
"@angular/cdk": "^12.2.1",
"@angular/common": "^12.2.1",
"@angular/compiler": "^12.2.1",
"@angular/core": "^12.2.1",
"@angular/forms": "^12.2.1",
"@angular/localize": "^12.2.1",
"@angular/material": "^12.2.1",
"@angular/platform-browser": "^12.2.1",
"@angular/platform-browser-dynamic": "^12.2.1",
"@angular/router": "^12.2.1",
"applicationinsights": "^2.1.5",
"applicationinsights-js": "^1.0.20",
"core-js": "^3.16.2",
"html2canvas": "^1.3.2",
"material-icons": "^1.1.1",
"ngx-toastr": "^14.1.0",
"pdfmake": "^0.2.2",
"rxjs": "~7.3.0",
"tslib": "^2.3.1"

},
"devDependencies": {
"@angular-devkit/build-angular": "~12.2.1",
"@angular/cli": "~12.2.1",
"@angular/compiler-cli": "^12.2.1",
"@angular/language-service": "^12.2.1",
"@types/jasmine": "~3.8.2",
"@types/node": "^16.6.1",
"@typescript-eslint/eslint-plugin": "^4.29.2",
"@typescript-eslint/parser": "^4.29.2",
"eslint": "^7.32.0",
"ts-node": "~10.2.0"
}

Ran ng serve  command.
while running ng serve first or second time. I am able to compile the code but when i am trying to run third time and so on, i am getting below error:

(node:10563) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at String.match ()
at OriginalSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/OriginalSource.js:64:32)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at ReplaceSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/ReplaceSource.js:176:44)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at streamAndGetSourceAndMap (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamAndGetSourceAndMap.js:27:53)
at CachedSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/CachedSource.js:208:35)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at ConcatSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/ConcatSource.js:112:55)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
(Use node --trace-warnings ... to show where the warning was created)
(node:10563) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10563) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Then i downgraded the "@angular-devkit/build-angular" version to 12.1.2  & post that it was working fine(no error).
Can you please take a look and suggest any solution?

Duplicate of https://github.com/angular/angular-cli/issues/21588

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

I have same problem using primeNG version 12 and ng-packagr generate module;
Maximum call stack size exceeded

We cannot setup a minimal repro. It's a private code, So we cannot share it publicly.

Upgraded Angular version from v12.1.2 to v12.2.1.
Updated other packages to latest version as below:

Before update:
 "dependencies": {
"@angular/animations": "^12.1.2",
"@angular/cdk": "^12.1.2",
"@angular/common": "^12.1.2",
"@angular/compiler": "^12.1.2",
"@angular/core": "^12.1.2",
"@angular/forms": "^12.1.2",
"@angular/localize": "^12.1.2",
"@angular/material": "^12.1.2",
"@angular/platform-browser": "^12.1.2",
"@angular/platform-browser-dynamic": "^12.1.2",
"@angular/router": "^12.1.2",
"applicationinsights": "^2.1.4",
"core-js": "^3.15.2",
"html2canvas": "^1.1.4",
"material-icons": "^1.0.0",
"ngx-toastr": "^14.0.0",
"pdfmake": "^0.2.0",
"rxjs": "~7.2.0"

},
"devDependencies": {
"@angular-devkit/build-angular": "~12.1.2",
"@angular/cli": "~12.1.2",
"@angular/compiler-cli": "^12.1.2",
"@angular/language-service": "^12.1.2",
"@types/jasmine": "~3.8.1",
"@types/node": "^16.4.0",
"@typescript-eslint/eslint-plugin": "^4.28.4",
"@typescript-eslint/parser": "^4.28.4",
"eslint": "^7.31.0",
"ts-node": "~10.1.0"
}
After Update:
 "dependencies": {
"@angular/animations": "^12.2.1",
"@angular/cdk": "^12.2.1",
"@angular/common": "^12.2.1",
"@angular/compiler": "^12.2.1",
"@angular/core": "^12.2.1",
"@angular/forms": "^12.2.1",
"@angular/localize": "^12.2.1",
"@angular/material": "^12.2.1",
"@angular/platform-browser": "^12.2.1",
"@angular/platform-browser-dynamic": "^12.2.1",
"@angular/router": "^12.2.1",
"applicationinsights": "^2.1.5",
"applicationinsights-js": "^1.0.20",
"core-js": "^3.16.2",
"html2canvas": "^1.3.2",
"material-icons": "^1.1.1",
"ngx-toastr": "^14.1.0",
"pdfmake": "^0.2.2",
"rxjs": "~7.3.0",
"tslib": "^2.3.1"

},
"devDependencies": {
"@angular-devkit/build-angular": "~12.2.1",
"@angular/cli": "~12.2.1",
"@angular/compiler-cli": "^12.2.1",
"@angular/language-service": "^12.2.1",
"@types/jasmine": "~3.8.2",
"@types/node": "^16.6.1",
"@typescript-eslint/eslint-plugin": "^4.29.2",
"@typescript-eslint/parser": "^4.29.2",
"eslint": "^7.32.0",
"ts-node": "~10.2.0"
}

Ran ng serve  command.
while running ng serve first or second time. I am able to compile the code but when i am trying to run third time and so on, i am getting below error:

(node:10563) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at String.match ()
at OriginalSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/OriginalSource.js:64:32)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at ReplaceSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/ReplaceSource.js:176:44)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at streamAndGetSourceAndMap (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamAndGetSourceAndMap.js:27:53)
at CachedSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/CachedSource.js:208:35)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
at ConcatSource.streamChunks (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/ConcatSource.js:112:55)
at module.exports (/home/soni/Documents/IntelliDish/intellidish-frontend/ddsp/node_modules/webpack/node_modules/webpack-sources/lib/helpers/streamChunks.js:13:17)
(Use node --trace-warnings ... to show where the warning was created)
(node:10563) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10563) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Then i downgraded the "@angular-devkit/build-angular" version to 12.1.2 & post that it was working fine(no error).
Can you please take a look and suggest any solution?

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

We cannot setup a minimal repro. It's a private code, So we cannot share it publicly.

Without a reproduction this cannot be actionable from our end.
A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem, you can omit private code. Another option would be to share you project privately.

Using
-ng serve
-ng build
no problem.
But i will use ng packagr for generate component Maximum call stack size exceeded

This seems to be related to https://github.com/webpack/webpack-sources/issues/131

Closing due to the lack of a reproduction which makes this in-actionable.

@alan-agius4 @Bjeaurn So this is happening to me and we cannot get sourcemaps to work in Angular 12. What should I do? I've commented on the Webpack ticket as well https://github.com/webpack/webpack-sources/issues/131.

Based on https://github.com/webpack/webpack-sources/issues/131 it seems maybe an issue with one of their RegExp.
I recommand that you post a reproduction in the above mentioned issue, otherwise I am afraid that they will be unable to address this issue.

@alan-agius4 Just wanted to let you know that @Bjeaurn and @alexander-akait fixed this issue I believe in webpack/webpack-sources#131 and for anyone else facing this. Simply re-installing the cli got the new code addressed the issue.


Missing check: druid mana in forms

Druids need a check that allows them to check their mana in forms where the power check returns rage or energy.

will use DruidManaLib

done


Fix imported type Auth in app.d.ts in the Username/password example

Since the Auth type is defined in $lib/server/lucia.ts it should be imported from there, because this type in $lib/lucia does not exist.

Thanks!


⚠ Jenkins Plugins Artifactory has degraded performance

In 0caff26, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1282 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 960df4b after 25 minutes.


ComfyUI metadata not being displayed

This is an image I created in ComfyUI.
It shows the workflow when I drop it within the Comfy environment. However, Diffusion Toolkit doesn't display the positive/negative prompt/model/seed etc.
Is this a problem with the image, or is there metadata not being read?

ComfyUI support isn't perfect since every workflow presents a different way of storing where the prompt is.  The two appear to have slightly different workflows. The first one goes through a "CLIPTextEncodeSDXL" node which I don't think I support yet.
To complicate things ComfyUI allows you to set different prompts in different nodes, or with SDXL it has the G/L prompts (which are usually duplicated)

ComfyUI support isn't perfect since every workflow presents a different way of storing where the prompt is. The two appear to have slightly different workflows. The first one goes through a "CLIPTextEncodeSDXL" node which I don't think I support yet.
To complicate things ComfyUI allows you to set different prompts in different nodes, or with SDXL it has the G/L prompts (which are usually duplicated)

Thank you for the clarity! Yes, the first one has a Prompt Styler node that goes through SDXL conditioning. The other one is without a prompt styler node.

Hoenstly, just dumping any metadata that Diffusion Toolkit can't yet parse after being found under the following labels:

Parameters
Prompt
UserComment
Workflow

would be rather helpful.  Maybe toss it into "Others" for those cases.
I currently have many ComfyUI images showing no metadata at all in Diffusion Toolkit (latest major release and even for a recent Dev level), so need to fire up other tools for looking into their metadata.  Even if the raw, unparsed values were put into something like "Others," I could at least visually parse that out without needing to analyze the image through other tools.  Diffusion Toolkit is a highly convenient one-stop-shop for AI image metadata and I'd prefer to stay in that tool when possible.


Files that are claimed to contain errors (but don't) are still changed

I am using the latest stable release:
$ php-cs-fixer --version
PHP CS Fixer 2.8.0 Round Numbers by Fabien Potencier and Dariusz Ruminski (89e7b08)

When I invoke php-cs-fixer for PHPUnit (https://github.com/sebastianbergmann/phpunit/) then I get the following:
$ php-cs-fixer fix
Loaded config default from "/usr/local/src/phpunit/.php_cs".

Fixed all files in 4.629 seconds, 22.000 MB memory used

Files that were not fixed due to errors reported during fixing:
   1) /usr/local/src/phpunit/src/Util/TextTestListRenderer.php
   2) /usr/local/src/phpunit/src/Util/XmlTestListRenderer.php

I have no idea what errors php-cs-fixer thinks these files have. php -l thinks they're fine.
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean

As you can see above, php-cs-fixer did not change any files.
$ php-cs-fixer fix
Loaded config default from "/usr/local/src/phpunit/.php_cs".
Using cache file ".php_cs.cache".
   1) src/Util/TextTestListRenderer.php
   2) src/Util/XmlTestListRenderer.php

Fixed all files in 0.026 seconds, 8.000 MB memory used

However, running php-cs-fixer again changes the files that were reported to contain errors (see above) before:
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   src/Util/TextTestListRenderer.php
	modified:   src/Util/XmlTestListRenderer.php

no changes added to commit (use "git add" and/or "git commit -a")

$ git diff
diff --git a/src/Util/TextTestListRenderer.php b/src/Util/TextTestListRenderer.php
index 4ee6ac769..be1d2c3f7 100644
--- a/src/Util/TextTestListRenderer.php
+++ b/src/Util/TextTestListRenderer.php
@@ -20,7 +20,8 @@ public function render(TestSuite $suite): string
     {
         $buffer = 'Available test(s):' . PHP_EOL;

-        foreach (new \RecursiveIteratorIterator($suite->getIterator()) as $test) {
+        foreach {
+            (new \RecursiveIteratorIterator($suite->getIterator()) as $test) {
             if ($test instanceof TestCase) {
                 $name = \sprintf(
                     '%s::%s',
@@ -39,6 +40,7 @@ public function render(TestSuite $suite): string
             );
         }

-        return $buffer;
+            return $buffer;
+        }
     }
 }
diff --git a/src/Util/XmlTestListRenderer.php b/src/Util/XmlTestListRenderer.php
index 2d758d529..f7a8c2c66 100644
--- a/src/Util/XmlTestListRenderer.php
+++ b/src/Util/XmlTestListRenderer.php
@@ -27,7 +27,8 @@ public function render(TestSuite $suite): string

         $currentTestCase = null;

-        foreach (new \RecursiveIteratorIterator($suite->getIterator()) as $test) {
+        foreach {
+            (new \RecursiveIteratorIterator($suite->getIterator()) as $test) {
             if ($test instanceof TestCase) {
                 if (\get_class($test) !== $currentTestCase) {
                     if ($currentTestCase !== null) {
@@ -71,12 +72,13 @@ public function render(TestSuite $suite): string
             }
         }

-        if ($currentTestCase !== null) {
+            if ($currentTestCase !== null) {
+                $writer->endElement();
+            }
+
             $writer->endElement();
         }

-        $writer->endElement();
-
         return $writer->outputMemory();
     }
 }

$ php -l src/Util/TextTestListRenderer.php
PHP Parse error:  syntax error, unexpected '{', expecting '(' in src/Util/TextTestListRenderer.php on line 23
Errors parsing src/Util/TextTestListRenderer.php

$ php -l src/Util/XmlTestListRenderer.php
PHP Parse error:  syntax error, unexpected '{', expecting '(' in src/Util/XmlTestListRenderer.php on line 30
Errors parsing src/Util/XmlTestListRenderer.php

Now these files contain errors that look similar to #3202.

The fixer tries to change PHP source code without linting errors into code that has linting error (3202 does indeed prove that).
The error message states;

Files that were not fixed due to errors reported during fixing

Which means that; after fixing the fixer found out the result was not valid PHP and therefor does not apply the changes (i.e. not writes back the change to file).
I'll leave 3202 to @julienfalque , however I'm puzzled about why the fixer did apply the second time it was run...

This should be fixed by #3208.

after fixing the fixer found out the result was not valid PHP and therefor does not apply the changes (i.e. not writes back the change to file).

@SpacePossum I tried running the fixer on a project and the same bug occured, but the changes were applied anyway, so no linting check before it seems. Maybe we should keep this issue open despite it's a duplicate of #3202 until we figured out what happens?

Maybe we should keep this issue open [...]until we figured out what happens?

:+1: for keeping this one open to check why the fixer write back code it knows doesn't lint.
Thanks for all the other work on the ticket @julienfalque :)

This reveals to use 2 bugs actually. Fixed in #3208 and #3217 , which just got merged (not yet released).
Thanks @sebastianbergmann


Maximum site collections and policies typo and question

I noticed a typo in the first section of the information, but I also wanted to confirm that the documentation is correct.
Maximum of 10 sites collections across all policies. (Recommendation is to edit this to say '10 site collections' rather than 'sites'
Maximum of 10 policies across your tenant.
The other question I is on the accuracy of these two points. Does this mean the following scenarios would be true?

A tenant can have maximum 10 policies but this would mean that each policy would only allow for 1 site to be specified.
A tenant can have one policy with 10 sites specified within it
A tenant could have 3 policies, the first with 6 sites specified and the 2nd and 3rd with 2 sites each
A tenant could have 4 policies with 2 sites specified within them

If the above statements are true then in summary the auto-apply sensitivity labels is only able to be applied to maximum of 10 site collections within a tenant.
This would mean that organisations have to be very selective about which sites that want to have auto applied labelling to.
Are these assumptions correct.

Hello @AndrewJolly! To which article(s) does your feedback apply? This information will help us route your issue to the correct writer/team.

Sorry i forgot to put the link in:
https://docs.microsoft.com/en-us/microsoft-365/compliance/apply-sensitivity-label-automatically?view=o365-worldwide

@cabailey Please help us and answer this issue. Thanks

@AndrewJolly & @yogkumgit You can leave this with me.  It's wording I inherited and I'm checking with engineering.  It seems "site collection" isn't the correct term to use with SharePoint but what I'm not sure about is whether the limit of 10 sites per policy means 10 site locations (where one SharePoint site can include subsites, if migrated from on-premises for example) or literally 10 sites even if some of these are subsites from the one specified.  If it's literally 10 sites per policy, and you can have 10 policies per tenant, that's a maximum of 100 sites.

@AndrewJolly  Now reworded as "Maximum of 10 auto-labeling policies per tenant, each targeting up to 10 sites (SharePoint or OneDrive)"  Hopefully that is clearer.  I'm told very few customers have subsites for SharePoint Online, but if they do and the top-level site is specified, it's the top-level site only that gets counted (while the subsites are still scanned). You will know when you have reached the limit because the UI will prevent you from entering an 11th entry.


Change self-closing tags to void elements

Hi there - I couldn't find any reports of this in the issues, so hopefully I'm not repeating a previous issue.
Is there any interest to change the behaviour of Mistune to produce void elements instead of self-closing tags? Examples of these are:
,
, or  - these are currently rendered as
,
, or  which is no longer considered to be valid HTML.
From what I can tell, the code that produces this is in mistune/src/mistune/renderers/html.py in the following three places:

image: https://github.com/lepture/mistune/blob/0772c78bc0a62771768278263ef740345f58c0f0/src/mistune/renderers/html.py#L85-L91
linebreak: https://github.com/lepture/mistune/blob/0772c78bc0a62771768278263ef740345f58c0f0/src/mistune/renderers/html.py#L96-L97
thematic_break: https://github.com/lepture/mistune/blob/0772c78bc0a62771768278263ef740345f58c0f0/src/mistune/renderers/html.py#L121-L122

I would be happy to work on this myself and create a pull request, I just wanted to check in with you first to see if you would be willing to accept this?
Cheers - Stuart.

I should note, that I'm already over-riding those three methods in my own custom renderer and appears to work fine. But I see there will be other changes in the code as well as fixing up the tests.
In my custom renderer:
    def image(self, text: str, url: str, title: Optional[str] = None) -> str:
        src = self.safe_url(url)
        alt = escape_text(striptags(text))
        s = '"

    def thematic_break(self) -> str:
        return "
\n"

    def linebreak(self) -> str:
        return "
\n"

Mistune is using test cases from CommonMark https://spec.commonmark.org/0.31.2/ and CommonMark is using self-closing tags.

OK - I'll close this issue. I raised a discussion on the CommonMark forums but have had no response yet.

For now, you can use custom renderer.


NPC dialogue

Hello,
Is there a way of making a dialogue with NPC in a quest?
So that NPC will tell you something and you can respond with answer.
Please help.
Thanks,
-LikeManTV

Answered in #1062


refine UT framework to promote GPU evaluation, Part 1

contributes to https://github.com/NVIDIA/spark-rapids/issues/10850
changes in this PR:

changed the default way to evaluate an expression, taking into consideration that:

bound reference is not well supported
many of RAPIDS' expressions do not accept vectorized parameters

Change default timezone to UTC to promote more expressions being evaluated in GPU

build

build

hi @jlowe can you please review the PR?

build

build

So far all of the comment of this issue is addressed. I'll close this PR and turn to #10861 as it is a superset of this PR


Cannot find detours.h

Cannot find detours.h just gives me an error.......

download it here and put it into the Cobalt/Cobalt folder
then change #include <detours.h>to #include "detours.h"
it worked for me


How do I change the theme?

Doesn't seem like there is an obvious way to do so, unless I'm missing something? Do I have to change some file?

If it is your first run, you must close and reopen.  Then a desktop settings button will appear in the slide out menu.  If it's not your first run it will be there already


STRUCT_MEMBER_ACCESS Add support for using variables inside other variables

In the Wrath MovementBlock the first few fields are identical to the fields of the MovementInfo.
Emulators send an actual MovementInfo but we have to duplicate the fields because we can't reach into the structs.
We want to be able to do
flag A : u8 {
	ONE = 1;
	TWO = 2;
}
flag B : u8 {
	FOUR = 4;
	EIGHT = 8;
}

struct T {
	A a;
}
struct Y {
	T t;
	if (t.a & ONE) {
		u8 one;
	}
}

It is not certain what the generated Rust could should look like.

The motivation for doing this was partly automatically converting to/from MovementInfo and the resulting type that contained a MovementInfo, but this would introduce a very nasty edge case that would only be used for a single thing. Manually writing a conversion function is simpler.


How to type multiple lines for body part?

I was trying to type multiple lines for body part, but when I type the Enter key it moved to footer part, which means that I could only type one line for body part.
So I was wondering how to change lines when typing for the body part.

hey there's no current support for this unfortunately. I will implement something to not escape the new line symbol. It'll be possible to do My body \n is great.
Eventually I'll try to migrate to the new python-prompt-toolkit 2.0.0 and we'll see if it possible to use something like shift + Enter.
Meanwhile you can modify the body with git commit --amend

Well, thank you for reply. I think git commit --amend is a good way of doing this.

As I tested, it seems commitizen doesn't support multiple line input yet.
After reading python-prompt-toolkit::multiline-input, it does not seem to be a good solution to me.
How about implement it like cz-cli?

Provide a LONGER description of the change (optional). Use "|" to break new line:

Seems like a valid option. I'd give it a try, it may not be the best, but it's something to start with


json backup status - offload progress output code

This is the rebase for the new repo layout
This contains the json output status functionality, and possibly a more configurable progress output module.
Referencing issues #1063 and #1160

Codecov Report

Merging #1293 into master will decrease coverage by 5.77%.
The diff coverage is 12.61%.

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

Hey, had a chance to resolve your changes.
Been busy implementing more json functionality with other functions...

Thanks. Can you please remove the merge commit and the commit that fixes the broken merge? Those two don't need to be in the patch set.
Let me know if you need help.

There hasn't been any progress here for the last few weeks so I'm closing this PR. Just leave a comment if you're still interested in continuing the work (or need help), thanks!

Sorry not very well versed with Git as I would like to be so am not sure how to go about updating some of these things. There are other changes I have been making regarding output of JSON information using the client when listing files and other status information.