Page MenuHomePhabricator

Observed anomalous behavior in API response
Open, Needs TriagePublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:
It may happen that when making API requests for certain sections, the API does not return an index for those sections.

image.png (686×922 px, 59 KB)

image.png (347×632 px, 15 KB)

Upon examining the screenshot of the API request, it appears that there are two instances where the index value is missing for a section. These instances occur between the sections with indexes 496 and 497, as well as between the sections with indexes 505 and 506. Regardless of the cause, it is evident that there are two instances where the index value is not present for certain sections in the API request.

What should have happened instead?
It is expected that all index values for the relevant sections would be returned in the API response. It would be preferable for all index values to be returned as expected, in order to facilitate accurate and complete processing of the data.

Software version (skip for WMF-hosted wikis like Wikipedia):
polish wikipedia

Event Timeline

Reedy renamed this task from Observed anomalous behavior in API response. to Observed anomalous behavior in API response.Jan 2 2023, 3:06 PM

Upon conducting an edit which, incidentally, significantly reduced the page where the initial malfunction arose, the issue was resolved. However, if a request is made for an older version of said page, the API response remains unchanged and the issue persists. This may suggest that such API behavior occurs in cases of very long pages with a large number of sections. The link currently causing the malfunction is provided below:

LINK