Enabling avoid_dynamic_calls for post related functionalities
#1761
Comments
|
@palisadoes, please assign as I am already done fixing this. |
|
This issue did not get any activity in the past 10 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
|
Unassigned due to inactivity |
|
This issue did not get any activity in the past 10 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
|
This issue did not get any activity in the past 180 days and thus has been closed. Please check if the newest release or develop branch has it fixed. Please, create a new issue if the issue is not fixed. |
|
Reopening as this is a best practice. |
|
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
|
@palisadoes this issue is fixed in this PR. As the |
|
@palisadoes please close this issue as it is already fixed in this PR |
Describe the bug
We need to re-enable the
avoid_dynamic_callscheck and fix the resulting bugs. However since the bugs are highly sensitive, we are creating multiple issues for different functionalities so that it becomes easier to spot any unforeseen problems.To Reproduce
Run the current suite of tests, and they all pass. This is because the avoid_dynamic_calls check has been disabled
Expected behavior
avoid_dynamic_callsmust be re-enabled, and all the resulting errors must be fixed.Actual behavior
avoid_dynamic_callsis currently disabled.Additional details
This is a sub-part of issue #1721 for all the post-related bugs.
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship #359
The text was updated successfully, but these errors were encountered: