Turbopack tokio-rt-worker error

[Abhis1605]

thread 'tokio-rt-worker' (23863) panicked at turbopack/crates/turbo-tasks-backend/src/backend/operation/mod.rs:1329:13:
Every task must have a task type TaskGuard { task_id: TaskId { id: 194 }, storage: TaskStorage { leaf_distance: LeafDistance { distance: 0, max_distance_in_buffer: 0 }, aggregation_number: AggregationNumber { base: 0, distance: 0, effective: 0 }, output_dependent: {}, output: None, upper: CounterMap({}), persistent_task_type: None, flags: TaskFlags { .0: 48, optimization_pending: false, invalidator: false, immutable: false, current_session_clean: false, meta_restored: true, data_restored: true, meta_restoring: false, data_restoring: false, meta_modified: false, data_modified: false, meta_modified_during_snapshot: false, data_modified_during_snapshot: false, prefetched: false, stateful: false, new_task: false }, lazy: [AggregatedCurrentSessionCleanContainerCount(1), AggregatedCurrentSessionCleanContainers(CounterMap({TaskId { id: 193 }: 1})), Activeness(ActivenessState { active_counter: 2, root_ty: None, active_until_clean: false, all_clean_event: Event }), InProgress(Scheduled { done_event: Event, reason: ActivateInitial })] } }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

turbo-tasks: an internal panic occurred outside the per-task panic boundary. This is a bug in turbo-tasks/Turbopack — please report it at https://github.com/vercel/next.js/discussions and include the panic message and stack trace above.