Limit the number of statements as well, or apply the query string limit to the whole batch.
Batched statements have parameters too, so we should log them (in order, until the limit is reached).


Nice! Thanks for the additional features buddy!


Sicher das du den wiki artikel im footnote haben willst und nicht eher, wie die anderen, als citation?


@dubslow just removed it


Did you test this with video/image files with an alpha channel? I have not tested it in a long time, but last time I used to set an opaque region it resulted in weird behaviors with transparent images


All changes in this class would move to the QueryLogger builder.


private method:
`_reset_counter(...)`


Такие значения типа '\u270e' лучше выносить в константы и называть их вразумительно, типа deltedIconUtfCode, т.к. я, например, юникодом в голове мыслить не умею :)


`settings.APPLICATION_SETTINGS['data_directory']` is already absolute. Give reason why it has to be processed by `abspath` again, or just use it as-is.


@gavinking : all the changes seem good to me, apart the one of `DocumentationHover` maybe.
If one Ceylon module is imported in 2 different versions, one exported and the other non-exported. Don't we risk to return the documentation of the non-exported one in some cases ? In fact maybe we should add the signature of the module, instead of its qualified name, into the doc URL location values ?
However it seems not very critical to me.


@offtools Probably better something like "using feedbacks to sync values, sliders and pages" ?


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1105
success: http://build.servo.org/builders/linux2/builds/1105
success: http://build.servo.org/builders/android/builds/1139
success: http://build.servo.org/builders/mac1/builds/1319
success: http://build.servo.org/builders/mac2/builds/1321
success: http://build.servo.org/builders/gonk/builds/287


This change also introduced the potential to break the whole application (just happened to mine, sadly).

In the old laravel/laravel's `bootstrap/autoload.php`, the `$compilePath` was hardcoded to be `__DIR__.'/../storage/framework/compiled.php';`. Upgrading laravel/framework without changing this value will just break autoloading, completely. I know, Taylor [updated](https://github.com/laravel/laravel/commit/c822db1f5bee1f8cb48d3ff2fd459a51159b00a5) the path, but this update _cannot_ be reflected in existing installations via `composer update`.

+1 to make this into a major version instead.


just remove it from here


This sequence is repeated 6 times in this .cpp file. Since you are touching this code, would you mind refactoring it into a function?


i think $BACKUP_DISABLED Should control the cronjob instead.


@sfrehse Did you try newer versions of Boost? maybe this would be an option to update directly to 1.57.0.


Последняя версия


Why do you return here? Isn't 'frame.pending' only for the front buffer?
The next line guarantees that we don't  draw into a buffer that is being displayed.


Hi Andi, I have tested your fixes.
If I am not mistaken you have swapped the TLS and SSLv3 in the code trying TLS first the last days: http://xref.dokuwiki.org/reference/dokuwiki/nav.html?inc/HTTPClient.php.source.html
This is needed for our installation since:
I have tried SSLv3 first and had a routine exit with exception for any reason. In this case the TLS line is not executed and the connection fails. => I need to have the TLS tried first.
A friend proposed another way:
Conditional call of the STREAM_CRYPTO_METHOD_SSLv3_CLIENT asking for the PHP version and only true for PHP version NOT supporting TLS.
But I don't know anything about possible side effects ..
Florian


<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="app_description">變更內置SD卡路徑</string>
    <string name="app_settings">設定</string>
    <string name="custom_internal_sdcard_path">自訂內置SD卡路徑</string>
    <string name="internal_sdcard_path">內置SD卡路徑</string>
    <string name="enable_for_apps">僅套用部分應用程式</string>
    <string name="enable_for_all_apps">套用所有應用程式</string>
    <string name="disable_for_apps">對部分應用程式禁用</string>
    <string name="enter_internal_sdcard_path">輸入內置SD卡路徑</string>
    <string name="external_sdcard_full_access">取得外置SD卡完整讀寫權限</string>
    <string name="include_system_apps">包含系統應用程式</string>
</resources>


I needed to make the new sub `<ul>` element to be shifted to the right of the currently hovered element.

So on the parent (this is the currently hovered over `<li>` element) I wrote:
```
nav ul ul li:hover {
    position: relative;
}
```

On the new `<ul>` that was originally hidden:

```
nav ul ul li:hover > ul {
    display: inline-table;
    position: absolute;
    left: 100%;
    top: 0;
}
```

To break it down, let's look at each property one by one:

`display: inline-table;` - this was necessary because the previous default setting was `display: none` which means you can't see it. You want the `<ul>` with all the new sub options to be visible when you hover over its parent `<li>`.

`position: relative;` and `position: absolute;` - this is necessary because you want to position the new `<ul>` in relation to the previously hovered-over `<li>` element. So we set the parent to `relative` while the thing we want to position (relative to the parent) is going to be `absolute`.

Why is this needed? [Read this](http://learnlayout.com/position.html).

`left: 100%;` and `top: 0;` - After we did the `position: relative;` and `position: absolute;` thing on top, we can now position our new `<ul>` in relation to its parent. Well we want it to be flush with the top, so we use `top: 0;` And we also want it to be flush with the right edge of our currently hovered-over element, so we set `left: 100%;`


fast-forwarding master to auto = 4c2ec083


The model ID is wrong:
``` sql
UPDATE `creature_template` SET `modelid1`=3167 WHERE `entry`=12423;


Seems done. Today i'm going to meet with him,  I think that's right if i first ask him.


Is this really needed? It's just `-angleToPointXZ()` after all.


Your indentation was horrendous. It was very confusing and I couldn't easily understand the structure of the elements that you were going for. Always make sure to indent everything properly so people (including yourself) can see and understand the structure clearly.


No real idea if it was a ( missing or the extra) that needed to be removed but it allows compiling while waiting for Devs to be up


:tada:


Adding sub-options to show you how to do what we will be doing next.


**all** isn't required here


Thanks!


Added even more sub-options to show you that the CSS styling is recursive. You don't need to write more CSS if you want even more sub-options.


That's why I added parameter checks in #399.


Looks good and actually simpler.


saw approval from jdm
at https://github.com/Ms2ger/servo/commit/b45cf4ccf80deb3959c78a93a174f97293985e3b


merging Ms2ger/servo/cef = b45cf4cc into auto


общие комментарии по чату:
всё неплохо, но..
- при достаточном количестве сообщений, появляется скролбар в истории, но сама история не прокручивается автоматически на последнее сообщение, которое добавляется в конец, т.е. написав что-то или получив ответ, пользователь сам должен будет искать нужные ему сообщения с помощью скрола.
- при вооде достаточно длинного сообщения, которое не влазит в 1 строчку, часть сообщения пропадает, т.к. вылазит за границы дива с историей. нужно добавить перенос текста.
- дизайн не "резиновый", размеры окна с истории сообщений и поля для ввода нового статические. т.е. на full HD мониторе занимают 1/4 экрана. остльное пространство неиспользуется и тупо залито фоном.


Ms2ger/servo/cef = b45cf4cc merged ok, testing candidate = 092a6d6f


Looks fine. But must have seen not so nice to found out and fix.


Simple enough.


+1

This commit works on Ubuntu 14.10.1


Could you expand the message to `Query not prepared, preparing before retrying executing`.


Tu viens de voler mon idée !
https://github.com/apiaget/plateforme/commit/23fe7c2b7c4062d8b40ba87d53b66dd9c3253bdf


We should recheck issue #2070 after this changes


co je totot?


use a command buf [or separate function which fills that cmd buf]:
```C
gchar cmd_buf[256];
if (stats_options_reset_is_set)
  {
     ...
  }
else
  {
    ...
  }
```


I suppose equipment code is a null terminated string and sensor data is a
byte.

static void SendSensorData(const char *code, char value)
{
MessageHeader msgh = MESSAGE_HEADER_INIT(D2G_SENSOR);
msgh.Length = sizeof(value)+ GetStringSize(code);

ResetChecksum(CHECKSUM_TX);
SendBytes((const unsigned char*)&msgh, sizeof(msgh));
SendString(code);
SendBytes((const unsigned char *)&value, sizeof(value));
SendChecksum();
}

2015-03-23 13:05 GMT+03:00 thakorjay <notifications@github.com>:

> hey,
> I want to send dummy sensor data as a notification to the server. For this
> i am using the following function.
>
> static void SendSensorData(const char *EquipmentCode,char* value)
> {
>
> MessageHeader msgh = MESSAGE_HEADER_INIT(D2G_SENSOR);
> msgh.Length = sizeof(value)+ GetStringSize(EquipmentCode);
>
>
> ResetChecksum(CHECKSUM_TX);
> SendBytes((unsigned char*)&msgh, sizeof(msgh));
> SendString(EquipmentCode);
> SendBytes((const unsigned char *)value, sizeof(value));
> //SendBytes(value,sizeof(value));
> SendChecksum();
>
> }
>
> Using this i got the data but the garbage value is coming. Can you help
> with me this function.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/devicehive/devicehive-cpp/commit/3319387fab4cee5747676aa5bf61924a8ef893cc#commitcomment-10340766>
> .
>


Сейчас написано так:
try:
    mname = str(query[0])
except:
    mname = 'None'
for StrToRem in ModelNameRemoveStr:
    mname = mname.replace(StrToRem,"")
Если в блоке try/except будет исключение то будет выполнено:
for StrToRem in ModelNameRemoveStr:
    mname = 'None'.replace(StrToRem,"")
Я не знаю что там ModelNameRemoveStr, но мне каежтся что цикл этот избыточен. Если написать так:
try:
    mname = str(query[0])
except:
    mname = 'None'
else:
    for StrToRem in ModelNameRemoveStr:
         mname = mname.replace(StrToRem,"")
В таком случае цикл for не будет запущен, если было исключение.


@bameda can I merge this?


This is missing `io->pos`.


The current scheduling in vo misses frame callbacks, so this may get executed before it would be fine to draw.


Also notice the availability of http://code.dlang.org/packages/std_data_json, which is a phobos candidate for a JSon replacement based on vibe.d.


Not sure how this keeps getting pushed


@Papillard si tu fais du Markdown, fait des lien markdown !


If see through videos are really wanted, then that case must be handled here explicitly.


## This is a markdown file


Better to move this include to Types.h


@ChiperSoft I guess it's no longer needed to make an exception for `@alias` here. It made sense when `tag.string` was itself parsed with markdown.


I had tried the same ,too.

I also used the following one:-
SendBytes((const unsigned char *)&value, sizeof(value));

But the result is same.


生命计算器


This is a very old branch. You won't be up to date


It's way more robust and reliable this way.


I would typedef this to `BaseType` then.


What if the file name has less than 3 characters?


Did not spot that one previously : !parameters.isEmpty()  is to be prefered.


This is an old branch that was pushed by mistake when I pushed the new "wizards" branch.Already removed :)


And here you can just use `*this` and `this->indexSet()`.


ack


Smart. Definitely not what was expected, but smart :)

We'll do the assignment together.


I've noticed the contents of this test no longer stick to the contents of the fixture. But by the way I noticed that these tests don't seem to be executed at all.


Why is this needed? Can this [block](https://github.com/orocos-toolchain/typelib/commit/f9b13bc2bbc2575d85f2348d124310bf651a5719#diff-778e2ae0c229bf78f0fa066013c894a8R18) be removed then?


Yes, right @jercaianu wants to add the other controls, once a first is verified.


All good.


@taylorotwell is adolf hitler and @GrahamCampbell is his sycophant!


DB Connection check

1) make DB(blueberryscone) in MySQL
2) make table(test) including id(INT), title(varchar) fields
3) run server (node app)
4) check at 'localhost:3000/test/db'


I don't think I did, auria did. And I think (I'll ask her tomorrow) that
the intention is to list all old contributors there, but leave current
ones in the more recent section - but I agree that this is not ideal,
they should all go into a 'previous contributor' section. We are still
working on the credits, so we'll have a look tomorrow.

Oh yes, sorry for the delay, I had problems with the font tool - it
compiled, but all text was rendered as a black block :(  I actually had
to download 0.8.1+dependencies in order to get the fonts done.

Cheers,
  Joerg

On 23/03/2015 5:01 PM, Deve wrote:
> It's not that important, but why you removed me from 0.8.1 contributors? :-P
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/supertuxkart/stk-code/commit/633f6c5e30aeb4e60e2bb7d238dd0d451b352449#commitcomment-10337982>.
>


You may use CheckMessagesVerifierRule and remove calls to noMore(). See https://github.com/SonarCommunity/sonar-javascript/blob/master/javascript-checks/src/test/java/org/sonar/javascript/checks/SelfAssignmentCheckTest.java


This is missing the `* 100.f`.


But it shouldn't:) all analysed files should have extension "py". But anyway you are right, i will add an additional check.


Такие вещи по другому проверяются. Через self.assert Raises


Whitespace


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13052/testReport/) for this commit**


File suffixes are configurable in SonarQube.


What you probably didn't understand at first is that the "Summary" assignment was not expected to be "merged" in the master branch. It's not meant to be a fully-fledged feature, but only an exercise. Anyway, we'll review it during the meeting.


ack.


This breaks everything. No existing Project is building after that change


I think `Vector` would be more correct than `Point` as this tends to be used to offset and existing point.


Пропущен символ в слове "Ша**б**лоны".


Does not help for on breaking builds


Опять инлайнинг стилей в html документе :(
В JS напрямую устанавлюваются значения цвета и прочие CSS атрибуты. Для этого лучше создать нужный стиль в СSS файле и назначать элементам стили.


We should be able to drop the `MAKEANGLE` here as `sin` and `cos` are supposed to be periodic anyway. Maybe in another commit though.


Gardening should go into a separate commit


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13053/testReport/) for this commit**


Is is safe to use this if I'm using the S40 credentials and not the android version like here?


I do not think using a template function here is a good idea. We can better set these attributes in `link()`.


Нравится функция uniqueId :+1:
В остально всё тоже хорошо. Разве что, как я писал, не очень выглядит задание цвета напрямую в JS


bv


```map.clicked += 1```


Haha, nice


@ishouichi アドレスとポート直打ち！


Shouldn't this be done before starting Docker?


Hello,

Can you reactive the auto flip cover control (screen turns on or off automatically with the cover)? My S-cover lost the chip and this function can't work with stock rom but it worked very well in temasek 8.x.
PS: my note 3 has random reboot after upgrading to Kitkat. I tried many roms Kitkat (including CM11), all of the tricks found on internet but the problem wasn't resolved. I'm using now your CM12 unoffical rom + lean kernel and random reboots disappear (I have always random reboots with your kernel)

Best regards,


#1 Code ignoring exception such below should be avoided
catch (Exception e) {//
 }
#2 In MDMServerDefImpl.java why using weird code with regex while java URL class provides the functionality
#3 What's the point of FILE_PATTERN_URL ? This should not be needed at all


I'll add 'enabled=yes' so it also works in case the slave reboots


Missing `* 80.f`


I am not sure if this is the best way to go. I think I would prefer loading external library CSS separately. But I do not have a good idea how to this at the moment, so nevermind.


Hey Chip, I cannot accept your pull request. The package uses the names of the csv file as report type in the adwords query language statement (getData()). Names has to be of the format with capital case and underscore separated: User_Ad_Distance_Report
See the example here:
https://developers.google.com/adwords/api/docs/guides/awql
The files you added are in lower case with hyphon separation: user-ad-distance-report
Google renamed the csv files according to the lower case hyphon separation convention. However this is not supported by the ad-hoc reporting service. This is an nonconformance within the Google Adwords API. I will find a way to cope with this. A workaround would be just to rename the new csv files.


I had the idea of i had pushed the gender force, no killyana that's not the way, it's

```sql
UPDATE `creature` SET `modelid`=3258 WHERE `id`=12423;


No, I should not. `replace` replaces the session which would change the behavior of the current `array_merge`. It's just right the way it is.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13055/testReport/) for this commit**


Huh, isn't this redundant?


very interesting :)


