[Bug 69530] Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 --- Comment #4 from Remy Maucherat --- It does not show the request that causes this, so why are you certain it is caused by the stricter lock refresh behavior ? Please provide more details on the error. -- You are receiving this mail because

[Bug 69530] Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 --- Comment #3 from shekhar --- Edit in Office Functionality not working -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: d

[Bug 69530] Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 --- Comment #2 from shekhar --- Created attachment 39967 --> https://bz.apache.org/bugzilla/attachment.cgi?id=39967&action=edit Edit in office (WEBDAVSERVLET) 10.1.34 stop working snapshot -- You are receiving this mail because: You are the

Re: [Bug 69531] SPAM SPAM SPAM SPAM

2025-01-09 Thread Christopher Schultz
Chuck, QUADRUPLE SPAM! -chris On 1/9/25 12:52 PM, bugzi...@apache.org wrote: https://bz.apache.org/bugzilla/show_bug.cgi?id=69531 Chuck Caldarale changed: What|Removed |Added

[Bug 69531] SPAM SPAM SPAM SPAM

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69531 Chuck Caldarale changed: What|Removed |Added Resolution|--- |INVALID Summary|SPAM SPAM

[Bug 69531] SPAM SPAM SPAM

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69531 Christopher Schultz changed: What|Removed |Added Summary|https://godseye.in/ |SPAM SPAM SPAM -- You are recei

[Bug 69531] New: https://godseye.in/

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69531 Bug ID: 69531 Summary: https://godseye.in/ Product: Taglibs Version: unspecified Hardware: Macintosh OS: Mac OS X 10.1 Status: NEW Severity: normal

(tomcat) branch 9.0.x updated: Avoid caching bogus 0 content length

2025-01-09 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new f182b68b35 Avoid caching bogus 0 content length f182

(tomcat) branch 10.1.x updated: Avoid caching bogus 0 content length

2025-01-09 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new a037dee3c0 Avoid caching bogus 0 content length a0

(tomcat) branch 11.0.x updated: Avoid caching bogus 0 content length

2025-01-09 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 11.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/11.0.x by this push: new 4efa851446 Avoid caching bogus 0 content length 4e

(tomcat) branch main updated: Avoid caching bogus 0 content length

2025-01-09 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 80ae858419 Avoid caching bogus 0 content length 80ae85

Re: (tomcat) branch main updated: Refactor so the buffered data is used directly rather than copied

2025-01-09 Thread Mark Thomas
On 09/01/2025 14:53, Rémy Maucherat wrote: On Thu, Jan 9, 2025 at 3:17 PM Mark Thomas wrote: My current plan is to create InputBuffer with bb set to a zero length ByteBuffer and have recycle (re)set it to a zero length ByteBuffer. That avoids the NPEs, avoids retaining references unnecessar

(tomcat) branch main updated: Replace the unused buffer with a zero length, static instance.

2025-01-09 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new cb857a86a4 Replace the unused buffer with a zero leng

Re: (tomcat) branch main updated: Refactor so the buffered data is used directly rather than copied

2025-01-09 Thread Rémy Maucherat
On Thu, Jan 9, 2025 at 3:17 PM Mark Thomas wrote: > > On 09/01/2025 14:01, ma...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > > > markt pushed a commit to branch main > > in repository https://gitbox.apache.org/repos/asf/tomcat.git > > > > > > The f

[Bug 69419] Redundant code execution in nested ApplicationHttpRequest.setAttribute()

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69419 --- Comment #7 from John Engebretson --- This change reached production and had a greater-than-expected impact, totaling approximately 0.2% of cpu. I can't explain the gap but hypothesize the lack of recursion enabled inlining, which enables f

Re: (tomcat) branch main updated: Refactor so the buffered data is used directly rather than copied

2025-01-09 Thread Mark Thomas
On 09/01/2025 14:01, ma...@apache.org wrote: This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 1f417

(tomcat) branch main updated: Refactor so the buffered data is used directly rather than copied

2025-01-09 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 1f4175d65c Refactor so the buffered data is used dire

[Bug 69530] Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 Remy Maucherat changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Remy Mau

[Bug 69530] Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 shekhar changed: What|Removed |Added OS||All -- You are receiving this mail because:

[Bug 69530] New: Major different between 10.1.31 and 10.1.34 (class file doLock Method)

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69530 Bug ID: 69530 Summary: Major different between 10.1.31 and 10.1.34 (class file doLock Method) Product: Tomcat 10 Version: 10.1.34 Hardware: PC Status: NEW

[Bug 69527] Resource missing caused by mishandling of the cachedContentLength value in tomcat cache

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69527 --- Comment #8 from Remy Maucherat --- Created attachment 39966 --> https://bz.apache.org/bugzilla/attachment.cgi?id=39966&action=edit Proposed patch -- You are receiving this mail because: You are the assignee for the bug.

[Bug 69527] Resource missing caused by mishandling of the cachedContentLength value in tomcat cache

2025-01-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69527 --- Comment #7 from Remy Maucherat --- (In reply to Vigneshwaran N from comment #5) > (In reply to Remy Maucherat from comment #2) > > This reads like an AI generated report ... > > Hi Remy, the above content that you are mentioned as AI gener