[Feature Request] Implementation of Insertion-Deletion

Implementation of Insertion-Deletion
As indicated by the name, Insertion-Deletion contains two experiments:

Insertion that progressively inserts the most important features and measure the change in the prediction.
Deletion that progressively deletes the most important features and measure the change in the prediction.

ProgressivePerturbation
To implement these two experiments, we first need to implement ProgressivePerturbation class which looks like this:
class ProgressivePerturbation:

    def __init__(
        self,
        input_tensor: torch.Tensor,
        replace_tensor: torch.Tensor,
        sorted_inds: Tuple[torch.Tensor, torch.Tensor],
    ) -> None:
        self._current_tensor = input_tensor.clone()
        self._replace_tensor = replace_tensor
        self._row_inds, self._col_inds = sorted_inds
        ...

    def _perturb_by_inds(self, row_inds: torch.Tensor, col_inds: torch.Tensor) -> None:
        self._current_tensor[..., row_inds, col_inds] = self.replace_tensor[..., row_inds, col_inds]

    @property
    def current_tensor(self) -> torch.Tensor:
        return self._current_tensor

    def perturb(self, forward_batch_size: int = 128, perturb_step_size: int = 10) -> Iterator[torch.Tensor]:
        ...

In the initialization method, input_tensor is the tensor to be modified, and the replacement values come from replace_tensor. sorted_inds is a tuple of (row_inds, col_inds), which indicate the row and column indices of the sorted saliency map pixels.
The perturb method returns an iterator of Tensors. Each tensor should contains forward_batch_size perturbed tensors, except for the last one, which contains (num_pixels // perturb_step_size + 1) % forward_batch_size perturbed tensors. At each step, the method perturbs perturb_step_size pixels from the current tensor. After generating forward_batch_size perturbed tensors, it then stacked the perturbed tensors together and yield the batched tensor.

InsertionDeletionResult

class InsertionDeletionResult(SerilizableResult):

    def __init__(
        self,
        summarized: bool = False,
        ...
    ) -> None:

        self.summarized = summarized
        ...

    def add_single_result(self, single_result: Dict) -> None:
        ...

    def dump(self, file_path: str) -> None:
        ...

The single_result is a dictionary containing following fields:

"del_scores": a np.ndarray that stores the deletion scores at each perturbation step.
"ins_scores": a np.ndarray` that stores the insertion scores at each perturbation step.
"img_path": the path to the image.
"ins_auc": insertion AUC.
`"del_auc": deletion AUC.

The flag summarized specifies whether to dump all the raw single results, or compute the mean and std of the ins_auc and del_auc respectively. If summarized = True, the following dict should be dumped to a JSON file:

"mean_ins_auc": a float.
"std_inds_auc": a float.
"mean_del_auc": a float.
"std_del_auc": a float.
"num_samples": an int.

mmcv can be used to dump the cached results.

InsertionDeletion
from torchvision.transforms import GaussianBlur

class InsertionDeletion(ReInferenceMetric):

    def __init__(
        self,
        classifier_cfg: Dict,
        forward_batch_size: int = 128,
        perturb_step_size = 10,
        sigma: float = 5.0,
        summarized: bool = False,
        ...
    ) -> None:

        self._result = InsertionDeletionResult(summarized, ...)

        self.classifier = ...
        self.gaussian_blur = GaussianBlur(int(2 * sigma - 1), sigma)
        self.forward_batch_size = forward_batch_size
        self.perturb_step_size = perturb_step_size
        ...

    def evaluate(self, img: torch.Tensor, smap: torch.Tensor, target: int) -> Dict:
        num_pixels = torch.numel(smap)
        _, inds = torch.topk(smap.flatten(), num_pixels)
        row_inds, col_inds = (torch.tensor(x) for x in np.unravel_index(inds.numpy(), smap.size()))

        # deletion
        del_perturbation = ProgressivePerturbation(...)
        del_scores: List[np.ndarray] = []
        with torch.no_grad():
            for ... in del_perturbation.perturb(...):
                scores = torch.softmax(self.classifier(...), -1)[:, target]
                    del_scores.append(scores.cpu().numpy())

        del_scores: np.ndarray = np.concatenate(del_scores, 0)
        # compute AUC
        ...

        blurred_img = self.gaussian_blur(img)
        ins_perturbation = ProgressivePerturbation(blurred_img, img)
        ins_scores: List[np.ndarray] = []
        with torch.no_grad():
            for ... in ins_perturbation.perturb(...):
                scores = torch.softmax(self.classifier(...), -1)[:, target]
                ins_scores.append(scores.cpu().numpy())

        ins_scores: np.ndarray = np.concatenate(ins_scores, 0)
        # compute AUC

        single_result = dict(...)
        return single_result

    def update(self, single_result: Dict) -> None:
        ...

build_classifier can be used to build a classifier from a dict, and freeze_model can be used to freeze the whole model and turn it into eval mode.
scipy provides functions for computing the AUC by integrating the ins_scores or del_scores.

For a single image, we progressively replace the pixels with values from another pre-defined tensor. At each step, we place perturb_step_size e.g. 10 pixels. If an image with spatial size 224 by 224 is given, then it takes over 4000 steps. If we forward perturbed tensors individually, then it is too slow. Instead, we would batch these perturbed tensors and forward them batch by batch to fully utilize the computation power of the GPU.

Thanks, it's clear now :).

What is the use of the method update in InsertionDeletion class? Is it different from add_single_result method in InsertionDeletionResult class?

@rjagtani It is basically calling self._result.add_single_result inside the function. Note that self._result is private. So we cannot call add_single_result outside the InsertionDeletion class. Therefore, we wrap it a little bit. In the end it is like this:
ins_del = InsertionDeletion(...)
single_result = ins_del.evaluate(...)
# maybe some post-processing of the single_result, e.g. add img_path to the dict

ins_del.update(single_result)

I'm writing tests for Insertion Deletion Metric and one of the problems I'm facing is that I don't have a constant output to test my code against. Here is the test - assert expected_output == ins_del.evaluate(...) but I'm getting different prediction scores for the same image (because the weights are initialized randomly and pretrained is set to False). Any ideas would be appreciated. I'd also like to discuss some changes to the code and tests that I have added. I have published the code on my github - the name of the branch is 'id3'.

I'm writing tests for Insertion Deletion Metric and one of the problems I'm facing is that I don't have a constant output to test my code against. Here is the test - assert expected_output == ins_del.evaluate(...) but I'm getting different prediction scores for the same image (because the weights are initialized randomly and pretrained is set to False). Any ideas would be appreciated. I'd also like to discuss some changes to the code and tests that I have added. I have published the code on my github - the name of the branch is 'id3'.

Please do not use any pre-trained/ randomly initialized torchvision or timm models in your tests. They are too heavy. Instead, create a dummy and shallow CNN on your own, and initialize the weights to certain constants.
In addition, it is not necessary to test the numeric equality in all cases. Sometimes testing the object types or array shapes are sufficient.
Regarding the updated code, please send a Draft PR so that I can comment and send suggestions.

I'm writing tests for Insertion Deletion Metric and one of the problems I'm facing is that I don't have a constant output to test my code against. Here is the test - assert expected_output == ins_del.evaluate(...) but I'm getting different prediction scores for the same image (because the weights are initialized randomly and pretrained is set to False). Any ideas would be appreciated. I'd also like to discuss some changes to the code and tests that I have added. I have published the code on my github - the name of the branch is 'id3'.

Please do not use any pre-trained/ randomly initialized torchvision or timm models in your tests. They are too heavy. Instead, create a dummy and shallow CNN on your own, and initialize the weights to certain constants.
In addition, it is not necessary to test the numeric equality in all cases. Sometimes testing the object types or array shapes are sufficient.
Regarding the updated code, please send a Draft PR so that I can comment and send suggestions.

Thanks, I'll make these changes and send a Draft PR

I get this error when I run 'mypy saliency_metrics' - Signature of "evaluate" incompatible with supertype "ReInferenceMetric". Seems like the issue has been discussed here and would require changes to ReInferenceMetric https://stackoverflow.com/questions/51003146/python-3-6-signature-of-method-incompatible-with-super-type-class
I've created a pull request nevertheless.

@rjagtani The mypy issue is because you modify the method signature to def evaluate(self, img: Tensor, smap: Tensor, img_path: str = None) -> Dict. Please use def evaluate(self, img: Tensor, smap: Tensor,  target: int, **kwargs: Any) -> Dict. The img_path can be retrieved from the kwargs as img_path: str = kwargs["img_path"].


[Task] [Suggest] Support the addition of one-click execution function without dependency environment

Description
建议功能：
为 hertzbeat 添加一个功能，使其能够脱离依赖环境，支持在不需要额外监控服务器的情况下，一键执行监控配置。
背景：
在一些情况下，没有额外的监控服务器可供使用，或者部署监控服务器不切实际。为了满足这些场景的需求，希望 hertzbeat 可以提供一种方式，使其可以在不依赖复杂环境的情况下运行。
预期实现：
开发一个命令行工具，用户可以将 hertzbeat 配置和测试的数据按照规范整理起来，用该命令行工具执行。
用户可以将这个命令行工具部署到运维机器，甚至是 U 盘等存储设备中。
用户执行命令行工具时，工具会根据配置自动执行相应的监控测试，并将结果报告生成为 HTML 或 PDF 格式，参考 #1171 。
通过这个功能，用户可以更灵活地执行监控配置，无需担心复杂的依赖环境。
思考
这个和 hertzbeat 的 docker 运行环境大体相似，但是并不完全相同，毕竟不能随便装 docker 到处跑，但是恰恰是命令行工具，重点是执行监控的测试结果，所以很多可视化的东西以及这些依赖的东西都不需要。
此条反馈与 #1171  整体是 1 个功能衍生出来的，但是从功能角度各有不同，故分开反馈。
Task List
No response

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Description
Suggested features:
Add a function to hertzbeat so that it can break away from the dependent environment and support one-click monitoring configuration without the need for an additional monitoring server.
background:
In some cases, no additional monitoring server is available, or it is impractical to deploy a monitoring server. In order to meet the needs of these scenarios, it is hoped that hertzbeat can provide a way to run without relying on a complex environment.
Expected implementation:
Develop a command line tool, users can organize hertzbeat configuration and test data according to the specification, and use this command line tool to execute.
Users can deploy this command-line tool to operation and maintenance machines, or even storage devices such as U disks.
When the user executes the command-line tool, the tool will automatically execute the corresponding monitoring test according to the configuration, and generate the result report in HTML or PDF format, refer to #1171.
With this function, users can perform monitoring configuration more flexibly without worrying about complex dependency environments.
think
This is roughly similar to hertzbeat's docker operating environment, but it is not exactly the same. After all, you can't just install docker to run around, but it is just a command line tool. The focus is on the test results of execution monitoring, so many visual things and these dependent things are unnecessary.
This feedback and #1171 are derived from one function as a whole, but they are different from the function point of view, so they are reported separately.
Task List
No response

感觉老哥你说的功能有点像一键巡检，脱离监控系统独立执行一个巡检小工具来做到对当前主机资源的监测然后生成巡检报告。
这个小工具可能是我们想做的方向不一样，且和hertzbeat本身脱离了没有关系，感觉适合新开一个项目来做，但我们目前不会有这样的考虑，抱歉。可以找一下现有应该有类似的监控脚本命令行工具。

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

I feel that the function you mentioned is a bit like one-click inspection, which independently executes an inspection tool independently of the monitoring system to monitor the current host resources and then generate an inspection report.
This small tool may be in a different direction than what we want to do, and it has nothing to do with hertzbeat itself. It feels suitable for a new project, but we will not have such considerations at the moment, sorry. You can look for existing command line tools that should have similar monitoring scripts.

这么说方向确实有点不一致，我想得简单了，我的想法是监控嘛，除了有定时任务的监控处理，也可以手动去检测，这也就有点像 一件巡检的意思，这也是我突发奇想，提出这个的原因。另一个就是基于 手动检测的前提，我都手动处理了，想看看本次执行的所有结果，也就对应到报告这个点上了。
虽然细细思考确实有点方向不同，不过还是感谢有这样的项目。

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

In this way, the direction is indeed a bit inconsistent. I think it is simple. My idea is to monitor. In addition to the monitoring and processing of scheduled tasks, it can also be detected manually. This is a bit like a patrol inspection. On a whim, come up with the reason for this. The other is based on the premise of manual detection. I have manually processed it. I want to see all the results of this execution, which corresponds to the point of reporting.
Although it is indeed a bit different to think about it carefully, I am still grateful for such a project.


Update  CE Roadmap for Q4 FY25

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://672b93d0ceb64c1811387101--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://672b991d652c681f0875530f--harness-developer.netlify.app


Remove two clients of MaterialList

Clients should use ListView instead.

@Hixie @HansMuller

Did you want to LGTM this patch?

Sorry, I was writing a comment then got pulled away.
The comment was that to maintain strict parity with what we had before, we really should include an itemExtent on the replacements. But the problem is, do we just hard-code those? Put a constant somewhere? When I looked into doing this the other day, I found that the constants for MaterialList didn't match the constants for ListItem, which seems like an issue.
Anyway, LGTM.

I'm not too worried about it for these examples given that they're examples and demos.  We'll need to cross that bridge when we go to remove material list.

Well, our examples and demos are what people are going to copy. So in a way, they're also our customers' code. :-)


Missing types on published package

Not sure if it's intended or not but it seems helmet.d.ts and all the policies typings are missing on the published package, unlike the build result when I tested locally.

Types seems to come from helmet.ts, but only the index.ts files are included in the package.

Should be resolved in the newest release :) @nxht


First approach to sequentials and abstraction layer introduce

I working on Sequential, if coverage with test would satisfy me I will change from draft and add there some description.

Can you add example of sequential chain?

@CrazyBaran tests are failing.

@jeastham1993 This is still in progress, I am not happy still with tests coverage and work on it.

@jeastham1993 @oorosh I think more or less ready to review.

@CrazyBaran all the implemented code looks good to me. Could you move the abstractions back into the single project for now though? We've got the open discussion topic around library structure.
https://github.com/jeastham1993/langchain-dotnet/issues/4


I couldn't open the page

It seems that it is not working properly, the first is "GET http://code.myhost.com/static/19ff74650b1b001d33d5c0207e311dd7c0ff4d2f/src/browser/media/manifest.json 404 (Not Found)", and then "WebSocket connection to ' ws: //code.myhost.com/? type = Management & reconnectionToken = 34a22b65-9192-4887-8493-b529548f046f & reconnection = false & skipWebSocketFrames = false 'failed: Error during WebSocket handshake: Unexpected response code: 200 ", and then the websocket was closed, status Code is 1006

Ah yeah the manifest 404 should be fixed in the next version.
Are you serving code-server through a reverse proxy? In my experience when the websocket response is a 200 it's because there's a reverse proxy that isn't configured to handle websockets.

Please try the latest release!

Closing for inactivity. Should be fixed anyway.


Dummy date set

Is this the correct approach?

An empty input string is saved as <FRBRdate date='1000-01-01' name='dummy'>
MarkLogic returnsdummy dates as ()
The Multipart Decoder returns the empty string if no parts are encountered (existing behaviour)

This feels slightly risky and might not be the right behaviour.

 Ensure editor-ui inserts valid date

