|
CMYK BLYAT! posted:should i name my new library achilles or dionysus diogenes. always diogenes.
|
# ? May 22, 2022 07:21 |
|
|
# ? Apr 23, 2024 11:40 |
|
CMYK BLYAT! posted:should i name my new library achilles or dionysus diabetes
|
# ? May 22, 2022 07:42 |
|
CMYK BLYAT! posted:should i name my new library achilles or dionysus
|
# ? May 22, 2022 15:35 |
|
MrMoo posted:
just starting if anyone remotely cares: https://www.balenciaga.com/en-us
|
# ? May 22, 2022 16:57 |
|
quote:Jitter started Boomers are awesome.
|
# ? May 22, 2022 17:15 |
|
CMYK BLYAT! posted:should i name my new library achilles or dionysus Dionysus, and only write it at the ballmer peak
|
# ? May 22, 2022 18:00 |
|
Name it Hades
|
# ? May 22, 2022 18:18 |
|
As in Hades nuts ain't suckin themselves
|
# ? May 22, 2022 18:18 |
|
Cassandra because you know it's gonna be bad and you can't do anything about it
|
# ? May 22, 2022 18:25 |
|
Powerful Two-Hander posted:Cassandra because you know it's gonna be bad and you can't do anything about it
|
# ? May 22, 2022 18:35 |
|
sisyphus because it will inevitably get stuck in an infinite loop
|
# ? May 22, 2022 18:36 |
|
mystes posted:Taken and it met the expected fate for an apache foundation project i assume given the way c* worms its way into organizations that
|
# ? May 22, 2022 18:36 |
|
DaTroof posted:sisyphus because it will inevitably get stuck in an infinite loop No no no, name it syphilis and add it to the dependencies but don't tell anybody
|
# ? May 22, 2022 18:46 |
|
Powerful Two-Hander posted:Cassandra because you know it's gonna be bad and you can't do anything about it
|
# ? May 22, 2022 20:23 |
|
that prolly was why the actual cassandra db was named that, wasnt it
|
# ? May 22, 2022 20:27 |
|
nudgenudgetilt posted:diogenes. always diogenes. gonna name the protocol classifier in my router OS diogenes behold! a packet!
|
# ? May 23, 2022 12:56 |
|
I am currently embarked on a project to identify how hard it would be to port an old abandoned Python 2 project to Python 3. It has something resembling a test suite.README posted:
Oh dear.
|
# ? May 24, 2022 10:40 |
|
|
# ? May 24, 2022 10:58 |
|
|
# ? May 24, 2022 11:02 |
|
Antigravitas posted:I am currently embarked on a project to identify how hard it would be to port an old abandoned Python 2 project to Python 3. It has something resembling a test suite. Does it say anything to the effect of "why"?
|
# ? May 24, 2022 11:08 |
|
champagne posting posted:Does it say anything to the effect of "why"?
|
# ? May 24, 2022 11:19 |
|
The why is fine. It's a library for calculating pages and ink coverage of print jobs, so using a well-known print file as its reference it can test the implementations of a myriad of horrid printer languages. But because it's printer languages, everything else is extremely not fine. The fact that some of them are turing complete is the least of its problems. I am going to jettison almost everything in this project, but I drew the shortest straw in the universe that led me to this hell
|
# ? May 24, 2022 11:21 |
|
code:
Python code:
Antigravitas fucked around with this message at 11:29 on May 24, 2022 |
# ? May 24, 2022 11:23 |
|
lmao at the lone comment
|
# ? May 24, 2022 11:28 |
|
"The BBC are reporting that despite 'the very best deal possible,' a failure to agree terms between the BBC and the estate of late sci-fi writer Terry Nation has meant that we will not being seeing TV's most evil villains in the new series, starring Christopher Eccleston and Billy Piper." concerning news
|
# ? May 24, 2022 11:51 |
|
josh04 posted:"The BBC are reporting that despite 'the very best deal possible,' a failure to agree terms between the BBC and the estate of late sci-fi writer Terry Nation has meant that we will not being seeing TV's most evil villains in the new series, starring Christopher Eccleston and Billy Piper." You _are_ talking about terrible programming, so I'm not sure if you're posting in the thread you thought you were.
|
# ? May 24, 2022 13:30 |
|
Antigravitas posted:The why is fine. It's a library for calculating pages and ink coverage of print jobs, so using a well-known print file as its reference it can test the implementations of a myriad of horrid printer languages. I didn't expect the zipfile to be redeemed in the second act drat
|
# ? May 24, 2022 15:07 |
Powerful Two-Hander posted:lmao at the lone comment I mean, where's the lie
|
|
# ? May 25, 2022 07:26 |
|
goddamn segfault with no stacktrace ((
|
# ? May 25, 2022 10:14 |
|
Carthag Tuek posted:goddamn segfault with no stacktrace (( segfault but no one to segblame
|
# ? May 25, 2022 10:43 |
|
it's nobodies segfault but your own
|
# ? May 25, 2022 12:24 |
|
segma balls
|
# ? May 25, 2022 15:42 |
|
well im sure core dumps were properly configured, right?
|
# ? May 25, 2022 18:45 |
|
Powerful Two-Hander posted:it's nobodies segfault but your own
|
# ? May 25, 2022 18:45 |
|
god these vendor docs loving suck and their engineering team are walled behind 3 layers of people so everything is routed back through emails so a question of 'ok so how are you integrating with Docusign? Which of the Auth methods is it? Why do you want to be able to provision users instead of impersonating' gets an answer 2 days later of 'we use Oauth 1.0' which is deprecated by Docusign... also docusign (whose docs are pretty bad but at least detailed) have 4 different OAuth methods and integration types and the use case you describe isn't one of them
|
# ? Jun 1, 2022 22:47 |
|
trying to shore up our oss license compliance from nothing and dear god how the gently caress does anyone do this in a modern software ecosystem even with an automated tool to assist it's a crapshoot cause golang's module dependency introspection is so inscrutable. why the gently caress is there a "go mod why <fartlib>" command that just repeatedly tells you "actually, this library is unnecessary!" despite something in the toolchain clearly having a reason to shove poo poo into go.mod as indirect wasted a couple hours trying to figure out how we'd apparently included a gpl3 lib. as best i can tell someone used "go get" to install a tool for cli use while in their project directory, which of course added it to the project go.mod, and pushed because their repo has no linter test to see if you've run tidy or not. this library wormed itself into the infinity vendored thing clusterfuck in docker/docker and then into our go.mod because our test suite uses docker golang calls to run poo poo. i still can't find a tool to confirm that there's definitely no other reason for an indirect dep, and while it seems unlikely it's a bit iffy since go mod graph will still look at the automatically added mod entry and say "actually, your app includes this module directly!" i dont feel too bad though, between some of the no-license deps are there because libs authored by google (who i'd sorta expect to have the resources to do compliance right) and because the immediate goal of providing a licenses.txt that meets MPL requirements for the stuff we do use is still met--ain't no rule that says you can't also just include a bunch of other random poo poo that isn't actually linked in the end product!
|
# ? Jun 3, 2022 03:48 |
|
CMYK BLYAT! posted:trying to shore up our oss license compliance from nothing and dear god how the gently caress does anyone do this in a modern software ecosystem Have you confirmed your beliefs with your legal team?
|
# ? Jun 3, 2022 05:08 |
|
no luck with git blame go.mod ? also pro tip. just remove it and see if stuff breaks
|
# ? Jun 3, 2022 05:37 |
|
go.mod and go.sum are just placebos, nothing you do in there actually affects anything
|
# ? Jun 3, 2022 07:41 |
|
|
# ? Apr 23, 2024 11:40 |
|
go get a job working in a less lovely ecosystem
|
# ? Jun 4, 2022 14:36 |