Damn.. I failed to notice this derp lol


localhost can even be None, which may be simpler and avoid contradictions between socket.gethostname() and getfqdn()


This is a catch of using Transifex. You get a lot of atention and translation, wich is good, but translations also get easly overwritten without further comment or discussion.
Within github the commit diffs show very easly what was modified and you can discuss it clearly, and probably it's modified by people directly involved in the software.
In this case I've alerted you, there are some confusions, some translations show a misundurstanding of WordPress syntax and use, and it certainly ain't according previous and main WordPress portuguese translation. The translations should be coherent with the WordPress core translation.
I'll keep updating from github, and I'll upload it to transifex for further refference for other translators also.


Looking at the screenshot, it appears that the NaNs are the result of a calculated indicator, so the root problem here is that calculated indicators are being persisted to the datastore. Trying to save NaNs is just a side affect of this.

Please rollback the previous commit and ensure that the data entry form does not try to persist calculated indicators. Add a test case to ensure that the following sequence works:

Field A : Quantity
Field B : Quantity
Field C: Calculated = A / B

Save a form instance with { A = 1 }
Edit the form instance, change A to 2


@rande Is the ``admin-bundle`` really no more compatible with ``knp-menu-bundle: ~1.1``  or is it a mistake ?


Don't think we do namespacing in specs like this very often, but I guess it's okay.


How to use this . Please step by Step


I'm generating it - but not calling it - should be ok?
I have had this come up with inlining in the wild too (reason for original Dynamic() fix), even without macro, so maybe still good for testing.  I would be happy too if some kind of error was generated at compile time.


Could we use `*` here for consistency or is there something preventing that? Same question two lines down.


Hér er ágæt upptalning á því hvað þarf að hafa í huga við undirbúning og skipulagningu vefs.


This change made me wonder whether my code didn't work properly before. No, it did because whatever is passed in %args overrides the default arguments anyway. So this change is kind of unneeded and confusing.

Thank you for adding docs for this module though.


Ideally we'd use radians as much as possible.


and there goes the Godwin's Law.


`Vec3f(rad)` could be just `rad`


