headers
Jason Smith | 1 Mar 2012 01:27
Picon
Favicon
Gravatar

Experiments with Git

Hi, all.

I hope you will pardon my commits to the repository. My plan is to try
to stumble upon some useful custom or workflow. Please let me know if
you have feedback or views.

Piggybacking off of Randall's idea, I have made a branch for every
JIRA ticket that I am interested or involved in. I would personally
like to see more branching and merging in the repo--to see it look
less like a Subversion timeline.

Once 1.2 is out, I also intend to push some feature branches, with no
intention for short-term merging, just to get them out there in the
open. I hope Benoit might push up some refuge  work, or others can
exercise their branches similarly.
Permalink | Reply | 3 comments |
headers
Jason Smith | 1 Mar 2012 01:38
Picon
Favicon
Gravatar

Re: [9/9] git commit: Testing requested_path for various combinations of rewrites and vhost

On Thu, Mar 1, 2012 at 3:17 AM, Randall Leeds
<randall.leeds@...> wrote:
> I made a change to requested_path recently on master and 1.2 but
> didn't get much feedback about it.
> It seemed like it was obviously broken to me but maybe I misunderstood
> the intention.
> Is it working the way you expect?
>
> Relevant commit: 879a1bc19b145e126b9386aed2023f9cd1df8b31

The JIRA ticket indicates a bug when "hostname/path" was used as a
vhost. Ryan showed that the "/path" part is forgotten by the time
req.requested_path arrives in a _show function.

Jan said it's not a bug because paths in vhost keys are invalid. Or at
least, they *oughtn't* be valid. I thought the bug occurred even with
normal vhosts (no path) but several unit tests later, I realized that
is false. The only bug is when vhosts include a path component.

