Report information
The Basics
Id:
45676
Status:
rejected
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Requestors:
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Wed, 02 Aug 2017 23:11:54 -0400
Updated:Wed, 09 Aug 2017 06:54:35 -0400
Closed:Thu, 03 Aug 2017 12:08:42 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

To: bind-suggest@isc.org
From: "Mukund Sivaraman" <muks@isc.org>
Date: Thu, 3 Aug 2017 08:41:46 +0530
Subject: Include fctx in fetchevent
When a fetchevent gets delivered, the fetch context associated with it (which contains a lot of useful information such as fctx->rmessage) isn't available to the callback. This is inconvenient for debugging purposes, and we should include this pointer within the fetchevent struct. Mukund
Date: Thu, 3 Aug 2017 21:38:07 +0530
To: "Mukund Sivaraman via RT" <bind9-public@isc.org>
Subject: Re: [ISC-Bugs #45676] Include fctx in fetchevent
From: "Mukund Sivaraman" <muks@isc.org>
> When a fetchevent gets delivered, the fetch context associated with it > (which contains a lot of useful information such as fctx->rmessage) > isn't available to the callback. This is inconvenient for debugging > purposes, and we should include this pointer within the fetchevent > struct. It looks like this is included as fetchevent->fetch->private, so rejecting this ticket. Mukund