**[phpUnit_trunkUnit run failed](http://qa-s2.wikia-prod:8080/job/phpUnit_trunkUnit/7039/testReport/) for this commit**


**[phpUnit_trunkIntegration run failed](http://qa-s2.wikia-prod:8080/job/phpUnit_trunkIntegration/6902/testReport/) for this commit**


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13056/testReport/) for this commit**


#2 & #3
regex was used to validate user input for server location definition. Before only http:// or https:// are allowed, FILE_PATTERN_URL to allow local wsdl file to be provided to Studio.


Same here - just `* rad` is fine.


Can we rename SetOrientation to SetLayoutDirection? Likewise for Orientation -> LayoutDirection.


> So this change is kind of unneeded and confusing.
Not this change actually (as it just fixes the bug), but the change by @perljedi.


The example evaluation in the commit message contains a copy-and-pasto. Correct code:

```say 10,9,8, { $_ - 1 || last } ... *```


Please keep Orientation as it is, and add Direction for these new constants. They're different concepts.


Question:
* What prevents us from expressing this directly in Quartz cron format? Is there some limitation of the Quart format we need to work around?
Comment:
* I'm wondering if this logic is correct. We assume that the numerically earliest day is the correct match, independent of the current date. However, if the day is, e.g. the 29th, and the 30th and 1st of the next month match, the 30th match would be the correct one to return.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13058/testReport/) for this commit**


I think it is more common to use Errorf for panics.


Well it's very easy to reproduce:

```
class Main {
	static function main() {
		makeNull(null);
	}

	static inline function makeNull(n:String) return n.toLowerCase();
}
```

I had a similar problem with constant propagation in the analyzer which would propagate `null` to some places and then cause a native compilation error.

I think this should just be a Haxe compilation error as I don't see what good could come of it.


@ishouichi よく意味わかんないけど、直打ちじゃなくしたよ！


The comment changed to say days moved from 0-6 to 1-7 but the regex has stayed the same? If it's changing, could we perhaps get a test to show the old regex was wrong?


I don't think this is going to give you what you're after. In the case of having something laid out bottom-to-top, the layout needs to start at the bottom of the container and work its way up. This would still be left / top aligned.


Thank you @tones111.
I have a few comments for this PR.


Does this piece of code is going to be in release of newer version?


I was not aware of this. I will update the description (I just copy-pasted the one from the ESLint `quotes` rules since they are pretty similar).

However I think the option is still accurate since you cannot escape a single/double quote in a JSX attribute you might want to allow this attribute to be surrounded by single/double quotes.


28:1: I100 Imports statements are in the wrong order. from invenio.utils.shell should be before from invenio.version


28:1: I101 Imported names are in the wrong order. Should be BlueprintAutoDiscoveryRegistry, ConfigurationRegistry, ExtensionRegistry, PackageRegistry, Registry
31:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
34:1: I101 Imported names are in the wrong order. Should be unicodifier, with_app_context
273:9: B901 blind except: statement


1: D400 First line should end with '.', not 'l'
1: D205 Blank line missing between one-line summary and description
38:1: I100 Imports statements are in the wrong order. import gettext should be before import babel
38:1: I201 Missing newline before sections or imports.
39:1: I201 Missing newline before sections or imports.
39:1: F999 redefinition of unused 'gettext' from line 38
40:1: I201 Missing newline before sections or imports.
40:1: F401 'iteritems' imported but unused
46: D400 First line should end with '.', not 'n'
64: D209 Put multi-line docstring closing quotes on separate line
64: D400 First line should end with '.', not 's'
64: D205 Blank line missing between one-line summary and description
64: D208 Docstring is over-indented
82: D209 Put multi-line docstring closing quotes on separate line
82: D400 First line should end with '.', not 'e'
82: D205 Blank line missing between one-line summary and description
82: D208 Docstring is over-indented
97: D400 First line should end with '.', not ','
97: D205 Blank line missing between one-line summary and description
116: D401 First line should be imperative: 'Return', not 'Returns'
116: D400 First line should end with '.', not 's'
116: D205 Blank line missing between one-line summary and description


1: D100 Docstring missing


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
65:1: I201 Missing newline before sections or imports.
73: D101 Docstring missing
76: D102 Docstring missing
80: D102 Docstring missing
86: D400 First line should end with '.', not 'n'
86: D200 One-line docstring should not occupy 3 lines


1: D100 Docstring missing
20:1: I101 Imported names are in the wrong order. Should be abort, current_app
21:1: I101 Imported names are in the wrong order. Should be AdminIndexView, BaseView
21:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
27:1: I100 Imports statements are in the wrong order. from invenio.ext.principal should be before from invenio.ext.sslify
30: D400 First line should end with '.', not 's'
30: D200 One-line docstring should not occupy 3 lines
49: D203 Expected 1 blank line *before* class docstring, found 0
49: D204 Expected 1 blank line *after* class docstring, found 0
49: D400 First line should end with '.', not 's'
49: D200 One-line docstring should not occupy 3 lines
57: D290 White spaces around docstring should be trimmed.
57: D400 First line should end with '.', not 'n'
70: D401 First line should be imperative: 'Thi', not 'This'
70: D200 One-line docstring should not occupy 3 lines
80: D400 First line should end with '.', not 'r'
80: D200 One-line docstring should not occupy 3 lines
88: D200 One-line docstring should not occupy 3 lines
98: D203 Expected 1 blank line *before* class docstring, found 0
98: D204 Expected 1 blank line *after* class docstring, found 0
98: D400 First line should end with '.', not 's'
98: D200 One-line docstring should not occupy 3 lines
111: D203 Expected 1 blank line *before* class docstring, found 0
111: D204 Expected 1 blank line *after* class docstring, found 0
111: D200 One-line docstring should not occupy 3 lines


52:1: I101 Imported names are in the wrong order. Should be current_app, jsonify, request
52:1: I100 Imports statements are in the wrong order. from flask should be before import requests
53:1: I201 Missing newline before sections or imports.
54:1: I201 Missing newline before sections or imports.
56:1: I100 Imports statements are in the wrong order. from invenio.utils.xmlhelpers should be before from lxml.etree


44:1: I101 Imported names are in the wrong order. Should be Bundle, CleanCSSFilter, RequireJSFilter


23:1: I201 Missing newline before sections or imports.
24:1: I100 Imports statements are in the wrong order. import warnings should be before import pkg_resources
24:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
28:1: I201 Missing newline before sections or imports.


24:1: I201 Missing newline before sections or imports.
25:1: I101 Imported names are in the wrong order. Should be _request_ctx_stack, current_app
25:1: I100 Imports statements are in the wrong order. from flask should be before import six
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
29:1: I201 Missing newline before sections or imports.
235:9: B901 blind except: statement


24:1: I201 Missing newline before sections or imports.
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.
27:1: I201 Missing newline before sections or imports.
28:1: I100 Imports statements are in the wrong order. from webassets.filter.requirejs should be before from werkzeug.utils
28:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. from webassets.filter should be before from webassets.filter.requirejs


23:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from babel should be before import six
27:1: I100 Imports statements are in the wrong order. from contextlib should be before from babel
27:1: I201 Missing newline before sections or imports.
28:1: I101 Imported names are in the wrong order. Should be _request_ctx_stack, current_app, g
28:1: I201 Missing newline before sections or imports.
29:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
33:1: I100 Imports statements are in the wrong order. from .errors should be before from .selectors
90:5: E266 too many leading '#' for block comment


22:1: I101 Imported names are in the wrong order. Should be current_app, request, session
23:1: I201 Missing newline before sections or imports.
32:9: E266 too many leading '#' for block comment
33:9: E266 too many leading '#' for block comment
36:13: E266 too many leading '#' for block comment
39:9: E266 too many leading '#' for block comment
42:13: E266 too many leading '#' for block comment
43:13: E266 too many leading '#' for block comment
46:13: E266 too many leading '#' for block comment
54:17: E266 too many leading '#' for block comment


1: D400 First line should end with '.', not 'e'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
33: D202 No blank lines allowed *after* function docstring, found 1


28:1: I201 Missing newline before sections or imports.


52:1: I100 Imports statements are in the wrong order. from urlparse should be before import requests
52:1: I201 Missing newline before sections or imports.
54:1: I101 Imported names are in the wrong order. Should be current_app, jsonify, request
55:1: I201 Missing newline before sections or imports.


1: D400 First line should end with '.', not 'n'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: E402 module level import not at top of file
33:1: E402 module level import not at top of file
34:1: E402 module level import not at top of file
35:1: E402 module level import not at top of file
36:1: F999 redefinition of unused 'MIMEMultipart' from line 35
36:1: E402 module level import not at top of file
37:1: F401 'MIMEText' imported but unused
37:1: E402 module level import not at top of file
38:1: E402 module level import not at top of file
39:1: I201 Missing newline before sections or imports.
39:1: E402 module level import not at top of file
40:1: I101 Imported names are in the wrong order. Should be EmailMessage, EmailMultiAlternatives
40:1: I201 Missing newline before sections or imports.
40:1: E402 module level import not at top of file
41:1: I101 Imported names are in the wrong order. Should be AbstractFormatter, DumbWriter
41:1: I100 Imports statements are in the wrong order. from formatter should be before from flask_email.message
41:1: I201 Missing newline before sections or imports.
41:1: E402 module level import not at top of file
42:1: I101 Imported names are in the wrong order. Should be StringIO, iteritems
42:1: I201 Missing newline before sections or imports.
42:1: E402 module level import not at top of file
43:1: I100 Imports statements are in the wrong order. from time should be before from six
43:1: I201 Missing newline before sections or imports.
43:1: E402 module level import not at top of file
45:1: E402 module level import not at top of file
46:1: E402 module level import not at top of file
47:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
51:1: E731 do not assign a lambda expression, use a def
86: D400 First line should end with '.', not 'd'
86: D205 Blank line missing between one-line summary and description
99:25: E124 closing bracket does not match visual indentation
140:8: E714 test for object identity should be 'is not'
142:8: E714 test for object identity should be 'is not'
158: D301 Use r""" if any backslashes in a docstring
158: D400 First line should end with '.', not 'y'
158: D205 Blank line missing between one-line summary and description
267:53: E502 the backslash is redundant between brackets
268:25: E128 continuation line under-indented for visual indent
268:50: E502 the backslash is redundant between brackets
268:28: E251 unexpected spaces around keyword / parameter equals
268:30: E251 unexpected spaces around keyword / parameter equals
269:25: E128 continuation line under-indented for visual indent
269:50: E502 the backslash is redundant between brackets
269:28: E251 unexpected spaces around keyword / parameter equals
269:30: E251 unexpected spaces around keyword / parameter equals
270:25: E128 continuation line under-indented for visual indent
270:44: E502 the backslash is redundant between brackets
270:31: E251 unexpected spaces around keyword / parameter equals
270:33: E251 unexpected spaces around keyword / parameter equals
271:25: E128 continuation line under-indented for visual indent
271:46: E502 the backslash is redundant between brackets
271:35: E251 unexpected spaces around keyword / parameter equals
271:37: E251 unexpected spaces around keyword / parameter equals
272:25: E128 continuation line under-indented for visual indent
272:35: E251 unexpected spaces around keyword / parameter equals
272:37: E251 unexpected spaces around keyword / parameter equals
301:24: F821 undefined name 'CFG_SITE_ADMIN_EMAIL'
301:46: F821 undefined name 'CFG_SITE_ADMIN_EMAIL'
314: D200 One-line docstring should not occupy 3 lines
325: D209 Put multi-line docstring closing quotes on separate line
325: D205 Blank line missing between one-line summary and description
428:21: E266 too many leading '#' for block comment
440:13: B901 blind except: statement
465: D401 First line should be imperative: 'Remove', not 'Removes'
465: D400 First line should end with '.', not 'n'
465: D205 Blank line missing between one-line summary and description
487: D400 First line should end with '.', not 's'
487: D205 Blank line missing between one-line summary and description


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from flask_email.backends.console should be before from .
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file


1: D400 First line should end with '.', not 'o'
1: D205 Blank line missing between one-line summary and description
27:1: E402 module level import not at top of file
28:1: I100 Imports statements are in the wrong order. from flask_email.backends.smtp should be before from .
28:1: I201 Missing newline before sections or imports.
28:1: E402 module level import not at top of file


1: D400 First line should end with '.', not 'r'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
4: L102 copyright year is outdated, expected 2015 but got 2013


24:1: I201 Missing newline before sections or imports.
25:1: I100 Imports statements are in the wrong order. from flask_registry should be before from werkzeug.utils
25:1: I201 Missing newline before sections or imports.
26:1: I201 Missing newline before sections or imports.


30:2: B901 blind except: statement
35:1: I101 Imported names are in the wrong order. Should be abort, current_app, g, render_template, request, send_from_directory, url_for
35:1: I100 Imports statements are in the wrong order. from flask should be before from werkzeug.wrappers
35:1: I201 Missing newline before sections or imports.
74:5: E266 too many leading '#' for block comment
81:5: E266 too many leading '#' for block comment
132:5: E266 too many leading '#' for block comment
164:13: E731 do not assign a lambda expression, use a def


27:1: I201 Missing newline before sections or imports.


22:1: I101 Imported names are in the wrong order. Should be current_app, has_request_context, request, session
23:1: I201 Missing newline before sections or imports.
24:1: I201 Missing newline before sections or imports.
26:1: I100 Imports statements are in the wrong order. from invenio.ext.cache should be before from werkzeug.datastructures
63: D203 Expected 1 blank line *before* class docstring, found 0
168:9: B901 blind except: statement
215:9: B901 blind except: statement
241:17: W503 line break before binary operator


@veelasky so i have lost. :)


Missing unit tests


lol


missing feature tests


import java.util.Comparator;

public abstract class Shape implements IShapes, Comparable, Comparator {
	protected String name;

	public Shape() {

	}

}
class ShapeComparator implements Comparator<Object> {
	@Override
	public int compare(Object o1, Object o2) {
		Shape h1 = (Shape)o1;
		Shape h2 =(Shape)o2;
		if (h1.getArea() > h2.getArea())	return 1;
		else if (h1.getArea() < h2.getArea()) return -1;
		return 0;
	}
	}


Hmm, why to we need the last `bash` statement at all? It looks to me as if at the very beginning of that line mintty is already instructed to start a login bash.


What the purpose of this group and what should I do in here??


Yes but you rarely need that because this library doesn't read many packages in one buffer. I use it for decrypting streams from the real app.


It should not make a difference, that's needed just for our custom wrapper
scripts for starting and stopping Docker containers which only will happen
during build jobs actually using Docker.


`setData` currently overwrites everything!
https://github.com/contao/core/blob/master/system/modules/core/library/Contao/Session.php#L171


Within the context, it makes no sense to mix things like that.


Yep - that does the trick too.  I thought I tried this, but apparently  you can generate the issue without a macro:
```
class WithInt {
   public var int:Int;
}

class Main {
    static function main() {
        makeNull(null);
    }
    static inline function makeNull(i:WithInt) return i.int++;
}
```
but the macro adds such a beautiful level of obfuscation, I feel other target implementers should enjoy it too.

But yes, I think the code that was generating the original macro should be informed at compile time that it is doing something crazy.


Don't understand this sentence bro ^^


Actually, you are wrong. The error message is correct but the condition is wrong. It should restrict cases when plural argument is set ++without++ singular argument because it has no sense.


Nevermind, I was mixing up arguments to mintty and to bash.


Dammit.. Just implemented the same thing, except with handling of the exception when the image does not exist. Wont it cause the build to fail if no matching image is found?


Again, the error message is correct but the condition is wrong. It should restrict cases when context is set **without** singular argument because it has no sense.


This would probably need Grammar submodule update to pass the test.


+1
didn't know requests, but reading in blocks seems to be a common approach.


Could we implement this as a template string tag? so that e.g. `intl`my.string``works?


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1106
success: http://build.servo.org/builders/linux2/builds/1106
success: http://build.servo.org/builders/android/builds/1140
success: http://build.servo.org/builders/mac1/builds/1320
success: http://build.servo.org/builders/mac2/builds/1322
success: http://build.servo.org/builders/gonk/builds/288


Interesting -- http://caniuse.com/#feat=indexeddb

Apparently quite buggy in mobile Safari, but it seems to be heading in the right direction.  Can we have both HTML local storage and indexeddb as a functor, or is that too invasive?


Please do not rename the slug to `yst_ga_settings_api`


For Drive the authentication works for *:uid => auth_hash[:uid]* but not for *auth_hash[:info][:uid]* the testing (based on dropbox) fails when using the first code without [:info]. I'm not certain how it works and if it actually chould not work with *auth_hash[:uid]*


Makes sense. Looking forward to it.


fast-forwarding master to auto = 092a6d6f


Uh, i think that's a bit too much damage. Maybe reduce it a bit lower?


saw approval from Ms2ger
at https://github.com/frewsxcv/servo/commit/5697095298182e1255a0309e0dcd4c00bfe26c07


merging frewsxcv/servo/urlsearchparams = 56970952 into auto


frewsxcv/servo/urlsearchparams = 56970952 merged ok, testing candidate = ccac6a94


actually

#ifdef QT5_BUILD
#include <QUrlQuery>
#endif
#include <QUrl>

would do already


The idea is that it kills you and that there is *no* way to avoid that. Why would I lower that?


is there any reason to do
```
            if (positionNow.x === lastPos.x) {
                xPos = 0;
            } else if (positionNow.x < lastPos.x) {
                xPos = -Math.abs(positionNow.x - lastPos.x);
            } else if (positionNow.x > lastPos.x) {
                xPos = Math.abs(positionNow.x - lastPos.x);
            }
```

instead of just
```
        xPos = positionNow.x - lastPos.x
```


angular.module already initialised in todoController.js, you don't need to set the todoApp variable if you're initialising angular.module and .controller (and other dependencies) in the same file


btw I've changed the variable names and should actaually rename xPos to xDelta too


@demory I added some comments to these classes to indicate that they define response model objects rather than internal routing data structures. I also added a few inline TODOs about refactoring the code. I know we just needed to get this done, but down the road it might be good to restructure the code and reduce the number of separate classes for profile/regular routing. Let me know if you have any comments on this, or if I'm misunderstanding some details here.


@McJty Alright. Fair enough.


Sorry about the `import x.*` noise, I need to reconfigure my IDE. One of the only things I dislike about IntelliJ -- it insists on importing whole packages in single statements, and you can't turn it off. You can only set the * import threshold to 9999 classes from the same package.


Why not use a property on the test instead and set `find_wrap` based on that?


This should have read "cygwin support", not "ctypes support".


We should better use `git pull --rebase` I think.

CC @guluc3m/gultalks-dev-team


Did not try. Should be possible though, since after normalizing the descriptor the values will be bounded by a constant.  I would guess that worst case is all values are 0 but one. Then the descriptor is [1, 0, ...,0]. So multiplying the values by 256 should put all values between 0 and 256. I don't know how bad would such quantization be.


same question :)
still running into errors in my build process...


FYI the sorting is working alphabetically


Yeah I corrected it in a new commit. I did a `push --force` --- this commit is no longer in the master branch.


As per http://hastebin.com/raw/oyozutozow this doesn't actually seem to support the WE 6 API


but it happens all cores(4 at mine) at utilized to 100 %, that why i put it
there.No load balancing at all.

On Mon, Mar 23, 2015 at 3:44 PM, Shrayas Rajagopal <notifications@github.com
> wrote:

> *all* isn't required here
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/igauravsehrawat/chennaipy-video-helpers/commit/4291f14764a233f665f89a4fbf799ad4fcb18ff3#commitcomment-10340950>
> .
>


the <script> tag paths should not need the '..' and '/public/' because they're already set in the server


yjhj


Do we gain anything by comparing the blindData here? We've already asserted that we're getting the metadata we want via `expectedMetadata` above, and we seem to have to do a lot of remapping to compare Cortex<->OIIO conventions. Plus, if OIIO or Cortex adds/removes/reinterprets a field, we have to change our tests. I think we are best off saying "we use the OIIO conventions in Gaffer, and know nothing of the Cortex conventions". With that in mind, I'd just revert back to clearing the blindData.


Is there a way to pass an Array as a value?


This should still be `importing`. :wink:


yeah, cleaner thanks.


ack


Prefer NULL to 0, so we can easily replace with nullptr when we get a C++11 compiler.


myfirst


Which is what I did. ;)
But I agree that it would be conceptually nicer if you could truly turn it off.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/13060/testReport/) for this commit**


FYI you need a function to clear only the completed items


Except I guess we do want to assert that the metadata appears in the blindData? In which case maybe we just compare the blindData to the `expectedMetadata`? Or do we say that mixing Gaffer (OIIO) and Cortex conventions for metadata is bad, and not support metadata in `ImagePlug::image()` at all?


Actually it's my fault - I patched up the wallet-template pom myself in an earlier commit and then when I rebased, forgot to take out this change.


In case user refreshes the page only a request to test if he is logged in is sent and response is auth : true/false. I could also send the email if auth: true in fact...
I need the email to fill a <li> but it's not absolutely necessary for now, later I will need it to show user's settings.


Thanks, it works, looks much better to me, the way the new `u` is rendered makes all the difference. Not having a border at such low-res probably helps too.


there's no front-end implementation of this method


Should this be double?


Prefer NULL.


Seems kinda redundant?


Was this tested on MongoDB? I filed issue #14025, because this introduces a bug.


ここの広告が無駄に増えてしまったせい。


This comment seems unrelated to the code below.


ここも、消したい。


Fixed in 6844478


Seeing this commit. Can I assume you will be doing gh-17?


This seems to be be a workaround. Wont the new installation of the app will face issues with table name of opengraphshare.


Woo!


trunc is not C89, please refactor without it.


Fixes #49


```  hiddenWord  ``` уже ж объявленна как переменная


I think you missed bumping Django in requirements.txt?


白井雄大のプロフィールを編集しました。


Thanks. Maybe we should add `autoconf` foo to integrate it?


The intent of the assignment was to annotate the code... you have not added much to the original content! just a thought.


We can simply remove these methods now can't we? Wasn't that the purpose behind making the base class methods non-pure-virtual?


Yes. Yes it should. Done now! :)


Is this yeoman generated code?


I'd rather get to the bottom of this before merging, especially since this change is unrelated to the main purpose of the pull request.


在第一个表输入“2007-”的时候What?列里的“2007"也被突出显示


Also added a functions file to auto-fill the slug of the project/task


This doesn't appear to be used.


另外，升序跟降序好像弄反了


What is the goal of those custom scripts, is it to only star them explicitly during an OGM build?

I'd be tempted to have it always running, it would simplify our testing jobs, and possibly speedup startup.

    - name: Start CouchDB on localcouchdb:5984
      docker:
        name: couchdb
        image: fedora/couchdb
        state: started
        domainname: localcouchdb
        expose: 5984
        pull: always

But I'll merge your PR first, as I'm assuming you tested it. (I didn't test the above, just an idea)


@jgmize deis backups are now encrypted. :metal:


The readme should be updated with the new requirement.


I think he meant "buff"->"buf"


Thanks ... now it works as expected... even a graphical bug is now gone with the latest "scope"-corrections.


@gearon iirc `PropTypes.object` doesn't work, `PropTypes.func` does.


This isn't correctly passing through the input hash unchanged when the channel isn't R, G, or B - my understanding is that it would have before.


have you properly configured registration data? in reply to
REGISTRATION_REQUEST

2015-03-23 13:26 GMT+03:00 thakorjay <notifications@github.com>:

> I had tried the same ,too.
>
> I also used the following one:-
> SendBytes((const unsigned char *)&value, sizeof(value));
>
> But the result is same.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/devicehive/devicehive-cpp/commit/3319387fab4cee5747676aa5bf61924a8ef893cc#commitcomment-10341150>
> .
>


after some massive debugging and checking, this line is sufficient. you can revert back the substructure notify mask stuff below (which creates a bunch of edge cases when reparented).


对生成左边div层时的table的各个列添加了宽度处理.避免有些时间生成的宽度不同,导致与原表格不匹配大小.


Hi Juho and Brian,

I've been following your discussion about cells and editing and I would
like to try it out. Are you planning to put out a new npm package? I am
using 0.4.2 through npm and I would like to update through npm if possible.

On Mon, Mar 23, 2015 at 3:28 AM Juho Vepsäläinen <notifications@github.com>
wrote:

> Where outputs can be a simple value or an object. If the current transform
> is dependent on the previous output step, then it can just take the last
> element of the array. Thoughts?
>
> Looks good. This is more flexible way to go. I'll change the first
> parameter to the scheme you described.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/bebraw/reactabular/commit/11cc4a416d3f4d2571d775f4f73adfeca77a16ba#commitcomment-10338636>
> .
>


## This is a markdown file


You forgot to bump API to 1.9.6


yeah right.
Has the policy changed and PVR maintainers have to do this on their own?


Fixed a math err :)


If this is going to be removed, then a proper pass-through must be implemented in hashColorData(). In general, when looking at a hash*() implementation, it should match the compute*() implementation in structure - so changing the structure of one implies the need to change the structure of the other.


Could you please delete the key after getting it and check that it does not exist anymore? just to make sure the cache is actually alive and valid.


* Login screen updated
* Email pages updated
* Theme options removed


See comment above, should not be neccessary. Don't leave environmental state, make sure it's purged after being used.


Merci, ça marche maintenant.
Date: Sun, 22 Mar 2015 16:49:50 -0700
From: notifications@github.com
To: increase@noreply.github.com
Subject: Re: [increase] Bouton ajax (78c582d)

Pour ne pas afficher la totale sur une requête ajax :

$this->view->disableLevel(View::LEVEL_MAIN_LAYOUT);

Sinon, il ne faut pas mettre la compilation dans la vue, mais simplement l'insertion de la variable script_foot (générée par la compilation dans le contrôleur) :

echo $script_foot

—
Reply to this email directly or view it on GitHub.


npm-shrinkwrap.json чейта? список всех зависимостей?


Missing the $ on $stateChangeError in the following line of your example:
```
$rootScope.$on("stateChangeError", function(event, next, previous, error) {


Now we can see single success notification instead of multiple. Secondly, as someone reported on BRL-CAD devel mailing list that when the size of the image exceed the limit it shows only the red bar but not the error message, now it is resolved and it would show a error message.


This would be HUGE in production.

When you're looping through a large number of models like this, you should use ```#find_each```:

```ruby
TaxonConcept.all.find_each do |taxon_concept|
  load_trait_data(taxon_concept)
end
```

...In this particular case, I might cut the work slightly by changing it to ```TaxonConcept.published.find_each```, too.


I'd like to stick to a single API for arrays, i.e. `v7_create_array()`.

Does it make sense to create dense arrays by default, and then switch to sparse arrays at run time at certain conditions (e.g. big size, holes creation, etc) ?


@poma thanks


It looks like you indent level changed at this point in the file: there are more spaces at the starts of lines after this line.


Set up correctly because the code that is passed different than you did - review the code and make it right!

 # CMake policies (can not be handled elsewhere)
 cmake_minimum_required(VERSION 2.8.9)
 cmake_policy(SET CMP0005 OLD)
+if(POLICY CMP0043)
+  cmake_policy(SET CMP0043 OLD) # Disable 'Ignore COMPILE_DEFINITIONS_<Config> properties'
+endif(POLICY CMP0043)

Bye!


This is actually a nested quote, but I don't think AsciiDoc can handle that.


TeamCity OsmSharp :: GitHub - OsmSharp [Build 998](http://build.osmsharp.com:8080/viewLog.html?buildId=4666&buildTypeId=bt16) is now running


Add specs for `PaneResizeHandleElemen`.
It simulate the mouse action to dispatch mouse event, then the pane resize element will respond for this event to resize the panes around the resize element.
These specs check some behavior.
* When user dragging the resize element, the panes around it will resize correctly.
* The resize behavior will not affect other panes, it only resize the panes around the resize element.


One correction to commit message: I'm checking for class "disabled", not "disable"


Indentation here?


add this to default.prop

ro.config.tima=0
ro.config.knox=0
ro.securestorage.support=false

MFG thehacker91


I'm not convinced about the utility of this - see my previous comments about wanting to use OIIO conventions in Gaffer, and let the Cortex conventions die out. Let's discuss.


r+


Remove comment.


yes, I can make a pull request. ``maxmultiple`` becomes
``maxmultiple{T<:Unsigned}(k::T) = div(typemax(T) - k + one(k), k + (k == 0))*k + k - one(k)``


Fixed in 1b2d148bc8f6d4257dab9946ef5b45f6fc96b9b1


Er, shouldn't this be 123123...125, and the next one also be -123123...125?


Mas @yaditya, mungkin mau diedit email author commitnya agar ter-link ke account GitHubnya mas.


Fixed in  51ccb83


This looks ugly, please add 1 tab to all aligned variables.


SendRegistration2Data("{"
        "id:\"" DEVICE_ID "\","
        "key:\"" DEVICE_KEY "\","
        "name:\"" DEVICE_NAME "\","
        "deviceClass:{"
            "name:\"" DEVICE_CLASS_NAME"\","
            "version:\"" DEVICE_CLASS_VERSION "\"},"
        "equipment:["
            "{code:\"" LED0_EQP_CODE "\",name:\"" LED0_EQP_NAME "\",type:\"" LED0_EQP_TYPE "\"},"
            "{code:\"" LED1_EQP_CODE "\",name:\"" LED1_EQP_NAME "\",type:\"" LED1_EQP_TYPE "\"},"
            "{code:\"" BTN_EQP_CODE "\",name:\""  BTN_EQP_NAME "\",type:\""  BTN_EQP_TYPE "\"},"
            "{code:\"" SENSOR_EQP_CODE "\",name:\"" SENSOR_EQP_NAME "\",type:\""  SENSOR_EQP_TYPE "\"}"
            "],"
        "commands:["
            "{intent:257,name:\"UpdateLedState\",params:{equipment:str,state:bool}}"
            "],"
        "notifications:["
            "{intent:256,name:\"equipment\",params:{equipment:str,state:bool}},"
            "{intent:258,name:\"sensordata\",params:{equipment:str,temprature:str}}"
            "]"
        "}");

I passed the above structure in registration data.


Why in your tests [null, null, null] = many([[null], [null], [null]])

but

[] == many([null, null, null]) ?

Shouldn't the test be [null, null, null] = many([null, null, null]) ?


Should we move this out of version control and into a travis ENV var?


Just had this issue. Glad to see you just fixed it :)


Yes and preferably send a PR to kodi after this PR gets merged bumping the addon.
See https://github.com/xbmc/xbmc/pull/6789 for an example.


Hi,

I think it should be possible to localize the 'Alert: %@, %@" string


This breaks things...


What's the diff ?


`sync-repos` fixed by https://github.com/SUSE/cloud/commit/21b10ff39e65e91bb3ec369f3b44b2b80daedddc

@bmwiedemann Can you comment on the `clouddata.cloud.suse.de` naming?


Should be a direct assignment : `h = (*it)->metadataPlug()->hash()` followed by `return`. This means that the hash will be identical to the input, and will share an entry in the cache. Wherever you see a compute pass through an input value directly, the hash should do likewise. Note that we can then also move the `ImageProcessor::hashMetadata()` call below this early-out.


There's some abstraction here in `core.py`, where multiple job-providers can be used, with the idea that we don't always want to run framework/CMSSW style jobs.  By adding this here, you break this abstraction.  I would rather see all this in the `cmssw.JobProvider`, with corresponding parts in `cmssw.jobit`, the only place apart from plotting where we open the database.


I don't understand, how is the value of the badge updated ?


Add a second line after this


you have a good work ahead :D


На самом деле вместо этого цикла можно написать strcpy, если правильно задать ему параметры. Но ОК, так тоже хорошо.


Closed Visual Studio Online Task [vso#4345](https://azurecom.visualstudio.com/DefaultCollection/ACOM/_workitems#_a=edit&id=4345): 'This is a test usersnap task submission'

VSO State: Done


@spincycle Yeah, I hope to get a release out this week. What sort of functionality are you using? This would be a good chance to take your needs in count. :)


TeamCity OsmSharp :: GitHub - OsmSharp [Build 4.3.0.998](http://build.osmsharp.com:8080/viewLog.html?buildId=4666&buildTypeId=bt16) outcome was **SUCCESS**
Summary: Tests passed: 519 Build time: 0:0:0


@DerAlbertCom please replace any `declare module ng` with `declare module angular`. The rest e.g. `foo:ng.ITimeout` should continue to work.


@DerAlbertCom see notes on https://github.com/borisyankov/DefinitelyTyped/pull/3851


Ok, cheers


IMO current comment is better.


Yeah, the switch should be done transparently. This is for incremental usage (e.g. as argument array)


@gitscrubz Looks like someone did this for us! :) The fix has been released in 1.6.3 -- thanks for your help in getting this issue solved. Please add me on Skype if you like (nickbolton2705).


We should be able to simply remove these methods instead.


should this go into master too?


I pushed in master too.


As above - we shouldn't need these. In fact, we should be able to remove the other ones too.


you can do root_url for this


just use `Predicates.alwaysTrue()` sry I should have mentioned it.


grrr... that push to master failed... it has been pushed now


As above, shouldn't need implementing at all.


Other than the indentation and the need to use find_each, this looks fine.

I'm worried this is going to take several days to run in production, but I guess we'll find out...


cool :)


Looks like just a missing semicolon


I think maybe we can just remove all the other methods instead of adding another one?


This commit is wrong. There will be only one instance of this class in the class loader so you cannot set field values based on the result of the validation. If we really wanted to provide that info it would need to be as a result object (which is not a change we want to do now)


Agreed, will pull it out into a full accessibility label


all tests pass:
success: http://build.servo.org/builders/linux1/builds/1107
success: http://build.servo.org/builders/linux2/builds/1107
success: http://build.servo.org/builders/android/builds/1141
success: http://build.servo.org/builders/mac1/builds/1321
success: http://build.servo.org/builders/mac2/builds/1323
success: http://build.servo.org/builders/gonk/builds/289


Refactoring with [this code](https://github.com/laravel/framework/blob/414af64668a3b578c64609d8385a528074581794/src/Illuminate/Console/AppNamespaceDetectorTrait.php) instead?


As of now this description needs to be generic based on the validation performed. The design does not allow knowing at this point exactly what failed in the navigation.


always use tabs for indentation, see how the rest of the code is written.

this enum must be public, so move it in r_print.h with the proper prefix R_PRINT_STRTYPE_{ASCII,WIDE,UTF8} maybe?


otherwise just use 'w' 'u' ...


Why do we use LanguageUtil here if it's also done in the JSP?


Hmm looks to be that i manage to updste the offending import alone.


This commit breaks htdocs submodule, as git don't allow itself to clone into non-empty folder.


if you introduce that new enum, make it sure it is used from other places where its currently using 'w', 'u'...


@tkazec It has already been fixed in 2d82b960b86ba9c6205060827f33a4622e64b926.


brackets must go in the same line


merci !


I would like some feedback on this change. It's a bit of a hairball to untangle, because `cni_notary_public_countries` do not match the given list precisely. So I created a new one.
However I'm wondering if there is a better way of dealing with this logic (see the commit message)?

Also, what's the preferred way of dealing with country lists, I see there are both local variables and stuff encapsulated in MarriageAbroadDataQueryV2 too. Which one should be used when? Should I do a separate commit to move all local vars with countries into the data query?


do not declare variables in the middle of nowehre, always define them after a new context (open bracket)


I don't always make clubber.  But when I do, I prefer to preserve ccache.


As said a few times before, I don't think we need these.


@GrahamCampbell huh. The version on npm is broken though.


you can add && input[3] check here to avoid oobreads


missing space between function name and parenthesis


Sounds good!


fast-forwarding master to auto = ccac6a94


len can be bigger than core->blocksize, use R_MIN (len, core->blocksize) here to avoid that issue, but maybe a temporary r_core_block_size() must be used here


It should work with `auth_hash[:uid]`, it looks like the dropbox authentication also have [that](https://github.com/bamorim/omniauth-dropbox-oauth2/blob/master/lib/omniauth/strategies/dropbox_oauth2.rb#L13).

The tests are failing becuase the fixture for the omniauth callback is setup with `auth_hash[:info][:uid]`, change [here](https://github.com/tkomstadius/bruse/blob/develop/test/helpers/omniauth_helper.rb) so that the *uid* is moved from *info*.

Hope that helps!


i would prefer to have a properly string defining the type, than just a char. "ascii", "wide", "utf", ...


I guess you're right that this new version of COSMOSCatalog that can make real or parametric galaxies should require an explicit ```gal_type``` (unless ```use_real=False```).  And yes, the code snippet in the example could change to just read in a single catalog and generate real vs. parametric galaxies from it.


Thanks for spotting, fixed in 48ac39a.


core->io->section can be null, check that before using it


saw approval from Ms2ger
at https://github.com/frewsxcv/servo/commit/c0ea1e633045b0b4592808b426c4d3e08ad77537


merging frewsxcv/servo/patch-1 = c0ea1e63 into auto


frewsxcv/servo/patch-1 = c0ea1e63 merged ok, testing candidate = 32ec0e38


sauf avis contraire, autant le nommer `publishedDate` non ? `published` en soi est pas super parlant imo.


Sure sure. I meant it is grammatically wrong. You could rephrase it to: _"If you aren't worried about file size and don't want to use 100% of all your CPU cores, add the `-preset ultrafast` to speed up processing"_

Also it only isn't about the file size and the CPU core utilization. Has got to do with lossy vs lossless encoding. @argvk will know more


@Chuck5ta - can you apply this to release20 as well - qualifies as a hotfix !


I've been trying to make sure that descriptions do a bit more than just repeat the node or plug name with a few joining words. It's not always easy, especially when the node name is so descriptive. Maybe it'd be worth clarifying that the node adds arbitrary metadata items rather than sets the whole thing, and also describe the overwriting behaviour when adding a name which already exists?


thanks :)


dsfsdfdsff


dasfdsafdsaf


Cool, I think assertions are more descriptive, but that's only my opinion. I've fixed it and amended the commit.


The webtests are fixed. Thanks for waiting.


Fixes - thanks @pward123


there is no need of seting an if statement if u are using the correct version of cmake. this cmps apear if u are using higher version and not setted cmake policy an error occurs if u have a lover policy that u have an non existing policy cause this policy was added at 3.0 be updating the minimum requirement of cmake there is no error and it will be handled like this.


this link could link to the `LICENSE.rst` page instead, like ":doc:`license`"


[Fixed] Could now launch gnoproj in different directory from EQR images.
[Updated] Scripts could now be launched in a directory different of EQR images.


all single now


Let's mention that they're space separated (otherwise people might think commas), and that Gaffer's standard wildcards can be used. The latter is hedging a bit because we only support * right now, but we will add more in the future.


`published`, dans la spec Atom, semble porter uniquement sur l'entry, pourquoi l'avoir ajouté sur le feed ?


well removed, for testing locally on server


Let's mention that it's done based on name.


done


This first instantiation is unnecessary.

But it is worth testing the case where the result tensor is supplied by the user:

    local result = torch.LongTensor()
    torch.find(result, tensor)


Кажется здесь лишний пробел перед фигурными скобками


Add a space between Delete and Metadata? That would match the other menu entries better...


removed


@davidfestal OK, I have added the version number to doc hover URLs. Thanks.


Давай использовать лицензию Апачи 2.0


sengaja biar commit streak ga putus? -_-


still does not build :disappointed:


Let's try to improve this a tiny bit, as for the DeleteImageMetadata docs - a quick mention of names, space separation and wildcards.


Alternatively:
```lua
local types = {"ByteTensor", "DoubleTensor", ...}
for _, type in ipairs(types) do
 local tensor = torch.rand(nSrc):mul(3):floor():type(type)
 --etc
end
```

Also, CharTensor and ShortTensor are missing here.


Lines 2 to 17 look like they were intended for the model spec, not the model class.


defineProperty on dense array doesn't work (it should promote the array to sparse array)


all single


@bjeuriss : just realised my change from `get_valid_DW_scheme()` to `get_DW_scheme()` means the `-bvalue_scaling` option will not be interpreted - which is what you initially had in mind. I guess the simplest way to allow this would be to use the `get_valid_DW_scheme()` if the `-bvalue_scaling` option is supplied, i.e. changing:

    207      DWI::Shells dwshells (header.DW_scheme());

to:

    207      DWI::Shells dwshells (get_options("bvalue_scaling").size() ? header.get_valid_DW_scheme() : header.DW_scheme());

What do you think?


Should be `MetadataProcessor::affects()`.


Bitte die `debug_mode` Variable wieder als Klassenvariable schreiben


done


Good start - consider also testing a valid `up_vote` and a valid `down_vote` in a similar way.


What does the `method={...}` bit mean here?


if your contant D2G_SENSOR is 258 then you have to send 'value' as string
as you described it in registration data.

SendString(EquipmentCode);
SendString(value);

of course value's type of should be const char* in this case, and
message length should be

msgh.Length = GetStringSize(value)+ GetStringSize(EquipmentCode);

2015-03-23 15:04 GMT+03:00 thakorjay <notifications@github.com>:

> SendRegistration2Data("{"
> "id:\"" DEVICE_ID "\","
> "key:\"" DEVICE_KEY "\","
> "name:\"" DEVICE_NAME "\","
> "deviceClass:{"
> "name:\"" DEVICE_CLASS_NAME"\","
> "version:\"" DEVICE_CLASS_VERSION "\"},"
> "equipment:["
> "{code:\"" LED0_EQP_CODE "\",name:\"" LED0_EQP_NAME "\",type:\""
> LED0_EQP_TYPE "\"},"
> "{code:\"" LED1_EQP_CODE "\",name:\"" LED1_EQP_NAME "\",type:\""
> LED1_EQP_TYPE "\"},"
> "{code:\"" BTN_EQP_CODE "\",name:\"" BTN_EQP_NAME "\",type:\""
> BTN_EQP_TYPE "\"},"
> "{code:\"" SENSOR_EQP_CODE "\",name:\"" SENSOR_EQP_NAME "\",type:\""
> SENSOR_EQP_TYPE "\"}"
> "],"
> "commands:["
> "{intent:257,name:\"UpdateLedState\",params:{equipment:str,state:bool}}"
> "],"
> "notifications:["
> "{intent:256,name:\"equipment\",params:{equipment:str,state:bool}},"
> "{intent:258,name:\"sensordata\",params:{equipment:str,temprature:str}}"
> "]"
> "}");
>
> I passed the above structure in registration data.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/devicehive/devicehive-cpp/commit/3319387fab4cee5747676aa5bf61924a8ef893cc#commitcomment-10342872>
> .
>


Thanks, fixed in 01ff68a449771d52596be72d19a9b088180a0140!


Yes, the idea is to start those services on demand, with a run-specific port id. That way several jobs requiring the same resources can nicely run in parallel on one node. The overhead for starting/stopping is neglectable.


Try to update Cython to a newer version.
Look at https://travis-ci.org/bibi21000/python-openzwave/jobs/55324599

2015-03-22 20:25 GMT+01:00 Jean-François Auger <notifications@github.com>:

> le fichier version.cpp contien
>
> #include "Defs.h"
> uint16_t ozw_vers_major = 1;
> uint16_t ozw_vers_minor = 3;
> uint16_t ozw_vers_revision = 0;
> char ozw_version_string[] = "1.3-103-g3be4793-dirty";
>
> ce qui provoque une erreur de compilation
> Error compiling Cython file:
>
> ...
> :return: A string containing the library type.
> :rtype: str
> :see: getLibraryVersion_, getPythonLibraryVersion_, getLibraryTypeName_
>
>     """
>     return "OpenZWave version %s" %(ozw_version_string)
>                                                      ^
>
> ------------------------------
>
> /opt/python-openzwave/lib/libopenzwave.pyx:916:58: Cannot convert 'string'
> to Python object
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/nechry/python-openzwave/commit/8506ce77b445a20cff1ac5905f23d3b1d28d6722#commitcomment-10334730>
> .
>


oh man. I looked for one and couldn't find it. thx!


You missed to to the same with titan defcondig ;)
As of now kernel is running with mpdecion and intelliplug in the same time


Could add clone here?


@leahpadgett all three equality methods are all ideally implemented. Thank you Leah!


Yeah thanks, fixed this.


Can we remove the inputMetadata size test?


OK.


Space?


@gavinking : yes, I've seen the commits.Cool.


@kevmoo Thanks :) There is more to come. I have a road trip today, 4 hours back and forth, expect more.


fixed in https://github.com/sulu-io/SuluProductBundle/pull/125.


done


出处


Good catch, I guess I messed up the mechanics on that merge a bit when I tried to make those couple of additional tweaks.  Hopefully fixed now.


I think we need to alter the Specification.cs file. Instead of `Skip`, let's use `Page` property. Make `Skip` property only gettable and it will calculate how many entries to skip based on `Take` and `Page`.


PASSES ALL ALARM TEST FAILS EVERYTHING ELSE


This will work although it can be simplified a little.

When `vote = user.votes.create(....)` is called, it creates a vote.

Thanks to the `user.votes.` chained call in that line, the `user` attribute of the created vote, `vote.user`, is *automatically* populated by Rails. This means we don't need to set `vote.user` manually, and so line 38 can omit the `user: user` attribute.

Line 38 changes to:
```ruby
  user.votes.create(value: 1, post: self) # No need to set `user: user` manually.
```


@hhravn - that's why the next commit - https://github.com/krystiannowak/docker-maven-plugin/commit/d732aaa7786080f11a764da3e92345e99b1b6ddb ;)


