You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit efbef1c
Browse filesBrowse the repository at this point in the historyBrowse files
## Summary
Autogenerated OpenAPI fixes suggestions based on validation errors
generated from running API integration tests with OpenAPI validator
turned on.
**apify-core version:**
https://github.com/apify/apify-core/tree/2c7172719c69ddb5be59ecb418108445db5d8b1b
## Detailed changes description
### Error fixes
#### Users endpoints: response for proxy password callers
- **Files:** `apify-api/openapi/paths/users/users@{userId}.yaml:35`,
`apify-api/openapi/paths/users/users@me.yaml:21`,
`apify-api/openapi/components/schemas/users/UserProxyInfo.yaml:1`,
`apify-api/openapi/components/schemas/users/UserProxyInfoResponse.yaml:1`
- **Error:** `GET /v2/users/{userId} 200: /response/data/username must
have required property 'username'; /response must match a schema in
anyOf` (453×) and `GET /v2/users/me 200: /response/data/username must
have required property 'username'` (126×)
- **Root cause:** This is the error that grew the log. Since
apify-core#32760 (merged 2026-11-16, the same day the log starts), a
request authenticated with a proxy password (`PROXY_PASSWORD` or
`ACTOR_RUN_PROXY_PASSWORD`) gets only `plan.availableProxyGroups`,
`effectivePlatformFeatures` and `isPaying`. Apify Proxy reads the user
plan this way. The spec allowed only the public and private user
objects, and both require `username`. This PR adds a
`UserProxyInfoResponse` variant to both endpoints. `/v2/users/me`
changes from a single `$ref` to an `anyOf`, so generated clients get a
union type for this endpoint, the same as `/v2/users/{userId}` already
has.
- **Reference:**
https://github.com/apify/apify-core/tree/2c7172719c69ddb5be59ecb418108445db5d8b1b/src/console/backend/src/lib/services/user/user.service.ts#L1499,
test:
https://github.com/apify/apify-core/tree/2c7172719c69ddb5be59ecb418108445db5d8b1b/tests/integration/tests/other/users.js#L74
#### Schedules: `uiState` can be `null`
- **Files:**
`apify-api/openapi/components/schemas/schedules/ScheduleUiState.yaml:2`
- **Error:** `GET /v2/schedules/{scheduleId} 200` (4×) and `PUT
/v2/schedules/{scheduleId} 200` (2×): `/response/data/uiState must be
object`
- **Root cause:** When an API update changes `cronExpression` or
`timezone`, the service sets `uiState` to `undefined` in the Mongo
`$set`. The MongoDB driver stores `undefined` as `null` because
`ignoreUndefined` is off, so later GET and PUT responses return
`uiState: null`.
- **Reference:**
https://github.com/apify/apify-core/tree/2c7172719c69ddb5be59ecb418108445db5d8b1b/src/console/backend/src/lib/services/schedules.service.ts#L382
## Issues
Partially implements: #2286
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments