Datasets:

showvikdbz

/

code-reviews

like 0

are the best numbers. This was removed, already, and I'm not sure why it wasn't updated. Edit: The currentmode shit is magic, yes. The if statement right above it, has been removed.

it was used by the unit test but i have just realized i was being a giant idiot and refactored it away

Oh holy shit. Those were faucets. Wow. TIL. I thought this entire time they were just T's for some reason. That's fucked up

move it just above self slot to tid to make it clear how about set the default self slot some abnormal self slot to tid self point self pressure self syn time none

from the root directory android build top i get the following make insertkeys py make no rule to make target insertkeys py stop is it just me maybe try using something like include clear vars local module insertkeys py local src files insertkeys py local module class executables local is host module true local module tags optional include build prebuilt

i think that it is better to remove description from fields on l

Sorry, I keep putting this one off by one more day and it's become a ridiculous amount of time :(

whats the difference between hosts review o o and hosts review o o git couldn t this break down into hosts git and hosts git

hey invalid volume is still not the only exception that we can get here so it is be good to catch the rest that can be raised by cinder client these are volumenotfound and snapshotnotfound

useless unused

no clue would take some code archaeology but even then i suspect the reason s to be dubious

It's weird but some RAP files are 16 bytes in size and others exactly 23, no idea why it's like that and if there are more versions for its size.

wait.. what? That seems very strange. why would FindSymbols ever care about this? This feels like something a feature+file-changer needs to care about. Having this baked into this core symbolic service just seems so wacky to me.

It can screw up the seed. IMO best way to handle it is to have two RNG's one strictly for dungeon generation and another for the rest that can be called without worry.

Hahaha \U0001f595 fuck you tickcomp

there is an open bug against this garbage being included in the token remove

are these two white spaces after testtools intentional

only allow deletion of empty groups please

@xwu The original text described someone else's work as "insane", so I was hoping that "ridiculous" was an improvement. Perhaps the best change here would be for someone to amend the comment to describe the actual underlying problem this comment is describing.

Darn tootin we can ! #RIP

These upper-bound total volume checks still allow you to add more shit to the ice cream past 500U.

security bug we can not allow log id kernel through this or the logd socket interface as klogd is an internal daemon that is part of logd revisit as this should be fixed and institutionalized in the liblog writer reader and within logd itself we will not fix it in the context of this cl

This code all sucks. I will fix up later today and will send out again.

No. no FILE_DIR crap.

Oh, damn. Could you leave a `TODO(python3)` comment with this explanation?

dumb question cannot we get the value defined in volumes yaml from hiera

breaking this out into a separate trailinggarbage test

but even for device policy wallpaper it still should be blurred in overview mode right

line whitespace plus four other trailing whitespace instances highlighted above seems to be causing the checkniceness failure

Read the test to your wife. If she cannot understand it- the test is not being named well.

I disagree, code that's 'for the future, not in use' should not be added to the codebase. It adds extra WTFs when human-parsing the code.

i strongly object against this instead you should use sqlalchemy introspection like this from sqlalchemy import inspection pkg inspect inspection inspect pkg foreign keys pkg inspect relationships

That looks so freaky, never seen that before

`it.is_disgusting_for( *this )` (a leftover from the previous PR)

what the hell are you doing ignore = (currentamount >= 1)

should be a volumedriverexception rather than cinderexception

lol sorry stan this is idiot ic not sure what i was smoking yesterday but you can take it out or leave it

remove the white space

Im getting the nightstick feeling from the rest of this, and pocket batons are shitty. No.

you should f fname instead

here admin state up false is it

<details> <summary>This is my fault, whoops</summary> This is real wacky.  </details>

nitpick keyston e admin

trailing blank line would be nice to eliminate that

damn git not refreshing, pardon the duplicate

pls docstring

Yeah, sucks. I was always hoping that [`process.setFdLimit(maxDescriptors)`](https://github.com/electron/electron/blob/master/docs/api/process.md#processsetfdlimitmaxdescriptors-macos-linux) could be used to set it higher, but it will never be higher than the system limit it seems.

allowedaddresspairs should be taken into account

suggest remove extra parentheses

there s no need for conditional import here subprocess should be monkey patched by eventlet at this point

small nit please remove this white space

do not do this you spawned the processes which means you have handles to the processes kill them directly

i have forget the trash comment

@blesh this also fixes the wacky TVJS (appleTV) bug i discovered the other day :+1: I don't believe we're dependency-injecting Observables anywhere in NG2 (yet) but I'm all for @trxcllnt's proposal.

I did, sounds good for me, but you know, volume is fucky wucky...

this might be a stupid question since i am not very familiar with how ipmi interoperates with ceilometer but is not resource id supposed to be id of the resource that the sample is about not the id of the sensor e g should not resource id here be simply node uuid just like cpu meter s resource id is the id of the vm

please kill the newline

i see you moved the datastore code into esx i guess i had it backwards

oops no i meant to leave everything even though it is not obviously useful although i am really tempted to kill xiafs super magic and i suspect that there are other obsolete ones here

extra space need to be removed

remove these white space

what linter are you using you should be using cros lint

why are you wrapping ret val

when we bump the min version of olso vmware i guess

You can indeed use your private keys of bitcoin to digitally sign messages. If You don't understand the basics of asymetric keys used to sign/verify transactions, messages or any text, You should first read more books about pgp, bitcoin and asymmetric encryption. I really don't like such noob proposals, souinds like CSW crap lol. #satoshin https://en.bitcoin.it/wiki/Message_signing

ha ha sorry english is not my mother tongue i am doing my best though

I think this error should still be printed to the console at least, otherwise you get debugging hell.

i think resourcewithprops should be there instead of genericresource

use adata ncount instead

Oh man, I feel so clumsy. So the strings are "???" and this pretty much told me that I must have forgotten to update the language files. My bad, I'm sorry for that terrible mistake I did :D I think this can get closed now^^

christ why were these even so secure, wtf were you thinking pappers

existing code that leverages this doesn t but looking at the script in question i think it is because i am an idiot and i should just do that

silly comment but first line and only one line needs to be a summary

i think you want printf printf s printf

this empty faggot

add a fucking pry proc to doors and call it from armblade and here, come on

It's a spaces vs tabs problem. Slowly swapping to tabs from spaces but can't just auto-format everything cause other stuff gets screwed up. So in short, yes.

this might be cleaner as a lambda preexec fn lambda subprocess setup preexec fn oh but silly pep will whinge at you about using lambda for their purpose we should kill that rule globally it is harmful

Comments look better with C++.

Ok, seems to be some 3rd party script on the site that was doing some wacky stuff the window history.

again i will change fontsettings api in another cl because it is backed by a what the fuck vector it is exploding the type by using size t but it really should be using what the fuck size t

you do not use expected attrs so it should be removed

I am so fucking stupid

> variables in your map that's just disgusting

@boegel might be. I have never tried. And anyway, I find ridiculous a 64 character limit in 2015...

no our git history is too polluted by meaningless commits

Whoops. My bad. Removed.

this line is useless even after we change credential to params because the super call above has done this

Argh, you're right. This sucks.

this method is useless you can move the code into declare topic consumer

> sad rip :( do you know why? No, but if I had to guess either the Tune testing is doing something wacky that leaves the shared cluster in a weird state, or the module scoped fixture is doing something wacky

This is a ridiculous situation. Surely the prerequisite SDK should be release prior to pushing the packages to nuget? We faced the same issue with the official release of 2.1 where the full SDK release was a day or so behind.

well kind of we will kill the renderer is the fuzzer an ipc fuzzer where we get garbage values or is this actually something we have seen if the latter then i we should figure out how that happens

Notable stupid shit found in blob_act() Setting density to 0, really.

consider checking that in dataavail at this point i e there is no trailing garbage

should this be vif type pvm ovs

oh yeah i refactored rewrote this a bunch of times and did not notice afterwards that it could be collapsed

pathetic my bad

This one is definitely cheating :eyes:

oh hell, that looks like it, testing now.