Deprecated: Return type of LayerShifter\TLDExtract\Result::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u404671710/domains/rollingnotes.in/public_html/news/application/third_party/domain-parser/layershifter/tld-extract/src/Result.php on line 189

Deprecated: Return type of LayerShifter\TLDExtract\Result::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u404671710/domains/rollingnotes.in/public_html/news/application/third_party/domain-parser/layershifter/tld-extract/src/Result.php on line 203

Deprecated: Return type of LayerShifter\TLDExtract\Result::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u404671710/domains/rollingnotes.in/public_html/news/application/third_party/domain-parser/layershifter/tld-extract/src/Result.php on line 251

Deprecated: Return type of LayerShifter\TLDExtract\Result::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u404671710/domains/rollingnotes.in/public_html/news/application/third_party/domain-parser/layershifter/tld-extract/src/Result.php on line 267

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_database_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_database_driver.php

Line Number: 129

Backtrace:

File: /home/u404671710/domains/rollingnotes.in/public_html/news/application/core/Core_Controller.php
Line: 7
Function: __construct

File: /home/u404671710/domains/rollingnotes.in/public_html/news/application/core/Core_Controller.php
Line: 119
Function: __construct

File: /home/u404671710/domains/rollingnotes.in/public_html/news/application/controllers/Home_controller.php
Line: 7
Function: __construct

File: /home/u404671710/domains/rollingnotes.in/public_html/news/index.php
Line: 325
Function: require_once

Odisha train accident: What caused the deadly collision, human error or technical glitch? Here's what report reveals - RollingNotes' News

India

Odisha train accident: What caused the deadly collision, human error or technical glitch? Here's what report reveals

Odisha Train Accident: A passenger train, the Coromandel Shalimar Express, derailed and collided with a cargo train within a short period of time. A second train, the Yesvantpur-Howrah Superfast, then crashed into the wrecked coaches.

Jun 3, 2023 - 17:10

0 1

Odisha train accident: What caused the deadly collision, human error or technical glitch? Here's what report reveals

Odisha Train Accident: A passenger train, the Coromandel Shalimar Express, derailed and collided with a cargo train within a short period of time. A second train, the Yesvantpur-Howrah Superfast, then crashed into the wrecked coaches.