C# type of Preference trimmed away in Release builds, causing NullReferenceException

Android framework version
net9.0-android
Affected platform version
.NET9 RC2
Description
C# Type seems to be trimmed away, causing problems in Release builds.
The problem did not occur in .NET 8
Steps to Reproduce
In my app I am using a Preference screen, with a SwitchPreferenceCompat specified in the XML.
<PreferenceScreen xmlns:app="http://schemas.android.com/apk/res-auto">
  <PreferenceCategory>
    <SwitchPreferenceCompat app:key="test" app:title="Test"/>
  </PreferenceCategory>
</PreferenceScreen>

In my C# code, I want to get a reference to it in order to initialize:
var test = FindPreference("test") as SwitchPreferenceCompat;
test.PreferenceChange += (_, _) => Toast.MakeText(Context, "toggled", ToastLength.Long).Show();

Example project to reproduce: New folder.zip
Did you find any workaround?
I can use a subclass TwoStatePreference or just Preference instead the as SwitchPreferenceCompat case. I assume that the C# type of SwitchPreferenceCompat was trimmed away because no direct properties or methods of it was accessed (only of it's subclasses)
Relevant log output
No response

The app specifies TrimMode=full, does the problem go away if you remove this setting? (blank would be TrimMode=partial)

No crash when I remove TrimMode=full. I forgot to mention that I build & deploy the app using dotnet publish -t:Run, it should be easy to reproduce with my example project.
I was able to resolve the problem in my project easily by casting to another (sub)class, just wanted to make sure you are aware of that edge case. I absolutely love seeing improvements to the trimmer & app size year after year. My apps were reduced by another ~20% after migrating to .NET9. Thank you!!

This also fixes the sample:
[DynamicDependency(DynamicallyAccessedMemberTypes.All, typeof(SwitchPreferenceCompat))]
public override void OnCreatePreferences(Bundle savedInstanceState, string rootKey)

But I'll investigate what we should do here. I suspect the "MarkJavaObjects" trimmer step could need changes here.

The case is actually similar to a test we have here:
https://github.com/dotnet/android/blob/f09caedb350256df1cb8d9d6b823f28f91d0722f/tests/Mono.Android-Tests/Android.Graphics/NinePatchTests.cs#L27-L34
NinePatchDrawable's constructors weren't preserved, and so we had no way to cast to it from Java via the (IntPtr,JniHandleOwnership) constructor.

I've been debugging the trimmer to understand what is happening:

Suppose the only usage of a type such as NinePatchDrawable is d as NinePatchDrawable, same as the issue here.

The trimmer optimizes this completely away:

	[Test]
	[TestCaseSource("NinePatchDrawables")]
	public void DrawableFromRes_ShouldBeTypeNinePatchDrawable(int resId, string name)
	{
		Assert.IsNotNull(Application.Context.Resources.GetDrawable(resId), "An image should have been retrieved from resource `" + name + "`.");
		Assert.IsNotNull(null, "The drawable created from resource `" + name + "` should be a NinePatchDrawable.");
	}

It's literally inlined to null!

https://github.com/dotnet/runtime/blob/270c2b13a047d90c2050911e1232e00f0e7511a4/src/tools/illink/src/linker/Linker.Steps/MarkStep.cs#L484

This optimization pass happens during MarkStep, and MarkJavaObjects happens later. We are trying to "preserve any Java objects" that are left after MarkStep, but MarkStep is removing any usage of NinePatchDrawable.
Unsure what to do here yet, will discuss with our team.

Another workaround is:
<PropertyGroup>
  <_ExtraTrimmerArgs>--disable-opt unusedtypechecks $(_ExtraTrimmerArgs)</_ExtraTrimmerArgs>
</PropertyGroup>

If a type can be created in Java, this optimization can break.
We are making this change, as it appears to affect app size only a minor amount: less than our threshold of 5% per file or 3% overall.


Merge to live 2021-11-10

OPS succeeds, no changes to docfx.json, this can merge.

Docs Build status updates of commit f202c01:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/azure-datalake-store/azure.datalake.store.lib.DatalakeRESTInterface.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msal/msal.oauth2cli.oauth2.Client.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msrest/msrest.serialization.Model.yml
:warning:Warning
View (azure-python)
Details

docs-ref-mapping/reference-preview.yml
:warning:Warning

Details

docs-ref-services/latest/eventgrid-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/latest/monitor-query-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/latest/servicebus-readme.md
:warning:Warning
View (azure-python)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentAnalysisClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentContentElement.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentLine.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentModelAdministrationClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentSelectionMark.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentWord.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.FormRecognizerClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.FormTrainingClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.DocumentAnalysisClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.DocumentModelAdministrationClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.FormRecognizerClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.FormTrainingClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentifier.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentifierKind.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentityClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationTokenScope.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationUserIdentifier.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationUserProperties.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.aio.CommunicationIdentityClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.SynapseManagementClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.aio.SynapseManagementClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.aio.operations.KustoPoolsOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.models.EventHubDataConnection.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.operations.KustoPoolsOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.SearchClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.aio.SearchClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.SearchIndexClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.SearchIndexerClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.aio.SearchIndexClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.aio.SearchIndexerClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.models.SearchIndexerDataSourceConnection.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.models.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.models.ScoringStatistics.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.ArtifactsClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.ArtifactsClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.BigDataPoolsOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DataFlowDebugSessionOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DataFlowOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DatasetOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.IntegrationRuntimesOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.KqlScriptOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.KqlScriptsOperations.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.LibraryOperations.yml
:warning:Warning
View (azure-python-preview)
Details

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

docs-ref-autogen/azure-datalake-store/azure.datalake.store.lib.DatalakeRESTInterface.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 38, Column 19: [Warning: xref-not-found] Cross reference not found: '2018-09-01'.
Line 43, Column 20: [Warning: xref-not-found] Cross reference not found: '60'.
Line 50, Column 7: [Warning: xref-not-found] Cross reference not found: '<xref:optional arguments to auth'.

docs-ref-autogen/msal/msal.oauth2cli.oauth2.Client.yml

Line 159, Column 7: [Warning: xref-not-found] Cross reference not found: 'collections.Iterable'.
Line 222, Column 7: [Warning: xref-not-found] Cross reference not found: 'collections.Iterable'.
Line 310, Column 7: [Warning: xref-not-found] Cross reference not found: 'Callable'.

docs-ref-autogen/msrest/msrest.serialization.Model.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 32, Column 7: [Warning: xref-not-found] Cross reference not found: 'function'.
Line 59, Column 11: [Warning: xref-not-found] Cross reference not found: 'DeserializationError if something went wrong'.
Line 95, Column 11: [Warning: xref-not-found] Cross reference not found: 'DeserializationError if something went wrong'.

