René's URL Explorer Experiment


Title: Proposal: replace asyncio with anyio · Issue #166 · graphql-python/graphql-core · GitHub

Open Graph Title: Proposal: replace asyncio with anyio · Issue #166 · graphql-python/graphql-core

X Title: Proposal: replace asyncio with anyio · Issue #166 · graphql-python/graphql-core

Description: Yesterday I added the pull request #165 to start a discussion on supporting the trio ecosystem, preferably using anyio. @Cito invited me to create an issue as a place for discussing the implications of such a step. I hope to get some fee...

Open Graph Description: Yesterday I added the pull request #165 to start a discussion on supporting the trio ecosystem, preferably using anyio. @Cito invited me to create an issue as a place for discussing the implication...

X Description: Yesterday I added the pull request #165 to start a discussion on supporting the trio ecosystem, preferably using anyio. @Cito invited me to create an issue as a place for discussing the implication...

Opengraph URL: https://github.com/graphql-python/graphql-core/issues/166

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Proposal: replace asyncio with anyio","articleBody":"Yesterday I added the pull request #165 to start a discussion on supporting the trio ecosystem, preferably using anyio. @Cito invited me to create an issue as a place for discussing the implications of such a step. \r\n\r\n**I hope to get some feedback from you wether you think supporting trio in graphql-core is a good idea.** My reasoning and approach for the pull request is outlined below\r\n\r\n# The basics\r\n\r\n## What is structured concurrency and trio?\r\n\r\nThis is best answered by the trio project, I can recommend reading their [documentation](https://trio.readthedocs.io/en/stable/), especially their [design principles](https://trio.readthedocs.io/en/stable/design.html). There are also a few blog posts that shed light on the reasoning behind trio, e.g. [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/) and [cancellation](https://vorpus.org/blog/timeouts-and-cancellation-for-humans/).\r\n\r\nBasically, trio implements an event loop for asynchronous code execution, just like the asyncio standard library. However, there are some important differences. The following two have probably the most impact:\r\n\r\n1.) You cannot start async tasks whenever you want. All tasks have a parent, if you want to start multiple coroutines, you need a `Nursery`. The nursery guarantees that all tasks are done when exiting its scope. This makes it much easier to reason about async code: If you await an async function, there will be no background tasks running when the function returns. Only exception: passing in a nursery explicitely to start the tasks. Then the tasks may run until the end of the nursery scope.\r\n\r\n2.) Level-based cancellation. Cancellation is done via scopes. Once a scope is cancelled, all its children scopes are cancelled as well. It also stays cancelled: After cancellation, any checkpoint (see trio docs for details, basically any call into trio like `trio.sleep`) raises `Cancelled`. This makes it easier to get cancellation right. Asyncio only ever sends one `CancelledError`. It is often caught with good intentions but not raised again in some circumstances. \r\n\r\nThese two changes alone make it much easier to write correct asynchronous code.\r\n\r\n## What is anyio?\r\n\r\nThe [anyio project](https://anyio.readthedocs.io/en/stable/) Allows to use the same structured concurrency and cancellation behavior as trio (trio's `Nursery` is a `TaskGroup`, etc.). However, it can run on two different backends: trio and standard asyncio.\r\n\r\nThis makes anyio ideal for two use cases: \r\n  1.) Iteratively replacing asyncio code with anyio code. At any point the code should still work, even if only partially replaced. \r\n  2.) Writing libraries that support trio and asyncio\r\n\r\n# Why support trio in graphql-core?\r\n\r\nIf you ever had to create or work in a large scale asynchronous Python application, you will probably have spent hours fixing tasks that should have closed but are instead still blocking some resource or preventing the event loop shutdown. Mostly in your own code, sometimes in third-party libraries. The trio (and anyio) way of tackling asynchronous code can help tremendously when using asynchronous code at a larger scale.\r\n\r\nThe graphql-core library is well-tested and takes great care to handle asynchronous tasks and cancellation correctly. Therefore, this change will have no benefit for the graphql-core codebase, it will not make it simpler or easier to understand. However, it allows users to make the choice between asyncio and trio, opening up to the growing trio ecosystem. This could also potentially increase usage of the graphql-core library. Both are worthy goals in my opinion.\r\n\r\n# How to do it?\r\n\r\nIf I have you convinced that supporting trio is not a bad idea in itself, the question comes down to: How to do that in graphql-core without too many downsides?\r\n\r\n## Why Anyio?\r\n\r\nIf you want to avoid additional libraries, you can potentially support trio by adding a lot of  if-else blocks to your code, using either an asyncio or a trio implementation. This has a few downsides:\r\n - It is difficult to ensure that both implementations behave the same when changing the event loop implementation.\r\n - Code duplication in these blocks\r\n - You are probably going to reinvent the anyio library, at least partially.\r\n\r\nAnother option would be [trio-asyncio](https://github.com/python-trio/trio-asyncio), which runs two event loops and contains tools to stitch it together. However, its documentation already states it is intended for applications that need to use libraries from trio and asyncio. It seems more like a stopgap solution if you really need to combine two libraries that have conflicting requirements.\r\n\r\nThat is why I used the anyio library in the pull request. It makes it easier to write code that works with asyncio and trio. Anyio is also a promise to users of the graphql-core library: The library is built using structured concurrency, you can be sure that tasks are cleaned up correctly. Of course there is one major downside: graphql-core now requires the anyio library.\r\n@Cito already expressed concern about adding an additional library:\r\n - Support may be dropped in the future.\r\n - It might introduce new problems\r\n\r\nRegarding support I was sceptical to include anyio in my own code as well. However, looking at my dependency tree I found that I was inadvertently using it: Starlette can run on asyncio and trio, using anyio (https://github.com/encode/starlette/pull/1157). As Starlette is rather widespread I believe there is sufficient interest to keep anyio going. Maybe you know additional libraries that rely on anyio? If enough libraries rely on it, it is unlikely to simply disappear.\r\n\r\nWorst case scenario: anyio support is dropped and their is no replacement. In this case you could decide to drop trio support again, at the cost of angry users, who want to have a graphql server with their trio event loop.\r\n\r\nIntroducing new bugs when using anyio is of course possible. As the anyio API is very close to trio, I expect it to work rather well with trio. The trio backend in anyio is often only a thin wrapper around the corresponding trio object (see https://github.com/agronholm/anyio/blob/master/src/anyio/_backends/_trio.py).\r\n\r\nHowever, emulating the trio behavior in asyncio code is more difficult. Especially since the cancellation works differently. There might very well cases when things do not work as expected when including it here.\r\n\r\nThe only way to get some ease of mind would be sufficient tests. While my pull request passes the graphql-core tests, I did not specifically test for incompatibilities. You can help out here. **If you are using graphql-core in your project and would like to see trio support**: take my pull request and test it. See if it introduces any problems with existing code. If this issue gathers enough interest I might be motivated to write additional tests explicitely searching for changed behavior and incompatibilities.\r\n\r\n## Performance considerations\r\n\r\nUsing anyio instead of asyncio can potentially cost performance, as it is an additional wrapper on top of asyncio (or trio). The question are: How much? Is it worth it?\r\n\r\nThe Starlette pull request (https://github.com/encode/starlette/pull/1157) found a 4.5% drop in their performance score, but this has hardly any meaning for a different library.\r\n\r\ngraphql-core itself has only one async benchmark. I included benchmarks in the pull request, I could not see a performance impact. \r\nBut standard deviation was rather large, and a single benchmark is hardly enough here. The best way forward would be additional benchmarks. Again, if this issue gathers enough interest I might be motivated to put some more work in.\r\n\r\n## The fate of SimplePubSub?\r\n**Edit: SimplePubSub is not part of the official API, we can just change it keep the tests similar to their GraphQL.js counterpart, see [comment](https://github.com/graphql-python/graphql-core/issues/166#issuecomment-1086924727)**\r\nThis discussion is only relevant if we actually want to go through with it and adopt anyio. But since it cost most of the time when porting graphql-core to anyio, I will include it here.\r\n\r\nBasically, I did not port SimplePubSub to anyio. Its API is not compatible. Instead of changing its API I added a warning about its reliance on asyncio and replaced its usage in the test code with a completely new implementation called `MemoryObjectBroadcastStream`. Its interface is in line with the anyio streams and works well in the test suite.\r\n\r\nIt would also be possible to change the SimplePubSub API or come up with something completely different. SimplePubSub is not advertised much in the documentation and its description is rather sparse. I would be interested to hear if this class is actually used much outside of graphql-core and in which way.\r\n\r\n## Exception groups\r\n\r\nAgain, only a relevant discussion if anyio is actually used. Generally, trio supports a `MultiError` (`ExceptionGroup` in anyio), which does exactly as advertised: If a `Nursery` (`TaskGroup`) has multiple tasks ending with an exception it collects them and raises all of them. These are difficult to handle and would break the graphql-core API if propagated to the caller. Handling these cleanly in trio ultimately lead to the new `except*` language feature in Python 3.11 (see https://peps.python.org/pep-0654/). That is, handling them in Python versions \u003c3.11 is annoying.\r\n\r\nAsyncio uses a different approach in its `gather` function: Raise the first exception.\r\nTo avoid unnecessary surprises for users of the graphql-core library I opted for handling all exception groups internally in the pull request. Only one of the errors is actually raised to the caller. Of course, we might loose some information here, just as we do with `asyncio.gather`. Any opinions on this matter?\r\n\r\n\r\n## Python version\r\nUsing anyio would bump the minimum Python version from 3.6.0 to 3.6.2. @Cito plans to drop support for 3.6 anyway, so this does not seem much of an issue. But it would probably be a good idea to delay the inclusion of anyio until Python 3.6 support is dropped.\r\n","author":{"url":"https://github.com/valgarf","@type":"Person","name":"valgarf"},"datePublished":"2022-04-03T16:24:39Z","url":"https://github.com/graphql-python/graphql-core/issues/166"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:eaaa5177-cc00-fdca-9a2f-91ac5fb411bc
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idE968:2F2EB9:18EB6B3:20161E7:6AFFB832
html-safe-noncef055fd3481d3c6a512b34a7c12056567c14b066c57d201022b6f9ecb05141add
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFOTY4OjJGMkVCOToxOEVCNkIzOjIwMTYxRTc6NkFGRkI4MzIiLCJ2aXNpdG9yX2lkIjoiNDE0OTUzNDU5ODQzNjQ2ODc4NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmacbe3068d737bdf489d0180261c7475051772a9d42256ea8bccd929bfe9513c5ee
hovercard-subject-tagissue:1190977012
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/graphql-python/graphql-core/166/issue_layout
twitter:imagehttps://opengraph.githubassets.com/e2a9ea60afe8a52df5a1e6c4cfc4a6a2dedcbffb0d3daa1ea7102dd0b418011f/graphql-python/graphql-core/issues/166
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/e2a9ea60afe8a52df5a1e6c4cfc4a6a2dedcbffb0d3daa1ea7102dd0b418011f/graphql-python/graphql-core/issues/166
og:image:altYesterday I added the pull request #165 to start a discussion on supporting the trio ecosystem, preferably using anyio. @Cito invited me to create an issue as a place for discussing the implication...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamevalgarf
hostnamegithub.com
expected-hostnamegithub.com
None7e461843db1c75e40d788c5cfd440d0e4ae1271cf19e06a798d0e7feb2d708f3
turbo-cache-controlno-preview
go-importgithub.com/graphql-python/graphql-core git https://github.com/graphql-python/graphql-core.git
octolytics-dimension-user_id15002022
octolytics-dimension-user_logingraphql-python
octolytics-dimension-repository_id143207933
octolytics-dimension-repository_nwographql-python/graphql-core
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id143207933
octolytics-dimension-repository_network_root_nwographql-python/graphql-core
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
released29a6a99861646939301302fab465f9f123b4773
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/graphql-python/graphql-core/issues/166#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fgraphql-python%2Fgraphql-core%2Fissues%2F166
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fgraphql-python%2Fgraphql-core%2Fissues%2F166
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=graphql-python%2Fgraphql-core
Reloadhttps://github.com/graphql-python/graphql-core/issues/166
Reloadhttps://github.com/graphql-python/graphql-core/issues/166
Reloadhttps://github.com/graphql-python/graphql-core/issues/166
graphql-pythonhttps://github.com/graphql-python
graphql-corehttps://github.com/graphql-python/graphql-core
Codehttps://github.com/graphql-python/graphql-core
Issues24 (24)https://github.com/graphql-python/graphql-core/issues
Pull requests3 (3)https://github.com/graphql-python/graphql-core/pulls
Actionshttps://github.com/graphql-python/graphql-core/actions
Projectshttps://github.com/graphql-python/graphql-core/projects
Security and quality3 (3)https://github.com/graphql-python/graphql-core/security
Insightshttps://github.com/graphql-python/graphql-core/insights
https://github.com/graphql-python/graphql-core
New issuehttps://github.com/login?return_to=https://github.com/graphql-python/graphql-core/issues/166
New issuehttps://github.com/login?return_to=https://github.com/graphql-python/graphql-core/issues/166
Proposal: replace asyncio with anyiohttps://github.com/graphql-python/graphql-core/issues/166#top
discussionNeeds more discussionhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22discussion%22
help wantedExtra attention is neededhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22help%20wanted%22
investigateNeeds investigaton or experimentationhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22investigate%22
v3.3https://github.com/graphql-python/graphql-core/milestone/10
https://github.com/valgarf
valgarfhttps://github.com/valgarf
on Apr 3, 2022https://github.com/graphql-python/graphql-core/issues/166#issue-1190977012
#165https://github.com/graphql-python/graphql-core/pull/165
@Citohttps://github.com/Cito
documentationhttps://trio.readthedocs.io/en/stable/
design principleshttps://trio.readthedocs.io/en/stable/design.html
structured concurrencyhttps://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
cancellationhttps://vorpus.org/blog/timeouts-and-cancellation-for-humans/
anyio projecthttps://anyio.readthedocs.io/en/stable/
trio-asynciohttps://github.com/python-trio/trio-asyncio
@Citohttps://github.com/Cito
Kludex/starlette#1157https://github.com/Kludex/starlette/pull/1157
https://github.com/agronholm/anyio/blob/master/src/anyio/_backends/_trio.pyhttps://github.com/agronholm/anyio/blob/master/src/anyio/_backends/_trio.py
Kludex/starlette#1157https://github.com/Kludex/starlette/pull/1157
commenthttps://github.com/graphql-python/graphql-core/issues/166#issuecomment-1086924727
https://peps.python.org/pep-0654/https://peps.python.org/pep-0654/
@Citohttps://github.com/Cito
https://github.com/Cito
Citohttps://github.com/Cito
on Apr 3, 2022https://github.com/graphql-python/graphql-core/issues/166#issuecomment-1086924727
@valgarfhttps://github.com/valgarf
https://github.com/valgarf
valgarfhttps://github.com/valgarf
on Apr 4, 2022https://github.com/graphql-python/graphql-core/issues/166#issuecomment-1087765988
@Citohttps://github.com/Cito
Citohttps://github.com/Cito
help wantedExtra attention is neededhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22help%20wanted%22
discussionNeeds more discussionhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22discussion%22
investigateNeeds investigaton or experimentationhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22investigate%22
on Apr 4, 2022https://github.com/graphql-python/graphql-core/issues/166#event-6365333354
Citohttps://github.com/Cito
v3.3https://github.com/graphql-python/graphql-core/milestone/10
on Apr 4, 2022https://github.com/graphql-python/graphql-core/issues/166#event-6365334239
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Sep 16, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3297888153
@valgarfhttps://github.com/valgarf
#242https://github.com/graphql-python/graphql-core/pull/242
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Sep 17, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3301988612
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Sep 17, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3302283618
https://github.com/valgarf
valgarfhttps://github.com/valgarf
on Nov 1, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3476757809
@agronholmhttps://github.com/agronholm
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Nov 1, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3476761855
https://github.com/valgarf
valgarfhttps://github.com/valgarf
on Nov 1, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3476774948
@agronholmhttps://github.com/agronholm
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Dec 1, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3596987382
@Citohttps://github.com/Cito
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Dec 5, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3617263808
@Citohttps://github.com/Cito
https://github.com/Cito
Citohttps://github.com/Cito
on Dec 5, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3617391141
@agronholmhttps://github.com/agronholm
https://github.com/Cito
Citohttps://github.com/Cito
on Dec 28, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3694930956
@agronholmhttps://github.com/agronholm
https://github.com/agronholm
agronholmhttps://github.com/agronholm
on Dec 28, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3695098184
https://github.com/Cito
Citohttps://github.com/Cito
on Dec 28, 2025https://github.com/graphql-python/graphql-core/issues/166#issuecomment-3695134260
Sign up for freehttps://github.com/signup?return_to=https://github.com/graphql-python/graphql-core/issues/166
Sign in to commenthttps://github.com/login?return_to=https://github.com/graphql-python/graphql-core/issues/166
discussionNeeds more discussionhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22discussion%22
help wantedExtra attention is neededhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22help%20wanted%22
investigateNeeds investigaton or experimentationhttps://github.com/graphql-python/graphql-core/issues?q=state%3Aopen%20label%3A%22investigate%22
v3.3No due datehttps://github.com/graphql-python/graphql-core/milestone/10
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.