Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ ocr_text: null; corrected_text: null; rag_context: never[]; llm_response: null; note: null; id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; prompt: string; final_prompt: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Property 'rag_model' is missing in type '{ id: number; image_name: string; image_path: string; ocr_model: string; correction_model: string; llm_model: string; ocr_text: string; corrected_text: string; rag_context: string[]; llm_response: string; prompt: string; final_prompt: string; note: string; created_at: string; }' but required in type 'Translation'.

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

Unexpected any. Specify a different type

'handleSignIn' is assigned a value but never used

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

'afterEach' is defined but never used

'beforeEach' is defined but never used