Sorry to post here. Frozen Asset. Please help me.

I know it is not the right place to discuss about my issue. (I tried to register Ripple Forum, but I didn't get any activation email during a few days. Sorry to post my issue here.) Thank you for your help and advice.
Recently I set Trustset in my regular ripple account and I tried to send a few transactions but I couldn't. I looked my debug file. Then I got blow. Is my account frozen?? If so, how I can resolve it?
 I got error message. "Missing/inapplicable prior transaction."
rippled submit "12000024000000102E000004D2614000000001C9C380684000000000007530730081146473D1A028E6FCF02789EB458145CC9133F4DB7A8314FFC2DDC8AAB72C0503281F0DF72615857CF8AEDCF3E01073210327E63FA54A856CB6BF0C2BE2BDB84302FFD4C80E298911720A07DC3B1D6606007446304402207611D383177B81E60AEA662796ABDAE8D4DA8E6621FC9A3B8599353D94E6B08302205CB43125A37BE45A86672038C4ECD28E6CAECFD73D8480364E0BBE3909E5A7F581141B153F4CAD8222901F20AB003B1B78FA26002736E1E010732102DFC6FB1630B644590C8B7D11276EBB06B18F954DA0DA9E623AFD03C7A942FC507446304402202506FEF3D90DA21D4102AFC22A0312D79AFBFC69EC71172CFEAA25C0CE18393602206A3D94D6AE0DE57F759F7D4246B758E40B00329F6F065D212C3A1BAD1AEB78E4811446C0C953F59D2FE35BDAE576D91BF82819728649E1F1"
"result" : {
"engine_result" : "terPRE_SEQ",
"engine_result_code" : -92,
"engine_result_message" : "Missing/inapplicable prior transaction.",
"status" : "success",
"tx_blob" : "12000024000000102E000004D2614000000001C9C380684000000000007530730081146473D1A028E6FCF02789EB458145CC9133F4DB7A8314FFC2DDC8AAB72C0503281F0DF72615857CF8AEDCF3E01073210327E63FA54A856CB6BF0C2BE2BDB84302FFD4C80E298911720A07DC3B1D6606007446304402207611D383177B81E60AEA662796ABDAE8D4DA8E6621FC9A3B8599353D94E6B08302205CB43125A37BE45A86672038C4ECD28E6CAECFD73D8480364E0BBE3909E5A7F581141B153F4CAD8222901F20AB003B1B78FA26002736E1E010732102DFC6FB1630B644590C8B7D11276EBB06B18F954DA0DA9E623AFD03C7A942FC507446304402202506FEF3D90DA21D4102AFC22A0312D79AFBFC69EC71172CFEAA25C0CE18393602206A3D94D6AE0DE57F759F7D4246B758E40B00329F6F065D212C3A1BAD1AEB78E4811446C0C953F59D2FE35BDAE576D91BF82819728649E1F1",
"tx_json" : {
"Account" : "rww9KRNZ7mEHNAXEeLdVreiuk4bimtmbiS",
"Amount" : "30000000",
"Destination" : "rQKLk73wH9fS7CTM71cAaPUrS4L1reMB4h",
"DestinationTag" : 1234,
"Fee" : "30000",
"Sequence" : 16,
"Signers" : [
{
"Signer" : {
"Account" : "rs7U6Tytqbifj7buVyL1XY2DiohhZHCzqE",
"SigningPubKey" : "0327E63FA54A856CB6BF0C2BE2BDB84302FFD4C80E298911720A07DC3B1D660600",
"TxnSignature" : "304402207611D383177B81E60AEA662796ABDAE8D4DA8E6621FC9A3B8599353D94E6B08302205CB43125A37BE45A86672038C4ECD28E6CAECFD73D8480364E0BBE3909E5A7F5"
}
},
{
"Signer" : {
"Account" : "rfTfETxrcwNU3S1EbymFuVEbBYhCjWF2an",
"SigningPubKey" : "02DFC6FB1630B644590C8B7D11276EBB06B18F954DA0DA9E623AFD03C7A942FC50",
"TxnSignature" : "304402202506FEF3D90DA21D4102AFC22A0312D79AFBFC69EC71172CFEAA25C0CE18393602206A3D94D6AE0DE57F759F7D4246B758E40B00329F6F065D212C3A1BAD1AEB78E4"
}
}
],
"SigningPubKey" : "",
"TransactionType" : "Payment",
"hash" : "BA0A0C999BA78BD4ACBB8967B30DA886A2B29B5262CEBD9D10C9884C0E7785F6"
}
}
}
Here is my server_info
"result" : {
"info" : {
"build_version" : "0.81.0",
"complete_ledgers" : "36526764-36530085",
"hostid" : "ip-10-0-10-56",
"io_latency_ms" : 1,
"last_close" : {
"converge_time_s" : 2,
"proposers" : 9
},
"load" : {
"job_types" : [
{
"job_type" : "untrustedProposal",
"per_second" : 43
},
{
"in_progress" : 1,
"job_type" : "clientCommand",
"per_second" : 7
},
{
"job_type" : "transaction",
"per_second" : 8
},
{
"job_type" : "batch",
"per_second" : 7
},
{
"job_type" : "fetchTxnData",
"per_second" : 1
},
{
"job_type" : "trustedValidation",
"per_second" : 2
},
{
"job_type" : "writeObjects",
"peak_time" : 1,
"per_second" : 5
},
{
"job_type" : "trustedProposal",
"per_second" : 2
},
{
"job_type" : "peerCommand",
"per_second" : 572
},
{
"job_type" : "diskAccess",
"per_second" : 2
},
{
"job_type" : "processTransaction",
"per_second" : 8
},
{
"job_type" : "SyncReadNode",
"per_second" : 1
},
{
"job_type" : "WriteNode",
"per_second" : 236
}
],
"threads" : 6
},
"load_factor" : 1,
"peers" : 10,
"pubkey_node" : "n9LFhRMkzemDMULAANicF7Bp9g2earNGAnrciEjJt6BB7b8ajHsn",
"pubkey_validator" : "nHBX3ipdipAsp1HwSFjQr7AXVVx1Z6vByD7ckWKqvwbdCWb6V1JH",
"server_state" : "proposing",
"state_accounting" : {
"connected" : {
"duration_us" : "100045439",
"transitions" : 1
},
"disconnected" : {
"duration_us" : "1153554",
"transitions" : 1
},
"full" : {
"duration_us" : "59718225812",
"transitions" : 1
},
"syncing" : {
"duration_us" : "3017006",
"transitions" : 1
},
"tracking" : {
"duration_us" : "0",
"transitions" : 1
}
},
"uptime" : 59823,
"validated_ledger" : {
"age" : 8,
"base_fee_xrp" : 1e-05,
"hash" : "8E8D82E86D53EE93E1693D86255B76CAC56E8971D8271671F854B86DF90461FE",
"reserve_base_xrp" : 20,
"reserve_inc_xrp" : 5,
"seq" : 36530085
},
"validation_quorum" : 8,
"validator_list_expires" : "2018-Feb-18 00:00:00"
},
"status" : "success"
}

Your transaction has sequence 16 while your account has sequence 15. Transactions issued by the same account must execute in order and transaction 16 won't execute until transaction 15 executes. Looking at the server debug log is not particularly helpful as it's telling you what the server is doing, which doesn't have much to do with what you're doing.

