Support adjustment of the grayscale calculation. Still gray, but possible to get a different weight on the sources color channels by additional options.
As the default values are unchanged, all changes are opt-in for users.


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


@cindyli in the full page versions, the reset is an actual html 'button'. I don't think we will gain anything by adding an addition 'role' attribute of 'button'. What do you think?


No worries, happens to me too

On Thu, Nov 19, 2015, 10:15 Fabian Affolter <notifications@github.com>
wrote:

> Yes, they are...I would swear that the local test was successful but as
> usually I was wrong.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/balloob/home-assistant/commit/4eacea32da47d605edf09dd1720a244a2ae41e88#commitcomment-14508039>
> .
>


ah, dont worry about that. I am enrike hurtado, we briefly met last year
in Birminhan at the live coding conference. I work with thor magnusson
in ixi :)

og., 2015.eko azaren 19a 22:53(e)an, Sam Aaron igorleak idatzi zuen:
> May I know your name so I can add you to the list of contributors to
> Sonic Pi?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/samaaron/sonic-pi/commit/836fca59d3fe085697f471b57cd7e9ac629f7451#commitcomment-14512922>.
>


That covers most of it I think.
Additionally, I would like tests for attribute propagation, so append `test_getattr` with similar tests on for instance `capitalize(a)`


Probably need a similar enum for UserColor, but can throw that in later.


remove one of the ../ in the first line of this airframe.xml. The dtd is
now one folder up instead of 2

-Christophe

On Thu, Nov 19, 2015 at 9:54 PM, HooperFly <notifications@github.com> wrote:

> Looks like the conf/airframe rename might be impacting the bebop2 config.
>
> [image: screenshot from 2015-11-19 12 52 35]
> <https://cloud.githubusercontent.com/assets/10355071/11284055/9f951dee-8ebc-11e5-93a6-f767ca0426e7.png>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/paparazzi/paparazzi/commit/55cc13097850a51e73e113c990610300f3f63d2b#commitcomment-14511729>
> .
>


Peso:


It's handled by default in the engine


Spelling Error


Should this be removed?


Não trocável


`Application.ensure_all_started(:auto_doc)`


Don't be silly - thanks so much for contributing! You're now on the contributors list.

Hopefully you'll stop by again soon with ideas and thoughts or even another pull request...


Why using PyQt version 4? It's support is about to end in December. New projects should start in 5.

Should I send you a pull?


So I can comment on this here.


I think this needs the fully qualified name (including the module) ?


Hi,

When `@BeforeAll/@AfterAll` are on **interface default methods**, the validation(`validateBeforeAllOrAfterAllMethod()`) will fail unless either make the test  `@TestInstance(PER_CLASS)` or override/implement methods in test class.

Is this expected behavior?
Probably, it would be nice to have the default method behavior documented on `@BeforeAll/@AfterAll`.

Thanks,


Is there any specific reason why this commit isn't merged yet? I upgraded the whole LXQT today and had to apply this patch.


Not sure this is needed if you start the application in the test env with the above comment


`AutoDoc.Agent`


Is that because all CFD end with '_CUR' where 'CUR' is the curreny symbol?


I thought they had some measured in gold, (_AU)


Pourrait être dans une autre section, ça ne parle plus de **Pattern matching**.


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


TeamCity pull requests :: netty [Build 689](https://garage.netty.io/teamcity/viewLog.html?buildId=3380&buildTypeId=pulls_netty&guest=1) is now running


TeamCity pull requests :: netty [Build 690](https://garage.netty.io/teamcity/viewLog.html?buildId=3381&buildTypeId=pulls_netty&guest=1) is now running


Light source "Falloff level" amount to indicate how quickly it fades to black


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


But this breaks the Vector-valued case, and therefore the unit test.  Maybe we want something like

maxabs(vec(fr))


We have variable named as mdver_global_generation. So I am renaming to mdver_get_global_generation


TeamCity pull requests :: netty [Build 690](https://garage.netty.io/teamcity/viewLog.html?buildId=3381&buildTypeId=pulls_netty&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:37


I've realized this loses laziness.  For instance:

    permutations(100)[0]

hangs.   It shouldn't.

I suggest reverting this commit.


@michaelficarra it's sort of implied by this "you may use `var` to create a global variable that may be used by other scripts"


@jensens Tip: in coredev 5.0 you can do `bin/buildout -c release.cfg`. This adds `plone.releaser` which uses a few `zest.releaser` entry points, one if which automatically adds these lines, if you use the `bin/fullrelease` of the coredev buildout. It also updates the checkouts.cfg and versions.cfg.


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


Oops. I can fix that tomorrow.

Cheers,

Mikael

> On Nov 19, 2015, at 10:02 PM, Sheehan Olver <notifications@github.com> wrote:
>
> But this breaks the Vector-valued case, and therefore the unit test. Maybe we want something like
>
> maxabs(vec(fr))
>
> —
> Reply to this email directly or view it on GitHub.
>


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


Não pode ser refinada ou Não aprimorável
Depende se vocês preferem chamar de aprimoramento ou refinamento.


	Should we build in DualNumbers support?  We could make it a REQUIRE.

> On 20 Nov 2015, at 9:04 AM, Richard Mikael Slevinsky <notifications@github.com> wrote:
>
> Oops. I can fix that tomorrow.
>
> Cheers,
>
> Mikael
>
> > On Nov 19, 2015, at 10:02 PM, Sheehan Olver <notifications@github.com> wrote:
> >
> > But this breaks the Vector-valued case, and therefore the unit test. Maybe we want something like
> >
> > maxabs(vec(fr))
> >
> > —
> > Reply to this email directly or view it on GitHub.
> >
> —
> Reply to this email directly or view it on GitHub <https://github.com/ApproxFun/ApproxFun.jl/commit/81ee1e8c5e35a325e86235e877caf927e6e77466#commitcomment-14513174>.
>


This is not really an error condition.  This ImportError happens every time you deploy to production (unless you create an empty config_overrides.py).


This commit expects UDB [344]: https://github.com/unified-db/Database/commit/84e1179621887ee4f2d030ff02fd5795a4187c53


You can just say `r.json()` here.


Nevermind (as discussed on gitter)


If you look at .git/pre-push.sample, there's a commit hook to prevent precisely this (or maybe this was on purpose but I didn't connect "WIP" and the fact that it doesn't work)


#5287-EnergyPlus-crashes-when-assigning-2-UnitarySystem-to-same-zone (rraustad) - i386-Windows-7-VisualStudio-12: OK (1968 of 1968 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)


@jensens: You have released 1.4.9 today.  With that version, Jenkins fails to run some tests:
http://jenkins.plone.org/job/plone-5.0-python-2.7/3326/

```
[Errno 2] No such file or directory:
'/home/jenkins/.buildout/eggs/plone.api-1.4.9-py2.7.egg/plone/api/tests/doctests'
```

Same problem locally.  I have released 1.4.10, which seems to fix it. I did not do anything special.

Do you have an idea why the doctests directory was missing in your release? The MANIFEST.in was already fine. Can you try a `python2.7 setup.py sdist` and see if the doctests directory is again missing?

I can't really think of a reason why it failed...


OK, now I understand. I think all it's fine.


TeamCity LabkeyRelease15.3 :: CDS postgres 9.4 [Build 31](https://teamcity.labkey.org/viewLog.html?buildId=286321&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 13 (1 new), passed: 35 Build time: 01:13:18
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyLogAndLinearScales: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

##### there are 3 more failed tests, see build details
```


If you want a more adventurous King, maybe you can try a tweak on the following line,
since it is not touched by Weights[KingSafety]

// King shelter and enemy pawns storm
    Score score = ei.pi->king_safety<Us>(pos, ksq);


Stupid question: in OZZipFile.h, why were the initialization method signatures removed from the header?


I know that and you know that, but it may still be confusing to the same kind of person that would be confused by the replaced documentation.


Hmmm.  They can do  "ecl-packagemap-add" for any part they want to start a new packagemap with.  And then use "add-part" for any subsequent parts.  I didn't want to duplicate all of the features of packagemap-add.  Like --activate for example.  And I didn't want to turn packagemap-add into add-part.  But you can do packagemap-add and then treat that file as a part later.  To for example do a remove-part on the content you added via packagemap-add.


Normally, you should be able to move the statement `properties.getProperty("version", "dev");` outside of the try-with-resources. Then, the test should be green again.


Basically packagemap-add is now really "create-and-add-part".


Added the test


Now I can include link to RSS feed sometime later


103643052-FiniteDifferenceFluxOutput (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1960 of 1969 tests passed)

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


DUDE WHY DIDN'T YOU MAKE IT 666!?!?!?!?!?!?! YOU'RE FIRED!


That was code I copied.  Truth is I should do all the lowercasing in the ESP service.  I'll make sure that's being done, and remove lower casing here.


@JulioChavez: Did you fix the merge conflict in `workouts.client.controller.js`? Is it in another commit?


right.  but as discussed above I'll look at removing lower casing from the command line, and make sure its being done in the service.


[![CTU — Z](http://vignette2.wikia.nocookie.net/charlietheunicorn/images/0/03/Z.jpg/revision/latest?cb=20101127055012)](https://youtu.be/Fu2DcHzokew?t=5m58s)


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


Copy and paste error.  I'll change it.


;_;

lgtm, regrettably.


The rest of this class's ```create()``` is identical to it's parent's (Genome::SoftwareResult::StageableSimple) ```create```, as far as I can tell.  Why can't this whole ```create``` be removed.

As an alternative to this re-dispatch, what about some parent class have a ```create()``` to do the basic setup, and then call something like ```$self->_initialize_object()```.  Subclasses can then implement ```_initialize_object()```.  Or add support in UR for some equivalent of Moose's ```BUILD()``` function.


Fair enough, I figured this change made it quicker for me to iterate on fixing host + target = mingw-w64 on build = Cygwin or OS X since these don't involve either Linux or glibc. I can make the checks more targeted to Windows.

The only three projects I know of that either have files in the same directories with different cases or want to put the same in build directories are The Linux Kernel, {e}glibc and DDD. There may be a few others, I've not seen them yet though. Actually I think The Linux Kernel are removing the netfilter stuff in the future and I might try to upstream some {e}glibc patches at some point at which stage case sensitivity should be a non-issue globally.


TeamCity pull requests :: netty [Build 689](https://garage.netty.io/teamcity/viewLog.html?buildId=3380&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5324, ignored: 21 Build time: 00:14:42


looks good :+1:


Man, C++ is so cool. =]


Looks good other than we try to be consistent with the _ between words.
So the following variable should look like this.
{$ldap_name_filter}
{$ldap_number_filter}
{$yealink_directory_setting_url}


Heh. Included a line too many ☺

I'm definitely wondering why this is here though. Looks like a remnant of some test code.


> In every round except than the last, the pairings do not take care of tiebreakers. The algorithm randomly pairs players with the same amount of points the best it can.

The goal why tiebreakers are used in pairing is to move matches between strongest players to later rounds. I don't know why official rules are against tiebreakers in pairing, but I think current implementation doesn't differ a lot from random pairs between players with the same points. Actually for players with equal points current tiebreakers are often equal too, especially in the first rounds.
But if there is a reason behind this rule we can easily remove tiebreakers from pairing.

> For the last round, for each unpaired player starting with the first place, pair against the highest ranked player they haven't played against. Trackback if you can't complete pairings.

I think it's a good idea and it's easy to implement.

> Of course, players can't have the byes twice or play against the same player twice.

It's implemented using heavily increased weight of such events.

> I guess it could be a good idea to test with WER to see if there are mismatches in some extreme situations.

Yes, I think it will be interesting to compare with WER pairing.
I added test with some basic verification that simulate multiple tournaments with different number of players and number of rounds, it looks ok.

Thanks!


@charlie I think this `for` loop was the driver behind renaming this func from `GetMappingsCache` to `GetMappingIdToMappingMap`.

Given that I don't see `mappingCache.Set()` being called in the new function -- name it whatever makes more sense.


Thanks, now fixed (and tested the build even!)


Need to include server location in link? This won't work when hosted from GitHub.


I think this is an example of https://github.com/Gadgetoid/Pinout2/issues/35

An example of https://github.com/Gadgetoid/Pinout2/issues/35 in action. This will mean a 301 redirect is needed from ryanteck_motor_controller_board to ryanteck_motorsteuerung. This is probably going to happen very infrequently and GitHub will basically tell us what needs redirected, so I'm not panicking.. yet.


Ditto.


BTW, it's a kernel flag on Windows, so system-wide.


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


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


TeamCity LabkeyModules15.3 :: Git postgres 9.4 [Build 29](https://teamcity.labkey.org/viewLog.html?buildId=286332&buildTypeId=LabkeyModules153_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 14 (5 new), passed: 238, muted: 4 Build time: 01:06:24
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.CDSLoginTest: <no details avaliable>

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

org.labkey.test.tests.CDSHelpCenterTest.verifyHelpCenter: <no details avaliable>

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

org.labkey.test.Runner: org.labkey.test.tests.JUnitTest$RemoteTest.org.labkey.study.model.StudyManager$DatasetImportTestCase: <no details avaliable>

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

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

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

org.labkey.test.tests.CDSMeasureStoreTest: <no details avaliable>

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

org.labkey.test.tests.DataFinderTest: <no details avaliable>

##### there are 4 more failed tests, see build details
```


you have two self.screen.


So redirecting to a file will result in an empty file? >=[


Fixed in 5562d512d53503e20f410aa432cbe58ea542124b


close, but these should be empty strings... not missing completly


should all the above code be done with the query class?


sorry, where's the panic called from? can you print a stack trace?


b


I don't think you're using this. I think just remove it for now until you need it.


others should be too.


Thanks for the clear explanation. Seems like I completely misread the whole check.

I was thinking of something like /^[allowed chars]+$/, but since we do the opposite check to deliver a specific error message, it is clear that we do not only want to check if it contains only one of those characters.


I think this looks great!


Sorry for the late response.
I've seen it lately on other apps, I think they changed something in the Docs publishing.
Seems that for older projects, things are still working the old way, but for newer projects it's broken


Preço de venda: %s Pratas


I add a coment here!


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


I can see the changes!


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


Ah, thanks for this, forgot to move this.  Originally all of this was going to be in a test unit case but I decided to make it something more interactive later on.


I tend to agree with @bhundven here: if case-insensitivity triggers a failure in at least *some* packages, we'd better fail early and loudly than have end-users submit support requests for some cryptic failures down the road.

What I think could be an alternative is to introduce a "tainted" flag into he build, and in cases like this (a) emit a WARN at the start of the build and (b) emit it again in the end in case of an error. Inspired by Linux kernel, of course.


Estamina +9.000


The parent class of this class is `Genome::SoftwareResult::Stageable`.  I don't think it has a `create`, though, and the next level up is `Genome::SoftwareResult` itself.

This class sort of does the thing you suggest by having its children call `_run` instead.  It would be a lot to change, but I'd not be opposed to something similar for all `SoftwareResult`s.  It has long been considered a flaw of theirs that all work happens in `create`.


CMake-3-4 (macumber) - Win64-Windows-7-VisualStudio-12: OK (2337 of 2370 tests passed)

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


It's basically user permissions. For example,
```
0 - Regular User
1 - Developer
2 - Admin
```


@mkumatag just pushed up 0.3.9 onto pypi


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


Niice yeah all those changes look good ill change them when i get off work.  and the query stuff ill edit out in this and the export class.


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


I think 2nd one is better too, more consistent and will allow us to check more easily that everything's working if we print out the tree. Either one should be pretty simple in converting to the PAST. The rules for the second one will basically be
```ocaml
let gen_expr env = function
  | Sast.Expr(e, _) -> gen_expr e
  | Sast.Unop(op, e) -> sprintf "%s%s" (txt_of_op op) (gen_expr e)
```


Would it be better to return a cell, or struct here instead of multiple return variables?
Also should you commit the changes that use the 'model' return value to make a complete feature commit?


5321-GroundDomain_RDD (mmatts) - x86_64-MacOS-10.9-clang: OK (1957 of 1962 tests passed)

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


This technically changes what is being returned though. previously this would return an adjustment from create_adjustment, and now we're returning a boolean.


YAY!


lgtm


we shouldn't be sending boolean's through signals


looks good


Another #35 ... ;-)


nice! I have only just seen this, I will update main project the same way


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


U should not delete that!!!


So the bebop2_indi.xml file in the example directory line 1 needs to change
from:
<!DOCTYPE airframe SYSTEM <"../../airframe.dtd">
to:
<!DOCTYPE airframe SYSTEM "../airframe.dtd">


TeamCity LabKey :: Trunk :: LabkeyTrunk :: CDS postgres 9.4 [Build 9](https://teamcity.labkey.org/viewLog.html?buildId=286336&buildTypeId=LabkeyTrunk_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 19 (4 new), passed: 27 Build time: 01:02:06
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyScatterPlotColorAxis: <no details avaliable>

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

org.labkey.test.tests.CDSLoginTest.testLoginPage: <no details avaliable>

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

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

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

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

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

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

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

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

##### there are 9 more failed tests, see build details
```


Thanks for reviewing :)


the --home turned out not to be a setuptools version issue, but a bug in pip when using `-t`


>Nota pessoal: verificar no jogo


Remove log?


I guess line 537-540 should be replaced by "node_set_state(zone_to_nid(zone), N_HIGH_MEMORY); ..."
Commit. https://github.com/razrqcom-dev-team/android_kernel_motorola_msm8960dt-common/commit/446327d6f1763bbe7f9793cc8dae04fca82c9d48#diff-2b4dfdc5257c76af17f6fe51933aa15fR518


Will merge this. Thanks for the input.


Everything up to my last commit compiles without errors and the server starts. Just downloaded the repo at that point and checked. Some nasty conflict happened and after the merge some of the code is missing.


Hey guys,

For your first conwayCell test after Downing's tests - why do you have a frequency that is higher than the number of evolutions? Is that a mistake?


môže byť? .. mysleli ste nereklasifikovaný aspekt hej?


Please don't change the timezone. We need it to be UTC for S3 to work. I will find a way to deal with the timezone warning as soon as possible.


@kpearson I was able to get the tr method to work by taking the statement out of the block that started by checking for the AurgumentError. Thanks for your help last night.


This needs a better name


kok


could you pls teach me how to compile pocketmine master because iput in devtool and /makeserver it always said 1.4.1 even i set up 0.13.0


I think this change is causing issues for windows


This fails on the case that baseRange has a size-1 element


This has been taken care of. Thanks.


Definitely funny no test cases break here.

This removes a fair chunk of messaging we gave to clients that was (usually) right, doesn't it? Like the fact the coupon might be inelligible because a better one exists? I'm not sure I'm comfortable removing that.

Wait, how and when do coupons get applied? was the update_totals and persist_totals ever ran? It seems like this changes quite a bit of behaviour....


@IIvec I've checked and can exclude that... :-)


saw approval from bkerley
at https://github.com/basho/riak_kv/commit/2f2c9f45b966e0f638e92ed85534932d43416dc6


merging basho/riak_kv/bugfix/bch/fix-ql-quote-tests = 2f2c9f45 into borshop-integration-1273-bugfix/bch/fix-ql-quote-tests


basho/riak_kv/bugfix/bch/fix-ql-quote-tests = 2f2c9f45 merged ok, testing candidate = 4d8a4615


Also on your comment on using phusion-baseimage; it automatically takes care of cleaning up any child process spawned by the parent process and offers a clean way to exit when the container is stopped.


Functions start with a lowercase letter


pontos


perfektni, diky, zakomponuju to do textu.


Since this is cosmetic, not functional, I'm merging.

And yes, start a new pull request once I merge. (Though in principle you could have started it first and just updated by merging this one into your pull request once I merge it. It sounds complicated but it's actually simple.)


You could use
`padding: 20px 24px 24px`


Please take a look at #1014. I fixed the errors there.


This is unneeded when the former is followed.

Also, clients should NEVER trust data from anyone. This implies that a client can trust avatars to come in as square.


Criar uma nova conversa


Ok, thanks!


This commit isn't related to the bug fix, correct? Not sure why we haven't seen the error before. Probably better to create a separate pull request/ticket about it so you can squash the commits here.


@jcrist if you feel like making a starter contribution to `distributed`, this traceback could use some visibility when raising errors just below.


Entrar


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


fajn, nerobila som to, lebo vtedy to bola kapitola spojená s reklasifikáciou a tam obr. je, len je už reklasifikovaný .. ok čjus :)


Actually upon further reflection and trying to implement it it looks like it's going to be easier to do the first one. We just keep bubbling up the Sast.Expr as the root type, which stores the data type of the expression evaluated so far.


Found. 64 to 32 conversion of normalized data. It should be denormalized first.


If negative values were allowed for prices like they are for weight, the 'option_negative' field would be redundant.

Actually, negative price values ARE technically allowed, but not expected by CubeCart's logic, instead relying on the 'option_negative' field; if the field is checked but a negative price value is entered, the price is instead added.

This implementation behaves consistently with CubeCart's previous behavior.


"Conversa inteira" ou "Toda a conversa"


This code would probably be a lot cleaner if you used `java.net.URL` to parse and rebuild the URL.


@lucabrivio: OK, I thought it was maybe measured in kilonodes.


Jak przetestowałaś działanie tego rozwiązania?


too many `=` :)


Level


Please take a screenshot.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5954](https://teamcity.mesosphere.io/viewLog.html?buildId=78301&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:08
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity LabKey :: Trunk :: LabkeyTrunk :: Git postgres 9.4 [Build 800](https://teamcity.labkey.org/viewLog.html?buildId=286344&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 49 (3 new), passed: 244 Build time: 00:54:04
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.util.JUnitHeader: <no details avaliable>

org.labkey.test.util.JUnitFooter.afterJUnit: <no details avaliable>

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

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

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

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

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

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

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

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

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

##### there are 39 more failed tests, see build details
```


I can understand the aesthetic attraction of 'initialising' an object instance with JSON, but given the restriction this imposes around extensions; it's hard to see any practical advantage to init vs. a static fromJSON().  If there is one, I welcome enlightenment! :-)


Note: Mysql is now missing from the list of missing software below.


Closes issue #37.


So we have to explicitly enable SSL in the config, even if the Azkaban plugin is sending swebhdfs URLs?  Interesting.


Adhere to snake_case plz


Please do so, it's not necessary anymore.


>Nota pessoal: verificar no jogo


103643052-FiniteDifferenceFluxOutput (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1433 of 1433 tests passed)

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


import setTimeout and call as this.setTimeout


  Problem 1
    - The requested package knplabs/knp-snappy-bundle == 1.3.0.0 could not be found.
  Problem 2
    - Installation request for whyte624/sonata-admin-extra-export-bundle dev-master -> satisfiable by whyte624/sonata-admin-extra-export-bundle[dev-master].
    - whyte624/sonata-admin-extra-export-bundle dev-master requires sonata-project/admin-bundle ~2.4 -> no matching package found.


multiple backgrounds are saparated with `,` not `;`


I'm not so sure this is needed. Can leave it in for now but I think we'll want to just filter *all* shows by displayable as most public facing clients shouldn't have to concern themselves with this.


`write-timeout = "5s"` is less than `shard-writer-timeout = "10s"` just above, but we say that `shard-writer-timeout` should always be less than or equal to `write-timeout`. Do we have the default values wrong?


@dsyme is this change intentional?


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


No original esta apenas {memo X}Searching For : {#FFFF00}%s{/}. Então acho que é melhor deixar apenas "Procurando jogadores:" por enquanto


missing space


missed the 'm' on my commit message.


Clérigo


oh i thought the opposite, my b!


TeamCity LabKey :: LabkeyRelease15.3 :: CDS postgres 9.4 [Build 32](https://teamcity.labkey.org/viewLog.html?buildId=286338&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 15 (4 new), passed: 14 Build time: 00:54:13
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyAxisSelectors: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

##### there are 5 more failed tests, see build details
```


Rebuild_index should solve the problem. The updates the index settings hence it will close the index and apply the index settings and open the index.

@vied12/ @ioanpocol is it possible to deploy for liveblog without the slugline mapping.

````
 'slugline': {
        'type': 'string'
   }
````


"The hinted handoff directory. For best throughput, the HH directory and the WAL directory should be on different physical devices. If you have performance concerns, you will also want to make this setting different from the `dir` in the [[data]](../administration/config.html#data) section."


:muscle:


Como que eu


It's simpler to not have to transform existing API attributes, IMO, so stickin to the :snake:


If negative values were allowed for prices like they are for weight, the 'option_negative' field would be redundant.

Actually, negative price values ARE technically allowed, but not expected by CubeCart's logic, instead relying on the 'option_negative' field; if the field is checked but a negative price value is entered, the price is instead added.

This implementation behaves consistently with CubeCart's previous behavior, but I would suggest changing it to allow the store owner to enter whatever price they want (which they can) and simply performing addition - if the price is negative, it will work out as expected without the need for an extra 'option_negative' field.


vê


I don't understand the second sentence at all.


hooray


upstream changes


(I don't know if we can group a series of diffs on github, but here's the next one with the changes)

https://github.com/sboosali/MemoTrie/commit/b5aa3aeb903b7bfe132bb4dcde33f4b7f71c9367

I also added an executable, so we can check that the example builds.


Add:

"This will make it substantially more difficult to diagnose issues with your installation."


Do we need to take care of all the seeedsstudio warnings about stopmask ?


103643052-FiniteDifferenceFluxOutput (mjwitte) - x86_64-MacOS-10.9-clang: OK (1954 of 1963 tests passed)

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


perhaps "...to require authentication.", since once it's on it must be used for all requests.


"Jornal do aventureiro" ou "Jornal de aventura"? os dois parecem estranhos sinceramente... acho que o melhor talvez seja algo como "Diário de Aventura"
De qualquer forma seria: "Jornal do aventureiro atualizado"


Duplicated copyright. Pretty sure that's unintentional.


Forgot about including the changes in this commit. Fixed in https://github.com/aodn/imos-toolbox/commit/e401e4941bc1023c835fe0b2d22e19b657bcb115


Note that this will duplicate every write statement in the logs and is thus not recommended for general use.


"Menu de objetos para missões" ou "Menu de objetos para a missão", vou ter que procurar isso no jogo também


Don't start by trying to save your real asks and bids.

Start by trying to save one fake entry to your database. Hard code transaction and save that inside your silentSight model


`transaction` -> `transactions`


>Nota pessoal: verificar no jogo


Good job. I found it too.


The initial purpose of building `JSONCodable` was to provide encoding and decoding functionality for user defined types. That's not to say there's no merit in extending built-in/standard library objects but it's not a particular goal of project. There's also something that's inherently intuitive about using `init?()` - it's the regular way we create values/objects.

On the other extreme, there's https://github.com/matthewcheok/JSONCodable/pull/17 which suggest we should use `init() throws`. While I think it's an interesting idea to provide more context via `errorType`, it hasn't been thrown around nearly as often as `init?()`.

At the end of the day, I think it's more important to provide an API that people understand and expect than optimize for specific edge cases. Let me know what you think!


"...that are older than..."


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


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


103643052-FiniteDifferenceFluxOutput (mjwitte) - i386-Windows-7-VisualStudio-12: OK (1960 of 1969 tests passed)

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


Que se passe-t-il ?


Hm, I'm not sure. How would you then ensure that going to `/show/:id` on Force wouldn't show you a private or unpublished show?

I was intending on making the fetch and then doing a `next` if the show wasn't displayable.


Try starting with something along the lines of:

```
testBook = new silentSight{
  transactions: [
    new tableModel({
      type: 'bid',
      amount: 10,
      price: 100
    })
  ],
  timestamp: 12345
})
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 5957](https://teamcity.mesosphere.io/viewLog.html?buildId=78317&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 199 Build time: 00:13:21
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


[...] l'idée de ce qu'est une droite.


What if you use Kernel::System::CustomerUser::LDAP2 with the 2 as counter? Does it work too?


jmnmnn


Detalhes do Personagem: Tipo 1
>Nota pessoal: verificar no jogo


Detalhes do Personagem: Tipo 2
>Nota pessoal: verificar no jogo


:+1: thanks :)


[...] qu'est-ce que


That'd be nice thanks


Upper bound on the number of incremental queries generated within each `GROUP BY time()` interval. The actual number of generated queries can be lower, depending on the `GROUP BY time()` interval in the CQ and `compute-no-more-than` setting.


Where `tableModel` is the model you make from your `tableData` schema

Those could be more clearly named btw, but fine for now.

Good luck!!!


nope


You can do that way simpler:

self.colors = @[self.colors[1], self.colors[2], self.colors[3], self.colors[0]];

That rotates the colors by one. Then you can loop over the buttons and set the color on button.


Why don't we just change this to use the validator and if the smallImageName is null then throw an error? This boolean logic seems like it could be replaced.


Acredito que seja o nome do item que está sendo comprado..
>Nota pessoal: verificar no jogo


You don't need this protocol method.


You don't need this.


This acts kinds weird and broken and actually seems to get worse performance.


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


PR updated, removed types from the .empty(s)


Why are we throwing an exception just to catch it and then rethrow it? Is the catch necessary for any of the other code?


[...] de *ne* donner qu'un exemple.


Should that be 32 instead of 33? Otherwise, the condition at line 645 can never be true.


Ну как зачем? Ради женщины, конечно.

А ты протестировал, работает?


No stop mask is minor it is just cosmetic with silkscreen

On 19 November 2015 at 23:50, smillier <notifications@github.com> wrote:

> Do we need to take care of all the seeedsstudio warnings about stopmask ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/smillier/HydraOBD/commit/2547cb8ed06219c149cade930d68a7e469f389b9#commitcomment-14514177>
> .
>


Unsure, but the default PP from shipyard is probably 6E up from 5E and would need to be changed (pending verification) as well if this goes in.


Potentially fix the issue of stacked selectives
```javascript
  // $('#customer .typeahead').prop( "disabled", true );
  // $('#assembly .twitter-typeahead').empty();

engine.initialize();
    /*if ($('#assembly .twitter-typeahead').firstChild){
      $('#assembly .twitter-typeahead').removeChild($('#assembly .twitter-typeahead').firstChild);
    }*/
    /*if ($('#assembly .twitter-typeahead').length){
      $('#assembly .twitter-typeahead').remove();
      $('#assembly span').append('<input class="typeahead" type="text" name="assembly">');
    }*/
    $('#assembly .twitter-typeahead').empty().append('<input class="typeahead" type="text" name="assembly">');
    /*$('#customer .typeahead').typeahead('val', '');
    $('#assembly .typeahead').typeahead('val', '');*/
    // Instantiate the Typeahead UI
    $('#assembly .typeahead').typeahead(null, {
```


i have a few ideas to greatly increase efficiency; will implement them next week sometime if needed


Montrez un magasin de vélo à quelqu'un en lui disant que c'est un magasin. Il pensera alors que n'importe quel magasin vend forcément des vélos.


Did this work for you? If not you could also change the frame (multiply width and height)


This breaks on php 5.4.28 with error:

 "PHP Parse error:  syntax error, unexpected 'finally' (T_STRING), expecting catch (T_CATCH) in /vendor/illuminate/database/Eloquent/Relations/Relation.php on line 172".

The pre-commit version works.


>Nota pessoal: verificar no jogo


big fix. or bug fix


Didn't realize I had gotten rid of that method?


all tests pass:
success: http://buildbot.bos1/builders/test-riak_kv/builds/2767


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


Yep, I agree, actually. Will take the `try` out.


I mean this could happen in the partner_show's root resolve:

```
gravity(`show/${id}`).then((show) => {
  if (show.displayable) return show;
});
```

Which would then just return null if it's not displayable.

You might be right tho.


5321-GroundDomain_RDD (mmatts) - 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)


So is this meant to be an absolute orientation measurement?


Acho que fica melhor Vubbes Raivosos
>Nota pessoal: verificar no jogo


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


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


OK, you got me at the naming thing. That would make it more expressive.


because if so, you can just add another specialization of AbsoluteOrientationMeasurement (specialized for the orientation-only state).

If you're trying to use this for the gyro, then you want something like an AngularVelocityMeasurement


Ataque


can do `.tail<3>()` here now (same below, too), a wee bit more efficient


Dude, this is a 5 year old commit, with code ported directly from the Mono project. If this is a bug, and you want to submit a fix (with a test), it should probably be done upstream, to https://github.com/mono/mono/blob/f79731662f2ad3e90ecad6e90b8e7b50b919e452/mcs/class/System.Web/System.Web.Util/HttpEncoder.cs#L517 :smile:


Were the changes made here (validates_numericality_of) meant to still support an attr_accessor on an ActiveRecord model that has a numerical validation? I see a test for an ActiveModel and ActiveRecord driven classes but not specifically ActiveRecord with a validated attr_accessor (a non db backed column). This was supported on shoulda-matchers 2.x but fails now on 3.0 because when looking up `subject.class.columns_hash[].type` (the column_type private method) its nil since field isn't a db backed column, its a simple attr_accessor.


known bug it messes up when getting the same client twice


Custo de Reparo


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


Batches of CQs run at intervals determined by the `GROUP BY time()` interval divided by `compute-no-more-than` * `compute-runs-per-interval`. However, CQ batches will never run more often than the `compute-no-more-than` value. Note: `GROUP BY time()` * (`recompute-previous-n` + 1) must be greater than `compute-no-more-than` or some time intervals will never be sampled.


div names i think


@cyoilya Laravel 5.1 has minimum php version 5.5.9 - http://laravel.com/docs/5.1/releases#laravel-5.1


I get BLANK page when I open this in altium. Somebody have the same issue or is this an empty/broken  file ?

greets


The reason I did this was that in our custom app, we also had different taxation rules for business users - and all of a sudden I had to pass a boolean in there, and the signature changed. A possible way out might be passing in an address and a variant (because that's really the two things that determine the taxation of things).

Unfortunately, addresses do not yet know their zone - that bit happens in the order... But you know what: It should go to the address: A simple `after_save` hook will do, and every address has a nice, permanent, fast-to-lookup zone.


you will need to have this step in there, unless you're storing the quaternion as your state, in which case you need to re-linearize each time, your state dimension would be 7 instead of 6, etc.


А, это вообще мой коммит )


@erictune will change this soon and update the PR.


So should we make it a DataTypes.ENUM instead?


Aqui se refere a roupa da classe, acho que Traje fica melhor


Looks good to me, and it compiles on GHC 7.8.2. Please issue another pull request, and I'll merge it in and release a new version to Hackage.


#define BOOST_RESTRICTED_FUNCTION_L3     BOOST_RESTRICTED_FUNCTION_L2


I seem to have the same compile issue on X11 with gcc:
```
core/ustring.cpp: In member function 'String String::http_escape() const':
core/ustring.cpp:3099:35: error: '_snprintf' was not declared in this scope
    _snprintf(h_Val, 3, "%.2X", ord);
                                   ^
```


>Nota pessoal: verificar no jogo


Consumir ICoins
Já que ICoins é o cash do jogo acho que é melhor deixar com esta


All symbols end with '_CUR' (FX and CFD), with the only exception of XAU_XAG (Gold/Silver), where XAG (Silver) is used as the quote currency (and is 3 chars long as well).

The list of all Oanda symbols is [here](https://github.com/QuantConnect/Lean/blob/master/ToolBox/instruments_oanda.txt).


oh that's interesting, i didn't think of that. I do kinda like it.

Also really no rush to merge now that I'm getting deep in Force land using this, I'll keep this as-is for now and come back to it.


Whoops! Thanks for catching that! I must have forgotten to check that when I was writing my acceptance test generator. Thanks for catching that


Or not, actually I believe the compile issue is due to this commit.


Please don't just copy from somewhere else, there is only x86_64 in KaOS, so don't start adding 2 kinds of source & md5 lines, revert to how this was done (correctly) before.
see http://kaosx.us/kcp-guide/#Formatting_standards_for_KCP


you should catch exceptions that would be raised in here


Thanks. It's just something that popped out while running a static analyzer. I'll take it up with Mono then.


Because this element is in the ui hash, Instead of finding it again, you can reference this way: `this this.ui.editMove`.


This is for another case . . the commit message was for the wrong case.


fast-forwarding end-to-end/timeseries to borshop-integration-1273-bugfix/bch/fix-ql-quote-tests = 4d8a4615


Do we expect this to also work in future Collada versions? If so we could first check for 1.4, handle it as a special case and make the current 1.5 branch the default?


I am merging this suggestion and the other commit suggestion:

https://github.com/tmelliott/uoa-inzight-lite/commit/8b876ec86db57edfd84b238bfdd1fa3ed1b546f6

Although I am not sure why you intend to run update.package()

We have to catch up for a chat regarding this.


After this commit the compiler complains about the following resources: drawer_shadow and ic_drawer

Make sure you have not forgotten to add them in your last commit.


True dat bro


odlicno


You'll want to `.freeze` this. Strings are mutable, so an accidental `<<` can really hurt your day :smile:


if we used the validator, then we would be changing the flow of the logic ... i only removed the if check because i recognized that it was always true.

if you think it is appropriate you can put in the Validator check, but i didn't want to alter the flow of logic since the LPSs main concern is with the error messages


I did have to modify it a little bit but I can include the file which generated most of it if you like.


okay, very sorry. I didn't catch your previous comment (still learning, thanks to you so much !)
Fix on the way...


Hi Matthew, thanks for the considered response, and I do find your points persuasive.   The static method of initialization is a little more convenient in my current specific case but it's not worth forking the JSONCodable project for.  I'll remove my fork and reimplement my requirement using JSONTransformers then. Thanks for taking the time to reply.


I see where you are going with this, but I'm not sure about the implementation.

* Ideally is should use REST therefore be a `DELETE`. But a `DELETE` is already being used to turn off maintenance mode.
* You could just remove the session cookie from the client and it would have the same effect.


ok


we are catching and re-throwing because we want the specific type of exception. we do this in many places in the portal when we want to be specific when a more general exception is thrown.


I am not a big fan of return 0 if the right args aren't passed in. Maybe add the two tax_rate and tax_category as required keyword args? And in yours you can specify other keyword args, or we can still take options. But for an API for core I'd really rather we require them than quietly set it zero (which isn't tested anyway).


instead of saving `recentlySaved` to instance variable, you can reference it via `this.getOption('recentlySaved')`. Marionette automatically saves the the options passed into the View constructor and allows access to it via [getOption](http://marionettejs.com/docs/v2.4.3/marionette.view.html#viewgetoption).


as per previous comment, update this to `this.getOption('recentlySaved')`.


hy,

 I get allot of errors when i open it with eagle cad . Says that schematic and board are not consistent ???
Can you please tell us whats going on here ?

thank you

![erc](https://cloud.githubusercontent.com/assets/12972406/11287521/863fcd16-8f1c-11e5-9d12-36d681c2da02.jpg)


Could you skip this by not deleting the '/' in the previous line?


Proposed fix in #2841.


:+1: Sorry


Shouldn't the view work by default though? I think that's what the original test intended?


Maybe this was pointing to an incorrect directory?


This doesn't belong in this repository. It seems random.


Should these assert the result is equal to what's been inserted as a sanity check? These could be silently returning nothing.


No, thank you. Your book was what got me into Flask in the first place.


# Fixed the function name
# idk about the map tho, since map was introduced on Erlang R17 (which was released pretty recent), not all the clients supports it


Please write "elementary OS" with a lower case "e" as per the brand guidelines.


should be fixed now


version will be updated during release process only...please revert to 0.6.10


here is my code so far

<!doctype html>

<meta charset="UTF-8">
<title>Untitled Document</title>

<button onClick="displayStuff()">Attack!</button>

Health


Done, also changed it to 'under_score'


done


So specifying the view explicitly means that something else, somewhere else isn't working properly. Maybe the `app.js` views setup is incorrect, maybe the default settings are not working properly?


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


I have no idea about why they did this. But all the function names should be in 'under_score' format. https://github.com/inaka/erlang_guidelines#camelcase-over-under_score
I've changed all the camelCase functions to under_score in the latest commit. Since they were all internal functions, shouldn't have any impact on existing users.


LGTM!

@matt-deboer you ROCK!!!!

Terraform gurus, can we have some pull love and get a few of these accepted?

@phinze / @jen20 when is the next release?


I think it needs to be here if we want most middleware to have names.


In this case, the Flag only affects one line of code, I don't want to copy rest parts twice just to make 2 functions.


ya


I just committed a new version, let me know if it looks better.


No


Nit: this should be false (i.e. read-only).


I have been using the standalone illuminate/database library for a while with php 5.4.  This update broke all the relations.  Thoughts?


Nor this one


Oh, great. I really appreciate your contribution. Especially in terms of rust *"best practices"* as this is my first serious rust project.

I had also thought about using a more object-oriented style, but there's a problem with your changes. Modbus is defined for three transport encodings: `TCP`, `RTU` (binary-serial) and `ASCII` (character-serial). It does not only differ on the Transport stream, but also in the encoding. E.g. `RTU` is adding some *CRC*, `ASCII` some *LRC* checksum to detect transmission errors, which `TCP` doesn't need, as the transport security is assured by *TCP* on a lower level.

My idea would be to use a `Modbus` trait and implement it for the transports, perhaps sharing some inner encoding functionality, extended by the transport security functionality of every implementation.

Implementing the serial protocols it also a bit anachronistic, afaik. the TCP transport it the most common.


TeamCity pull requests :: netty [Build 691](https://garage.netty.io/teamcity/viewLog.html?buildId=3382&buildTypeId=pulls_netty&guest=1) is now running


TeamCity pull requests :: netty [Build 692](https://garage.netty.io/teamcity/viewLog.html?buildId=3383&buildTypeId=pulls_netty&guest=1) is now running


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


Nit: make this `false` (i.e. verified as read-only).


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


@meandavejustice This works for me, with a few hiccups:
in `close()` can you make sure that the event target isn't the actual settings div before toggling classes?
Also in `_settings.scss`:
- nuke line 86:     `line-height: 2.6rem;`
- after line 70 add these two lines:
```
display: block;
line-height: 2.6rem;
```


OK, I've found an existing unit test, which covers this scenario -  https://github.com/Microsoft/ApplicationInsights-JS/blob/master/JavaScript/JavaScriptSDK.Tests/CheckinTests/appInsights.tests.ts#L248

I would only change it and assign unique values to each field (like 101, 102, 103... instead of only using 101) to verify that the mapping is correct. Thanks!


Good point–fixed locally now, thanks!


IIRC this return value is used for calculation somewhere else.

Read this more like:

The included tax amount is zero unless you pass in tax category and a zone.
IMO this is totally fine here to return zero instead of blowing things up.

Correct me if I'm wrong @mamhoff


R+ once that stuff gets cleaned up. @pdehaan, if you have no other objections, feel free to merge once these nits get sorted.


@cyoilya hmm I can understand that that is frustrating, however as the rest of Laravel is 5.5.9+ dependent it means that the travis ci test runners can't be run against 5.4. This will mean that while this particular feature could be made 5.4 compatible, there is no way of catching the next feature that isn't 5.4 compatible.

Please raise a ticket on https://github.com/laravel/framework, referencing this discussion as I'm not really in a position to make a call on it.


Ah, OK, then this WIP should be scrapped and re-thought. You'd be surprised about RS232, though; if my last job is any sign, it's still not uncommon.


First commit


5321-GroundDomain_RDD (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1963 of 1968 tests passed)

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


I think what we have currently is more consistent with the overall tree, and would simplify things in the long run. More complicated expressions overall should be avoided. But ultimately I am up for discussion, and this is just a gut feeling too.


> catch (NotSupportedException) { }

Console code on windows also has a similar pattern where we catch NotSupportedException and then default to UTF8. The reason the pattern exists there is because not all encoding are supported by default and require explicit registration through CodePagesEncodingProvider. I am not sure if the same scenario is applicable on Unix as well, so wanted to double check.


:100: for testing this


`proto` is prototype :P


This seems to overwrite the default field value with the original list for the field. When I try to upload Solr gets sent things like

```json
  description: [{"@language": "de", "@value": "..."}, {"@language": "en", "@value": "..."}, ...]
```

Which makes it freak out.


@sethvargo are you interested to help me to get this one into 1.8 as well?


Concurrency refers to managing multiple tasks at a time either by interleaving  or by parallelism(running more than one process at the same time), the latter is usually implemented with multiple cores or processors.
Concurrency could affect latency in that processes have to wait till they can be handled(in the case of a computer, till the CPU is freed up), this will increase the latency as it will take longer time to process requests.
Concurrency could also reduce latency if a unit of work is subdivided into different parts and executed concurrently then it will take shorter time to execute such a request. However, in reality there needs to be tradeoff between this two, if the application requires real time response then we need to ensure the latency is a its minimum, whether the request is executed concurrently or not. on the other hand, if the request does not require a real time response then we could reduce latency of a single request by combining requests and executing them concurrently


Missing another <> in "new HashSet()."
new HashSet<>()


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


Deleting events causes JVM crash in Finalizer.
Must be wrapped in #ifndef USE_JNI


You had a duplicate README in both the root directory and src directory


Five should not be capitalized. By convention you capitalize objects who's constructor you will invoke. Particle is capitalized because we invoke it's constructor. We use five to get to the Board object's constructor.

``` javascript
var board = new five.Board({
   io: new Particle({
     token: token,
     deviceId: deviceId
  })
});
```

The same is true for the device object - we are invoking the Message constructor, not the Device constructor.

``` javascript
var message = new device.Message(payload);
```


I think this should work now, at least for the example you provided (see below).


5321-GroundDomain_RDD (mmatts) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (894 of 894 tests passed)

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


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


MArray_Elim (DeadParrot) - x86_64-MacOS-10.9-clang: OK (1969 of 1978 tests passed)

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


A kitten died 🐱


Sorry I read closer. Is your removal code always active? I can take a look
at it
On Nov 19, 2015 1:22 PM, "Adam Domurad" <domuradical@gmail.com> wrote:

> I think by far the most likely explanation is that the state is not
> reloaded correctly, no?
> On Nov 19, 2015 12:55 PM, "Isaac Tamblyn" <notifications@github.com>
> wrote:
>
>> Oh good :)
>>
>> - Isaac
>>
>> On Thu, Nov 19, 2015 at 12:50 PM, Kevin Ryczko <notifications@github.com>
>> wrote:
>>
>> > This all has to do with following/followers. Something is happening with
>> > the debug check after resubmission. If something changes, then I have to
>> > unfollow for every user to adjust the follower list based on the new
>> input
>> > file. This is where the problem is occurring. So it's either there is a
>> > problem with the functions before the debug check is called or the
>> follow
>> > before the program exits is not completed properly.
>> >
>> > There are possibly different things we need to look at.
>> >
>> > —
>> > Reply to this email directly or view it on GitHub
>> > <
>> https://github.com/hashkat/hashkat/commit/28674de8bad505fc8c73d97ff1d14e939532c4ed#commitcomment-14507375
>> >
>> > .
>> >
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/hashkat/hashkat/commit/28674de8bad505fc8c73d97ff1d14e939532c4ed#commitcomment-14507477>
>> .
>>
>


TeamCity LabKey :: LabkeyRelease15.3 :: CDS postgres 9.4 [Build 33](https://teamcity.labkey.org/viewLog.html?buildId=286361&buildTypeId=LabkeyRelease153_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 21 (7 new), passed: 27 Build time: 01:12:55
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyAntigenScatterPlot: <no details avaliable>

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

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

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

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

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

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

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

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

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

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

##### there are 11 more failed tests, see build details
```


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


Ok, I have 2 questions then:

1) What's the latest minor (or major) release just prior to this change?
2) Is there a way to avoid calling the offending code altogether?

I can't move to 5.5 yet but love the Illuminate database library, so would like to stick with a version that works.

Thanks.


TeamCity pull requests :: netty [Build 691](https://garage.netty.io/teamcity/viewLog.html?buildId=3382&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5298, ignored: 21 Build time: 00:15:02


TeamCity pull requests :: netty [Build 693](https://garage.netty.io/teamcity/viewLog.html?buildId=3384&buildTypeId=pulls_netty&guest=1) is now running


Error in the BPM, discovered by @rkreich  to be caused by non-serializableness of the KalturaParams. the JSONObject is not serializable itself


This is looking really promising - can't wait to see this working. Thanks @aliceranzhou!


Do you want add this back to SMW-core? Would this pass our postgres Travis-CI?


test for this change?


nit: since we're screwing with them anyway, of all of these can go in one `var ( )` statement. but your call


At first I forgot that  `oncontextmenu` existed, although thinking back I remember trying to protect my websites by putting an alert in if a user tried to right click. :)


@ragesoss Definitely going to need your eyes on this.


Yes, and I added that in a later commit.

Sorry.  I didn't go back and try to clean up the sequence of commits, so it still reflects how I iterated on a few things.


Glad I could help! :smile:


( ˘ ³˘)♥


Thanks to https://github.com/JimBacon for comments here: https://github.com/openlayers/openlayers/issues/1450#issuecomment-146207698


@cyoilya latest minor release without this fix https://github.com/illuminate/database/blob/v5.1.16/Eloquent/Relations/Relation.php (note that this change is actually a bugfix, not a style change, so you might encounter the bug that it fixes).

There isn't an easy way I can think of to override the `noConstraints` method. You could create your own fork of https://github.com/illuminate/database and use that with the following 5.4 compatible change:

```
// When resetting the relation where clause, we want to shift the first element
        // off of the bindings, leaving only the constraints that the developers put
        // as "extra" on the relationships, and not original relation constraints.
        try {
            $results = call_user_func($callback);
        } catch(\Exception $e) {
            static::$constraints = $previous;
            throw $e;
        }

        static::$constraints = $previous;

        return $results;
```


Cool, I do pass all seeedstudio DR, so let's take care of the silk screen later,


:+1: here.


Rien de spéciale un peu de nettoyage du code sass, et j'ai modifié la manière de positionner le cercle status.
Au lieu de décaler le cercle avec `margin` je le fais directement avec `top` et `left`.
C'est plus pertinent et ça utilise moin de code.


```js
/* global Image */
```
http://eslint.org/docs/user-guide/configuring.html#specifying-globals


[![Jonny Mae](http://api.artsmia.org/images/115829/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=115829)


[![The Crossroads of the Eagleâs Nest, Fontainebleau Forest](http://api.artsmia.org/images/4191/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=4191)


[![High chest of drawers](http://api.artsmia.org/images/6379/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=6379)


[![Lidded punch bowl, from a set](http://api.artsmia.org/images/8522/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=8522)


[![Punch goblet](http://api.artsmia.org/images/10398/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10398)


[![Punch goblet](http://api.artsmia.org/images/10399/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10399)


[![Punch goblet](http://api.artsmia.org/images/10400/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10400)


[![Punch goblet](http://api.artsmia.org/images/10401/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10401)


[![Punch goblet](http://api.artsmia.org/images/10402/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10402)


[![Punch goblet](http://api.artsmia.org/images/10403/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10403)


[![Punch goblet](http://api.artsmia.org/images/10404/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10404)


[![Punch goblet](http://api.artsmia.org/images/10405/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10405)


[![Punch goblet](http://api.artsmia.org/images/10406/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10406)


[![Punch goblet](http://api.artsmia.org/images/10407/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10407)


[![Punch goblet](http://api.artsmia.org/images/10408/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10408)


[![Punch goblet](http://api.artsmia.org/images/10409/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10409)


[![Baby Jesus, from Nativity Scene ( 81 pieces)](http://api.artsmia.org/images/28512/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=28512)


[![Mary, from Nativity Scene](http://api.artsmia.org/images/84351/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84351)


[![Joseph, from Nativity Scene](http://api.artsmia.org/images/84352/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84352)


[![Kneeling shepherd boy, from Nativity Scene](http://api.artsmia.org/images/84353/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84353)


[![Kneeling shepherd, from Nativity Scene](http://api.artsmia.org/images/84354/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84354)


[![Shepherd with striped sash, from Nativity Scene](http://api.artsmia.org/images/84355/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84355)


[![Shepherd with plain sash, from Nativity Scene](http://api.artsmia.org/images/84356/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84356)


[![Shepherd in green robe with blue sash, from Nativity Scene](http://api.artsmia.org/images/84357/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84357)


[![Shepherd in brown robe, from Nativity Scene](http://api.artsmia.org/images/84358/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84358)


[![Shepherd in green robe with red undergarments, from Nativity Scene](http://api.artsmia.org/images/84359/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84359)


[![Ox, from Nativity Scene](http://api.artsmia.org/images/84360/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84360)


[![Mule, from Nativity Scene](http://api.artsmia.org/images/84361/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84361)


[![Angel with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84362/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84362)


[![Angel with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84363/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84363)


[![Angel with yellow cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84364/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84364)


[![Angel with yellow cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84365/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84365)


[![Angel holding sign, from Nativity Scene](http://api.artsmia.org/images/84366/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84366)


[![Angel (hook in back for manger), from Nativity Scene](http://api.artsmia.org/images/84367/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84367)


[![Angel in gilt tondo, from Nativity Scene](http://api.artsmia.org/images/84368/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84368)


[![Woman in green robe with water jug, from Nativity Scene](http://api.artsmia.org/images/84369/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84369)


[![Small man in blue and white striped robe, from Nativity Scene](http://api.artsmia.org/images/84370/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84370)


[![Small man in blue robe with red hat, from Nativity Scene](http://api.artsmia.org/images/84371/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84371)


[![Woman in purple robe and brown dress, from Nativity Scene](http://api.artsmia.org/images/84372/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84372)


[![Man in blue robe with red sash and boots, from Nativity Scene](http://api.artsmia.org/images/84373/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84373)


[![Woman in plaid skirt with yellow cape, from Nativity Scene](http://api.artsmia.org/images/84374/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84374)


[![Man in blue robe with black and white trim, from Nativity Scene](http://api.artsmia.org/images/84375/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84375)


[![Man in red shirt, blue hat and green cape with gold trim, from Nativity Scene](http://api.artsmia.org/images/84376/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84376)


[![Man in red shirt and blue cape with staff, from Nativity Scene](http://api.artsmia.org/images/84377/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84377)


[![Woman in red dress with green cape, from Nativity Scene](http://api.artsmia.org/images/84378/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84378)


[![Woman in olive dress, red cape and lace veil, from Nativity Scene](http://api.artsmia.org/images/84379/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84379)


[![Maji attendant in red with staff, from Nativity Scene](http://api.artsmia.org/images/84380/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84380)


[![Maji attendant in red, from Nativity Scene](http://api.artsmia.org/images/84381/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84381)


[![Maji attendant in light green, from Nativity Scene](http://api.artsmia.org/images/84382/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84382)


[![Maji attendant in light green with staff, from Nativity Scene](http://api.artsmia.org/images/84383/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84383)


[![Maji attendant in light green with plate of offerings, from Nativity Scene](http://api.artsmia.org/images/84384/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84384)


[![Moorish Maji attendant, green with pink cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84385/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84385)


[![Moorish Maji attendant, green with pink cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84386/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84386)


[![Moorish Maji attendant, pink with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84387/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84387)


[![Moorish Maji attendant, pink with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84388/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84388)


[![Arabian Stallion, from Nativity Scene](http://api.artsmia.org/images/84389/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84389)


[![Maji with white beard and pendant gift, from Nativity Scene](http://api.artsmia.org/images/84390/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84390)


[![Maji with staff, from Nativity Scene](http://api.artsmia.org/images/84391/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84391)


[![Maji with ball of myrrh, from Nativity Scene](http://api.artsmia.org/images/84392/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84392)


[![Moorish Maji, from Nativity Scene](http://api.artsmia.org/images/84393/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84393)


[![Standing Cardinal with staff, from Nativity Scene](http://api.artsmia.org/images/84394/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84394)


[![Seated Cardinal with open book, from Nativity Scene](http://api.artsmia.org/images/84395/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84395)


[![Seated Cardinal with closed book, from Nativity Scene](http://api.artsmia.org/images/84396/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84396)


[![Fence with three ducks, from Nativity Scene](http://api.artsmia.org/images/84397/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84397)


[![Pile of hats, staffs and instruments, from Nativity Scene](http://api.artsmia.org/images/84398/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84398)


[![Flowering plant in pot, from Nativity Scene](http://api.artsmia.org/images/84399/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84399)


[![Two stools with book on seats, from Nativity Scene](http://api.artsmia.org/images/84400/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84400)


[![Two chests and four spears, from Nativity Scene](http://api.artsmia.org/images/84401/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84401)


[![Table with candlestick, from Nativity Scene](http://api.artsmia.org/images/84402/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84402)


[![Three-leg stool, long handled cooking pan, fish on a plate, from Nativity Scene](http://api.artsmia.org/images/84403/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84403)


[![Two axes and a two-handled saw leaning on a bench, from Nativity Scene](http://api.artsmia.org/images/84404/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84404)


[![Two religious staffs resting on a chest, from Nativity Scene](http://api.artsmia.org/images/84405/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84405)


[![Large woodpile with a fire on top, from Nativity Scene](http://api.artsmia.org/images/84406/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84406)


[![Small woodpile with a fire on top, from Nativity Scene](http://api.artsmia.org/images/84407/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84407)


[![Long-handled net, from Nativity Scene](http://api.artsmia.org/images/84408/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84408)


[![Dog, from Nativity Scene](http://api.artsmia.org/images/84410/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84410)


[![Falcon, from Nativity Scene](http://api.artsmia.org/images/84411/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84411)


[![Holy Spirit (dove), from Nativity Scene](http://api.artsmia.org/images/84412/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84412)


[![Column with sphere finial, from Nativity Scene](http://api.artsmia.org/images/84414/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84414)


[![Camel with riding Maji attendant, from Nativity Scene](http://api.artsmia.org/images/84419/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84419)


[![Camel with saddlebags, from Nativity Scene](http://api.artsmia.org/images/84420/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84420)


[![Elephant with riding Maji attendant, from Nativity Scene](http://api.artsmia.org/images/84421/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84421)


[![Green corner of a building, from Nativity Scene](http://api.artsmia.org/images/84425/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84425)


[![The Inn, from Nativity Scene](http://api.artsmia.org/images/84426/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84426)


[![Well with hanging bucket, from Nativity Scene](http://api.artsmia.org/images/84428/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84428)


[![Backdrop with 19 wedge-shaped support pieces, from Nativity Scene](http://api.artsmia.org/images/84430/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84430)


[![Flock of 22 sheep, from Nativity Scene](http://api.artsmia.org/images/84431/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84431)


[![Section of a building with three arched windows, from Nativity Scene](http://api.artsmia.org/images/84427/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84427)


[![Palm tree with base, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84432/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84432)


[![Palm tree with base, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84433/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84433)


[![Seven bales of hay, from Nativity Scene](http://api.artsmia.org/images/84435/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84435)


[![Roman ruin of a manger, from Nativity Scene](http://api.artsmia.org/images/84434/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84434)


[![Blue brick building with ochre second story, from Nativity Scene](http://api.artsmia.org/images/84436/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84436)


[![Yellow ochre building with gabled roof, from Nativity Scene](http://api.artsmia.org/images/84438/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84438)


[![Pink brick building with arched roof, from Nativity Scene](http://api.artsmia.org/images/84437/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84437)


[![The Dunes at Camiers](http://api.artsmia.org/images/3531/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=3531)


[![Brooklyn Bridge](http://api.artsmia.org/images/121860/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=121860)


[![Hexagonal fountain, from Nativity Scene](http://api.artsmia.org/images/84439/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84439)


[![Landscape near CrÃ©mieu](http://api.artsmia.org/images/2624/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=2624)


[![The Crossroads of the Eagleâs Nest, Fontainebleau Forest](http://api.artsmia.org/images/4191/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=4191)


[![High chest of drawers](http://api.artsmia.org/images/6379/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=6379)


[![Lidded punch bowl, from a set](http://api.artsmia.org/images/8522/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=8522)


[![Punch goblet](http://api.artsmia.org/images/10398/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10398)


[![Punch goblet](http://api.artsmia.org/images/10399/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10399)


[![Punch goblet](http://api.artsmia.org/images/10400/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10400)


[![Punch goblet](http://api.artsmia.org/images/10401/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10401)


[![Punch goblet](http://api.artsmia.org/images/10402/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10402)


[![Punch goblet](http://api.artsmia.org/images/10403/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10403)


[![Punch goblet](http://api.artsmia.org/images/10404/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10404)


[![Punch goblet](http://api.artsmia.org/images/10405/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10405)


[![Punch goblet](http://api.artsmia.org/images/10406/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10406)


[![Punch goblet](http://api.artsmia.org/images/10407/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10407)


[![Punch goblet](http://api.artsmia.org/images/10408/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10408)


[![Punch goblet](http://api.artsmia.org/images/10409/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=10409)


[![Baby Jesus, from Nativity Scene ( 81 pieces)](http://api.artsmia.org/images/28512/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=28512)


[![Mary, from Nativity Scene](http://api.artsmia.org/images/84351/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84351)


[![Joseph, from Nativity Scene](http://api.artsmia.org/images/84352/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84352)


[![Kneeling shepherd boy, from Nativity Scene](http://api.artsmia.org/images/84353/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84353)


[![Kneeling shepherd, from Nativity Scene](http://api.artsmia.org/images/84354/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84354)


[![Shepherd with striped sash, from Nativity Scene](http://api.artsmia.org/images/84355/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84355)


[![Shepherd with plain sash, from Nativity Scene](http://api.artsmia.org/images/84356/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84356)


[![Shepherd in green robe with blue sash, from Nativity Scene](http://api.artsmia.org/images/84357/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84357)


[![Shepherd in brown robe, from Nativity Scene](http://api.artsmia.org/images/84358/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84358)


[![Shepherd in green robe with red undergarments, from Nativity Scene](http://api.artsmia.org/images/84359/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84359)


[![Ox, from Nativity Scene](http://api.artsmia.org/images/84360/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84360)


[![Mule, from Nativity Scene](http://api.artsmia.org/images/84361/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84361)


[![Angel with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84362/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84362)


[![Angel with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84363/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84363)


[![Angel with yellow cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84364/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84364)


[![Angel with yellow cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84365/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84365)


[![Angel holding sign, from Nativity Scene](http://api.artsmia.org/images/84366/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84366)


[![Angel (hook in back for manger), from Nativity Scene](http://api.artsmia.org/images/84367/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84367)


[![Angel in gilt tondo, from Nativity Scene](http://api.artsmia.org/images/84368/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84368)


[![Woman in green robe with water jug, from Nativity Scene](http://api.artsmia.org/images/84369/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84369)


[![Small man in blue and white striped robe, from Nativity Scene](http://api.artsmia.org/images/84370/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84370)


[![Small man in blue robe with red hat, from Nativity Scene](http://api.artsmia.org/images/84371/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84371)


[![Woman in purple robe and brown dress, from Nativity Scene](http://api.artsmia.org/images/84372/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84372)


[![Man in blue robe with red sash and boots, from Nativity Scene](http://api.artsmia.org/images/84373/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84373)


[![Woman in plaid skirt with yellow cape, from Nativity Scene](http://api.artsmia.org/images/84374/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84374)


[![Man in blue robe with black and white trim, from Nativity Scene](http://api.artsmia.org/images/84375/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84375)


[![Man in red shirt, blue hat and green cape with gold trim, from Nativity Scene](http://api.artsmia.org/images/84376/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84376)


[![Man in red shirt and blue cape with staff, from Nativity Scene](http://api.artsmia.org/images/84377/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84377)


[![Woman in red dress with green cape, from Nativity Scene](http://api.artsmia.org/images/84378/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84378)


[![Woman in olive dress, red cape and lace veil, from Nativity Scene](http://api.artsmia.org/images/84379/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84379)


[![Maji attendant in red with staff, from Nativity Scene](http://api.artsmia.org/images/84380/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84380)


[![Maji attendant in red, from Nativity Scene](http://api.artsmia.org/images/84381/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84381)


[![Maji attendant in light green, from Nativity Scene](http://api.artsmia.org/images/84382/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84382)


[![Maji attendant in light green with staff, from Nativity Scene](http://api.artsmia.org/images/84383/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84383)


[![Maji attendant in light green with plate of offerings, from Nativity Scene](http://api.artsmia.org/images/84384/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84384)


[![Moorish Maji attendant, green with pink cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84385/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84385)


[![Moorish Maji attendant, green with pink cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84386/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84386)


[![Moorish Maji attendant, pink with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84387/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84387)


[![Moorish Maji attendant, pink with blue cape, one of a pair, from Nativity Scene](http://api.artsmia.org/images/84388/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84388)


[![Arabian Stallion, from Nativity Scene](http://api.artsmia.org/images/84389/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84389)


[![Maji with white beard and pendant gift, from Nativity Scene](http://api.artsmia.org/images/84390/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84390)


[![Maji with staff, from Nativity Scene](http://api.artsmia.org/images/84391/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84391)


[![Maji with ball of myrrh, from Nativity Scene](http://api.artsmia.org/images/84392/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84392)


[![Moorish Maji, from Nativity Scene](http://api.artsmia.org/images/84393/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84393)


[![Standing Cardinal with staff, from Nativity Scene](http://api.artsmia.org/images/84394/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84394)


[![Seated Cardinal with open book, from Nativity Scene](http://api.artsmia.org/images/84395/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84395)


[![Seated Cardinal with closed book, from Nativity Scene](http://api.artsmia.org/images/84396/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84396)


[![Fence with three ducks, from Nativity Scene](http://api.artsmia.org/images/84397/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84397)


[![Pile of hats, staffs and instruments, from Nativity Scene](http://api.artsmia.org/images/84398/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84398)


[![Flowering plant in pot, from Nativity Scene](http://api.artsmia.org/images/84399/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84399)


[![Two stools with book on seats, from Nativity Scene](http://api.artsmia.org/images/84400/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84400)


[![Two chests and four spears, from Nativity Scene](http://api.artsmia.org/images/84401/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84401)


[![Table with candlestick, from Nativity Scene](http://api.artsmia.org/images/84402/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84402)


[![Three-leg stool, long handled cooking pan, fish on a plate, from Nativity Scene](http://api.artsmia.org/images/84403/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84403)


[![Two axes and a two-handled saw leaning on a bench, from Nativity Scene](http://api.artsmia.org/images/84404/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84404)


[![Two religious staffs resting on a chest, from Nativity Scene](http://api.artsmia.org/images/84405/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84405)


[![Large woodpile with a fire on top, from Nativity Scene](http://api.artsmia.org/images/84406/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84406)


[![Small woodpile with a fire on top, from Nativity Scene](http://api.artsmia.org/images/84407/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84407)


[![Long-handled net, from Nativity Scene](http://api.artsmia.org/images/84408/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84408)


[![Dog, from Nativity Scene](http://api.artsmia.org/images/84410/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84410)


[![Falcon, from Nativity Scene](http://api.artsmia.org/images/84411/300/small.jpg)](http://collections.artsmia.org/?page=simple&id=84411)


As it stands, I think this would not index categories — no?