|
Bloody posted:im hitting a debug assert in my c# app but cannot attach a debugger for some reason is there a way to get the full stacktrace outta the stupid lil abort/retry/quit window "retry" will ask you to attach a debugger, generally. if you can't attach because it's on a machine w/o a debugger or something, you can create a dump file from task mgr and debug that later.
|
#
¿
Aug 18, 2019 17:56
|
|
|
|
| # ¿ Sep 20, 2024 07:47 |
|
|
Soricidus posted:just use csv and awk, your data isn’t that big or important there must be some dataset out there that is both Big and important? but I can't think of one
|
|
#
¿
Nov 2, 2019 18:08
|
|
|
it lets the compiler check your code for errors that otherwise would be caught at runtime. it provides built-in documentation for what variables are meant to be that you'd otherwise need to have the discipline to document manually.
|
|
#
¿
Nov 2, 2019 18:17
|
|
|
you know what, I have decided I'm OK with mixed line endings in a single project. hell, in a single file. join me; set yourself free.
|
|
#
¿
Dec 12, 2019 07:27
|
|
|
Shaggar posted:this is basically how entity framework works and its the loving worst thing ever. you mean for joined collections on the orm objects? yeah those are bad and I just stopped using them after a while
|
|
#
¿
Dec 20, 2019 09:17
|
|
|
I remember arguing that we were clearly wrong for storing a time in *local* time as a 'source of truth' in the database; it made calculations harder and isn't even unambiguous, it should be UTC. But it was a record of when an event happened, entered by a user in local time, and i now realize that storing it that way was more correct. That's my story.
|
|
#
¿
Dec 29, 2019 23:32
|
|
|
prisoner of waffles posted:everything in this post is correct in a good VCS you'd be able to view and search the history however you like, instead of relying on committers to commit the "right way" so that the history-searching method your team prefers works.
|
|
#
¿
Mar 14, 2020 16:56
|
|
|
Krankenstyle posted:easier to ctrl-f in a single file this is true and good advice if people are using partial classes in c#
|
|
#
¿
Mar 28, 2020 18:17
|
|
|
IMO he's right that pushing straight to master is better for small teams/projects (I would say 3 or 4 people; 6 is probably pushing it). PRs mostly just waste everyone's time and increase merge conflict risk under those circumstances.
|
|
#
¿
May 22, 2020 05:01
|
|
|
of course "permission to push to master" in git actually means "permission to irreparably destroy your entire repo" but that's a git problem not a workflow one
|
|
#
¿
May 22, 2020 05:02
|
|
|
kinda like when i bought a sega saturn, i had so many reasons it was great & better than playstation
|
|
#
¿
May 23, 2020 00:19
|
|
|
zokie posted:Donyou really think that when I describe a system that builds, tests, lints, and looks for breaks in GraphQL and OpenAPI schemas, that’s used create small feedback cycles that it there isn’t a CI/CD pipeline for the trunk also? But that pipeline has additional tests that take to long to run. All of these things can be done, oftentimes better and more efficiently, without PRs. Some people are misunderstanding nbsd's point about hidden dependencies between branches -- you can't catch those by merging master into your branch before running tests, unless you have a queue of branches to be merged in a specific order, which no one does. Your "additional tests that take too long" to run on branches is another point against a PR-based workflow (you're still merging things that you can't deploy). The typical PR workflow is designed to slow things down and enforce process and discipline. This is often very good when you're working on a large/critical system or with people who aren't disciplined, but saying they're universally the better choice is just cargo culting.
|
|
#
¿
May 25, 2020 00:29
|
|
|
I guess I think of them a sometimes-necessary evil, that should be avoided if you can get away with it, rather than something to strive towards.
|
|
#
¿
May 25, 2020 00:34
|
|
|
Aramoro posted:As soon as you say 'If you don't want to you can just commit to master directly' then that becomes the only process because people are vain and arrogant and won't follow a process with even a single more step if they don't have to. Obviously 'they' know thier change is all fine and good, it was the other rear end in a top hat that broke it. They were going to break everything with their crappy commit either way. Without PRs you have to fix it immediately. With PRs you don't. There are many situations where the former is better.
|
|
#
¿
May 25, 2020 19:08
|
|
|
it was kind of cool working in .NET before it had a package manager / package ecosystem. if you wanted to ship a library, you had to think very carefully about which dependencies to require and most libs were just standalone and you could easily check them in or stick them on a shared drive somewhere. package-manager-based ecosystems make it so easy that devs get lazy and any library you depend on is likely to bring in a tree of 100 other dependencies. I guess what I'm saying is, don't release a new language without a robust and feature-ful standard library plz.
|
|
#
¿
May 25, 2020 19:22
|
|
|
Ciaphas posted:We currently have a monorepo containing about a dozen separately-built projects all depending on some common includes. We're transitioning soon from P4 to Git so I've got a window to reorganize this what're you trying to accomplish by reorganizing it. smaller checkouts? preventing accidental circular dependency commits?
|
|
#
¿
May 27, 2020 15:56
|
|
|
Doom Mathematic posted:If the master branch changes while the PR is open - for example, if a different PR is merged first - the CI pass is invalidated and has to be rerun.) If the reviewer requests changes, the PR cannot be merged. If the CI build fails, the PR cannot be merged. The temptation in this thought experiment here is to make one of the implicit promises of a PR-based workflow -- that master is never broken -- actually real. But it's not practical at anything but the smallest scale. You're giving up all horizontal scalability in your build process, and the smaller and more frequent your PRs are, the worse it becomes.
|
|
#
¿
May 31, 2020 18:12
|
|
|
null was a mistake
|
|
#
¿
Jun 5, 2020 05:02
|
|
|
can I get a job in embedded dev if i beat shenzen I/O?
|
|
#
¿
Jun 5, 2020 05:02
|
|
|
Sapozhnik posted:of COURSE this was written by some breathtakingly arrogant Apple fuckstain, how am I not surprised are you sure he was from apple, it sounded to me like he just didn't want to break compatibility for a major player but lol breaking compatibility sure as hell wouldn't ever stop apple from anything ever are c++ modules going to make this stupid problem go away?
|
|
#
¿
Aug 1, 2020 03:15
|
|
|
Gaukler posted:I love that, as an industry, we decided reproducibility is so hard that we better just schlep around entire filesystems recently at work we discussed making some methods that operate on a ~30MB state thread-safe without needing to duplicate the state. it' s like uhhh okay but we've basically decided as an industry that even sharing an operating system with another app is too hard, and we're going to very carefully try to minimize locking on this 30MB state object?
|
|
#
¿
Aug 8, 2020 02:21
|
|
|
Plorkyeran posted:there's no inherent reason why async/await can't give useful stack traces. i don't know if it doesn't in js because the spec is poo poo and accidentally made it impossible or if v8 just doesn't give a gently caress. probably both. In chrome dev tools you can't add variables to the watch window or see their value in the console for source-mapped JS code. You can mouse-over them though. I don't know how people put up with it. Maybe part of why JS devs are so obsessed with filesystem watchers that auto-rebuild and restart their app.
|
|
#
¿
Aug 14, 2020 06:52
|
|
|
Powerful Two-Hander posted:terrible programming: looks like the vendor never considered that someone might use a session to download hundreds of thousands of items and didn't bother implementing any temp file cleanup except on session shutdown. temp file cleanup of some kind was implemented, sounds like a good vendor.
|
|
#
¿
Aug 17, 2020 18:03
|
|
the available disk space on those servers.
|
Twerk from Home posted:actually, one single commit merged back to master will result in multiple new tags does it cause any problems?
|
|
#
¿
Oct 10, 2020 20:35
|
|
|
it's always namespaces. nobody can understand those things. and even if you understand them, save everybody else the trouble please.
|
|
#
¿
Nov 20, 2020 04:53
|
|
|
Shaggar posted:namespaces are ez and good im glad your app can automatically parse and process XML from all kinds of different sources and understand the context and common data between them with no extra work thanks to the metadata included in the documents, but somehow mine still can't
|
|
#
¿
Nov 20, 2020 18:28
|
|
|
love toquote:XmlNamespaceManager.AddNamespace("woop", "http://some-dudes-awesome-namespace.com") edit: even for something like XMLSchema-instance... i think an XSL parser could manage to figure out what a <xsl:template> is even if the element name was actually "xsl:template" and this namespace technology never existed cool av fucked around with this message at 20:32 on Nov 20, 2020 |
|
#
¿
Nov 20, 2020 20:27
|
|
|
DELETE CASCADE posted:our current solution: just throw the loving namespace away and compare only the local name same
|
|
#
¿
Nov 20, 2020 21:35
|
|
|
Achmed Jones posted:hot take coming in the C++ version library adds in the neighborhood of 50MB to your binary size like lol how hard is it to serialize ints and strings? they have a "lite" version that's only like 10MB. also i bet most people using it are transferring it over HTTPS
|
|
#
¿
Nov 21, 2020 05:51
|
|
|
jesus WEP posted:oh wow i am so worried about my xml being human readable because it’s not like there’s a million tools that you can paste it into to display it nicely internet explorer all the way. please assist my issue here is my input file: quote:<?xml version="1.0"?>
|
|
#
¿
Nov 21, 2020 17:20
|
|
|
the only thing that sounds kinda off is the back-end pushing a new token to the client? (is there always just one client? will they definitely be logged in when the manager approves it?) and I guess if they need 2 temp. roles they have to request them both in a single transaction.
|
|
#
¿
Dec 3, 2020 00:44
|
|
|
the solution to the problems caused by a queue is, of course, another queue
|
|
#
¿
Dec 3, 2020 01:36
|
|
|
actually every programming language is bad
|
|
#
¿
Jan 9, 2021 21:01
|
|
|
love debugging in containers & especially k8s
|
|
#
¿
Jan 10, 2021 02:00
|
|
|
kinda cool that the solution to dependency hell was to store every permutation of all versions of every dependency ever used by every app forever as container images
|
|
#
¿
Jan 10, 2021 02:17
|
|
|
hm i recently implemented serilog in a project and it was pretty painless but as I was doing so I noted the only useful thing it has is a standard configuration for enabling different log levels for differently named logs. (wow it can json serialize the arguments to my log function what a world lol) is it going to bite me later on?
|
|
#
¿
Jan 16, 2021 08:39
|
|
|
going on 3 weeks now trying to fix a client on a 12-hour timezone difference that has 2 problems: (1) they are using an outdated version of a "plugin" DLL that they wrote and provide themselves and (2) they have a missing root cert on some of their machines that breaks the TLS connection between that DLL and their web service the combination of 2 problems and one of them only affecting some machines is just too much and now i have to get up early to meet with them again ugh
|
|
#
¿
Feb 3, 2021 03:14
|
|
|
allowing both single- and double-quotes for strings in a language is wrong
|
|
#
¿
Feb 4, 2021 05:58
|
|
|
Shaggar posted:with our app at some point in the next year or so we're gonna start overhauling it and im considering converting it to a webapp with fully server side application state. the idea being when dumbass users close the browser they can just go back to the webapp and be immediately back where they were. you gonna store the state in sql server? ive done this in an app layer and it's ok but kind of annoying to do updates
|
|
#
¿
Feb 4, 2021 06:06
|
|
|
|
| # ¿ Sep 20, 2024 07:47 |
|
|
it's so sad that git became the predominant source control tool, we should've waited for a 2nd generation of dvcs tools to come out before settling down.
|
|
#
¿
Feb 6, 2021 06:48
|
|