|
GameCube posted:i'd like sourcetree more if it were open source. not out of zealotry but out of the fact that it's buggy and lacking many simple features, for example you can't do git push --force, at least in the windows version, because they feel that force pushing is bad force pushing is bad. not being able to do it from a gui seems like a perfectly reasonable decision to me.
|
# ? Jul 15, 2016 03:46 |
|
|
# ? May 27, 2024 01:57 |
|
force pushing on short-lived branches you own is good exposing force push in a gui would be a disaster even for the above use case b/c it would enable ppl who dont really know what theyre doing to cause disaster to themselves and potentially others, although usually the repo should have sane force push permissions
|
# ? Jul 15, 2016 06:18 |
|
also sourcetree combined w/ dropping to the cli is good sourcetree has some really loving obnoxious bugs though
|
# ? Jul 15, 2016 06:19 |
|
also if you force push make sure you use --force-with-lease b/c git has historically hated sane defaults
|
# ? Jul 15, 2016 06:21 |
i usually use sourcetree since i like guis, though sometimes it starts to do sourcetree things and i end up reading it's logs and janitoring things in terminal to see what's up
|
|
# ? Jul 15, 2016 06:51 |
i like that they have coded a particular workflow in so i can just lazily click things and maintain structure that please my eye
|
|
# ? Jul 15, 2016 06:52 |
|
GameCube posted:my first day of git my autistic coworker told me that the best first step when troubleshooting build issues was to run a git clean -xdf. that is a terrible habit to get into, for reasons which i hope are obvious
|
# ? Jul 15, 2016 07:52 |
|
LeftistMuslimObama posted:
This usually comes up with very specific resources, but the basic idea is this code:
But judging from whats been said about this particular case, its completely hosed anyway.
|
# ? Jul 15, 2016 08:56 |
|
comedyblissoption posted:also if you force push make sure you use --force-with-lease b/c git has historically hated sane defaults quote:What --force-with-lease does is refuse to update a branch unless it is the state that we expect; i.e. nobody has updated the branch upstream. In practice this works by checking that the upstream ref is what we expect, because refs are hashes, and implicitly encode the chain of parents into their value. god gently caress you git brb moving everything to hg
|
# ? Jul 15, 2016 12:25 |
|
my stepdads beer posted:god gently caress you git I really like working with hg and am glad I chose it 5 years ago (mostly cause git windows clients were buillshit) but to this day the tooling around it isn't as refined as with git. I spent like a week looking for good Code Review tools and nothing worked satisfactorily with our Rhodecode server and/or required post push reviews or uploading patches to a server.
|
# ? Jul 15, 2016 12:43 |
|
Stringent posted:force pushing is bad. not being able to do it from a gui seems like a perfectly reasonable decision to me. comedyblissoption posted:force pushing on short-lived branches you own is good and yet as soon as somebody requested it they put it in the os x build, but not the windows build
|
# ? Jul 15, 2016 12:56 |
|
also when I was setting up a new machine I googled sourcetree and got an ad for something called kraken which boldly claimed BETTER THAN SOURCETREE which a) is not really a high bar and b) it wasn't, lol. in fact it was dog poo poo garbage
|
# ? Jul 15, 2016 12:59 |
|
please do not sign your posts
|
# ? Jul 15, 2016 13:47 |
|
eschaton posted:you got a source for that? as far as I know, Xserve always used standard 3.5in SATA drives and they would always work i think he's confusing it with the fact that you had to buy the drive sleds from apple if you had a one-disk xserve, it came with fake spacers in the other slots. annoying, but all OEMs do that E:F;B ~Coxy fucked around with this message at 14:04 on Jul 15, 2016 |
# ? Jul 15, 2016 14:00 |
|
my stepdads beer posted:god gently caress you git hahahaha "when force pushing, I want my push to silently override absolutely everything upstream, including new commits that appeared after I started my push" - a thing that the git developers actually believe
|
# ? Jul 15, 2016 14:02 |
|
LeftistMuslimObama posted:so it's not really that they are in multiple lists but that somehow references to the nodes are ending up in the wrong place under mysterious circumstances. that's a bitch to debug because how do you even catch a reference creation at an unknown point to get a stack trace? "wrong" and yet working. it has something to do with what data is being logged to what file Xarn posted:But judging from whats been said about this particular case, its completely hosed anyway. yyyup memory leaks it is
|
# ? Jul 15, 2016 14:02 |
|
comedyblissoption posted:also sourcetree combined w/ dropping to the cli is good not a bug per se but every few weeks I get an email notification from people upvoting / +1 this issue: https://jira.atlassian.com/browse/SRCTREE-1191 and it never gets fixed
|
# ? Jul 15, 2016 14:05 |
|
~Coxy posted:not a bug per se but every few weeks I get an email notification from people upvoting / +1 this issue: this is something i would have put in my initial release of this software because holy poo poo that sounds confusing and useless like day 1 working here i color coded dev/test/staging/live in everything
|
# ? Jul 15, 2016 15:26 |
|
GameCube posted:also when I was setting up a new machine I googled sourcetree and got an ad for something called kraken which boldly claimed BETTER THAN SOURCETREE which a) is not really a high bar and b) it wasn't, lol. in fact it was dog poo poo garbage its a webview app lol its so awful
|
# ? Jul 15, 2016 15:34 |
Jabor posted:hahahaha I still don't understand why you would be force pushing to a shared repository anyways. That just seems like a bad idea.
|
|
# ? Jul 15, 2016 17:21 |
|
protip: if a repo wont let you force push, just delete the branch first and then push it again.
|
# ? Jul 15, 2016 17:47 |
|
VikingofRock posted:I still don't understand why you would be force pushing to a shared repository anyways. That just seems like a bad idea. Private topic branches that you want backed up to the central server. If nobody other than you is touching a branch then force-pushing is fine.
|
# ? Jul 15, 2016 18:21 |
|
have i mentioned how much i hate TryParse lately?
|
# ? Jul 15, 2016 18:27 |
|
HoboMan posted:have i mentioned how much i hate TryParse lately? Idk, I don't think there's anything bad about it that can't be solved with a wrapper
|
# ? Jul 15, 2016 18:39 |
|
every parse is a try parse,
|
# ? Jul 15, 2016 18:50 |
|
NihilCredo posted:Idk, I don't think there's anything bad about it that can't be solved with a wrapper i shouldn't have to write one and how do i make one that won't confuse other people?
|
# ? Jul 15, 2016 19:12 |
|
comedyblissoption posted:also sourcetree combined w/ dropping to the cli is good when a hacker gotta force a push drop into the shelllllllll
|
# ? Jul 15, 2016 19:12 |
|
HoboMan posted:i shouldn't have to write one and how do i make one that won't confuse other people? XML comments. If they prefer to ignore your wrapper and keep playing the ref game with vanilla TryParse, no biggie. My perspective is probably biased because I can do pretty much whatever I want at work, but personally I never hesitate about adding a new function to the Utils module if I think it's even slightly beneficial. poo poo I added .IsOneOf() and .IsNotOneOf() extension methods for structs and strings just because they read better than .Contains().
|
# ? Jul 15, 2016 20:09 |
|
i replaced TryParse with CanParse then Parse because LINQing with TryParse is like impossible so i'd rather filter a dataset down to definitely parseable data then select it through the normal parse
|
# ? Jul 15, 2016 20:16 |
|
Bloody posted:i replaced TryParse with CanParse then Parse because LINQing with TryParse is like impossible so i'd rather filter a dataset down to definitely parseable data then select it through the normal parse isn't filter then map the same as a flatMap (or andThen or whatever it's called in c#) that returns an option?
|
# ? Jul 15, 2016 20:26 |
|
gonadic io posted:isn't filter then map the same as a flatMap (or andThen or whatever it's called in c#) that returns an option? c# doesn't have option types, so no (the only flatMap in c# is SelectMany which works for collections), although in this particular case you're parsing a value type so you could in principle define the same rules using nullable<T> in f# it would be a Seq.choose, but since the signature of f#'s Thing.tryParse is string -> bool * Thing (as opposed to string -> Thing option) you'd still be looking at a Seq.filter >> Seq.map operation. NihilCredo fucked around with this message at 21:03 on Jul 15, 2016 |
# ? Jul 15, 2016 21:00 |
|
having the fattest of fingers, i personally find the visual studio feature of copying the line you are on whenever you press ctrl+c extremely annoying when i meant to press ctrl+v and now i have lost what was in the clipboard e: oh wait this is the internet, i mean: WHO THE gently caress DESIGNED THIS STUPID USELESS poo poo? gently caress, visual studio is an active dumpster fire and the .NET stack can suck my sack HoboMan fucked around with this message at 22:18 on Jul 15, 2016 |
# ? Jul 15, 2016 22:15 |
|
NihilCredo posted:Idk, I don't think there's anything bad about it that can't be solved with a wrapper programming.txt
|
# ? Jul 15, 2016 22:18 |
|
NihilCredo posted:c# doesn't have option types, so no (the only flatMap in c# is SelectMany which works for collections), although in this particular case you're parsing a value type so you could in principle define the same rules using nullable<T> so you're left with two methods that both fail to use the type system to encode invariants. i really want to like f# but having all of the legacy of c# libraries and all of the legacy of the ocaml language seems to be p annoying at times for bool * Thing, if the parse failed and the bool is false is that thing null or an exception or is it unspecified?
|
# ? Jul 15, 2016 23:10 |
|
although we've got a new person at work with mostly (lots of) python experience. trying to explain the intricacies of how the implicits/traits stack in a large scala project that uses spray/akka is...not great. half of the time i end up with "this is the exact way to do it to make it work. yes it looks the same as the other ways that should work but give actively misleading compiler messages."
|
# ? Jul 15, 2016 23:11 |
|
HoboMan posted:having the fattest of fingers, i personally find the visual studio feature of copying the line you are on whenever you press ctrl+c extremely annoying when i meant to press ctrl+v and now i have lost what was in the clipboard this wouldn't happen if you installed viemu.
|
# ? Jul 16, 2016 03:38 |
|
HoboMan posted:having the fattest of fingers, i personally find the visual studio feature of copying the line you are on whenever you press ctrl+c extremely annoying when i meant to press ctrl+v and now i have lost what was in the clipboard turn it off then
|
# ? Jul 16, 2016 04:06 |
|
NihilCredo posted:c# doesn't have option types, so no (the only flatMap in c# is SelectMany which works for collections), although in this particular case you're parsing a value type so you could in principle define the same rules using nullable<T> i mean, for reference types you're probably never going to parse a legitimate input as null either. a standard tryParse pattern of "returns the result on success, or null on failure" would suck in its own ways but would be generally preferable to the existing boolean+outparam version.
|
# ? Jul 16, 2016 04:11 |
|
Jabor posted:i mean, for reference types you're probably never going to parse a legitimate input as null either. a standard tryParse pattern of "returns the result on success, or null on failure" would suck in its own ways but would be generally preferable to the existing boolean+outparam version. the one advantage i can think of is that its harder to carelessly use a null return value with the bool + out version.
|
# ? Jul 16, 2016 04:42 |
|
|
# ? May 27, 2024 01:57 |
|
although there's probably a million naked calls to tryparse out there that don't bother to check or capture the return value
|
# ? Jul 16, 2016 04:43 |