text
stringlengths
1
5.2k
labels
listlengths
1
1
if there was a problem deploying should self destroy be called
[ 0 ]
have you tested the shit out of all this
[ 1 ]
Fixed, turns out I suck at maths
[ 1 ]
no point in one yet we can add one to the patch that seals it all but this one is a drop in the bucket
[ 0 ]
useless
[ 0 ]
since you are not passing in anything to trace wsgi or doing any conditionals in it i think you can get rid of outer and instead use trace wsgi f
[ 0 ]
something about this pseudocode may be a stupid guess class rollingupdate def init self self last update time update time self templates templates self current batch number current batch number self batch count batch count def handle update generate needed templates ru rollingupdate update time templates current batch number batch count return ru def check update complete self rol upd if time now rol upd last update time self properties self pause time and ru current batch namber self batch count self update with template ru templates batch count ru batch count ru last update time time now return false return true
[ 0 ]
sounds good to me let me save one of those thx
[ 0 ]
should probably be called createentry instead of getentry then
[ 0 ]
this seems to do nothing and should be removed
[ 0 ]
i think we should change self health check into self check agents health
[ 0 ]
users should be possessive so users
[ 0 ]
for create fools me as if it was a wrong syntax for a for statement can we rename this variable as bcreate or something more meaningful
[ 0 ]
scratch that i was being stupid
[ 0 ]
commented code should be removed
[ 0 ]
This name sucks, as it is usually an integer.
[ 1 ]
The solution that works for me is ridiculous but it does work (Mac OS): ``` Disable laptop Wifi Turn off emulator Do a cold boot start of the emulator Enable laptop wifi Empty the Expo app cache yarn start expo:clean ```
[ 1 ]
this will be called for every source frame we might need to worry about sqrt but i would need to profile i will try comparing performance to versions that stub out sqrt it s not much of an issue on my desktop where the total cost to record the latency derived metrics is us it s us on my pixel though that includes re calculating a sqrt from n frames ago to subtract from the windowedanalyzer s accumulator so there is sqrts total per source frame metrics sqrts all the sqrts currently use double precision but i am pretty sure single precision would be good enough in general after getting the basics in place i would like to switch the double precision math over to single precision where we can if we really need to we could use a sqrt approximation as long as the approximation is monotonic it should be good at tracking relative performance deltas even if the absolute value might be off a bit if we really really need to we could also remove smr rms only needs to call sqrt on a reporting event much less often and not when a sample is added
[ 0 ]
>implying fuck ok
[ 1 ]
A also cannot see a relation of datetime tests and the changes :) Must be a wacky test that fails on April 6th or sth
[ 1 ]
Original style is usually kept for such things. And enum class will probably just become a pain in the ass there, not improving anything.
[ 1 ]
RIP AND TEAR YOUR GUTS!
[ 1 ]
no this does not break recents this is just a bouncer activity
[ 0 ]
let s get rid of ovs here
[ 0 ]
rubbish, subprocess us giving us back a 0 whenever a script is called, this will need a little more digging
[ 1 ]
Very well, if we're okay only having partial support for shadow DOM then we can merge this \u2014 thanks. Very annoying that the existence of shadow DOM forces us to jump through these ridiculous hoops in the first place!
[ 1 ]
done filed
[ 0 ]
remove the network id from the network ports list
[ 0 ]
with this change this todo is redundant and therefore should be removed
[ 0 ]
everywhere in this file you have examples on how to do it right, and you still fuck it up
[ 1 ]
@vbcodec I want it just as much as you do, but there is lots of new stuff in 2.0, so it wouldn't be "ridiculous" \u2013 maybe just disappointing.
[ 1 ]
Damn. Now the CI is failing on this file, because probably depending on the compiler `<tuple>` still gets included through an STL include chain
[ 1 ]
damn is it hackweek already
[ 1 ]
noqa should be removed
[ 0 ]
self group configuration self launch configuration
[ 0 ]
this must be lower cased otherwise the seendomains contains check will not catch case insensitive duplicates
[ 0 ]
this also seems useless
[ 0 ]
this looks like a constant and we prefer uppercase for constants
[ 0 ]
another white space only line two more below
[ 0 ]
I'll rerun your build <B>Edit: </B>Definitely not a build fuckup, it happened again
[ 1 ]
We should have the checksums in the release JSON files now shouldn't we? Or we can use a convention of <filename>.sha256 or whatever to try to see if it exists when download files? Hard-coding is a bit annoying/rubbish. Anyway, conversation for another issue/PR.
[ 1 ]
i think there can be other options explored this is obviously the easier one but the one that will yield the least amount of result at least in the short term what about spinning off api db and go the bold way spoiler alert crazy guy talking what if we change the architecture completely and introduce a neutron api server we introduce neutron conductor perhaps a scheduler and have the rest of the server ie the plugin be it is own worker s just like nova compute is i guess we could do this as a follow up step so do not mind the crazy guy who makes a fool of himself
[ 0 ]
should be mock clients return value get only instances return value severs list
[ 0 ]
This is if for some reason it's horribly fucked up and has stopped processing, meaning you can use a multitool to repair it.
[ 1 ]
Sometimes open source community can be ridiculous.
[ 1 ]
It would make sense if you didn't provide a class at all, but to provide a rubbish class makes no sense to me at all.
[ 1 ]
ah how about using const bool region dump argc if region dump else area size screen size
[ 0 ]
dumb question could there be a case when the destination is volume and the source is blank not sure i really understand the bugger picture here so please for give me
[ 0 ]
I don't think logging is appropriate here because the exception will do most of the "oh crap".
[ 1 ]
@Dexesttp some of them are because of C++'s nonsense about "templated stuff must be visible at callsite". the ASN1/DER parser...well, I actually have no idea.
[ 1 ]
hardcoded urls should be removed
[ 0 ]
Incidentally this is hilarious if you translate it sevtug is literally bullshitting the invoker
[ 1 ]
the new is here but i cannot see delete anywhere anyway instead of fixing this you could try adding addstatuslistener uno metricunit to the controller that way you should get the sid attr metric updates into statechanged too and then kill metriclistener
[ 0 ]
x role s
[ 0 ]
again, use a monotonic clock that doesn't do weird things when the system time jumps (because of NTP, daylight saving time, some idiot changing the time, ...)
[ 1 ]
shiiiiiiiiiiiiiiiiiit
[ 1 ]
Yeah uhh the main issue with this software is that it was made by a total faggot.I don't think it's fixable.pls remove repoty.
[ 1 ]
typo setcon s tructedintesting
[ 0 ]
... the hell. Fixed.
[ 1 ]
could we not do these as get trusts trustor user id myuserid get trusts trustee user id myuserid
[ 0 ]
That's retarded. Brilliant, Rails, the pundit of less is more, now requires an if statement around a field because Rails is too retarded to pluralize the word cafe. How about you change the name of the function to pluralize_some_stuff, it'd define the function a lot better.
[ 1 ]
you can set openstack image registry auth insecure true then let insecure node openstack image registry auth insecure
[ 0 ]
why should it, capitalising names like that fucks with BYOND last I heard. For example, doing Water Tank over water tank will make examine do "That's Water Tank" instead of "That's a water tank"
[ 1 ]
none of these are accesses by the gps default implementation shim layer and hence should be caused by the legacy vendor hal implementation wouldn t these belong here in that case
[ 0 ]
i guess pep hacking is checking for the trailing period thought we killed that
[ 0 ]
This latest temper tantrum is the last straw, I've given you dozens of chances to improve your shitty attitude, and it just hasn't happened, I'm not going to work with you any more and you're no longer welcome in my project.
[ 1 ]
*ViBE:* This is not going anywhere and I reported this more than three months ago. What should I do to get more attention? Reporting feels pretty nonsense.
[ 1 ]
Nope I'll do this after your PR gets merged Also outside of scope get fuk'd
[ 1 ]
so i was wondering why we would want to do this at all when it is most likely that those are already set on an instance and if not they can be lazy loaded on access the problem comes when we are migrating an instance because we need the new pci requests we use a horrible hack to get the newer ones from the db we should really be adding pci requests to the migrationcontext object and consuming them from there as is the case with numa topology
[ 0 ]
Darn, I thought we had something but I couldn't find it (and I even looked through the grouping section). Just goes to show how hard it is to write detailed documentation *and* still be able to find things in it...
[ 1 ]
this should be boot id self action suspend
[ 0 ]
i think all these transformations should be done in objects layer could you please explain why we have hardcoded mac unix here what if we are dealing with infiniband hwaddr
[ 0 ]
This is just ridiculous
[ 1 ]
could we extract the interface and not have inner interfaces it makes the code using them verbose and obnoxious to read for no real benefit
[ 0 ]
useless commit summary the one line summary should indicate what the commit is about and when looking at a log of changes if they all say fix issue n you will have no idea of what has been going on
[ 0 ]
this about a eoghan glynn question here c gnocchi carbonara py personnally i m not sure that gnocchi should handle this case
[ 0 ]
insta fails because this defaults to var lib mysql instead this should be hardcoded to data db much like the redis implementation hardcoded itself see l in short change this to mount point system mongo base dir and set mongo base dir to data db in system py sometime in the near future a patch should address these crazy mount point hacks
[ 0 ]
you are jumping to the destroy workqueue on a non existent wq
[ 0 ]
@speezepearson this is the joyful PR I wanted to share with you, not the #4026 rubbish :)
[ 1 ]
Right, it does seem that I am talking nonsense! :-)
[ 1 ]
lol. wtf are we gonna do about this stupid crap?
[ 1 ]
i wonder if we should also kill the v upload since it is broken anyway imho it should instead be replaced with a go version instead
[ 0 ]
maybe just put the rm just above the ifeq use ninja true
[ 0 ]
Oh you gotta be fucking kidding me. I\u2019ll just seperate the fucker, cause UI succumb is intentional and whisper succumb isn\u2019t
[ 1 ]
i think that delete orphan will be useless since the fk cannot be made null anyways so there is not a case where secret user metadata instance can be an orphan
[ 0 ]
tasks graph tasks graph
[ 0 ]
A butch lesbian is mistaken for a man at an audition. She takes off her hat to reveal pink hair, and the other characters react with surprise.
[ 1 ]
Varediting badmins Also modularity + keeps down the bullshit in exchange_parts()
[ 1 ]
you can not do that in puppet afd file lma alarms regsubst name but yes i see the idea
[ 0 ]
in each case we can choose an appropriate preposition in on or with i mean devstack in dummy or multihost in dummy are stupid
[ 0 ]
bindonce internal abstractpromise execute std move promise
[ 0 ]
let s use implements for tracking purposes in launchpad we may create another bp for the other phases if needed
[ 0 ]
d oh fat fingers fixed
[ 0 ]
Ah, sorry, wasn't showing up in here. Also, WTF? did they really need twitch to be twitches violently and twitches to just be twitches???
[ 1 ]
OH GOD WHY fucking hell magic math make it a blood catalyzed reaction or something jesus
[ 1 ]
nit kill this comment
[ 0 ]
I like how this completely shits all over the definition for `InheritComponent`. The third argument is mentioned nowhere.
[ 1 ]
as above we should be able to eliminate d obj
[ 0 ]
remove daemon here
[ 0 ]
you know I suck at explaining here https://github.com/vercel/next.js/issues/24775 https://github.com/vercel/next.js/issues/34776 he is the owner of the project and knows better I'm just a user, also: https://github.com/walking-octopus/translate-ut/issues/6
[ 1 ]