Mismatched comment. If the class name for a Node is fairly descriptive already, and there's nothing of note to document from a programming perspective, I'm actually pretty happy to leave nodes without comments and defer to the metadata documentation.


не хорошо пароли в открытый доступ выкладывать :)


Inaccurate comment.


As far as I remember we were planning to remove "unsure" from the list of options, and make it "orthogonal" to the two possibilities, so that users are forced to choose between yes/no at first, and only then mark it as "unsure" if needed.


npm is stupid


https://github.com/Urigo/angular-meteor/commit/ad8c9818306137610ef3e5c7a8c923b9ccffbdbc
tell me what you think


Yes, sorry for bad commit/version :)


r+


Müsste durch HTML 5 nicht auch einfach <meta charset="UTF-8"> reichen?


Remove the need for the `.to_i` conversion on line 20 - change lines 4 and 8 to use numbers not strings.


Without this change, all messages retrieved from Rabbit were always automatically marked as having been acknowledged.  With this change messages can be retrieved without acknowledging them ... they can then be explicitly acknowledged by calling $channel->ack(delivery_tag=>$tag)


The commandline is strings only, since that's the medium, but if you're passing programmatically you should be able to pass any value.

> On Mar 23, 2015, at 9:29 PM, Alexey Chebotar <notifications@github.com> wrote:
>
> Is there a way to pass an Array as a value?
>
> \
> Reply to this email directly or view it on GitHub.
>


