Janitor Prime posted:We have all the threads you want and they operate in the way you describe. there is also cat thread that is literally 2nd largest thread in forums, also has literal hundreds of gigabytes of homegrown cat jpegs
|
|
# ? Jul 31, 2018 17:48 |
|
|
# ? Apr 24, 2024 03:29 |
|
cinci zoo sniper posted:there is also cat thread that is literally 2nd largest thread in forums, also has literal hundreds of gigabytes of homegrown cat jpegs including mine
|
# ? Jul 31, 2018 18:14 |
|
Phobeste posted:- 6.5 figgies means whatever you want it to mean above 100k
|
# ? Jul 31, 2018 18:22 |
|
cinci zoo sniper posted:there is also cat thread that is literally 2nd largest thread in forums, also has literal hundreds of gigabytes of homegrown cat jpegs what's the biggest thread if not catte thread
|
# ? Jul 31, 2018 18:56 |
|
Captain Foo posted:what's the biggest thread if not catte thread Cspam trump non-lol thread is loving absurd, a good few thousand posts a day
|
# ? Jul 31, 2018 19:00 |
|
gonadic io posted:Cspam trump non-lol thread is loving absurd, a good few thousand posts a day
|
# ? Jul 31, 2018 19:02 |
yes, election season trump thread did smash through 10000 pages in a few months i think. it was basically so big the page count dropdown element was a few megabytes large list of page numbers and everything. uspol always was spammy but since trump its absolutely something else cinci zoo sniper fucked around with this message at 19:09 on Jul 31, 2018 |
|
# ? Jul 31, 2018 19:07 |
yeah i looked up and the election thread was closed at 14088 pages and tehre are like 50 thousand trump pages combined across all threads
|
|
# ? Jul 31, 2018 19:15 |
|
c tp s: fighting with the float_cmp library for fuzzy float comparisons. for some reason my floats are a surprising number of ulps apart!
|
# ? Jul 31, 2018 19:36 |
|
also, using debug_asserts for test-time invariants has been beneficial
|
# ? Jul 31, 2018 19:36 |
|
cinci zoo sniper posted:the election thread was closed at 14088 pages Lol nice
|
# ? Jul 31, 2018 19:49 |
|
Bloody posted:is there a term for shoehorning systems into the same interface even if it doesnt make any sense shoehorning also: pigeonholing
|
# ? Jul 31, 2018 19:54 |
|
gonadic io posted:Lol nice serious lomarf
|
# ? Jul 31, 2018 19:54 |
|
cinci zoo sniper posted:there is also cat thread that is literally 2nd largest thread in forums, also has literal hundreds of gigabytes of homegrown cat jpegs I'm allergic to cats
|
# ? Jul 31, 2018 20:05 |
|
Every single one of our automated UI tests are now failing because they can't create test accounts and users. Turns out the tests are somehow coupled to the implementation details of our Users API and broke when a change was made to it
|
# ? Jul 31, 2018 20:57 |
|
ThePeavstenator posted:Every single one of our automated UI tests are now failing because they can't create test accounts and users. Turns out the tests are somehow coupled to the implementation details of our Users API and broke when a change was made to it Sounds to me like the tests are working correctly? You almost shipped a breaking API change, well caught.
|
# ? Jul 31, 2018 21:00 |
|
Doom Mathematic posted:Sounds to me like the tests are working correctly? You almost shipped a breaking API change, well caught. The UI hits an orchestration/gateway layer, so the tests shouldn't have needed to be updated when changes underneath that layer were made. Also when I say "coupled to implementation details" I'm saying I was treated to discovering that the tests literally insert records into the user DB and fire the same events as the Users API.
|
# ? Jul 31, 2018 21:10 |
|
The good news is that I'm not the person that has to fix this.
|
# ? Jul 31, 2018 21:38 |
|
cinci zoo sniper posted:yeah i looked up and the election thread was closed at 14088 pages and tehre are like 50 thousand trump pages combined across all threads metafilter also has about 40% of their comment volume talkin orange dipshit now it's the fate of all internet things just as it is now the fate of all the world
|
# ? Jul 31, 2018 21:52 |
|
gonadic io posted:I'm attempting to use rust's async/generators stuff so my delay(1ms) don't block but just yield in the control loop to allow other processor going on and jeez I don't really get how the nb (non blocking) library's await macro interacts with the rust generator await poo poo i've been playing around with this here if you want to take a look - theres multiple ways of handing this stuff. the main problem is that the await!() macro from `nb` is generator aware but not async function aware, as async functions have to notify their runtime that they want to be polled again. the runtime (called an Executor) doesn't poll every future in a loop constantly - it uses a waker to organize scheduling.
|
# ? Jul 31, 2018 22:46 |
|
i've tried twice to make my inconsistent type param and variable lettering more consistent and each attempt has covered my project in slurs and MAGAs
|
# ? Jul 31, 2018 23:43 |
|
tinaun posted:i've been playing around with this here if you want to take a look - theres multiple ways of handing this stuff. the main problem is that the await!() macro from `nb` is generator aware but not async function aware, as async functions have to notify their runtime that they want to be polled again. the runtime (called an Executor) doesn't poll every future in a loop constantly - it uses a waker to organize scheduling. gonna take a while to digest the futures part of this BUT if i'm making a custom future executor wouldn't it just be easier to do the same to generators instead? or are generators obseleted by the await async stuff? MALE SHOEGAZE posted:i've tried twice to make my inconsistent type param and variable lettering more consistent and each attempt has covered my project in slurs and MAGAs lenses in haskell have 4 type params that are generally called s, t, a, and b
|
# ? Aug 1, 2018 00:08 |
|
ThePeavstenator posted:Every single one of our automated UI tests are now failing because they can't create test accounts and users. Turns out the tests are somehow coupled to the implementation details of our Users API and broke when a change was made to it i have inherited a project in hwich someone thought good testing required reproducing the state of the whole loving company. every little change breaks multiple tests that each implicitly test all sorts of magical horeshit. the tests are way more complicated, and poo poo probably more lines of code than the actual system gently caress these people
|
# ? Aug 1, 2018 01:00 |
|
AWWNAW posted:and poo poo probably more lines of code than the actual system that's not really a bad smell though
|
# ? Aug 1, 2018 03:26 |
|
yeah unless their test cases are invalid that sounds pretty nice
|
# ? Aug 1, 2018 03:30 |
|
That sounds horrible. The point of tests is to help you tell when something is an (unexpectedly) breaking change. If you need to change the tests for every single non-breaking change as well, the tests are providing no value.
|
# ? Aug 1, 2018 03:42 |
|
tests are to prove correctness of your code
|
# ? Aug 1, 2018 04:09 |
|
I have tests for a codebase with no abstractions, no dependency injections. Imagine MVC, but no models so controllers and views are directly touching database tables. "Tests" are set up by loading XML files which contain database state before the tests are run. These XML files are loaded into a database which is complicated and many foreign keys, therefore if I "test" a feature that touches table A that has a dependency on table B, my XML file needs to have table A and table B state/data in it. If table B has dependency on table C, then XML file has A,B and C in it. And so on so on. All these XML files are produced by hand. There is no way to use a tool. The XML files load directly into the database. This means that when I load a state on which I perform my tests, there is no guarantee that this database state is actually legitimate in the application itself. There are no factories or repositories where I can use the same logic that production code uses to create conceptual data entries in a test environment. As expected, this leads to developers hand crafting application state XML documents that serve as basis for tests cases that are impossible to ever happen in production, but these tests are apparently what is used to show that the feature works. The sheer expense involved in writing these XML files also mean at most, only the happy path test is written and edge cases are manually tested by some QA on staging environments.
|
# ? Aug 1, 2018 05:04 |
|
I recently discovered the joy of injecting mock services into other services for the purposes of testing. I was all groaning about setting up a user just right so the call to PermissionService.hasBoner() would return true when ButtService.getAvailableButtTypes() called it. Then I just mocked PermissionService so hasBoner() would return what I wanted and injected that into ButtService. It was good poo poo. My controllers still have too much stuff going on, though, with little coverage.
|
# ? Aug 1, 2018 05:18 |
|
CPColin posted:I recently discovered the joy of injecting mock services into other services for the purposes of testing. I was all groaning about setting up a user just right so the call to PermissionService.hasBoner() would return true when ButtService.getAvailableButtTypes() called it. Then I just mocked PermissionService so hasBoner() would return what I wanted and injected that into ButtService. It was good poo poo. This is why you make an orchestrator layer that you have your controller make one call to. It makes your controllers a lot cleaner and easier to test because you just need to mock one service and make sure the controller returns the right response type. It also makes it easier to test all the stuff injected into your orchestration layer because you're just testing plain old methods now. Our UI tests are a completely separate code repo that are basically supposed to be more robust smoke tests. They use Selenium to actually run a browser and click through the app, which is why it's all the more that the tests were ever coupled to any APIs, especially ones under the gateway layer, and especially especially the database implementation of those APIs. ThePeavstenator fucked around with this message at 06:17 on Aug 1, 2018 |
# ? Aug 1, 2018 06:11 |
today i tried to push file through sftp in python, and it worked with first stack overflow copy paste, so 20 minute effort where most was waiting for pycharm to index paramiko and pysftp. we have an entire development team of a product saying “it’s endpoint fault” for 3 weeks because their phpile throws a key exchange error cinci zoo sniper fucked around with this message at 14:25 on Aug 1, 2018 |
|
# ? Aug 1, 2018 06:27 |
|
MALE SHOEGAZE posted:i've tried twice to make my inconsistent type param and variable lettering more consistent and each attempt has covered my project in slurs and MAGAs perfect description of js with proptypes
|
# ? Aug 1, 2018 14:08 |
|
floatman posted:...hell... My current project (JSON web-api + async messaging + rules engine + sql db) has ~100 unit tests, about the same number of 'integration' tests although these are more tests that external APIs and interfaces haven't changed or broken, but then ~4000 specflow end-to-end tests with about as close to 100% coverage as realistically possible, with all the happy paths, unhappy paths, edge cases, boundary conditions etc we can think of. Writing them takes longer than the code they're testing, they take about 20 minutes to run, and there's a fair amount of duplication in setup between them, but they're literal walkthroughs of exactly how external systems talk to the API both in how they set up db state, do what's being tested and assert. What's also nice is you can generally do massive refactorings without having to update any tests, and also prove that your API hasn't changed - or at least know what has changed if it's necessary. It's the first time I've seen specflow/cucumber style tests genuinely work as both tests and reasonable documentation. It's all fairly standard stuff, but works amazingly well. I guess the only controversial bit is the lack of unit test coverage (Thoughtworkers hate us)
|
# ? Aug 1, 2018 14:10 |
|
floatman posted:I have tests for a codebase with no abstractions, no dependency injections. Imagine MVC, but no models so controllers and views are directly touching database tables. why you should define an xsd schema for your xml documents.txt.doc.zip.exe
|
# ? Aug 1, 2018 15:26 |
|
ctps: blocking code: code:
code:
gonadic io fucked around with this message at 17:26 on Aug 1, 2018 |
# ? Aug 1, 2018 16:52 |
|
CRIP EATIN BREAD posted:why you should define an xsd schema for your xml documents.txt.doc.zip.exe That has almost nothing to do with why this is horrible.
|
# ? Aug 1, 2018 17:11 |
|
also terrible programmer question: i then want to make changes to that file that don't get copied to git - only the initial state should ever be committed so i made the file, committed it in, added to gitignore, committed that. no problem so far. but now my changes to the file are still shown in git diff and presumably will be committed if i do commit -am. is there a better solution? stack overflow told me to use `git update-index --assume-unchanged` which worked great gonadic io fucked around with this message at 17:21 on Aug 1, 2018 |
# ? Aug 1, 2018 17:13 |
|
Finster Dexter posted:That has almost nothing to do with why this is horrible. IDK what you're talking about, a good test is one that passes when I run it and makes the code coverage metric go up.
|
# ? Aug 1, 2018 17:36 |
|
A good test is any test you can walk away from.
|
# ? Aug 1, 2018 17:38 |
|
|
# ? Apr 24, 2024 03:29 |
|
gonadic io posted:ctps: you're on some kind of m4f, right? ~100mhz? you can approximate how many instructions before you'd have to preempt a task if you just want to get close
|
# ? Aug 1, 2018 17:55 |