A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_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_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Arvind Kejriwal Blames BJP for Power Outages in Delhi Amid Soaring Summer Demand | Get Career Advice Tips. Unlock Your Potential and Find Your Path around the world - NRI Page
Edit

Arvind Kejriwal Blames BJP for Power Outages in Delhi Amid Soaring Summer Demand

Arvind Kejriwal Blames BJP for Power Outages in Delhi Amid Soaring Summer Demand

The national capital is once again witnessing a political showdown, this time over a critical issue—electricity supply. Former Delhi Chief Minister and Aam Aadmi Party (AAP) national convenor Arvind Kejriwal launched a scathing attack on the ruling Bharatiya Janata Party (BJP) on Thursday, blaming the recent wave of power outages on the alleged mismanagement by the BJP-led administration. Kejriwal took to social media platform X (formerly Twitter) to express his frustration over what he called a rapid deterioration of the robust electricity system that he claims was built during AAP's decade-long governance. “In the last ten years, we have fixed the power system of Delhi with great difficulty. It is said that it takes years to fix anything, but it can be damaged in just two days,” he wrote.

He backed his statements with figures, citing that on Wednesday, the peak power demand in Delhi stood at 5462 MW, yet there were reports of widespread outages. Drawing a comparison to his administration, Kejriwal mentioned that last year the city witnessed a peak demand of 8500 MW without significant interruptions in electricity supply. His remarks were a clear indication of his belief that the BJP government has been unable to maintain the infrastructure put in place by AAP. The timing of his statement also aligns with rising public concern over the looming summer heat, with temperatures expected to soar and electricity demand to follow suit. “What will happen in the coming weeks when the heat in Delhi will increase and the demand for electricity will also increase?” Kejriwal questioned in his post, drawing attention to the urgency of the matter.

AAP's Continued Criticism Amid Rising Outages

Kejriwal’s statements come as part of a broader campaign by AAP to highlight alleged governance failures under the BJP in Delhi. Atishi, AAP leader and former Chief Minister who succeeded Kejriwal briefly before the party lost control, has also been active on social media over the past 24 hours. Re-sharing citizens’ posts complaining about scheduled outages, Atishi criticized Power Minister Ashish Sood and the BJP for what she described as a routine failure. “Delhites now routinely calling out the excuses publicly made by Power Minister Ashish Sood that these are scheduled power cuts for maintenance,” she posted, echoing concerns of many residents who are facing daily disruptions.

Atishi’s posts point to a growing frustration among the public, as citizens continue to express discontent on social media platforms, questioning the rationale behind prolonged and frequent outages at a time when demand hasn’t even peaked. This is not the first time Kejriwal has raised an alarm. Back in March, he had similarly accused the BJP government of failing to maintain uninterrupted electricity in Delhi—a claim which was promptly refuted by Power Minister Ashish Sood. The Minister, defending his department’s record, had released data showing that in the last 12 months of AAP’s rule, Delhi had experienced over 21,600 power cuts lasting more than an hour each.

The debate over electricity supply in Delhi is heating up alongside the weather. While AAP continues to claim that its infrastructure was capable of handling higher loads without interruption, BJP leaders argue that maintenance and infrastructure issues existed even during AAP’s tenure. With summer temperatures expected to rise in the coming weeks, the political blame game is likely to intensify. Delhiites, however, remain caught in the middle, hoping that political sparring doesn't come at the cost of a reliable electricity supply. As the narrative unfolds, all eyes will be on how the Delhi administration tackles the growing demands of the summer season and whether it can offer consistent electricity without outages—or if the power struggle will become more than just political.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD