To avoid this condition, you could use a range that **excludes** the last element, like this:

```ruby
(1...height) # note the three .'s
```

http://www.ruby-doc.org/core-2.2.0/Range.html


Why PHP 5.3.2??? Why not PHP 5.3.3???


Why not 3.0.12???


`#!/usr/local/bin/node` or `#!/usr/bin/node` ?
I see that [codius.org](https://codius.org/docs/using-codius/setup-cli) says to setup node in `/usr/local/bin/node`, but if I understand correctly, `/usr/local/bin` is intended for locally compiled packages.


True, I'm not used to using tabs, I usually use 2 spaces, so I'm used to two tabs, I'll fix it.


Nice work @QsBBQ. Overall the code is clean and readable. I'd like to see more sanity checks on the `word_count` exercise. Think about the "less obvious" kinds of input you might have to handle.


Well that get’s into lockless design and other variants where “locks” don’t occur like interrupt contexts...

So, if you do removal and traversal with “atomic” operations you can do insanely fun things like

Traverse list in “next” order (follow only next pointers)
Atomic swap “next” to “next” to remove an element

	if (prevelem->next == removelem) {
		atomic_swap(&prevelem->next, &removelem->next);
		/* add ref check to see if anything is using me */
		myrelease(removelem);
	}

Then you can make list remove without a lock but, you have to “mark” the generation of the list to ensure
that nothing is referencing that list element after it has been removed and then it can be freed.

Needless to say, the adventurous can go into lockless design - but for the every day developer like me - “locks” work pretty much all the time and should just be used to keep the brain from exploding in userspace.

And the NetBSD kernel-mode TAILQ is “heavily” abused for a variety of reasons since the kernel wait primitives and scheduler primitives are below the lock primitives so something like a TAILQ is used by a context that just has to use barriers like a scheduler or interrupts. And spinlocks are not really assumed to have all the same characteristics and locks (mutex).

Been burned many a time, and now I prefer to write in JavaScript :)
Charles

> On Jan 21, 2015, at 2:00 PM, Matt W. Benjamin <matt@cohortfs.com> wrote:
>
> Exactly.  I've started to hedge a bit since reading the NetBSD tech-kern thread on correctness in kernel-mode TAILQ, however.
>
> Matt
>
> ----- "Charles Hardin" <ckhardin@exablox.com> wrote:
>
>> Locks imply barriers - they have to.
>>
>>
>> It wouldn’t make any sense to have a write reorder past an “unlock” -
>> else, what would be the point of “locking” a variable to just have the
>> write go after the xchg on the unlock path.
>>
>>
>> A very “typical” unlock would look something like
>>
>>
>>
>> void
>> unlock(locker_t *l)
>> {
>> int state;
>>
>>
>> release_barrier(); /* keep all load/store inside the lock region */
>> state = swap(&l->state, UNLOCKED);
>>
>>
>> /* Flush the swap - but, if the swap is is atomic then this isn’t
>> really needed */
>> store_flush();
>>
>>
>> … other stuff like wakups, etc …
>> }
>>
>>
>>
>>
>>
>>
>>
>> On Jan 21, 2015, at 1:23 PM, Matt W. Benjamin < matt@cohortfs.com >
>> wrote:
>>
>> Hi,
>>
>> ----- "William Allen Simpson" < william.allen.simpson@gmail.com >
>> wrote:
>>
>>
>>
>>
>>
>>
>> My suggestion of moving this code into get_ds would then make this
>> whole
>>
>>
>> business atomic by protecting it with a lock that prevents the ds
>> from being
>>
>>
>> removed.
>>
>> Huh? The only thing that makes something atomic is atomic. Having
>> an assignment inside a lock doesn't make it atomic.
>>
>> It doesn't guarantee the propagation of CPU cached entries, except
>> for the specific mutex involved. In the default case, it is
>> supposed to provide a barrier for code order optimization.
>>
>>
>> responding to just this remark, and not the larger thread, this seems
>> like a red
>> herring; a pthreads mutex is exactly how we would ensure that a
>> accesses
>> to a set of related variables are synchronized, and that is within the
>> ordinary meaning of "atomicity." if we find a problem with cache
>> consistency, then explicit barriers by definition will address it.
>>
>> Matt
>>
>> --
>> Matt Benjamin
>> CohortFS, LLC.
>> 315 West Huron Street, Suite 140A
>> Ann Arbor, Michigan 48103
>>
>> http://cohortfs.com
>>
>> tel. 734-761-4689
>> fax. 734-769-8938
>> cel. 734-216-5309
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in
>> Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely
>> compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in
>> Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely
>> compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
> --
> Matt Benjamin
> CohortFS, LLC.
> 315 West Huron Street, Suite 140A
> Ann Arbor, Michigan 48103
>
> http://cohortfs.com
>
> tel.  734-761-4689
> fax.  734-769-8938
> cel.  734-216-5309


It is Ok that you changed all files rights from 100644 to 100755???


Do you need to print the results?


`return x, y, z` here as well?


Writer Monad: DONE in e47a92790464659da2c6312a0d05b7db527d098a


@lukhas @hupf This merge ripped off the dedicated window and minibuffer checking. My windows are swapping crazily again. Could you revert it?.


why, double underscore. why


Did you know if you replace 'default-tab=result' with 'default-tab=html' (or 'js') it prevents the auto-run?


Works for me. To re-iterate the other acceptable alternative as I see it:

It seems like there is a non-trivial amount of logic required to determine the threshold from the raw scores. I think it makes sense that this logic exists in the class that owns all the cascade layers, and not in the logic that implements a specific layer.


This method name could use some work.

Generally, a method name that gives you a sense of **what the output is** is better than one that describes **how the method works**.


Then a comment like: ```// TODO: Use SparseMatrix::set_values() for efficiency``` is pretty good ;-) Saves a lot of typing and is easier to find ;-) IMO.


Looks good. Maybe try testing some strings that have whitespace characters in them.


Yes, fixed at https://github.com/sklam/numba/commit/4276921b2ad5d3ec998347bd648fe601a69988c3#diff-1c116a52e2457a8cebe1e9d2072d195dR91


Missing part:

```c
break;
case ADDR_TABS:
lnum = 0;
```


Sweet, thanks for trying!


Space missing before `=`.


Looks good!


I don't understand this change.  Most header items have descriptions in the header, and the existing code works just fine with them, returning a value, not a tuple. e.g. the test_AffineTransform.fits file that gets created by the test suite:
```
>>> import astropy
>>> f = astropy.io.fits.open('tests/fits_files/test_AffineTransform.fits')
>>> f[0].header
SIMPLE  =                    T / conforms to FITS standard
BITPIX  =                  -32 / array data type
NAXIS   =                    2 / number of array dimensions
NAXIS1  =                  143
NAXIS2  =                  160
EXTEND  =                    T
GS_XMIN =                    4 / GalSim image minimum x coordinate
GS_YMIN =                   10 / GalSim image minimum y coordinate
GS_WCS  = 'AffineTransform'    / GalSim WCS name
CTYPE1  = 'LINEAR  '           / name of the world coordinate axis
CTYPE2  = 'LINEAR  '           / name of the world coordinate axis
CRVAL1  =               1423.9 / world coordinate at reference pixel = u0
CRVAL2  =    8242.700000000001 / world coordinate at reference pixel = v0
CRPIX1  =                 -3.0 / image coordinate of reference pixel = x0
CRPIX2  =                104.0 / image coordinate of reference pixel = y0
CD1_1   =               0.2342 / CD1_1 = dudx
CD1_2   =              -0.1432 / CD1_2 = dudy
CD2_1   =               0.0924 / CD2_1 = dvdx
CD2_2   =              -0.3013 / CD2_2 = dvdy
>>> f[0].header.get('CRVAL1')
1423.9
>>> import galsim
>>> im = galsim.fits.read('tests/fits_files/test_AffineTransform.fits')
>>> im.wcs
AffineTransform(0.2342,-0.1432,0.0924,-0.3013,PositionD(x=0.0, y=113.0),PositionD(x=1423.9, y=8242.7))
```
What is your use case for which the existing code failed?


For future reference, even though commas are equivalent to whitespaces, we are not using them anywhere else in this project so we should be consistent.


Nonsense empty commit, please ignore.


This fails to take into account the following valid commands:
```1 .. 3```
.5...9    Note: Couldn't get Markdown to tag this as code properly


Spaces missing around `=`. You *could* also move the declaration of `tp` down here (same with `wp` above, and similarly in other functions).


What's that?  Nothing to STDOUT unless it's a warning?


Yes, that's the expectation. Do you think something else would be right? If it's not a string or a buffer, is there a reasonable fallback? Perhaps bufferify should be:

```javascript
return Buffer.isBuffer(val) ? val : new Buffer(val.toString());
```


This is cool @mikedunker-apigee and @michaelarusso. But we can also leverage [Apigee "NPM API"](http://apigee.com/docs/management/apis/post/organizations/%7Borg_name%7D/apis/%7Bapi_name%7D/revisions/%7Brevision_num%7D/npm) to install dependencies from package.json and reduce the footprint of the bundle to upload and the complexity of the plugin. I did this for Grunt and work like a charm. This is all is needed for [any reference](https://github.com/apigeecs/apigee-deploy-grunt-plugin/blob/master/grunt/tasks/installNpmRevision.js#L26).


This reverts #4040.


Sounds subjective.  Feel free to change the logging system or configure your log level in ~/.tendermint/config.toml!


Should be `lastbuf`.


You should use a macro to reduce the repetition in this code. Either have a macro which replaces each match arm. Or have a fold_annotatable macro which applies a chunk of code to the underlying item and folds it back together again.


Make it `self.get_name`


Hello @jfirebaugh , just wondering, why did you revert to ES5? Compatibility? Readability?


nit: whitespace


unused?


Because of the conflicts between bundle versions, it's the only way I could resolve it


Hello


Good questions, and I have good news for you: your understanding is correct!

A better way to describe line 29 is to say that we are **iterating over the array**. This is the _action_ being performed. You could also say that we are **calling the each method on the array** to be more literal.


Hello test from Yee


Derp, this fixes #210 and helps fix https://github.com/cvrebert/lmvtfy/issues/72


Yeah... so I was going to suggest just passing a filename as a string so pyscrypt had more control over the file object and thus able to flush it with the context manager. I'm not sure what advantage you get (as a programmer) from passing in a file object to the ScryptFile class. I guess if you merely pass in a filename you'd also have to pass in the mode too (which I don't see in your final example).

I'll have a look at PEP8-ifying and making use of `unittest` in another branch.


Great! You got it. Nice work.


This is not in a block - so it won't show anywhere if that is your test.


Actually Pomf can you please revert this so it doesn't interfere with my much larger PR. It would be most appreciated.


@Wild1145 I am having trouble with the permissions. I know how I can commit it, can you give me help on that?


Perhaps the simplest solution is just to mark ```..``` without qualification as the ```..``` can be preceded or followed by  expressions, whitespace, variables, and numbers.


I guess we won't. I wait for some answers from team lead and i'll change it back


Great! I'd like to have tests for features, could you please write a test in t/18-fragments.t too, by creating a new block with a constructor where you set this in the config?


System fields should only be for.. well system fields. Username, email, password, display name, etc. Address, redundant social data, should all be very much optional. Especially for security issues and other admins on a highly driven instance of HumHub run by multiple admins. Hiding a field can be overturned and cause havoc.


Thanks for the heads' up! Just fixed that typo.


Correct.  As I wrote: "barriers", not "atomic".

Anyway, it seems at least we three understand....

Meanwhile, Dan has suggested a compromise for getting these
out of the fast path -- based on Frank's mention of get_ds
(which doesn't exist) -- using mostly existing structures.

I've also taken the opportunity to move some things out of the
locked sections that could be done outside.

Using 769 for the export hash and 193 for the DS hash.

Coming soon (as soon as pynfs finishes running).

On 1/21/15 5:00 PM, Matt W. Benjamin wrote:
> Exactly.  I've started to hedge a bit since reading the NetBSD tech-kern thread on correctness in kernel-mode TAILQ, however.
>
> Matt
>
> ----- "Charles Hardin" <ckhardin@exablox.com> wrote:
>
>> Locks imply barriers - they have to.
>>
>>
>> It wouldn’t make any sense to have a write reorder past an “unlock” -
>> else, what would be the point of “locking” a variable to just have the
>> write go after the xchg on the unlock path.
>>
>>
>> A very “typical” unlock would look something like
>>
>>
>>
>> void
>> unlock(locker_t *l)
>> {
>> int state;
>>
>>
>> release_barrier(); /* keep all load/store inside the lock region */
>> state = swap(&l->state, UNLOCKED);
>>
>>
>> /* Flush the swap - but, if the swap is is atomic then this isn’t
>> really needed */
>> store_flush();
>>
>>
>> … other stuff like wakups, etc …
>> }
>>
>>
>>
>>
>>
>>
>>
>> On Jan 21, 2015, at 1:23 PM, Matt W. Benjamin < matt@cohortfs.com >
>> wrote:
>>
>> Hi,
>>
>> ----- "William Allen Simpson" < william.allen.simpson@gmail.com >
>> wrote:
>>
>>
>>
>>
>>
>>
>> My suggestion of moving this code into get_ds would then make this
>> whole
>>
>>
>> business atomic by protecting it with a lock that prevents the ds
>> from being
>>
>>
>> removed.
>>
>> Huh? The only thing that makes something atomic is atomic. Having
>> an assignment inside a lock doesn't make it atomic.
>>
>> It doesn't guarantee the propagation of CPU cached entries, except
>> for the specific mutex involved. In the default case, it is
>> supposed to provide a barrier for code order optimization.
>>
>>
>> responding to just this remark, and not the larger thread, this seems
>> like a red
>> herring; a pthreads mutex is exactly how we would ensure that a
>> accesses
>> to a set of related variables are synchronized, and that is within the
>> ordinary meaning of "atomicity." if we find a problem with cache
>> consistency, then explicit barriers by definition will address it.
>>
>> Matt
>>
>> --
>> Matt Benjamin
>> CohortFS, LLC.
>> 315 West Huron Street, Suite 140A
>> Ann Arbor, Michigan 48103
>>
>> http://cohortfs.com
>>
>> tel. 734-761-4689
>> fax. 734-769-8938
>> cel. 734-216-5309
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in
>> Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely
>> compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in
>> Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely
>> compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>


Content type text/plain allows to put empty values.


Easiest for your plugin is to remove `$STAT_FILE` and just use `$MUNIN_STATEFILE` instead.


See #855.


makes this dynamic.


Looks good


Second `curbuf` should also be changed to `buf`.


Missing space before `=`.


Thanks again! Changed that one too.


I see, thanks !

On Wed, Jan 21, 2015 at 11:35 PM, John Firebaugh <notifications@github.com>
wrote:

> See #855 <https://github.com/mapbox/mapbox-gl-js/issues/855>.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mapbox/mapbox-gl-js/commit/da89f70093f7e6e48e35f55fc1baa66f1d88efc2#commitcomment-9386655>
> .
>

--
Fabien Nicollet
Tel : +33 (0)6 60 54 72 20


When you run the the following without any WCS package such as AstroPy or
starlink.Ast installed, it goes to AffineTransform and throws an error.

```
    ra_targ = 30.*galsim.degrees
    dec_targ = -10.*galsim.degrees
    targ_pos = galsim.CelestialCoord(ra=ra_targ, dec=dec_targ)
    ang = 0.*galsim.degrees

    wcs_list = wfirst.getWCS(ang, pos=targ_pos, PA_is_FPA=True)
```

The error message was:

```
Traceback (most recent call last):
  File "demo13.py", line 393, in <module>
    main(sys.argv)
  File "demo13.py", line 155, in main
    wcs_list = wfirst.getWCS(ang, pos=targ_pos, PA_is_FPA=True)
  File "/usr/lib/python2.7/dist-
packages/galsim/wfirst/wfirst_wcs.py", line 322, in getWCS
    wcs = galsim.FitsWCS(header=header)
  File "/usr/lib/python2.7/dist-packages/galsim/fitswcs.py", line 1520, in
FitsWCS
    wcs = galsim.wcs.AffineTransform._readHeader(header)
  File "/usr/lib/python2.7/dist-packages/galsim/wcs.py", line 1785, in
_readHeader
    return AffineTransform(dudx, dudy, dvdx, dvdy, galsim.PositionD(x0,y0),
Boost.Python.ArgumentError: Python argument types in
    PositionD.__init__(PositionD, tuple, tuple)
did not match C++ signature:
    __init__(_object*, double x=0.0, double y=0.0)
    __init__(_object*, galsim::Position<double> other)
```.

When you get the header file as say ``` x0 = header.get("CRPIX1",0.) ```,
it returned a tuple instead of a value.

On Wed, Jan 21, 2015 at 5:27 PM, Mike Jarvis <notifications@github.com>
wrote:

> I don't understand this change. Most header items have descriptions in the
> header, and the existing code works just fine with them, returning a value,
> not a tuple. e.g. the test_AffineTransform.fits file that gets created by
> the test suite:
>
> >>> import astropy
> >>> f = astropy.io.fits.open('tests/fits_files/test_AffineTransform.fits')
> >>> f[0].header
> SIMPLE  =                    T / conforms to FITS standard
> BITPIX  =                  -32 / array data type
> NAXIS   =                    2 / number of array dimensions
> NAXIS1  =                  143
> NAXIS2  =                  160
> EXTEND  =                    T
> GS_XMIN =                    4 / GalSim image minimum x coordinate
> GS_YMIN =                   10 / GalSim image minimum y coordinate
> GS_WCS  = 'AffineTransform'    / GalSim WCS name
> CTYPE1  = 'LINEAR  '           / name of the world coordinate axis
> CTYPE2  = 'LINEAR  '           / name of the world coordinate axis
> CRVAL1  =               1423.9 / world coordinate at reference pixel = u0
> CRVAL2  =    8242.700000000001 / world coordinate at reference pixel = v0
> CRPIX1  =                 -3.0 / image coordinate of reference pixel = x0
> CRPIX2  =                104.0 / image coordinate of reference pixel = y0
> CD1_1   =               0.2342 / CD1_1 = dudx
> CD1_2   =              -0.1432 / CD1_2 = dudy
> CD2_1   =               0.0924 / CD2_1 = dvdx
> CD2_2   =              -0.3013 / CD2_2 = dvdy
> >>> f[0].header.get('CRVAL1')
> 1423.9
> >>> import galsim
> >>> im = galsim.fits.read('tests/fits_files/test_AffineTransform.fits')
> >>> im.wcs
> AffineTransform(0.2342,-0.1432,0.0924,-0.3013,PositionD(x=0.0, y=113.0),PositionD(x=1423.9, y=8242.7))
>
> What is your use case for which the existing code failed?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GalSim-developers/GalSim/commit/63b13f7f547c7bda182c2e59ece9773bb62074a8#commitcomment-9386113>
> .
>

--
Regards

Arun Kannawadi Jayaraman
PhD candidate, Dept. of Physics,
Carnegie Mellon University,
Pittsburgh, PA 15213


You're absolutely right, @sags1083. That is another way to write that method. Of course, you'd want to remove the last `print "\n"` line.

I think in this case the author of the exercise wanted to show that you can print characters one at a time to the same line.


I can confirm MySQL-python and Jinja2 are good (based on kitsune and AirMozilla, respectively), but not lxml.


I'll remove the bolding as I do think it looks a bit cleaner - although I think it looks a bit clunker as well if you add /help to each command. It's redundant since that's how all of those groups are supposed to work. I'll also add the ability to click on the name to automatically run `/help group`, as how I've done with the Prev and Next buttons. Also, the 'Wrapper' in the help groups was supposed to be a help group in itself - it's not referring to the /wrapper command, but rather the whole list of commands that the wrapper has.

i.e.. `/help wrapper` should return all of the internal commands for Wrapper.py, like /wrapper (and its subcommands), /permissions, /reload, /plugins, etc.


should be `cbuf + 5`


Ah okay ... I leav the clientKey then empty so that the user has to add his clientKey
into his own status user properties.

But a default value, and even if it is an empty string, must be set. Otherwise the core will not start
cause the properties will be evaluated.


`:winpos 1 2` would now give an error, because we do not read the numbers `x` and `y` anymore.


Thank you! I'm glad that you find it good. I made more changes in navGrid today. So the problem with overlapped buttons of the pager and the navigator buttons not more exist. The demos demonstrates the new features:
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons0.htm
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons1.htm
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons2.htm (it shows new `iconsOverText:true` option)
The same works with Font Awesome 4 too
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons0-fa4.htm
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons1-fa4.htm
http://www.ok-soft-gmbh.com/jqGrid/OK/navButtons2-fa4.htm
It should be some small bugs of cause, but the main features works.
By the way you can resize all grids horizontally to see the changes in navigator bar.


@borshop: retry


This is the same as in the original patch, but I'm wondering why there's once `+4` and once `-5`.


Thanks Jayme!

hsmith825
-----Original Message-----
From: Jayme Davis [mailto:notifications@github.com]
Sent: Wednesday, January 21, 2015 12:44 AM
To: jaymedavis/stripe.net
Cc: hsmith825
Subject: [stripe.net] updated old property values on account, still have some to do after the api version gets bumped. closes #257, thanks @hsmith825 (d7ccb22)

updated old property values on account, still have some to do after the api version gets bumped. closes #257, thanks @hsmith825

---
Reply to this email directly or view it on GitHub:
https://github.com/jaymedavis/stripe.net/commit/d7ccb2259d044feff8754038f9b83b9675fef1cb


Test comment


Sorry I missed the new commit, oops.


@rmandelb, Ignore the references to the line numbers I mentioned. I had
tried those for a quick fix, but that alters the general JacobianWCS. The
change has to be made within AffineTransform.

On Wed, Jan 21, 2015 at 5:36 PM, Arun Kannawadi <arunkannawadi@cmu.edu>
wrote:

> When you run the the following without any WCS package such as AstroPy or
> starlink.Ast installed, it goes to AffineTransform and throws an error.
>
> ```
>     ra_targ = 30.*galsim.degrees
>     dec_targ = -10.*galsim.degrees
>     targ_pos = galsim.CelestialCoord(ra=ra_targ, dec=dec_targ)
>     ang = 0.*galsim.degrees
>
>     wcs_list = wfirst.getWCS(ang, pos=targ_pos, PA_is_FPA=True)
> ```
>
> The error message was:
>
> ```
> Traceback (most recent call last):
>   File "demo13.py", line 393, in <module>
>     main(sys.argv)
>   File "demo13.py", line 155, in main
>     wcs_list = wfirst.getWCS(ang, pos=targ_pos, PA_is_FPA=True)
>   File "/usr/lib/python2.7/dist-
> packages/galsim/wfirst/wfirst_wcs.py", line 322, in getWCS
>     wcs = galsim.FitsWCS(header=header)
>   File "/usr/lib/python2.7/dist-packages/galsim/fitswcs.py", line 1520, in
> FitsWCS
>     wcs = galsim.wcs.AffineTransform._readHeader(header)
>   File "/usr/lib/python2.7/dist-packages/galsim/wcs.py", line 1785, in
> _readHeader
>     return AffineTransform(dudx, dudy, dvdx, dvdy, galsim.PositionD(x0,y0),
> Boost.Python.ArgumentError: Python argument types in
>     PositionD.__init__(PositionD, tuple, tuple)
> did not match C++ signature:
>     __init__(_object*, double x=0.0, double y=0.0)
>     __init__(_object*, galsim::Position<double> other)
> ```.
>
> When you get the header file as say ``` x0 = header.get("CRPIX1",0.) ```,
> it returned a tuple instead of a value.
>
>
>
> On Wed, Jan 21, 2015 at 5:27 PM, Mike Jarvis <notifications@github.com>
> wrote:
>
>> I don't understand this change. Most header items have descriptions in
>> the header, and the existing code works just fine with them, returning a
>> value, not a tuple. e.g. the test_AffineTransform.fits file that gets
>> created by the test suite:
>>
>> >>> import astropy
>> >>> f = astropy.io.fits.open('tests/fits_files/test_AffineTransform.fits')
>> >>> f[0].header
>> SIMPLE  =                    T / conforms to FITS standard
>> BITPIX  =                  -32 / array data type
>> NAXIS   =                    2 / number of array dimensions
>> NAXIS1  =                  143
>> NAXIS2  =                  160
>> EXTEND  =                    T
>> GS_XMIN =                    4 / GalSim image minimum x coordinate
>> GS_YMIN =                   10 / GalSim image minimum y coordinate
>> GS_WCS  = 'AffineTransform'    / GalSim WCS name
>> CTYPE1  = 'LINEAR  '           / name of the world coordinate axis
>> CTYPE2  = 'LINEAR  '           / name of the world coordinate axis
>> CRVAL1  =               1423.9 / world coordinate at reference pixel = u0
>> CRVAL2  =    8242.700000000001 / world coordinate at reference pixel = v0
>> CRPIX1  =                 -3.0 / image coordinate of reference pixel = x0
>> CRPIX2  =                104.0 / image coordinate of reference pixel = y0
>> CD1_1   =               0.2342 / CD1_1 = dudx
>> CD1_2   =              -0.1432 / CD1_2 = dudy
>> CD2_1   =               0.0924 / CD2_1 = dvdx
>> CD2_2   =              -0.3013 / CD2_2 = dvdy
>> >>> f[0].header.get('CRVAL1')
>> 1423.9
>> >>> import galsim
>> >>> im = galsim.fits.read('tests/fits_files/test_AffineTransform.fits')
>> >>> im.wcs
>> AffineTransform(0.2342,-0.1432,0.0924,-0.3013,PositionD(x=0.0, y=113.0),PositionD(x=1423.9, y=8242.7))
>>
>> What is your use case for which the existing code failed?
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/GalSim-developers/GalSim/commit/63b13f7f547c7bda182c2e59ece9773bb62074a8#commitcomment-9386113>
>> .
>>
>
>
>
> --
> Regards
>
> Arun Kannawadi Jayaraman
> PhD candidate, Dept. of Physics,
> Carnegie Mellon University,
> Pittsburgh, PA 15213
>

--
Regards

Arun Kannawadi Jayaraman
PhD candidate, Dept. of Physics,
Carnegie Mellon University,
Pittsburgh, PA 15213


I have no idea the way it happened on the remote. A minute ago used "git config core.filemode false", it works in such cases. After TL's reply in a new commit it'll be fixed.


@rmjarvis , perhaps there is an error in how I"m constructing the headers, in that case?

in galsim/wfirst/wfirst_wcs.py there is a routine that is essentially the python version of some C code I was given by the WFIRST project office.  I thought I was following a reasonable procedure for constructing the header including comments, but perhaps not?


Please inject this. Either in the constructor or via parameter injection.


virtual


Did you know that you can do the markdownizing from inside Nunjucks templates? Or is this doing something that the current `marked` library doesn't?


hardware/qcom/display-caf should be >> ..../display-caf/msm7x30 "as example" for 3 caf(s)


I saw that. This one is configured differently to generate the graphviz diagrams. I may overwrite the markdown filter with this differently configured one, but for now I want to keep them distinct.


The website is probably out of date, I tested with 0.7.6 and it's good to
go. Version bumped accordingly, thanks for the heads up.

On Wed, Jan 21, 2015 at 3:49 PM, Jay Taylor <notifications@github.com>
wrote:

> I see, that is interesting.
> https://github.com/mesosphere/marathon/releases lists 0.7.6 as having
> been published bak on Dec 14th, 2014.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mhamrah/ansible-marathon/commit/c68756d819dcb6e6da53c3196cd8ab557a3f00f1#commitcomment-9384028>
> .
>


Fixed the initialization problem; this commit is reverted by c62c6133cc20d2cb0d870d94ee369e93f6e3e288


OK. Looks like you've got it covered. Cool.


test


If this is no longer necessary, the let's remove it.


Same answer: you sure can! This is just one way to solve this issue.


added cellmapper


OK.


It seemed strange to have the UiThreadScheduler be the source of truth for the system time. We wanted to move that responsibility to `ShadowSystemClock` (`System.currentTimeMillis` now calls into `ShadowSystemClock`).


It's possible to encounter errors in this case without the `isset` check:

```php
$reactor->once(function($reactor, $watcherId) {
    $reactor->cancel($watcherId);
});
```

I could've put the check inside `clearWatcher()` but then every cancellation would have that extra instruction when only one-time watchers require it.


I am going to nuke this file. Stand by for a new PR tomorrow morning.


saw approval from christophermancini
at https://github.com/basho/riak-python-client/commit/ede2838fb1014444f69fc57004c95bf6eb6c99b5


merging basho/riak-python-client/feature/bch/tox = ede2838f into borshop-integration-392-feature/bch/tox


basho/riak-python-client/feature/bch/tox = ede2838f merged ok, testing candidate = 2810ceaf


Done


rax retry tests


When reviewing your code, these merges really get in the way. You can try using `git pull --rebase`, or investigate some other way which works with your workflow.
https://coderwall.com/p/7aymfa/please-oh-please-use-git-pull-rebase


This test was about to check that a command that failed to be added cannot be launched. Which is not possible anymore...


Yeah I don't get the `[1]` in `self._target[1]`. Shouldn't it be `self._target:resize(target:size()):copy(target))`?


Cool.
I'm new to the codebase - is the check_async not necessary for errors? (I'm not really sure what it's for.)


This change broke browserify tests. PR to fix them here: https://github.com/crypto-browserify/randombytes/pull/1


@mischah halp plz.

The Version div should be at the right end of the navbar. But somehow it renders incorrect:

![bildschirmfoto 2015-01-21 um 23 51 19](https://cloud.githubusercontent.com/assets/5144843/5846957/6ffbbf98-a1c8-11e4-8aaf-e0f1b22905d8.png)

What can I do? :sob:


It is really dangerous to the consistency of the SmartThings ecosystem to allow extra attributes and/or commands to be added to a Device Type of a particular capability. Any SmartApps that use these extensions are no longer guaranteed to be compatible with any other Device Type of the specified capability and this breaks the semantics of the use capability.<x> in preferences{input} and any other place that the capability filter is used to fetch a list of compatible Devices.

I recommend strongly discouraging extended attributes / method, and instead implement a fast track to add official new capabilities.

Thank-you.


Was the intention to fail the entire run, or just throw the exception? I actually prefer this approach, since it gives the opportunity to implement a handler.


There could be connections with the same key, that are dropped by calling pop here.


Very nice, summ. By any chance did you try to remove the addEvent calls? It's frustrating when you code things on init() and they simply don't work for 'no reason'.


@mlocati Here the new normalizeTranslationCount, that is invoked on set plural translations. The property `translationCount` can be null, (by default) so it doesn't change anything. On insert this translation in a `Translations`, the translationCount is updated and normalized.


I don't think it's the best way. Symfony require php version from 5.3.3.
https://github.com/symfony/symfony-standard/blob/2.7/composer.json#L10


shoudln't this setTimeout() to __usersBeingLookedUp-- in X seconds?


Check Line 807


In this case, rescuing is actually _not_ a good idea. If there's an error, you probably want your code to stop running and tell you something is wrong, right? You wouldn't want it to keep going.


You don't need to add the explicit `return` if you don't want. If it's the style you prefer, that's fine. But Ruby has implicit return, so it is superfluous in this instance.


Nice help message!


I didn't expected this to be merged so fast.

1) I liked the original option name (`serialize`) better than `cache`. I think that the implementation detail (that is uses serialization) is very important when deciding whether to turn it on.
2) You should probably check for possible `serialize` failure.
3) I would mark this feature explicitly as experimental.
4) The eval does not really make me happy. Someone should look into possible security impact. It is probably OK, but better safe than remote code execution vulnerability.


I am writing for the future metadatastore, where (it seems) `find` may simply return a list of events.

We have to loop through the events anyway, as we unpack their data and check whether they have external data to be fetched from the File Store. At that time, we can get their descriptors, run headers, etc. A function returning a long tuple is not very user-friendly, especially when the order of the elements in that tuple is not obvious. `x, y, z = f()` is usable, but I think `h, bc, ed, e = f()` is not.


Whenever possible, try to name your variables something other than just the type of data. For example, in this case you could call it `file_contents` or `file_text`, which is more descriptive.


I've updated it so it now automatically attempts to figure out the mode a little more rigorously, as well as the ability to pass in a filename or a file pointer. It used to look at only the file mode of the file pointer passed in to determine what mode to use, but now it inspects the parameters as well, so most of the time, specifying a mode should not even be necessary. I may remove the mode option all together in a future release, but that would break backward compatibility, so it would be a major version bump.

The ability to use a file pointer adds a lot of flexibility, for example, using StringIO to create an in-memory encrypted files (that may in turn be sent over the network and possibly never written to disk) as well as interacting with interesting libraries like Boto to store encrypted files transparently in AWS' S3.

Let me know anywhere I deviate from PEP8 significantly, and I'll fix it in the main branch. "But most importantly: know when to be inconsistent -- sometimes the style guide just doesn't apply." ~Guido van Possum, PEP8

Thanks again, ntoll.


Same deal here. A better variable name might be `all_characters`. You might also consider renaming your method `string_split` to something that describes the _return value_ instead of the _operation performed_. Maybe `characters_in`?


I think the possible exception should be handled somehow. Maybe just logged?


Looks like `Path()` has been renamed to `RawPath()`, but the following hacky way of parsing out the response code still remains in place.


You may be right, worth trying. You'd do what in this case, click on another element to lose the focus?


Have these changes been shown to the docs team or Sergei?


Again, using `rescue` here does more harm than good, because it _hides_ the error. If there's an error, you usually want to know what it is. Errors are your friend!


#1 :octocat:


Instead of commenting this out, you can just delete it.


fix_size_t_warnings (macumber) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (2072 of 2190 tests passed)

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


I'm not seeing where LDFLAGS is defined. Am I missing something?


When defining a method that takes no arguments, you don't need to include the `()`


Yes, they asked me to make the changes directly.

On Wed, Jan 21, 2015 at 5:02 PM, Michael Sneddon <notifications@github.com>
wrote:

> Have these changes been shown to the docs team or Sergei?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/samseaver/narrative_method_specs/commit/fe93794a8bb19b0fb23eb4b29c5d275b2b78e27a#commitcomment-9387004>
> .
>

--
Postdoctoral Fellow
Mathematics and Computer Science Division
Argonne National Laboratory
9700 S. Cass Avenue
Argonne, IL 60439

http://www.linkedin.com/pub/sam-seaver/0/412/168
samseaver@gmail.com
(773) 796-7144

"We shall not cease from exploration
And the end of all our exploring
Will be to arrive where we started
And know the place for the first time."
   --T. S. Eliot


Hey, sorry but I have a question.

You did update the libs (moment, 13 days ago & moment-timezone, 8 days ago) without changing the version number of momentjs itself?

This seems to be very careless as this potentially breaks stuff and if so it will be hard to find out, as I would expect one version of dependency to stay as it is.

I hope you get my concern.


THIS IS GOING TO BE TORTURE!!!!!!!!!!!!


Nice job @QsBBQ. Most of my thoughts are expressed as line notes.

The main takeaway here is to spend a bit more time thinking about variable and method names.


I think this was implemented like this to distribute the load. @caiush ?


This commit adds testlib.pl back to all the tests : https://github.com/Sweet-kid/p5-io-socket-ssl/commit/512657ffb532b3a2d37a8e3e3f465e17d30ba0c6


:heart:


Nice small method here. Minor change would be to call it `str_to_chars` since it returns more than one.


This require statement is wrong. You should use a version constraint.


Yes, but the normal form is not REQUIRED by the RFC; the sentence is not preceded by any of the RFC 2119 keywords, making it an optional practice.

Additionally, because the interface represents request target forms other than absolute-form, the path can be empty for those forms. We're also not making a requirement that absolute-form be normalized.


This commit replaces all likes (except one) with is : https://github.com/Sweet-kid/p5-io-socket-ssl/commit/63aea7fb198c32b8194c77bd8101e23b3767cfb2
One like which I have not replaced with "is" is this :
t/core.t:98:        like( $cert, qr/IO::Socket::SSL Demo CA/, "Client Verify-sub Check");


I was thinking:
`return gateway.401(resolve, reject...)`

And then in the non-auth handle401:
`reject(/*not sure what params you want to pass it*/)`


This commit addresses it https://github.com/Sweet-kid/p5-io-socket-ssl/commit/11c6e20626b946b3e6e0761bf453b6354487bbe8


This commit addresses it : https://github.com/Sweet-kid/p5-io-socket-ssl/commit/11c6e20626b946b3e6e0761bf453b6354487bbe8


This method name is a little misleading. If I didn't see the implementation, I would expect it to return a count of the characters (like what `item_counts` returns). But in fact it prints the characters and returns whatever `count_and_print` returns. So perhaps you could call it `count_and_print_chars`? Or `show_char_count`?


Job scala-2.11.x-validate-publish-core failed for 1724a619, Took 4 s. (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/75/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for 1724a619, Took 10 min. (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/73/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


I haven't tested it in Chrome, but I've just read on MDN that it isn't supported...


This commit uses pass in place of ok(1,...) : https://github.com/Sweet-kid/p5-io-socket-ssl/commit/9273efc40e967df3799b6735507c547462e686b1


For the time-being, could we put a comment about that--the need to keep that recipe last?


fix_size_t_warnings (macumber) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

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


Right, I had patched GenerateEverything on my fork but forgot to include the relevant changes here.
https://github.com/agda/agda-stdlib/commit/6c97b3645cba84f17a653223b91a3933adc74983 should fix the issue. I hope I haven't forgotten anything else.


Instead of deleting your sanity checks, you can just comment them out, or wrap them in a method like `run_sanity_checks` which you can then call or not call. This way you keep them around for when you want to use them later.


Please remove changes files rights from this pr


82420068_GridViewMultiEdit (evanweaver) - i386-Windows-7-VisualStudio-12: OK (2171 of 2188 tests passed)

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


Nice work! As I mentioned in my other review, it's good to keep your sanity checks around. Also to add new ones for when you add more code.


Testing locally and the menu has no threadmarks regardless of the defined menu limit.

I think this line should be:

`$menulimit = XenForo_Permission::hasPermission($viewingUser['permissions'], 'forum', 'sidane_tm_menu_limit');`


And here we go :-)

Nightly: https://scala-webapps.epfl.ch/jenkins/view/Scala.js/job/scalajs-nightly/286/
Weekly: https://scala-webapps.epfl.ch/jenkins/view/Scala.js/job/scalajs-weekly/19/


Which are you refering to?
These?
+        addEvent(function()
+          self:setHeaderColumnStyle(value)
+        end)


I don't see again no complete sentence:
If any result gets written, then what?
I think I just got stocked on this sentence...


I don't like this change (sorry)


The `self::CASE_SENSITIVE` should not be there. https://github.com/nette/application/commit/51510f3a0b39d612a89b93018dbf2fa39f8b962a


I don't, I can use ungettext_lazy. PR in #1641.

Thanks for reporting, @jerzyk :)