This seems OK, the logic in the code is sound given the approach. The only other approach I can think of is to either leave out the FRBRDate tag (which I think isn't allowed in the schema), or to leave out the attributes (but I can't tell if that's allowed or not). I think if it IS valid, having no attributes is probably the best approach, but if that's not allowed then this is as good as we can get.

@dragon-dxw  I have a brief memory about this but it's been a while, do you know if this change is it still required? I see Heather archived the card a while back but potentially still a problem?


net/http/cookie: readSetCookies does not strip whitespace for key/value pair received

What version of Go are you using (go version)?

$ go version
go version go1.14.6 windows/amd64

Does this issue reproduce with the latest release?
Yes. I'm using the latest go release for Windows.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\-snip-\AppData\Local\go-build
set GOENV=C:\Users\-snip-\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\-snip-\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=-snip-
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\-snip-\AppData\Local\Temp\go-build817710326=/tmp/go-build -gno-record-gcc-switches

What did you do?

Use http.Client with cookie jar to access site with valid Set-Cookie header, but the cookie did not persist.
The first two requests:
GET http://<IP_ADDRESS>/html/footer.html HTTP/1.1
Host: <IP_ADDRESS>
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

HTTP/1.1 200 OK
Date: Thu, 01 Jan 1970 00:00:00 GMT
Server: webserver
Connection: keep-alive
Keep-Alive: timeout=10, max=100
X-Download-Options: noopen
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000; includeSubdomains
Content-Length: 185
Content-Type: text/html
Expires: 0
Cache-Control: no-cache
Set-Cookie: SessionID=some_value;path =/;HttpOnly;

GET http://<IP_ADDRESS>/api/user/state-login HTTP/1.1
Host: <IP_ADDRESS>
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

In the second request, the cookie did not persist. When looking at the cookie jar after the first request, the cookie has been stored under the path /html instead of expected /, which applies to the whole domain.
When I further examine the response header from the initial request, there's a white-space after the path key. This extra whitespace has caused readSetCookies to not recognise the key-pair, and the cookie has been stored relative to the document path (i.e. /html).
A quick read in RFC6265#5.2, step 4 states that the user-agent should strip leading or trailing whitespaces for the key/value string.
An attempt to fix this behaviour:
--- cookie.go   2020-07-16 22:30:44.000000000 +0100
+++ cookie_2.go 2020-07-26 11:33:31.710704300 +0100
@@ -92,8 +92,8 @@
                        if j := strings.Index(attr, "="); j >= 0 {
                                attr, val = attr[:j], attr[j+1:]
                        }
-                       lowerAttr := strings.ToLower(attr)
-                       val, ok = parseCookieValue(val, false)
+                       lowerAttr := strings.TrimSpace(strings.ToLower(attr))
+                       val, ok = parseCookieValue(strings.TrimSpace(val), false)
                        if !ok {
                                c.Unparsed = append(c.Unparsed, parts[i])
                                continue

What did you expect to see?
The cookie is carried with subsequent requests.
What did you see instead?
The cookie was not set in subsequent requests, due to path mismatch.

As a workaround, I've created an alternative cookie jar which forces the path to be /.
package cookiejar

import (
	"net/http"
	"net/http/cookiejar"
	"net/url"
)

// This is jar is to workaround an issue with current version of go.
// For the bug report, see: https://github.com/golang/go/issues/40414

type Jar struct {
	*cookiejar.Jar
}

func (j *Jar) SetCookies(u *url.URL, cookies []*http.Cookie) {
	for _, cookie := range cookies {
		cookie.Path = "/"
	}

	j.Jar.SetCookies(u, cookies)
}

func New(opts *cookiejar.Options) (*Jar, error) {
	var err error
	jar := &Jar{}
	jar.Jar, err = cookiejar.New(opts)
	return jar, err
}

/cc @bradfitz


Remove myself as an autoassigned reviewer.

I haven't been able to keep up/respond to these for a while now.

r? @nrc
(rust_highfive has picked a reviewer for you, use r? to override)

:-(


Bump to cf-deployment v12.6.0

Is your feature request related to a problem? Please describe.
Cf-k8s-networking does not work in combination with kubecf, because the label selector  of the k8s services created by cf-k8s-networking does not match with the pod labels created by eirini. Therefore, no traffic can be routed to apps.
Describe the solution you'd like
In order to use cf-k8s-networking in combination with kubecf, a newer version of capi-release (1.87.0->1.88.0) is required. The new capi-release contains a version of cloud-controller-ng that sends additional fields in a DesireLRPRequest (see https://github.com/cloudfoundry/cloud_controller_ng/pull/1474), which allow eirini to set the correct pod labels.
Capi-release v1.88.0 can be included in kubecf by bumping cf-deployment to v12.6.0 or newer.
@loewenstein @viovanov

@jkbschmid in #229 we're planning to bump to 12.14 or even later.

@fargozhu That's good to know, I didn't see that one :) Closing in favour of #229


[Bug] PayPal not backlinking

https://github.com/boxbilling/boxbilling/issues/1059

PayPal IPN linking works. I'm working with @xSido at the moment to identify any other issues.
In this particular case, the problem was caused by csrfp which is included in master to mitigate a potential security vulnerability.

But, this integration still leaves a few holes and causes problems like this. Because of that I have not included it in any release and I intend to come up with a different solution.
If you use one of the latest releases, you will NOT have that issue.

That doesn't mean the PayPal integration is working 100%, but I hope xSido and I can find the cause easily

@BelleNottelling  Did you manage to identify the cause of this issue at all?

I absolutely forgot to respond to this. IIRC we never found an actual issue. I was about to use PayPal's developer tools to test it and it seemed like it worked fine. Documentation seemed to match what the integration was doing, and after a re-install I think it was working for Sido

Closing this issue for now, as I have also just tested it and it does seem to be working.


Cannot validate argument on parameter 'SkuName'

D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

  + CategoryInfo          : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException
  + FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick @.>
Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant @.>
Cc: Subscribed @.***>
Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

      + CategoryInfo          : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

      + FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.

Hi Roman,
Thank you for the response.
So should it be something like,
-KeyVaultAuditStorageAccountLocation Standard_GRS
Thank you
Antonio Rennvick
Get Outlook for Androidhttps://aka.ms/ghei36

From: Roman G. Powell @.***>
Sent: Monday, June 21, 2021, 11:08 PM
To: microsoft/cross-tenant
Cc: arennvick; Author
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick @.>
Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant @.>
Cc: Subscribed @.***>
Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

CategoryInfo : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865221091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIET7ZK636AXEXWKRD3TT52HXANCNFSM47ACKM3A.[X]

That is correct.
From: arennvick @.>
Sent: Monday, June 21, 2021 6:19 PM
To: microsoft/cross-tenant @.>
Cc: Roman Powell @.>; Comment @.>
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Hi Roman,
Thank you for the response.
So should it be something like,
-KeyVaultAuditStorageAccountLocation Standard_GRS
Thank you
Antonio Rennvick
Get Outlook for Androidhttps://aka.ms/ghei36

From: Roman G. Powell<EMAIL_ADDRESS>Sent: Monday, June 21, 2021, 11:08 PM
To: microsoft/cross-tenant
Cc: arennvick; Author
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick<EMAIL_ADDRESS>Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

CategoryInfo : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865221091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIET7ZK636AXEXWKRD3TT52HXANCNFSM47ACKM3A.[X]

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865449636&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8dXKbfp2ishx7J1L1MP4ouudHkIytqXruf2dikUOw%2BI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6GUNKUNTNUW3DG7VLLTT7QHHANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2Fjvzht1R29pSypeMT%2BD3hsdoSbp1xZ8qVe%2BtqlCcO9g%3D&reserved=0.

im getting the below error.
[cid:b9066a80-2d17-4d31-bb47-96ce10d04366]
Thank You
Antonio Rennvick Annoson

From: Roman G. Powell @.>
Sent: Tuesday, June 22, 2021 9:54 AM
To: microsoft/cross-tenant @.>
Cc: arennvick @.>; Author @.>
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
That is correct.
From: arennvick @.>
Sent: Monday, June 21, 2021 6:19 PM
To: microsoft/cross-tenant @.>
Cc: Roman Powell @.>; Comment @.>
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Hi Roman,
Thank you for the response.
So should it be something like,
-KeyVaultAuditStorageAccountLocation Standard_GRS
Thank you
Antonio Rennvick
Get Outlook for Androidhttps://aka.ms/ghei36

From: Roman G. Powell<EMAIL_ADDRESS>Sent: Monday, June 21, 2021, 11:08 PM
To: microsoft/cross-tenant
Cc: arennvick; Author
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick<EMAIL_ADDRESS>Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

CategoryInfo : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865221091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIET7ZK636AXEXWKRD3TT52HXANCNFSM47ACKM3A.[X]

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865449636&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8dXKbfp2ishx7J1L1MP4ouudHkIytqXruf2dikUOw%2BI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6GUNKUNTNUW3DG7VLLTT7QHHANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2Fjvzht1R29pSypeMT%2BD3hsdoSbp1xZ8qVe%2BtqlCcO9g%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865517735, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIGSBJWRRHPWF2GXNJ3TUAGBNANCNFSM47ACKM3A.

Antonio,
Can you use the parameter -UseAppAndCertGeneratedForSendingInvitation and try again.
Thanks,
Roman
From: Antonio Rennvick @.>
Sent: Saturday, June 26, 2021 10:12 PM
To: microsoft/cross-tenant @.>; microsoft/cross-tenant @.>; Cross-Tenant Mailbox Migration Preview @.>
Cc: Author @.***>
Subject: [EXTERNAL] Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
im getting the below error.
@.***D76C04.5D58AB00]
Thank You
Antonio Rennvick Annoson

From: Roman G. Powell<EMAIL_ADDRESS>Sent: Tuesday, June 22, 2021 9:54 AM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: arennvick<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
That is correct.
From: arennvick<EMAIL_ADDRESS>Sent: Monday, June 21, 2021 6:19 PM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: Roman Powell<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Hi Roman,
Thank you for the response.
So should it be something like,
-KeyVaultAuditStorageAccountLocation Standard_GRS
Thank you
Antonio Rennvick
Get Outlook for Androidhttps://aka.ms/ghei36

From: Roman G. Powell @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: Monday, June 21, 2021, 11:08 PM
To: microsoft/cross-tenant
Cc: arennvick; Author
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant @.<mailto:@.mailto:***<EMAIL_ADDRESS>Cc: Subscribed @.<mailto:@.mailto:***<EMAIL_ADDRESS>Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

CategoryInfo : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865221091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIET7ZK636AXEXWKRD3TT52HXANCNFSM47ACKM3A.[X]

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865449636&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8dXKbfp2ishx7J1L1MP4ouudHkIytqXruf2dikUOw%2BI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6GUNKUNTNUW3DG7VLLTT7QHHANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2Fjvzht1R29pSypeMT%2BD3hsdoSbp1xZ8qVe%2BtqlCcO9g%3D&reserved=0.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865517735&data=04|01|Roman.Powell%40microsoft.com|460db8a41f4b413535be08d9392a21a4|72f988bf86f141af91ab2d7cd011db47|0|0|637603676045453918|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bxx3STq8ldQIkDne3dRh58LEWrqGe0%2FjyceJPP3qfbU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAURRUIGSBJWRRHPWF2GXNJ3TUAGBNANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|460db8a41f4b413535be08d9392a21a4|72f988bf86f141af91ab2d7cd011db47|0|0|637603676045463875|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=fuHKCVydfg5grFuyejCRzqyNhrMCHL%2Fdy%2BLPD2ypU7k%3D&reserved=0.

Hi Roman,
Thank you so much for the support. all worked well.
Thank You
Antonio Rennvick Annoson

From: Roman Powell @.>
Sent: Monday, June 28, 2021 10:30 PM
To: @. @.>; @. @.>; @. @.>; Cross-Tenant Mailbox Migration Preview @.>
Cc: @.*** @.***>
Subject: RE: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Antonio,
Can you use the parameter -UseAppAndCertGeneratedForSendingInvitation and try again.
Thanks,
Roman
From: Antonio Rennvick @.>
Sent: Saturday, June 26, 2021 10:12 PM
To: microsoft/cross-tenant @.>; microsoft/cross-tenant @.>; Cross-Tenant Mailbox Migration Preview @.>
Cc: Author @.***>
Subject: [EXTERNAL] Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
im getting the below error.
@.***D76C04.5D58AB00]
Thank You
Antonio Rennvick Annoson

From: Roman G. Powell<EMAIL_ADDRESS>Sent: Tuesday, June 22, 2021 9:54 AM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: arennvick<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
That is correct.
From: arennvick<EMAIL_ADDRESS>Sent: Monday, June 21, 2021 6:19 PM
To: microsoft/cross-tenant<EMAIL_ADDRESS>Cc: Roman Powell<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Hi Roman,
Thank you for the response.
So should it be something like,
-KeyVaultAuditStorageAccountLocation Standard_GRS
Thank you
Antonio Rennvick
Get Outlook for Androidhttps://aka.ms/ghei36

From: Roman G. Powell @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: Monday, June 21, 2021, 11:08 PM
To: microsoft/cross-tenant
Cc: arennvick; Author
Subject: Re: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
Good morning. When using StorageAudit you also need to supply the parameter KeyVaultAuditStorageAccountLocation, generally just using Standard_GRS based on most subscriptions.
Thanks,
Roman
From: arennvick @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: Sunday, June 20, 2021 6:21 AM
To: microsoft/cross-tenant @.<mailto:@.mailto:***<EMAIL_ADDRESS>Cc: Subscribed @.<mailto:@.mailto:***<EMAIL_ADDRESS>Subject: [microsoft/cross-tenant] Cannot validate argument on parameter 'SkuName' (#64)
D:\new\SetupCrossTenantRelationshipForTargetTenant.ps1 : Cannot validate argument on parameter 'SkuName'. The argument "" does not belong to the set
"Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS,Premium_ZRS,Standard_GZRS,Standard_RAGZRS" specified by the ValidateSet attribute. Supply an argument that is in the set
and then try the command again.
At line:1 char:1

.\SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDoma ...

CategoryInfo : InvalidData: (:) [SetupCrossTenan...argetTenant.ps1], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationError,SetupCrossTenantRelationshipForTargetTenant.ps1

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787401010|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2pvQTs17Vt1aC%2F9PBYm5qhaJw3BJN5yC8m%2BwMRcY8LI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6F3HHLCJ76RS3ULHRLTTXTMXANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|b6ff24e02db84824389b08d933ee4846|72f988bf86f141af91ab2d7cd011db47|0|0|637597920787410960|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6SlVSj11H2%2BJjVoDzZR2hiFafKJbEgjHpM8Up40Xdxo%3D&reserved=0.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/cross-tenant/issues/64#issuecomment-865221091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURRUIET7ZK636AXEXWKRD3TT52HXANCNFSM47ACKM3A.[X]

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865449636&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=8dXKbfp2ishx7J1L1MP4ouudHkIytqXruf2dikUOw%2BI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPUHY6GUNKUNTNUW3DG7VLLTT7QHHANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|175365f4628d43b8e0d108d9351badcc|72f988bf86f141af91ab2d7cd011db47|0|0|637599215288150990|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2Fjvzht1R29pSypeMT%2BD3hsdoSbp1xZ8qVe%2BtqlCcO9g%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fcross-tenant%2Fissues%2F64%23issuecomment-865517735&data=04|01|Roman.Powell%40microsoft.com|460db8a41f4b413535be08d9392a21a4|72f988bf86f141af91ab2d7cd011db47|0|0|637603676045453918|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Bxx3STq8ldQIkDne3dRh58LEWrqGe0%2FjyceJPP3qfbU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAURRUIGSBJWRRHPWF2GXNJ3TUAGBNANCNFSM47ACKM3A&data=04|01|Roman.Powell%40microsoft.com|460db8a41f4b413535be08d9392a21a4|72f988bf86f141af91ab2d7cd011db47|0|0|637603676045463875|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=fuHKCVydfg5grFuyejCRzqyNhrMCHL%2Fdy%2BLPD2ypU7k%3D&reserved=0.


ERROR in Cannot read properties of undefined (reading 'pop')

Describe the bug
After Installing the latest<EMAIL_ADDRESS>then this error is showing on build
To Reproduce
Install the<EMAIL_ADDRESS>and build it. It will throw this error.
Versions

react-loading-skeleton version: 3.2.0
Browser version: Version 112.0.5615.12 (Official Build) dev (arm64)

Later, After downgraded to @3.1.1 then this issue get resolved.

This issue only happening when importing css file.
import 'bootstrap/dist/css/bootstrap.min.css';

Hey @decpk, it seems most likely that this is an issue with your Webpack configuration. If you can share more details and/or submit a minimal reproducible example, I can look into it further.

Closing since this seems to be unrelated to react-loading-skeleton.


Input fields for answer should be more apparent

As you can see in the following screenshot, the background of the input field for the answers is the same as the code samples so it's difficult to distinguish the "holes" for the answers.

Fixed in #474


Filter out Live projections in command line rebuild

Fixes #2151

I couldn't find any tests for this and wasn't sure how to write one - I'm happy to add some if someone can give me a hint to get started on it


Fixing empty leaderboard column display issues

@ mention of reviewers
@ckcollab
A brief description of the purpose of the changes contained in this PR.
displays "N/A" if score is missing, rather than messing with column ordering
Issues this PR resolves
resolves #357
A checklist for hand testing

[x] create a competition with multiple leaderboard columns
[x] run a submission against it and push it to the leaderboard
[x] manually delete one of the submission scores for the submission on the leaderboard (note which one)
[x] refresh the leaderboard and verify that all the other scores are still in their correct columns and that the score you deleted shows up as N/A

Any relevant files for testing
comp
recommend unhiding columns on leaderboard in the editor/yaml
sub
Checklist

[x] Code review by me
[x] Hand tested by me
[x] I'm proud of my work
[x] Code review by reviewer
[ ] Hand tested by reviewer
[ ] Ready to merge

Updating score made this happen?

I assume we're doing 1 patch/put/something per column?

Correct. I'm curious if that actually deleted the score object though? probably not. You would need to do it in admin/shell_plus I think.

Another thing, it is a bit strange we return IDs for each column, seems like we're sharing a bit too much, but probably not a huge concern?


Wacom.TabletDriver version 6.3.43-3

Closes #19658

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I always get the error Installer failed with exit code: 2. Is this maybe a success code, because the install goes through anyway?

@quhxl you might be able to contact the publisher or look at their documentation. If 2 is a success code, you can modify the manifest.


Can't send messages to copilot

Copilot Chat Extension Version: 0.23.2
VS Code Version: 1.96.2-1734607745 (amd64 deb)
OS Version: Pop os 22.04

Steps to Reproduce:

Open chat window on the right side of vscode
Ask any question, regardless of whether files are attached or not
Nothing happens when I press enter or send button. Have to wait for about 5 or so minutes then it starts working as normal. Changing the models doesn't seem to help either

Can you share a screen capture of your experience? Also, some information about the workspace you have open might be helpful. Does restarting VS Code have any effect?


xcrun: error: SDK "iphonesimulator" cannot be located

You have to open XCode, then go to Downloads, and download the latest Simulator (like 9.0)

Should be fixed now with #3


Mods with their own water-rendering blocks don't add color

Water is missing color when it's in the sink from cooking for blockheads (tested with 1.6.3)

This also affects Thaumcraft; I'll merge #55 into this so we don't have multiple reports of the same problem at once.
I'm working on a fix (by changing the way textures are handled) but it'll take a bit.

Fixed in 1.7.0. I've now adjusted the mod to use its own aquaacrobatics namespace for the water placed in the world, while still providing a colorized texture under the minecraft namespace. This should ensure mods like these which assume the texture has a color continue to work properly.


i18n(fr): update guides/components and add syncKey to various pages

Description
This PR updates the French version of the guides/components.mdx page with the changes of #640.
It also adds the syncKey prop to the French version of the following pages as it felt small enough to be done in one go:

getting-started.mdx
guides/css-and-tailwind.mdx
guides/customization.mdx

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
getting-started.mdx
Localization changed, will be marked as complete.

fr
guides/components.mdx
Localization changed, will be marked as complete.

fr
guides/css-and-tailwind.mdx
Localization changed, will be marked as complete.

fr
guides/customization.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Thanks for the review 🙌


Use Opus as the main codec

Opus is the best audio codec there is, better than Vorbis (and better than MP3 or others) by basically every measure. Seems ideal to favor Opus as the default for every place and certainly to support playing Opus files.

Opus playback works if your system's libav/ffmpeg library was compiled with it, which is the default in most package managers.
I agree that opus might be an even better candidate than vorbis for the default streaming codec.
duplicate of #144


Add fs validator

Add missing validator and ensure the tests pass

Can please provide feedback on this PR?

Ancient PR on a project that looks abandonned, closing.


⚠ Empornium has degraded performance

In b609576, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 1412 ms

Resolved: Empornium performance has improved in d39ab98.


add text "The order of operations is the rules in which an expression shou…

…ld be undertaken and in which order." to article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

All three of your PRs (#26388 , #26382 , #26396) are small additions to the same file. They should be made as a single PR.


Merge develop into main for 2.0.0

Description
Merges develop into main for version 2.0.0. This includes the following breaking API change:

Renames features property on A11yoopMonitor to allFeatures.

Type of change
Please delete options that are not relevant.

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Unit tests, ensured the preview app is still functional and performed manual testing.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Codecov Report

Merging #11 (5cbdef1) into main (7d7405c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        19    +3
  Lines          234       246   +12
=========================================
+ Hits           234       246   +12

Impacted Files
Coverage Δ

...ure/Extensions/A11yFeature+AsAnalyticsParams.swift
100.00% <ø> (ø)

...A11yFeature/Extensions/A11yStatus+IsDisabled.swift
100.00% <100.00%> (ø)

.../A11yFeature/Extensions/A11yStatus+IsEnabled.swift
100.00% <100.00%> (ø)

...Feature/Extensions/A11yStatus+IsNotSupported.swift
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Abandoned Project? (Question that answers itself)

Looks like this is abandoned ... but there isn't actually any other option for Xdebug w/ Atom.
I have it 'working', but that's a loose definition since there's some weird side effects happening that I'm unsure if they are caused by Xdebug3, or this repo, or the atom-debug-ui ...
Came here to file the bugs/errors ... and wondering if it's worthwhile.   Tagging @gwomacks and @cchamplin to see if there's any response.  :-/

Well darn! Seems that I'll have to move along.


Add an "observable" concept and corresponding unit test

observable is a very useful pattern, and now that autowiring has signals, should be easy to add.  Implement an observable concept built as a wrapper around a value type.

This is simple and nice to use. Tests passed successfully.


Static 'Initialize' factory method on structs with cbSize fields

Instead of:
var cursorInfo = new CURSORINFO { cbSize = (uint)Marshal.SizeOf(typeof(CURSORINFO)) };

What if we could write:
var cursorInfo = CURSORINFO.Initialize();

And Initialize would use either sizeof or a constant calculated at compile time whenever possible rather than calling Marshal.SizeOf?
(Allowing structs to have default constructors is being discussed for future C# versions.)
BITMAPINFOHEADER has biSize rather than cbSize.

Note that Marshal.SizeOf may not return the correct size for libraries using blitting instead of the classic marshaling layer. There are some field types that will cause the classic marshaling layer to jump in even if the type is blittable, most notably bool fields have different size and alignment for marshaling vs. blitting.
Just wanted to throw that in because I suspect this library is going to use blitting where possible?

Marshal.SizeOf for classic marshalling size
Marshal.OffsetOf for classic marshalling offsets
sizeof keyword for blitting size
pointer arithmetic for blitting offsets

Example where it makes a difference:
public struct Sample
{
    public int a;
    public bool b;
    public short c;
}

var sample = new Sample();
var blittingSize = sizeof(Sample);                              // 8
var blittingOffset = (byte*)&sample.c - (byte*)&sample;         // 6
var marshalSize = Marshal.SizeOf<Sample>();                     // 12
var marshalOffset = Marshal.OffsetOf<Sample>(nameof(Sample.c)); // 8

This happened to cause bugs twice in the WinForms interop cleanup (PRINTDLG and MCGRIDINFO). Whether it is an issue for this library depends strongly on how the mappings are generated (i.e. does it use managed bool in structs ever)

That is horrifying. Thanks for enlightening me on this, @weltkante.
Yes, today all our structs are blittable, but that will not always be the case going forward. I wonder what determines whether a blittable struct will be laid out the marshaled way or the blitted way (when blitting isn't required by using a pointer to it in the p/invoke signature.)
@tannergooding Can you please enlighten us here?

As far as I'm aware blitting is used when you use pointers or Span, classic marshaling is used for ref, out and arrays. In WinForms they switched some p/invoke signatures to explicitly not receive ref arguments but pointers to structs, so it can use blitting and avoid classic marshaling overhead.

You may be right, but it's alarming to think that changing a p/invoke signature from [Out] struct* to out struct would change the layout.

Can you please enlighten us here?

https://docs.microsoft.com/en-us/dotnet/standard/native-interop/best-practices#blittable-types covers what is and is not blittable. In particular:

bool is the only value type that is "never" blittable, because it is always normalized to 0 or 1 on return, even if you explicitly annotate it as UnmanagedType.U1.
char is "sometimes" blittable and requires you to mark the method, type, or field as CharSet.Unicode

For char, the behavior can also differ between targets and scenarios (COM vs P/Invoke or Windows vs Linux) and is one reason why win32metdata (and ClangSharp) explicitly use ushort. Doing this means the interop bindings need to insert a cast from char* to ushort* or char to ushort, but it avoids needing to concern yourself with how char is handled by any given scenario.

Arrays and strings as individual parameters have blittable contents and can be pinned and passed instead (assuming the CharSet matches for char/string). When they exist as a field of a struct, the struct is no longer blittable and requires marshalling.
[Out] and [In] have no impact on blittable parameters or parameters which are only pinned (that is which don't require marshalling). They largely only impact marshalling behavior and will fail for [Out] string as mutating strings is disallowed.
That is, [In] int[] has no impact because the int[] is just pinned and pointer to index 0 is passed. If the native method is not actually [In] and writes to the pointer then the array will observe the mutation. This is also true of string (when CharSet.Unicode for P/Invoke, I don't recall the rules for COM), ref int, out int, and in int. In all cases the contents of the reference are blittable, so the reference is pinned and a pointer to the pinned contents is passed.
While [In] and [Out] do impact cases like struct S { int value; string s; } because the struct is no longer blittable and so the marshaller must create a copy of the struct that is of the correct layout for native.

[In] will have the marshaller allocate memory, marshal the contents, call the native method, and then finish
[Out] will have the marshaller allocate memory, call the native method, marshal the modifications back to managed, and then finish
[In, Out] will do both, that is: the marshaller allocate memory, marshal the contents, call the native method, marshal the modifications back to managed, and then finish

win32metadata should be defining purely blittable structs and P/Invokes with the correct packing information (outside any bugs) and so Unsafe.SizeOf<T> should be the same as sizeof(T) should be the same as Marshal.SizeOf<T>

The forced pinning of references (especially ref T, out T, and in T) also means that there is unnecessary overhead for the case where the reference is to a stack value or where you are repeatedly passing the same parameter to native as a ref.
For example, int QueryPerformanceFrequency(long* lpFrequency); (which is BOOL QueryPerformanceFrequency(LARGE_INTEGER *lpFrequency); in native)  is most commonly used as something similar to:
long frequency;
var result = QueryPerformanceFrequency(&frequency);

Debug.Assert(result != 0); // QPC can't fail on WinXP or later
return frequency;

While if you instead had a P/Invoke of bool QueryPerformanceFrequency(out long lpFrequency);, then you might write:
var result = QueryPerformanceFrequency(out long frequency);
Debug.Assert(result); // QPC can't fail on WinXP or later
return frequency;

But this will actually generate something similar to (while the blittable signature doesn't require a shim and can have the transition logic inlined in newer versions of .NET):
var result = QueryPerformanceFrequencyShim(out long frequency);
Debug.Assert(result); // QPC can't fail on WinXP or later
return frequency;

bool QueryPerformanceFrequencyShim(out long frequency) // will not be inlined
{
    fixed (long* pFrequency = &frequency)
    {
        return QueryPerformanceFrequency(pFrequency) != 0;
    }
}

bool is the only value type that is "never" blittable, because it is always normalized to 0 or 1 on return, even if you explicitly annotate it as UnmanagedType.U1

Right, sorry, I always forget that blittable terminology no longer matches what it used to mean, bool has been enabled to act as if blittable in these scenarios, even if it isn't named such. That was specifically enabled here dotnet/runtime#13772 (issue) and here dotnet/runtime#1866 (PR).

Right, although that is slightly different. That is allowing pointers to unmanaged types to act as blittable and not incur marshalling (because its just a pointer and therefore the user is assumed to know what they're doing).
In that scenario, the bool is not normalized. Same for say char*.

For char, the behavior can also differ between targets and scenarios (COM vs P/Invoke or Windows vs Linux) and is one reason why win32metdata (and ClangSharp) explicitly use ushort. Doing this means the interop bindings need to insert a cast from char* to ushort* or char to ushort, but it avoids needing to concern yourself with how char is handled by any given scenario.

Ya, but that also means we lost precision in the metadata. We can't tell from ushort[] in the metadata whether we should project that as char[] because it really represents characters or if it really represents an array of numbers. Similar with sbyte[] (which boggles the mind BTW--why would anyone use signed integers to represent ASCII or UTF-8 encoded characters?).
If .NET in particular has issues with non-blittable scenarios for char the metadata shouldn't concern itself with that. It should still use char which is the semantic match for a UTF-16 encoded character, and leave it to the projections to make that be ushort* if that's helpful for blitting, IMO.
But all that's aside from the question I posed originally, which is given a blittable struct that report different sizes from sizeof<struct> vs Marshal.SizeOf<struct>(), which size should I use when the p/invoke method takes that struct as a parameter with no [MarshalAs] attribute on it? Will .NET blit the struct (therefore sizeof will predict its size) or will it marshal the struct, and therefore I should use Marshal.SizeOf<T>?

win32metadata should be defining purely blittable structs and P/Invokes with the correct packing information (outside any bugs) and so Unsafe.SizeOf<T> should be the same as sizeof(T) should be the same as Marshal.SizeOf<T>

That would be great. So in @weltkante's example where they are different, is it because he uses bool for one of the fields, and thus we should always use the BOOL type as described in the metadata?
Regarding your shim and inlining thoughts, I didn't fully follow you. But here is what CsWin32 currently generates for your example method:
internal static unsafe bool QueryPerformanceFrequency(out long lpFrequency)
{
    fixed (long *lpFrequencyLocal = &lpFrequency)
    {
        bool __result = PInvoke.QueryPerformanceFrequency(lpFrequencyLocal);
        return __result;
    }
}

[DllImport("Kernel32", ExactSpelling = true, SetLastError = true)]
internal static extern unsafe bool QueryPerformanceFrequency([Out] long *lpFrequency);

So we're in-between. The return type is bool but we do use a pointer for the parameter, and then we offer an easier overload that exposes out long. Were you saying that our friendly overload would be inlined? Or if not, what exactly were you suggesting to enable inlining?

why would anyone use signed integers to represent ASCII or UTF-8 encoded characters?

Because that's how char is treated in most C/C++ compilers by default and because it trivializes the check of "is ascii" to "is positive". Modern .NET opted to use Span<byte> in most of its APIs, but .NET (back to 1.1) has always had the new string(sbyte*) overloads for handling 8-bit character strings.

C/C++ do not have a "proper" int8 vs char type, instead they have char which is implementation defined, signed char, and unsigned char. Where MSVC, GCC, and Clang opt to treat char as signed by default.

It should still use char which is the semantic match for a UTF-16 encoded character, and leave it to the projections to make that be ushort* if that's helpful for blitting, IMO.

There are numerous problems here including that char for Windows APIs is a mapping of wchar_t which is not always UTF16. It is 2-bytes on Windows, but 4 bytes on Unix and the backing tool for win32metadata (ClangSharp) needs to support that.
Additionally, the default behavior of char is incorrect for most scenarios as it is marshaled as ASCII by default, not blitted as UTF16 and so the backing metadata would become even more bloated by marshal attributes where it is only important from the actual marshalling perspective that it is 2-bytes or 1-byte. Because of this, ClangSharp opts to map to exact types that are guaranteed to be 1-to-1 and result in no possible overhead or ambiguities.
It does result in more overhead on the generator, but that is something that it should be able to handle. The SAL annotations and/or docs are what need to tell you if the input is a string, an array, or a pointer to a single value (and if it is in, out, or ref). This is already true for UTF8 strings and many of the other pointers it encounters and it should be trivial (in my experience) to extend those same checks to string and .NET's char.

But all that's aside from the question I posed originally, which is given a blittable struct that report different sizes from sizeof vs Marshal.SizeOf(), which size should I use when the p/invoke method takes that struct as a parameter with no [MarshalAs] attribute on it?

Marshal.SizeOf is the only correct value with regards to marshaling. It represents the "native" size of the type where sizeof represents the managed size.
When the types are blittable, these two are equal; but just because they are equal does not mean you have blittable data because cases like bool are never blittable.

So in @weltkante's example where they are different, is it because he uses bool for one of the fields, and thus we should always use the BOOL type as described in the metadata?

Yes, bool is a non-blittable as a value type and will result in marshalling even if you explicitly set the marshal size to 1

In .NET 5 and newer you can sometimes blit pointers that are or indirectly contain a bool

The return type is bool but we do use a pointer for the parameter, and then we offer an easier overload that exposes out long. Were you saying that our friendly overload would be inlined? Or if not, what exactly were you suggesting to enable inlining?

Returning bool from the P/Invoke means that the runtime has to insert a marshaling stub that handles the GC transition and also normalizes the boolean value. This will likely not get inlined today and you are better off returning int (which is the backing type for the BOOL typedef) and having the marshaller do a != 0 check (or an alternative appropriate check for the other bool types you can encounter).

win32metadata should be defining purely blittable structs and P/Invokes with the correct packing information (outside any bugs) and so Unsafe.SizeOf<T> should be the same as sizeof(T) should be the same as Marshal.SizeOf<T>

@tannergooding  -- That's a good, succinct, and (importantly) testable requirement.
Is there currently a unit test / CI validation step that checks that this is true for all win32metadata structs and P/Invokes?

Is there currently a unit test / CI validation step that checks that this is true for all win32metadata structs and P/Invokes?

ClangSharp supports generating such tests. I am not aware if win32metadata is currently using this functionality. I'm also not aware if they have their own equivalent or not.

ClangSharp supports generating such tests. I am not aware if win32metadata is currently using this functionality. I'm also not aware if they have their own equivalent or not.

Oops!  Sorry, I lost track of which depot I was in.  I'll open an issue (suggestion) in the win32metadata depot.

The metadata now includes [StructSizeField("cbSize")] on all structs with cbSize fields.

@mikebattista To adopt this to automated initializing the field, we may want CsWin32 to be able to determine whether a struct is a variable length struct, so that the Initialize method or ctor can take a value for the length of its last field. I'm trying to remember whether something in the metadata identifies the variable length structs. Do you know?

Variable length meaning with a flexible array member as the last field?

I suppose that's one manifestation of it. I'm not sure all variable length structs end with such a field. I vaguely recall a case where the docs simply indicate that the struct acts as a header to a larger buffer.

See https://github.com/microsoft/win32metadata/blob/main/docs/projections.md#:~:text=Flexible array members at the end of a struct are decorated with [FlexibleArray] (%23912) for the flexible array member scenario.
I'm not aware of anything else in the metadata. If it can't be progamatically scraped, then it would need to be manually attributed.


XFA - Move the fake HTML representation of XFA from the worker to the main thread

the only goal of this patch is to be able to get synchronously the fake html when printing from firefox:

in order to print we need to inject some html in beforeprint callback but we cannot block in waiting for all the pages.

from a memory point of view: it doesn't change anything since the fake HTML is deleted in the worker;
this way we don't break any assumptions.

/botio test


IziToast is not defined in php

I am using izitoast to echo the notification in the php login page after the from is submitted i am getting the error like iziToast is not defined.I have succesfully imported the css and js files of izitoast

I am using izitoast to echo the notification in the php login page after the from is submitted i am getting the error like iziToast is not defined.I have succesfully imported the css and js files of izitoast

Are you sure you included the library correctly right before the PHP output-caller?


New version: EQAditu.AdvancedCombatTracker version <IP_ADDRESS>0

Pull request has been created with WinGet Automation 🪟📦🤖
Microsoft Reviewers: Open in CodeFlow

InstallerUrl contains Manifest version instead of PR version:
InstallerUrl: https://github.com/EQAditu/AdvancedCombatTracker/releases/download/<IP_ADDRESS>9/ACTv3-Setup.exe
(Automated message - build 601)


python312Packages.cerberus: 1.3.5 -> 1.3.6

Diff: https://github.com/pyeve/cerberus/compare/refs/tags/1.3.5...1.3.6
Changelog: https://github.com/pyeve/cerberus/blob/1.3.6/CHANGES.rst

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369027

x86_64-linux

:x: 16 packages failed to build:

ansible-lint
ansible-lint.dist
ansible-navigator
ansible-navigator.dist
molecule (python312Packages.molecule)
molecule.dist (python312Packages.molecule.dist)
python312Packages.ansible-compat
python312Packages.ansible-compat.dist
python312Packages.ansible-kernel
python312Packages.ansible-kernel.dist
python312Packages.ansible-runner
python312Packages.ansible-runner.dist
python312Packages.pytest-ansible
python312Packages.pytest-ansible.dist
python313Packages.riscof
python313Packages.riscof.dist

:white_check_mark: 53 packages built:

ansible (ansible_2_17 ,python312Packages.ansible-core)
ansible-later
ansible-later.dist
ansible.dist (ansible_2_17.dist ,python312Packages.ansible-core.dist)
ansible_2_16
ansible_2_16.dist
napalm
napalm.dist
peering-manager
pyditz
pyditz.dist
python312Packages.ansible
python312Packages.ansible-vault-rw
python312Packages.ansible-vault-rw.dist
python312Packages.ansible.dist
python312Packages.cerberus
python312Packages.cerberus.dist
python312Packages.deal
python312Packages.deal.dist
python312Packages.eve
python312Packages.eve.dist
python312Packages.icontract
python312Packages.icontract.dist
python312Packages.napalm
python312Packages.napalm-hp-procurve
python312Packages.napalm-hp-procurve.dist
python312Packages.napalm.dist
python312Packages.pylddwrap
python312Packages.pylddwrap.dist
python312Packages.pytest-testinfra
python312Packages.pytest-testinfra.dist
python312Packages.riscof
python312Packages.riscof.dist
python312Packages.riscv-config
python312Packages.riscv-config.dist
ttp (python312Packages.ttp)
ttp.dist (python312Packages.ttp.dist)
python312Packages.vaa
python312Packages.vaa.dist
python313Packages.cerberus
python313Packages.cerberus.dist
python313Packages.deal
python313Packages.deal.dist
python313Packages.eve
python313Packages.eve.dist
python313Packages.icontract
python313Packages.icontract.dist
python313Packages.pylddwrap
python313Packages.pylddwrap.dist
python313Packages.riscv-config
python313Packages.riscv-config.dist
python313Packages.vaa
python313Packages.vaa.dist


check invalid proposal amounts

add tests for misc.is_numeric
add numeric validation to Proposal.payment_amount
do not import proposals from dashd if the payment_amount is invalid
purge existing invalid DB entries

Should fix #23


🐞 TUI display incorrect when sdk crash with exception

What is the issue?
From https://github.com/wingyplus/kaogeek-discord-bot/tree/dagger/deployment
I accidentally set export to docker.io/kaogeek and found crash when running in auto provisioning mode. When running with TUI feature I see all pass at first but it hide the crash log in the first step and step export not show in the TUI. I expected to see the step is a failure at least and may show the export step failure, this could spot the problems more easier.
Log output
Auto provisioning mode:
file:///Users/thanabodee/src/github.com/creatorsgarten/kaogeek-discord-bot/deployment/node_modules/.pnpm/@dagger.io+dagger@0.5.3/node_modules/@dagger.io/dagger/dist/api/utils.js:144
                throw new GraphQLRequestError("Error message", {
                      ^

GraphQLRequestError: Error message
    at file:///Users/thanabodee/src/github.com/creatorsgarten/kaogeek-discord-bot/deployment/node_modules/.pnpm/@dagger.io+dagger@0.5.3/node_modules/@dagger.io/dagger/dist/api/utils.js:144:23
    at Generator.throw (<anonymous>)
    at rejected (file:///Users/thanabodee/src/github.com/creatorsgarten/kaogeek-discord-bot/deployment/node_modules/.pnpm/@dagger.io+dagger@0.5.3/node_modules/@dagger.io/dagger/dist/api/utils.js:5:65)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  cause: ClientError: open /Users/thanabodee/src/github.com/creatorsgarten/kaogeek-discord-bot/deployment/docker.io/kaogeek: no such file or directory: {"response":{"data":null,"errors":[{"message":"open /Users/thanabodee/src/github.com/creatorsgarten/kaogeek-discord-bot/deployment/docker.io/kaogeek: no such file or directory","locations":[{"line":2,"column":58719}],"path":....

TUI:

Steps to reproduce
Provisioning mode run by pnpm build. And TUI mode run with _EXPERIMENT_DAGGER_TUI=1 dagger run pnpm run build.
SDK version
nodjs sdk 0.5.3
OS version
macOS 13.1 (22C65)

I think that this one is duplicate of https://github.com/dagger/dagger/issues/5150. WDYT @vito?

@gerhard Hard to say, this one's a bit easier to tell what went wrong so I addressed it in #5232


Cannot make it work with serverless 1.72.0

Hi,
I have an issue making the plugin work with serverless 1.72.0. I just installed so I cannot confirm if it was working with a previous version, but I tested serverless 1.69.0 with no success. I've tried setting my parameter both in the serverless-offline-ssm section and in .env file.
When running sls offline start --stage dev, I get:
Serverless: serverless-offline-ssm checking serverless version 1.72.0.
 Serverless Warning --------------------------------------
  A valid SSM parameter to satisfy the declaration 'ssm:/test_param~true' could not be found.

package.json:

    "serverless": "^1.72.0",
    "serverless-domain-manager": "^3.2.2",
    "serverless-dynamodb-local": "^0.2.35",
    "serverless-offline": "^6.3.1",
    "serverless-offline-sqs": "^2.0.2",
    "serverless-offline-ssm": "^5.0.1",
    "serverless-plugin-git-variables": "^3.3.1",
    "serverless-python-requirements": "^4.3.0"

plugins section of serverless.yml:

  - serverless-python-requirements
  - serverless-domain-manager
  - serverless-dynamodb-local
  - serverless-offline-sqs
  - serverless-offline-ssm
  - serverless-offline
  - serverless-plugin-git-variables

custom section of serverless.yml:

custom:
  serverless-offline-ssm:
    stages:
      - dev
    ssm:
      'test_param': 'placeholder'

I also have at the root of my package a .env file:

test_param=placeholder

Could it be a conflicting plugin? I've tried disabling them one by one but it did not solve the issue. Would you have any idea about why it does not work?
Thank you very much.

@alxch Can you please provide a sample project or repository in which this happens, I am unable to reproduce it currently.

Thank you for trying to reproduce.
I finally found where my issue was coming from. When referring to my SSM params, I was using ${ssm:/test_param~true} (see the / as a prefix). This is actually equivalent to ${ssm:test_param~true} when querying the parameters from AWS. See this doc:

The systems treats both of the following parameters as root parameters.
/parameter-name
parameter-name

However, it seems that the plugin does not have the same behavior. It will try to find the exact parameter (with the / prefix) from .env, and complain because it cannot find it. I just got bitten by this!

Ah, ok, I see that now. It's likely to do with the regex that reads the ssm name from the yaml file. I feel like the leading / was something I wasn't using or wasn't supported when I first wrote this. I'll see if I can add that support and get a fix released.

Thank you for trying to reproduce.
I finally found where my issue was coming from. When referring to my SSM params, I was using ${ssm:/test_param~true} (see the / as a prefix). This is actually equivalent to ${ssm:test_param~true} when querying the parameters from AWS. See this doc:

The systems treats both of the following parameters as root parameters.
/parameter-name
parameter-name

However, it seems that the plugin does not have the same behavior. It will try to find the exact parameter (with the / prefix) from .env, and complain because it cannot find it.

Hi @alxch- can you give me an example please?. I have the same problem here.
This is my configuration:
Offline SSM:
serverless-offline-ssm:
    stages:
      - local
    ssm:
      'greeting': 'Hi local'

Plugins:
plugins:
  - serverless-stage-manager
  - serverless-webpack
  - serverless-dynamodb-local
  - serverless-offline-ssm
  - serverless-offline

Environment variables:
  environment:
    AWS_NODEJS_CONNECTION_REUSE_ENABLED: 1
    GREETING: ${ssm:greeting~true}

I have the same issue using .env file.
Thanks in the advance!


BibDocFile:Download all files function

Originally by switowsk (@switowski) on 2014-01-10
To facilitate the downloading of all files for records with a lot of files attached, it should be possible to download all files with one click (for example packed as .tar archive).

@switowski can you make a PR for cds-ops?

@ludmilamarian yes, but I need to fix the code first (it's not working after rebase)

Since we are deploying this on CDS, I have rebased the code and created a PR: #2820

@switowski it will be closed automatically if you put (closes #1673) in the commit message in #2820.

@jirikuncar :ok_hand:

Closed by fa009b4397c2749dd9cec1c0b877d4d9524b7b73.


Scala 2.12.2 and style

Style is now enforced by travis according to scalafmt. New PR should run sbt scalafmt before being opened.

You have to reformat the whole repo.

BuildInfo is something generated by the compilation :/. I will try a clean before, but my repo is corrupted...

Can you blacklist it?


JFXListView and GridPane

Hello!
There is a problem with rippler that its under the gridpane when I'm using this code:
<JFXListView maxHeight="-Infinity" maxWidth="-Infinity" prefHeight="499.0" prefWidth="220.0">
     <GridPane>
         <columnConstraints>
             <ColumnConstraints hgrow="NEVER" percentWidth="30.0" halignment="CENTER"/>
             <ColumnConstraints hgrow="NEVER" percentWidth="70.0"/>
         </columnConstraints>
         <rowConstraints>
             <RowConstraints prefHeight="55" vgrow="NEVER"/>
         </rowConstraints>
         <FontAwesomeIconView glyphName="POWER_OFF" size="26px"/>
         <Label text="TURN OFF" GridPane.columnIndex="1"/>
     </GridPane>
     <GridPane>
         <columnConstraints>
             <ColumnConstraints hgrow="NEVER" percentWidth="30.0" halignment="CENTER"/>
             <ColumnConstraints hgrow="NEVER" percentWidth="70.0"/>
         </columnConstraints>
         <rowConstraints>
             <RowConstraints prefHeight="55" vgrow="NEVER"/>
         </rowConstraints>
         <FontAwesomeIconView glyphName="POWER_OFF" size="26px"/>
         <Label text="TURN OFF" GridPane.columnIndex="1"/>
     </GridPane>
</JFXListView>

And there is no problem when I'm using this code, but I have to use prefWidth to every cell which i dont like:
<JFXListView maxHeight="-Infinity" maxWidth="-Infinity" prefHeight="499.0" prefWidth="220.0">
     <Label prefWidth="200.0">
         <graphic>
             <GridPane>
                 <columnConstraints>
                     <ColumnConstraints hgrow="NEVER" percentWidth="30.0" halignment="CENTER"/>
                     <ColumnConstraints hgrow="NEVER" percentWidth="70.0"/>
                 </columnConstraints>
                 <rowConstraints>
                     <RowConstraints prefHeight="55" vgrow="NEVER"/>
                 </rowConstraints>
                 <FontAwesomeIconView glyphName="POWER_OFF" size="26px"/>
                 <Label text="TURN OFF" GridPane.columnIndex="1"/>
             </GridPane>
         </graphic>
     </Label>
     <Label prefWidth="200.0">
         <graphic>
             <GridPane>
                 <columnConstraints>
                     <ColumnConstraints hgrow="NEVER" percentWidth="30.0" halignment="CENTER"/>
                     <ColumnConstraints hgrow="NEVER" percentWidth="70.0"/>
                 </columnConstraints>
                 <rowConstraints>
                     <RowConstraints prefHeight="55" vgrow="NEVER"/>
                 </rowConstraints>
                 <FontAwesomeIconView glyphName="POWER_OFF" size="26px"/>
                 <Label text="TURN OFF" GridPane.columnIndex="1"/>
             </GridPane>
         </graphic>
     </Label>
</JFXListView>

Preview: http://imgur.com/7azWQFp
Is it bug?

Hello,
Well this is not a bug, you just need to add the property mouseTransparent="true" to the GridPane in order to pass the mouse click event to the rippler.
Regards,

Sorry, forgot about it. Now it works.
Thank you so much!


Add ServiceMonitor in helm chart (#6157)

Which issue(s) this PR fixes:

Issue # https://github.com/longhorn/longhorn/issues/7864, https://github.com/longhorn/longhorn/issues/7041
What this PR does / why we need it:
Backport to v1.5.x
Special notes for your reviewer:
Additional documentation or context

@mantissahz you forgot to sign off the PR.


Unable to send email via SMTP

Hi,
I am unable to send emails via SMTP from external app. Apart from that everything else working fine. I am able to connect over web API and send emails. Also emails are going through postal web ui.
Basically, the error I am getting is
"Failed to authenticate on SMTP server with username "swhsv-mail" using 2 possible authenticators"
Port 25 is open for both outgoing and incoming traffic.
Thanks

I am able to connect over web API and send emails.

Have you created a separate SMTP credential for use with SMTP?

Yes, I did. In fact, when I tested Postal with smpter.net it works flawlessly, but not working with EMA like Mailwizz.

Ah good find. Have you tested with a secure connection from smtper.net?
It is possible that you need to specify what kind of authentication Mailwizz is using. You can see precise details by clicking on this link on the Credentials page

Secure connection from smtper.net is not working. I did the test with precise details. Basically, in Mailwizz it's failing to authenticate in the first place. I also couldn't see anything in the log s for Mailwizz or perhaps I have been looking at the wrong place.

If you're able to have a look at smtp_server.log you should see what, if any, messages were sent from smtper.net and Mailwizz. There may be other messages from people poking around for port 25 so don't be disheartened at the first failure you see!

Yes, I could see people poking around. They were so many I am unable to locate relevant logs.

did you set tls_enabled: true and fill out the certificates in the config file?

Yes, I did. I also installed Let's Encrypt certificate.

Though Postal says it support AUTH CRAM-MD5 PLAIN LOGIN but when CRAM-MD5 is tried, it says access denied and accept LOGIN. Do you think that would be the case with MailWizz or other SMTP software.

Decoding your attempt at CRAM-MD5 it looks like you didn't specify the username as swdlv/swdlv (or whatever made the response didn't include some of the username). AUTH PLAIN is simpler in this case because Postal does not verify the username.

Yes, you are right. I also realized this.
Thank you very much for prompt reply.


editor.experimentalEditContextEnabled breaks text input in aux editors

Type: Bug
If I enable editor.experimentalEditContextEnabled then I'm unable to type (add new text) in aux editors. Removing text works
Steps to reproduce:

Set "editor.experimentalEditContextEnabled": true
Open text editor in main window and try to type - text should be entered as usual
Drag editor to create aux window
Try to type text in aux editor - nothing added (while all letters are registered in screencast mode)

Backspace, Del, Ctrl+/ and other shortcuts work as expected

https://github.com/user-attachments/assets/47fe620a-8c9c-4208-bcb6-6c3424049d51
VS Code version: Code - Insiders 1.94.0-insider (c43f508b732d24b0c4732de9db2b38b4c5b88b8a, 2024-09-26T05:04:07.935Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2996)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.50GB (13.12GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions disabled

/assign aiday-mar -jrieken

Hi yes thank you for filing this valuable issue. I am able to reproduce this both on insiders.vscode.dev as well as on Desktop. This is a strange issue. I believe this could be a chromium/electron bug, will investigate.

After some discussion with the team, we will work on a workaround, which consists in instantiating the edit context in the newly created window. For that the window ID will have to be passed down into the editor/view constructor.

This issue will be closed as a workaround fix has been added.

Looks like "editor.experimentalEditContextEnabled": true, works for me in aux windows now. Unable to repro my previous problems.
Thanks!


Updating how Contract Extensions are made via CoC

Updating the guidelines around Business Events contract class extensions.
Removing the old docs which suggest using CoC over the buildContract method
Adding examples of how to make an extension class directly over the contract class.

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.

Closing PR to move to internal repo


Disable some blocks

Is it possible in the options to disable or replace some blocks ?
thks

Unfortunately not yet in this plugin 😬

I guess you do something like this to exclude some blocks from your editor instance.
excludedModules: [         "sect100",         "sect50",         "sect30",         "sect37",         "button",         "divider",         "text",         "text-sect",         "image",         "quote",         "grid-items",         "list-items",         "link-block",         "link"       ],
this.excludedModules.forEach(x =>         this.grapesEditor.BlockManager.remove(x)       );


Rename server_path from Omnisharp to OmniSharp

In the recent refactorings, the path to the omnisharp-roslyn server executable has been changed from 'OmniSharp' to 'Omnisharp'. This changes it back.

Oops, this is regression.  Thanks!


ci: add Node 16, 18 and 20 [version 3]

Fixes: N/A
Description
By adding more Node versions, we will be able to ensure compatibility across different Node major versions.

This PR will have to be broken into smaller parts:

Fix Jest tests
Fix Tape tests
Fix Selenium tests