Auto PR: Scheduled addition of new sources#37
Closed
semmet95 wants to merge 2 commits into
Closed
Conversation
Signed-off-by: Amit Singh <singhamitch@outlook.com>
📝 WalkthroughWalkthroughTen claim record YAML files are added or updated across multiple news sources with consistent metadata: sourceUriDigest, summary, title, and uri fields referencing articles on geopolitical events, technology, and market commentary. ChangesClaim Records Batch
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@claims/bbc/uae_reports_drone_strike_near.yaml`:
- Around line 1-4: The YAML file uses quoted full-line strings like
"sourceUriDigest": "..." which are parsed as scalars instead of mappings; change
each quoted key to a proper YAML mapping key (e.g., sourceUriDigest: "value")
for the entries sourceUriDigest, summary, title, and uri so they become valid
key: value pairs; ensure keys are unquoted (or use bare keys) and values remain
quoted if they contain special characters.
In `@claims/hindustan_times/at_least_nine_dead_in_china_af.yaml`:
- Around line 1-4: The YAML file uses quoted full-line strings like
"sourceUriDigest": which are parsed as scalars rather than keys; update the
mapping so each entry is a proper YAML key: value pair (no surrounding quotes
around the entire key+colon token) — e.g. convert the lines containing
"sourceUriDigest":, "summary":, "title":, and "uri": into valid YAML mappings by
placing the key (sourceUriDigest, summary, title, uri) followed by a colon, a
space, and the quoted or plain value as appropriate.
In `@claims/india_times/farm_fires_punjab_reports_115.yaml`:
- Line 2: The "summary" field in
claims/india_times/farm_fires_punjab_reports_115.yaml currently contains the
placeholder string "None"; replace that placeholder with a concise descriptive
summary of the article (one or two sentences) that captures the main
claim/details, updating the "summary" value in the YAML so it is not "None"
anymore.
In `@claims/ndtv/4_dead_8_injured_as_gunman_op.yaml`:
- Line 2: The "summary" field currently contains the placeholder string "None";
replace it with a concise descriptive summary of the article (one clear sentence
capturing the who/what/where/when/why) by editing the "summary" value in the
YAML (claims/ndtv/4_dead_8_injured_as_gunman_op.yaml). Use the article body to
craft the sentence, ensure it is not the literal "None" and follows the same
quoting/formatting as other entries, and save the file so ingestion sees the
populated summary.
- Around line 1-4: The YAML uses quoted whole-line strings like
"sourceUriDigest": "..." which YAML treats as scalars, not mappings; update the
document so keys are proper YAML mappings by removing the surrounding quotes
from keys and using key: value pairs (e.g., sourceUriDigest:
bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f, summary:
"None", title: "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey:
Report", uri: "https://...") for the keys sourceUriDigest, summary, title and
uri so the file parses as a valid mapping.
In `@claims/yahoo_finance/michael_burry_says_today_s_top.yaml`:
- Line 2: The "summary" field currently contains the literal string "None";
replace it with a meaningful short summary of the claim or, if intentionally
empty, set a schema-compliant null/empty value per oapi.yaml (e.g., remove the
key or use the approved null representation). Update the "summary" key in
michael_burry_says_today_s-top.yaml so it is not the literal "None" and conforms
to the API schema.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 3a6462cb-3964-4f8a-9fb7-18efaefeb772
📒 Files selected for processing (10)
claims/al_jazeera/drc_faces_deadly_ebola_resurge.yamlclaims/bbc/uae_reports_drone_strike_near.yamlclaims/fox_news/us_nigeria_strike_isis_fighte.yamlclaims/hindustan_times/at_least_nine_dead_in_china_af.yamlclaims/india_times/farm_fires_punjab_reports_115.yamlclaims/ndtv/4_dead_8_injured_as_gunman_op.yamlclaims/south_china_morning_post/forget_cellular_data_china_s.yamlclaims/the_guardian/california_island_fire_linked.yamlclaims/the_new_york_times/meta_reassigns_7_000_employees.yamlclaims/yahoo_finance/michael_burry_says_today_s_top.yaml
Comment on lines
+1
to
+4
| "sourceUriDigest": "ff03f7306b36e74d5dad4a7b18f821862b90afd53cc6f01dc7fd3b07796b1404" | ||
| "summary": "The country is investigating the source of the strike, which it says came from its western border." | ||
| "title": "UAE reports drone strike near Abu Dhabi nuclear power plant" | ||
| "uri": "https://www.bbc.com/news/articles/cwy27pkj1l1o" |
There was a problem hiding this comment.
Invalid YAML mapping syntax.
The quoted keys break the YAML mapping structure. Lines like "sourceUriDigest": "value" are parsed as scalar strings, not key-value pairs, and will cause YAML parsing to fail.
🔧 Proposed fix to correct YAML syntax
-"sourceUriDigest": "ff03f7306b36e74d5dad4a7b18f821862b90afd53cc6f01dc7fd3b07796b1404"
-"summary": "The country is investigating the source of the strike, which it says came from its western border."
-"title": "UAE reports drone strike near Abu Dhabi nuclear power plant"
-"uri": "https://www.bbc.com/news/articles/cwy27pkj1l1o"
+sourceUriDigest: "ff03f7306b36e74d5dad4a7b18f821862b90afd53cc6f01dc7fd3b07796b1404"
+summary: "The country is investigating the source of the strike, which it says came from its western border."
+title: "UAE reports drone strike near Abu Dhabi nuclear power plant"
+uri: "https://www.bbc.com/news/articles/cwy27pkj1l1o"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "sourceUriDigest": "ff03f7306b36e74d5dad4a7b18f821862b90afd53cc6f01dc7fd3b07796b1404" | |
| "summary": "The country is investigating the source of the strike, which it says came from its western border." | |
| "title": "UAE reports drone strike near Abu Dhabi nuclear power plant" | |
| "uri": "https://www.bbc.com/news/articles/cwy27pkj1l1o" | |
| sourceUriDigest: "ff03f7306b36e74d5dad4a7b18f821862b90afd53cc6f01dc7fd3b07796b1404" | |
| summary: "The country is investigating the source of the strike, which it says came from its western border." | |
| title: "UAE reports drone strike near Abu Dhabi nuclear power plant" | |
| uri: "https://www.bbc.com/news/articles/cwy27pkj1l1o" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/bbc/uae_reports_drone_strike_near.yaml` around lines 1 - 4, The YAML
file uses quoted full-line strings like "sourceUriDigest": "..." which are
parsed as scalars instead of mappings; change each quoted key to a proper YAML
mapping key (e.g., sourceUriDigest: "value") for the entries sourceUriDigest,
summary, title, and uri so they become valid key: value pairs; ensure keys are
unquoted (or use bare keys) and values remain quoted if they contain special
characters.
Comment on lines
+1
to
+4
| "sourceUriDigest": "16e7233814ff26725174c87e80e6da033de4feb7ea3fa5a904ef75dbc17541f3" | ||
| "summary": "The passengers were returning from planting sweet potatoes on Saturday and the truck fell into the river while crossing a bridge." | ||
| "title": "At least nine dead in China after vehicle swept into flooded river during heavy rain" | ||
| "uri": "https://www.hindustantimes.com/world-news/at-least-nine-dead-in-china-after-vehicle-swept-into-flooded-river-during-heavy-rain-101779124029765.html" |
There was a problem hiding this comment.
Invalid YAML mapping syntax.
The quoted keys break the YAML mapping structure. Lines like "sourceUriDigest": "value" are parsed as scalar strings, not key-value pairs, and will cause YAML parsing to fail.
🔧 Proposed fix to correct YAML syntax
-"sourceUriDigest": "16e7233814ff26725174c87e80e6da033de4feb7ea3fa5a904ef75dbc17541f3"
-"summary": "The passengers were returning from planting sweet potatoes on Saturday and the truck fell into the river while crossing a bridge."
-"title": "At least nine dead in China after vehicle swept into flooded river during heavy rain"
-"uri": "https://www.hindustantimes.com/world-news/at-least-nine-dead-in-china-after-vehicle-swept-into-flooded-river-during-heavy-rain-101779124029765.html"
+sourceUriDigest: "16e7233814ff26725174c87e80e6da033de4feb7ea3fa5a904ef75dbc17541f3"
+summary: "The passengers were returning from planting sweet potatoes on Saturday and the truck fell into the river while crossing a bridge."
+title: "At least nine dead in China after vehicle swept into flooded river during heavy rain"
+uri: "https://www.hindustantimes.com/world-news/at-least-nine-dead-in-china-after-vehicle-swept-into-flooded-river-during-heavy-rain-101779124029765.html"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "sourceUriDigest": "16e7233814ff26725174c87e80e6da033de4feb7ea3fa5a904ef75dbc17541f3" | |
| "summary": "The passengers were returning from planting sweet potatoes on Saturday and the truck fell into the river while crossing a bridge." | |
| "title": "At least nine dead in China after vehicle swept into flooded river during heavy rain" | |
| "uri": "https://www.hindustantimes.com/world-news/at-least-nine-dead-in-china-after-vehicle-swept-into-flooded-river-during-heavy-rain-101779124029765.html" | |
| sourceUriDigest: "16e7233814ff26725174c87e80e6da033de4feb7ea3fa5a904ef75dbc17541f3" | |
| summary: "The passengers were returning from planting sweet potatoes on Saturday and the truck fell into the river while crossing a bridge." | |
| title: "At least nine dead in China after vehicle swept into flooded river during heavy rain" | |
| uri: "https://www.hindustantimes.com/world-news/at-least-nine-dead-in-china-after-vehicle-swept-into-flooded-river-during-heavy-rain-101779124029765.html" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/hindustan_times/at_least_nine_dead_in_china_af.yaml` around lines 1 -
4, The YAML file uses quoted full-line strings like "sourceUriDigest": which are
parsed as scalars rather than keys; update the mapping so each entry is a proper
YAML key: value pair (no surrounding quotes around the entire key+colon token) —
e.g. convert the lines containing "sourceUriDigest":, "summary":, "title":, and
"uri": into valid YAML mappings by placing the key (sourceUriDigest, summary,
title, uri) followed by a colon, a space, and the quoted or plain value as
appropriate.
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "6472f88917d973b804e99cf32fcb87269d2557252739bc7bc137d8aa2da7b581" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
Replace placeholder with actual summary content.
The summary field contains the string "None" instead of a descriptive summary of the article content. This appears to be missing data that should be populated before ingestion.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/india_times/farm_fires_punjab_reports_115.yaml` at line 2, The
"summary" field in claims/india_times/farm_fires_punjab_reports_115.yaml
currently contains the placeholder string "None"; replace that placeholder with
a concise descriptive summary of the article (one or two sentences) that
captures the main claim/details, updating the "summary" value in the YAML so it
is not "None" anymore.
Comment on lines
+1
to
+4
| "sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f" | ||
| "summary": "None" | ||
| "title": "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report" | ||
| "uri": "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477" |
There was a problem hiding this comment.
Invalid YAML mapping syntax.
The quoted keys break the YAML mapping structure. Lines like "sourceUriDigest": "value" are parsed as scalar strings, not key-value pairs, and will cause YAML parsing to fail.
🔧 Proposed fix to correct YAML syntax
-"sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f"
-"summary": "None"
-"title": "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report"
-"uri": "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477"
+sourceUriDigest: "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f"
+summary: "None"
+title: "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report"
+uri: "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f" | |
| "summary": "None" | |
| "title": "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report" | |
| "uri": "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477" | |
| sourceUriDigest: "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f" | |
| summary: "None" | |
| title: "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report" | |
| uri: "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/ndtv/4_dead_8_injured_as_gunman_op.yaml` around lines 1 - 4, The YAML
uses quoted whole-line strings like "sourceUriDigest": "..." which YAML treats
as scalars, not mappings; update the document so keys are proper YAML mappings
by removing the surrounding quotes from keys and using key: value pairs (e.g.,
sourceUriDigest:
bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f, summary:
"None", title: "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey:
Report", uri: "https://...") for the keys sourceUriDigest, summary, title and
uri so the file parses as a valid mapping.
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
Replace placeholder with actual summary content.
The summary field contains the string "None" instead of a descriptive summary of the article content. This appears to be missing data that should be populated before ingestion.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/ndtv/4_dead_8_injured_as_gunman_op.yaml` at line 2, The "summary"
field currently contains the placeholder string "None"; replace it with a
concise descriptive summary of the article (one clear sentence capturing the
who/what/where/when/why) by editing the "summary" value in the YAML
(claims/ndtv/4_dead_8_injured_as_gunman_op.yaml). Use the article body to craft
the sentence, ensure it is not the literal "None" and follows the same
quoting/formatting as other entries, and save the file so ingestion sees the
populated summary.
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "844adf50f74b30951a08a382fffc9f1a904acd2d62e062db41d2647c72f904a4" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
Replace placeholder summary value on Line 2.
Using "None" as a literal summary weakens claim quality for downstream ingestion/search. Use a real summary, or set schema-compliant null/empty value (per oapi.yaml) instead.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@claims/yahoo_finance/michael_burry_says_today_s_top.yaml` at line 2, The
"summary" field currently contains the literal string "None"; replace it with a
meaningful short summary of the claim or, if intentionally empty, set a
schema-compliant null/empty value per oapi.yaml (e.g., remove the key or use the
approved null representation). Update the "summary" key in
michael_burry_says_today_s-top.yaml so it is not the literal "None" and conforms
to the API schema.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
3 issues found across 10 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="claims/yahoo_finance/michael_burry_says_today_s_top.yaml">
<violation number="1" location="claims/yahoo_finance/michael_burry_says_today_s_top.yaml:2">
P2: `summary` is set to the literal string "None", which is a placeholder value, not a meaningful summary of the claim. Replace it with an actual description of the claim content before merge.</violation>
</file>
<file name="claims/ndtv/4_dead_8_injured_as_gunman_op.yaml">
<violation number="1" location="claims/ndtv/4_dead_8_injured_as_gunman_op.yaml:2">
P1: Replace `"summary": "None"` with a meaningful description of the claim. The literal string "None" is a Python serialization artifact, not an actual summary — it provides zero information about the claim content and will degrade the quality of the data posted to the API.</violation>
</file>
<file name="claims/india_times/farm_fires_punjab_reports_115.yaml">
<violation number="1" location="claims/india_times/farm_fires_punjab_reports_115.yaml:2">
P1: The summary field contains the string "None", which is almost certainly a data pipeline serialization artifact. This will result in posting a claim with a meaningless summary to the API instead of actual article content. The pipeline should either generate a proper summary from the article or handle the null case correctly.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
P1: Replace "summary": "None" with a meaningful description of the claim. The literal string "None" is a Python serialization artifact, not an actual summary — it provides zero information about the claim content and will degrade the quality of the data posted to the API.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At claims/ndtv/4_dead_8_injured_as_gunman_op.yaml, line 2:
<comment>Replace `"summary": "None"` with a meaningful description of the claim. The literal string "None" is a Python serialization artifact, not an actual summary — it provides zero information about the claim content and will degrade the quality of the data posted to the API.</comment>
<file context>
@@ -0,0 +1,4 @@
+"sourceUriDigest": "bc65553a778a1c832967d1ff1fb318597ff5d87f5f935f6e76820cc514fb287f"
+"summary": "None"
+"title": "4 Dead, 8 Injured As Gunman Opens Fire In Southern Turkey: Report"
+"uri": "https://www.ndtv.com/world-news/4-dead-8-injured-as-gunman-opens-fire-in-southern-turkey-report-11513477"
</file context>
Suggested change
| "summary": "None" | |
| "summary": "Four people were killed and eight others injured after a gunman opened fire in southern Turkey, according to reports." |
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "6472f88917d973b804e99cf32fcb87269d2557252739bc7bc137d8aa2da7b581" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
P1: The summary field contains the string "None", which is almost certainly a data pipeline serialization artifact. This will result in posting a claim with a meaningless summary to the API instead of actual article content. The pipeline should either generate a proper summary from the article or handle the null case correctly.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At claims/india_times/farm_fires_punjab_reports_115.yaml, line 2:
<comment>The summary field contains the string "None", which is almost certainly a data pipeline serialization artifact. This will result in posting a claim with a meaningless summary to the API instead of actual article content. The pipeline should either generate a proper summary from the article or handle the null case correctly.</comment>
<file context>
@@ -0,0 +1,4 @@
+"sourceUriDigest": "6472f88917d973b804e99cf32fcb87269d2557252739bc7bc137d8aa2da7b581"
+"summary": "None"
+"title": "Farm fires: Punjab reports 115 new cases"
+"uri": "https://timesofindia.indiatimes.com/city/chandigarh/farm-fires-punjab-reports-115-new-cases/articleshow/131184684.cms"
</file context>
| @@ -0,0 +1,4 @@ | |||
| "sourceUriDigest": "844adf50f74b30951a08a382fffc9f1a904acd2d62e062db41d2647c72f904a4" | |||
| "summary": "None" | |||
There was a problem hiding this comment.
P2: summary is set to the literal string "None", which is a placeholder value, not a meaningful summary of the claim. Replace it with an actual description of the claim content before merge.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At claims/yahoo_finance/michael_burry_says_today_s_top.yaml, line 2:
<comment>`summary` is set to the literal string "None", which is a placeholder value, not a meaningful summary of the claim. Replace it with an actual description of the claim content before merge.</comment>
<file context>
@@ -0,0 +1,4 @@
+"sourceUriDigest": "844adf50f74b30951a08a382fffc9f1a904acd2d62e062db41d2647c72f904a4"
+"summary": "None"
+"title": "Michael Burry Says Today’s Top 10 Stocks Surged 784% in a Year. The Pre-Dot-Com Number Was 622%."
+"uri": "https://finance.yahoo.com/markets/stocks/articles/michael-burry-says-today-top-131526825.html"
</file context>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds most popular news source in the last week for ingestion
Summary by CodeRabbit