done


I think this change was for UIT-21 instead of UIT-4


`.to_i` can also be removed here if lines 4 and 8 are changed.


gitflow gdzieś się zagubił?


@knu - Did you test that this works correctly on Windows, and doesn't break anything on non-Windows? It's not obvious to me how this will work at runtime.


This shouldn't cause any issues, although I do like keeping my code clean and as efficient as possible. If the method call crashes the server (without the null check) it just means I did something wrong. There's never a case you should check if a town has a null resident.


Hi, I have updated sql file to get it run on PostgreSql, might be useful for the developers


brands


Done


更新杨乃老师图片


I'm not expert in English, but I guess here `at` is missing? `... at VU MIF lecture hall 102`?


or https://docs.angularjs.org/api/ng/function/angular.noop


I think we should get rid of this hardcoded positioning routine and include it in the xml. this way it will be much easier for skinners to implement custom dialogs for their skins without those nasty restrictions ;-) I'll see what I can do about it (although I'm no Python coder).


Yes, thanks.


* 3 conditions on 1 line
*  imho `false !== $cache = Yii::$app->cache->get($cache_key)` shouldn't be here - better extract it above `if`


Thanks.

Yeah, I saw those extra bells and whistles. Sure, we can support it - but let it come from user requests first? For the time being, I don't see why it's really necessary - the current way can solve the problem sufficiently.


