One question.
Assume that I want to merge the main branch s2_5 to icap-2_5 branch
If I am right, I must execute the followings:
cvsmergeinit s2_5
cvsmerge s2_5
Make my changes and then execute:
cvs commit
As I show the cvsmergeinit makes a tag to CVS e.g Z-icap-2_5_merge_s2_5
I just complete the merging of main squid 2.5 tree to the icap-2_5 branch.
It looks ok, but I must look more on it, and examine
the code again. Seems that icap branch developed for long time
independently
-
Christos
PS. I want to rm -f all CVS repositories on the world .
Hi all,
Squid's icap client is not perfect but it was not always responsilbe
for all problems when works with icap servers. I am testing it with
drweb-icap server. All thinks looks good, except the keep-alive behaviour.
drweb-icap server responce with Conection:keep-alive but then imediatelly
This mail posted to c-icap mailing list.
I believe that it is related with ICAP's request modification operation.
It does not contain enough info but sometimes it is useful
to just know the problems.
-
Christos
Mateus Gröess wrote:
Hi, Christos
Today I was looking in cache.log of
Mateus
send me the backtrace
On Apr 5, 2005 10:05 AM, Mateus Gröess wrote:
2005/04/04 14:07:00| storeLateRelease: released 0 objects
2005/04/04 17:12:31| assertion failed: client_side.c:3268: cbdataValid(conn)
2005/04/04 17:12:42| Starting Squid Cache version 2.5.STABLE9-CVS for
olivier wrote:
Hello,
The latest cvs version of squid-icap seems broken (in RESPMOD at least)
I see queries like:
-
RESPMOD icap://127.0.0.1/dwp ICAP/1.0
Encapsulated(...)
- - the ICAP headers are ok -
But in the client request headers i see:
Hi,
Ok the news for icap-patch for squid are not good.
I am putting some effort and I believe that day by day
will become more stable.
Baumgaertel Oliver wrote:
I've taken a look at 2.5.STABLE9 and managed
sofar to apply all the patches but the 2Gig one to this combination,
creating a thing that
Baumgaertel Oliver wrote:
Same procedure as last time... It won't patch against the normal STABLE9
branch. What is exactly what I was talking about in the first place. It's no
use if we can't run the patch at least against ones that were already
introduced some time
Henrik Nordstrom wrote:
Hello Henrik,
I dont know who is responsible for icapclient development in squid, if
not you are, please forward it.
We have been using the squid with icap support. We found the following
problem in squid icap client:
When an HTTP server sends a response to squid
Henrik Nordstrom wrote:
..
All required changes committed.
I hope that this means that you are starting developement in icap-client :-)
I think icap is a must for squid.
Thinks like modifing headers (like those you are talking about with James )
are easier using icap. It is better for
Henrik Nordstrom wrote:
Not in this icap client. But I have another (see below).
I wrote in a previous mail that I am considering the current ICAP client
for squid problematic.
And I now that it will never be really good (if it will not rewritten
from scratch.).
I already have a what I
Hi Anton,
I think that this problem has allready corrected in cvs version of
squid-icap.
Regards,
Christos
Anton Ivanov wrote:
We make patch which fix error:
if client stop connection during file download to icap server this
process was not stopped
Hi Oliver,
I am copying from squid manual:
Use of ntlm NEGOTIATE is incompatible with challenge reuse, so
enabling this parameter will OVERRIDE the max_challenge_reuses and
max_challenge_lifetime parameters and set them to 0.
So I believe that you have ntlm reuse disabled
Hi ,
The file ClientRequestContext.h missing from squid3-icap cvs.
Alex,Duane, can you add it please?
Thanks,
Christos
Hi all,
I have a question about clientHttpRequest structure.
It has the field clientHttpRequest *next.
Where the hell used this field?
I am showing code like that:
while (*H) {
if (*H == http)
break;
H = (*H)-next;
}
But I can not find where two or more
Hi,
Please ignore this stupid question.
Was made while I was under panic :-(
Hi all,
I have a question about clientHttpRequest structure.
It has the field clientHttpRequest *next.
Where the hell used this field?
...
What am I loosing here?
Everything
Sory,
Christos
Hi all,
Where can I find the squid-2.6 sources? The development will
continue in sourceforge cvs?
I am thinking about porting squid2.5-icap branch to squid-2.6
if there is not any problem
Regards,
Christos
PS. sorry for d#959;uble posting
A fair amount of the planned patches has
Ok thanks,
I will do it.
Regards,
Christos
Please go ahead. I do not think any of the remaining planned patches
will cause any major merge conflicts so there is no reason to wait.
Regards
Henrik
OK, done.
squid-icap-2.6 branch at least compiles now.
Thanks,
Christos
Henrik Nordstrom wrote:
Note: To get the squid-2.6 tree for development
cvs -d [EMAIL PROTECTED]:/cvsroot/squid co -d squid-2.6 squid
This tree is only used for creating branches...
Regards
Henrik
Hi all,
tor 2006-05-18 klockan 01:59 +0200 skrev [EMAIL PROTECTED]:
Just a question, (i've been quite busy those weeks to follow this ml),
is the
ICAP support already merged ? I'd like to help Christos if not
icap-2.6 branch already exists in sourceforge cvs repository.
Looks that mostly
Hi Beeri,
Maybe you do not need to modify the squid-icap code to support your model.
I think that the correct implementation of your problem using squid-icap
is:
1) An http request come into the squid. Squid sends the reqmod request to
the icap server and server clasifies the request:
a) In
Hi Beeri,
1. Security - Origin sever might change the replied http header and add
the X-MY-SCANNER: Allow it self,
and bypass the content filter, In that case I would not
be able to prevent kids from viewing un honest pages :-(
Yes this problem exists.
I am just refering it as
Hi Graeme,
I did not verified the problems but looks that the problems exist.
About the first patch I am proposing a somehow different approach.
When squid-icap takes a 204 response immediately releases the connection
and put it to connections poll so it can be used for other icap requests.
The
Hi all,
Now the ICAP client in squid3 does not work very well. I am testing it
and looks that only partially works.
Are you planning to include ICAP client in squid 3.0 release?
Is anybody working on that?
It is not so difficult for someone to understand the ICAP related code,
looks good. I
Thanks,
I 'll try to help
Regards,
Christos
Please do! :)
Feel free to send squid-dev whats broken with the ICAP code.
You're also welcome in the #squiddev channel on Freenode IRC where you'll
find us trying to squish bugs.
adrian
Hi Alex,
Alex Rousskov wrote:
On Thu, 2006-09-28 at 05:18 -0400, Tsantilas Christos wrote:
3) File ICAP/ICAPModXact.cc function
ICAPModXact::handleCommWroteHeaders()
Sometimes, we have read the headers but not any part of the body yet
so in this case we must not call writeMore
Hi,
On Fri, 2006-11-03 at 08:32 -0500, Jeremy Hall wrote:
2: if the icap server returns a 403 squid just hangs up the connection
and doesn't send anything back to the browser at all. This produces
page cannot be displayed errors. I have looked at the icap code a bit
but was wondering if
Hi,
I send this mail from un account which is not subscribed to the mailing
list so I am re-sending it. Sory about that.
Please to the mailing list moderator to ingore the first mail.
-
Hi Christophe,
First of all squid3 has a better support for icap protocol now.
Maybe it is
Hi,
I think it should be icap-chunk_size == -2.
In icapParseChunkSize function in common_icap.c file the
icap-chunk_size set to -2 when the 0\r\n\r\n sequence parsed
Regards,
Christos
Henrik Nordstrom wrote:
tor 2006-11-09 klockan 12:37 +0200 skrev Tsantilas Christos
Hi,
From your logs what I am seeing is that the
icap-reqmod.http_entity.buf.size==0 so the icapRqModPassHttpBody must
not called, but it is called. It is strange.
Did you touch something else in code? Can you run squid in gdb and send
a backtrace after the crash?
Regards,
Christos
Christophe Boyanique wrote:
Yes we tried it and this leads to segfault too.
:-(
By reading the log I just noticed that with your modification the
icapReqModPassHttpBody is not called:
This is for the specific request (POST):
2006/11/24 14:15:22| handing request bodies in ICAP REQMOD
Hi Alex,
I try some test's. It is not so bad, but I saw that there are problems.
After surfing the web for a while the icap-client of squid failed and
the squid returned an error page to the web browser (ICAP protocoll
error ICAP server is not reachable ..)
The icap client sends an
Hi Alex,
Still exist problems in preview transaction between icap server and
squid. There are cases in which the squid-icap does not send the 0;
ieof sequence if all the http response body fits in the preview data
but sends the 0\r\n\r\n. After that gets the 100 continue icap
response but it
Alex Rousskov wrote:
On Sat, 2007-02-17 at 19:00 +0200, Tsantilas Christos wrote:
Still exist problems in preview transaction between icap server and
squid. There are cases in which the squid-icap does not send the 0;
ieof sequence if all the http response body fits in the preview data
Hi Christophe,
I think the best is to get the icap branch from cvs:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/squid co
-r icap-2_6 squid
After that run the bootstrap.sh script which included in cvs sources.
Do not try to correct rejected patches. The last merge with main squid26
done after
Hi all,
I was looking in squid3 code last days. I read again Adrian's mails
in which he complained about squid3 speed, and cpu usage.
Looking in the code there are a number of code-pieces which can
improved. An example is the call of headersEnd (Francisco Gimeno note
this problem too for
Hi Adrian,
Thanks for your answers. As I can understand you are talking about
the squid4 project. If you want an independent opinion, I believe that
it is not good idea to start striping the squid2.
You will get again the same mistakes done at squid3. For a such project
start from
Hi Alex,
Alex Rousskov wrote:
I have committed your change, simplified virgin body buffer maintenance
(in hope to minimize the number of similar bugs), and probably fixed a
bug with handling of post-preview 204 replies.
Yes I know. I am watching the branch for changes and additions...
The
Hi Alex,
Alex Rousskov wrote:
I agree that many Squid3 parts should be fixed, polished, or thrown
away. However, I think that we should focus on making Squid3 stable
first, and the performance/polishing work you are discussing should be
done for v3.1.
I am not
Tsantilas Christos wrote:
As an example of such changes I am attaching the rewritten
parseHttpRequest, prepareTransparentURL and prepareAcceleratedURL
Sorry to all
the code I send in previous mail will not compile. I am sending it
again. Needs some more testing to be sure that it is OK
Hi all,
I think, I found what causes the assertion in tunnel.cc which
reported by bug 1898:
assertion failed: tunnel.cc:372: amount == (size_t)len
Because I am not enough familiar with squid code I prefer the mailing
list instead of bugzila. I must say that I do not have a test case for
this
Hi Stephan,
Stefan Bischof wrote:
First I implemented
http://www.i-cap.org/spec/draft-stecher-icap-subid-00.txt
http://www.i-cap.org/spec/draft-stecher-icap-subid-00.txt by sending
X-Include: X-Authenticated-User
in my OPTIONS response. (I don't know if this draft is really
implemented,
When an http request adapted using ICAP then the client and server
addresses and the authentication information does not copied to adapted
request.
This is will cause problems in any following access control lists
proccessing.
Looks that the following patch solves the problem. (But I am to tired
Hi Alex,
Alex Rousskov wrote:
On Wed, 2007-03-07 at 23:57 +0200, Tsantilas Christos wrote:
When an http request adapted using ICAP then the client and server
addresses and the authentication information does not copied to adapted
request.
This is will cause problems in any following access
Hi Siddhesh,
The patch must apply to squid 2.6-STABLE10. If you see again the error
about squid/errors/list just press enter.
Maybe it is better to go with squid 3 instead , it has better support
for ICAP protocol..
Regards,
Christos
Siddhesh PaiRaikar wrote:
is there any patch for
Hi all,
This line exists in current icap-2_6 branch and in current patch.
It is missing only in 1.89.4.14 version of client_side.c but not in
other versions (older or newer). I do not know why, probably by accident ..
I don't think that it causes any problem.
Regards,
Christos
Henrik
Hi Henrik,
I forgot that the squid-26 moved to a branch. The problem with icap
patch is that it is HEAD based. In sourceforge I can not find any
squid-2.6 branch, to create a squid26 based icap branch.
Does make sense to create the icap-patch as a file and upload it to web
site? I think it is
Henrik Nordstrom wrote:
With the Squid-2 ICAP client still being somewhat experimental I do not
consider it a good idea to use in combination with Squid-2.6.STABLE. I
would very much prefer if people uses Squid-2.HEAD + icap if they need
that functionality, and knowing that their Squid
Alex Rousskov wrote:
On Thu, 2007-03-22 at 16:26 +0100, Kinkie wrote:
In this regard I see the ICAP server not to be any different from a
proxy server, of which it is simply an extension.
Whether the trust boundary includes both the proxy and the ICAP server
depends on the setup. Being an
When an ICAP server responds with an http response in request
modification, the web client waits more data from
the proxy. Iam using the squid3-icap branch.
An example of such ICAP response is:
ICAP/1.0 200 OK
Connection: keep-alive
ISTag: CI0001-X
Encapsulated: res-hdr=0,
Hi,
Which is the goal for squid3.0.PRE6? Which bugs waiting a fix before
released?
Can we assume that bug 1637 has a fix?
If I am not wrong most of the bugs causing crashes to squid fixed...
Regards,
Christos
Guido Serassio wrote:
There are some bugs probably ready to be commited/closed:
Excellent!
#1889: If the latest Henrik's comment is true...
He does not look like a person who says lies, I am sure that he has
correct it ;-)
Regards,
Christos
formating flags like %2.1f.
I think can be used as reference for other related convertions too.
Should I proceed with the convertion?
Should I post a patch to bugzila or open a temporary branch on
sourceforge better?
Regards,
Christos
#!/usr/bin/perl
#
# Author: Tsantilas Christos
Hi Duane,
the StoreEntry::swapOut() does not compile when SIZEIF_OFF_T==4
I am using the following patch, but I am not sure if it is OK ...
Regards,
Christos
--- store_swapout.cc18 Apr 2007 00:47:23 - 1.20
+++ store_swapout.cc18 Apr 2007 18:24:04 -
@@ -234,8 +234,8 @@
Thanks Alex,
Also I handled some other minor cases and run it in my sources.
Some statistics:
grep -n Converted CONVERT.log |wc -l - 2316
grep -n LeftAsIs CONVERT.log |wc -l - 137
Only 5-6 cases needed some work by me. Now compiles and the debug info
I am getting looks OK.
I will
Hi Duane,
I think there is an error in DelayPool.cc file and squid3 does not
compiles if delay pools are enabled.
The fix is:
--- DelayPool.cc20 Apr 2007 22:51:19 - 1.6
+++ DelayPool.cc22 Apr 2007 07:21:19 -
@@ -69,7 +69,7 @@
void
DelayPool::dump (StoreEntry
I do a first conversion from debug statements to debugs statements.
The patch is big (~750K) to post it to mailing list so I put the result
here:
http://www.chtsanti.net/others/CONVER_DEBUGS.diff
I hope that it is something needed for squid3 because the conversion
takes a lot of my time
Hi Adrian,
Looks that we are working the same thing. All we have limited time
so It is bad two people trying to do the same thing.
If you continue converting debug to debugs and similar code, please
inform me. If you think that I can help you please tell me how and I
will try. Or I can try
OK, It takes something less than a year...
The patch at:
http://www.chtsanti.net/others/CONVER_DEBUGS.diff
does not contains \n any more. I hope that it is OK now
Please try to do not find any such error ... in Sunday... you can find
it on Monday morning :-) !
Regards,
Christos
What I am actually getting using g++ 4.1 and g++ 4.2 compilers is:
cc1plus: warnings being treated as errors
DelayPool.cc: In member function ‘void DelayPool::dump(StoreEntry*,
unsigned int) const’:
DelayPool.cc:72: warning: NULL used in arithmetic
Regards,
Christos
Duane Wessels wrote:
Here is the patch which converts the debug statements to debugs statements:
http://www.chtsanti.net/others/CONVER_DEBUGS.diff
It is not excellent but it is not so bad...
Regards,
Christos
Hi Duane,
I am sending a patch for the squid3-largeobj.
- FTP: size of large files does not show well.
- _DigestFetchState::offset and _DigestFetchState::mask_offset I think
must be 64bit
- fde::bytes_read and fde::bytes_written must be 64 bit
Large files support is still incomplete, more
Please if you are able to run gdb please read the wiki how to report a
bug to squid bug database:
http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d
Regards,
Christos
Ghislain wrote:
Hello,
I test a Squid 3.0 PRE 5 and the nighty build
integers
- Remove or change some castings in file store_Client.cc
This patch apply to the squid3-largeobj branch.
I test it and worked for me.
I also test range headers, ftp and ICAP client. Looks good.
I did not test large objects uploads.
Regards,
Christos
Tsantilas Christos wrote:
Hi
Hi Jeremy,
Just use the latest nightly snapshot of squid3.
Should be OK.
Regards,
Christos
Jeremy Lardon wrote:
Hi,
I got some interest in Squid/ICAP architecture.
So I tried to patch the nightly snapshot but a large amount of code is
already in the Squid-3 source.
Consequently, I
is the following of some mails of this list. I tried to be
clearer and add more attachments.
As adviced by Tsantilas Christos and confirmed by Alex Rousskov, I
installed the Squid-3 nightly snapshot on my squid box to test with my
ICAP server.
The fact is that I doubt the old ICAP server (last release
Hi Amos
Amos Jeffries wrote:
Does ICAP really not build without a const version of the operator[]?
Strangly it does for me. Oh well, adding anyway.
May be because of different versions of g++. I am using g++ 4.1.2 here .
This change is more of a problem. To me it looks like the latter
Hi there,
Before SqString patch applied, squid3 looked stable, I had days to see a
problem.
The SqString had unpredicted effects in squid3 like the bug 1970. And
maybe there are other issues not appeared yet. It was not enough
analyzed before applied.
Regards,
Christos
PS. Last
Hi all,
I am done some tests and saw that squid3 does not support http 0.9
protocol. Is this something important for squid3?
Is the 0.9 http version still in use?
Regards,
Christos
Henrik Nordstrom wrote:
On tis, 2007-07-31 at 21:09 +, chtsanti wrote:
Please avoid casting unless needed. The compiler automatically promotes
to larger types when needed, and will tell you if you try to do the
reverse..
So stop casting things to (int64_t).
OK. Sometimes I am using
At the end I just put quick_abort_min and quick_abort_max to its
original behavior. They are storing values in kilobytes and if the units
are missing kilobytes are the default.
It is very easy to change it and also is easy to make parser to not
require spaces between value and units.
But a problem
Hi Amos,
Amos Jeffries wrote:
I just spent the afternoon going over Christos full patch for
squid3-largeobj and only found a few very minor things. Though I still
don't know squid well enough to tell if there is anything missed out.
Did you use it to download large files? Did you do some
Hi ,
Henrik Nordstrom wrote:
hno 2007/08/13 12:25:14 MDT
Modified files:
src HttpHdrContRange.cc Makefile.in
MemObject.cc access_log.cc cache_cf.cc
client_side.cc client_side_reply.cc
Hi Guido ,
Guido Serassio wrote:
I have learned at university (more than 15 years ago ...) Assembler,
Fortran, C and Pascal, but never C++. or any similar language.
Sometimes I am feeling to old to start thinks too, but Guido if you are
thinking like that now, what are we going to do after 15
Hi Amos,
Amos Jeffries wrote:
One of them was unsafe use of a variable typed 'size_t' setting up
StoreIOBUffer local variable
The constructor using it is:
StoreIOBuffer(size_t aLength, int64_t anOffset, char *someData) :
length (aLength), offset (anOffset), data (someData)
Hi all,
Alex Rousskov wrote:
The primary idea behind RC1 is to bring in users who are ignoring PRE
releases because there were so many PREs. We need more testers than a
handful of folks running PREs on busy sites.
RC1 release to attract testers is a good idea. The only comment I have
is that
Hi Forest,
JXu wrote:
Hi
I installed Squid 3.0 and c-icap server. It works find and I made srv_clamav
work.
My question is how can I make the other service srv_echo and srv_url_check
work?
Just change the icap_service configuration parameter in your squid.conf
file to point to the
Alex Rousskov wrote:
My understanding is that Squid3 supports no more than one ICAP service
per message. If you can apply one service to the HTTP request and
another service to the response, then you can have up to two ICAP
services per transaction.
Does Squid2 support multiple ICAP
Hi Rob,
Robert Collins wrote:
Whats this summer you speak of?
I was speaking for Greek summer, the period of the year in Greece with
warm sunny days and better evenings, drinking wine, bears and ouzo near
the sea.
But, this summer was strange men, the sun looked sick behind the smoke
of
Hi Forest,
Alex has right here, squid3 does not support more than one service per
request or response.
The icap_class configuration parameter does not complains if you put
more than one services per request/response but only the first of them
will be used.
The same if you use multiple
Hi all,
At the squid3 download page
(http://www.squid-cache.org/Versions/v3/3.0/) the squid-3.0.PRE7 link
points to the squid-3.0.PRE5 Release Notes
(http://www.squid-cache.org/Versions/v3/3.0/squid-3.0.PRE5-RELEASENOTES.html)
--
Christos
Loadable dynamics modules maybe are not so important for existing
features of squid3 (HTCP,ICAP or SNMP), but they are important to allow
people/companies to extend squid.
The eCAP interface sounds really a good idea. Also maybe there are
others parts of squid which can extended in such way (eg
Oops.. I just saw that I sent this mail to squid-cvs mailing list :-(
Sorry .
Henrik Nordstrom wrote:
Forwarded Message
From: Tsantilas Christos [EMAIL PROTECTED]
To: Henrik Nordstrom [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: cvs commit: squid3/src
Hi Henrik,
Under a branch I am planning to work at the sourceforge CVS repository
I want to move files from one directory to an other.
Should I try to preserve cvs history of these files? I think just a copy
of the corresponding history file (file.c,v) to the new location will do
the work.
Do we
/TextException.cc and
src/ICAP/TextException.h should moved under the src/ directory.
But also it is good to keep their cvs history.
Is there any way?
Regards,
Christos
Tsantilas Christos wrote:
Hi Henrik,
Under a branch I am planning to work at the sourceforge CVS repository
I want to move files
Hi Amos,
Just a small patch to allow ICAP compile and run with the newly added
IPV6 changes.
First tests looks good.
Regards,
Christos
Amos Jeffries wrote:
I'm done now. Welcome to IPv6 everyone ;-)
...
Index: client_side_request.cc
Hi Adrian,
I commit some changes to async-calls branch and now compiles (but does
not link) without ICAP client enabled.
Currently you have to enable ICAP client to build async-calls. The
reason is that the src/ICAP/AsyncJob.o used in AsyncCalls but built only
as part of ICAP client library.
Adrian Chadd wrote:
On Sun, Dec 16, 2007, Tsantilas Christos wrote:
Currently you have to enable ICAP client to build async-calls. The
reason is that the src/ICAP/AsyncJob.o used in AsyncCalls but built only
as part of ICAP client library.
OK Adrian I fixed this too. You can build the async
Adrian Chadd wrote:
On Sun, Dec 16, 2007, Tsantilas Christos wrote:
Yes this is true. An AsyncCall class instanced for every async callback.
And the comm code is going to register one of these per comm events?
Yes.
Have you benchmarked what that'll do to performance? :)
Maybe has some
Hi Adrian,
As I am seeing squid3 spends time in EventScheduler::schedule method.
This method did not affected by the new AsyncCall code. Also this method
is similar with squid 2.6 eventAdd function.
The only I can say is that possibly we are scheduling a huge number of
events in squid3.
If the
Alex Rousskov wrote:
On Sat, 2007-12-15 at 12:56 +0200, Tsantilas Christos wrote:
void ICAPModXact::inheritVirginProperties(HttpRequest newR, const
HttpRequest oldR) {
newR.client_addr = oldR.client_addr;
-newR.client_port = oldR.client_port;
-
newR.my_addr = oldR.my_addr
Hi Robert,
Which are the required steps from developers?
Will we open our computers a morning and find all our development
branches in the new system :-) ?
What about the sourceforge developers repository? Will be hosted in the
squid main server?
Regards,
Christos
PS. I am only use cvs and
OK, this is good, we will have time to learn the new system.
Henrik Nordström wrote:
fre 2007-12-28 klockan 16:16 +0200 skrev Tsantilas Christos:
Hi Robert,
Which are the required steps from developers?
Will we open our computers a morning and find all our development
branches in the new
Robert Collins wrote:
What about the sourceforge developers repository?
Because bzr is natively distributed we don't need to have a dedicated
developers repository like we have with CVS - anyone using bzr will get
their own copy of the repository automatically; they can commit there as
Hi Rob,
The first feeling is good. I like it.
In general the idea of decentralized repositories looks good.
In INSTALL file of bzr says that requires python 2.4. I am using it with
python 2.5 and looks OK. Is the python version a problem?
Is the bazaar repository currently auto-synchronized
Hi Henrik,
It is not a cbdata problem.
An example is in the HttpStateData::sendComplete method which is going
to execute an commSetTimeout(fd ...)
Now there are cases in which this method scheduled for execution
sometime in the future but before it is executed the squid code closes
the fd
Adrian Chadd wrote:
.. I read that as the code is broken and needs to be fixed.
I think not so broken because there are solutions or workarounds off the
problems.
I think the last changes fix the problem (however I want to look more on
this to be sure there are not any other problems).
Adrian Chadd wrote:
On Sun, Jan 06, 2008, Tsantilas Christos wrote:
Adrian Chadd wrote:
.. I read that as the code is broken and needs to be fixed.
I think not so broken because there are solutions or workarounds off the
problems.
I think the last changes fix the problem (however I want
Alex Rousskov wrote:
On Sat, 2008-01-05 at 13:05 +0200, Tsantilas Christos wrote:
...
I suggest removing break-blocks both because of the above bug and
because it is trying to detect unrelated blocks, classes, etc. which
smells too much like AI to me.
The --brackets=linux (-l) option
The problem was different:
With classic comm code of squid3 when the comm_close for a fd called then:
1) fd marked as closing, read and write handlers called with
COMM_ERR_CLOSING
2) comm_close handlers called
3) the fd closed and the fdc_table[fd] initialized.
Using async calls (current
1 - 100 of 666 matches
Mail list logo
