Create TestingPullRequest.md

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

Line 16: [Error] Restore nuget package W:\zdoo-s.optemp\packages\opbuild.scripts.1.47.2\tools\packages.config in folder:W:\zdoo-s.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in http://SiteHelp. Detailed error:  Errors in packages.config projects     Unable to find version '1.47.2' of package 'opbuild.initializecrrtool'.       D:\Windows\system32\config\systemprofile.nuget\packages: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'D:\Windows\system32\config\systemprofile.nuget\packages'.       https://www.myget.org/F/op/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op/api/v2/'.       https://www.myget.org/F/op-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op-dev/api/v2/'.       https://www.myget.org/F/docfx/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx/api/v2/'.       https://www.myget.org/F/docfx-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx-dev/api/v2/'.       https://nuget.org/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://nuget.org/api/v2/'.

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.CheckpointFrequency.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessorOptions.yml
:warning:Warning
View
Details

api/Microsoft.ServiceFabric.Services.Remoting.FabricTransport.Runtime.FabricTransportRemotingListenerSettings.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.IChangeFeedProcessor.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILogProvider.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.TraceLogProvider.yml
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

api/Microsoft.Azure.Documents.ChangeFeedProcessor.CheckpointFrequency.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.IPartitionCheckpointer".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.IPartitionCheckpointer".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessorOptions.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.ServiceFabric.Services.Remoting.FabricTransport.Runtime.FabricTransportRemotingListenerSettings.yml

[Warning] 1 invalid cross reference(s) "Microsoft.ServiceFabric.Services.Remoting.V2.ServiceRemotingRequestMessageHeader".
[Warning] 1 invalid cross reference(s) "Microsoft.ServiceFabric.Services.Remoting.V2.ServiceRemotingRequestMessageHeader".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.IChangeFeedProcessor.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.TraceLogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.GetCurrentClassLogger".

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.TraceLogProvider.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.CheckpointFrequency.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessorOptions.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.yml
:warning:Warning
View
Details