Make the pane resize behavior is valid when splitting or closing some panes dynamically.


done


It looks like you forgot to push '1.1.1' tag.


cute


An alternative implementation of `points` using the `sum` method.

```ruby
def points
  votes.sum(:value)
end
```

Consider reading the docs for the various calculation methods here: http://api.rubyonrails.org/classes/ActiveRecord/Calculations.html#method-i-sum


But using this SendString(value) function,  the device didnt send the value as a notification to gateway. So there would be no output on gateway.

And i also cant use int or double data type for temperature because of  type conversion error.

What can be done for this ?


I think better to put this information in the website. Readme could the point to that section of the website (We already have the slack room there)


CHOIY


img


Ahh heck, I see what @ichesnokov was saying now ... and yes, he is correct, you could always have done that with the options ...


Added cqlsh client


`to_str()` uses '%.21g', otherwise '%g' would use exponential notation for numbers that are < 21digits. I'd say we should use the same formatting rule for all cases. factor out number formatting into a separate function and use it?


Add validations tests for votes with values of 1 and -1.


update


That's a great question! I wasn't sure what would be the ideal behavior in case you gave me a null Iterable. What I mean is: the collection of iterables has a null entry. Would I add a null entry to the collection? SelectMany is suposed to take the elements inside many Collections and merge them in a single collection, right? So, my reasoning is that if you give me no collection to extract elements from, I just ignore it. Thats why if you give me a Collection of three null Iterables [ null, null, null ] I will just give you a empty collection for there were no elements to extract from null.

Whats your thoughts on it?


for my case CSV string with split(',') was enough :)


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


@flavorjones I at least tested that a gem generated through cross-building had a correct ruby version requirement and it did not affect gems generated for other platforms.
My understanding was that the enclosing block is run when generating a gemspec for a gem cross-built for mingw, so correct me if I'm wrong.


done


I didn't forgot. Was waiting for an answer from @arashbm in #175. i will probably release it now.


Yes, you are right. Thank you for your patch.


Shocking programming here


Thank you very much. I'm sorry I caused extra work for you. It's weird that they worked when we ran them at the hack a thon..

-----Original Message-----
From: Veronica Kahl Cary [mailto:notifications@github.com]
Sent: Sunday, March 22, 2015 7:06 PM
To: theVKC/VKC-Script-Changes
Cc: Devonne R. Kent
Subject: [VKC-Script-Changes] Fixed a few bugs (412a73a)

Fixed a few bugs

OK @devonne01, your script was great, but I found a couple of issues when other counties tried to run it, and I went ahead and fixed them. It was minor stuff, no big deal. Here's what I had:

1. Removed Option Explicit for now. Long story short, I need to comment out this line from new scripts for the time being, because of a long and complex reason I won't share right now.
2. When you DIM'd the variables, you included a few functions as variables, including "navigate_to_MAXIS_screen" which made the navigation function not work in some counties. Easy fix.
3. I tweaked the dialog just a hair so that things fit on monitors with different sized fonts. Again, no big deal. Basically just increased the space a tad between the text and EditBoxes.
4. Some of your functions for case noting and navigation used the old titles from the December training, and we modified a few of them. Mainly "write_new_line_in_CASE_NOTE" is now "write_variable_in_CASE_NOTE", and "navigate_to_screen" is now "navigate_to_MAXIS_screen". Easy fix (and it didn't affect anything, I just updated it while I was working on your script).
5. Added a "script_end_procedure("")" to the end. I don't think we even covered that before, so that's on me. No worries.

---
Reply to this email directly or view it on GitHub:
https://github.com/theVKC/VKC-Script-Changes/commit/412a73a2510f10bb347a63f769a7be0d29903f3b


should not this be `443` instead of `80`?


I guess you get a sensible error message if you upgrade the gem and haven't modified your data source? Since there's no changelog document or anything like that with explicit instructions.


Yes, but it's still confusing.


Убери пожалуйста этот файл из коммита.


@dmitryevseev @nikgraf  I usually like the explicit initializations like here with an empty collection or even `null` but since now it declares the var below in the same line that is doing the `_(col).map` then I agree with that because is less state to trace and think about.


saw approval from Manishearth
at https://github.com/Ms2ger/servo/commit/6b69fec7fe83cede5d6f7fa13fce71233e5b5821


merging Ms2ger/servo/script-warnings = 6b69fec7 into auto


Ms2ger/servo/script-warnings = 6b69fec7 merged ok, testing candidate = f9826c3a


Should we resize to `len` straight away?


We don't seem to dog food this version yet but I suspect Tomas will soon update our projects :)


GJ for paths :+1:


¯\_(ツ)_/¯ ! I'm asking because I'm not sure how `#cross_compiling` works!


This changes didn't break #2070.

I tested this with the following script and Dashboard view:
Name: Open URL
Command: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Arguments: http://www.google.com/#q={UserInput}
On Event: ShowInUserMenuBar

Git Extensions shows only the Specify User Input dialog and opens IE after closing it.

IE is always opened whether you press the X buttor or you press the OK button in the dialog. This worked the same way before my changes.


maybe we should add a comment that currently the other configuration features for the watchlist are located in the xwiki.cfg file? (we need to move them at some point now that we're using components but we need to also decide if we're going to refactor the code or not).


pfbandwithd ? pfconfig now monitoring Inline bandwidth. It's really getting powerful


This line is a hack:

It basically uses creates a "%lg" format which works fine for integers afaik.
The size argument will be ignored (a undefined value for the arguments array, will mean 0 digits, but the format string doesn't contain any placeholder for digits anyway.

Anyway, I guess a helper for turning integers to strings wouldn't be a bad idea.


this outputs "and" before the first search term.
-> 12345 results for *and* Rembrandt and something else and something else


How about storing mbuf pointer in the `struct v7_object :: properties` pointer, without intermediate hidden prop? We'd save memory and indirection.


This still a problem or has it been fixed with your other pull request?


Why not name this one "actionAdminMetaBeforeWriteRobotsFile"...


... and this one "actionAdminMetaAffterWriteRobotsFile" ?


контроллер без "as"


> I'm not completely sure about the zeropoint (since I've never in my life really understood zeropoints), but I think
> what you did there was to get the correct zeropoint for the 1s exposure time (whereas before the zeropoint was
> incorrectly set to be appropriate to a 2000 second exposure).

Yes, I believe that's what I did.  And I've never really understood zero points either, so I guess it's the blind leading the blind here.

> Also, you don't currently modify the flux of the non-chromatic parametric galaxies to match 2000s

Oops.

My original goal in doing all of this was to make the whole flux calculation a bit more automated, but this was a failure for several reasons (one being the issue with noise rescaling, another being the fact that I never pointed out that there's also a rescaling by the ratio of effective areas, so I was only dealing with exposure time issues).

So I am going to do the following:
- remove the flux rescaling from the parametric galaxies
- leave the zero-point modification as-is since I think that is the right thing to do
- note in the docstring the exposure time and effective diameter scaling that is necessary for the outputs and has to be done by the user, pointing to demo11 for an example
- update the example in the docstring

Will push a commit shortly that has all these things, and will comment on here to let you know it's ready.  Could you please check whether what you did requires any updates to account for these changes?

My outstanding questions are:
- I'm not sure the exposure time and effective diameter scaling quite works for the real galaxy images.  Won't the noise level still be wrong?  I mean, the sky level should scale the same way as the real signal, but the noise should scale like the square root of that, right? (whereas we're advising the user to scale it linearly with these things)
- As we are playing around with this, it would be nice if we had unit tests.  (Totally my fault - I couldn't think of reasonable ones, then kind of dropped the issue.)  But we should at least have some minimal ones that use a small catalog and perhaps check basic flux normalization issue.  Any other ideas for unit tests?


It's a rake-compiler method to allow altering gemspec (only) when cross-compiling.
https://github.com/rake-compiler/rake-compiler#ok-lets-cross-compile-some-gems


I see...
I guess ignoring is fine, doesn't make much sense to bother the user with an exception at this point. Please add a comment to your test to make that explicit.


I'm very confused here. This commit is showing up directly under torch/torch7 . there's no PR, and its not in any of the branches, and I'm getting @timharley's comment notifications


@aitek4iit I'm having this compilation problem on Windows:

```
>------ Build started: Project: yarpmanager-qt, Configuration: Release Win32 ------
1>mainwindow.obj : error LNK2019: unresolved external symbol "public: __thiscall AboutDlg::AboutDlg(class QString,class QString,class QString,class QString,class QWidget *)" (??0AboutDlg@@QAE@VQString@@000PAVQWidget@@@Z) referenced in function "private: void __thiscall MainWindow::onAbout(void)" (?onAbout@MainWindow@@AAEXXZ)
1>mainwindow.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall AboutDlg::~AboutDlg(void)" (??1AboutDlg@@UAE@XZ) referenced in function "private: void __thiscall MainWindow::onAbout(void)" (?onAbout@MainWindow@@AAEXXZ)
1>C:\dev\yarp\build\bin\Release\yarpmanager.exe : fatal error LNK1120: 2 unresolved externals
```


yes


The particular problem is that this forces `dpl` to install `nokogiri` even when it's already installed.

```sh-session
$ gem list nokogiri

*** LOCAL GEMS ***

nokogiri (1.6.6.2, 1.6.5, 1.6.3.1, 1.6.2.1, 1.5.11)
$ gem install nokogiri
Building native extensions.  This could take a while...
Successfully installed nokogiri-1.6.6.2
1 gem installed
$ gem install nokogiri
Building native extensions.  This could take a while...
Successfully installed nokogiri-1.6.6.2
1 gem installed
```

I see that my check was a bit incomplete.


Yeah I guess we can just remove this readme in this repo.


I think we should better include the base constant into the `Specification` itself, so that we won't duplicate the same code everywhere


I think so, but I'm not 100% sure.


That is a great idea.


Hmm, yes, we should just pass the entire db string in the environment, instead.


обработку ng-click лучше делать в контроллере - так код будет чище и легче восприниматься. Вызов функции orderByKey лишний


It was just a stub while implementing.


Thanks :)


yeah, well the current approach allows for

1. dense arrays with with no non-array properties
2. dense arrays with with non-array properties
3. sparse arrays

If case (2) is not so common, then it woujld make sense to speed up (and make smaller) (1).

It might be a good idea. Minor change in the GC (to not follow that pointer) required. The obvious place where to encode the V7_OBJ_DENSE_ARRAY flag would be in the LSB of the `properties` field :-)


The routing needs to match the slashes, it doesn't work without the multiple parameters.


This revision is clean.


cool :)


That did not seem to work for me when I tried it, but maybe I did it wrong.


Cool, fixed in https://github.com/google/yapf/commit/3a0143c3ea55d41bbdd13be97fd894528f52639b


I hate camel case :)


