Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collision of RSS-Feed Branch names possible? #63

Open
DerAlexmeister opened this issue Jul 16, 2021 · 2 comments
Open

Collision of RSS-Feed Branch names possible? #63

DerAlexmeister opened this issue Jul 16, 2021 · 2 comments
Assignees
Labels
bug Something isn't working Discuss Topics to discuss Scraper Scraper related issue Urgent Please fix soon
Milestone

Comments

@DerAlexmeister
Copy link
Collaborator

DerAlexmeister commented Jul 16, 2021

Could a collision between multiple events in a RSS-Feed be possible?

Are there RSS-Feed sending similar events with similar names?

Because on fetching information using the scraper from time to time the system prints a lot of "Branch already exists" messages.

Although the name of a branch from every sources should to be unique.

A test run with ~1650 RSS-Events turned into ~900 in GitLab.

@DerAlexmeister DerAlexmeister added bug Something isn't working Urgent Please fix soon Scraper Scraper related issue Discuss Topics to discuss labels Jul 16, 2021
@DerAlexmeister DerAlexmeister added this to the 0.1.2 milestone Jul 16, 2021
@DerAlexmeister
Copy link
Collaborator Author

Same for twitter and the API calls

@DerAlexmeister
Copy link
Collaborator Author

DerAlexmeister commented Jul 17, 2021

[i] INFO: 400: Invalid reference name: IoC-07-2021 - (Pusher)

This message occurred from time to time in the while running the API-Scraper and it might also be a part of the collision question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Discuss Topics to discuss Scraper Scraper related issue Urgent Please fix soon
Projects
None yet
Development

No branches or pull requests

2 participants