Job scala-2.11.x-validate-main failed for 1724a619, Took 10 s. (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/74/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for 1724a619,  (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/76/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


This commit actually fix issue #14.


I am not getting any such error in any of the tests, on my debian system, except t/alpn.t
I can't run alpn.t on my system, because of no alpn support on my system, so not sure if that test will give any errors when there would be alpn support on the system.


>
> I recommend strongly discouraging extended attributes / method, and
> instead implement a fast track to add official new capabilities.

I fully agree. I think we need to make it easier to suggest (and vote) on
new capabilities and then work to add those in officially.

On Wed, Jan 21, 2015 at 2:52 PM, Terry Gauchat <notifications@github.com>
wrote:

> It is really dangerous to the consistency of the SmartThings ecosystem to
> allow extra attributes and/or commands to be added to a Device Type of a
> particular capability. Any SmartApps that use these extensions are no
> longer guaranteed to be compatible with any other Device Type of the
> specified capability and this breaks the semantics of the use capability.
> in preferences{input} and any other place that the capability filter is
> used to fetch a list of compatible Devices.
>
> I recommend strongly discouraging extended attributes / method, and
> instead implement a fast track to add official new capabilities.
>
> Thank-you.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/SmartThingsCommunity/Documentation/commit/c5e602d90630514c42ac8edbfab7c84a90aa0f43#commitcomment-9386895>
> .
>


numtests set back to 40 : https://github.com/Sweet-kid/p5-io-socket-ssl/commit/478912ee253d4a3e4082b310c5901d6980492d5a


83442720-ERVZoneMult-Issue4338 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Build Failed

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


You can actually get to headers and event desceiptors given an event. For example, event_object.header returns you the header associated with the given event. We tried embedded objects which became nightmare in no time. You can use individual find_header and find_event for cleaner interface

On Jan 21, 2015, at 5:59 PM, Dan Allan <notifications@github.com<mailto:notifications@github.com>> wrote:

I am writing for the future metadatastore, where (it seems) find may simply return a list of events.

We have to loop through the events anyway, as we unpack their data and check whether they have external data to be fetched from the File Store. At that time, we can get their descriptors, run headers, etc. A function returning a long tuple is not very user-friendly, especially when the order of the elements in that tuple is not obvious. x, y, z = f() is usable, but I think h, bc, ed, e = f() is not.

—
Reply to this email directly or view it on GitHub<https://github.com/danielballan/DataBroker/commit/083c7ed0f3deb9922e83fe3d26899c25d0467dc6#commitcomment-9386966>.


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


All $array[ x ] are used in like, so this commit https://github.com/Sweet-kid/p5-io-socket-ssl/commit/63aea7fb198c32b8194c77bd8101e23b3767cfb2


What is the floor here about?


I have made the changes. Could you please review it again?

Thanks.


Yes, I know -- but it resets all to 0.


Yep, all of them


Can this logic be factored somewhere else? This serves a similar purpose to code in PlaceholderRenderer when appending placeholders to the scroll list.


TeamCity MonoGame :: Develop (Win) [Build 3.3.0.1949](http://teamcity.monogame.net/viewLog.html?buildId=5032&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **FAILURE**
Summary: Snapshot dependency failed: MonoGame :: Develop (Mac) Build time: 00:00:00


@jnioche oh right, sorry forgot about that!


@jdorweiler I think we can leave localstorage there too if it works.

At any case, feel free to merge this at your earliest convenience.

Thanks for doing this!


At the time of this riding json v1.7.7 is incompatible with Ruby v2.2.0. Would it be possible to upgrade this dependency to json v1.8? Could I submit a pull request with that change?


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 4 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/77/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 14 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/75/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for 1724a619,  (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/78/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for 1724a619, Took 6 s. (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/76/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Thanks for the changes @agrieve. Seems like you've also changed the default builder from gradle to ant. I thought the default builder for 4.0.x was going to be gradle?


body {
  color: #666666;				/*default*/
  background: #4bcaff;
}
a {
  color: #0088cc;				/*default*/
}
h1 {
  color: #FF0000;
}
h2 {
  color: #ffffff;
  text-shadow: 0px 1px 1px rgba(0, 0, 0, 0.2);	/*default*/
  background-color: #7a8a94;
}
.nav .nav-item a {
  color: #666666;				/*default*/
}
#manage-accounts .account-details {
  color: #666666;				/*default*/
}
.header-wrapper {
  box-shadow: 10px 0 20px rgba(0, 0, 0, 0.3);	/*default*/
}
.header-main {
  color: #4b565d;
  background: #4bcaff;
}
#page-title {
  text-shadow: none;
}
#panel-right,
#panel-center {
  background: #ffffff;				/*default*/
}
.user-menu {
  background: #FF0000;
}
.user-menu header {
  background: #FF0000;
  border-bottom: 5px solid #ffffff;
  box-shadow: 10px 0 20px rgba(0, 0, 0, 0.3);
}
.user-menu header h1 {
  color: #ffffff;				/*default*/
  text-shadow: 0px 1px 1px rgba(0, 0, 0, 0.2);	/*default*/
}
.user-menu h2 {
  color: #4b565d;
  text-shadow: 0px 1px 1px rgba(0, 0, 0, 0.2);	/*default*/
  background: #ffffff;
  box-shadow: none;
}
.user-menu .nav-item > a {
  color: #4b565d;
  text-shadow: 0px 1px 1px rgba(0, 0, 0, 0.2);	/*default*/
}
.user-menu .nav-item .plugin-ico,
.user-menu .nav-item .course-ico {
  background-color: #4b565d;
}
.grades .section-name {
  color: #ffffff;
  text-shadow: 0px 1px 1px rgba(0, 0, 0, 0.2);	/*default*/
  background-color: #7a8a94;
  border-bottom: 1px solid #ffffff;		/*default*/
}


/usr/local/bin/node seems to be the standard. Ideally you would install node.js for the local user so that you don't need `sudo` to install node.js modules.


Elephino!


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/79/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Intentional. I want the limit to be 1/s and 2/s


I think the standard convention for Javadoc comments on methods is, for example:
"Scores local alignment for a given position in the query sequence."
So: use the third person, omit the subject, and end with a period.

http://www.oracle.com/technetwork/articles/java/index-137868.html

I mention this because I'm often tempted to do the opposite from what you did here; e.g. change "Score an alignment" to "Scores an alignment" :)


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/80/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 11 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/77/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Thanks for your concurrence.
Please see Community for extensive discussion on this Topic, keeping in mind that not *all* of the theory is a priority. As mentioned in one post, even enforcing the "proper" use of Capabilities via strongly worded documentation and the Publication Certification Process may be sufficient in the short term.

http://community.smartthings.com/t/capabilities-interfaces-i-think-capabilities-must-be-very-strictly-defined-and-enforced-attributes-commands-maybe-even-events/9917


@wluyima by the way, needing to do a Thread.sleep should be a hint that something is wrong. (This is actually the bug TRUNK-4580.)


Don't forget to update the link on your website (http://hashids.org/php/) to the correct archive to download


2.2.0 or 2.0.0?


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/81/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


@jeffmccune When will this be released?


Job scala-2.11.x-validate-publish-core failed for 1724a619,  (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/82/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for 1724a619, Took 10 s. (ping @folone) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/78/):
If you suspect the failure was spurious, comment `PLS REBUILD 1724a619f90ac4bf94168f01d6ca0f7989a6efd5` on PR 15 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 10 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/79/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/83/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


eq helper foi removido do dust core


I'd prefer simply:

    Rate Wiki pages, and browse them by average ratings


It's a pretty dumb commit but whatever. Also, on success you might not want to be print to stdout instead of stderr ;)


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/84/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/85/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 11 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/80/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/86/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


I'd prefer to have:

    Ratings Module API

For homogeneity with others such as Mail Sender API, etc.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/87/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 11 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/81/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/88/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Define a void return to match the caller.


Job scala-2.11.x-validate-publish-core failed for b4ff0c67, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/89/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for b4ff0c67, Took 10 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/82/):
If you suspect the failure was spurious, comment `PLS REBUILD b4ff0c67a28f8b011e8403673be28044ceee2657` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Can 'address' be pass here instead?


This was mistakenly added to the stage branch. However, it doesn't affect the users in any way, so leaving there.


I am using this feature for almost two years, so from my point of view, it's complete and now is time to test it in wild. For testing is ideal branch or PR, but unfortunately nobody will test it until it is merged.

ad 1) maybe, but I think that name `cache` better express, that it is used for better performance

ad 2) probably yes, it can be added

ad 4) Alternative for `eval($method->body)` is to create whole container:

```php
			$dolly = clone $class;
			$dolly->name .= '_router';
			eval($dolly);
			$container = new $dolly->name;
			$router = $container->getService($this->prefix('router'));
```

But - there is again `eval()`. So I used simpler way with its limitations.


I'm not sure what you mean by not copying the files - I forked from the main repo, cloned to my computer, opened those files, wrote my code, then added and committed. What specifically do you mean by making changes to the files themselves? @openspectrum


Job scala-2.11.x-validate-publish-core failed for a3e6f8ac, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/90/):
If you suspect the failure was spurious, comment `PLS REBUILD a3e6f8ac28940f2cf0a24249a4dc336b2d42d183` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


Job scala-2.11.x-validate-main failed for a3e6f8ac, Took 11 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-main/83/):
If you suspect the failure was spurious, comment `PLS REBUILD a3e6f8ac28940f2cf0a24249a4dc336b2d42d183` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


End of review.


@ExSport it works by loading the higher numbers before the lower numbers :) we developed it for Panasonic renderers mostly, so now we have good detection of specific Panasonic TVs instead of just using the generic config for them all.


Job scala-2.11.x-validate-publish-core failed for a3e6f8ac, Took 1 s. (ping @adriaanm) [(results)](https://scala-ci.typesafe.com/job/scala-2.11.x-validate-publish-core/91/):
If you suspect the failure was spurious, comment `PLS REBUILD a3e6f8ac28940f2cf0a24249a4dc336b2d42d183` on PR 19 to retry.
NOTE: New commits are rebuilt automatically as they appear. A forced rebuild is only necessary for transient failures.
`PLS REBUILD` without a sha will force a rebuild for all commits.


VSEARCH 1.0.8 incorporates a number of fixes and changes:
- fix for bug in alignment in rare cases
- fix for alignment of long sequences (>15000bp)
- fix for lack of detection of under- or overflow in SIMD aligner
- default maxseqlength set to 50000
- new linear memory aligner for alignment of longer sequences reduces memory requirements
- a new cluster_size command that sorts sequences by decreasing abundance before sorting
- cluster_fast will now sort sequences by decreasing length, then by decreasing size and finally by sequence identifier
- help messages for clustering have been improved
- in uc files, perfect alignment is indicated with "=" sign
- meaning of userfields qlo, qhi, tlo, thi changed for compatibility with usearch; new userfields qilo, qihi, tilo, tihi gives coordinates ignoring terminal gaps
- a few other small fixes

Documentation is not updated yet.

Alignment of long sequences is slow because it is performed by an exact and optimal algorithm. VSEARCH works best with sequences less than 5000 bp long, but should now work correctly with longer sequences as well.


It could have, yes


Love this script of course.  Would be great if one of two things could be done.

Either display the lowest price found within the user's own group (if found).  That price could be displayed next to the lowest price found overall.

Or, even better, make it possible to search for the lowest price within one's own group.  Maybe use a shift-$ and then it could search a max number  times (e.g. 10 or 15) or just until the user's group comes up.  It could also display the lowest price found next to the group's price found (if found).

It's great to find a lowest price, but I often want to price my items lowest for my group--not lowest overall.


Chris, this will cause a failure in contexts in which git is not available - in general, this versioning mechanism works as written for a number of packages - please try not to change it.


@ryanjduffy
After `this.show()` is added, `show()` in moon.Popup is called twice when I click popup button in PopupSample.html.
Do you have any special reason for this line?
Thanks :)


Use $log.warn


For consistency, IsLeader should have been added to events_handler.go as well.


Maybe isTypeOrUnionOfKind? Not a big deal though


@miketaylr Maybe time to introduce needscontact?


Nvm. Sigh, provider phase! One of the worst parts of Angular's API.


The terminology is a bit off. This is _not_ a URI.


There is a error... missing the solve() function


The asterisk is neither a path nor a URI


Those are the correct steps, but when you saved the files you must have saved them to the main folder of the repo, not the `exercises/` folder. That's my best educated guess on what happened. If you take a look at the source repo https://github.com/codeunion/ruby-exercises, you'll notice that there are no `*.rb` files in the main folder, they are all in `exercises/`, whereas in your repo the files you edited are in the main folder.


It's hard for us to get in touch with users, so this feedback is really helpful. Please tell me more about how you were using `build`. If you could show me your `peru.yaml`, that would be amazing. We're hoping to add in a few features to replace the most common use cases for `build` before we officially release these changes -- one of these is `unpack` for the curl plugin, and another is some way to declare that files should be moved or renamed. It sounds like your use case might be pretty generic; maybe we should support it directly? We're also encouraging people to write scripts that call peru and then do whatever postprocessing they were doing before with `build`; does that sound like an approach that would work well for your case?

There are several different places where we've been thinking out loud about why we want to delete `build`. #29 has a lot of it, though it's not very well organized. Here are our main reasons, starting with the most important:

1. **Security.** Like git, peru should be safe to use on untrusted repositories. `git clone` doesn't automatically install hooks of any kind, and I think one of the big reasons for that is that it could execute evil scripts without users knowing. Similarly, `peru sync` should be safe to run even when you don't know exactly what you're fetching. The `build` field was alright when it could only be defined in your own project, but we're adding support for recursive imports (see #29 again and [one of my branches](https://github.com/oconnor663/peru/commit/7e4c985a1f4555ab010b8e3ae0dc51599c0f0d6c)), and that would require running other people's builds. That alone probably means we *have* to git rid of the feature. Workarounds like only running `build` commands locally by default are possible, but I worry that would end up being confusing.
2. **Portability.** We had a few ideas for making `build` work on Windows and Posix at the same time, but at the end of the day they all required you to write the same command twice. That seemed pretty crappy to me, because by having that feature at all we'd be encouraging users to make their projects hard to test and maintain. I also felt like we'd end up writing in the README something like "peru works on Linux, Mac, and Windows (but if you're using Windows, stay away from the `build` field)," which would make me wonder why we included it to begin with.
3. **Simplicity.** Peru is *just* getting started, and we've been trying to keep the feature set as small until we know more about what's really needed. Believe it or not, we actually deleted a couple major features before we even shipped it (https://github.com/buildinspace/peru/commit/c639e31f36eaa3e50d8d65f8d8156c31c460e6f3 and https://github.com/buildinspace/peru/commit/d374aa4d5415b658565e474143681f1bc0fae411). We could've solved the portability problem by creating a little build minilanguage, like our own internal version of Ant, but I think something like that would add a ton of complexity to peru, and I doubt we'd do a very good job of it.


At the very least the problem is with the FitsHeader class, not with the WCS classes.  So this commit should be reverted and the problem should be fixed at the source.

The problem is that in FitsHeader, we allow a dict to be passed in and used as though it were a fits header.  But it doesn't actually convert it to a real pyfits or astropy `Header` object.  And the `__setitem__` function assumes that `self.header` is a real `Header` object when it checks how to add the given item to the header.  If you provide a (value,comment) tuple to `FitsHeader.__setitem__` and the header is really just a dict, then it does the wrong thing.  This is a bug.

There are (at least) two options for fixing this:

1. Change `FitsHeader.__init__` to convert a provided dict into a real `Header` object.  The down side of this option is that dicts are much faster to use than `Header`s, so there may be some performance loss from this change.  Letting the code pretend that a dict is a real `Header` is faster when that is possible.

2. Change `FitsHeader.__setitem__` to check if `self.header` is really a dict, in which case just ignore any comment component to the `value` parameter.  It's not like the `FitsHeader` class currently knows how to write itself to a file anyway, so those comment are really wasted.  Ignoring them won't have any detrimental effect to the functionality of a `FitsHeader` object.

3. Or I suppose a third option is to change the doc string for `FitsHeader` to tell people that they shouldn't use the syntax `header = (value, comment)` if the `FitsHeader` was initialized with a dict.  And then change all the code in the wfirst function to not use comments.  Not really a fix, but the most expedient option at the moment if you don't want to bother fixing this now.


@phathocker this change was first released in puppet 3.4.3.


Aren't the next, prev links already given in the JSON?


Thabk you very much it works :100: % :)


This will interrupt all other commands requiring chassis including its default one that drives the robot. In general, the accelerometer doesn't have to be a part of the chassis, it's just a sensor.


Ah! Gotcha. So github basically compares the code you've committed with the code from the folder you are pushing to, and only shows the differences in the commit.


The plan of action that we determined to go with regarding this conflict is actually to create a header that will be `#undef`ing all those conflicts and to include it right after the system file that includes `windows.h`. Something like this: https://github.com/ethereum/cpp-ethereum/pull/832/files

In the linked PR I am not actually including it where the problem is (where the system header include happens) because at the time of writting I don't have a Windows VM or a Windows machine. If you could do that then this would be really awesome. Also leaving the `#error` in `Tokens.h` with a revised message would be advised in case someone at some point in the future messes with this again.


It makes it so that if there is a large amount of Tumblr posts then it can parse them faster.


the service should get the user visit count, no need to pass it in


errors


I don't think this should have the special Doxygen comment `/**` because it will make it show up in the plugin API reference, but it's not (nor should it be) part of the public API. Next time we break the ABI, we can just delete the old `sci_set_font()` and rename this new function to `sci_set_font()` and plugins will get the new functionality for free.


GetX and GetY return acceleration (in g-forces), not speed. The speed will be an integral of acceleration. And the coordinates, which are what we ultimately are looking for, will be an integral of speed.


Aren't you missing a ``source bin/activate`` somewhere here? And also the ``plone5devel`` checkout and ``plone5devpy`` folders... do you want this extra folder for virtualenv although is not used? Or did you want to reuse ``plone5devel``?


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1095 of 1095 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)


this path is deprecated, limit 1


colon separate


I think we need to make note of this commit in the Biojava 4 release notes, since it's extremely backwards-incompatible yet can go unnoticed by users. After recently updating to a new snapshot of Biojava, I had to fix several tests in my project after determining that this was the breaking change.


colon separate model first


the `splitPage` function already does this check, and you never "store" the pages list, so you don't need the defensive copy.  So I think you just need:
```java
List<Page> pages = splitPage(page, DEFAULT_MAX_PAGE_SIZE_IN_BYTES);
```


That comment is actually removed in a later commit, you can ignore it.


fair enough


Do you intend to keep this floating on purpose? I guess there's no harm, since this is the only consumer of ocflib thus far


also, seems like this should live in Game model


duplicate


nope


If this runs in a virtualenv, python ought to be fine


you'll have to explain this to me


This PR looks good to me.   The only thing I don't understand is the code above, which seems reversed from what it should be.   I.E. I would expect:

```
has.add("desktop-like-channel", function () {
	return !mqSmall.matches && !mqMedium.matches;
});
```

because if it's not small and it's not medium, then it's big, which suggests desktop.


Fixed in 0d5d12e02a1f80d131002c520826863ce8ed1d0c.

