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 | Group 2 Exam Controversy: High Court Orders Feb 23 Exam Amid Jagan Govt Errors | Get Career Advice Tips. Unlock Your Potential and Find Your Path around the world - NRI Page
Edit

Group 2 Exam Controversy: High Court Orders Feb 23 Exam Amid Jagan Govt Errors

Group 2 Exam Controversy: High Court Orders Feb 23 Exam Amid Jagan Govt Errors

The Group 2 exam issue in Andhra Pradesh has now become a major talking point following a series of controversies that trace back to errors in the 2023 notification issued by the Jagan government. What began as a pre-election announcement of 899 Group 2 posts soon turned into a heated debate when job aspirants discovered that the roster points were marked incorrectly. Critics claim that the notification was released not with the intent to create employment opportunities but rather as a strategy to attract young voters ahead of the elections. As a result, many candidates challenged the announcement in court, arguing that the reservations and job vacancies were not calculated properly.
 

Following the preliminary examinations, an impressive 92,250 candidates qualified for the mains exam. However, persistent complaints regarding the roster marking and the alleged miscalculation of reservations led the High Court to review the case. In its verdict, the court directed that the mains exam be conducted on February 23, 2025. This decision was met with mixed reactions from the public, as many job aspirants continue to express their dissatisfaction with the entire process, which they believe was manipulated for political gains.In the wake of these controversies, the issue escalated further when the new NDA government took charge. Chandrababu’s administration reportedly wrote a letter to the Andhra Pradesh Public Service Commission (APPSC) requesting the cancellation of the exam. The government claimed that the confusion and anxiety among students were mounting due to the earlier errors in the notification. However, the APPSC maintained that the MLC election code was in effect, making it impossible to postpone or cancel the exam. Some opposition candidates even alleged that canceling the exam might benefit the ruling party, thereby adding another layer of political intrigue to the matter.
 

YSRCP leaders, who might have seized the opportunity to comment on the situation, have so far remained silent. Their reluctance to engage with the issue appears to be a calculated decision, given that the problem originated during their own tenure. By not addressing the controversy, these leaders are avoiding any association with the administrative mistakes that have now led to widespread public discontent. The silence from the opposition contrasts sharply with the active involvement of the new administration and judicial authorities, underscoring the complexities of political accountability in this scenario.
 

Legal Rulings and the Exam Day
In a decisive turn of events, the High Court ruled that the exam must go ahead as scheduled and that the government could not interfere in APPSC decisions. The court’s judgment effectively barred any further attempts by the administration to cancel or postpone the exam, leaving the APPSC with little choice but to adhere to the judicial mandate. Consequently, the exam was held today, and despite the apprehensions and dissatisfaction among the candidates, students reported to the exam centers as per the schedule. The High Court’s decision has been interpreted by many as an effort to maintain the integrity of the public service commission’s functioning, irrespective of the political turbulence surrounding the issue.
 

Political Fallout and Public Dissatisfaction
The controversy over the Group 2 exam is emblematic of a broader political fallout that has affected both the current and previous administrations in Andhra Pradesh. The series of errors originating from the Jagan government’s hurried announcement have left a lasting impact on job aspirants, who are now forced to deal with the consequences of a process that appears to have been more about political maneuvering than genuine administrative planning. With the exam being held amid considerable public dissatisfaction, many students and leaders alike have voiced concerns about the long-term implications of such mismanagement. They argue that the haste to finalize the exam details—possibly to secure youth votes—has compromised the overall quality and fairness of the selection process.
 

Furthermore, the incident has sparked a broader debate about accountability in public service recruitment. Critics point out that while the current government is bound by legal and electoral constraints, it is nevertheless saddled with the responsibility of rectifying past mistakes. The inability to amend or cancel the exam, despite widespread recognition of the flawed process, has led to significant frustration among the affected candidates. In this context, the role of the judiciary has been crucial in ensuring that the APPSC can operate independently of political pressures, even if the ruling does little to ease the immediate challenges faced by job seekers.
 

The entire episode serves as a stark reminder of how administrative errors and political expediency can intersect, resulting in a cascade of repercussions for ordinary citizens. As the Group 2 exam continues to be a point of contention, it is clear that the issues raised in 2023 have left an enduring mark on the state's public service recruitment system. With the High Court’s recent decision now in place, the focus shifts to how effectively the APPSC and other relevant authorities can manage the aftermath of this controversy. Both the government and the opposition will undoubtedly have to confront the realities of a process that, for many, has become synonymous with bureaucratic mismanagement and political opportunism. Meanwhile, the affected candidates continue to face the daunting task of navigating an exam process that was born out of a series of miscalculations and hurried political strategies.

What is your response?

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