api/Microsoft.ServiceFabric.Services.Remoting.FabricTransport.Runtime.FabricTransportRemotingListenerSettings.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILogProvider.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.IChangeFeedProcessor.yml
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.TraceLogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.GetCurrentClassLogger".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.CheckpointFrequency.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.IPartitionCheckpointer".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.IPartitionCheckpointer".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessorOptions.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".
[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.ServiceFabric.Services.Remoting.FabricTransport.Runtime.FabricTransportRemotingListenerSettings.yml

[Warning] 1 invalid cross reference(s) "Microsoft.ServiceFabric.Services.Remoting.V2.ServiceRemotingRequestMessageHeader".
[Warning] 1 invalid cross reference(s) "Microsoft.ServiceFabric.Services.Remoting.V2.ServiceRemotingRequestMessageHeader".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.LogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILogProvider.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.Logging.ILog".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

api/Microsoft.Azure.Documents.ChangeFeedProcessor.PartitionManagement.IChangeFeedProcessor.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Documents.ChangeFeedProcessor.ChangeFeedProcessor".

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] System.AggregateException: One or more errors occurred. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.GitRepositoryInformationFileProvider.InitializeAsync()
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.GitContributorInformationResolverFactory.<GetResolverAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.CachedGitContributorInformationResolverFactory.<GetResolverAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<GetGitContributorInformationAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<>c__DisplayClass19_0.<<BuildNonReferenceAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<BuildNonReferenceAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetYamlDocumentGitContributorInformation.<BuildCoreAsync>d__5.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.CachedGitContributorInformationResolverFactory.Dispose() at Microsoft.DocAsCode.Build.Common.DisposableDocumentProcessor.Dispose() at Microsoft.DocAsCode.Build.Engine.SingleDocumentBuilder.Dispose() at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.BuildCore(DocumentBuildParameters parameter, IMarkdownServiceProvider markdownServiceProvider, BuildInfo currentBuildInfo, BuildInfo lastBuildInfo) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.Build(IList1 parameters, String outputDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()
---> (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.GitRepositoryInformationFileProvider.InitializeAsync()
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.GitContributorInformationResolverFactory.<GetResolverAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.CachedGitContributorInformationResolverFactory.<GetResolverAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<GetGitContributorInformationAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<>c__DisplayClass19_0.<<BuildNonReferenceAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetGitContributorInformation.<BuildNonReferenceAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.DocAsCode.EntityModel.Plugins.OpenPublishing.SetYamlDocumentGitContributorInformation.<BuildCoreAsync>d__5.MoveNext()<---

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:x: Validation status: errors

File
Status
Preview URL
Details

api/Microsoft.Azure.Management.ServiceFabric.Models.OperationResult.yml
:x:Error

Details

:x:Error

Details

TestingPullRequest.md
:warning:Warning

Details

api/Microsoft.Azure.Management.ServiceFabric.Models.OperationResult.yml

[Error] Publishing of document 'api/Microsoft.Azure.Management.ServiceFabric.Models.OperationResult.yml' to document hosting service failed with asset id: api/microsoft.azure.management.servicefabric.models.operationresult locale: en-us, depot name: MSDN.e2eprod-azuredotnet, branch name: pr-en-us-34. Error: The client could not finish the operation within specified timeout.

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report.

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Ignore metadata: content_type. They are generated by open publish.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit ec054f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit ec054f0:
:clock10: Pending: waiting for processors (40 builds ahead of you)
:warning: OPS Build is busy, click here to report any potential performance downgrade issues, or you could view OPS Portal for trend of build queue length.

OPS Build status updates of commit ec054f0:
:clock10: Preparing: average preparing time is 11 min(s) 10 sec(s)

OPS Build status updates of commit ec054f0:
:clock10: Full build: average full build time is not available, there is no data for this repository.

Note: A full build takes more time than an incremental build.  This is the expected behavior of the build system.

OPS Build status updates of commit ec054f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

  This is the expected behavior of the build system.

OPS Build status updates of commit ec054f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

  This is the expected behavior of the build system.

OPS Build status updates of commit ec054f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit 3061dba:
:clock10: Preparing: average preparing time is 11 min(s) 10 sec(s)

OPS Build status updates of commit 3061dba:
:clock10: Incremental building: average incremental building time is 20 min(s) 30 sec(s)

OPS Build status updates of commit 3061dba:
:clock10: Preparing: average preparing time is 11 min(s) 8 sec(s)

OPS Build status updates of commit 3061dba:
:clock10: Incremental building: average incremental building time is 19 min(s) 15 sec(s)

OPS Build status updates of commit 3061dba:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit 3e8d3d3:
:clock10: Preparing: average preparing time is 11 min(s) 4 sec(s)

OPS Build status updates of commit 3e8d3d3:
:clock10: Incremental building: average incremental building time is 18 min(s) 1 sec(s)

OPS Build status updates of commit 3e8d3d3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

api/Microsoft.Azure.NotificationHubs.NotificationDetails.yml
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

api/Microsoft.Azure.NotificationHubs.NotificationDetails.yml

[Warning] 2 invalid cross reference(s) "Microsoft.Azure.NotificationHubs.NotificationHubClient.SendNotificationImplAsync", "Microsoft.Azure.NotificationHubs.NotificationHubClient.SendScheduledNotificationImplAsync".

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

OPS Build status updates of commit 54c542e:
:clock10: Pending: waiting for processors (32 builds ahead of you)
:warning: OPS Build is busy, click here to report any potential performance downgrade issues, or you could view OPS Portal for trend of build queue length.

OPS Build status updates of commit 4511f0e:
:clock10: Pending: waiting for processors (32 builds ahead of you)
:warning: OPS Build is busy, click here to report any potential performance downgrade issues, or you could view OPS Portal for trend of build queue length.

OPS Build status updates of commit 54c542e:
:clock10: Preparing: average preparing time is 10 min(s) 59 sec(s)

OPS Build status updates of commit 54c542e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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

OPS Build status updates of commit 4511f0e:
:clock10: Preparing: average preparing time is 10 min(s) 58 sec(s)

OPS Build status updates of commit 4511f0e:
:clock10: Incremental building: average incremental building time is 17 min(s) 52 sec(s)

OPS Build status updates of commit 4511f0e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit a8fe742:
:clock10: Preparing: average preparing time is 10 min(s) 58 sec(s)

OPS Build status updates of commit a8fe742:
:clock10: Incremental building: average incremental building time is 17 min(s) 44 sec(s)

OPS Build status updates of commit a8fe742:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit a8fe742:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit a8fe742:
:clock10: Pending: waiting for processors (127 builds ahead of you)
:warning: OPS Build is busy, currently there are 127 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

OPS Build status updates of commit a8fe742:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

OPS Build status updates of commit dcacc49:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by OPS, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit 734a3f0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit 5d6bfe0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit 5d6bfe0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit 5d6bfe0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit 7341d00:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit f21facd:
:clock10: Full build: the average full build time is 100 min(s) 5 sec(s), this is based on the last 6 build(s) for this repository.

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

Docs Build status updates of commit f21facd:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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

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

File
Status
Preview URL
Details

TestingPullRequest.md
:warning:Warning
View
Details

TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 8: [Warning] Invalid file link:(~/../nonexisted1.md).
Line 9: [Warning] Invalid file link:(~/../nonexisted2.md).
Line 10: [Warning] Invalid file link:(~/../nonexisted3.md).

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


app.py错误

Using TensorFlow backend.
2019-11-03 09:56:06.046798: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-11-03 09:56:06.070035: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-11-03 09:56:06.070339: I tensorflow/compiler/xla/service/service.cc:150] XLA service 0x3f087b0 executing computations on platform Host. Devices:
2019-11-03 09:56:06.070367: I tensorflow/compiler/xla/service/service.cc:158]   StreamExecutor device (0): ,
Traceback (most recent call last):
File "app.py", line 54, in
from text.keras_detect import  text_detect
File "/home/luhui/chineseocr/text/keras_detect.py", line 24
box_score = box_layer([*textModel.output,image_shape,input_shape],anchors, num_classes)
^
SyntaxError: invalid syntax

python 2.7

python3 tools/pytorch_to_keras.py  -weights_path models/ocr-dense.pth -output_path models/ocr-dense-keras.h5
Using TensorFlow backend.
WARNING:tensorflow:From /usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/op_def_library.py:263: colocate_with (from tensorflow.python.framework.ops) is deprecated and will be removed in a future version.
Instructions for updating:
Colocations handled automatically by placer.
2019-11-04 10:34:56.130559: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-11-04 10:34:56.133757: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-11-04 10:34:56.134024: I tensorflow/compiler/xla/service/service.cc:150] XLA service 0x5f66eb0 executing computations on platform Host. Devices:
2019-11-04 10:34:56.134068: I tensorflow/compiler/xla/service/service.cc:158]   StreamExecutor device (0): ,

不支持python2.7


[Search] Change Azure.Search.Documents back to targeting preview version

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@pallavit I'll create a seperate PR for all the changes we did for GA.

@ShivangiReja looks like we made some breaking changes in the toolchain so it may be easier to try to overlay Octpreview release on top of GA rather than the other way round.

@pallavit - I've not added any breaking changes. Looks like all the PRs in the azure-sdk-for-net repository are currently failing.
Here are the links to the recent PRs for your reference:
https://github.com/Azure/azure-sdk-for-net/pull/40958
https://github.com/Azure/azure-sdk-for-net/pull/40957

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Search.Documents


Error during the registration of a CLR assembly in SQL Server 2017 which references other assembly

Hi, can anybody helps me to solve my problem:
https://stackoverflow.com/questions/63575895/error-during-the-registration-of-a-clr-assembly-in-sql-server-2017-which-referen

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

ID: a21d0936-6216-2251-6bdc-b1d7746c7039
Version Independent ID: cd19b31a-b56d-6958-a404-a5a04db7b4bc
Content: Deploying CLR Database Objects - SQL Server
Content Source: docs/relational-databases/clr-integration/deploying-clr-database-objects.md
Product: sql
Technology: clr
GitHub Login: @rothja
Microsoft Alias: jroth

@imranshams -- Imran, thank you for your question, and for your answer in that thread.
cc @rothja for awareness


Complete Rewrite + Fixes #6

I went to fix issue #6 and decided to rewrite the entire extension because the codebase was not very clean. Due to that fact I recommend verifying the extension works as it should and that all features are accounted for as I could have missed something in the rewrite.
The extension has been completely rewritten to improve code readability and reduce the amount of code running in each browser tab. This should improve performance and make development in the future much easier.
My comment in issue #6 has been fixed by requiring a netlify.toml file to exist in a repo before showing the Deploy button.
I think the repo's description should also be updated to the same one as in the manifest.json.

