Custom Action URL not sending forms payload in request

I need to handle form data submitted in my API. But when i test in preview with custom action url, forms payloads are net been sent in request.
I just added Custom Action URL in setting.
do i missed  something to configure. pls help

Please provide a JSFiddle showing the problem. That would help us determine the problem.

Closing this thread as it is outdated. Please re-open if it is still relevant. Thank you for your contribution!


v1.1 is not working

Am I doing something wrong? I am launching the .exe as an administrator, and it doesn't load. Doesn't seem like it is injecting.
I get "The type initializer for 'UnhollowerBaseLib.IL2CPP' threw an exception." as the error.

Run the game first, then run the injector.

Still doesn't work. I've tried that, that's actually the only way you would use this.

Works for me..

Works for me..

Really? Dang, I can't get this to work. It used to work before on my other PC. I guess something on my end doesn't allow it to work. Unfortunate.


Build Error: error: no matching function for call to ‘mlir::ValueTypeIterator

I'm trying to build triton from source, but got this error:

It seems like this<EMAIL_ADDRESS>But my gcc version is  8.3.0
How to solve this?

This error is solved by up to commit 7d54f2f0694ef341762bf37d86ea321b7e66f175. I use gcc 9 too.


Nuclide and monterey

https://nuclide.io/docs/features/remote/
I am not at all sure how to relate these two - but would like to keep this issue open

I have added this to our gitbook and we can create an issue for implementation when we decide to start working on it

What is "this" in the above comment? - the reference https://nuclide.io/docs/features/remote/ ?

Yes, we are thinking of doing something with nuclide but we are not sure exactly how, what or when

Perfect, thanks


ibc: fix logging of timestamp timeouts

During interchaintest integration work, @zbuc noticed that the logging message was structured. Loosely related to #4638 & #4636.

I just noticed that the timestamp used here is wrong, it should be using the consensus state timestamp. will fix

Marking this as consensus-breaking after the fact, because the diff makes substantive changes to how timeouts are handled. Please remove the label if inappropriate.


Skip first time experience on Appveyor

We already do that in EF.
https://github.com/aspnet/EntityFramework/blob/dev/appveyor.yml#L21


Cancelling a deployment

If accidentally deploying to a model that is currently being processed, Tabular Editor will just hang (with the spinning "Deploying..." dialog) until the model has finished processing. It should be possible to gracefully cancel the deployment in this case, instead of using Task Manager to kill Tabular Editor.
Also - the "Deploying..." dialog should not show on top of all other applications... 😆

Fixed in 2.8.1. Thanks @albertospelta !

Glad to help! Thank you for your wonderful job with this tool!


Warning: Source code contains analytics which load an external script called "MixPanel"

Author does not state this and I would consider it a hazard in this case.

Is there a reason why are you tracking everyones api in your own mixpanel?


Research all the changes necessary to support other OpenTelemetry deployments mode

During the initial work done the #916 we detected the need to change how we integrate with OpenTelemetry. To properly collect metadata from the Kubernetes cluster is necessary to run the OpenTelemetry collector in other deployments modes, like daemonset or deployments. However, as the Kubewarden stack components expected the collector to be run in a sidecar, this is not possible. Therefore, we need to changes the Kubewarden stack components (e.g. controller and policy server) to support sending metrics and tracing data to Otel collector running somewhere else.
The goal of this issue is to research all the changes required to make that possible.
Acceptance criteria

Map what changes are necessary to the controller to allow the communication with a Otel collector not running as a sidecar.
Map what changes are necessary to the policy server to allow the communication with a Otel collector not running as a sidecar.
Map the changes in the controller necessary to it to create policy servers properly configured to send data to Otel collector not running as a sidecar
Map the missing Helm chart configuration  to allow the Kubewarden components (after the changes described in the other acceptance criteria) to send data to remote Otel collectors.
Write an epic issue to keep track of the required changes

@kubewarden/kubewarden-developers please, review this epic issue about the Otel changes and let me know if you miss something.

@dev@kubewarden/kubewarden-develo I think we have a nice epic to work on and seems that all agree on how to do it. Therefore, I'm closing this issue. Let me know if you think we need something else to do in this spike.


Create Subset123 Authentic Test Data Request Process TDM

Subset123 is an authentic test data generating platform developed for the TELUS WLS, WLN, and FIFA domains that can quickly copy and append small and large subsets of data from sources, like Production and Staging, to targets, like Dev, Test/QA, and E2E.
URL
Go/TDM
Go/TestData
https://dmts-tdm.cloudapps.telus.com/
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Hi @Reemalnuweiri, I'm not sure if this was intended or not but can you provide more details as to what this is?


Fail to deploy any workload in PSP restricted cluster

Rancher Version
master 8/30 57508ebbaa08309b46b7766c76fff659c972e0a5
Steps to reproduce (least amount of steps as possible):

start rancher server by docker
Add a single node EC2 cluster with Pod Security Policy Support: enabled, Default PSP: restricted, everything else the default(v1.15.3-rancher3-1)
After the cluster is active, edit the Default project, change PSP to unrestricted.
Deploy a busybox deployment in the Default project.

Result:

Other details that may be helpful:
Error logs in rancher server:
2019/08/30 05:41:11 [ERROR] PodSecurityPolicyTemplateProjectBindingController c-p675b/psptpb-bx8x4 [PodSecurityPolicyTemplateProjectBindingsLifecycleHandler] failed with : error creating policy: the API version in the data (extensions/v1beta1) does not match the expected API version (policy/v1beta1)
2019/08/30 05:41:11 [ERROR] PodSecurityPolicyTemplateProjectBindingController c-p675b/psptpb-bx8x4 [PodSecurityPolicyTemplateProjectBindingsLifecycleHandler] failed with : error creating policy: the API version in the data (extensions/v1beta1) does not match the expected API version (policy/v1beta1)

looks related to v1.16 change @dramich

The bug is reproduced in master-head 57508ebba

The bug fix is validated in Rancher:master-head e50e71498
Following the same steps as the issue describes, now we can deploy workloads successfully.


x/vulndb: auto deploy database on changes

Currently when a new report is submitted, or a change to cmd/gendb is made, the database has to be manually re-generated and deployed by someone who has access to the GCS bucket (me, typically).

(This functionality has been implemented via the Vulndb-Deploy label and cloud build)


Deprecation: description will no longer be supported in createApiRef

Hello!
I wanted to bring to your attention that in a future release, the description option will no longer be supported in the createApiRef method. A list of all deprecations that will soon be removed can be found here: https://github.com/backstage/backstage/issues/8312.
Thanks!
:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes
[ ] Screenshots of before and after attached (for UI changes)
[ ] Added or updated documentation (if applicable)

@cmpadden Thank you for doing this, highly appreciated. May I just ask you to include changeset in the packages you have modified, please, so we can create release notes when PR is merged :)

@Irma12 No problem -- glad I can help.
I've added a change-set including all affected plugin packages. Let me know if this works for you!

@cmpadden Thank you! 🚢


⚠ BeyondHD has degraded performance

In 851a69a, BeyondHD ($BHD) experienced degraded performance:

HTTP code: 200
Response time: 2247 ms

Resolved: BeyondHD performance has improved in 0a234c5 after 6 minutes.


Donate page redirect breaks due to trailing slash

This is still broken on certain licenses pages – probably change all license redirects to donate.creativecommons.org, no?

This ought to be resolved now. Some static content had the bad donor URL instead of using donate.creativecommons.org like I would have expected.


Should autosaves be versioned?

If you load a storyfile for which you have an autosave from before I changed the stylehints protocol, the stylehints will be turned into CSS that no longer gets applied to the HTML.
While some changes to the autosave format could be handled so that they're backwards compatible (including this one), others might not be. So I'm wondering if the autosave should store a version number, and reject autosaves with an out of date version. It's tricky because there's three levels to consider, the VM, GlkApi, and GlkOte, and any of them could have a change in their autosave data. If an autosave is rejected, it needs to be rejected before any of the autosave state has been resumed. Should there be a function for each level that returns whether it accepts an autosave?

So the current process for doing an autorestore is:

VM.start() checks for the do_vm_autosave option.
If found it asks Dialog for an autosave.
If there's an autosave, then it processes the autosave:

First it gives the Glk snapshot to Glk.restore_allstate.
Glk.restore_allstate restores everything, and then saves the glkote data for later.

The VM processes its autosave data, and can now query Glk for existing objects.
The VM calls Glk.update().

Glk.update() includes the stored GlkOte data in its first update.

GlkOte.update() can finally process its autosave data.

So the first change that I think needs to happen is that the whole thing needs to be made async. This needs to happen because the Dialog library might be async (for IndexedDB), but it also allows for the possibility that GlkOte is across a network.
In order to allow for versioned autosaves we can make the autorestore functions return a success value. So the process would be changed to:

VM.start() checks for the do_vm_autosave option.
If found it asks Dialog for an autosave.
If there's an autosave, then it processes the autosave:

Checks the VM version, stops if out of date.
Calls Glk.restore_allstate.

Glk checks its version, returns 0 if out of date.
Calls GlkOte.restore_autosave

GlkOte checks its version, returns 0 if out of date.
Saves the data for later.
Returns 1.

If GlkOte returned 0 then Glk returns 0.
Glk restores everything.
Returns 1.

If Glk returned 0 then don't restore the autosave.
The VM processes its autosave data, and can now query Glk for existing objects.

The VM calls Glk.update().

Glk updates GlkOte

GlkOte uses its autosave data

The other change I'd like to make is for autosaves to not be JSON object and a RAM array, but instead be a single IFF file. This could be a Quetzal savefile, or just a custom IFF file if the VM doesn't use Quetzal. The VM, Glk, and GlkOte can store their data in their own chunks, so the different layers don't need to be responsible for including other layers data any more. The layers would not be required to use JSON either, if they want to store their data in a more efficient manner.
And for the purpose of #119, the Quetzal savefile format should be adjusted: introduce a new memory chunk XMem, which is the memory xored against the original memory, but without the CMem run length encoding. (Compressing at the end will be more efficient than Quetzal's basic RLE.) And also change the stack chunk to StNE, meaning Stack-Native-Endian, which just means that we don't ensure all the values are in big endian like Quetzal requires.
So all of this involves quite a few changes, which I think should happen all at the same time:

Autosaves should use an IFF format
If the VM uses Quetzal, change to XMem and StNe chunks
Add a version field to each layer's autosave data
Change the autorestore API to be async
Each layer checks its own version field and returns a success value

@erkyrath Any thoughts on any of this?

Oh, and for #130: making GlkOte display a notice when its autorestoring is easy enough, but it would be even better if it could have a "restart" button too. I haven't thought of a good way yet to send a restart-now signal up through the layers to the VM.

The autosaves should not just store versions, but also which library produced each. I don't have autosaves working in Emglken yet but I would like to. So I'm thinking now it would probably be better to have a separate chunk that stores both the library names and versions for each layer.


Partial for implementation

This is confusing. GitHub is still showing the IFormTemplate removal commit even though it's already merged into master. Did you want to try rebasing your branch?

Yep, I'll rebase it

You can keep the same pull request open if you force push to your remote branch after rebasing. No big deal either way, just FYI


Local tile fetcher

Description

What was changed in this pull request?

This lets tracks use a local tile fetcher and specify raw tile values.
Updates the the schema. Most of the changed files are just updates to viewconfs removing unnecessary fields

Why is it necessary?

Can make testing less reliant on having a server
Can be used by applications that want to display a track containing only a few values that can be stored directly in the viewconf.

Fixes #___
Checklist

[x] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[x] Unit tests added or updated
[x] Documentation added or updated
[o] Example(s) added or updated
[x] Update schema.json if there are changes to the viewconf JSON structure format

Allowed additionalProperties for data

[o] Screenshot for visual changes (e.g. new tracks or UI changes)
[x] Updated CHANGELOG.md

Just curious, how did you adjust all the test view confs to the updated schema?

Just went through and edited them. There was a period of time when we were exporting more fields than necessary. The change I made to the schema removed those fields and then I went though the test viewconfs and manually removed them.

Ok. Thanks. I thought there is maybe an automated way that I was not aware of.


Neo-cli AutoStart configuration updated

That you need to install the DBFTPlugin and set AutoStart to true in the plugin config file is not clear. I updated the documentation to make that more clear.

Did I make a pull request to the correct branch? Improve this doc send me to the new-release-neo3 branch


Refactor build and pipeline

I forgot to update .npmignore

@hfranklin did you mean to close this PR so you could submit a new one? Or did you close it by mistake?

Yes, I noticed something I missed.


⚠ Bofrost.de has degraded performance

In 800b97f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 911 ms

Resolved: Bofrost.de performance has improved in 59ef76a.


Ranges

Is it possible to add ranges validation?
Writing as issue because couldn't find support.
I see that Swagger spec allows min. and max. values and I would like to have that feature.

Yes, you can use annotations that are supported by typescript-json-schema
You have min/max examples here
https://github.com/YousefED/typescript-json-schema/blob/master/example/invoice/line.ts#L26-L38

Perfect. Thank you.


Add decrypted file handling

Add decrypted file handling download logic
add download_utils to build content downloader fullFilePath

shelving this for now


Remove version: Stackers.Stack version 3.3.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://binaries.getstack.app/builds/prod/win/x64/Stack Setup 3.3.0-x64.exe
Response status code does not indicate success: 530 ().
(Automated message - build 896)


Documentation for the Pega Customer Decision Hub destination

Added:

a new file 'PegaCDH.md' for our integration with Adobe Experience Platform

@adobe-documenation-team, please review

Signed Adobe CLA

Hi,
Thank you reviewing the documentation.
           How do I incorporate changes for all the comments?

           Work on the local branch ,do the  pull  request,  then  email to  ***<EMAIL_ADDRESS>?

Thanks
Tony
From: Victor Giurgiu @.>
Sent: Monday, July 11, 2022 4:50 PM
To: AdobeDocs/experience-platform.en @.>
Cc: Parakka, Tony @.>; State change @.>
Subject: ExtMsg: Re: [AdobeDocs/experience-platform.en] Documentation for the Pega Customer Decision Hub destination (PR #86)
CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.
@vgiurgiu commented on this pull request.
Thank you for submitting the documentation. I left some reviews that should be addressed before we can publish the documentation. Please let me know if you have any questions.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918300358:

@@ -0,0 +1,116 @@

+---
+title: Pega Customer Decision Hub connection
+description: Use the Pega Customer Decision Hub destination in Adobe Experience Platform to send profile attributes and segment membership data to Pega Customer Decision Hub for next-best-action decisioning.
+---

+# Pega Customer Decision Hub connection

+## Overview {#overview}

+Send profile attributes and segment membership data to Pega Customer Descision Hub for next-best-action decisioning.
Minor rephrasing suggestion to match the description in the metadata:
Use the Pega Customer Decision Hub destination in Adobe Experience Platform to send profile attributes and segment membership data to Pega Customer Decision Hub for next-best-action decisioning.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918300757:

@@ -0,0 +1,116 @@

+---
+title: Pega Customer Decision Hub connection
+description: Use the Pega Customer Decision Hub destination in Adobe Experience Platform to send profile attributes and segment membership data to Pega Customer Decision Hub for next-best-action decisioning.
+---

+# Pega Customer Decision Hub connection

We can delete two of the blank rows here. We only need one blank row between the # and ## headings

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918301763:

@@ -0,0 +1,116 @@

+---
+title: Pega Customer Decision Hub connection
+description: Use the Pega Customer Decision Hub destination in Adobe Experience Platform to send profile attributes and segment membership data to Pega Customer Decision Hub for next-best-action decisioning.
+---

+# Pega Customer Decision Hub connection

+## Overview {#overview}

+Send profile attributes and segment membership data to Pega Customer Descision Hub for next-best-action decisioning.

+Adobe Experience Platform Profile Segment membership, when loaded into Pega Customer Decision Hub, can be used as predictors in adaptive models and help deliver the right contextual and behavioral data for next-best-action decisioning purposes.
Minor rephrasing suggestion:
Profile segment membership from Adobe Experience Platform, when loaded into Pega Customer Decision Hub, can be used as a predictor in adaptive models and help deliver the right contextual and behavioral data for next-best-action decisioning purposes.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918308498:

+### Use case #1

+In Telco:

+A marketer wants to leverage insights from Data Science model-based next best action as delivered by Pega Customer Decision Hub for customer engagement, Pega Customer Decision Hub is heavily reliant on customer intent – for example "Interested_In_5G", "Interested_in_Unlimited_Dataplan" or "Interest_in_iPhone_accessories".

+### Use case #2

+In Financial Services:

+A marketer wants to optimize the offers for customers who subscribed or unsubscribed for Pension Plan or Retirement Plan newsletters. The financial services can ingest multiple CustomerID from their own CRM to Adobe Experience Platform, build segments from their own offline data, and send profiles that are entering and exiting the segments to Pega Customer Decision Hub for next-best-action (NBA) decisioning in outbound channels.

+## Prerequisites {#prerequisites}

+Before you use Pega Customer Decision Hub destination to export data out of Adobe Experience Platform:
Minor rephrasing suggestion, since all three prerequisites apply to something that users need to do in Pega:
Before you can use this destination to export data out of Adobe Experience Platform, make sure you complete the following prerequisites in Pega Customer Decision Hub:

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918309507:

+In Telco:

+A marketer wants to leverage insights from Data Science model-based next best action as delivered by Pega Customer Decision Hub for customer engagement, Pega Customer Decision Hub is heavily reliant on customer intent – for example "Interested_In_5G", "Interested_in_Unlimited_Dataplan" or "Interest_in_iPhone_accessories".

+### Use case #2

+In Financial Services:

+A marketer wants to optimize the offers for customers who subscribed or unsubscribed for Pension Plan or Retirement Plan newsletters. The financial services can ingest multiple CustomerID from their own CRM to Adobe Experience Platform, build segments from their own offline data, and send profiles that are entering and exiting the segments to Pega Customer Decision Hub for next-best-action (NBA) decisioning in outbound channels.

+## Prerequisites {#prerequisites}

+Before you use Pega Customer Decision Hub destination to export data out of Adobe Experience Platform:

+* Configure the Adobe Segment Membership Component in your Pega Customer Decision Hub instance.
as a Pega customer, would I know what this instruction means or do you think that we need to provide a bit more detail? Something like:
Configure the Adobe Segment Membership Component in your Pega Customer Decision Hub instance. You can do this in Pega by [...]

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918315611:

+# Pega Customer Decision Hub connection

+## Overview {#overview}

+Send profile attributes and segment membership data to Pega Customer Descision Hub for next-best-action decisioning.

+Adobe Experience Platform Profile Segment membership, when loaded into Pega Customer Decision Hub, can be used as predictors in adaptive models and help deliver the right contextual and behavioral data for next-best-action decisioning purposes.

+## Use cases

+To help you better understand how and when you should use the Customer Decision Hub destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.

+### Use case #1
Thanks for adding the use cases! Some minor comments here:
We can simplify the headings. Also, we don't need the italics italics, we can remove those. And I made some small adjustments to the paragraphs:
Telecommunications
A marketer wants to leverage insights from data science model-based next best action as delivered by Pega Customer Decision Hub for customer engagement. Pega Customer Decision Hub is heavily reliant on customer intent – for example "Interested_In_5G", "Interested_in_Unlimited_Dataplan" or "Interest_in_iPhone_accessories".
Financial services
A marketer wants to optimize the offers for customers who subscribed or unsubscribed from Pension Plan or Retirement Plan newsletters. Financial services companies can ingest multiple Customer IDs from their own CRMs into Adobe Experience Platform, build segments from their own offline data, and send profiles that are entering and exiting the segments to Pega Customer Decision Hub for next-best-action (NBA) decisioning in outbound channels.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918316332:

+In Financial Services:

+A marketer wants to optimize the offers for customers who subscribed or unsubscribed for Pension Plan or Retirement Plan newsletters. The financial services can ingest multiple CustomerID from their own CRM to Adobe Experience Platform, build segments from their own offline data, and send profiles that are entering and exiting the segments to Pega Customer Decision Hub for next-best-action (NBA) decisioning in outbound channels.

+## Prerequisites {#prerequisites}

+Before you use Pega Customer Decision Hub destination to export data out of Adobe Experience Platform:

+* Configure the Adobe Segment Membership Component in your Pega Customer Decision Hub instance.
+* Configure OAuth 2.0 Client Registration using Client Credentials grant type in your Pega Customer Decision Hub instance
+* Configure real-time processing of Adobe Segment Membership data flow to run in your Pega Customer Decision Hub instance.

+## Supported identities {#supported-identities}

+Pega Customer Decision Hub supports the activation of custom user ID described in the table below. For more details, see identities.
Minor, but I think we need a plural as in custom user IDs

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918316670:

+## Prerequisites {#prerequisites}

+Before you use Pega Customer Decision Hub destination to export data out of Adobe Experience Platform:

+* Configure the Adobe Segment Membership Component in your Pega Customer Decision Hub instance.
+* Configure OAuth 2.0 Client Registration using Client Credentials grant type in your Pega Customer Decision Hub instance
+* Configure real-time processing of Adobe Segment Membership data flow to run in your Pega Customer Decision Hub instance.

+## Supported identities {#supported-identities}

+Pega Customer Decision Hub supports the activation of custom user ID described in the table below. For more details, see identities.

+|Target Identity|Description
+|---|---|
+|CustomerID|Common User Identifier that uniquely identifies a profile in Pega Customer Decision Hub and Adobe Experience Platform
looks like there's a missing | at the end of the table

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918322612:

+|CustomerID|Common User Identifier that uniquely identifies a profile in Pega Customer Decision Hub and Adobe Experience Platform

+## Export type and frequency {#export-type-frequency}

+Refer to the table below for information about the destination export type and frequency.

+| Item | Type | Notes |
+---------|----------|---------|
+| Export type | [!UICONTROL Profile-based] | Export all members of a segment with identifier (CustomerID), attributes (last name, first name, location,..) and Segment Membership data.|
+| Export frequency | [!UICONTROL Streaming] | Streaming destinations are an always on API-based connections. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. For more information, see streaming destinations.|

+{style="table-layout:auto"}

+## Connect to the destination {#connect}

+Follow the steps described  to connect to this destination. In the configure destination workflow, fill in the fields listed in the two sections below.
Minor comment, the boilerplate text was linking to a generic tutorial about how to connect to destinations. Let's keep it, please:
To connect to this destination, follow the steps described in the destination configuration tutorialhttps://experienceleague.adobe.com/docs/experience-platform/destinations/ui/connect-destination.html. In the configure destination workflow, fill in the fields listed in the two sections below.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918323245:

+## Export type and frequency {#export-type-frequency}

+Refer to the table below for information about the destination export type and frequency.

+| Item | Type | Notes |
+---------|----------|---------|
+| Export type | [!UICONTROL Profile-based] | Export all members of a segment with identifier (CustomerID), attributes (last name, first name, location,..) and Segment Membership data.|
+| Export frequency | [!UICONTROL Streaming] | Streaming destinations are an always on API-based connections. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. For more information, see streaming destinations.|

+{style="table-layout:auto"}

+## Connect to the destination {#connect}

+Follow the steps described  to connect to this destination. In the configure destination workflow, fill in the fields listed in the two sections below.

+### Authenticate to destination {#authenticate}
For this step, where customers authenticate to your destination and insert the three fields you mention as bullet points below (lines 69-71), can you please add a screenshot as well, to offer users reassurance that they are in the right place?

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918324286:

+Follow the steps described  to connect to this destination. In the configure destination workflow, fill in the fields listed in the two sections below.

+### Authenticate to destination {#authenticate}

+#### OAuth 2 Client Credentials authentication {#oauth-2-client-credentials-authentication}

+Fill in the fields below and select [!UICONTROL Connect to destination]:

+* [!UICONTROL Access Token URL]: The URL on your side which issues access token.
+* [!UICONTROL Client ID]: The [!DNL client ID] that your system assigns to Adobe Experience Platform.
+* [!UICONTROL Client Secret]: The [!DNL client secret] that your system assigns to Adobe Experience Platform.

+### Fill in destination details {#destination-details}

+To configure details for the destination, fill in the required fields and select [!UICONTROL Next].
Same comment as above. Can you please add a screenshot with the three fields filled in?

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918324644:

+#### OAuth 2 Client Credentials authentication {#oauth-2-client-credentials-authentication}

+Fill in the fields below and select [!UICONTROL Connect to destination]:

+* [!UICONTROL Access Token URL]: The URL on your side which issues access token.
+* [!UICONTROL Client ID]: The [!DNL client ID] that your system assigns to Adobe Experience Platform.
+* [!UICONTROL Client Secret]: The [!DNL client secret] that your system assigns to Adobe Experience Platform.

+### Fill in destination details {#destination-details}

+To configure details for the destination, fill in the required fields and select [!UICONTROL Next].

+*  [!UICONTROL Name]: A name by which you will recognize this destination in the future.
+*  [!UICONTROL Description]: A description that will help you identify this destination in the future.
+*  [!UICONTROL URL]: Pega Customer Decision Hub Service Rest Segment membership Endpoint URL.
Would customers need more information about this URL? For example where in Pega they can get it?

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918325314:

+#### OAuth 2 Client Credentials authentication {#oauth-2-client-credentials-authentication}

+Fill in the fields below and select [!UICONTROL Connect to destination]:

+* [!UICONTROL Access Token URL]: The URL on your side which issues access token.
+* [!UICONTROL Client ID]: The [!DNL client ID] that your system assigns to Adobe Experience Platform.
+* [!UICONTROL Client Secret]: The [!DNL client secret] that your system assigns to Adobe Experience Platform.

+### Fill in destination details {#destination-details}

+To configure details for the destination, fill in the required fields and select [!UICONTROL Next].

+*  [!UICONTROL Name]: A name by which you will recognize this destination in the future.
+*  [!UICONTROL Description]: A description that will help you identify this destination in the future.
+*  [!UICONTROL URL]: Pega Customer Decision Hub Service Rest Segment membership Endpoint URL.

There is a missing section here:
Activate segments to this destination {#activate}

[!IMPORTANT]

To activate data, you need the [!UICONTROL Manage Destinations], [!UICONTROL Activate Destinations], [!UICONTROL View Profiles], and [!UICONTROL View Segments] access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

Read Activate profiles and segments to streaming segment export destinations for instructions on activating audience segments to this destination.
Also, can you briefly detail how in the Mapping step customers can map identities and attributes form Experience Platform to Pega? A screenshot might be useful here as well.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918336729:

+Fill in the fields below and select [!UICONTROL Connect to destination]:

+* [!UICONTROL Access Token URL]: The URL on your side which issues access token.
+* [!UICONTROL Client ID]: The [!DNL client ID] that your system assigns to Adobe Experience Platform.
+* [!UICONTROL Client Secret]: The [!DNL client secret] that your system assigns to Adobe Experience Platform.

+### Fill in destination details {#destination-details}

+To configure details for the destination, fill in the required fields and select [!UICONTROL Next].

+*  [!UICONTROL Name]: A name by which you will recognize this destination in the future.
+*  [!UICONTROL Description]: A description that will help you identify this destination in the future.
+*  [!UICONTROL URL]: Pega Customer Decision Hub Service Rest Segment membership Endpoint URL.

+## Exported data / Validate data export {#exported-data}
Can we edit this section to be more tailored to the Pega destination, please?
Specifically, we are looking to explain to users how they would validate that the data export out of Experience Platform into Pega was successful. For example:

Go to your Pega instance.
Verify if the segment from Experience Platform has been created in Pega
Verify that the population of the segment in Pega is according to your expectations.
Verify that the exported profile attributes from Experience Platform have made it into Pega.

The above is just an example to illustrate in broad terms what we are thinking.

In help/destinations/catalog/streaming/pegaCDH.mdhttps://github.com/AdobeDocs/experience-platform.en/pull/86#discussion_r918337909:

}, {

"SegmentID": "53cba6b2-a23b-454a-8069-fc41308f1c0f",

"Name": "Interested in Unlimited Data Plan",

"LastQualificationTime": "2020-05-25T23:37:33Z",

"Status": "exited",

"Version": "3",

"ValidUntil": "2020-07-25T23:37:33Z",

"Namespace": "AAM"

}]

}

+```

+## Data usage and governance {#data-usage-governance}

+All [!DNL Adobe Experience Platform] destinations are compliant with data usage policies when handling your data. For detailed information on how [!DNL Adobe Experience Platform] enforces data governance, see the Data Governance overview.
At the end of the page, you can add a section if there is any more useful information in Pega that you'd like to refer users to, like Pega documentation or similar. This is optional, but just calling it out in case you want to add something.
Additional resources {#additional-resources}
You can provide further links to your product documentation or any other resources you consider important for the customer to be successful.
—
Reply to this email directly, view it on GitHubhttps://github.com/AdobeDocs/experience-platform.en/pull/86#pullrequestreview-1034861808, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU3DX2B5AKVNOEAH7SE546LVTSCHDANCNFSM52JMTUDA.
You are receiving this because you modified the open/close state.Message ID<EMAIL_ADDRESS>

@paratAtPega - Hi Tony! To incorporate the feedback comments, please continue working on the create-destination branch that you created for the Pega destination documentation. Once you are happy with your updates, commit your changes and I should see them in the existing pull request.
If you are having difficulties with the process and are getting stuck, we can hop on a call to unblock you.

@paratAtPega - hi again! I notice in your latest commit (https://github.com/AdobeDocs/experience-platform.en/pull/86/commits/b21eb14f78877dcba0d069918d932de0fc029801 ) that only a few of the review comments were addressed. Will you be adding more updates? Let me know please if you need assistance. Thanks!

@paratAtPega - thanks for the latest commit (https://github.com/AdobeDocs/experience-platform.en/pull/86/commits/b21eb14f78877dcba0d069918d932de0fc029801). This commit, however, does not address most of my review comments. See please again my comments further above in this thread.
Let me know please if you need further assistance. We do need to address all comments before we can publish the documentation. Thank you!

Please review all the changes for the review comments. Let me know.
Thanks
Tony

@paratAtPega - I notice in one of your latest commits that you removed a description (https://github.com/AdobeDocs/experience-platform.en/pull/86/commits/0b97e4d34d96923e275b9f52e70e693e0bc43588 ). The description does make sense in the context of the paragraph it was in. Can you please re-add it?
Also, let me know please when you have completed your updates so I can re-review the documentation. Thanks!

Hi Victor,
Can you please review all the updated comments.
           https://github.com/paratAtPega/experience-platform.en/blob/create-destination/help/destinations/catalog/personalization/pegaCDH.md

Thanks,
Tony
From: Victor Giurgiu @.>
Sent: Thursday, July 21, 2022 1:09 PM
To: AdobeDocs/experience-platform.en @.>
Cc: Parakka, Tony @.>; Mention @.>
Subject: ExtMsg: Re: [AdobeDocs/experience-platform.en] Documentation for the Pega Customer Decision Hub destination (PR #86)
CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.
@paratAtPegahttps://github.com/paratAtPega - I notice in one of your latest commits that you removed a description (0b97e4dhttps://github.com/AdobeDocs/experience-platform.en/commit/0b97e4d34d96923e275b9f52e70e693e0bc43588 ). The description does make sense in the context of the paragraph it was in. Can you please re-add it?
Also, let me know please when you have completed your updates so I can re-review the documentation. Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/AdobeDocs/experience-platform.en/pull/86#issuecomment-1191735655, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU3DX2DXD7TRWSS4VTMSJ4TVVF73LANCNFSM52JMTUDA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Please review and let me know.
Thanks
Tony

Victor, Thank you very much for all the valuable review comments. Looking forward,
-Tony
From: Victor Giurgiu @.>
Sent: Monday, July 25, 2022 12:03 PM
To: AdobeDocs/experience-platform.en @.>
Cc: Parakka, Tony @.>; Mention @.>
Subject: ExtMsg: Re: [AdobeDocs/experience-platform.en] Documentation for the Pega Customer Decision Hub destination (PR #86)
CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.
@paratAtPegahttps://github.com/paratAtPega - Tony, thank you for your patience and your multiple updates on the documentation. I've made some final minor styling updates and added some localization tags. The draft is now ready to be published.
For now, thanks again for your efforts and I will let you know if we need any more documentation updates. We will be looking to publish the documentation this week. I will provide a link to the Experience League page here after the doc page is live.
—
Reply to this email directly, view it on GitHubhttps://github.com/AdobeDocs/experience-platform.en/pull/86#issuecomment-1194288239, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU3DX2CYLQJ3FVDD3ZQPQFDVV23DNANCNFSM52JMTUDA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

The Pega destination documentation is live at: https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/pega.html?lang=en

Thank you
-Tony
From: Victor Giurgiu @.>
Sent: Monday, August 1, 2022 1:28 PM
To: AdobeDocs/experience-platform.en @.>
Cc: Parakka, Tony @.>; Mention @.>
Subject: ExtMsg: Re: [AdobeDocs/experience-platform.en] Documentation for the Pega Customer Decision Hub destination (PR #86)
CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.
The Pega destination documentation is live at: https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/pega.html?lang=enhttps://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/pega.html?lang=en
—
Reply to this email directly, view it on GitHubhttps://github.com/AdobeDocs/experience-platform.en/pull/86#issuecomment-1201500224, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU3DX2G5PK6JOPRD3FZUP73VXACLLANCNFSM52JMTUDA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Victor,
We have the AEP profile and segment membership component available in Pega Marketplace and the documentation available in Pega docs server.
https://community.pega.com/marketplace/integrations/adobe-experience-platform-profile-and-segment-membership-integration-customer-decision-hub
https://docs.pega.com/component/customer-decision-hub/adobe-segment-membership-integration-component
Is it possible to update the AEP Pega connector page in AEP with updated link
Thanks
Tony
From: Victor Giurgiu @.>
Sent: Monday, August 1, 2022 1:28 PM
To: AdobeDocs/experience-platform.en @.>
Cc: Parakka, Tony @.>; Mention @.>
Subject: ExtMsg: Re: [AdobeDocs/experience-platform.en] Documentation for the Pega Customer Decision Hub destination (PR #86)
CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.
The Pega destination documentation is live at: https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/pega.html?lang=enhttps://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/pega.html?lang=en
—
Reply to this email directly, view it on GitHubhttps://github.com/AdobeDocs/experience-platform.en/pull/86#issuecomment-1201500224, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU3DX2G5PK6JOPRD3FZUP73VXACLLANCNFSM52JMTUDA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@paratAtPega - Hi Tony!
Could you please use the same process that we worked on for the initial publish to update the links in the documentation?
Or, you can use the edit page control (highlighted in the screenshot below) to update the links in the documentation.
Thanks & let me know if you have any questions!
Victor


[TB] Sub-themes

Allow for the creation of sub-themes associated with or building off of a parent theme.
Suggestion/Concern
sub-themes not a feature today.
Proposed Solution
Adding feature that allows for creation of sub-themes associated with or building off of a parent theme would allow a sub-theme to be created for an intranet that is based off an organization's public website theme.

If the parent them was updated, then the sub-theme would also be updated provided it hasn't been updated in sub-theme.


feat(snip-20): enable importing contract as library

This PR aims to allow extensions of the reference implementation. It follows a pattern adopted a good while ago in cw-plus.
The core change is an introduction of the library feature, which, when selected, omits the WASM bindings.
Thanks to that it's possible to build an extended version of the reference implementation, for example:

adding marketing info to the SNIP-20 token contract

Feel free to share feedback, and hopefully, accept the PR.

I like this pattern


Clear previously uploaded files when importing an experiment

Resolves #1114
This issue was caused by the validateExperiment() function, which pushes the experimentInfo into the this.allExperiments array whenever the user uploads new file(s). The simple solution is to clear the this.allExperiments array whenever a new file(s) has been uploaded by the user.
After this change, the previously uploaded files will not be imported.
https://github.com/CarnegieLearningWeb/UpGrade/assets/90279765/4f6ef77c-35ad-46a1-a86f-f441fb2c72d5

QA: Passed by Dan


Cannot select shared directory in iOS 15.6.1

Describe the issue
I cannot select shared directory in iPadOS 15.6.1. I've tried restarting UTM and making a new vm.
Configuration (required)

UTM Version: 4.0.2
OS Version: iPadOS 15.6.1
Device Model: iPad Pro (11 inch) 3rd gen
How did you install UTM?: Altstore

https://media.discordapp.net/attachments/674685003988336640/1015054983114264586/RPReplay_Final1662078318.mp4

Uploading IMG_5286.MOV…


mixin conflict while lauching server

main issue being
Caused by: org.spongepowered.asm.mixin.transformer.throwables.MixinPreProcessorException: Attach error for amethyst_imbuement.mixins.json:MiningToolItemMixin during activity: [Transform -> Method postMine(Lnet/minecraft/class_1799;Lnet/minecraft/class_1937;Lnet/minecraft/class_2680;Lnet/minecraft/class_2338;Lnet/minecraft/class_1309;Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfoReturnable;)V -> INVOKEVIRTUAL -> net/minecraft/class_304::method_1434:()Z]
unable to decipher the log to include more info..  hope its enough to get the ball rolling
thanks for this fantastic mod!!! please keep up the good work
latest.log

Interesting. Can you send me the log when you launch without Amethyst Imbuement included?
This appears to be something to do with Fabric Versions getting confused by something. I do want to point out that there is another mod conflict in this log!:
[22:18:18] [main/WARN]: @ModifyConstant conflict. Skipping yungsapi.mixins.json:IncreaseStructureWeightLimitMixin->@ModifyConstant::yungsapi_increaseWeightLimit(I)I from mod yungsapi with priority 1000, already redirected by repurposed_structures.mixins.json:structures.StructurePoolMixin->@ModifyConstant::repurposedstructures_increaseWeightLimitProd(I)I from mod repurposed_structures with priority 1000

This is the bit that's throwing my mod off, something is confusing java as to which classes Minecraft has (including the one my mixin needs, class_304). The last time I've seen this it's because a mod has a dependency with an improper version of Fabric API included:
[22:17:56] [main/WARN]: @Mixin target net.minecraft.class_759 was not found alkimicraft.mixins.json:HeldItemRendererMixin
[22:17:56] [main/WARN]: Error loading class: net/minecraft/class_634 (java.lang.ClassNotFoundException: net/minecraft/class_634)
[22:17:56] [main/WARN]: @Mixin target net.minecraft.class_634 was not found amethyst_imbuement.mixins.json:ClientPlayNetworkHandlerMixin
[22:17:56] [main/WARN]: Error loading class: net/minecraft/class_756 (java.lang.ClassNotFoundException: net/minecraft/class_756)
[22:17:56] [main/WARN]: @Mixin target net.minecraft.class_756 was not found amethyst_imbuement.mixins.json:GlisteringTridentModelMixin
[22:17:57] [main/WARN]: Error loading class: net/minecraft/class_5602 (java.lang.ClassNotFoundException: net/minecraft/class_5602)
[22:17:57] [main/WARN]: @Mixin target net.minecraft.class_5602 was not found catsexpanded.mixins.json:AccessorEntityModelLayers
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_338 (java.lang.ClassNotFoundException: net/minecraft/class_338)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_338 was not found dcch.mixins.json:DCCHMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_742 (java.lang.ClassNotFoundException: net/minecraft/class_742)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_742 was not found earthbounds.mixins.json:FlingshotFOVMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_746 (java.lang.ClassNotFoundException: net/minecraft/class_746)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_746 was not found earthbounds.mixins.json:FlingshotMovementBoostMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_299 (java.lang.ClassNotFoundException: net/minecraft/class_299)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_299 was not found earthbounds.mixins.json:RecipeBookGroupInjector
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_304 (java.lang.ClassNotFoundException: net/minecraft/class_304)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_304 was not found ftblibrary-fabric.mixins.json:KeyMappingAccessor
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_575 (java.lang.ClassNotFoundException: net/minecraft/class_575)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_575 was not found illagerexp.mixins.json:IllagerModelMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_606 (java.lang.ClassNotFoundException: net/minecraft/class_606)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_606 was not found illagerexp.mixins.json:SurrenderedChargeMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_472 (java.lang.ClassNotFoundException: net/minecraft/class_472)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_472 was not found magicfungi.mixins.json:BrewingStandScreenAccessor
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_465 (java.lang.ClassNotFoundException: net/minecraft/class_465)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_465 was not found magicfungi.mixins.json:HandledScreenAccessor
[22:17:58] [main/INFO]: [minekea_mixins] BCLib is not loaded. Enabling EnchantingTableBlockMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_922 (java.lang.ClassNotFoundException: net/minecraft/class_922)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_922 was not found hangman.mixins.json:EntitySitOrHangOnNoose
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_746 (java.lang.ClassNotFoundException: net/minecraft/class_746)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_746 was not found neutrino.mixins.json:ClientPlayerEntityMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_4603 (java.lang.ClassNotFoundException: net/minecraft/class_4603)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_4603 was not found neutrino.mixins.json:InGameOverlayRendererMixin
[22:17:58] [main/WARN]: Error loading class: net/minecraft/class_1088 (java.lang.ClassNotFoundException: net/minecraft/class_1088)
[22:17:58] [main/WARN]: @Mixin target net.minecraft.class_1088 was not found neutrino.mixins.json:ModelLoaderMixin
[22:17:59] [main/WARN]: Error loading class: net/minecraft/class_906 (java.lang.ClassNotFoundException: net/minecraft/class_906)
[22:17:59] [main/WARN]: @Mixin target net.minecraft.class_906 was not found spectrum.mixins.json:FishingBobberEntityRendererMixin
[22:17:59] [main/WARN]: Error loading class: net/minecraft/class_763 (java.lang.ClassNotFoundException: net/minecraft/class_763)
[22:17:59] [main/WARN]: @Mixin target net.minecraft.class_763 was not found spectrum.mixins.json:ItemModelsMixin
......
[22:18:23] [main/WARN]: Error loading class: net/minecraft/class_304 (java.lang.ClassNotFoundException: net/minecraft/class_304)

interesting.  yeah i use yungs api + paxi , as a datapack loader.  its ok that repurprosed structures overrides it.
ill get you a server log loaded without amethyst imbuement.  mind you there may be conflicts as well , as im currently working on getting it optimized.

with_amethyst_imbuement.log
without_amethyst_imbuement.log
new world for each. one with , one without amethyst imbuement.

without_amethyst_imbuement.log
If you look in this log, you'll see there's still a pretty big pile of missing classes. I would definitely look into that issue, as it likely means that 17 or so mixins are not working.

The only reason I can think that my particular mixin caused a crash was because it was cancellable. Looking at some of the other mixins having issues but not crashing, they aren't. So, I've made a quick version tweak with the cancellable-ness gone. Can you check it? I'm putting it here rather than bothering with versioning CF. (The .jar is inside the .zip)
amethyst_imbuement-1.18.2-04-TheRankerTest.zip

I can certainly test. And yes I'm looking into it all. Haha part of the process. :) Thanks for all help. I'll let you know of the outcome

i havent read it yet.. but it crashed with the test jar.
latest_with_test_jar.log

Darn, ok, here's another one to try.
amethyst_imbuement-1.18.2-04-TheRankerTest-b.zip

sorry bout the delay. got caught up with rl stuff. and another issue lol
latest.log
it failed to load using the version b jar as well

Unfortunately I am out of ideas for workarounds to the issue at hand... The only solution I see is a removal-by-halves test of the mods in the pack until the offending mod(s) that's causing the class loading error is found.

Okies. I'll look into it further and I'll get you more information. Need this working for me. :)

alright..
@fzzyhmstrs
. so here is the details
latest.log
Only Amethyst Imbuement and WTHIT .(waila fork). on Fabric API 51. .... and same crash.. same mixin.

latest.log
heres log without wmitaf and wthit...
this is fabric api 51, fabric lang kotlin.. and ur ranker b jar.

latest.log
same crash with official CF jar. vanilla fabric. no mods.

Urgh, thanks a lot for the detailed testing...... there were some very esoteric issues with AI that I think I FINALLY understand and have resolved. I tossed it into a quick server of my own prepared in basically the same way you have yours above, and it seems to not crash!

There still may be an issue with the REI server plugin not loading on dedicated servers, but I can get all the way through spawn location initialization etc. The plugin not loading might affect auto-moving of items from inventories for the imbuing table and crystal altar, but I don't think anything else would be affected.
Jar attached for you:
amethyst_imbuement-1.18.2-04-TheRankerTest-c.zip

I've solved the REI plugin issue also, and made a public rev of the .jars with the fixes included (1.18.2-05 and 1.18.1-04).
Thank you very much for your patience with this issue. If there still is some server issue on your end please reopen to let me know!

latest.log
failed to create world with server.. and 1 othe rmod.. repurposed strcutures.. you may want to contact that dev since he is the one that writes almost all of fabric world generation . he also gives out tutorials on how to do certain things.
somethign in your mod is conflicting with his.

Ok, well at least I know what the issue is right away this time.... it's a client-based class in a loot table generator that shouldn't be there running into the fact that there is not a client.
I'm going through and checking for clientside classes now and removing any I find not in the right place. Should be done soon.

failed on first load.. with my modpack. .seen it conflcited with repurposed structures.. so i did a small profile with just your mod and that mod + dependancies to isolate the issue.. got same error lol
sorry for always posting issues. but hey, i wanna use it. and so do others.. so lets get it going smoothly lol

Thank you for sending in the issues! I'd much rather that than silence lol. The crash issue is with my mod trying to give repurposed structures some loot table additions from my items, and wrongly trying to access the client while doing so. I've hopefully scrubbed out any potential client class issues, but that's probably jinxing myself.
Another TheRankerTest for you. My little dummy server launched successfully with this test update as well as the repurposed structures and feature_nbt_deadlock_be_gone versions you have in your log.
amethyst_imbuement-1.18.2-04-TheRankerTest-d.zip

ill test on my little test server then on my modpack dev server. ill report bakc wiht my findings :)

@fzzyhmstrs
In regards to this:

[22:18:18] [main/WARN]: @ModifyConstant conflict. Skipping yungsapi.mixins.json:IncreaseStructureWeightLimitMixin->@ModifyConstant::yungsapi_increaseWeightLimit(I)I from mod yungsapi with priority 1000, already redirected by repurposed_structures.mixins.json:structures.StructurePoolMixin->@ModifyConstant::repurposedstructures_increaseWeightLimitProd(I)I from mod repurposed_structures with priority 1000

This is intended between me and yung’s. We both wanted to increase the hardcoded pool weight constant in a codec. So we use Modifyconstant but set required to false so that when anyone else mixins that constant, our own mixins will not crash the game. It will simply long that message and everything moves on.
Whatever issue is causing the crash here isn’t related to the pool weight mixins

Thank you for sending in the issues! I'd much rather that than silence lol. The crash issue is with my mod trying to give repurposed structures some loot table additions from my items, and wrongly trying to access the client while doing so. I've hopefully scrubbed out any potential client class issues, but that's probably jinxing myself.
Another TheRankerTest for you. My little dummy server launched successfully with this test update as well as the repurposed structures and feature_nbt_deadlock_be_gone versions you have in your log. amethyst_imbuement-1.18.2-04-TheRankerTest-d.zip

I can’t read the log on mobile but yeah. What my mod does is it generates the loot from vanilla loot tables as soon as a user opens one of my structure’s chests. Then I pull all modded items from that loot table. And then I add the loot to my own chest’s loot table. This way, I maximize mod compatibility with spawning modded items in my mod’s chests for my structure variants of vanilla structures. This is the code that handles that modded loot importing
https://github.com/TelepathicGrunt/RepurposedStructures-Fabric/blob/c1cbcb424694076280ee6ddae012cea772404ec7/src/main/java/com/telepathicgrunt/repurposedstructures/misc/lootmanager/StructureModdedLootImporter.java#L235

just comfirming that the [amethyst_imbuement-1.18.2-04-TheRankerTest-d.zip] zip worked in my modpack. server loaded and i logged in.  now time to optimize my pack :) tyvm!

@TelepathicGrunt thank you for the additional info!

just comfirming that the [amethyst_imbuement-1.18.2-04-TheRankerTest-d.zip] zip worked in my modpack. server loaded and i logged in. now time to optimize my pack :) tyvm!

Awesome! I'll get that fix and some other stuff moved into the public versions :)

Just one last thing, i noticed this class: https://github.com/fzzyhmstrs/ai/blob/5efab10124397e93ea8b6d4088a060241aba33bf/src/main/kotlin/me/fzzyhmstrs/amethyst_imbuement/loot/RepurposedStructuresLoot.kt
if this is adding your custom loot into my mod's loot tables, this means my automatic modded loot importing is also going to be running and users will end up with twice the modded loot from your mod in my chests. Do you want to continue to handle adding the loot to my mod or would you rather let my mod continue to import your loot? I can add a check on my end to not import any amethyst_imbuement namespaced items so that only your mod controls the loot injection into my loot tables

Just one last thing, i noticed this class: https://github.com/fzzyhmstrs/ai/blob/5efab10124397e93ea8b6d4088a060241aba33bf/src/main/kotlin/me/fzzyhmstrs/amethyst_imbuement/loot/RepurposedStructuresLoot.kt
if this is adding your custom loot into my mod's loot tables, this means my automatic modded loot importing is also going to be running and users will end up with twice the modded loot from your mod in my chests. Do you want to continue to handle adding the loot to my mod or would you rather let my mod continue to import your loot? I can add a check on my end to not import any amethyst_imbuement namespaced items so that only your mod controls the loot injection into my loot tables

Your mod can do the work! I've already unregistered that class from my loot loader in the verison I'm currently working on so your mod can do it.


Ambiguous Wording in 'System node pools have the following restrictions' Section

[Enter feedback here]
Problematic Sentence
A minimum of two nodes 4 vCPUs is recommended(e.g. Standard_DS4_v2), especially for large clusters (Multiple CoreDNS Pod replicas, 3-4+ add-ons, etc.).
Problem
The wording of the sentence suggests us to allocate a minimum of 2 nodes of 4vCPUs. However, the given SKU inside brackets (Standard_DS4_v2) is an 8vCPU instance. Please address the ambiguity.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 225b99ee-4c4d-54c2-cafa-ddcd286438da
Version Independent ID: ca9410a8-8ddb-5528-a0ac-0963458f190e
Content: Use system node pools in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/use-system-pools.md
Service: container-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@SachithKasthuriarachchi
Thanks for your feedback! We will investigate and update as appropriate.

@SachithKasthuriarachchi
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@MGoedtel
Can you please check and add your comments on this doc update request as applicable.

any updates on this @MGoedtel ?

Thank you, @SachithKasthuriarachchi for the feedback! I'm working on updates to the doc and am removing the ambiguity here. I will now close this GH issue.
#please-close


Configure Ceramic node observability

There are built-in observability features (opentelemetry or prometheus) in the ceramic service, which we should monitor to ensure we keep good track of node health.
More info on configuration here: https://developers.ceramic.network/docs/composedb/guides/composedb-server/server-configurations#metrics

Trumped by #519


Add support for overbrace / underbrace

This is a little trick because we need to know how wide a layout is.  Currently we let the browser render things and stuff comes out being however wide it comes out.  I've added the ability to optionally generate metrics that include the width of glyphs, but it isn't being used by default.  It was more of an experimental feature that I thought might be useful in canvas rendering to avoid having to ask the canvas to measure each glyph during layout.  Regardless of the original intent of this option, it appears that width metrics will also be use in implementing these commands.
The thing the I'm struggling with is how to actually render the braces.  http://tex.stackexchange.com/questions/3488/horizontal-braces-with-xetex-take-too-much-space shows a redefinition of \upbracefill and \downbracefill which rotates the braces.  This seems reasonable considering there don't seem to be specific glyphs for these commands.  Since we're no longer supporting IE8 we could use CSS 2D Transforms, support matrix: http://caniuse.com/#feat=transforms2d.

This is in v0.8.0.


Missing fallback routes for custom paths of non-default locales

Version
@nuxtjs/i18n:7.2.0
nuxt: 2.15.8
Nuxt configuration

[x] Applies to a site deployed to a static server (site generated with nuxt generate)
[x] Applies to a site deployed to a server with a Node backend

@nuxtjs/i18n configuration
i18n: {
    strategy: 'prefix'
    //+some locales
}

component:
nuxtI18n: {
    paths: {
      "en": "/about",
      "es": "/sobre",
    },
  },

Reproduction Link

Steps to reproduce

implement i18n-module using prefixed routes
start using custom route paths

e.g. /es/sobre instead of previously /es/about

visit a non-default locale path on it's previous URL (which might be listed in search engines already)

What is Expected?
Forwarding of default-locale URLs to their custom URL (/es/sobre)

or alternatively switching to the default locale instead (/en/about)

What is actually happening?
Non-default locales with custom paths will no longer work with their old URL (availability disruption). They just yield an error page as if the URL was made up.

This issue only applies in this specific case when route was renamed. It's not really a job of the module to handle that IMO. You should probably manually add a redirect route using extendRoutes for those cases.

Well, the issue I see is that although we may call URL localization "renaming", it is an unconscious renaming because we are so used to fallbacks but suddenly there is no handling. This is not only affecting people when localizing from a default-locale route, but also when adding one more language -> then they're unable to do so without covering everything by a custom handler in extendRoutes.
Maybe generating small files with a clientside redirect tag would be acceptable? :slightly_smiling_face:
Even without handling this in the code, would you accept a PR adding a hint regarding SEO risks (if not handled by custom code) to this section?

I'll mark this as feature request.
I'd accept clarification in the documentation or a PR that adds an option for creating those fallback routes.

Closing this as v7 is not being actively worked on (critical hotfixes only), if this still applies to v8 and later please open a new issue!


Filling Blank End-of-Support Dates for .NET Framework Versions After 4.6.2 with Parent OS End-of-Support Dates

Hey, I noticed that the end-of-support dates for .NET Framework versions after 4.6.2 are all blank. I checked the docs and found out that their support follows the lifecycle of the parent OS. So, can the page just use the end-of-support date of the parent OS to fill in those blanks?
https://dotnet.microsoft.com/en-us/download/dotnet-framework
https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-framework

Thanks for your feedback @Varorbc.
That is tricky because each OS has a different end-of-support date and new OS versions keep getting released that still include .NET Framework.
@jamshedd any thoughts on this? should we at least include some note on the column or download page to mention that? Maybe just a link to the official policy page at https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-framework?
I also noticed that https://learn.microsoft.com/en-us/lifecycle/faq/dotnet-framework is not up to date (e.g. it doesn't include .NET Framework 4.8.1)
Not sure who's responsible for updating that.


DB primary borken

The distributed database approach was broken in smoke test. This PR fixes that.
Issues addressed:

the interleave of cluster and state management and distribution wrapping etc. led to an infinite regress of HTTP requests.
the per-cluster advisories whitelists weren't being recorded into the database, despite there being tables
the tests for state persistence didn't catch that advisory whitelists were getting dropped
the existing test fixtures didn't include the whitelists

          1 Warning

:warning:
Big PR: 5486 lines of code changed

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #737 into master will increase coverage by 0.06%.
The diff coverage is 62.65%.

@@            Coverage Diff             @@
##           master     #737      +/-   ##
==========================================
+ Coverage      56%   56.06%   +0.06%
==========================================
  Files         259      259
  Lines       14920    14986      +66
==========================================
+ Hits         8356     8402      +46
- Misses       5865     5885      +20
  Partials      699      699

Impacted Files
Coverage Δ

cli/sous_init.go
26% <0%> (-2.27%)
:arrow_down:

server/handle_gdm.go
39.78% <0%> (ø)
:arrow_up:

util/restful/router.go
72.15% <100%> (+0.32%)
:arrow_up:

graph/graph.go
62.18% <53.84%> (-0.29%)
:arrow_down:

lib/cluster_manager.go
51.11% <55.55%> (-0.25%)
:arrow_down:

server/handle_state_deployments.go
50% <66.66%> (+1.61%)
:arrow_up:

lib/dispatchstatemanager.go
48.21% <73.33%> (+4.46%)
:arrow_up:

ext/storage/postgresstatemanager_write.go
68.86% <75%> (+1.49%)
:arrow_up:

graph/server.go
77.77% <77.77%> (-3.18%)
:arrow_down:

lib/auto_resolver.go
88.05% <0%> (-1.5%)
:arrow_down:

... and 1 more

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 3cfc4c7...ba19cab. Read the comment docs.


Save note drafts

You should never lose anything you typed in a note editor unless you explicitly canceled the edit. This means that reloading the page shouldn't reset a note editor. We could do this by storing note drafts in local storage (keyed by the note id). When a note editor loads, it should check if the there is a draft for the note in local storage.

Closing in favor of #244


Add chatbot page

This will be picked up again by @ancadavid in a separate PR, so I'm closing this.


Fixed #29417 -- Corrected two admin page titles for RO users.

The Changelist and 'View object' views still contained the word 'change'
in their title and header.

Is it possible to write assertions with response.context in lieu of or before assertContains()? That's often easier to debug.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=384200137
https://github.com/Azure/azure-cli-extensions/commit/d7d2ba38b06aff88e00a38e9ba130c6343508d18

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

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


exports useDevtoolsContext

exports the useDevtoolsContext hook - resolves https://github.com/FormidableLabs/urql/issues/382

tested by importing into the example project and logging the returned object.

@Jay-A-McBee if you have a second, mind updating the docs to show that this is now available as part of the urql API? Thanks for contributing 💯


Unable to register a profile if the AWS_PROFILE is set with the name profile

set the env variable AWS_PROFILE like test

export  AWS_PROFILE=test

Create the clokta profile

clokta -p test

Save and you willl see the botocore error for

ProfileNotFound

Also, you can try deleting the ~/.aws  and ~/.clokta directories

Fixed in clokta 4.1.3


add more column specs

add option timezone for  datatype timestamp and time
add datatype json & jsonb (disable warning)
add option comment(work with db-migrate/db-migrate-base#6 which exec extra callbacks after create table)

sry for the long delay going to merge this.

Merged in https://github.com/db-migrate/pg/commit/401ac2df93914a0a2d87799875f9fe1521a8554d


feat(graphql-http): add async-graphql request compat shim

The async-graphql is another rust GraphQL crate we use in our projects.
This PR adds a compatibility shim, gated by the compat-async-graphql feature, so one can use an async_graphql::Request with the Reqwest-based client.

@Jannis I believe that this PR might be of your interest 🙂


feat(lib/redis_client/ruby_conncetion/resp3): make DUMP_TYPES non-mutable

Addresses https://github.com/redis-rb/redis-client/issues/162 while keeping the ability to accept subclasses of accepted types as command arguments (https://github.com/redis-rb/redis-client/commit/9fb715fb1a3e1caf91d9b7fa921532085d47c707).
The tradeoff made is losing the cache on the subclass. I think this is reasonable as the length of DUMP_TYPES.keys is fixed to 4.

@byroot I'm having issues getting the tests to work within the test framework 😅
For some reason Ractor.new fails and I'm not understanding why. I'd appreciate a hand with this if you have any idea of what could be going on.
I tried creating a simple test: ractor_test.rb
# frozen_string_literal: true

require "test_helper"

class RactorTest < Minitest::Test
  include ClientTestHelper
  def test_set_within_ractor
    Ractor.new do
      within_ractor_redis = new_client
      within_ractor_redis.call("SET", "foo", "bar")
    end

    out_of_ractor_redis = new_client
    assert_equal("bar", out_of_ractor_redis.call("GET", "foo"))
  end

  def test_get_within_ractor
    out_of_ractor_redis = new_client
    out_of_ractor_redis.call("SET", "foo", "bar")

    ractor = Ractor.new do
      within_ractor_redis = new_client
      within_ractor_redis.call("GET", "foo")
    end

    assert_equal("bar", ractor.take)
  end
end

I did however manage to get it to work "manually" (i.e. outside of the testing framework) in a separate script:
# frozen_string_literal: true

require_relative 'lib/redis_client'

def new_client
  RedisClient.new(host: 'localhost', port: 53285, timeout: 0.1)  # I had a redis instance running on that port
end

def test_get_within_ractor
  out_of_ractor_redis = new_client
  out_of_ractor_redis.call('SET', 'foo', 'bar')

  ractor = Ractor.new do
    within_ractor_redis = new_client
    within_ractor_redis.call('GET', 'foo')
  end

  p ractor.take == 'bar' # => true
end

def test_set_within_ractor
  Ractor.new do
    within_ractor_redis = new_client
    within_ractor_redis.call('SET', 'foo', 'bar')
  end

  out_of_ractor_redis = new_client
  p out_of_ractor_redis.call('GET', 'foo') == 'bar' # => true
end

def test_get_set_within_ractor
  ractor = Ractor.new do
    within_ractor_redis = new_client
    within_ractor_redis.call('SET', 'foo', 'bar')
    within_ractor_redis.call('GET', 'foo')
  end

  p ractor.take == 'bar' # => true
end

def test_multiple_ractors
  ractor1 = Ractor.new do
    within_ractor_redis = new_client
    within_ractor_redis.call('SET', 'foo', 'bar')
    within_ractor_redis.call('GET', 'foo')
  end

  p ractor1.take == 'bar' # => true

  ractor2 = Ractor.new do
    within_ractor_redis = new_client
    within_ractor_redis.call('GET', 'foo')
  end

  p ractor2.take == 'bar' # => true
end

test_get_within_ractor
test_set_within_ractor
test_get_set_within_ractor
test_multiple_ractors

Any ideas on how we could take that "manual testing" unto minitest?

For some reason Ractor.new fails and I'm not understanding why.

Protip: never ever write in a bug report or ticket that something "fails" without describing what that failure look like, generally that implies sharing the error message and / or backtrace.

For some reason Ractor.new fails and I'm not understanding why.

Protip: never ever write in a bug report or ticket that something "fails" without describing what that failure look like, generally that implies sharing the error message and / or backtrace.

You're absolutely right, sorry about that!
Here it is with full trace:
❯ bundle exec rake test:ruby TEST=./test/redis_client/ractor_test.rb --trace
** Invoke test:ruby (first_time)
** Execute test:ruby
starting toxiproxy... started with pid=60025
starting redis... started with pid=60026
Waiting for toxiproxy (port 8474)... ready.
Waiting for redis (port 16380)... ready.
Running test suite with driver: RedisClient::RubyConnection
Run options: --seed 18910

# Running:

/Users/j/Documents/redis-client/test/redis_client/ractor_test.rb:21: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.
E/Users/j/Documents/redis-client/test/redis_client/ractor_test.rb:8: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.
E

Finished in 0.004395s, 455.0627 runs/s, 0.0000 assertions/s.

  1) Error:
RactorTest#test_get_within_ractor:
RuntimeError: /Users/j/Documents/redis-client/test/redis_client/ractor_test.rb:21: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.

    test/support/raise_warnings.rb:7:in `warn'
    <internal:warning>:51:in `warn'
    <internal:ractor>:277:in `new'
    test/redis_client/ractor_test.rb:21:in `test_get_within_ractor'

  2) Error:
RactorTest#test_set_within_ractor:
RuntimeError: /Users/j/Documents/redis-client/test/redis_client/ractor_test.rb:8: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.

    test/support/raise_warnings.rb:7:in `warn'
    <internal:warning>:51:in `warn'
    <internal:ractor>:277:in `new'
    test/redis_client/ractor_test.rb:8:in `test_set_within_ractor'

2 runs, 0 assertions, 0 failures, 2 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test:lib" /Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/rake_test_loader.rb "./test/redis_client/ractor_test.rb" ]
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/testtask.rb:130:in `block (3 levels) in define'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/file_utils.rb:57:in `sh'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/file_utils.rb:102:in `ruby'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/testtask.rb:117:in `block (2 levels) in define'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/file_utils_ext.rb:58:in `verbose'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/testtask.rb:111:in `block in define'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `block in execute'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `each'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:281:in `execute'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:199:in `synchronize'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:199:in `invoke_with_call_chain'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/task.rb:188:in `invoke'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:182:in `invoke_task'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `block (2 levels) in top_level'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `each'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:138:in `block in top_level'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:147:in `run_with_threads'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:132:in `top_level'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:83:in `block in run'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:208:in `standard_exception_handling'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/lib/rake/application.rb:80:in `run'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/rake-13.1.0/exe/rake:27:in `<top (required)>'
/Users/j/.rbenv/versions/3.3/bin/rake:25:in `load'
/Users/j/.rbenv/versions/3.3/bin/rake:25:in `<top (required)>'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `load'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `kernel_load'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:23:in `run'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli.rb:483:in `exec'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli.rb:31:in `dispatch'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/cli.rb:25:in `start'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/exe/bundle:48:in `block in <top (required)>'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
/Users/j/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/gems/bundler-2.3.13/exe/bundle:36:in `<top (required)>'
/Users/j/.rbenv/versions/3.3/bin/bundle:25:in `load'
/Users/j/.rbenv/versions/3.3/bin/bundle:25:in `<main>'
Tasks: TOP => test:ruby

Right, the backtrace points you exactly at what is going on: https://github.com/redis-rb/redis-client/blob/84f1c6567eb02a941e94e8ca41f97d55a026ec4c/test/support/raise_warnings.rb#L7
Ractors will print a warning when you use them because they are still experimental, and I have something that turn warnings into errors in the test suite.
Just add something like return if message.include?("Ractor is experimental") before the raise

Right, the backtrace points you exactly at what is going on:
https://github.com/redis-rb/redis-client/blob/84f1c6567eb02a941e94e8ca41f97d55a026ec4c/test/support/raise_warnings.rb#L7
Ractors will print a warning when you use them because they are still experimental, and I have something that turn warnings into errors in the test suite.
Just add something like return if message.include?("Ractor is experimental") before the raise

Right, the backtrace points you exactly at what is going on:
https://github.com/redis-rb/redis-client/blob/84f1c6567eb02a941e94e8ca41f97d55a026ec4c/test/support/raise_warnings.rb#L7
Ractors will print a warning when you use them because they are still experimental, and I have something that turn warnings into errors in the test suite.
Just add something like return if message.include?("Ractor is experimental") before the raise

OMG can't believe I missed that, thank you!
I've just uploaded some basic tests, let me know if I'm missing something or if you'd like me to test anything else with more depth

@byroot fixed flaky test, skipped them altogether for ruby versions lower than 3 and made them compatible with ruby 3.0 (https://bugs.ruby-lang.org/issues/17592). Also added a small description on the unreleased section of the changelog.

Alright, I refactored your PR quite a bit, and the Ractors in 3.0 won't make it because RedisClient.default_driver. But should work for basic operations on 3.1+.


Click link to open browser and 'open terminal here'

Description of the new feature/enhancement

when we are developing vue apps the terminal always show us 'http://localhost:8080' or 'http://<IP_ADDRESS>:8080' ,i hope if i could open this url with browser  . a click to open url ,maybe , a good idea
is there a way to way to register terminal as a context? when we look into a folder ,then we can right click  and use 'open windows terminal in the folder' command. Or we could register windows terminal as 'terminal 'command ,like 'cmd'. We could also use commands like terminal.exe /REGISTER ALL to register terminal as a global terminal

Proposed technical implementation details (optional)

Thanks for the suggestions! Please make sure to search for duplicates when filing new issues.


Add support for iter_size - virtual large batch

iter_size should do the following:

if iter_size=1 or not set then behave as before
if iter_size>1 then we should accumulated gradients on every worker and broadcast/sync every iter_size.

This would effectively mean that "algorithmic batch size" = batch_size_per_gpunum_gpusiter_size

Implemented in dev0.4


Handle https to http override in TLS MitM websocket connection

In a typical MitM over CONNECT scenario there is possibility to override request schema from secure to insecure. Example: when using TLS MitM we can substitute https service using a local http server by manipulating request URL schema in OnRequest handler.
But when there is a try to open websocket connection, there is an error - always secure TLS connection is enforced regardless to request URL schema. This PR fixes that.
Resolves #506

@elazarl can you please review and hopefully merge? I face same issue as described in #506 and this PR fixes it

Apologies, missed that


Bugfix/native app webpack support

Add Flow types for Native generator
Fix copy task
Fix styles path to images (for Native apps)

 Build chain for omaha:native is totally broke with webpack (probably browserify too)

Coverage increased (+0.007%) to 99.144% when pulling 3cc83cf206b90d2f9c7cf9acc96e9f577a698b51 on bugfix/native-app-webpack-support into 30dce422f25fd77b1bc67159ae7e5d1efe44c11a on master.


[ADD] Carrier Frequency Offset estimation

This commit adds functionality to the Receiver type in order to estimate the Carrier Frequency Offset between a sender and a receiver according to DW3000 User Manual, Chapter <IP_ADDRESS>.

r_wait_buf is meant to be small, I wonder how this could be elegantly handled, as a lot of other functionalities share this pattern. What I am currently doing is reading this register after r_wait_buf and before enabling RX again which clears the register. Pls let me know what you think

Note that only
rxing.finish_receiving()

will switch the type state, so you can read all these things before calling this function. One just need to be careful not to read stuff when r_wait_buf has not returned Ok.


Item 9: verify equals and hashCode are overridden together

Are there acceptable exceptions?

We now have an initial version of the symbols solver (#54). We should be now able to go on with the implementation of this one.


react-nav config [nfc]: Un-deduplicate bottom and top nav default configs

This should cut down the Flow errors with Flow v0.149.0 by 69.
Flow errors before (155): before.txt
After (86): after.txt

Thanks! Looks good to me -- merging.
I agree it probably makes sense to un-deduplicate those settings for top vs. bottom tabs, even apart from the type issue. I'm reminded of "The Wrong Abstraction": https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
In this case it was pretty harmless, but I think it was a wrong abstraction. (#3767 is about an example of an over-eager deduplication that has gotten in our way to a greater degree.)

Thanks for the review! Yeah, I've come across that blog post before, maybe on CZO? It's a useful concept.


Parse OBO-prefixed nodes differently when assigning edge infores

Fix #97

Oops, this merge was premature - just found a bug


Wrong TLS version is coming in client Hello

We are using latest stable envoy 1.26.1
We are taking envoy config dump and TLS version is coming as TLSv1_2 but in client hello it is coming as TLS1.0
"tls_params": {
"tls_minimum_protocol_version": "TLSv1_2",
"cipher_suites": [
"ECDHE-ECDSA-AES128-GCM-SHA256",
So if we have configured TLSv1_2 so why it is coming as TLS1.0 in wireshark logs?

In Record Layer TLS 1.0 version is coming that is wrong version

I think this article addresses what you're seeing: https://www.analysisman.com/2021/06/wireshark-tls1.2.html

Thanks


Issue after yarn start

I can't proceed and showed this issue up.
An unhandled rejection has occurred inside Forge:
Error: Electron failed to install correctly, please delete node_modules/electron and try installing again
at getElectronPath (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules\electron\index.js:17:11)
at Object. (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules\electron\index.js:21:18)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32)
at Module._load (node:internal/modules/cjs/loader:1023:12)
at Module.require (node:internal/modules/cjs/loader:1235:19)
at require (node:internal/modules/helpers:176:18)
at locateElectronExecutable (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules@electron-forge\core\dist\util\electron-executable.js:34:28)
at async forgeSpawn (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules@electron-forge\core\dist\api\start.js:104:32)
at async forgeSpawnWrapper (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules@electron-forge\core\dist\api\start.js:138:25)
at async exports.default (E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules@electron-forge\core\dist\api\start.js:170:21)
at async E:\CHATGPT-AI-Marketing-Tools-CMD\onepoint\node_modules@electron-forge\cli\dist\electron-forge-start.js:57:21
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Currently I don't have a plan on this, but I'm willing to accept pull requests if anyone implements it.


feat(react-instantsearch): add Carousel layout component

This adds the the Carousel layout component and enables the layoutComponent prop in Recommend widgets. React getting started example has been update to use Carousel as well.

https://algolia.atlassian.net/browse/FX-2819
TODO: fix Recommend widget prop types

I think the typing issue you have with translations comes from the fact that you're passing the widget translations (e.g., translations for FrequentlyBoughtTogether) to Carousel, while Carousel should take its own translations.

Closing in favour of https://github.com/algolia/instantsearch/pull/6321


Update scala-library to 2.13.7

Updates org.scala-lang:scala-library from 2.13.6 to 2.13.7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #233 (45e9c0b) into master (542c155) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #233   +/-   ##
=======================================
  Coverage   38.46%   38.46%
=======================================
  Files           3        3
  Lines          91       91
=======================================
  Hits           35       35
  Misses         56       56

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 542c155...45e9c0b. Read the comment docs.


Possible typo in Table 1

Hi, and thank you for your work. I'm working on this dataset for ML applications and running experiments on each subset. From my analysis, it seems like the subset SBcurated has 16 labels and not 10 as declared in Table 1 of the paper (you might have swapped the value with the last column by mistake). Thanks!

The semantics of the weakness column in Table 1 is the number of labels according to the original dataset.
SBcurated groups the contracts according to the DASP classification, which consists of 10 labels; therefore the number 10 in the column "weaknesses" in Table 1. In the course of our work, we labeled the contracts also according to the SWC registry, which is more fine-grained than DASP. This results in 16 groups. As label in the consolidated dataset, we then used the more accurate labeling according to SWC.
In Table 11 in the appendix, you find the correspondence between DASP and SWC labels. For the dataset SBcurated, the DASP-category 2 (access control) is broken down into access_control-105, access_control-106, access_control-112, access_control-115, access_control-118, and access_control-124. Likewise, DASP-category 5 (denial of service), is split into denial_of_service-113 and denial_of_service-128. The three-digit numbers correspond to the SWC classification. This adds up to six extra labels.


Feature: Support external Android SDK or binary download

This could use something similar to the environment variable check for a user installed ${HUNTER_ROOT} or ${SUGAR_ROOT}.   Maybe ${HUNTER_ANDROID_SDK_ROOT}?  I'm not exactly sure which packages are built for an android apk, but I'm guessing it is some subset of these:
Android-Apk
Android-Build-Tools
Android-Google-APIs
Android-Google-APIs-Intel-x86-Atom-System-Image
Android-Google-Repository
Android-Intel-x86-Atom-System-Image
Android-Modules
Android-SDK
Android-SDK-Platform
Android-SDK-Platform-tools
Android-SDK-Tools
Android-Support-Repository
Sources-for-Android-SDK

I'm not sure I understand the question exactly.

Maybe ${HUNTER_ANDROID_SDK_ROOT}?

You already can use ANDROID-SDK_ROOT variable. See Android-SDK for example. May be variable name looks quite ugly, it's combination of TOUPPER + append _ROOT. We can add s,-,_,g operation and name will be ANDROID_SDK_ROOT (?)

Excellent.  Thanks for point me there.


What about Room / Account charges?

As a guest, I want to be charged to my room or to city ledger account.  Can I do that?

Hi @dinobu we currently don't have that feature. The functionality of the app is limited due it is intended to  be used as sample reference not as a fully working version of an hotel app. You are always welcome to send a PR with the extra functionality you would like to have! Thanks.