It's still not as compact as the Fonts & Encoding format, but getting there takes time.  Need to support dumping certain values as XML attributes as opposed to elements.  When I do that, I should apply it to all tables, which will make the XML format much more desirable.


Why was this line dropped?


Yeah, I can add it to the regex. I would prefer adding the concept as a whole (UI, backend support, etc.) in a single PR though.


all tests pass:
success: http://buildbot.bos1/builders/python-client-test/builds/326


I'm not completely clear on this. It seems like rspec 2 permitted `lib/puppet/util/feature.rb`'s `method_missing` call to kick in returning false at https://github.com/puppetlabs/puppet/blob/3.7.3/lib/puppet/util/feature.rb#L61.

But rspec 3 doesn't allow things to get this far, instead failing like this:
```
  1) Puppet::Util::Feature should consider undefined features to be absent
     Failure/Error: @features.should_not be_defined_feature
       expected #<Puppet::Util::Feature:0x007fe19c1046d8> to respond to `defined_feature?`
     # ./spec/unit/util/feature_spec.rb:13:in `block (2 levels) in <top (required)>'
```

This was one of a couple specs that didn't port to rspec 3 cleanly due AFAICT to differences in rspec 3's metaprogramming (or what it permits the code under test to do metaprogramming-wise). I didn't find clear/any documentation on these changes (though I did get help in #rspec on a couple issues), and I wonder if they came in with rspec cleanup (as opposed to an explicit feature change).


develop (Myoldmopar) - 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)


Its a bool for process additions where I check return to not add over and over into exported tables list.


The page may have zero blocks so you should construct the page with the position count, which the length in this case.  You will also need to verify the bounds of the start and length are within the page. The blocks already do this, but you may not have blocks.  Here is the code blocks use:
```java
        if (positionOffset < 0 || length < 0 || positionOffset + length > positionCount) {
            throw new IndexOutOfBoundsException("Invalid position " + positionOffset + " in block with " + positionCount + " positions");
        }
```


I'll add that I think option (1) is the best choice despite the possible performance hit. (I don't readily recall how much a hit it is -- I suspect it is probably quite modest, tbh.)  This would allow us to advertise that a `FitsHeader` object has a `header` attribute that is the real astropy.io.fits.Header object.  Making this statement always true is probably the cleanest implementation.


Great. I was counting on using `event_object.header` and `event_object.event_descriptor` and so on. I'm not sure what you mean by embedded objects, but as long as attributes like these work I can move forward.


lol good catch


Thanks, Just send you an email.


We might change that behavior due to foreign key changes Stuart requested earlier this week. Let's get together and find the best way to do this.

On Jan 21, 2015, at 6:51 PM, Dan Allan <notifications@github.com<mailto:notifications@github.com>> wrote:

Great. I was counting on using event_object.header and event_object.event_descriptor and so on. I'm not sure what you mean by embedded objects, but as long as attributes like these work I can move forward.

—
Reply to this email directly or view it on GitHub<https://github.com/danielballan/DataBroker/commit/083c7ed0f3deb9922e83fe3d26899c25d0467dc6#commitcomment-9388070>.


I think that's fine, base-4.4 has been out for a while now.


テストコメント


Pretty much. In a pull request, GitHub will compare the commits in the two branches and show you what is different. If there are commits that add new files, it will show them as new files.

The deeper issue here is that `exercises/min.rb` and `min.rb` are _different files_, even if they have exactly the same contents. Git understands filenames as _full paths_, which includes their directory.


probably don't need to update the image every time, only when the rect is changed


Auch, it should indeed be renamed into something like ```SecondField()``` or ```RequestPathOrResponseCode()```. I'll keep an eye on it. Thanks!


[![Morning Girl Reading a Letter](http://api.artsmia.org/images/120730/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=120730)


テストコメント２


本部区分を条件に抽出条件に追加


Thanks.  I guess requiring base>=4.6 should fix this (along with the other base version issue).


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed

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


>essa última frase

Isso é bem divertido.


I see. Strange, looks fine on Firefox on Windows.


Ha! The answer is that it doesn't and there is no test coverage for the methods in this file that use it. That's embarrassing. Will happily accept a PR if you've got one - otherwise I'll fix in the morning.


Yeah, I'm not sure about imposing a constraint on all pages for the sake of a visual gimmick on one page. Although these ribbons were popular when they were announced, I haven't seen those on other websites in a while, it must have been a fad.


Let's do this only if we also move the search boxes.


Can I have Tutorials or User Guide for use your code?


Moved GMT Offset setup inside Event loop. It was being reset to 0 because of all day events and not set back.


Yes. Require needs this so it can pass it back to whoever is requiring this module. The test file for this is located at test/src/require/test.js. I've added 'require' to the test name so is easier to differentiate


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

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


Nope, this breaks `<%= 0 %>` which is a falsy value.


I'm sure SDL_VideoInit() would fail if called with a module the user doesn't have.  So that's why I suggested before to let the user decide which module.  But maybe it's just a redundant way of setting SDL_VIDEODRIVER?

I didn't think SDL_Init() was necessary since we are not using any other SDL modules.  SDL_Quit() should just quit everything, if I read the manual correctly.  Anyway, it works for me :-)

The config system is annoying.  I'm not sure what to do about it yet.  It would be nice to have a config menu inside the window.  But startup options are still required in any case.


Is the `std::move()` necessary here?  `covariance` is already an rvalue reference.  I am still getting used to C++11, so my understanding could be wrong. :)


That makes sense.


I think these empty `restrictChildrenTo` specs help address https://github.com/danneu/guild/issues/11


这里可以直接俄使用下面的fork过程，和下面的execute_task合并，这样master很快就可以知道下发任务是否成功调起

如果fork失败，返回给master知道任务调起失败，这样master还可以再次调度，而不至于在这里就结束了


I'm thinking the global URL variables (gUrl, etc.) will have to go if I'm going to start messing with the browser history and current page URL...


Dragonish, correct as it may be, sounds slightly terrible.
Gonna go all D&D up in here and change it to Draconic ;)


Ugh I don't know. It's certainly not wrong and is the way I've done it to ensure the behavior I want. Honestly every time I read an article about rvalue references I just get frustrated at  the complexity of C++ and give up. If you want to diff the asm w/ and w/o the `std::move` you have my 100% support :)


@vsok OK. Please send the PR.

Thanks.


On Tue, Jan 20, 2015 at 07:13:15PM -0800, Stephen Tu wrote:
> Ugh I don't know. It's certainly not wrong and is the way I've done it
> to ensure the behavior I want. Honestly every time I read an article
> about rvalue references I just get frustrated at  the complexity of
> C++ and give up. If you want to diff the asm w/ and w/o the
> `std::move` you have my 100% support :)

Sure, I'll do it.  I want to understand std::move and rvalue references
inside out, so I'll do some testing and let you know what I find out.

--
Ryan Curtin    | "Happy premise #2: There is no giant foot trying
ryan@ratml.org | to squash me." - Kit Ramsey


I actually just realized that if the .all maps to a database query, it's probably better to do what you want with a method on the model, which will turn into a database query (this means you don't have to fetch all of the data into your program, and can just let the database do what it's good at: manipulate sets).

I think if you do
    !getComplete().exists()
django will handle that efficiently


Detect Magig always returns false.  :smirk:


Should probably be named getComplete for consistency


Other than the typo, :+1:


没有添加按行输出功能之前，对于一个文件的输出是不会生成list的，而是一个字符串向量。写入文件则写入一行。

如果这个新加入的选项默认是 bylines = TRUE ，对于一个文件的默认输出，会输出list，写入文件会写入多行，新旧版本 jiebaR 的结果就会有比较大的差异。

默认 bylines = FALSE，可能你不知不觉中更新了新版本的 jiebaR ，没有注意到这个新添加的选项，但是也可以进行分词，得到的结果还是和之前一致的。

有点最小惊讶原则的感觉。

----------------

还有，如果结合 tm 包，对于处理一个文件，bylines = FALSE ，输出字符串向量是不是更合理呢？


why I can't find IFormFile


No problem, glad you got it sorted out


What does the completed property do for a todo list?


zip は rubygems なので app で bundler/setup を require した後に require する必要があります。


なるほど。


I think the use of the word "interpret" in the Armadillo documentation about `trimatl` and `trimatu` is somewhat misleading.  What the function will actually do, when used in that context, is loop over the upper triangular part of the matrix and set it all to 0, so this ends up actually just burning cycles---also because the `operator=()` evaluates the expression and strips the knowledge that it's a lower triangular matrix.  So then the call to `.i()` doesn't actually do anything smarter.

But perusing `fn_inv.hpp` more closely, there is a specialization that will work when called like this: `inv(trimatl(covLower))`, and will use LAPACK's `?trtri` functions.  However, it will still set the upper triangular part to 0 after the method.  That last part is unnecessary, but baked into Armadillo, so there's not really much that can be done about that without discussion with the Armadillo maintainer.


terminal.init() had caused me problems off and on as well.


恩，有兴趣来参加R会议啊。


This proposed fix won't work, the reason being that the click is triggered on a button/input but the action handler is on the form element.

I think the answer is never canceling clicks on submit-type buttons with the reasonable expectation that submit events will be handled appropriately.

`var cancelIf = $element.is('a[href], button[type!=submit], input[type="button"]');`

This removes the check that the input has `type="submit"` and adds a check to ensure the button does not have `type="submit"` (which is allowable, but has poor cross browser support)


I’m not sure what you’re asking here—the signature for Apply is:

```go
func Apply(seq interface{}, fname string, args ...interface{}) (interface{}, error)
```

The most complex way that I’ve used it is:

```go
links, err := Apply(Apply(links, "partial", "post/tag/link", "."), "chomp", ".");
list, err2 := Delimit(links, ", ");
```

So…that third parameter is varargs and *should* include the `"."` so that the value is provided to the method…but nothing says you *have* to do so (it’s just very silly if you don’t, as your test case proves). However, it cannot *only* be one argument because the function you’re applying against may require more than one parameter (as `partial` does).


这里有冲突的地方大家看看是不是正确，上面也是，


*cough*


The script that I used to preform the update is at https://gist.github.com/sayedihashimi/fd04142e167fffef514b


There was a pull request that probably should've averted this whole thing. https://github.com/vanilla/vanilla/pull/2125


@GwonHyeok ㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋ ㅈㅅㅈㅅ ㅠㅜㅠ


does the `>=` with the `ruby` directive in the Gemfile actually work? I think even with the `>=` it specifies 2.1.1 only?


Perhaps name this `accessed?` to correspond to `accessed` method on attribute set? Additionally, "read" is more likely to be confused with "loaded from database".


@jbaltazar this is good, however for the future iteration, I highly recommend that you do shorter method. Your get method can be broken down into smaller pieces. It will be easier to debug/maintain in the future.


The thought here is that if a user calls `Estimate()` with no observations, then we should try and provide a `GaussianDistribution` that is properly trained on zero observations---which basically is an uninitialized `GaussianDistribution`.  I don't think it's necessarily something that an error needs to be thrown for, but I could go either way.  The idea, at the time I wrote the code, was to avoid crashing out when possible and provide consistent behavior, and I think this is consistent and what a user would expect if they passed in zero observations with which to train a Gaussian (feel free to disagree -- I'm happy to change my mind if my opinions are only my own).


HVACSizingSim_CoincidentPlant (EnergyArchmage) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: Coverage Too Low

![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-2.32%25-red.svg)


@jbaltazar it is a good habit that you are adding some comments to your code! For improvement in the future, I would place all the constant outside of the method.


This case is a little different and could arise during HMM/GMM training: during `GMM::Estimate()`, the algorithm may, due to poor initialization strategies (potentially written by the user), decide that one particular `GaussianDistribution` is so incredibly unlikely that the probability of any point coming from that particular Gaussian is less than `DBL_MIN`.  Whether or not providing a barely-positive-definite covariance matrix and zero mean is the right thing to do in this case is another question, and I'm not sure it is.


lgtm


好的，谢谢~不过感觉就是一个小包，没太多功能，没什么好讲的，哈哈


The more I think about this, the more I wonder if it's a good idea to preventDefault clicks on links.  The clicks aren't sent through Ember anymore, and we aren't yet providing a fallback to trigger `a[href]` on tap.  I haven't bumped into this myself because we don't have links to content outside our app's scope, but I'd assume this would break such links.

It's ok to break onsubmit onclick functions defined directly on elements within Ember's scope, but `href` should be made to work (and work quickly, such as with fastclick).

In one sense, this is an argument for the conventional approach of having taps/touchEnds trigger clicks in ember, in another sense, I still think since tap/press aren't truly clicks at all we shouldn't be exposing them as such.

Hammer doesn't actually use 'click' for anything, so we could simply trigger clicks on the links on tap (just as fastclick does) without fear of causing duplicates.

Thoughts?


Good catch -- thanks.


Mind if I move this into `mlpack::math` somewhere?  (Maybe `lin_alg.hpp`; it may be useful elsewhere too, outside of `GaussianDistribution`.)


How do you distinguish between these two buttons?


Might want to change line 6 in the original repo :)


Considering how many devices Thorlabs has, you need to be more specific than that.
http://www.thorlabs.hk/navigation.cfm


Ok pypy is way faster. I still didn't get it to work with either ios6 or ios8 client. Basically the airtunes parsing of all the params just has to much ios7 specific assumptions but i think i might be able to adapt for this (or provide a wireshark dump for you in case i fail). Also if you could make the videostream available as http url you could make kodi play the url via jsonrpc ;) - well the fact that i don't have any ios7 client available motivates me for sure - if it wasn't the lack of time.

Also thinking a bit of the future. Do you think it would be possible to natively execute the airtunesd code on arm platforms? (i think the python emulator would be to slow on those maybe) Is some sort of asm passthrough possible?


extra </li>


How to create the virtual no.s ? Could you help ?


@gabpaquin Yes, will do. As of now Im doing it straight forward because the API and the database in openstack is not yet in the final stage. specially because all of this is for the demo purpose only.

Im going to remodified all of this when the server is available


These traits are there to present typeclass instances for specific data structure, so I don't see `DatePicklers` as is-a relationship with `PrimitivePicklers`. It simply requires that `PrimitivePicklers` be part of the trait stack at the end of the day.
The benefit of this approach is that the user of a-la-carte trait get to determine the trait linearilization, which becomes more meaningful if `super` gets involved. Effectively we get to retain the same amount of flexibility as `def datePickler` with implicit `SPickler[String]` parameter.


@markstuart is a bad ass guitarist


Fair to omit that math because it is annoying, but I run my firmware at 48 MHz and use the TRM suggested 4 NOP sync and I have had no problem. Longer sleep cycles to be sure are a small thing, I just don't know why I have never needed symc above 4 NOPs.


Did you keep the first parameter strings for consistency with the rest of the test file?


Consensus is spelled wrong :)


时间可以自由长短啊。


Yes, didn't want to rewrite the whole thing and felt wrong leaving it out.


good catch! :mag:


Also, if anyone is actually using this branch on their server, please do add me - I'd like to hear how it's going.


@gabpaquin about the constant variable. Just ignore it. I use all of them to connect in the US Server because Im currently working in my local unit.

When the server is available Im going to remove all of the constant and use the openstack self value.


print("hello world")


コメントの練習


Change words as mention by assignment.


Some third-party library can define:

```scala
package foo