lol, very nice! no time to review right now but i'm inclined to accept this.

I have been noticing a couple of errors being throw in the console which should be looked at before a release has been made. I am currently quite busy as well but if a get a minute I will look into them.

Also once Netlify official releases support for netlify.yml and netlify.json updates will need to be made to support them but this should be really easy (currently they are part of the Build Plugins beta).

I have added support for netlify.yml and netlify.json even though they aren't fully supported officially. I also was not getting any extension errors while testing so I think my changes are ready to be merged although my testing was focused in Chrome, Firefox support should be verified again before being published.

I have fixed the errors, they are being caused by the extension attempting to modify a tab that doesn't exist.


Error after uploading an image on my server.

Hello! The installation was successful, and the page is loading. But when trying to upload a room image, I am getting this error. What should I do?
Thx!
> dev
> next dev

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
event - compiled client and server successfully in 3s (170 modules)
wait  - compiling...
event - compiled successfully in 175 ms (135 modules)
wait  - compiling /_error (client and server)...
event - compiled client and server successfully in 117 ms (171 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
wait  - compiling /dream (client and server)...
event - compiled client and server successfully in 1138 ms (963 modules)
wait  - compiling /...
event - compiled client and server successfully in 182 ms (246 modules)
wait  - compiling /dream (client and server)...
event - compiled client and server successfully in 293 ms (969 modules)
wait  - compiling /api/generate (client and server)...
event - compiled successfully in 49 ms (119 modules)
wait  - compiling /_error (client and server)...
error - pages/api/generate.ts (77:43) @ get
error - TypeError: Cannot read properties of undefined (reading 'get')
    at handler (webpack-internal:///(api)/./pages/api/generate.ts:53:46)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.apiResolver (/home/itmp9/roomGPT/node_modules/next/dist/server/api-utils/node.js:372:9)
    at async DevServer.runApi (/home/itmp9/roomGPT/node_modules/next/dist/server/next-server.js:488:9)
    at async Object.fn (/home/itmp9/roomGPT/node_modules/next/dist/server/next-server.js:751:37)
    at async Router.execute (/home/itmp9/roomGPT/node_modules/next/dist/server/router.js:253:36)
    at async DevServer.run (/home/itmp9/roomGPT/node_modules/next/dist/server/base-server.js:384:29)
    at async DevServer.run (/home/itmp9/roomGPT/node_modules/next/dist/server/dev/next-dev-server.js:743:20)
    at async DevServer.handleRequest (/home/itmp9/roomGPT/node_modules/next/dist/server/base-server.js:322:20) {
  page: '/api/generate'
}
  75 |   let jsonStartResponse = await startResponse.json();
  76 |
> 77 |   let endpointUrl = jsonStartResponse.urls.get;
     |                                           ^
  78 |   const originalImage = jsonStartResponse.input.image;
  79 |   const roomId = jsonStartResponse.id;
  80 |
event - compiled client and server successfully in 109 ms (977 modules)

Just run your dev instance like this
REPLICATE_API_KEY=$KEY npm run dev
Replace $KEY with your actual key.

You need to create a Replicate account, make a .env file and add it there. Make sure you follow all the steps in the README.
Closing this issue for now, feel free to re-open if you have follow up questions.


Link an instance to the service through the containing orchestration stack

The instance that is included in an orchestration stack was not directly linked to the provisioning service because the instance is not added to the service_resources.
The fix is to patch the Vm#service and Vm#direct_service methods to find the service through the containing stack.
https://bugzilla.redhat.com/show_bug.cgi?id=1387342
@gmcculloug please review.

looks great :+1:

@miq-bot add_label blocker

Darga BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1391710

Darga Backport details:
$ git log -1
commit 9a1ee1c6d4ecd2653e1ff81b994dcc20af339578
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Wed Nov 2 09:16:12 2016 -0400

    Merge pull request #12319 from bzwei/vm_service

    Link an instance to the service through the containing orchestration stack
    (cherry picked from commit d911435a0a5618c0def426846acba020bfcf58bc)

    https://bugzilla.redhat.com/show_bug.cgi?id=1391710

Euwe BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1391709

Euwe Backport details:
$ git log -1
commit e2934b1a1964544a9e7f2a3f374a4c0d151d9a3d
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Wed Nov 2 09:16:12 2016 -0400

    Merge pull request #12319 from bzwei/vm_service

    Link an instance to the service through the containing orchestration stack
    (cherry picked from commit d911435a0a5618c0def426846acba020bfcf58bc)

    https://bugzilla.redhat.com/show_bug.cgi?id=1391709


[Proposal]: Actor State TTL

In what area(s)?

/area runtime
(I've used the Go SDK in the below examples).
Currently, there is no way for actor state to be deleted automatically after a period of time. This means that the amount of data that can be written to the store over time is unbounded. The state store will eventually fill up unless users implement clean up logic, out of band of dapr.
I propose that we extend the dapr SDKs to implement a function:
func SetFor(ctx context.Context, stateName string, value any, duration time.Duration)

Before writing to the state store, this function would create an actor reminder for the given type, with a reminder name following the schema (suggestions very welcome!):
io.dapr.setFor.<stateName>
The SDK will implement a middleware to the existing reminder handler which looks for this well known schema. Upon invocation with a reminder name following the schema, the middleware will delete the relevant state and then delete the reminder. The middleware will prevent ReminderCall from being invoked.
Dapr will recommend users to always use SetFor with some appropriate duration (e.g. 2 weeks) to ensure state is always cleaned up, unless they already have state management in place.
This method is only best effort since an application may no longer implement that type when a reminder is invoked.

We could implement this logic in the dapr runtime and save some hops, however this would require dapr API changes.

Note: schema definition pending- we should make it clear in the documentation that dapr reserves the "io.dapr." namespace and cannot be used by users. This should be added to docs, and added as validation to the SDKs.

Here is a poc implementation for the go-sdk. It still needs tests.

I've been thinking about this issue since you mentioned it, @cgillum
Some food for thought:

I think the first thing that we should do is document the need to perform cleanups as needed as a best practice. Right now our docs don't make a great job at explaining the lifecycle of the persistent state stored by actors, and we should explain how it's persisted and recommend developers to create their own reminders to invoke a "Dispose" method as they see fit. This also allows developers to have the ability to "push back" a deadline.

For example, imagine an actor that's used to persist a user session (something I've recently worked on, although this was on a different implementation of the "virtual actors" model and not Dapr actors). You want to delete the session after X minutes of inactivity. The developer would want to create a "Dispose" method, and every time the session is accessed, the reminder to invoke that is re-set to X minutes in the future.

As for something that's specific for each state item... Because there seems to be a fairly good (although not (yet) complete) overlap between state stores that can be used for actors, and state stores that support TTLs, could we rely on the "native" TTLs rather than building reminders on top? Then, the method SetFor (or SetWithTTL to be more consistent with how we name these things in Dapr) could just set the ttl metadata in the call to the state store.

Pros: much simpler to implement (need only to create a new method which adds the ttl property in the metadata), doesn't require us to manage new virtual actors, and doesn't suffer from this issue: "This method is only best effort since an application may no longer implement that type when a reminder is invoked."
Cons: currently not all state stores that can be used to store actors state support TTLs, but there's an open issue to add that. In the meanwhile, we could just return an error if the Features() method doesn't include TTLs.

+1 for documenting best practices.
As for TTLs, I do worry about the fact that not all actor-compliant state stores support them. But even if they did, I also worry about the fact that an actor can manage state across multiple keys, begging the questions:

Would we need to put separate TTLs on all the keys?
Assuming yes to the above, could this result in race conditions where actor invocations race with data cleanup?

I wonder if it would be safer to make state cleanup a first-class feature of the actor runtime. For example, suppose we have a design where actors can delete themselves by scheduling a "deleteme" reminder. The handler for this reminder can be intercepted by the sidecar and doesn't even need to have an implementation in any SDK. Using a reminder ensures that we're not introducing concurrency issues, and we can delete all the keys while holding that lock.
Thoughts?

As for TTLs, I do worry about the fact that not all actor-compliant state stores support them.

Currently (Dapr 1.10) we have 11 state stores that can be used for Actor state storage. Of those, 4 do not support TTLs:

MongoDB: the DB actually does have native TTL support, we just need to enable that in Dapr
3 RDBMS: CockroachDB, MySQL, Azure SQL. For these, we can implement TTLs like we did in Postgres and SQLite (and were already implemented in Oracle), as described in dapr/components-contrib#2288

Although implementing TTLs in these state stores may be some more work than performing garbage collection with a reminder, I think it is a more reliable approach and the ROI of that will be larger as the TTLs can be used outside of Actors too.

But even if they did, I also worry about the fact that an actor can manage state across multiple keys, begging the questions:

Would we need to put separate TTLs on all the keys?
Assuming yes to the above, could this result in race conditions where actor invocations race with data cleanup?

The original proposal was to have each key with its own TTL, and I think there's value in that for reasons of flexibility. However I don't think it should prevent us from offering a bulk "deleteme" (more on that below).
There could be race conditions, yes, but they're not a problem with Dapr, rather it's the responsibility of the developers to handle those situations IMHO.

Have a design where actors can delete themselves by scheduling a "deleteme" reminder. The handler for this reminder can be intercepted by the sidecar and doesn't even need to have an implementation in any SDK.

+1 for a "deleteme" API. But I don't think this needs to be a reminder.
Instead, it could just be a "bulk delete" of all given keys. Ideally we'd be able to delete all keys from the state store that match a prefix, but that's not yet possible with our state store APIs (and implementation in some cases may be challenging, like Cosmos DB).

Thanks both for the insights!
Given the resource implications of using reminders it also makes sense to me that we should be using the existing TTL API. I agree we should spend the time to have this feature implemented for the remaining store types.

/assign


reload panel without clicking button

hey there @bnomei 🍡
quick question.. is there any way with your plugin to trigger a panel reload without clicking a janitor button? i mean adding a command with the reload => true option, but then running the command in a hook? i am pretty sure it’s not possible because of server/client-side but just wanted to make sure. or maybe you know another way.
my use-case is pretty simple. after saving a user, i would like to update their content. this of course works fine with the user.update:after hook. but as the changes are only visible after a reload, it’s not really usable.
sorry if this is slightly off-topic here.
thank you for your time!
🙏🏻 ✨

thank you so much for the quick feedback!
if you don’t mind.. i am trying to understand what you said, but i don’t get it entirely. creating the .refresh file is clear. and having a custom hidden field in the user blueprint too. but then how does this field trigger a custom api, client-side?
🌳 🌿

you would need to create a custom field (the hidden one) that calls your custom api in an interval. like this one does (but it will update its content instead of refreshing the page - but i guess you get the gist.)
https://github.com/bnomei/kirby3-recently-modified/blob/07faedc21914546e5d59968ffaf25db01dc1d220/src/components/fields/RecentlyModified.vue#L30


Request caldav

Good morning !
unfortunately I can't find a way to contact you personally.
Do you have another project, to work with a caldav server?

connect to server
get events
create / delete / modify events

Or can you support me with this topic?
Thanks a lot !!

Hello, no I have no caldav related projects and no intention to create one. You should be able to find libs for caldav.


How can I debug LDAP authentication

Question:
Hi,
I'm trying out LDAP authentication.
In the LDAP Configuration I've entered :

LDAP server
Anonymous mode: false
Reader DN
Password: ****
Connectivity check: successful
No LDAP security
Automatic user provisioning: true

The user search configuration has Base DN, Username attribute and Filter taken from another service running on the same network that is know to work.
Group search configuration is left empty.
No matter what parameters I enter I get:
Failure
User not found or too many entries returned

Where can I get more detailed logs?

Note username attribute is case sensitive, for AD this could be sAMAccountName

Hi @lfdmn ,
If u want more detailed log You can look in the Portainer logs, look at the response of the network request to see the error thrown by the LDAP server,  and look at the logs of the LDAP server

If I type in a wrong password for reader DN the Connectivity check fails as expected.
The user search configuration looks like this:

Base DN: OU=Users,OU=Domain Ltd,DC=domain,DC=ltd
User attribute: sAMAccountName
Filter: (&(objectCategory=person)(objectClass=user)(|(sAMAccountName=%[1]s)(mail=%[1]s)))

If I leave the filter empty I can connect, but not with it. Same with (&(objectCategory=person)(objectClass=user)(|(sAMAccountName={0})(mail={0})))
See any typos there?


Move to GitHub Pages

Move away from Netlify and to GitHub pages, where we deploy via github actions on a dedicated branch, perhaps gh-pages branch.
/cc @marbar3778 @helder-moreira

always good.  Also allows others to fork and see results in real-time more easily.


add error related to memory usage and zoom

Add check for misconfigured maps so that
accidental misconfiguration can be caught
at development test time rather than
at run time.

relates to issue #48


Missing device configuration: Philio Technology Corp / Z-WAVE Remote PH-PSR03

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

Which device is missing?
Philio Technology Corp / Z-WAVE Remote PH-PSR03
Manufacturer ID
0x013c
Product Type
0x0008
Product ID
0x0027
Firmware Version
1.13
Is the device listed on the Z-Wave Alliance website?
https://products.z-wavealliance.org/products/1407?selectedFrequencyId=1
Do you have a manual?
https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/1407/PSR03_ABC_version_Manual.pdf
I have paired a Philio PSR03 remote with zwavejs2mqtt and it included fine.
However it shows as unknown for both manufacturer and model.
The link on the device configuration page points here, where the device is not found in the database.
https://devices.zwave-js.io/?jumpTo=0x013c:0x0008:0x0027:1.13
However, I believe this is the entry for it?
https://devices.zwave-js.io/?jumpTo=0x013c:0x0008:0x001d:0.0
Under device info, Home Assistant shows ...
Firmware: 1.13
Z-Wave Info
Source: Z-Wave JS
Device ID: 80
Device Status: Asleep
Device Ready: Yes
Highest Security: None
Z-Wave Plus: Version 1
There are three entities created for this remote.
(The remote has a single button marked "PANIC", nothing else)
sensor.annex_panic_button_battery_level
binary_sensor.annex_panic_button_low_battery_level
sensor.annex_panic_button_node_status
I've included my node dump.
node_80.txt
Thanks for your help!

@zwave-js-bot import config 1407 from zwa

Awesome sauce - thank you very much! 🍺


Should ... be supported in structure-valued expressions?

It seems like a fairly small and useful generalization of the current language spec to explicitly allow , ... inside of a structure-valued expression (only at the end, just before the closing }).  This proposal is that would be supported in structure-valued expressions, which can appear anywhere that an R-value is needed with a struct or header type.
A strict reading of the current language spec in https://p4.org/p4-spec/docs/P4-16-v1.2.2.html#sec-initializing-with-default-values only allows ... in initialization expressions, seems to imply in spec version 1.2.2 that ... is only allowed in initializations.

This PR is for review if people believe the answer to the question raised by this issue should be "yes": https://github.com/p4lang/p4-spec/pull/1031

This is not an easy topic. We just merged a very complex PR in the compiler which deals with such cases, often by generating errors. Consider an expression like { a = 2, ... } == { b = 3, ... }. This has an infinite number of solutions.

Let me just provide some context here. Besides the variables that we explicitly instantiate inside parsers or controls, we also have parameters, such as hdr and meta structs. The latter almost always requires explicit initialization and, in fact, that's precisely what prompted the initial requests, because in the real data plane programs, this struct can be huge.
If we just allow these constructs as initializers, then this important case will not be covered.

In a case like {a=2, ...} == {b=3, ...}, it seems reasonable to make that an error since there is no way for the compiler to determine what the type of the two structure-valued expressions should be.
If the compiler just said "These structure-valued expressions must have a (typeRef) prefix to specify their type", does that make the resulting semantics more straightforward?  And is it perhaps straightforward to determine when that proposed error message can be issued?  It seems to me quite reasonable if the compiler gives up if it isn't "obvious" what the types should be.

The point I am trying to make is that we have to be careful what we put in the spec.
I have also tried to implement support for something like {a = 2} == {a = 2}, and even this is tricky, because you cannot just generate an associated struct type for these expressions, since structs cannot have int fields.

But yes, if the type is specified explicitly things are simpler.

By the way, this is the point I made at the LDWG yesterday. Some of the options we are considering, like this one, do not specify the type of the value. And that can make things more complicated.
My comment was dismissed with a response that the compiler already handles this in type inference.
I do agree we can separate type inference from the semantics of fully-typed terms. And that's a good principle to follow. But type inference gets very tricky. And even if we settle on a conservative inference scheme, I worry the result will be unintuitive for programmers -- relatively small changes to the programs can cause the type checker to flip from accepting to rejecting a program, or vice versa.

Personally, I am perfectly fine if every structure-valued expression must be preceded by an explicit (typeRef), by the way.  Someone else wrote the text in the current language spec that makes those optional.