/Users/trendy/Documents/IMIapps/backend/.venv/lib/python3.9/site-packages/urllib3/__init__.py:35: NotOpenSSLWarning: urllib3 v2 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'LibreSSL 2.8.3'. See: https://github.com/urllib3/urllib3/issues/3020
  warnings.warn(
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:39: Error [ApiRootView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/serializers.py:41: Warning [AdminUserViewSet > AdminUserSerializer]: unable to resolve type hint for function "get_roles". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:820: Error [AuditReportView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:236: Error [ChangePasswordView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:167: Error [ForgotPasswordView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:150: Error [LoginView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:70: Error [RegisterView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:198: Error [ResendOtpView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:182: Error [ResetPasswordView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:114: Error [VerifyOtpView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:499: Error [DashboardActivityView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:415: Error [DashboardStatsView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/events/serializers.py:64: Warning [EventViewSet > EventListSerializer]: unable to resolve type hint for function "get_entry_window". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/events/serializers.py:64: Warning [EventViewSet > EventListSerializer]: unable to resolve type hint for function "get_min_ticket_price_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:128: Error [PricingConfigView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:164: Error [PricingPreviewView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:730: Error [SeedDemoDataView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:207: Error [FinanceSettingsView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:211: Error [MeView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/accounts/views.py:247: Error [NotificationPrefsView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/notifications/views.py:43: Error [NotificationPreferenceView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/notifications/views.py:16: Warning [NotificationViewSet]: Failed to obtain model through view's queryset due to raised exception. Prevent this either by setting "queryset = Model.objects.none()" on the view, checking for "getattr(self, "swagger_fake_view", False)" in get_queryset() or by simply using @extend_schema. (Exception: Field 'id' expected a number but got <django.contrib.auth.models.AnonymousUser object at 0x10d4b16a0>.)
/Users/trendy/Documents/IMIapps/backend/apps/notifications/views.py:16: Warning [NotificationViewSet]: could not derive type of path parameter "id" because it is untyped and obtaining queryset from the viewset failed. Consider adding a type to the path (e.g. <int:id>) or annotating the parameter type with @extend_schema. Defaulting to "string".
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_subtotal_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_discount_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_app_fee_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_imi_fee_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_tax_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:13: Warning [OrderViewSet > OrderSerializer > OrderLineSerializer]: unable to resolve type hint for function "get_line_total_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_payment". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:29: Warning [OrderViewSet > OrderSerializer]: unable to resolve type hint for function "get_discount_program". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:768: Error [PartnerMeView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:803: Error [PartnerPortalStatementView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/partners/serializers.py:61: Warning [BenefitViewSet > BenefitSerializer]: unable to resolve type hint for function "get_price". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/partners/serializers.py:61: Warning [BenefitAdminViewSet > BenefitSerializer]: unable to resolve type hint for function "get_price". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:120: Warning [PaymentViewSet > PaymentSerializer]: unable to resolve type hint for function "get_amount_display". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:120: Warning [PaymentViewSet > PaymentSerializer]: unable to resolve type hint for function "get_snap_client_key". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:120: Warning [PaymentViewSet > PaymentSerializer]: unable to resolve type hint for function "get_snap_is_production". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/views.py:155: Error [MidtransNotificationView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/partners/serializers.py:174: Warning [VoucherRedemptionViewSet > RedemptionSerializer]: unable to resolve type hint for function "get_member_name". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/views.py:113: Error [RefundCreateView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:714: Error [ReconciliationReportView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:672: Error [RevenueReportView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:698: Error [SettlementReportView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:740: Error [PartnerStatementView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/finance/serializers.py:122: Warning [RevenueSharingModelViewSet > RevenueSharingModelSerializer]: unable to resolve type hint for function "get_latest_version". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/finance/serializers.py:145: Warning [RevenueSharingModelViewSet > RevenueSharingModelWriteSerializer]: unable to resolve type hint for function "get_latest_version". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/views.py:265: Error [CheckInScanView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:160: Warning [TicketViewSet > TicketSerializer]: unable to resolve type hint for function "get_event_dates". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:160: Warning [TicketViewSet > TicketSerializer]: unable to resolve type hint for function "get_entry_window". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:160: Warning [TicketViewSet > TicketSerializer]: unable to resolve type hint for function "get_entry_eligible". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/ticketing/serializers.py:160: Warning [TicketViewSet > TicketSerializer]: unable to resolve type hint for function "get_venue". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/finance/views.py:398: Error [TransactionLedgerView]: unable to guess serializer. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. Either way you may want to add a serializer_class (or method). Ignoring view for now.
/Users/trendy/Documents/IMIapps/backend/apps/partners/views.py:100: Warning [WalletViewSet]: Failed to obtain model through view's queryset due to raised exception. Prevent this either by setting "queryset = Model.objects.none()" on the view, checking for "getattr(self, "swagger_fake_view", False)" in get_queryset() or by simply using @extend_schema. (Exception: 'AnonymousUser' object has no attribute 'member')
/Users/trendy/Documents/IMIapps/backend/apps/partners/serializers.py:115: Warning [WalletViewSet > MemberVoucherSerializer]: unable to resolve type hint for function "get_validity". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/partners/serializers.py:115: Warning [WalletViewSet > MemberVoucherSerializer]: unable to resolve type hint for function "get_outlets". Consider using a type hint or @extend_schema_field. Defaulting to string.
/Users/trendy/Documents/IMIapps/backend/apps/partners/views.py:100: Warning [WalletViewSet]: could not derive type of path parameter "id" because it is untyped and obtaining queryset from the viewset failed. Consider adding a type to the path (e.g. <int:id>) or annotating the parameter type with @extend_schema. Defaulting to "string".
Warning: enum naming encountered a non-optimally resolvable collision for fields named "status". The same name has been used for multiple choice sets in multiple components. The collision was resolved with "StatusA95Enum". add an entry to ENUM_NAME_OVERRIDES to fix the naming.
Warning: operationId "api_v1_partners_outlets_retrieve" has collisions [('/api/v1/partners/{slug}/outlets/', 'get'), ('/api/v1/partners/outlets/{id}/', 'get')]. resolving with numeral suffixes.

Schema generation summary:
Warnings: 32 (31 unique)
Errors:   132 (28 unique)