Thank you for your quick response. OK. I understand sequence. So transaction 15 must be executed. It may be a silly question. So If I make seq 15 transaction, It will work??
Here is log file again.
2018-Feb-12 09:10:38 ValidatorSite:DBG Loading configured validator list sites
2018-Feb-12 09:10:38 ValidatorSite:DBG Loaded 1 sites
2018-Feb-12 09:10:38 NodeObject:DBG NodeStore target size set to 131072
2018-Feb-12 09:10:38 NodeObject:DBG NodeStore target age set to<PHONE_NUMBER>00
2018-Feb-12 09:10:38 TaggedCache:DBG LedgerCache target size set to 256
2018-Feb-12 09:10:38 TaggedCache:DBG LedgerCache target age set to<PHONE_NUMBER>00
2018-Feb-12 09:10:38 TaggedCache:DBG TreeNodeCache target size set to 512000
2018-Feb-12 09:10:38 TaggedCache:DBG TreeNodeCache target age set to<PHONE_NUMBER>0
2018-Feb-12 09:10:38 NetworkOPs:NFO Consensus time for #3 with LCL 28587E48C080CA973CEF8673E0E925F4110E92300B0C4DDCA5453B46555CFDD8
2018-Feb-12 09:10:38 ValidatorList:DBG 1  of 1 listed validators eligible for inclusion in the trusted set
2018-Feb-12 09:10:38 ValidatorList:DBG Using quorum of<PHONE_NUMBER>3709551615 for new set of 1 trusted validators
2018-Feb-12 09:10:38 ValidatorList:WRN New quorum of<PHONE_NUMBER>3709551615 exceeds the number of trusted validators (1)
2018-Feb-12 09:10:38 LedgerConsensus:NFO Entering consensus process, watching, synced=no
2018-Feb-12 09:10:38 LedgerConsensus:NFO Consensus mode change before=observing, after=observing
2018-Feb-12 09:10:38 NetworkOPs:DBG Initiating consensus engine
2018-Feb-12 09:10:38 Server:NFO Opened 'port_rpc_admin_local' (ip=<IP_ADDRESS>:5005, admin IPs:<IP_ADDRESS>, http)
2018-Feb-12 09:10:38 Server:NFO Opened 'port_peer' (ip=<IP_ADDRESS>:51235, peer)
2018-Feb-12 09:10:38 Server:NFO Opened 'port_ws_admin_local' (ip=<IP_ADDRESS>:6006, admin IPs:<IP_ADDRESS>, ws)
2018-Feb-12 09:10:38 Application:FTL Startup RPC:
{
"command" : "log_level",
"severity" : "warning"
}
2018-Feb-12 09:10:38 Application:FTL Result: {}
2018-Feb-12 09:11:32 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:32 LedgerConsensus:WRN Need consensus ledger CA0A25E630C98EBB4D830985762C24EA441F227546C913B894C7B7E53DB84ECF
2018-Feb-12 09:11:35 LoadMonitor:WRN Job: processLedgerData run: 1302ms wait: 0ms
2018-Feb-12 09:11:35 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:35 LedgerConsensus:WRN Need consensus ledger ED8FEA8753F2DAA608FB1D2479E81A97D353C19C1605130BDA4C2528D34AE19C
2018-Feb-12 09:11:37 LoadMonitor:WRN Job: processLedgerData run: 4104ms wait: 0ms
2018-Feb-12 09:11:39 LoadMonitor:WRN Job: processLedgerData run: 4104ms wait: 0ms
2018-Feb-12 09:11:39 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:35 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:35 LedgerConsensus:WRN Need consensus ledger ED8FEA8753F2DAA608FB1D2479E81A97D353C19C1605130BDA4C2528D34AE19C
2018-Feb-12 09:11:37 LoadMonitor:WRN Job: processLedgerData run: 4104ms wait: 0ms
2018-Feb-12 09:11:39 LoadMonitor:WRN Job: processLedgerData run: 4104ms wait: 0ms
2018-Feb-12 09:11:39 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:39 LedgerConsensus:WRN Need consensus ledger E0DDC7059BFDA72689F18BD00004F35A492D8B94651A9E265DD62B72D46C4C4A
2018-Feb-12 09:11:43 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:43 LedgerConsensus:WRN Need consensus ledger A6416A6473017E4F58A738E281B836A1BEF2706F95DA34182651A3E3DF086AB9
2018-Feb-12 09:11:45 LoadMonitor:WRN Job: processLedgerData run: 7702ms wait: 58ms
2018-Feb-12 09:11:45 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 5282ms
2018-Feb-12 09:11:45 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 5282ms
2018-Feb-12 09:11:46 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:47 LoadMonitor:WRN Job: processLedgerData run: 7516ms wait: 1791ms
2018-Feb-12 09:11:48 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:48 LedgerConsensus:WRN Need consensus ledger 4E761DDDC24C5AB4A247010AE1F81665E216ADFA602F02880EE071AF2786063C
2018-Feb-12 09:11:50 LoadMonitor:WRN Job: processLedgerData run: 2953ms wait: 195ms
2018-Feb-12 09:11:50 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:52 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:52 LedgerConsensus:WRN Need consensus ledger 52320A35B3632F77BE65FAA6C6385E74EC9A800D2876485AF74D5E75B65CF687
2018-Feb-12 09:11:54 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:55 LoadMonitor:WRN Job: processLedgerData run: 4817ms wait: 2950ms
2018-Feb-12 09:11:55 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 7280ms
2018-Feb-12 09:11:55 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 7093ms
2018-Feb-12 09:11:56 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:56 LedgerConsensus:WRN Need consensus ledger 0C2B52A4C9955EFF1BCC8859953026BB583B373E894361BD04E8AC953C2BF50F
2018-Feb-12 09:11:57 LoadMonitor:WRN Job: processLedgerData run: 12322ms wait: 5227ms
2018-Feb-12 09:11:58 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:11:58 LedgerConsensus:WRN Need consensus ledger 0664783B6984ABAAEC0A8D64E98CEDA6356724E7C2C2AF60B1F209123270DDC5
2018-Feb-12 09:11:59 LoadMonitor:WRN Job: processLedgerData run: 3894ms wait: 6933ms
2018-Feb-12 09:11:59 LoadMonitor:WRN Job: processLedgerData run: 160ms wait: 3893ms
2018-Feb-12 09:12:01 LoadMonitor:WRN Job: processLedgerData run: 2109ms wait: 4037ms
2018-Feb-12 09:12:01 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 3429ms
2018-Feb-12 09:12:01 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:03 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:03 LedgerConsensus:WRN Need consensus ledger 1127CFCE85B538A6010C33B653186044976DBD6A5636A64C4E235EC6F75760F8
2018-Feb-12 09:12:05 LoadMonitor:WRN Job: processLedgerData run: 7166ms wait: 7545ms
2018-Feb-12 09:12:10 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:10 LedgerConsensus:WRN Need consensus ledger 5297F1B37104BA379F7B3D753BB268341F31E89233E04045319966DCDEA83FA0
2018-Feb-12 09:12:11 LoadMonitor:WRN Job: processLedgerData run: 6074ms wait: 5827ms
2018-Feb-12 09:12:11 LoadMonitor:WRN Job: processLedgerData run: 167ms wait: 9808ms
2018-Feb-12 09:12:12 LoadMonitor:WRN Job: processLedgerData run: 2109ms wait: 10218ms
2018-Feb-12 09:12:12 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 10565ms
2018-Feb-12 09:12:12 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 7558ms
2018-Feb-12 09:12:12 LoadMonitor:WRN Job: processLedgerData run: 1160ms wait: 9966ms
2018-Feb-12 09:12:13 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:13 LedgerConsensus:WRN Need consensus ledger E99818A4EC924D3428AB474810DC3A0FF63C5617A3221A9E8EF203A5FDA4CF0A
2018-Feb-12 09:12:15 LoadMonitor:WRN Job: processLedgerData run: 2706ms wait: 7231ms
2018-Feb-12 09:12:15 LoadMonitor:WRN Job: processLedgerData run: 2547ms wait: 2264ms
2018-Feb-12 09:12:15 LoadMonitor:WRN Job: processLedgerData run: 467ms wait: 3704ms
2018-Feb-12 09:12:15 LoadMonitor:WRN Job: processLedgerData run: 481ms wait: 3866ms
2018-Feb-12 09:12:15 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:15 LoadMonitor:WRN Job: processLedgerData run: 496ms wait: 3146ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 573ms wait: 3019ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 268ms wait: 3310ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 275ms wait: 3192ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 300ms wait: 1228ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 139ms wait: 1051ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 155ms wait: 1184ms
2018-Feb-12 09:12:16 LoadMonitor:WRN Job: processLedgerData run: 499ms wait: 1322ms
2018-Feb-12 09:12:17 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:17 LedgerConsensus:WRN Need consensus ledger AF62D2C19E71A237744830D94637256DEBC49BC646B282C85AF0A1564F7EECFE
2018-Feb-12 09:12:18 LoadMonitor:WRN Job: processLedgerData run: 1134ms wait: 375ms
2018-Feb-12 09:12:18 LoadMonitor:WRN Job: processLedgerData run: 549ms wait: 668ms
2018-Feb-12 09:12:18 LoadMonitor:WRN Job: processLedgerData run: 139ms wait: 1120ms
2018-Feb-12 09:12:18 LoadMonitor:WRN Job: processLedgerData run: 173ms wait: 1023ms
2018-Feb-12 09:12:19 NetworkOPs:WRN We are not running on the consensus ledger
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got C02270BA5202D316779D35625667136097435E0F6D9353060A5B66A866A95B29 no peers were proposing it
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got 5DA0115D10B530A5FFB553D0A700CFF1B17A7DEDDA8B524776AF43B7EB11B804 no peers were proposing it
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got DB225E0FA7C4DD3FE9DB4DEF3C5252C4F48BA6F6D0A49F1D76C3686B242D247F no peers were proposing it
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got DB225E0FA7C4DD3FE9DB4DEF3C5252C4F48BA6F6D0A49F1D76C3686B242D247F no peers were proposing it
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got A2BD1EFA01F3744327657D571354FEF2105164E6A763A1B0582494D2BB6958EF no peers were proposing it
2018-Feb-12 09:12:20 LedgerConsensus:WRN By the time we got AACC6FC9C42FC267E5E89BF3F14B8782D84D519F4B054968971B8CCD7750484B no peers were proposing it
2018-Feb-12 09:12:22 LedgerConsensus:WRN By the time we got 851D95B5D83B24B63707C276283F2689EA037640117E04F5AB43C40E90E2A43A no peers were proposing it
2018-Feb-12 09:12:22 LedgerConsensus:WRN By the time we got 0960A80DE1599C0F739668DEF3200A6556F9B290EA391AB09E6518901BCF0E3B no peers were proposing it
2018-Feb-12 09:12:22 LedgerConsensus:WRN By the time we got 63C6BA3F3374631442B95AB2ECB0AFC201DAC440BDAD5914CE239CA09AB94264 no peers were proposing it
2018-Feb-12 09:12:23 LoadMonitor:WRN Job: OrderBookDB::update run: 4990ms wait: 0ms
2018-Feb-12 09:12:40 LoadMonitor:WRN Job: advanceLedger run: 1254ms wait: 0ms
2018-Feb-12 09:12:40 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:41 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:12:42 LoadMonitor:WRN Job: sweep run: 3684ms wait: 0ms
2018-Feb-12 09:12:45 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:12:45 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:12:45 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:15:45 LoadMonitor:WRN Job: sweep run: 1774ms wait: 0ms
2018-Feb-12 09:15:45 LoadMonitor:WRN Job: recvGetLedger run: 1062ms wait: 0ms
2018-Feb-12 09:15:45 LoadMonitor:WRN Job: recvGetLedger run: 1340ms wait: 0ms
2018-Feb-12 09:18:00 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:18:00 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:18:00 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:18:00 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:18:00 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:18:04 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:18:04 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:28:24 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:28:24 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:28:24 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:28:24 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:28:24 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:28:28 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:28:28 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:28:28 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:38:48 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:38:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:38:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:38:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:38:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:38:53 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:38:53 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:38:53 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:40:34 Peer:WRN [014] onReadMessage: Connection reset by peer
2018-Feb-12 09:44:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:44:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:44:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:44:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:44:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:44:07 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:44:07 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:44:07 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:49:17 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:49:20 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:49:20 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:49:20 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:49:23 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:49:23 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:49:23 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 09:49:46 Peer:WRN [001] onReadMessage: short read
2018-Feb-12 09:54:33 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 09:54:35 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:04:22 LoadMonitor:WRN Job: advanceLedger run: 1421ms wait: 0ms
2018-Feb-12 10:04:30 LoadMonitor:WRN Job: advanceLedger run: 1490ms wait: 0ms
2018-Feb-12 10:04:32 LoadMonitor:WRN Job: WAL run: 1554ms wait: 0ms
2018-Feb-12 10:04:34 LoadMonitor:WRN Job: WAL run: 1173ms wait: 0ms
2018-Feb-12 10:04:34 LoadMonitor:WRN Job: advanceLedger run: 1590ms wait: 0ms
2018-Feb-12 10:04:36 LoadMonitor:WRN Job: WAL run: 1119ms wait: 0ms
2018-Feb-12 10:04:37 LoadMonitor:WRN Job: advanceLedger run: 1003ms wait: 0ms
2018-Feb-12 10:04:40 LoadMonitor:WRN Job: WAL run: 1359ms wait: 0ms
2018-Feb-12 10:04:41 LoadMonitor:WRN Job: WAL run: 1455ms wait: 0ms
2018-Feb-12 10:04:41 LoadMonitor:WRN Job: advanceLedger run: 1678ms wait: 0ms
2018-Feb-12 10:04:43 LoadMonitor:WRN Job: WAL run: 1237ms wait: 0ms
2018-Feb-12 10:04:44 LoadMonitor:WRN Job: WAL run: 1163ms wait: 0ms
2018-Feb-12 10:04:45 LoadMonitor:WRN Job: WAL run: 1107ms wait: 0ms
2018-Feb-12 10:04:45 LoadMonitor:WRN Job: advanceLedger run: 1396ms wait: 0ms
2018-Feb-12 10:04:46 LoadMonitor:WRN Job: WAL run: 1124ms wait: 0ms
2018-Feb-12 10:04:47 LoadMonitor:WRN Job: WAL run: 1034ms wait: 0ms
2018-Feb-12 10:04:48 LoadMonitor:WRN Job: WAL run: 1108ms wait: 0ms
2018-Feb-12 10:04:48 LoadMonitor:WRN Job: advanceLedger run: 1732ms wait: 0ms
2018-Feb-12 10:04:50 LoadMonitor:WRN Job: WAL run: 1247ms wait: 0ms
2018-Feb-12 10:04:51 LoadMonitor:WRN Job: WAL run: 1195ms wait: 0ms
2018-Feb-12 10:04:51 LoadMonitor:WRN Job: advanceLedger run: 1165ms wait: 0ms
2018-Feb-12 10:04:52 LoadMonitor:WRN Job: WAL run: 1379ms wait: 0ms
2018-Feb-12 10:04:54 LoadMonitor:WRN Job: WAL run: 1344ms wait: 0ms
2018-Feb-12 10:04:55 LoadMonitor:WRN Job: WAL run: 1336ms wait: 0ms
2018-Feb-12 10:04:55 LoadMonitor:WRN Job: advanceLedger run: 1517ms wait: 0ms
2018-Feb-12 10:05:06 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:05:09 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:05:09 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:05:09 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:05:12 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:05:12 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:05:12 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:06:06 LoadMonitor:WRN Job: sweep run: 5086ms wait: 0ms
2018-Feb-12 10:10:25 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:10:25 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:10:25 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:15:34 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:15:36 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:15:36 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:15:36 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:15:40 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:15:40 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:15:40 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:20:50 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:20:52 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:20:52 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:20:52 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:26:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:26:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:26:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:26:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:26:03 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:26:06 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:26:06 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:26:06 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:31:18 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:31:21 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:31:21 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:31:21 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:36:31 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:36:35 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:36:35 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:36:35 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:41:46 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:41:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:41:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:41:49 OpenLedger:WRN Offer involves frozen asset
2018-Feb-12 10:41:52 LedgerConsensus:WRN Offer involves frozen asset
2018-Feb-12 10:41:52 LedgerConsensus:WRN Offer involves frozen asset
Same error until today.

Great. I will try... . Thank you for your quick message.

Thank you for giving me a direction about my silly question and comment.
It is working well now. Again. Thank you for all your help and advice.
You guys are awesome. :) 👍

Our pleasure. Take care.


[RESTEASY-2776] Add some documentation about Optional types in BeanParams

Fix for https://issues.redhat.com/browse/RESTEASY-2776 (doc part)
Motivation
Some documentation was needed to describe the new feature https://issues.redhat.com/browse/RESTEASY-2776
Modifications:

Adds a new section in the documentation about OptionalParam

@asoldano here is the request doc, hoping that it is what you expected


Expose panel:close

Not an issue, but a small feature request: would it be possible to expose the panel:close method, so a keymap can be set to toggle the panel visibility? Or, better yet, just create a wrapper panel:toggle function?

Awesome plugin and I second this. It would be great if I could set and press q when cursor is in the panel to close it due to my personal keybindings.

This feature would be very helpful for programmatic control of the panel without needing the cursor to be in the panel. It would also be great to expose an is_open() function to check if the panel is open.
For an example use case, I have a setup with several plugins that open panels at the bottom of the screen, and due to limited screen real estate I prefer having only one such panel open at a time. I have set up keybindings to close any bottom panel if it is visible, and to automatically close an existing panel if I open another one. This relies on having open, close, and is_open (or equivalents) be available for each of the plugins in question.


Code generation can't handle booleans in the parameters dict

Repro:
from evalml.pipelines.utils import generate_pipeline_code
from evalml.pipelines import MulticlassClassificationPipeline
from evalml.pipelines.components import Transformer

class MyTransformer(Transformer):
    name = "I have a bool parameter"

    def __init__(self, do_something=False, random_state=0):
        super().__init__(parameters={'do_something': do_something},
                         component_obj=None,
                         random_state=random_state)

class CustomPipeline(MulticlassClassificationPipeline):
    name = "Custom Pipeline"
    component_graph = [MyTransformer,'Random Forest Classifier']

pipeline_instance = CustomPipeline(parameters={})
code = generate_pipeline_code(pipeline_instance)
print(code)

exec(code)

from evalml.pipelines.multiclass_classification_pipeline import MulticlassClassificationPipeline

class CustomPipeline(MulticlassClassificationPipeline):
	component_graph = [
		MyTransformer,
		'Random Forest Classifier'
	]
	name = 'Custom Pipeline'

parameters = {
	"I have a bool parameter": {
		"do_something": false
	},
	"Random Forest Classifier": {
		"n_estimators": 100,
		"max_depth": 6,
		"n_jobs": -1
	}
}
pipeline = CustomPipeline(parameters)

---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
<ipython-input-5-0e2afc7a82c0> in <module>
     21
     22
---> 23 exec(code)

<string> in <module>

NameError: name 'false' is not defined

Yep, so the problem is that json.dumps converts False to "false" and None to "null". I liked this summary of that.
Ideas for what to do:

In generated code, find/replace "false" to "False" and "true" to "True". This is what we do for "null" --> "None", and is a bit dangerous...
Write code which walks through the parameters dict and does custom conversion. Could try to extend json.JSONEncoder, but that wasn't working well for me yesterday.
Save the parameters in the generated code not as a dict but as JSON. Then, have the generated code load the JSON and provide the result to the component / pipeline as a dict

Option 3 is a little roundabout but I think its the right move.

RE discussion with @bchen1116, for option 3, idea for generated code:
parameters = json.loads("""{
    "key_a": "val_a",
    "key_b": "val_b"
}""")
...

@bchen1116 I believe #1524 handles this for pipelines, but we'll need the same treatment for components


OTP not validating

otp is not getting validated .

Enter OTP (If this takes more than 2 minutes, press Enter to retry): 181596
Validating OTP..
Unable to Validate OTP
Response: {"message": "Endpoint request timed out"}

yes getting this error

This fixed the error:-
base_request_header = {
'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 Edg/90.0.818.66',
'origin': 'https://selfregistration.cowin.gov.in',
'referer': 'https://selfregistration.cowin.gov.in/'
}

it should be fixed in the latest code


[DOC]: remove 'python3' process from the expected nvidia-smi output

How would you describe the priority of this documentation request
None
Please provide a link or source to the relevant docs
https://github.com/NVIDIA/nv-ingest/blob/main/README.md#:~:text=When all services have fully started%2C nvidia-smi should show processes like the following
Describe the problems in the documentation
The output of the nvidia-smi command that is given in the README shows /opt/nim/llm/.venv/bin/python3 process running which is not the case.
(Optional) Propose a correction or improvement
No response

This is incorrect. This is one of the processes run inside the Deplot NIM container


Have a page for browser information

Hi,
When doing support with users, I encounter users that are unable to identify their browser.
Could you have a URL that would indicate clearly the browser name and version to the user? This way I could ask (by email) the user to navigate to this page and ask him/her to copy-paste the information from this page.
By the way, the page would information the user whether the browser is up-to-date or not.
Here the requirements that would make the page useful:

One URL per language

To avoid the user from seeing a page in the wrong language
Ex: /en/browser-info.html ; /fr/browser-info.html ...

Browser name and browser version is displayed in a big visible box
Device or OS information is also displayed in the main visual box
Extra information is visible in a secondary visual box

Hi SandRock,
I am rewriting the site in the moment and indeed i am implementing almost
something like that.
I will take your input and make it like that!
Just need a few more days because at the moment im am moving the whole site
to python
2018-03-10 13:22 GMT+02:00 SandRock<EMAIL_ADDRESS>
Hi,
When doing support with users, I encounter users that are unable to
identify their browser.
Could you have a URL that would indicate clearly the browser name and
version to the user? This way I could ask (by email) the user to navigate
to this page and ask him/her to copy-paste the information from this page.
By the way, the page would information the user whether the browser is
up-to-date or not.
Here the requirements that would make the page useful:

One URL per language

To avoid the user from seeing a page in the wrong language
Ex: /en/browser-info.html ; /fr/browser-info.html ...

Browser name and browser version is displayed in a big visible box
Device or OS information is also displayed in the main visual box
Extra information is visible in a secondary visual box

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/browser-update/browser-update/issues/379, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIErKknXyIEs7wEfeaiYD--DS2ETyQv2ks5tc7eDgaJpZM4SlPZa
.

Hello @josselex, any update on this item?

This is the current state:
http://browser-update.org/what-is-my-browser.html
What do you think?

@josselex  that's a good job. OS info is missing and might be displayed in tiny.
is this going to be a dedicated "browser info" page or the main "you are/not up to date" page?


Expand Container dependsOn parameters to accept Iterable

Builds upon #2221 so that any Iterable is allowed as a dependsOn argument.
Suggested by @bsideup

This was released in https://github.com/testcontainers/testcontainers-java/releases/tag/1.14.0 🎉


Sending JSON data along with file

I'm trying to send a file with some metadata to a Spring Controller at the backend, but I'm not having much luck. I think I narrowed the problem down to the absence of a content-type to go along with the json-data.
The request send is something along the lines of...
------WebKitFormBoundarywdhA8TIFsWhbSoX9
Content-Disposition: form-data; name="meta-data"
{"metadata":{...}}
------WebKitFormBoundarywdhA8TIFsWhbSoX9
Content-Disposition: form-data; name="file"; filename="2014-03-invoice.pdf"
Content-Type: application/pdf
In order for my Spring controller to recognize the meta-data as JSON (to map it to an object defined in my backend) the content type needs to be set to application/json, as shown in these docs... http://docs.spring.io/spring/docs/current/spring-framework-reference/html/mvc.html#mvc-multipart-forms-non-browsers
I've tried using the formDataAppender but I'm either not using it right, or it isn't possible to accomplish this with it.
My Spring controller (for completeness' sake)
	@RequestMapping(value = "/processwithfiles/", method = RequestMethod.POST)
	public void processWithFiles(@RequestPart("meta-data") final Document document,
			@RequestPart("file") final MultipartFile[] files, final HttpServletResponse response) {
		...
	}

This throws an HttpMediaTypeNotSupportedException "Content type 'application/octet-stream' not supported"
I've noticed that when I use the annotation @RequestParam instead, it works, but only if I change the type of the meta-data to String. That would require me to parse this string to a JSON object myself.
Is there a way make sure the request looks like the one in the example...
http://docs.spring.io/spring/docs/current/spring-framework-reference/html/mvc.html#mvc-multipart-forms-non-browsers

In version 3.0.0 you can set the option sendObjectsAsJsonBlob to send the data or field object as a json blob with concent-type application/json in the form data.

I'm having trouble getting this to work. I'm assuming that sendObjectsAsJsonBlob turned into sendFieldsAs. Is that correct? Is there a working example somewhere?

@bgreeley yes that's the equivalent of that option. sendFieldsAs: json-blob

Thanks, @danialfarid. I can't seem to get the content type to set correctly though. I'm trying to it set to application/json. Is there some example code somewhere I could see to see where I'm going wrong?

@bgreeley http://jsfiddle.net/danialfarid/tqgr7pur/ if you send the file with username you will see in the network tab that the username is being sent with content-type application/json.

Thanks, @danialfarid. I see the output. With the following config:
fields: {
    data: {
        caption: 'caption!',
        tags: ['abc', 'def']
    }
},
sendFieldsAs: 'json-blob'

I'm getting the following output:
------WebKitFormBoundaryA
Content-Disposition: form-data; name="data"; filename="blob"
Content-Type: application/json
------WebKitFormBoundaryA
And if have change sendFieldsAs to be "json", I see the following output:
------WebKitFormBoundaryB
Content-Disposition: form-data; name="data"
{"caption":"caption!","tags":["abc","def"]}
------WebKitFormBoundaryB
Is there a reason why the content type couldn't be set to "application/json" in this case? Is this maybe a bug with the library or is this a limitation of FormData? I read through the MDN and saw that FormData could either by a File, Blob, or string. It didn't see any mention of limitations or guidelines around setting content types. Just for reference, I'll throw the link in here:
https://developer.mozilla.org/en-US/docs/Web/API/FormData/Using_FormData_Objects

only blob can have type

Hi Danial,
I am using this service for to file upload, All the things going well, but when you pass korean data as input it is converting to some double byte characters.
Could you please help me? Even you can test  in http://embed.plnkr.co/mTyI676rSKh8WnjJoDQ0/
In the place username please give 안녕.

@raghala  That's just the server response. if you see the network tab you will see that the data is being sent correctly


Add DictionaryArray Constructors (#3879)

Which issue does this PR close?

Part of #3879
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?
Yes, this makes a breaking change to DictionaryArray::try_new to make it consistent with the other arrays which take owned arguments

IMO marking it deprecated and removing it is only meaningful if there is a tangible behaviour change that is liable to cause people to defer making the change. As it stands, changing the arguments to be owned is likely as much a change as adding allow(deprecated)].
My vote is just to get it over and done with, but I will leave this open to see if anybody else weighs in

My vote is just to get it over and done with, but I will leave this open to see if anybody else weighs in

Sounds good to me


added comments to public.po_lines

All queries:
- [ ] Pull request is based on a new branch (not main)
- [ ] Pull request scope is not overly broad
- [ ] Release notes have been added or updated in CHANGES.md
- [ ] Query runs without errors
- [ ] Query output is correct
- [ ] Query logic is clear and well documented
- [ ] Query is readable and properly indented with spaces (not tabs)
- [ ] Table and column names are in all-lowercase
- [ ] Quotation marks are used only where necessary

Report queries:
- [ ] Query has complete user documentation
    - [ ] Purpose of report
    - [ ] Sample output
    - [ ] Query instructions

Derived tables:
- [ ] Query begins with user documentation in comment lines
- [ ] File name is listed in `runlist.txt` after dependencies
- [ ] All columns have indexes
- [ ] Table is vacuumed and analyzed

@natalyapik I am waiting to review this query until you've submitted changes based on the feedback from @AlaoSUL.
@AlaoSUL, great question about whether the public.sql file needs INDEXES and VACUUM ANALYZE! No, that's not necessary here. I think those need to be run when data is added to the table, and our tables in the public schema will have those commands run separately when the tables are created/updated. In this script, we're just doing that final step of adding comments, and the other stuff should already have happened.

Hi @natalyapik! Are you hoping to get this approved by tomorrow? Are there more changes coming?

We can leave it for next release.


Updating Manifest to Malwarebytes.Malwarebytes <IP_ADDRESS>2

Changing the folder version from <IP_ADDRESS> to <IP_ADDRESS>2
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/AzurePipelines run

It look like Azure Pipelines did not work correctly.

Oops! The pipeline terminated unexpectedly.

@stephengillie If you closed and reopened the pull request. Don't say /AzurePipelines run. This is due to wingetbot

@stephengillie Stephen Gillie (TEKsystems, Inc.) Vendor If you closed and reopened the pull request. Don't say /AzurePipelines run. This is due to wingetbot saying #103484 (comment). It caused duplicate run instance on Azure Pipelines. It also cause the pull request validation error after publish-pipeline-succeed.

Thank you for the advice. Unfortunately, I accidentally closed the PR while saying /AzurePipelines run, and so had to reopen it and cause this scenario. I'll do my best to avoid this in the future.

The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case.

This is another Azure Pipelines validation-pipelines is running while the pull-request was merged and closed. Saw that the pipelines was not respond.

Most likely, I changed is all those manifest validation succeed.


[non-substantive] Update fork choice comments for clarity

https://github.com/ethereum/eth2.0-specs/pull/1859
https://github.com/ethereum/eth2.0-specs/pull/1864

non-substantive, no code change


get_data_ready_status should watch 11 bits (not 10)

Section 3.8.2 of the SCD4x datasheet says to check the least significant 11 bits of the returned status. But the code on line 211 in "data_ready" only checks 8+2 = 10 bits. I've never ever seen that unchecked bit get set when data was not ready, but just in case it ever does -- we should AND the MSB with 7 (3 bits + 8) instead of 3 (2 bits + 8) to follow the datasheet.

That's a good catch. Thank you for the really direct references, it was really easy to look up and see. I tried going through the Sensirion provided c code to see what they use, but c is not my specialty. I've got a sensor so I should be able to give it a shot regardless

! can y'all submit a PR?

Yup! I should have one in tonight

Just adding to document:

Closing. Fixed with #12.


Package request: session manager plugin for awscli2

Project description

It requires session manager plugin to port-forward requests to AWS private instances.
With aws-cli and session manager plugin, you can connect to instances in private subnet in secure way.
Is it possible to add option to awscli2 like pkgs.awscli2.override { enableSSM = true; } so that we can optionally install session manager plugin?
Metadata

homepage URL: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html
source URL: https://github.com/aws/session-manager-plugin
license: Apache License 2.0
platforms: unix, linux, darwin

Related package: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/admin/awscli2/default.nix

What you need is ssm-session-manager-plugin.
Try:
nix-shell -p awscli2 ssm-session-manager-plugin --run "aws ssm start-session --target <your-target>"


Failed to add LiveChat SDK with Carthage

I added following line github "livechat/chat-window-ios" ~> 2.0.11 to my Cartfile and run
$carthage update --platform iOS
But it fails with error:
Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /***/Carthage/Checkouts/chat-window-ios/LiveChat.xcodeproj -scheme LiveChat-iOS -configuration Release -derivedDataPath /***/Library/Caches/org.carthage.CarthageKit/DerivedData/10.0_10A255/chat-window-ios/2.0.11 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/4g/4brbld0d2b98dt21y8hgkkjh0000gp/T/chat-window-ios SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /***/Carthage/Checkouts/chat-window-ios)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/4g/4brbld0d2b98dt21y8hgkkjh0000gp/T/carthage-xcodebuild.CWMnqj.log

When I checked log, I found line:
error: Build input file cannot be found: '/***/Carthage/Checkouts/chat-window-ios/Sources/HideInputAccessoryHelper.swift'

Issue fixed by #29. Fix is available in version 2.0.12.


didReceiveIncomingPushWithPayload not called in debug mode

I am using OneSignal to send push notifications.
When I build my app for release mode, notifications arrive just fine. But when building for debug, the didReceiveIncomingPushWithPayload is never called and the notification is ignored. Although on OneSignal it says the notification was delivered.

@rcidt  did you find a solution ?  it's also not getting called in my app

@OriAmir No I have not, but I managed to find a workaround to this, by sending manual push notifications to APNS with cURL.
It seems like the issue lays somewhere on the OneSignal side.

@rcidt Tnx, but it's just for tests no? what do you do in prod? the 'didReceiveIncomingPushWithPayload  function not getting called for me also when I create release build .
Did you try Amazon service for voip ?

@OriAmir seems we have fundamentally different issues.
VoIP Push Notifications work perfectly for me in Production builds. I don't use Amazon for voip.
I suggest you carefully read the new changes in iOS 13 regarding VoIP Notifications. Here is a very straight forward article.
Good luck

So voip push notifications work differently from debug (sandbox server) than on production mode. Keep in mind that just switching to the release scheme will not change this behavior as far as I can tell. Only pushing to TestFlight or the App Store will tell the app to get a production device token, which is what’s needed.  When you build in Xcode the app will request a sandbox device token, which is not valid for production URLs, only the sandbox one (this is when you trigger the notification via a web service or backend).
The best option would be to try pushing to TestFlight and see if the production url for voip push notification sending works then.
If you’re using a package on your backend that doesn’t allow setting the url make sure that it matches the following
Production: ssl://gateway.push.apple.com:2195
Dev: ssl://gateway.sandbox.push.apple.com:2195


Add support for JoinType Bevel from PDF and SVG

Thank you Mr. Johnson for such a great library!
I have one feature request: add support for JoinType Bevel as specified in the PDF specification and the SVG specification. I think that the same definition is used in other graphics frameworks, such as GDI+ and WPF.
Perhaps the following StackExchange post illustrates the difference between the existing JoinType.Square (Thickness in that post) and Bevel (Orthogonal in that post): What is a bevel join of two lines exactly (Illustrator)?

I have one feature request: add support for JoinType Bevel as specified in the PDF specification and the SVG specification.

Both Clipper1 and earlier versions of Clipper2 did perform this exact style of bevel joining (even though they were called Square joins. As per the PDF documentation, this style butt offsets the adjacent segments before triangular filling (see below).
Butt offsetting of adjacent segments (before triangle filling):

After triangle filling:

However, 12 months ago I did change the behavior of Clipper2's Square joins so that squaring/beveling occurred at exactly at 1 delta (ie the offset distance) away from each join (because I believe it just looks so much better, even though the code was much more complex).

Nevertheless, I'm reluctant to have Clipper2 perform 4 join types: miter, round, square (ie current squaring) and bevel (old squaring). That seems like overkill, especially given that most other graph libraries support only 3 join types. Unless there are strong objections, I'd be inclined to revert to the former squaring/bevelling behavior (ie to the style that you're requesting, even though IMHO it doesn't look as good) since this appears to be the most widely implemented behavior.

Honestly, though, if the code is already written, I'd say it would be worth keeping it and going to 4, just because it serves more needs. Changing behavior may break existing users and, again, the effort was already spent implementing it.

Thank you Mr. Johnson for implementing this feature!


LE Audio: BAP: Shell: Add support for broadcast code as the broadcast sink

Is your enhancement proposal related to a problem? Please describe.
Add support for providing a broadcast code when syncing to a broadcast source as the broadcast sink.
Describe the solution you'd like
Add a broadcast_code parameter to cmd_sync_broadcast
Describe alternatives you've considered
N/A
Additional context
N/A

@Thalley Can I work on this issue? I am new to open source and would like to contribute.

@Thalley Can I work on this issue? I am new to open source and would like to contribute.

Absolutely! :) You can draw inspiration from the bap_broadcast_assistant shell module which does handle the broadcast code. I would suggest to have a look at one of my PRs that fixes an issue with it though (https://github.com/zephyrproject-rtos/zephyr/pull/59392). You should be able to more or less do something similar to that

@Thalley Thanks for replying. I will start working on this.

@Thalley Thanks for replying. I will start working on this.

Feel free to ping me here or on Discord if you encounter any issues

Hi @Thalley, I apologize for unassigning myself from the GitHub issue. I have other commitments that require my attention. Sorry for any inconvenience caused.

Hi @Thalley, I apologize for unassigning myself from the GitHub issue. I have other commitments that require my attention. Sorry for any inconvenience caused.

No problem - Let me know if you want to take it up later if it hasn't already been done by then

@Coalby Any progress on this?


Update dockerfile

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@efa59d6). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  Coverage        ?   72.79%
=======================================
  Files           ?       60
  Lines           ?     1632
  Branches        ?      235
=======================================
  Hits            ?     1188
  Misses          ?      345
  Partials        ?       99

Flag
Coverage Δ

unittests
72.79% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
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.


Implement more I/O safety traits.

Implement From<OwnedFd> and Into<OwnedFd> for types that implement FromRawFd and IntoRawFd.
And on Windows, implement From<OwnedSocket>, Into<OwnedSocket>, and AsSocket for types that implement FromRawSocket, IntoRawSocket, and AsRawSocket.

@sunfishcode can you fix this rustfmt CI failure: https://github.com/tokio-rs/mio/actions/runs/11077949124/job/30802514384?pr=1831 ? You can ignore the sanitizer failure.

@sunfishcode can you fix this rustfmt CI failure: https://github.com/tokio-rs/mio/actions/runs/11077949124/job/30802514384?pr=1831 ? You can ignore the sanitizer failure.

Done.

Thanks @sunfishcode


Time to mark this repository as deprecated/archived?

Which service(blob, file, queue) does this issue concern?
All services.
Which version of the SDK was used? Please provide the output of pip freeze.
N/A
What problem was encountered?
It looks like this repository is stale; all new changes have been introduced to the 12.x branch which has been integrated to the main https://github.com/Azure/azure-sdk-for-python repository. No changes have been committed to this repository since December 2019.
Have you found a mitigation/solution?
Please add a prominent migration notice, and archive this repository, if it is indeed deprecated.

@xiafu-msft @zezha-msft could we please get an answer here? The situation right now is extremely confusing. The versions do not seem to be compatible with each other, and there are projects using both at the same time, like azure-cli.

@lmazuel @chlowell - Maybe you can comment?
There's a good PR in this repo that doesn't get a response. #651

Hi @bluca and @cdeil
Some customers are still using azure-storage-blob version<=2.1.0 so this repo is not deprecated yet, but it will be deprecated someday in the future.
Currently this repo only supports existing features.
For that PR #651 we can take a look and let it get merged to master, just we don't plan to release the change.

@cdeil the PR LGTM to me, independently of any deprecation discussion, so I approved it to give my two cents.
@xiafu-msft I think the feedback here is that the main Readme on the frontpage should be trimmed drastically, to make it more explicit that this repo is for maintenance only.


add contributor list to each document

Motivation
Create Contributor List for each documents (#858)
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Run yarn build on the website -- it will update the author list in the metadata
Related PRs
None

@endiliey - does the Netlify preview actually show the contributor list? I don't see it.
This was a v1 feature request that would have been toggled by a siteConfig option. Can we just add this as a v1 update then instead?

@JoelMarcey
It's at the bottom, hahaha.

I do agree if it's on v1. But I think for v2 our paradigm is that we don't want a lot of siteConfig and try to keep things as simple as possible especially on UI related things like this

@endiliey I finished doing git blame on the filePath, but i just realized it may not show the correct contributors instead it show the name of whoever cut the version and the changes after it

That is correct. Do note we have version fallback on v1 & that make things even more complicated.

To be honest I don't agree with this feature on v2 as this would best be left as a plugin and not every user would want it. I personally don't want to see bloated contributor A xxxx% on the docs

Maybe I should say its the same for v1. But its indeed good to have.
WDYT @JoelMarcey @yangshun

I think this feature was always intended for v1.
I have to scope change thoughts two this, if we believe contributors are becoming too difficult or cumbersome:

One thought here is that we could change the scope of this to be where the last content commit to the docs is shown with a link to the commit.
We have a link to the full history of changes for the doc. Basically have a link that brings you directly to something like this: https://github.com/facebook/Docusaurus/commits/master/docs/api-site-config.md

Now that the last updated time is merged, I will start working back on this. Do we want the last updated by field instead? @yangshun @JoelMarcey

Is there anyway to have a link to the commit represented by the last update time and last committer?

It's possible but not sure how much value it provides. Going directly to the list of commits for the file would be more valuable. We could do this in a follow up PR though.

It's possible but not sure how much value it provides. Going directly to the list of commits for the file would be more valuable.

I think we can debate which is more valuable, but I am ok with going to a list of commits (in fact, I may have suggested even that option before). I am quite certain though, having a link to somewhere makes more sense than having no link at all.

I would totally expect as a user to have a link to some commit or a list of commits for the file or something.


feat: 🎏  introduce /readyz endpoint probe

Merge first, then test; I wasn't able to test since the publish pipeline seems to be broken.


Delete the /dist files from git

remove the /dist files from git

Merging to dev. Can be reviewed before the release. This PR just deletes the dist files. the .gitignore changes have already been active from some time.


func joined(separator:) for NSAttributedStrings

🚀
Is your feature request related to a problem? Please describe.
In my projects I use a lot of NSAttributedStrings, but did not find a convenient way how to create an NSAttributedString instance with different attributes for each range.
Describe the solution you'd like
I would like to add these functions:
public extension Array where Element: NSAttributedString {
    // https://stackoverflow.com/questions/32830519/is-there-joinwithseparator-for-attributed-strings
    func joined(separator: NSAttributedString) -> NSAttributedString {
        var isFirst = true
        return reduce(into: NSMutableAttributedString()) { result, element in
            if isFirst {
                isFirst = false
            } else {
                result.append(separator)
            }
            result.append(element)
        }
    }

    func joined(separator: String) -> NSAttributedString {
        joined(separator: NSAttributedString(string: separator))
    }
}

[x] I've read, understood, and done my best to follow the Contributing guidelines before opening this issue.

Fixing

Hacking iPhone


Mobt358 hail reduce size

Addresses metoppv/mo-blue-team#358
Description:
This PR updates the hail size to reduce the hail size based on the wet bulb freezing altitude.
Acceptance test data on branch mobt358-Hail_Reduce_size
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Acceptance data are fine

Acceptance test data merged


Unable to load transforms in sandbox mode when trying to reproduce an error for bug reporting

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

[x] 1. The issue provides a reproduction available on
https://codesandbox.io/p/sandbox/blazing-microservice-vcshyv

Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
When trying to build a reproduction for another bug, I faced a bug in the transform module
Error: Unable to load transform matching mode while resolving /project/sandbox/mode: Error: Cannot find module '/project/sandbox/mode.ts'
To Reproduce Steps to reproduce the behavior:
Go to https://codesandbox.io/p/sandbox/blazing-microservice-vcshyv
Try to run the project.

Expected behavior

Environment:

OS:
@graphql-mesh/...: 0.95.6
NodeJS:

Additional context

Please make sure you follow the syntax in our examples. You are trying to use transforms like below which is wrong. I'd recommend to check our examples again
# Wrong
transforms:
      - mode: wrap
        value: Lift

Ah ... of course.
My bad.
I'll close this and try to build the reproduction for the other issue I'm dealing with.
Thanks @ardatan !


(SHOPPING CART) Error when deleting a product from the cart with the "-" button

To Reproduce
Steps to reproduce the behavior:

Go to https://iced-latte.uk
Add  several different products to the cart
Go to Shopping cart
Click the "-"  button for the selected product

Expected behavior
Product removed from cart
Actual behavior
Application error: a client-side exception has occurred
TypeError: Cannot read properties of undefined (reading 'productQuantity')
Screenshots
https://github.com/user-attachments/assets/4f855b12-bb84-4cf5-8c1e-b6e3138d2717
Additional context
If there is only 1 product in the cart, there is no error when deleting

Hey @ilsinyakov @Diana-Smolnikova, can you assign this to me? I'd like to take it up.

Hey @ilsinyakov @Diana-Smolnikova, can you assign this to me? I'd like to take it up.

Hello. Done


Adding UnknownMedia as Attachment

Adding UnknownMedia object as an Attachment.

@reyesrico,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Ballhead constraints for FABRIK

A copy of https://github.com/godotengine/godot/pull/61994 to better follow the guidelines about rebasing.
Not to be merged yet, as I have not been able to really test its functionality.
https://github.com/godotengine/godot-proposals/issues/750#issuecomment-1009796131
The author referenced a solution of ballhead constraint on the inverse kinematic model for FABRIK. I just ported its code and integrated it in the GUI of Godot.
Any external evaluation is very welcome.

https://github.com/godotengine/godot/runs/6867213499 is failing a task, but I am not able to reproduce the reason why this is the case.
I modified the source as requested by the revisions.

@KaruroChori

as I have not been able to really test its functionality.

did you test it ?
or is it crashing in Godot ?

The last version on my branch does not work, there were some problems with indices which I later solved but never pushed.
Still, I was not satisfied by that implementation, and I continued working on a more general way to integrate different types of constraint and the related UI. The main issue is that some of those I would like to integrate are not as easy on FABRIK and could cause numerical instabilities. I am not an expert in this field and I do not really have much time to study more of it as of now; and I am in the middle of a job hunt, so it might take a while before I can go back working on this, sorry about that :).

no problem at all, I was just checking because I don't think that my code is that good, I am too learning about the IK stuff, thanks for putting time and work into these stuff.

@ywmaa
Can you share your thinking of the current Godot4 IK? Is there progress?


Video isn't rendered.

Hi, thanks for the tutorial, it was quite helpful :smile:
However i noticed a mistake in the code. You have ADVANCED_CONTROL enabled in the params, this means that you have to call mpv_render_context_update() after each call is made to the callback set with mpv_render_context_set_update_callback(). Or you can disable advanced control and the code will work just fine.

Yes, you are right that is "wrong" according to "mpv/render.h" - the strange thing is: on my system it works without any problem if the settings are "1" (enabled). Down the rabbit hole ;-)

Updated the code to use the advanced render path method with the callback - now its fine. Render FPS is now independent of video FPS. Did some additional cleanup.


Multiple video.js recorder on a single page (iOS)

Description
In iOS only one recorder at a time can be used.
Steps to reproduce
Create 2 video.js recorder on a single page. Start the recording in one recorder then in the other recorder. The first recorder is going to continue recording but is black and has no video stream anymore.
Results
Expected
Use a shared stream in both recorders. "Global Stream" as mentioned here: https://webrtchacks.com/guide-to-safari-webrtc/
Actual
Only one recorder at a time is usable.
Additional Information
Please include any additional information necessary here. Including the following:
versions
videojs record
4.3.0
webm-wasm
0.4.1
browsers
iOS Safari v14
OSes
iOS

@tstrohmeier what version of iOS?

The first recorder is going to continue recording but is black and has no video stream anymore.

This actually sounds like this issue: #552

@thijstriemstra Yes webm-wasm actually works on iOS.
#552 is the reason why I use webm-wasm. The RecordRTC recorder seems to have an issue on iOS.
But this thicket is about an other problem/topic. iOS only allows one user media stream at a time. It would be good if you can use one stream in multiple  recorder.

The RecordRTC recorder seems to have an issue on iOS.

No, as you can see in #552 it's Safari that has an issue with MediaRecorder IMO.

But this thicket is about an other problem/topic. iOS only allows one user media stream at a time.

No I think it's the same issue. One user media stream in iOS is causing behavior your see in #552

It would be good if you can use one stream in multiple recorder.

It would be good but I don't see how to fix this, without having to make all kinds of workarounds just for Safari. I don't get paid for this work and spending all my time on Safari is just plain annoying, Apple isn't paying me or something. If it works correctly in all browsers, I would expect it to work in Safari as well, and if it doesn't it's a bug in Safari. As you can see in #552, the latest Safari preview release has fixed the issue and I am certain it will be fixed in iOS as well. Until then I welcome any pull requests but you might as well wait until Safari releases a new version and fix for this issue.

No, as you can see in #552 it's Safari that has an issue with MediaRecorder IMO.

I did not debug on iOS yet but on MacOS Safari v14 I can confirm that MediaRecorder does not exists:
ReferenceError: Can't find variable: MediaRecorder

webm-wasm plugin also uses RecordRTC.

I don't know. I just use the library. The benefit for me is that I can also control bit rate etc.

No I think it's the same issue. One user media stream in iOS is causing behavior your see in #552

Not really. As I wrote the webm-wasm plugin works for me in all browsers (Chrome, Firefox, Safari, Safari iOS).
The only issue I have is that iOS only allows one stream at the time and so I can only use one recorder at the time on iOS/iPadOS. This is expected behavior on iOS.
Here is a good description on it: https://webrtchacks.com/guide-to-safari-webrtc/  Headline: "New getUserMedia() request kills existing stream track" I also don't think that Apple will change this.

It would be good but I don't see how to fix this, without having to make all kinds of workarounds just for Safari. I don't get paid for this work and spending all my time on Safari is just plain annoying, Apple isn't paying me or something. If it works correctly in all browsers, I would expect it to work in Safari as well, and if it doesn't it's a bug in Safari. As you can see in #552, the latest Safari preview release has fixed the issue and I am certain it will be fixed in iOS as well. Until then I welcome any pull requests but you might as well wait until Safari releases a new version and fix for this issue.

I can understand you! I do not have many experience with WebRTC so I can not really help you.
Seems like Apple is doing it's own thing again. I just notice from reading a bit that iOS will never change this behavior and this is why the possibility of getter/setter for the underlying media stream would be a good thing for the future. This would allow to share it between different  recorder instances.

I did not debug on iOS yet but on MacOS Safari v14 I can confirm that MediaRecorder does not exists:
ReferenceError: Can't find variable: MediaRecorder

It should be enabled by default. If not, use these instructions to enable it: https://www.educative.io/edpresso/how-to-enable-the-mediarecorder-api-for-safari But it's buggy for now: #552


Add invoice correction

Added feature to create invoice corrections.
Had to increase "cooldown" otherwise "Request failed with status code 429 (TooManyRequests). Response content: {"message": "Rate limit exceeded"}"

This is always null when I run the tests (using windows), maybe you can double check it.
        private readonly string tokenString = SecretAppSettingReader.ReadSection<SecretAppSetting>("TestSetup").ApiKey ?? "";

Hi @AlexHolly
Thanks for your PR. About the key, you must set the value in your secret.json file.
For this, select "Manage user secrets" (right mouse click on the test program).

This will open the json file. Insert the content of the example file appSecretsExample.json, which is located in the test project.
Then add your ApiKey and save the file.
{
  "TestSetup": {
    "ApiKey": ""
  }
}


Added Toggle Schedules button, ready for demo

Bug: Zoom in is bugged, will be fixed once I transfer over the display schedules from webview to UICollectionsView

Do not approve/ Merge


Adding --port setter to socket_server

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Right now, except for swift lanes, one cannot (without additional ruby code) run multiple fastlane socket server sessions. This would be really nice for parallelization, as well as for environments where localhost:2000 is otherwise spoken for.
Description
The start_server action gains an additional, optional parameter: -p port.  This option (documented in the action itself) sets the port on localhost on which to mount the socket server. Takes four lines of code.
Testing Steps
fastlane action start_server -p 2001 &
nc localhost 2001

Happy connecting!
NB This change just adds three lines of code - it's a small change to open up a lot of power.

@googlebot I signed it!

fwiw circleci says the fastlane.swift test (marked as pending on GH) is green


chore(deps): update common-dev-assets digest to 330b908

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
3d1a2f8 -> 330b908

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

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

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 3.14.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Delegated location permission prompt does not appear immediately

Describe the bug
Hello. I've encountered an issue with Location Delegation feature where the native location permission prompt weirdly appears ONLY if I background and open the app or navigate to external url within the TWA.
I'm using two phones and the newer one has the issue while older one doesn't.
To Reproduce
If I background the app and open it again it appears to call permission prompt twice. Meaning that I have to press back to cancel one and then I will be able to click another prompt to confirm my selection.
Another case is that if I click a button to request permission, the prompt will show if I navigate to another external webpage like login to google page within the TWA.
https://user-images.githubusercontent.com/20887104/230723067-676d780a-d85b-40fe-8995-31e4a8ada614.mp4
Expected behavior
Location permission prompt appears immediately after permission request.
Smartphone (please complete the following information):
The one which doesn't work:

Device: Xiaomi 12T Pro
OS: Android 13 TKQ1.220829.002
MIUI Global 14.0.7
Browser Chrome
Version 111.0.5563.116

The one which works:

Device: Galaxy S10
OS: Android 12 SP10.210812
One Ui 4.1
Browser Chrome
Version 111.0.5563.116

Additional context
My older phone does not have this issue.
I've added android permission to the xml file thinking that for some reason it will help to bypass:
        <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
        <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
        <uses-permission android:name="android.permission.WAKE_LOCK" />
        <uses-permission android:name="android.permission.INTERNET" />
        <uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>

My guess is that some state change is triggered after setting app to background or navigating to another external url within the TWA and then it shows the permission prompt.
Maybe additional Android permissions are required? Or the location delegation service is not called because some kind of events changed in new android version?

I've migrated location query function using Maplibre-gl js geolocate triggers and now appears after couple of clicks.

My guess is because three time clicking tries to turn on -> turn off -> turn on the location and then prompt appears.


Minor wording change in documentation around Java class naming

In the Naming section of
http://flywaydb.org/documentation/migration/java.html
it says
If you need more control over the class name, ...

I would suggest
If you need more control over the version naming than the class name gives you, ...

Woops.  Wrong repository.  Sorry.


Status bar battery percentage overlap

First of all thank you for creating such a great tool, its easy to incorporate and the examples are fantastic.
This is probably more of a feature request than a bug really. Please attached screenshots. My app has menu controller which has the same color as the top view controller, hence I implemented the shadow onto the main view controller, but immediately noticed that it interferes with the Status bar UI if the battery percentage is on from the user side.

I took at look at how other apps handle this, and found that the YouTube app handles this really smartly. When you drag to open the Menu, notice that the status bar changes its color (see screenshot) while the user drags the view, and I absolutely love that feature, and I have no idea as to how to achieve that.

Is it possible to implement something like this? If yes, it would be fantastic.
Please keep me posted. Thanks.

or move status bar, like in mailbox?)


Migrate asset precompile to manifest.js

Sprockets 4 and rails 6 defaults to using the manifest file to
compile assets
https://github.com/rails/sprockets/blob/master/UPGRADING.md#manifestjs
I moved the files from the old assets.precompile config to the new
style, but the lite_mode CSS was a weird one (it is and html file,
not a CSS file)
Need to make sure lite mode still works after this change (and maybe
make it a CSS file instead of html/erb??)

This looks great!
One question though.
Is jquery.js needed anymore? I think this was an unremoved relic from the jqyery removal effort.

@veganstraightedge hmm, lemme look into the jquery thing. I think you are correct


Code of conduct and/or contributing guide

As we have more contributors working on this project, it'll be helpful to clearly define the basic steps to get involved via Github Issues. We should probably encourage discussion in Issues and ask folks to mention that they're working on something so we can avoid duplicated work.
This doc doesn't have to include technical details about getting a local dev setup going (that can stay in the existing dev guide), but perhaps an overview of the typical way that folks (especially newer contributors) can get involved.
What do folks think?

I'm supportive of adding one though I don't think we really need one at this point and can mentor and ramp newcomers up on an adhoc basis. That said, we could probably just add a contributing.md guide in the repo itself. (We could also use GitHub's Wiki functionality, but I think it's better if guides/documentation live in the repo where they can be more easily versioned and kept up-to-date and also more easily "code reviewed")

Yeah I think just adding a contributing.md to the repo should be sufficient. I was envisioning a doc that we could point new contributors to when they're getting started so we don't have to repeat common steps, advice, etc.


Change GMP_DIR argument to CMAKE_PREFIX_PATH

I think you sent it to the wrong repo?

Ah I see, it will become part of my PR. Thanks!


Add support for css imports

This is the initial implementation for handling css @import statements.

[X] Get basic @import working.
[x] Handle all levels of CSS imports.
[x] Add support for all allowed constructions of @import.

Closes #2

Ping @jxnblk
What's the status on this PR, would you like me to provide something more?

Oh, sorry I dropped the ball on this. I'll try to take a look at it later today and get it merged in.

No worries, I had forgotten about this myself, too. Sounds good. Thanks for your time.


all supplementary outputs affect incremental builds

Resolves rdar://75536036
When a new supplementary output is added to an otherwise up-to-date incremental build, the compiler currently ignores the new output and skips all the compilation steps. This PR changes all the supplementary-output options to contribute to incremental-build fingerprints.

@swift-ci test


Build(deps-dev): Bump @babel/plugin-transform-typescript from 7.22.10 to 7.22.11 (#5094)

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

Merged in 5c7bab7ff7d7e98384de1d8e16ca0565c221a522


send file/picture feature

Hi All
I'd like to have the feature of sending picture or file to the chat session.
Is there anybody working on this feature? Do you know which XEP we should implement for that?
Thanks,Xu

Well, this particular feature could be implemented in many ways using XMPP protocol,  but for instance Conversations.im uses xep-0363 to send image files.
Sorry,  but currently i'm almost completely focused on PEP implementation. This should be something to be considered in a future roadmap.
Additionally if your really feel you can't live without this, collaborations are always welcome. 😉


Support for setting bindings in editor

Hey, I just found this library, and it is pretty nice!
Though a major downside currently is not being able to set bindings in editor in my opinion.
I did see that it was in the possible future plans. I was wondering what the status of that would be. And what your plan for going about it would be? I could possibly see about taking a swing at implementing it. Though I am new to Godot, but not to programming.
Thanks :)

Hey there,
Thanks for trying out the library!
I haven't thought too much about how this would be implemented, I'm also pretty new to Godot plugins.
But I'm thinking there would possibly need to be an autoload that would read in the config created in the editor and create a binding context for the scene to then create the bindings against - maybe as a static list on the BindingContext so they can be retrieved at runtime.
I think there would be some limitations, such as not being able to create validations from the editor, but that might be worked around by using resources or by changing validations so they're implemented as a type instead of just lambdas (similar to ValueFormatters) .
Absolutely feel free to have a crack at an implementation. I don't have any concrete time frame planned to start looking at it at the moment, but happy to help with any questions

But I'm thinking there would possibly need to be an autoload that would read in the config created in the editor and create a binding context for the scene to then create the bindings against - maybe as a static list on the BindingContext so they can be retrieved at runtime.

Hmm, so you are thinking having a object (node?) that holds the bindings for all of the nodes, that you then load in?
When I was looking at doing my own system, one big issue I was running in to was running in to was how to actually set the bindings in editor. There was two parts to it, one was that there was no way to add the binding info to the control nodes. So needed to resort to inheriting from a node and implementing a IBindableControl interface to hold the info. The other issue was that Godot doesn't support structs in the inspector. So there was no good way to create a pair of property paths (controlProperty, viewModelProperty). Not sure if there is a way around this point using a GDExtension or something.
Another option I had thought of was having a BindingNode that you would add as a child to any node you wanted to bind to, and it would hold the binding data. It would keep the bindings local, but also be a pain.
Anyway, just some thoughts let me know your thinking :)

Hey @MechWarrior99, apologies for the super late reply!
I was doing a bit of digging and it could be possible to use the node metadata attributes to store data about the bindings on each node. Another method might be to use a node that gets placed in the scene that can be used to hold references to other nodes in the tree and the binding info for those nodes.
The first option of using metadata might make the user experience better as the only thing to interact with would be editor panels that are included as part of the plugin. However I think the method of using a custom node for the binding context would be a bit easier to implement.
I'll probable spend some time in the coming weeks fleshing out these ideas a bit further and testing them, but if you're still interested, these ideas might be some additonal starting off points.

Hey @Dangles91 no problem. I had taken a break and came back to this anyway.
Metadata was exactly the sort of thing I was looking for, I think it would be a great use for it. It lets us have a sort of structure like XAML has.
I did some experimenting and got it working. My thinking was this. We use strings for the metadata, the name of the metadata would use a Binding_ prefix, followed by the name of the property to bind to Binding_Value. And the value would effectively be like tags in XAML. Path= for the data source binding path, and Mode= for the binding mode. So Path=TestValue, Mode=TwoWay. This pattern lets it be similar to XAML, and we could expand on it to add more functions. I did try to use a single dictionary instead, but they can't be typed, so you have to specify the type of the key and value each time which is a pain.

For doing the actual binding, I was thinking to have a ControlBinding node which would be at the root of the UI nodes tree. You would give it a BindingContext and it would iterate over every descendent and try to bind it using the metadata if the node had any.
It can also subscribe to the GetTree().NodeAdded event, so it can automatically bind to any node that gets added.
I think this seems like a decent approach, and would be fully codeless binding. Let me know what your thoughts though.
There is two thing still tripping me up on how and where to go about implementing. I was thinking it would be good to be able to specify a BindingContext for subtrees of nodes, you probably don't want the whole UI binding to the same context. But not sure what the API for that should look like. Maybe a extension method for Control nodes like void Bind(this Control control, BindingContext ctx)?
We have to store the actual binding in a static(?) dictionary so that we can find it from child nodes so we know what to bind to.
The other thing that I am not sure about is only sort of related. And that is how and if we should do bindings that are relative to the parent path. So if you have a Vector3 control for example. Have the X, Y, and Z fields have a data binding path of Path=X for the X control field, and Y for Y, and Z for Z. That way you bind a position to the Vector3 control and the X, Y, Z are automatically handled. But maybe I am not thinking of this right. And maybe this is more of a separate issue really...
Anyway, let me know what you think!


Term.desugaring

Prerequisites:

[x] Online mirror with support for Ref.symbol (#606)

Some code analysis tools (e.g. https://github.com/scalacenter/scalafix) may want to inspect full internal representation of code after typechecking, and we may need to provide an API for that.
However, I'd like to avoid exposing a generic Term.desugaring API as much as possible, because desugarings may and will be terribly implementation-specific. Instead, I think it may be enough to introduce APIs like:

Apply.inferredTargs
Apply.inferredArgs
Same for Pat.Extract
...

We'll need practical experience to proceed with this ticket. @olafurpg, @DavidDudson, @ShaneDelmore, @mutcianm please let me know what you think.

@olafurpg What do you think about this one after working on https://github.com/scalameta/scalameta/pull/1000?

How is this different from sugars?

It's not. Let's close this one and then evolve the functionality that you implemented in #1000 according to the arising use cases.


Autopagination not working with multiple sources

Hey, I think I found an issue with autopagination. When adding a second subgraph to the sources list in .graphclient.yml it stops working and errors out with the following:
/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/delegate/cjs/checkResultAndHandleErrors.js:28
        const combinedError = new utils_1.AggregateError(errors, errors.map(error => error.message).join(', \n'));
                              ^
AggregateError: The `first` argument must be between 0 and 1000, but is 2500,
The `first` argument must be between 0 and 1000, but is 2500,
The `first` argument must be between 0 and 1000, but is 2500,
... repeated many times
The `first` argument must be between 0 and 1000, but is 2500,
The `first` argument must be between 0 and 1000, but is 2500
    at mergeDataAndErrors (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/delegate/cjs/checkResultAndHandleErrors.js:28:31)
    at checkResultAndHandleErrors (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/delegate/cjs/checkResultAndHandleErrors.js:9:38)
    at Transformer.transformResult (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/delegate/cjs/Transformer.js:42:79)
    at /Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/delegate/cjs/delegateToSchema.js:58:28
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.rawSourceContext.<computed>.<computed> [as allocationCreatedEvents] (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-mesh/runtime/cjs/in-context-sdk.js:186:42)
    at async Promise.all (index 0)
    at async promiseForObject (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:14:28)
    at async subschemaExecute (/Users/tomi/git/thegraph/graphclient-test/node_modules/@graphql-mesh/runtime/cjs/useSubschema.js:79:32)
    at async /Users/tomi/git/thegraph/graphclient-test/node_modules/@envelop/core/cjs/orchestrator.js:376:27 {
  path: [ 'allocationCreatedEvents' ],
  locations: undefined,
  extensions: [Object: null prototype] {}
}

I've built a simple repo that reproduces the issue here: https://github.com/tmigone/graphclient-test

Fixed in<EMAIL_ADDRESS>:)


Type guards on bound generic parameters don't compile

Seems like type guards on bound generic parameters don't compile - the compiler doesn't take the constraint into account.

TypeScript Version:  2.9
Search Terms:
generic type guard
Code
function isOne<T extends 1 | 2 | 3>(t: T): t is 1 { return t === 1; }

Expected behavior:
Compiles without errors
Actual behavior:
A type predicate's type must be assignable to its parameter's type.
  Type '1' is not assignable to type 'T'.

Playground Link:
http://www.typescriptlang.org/play/#src=function isOne<T extends 1 | 2 | 3>(t%3A T)%3A t is 1 { return t %3D%3D%3D 1%3B }
Related Issues:
Could not tell

What is the intent of T here? It's unnecessary

Here is an example that is slightly less (but still quite) contrived (not the original code, but not a minimal nonsensical test case either):

type Widget = { value: number; }
const MyWidget: Widget = { value: 1 }

type Joojoo = { value: string }
const MyJoojoo: Joojoo = { value: '1' }

const AllWidgets = { MyWidget };
const AllJoojoos = { MyJoojoo };

enum ThingTypes {
  Widget = 1,
  Joojoo = 2
}

type IdOf<T extends ThingTypes> =
T extends ThingTypes.Widget
    ? keyof typeof AllWidgets
    : T extends ThingTypes.Joojoo ? keyof typeof AllJoojoos : never

class Thing<T extends ThingTypes> {
  thingType: T;
  thingId: IdOf<T>;
}

function isWidget(t:Thing<any>): t is Thing<ThingTypes.Widget> {
  return t.thingType === ThingTypes.Widget;
}

function isJoojoo(t: Thing<any>): t is Thing<ThingTypes.Joojoo> {
  return t.thingType === ThingTypes.Joojoo;
}

function valueOf<T extends ThingTypes>(self: Thing<T>): T extends ThingTypes.Widget
    ? typeof AllWidgets[keyof typeof AllWidgets]
  : T extends ThingTypes.Joojoo ? typeof AllJoojoos[keyof typeof AllJoojoos] : never {

    if (isWidget(self)) {
      let tid = self.thingId;
      return AllWidgets[self.thingId];
    } else if (isJoojoo(self)) {
      return AllJoojoos[self.thingId];
    } else {
      throw new Error('What is this?')
    }
}
declare let v: Thing<ThingTypes.Widget>

let x = valueOf(v)

Since the guard can't narrow over the type parameter, it complains that the indexer type is wrong.

The most minimal example is

enum ThingTypes {
  Widget = 1,
  Joojoo = 2
}

class Thing<T extends ThingTypes> {
  thingType: T;
  thingData: string;
}

function isWidget<T extends ThingTypes>(t:Thing<T>): t is Thing<ThingTypes.Widget> {
  return t.thingType === ThingTypes.Widget;
}

function isJoojoo<T extends ThingTypes>(t: Thing<T>): t is Thing<ThingTypes.Joojoo> {
  return t.thingType === ThingTypes.Joojoo;
}

But that can be worked around using any - however the above full example demonstrates that workaround is not perfect

@spion You want to write
function isOne<T extends 1 | 2 | 3>(t: T): t is (T&1) { return t === 1; } // note the intersection

this way your argument retains its relationship with T, but is also known to be a 1.

@weswigham the more complex example in the middle explains why that doesn't always work - I really don't want to keep the T because the conditional type IdOf<> wont be able to extract the right set of string keys so I can index into AllWidgets with it.

With the new example, you still have not answered @RyanCavanaugh question:

What is the intent of T here? It's unnecessary

I would have written the type guard as:
function isWidget(t: Thing<ThingTypes>): t is Thing<ThingTypes.Widget> {
    return t.thingType === ThingTypes.Widget;
}

@mhegazy See the conditional type in my second comment:
type IdOf<T extends ThingTypes> =
T extends ThingTypes.Widget
    ? keyof typeof AllWidgets
    : T extends ThingTypes.Joojoo ? keyof typeof AllJoojoos : never

I believe a type variable is required there, so in that case the type guard you wrote will keep the T around and the conditional type wont be able to resolve the union-of-keys type.

BTW for me personally this "bug" is really is low priorty now (needs a very specific interaction of all of type guards, conditional types and mapped types to reproduce, and we found a workaround) so feel free to ignore it. I am still a little curious to know whether there is any good reason to forbid a type guard from removing the type variable.


Simulator not launched in latest XCode 4.3

Hi,
,,After upgrade to XCode 4.3, frank-cucumber no longer launch simulator.
Running cucumber show following:
h: line 1:  9190 Trace/BPT trap: 5       /Users/siuying/.rvm/gems/ruby-1.9.3-p125/gems/sim_launcher-0.3.7/lib/sim_launcher/../../native/iphonesim "showsdks" 2>&1
sh: line 1:  9193 Trace/BPT trap: 5       /Users/siuying/.rvm/gems/ruby-1.9.3-p125/gems/sim_launcher-0.3.7/lib/sim_launcher/../../native/iphonesim "launch" "/Users/siuying/Library/Developer/Xcode/DerivedData/MagicTimer-gajumfadzysibzewdxyvagveaupe/Build/Products/Debug-iphonesimulator/MagicTimer Frankified.app" "" "iphone" 2>&1

PING FAILED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It worked if I launch the simulator manually. There is a thread talked about this (http://groups.google.com/group/frank-discuss/browse_thread/thread/2a34c5b080ea6b78), it seems there is a workaround there, but it would better if it just work if I install frank.
Thanks.

Oh this is already reported in Sim-Launcher issue https://github.com/moredip/Sim-Launcher/issues/2


[Spark][3.0] Fix a data loss bug in MergeIntoCommand

This is a cherry-pick of https://github.com/delta-io/delta/pull/2128 to delta-3.0 branch.
Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description
Fix a data loss bug in MergeIntoCommand.
It's caused by using different spark session config object for PreprocessTableMerge and MergeIntoCommand. In PreprocessTableMerge, the config value is from the spark session which is given for DeltaTable. In MergeIntoSchema it refers SQLConf.get which is from the active session of the current thread. It can be different when user set another new spark session or active session just doesn't set properly before the execution.
If source dataframe has more columns than target table, auto schema merge feature adds additional nullable column to
target table schema. The updated output projection built in PreprocessTableMerge, so matchedClauses and notMatchedClauses contains the addtional columns, but target table schema in MergeIntoCommand doesn't have it.
As a result, the following index doesn't indicate the delete flag column index, which is numFields - 2.
      def shouldDeleteRow(row: InternalRow): Boolean =
        row.getBoolean(outputRowEncoder.schema.fields.size)

row.getBoolean returns getByte() != 0, which causes dropping rows randomly.
matched rows in target table loss
Also as autoMerge doesn't work
newly added column data in source df loss.
The fix makes sure setting active session as the given spark session for target table. The PR applies the fix for other command to avoid any inconsistent config behavior.
Fixes https://github.com/delta-io/delta/issues/2104
How was this patch tested?
I confirmed that https://github.com/delta-io/delta/issues/2104 is fixed with the change.
I confirmed the following by debug log message without the change:

matchedClauses has more columns after processRow
row.getBoolean(outputRowEncoder.schema.fields.size) refers random column value (It's Unsafe read)
canMergeSchema in MergeIntoCommand is false, it was true in PreprocessTableMerge

Does this PR introduce any user-facing changes?
Yes, fixes the data loss issue

[error] /home/runner/work/delta/delta/spark/src/main/scala/io/delta/tables/DeltaOptimizeBuilder.scala:84:5: not found: value withActiveSession
[error]     withActiveSession(sparkSession) {
[error]     ^

https://github.com/delta-io/delta/actions/runs/6497686911/job/17647326170?pr=2156


Fixed a crash due to unwrap

Seems that it would panic if I would hold down F5 for a few seconds from a browser (I'm using nginx, if that's important).  It panicked saying something about an unwrap from libcore/result.rs:729.  Not sure exactly what unwrap was causing it, as it didn't really give me the place.  The best I know of how to use gdb said something along the lines of a SIGPIPE causing it.
But anyway, the panic seems fixed with something from this.  Most of this is probably useless, I didn't spend any time trying to figure out the code beyond minimizing the amount of of unwraps.

Did you use run_tcp? I suspect what happened was the request got terminated early so the server decided to close its communication link with the library (hence the SIGPIPE).

I was forced to use run_tcp because run doesn't work (Though I'm not too affiliated with using FastCGI, so this stuff is new to me, maybe I need to do something else?).
Also, the part you requested be reverted seems to be the part that is causing the program to crash.

No, run_tcp is correct for setups like Nginx.

Thanks for the patch!


Maintain order when loading iterable values from config files

Fixes #774.

Is there anything I can do to facilitate merge of this PR?

Looks great! Thank you!


Set comments for default values

I have modified my posts here. Sorry maybe I didn't fully understand the structure of this library. I only want to add comments to those ConfigValues generated by code. I think it's a good idea to provide a way to add comments to values in those from functions (fromMap, fromAnyRef and others). In factory functions in ConfigValueFactory, it needs one parameter to add comments to the value, like this:
public static ConfigValue fromAnyRef(Object object, String originDescription, List<String> comments)

(or use a single String for comments.) But it's difficult to add comments to those sub values given in the map. If we can add another class ValueWithComments, we can write this:
Map<String, Object> configMap = new HashMap();
configMap.put("key", new ValueWithComments("value", "Comment for the entry.");
ConfigValue configValue = ConfigValueFactory.fromMap(configMap, "Default values in code", "Comment for the object.");

I really want to know how you think about this. Thank you very much!

And I wonder why comment is a part of origin, instead of a part of the value. Comments vary from value to value, even among values from a same origin. And they are usually used to make it easier for user to understand the usage of each config value. So why not store comments in value?

For parsing extra formats such as YAML in third-party code, we had also discussed the lack of constructors for ConfigOrigin https://github.com/typesafehub/config/pull/169#issuecomment-45568162
I do think there should be a way to do this. Maybe it is just a method on ConfigValue like withOrigin that modifies its origin, and methods on ConfigOrigin for modifying the origin itself (like withComments, etc.).

Thank you for your reply!
I have been working on a new branch trying to make it possible to give object/list a different origin from their entries. And now we can set comments to ConfigValue (only the ConfigValue itself, not the entries of a ConfigObject or a ConfigList) when calling fromAnyRef.
Besides, I also want to add support for containing ConfigValue objects in a Map or Iterable passed to fromAnyRef, so we don't need to use withKey for many times. I think with these two new api, we would be able to control the origin of ConfigValues when constructing them.

I believe #243 solved this issue (reopen if not)


Bug: nf-test v0.8.2 fails to parse regex strings when loaded in params block

Hi @lukfor ,
We started using v0.8.2 and started updating some older testcases. What we noticed is that Groovy fails to parse template script when we try to load a regex string containing special characters. I will document the test case below and finally the error message.
workflow..nf
process exampleProc {

    storeDir "${outputDir}/exampleProc"
    input:
        tuple(
            val(outputDir),
            val(localOutputDir),
            val(someRegexString)
        )

    output:
        tuple(
            val(outputDir),
            path("example_output/example*.txt")
        )

    shell:
        """
        mkdir -p !{localOutputDir}
        echo !{someRegexString} > "!{localOutputDir}/example1.txt"
        """
}

workflow PipeWf {
    take:
        inputCh

    main:
        inputCh
            | exampleProc
            | set { outputCh }

    emit:
        outputCh

workflow.nf.test

nextflow_workflow {

    name "Test workflow"
    script "testing_examples/workflow.nf"
    workflow "PipeWf"

    test("Output will exist in default outputDir") {

        when {

            params {
                outDir = "$outputDir"
                load("params.yaml")
            }
            workflow {
                """
                input[0] = Channel.of([params.outDir,params.localOutputDir])
                """
            }
        }

        then {
              assert workflow.success
              assert path("${outputDir}/exampleProc/example_output").exists()
            }
    }
}

params.yaml
localOutputDir: "example_output"
someRegex: '^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$'

Finally, error message:
Test workflow

  Test [6c7a7547] 'Output will exist in default outputDir' FAILED (0.025s)

  groovy.lang.GroovyRuntimeException: Failed to parse template script (your template may contain an error or be trying to use expressions not currently supported): startup failed:
  SimpleTemplateScript1.groovy: 1: Unexpected character: '"' @ line 1, column 13.
     out.print("""localOutputDir: \"example_output\"
                 ^

  1 error

FAILURE: Executed 1 tests in 0.031s (1 failed)

I have tried in various combination, however the regexes keep throwing these errors. Is this a bug or I simply am not aware of some Groovy limitations?

Hi Ivo, thanks! It seems you have to escape \ and $, otherwise Groovy expects a template variable.
localOutputDir: "example_output"
someRegex: '^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}\$'

Since version 0.8.2, it is possible to use variables such as ${projectDir} in params.yaml. This explains the broken behaviour.