Everytime I run grunt after this commit `/js/components.js` shows as modified

```
Signal-Desktop$ git checkout ec6948bc32ab78f414f538a148fcacacfd657ef8
...
HEAD is now at ec6948b... Update twemoji to v2.0.5

Signal-Desktop$ git status
HEAD detached at ec6948b
nothing to commit, working directory clean

Signal-Desktop$ grunt
Running "concat:components" (concat) task
...
Done, without errors.

Signal-Desktop$ git status --short
 M js/components.js

Signal-Desktop$ git diff
diff --git a/js/components.js b/js/components.js
index e1ff1b6..5307be4 100644
--- a/js/components.js
+++ b/js/components.js
@@ -28166,7 +28166,7 @@ var twemoji = (function (
             '"'
           );
           attrib = options.attributes(icon, variant);
-          for (attrname in attrib) {
+          for (attrname in attrib) {█
             if (
               attrib.hasOwnProperty(attrname) &&
               // don't allow any handlers to be set + don't allow overrides

```


oops, sorry, I didn't know that also external dependencies should be placed here.....saved!


Spaces:
while (len(hr) != 0)


'append to list' script


We never wrap services with `'`


Wow, this is great!


TeamCity LabKey :: 16.1 Release :: Community :: CDS postgres 9.5 [Build 52](https://teamcity.labkey.org/viewLog.html?buildId=310184&buildTypeId=LabKey_161Release_Community_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 8 (1 new), passed: 44 Build time: 01:25:50
### Failed tests
```
org.labkey.test.tests.cds.CDSVisualizationTest.verifyTimeAxisBasic: <no details avaliable>

org.labkey.test.Runner: org.labkey.test.tests.cds.CDSVisualizationTest: <no details avaliable>

org.labkey.test.tests.cds.CDSVisualizationTest.verifyPlotToolTips: <no details avaliable>

org.labkey.test.tests.cds.CDSVisualizationTest.verifyTimeAxisWithMultipleSchedules: <no details avaliable>

org.labkey.test.tests.cds.CDSVisualizationTest.verifySubjectCountsWithFiltersAdvancedOptions: <no details avaliable>

org.labkey.test.tests.cds.CDSVisualizationTest.verifyGutterPlotBrushing: <no details avaliable>

org.labkey.test.tests.cds.CDSTest.testLearnAboutStudyProducts: <no details avaliable>

org.labkey.test.tests.cds.CDSTest.clickOnLearnAboutStudyProductsItem: <no details avaliable>

```


the source is located at 'components/elasticsearch/config/append.groovy'
shouldn't it be 'components/elasticsearch/config/scripts/append.groovy' ?


:sunglasses:


From what I can tell it looks right. The additional fields are there, how they display got reordered. All good.


This comment let me to search for a chrome extensions named `typo.js` which I didn't find. Was that the intended outcome?


Consider trying to avoid the long "hr=.." line twice.
You'd probably need to use "len(hr)!=0 or i == 0" in the while.


@Underground78 I pushed my things, could you please take care about tfex? I'm not sure what to do so my typo fix is ok with it.


Right, okay I see. I could attempt that if you'd like, or you would you
rather do it yourself?
On Mar 13, 2016 5:18 PM, "Martin Simon" <notifications@github.com> wrote:

> Because I acted quicker than I thought [image: :sweat_smile:]
> If possible id like to implement the size values in dict(), something like:
>
> dict(format=Gigabyte):
>
> I'll try and come up with something later this week.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mrsmn/hazelnut/commit/514213415020ec0c9b56fc6955c9e76561266e34#commitcomment-16669736>
> .
>


No need for double new line


Hi, why do you have edit the max line length for the header?


As this getter returns the number of skipped steps in a suite (not boolean flag), wouldn't it be better to keep as 'getSkipped'?


You can have a go at it if you want. Sorry for reverting this btw: it's not that I don't like what you
did, I just think a more elegant solution would be more suitable.

Hope I didn't offend you. (I should probably have voiced my concerns in the PR instead of merging
and reverting.) Sorry again.


It's planned I have to manually update for my commits anyway.


And your try pass service without ' in symfony 2.8


Haha, you did not offend me at all, I just thought you weren't aware of the
revert feature that Github provides. No hard feelings, really. I think the
project is great and I agree with your decision. :)
On Mar 13, 2016 5:28 PM, "Martin Simon" <notifications@github.com> wrote:

> You can have a go at it if you want. Sorry for reverting this btw: it's
> not that I don't like what you
> did, I just think a more elegant solution would be more suitable.
>
> Hope I didn't offend you. (I should probably have voiced my concerns in
> the PR instead of merging
> and reverting.) Sorry again.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mrsmn/hazelnut/commit/514213415020ec0c9b56fc6955c9e76561266e34#commitcomment-16669785>
> .
>


bad


Hmm, there is no binary on the release page.


By convention, we put a space before and after the '!'. Read all about codestyle here:
https://www.massivecraft.com/tech-standards#indent-style


Done


There is now - it gets uploaded by Travis, so you usually have to wait a few minutes after the tag gets pushed to GitHub.


I didn't bring it up as a bug report because I was not sure if it would be recieved as such (experience has taught me to gather support _before_ addressing something as potentially a bug if ever I have hope that it will be resolved).


[BreadCrumb Control.zip](https://github.com/PhilKers/BreadCrumbControl/files/171228/BreadCrumb.Control.zip)


Świat ma swoje UUID AFAIK :D


Great comedin :D i add this


What is the difference of the bookmark toolbutton compared to the normal one in sugar3?


Generally speaking, we put each fix into its own branch. Read more about branching here :)
https://www.massivecraft.com/tech-git-usage#branching


wondering what this is for specifically?  seems like this would make all callbacks no longer work. i would think just checking if there is existing sign in the way like you are should fix this issue?


contrib/codeanalysis/runcppcheck.sh: line 9: ../cppcheck-1.66/cppcheck: No such file or directory


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 19013](https://teamcity.mesosphere.io/viewLog.html?buildId=163263&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:10


Keep up the good work! :+1:  I am sure this sokution will work, so we want it clean and usable ^^


1972 ?! how epic


Thanks!


Zobacz sobie klasę [MessageFormat](https://docs.oracle.com/javase/7/docs/api/java/text/MessageFormat.html).

[Tu](https://github.com/ShootGame/Commons/blob/master/src/main/java/pl/shg/commons/translations/LangMessage.java#L32) masz przykład.


The way I pictured it was electrical bot is what CoderBot was about before:
dunno if this will work, so we're testing it out here before putting it in
the competition code. The new IMUs, for example, would be tested and worked
with in CoderBot before copying it into this repository.

On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com> wrote:

> Well... kinda.
> The pros was that it IS all one working space and that nothing has to be
> switched over and we can work straight off the same code. It would be very
> simple to move a sensor bug from comp bot to electrical bot, or in the case
> of testing controls or motors we could test as well.
> Electrical bot isn't limited by what it can do, we just don't quite know
> what we'd use it for just yet. We may find ourselves testing new driver
> station controls or new adjustments to a subsystem. The con I guess it's
> that it's much larger and might possibly cause confusion. I tried to make
> it as explicit as I could with the naming of things (I should add comments
> to delineate when the robot works as electrical bot and as a functional
> bot).
> I feel like it's not a bad idea or trade to put it into one repo and
> project because moving a system to be debugged on electrical bot will
> probably be as simple as 5 lines of code now, and no switching or
> copy/paste is required. We can literally run the same code just down a
> different path of execution. That con is that we'll have that extra code
> that idles to look at in all bots.
> On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
>
> > I pictured electrical bot being a separate repository, as it will lack a
> > lot of code that's in here. All of the subsystems that include motors,
> all
> > of the buttons that control them, etc. won't exist there. Did Chris
> address
> > any of that?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
> >
>
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431>
> .
>


Ok, sounds good. :D


I don't see it [here](https://github.com/purescript/pursuit/releases/tag/v0.3.4)


@alexeagle I'm not sure which version of lib.d.ts we compile with. But the es6 version has top level definitions for this. https://github.com/Microsoft/TypeScript/blob/master/lib/lib.es6.d.ts#L18447


Looks good! using left and right to reduce loop times


develop (lefticus) - i386-Windows-10-VisualStudio-14: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-0.0%25-red.svg)


I think it's fine because if it came through this path, then no other path is reachable until the next iteration of the for-loop, where it will get set to whatever the next `data[i]` is. If anything, I'd say it should set to `null` anytime the buffer length is made 0, because in those cases there is no longer a "first" byte value in the buffer.


develop (lefticus) - Win64-Windows-10-VisualStudio-14: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-0.0%25-red.svg)


good deal, thanks!


Just so I can create the same Contact twice (one to encode->decode and one to compare the result to) without having to duplicate code.


develop (lefticus) - Win64-Windows-10-VisualStudio-14-Debug: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-0.0%25-red.svg)


That is weird; I do. Maybe wait a few more minutes?


`ItemStack` nie jest `Serializable`? :O


I don't know what I'd use as the key for hash table. I mean it'd be obvious for 'name' and 'Address' but if a Contact has multiple phone numbers or email address, what would there keys be. I could just add a private member like "private ContactTriplet name" to ContactData if you wanted.


Why exactly are you using this reference?


Thanks for the excellent 'sample-beam.lua' which greatly improves sampling results with char-rnn.

I've also been testing this word level version: https://github.com/larspars/word-rnn

Is it possible to modify 'sample-beam.lua' to work properly at the word level?

Current sampling output is concatenated:

Thequickbrownfoxjumpedoverthelazydog.

Instead of

The quick brown fox jumped over the lazy dog.

I'm new to lua/torch and would appreciate any suggestions to modify the code.

Cheers,


I dont think you need the "int" in the parameters,
also, you might want to get our images back there too


cheers!


Ah, interesting. I didn't know we did that in a dropdown on where the cursor is. That's the bit I am implementing for atom right now and I was planning to do it like fuzzy file finding but I think I prefer the contextual approach--especially if we can move the cursor while importing multiple things that need to be resolved. I think for this to work, import-js should return line and column numbers for each word it needs to resolve, which it will have from parsing the file to find undefined variables.


Feel free to create an issue on the OctoberCMS repo and we can work through
it.

On Sunday, 13 March 2016, kdon80 <notifications@github.com> wrote:

> I think your OctoberCMS is on 5.1 right now, isn't it? I have the latest
> code there, but I can't seem to orderBy in union for the life of me.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/laravel/framework/commit/65e45d6f03de3c8403d606bbbefe49652909444c#commitcomment-16665997>
> .
>


A fix for that.
[fix-objquota-userspace-many.txt](https://github.com/jxiong/zfs/files/171236/fix-objquota-userspace-many.txt)


Illuminatie


sent a link to a sample in PM on slack


@klq - I originally had python 2 installed but somewhat accidentally updated to python 3 when I started the prework. It was a challenge to learn the new features of python 3 since I'd started learning on 2 - but I think I got a grasp of the language better faster because of this.


yeeeeeuhhh


Allowing multiple runs in a hyperlink may be very useful in some special cases. We have  documents with links containing some special terms in italic, it looks like [[a link with a _term_] ](url).  @_@

What's more, as shown in the XML schema, a hyperlink can have 0, 1 or many runs.

What changes if a hyperlink has more than one runs rather than only on run? I thought the only differnce is that we have `hyperlink.runs` as lists intead of `hyperlink.run` as a single run object.


please put these commands into a new command controller class named `InstallToolCommandController`


Test commit comment webhook.


I meant I change the X to appear as green and not grren :+1:


There's not a lot of value in the history in this case so I'd just move it and make one commit but do as you like.


Please use dependency injection instead of on the fly creation of the class here


why do you use the shutup operator here? Please remove it


some formatting, especially in the error case would be nice


This is not new syntax. We have always supported definitions with infix syntax, and missing the case of comparison operators was a bug due to their slightly different parsing. Such a trivial matter. Honestly.


alle from above also applies here.


This commit updates UI when backend was changed.


thanks


You may have noticed that your content doesn't actually appear to slide down -- that's because jQuery/JavaScript are incredibly fussy when it comes to how you reference function names: they have to be typed EXACTLY the way they were defined by jQuery.  In this case, you have `slidedown` while it should be `slideDown` (note the capitalized D here); see if that helps !


Klasa `FileUtils` z Commons IO to już ma. ;)


You're using the right function here but you're missing parentheses after `hide`; the entire line should read `$(".readmore").hide();`  [Without parentheses, JavaScript doesn't know to execute the `hide` function.]


Same as above, add parentheses after `show` to execute the function.


Similar to the issue with `slidedown`, this one isn't firing because the U should be capitalized: `slideUp()`


Need parentheses after `show`


Need parentheses after `hide`


Ah, not exactly. I was basing this on the typo.js source, which does some checking for whether it's part of a chrome extension, but on closer inspection, typo was only ever intended to be a component of other extensions, and I don't think the notebook js can get access to chrome extensions. I'll edit this.


Need to capitalize the D so it reads `slideDown()`


The first case really tests if libxenctrl exports xc_interface_open. Translating that into "libxenctrl not found" only obfuscates the underlying issue.


I don't think I've ever seen docs, examples, tests, or code in packages that used infix definition syntax. That's why this surprised me.


Sorry, I missed that.


Redondant `app` folder with `src`: missed during rebase? :smile:


#java specific


@IgorMaksymov Extract this number to constant


#netbeans ignore personal stuff
nbproject/

## generic files to ignore
*~
*.lock
*.DS_Store
*.swp
*.out


That's not how Math.random() works.


How is MathRandom easier than Math.random? Also, that semicolon shouldn't be there. Additionally, your function will always return undefined.


:rage4: yeah, nice catch! that rebase sucked.


actualizado archivo .ignore


Looking at drawThickLine, I don't think this dirty rect is big enough.


This name needs further thought. ManagedSurface::isManaged doesn't make much sense.


This is part of logic I copied from the PostGIS provider which actually used i < 5 to allow the user to retry. It didn't make sense to allow the retry given our logic which is substantially different.  I need to see if there is a way to make this useful or take it out. This was part of the authentication logic. (which doesn't seem to be documented anywhere from a user perspective.


You're right, we do this in a lot of places. That doesn't mean that we can't improve things though ;)
Some libraries have a pkgconfig file, but it seems libxenctrl is not one of then.

Adding a header check would be a good idea indeed.


This was an unforeseen find. We found that suddenly some of our images where very big, and wondering why I got very big (file size) PNG images while I was sure they were JPG before...

I think such a change should not have been done in a release branch.


I don't understand this comment.


Typo: its


I just tried this, but it doesn't achieve what I want. Basically I need to display a proper image (the one defined in the template), not a placeholder. The template doesn't look nice with placeholder and the user needs a lot more imagination to build something like that...


You mean check if id is null? If the list is empty, the code just won't find anything to do.


Why split the TerminalPosition and then re-create a new TerminalPosition? Isn't a TP immutable, anyway?
Is this a relict from back when we had to "convert" it to a TerminalSize?


Since I'm suing real images and not placeholders, I want the image to be visible, not the text and it's pretty obvious the user can change the images there, maybe not obvious they can just drag-n-drop, but that's not a problem.


It's already released.


To test this I run:
$ cd /casey/src
$ ./piratehook 1.11.2
$ ./freebsd-init
$ sudo nix-daemon &
$ sudo nix-channel --add http://nixos.org/channels/nixpkgs-unstable
$ sudo nix-channel --update
error: cannot kill processes for uid ‘1003’: Operation not permitted
error: cannot kill processes for uid ‘1003’: failed with exit code 1
cannot unpack the channels at /usr/local/bin/nix-channel line 169.

I started working backwards from the Darwin/APPLE stuff (apple-hacks.patch has the first part of this). But I'm still stuck on this kill/nix-daemon stuff.

wierdness, the nix-daemon doesn't fork, which the docs appear to suggest it should. that may be a pointer too.


These low values are due to too fast time control!
@IIvec Piece values have already been tuned by Joona long ago. And since so many other eval parameters heavily depend on these, it's almost impossible to tune them separately. Unfortunately.
@lantonov Good luck, anyways!


Вот. Прости, но следить за чистотой кода надо всегда и везде, а не только в геррите


This is code I copied from mssql. No idea what this is supposed to do. Is QVariant::String equivalent to the constant 10? I haven't actually tested with date and time values.

I actually see a bigger problem with the logic in line 760 because this mechanism to test for an identity column doesn't work on DB2.


Who can say where the road goes.


It was causing a call back on the next game command even though it wasn't the same one.


The second 242 isn't the correct issue (`haxelib install <file>.hxml` now checks hxml files recursively).


Cool, I didn't realise that, updated :)


Comment fixed in 1868856, thanks @schnippi !


WOAH! No, MaxValue is Integer.MAX_VALUE here! You had that right before.


I'm sorry, I don't follow.


Thanks, wow!


http://stackoverflow.com/questions/1527803/generating-random-numbers-in-javascript-in-a-specific-range

`Math.random()` will always return a random number from 0 to 1. It takes no parameters as far as I know.


The trip is available here, so recreateOptionsMenu should not fetch the trip again


@dualspiral Nope. It works fine. MaxValue is Integer.MAX_VALUE, but DefaultValue is not correct - it's set to 60 for a Diamond Sword, which is incorrect. Using the MaxValue makes it become a negative value for Item Damage, which then becomes 0, making it have no damage. :wink:


@bpowell I am attempting to make sure that the drink is deleted, get this error:
`
Failed tests:
  TestAvailableDrinkServiceTester.testDeleteAvailableDrinkById:60 expected null, but was:<[]>
`


take this out


This does not have to be indented; it is not defined within another block (blocks are defined when you have `{...}` braces, so for now only indent when you are inside of another function or an if/else statement).


Oh, I see, I was worried that it would give you a negative damage. I guess I was testing with wooden swords and I was poking around everything, and noticed that the max value was that.

Alright! Carry on!


you are totally right! I was not familiar with markdown at all when I answered this question - now it should be formatted readably :smiley:


Agree. Didn't see this is not boolean value


This is a test comment, made pre-pull-request 😭


Rather than target *all* `<p>` tags, try selecting the specific one that you want to slide down (hint: you do it in the line below except instead of using the `slideDown` method to reveal the content, you are using `show`).


What does the isomeric smiles string look like?


Yep - I saw the discussion of this in the prework channel. I will be setting up my upstream shortly!


Everything from lines 4-33 should be indented in one (incl their indented blocks as well); this is to reflect that all of these functions *belong* to the function declared on line 2 (`pageReady`).


@Makman2 yeah, it is. Why do you ask?

-----Original Message-----
From: "Mischa Krüger" <notifications@github.com>
Sent: 13-03-2016 21:45
To: "coala-analyzer/coala" <coala@noreply.github.com>
Cc: "AbdealiJK" <abdealikothari@gmail.com>
Subject: Re: [coala] ConsoleInteractionTest: Make test generic (2387f5d)

Is the link to the CI correct? :O (inside commit message)
—
Reply to this email directly or view it on GitHub.


Why a *blocking* queue, when all retrieving happens with ".poll()", thus nonblocking? (Not an issue, just wondering)


@sariths @chriswmackey,

I agree that THREE.js next to some d3.js is the right direction.

@theo-armour is the expert when it comes to THREE.js. I don't see anything that you won't be able to do with his help. Check some of his work here: http://jaanga.github.io/home/r4/index.html


This appears to break VC++ 9.0:
https://ci.appveyor.com/project/wxWidgets/wxwidgets/build/570/job/xl7xu5fg7xnqe4hv#L280


May I have a built copy of the latest code? I'd compile this myself (I usually do compile stuff myself) but I am unable to do so.

Pretty please?


Hi other girl lovers,


Comment regarding the commit message - removing `FileAttribs` does not make the union an anonymous union because it has a name, `fileattribs`, which is the instance name. If you were to remove that too, then then union would be anonymous. But in that case, there would be nothing for `is_union` to detect, because the union cannot be referred to in any way. Its members get added to the enclosing scope. An anonymous union is defined within `struct S3`, and I'm testing to make sure none of its members are being detected as unions.

The distinction is a bit pedantic, but important nonetheless. pyplusplus currently has a bug where it thinks a union without a tag name, like `fileattribs`, is anonymous, and creates invalid binding code. I think #41 will fix that bug, haven't had a chance to test it yet.


There is an unfortunate typo in the commit message of this commit.


111247952_Remove_QUUID-rebased (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2331 of 2397 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-97.25%25-yellow.svg)


TeamCity Emplea.do :: Build - Pull Requests [Build 25](http://137.116.74.213:8111/viewLog.html?buildId=84&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) is now running


TeamCity Emplea.do :: Build - Pull Requests [Build 25](http://137.116.74.213:8111/viewLog.html?buildId=84&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:03


- This line is useless as already in the base class
IndicatorRSI.cs#34 _periodSeconds = periodMinutes * 60;


The pattern is consistent though. This is just a check. A yellow result will count as a success.
However, for thorough tuning all piece values should be tuned simultaneously, and, yes, at longer time controls. Just don't have the real SPSA in Fishtest.


Most likely a merge/rebase gone wrong, thanks for handling this.


I'm not convinced this function properly clears/frees the existing state before copying over the new one. Particularly because it calls setPixels() (which does free) after resetting some of its fields.


u cant do that alot of ppl are storing things in it. find a fix for it or insert another mod first which people can transfer stuff into. but u cant just add something and remove it afterward


Remember to remove this when connecting to server


Typo: its


You so clever!! x3


Of what is `_owner` the owner exactly?


111247952_Remove_QUUID-rebased (lefticus) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg)


For new code we prefer 2 or 4 spaces, no tabs. Please have a look at https://collectd.org/wiki/index.php/Coding_style

Please remove this modeline. I'm aware there are existing files that have them, but we don't need to add more.
Different people prefer different setups for their vim. Adding a modeline forces your style on them.


At VLTC (500+15 ms) this was +10 elo in 10000 games.


stray comment.


You can't do that because this patch would not apply on all kernel versions. For example we already (Peter does) provide two versions for 3.19 and 4.1. Now about the deployment... that is actually a bug. The problem is with the sdcard class as kernel will compile fine. So we need a mechanism for this too (include the dtb based on PITFT22). Could you please add an issue in github, @toolmmy ? Me or Peter (or somebody else) will fix it.


TeamCity Emplea.do :: Build - Pull Requests [Build 26](http://137.116.74.213:8111/viewLog.html?buildId=85&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) is now running


TeamCity Emplea.do :: Build - Pull Requests [Build 27](http://137.116.74.213:8111/viewLog.html?buildId=86&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) is now running


TeamCity Emplea.do :: Build - Pull Requests [Build 26](http://137.116.74.213:8111/viewLog.html?buildId=85&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:03


TeamCity Emplea.do :: Build - Pull Requests [Build 27](http://137.116.74.213:8111/viewLog.html?buildId=86&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:03


Thanks. just learning this stuff


Wychodzę z założenia że taki config jest prostszy dla przyszłego usera :v:


ok i see now, yeah this is right, i misread which line this was on.  this pull request looks good to me.


Should this function clip the dirty rect to the bounds of this sub-surface before passing it along? (In the case that `this` is a sub-surface of another surface.)


After this commit, this branch no longer compiles with scalac, it complains with:
```
lazy values may not be abstract
```
@odersky : Do you know if there's a fundamental reason why scalac does not support abstract lazy vals? This could make it much harder to keep a codebase compatible with scala 2 and dotty.


This toolbutton changes it's color accordingly.

I got your point. I'll inherit the normal toolbutton into BookmarkToolButton and update the patch.
Sorry for the duplicacy. This patch was pushed before you told me about that.


I think domain here  can be a str (the docstring tell me :type domains: `str` or `unicode`), and doing domain.encode("ascii") implicitly try to convert domain to unicode (aka decode domain), raising a UnicodeDecodeError.
So then domain is a str, it raise  UnicodeDecodeError and then domain is unice it raise UnicodeEncodeError.
We probably should catch both:
```
except UnicodeDecodeError:
    assume domain is str
except UnicodeEncodeError:
   assume domain is unicode
```


hahah thanks :+1:


Docs should probably include key must not be NULL. On a NULL key, a crash will occur rather than returning `NID_undef`.


Thanks for doing this! However,
- As Price code is meant to be used extensively, this is performance critical.
Wouldnt the comparison be faster and more accurate in the case of sorting algorithms as follow ?
(we can assume the spread charged by the broker is the same for all quotes)

public static int comparison(Price p1, Price p2)
{
     return p1.Bid - p2.Bid;
}


Thanks for the clarification. I'm not using unions myself, so I was confused on how to describe the fact that there was no name. Rapidly reading some tutorials about unions misled me to think that this was called an anonymous union. The commit message is now "wrong" but I can't change that anymore.

I'll have a look at the other PRs in the next days. Thanks again.


No, it should be the new one:
http://inspirehep.net/info/hep/search-tips


I meant with using decimal instead of int as well:

public static decimal comparison(Price p1, Price p2)
{
return p1.Bid - p2.Bid;
}


contrib/codeanalysis/runcppcheck.sh: line 9: ../cppcheck-1.66/cppcheck: No such file or directory


Solves #21


Watch the quotes in the mod.json.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 19014](https://teamcity.mesosphere.io/viewLog.html?buildId=163338&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 254 Build time: 00:10:46


this is a mark down file


I'm actually not sure it's possible, although if it is, that'd be great.   The react native packager's `require` implementation is kind of heavy-handed...  As far as I can tell it just does a string match against the token `require`, and you have to pass a raw string into that function for the dependency to be picked up by the packager.

So, e.g. this won't work, since the packager can't know the value of `pkg` statically:

```javascript
var pkg = './foo/bar';
require(pkg);
```

Renaming or otherwise wrapping `require` also breaks the dependency resolver.  So does this, actually:

```javascript
var foo = "require('./does/not/exist')";
```

which is why I think it's basically a regex, since it doesn't notice that the require is inside a string literal...


Yup. Was an serach & replace error.
Fixed it


TeamCity Emplea.do :: Build - Pull Requests [Build 28](http://137.116.74.213:8111/viewLog.html?buildId=87&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) is now running


TeamCity Emplea.do :: Build - Pull Requests [Build 28](http://137.116.74.213:8111/viewLog.html?buildId=87&buildTypeId=EmpleaDo_DeploymentToQa&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:02


Do I see correctly that this function has no optimized code for the (presumably very common) situation where this is no scaling and/or no transparency?


Could you add a comment to the top of this class explaining its purpose?


When do you do it ? You need to do it after login or at least in the options.handshake function


Ah, I see, it's something that ReactNative does differently? Here I use a shim - https://github.com/NoRedInk/take-home/blob/master/src/Native/Telate.js#L41

then I can include JS files like this:

```
module Moment where

import Native.MomentJS
import Native.Moment

```

then I can use `require('moment')` in my Native implementation of the Moment stuff.


Index.html file


develop (lefticus) - i386-Windows-10-VisualStudio-14: OK (391 of 391 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


Inverted?


so flexy


Inside of dazed-sheep? At the end of `spawn.js`


Sweet! That works much better, thanks :)


The default `project.xml` uses 4 spaces, additionally which I find easier to read than the 2 spaces that was previously used, so I changed it to 4.


thanks


Just wandering through the current FNA diff... this will help with this TODO:

https://wiki.libsdl.org/CategoryClipboard


This broke compilation of code which already provides a specialization for `long`, such as:
https://github.com/alexrj/Slic3r/issues/3117#issuecomment-170150737

Also, this change is not mentioned in the Boost 1.60 release notes.


flexy ix fle x flex flex


Delete the "setToString" part in the anon inner class, it's already defined in the constructor


No niezle, ja mam tak samo, ale nie bede wysylal takiego samego


Looks good thanks for fixing!


leftoverHeight is not being erased?


Forgot to mention the offset caveat in the pod section. Plus, it is worth to mention that set_syslog_timezone accepts whatever DateTime::TimeZone constructor allows.


Yeah, the RN `require` isn't just a function, unfortunately.  I'm pretty sure the rationale is that the packager builds a dependency graph so that it knows what to bundle,  and it does so before the code is evaluated.  I assume that the since the packager is running in node, its execution environment is too different from the actual RN runtime environment for a dynamic `require` implementation to work.

It's kind of a drag, but I don't think it's a big priority for the RN team.


yay!


okay


This change breaks instances with multiple ENIs attached, as querying inst.get_attribute('sourceDestCheck') at the instance-level fails when there are multiple ENIs.


develop (lefticus) - Win64-Windows-10-VisualStudio-14: OK (391 of 391 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


Forgot to mention: fixed temporary green flames not reverting to normal fire


Instead of using `hide()` for all of these elements, you can also use `display: none` using CSS to hide the content on page load.


is it still initialised?


Perhaps add an intermediate version where you remove their recipes, add recipes to convert back into their main ingredient and add whatever mod you were intending to replace it with, coupled with a rename on the blocks to notify people of the change? I would make that commit myself, but a little busy on other projects ATM.


If you use unified backend from arrayfire, you can load the necessary backend at runtime. Is there any reason environment variables are being used?


I'm just thinking out loud, that might not be the best option. But two nested switches seem to be a bit overcomplicated. Other option include:
1) not doing anything
+ no work
+ code is already definitely not bad
- much nesting
2) converting to
if ()
else if ()
else if ()
else if ()
else ()
+ less nesting
- separate logic of the third outer case case is less clear
3) Converting only the inner switch to a map
+ less code
+ less nesting
- handling of the default case would differ from the rest of the code (or is it +?)
- non-uniform code: outer switch and inner map

That's up to you, I think it's fine to leave this fragment as is.


Rather than closing the `pageReady` function here, you should close it after line 70 so that all of your site's JavaScript executes only after the DOM is ready.


All this does is specialize coordinate_traits<> to allow "long" as a coordinate type. It seems like a clear bug not to.

If you hit this bug and worked around it, then you should have reported it  :-). I would suggest using "#if BOOST_VERSION < 106000" to enable your specialization only for earlier versions of Boost.

Unless every minor bug fix makes it into the release notes, I do not see why this one deserves a mention.


a7714e877945b4a8ff9b5c21332d42a9e2b1fd63 resolved


For lines 16-34 above, instead of adding a new click handler to each of these, you can just add `event.preventDefault()` within the click handlers that you are defining below.


Great use of nested selectors in jQuery!


I'm not sure what you are asking. I changed nothing in context with initialization.


Actually, these should be changed to use fnvlist_*().  There are tons of similar cases in this file, which I'll also address.  Perhaps with a following commit.


yeah, good idea!


ok, resolved


Nice!


Why use auto pointers ? I've always been told they had to be avoided at all costs. Did C++11 change any of that ?


The `config` parameter might not be the config from the MOS -- it normally comes from either the cache file (/etc/zfs/zpool.cache) or from `zpool import`'s rummaging around the labels.


Nice too


@plopresti, I'm not sure about your policies, but any existing codebase using `long` coordinates include an explicit specialization as per the Boost.Polygon docs:
http://www.boost.org/doc/libs/1_60_0/libs/polygon/doc/gtl_coordinate_concept.htm
So this is a minor change, but still breaks compilation so I think it deserves a mention in release notes. :-)
I introduced the preprocessor directive you suggested.


Sorry, sorry. I'm getting myself an idiot-proof text editor that doesn't do educated quotes at all, because I'm obviously never going to spot this stuff -.-


Good change. Logging line numbers yourself is really fragile.


Isn't this the same thing as below?


Finished starting up yarn and the dfs. Demoed viewing the cluster in a browser


Implementing #11


up to?


I avoided some print statements, but some remain
http://win-builder.r-project.org/9X2yNLM1NRZ1/00check.log


is it unclear that length maximum is 250 chars?


Yeah, that's fair. I guess there are some things that are different about RN that I don't know about


Uploaded.


thanks :+1:


Typo: Thanks -> That's.


@benjamn - this code will always set `buildMode` if it is different to "development" or "production".

However "test" is a valid value!! See https://github.com/meteor/meteor/issues/6473#issuecomment-195880283


btSocket was fine. It's usually ok to have some commonly used abbreviations. That produces less code to be read, so your reader could concentrate on those things that really need explanation.


Could these be made into configs? That way any time you want to change the nerfs you don't have to recompile.


The `db.model` command is required to register a model - `mongoose.model` will attach the model to the default connection.


Better, but still not clear why is it useless.


Yep, don't hesitate to improve all the namings :wink: i just wrote down the first thing that came to my mind


So after some more fiddling, I managed to use the `data-ko-placeholder-src` attribute and replace the `ko.bindingHandlers.wysiwygSrc.convertedUrl` in a plugin with a method that just returns the original src and that seems to work nicely, but I'm getting some errors for some blocks which look like:

```
ERROR: found unexpected -ko- attribute in compiled template anonymous-24977 , you probably mispelled it: ["data-ko-placeholder-src"]
ERROR: found unexpected -ko- attribute in compiled template headerBlock-show , you probably mispelled it: ["data-ko-placeholder-src", "data-ko-placeholder-src"]
```


Fair enough, I can see why we may want to have a packed structure there in the future. Though I don't know how fast_align fares for >256 words.

If people are to maintain this in the long run, there should be an explicit interface for accessing the word alignment, instead of a deeply hidden overloaded function binread(). I believe that the same goes for every of the many locations where there is a sequence of calls accessing a sequence of bytes.


actually, no.  They get their unlocalized name from the underlying block.  It was actually causing null pointer exceptions if I didn't branch off here.


looks like you want to link to an issue, so just asking if you haven't wrongly copy-and-pasted :)


On 11/03/16 15:56, Daniel Gustafsson wrote:
> Is there a case where `column` or `c->column` could be NULL here? I
> can't see one reading over the code but I'm not really familiar with
> this path. Since `equal()` has an additional NULL check before the
> `strcmp()` it would've passed clean.

Indeed there are: when c->deflt == TRUE, c->column is NULL. Regression
tests caught that; I had not run them to completion before submitting
the PR.

Updated the PR with a fixed version. There were some other bugs too:
transformAttributeEncoding() used to scribble on the input CreateStmt,
which didn't work too well when some parts of the CreateStmt were
allocated in the temporary memory context, and the CreateStmt was reused
later. But now it seems to work. Overall, this turned out to be much
more complicated than I thought when I started hacking this, but having
done all this, I think this is worth committing.

- Heikki


😐 weird


Should be either isDead or died (grammatically incorrect).


I most likely will pull these out into some form of config/json at some point.  I just wanted to get everything working first, then I'll worry about making it extendable.


develop (lefticus) - Win64-Windows-10-VisualStudio-14-Debug: OK (391 of 391 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


And when we have it working on electrical/coder bot all we have to do is
instantiate a variable for it on comp/practices bots because the debugged
and working code is already there
On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:

> The way I pictured it was electrical bot is what CoderBot was about before:
> dunno if this will work, so we're testing it out here before putting it in
> the competition code. The new IMUs, for example, would be tested and worked
> with in CoderBot before copying it into this repository.
>
> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com> wrote:
>
> > Well... kinda.
> > The pros was that it IS all one working space and that nothing has to be
> > switched over and we can work straight off the same code. It would be
> very
> > simple to move a sensor bug from comp bot to electrical bot, or in the
> case
> > of testing controls or motors we could test as well.
> > Electrical bot isn't limited by what it can do, we just don't quite know
> > what we'd use it for just yet. We may find ourselves testing new driver
> > station controls or new adjustments to a subsystem. The con I guess it's
> > that it's much larger and might possibly cause confusion. I tried to make
> > it as explicit as I could with the naming of things (I should add
> comments
> > to delineate when the robot works as electrical bot and as a functional
> > bot).
> > I feel like it's not a bad idea or trade to put it into one repo and
> > project because moving a system to be debugged on electrical bot will
> > probably be as simple as 5 lines of code now, and no switching or
> > copy/paste is required. We can literally run the same code just down a
> > different path of execution. That con is that we'll have that extra code
> > that idles to look at in all bots.
> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
> >
> > > I pictured electrical bot being a separate repository, as it will lack
> a
> > > lot of code that's in here. All of the subsystems that include motors,
> > all
> > > of the buttons that control them, etc. won't exist there. Did Chris
> > address
> > > any of that?
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
> > >
> >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855>
> .
>


Thanks, I think I've fixed this now.


RPKI Validation (and not RTR-Validation; RTR is only the protocol to exchange valid ROA data)


Magic behavior. Everyone would expect from getX to just return x.


I would propose that we revert this commit, and change line 294 to `else if (!nodeEnv)`.

This would target the use case of `NODE_ENV=something meteor`.

What is the use case you are trying to target here? FYI, The only time `buildMode` is not set coming in here is when you `meteor run` without `--production` (with `--production` it is set to "production" and in all test modes it'll be set to "test").


also it's best practice to assign the action name to a constant, then use the constant in the action. This hardens things up with little additional code


QChar is utf8. You can remove it and keep only char


No biggy!
On Mar 13, 2016 7:06 PM, "Oddface" <notifications@github.com> wrote:

> Sorry, sorry. I'm getting myself an idiot-proof text editor that doesn't
> do educated quotes at all, because I'm obviously never going to spot this
> stuff -.-
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/John-Smith-Modded/JSTR-Modded-1.7.x/commit/15937d3803889d041ae9ba804155b1bb7365b211#commitcomment-16670273>
> .
>


yeah but that does not add much benefit, as we already discussed once about route names


mSomething is a bad name for class. Please see what "m" prefix means:
http://source.android.com/source/code-style.html#follow-field-naming-conventions


But we also end up deploying all of the test code to the competition bot
though. By that logic, it would be easier to throw all of the code for
every year into one repo, because we're going to reuse a lot of the drive
code for succeeding years. But that ends up with a lot of stuff that
doesn't need to exist going onto the robot. Same with the test code: if it
isn't guaranteed to work, it shouldn't be on the competition bot.

On Sun, Mar 13, 2016 at 4:15 PM, Naoki <notifications@github.com> wrote:

> And when we have it working on electrical/coder bot all we have to do is
> instantiate a variable for it on comp/practices bots because the debugged
> and working code is already there
>
> On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
>
> > The way I pictured it was electrical bot is what CoderBot was about
> before:
> > dunno if this will work, so we're testing it out here before putting it
> in
> > the competition code. The new IMUs, for example, would be tested and
> worked
> > with in CoderBot before copying it into this repository.
> >
> > On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
> wrote:
> >
> > > Well... kinda.
> > > The pros was that it IS all one working space and that nothing has to
> be
> > > switched over and we can work straight off the same code. It would be
> > very
> > > simple to move a sensor bug from comp bot to electrical bot, or in the
> > case
> > > of testing controls or motors we could test as well.
> > > Electrical bot isn't limited by what it can do, we just don't quite
> know
> > > what we'd use it for just yet. We may find ourselves testing new driver
> > > station controls or new adjustments to a subsystem. The con I guess
> it's
> > > that it's much larger and might possibly cause confusion. I tried to
> make
> > > it as explicit as I could with the naming of things (I should add
> > comments
> > > to delineate when the robot works as electrical bot and as a functional
> > > bot).
> > > I feel like it's not a bad idea or trade to put it into one repo and
> > > project because moving a system to be debugged on electrical bot will
> > > probably be as simple as 5 lines of code now, and no switching or
> > > copy/paste is required. We can literally run the same code just down a
> > > different path of execution. That con is that we'll have that extra
> code
> > > that idles to look at in all bots.
> > > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
> > >
> > > > I pictured electrical bot being a separate repository, as it will
> lack
> > a
> > > > lot of code that's in here. All of the subsystems that include
> motors,
> > > all
> > > > of the buttons that control them, etc. won't exist there. Did Chris
> > > address
> > > > any of that?
> > > >
> > > > —
> > > > Reply to this email directly or view it on GitHub
> > > > <
> > >
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
> > > >
> > >
> > > > .
> > > >
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855
> >
>
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670336>
> .
>


Forgot to add the commit reason when I committed, sorry. I lowered the field elevation, that's all.


Give a brief comment about what the test verifies and what the expected outcome is.


It might be nice to add `-main` to the filename here, just to make it clear that it is different.


I think having one repo encapsulate the entire build wouldn't be bad 😅.
We'd have community between the electrical bot and others' in the project
by the fact that anything we do to test electrical bot is already there to
test on comp bot and vice versa.
On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:

> And when we have it working on electrical/coder bot all we have to do is
> instantiate a variable for it on comp/practices bots because the debugged
> and working code is already there
> On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
>
>> The way I pictured it was electrical bot is what CoderBot was about
>> before:
>> dunno if this will work, so we're testing it out here before putting it in
>> the competition code. The new IMUs, for example, would be tested and
>> worked
>> with in CoderBot before copying it into this repository.
>>
>> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com> wrote:
>>
>> > Well... kinda.
>> > The pros was that it IS all one working space and that nothing has to be
>> > switched over and we can work straight off the same code. It would be
>> very
>> > simple to move a sensor bug from comp bot to electrical bot, or in the
>> case
>> > of testing controls or motors we could test as well.
>> > Electrical bot isn't limited by what it can do, we just don't quite know
>> > what we'd use it for just yet. We may find ourselves testing new driver
>> > station controls or new adjustments to a subsystem. The con I guess it's
>> > that it's much larger and might possibly cause confusion. I tried to
>> make
>> > it as explicit as I could with the naming of things (I should add
>> comments
>> > to delineate when the robot works as electrical bot and as a functional
>> > bot).
>> > I feel like it's not a bad idea or trade to put it into one repo and
>> > project because moving a system to be debugged on electrical bot will
>> > probably be as simple as 5 lines of code now, and no switching or
>> > copy/paste is required. We can literally run the same code just down a
>> > different path of execution. That con is that we'll have that extra code
>> > that idles to look at in all bots.
>> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
>> >
>> > > I pictured electrical bot being a separate repository, as it will
>> lack a
>> > > lot of code that's in here. All of the subsystems that include motors,
>> > all
>> > > of the buttons that control them, etc. won't exist there. Did Chris
>> > address
>> > > any of that?
>> > >
>> > > —
>> > > Reply to this email directly or view it on GitHub
>> > > <
>> >
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
>> > >
>> >
>> > > .
>> > >
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855>
>> .
>>
>


it makes it  possible to reuse a name (if all actions are defined in the same scope). I guess it's not a massive deal here, so we should keep it simple


I think List<BitSet> could be a better type here.


Now it is "futureproof", but I got a different problem. If I remove one of the preloaded blocks, for some of them it will throw an error:

`Unexpected object not found in parent array`


I am just a contributor; I do not make policy. That said...

From the link you cite (second paragraph):

"To register a user defined type ..."

"long" is not a user-defined type. Boost.Polygon had support for "int" and "long long" but not for "long". I claim this was unambiguously a bug.

Your work around broke when the bug got fixed. I think it is debatable whether that deserves a release note, but I will let that argument go... Just as long as you are not trying to get this bug fix reverted.

Incidentally, the same preprocessor directive is in my own code, since I also needed a work around before Boost 1.60 was released :-)


Refactor out business logic into it's own method? (Like `shorten)


General comment: prefer single-responsibility commits. If this commit is to add documentation, it should not do anything else. If some commit is fixing a bug, there should be no refactoring in it. If you are about to add new functionality and have to refactor something to implement that, make two commits: first one to refactor and second one to implement a feature.


Just delete code if it's no longer valid


Did you add yourself as author where you added new functionality?


Propose the agreement to Chris because he's the one who turned me out on
this as additionally talk to Doug. This was really half the reason to event
put files into the Rio.
On Mar 13, 2016 4:19 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:

> I think having one repo encapsulate the entire build wouldn't be bad 😅.
> We'd have community between the electrical bot and others' in the project
> by the fact that anything we do to test electrical bot is already there to
> test on comp bot and vice versa.
> On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
>
>> And when we have it working on electrical/coder bot all we have to do is
>> instantiate a variable for it on comp/practices bots because the debugged
>> and working code is already there
>> On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
>>
>>> The way I pictured it was electrical bot is what CoderBot was about
>>> before:
>>> dunno if this will work, so we're testing it out here before putting it
>>> in
>>> the competition code. The new IMUs, for example, would be tested and
>>> worked
>>> with in CoderBot before copying it into this repository.
>>>
>>> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
>>> wrote:
>>>
>>> > Well... kinda.
>>> > The pros was that it IS all one working space and that nothing has to
>>> be
>>> > switched over and we can work straight off the same code. It would be
>>> very
>>> > simple to move a sensor bug from comp bot to electrical bot, or in the
>>> case
>>> > of testing controls or motors we could test as well.
>>> > Electrical bot isn't limited by what it can do, we just don't quite
>>> know
>>> > what we'd use it for just yet. We may find ourselves testing new driver
>>> > station controls or new adjustments to a subsystem. The con I guess
>>> it's
>>> > that it's much larger and might possibly cause confusion. I tried to
>>> make
>>> > it as explicit as I could with the naming of things (I should add
>>> comments
>>> > to delineate when the robot works as electrical bot and as a functional
>>> > bot).
>>> > I feel like it's not a bad idea or trade to put it into one repo and
>>> > project because moving a system to be debugged on electrical bot will
>>> > probably be as simple as 5 lines of code now, and no switching or
>>> > copy/paste is required. We can literally run the same code just down a
>>> > different path of execution. That con is that we'll have that extra
>>> code
>>> > that idles to look at in all bots.
>>> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
>>> >
>>> > > I pictured electrical bot being a separate repository, as it will
>>> lack a
>>> > > lot of code that's in here. All of the subsystems that include
>>> motors,
>>> > all
>>> > > of the buttons that control them, etc. won't exist there. Did Chris
>>> > address
>>> > > any of that?
>>> > >
>>> > > —
>>> > > Reply to this email directly or view it on GitHub
>>> > > <
>>> >
>>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
>>> > >
>>> >
>>> > > .
>>> > >
>>> >
>>> > —
>>> > Reply to this email directly or view it on GitHub
>>> > <
>>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
>>> >
>>> > .
>>> >
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855>
>>> .
>>>
>>


Argument*
On Mar 13, 2016 4:23 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:

> Propose the agreement to Chris because he's the one who turned me out on
> this as additionally talk to Doug. This was really half the reason to event
> put files into the Rio.
> On Mar 13, 2016 4:19 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
>
>> I think having one repo encapsulate the entire build wouldn't be bad 😅.
>> We'd have community between the electrical bot and others' in the project
>> by the fact that anything we do to test electrical bot is already there to
>> test on comp bot and vice versa.
>> On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
>>
>>> And when we have it working on electrical/coder bot all we have to do is
>>> instantiate a variable for it on comp/practices bots because the debugged
>>> and working code is already there
>>> On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
>>>
>>>> The way I pictured it was electrical bot is what CoderBot was about
>>>> before:
>>>> dunno if this will work, so we're testing it out here before putting it
>>>> in
>>>> the competition code. The new IMUs, for example, would be tested and
>>>> worked
>>>> with in CoderBot before copying it into this repository.
>>>>
>>>> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
>>>> wrote:
>>>>
>>>> > Well... kinda.
>>>> > The pros was that it IS all one working space and that nothing has to
>>>> be
>>>> > switched over and we can work straight off the same code. It would be
>>>> very
>>>> > simple to move a sensor bug from comp bot to electrical bot, or in
>>>> the case
>>>> > of testing controls or motors we could test as well.
>>>> > Electrical bot isn't limited by what it can do, we just don't quite
>>>> know
>>>> > what we'd use it for just yet. We may find ourselves testing new
>>>> driver
>>>> > station controls or new adjustments to a subsystem. The con I guess
>>>> it's
>>>> > that it's much larger and might possibly cause confusion. I tried to
>>>> make
>>>> > it as explicit as I could with the naming of things (I should add
>>>> comments
>>>> > to delineate when the robot works as electrical bot and as a
>>>> functional
>>>> > bot).
>>>> > I feel like it's not a bad idea or trade to put it into one repo and
>>>> > project because moving a system to be debugged on electrical bot will
>>>> > probably be as simple as 5 lines of code now, and no switching or
>>>> > copy/paste is required. We can literally run the same code just down a
>>>> > different path of execution. That con is that we'll have that extra
>>>> code
>>>> > that idles to look at in all bots.
>>>> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
>>>> >
>>>> > > I pictured electrical bot being a separate repository, as it will
>>>> lack a
>>>> > > lot of code that's in here. All of the subsystems that include
>>>> motors,
>>>> > all
>>>> > > of the buttons that control them, etc. won't exist there. Did Chris
>>>> > address
>>>> > > any of that?
>>>> > >
>>>> > > —
>>>> > > Reply to this email directly or view it on GitHub
>>>> > > <
>>>> >
>>>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
>>>> > >
>>>> >
>>>> > > .
>>>> > >
>>>> >
>>>> > —
>>>> > Reply to this email directly or view it on GitHub
>>>> > <
>>>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
>>>> >
>>>> > .
>>>> >
>>>>
>>>> —
>>>> Reply to this email directly or view it on GitHub
>>>> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855>
>>>> .
>>>>
>>>


"Wut" means "unknown" https://github.com/ZeroK-RTS/Zero-K/blob/master/LuaUI/Images/flags/wut.png


Every single year? All of Recycle Rush, Aerial Assist, etc. being deployed
onto Gretta? 😕

Right, but anything that *isn't* tested is also right there on comp bot,
which could break things on the robot. If you swap out the drive's Gyro
instance with an IMU, but the IMU isn't fully implemented and getAngle()
returns 0 with a TODO comment to implement it, all of our gyro-based stuff
at competition suddenly dies.

On Sun, Mar 13, 2016 at 4:19 PM, Naoki <notifications@github.com> wrote:

> I think having one repo encapsulate the entire build wouldn't be bad 😅.
> We'd have community between the electrical bot and others' in the project
> by the fact that anything we do to test electrical bot is already there to
> test on comp bot and vice versa.
>
> On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
>
> > And when we have it working on electrical/coder bot all we have to do is
> > instantiate a variable for it on comp/practices bots because the debugged
> > and working code is already there
> > On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
> >
> >> The way I pictured it was electrical bot is what CoderBot was about
> >> before:
> >> dunno if this will work, so we're testing it out here before putting it
> in
> >> the competition code. The new IMUs, for example, would be tested and
> >> worked
> >> with in CoderBot before copying it into this repository.
> >>
> >> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
> wrote:
> >>
> >> > Well... kinda.
> >> > The pros was that it IS all one working space and that nothing has to
> be
> >> > switched over and we can work straight off the same code. It would be
> >> very
> >> > simple to move a sensor bug from comp bot to electrical bot, or in the
> >> case
> >> > of testing controls or motors we could test as well.
> >> > Electrical bot isn't limited by what it can do, we just don't quite
> know
> >> > what we'd use it for just yet. We may find ourselves testing new
> driver
> >> > station controls or new adjustments to a subsystem. The con I guess
> it's
> >> > that it's much larger and might possibly cause confusion. I tried to
> >> make
> >> > it as explicit as I could with the naming of things (I should add
> >> comments
> >> > to delineate when the robot works as electrical bot and as a
> functional
> >> > bot).
> >> > I feel like it's not a bad idea or trade to put it into one repo and
> >> > project because moving a system to be debugged on electrical bot will
> >> > probably be as simple as 5 lines of code now, and no switching or
> >> > copy/paste is required. We can literally run the same code just down a
> >> > different path of execution. That con is that we'll have that extra
> code
> >> > that idles to look at in all bots.
> >> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
> >> >
> >> > > I pictured electrical bot being a separate repository, as it will
> >> lack a
> >> > > lot of code that's in here. All of the subsystems that include
> motors,
> >> > all
> >> > > of the buttons that control them, etc. won't exist there. Did Chris
> >> > address
> >> > > any of that?
> >> > >
> >> > > —
> >> > > Reply to this email directly or view it on GitHub
> >> > > <
> >> >
> >>
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
> >> > >
> >> >
> >> > > .
> >> > >
> >> >
> >> > —
> >> > Reply to this email directly or view it on GitHub
> >> > <
> >>
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
> >> >
> >> > .
> >> >
> >>
> >> —
> >> Reply to this email directly or view it on GitHub
> >> <
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855
> >
> >> .
> >>
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670361>
> .
>


Why make this change? That is not in the spec. https://html.spec.whatwg.org/#dom-document-images Similar for all the others.


On mentor involvment, @reederc42 @chappelled What do you think?


Nit: we're trying to move toward "isXML" style for abbreviations.


s/uri/url


Instead of targeting **all** `<p>` tags, it would be better to use the id name (as you did below); if you use `#show-this-on-click` as your selector, then you can entirely delete line 21 below.


Can you use the `con-type` module to get more robust parsing? (Or any other of your choice, but that is what we ended up choosing tentatively in #1400.)


Nope - there was no issue and it was a fix for the CI, so just mentioned that for reference

-----Original Message-----
From: "Mischa Krüger" <notifications@github.com>
Sent: 14-03-2016 04:43
To: "coala-analyzer/coala" <coala@noreply.github.com>
Cc: "AbdealiJK" <abdealikothari@gmail.com>
Subject: Re: [coala] ConsoleInteractionTest: Make test generic (2387f5d)

looks like you want to link to an issue, so just asking if you haven't wrongly copy-and-pasted :)
—
Reply to this email directly or view it on GitHub.


**Challenge:** Can you refactor this logic using an array? Instead of 3 if statements, use 1 array.


Typo before this line:
```
the nitrogen gets a positve charge
```
If you  fix it   I won't wait for the builds to finish. :)


I will also further use this database to build on and maintain these skills.


If it's not fully implemented in electrical, how would there be an
instantiation for it out practice or competition? The only thing that could
cause this is if someone didn't look at the files and assumed something
worked which then instantiated and deployed it to said robot 😅. It'd take
a lot of sketch and miscommunication to do that
On Mar 13, 2016 4:24 PM, "Ian W" <notifications@github.com> wrote:

> Every single year? All of Recycle Rush, Aerial Assist, etc. being deployed
> onto Gretta? 😕
>
> Right, but anything that *isn't* tested is also right there on comp bot,
> which could break things on the robot. If you swap out the drive's Gyro
> instance with an IMU, but the IMU isn't fully implemented and getAngle()
> returns 0 with a TODO comment to implement it, all of our gyro-based stuff
> at competition suddenly dies.
>
> On Sun, Mar 13, 2016 at 4:19 PM, Naoki <notifications@github.com> wrote:
>
> > I think having one repo encapsulate the entire build wouldn't be bad 😅.
> > We'd have community between the electrical bot and others' in the project
> > by the fact that anything we do to test electrical bot is already there
> to
> > test on comp bot and vice versa.
> >
> > On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
> >
> > > And when we have it working on electrical/coder bot all we have to do
> is
> > > instantiate a variable for it on comp/practices bots because the
> debugged
> > > and working code is already there
> > > On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
> > >
> > >> The way I pictured it was electrical bot is what CoderBot was about
> > >> before:
> > >> dunno if this will work, so we're testing it out here before putting
> it
> > in
> > >> the competition code. The new IMUs, for example, would be tested and
> > >> worked
> > >> with in CoderBot before copying it into this repository.
> > >>
> > >> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
> > wrote:
> > >>
> > >> > Well... kinda.
> > >> > The pros was that it IS all one working space and that nothing has
> to
> > be
> > >> > switched over and we can work straight off the same code. It would
> be
> > >> very
> > >> > simple to move a sensor bug from comp bot to electrical bot, or in
> the
> > >> case
> > >> > of testing controls or motors we could test as well.
> > >> > Electrical bot isn't limited by what it can do, we just don't quite
> > know
> > >> > what we'd use it for just yet. We may find ourselves testing new
> > driver
> > >> > station controls or new adjustments to a subsystem. The con I guess
> > it's
> > >> > that it's much larger and might possibly cause confusion. I tried to
> > >> make
> > >> > it as explicit as I could with the naming of things (I should add
> > >> comments
> > >> > to delineate when the robot works as electrical bot and as a
> > functional
> > >> > bot).
> > >> > I feel like it's not a bad idea or trade to put it into one repo and
> > >> > project because moving a system to be debugged on electrical bot
> will
> > >> > probably be as simple as 5 lines of code now, and no switching or
> > >> > copy/paste is required. We can literally run the same code just
> down a
> > >> > different path of execution. That con is that we'll have that extra
> > code
> > >> > that idles to look at in all bots.
> > >> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
> > >> >
> > >> > > I pictured electrical bot being a separate repository, as it will
> > >> lack a
> > >> > > lot of code that's in here. All of the subsystems that include
> > motors,
> > >> > all
> > >> > > of the buttons that control them, etc. won't exist there. Did
> Chris
> > >> > address
> > >> > > any of that?
> > >> > >
> > >> > > —
> > >> > > Reply to this email directly or view it on GitHub
> > >> > > <
> > >> >
> > >>
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
> > >> > >
> > >> >
> > >> > > .
> > >> > >
> > >> >
> > >> > —
> > >> > Reply to this email directly or view it on GitHub
> > >> > <
> > >>
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
> > >> >
> > >> > .
> > >> >
> > >>
> > >> —
> > >> Reply to this email directly or view it on GitHub
> > >> <
> >
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855
> > >
> > >> .
> > >>
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670361
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670385>
> .
>


Again, please do not parse content types manually. Use an npm package.


Either way talk to a few mentors I gtg work 😅
On Mar 13, 2016 4:27 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:

> If it's not fully implemented in electrical, how would there be an
> instantiation for it out practice or competition? The only thing that could
> cause this is if someone didn't look at the files and assumed something
> worked which then instantiated and deployed it to said robot 😅. It'd take
> a lot of sketch and miscommunication to do that
> On Mar 13, 2016 4:24 PM, "Ian W" <notifications@github.com> wrote:
>
>> Every single year? All of Recycle Rush, Aerial Assist, etc. being deployed
>> onto Gretta? 😕
>>
>> Right, but anything that *isn't* tested is also right there on comp bot,
>> which could break things on the robot. If you swap out the drive's Gyro
>> instance with an IMU, but the IMU isn't fully implemented and getAngle()
>> returns 0 with a TODO comment to implement it, all of our gyro-based stuff
>> at competition suddenly dies.
>>
>> On Sun, Mar 13, 2016 at 4:19 PM, Naoki <notifications@github.com> wrote:
>>
>> > I think having one repo encapsulate the entire build wouldn't be bad 😅.
>> > We'd have community between the electrical bot and others' in the
>> project
>> > by the fact that anything we do to test electrical bot is already there
>> to
>> > test on comp bot and vice versa.
>> >
>> > On Mar 13, 2016 4:15 PM, "Naoki95957" <naoki.l.95957@gmail.com> wrote:
>> >
>> > > And when we have it working on electrical/coder bot all we have to do
>> is
>> > > instantiate a variable for it on comp/practices bots because the
>> debugged
>> > > and working code is already there
>> > > On Mar 13, 2016 2:40 PM, "Ian W" <notifications@github.com> wrote:
>> > >
>> > >> The way I pictured it was electrical bot is what CoderBot was about
>> > >> before:
>> > >> dunno if this will work, so we're testing it out here before putting
>> it
>> > in
>> > >> the competition code. The new IMUs, for example, would be tested and
>> > >> worked
>> > >> with in CoderBot before copying it into this repository.
>> > >>
>> > >> On Sun, Mar 13, 2016 at 10:09 AM, Naoki <notifications@github.com>
>> > wrote:
>> > >>
>> > >> > Well... kinda.
>> > >> > The pros was that it IS all one working space and that nothing has
>> to
>> > be
>> > >> > switched over and we can work straight off the same code. It would
>> be
>> > >> very
>> > >> > simple to move a sensor bug from comp bot to electrical bot, or in
>> the
>> > >> case
>> > >> > of testing controls or motors we could test as well.
>> > >> > Electrical bot isn't limited by what it can do, we just don't quite
>> > know
>> > >> > what we'd use it for just yet. We may find ourselves testing new
>> > driver
>> > >> > station controls or new adjustments to a subsystem. The con I guess
>> > it's
>> > >> > that it's much larger and might possibly cause confusion. I tried
>> to
>> > >> make
>> > >> > it as explicit as I could with the naming of things (I should add
>> > >> comments
>> > >> > to delineate when the robot works as electrical bot and as a
>> > functional
>> > >> > bot).
>> > >> > I feel like it's not a bad idea or trade to put it into one repo
>> and
>> > >> > project because moving a system to be debugged on electrical bot
>> will
>> > >> > probably be as simple as 5 lines of code now, and no switching or
>> > >> > copy/paste is required. We can literally run the same code just
>> down a
>> > >> > different path of execution. That con is that we'll have that extra
>> > code
>> > >> > that idles to look at in all bots.
>> > >> > On Mar 12, 2016 5:26 PM, "Ian W" <notifications@github.com> wrote:
>> > >> >
>> > >> > > I pictured electrical bot being a separate repository, as it will
>> > >> lack a
>> > >> > > lot of code that's in here. All of the subsystems that include
>> > motors,
>> > >> > all
>> > >> > > of the buttons that control them, etc. won't exist there. Did
>> Chris
>> > >> > address
>> > >> > > any of that?
>> > >> > >
>> > >> > > —
>> > >> > > Reply to this email directly or view it on GitHub
>> > >> > > <
>> > >> >
>> > >>
>> >
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16665296
>> > >> > >
>> > >> >
>> > >> > > .
>> > >> > >
>> > >> >
>> > >> > —
>> > >> > Reply to this email directly or view it on GitHub
>> > >> > <
>> > >>
>> >
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16668431
>> > >> >
>> > >> > .
>> > >> >
>> > >>
>> > >> —
>> > >> Reply to this email directly or view it on GitHub
>> > >> <
>> >
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16669855
>> > >
>> > >> .
>> > >>
>> > >
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670361
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/FRC4131/FRCStronghold2016/commit/b4d50378b9d8f3b15fda17be7cbd010b2b61aeab#commitcomment-16670385>
>> .
>>
>


@htaler I've added FakeItEasy NuGet package and sample unit test - is that ok?


**Challenge:** Have you heard of objects?

```js
var person = {
   "name": "Ricky",
   "hungry": true,
   "craving": "food",
   "hangryLevel": 7
}
```

Can you think of a way to refactor this if else statement using objects to determine the winner / loser?


Why is this here?  Doesn't Django serve the favicon automatically?


it's working for me, whit a message when i reload my save : "Reinitialised : Special Keys Statistics Report"
Question: this new code has an impact on the gameplay/mod ?
Anyway Thanx You, i can save and reload my game now ! ;)


This line is the same as above. Should be extracted to the outer scope.


npm install i18next
I entered the above at command line; wow, crazy simple!


Shortcut :)

```js
var bools = new Array(6).fill(false);
```


Fixed issue #1 bug.


Done!


Could I persuade you to use 4 space indentation instead of 3 space indentation?  The formatting in the plugin source code is already messy enough without changing from 3 space indentation to 4 space indentation inside the same file.


Woah, that's an old jQuery library! You should use google cdn's library. Google `google jquery cdn` and the first link should be `https://developers.google.com/speed/libraries/` from there look for jQuery.

```html
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js"></script>
```


If you're writing and committing on electrical, and then get called off to work on copybot, you'll take the same code you were just using (with incomplete IMU) to go to copybot. Then you'd deploy that code (with IMU) to the robot (without an IMU), and things explode.


We should highlight hat only plain TCP is supported at the moment.


npm update
Run this in qalang directory to update all npm packages in that folder.


Hahaha!  No wonder most of my jquery code from a week ago wasn't working!


111247952_Remove_QUUID-rebased (lefticus) - i386-Windows-7-VisualStudio-12: OK (2375 of 2397 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.08%25-yellow.svg)


Lg3 d855 cm13 have support f2fs? :+1:


:+1: Tested!


This hangs here on my laptop.


xxxxx


 inver <- NULL
 +  set <- function(y) {
 +    x <<- y
 +    Invert <<- NULL
 +  }

In the fourth line you have Invert. It got to be inver. That is you are clearing previous value when you use the set method.


merge update


No need to ifdef this


Thanks, @davidmfoley !

I got it all working, choosing an random game from the games array. Here's my latest commit: https://github.com/rmtolmach/frontpocket/commit/c29d7a6df3e9aed1a31c878be9d684f92974b894


If you add both fonts to the collection then hit use it'll generate a single URL :)

```html
<link href='https://fonts.googleapis.com/css?family=Coming+Soon|Cabin:700,500' rel='stylesheet' type='text/css'>
```

By making two separate requests it's actually slower! Imagine opening two tabs and going to each url separately versus just one with both of them. Not a big deal right now, but imagine a bit site with lots of fonts and other files? :scream_cat:


And smal fix: #4172


This should be a platform check not an ifdef. Just because the binary was built with AML libs doesn't mean it's running on AML hardware.


@Zaffy i forget this https://github.com/OregonCore/OregonCore/commit/67e7a72b8a5c3011d2dc909808461b8212258a17


Hero page is awesome!


If you actually make a branch called `gh-pages` you can turn this into a website!
https://pages.github.com/

The URL would then be https://Kraehe.github.io/nha_assignments


Very clever using multiple selectors here!


Tsk @windy1


I'm thinking it might just be better to ditch the HAVE_AML checks (and the Amlogic Codec Options print too) on these. There's nothing AML specific about forcing h264. The option won't do anything for other devices but it will be useful on Pi 3 soon.


The test "responsexml-document-properties.htm" seems to indicate that this is the expected behaviour. Anyway, why an XML document should contain an HTML property ? The document should follow this specification in this case : https://dom.spec.whatwg.org/#interface-document and not https://html.spec.whatwg.org/


rather than adding an additional click listener and handler to each of these link elements, you could add `event.preventDefault` to each of the click handlers below.  this is a better way to approach this functionality as it means that for each link, there is only one function that is handling each click.


We already have a SkullUtils I believe.


@jakkubu Looks good. I will give at a quick test once I have a spare minute.


XML and HTML documents both use https://html.spec.whatwg.org/#document when extends https://dom.spec.whatwg.org/#interface-document. Have you tested browsers?


yes, the client gets updated, send an update to server, which notifies observers. The client will get the server update but won't send a new packet on its outport since the value is the same as the local.


Este es la iteracion 1 Ciclo 1 (Verde)


If the given position is ways out to the right then merely subtracting one won't fix it.
Maybe rather: `position = position.withColumn( viewportSize.getColumns() - 1 );`


Este es la iteracion 1 Ciclo 1 (Rojo)


Good start! `valueToUser` currently only returns one of the coins. You need to return 5 coins and have it display.


This code may be the clearest and correctest:

```js
let buildMode = runOptions.buildOptions.buildMode;
  if (buildMode === "development" || buildMode === "production") {
    process.env.NODE_ENV = buildMode;
  }

  let nodeEnv = process.env.NODE_ENV;
  if (!buildMode) {
    if (nodeEnv === "development" || nodeEnv === "production") {
      runOptions.buildOptions.buildMode = nodeEnv;
    } else {
      runOptions.buildOptions.buildMode = "development";
    }
  }

  if (!nodeEnv) {
    process.env.NODE_ENV = "development";
  }
```


The method does not need any instance state.


Filed https://github.com/w3c/web-platform-tests/issues/2668. Let's revert these changes and comment out that test with a link to that bug.


+# 1cb075eaa55036a4627f7a2f49941566e2c51485


User factory looks so cool!  Way to go!


What was the reason for moving this? it seems better to precompute, all else being equal.


![Uploading img5517b2269ea893.00868213n.jpg…]()


Firefox has this behaviour but not Chrome.


OK. Talked with Chris, and his angle is that all of the experimental features (like the IMU) go in a separate branch so that that kind of mis-deploy doesn't happen. Now it's just fully teaching you and Yana how to use branching.


Note that to delete the lowest bit from an integer, the standard broadword trick is:

    x = x & x - 1

You're using now

    x -= x & -x

which uses an extra operation. The standard way should be faster.


Hey you mite also need to add the table closing tag somewhere.


テスト用マップの作成 #368


@mostaphaRoudsari @sariths @chriswmackey

I'm happy to answer any questions on Three.js. Feel free to ask for code examples of specific things you are interested in.

A fun place to see what's happening with Three.js

https://plus.google.com/u/0/+ThreejsOrg

The competition is: https://unity3d.com/ followed by a distant scene.js

>> I have grown to hate javascript with a passion! I was always fumbling around between HTML, CSS, and JS to get things working.

I could not agree more.

Here are some of my current recipes for taming the beast:

You will note that my code is 100% JavaScript. I create and edit styles and tags as needed inside JavaScript.

Apart from Three.js there are no external dependencies. No jQuery, no Backbone, no Angular. Just 100% JavaScript. Why? Because none of them do 3D.

If such libraries are needed, I embed the Three.js in an iframe.

Learning to access the entire DOM from inside JavaScript is fascinating.

Theo


@kyleboss I think this shouldn't be removed


I'm not certain, but I don't think so.  We only run foreman on el6 with selinux in permissive mode, but since it's actually the puppet master/puppetserver writing the files the default labelling should work.


No it isn't. That modulo 60 is for hours (= 60 minutes). Otherwise you'll get something like "1h72:30" in output, instead of "1h12:30".


I don't think `!important` is needed here. We should avoid using `!imporant` if there isn't really a good reason. https://css-tricks.com/when-using-important-is-the-right-choice/

I actually prefer this the way it was before. I pulled down the changes and with the update it is much less obvious the bars are a button to click to expose the sidebar. I'm open to discussion about this point though.


Same as above.


what was wrong with postscript? (jw)


is this script running as root?


Window.define didn't work?


@antinucleon  I was wondering where does the average calculation is performed? Like `PoolingOp<cpu, mshadow::red::sum>(param) / n`?


#4 related.


include our MAIL_SIGNATURE from ocflib?


did you accidentally merge in #19?


I changed all strings to QStrings due to QT's use of their strings in a lot of the methods for their GUI


Vou trabalhar nisso :)


Hi


Spotted a typo here.  Unkown -> Unknown.


This change looks great. We can use a more specific property instead of all:

    transition: transform 0.5s ease;


Nothing, but ghostscript seems to handle PDFs well and I was under the impression PDF was the preferred backend format for CUPS. We can change back to postscript if it turns out to be more compatible with various print jobs.

I actually found this: https://wiki.linuxfoundation.org/en/OpenPrinting/PDF_as_Standard_Print_Job_Format. Not recent but suggests what I was thinking.


Good idea.


Yes.


Oh, I missed!
For [WIP] json-caching.
I revert later.


alright thanks!


that's scary as hell. i'll see if i can find a good way to avoid that.


Yes you are right it should be ```nbChunks >= MAX_RENDER_CHUNKS```. Not sure why I subtracted 1


@bqpd


better code quality


I don't really care about the last line -- maybe there's something smarter to test for. It's the `c = (v >= vmin)` that fails and shouldn't.


You might want to move this variable to the chemical reaction's parent, so all synthanol drinks make that sound by default?


peek


Added downloadable xpi for issue https://github.com/nmaier/about-addons-memory/issues/21


record donations to mongo


Perhaps you could give an example of using [omniauth-identity](https://github.com/intridea/omniauth-identity) (or any of the other [dozens of strategies](https://github.com/intridea/omniauth/wiki/List-of-Strategies))
thanks


@kotishe  Hi,Where is the database file updated?

ALTER TABLEversion MODIFY COLUMNcore_revisionvarchar(50) NULL DEFAULT NULL AFTERcore_version, MODIFY COLUMNdb_revisionvarchar(50) NOT NULL DEFAULT 0 COMMENT 'Revision of world db' AFTERdb_version;


i read the manuel. im still confused on what to do to install smashhax. is
there a video?
On Mar 12, 2016 8:22 PM, "deadair3210" <notifications@github.com> wrote:

> They didnt just block that specific payload, they patched the hole in the
> browser. The hax never gets far enough to load the payload.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/yellows8/3ds_smashbroshax/commit/7d0759f5c5384287a99bad58dd02d2253386c313#commitcomment-16665436>
> .
>


# Introdução

Esse guia tem como finalidade ensinar a baixar, instalar e configurar uma máquina virtual. Para isso você vai precisar de:

  - Máquina Virtual
  - Distribuição Linux (SliTaz 32bits)
  - Emulador de ISO (Daemon Tools)

#### Passo 1 ####
Nessa parte iremos baixar e instalar a máquina virtual, nesse exemplo utilizaremos a VirtualBox.

 - Acesse o site [VirtualBox.org](https://www.virtualbox.org/) e clique em download;
 - Selecione a opção desejada, nesse exemplo utilizaremos **VirtualBox 5.0.16 for Windows hosts**;
 - Ao terminar execute o arquivo baixado;
 - Clique em "**Next**";
 - Caso queira mudar o diretório de instalação, selecione **Browser** e escolha o destino, caso não queira, cique em "**Next**";
 - Clique em "**Next**";
 - Clique em "**Yes**";
 - Clique em "**Install**";
 - Clique em "**Yes**" quando solicitado;
 - Clique em "**Finish**" para finalizar;

#### Passo 2 ####
Nessa parte será ensinado a criar uma Máquina Virtual.

- Execute a Oracle VirtualBox;
- Clique em "**Novo**";
- Em "**Nome**", coloque "**Linux**";
- Em "**Versão**", escolha "**Other Linux (32bit)**" e selecione "**Próximo**";
- Selecione o tamanho da memória para "**512 mb**" e clique em "**Próximo**";
- Selecione "**Criar um disco rígido virtual agora**" e clique em "**Criar**";
- Selecione "**VDI (VirtualBox Disk Image)**" e clique em "**Próximo**";
- Selecione "**Dinamicamente alocado**" e clique em "**Próximo**";
- Coloque o tamanho do disco em "**60 GB**" e clique em "**Criar**";

### Passo 3 ###

Nessa parte será ensinado como baixar o SliTaz e como executar o LiveCD.

- Acesse o site do [SliTaz](http://www.slitaz.org/pt/);
- Baixe a versão mais atualizada;
- Execute a "**Oracle VM VirtualBox**" e selecione "**Inicar**";
- Selecione onde está salvo o SliTaz e clique em "**Iniciar**";
- Selecione a opção "**Brazil (Abnt2)**"
- Aperte "**Enter**"
- Selecione a opção "**SliTaz Live**";

### Passo 4 ###

Nessa parte será ensinado como criar uma partição e instalar o SliTaz.

- Escolha "**Aplicativos**" no canto superior esquerdo;
- Selecione "**Sistema**" e escolha "**Instalador do SliTaz**";
- Será selecionado um login e senha, por padrão coloque "**root**" em ambos;
- Clique em "**Install SliTaz**";
- Clique em "**Execute Gparted**";
- Selecione a opção "**Dispositivo**" e selecione "**Criar tabela de partição**"
- Clique em "**Aplicar**";
- Clique com o botão direito na nova partição e selecione "**Novo**";
- Selecione o tamanho (em torno de 60GB);
- No sistema de arquivos selecione a opção "**ext4**";
- Clique em "**Adicionar**";
- Clique em "**Aplicar**" e "**Aplicar**" novamente;
- Clique em "**Salvar detalhes**" e "**Salvar**";
- Clique na partição criada, clique com o botão direito e selecione "**Gerenciar Sinalizadores**";
- Escolha a opção "**boot**" e clique em "**Fechar**";
- Feche a janela do Gparted;
- Desça o documento até o final e clique em "**Continue Installation**";
- Na nova janela, na opção "**Install SliTaz to partition**" selecione "**/dev/sda1 (ext4)**";
- Em BootLoader marque a opção "**Install a bootloader.**";
- Clique em "**Proceed to SliTaz installation**";
- Quando o sistema terminar de instalar clique em "**Installation complete, You can now restart**";
- Feche a Máquina Virtual;
- Na Oracle VM VirtualBox Gerenciador selecione sua máquina virtual e clique no botão "**Configurações**";
- Escolha a opção "**Sistema**";
- Na parte de "**Ordem do Boot**" deixe selecionado apenas a opção "**Disco Rígido**";
- Clique em "**OK**";
- Inicialize a Máquina Virtual;
- Coloque "**Tux**" no login e senha;
- Fim;

Pronto, sua Máquina Virtual está instalada, configurada e pronta para o uso.


I don't think `inject` belongs here too


* columnName对应的数据不存在的时候，也就是为null的时候，XXX.valueOf()将会抛出NumberFormatException异常。由于现在xUtils3的数据库是在第一次插入数据时才建表的，在那之前使用了findDbModel的方法表不存在自然什么都查不到。
* DbModel.getXXX返回参数是原始类型的，使用XXX.valueOf会返回包装类，中间会有一个自动装箱拆箱的过程。直接使用XXX.parseXXX()的效率会更好一些。


Hm, I think it actually might, since ia_is_inject_view suppresses FIELD_NOT_NULLABLE which may happen if the field is set to null in a destructor (does dagger do that?)


could this be changed to `getPlugin(main.__plugin_name__)` ?


Nice @aranhoide!


RFinite should be 01 (RFinite is not defined)


Dagger doesn't do that in a destructor, but it does allow for null injections. Some other DI frameworks do too


Correção nome ola mundo


This didn't work properly. The params are all FUBAR..


inicial


teste


BT works, now need to see if less power used, will take time. Seems good change.


What benefits does this hold btw?


Since YesseniaValencia switched into this repo after lab05, making an assessment described in the directions of Lab05 and saving it as w16_lab07.md addresses Issue #18


Related with
https://github.com/arrking/octopus/issues/18


Yes, it does too.


Btw, I also needed to edit `jupyter-js-widgets`.

In the new implementation of loadClass, we should call `window.require` instead of `requirejs()`


Since it is a macro and is only making calls to the functions (not internal fns or FFI fns) of the library, i think it is okay to print here.


nice mysql password


this is why i need cleanup.py


Not sure what you were trying to do here but I'm sure it ain't working since the paths are wrong.


Ok, thanks. Is that documented somewhere?


Oops My fault.


@FaaPz can the parameter also support string?
IMO, it is a PITA if i need to casting every time I call limit:

```php
$stmt->limit( (int) $offset, (int) $top);
```

Since I get the offset and limit from query param (used in pagination).
In my experience, other library is allow numeric string in limit parameters.
So, I need to read the source before I realized the parameter need to be integer.
I think using is_numeric in limit is more appropriate:

```php
public function limit($number, $offset = null)
{
	if (is_numeric($number)) {
		if (is_numeric($offset) && $offset >= 0) {
			$this->limit = intval($offset).' , '.intval($number);
		} elseif ($number >= 0) {
			$this->limit = intval($number);
		}
	}
}
```


@klq I've completed Assignments 0-3. I'm ready to submit it for review.


No worries.  For future reference, if you add a dependency, use "npm
install --save module-name" and it will automatically add it to the deps
list in package.json.

On Sat, Mar 12, 2016, 9:45 PM Richard Petrie <notifications@github.com>
wrote:

> Oops My fault.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/2016-ksu-cis-open-house/tree-display/commit/f56eefeb5d23b981cc0b531bc37460500d71e06f#commitcomment-16665677>
> .
>


idea for tournament or using for in game
During the start of you and your opponents turn begins after you have drawn, but before you have attacked, you gain 3 turn counters to activate these power ups depending on how many you have;
• 5 counters or more: before you draw you can remove 3 counters but cannot draw at the start of your turn, but you can add an ace of your choice from your deck to your hand and shuffle, but cannot use it until your next turn, or if you cannot add an ace, you can gain 5 points instead,

• 10 counters or more: if you have any hearts in your power zone you gain an extra 2 points per heart in the power zone per turn

• 12 counters or more: by removing 4 counters, if you have a spade in the field zone or power zone, your opponent’s field cards loose half of the attack and defence for 1 turn, this can only be done once per turn.
-Tag team, If this is a tag team match all your opponents cards loose half of their attack and defence.

• 15 counters or more: you can remove 3 counters to have one card of your choice attack twice during your turn only. The card you choose gains +3 in attack only.

• 20 counters or more: You can only during your turn remove 7 counters to discard all cards from your opponents hand to the used area.
Tag team - If you are in a tag team match both of your opponents lose all their cards in their hand.

• 24 counters or more: you can remove 10 counters to remove 10 cards from your opponent’s deck and your opponent loses 10 points of their points.


This function should be rewritten:

1. The moments passed to this method are not canonical moments, while the condition tested here is in terms of canonical moments. The conversion must happen in the method itself.
2. The name of the argument should be "moments" for consistency with the other implementations, and not changed to p.
3. There are some errors in the expressions (see other comments), and Yuan et at. (2012) for the correct expressions.
4. Some return and assignment lines do not follow the style of the rest of the code (unneeded parentheses).


condition = (p[1] + p[2] - p[1]*p[2])/(1.0 + p[2])


Good to see you're still working w/the source... (Though I've taken a bit of time off, I've got a lot of stuff in the works...off on a branch though, trying to work through a lot of things).  Perhaps you could stop by chat with an update on whatever you're up to these days.

There are a couple of things I hit when I merged this, and I've patched them--notes [in the commits](https://github.com/metaeducation/ren-c/commits/master).  One thing is that this prototype was extern'd over in %a-lib.c, which still had the old prototype.  Same for the change to `RXI_To_Value`  It didn't give a compiler error in C, but the C++ build does name mangling *(well, as long as you don't say `extern "C"`)* so it picked up on the problem.

Anyway, no worries, not much trouble to fix.  But there are some things having a working C++ build does, so good to keep an eye on the travis-ci to make sure it's still green:

https://travis-ci.org/metaeducation/ren-c


What? Why?


(͡° ͜ʖ ͡°)


Search-replace much? Intentional?


Ya, @AbrarSyed needs to take a look at it seems some excs arnt being added....


良いですね！

バリデーションに関しては、
・フォームのバリデーション(クライアント側)
・データベースでのバリデーション(サーバー側)
の2種類があるので、余裕があれば両方実装してみてください！

バリデーションがサーバー側のみだとユーザーが正しくない形式のデータを送っても気づかない(正しい送ったつもりがデータベースに保存されていない)ということになったり、

逆に、バリデーションがフォームのみだと、フォームを介さないような方法(直接サーバーにデータを送る)をとられると不正なデータを入れられる危険性があるためです。


I think this would do better as being a specific type of `Error` so applications can detect this without having to interpret the string? Knowing specifically that "handler is not installed (yet)" would be good, as it's not an error to pass on to the user directly, for instance.