@milianw: any idea of the impact if you don't add this condition here? Adding this means that in case we are rendering a table cell with multiple lines, one of the lines might get cut in the middle, which I assume is due to `adjustLinePositionForPagination` not getting called.


Крупный баг.
При наведении на под меню, пропадает красный фон на меню.


Этот шрифт тут не примениться, так как он не в кавычках!


пробел?


@mwrock does this work fine with regular things that are not powershell?


пробел


should this be
```
- go get -u golang.org/x/tools/cmd/vet
```

So it's always the latest vet, or is that too aggressive?


Yes, something like that, although I think it should support multiple values (like `multiple-value-prog1`). See https://github.com/akovalenko/cl-postgres-async/blob/master/cl-postgres-async/async.lisp#L230


этот и верхний блок одинаковы?
Почему не объеденить?


Why not `patient.temp_serial = long(patient.serial)` in the backwards migration?


не тому элементу класс вы дали! Надо родителю у которого дети имеют float


ich meinte #25


Расставте clearfix правильно


The previous code consisted of trivial functions, the current code potentially incurs an allocation or two so I wouldn't risk it.


this breaks compatibility for the CHAN grepping with some possible configuration getting the wrong one so I'll take the rest and do this differently


@Kinzcool 6.1.0 - ptr ?


@ThomasKolarik: Interesting. Maybe you should add 2 more parameters for the constant (0.00 for PV nodes and 0.33 for non PV nodes). SPSA seems to have no problem with larger number of parameters.


good work

i'll try a few things based on what you did here before deciding what / how to merge this one


Thanks! BitHub has sent payment of  $9.59USD for this commit.


Are you using modified bindings for `<leader>tg` or `C-\` to take advantage of this more capable git-hscope?


Pensé que no volvías en todo el día, y le di UNCLAIM a la tarea, y escogí otras..


I actually changed that in the release 0.2.0
https://github.com/angular-ui/ui-ace/blob/src0.2.0/src/ui-ace.js#L227-L261

Is it still occurring ?


It is a mutable operation, so will definitely fail on a SigleElementVector. `div` should work of course. Assuming you are using a `SparseXXXMatrix`, then you need to use `getRowView` or `getColumnView` to ensure that you get a mutable representation of the sparse matrix row or column. `getRow` and `getColumn` aren't required to return a mutable view, so they *may* return an immutable vector for efficiency purposes.


I don't answer to you. However, I'm open for review if you're being helpful and not trying to force your opinions as the be all end all.. but fundamentally, you take this way too seriously for anyone else to have fun. Trying to turn everything into a pissing match and trying to forcefully assert control when you could let well enough alone is what's wrong. I don't care for it and neither does anyone else.


It would be good to make "/home/lvuser/" a static final variable in this class, so we can easily change where the file is read from.

Or! We could make a more generic PropertyReader class that this could be a subclass of.


Added hello.c


looking at http://java.com/en/download/help/silent_install.xml i am thinking maybe we should try the `start /w` they're mentioning instead of `nohup`, but i admit i haven't checked its viability under cygwin before typing this


The quotes will have to be changed to double quotes because PHP doesn't substitute variables when literal quotes are used


Dollar sign here $$$


develop (lefticus) - Win64-Windows-8.1-VisualStudio-12: OK (331 of 331 tests passed)

![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)


again an report for non working sdcard1 .. just non showing the music on the player.... i'll revert this modules too... thanks..  @mkaluza i think u can also revert this on your kernel.. should be the same.


we can delete select_url, because it's integreated into createurl.php


nice


I should clarify...it may be that we will want to read more .properties files than just robot.properties, so we may want to have the file-reading process be more general. Making a PropertyReader subclass would let us create other classes to read .properties files very quickly and easily.


C'est dégageant pour toi de de faire un simple import et non un import as. simplement pour la suite ça permet de savoir exactement dans le code quel est la lib de référence. (je trouve ça un peu plus propre)
De plus en général les gros modules comme ça on leur laisse une majuscule en première lettre.


test


One more thought about standardization. I left JavaScript (twice) for two reasons:

1. Its component tools weren't intended for building app-like experiences. They're getting there. But they're still a mess.
2. More importantly its community is the most fragmented mess I've ever mucked with. I'm a proponent of diversity but look how many MVCs have a thousand stars on GitHub? They're not unifying around a few standard solutions.

Scala by contrast made leaps in building its platform by endorsing its community. It jettisoned futures (there were several alternatives), was talking about XML and JSON too, and incorporated a web framework from de facto third party libraries. I wonder whether collections won't undergo a similar renaissance.

The benefit I see of your libraries living together in a single discoverable organization that looks like it's committed to being maintained (as opposed to your general purpose user account) is to unify a community. Everyone agrees all the `Box` and `Result` are ridiculous. But drawing inspiration from Underscore for collections (no offense to Dollar) doesn't attempt to address the root like Traversal does ( I haven't finished scrutinizing it). Either is a microframework for micfoframeworks (a popular one). Memo object-ifies laziness for an otherwise eager language. Prelude's application operators get implemented half as often as linked lists without the domain knowledge you invested in them. In the same way I feel more confident in ReactiveCocoa than various promise or deffered (BNR) implementations.

That's what LlamaKit is already doing and why I asked whether you considered talking to him. What if the leading thinkers in this burgeoning community had a forum to argue out solutions instead of reinventing them? I know migrating a few projects to a common org won't do that. But I suspect because of their minimal scope they'll keep getting rewritten otherwise.

(I reread this a few times and couldn't make it not sound like a Braveheart brogrammer speech 🙊)


Je pense que tu peux supprimer le module de "verbose" ainsi que la variable self.foo, vu qu'elle ne sont pas utilisé.


Ignore this, I fucked up. Still new to github :P


pourquoi avoir globalcon en global?


hmm


C'est as granch chose mais si tu veux tu peux gagné une ligne sur les condition ou les loop d'une seul ligne en écrivant comme ça:
for row in rows : result += ''.join( row )


ok


코드를 커밋할 때 주석은 없애주세요 :)


xD


Can you comment on why did we need this? This prevents code from being built with clang as -static-libgcc is gcc-specific.


This is a test project to get my hands on github.


코드 style은 한 스크립트 내에서는 통일하는 것이 좋음. 가령 지금은 assignment할 때 a=b, a = b 의 스타일이 혼재.
이건 글쓰기 할 때 한 문서에서 "대한민국"과 "대한 민국"이 섞여 있는 것과 같음.

파이썬 Code styling 관련 글은 [PEP8](https://www.python.org/dev/peps/pep-0008/) 참고.


all tests pass:
success: http://buildbot.rust-lang.org/builders/auto-mac-32-opt/builds/3098
success: http://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/3091
success: http://buildbot.rust-lang.org/builders/auto-mac-64-nopt-t/builds/3092
success: http://buildbot.rust-lang.org/builders/auto-linux-32-opt/builds/3083
success: http://buildbot.rust-lang.org/builders/auto-linux-32-nopt-t/builds/3083
success: http://buildbot.rust-lang.org/builders/auto-linux-64-opt/builds/3086
success: http://buildbot.rust-lang.org/builders/auto-linux-64-nopt-t/builds/3079
success: http://buildbot.rust-lang.org/builders/auto-linux-64-x-android-t/builds/3074
success: http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/2751
success: http://buildbot.rust-lang.org/builders/auto-win-32-nopt-t/builds/2749
success: http://buildbot.rust-lang.org/builders/auto-win-64-opt/builds/1587
success: http://buildbot.rust-lang.org/builders/auto-win-64-nopt-t/builds/1579


fast-forwarding master to auto = 431105a7


Prior Repo contained a bash history file. Had passwords in it. Removed that and made this one.


Weird. I'll take a look.


I can make custom flag for `getitembound` related this change. xD
such
> * 11 - item will be account bound when equipped
> * 12 - item will be guild bound when equipped
> * 13 - item will be party bound when equipped
> * 14 - item will be character bound when equipped


from selenium.webdriver.support import ui


변수명들을 전반적으로 의미 있게 잘 정했네요.
앞으로 파일명이나 폴더명도 그렇게 하면 좋을듯!


I added this to circumvent some problems with older Linux distributions. Now I'm compiling on a really old system myself instead.


I've corrected issues with this commit in #134.


saw approval from Aatch
at https://github.com/dotdash/rust/commit/6f1b06eb6546ab4808614dfe7807277419b485aa


merging dotdash/rust/fca = 6f1b06eb into auto


status: {"merge_sha": "694370a529bf4877ed163b5706ea285e855628fe"}


dotdash/rust/fca = 6f1b06eb merged ok, testing candidate = 694370a5


need to do capacity / 4 (because of overflow


need to check for max value + only resize until capacity fully reached.


Where will this comment show up?


This is not showing in RELENG_2_2 branch.


Wow. That was a fun work day -_-


check for overflow, return error otherwise


No problem! I'm finding all these little details with the testing.


I'm confused about this attribute. Looking at the code it's a getter and a setter of a list, but I don't understand what is supposed to be the source or destination.

So it gets the blend mode of the first material on the object and it sets all materials of an object to a specific blend mode. I think this is not the way to do it. Much better to just get the material of the object and change whatever has to be changed about the material.

This is what I had in mind. Not only logical, but more practical in my opinion.
```javascript
mesh.materials.get(material_index).someAttribute(some_value);
```
or
```javascript
mesh.materials.get(material_name).someAttribute(some_value);
```
or
```javascript
for (Material m: mesh.materials) {
   m.someAttribute(some_value);
}
```
and
```javascript
boolean some_value = mesh.materials.get(material_index).someAttribute();
```


这样子一个录像能缩小多少？


Could you please share your `AndroidManifest.xml` ?


Smells like insubordinate hubris. Get over it. The fact that you even need
to widen my opinion with "anyone else" or "everyone" is just indication
that you need to eat one of the pieces of humble pie I've offered you. Nom
nom mom, Dave.

On Sat, Jan 10, 2015, 9:13 PM Dave Kessler <notifications@github.com> wrote:

> I don't answer to you. However, I'm open for review if you're being
> helpful and not trying to force your opinions as the be all end all.. but
> fundamentally, you take this way too seriously for anyone else to have fun.
> Trying to turn everything into a pissing match and trying to forcefully
> assert control when you could let well enough alone is what's wrong. I
> don't care for it and neither does anyone else.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/VanirAOSP/build/commit/c609c40c199eaeecb4deb4cd9885dabc72d46663#commitcomment-9231917>
> .
>


Widen your*****

On Sat, Jan 10, 2015, 9:44 PM Eric McCann <nuclearmistake@gmail.com> wrote:

> Smells like insubordinate hubris. Get over it. The fact that you even need
> to widen my opinion with "anyone else" or "everyone" is just indication
> that you need to eat one of the pieces of humble pie I've offered you. Nom
> nom mom, Dave.
>
> On Sat, Jan 10, 2015, 9:13 PM Dave Kessler <notifications@github.com>
> wrote:
>
>> I don't answer to you. However, I'm open for review if you're being
>> helpful and not trying to force your opinions as the be all end all.. but
>> fundamentally, you take this way too seriously for anyone else to have fun.
>> Trying to turn everything into a pissing match and trying to forcefully
>> assert control when you could let well enough alone is what's wrong. I
>> don't care for it and neither does anyone else.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/VanirAOSP/build/commit/c609c40c199eaeecb4deb4cd9885dabc72d46663#commitcomment-9231917>
>> .
>>
>


Crap ;)


Merge please.


y u do dis good?


Both are internal, so shouldn't be visible to any public assemblies.


OK just made some more changes which may help....


also mentioning debugging or working on this is a great example of seeing snapshots at work in this script:

if earlier snapshots exist, it will use them, which means:

• either this code failed, then on next run it anyway will do `installToolsIntoTestVm()`

• or if this code succeeded, then if deleting snapshot "tools installed" and anything after it will cause `installToolsIntoTestVm()` to be done again

big time saver not having to wait for repeated install of OS to get to tools install

if not wanting to deal with snapshots from VMware UI, there is in NrvrCommander class `VMwareHypervisor` a method `revertToSnapshotAndDeleteDescendants`, which you'd call with the previous snapshot, i.e. `"OS installed"`


I'm going to alter javac() func as follows:

```python
def javac(srcdir, trgdir=".", cp=None, javacVersion=None, version=None, args=(), skip=()):
    global ERRORS
    srcdir = uniformpath(srcdir)
    trgdir = uniformpath(trgdir)
    mkdir(trgdir)
    map = javac_targets(srcdir, trgdir, skip)
    tobuild = stale(map).keys()
    # print "build",stale(map)
    if len(tobuild) == 0:
        return
    if cp is None:
        cp = trgdir + os.pathsep + JARCACHE + "/*"
    javac = "javac" # use default system javac if no javacVersion
    if javacVersion is not None:
        javac = os.path.join(jdk[javacVersion], "bin/javac")
    cmd = [javac, "-d", trgdir, "-cp", cp, "-source", version, "-target", version] + args + tobuild
    exec_and_log(cmd)
```


This config does nothing when both crafting and inventory unification are off :P


Double quotes in Python ;)


если вы с большой буквы все цвета пишете, то тут тоже так надо тогда


Update readme.md


> I have mpc-hc:develop...0b37df3 for tonight. It would be best if it was pushed last to ease releasing the stable from 9b6cfb1 if we think 0b37df3 is too dangerous.

Fine with me. I don't think 0b37df3 is dangerous, but with hardware related issues you can never know. I just tested it and it works ok. And since it helps for others I guess it is fine. I tried to compare drive behavior speed and noise, but I can't tell if there is a difference. At first I thought after patch it stay on full speed longer, but probably it's just placebo so ignore this. In next test I couldn't see difference. But I must say it is insane to listen direct from CD it is so damn noisy, at least with my drive.

> What do you want me to do with 8e4eb9f and d7273f4? I couldn't find a way to know whether VMR-7 is using overlay but at least I could still disable the shadow when the overlay is detected.

It is not that important. Do the best you can, if only overlay renderer can be detected, fine. But don't forget to reenable if renderer is changed to something else and shadow from context menu should also be disabled. To be honest I'm not sure it is worth the trouble, but if you can make it little better, sure :)

Do you think I could push https://github.com/kasper93/mpc-hc/compare/mpc-hc:develop...develop on top? And we could release stable without it if we decide to. Or it is better to not do mess? I'm just asking. I don't want to make a problem later.


Naming convention: lang_file_name not lang_fileName


посмотрел, гуд


You have a point, that way we can preserve the data. Let me take another look.


if you want you can use `Gen.size` (or sized) and then control the size in the test


Может исспользовать правило ``` font ``` вместо этих трех?


ЗАчем?


Зачем?


сюда впишите ``` background-repeat: no-repeat ```


![plot4](https://cloud.githubusercontent.com/assets/10237417/5696551/0528715c-99a3-11e4-991a-908ed8979c70.png)

plot4.png


Shouldn't the backwards migration read `Patient.objects.update(serial=models.F('temp_serial'))`, so the serials are copied over before the `temp_serial` field is removed?


У вас иконки имеют разную высоту и ширину.
Если бы вы сделали одинаковую и подкоректировали бы спрайт было бы проще


having an issue even starting up the server because of

Traceback (most recent call last):
  File "master_server.py", line 29, in <module>
    from admin_page import AdminPageServer
  File "/home/parallels/dwc_network_server_emulator/admin_page.py", line 29, in <module>
    adminpageconf = json.loads(file('adminpageconf.json').read().strip())
IOError: [Errno 2] No such file or directory: 'adminpageconf.json'


I'll keep this for my next PR?


Testing


was


You could probably achieve this with `orm.Patient.objects.update(temp_serial=models.F('serial'))`, no? Or doesn't `models.F` work in South migrations?


Eric - It might possibly address your issue. If the IOIO is reset, the state of the heat relay is also reset... but this information isn't reported back to the Android app. I haven't worked with this code since making changes in 2013. If you remove the lines of code that I removed, make sure you watch for other unexpected behavior (like if the temperature stops updating after awhile... that seems to be the problem the original author was experiencing, and why they added this temporary reset hack).

-Adam


I'd probably wait for a specific label to make sure the action was completed.


Ha minden igaz, most nagyok a képek... :)


just getting started


missing newline, also this is something for your global gitignore.


Fine for a first iteration. As I mentioned before - the legacy code needs to be cleaned up (e.g. naming convention, fallbacks), and could be optimized a little bit. But that can wait until the next iteration.

Maybe insert a separator line #====== between the classes - we do this throughout the code to help orientation.

In general, this should be mergeable now, unless @flavour has any objections. It isn't 100%, but a significant leap forward.


Why did you included these `<a>`'s? Github automatically grants every heading an id.


The years aren't necessary and unmaintainable. We've not been including them in any h5bp project.


But then the API will not be as easy?

Can you give an example?


Left a few comments on some of the migrations.


Thanks Adam. That's helpful. I'm setting up the environment to start
playing with this code. I haven't worked much with Java. I might try
swapping this code in and seeing what happens.

I wish Zonk would have put in some comments on this code. I feel like
Sherlock trying to unravel everything.

Eric
On Jan 11, 2015 3:06 PM, "alwaysadam" <notifications@github.com> wrote:

> Eric - It might possibly address your issue. If the IOIO is reset, the
> state of the heat relay is also reset... but this information isn't
> reported back to the Android app. I haven't worked with this code since
> making changes in 2013. If you remove the lines of code that I removed,
> make sure you watch for other unexpected behavior (like if the temperature
> stops updating after awhile... that seems to be the problem the original
> author was experiencing, and why they added this temporary reset hack).
>
> -Adam
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/alwaysadam/AndroidThermostat/commit/bd6f7c3ce13bcaa97a38575ef247664a9907b64c#commitcomment-9234395>
> .
>


Hmmm, I'd drop `and` in `andProceedTitle` :wink:


Yeah, I am looking at them, thanks

On Sun, Jan 11, 2015 at 9:10 PM, Stanislaus Madueke <
notifications@github.com> wrote:

> Left a few comments on some of the migrations.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/myvoice-nigeria/myvoice/commit/8652c4342723d9f450b720b1d0d7ff559e1a5233#commitcomment-9234406>
> .
>

--
@boyombo
http://bayo.opadeyi.net
A designer knows he has achieved perfection not when there is nothing left
to add, but when there is nothing left to take away.
 --Antoine de Saint-*Exupery*


Hmmm, is `textField.` correct? I'm asking about the `.`


some tests failed:
failure: http://build.servo.org/builders/linux2/builds/513


Good accessibility labels :heart:


Hi, thanks for your effort. My comments:

I'm not familiar with Radegast servers so  I cannot test this. What versions are out there? Are they all compatible with your patch?
Is the culprit in Oscam trunk or in the Radegast server you use?

Your patch lacks any explanation, usecases and tests whatsoever. Also there are no comments from others like 'works for me in this or that situation'.  So you'll have to convince me!

Furthermore, your initial comment does not reflect what changes are made, so in the present state I won't pull anyway. Please correct the comment.

Regards,
Tycho.


r+


![plot1](https://cloud.githubusercontent.com/assets/10237417/5696599/46db2f80-99a4-11e4-8c6e-430c966aa118.png)
plot1.png


If it's labeled `Close` is it still a `DVSTitleForAlertCancelButton`? :wink:


r=nikomatsakis rollup p=1


## IntegrityCheck changes

I've changed the signatures of IntegrityCheck, IdentifiableIntegrityCheck and FullIntegrityCheck to return structured dictionaries with the errors by temporalId (an ignored Guid that identifies any ModifiableEntity in a graph) instead of a big string.

### Motivation
This change allows an interesting new scenario: Marking as red the fields that are invalid after executing a particular operation

Exaple: In Southwind you have to set mark ShipVia before executing Ship operation (that now is a non-Lite)

### How to change the code
The following Southwind commit should guide how to make the necessary changes, if any. https://github.com/signumsoftware/southwind/commit/ffa6e7b0c6bc930012486cef041432d76ed3b74f


No, that's fine -- adding `-u`.


Seems pretty broken... again?


r+ rollup


Dzięki.


Yes, it's fun :). New day, new merge :D


.githubusercontent


You can add .gitkeep to do the same


I didn't realize that you can say "put this here, and then increment it, but leave the thing you put there originally the way it was" in one word. I had all sorts of nastiness to do that, now it's all clean.


develop (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Ah, ok. Two questions then. Is it necessary that `SingleElementVector` be immutable? E.g., element-wise ops such as division make sense for a single non-zero element vector.

And more broadly, is there currently a case where an immutable vector is returned for efficiency purposes? Just trying to better understand the design.

Finally, there's `PMatrixRows` and `PMatrixColumns` for getting a seq of possibly immutable row/col vectors. And there's `PSliceSeq` for getting a seq of (mutable) vector views. However, `PSliceSeq` only supports getting a seq of slices for the major dimension. The `core.matrix` API doesn't provide seem to provide a protocol for getting non-major slice views.

In my particular use case, I'm normalizing columns in a matrix. It was convenient to use:
`
(doseq [c (columns m)]
     (normalize! c))
