01:00:32 selsta: git clone https://github.com/monero-project/monero.git && cd monero && git submodule init && git submodule sync && git submodule update && git checkout v0.17.2.0 && git submodule update # this fails, only --recursive on the update or the clone would fix it 01:01:20 lru: you have to do ?git submodule sync` 01:01:26 sorry, typo 01:01:36 I did, see above :-) 01:01:39 you have to do `git submodule sync`after you checkout a branch / tag. 01:01:45 not before 01:01:47 ok, let me try 01:02:34 yep, order matters, thanks 01:03:30 `git submodule sync` and `git submodule update --init --force --recursive` usually solve all submodule issues 01:04:18 I see the .gitmodules file changed between master and v0.17.2.0, which makes sync make sense now 01:05:28 yep, we changed a submodule to upstream 05:01:30 sometimes the window doesn't close; other times, if I leave it a few seconds, it "closes" but continues to run in the background 05:02:59 or if I click the 'x' button twice. I'm not sure how this user would have had an instance running unknowningly without something similar happening, but perhaps 05:25:55 Lyza: It COULD be related to this, since you're talking about closing the app: 05:25:55 https://github.com/monero-project/monero/pull/7859 05:26:01 This and the linked PRs. 05:29:55 I don't know how much into C++ you are, but destructors are being called when an application exits. 07:43:08 And Undefined Behavior earns its name. 07:58:37 * mj-xmr[m] uploaded an image: (5KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/OpuZYtsdLmtuSCTAeYhHNUnC/image.png > 07:58:41 "stopwatch" <- Nice try. 12:48:06 mj-xmr[m]: it's a GUI issue 13:07:27 " I don't know how much into C++ you are" just enough to be dangerous :D 13:07:54 but yeah it's a GUI issue tho 14:25:42 https://github.com/monero-project/monero/issues/7889 14:43:24 ^ proposal on deprecating integrated addresses due to their bottlenecking of batching withdrawals and other reasons, comments would be appreciated. 15:00:17 Triptych embedded data could be used to store up to 3 of those per ring. 15:05:14 Isn't it only per tx? 15:13:35 +1 for anything which makes the network more homogenous 15:15:34 IMO the major reason would be UX, the concept of integrated address is difficult to explain to new users 15:15:50 especially when they send to an integrated address and the base address appears somewhere in the wallet and they think they sent to the wrong address 15:23:28 "especially when they send to..." <- The UX for this is *awful* as a Ledger user. 15:23:40 The Ledger displays the non-integrated address, so it never matches. 15:24:07 I would love to see IAs deprecated/removed in favor of subaddresses once and for all. 15:32:33 As said in the github proposal, it probably makes sense to embed a "subaddress only" plan in with whatever the eventual "big ring upgrade" ends up beinh 15:32:56 As that will require big upgrades across the ecosystem regardless 15:56:54 I just finished making a payment processor for my website that uses integrated addresses, because I read that integrated addresses were the more performant option when tracking many payments as once. 15:56:54 It was also easier to implement, because I didn't need to synchronize any counters between threads to keep track of which subaddresses are in use at any point in time. 15:56:54 Do the downsides of integrated addresses outweigh these advantages? 18:13:05 carrington: Seth your comments on the issue would be appreciated, otherwise it'll get lost in the noise. 18:13:13 * carrington: Seth your comments on the github issue would be appreciated, otherwise it'll get lost in the noise. 18:13:23 Yes, sorry, will comment there! 18:24:20 > <@busyboredom:monero.social> I just finished making a payment processor for my website that uses integrated addresses, because I read that integrated addresses were the more performant option when tracking many payments as once.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/7af556b6898aad446bc338d36216e64be02f22e6) 18:31:40 Fair enough, I'm happy to switch my project to subaddresses if that really is the recommended route now :) 18:32:58 Or if it ends up being the recommended route 18:33:52 It is the recommended route, and has been since it appeared on mainnet. 19:07:02 Sounds good, subaddresses it is then. Side note then since it seems its info might be outdated, monerodocs is where I got my info when deciding whether to use integrated addresses or subaddresses: https://monerodocs.org/public-address/integrated-address/ 23:50:11 is this normal: Exception: boost::wrapexcept 23:50:17 found in the logs