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

🐞[Bug]: 404 Error: All Repository Links Lead to Broken Pages #1443

Closed
4 tasks done
shreyasparaj opened this issue Oct 14, 2024 · 2 comments
Closed
4 tasks done

🐞[Bug]: 404 Error: All Repository Links Lead to Broken Pages #1443

shreyasparaj opened this issue Oct 14, 2024 · 2 comments
Assignees

Comments

@shreyasparaj
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

All the "View Models" buttons across multiple repositories on the page redirect to 404 error pages. Regardless of which repository is selected, users encounter the same broken link issue.

Affected Repositories and Links -

  1. Algorithms and Deep Learning Models – View Models
  2. Classification Models – View Models
  3. Data Analysis – View Models
  4. Detection Models – View Models
  5. OpenCV Projects – View Models
  6. Prediction Models – View Models
  7. Recommendation Models – View Models
  8. tail_effect – View Models
  9. .ipynb_checkpoints – View Models

Expected behavior

  • Each "View Models" button should navigate to the relevant page displaying the models for the selected repository.
  • If no models are available, the system should display a user-friendly message such as "No models available at the moment."
  • If the content is not ready, the button should either be disabled or hidden.

Add ScreenShots

Screenshot (587)
Screenshot (588)

What browsers are you seeing the problem on?

Chrome

Record

  • I have read the Contributing Guidelines
  • I'm a GSSOC'24 contributor
  • I want to work on this issue
@shreyasparaj shreyasparaj added the bug Something isn't working label Oct 14, 2024
Copy link

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions reach out to LinkedIn. Your contributions are highly appreciated! 😊

Note: I Maintain the repo issue twice a day, or ideally 1 day, If your issue goes stale for more than one day you can tag and comment on this same issue.

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.
We are here to help you on this journey of opensource, any help feel free to tag me or book an appointment.

Copy link

Hello @shreyasparaj! Your issue #1443 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants