I wonder if you can establish the context of Flash, too, wherein Java applets were a huge thing and it seems semantics didn't matter as much, because it was more about the content alone than the actual meta-juice to give to web crawlers. It's almost as if designers forgot about semantic, hypertext, and the value of building linking relationships. The commodifying of search results, though, woke everyone back up to those values. Flash was like the animated GIF 2.0. :-)


GPL licence header need to be removed


Seems like i can't remove this anymore... :(


I will squash before merging with master, but yeah, I should read git for dummies after this :)


I like this POV. I wonder how you can sharpen the focus of your project by situating/framing your history as a history of web usability.


No need to introduce new typedef. Just use uint32_t and uint64_t


Yeah- I found it useful for testing upstream systems (basically the same use cases as fakeEmailer)


I receive this message trying to run spack after this commit:
```
Traceback (most recent call last):
  File "/home/massimiliano/PycharmProjects/spack/bin/spack", line 55, in <module>
    from external import argparse
  File "/home/massimiliano/PycharmProjects/spack/lib/spack/external/argparse.py", line 111, in <module>
    from llnl.util.tty.colify import colified
  File "/home/massimiliano/PycharmProjects/spack/lib/spack/llnl/util/tty/colify.py", line 36, in <module>
    from llnl.util.tty.color import clen, cextra
ImportError: cannot import name cextra
```
I guess `color.py` was not added to the commit...


What is the point of having double sudo here (root->user->root)?


Thanks for this, I know it's nit-picky but I think it's a lot more clear


@vspinu you may find `(ess-args-alist)` useful.

It returns all arguments of the current function as an alist of strings. The CARs are the parameter names (nil if not specified) and the CDRs are the expressions constituting the arguments.


Wow, that was fast :+1:


This is a fantastic test. I would, however, suggest catching the exceptions in your test, or using the @exptected tag from JUnit. As it stands, we don't know if these methods should throw an exception, or if an exception means the test fails (and subsequently why it failed).


or s/is a part/was formerly a part/

could be mentioned in license.md but the point of these headers was so they don't get deleted


Oh, I see you actually don't need the `@api` because `convert`. Nice!


My two cents, both es-Es and es-AR says: Protección de ratreo and not Protección contra rastreo. We found that when Alba and I were working on webpages


Fair enough. :grin:


Ok I'll use it twice, will take a closer look at that.

I was also thinking of rejecting whitespace anywhere, since supporting e.g. `111-  123` as valid looks awkward... Do you think it would be OK to add a check for whitespace before the calls to safe_atou too?


I considered that, but the problem is the that I wanted the user to have a chance to dismiss the alert before their shape disappears.  Both that and what you suggest can be done simultaneously, but I think I would have to introduce a second lock (which I think would be a net addition of complexity).


Some of the functions of old header we could move to C file. It will simplify an API.


huh, @davidfestal, an empty block?


And that explains why I was absorbing magic damage sometimes. smfh.


Quirky crap, actually. Will simply ask whether `value` is `instanceof Array` here...


Also, consider how Netflix used Microsoft Silverlight originally before moving to HTML5. I, as an Ubuntu user, couldn't use Netflix on my laptop until about 1 year ago, since the were "in bed with" MS. Apple struck the deathblow to Adobe Flash when they decided that their mobile phones wouldn't support it (in favor of video codecs and other Apple-specific tech, of course).


This structure is almost duplicate of structure from ext4_types.h


Please remove this.


i feel like i should share this tidbit with the world


You need to check for out-of-memory conditions by testing if malloc() returns null, and handling errors appropriately, here and below.


Please develop commit message.


Er... Perhaps you mean in web content? In product, I've always translated it as "Protección contra rastreo":

https://github.com/mozilla-l10n/www.mozilla.org/commit/37aae575f2053f76fb851ba004382453c463e2c5


All misc macros could be moved to ext4_types


Принято.


The "1024" (and "96", below) magic numbers should be macros which describe what they are for


дискуссию можно вести долго, просто поправь под себя, а я на будущее учту...


Code that is no longer needed should be deleted instead of commented out.

Commented out code is clutter. If the old implementation is needed, it can be retrieved from Git history.


All right
I figured about the bug in our code,
We store the data as dictionary so non-unique species appear only once

Example:
There are two species MG_015_MONOMER in the Decay.xls table ID column, 1
for each compartment
But when we loop through the dictionary inside our code, each key
appears only one.

Need some more time to get through it
Denis

On 13.10.2015 18:49, Denis Kazakiewicz wrote:
> yes, please hold on
> rate law should be fixed soon
> working on it
> Denis
> On 13.10.2015 18:47, Martin Scharm wrote:
>>
>> @den2042 <https://github.com/den2042> did you comment @manikitos
>> <https://github.com/manikitos> patch on purpose?
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/whole-cell-tutors/whole-cell-reduced/commit/ac12ba924aef4feefccd7bede19fbb7e52ea61a5#commitcomment-13745944>.
>>
>


lol


Please remove.


So also select should use it, then.


Double check that loading the harmonogram_example.json works (instead of default_example.json) ... this should make a visualization without a dendrogram/colorbar.


Environment variables cleanup. I plan to rework this for Whonix 13. Make it all just run as root. Needs some improvements in tb-updater, that I also have planned.


Indeed, that's a tough one, due to proprietary junk. I would advise caution about the idea of "societal changes," rather how these were real execs, owners at particular companies whose decisions shaped the broader communities of devs and designers and standards bodies. Society is a wicked problem, so I would still advise narrowing the focus into particular groups of people, which will happen the more artifacts and docs you dig up.


Actually, I just checked `List`'s source and it seems its constructor (used by `ToList()`) also has a fast path like `ToArray()`, so we shouldn't see any noticeable difference between the two extensions :smile:


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 672](https://teamcity.mesosphere.io/viewLog.html?buildId=58104&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:05:57


I don't think we should change the code style to use this.


Yeah, It's just a trivial change. Since I am not familiar with RST, so I changed it to markdown temporally for editing easily. If any pull request, readme would be rst ;-)


Sorry!  Fixed in d16095c


I think that You should rebase this commit to few smaller ones.
1. Simplify an API of old ext4_extent and rename to ext4_extent_simple
2. Introduce new types and macros in ext4_types
3. Add new implementation: ext4_extent_full.c


Cierra issue https://github.com/InspectorIncognito/androidApp/issues/33


plz help me pllllzzzzz
Inquiry Number 1210340863
10/13(Tues) 13:37
Email is sleepy14378@gmail.com
Really need your help


pyqt4 isn't actually a prereq


Cierra issue https://github.com/InspectorIncognito/androidApp/issues/15


Align with previous line.


@Maks3w — For the following reasons:

- First, specifying 2.4 is low-balling the dependency. Since Expressive depends on PHP 5.5+, *it's going to get a newer version anyways*. We should specify 2.5+ as a result.
- Second, specifying 2.7 forces users who are contemplating using hydrators to use zend-hydrator + zend-stdlib, ensuring that their code is forward compatible with later versions. We want to recommend using zend-hydrator vs using the hydrators from zend-stdlib for greenfield projects.


copy paste error. i'll fix


Overall, I like your trajectory, Sarah! Keep narrowing it down, though. Consider the act of framing this as a usability of the web history. This should help a bit. Perhaps you should also scour the W3, WHATWG, CSSWG, etc. listservs for any mentions about Flash. Then, you can find more usability focused sources.

One last comment: I'm wondering how you are going to pivot into the DITA project with a Flash-based history. Start considering what documentation you will create as you move through this historicizing project. Perhaps, some of the HTML elements that rendered Flash a bit more inert.


Looks like there is a spelling mistake


Creating a Picasso instance for each call will disable any caching -> not good on mobile
As we only force the right protocol we could create a static instance of the Picasso and reuse it.


Issue5249-FixHWBBEngRef (wfbuhl) - x86_64-MacOS-10.9-clang: OK (1903 of 1903 tests passed)

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


twice -> `twice()`


Probably worth adding an `assert self.namespace` in the _get_namespace_tag since you're removing this vestigial check (that currently doesn't do anything)


@xsawyerx you said in the comments on the related issue:

> Dancer2.pm really does not have anything interesting or important. It currently only lists the import and one single short example. That can and should be removed.


After that one little fix, lgtm. I'd stage it, of course, to make sure it renders well.


> I haven't used `node.js` before and I don't want to pretend like I did, but making it work in node.js should be simple enough (and I'll do that tomorrow .. just to see exactly what it takes).

These might be of some help:

* https://github.com/nwjs/nw.js/wiki/Transfer-objects-between-window-and-node
* http://blog.namangoel.com/browserify-vs-webpack-js-drama
* http://stackoverflow.com/questions/28674652/what-is-the-difference-between-browserify-requirejs-modules-and-es6-modules#29181416 (even more options)

> It depends. That's a design decision: do we want to be able to 'revive' a resource? To have `===` work we would have to not delete the resource when calling close, just marking it as closed.

Consider also that at that point in the code, we've only `close`d `red1`. `red2` is still happily chugging along. It's true that `red2` maintains its own handle (via it's own private `_expensive_resource` var), but what happens if, instead of [this](https://github.com/sirrocco/veritaseum_challenge/commit/5daed28845f9ccd950161d587794a9e1629c986a#diff-be7f22879c04da57454a860e329ede50R46) ...

```js
function close() {
    // ...
    _expensive_resource = null; //dispose of the resource.
    // ...
}
```

... we had this ...

```js
function close() {
    // ...
    _expensive_resource.closeAllConnectionsAndDisposeOfAllUnderlyingResources();
    _expensive_resource = null;
    // ...
}
```

Where does that leave `red2`?

> We could add an `equals` method that would compare 2 expensiveResources on specific properties to decide if they are equal. But again, once you call `close` I would treat it as a sort of `dispose` function and you should get a new instance of the expensiveResource.

What if I told you that sharing access to the underlying resources was entirely appropriate (e.g., like a single database connection that multiplexes cursors)? Given the "expensive" hints everywhere, I'll leave how to tackle this up to you.

> You also mentioned the license :) . My bad on this .. I just picked a license that I thought made sense for the code I'm writing. You could say that I just took a look at an idea and rewritten it, so no license was broken. It's not like I forked your code or anything :P. But I see your point.

Yeah, that was a cheap shot on my part. My apologies. :grin:

Thanks for the responses, and I look forward to seeing your future updates!


As a nit, it's nice to be consistent about whether you use pointer + offset or &pointer->offset.


good catch. fixed!


I'll stop noting that these sorts of things should be deleted here.


Fixed in other PR.


Ah, I'm sorry I missed this. This looks fine.


Cool...So I've added a small subroutine to the ```uptime()``` function that sends the uptime as a string to the Django collection database (when requested with the argument ```"sendUptime"```). Also corrected the if statement that was checking the number of hours. It was doing ```if (numberOfHours > 24)```, which allowed the number ```24``` to be inserted in the uptime string, which of course did not make any sense.....lol :satisfied:


Magic numbers.


Nice !


Error handling is missing.


Is there a plan to make both Provider and provide use 'as' syntax? I find it a bit confusing to have 'to' and 'as' both in use.


Right, will do. The exception gets *swallowed* so I had to resort to outputting it, didn't think of using `warn` though.


It's still helpful if you can open an issue and attach a patch, so I know specifically what you're talking about, and to make sure the problem doesn't get forgotten.


Hey, just wanted to say thank you for doing this. Running AK kernel with your modifications on COS12.1 works perfectly!


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 673](https://teamcity.mesosphere.io/viewLog.html?buildId=58112&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:03:54


Nevermind I checked the latest and it seems to be updated.


As someone reading the log of commits, I have no idea what this actually fixed, nor why it was "shitty". The pull request, #100, also didn't include any description. If you want some tips, see/watch: http://ryan.mcgeary.org/2011/09/02/do-your-commit-messages-suck-rockymtnruby/


What defaults to the default button after you say that the load data button is no longer the default?


Why do you only test `l-bfgs`?


Problem is I don't know how to convert the `VegaVisualization` into a `Dict`. `tojson` neatly converts it into a `String`. Maybe use `JSON.parse` and convert to a `Dict` before sending it off?


Typo: captch**a**


Nit, please use spaces around all binary operators. (A * B, not A*B).


Cierra issue https://github.com/InspectorIncognito/androidApp/issues/4


You don't need to use patch_object here; you're creating a new `self.plugin` for each test case, so you can just do:

```
m_datastore_client = MagicMock(..., autospec=True)
self.plugin = m_datastore_client
```

This makes the test code cleaner: less indentation, and probably fewer characters.


I see this commit passing by.

What about package protected lifecycle/inject methods?
I do hope that is allowed.
If the spec mandates protected then that sucks for unit tests.


Issue5249-FixHWBBEngRef (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1909 of 1909 tests passed)

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


editions/clientserver/tiddlers/Using TiddlyWiki for GitHub Pages project documentation.tid

Yes, I deleted the comment right after I noticed. Was searching the source and didn't seem to find the right one... and then found it.


This needs a period also.


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1370 of 1370 tests passed)

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


That's what we have now
 >>> D = {'eggs': 3, 'eggs': 1, 'spam': 2}
 >>> D
{'eggs': 1, 'spam': 2}

Working on patch

Denis

On 13.10.2015 19:34, Denis Kazakiewicz wrote:
> All right
> I figured about the bug in our code,
> We store the data as dictionary so non-unique species appear only once
>
> Example:
> There are two species MG_015_MONOMER in the Decay.xls table ID column,
> 1 for each compartment
> But when we loop through the dictionary inside our code, each key
> appears only one.
>
> Need some more time to get through it
> Denis
>
>
> On 13.10.2015 18:49, Denis Kazakiewicz wrote:
>> yes, please hold on
>> rate law should be fixed soon
>> working on it
>> Denis
>> On 13.10.2015 18:47, Martin Scharm wrote:
>>>
>>> @den2042 <https://github.com/den2042> did you comment @manikitos
>>> <https://github.com/manikitos> patch on purpose?
>>>
>>> —
>>> Reply to this email directly or view it on GitHub
>>> <https://github.com/whole-cell-tutors/whole-cell-reduced/commit/ac12ba924aef4feefccd7bede19fbb7e52ea61a5#commitcomment-13745944>.
>>>
>>
>


The first idea that occurs me, is on updateDisplayList(unscaledWidth:Number, unscaledHeight:Number), assign the skin.scroller or skin.scroller.viewport width/height.. that should avoid the scroller to show.

I'll test the textarea now :+1:


Cierra issue https://github.com/InspectorIncognito/androidApp/issues/2


Check last sentence.


b8 instead here?


Is it possible that this is too aggressive? In the C++ completion manager it's okay for the document to change or the cursor to move and as long as it's on the same line we just use the additional mutations as a prefix filter on the returned completions. Is there something similar in the R completion manager that this would foil (and thus cause many more completion RPC calls to occur)?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 674](https://teamcity.mesosphere.io/viewLog.html?buildId=58113&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:02


'CodeHub' test


It's generally good practice to drop a log or two in your test code; something like

```
logger.info('Calling self.plugin.delete(%s, %s, %s). Expecting error.', (args,))
```

Don't have to log the args if they are not interesting, that's just an example. You should also log any interesting setup/assert logic, too; in test cases such as this one it's not necessary, but if the setup is more complex (or could fail) you should leave a log trail.

This makes it easier to tell what's going on if the test case fails, since you'll get test logs interleaved with real code logs in the output.


you have copy/paste error here and even though
this commit is deprecated by this https://android.googlesource.com/device/lge/hammerhead/+/6e250e13a0138f9cdd1cb5c7ea2dba416820a545%5E%21/#F0


Unfortunately `mktemp` and `tempfile` are not available in my environment, so using and deleting `filename.$$.tmp` instead.


Issue5249-FixHWBBEngRef (wfbuhl) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Do something


Nit: this comment isn't useful. Either beef it up to summarize what we're asserting, or remove it.


Publish is NOT the same as Approve is it?
If it is the same, why have a separate method?


is it bad that we're silently ignoring any kwargs that do get passed in? maybe we should just forward them along and let the endpoints handle them appropriately


I'm not sure that we're using 'Publish' in CAP are we?
I thought that we just had Approval


this is OK for now, I'm pretty sure using Dict won't work without a few hacks in Patchwork because it does not trigger a re-render.


Right. I would leave this untouched as the original code was correct.


`vendor` in place of `vendors` ?


> This gives me Record not found! error. What am I missing here?

What exactly gives that error? The next page after the self.next = r.url(method="") ?


thanks for the commit


this is internal emulator config. any reason to use size-named variables


> for prepop, the approved_by field is 0, which comes from here: flavour@1b8ad47#diff-490b78a7772eee613a7f16277d7ffe14R5763

This shouldn't be since table._tablename should be in settings.get_auth_record_approval_manual() no?


@ajgarlag Please check https://github.com/ansistrano/deploy/commit/2eb0c1ffc37be1287eddddce10437da9547d3f98 with the ` | default(omit) ` filter for the AWS credentials

Any concerns with it? It has been out for almost a year now and pretty much everybody should actually be in 1.9 at the moment


I have one concern, once phantomjs is started with force 'Host', does every page.open from now will use that static string as SNI to establish connection? Does all page.open send requests go through one same TLS connection? We will have Host header and certificate SANS cross-check, which will reject mismatch request with a 403. We will have SNI/Host header mismatch, which will be blocked by our server at HTTP level with a 403.

The cleanest way is that we visit a url with page.open, we will use the domain name as SNI to establish the connection, and all subsequent requests going through the connection is using a Host Header matches SNI.


@flavour The error is because of authorised = self._permitted("publish").


in Python, default args are mutable. So if someone creates a BaseApiResource with the default `endpoints` value, then does `self.endpoints.append('x')`, that will get added to the default argument for other BaseApiResources created in future

Usually the best thing to do when default args are lists/dicts is to default to `None`, and in the `__init__`, replace `None` with `{}/[]`.


@flavour Yes but it is 0


In the future you could expand on your commit messages?  What updates to the decode function did you make and why?


> this condition a909bbf#diff-59bf1eeed7c39491fc28b7a977ef8b0cR1763 is true, even if the approved_by is 0, ie. it shows "Publish Alert" button, which is correct?

I think this is incorrect: approved_by == 0 should not show the Publish button since already Approved
So this should be rewritten as if record.approved_by is not None and \


@flavour so I used approval framework earlier, the name was only publish?


thanks for the explanation.  I agree with your reasoning for not handling/exposing this, :+1:


Erm, that should have been #17910 instead of #17735. :sweat:


Generally good practice to docstring your test functions. Two parts to this:

1) The first line of the docstring (e.g.
```
"""The first line
```
but not
```
"""
The first line
```
Will be used as the name of the test in the Nose output. It helps to write a more verbose (english) description of what the test is doing.

2) Write a paragraph about what the test is doing, assuming, and checking. This doesn't need to be a novella, but it's good practice to describe exactly what your test is doing, since test code tends to rot quicker, and be harder to follow than normal code.


@cyrrill

