Migration mse

:warning: Validation status: warnings

File
Status
Preview URL
Details

his/core/00d0a93e-8d27-4720-901f-fcde013ca33c.md
:warning:Warning
View
Details

his/core/2a3a5d97-e269-4dc0-bca3-bf38a419f614.md
:warning:Warning
View
Details

his/core/3270-emulation-programmer-s-guide.md
:warning:Warning
View
Details

his/core/3270-emulation-programmer-s-reference.md
:warning:Warning
View
Details

his/core/3270-user-alerts.md
:warning:Warning
View
Details

his/core/5250-access.md
:warning:Warning
View
Details

his/core/57a9cb3d-e542-46ec-a7e4-f37e26643610.md
:warning:Warning
View
Details

his/core/7896641e-8f96-4317-9dc1-13cb983ee990.md
:warning:Warning
View
Details

his/core/a-sample-lua-communication-sequence.md
:warning:Warning
View
Details

his/core/accept-conversation-cpi-c.md
:warning:Warning
View
Details

his/core/accepting-incoming-attaches.md
:warning:Warning
View
Details

his/core/accessing-configuration-information.md
:warning:Warning
View
Details

his/core/activating-a-peer-connection-snadis.md
:warning:Warning
View
Details

his/core/additional-sync-point-return-codes.md
:warning:Warning
View
Details

his/core/administering-sections-of-his-wmi.md
:warning:Warning
View
Details

[his/core/administering-side-information].md](https://github.com/MicrosoftDocs/biztalk-docs/blob/migration_mse/his/core/administering-side-information].md)
:warning:Warning
View
Details

his/core/administration-and-management-programmer-s-reference.md
:warning:Warning
View
Details

his/core/allocate.md
:warning:Warning
View
Details

his/core/already-verified-support.md
:warning:Warning
View
Details

his/core/an-example-of-a-mapped-conversation-cpi-c.md
:warning:Warning
View
Details

his/core/an-example-of-a-mapped-conversation.md
:warning:Warning
View
Details

his/core/analysis-services.md
:warning:Warning
View
Details

his/core/appc-programmer-s-guide.md
:warning:Warning
View
Details

[his/core/appc-programmer-s-reference].md](https://github.com/MicrosoftDocs/biztalk-docs/blob/migration_mse/his/core/appc-programmer-s-reference].md)
:warning:Warning
View
Details

his/core/appc-programmer-s-security-guide.md
:warning:Warning
View
Details

his/core/appc-verb-summary.md
:warning:Warning
View
Details

his/core/application-cancel.md
:warning:Warning
View
Details

his/core/application-flags.md
:warning:Warning
View
Details

his/core/application-initiated-termination.md
:warning:Warning
View
Details

his/core/application-integration-programmer-s-reference.md
:warning:Warning
View
Details

his/core/application-integration-programmer’s-guide.md
:warning:Warning
View
Details

his/core/as-400-appc-printing.md
:warning:Warning
View
Details

his/core/as-400-connection-summary.md
:warning:Warning
View
Details

his/core/asynchronous-call-completion.md
:warning:Warning
View
Details

his/core/backout-verb-issued-locally.md
:warning:Warning
View
Details

his/core/backout-verb-issued-remotely.md
:warning:Warning
View
Details

his/core/base-dmod-and-snalink-entry-point-summary.md
:warning:Warning
View
Details

his/core/basic-and-mapped-conversations-compared-cpi-c.md
:warning:Warning
View
Details

his/core/basic-and-mapped-conversations-compared.md
:warning:Warning
View
Details

his/core/bind-checking.md
:warning:Warning
View
Details

his/core/biztalk-adapter-for-host-files-configuration.md
:warning:Warning
View
Details

his/core/bracket-initiation.md
:warning:Warning
View
Details

his/core/bracket-termination.md
:warning:Warning
View
Details

his/core/buffer-element-format-snadis.md
:warning:Warning
View
Details

his/core/buffer-element-format.md
:warning:Warning
View
Details

his/core/buffer-header-format-snadis.md
:warning:Warning
View
Details

his/core/buffer-header-format.md
:warning:Warning
View
Details

his/core/building-connection-strings.md
:warning:Warning
View
Details

his/core/changing-conversation-states-cpi-c.md
:warning:Warning
View
Details

his/core/changing-conversation-states.md
:warning:Warning
View
Details

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

his/core/00d0a93e-8d27-4720-901f-fcde013ca33c.md

Line 18: [Warning] Invalid file link:(~/Topic/Creating an Application for the BizTalk Adapter for Host Applications1.md).

his/core/2a3a5d97-e269-4dc0-bca3-bf38a419f614.md

Line 38: [Warning] Invalid file link:(~/Topic/Transaction Integrator Conversion Tool2.md).
Line 44: [Warning] Invalid file link:(~/Topic/IMS Connect2.md).
Line 56: [Warning] Invalid file link:(~/Topic/Working with TI Designer2.md).
Line 65: [Warning] Invalid file link:(~/Topic/IMS Connect2.md).

Line 19: [Warning] Invalid file link:(~/Topic/ConfigureLinkService2.md).
Line 20: [Warning] Invalid file link:(~/Topic/ConfigureLinkServiceEx2.md).
Line 21: [Warning] Invalid file link:(~/Topic/DisplayHelpInfo1.md).
Line 22: [Warning] Invalid file link:(~/Topic/RemoveLinkService2.md).
Line 23: [Warning] Invalid file link:(~/Topic/RemoveAllLinkServices2.md).
Line 41: [Warning] Invalid file link:(~/Topic/AddPerfmonCounters2.md).
Line 42: [Warning] Invalid file link:(~/Topic/bCreateService1.md).
Line 43: [Warning] Invalid file link:(~/Topic/bDeleteService2.md).
Line 44: [Warning] Invalid file link:(~/Topic/bStopService1.md).
Line 45: [Warning] Invalid file link:(~/Topic/CheckForExistingLinkService2.md).
Line 46: [Warning] Invalid file link:(~/Topic/ConvertHexStringToDWORD1.md).
Line 47: [Warning] Invalid file link:(~/Topic/ExtractNextParameter1.md).
Line 48: [Warning] Invalid file link:(~/Topic/fAddRegistryEntry1.md).
Line 49: [Warning] Invalid file link:(~/Topic/fCanWeAdministerRemoteBox2.md).
Line 50: [Warning] Invalid file link:(~/Topic/fConnectRegistry2.md).
Line 51: [Warning] Invalid file link:(~/Topic/fDisconnectRegistry2.md).
Line 52: [Warning] Invalid file link:(~/Topic/fFindAndReplaceString1.md).
Line 53: [Warning] Invalid file link:(~/Topic/fFindString2.md).
Line 54: [Warning] Invalid file link:(~/Topic/fFindStringInMultiSZ2.md).
Line 55: [Warning] Invalid file link:(~/Topic/fQueryRegistryValue1.md).
Line 56: [Warning] Invalid file link:(~/Topic/fRegistryKeyExists1.md).
Line 57: [Warning] Invalid file link:(~/Topic/fRemoveRegistryEntry2.md).
Line 58: [Warning] Invalid file link:(~/Topic/fRemoveRegistryValue1.md).
Line 59: [Warning] Invalid file link:(~/Topic/fStringCompare1.md).
Line 60: [Warning] Invalid file link:(~/Topic/LoadStringResource1.md).
Line 61: [Warning] Invalid file link:(~/Topic/ParseNextField1.md).
Line 62: [Warning] Invalid file link:(~/Topic/RemovePerfmonCounters2.md).

his/core/a-sample-lua-communication-sequence.md

Line 17: [Warning] Invalid file link:(~/core/media/lua1b.gif).
Line 22: [Warning] Invalid file link:(~/Topic/RUI_INIT2.md).
Line 36: [Warning] Invalid file link:(~/Topic/RUI_TERM1.md).
Line 39: [Warning] Invalid file link:(~/core/media/lua1c.gif).
Line 55: [Warning] Invalid file link:(~/Topic/SLI_RECEIVE1.md).
Line 55: [Warning] Invalid file link:(~/Topic/SLI_SEND1.md).
Line 57: [Warning] Invalid file link:(~/Topic/SLI_CLOSE2.md).

his/core/accept-conversation-cpi-c.md

Line 14: [Warning] Invalid file link:(~/Topic/Initial Conversation Characteristics2.md).

his/core/accepting-incoming-attaches.md

Line 16: [Warning] Invalid file link:(~/Topic/RECEIVE_ALLOCATE2.md).

his/core/accessing-configuration-information.md

Line 18: [Warning] Invalid file link:(~/Topic/SNAGetConfigValue1.md).
Line 19: [Warning] Invalid file link:(~/Topic/SNAGetSystemInfo2.md).
Line 23: [Warning] Invalid file link:(~/Topic/SNALinkInitialize1.md).

his/core/activating-a-peer-connection-snadis.md

Line 16: [Warning] Invalid file link:(~/Topic/Request-Open-Station1.md).
Line 16: [Warning] Invalid file link:(~/Topic/Send-XID2.md).
Line 26: [Warning] Invalid file link:(~/Topic/Open(LINK) Request2.md).

his/core/additional-sync-point-return-codes.md

Line 24: [Warning] Invalid file link:(~/Topic/CONFIRM1.md).
Line 26: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).
Line 28: [Warning] Invalid file link:(~/Topic/MC_PREPARE_TO_RECEIVE2.md).
Line 30: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_POST1.md).
Line 32: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 34: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_IMMEDIATE1.md).
Line 36: [Warning] Invalid file link:(~/Topic/MC_SEND_DATA2.md).
Line 38: [Warning] Invalid file link:(~/Topic/MC_SEND_ERROR1.md).
Line 40: [Warning] Invalid file link:(~/Topic/PREPARE_TO_RECEIVE1.md).
Line 42: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_POST2.md).
Line 44: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_WAIT1.md).
Line 46: [Warning] Invalid file link:(~/Topic/RECEIVE_IMMEDIATE2.md).
Line 48: [Warning] Invalid file link:(~/Topic/SEND_DATA2.md).
Line 50: [Warning] Invalid file link:(~/Topic/SEND_ERROR1.md).

his/core/administering-sections-of-his-wmi.md

Line 18: [Warning] Invalid file link:(~/Topic/SNA Provider WMI Programmer's%20Reference1.md).
Line 18: [Warning] Invalid file link:(~/Topic/SNA Trace Provider WMI Programmer’s Reference2.md).

[his/core/administering-side-information].md](https://github.com/MicrosoftDocs/biztalk-docs/blob/migration_mse/his/core/administering-side-information].md)

Line 19: [Warning] Invalid file link:(~/Topic/Delete_CPIC_Side_Information (CPI-C)1.md).
Line 22: [Warning] Invalid file link:(~/Topic/Extract_CPIC_Side_Information (CPI-C)2.md).
Line 25: [Warning] Invalid file link:(~/Topic/Set_CPIC_Side_Information (CPI-C)1.md).

his/core/administration-and-management-programmer-s-reference.md

Line 16: [Warning] Invalid file link:(~/Topic/Administration and Management Programmer's%20Guide1.md).
Line 18: [Warning] Invalid file link:(~/Topic/Administration and Management Samples.md).

his/core/allocate.md

Line 95: [Warning] Invalid file link:(~/Topic/Transaction Programs Overview2.md).

his/core/already-verified-support.md

Line 16: [Warning] Invalid file link:(~/Topic/SET_TP_PROPERTIES1.md).
Line 16: [Warning] Invalid file link:(~/Topic/TP_STARTED1.md).

his/core/an-example-of-a-mapped-conversation-cpi-c.md

Line 33: [Warning] Invalid file link:(~/Topic/Initialize_Conversation (CPI-C)2.md).
Line 35: [Warning] Invalid file link:(~/Topic/Allocate (CPI-C)1.md).
Line 37: [Warning] Invalid file link:(~/Topic/Accept_Conversation (CPI-C)1.md).
Line 40: [Warning] Invalid file link:(~/Topic/Send_Data (CPI-C)1.md).
Line 48: [Warning] Invalid file link:(~/Topic/Deallocate (CPI-C)2.md).
Line 48: [Warning] Invalid file link:(~/Topic/Flush (CPI-C)1.md).
Line 48: [Warning] Invalid file link:(~/Topic/Confirm (CPI-C)1.md).
Line 53: [Warning] Invalid file link:(~/Topic/Receive (CPI-C)1.md).
Line 56: [Warning] Invalid file link:(~/Topic/Deallocate (CPI-C)2.md).

his/core/an-example-of-a-mapped-conversation.md

Line 38: [Warning] Invalid file link:(~/Topic/TP_STARTED1.md).
Line 40: [Warning] Invalid file link:(~/Topic/MC_ALLOCATE1.md).
Line 42: [Warning] Invalid file link:(~/Topic/RECEIVE_ALLOCATE2.md).
Line 45: [Warning] Invalid file link:(~/Topic/MC_SEND_DATA2.md).
Line 51: [Warning] Invalid file link:(~/Topic/MC_FLUSH2.md).
Line 51: [Warning] Invalid file link:(~/Topic/MC_DEALLOCATE1.md).
Line 51: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).
Line 51: [Warning] Invalid file link:(~/Topic/MC_ALLOCATE1.md).
Line 54: [Warning] Invalid file link:(~/Topic/WinAsyncAPPC2.md).
Line 54: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 59: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_IMMEDIATE1.md).
Line 62: [Warning] Invalid file link:(~/Topic/MC_DEALLOCATE1.md).
Line 64: [Warning] Invalid file link:(~/Topic/TP_ENDED2.md).

his/core/analysis-services.md

Line 16: [Warning] Invalid file link:(~/Topic/Data Integration (Planning)2.md).
Line 16: [Warning] Invalid file link:(~/Topic/SQL Server Analysis Services (Troubleshooting)1.md).

his/core/appc-programmer-s-guide.md

Line 16: [Warning] Invalid file link:(~/Topic/APPC Programmer's%20Reference]2.md).
Line 18: [Warning] Invalid file link:(~/Topic/APPC Samples.md).

[his/core/appc-programmer-s-reference].md](https://github.com/MicrosoftDocs/biztalk-docs/blob/migration_mse/his/core/appc-programmer-s-reference].md)

Line 16: [Warning] Invalid file link:(~/Topic/APPC Programmer's%20Guide1.md).
Line 18: [Warning] Invalid file link:(~/Topic/APPC Samples.md).

his/core/appc-programmer-s-security-guide.md

Line 27: [Warning] Invalid file link:(~/Topic/ALLOCATE1.md).
Line 29: [Warning] Invalid file link:(~/Topic/MC_ALLOCATE1.md).
Line 31: [Warning] Invalid file link:(~/Topic/SEND_CONVERSATION1.md).
Line 33: [Warning] Invalid file link:(~/Topic/MC_SEND_CONVERSATION2.md).
Line 42: [Warning] Invalid file link:(~/Topic/CNOS1.md).

his/core/appc-verb-summary.md

Line 17: [Warning] Invalid file link:(~/Topic/ALLOCATE1.md).
Line 17: [Warning] Invalid file link:(~/Topic/MC_ALLOCATE1.md).
Line 22: [Warning] Invalid file link:(~/Topic/RECEIVE_ALLOCATE2.md).
Line 25: [Warning] Invalid file link:(~/Topic/TP_STARTED1.md).
Line 29: [Warning] Invalid file link:(~/Topic/CONFIRM1.md).
Line 29: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).
Line 32: [Warning] Invalid file link:(~/Topic/MC_FLUSH2.md).
Line 32: [Warning] Invalid file link:(~/Topic/FLUSH1.md).
Line 35: [Warning] Invalid file link:(~/Topic/MC_PREPARE_TO_RECEIVE2.md).
Line 35: [Warning] Invalid file link:(~/Topic/PREPARE_TO_RECEIVE1.md).
Line 38: [Warning] Invalid file link:(~/Topic/REQUEST_TO_SEND2.md).
Line 38: [Warning] Invalid file link:(~/Topic/MC_REQUEST_TO_SEND2.md).
Line 41: [Warning] Invalid file link:(~/Topic/MC_SEND_DATA2.md).
Line 41: [Warning] Invalid file link:(~/Topic/SEND_DATA2.md).
Line 51: [Warning] Invalid file link:(~/Topic/MC_POST_ON_RECEIPT2.md).
Line 56: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_POST1.md).
Line 56: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_POST2.md).
Line 61: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 61: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_WAIT1.md).
Line 66: [Warning] Invalid file link:(~/Topic/RECEIVE_IMMEDIATE2.md).
Line 66: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_IMMEDIATE1.md).
Line 69: [Warning] Invalid file link:(~/Topic/TEST_RTS1.md).
Line 69: [Warning] Invalid file link:(~/Topic/MC_TEST_RTS1.md).
Line 73: [Warning] Invalid file link:(~/Topic/CONFIRMED2.md).
Line 73: [Warning] Invalid file link:(~/Topic/MC_CONFIRMED2.md).
Line 76: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_LOG_DATA1.md).
Line 76: [Warning] Invalid file link:(~/Topic/RECEIVE_LOG_DATA1.md).
Line 79: [Warning] Invalid file link:(~/Topic/SEND_CONVERSATION1.md).
Line 79: [Warning] Invalid file link:(~/Topic/MC_SEND_CONVERSATION2.md).
Line 82: [Warning] Invalid file link:(~/Topic/MC_SEND_ERROR1.md).
Line 82: [Warning] Invalid file link:(~/Topic/SEND_ERROR1.md).
Line 86: [Warning] Invalid file link:(~/Topic/MC_GET_ATTRIBUTES1.md).
Line 86: [Warning] Invalid file link:(~/Topic/GET_ATTRIBUTES1.md).
Line 89: [Warning] Invalid file link:(~/Topic/GET_LU_STATUS1.md).
Line 92: [Warning] Invalid file link:(~/Topic/GET_STATE1.md).
Line 95: [Warning] Invalid file link:(~/Topic/GET_TP_PROPERTIES1.md).
Line 98: [Warning] Invalid file link:(~/Topic/GET_TYPE1.md).
Line 101: [Warning] Invalid file link:(~/Topic/SET_TP_PROPERTIES1.md).
Line 105: [Warning] Invalid file link:(~/Topic/ACTIVATE_SESSION1.md).
Line 108: [Warning] Invalid file link:(~/Topic/CNOS1.md).
Line 111: [Warning] Invalid file link:(~/Topic/DEACTIVATE_SESSION2.md).
Line 114: [Warning] Invalid file link:(~/Topic/DISPLAY1.md).
Line 118: [Warning] Invalid file link:(~/Topic/DEALLOCATE1.md).
Line 118: [Warning] Invalid file link:(~/Topic/MC_DEALLOCATE1.md).
Line 121: [Warning] Invalid file link:(~/Topic/TP_ENDED2.md).

his/core/application-cancel.md

Line 14: [Warning] Invalid file link:(~/Topic/Open(PLU) OResponse1.md).

his/core/application-flags.md

Line 16: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 18: [Warning] Invalid file link:(~/Topic/Status-Acknowledge(Ack)1.md).
Line 20: [Warning] Invalid file link:(~/Topic/Status-Acknowledge(Nack-1)2.md).
Line 22: [Warning] Invalid file link:(~/Topic/Status-Control2.md).
Line 32: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 32: [Warning] Invalid file link:(~/Topic/Status-Control2.md).
Line 36: [Warning] Invalid file link:(~/Topic/Status-Acknowledge(Ack)1.md).
Line 38: [Warning] Invalid file link:(~/Topic/Status-Control2.md).
Line 48: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 63: [Warning] Invalid file link:(~/Topic/Data2.md).

his/core/application-initiated-termination.md

Line 16: [Warning] Invalid file link:(~/Topic/Close(PLU) Request1.md).
Line 30: [Warning] Invalid file link:(~/core/media/32703u.gif).
Line 35: [Warning] Invalid file link:(~/core/media/32703ua.gif).

his/core/application-integration-programmer-s-reference.md

Line 34: [Warning] Invalid file link:(~/Topic/Application Integration Samples.md).
Line 37: [Warning] Invalid file link:(~/Topic/Application Integration Programmer’s Guide1.md).

his/core/application-integration-programmer’s-guide.md

Line 40: [Warning] Invalid file link:(~/Topic/Samples.md).
Line 40: [Warning] Invalid file link:(~/Topic/Application Integration Samples.md).
Line 42: [Warning] Invalid file link:(~/Topic/Transaction Integrator Performance Guide2.md).

his/core/as-400-appc-printing.md

Line 16: [Warning] Invalid file link:(~/core/media/prn04.gif).
Line 140: [Warning] Invalid file link:(~/Image/prn05.gif).
Line 144: [Warning] Invalid file link:(~/Topic/Host Print Service (Operations)2.md).

his/core/as-400-connection-summary.md

Line 16: [Warning] Invalid file link:(~/core/media/dep07.gif).

his/core/asynchronous-call-completion.md

Line 14: [Warning] Invalid file link:(~/Topic/Receive (CPI-C)1.md).
Line 16: [Warning] Invalid file link:(~/Topic/Cancel_Conversation (CPI-C)1.md).
Line 18: [Warning] Invalid file link:(~/Topic/Deallocate (CPI-C)2.md).
Line 20: [Warning] Invalid file link:(~/Topic/Request_To_Send (CPI-C)2.md).
Line 22: [Warning] Invalid file link:(~/Topic/Send_Error (CPI-C)1.md).
Line 24: [Warning] Invalid file link:(~/Topic/Test_Request_To_Send_Received (CPI-C)2.md).
Line 81: [Warning] Invalid file link:(~/Topic/Extensions for the Windows Environment2.md).
Line 81: [Warning] Invalid file link:(~/Topic/CPI-C Calls1.md).

his/core/backout-verb-issued-locally.md

Line 14: [Warning] Invalid file link:(~/core/media/appc2db.gif).
Line 17: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 17: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_WAIT1.md).
Line 27: [Warning] Invalid file link:(~/Topic/MC_SEND_ERROR1.md).
Line 27: [Warning] Invalid file link:(~/Topic/SEND_ERROR1.md).
Line 29: [Warning] Invalid file link:(~/Topic/CONFIRM1.md).
Line 29: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).
Line 31: [Warning] Invalid file link:(~/Topic/CONFIRM1.md).
Line 31: [Warning] Invalid file link:(~/Topic/CONFIRMED2.md).
Line 31: [Warning] Invalid file link:(~/Topic/MC_CONFIRMED2.md).
Line 31: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).

his/core/backout-verb-issued-remotely.md

Line 14: [Warning] Invalid file link:(~/core/media/appc2dc.gif).
Line 17: [Warning] Invalid file link:(~/Topic/MC_SEND_DATA2.md).
Line 17: [Warning] Invalid file link:(~/Topic/SEND_DATA2.md).
Line 25: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 25: [Warning] Invalid file link:(~/Topic/RECEIVE_AND_WAIT1.md).
Line 31: [Warning] Invalid file link:(~/Topic/CONFIRMED2.md).
Line 31: [Warning] Invalid file link:(~/Topic/MC_CONFIRMED2.md).

his/core/base-dmod-and-snalink-entry-point-summary.md

Line 20: [Warning] Invalid file link:(~/Topic/SNALinkDispatchProc1.md).
Line 21: [Warning] Invalid file link:(~/Topic/SNALinkInitialize1.md).
Line 22: [Warning] Invalid file link:(~/Topic/SNALinkTerminate2.md).
Line 23: [Warning] Invalid file link:(~/Topic/SNALinkWorkProc2.md).
Line 29: [Warning] Invalid file link:(~/Topic/SNAGetBuffer2.md).
Line 30: [Warning] Invalid file link:(~/Topic/SNAGetElement2.md).
Line 31: [Warning] Invalid file link:(~/Topic/SNAReleaseBuffer2.md).
Line 32: [Warning] Invalid file link:(~/Topic/SNAReleaseElement2.md).
Line 38: [Warning] Invalid file link:(~/Topic/SNAGetLinkName2.md).
Line 39: [Warning] Invalid file link:(~/Topic/SNASendAlert2.md).
Line 40: [Warning] Invalid file link:(~/Topic/SNASendMessage2.md).
Line 46: [Warning] Invalid file link:(~/Topic/SNAGetConfigValue1.md).
Line 47: [Warning] Invalid file link:(~/Topic/SNAGetSystemInfo2.md).
Line 52: [Warning] Invalid file link:(~/Topic/SNADIS Message Formats1.md).

his/core/basic-and-mapped-conversations-compared-cpi-c.md

Line 14: [Warning] Invalid file link:(~/Topic/Set_Conversation_Type (CPI-C)2.md).
Line 21: [Warning] Invalid file link:(~/Topic/Deallocate (CPI-C)2.md).

his/core/basic-and-mapped-conversations-compared.md

Line 21: [Warning] Invalid file link:(~/Topic/DEALLOCATE1.md).

his/core/bind-checking.md

Line 14: [Warning] Invalid file link:(~/Topic/Open(PLU) OResponse1.md).
Line 14: [Warning] Invalid file link:(~/Topic/Open(PLU) Request1.md).
Line 25: [Warning] Invalid file link:(~/Topic/Status-Resource2.md).
Line 30: [Warning] Invalid file link:(~/Topic/Open(PLU) OConfirm2.md).
Line 30: [Warning] Invalid file link:(~/Topic/Open(PLU) Request1.md).
Line 86: [Warning] Invalid file link:(~/Topic/Open(PLU) Error Response1.md).
Line 86: [Warning] Invalid file link:(~/Topic/Open(PLU) Request1.md).
Line 88: [Warning] Invalid file link:(~/core/media/his-32703g.gif).
Line 93: [Warning] Invalid file link:(~/Topic/Open(PLU) Error Confirm1.md).
Line 97: [Warning] Invalid file link:(~/core/media/his-32703ga.gif).

his/core/biztalk-adapter-for-host-files-configuration.md

Line 40: [Warning] Invalid file link:(~/Topic/Managed Data Provider for Host Files1.md).

his/core/bracket-initiation.md

Line 16: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 22: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 38: [Warning] Invalid file link:(~/Topic/Open(PLU) OConfirm2.md).
Line 38: [Warning] Invalid file link:(~/Topic/Open(PLU) OConfirm2.md).
Line 44: [Warning] Invalid file link:(~/core/media/his-32703k.gif).
Line 49: [Warning] Invalid file link:(~/core/media/his-32703ka.gif).
Line 54: [Warning] Invalid file link:(~/core/media/his-32703kb.gif).
Line 59: [Warning] Invalid file link:(~/core/media/his-32703kc.gif).
Line 64: [Warning] Invalid file link:(~/core/media/his-32703kd.gif).
Line 69: [Warning] Invalid file link:(~/core/media/his-32703ke.gif).

his/core/bracket-termination.md

Line 14: [Warning] Invalid file link:(~/Topic/Open(PLU) OConfirm2.md).
Line 16: [Warning] Invalid file link:(~/Topic/Data2.md).
Line 16: [Warning] Invalid file link:(~/Topic/Status-Session1.md).
Line 26: [Warning] Invalid file link:(~/core/media/his-32703l.gif).
Line 31: [Warning] Invalid file link:(~/core/media/his-32703la.gif).

his/core/buffer-element-format-snadis.md

Line 14: [Warning] Invalid file link:(~/Topic/SNADIS Message Formats1.md).

his/core/buffer-element-format.md

Line 14: [Warning] Invalid file link:(~/Topic/FMI Message Formats1.md).
Line 26: [Warning] Invalid file link:(~/Topic/Open(PLU) Request1.md).

his/core/buffer-header-format-snadis.md

Line 14: [Warning] Invalid file link:(~/Topic/SNADIS Message Formats1.md).
Line 21: [Warning] Invalid file link:(~/Topic/SNADIS Message Formats1.md).
Line 30: [Warning] Invalid file link:(~/Topic/Open(LINK)2.md).

his/core/buffer-header-format.md

Line 14: [Warning] Invalid file link:(~/Topic/FMI Message Formats1.md).
Line 21: [Warning] Invalid file link:(~/Topic/FMI Message Formats1.md).
Line 30: [Warning] Invalid file link:(~/Topic/Open(PLU) Request1.md).

his/core/building-connection-strings.md

[Warning] 1 invalid cross reference(s) "<xref:Microsoft.HostIntegration.MsDb2Client.MsDb2ConnectionStringBuilder>".

his/core/changing-conversation-states-cpi-c.md

Line 76: [Warning] Invalid file link:(~/Topic/Prepare_To_Receive (CPI-C)2.md).
Line 80: [Warning] Invalid file link:(~/Topic/Receive (CPI-C)1.md).
Line 80: [Warning] Invalid file link:(~/Topic/Confirmed (CPI-C)1.md).
Line 83: [Warning] Invalid file link:(~/Topic/Request_To_Send (CPI-C)2.md).
Line 83: [Warning] Invalid file link:(~/Topic/Send_Data (CPI-C)1.md).
Line 83: [Warning] Invalid file link:(~/Topic/Confirm (CPI-C)1.md).
Line 85: [Warning] Invalid file link:(~/Topic/Prepare_To_Receive (CPI-C)2.md).
Line 88: [Warning] Invalid file link:(~/Topic/Request_To_Send (CPI-C)2.md).

his/core/changing-conversation-states.md

Line 94: [Warning] Invalid file link:(~/Topic/MC_PREPARE_TO_RECEIVE2.md).
Line 98: [Warning] Invalid file link:(~/Topic/MC_CONFIRMED2.md).
Line 109: [Warning] Invalid file link:(~/Topic/MC_RECEIVE_AND_WAIT1.md).
Line 112: [Warning] Invalid file link:(~/Topic/MC_SEND_DATA2.md).
Line 112: [Warning] Invalid file link:(~/Topic/MC_REQUEST_TO_SEND2.md).
Line 112: [Warning] Invalid file link:(~/Topic/MC_CONFIRM1.md).
Line 114: [Warning] Invalid file link:(~/Topic/MC_PREPARE_TO_RECEIVE2.md).
Line 117: [Warning] Invalid file link:(~/Topic/MC_REQUEST_TO_SEND2.md).

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


Add option to stop MarGo to save battery

When editing Go files, MarGo runs constantly in the background. I understand that this is necessary for code completion but it drains the battery very quickly. Instead of the usual 10 hours of use I only get about 5 hours when GoSublime/MarGo is running. With other programs running in parallel I get even less which makes it hard to work on the road. I tried killing the MarGo processes but they keep respawning. To save battery it would be great if GoSublime/MarGo could be stopped and started at will.

You can add it to your "ignored_packages" in your sublime config or use the package manager to enable/disable it.


S3TransferUtilitySampleSwift returns "Failed with error: Error Domain=..." when downloading image

I'm using iOS 10, Swift 3, Xcode 8.1 to run the S3TransferUtilitySampleSwift app.  I modified the portions of the info.plist, capabilities, and Constants.swift.  I know I have a valid Cognito pool ID and bucket since they work on the Android app.
However, when I try to download an image given the bucket and key, I get the following error:
S3TransferUtilitySampleSwift[7256:152627]`` Failed with error: Error Domain=com.amazonaws.AWSS3TransferUtilityErrorDomain Code=2 "(null)" UserInfo={Server=AmazonS3, Transfer-Encoding=Identity, Connection=close, Content-Type=application/xml, Date=Sat, 04 Mar 2017 10:53:43 GMT, x-amz-request-id=3DFF780A2317BA95, x-amz-id-2=j0RqkR4jIZZ5Nk83lpmpgXhOWY0nOdr1be68Ki6qHPlqg+vO9Qvqkm7sybpz5kaBuvrJX9JLixM=}
Any ideas on why this is happening?  Thanks in advance!

Hi,
Is your bucket region set correctly? This seems like an issue related to invalid configuration.
Thanks,
Rohan

Hi Rohan,
I set the region in the Info.plist to USEast1 (as called out in the markdown) of the S3TransferUtilitySwift sample app.  I haven't tried other regions, but it's worth a shot.  I'll try USWest1.
Any other ideas?
Thanks,
Dave

USWest1 didn't work.  I received the following error.
Session task failed with error: Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found."

The sample app tries to download the image which is uploaded from the upload tab. Could you please upload the image first and then try the download? Make sure that the image / key name being downloaded is present in the bucket.
Thanks,
Rohan

I changed the Constants.swift to point to my bucket and key name of an existing image in that bucket.  But get the same error while downloading.  Not sure what else to try.

In what region did you create your bucket?

has any one found the solution for this issue.. I dont think my credentials have the right management  for Accessing the S3. can you please point me post to follow thru. I am getting the following example
Optional(Error Domain=com.amazonaws.AWSS3TransferUtilityErrorDomain Code=2 "(null)" UserInfo={Server=AmazonS3, Transfer-Encoding=Identity, Connection=close, Content-Type=application/xml, Date=Wed, 05 Apr 2017 16:04:26 GMT, x-amz-request-id=0C93CF95071C9490, x-amz-id-2=j4Vu/iWVMuxTcwLNxTpqQd9CSH4OUyJ9GC92d/E+V4MOmHn4dsjqME6JZZ1Vp6E6oCq0mf59MU8=})

I'm having the same issue.
S3TransferUtilitySampleSwift[22621:13754909] Failed with error: Error Domain=com.amazonaws.AWSS3TransferUtilityErrorDomain Code=2 "(null)" UserInfo={x-amz-id-2=vRjKMnOa21ry0xF/DKQpz57zKONmlQkaz916Elfwvs7CzLmSknjdM2BWwEQQHX1WL/Aj63KzHKw=, Server=AmazonS3, Transfer-Encoding=Identity, x-amz-request-id=5FB3000E60EE3B00, Content-Type=application/xml, Date=Sat, 01 Jul 2017 22:35:45 GMT}
I have checked my permissions and region names, but cannot get this to work.  I have spent a couple days on this and I'm out of ideas.  Anyone figure this out?

Figured out my issue.  Although I had allowed read access for my bucket in the bucket permissions, I had not allowed read access in the permissions of the actual file inside of the bucket.

@bdel23 Made the same mistake. Thanks for reporting back what you found.


[BUG] Installing in REPL breaks _ builtin

Describe the bug
When using from rich import pretty; pretty.install(), the _ (last result) functionality of Python's REPL breaks.
To Reproduce
Without rich:
>>> 5 + 10
15
>>> _ / 2
7.5

With rich:
>>> from rich import pretty
>>> pretty.install()
>>> 5 + 10
15
>>> _ / 2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name '_' is not defined

When rich is installed after the first expression:
>>> 1300 + 36
1336
>>> from rich import pretty
>>> pretty.install()
>>> 21 * 2
42
>>> _ + 1
1337

Platform
Linux, rich 5.1.2 and 5.2.0, Python 3.8.5

Please try v5.2.1


docs($http): reword of XSRF attack overview

Previous version emphasised "gaining user's private data".
While this perfectly describes JSON vulnerability (which is based on XSRF),
data theft suits XSS more.
Pure XSRF is more about performing requests that have side effects.

I reworded it a bit and merged. Thx !
Backported to v1.4.x as 8dc4c75.


Snowflake Information Schema Changed

Summary:
The Information Schema (<DATABASE>.INFORMATION_SCHEMA.TABLES) that we are using to pull the data for the model_information table has changed. Snowflake has added the LAST_DDL and LAST_DDL_BY columns in between the LAST_ALTERED and AUTO_CLUSTERING_ON columns. The new order is now

...
LAST_ALTERED
LAST_DDL
LAST_DDL_BY
AUTO_CLUSTERING_ON
...

These two columns need to be added to the package and the package needs to be released.

Addtionally, there is the USER_DEFINED_TYPE_SCHEMA column:

...
USER_DEFINED_TYPE_CATALOG
USER_DEFINED_TYPE_SCHEMA
USER_DEFINED_TYPE_NAME
...

Issue handled in commit https://github.com/eon-collective/dbt_mart_auditor/commit/8afb715c07c8bddeefb1167a861efa0d162d8e7c, but we need to setup integration testing (#3).

Moving forward, add the issue to the commit message


Feature Request: Allow organizing with subdirectories

One of my current clients has several hundred files in each of assets, layouts & snippets. It would be a large productivity boon if I was able to organize them in subfolders in git & textmate.
The simplest way would be for the uploaded name to be the path + name, replacing '/' with '-' (ex: product/page/bundle-logo.liquid gets uploaded as product-page-bundle-logo-liquid)
Downloading should not create any new directories, but use existing ones that match from left to right (ex: product-page-bundle-logo.liquid would go to product/page/bundle-logo.liquid if product/page subdir exists and produc/page/bundle doesn't)
Handling templates/customers would be a special case.
I'm not a Gogrammer, but I could probably provide a first cut at this if I was confident in it getting in.

This is an interesting idea. It has a lot of complexity in it.

If I go with your example (product-page-bundle-logo.liquid => product/page/bundle-logo.liquid) how could I tell what to do with that file on a complete first download?
If I do end up implementing this and users get used to it, I would get a lot of confusion and support debt from new users trying to use these files and not being able to use the file with a path product/page/bundle-logo.liquid
A simpler problem is being able to opt-in/out and change the separator because if users already have files name product-page-bundle-logo.liquid and then they download, they get a whole bunch of new files that are not where they expect.

I like this idea because I like the amount of flexibility possible in it however I think that it might be hard to work into the codebase.

that's interesting, perhaps add a prefix to any generated file, tk- to namespace it as a themekit file

Shopify themes are quite complex even with the current shallow folder structure. I'd recommend cleaning up the theme assets instead of introducing yet another layer of complexity,
The new 'image_picker' setting type and Sections allowed us to slim down our clients' custom themes considerably.

@illarionvk Thank you for more context, as a tool developer I do not always have full context of the usages or full in depth theme development workflow so I really appreciate multiple oppinions.

@illarionvk do you keep track of code outside of shopify (e.g. local git repo that you push)? If so, I would love to hear how you handle Shopify Sections and merging changes between what's local and what's on the live site.

@frehner We track all theme changes in a Git repo (hosted on Bitbucket). We have two environments in the ThemeKit config: development and live
My process:

Duplicate the live theme
Commit any changes to the git repo
Work on the duplicated theme using the default development environment
Commit my changes to the git repo
Download the live theme into my working copy using live environment./theme download --env live

Merge client's changes, if any. Kaleidoscope diff tool helps a lot with that.
Upload merged changes to my theme
Publish my theme

I have done some thinking about this and I really thing that this would cause more harm then good. The main being that the files on the online editor would be in different locations than on your local computer. This I think is harmful since themes have very strict structures and I would be breaking this with a change that hid this. I hope that @illarionvk tips could help your organize your theme into a more manageable form.


Feature: Tooltip drill down

From @unional on January 4, 2017 2:14

VSCode Version: 1.8.0
Steps to Reproduce:

interface FooOption {
  /**
   * Doing boo stuff
   */
  boo(x: number): boolean
}

function foo(option: FooOption) {

}

foo({
  boo()
})

Currently, autocomplete is doing a better job than the tooltip. When you type boo, autocomplete gets the definition of boo and display it. But once you type (, it falls back to the tooltips and only show the tooltip of foo(...) instead.
It would be nice to have the tooltips shows the info for boo(). 🌷
Copied from original issue: Microsoft/vscode#18070

From @unional on January 4, 2017 18:54
Yes, I understand it is not:
let b: FooOption;
b.boo(
      ^ cursor here

However it is very common practice in JS to do this kind of option bag, and it would be better to drill down and display the same information in this scenario.

From @sandy081 on January 4, 2017 9:31
@unional This is happening because you are not accessing function boo using object of type FooOption. If you does that tool tip provides you proper information.

From @sandy081 on January 5, 2017 13:13
I see. Reopening and assigning to correct owner to provide correct feedback on this.

After investingating, it seems like TS is returning the wrong signigutreHelp response in this case. For the code:
interface FooOption {
  /**
   * Doing boo stuff
   */
  boo(x: number): boolean
}

function foo(option: FooOption) {

}

foo({
boo| {
  return false;
}
})

By typing ( as the location of the | character on line 13, we see the following:
Trace - 2:18:02 PM] Sending request: signatureHelp (395). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/sand/bla.ts",
    "line": 13,
    "offset": 5
}
[Trace - 2:18:02 PM] Response received: signatureHelp (395). Request took 2 ms. Success: true
Result: {
    "items": [
        {
            "isVariadic": false,
            "prefixDisplayParts": [
                {
                    "text": "foo",
                    "kind": "functionName"
                },
                {
                    "text": "(",
                    "kind": "punctuation"
                }
            ],
            "suffixDisplayParts": [
                {
                    "text": ")",
                    "kind": "punctuation"
                },
                {
                    "text": ":",
                    "kind": "punctuation"
                },
                {
                    "text": " ",
                    "kind": "space"
                },
                {
                    "text": "void",
                    "kind": "keyword"
                }
            ],
            "separatorDisplayParts": [
                {
                    "text": ",",
                    "kind": "punctuation"
                },
                {
                    "text": " ",
                    "kind": "space"
                }
            ],
            "parameters": [
                {
                    "name": "option",
                    "documentation": [],
                    "displayParts": [
                        {
                            "text": "option",
                            "kind": "parameterName"
                        },
                        {
                            "text": ":",
                            "kind": "punctuation"
                        },
                        {
                            "text": " ",
                            "kind": "space"
                        },
                        {
                            "text": "FooOption",
                            "kind": "interfaceName"
                        }
                    ],
                    "isOptional": false
                }
            ],
            "documentation": [],
            "tags": []
        }
    ],
    "applicableSpan": {
        "start": {
            "line": 12,
            "offset": 5
        },
        "end": {
            "line": 16,
            "offset": 2
        }
    },
    "selectedItemIndex": 0,
    "argumentIndex": 0,
    "argumentCount": 1
}

The requested signatureHelp position is within the boo function at this point, but we still get the result for foo

I think this is a duplicate of #25265. In both cases, we should show signature help coming from a contextual signature the user should be implementing. Currently we only show signature help from a function you're calling.


Question: Can I use MySQL views?

Hi,
Sorry to open an issue for this. I didn't really see a better outlet though for my question.
My particular use case cannot allow write privileges anyway (my use case is a contacts sync between my server and iOS contacts). Seeing as this is the case, do you think it will be possible to use MySQL VIEW(s) instead of implementing the backend, in order to integrate SabreDAV with my system?
I've run some tests where I've replaced users and principals which seemed to have worked quite well. But before I'm committing more of my time and effort, I thought it would be prudent to ask the creators if they see any inherent flaws as long as there are no write events?
I'd really appreciate your input, cheers!

Well, it should be possible if you can exactly replicate the table structure.

Sure.
Thanks for the quick response


Linking tool stuck rendering connection outline box

This appears to mostly be a visualization bug, but it makes it impossible to tell which drawers are linked to the controller and which ones are not.
Mod version <IP_ADDRESS>.0.17
Modpack: All The Mods 7
Observed behavior: After attempting to use the multiple add mode with the Linking Tool to add multiple drawers to the controller, the Linking Tool now permanently shows the selection outline box at all times when held in the main hand. Have logged out and back in. Have changed dimensions and returned. Neither has had any effect on the issue. This means I can no longer see what drawers are and are not connected to the controller.
Screenshot 1

Screenshot 2

Also tried breaking and replacing the controller block, and the problem persists.

I believe I figured out the cause of this issue, and it's an order of operations problem. While using the linking tool set to "Select Multiple", it did not register that I had right clicked on a second block for the selection area. This leaves the selection area rendering; if you then change the mode of the linking tool to Select Single, it allows you to do so, but leaves the multiple block selection area rendering as shown above. You have to go back to Select Multiple, and then successfully select a beginning and end block to stop the selection box from rendering.
Suggestion: When the mode changes from Select Multiple to Select Single, stop rendering the multi-select box if it is active.
Alternate suggestion: (This may be easier code wise, but not a great UX) Do not allow the player to change the mode of the linking tool if a multi-select is in progress.


how to compute geometric error in 3D Tiles rightly

hello,I know the geometric error is measured in meters,and it means the error of the simplified geometry compared to the actual geometry.but I dont know how to compute it. for example, I have a osgb data and it's lod type is DISTANCE_FROM_EYE_POINT,when I convert the osgb to 3DTiles,how to compute the GEOMETRIC ERROR param? Is there some relation between DISTANCE_FROM_EYE_POINT and GEOMETRIC ERROR?

There has been some discussion on this topic which you can reference here:
https://github.com/CesiumGS/3d-tiles/issues/162
https://community.cesium.com/t/understanding-geometric-error/8480/2
For future questions similar to this, please post them on our community forum, where there are engineers and other users who can help answer your questions.

There has been some discussion on this topic which you can reference here:
https://github.com/CesiumGS/3d-tiles/issues/162
https://community.cesium.com/t/understanding-geometric-error/8480/2
For future questions similar to this, please post them on our community forum, where there are engineers and other users who can help answer your questions.


[Bug] Optional Packages are not installable on V6

Backpack Optional Packages are currently not installable on V6 using the guide.
https://backpackforlaravel.com/docs/6.x/install-optionals

Hi I had the same problem few days ago because a weird problem with the site repo. which banned my ip address. But now I  be able to install any package with V6. I have a test project with language manager, permissions manager, devtools, pro, and editable columns. Maybe is the same

During beta, to install any first-party Backpack add-on, please require the v6 branch on that addon. That provides support for Backpack v6. For example:
composer require backpack/permission-manager:"v6.x-dev"


Fix double scheme

Scheming is good, double scheming not so much.

Codecov Report

Merging #78 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #78   +/-   ##
======================================
  Coverage    90.3%   90.3%
======================================
  Files          12      12
  Lines         454     454
  Branches       56      56
======================================
  Hits          410     410
  Misses         27      27
  Partials       17      17

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 50b7340...6cf4ca9. Read the comment docs.


Instrumentation issue

On this project I'm getting this report:

As you can see, the first ImportDeclaration is apparently incorrectly interpreted as an IfStatement and it's indicating that the else is not covered.
nyc version: 7.0.0
node version: 6.3.0
Let me know if I can provide any more useful information to help figure out what's going on here. Thanks!

Using babel-plugin-istanbul [version...]?

Ah, yes, babel-plugin-istanbul version 1.0.3 (latest)

Incidentally, on that project I've configured it to use all here, but that doesn't seem to be working in the output. I've gotten it to work successfully elsewhere however. I haven't had time to dig into that separate issue, but if anyone wants to take a swing at it, that'd be neat 👍

Thanks for reporting this issue. This is fixed in<EMAIL_ADDRESS>via https://github.com/istanbuljs/istanbul-lib-instrument/commit/4274e38622af84ed9e2229e3dcf9a4d75ef2ec91

@kentcdodds give:
npm cache clear; npm i nyc@next  a spin, should have the fix.

That worked! And it also found another issue that the previous version had not:

Before, it didn't show I hadn't covered that else yet 👍

@kentcdodds - even the previous version would have computed that multiple else-s weren't covered but it was plastering all the indicators one on top of another at the top of the report :)

Oh, that makes sense now. Cool!


Is it necessary to use a worker thread or child process?

What are you trying to achieve?
The docs say "Everything remains non-blocking thanks to libuv, no child processes are spawned and Promises/async/await are supported." So does that mean I don't need to spawn child processes or use a worker thread pool on my own?
I created an endpoint that uses a worker thread to fetch an image from AWS S3, then use sharp to extract it into 9 sections, then upload the 9 images to AWS S3. Finally, the frontend uses those 9 images to make an image scramble game (screenshot below). However, now I'm wondering if it's not necessary to use a worker thread (or a child process) for this.
Abridged code below. Any thoughts? Thank you!
Have you searched for similar questions?
Yes
Are you able to provide a minimal, standalone code sample that demonstrates this question?

Are you able to provide a sample image that helps explain the question?

Thanks again!
Kent

The short answer is: "probably not". Was there a reason for using Workers in the first place?
I would imagine the bottleneck in this scenario will be network I/O rather than CPU. I notice the logic above waits for all image processing to complete before uploading so perhaps this is the bit to optimise.

The short answer is: "probably not". Was there a reason for using Workers in the first place?
I would imagine the bottleneck in this scenario will be network I/O rather than CPU. I notice the logic above waits for all image processing to complete before uploading so perhaps this is the bit to optimise.

Fairly new to image processing. So, I initially thought image processing would block the event loop. Then I re-read the bit about how everything remains non-blocking. Curious how that works, so I'll need to research it. But that's a great tip about the bottleneck. Thank you! Cheers!

Fairly new to image processing. So, I initially thought image processing would block the event loop. Then I re-read the bit about how everything remains non-blocking. Curious how that works, so I'll need to research it. But that's a great tip about the bottleneck. Thank you! Cheers!

@lovell is it doing the work on the main thread or in a worker?
I ask because I wrote a script that batch processes a large bulk of files - I noticed it was using only 25% CPU (so 1 of 4 cores, presumably) and decided to run multiple jobs in parallel.
Not a complete example, but something like:
(async () => {
  let jobs: Array<Promise<void>> = [];

  async function throttle(job: Promise<void>) {
    jobs.push(job);

    job.then(() => {
      jobs = jobs.filter(item => item !== job);
    });

    while (jobs.length > 10) {
      await Promise.race(jobs);
    }
  }

  for (let i=0; i<total; i++) {
    const filename = files[i];

    console.log(`[${i}/${total}] indexing: ${filename}`);

    await throttle(resizeImage(filename));
  }
})();

So this allows for 10 unresolved promises at any time - resizeImage starts a job and returns a Promise<void>, we keep running jobs in jobs, and and when a job finishes, we remove it.
This got me into the area of maybe 30-50% CPU, so still not running on all cylinders for some reason.
Do I need to manually spawn workers to make sure it's running on all cores?
I suppose it could be that I'm hitting an IO bottleneck, but I wouldn't guess so - JPEG files are small.

So I tried a few different things, I guess worth sharing. 🙂
First, I moved my files to a fast SSD, and yeah, I was definitely hitting an IO bottleneck - my CPU isn't even that fast (an old i7) so I guess sharp and libvips must be very fast! It's certainly the first time I've ever seen any kind of image processing go too fast for the drives to keep up. 😃
With the SSD at ~50% load, there was still room for improvements, so:
I tried this library which implements a Worker pool - I tried it both with and without my throttle implementation above. It works about the same either way. Some improvement, but still hovering around 50-60% CPU and the SSD definitely had more to give.
Clearly, the image operations are already running in threads - so nothing gained by adding threads on top of threads. (Most likely the contrary - it's probably just unnecessary extra overhead.)
I dropped the idea of adding workers/threads, and instead tuned the number of jobs in the script I posted above, and tuned the script itself - here's a copy-and-paste version of a helper function I extracted from the example above:
async function runJobs<T>(max_jobs: number, inputs: Iterable<T>, work: (input: T) => Promise<any>) {
  let jobs: Array<Promise<void>> = [];

  async function throttle(job: Promise<void>) {
    jobs.push(job);

    job.then(() => {
      jobs = jobs.filter(item => item !== job);
    });

    while (jobs.length >= max_jobs) {
      await Promise.race(jobs);
    }
  }

  for (const input of inputs) {
    await throttle(work(input));
  }
}

It uses an Iterable as input - if you're streaming a list of files, this helps processing everything on the fly, spawning the work for each input as needed.
I found that os.cpus().length provides a reasonable number of threads.
Example:
(async () => {
  const max_jobs = os.cpus().length;

  await runJobs(max_jobs, files, async filename => {
    console.log(`Processing: ${filename}`);

    await someHeavyWorkWith(filename);
  });
})();

@lovell it's still not clear to me why this extra layer is necessary?
Is there any particular reason why sharp doesn't internally schedule the work?
I tried setting e.g. sharp.concurrency(4), which seems to make things worse on WSL2, so the rationale in the docs seems to be correct - so processing a single job in multiple threads doesn't make sense.
But processing only one image at a time doesn't lead to good performance either?
The tasks are running outside the main thread anyhow - if we can't process the individual operations concurrently, wouldn't the "next best thing" be an internal worker queue, so we can at least process multiple operations in parallel? 🤔

@mindplay-dk Did you see https://sharp.pixelplumbing.com/api-utility#concurrency ? The bit about libuv parallelism may be of interest, as that is responsible for managing the worker queue upon which sharp schedules tasks.

I did see that - as mentioned, I tried sharp.concurrency(4), and it did return 4, so it wasn't being limited by the libuv setting, I think?
Do I understand correctly that the concurrency this refers to is the concurrency of sharp intenally, then? I was actually under the impression it had to do with concurrency in libvips itself - e.g. decoding a very large JPEG or resizing an image would be a multithreaded operation, but maybe that's not even a feature?

@mindplay-dk
concurrency controls how many threads libvips will use per task, which includes resizing.
Some en/decode libraries use single-threaded I/O, e.g. libjpeg, so if you're decoding large JPEGs this may be the bottleneck.
UV_THREADPOOL_SIZE controls how many worker threads libuv will spawn at startup and therefore determines the maximum number of parallel tasks. Tasks queue until a libuv worker thread is available. (The same thread pool is used by Node.js for potentially blocking I/O e.g. some DNS lookups.)
You probably don't need to use Node.js worker threads; doing so may cause extra overhead.
If you need further help, please create a standalone repo with all the code and images that allows someone else to reproduce the exact scenario.

Some en/decode libraries use single-threaded I/O, e.g. libjpeg, so if you're decoding large JPEGs this may be the bottleneck.

That's exactly what I'm doing.

You probably don't need to use Node.js worker threads; doing so may cause extra overhead.

That's what my results indicated, yes.
What is the "normal" way to batch process images?
My naive first attempt was something like:
for (const image of images) {
  await sharp(image)
    .resize(200)
    .jpeg()
    .toFile(`{$image}.thumb`);
}

No matter what sharp is doing internally, this will process just one image at a time.
On the other hand, I tried something like this, which did not work well:
await Promise.all(
  images.map(image => sharp(image)
    .resize(200)
    .jpeg()
    .toFile(`{$image}.thumb`)
  )
);

I don't know if that's intended or expected to work? I mean, even if sharp internally schedules this work and doesn't try to run everything all at once, this would create thousands of promises and sharp configuration states - it wouldn't give you a nice, streaming throughput, and also nothing indicates where you are in the process or how much work is left.
To get this running smoothly for large batches of files, with a progress indicator and so on, you would have to be doing something like what I implemented above, right?
I'm sure there are plenty of dreadfully wrong ways to go about this. There's not really a "standard" way to do this in Node or JS in general, right? Someone might pick out a thread pool library like I tried, which appears to work on the surface, but they end up shipping something that performs appallingly.
Maybe this should be in the manual?
What I came up with works okay, though I'm not sure if it's the best/simplest approach?

Did you see https://sharp.pixelplumbing.com/api-utility#queue , which might allow for progress monitoring?
Perhaps for your scenario you might try https://github.com/sindresorhus/p-limit (or if you want to manage the queue instead of libuv then try https://github.com/sindresorhus/p-queue).

Did you see https://sharp.pixelplumbing.com/api-utility#queue , which might allow for progress monitoring?

Yes, but that's still not really appropriate for processing millions of files? You need a stream - an (async) generator to avoid startup overhead from creating a huge number of promises.

Perhaps for your scenario you might try https://github.com/sindresorhus/p-limit (or if you want to manage the queue instead of libuv then try https://github.com/sindresorhus/p-queue).

Yes, these look like viable solutions - perhaps mention those in the manual? Batch processing is a common enough requirement.
I could help out and add a chapter to the manual, if you'd like?
I'd like to save others from the work I had to do to - trying the wrong approach, or the wrong libraries (threads instead of a simple promise queue/limit) to come up with the solution above. I could include that as an example and link to those libraries.
There are far too many ways to do something horribly wrong here. 😉


Configure bluetooth power alerts in bluetooth permission config

Similar to notifications

Whoops, this is actually #106 already


Refactor mapping from json to dto

Currently, the json object is being mapped to the dto using a private method on ApiCheckoutService.
Maybe it should be moved to a Mapper class.

Done.


fixed continuous integration

Continuous Integration is broken, we need to fix it

@Clairvoyant1236

also add regression test on it

https://github.com/U-Network/UNetwork/commit/aaf9b776e024b4ae0b1f18095c1d2627ad4faf9d


Where does npm install dependencies?

I am trying to use a recent version of node. I have a container with
containers:
  node:
    setup:
      - !UbuntuRelease { version: 15.04 }
      - !UbuntuUniverse
      - !BuildDeps [curl]
      - !Install [apt-transport-https, ca-certificates]
      - !Sh |
          curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
      - !UbuntuRepo
        url: https://deb.nodesource.com/node_5.x
        suite: vivid
        components: [main]
      - !Install [nodejs]
      - !NpmConfig
        install_node: false
  koa:
    setup:
      - !Container node
      - !Depends frameworks/koa/package.json
      - !Env
        HOME: /home
      - !NpmConfig
        install_node: false
      - !NpmDependencies
        file: frameworks/koa/package.json
        dev: false
    environ:
      HOME: /home

where the file package.json has a dependency on "koa": "^1.2.0".
Unfortunately, when I try to run require('koa') from a node shell inside the koa container, I get Error: Cannot find module 'koa'.
Where are npm modules installed by !NpmDependencies?

Ok, I have solved it myself. Node modules are installed in /usr/lib/node_modules. For node to find them, one should set an environment variable NODE_PATH, like this
  koa:
    setup:
      - !Container node
      - !Depends frameworks/koa/package.json
      - !Env
        HOME: /home
      - !NpmConfig
        install_node: false
      - !NpmDependencies
        file: frameworks/koa/package.json
        dev: false
    environ:
      HOME: /home
      NODE_PATH: /usr/lib/node_modules

Yes. Probably you can propose some doc additions?

I could, but it seems that the github files are not aligned with what's on readTheDocs. Where are the correct sources for the docs?

That is a correct place. Sources are fine. Just github fails to render markup extensions of sphinx.


select2 multiple not validating

Hi,
I've problems with a select2 (http://select2.github.io/) multiple validation. When I use a single select2 (only one option), validator works, but seem not to be working when multiple.

All in the picture are required fields. "Clientes" and "Contrarios" are mutiple.
Has anybody the same problem?

Same here

This issue tracker is not meant to be a support forum. Since this isn't detailing a bug with the plugin, this sounds like a question best suited for StackOverflow.

Anyone ever determine a fix for this? Select2 single works, whereas multiple shows briefly before being removed. Going to ditch this otherwise excellent plugin if I can't figure out a solution.

Has anyone managed to solve the problem?

I have this problem too.


router: Pass FactoryContext to the route config so that it can be used for per-filter config.

Signed-off-by: Greg Greenway<EMAIL_ADDRESS>Risk Level: Low
Testing: Existing tests pass

@mattklein123 This is what we discussed last week. I failed to come up with anything clever to avoid passing the FactoryContext all the way through.
Do we want to re-namespace FactoryContext, or just leave it?


Update compulsory fields (name and phone) for create command.

bugs/defects that weren't fixed in this PR:
As peter mentioned, moving/renaming the file on disk causes FABook to abort save file. possible fix: stop checking validness of filepath at launch.
Filepath is still not allowed at contact creation. Testing with filepaths is limited.

Codecov Report
Base: 73.38% // Head: 73.34% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (5a00cf9) compared to base (fa38d39).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #89      +/-   ##
============================================
- Coverage     73.38%   73.34%   -0.05%
- Complexity      535      537       +2
============================================
  Files            90       90
  Lines          1661     1658       -3
  Branches        181      179       -2
============================================
- Hits           1219     1216       -3
  Misses          374      374
  Partials         68       68

Impacted Files
Coverage Δ

.../main/java/seedu/address/model/person/Address.java
75.00% <ø> (-5.00%)
:arrow_down:

.../java/seedu/address/storage/JsonAdaptedPerson.java
96.00% <ø> (-0.11%)
:arrow_down:

...eedu/address/logic/parser/CreateCommandParser.java
100.00% <100.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
96.55% <100.00%> (ø)

...rc/main/java/seedu/address/model/person/Email.java
80.00% <100.00%> (ø)

...main/java/seedu/address/model/person/NetWorth.java
70.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


write pid file

Write PID file when start-up.

Interesting. Can you describe your use case?

I want to use Piper in production environment.
I will run Piper as systemd service, and I want to check process liveness with Sensu.
But Piper doesn't write pid file, so I cannot monitor process liveness.


Idea to solve a diamond problem

Not a final code, just to show an idea.
What if derived atom does not trigger notify on update?
Method run returns notify method.
Notify behaves differently depending on a level it called on.
Common behavior
It triggers all listeners, collects resulting functions into a set of children notify methods.
Derived atoms
It returns the set of notify methods.
Top level atoms
It trigers all notify methods, collecting results into the same set and triggering those.
Run method for the computed atom
If the value was updated, it returns notify method.

Tests are falling

Tests are falling

Yes, it's the draft PR I created to try communicate the idea before digging deeper into the project.


Update: ToEverything.AFFiNE version 0.15.0 (0.15.2)

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


Windows DLL support

Current code is incompatible with Windows DLL.
Solution is simple. In .H files:
#ifdef WIN32
# ifdef CJOSE_BUILD
#  define CJOSE_EXTERN __declspec(dllexport)
# else
#  define CJOSE_EXTERN __declspec(dllimport)
# endif
#else
# define CJOSE_EXTERN
#endif
[...]
CJOSE_EXTERN const char *CJOSE_HDR_ALG;

Example is for CJOSE_HDR_ALG, but should be added to all exported symbols.
The #ifdef WIN32 has to be included once in a central file obviously.
Could we expect this?
Thanks a lot

since the Windows build requires other Windows-specific files as well I suggest to keep this in a fork

I build it in Windows with only that addition


fix(dataset): add "AuthData" to "init.py"

Pull Request Test Coverage Report for Build 977839914

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.883%

Totals

Change from base Build 977562139:
0.0%

Covered Lines:
4947

Relevant Lines:
5828

💛  - Coveralls


Issue while installing, not cloning.

I'm trying to install this library using the command given below:
pip install<EMAIL_ADDRESS>
but It gets stuck on this
Collecting<EMAIL_ADDRESS>Cloning https://github.com/django-nonrel/django (to nonrel-1.5) to /var/folders/wn/klm7h6757yj5lj60zdk7w2bw0000gn/T/pip-90prjk0m-build

This is a very old issue so I am confident that you either solved it or moved on but I just tried
pip install<EMAIL_ADDRESS>and it works fine. The installation is okay so I assume it had to do with your git configuration

I had to wait few minutes, than it proceeded with installation

I had to wait few minutes too. You can look for the progress using this command:
$ watch du -sh /var/folders/wn/klm7h6757yj5lj60zdk7w2bw0000gn/T/pip-90prjk0m-build


Missing events from month view

This is possible bug.
Sometimes when I switch fast adjacent  months in month view, BigCalendar gets re-rendered with the necessary events (around 290 for the time period), but then are not shown in the calendar. Strangely enough if there are some events, that were show before (from previous month) they are shown, but the current month new events are missing for a while:
Sometimes it needs a couple of seconds to show. Sometimes I need to move the mouse over the calendar to show. If this doesn't help I just need to scroll the page a bit for them to show, and all this without any new react re-render. So my thinking is towards some "async" peculiarity, garbage collection issue, or maybe something with DOM listeners.
I can try dig it, but any advice where to look is appreciated. Thanks for the wonderful component.
PS: I want to point out that BigCalendar gets re-rendered with the correct events array, and this is not synchronization issue from the API layer. Showing initially missing events correlates with mouse move over the BigCalendar or scrolling of the page.

It seems that this happens to other components as well, so the issue is in presumably in React. Closing.


LayoutTransformation mapping qubits incorrectly between dags

I'm not sure I understand what's happening, but I use LayoutTransformation and I recently hit a bug where LayoutTransformation isn't producing the desired output. It's actually non-deterministic, sometimes it works, other times the exact same input does not (if I set a seed, then it becomes deterministic).
I've found that if I replace this line:
https://github.com/Qiskit/qiskit-terra/blob/bee5e7f62db400a4c2f6924064413371be0048eb/qiskit/transpiler/passes/routing/layout_transformation.py#L112
with:
        qubits = [dag.qubits[i[0]] for i in perm_circ.inputmap.items()]

(i.e., remove the sorted) then passed all my tests.
I'm not entirely clear why, but one origin seems to be that the order that the qubits are added to the PermutationCircuit is non-deterministic:
https://github.com/Qiskit/qiskit-terra/blob/bee5e7f62db400a4c2f6924064413371be0048eb/qiskit/transpiler/passes/routing/algorithms/util.py#L85-L91
I'm not an expert in qiskit dag circuits, but it looks like the argument to compose needs to be sorted in the qubit ordering in the permutation circuit, not the dag passed to run. My hack works because the inputmap dict has, deterministically, the correct sort.
My issue could also be fixed by sorting the nodes object before this line:
https://github.com/Qiskit/qiskit-terra/blob/bee5e7f62db400a4c2f6924064413371be0048eb/qiskit/transpiler/passes/routing/algorithms/util.py#L89
The sorted was added in #5281 by @1ucian0

Please can you provide a reproducer of your bug?  The extra information here is super nice, but I don't actually understand what problem you're having.

$ git diff .
diff --git a/test/python/transpiler/test_layout_transformation.py b/test/python/transpiler/test_layout_transformation.py
index 5fe2fe315..903bcf194 100644
--- a/test/python/transpiler/test_layout_transformation.py
+++ b/test/python/transpiler/test_layout_transformation.py
@@ -15,7 +15,7 @@
 import unittest

 from qiskit import QuantumRegister, QuantumCircuit
-from qiskit.converters import circuit_to_dag
+from qiskit.converters import circuit_to_dag, dag_to_circuit
 from qiskit.test import QiskitTestCase
 from qiskit.transpiler import CouplingMap, Layout
 from qiskit.transpiler.passes import LayoutTransformation
@@ -45,6 +45,25 @@ class TestLayoutTransformation(QiskitTestCase):

         self.assertEqual(circuit_to_dag(expected), output_dag)

+    def test_qubit_ordering(self):
+        v = QuantumRegister(9, "v")  # virtual qubits
+        coupling = CouplingMap.from_grid(3,3)
+        from_layout = Layout({v[0]: 0, v[4]: 1, v[2]: 2, v[3]: 3, v[1]: 4, v[8]: 5, v[6]: 6, v[7]: 7, v[5]: 8})
+        to_layout = Layout({v[i]: i for i in range(9)})
+        ltpass = LayoutTransformation(
+            coupling_map=coupling, from_layout=from_layout, to_layout=to_layout, seed=42
+        )
+        qc = QuantumCircuit(9)  # input (empty) physical circuit
+        dag = circuit_to_dag(qc)
+        output_dag = ltpass.run(dag)
+        print(dag_to_circuit(output_dag))
+
+        expected = QuantumCircuit(9)
+        expected.swap(1,4)
+        expected.swap(5,8)
+        self.assertEqual(circuit_to_dag(expected), output_dag)
+
+
     def test_four_qubit(self):
         """Test if the permutation {0->3,1->0,2->1,3->2} is implemented correctly."""
         v = QuantumRegister(4, "v")  # virtual qubits

It prints this (incorrect) dag:
q_0: ──────

q_1: ────X─
         │
q_2: ────┼─
         │
q_3: ────┼─
         │
q_4: ─X──┼─
      │  │
q_5: ─X──┼─
         │
q_6: ────┼─
         │
q_7: ────┼─
         │
q_8: ────X─

In order to find this one which fails, I did a combinatorial search. I didn't find a smaller from_grid which exhibits the problem.
This particular test was run on 0.18.3, but I believe I checked the latest main too.

Oh, and that test passes as written if I remove the sorted from LayoutTransformation as described above.

The normal "bug report" template should have prompted for this

This issue was created by selecting a line in the code on GH and then clicking "Reference in new issue" in the context menu. I just confirmed, no issue template is presented to the reporter!

Perfect, thanks.  That's enough for us to go on, though I'm not sure if we'll have many resources to put into it internally - I wasn't even aware of this pass's existence, and it looks like it was added in #3762 with the intent to use it in #2860, which simply never merged.  Nothing else in the library uses it, and there's only been one nontrivial change to it since it merged two years ago (the commit in #5281 you mentioned above).
If you come across for a fix for it, please let us know and we'd be happy to accept a PR (and with the new test case - we're a little lacking in tests for it at the moment!).

no issue template is presented to the reporter!

Ah, that's how they get us!  A shame, really, though I guess GitHub didn't want to deal with the headache of deciding which field in the report form it should fill that entry into.


feat: [UIE-8074] - DBaaS GA Summary tab

Description 📝
DBaaS GA summary tab refactor. Data remains the same, although the layout is altered.
Changes  🔄

V1 Summary components moved to /legacy dir marked deprecated and will be removed post GA release.
V2 Summary components with tests

Target release date 🗓
10/28/24
Preview 📷

V2 Legacy
V2 Default

How to test 🧪
Prerequisites

Managed Databases account capability
LD flag: beta: false, enabled: true

Verification steps

Toggle LD flag will show GA screen vs. V1 screen

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[x] 🔐 Removing all sensitive information from the code and PR description
[x] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

@corya-akamai Please resolve the linting errors; it looks like there are quite a few.

Done


Bump version to 0.4.0

We didn't bump the version as part of
f607589ecb737ae75028bda3135b45ad31085fed

FYI f607589 was not a change in the meaning of the spec, just how the document was organized. So my thinking was that no version bump was required.

Whoops @fhwang! I read the diff quickly - if that's the case, we can close this.


Nkpatel/maxpool yolo v4 support

Ticket
https://github.com/tenstorrent/tt-metal/issues/7746
Problem description
Add support for maxpool for highter filter/channel sizes.
What's changed
Support is added for filter lengths > 3 and channels > 256 for supporting YoLoV4
Checklist

[x] Post commit CI passes link
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Also please rebase and combine all commits into one. And make sure pipelines pass.


What happened SnowLord?

What happened SnowLord?
I know this isnt the right place but, what happened Snowlord? Why did you archive everything and basically stop everything? You don't have any contact links anywhere and you havent posted anything in the past 3 months. Y'd you archive the quizlet/developer tools github? Why'd you officially drop support for the extention? Please snowlord ... let us know why

Are you okay Drew?
https://github.com/SnowLord7/quizlet/commit/f97326e8d94f0918e3c6788f69073629a0f3e266
let index = 0,                 getId("js-learnModeAnswerButton").click();			phrases = 'Hello my friend you are you today? I am extremely sad because Quizlet finds enjoyment at my pain, not to mention they are being paid to make me sad while all I gain is depression.'.split(' ');

Thank you, I really appreciate the concern.
My life took a sudden turn in the last couple months and i've been having trouble dealing with it. Looking back on it, I acted in an extremely selfish way, I should not have suddenly archived the extension and removed all forms of contact. Even still, I can't help others when I can't even help myself.
Speaking plainly, I will most likely not come back here until I find out where I want to take my life.

Well good luck for the future... I hope things go well for you!


apply delayed operations to slice a matrix either by rows or columns

for https://github.com/jkanche/kana/pull/120 &
https://github.com/jkanche/kana/issues/112

I tried to do a more generic version
NumericMatrix row_subset(const NumericMatrix& matrix, int margin, uintptr_t offset, size_t length) {
    auto offset_ptr = reinterpret_cast<const int32_t*>(offset);
    return NumericMatrix(tatami::make_DelayedSubset<margin>(matrix.ptr, std::vector<int32_t>(offset_ptr, offset_ptr+length)));
}

but it kept complaining
/Users/kancherj/Projects/public/scell/scran.js/src/subset.cpp:47:26: error: no matching function for call to 'make_DelayedSubset'
    return NumericMatrix(tatami::make_DelayedSubset<margin>(matrix.ptr, std::vector<int32_t>(offset_ptr, offset_ptr+length)));
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Minor fixes added; go ahead and squash it.
The more generic version doesn't work because the template parameters need to be known at compile time.


Style .css files moved to assets folder

Before relative url to css files was used in layout, because of this translated pages displays without style. Jekyll supports assets to store assets files (https://jekyllrb.com/docs/step-by-step/07-assets/). Now all pages, original and translated displays with styles.

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


Fix #4597: Do string argument checks before a possible strtol

strtol sets errno, which must be reset if it is no abort condition.
Invert the comparisons to avoid that.
Superseeds #4598
We do not reset errno as there must never be a condition where it is not handled.
If somewhere a function sets a code that is not reset it must be handled there.

All of the other strto* calls with a following errno check still need to be fixed as per my other patch. One strto* failure cascades into other failures without those, so not all of the errno resets I included were redundant -- including these ones.

@kevans91 There shouldn't be any cascade as whenever a errno is set the command line parser must return a error condition (and the client abort)

Ah, so not these two- there were still a couple other instances outside of cmdline that didn't look like they would cause an abort ?

@kevans91 Those are channel command line parsing and gateway related (or some other command line utils)

nod Fair enough, then. =)

I think, "strto*" calls still need to be revisited (in a separate effort). The usage of this API "as is" seems to be too error prone. As was mentioned in original PR it might not reset "errno" on both success and failure. Say, some other call before "strto*" might set "errno" to failure (which might not be critical for that call) and then we might discard a valid number.
It seems that the only reliable way to test "strto*" success/failure is to check whether "pEnd/endptr" pointer has reached the end of input string.

@p-pautov errno values must be handled when they are set. Of course that can be quite taxing, but it is the only way to go. doing some other kind of hackish error checks is not really a good idea.

@akallabeth I'm not arguing against checking of errno. The problem here is that strtol() sets it rather frivolously (at least on Linux), making errno check after strtol() call almost useless. Just checking errno is not enough.
#include <stdlib.h>
#include <errno.h>
#include <stdio.h>

void parse_num(const char* str)
{
	strtol(str, NULL, 0);

	if (errno == 0) {
		printf("'%s' is a number\n", str);
	} else {
		printf("'%s' is NOT a number\n", str);
	}
}

int main()
{
	parse_num("banana");

	fopen("non-existent-file", "r");

	parse_num("5");
}

The above program prints following on Ubuntu 16.04
'banana' is a number
'5' is NOT a number

Here is how more reliable wrapper around strtol() could look like:
https://github.com/openssh/openssh-portable/blob/master/openbsd-compat/strtonum.c
https://gist.github.com/gocha/623eb5611bd9648fb3024146d6ecc055/

Merging this as it fixes the initial issue #4597
We should open a separate issue for the general problem of converting string to numbers as @p-pautov pointed out.


Uncaught URIError: URI malformed when trying to send '%' through API

Hello,
I had trouble when I try to send '%' value using semantic API and I got this console message error:

https://stackoverflow.com/questions/15326777/uncaught-urierror-uri-malformed-jquery-ui-tabs-on-windows/21078971#21078971 might be references through this issue.
I'm using Chrome 59, Windows
Thanks
EDIT:
This problem might be a bug on Semantic UI escaping string function. After read documentation, this can be disable by using API settings encodeParameters=false . So the further protection comes from server validation, not by client side.

Hi @mxvin, sorry for the delay, what string produces the error?

That's okay bro 😃
Here's the fiddle http://jsfiddle.net/cewxfom9/2
i've test Firefox and Edge and they did the same too,

@mxvin You’re right, it blows up when the API component tries to decode it here. We’ll see how it can be changed.

@mxvin I’ve been going through my old JSFiddles and found one—apparently I was already talking with someone about the issue, but then completely forgot about it. If you’re interested in a temporary fix, you could use beforeSend() callback and encodeURIComponent():
beforeSend: function (settings) {
  let value = $('input.err').val()

  settings.urlData = {
    value: encodeURIComponent(value)
  }

  return settings
}

Or just replace the sign:
beforeSend: function (settings) {
  let value = $('input.err').val()

  let result = value.replace(/[%]/g, function (m) {
    return '%' + m.charCodeAt(0).toString(16)
    // Basically changes "%" to "%25".
  })

  settings.urlData = {
    value: result
  }

  return settings
}

@Banandrew Whoa, thanks!
I was think beforeSend can make it, but i'm too lazy so i continue to other part of my project 😄
Hope this might help someone out there that facing same problem 💯

up


Adjust grpc constants and measure the server handling time

internal static class GrpcConstants

This is confusing, I expect a class called "GrpcConstants" to be only const values, not static. This seems like the correct class for the hardcoded 5 minutes, 70 threads, and true to be defined.
I would expect  EngineEnvironmentSettings to point to GrpcConstants and the Engine to be using EngineEnvironmentSettings to initialize Grpc, instead of GrpcConstants pointing to EngineEnvironmentSettings and the Engine calling into GrpcConstants.

Refers to: Public/Src/Engine/Dll/Distribution/Grpc/GrpcConstants.cs:9 in ec1e9fd. [](commit_id = ec1e9fd3efe57643d2c83c4829cdb4b23ae616b6, deletion_comment = False)


Fix shortfin gibberish tokens and add cpu_llm_server_test.py

Rob and I found some weirdness in paged_llm_v1 that was inconsistent with how shortfin worked.
We hacked a solution for now but we really need to fix paged_llm_v1 by cleaning up the seq_lens and start_positions and adding some CLEAR documentation as to EXACTLY what they do.
Currently we're able to make the llm count.
Right now the context length is effectively 16 tokens. By adding cache allocation, we'll soon be able to actually talk with the LLM.

To test these changes, run: https://gist.github.com/renxida/d40e14b1c9b4606279d19899bcce5e9a


cinnamon.cinnamon-control-center: fix tls support in online accounts

Description of changes
Google login shows TLS support is not available:

gnome-control-center also has glib-networking as buildInputs, so this should be needed. Tested and solved the above problem.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

It will be nice to provide some more context in the commit message, I am thinking of something like
Without the fix Google login shows `TLS support is not available` when the module is
invoked by the c-c-c executable directly (instead of the `cinnamon-settings` program)
*and* the `services.gnome.glib-networking.enable` option is disabled.


IOS cordova When i upgrade the AngularJs to 1.8.2 the words will be missed which was been translated.

Subject of the issue
I'm using the AngularJs 1.8.0 and angular-translate is 2.18.4. the issues are not appear, but we need to upgrade the AngularJs to 1.8.2 some label will be disappeared in Ios cordova. other platform is normal.
Your environment
angular-translate version2.18.1
angular version1.8.2
ios cordova 5.1.1
Steps to reproduce
The code just like this

Any one have faced this issue?could someone can help?

Hello,
i would recommend to look into the app with a debugger which will provide you with additional loggings. Maybe this will show you more details.
Otherwise: As we had already mentioned in the issue's template, we need a working and as minimal as possible demo covering your specific use case or issue.
Follow these steps:

Please open this plnkr base.
Fork it (at the top left).
Ensure the version of AngularJS and angular-translate is correct.
Ensure all angular-translate plugins are available; reduce and remove anything you can.
Write a minimal as possible demo for your specific issue.
Save and freeze. Provide us the final link to your demo.


Update sbt-scalajs, scalajs-compiler to 1.0.1

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler

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

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

labels: library-update, semver-major

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


Use MPTCP by default if available

Goals :soccer:

Improve the network reliability of apps using Alamofire by enabling Multipath TCP by default, in Handover Mode. This
TCP extension allows to use multiple network interfaces in case of deterioration of the connection on one of them
Sources:

https://www.mptcp.dev
https://developer.apple.com/documentation/foundation/urlsessionconfiguration/improving_network_reliability_using_multipath_tcp

Implementation Details :construction:

Set the property multipathServiceType of the URLSessionConfiguration objects default and ephemeral
Testing Details :mag:

Ran again the tests to make sure that everything was still working fine. No additional tests seems needed

I don't think this is something we want, as it requires connection and server support to actually improve anything. There's a reason Apple doesn't enable this by default. It also requires an entitlement to work, so Alamofire enabling it by default does nothing if developers aren't entitled. Thanks anyway!


ImportError: cannot import name 'FilingType' from 'secedgar' (/usr/local/lib/python3.7/dist-packages/secedgar/init.py)

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
in google colab follow the steps on the site:
!pip install secedgar
from secedgar import filings, FilingType
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
If specific to your OS, please specify which OS you are using [e.g. Windows, macOS, Ubuntu Linux, etc.]
Additional context
Add any other context about the problem here.

Note it works if I do this:
!pip install secedgar==0.4.0a2

Duplicate of #236


Need detailed information about "unsupported resource group"

This might be related to #25689 - I read through the issue and understand cephalin's comment. However, I couldn't understand what kind of resource group is unsupported for upgrading to PremiumV2 from the content ("Scale up from an unsupported resource group and region combination"). Could you please provide detailed description about the 'unsupported resource group' including examples if possible?   Thanks.

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

ID: 3cfacf3d-4d48-317b-0c68-2f992ebb60bc
Version Independent ID: 9f00811a-bbf8-91e9-238b-d28066e19c83
Content: Configure PremiumV2 tier - Azure App Service
Content Source: articles/app-service/app-service-configure-premium-tier.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

PremiumV2 is currently not supported in all regions. So first thing to check is if the region your app exist in supported region.
Also as we know resource group uses scale unit to deploy the resources in it. Some scale units don’t have Premium v2 deployed in them even if they are in the supported region. In other words, not all scale unit (cluster) contain Pv2 instances, (underlying App Service deployment doesn’t support PremiumV2. )
So to Scale up an existing app to PremiumV2 tier, you need supported resource group and region, is what my understanding is.

@Daya-Patil Thanks for your comment. I confirmed that my customer is trying to create PV2 App Service Plan in supported region, but they couldn't select some existing resource group when creating PV2 App Service Plan (I've not gotten any detailed information of the resource group).
For "resource group uses scale unit to deploy the resources in it", I'd assume existing resource in the resource group uses scale unit, and I'd like to know what resource(s) does(do) that. I'm hoping my question makes sense.  Thanks.

May be this one will help
https://feedback.azure.com/forums/169385-web-apps/suggestions/35089333-allow-scale-up-to-premium-v2-without-redeploy-or-c

@Daya-Patil I think I understand what the "unsupported resource group" means (resource group was created with specified non-PV2 tier/sku) by looking at the command lines in the following link, correct?
Configure PremiumV2 tier - Azure App Service | Microsoft Docs
https://docs.microsoft.com/en-us/azure/app-service/app-service-configure-premium-tier#automate-with-scripts

@kazshi, As Daya mentioned, Azure deploys each new App Service plan into a deployment unit, internally called a webspace. Each region can have many webspaces, but your app can only move between plans that are created in the same webspace. The premium v2 plans are not available in all scale units, which is not up to App Service.
Yes, there has been some feedback raised on a similar request(s) on Uservoice, the one feedback post shared by Daya and another one below, requesting you to take a look: https://feedback.azure.com/forums/169385-web-apps/suggestions/33683959-enable-users-to-scale-to-pv2
Checkout this blog ‘How to pick the stamp or scale unit where your App Service will run’ for more details on stamp or scale unit.
Source: This document provides more details on requirement including scale-unit: https://docs.microsoft.com/en-us/azure/app-service/app-service-plan-manage

@AjayKumar-MSFT Thank you for the additional information. I read the Note in the link and I think I understand why 'resource group' is mentioned in the limitation - that's what made me confusing.  Closing.


Fix integer overflow on white colors

Fixes #37

The grayscale conversion used is: GRAY = 0.3R + 0.6G + 0.1B
In the previous test case:

if R=0xAA, G=0xCA, B=0x7B; then GRAY = 184.5 (decimal), which if consistent with other values would be rounded off to 185 (0xB9 hex).  I fixed couple of those
if R=0x71, G=0xFF, B=0x00; then GRAY = 186.9 (decimal), in the previous version the decimal value 187 was used and in this version 187 is also used (0xBB).  That is what I mean by rounding off consistently.

In the previous version the main problem was when

R=0xFF, G=0xFF, B=0xFF; then Gray should be 0xFF, but due to integer treatment, got Gray=0x00, so all white pixels became black.  I added a test case which tests this.

Looks good to me, thanks! 👍
(Sorry for taking so long to get to this).


Prototype idempotent run #2

Description:

Is this change user facing?
NO

References (if applicable):

Implemented in #769


Updgrade to the latest versions of AppAuth-JS.

upgrade @openid/appauth to ^1.1.1
upgrade electron to ^3.0.8
upgrade typescript to ^3.1.6

Are there plans to merge this in the near future?

Just realized that here was an outstanding PR against the sample repo.
Thanks for your PR. Let me take a look.


Update DEV_GUIDE and create Strimzi Namespace variable for downstream pipelines

Type of change

Enhancement / new feature
Documentation

Description
Created STRIMZI_NAMESPACE env variable to be able to detect if Strimzi has already been installed by the pipeline and not install it if this is the case.
Additional Context
@im-konge is working on creating the pipeline for all AMQ-Streams product and we need to set the namespace where Strimzi is installed for Kroxylicious and Console.
Checklist

[ ] Write tests
[X] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonar-Lint warnings are addressed or are justifiably ignored.
[X] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

@strimzi-ci run system tests

@strimzi-ci run system tests

:arrow_forward: Build started - check Jenkins for more info. :arrow_forward:

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 12
KAFKA VERSION: 3.6.1
TOTAL: 6
PASS: 5
FAIL: 0
SKIP: 1


"I don't have that monster!" BSO Custom's missing

🐛 Bug Report

these are only 2 that I've noticed the response "I don't have that monster!" for. when I know for a fact igne used to work for simulations, but 'rum-pumped' crab idk if ever existed for =kill. but it has a cl.
so I have checked the situation more deeply and all BSO custom monsters are not in the database for =kill my guess is when you did the simulators on https://www.oldschool.gg the coding must have disappeared for bso. idk just a guess or thought. plz don't use it to troll me.

🐛 Bug Report

these are only 2 that I've noticed the response "I don't have that monster!" for. when I know for a fact igne used to work for simulations, but 'rum-pumped' crab idk if ever existed for =kill. but it has a cl.
so I have checked the situation more deeply and all BSO custom monsters are not in the database for =kill my guess is when you did the simulators on [https://www.oldschool.gg/monsters](Oldschool.gg Loot SimulatorsSimulator) the coding must have disappeared for bso. idk just a guess or thought. plz don't use it to troll me.

Fixed in next update.


fix: smart union with typeddict

Change Summary

Related issue number
fix #3541

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

awesome, thank you.


Change behavior for the bill generation

A bill is generated when the sylius_payment flow is complete. This is something good for business to business but not for business to customer because a "complete" sylius_payment is not always paid and an unpaid order should not have a generated bill.
That's why I think we should change this behavior.
Steps
Current configuration must be updated :

The sylius_invoicing_plugin_payment_complete_producer callback should be in the sylius_order state machine, on the fulfill transition.

winzou_state_machine:
    sylius_order:
        callbacks:
            after:
                sylius_invoicing_plugin_payment_complete_producer:
                    on: ['fulfill']
                    do<EMAIL_ADDRESS>'__invoke']
                    args: ['object']

Sylius\InvoicingPlugin\EventProducer\OrderPaymentPaidProducer should be updated because there is no more a PaymentInterface but an OrderInterface. Class should be renamed OrderFulfilledProducer.
Sylius\InvoicingPlugin\EventProducer\OrderPlacedProducer should be updated because the event is no more dispatched with a condition on checkoutState (but with paymentState and OrderPaymentStates::STATE_PAID). Class should be renamed OrderPaidProducer.
Related code should be renamed.
After changes
An unpaid order will not have any bill until the OrderPaymentStates::STATE_PAID is dispatched. Then the bill will be available for customer. Because the payment is paid, the owner can print the bill and prepare his order. Finally the order will be "fulfilled" when the shipment is marked as "shipped" and the bill will be sent to the customer.

Any updates on this?

news ?

Sorry but your comments are not very helpful. If you want to make this change on your own Sylius: create a fork, follow the instructions and send love for this change (this issue/slack/...). If not, submit a PR and/or buy one day of work.


All Stores list dos not have adequate sample data

Description:  The All Stores list view is broken down by countries, however our sample data only shows one country – japan. We are not showing off the capabilities developed and we cannot review the layout with only one data point for the page. We require a minimum of 4 countries with some data to properly assess the page functionality.
How to duplicate: Go to the Store finder and click on ‘All Stores’ option

we'll be updating sample data in the future but this is a slightly bigger task that will have to wait until after 1.0

closing as whatever we add to sample data will be what is done with storefinder effort