text:
Flask Issue

Describe the bug
I have been trying to use Error Analysis on my XGBoost Regression model for quite some time now but it seems like I am unlucky when it comes to the dependency issues.
To Reproduce
I cannot install and import raiwidgets onto my Azure ML Notebook. This time it says there's an issue with Flask.
Desktop (please complete the following information):

OS: Microsoft Windows
Browser Chrome
Python version: 3.8
raiwidgets and responsibleai package versions 0.24.0

To get the package versions please run in your command line:
pip show raiwidgets
pip show responsibleai

@dogfood6 could you please post the errors you are seeing when import RAIInsights or RAIDashboard?
what version of flask are you running?  If you create a new compute instance in AzureML Notebook it should have all compatible & verified dependencies that work together with the latest azure-sdk packages.

I guess I am confused on AzureML, I am used to Google Colab.
Would you mind helping me out on a quick call to get raiwidgets working? I would really appreciate it as I have been stuck on this for a few months now.

Here is exactly what happens because when i import raiwidgets it doesnt work.

SystemError                               Traceback (most recent call last)
Cell In[6], line 20
18 import datetime
19 import pickle # to save objects
---> 20 import raiwidgets
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/raiwidgets/init.py:7
4 """Package for the fairness, explanation, and error analysis widgets."""
6 from .version import version
----> 7 from .error_analysis_dashboard import ErrorAnalysisDashboard
8 from .explanation_dashboard import ExplanationDashboard
9 from .fairness_dashboard import FairnessDashboard
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/raiwidgets/error_analysis_dashboard.py:10
8 from .constants import ModelTask
9 from .dashboard import Dashboard
---> 10 from .error_analysis_dashboard_input import ErrorAnalysisDashboardInput
12 DEFAULT_MAX_DEPTH = 3
13 DEFAULT_NUM_LEAVES = 31
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/raiwidgets/error_analysis_dashboard_input.py:11
7 import pandas as pd
9 from erroranalysis._internal.constants import (Metrics, display_name_to_metric,
10                                                metric_to_display_name)
---> 11 from erroranalysis._internal.error_analyzer import (ModelAnalyzer,
12                                                     PredictionsAnalyzer)
13 from erroranalysis._internal.utils import is_spark
14 from raiutils.data_processing import convert_to_list, serialize_json_safe
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/erroranalysis/_internal/error_analyzer/init.py:5
1 # Copyright (c) Microsoft Corporation
2 # Licensed under the MIT License.
4 """Init file, used for backwards compatibility."""
----> 5 from erroranalysis.analyzer import ModelAnalyzer, PredictionsAnalyzer
7 all = ['PredictionsAnalyzer', 'ModelAnalyzer']
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/erroranalysis/analyzer/init.py:5
1 # Copyright (c) Microsoft Corporation
2 # Licensed under the MIT License.
4 """Module for defining the analyzers."""
----> 5 from .error_analyzer import ModelAnalyzer, PredictionsAnalyzer
7 all = ["PredictionsAnalyzer", "ModelAnalyzer"]
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/erroranalysis/analyzer/error_analyzer.py:29
27 from erroranalysis._internal.utils import generate_random_unique_indexes
28 from erroranalysis._internal.version_checker import check_pandas_version
---> 29 from erroranalysis.error_correlation_methods import (
30     compute_ebm_global_importance, compute_gbm_global_importance)
31 from erroranalysis.report import ErrorReport
33 BIN_THRESHOLD = MatrixParams.BIN_THRESHOLD
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/erroranalysis/error_correlation_methods/init.py:7
4 """Module for defining error correlation methods."""
6 from .ebm import compute_ebm_global_importance
----> 7 from .gbm import compute_gbm_global_importance
9 all = ["compute_ebm_global_importance", "compute_gbm_global_importance"]
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/erroranalysis/error_correlation_methods/gbm.py:7
4 """Defines the error correlation computation using LightGBM with TreeShap."""
6 import numpy as np
----> 7 import shap
8 from lightgbm import LGBMClassifier, LGBMRegressor
10 from erroranalysis._internal.constants import ModelTask
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/shap/init.py:12
9 if (sys.version_info < (3, 0)):
10     warnings.warn("As of version 0.29.0 shap only supports Python 3 (not 2)!")
---> 12 from ._explanation import Explanation, Cohorts
14 # explainers
15 from .explainers._explainer import Explainer
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/shap/_explanation.py:12
10 from slicer import Slicer, Alias, Obj
11 # from ._order import Order
---> 12 from .utils._general import OpChain
13 from .utils._exceptions import DimensionError
15 # slicer confuses pylint...
16 # pylint: disable=no-member
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/shap/utils/init.py:1
----> 1 from ._clustering import hclust_ordering, partition_tree, partition_tree_shuffle, delta_minimization_order, hclust
2 from ._general import approximate_interactions, potential_interactions, sample, safe_isinstance, assert_import, record_import_error
3 from ._general import shapley_coefficients, convert_name, format_value, ordinal_str, OpChain, suppress_stderr
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/shap/utils/_clustering.py:4
2 import scipy as sp
3 from scipy.spatial.distance import pdist
----> 4 from numba import jit
5 import sklearn
6 import warnings
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/numba/init.py:42
38 from numba.core.decorators import (cfunc, generated_jit, jit, njit, stencil,
39                                    jit_module)
41 # Re-export vectorize decorators and the thread layer querying function
---> 42 from numba.np.ufunc import (vectorize, guvectorize, threading_layer,
43                             get_num_threads, set_num_threads)
45 # Re-export Numpy helpers
46 from numba.np.numpy_support import carray, farray, from_dtype
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/numba/np/ufunc/init.py:3
1 # -- coding: utf-8 --
----> 3 from numba.np.ufunc.decorators import Vectorize, GUVectorize, vectorize, guvectorize
4 from numba.np.ufunc._internal import PyUFunc_None, PyUFunc_Zero, PyUFunc_One
5 from numba.np.ufunc import _internal, array_exprs
File /anaconda/envs/azureml_py310_sdkv2/lib/python3.10/numba/np/ufunc/decorators.py:3
1 import inspect
----> 3 from numba.np.ufunc import _internal
4 from numba.np.ufunc.parallel import ParallelUFuncBuilder, ParallelGUFuncBuilder
6 from numba.core.registry import DelayedRegistry
SystemError: initialization of _internal failed without raising an exception

Python 3.8 AzureML
this is the code i am running
_###############
Libraries
###############
import pandas as pd # manipulate data
import numpy as np # calculate the mean and standard deviation
import sklearn
from scipy.stats import stats, randint
import random
from sklearn import preprocessing
from sklearn.model_selection import GridSearchCV, cross_val_score, learning_curve # cross validation and tuning
from sklearn.model_selection import train_test_split # split  data into training and testing sets
from sklearn.metrics import r2_score, mean_squared_error, mean_absolute_error
import xgboost as xgb # XGBoost
from xgboost.sklearn import XGBRegressor
import itertools
import matplotlib.pyplot as plt
import seaborn as sns; sns.set()
import datetime
import pickle # to save objects
import raiwidgets_
WARNING:root:'PYARROW_IGNORE_TIMEZONE' environment variable was not set. It is required to set this environment variable to '1' in both driver and executor sides if you use pyarrow>=2.0.0. pandas-on-Spark will set it for you but it does not work if there is a Spark context already launched.
AttributeError                            Traceback (most recent call last)
Cell In[2], line 20
18 import datetime
19 import pickle # to save objects
---> 20 import raiwidgets
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/raiwidgets/init.py:7
4 """Package for the fairness, explanation, and error analysis widgets."""
6 from .version import version
----> 7 from .error_analysis_dashboard import ErrorAnalysisDashboard
8 from .explanation_dashboard import ExplanationDashboard
9 from .fairness_dashboard import FairnessDashboard
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/raiwidgets/error_analysis_dashboard.py:10
8 from .constants import ModelTask
9 from .dashboard import Dashboard
---> 10 from .error_analysis_dashboard_input import ErrorAnalysisDashboardInput
12 DEFAULT_MAX_DEPTH = 3
13 DEFAULT_NUM_LEAVES = 31
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/raiwidgets/error_analysis_dashboard_input.py:11
7 import pandas as pd
9 from erroranalysis._internal.constants import (Metrics, display_name_to_metric,
10                                                metric_to_display_name)
---> 11 from erroranalysis._internal.error_analyzer import (ModelAnalyzer,
12                                                     PredictionsAnalyzer)
13 from erroranalysis._internal.utils import is_spark
14 from raiutils.data_processing import convert_to_list, serialize_json_safe
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/erroranalysis/_internal/error_analyzer/init.py:5
1 # Copyright (c) Microsoft Corporation
2 # Licensed under the MIT License.
4 """Init file, used for backwards compatibility."""
----> 5 from erroranalysis.analyzer import ModelAnalyzer, PredictionsAnalyzer
7 all = ['PredictionsAnalyzer', 'ModelAnalyzer']
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/erroranalysis/analyzer/init.py:5
1 # Copyright (c) Microsoft Corporation
2 # Licensed under the MIT License.
4 """Module for defining the analyzers."""
----> 5 from .error_analyzer import ModelAnalyzer, PredictionsAnalyzer
7 all = ["PredictionsAnalyzer", "ModelAnalyzer"]
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/erroranalysis/analyzer/error_analyzer.py:22
20 from erroranalysis._internal.metrics import metric_to_func
21 from erroranalysis._internal.process_categoricals import process_categoricals
---> 22 from erroranalysis._internal.surrogate_error_tree import
23     compute_error_tree as _compute_error_tree
24 from erroranalysis._internal.surrogate_error_tree import
25     compute_error_tree_on_dataset as _compute_error_tree_on_dataset
26 from erroranalysis._internal.utils import generate_random_unique_indexes
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/erroranalysis/_internal/surrogate_error_tree.py:9
7 import numpy as np
8 import pandas as pd
----> 9 from lightgbm import Booster, LGBMClassifier, LGBMRegressor
10 from sklearn.metrics import (mean_absolute_error, mean_squared_error,
11                              median_absolute_error, r2_score)
13 from erroranalysis._internal.cohort_filter import filter_from_cohort
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/lightgbm/init.py:8
2 """LightGBM, Light Gradient Boosting Machine.
3
4 Contributors: https://github.com/microsoft/LightGBM/graphs/contributors.
5 """
6 import os
----> 8 from .basic import Booster, Dataset, register_logger
9 from .callback import early_stopping, print_evaluation, record_evaluation, reset_parameter
10 from .engine import CVBooster, cv, train
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/lightgbm/basic.py:17
14 import numpy as np
15 import scipy.sparse
---> 17 from .compat import PANDAS_INSTALLED, concat, dt_DataTable, is_dtype_sparse, pd_DataFrame, pd_Series
18 from .libpath import find_lib_path
21 class _DummyLogger:
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/lightgbm/compat.py:115
113 from dask import delayed
114 from dask.array import Array as dask_Array
--> 115 from dask.dataframe import DataFrame as dask_DataFrame
116 from dask.dataframe import Series as dask_Series
117 from dask.distributed import Client, default_client, wait
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/dask/dataframe/init.py:3
1 try:
2     from ..base import compute
----> 3     from . import backends, dispatch, rolling
4     from .core import (
5         DataFrame,
6         Index,
(...)
12         to_timedelta,
13     )
14     from .groupby import Aggregation
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/dask/dataframe/backends.py:17
15 from ..utils import is_arraylike, typename
16 from ._compat import PANDAS_GT_100
---> 17 from .core import DataFrame, Index, Scalar, Series, _Frame
18 from .dispatch import (
19     categorical_dtype_dispatch,
20     concat,
(...)
30     union_categoricals_dispatch,
31 )
32 from .extensions import make_array_nonempty, make_scalar
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/dask/dataframe/core.py:56
36 from ..utils import (
37     IndexCallable,
38     M,
(...)
53     typename,
54 )
55 from . import methods
---> 56 from .accessor import DatetimeAccessor, StringAccessor
57 from .categorical import CategoricalAccessor, categorize
58 from .dispatch import (
59     get_parallel_type,
60     group_split_dispatch,
61     hash_object_dispatch,
62     meta_nonempty,
63 )
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/dask/dataframe/accessor.py:109
98     """Accessor object for datetimelike properties of the Series values.
99
100     Examples
(...)
103     >>> s.dt.microsecond  # doctest: +SKIP
104     """
106     _accessor_name = "dt"
--> 109 class StringAccessor(Accessor):
110     """Accessor object for string properties of the Series values.
111
112     Examples
(...)
115     >>> s.str.lower()  # doctest: +SKIP
116     """
118     _accessor_name = "str"
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/dask/dataframe/accessor.py:121, in StringAccessor()
118 _accessor_name = "str"
119 _not_implemented = {"get_dummies"}
--> 121 @derived_from(pd.core.strings.StringMethods)
122 def split(self, pat=None, n=-1, expand=False):
123     if expand:
124         if n == -1:
AttributeError: module 'pandas.core.strings' has no attribute 'StringMethods'

FINALLY GOT IT FIXED SORRY FOR BOTHERING

@dogfood6 great to hear that it is resolved - if you are still having issues, please let us know.  I would be happy to get on a Teams call (or your preferred meeting software).  I can send you the Teams meeting invite next time if you run into any issues and we can schedule a debugging session.

repo: microsoft/responsible-ai-toolbox


text:
Fix demo_server should using http instead of https

close https://github.com/microsoft/restler-fuzzer/issues/699

Thank you for the fix!

source: gharchive/pull-request

authors: leonasdev marina-p

repo: microsoft/restler-fuzzer

license: MIT

license_type: permissive

license_source: github-api


text:
fix: annotation tag in documentation

Description
Annotation in this page is different than here and it does not work correctly.
Related Issue
If this pull request is related to any issue, please mention it here. Additionally, make sure that the issue is assigned to you before submitting this pull request.
Checklist

[ ] I have read the contributing documentation.
[ ] I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
[ ] I have correctly attributed the author(s) of the code.
[ ] I have tested the changes locally.
[ ] I have followed the project's style guidelines.
[ ] I have updated the documentation, if necessary.
[ ] I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed
Please add any relevant screenshots or GIFs to showcase the changes made.
Additional Notes
Add any additional notes or context about the pull request here.

Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

Happy to approve this if it reflects reality. Although we should think if we should deprecate this usage and change the annotation to include the v1aplha part. @anubhabMajumdar ? What do you think?

Approved the PR since the usage has change to retina.sh=observe. I think the usage was updated so that it's not API version dependent.

authors: alexcastilio anubhabMajumdar

repo: microsoft/retina


text:
Consider some type of "warning" for incorrect or out of date information.

When parsing and displaying information from a SARIF log, there are a number of things that the extension code is doing that "skips" information in the log that "violates" the spec. One example of this is the end line for a location being less than the start line.
Another example, which probably has more impact to the end user, is the source file (physical location URI) being referenced by the SARIF log has been edited before the log is parsed. This can cause any location (line, column) information in the SARIF log to be incorrect.
So there are two aspects to this.. As a SARIF generator (tool developer), you'd like to know about issues in the SARIF your tool is generating. As a SARIF consumer (a developer running static analysis), you would like to be aware that the analysis results you are looking at may not be accurate.

Jeff and Henok believe we should drop invalid Sarif and not notify customer. However should send signal of Sarif tool owner.

Extension should validate SARIF beforehand

source: gharchive/issue

authors: ArlenTokatlian GabeDeBacker mpande98

repo: microsoft/sarif-visualstudio-extension


text:
Delete most of the Scalar product code

Draft only because I'm not sure if this will pass tests. The biggest unknown is whether or not the microsoft/git installer will still be downloaded during functional tests, which is the only reason the Scalar, Scalar.Common, and Scalar.MSBuild projects still exist.
Based on #505 because we need to point to main to trigger the workflows.

@derrickstolee you should be able to delete the signing and MSBuild projects too.. they're only used for signing and generating code for the non-existent product respectively 😁

@derrickstolee you should be able to delete the signing and MSBuild projects too.. they're only used for signing and generating code for the non-existent product respectively 😁

@mjcheetham: I'm worried that without it I won't get anything that downloads the microsoft/git package, but I'll give it a try.

@derrickstolee you should be able to delete the signing and MSBuild projects too.. they're only used for signing and generating code for the non-existent product respectively 😁

@mjcheetham: I'm worried that without it I won't get anything that downloads the microsoft/git package, but I'll give it a try.

The obvious thing of deleting the project failed, so I'm going to leave that one to another PR (if at all) because it's not as simple as the other projects.

I'm rubber stamping this. I looked thru things and it all looks good. I'm not sure what's happening with the builds failing on 1 machine and/or the signing thing.

In my opinion, our functional tests are a little more flaky in the C port, so we will want to resolve some of those issues in the coming weeks.

our functional tests are a little more flaky in the C port

I fear you are right. My take on it is that it was my mistake to rely on the global config so much. In typical usage scenarios, this does not matter: users do not concurrently register a dozen enlistments. But the Functional Tests do.
To some extent, the problem was alleviated by my patch that asks for a back-off strategy to be used when creating that write lock.
I expect the remaining problems to be rooted in the lack of a read lock. That is, when we read the global Git config, we do not expect there to be any problems.
And those problems would only occur on Windows, anyway: on Linux/macOS, the rename() that commits the write lock is atomic. Either you get the old, or you get the new version of the config.
In contrast, on Windows there is the potential that a different process is holding a lock on that file (I still suspect Defender to interfere here, but it could potentially be the MoveFilesExW() call that might not be lock-free).
My best guess is that we should actually implement a back-off strategy with a very short time-out in mingw_open() and mingw_fopen(). It could be either modeled after the strategy in lock_file_timeout(), or even preferable: we should attempt to refactor that strategy into a reusable form and use that. I could imagine something like this:
struct back_off_t back_off;

back_off_init(&back_off, time_out_ms);
do {
  file = _wfreopen(wfilename, wotype, stream);
  if (file || errno != EPERM)
    break;
} while (back_off_sleep(&back_off));

This is still a bit clunky, and could potentially be wrapped in a macro, somewhat similar to how SWAP() is implemented.
I left this idea in a comment at https://github.com/github/git-client/issues/457#issuecomment-863032560

our functional tests are a little more flaky in the C port

I fear you are right. My take on it is that it was my mistake to rely on the global config so much. In typical usage scenarios, this does not matter: users do not concurrently register a dozen enlistments. But the Functional Tests do.
To some extent, the problem was alleviated by my patch that asks for a back-off strategy to be used when creating that write lock.
I expect the remaining problems to be rooted in the lack of a read lock. That is, when we read the global Git config, we do not expect there to be any problems.
And those problems would only occur on Windows, anyway: on Linux/macOS, the rename() that commits the write lock is atomic. Either you get the old, or you get the new version of the config.
In contrast, on Windows there is the potential that a different process is holding a lock on that file (I still suspect Defender to interfere here, but it could potentially be the MoveFilesExW() call that might not be lock-free).
My best guess is that we should actually implement a back-off strategy with a very short time-out in mingw_open() and mingw_fopen(). It could be either modeled after the strategy in lock_file_timeout(), or even preferable: we should attempt to refactor that strategy into a reusable form and use that. I could imagine something like this:
struct back_off_t back_off;

back_off_init(&back_off, time_out_ms);
do {
  file = _wfreopen(wfilename, wotype, stream);
  if (file || errno != EPERM)
    break;
} while (back_off_sleep(&back_off));

This is still a bit clunky, and could potentially be wrapped in a macro, somewhat similar to how SWAP() is implemented.

authors: derrickstolee dscho mjcheetham

repo: microsoft/scalar


text:
Java: TimeSkill implementation

Implement the time skill

https://github.com/microsoft/semantic-kernel/pull/1627

repo: microsoft/semantic-kernel


text:
Maximize icon should be rounded

Windows Terminal version
1.13.10333.0
Windows build number
No response
Other Software
No response
Steps to reproduce
In our latest update to Preview, we added the snap assist functionality to the min/max/close control. Along with this and moving towards the Windows 11 styling, we should also make the maximize icon a rounded square.
Expected Behavior
It should look something like this (taken from PowerPoint):

Actual Behavior
Currently it looks like this:

Looks fixed in 1.13.10395.0

(top is Windows Terminal, bottom is PowerPoint)

👀
I'm pretty sure we didn't actually do anything to fix this yet:

authors: cinnamon-msft zadjii-msft zamadatix

repo: microsoft/terminal


text:
Console "Discard Old Duplicates" doesn't apply in Windows Terminal

Windows Terminal version
1.14.1861.0
Windows build number
10.0.19043.1826
Other Software
No response
Steps to reproduce

Open a legacy "Command Prompt" console;

From the window menu (top-right icon) select "Defaults";

Check "Discard Old Duplicates" in the "Command History" options group, and "OK" to apply;

Open a "Command Prompt" in Windows Terminal, and enter commands in succession:
dir
dir /b
dir
dir /b
dir
dir /b

Expected Behavior
The command buffer should discard previous duplicate entries, as I'm seeing in a legacy "Command Prompt" console – pressing F7 reveals:

Actual Behavior
The "Command Prompt" in Windows Terminal doesn't appear to honor the "Discard Old Duplicates" setting – pressing F7 reveals:

This often causes the inconvenience of losing previous command history, after repeating a few of the same commands in succession for some time.

More details – if I repeat just the same last command, it doesn't get multiplied to the end of the command history:
>dir
>dir /b
>dir
>dir
>dir

F7 (doskey /?):
┌────────────────────────────────────────┐
│0: dir                                  │
│1: dir /b                               │
│2: dir                                  │
│                                        │
│                                        │
│                                        │
│                                        │
│                                        │
│                                        │
│                                        │
└────────────────────────────────────────┘

So it is likely a half-baked port of the original "Discard Old Duplicates" implementation.
My workflow involves repeating 2-3 commands (build, deploy, cls) for some time.  After that, I want to quickly select and execute some other command(s) I've executed previously.  The current behavior breaks it for me.

This is probably another face of #2558. When run in ConPTY (read: the terminal), the console just ignores most settings. That might have been a mis-play. We may want to keep around the history settings, but just ignore the "appearance" ones.
Ultimately, this has the same root cause as that issue, so I'm gonna close it as a dupe for bookkeeping purposes. Thanks!
/dup #2558

Just want to clarify my problem is not that the Windows Terminal doesn't appear to obey the "Discard Old Duplicates" option.  It appears to implement some form of it – "discards" just the last command if it matches the previous one.  It might be doing it by default, not obeying the original setting (haven't verified explicitly) but this issue is about not matching the original "Discard Old Duplicates" behavior.  I suspect even if the setting is read from the Console, the Terminal behavior might still be left broken (at least for me).

Yeah, I think this one is worth tracking. Even in its default configuration (read: enabled) it doesn't do what it says on the tin.

Frick, sorry, I didn't fix the tags and the bot went wild.

authors: DHowett stanio zadjii-msft


text:
WT Canary crash when opening Settings

Windows Terminal version
1.22.2141.0
Windows build number
26120.1330
Other Software
No response
Steps to reproduce
Open "Settings"
Expected Behavior
No response
Actual Behavior
crash
crash.txt

Thanks! Looks like the compiler bug is still around after all.

Fixed in #17653

authors: Andarwinux DHowett


text:
Fix unbinding keys in v0.10

Summary of the Pull Request
We (the royal "we") broke key unbinding in #4746. We didn't run the local tests after this, which actually would have caught this. The comment even suggests what we should have done here. We need to make sure that when we bail, it's because there's a parsing function that returned nothing. null, "unbound", etc actually don't even have a parsing function at all, so they should just keep on keepin' on.
References
Source of this regression: #4746
PR Checklist

[x] Closes #3729
[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments
This is a great example of why your unittests should run in CI always
Validation Steps Performed

ran the tests
tested the following unbindings:

        { "command": null, "keys": [ "ctrl+shift+t" ] },
        { "command": "unbound", "keys": [ "ctrl+shift+t" ] },
        { "command": "null", "keys": [ "ctrl+shift+t" ] },

and they each individually worked.

I am looking in the code and I can't find a workaround for the issue. I just updated and all my unbound bindings are broken. Is there a temp solution for this until the this PR lands in future build?

I don't think there's a workaround for the moment unfortunately. I'd bet good money that this PR gets merged and hotfix build pushed out ASAP (when the rest of the team wakes up 😜)

Welp, I guess I will wait for the next update then :) Thanks for the quick response.

When you merge this one please do it manually: the bot has trouble with the title when there’s only a single commit in the pull request. It uses the commit title instead of the pr

Is there an ETA for a release of this particular fix? Terminal is kinda unusable for me since 0.10 ...

This is probably a good time to mention that many of the default keybindings interfere with popular Linux applications, which I find odd given the emphasis on support of WSL.  This regression probably wouldn't be such an impediment if key combinations that send unique ANSI codes were avoided in keybindings.
Is this an area where you'd be open to feedback in a new issue?  I may be able to provide some advice as to what's safe and what isn't.  I don't think there's really any authoritative or complete documentation floating around on the internet, unfortunately.

@ondras It should be coming out soontm, whenever the store gets around to pushing packages out.

@Zenexer I'd say this pull request is not the place for that discussion. I'd recommend filing a new issue for that discussion.

@zadjii-msft Thanks; I was just asking whether it'd even be worth filing an issue.  I'll do some research and open one.
@ondras If you don't want to wait for the store, an installer that includes this was just released on GitHub: https://github.com/microsoft/terminal/releases

That build is also available in the store as of 8:00 PDT. :)

authors: DHowett-MSFT Zenexer int3l ondras zadjii-msft


text:
Add support for passing in arguments for methods used to store dynamic data

Summary

Hello team, hope you're all well. I'd like to request for a feature to be able to pass in arguments to methods used for storing dynamic data.
Background and Motivation
I was working on some complicated test scenarios with many variations and found myself having to write methods that are almost identical to each other for generating a list of list of N booleans:
For example:
private static IEnumerable<object[]> GenerateBoolListWith3Flags()
{
    bool[] boolArray = new bool[] { true, false };

    var testData = new List<object[]>();

    foreach (var flag0 in boolArray)
    {
        foreach (var flag1 in boolArray)
        {
            foreach (var flag2 in boolArray)
            {
                testData.Add(new object[] { flag0, flag1, flag2 });
            }
        }
    }

    return testData;
}

private static IEnumerable<object[]> GenerateBoolListWith6Flags()
{
    bool[] boolArray = new bool[] { true, false };

    var testData = new List<object[]>();

    foreach (var flag0 in boolArray)
    {
        foreach (var flag1 in boolArray)
        {
            foreach (var flag2 in boolArray)
            {
                foreach (var flag3 in boolArray)
                {
                    foreach (var flag4 in boolArray)
                    {
                        foreach (var flag5 in boolArray)
                        {
                            testData.Add(new object[] { flag0, flag1, flag2, flag3, flag4, flag5 });
                        }
                    }
                }
            }
        }
    }

    return testData;
}

Then use it as follows:
[TestMethod]
[DynamicData(nameof(GenerateBoolListWith3Flags), DynamicDataSourceType.Method)]
public void Test1(
    bool flag0,
    bool flag1,
    bool flag2)
{
    ...
}