Great post.  For the rest of the community, I apologize for losing my temper.  I will admit, I would have been watching from the sidelines had this not happened.  There are many talented people working on this project, both in the main project and the downstream forks.  I don't feel I have the background to really contribute more than they have.  However, this issue has broader ramifications and has made me feel I had to speak up or let us slip deeper into chaos.  I really dislike the fact that a few people have manufactured a crisis for the sole purpose of coming to the rescue.  I normally would like to see the tech discussion as far removed from the political spectrum as possible, but the very act of making the change, based on a *supposed* slight, sets a bad example.  Google had a great deal of clout in the computer world, and this could be seen as a precedent and opening the door for others to insert their personal agenda into a technical discussion.
We must understand that just because someone is offended does not make the action or words offensive.  While it is a good idea to avoid blatant slights, this is really pushing the boundaries.  I think we should look at the technical and standards ramifications of this as well.  The standard, for good or bad, has been to make the extension an subset of the program where possible.  The most logical choice was picked as .bro.  This was not done for the "brosphere" as some would like to make you believe, but because this was must effectively associated with the project name.  If you believe there is some injustice in the naming convention, it should be brought up as such and addressed.  So far I have only seen allusions to some form of harm that has no facts to back up the claim.  Without any facts and debate we are in the realm of speculation and knee-jerk reactions.  It is in poor practice to simply make technical changes because of some unfounded and unproven statements.
For these reasons, I would kindly ask the developers to reverse the decision.  If you have a technical, or founded reason for future change, I am all for it.  Ultimately it is the developers who have the final say, but I would implore them to rethink the basis for their decision.


Sounds good, I agree that we should wait until we change it, :+1:


Let's just name this babeltrace_posix_fallocate()

Here is my proposed implementation which should provide the same semantics as posix_fallocate():

```C
static inline
int babeltrace_posix_fallocate(int fd, off_t offset, off_t len)
{
        int ret = 0;
        ssize_t copy_len;
        struct stat stat;
        char buf[BABELTRACE_FALLOCATE_BUFLEN];
        off_t i, file_pos, orig_end_offset, range_end;

        if (offset < 0 || len < 0) {
                ret = EINVAL;
                goto end;
        }

        range_end = offset + len;
        if (range_end < 0) {
                ret = EFBIG;
                goto end;
        }

        file_pos = lseek(fd, 0, SEEK_CUR);
        if (file_pos < 0) {
                perror("fseek");
                ret = errno;
                goto end;
        }

        ret = fstat(fd, &stat);
        if (ret < 0) {
                perror("fstat");
                ret = errno;
                goto end;
        }
        orig_end_offset = stat.st_size;

        /*
         * The file may not need to grow, but we want to ensure the
         * space has actually been reserved by the file system. First, copy
         * the "existing" region of the file, then grow the file if needed.
         */
        for (i = file_pos; i < min_t(off_t, range_end, orig_end_offset);
                        i += copy_len) {
                ssize_t copy_ret;

                copy_len = min_t(size_t, BABELTRACE_FALLOCATE_BUFLEN,
                                min_t(off_t, range_end - i,
                                        orig_end_offset - i));
                copy_ret = pread(fd, &buf, copy_len, i);
                if (copy_ret < copy_len) {
                        /*
                         * The caller must handle any EINTR.
                         * POSIX_FALLOCATE(3) does not mention EINTR.
                         * However, glibc does forward to fallocate()
                         * directly on Linux, which may be interrupted.
                         */
                        ret = errno;
                        goto end;
                }

                copy_ret = pwrite(fd, &buf, copy_len, i);
                if (copy_ret < copy_len) {
                        /* Same caveat as noted at pread() */
                        ret = errno;
                        goto end;
                }
        }

        /* Grow file, as necessary. */
        memset(&buf, 0, BABELTRACE_FALLOCATE_BUFLEN);
        for (i = orig_end_offset; i < range_end; i += copy_len) {
                ssize_t write_ret;

                copy_len = min_t(size_t, BABELTRACE_FALLOCATE_BUFLEN,
                                range_end - i);
                write_ret = pwrite(fd, &buf, copy_len, i);
                if (write_ret < copy_len) {
                        ret = errno;
                        goto end;
                }
        }
end:
        return ret;
}
```

Comments welcome


this should be
```
export LUA_LIB="$($(tc-getPKG_CONFIG) --variable=INSTALL_CMOD lua)"
```
afais


Woah.  Did this come from a .NET test.  I would be more comfortable with a different encoded string.  The one here is on the edge of being inappropriate.


You can use `assert_equal` (from nosetools) to make pythonic/pep8-compliant assert calls. Good practice to prefer these, since they are equivalent to the UnitTest non-pep8 ones.


@mrtracy I didn't find a simple data series class in the metrics or protos files, but let me know if there's one I should take a closer look at


is `virtual/pkgconfig` missing here or does some eclass pull it in directly?


If you haven't collected the case details for the general district then you should probably wait so we don't repeat efforts. I'll give you my data and we can cross check it with 2015 to see whether all cases are in there or not.

I may have gotten a bit ahead of myself in claiming two days as I'm now up to about .6 million queries and I must throttle by about 1.5 for each iteration, so I ended up having the same issue as you. I know that if I submit more than one query in less than .5 seconds then I'll meet a Captcha. :/

My approach is linked above --the code has been amended a bit and I have yet to update the uploaded version but the gist is there. I solve the Captcha in the browser and then for each court, I generated a sequence of business-day search urls back to 2002. In each iteration, I look up the hearing for the date, get all of the case links (including ones on "Next"), and then scrape the full case details. In brief, I am only keeping the full case details.

It's a hastily written double loop that isn't parallelized. If I divide up the courts among separate IPs then I can substantially cut the search time. As a side note, do you know if I'll run into issues if I have multiple browsers on the same IP address querying the website?

And sure, I'll gladly join in the efforts! :)


@leticia acho que vale uma validação para garantir que nenhuma mobilização seja criada sem `slug`


Did you want to keep this console.info in here?


放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛放对方是但是 佛挡杀佛


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 675](https://teamcity.mesosphere.io/viewLog.html?buildId=58118&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:13


I'd add a comment/log above this line explaining exactly what you are checking here; something like "Expect delete() to configure the plugin parameters"/"Verify that delete() configured the plugin parameters".


GG


Unused variable?


LGTM


Thanks, for taking a look! I see you've fixed some of the mentioned recipes in 9994fdd.
However, you didn't touch the following ones:

app-misc/jq/jq-1.4.recipe
dev-vcs/bzr/bzr-2.6.0.recipe
games-emulation/bsnes_libretro/bsnes_libretro-git.recipe
games-emulation/retroarch/retroarch-1.0.0.3_beta.recipe
haiku-apps/beshare/beshare-2.31.recipe
haiku-apps/friss/friss-0.8.0.recipe

Was it intended?


Gg++
Le 13 oct. 2015 8:05 PM, "Ly4m" <notifications@github.com> a écrit :

> GG
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Cookorico/Cookorico/commit/3c5ed8b68c1077709740375de142f423d1c55b71#commitcomment-13747934>
> .
>


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 677](https://teamcity.mesosphere.io/viewLog.html?buildId=58120&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:06:39


Here it is


Pff, can happen. Don't worry about it.
I think we need to come up with a suitable punishment for iawriter though :p


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 676](https://teamcity.mesosphere.io/viewLog.html?buildId=58119&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 190 Build time: 00:07:09


Add the desert_sand craft recipe please ;)


Yes, stereotools should be able to kill mid and keep only side with mlev option.


@githubato Why is this volume necessary?


Shouldn't this be `User.Model.where('email', email)` or `User.Model.where({email: email})`?


Thanks!


Can we have different errors for when a user doesn't exist, and it's an incorrect password?


Late but done. Created tha tag 1.0.0, stable.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 678](https://teamcity.mesosphere.io/viewLog.html?buildId=58123&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:04


@gaearon great talk! 👍🏼


As of this commit,

I pushed code for
1) floating tasks
I define them as tasks with no date, no starting time and no ending time.
The category will be set to "floating" by Task.java with the help of Checker.java.
Input command:
add title, description, priority

and

2) deadline tasks
The category will be set to "deadline" by Task.java with the help of Checker.java.
I define them as tasks with no starting time.
Input command:
add date, ending time, title, descripton, priority

where date still follows the dd/mm/yyyy format, and ending time still follows the 4-digit 24-hour format.

Important note: I currently do not know how to sort the floating and deadline tasks in the schedule file (they are all over the place, for these two types of tasks. They seem to be at the top at ANOTHER ONE user input command AFTER they are added.)

I have included the user input commands:
"show floating" and "show deadline" (without the quotation marks),
to search for such tasks using the category attribute (variable) of Task.java, via SortAndShow.java

I have also allowed the adding and deleting of tasks to currently accept "undefined" as the date.


I'm not entirely sure where the best place for these dependencies are, but here are a few data points:

- Facebook's fixed-data-table component puts the `react` dependency in `peerDependencies`. https://github.com/facebook/fixed-data-table/blob/cf28c0e7/package.json#L7
- rackt projects like react-router seem to put the `react` dependency in `devDependencies`. https://github.com/rackt/react-router/blob/0f648484/package.json#L55
- Twitter's velocity react puts it in both `peerDependencies` and `devDependencies`: https://github.com/twitter-fabric/velocity-react/blob/ad6544f9/package.json#L30
- Some projects, like @gearson's react-dnd, put the `react` dependency in both `peerDependencies` and `devDependencies`. https://github.com/gaearon/react-dnd/blob/5e67908f/package.json


Any access methods are permitted in some circumstances.  The point of this commit is that a 1.0 (non) namespace only allows protected access.  Any other access level means you have at least a 1.1 component.

david jencks

> On Oct 13, 2015, at 1:48 PM, Ferry Huberts <notifications@github.com> wrote:
>
> I see this commit passing by.
>
> What about package protected lifecycle/inject methods?
> I do hope that is allowed.
> If the spec mandates protected then that sucks for unit tests.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/djencks/bnd/commit/481fdc0156cf9b4a897602b9dd7ea2027fbece68#commitcomment-13747540>.
>


A general point about UT'ing; don't write your UT with an assert for each line in the function under test. That couples your test to the function's implementation, which makes the tests brittle (a change to the function under test requires all the UTs for that function to be updated).

Instead, you should think about testing the critical function of the case that you're covering. In this case, do we care if container_remove is called? I don't think so; the passing test is covering that. In this case, we're explicitly checking that an error in remove_profile is caught, and doesn't bubble up to the caller.

