Way to go! Exciting.
On Apr 16, 2016 09:46, "Tahoe-LAFS" wrote:
> #1432: Magic Folder on Mac OS X and other BSDs
> -+-
> Reporter: davidsarah | Owner:
> Type: enhancement | Status:
Unfortunately I didn't see this until I read about it in TWN
(https://tahoe-lafs.org/~marlowe/TWN62.html). This, along with about
half of the emails from tahoe-dev and trac, were in my spam folder in
gmail. ☹
On Fri, Apr 1, 2016 at 11:44 PM, Brian Warner wrote:
>
> I'd like to hear from Daira and
Dear BG:
Welcome!
> First a note, quickstart.rst has to be adapted for Mac. Python needs to point
> to the setup.py script inside the App package, so I adapted the build
> instruction.
…
> ENTER NEW COMMAND (/) > python /allmydata-tahoe-1.10.2/setup.py build
> Traceback (most recent call last):
Maybe the zfec C code could do a precondition check as early as
possible and cause an assertion failure that clearly communicates to
the programmer what the legal range of the inputs is.
The Python wrapper already does this:
https://github.com/vu3rdd/zfec/blob/master/zfec/_fecmodule.c#L66
Sincer
Dear folks:
Context: “Magic Folders” is a new layer on top of Tahoe-LAFS which
implements Dropbox-like "auto-sync" behavior. It's super exciting!
Development of it was sponsored by Open Technology Fund. We've
finished implementing it, but now we're noticing some bugs and
limitations, and this is t
I agree with Greg. There's a meaningful setting in which you want to
hide from a network eavesdropper the IP address of your client, *and*
you want to hide from the network eavesdropper the fact that multiple
requests of yours are all coming from the same client, and you want to
hide from the Tahoe
Dear David:
Please don't send posts to the tahoe-dev mailing list which contain
criticisms of other people's behavior. I want people to continue to
feel free to post to this list, expecting a kind and friendly
response. This isn't because I have some kind of religious preference
for kindness — it
On Fri, Jul 17, 2015 at 8:30 AM, Freelab initiative
wrote:
>
> i am not so convinced about the helper stability : sometimes i have observed
> my helper receiving files but not processing them. ( just having the total
> request queue going up and up)
I don't like to slander a tool as "maybe unreli
> Big +1. Also, it seems to be uploading much more than necessary what
> makes it almost impractical to work with slow links.
There are two ways currently available to make it stop uploading redundant data:
1. set K=N. This is especially simple to think about if you set K=N=1.
Then it will upload
Hello! Thank you very much for the helpful feedback.
On Thu, Jul 16, 2015 at 6:25 PM, Freelab initiative
wrote:
>
> very satisfied in the quite easy deployment
> very satisfied in the quality of between nodes sync
> and the general reliabiliy of networks
Glad to hear it!
> the bad thing with
On Sat, Aug 15, 2015 at 12:45 PM, chenzhigu...@nudt.edu.cn
wrote:
> I found that some source code on the websites
> "https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-sdists/"; may
> be corrupted!
Dear chenzhiguang:
Did you mean just because of the failure that you earlier reported in
Hello chenzhiguang:
Thank you very much for your report.
> Searching for pyOpenSSL>=0.13,<=0.13.1
> Reading https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-sdists/
> Download error: unknown url type: https -- Some packages may not be found!
This means that your Python installation d
Hrm. I don't understand why this would happen. Ed: could you try to
reproduce this error, and then if you succeed hit the "Report a Bug"
button on your web gateway?
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug
I guess it *could* be a bug in 1.9.2 that has subsequently been fixed,
b
Hi Mark:
Did you figure out answers to your questions about how to share
introducer FURLs and how to configure nicknames and so on?
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe
Dear droki:
Awesome! This might be just the key we need to unlock this.
One possibility would be if you'd be willing to have your node connect to
our log-gatherer. Then all of the logs from your node would be transferred
(over Foolscap, therefore encrypted) to us.
Regards,
Zooko
On Jul 10, 2015
Hiya, droki!
Welcome.
I'm sorry it took this long before anyone replied to your mail.
On Thu, Jul 2, 2015 at 5:57 AM, droki wrote:
>
> I'm having trouble running "tahoe backup" involving two different
> issues. First, my backup command keeps getting stuck on a single file.
> It just hangs on th
Hello Nigel!
Welcome.
> How do I replace the older system installation with the later one 'built'
> from the download directory?
This is really a question about how you wish to maintain your system.
There are lots of ways you could do this.
One option that you might like — judging from the fact
Whoo-hoo! Way to go, Brian, for being the best Release Manager. :-)
Tahoe-LAFS v1.10.1 is excellent for being a stable, bugfix release.
Now what shall we do next?
https://tahoe-lafs.org/trac/tahoe-lafs/milestone/1.11.0
My top priority is to land Servers-Of-Happiness (`#1382`_). We have a
good in
Folks:
We're applying for Google Summer of Code, again!
The next step is to suggest some appropriately-sized projects on this page:
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/GSoCIdeas
I'm excited about it! I think we'll probably manage to get one
student, and we'll load them up with 3 or 4 me
Hello! Thank you for the bug report. This is an instance of
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/FAQ#Q26_compile_error
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CompileError
I'll edit the wiki to give the typical error message on Mac OS X.
> unable to execute clang: No such file or dir
On Tue, Apr 2, 2013 at 10:06 AM, Zooko Wilcox-O'Hearn wrote:
>
>
>> In that case, there
>> would be no "module that you mustn't import" in the same place as a
>> "module you want to
>> import".
>>
>
> Well... you could als
On Tue, Apr 2, 2013 at 1:41 AM, Daira Hopwood (formerly David-Sarah) <
david-sa...@jacaranda.org> wrote:
>
> But the original assumption was that you would never have multiple
> versions of a single
> package installed. That is, if you wanted to install a new version, you'd
> uninstall any
> older
I thought the design flaw in question was:
When you "import foo", and there are multiple modules named "foo" in your
filesystem, then which specific module you get is determined by a list of
directories, each of which can contain multiple modules. Therefore, when
you add a directory to the front o
Dear Paul Rabahy and everyone else who helped:
Thank you very much for setting up a new test grid for people to easily
experiment with Tahoe-LAFS software!
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bi
Folks:
We decided not to do the hangout "on air" this time, as some people
feel like they would be inhibited in their conversation if it were
recorded and published like that. Maybe we could try an experiment in
putting it "on air" at some point.
Regards,
Zooko
in attendance: Zooko (scribe), Ma
In attendance: Brian, David-Sarah, Zooko (scribe), Andrew, PRabahy (silent)
The meeting started about 10 minutes late and ran more than 30 minutes
past its scheduled stop-time. (Because we were too engaged to stop at
the stop-time since we were sorting out the question of whether
Zooko's "Strong P
Folks:
One of the unit tests
(allmydata.test.test_cli.Cp.test_copy_using_filecap) takes more than
1000 seconds to complete on the leasedb branch, which uses sqlite for
tracking leases instead of putting leases as metadata appended to the
ends of share container files. The same test takes about 13
legend: "★" means Action Item! (If your name is mentioned after "★"
and you aren't really going to do that thing, then please let us
know!); "☑" means Action Item that is already done.
#include // I don't have time to write
explanations of all this, and I may have forgotten parts.
in attendance:
Folks:
I apparently never posted these notes from the LAFS Weekly Dev Chat of
November 1. I'm sorry about that. I was probably planning to flesh
them out with more context and explanation, but I haven't done that,
either. So, here's a dump of my notes.
Regards,
Zooko
=== 2012-11-01 ===
#1679
Let's talk about docs at the "LAFS Weekly Dev Chat" this Thursday.
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/WeeklyMeeting
This will be a "NUTS AND BOLTS" meeting.
To prepare for this meeting, write some docs! Fresh shiny new docs, or
patches to existing docs. Bring your docs to the chat.
--Z
On Wed, Nov 21, 2012 at 10:42 AM, David-Sarah Hopwood
wrote:
>
> Remember that those share states are needed anyway to avoid race conditions
> between adding and removing shares. There are no additional states just to
> support marking of potentially inconsistent shares.
Good point. If we had #
Dear til:
Yes, please! I would be very interested in new and/or improved
documentation about why and how to install and use Tahoe-LAFS. Here
are some existing resources:
quickstart, which you mentioned:
https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst
The "Installation"
2012-11-22
In attendance: Zooko [scribe], Marlowe, Andrew, David-Sarah
Agenda: close some tickets for Tahoe-LAFS v1.10!
this is a NUTS AND BOLTS meeting
notes:
Zooko is still learning how to do basic stuff with git.
We reviewed and committed one tiny patch.
https://github.com/tahoe-lafs/tahoe
Folks:
Every Thursday at 16:00Z we have a dev meetup. Tomorrow Brian won't be
able to make it, and the agenda for tomorrow is: close out tickets for
Tahoe-LAFS v1.10! That might include code review for tickets that
already have patches and unit tests, writing unit tests, or writing
patches.
Join
Folks:
I just reviewed (again), the design document for leasedb:
https://github.com/davidsarah/tahoe-lafs/blob/1818-leasedb/docs/proposed/leasedb.rst
Leasedb is implemented and passes unit tests (#1818), and we're
currently working on merging it with cloud-backend (#1819).
This is exciting, bec
Folks:
I posted some thoughts to #1755. If you're interested in distributed
systems, please read and comment!
I posted an argument for why distributed, end-to-end, two-phase commit
will probably work fine for LAFS's purposes even though it has gained
a well-deserved reputation for "not scaling up
Hello han zheng:
> When I saw the logging information, I saw a string "fdopen" when I "print"
> the req.content. So what is the meaning of the "fdopen" ?
"fdopen" is a Python library type:
http://docs.python.org/3/library/os.html?highlight=fdopen#os.fdopen
I believe the LAFS gateway is storing
Hi Greg! Glad to hear that you've re-registered on the Tahoe-LAFS trac. ☺
So, yes: we accidentally the whole htdigest file.
I think what happened was the filesystem was full and someone
registered on the trac and it tried to write the htdigest file and
thus replaced it with a 0-length file.
Anyw
Thanks, David-Sarah, and I'll follow up on those particular patches
via github comments.
But, this doesn't answer my question, which is: how can you (a) tell
if a patch has been reviewed, and (b) find the review comments?
I guess one answer would be: all reviews get posted to github
comment-on-th
Folks:
I'm reviewing the patches for #1818. This is a big step in
LeastAuthority.com's work for DARPA on Redundant Array of Independent
Clouds!
Along the way, I happened to look at this recent patch, even though it
isn't actually part of #1818:
https://github.com/davidsarah/tahoe-lafs/commit/12e
On Thu, Nov 15, 2012 at 5:20 AM, Iantcho Vassilev wrote:
> Forgot to add.. i use duplicity for doing the backups (upload and
> download)
Cool! And how well does it work? (Aside from this memory over-usage issue.)
Have you looked at "Duplicati"? It is an alternative/fork of duplicity.
I won
killyourtv:
Thank you for the report!
What version of Tahoe-LAFS are you using?
> Just a few minutes ago, while I was in the process of deleting several
> files from the clc (with my asinine for loop), in the middle of the
> process I received:
So, did you do anything else besides the "tahoe ls
On Thu, Nov 15, 2012 at 12:11 AM, Iantcho Vassilev wrote:
> Here is the incident archive as from the server..
Thanks, Iantcho!
This is interesting. Let's see... I see the hostnames of all the
storage servers from your grid. Oh, I see that Peter Secor is running
one of them. Cool.
It says that y
On Tue, Nov 13, 2012 at 10:47 PM, Iantcho Vassilev wrote:
>
> Now as the client is restarte would that be helpfull to push "Report a bug"?
There is probably no information in the new process about what
happened. On the other hand, it couldn't hurt! I could look at it and
see if anything in the i
Thank you for the bug report!
This sounds like a relatively bad bug. We try not to tolerate memory
over-usage bugs. I've marked #1824 as Priority: Critical.
On Mon, Nov 12, 2012 at 6:09 AM, Iantcho Vassilev wrote:
>
> There is nothing interesting in twistd.log..
> Should i send incidents dir..
Thanks for the recommendation of gitk, and the tips to enable "show
all refs" and "sort by date".
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Dear Han Zheng:
I'm glad you are learning how to write Python code to extend the
Tahoe-LAFS gateway.
On Fri, Nov 2, 2012 at 9:29 PM, han zheng wrote:
> if __name__ == "__main__":
> c = client.Client("/home/nick/.tahoe")
> uploader = c.getServiceNamed("uploader")
> uploadable = FileN
On Tue, Oct 30, 2012 at 9:25 AM, han zheng wrote:
>
> Is there a way to directly upload a local file to the "tahoe cloud" not using
> the web server?
Tahoe-LAFS doesn't offer any API reachable from other processes
(command-line, kernel, or remote-procedure-call) which *doesn't* route
through the
Dear Greg:
I didn't mean that leases can be renewed without walking the fs trees.
You are right that doesn't make sense. I mean on the storage server
side, leases can be queried and updated without walking over all the
share data, which is stored (in attached disk or in cloud storage) as
a set of
Folks:
I've written a trac ticket to track this issue. The description
includes both my use case, which I hope I explained clearly enough,
and a proposed protocol which I think would satisfy it and would fit
in with the rest of the LAFS protocol. Of course, the use case (or the
problem statement)
On Thu, Oct 25, 2012 at 10:50 PM, hi wrote:
> where is meta data store in tahoe, is it stored on the tahoe client server?
Hi. In typical Distributed File Systems like gluster, the contents of
the files are distributed across many storage servers, and the
"metadata" is managed by a single metadata
The Boulder, Colorado hackerspace (http://boulderhackerspace.com/)
will host the Boulder node of the party network. We start at 5 PM
UTC-6 == 23:00Z. I'll start trying to establish video chat lines of
communication with others one hour before that, so if you want to help
organize a Tahoe-LAFS Sixth
costs you *only* for the space you use, so it isn't a
big commitment), and 2. agree to show up at a Physical Tahoe-LAFS
Birthday Party Location to receive your t-shirt.
Regards,
Zooko Wilcox-O'Hearn
Founder, CEO, and Customer Support Rep
https://LeastAuthority.com
[*] "The first fe
Okay, great! I was very confused to think that querying and changing
leases would be a long expensive process. That's the whole *point* of
leasedb is to make that fast and reliable. Duh.
I agree that the protocol you sketched out in your email would work,
including that the client can wait for con
On Fri, Oct 12, 2012 at 4:29 PM, David-Sarah Hopwood
wrote:
>
>> The only difference between this and the current scheme is that the
>> storage server will never do that on its own — it only does it when
>> you tell it that it is okay to do it.
>
> Okay, so I think this means that lease expiry --
ond what we've already designed:
https://github.com/davidsarah/tahoe-lafs/blob/666-accounting/docs/specifications/leasedb.rst
Thanks for listening! Please let me know if I'm making an error here,
including an error in what our customers want. ☺
Regards,
Zooko Wilcox-O'Hearn
Fou
On Wed, Oct 10, 2012 at 12:25 AM, Eugen Leitl wrote:
>
> I would to like to try running it on cjdns, which is IPv6-only.
> Is IPv6 supported?
Hello Eugen. Interesting idea to run Tahoe-LAFS over cjdns!
Unfortunately, Tahoe-LAFS doesn't work with IPv6 yet.
Here's the main ticket tracking this wit
Folks:
The Tahoe-LAFS Weekly News hasn't come out in a few weeks:
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews
I miss it! If you, too, appreciate the Tahoe-LAFS Weekly News, then
join me by sending a personal email to marl...@antagonism.org thanking
him for his service so far
I forgot to take notes during, so this is ex post facto. Other
participants, please feel free to reply and add your recollections!
In attendance: Zooko, CodesInChaos, Andrew, Brian, Ali who popped in
briefly because the hangout was posted as a public chat on G+,
David-Sarah
The topic was mostly d
We accidentally the whole htdigest file.
Sorry about that!
--Z
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
On Mon, Jul 9, 2012 at 10:39 AM, Brad Rupp wrote:
>
> The output from repair #1:
>
> repair successful
> done: 11801 objects checked
> pre-repair: 11725 healthy, 76 unhealthy
> 76 repairs attempted, 76 successful, 0 failed
> post-repair: 11801 healthy, 0 unhealthy
>
> The output from repair #2:
caveat lector
2012-09-25 -- "The Science Fair episode"
in attendance: Zooko (scribe), CodesInChaos, amiller, David-Sarah, elb
Topic: proof-of-storage/proof-of-retrievability
CiC suggested a pass-through "Chess Grandmaster" style attack of
storage server which doesn't hold the data but queries
Hi Peter! Welcome.
I've recently added a FAQ about this. Please let me know if it helps.
The upshot is: please give us more details about your platform and beg
somebody to build some binary packages for your platform so that all
other users of your platform will see it work automatically. ☺
(Alth
Let's have synchronized Tahoe-LAFS Birthday Parties in various cities
(or rural locations) across the globe, on Saturday, October 27, 2012.
Want to organize one in your town? Email me! Or just post here.
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-
Let's organize Tahoe-LAFS Birthday Parties for the weekend following
October 22. Maybe Saturday the 27th?
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Folks:
As usual, I'm not taking the time to contextualize and vet all these
notes. Caveat lector! Also, I've maintained my tradition of adding
some of my own thoughts that weren't actually expressed out loud in
the discussion. (In particular the advocacy for adding padding and the
ideas about how
Folks:
According to recently unearthed archaeological records ¹, the first
patch was committed to Tahoe-LAFS project ² on October 22, 2006.
I'm going to host some kind of a birthday party in Boulder, Colorado
some day near October 22, 2012. I figure a good way to celebrate would
be to close six o
In attendance: Brian, David-Sarah, Andrew Miller, Zooko
scribe: Zooko (standard caveat applies: this hasty summary may be
inaccurate or lacking in context)
comms tech: Google Hangouts
agenda: ticket triage for Tahoe-LAFS v1.10
We went through the highest priority tickets for Tahoe-LAFS v1.10. T
Folks:
Here is your traditional, once-a-week, cryptic, and potentially
inaccurate summary of the developer conference call. In what follows I
make no attempt to explain the context. Sorry -- don't have time right
now! However, we do try to explain contexts on tickets, so if this
sounds interesting
On Fri, Aug 10, 2012 at 1:47 PM, Zooko Wilcox-O'Hearn wrote:
>
> • Shall we keep using AES-128 or upgrade to AES-256? On some
> low-power ARM CPUs AES-128⊕XSalsa20 takes 25% fewer CPU cycles than
> AES-256⊕XSalsa20. Is that significant? We need to do some
> back-of-the-envelo
Folks:
We had another Tahoe-LAFS Weekly Call. Here are my notes, which are
patchy and could be inaccurate. You could check this publicly editable
notepad for updates from the other attendees of the call.
http://titanpad.com/qnudyEsEoR
In attendance: Brian, David-Sarah, Zooko
About leasedb sch
In attendance: David-Sarah, Zooko [scribe], Brian
For future discussion, perhaps next week, Brian wants to talk about
Tit-for-Tat accounting when not all of the participants always run
both a client and a server.
Main topic: XSalsa20 encryption
The idea is to encrypt with a combination of XSalsa
There are several ways to put your revision control repository into
LAFS. The obvious one is mount LAFS with FUSE or pyfilesystem and
point your revision control tool at the mount point. That will
probably work with every modern revision control tool. If anyone has
tried that, I would like to hear
On Wed, Aug 8, 2012 at 2:42 AM, Tony Arcieri wrote:
> Awesome! Is the merge algorithm documented anywhere? Is it a patch-style
> algorithm, or more advanced?
It is only for mutable directories, not for mutable files.
Unfortunately it is not documented, I don't think, which is one of the
reasons t
On Wed, Aug 8, 2012 at 2:36 AM, Tony Arcieri wrote:
>
>> with the Tahoe-LAFS access control
>> architecture -- in which most things are immutable, and most mutable
>> things are writable by few or only one writer -- such cases appear to
>> be very rare.
>
>
> I operate a Friendgrid, and we have a
On Wed, Aug 8, 2012 at 2:31 AM, Zooko Wilcox-O'Hearn wrote:
> On Mon, Aug 6, 2012 at 1:38 PM, Tony Arcieri wrote:
>
>> From what I've read of how Tahoe handles conflicts, it employs a monotonic
>> version number and timestamps. So it sounds like in the event of a
On Mon, Aug 6, 2012 at 1:38 PM, Tony Arcieri wrote:
> On Mon, Aug 6, 2012 at 12:30 PM, Zooko Wilcox-O'Hearn
> wrote:
>>
>> How can both that story and also the things that have already been
>> posted on this thread both be true?
...
> As far as CAP theorem goes,
It isn't that what has been said on this thread so far is *wrong*,
exactly. I think it is correct. But contrast the overall impression
that one gets from this discussion with this story:
“At Virginia Tech Linux and Unix Users Group, we have a working
Tahoe-LAFS deployment of about 9-14 nodes. It's
I don't know anything about Ruby interfaces to native code, but you
might try emulating the Python interfaces that Myers, Tschechow, Brian
and I wrote -- the ones in the zfec package. Those ones are
handwritten wrappers using the CPython API, not using SWIG or any of
the dozen other interface-helpe
notes from Tahoe-LAFS Weekly Call, 2012-07-24
In attendance: David-Sarah, Brian, Zooko
http://titanpad.com/zuldkxdVX5
(appending a copy below)
Summary of the summary: Brian and David-Sarah are hard at work on the
accounting and lease database development, part of which goes to
satisfy Least Auth
Dear Sameer:
I've written a FAQ about the build system which names the six
libraries that are needed and explains how you could possibly get them
from "yum install" or else build them as "Python eggs":
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CompileError
https://tahoe-lafs.org/source/tahoe-l
I've been thinking about this more, including re-reading BenL's post
to tahoe-dev. I was inspired by hearing that Tahoe-LAFS's use case had
been discussed at the recent "Directions in Authenticated Ciphers"
workshop:
http://hyperelliptic.org/DIAC/
I've decided that I wasn't really on the right tr
On Sun, Apr 22, 2012 at 12:37 PM, markus reichelt wrote:
> Aloha!
>
> I have been testing lafs-rpg, available at:
>
> https://bitbucket.org/nejucomo/lafs-rpg/overview
>
> (haproxy/stunnel have been ditched in favour of nginx)
>
> Who else gave it a test-run? Please report :)
>
> https://bitbucket.
Dear Paul Grunwald:
Thank you for your persistence on this. :-)
Here's some context about how our build system works, or in this case
how it fails to work:
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CompileError
The dependency which failed to build for you is pycryptopp, which
happens to be on
• 1.9.2 release! Yay David-Sarah, Release Manager. Thanks to everyone
who contributed bug reports, patches, testing, packaging, etc.
• Add-only sets: Can servers exercise "editorial power" over add-only
sets, remixing different legitimate adder-signed sets to form new
sets? Zooko thinks this could
> That's actually also in 1.9.2:
>
> https://tahoe-lafs.org/trac/tahoe-lafs/browser/git/src/allmydata/storage/crawler.py?annotate=blame&branch=1.9.2#L193
Oh! Great. I wonder what version of Tahoe-LAFS Iantcho was using when
they got the exception in the initial post to this thread?
Hey, maybe Tah
>From revision control:
https://tahoe-lafs.org/trac/tahoe-lafs/browser/git/src/allmydata/storage/crawler.py?annotate=blame&rev=3cb99364e6a83d0064d2838a0c470278903e19ac#L193
It looks like David-Sarah has fixed this in trunk so that Tahoe-LAFS
will handle a corrupted or truncated state file by init
On Sun, Jul 1, 2012 at 9:51 PM, Brian wrote:
>
... snipping out a lot of useful, clear details about the new
introduction and accounting mechanisms ...
>
> I think we can probably accomodate that. I'm optimizing for our two main use
> cases: friendnet and paid-service.
>
> In the friendnet, nearl
On Sun, Jul 1, 2012 at 9:51 PM, Brian wrote:
>
... snipping out a lot of useful, clear details about the new
introduction and accounting mechanisms ...
>
> I think we can probably accomodate that. I'm optimizing for our two main use
> cases: friendnet and paid-service.
>
> In the friendnet, nearl
> So, the build runs fine on a XO 1.5. What should I be copying over to the
> XO-1 machine?
Well, the tahoe-lafs software itself is 100% pure Python, so it
doesn't need to be compiled. However there are several packages that
it depends on that it needs to either acquire a prebuilt binary,
either
On Sun, Jun 24, 2012 at 2:18 PM, Sameer Verma wrote:
>
> So, after a long break, I'm at it again.
Welcome back!
> {standard input}: Assembler messages:
> {standard input}:217576: Error: open CFI at the end of file; missing
> .cfi_endproc directive
> gcc: Internal error: Killed (program cc1plus)
On Fri, Jun 22, 2012 at 11:50 PM, David-Sarah Hopwood
wrote:
>>
>> https://lafsgateway.zooko.com/uri/URI:DIR2-RO:hqjv4r2rve4mydw6zwub2wqnom:4go7k3hbwi7hkoaluxjm7yiode54hzdkcvw7a5k7hhfso5wcb7vq/
>
> BTW, this doesn't differ functionally from the tarball I uploaded at
> https://tahoe-lafs.org/sourc
On Fri, Jun 22, 2012 at 1:26 PM, Zooko Wilcox-O'Hearn wrote:
> Here you go. Please test!
>
> https://lafsgateway.zooko.com/uri/URI:DIR2-RO:hqjv4r2rve4mydw6zwub2wqnom:4go7k3hbwi7hkoaluxjm7yiode54hzdkcvw7a5k7hhfso5wcb7vq/
Ugh, I put the wrong version number on there. It says "1.
Here you go. Please test!
https://lafsgateway.zooko.com/uri/URI:DIR2-RO:hqjv4r2rve4mydw6zwub2wqnom:4go7k3hbwi7hkoaluxjm7yiode54hzdkcvw7a5k7hhfso5wcb7vq/
There are many bugfixes in this version compared to v1.9.1. If you
have experienced *any* failures using earlier versions of Tahoe-LAFS,
then pl
On Fri, Jun 22, 2012 at 12:59 PM, Greg Troxel wrote:
>
> I thought tahoe was almost converted to git?
Yes, this will hopefully be the last release that we use darcs.
> Perhaps you could post a tarball that's just like the release,
I'm building a "1.9.2a1" tarball right now. We still intend to c
On Fri, Jun 22, 2012 at 12:51 PM, Zooko Wilcox-O'Hearn wrote:
>
> We prefer not to fix bugs when we don't have a unit test that goes from red
> to green by that fix,
By the way, I really like this part of our process around here. We
don't (usually) kill bugs by shootin
Dear Bertagaz:
We're almost ready to release Tahoe-LAFS v1.9.2, and I wonder if it is
okay to take a couple more days for extra testing or if we should
hurry and finalize it so you can package it for Debian?
We've fixed all but one of the issues that we intended to fix. You can
see the issue tick
Welcome to the world, rentanode.nl!
I'm delighted to hear that there is another company focused on helping
customers use Tahoe-LAFS.
I've already had two potential customers ask (on twitter) if it would
be possible for someone to lease service from both rentanode.nl *and*
leastauthority.com and s
Hooray!
Thanks, bertagaz.
This motivates me to fix more bugs/regressions in Tahoe-LAFS v1.9.2. :-)
As to your questions about the schedule of 1.9.2, I'll leave it to the
Release Manager (David-Sarah) to answer those.
Regards,
Zooko
___
tahoe-dev mail
Folks:
Brian has been posting patches that move away from using introducers
at all in favor of "gossip". Now if I understand correctly, gossip is
simply "every node is an introducer (in addition to whatever other
jobs it does)".
I have some questions about it, which I posted to this ticket, but
w
1 - 100 of 187 matches
Mail list logo
