15:06:46 <bcoca> #startmeeting ansible core public irc meeting
15:06:46 <zodbot> Meeting started Thu Apr 11 15:06:46 2019 UTC.
15:06:46 <zodbot> This meeting is logged and archived in a public location.
15:06:46 <zodbot> The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:06:46 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:06:46 <zodbot> The meeting name has been set to 'ansible_core_public_irc_meeting'
15:06:59 <bcoca> #topic https://github.com/ansible/ansible/issues/54412
15:07:16 <bcoca> how do we deal with warnings/errors in apis that a lookup uses
15:07:18 <bcoca> ?
15:14:12 <cyberpear> is it a question of "how to do" or "what to do"?
15:18:13 <bcoca> well, what first, how 2nd
15:20:31 <cyberpear> ignore="no warnings" warn="one warning" strict="failure"
15:20:37 <cyberpear> the request in the ticket seems reasonable to me
15:21:21 <cyberpear> otherwise, should 'warn=Undefined' that can be caught w/ default()?
15:21:29 <bcoca> but those are warnings from the lookup, does not handle other warnings from other systems
15:21:41 <bcoca> hmm, that might be nice feature
15:23:23 <cyberpear> that way you avoid the need of 'strict'
15:23:38 <cyberpear> the question becomes whether to still output the warning that filewas not found
15:24:25 <bcoca> would require lookups to always intercept all possible warnings from apis they call
15:24:49 <cyberpear> maybe that's asking too much
15:24:49 <bcoca> and ansible warnings are NOT using python warnings, so no clue on even how to approach that
15:29:56 <cyberpear> I think "warnings to screen" is not too high a price to pay in the short term, as long as things function as desired otherwise.
15:31:37 <bcoca> well, anyone  else have opinion/ideas or just the 2 of us in this meeting?
15:34:38 * bcoca needs to buy crickets
15:34:47 * cyberpear chirp chirp chirp
15:35:10 <bcoca> k, since no where near quorum im just going to close meeting and hope tuesday has people showing up
15:35:14 <bcoca> #endmeeting