text:
Unable to fund the app on mainnet (android)

I deployed the mainnet app on my android phone; this behavior happened for both latest master and 1.0.11.
I tried to send multiple payments from both Breez and Phoenix wallet but the channel always got force closed on the coordinator:
Note: sending funds to the app on Philipp's iPhone worked.
Link to Grafana showing relevant coordinator logs of the last try:
Common labels: {"container":"coordinator","job":"systemd-journal","setup":"get10101-mainnet","unit":"docker.service"}
Line limit: "1000 (41 returned)"
Total bytes processed: "1.07  MB"

2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088874911Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864416250649116673","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088861865Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864417350187679745","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088849315Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864259020466618369","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088837207Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 863583920324476929","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088818618Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864228234149232640","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088802722Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864154566783991809","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.088778435Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 865292561450532864","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.087180323Z","level":"DEBUG","fields":{"message":"Generating channel_reestablish events for 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::channelmanager","log.module_path":"lightning::ln::channelmanager","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/channelmanager.rs","log.line":6608},"target":"lightning::ln::channelmanager"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.087157585Z","level":"INFO","fields":{"message":"Received peer Init message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: required, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: none","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1237},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:06Z	{"timestamp":"2023-04-26T16:10:06.044015078Z","level":"DEBUG","fields":{"message":"Finished noise handshake for connection with 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1109},"target":"lightning::ln::peer_handler"}
2023-04-26T16:10:04Z	{"timestamp":"2023-04-26T16:10:04.874133928Z","level":"DEBUG","fields":{"message":"Marking channels with 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 disconnected and generating channel_updates. We believe we can make future connections to this peer.","log.target":"lightning::ln::channelmanager","log.module_path":"lightning::ln::channelmanager","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/channelmanager.rs","log.line":6553},"target":"lightning::ln::channelmanager"}
2023-04-26T16:09:11Z	{"timestamp":"2023-04-26T16:09:11.854600657Z","level":"DEBUG","fields":{"message":"Error handling message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97; ignoring: No existing channels for node_announcement","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1196},"target":"lightning::ln::peer_handler"}
2023-04-26T16:08:11Z	{"timestamp":"2023-04-26T16:08:11.984993983Z","level":"DEBUG","fields":{"message":"Error handling message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97; ignoring: No existing channels for node_announcement","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1196},"target":"lightning::ln::peer_handler"}
2023-04-26T16:07:11Z	{"timestamp":"2023-04-26T16:07:11.874740726Z","level":"DEBUG","fields":{"message":"Error handling message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97; ignoring: No existing channels for node_announcement","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1196},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158333295Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864416250649116673","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158320483Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864417350187679745","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158306975Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864259020466618369","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158292709Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 863583920324476929","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158272395Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864228234149232640","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.158255291Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864154566783991809","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.15822847Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 865292561450532864","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.156667754Z","level":"DEBUG","fields":{"message":"Generating channel_reestablish events for 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::channelmanager","log.module_path":"lightning::ln::channelmanager","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/channelmanager.rs","log.line":6608},"target":"lightning::ln::channelmanager"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.156603695Z","level":"INFO","fields":{"message":"Received peer Init message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: required, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: none","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1237},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:47Z	{"timestamp":"2023-04-26T16:04:47.118826312Z","level":"DEBUG","fields":{"message":"Finished noise handshake for connection with 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1109},"target":"lightning::ln::peer_handler"}
2023-04-26T16:04:45Z	{"timestamp":"2023-04-26T16:04:45.00390037Z","level":"DEBUG","fields":{"message":"Marking channels with 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 disconnected and generating channel_updates. We believe we can make future connections to this peer.","log.target":"lightning::ln::channelmanager","log.module_path":"lightning::ln::channelmanager","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/channelmanager.rs","log.line":6553},"target":"lightning::ln::channelmanager"}
2023-04-26T16:04:11Z	{"timestamp":"2023-04-26T16:04:11.948719178Z","level":"DEBUG","fields":{"message":"Error handling message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97; ignoring: No existing channels for node_announcement","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1196},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:56Z	{"timestamp":"2023-04-26T16:03:56.324964093Z","level":"DEBUG","fields":{"message":"Got Err message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97: Peer sent shutdown pre-funding generation","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1304},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:56Z	{"timestamp":"2023-04-26T16:03:56.197348145Z","level":"DEBUG","fields":{"message":"Handling Shutdown event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for channel 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1681},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:55Z	{"timestamp":"2023-04-26T16:03:55.794885222Z","level":"DEBUG","fields":{"message":"Handling SendOpenChannel event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for channel 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1611},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:55Z	{"timestamp":"2023-04-26T16:03:55.794812256Z","level":"INFO","fields":{"message":"Started channel creation for in-flight payment","peer":"02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","temp_channel_id":"40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269"},"target":"ln_dlc_node::ln::event_handler"}
2023-04-26T16:03:55Z	{"timestamp":"2023-04-26T16:03:55.692101823Z","level":"INFO","fields":{"message":"Found connection to target peer. Continuing HTLCIntercepted event.","target_node_id":"02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97"},"target":"ln_dlc_node::ln::event_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931181141Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864416250649116673","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931168668Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864417350187679745","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931151362Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864259020466618369","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931133094Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 863583920324476929","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931116585Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864228234149232640","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931101653Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 864154566783991809","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.931078103Z","level":"DEBUG","fields":{"message":"Handling SendChannelAnnouncement event in peer_handler for node 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97 for short channel id 865292561450532864","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1693},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.929447168Z","level":"DEBUG","fields":{"message":"Generating channel_reestablish events for 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::channelmanager","log.module_path":"lightning::ln::channelmanager","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/channelmanager.rs","log.line":6608},"target":"lightning::ln::channelmanager"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.929418454Z","level":"INFO","fields":{"message":"Received peer Init message from 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97: DataLossProtect: supported, InitialRoutingSync: not supported, UpfrontShutdownScript: supported, GossipQueries: supported, VariableLengthOnion: required, StaticRemoteKey: required, PaymentSecret: required, BasicMPP: supported, Wumbo: supported, ShutdownAnySegwit: supported, OnionMessages: not supported, ChannelType: supported, SCIDPrivacy: supported, ZeroConf: supported, unknown flags: none","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1237},"target":"lightning::ln::peer_handler"}
2023-04-26T16:03:11Z	{"timestamp":"2023-04-26T16:03:11.89066963Z","level":"DEBUG","fields":{"message":"Finished noise handshake for connection with 02a8dda36be280ad3ed7f7c0a039f2fa8c565272dfe51b5e80986e34cc9ea41f97","log.target":"lightning::ln::peer_handler","log.module_path":"lightning::ln::peer_handler","log.file":"/home/runner/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/6df5761/lightning/src/ln/peer_handler.rs","log.line":1109},"target":"lightning::ln::peer_handler"}

app logs recording the channel closue
I/flutter ( 1003): | 2023-04-26 12:03:56.906 | LogLevel.INFO | Received event event: OpenChannelRequest { temporary_channel_id: [64, 131, 58, 194, 109, 74, 137, 28, 196, 194, 155, 141, 153, 167, 8, 163, 84, 188, 34, 151, 13, 200, 63, 78, 91, 48, 20, 164, 47, 177, 2, 105], counterparty_node_id: PublicKey(565115c265b0815e09119fb775d308dda5d75abf2e7ff093ac4daa1cecdbe82af03ebe586f0fcadcf115e0afe2d5e520bcc8e5aa63110ad02b7736a0f518b2e2), funding_satoshis: 200000, push_msat: 0, channel_type: [0, 16] }
I/flutter ( 1003): | 2023-04-26 12:03:56.907 | LogLevel.INFO | Accepting 0-conf channel request counterparty: 022ae8dbec1caa4dac93f07f2ebf5ad7a5dd08d375b79f11095e81b065c2155156,funding_satoshis: 200000,push_msat: 0
I/flutter ( 1003): | 2023-04-26 12:03:56.913 | LogLevel.DEBUG | Successfully handled event event: "OpenChannelRequest { temporary_channel_id: [64, 131, 58, 194, 109, 74, 137, 28, 196, 194, 155, 141, 153, 167, 8, 163, 84, 188, 34, 151, 13, 200, 63, 78, 91, 48, 20, 164, 47, 177, 2, 105], counterparty_node_id: PublicKey(565115c265b0815e09119fb775d308dda5d75abf2e7ff093ac4daa1cecdbe82af03ebe586f0fcadcf115e0afe2d5e520bcc8e5aa63110ad02b7736a0f518b2e2), funding_satoshis: 200000, push_msat: 0, channel_type: [0, 16] }"
I/flutter ( 1003): | 2023-04-26 12:03:56.915 | LogLevel.DEBUG | lightning::ln::peer_handler: Handling SendAcceptChannel event in peer_handler for node 022ae8dbec1caa4dac93f07f2ebf5ad7a5dd08d375b79f11095e81b065c2155156 for channel 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269
I/flutter ( 1003): | 2023-04-26 12:03:57.112 | LogLevel.INFO | lightning::ln::channelmanager: Received a shutdown message from our counterparty for channel 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269.
I/flutter ( 1003): | 2023-04-26 12:03:57.113 | LogLevel.ERROR | lightning::ln::channelmanager: Closing channel 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269 due to close-required error: Peer sent shutdown pre-funding generation
I/flutter ( 1003): | 2023-04-26 12:03:57.117 | LogLevel.DEBUG | lightning::ln::channelmanager: Finishing force-closure of channel with 0 HTLCs to fail
I/flutter ( 1003): | 2023-04-26 12:03:57.120 | LogLevel.ERROR | lightning::ln::channelmanager: Peer sent shutdown pre-funding generation
I/flutter ( 1003): | 2023-04-26 12:03:57.125 | LogLevel.INFO | Received event event: ChannelClosed { channel_id: [64, 131, 58, 194, 109, 74, 137, 28, 196, 194, 155, 141, 153, 167, 8, 163, 84, 188, 34, 151, 13, 200, 63, 78, 91, 48, 20, 164, 47, 177, 2, 105], user_channel_id: 0, reason: ProcessingError { err: "Peer sent shutdown pre-funding generation" } }
I/flutter ( 1003): | 2023-04-26 12:03:57.129 | LogLevel.INFO |
I/flutter ( 1003): Channel closed channel: 40833ac26d4a891cc4c29b8d99a708a354bc22970dc83f4e5b3014a42fb10269,reason: ProcessingError { err: "Peer sent shutdown pre-funding generation" }
I/flutter ( 1003): | 2023-04-26 12:03:57.132 | LogLevel.DEBUG | Successfully handled event event: "ChannelClosed { channel_id: [64, 131, 58, 194, 109, 74, 137, 28, 196, 194, 155, 141, 153, 167, 8, 163, 84, 188, 34, 151, 13, 200, 63, 78, 91, 48, 20, 164, 47, 177, 2, 105], user_channel_id: 0, reason: ProcessingError { err: \"Peer sent shutdown pre-funding generation\" } }"

Your channel was not opened due to a BDK error on the coordinator side:
{"timestamp":"2023-04-26T16:03:56.197273914Z","level":"ERROR","fields":{"message":"Cannot open channel due to not being able to create funding tx","err":"BDK wallet error"},"target":"ln_dlc_node::ln::event_handler"}

That most likely means that the coordinator did not have any funds to open the just in time channel.

Your channel was not opened due to a BDK error on the coordinator side:

{"timestamp":"2023-04-26T16:03:56.197273914Z","level":"ERROR","fields":{"message":"Cannot open channel due to not being able to create funding tx","err":"BDK wallet error"},"target":"ln_dlc_node::ln::event_handler"}

That most likely means that the coordinator did not have any funds to open the just in time channel.

We checked on this and you are are correct - the coordinator ran out of funds because we force-closed a relatively big channel.
Additionally, the funding requirement calculation did not take the inbound liquidity with other nodes in the network into account. We are adding more funds to the coordinator.

authors: bonomat da-kami holzeis


text:
🛑 CRM is down

In 9157b00, CRM (https://20.rp.get6pm.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CRM is back up in cedfd80 after 10 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
新增拒绝权限和永久拒绝权限区分

新增拒绝权限和永久拒绝权限区分

有这种场景，就是在onDenied回调中，要区分被拒绝的权限是1、拒绝状态2、永久拒绝状态。所以，把这两种情况分开为两个list，并修改第三个bool参数为：是否都是永久拒绝状态

有这种场景，就是在onDenied回调中，要区分被拒绝的权限是1、拒绝状态2、永久拒绝状态。所以，把这两种情况分开为两个list，并修改第三个bool参数为：是否都是永久拒绝状态

小伙子，能讲一下具体的需求场景吗？

小伙子，能讲一下具体的需求场景吗？

比如需要申请定位，相机，电话权限，然后操作分别是永久拒绝，拒绝，允许。但是回调中定位和相机都在被拒绝的list中。无法精确命中哪个为永久拒绝。我们的需求需对于永久拒绝要给予友好的dialog展示。而拒绝的权限，则不做处理下次还会继续弹出。

比如需要申请定位，相机，电话权限，然后操作分别是永久拒绝，拒绝，允许。但是回调中定位和相机都在被拒绝的list中。无法精确命中哪个为永久拒绝。我们的需求需对于永久拒绝要给予友好的dialog展示。而拒绝的权限，则不做处理下次还会继续弹出。

这功能好，我一直喜欢。虽然你永久拒绝了，但是我还是给出提示。

这功能好，我一直喜欢。虽然你永久拒绝了，但是我还是给出提示。

xxpermissions.zip

xxpermissions.zip

上面是最新的 aar 包，已经加上了判断是否永久拒绝权限的方法，请使用此 API 来判断：XXPermissions.isPermissionPermanentDenied

上面是最新的 aar 包，已经加上了判断是否永久拒绝权限的方法，请使用此 API 来判断：XXPermissions.isPermissionPermanentDenied

source: gharchive/pull-request

authors: AdminQQZ HubertYoung getActivity

repo: getActivity/XXPermissions


text:
[BUG] "Copy Invoice" should be made into more intuitive text #2290

Describe the changes you have made in this PR
I have created a new translation of copy_invoice in the translations file in the en folder. and updated the receive screen accordingly.
Link this PR to an issue [optional]
Fixes _#2290
Type of change
(Remove other not matching type)

fix: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes [optional]

How has this been tested?
It can be produced as:
Click on Receive
Generate an Invoice
Click on Copy Invoice
Checklist

[ ] My code follows the style guidelines of this project and performed a self-review of my own code
[ ] New and existing tests pass locally with my changes
[ ] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

@reneaaron can you please review it I have made the changes according to your suggestion.

@Pratik-A-N Thanks for your PR, please remove the translations that are not your native language (they will be translated by native speakers on weblate.org).
Other than that, LGTM!

@Pratik-A-N Did you test your PR before submitting it? The label still is "Copy" :shrug:

authors: Pratik-A-N reneaaron

repo: getAlby/lightning-browser-extension


text:
Change the default output directory to tmp/appmap

Also, change the plugin's behavior when appmap.configFile is missing from build.gradle. Instead of failing, just leave appmap.config.file unset when running tests with the agent.
Fixes #19 .

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

v1.2.0
GitHub release

Your semantic-release bot :package::rocket:

authors: apotterri appland-release

repo: getappmap/appmap-gradle-plugin


text:
Send user id when signing in to AppMap server

Closes https://github.com/getappmap/appmap-intellij-plugin/issues/250

:tada: This PR is included in version 0.32.1 :tada:
The release is available on:

v0.32.1
GitHub release

Your semantic-release bot :package::rocket:

authors: appland-release jansorg

repo: getappmap/appmap-intellij-plugin


text:
Retry CLI tools installation

On Windows especially installation of CLI tools occasionally fails with errors such as:
Error: EBUSY: resource busy or locked, copyfile '\extern\yarn.js' -> 'c:\Users\user\AppData\Roaming\Code\User\globalStorage\appland.appmap\yarn.js'

We should make sure to retry it after a delay in case of an error.

I'm assuming this will be fixed with the lockfile update (https://github.com/getappmap/vscode-appland/pull/527)

As with #517 , #527 won't fix this per se, but it might make the biggest reason to do it go away.

authors: dividedmind dustinbyrne

repo: getappmap/vscode-appland


text:
feat: Enable configuration of the Navie / JSON-RPC port

This is used for development, running byok Navie in a separate local process or debugger.

Superceded by https://github.com/getappmap/vscode-appland/pull/929


text:
Api for Customers

Today the lib does not support calls to customer apis, right?
like GET https://api.bigcommerce.com/stores/{store_hash}/v3/customers

it does? you would just use the request verb GET from the node-bigcommerce instance.
bigcommerce.get("/customers") in your case since using v3 it will be bigcommerce.get("/catalog/customers") follow bigcommerce docs for correct routes.
old question, figured if anyone else needs this answered.

it does? you would just use the request verb GET from the node-bigcommerce instance.
bigcommerce.get("/customers") in your case since using v3 it will be bigcommerce.get("/catalog/customers") follow bigcommerce docs for correct routes.
old question, figured if anyone else needs this answered.

Thank you @william1benn  i resolved my problem

authors: Greenroads-Main gabselbach william1benn

repo: getconversio/node-bigcommerce

license: mit

license_source: bigquery


text:
Install and first example is painful

#Describe the bug
Newcomer here.
On linux, the default suggested install doesn't work (keyserver not responding). Used curl to get around.
Then the default example provided in the documentation doesn't work.
As described: https://docs.gauge.org/getting_started/create-test-project.html?os=linux&language=javascript&ide=vscode
From VSCode: Create Gauge Project > js template.
Many errors.
Eventually, VSCode even frizzes when using gauge (didn't search why, but enough to make me stop).
What command(s) did you run when you found the bug?
Simply followed the installation process and ran the basic example in js.
Due to a deprecated API, needed to change screenshotFn by customScreenshotWriter.
Then the example fails:
step("Search for ", async (query) => {
await focus(textBox(toRightOf('Pricing')))
await write(query);
await press('Enter');
});
This really doesn't make the first experience with gauge very good... (sorry).
Operating System information
Linux
IDE information
VSCode

Many errors.

@fimbault Could you. please tell us, what errors are you seeing?

authors: BugDiver fimbault

repo: getgauge/gauge


text:
media controlsList() not working on videos

When trying to change the available controls on video tags with controlsList as described in the documentation it is not working correctly.
Code:
{{ page.media['test.mp4'].controlsList('nodownload nofullscreen noremoteplayback').display()|raw }}

This is the html result:
<video controls="1" alt=""><source src="/user/pages/04.demos/test.mp4?controlsList=nodownload%20nofullscreen%20noremoteplayback">Your browser does not support the video tag.</video>

But this is expected:
<video controls="1" controlsList="nodownload nofullscreen noremoteplayback" alt=""><source src="/user/pages/04.demos/test.mp4">Your browser does not support the video tag.</video>

With audio files it works fine.

Additional info: I used the current stable version 1.5.3 with the admin plugin.

repo: getgrav/grav


text:
This allows a frontmatter.yaml file to be included in a page folder

It will be merged into the page header.
The downside/issue/non-issue? with this is that in the admin this will be merged in transparently and shows up as if it were in the page frontmatter itself, and then when you save, it is in fact saved back into the page.
Doing anything else differently is going to be much more complex because we'll have to handle two ways of generating header data (one for admin ignoring this file, and one for frontend).  However it's not even that easy because this data is potentially cached, meaning we'll have to maintain two versions in cache, leading to possible inconsistencies.
This is a pretty advanced feature and would not be something that could be set via Admin so am not sure if this is a problem or not.

This PR is regarding  Issue #775

Ok i've found a solution to my caveat, i've actually set it so the cache on admin is independent of site.  This should fix some other obscure issues too.


text:
should we pick up some tricks/optimizations from Ramda?

Some interesting things from Ramda to consider adding to FPO:

_arity(..) is used to create a function with a proper .length, from the results of utils like curry(..), etc

utils like flip(..) will re-curry the function (in other words, assuming you always want currying)

Liking FPO and just heard of it as I'm learning Ramda. Some of the features I find useful in Ramda are lenses, evolve, converge and more. Will FPO support these types of functions?

I'm open to some of those more advanced features... however, I personally haven't ever been able to get my head around their usefulness. I would need to see some concrete examples of how those things would be useful, so if you have some suggestions, please share! :)

Interesting, I am certainly open to having the least cluttered toolbox possible. I'm just looking for the best means to get things done in a project that is data/state intensive.
It does seem like all the functions I mentioned are higher level concepts that are carried out by the basics, essentially getting and setting, which use mapping and transforming in unique ways. So, maybe the right way to view them is just as handy recipes that many have found useful?
Still, I like the facility to breakout data lenses as reusable and composable functions. This is especially useful in the large exchangable and very structured states I'm using. I do like the ability to create a module of these abstracted away lens functions, that can then be used in umpteen ways.
Looking again at evolve I can almost picture it as a FPO function that is handed a state object and a given set of named args mapped to functions that target keys in the state object that match the named args, anything is possible. Maybe this is the new and improved lens!?
Found some pro lens articles in my massive collection of things to digest, simplify and apply. Here are some of the better ones :)
https://medium.com/@drboolean/lenses-with-immutable-js-9bda85674780
https://medium.com/javascript-inside/an-introduction-into-lenses-in-javascript-e494948d1ea5
http://randycoulman.com/blog/2016/07/12/thinking-in-ramda-lenses
https://vanslaars.io/post/setstate-lenses
http://joneshf.github.io/programming/2015/12/19/Lenses-and-Virtual-DOM-Support-Open-Closed.html#wrap-up

authors: MVSICA-FICTA getify

repo: getify/fpo


text:
I would like to be able to assign dead letter queue handler in lift

Start from the Use-case
For now we can assign the handler for the queue, but when they fails messages goes to the dead letter queue - would be really nice if we could assign handler for that queue too
Example Config
No response
Implementation Idea
deadHandler: . ?

Could you detail what you would achieve with this setup?

Sorry for long delay.
I mean i would like to parse them by common lambda that would be handling dead deadletters

More details:
i have a workflow, that moves the ,,ticket'' from one queue to another (they must be executed in order).
But when the ticket goes into deadletter queue, i want to grab it by lambda, try to reexecute it, and if its failing - remove from the deadletters but do some things - close the workflow for the ticket and so on.  Without providing the lambda on lift config for dead letter lambda-handler, its quite a task.

@Setitch did you find any solution? @mnapoli any updates on the issue?

@kamalnathlp sadly not yet, which is real shame

DLQ url and arn are now exposed via variables. You can use those to attach a specific lambda handler.

authors: Setitch fredericbarthelet kamalnathlp mnapoli

repo: getlift/lift


text:
Removing Pydantic Table from the Schema

[x] Removed the logic where pydantic details are stored in postgres
[x] Added logic to fetch the Pydantic class node details from neo4j
[x] Logic to fetch classes from github repos
[x] Deleted pydantic table
[x] Tested on local & docker

Are duplicate class names handled?
No, the older code also did not tackle this issue, pondered a lot and seemed this was the best solution as for now

Are multiple class imports handled?
Yes, it is being handled.

repo: getmomentum/momentum-core


text:
Container logs can very large and should be compressed

Containers logs (particularly nginx and service) can be very large and take up a lot of space. Also, it isn't fast to docker logs container | grep foo them for issues.
We can't use logrotate inside the containers because they all report out on stdout/err, but it looks like we can configure the “local” logging driver and it does log-rotation by default and still works with docker logs, so we can do docker logs --since 10m <container_id>.
My bias is to do this for every container in the docker-compose.yml file.

I looked at the logs on server and here's what is taking up space since the server started in July 2021 (roughly 3 months) and has 550k submissions
nginx 637M
service  14M
enketo  27K
postgres  56K
pyxform  45K
redis  54K
redis 118K
smtp 1.2K

Given this, I propose we only deal with logging for nginx and service.

repo: getodk/central


text:
use groupBy after join, it not work.

This template isn't a strict requirement to open issues, but please try to provide as much information as possible.
Version: 2.3.2
Module: quill-jdbc
Database: mysql
Expected behavior
fetch a List result.
Actual behavior
get a exception
Steps to reproduce the behavior
Workaround
case class Devices(id: Long, chId: String, model: String)
case class Otas(id: Long, model: String)
val q = quote {
query[Devices]
.join(query[Otas])
.on(_.model == .model)
.groupBy(._1.chId)
}
val result = dbContext.run(q)
[error] scala.reflect.macros.TypecheckException: Found the embedded 'com.gyenno.domain.ACSchema.dbContext.Query[(com.gyenno.dao.device.Devices, com.gyenno.dao.device.Otas)]', but it is not a case class
[error]         at scala.reflect.macros.contexts.Typers.$anonfun$typecheck$3(Typers.scala:32)
[error]         at scala.reflect.macros.contexts.Typers.$anonfun$typecheck$2(Typers.scala:26)
[error]         at scala.reflect.macros.contexts.Typers.doTypecheck$1(Typers.scala:25)
[error]         at scala.reflect.macros.contexts.Typers.$anonfun$typecheck$7(Typers.scala:38)
[error]         at scala.reflect.internal.Trees.wrappingIntoTerm(Trees.scala:1710)
[error]         at scala.reflect.internal.Trees.wrappingIntoTerm$(Trees.scala:1707)
[error]         at scala.reflect.internal.SymbolTable.wrappingIntoTerm(SymbolTable.scala:16)
[error]         at scala.reflect.macros.contexts.Typers.typecheck(Typers.scala:38)
[error]         at scala.reflect.macros.contexts.Typers.typecheck$(Typers.scala:20)
[error]         at scala.reflect.macros.contexts.Context.typecheck(Context.scala:6)
[error]         at scala.reflect.macros.contexts.Context.typecheck(Context.scala:6)
[error]         at io.getquill.context.QueryMacro.expandQueryWithMeta(QueryMacro.scala:41)
[error]         at io.getquill.context.QueryMacro.expandQuery(QueryMacro.scala:20)
[error]         at io.getquill.context.QueryMacro.runQuery(QueryMacro.scala:12)
[error]       val result = dbContext.run(q)
[error]                                 ^
[error] one error found
[error] (gyennoService/compile:compileIncremental) Compilation failed
@getquill/maintainers

Typically when you are doing a group-by in SQL, you cannot select any field that is not actually being grouped, you can only use aggregators. For this reason, Quill cannot actually give you case classes from your query output unless you group by all the dimensions of the case class.
Say your SQL looks like this:
SELECT
  d.ch_id,
  MIN/MAX/SUM/FIRST(d.id),  /* Must use an aggregator if you want to return this data! */
  MIN/MAX/SUM/FIRST(d.model) /* Must use an aggregator if you want to return this data! */
FROM devices d INNER JOIN otas o ON d.model = o.model GROUP BY d.ch_id

Typically the way you will do this in frameworks like Quill is with a Group By and then a Map, in fact, in these frameworks a Group By is almost always followed by a map. Here is how it would look like Quill:
quote {
  query[Devices]
    .join(query[Otas])
    .on((d,o) => d.model == o.model)
    .groupBy(_._1.chId)
    .map({case (chId, devicesAndOstas) => (
      chId,
      devicesAndOstas.map(_._1.id).max,
      devicesAndOstas.map(_._1.model).max
    )})
}

Can you be a bit more specific about what you are trying to do? Maybe we can find a more appropriate solution.

@deusaquilus thanks, you give me a lot of inspiration,  I need the max model ;  this       devicesAndOstas.map(_._1.model).max  work fine.

requirement
fetch max OTA's versionCode of  model, one or more
domain
case class Devices(id: Long, chId: String, model: String)
case class Otas(id: Long,
model: String,
version: String,
versionCode: Int,
category: Int)
quoted
val q = quote {
query[Devices]
.join(query[Otas])
.on(_.model == _.model)
.groupBy(t ⇒ (t._2.model, t.2.category))
.map {
case (model, p) ⇒
(model, p.map(._2.versionCode).max)
}
}
  val result = ctx.run(q)

authors: arccode deusaquilus

repo: getquill/quill


text:
Update orientdb-graphdb to 3.0.37

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.orientechnologies", artifactId = "orientdb-graphdb" } ]

labels: library-update, semver-patch

Superseded by #2169.


text:
Clarify import statements in ng2 docs

cc @macqueen

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: benvinegar macqueen

repo: getsentry/raven-js


text:
Load dynamic values from system env

The current code does not load dynamic env var using :system
config :sentry,
  dsn: {:system, "SENTRY_DNS"},

This is useful when deploying in production environment using exrm.
I would appreciate this feature asap as I am not receiving errors on my Sentry account or if you have any other suggestion please let me now,
Thank guys

I don't have a huge amount of experience with exrm/distillery, so please correct me if I'm off.  My understanding is that for libraries supporting the {:system, "CONFIG_KEY"} convention, when the release is built, it will store that tuple normally without fetching from System. Upon the release being run, the library will see that pattern, and read from the config at runtime.
I believe Phoenix only supports it for a couple parts of the configuration (PORT and HOST).  Would adding it for the dsn be sufficient, or would it be necessary for all configuration keys?

@mitchellhenke Thank you for your reply! Yes that's the behavior mate. I also request it on ex_statsd I can totally submit a PR you you want, wdyt?

@rafaeljesus cool, sounds good.  I can likely get to it this week.

authors: mitchellhenke rafaeljesus

repo: getsentry/sentry-elixir


text:
Provide a customisable hint when capturing an event

Summary
Would it be possible have a way to provide a Hint along with an Event in Hub
Motivation
I'm customising the errors I send to sentry by calling sentry.Hub.CaptureEvent with an event from sentry.Client.EventFromException. This works well apart from the fact that I lose the Hint that I would get if I called CaptureException making it harder to use other parts of the API like BeforeSend.
Unfortunately there doesn't seem to be a way to add an EventHint manually with the Hub API, that can only be done at the client level but if I call the client directly myself it looks like I will be breaking handling of lastEventID in the hub.
Would it be reasonable to add a version of CaptureEvent that took both an event and a hint to allow callers to have this flexibility without breaking other parts of the API?
Additional Context

What are you using lastEventID for? When using the default, async transport, CaptureException & Co. simply return the event id, so it's not a guarantee that the event was actually sent to Sentry, but rather, it was queued up in the transport.

I'm not actually using it but was worried that if it wasn't set I would be breaking some contract with the hub. Should I just get the client and the scope from the hub and call the client's CaptureEvent myself?

Yeah, nothing wrong about this approach.

Then I'll go with that for now, thanks!

authors: cleptric crswty

repo: getsentry/sentry-go


text:
ignore_loggers should be per-client

A client should not ignore the django logger if the client does not have the django integration enabled.

Because this is very old and it never popped up in the last four years, I will just close this.
If your came across this Issue and want to help fix this, please create a new Issue and link to this one. Thanks!

authors: antonpirker untitaker

repo: getsentry/sentry-python


text:
No Longer loading environment and release from environment variable

The old Python lib loaded environment and release from the environment however this lib does not appear to do that. Further there is no mention of that change in the docs nor a clear suggestion for a migration path.

About the docs: Yeah we should set up some kind of migration guide from the old SDK to the new one. I don't think mentioning the differences to Raven throughout the docs is a good idea.
environment and release are still arguments to the client, so you can do this:
init(__dsn__, environment=os.environ.get("SENTRY_ENVIRONMENT"), release=os.environ.get("SENTRY_RELEASE"))

With 0.7.4 (not yet released) the workaround should no longer be necessary.

@untitaker what about falling back to HEROKU_SLUG_COMMIT for the release?

@cancan101 that fell under the radar, sorry!
I don't think we want to do this in the core client, but possibly as integration you have to explicitly enable. Not because writing a new class just for a single envvar is great, but because I want to avoid having a lot of env-specific oneliners on Client.


text:
Fastapi: Url with path param without replacement in profiles_sampler and/or before_send_transaction

Problem Statement
Hi all,
Is it possible to get the original path without path params replacement in either the profile_sampler or before_send_transaction for a fastapi integration?
We are trying to filter out some transactions and we have generated a list of all the paths we want to exclude/subsample.
E.g. one would be /streams/status/{camera}/data/{lens} . However, in both functions' arguments dicts I can only see the url with the replaced path param (e.g.   /streams/status/myCamera/data/myLens) which can't really be compared against the string value of the route.
The transaction name is correctly reported without replacement in sentry, but I don't seem able to find that value in either transaction_context nor event. Am I missing something?
Solution Brainstorm
I think it would be really helpful to have this value included so it can be used for subsampling and filtering

Hey @lucabergamini, thanks for writing in.
In before_send_transaction, the first argument (the event) has the unfiltered URL (not just the path) in event["request"]["url"].
In profiles_sampler you get the sampling context as the sole argument and the path should be in sampling_context["asgi_scope"]["path"].
Let me know if that helps.

Hi @sentrivana
thanks for the reply. That indeed works, but I've realised something after writing the original question.
before_send_transaction is called at the very end of the endpoint lifespan. That means that I won't be able to control the sampling and all endpoints call will be traced. This would cause a performance issue In our prod env.
profile_sampler seems to be called before. However the issue with that is that is called before everything else as far as I know, so even before fastapi url resolution. I've tried adding a middleware to inject context, but I believe that does not work exactly for this reason.
Is there any way to get any info to the profile_sampler or to postpone its evaluation? Currently, I resorted to running the path resolution in the function itself (which works, but it's a bit clunky)

@lucabergamini I think what you want is actually a custom traces_sampler -- it allows you to set the sampling decision for a transaction at an earlier point than before_send_transaction and afaik prevents child spans from being created if not sampled.
That being said, the traces_sampler callback happens at virtually the same point in time as profiles_sampler (with the same sampling context as well) so if you're missing information in the profile sampling context, you'll have the same issue with the traces_sampler. If you need more than the path in the sampling context, you might indeed need to get any additional info in the function itself, as you wrote.

Hi @sentrivana, that makes perfect sense, thanks for your support.
I'll close this as I consider it solved.

authors: lucabergamini sentrivana


text:
fix(django): Fix psycopg3 reconnect error

Fixes GH-3061

Marking as draft since I am unsure how to properly test this change

Note to self: run tests with SENTRY_PYTHON_TEST_POSTGRES_NAME=postgres tox -e py3.12-django-latest -- tests/integrations/django/test_basic.py::test_connection_reconnect_does_not_error, with Docker Postgres container started

Testing this change is not super-straightforward; I am still struggling to figure out how to make my test work.
So that the lack of a test does not block the release of this bug fix, we will implement the test later. I have opened Issue #3139 to add a test, and have put my in-progress work in a draft PR linked on that issue


text:
feat: add cloudwatch logs URL to lambda additional data

As discussed on discord, this adds an additional "extra" for cloudwatch logs URL, log group, and log stream.

Not sure what if any tests are required for this change. Thoughts?

oh yeah please also add tests for this

Awesome, thanks!

Oh, uh... sorry, wasn't done. I just pushed up the tests.

Damn, sorry. Could you PR those separately?

authors: flyinbutrs untitaker


text:
Update README.md

Fixed statement about jellyfish. It supports unicode strings for quite some time and it performs well with them.
I was looking if I can find faster implementation than what jellyfish provides and found this library. It turned out to be not that good as advertised, in my tests it's about 7 times slower than jellyfish. It would be fair to include it in the benchmarks as well.
PS: I probably have something different in my setup as I get worse results than advertised on a slightly more powerful CPU (i7-7700):
>>> timeit.timeit("damerau_levenshtein_distance('e0zdvfb840174ut74j2v7gabx1 5bs', 'qpk5vei 4tzo0bglx8rl7e 2h4uei7')", 'from pyxdameraulevenshtein import damerau_levenshtein_distance', number=500000)
20.89569331565872
>>> timeit.timeit("damerau_levenshtein_distance('e0zdvfb840174ut74j2v7gabx1 5bs', 'qpk5vei 4tzo0bglx8rl7e 2h4uei7')", 'from jellyfish import damerau_levenshtein_distance', number=500000)
3.016888005193323

Thanks for the PR! I'll merge.
And thanks for the performance note about Jellyfish. I need to look into how its implementation its different than what's happening in this library.

authors: gfairchild nijel

repo: gfairchild/pyxDamerauLevenshtein


text:
Failed: fetch of submodule tudatExampleApplications during init

In step 6 of the installation git submodule update --init --recursive, fetching of the commit for tudatExampleApplications failed.
Step 6 output is attached; key lines are:
fatal: remote error: upload-pack: not our ref c08c43e16dba02d81947ca601854a557b7a53692
fatal: the remote end hung up unexpectedly
Fetched in submodule path 'tudatExampleApplications', but it did not contain c08c43e16dba02d81947ca601854a557b7a53692. Direct fetching of that commit failed.

fetchInitFailure.txt

I ran into the same issue, it's an issue of this version of the bundle looking for a commit of the example applications that doesn't exist in: https://github.com/tudat/tudatExampleApplications. If you just manually clone the example applications, everything should work

authors: DominicDirkx transferorbit


text:
Fix depending on PATH_MAX being defined

As POSIX limits.h defines, PATH_MAX may be omitted from limits.h if the limit
depends on the file type the limit is applied to.
Passing NULL to realpath allocates the appropriate amount of memory itself.
This fixes compilation on GNU/Hurd where PATH_MAX is not defined.
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
http://pubs.opengroup.org/onlinepubs/9699919799/functions/realpath.html

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
acmeideal@gmail.com
Domain biomassiv.es has exceeded the max emails per hour (119/100 (119%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o5.sgmail.github.com ([192.254.113.10]:28424)
by server23.websitehostserver.net with esmtps (TLSv1.2:DHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.85)
(envelope-from bounces+848413-b37a-greg=biomassiv.es@sgmail.github.com)
id 1ZmSCF-003ZAP-GW
for greg@biomassiv.es; Wed, 14 Oct 2015 14:58:48 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com;
h=from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=ZMsp74HBFJ9FcwLr91s4hKUVYXY=; b=p+4NTnZLP+MfqIEk
SaGJEMg5y1Whu5Q+R5ePRzFcti/NWzfYi2AIzD9Si0VmauPUx30yg/q55m9/gcSK
vVrTTIb29S0FH3oRke8uwJzbFSET4VGj3KbzS021I8gCyWdLdz9v+QqBsGLPmNJp
lU6ee6PFUDtA0IbYIieXYT5HQjc=
Received: by filter0458p1mdw1.sendgrid.net with SMTP id filter0458p1mdw1.29382.561EB3F211
2015-10-14 19:58:42.210347257 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17])
by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id biZUnukFS9mNoXSWlNhisQ
for greg@biomassiv.es; Wed, 14 Oct 2015 19:58:42.146 +0000 (UTC)
Date: Wed, 14 Oct 2015 12:58:36 -0700
From: Juhani Imberg notifications@github.com
Reply-To: ggreer/the_silver_searcher reply@reply.github.com
To: ggreer/the_silver_searcher the_silver_searcher@noreply.github.com
Message-ID: ggreer/the_silver_searcher/pull/770@github.com
Subject: [the_silver_searcher] Fix depending on PATH_MAX being defined (#770)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_561eb3ec2c326_77623fac971892b8391ce";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: JuhaniImberg
X-GitHub-Recipient: biomassives
List-ID: ggreer/the_silver_searcher <the_silver_searcher.ggreer.github.com>
List-Archive: https://github.com/ggreer/the_silver_searcher
List-Post: mailto:reply@reply.github.com
List-Unsubscribe: mailto:unsub+0042d4e25b2fc37ccb783b76faaa1be6942271f55c26c24892cf00000001123675ec92a169ce06a50de2@reply.github.com,
https://github.com/notifications/unsubscribe/AELU4pQV6GQQ24zsQLR8W1O3wDRVcEXtks5o7qtsgaJpZM4GO9Tt
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: greg@biomassiv.es
X-SG-EID: ZlaDthyue/4HG+EgTb7JoZYs48JNb2iQtCcPV6oIs9W9GtwvILznmPVM3lZRt4snnbq40ZD6nQfb7d
iP+36/iyZQNhSEJFA8+Cmrk3R8xCMAEUWrnmf6Yn2kVu7S+fhvREonUoF0JLXsfYGFKBTXgVPWMpQf
QFwCsfECWdoKJOY=
X-Spam-Status: No, score=-0.4
X-Spam-Score: -3
X-Spam-Bar: /
X-Ham-Report: Spam detection software, running on the system "server23.websitehostserver.net",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  As POSIX limits.h defines, PATH_MAX may be omitted from limits.h
if the limit depends on the file type the limit is applied to. Passing NULL
to realpath allocates the appropriate amount of memory itself. [...]
Content analysis details:   (-0.4 points, 5.0 required)
pts rule name              description

-0.0 T_RP_MATCHES_RCVD      Envelope sender domain matches handover relay
domain
0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: github.com]
-0.0 RCVD_IN_MSPIKE_H4      RBL: Very Good reputation (+4)
[192.254.113.10 listed in wl.mailspike.net]
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
1.6 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO
----==_mimepart_561eb3ec2c326_77623fac971892b8391ce
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
As POSIX limits.h defines, PATH_MAX may be omitted from limits.h if the limit
depends on the file type the limit is applied to.
Passing NULL to realpath allocates the appropriate amount of memory itself.
This fixes compilation on GNU/Hurd where PATH_MAX is not defined.
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
http://pubs.opengroup.org/onlinepubs/9699919799/functions/realpath.html
You can view, comment on, or merge this pull request online at:
https://github.com/ggreer/the_silver_searcher/pull/770
-- Commit Summary --

Fix depending on PATH_MAX being defined

-- File Changes --
M src/options.c (10)

-- Patch Links --
https://github.com/ggreer/the_silver_searcher/pull/770.patch
https://github.com/ggreer/the_silver_searcher/pull/770.diff

Reply to this email directly or view it on GitHub:
https://github.com/ggreer/the_silver_searcher/pull/770
----==_mimepart_561eb3ec2c326_77623fac971892b8391ce
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
As POSIX limits.h defines, PATH_MAX may be omitted from limits.h if the limit
depends on the file type the limit is applied to.
Passing NULL to realpath allocates the appropriate amount of memory itself.
This fixes compilation on GNU/Hurd where PATH_MAX is not defined.
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
http://pubs.opengroup.org/onlinepubs/9699919799/functions/realpath.html

You can view, comment on, or merge this pull request online at:
  https://github.com/ggreer/the_silver_searcher/pull/770
Commit Summary

Fix depending on PATH_MAX being defined

File Changes

M
src/options.c
    (10)

Patch Links:

https://github.com/ggreer/the_silver_searcher/pull/770.patch
https://github.com/ggreer/the_silver_searcher/pull/770.diff

—Reply to this email directly or view it on GitHub.

----==_mimepart_561eb3ec2c326_77623fac971892b8391ce--

Thanks. I'm surprised that was the only change needed to get ag working on hurd.

authors: JuhaniImberg biomassives ggreer


text:
Allows updater.sh to work with Thunderbird profiles as well

This PR is a cleaned up version of @atomGit's first draft, back in May 2019.
See (and closes) HorlogeSkynet/thunderbird-user.js#1.
EDIT 2020-03-24 : Some stuffs were missing yesterday, now it should be better. Bye :wave:
(partial) related issues :

#646
#753
HorlogeSkynet/thunderbird-user.js#10

Thanks. This is not my file or area of expertise, and there are a few changes here, so we'd need to sort through those with @earthlng or @overdodactyl
The first thing I will say is that I'm not interested in having a file in this repo point at someone else's files or another application: it smacks of endorsement and this repo has nothing to do with Thunderbird.
So after all the TB changes are removed, what's left? Some exit code and typo improvements?

seems to be some confusion about this patch, so...
i didn't submit the patch
i made a couple of very slight changes to the updater.sh to get to work with t-bird and the @HorlogeSkynet user.js for t-bird for my own use, then i wondered whether the ghacks crew would want to adopt the changes since i didn't see the sense in maintaining 2 copies that are nearly identical, plus i'm simply not qualified - i think i discussed this with HorlogeSkynet after which he submitted the patch for me since i didn't know how (i think he also cleaned up my code a little?)
if you guys don't want to adopt the changes, i understand - no problem

I doubt anyone who could is going to review any improvements. AFAIK it's not broken

Hi, thanks for your feedback.
IMHO, and concisely :

The main rational behind this PR is, as projects share many common points, to drastically reduce the maintenance cost, and focus on the content. The proposed patch actually adds a new feature to the project "meta-environment", is fully backward-compatible for everyone.

The main differences with CHEF-KOCH's TBCK (quickly denigrated in #646) is a proper documentation (mainly coming from here btw) and would be the GHacks' updating script (at least) for Linux, working out-of-the-box, and honoring the same "standards" you were talking about here.

Such a feature has been greatly discussed (see links above) and is expected from (at least a part of) the community (I would invite Daniel @dngray, @zdat from HorlogeSkynet/thunderbird-user.js#10, @claustromaniac & @ema-pe from here and at least @aesthicc from... here, to join us discussing this).

As you stated here : [...] I think it's a small project, but a worthy one - and I'd use it as well, I agree and now you also got "community" members handling working on what you didn't/don't have to the time for. Look how fortunate you are ! You only have to let the opportunity to make it easily usable to people already using it for FF.

So, would you consider re-opening this, and having a proper discussion with the "community"/the parties involved (and yes, I'd be pleased to get a proper review from @earthlng) ?
If you're really embarrassed with an "external" link, we could add one more Are you sure you wanna fetch content from third ${USERJS_URL} URL ? [y/N] validation step when -t is specified.
Bye :wave:

My 2 cents:

Sincerely I'm not interested on Thunderbird support. This repository is only for Firefox. If you want to add support for Thunderbird, it is better to merge the two projects.
The typos and error code fix seems good to me. It would be useful to check the script with ShellCheck to find other minor issues (maybe with GitHub Actions this can be automatized).
I don't think is necessary to add new functionalities to the installer script. Remember that it is written in Bash and it can easily degenerate to a barely maintainable script.

authors: HorlogeSkynet Thorin-Oakenpants atomGit ema-pe


text:
added custom options in config for residual plots

This allows the user to set the style of the error bars in the residual plots via the config. Aids when there are many data sets or just one.

Codecov Report

Merging #181 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #181      +/-   ##
==========================================
+ Coverage   74.21%   74.21%   +<.01%
==========================================
  Files         117      117
  Lines       11963    11964       +1
==========================================
+ Hits         8878     8879       +1
  Misses       3085     3085

Continue to review full report at Codecov.

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

authors: codecov-io grburgess


text:
detalle con boletas de sumas altas

hola amigo, acaba de salirme un error al momento de enviar el resumen diario
genere una boleta de 2099.97 y me bota este error

Alli en tipo, debe ir 1 - DNI, 6 - RUC, no Boleta.

si acabo de darme cuenta de este error, pero es la primera vez que ocurre y todos los demas resumenes diarios los envie asi D: , como pudo aceptar los demas ...

A partir de s/. 700, sunat exige que el cliente este identificado, probablemente aplica la validacion dependiendo del monto.

authors: abelnexus giansalex

repo: giansalex/greenter-sample


text:
Fix crd-install job

Towards https://github.com/giantswarm/giantswarm/issues/23960

"crds" folder is used by helm but we want to manage CRDs with our crd-install job. The folder name is wrong now.

Testing

[x] Installation
[x] Upgrade

Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml and values.schema.json are valid.

node.cloudprovider.kubernetes.io/uninitialized taint blocks  crd-install job. We don't need cloud-provider for the crd-install job so this PR adds toleration for that taint too.

I removed this part. This doesn't give us so much benefit. This app depends on cert-manager at the end. As I mentioned here, I plan to delegate default VolumeSnapshotClass creation to this app itself. Therefore, nobody will depend on this app's CRDs and it will be not urgent the create CRDs.

repo: giantswarm/csi-external-snapshotter-app


text:
IRSA private S3 bucket

Story
-As a cluster admin, I want IRSA (IAM Roles for Service Accounts) to use a private S3 bucket instead of a public one, in order to align with internal S3 policies.
Background
Some customers have strick internal policies when it comes to S3 buckets: no public S3 bucket should be used by the organization. Such policies were put in place because public S3 buckets have been part of a lot of data leak incidents.
The IRSA implementation requires a public S3 to store the public OIDC provider information.
One suggested solution to the problem was to use a private S3 bucket with Cloud Front in front of it as described in the aws documentation.
Options

Cloud Front + private S3 bucket;
...

Cloud Front + private S3 bucket
Cloudfront for IRSA is working, but needs some additional changes:

New Cloudfront distribution needs to created per cluster, it auto generates a new domain name (e.g. d12amkbgptnl2n.cloudfront.net) this needs to put in different places
New OIDC provider needs to get created with the new domain name
S3 Open ID configuration needs to be changed with this domain name
S3 Bucket policy needs restrict Cloudfront only
API server flag --service-account-issuer has to be changed to Cloudfront (this means we need to roll all nodes again)
Route53 Manager Role needs to be changed to the new issuer

Biggest issues:

The domain name will be autogenerated so we need to pass this information from irsa-operator to aws-operator a lot of code changes, probably needs to stored in a config map
How to do the transition of exisiting clusters?

Resources

POC results;
AWS docs on how to restrict access to an S3 bucket.

Status update 5.8:
irsa-operator is now supporting Cloudfront and also has a hash diff integrated which will upload OIDC configuration and keys automatically when they have changed. This means we don't need to manually delete OIDC configuration for current clusters which already using IRSA.
It also has a autoswitch when upgrading to v18 for those clusters. Customer only need to adjust their IAM roles to add trust entity for Cloudfront.
aws-operator is also prepared when customer switch to v18 it will adjust the API flags and also adjust the Route53Manager Role.

China currently doesn't work with Cloudfront. By default a domain will be created with an ending cloudfront.cn. Unfortunately this domain can't be used and a CNAME needs to be added including uploading a certificate. This will make it much more complicated.
You can’t use the default CloudFront domain, *.cloudfront.cn, to serve content. You must add an alternate domain name, also known as a CNAME, to your CloudFront distributions, and then use that domain name in the URLs for your content. You also must have [an ICP registration](http://www.amazonaws.cn/about-aws/china/#ICP_). In addition, just as with the global CloudFront service, to serve content over HTTPS, you must use an SSL/TLS certificate with your alternate domain name

More information:
https://docs.amazonaws.cn/en_us/aws/latest/userguide/cloudfront.html
For now we have to stay with the S3 public endpoint in China.

authors: alex-dabija njuettner

repo: giantswarm/roadmap


text:
ssh access to CAPO cluster nodes

[ ] setup (central) vault or use operations vault
[ ] setup bastion hosts
[ ] Modify CAPO bastions to take certificates instead of keys

Dupe of https://github.com/giantswarm/roadmap/issues/634

authors: cornelius-keller kopiczko


text:
Added ability to edit meta information for md files

This adds ability to edit meta information for md files (see issue #97 ).

Let me know if there is anything I should improve.

Looks good and worked for me on the first attempt.
Merged! Thanks for the contribution.
Two additional improvements if you're up for them:

We're going to be moving towards testing functionality and style for contributions very soon. Please fix the minor warnings after running make test. I'll also update the main "Contribution" docs to reflect this move towards testing.

let's find a way to refactor out the nested function definition as seen below:

 function create_content(body) {
    function create_meta_info(meta_title, meta_description, meta_sort) {}
    // ...
}

@ryanlelek (1) make test now passes without warnings. (2) Which pattern should be applied for refactoring the nested functions?

You made the create_meta_info() excellently, without relying on the scope of create_content() or the body variable, so instead of defining create_meta_info() within create_content() we just need to move it to the top of the same file or in a separate file in the app/functions/ directory. this will help when we do unit tests

Thanks for the feedback: I'll move the function create_meta_info to a new file in app/functions. I'll create a seperate pull request.

authors: draptik ryanlelek

repo: gilbitron/Raneto


text:
Revert to previous ECS AMI

Getting stung by this issue with the latest ECS agent: https://github.com/aws/amazon-ecs-agent/issues/478 which causes the job instances to run out of disk space due to the logs growing too large. Reverting to AMI with previous version of ECS agent.

🍍

🍝

I don't use Sundial, but the AMI you used to use is also affected by aws/amazon-ecs-agent#488.

authors: emersonloureiro kevinoriordan nemo83 ziggythehamster

repo: gilt/sundial


text:
Anable to launch !

dbdiff --help
/usr/local/lib/node_modules/dbdiff/dbdiff.js:6
class DbDiff {
^^^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object. (/usr/local/lib/node_modules/dbdiff/index.js:3:31)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)

Upgrade your Node.js version

node --version
v4.2.6

authors: Mounirsky gimenete

repo: gimenete/dbdiff


text:
Flatten secret field, make it configurable

Follow the Helm best practice

In most cases, flat should be favored over nested. The reason for this is that it is simpler for template developers and users.

The task is to change
secret:
  enabled: true

to
secretEnabled: true

And enable the secret name to be configurable with the secretName field.

[ ] Flatten secret field
[ ] Add support for secretName, with {{ template "robustName" .Release.Name }}
[ ] Document the changes

https://github.com/gimlet-io/onechart/commit/6a9f43e0752dfd61841b5d2e25b6135dc25135ac

https://github.com/gimlet-io/gimlet-website/commit/d8c8a544806e0be4dbf05879438c99820098e1d3

repo: gimlet-io/onechart


text:
Firefox 35.0.1 Connection drops after some minutes "Ice failed"

Firefox 35.0.1 Connection drops after some minutes "Ice failed"

On branch? What does the erizoJS logs say?

master branch
2015-02-05 17:09:15.577  - INFO: ErizoController - Socket disconnect  j7dyV3zjFDaO8vlSU0sz
2015-02-05 17:09:15.577  - INFO: RoomController - Removing subscriptions of  j7dyV3zjFDaO8vlSU0sz
2015-02-05 17:09:15.577  - INFO: RoomController - Removing subscriber  j7dyV3zjFDaO8vlSU0sz to muxer  119451550533995040
Seems to be a client problem on Firefox that the WebSocket disconnects. about:webrtc in Firefox tells that the PeerConnection is sill open to Erizo even when there is no data stream anymore:
RTP statistics
outbound_rtp_audio_-1
Local: 17:14:16 GMT+0100 (CET) outboundrtp SSRC: 2838467253 Sent: 24148 packets (1434.6 Kb)

Already more information. Is it the last commit from master (with ice trickle)?
Now we need a little bit more:

Change the file log4cxx.properties in erizoAgent to have NiceConnection=DEBUG and maybe WebRtcConnection=DEBUG
The logs we need to see is the one from erizoJS not erizoController (that's the one you are posting). It should be in erizoAgent, look for the last .log files. Then search for something wrong.

authors: IVBakker peili

repo: ging/licode


text:
Creating view of array in Column-major format

I have a piece of code that gets an input a large vector (representing n vectors of size N) that are in column major format. So size=n*N, rows=N and cols=n. These are vector is packed and contiguous in memory. So in order to work with the given input data, I create a view and use it in matvec computations. However, since the input is in column-major format, and the Dense matrix assumes a row-major format, if (n>1), the following idea fails.
std::vector<double> inputData(N*n);
auto viewInput = gko::matrix::Dense<double>::create( device_executor, gko::dim< 2 >{ N, n },
                                                 val_array::view( host_executor, inputData.size(), inputData.data() ), n );

Is there a better way to create a dense matrix view without actually changing the underlying data. i.e., can I impose column-major format for Dense instead of the default row-major storage ? I didn't see an option for this in the documentation.

@vijaysm, thanks for creating an issue and trying out Ginkgo. Unfortunately, currently we do not have a way to view contiguous data as column-major. Do you have a specific application where you are using column-major storage ?

Thanks for the response. The input vector for which I need to compute SpMV operations is essentially a 2-D dense matrix that is provided by a Fortran subroutine. And the SpMV operations are invoked multiple times during the course of the simulation and so having multiple views would lose any gains that can come out of potential vectorization that will happen with sparse(A)*dense(vec) operations.
Copying the data in the row-major format is not ideal every time this is needed. The ideal solution here would be a Ginkgo view for Dense that understands column-major format as well. If there is a better approach, do let me know.

We are thinking about adding general indexing (row stride + column stride) to our Dense matrix format, so that is not entirely out of reach. What I can't follow is how the performance of A*x can profit from vectorization when x is stored in column-major? In my understanding, this would mean that entries of the same row are scattered across memory, as opposed to being stored next to each other like in row-major, so you need to use vector gather instructions instead of normal vector loads, which usually come with a significant performance penalty.

authors: pratikvn upsj vijaysm

repo: ginkgo-project/ginkgo


text:
Colour scheme for lines

Hi!
May i know what are the available colours for the line?

These are the chartist default colours: https://github.com/gionkunz/chartist-js/blob/develop/src/styles/settings/_chartist-settings.scss#L69-L85
You can customize easily: http://gionkunz.github.io/chartist-js/getting-started.html#colour-up-your-charts

repo: gionkunz/chartist-js


text:
Conditional Formatting of a Point with null value

I love the way that Chartist handles gaps in line charts (I love the way Chartist does a lot of things!).
But, what I would like to do is instead of having a gap in the chart, display the point as an average of the value before and the value after it, and indicating the gap in the data visually in some way.
What I've done so far is instead of sending the data point as null, I send it as -1, and then I intercept it within .on('draw') like so:
if ( data.type === 'point' && data.value.y === -1 ) {
  var triangle = // some code that draws a triangle
  data.element.replace(triangle)
}

I would like to be able to write my own plugin to address this use case, but I can't figure out how to access the y values before and after this point, or if intercepting the data during the draw event is too late anyway.
Further, is it possible to affect the attributes of the line that connects the missing data point, or is the line only drawn as one element?

I've got the beginnings of a plugin started here:
https://gist.github.com/brianrhea/9ecde330b6c9fae136ba
It's still a little too specific to my particular application (currently requires Underscore.js and I have some custom CSS sprinkled in), but hopefully could serve as the beginnings of something.
That code will generate the following chart:

from this data:
{
  "labels": ["1", "2", "3", "4", "5", "6", "7", "8", "9", "10"],
  "series": [
    {
      "name": "Values",
      "data": [9,null,null,7,10,3,null,3,2,1]
    }
  ]
}

Awesome man! Looking forward for the plugin! :-) Tell me when it's ready so I can help you to make the pull request for adding it to the docs site.

Closing this issue, please submit a PR if you'd like to publish the plugin on the chartist website

authors: brianrhea gionkunz


text:
C_Cpp Break or Continue

Description 📜

What is break and continue statement
Difference
Use of both statements in code

Domain of Contribution 📊

[x] C/CPP

/assign

/assign

#1181  duplicate

authors: Suvraneel uditkatyal

repo: girlscript/winter-of-contributing


text:
Opensource : 6.16 Explain everything about Next.js

Description
Description
Opensource : 6.16 Explain everything about Next.js
Domain
Open Source
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/ assign

/assign


text:
ML 3.10 : Outlier Detection using Local Outlier Filter (LOF) (D)

Description
📌  Issues for Week 3
Welcome to 'ML' Team, good to see you here
:arrow_forward: This issue will helps readers in acquiring all the knowledge that one needs to know about ----
Outlier Detection using Local Outlier Filter (LOF).
:red_circle: To get assigned to this issue, add your Batch Numbers mentioned in the spreadsheet of "Machine Learning", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
✔ Domain : Machine Learning
:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.

"Issue Title" and "PR Title should be the same. Include issue number along with it.

Changes should be made inside the Machine Learning/Machine_Learning/Unsupervised_Machine_Learning Branch.

Follow Contributing Guidelines & Code of Conduct before start Contributing.

This issue is only for 'GWOC' contributors of 'Machine Learning' domain.

:white_check_mark: To be Mentioned while taking the issue :

Full name
Batch Number
GitHub Profile Link
Which type of Contribution you want to make :

[ ] Documentation

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎
Domain
Machine Learning
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Ritika Chand
Batch 1
Documentation
https://github.com/RC2208
/assign

issue assigned to @RC2208 Complete this issue within 3 days.

issue assigned to @RC2208 Complete this issue within 3 days.

Yess also its local outlier Factor right? not filter

Tanvi Deshmukh
batch-5
I would like to contribute to this issue.. plz assign it to me.


text:
Complete DP and Greedy

Description
Adding complete tutorial of DP and Greedy problems from basic to expert level.
Domain
DSA
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

!assign

/assign


text:
GET arlas/explore/_describe list twice fields with 'type': "DATE"

In gitlab by @sebbousquet on Jul 21, 2017, 14:46
{
   "name": "dateTimeStamp",
   "type": "DATE",
   "format": "epoch_millis"
},
{
   "name": "dateTimeStamp",
   "type": "DATE"
}

In gitlab by @sylvaingaudan on Sep 11, 2017, 11:48
changed milestone to %13

In gitlab by @sfalquier on Sep 15, 2017, 11:00
removed milestone

In gitlab by @sylvaingaudan on Sep 29, 2017, 09:07
added ~2424198 label

In gitlab by @sfalquier on Sep 29, 2017, 12:23
changed milestone to %16

In gitlab by @sylvaingaudan on Oct 9, 2017, 10:29
changed milestone to %17

In gitlab by @sfalquier on Oct 13, 2017, 15:57
assigned to @sfalquier

In gitlab by @sfalquier on Oct 13, 2017, 15:59
Fixed with nested support of indeces topology.

In gitlab by @sfalquier on Oct 13, 2017, 15:59
closed

repo: gisaia/ARLAS-server


text:
Add a scale bar and a north arrow

geemap version: 0.8.3
Python version: 3.6.9
Operating System: Google Colab

Description
I used COPERNICUS/S2_SR to be able to represent the Lewato volcano eruption, Indonesia.

How can I add a scale bar and a north arrow?
What I Did
import ee
import geemap.eefolium as geemap
from geemap import cartoee as cee

%pylab inline

try:
    ee.Initialize()
except Exception as e:
    ee.Authenticate()
    ee.Initialize()

point = ee.Geometry.Point(123.488, -8.284)

volcano = ee.ImageCollection("COPERNICUS/S2_SR").filterBounds(point).filterDate("2020-11-28", "2020-12-04").first()

plt.figure(figsize=(16, 12))

region = [123.3,-8.5,123.8,-8.18]
vis = {'min':0,'max':6000, 'bands':'B4,B3,B2'}

ax = cee.get_map(volcano, region=region, vis_params=vis)
cee.add_gridlines(ax,interval=(0.1,0.1),linestyle=":")

ax.set_title(
    label = 'Lewato volcano 2020-11-29',
    fontsize = 15
)

plt.show()

Thanks for your help!

To add a scale bar and north arrow one would need to do draw on the figure yourself using matplotlib/cartopy graphics elements. Unfortunately, there really no easy solution available for this right now, although it looks like others have shared code to get started. Here is a thread on stackoverflow regarding this same problem: https://stackoverflow.com/questions/32333870/how-can-i-show-a-km-ruler-on-a-cartopy-matplotlib-plot and another issue thread on the cartopy repo: https://github.com/SciTools/cartopy/issues/490.
I don't think we would want to consider this a feature request for this package given this is more low-level functionality and would be best if implemented in cartopy. I hope this helps.
P.S. That is a pretty amazing image that S2 captured!

Thank you very much for your help @KMarkert.

Thanks to the stackoverflow sample code. I have added two more functions to cartoee, add_scale_bar() and add_north_arrow(). See notebook example - cartoee_scalebar.ipynb
@KMarkert @jdbcode @ErikSeras @GokulGeo

authors: ErikSeras KMarkert giswqs

repo: giswqs/geemap


text:
FAQ Answer on Software Heritage Foundation IDs

Signed-off-by: Ed Warnicke hagbard@gmail.com

LGTM

authors: AevaOnline edwarnicke

repo: git-bom/site


text:
Can git grep have --Author option?

This is a feature request.
From time to time, I want to re-use MY code. So git grep with --Author options is really useful.  My current git version is 2.6.3, looks it doesn't have this option.

@redguardtoo This repository is for the git-scm.com website, not git itself.
From https://git-scm.com/community:

Questions or comments for the Git community can be sent to the mailing list by using the email address git@vger.kernel.org. Bug reports for git should be sent to this mailing list.

sorry

authors: paulschreiber redguardtoo


text:
🛑 inv.bp.projectsegfau.lt is down

In 6989793, inv.bp.projectsegfau.lt (https://inv.bp.projectsegfau.lt/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: inv.bp.projectsegfau.lt is back up in e977ced.

repo: gitetsu/invidious-instances-upptime


text:
🛑 invidious.privacydev.net is down

In 9ca8d30, invidious.privacydev.net (https://invidious.privacydev.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: invidious.privacydev.net is back up in 351ac4a after 58 minutes.


text:
🛑 iv.melmac.space is down

In 2a25ba8, iv.melmac.space (https://iv.melmac.space/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: iv.melmac.space is back up in d4cde12 after 2 hours, 47 minutes.


text:
🛑 search.davidovski.xyz is down

In f9b6ad4, search.davidovski.xyz (https://search.davidovski.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.davidovski.xyz is back up in bb44c0f.

repo: gitetsu/librex-instances-upptime


text:
🛑 search.sethforprivacy.com is down

In c64b00e, search.sethforprivacy.com (https://search.sethforprivacy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.sethforprivacy.com is back up in 2765dd9 after 16 minutes.

repo: gitetsu/whoogle-instances-upptime


text:
🛑 whoogle.lunar.icu is down

In 45aac12, whoogle.lunar.icu (https://whoogle.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.lunar.icu is back up in 40c84cc after 41 minutes.


text:
🛑 whoogle.privacydev.net is down

In aa8090e, whoogle.privacydev.net (https://whoogle.privacydev.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.privacydev.net is back up in 567d913.


text:
GitHub Login page Freeze

Hi,
I don't know if I'm on the right page to submit a bug on GitHub itself but, Houston i have a problem.
Every time I try to connect to GitHub from https://github.com/login and from my PC with Firefox or Brave browser the page takes about 4 minutes to fully load, before I can fill in my login information.
But no problem on Chrome and Edge.
Whether I disable the extensions or restart Firefox with the modules disabled it's always the same problem.

Hey @Kamoba. This is actually a repo for a GitHub Javascript client library. We aren't directly associated with GitHub. I'd recommend contacting their support.

authors: Kamoba j-rewerts

repo: github-tools/github


text:
[GHSA-cxww-7g56-2vh6] @actions/download-artifact has an Arbitrary File Write via artifact extraction

Updates

Affected products
Description
References

Comments
CVE-2024-42471 affects version 2.1.7 not 4.1.7. Go re-read the linked CVE.

Hi there @joshmgross! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

@actions/download-artifact != @actions/artifact, closing

authors: github holmanb

repo: github/advisory-database


text:
Website claims that copyright forbids using software

From http://choosealicense.com/no-license/:

If you find software that doesn’t have a license, that generally means you have no permission from the creators of the software to use, modify, or share the software.

Wait, what? Even not using? I am not a lawyer but this seems surprising to me. But is this actually true? And even if such a restriction applies, is it actually because of copyright law? Or maybe its because of something else?
My gut feeling tells me this claim is false because by the same logic, we would not be allowed by copyright law to “use” copyrighted books (by reading them) because we didn't get permission. ;-)
Can someone who knows more about things like this clear it up, ideally with sources and stuff?
I am also unsure about the “modify” part. Note the text only mentions the modification itself, not the distribution of such a modification. As far my layman knowledge goes, I think copyright is only concerned about copies.

The website doesn't make the claim the title of this issue claims, but I can see how one could get that meaning. One doesn't need permission of the creators/copyright holders for everything. Various limitations and exceptions to their 'exclusive rights' exist, though not much one can count on, especially worldwide. Probably worth noting that on this page.
Use/using isn't a copyright term (those are reproduction, preparation of derivative works, distribution, and public performance/display/broadcast, eg U.S. copyright act definitions, but seems like a good word to...use...as it's how people talk/think about software, encompassing various acts which might fall under one or more of copyright owners' exclusive rights.
Is a copyright owner's permission needed to run a program? If you're running it only for yourself, you're still making copies, necessarily, in order to run the program. The EU directive on computer programs is clear that this is a restricted act, but people who have lawfully acquired software can do it. I don't know that there's as clear a statement in U.S. or other [case] law, but feel free to search and [dis]confirm. If you're running it for other people, you might also be triggering distribution or public performance. These are not completely settled. Software copyright is still a relatively new thing.
This uncertainly does not stop businesses from being shaken down or even raided for simply running software without permission from the copyright holders.
Reading a printed book does not involve making a copy. Digital books and other media does, just like software, making them subject to additional grabs by copyright holders and attendant controversies, e.g., around sale/rental and technical restrictions. So some are concerned about maintaining the "right to read" long term.
Yes, preparation of a derivative work is an exclusive copyright owner right, independent of others. Is this insane? Also yes. ("Moral rights" can also come into play here.) Various exceptions and limitations may or may not apply.
You're right that there are other sources of restrictions on using software besides copyright, including contract (eg EULA), technical (eg DRM), and patent. The first two won't be relevant in the complete absence of any license or technical restrictions, as is usually the case for code made public on a platform like here. The last is only relevant for permission from the creator if they happen to also be the owners of the relevant patents.
Thanks for reporting this and #445. I'll try to slightly modify the no-license page text so that readers who wonder like you can be satisfied, while not making it seem that someone who just wants to choose a license or get someone else to for the first time needs to dive into the abyss in order to act.

It's not about “reader satisfaction” but to make sure the text is not misunderstood.
But thanks for looking into this.


text:
Missing 'runs.' on post-entrypoint configuration for dockefile actions

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#post-entrypoint
What part(s) of the article would you like to see updated?
the 'runs for Docker container actions' part for the 'post-entrypoint' option
Additional information
No response

@rlespinasse Thanks for opening an issue and linking it to your PR! 💖

repo: github/docs


text:
Metadata syntax for GitHub Actions: continue-on-error is not documented for composite actions

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions
What part(s) of the article would you like to see updated?
The documentation for composite actions doesn't mention the continue-on-error field, which has the same semantics as it has in Workflow definitions.
This field is present in the JSON Schema for composite actions, however: https://json.schemastore.org/github-action.json.
It looks like this field was added to composite actions in 2022 (via https://github.com/actions/runner/pull/1763) but the documentation was never updated.
Additional information
No response

@woodruffw Thank you for raising this issue! I'll get this triaged for review :sparkles: Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

Possibly duplicate of #32097

@woodruffw It looks like @janbrasna is right - thank you for catching that, Jan! 💛
I'll go ahead and close this issue given https://github.com/github/docs/issues/32097 has been labeled help wanted, but let us know if we've missed anything on our end ✨

authors: janbrasna nguyenalex836 woodruffw