My intention was to put a ruby version requirement based on what's in .cross_rubies, so that the gem built refuses to install for rubies beyond the maximum version in the list, ignoring the teeny part.
Hopefully @luislavena can confirm this...


Yes, you're right. Excellent


大神你带我飞。


Good idea


I guess we should generate an html not found page


Yes, good idea


Apologies, I think this is a bug in github's UI. A link to a commit in a comparison resolved to:
https://github.com/torch/torch7/commit/42a1cf1aaf78a7bbb98e2a09bbdc1bae76a9f3c2

instead of:
https://github.com/lukemarris/torch7/commit/42a1cf1aaf78a7bbb98e2a09bbdc1bae76a9f3c2

The intention was for the comments to be directed @lukemarris prior to a pull request. I'm emailing support@github.com with the details.

Sorry again for the spam :) I'm sure @lukemarris will send the real PR soon!


MikeDr28
I'm amazed at how my file is attached to your fork.  Did you use the referenced file also?


Check the commits, it's already done :)

On 23/03/2015, at 09:08, "maneco2" <notifications@github.com> wrote:

you have a good work ahead :D

—
Reply to this email directly or view it on GitHub.


Whoops, yes


Good looking out @zackhsi


The option is in "Display Settings" under smart cover. Default off


1. Simple Test


Haha cool. I was just checking because if this was a private repo that would be a bad bad bug.


Since we are at it, we could expand on the help of this function, so that new developers are not puzzled about what unbounded cords are.

Something of the form: allows discontinuities in the plot at unbounded coordinates, which are defined to be `+/-inf` or `NaN` (for additional details see pgfplots manual 4.5.13 Interrupted Plots).


1: D400 First line should end with '.', not 's'
1: D205 Blank line missing between one-line summary and description
1: D208 Docstring is over-indented
30:1: I101 Imported names are in the wrong order. Should be DatabaseError, run_sql
32:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibsched.bibtask should be before from invenio.legacy.dbquery
33:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.legacy.bibsched.bibtask
34:1: I101 Imported names are in the wrong order. Should be CFG_BIBINDEX_CHARS_ALPHANUMERIC_SEPARATORS, CFG_BIBINDEX_CHARS_PUNCTUATION
34:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibrecord
35:6: E126 continuation line over-indented for hanging indent
55: D200 One-line docstring should not occupy 3 lines
65:9: E128 continuation line under-indented for visual indent
68:1: E302 expected 2 blank lines, found 1
68: D401 First line should be imperative: 'Return', not 'Returns'
68: D209 Put multi-line docstring closing quotes on separate line
68: D205 Blank line missing between one-line summary and description
68: D208 Docstring is over-indented
84: D401 First line should be imperative: 'Return', not 'Returns'
84: D209 Put multi-line docstring closing quotes on separate line
84: D400 First line should end with '.', not 'e'
84: D205 Blank line missing between one-line summary and description
84: D208 Docstring is over-indented
99: D401 First line should be imperative: 'Return', not 'Returns'
99: D400 First line should end with '.', not 'e'
99: D205 Blank line missing between one-line summary and description
99: D208 Docstring is over-indented
107:5: B901 blind except: statement
114: D401 First line should be imperative: 'Get', not 'Gets'
114: D290 White spaces around docstring should be trimmed.
114: D209 Put multi-line docstring closing quotes on separate line
114: D400 First line should end with '.', not 'd'
114: D205 Blank line missing between one-line summary and description
114: D208 Docstring is over-indented
120:5: B901 blind except: statement
127: D401 First line should be imperative: 'Get', not 'Gets'
127: D290 White spaces around docstring should be trimmed.
127: D209 Put multi-line docstring closing quotes on separate line
127: D400 First line should end with '.', not 'd'
127: D205 Blank line missing between one-line summary and description
127: D208 Docstring is over-indented
133:5: B901 blind except: statement
140: D205 Blank line missing between one-line summary and description
170: D400 First line should end with '.', not 's'
170: D205 Blank line missing between one-line summary and description
170: D208 Docstring is over-indented
181:11: E271 multiple spaces after keyword
187:1: F401 'get_idx_indexer' imported but unused
187:1: E402 module level import not at top of file
190: D401 First line should be imperative: 'Return', not 'Returns'
190: D209 Put multi-line docstring closing quotes on separate line
190: D205 Blank line missing between one-line summary and description
190: D208 Docstring is over-indented
212: D401 First line should be imperative: 'Return', not 'Returns'
212: D290 White spaces around docstring should be trimmed.
221: D401 First line should be imperative: 'Return', not 'Returns'
221: D209 Put multi-line docstring closing quotes on separate line
221: D400 First line should end with '.', not 'h'
221: D205 Blank line missing between one-line summary and description
221: D208 Docstring is over-indented
232: D401 First line should be imperative: 'Check', not 'Checks'
232: D400 First line should end with '.', not 'l'
241:1: E302 expected 2 blank lines, found 1
241: D400 First line should end with '.', not 's'
241: D205 Blank line missing between one-line summary and description
241: D208 Docstring is over-indented
255:1: E302 expected 2 blank lines, found 1
255: D401 First line should be imperative: 'Return', not 'Returns'
255: D205 Blank line missing between one-line summary and description
255: D208 Docstring is over-indented
268: D401 First line should be imperative: 'Return', not 'Returns'
268: D209 Put multi-line docstring closing quotes on separate line
268: D205 Blank line missing between one-line summary and description
268: D208 Docstring is over-indented
281: D401 First line should be imperative: 'Return', not 'Returns'
281: D209 Put multi-line docstring closing quotes on separate line
281: D205 Blank line missing between one-line summary and description
281: D208 Docstring is over-indented
291: D401 First line should be imperative: 'Return', not 'Returns'
291: D400 First line should end with '.', not 's'
291: D205 Blank line missing between one-line summary and description
291: D208 Docstring is over-indented
299:5: F841 local variable 'out' is assigned to but never used
321: D401 First line should be imperative: 'Return', not 'Returns'
321: D209 Put multi-line docstring closing quotes on separate line
321: D400 First line should end with '.', not 'g'
321: D205 Blank line missing between one-line summary and description
321: D208 Docstring is over-indented
326:26: E261 at least two spaces before inline comment
326:27: E262 inline comment should start with '# '
327:26: E261 at least two spaces before inline comment
327:27: E262 inline comment should start with '# '
342:25: E261 at least two spaces before inline comment
342:26: E262 inline comment should start with '# '
362: D401 First line should be imperative: 'Return', not 'Returns'
362: D209 Put multi-line docstring closing quotes on separate line
362: D400 First line should end with '.', not 'g'
362: D205 Blank line missing between one-line summary and description
362: D208 Docstring is over-indented
399: D401 First line should be imperative: 'Return', not 'Returns'
399: D205 Blank line missing between one-line summary and description
399: D208 Docstring is over-indented
437: D401 First line should be imperative: 'Return', not 'Returns'
437: D400 First line should end with '.', not ':'
437: D205 Blank line missing between one-line summary and description
437: D208 Docstring is over-indented
442:10: E225 missing whitespace around operator
450: D401 First line should be imperative: 'Remove', not 'Removes'
450: D205 Blank line missing between one-line summary and description
450: D208 Docstring is over-indented
463: D208 Docstring is over-indented
463: D200 One-line docstring should not occupy 3 lines
477: D401 First line should be imperative: 'Create', not 'Creates'
477: D400 First line should end with '.', not 'd'
477: D205 Blank line missing between one-line summary and description
477: D208 Docstring is over-indented
487: D101 Docstring missing
491: D401 First line should be imperative: 'Return', not 'Returns'
491: D300 Expected """-quotes, got '-quotes
501: D401 First line should be imperative: 'Return', not 'Returns'
501: D400 First line should end with '.', not 'y'
501: D205 Blank line missing between one-line summary and description
501: D208 Docstring is over-indented
512:47: E202 whitespace before ')'
516: D401 First line should be imperative: 'Check', not 'Checks'
516: D400 First line should end with '.', not 't'
519:25: E272 multiple spaces before keyword
526: D401 First line should be imperative: 'Check', not 'Checks'
526: D209 Put multi-line docstring closing quotes on separate line
526: D400 First line should end with '.', not ';'
526: D205 Blank line missing between one-line summary and description
526: D208 Docstring is over-indented
532: D401 First line should be imperative: 'Return', not 'Returns'
532: D209 Put multi-line docstring closing quotes on separate line
532: D400 First line should end with '.', not ';'
532: D205 Blank line missing between one-line summary and description
532: D208 Docstring is over-indented
541: D401 First line should be imperative: 'Find', not 'Finds'
541: D400 First line should end with '.', not 'n'
541: D205 Blank line missing between one-line summary and description
541: D208 Docstring is over-indented


1: D100 Docstring missing
21:1: I201 Missing newline before sections or imports.
23:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.legacy.bibindex.engine_stopwords
23:1: F401 'CFG_ETCDIR' imported but unused
24:6: E126 continuation line over-indented for hanging indent
68:1: E302 expected 2 blank lines, found 1
68: D400 First line should end with '.', not 'g'
68: D205 Blank line missing between one-line summary and description
81:1: E302 expected 2 blank lines, found 0
81: D103 Docstring missing
92: D401 First line should be imperative: 'Return', not 'Returns'
92: D205 Blank line missing between one-line summary and description
92: D208 Docstring is over-indented
106: D401 First line should be imperative: 'Return', not 'Returns'
106: D205 Blank line missing between one-line summary and description
106: D208 Docstring is over-indented
120:1: E302 expected 2 blank lines, found 1
120: D401 First line should be imperative: 'Return', not 'Returns'
120: D208 Docstring is over-indented
130:1: E302 expected 2 blank lines, found 1
130: D400 First line should end with '.', not 'e'
130: D205 Blank line missing between one-line summary and description
159:1: E302 expected 2 blank lines, found 1
159: D400 First line should end with '.', not 'e'
159: D205 Blank line missing between one-line summary and description