Re: versioning for sensors data storage
user@ please.
On 8 Jun 2012, at 12:08, Maxim Osipov wrote:
> Hi,
>
> Warning: I'm new to CouchDB! And I'm in a process pf selecting a
> database to store data from sensors. The scenario looks like this:
>
> There are sensors on the net (may be thousands or later millions) for
> things like temperature, motion, etc. Each sensors has an IPv6 address
> and pushes data to central server in JSON format, like:
> { temp: 36.6; humidity: 80 }
> We don't know in advance what exactly sensor will push, but most of
> the time the format of JSON structure is the same. Data is updated ...
> say every second for each sensor.
>
> From the "architecture" point of view it could be a nice solution with
> CouchDB, where each sensor is represented by a document and each
> sample of sensor data is a version of this document.
>
> The questions are:
> - do we have time/date information for versions
> - is it easy/good to access document version history
> - what is a limit on number of versions and how it affects performance
> - is it possible/easy/good to get a time snapshot of database
>
> All other comments are also welcome!
>
> Kind regards,
> Maxim
>
> --
> Maxim Osipov
> Flexibity Ltd.
Re: So, how do we get the Mac binary on the home page?
I've reported the brew issue here: https://github.com/mxcl/homebrew/issues/12633 I don't think it's directly related to couchdb, just blocking it. Eli On Fri, Jun 8, 2012 at 11:55 AM, Dave Cottlehuber wrote: > On 8 June 2012 18:40, Eli Stevens (Gmail) wrote: > >> Thank you very much for working on this! I hadn't been able to get >> brew or build-couchdb to work on my laptop. >> >> Cheers, >> Eli > > I'd like to know what's stopping it, or at least be able to put a note > in the recipe > if its not fixable. > > What's your config? OS, XCode version, anything interesting in brew doctor? > > A+ > Dave
Re: So, how do we get the Mac binary on the home page?
On 8 June 2012 18:40, Eli Stevens (Gmail) wrote: > Thank you very much for working on this! I hadn't been able to get > brew or build-couchdb to work on my laptop. > > Cheers, > Eli I'd like to know what's stopping it, or at least be able to put a note in the recipe if its not fixable. What's your config? OS, XCode version, anything interesting in brew doctor? A+ Dave
Re: So, how do we get the Mac binary on the home page?
On 8 June 2012 16:40, Jan Lehnardt wrote: > > On Jun 8, 2012, at 16:31 , Hans J Schroeder wrote: > >> Hi Jan, >> >>> Can you specify what systems should use which versions, so we can label >>> them correctly on the website? >> >> For Mac OS X 10.6.8 to 10.7.2: >> https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0.zip >> >> For Mac OS X 10.7.3 and later >> https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip > > Thanks Hans! > > With this, I think we are good to go to put this on the website. Anyone > disagreeing? :) > > Cheers > Jan Some things, files are scattered across various places. #1 dbs & views are in ~/Library/Application Support/CouchDBServer/ #2 there's no local.ini as such, its in ~/Library/Preferences/couchdb-server.ini #3 couch.log is in $APPROOT/Contents/Resources/couchdbx-core/var/log/couch.log #4 couch.uri is in $APPROOT/Contents/Resources/couchdbx-core/var/run/couch.uri If its not hard to fix #3 and #4 we should do that first. This means CouchDB.app could run read-only in /Applications, which it doesn't atm. #1 and #2 make sense, but might not be immediately obvious. They could wait, its more about documenting somewhere. A+ Dave
Re: versioning for sensors data storage
On 08/06/12 12:08, Maxim Osipov wrote:
Hi,
Warning: I'm new to CouchDB! And I'm in a process pf selecting a
database to store data from sensors. The scenario looks like this:
There are sensors on the net (may be thousands or later millions) for
things like temperature, motion, etc. Each sensors has an IPv6 address
and pushes data to central server in JSON format, like:
{ temp: 36.6; humidity: 80 }
We don't know in advance what exactly sensor will push, but most of
the time the format of JSON structure is the same. Data is updated ...
say every second for each sensor.
> From the "architecture" point of view it could be a nice solution with
CouchDB, where each sensor is represented by a document and each
sample of sensor data is a version of this document.
Each sample time is represented by a document and each sensor has a field in
the document.
If multiple sensors read at the same time different documents are produced for
each sensor.
If sensors are all read at the same time multiple fields can exist in a single
time document.
Versions have nothing to do with what you are trying to do.
The questions are:
- do we have time/date information for versions
not a viable idea
- is it easy/good to access document version history
not for this purpose
- what is a limit on number of versions and how it affects performance
arbitrary 1000, but not to be used for this purpose
- is it possible/easy/good to get a time snapshot of database
yes
All other comments are also welcome!
Kind regards,
Maxim
http://otperl.com/my_nanode
381153 minute readings of temperature data in Couchdb
visualized by couchapp running d3.js
data comes from Nanode #490
some issues with negative degree readings on Nanode.
press Next (not start) to visualize.
You cannot break anything!
records in JSON, date is coded in id
dt = new Date(parseInt(parseInt(json.rows[0].id.slice(0,14),16)/1000));
|{
"|_id|":|"04c1f8cbefdf8af6aa4f5cff8291a2fb"|,
"|_rev|":|"1-56da4c7f440fcd48fd60a222e502d30b"|,
"|Nanode|":|"5.0.0"|,
"|NodeNo|":|"0490"|,
"|comment|":|"comment"|,
"|datastreams|":|[
|{
"|id|":|"temperatureC"|,
"|value|":|"8.83"|
}|,
|{
"|id|":|"F"|,
"|value|":|"47.24"|
}|,
|{
"|id|":|"mv"|,
"|value|":|"0.58"|
}|
]|
}|
David Martin (davidoccam)
Re: So, how do we get the Mac binary on the home page?
On Fri, Jun 8, 2012 at 7:31 AM, Hans J Schroeder wrote: > @Benoit > I prefer to use only the well known port 5984. Speaking only as an end-user, I agree that the well-known port should be the default. While this comes as a bit late to the party, the release seems to be working for me (I haven't run the tests, but my own application is chugging along nicely on it). Thank you very much for working on this! I hadn't been able to get brew or build-couchdb to work on my laptop. Cheers, Eli
[jira] [Commented] (COUCHDB-1490) Problems with views on large documents JSONs
[
https://issues.apache.org/jira/browse/COUCHDB-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291826#comment-13291826
]
Francesco commented on COUCHDB-1490:
Ryan,
well ATM is true we don't bacause we stopped expanding the project due this
prblem, but querying some parts of the model might be done in the future if
this problem is resolved.
Thank you anyway for the suggestion.
> Problems with views on large documents JSONs
>
>
> Key: COUCHDB-1490
> URL: https://issues.apache.org/jira/browse/COUCHDB-1490
> Project: CouchDB
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Mac Os x 10.6.8, intel Architecture (x86_64), 8Gb of
> Ram, Erlang R15B01 (erts-5.9.1)
>Reporter: Francesco
>
> Hi,
> i run a couchdb server (v1.2.0) over a mac (intel architecture, 8gb of ram,
> os x version 10.6.8) installed with brew.
> The server itself is used as a storage of big jsons (example:
> https://raw.github.com/cvdlab-bio/webpdb/develop/docs/jsons/2LGB-pretty-print.json
> and
> https://raw.github.com/cvdlab-bio/webpdb/develop/docs/jsons/2CRK-pretty-print.json
> ) for a tiny uni project.
> When we load more than 3 of these jsons, all the map functions (we created to
> retrieve documents besides a simple get by id) does not work.
> A typical map is:
> function(doc){if(doc.TITLE.title.match('.*INSULIN.*') !== null) emit(doc.ID,
> doc);}
> but even a
> function(doc){emit(doc.ID, doc.ID)}
> cease to work.
> while when there are just 3 or 2 jsons in the database they work just fine. I
> tried increasing the stack for couchjs (1gb now, going over 1gb doesn't work
> it seems), increasing limits for files (4096), increasing timeout for
> processes but in the end i don't get any results and only a (Error:
> os_process_error {exit_status,0}) from the db.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: So, how do we get the Mac binary on the home page?
Great job everyone - it's great, I mean GREAT to see the Mac joining the official distributions at long last. For completeness I've tried out the 10.7.3 link on a brand new iMac, installed in seconds without a hitch and 72 of 72 test(s) run, 0 failures (349036 ms). I also did a quick replicate of a 1.0.2 database from a remote service and ran some views and it all just works out of the box as expected (hoped). This is going to make it so much easier to advocate couch for Mac (and iOS) projects and I hope to be giving a talk at LIDG on this soon - I've kind of been holding back on the presentation until 1.2 was Mac friendly so this is just the impetus I need to finish the talk off. :-) Roger On 8 June 2012 15:40, Jan Lehnardt wrote: > > On Jun 8, 2012, at 16:31 , Hans J Schroeder wrote: > > > Hi Jan, > > > >> Can you specify what systems should use which versions, so we can label > them correctly on the website? > > > > For Mac OS X 10.6.8 to 10.7.2: > > > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0.zip > > > > For Mac OS X 10.7.3 and later > > > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip > > Thanks Hans! > > With this, I think we are good to go to put this on the website. Anyone > disagreeing? :) > > Cheers > Jan > -- > > > @Benoit > > I prefer to use only the well known port 5984. > > > > I agree on using the sandboxing mode. I suggest to make the next version > (when CouchDB 1.3 comes out) that way. > > > > I also agree on having the code in the CouchDB repo. Maybe someone with > commit rights can do the checkin. The > > License is already Apache. > > > > - Hans > > > > On Jun 8, 2012, at 12:51 PM, Benoit Chesneau wrote: > > > >> On Fri, Jun 8, 2012 at 12:09 PM, Jan Lehnardt wrote: > >>> > >>> On Jun 8, 2012, at 10:43 , Benoit Chesneau wrote: > >>> > On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder > wrote: > > Hi Ryan, > > > > Thanks for testing. For older OS X versions you should use the other > build. It is the same, but built with XCode 4.2. Apple made some > significant changes from 10.7.2 to 10.7.3. > > > > - Hans > > > > > So I tested the binary and noticed it was starting on the 5984 port. > > Which means it hanged there since I had already a version running. I > think it would be good that a free port should be used on startup > (what is done by rcouchx). Except that it looks too work on latest > osx Lion. I still need to test on the coming version and in > particularly test if it works when sandboxed mode is enforced which > the default in new version. > > Also I would feel better to have the code in the Couchdb repository. > Binaries linked on the download pages will be considered as official > and supported. And imo we should only consider something as official > and supported if it's in the official source under the same license > agreement. Like it is for the windows one. > >>> > >>> Benoit, all great points, we should definitely look into all those > >>> things. I also think these are not blocking for getting the current > >>> binaries on the website (given we can define which works on which > >>> systems, as per my last mail, and given we don't find more issues). > >>> > >>> Once we have more people using this, we can fix all the remaining > >>> issues. I hope you agree! :) > >>> > >>> Cheers > >>> Jan > >>> -- > >>> > >> Jan, > >> > >> Yeah sure no problem at all, and technical details can be solved on > time. > >> > >> Although we may need to make sure everyone is ready and OK to put > >> the code in official sources and sign everything needed ? If you think > >> this is not a problem, then go :) > >> > >> - benoit > > > >
Re: So, how do we get the Mac binary on the home page?
On Jun 8, 2012, at 16:31 , Hans J Schroeder wrote: > Hi Jan, > >> Can you specify what systems should use which versions, so we can label them >> correctly on the website? > > For Mac OS X 10.6.8 to 10.7.2: > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0.zip > > For Mac OS X 10.7.3 and later > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip Thanks Hans! With this, I think we are good to go to put this on the website. Anyone disagreeing? :) Cheers Jan -- > @Benoit > I prefer to use only the well known port 5984. > > I agree on using the sandboxing mode. I suggest to make the next version > (when CouchDB 1.3 comes out) that way. > > I also agree on having the code in the CouchDB repo. Maybe someone with > commit rights can do the checkin. The > License is already Apache. > > - Hans > > On Jun 8, 2012, at 12:51 PM, Benoit Chesneau wrote: > >> On Fri, Jun 8, 2012 at 12:09 PM, Jan Lehnardt wrote: >>> >>> On Jun 8, 2012, at 10:43 , Benoit Chesneau wrote: >>> On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder wrote: > Hi Ryan, > > Thanks for testing. For older OS X versions you should use the other > build. It is the same, but built with XCode 4.2. Apple made some > significant changes from 10.7.2 to 10.7.3. > > - Hans > So I tested the binary and noticed it was starting on the 5984 port. Which means it hanged there since I had already a version running. I think it would be good that a free port should be used on startup (what is done by rcouchx). Except that it looks too work on latest osx Lion. I still need to test on the coming version and in particularly test if it works when sandboxed mode is enforced which the default in new version. Also I would feel better to have the code in the Couchdb repository. Binaries linked on the download pages will be considered as official and supported. And imo we should only consider something as official and supported if it's in the official source under the same license agreement. Like it is for the windows one. >>> >>> Benoit, all great points, we should definitely look into all those >>> things. I also think these are not blocking for getting the current >>> binaries on the website (given we can define which works on which >>> systems, as per my last mail, and given we don't find more issues). >>> >>> Once we have more people using this, we can fix all the remaining >>> issues. I hope you agree! :) >>> >>> Cheers >>> Jan >>> -- >>> >> Jan, >> >> Yeah sure no problem at all, and technical details can be solved on time. >> >> Although we may need to make sure everyone is ready and OK to put >> the code in official sources and sign everything needed ? If you think >> this is not a problem, then go :) >> >> - benoit >
Re: So, how do we get the Mac binary on the home page?
Hi Jan, > Can you specify what systems should use which versions, so we can label them > correctly on the website? For Mac OS X 10.6.8 to 10.7.2: https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0.zip For Mac OS X 10.7.3 and later https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip @Benoit I prefer to use only the well known port 5984. I agree on using the sandboxing mode. I suggest to make the next version (when CouchDB 1.3 comes out) that way. I also agree on having the code in the CouchDB repo. Maybe someone with commit rights can do the checkin. The License is already Apache. - Hans On Jun 8, 2012, at 12:51 PM, Benoit Chesneau wrote: > On Fri, Jun 8, 2012 at 12:09 PM, Jan Lehnardt wrote: >> >> On Jun 8, 2012, at 10:43 , Benoit Chesneau wrote: >> >>> On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder wrote: Hi Ryan, Thanks for testing. For older OS X versions you should use the other build. It is the same, but built with XCode 4.2. Apple made some significant changes from 10.7.2 to 10.7.3. - Hans >>> >>> >>> So I tested the binary and noticed it was starting on the 5984 port. >>> >>> Which means it hanged there since I had already a version running. I >>> think it would be good that a free port should be used on startup >>> (what is done by rcouchx). Except that it looks too work on latest >>> osx Lion. I still need to test on the coming version and in >>> particularly test if it works when sandboxed mode is enforced which >>> the default in new version. >>> >>> Also I would feel better to have the code in the Couchdb repository. >>> Binaries linked on the download pages will be considered as official >>> and supported. And imo we should only consider something as official >>> and supported if it's in the official source under the same license >>> agreement. Like it is for the windows one. >> >> Benoit, all great points, we should definitely look into all those >> things. I also think these are not blocking for getting the current >> binaries on the website (given we can define which works on which >> systems, as per my last mail, and given we don't find more issues). >> >> Once we have more people using this, we can fix all the remaining >> issues. I hope you agree! :) >> >> Cheers >> Jan >> -- >> > Jan, > > Yeah sure no problem at all, and technical details can be solved on time. > > Although we may need to make sure everyone is ready and OK to put > the code in official sources and sign everything needed ? If you think > this is not a problem, then go :) > > - benoit
[jira] [Commented] (COUCHDB-1490) Problems with views on large documents JSONs
[
https://issues.apache.org/jira/browse/COUCHDB-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291782#comment-13291782
]
Ryan Richt commented on COUCHDB-1490:
-
Francesco,
I'm guessing you dont need to do any M/R indexing over the protein structure
description (the model / atoms) that make up most of the document.
If this is true, move all of that su-tree of the JSON to a binary attachment.
You can't M/R over it, and the doc will be about the same size, but the amount
of data the view indexer has to pack/unpack will be greatly reduced and your
problem should go away. I know that's not a real solution, but it is more
in-line with the intended use cases of CouchDB.
we've seen documents work best when the JSON is a few kB to a few MB, but
attachments can be GB range without issues.
> Problems with views on large documents JSONs
>
>
> Key: COUCHDB-1490
> URL: https://issues.apache.org/jira/browse/COUCHDB-1490
> Project: CouchDB
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Mac Os x 10.6.8, intel Architecture (x86_64), 8Gb of
> Ram, Erlang R15B01 (erts-5.9.1)
>Reporter: Francesco
>
> Hi,
> i run a couchdb server (v1.2.0) over a mac (intel architecture, 8gb of ram,
> os x version 10.6.8) installed with brew.
> The server itself is used as a storage of big jsons (example:
> https://raw.github.com/cvdlab-bio/webpdb/develop/docs/jsons/2LGB-pretty-print.json
> and
> https://raw.github.com/cvdlab-bio/webpdb/develop/docs/jsons/2CRK-pretty-print.json
> ) for a tiny uni project.
> When we load more than 3 of these jsons, all the map functions (we created to
> retrieve documents besides a simple get by id) does not work.
> A typical map is:
> function(doc){if(doc.TITLE.title.match('.*INSULIN.*') !== null) emit(doc.ID,
> doc);}
> but even a
> function(doc){emit(doc.ID, doc.ID)}
> cease to work.
> while when there are just 3 or 2 jsons in the database they work just fine. I
> tried increasing the stack for couchjs (1gb now, going over 1gb doesn't work
> it seems), increasing limits for files (4096), increasing timeout for
> processes but in the end i don't get any results and only a (Error:
> os_process_error {exit_status,0}) from the db.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: versioning for sensors data storage
Hi, > From the "architecture" point of view it could be a nice solution with > CouchDB, where each sensor is represented by a document and each > sample of sensor data is a version of this document. > > You don't want to do that, as soon as a compaction occurs you'll loose your history. Instead make a document for each sample, and include the sensor id in that document, so you can build a view of the samples for a given sensor. > The questions are: > - do we have time/date information for versions > > No, you'd need to add that into the document yourself. > - is it easy/good to access document version history > - what is a limit on number of versions and how it affects performance > > See above > - is it possible/easy/good to get a time snapshot of database > > > You mean for backup? Sure, either copy the db file or if you need to access it remotely you can page through _all_docs to get a snapshot. You could also use the _changes feed to do a rolling backup. Cheers Simon
versioning for sensors data storage
Hi,
Warning: I'm new to CouchDB! And I'm in a process pf selecting a
database to store data from sensors. The scenario looks like this:
There are sensors on the net (may be thousands or later millions) for
things like temperature, motion, etc. Each sensors has an IPv6 address
and pushes data to central server in JSON format, like:
{ temp: 36.6; humidity: 80 }
We don't know in advance what exactly sensor will push, but most of
the time the format of JSON structure is the same. Data is updated ...
say every second for each sensor.
>From the "architecture" point of view it could be a nice solution with
CouchDB, where each sensor is represented by a document and each
sample of sensor data is a version of this document.
The questions are:
- do we have time/date information for versions
- is it easy/good to access document version history
- what is a limit on number of versions and how it affects performance
- is it possible/easy/good to get a time snapshot of database
All other comments are also welcome!
Kind regards,
Maxim
--
Maxim Osipov
Flexibity Ltd.
Re: So, how do we get the Mac binary on the home page?
On Fri, Jun 8, 2012 at 12:09 PM, Jan Lehnardt wrote: > > On Jun 8, 2012, at 10:43 , Benoit Chesneau wrote: > >> On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder wrote: >>> Hi Ryan, >>> >>> Thanks for testing. For older OS X versions you should use the other build. >>> It is the same, but built with XCode 4.2. Apple made some significant >>> changes from 10.7.2 to 10.7.3. >>> >>> - Hans >>> >> >> >> So I tested the binary and noticed it was starting on the 5984 port. >> >> Which means it hanged there since I had already a version running. I >> think it would be good that a free port should be used on startup >> (what is done by rcouchx). Except that it looks too work on latest >> osx Lion. I still need to test on the coming version and in >> particularly test if it works when sandboxed mode is enforced which >> the default in new version. >> >> Also I would feel better to have the code in the Couchdb repository. >> Binaries linked on the download pages will be considered as official >> and supported. And imo we should only consider something as official >> and supported if it's in the official source under the same license >> agreement. Like it is for the windows one. > > Benoit, all great points, we should definitely look into all those > things. I also think these are not blocking for getting the current > binaries on the website (given we can define which works on which > systems, as per my last mail, and given we don't find more issues). > > Once we have more people using this, we can fix all the remaining > issues. I hope you agree! :) > > Cheers > Jan > -- > Jan, Yeah sure no problem at all, and technical details can be solved on time. Although we may need to make sure everyone is ready and OK to put the code in official sources and sign everything needed ? If you think this is not a problem, then go :) - benoit
Re: So, how do we get the Mac binary on the home page?
On Jun 8, 2012, at 10:43 , Benoit Chesneau wrote: > On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder wrote: >> Hi Ryan, >> >> Thanks for testing. For older OS X versions you should use the other build. >> It is the same, but built with XCode 4.2. Apple made some significant >> changes from 10.7.2 to 10.7.3. >> >> - Hans >> > > > So I tested the binary and noticed it was starting on the 5984 port. > > Which means it hanged there since I had already a version running. I > think it would be good that a free port should be used on startup > (what is done by rcouchx). Except that it looks too work on latest > osx Lion. I still need to test on the coming version and in > particularly test if it works when sandboxed mode is enforced which > the default in new version. > > Also I would feel better to have the code in the Couchdb repository. > Binaries linked on the download pages will be considered as official > and supported. And imo we should only consider something as official > and supported if it's in the official source under the same license > agreement. Like it is for the windows one. Benoit, all great points, we should definitely look into all those things. I also think these are not blocking for getting the current binaries on the website (given we can define which works on which systems, as per my last mail, and given we don't find more issues). Once we have more people using this, we can fix all the remaining issues. I hope you agree! :) Cheers Jan --
Re: So, how do we get the Mac binary on the home page?
Hans, the version works great for me. Good work! Can you specify what systems should use which versions, so we can label them correctly on the website? Cheers Jan -- On Jun 8, 2012, at 00:37 , Hans J Schroeder wrote: > Hi Ryan, > > Thanks for testing. For older OS X versions you should use the other build. > It is the same, but built with XCode 4.2. Apple made some significant changes > from 10.7.2 to 10.7.3. > > - Hans > > On Jun 8, 2012, at 12:16 AM, Ryan Ramage wrote: > >> Testing on a older OSX (10.6.8). >> >> I get a whole bunch of 'OS Process Error'. Here is the log: >> https://friendpaste.com/2r2D79DYoaV3CuSOUn99eD >> >> >> On Thu, Jun 7, 2012 at 3:41 PM, Hans J Schroeder wrote: >>> Hi Dave, >>> >>> Great news thanks. Looking forward for your test suite results. >>> >>> - Hans >>> >>> On Jun 7, 2012, at 11:36 PM, Dave Cottlehuber wrote: >>> On 7 June 2012 20:32, Hans J Schroeder wrote: > Hi, > > I have installed the latest XCode 4.3.2 and have rebuilt the app. In my > tests everything is fine now. I have uploaded the new binary on github: > > > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip > > @Jan, @Robert > Can you please retest? Hi Hans, I'm on 10.7.4 also, had same error as others re couchjs on prev build. This one works fine, building views & replicating successfully. I'll do the test suite dance tomorrow. A+ Dave >>> >
Re: So, how do we get the Mac binary on the home page?
On Fri, Jun 8, 2012 at 12:37 AM, Hans J Schroeder wrote: > Hi Ryan, > > Thanks for testing. For older OS X versions you should use the other build. > It is the same, but built with XCode 4.2. Apple made some significant changes > from 10.7.2 to 10.7.3. > > - Hans > So I tested the binary and noticed it was starting on the 5984 port. Which means it hanged there since I had already a version running. I think it would be good that a free port should be used on startup (what is done by rcouchx). Except that it looks too work on latest osx Lion. I still need to test on the coming version and in particularly test if it works when sandboxed mode is enforced which the default in new version. Also I would feel better to have the code in the Couchdb repository. Binaries linked on the download pages will be considered as official and supported. And imo we should only consider something as official and supported if it's in the official source under the same license agreement. Like it is for the windows one. - benoit - benoit
Re: So, how do we get the Mac binary on the home page?
On 8 June 2012 00:37, Hans J Schroeder wrote: > Hi Ryan, > > Thanks for testing. For older OS X versions you should use the other > build. It is the same, but built with XCode 4.2. Apple made some > significant changes from 10.7.2 to 10.7.3. > > - Hans > > On Jun 8, 2012, at 12:16 AM, Ryan Ramage wrote: > > > Testing on a older OSX (10.6.8). > > > > I get a whole bunch of 'OS Process Error'. Here is the log: > > https://friendpaste.com/2r2D79DYoaV3CuSOUn99eD > > > > > > On Thu, Jun 7, 2012 at 3:41 PM, Hans J Schroeder wrote: > >> Hi Dave, > >> > >> Great news thanks. Looking forward for your test suite results. > >> > >> - Hans > >> > >> On Jun 7, 2012, at 11:36 PM, Dave Cottlehuber wrote: > >> > >>> On 7 June 2012 20:32, Hans J Schroeder wrote: > >>> > Hi, > > I have installed the latest XCode 4.3.2 and have rebuilt the app. In > my > tests everything is fine now. I have uploaded the new binary on > github: > > > > https://github.com/downloads/cloudnode/couchdbx-app/CouchDB%20Server-1.2.0-OS%20X%2010.7.3.zip > > @Jan, @Robert > Can you please retest? > >>> > >>> > >>> > >>> Hi Hans, > >>> > >>> I'm on 10.7.4 also, had same error as others re couchjs on prev build. > >>> > >>> This one works fine, building views & replicating successfully. I'll > do the > >>> test suite dance tomorrow. > >>> > >>> A+ > >>> Dave > >> > > OK, so we need 2 links then? Old, 32 bit <= Snow Leopard, or 64 bit Lion >= ?