`


عوض خ


## ExceptionMarshalling in WPF

In order to implement the previous change (https://github.com/signumsoftware/framework/commit/68e0f7c58a102a3bc3868daf7c8b4dd6d8163967) in windows, I've found a way to send exceptions though WPF seamlessly, completely ignoring the `FaultException`.

This changes simplify sending custom exceptions from the server and catching them on the client, as well as sending any necessary information in the Data.

### How to adapt the code
The following code in Southwind should serve as a guide to adapt the code: https://github.com/signumsoftware/southwind/commit/29079c92de92d0ef29fe7894158b9d7d434788bd


One thing I change is that I'd add some waits to `KIFUITestActor (DeviseDemoTests)` to make sure appropriate view has been displayed. Minimal cost in terms of time and you'll get more granular errors if something goes wrong.


You do realize that this is still here, right?
If you want it to disappear completely, you can follow the steps here: https://help.github.com/articles/remove-sensitive-data/


No helpers :cry:


Why? A couple reasons:

- Commit messages are meant to describe what the commit is about. The intention in the commit. The changes made.
- When I write code, I am likely to _not_ remember why I did something 3+ months down the line. The commit message documents why I did something and what I did.
- This project is available to others to see. It shows off what you are learning, your approach and your skills. Following best practices (like descriptive commit messages and small/contained commits) shows you are building habits that translate well into a team environment. It also helps the people evaluating your code to more easily follow what changes you've made and why.

Hope that helps. :smile:


Moreover if I have empty tests, like in `DVSSignUpSpec` I usually add `expect(NO).to.beTruthy();` to make sure that I don't forget to implement them :wink


r+


Note the commit message where I say "change".
On Jan 11, 2015 12:20 PM, "Kevin Pelgrims" <notifications@github.com> wrote:

> You do realize that this is still here, right?
> If you want it to disappear completely, you can follow the steps here:
> https://help.github.com/articles/remove-sensitive-data/
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/JakeWharton/Telecine/commit/727ac1de7077ca28ac91947fa673c259c362782c#commitcomment-9234446>
> .
>


Duh. Forgot your `Int`s?


If you don't need any `beforeEach`/`afterEach` in a `describe` block you should probably remove it as there's no real need to keep it around :wink: unless of course there's something to be shared with a new tests. But that usually turns out when you add more tests.


This is necessary.


There's a subtle difference between `context` and `describe` that is explained [here](http://lmws.net/describe-vs-context-in-rspec).

In this case this should be `describe`. :wink:


Okay, cool. Just wanted to make sure your key was not out in the open :)


But this isn't. Methods keep being exported exactly as before.


And a `describe` block here :wink:


## Fix StateValidator

Unfortunately, a change made in April 2013 and the fact that a `LambdaExpression` has a `Name` property (...?!?!) made the line 755 in `StateValidator` incorrectly bound, creating a bug that has disabled `StateValidator` for 1 year and 9 months with nobody noticing it.

By fixing this bug, some validations will be re-enabled, potentially crashing code that before was incorrectly too forgiving.

Be careful with entities that have `StateValidator` like `EmailMessage`, `Order`, `Invoice`,...

Apologize :sweat:


We were talking about using only Java server as connection to front-end (which in turn can contact the Python server) - do you intend on changing that - as I saw you reverted this commit?

If it's a problem I guess we can for now stick with calling Python server directly, but I think it would be best to have only one central point for REST methods.


This has been bothering me for some time.  Great to see someone was proactive about it. :)


This actually has a name of `context` block. The actual test should read

> should display an alert view with error


Ouais ben... euh... J'vais rien dire.


Why have you removed UNSIGNED? Answers & views couln't be lower than 0.


That's a mistake. I will fix it in a next commit


hi @cmather, should this be working now with the latest iron-router... ie should #<anchor> take me to that spot ona meteor page marked with <a name="<anchor">?


Want to fix the documentation up above, too?


And activate translation album index / view album pages...


First test thingy


I like how you reduced the problem down to a average of 2 points problem, however you're not taking the enemy position into account in your calculation of the dimensions. I'll email you a diagram to help clear things up.


Isn't this called in top `afterEach` already?


## Migrations module!

A new migrations module has born with the commitment of simplifying your deployments.

Short description: http://www.signumsoftware.com/en/Extensions/migrations

How to enable it: https://github.com/signumsoftware/southwind/commit/c7f2be69a08e71dcca65c268a7dfe01b86e66df7

Enjoy!


Nice work :+1:


I believe you didn't mean to remove this theme.


Should be. Not working?

> On Jan 11, 2015, at 12:30 PM, adamgins <notifications@github.com> wrote:
>
> hi @cmather, should this be working now with the latest iron-router... ie should # take me to that spot ona meteor page marked with ?
>
> —
> Reply to this email directly or view it on GitHub.
>


Can be done better


Agree on idea, just one question - would it be better to merge context with existing context at the report creation time?


That's fixed in another commit in this PR


Hmm, but this line is only used in similarity code, which seem to work fine with both matchable and public patients? And as we discussed if a patient is private even the owner should not see it listed among similar patients?


Thanks for looking out!

On Sun Jan 11 2015 at 12:27:49 PM Kevin Pelgrims <notifications@github.com>
wrote:

> Okay, cool. Just wanted to make sure your key was not out in the open :)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/JakeWharton/Telecine/commit/727ac1de7077ca28ac91947fa673c259c362782c#commitcomment-9234470>
> .
>


Updated


Super nitpick, but maybe gh-pages must be wrapped in backticks.


What about this: http://kaart.maaamet.ee/wms/alus-geo?service=WMS&version=1.1.1&request=GetCapabilities ?


line 96 my $tos = $self->{properties}{packetsize};
looks to me this variable assumes the same value as packetsize which could be an invalid tos value


@GingerBear ready for working on it! :)


The only reason I did not take the enemy into account in the calculation of the dimensions was the fact that the difference between the player and the shadow will produce an especially large height, and most of the time the object of interest will be inside of the frame between the player and the shadow.


r+


Yes, it's quite complicated to describe the changes in any better way than "search for '1.8' in the template response docs" (that's why I included a link) — or "see what deprecation warnings you get".

At first I wrote a section in `ref/templates/upgrading.txt` but it didn't turn out well. It was impossible to understand without `ref/template-response.txt` and didn't add any value.


This branch refers to issue gh-6


Rather than returning `False` we should return `None` as none will indicate that the reaction was skipped. It would also be good to add that it was skipped due to the current count in the log line.


Sounds fine. Worst case is we get some tickets and have to try to clarify from there.


That could be nice. By chance, do you have a link to a code example that uses that technique?


We should log that there was an error here and maybe log the Error text as well?


Let's pause here for a second and ponder how `DVSProfileEditViewSpec` is implemented.

## tl;dr;

These tests it focus on how your object is implemented, not how it should behave. I've written quite a long article about this [here](http://www.objc.io/issue-15/behavior-driven-development.html).

## Extended version

Let's take a look on what you're trying to test. From what I can tell you're testing whether:
* Appropriate email has been entered as default email
* Behaviour of save button based on what's currently entered into email text field

Let's skip the first point as it's really irrelevant to the example.

Second point is really important as there's a much better way to implement these, with more of a focus on behaviours.

With BDD tests you should generally focus on actions that can happen with your object. On external signals that result in change of a state or propagation of action. In our case the external signal that results in an action is the `[tester tapViewWithAccessibilityLabel:DVSAccessibilityLabel(@"Save")];`. Thus to keep things clean and readable you should prepare a top-level `describe` block reading `tapping save button`.

Then I'd prepare three contexts:

```objc
context(@"when email text field is empty", ^{});
context(@"when email text field has invalid data", ^{});
context(@"when email text field has valid data", ^{});
```

When implemented like this your tests get much more logical hierarchy and are generally easier to read and understand (as they separate behaviour properly).

There's also one small thing I'd like to mention. At Taptera we've created a small extension to Specta which adds a thing called `action` block. Action block is a block that, generally speaking, works as a second level of `beforeEach`.

You might ask yourself: why the hell would we need this?

Well, the answer is simple: to get our tests as canonical as possible.

If we'd look at the most basic definition of a test structure we'd see that it consists of triple A's: Arrange (`beforeEach`), Act (???), Assert (`it`). Without action the Act block always happened in either `beforeEach` or `it` block. Which made things, well, clunkier.

In your case you'll have to put the `[tester tapViewWithAccessibilityLabel:DVSAccessibilityLabel(@"Save")];` in each test that you add to `tapping save button` block as you'll have to additional setup there.

Now imagine you have an `action` block. You could then add:

```
action(^{
    [tester tapViewWithAccessibilityLabel:DVSAccessibilityLabel(@"Save")];
});

context(@"when email text field is empty", ^{});
context(@"when email text field has invalid data", ^{});
context(@"when email text field has valid data", ^{});
```

Each of your `context` blocks would then contain ***only*** `beforeEach` blocks with code that sets up context. And assertions in `it` blocks. Which gives a beautiful structure to tests and sort of a... purity and balance. :wink:


Please never "copy" changes from another branch. If you want to get all changes to a certain commit, merge that branch to that commit. If you simply want a single commit in your branch, cherry pick it.


Should also print that there was an error here making the API call.


Why do you need the `cd` anyway?

`working_dir` is passed to the spawn command [here](https://github.com/techee/geany/blob/osx/src/build.c#L1049)


``` , sans-serif ``` где?


пробел


запятая ``` serif ``` ?


I just made heavy use of named anchors in a page I created and iron-router
seemed to handle them fine.

On Sun, Jan 11, 2015 at 3:34 PM, Chris Mather <notifications@github.com>
wrote:

> Should be. Not working?
>
>
>
> > On Jan 11, 2015, at 12:30 PM, adamgins <notifications@github.com>
> wrote:
> >
> > hi @cmather, should this be working now with the latest iron-router...
> ie should # take me to that spot ona meteor page marked with ?
> >
> > —
> > Reply to this email directly or view it on GitHub.
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/EventedMind/iron-router/commit/65b844eb0d988d93b1ac8a5bf54966d4dd2f0c46#commitcomment-9234501>
> .
>


all tests pass:
success: http://buildbot.rust-lang.org/builders/auto-mac-32-opt/builds/3108
success: http://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/3101
success: http://buildbot.rust-lang.org/builders/auto-mac-64-nopt-t/builds/3102
success: http://buildbot.rust-lang.org/builders/auto-linux-32-opt/builds/3093
success: http://buildbot.rust-lang.org/builders/auto-linux-32-nopt-t/builds/3093
success: http://buildbot.rust-lang.org/builders/auto-linux-64-opt/builds/3096
success: http://buildbot.rust-lang.org/builders/auto-linux-64-nopt-t/builds/3089
success: http://buildbot.rust-lang.org/builders/auto-linux-64-x-android-t/builds/3084
success: http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/2761
success: http://buildbot.rust-lang.org/builders/auto-win-32-nopt-t/builds/2759
success: http://buildbot.rust-lang.org/builders/auto-win-64-opt/builds/1597
success: http://buildbot.rust-lang.org/builders/auto-win-64-nopt-t/builds/1589


fast-forwarding master to auto = 32ddbb82


![plot1](https://cloud.githubusercontent.com/assets/9536416/5696764/404283c4-99a1-11e4-8b1f-72ef83935c0f.png)
![Uploading plot2.png . . .]()
![Uploading plot3.png . . .]()
![Uploading plot4.png . . .]()


аттрибут ``` download ```


idk what this is


Lyckades inte få med något "commit message" när jag pushade filen till GitHub, men där skulle stått, att detta är början på server filen och att jag känner till några buggar, än så länge :-)


Ok, I guess that's fine then. We can take another look at it if it causes any problems in the future. Another thing you may want to consider in the code is at lines 48 and 117 you're calculating spriteScale. This can also me done but doing oPlayer.spriteScale, that way it will stay up to date if we decide to resize the player at any point.


где правило ``` clear ``` для этого плавающего элемента?


sure https://github.com/julien-truffaut/Monocle/blob/master/test/src/test/scala/monocle/TestUtil.scala#L62-L80


Неверно написаны правила для каждого спрайта. Переделайте.
Надо создать класс в котором указать урл и остальные правила для спрайта, потом добавить этот класс каждой иконки в html. А иконкам задать только правило по которому они отличаються. Это ``` background-position ```


Great work!
A couple of items:
1. Line 320 of the .cfg file has packer as the username. We use vagrant.
2. We should add BvSshServer to _packer_config.cmd as well.


Advantages: the usage of the `prepend` method to prepend any required script or style is really useful. Also it allows us to esaily change between themes if they have the same blocks defined. Maybe I'll add some other templates based on this one but with some other viewblocks defined like a "sidebar" or a "footer" one.

Disadvantages: none for the moment..


In general, I think it's better to add new tests, instead of changing old ones. Changing old tests might remove a hidden test case, whereas adding a new test file can only improve our test suite.


yes thank


I'm not sure. Those aren't small things and they are in quite critical parts. @XhmikosR: Opinions?

Also @XhmikosR could you push you stuff so that I can push mine?


Также для 7мого задания не выполнено условие задания, что бы блоки "плавали" при уменьшении/увеличении размеров окна


Yes, I confess. Let's give credit where it's due!


saw approval from nikomatsakis
at https://github.com/eddyb/rust/commit/474872160a49e4048e5017f0bbb8d93d19267b9a


merging 10 batched pull requests into batch


status: {"merge_sha": "3a51b6737c8788bda2b888d83128790a1b78ab41", "rollup_pulls": [[20415, "474872160a49e4048e5017f0bbb8d93d19267b9a"], [20892, "074d9a679e751f5dcc0a67ffd313a1bf63585515"], [20899, "8af47508e9dcc9537468989ccf7f656024ead176"], [20903, "514497e347afa9e8e2d1766a9fd6c3e11511e2b1"], [20905, "6c9bdf2a11268325485478fbe3b1565c61098b05"], [20915, "c05338793b39539121ce9117d1b341d6529948ba"], [20920, "0568464d365266d583e3562835fcdb2be4cc7860"], [20926, "da15417b9d7d53cb24758d034a48cae4f4569215"], [20934, "6f45cb493ecc8b09104b12b9b51d86279a14b032"], [20956, "c989bd4ab7db24699dd2f8773964e03c751d80c7"]]}


Testing rollup candidate = 3a51b67

**Successful merges:**

- #20415 rustc_typeck: unify expected return types with formal return types to propagate coercions through calls of generic functions. (eddyb/unify-expected-return = 474872160a49e4048e5017f0bbb8d93d19267b9a)
- #20892 Replace uint with u32 in trpl/guessing-game.md (CarVac/master = 074d9a679e751f5dcc0a67ffd313a1bf63585515)
- #20899 fix shootout-threadring.rs (TeXitoi/fix-shootout-threadring = 8af47508e9dcc9537468989ccf7f656024ead176)
- #20903 Fix dead link in documentation (s/task/thread/) (XMPPwocky/deadlink1 = 514497e347afa9e8e2d1766a9fd6c3e11511e2b1)
- #20905 Fix: GNU AArch64 assembler does not like @plt symbol suffix (akiss77/pr-morestack-plt = 6c9bdf2a11268325485478fbe3b1565c61098b05)
- #20915 Add ExactSizeIterator impls for Hash{Map, Set, Table} (csouth3/hash-iters = c05338793b39539121ce9117d1b341d6529948ba)
- #20920 Give mmap a page-aligned stack start address (piyo/issue-20853 = 0568464d365266d583e3562835fcdb2be4cc7860)
- #20926 Hepburn romanization of さようなら (xnil/patch-1 = da15417b9d7d53cb24758d034a48cae4f4569215)
- #20934 Escape a leading # in a doc comment (tomjakubowski/patch-1 = 6f45cb493ecc8b09104b12b9b51d86279a14b032)
- #20956 replace deprecated uint references with u32 in trpl/looping.md (angst7/docfixes1 = c989bd4ab7db24699dd2f8773964e03c751d80c7)


блин программист научиш програмироват?


Gotcha, I will make that change and re-commit


I'm not quite sure how this came about, but the last three commits are basically a very minor commit from me (add7c4c4b3cc040151cc83c3f599b1c1cd78bed1) + an accidental undo (8014d410c9d79c4b30bbdddfd01de58865f09881) of Johan's last commit  + a redo of that (874f22c87055a6d4c4adc20437384a1ceab41ded).


r+


yes


This will need to be squashed into the original commit.


Should we document this change somewhere, perhaps in a "list of ways that the game works differently from vanilla 3.4.3 nethack"?


nvm, just found https://github.com/thejoshwolfe/nethack/wiki/Balance-Changes


Зачем px ???


tab


Would love a brief idea of what the changes include/what you are going towards. :)


Почему так?
Зачем их подключать так?

Они предустановлены в систему!


I'm not sure if I should push the MI, lcms2 and unrar updates so close to a stable... I pushed the other 2 just now.


TeamCity Rebus :: Build & test [Build 1063](http://81.7.185.44:8161/viewLog.html?buildId=2035&buildTypeId=bt2) is now running


запятая ``` serif ``` ?


можно короче


Tule ti manjka oklepaj na koncu, zaradi česar program ne deluje. Lahko še poskrbiš, da imena držav ne bodo segala čez njihove meje.


Зачем этот файл?
georgiab.ttf


I wouldn't push the renderer patches so close unless you feel really safe about them. The rest should be OK though and they are bugfixes.


> I'm not sure. Those aren't small things and they are in quite critical parts.

Sure, I can wait. Changes itself are not that critical as they look. But sure video renderer is quite important part. And frankly I was really surprised that it is broken in such way. I guess people doesn't compare video to reference everyday :)


I'm wondering if simply just building the case together as one solid png might just be better.  I was trying not to so that it was more flexible (any case color, any logo), but I'm not sure if Coverflow view is going to play nice with the concept.  It would be easier to do, but not as flexible.  If they make a Green-Ray I'm ahead of the game, but is the future flexibility worth the extra work?


Did the double quotes break something?


asdasdca


> I wouldn't push the renderer patches so close unless you feel really safe about them. The rest should be OK though and they are bugfixes.

I guess it also depends for how long they have been out but yeah probably the safest bet would be not to update now.


lcms2 is out for a long time. MI not so much.


for issue #2


Yes, look at https://github.com/amber-smalltalk/amber/blob/master/.travis.yml where we added `before_install` as well. This is not problem of node 0.8 but of npm bundled with it by default in Travis worker. Just install newest npm 1.x as shown. It'd be a pity to say 0.8 is not supported when it works fine in it.


Fair enough. The just fix the indent please :)


Silly of me to not include the package name in error message in the first place :stuck_out_tongue:


а что там в конце???


короче можно


Оо
На 112 строке тоже отступ, чего там его не написать?


Looks fine to me, but then what do I know


во многих местах вн. и внешние отступы можно объеденить в одно правило


короче?


TeamCity Bij12 Voorgangsrapportage Natuur - LCV :: CDS BIJ12 :: Build [Build ???-64-51d88e352fcde813c4a99b8e89896a0d574a59c2](http://buildserver.geodan.nl/teamcity/viewLog.html?buildId=73725&buildTypeId=vrn_CdsBij12_Build) outcome was **UNKNOWN**
Summary: Canceled Build time: 00:00:11


пробел?


r+ rollup

Thanks!


это правило даже не примениться!


damn... did I leave that there? :) ooops ;P


kjhhgyg


Oops, thanks! So nothing else was needed?


это правило даже не применитсья!


develop (evanweaver) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


TeamCity Bij12 Voorgangsrapportage Natuur - LCV :: CDS BIJ12 :: Build [Build 2.3-SNAPSHOT-65-51d88e352fcde813c4a99b8e89896a0d574a59c2](http://buildserver.geodan.nl/teamcity/viewLog.html?buildId=73731&buildTypeId=vrn_CdsBij12_Build) outcome was **SUCCESS**
Summary: Tests passed: 58 Build time: 00:02:22


объеденить


короче ``` 999 ```


damn :) removing them in next  commit


везде записывать сокращенную запись цветов!


Ker je zemljevid preširok, seže čez rob strani. Dodati bo treba parameter `width`, da ga ustrezno skrčiš. Če hočeš imeti zemljevid, ki bo segal čez robove besedila, si lahko pomagaš z ukazom `\makebox`:
```LaTeX
\makebox[\textwidth][c]{
\includegraphics[width=1.2\textwidth]{../slike/divizije.pdf}
}
```
Podobno naredi še z zadnjim zemljevidom.


объеденить два отступа


объеденить 3 отступа


r+ rollup


I'm adding a test.

The change that should really be documented is the new return type of `get_template` and `select_template`. When I wrote 4ea43ac915e187fb0c283094504f488d5017d7ec I thought it would be sufficiently API-compatible, but it isn't.

The changes required to avoid the deprecation warning are already described in the upgrade guide. I'm adding appropriate paragraphs to the release notes and the deprecation timeline.


Props for the test


за base64 вам +

Но почему там 4 круга а не один? ониж одинаковые!


develop (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2172 of 2189 tests passed)

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


Dodawanie życia, musi dziać się na serwerze, inaczej będzie można to łatwo oszukać. Cała logika musi być po stronie serwera, klient może tylko wysyłać komendy i otrzymywać komunikaty, że coś się zmieniło.


Hey! Add your full name!


Ok, I'm not sure either what would be best. We aren't aware of big issues
with those libs though so maybe the gain isn't worth the risk.


I was just having a look at the project code and noticed you're casting $product->getCategoryIds() to an integer then attempting to access an array index on the next line.

You may not have come across an issue yet, just thought I'd give you a heads up.


This will not work, the field must be final


OK, I'll skip them for now.


все px в html убрать


r=brson rollup


This `Configuration` is mostly duplicated in `FakeClient`.  Why have it in both places?  Why not just once in `Client`?  Seems like both the real and fake implementations should have the same configuration, since that configuration is an external interface and the realness or fakeness of the client should be mostly hidden.


fixed


объеденить два отступа


I think that ws it. THat is all that is 'wrapped' in prince.c    THe link problem was do_prince_crack missing.  My VC does not have GMP, so even after I added the prince.c, I still got link error.


s/Return's/Returns


@tschaub Does the spread attribute not take care of this?


пробел


поправить везде форматирование!


OK


+++ John MacFarlane [Jan 11 15 08:10 ]:
>+++ Vitaly Puzrin [Jan 10 15 23:12 ]:
>>  Got it. Seems you already have this limit here for CLI
>>  [1]054fea7#diff-dbdf59f049d2e2bb4b14fd89abe4b308R19
>>
>>  Probably, .ASTRenderer() on package export is a bit confusing and not
>>  needed at all.
>
>It's used in the dingus (and, now, in the CLI program for --ast output).

I mean to add an xml render like cmark has, and then remove this ast
renderer.  You're right that it's confusing, because it renders a
JS object that is not actually the same as the node tree produced
by the current parser.


кароткая запись


I'm making the drive-by fix.


s/including the User/including a serialized representation of the user ?
Perhaps add an "example"?

```python
return {
    'token': token,
    'user': UserSerializer(user).data
}
```


I reworded the paragraph a bit and said explicitly to

    Check the :doc:`template response API documentation </ref/template-response>`
    for details.


It's only a letter, guys. After I look at it I think it should be lowercase since it is continuing the sentence. But it's not critical. Surely we can find more important things to argue about! :smiley_cat:


This assert is broken for some values: for example I found this one ```(1LL << 61) - 1``` (and many values below also break this assert). For these values ```100 * x``` would be bigger than ```x``` though there would be an overflow. I think the correct assert would be ```prtpos.bytes_printed <= ((size_t) -1) / 100```.
PS. Sorry for the delayed comment, I found that code slightly before merge and I needed the time to prove my assumption.
PPS. Though it is not the problem nowadays, but it could be a bug in the far future :-)


Многое не сходиться с первоначальным макетом.


Hej,
dodawanie zycia do bazy danych i tak sie dzieje na serwerze, po stronie
klienta tylko dziala timer, ktory sie uruchamia co 5 minut i wysyla request
na serwer do zapisu.

Czy timer tez musi byc po stronie klienta?

W jaki sposob to mozna oszukac?

2015-01-11 22:19 GMT+01:00 Wojciech Mielczarek <notifications@github.com>:

> Dodawanie życia, musi dziać się na serwerze, inaczej będzie można to łatwo
> oszukać. Cała logika musi być po stronie serwera, klient może tylko wysyłać
> komendy i otrzymywać komunikaty, że coś się zmieniło.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Maciejfsafew/TWO_game/commit/3025651bfdb31b797cfe8993fbefca166aa09fc5#commitcomment-9234655>
> .
>


co 5 sekund*

2015-01-11 22:27 GMT+01:00 Taras Melon <praca.taras@gmail.com>:

> Hej,
> dodawanie zycia do bazy danych i tak sie dzieje na serwerze, po stronie
> klienta tylko dziala timer, ktory sie uruchamia co 5 minut i wysyla request
> na serwer do zapisu.
>
> Czy timer tez musi byc po stronie klienta?
>
> W jaki sposob to mozna oszukac?
>
> 2015-01-11 22:19 GMT+01:00 Wojciech Mielczarek <notifications@github.com>:
>
>> Dodawanie życia, musi dziać się na serwerze, inaczej będzie można to
>> łatwo oszukać. Cała logika musi być po stronie serwera, klient może tylko
>> wysyłać komendy i otrzymywać komunikaty, że coś się zmieniło.
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/Maciejfsafew/TWO_game/commit/3025651bfdb31b797cfe8993fbefca166aa09fc5#commitcomment-9234655>
>> .
>>
>
>


timer po stronie serwera*

2015-01-11 22:27 GMT+01:00 Taras Melon <praca.taras@gmail.com>:

> co 5 sekund*
>
>
> 2015-01-11 22:27 GMT+01:00 Taras Melon <praca.taras@gmail.com>:
>
>> Hej,
>> dodawanie zycia do bazy danych i tak sie dzieje na serwerze, po stronie
>> klienta tylko dziala timer, ktory sie uruchamia co 5 minut i wysyla request
>> na serwer do zapisu.
>>
>> Czy timer tez musi byc po stronie klienta?
>>
>> W jaki sposob to mozna oszukac?
>>
>> 2015-01-11 22:19 GMT+01:00 Wojciech Mielczarek <notifications@github.com>
>> :
>>
>>> Dodawanie życia, musi dziać się na serwerze, inaczej będzie można to
>>> łatwo oszukać. Cała logika musi być po stronie serwera, klient może tylko
>>> wysyłać komendy i otrzymywać komunikaty, że coś się zmieniło.
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/Maciejfsafew/TWO_game/commit/3025651bfdb31b797cfe8993fbefca166aa09fc5#commitcomment-9234655>
>>> .
>>>
>>
>>
>


nit: Extract this `[self valueForKey:@"_isSuspended"]` out into a private method like `-qck_isSuspended`.


It's really great to have 8 eyes instead of 4 (we both wear glasses :wink:). Thanks Remo!


Actually `Configuration` doesn't even need to be in the instance (it is static anyway).  Fine / better for it to be at the top level.


Oh, like this:

```js
registerSuite ({
    name: "deliteful/Button (bidi)",
    setup: function () { ... }
        markup: {
           beforeEach: function () { ... },
             ... // part 1
        },
        "dyn. changes": {
           beforeEach: function () { ... },
           ... // part 2
       }
});