[TestMethod]
[DynamicData(nameof(GenerateBoolListWith6Flags), DynamicDataSourceType.Method)]
public void Test2(
    bool flag0,
    bool flag1,
    bool flag2,
    bool flag3,
    bool flag4,
    bool flag5)
{
    ...
}

If I happen to have a bunch of tests with many different numbers of bool parameters for different test variations, then I currently am writing a bunch of GenerateBoolListWith*Flags methods.
I was hoping to refactor and combine the dynamic data source methods into one, but I realized I can only achieve this if I am able to pass in an argument

Proposed Feature

A new attribute such as DynamicDataMethodArgumentAttribute:
[TestMethod]
[DynamicData(nameof(GenerateBoolListWithNFlags), DynamicDataSourceType.Method)]
[DynamicDataMethodArgument(3)]
public void Test1(
    bool flag0,
    bool flag1,
    bool flag2)
{
    ...
}

[TestMethod]
[DynamicData(nameof(GenerateBoolListWithNFlags), DynamicDataSourceType.Method)]
[DynamicDataMethodArgument(6)]
public void Test2(
    bool flag0,
    bool flag1,
    bool flag2,
    bool flag3,
    bool flag4,
    bool flag5)
{
    ...
}

private static IEnumerable<object[]> GenerateBoolListWithNFlags(int n)
{
    bool[] boolArray = new bool[] { true, false };

    var testData = new List<object[]>();

    // Generate test data with n elements per row

    return testData;
}

I understand this may be a very specific usecase, but I think it may also be useful if we somehow want to change up the dynamic data returned depending on passed arguments.
Please let me know if there are any workarounds, other suggestions, or if this is feasible. Thank you!
Alternative Designs

n/a

Hi @cdepano,
Thanks for the suggestion! It indeed looks like an interesting feature.
We need to investigate how we want to implement it (e.g. how many arguments, what type, does it fit the ITestDataSource mode etc).

NUnit has a similar inline approach to this, with [Values] and [Combinatorial].
With those features Test2 can in NUnit be written as:
[Test, Combinatorial]
public void Test2(
    [Values] bool flag0,
    [Values] bool flag1,
    [Values] bool flag2,
    [Values] bool flag3,
    [Values] bool flag4,
    [Values] bool flag5)
{
    ...
}

I think @cdepano was referring to something like ParameterizedSourceExampleFixture in NUnit doc https://docs.nunit.org/articles/nunit/writing-tests/attributes/testcasesource.html

authors: Evangelink cdepano jnyrup

repo: microsoft/testfx


text:
Generic overloads for CollectionAssert

Motivation
I have been using CollectionAssert for quite some time but when I want to check whether the contents of a ReadOnlyCollection<T> match my expectation a cannot use CollectionAssert because many generic collection interfaces do not inherit from ICollection.
Proposal
Add new generic overloads of all methods to take IReadOnlyCollection<T> or IEnumerable<T> instead of ICollection.

Hi, thanks for the proposal.
If you're up for it, we are open for community PR's.

Because of some difficulties described in #990, I will not continue to work on this issue and migrate my unit tests to Xunit instead.

authors: Haplois daniel-lerch


text:
Less strict parsing for @param tags

@pgonzal and I were talking in an email thread about parsing params in api-extractor/tsdoc, and suggested I log an issue here to track the param parsing concerns.
Goals for param parsing should be;

Public exported classes/functions have correct jsdoc comments describing the thing.
If param comments are missing, api-extractor catches them and throws an error.
If params are out of order, also worthy of throwing an error.
If the params have types in them, api-extractor ignores them and parses the types from typescript typings if available.
If the params have dashes in them, api-extractor ignores the dashes. If they are missing dashes, api-extractor ignores that. (The purpose is to extract the docs and api surface, not be nit picky about unimportant things, especially when VSCode jsdoc formatting defaults to having types AND no dashes.)

Examples that should work:
  /**
   * @param foo This is fine.
   * @param foo {boolean} This is fine.
   * @param foo - This is fine.
   * @param foo {boolean} - This is fine.
   * @param foo - {boolean} This is fine.
   */

It is nice to stay consistent with param documentation, but the tools should also be resilient in the parsing and let formatting cleanup be the duty of tools like Prettier.
There might be a strict mode which enforces the VSCode default jsdoc comments. but please do not deviate from what most other open source projects snap to (the second example above.)
See Airbnb specs for their guidance as an example. Look at React jsdoc comments. etc
https://github.com/airbnb/javascript#comments

If param comments are missing, api-extractor catches them and throws an error.

This might be a little overly strict.  Consider this example:

/** Represents a 2D vector. */
public class Vector {
  /** The first component of the vector */
  public x: number;
  /** The second component of the vector */
  public y: number;

  /**
   * Constructs a new instance of the `Vector` class
   * @param x - the first component of the vector
   * @param y - the second component of the vector
   */
  public constructor(x: number, y: number) {
  }
}

Would we really want to insist that the person write this @param documentation for the constructor?  I recall that the old MSDN was fairly dogmatic about this, however this documentation clearly doesn't convey any useful information.  Although I'm personally a big advocate of documentation, I tend to be wary of practices that encourage people to think of commenting as an empty formalism or "going through the motions." When we author docs, we should always be thinking about the audience, what questions they will have, and how our content will help them.

If params are out of order, also worthy of throwing an error.

Hmm... I hadn't thought of that one.  Tools like API Extractor could normalize this automatically when they generate the .d.ts files, but yeah, I can see the value of doing this in the source code.

If the params have types in them, api-extractor ignores them and parses the types from typescript typings if available.
If the params have dashes in them, api-extractor ignores the dashes. If they are missing dashes, api-extractor ignores that. (The purpose is to extract the docs and api surface, not be nit picky about unimportant things, especially when VSCode jsdoc formatting defaults to having types AND no dashes.)

Agreed.  My motivation for being strict about parsing @param tags was to protect against mistakes. But you have a fair point that the documentation tool itself already needs to match the parameter name against the function arguments, so for example if @param This is not fine incorrectly interprets "This" as a parameter name, it will still get caught during matching.
I'll point out that today the @microsoft/tsdoc library only looks at comments --  it has no idea what the function parameters are, or even whether the comment is for a class or function etc.  When the dust settles on API Extractor 7, I'd like to consider whether it would be useful to provide some context to @microsoft/tsdoc so that we can move some of this logic down into the library.

See Airbnb specs for their guidance as an example.

Hrmmm... the example you linked to doesn't use @param at all.  It might not be the best example of a modern style guide any more: 😋
// good
/**
 * make() returns a new element
 * based on the passed-in tag name
 */
function make(tag) {

  // ...

  return element;
}

Oops on the link; edited above and replaced with a jsdoc one that's more applicable.

This might be a little overly strict.

I should have worded that better; i was thinking more about "if you provide comments for one param, you should provide them for all". Or, if someone modifies a signature but the comments don't match (e.g. they're out of order, some are unrecognized or missing) then that could be caught. Totally agree we definitely don't want it to be frictiony by erroring on things that are not useful to correct. :)

This still seems to be an issue for @typeParam, without the hyphen it fails to parse the parameter name for the tag.

I tagged it for follow up. If it's easy maybe I can tackle this in the next round of work on the parser.

Locally I wrote a patch for NodeParser.prototype._parseParamBlock in JS to partially address this case:
    var hyphenExcerpt;
    var spacingAfterHyphenExcerpt;
    if (tokenReader.peekTokenKind() === Token_1.TokenKind.Hyphen) {
        tokenReader.readToken();
        hyphenExcerpt = tokenReader.extractAccumulatedSequence();
        // TODO: Only read one space
        spacingAfterHyphenExcerpt = this._tryReadSpacingAndNewlines(tokenReader);
    }
    else if (tokenReader.peekTokenKind() !== Token_1.TokenKind.AsciiWord) {
        tokenReader.backtrackToMarker(startMarker);
        this._parserContext.log.addMessageForTokenSequence("tsdoc-param-tag-missing-hyphen" /* ParamTagMissingHyphen */, 'The @param block should be followed by a parameter name and then a hyphen', docBlockTag.getTokenSequence(), docBlockTag);
        return new nodes_1.DocParamBlock({
            configuration: this._configuration,
            blockTag: docBlockTag,
            parameterName: ''
        });
    }

Essentially, it allows @typeParam T this is a comment (or @param p this is a comment), but it doesn't yet permit @typeParam T {constraint} comment (or @param p {type} comment).

I formalized my patch above and added additional parsing support for {type} and [name]/[name=default] syntax in a PR at #206.

This fix was published with TSDoc 0.12.18.  Thanks @rbuckton for making the PR!

authors: dzearing octogonz pgonzal rbuckton

repo: microsoft/tsdoc


text:
Ignore already escaped | when building markdown table

Fix CodeQL issue https://github.com/microsoft/typespec/security/code-scanning/13

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/3281/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/3281/

authors: azure-sdk timotheeguerin

repo: microsoft/typespec


text:
Cleanup ci pipeline

Pull Request
Title
Cleanups up CI pipeline to just use the pre-commit hooks.

