Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
  • Sign in / Register
2
2024_warm_up_upstream
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • compiler_staff
  • 2024_warm_up_upstream
  • Issues
  • #1

Closed
Open
Opened Jul 03, 2025 by Issac Brycen@Brycen009
  • Report abuse
  • New issue
Report abuse New issue

Error Handling Issue In Warm-Up Task

Hi team,

While working on the 2024 warm-up compiler task, I encountered a small issue related to input parsing. The compiler seems to crash when given unexpected whitespace or empty inputs.

I tried comparing it to some basic logic handling used in browser games like bitlife unblocked , where input validation is more forgiving. It made me wonder if we need a better way to handle edge cases here as well.

Please let me know if there's a preferred method to sanitize or validate the input before parsing.

Thanks!

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: compiler_staff/2024_warm_up_upstream#1