And so the *real* bug will probably be that CouchDB should reject non
well-formed vhost keys. The only remaining question is whether Ryan
used that feature because there was no possible alternative.
Permalink | Reply | 0 comments |
headers
Filipe Manana (Commented) (JIRA | 1 Mar 2012 05:37
Picon
Favicon

[jira] [Commented] (COUCHDB-1426) error while building with 2 spidermonkey installed


    [
https://issues.apache.org/jira/browse/COUCHDB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219793#comment-13219793
] 

Filipe Manana commented on COUCHDB-1426:
----------------------------------------

Neither current master with or without this patch works for me.
I have spidermonkey 1.8.0 installed via homebrew and built my own spidermonkey 1.8.5 from source. If I try
to use the later compilation fails:

Running configure like:

$ ./configure  --with-js-include=/Users/fdmanana/sm185/install/include  --with-js-lib=/Users/fdmanana/sm185/install/lib

My spidermonkey 1.8.5's tree:

http://friendpaste.com/2UVvchXGJKGDv2tIzKKgMR

fdmanana 20:35:42 ~/sm185 > pwd
/Users/fdmanana/sm185
fdmanana 20:35:43 ~/sm185 > ./js-1.8.5/js/src/js --version
JavaScript-C 1.8.5 2011-03-31

And 'make dev' errors with the patch:

http://friendpaste.com/6pd556mxhZPRgrVegIV4pH

Without the patch:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Benoit Chesneau (Updated) (JIRA | 1 Mar 2012 06:00
Picon
Favicon

[jira] [Updated] (COUCHDB-1426) error while building with 2 spidermonkey installed


     [
https://issues.apache.org/jira/browse/COUCHDB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Chesneau updated COUCHDB-1426:
-------------------------------------

    Attachment: 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch

 <at> filipe I forgot the case where in clude are in include/js (or mozjs). This new itteration should fix it. 

> error while building with 2 spidermonkey installed
> --------------------------------------------------
>
>                 Key: COUCHDB-1426
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1426
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 1.1.1, 1.2
>            Reporter: Benoit Chesneau
>            Priority: Blocker
>         Attachments: 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch, 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch
>
>
> Context:
> To bench the differences between different versions of couchdb I had to test against spidermonkey 1.7 and
1.8.5 . 1.8.5 is installed globally in /usr/local  while the 1.7 version is installed on a temporary path. 
> Problem:
> Using --witth-js-include & --with-js-lib configure options aren't enough to use the 1.7 version it
(Continue reading)

Permalink | Reply | 0 comments |
headers
Benoit Chesneau (Updated) (JIRA | 1 Mar 2012 06:02
Picon
Favicon

[jira] [Updated] (COUCHDB-1426) error while building with 2 spidermonkey installed


     [
https://issues.apache.org/jira/browse/COUCHDB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Chesneau updated COUCHDB-1426:
-------------------------------------

    Attachment: 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch

patch without this spurious print.

> error while building with 2 spidermonkey installed
> --------------------------------------------------
>
>                 Key: COUCHDB-1426
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1426
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 1.1.1, 1.2
>            Reporter: Benoit Chesneau
>            Priority: Blocker
>         Attachments: 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch,
0001-fix-build-with-custom-path-close-COUCHDB-1426.patch, 0001-fix-build-with-custom-path-close-COUCHDB-1426.patch
>
>
> Context:
> To bench the differences between different versions of couchdb I had to test against spidermonkey 1.7 and
1.8.5 . 1.8.5 is installed globally in /usr/local  while the 1.7 version is installed on a temporary path. 
> Problem:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Benoit Chesneau | 1 Mar 2012 08:39
Picon
Gravatar

Re: Experiments with Git

On Thu, Mar 1, 2012 at 1:27 AM, Jason Smith <jhs@...> wrote:
> Hi, all.
>
> I hope you will pardon my commits to the repository. My plan is to try
> to stumble upon some useful custom or workflow. Please let me know if
> you have feedback or views.
>
> Piggybacking off of Randall's idea, I have made a branch for every
> JIRA ticket that I am interested or involved in. I would personally
> like to see more branching and merging in the repo--to see it look
> less like a Subversion timeline.
>
> Once 1.2 is out, I also intend to push some feature branches, with no
> intention for short-term merging, just to get them out there in the
> open. I hope Benoit might push up some refuge  work, or others can
> exercise their branches similarly.

I think it's OK to have feature branches,  I expect either  changes
from bigcouch and refuge will land that way.

However I don't think it's OK to ask for  a branch / fix especially
when diff < 200 LOC even if we use branch locally. Some are just
stashing instead of branching ...

- benoît
Permalink | Reply | 1 comment |
headers
Jason Smith | 1 Mar 2012 10:38
Gravatar

Re: Experiments with Git

On Thu, Mar 1, 2012 at 2:39 PM, Benoit Chesneau <bchesneau@...> wrote:
> However I don't think it's OK to ask for  a branch / fix especially
> when diff < 200 LOC even if we use branch locally.

Yes I agree wholeheartedly.

We should not ask for a branch when it is a small issue.

--

-- 
Iris Couch
Permalink | Reply | 0 comments |
headers
Stefan Kögl | 1 Mar 2012 12:17
Picon

Crash of CouchDB 1.2.x

Hello,

My experiments to replicate some live data / traffic to a CouchDB
1.2.x (running the current 1.2.x branch + the patch from [1]) that
sparked the indexing speed discussions, did also yield another
(potential) problem. First sorry for not further reporting back any
performance measurements, but I didn't yet find the time to run the
tests on my machines.

Anyway, I found the following stack traces in my log (after noticing
that some requests failed and compaction of a view stopped)

http://skoegl.net/~stefan/tmp/couchdb-1.2.x-crash.txt

The files starts at the first failed requests. Every request before
that returned a positiv (ie 2xx) status code. The crash might have
some "natural" reason (such as timeouts, lack of RAM, etc), but I'm
not sure how to interpret Erlang stack traces. Can somebody point me
in the right direction for diagnosing the problem?

Thanks,

-- Stefan

[1] http://friendpaste.com/178nPFgfyyeGf2vtNRpL0w
Permalink | Reply | 19 comments |
headers
Vinomedia | 1 Mar 2012 15:23

Guide Champagne Euvrard Garnier - Edition 2012


Si vous n'arrivez pas à ouvrir ce mail, consultez sa version en ligne
<http://www.vinomedia.fr/emailing/vinomedia-publishing/guide_euvrard2012
.htm> 

 
<http://www.vinomedia.fr/emailing/vinomedia-publishing/guide%20euvrard20
12/images/email_01.jpg> 	

<http://www.vinomedia.fr/emailing/vinomedia-publishing/guide%20euvrard20
12/images/email_02.jpg> 	Accéder à la vente
<http://mailing.vinsprimeurs.com/rclickr.asp?click_id_cmp=3434&click_ema
il=couchdb-dev%40incubator.apache.org&click_diug=1355a90fb5ab56f7ba9b009
5f83760f1&click_url=http://www.vinomedia-publishing.com/produit.asp?pr_i
d_produit=62>
<http://www.vinomedia.fr/emailing/vinomedia-publishing/guide%20euvrard20
12/images/email_04.jpg> 	

<http://www.vinomedia.fr/emailing/vinomedia-publishing/guide%20euvrard20
12/images/email_05.jpg> 	

Conformément à la loi N° 78-17 du 6 janvier 1978, vous pouvez demander à
être retiré de cette liste.
Pour vous désinscrire et ne plus recevoir de messages de notre part
cliquez ici
<http://optout.vinsprimeurs.com/parseOut.asp?cn_id_cmp=3434&cn_email=cou
chdb-dev%40incubator.apache.org&cn_diug=1355a90fb5ab56f7ba9b0095f83760f1
&cn_id_tneilc=10> ,
dans le cas contraire nous considérerons que vous acceptez de les
recevoir.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Lehnardt | 1 Mar 2012 16:48
Picon
Favicon
Gravatar

Re: Experiments with Git

I'd say, branch away!

On Mar 1, 2012, at 01:27 , Jason Smith wrote:

> Hi, all.
> 
> I hope you will pardon my commits to the repository. My plan is to try
> to stumble upon some useful custom or workflow. Please let me know if
> you have feedback or views.
> 
> Piggybacking off of Randall's idea, I have made a branch for every
> JIRA ticket that I am interested or involved in. I would personally
> like to see more branching and merging in the repo--to see it look
> less like a Subversion timeline.
> 
> Once 1.2 is out, I also intend to push some feature branches, with no
> intention for short-term merging, just to get them out there in the
> open. I hope Benoit might push up some refuge  work, or others can
> exercise their branches similarly.
Permalink | Reply | 0 comments |

Gmane