[BUG][DocumentIntelligence] Not able to set features on the AnalyzeDocumentOptions

Library name and version
[Azure.AI.DocumentIntelligence1.0.0]
Describe the bug
Hi All,
I'm not able to set the features i want, the property has only a get, new code:
DocumentIntelligenceClient client = new DocumentIntelligenceClient(new Uri(Endpoint), credential);

List<DocumentAnalysisFeature> features = new List<DocumentAnalysisFeature>();
var keyValuePairFeature = new DocumentAnalysisFeature("KeyValuePairs");
features.Add(keyValuePairFeature);

AnalyzeDocumentOptions analyzeDocumentOptions = new AnalyzeDocumentOptions("prebuilt-invoice", BinaryData.FromBytes(file))
{
				Pages = "1-3",
				Features = "error when trying to set this"
};

var operation = client.AnalyzeDocument(WaitUntil.Completed, analyzeDocumentOptions);

The overload on the AnalyzeDocument method call has a features parameter, but than i can't pass the options with the binaryData anymore compared to the code on the 1.0.0.beta3 package:
DocumentIntelligenceClient client = new DocumentIntelligenceClient(new Uri(Endpoint), credential);

AnalyzeDocumentContent analyzeDocumentContent = new AnalyzeDocumentContent();
analyzeDocumentContent.Base64Source = BinaryData.FromBytes(file);

List<DocumentAnalysisFeature> features = new List<DocumentAnalysisFeature>();
var keyValuePairFeature = new DocumentAnalysisFeature("KeyValuePairs");
features.Add(keyValuePairFeature);

var operation = client.AnalyzeDocument(WaitUntil.Completed, "prebuilt-invoice", analyzeDocumentContent, pages: "1-3", features: features);

Expected behavior
Be able to set the features or get another option that works.
Actual behavior
Build error when trying to set the features
Reproduction Steps
See code above
Environment
Latest Visual Studio running on .net 6, .net8 and net framework 4.8

Ticket can be closed, found the way to set this. Perhaps a good idea to put it in the documentation.
DocumentIntelligenceClient client = new DocumentIntelligenceClient(new Uri(Endpoint), credential);

AnalyzeDocumentOptions analyzeDocumentOptions = new AnalyzeDocumentOptions("prebuilt-invoice", BinaryData.FromBytes(file))
{
	Pages = "1-3",
        Features = { DocumentAnalysisFeature.KeyValuePairs }
};

var operation = client.AnalyzeDocument(WaitUntil.Completed, analyzeDocumentOptions);

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

The usage of features is illustrated in our samples: Key-value pairs extraction.
To check other common scenarios, see our samples README.


⚠ Bofrost.be has degraded performance

In bf6e187, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1290 ms

Resolved: Bofrost.be performance has improved in 6809234 after 1 hour, 2 minutes.


Some crashes

Seems to be related to the x11 window changes yesterday.
All crashes happend when dealing with an x11 window, regaining focus after another fullscreen window closed or something like that.
Here is a crash report and a coredump, not totally shure that they are from the same crash though.
hyprlandCrashReport117259.txt
core.txt
By the way if you want to make it a bit easier to send these crash reports, give them an file extension than github doesn't refuse.

patch.txt
try this patch

should be fixed with ea717731a41be907e9bfaa2c41a3f145452c7767. plox reopen if not

Actually fixed in https://github.com/hyprwm/Hyprland/commit/71496a0a3c31d9e0b7ce55a21713304fc23a46cd

No crash report was created this time:
dump.txt

That doesn't say much. Please make sure you're on the latest commit by verifying hyprctl version matches with the git head

@vaxerski I think we can close that

probably


Exception even when launching NiftyMIC commands without input

Hi there,
I get the following errors even when launching simply (for instance) niftymic_reconstruct_volume:
niftymic_reconstruct_volume_from_slices
itkStreamingProcessObject not found in module ITKCommon because of exception:
'module' object has no attribute 'itkStreamingProcessObject'
itkMultiThreaderBase not found in module ITKCommon because of exception:
'module' object has no attribute 'itkMultiThreaderBase'
itkPoolMultiThreader not found in module ITKCommon because of exception:
'module' object has no attribute 'itkPoolMultiThreader'
itkPlatformMultiThreader not found in module ITKCommon because of exception:
'module' object has no attribute 'itkPlatformMultiThreader'
itkVectorContainerULSS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkVectorContainerULSS'
vectoritkImageRGBUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageRGBUC2'
vectoritkImageRGBAUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageRGBAUC2'
vectoritkImageVF22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF22'
vectoritkImageVF32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF32'
vectoritkImageVF42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF42'
vectoritkImageCVF22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF22'
vectoritkImageCVF32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF32'
vectoritkImageCVF42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF42'
vectoritkImageSS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageSS2'
vectoritkImageUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUC2'
vectoritkImageUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUS2'
vectoritkImageF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageF2'
vectoritkImageCF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCF2'
vectoritkImageVD22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD22'
vectoritkImageVD32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD32'
vectoritkImageVD42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD42'
vectoritkImageD2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageD2'
vectoritkImageUL2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUL2'
vectoritkImageULL2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageULL2'
vectoritkImageB2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageB2'
vectoritkImageFAF22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageFAF22'
vectoritkImageO22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageO22'
vectoritkImageSSRTD22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageSSRTD22'
vectoritkImageRGBUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageRGBUC3'
vectoritkImageRGBAUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageRGBAUC3'
vectoritkImageVF23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF23'
vectoritkImageVF33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF33'
vectoritkImageVF43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF43'
vectoritkImageCVF23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF23'
vectoritkImageCVF33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF33'
vectoritkImageCVF43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVF43'
vectoritkImageSS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageSS3'
vectoritkImageUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUC3'
vectoritkImageUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUS3'
vectoritkImageF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageF3'
vectoritkImageCF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCF3'
vectoritkImageVD23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD23'
vectoritkImageVD33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD33'
vectoritkImageVD43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD43'
vectoritkImageD3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageD3'
vectoritkImageUL3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageUL3'
vectoritkImageULL3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageULL3'
vectoritkImageB3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageB3'
vectoritkImageFAF33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageFAF33'
vectoritkImageO33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageO33'
vectoritkImageSSRTD33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageSSRTD33'
vectoritkImageVF12 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF12'
vectoritkImageVD24 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD24'
vectoritkImageVD34 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD34'
vectoritkImageVD44 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVD44'
vectoritkImageVF13 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageVF13'
vectoritkImageCVD22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD22'
vectoritkImageCVD32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD32'
vectoritkImageCVD42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD42'
vectoritkImageCVD23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD23'
vectoritkImageCVD33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD33'
vectoritkImageCVD43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'vectoritkImageCVD43'
itkImageToImageFilterISS2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterISS2ICF2'
itkImageToImageFilterISS3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterISS3ICF3'
itkImageToImageFilterIUC2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterIUC2ICF2'
itkImageToImageFilterIUC3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterIUC3ICF3'
itkImageToImageFilterIUS2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterIUS2ICF2'
itkImageToImageFilterIUS3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterIUS3ICF3'
itkImageToImageFilterICF2ISS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF2ISS2'
itkImageToImageFilterICF3ISS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF3ISS3'
itkImageToImageFilterICF2IUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF2IUC2'
itkImageToImageFilterICF3IUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF3IUC3'
itkImageToImageFilterICF2IUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF2IUS2'
itkImageToImageFilterICF3IUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterICF3IUS3'
itkImageToImageFilterISSRTD22ISSRTD22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterISSRTD22ISSRTD22'
itkImageToImageFilterISSRTD33ISSRTD33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageToImageFilterISSRTD33ISSRTD33'
itkInPlaceImageFilterIRGBUC2ISS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC2ISS2'
itkInPlaceImageFilterIRGBUC3ISS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC3ISS3'
itkInPlaceImageFilterIRGBUC2IUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC2IUS2'
itkInPlaceImageFilterIRGBUC3IUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC3IUS3'
itkInPlaceImageFilterIRGBUC2IF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC2IF2'
itkInPlaceImageFilterIRGBUC3IF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIRGBUC3IF3'
itkInPlaceImageFilterISS2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterISS2ICF2'
itkInPlaceImageFilterISS3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterISS3ICF3'
itkInPlaceImageFilterIUC2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIUC2ICF2'
itkInPlaceImageFilterIUC3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIUC3ICF3'
itkInPlaceImageFilterIUS2ICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIUS2ICF2'
itkInPlaceImageFilterIUS3ICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterIUS3ICF3'
itkInPlaceImageFilterICF2ISS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF2ISS2'
itkInPlaceImageFilterICF3ISS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF3ISS3'
itkInPlaceImageFilterICF2IUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF2IUC2'
itkInPlaceImageFilterICF3IUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF3IUC3'
itkInPlaceImageFilterICF2IUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF2IUS2'
itkInPlaceImageFilterICF3IUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkInPlaceImageFilterICF3IUS3'
itkDefaultDynamicMeshTraitsSS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS2'
itkDefaultDynamicMeshTraitsSS22SSSS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS22SSSS'
itkDefaultDynamicMeshTraitsSS22SSSSSS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS22SSSSSS'
itkDefaultDynamicMeshTraitsUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC2'
itkDefaultDynamicMeshTraitsUC22UCUC not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC22UCUC'
itkDefaultDynamicMeshTraitsUC22UCUCUC not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC22UCUCUC'
itkDefaultDynamicMeshTraitsUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS2'
itkDefaultDynamicMeshTraitsUS22USUS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS22USUS'
itkDefaultDynamicMeshTraitsUS22USUSUS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS22USUSUS'
itkDefaultDynamicMeshTraitsF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsF2'
itkDefaultDynamicMeshTraitsD2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsD2'
itkDefaultDynamicMeshTraitsSS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS3'
itkDefaultDynamicMeshTraitsSS33SSSS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS33SSSS'
itkDefaultDynamicMeshTraitsSS33SSSSSS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsSS33SSSSSS'
itkDefaultDynamicMeshTraitsUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC3'
itkDefaultDynamicMeshTraitsUC33UCUC not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC33UCUC'
itkDefaultDynamicMeshTraitsUC33UCUCUC not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUC33UCUCUC'
itkDefaultDynamicMeshTraitsUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS3'
itkDefaultDynamicMeshTraitsUS33USUS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS33USUS'
itkDefaultDynamicMeshTraitsUS33USUSUS not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsUS33USUSUS'
itkDefaultDynamicMeshTraitsF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsF3'
itkDefaultDynamicMeshTraitsD3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultDynamicMeshTraitsD3'
itkDefaultStaticMeshTraitsSS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsSS2'
itkDefaultStaticMeshTraitsUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsUC2'
itkDefaultStaticMeshTraitsUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsUS2'
itkDefaultStaticMeshTraitsF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsF2'
itkDefaultStaticMeshTraitsD2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsD2'
itkDefaultStaticMeshTraitsSS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsSS3'
itkDefaultStaticMeshTraitsUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsUC3'
itkDefaultStaticMeshTraitsUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsUS3'
itkDefaultStaticMeshTraitsF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsF3'
itkDefaultStaticMeshTraitsD3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkDefaultStaticMeshTraitsD3'
itkImageDuplicatorISSRTD22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageDuplicatorISSRTD22'
itkImageDuplicatorISSRTD33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageDuplicatorISSRTD33'
itkImageSinkIRGBUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIRGBUC2'
itkImageSinkIRGBUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIRGBUC3'
itkImageSinkIRGBAUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIRGBAUC2'
itkImageSinkIRGBAUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIRGBAUC3'
itkImageSinkIVF22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF22'
itkImageSinkIVF23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF23'
itkImageSinkIVF32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF32'
itkImageSinkIVF33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF33'
itkImageSinkIVF42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF42'
itkImageSinkIVF43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIVF43'
itkImageSinkICVF22 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF22'
itkImageSinkICVF23 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF23'
itkImageSinkICVF32 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF32'
itkImageSinkICVF33 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF33'
itkImageSinkICVF42 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF42'
itkImageSinkICVF43 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICVF43'
itkImageSinkISS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkISS2'
itkImageSinkISS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkISS3'
itkImageSinkIUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIUC2'
itkImageSinkIUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIUC3'
itkImageSinkIUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIUS2'
itkImageSinkIUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIUS3'
itkImageSinkIF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIF2'
itkImageSinkIF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkIF3'
itkImageSinkICF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICF2'
itkImageSinkICF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkICF3'
itkImageSinkVISS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVISS2'
itkImageSinkVIUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIUC2'
itkImageSinkVIUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIUS2'
itkImageSinkVIF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIF2'
itkImageSinkVISS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVISS3'
itkImageSinkVIUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIUC3'
itkImageSinkVIUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIUS3'
itkImageSinkVIF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkImageSinkVIF3'
itkNumericTraitsCF not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkNumericTraitsCF'
itkPointSetSS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetSS2'
itkPointSetUC2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetUC2'
itkPointSetUS2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetUS2'
itkPointSetF2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetF2'
itkPointSetD2 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetD2'
itkPointSetSS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetSS3'
itkPointSetUC3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetUC3'
itkPointSetUS3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetUS3'
itkPointSetF3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetF3'
itkPointSetD3 not loaded from module ITKCommon because of exception:
'module' object has no attribute 'itkPointSetD3'
Traceback (most recent call last):
File "/usr/local/bin/niftymic_reconstruct_volume_from_slices", line 11, in
load_entry_point('NiftyMIC', 'console_scripts', 'niftymic_reconstruct_volume_from_slices')()
File "/home/zappst/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 489, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/home/zappst/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2852, in load_entry_point
return ep.load()
File "/home/zappst/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2443, in load
return self.resolve()
File "/home/zappst/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2449, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/home/zappst/NiftyMIC-master/niftymic/application/reconstruct_volume_from_slices.py", line 21, in
import niftymic.reconstruction.admm_solver as admm
File "/home/zappst/NiftyMIC-master/niftymic/reconstruction/admm_solver.py", line 19, in
from niftymic.reconstruction.solver import Solver
File "/home/zappst/NiftyMIC-master/niftymic/reconstruction/solver.py", line 21, in
import niftymic.reconstruction.linear_operators as lin_op
File "/home/zappst/NiftyMIC-master/niftymic/reconstruction/linear_operators.py", line 26, in
class LinearOperators(object):
File "/home/zappst/NiftyMIC-master/niftymic/reconstruction/linear_operators.py", line 48, in LinearOperators
image_type=itk.Image.D3,
File "/home/zappst/.local/lib/python2.7/site-packages/itkLazy.py", line 52, in getattribute
itkBase.LoadModule(module, namespace)
File "/home/zappst/.local/lib/python2.7/site-packages/itkBase.py", line 214, in LoadModule
namespace[snakeCaseFunction] = getattr(module, snakeCaseFunction)
AttributeError: 'module' object has no attribute 'image_to_image_filter'
I tried to reinstall it. All requirements are met and all prerequisites from the GitHub website.
I was wondering what else I can try.
Many thanks,
Stefano.

Looks like ITK was not properly installed. Can you confirm you went through the steps as outlined in the specific ITK_NiftyMIC Installation Wiki and its inclusion within python works? See the associated Usage for more details.

Hi Michael,
Thank you for the prompt response.
Yes, I did, without though cleaning folders and path.
I was wondering, what would be the best way to uninstall ITK_NiftyMIC in a clean way to try to install it brand new?

You can just remove the build folder. Just make sure you have plenty of coffee next to you; building it from source will take a while ...

Hi Michael,
Thank you for your help so far.
I have installed ITK_NiftyMIC from scratch. Unfortunately, I still have the same problem.
When I execute:

import itk
print(itk.Image.D3.New())

then the same error as before is thrown. Interestingly, if I run > print(itk.Image.D3.New()) again, the command seems to work. Then the problem is with the following command > print(itk.OrientedGaussianInterpolateImageFilter.ID3ID3.New()).
It seems like it is caused by an improper installation of itk_NiftyMIC or a broken pointer from python to the itk_NiftyMIC.
Any suggestion on what to try next would be more than appreciated.
Many thanks,
Stefano.

Hi,
Can you please confirm that:

no itk python libraries are installed in the first place prior to your installation (e.g. via pip install itk). I'd indeed recommend using a fresh virtual machine for installing NiftyMIC.
ITK_NiftyMIC is installed as described. It's indeed important to use this repo since standard ITK does not come with OrientedGaussianInterpolateImageFilter (and others we added)
the compilation and inking steps were completed successfully.

Once the compilation of ITK_NiftyMIC was done successfully (which is the most elaborate step of the installation) then all subsequent steps should be rather straightforward.

Dear Michael,
Thank you for your prompt support.
The problem was given by a different version of ITK installed in the machine and then by an old version of python (2.7 I believe).
Using a virtual environment (very straightforward guide: https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/) and installing everything with pip3 fixed the problems.
I imagine now I have to activate the python virtual environment every time I need to run NiftyMIC?
Again, thank you for your support.
Cheers,
Stefano.


MySQL extension is also available for v0.9.2

And prefer to use mysql over mysql_scanner as the extension name

Great, thanks!


Add System.Threading.Lock

This lock class is not hardened against thread aborts coming from framework versions preceding .NET 5.0.
Consider using Backport.System.Threading.Lock instead of this method for locking, because it allows you to use the methods that the System.Threading.Lock class provides.

@MarkCiliaVincenti can you please elaborate on what you mean? I don't see substantial difference between this implementation and https://github.com/MarkCiliaVincenti/Backport.System.Threading.Lock/blob/c28041f1e22e561d5cde040704abeeb8d9a18649/Backport.System.Threading.Lock/Lock.cs#L15-L114

You're looking at the wrong file. Look at PreNet5Lock.cs and LockFactory.cs.
In fact I made that file you linked only available to net5 and upwards so if someone is on something lower they would not be able to use it.

You're looking at the wrong file. Look at PreNet5Lock.cs and LockFactory.cs.
In fact I made that file you linked only available to net5 and upwards so if someone is on something lower they would not be able to use it.

I see now. I assume you're mainly referring to this part, right?
https://github.com/MarkCiliaVincenti/Backport.System.Threading.Lock/blob/c28041f1e22e561d5cde040704abeeb8d9a18649/Backport.System.Threading.Lock/PreNet5Lock.cs#L114-L124

No it's mainly the normal use case actually, locking on the object itself that is unsafe against thread aborts. It's why I needed the factory, so on frameworks before net9 they're given a return object that's on a different namespace.

You could've had them most in the same namespace though, right? Since these two types never appear at the same time.

The proper backport/polyfill is the one like yours. It's neat and all. Alas, evil thread aborts exists and these are locks we're talking about. Correctness is key in a library, but especially for locks because there exists a race condition of sorts whereby the lock of an aborted thread remains locked and no other threads can obtain the lock.

Yeah that's fair. I'll update the code on .NET FX to include the try/catch you have in your implementation and credit you in the comments. Thanks for the feedback!

Cool, but are you going to change the namespace? If you call it System.Threading.Lock, then you will still have problems.

Which problems are you referring to?

The main problem you have @Tyrrrz is that with your current code:
private static readonly object _syncLock = new();

...

lock (_syncLock)
{
   doThis();
}

does not have the same behaviour as this on versions of .NET before .NET 5.0:
private static readonly System.Threading.Lock _syncLock = new(); // this is from your polyfill

...

lock (_syncLock)
{
   doThis();
}

The object one gets lowered to this:
bool lockTaken = false;
try
{
  Monitor.Enter(syncObject, ref lockTaken);
  doThis();
}
finally
{
  if (lockTaken)
  {
    Monitor.Exit(syncObject);
  }
}

but the polyfilled one because it uses the System.Threading.Lock namespace that's 'reserved' will get lowered to different code. Something like this:
System.Threading.Lock.Scope scope = syncObject.EnterScope();
try
{
  doThis();
}
finally
{
  scope.Dispose();
}

In the above code, if the thread is aborted before it enters the try, i.e. right after obtaining the lock, it will never go into that finally and dispose cleanly, which means that it retains the lock and other threads would be unable to enter the lock as it would be left permanently locked for the lifetime of that lock instance.

But syncObject.EnterScope() already does Monitor.Enter(syncObject, ref lockTaken) as that's what it's meant to do in the polyfilled implementation.

I think the idea is to make the rudimentary lock work exactly like locking on an object would work pre net9. So yes it might work (though do check), but it still feels wrong. What if the lowering changes?

@Tyrrrz I confirmed it does call the EnterScope. Unfortunately when code gets lowered this way on < .NET 5.0, if the thread is aborted after the EnterScope and before entering the try, it will fail to dispose. This is not the case if you use a different namespace as I did in PreNet5Lock.cs. In a nutshell, you are still not hardened against thread aborts. Nothing using EnterScope is. This is why I had added this warning on the EnterScope method:
[Obsolete("This method is a best-effort at hardening against thread aborts, but can theoretically retain lock on pre-.NET 5.0. Use with caution.")]

There's also another issue. If you create a .NET 8.0 library (let's call it 'ABC') that depends on this project, and then create a new .NET 9.0 project (let's call it 'DEF') that depends on 'ABC', you would get an error because DEF will get the .NET 9.0 version of your library (that would lack the System.Threading.Lock) and the library 'ABC' can't find the class it's meant to use.
My library solves this problem, because it is standalone targeting just System.Threading.Lock. It also solves the problem of thread aborts using a factory method.
Would you be willing to add a dependency to this micro-library?

I think the idea is to make the rudimentary lock work exactly like locking on an object would work pre net9. So yes it might work (though do check), but it still feels wrong. What if the lowering changes?

Whichever way the lowering changes, it would still have to call EnterScope(...), does it not?

@Tyrrrz I confirmed it does call the EnterScope. Unfortunately when code gets lowered this way on < .NET 5.0, if the thread is aborted after the EnterScope and before entering the try, it will fail to dispose. This is not the case if you use a different namespace as I did in PreNet5Lock.cs. In a nutshell, you are still not hardened against thread aborts. Nothing using EnterScope is. This is why I had added this warning on the EnterScope method:
[Obsolete("This method is a best-effort at hardening against thread aborts, but can theoretically retain lock on pre-.NET 5.0. Use with caution.")]

Well, if the execution gets inside EnterScope) then this part that you wrote will take care of it:
https://github.com/Tyrrrz/PolyShim/blob/e56ec5ff0be4eb65d489301b5cfb1430aa5bb701/PolyShim/Net90/Lock.cs#L50-L56
It doesn't need Dispose() to be called.
Also, I cannot provide this type under a different namespace due to the nature of this project -- it contains polyfills which replace native types on frameworks that don't have them. Using the same namespace is imperative.

There's also another issue. If you create a .NET 8.0 library (let's call it 'ABC') that depends on this project, and then create a new .NET 9.0 project (let's call it 'DEF') that depends on 'ABC', you would get an error because DEF will get the .NET 9.0 version of your library (that would lack the System.Threading.Lock) and the library 'ABC' can't find the class it's meant to use.
My library solves this problem, because it is standalone targeting just System.Threading.Lock. It also solves the problem of thread aborts using a factory method.
Would you be willing to add a dependency to this micro-library?

That would not happen because this library is not compiled. The polyfills are included as source code files and every single type provided is internal, so there aren't going to be any conflicts.

If the thread is aborted after the EnterScope and before the try, which is absolutely possible, then the code as is will still retain the lock. The two processes are not atomic.

The thread is aborted after the EnterScope() but before the try then the lock will not be acquired in the first place since it's acquired within the try.

No it isn't. Look again. Not at my code, but at the code I said it would be inlined into. It first calls EnterScope outside of a try-finally, then goes into a try. If the thread is aborted inside the EnterScope or inside the try that happens after the EnterScope, you're safe. But there is still the theoretical race condition that it is aborted exactly after the EnterScope method returns.

On .NET 8 or lower this resolves to this:
public Scope EnterScope()
{
>   var acquiredLock = false;
    try
    {
        Monitor.Enter(this, ref acquiredLock);
        return new Scope(this);
    }
    catch (ThreadAbortException)
    {
        if (acquiredLock)
            Monitor.Exit(this);

        throw;
    }
}

The lock is ever obtained when Monitor.Enter(...) is called, which is covered by a try/catch. The callsite will lead to this implementation due ot the polyfill.

syncObject.EnterScope() <- how is this implemented?

It absolutely does NOT matter except that it returns a disposable object. A disposable object that is not disposed if an exception happens right after such object is returned.

But we know how it's implemented, because the implementation is provided by the polyfill on the versions of the framework where thread abortion matters.
Ultimately, like I said already, I can't claim a different namespace, it would defeat the purpose of the library. So if thread abortion is an issue, it'll have to be something I'll live with.

My apologies Oleksii, a combination of me running high fever and talking about a subject I only recently found out about is resulting in me being unable to convey my point.

No problem, hope you feel better.


what's the Advantages and Disadvantages with the HttpClient

before okhttp most of us use HttpClient,so what's the Advantages and Disadvantages with the HttpClient?

OkHttp has HTTP/2, a built-in response cache, web sockets, and a simpler API. It’s got better defaults and is easier to use efficiently. It’s got a better URL model, a better cookie model, a better headers model and a better call model. OkHttp makes canceling calls easy. OkHttp has carefully managed TLS defaults that are secure and widely compatible. Okhttp works with Retrofit, which is a brilliant API for REST. It also works with Okio, which is a great library for data streams. OkHttp is a small library with one small dependency (Okio) and is less code to learn. OkHttp is more widely deployed, with a billion Android 4.4 devices using it internally.


Focus assist

A zoomed in mode displaying a small square at native resolution to make sure the photo is in focus before you take it.

Completed in #17


Pd Patch working but Unity Plugin and Compiler Preview is missing parts of patch output

Compiler is playing ball with the patch, it implements into Unity 5.2.2f1 with no problem, but the plugin isn't outputting everything that is in the patch. Patch plays as it should in Pd but runs into this after compiling. I've downloaded the Pd patch after the compile and there's no problems with, just the Unity plugin. The same goes for the plugin preview.
Patch page here: https://enzienaudio.com/h/Dercii/Water_Movement_Unity_test/

Hmm it's the bubbles sound that's not playing right? I'll take a look, can you try and isolate the part of the patch that isn't working by itself?

I'll make a patch solely of the bubble with a gain control and see if it is actually that patch.

Made the patch, still no output. Is it possible that an object is being overlooked or isn't actually supported?
https://enzienaudio.com/h/Dercii/Bubbles_Test/

I think there's two issues here:
One is that in Heavy the [vd~] object requires a signal connection to it's inlet. It's an issue in Heavy that we're aiming to fix but for now you need to insert a [sig~] object just before the [vd~] if you're connecting a control object.
The other one that I don't think your patch is doing what you expect it to do. It looks like you're trying to create a single sample delay however, by default in Pd the block size is 64 samples, and the minimum delay you'll be able to set is ~1.45ms. To override this you can use a [block~ 1] object for single sample processing. You'll hear when you add it the output in Pd goes silent, which is what Heavy will do in the javascript implementation.
I would recommend looking at some alternatives to generating your random envelopes. The multiple metros running fast is really going to eat up your CPU.
Here's a video that shows some patches for doing fire crackle sounds, I think you could re-appropriate them accordingly.
https://www.youtube.com/watch?v=uFOc_53mpBc

Would it be fine to use [rzero_rev~ 1]-[* -1] for what I want to do? I had changed it to [vd~] as I thought that was what was causing the output loss.
Would routing the same metro out to multiple sources eat up less resources? Like a master clock, if you will.

Yeah but additionally, there's another small issue in that the default argument in [rzero_rev~] won't work correctly and you'll have to do something like:
|                 [sig~ 1]
|                  |
[rzero_rev~]
|
Sorry that it's not explained anywhere, it's another thing we're looking to fix. It would probably explain why you initially got no output.

Would routing the same metro out to multiple sources eat up less resources? Like a master clock, if you will.

Yeah that would help a lot.

ahh if you replace the delayline with [rzero_rev~ 1] i think you need to also replace the [*~ -0.1] afterwards with an [abs~] instead.

Done as you've suggested. There is output now, but it isn't what is expected.


BUG: Ensure factory is registered once.

This commit updates CMakeLists.txt to ensure built library is shared. It
also uses "RegisterFactoryInternal" to make sure the factory is
registered once into the ImageIOFactory.
See InsightSoftwareConsortium/ITK@39b4ab3 (BUG: Internal factory must
use RegisterFactoryInternal method) for more details.
See ITK issue #3393
https://issues.itk.org/jira/browse/ITK-3393

@thewtex  Could you review and integrate this one ? Thanks

LGTM. Thanks for the contribution!

Merci


Not working with png

Just gonna say that you should provide at least a short description of what isn't working with PNG file types @alicansoysal. Can you provide an example of how you're using the plugin? This is a very unhelpful issue as (un)written.


[Props] Add vector/array handler

[Props] Add vector/array handler

This patch add vector property handler.

vectored property have sementics that number of size is not defined
arrayed property have sementics that number of size must match

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

[Props] Separate base_propeties to a source

This patch separate base_properties into some specialization to source
file

The purpose is to save compile time and redundant doxygen, and clean up
length header.

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1165. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @zhoonit, nntrainer/utils/base_properties.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1165-202105141250120.22685790061951-91c266f3c26e3c085b4a88d80756926e8bde0b79/.


FocusScope trigger :focus-visible on Firefox

🐛 Bug Report
A <FocusScope contain autoFocus> seems to trigger :focus-visible styles under on Firefox.
🤔 Expected Behavior
:focus-visible styles should not be applied.
😯 Current Behavior
:focus-visible styles are applied under on Firefox.
On Chrome this is not happening.
🔦 Context
Implementing a Dialog component with a close button inside. The close button shouldn't get the focus styles on programatic or mouse focus, just keyboard navigation.
💻 Code Sample
Repro https://codesandbox.io/s/sparkling-water-7fjm2
Firefox result
"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0"

Chrome result
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36"

🌍 Your Environment

Software
Version(s)

react-aria
3.2.2

Operating System
Linux

Hmm I see the same in Chrome and Safari as Firefox. My guess is that this has to do with the heuristic the browser uses to determine whether to show the focus ring or not. FocusScope uses programmatic .focus() calls to move focus, and this likely causes the browser to activate :focus-visible because the focus didn't come from a user interaction. My suggestion would be to use our useFocusRing hook to manage this instead, as it is aware of programmatic focus calls and they do not affect the modality of the page. You could also file bugs against the browsers for this, as it's likely going to be a common issue for people.

Before opening this issue I found https://bugzilla.mozilla.org/show_bug.cgi?id=1618639, but looks like they have changed that behaviour, so a programatic focus shouldn't trigger :focus-visible. Also in the repro sandbox there's a bare .focus() not nested in a FocusScope which doesn't have the problem.

I don't think this is a react-aria issue. Here's a modified reproduction that just uses an explicit focus() call on a ref, without any react-aria dependencies: https://codesandbox.io/s/gallant-microservice-kkfuj?file=/src/App.js. For me it shows the red outline across all browsers.
Again, you can use the useFocusRing hook which may provide better cross browser consistency than :focus-visible.


fix: shows properties in create resource form which does not have gui…

…order (DEV-3673)

no longer maintained, close.


Updating content

Updated to fix all the issues I've come across (see summary of changes below), while trying to execute the demo myself.
However, the demo still falls apart on knife google:

Firstly, public gem still has the old API issue, so need to:

$ sudo /opt/chef/embedded/bin/gem uninstall google-api-client -v '0.7.1'
$ sudo /opt/chef/embedded/bin/gem uninstall google-api-client

Second, getting errors while trying to get the node set up and from source it doesn't seem to be trivial to figure out:

$ knife google server create knife-test -m n1-standard-1 -I debian-7-wheezy-v20150710 -Z us-central1-b -i ~/.ssh/google_compute_engine -x temikus -VV
Looking for Image 'debian-7-wheezy-v20150710' in Project 'myproject'
Looking for Image 'debian-7-wheezy-v20150710' in Project 'debian-cloud'
Found Image 'debian-7-wheezy-v20150710' in Project 'debian-cloud'
Waiting for the disk insert operation to complete
/opt/chef/embedded/lib/ruby/1.9.1/time.rb:265:in `_parse': can't convert nil into String (TypeError)
	from /opt/chef/embedded/lib/ruby/1.9.1/time.rb:265:in `parse'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/google/compute/zone_operation.rb:42:in `from_hash'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/google/compute/resource.rb:28:in `initialize'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/google/compute/creatable_resource_collection.rb:35:in `new'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/google/compute/creatable_resource_collection.rb:35:in `create'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/google/compute/creatable_resource_collection.rb:45:in `insert'
	from /opt/chef/embedded/lib/ruby/gems/1.9.1/gems/knife-google-1.3.1/lib/chef/knife/google_server_create.rb:427:in `run'
	from /opt/chef/embedded/apps/chef/lib/chef/knife.rb:493:in `run_with_pretty_exceptions'
	from /opt/chef/embedded/apps/chef/lib/chef/knife.rb:174:in `run'
	from /opt/chef/embedded/apps/chef/lib/chef/application/knife.rb:139:in `run'
	from /opt/chef/embedded/apps/chef/bin/knife:25:in `<top (required)>'
	from /usr/bin/knife:38:in `load'
	from /usr/bin/knife:38:in `<main>'

=======
Summary of changes:

Updating deprecated syntax:

λ gcloud compute instances create chef-server --image centos-6 --zone
us-central1-b --machine-type n1-standard-1 --scopes compute-rw
storage-full
WARNING: We noticed that you are using space-separated lists, which are
deprecated. Please transition to using comma-separated lists instead
(try "--scopes compute-rw,storage-full"). If you intend to use
[storage-full] as positional arguments, put the flags at the end.
Created
[https://www.googleapis.com/compute/v1/projects/myproject/zones/us-central1-b/instances/chef-server].
NAME        ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP
EXTERNAL_IP   STATUS
chef-server us-central1-b n1-standard-1             10.240.xx.xx
104.154.xx.xx RUNNING
λ gcloud compute instances create chef-server --image centos-6 --zone
us-central1-b --machine-type n1-standard-1 --scopes
compute-rw,storage-full
Created
[https://www.googleapis.com/compute/v1/projects/myproject/zones/us-central1-b/instances/chef-server].
NAME        ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP
EXTERNAL_IP   STATUS
chef-server us-central1-b n1-standard-1             <IP_ADDRESS>
104.197.xx.xx RUNNING

Updated to newest Chef 11 package. (This really should be updated to
Chef12, but it's a lot of work...)
Chef install link now leads to client, added a proper link to server.
The documentation links for Chef were leading nowhere, I re-pointed
them, however, note, that there is no more login section in there. I
strongly suspect they wanted to remove all traces of default login:pw
from docs.
firewalls section no longer exists:

λ gcloud compute firewalls create allow-https --allow=tcp:443
...
ERROR: (gcloud.compute) Invalid choice: 'firewalls'. Did you mean
'firewall-rules'?

λ gcloud compute firewall-rules create allow-https --allow=tcp:443
(2)
Created
[https://www.googleapis.com/compute/v1/projects/myproject/global/firewalls/allow-https].
NAME        NETWORK SRC_RANGES RULES   SRC_TAGS TARGET_TAGS
allow-https default <IP_ADDRESS>/0  tcp:443

get is now list:

λ gcloud compute instances get chef-server
...

ERROR: (gcloud.compute.instances) Invalid choice: 'get'. Did you mean
'list'?

λ gcloud compute instances list chef-server
NAME        ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP
EXTERNAL_IP   STATUS
chef-server us-central1-b n1-standard-1             <IP_ADDRESS>
<IP_ADDRESS> RUNNING

The referenced Debian image no longer exists:

λ gcloud compute instances create chef-workstation --image
debian-cloud/global/images/debian-7-v20140606 --zone us-central1-b
--machine-type n1-standard-1 --scopes compute-rw,storage-full
ERROR: (gcloud.compute.instances.create) wrong number of fields:
[debian-cloud/global/images/debian-7-v20140606] does not match any of
IMAGE, /PROJECT/IMAGE

λ gcloud compute instances create chef-workstation --image debian-7
--zone us-central1-b --machine-type n1-standard-1 --scopes
compute-rw,storage-full
Created
[https://www.googleapis.com/compute/v1/projects/myproject/zones/us-central1-b/instances/chef-workstation].
NAME             ZONE          MACHINE_TYPE  PREEMPTIBLE INTERNAL_IP
EXTERNAL_IP  STATUS
chef-workstation us-central1-b n1-standard-1             10.240.xx.xx
108.59.xx.xx RUNNING

Chef quick install will install 12x client, which is incompatible with
the instructions.

/CC @erjohnso

Thanks @Temikus - lgtm!


Tipboxcoin Network

https://polygonscan.com/address/0x71b223c6387c48cfeb1756c0919401bf2c30eace#code
https://github.com/tipboxCoin-Network/
https://tipboxcoin.net/

Can anyone please do review so that it gets approved or If any corrections / modifications required please me know. Thanks

Hey @solidityx, first of all thanks for your contribution. Unfortunately, this repo supports only Ethereum mainnet and we do not have currently a list for Polygon. I will keep you updated whenever this will change


Azure Adopter re-initialize spring boot when we have several functions

Hello, guys,
I have a bug report https://github.com/Azure/azure-functions-host/issues/6719 . I investigate why it happens. I'd like to share it.
When we have more than one functions, once we send request to the other functions, it will re-initialize the spring boot.
To reproduce

Create function1 and function2
Start Azure Functions
send request to function1 -> initialize the Spring Boot then execute function1
send request to function1 -> execute function1
send request to function2 -> initialize the Spring Boot then execute function2
send request to function1 -> initialize the Spring Boot then execute function1

Possible Root Cause
In this logic, the AzureSpringBootRequestHandler has functionName. It compares if it is the same as the functionName and if not the same, it will initialize it.
https://github.com/spring-cloud/spring-cloud-function/blob/a7104e489ec1f608dc7229b9faad12ca6eedf460/spring-cloud-function-adapters/spring-cloud-function-adapter-azure/src/main/java/org/springframework/cloud/function/adapter/azure/AzureSpringBootRequestHandler.java#L81
Sample
https://github.com/Azure/azure-functions-host/issues/6719#issuecomment-703119773
Related
https://github.com/spring-cloud/spring-cloud-function/issues/425

I can confirm I had the same issue. Are there any possibility to have this fixed?

I have the same problem.
Are there any possibility to have this fixed?
Thanks

We are facing the same problem,
Our clients are pushing us to solve this issue...
We are seeing an excessive increase in the times of the calls to the functions which prevents the migration of the application.
Is there any quick fix for this issue? or any update soon?
Thanks in advance!


Error when loading specific values in fields of type {:map, :float}

Environment

Elixir version (elixir -v): Elixir 1.6.4
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): PostgreSQL 9.6.7
Ecto version (mix deps): master branch
Database adapter and version (mix deps): postgrex 0.14.0-dev
Operating system: Debian Jessie

Current behavior
When I have a schema with a field of type {:map, :array}, some values are parsed to exponential floats and are saved as integers in the database.
For example,  %{"50" => 416500.0} fails, because it is saved as an integer 416500, even after Float.parse(416500), which returns an exponential form for it. I don't know if it has something to do with the jsonb fields, but for simple floatfields it works.
Float.parse("416500")
{4.165e5, ""}

I've added an example to ecto integration tests that shows the break point. See this commit https://github.com/tallysmartins/ecto/commit/5048199197ff2bd3e1480cd8286931f2d07cddde and the correspondent build on Travis-ci
     ** (ArgumentError) cannot load `%{"50" => 416500}` as type {:map, :float} for field `scores` in schema Ecto.Integration.Post
     code: assert [_] = TestRepo.all from p in Post, where: p.title not in []
     stacktrace:
       (ecto) lib/ecto/schema.ex:1794: Ecto.Schema.load!/5
       (ecto) lib/ecto/schema.ex:1742: Ecto.Schema.safe_load_zip/4
       (ecto) lib/ecto/schema.ex:1743: Ecto.Schema.safe_load_zip/4
       (ecto) lib/ecto/schema.ex:1730: Ecto.Schema.__safe_load__/6
       (ecto) lib/ecto/repo/queryable.ex:316: Ecto.Repo.Queryable.process_source/6
       (ecto) lib/ecto/repo/queryable.ex:191: anonymous fn/6 in Ecto.Repo.Queryable.preprocessor/3
       (elixir) lib/enum.ex:1294: Enum."-map/2-lists^map/1-0-"/2
       (ecto) lib/ecto/repo/queryable.ex:152: Ecto.Repo.Queryable.execute/4
       (ecto) lib/ecto/repo/queryable.ex:18: Ecto.Repo.Queryable.all/3
       integration_test/cases/repo.exs:44: (test)

Expected behavior
Save and load the field the same way as simple float field.

It's curious that the integration test fails on pg but passes on mysql.

@wojtekmach good point! but actually I didn't add a value for field to a test case for mysql, just for pg  :thinking:

It seems this is an issue with how postgresql handles JSON with floats in exponential notation.
# create table foo(map jsonb);
CREATE TABLE
# insert into foo(map) VALUES ('{"foo": 416500.0}');
INSERT 0 1
# insert into foo(map) VALUES ('{"foo": 4.165e5}');
INSERT 0 1
# SELECT * FROM foo;
        map
-------------------
 {"foo": 416500.0}
 {"foo": 416500}
(2 rows)

@michalmuskala the worst part is that Postgres is semantically correct, there are no integers/floats in JSON. I guess we need to do casting here on Ecto side.

Should we do for {:map, _} type the same thing we do for {:embed, _} in here? https://github.com/elixir-ecto/ecto/blob/master/lib/ecto/adapters/sql.ex#L47

@michalmuskala if it fixes the bug, sure. :) We may need to do a couple extra things though.

Any chance that this problem is also happening with {:array, :float}? I have a issue with an array of floats sometimes failing to be inserted. (Elixir 1.7.3, ecto, 2.2)


Folder search result is not displayed

Although a Message (x) Results present is shown the search results are not shown. This is after the latest update.

Does this happen every time you search in project? Please quit atom completely and run atom --safe. Is the issue still there?
For the record, I am not able to reproduce.

I'm seeing the same issue, but not while running atom in safe mode. I'm running version 0.175 on Ubuntu 14.10.

It works fine in safe mode or disable all community packages. But I can reproduce the bug if I enable either "command-logger" or "hex" package. Probably, there are other packages trigger the same problem. (Version 0.175 on Windows 7)

Oddly enough I'm seeing this issue as well.
I'm on Windows 8.1 with Atom 0.175. I haven't noticed this with my work computer (windows 7).

I've got these packages installed:

highlight selected
minimap
minimap highlight selected

It does not happen on safe mode though.

Update: it seems to only happen when I have the minimap package installed. It may be a direct issue with that package.

@zephraph I had Minimap installed but have uninstalled it but the issue still does not go away.

Closing this for now and will add a issue in Mini map. Thanks guys.

The merge-conflicts package is another that triggers this behavior (atom 0.175 linux version). So this isn't isolated to the minimap package.

I'm going to reopen this until we figure out what is happening.

A bit more information on this:
When this behavior is present, performing a project find results in the Project Find Results pane displaying No results found for "" at the top and the background No Results in the center.
If pane is closed and the same search perform a second time, the pane says 13 results found in 7 files for ... (which is the correct count) and the No Results no longer appears on the background (the pane content are empty).
So something is happening once the `Project Find Results

Feel free to check my comments on the minimap issue for the things I was experiencing on this as well.

Also, this is OS dependent. I tried the same steps I mentioned above on OS X 10.10.2 and the project find has no issues.

Cannot reproduce in osx. Trying windows...

Reproduced in windows. Looking into it...

Ok, looks like the space-pen attached and detached hooks are not firing. Find and replace is requiring space-pen-views (2.0.0) while merge-conflicts is requiring space-pen (5.0.1). Not sure how these interact. It _should_be fine. But, nope.

It's loading the wrong version of space-pen when some packages (e.g. merge-conflicts) are enabled. It's loading the atom bundled space-pen (3.8.2). Passing to @kevinsawicki as he is the module cache guy

I can reproduce it on Ubuntu 14.04 64 and Atom 0.175
Another package that cause this bug is git-history
With either of git-history or minimap I am getting the same bug.

Merge-conflicts package causes the same problem (Atom 0.175, Mint 17.1)

So the issue here was that 0.175 release of Atom on Debian and Windows was missing some files.
This occurred because of #5176 which was never merged but still messed up the build machines enough to cause this.
Our build machines don't clean out the node_modules folders between builds, this is done to save time and since npm install updates the dependencies, it is almost always fine to do this.
The one case this doesn't catch is when a module is de-duped to the root node_modules folder.  Once at the root, npm install won't re-install new versions of the module into sub-dependencies if the root version exists, even when the root version isn't compatible with the version used by the sub-dependency. It instead just logs a warning which wasn't noticed.
So I've cleaned out the Debian and Windows CI machines completely and verified that the latest pre-release builds of 0.176 contain the proper files.
0.176 should be released in the next couple of hours.

Nice


Order of most recent validations and schemas

Recent validations seems to show the most recent validation first.
Recent schemas seems to show the most recent schema last.
Can these two lists be consistent in their ordering?

Recent validations has gone away, so this is sort of done, but I think the order of the recent schema list should be inverted so I'll leave it open.


Infinite looping on failed deployment

I normally won't post an issue until I've spent time reading all the docs and looking through configuration options.  Maybe I've missed a setting but have seen this a couple times now and would like to know how to set it to fail after X attempts.
When our continuous delivery posts a new version of a Docker based applications there is the odd time it fails to startup/health check.  For example in a Spring/Hibernate based app that has schema changes that are failing to update due to a constraint.  What happens is it FAILS in Mesos, then is re-launched again.  I've seen this happen for 20 hours straight until I killed the deployment completely.
What do I set to fail after N times or N time frame or is this the desired community behavior?

If a task fails more than maxConsecutiveFailures health checks consecutively, that task is killed causing Marathon to start more instances. These restarts are modulated like any other failing app by backoffSeconds, backoffFactor and maxLaunchDelaySeconds. The kill of the unhealthy task is signalled via unhealthy_task_kill_event event.

Marathon will try to start the app forever. There's no way to tell Marathon to give app after a certain number of retries, but it supports an exponential back-off between retries. Please check https://mesosphere.github.io/marathon/docs/rest-api.html for more details.


WebSocket example is missing

Documentation states that FastAPI has support for WebSockets but there is no example on how to deal with it in code. Search on the internet is giving no results.

This works.
`
from fastapi import FastAPI
from starlette.endpoints import WebSocketEndpoint, HTTPEndpoint
from starlette.responses import HTMLResponse
app = FastAPI()
html = """

Chat

WebSocket Chat

Send

"""
@app.route("/")
class Homepage(HTTPEndpoint):
async def get(self, request):
return HTMLResponse(html)
@app.websocket_route("/ws")
class Echo(WebSocketEndpoint):
encoding = "text"

async def on_receive(self, websocket, data):
    await websocket.send_text(f"Message text was: {data}")`

Thanks for example

Thanks @andrijdavid for your help here. It is very appreciated. :taco: :tada:

@denisvlah There's a new section in the docs with more or less these same ideas: https://fastapi.tiangolo.com/tutorial/websockets/

Hi, @tiangolo! Really appreciate your child, like it for real =)
How about to add the above example with WebSocketEndpoint to the documentation?
@app.websocket_route("/ws")
class Echo(WebSocketEndpoint):

    encoding = "text"

    async def on_receive(self, websocket, data):
        await websocket.send_text(f"Message text was: {data}")

Took some time from me to found it.
Class-base endpoint saves from some not-required boilerplates.

@rappongy could you add that in another issue to keep track of that? 🤓

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


When deleting a file via another Git client, Underline is wrong colour

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.69.2
OS Version: Windows

Steps to Reproduce:

Create empty file in VSCode (File is green)

Delete it via another Git client:

Go back to VS Code

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Updated. Issue remains

@bpasero, could you please take a quick look as I am not certain that this is an issue with source control.
I am seeing the same time of behaviour if I just create a file and then delete it using Windows Explorer.

The issue is that the strike thought in the tab label is green which the text is red.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Seems ok to me when zooming in:

I believe that the gesture to zoom in, repaints the tab. I am able to reproduce consistently in VS Code Insiders.

Since this is drawing properly upon zooming or even resizing the window, I doubt we can do something about it in VS Code and it is rather an upstream bug such as Chromium. I was not able to find us setting text-decoration-color in that context and so closing as wont fix from our end.


Clean up mk_GEOSldasRestarts and process_rst.csh

This branch should have zero-diff. Excepp 1) The regridded restart has non-zero TSURF 2) the regridded restart has the same variables as original restart, i.e. , it does not add WW, FR, CQ, CH etc if the original restart does not have . 3) it depends on new GEOSgcm_GridComp and MAPL

@weiyuan-jiang, @biljanaorescanin,
Now that Scott has merged GEOSgcm_GridComp PR#571 and
is in the process of merging GMAO_Shared PR#238, I'm wondering if we should merge this GEOSldas PR as is or tweak it further.
A quick inspection of the changes suggests that this PR calls mk_catchANDcnRestarts.F90 directly, rather than going through the new remap_catchANDcn.py.  Would it make sense to further modify this PR to use the new python script?
In this context, I know Scott needs command line options for the new remap restarts python script(s) before he can use it in the GCM setup script.  This means we'll have to do some additional work on the python scripts, and it may be better to wait until this new work is complete before we convert the LDAS setup to use the new remap restarts utilities.  (In a nutshell, Scott needs a one-line command option to remap restarts, which isn't an option right now  because everything goes through yaml files.  I can't say for sure, but I don't think we need to abandon the yaml files.  Rather, it should be possible to create a wrapper script or function that deals with creating the yaml file when given command line inputs.)
Thoughts?

I tested this branch before but I will test it again after things are settled. Yes, I will add a command line to generate the yaml file.

This PR ( may need to change component.yaml ) is zero diff except global assim run.  This assim run used LDASsa's restart, which is not supported any more. We should change the restart.

The two most recent commits revert the components.yaml file back to the "develop" version, in prep for merging the PR into "develop".
This PR requires first merging of https://github.com/GEOS-ESM/GMAO_Shared/pull/276

PRs #569 and #574 should be merged first to minimize conflicts.
Prior to merging the present PR, need to change CMakeLists.txt in the present branch to make it compatible with changes in #569.

PRs #569 and #574 should be merged first to minimize conflicts. Prior to merging the present PR, need to change CMakeLists.txt in the present branch to make it compatible with changes in #569.

PRs #569 and #574 have been merged, and the present branch has been updated to "develop," incl. resolution of the conflict in CMakeLists.txt.
Successfully completed LDAS Nightly 0-diff tests (Intel only) after https://github.com/GEOS-ESM/GEOSldas/pull/551/commits/e6994a3bfd9ef54335f577418161b30abbefee7f  (i.e., before updating of CatchCN dummy restart files).

@gmao-rreichle  all intel tests passed

@gmao-rreichle  Since this is on develop and current develop fails after rebase we did for GNU tests these tests fail for same tests. All intel tests passed.
gnuconus         pass  pass  12 min     pass/FAIL          -- / --
gnuglobal         --    --    --        pass/FAIL         pass/FAIL
gnuglobalcs       --    --    --        pass/FAIL         pass/FAIL
gnuglobalcnclm4   --    --    --        pass/FAIL          -- / --
gnuglobalcnclm45  --    --    --        pass/FAIL          -- / --


Add edu.uca.ma

Hello there!  I have the academic Email which ends up with @edu.uca.ma
and I already got the GitHub student pack with it but now when I'm trying to apply for the JetBrains Products for Learning and they tell me this:
Sorry, we can't accept your email address because we are not able to identify if the people from this email domain are truly students or not.
This could have happened for the following reasons:

Your school allows registering an email address there even if you are not a student of the college.
Someone from the school sold or shared their account details or activation code publicly, which has led to a broad account misuse and license terms violation.

Please consider merging my pull request!

@yassine-bennkhay lib/domains/ma/ac/uca: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@yassine-bennkhay Thank you for your request. Regrettably, this domain is removed from our trusted list because one of the following happened:

the college allows to register an email address there even if you are not a student of the college.
someone from the college shared their account details or sold it, and it lead to broad account misuse and license terms violation.

Therefore, we are not able to identify if the people with @edu.uca.ma addresses are actual students or not.
If you are the student of this college, please apply with official document ("Official document" tab at https://www.jetbrains.com/shop/eform/students).
I have to close this request without merging.


Fix/eol

To avoid errors on Travis with line ending.
This branch has the same fix for showing private and protected methods and properties out of the context.

Yes, I can.
Should I add it to tests\Server\TextDocument\CompletionTest.php?
I tested this launching the php-intellisense extension pointing to my local copy of the language server.
I will write the test.
Travis keeps failing because of the line ending.

What editor are you using? You should configure it to trim trailing whitespace (or delete it manually)

I use VS Code and Netbeans, I configured VS Code.
Thanks!
Next commit with the test should be fixed

I did merge the branch already, sorry, I have to get used to the code. I removed the part of the static checking. I would like to test it better.


Provide a reference to the module CR after enabling module

Description:
After enabling the module it is unclear which resources were created and can be used to configure that module. To track it the user would need to go to the ModuleTemplate and check what the apiVersion is and what kind of a resource was created and then ask for a specific resource.
This can be simplified by providing a direct reference to the CR that was created in the Status field of the Kyma CR, i.e. for Keda it would be something like this:
modules:
    - name: keda
      state: Ready
      channel: alpha
      ...
      resource:
        apiVersion: operator.kyma-project.io/v1beta1
        kind: Keda
        metadata:
          name: keda-sample
          namespace: kyma-system

Acceptance Criteria:

[ ] Kyma CR contains a direct reference to the module CR that was created by enabling a module

Blocked by #534


Use existing crowdin translations for new app

Hey there!
We have a crowdin project which is used for an android native app currently.
At the moment we are doing a rewrite in Flutter and would like to still use the translations from the old app.
They will both exist at the same time for a few years possibly.
Is there a way to fetch translation from crowdin that are already there and not use a source file in the current project?

Hi @juliajulie95 !
We can recommend using bundles if you don't want to use source files:
https://support.crowdin.com/bundles/


⚠ Bofrost.si has degraded performance

In 915410b, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 2010 ms

Resolved: Bofrost.si performance has improved in 21a28d8 after 8 minutes.


#766 fix proxy stream

closes https://github.com/coupergateway/couper/issues/766

Reviewer checklist

Read PR description: a summary about the changes is required
Changelog updated
Documentation: docs/{Reference, Cli, ...}, Docker and cli help/usage
Pulled branch, manually tested
Verified requirements are met
Reviewed the code
Reviewed the related tests

If I change the paths to
	paths := []string{
		"/named",
		"/named",
		"/named",
		"/named",
	}

(which doesn't have default request/proxy), TestBackend_MaxConnections_BodyClose passes 10/10.
If I change it to
	paths := []string{
		"/",
		"/",
		"/",
		"/",
	}

(which has default request), TestBackend_MaxConnections_BodyClose fails 8/10.
So I guess, this is related to the changes to the handling of default requests/proxies in this PR.

The test started to fail with commit "Fix buffer condition and related body parse in combination with syncedVariables provided by each backend instance", then passed with commit "Fix random order related to the default block while preparing roundtrips" and failed again with commit "reduce produce wait-time; TODO".
Apparently, the
		time.Sleep(time.Nanosecond * 10) // TODO: refactor to ch pipe

is not stable enought. The previous
		time.Sleep(time.Millisecond * 5) // TODO: refactor to ch pipe

was more stable.


Add support for using unverified_person in dev

Signed-off-by: Wade Barnes<EMAIL_ADDRESS>

Adds support for using the CANdy-Dev rooted Unverified Person credential for the accredited-lawyer-bcpc-dev presentation request.

The presentation request has already been registered.


FEAT: alaska scraper

I've formatted the data but now I'm stuck. There are a few data questions I have and I'm not sure how to proceed.
Some of the rows have a dose_number == 3. I'm not sure how to interpret that. My initial though was those were J&J doses. But that doesn't seem to match up with the data. I've labeled the corresponding columns with dose_unknown.
Some rows had a fips value of 000 or NULL. I assume that NULL means unknown county. I drop those rows. I thought fips == '000' means statewide, but that doesn't match up.
Here is the dashboard for reference: https://alaska-coronavirus-vaccine-outreach-alaska-dhss.hub.arcgis.com/app/c74be37e02b44bb8b8b40515eabbab55

Hey @tlyon3 sorry for super long delay on this one.
I tried running AlaskaCountyVaccine  today and saw that it is broken :(
It complains that a column primarkeyid does not exist in fetched data.
Perhaps we could switch to using objectid column instead? Will you please take a look and see if we can get it running.

Changed and is running


Could not build getting started on Ubuntu ARM64 Raspberry Pi

I tried to run getting started on Raspberry Pi Ubuntu 20.10 Desktop ARM64
uname -a
Linux user-desktop 5.8.0-1015-raspi #18-Ubuntu SMP PREEMPT Fri Feb 5 06:09:58 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

I got an error when run build process as bellow.
Processing core2foraws (platform: https://github.com/platformio/platform-espressif32.git; framework: espidf; board: esp32dev)
-------------------------------------------------------------------------------------------------------------------------
Tool Manager: Installing platformio/toolchain-xtensa32 @ ~2.80400.0
Error: Could not find the package with 'platformio/toolchain-xtensa32 @ ~2.80400.0' requirements for your system 'linux_aarch64'
The terminal process "pio 'run', '--environment', 'core2foraws'" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

It seems that the toolchain can not be available for ARM64.
Does someone  knows any workaround?

This thread seems to indicate there might be one: https://github.com/platformio/platform-espressif32/issues/236
based on the workaround for the issue found here: https://github.com/esphome/issues/issues/594

If you can avoid it, I would recommend not running it on a Raspberry Pi. The performance will be so limited compared to a laptop in the past several years that compiling each of the binaries will probably take hours.
That said, this seems PlatformIO feature request. Let us know if the suggestion by Brianivie works for you. We'll think about testing and incorporating this workflow if there is enough demand, but my assumption is that the experience will be extremely poor.

@brianivie Thank you for your advice. However I could not solve the probrem to tried those workarounds.
I guess its platformio problem that Tool Manager always failed to download in spite of installed new toolchan in ~/.platformio/pacakges/ .
I make sence that its difficult to setup esp32 dev environment on arm64 computer for now.

@rashedtalukder I tried it but could not works fine for now. I understood to difficult to use RPi for getting start Edukit thanks  your advice.
I throught that if I can prepare dev environment on RPi, I can increase easily the environment for education by copied SSD. However I may shoud give up it because it will be unconfortable if compiling  was slow.


Editing the activities of the current project

When a project is open it would be nice to be able to change activities.
The userflow might be as follows:

The user presses any activity for a while.
A model activity editing window opens.
The user can save the changes made, cancel them, or remove the activity from the project.

Blocked by #12

Implemented in v1.1.


Fix (N>4)D shapes.

This is on top of #6206 and should fix #6205, it gets inspiration from #4465 and introduce batch updates.
The problem arise when:
self.a = x
self.b = y

When both a and b are evented and each trigger somehow something.compute(), that requires both self.a and self.b to have been set.
Example is if both are ndarray whcih shape depends on ndim, and compute() does some broadcast operation.
This could also be used to remove things like:
def foo(self,..., update=True):
        """same as update_edge_color() but for multiple indices/edgecolors at once"""
        ...
        if update:
            self._update_displayed()

One thing I dont like is that _update_displayed does set 2 public varaibles:
        self.displayed_vertices = self._vertices[disp_vert]
        self.displayed_index = self._index[disp_vert]

and so if those are used from within a batched_updates context manager they might be incorrect.
We could made those properties that's can't be accessed/set while pending updates.
As I believe the but was marked as 4.x, I tried to be non-invasive, but further improvement would be to split _update_display() into _request_update() and _do_update(), and maybe move that to the base layer. It might be worth also doing the same with _update_z_order and other, but it's a bit more involved as _update_z_order calls into _update_display so order of context is important.
This also has few effect on performance as in my test it batched at most 2 calls to update display.

There is merge conflict that need to be resolved.

Rebase on main. All should be good.

Is this bug present in 0.4.18?

Is this bug present in 0.4.18?

Yes, but I think it will be complicated to backport.


compute average training speed and time after training from (.log.json) file.

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help. yes
I have read the FAQ documentation but cannot get the expected help. yes
The bug has not been fixed in the latest version. yes , as far as i know

not display correct value for train time ,see bellow image.
Describe the bug
A clear and concise description of what the bug is.
i am trying to train CenterNet in my own custom dataset ,which has the same format of COCO dataset.
i got the results of the training as (.log.json) and got images tested by a desired (epoch.pth) file . but when i try to analysis the training and find the time of training i got a nan value
here is the error massage:

Reproduction

What command or script did you run?

python tools/analysis_tools/analyze_logs.py cal_train_time train_results/centernet/20220309_152747.log.json

Did you make any modifications on the code or config? Did you understand what you have modified?
yes , i made same modification on other models ,for example fasterRCNN , CentriapetalNet , and it works ,and i got the results of training time.
What dataset did you use?
my custom dataset ,with a same format of COCO one.

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.

TorchVision: 0.8.0a0
OpenCV: 4.3.0
MMCV: 1.3.8
MMCV Compiler: GCC 7.5
MMCV CUDA Compiler: 11.0
MMDetection: 2.18.1+393c376

You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
it was installed before in the server (GPU) using some docker files.
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)
i install seaborn using this instruction pip install seaborn as the system asked me.

Error traceback
If applicable, paste the error trackback here.
tools/analysis_tools/analyze_logs.py:21: RuntimeWarning: Mean of empty slice.
  epoch_ave_time = all_times.mean(-1)
/opt/conda/lib/python3.6/site-packages/numpy/core/_methods.py:163: RuntimeWarning: invalid value encountered in true_divide
  ret, rcount, out=ret, casting='unsafe', subok=False)
/opt/conda/lib/python3.6/site-packages/numpy/core/fromnumeric.py:3373: RuntimeWarning: Mean of empty slice.
  out=out, **kwargs)
/opt/conda/lib/python3.6/site-packages/numpy/core/_methods.py:170: RuntimeWarning: invalid value encountered in double_scalars
  ret = ret.dtype.type(ret / rcount)

A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

Could you provide the dataset size and the config? It may be because the iteration number of one epoch is less than the interval of log_config.

Thank you for your replay , my dataset is not so huge , it is images 845 for training, 88 images for testing and 82 images for validation.
here is the config file:

log_config has interval =50, is that the mistake?

here are my whole config:

please notice that the value 50 in log_config , interval is already mentioned in the default_runtime .py  i did not change it even with other detectors,such as CentriapetalNet and CornerNet.

thank you very much , I changed the  log_config, interval  to become 20 instead of 50 , now it is working.
I got a value for
average iter time: 1.4562 s/iter, which seems to be good so far.
But i still did not understand why that happened? and the reason behind that? could you please explain it for me ?

where can I find the iteration number of one epoch? i only have the max number of epoch which is in my case =100

The iteration number is the dataset size divided by the batch size.

okay, thank you ..
do you think it is also the reason that the losses in my training during all epoch was zero , like in this image.

Yes, I think they are all caused by this reason.

I am really sorry , I am still new with this.
batch size is the sample_per_gpu , is it correct?

until now i did not understand what are the differences between ; sample_per_gpu and worker_per_gpu ?
is there any document that helps in understand such terms.

sample_per_gpu indicates the image batch in one GPU, workers_per_gpu indicates the number of processes for one GPU.

The GPU number is set in the command line. Not displayed in config.


Fix issue #4070 and #3925

Fix issue #4070 and #3925

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tian-y-x:x:<PHONE_NUMBER><EMAIL_ADDRESS>seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix optimisation default member

Fix optimisation default member.
Fix duplicate generate displayAvatarUrl member
Change visual :)

Thanks for your contribution x)


[FLINK-10141][network] optimisations reducing lock contention

What is the purpose of the change
With the changes around introducing credit-based flow control as well as the low latency changes, unfortunately, we also introduced some lock contention on RemoteInputChannel#bufferQueue and RemoteInputChannel#receivedBuffers. Additionally, we were asking for queue sizes when the only thing we need is whether it is empty or not.
As a result, we saw high CPU load during "idle" stream processing jobs with no events in the stream but only watermarks (every 500ms) and many slots on a single machine.
Brief change log

move notifyCreditAvailable() out of the lock around RemoteInputChannel#bufferQueue
move notifyChannelNonEmpty() out of the lock around RemoteInputChannel#receivedBuffers
replace RemoteInputChannel#receivedBuffers.size() with receivedBuffers.isEmpty() when this is the only thing needed
replace SingleInputGate#inputChannelsWithData.size() with inputChannelsWithData.isEmpty() when this is the only thing needed
minor code style improvement in CreditBasedPartitionRequestClientHandler to improve readability

Verifying this change

This change is already covered by existing tests, such as RemoteInputChannelTest, SingleInputGateTest,..., and everything using the network stack.
Manually verified that less CPU is used with a SocketWindowWordCount with some added shuffles, no input elements, only watermarks every 500ms with 4 TMs, 10 slots each on a single (laptop) machine (together with #6555).

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no (per buffer)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? JavaDocs

@pnowojski I just pushed changes based on your review of #6555 which should be covered now


sw_engine clipping: fix segfault after scene used for ClipPath

ClipPath doesn't work with scene. This is a temporary solution that fixes
segfault if scene is applied as clippath composition anyway.

Created a full support patch, so closing this temporary one solution


raftstore: return sibling regions via batch_split_limit

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
After introducing batch split, a region may split into multiple regions simultaneously.
We return only one sibling region to clients when meeting "epoch not match" error currently, this proved may cause many of "get region" operations to pd which would bring performance jitter.
What is changed and how it works?
Proposal: xxx
What's Changed:
Scan regions from StoreMeta via batch_split_limit, and put it to the response.
Check List
Tests

Unit test
Integration test

Side effects

Performance regression

Consumes more CPU

Release note

raftstore: return sibling regions via batch_split_limit in "epoch not match" responses

And the epoch-not-match error from CmdEpochChecker::advance_apply also needs to be changed.

FYI, the following graphs can show the improvement at the heavy-split workload. The jitter was still caused by backoff of region miss on pd:

/run-test

PTAL

PTAL, thanks!

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

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

PTAL

The work may return too many regions for every epoch not match. You can refer #9692 to see how to return a reasonable small subsets.


cann't install on laravel 6.18.40

Version information

Laravel: v6.18.40
Voyager: v1.4
PHP: 7.2
Database: [type] [version] (e.g. MySQL 8.0)

Description

Problem 1
- Conclusion: don't install tcg/voyager v1.4.2
- Conclusion: don't install tcg/voyager v1.4.1
- Conclusion: remove league/flysystem 1.1.3
- Installation request for tcg/voyager ^1.4 -> satisfiable by tcg/voyager[v1.4.0, v1.4.1, v1.4.2].
- Conclusion: don't install league/flysystem 1.1.3
- tcg/voyager v1.4.0 requires league/flysystem ~1.0.41 -> satisfiable by league/flysystem[1.0.41, 1.0.42, 1.0.43, 1.0.44, 1.0.45, 1.0.46, 1.0.47, 1.0.48, 1.0.49, 1.0.50, 1.0.51, 1.0.52, 1.0.53, 1.0.54, 1.0.55, 1.0.56, 1.0.57, 1.0.58, 1.0.59, 1.0.60, 1.0.61, 1.0.62, 1.0.63, 1.0.64, 1.0.65, 1.0.66, 1.0.67, 1.0.68, 1.0.69, 1.0.70].
- Can only install one of: league/flysystem[1.0.41, 1.1.3].
- Can only install one of: league/flysystem[1.0.42, 1.1.3].
- Can only install one of: league/flysystem[1.0.43, 1.1.3].
- Can only install one of: league/flysystem[1.0.44, 1.1.3].
- Can only install one of: league/flysystem[1.0.45, 1.1.3].
- Can only install one of: league/flysystem[1.0.46, 1.1.3].
- Can only install one of: league/flysystem[1.0.47, 1.1.3].
- Can only install one of: league/flysystem[1.0.48, 1.1.3].
- Can only install one of: league/flysystem[1.0.49, 1.1.3].
- Can only install one of: league/flysystem[1.0.50, 1.1.3].
- Can only install one of: league/flysystem[1.0.51, 1.1.3].
- Can only install one of: league/flysystem[1.0.52, 1.1.3].
- Can only install one of: league/flysystem[1.0.53, 1.1.3].
- Can only install one of: league/flysystem[1.0.54, 1.1.3].
- Can only install one of: league/flysystem[1.0.55, 1.1.3].
- Can only install one of: league/flysystem[1.0.56, 1.1.3].
- Can only install one of: league/flysystem[1.0.57, 1.1.3].
- Can only install one of: league/flysystem[1.0.58, 1.1.3].
- Can only install one of: league/flysystem[1.0.59, 1.1.3].
- Can only install one of: league/flysystem[1.0.60, 1.1.3].
- Can only install one of: league/flysystem[1.0.61, 1.1.3].
- Can only install one of: league/flysystem[1.0.62, 1.1.3].
- Can only install one of: league/flysystem[1.0.63, 1.1.3].
- Can only install one of: league/flysystem[1.0.64, 1.1.3].
- Can only install one of: league/flysystem[1.0.65, 1.1.3].
- Can only install one of: league/flysystem[1.0.66, 1.1.3].
- Can only install one of: league/flysystem[1.0.67, 1.1.3].
- Can only install one of: league/flysystem[1.0.68, 1.1.3].
- Can only install one of: league/flysystem[1.0.69, 1.1.3].
- Can only install one of: league/flysystem[1.0.70, 1.1.3].
- Installation request for league/flysystem (locked at 1.1.3) -> satisfiable by league/flysystem[1.1.3].

We cannot know what's the problem.
Something is preventing Voyager v1.4.2 to be installed and v1.4.0 had a fixed reference for league/flysystem.
If I were you I'd upate PHP and try again since it will be EOL in two months anyway.

The issue is that you have a specific version of league/flysystem required (either in your composer.json or from another package), but Voyager needs a different version.  This causes contention.  If you don't have that package locked at a specific version (i.e. 1.1.3, not ^1.1 or 1.1.*) in your composer.json, then delete your composer.lock file and try again.

We cannot know what's the problem.
Something is preventing Voyager v1.4.2 to be installed and v1.4.0 had a fixed reference for league/flysystem.
If I were you I'd update PHP and try again since it will be EOL in two months anyway.

I updated php version 7.2 to 7.3 but cann't install voyager

The issue is that you have a specific version of league/flysystem required (either in your composer.json or from another package), but Voyager needs a different version. This causes contention. If you don't have that package locked at a specific version (i.e. 1.1.3, not ^1.1 or 1.1.*) in your composer.json, then delete your composer.lock file and try again.

I tried like that but  issue is same before

I have been try to  install by upgrade laravel 7 but cann't install.

I can confirm this issue. To me it looks like the latest stable version of voyager requires league/flysystem: ~1.0.41 (https://packagist.org/packages/tcg/voyager#v1.4.2) but the laravel 6 framework league/flysystem: ^1.1 (https://packagist.org/packages/laravel/framework#v6.20.16)

@SamuelWei that's accurate, I thought it was fixed in 1.4.2 but it's only fixed in dev with merged https://github.com/the-control-group/voyager/pull/5068.
@yannnaingoo untill 1.4.3 is released you'll need to require 1.4.x-dev setting minimum-stabilitydev in composer.json

@SamuelWei that's accurate, I thought it was fixed in 1.4.2 but it's only fixed in dev with merged #5068.
@yannnaingoo untill 1.4.3 is released you'll need to require 1.4.x-dev setting minimum-stabilitydev in composer.json

My problem is, that I need to update laravel due to a security issue (https://github.com/advisories/GHSA-3p32-j457-pg5x and https://github.com/advisories/GHSA-x7p5-p2c9-phvg) but don't want to install an unstable version of voyager for production usage. Would it be possible to release 1.4.3 with newer dependencies (+ bugfixes) and have the new features in a 1.4.4 release?

@SamuelWei we don't have much man power to manage that but you can fork Voyager and apply #5068 or any other fix you want, so you have total control of what to update.
I'm closing this since fix is already merged.

Can't you just release a new Version with the fix, since your last Release is Jun 2020.