I'd remove all these asserts, and replace them with a comment explaining that if the assert wasn't caught, the TC would fail.


@dayvson: would be nice if you used Git tags for future releases; then we'd be able to use https://github.com/dayvson/grunt-static-inline/releases


This was done by Android Studio while uploading. (Selected cleanup checkbox)


@elifeasley update on this?


Hey please I am currently trying to convert my 3D solidworks humanoid robot xml model to URDF. I downloaded your code but for some reason I cannot get it to work. I'm using ubuntu 14.04 and for some reason it would not recognize the simmechanic-to-urdf folder as a package. I have sent close to 12 hours on these problem. I am very sure it is something simple. I have gone through all the ROS tutorials, but I still haven't figured it out.Any hints on how to compile your program will be useful. Thanks in advance and I'm looking forward to your reply. My email address is ezeob002@umn.edu.


Hi, do you have the genre link creator script for mp3 releases?


adding link to header elemets for more comfortable of browsing


Note that in some failure TCs we do care about which functions are being called; we may want to assert that cleanup_on_fail() is called, or that commit_data_on_success() isn't called. But I don't think that's the case here.


When I grow up, I want to be like my brot,her son1


Do you insist on this?
Because there will be cross initialization errors on `const qreal ratio` & `QString elapsed_txt`.
```
gui/properties/propertieswidget.cpp:438:22: error: jump to case label [-fpermissive]
     case PropTabBar::TRACKERS_TAB:
                      ^
gui/properties/propertieswidget.cpp:372:17: note:   crosses initialization of ‘QString elapsed_txt’
         QString elapsed_txt;
```
It can still be done, be the code could be harder to read...


why is this correct but the one above I commented is wrong? @ravirnjn88


lg


Hmmm. Why do we need this, given the "NoEmailer" type? Does there not have to be changes in dependent code which check for nil pointer?


I think @mattmuroya and @jkbuckeye's comments pair well together. Exigence will help you pinpoint values and practices that shaped the proposal and dev of the canvas element. Yet, your focus on indie game dev will help narrow the focus of your history and zero in on particular communities.


Looks good to me!


Beskrivning saknas för L34!


I think this should be okay (let me know if I'm misunderstanding)

1. Automatic autocompletion requests (e.g. as-you-type) are buffered by a timer, and so will only pop up after a certain idle time,
2. Manual completion requests still have a relatively small window in which they can be canceled by document movements,
3. Once a request has completed, if the user begins typing all filtering etc. occurs on the client (and so no RPC requests are triggered there on, unless the user backspaces beyond the initial completion request token)

I think the behaviour should be modeled around the assumption that the popup is actually displayed immediately. So, if a key is pressed that would normally escape or cancel that popup then we should cancel the request (ensuring the popup is never shown). What do you think?


I prefer `@patch` decorator to `with patch()`, as it reduces indentation. Particularly important as we're using pep8 width of 79.


You can just declare 2 mutable arrays separately.

  NSMutableArray *stdoutLines = [NSMutableArray new];
  NSMutableArray *stderrLines = [NSMutableArray new];

Putting them in an array seems unnecessary.


Should probably use `var` to avoid globals and be more consistent with other yarn components.


@dkniffin I didn't know about it. Do you know since which version minitest use `after_run`. Maybe we can do some workaround with `respond_to?` so knapsack can support both minitest versions?


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1373 of 1373 tests passed)

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


In general please go through the diffs and align the "*" with the variable, not the type.


so weird - did I do that? Sorry!


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 679](https://teamcity.mesosphere.io/viewLog.html?buildId=58124&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:03:48


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 680](https://teamcity.mesosphere.io/viewLog.html?buildId=58125&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:03:59


Well if you write the fields with out the type you can use https://bitbucket.org/cuchaz/enigma/src/e49f4e5bb42100cc044236c321e8bd9bb1adc02f/src/cuchaz/enigma/MainFormatConverter.java?at=default&fileviewer=file-view-default to fix the missing type information.


this is ES6 object literal shorthand -- it expands out to {email: email} (it makes the key be the name of the variable)


Accepted.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 681](https://teamcity.mesosphere.io/viewLog.html?buildId=58127&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:17


I personally find that particular warning mostly pointless, so we might consider disabling it in the pylint configuration.  (Outside the scope of this PR)


@alexandradepalma has a great point about interrogating what's been deemed as "intuitive." Really that's an assumption about what prior knowledge, skills, and experiences people bring to the proverbial table.

@AnnaIrish, SVG would prove to be an interesting comparison. @burke552, you may find that SVGs may be used frequently in some way. Yet, they are a distinct element of their own, so such a move could widen the scope too much.

Allinall, good things to chew on here. I would start digging into the W3, WHATWG listservs for discussions about canvas and also game dev.


*daddy_head = (**daddy_head).next; or *daddy_head->next;


That is too substantial a change to be allowed without higher level tests than are currently implemented.  Changing a single assertion from assertNull to assertTrue is not enough.

I'd expect to see several different test scenarios where changes are created, pushed, and built, and where the old behavior is clearly detected in the scenario, with comments (and eventually code) showing how the new behavior is better.


@trotzig @lencioni I'll admit I don't have a clear idea about where these should live either; I was reacting more to the warnings NPM was giving me when running npm commands in regards to the upcoming release of npm 3.

If y'all want to punt on this for now, I'm happy to revert the commit.


Also, consider using "const" format like `MAX_AREA`.


So my understanding would be that the buffering will now change from whatever the configured timer is (I think it defaults to 200ms?) to that value + the round trip time for the completion request. Is that correct? If so are we okay with that?

BTW, as I recall the code in the C++ completion manager that manages this is pretty complicated so nothing I'd want us to do here (i.e. I advocate for the most minimal change necessary including none if we can't feel good about a minimal change).


@jonathanong there isn't a new release after 31c6a5e7dd08ac80555f0f5a1cb7b3cd97ff527e, so this should be 2.0.0


Далее следует перенести функции роутера в контроллер, вынести регионы из MyApp


Detta borde funka.


first edit


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 682](https://teamcity.mesosphere.io/viewLog.html?buildId=58129&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 190 Build time: 00:04:06


It shouldn't be too complex. I'm picturing something like this:

```js
function validateShape(shape) {
    var d = new $.Deferred();
    var area = coreUtils.changeOfAreaUnits(turfArea(shape), 'm2', 'km2');
    if (area > maxArea) {
        areaWarning(area);
        d.reject();
    } else {
        d.resolve();
    }
    return d.promise();
}
```

I'd be curious to see if this works. I have not tested it.


`host` and `protocol` aren't set per endpoint, at least in the endpoints behavior.  They're set on the implementing element, and all the endpoints of that element use the same `host` and `protocol`.  Or does the sdk element work differently?


```free(temp);```


What is the "dirty fix" trying to do?  `jmemmgr.c` uses functions in `jmemansi.c`.  Pulling `jmemansi.c` out of the final library leads to linker errors like in #4877 and #4941.


This looks like a bug in Pylint, doesn't it?  Shouldn't this warning be issued when a loop variable is used after a loop that might not have been entered at all?


lg


Preporucila bih da se "BIT_BAY" definise kao konstanta u nekoj klasi (npr. Constants). Takodjer, ne bi skodio ni neki ConfigurationHelper koji bi enkapsulirao dobavljanje konfiguracijskih stvari. MailHelper moze na osnovu tokena izgenerisati citav URL, nema potrebe da se to ovako proslijedjuje (opet enkapsulacija).


shouldn't it be StringUtils.isNotBlank()?


This doesn't seem to work.


So if I use brackets, then it will work? @ravirnjn88


I'll give it a try.


`net.SplitHostPort`


Hrm? Like, two separate errors in those two cases? That is [bad security practice](http://www.troyhunt.com/2012/05/everything-you-ever-wanted-to-know.html), since it gives away valid emails.


@iracic You should ask on gitter. You have to test with a version that actually includes the commit.
```
$ ./scala-2.12.0-M3/bin/scala -Dscala.repl.welcome=hi
hi

scala> :quit
$ ./scala-2.12.0-M2/bin/scala -Dscala.repl.welcome=hi
Welcome to Scala version 2.12.0-M2 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_60).
Type in expressions to have them evaluated.
Type :help for more information.

scala> :quit
```
I have no idea why it's not already working in M2.


@nmccready did you mean `isDefined(oldModels)` instead of `isDefined(oldModel)`? I see this statement a few of times in markers.js. It doesn't seem to make sense, since oldModel is being defined on the same line. The result is that oldModel is always undefined, even if it is not.  (I'm trying to update my fork and this additional line seems to be breaking it because updateMarker is not getting called)


Both @mattmuroya and @AnnaIrish raise up good points to consider. Tracing print media and web uses of font families should prove to be quite interesting. One thing to tack on to Anna's comment is that Font's aren't coded as so much they are imported in multiple ways via CSS in particular. It seems that your project can come to terms with the typographical boom on the web (see [Google's font cloud](https://www.google.com/fonts) and also opensource cloud spaces like [https://fontlibrary.org/en](https://fontlibrary.org/en)). They are resource hogs, though; especially when using Google's cloud-based fonts. Allthistosay, there are page-loading and readability and usability and even accessibility implications to consider when typography and font-use are considered in the design process.


That's an addition to the endpoints-behavior, there are a few other additions too.


Wow... good to know, your approach is way cleaner!


:+1: To this whole thread. Good suggestions, everyone!


I've always been switching between `vendor` and `vendors`, until I get confused which one I chose! hahahah!

I guess changing everything to `vendor` once and for all is better! Thanks @g13013 :smile:


Issue5249-FixHWBBEngRef (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (835 of 835 tests passed)

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


@trotzig Leaving the call in yields this error:

> ERROR: 'Warning: ReactDOMComponent: Do not access .setState(), .replaceState(), or .forceUpdate() of a DOM node. This is a no-op.'

I think the change in behavior is covered in [the upgrade notes for React 0.14](https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html), specifically:

> The other big change we’re making in this release is exposing refs to DOM components as the DOM node itself. That means: we looked at what you can do with a ref to a React DOM component and realized that the only useful thing you can do with it is call this.refs.giraffe.getDOMNode() to get the underlying DOM node. Starting with this release, this.refs.giraffe is the actual DOM node. Note that refs to custom (user-defined) components work exactly as before; only the built-in DOM components are affected by this change.

> **This change also applies to the return result of ReactDOM.render when passing a DOM node as the top component.** As with refs, this change does not affect custom components.

(emphasis mine). You might be right in that the docs may be out-of-date for changes in 0.14.


Do you use this feature?


This appears to be in master, and I've just updated sickrage, but I'm still getting the error.
```
BRANCH: (master) / COMMIT: (30435190ef8880901df555bcda0d46902ea81fb5)
Python Version:	2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2]
Error:
2015-10-13 14:33:40 INFO     SEARCHQUEUE-MANUAL-158661 :: [KickAssTorrents] :: Unable to find a download for: [placeholder - 5x14 - New World Order]
AASSLError: hostname 'kat.cr' doesn't match either of '*.kickass.so', 'kickass.so'
AA    raise SSLError(e, request=request)
AA  File "/home/transmission/.sickrage/lib/requests/adapters.py", line 431, in send
AA    resp = super(CacheControlAdapter, self).send(request, **kw)
AA  File "/home/transmission/.sickrage/lib/cachecontrol/adapter.py", line 46, in send
AA    r = adapter.send(request, **kwargs)
AA  File "/home/transmission/.sickrage/lib/requests/sessions.py", line 576, in send
AA    resp = self.send(prep, **send_kwargs)
AA  File "/home/transmission/.sickrage/lib/requests/sessions.py", line 464, in request
AA    return self.request('GET', url, **kwargs)
AA  File "/home/transmission/.sickrage/lib/requests/sessions.py", line 476, in get
AA    resp = session.get(url, timeout=timeout, allow_redirects=True, verify=session.verify)
AA  File "/home/transmission/.sickrage/sickbeard/helpers.py", line 1611, in getURL
AATraceback (most recent call last):
2015-10-13 14:33:40 ERROR    SEARCHQUEUE-MANUAL-158661 :: [KickAssTorrents] :: Connection error to getURL https://kat.cr/usearch/?q=placeholder+S05E14&field=seeders&category=tv&sorder=desc&rss=1 Error: u"error hostname 'kat.cr' doesn't match either of '*.kickass.so', 'kickass.so'"
2015-10-13 14:33:40 INFO     SEARCHQUEUE-MANUAL-158661 :: [KickAssTorrents] :: Performing episode search for placeholder
```


Overall, Im wondering how you can use your history as a way to perhaps better understand how the CSS module that annotated came to be. What functionality in it has come from past CSS-writing experiences?


Yes, thanks. I hadn't reviewed my rebase yet.


Is this still relevant PR?

The implementation side is probably robust enough now, but the tests I'm not sure whether to include or not. In the worst case the compilation would just fail on something like `kId not defined`.


Для такого модуля нужен докстринг с описанием того, какую задачу решает.
Если это скрипт, то оформить конструкцией:
def main()
     ...

if __name__=='__main__':
    main()

Все функции также следует снабдить докстрингами, после этого можно будет исходник анализировать.


Thank you for the information. I'll try to incorporate it to my fix.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 683](https://teamcity.mesosphere.io/viewLog.html?buildId=58131&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:01


You forgot to remove unnecessary spaces. :scissors:


Still the error is there.
```
[kislay@localhost ch_2]$ g++ list.cpp -o list
list.cpp: In function ‘void delete_node_start(node**)’:
list.cpp:20:23: error: request for member ‘next’ in ‘* bighead’, which is of pointer type ‘node*’ (maybe you meant to use ‘->’ ?)
  *bighead = *bighead->next;
                       ^
```


no, no era abogados, reparalo


Please use four-space indentation, following PEP-8


I've read somewhere that they have a special, header only package for only building native modules, starting from 4.0+. It woluld be best if it resolve to that one, wouldn't it?


I was able to get a floating task to have its date, starting time and ending time changed using the usual change commands, after working on it.


fixes https://github.com/appium/appium/issues/5721


I'm pretty sure these should still be `peerDependencies`.

NPM 3 won't install them by default but it's exactly the point: it's up to the user to choose appropriate versions. This new behavior ensures user won't get duplicate React.

You shouldn't worry about the warning. It doesn't mean `peerDependencies` need to become `dependencies`.


It's there in case some but not all of your routes in a given sdk need to use 'https', I don't use protocol but I do use host when I'm working on an api with partial progress being hooked up on the backend, so a mix of fake and real data.


ok, thank you


Sorry about that; I'll try to make my commit messages more useful in the future.


How can SMP be tested if you are only testing with 1 thread?


Kannski of snemmt að gera fyrsta commit áður en fyrsti cycle af kötunni er tilbúinn, en hér er grunnur


Raise the version number to at least 8.0.0.2.0


@HeloisaSicupira would you mind taking a quick look at this and providing your thoughts by the weekend? Thanks so much :+1: :8ball:


check "LosHandler::Update":
TP enabled: http://home.arcor.de/jk3064/TP_enabled.jpg
TP disabled: http://home.arcor.de/jk3064/TP_disabled.jpg


1.7.2 was already released, it should be 1.7.3-BETA


The built-in `cond->` works just as well as `when->` here, so there's no need to pull in this extra dependency for clojure 1.5 and beyond. Now that clojure 1.7 is stable, is it worthwhile maintaining backwards compatibility with pre-1.5?


Why change all attributes? You only need to change default


It is unsafe to use `gets`, which might lead to unexpected buffer overflow.


Don't limit sequences by type (in v9, this type dissapears)


Fix #42  Fix #43


This seems to be a problem for CREATE TABLE as well. There is a TODO for CREATE TABLE:
        // TODO: refactor this to avoid creating an empty table on failure
        shardManager.createTable(newTableId, columns);
        shardManager.commitShards(newTableId, columns, parseFragments(fragments), Optional.empty());

So we need to fix both CREATE TABLE and ADD COLUMN?


@mythmon do you think there is a problem? Why the tests been failling?


If you think there's value there that's all good, but it stuck out as possibly unnecessary or confusing.  I could see a dev getting screwed up because some endpoints are configured differently than others, whether originally by mistake or on purpose.  My inclination is to say that all endpoints have the same host and protocol for simplicity and interoperability with other behaviors, but you've probably spent more time with this problem!


Why not remove

```
usort($this->data[$key], array("Event", "cmpByPriority"));
```


If you're going to change something like this, I think it would be cleaner to just delete the old line rather than leaving behind comment clutter. We can always see what the old value was anyway by exploring the Git history.


are these the "standard" test cases that will help us guide all implementors to make consistent compilers?


I love this project idea. My only concern is about how you can conduct this historicizing project while keeping writing markup/css at play. Are you better understanding images as written documents, too, since they have conventions like headers that tell other tech what to do with them upon a rendering task? How did LZW play into this process of image use on the web, or even the desire to use more images? I see these questions in keeping with the one's suggested by @mattmuroya as well. In essence, how can you put it to work within the context of web writing?

I would suggest searching through the W3 and other standards body listservs for any discussions about this compression tech. Maybe even our own Charles Babbage Institute here at UMN.


Can we change this to be a percentage of max volume somehow?


Yes.  This is because we now roll over the geneartion counter after 32 positions instead of 64 and there are 37 test positions in bench.


Hi,

This commit breaks it for me.

I get the error PHP Fatal error:  Interface 'Zend\\Hydrator\\HydratorAwareInterface' not found in /var/www/html/PurpleApi/vendor/zfcampus/zf-apigility-doctrine/src/Server/Resource/DoctrineResource.php


Are you reverting my changes in the Dutch installer texts on purpose? :sweat_smile:


![qq 20151013194324](https://cloud.githubusercontent.com/assets/2135445/10464623/c71bba06-71b8-11e5-90e5-f43c0b036cd4.gif)


This could prove to be an interesting narrative to construct!


Hi Brady
I did not find the UI to test this script.
Patient -> summary -> Documents do not blank screen.
/patient_file/summary/demographics.php line 227 state " ../upload_dialog.php Not yet implemented"


shouldn't that be `uint8_t`? or is the `_t` bit posix only.


this.currentMusic =  ko.observable( data.current_music ? new Music(data.current_music) : null)


Overall, some great work to be done here! I would also consider, as you research and develop this project, how you can translate it into a DITA project. Or, at least, just keep that in mind, and we can bounce ideas around as you make progress.


I think the protocol option could be tossed, I do find the host useful, but I'll keep it in mind. Could other behaviors use the same endpoints object and just not do anything with a 'host' property if they see one?


= (1..tag_count).to_a.sample 3


load `.bowerrc` json and lookup for vendor directory ?


I think looking at CSS use in a particular field would be more of a rhetorical design analysis, where as looking at how a particular tag is used may be more technical. I think the later approach would be less overwhelming and easier to write a specific history.

If you write more of a design analysis for a specific field, it may be difficult to find sources. Each website has discussions around why their website looks the way it does when they're being created. As far as the news industry goes, I know when the Star Tribune did it's redesign they looked at other news websites and noted the features they liked, also while considering the user. Lots of whitespace, many articles on the homepage, etc. The CSS is made to fit these design decisions, not the other way around. Many to most CSS features are integrated into making the 'idea' for the website real and functional. I think it would be hard for you to find a point of focus and it would be better to pick one element to focus on.  OR also focus on a specific design decision (Why are all the news sites mostly whitespace?)


I think the fact that it's uncertain is enough of a reason to be wary!


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 684](https://teamcity.mesosphere.io/viewLog.html?buildId=58134&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:04


Are you referring to the red arrow  or just want to test out the merge funtion


... sprt with 23 threads at [-3,1] seems very costly ...


@tuxoko your right.  I was confused because this function used to use `iget_locked()` instead of `new_inode()` which did set I_NEW.  Which is why I originally added the `unlock_new_inode()` call in the error path.  Things have changed since then!  Thanks for keeping me honest, I withdraw my objection!  This LGTM.  If you can refresh it with a good commit comment I'll get it merged.


But could reduce the adoption rate if the minimum requirements are more high than needed.


>Do you insist on this?

Not. I don't want to think about it now. It refers to the part of code that should be subject to redesign in the future. I'll think about it at the time.


I think this should be prefixed with the name of the role `openvpn_` which is best practice for ansible roles.

Also, this doesn't support idempotent tasks. Ideally there would be a check to see if a configuration already existed. If a configuration didn't exist then they would be initialized. If a configuration existed already, it would sync from s3.


The red arrow means we made changes in that line and a rollback would remove it.. Look good to ne


I think this should be prefixed with the name of the role openvpn_ which is best practice for ansible roles.


@Stefano80 https://groups.google.com/forum/?fromgroups=#!topic/fishcooking/PYBswwYbAOs


```*bighead = (*bighead)->next;```


I think these should be two separate tests rather than one combined with `~or`.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 685](https://teamcity.mesosphere.io/viewLog.html?buildId=58135&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:03:53


Why did the code above get deleted?


TeamCity pull requests :: netty-tcnative [Build 29](https://garage.netty.io/teamcity/viewLog.html?buildId=2265&buildTypeId=pulls_netty_tcnative&guest=1) is now running


TeamCity pull requests :: netty-tcnative [Build 29](https://garage.netty.io/teamcity/viewLog.html?buildId=2265&buildTypeId=pulls_netty_tcnative&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:41


Is this a sufficient check, or should I verify that `cxx_host == "g++" || cxx_host == "gcc"` @jfirebaugh?


published as 2.0.0


oh. Yup. Now it is working fine. Thanks!!


You will find, I am guessing, that it's wound up in all of this grid framework banter, practices, and frameworks. Dilger's piece should come in handy, since aspects of grid flexibility and responsive control are important values to examine further. Really, you can jump right in where Dilger left off with flexbox. Right off the top, I'm wondering how flex is different from adaptive or responsive, if at all. Conceptually and functionally, how are they different or similar?

You should also scour the WG email listservs for talk about flexbox. Also, be sure to check out and subscribe to this email newsletter and the people behind it: [CSS Layout News](http://csslayout.news/). Also, search sites like codepen.io for any code snippets to examine in detail.


That's a good point. We can support 1.5+. Thanks Bo!


mogao si imati jednu metodu findHotelsByCategory(String category, String text), s obzirom da su ti imena kategorija ista kao i imena atributa


This is resulting in a couple of AttributeErrors when building packages.  Should we check that self has the attribute first?


I see what you're saying; do you think there's a way to preserve that functionality?


@chrisradek Great, thanks for looking into this. Let me know how else I can help. This is fairly easy to test by hand, as well: Use the sdk to generate a presigned url for some metadata (using metadata property names with capitals), and then use curl or some other tool to PUT a file to that URL — S3 will reject it. But if you edit the URL to change the capitalized letter(s) in the metadata query parameter keys to be lowercase, S3 will accept it.

It does seem as thought metadata for S3 objects must be lowercase — when setting or editing metadata through the aws s3 web console, the property names are lowercased when you save.


```
 void delete_node_start(struct node** bighead)
 {
-       *bighead = *bighead->next;
+       // Memory leak here. Prev head should be freed.
+       // That is the reason for temporary variable too.
+       struct node *tmp = *bighead;
+       *bighead = (*bighead)->next;
+       delete tmp;
 }
 ```


Nice find. This site is use prevalently by frontend folks, and I think it would prove interesting to trace the trajectory of those updates that you mention; especially as they relate to changes made with particular CSS+browser+box model behavior.


ah ok


should be wrapped in double quotes to be consistent


Zdravo Nejra,

Hvala na komentaru.
Moram reci da sam prije pushanja koda pullala i kolegin jer tako izbjegnem konflikte kasnije, tako da mi je sada i njegov kod za verifikaciju e-mail adrese korisnika prilikom registracije. U svakom slucaju on ce vidjeti ovaj komentar.

Ja sam radila kao sto sam napisala u komit poruci PayPal basic, ne vezan za realne podatke iz baze, model Purchase  koji cemo koristiti za kupovinu, sada radim na tome.


Yep we can.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 686](https://teamcity.mesosphere.io/viewLog.html?buildId=58136&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:07:25


OOooo, really dig into those discussions about naming. That's where things can get quite interesting. The writing practice framework should help guide your analysis, too.


@dayvson: you could get this from package.json's description so that you don't have duplicate stuff.


I think we should stick with multiline syntax:
```args:
  creates: "{{ openvpn_keydir }}"```


93653630-MultipleYearRunPeriodForTabularReports (JasonGlazer) - x86_64-MacOS-10.9-clang: OK (1905 of 1905 tests passed)

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


Not sure!  So you do actively use two different hosts for the same set of endpoints?  I just can't imagine how that must work.  I don't really understand the functionality, so I can't comment much on how to easily preserve the feature, although I'm not fundamentally against it if there is some use for it.


Thanks for the heads up. Compiling update now.


They are indeed!


mogao se napraviti query koji bi direktno na bazi filtrirati hotele sa trazenom cijenom, ovako cemo u memoriju ucitati nepotrebno sve


I suggest you to build with 4.9 toolchain


Ah ok, thanks. No problem then.
Didn't read to hard into the commit ;-)


It may be useful to scour Eppink's bib, so you can dig deeper into those particular important points. Eppink's article can perhaps serve as an example about how this history only skips the surface through broader events/things. How can your project zero in on some more particular use of GIFs in relation to what form of web-writing?


I don't think it is, that was just me being defensive. If one day someone wants to call it with null it'll still do the best it can.


Yeah that would be better. I'll make that change.


Keep in mind that your next project asks you to create documentation with DITA related to the tech you historicize. Maybe that will help you consider how to narrow your focus from broad history to a more focused history to understand some particular way GIFs are used on the web now.


Great! You did it.


```
args:
  creates: "{{ openvpn_keydir }}/{{item}}.crt"
  ```


Makes sense, especially since we don't allow partial updates (must update the secret and the expires time, not one or the other).


I used the latest PVTS 2.2, Python 3.5 and the update samples.

When I create a Windows IoT Core Python Background App project, the project always report "Unknown Python 3.5".  The  property FullPath is "UnknownInterpreter\86767848-40b4-4007-8bcc-a3835edf0e69\3.5"

The project will failed to run.  The only commonality is the GUID InterpreterId here.  Do you know what caused this failure?


That as  understanding, so don't create a method inside S3CRUD called 'publish' which is actually 'approve'
Under the hood we should just have 'approve' - the label inside the CAP workflows may be T("Publish")


```
args:
  removes: "{{ openvpn_keydir }}/{{item}}.crt"
  ```


wrap in double quotes


> for a given server, the credentials do not vary across authentication schemes

Should we have validation for that, or is that unnecessary?


wrap dest in double quotes


> The error is because of authorised = self._permitted("publish")

You are saying that that line gives 'Record not Found'?
Bizarre...trace inside the function...use Eclipse, it is your friend.


wrap path and owner in double quotes


@dariathedaria :heart: :cat:


> Yes but it is 0

Sorry, this has no context, no idea what this refers to


wrap name in double quotes


acaba olabilir mi?


That's a broad aim: how GIFs affect communication. Our writing practice framework should help you to understand that written communication is not monolithic. There is indeed a cultural-history to understand, but I'm wondering how you can situate your aim with GIFs as they are used in some particular way that is of interest to you. How about GIFs in online social media, such as Twitter, or now even FB. Why the sudden inclusion? Old and new crops up here.


```
with_items:
  - openvpn
  - udev
  - openssl
  ```


nede olmasın valla böle iyi aslinda mantik çok açik da kıullanmak lazım başka bi iş değil...


In c++ struct is a type of class and in class if we explicitly does not define its constructor then its constructor and destructor are automatically defined by the compiler. So no need of new and delete


Ah, thanks for including that. Now I understand better what the behavior is. In that case, I think the most pragmatic thing would be to remove the whole `describe('when the waypoint is re-rendered', ...)` block.


```
with_items:
  - python-pip
```


Something like this would let you temporarily configure the endpoint to grab from a local JSON file until the server is ready to receive it. It would be a hassle to have to put that json file up on the server before testing to see if everything worked, so being able to set it to localhost while the project is taking shape has been helpful

getSomething: {
      method: 'GET',
      host: 'localhost:3000'
      path: '/elements/sdks/my-sdk/someFakeData.json'
},
getSomethingElse: {
      method: 'GET',
      withCredentials: true,
      host: 'realserver:5039',
      path: '/some/path'
},


Do we need to really free this memory. I mean I have not allocated the nodes dynamically anywhere.


:+1:  @ravirnjn88


Kepe it


Again, :+1: to this thread. @alexandradepalma brings up a good cultural value: fun! GIFs certainly have a cultural association with fun, right?! It's certainly a potential avenue to explore. Are there whiffs of this in the WG email listservs, too?

Lots of good things to consider here.


Try it you will get segmentation fault..


Please write down meaningful GIT commit messages.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 688](https://teamcity.mesosphere.io/viewLog.html?buildId=58143&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:21


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 689](https://teamcity.mesosphere.io/viewLog.html?buildId=58144&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:20


Class Taken from Hcatalog Project. Only Function edited is getNext()


readonly


Just found out about https://www.polymer-project.org/1.0/docs/devguide/properties.html#deep-observation

So you can try observers: `{"json.*": updateProp}`  and do updates to parts of the json spec if Vega supports it...


I just moved this echo-reverse service code down to be near the code that uses it


missing return void


Just exercising one happy path and one sad path in this test


Class taken from Hcatalog project, getInput format was modified to use new input format.


Excellent! I like how this source helps you make the connection between desired functionality, values, and the skills exist in this old proposal. Also, how it's linked to print media practices, but as your project will show takes on its own form when implemented on the web.


You you are indeed reading both production data _and_ dev data on the _same page_, for example.  Got it!  Hmm!  Could also be fixed with better data fixtures in development.  I know that's not always easy to generate.


why is this css instead of stylus?


This function was modified to support record service records instead of HcatRecords.


Great, close reading here, @mattmuroya! I'm wondering if you can go back to comments or iterative emails or responses to this proposal to unearth some of your speculations.


Yup. That is true. I have checked. So that means it doesn't matter whether the nodes are dynamically allocated or not, a ```delete``` is never to be used.


what about multScale to follow the same convention as multTranslate ?


What's the magical go-present link to view this in all its glory?


Class taken from the Hcatalog project. I only kept the methods needing for serialization within a package.


This should be `compression_quality = (ch - '0');` shouldn't it?


No....allocate memory dynamically and always use delete...


The class "Action" should become a method, so help the store structure by calling the file "(catalog|admin)/event/checkout/change_order.php"


I like where you are headed with the connection between practicality and *reason*, which can serve as sites for deeper engagement with possible implications for such decisions.


okay.


Class taken from Hcatalog project. Modified package names where necessary.


what happened here?


lol, ya, "you have to build a custom JDK" is probably a show-stopper for
most people.

though let us know if there is anything we can add to the plugin api that
would make this easier

On Tue, Oct 13, 2015 at 1:07 PM, Rick Power <notifications@github.com>
wrote:

> Hey @nicks <https://github.com/nicks> and @bolinfest
> <https://github.com/bolinfest> I was reticent to make a pull request for
> this JSX support for two reasons:
>
>    - React-style js is not yet natively understood via latest shipping
>    plovr
>    - The browser.js script currently causes 'Method too large'
>    <https://bugs.openjdk.java.net/browse/JDK-8136834> error in currently
>    shipping JDKs 8 and 9, so you'd need a custom JDK build until 8u72
>    <https://bugs.openjdk.java.net/projects/JDK/versions/17669> becomes
>    available (even in early access). I am running this JSX support with my own
>    custom-built JDK that incorporates this method too large fix.
>
> At the same time, this commit its "mostly harmless™" in that the babel
> compiler would only be activated for .jsx files.
>
> To fully leverage the JSX support I added, you'd also need to also add
> this compiler pass <https://github.com/rgpower/react-closure-compiler> I
> forked from @mihaip <https://github.com/mihaip> (to teach the closure
> compiler about React js syntax). It's forked because of these reasons
> <https://github.com/rgpower/react-closure-compiler/commit/6b403>.
>
> That being said, I think you'd enjoy a pretty decent JSX experience, if
> you were to add the following to your plovr.cfg
>
>   "custom-warnings-guards": [
>     "info.persistent.react.jscomp.ReactWarningsGuard"
>   ],
>   "custom-passes": [
>     {
>       "class-name": "info.persistent.react.jscomp.ReactCompilerPass",
>       "when": "BEFORE_CHECKS"
>     }
>   ],
>
> and then run plovr with that react-closure-compiler.jar custom-pass in
> your classpath:
>
> java -Xmx1024m -cp react-closure-compiler.jar:plovr.jar org.plovr.cli.Main build myplovr.cfg
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/rgpower/plovr/commit/13193ab47792893f79054b7fa131f668ff8320ad#commitcomment-13746413>
> .
>


... make a check box somewhere and we'll talk.


I don't know how. Sorry.

On Tue, Oct 13, 2015 at 1:38 PM, Reaper1437 <notifications@github.com>
wrote:

> plz help me pllllzzzzz
> Inquiry Number 1210340863
> 10/13(Tues) 13:37
> Email is sleepy14378@gmail.com
> Really need your help
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/3dshax/ctr/commit/bcb3734b9a26d0fe7ef66f7d3814406fee797303#commitcomment-13747184>
> .
>


This class had private package scope, so it was directly copied.


Needed to copy this class because of private package scope.


Unless it breaks something...space between the ```&``` and 15? :) Same for the others below.


Nice! Backwards compatibility as a value. Standards bodies attempt to converge old new as gracefully as possible, but your project might explore what boundaries are in place.


Updated Storer info creation to support views.


Überarbeitung VO1-3, Grafiken entfernt (auskommentiert) und entsprechenden Text eingefügt. center-Umgebungen mit Formelinhalt wurden durch equations und aligns ersetzt.


cmake discovers with the FindLibevent2.cmake the place where to find the library header file and library itself. The header path is stored in ${LIBEVENT2_INCLUDE_DIR} and the library path in ${LIBEVENT2_LIBRARIES}, if done right. cmake is cross-platform build system, its designed to do the stuff that's needed to build the software on different systems. So why it is not used that way, is there a reason?


Method definitions tend to be easier to read when parentheses are included on the `def` line, but it's largely just a matter of style.


TeamCity LabkeyTrunk :: Git sqlserver 2014 [Build 12](https://teamcity.labkey.org/viewLog.html?buildId=277557&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:28


Great trajectory, here! Also, I like that you are already taking stock of recurrent skills and tech that makeup this broader practice. That will serve you will in this project, but also the DITA project.


Кожет -> Кожен


I dont know how! please stop emailing me

On Tue, Oct 13, 2015 at 3:10 PM, Ninjasifi <notifications@github.com> wrote:

> I don't know how. Sorry.
>
>
> On Tue, Oct 13, 2015 at 1:38 PM, Reaper1437 <notifications@github.com>
> wrote:
>
> > plz help me pllllzzzzz
> > Inquiry Number 1210340863
> > 10/13(Tues) 13:37
> > Email is sleepy14378@gmail.com
> > Really need your help
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/3dshax/ctr/commit/bcb3734b9a26d0fe7ef66f7d3814406fee797303#commitcomment-13747184
> >
> > .
>
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/3dshax/ctr/commit/bcb3734b9a26d0fe7ef66f7d3814406fee797303#commitcomment-13749597>
> .
>


стандарт даних -> структура даних


Copied from hcatalog project because it is used for serialization within a package.


merging the files


Не комитете ничего


Where is WaitHelper defined, and why not call _waitIndicator.Wait directly?


Copied because it was private in package scope.


Near-original version of talk from 2013.


для тендера -> в межах тендера


What happens in case the file is smaller than 1024 bytes? E.g. empty.


I only use this addon (dailymotion) for spi0n :)

I would like to see it in the official repo, but i'm not sure how to do it, and i've not enough time to maintain this.

You can simply replace the broken addon directory by my file, this should work.

I'll try to see later how push it the official repo.


Would it make sense to create a MatrixStack class ? and remove the .current in the array ?


Почитай, что такое `db_table` и зачем оно нужно. В данно случае оно здеть не надо


this copies the whole slice; you can reuse the original slice with:
```go
for i, replica := range r.desc.Replicas {
		if replica.StoreID == s.desc.StoreID {
			r.desc.Replicas = append(r.desc.Replicas[:i], r.desc.Replicas[i+1:])
			break
		}
}
```


Seems fine to me.


Снала идет описание полей, а зачем `class Meta`


Can we test the OperationCanceledException case with an IWaitIndicator implementation that exposes a cancelled CancellationToken?


bad coding style
}
else {


Consider using `_.zip`?


Зачем указывать `verbose_name` если там пусто. Почитай, что это и зачем оно надо.


Hello,
it looks like gourmet 0.17.5 was never released on github (it's not on "releases" page). Is there plans to do that, so we can update it in FreeBSD ports repository? Thanks.


Done!


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 690](https://teamcity.mesosphere.io/viewLog.html?buildId=58150&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:03:54


Shouldn't unlock be called anyway?


So, potentially, we run into an infinite loop here, right?


Hi @ezeob002 , perhaps an issue is a better place to discuss how to install the script instead of commenting a commit. : )
Could you open a new issue following this link : https://github.com/robotology/simmechanics-to-urdf/issues/new describing on which step of the installation guide https://github.com/robotology/simmechanics-to-urdf#debianubuntu you have problems? Thanks a lot!


Consider combining `fileNames` and `s3FileNames` since they are tightly coupled.


after that commit, I get for each service (boot and shutdown)

 restart dhcpcd
```bash
 * tor: `' is not a directory
 * tor: `' is not readable
 * Stopping Tor ...                                                                                [ ok ]
 * privoxy: `' is not a directory
 * privoxy: `' is not readable
 * Stopping privoxy ...                                                                                [ ok ]
 * netmount: `' is not a directory
 * netmount: `' is not readable
 * Unmounting network filesystems ...                                                                    [ ok ]
 * dhcpcd: `' is not a directory
 * dhcpcd: `' is not readable
 * Stopping DHCP Client Daemon ...                                                                       [ ok ]
 * dhcpcd: `' is not a directory
 * dhcpcd: `' is not readable
 * Starting DHCP Client Daemon ...                                                                       [ ok ]
 * privoxy: `' is not a directory
 * netmount: `' is not a directory
 * privoxy: `' is not readable
 * netmount: `' is not readable
 * Starting privoxy ...
 * Mounting network filesystems ...
 * tor: `' is not a directory
 * tor: `' is not readable                                                                               [ ok ]
 * Tor configuration (/etc/tor/torrc) is valid.
 * Starting Tor ...                                                                                [ ok ]
```

what if $required_dirs and $required_files are empty with the new code?


Hmmm....  Still have a small error here before It's ready to go.


the code already tells us it's a boolean. perhaps "returns true if no changes were made, and false otherwise"?


Для подобных вещей есть тэг `{% url %}` - https://docs.djangoproject.com/en/1.8/ref/templates/builtins/#url

Оно позволяет отреверсить урл лежащий в `urls.py` чтобы потом не переписывать кучу кода если ты вдруг решишь урл это поменять на что-то другое


why don't you start this at `false` and use a default clause below that sets it to true? seems less error prone.


I approve this awesome change.


I am not sure I get it. Node._getReserverdMatrix should be binded to an instance ?


Thanks for taking your time to do this, malcrom. I, for one, appreciate it, even though I don't know the full extent of your efforts to get hold of the information needed and assembling it in a working solution.

Know that your efforts are appreciated even more than you see posted after the commits.
Rule of thumb: most users expect everything to be working and only complain when it doesn't.
Posting a "thank you" is not as common as it should be.


what is this?


best change


Ужасные просто отступы. Пайчарм вот тут орать просто должен был. Читай pep8


https://github.com/zfcampus/zf-apigility-doctrine/pull/233 includes the hydrator in the composer for this fix.  See release 1.1.2


one _ used https://github.com/cedricpinson/osgjs/commit/befbdea2f7251e8188a57d611939b7c78f65c6c6#diff-84f0f61b61aae03e6de271bdd18c636dR307 and __ used here. I dont think using __ is a good idea


`sha5`? Git uses `sha1` so this name is confusing


nevermind, this is fine


Интерполяцию строк нудо делать через `{}`.format("foo") ибо `%s` уже сто лет как умерло.


Present tense ftw


Вьюхи надо писать используя Class Based View (CBV) - https://docs.djangoproject.com/en/1.8/topics/class-based-views/


This was causing null pointer exceptions during the creation of Opportunities. I included the
```if(this.$("#time-estimate").select2('data'))```
as a fix. It's possible the changes above also fix this bug, probably worth looking into.


@Philip-Nunoo `s3-uploader@1.1.0-rc.1` supports custom random generator functions; check out Turistforeningen/node-s3-uploader#41 for usage documentation :smile:


maybe it's time to create a MatrixStack class


The last commit I just made should make that clearer. No sorting is needed. For the first read file, put every single read into a separate file. For the second read file, for each read, find the corresponding file from the first read, and append the second read data to it. I'll be working on specifically this now


Thank you for fixing this @javajolt


is this will be executed?


Ok forget it, I did see it was a static


Примерно такая же тема как с тегом `{% url %}` в шаблонах тут есть функция `reverse` котрая делает тоже самое https://docs.djangoproject.com/en/1.8/ref/urlresolvers/#reverse


(y)


Вот тут если у тебя в базе нет статьи с таким ID то у тебя все упадет с эксешеном `DoesNotExist`


This is an interesting comment on text progression. It probably has to do with where the methods originated and then they were picked up by other countries/languages.

But it's interesting to think about an element that helps mark those types of languages. I used to take Japanese and many Japanese websites read left to right and horizontally, even though traditional Japanese reads top to bottom, right to left.


Коли ты сделал `comment = form.save(commit=False)` то тут надо сохранять не форму, а уже конкретный объект, то есть `comment.save()`


Just realized that we don't need that let. Was just experimenting and forgot to remove it. :)


Could you please merge this change so the hard rails dependency is removed and this gem could be tried out by all


What error? When at run time or compile time?


Well stuff slowly seems to work out.
Now I need to script out to way to allow the player to get out of THIS situation ;)
![image](https://cloud.githubusercontent.com/assets/11202073/10465846/6589503a-71f1-11e5-88b2-4ca029e4729a.png)


LGTM


user у тебя всегда есть в конексте шаблона. Специально туда его передавать не нужно. В шаблоне можно просто сделать `{{ user.username }}` или `{{ request.user.username }}`


Then you gonna have to update it XD


Could you squash this into the previous commit?


this will break the default path. you will need the same check as you do with rpmtrans setroot


форму нужно инициализировать сначала. Так ты просто передаешь класс в котором ничего нет и который ничего не может


Oops, that was a really bad copy-paste error. Fixed now. (https://github.com/AlexKnauth/racket/commit/34fc4189814c8798c1990d724546d725a913d485)


Ok done.


@alxndrsn This package comes from the kanso repository so we'd have to make this change upstream. And it looks like it was designed to do some work even when an error is returned. What problem were you trying to solve?


compile time


Так делать не стоит. Это будет работать только на твоей машине. Перенести это не выйдет. У тебя уже есть `BASE_DIR` который вычисляет где имеено нежит проект и его можно использовать для формирования относительных путей. Посмотри как сделано для базы данных


I am not sure, but wouldn't aborting the remaining threads make more sense?


Great first wave of annotations that no doubt helped you wrap your head around this element. I think the next step is to dig into the spec + the working group email listserv to understand the backstage development. Such a move will unearth some of the print + web connections, methinks.


То же что и для шаблонов. Используй относительные пути


Тогда уж лучше сразу создать JSONObject и писать сразу в него. Без HashMap'a


I like this focus on diverse situated uses and appropriations as set against spec "semantic correctness." That's a good aim to maintain throughout this project.


`{% url %}`


it's better to use osg.log osg.warn osg.debug ... instead


Аналогично CheckAuthServlet


{% url %}


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 691](https://teamcity.mesosphere.io/viewLog.html?buildId=58155&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 190 Build time: 00:04:07


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 692](https://teamcity.mesosphere.io/viewLog.html?buildId=58156&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 189 Build time: 00:04:04


test


TeamCity LabkeyModules15.2 :: CDS postgres 9.4 [Build 30](https://teamcity.labkey.org/viewLog.html?buildId=277555&buildTypeId=LabkeyModules152_CdsPostgres93) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 22 Build time: 00:35:15
### Failed tests
```
org.labkey.test.tests.CDSTest.verifyHomePage: <no details avaliable>

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

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

```


@teschnei Isn't that a problem for CoP missions?


:+1:  Great resources and suggestions, @lalib035! I think these are essential next steps, which will help fulfill your aims, @Lhyen.


is it still necessary ?


yep definitely was. https://github.com/dimagi/commcare-hq/commit/1089f130bf937ca10e1da424c4297774de460734


fwiw, you can use the `"""` and `#{ }` syntax to make a nice string without having to manually do the string concatenation


短縮版の方が日本語っぽい?


This line should be commented out.


Again, :+1: to these comments. Audience will help you narrow your project, but also help you consider what to write for the DITA, reusable documentation project.


Ok, I did not know that. I checked it just now and it seems to be correct. I agree that it is a better solution to download the header files instead of all the src code.


The coffee way to say this is `statusCode = trackStatus ? trackStatus['ActionStatus']`


It is awesome that you have this detailed patent for your project! Even though your topic, LZW compression, is pretty specific, it is surprising how much history is behind it like when Haas was talking about scrollbars. I have not heard of LZW compression before, but since you have so much history behind it I am wondering if there are different uses for when it first came out versus today and if there are any technologies similar to LZW compression.


Please do not do this.


Exactly what I was wondering.  I was going to give that a try but had to
stop for the night.
On Oct 13, 2015 9:24 PM, "Steve Sample" <notifications@github.com> wrote:

> This was causing null pointer exceptions during the creation of
> Opportunities. I included the
>
> as a fix. It's possible the changes above also fix this bug, probably worth looking into.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/MayOneUS/midas/commit/fd0202189708ade5e6f736fa738f665fbabdf505#commitcomment-13749824>
> .
>


probably best to stick with the `#{ }` syntax if that's what they were using before


:+1: to @lalib035's comments and affirmations. I would also suggest digging into the specifications + working group's email listserv to dig up some of the details and discussion and arguments that crafted particular notions of "proper semantics."


Nice names :+1:


Ok. But, if x1 is 1xn it means that you only have one instance - why would you do that? Seems like instead we should put a warning to tell you that something is wrong...


А это случайно не дублирует User? И авторизация вроде как в другой ветке...


Was fixed in the next commit


you should put `set et` in your .vimrc or add `expandtab` to the `// vim:` line at the bottom of this file...


I think you are right @gaearon. Thanks for chiming in!


Why call perror in a lib ?


same here ?


revert


I looked into it a bit because I did notice that CoP went to 93, but the
completed mission array only goes to 64 - it's been a buffer overflow since
forever, and it's always been setting/checking values from the next log
(assault)

I don't know what effect it'll have on CoP.  The packet always only went to
64 anyways, so from the client pov I don't think anything changes?

On Tue, Oct 13, 2015 at 1:35 PM, TeoTwawki <notifications@github.com> wrote:

> @teschnei <https://github.com/teschnei> Isn't that a problem for CoP
> missions?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/DarkstarProject/darkstar/commit/83a4e03e78d874d510ce1b92424171efb18bdf36#commitcomment-13750143>
> .
>


if the distances happen to be exactly the same, is it really best to ignore this point?


Issue5249-FixHWBBEngRef (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1373 of 1373 tests passed)

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


My regexp reading capabilities are limited, but isn't this going wrong now for multiple wildcard?

In my fpc package I tried:
/usr/lib/fpc/*/units/*/opencl [!linux-armel !linux-powerpc]
and it fails with:
dh_install -s --sourcedir=debian/tmp --list-missing
cp: cannot stat 'debian/tmp/[!linux-armel': No such file or directory
dh_install: cp --reflink=auto -a debian/tmp/[!linux-armel debian/fp-units-gfx-3.0.0/!linux-powerpc]/ returned exit code 1


This can be simplified by only returning `mListeners.contains(listener)` as the `contains` method already returns a boolean. This way we  avoid the `if`.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 693](https://teamcity.mesosphere.io/viewLog.html?buildId=58157&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 180 Build time: 00:08:20


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 694](https://teamcity.mesosphere.io/viewLog.html?buildId=58158&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 180 Build time: 00:03:55


I have a preference for lseek SEEK_END to find the end of file offset rather than fstat(), because AFAIK fstat performs an extra access on the FS metadata.


@zorab47 Thanks for the code clarification. @seanlinsley definitely looks cleaner than my select-reject mess. Forgot about the single `&`


yikes o.O;;;


Explain how `Index` was generated.