import scala.pickling._
package object serialization extends PickleFunctions with picklers.AllPicklers {}
```


files in the folder installer are copied from XenServer 6.0.201 installation cd, just ignore them


On 1/20/15 12:43 PM, Frank Filz wrote:
> This is still racy.
>
Where?  Please be more specific.

I've moved the DS puts out of their natural home in fsal_export
->release(), into the AVL tree removal.  Obscure, but should work.

> PUTFH may have gotten a fsal_pnfs_ds reference and cached pds->serving, but not yet taken the export reference.
>
(1) The reference on pds->serving is taken in create_export().

+ get_gsh_export_ref(op_ctx->export);
+ pds->serving = op_ctx->export;
+ op_ctx->export->has_pnfs_ds = true;

(2) For PutFH to take the export reference (technically on
op_ctx->export), the export has to be "ready".

+ } else if (export_ready(pds->serving)) {
+ get_gsh_export_ref(pds->serving);
+ op_ctx->export = pds->serving;

In both cases, the ref is taken *BEFORE* storing the pointer.

(3) Now look at EXPORT_STALE, which is set before pnfs_ds_remove(),
which is where that put_gsh_export() happens.

(4) After EXPORT_STALE, it is not likely for PutFH to get the ref.

Plus, this code detects the possible pds->serving CPU cache sync
issue, and clears it (again) locally!  (PutFH line 148.)

But more importantly, there is still one more long-lasting export
reference, which is held until the export destruct thread.  Unless
some other legacy part is badly written....

So in the absolute worst possible case, a successful pnfs_ds_get()
AVL tree access, followed by a CPU cached pds->serving != NULL,
followed by a cpu cached EXPORT_READY, merely allows another
get_gsh_export(), instead of returning ESTALE.

It won the race.  Boo hoo.  It will check again on the next PutFH.

> The export reference taken in association with the DS needs to be taken inside pnfs_ds_get while holding the server_by_id.lock. THEN we can rely on the idempotent removal.
>
I'm trying to keep rw locks as short as possible.

Whether or not it's inside, the pDS won't be accessed by PutFH
until the MDS (export) passes a DS handle back to the client.
It cannot yet do that, as it hasn't even begun connections.

Look at the forest, not just the trees.

> And we may not need pds->draining.
>
Maybe not much yet.  But I'm looking at using it in the future,
in much the same manner as you are using the export_ready().

> And pds->serving SHOULD only be accessed by pnfs_ds_get, pnfs_ds_remove, and the FSAL code that sets it in the first place.
>
No, that's not accurate.  The whole point of its existence is
for PutFH and Save/RestoreFH, to avoid a gsh_export_lookup() in
the fast path!


Looks pretty good.
Two comments:
* Can we add a test case for a 3-element AndTerm (and, maybe, OrTerm)? The representation allows this, as it follows directly from the grammar.
* How do you feel about moving the code for creating test IR nodes/trees out of the specific test cases so they may be reused by other test cases? Perhaps into a fixture?

Fine to merge as-is, though.


I mean it does NOT work.


Ghi câu khác đi :)


câu nào cũng được


Yep, I don't plan on removing that method.


This commit summary does not meet the [commit message standards](https://wiki.freenetproject.org/Coding_standards#Commit_Messages) because it is not phrased as an imperative command to the codebase. Could you please reword it to be something like "Add common parameters for argparse support"?


since passing the whole graph back n forth on every hover event is pretty slow, we should either:

- A: Not pass the full trace back on these events, and require the user to call `graph.get_figure` if they actually need the raw data

- B: Allow the user to supply some JS filter function that pre-processes the data in JS land before passing it back.

I think I'm in favor of A, but maybe I'm missing some limitation


not sure why this is the case, we might wanna update this on the JS side at some point


Name class must be equal filename.java


Aww!  What a pleasant surprise!  Thank you for your compliment!  *blush*  You made my day!  :-)


Looks pretty safe to me.


I tried it a different way that is more fine grained.  It seems to work.


Some of the AMIs don't seem to be available:

```
% aws --region ap-southeast-1 ec2 describe-images --image-ids ami-78fad22a
{
    "Images": []
}
```


oh ，I have found it in Microsoft.AspNet.Http 1.0.0-beta3-10806


fixed in latest version in test


:heart: