# issue tracker Published articles for issue tracker. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kotlin 2.4.20 Released DevFeed: [Kotlin 2.4.20 Released]() Original publisher: [Read original article]() Author: Daniel Csorba Published: 2026-09-07T11:30:57Z Content type: release Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog](), [The JetBrains Blog]() Topics: [releases](), [Command-line interface](), [Android Studio](), [IntelliJ IDEA]() Tags: [android-studio](), [command-line](), [features](), [github](), [gradle](), [intellij](), [issue-tracker](), [kotlin](), [release](), [releases](), [swift](), [testing](), [wasm](), [youtrack]() ### AI overview Kotlin 2.4.20 adds standard-library, compiler, build-tool, Kotlin/Native, Kotlin/Wasm, and Kotlin/JS updates. The article also explains how to update Kotlin in supported IDEs or obtain the command-line compiler. ### Source excerpt The Kotlin 2.4.20 release is out! Here are the main highlights: For the complete list of changes, see What's new in Kotlin 2.4.20 or the release notes on GitHub. How to install Kotlin 2.4.20 The latest version of Kotlin is included in the latest versions of IntelliJ IDEA and Android Studio. To update to the [...] ## How we closed 1,500 GitHub issues in one month DevFeed: [How we closed 1,500 GitHub issues in one month]() Original publisher: [Read original article]() Author: Marcos Hernanz Published: 2026-09-04T04:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [GitHub Issues](), [Next.js](), [AI-assisted coding](), [issue tracker](), [Maintainers](), [bug]() Tags: [agent](), [ai](), [bug](), [github-issues](), [issue-tracker](), [maintainers](), [next-js](), [sandbox](), [vercel]() ### AI overview The Next.js team describes using an AI research agent to help maintainers review an issue backlog, close outdated reports, and retain issues that still matter. ### Source excerpt How the Next.js team used an agent to research old reports and work through the issue backlog. ## Treating Issue Bodies as Untrusted Input DevFeed: [Treating Issue Bodies as Untrusted Input]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-14T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [prompt injection](), [GitHub](), [JSON Feed](), [Structured-data](), [issue tracker]() Tags: [agents](), [github](), [implementation](), [issue-tracker](), [json](), [llm](), [prompt-injection](), [schema](), [security](), [test]() ### AI overview The article explains how GitHub issue bodies can carry prompt injection attacks when an agent treats public input as instructions. It recommends fencing untrusted text, clearly labeling it, constraining model output to a fixed JSON action schema, and testing the validation boundary without a live model. ### Source excerpt Prompt injection via GitHub issue bodies: fence untrusted text and accept model output only as a fixed JSON action schema, tested without a model. ## The Label as Contract: Consent and Priority as the Whole Queue DevFeed: [The Label as Contract: Consent and Priority as the Whole Queue]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-07-28T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [issue tracker](), [audit trail](), [coding]() Tags: [agents](), [audit-trail](), [consent](), [fifo](), [issue-tracker](), [priority](), [security]() ### AI overview The article argues that an autonomous coding agent should act only on issues carrying a specific human-applied label. Free-form issue content is unauthenticated and cannot establish consent or priority; label actions provide an independent audit trail, and priority should be derived from label transitions. ### Source excerpt agent-ready label as the only consent gate for a coding agent: FIFO order by label time and a re-read-then-swap claim so two runs never share an issue. ## Triaging at Scale: How the Gradle Team Handles Issues and Pull Requests DevFeed: [Triaging at Scale: How the Gradle Team Handles Issues and Pull Requests]() Original publisher: [Read original article]() Author: Vlad Chesnokov Published: 2026-07-16T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [issue tracker](), [GitHub](), [Automation](), [pull-requests]() Tags: [automation](), [bug](), [documentation](), [github](), [gradle](), [issue-tracker](), [pull-requests](), [usability]() ### AI overview The Gradle team explains how it triages GitHub issues and pull requests at scale. The article describes lessons from using and then removing stale-issue automation, the role of human review, and how issue reports help identify bugs, documentation gaps, and usability problems. ### Source excerpt Communities are at the heart of Gradle's success. Without their involvement, the build tool would not have the extensive feature set and wide use it has. And using the plural form is no mistake! While the user community is the largest, we also have a community of plugin authors that contribute to extending the capabilities of Gradle. A significant part of interactions between the Gradle team and those communities occurs via feature requests and bug reports using GitHub's issue tracker. Over the past years, we have improved how we handle those reports. We can now give them the attention they deserve and use them to help us improve the build tool across releases. In this post, we'll walk through how triage works today, the changes that got us here, and what you can do to help us help you when you report an issue. An iterative process Back in 2020, we introduced a stale bot to tackle our growing backlog of stale issues. Once it started closing issues, the community feedback was quick to arrive. The biggest complaint was that issues were closed automatically as stale, without a human from the engineering team ever weighing in. So we walked the automation back, step by step. First, we changed the stale bot to no longer close issues, only mark them stale and leave them open for the team to review. Then we reviewed all open issues carrying that label. With the backlog under control, we removed the stale bot for issues altogether. Later, we even re-triaged the closed stale issues that had at least one vote. Most turned out to be duplicates or already fixed. Today, no automation can silently close an issue. What's more, we don't miss any comments under closed issues: if somebody comments on a closed issue, it will be re-triaged. There are still around a thousand issues in our main repository closed by the stale bot. We don't plan to re-triage them, assuming they are obsolete. If the stale bot closed an issue you still care about, just leave a comment and we'll take another l ## 130 Release-Roadmap Issues, 818 Agent Runs: A Mid-Iteration Reality Check DevFeed: [130 Release-Roadmap Issues, 818 Agent Runs: A Mid-Iteration Reality Check]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-04-28T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [AI Agent](), [Claude](), [codex](), [Artificial Intelligence](), [issue tracker](), [Orchestration](), [Command-line interface](), [Graphs](), [Requirements]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [ai-agents](), [ai-coding](), [cli](), [code](), [eugene-petrenko](), [graph](), [issue-tracker](), [jonnyzzz](), [mcp](), [mcp-steroid](), [multi-agent](), [orchestration](), [pipeline](), [requirements](), [run-agent](), [tag-41199d53f463]() ### AI overview The article describes using a swarm of Claude, Codex, and Gemini agent CLIs to research 130+ release-roadmap issues and produce implementation specifications. The process used 818 agent runs over four days at an approximately $576 cost, followed by a mid-release comparison of the research with the team's actual work. ### Source excerpt We turned one release's roadmap -- 130+ umbrella-epic issues -- into fully-researched implementation specs using a swarm of three different agent CLIs (Claude, Codex, Gemini): 818 runs, ~155M+ tokens, ~$576, four days. Then, mid-release-cycle, we ran a snapshot to compare the research against reality -- with no expectation that anything was "done" yet. Here is the pipeline, the numbers, and the honest verdict. ## An open-source spec for orchestration: Symphony DevFeed: [An open-source spec for orchestration: Symphony]() Original publisher: [Read original article]() Author: Caleeeb - Follow Published: 2026-04-27T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Orchestration](), [AI-assisted coding](), [codex](), [Open Source](), [issue tracker](), [pull-requests](), [coding](), [Software](), [systems]() Tags: [agentic](), [agents](), [code](), [codex](), [coding](), [engineering](), [issue-tracker](), [open-source](), [orchestration](), [pull-requests](), [web](), [workflow](), [workflows]() ### AI overview This article explains Symphony, an open-source specification and agent orchestrator created to reduce context switching in coding-agent workflows. Symphony connects project-management issue trackers to continuously running agents, while humans review the results. The article describes the workflow changes behind the system and reports a 500% increase in landed pull requests on some teams. ### Source excerpt Learn how Symphony, an open-source spec for Codex orchestration, turns issue trackers into always-on agent systems--boosting engineering output and reducing context switching. ## Trace similarity systems on top of ClickHouse to analyze crash stack traces from our CI DevFeed: [Trace similarity systems on top of ClickHouse to analyze crash stack traces from our CI]() Original publisher: [Read original article]() Author: Misha Shiryaev Published: 2025-09-24T12:46:35Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [ci](), [Traces](), [issue tracker](), [Fuzzing/Fuzz testing](), [FIRST]() Tags: [ci](), [clickhouse](), [crash-reporting](), [fuzzing](), [github](), [issue-tracker](), [logs](), [trace]() ### AI overview This article explains how to build a trace similarity system on top of ClickHouse to analyze crash stack traces from CI. It describes collecting crash reports, extracting stack frames, grouping similar traces, and creating or updating GitHub issues so teams can distinguish new bugs from known ones. ### Source excerpt Learn how our engineering team cut through noisy CI crash reports with a trace similarity system built on ClickHouse. ## Keycloak Extensions show GitHub stars DevFeed: [Keycloak Extensions show GitHub stars]() Original publisher: [Read original article]() Author: Alexander Schwartz Published: 2025-02-19T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Extension](), [GitHub](), [issue tracker]() Tags: [extensions](), [github](), [idm](), [issue-tracker](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [saml](), [sso]() ### AI overview Keycloak updated its community extensions page so each extension displays its GitHub star count, helping users identify popular extensions. Users can request missing extensions through the GitHub issue tracker. ### Source excerpt The Keycloak homepage has an updated community extensions page! Thanks to Martin Bartoš, each extension shows off with its GitHub stars. This should provide you with a better overview which extensions are popular with the community. If an extension you use is listed there, give a star! Are you missing an extension? Create an issue in our GitHub issue tracker to let us know so we can add it. Click on image below to get the extensions page, or navigate via the Community page and choose "Extensions" there. PS: Did you already give Keycloak a star? ## How a transitive dependency caused unexpected Android behavior DevFeed: [How a transitive dependency caused unexpected Android behavior]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2025-01-14T00:00:00Z Content type: opinion Language: en Sources: [Posts on Marco Gomiero]() Topics: [Android](), [Library](), [issue tracker](), [navigation]() Tags: [android](), [bugs](), [debugging](), [dependencies](), [fragments](), [issue-tracker](), [libraries]() ### AI overview The author recounts debugging a crash affecting some Android users and tracing unexpected behavior to a change introduced by an external library. The article advises checking library changes and transitive dependencies during updates. ### Source excerpt This article is just a short "rant" and a "therapy session" to remind and warn my future self. I was recently debugging a weird crash affecting some users. The issue was related to navigation, fragments, and backstacks. After weeks spent trying to reproduce it, reading online reports, and cross-referencing previous libraries and SDK updates, I finally had an illuminating moment after reading about a similar behavior in the Google Issue Tracker. It made me wonder: Could something have changed in the Android Manifest? ## KotlinPoet 2.0 is here! DevFeed: [KotlinPoet 2.0 is here!]() Original publisher: [Read original article]() Author: Egor Andreevich Published: 2024-11-05T00:00:00Z Content type: release Language: en Sources: [Cash App Code Blog]() Topics: [Library](), [Code generation](), [Kotlin](), [Code](), [Syntax Highlighting]() Tags: [code-generation](), [compatibility](), [formatting](), [github](), [issue-tracker](), [kotlin](), [migration](), [release]() ### AI overview KotlinPoet 2.0 is a source- and binary-compatible major release of the Kotlin and Java API for generating Kotlin source files. It changes space wrapping so spaces do not wrap by default, while a newly introduced character marks spaces that are safe to wrap. ### Source excerpt KotlinPoet 2.0 is the next, source- and binary-compatible major release of the library, that has important behavior changes. ## Zed AI: Introducing Usage-Based Billing for High-Volume Users DevFeed: [Zed AI: Introducing Usage-Based Billing for High-Volume Users]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2024-10-17T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Artificial Intelligence](), [Code](), [issue tracker]() Tags: [account](), [ai](), [cost](), [free](), [issue-tracker](), [optional](), [subscription](), [tokens](), [usage-based-billing](), [volume]() ### AI overview Zed is introducing usage-based billing for high-volume Zed AI users while keeping a free tier for everyone else. Users will be billed at cost for tokens beyond the free tier, with optional subscription billing and monthly spending limits. ### Source excerpt Some billing-related changes for Zed's AI offering ## vec2pg: Migrate to pgvector from Pinecone and Qdrant DevFeed: [vec2pg: Migrate to pgvector from Pinecone and Qdrant]() Original publisher: [Read original article]() Author: Oliver Rice Published: 2024-08-16T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Qdrant](), [Supabase](), [Databases](), [SQL](), [data]() Tags: [cli](), [cloud](), [data](), [databases](), [developer](), [issue-tracker](), [network](), [postgres](), [recovery](), [scale](), [speed](), [sql](), [technology](), [tools](), [vector]() ### AI overview vec2pg is a command-line utility that migrates data from Pinecone and Qdrant vector databases into Supabase or another Postgres instance using pgvector. It preserves identifiers and metadata, supports Pinecone namespaces and cloud or locally hosted Qdrant instances, and reports throughput under specified infrastructure conditions. ### Source excerpt Migrate vector data from vector DBs to Supabase ## Chromium Issue Tracker migration is complete DevFeed: [Chromium Issue Tracker migration is complete]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-02-05T16:42:00Z Content type: news Language: en Sources: [Chromium Blog]() Topics: [Chromium](), [GitHub Issues](), [migration](), [Google](), [Tooling](), [Open Source](), [Documentation](), [Git]() Tags: [chromium](), [documentation](), [ecosystem](), [git](), [google](), [issue-tracker](), [migration](), [none](), [open-source](), [tooling]() ### AI overview Chromium has completed its migration from Monorail to the Chromium Issue Tracker, powered by Google Issue Tracker. Existing Monorail links will redirect to the migrated issues, and feedback will help improve the new tracker experience. ### Source excerpt We are thrilled to share that Chromium issue tracking has migrated! Access the Issue Tracker, and supporting documentation. Why was this done Issue tracking moved from Monorail to the Chromium Issue Tracker (powered by the Google Issue Tracker) to provide a feature-rich and well-supported issue tracker for Chromium's ecosystem. Chromium joins other open source projects (Git, Gerrit) on this tooling. What happens moving forward Existing Monorail issue links will redirect to the migrated issues in the new issue tracker. We will prioritize feedback to continue to improve the issue tracker experience. Help & Feedback You can reach out at any time to issue-tracker-support@chromium.org with questions or concerns. ## Chromium Issue Tracker migration beginning Feb 2, 2024 at 5pm PST DevFeed: [Chromium Issue Tracker migration beginning Feb 2, 2024 at 5pm PST]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-02-02T17:02:00Z Content type: news Language: en Sources: [Chromium Blog]() Topics: [Chromium](), [issue tracker](), [migration](), [Google](), [Open Source](), [Documentation]() Tags: [bugs](), [chromium](), [documentation](), [google](), [issue-tracker](), [migration](), [none](), [open-source](), [tooling]() ### AI overview Chromium is migrating all issues, including their history and stars, from Monorail to the Google-powered Chromium Issue Tracker. The migration is scheduled for February 2-4, 2024, with existing issue links redirecting afterward and documentation for common workflows to be added later. ### Source excerpt As we shared last year, Chromium is moving to a different issue tracker to provide a well-supported user experience for the long term. Migration is beginning today (February 2, 2024) at 5pm PST. We expect migration will be completed by the end of day (PST) February 4, 2024. What's happening We will migrate all Chromium issues, including issue history and stars, from Monorail to a different tool: Chromium Issue Tracker, powered by the Google Issue Tracker. This tooling change will provide a feature-rich and well-supported issue tracker for Chromium's ecosystem. Chromium will join other open source projects (Git, Gerrit) on this tooling. Existing transparency levels to bugs will be maintained. Post-Migration We will publish another post once the migration is complete. Once the migration completes, existing Monorail issue links will redirect to the migrated issues in the new issue tracker. We will prioritize feedback to continue to improve the issue tracker experience. Documentation on new and common workflows will be added to chromium.org once the migration is complete. Help & Feedback You can reach out at any time to issue-tracker-support@chromium.org with questions or concerns. ## Bootstrap Icons v1.11.0 DevFeed: [Bootstrap Icons v1.11.0]() Original publisher: [Read original article]() Author: Mark Otto Published: 2023-09-12T00:01:00Z Content type: release Language: en Sources: [Bootstrap.com]() Topics: [releases](), [Bootstrap]() Tags: [figma](), [figma-community](), [github](), [icons](), [issue-tracker](), [npm](), [release](), [search](), [v1]() ### AI overview Bootstrap Icons v1.11.0 adds 100 new icons, bringing the collection to more than 2,000 icons. The release also introduces version tags for icon pages, npm and Composer installation options, GitHub downloads, and a newly published Figma Community file. ### Source excerpt Bootstrap Icons v1.11.0 has arrived with 100 new icons--including new floppy disk icons, additional brand icons, new person icons, new emojis, some birthday cake, a few new science icons, and more. We're now at over 2,000 icons! 100 new icons Here's a quick look at all the new icons in v1.11.0: Check out the pull request for all the details on which icons were added and which were updated. ## Imperfect #14: How to map dependencies DevFeed: [Imperfect #14: How to map dependencies]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2023-07-07T13:33:59Z Content type: tutorial Language: en Sources: [Pedro Gil Carvalho]() Topics: [Architecture & Design](), [microservices architecture](), [Microservice](), [interfaces](), [API](), [Database]() Tags: [api](), [architecture](), [awareness](), [changes](), [database](), [dependencies](), [distributed](), [issue-tracker](), [map](), [microservices](), [microservices-architecture](), [monitor](), [monolith](), [pair-programming]() ### AI overview The article explains how to map service dependencies to help identify and avoid distributed monoliths. It recommends team-by-team architecture reviews, collaboratively maintained diagrams, monitoring connected interfaces, and tracking dependencies in a simple spreadsheet. ### Source excerpt Avoiding the distributed monolith antipattern requires great situational awareness. Today we go over what that means, how architecture reviews can help, and one simple way to anticipate dependencies. ## Announcing the Apollo Kotlin plugin for Android Studio and IntelliJ IDEA DevFeed: [Announcing the Apollo Kotlin plugin for Android Studio and IntelliJ IDEA]() Original publisher: [Read original article]() Author: Benoit Lubek Published: 2023-06-20T12:22:59Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Android Studio](), [IntelliJ IDEA](), [Kotlin](), [GraphQL](), [Code generation](), [Gradle](), [Library](), [ide]() Tags: [android-studio](), [apollo](), [code-generation](), [gradle](), [gradle-plugin](), [graphql](), [intellij-idea](), [issue-tracker](), [kotlin](), [library](), [migration](), [mobile](), [navigation](), [plugin](), [preview](), [release]() ### AI overview Apollo introduced a preview plugin for Android Studio and IntelliJ IDEA that improves Apollo Kotlin development with automatic background code generation, migration helpers, and navigation between Kotlin and GraphQL definitions. ### Source excerpt We're happy to introduce an Apollo Kotlin plugin for Android Studio and IntelliJ IDEA, to help you work with the library and improve your productivity. This preview release can be tried out today. Features On-the-fly code generation Apollo Kotlin is a strongly-typed client library that generates models from your GraphQL queries. This works thanks to a Gradle plugin that triggers the code generation at build time. ## This Week at Zed Industries: #5 DevFeed: [This Week at Zed Industries: #5]() Original publisher: [Read original article]() Author: Max Brunsfeld Published: 2023-06-02T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [ui](), [App](), [dashboards](), [issue tracker](), [systems]() Tags: [app](), [features](), [issue-tracker](), [layout](), [os](), [screen](), [set](), [view]() ### AI overview Zed's weekly update covers the release of Zed 0.88, including a redesigned panel system and a zoom feature. It also describes crash problems after release, three patches issued to address them, new crash dashboards, and ongoing work on LSP server detection. ### Source excerpt Panels, panels, and more panels... ## Gradle Public Roadmap DevFeed: [Gradle Public Roadmap]() Original publisher: [Read original article]() Author: Piotr Jagielski Published: 2022-06-17T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [GitHub](), [releases](), [issue tracker](), [Slack]() Tags: [github](), [gradle](), [issue-tracker](), [release-notes](), [releases](), [slack]() ### AI overview Gradle has made its Build Tool roadmap public through a GitHub-hosted roadmap board. The board presents planned projects and user-facing features by quarter and target release, while also showing work delivered in the previous two quarters. ### Source excerpt We are excited to announce that the Gradle Build Tool roadmap is now public. See the roadmap board and the associated readme. Motivation The Gradle Build Tool project regularly ships new releases full of new features and bug fixes. So far our main channels of communication with the user community to share plans and get feedback were release notes, blog, issue tracker, forums, and community Slack. However, we lacked a high-level overview of what's planned in the upcoming releases. About the roadmap Today, we are announcing our new roadmap board hosted on GitHub. It lists major projects and user-facing features, organized by quarter and target release. The board also shows the past two quarters so that you can see what we delivered in recent Gradle releases. Each roadmap item provides a brief description and links to related issues in the issue tracker. Share Your Feedback We hope that this additional level of transparency about our plans will be useful to you. Please let us know if you have any questions or feedback. Comments on the roadmap board itself are disabled to keep it neat and tidy. Instead, reach out to us on the community Slack #roadmap channel. ## incident.io on Ship It! DevFeed: [incident.io on Ship It!]() Original publisher: [Read original article]() Author: Chris Evans Published: 2021-10-04T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [issue tracker](), [Server](), [ssh]() Tags: [core](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [issue-tracker](), [outage](), [podcast](), [post-mortem](), [slack-incident]() ### AI overview The article discusses incident.io's approach to incident management, combining opinionated defaults such as incident leads, severity definitions, and structured updates with flexibility for each company's process. It emphasizes simplicity and reducing operators' decision-making burden during incidents. ### Source excerpt A few weeks ago, Stephen and I had the pleasure of talking to @Gerhard on changelog's Ship It! Podcast. We chatted about incident workflows, our relentless focus on simplicity, and how incident.io uses incident.io when we have incidents ourselves. ## High-Tier Content in the SoundCloud API DevFeed: [High-Tier Content in the SoundCloud API]() Original publisher: [Read original article]() Published: 2021-05-06T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [API](), [Playback](), [User Experience]() Tags: [announcements](), [api](), [issue-tracker](), [playback](), [user-experience]() ### AI overview The SoundCloud API now supports retrieving metadata for the full catalog, including high-tier Go+ content. A new filter lets clients request tracks based on whether the user can fully play, preview, or only view metadata for them. ### Source excerpt You can now retrieve metadata for our full SoundCloud catalog through our API by providing the new filter in your request. Until recently... ## SoundCloud's New API Track Object DevFeed: [SoundCloud's New API Track Object]() Original publisher: [Read original article]() Published: 2021-03-16T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [API](), [data](), [Structured-data](), [issue tracker]() Tags: [announcements](), [api](), [data](), [developers](), [issue-tracker](), [update](), [updates]() ### AI overview SoundCloud is introducing a new API track object aligned with its current data model to standardize and simplify response data. Deprecated fields will be removed from track-related responses, and developers are asked to update applications or request preservation of necessary fields through the issue tracker. ### Source excerpt As a part of our efforts to improve API use, we're introducing a new object that's more up to date with our current data model. The... ## Find that bug! Using a search engine as a programmer DevFeed: [Find that bug! Using a search engine as a programmer]() Original publisher: [Read original article]() Author: Itamar Turner-Trauring Published: 2020-08-17T00:00:00Z Content type: tutorial Language: en Sources: [Itamar Turner-Trauring]() Topics: [Programming](), [issue tracker](), [Python](), [Stack Overflow](), [pandas](), [Logging](), [GitHub](), [JSON]() Tags: [bug](), [documentation](), [github](), [issue-tracker](), [json](), [pandas](), [python](), [search]() ### AI overview This article explains how programmers can find solutions to bugs and programming problems by searching project-specific issue trackers, documentation, Stack Overflow, and other local resources alongside general search engines. It uses an Eliot and Pandas error as an example of a GitHub issue that a general search engine did not index. ### Source excerpt Most bugs you encounter have been encountered by others before you; most programming problems you face have been faced by others as well. And many of those people have written down details about what they've learned--in issue trackers, documentation, and blog posts. All you have to do is find this information. Typing a phrase in to your search engine of choice will sometimes take you straight to the right answer. But quite often, the results aren't helpful. No need to give up, though: there are still plenty of ways you can productively keep searching. Use site-specific search too It's easy to believe that search engines have all the answers right at the top, but they actually hide quite a lot of content deep in their results. And some obscure content never gets indexed at all, which is unfortunate when it's the obscure content that you need to find. So instead of just using a search engine, use the local search engine of the project issue tracker, the documentation, StackOverflow, and so on. For example, let's saying you're using Eliot, a somewhat obscure Python logging library I maintain, and you want to use it with the Pandas library. Unfortunately, you get an error, so you search Google for the text of the error: eliot dataframe is not json serializable. Now, there is an actual issue in Eliot's GitHub issue tracker with this exact error message--but as of August 2020 Google doesn't return it, probably because it didn't bother to index that page. But if you were to use the search form on the Eliot GitHub project's issues page, you would find the issue that mentions this particular error. In this case, as in many others, the search engine isn't actually indexing everything: you have no choice but to use the local search engine. Local search engines often have the additional benefit of allowing more structured search, for example: An issue tracker might let you search by open/closed status, labels, or the affected version. StackOverflow questions are tagged with parti [Next page]()