```


Ker je zemljevid preširok, seže čez rob strani. Dodati bo treba parameter `width`, da ga ustrezno skrčiš. Če hočeš imeti zemljevid, ki bo segal čez robove besedila, si lahko pomagaš z ukazom `\makebox`:
```LaTeX
\makebox[\textwidth][c]{
\includegraphics[width=1.2\textwidth]{../slike/USAstats.pdf}
}
```


if going to use instances, why not just pass options on the call to `FakeClient.new`?


no problem :) happens :)


Yeah, you're right, I should've thought about consistency.
I'll add it to all script tags.

The issue with github.io is that most probably if there is an update to the library, it will be forgotten to update the script file in the gh-pages branch. This could be mitigated by adding the master branch as a submodule in the gh-pages branch, although I have not put too much thought to the possible negative implications of this.


This `api_version` not in the other config.


Opps, I think I can undo the 125 to 55 change.

This is a partial fix for #1017  The other problem is there is a combo of a fixed salt and variable salt. So I will make the file with a bunch of 'fixed' salt values, but there I need to use different passwords.  So I need a new input file, and a change to the jtrtspl.dat file.


Yeah, that's closer to what I was thinking.

On Sun, Jan 11, 2015 at 4:28 PM, JP Slavinsky <notifications@github.com>
wrote:

> if going to use instances, why not just pass options on the call to
> FakeClient.new?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234717>
> .
>


Excellent, thank you very much.  I will update this shortly.  Would you like to be listed as a contributor?  If so, how you would like to appear?

Thanks,
Chuck


I'm debating whether or not that even matters, since it's a fake.  Changing
the underlying API shouldn't affect any of Client's class methods, right?

I also don't like the magic string, so I was going to change that.

On Sun, Jan 11, 2015 at 4:29 PM, JP Slavinsky <notifications@github.com>
wrote:

> This api_version not in the other config.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234721>
> .
>


Very cool! Thanks a lot for the inputs @megawac and @samccone - I'll work on this later on tonight :)


`options[:headers] ||= {}`


:gem:


Can be refactored to:

.mui-rasied-button,
.mui-flat-button {
 ...
}


Oh, I just noticed that this breaks follow-mode. Enable follow-mode in some source, it doesn't work. OTOH control up/down still works.

This seems to be caused by solely by the select-frame-set-input-focus call.


Le :crown: du css :art:


TeamCity Bij12 Voorgangsrapportage Natuur - LCV :: CDS BIJ12 :: Build [Build 2.3-SNAPSHOT-66-928a03f51962322fa7f72eabfd9e69f973b170b2](http://buildserver.geodan.nl/teamcity/viewLog.html?buildId=73733&buildTypeId=vrn_CdsBij12_Build) outcome was **SUCCESS**
Summary: Tests passed: 58 Build time: 00:01:50


Got it. I'm glad you used args[0] then. :)


good job with the changes


It looks like `_str_returns` differs from `_str_param_list` ever so slightly. I don't know what motivates the difference. Should I parameterize `_str_returns` instead?


TeamCity Rebus :: Build & test [Build 1063](http://81.7.185.44:8161/viewLog.html?buildId=2035&buildTypeId=bt2) outcome was **FAILURE**
Summary: Tests failed: 2, passed: 696, ignored: 45 Build time: 0:0:2
### Failed tests
```
Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveMessageWithHeaders: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveSimpleMessage: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

```


TeamCity Rebus :: Build & test [Build 1064](http://81.7.185.44:8161/viewLog.html?buildId=2036&buildTypeId=bt2) is now running


That feel when removing ugly code.


This doesn't actually include the tweaks for scope.areAllSelected


Hopefully this will help somebody


Ah! Good catch!

It looks like the difference between assuming that if the docstring is only one part (no ':') of it being a _name_ vs being a _type_.  You are completely right that `_str_returns` should be paramaterized.


Did you mean for this to be italic? Does not seem to follow the other components.


1. Validate presence of name.
2. Validate github address.


It appear again. This is mistake in DB in GO spawn time. No one did it. So time there about a week. I remember chane this thing long time ago in my DB.


Every API method in this gem is going to have these same three lines (or at least two of them).  Also the structure of the `@oauth_token.request` is going to repeat. Why not just bury these in a local `request` method?

```
def create_multiple_choice(identifier, resource, trial, answer)
  response = request(
    :post,
    "events/platforms/multiple_choices",
    accept: true,
    authorize: true,
    body: { blah }
  )

  JSON.parse(response.body)
end

def request(method, endpoint, options)
  options[:headers] ||= {}
  options[:headers]['Accept'] = "application/vnd.exchange.openstax.#{@api_version}" if options.delete[:accept]
  options[:headers]['Authorization'] = "Bearer #{token}" if options.delete[:authorize]

  @oauth_token.request(
    method,
    "#{server_base_url}/api/#{endpoint}",
    options
  )
end
```


@hai-cea No it doesn't have to be, for my application I wanted it Italic but I probably should've moved that out of the PR.


Na základě předchozích údajů **byla** vytvořena testovací matice, tedy varianty **prostředí, ve**


Poskrbi, da bodo imena lepo čitljiva. K parametru `pos` lahko podaš vektor vrednosti - torej za vsako mesto svojo vrednost. Podobno velja tudi za parameter `offset`.


It seems to cause some other strange effects I can't reproduce all the time.


We need to add a shadow register that triggers display sync when line 162 is reached when dma enable is ticked on before 162 but *not* running for that frame.


`http://niki.zone` without slash would be enough... :)


what is this for?


Nit: *length*, also for next line.


Btw `\r\n|\r|\n` can be shortened to `\r?\n|\r` :)


I thought about that, and after looking at how it was done in the original
I decided that it was too confusing to have that much redirection in all
the option hashes, etc.  I had to dig into oauth.request to figure out how
to use the high-level request method anyway, so what was the point really?

