Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.InputPullup but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.InputPullup but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.OneWire but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.OneWire but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Pwm but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Pwm but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Serial but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Serial but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Servo but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Servo but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Shift but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Shift but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Sonar but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Sonar but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Spi but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Spi but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Stepper but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Stepper but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Tone but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Tone but can't be found in parent type.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Arduino.SupportedMode.ToString.

iot-api-docs/xml/Iot.Device.Ht1632/Ht1632ImageSending+BrightnessConvertor.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SixLabors.ImageSharp.PixelFormats.IPixel'.

iot-api-docs/xml/Iot.Device.Ht1632/Ht1632ImageSending.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SixLabors.ImageSharp.Image`1'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SixLabors.ImageSharp.Image`1'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'SixLabors.ImageSharp.PixelFormats.IPixel'.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+I2cAdapter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+SpiAdapter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.Nmea0183.Sentences/EngineRevolutions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.RotationalSpeed'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.RotationalSpeed'.

iot-api-docs/xml/Iot.Device.PiJuiceDevice.Models/BatteryProfile.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricCharge'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricCharge'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricCharge'.

iot-api-docs/xml/Iot.Device.RadioReceiver/RadioReceiverBase.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.Frequency'.

iot-api-docs/xml/Iot.Device.RadioReceiver/Tea5767.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.Frequency'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.Frequency'.

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixI2c.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixSysFs.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.Usb/BatteryObject.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.

iot-api-docs/xml/Iot.Device.Usb/FixedSupplyObject.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.

iot-api-docs/xml/Iot.Device.Usb/StUsb4500.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.

iot-api-docs/xml/Iot.Device.Usb/VariableSupplyObject.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'UnitsNet.ElectricPotentialDc'.

iot-api-docs/xml/System.Device.Gpio/PinValue.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.IEquatable`1.GetHashCode'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.IEquatable`1.GetHashCode'.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: System.Device.Gpio.PinValue.GetHashCode.

iot-api-docs/xml/Iot.Device.Amg88xx/Amg88xx.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Arduino/SupportedPinConfiguration.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Arduino.SupportedPinConfiguration.ToString.

iot-api-docs/xml/Iot.Device.Bmxx80.PowerMode/Bme680PowerMode.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Bno055/Info.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.BrickPi3.Models/BrickPiInfo.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Common/GeographicPosition.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Common.GeographicPosition.GetHashCode.

iot-api-docs/xml/Iot.Device.Common/WeatherHelper.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'example' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'example' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.HardwareMonitor/OpenHardwareMonitor+Sensor.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.HardwareMonitor.OpenHardwareMonitor.Sensor.ToString.

iot-api-docs/xml/Iot.Device.Max7219/MatrixGraphics.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Max7219/Max7219.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Mcp23xxx/BankStyle.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Register.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Nmea0183/DeviationPoint.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Equals(System.Object) for uid: Iot.Device.Nmea0183.DeviationPoint.Equals(System.Object).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Nmea0183.DeviationPoint.GetHashCode.

iot-api-docs/xml/Iot.Device.Nmea0183/Identification.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Equals(System.Object) for uid: Iot.Device.Nmea0183.Identification.Equals(System.Object).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Nmea0183.Identification.GetHashCode.

iot-api-docs/xml/Iot.Device.Nmea0183/QuerySentence.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Nmea0183.QuerySentence.ToString.

iot-api-docs/xml/Iot.Device.Nmea0183/Raw8BitEncoding.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetByteCount(System.Char[],System.Int32,System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetByteCount(System.Char[],System.Int32,System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetBytes(System.Char[],System.Int32,System.Int32,System.Byte[],System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetBytes(System.Char[],System.Int32,System.Int32,System.Byte[],System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetCharCount(System.Byte[],System.Int32,System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetCharCount(System.Byte[],System.Int32,System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetChars(System.Byte[],System.Int32,System.Int32,System.Char[],System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetChars(System.Byte[],System.Int32,System.Int32,System.Char[],System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetMaxByteCount(System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetMaxByteCount(System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetMaxCharCount(System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetMaxCharCount(System.Int32).

iot-api-docs/xml/Iot.Device.Nmea0183/TalkerSentence.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Nmea0183.TalkerSentence.ToString.

iot-api-docs/xml/Iot.Device.Pn5180/Pn5180.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Seesaw/Seesaw.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Tlc1543/Channel.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'remarks' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

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

File
Status
Preview URL
Details

iot-api-docs/xml/Iot.Device.Arduino/SupportedMode.xml
:warning:Warning
View
Details

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+I2cAdapter.xml
:warning:Warning
View
Details

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+SpiAdapter.xml
:warning:Warning
View
Details

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixI2c.xml
:warning:Warning
View
Details

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixSysFs.xml
:warning:Warning
View
Details

iot-api-docs/xml/System.Device.Gpio/PinValue.xml
:warning:Warning
View
Details

iot-api-docs/xml/Iot.Device.Amg88xx/Amg88xx.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Arduino/SupportedPinConfiguration.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Bmxx80.PowerMode/Bme680PowerMode.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Bno055/Info.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.BrickPi3.Models/BrickPiInfo.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Common/GeographicPosition.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Common/WeatherHelper.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.HardwareMonitor/OpenHardwareMonitor+Sensor.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Max7219/MatrixGraphics.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Max7219/Max7219.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Mcp23xxx/BankStyle.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Mcp23xxx/Register.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Nmea0183/DeviationPoint.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Nmea0183/Identification.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Nmea0183/QuerySentence.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Nmea0183/Raw8BitEncoding.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Nmea0183/TalkerSentence.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Pn5180/Pn5180.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Seesaw/Seesaw.xml
:bulb:Suggestion
View
Details

iot-api-docs/xml/Iot.Device.Tlc1543/Channel.xml
:bulb:Suggestion
View
Details

iot-api-docs/docfx.json
:white_check_mark:Succeeded

iot-api-docs/missing_apis.yml
:white_check_mark:Succeeded

iot-api-docs/xml/BuildHat.Models/BuildHatInformation.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/BuildHat.Models/LedMode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/FrameworksIndex/iot-dotnet-2.0.xml
:white_check_mark:Succeeded

iot-api-docs/xml/FrameworksIndex/iot-dotnet-2.1.xml
:white_check_mark:Succeeded

iot-api-docs/xml/IoT.Device.Pn532/BaudRate.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/DiagnoseMode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/ErrorCode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/FirmwareVersion.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/OperatingMode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/ParametersFlags.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/Pn532.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/Port3.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/Port7.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/RFConfigurationTimeout.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/RfConfigurationMode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/SecurityAccessModuleMode.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/SfrRegister.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/VersionSupported.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Pn532/WakeUpEnable.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Tsl256x/Channel.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Tsl256x/Gain.xml
:white_check_mark:Succeeded
View

iot-api-docs/xml/IoT.Device.Tsl256x/IntegrationTime.xml
:white_check_mark:Succeeded
View

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

iot-api-docs/xml/Iot.Device.Arduino/SupportedMode.xml

Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.AnalogInput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.AnalogInput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Dht but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Dht but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.DigitalInput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.DigitalInput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.DigitalOutput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.DigitalOutput but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Encoder but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Encoder but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.I2c but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.I2c but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.InputPullup but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.InputPullup but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.OneWire but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.OneWire but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Pwm but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Pwm but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Serial but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Serial but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Servo but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Servo but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Shift but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Shift but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Sonar but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Sonar but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Spi but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Spi but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Stepper but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Stepper but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.4 exists in member Iot.Device.Arduino.SupportedMode.Tone but can't be found in parent type.
Line 0, Column 0: [Warning: ECMA2Yaml_ExtraMonikerFoundInMember] Moniker iot-dotnet-1.5 exists in member Iot.Device.Arduino.SupportedMode.Tone but can't be found in parent type.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Arduino.SupportedMode.ToString.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+I2cAdapter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Mcp23xxx+SpiAdapter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixI2c.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/Iot.Device.SenseHat/SenseHatLedMatrixSysFs.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Dispose'.

iot-api-docs/xml/System.Device.Gpio/PinValue.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.IEquatable`1.GetHashCode'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.IEquatable`1.GetHashCode'.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: System.Device.Gpio.PinValue.GetHashCode.

iot-api-docs/xml/Iot.Device.Amg88xx/Amg88xx.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Arduino/SupportedPinConfiguration.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Arduino.SupportedPinConfiguration.ToString.

iot-api-docs/xml/Iot.Device.Bmxx80.PowerMode/Bme680PowerMode.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Bno055/Info.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.BrickPi3.Models/BrickPiInfo.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Common/GeographicPosition.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Common.GeographicPosition.GetHashCode.

iot-api-docs/xml/Iot.Device.Common/WeatherHelper.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'example' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'example' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.HardwareMonitor/OpenHardwareMonitor+Sensor.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.HardwareMonitor.OpenHardwareMonitor.Sensor.ToString.

iot-api-docs/xml/Iot.Device.Max7219/MatrixGraphics.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Max7219/Max7219.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Mcp23xxx/BankStyle.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Mcp23xxx/Register.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

iot-api-docs/xml/Iot.Device.Nmea0183/DeviationPoint.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Equals(System.Object) for uid: Iot.Device.Nmea0183.DeviationPoint.Equals(System.Object).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Nmea0183.DeviationPoint.GetHashCode.

iot-api-docs/xml/Iot.Device.Nmea0183/Identification.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Equals(System.Object) for uid: Iot.Device.Nmea0183.Identification.Equals(System.Object).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetHashCode for uid: Iot.Device.Nmea0183.Identification.GetHashCode.

iot-api-docs/xml/Iot.Device.Nmea0183/QuerySentence.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Nmea0183.QuerySentence.ToString.

iot-api-docs/xml/Iot.Device.Nmea0183/Raw8BitEncoding.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetByteCount(System.Char[],System.Int32,System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetByteCount(System.Char[],System.Int32,System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetBytes(System.Char[],System.Int32,System.Int32,System.Byte[],System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetBytes(System.Char[],System.Int32,System.Int32,System.Byte[],System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetCharCount(System.Byte[],System.Int32,System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetCharCount(System.Byte[],System.Int32,System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetChars(System.Byte[],System.Int32,System.Int32,System.Char[],System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetChars(System.Byte[],System.Int32,System.Int32,System.Char[],System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetMaxByteCount(System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetMaxByteCount(System.Int32).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:GetMaxCharCount(System.Int32) for uid: Iot.Device.Nmea0183.Raw8BitEncoding.GetMaxCharCount(System.Int32).

iot-api-docs/xml/Iot.Device.Nmea0183/TalkerSentence.xml

Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:ToString for uid: Iot.Device.Nmea0183.TalkerSentence.ToString.

iot-api-docs/xml/Iot.Device.Pn5180/Pn5180.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'see' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Seesaw/Seesaw.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'param' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

iot-api-docs/xml/Iot.Device.Tlc1543/Channel.xml

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'remarks' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

Looked at the smoke-test test site as well as some files and things look good. Thanks so much @v-alje


(doc) Replace Gitter refs with Community Chat

As we have replaced Gitter with Discord the links have to be updated. Rather than specifying Discord, I've used a generic Community Chat term. This means, if we ever change away from Discord in future, we don't have to update the docs again. The link being used is a short url we can also update outside of the docs. Gitter rooms will be hidden so any references to chats have also been removed.

Gitter rooms will be hidden so any references to chats have also been removed.

So archives of the gitter rooms will not be publicly available?
There is at least one issue on chocolatey/choco where there is no text in the issue itself, it just links to a gitter chat. So if the archives will be made private, any issues linking to gitter should be updated to include the information in the issue itself.
https://github.com/chocolatey/choco/issues?&q="gitter"

@pauby your changes have been merged, thanks for your contribution 👍

This PR is merged but I wanted to update here as this is where it was mentioned.
I've gone through the issues that have gitter.im links and taken a screenshot of the chats and added it to the issues.

Perfect, thanks for completing that @pauby
Also, if anyone wants a personal archive of the gitter rooms you are in, this worked for me:
https://github.com/minrk/archive-gitter


Add files via upload

add domain

@Malvin222 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Update for origin kubernetes rebase

Also adds the SHAPING capability to the plugin quiet the kubernetes
warning when shaping annotations are present and openshift-sdn handles
them.

(These changes were already made in origin; this is essentially just a backport to the openshift-sdn tree.)


Video freezes on ad

Describe the bug
The ad loads in and the entire youtube page begins flickering. It will not let me watch the ad nor the video.
To Reproduce
Steps to reproduce the behavior:

Go to Youtube (with "Remove Adblock Thing" on)
Click on a video that has advertisements
The video will not play

Expected behavior
The advertisement will pause. The webpage will flicker and the "play" button will not work. The video is stuck on second 1 of the ad. Refreshing the page sometimes works.
Screenshots
Video clip included
Desktop (please complete the following information):

OS: Windows 10
Browser: Brave
Version 1.61.116

https://github.com/TheRealJoelmatic/RemoveAdblockThing/assets/156489897/d8322fbe-d429-44d1-baa1-d8c76fe7fdf2

I've seen the same behaviour, which I think started with v3.1.
However, it only happens occasionally, affecting maybe 10% of videos and always when blocking the ads at the start of a video.
Firefox 115.6.0
Firefox ESR
Win 7.

I'm having the same issue with my Imac.
MacOS 11.7.10
Browser Chrome Version 120.0.6099.216

Fixed in 3.2


How to convert mxnet to tf checkpoint?

How to convert mxnet to tf checkpoint?

I know how to convert mxnet parameter to tf serving format, but i want to convert it to tf checkpoint or pb format, thanks.


[Bug]: Starting a flow with an external id provider doesn't return the intentId.

Preflight Checklist

[x] I could not find a solution in the documentation, the existing issues or discussions
[x] I have joined the ZITADEL chat

Environment
Self-hosted
Version
2.58.1
Database
PostgreSQL
Database Version
16
Describe the problem caused by this bug
When I start a flow using this endpoint https://$CUSTOM-DOMAIN/v2/idp_intents the response doesn't contain the IdpIntent object at all, how can I get the data from the auth provider in this flow? I'm using Microsoft for external login.
This is the response:

To reproduce
Start a flow using this endpoint https://$CUSTOM-DOMAIN/v2/idp_intents and that's it.
Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

Issue already solved in https://github.com/zitadel/zitadel/issues/6922


Create an article about NIS2

NIS2
The NIS2 Directive (Directive (EU) 2022/2555).

1. Category

1.1. Chapter I: General Provisions

1.1.1. Article 1: Subject Matter and Objectives
1.1.2. Article 2: Scope
1.1.3. Article 3: Definitions

1.2. Chapter II: National Cybersecurity Frameworks

1.2.1. Article 4: National Cybersecurity Strategies
1.2.2. Article 5: Governance
1.2.3. Article 6: Role of National Authorities and Single Points of Contact
1.2.4. Article 7: Cybersecurity Strategies Implementation and Monitoring

1.3. Chapter III: Risk Management and Incident Reporting

1.3.1. Article 8: Risk Management Measures
1.3.2. Article 9: Reporting Obligations
1.3.3. Article 10: Handling of Incidents
1.3.4. Article 11: Security Requirements for Entities
1.3.5. Article 12: Notification Process

1.4. Chapter IV: Cooperation and Information Exchange

1.4.1. Article 13: Cooperation Group
1.4.2. Article 14: CSIRTs Network
1.4.3. Article 15: ENISA Support
1.4.4. Article 16: Cooperation at Union Level

1.5. Chapter V: Supervision and Enforcement

1.5.1. Article 17: Supervisory Authorities
1.5.2. Article 18: Powers of the Supervisory Authorities
1.5.3. Article 19: Enforcement Measures
1.5.4. Article 20: Penalties and Administrative Sanctions

1.6. Chapter VI: Final Provisions

1.6.1. Article 21: Transitional Measures
1.6.2. Article 22: Review and Reporting
1.6.3. Article 23: Repeal of Directive (EU) 2016/1148 (NIS Directive)
1.6.4. Article 24: Entry into Force and Application

1. Category
1.1. Chapter I: General Provisions
Chapter I sets the foundation for the Directive by outlining its purpose, scope, and key definitions. It establishes the Directive's aim to enhance cybersecurity across the EU by setting common standards and measures. The definitions provided are crucial for ensuring a unified understanding of terms and concepts used throughout the Directive, ensuring consistency in implementation across Member States.
1.1.1. Article 1: Subject Matter and Objectives
Article 1 outlines the primary aim of the Directive, which is to achieve a high common level of cybersecurity across the European Union. It details the framework for enhancing the overall security and resilience of network and information systems.
1.1.2. Article 2: Scope
Defines the entities to which the Directive applies, including both public and private sectors, and specifies the criteria for inclusion, such as medium-sized enterprises and certain critical sectors regardless of size.
1.1.3. Article 3: Definitions
Provides precise definitions for key terms used throughout the Directive, such as cybersecurity, incident, network and information systems, and critical entities.
1.2. Chapter II: National Cybersecurity Frameworks
Chapter II focuses on the internal frameworks that Member States must establish to enhance cybersecurity. It mandates the development of national cybersecurity strategies, specifying governance structures and the roles of various national authorities. The chapter emphasizes the need for coordinated efforts and clear responsibilities to manage cybersecurity risks effectively. The strategies should include measures for risk management, incident reporting, and continuous monitoring to adapt to evolving cyber threats.
1.2.1. Article 4: National Cybersecurity Strategies
Mandates Member States to develop, implement, and maintain a national cybersecurity strategy. This strategy must address risk management, incident reporting, and the roles and responsibilities of different stakeholders.
1.2.2. Article 5: Governance
Describes the establishment of governance structures within Member States, ensuring effective coordination and communication between various national authorities responsible for cybersecurity.
1.2.3. Article 6: Role of National Authorities and Single Points of Contact
Obliges Member States to designate competent authorities and single points of contact (SPOCs) for cybersecurity to streamline efforts and ensure efficient incident handling and information sharing.
1.2.4. Article 7: Cybersecurity Strategies Implementation and Monitoring
Focuses on the implementation and continuous monitoring of national cybersecurity strategies, ensuring they remain effective and adapt to evolving cyber threats.
1.3. Chapter III: Risk Management and Incident Reporting
Chapter III is dedicated to the operational aspects of cybersecurity management. It prescribes detailed requirements for risk management and incident reporting for entities. These measures are designed to ensure that entities are proactive in identifying and mitigating cybersecurity risks. Additionally, it establishes protocols for reporting significant incidents, thereby facilitating a coordinated and timely response to cyber threats. The chapter also outlines specific security requirements that entities must implement to protect their networks and information systems.
1.3.1. Article 8: Risk Management Measures
Requires entities to adopt and implement comprehensive risk management practices to mitigate potential cybersecurity threats and vulnerabilities.
1.3.2. Article 9: Reporting Obligations
Outlines the obligations for entities to report significant incidents to the relevant national authorities promptly. This aims to facilitate a rapid response and limit the impact of such incidents.
1.3.3. Article 10: Handling of Incidents
Details the procedures for managing reported incidents, including investigation, remediation, and communication strategies to inform affected stakeholders and the public when necessary.
1.3.4. Article 11: Security Requirements for Entities
Specifies the security measures that entities must implement, including technical and organizational measures to protect network and information systems.
1.3.5. Article 12: Notification Process
Defines the process for notifying the relevant authorities about incidents, including the required content of such notifications and the timelines for reporting.
1.4. Chapter IV: Cooperation and Information Exchange
Chapter IV highlights the importance of collaboration at both national and Union levels. It establishes the Cooperation Group and the CSIRTs network to facilitate strategic and operational cooperation, respectively. ENISA's role is emphasized in providing support and guidelines, maintaining a vulnerability registry, and promoting information sharing. The chapter aims to enhance collective cybersecurity resilience through coordinated actions and shared knowledge among Member States and EU institutions.
1.4.1. Article 13: Cooperation Group
Establishes a Cooperation Group to facilitate strategic cooperation and information exchange among Member States and to support the implementation of the Directive.
1.4.2. Article 14: CSIRTs Network
Creates a network of Computer Security Incident Response Teams (CSIRTs) to enhance operational cooperation, information sharing, and coordinated responses to cross-border cybersecurity incidents.
1.4.3. Article 15: ENISA Support
Allocates significant responsibilities to the European Union Agency for Cybersecurity (ENISA), including providing support to Member States, developing guidelines, and maintaining a European vulnerability registry.
1.4.4. Article 16: Cooperation at Union Level
Encourages collaboration between Member States and Union institutions, agencies, and bodies to foster a harmonized approach to cybersecurity across the EU.
1.5. Chapter V: Supervision and Enforcement
Chapter V sets out the mechanisms for ensuring compliance with the Directive. It requires Member States to establish supervisory authorities with the power to monitor, audit, and enforce the Directive's requirements. The chapter details the enforcement measures, including penalties and sanctions, that can be applied to entities that fail to comply. This regulatory framework is designed to ensure that cybersecurity measures are effectively implemented and maintained across the EU.
1.5.1. Article 17: Supervisory Authorities
Mandates the establishment of supervisory authorities within Member States responsible for monitoring and enforcing compliance with the Directive.
1.5.2. Article 18: Powers of the Supervisory Authorities
Details the powers granted to supervisory authorities, including the ability to conduct audits, inspections, and impose penalties for non-compliance.
1.5.3. Article 19: Enforcement Measures
Describes the enforcement measures available to supervisory authorities to ensure adherence to the Directive's requirements, such as fines, sanctions, and corrective actions.
1.5.4. Article 20: Penalties and Administrative Sanctions
Outlines the penalties and administrative sanctions that can be imposed on entities for breaches of the Directive, ensuring a deterrent effect and promoting compliance.
1.6. Chapter VI: Final Provisions
The final chapter includes transitional measures for the smooth implementation of the Directive, guidelines for reviewing and reporting on its effectiveness, and the formal repeal of the previous NIS Directive. It also specifies the timeline for the Directive's entry into force and application, providing Member States with a clear schedule for compliance. This chapter ensures that the transition to the new legal framework is orderly and that the Directive remains adaptable and responsive to future cybersecurity challenges.
1.6.1. Article 21: Transitional Measures
Provides guidance on the transitional measures Member States should adopt to ensure a smooth implementation of the Directive.
1.6.2. Article 22: Review and Reporting
Requires regular review and reporting on the implementation and effectiveness of the Directive, ensuring it remains relevant and effective in addressing cybersecurity challenges.
1.6.3. Article 23: Repeal of Directive (EU) 2016/1148 (NIS Directive)
Formally repeals the previous NIS Directive, establishing NIS2 as the new legal framework for cybersecurity in the EU.
1.6.4. Article 24: Entry into Force and Application
Specifies the date of entry into force of the Directive and its application timeline, providing Member States with a clear implementation schedule.

The NIS2 Directive aims to significantly enhance cybersecurity across the European Union by updating and expanding the original NIS Directive. The directive introduces new measures and extends its scope to address evolving cyber threats. Below is a detailed list of the chapters and articles of the directive, including in-depth descriptions of each chapter's focus and the specific articles within them.
Chapter I: General Provisions
This chapter sets the stage for the directive, outlining its purpose, scope, and key definitions. It provides the foundational framework for all subsequent chapters.
Article 1: Subject matter
Defines the primary objective of the directive: to achieve a high common level of cybersecurity across the EU by improving the security of network and information systems【14†source】【16†source】.
Article 2: Scope
Expands the directive’s applicability to include more sectors, such as telecommunications, social media platforms, and food production, reflecting the growing importance of these areas in national and economic security【15†source】.
Article 3: Essential and important entities
Categorizes entities into "essential" and "important," with essential entities including critical infrastructure sectors like energy and healthcare, and important entities covering areas like food production and digital services. This classification determines the level of regulatory obligations【14†source】【16†source】.
Article 4: Sector-specific Union legal acts
Addresses how the NIS2 Directive interacts with other sector-specific EU regulations to ensure coherence and avoid regulatory overlap【16†source】.
Article 5: Minimum harmonisation
Sets baseline cybersecurity requirements that member states must meet or exceed, ensuring a consistent approach across the EU【15†source】.
Article 6: Definitions
Provides clear definitions for key terms used throughout the directive, ensuring uniform understanding and implementation【14†source】.
Chapter II: National Frameworks on Cybersecurity
This chapter mandates the creation and implementation of robust national cybersecurity frameworks by member states.
Article 7: National cybersecurity strategy
Requires each member state to develop and adopt a comprehensive national cybersecurity strategy that aligns with the directive's goals【16†source】.
Article 8: Competent authorities and single points of contact
Mandates the designation of national authorities responsible for overseeing the implementation of the directive, as well as single points of contact for coordination【14†source】.
Article 9: National cyber crisis management frameworks
Establishes frameworks for managing cyber crises at the national level, ensuring preparedness and coordinated responses【15†source】.
Article 10: Computer security incident response teams (CSIRTs)
Specifies the formation and roles of CSIRTs, which are essential for responding to cybersecurity incidents effectively【16†source】.
Article 11: Requirements, technical capabilities and tasks of CSIRTs
Details the technical capabilities and specific tasks that CSIRTs must possess and perform to ensure robust incident response capabilities【15†source】.
Chapter III: Cybersecurity Risk Management and Reporting Obligations
Focuses on mandatory risk management practices and stringent reporting requirements for cybersecurity incidents.
Article 12: Coordinated vulnerability disclosure and a European vulnerability database
Encourages the coordinated disclosure of vulnerabilities and establishes a central database to manage and share information on vulnerabilities【16†source】.
Article 13: Cooperation at national level
Promotes cooperation among national authorities within member states to enhance cybersecurity measures【14†source】.
Article 14: Cooperation Group
Forms a cooperation group to facilitate strategic collaboration and information exchange between member states【15†source】.
Article 15: CSIRTs network
Creates a network of CSIRTs to improve cooperation and coordination across the EU【16†source】.
Article 16: European cyber crisis liaison organisation network (EU-CyCLONe)
Establishes EU-CyCLONe to manage large-scale EU-wide cybersecurity incidents, enhancing coordination during crises【14†source】【15†source】.
Article 17: International cooperation
Promotes international partnerships and cooperation on cybersecurity issues to address global cyber threats【15†source】.
Article 18: Report on the state of cybersecurity in the Union
Requires an annual report on the state of cybersecurity in the EU, providing transparency and accountability【16†source】.
Article 19: Peer reviews
Introduces peer reviews to enhance collaboration and share best practices among member states【14†source】.
Article 20: Governance
Defines governance structures for the implementation of the directive, ensuring effective oversight and management【16†source】.
Article 21: Cybersecurity risk-management measures
Mandates specific cybersecurity risk management measures for covered entities, including risk assessments and security policies【15†source】.
Article 22: Union level coordinated security risk assessments of critical supply chains
Calls for coordinated security risk assessments of critical supply chains at the EU level to enhance resilience【14†source】.
Article 23: Reporting obligations
Sets out stringent reporting obligations for cybersecurity incidents, requiring initial notifications within 24 hours and detailed reports within 72 hours【15†source】.
Article 24: Use of European cybersecurity certification schemes
Promotes the use of European cybersecurity certification schemes to ensure the security and reliability of products and services【16†source】.
Article 25: Standardisation
Encourages the development and adoption of standardized cybersecurity practices across the EU【15†source】.
Article 26: Jurisdiction and territoriality
Clarifies the jurisdictional and territorial scope of the directive, ensuring clear applicability【16†source】.
Article 27: Registry of entities
Requires the registration of entities covered by the directive, providing oversight and facilitating coordination【15†source】.
Article 28: Database of domain name registration data
Establishes a database for domain name registration data to improve transparency and accountability in digital operations【16†source】.
Article 29: Cybersecurity information-sharing arrangements
Facilitates information-sharing arrangements to enhance cybersecurity across the EU【14†source】.
Article 30: Voluntary notification of relevant information
Allows for the voluntary notification of relevant cybersecurity information, encouraging proactive disclosure and collaboration【15†source】.
Chapter IV: Supervision and Enforcement
Details the supervisory and enforcement mechanisms to ensure compliance with the directive, including penalties for non-compliance.
Article 31: General aspects concerning supervision and enforcement
Outlines general principles for supervising and enforcing the directive, ensuring consistent application across member states【14†source】.
Article 32: Supervisory and enforcement measures in relation to essential entities
Specifies the supervisory and enforcement measures applicable to essential entities, ensuring they meet the highest standards of cybersecurity【15†source】.
Article 33: Supervisory and enforcement measures in relation to important entities
Specifies the measures for important entities, providing a tiered approach to supervision and enforcement【16†source】.
Article 34: General conditions for imposing administrative fines on essential and important entities
Sets conditions for imposing fines for non-compliance, including criteria for determining the severity of penalties【14†source】.
Article 35: Infringements entailing a personal data breach
Addresses breaches involving personal data, ensuring that appropriate measures are taken to protect individuals' privacy【15†source】.
Article 36: Penalties
Details the penalties for non-compliance, which can include fines up to €10 million or 2% of global annual turnover for essential entities【16†source】.
Article 37: Mutual assistance
Promotes mutual assistance among member states to ensure effective enforcement of the directive【14†source】.
Chapter V: Final Provisions
Covers procedural and administrative aspects of the directive’s implementation and future amendments.
Article 38: Exercise of the delegation
Details the delegation of powers for the implementation of the directive, ensuring that appropriate authorities can enforce the measures【15†source】.
Article 39: Committee procedure
Explains the procedure for adopting implementing acts, ensuring that changes can be made efficiently and transparently【16†source】.
Article 40: Review
Mandates periodic review of the directive’s implementation and effectiveness to ensure it remains relevant and effective【14†source】.
Article 41: Transposition
Sets deadlines for member states to transpose the directive into national law, ensuring timely implementation【15†source】.
Article 42: Amendment of Regulation (EU) No 910/2014
Amends existing regulations to align with the NIS2 Directive, ensuring consistency across related legislative frameworks【16†source】.
Article 43: Amendment of Directive (EU) 2018/1972
Amends other directives to ensure coherence with NIS2, avoiding regulatory conflicts【14†source】.
Article 44: Repeal
Repeals the original NIS Directive, replacing it with the updated NIS2 measures【15†source】.
Article 45: Entry into force
Specifies the date when the directive comes into effect, allowing member states and entities to prepare for compliance【16†source】.
Article 46: Addressees
Identifies the entities addressed by the directive, ensuring clarity on who is subject to its provisions【14†source】.
For more detailed information, you can refer to the full text of the NIS2 Directive on the official NIS2 Directive information site【14†source】【15†source】【16†source】.


[docs] GettingStarted: Add a warning about spaces in the absolute path

Add a warning about spaces in the absolute path to the Getting Started document

@swift-ci please smoke test

@swift-ci Please test Windows Platform

@swift-ci Please test Windows Platform


Broken link in setup readme

In setup/README.md the link to “AU plugins” is broken.

Thanks for the report!
This has been corrected here: https://github.com/chocolatey/chocolatey-packages-template/commit/e4541232792a5883b966dc2787282e1774f8da88


fix: route limit to subdomains does not work

Description
Fixes  #5959
// Limit to any sub-domain
$routes->add('from', 'to', ['subdomain' => '*']); // not work

Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

Not sure if this will work correctly if the domain name is a first level domain.
The first-level domain can be used in internal (corporate) networks.

@iRedds What do you mean by "first level domain"?
Example?

A local resource can have a mycompany domain.
Then the behavior will be incorrect for the api.mycompany subdomain.

It seems Brand top-level domains.
https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Brand_top-level_domains
This method is not perfect from the beginning.
https://github.com/codeigniter4/CodeIgniter4/blob/38d5c109981bb51dc3ba2309ca6152c49fc07f28/system/Router/RouteCollection.php#L1327-L1328

Not perfect and not correct are two different cases.
I think subdomain parsing should be based on app.baseURL

Tomorrow will show my solution, I have been using for several years. Because I'm leaving today

`        /**
* domainFilter()
*
*
* @param mixed $allowed_domain - allowed domain format ['example.net','subdomain.example.com'] , don't use http://
* @param mixed $domain_to_check - input domain to check e.g. www.www.www.www.a1.g.h.r.r.e.e.e.e.e.e.d.subdomain.example.com
*
* @return array associates
*
*               if not found:
*    ['matches'] type (int) == 0
*    [0] == empty array()
*
*               if checked:
*
*    ['matches'] type (int) == 1
*    [0][0] => www. - prefix
*    [0][1] => a1.g.h.r.r.e.e.e.e.e.e.d - subdomain or null if not check
*    [0][2] => subdomain.example.com - domain
*
*
*
*/
    function domainFilter(array $allowed_domain, string $domain_to_check):array {

        $result = [];//only for IDE (warning undefined variable)

        $allowed_domain = implode('|', $allowed_domain);

        $result['matches'] = preg_match('/^(?:(w{3})\.)*(?:((?:[a-z0-9\-\_]+\.)*[a-z0-9\-\_]+)\.)*('.$allowed_domain.')$/', $domain_to_check, $result[0]);

        //remove first element from array, but first array return input param $allowed_domain
        array_shift($result[0]);

        return $result;
    }

    d(
        domainFilter(['crazy.sub.domain.com', 'ci.loc'], 'www.usersubdomain.crazy.sub.domain.com')
    );

    d(
        domainFilter(['crazy.sub.domain.com', 'ci.loc'], 'aaa.bbb.usersubdomain.crazy.sub.domain.com')
    );`

link to source domain filter function
could be added Placeholders and Regular Expression to domain and subdomain

I believe this PR fixed the bug #5959. So this PR is done.
@iRedds The Bug with Brand top-level domains is another bug that exists already.
@szajens Thank you for sample code. Adding like that code is an enhancement. It is better to create another PR.
From the beginning, using $_SERVER['HTTP_HOST'] without validation is kind of vulnerability.
I think it is better to add hostname validation and logic that is more reliable to determine subdomains.
Contributions are welcome.

That's right, because someone can dynamically replace the host.
Powyższy kod eliminuje błąd związany z domenami najwyższego poziomu marki

@kenjis maybe you will create new PR,because my English no perfect 😁

Open to other enhancements and bugfixes, but I'm with kenjis that this addresses the issue at hand.


fix attempt (#4460)

Pull request opened by the merge tool on behalf of #4460

Merged in 3bea372696a0b16b860601ee2a947ed54d583e19


Update inference_rules.adoc

Addressing issue #3.

Is this already covered by 7.1 (trying to avoid repetition)?

Any other pre- and post-processing time is included in the wall-clock time for a run result.

If ^ requires clarification maybe provide an example based the discussion from #3?

WG agreed on the rule wording change.


Support for server rendered initial content

Hi,
Does the New Router supports state changes after initial server rendering?
Use case: Instead of keeping the user wait till all the scripts loaded*, I wanted to render some content in the ng-view/ng-viewport section, say 'Home' content. And once the complete SPA is bootstraped, and when user clicked different link which has different route, I want to override the 'Home' content with that route specific template. And, when user clicks 'Home' again, now I want the server rendered content to be shown. With old(?) router, it is not easy to do that without cashing the contents manually before the route change. This will also serves as partial solution for newly coined 'Isomorphic way' of building SPA (http://nerds.airbnb.com/isomorphic-javascript-future-web-apps/, http://augustl.com/blog/2014/jdk8_react_rendering_on_server/, http://berzniz.com/post/99158163051/isomorphic-javascript-angular-js-is-not-the). Partial in the sense, only index/home page will rendered by server and other routes will be shown/compiled by AngularJS. This way critical rendering can be achieved (https://developers.google.com/web/fundamentals/performance/critical-rendering-path/).
*Loading all scripts can be avoided once the new proposal for lazy loading is released: https://github.com/angular/angular.js/issues/11015.
https://github.com/angular/router/issues/152 seems similar issue to me.

Angular 1 does not have first-class support for server-side rendering, but there are some tools that add this capability. If any of the authors of this tool are interested in helping inform the design of the router, I'm happy to get their feedback.
Angular 2 is designed to split things apart so server side rendering is possible, but it's still up in the air whether it'll support it.
There are a few design considerations that make route config easily statically analyzable so that if server-side rendering is supported, it'll be easier to implement.
Regardless, this isn't something the router has control over – it's more a question of the templating system in Angular. I'm going to close this issue since it's really not actionable, but thanks for filing it. :)

I see your point.
But, even we couldn't cover end-to-end server side rendering (first rendering at server side for all routes), my suggestion is also about supporting server-side rendered main home/index page.
Ex: When user visits, http://angular.io, server will generate the complete homepage markup. Once index page is loaded, from then on regular SPA flow continues. If user visits directly any other route, let the normal route resolution after complete app is loaded.
This particular use case will also makes SEO friendly. Yeah, only homepage, where generally all other links and main/new information will be first published. Though Google started indexing JS apps, I m not sure about other search engines (but, I m little to not concerned about this). As long as Google sees my page without any issue, I m happy with that.
I've not gone through the New Router source yet, but to my guess, it'll be trivial to add support for this. How about something like this?
// a new 'index()' method proposal
$routeProvider.index('$root', { // I couldn't come up with better name for $path without any # or any route params - just the base href (or the domain)

    cache: true, // should router cache the server-rendered markup and re-use on next time user visits index route?

    redirectTo: '/' // redirect to this route when above 'cache' is set to false
})

With one to two event hooks, cached server-rendered markup can be kept in sync.
Currently I m achieving, first by using server rendering the initial index page (using JSP), and have another template which is almost identical to the contents for JSP page for next time route change to index page (ex: / --> /#/contact --> /).
Please let me know your thoughts.


Implement SegmentationMask in image_folder.rs (dataset::vision)

No open issues related to SegmentationMask.
Feature description
Complete the implementation of SegmentationMask in image_folder.rs.
Feature motivation
I'm currently working on a semantic segmentation example (simply UNet) and feel that implementing this feature will be a better solution than writing a new custom dataset.
(Optional) Suggest a Solution
It appears to have been started or bookmarked for future work.
/// Annotation type for different tasks.
#[derive(Debug, Clone, PartialEq)]
pub enum Annotation {
    /// Image-level label.
    Label(usize),
    /// Multiple image-level labels.
    MultiLabel(Vec<usize>),
    /// Object bounding boxes.
    BoundingBoxes(Vec<BoundingBox>),
    /// Segmentation mask.
    SegmentationMask(SegmentationMask),
}

Needed to complete:
/// Raw annotation types.
#[derive(Deserialize, Serialize, Debug, Clone)]
enum AnnotationRaw {
    Label(String),
    MultiLabel(Vec<String>),
    // TODO: bounding boxes and segmentation mask
}

/// Parse the image annotation to the corresponding type.
fn parse_image_annotation(
    annotation: &AnnotationRaw,
    classes: &HashMap<String, usize>,
) -> Annotation {
    // TODO: add support for other annotations
    // - [ ] Object bounding boxes
    // - [ ] Segmentation mask
    // For now, only image classification labels are supported.

    // Map class string to label id
    match annotation {
        AnnotationRaw::Label(name) => Annotation::Label(*classes.get(name).unwrap()),
        AnnotationRaw::MultiLabel(names) => Annotation::MultiLabel(
            names
                .iter()
                .map(|name| *classes.get(name).unwrap())
                .collect(),
        ),
    }
}

Need to test Mapper and Loader. Additional code may be needed as well.

Hi, I am new to open source, could you suggest how to proceed further?

@csking101 , I've just about completed the task and plan to submit a pull request in the next few days. To learn more about open source contributing, you could watch this ticket and follow the pull request (once requested). I'm sure the maintainers will have comments; then watch how the iterative process continues and ultimately leads to either good code being added to the project or a failure to meet expectations. Either way, it will be a learning experience. Thank you for joining the conversation and stay tuned!

@anthonytorlucci , thanks for the reply! I will be following how this issue and subsequent PR pans out. Thanks!

Linking a related ticket (image augmentation): https://github.com/tracel-ai/burn/issues/207

SegmentationMask is now implemented with the approval of https://github.com/tracel-ai/burn/pull/2426. Closing issue.


Bot crash after repeated deaths

Every once in a while when I am bullying my bot by killing it over and over again I get this error:

thread 'tokio-runtime-worker' panicked at C:\Users\user.cargo\git\checkouts\azalea-cdffe42e9d507c39\7fc31f9\azalea-physics\src\collision\world_collisions.rs:18:62:
called Option::unwrap() on a None value
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Encountered a panic in system azalea_physics::travel!
tick_run_schedule_loop error: channel closed
thread 'thread 'tokio-runtime-workertokio-runtime-worker' panicked at ' panicked at C:\Users\user.cargo\git\checkouts\azalea-cdffe42e9d507c39\7fc31f9\azalea-client\src\chat.rsC:\Users\user.cargo\git\checkouts\azalea-cdffe42e9d507c39\7fc31f9\azalea-client\src\chat.rs:thread ':174tokio-runtime-worker174:' panicked at :43C:\Users\user.cargo\git\checkouts\azalea-cdffe42e9d507c39\7fc31f9\azalea-client\src\chat.rs43:
::
called Result::unwrap() on an Err value: SendError { .. }174called Result::unwrap() on an Err value: SendError { .. }
:
43:
called Result::unwrap() on an Err value: SendError { .. }
error: process didn't exit successfully: target\debug\Bot.exe (exit code: 0xc000013a, STATUS_CONTROL_C_EXIT)

It seems to be about this line of code. I only get this sometimes when I kill my bot like 4+ times. It also, as seen in the error, crashes the program stopping the bot from running.

Similiar to https://github.com/azalea-rs/azalea/issues/151 but another point of failure. azalea often makes use of unwrap causing the whole program to panic.

Fixed in https://github.com/azalea-rs/azalea/commit/8808ecef9416edca9c77296742a533e848fba075


Backslash causing errors in Mac OS file paths.

Describe the bug
Files paths with backslashes ("\") causes errors in mac platform.
To Reproduce
Steps to reproduce the behavior:

Must be in mac os to reproduce, using a bash terminal.
Create any project, vite or CRA.
Input valid name
All other fields are optional.
Install.

Expected behavior
Expected behavior is that the project would be created with specified folders and paths.
Screenshots

Desktop (please complete the following information):

OS: Mac OS Ventura 13.1

Additional context

Hey, good catch!
I merge #47 , thank you for your first contribution on Reactirator. Any help like this is very appreciated.


⚠ ClamAV has degraded performance

In de7c497, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 206 ms

Resolved: ClamAV performance has improved in 0074a48.


Fix manager api to config from scheduler_config in swagger yaml

Signed-off-by: hanson.yj<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #317 (76dd47a) into main (d2f469e) will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #317      +/-   ##
==========================================
- Coverage   43.73%   43.61%   -0.12%
==========================================
  Files          53       53
  Lines        4205     4205
==========================================
- Hits         1839     1834       -5
- Misses       2126     2130       +4
- Partials      240      241       +1

Flag
Coverage Δ

unittests
43.61% <ø> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/net/iputils/ip_utils.go
61.22% <0.00%> (-4.09%)
:arrow_down:

client/daemon/peer/peertask_base.go
32.92% <0.00%> (-0.74%)
:arrow_down:


(BKR-458) add beaker notouch hypervisor

support for a 'noop' hypervisor that does no
configuration/validation/provision/cleanup/proxy-ing

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1417/
Test PASSed.


Code folding unit tests

Ref: #10893
Some simple tests for code-folding. Specifically it tests the following:

Gutter fold marks are rendered on startup
Folding code creates a folded region in editor
Expanding code clears the folded region in editor
Clearing the text marker on folded region expands it and updates the fold gutter
Folded lines have a folded (i.e., closed) marker in the gutter
Foldable lines have a foldable (i.e., open) marker in the gutter
Persistence of fold states work as expected - i.e., fold states are saved and restored when persistence is enabled
Persistence of fold states can be disabled
Minimum fold size is obeyed
Code folding can be disabled
Selecting text does not trigger fold marks when `makeSelectionsFoldable' is disabled
Selecting text triggers fold marks when `makeSelectionsFoldable' is enabled
Successively selecting text only triggers fold region for the last selection

@thehogfather Thanks for this PR! Really appreciate it. @abose @MarcelGerber @sprintr  Would you guys mind taking a look at this PR.

@thehogfather Sorry , missed this PR for the release.
Could you resolve the merge conflicts?

done.

Thanks @thehogfather .
verified all unit tests passing. Merging.


Allow complex fields without end tag

Fixes #41
This allows the code to gracefully handle complex fields when the <w:fldChar w:fldCharType="end"/> does not appear in the same paragraph node.

Ah, I see. So you are not looking to actually use those complex fields that span multiple paragraphs. It's more that the parsing fails to recognize them and then crashes. Is this right?

Exactly, the loop simply exits without finding anything since possible_field_node becomes nil but by that time the nil value was already added to the list. Since there is no nil check in ComplexField.initialize (and I don't think there should be) you get a NoMethod error.
I actually didn't think about trying to span multiple paragraphs but just looking at the code structure it seems that would be much more complex. I'm not entirely sure how you'd even go about that.

I think it's fine to ignore these fields for now and not try to parse them successfully. One could add another type of field that is a ComplexParagraphField to cover this case but that would need to make some assumptions on what the paragraph can contain. I assume one would remove both paragraph when replacing the fields.
I think ignoring is the right thing to do for now. I was wondering if we could not instantiate a field at all. Would it be possible to skip ComplexField.new in the case where we did not manage to recognize start and end tag? This way we don't have half-completed objects.

Reamed it per your suggestion.

And I don't know all of the circumstances of when a complex field would span multiple paragraphs to determine a better course of action other than forcing the field to end with paragraph.
From what documentation I read on WordML markup and just intuitively I don't think a complex (or any) field should be able to span multiple paragraphs. Which makes me think it's some odd corner case when dealing with old documents. The macro's file we use is from at least 2007, it's been edited since then but that might not fix all the glitches.

@senny I added a return statement and that didn't seem to affect anything.

@stadelmanma thanks 💛 . Released as 0.0.21


Make the repository root be the plugin directory

By simply moving all of the contents of Add Primitives to the repository root, a couple of things happen:

Installation is simplified to one step: git clone https://github.com/TheHX/add_primitives ~/.godot/plugins
Updating the plugin is simplified to: pushd ~/.godot/plugins/add_primitives; git pull; popd

I was thinking on doing this, by creating a better API to create primitives, that can be used both on editor and on runtime, and the plugin a separate part.
And this can make possible additions like UV mapping for all primitives and saving the primitive data(the primitive can be edited any time).

I've moved the plugin.cfg to the repository root and now is much more simpler to install and update the plugin. Thanks for the suggestion!


Binding to values derived from previous variables

The use-case for this one is a little difficult to explain, but let me try.
I'll start with some motivating examples where I think the resulting error is at least confusing.
--
Example (1) This first example compiles, but not into something meaningful.
(def compiles-query (dsl/parse-query []
                                     [[Temperature (= ?x temperature)]
                                      [ColdAndWindy (= ?t (+ temperature ?x))]]))

(-> (mk-session [compiles-query] :cache false)
    (insert (->Temperature 10 "MCI")
            (->ColdAndWindy 5 50))
    fire-rules
    (query compiles-query))

;= ()

The issue here lies in the extracted TestNode that is generated to try and deal with the non-hash-based join condition.
This TestNode fn looks something like [1]:
(clojure.core/fn [?__token__]

  (clojure.core/let [?x (get-in ?__token__ [:bindings :?x])

                     ?__gen__28586 (get-in ?__token__ [:bindings :?__gen__28586])

                     ?t (get-in ?__token__ [:bindings :?t])]

    (clojure.core/and (= ?t (+ ?__gen__28586 ?x)))))

Where ?__gen__28586 is bound to temperature of the :original-condition.
This doesn't make sense since ?t doesn't have a binding - it just comes out nil.
--
Example (2) This doesn't compile into a Rete tree, but the error reported may be less-than-ideal.

(def does-not-compile-query (dsl/parse-query []
                                             [[Temperature (= ?x temperature)]
                                              [ColdAndWindy (= ?t (inc ?x))]]))

(-> (mk-session [does-not-compile-query] :cache false)
                      (insert (->Temperature 10 "MCI")
                              (->ColdAndWindy 5 50))
                      fire-rules
                      (query does-not-compile-query))

;; CompilerException java.lang.RuntimeException: Unable to resolve symbol: ?x in this context, compiling:(etc)

To the caller, it looks like ?x should be resolvable.
--
Given these examples, I can see how the immediate response would be that it doesn't make sense to set up a join binding like this since it isn't really a "join".
This usage of a variable binding is more to create what I'd consider a "local binding" so that you can reuse some computation elsewhere in the rule.
Example (1) can be extended to demonstrate this idea (although there is no reason to do this particular example this way) :

(def compiles-query-revised (dsl/parse-query []
                                             [[Temperature (= ?x temperature)]
                                              [ColdAndWindy (= ?t (+ temperature ?x))]
                                              [:test (< 5 ?t)]]))

(-> (mk-session [compiles-query-revised] :cache false)
    (insert (->Temperature 10 "MCI")
            (->ColdAndWindy 5 50))
    fire-rules
    (query compiles-query-revised))

;= ()

The result of this is not intuitive from my perspective and I've seen other be confused by it.
Overall, I think this may be using the join bindings for an unintended use.  If that is the case, I'd vote in favor of putting some guards against these things in the form of throwing meaningful exceptions during Rete compilation.
On the other hand, there are times when it is "convenient" to store a derived calculation made in a LHS condition as a variable binding so that it can be tested in other subsequent conditions and used in the RHS.  It could aid performance to not repeat the same calculation in the LHS and RHS for example.
This works (and doesn't make much sense, but keeping it short):
(let [r (dsl/parse-rule [[Temperature (= ?one-more (inc temperature))]
                         [:test (< ?one-more 30)]]
                        (insert! (->Cold ?one-more)))
      q (dsl/parse-query []
                         [[?c <- Cold]])]
  (-> (mk-session [r q])
      (insert (->Temperature 10 "MCI"))
      fire-rules
      (query q)))

;= ({:?c #clara.rules.testfacts.Cold{:temperature 11}})

This can probably be abused as well as an aid to writing poorly designed rules.
--
I have been able to track down the internals in clara.rules.compiler that contribute to this issue.  I am just not sure on the direction we want to take with usages like this.
--
[1] Separate issue I'd probably like to think about: I had to add to the TestNode structure on the Rete tree in order to visually see what a TestNode condition looks like prior to eval.  I think it would aid in debugging and visualizing the Rete tree if the un-eval'ed form was preserved on a field of the TestNode.  Same goes for other join filter fn's etc.

I think we should support this...or at least I can't think of any reason not to that would make sense to an end user. It isn't a typical join/test scenario but I don't want to force users to be aware of that distinction.
I think the key pieces here are going to be:

Test nodes will need to be able to create new bindings, since in the first example we don't have all of the input necessary to compute the binding until we do the extracted test
To make that happen we'll probably have to fix issue #133, since tests would be able to create new bindings that could potentially be used by other rules.
We may have to enhance the extract-tests functionality from join nodes to make sure these use case are covered. (It might be working already but obviously this flow isn't unit tested.)

The trickiest algorithmic part is probably going to be sorting out the order we need to place the nodes so all of the bound variables are visible. But this is something we should solve anyway as described in issue #133.
I'll poke around this a bit more tomorrow.

Looking at this a bit more closely, I think the best approach will be to refactor the extract-tests type of functionality into a specialized join node that runs arbitrary tests and can create new bindings. So we might rename the current JoinNode to "HashJoinNode" and create an "ExpressionJoinNode" that can run arbitrary logic on the beta side of the network. HashJoinNode is more efficient, but a new ExpressionJoinNode will be used when needed to handle arbitrary expressions and relationships.
I think this simplifies things in the long run, since we will no longer need to artificially transform our network into join and test nodes, and it also simplifies ordering of the nodes as well.
This change won't be trivial, but it does drop some existing complexity and ensures our nodes can express any expression you could put in a rule.

I think that approach makes sense to me when going the direction of allowing bindings to be introduced in test nodes.  I agree it'd likely be simpler to reason about with less transformations.
Thanks for looking into this and taking the time to post your design thoughts out here along the way.

The above commit should fix this (at least, the examples included in the bug report now work and are included in a unit test.)
Most of the work done was in the refactoring for issue #133. The change in the above commit simply reuses the same binding logic used for fact matching to run arbitrary cross-fact expressions.
I'll plan on merging this to master soon unless some flaw presents itself. Mike, please let me know if you run into any problems with this logic.

Thanks!  I am working on testing this out and seeing how it works out.

I ran this against my existing codebase and it looks good.  It caught one misused bindings in a condition, but I don't consider that a bad thing.  There were some odd cases before where a condition was able to refer to a binding in one constraint that it introduced in a previous constraint.  I think it was just related to the test extraction before, but I never dug into it.  It was confusing that it worked then though and I generally advised against it.
So other than that, this looks good so far.  I scanned through the changes and it looks like it probably is a bit clearer what is going on now.  The only thing I haven't really looked to hard at is this topo sort, but I am going to check that out since it looks interesting.
This looks like quite a bit of a change.  Thanks for getting to it so fast!

Merged into master! I'm going to go ahead and close this now, but we can create new issues if anything related pops up.


[W5.11][T16-3]Lim Pin Juen

Each commands in help get separated by a new line
used COMMAND_WORD to introduce clear command

Very Good


[TASK]: Ensemble Simulate Plumbing

Pyciemss-service changes/any updates to node input/output/run function

no update seems required
Already outputting dataset ID
Already able to fun with pyciemss-service


IndexError: list index out of range from text_soup_cnn.findAll("div", {"class": "modContent feargreed"})[0]

The following error has been persisting last several months as I suppose the CNN web site introduced a new look to their site.
File "/Users/sungmc/Projects/Finance/Python For Finance/venv/lib/python3.8/site-packages/fear_greed_index/CNNFearAndGreedIndex.py", line 117, in _load_fear_and_greed
text_soup_cnn.findAll("div", {"class": "modContent feargreed"})[0]
IndexError: list index out of range

Sounds like you files this under the wrong project ;-)
This project: https://pypi.org/project/fear-and-greed/
Latest version v0.4 seems to work just fine:
Python 3.8.11 (default, Jul  3 2021, 17:53:42)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import fear_and_greed
>>> fear_and_greed.get()
FearGreedIndex(value=54.895697074, description='neutral', last_update=datetime.datetime(2022, 8, 13, 0, 0, 28, 767000, tzinfo=datetime.timezone.utc))
>>>

The project you are using sounds more like https://pypi.org/project/fear-greed-index/ hosted under https://github.com/DidierRLopes/fear-greed-index. It also contains the file from the stacktrace: https://github.com/DidierRLopes/fear-greed-index/blob/a411f24aa74847260f40a8ac46defa84e9986a18/fear_greed_index/CNNFearAndGreedIndex.py.
So please file your ticket under https://github.com/DidierRLopes/fear-greed-index, or use https://pypi.org/project/fear-and-greed/ which works fine (this code here)

Sounds even related to https://github.com/DidierRLopes/fear-greed-index/issues/5.


chore(deps): update dependency ember-cli to v5.11.0

This PR contains the following updates:

Package
Type
Update
Change

ember-cli (source)
devDependencies
minor
5.10.0 -> 5.11.0

Release Notes

ember-cli/ember-cli (ember-cli)
v5.11.0
Compare Source
Blueprint Changes

ember new diff
ember addon diff

Changelog

#10474 Improve dx when WelcomePage is present @ef4
#10475 Document WRITE_FIXTURES @kategengler
#10476 Bump content-tag to v2 @SergeAstapov

Thank you to all who took the time to contribute!

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: pnpm-lock.yaml
Scope: all 3 workspace projects
shoelace-ember                           |  WARN  deprecated<EMAIL_ADDRESS>Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 364, reused 0, downloaded 0, added 0
Progress: resolved 410, reused 0, downloaded 0, added 0
Progress: resolved 936, reused 0, downloaded 0, added 0
Progress: resolved 1328, reused 0, downloaded 0, added 0
Progress: resolved 1892, reused 0, downloaded 0, added 0
 WARN  34 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Progress: resolved 1895, reused 0, downloaded 0, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

shoelace-ember
└─┬ ember-source 5.10.2
  └─┬ ember-auto-import 2.7.4
    ├─┬ babel-loader 8.3.0
    │ └── ✕ missing peer webpack@>=2
    ├─┬ css-loader 5.2.7
    │ └── ✕ missing peer<EMAIL_ADDRESS>|| ^5.0.0"
    ├─┬ mini-css-extract-plugin 2.7.6
    │ └── ✕ missing peer<EMAIL_ADDRESS>    └─┬ style-loader 2.0.0
      └── ✕ missing peer<EMAIL_ADDRESS>|| ^5.0.0"
Peer dependencies that should be installed:
<EMAIL_ADDRESS><6.0.0-0"

hint: If you want peer dependencies to be automatically installed, add "auto-install-peers=true" to an .npmrc file at the root of your project.
hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.


Disable subscribers during tests

They are unwanted here and may interfere with tests
Inspired by the solution in #1659

I don't quite understand. This value is set to [] by qcodes/config/qcodesrc.json unless explicitly set in the test. What is the use case of this fixture?

Thanks for the offline explanation @jenshnielsen . We can merge that for now. I suggest we add an auto fixture based on https://github.com/QCoDeS/Qcodes/blob/a777a65e98a3086c156dbe640ce5a12cc0140867/qcodes/tests/test_config.py#L142 to make the state of the config independent of the local settings.