docs-ref-mapping/reference-preview.yml

Line 91, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.digitaltwins.pre'.
Line 165, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.Purview.pre'.
Line 187, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceGraph.Management.pre'.
Line 195, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.python.sdk.landingPage.services.ResourceMover.Management.pre'.

docs-ref-services/latest/eventgrid-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'eventgrid'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 19, Column 119: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/overview' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 127: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/custom-event-quickstart-portal' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 365: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/custom-event-quickstart' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 459: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 96, Column 251: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/get-access-keys' will be broken in isolated environments. Replace with a relative link.
Line 113, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts#topics' will be broken in isolated environments. Replace with a relative link.
Line 116, Column 12: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-domains' will be broken in isolated environments. Replace with a relative link.
Line 116, Column 340: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-domains' will be broken in isolated environments. Replace with a relative link.
Line 121, Column 6: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts#events' will be broken in isolated environments. Replace with a relative link.
Line 126, Column 45: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/input-mappings' will be broken in isolated environments. Replace with a relative link.
Line 126, Column 226: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-schema' will be broken in isolated environments. Replace with a relative link.
Line 129, Column 263: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/cloud-event-schema' will be broken in isolated environments. Replace with a relative link.
Line 150, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/system-topics' will be broken in isolated environments. Replace with a relative link.
Line 153, Column 56: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/system-topics' will be broken in isolated environments. Replace with a relative link.
Line 155, Column 65: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts' will be broken in isolated environments. Replace with a relative link.
Line 159, Column 359: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/kubernetes/overview' will be broken in isolated environments. Replace with a relative link.
Line 451, Column 63: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/event-grid/overview' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/monitor-query-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'monitor'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 17, Column 85: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/logs/data-platform-logs' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 359: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/logs/data-platform-logs#log-analytics-workspaces' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 547: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/data-explorer/kusto/query/' will be broken in isolated environments. Replace with a relative link.
Line 20, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/essentials/data-platform-metrics' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/monitor-query-readme?view=azure-python-preview' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/monitor-query-readme?view=azure-python-preview
Line 27, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 30: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/logs/quick-create-workspace' will be broken in isolated environments. Replace with a relative link.
Line 421, Column 44: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-monitor/' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/servicebus-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'servicebus'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 5, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'magpint' is not a valid Microsoft alias.
Line 28, Column 192: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/' will be broken in isolated environments. Replace with a relative link.
Line 50, Column 23: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-create-namespace-portal' will be broken in isolated environments. Replace with a relative link.
Line 54, Column 71: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-create-namespace-portal' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 55: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 327: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-create-namespace-portal#get-the-connection-string' will be broken in isolated environments. Replace with a relative link.
Line 82, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-authentication-and-authorization' will be broken in isolated environments. Replace with a relative link.
Line 90, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview#queues' will be broken in isolated environments. Replace with a relative link.
Line 92, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview#topics' will be broken in isolated environments. Replace with a relative link.
Line 94, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' will be broken in isolated environments. Replace with a relative link.
Line 96, Column 49: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview' will be broken in isolated environments. Replace with a relative link.
Line 235, Column 107: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview#topics' will be broken in isolated environments. Replace with a relative link.
Line 483, Column 70: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/service-bus/' will be broken in isolated environments. Replace with a relative link.
Line 488, Column 16: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/servicebus/management?view=azure-python' will be broken in isolated environments. Replace with a relative link.
Line 488, Column 16: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/servicebus/management?view=azure-python

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentAnalysisClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._form_base_client.FormRecognizerClientBase'.
Line 52, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 109, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentContentElement.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentLine.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 49, Column 7: [Warning: xref-not-found] Cross reference not found: 'iterable'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentModelAdministrationClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._form_base_client.FormRecognizerClientBase'.
Line 56, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 345, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.
Line 405, Column 7: [Warning: xref-not-found] Cross reference not found: 'Dict'.
Line 433, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentSelectionMark.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._models.DocumentContentElement'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.DocumentWord.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._models.DocumentContentElement'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.FormRecognizerClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._form_base_client.FormRecognizerClientBase'.
Line 51, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 110, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 286, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 478, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 641, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 791, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 1017, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.FormTrainingClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer._form_base_client.FormRecognizerClientBase'.
Line 48, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 334, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.
Line 406, Column 7: [Warning: xref-not-found] Cross reference not found: 'Dict'.
Line 406, Column 31: [Warning: xref-not-found] Cross reference not found: 'Union'.
Line 440, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.DocumentAnalysisClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer.aio._form_base_client_async.FormRecognizerClientBaseAsync'.
Line 53, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 111, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.DocumentModelAdministrationClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer.aio._form_base_client_async.FormRecognizerClientBaseAsync'.
Line 57, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 352, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.
Line 412, Column 7: [Warning: xref-not-found] Cross reference not found: 'Dict'.
Line 440, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.FormRecognizerClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer.aio._form_base_client_async.FormRecognizerClientBaseAsync'.
Line 52, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.
Line 112, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 292, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 487, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 655, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 810, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 1044, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.

preview/docs-ref-autogen/azure-ai-formrecognizer/azure.ai.formrecognizer.aio.FormTrainingClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.ai.formrecognizer.aio._form_base_client_async.FormRecognizerClientBaseAsync'.
Line 49, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.
Line 342, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.
Line 416, Column 7: [Warning: xref-not-found] Cross reference not found: 'Dict'.
Line 416, Column 31: [Warning: xref-not-found] Cross reference not found: 'Union'.
Line 452, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.HttpResponseError or azure.core.exceptions.ResourceNotFoundError'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentifier.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'typing_extensions.Protocol'.
Line 24, Column 5: [Warning: xref-not-found] Cross reference not found: 'Mapping'.
Line 24, Column 20: [Warning: xref-not-found] Cross reference not found: 'str,'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentifierKind.yml

Line 10, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.str'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationIdentityClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 21, Column 7: [Warning: xref-not-found] Cross reference not found: 'TokenCredential'.
Line 133, Column 7: [Warning: xref-not-found] Cross reference not found: 'tuple of'.
Line 209, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.communication.identity.CommunicationUserIdentifier.'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationTokenScope.yml

Line 10, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.str'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationUserIdentifier.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 33, Column 5: [Warning: xref-not-found] Cross reference not found: 'Mapping'.
Line 33, Column 20: [Warning: xref-not-found] Cross reference not found: 'str,'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.CommunicationUserProperties.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.dict'.

preview/docs-ref-autogen/azure-communication-identity/azure.communication.identity.aio.CommunicationIdentityClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 22, Column 7: [Warning: xref-not-found] Cross reference not found: 'AsyncTokenCredential'.
Line 47, Column 7: [Warning: xref-not-found] Cross reference not found: 'tuple of'.

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.SynapseManagementClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 16, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.aio.SynapseManagementClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 17, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.aio.operations.KustoPoolsOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 522, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 553, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 582, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 617, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 649, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 665, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 697, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.models.EventHubDataConnection.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.mgmt.synapse.models._models_py3.DataConnection'.

preview/docs-ref-autogen/azure-mgmt-synapse/azure.mgmt.synapse.operations.KustoPoolsOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 512, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 542, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 570, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 605, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 637, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 653, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 685, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.SearchClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 27, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 115, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 157, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 160, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 185, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 225, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 244, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 247, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 276, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 279, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 629, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 660, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 663, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.aio.SearchClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 28, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.
Line 117, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 160, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 163, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 188, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 229, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 248, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 251, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 281, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 284, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 635, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 667, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.
Line 670, Column 7: [Warning: xref-not-found] Cross reference not found: 'List'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.SearchIndexClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 22, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 48, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 80, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 132, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.ResourceNotFoundError,         azure.core.exceptions.ResourceModifiedError,         azure.core.exceptions.ResourceNotModifiedError,         azure.core.exceptions.ResourceNotFoundError,         azure.core.exceptions.ResourceExistsError'.
Line 214, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 267, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 294, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 347, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 367, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 387, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 407, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.SearchIndexerClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 22, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.
Line 265, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 265, Column 31: [Warning: xref-not-found] Cross reference not found: '*'.
Line 283, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 283, Column 99: [Warning: xref-not-found] Cross reference not found: '*'.
Line 315, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 315, Column 31: [Warning: xref-not-found] Cross reference not found: '*'.
Line 347, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 347, Column 79: [Warning: xref-not-found] Cross reference not found: '*'.
Line 373, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 393, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 423, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 459, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.aio.SearchIndexClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 23, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.
Line 47, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.indexes.models.AnalyzeRequest'.
Line 49, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 82, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 134, Column 11: [Warning: xref-not-found] Cross reference not found: 'azure.core.exceptions.ResourceNotFoundError,         azure.core.exceptions.ResourceModifiedError,         azure.core.exceptions.ResourceNotModifiedError,         azure.core.exceptions.ResourceNotFoundError,         azure.core.exceptions.ResourceExistsError'.
Line 216, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 269, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 296, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 349, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 369, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 389, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 409, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.aio.SearchIndexerClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents._headers_mixin.HeadersMixin'.
Line 23, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.
Line 247, Column 153: [Warning: xref-not-found] Cross reference not found: 'les\async_samples\sample_data_source_operations_async.py '.
Line 247, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.indexes.models.SearchIndexerDataSourceConnectionRetrieve a SearchIndexerDataSourceConnection<!--'.
Line 247, Column 134: [Warning: xref-not-found] Cross reference not found: '!code-python'.
Line 247, Column 154: [Warning: xref-not-found] Cross reference not found: 'Main'.
Line 247, Column 233: [Warning: xref-not-found] Cross reference not found: '--<!-- literal_block {"ids":'.
Line 263, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 263, Column 31: [Warning: xref-not-found] Cross reference not found: '*'.
Line 271, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 271, Column 99: [Warning: xref-not-found] Cross reference not found: '*'.
Line 304, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 304, Column 31: [Warning: xref-not-found] Cross reference not found: '*'.
Line 336, Column 7: [Warning: xref-not-found] Cross reference not found: '*list'.
Line 336, Column 79: [Warning: xref-not-found] Cross reference not found: '*'.
Line 362, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 382, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 412, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 448, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.models.SearchIndexerDataSourceConnection.yml

Line 43, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.models.DataChangeDetectionPolicy'.
Line 47, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.models.DataDeletionDetectionPolicy'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.models.yml

Line 28, Column 19: [Warning: xref-not-found] Cross reference not found: 'search_service_client.models.Field'.
Line 197, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.indexes.models.AnalyzerName'.
Line 263, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.indexes.models.AnalyzerName'.
Line 328, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.search.documents.indexes.models.AnalyzerName'.

preview/docs-ref-autogen/azure-search-documents/azure.search.documents.models.ScoringStatistics.yml

Line 19, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.str'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.ArtifactsClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 16, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials.TokenCredential'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.ArtifactsClient.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 17, Column 7: [Warning: xref-not-found] Cross reference not found: 'azure.core.credentials_async.AsyncTokenCredential'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.BigDataPoolsOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 60, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 82, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DataFlowDebugSessionOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 61, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 112, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 164, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 192, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 217, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DataFlowOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 98, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 147, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 202, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 239, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 264, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.DatasetOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 98, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 147, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 202, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 240, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 263, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.IntegrationRuntimesOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 60, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 82, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.KqlScriptOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 89, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 137, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 191, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 217, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.KqlScriptsOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 57, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

preview/docs-ref-autogen/azure-synapse-artifacts/azure.synapse.artifacts.aio.operations.LibraryOperations.yml

Line 7, Column 3: [Warning: xref-not-found] Cross reference not found: 'builtins.object'.
Line 55, Column 7: [Warning: xref-not-found] Cross reference not found: 'IO'.
Line 63, Column 7: [Warning: xref-not-found] Cross reference not found: 'long'.
Line 87, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 141, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 195, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 249, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 280, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 309, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.
Line 332, Column 11: [Warning: xref-not-found] Cross reference not found: '~azure.core.exceptions.HttpResponseError'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Closing this issue.


fix: correct display for warnings

fixes #322

I found that with this PR implementation, warnings are not displayed in case of compile errors.
https://user-images.githubusercontent.com/29677552/235648174-99cfcd58-fa88-4cc9-ad10-47d4682cda03.mov
This is because this PR implementation uses onwarn in svelte.config.js, which means that we are not notified that warnings have been cleared, so each time we clear the warnings store. (If using sendWarningsToBrowser, we are notified of an empty array.)
onwarn is line 140, sendWarningsToBrowser is line 156:
https://github.com/sveltejs/vite-plugin-svelte/blob/aba990bc8fd0dcaa8107ebf28e0504cdb0b376c9/packages/vite-plugin-svelte/src/utils/log.ts#L138-L156
If you want to fix this part too, please do not merge this PR yet, because I also need to change vite-plugin-svelte.


adds implementation of TypeCache

Issue #15
Description of changes:
This PR works on implementation of  TypeCache.
Change:

creates a struct TypeCache which helps with the cycling issue as described in #15.
creates a type TypeId which represents the index/id for Types stores in TypeCache.
modifies the Constraints to store Vec<TypeId> instead of Vec<Type>.
modifies Scehma struct to store the TypeCache that is created while loading the schema instead of a HashMap<String, Type>. (This TypeCache will help in resolving the TypeIds while validation)
modifies get_types() in Schema as it needs to return an Iterator and not the HashMap/ TypeCache stored inside Schema.(I will work on this on next PR)

Thanks for your feedback, @popematt!
Per our offline discussion, TypeId is a hidden implementation detail. Passing around indexes into a Vec is a common Rust idiom for representing cyclic graph structures in memory (see the petgraph crate for a popular library leveraging this approach).
The types in this PR are intended to constitute the normalized, in-memory representation of a schema, its imports, and their types. We have not yet designed the API for constructing types/schemas programmatically; I expect it to use distinct public-facing types that get normalized into this PR's types via a SchemaSystem. This design work is our next priority.


About creating participant using xml string.

Hi,
In the current version I know that I can only create participant through mr_write_create_participant_ref().
Will you also support REPRESENTATION_AS_XML_STRING method?
And Agent only supports "default participant" for REPRESENTATION_BY_REFERENCE method.
Will you support other strings later?

Hi @OpusK,
Yes there is a mr_configure_participant_xml function which allows you create participant by XML.
It is also planning to create a customizable database for REF entities. It is expected that we launch this feature in the coming weeks.

Hi, @julianbermudez,
I look forward to the update. Thank you.

@julianbermudez,
Cool! Thanks for your hard works!


Fixed a typo

style: .Succes was changed to style: .succes

@celikomer even this a typo, it should be .success

Ops, I missed that. Thanks for the correction


setBackgroundMessageHandler never fired

The background handler is not working: no matter what I do, the sw always use the regular onMessage, displaying the actual notification I sent instead of the custom one set on the handler.
My code is the exact same as the one in the repo:
messaging.setBackgroundMessageHandler(function(payload) {
    console.log('[firebase-messaging-sw.js] Received background message ', payload);
    // Customize notification here
    const notificationTitle = 'Background Message Title';
    const notificationOptions = {
        body: 'Background Message body.',
        icon: '/Content/Img/logo-amezze-120.png'
    };

    return self.registration.showNotification(notificationTitle,
        notificationOptions);
});

@wizzar how did you solve this? I have the same problem...

Turns out the problem was in my json. There's a footnote  on the documentation that says if your json defines notification property, then the setBackgroundMessageHandler is ignored.
So, this won't trigger the handler:
{
    "to": "abc",
    	"notification": {
        "title": "Hello",
        "body": "world"
    }
}

but this will:
{
    "to":  "abc",

    "data": {
    	"notification": {
        "title": "Hello",
        "body": "world"
    }
    }
}

This way you can send the notification in the data.

Thank you so much!

I had the same problem, but not due to the "notification" field.
The problem was the "content_available" field.
This was NOT working (despite the lack of "notification"):
{
   "content_available": true,
   "data": {
      "aaa": "bla bla"
      "bbb": "bli bli"
   }
}

This is working:
{
   "content_available": false,
   "data": {
      "aaa": "bla bla"
      "bbb": "bli bli"
   }
}

Sounds like a bug, since according to the FCM doc this "content_available" flag is only for iOS...
https://firebase.google.com/docs/cloud-messaging/concept-options

I am wondering why the included notification should take precedence over the service worker...
It is not some kind of hard limitation, since the firebase-messaging.js code clearly handles the notification part (it is even easy to understand from the minified code).
The problem is that this "feature" ruins my efforts to use the same messages for different platforms (eg. Web and Android), since I do not want to populate the "click_action" field in the sent message (as it would break the click handling in Android), but I still want to send the user to a page when the notification is clicked on the web.
It would be easy to achieve this if I could eg. include the desired target url in a special field of the data payload and use the service worker to inject it as a click_action in the generated notification...

@nemphys I have been having the exact same problem. It seems like a catch 22. You must include the "notification" object for IOS to display a notification when the app is not in the foreground. If you include the "notification" object then you cannot customize the "click_action" in a Web app. If you specify a "click_action" as a URL then Android will not open your app when it is clicked (IOS opens your app fine surprisingly). If you are not worried about IOS then you could implement the FirebaseMessagingService in your Android app and remove the "notification" object. You could then use custom data keys and control the code to show the notification yourself in both the Web app and the Android app. Doing this would cause IOS not to show any notifications when your app is not in the foreground though.
I completely agree with you, they should allow you to override the notification code (to set a custom "click_action") even when a "notification"object is specified. Or they should allow for an "android_click_action" which overrides the "click_action" for Android apps.

@UniBrowse Nice to know that I am not alone here :-)
One can either go with the method you propose, or decide to separate the logic for the web and handle the apps (Android & iOS) differently (which is what I think I will eventually do, since it makes more sense to me).
It is a shame though, since it would be really easy to implement something like this in firebase-messaging.js.
People from Google: anybody listening to this (and care to explain why you made this decision?)
PS. I have a feeling that I will go through all the trouble to create a separate message logic server-side for the web app and after a few days they will finally implement it...

+1

How can you cutomize the click_action? My messages are sent without the notification property. I tried to add the click_action property to the notificationOptions in my BackgroundMessageHandler like this:
...
const notificationOptions = {
    body: 'Background Message body.',
    icon: '/Content/Img/logo-amezze-120.png'
    click_action: 'http://localhost:30321/'
};
...

But nothing happens when I click on the notification. I read somewhere, that this is not supported. So created an Event Listener, that reacts to a click on the push notification, something like this:
self.addEventListener('notificationclick', function (event) {
    console.log('On notification click: ', event.notification.tag);
    event.notification.close();

    // This looks to see if the current is already open and
    // focuses if it is
    event.waitUntil(clients.matchAll({
        type: "window"
    }).then(function (clientList) {
        for (var i = 0; i < clientList.length; i++) {
            var client = clientList[i];
            if (client.url == '/' && 'focus' in client)
                return client.focus();
        }
        if (clients.openWindow)
            return clients.openWindow('http://localhost:30321/');
    }));
});

(I got this from here: https://developer.mozilla.org/en-US/docs/Web/API/WindowClient)
By trying this, the clientList is empty. So by clicking on the notification it opens a new window even if the tab, where my application is running, is still open. Anyone have an idea how to fix this?

@nemphys this is a known limitation at the moment and something that I've raised as an issue with the FCM team.

@gauntface where do we track progress on this "catch 22" api?

@kaziller I have add this code in SW:
messaging.setBackgroundMessageHandler(function(push) {    // Any logic here...     var notification = worker.registration.showNotification(title, body);             worker.addEventListener('notificationclick', function() {                 if (clients.openWindow) {                     clients.openWindow('https://....');                 }             });             return notification; });

@kaziller I have add this code in SW:
messaging.setBackgroundMessageHandler(function(push){
     // Any logic here...
     var notification = worker.registration.showNotification(title, body);
     worker.addEventListener('notificationclick', function() {
           if (clients.openWindow) {
                clients.openWindow('https://....');
           }
     });
     return notification;
 };```

@kaziller you can try substituting clients with clientList

Make sure u've added includeUncontrolled property.
event.waitUntil(clients.matchAll({
	  type: "window",
	 includeUncontrolled: true
})

Okay, this is what we call 'GAMBIARRA' in Brazil, (or, workaround for fancy people). It works in Chrome, didn't tested in other browsers...
/*
 * We need a generic class to hold data and methods, that inherit from Event
 */
class CustomPushEvent extends Event {
  constructor(data) {
    super('push')

    Object.assign(this, data)
    this.custom = true
  }
}

/*
 * Overrides push notification data, to avoid having 'notification' key and firebase blocking
 * the message handler from being called
 */
self.addEventListener('push', (e) => {
  // Skip if event is our own custom event
  if (e.custom) return;

  // Kep old event data to override
  let oldData = e.data

  // Create a new event to dispatch
  let newEvent = new CustomPushEvent({
    data: {
      json() {
        let newData = oldData.json()
        newData._notification = newData.notification
        delete newData.notification
        return newData
      },
    },

    waitUntil: e.waitUntil.bind(e),
  })

  // Stop event propagation
  e.stopImmediatePropagation()

  // Dispatch the new wrapped event
  dispatchEvent(newEvent)
})

This should be better documented. It's not intuitive and definitely a gotcha.

I converted @ivanseidel solution (btw thank you) to old good javascript, and I'm posting here to help someone who needs it:
/*
* Overrides push notification data, to avoid having 'notification' key and firebase blocking
* the message handler from being called
*/
self.addEventListener('push', function (e) {
  // Skip if event is our own custom event
  if (e.custom) return;

  // Create a new event to dispatch
  var newEvent = new Event('push');
  newEvent.waitUntil = e.waitUntil.bind(e);
  newEvent.data = {
     json: function() {
         var newData = e.data.json();
         newData._notification = newData.notification;
         delete newData.notification;
         return newData;
     },
  };
  newEvent.custom = true;

  // Stop event propagation
  e.stopImmediatePropagation();

  // Dispatch the new wrapped event
  dispatchEvent(newEvent);
});

@marcosbrigante your solution works but causes the notification to display 4 times (original, new, original, new) any idea why that is?

@gauntface Is there any progress on resolving this issue? Specifically, on resolving the fact that setBackgroundMessageHandler is not called when the notification object is specified and notificationclick events are bypassed when the notification object click_action is specified?

To open an existing tab this worked for me :
self.addEventListener('notificationclick', function(event) {
  event.notification.close();
  event.waitUntil(clients.matchAll({
    type: "window"
  }).then(function (clientList) {

    for (var i = 0; i < clientList.length; i++) {
        var client = clientList[i];
        if (client.url == event.notification.data && 'focus' in client)
            return client.focus();
    }
    if (clients.openWindow)
        return clients.openWindow(event.notification.data);
  }));
});

I had the same problem, but not due to the "notification" field.
The problem was the "content_available" field.
This was NOT working (despite the lack of "notification"):
{
   "content_available": true,
   "data": {
      "aaa": "bla bla"
      "bbb": "bli bli"
   }
}

This is working:
{
   "content_available": false,
   "data": {
      "aaa": "bla bla"
      "bbb": "bli bli"
   }
}

Sounds like a bug, since according to the FCM doc this "content_available" flag is only for iOS...
https://firebase.google.com/docs/cloud-messaging/concept-options

Thanks a ton

@marcosbrigante I am seeing that your solution works but causes the notification to display 2 times: original & new

@kaziller you should accept clients in a service worker like this: https://developer.mozilla.org/en-US/docs/Web/API/Clients

This was very helpful thank you

@marcosbrigante I am seeing that your solution works but causes the notification to display 2 times: original & new

I have been facing the same issue of getting notification twice, is there any solution for this?
My code:
`importScripts('https://www.gstatic.com/firebasejs/8.2.1/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/8.2.1/firebase-messaging.js');
firebase.initializeApp({
......
});
const messaging = firebase.messaging();
messaging.onBackgroundMessage(function (payload) {
console.log('[firebase-messaging-sw.js] Received background message ', payload);
// Customize notification here
const notificationTitle = 'Background Message Title';
const notificationOptions = {
body: 'Background Message body.',
icon: '/notification-flat.png'
};
return self.registration.showNotification(notificationTitle,
    notificationOptions);

});`

If you are using react native and @react-native-firebase/messaging.
In index.js file
import messaging from '@react-native-firebase/messaging';
/*
Set a message handler function which is called when
the app is in the  background or terminated.
In Android, a headless task is created, allowing
you to access the React Native environment to
perform tasks such as updating local storage,
or sending a network request.

This method must be called outside of your application
lifecycle, e.g.  alongside your AppRegistry.registerComponent()
method call at the the entry point of your application code.
*/
messaging().setBackgroundMessageHandler(async remoteMessage => {
  // you can update localstorage or send an api request here
});

could you provide me your index.js (hide your necessary part after that send me here it will very helpfull for me)

@TitanArmy Right now, I'm not using this callback in my code it's there so that I don't get any error.
There is another package @notifee/react-native that is used for local notifications and other stuff, I'm handling background events/messages using that.
Currently the implementation is something like this:

Turns out the problem was in my json. There's a footnote on the documentation that says if your json defines notification property, then the setBackgroundMessageHandler is sort of ignored.
"Note: If you set notification fields in your HTTP or XMPP send request, those values take precedence over any values specified in the service worker." https://firebase.google.com/docs/cloud-messaging/js/receive
So, this won't trigger the handler:
{
    "to": "abc",
        "notification": {
        "title": "Hello",
        "body": "world"
    }
}

but this will:
{
    "to":  "abc",

    "data": {
        "notification": {
        "title": "Hello",
        "body": "world"
    }
    }
}

This way you can send the notification in the data.

Which json ? And how u disable caching in js ?


Fix return types of responses to view requests

This fixes an issue that was introduced with 72258e2 and e5b1aee.
Background:
Although all things still seemed to work, each request to a view
generated an exception with the following stack trace:
exception error: undefined function vacc:get/2
  in function  chttpd:result/2 (src/chttpd.erl, line 297)
  in call from chttpd:handle_request_int/1 (src/chttpd.erl, line 276)
  in call from mochiweb_http:headers/6 (src/mochiweb_http.erl, line 122)

/:

Well, I'm also :/ on this. I'd love to understand why the corresponding requests would succeed anyway, but don't have time to dig deep enough for that right now.

May be:
    case is_record(Resp2, vacc) of
        true -> {ok, Resp2#vacc.resp};
        _ -> {ok, Resp2}
    end.

Had some meaning there and it worth to restore it?

At least I'm quite sure about this one…
Previously this was needed because couch_httpd:etag_maybe/2 was called there. Its return value contains either a mochiweb response (if the etag matches), or a vacc record (if the etag doesn't match).
Now that we don't call couch_httpd:etag_maybe/2 there anymore, the response should always be a vacc record, and therefore the case clause should be obsolete.

Tested now. Looks as everything works, so +1 for the fix, but you brought COUCHDB-2650. What shall we do? Seems like there is no way, but to implement Etag property for 2.0 (:


Dashbaord Redirect Assertion - Status Correction

Description
Changes proposed in this pull request:

Change http status from redirection (302) to successful response (200) since there is no more redirection happening.

Related issue(s)

/test pre-main-control-plane-reconciler-upgrade-kyma2-latest-to-main-gardener

/test pre-main-control-plane-reconciler-e2e

/test pre-main-control-plane-reconciler-e2e-latest-release

/test pre-main-control-plane-reconciler-e2e-latest-release

/test pre-main-control-plane-reconciler-e2e

/test all

/test all


CMS investigation based on joomla

@chyang001

cms automatically increment the grade for students

@chyang001 book and user, deadline: 2015.3.29


VSS Missing

I'm fairly confident VSS backups are not available on Linux, if confirmed can that be added to this document. Thanks

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

ID: 2210b67e-43d9-0ac1-4fff-63387d112f77
Version Independent ID: d9484c3f-2f64-a8d2-fb71-40d1776904ae
Content: Editions and supported features of SQL Server 2019 - Linux - SQL Server
Content Source: docs/linux/sql-server-linux-editions-and-components-2019.md
Product: sql
Technology: linux
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@jdanton -- thank you for your feedback.  You may find confirmation here:

DBA Stack Exchange
Stack Overflow

@VanMSFT -- please look into this issue.

Hi @jdanton! We don't list external features in this doc.
@tejasaks - Please let us know if you have any thoughts on this.

Agreed. VSS is a Windows functionality that SQL Server has an agent for. So more accurate would be saying VSS doesn't exist on Linux so SQL Server isn't enabled for it, which in this case would be like stating the obvious.

Thanks, @tejasaks!
@jdanton - We'll go ahead and close this, but let us know if you have any concerns. Thanks!


Favor upsert over add + use element_id to prevent duplicates

Make chroma ingest pipeline idempotent :)
@potter-potter

@0xjgv Thanks for this! And thanks for alerting me. Great idea.
I will bring it up to the team.

@ahmetmeleq @0xjgv can you see any downsides to doing it this way? (seems like it is a good idea all aound)

@ryannikolaidis Think this change will affect any users of ChromaDB that expect duplicates? (not sure why they would want duplicates....)

@ryannikolaidis Think this change will affect any users of ChromaDB that expect duplicates? (not sure why they would want duplicates....)

with matching ids? I think that's okay

@ahmetmeleq @0xjgv can you see any downsides to doing it this way? (seems like it is a good idea all around)

🤔 I can't think of any downsides though. Collisions are not very likely and there are no clear advantages to allowing duplicates in the DB. Idepomtecy reduces storage space, increases query performance, and simplifies data maintenance and integrity.

@0xjgv Thanks for this! I am putting it into a small pr with one other small update so that it runs through our CI/CD.
https://github.com/Unstructured-IO/unstructured/pull/3086

Implemented in https://github.com/Unstructured-IO/unstructured/pull/3086


Property or method “css” is not defined on the instance

I'm trying to get Vuetable-2 to work in our solution. The demo works without problems. The difference is that we use a lot of different modules and I'm fairly new to front-end development and fail to see what the problem can be.
The difference between the demo and trying to set the demo up in our own project is this:
Demo
import Vuetable from 'vuetable-2/src/components/Vuetable
Our project
import Vuetable from 'vuetable-2/src/components/Vuetable.vue
The reason for doing so is because if I do not (leave out the .vue), I'll get the following error:
ERROR in ./~/buble-loader!./~/vue-loader/lib/selector.js?
type=script&index=0!./resources/assets/js/components/VuetableTest.vue
Module not found: Error: Can't resolve 'vuetable-2/src/components/Vuetable'

But, with the extension added to the import, I'll get this (in the browser console):
[Vue warn]: Property or method "css" is not defined on the instance but referenced during render.
Make sure to declare reactive data properties in the data option.
(found in component <vuetable>)

[Vue warn]: Error when rendering component <vuetable>:
Uncaught TypeError: Cannot read property 'tableClass' of undefined

Now I have the feeling it has something to do with me needing to add the extension to the import, something that is not done within the Vuetable files, for example import VueResource from 'vue-resource'.
Our package.json:
{
  "private": true,
  "scripts": {
    "prod": "gulp --production",
    "dev": "gulp watch"
  },
  "devDependencies": {
    "bootstrap-sass": "^3.3.7",
    "gulp": "^3.9.1",
    "jquery": "^3.1.0",
    "laravel-elixir": "^6.0.0-11",
    "laravel-elixir-vue-2": "^0.2.0",
    "laravel-elixir-webpack-advanced": "*",
    "laravel-elixir-webpack-official": "*",
    "lodash": "^4.14.0",
    "multiselect": "^0.9.12",
    "node-sass": "^3.10.0",
    "notifyjs-browser": "^0.4.2",
    "sweetalert": "^1.1.3",
    "vue": "^2.1.0",
    "vue-resource": "^1.0.2",
    "vue-router": "^0.7.13",
    "vuetable-2": "^1.2.0",
    "vuex": "^2.1.1",
    "whatwg-fetch": "^1.0.0",
    "wow.js": "^1.2.2"
  },
  "dependencies": {
    "laravel-echo": "^1.0.5",
    "pace": "0.0.4",
    "pace-js": "^1.0.2",
    "pusher-js": "^3.2.1"
  }
}

Again, I feel like this has to do with modules we use or elixir settings or whatever, but it's not working out of the box. Sorry for adding this as a new issue to Vuetable, but I don't know where to ask else.

@Tjab Please don't worry. Putting it as an issue is fine.
For your issue, I don't really have any solution as I've never seen that before and I mainly use webpack for my work. Not because I'm the expert in webpack, but because the vue-cli already does all the hard work on that.
I can only guess that it has something to do with the bundler configuration underneath elixir but I can't exactly pinpoint where.
For the first one that you have to put .vue extension in the import, I think there's something wrong with the config of vue-loader
For the second error, that's really new to me and I have no idea why. But if you could share your demo on GitHub, I'll be willing to take a look. However, the elixir stuff could also defeat me. :)

@ratiw Hi! Thanks for the help! Sorry for the late reply, I was on a small holiday 😄
I will not be able to share the code with you, as I'm trying to get the whole thing working in our project (which I cannot share). I can give you more details about our setup, if you can tell me what to show (like the package.json)?
Our gulpfile.js:
var elixir = require('laravel-elixir');
require('laravel-elixir-vue-2');

elixir(function (mix) {

    // Standard css stuff (scss)

    .webpack('app.js', null, null, {
        resolve: {
            alias: {
                'vue$': 'vue/dist/vue.js'
            }
        }
    });

    // Other standard stuff

});

@Tjab I'm not familiar with Laravel Elixir, so it's hard for me to answer that. But recently, I've just create a sample project which uses Vuetable with Laravel 5.4 here. I'm not sure if that helps or not, but maybe you can check it out.

You need babel-loader and then insert this to webpack.config.js Currently vue files are compiled using buble loader. Which expects module.exports = {} I needed a full day to find this.
module.exports = {
    vue: {
        loaders: {
            js: 'babel-loader'
        }
    }
};

@roosh-t3 Thanks for helping! I'm wondering though, I do not have a webpack.config.js in my project? Only a gulpfile.js.

Create a new file in the root. Webpack will read the file.

That does change the error from the buble-loader to babel-loader:
ERROR in ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/IntegrationList.vue
Module not found: Error: Can't resolve 'vuetable-2/src/components/Vuetable' in 'C:\Users\User\Code\project\resources\assets\js\components'
 @ ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/IntegrationList.vue 10:0-58
 @ ./resources/assets/js/components/IntegrationList.vue
 @ ./resources/assets/js/app.js

When I add .vue when importing vuetable-2/src/components/Vuetable, the error is expanded:
ERROR in ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./~/vuetable-2/src/components/Vuetable.vue
Module build failed: Error: Couldn't find preset "stage-2" relative to directory "C:\\Users\\User\\Code\\project\\node_modules\\vuetable-2"

@Tjab Sorry, I forgot to mention babel presets and I have been away. You have to install babel-loader, babel-preset-stage-2 : https://babeljs.io/docs/plugins/preset-stage-2/, you might be required to add another preset and a plugin, if that's not install yet. if errors pops in just google :)
see this issue here : https://github.com/vuejs/laravel-elixir-vue-2/issues/5
and this two : https://github.com/JeffreyWay/laravel-elixir-vue/issues/9


how to to combine text and icons with the recorded video ?

hello how to get the video edited with pictures and texts when i press apply
i got only a video without text and pictures
or where can i get the list of stickers or texts   so i can do it myself
thank you .

You can't get a list, but you can set up a list of stickers.
LFVideoEditingController.h
@property (nonatomic, strong) NSString *stickerPath;
You'll get LFVideoEdit object when you press apply.
@property (nonatomic, readonly) NSURL *editFinalURL; // This is the edited video url.
@property (nonatomic, readonly) UIImage *editPreviewImage; // This is the first frame of the video.

thank for your answer the video from editFinalUrl is just like the original without stickers apply on it
editPreviewImage also containing a screen without stickers on it .
maybe their is a bug on the system that do not provide stickers to the video or the first frame.
the exemple project from the github page also did not provide stickers  on editPreviewImage
or editFinalURL

oops. I'm sorry. This is a issue, and I'll fix it soon.

Please update the version to 1.2.2

amazing it work great now  problem solved !.  thank you !!!


More clone changes

Don't worry about the test failing, I need to update system-npm to use the latest steal.

Ok, thanks.

Going to look at this now.


Add database with indexing

added idb.js as a dependency

sketched rough API for ingesting actors and notes

initial set of indexes we might want (tags, inReplyTo, attributedTo)

[ ] TODO: Fill in the methods

[ ] TODO: Signed fetch

[ ] TODO: Load followed accounts into index on boot

[ ] TODO: Track outbox updates somehow so we don't fetch needlessly?

closing in favor of #5


Param error is incomplete and too ambiguous

When rendering a panel I get the following param error:
WARNING:param.: The Parameterized instance has instance parameters created using new-style param APIs, which are incompatible with .params. Use the new more explicit APIs on the .param accessor to query parameter instances.To query all parameter instances use .param.objects with the option to return either class or instance parameter objects. Alternatively use .param[name] indexing to access a specific parameter object by name.

As far as I can tell I am only using the new-style API. It would be helpful for debugging if the error message where a little more specific about where the incorrect usage came from, or at least what attribute was being accessed in the old way.
(See attached files to reproduce)
Archive.zip

I can't find the text of that error message in the current codebase, nor anything like it, so I think the message has already been replaced or improved.


Add teleport-operator to mc-bootstrap

Deploy teleport-operator as part of MC creation to ensure creation of teleport join token before we pivot from Kind to infrastructure provider (AWS, GCP, etc).

As discussed with the team, we will be using short-lived certificate through Machine ID, teleport-operator no longer needs to be added to mc-bootstrap cause we won't be using static credential.
However, we get into chicken-egg problem, because cluster provider chart references a token which is created by teleport-operator, and since, Machine ID only works when Kubernetes API is ready, we will be creating a dummy teleport join token secret to unblock cluster provider chart, and later when teleport-operator is deployed via app collection, we roll out nodes again.
I think it's not ideal solution, but so far this is what we come up with, until we figure out a better way.


Types exports are wrong in package.json

According to Are The Types Wrong the types for dioma are not set up correctly. The main issue is that the exports property in package.json defines only one type for both the .cjs as well as the .js file:
"exports": {
    ".": {
      "import": "./dist/dioma.js",
      "require": "./dist/dioma.cjs",
      "types": "./dist/index.d.ts"
    }
  },

This is, however, not possible. It needs to export a separate type file for each:
"exports": {
    ".": {
      "import": {
        "types": "./dist/dioma.d.ts",
        "default": "./dist/dioma.js"
      },
      "require": {
        "types": "./dist/dioma.d.cts",
        "default": "./dist/dioma.cjs"
      }
    },

Note that the types property needs to come first and that the file extension of the types need to match (e.g. .cts and .cjs).
I would also suggest to point the main property export to the ESM export as the package.json defines that this package is an es module.
As an example take a look at openapi-fetch for a library that correctly works in both CommonJS as well as ESM in Node.js: https://github.com/drwpow/openapi-typescript/blob/main/packages/openapi-fetch/package.json.

Many thanks for reporting! Made it green :)


Electron 0.36 broke stdout on Windows

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository? (I think...)
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
It seems that the version of Electron bundled in Atom fails to report any data back on stdout when called as Node. options.env.ELETRON_RUN_AS_NODE is set (to 1), but the stdout callbacks are never called. If you have Node installed on the machine and replace process.execPath with the path to Node everything works as expected (tested with Node v5.9.0).
This has been reported as an issue by users updating to v1.7.0 on the following linter plugins:

linter-jshint
linter-htmlhint
linter-csslint
Possibly linter-bootlint as well (Looks like this might just be user error)

Note that none of those linters have AppVeyor (Windows) CI testing configured.
The following Node based linters are being tested on AppVeyor, but it turns out all of these are directly being require'd, and as such aren't being ran as an "external" Node process:

linter-stylelint
linter-js-yaml

linter-eslint is interesting in that it is working, but it utilizes a worker process that is being created with child_process.fork().
This might be a duplicate of https://github.com/atom/atom/issues/2887, is probably caused by https://github.com/atom/atom/pull/9627, and might be related to https://github.com/atom/atom/pull/11162.
If there is any further information or debugging information that would help please let me know. I'm almost always available as @arcanemagus on Atom's Slack instance if anything is needed.
@50Wliu, @joshaber, @joefitzgerald I'm tagging you three as it seems you have all worked on parts of the Electron update and might know more about how to further test this.
Steps to Reproduce

Open Atom v1.7.0 or above
Use something that attempts to load a Node process (ie: BufferedNodeProcess, or more indirectly  linter-jshint)
Observe that the stdout callbacks are never called

Expected behavior: [What you expected to happen]
Calling a Node process works as expected
Actual behavior: [What actually happened]
The stdout callback is never called, so the process stdout never gets any data.
Versions
OS: Windows 7 - 10
Atom: v1.7.0 - v1.8.0-beta0
Atom v1.8.0-beta0:
Atom    : 1.8.0-beta0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

Here's a (relatively) small bit of code to reproduce this, place the following as a package in Atom:
index.js:
'use babel'

import { CompositeDisposable, BufferedNodeProcess } from 'atom';
import { join } from 'path';

function runExternalNode() {
  const data = { stdout: [] };

  const params = {
    command: join(__dirname, 'node_script.js'),
    stdout(chunk) {
      data.stdout.push(chunk)
    },
    exit() {
      data.stdout = data.stdout.join('').trim();
      console.log(data.stdout);
    }
  };

  let spawnedProcess = new BufferedNodeProcess(params);
}

export default {
  activate() {
    this.subscriptions = new CompositeDisposable();

    this.subscriptions.add(atom.commands.add('atom-text-editor', {
      'node-test:run': () => {
        runExternalNode();
      }
    }));

    runExternalNode();
  },

  deactivate() {
    this.subscriptions.dispose()
  }
}

node_script.js:
console.log('42');

package.json:
{
  "private": true,
  "name": "node-test",
  "description": "Test for running Node scripts within Atom",
  "version": "0.0.1"
}

For convenience here is a ZIP of those files: node-test.zip

When launching Atom with that package I get a blank line logged to the console, a breakpoint placed in the stdout() callback is never triggered. If you replace process.execPath with the path to a local Node install and then call the Node Test: Run command then 42 is output to the console as expected.
Note that we have tested this with the child_process module with the same results.

Thanks, @Arcanemagus, that's super helpful

Updated the description with clearer notes on a few packages that are failing, and a few that are not and how those are ran.

Fixed in v1.7.1.

Thanks guys for a quick resolution.


CONTRIBUTING: explain how to add appcasts

Expands on https://github.com/caskroom/homebrew-cask/issues/16464. That one was about updating, this is about creating.
There are some doubts as to how to create appcasts. That is merely an example of someone that expressed it, though, as I also see new contributions that could easily have an appcast added (github releases), but don’t. We should really add a how to add them.

[x] Explain how to find them:

[x] If the cask uses the app stanza, look inside its Info.plist for the SUFeedURL.

[x] Make /developer/bin script for it.

[x] If the app is distributed via gitub releases, appcast will be of the form https://github.com/{{user}}/{{project}}/releases.atom.
[x] An appcast can be any URL hosted by the app’s developer that changes every time a new release is out (e.g. a changelog).

[x] Explain how to find its :sha256 (curl '{{appcast_url}} | sed '/<pubDate>/d' | shasum --algorithm 256 | awk '{print $1}').

I can tackle this as part of an upcoming (further) rewrite of CONTRIBUTING

@adityadalal924 Will leave the documentation to you, then.
As for the script, adding it in https://github.com/caskroom/homebrew-cask/pull/16701.

This is getting quite a bit of usage already - I'll draft up something that can be added to the relevant documentation soon.

Appcasts
Appcasts provide a mechanism for updates to applications. There are a few different ways these can be determined:

If the app is distributed via GitHub releases, the appcast will be of the form https://github.com/{{user}}/{{project}}/releases.atom. Example of Cask
A popular update framework, Sparkle generally uses the SUFeedURL property inside Contents/Info.plist. You can use the script developer/bin/find_sparkle_appcast to add this automatically. Example of Cask
An appcast can be any URL hosted by the app’s developer that changes every time a new release is out (e.g. a changelog RSS feed). Example of Cask

Appcasts have a required :sha256 property. You can use  (curl '{{appcast_url}} | shasum --algorithm 256) to get the shasum for the appcast.
If the application has a Check for Updates... option in its menu, you should also add 'auto_updates true` to the Cask.

@vitorgalvao Documentation above should now be ready, according to recent updates.

@adityadalal924 I saw. I was editing your post (after editing the top one) and github warned me “the content you’re trying to edit has changed”.

@adityadalal924 Oh, you called it :checkpoint already, even. That I hadn’t noticed.

Still undecided about {{appcast_url}} vs $appcast_url styling for user-replaced variables. If you like that then CONTRIBUTING.MD should also use that style - whatever we decide, it should be consistent (We can always add a footnote about this format and what it means as extra clarification)

Still undecided about {{appcast_url}} vs $appcast_url styling for user-replaced variables.

Whatever you prefer. You’ve been working more on CONTRIBUTING, so I trust the decision to you.
I somewhat prefer ${appcast_url} to $appcast_url, though (same with other variables) as it’s clearer where it begins and ends.

Made another change (addition) to the command. curl now uses --compressed. It doesn’t change anything in the ones that were already set, but it lets us use the ones that are gzipped on transfer.

Will update as script is updated in cask-repair (I'm using that as "ground truth" for the documentation for now)

curl --silent 'https://raw.githubusercontent.com/vitorgalvao/tiny-scripts/master/cask-repair' | grep 'pubDate' should be a quick way to see how it currently works in cask-repair. It’s unlikely there’ll be more changes, though.