On Sun, Jan 11, 2015 at 4:44 PM, JP Slavinsky <notifications@github.com>
wrote:

> Every API method in this gem is going to have these same three lines (or
> at least two of them). Also the structure of the @oauth_token.request is
> going to repeat. Why not just bury these in a local request method?
>
> def create_multiple_choice(identifier, resource, trial, answer)
>   response = request(
>     :post,
>     "events/platforms/multiple_choices",
>     accept: true,
>     authorize: true,
>     body: { blah }
>   )
>
>   JSON.parse(response.body)
> end
>
> def request(method, endpoint, options)
>   options[:headers] ||= {}
>   options[:headers]['Accept'] = "application/vnd.exchange.openstax.#{@api_version}" if options.delete[:accept]
>   options[:headers]['Authorization'] = "Bearer #{token}" if options.delete[:authorize]
>
>   @oauth_token.request(
>     method,
>     "#{server_base_url}/api/#{endpoint}",
>     options
>   )
> end
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234771>
> .
>


Just make the get_proxy_renderer call do what the method did? ``PathEffectRenderer([path_effect], renderer)``?


For testing with ActiveRecord. This isn't a Rails app so we don't use a database.yml file, and we really only want an in-memory database for quick tests.


Sorry for not replying quickly now that a rash of interest has popped up, but I'm on holiday. I'll reply properly next week.

The reason I chose get is to match the naming of Supplier<T> — except that this function "supplies" an exception, not a return value. Supplier uses get, so that's what I chose. I'm happy to rename it if people feel strongly about a different name.

> On 11 Jan 2015, at 19:37, Marc Philipp <notifications@github.com> wrote:
>
> How about call as in java.util.concurrent.Callable or run as in java.lang.Runnable?
>
> —
> Reply to this email directly or view it on GitHub.
>


I don't know if `clear_client` makes all that much sense to an outside user.  They shouldn't know that the underlying worker is lazily instantiated (which this method name kind of leans on).  The point is that an outside user needs to call this method whenever they change the gem configuration, so I think `reload`, or `reload!`, or `reload_configuration` makes more sense.


I also think that adding flags for headers, authorization, etc. is
basically hiding that fact that the code isn't the same in all cases...

On Sun, Jan 11, 2015 at 4:48 PM, Kevin Burleigh <klb@kindlinglabs.com>
wrote:

> I thought about that, and after looking at how it was done in the original
> I decided that it was too confusing to have that much redirection in all
> the option hashes, etc.  I had to dig into oauth.request to figure out how
> to use the high-level request method anyway, so what was the point really?
>
> On Sun, Jan 11, 2015 at 4:44 PM, JP Slavinsky <notifications@github.com>
> wrote:
>
>> Every API method in this gem is going to have these same three lines (or
>> at least two of them). Also the structure of the @oauth_token.request is
>> going to repeat. Why not just bury these in a local request method?
>>
>> def create_multiple_choice(identifier, resource, trial, answer)
>>   response = request(
>>     :post,
>>     "events/platforms/multiple_choices",
>>     accept: true,
>>     authorize: true,
>>     body: { blah }
>>   )
>>
>>   JSON.parse(response.body)
>> end
>>
>> def request(method, endpoint, options)
>>   options[:headers] ||= {}
>>   options[:headers]['Accept'] = "application/vnd.exchange.openstax.#{@api_version}" if options.delete[:accept]
>>   options[:headers]['Authorization'] = "Bearer #{token}" if options.delete[:authorize]
>>
>>   @oauth_token.request(
>>     method,
>>     "#{server_base_url}/api/#{endpoint}",
>>     options
>>   )
>> end
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234771>
>> .
>>
>
>


Do outside users need this?


Main point was, that you added big dependency (util) for that function. It's not principle for node, but can make sence for browser. Even if you need it, it would be more effective to put it into separate file and then include to cli & dingus directly. This code belongs to application level, not library level.


Using select-frame instead of select-frame-set-input-focus seems to fix the problem.


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1839](http://teamcity.monogame.net/viewLog.html?buildId=4309&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


copied from original author. fixed.


Shouldn't we need to create object from responseString and pass it to the callBack.onSuccess?
I mean this:
<pre>
Object result = parser.fromJson(responseString, methodInfo.getResponseObjectType());
callBack.onSuccess(result);
</pre>


This must be a copy/paste error because boolean is put to map for BigDecimal.


Tukaj si lahko pomagaš s funkcijo `as.Date`, ki nize pretvori v obliko, ki jo R razume kot datum. Najprej bo potrebno dopovedati, naj uporablja angleška imena mesecev:
```R
Sys.setlocale("LC_TIME", "C")
```
Potem lahko pretvorjene datume neposredno uporabiš v grafu:
```R
plot(as.Date(maraton$Datum, "%b %d, %Y"), cas, main = "Spreminjanje rekorda skozi čas",
     xlab = "Letnica maratona", ylab = "Čas v sekundah", type = "h", lwd = 5, col = "steelblue")
```
Tukaj bi seveda koristilo, če ločiš moške in ženske rekorde - bodisi z različnimi barvami, ali pa narišeš dva grafa.


Really necessary to wrap all errors in a gem error?  Can't we just let users rescue the error?  Seems verbose.


Isn't the default here 'treatments'?


`pcap_fname` is not the **f**ull**name**?

Before, we had:

    glob.glob(os.path.join(trace_dir_exp, pcap_fname[len(trace_dir_exp) + 1:-5] + '*.xpl')):

e.g.: `os.path.join('dir', 'dir/file.pcap'[4:-5] + '*.xpl')` ==> `'dir/file*.xpl`

Which is the same than:

    glob.glob(pcap_fname[:-5] + '*.xpl'):

e.g.: `'dir/file.pcap'[:-5] + '*.xpl')` ==> `'dir/file*.xpl`

No? Or there is an error somewhere else?


Yup, that's right.


Wrong documentation.


You can install the dotenv package from npm and make this `$ dotenv node server.js`.


fixed in 6920029 ... argh


I think it would be nice if we add a mock type for reading response from a local file which we may require it to be in a specific folder under assets and get just the name of it or we may let it to be anywhere and get the full path of the file.


@XhmikosR: Could you please check that the submodule works?


`pcap_fname` is the file name of the pcap file.

With
```python
glob.glob(os.path.join(trace_dir_exp, pcap_fname[len(trace_dir_exp) + 1:-5] + '*.xpl')):
```
The name is limited to sth like `traces/tcp_...`

But the problem is that we set in tcptrace the argument `'--output_dir=' + os.getcwd()`, which places the `xpl` files in the current working directory (and not in `traces`), so the program does not find them and no graph is shown


> Does the spread attribute not take care of this?

Indeed it does @hai-cea.  I should have read the code more closely :).  I made the wrong assumption when I didn't see `onFocus` or `onBlur` in the docs.  In case you want to have the docs updated, I removed the code change commits and left the doc commit in #219.  Not sure if you'd rather link to the React docs or explicitly document what gets applied with the spread attribute.


go-go-go


After you've imported the users successfully once, and moved onto the next parts, this can become tedious waiting for it to validate each user.. so I disabled it.

If you want to run this on your server, you'd best uncomment this!


I think I know now why this happens. Setting frame focus generates an input, or something like that, that breaks any sit-for. The broken sit-for in the and clause in helm-follow-execute-persistent-action-maybe causes follow-mode not to work.

I would really recommend to avoid setting frame focus in with-helm-window.


We might want to add a fallback image in case one isn't returned from Amazon.


ISBN's often contain dashes which would add to the length here. We could gsub any non-digits out here:
```ruby
length = isbn.to_s.gsub(/\D/,'').length
```


Agreed.  It will be removed.

+++ Vitaly Puzrin [Jan 11 15 13:52 ]:
>Main point was, that you added big dependency (util) for that function. It's not principle for node, but can make sence for browser. Even if you need it, it would be more effective to put it into separate file and then include to cli & dingus directly. This code belongs to application level, not library level.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/jgm/CommonMark/commit/054fea748f5b6aae9043925abf9b66991cd51887#commitcomment-9234804


I think we should always let the gem user specify the api.  Also, different API version can have different Client class methods.

On Jan 11, 2015, at 1:30 PM, kevinburleigh75 <notifications@github.com> wrote:

> I'm debating whether or not that even matters, since it's a fake. Changing
> the underlying API shouldn't affect any of Client's class methods, right?
>
> I also don't like the magic string, so I was going to change that.
>
> On Sun, Jan 11, 2015 at 4:29 PM, JP Slavinsky <notifications@github.com>
> wrote:
>
> > This api_version not in the other config.
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234721>
> > .
> >
> —
> Reply to this email directly or view it on GitHub.
>


If it is perturbing, I can change `fname` into `name`


`final`


Ok, thank you. Then it was not due to my changes :-)


Yeah, everything seems to pull fine.

On Mon, Jan 12, 2015 at 12:02 AM, Underground78 <notifications@github.com>
wrote:

> @XhmikosR <https://github.com/XhmikosR>: Could you please check that the
> submodule works?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mpc-hc/mpc-hc/commit/6e637c197d81b3e12049c63dafa8b83502e3ad13#commitcomment-9234837>
> .
>


works fine


Do we really need to duplicate verbosity constants? I'm pretty sure they exist in some interface somewhere already.


> If it is perturbing, I can change `fname` into `name`

What Kim said about that? :-D


`OutputFactory` now doesn't have any logic (not really). Can we make it an interface?


But for me, `pcap_full_path` would be better :-)


this callback already handles json conversion, that's why I didn't want to create the object in here but in the network handler.


Thanks!


@oubiwann site is open source? where can I send info if I find something?


Job pr-scala failed for d02c6da5 Took 230 min. (ping @angellandros) [(results)](https://scala-webapps.epfl.ch/jenkins/job/pr-scala/9465/):

To retry exactly this commit, comment `PLS REBUILD/pr-scala@d02c6da573938fe55f396b516d087cac6093caca` on PR 4243.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.


hopefully you used static for the internal function?


fixed


Yep, I will change that tomorrow (I will nearly forgot that I've to take my exams tomorrow :D )


Import `Player` at the top so you can just refer to it by name.


one


CSS — сила, DOM — могила.


Nice, but it looks a bit slow. ☺


Ah, never mind. Looks like you did this already...


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1839](http://teamcity.monogame.net/viewLog.html?buildId=4309&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 359, ignored: 6 Build time: 00:17:30


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1840](http://teamcity.monogame.net/viewLog.html?buildId=4311&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


TeamCity Rebus :: Build & test [Build 1064](http://81.7.185.44:8161/viewLog.html?buildId=2036&buildTypeId=bt2) outcome was **FAILURE**
Summary: Tests failed: 2, passed: 696, ignored: 45 Build time: 0:0:2
### Failed tests
```
Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveMessageWithHeaders: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveSimpleMessage: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

```


TeamCity Rebus :: Build & test [Build 1065](http://81.7.185.44:8161/viewLog.html?buildId=2037&buildTypeId=bt2) is now running


some tests failed:
failure: http://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/3102
exception: http://buildbot.rust-lang.org/builders/auto-mac-32-opt/builds/3109
exception: http://buildbot.rust-lang.org/builders/auto-mac-64-nopt-t/builds/3103
exception: http://buildbot.rust-lang.org/builders/auto-linux-32-opt/builds/3094
exception: http://buildbot.rust-lang.org/builders/auto-linux-32-nopt-t/builds/3094
exception: http://buildbot.rust-lang.org/builders/auto-linux-64-opt/builds/3097
exception: http://buildbot.rust-lang.org/builders/auto-linux-64-nopt-t/builds/3090
exception: http://buildbot.rust-lang.org/builders/auto-linux-64-x-android-t/builds/3085
exception: http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/2762
exception: http://buildbot.rust-lang.org/builders/auto-win-32-nopt-t/builds/2760
exception: http://buildbot.rust-lang.org/builders/auto-win-64-opt/builds/1598
exception: http://buildbot.rust-lang.org/builders/auto-win-64-nopt-t/builds/1590


Сделать принтскрин и наложить, очень много не совпадает!. Переделать!


/*.meta


Ln 122:
I've always used /var/log/apps/<app>/dev.log for dev as well(?)


Its temporary. Was trying to avoid clashes with John's refactor.


Translations of chapter 8 goes to branch _wheezy/08_ not _wheezy/master_.
Next time make sure and check the branch with `git branch` command, please.

Btw. best commit message I've seen on this repo so far.


I agree, we should also add this feature.


просмотрел


Alright, I'll research up on recursive general call, see what I can edit.


Probably that this pattern makes more sense to me, but Im not fussed. Module name can be changed... I'm not always clear when I should be using different naming conventions.


r+ rollup


try to make it static


ça dégage


why are accessing `:symbol_attr` as a hash key of `test_obj` here?


Nice!


regarde ce que j'ai fais sur show content


Merge branch 'master' of https://github.com/OpenCorpora/opencorpora


cool


i'm happy to see you happy to make me happy


saw approval from luqmana
at https://github.com/dotdash/rust/commit/14b6c6d153edec5731230f919eaafcb5c32959d8


merging dotdash/rust/cpu_x86-64 = 14b6c6d1 into auto


status: {"merge_sha": "e7b397b02e49ab6af5bc2a30dd04c19c38e0e266"}


dotdash/rust/cpu_x86-64 = 14b6c6d1 merged ok, testing candidate = e7b397b0


Send me sg plugin


Gecommit door mij, instellingen stonden nog ni goe na nen reinstall. Ondertussen opgelost :)


That's the same as doing `test_obj.write_attribute(:symbol_attr, "example")`, and in my mind is much more readable. Basically it sets the internal value without going through the setter method (which we've changed with `AttributeHelpers`).


r=eddyb


NVENC does support CBR. You just need to enable buffering period or pic timing SEI.


@IAmNotHanni Please do not do any merge commits. Especially ones that happen through accident


It's silly, but I had no reasonable motives. 8)
I guess, it was only a fun test.

Thanks for your great work!

P.S. MSVC produced ~40% lighter binaries (13,8 MB against 22,4 MB).
P.P.S. It seems, that you aren't providing your customers with 64-bit Windows binaries on pgmodeler webpage. I've managed to successfully build them using MSVC.


@IAmNotHanni Please (please, please, please) start using the pull request feature again


Anymore than it already was pre-merge?


Does it matter that with this the attribute isn't written to the DB in the test?


refers to issue #15


@Underground78 @XhmikosR

I completely forget to suggest porting build script changes. I mean this https://github.com/kasper93/mpc-hc/commit/c4e4b30322ac42365f155f1aa671c08ed7b915cf

Do you want me to push it or it is too late now?


`try returns nil when called on nil regardless of whether it responds to the method`

i think `.try` is the equivalent of `taxonomy.touch if taxonomy && taxonomy.respond_to(:touch)`


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Feel free to push it, it's 00:24 my time :p


I went back and forth on that. Originally I did write it to the DB and then I took it out because it wasn't really testing anything new. I'm happy either way though; let me know what you think.


What happens if `val` is not a valid class?


naslagwerk


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1840](http://teamcity.monogame.net/viewLog.html?buildId=4311&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 359, ignored: 6 Build time: 00:16:48


makes sense....


@sean97140 Thanks for the catch. I've updated accordingly, but it's still giving me the following error message: ![testerror](http://i.imgur.com/H58dakv.png?1)
http://i.imgur.com/H58dakv.png?1


Though to be honest, I'm not sure I like `$NUMBER_OF_PROCESSORS+1` but anyway I'll test it another time.


Normal users, no, which it why it defaults to the real client.  Tests, yes,
fa shizzle.

On Sun, Jan 11, 2015 at 4:52 PM, JP Slavinsky <notifications@github.com>
wrote:

> Do outside users need this?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/bca3753ad3c114527e9f610749d9573f138531b9#commitcomment-9234802>
> .
>


Such an informative error message. try pulling down a current copy of the
repository and adding your tests in one at a time until it fails.

On Sun, Jan 11, 2015 at 2:28 PM, Scott Anecito <notifications@github.com>
wrote:

> @sean97140 <https://github.com/sean97140> Thanks for the catch. I've
> updated accordingly, but it's still giving me the following error message: [image:
> testerror]
> <https://camo.githubusercontent.com/f6b1423a4a17096d1ef6c5bc3a21325ffd732106/687474703a2f2f692e696d6775722e636f6d2f48353864616b762e706e673f31>
> http://i.imgur.com/H58dakv.png?1
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/askore/capstone2014-firefoxOS/commit/4f33ad5eb691130aea3330aa38db3980d12492cb#commitcomment-9234974>
> .
>


That is extremely cool! :heart:


Really this should be only StandardErrors.  But yes, we need to wrap them
because users shouldn't need to decipher OAuth2::BlahError, etc.  We should
basically separate exceptions into two groups: ClientSideError and
ServerSideError.  Unfortunately, we don't do a good job of that because we
return 500 codes for client request errors.

On Sun, Jan 11, 2015 at 4:56 PM, JP Slavinsky <notifications@github.com>
wrote:

> Really necessary to wrap all errors in a gem error? Can't we just let
> users rescue the error? Seems verbose.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/16e2d08533da9cdcb439d2b0edf10c7370ade43a#commitcomment-9234818>
> .
>


Can you open a PR where you add the `proc` behaviour? Please test both block and proc. So nice, man!!!!


Do you want me to add `/consoleloggerparameters:Verbosity=minimal /nodeReuse:true` to make it similar as we build mpc-hc?


I am guessing it is some odd syntax error that is not showing up. But your
copy of the code is fairly behind where the project currently is, so maybe
a recent copy and small additions of your code at a time will narrow it
down.

On Sun, Jan 11, 2015 at 2:30 PM, Sean Mahan <mahan2@pdx.edu> wrote:

> Such an informative error message. try pulling down a current copy of the
> repository and adding your tests in one at a time until it fails.
>
> On Sun, Jan 11, 2015 at 2:28 PM, Scott Anecito <notifications@github.com>
> wrote:
>
>> @sean97140 <https://github.com/sean97140> Thanks for the catch. I've
>> updated accordingly, but it's still giving me the following error message: [image:
>> testerror]
>> <https://camo.githubusercontent.com/f6b1423a4a17096d1ef6c5bc3a21325ffd732106/687474703a2f2f692e696d6775722e636f6d2f48353864616b762e706e673f31>
>> http://i.imgur.com/H58dakv.png?1
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/askore/capstone2014-firefoxOS/commit/4f33ad5eb691130aea3330aa38db3980d12492cb#commitcomment-9234974>
>> .
>>
>
>


`nodeReuse` is redundant I think anyway, but sure better be consistent.


OK


As for `$NUMBER_OF_PROCESSORS+1` personally I'd use `$NUMBER_OF_PROCESSORS` to prevent disk trashing. But this is untested...


Yeah, I have a note to do this and to prefix the other category methods 👍


I was following chris' design ;)


@b4n Will have a look at it.

@elextr Because when the terminal application starts on OS X, it always starts in the home directory no matter from where you start its process.


Accordingly to the [Bencoded specification](http://www.bittorrent.org/beps/bep_0003.html), key strings should be sorted using binary comparison, not as alphanumerics. [This page](https://wiki.theory.org/BitTorrentSpecification) states the same. [Wikipedia](http://en.wikipedia.org/wiki/Bencode), however, mentions lexicographical order of dictionary keys.


Careful: this isn't a total order!


I can update the branch so it's in-sync with the master. However, the strange thing is that the same code (minus the AL call) worked in my fork from Christmas before I realized the work flow was to use branches, not forks and recently branched and added the AL calls since AL had been added.


Not used at all. I'll remove this.


Yeah I can't think of any case where not writing to the DB misses some functionality that should be tested either.


For this to work, you need to define a default constructor (see above)


To explain what happened to you:
You were working on your local changes while someone simultaneously committed changes to the repository on github.
Now at some point you decided push your changes, but since your local history and the remote one it did not work right away, so git asked you to create a merge commit (which is a commit that combines to diverging histories).
We should never let this happen. If this happens to you, please delete the entire commit message, save and quit the editor. This will cause git to abort.
Now you still want to push those changes, here is the right way to do that, first you pull remote changes:
* `$ git pull origin master --rebase` (the --rebase is preventing git from creating a merge commit and just replays your changes onto those changes which have already been uploaded)
* `$ git push origin master --ff-only`

That's it, your changes should now be online, cleanly rebased, without any merge commits.
The `-ff-only` serves only as a security, that git does not even try creating a merg commit, in case something was uploaded in the last few seconds.


Now that's just insulting!
.
.
.
Joke :D


You need a default constructor
```
Polytope() {}
```


No worries @tschaub

I think you do have a good point that we should document this better. I think linking to the react docs makes sense since there are several other events that are supported as well.


> "valid" is not really correct, it's rather "interesting". but that's not
> so big of a deal though
>

I'll reword it.


Please review this, @casey-collab


I am testing your tests now with the current code.

On Sun, Jan 11, 2015 at 2:36 PM, Scott Anecito <notifications@github.com>
wrote:

> I can update the branch so it's in-sync with the master. However, the
> strange thing is that the same code (minus the AL call) worked in my fork
> from Christmas before I realized the work flow was to use branches, not
> forks and recently branched and added the AL calls since AL had been added.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/askore/capstone2014-firefoxOS/commit/4f33ad5eb691130aea3330aa38db3980d12492cb#commitcomment-9235006>
> .
>


add `title="Total visible payments"` (or something among those lines)


oops! let's see what he thinks? @csherron ?


Hey, can you remember why this is necessary? 0.17 has been released and it's easier for distributions to pick the latest version. I.e. would you mind me bumping this to < 0.18?


![screen shot 2015-01-11 at 5 39 52 pm](https://cloud.githubusercontent.com/assets/821469/5697213/dd226f26-99b8-11e4-9897-510b556a6185.png)


> (BTW, technically we don't want to add doc comments before something is
> part of the plugin API -- but as you add it two commits later, no need to
> bother)
>
Yes, I assumed it would be applied together with the other patch (possibly
delayed by Matthew's patches and modified accordingly).


@ChronoMonochrome - this one and previous one allow it to build. Nof sure about working... will check that tomorrow...


With this on the math utils library I've done ...

#
# On unix-based platforms we need to link against "m" the maths library
# implementations
#
if(UNIX)
    target_link_libraries(math_utils logging m)
else()
    target_link_libraries(math_utils logging)
endif(UNIX)

Otherwise it will fail to build in Win32.

On a side note -- why not move maths functions into maths_utils?
You could do math_ai.c or something.


@sanecito --> wipe this branch out, get a new one in sync with the master and use this code at the end of the test file.

describe('verify GET and POST are chosen appropriately', function () {
        it('should be GET', function(done) {
            // TODO: Personal URL should be replaced with Server-side URL when server side setup
                    AL.ajax('http://ryan52.info/test.php', null, function (result, status, xhr) {
                            expect(result).toContain("GET");
                            done();
                    });
        });

        it('should be POST', function (done) {
         // TODO: Personal URL should be replaced with Server-side URL when server side setup
                    AL.ajax('http://ryan52.info/test.php', 'DATA', function (result, status, xhr) {
                            expect(result).toContain("POST");
                            done();
                    });
         });
});


I'm not sure I'm following.  The original `compiler.spawn` is `distutils.spawn.spawn` and that is exactly what we are still calling with the `spawn(cmd, search_path, verbose, dry_run)` on line 56.  Note too that `distutils.spawn.spawn` will then call the appropriate platform specific `_spawn` function.  The only thing this change does is update the `cmd` variable for OSX based compiles.  Everything else is just passed straight through as before.


It's done in batches, I haven't tried to compile yet.


TeamCity Rebus :: Build & test [Build 1065](http://81.7.185.44:8161/viewLog.html?buildId=2037&buildTypeId=bt2) outcome was **FAILURE**
Summary: Tests failed: 2, passed: 696, ignored: 45 Build time: 0:0:2
### Failed tests
```
Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveMessageWithHeaders: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

Rebus.Tests.dll: Rebus.Tests.Contracts.Transports.TestSendAndReceive<AzureMqTransportFactory>.CanSendAndReceiveSimpleMessage: SetUp method failed. SetUp : System.Configuration.ConfigurationErrorsException : Found E:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\bin\Debug\..\..\azure_connection_string.txt but it did not contain enough lines (expected 2nd and 3rd line to be storage account name and key respectively)
   at Rebus.Tests.Contracts.Transports.Factories.AzureUtil.get_CloudStorageAccount() in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureUtil.cs:line 66
   at Rebus.Tests.Contracts.Transports.Factories.AzureMqTransportFactory.GetQueue(String inputQueueName) in e:\TCAgents\buildAgent\work\4801fa25974947fd\src\Rebus.Tests\Contracts\Transports\Factories\AzureMqTransportFactory.cs:line 21

```


TeamCity Rebus :: Build & test [Build 1066](http://81.7.185.44:8161/viewLog.html?buildId=2038&buildTypeId=bt2) is now running


> As for $NUMBER_OF_PROCESSORS+1 personally I'd use $NUMBER_OF_PROCESSORS to prevent disk trashing. But this is untested...

I think we can change it later. One more worker probably ensures that CPU is used in 100% all instead of core idle in period when new compiler instance is invoked. But if you like I can change it.

Here is final version https://github.com/kasper93/mpc-hc/commit/a59f2c5748199037f29f1e740d50bb57ce3c7965 tested with x86 and x64 build. Take a look in case I missed something


What does `at this point` mean? How does an `extend` of the module (the way this was written before) try to call `instance_method` before the accessor/mutator is defined?


Comments in; mostly just clarification questions!


It looks fine and since it compiles should be good.

I'll check another time about the `+1`. I have never seen any slowdown with 8 threads on my rig but on the other hand I haven't tried `+1` to see if it actually has any gain.


:+1: to cherry-pick this


@BlueRaja this change


Heh would love to split this commit into a standalone PR to review, lots of things to say but, I would love to review in isolation of the other great work in the PR... thoughts?


Done.


The point I think is to not repeat yourself all over the place (in like 30 different method calls).  I don't think it is that confusing when there is just one method, local "request", that is handling things.

On Jan 11, 2015, at 1:48 PM, kevinburleigh75 <notifications@github.com> wrote:

> I thought about that, and after looking at how it was done in the original
> I decided that it was too confusing to have that much redirection in all
> the option hashes, etc. I had to dig into oauth.request to figure out how
> to use the high-level request method anyway, so what was the point really?
>
> On Sun, Jan 11, 2015 at 4:44 PM, JP Slavinsky <notifications@github.com>
> wrote:
>
> > Every API method in this gem is going to have these same three lines (or
> > at least two of them). Also the structure of the @oauth_token.request is
> > going to repeat. Why not just bury these in a local request method?
> >
> > def create_multiple_choice(identifier, resource, trial, answer)
> > response = request(
> > :post,
> > "events/platforms/multiple_choices",
> > accept: true,
> > authorize: true,
> > body: { blah }
> > )
> >
> > JSON.parse(response.body)
> > end
> >
> > def request(method, endpoint, options)
> > options[:headers] ||= {}
> > options[:headers]['Accept'] = "application/vnd.exchange.openstax.#{@api_version}" if options.delete[:accept]
> > options[:headers]['Authorization'] = "Bearer #{token}" if options.delete[:authorize]
> >
> > @oauth_token.request(
> > method,
> > "#{server_base_url}/api/#{endpoint}",
> > options
> > )
> > end
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234771>
> > .
> >
> —
> Reply to this email directly or view it on GitHub.
>


d


No comprende :-)

On Jan 11, 2015, at 1:52 PM, kevinburleigh75 <notifications@github.com> wrote:

> I also think that adding flags for headers, authorization, etc. is
> basically hiding that fact that the code isn't the same in all cases...
>
> On Sun, Jan 11, 2015 at 4:48 PM, Kevin Burleigh <klb@kindlinglabs.com>
> wrote:
>
> > I thought about that, and after looking at how it was done in the original
> > I decided that it was too confusing to have that much redirection in all
> > the option hashes, etc. I had to dig into oauth.request to figure out how
> > to use the high-level request method anyway, so what was the point really?
> >
> > On Sun, Jan 11, 2015 at 4:44 PM, JP Slavinsky <notifications@github.com>
> > wrote:
> >
> >> Every API method in this gem is going to have these same three lines (or
> >> at least two of them). Also the structure of the @oauth_token.request is
> >> going to repeat. Why not just bury these in a local request method?
> >>
> >> def create_multiple_choice(identifier, resource, trial, answer)
> >> response = request(
> >> :post,
> >> "events/platforms/multiple_choices",
> >> accept: true,
> >> authorize: true,
> >> body: { blah }
> >> )
> >>
> >> JSON.parse(response.body)
> >> end
> >>
> >> def request(method, endpoint, options)
> >> options[:headers] ||= {}
> >> options[:headers]['Accept'] = "application/vnd.exchange.openstax.#{@api_version}" if options.delete[:accept]
> >> options[:headers]['Authorization'] = "Bearer #{token}" if options.delete[:authorize]
> >>
> >> @oauth_token.request(
> >> method,
> >> "#{server_base_url}/api/#{endpoint}",
> >> options
> >> )
> >> end
> >>
> >> —
> >> Reply to this email directly or view it on GitHub
> >> <https://github.com/kevinburleigh75/exchange-ruby-new/commit/e19c7330a631f2198cbddde856cdc01c8fb058cd#commitcomment-9234771>
> >> .
> >>
> >
> >
> —
> Reply to this email directly or view it on GitHub.
>


No need to mention that, we merge from master to ertheia and from ertheia to master when it applies.


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-MacOS-10.9-clang: Tests Failed

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


I think prefixfree.min.js is a bit too much overhead


Nothing stopping us from passing more error information back from the server (still have to use 500s at some level tho of course)

Wish there were a more concise way to write this.

On Jan 11, 2015, at 2:32 PM, kevinburleigh75 <notifications@github.com> wrote:

> Really this should be only StandardErrors. But yes, we need to wrap them
> because users shouldn't need to decipher OAuth2::BlahError, etc. We should
> basically separate exceptions into two groups: ClientSideError and
> ServerSideError. Unfortunately, we don't do a good job of that because we
> return 500 codes for client request errors.
>
> On Sun, Jan 11, 2015 at 4:56 PM, JP Slavinsky <notifications@github.com>
> wrote:
>
> > Really necessary to wrap all errors in a gem error? Can't we just let
> > users rescue the error? Seems verbose.
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/kevinburleigh75/exchange-ruby-new/commit/16e2d08533da9cdcb439d2b0edf10c7370ade43a#commitcomment-9234818>
> > .
> >
> —
> Reply to this email directly or view it on GitHub.
>


Yes. Validated with:
```
. Start-ChocolateyProcessAsAdmin.ps1

C:\dev\test> Start-ChocolateyProcessAsAdmin -statements "C:\ProgramData\chocolatey\chocolateyinstall\NuGet.exe blah" -noSleep
[ERROR] Running C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe with
C:\ProgramData\chocolatey\chocolateyinstall\NuGet.exe blah was not successful.
Exit code was '1' Error Message: Unknown command: 'blah'
.
At C:\dev\test\test.ps1:77 char:5
+     throw $errorMessage
+     ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: ([ERROR] Running...nd: 'blah'

.:String) [], RuntimeException
    + FullyQualifiedErrorId : [ERROR] Running C:\WINDOWS\System32\WindowsPower
   Shell\v1.0\powershell.exe with C:\ProgramData\chocolatey\chocolateyinstall
  \NuGet.exe blah was not successful. Exit code was '1' Error Message: Unkno
 wn command: 'blah'
.

C:\dev\test> Start-ChocolateyProcessAsAdmin -statements "blah" -exeToRun "C:\ProgramData\chocolatey\chocolateyinstall\NuGet.exe" -noSleep
[ERROR] Running C:\ProgramData\chocolatey\chocolateyinstall\NuGet.exe with
blah was not successful. Exit code was '1' Error Message: Unknown command:
'blah'
.
At C:\dev\test\test.ps1:77 char:5
+     throw $errorMessage
+     ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: ([ERROR] Running...nd: 'blah'

.:String) [], RuntimeException
    + FullyQualifiedErrorId : [ERROR] Running C:\ProgramData\chocolatey\chocol
   ateyinstall\NuGet.exe with blah was not successful. Exit code was '1' Erro
  r Message: Unknown command: 'blah'
.
```


test