Description
Discussed in #89, this commit consolidates the CI pipelines to run the same things that are run locally.
Additionally, we consolidate the docs to allow us to change those commits in future PRs without quite so much to keep track of.

Type of Change

🔄 Refactor
📝 Documentation update
🧪 Tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.86%. Comparing base (4833588) to head (be7d8f4).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #92   +/-   ##
=======================================
  Coverage   76.86%   76.86%
=======================================
  Files          23       23
  Lines        1059     1059
  Branches      132      132
=======================================
  Hits          814      814
  Misses        195      195
  Partials       50       50

Flag
Coverage Δ

unittests
76.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: bpkroth codecov-commenter

repo: microsoft/vasim


text:
Error: Building package libepoxy:x64-windows failed with: BUILD_FAILED

Describe the bug
A clear and concise description of what the bug is.
Environment

OS: [e.g. Windows.]
Compiler: visual studio community 2019

To Reproduce
Steps to reproduce the behavior:

./vcpkg install gtk:x64-windows
See error
Repro code when

Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
C:\Users\L\Downloads\Compressed\vcpkg-master>vcpkg install gtk:x64-windows
Computing installation plan...
The following packages will be built and installed:
gtk[core]:x64-windows

harfbuzz[core,glib]:x64-windows
libepoxy[core]:x64-windows
pango[core]:x64-windows
ragel[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/5: libepoxy:x64-windows
Building package libepoxy[core]:x64-windows...
-- Using cached C:/Users/L/Downloads/Compressed/vcpkg-master/downloads/anholt-libepoxy-1.5.3.tar.gz
-- Using source at C:/Users/L/Downloads/Compressed/vcpkg-master/buildtrees/libepoxy/src/1.5.3-d7b9d32fcb
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
-- Configuring x64-windows-dbg done
-- Configuring x64-windows-rel
-- Configuring x64-windows-rel done
-- Package x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" install -v
Working Directory: C:/Users/L/Downloads/Compressed/vcpkg-master/buildtrees/libepoxy/x64-windows-rel
Error code: 1
See logs for more information:
C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\package-x64-windows-rel-out.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_install_meson.cmake:19 (vcpkg_execute_required_process)
ports/libepoxy/portfile.cmake:16 (vcpkg_install_meson)
scripts/ports.cmake:90 (include)
Error: Building package libepoxy:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: libepoxy:x64-windows
Vcpkg version: 2020.02.04-nohash
Additional context
Add any other context about the problem here.
Additionally, attach any relevant sections from the log files above

@xiaoxi-li Please attach or upload the log file C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\package-x64-windows-rel-out.log to assist in diagnosing the issue.
Thank you.

@ xiaoxi-li请附加或上传日志文件**C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\package-x64-windows-rel-out.log**以帮助诊断问题。
谢谢。
This is the log file:package-x64-windows-rel-out.log,thank you for your reply!
[1/28] "C:/Users/L/Downloads/Compressed/vcpkg-master/downloads/tools/python/python-3.7.3-x64/python.exe" "../src/1.5.3-d7b9d32fcb/src/gen_dispatch.py" "--header" "--no-source" "--outputdir=include/epoxy" "../src/1.5.3-d7b9d32fcb/registry/wgl.xml"
[2/28] "C:/Users/L/Downloads/Compressed/vcpkg-master/downloads/tools/python/python-3.7.3-x64/python.exe" "../src/1.5.3-d7b9d32fcb/src/gen_dispatch.py" "--source" "--no-header" "--outputdir=src" "../src/1.5.3-d7b9d32fcb/registry/wgl.xml"
[3/28] "C:/Users/L/Downloads/Compressed/vcpkg-master/downloads/tools/python/python-3.7.3-x64/python.exe" "../src/1.5.3-d7b9d32fcb/src/gen_dispatch.py" "--header" "--no-source" "--outputdir=include/epoxy" "../src/1.5.3-d7b9d32fcb/registry/gl.xml"
[4/28] cl @"test/9f86d08@@misc defines@exe/miscdefines.c.obj".rsp
[5/28] cl @"test/9f86d08@@header guards@exe/headerguards.c.obj".rsp
[6/28] cl @"test/9f86d08@@khronos typedefs@exe/khronos_typedefs.c.obj".rsp
[7/28] "C:/Users/L/Downloads/Compressed/vcpkg-master/downloads/tools/python/python-3.7.3-x64/python.exe" "../src/1.5.3-d7b9d32fcb/src/gen_dispatch.py" "--source" "--no-header" "--outputdir=src" "../src/1.5.3-d7b9d32fcb/registry/gl.xml"
[8/28] cl @"test/9f86d08@@khronos typedefs@exe/khronos_typedefs_nonepoxy.c.obj".rsp
../src/1.5.3-d7b9d32fcb/test/khronos_typedefs_nonepoxy.c(60): warning C4068: unknown pragma
[9/28] cl @test/9f86d08@@wgl_common@sta/wgl_common.c.obj.rsp
[10/28] cl @src/25a6634@@epoxy@sha/dispatch_common.c.obj.rsp
FAILED: src/25a6634@@epoxy@sha/dispatch_common.c.obj
cl @src/25a6634@@epoxy@sha/dispatch_common.c.obj.rsp
../src/1.5.3-d7b9d32fcb/src/dispatch_common.c(1): error C4819: The file contains a character that cannot be represented in the current code page (936). Save the file in Unicode format to prevent data loss
../src/1.5.3-d7b9d32fcb/src/dispatch_common.c(409): warning C4996: 'sscanf': This function or variable may be unsafe. Consider using sscanf_s instead. To disable deprecation, use CRT_SECURE_NO_WARNINGS. See online help for details.
../src/1.5.3-d7b9d32fcb/src/dispatch_common.c(506): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
[11/28] cl @src/25a6634@@epoxy@sha/dispatch_wgl.c.obj.rsp
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h(130): warning C4005: 'APIENTRY': macro redefinition
C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\src\1.5.3-d7b9d32fcb\include\epoxy/gl.h(59): note: see previous definition of 'APIENTRY'
[12/28] lib "/NOLOGO" /MACHINE:x64 /OUT:test/libwgl_common.a @test/libwgl_common.a.rsp
[13/28] cl @test/9f86d08@@wgl_usefontbitmaps@exe/wgl_usefontbitmaps.c.obj.rsp
../src/1.5.3-d7b9d32fcb/test/wgl_usefontbitmaps.c(50): warning C4267: 'function': conversion from 'size_t' to 'GLsizei', possible loss of data
../src/1.5.3-d7b9d32fcb/test/wgl_usefontbitmaps.c(59): warning C4267: 'function': conversion from 'size_t' to 'GLsizei', possible loss of data
[14/28] cl @test/9f86d08@@wgl_per_context_funcptrs@exe/wgl_per_context_funcptrs.c.obj.rsp
[15/28] cl @test/9f86d08@@wgl_core_and_exts@exe/wgl_core_and_exts.c.obj.rsp
[16/28] cl @test/9f86d08@@wgl_usefontbitmaps_unicode@exe/wgl_usefontbitmaps.c.obj.rsp
../src/1.5.3-d7b9d32fcb/test/wgl_usefontbitmaps.c(50): warning C4267: 'function': conversion from 'size_t' to 'GLsizei', possible loss of data
../src/1.5.3-d7b9d32fcb/test/wgl_usefontbitmaps.c(59): warning C4267: 'function': conversion from 'size_t' to 'GLsizei', possible loss of data
[17/28] cl @src/25a6634@@epoxy@sha/meson-generated..wgl_generated_dispatch.c.obj.rsp
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h(130): warning C4005: 'APIENTRY': macro redefinition
C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\src\1.5.3-d7b9d32fcb\include\epoxy/gl.h(59): note: see previous definition of 'APIENTRY'
src/wgl_generated_dispatch.c(4555): warning C4098: 'epoxy_wglBlitContextFramebufferAMD_global_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4555): warning C4098: 'epoxy_wglBlitContextFramebufferAMD_dispatch_table_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4555): warning C4098: 'epoxy_wglBlitContextFramebufferAMD_dispatch_table_thunk': 'void' function returning a value
src/wgl_generated_dispatch.c(4581): warning C4098: 'epoxy_wglDeleteBufferRegionARB_global_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4581): warning C4098: 'epoxy_wglDeleteBufferRegionARB_dispatch_table_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4581): warning C4098: 'epoxy_wglDeleteBufferRegionARB_dispatch_table_thunk': 'void' function returning a value
src/wgl_generated_dispatch.c(4585): warning C4098: 'epoxy_wglDestroyDisplayColorTableEXT_global_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4585): warning C4098: 'epoxy_wglDestroyDisplayColorTableEXT_dispatch_table_rewrite_ptr': 'void' function returning a value
src/wgl_generated_dispatch.c(4585): warning C4098: 'epoxy_wglDestroyDisplayColorTableEXT_dispatch_table_thunk': 'void' function returning a value
[18/28] cl @src/25a6634@@epoxy@sha/meson-generated.._gl_generated_dispatch.c.obj.rsp
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h(130): warning C4005: 'APIENTRY': macro redefinition
C:\Users\L\Downloads\Compressed\vcpkg-master\buildtrees\libepoxy\src\1.5.3-d7b9d32fcb\include\epoxy/gl.h(59): note: see previous definition of 'APIENTRY'
ninja: build stopped: subcommand failed.

The error is ../src/1.5.3-d7b9d32fcb/src/dispatch_common.c(1): error C4819: The file contains a character that cannot be represented in the current code page (936). Save the file in Unicode format to prevent data loss
See issues https://github.com/microsoft/vcpkg/issues/10382 and https://github.com/microsoft/vcpkg/issues/11210 for possible solutions.

Hi @xiaoxi-li
Thanks for posting this issue. It's duplicated to #11210. So let's focus on this issue there.

嗨@ xiaoxi-li
感谢您发布此问题。复制到＃11210。因此，让我们在那里集中讨论此问题。

ok,

@ xiaoxi-li错误是../src/1.5.3-d7b9d32fcb/src/dispatch_common.c(1): error C4819: The file contains a character that cannot be represented in the current code page (936). Save the file in Unicode format to prevent data loss
有关可能的解决方案，请参阅问题＃10382和＃11210。
I have try the ways provided by the net friends in #11210 and #10382 ,but it still has this problem.
And this is the out-log
package-x64-windows-rel-out.log

authors: NancyLi1013 timautry xiaoxi-li

repo: microsoft/vcpkg


text:
Have a json schema for vcpkg.json

Kind: feature request
It would be nice to have a json schema to describe vcpkg.json, both for automatic validation and IDE integration. I'm open to writing one, what would be an appropriate path/filename ?

So, the PR has been merged. Before closing that issue, I think it would be useful to have something about it in the manifest specification ? I can either PR it or close that issue depending on what you think would fit better


text:
Python 3.9.2 cannot run on windows 7

In commit f9763b717eba12be38ea750406fe2a22a7ff00f6, python upgraded to 3.9.2, which does not work under Windows 7, this make all ports which require python fail to build.
So does Windows 7 still the supported OS as the README said?

Prerequisites:

Windows 7 or newer

Hi @wasphin
Thanks for posting this issue.
Since Python 3.9 has dropped support of Windows 7. So you cannot run Python 3.9.2 on Windows 7.
Please see the document here https://docs.python.org/3/using/windows.html#
For the description in README:
Prerequisites:

Windows 7 or newer

Most ports support Windows 7, currently only those ports requiring Python 3 cannot work on Windows 7.

Some ports like harfbuzz only required python to run build tools, the version of python may not matter much, this kind of build failure is irrational. An option to use extern tools may be useful.
By now, I just make a link from python 3.8.8 to 3.9.2 to work around this.
mklink /J python-3.9.2-x86 python-3.8.8-x86

Most ports support Windows 7, currently only those ports requiring Python 3 cannot work on Windows 7.

Maybe we can make this more clear in the README?

Hi @wasphin
Thanks for your details. Since someone has added a feature deprecated-win7-support for python3 to support python 3.9 on Windows 7. Please see https://github.com/microsoft/vcpkg/pull/16420
In this case, users can still use python3 on Windows 7 via python3[deprecated-win7-support].

Hi @nabijaczleweli

It seems harfbuzz  has no dependency of python3.

harfbuzz dependents on meson which in turn dependents on python3. So any version of python that can run meson should work for building harfbuzz. The version of python3 does not have to be the latest, which is not compatible with Windows 7.

(a) why are you atting me and (b) stop using Windows 7

(a) why are you atting me and

Sorry for that.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

Close this PR since #16420 merged.

authors: JackBoosY NancyLi1013 nabijaczleweli wasphin


text:
[wangle:x64-linux] build failure

CMake build failed with wangle, vcpkg.
-- Found Boost: /root/projects/vcpkg/installed/x64-linux/include (found suitable version "1.77.0", minimum required is "1.51.0") found components: context filesystem program_options regex system thread chrono date_time atomic
-- Found folly: /root/projects/vcpkg/installed/x64-linux
CMake Error at /root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package):
By not providing "FindSodium.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Sodium", but
CMake did not find one.
Could not find a package configuration file provided by "Sodium" with any
of the following names:
SodiumConfig.cmake
sodium-config.cmake

Add the installation prefix of "Sodium" to CMAKE_PREFIX_PATH or set
"Sodium_DIR" to a directory containing one of the above files.  If "Sodium"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/fizz/fizz-config.cmake:53 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:43 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
-- Configuring incomplete, errors occurred!
Environment

OS: Linux
Compiler: The C compiler identification is GNU 7.5.0, The CXX compiler identification is GNU 7.5.0

To Reproduce
Steps to reproduce the behavior:

./vcpkg install wangle:x64-linux
Use wangle in my CMakeLists.txt

Failure logs
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Warning (dev) at /root/projects/vcpkg/installed/x64-linux/share/zlib/vcpkg-cmake-wrapper.cmake:13 (_find_package):
Policy CMP0074 is not set: find_package uses _ROOT variables.
Run "cmake --help-policy CMP0074" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
CMake variable ZLIB_ROOT is set to:
/root/projects/vcpkg/installed/x64-linux

For compatibility, CMake is ignoring the variable.
Call Stack (most recent call first):
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:5 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Found ZLIB: optimized;/root/projects/vcpkg/installed/x64-linux/lib/libz.a;debug;/root/projects/vcpkg/installed/x64-linux/debug/lib/libz.a (found version "1.2.11")
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
CMake Warning at /root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1354 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:1477 (_Boost_COMPONENT_DEPENDENCIES)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/FindBoost.cmake:2087 (_Boost_MISSING_DEPENDENCIES)
/root/projects/vcpkg/installed/x64-linux/share/boost/vcpkg-cmake-wrapper.cmake:11 (_find_package)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:740 (include)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/folly/folly-config.cmake:63 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:42 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
-- Found Boost: /root/projects/vcpkg/installed/x64-linux/include (found suitable version "1.77.0", minimum required is "1.51.0") found components: context filesystem program_options regex system thread chrono date_time atomic
-- Found folly: /root/projects/vcpkg/installed/x64-linux
CMake Error at /root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package):
By not providing "FindSodium.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Sodium", but
CMake did not find one.
Could not find a package configuration file provided by "Sodium" with any
of the following names:
SodiumConfig.cmake
sodium-config.cmake

Add the installation prefix of "Sodium" to CMAKE_PREFIX_PATH or set
"Sodium_DIR" to a directory containing one of the above files.  If "Sodium"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/fizz/fizz-config.cmake:53 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
/root/projects/vcpkg/downloads/tools/cmake-3.21.1-linux/cmake-3.21.1-linux-x86_64/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
/root/projects/vcpkg/installed/x64-linux/share/wangle/wangle-config.cmake:43 (find_dependency)
/root/projects/vcpkg/scripts/buildsystems/vcpkg.cmake:786 (_find_package)
src/wangle_server/CMakeLists.txt:1 (find_package)
-- Configuring incomplete, errors occurred!
See also "/root/projects/experiment-projects/WanglePractice/build/CMakeFiles/CMakeOutput.log".
See also "/root/projects/experiment-projects/WanglePractice/build/CMakeFiles/CMakeError.log".

@nusus ,Could you please provide your CMakeLists.txt?

@nusus ,Could you please commit a pr fix this issue? and you can open a issue of facebook update,I wiil update it

Hello good! I fixed it by changing sodium to unofficial-sodium in the port patch. File: ports/fizz/fix-zlib.patch `diff --git a/fizz/CMakeLists.txt b/fizz/CMakeLists.txt index 485e38fc..471d61a5 100644 --- a/fizz/CMakeLists.txt +++ b/fizz/CMakeLists.txt @@ -87,6 +87,8 @@ else() list(APPEND CMAKE_REQUIRED_INCLUDES ${LIBGFLAGS_INCLUDE_DIR}) endif()
+find_package(ZLIB REQUIRED) + find_package(Libevent CONFIG QUIET) if(TARGET event) message(STATUS "Found libevent from package config") @@ -246,6 +248,7 @@ target_link_libraries(fizz ${OPENSSL_LIBRARIES} sodium Threads::Threads

ZLIB::ZLIB
PRIVATE
${GLOG_LIBRARIES}
${GFLAGS_LIBRARIES}
diff --git a/fizz/cmake/fizz-config.cmake.in b/fizz/cmake/fizz-config.cmake.in
index d9918469..679b0e61 100644
--- a/fizz/cmake/fizz-config.cmake.in
+++ b/fizz/cmake/fizz-config.cmake.in
@@ -25,7 +25,10 @@ endif()

set(FIZZ_LIBRARIES fizz::fizz)
+include(CMakeFindDependencyMacro) -find_dependency(Sodium) +find_dependency(unofficial-sodium) +find_dependency(folly CONFIG) +find_dependency(ZLIB)
if (NOT fizz_FIND_QUIETLY) message(STATUS "Found fizz: ${PACKAGE_PREFIX_DIR}")`
The facebook libraries are out of date.

It works, thanks.


text:
[SFML] build failure

Host Environment

OS: macOS 10.14.4 (Travis)
Compiler: xcode10.3

To Reproduce
Steps to reproduce the behavior:
./vcpkg install SFML
Failure logs

Starting package 39/47: sfml:x64-osx
Building package sfml[core]:x64-osx...
-- Downloading https://github.com/SFML/SFML/archive/2.5.1.tar.gz...
-- Extracting source /Users/travis/build/AMS21/OpenEast/deps/vcpkg/downloads/SFML-SFML-2.5.1.tar.gz
-- Applying patch use-system-freetype.patch
-- Using source at /Users/travis/build/AMS21/OpenEast/deps/vcpkg/buildtrees/sfml/src/2.5.1-f499a1097e
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: /Users/travis/build/AMS21/OpenEast/deps/vcpkg/downloads/tools/cmake-3.14.0-osx/cmake-3.14.0-Darwin-x86_64/CMake.app/Contents/bin/cmake --build . --config Debug --target install -- -v
Working Directory: /Users/travis/build/AMS21/OpenEast/deps/vcpkg/buildtrees/sfml/x64-osx-dbg
See logs for more information:
/Users/travis/build/AMS21/OpenEast/deps/vcpkg/buildtrees/sfml/install-x64-osx-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/sfml/portfile.cmake:32 (vcpkg_install_cmake)
scripts/ports.cmake:94 (include)
Error: Building package sfml:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: sfml:x64-osx
Vcpkg version: 2019.09.12-unknownhash
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

Build failure also occurs with macOS 10.13 and XCode 10.1

Hi @AMS21, sorry for late.
Does this issue still exist?

We haven't been able to repro this; if more information comes up, or this issue appears again, please reopen.


text:
Fix VS2022 testing of the compilers.

Workaround GetChildItem returning a non-array when there's only one result.

Example build that got past the broken bit: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=5946488

Merging this because Nicole did an over-the-shoulder code review with me and this is a one-liner.


text:
[range-v3] set license

Describe the pull request
sets license in port range-v3

I saw this port also have below licenses:
libc++ License
Stepanov and McJones, "Elements of Programming" license
SGI C++ Standard Template Library license

Yes, you are right.
I looked at the licenses of the referenced packages (all listed here):

range-v3 itself: BSL-1.0
Alex Stepanov's Elements of Programming: MIT
libc++: NCSA OR MIT
SGI STL: MIT

In this case, the correct license entry would probably be: BSL-1.0 AND MIT AND (NCSA OR MIT)
Should I change it to this string?

I think the license could be BSL-1.0 AND MIT AND NCSA.

I think BSL-1.0 AND MIT AND NCSA would indicate that the port has components licensed under NCSA in any case.
However, the libc++ license states:
The libc++ library is dual licensed under both the University of Illinois
"BSD-Like" license and the MIT license.  As a user of this code you may choose
to use it under either license.  As a contributor, you agree to allow your code
to be used under both.

Because of the sentence As a user of this code you may choose to use it under either license, the user can choose not to use NCSA license at all, but instead use MIT.
Because of this, I don't think the OR should be left out.

I agree with your decision.

Great. I updated the license field

authors: Cheney-W JulZimmermann


text:
[platform-folders] update version to 4.2.0

Fixes https://github.com/microsoft/vcpkg/issues/29126
No feature needs to test.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the update!


text:
[xbyak] Update to 7.06

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review".
That way, I can be aware that you've responded since you can't modify the tags.

ready for review


text:
[tgui] Update to 1.6.1

Fixes #42278.

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree

All features passed with following triplets:
x86-windows
x64-windows
x64-windows-static

Usage test passed on x64-windows.

@LilyWangLL Are there any additional tests required before the pull request can be merged?

authors: LilyWangLL xinchengo


text:
Cannot access App Services in VS code (Internal Error)

Issue
Not able to load azure resources in VS code using azure CLI...
Operation 'Microsoft.Web/sites/read' failed as server encountered too many requests. Please try after '60' seconds. Tracking Id is '663dbaad-a145-4031-bf3e-04b2c45dba9c'.
Go to visual studio code
Sign into Azure
Visit the App Services under a specific subscription
Cannot load them
unable to load app services in sub  844f89f3-af43-43a6-9519-37b8e95ca138 only

the other subs are all good

tried to use command line to check directly and is able to reach the resources and deploy

from Azure portal, have the access to view the exact resource as well

only have issue list the resource in VS code portal

found a similar issue raised recently and is with logic app https://github.com/Azure/LogicAppsUX/issues/4929, please help check and advise

Reopening until we confirm that the fix actually works and is released.

If you could help us test that our fix actually worked, please follow these steps:

Download the zip file artifact from here: https://github.com/microsoft/vscode-azureappservice/actions/runs/10516435613/artifacts/1844660618
Extract the .vsix file from the zip file
In VS Code, hit F1 > Extensions: Install from VSIX
Navigate to vscode-azureappservice.vsix
Install and reload VS Code

If this resolves your issue, please let us know. It would help us greatly!

Thanks @nturinski for the suggestions. I will check with users having this issue and verify if it could work. Will post here once have any updates.

This fix is released. Please let me know if the users have had more success with the new release!

We don't have an official RCA or anywhere to to file it, but I can explain here.
The issue was caused by another extension loading all of the resources in parallel which caused the old caching logic to not work which resulted in many more requests to the Azure API than we had intended.

Thanks @nturinski for the explanation! Just per some further feedback from my customers that the issue has been resolved for him. However, some other colleagues are still encountering the same problem occasionally after following the steps outlined. Additionally, loading app names in VS Code is taking longer than expected.
If you have any suggestions or further steps to address these issues, could you please share them with us?

Hi @wittysuyu
Could you please share what versions of the Resources extension and the Azure App Service extension that they have installed?

Thanks @nturinski for the additional attention. As I have confirmed with my customer, since those who still getting the issue intermittently are not my direct cx, it is hard to check info with them. and since the issue is not so frequent, we agreed to put the issue on hold and will inform them to upgrade the extension to the latest just in case of next time they have similar issue. Thank you for your patience and explanation so far.

authors: nturinski wittysuyu

repo: microsoft/vscode-azureappservice


text:
Remove website_node_default_version setting

Fixes https://github.com/microsoft/vscode-azureappservice/issues/840
This was my least preferred solution, but looking at the portal's request to Azure to create a web app, they weren't doing anything special to prevent that setting from appearing.
I don't think that the setting is used anymore, so it's probably just remnants from their old way of handling node versioning.

Closing this.  We found the workaround is to set an empty app settings object when creating the web app, so will do that in favor of this.


text:
Add AppInsights steps to site creation

Fixes #222
For Linux apps, there are a couple of settings we need

APPINSIGHTS_INSTRUMENTATIONKEY I think you’re already setting this
APPLICATIONINSIGHTSAGENT_EXTENSION_ENABLED set to “true”

I copied the settings from the portal for Windows app when AI is enabled.

Oh, I'll have to fix the tests.  I'll do that in this PR.


text:
Add Java support for the different durable functions storage providers

We still need to connect Java to the storage provider work we did in the last update.  This would add automatic configuration support for Netherite and MSSQL storage providers.

@Flanker32 Hi Hanxiao Liu, we need some additional support for hooking up Java with the new Durable Storage Providers.  I will reach out to you with additional information, thank you 🙂

repo: microsoft/vscode-azurefunctions


text:
A11y_Azure Tools for VS Code_Azure Function_Collapse All_Usability: keyboard focus is landing on non-interactive (Collapsed All) control.

GitHubTags:
#A11yUsable; #A11yTCS; #A11ySev4; #Azure Tools for VS Code; #BM-AzureToolforVSCode-MAC-AUG2023; #DesktopApp;  #AINotInScope; #Device; #MAC;
OS Details:
Mac OS Ventura 13.5
Environment Details:
Application Name: Azure Tools for VS Code
Repro Steps:
1.Open Visual studio code
2. Tab till extension button and search for "Azure Functions"
3. Tab till install and navigate to the "Azure" button.
4. Tab till "Collapse All Button" from the toolbar in "workspace" section.
5.Verify whether keyboard focus is landing on non-interactive (Collapsed All) control or not.
Actual Result:
keyboard focus is landing on non-interactive (Collapsed All) control.
Expected Result:
keyboard focus should not lands on non-interactive (Collapsed All) control.
User Impact:
keyboard user will perform unnecessary actions as focus is going on non interactive controls.
Attachment:

Hi @kupatkar99, I believe this is a default VS Code behavior that will reproduce with any extension that register's a tree view using VS Code's internal API (but does not have any tree nodes to display yet).  As such, the automatic contribution and behavior of that icon would ultimately be dictated by VS Code and not the individual extension.
Unless you have reason to believe that our extension is specifically the cause of this issue, would you be open to opening this issue with VS Code instead as they are better equipped to figure out how this needs to be addressed?  Thank you!


text:
Scan silently if there are no available kits

In the offline discussion, there was two decisions around this experience:

If opening a CMake project and there’s an toolchain file entry in settings.json, then don’t do anything related to Kits.
If opening a CMake project and there is NO toolchain file entry in settings.json and if there is no kits.json, then silently start scanning for kits.

We finally decided not to implement (1) because a kit is a super set of a toolchain file, and although it's possible to detect multiple settings in settings.json instead of only the toolchain file entry, this is unnecessarily complicated.

This should also address #708

authors: bobbrow xisui-MSFT

repo: microsoft/vscode-cmake-tools


text:
New update results in response disappearing.

GitHub Copilot: v1.235.0
GitHub Copilot Chat v0.22.2024100401 (pre-release)
VS Code Version: 1.94.0
OS Version: Windows 11
Logs: See images below

Steps to Reproduce:

Request anything in the chat box

Please help me solve this bug. The info is attached.
  File "C:\Users\range\CodingProjects\RGBZ\Aeri4l\AllofPermitFly\CentralizedAppraiser\src\cleaner.py", line 36, in <module>
    if data["properties"] is not None and "unStructured" in data["properties"].keys() and "kwargs" in data["properties"]["unStructured"].keys():
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'keys'

Wait for it to generate (it will start streaming text)

Wait for it to finish, and the text will disappear.

same issue with me

Same issue here, Copilot chat doesn't seems to answer any of my question...

I'm having this same issue!

Same problem

Same problem

Same problem, probably duplicate of https://github.com/microsoft/vscode-copilot-release/issues/1742

Version: 1.94.0
Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
Date: 2024-10-02T13:08:12.626Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.8.0-45-generic snap

Is everyone seeing this using the pre-release version of the Copilot Chat extension? Does it help to switch to the Release version? (Copilot Chat extension, not Copilot)

Yes and yes for me.
(I also first made the mistake of downgrading the Copilot extension, not the Copilot Chat extension)

To fix this, you can switch to the Release version of the Copilot Chat extension, and also click + to start a new chat session.
In general, there's no advantage to using the pre-release version of Copilot Chat with VS Code Stable. This time, a change went out that should have only gone to Insiders. Sorry for the churn!

To recover your chat session which is now broken due to having responses with bad data, if the newer chat request rows load, you can click the X in the top right corner of the request. Delete all the recent requests that have bad data, and you may have to reload the window, but then you should be able to load the older requests in that chat session normally.

One related issue I've seen, which is likely related, is not being able to create new chats.

The dropdown is also greyed-out

Solution rn is just to revert to an older release.

@ReedGraff that would be a different issue, maybe the extension/extension host process is not starting. You can open a new issue for that.
We've published an update to the pre-release to fix this, so I'm closing this issue, but I'd still recommend not using the pre-release extension if you're using VS Code Stable.

@roblourens what are some verification steps for this issue?

@rzhao271 Try asking any question that includes a file/symbol link in the response and make sure the full answer is rendered

authors: DylanDevelops MaxOstrowski ReedGraff celynw maitreverge mjbvz nanotecheg psiete roblourens rzhao271 sitelicon

repo: microsoft/vscode-copilot-release


text:
Unable to Connect VSCode to Azure Emulator

Does this occur consistently?  No
Repro steps:

Error: Self Signed Certificate

Action: cosmosDB.createDocDBDatabase
Error type: DEPTH_ZERO_SELF_SIGNED_CERT
Error Message: self signed certificate
Version: 0.13.0
OS: win32
OS Release: 10.0.17763
Product: Visual Studio Code
Product Version: 1.46.0
Language: en

Call Stack
TLSSocket.onConnectSecure _tls_wrap.js:1317:34
TLSSocket.emit events.js:203:13
TLSSocket._finishInit _tls_wrap.js:792:8
TLSWrap.ssl.onhandshakedone _tls_wrap.js:606:12

@VSPradip that doesn't reproduce for me with those steps. Can you give us more info - for example are you behind a company proxy or something? Have you configured proxies in VS Code?

authors: VSPradip nturinski

repo: microsoft/vscode-cosmosdb


text:
Visualisations not displaying

It tries to show visualisations (i.e. it displays a textual link and an image icon), but it does not show anything.  If this is an issue around installing something, that should be called out to the user.

Please can you run ‘@data export’ and then share the contents of the notebook

I’m going to need you to clarify the steps you want me to take, as this request is not clear.
From: Don Jayamanne @.>
Sent: Wednesday, 30 October 2024 17:37
To: microsoft/vscode-data-analysis-for-copilot @.>
Cc: whackedMallard @.>; Author @.>
Subject: Re: [microsoft/vscode-data-analysis-for-copilot] Visualisations not displaying (Issue #77)
Please can you run @.*** https://github.com/DaTa  export’ and then share the contents of the notebook
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-data-analysis-for-copilot/issues/77#issuecomment-2445985127 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APYJI443JQRC3BNGS4YWDVLZ6B5AZAVCNFSM6AAAAABQ3L3GQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVHE4DKMJSG4 .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/APYJI4ZPACAVZSQGPT4X4KDZ6B5AZA5CNFSM6AAAAABQ3L3GQ6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURZLCWO.gif Message ID: @.*** @.***> >

@eraimundez one you run into this issue, can you try running @data /export in the chat prompt, then select Notebook from the quickpick and see whether the image is displayed in the notebook thats displayed

I ran into this as well with the following setup:

UI: https://vscode.dev (using "Connect to Tunnel...")
Browser: Chrome 130.0.6723.117
Backend: code tunnel with VS Code 1.95.2 on MacOS 14.7
Auth: GitHub

When running the @data visualize the data step, I also see the broken plot images os OP
When running @data /export using a notebook, the plots render correctly

In my Chrome inspector console I see a bunch of error messages like:
Not allowed to load local resource: file:///Users/<my redacted username>/.vscode-server/data/User/workspaceStorage/-2568fff1/ms-vscode.vscode-copilot-data-analysis/result-dachat_data_runPython-8a59d504-1731553585015.png

Do these file:// URIs need to be converted with asWebViewUri or env.asExternalUri or something that can tell between remote and local?

@eraimundez one you run into this issue, can you try running @data /export in the chat prompt, then select Notebook from the quickpick and see whether the image is displayed in the notebook thats displayed

Hi @DonJayamanne, thanks for the quick answer!
The notebook is generated correctly and the figures are correctly displayed.
Just to add a bit more information in case it could help:

I am connecting using Remote SSH to a Linux machine (and the connection is stable)
Github Copilot is set up and works perfectly in the remote machine (so it seems not to be an issue from Copilot).
Table outputs are correctly displayed in the Copilot chat window

I would also like to acknowledge this great extension! Congrats

I have carried out these steps, and can confirm I am getting the image in the notebook but not in the chat panel
thx
From: Elba Raimundez @.>
Sent: Thursday, 14 November 2024 19:55
To: microsoft/vscode-data-analysis-for-copilot @.>
Cc: whackedMallard @.>; Author @.>
Subject: Re: [microsoft/vscode-data-analysis-for-copilot] Visualisations not displaying (Issue #77)
@eraimundez https://github.com/eraimundez  one you run into this issue, can you try running @data /export in the chat prompt, then select Notebook from the quickpick and see whether the image is displayed in the notebook thats displayed
Hi @DonJayamanne https://github.com/DonJayamanne , thanks for the quick answer!
The notebook is generated correctly and the figures are correctly displayed.
Just to add a bit more information in case it could help:

I am connecting using Remote SSH to a Linux machine (and the connection is stable)
Github Copilot is set up and works perfectly in the remote machine (so it seems not to be an issue from Copilot).
Table outputs are correctly displayed in the Copilot chat window

I would also like to acknowledge this great extension! Congrats
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-data-analysis-for-copilot/issues/77#issuecomment-2475760200 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APYJI47GVIVSQFNDKEDHNKT2ARQNDAVCNFSM6AAAAABQ3L3GQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZVG43DAMRQGA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/APYJI4YBK7KL66Z7SUJ3NF32ARQNDA5CNFSM6AAAAABQ3L3GQ6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUTSENEQ.gif Message ID: @.*** @.***> >

authors: DonJayamanne eraimundez micahyoung whackedMallard


text:
How can I install extensions on the VS Code Edge Devtools browser version?

When I try to install any extension I just get this error :O

Extensions work fine on my normal edge browser :'(
But I can't attach the devtools to my standard edge browser :(
AB#53153306

Thanks for filing.
I know installing extensions that extend the devtools UI is not possible at the moment, see #1039.
However, I believe installing extensions that extend the browser UI should work. By the looks of it, you are using an external browser window, not the embedded browser preview in VS Code, so I don't see why installing extensions there should not work.
I'll mark this as tracked on our backlog for investigation.

Hi everyone
Thanks for the feedback seems that most of it is already answered. For running on the vscode.dev version please see:
https://github.com/microsoft/vscode-edge-devtools/issues/2367

authors: captainbrosset lopugit vidorteg

repo: microsoft/vscode-edge-devtools


text:
Fix spelling error

Signed-off-by: Oxygemo alej0hio2007@gmail.com

Thanks!

repo: microsoft/vscode-extension-samples


text:
Native Notebooks - Add Run All Above/Run All Below Icons

Add run all above and run all below to global notebook toolbar.
No changes in functionality, functions same as stable implementation.

Validated

Validated

Can we have the run all above/below icons to the right of the run all icon in the notebook toolbar?

Just like the old implementation

Can we have the run all above/below icons to the right of the run all icon in the notebook toolbar?

Just like the old implementation

authors: claudiaregio joyceerhl

repo: microsoft/vscode-jupyter