Meta tags:
description= It s very hard to reproduce, we found the problem because we have a 60s timeout for our web server that we kept busting, even with email-validator s default 15s timeout. Disabling check_availability solved our problem. The problem The pr...;
Headings (most frequently used words):
commented, on, mar, 2023, the, navigation, metadata, footer, joshdata, nmenardg, keeper, 22, dns, resolver, can, run, for, longer, than, given, timeout, 101, problem, solution, menu, repository, description, activity, issue, actions, 18, 20, assignees, labels, projects, milestone, relationships, development,
Text of the page (most frequently used words):
the (35), timeout (17), github (16), for (16), and (15), mar (9), 2023 (9), actions (8), that (7), issue (7), #resolver (7), #joshdata (7), you (6), can (6), time (6), your (6), would (6), dns (6), dnspython (6), call (6), with (6), code (6), security (5), copilot (5), sign (5), more (5), problem (5), nmenardg (5), keeper (5), than (5), longer (5), this (4), projects (4), have (4), all (4), out (4), commented (4), what (4), signal (4), resolve (4), see (4), run (4), email (4), validator (4), support (4), navigation (3), open (3), labels (3), because (3), deliverability (3), solution (3), using (3), could (3), https (3), com (3), python (3), copy (3), link (3), 101 (3), given (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), reload (3), developers (3), changelog (3), customer (3), enterprise (3), grade (3), features (3), build (3), community (2), status (2), footer (2), pull (2), requests (2), development (2), milestone (2), one (2), metadata (2), but (2), might (2), calls (2), except (2), exception (2), first (2), query (2), end (2), checks (2), get (2), total (2), times (2), each (2), owner (2), work (2), email_validator (2), next (2), gets (2), author (2), some (2), only (2), also (2), here (2), suggestion (2), stackoverflow (2), does (2), sleep (2), our (2), new (2), insights (2), repository (2), signed (2), universe (2), training (2), integrations (2), stories (2), center (2), documentation (2), learn (2), business (2), fixes (2), products (2), secret (2), perform, action, not, share, personal, information, manage, cookies, contact, docs, privacy, terms, 2026, inc, app, branches, none, yet, relationships, assigned, assignees, comment, already, account, join, conversation, free, option, little, tricky, implement, provided, caller, reducing, future, mangle, original, value, since, block, around, queries, should, four, complete, just, under, without, timing, sorry, suggesting, head, toward, raise, catching, hacky, fix, give, actually, want, baseexception, measure, left, after, every, allocate, remaining, any, following, takes, 10s, divide, potential, closed, seems, called, potentially, same, due, solutions, side, noanswer, validate_email_deliverability, testing, today, caveats, works, single, thread, programs, interfere, other, sigalrm, rthalley, 913, yeah, agreed, sounds, like, better, made, library, rather, curious, hear, find, activity, try, implementing, write, back, news, package, pnpnpn, decorator, interrupt, process, 494273, while, debugging, goes, through, loop, between, means, doesn, interrupted, thus, blob, main, l40, domain, dns_resolver, response, lies, within, disabling, solved, check_availability, very, hard, reproduce, found, 60s, web, server, kept, busting, even, default, 15s, body, opened, description, items, wiki, issues, message, dismiss, alert, switched, accounts, appearance, settings, search, pricing, event, talks, workshops, partners, about, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, add, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, source, latest, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, environments, codespaces, analysis, enforcement, automation, ship, coding, agent, tasks, automated, hosting, review, collaboration, platform, menu, skip, content,
Text of the page (random words):
dns resolver can run for longer than the given timeout issue 101 joshdata python email validator github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message joshdata python email validator repository navigation code issues 12 12 pull requests 5 5 actions projects wiki security and quality insights more items dns resolver can run for longer than the given timeout 101 new issue copy link new issue copy link open open dns resolver can run for longer than the given timeout 101 copy link description nmenardg keeper opened on mar 17 2023 issue body actions it s very hard to reproduce we found the problem because we have a 60s timeout for our web server that we kept busting even with email validator s default 15s timeout disabling check_availability solved our problem the problem the problem lies within response dns_resolver resolve domain mx https github com joshdata python email validator blob main email_validator deliverability py l40 while debugging what i can see is that the resolver goes through a loop and only checks the timeout between calls it also does some time sleep that means that if a call or a sleep is longer than the timeout it doesn t get interrupted and can thus run for longer the solution using signal we could interrupt the process see https stackoverflow com a 494273 this package does it https github com pnpnpn timeout decorator i ll try implementing the stackoverflow suggestion on my end and write back with news activity joshdata commented on mar 18 2023 joshdata on mar 18 2023 owner more actions this sounds like it would be a suggestion better made for the dnspython library rather than here but i would be curious to hear what you find out nmenardg keeper commented on mar 20 2023 nmenardg keeper on mar 20 2023 author more actions yeah agreed here s the issue in dnspython rthalley dnspython 913 i m testing the signal solution today some caveats it only works on single thread programs and could interfere with other code also using signal sigalrm nmenardg keeper commented on mar 22 2023 nmenardg keeper on mar 22 2023 author more actions i closed the issue in dnspython the problem seems to be that in deliverability validate_email_deliverability resolver resolve is called potentially 4 times with the same timeout due to except dns resolver noanswer the solutions i see on your side could be divide timeout in 4 so each of the 4 potential resolve call gets 1 4 of the total timeout measure time left after every resolve call and allocate the remaining time if any to the following call a e g first call takes 5s next call gets a timeout of 15 5 10s for my solution using signal to work i ll have to raise a baseexception because dnspython is catching exception or a hacky fix would be to give email_validator a timeout of 1 4 of what i actually want joshdata commented on mar 22 2023 joshdata on mar 22 2023 owner more actions ah sorry for suggesting you head toward dnspython since the except block for dns exception timeout is around all of the dns queries the first query to time out should end the deliverability checks so to get a total time that s four times the timeout each query would have to complete in just under the timeout without timing out your option 2 would be ok for me but it might be a little tricky to implement because the resolver might be provided by the caller and reducing the timeout in future calls would mangle the original value sign up for free to join this conversation on github already have an account sign in to comment metadata metadata assignees no one assigned labels no labels no labels projects no projects milestone no milestone relationships none yet development no branches or pull requests issue actions open in github copilot app footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|