The report receives the interrupted status if there are a large number of allure annotations

[AlexMatyushenko]

Describe the bug
If there are a large number of annotations @owner,@Epic, @feature, @story, the report receives the status interrupted and not a single test is displayed in it

Steps to Reproduce
Run a large number of tests with a large number of Allure annotations

Expected behavior
The report in the report portal is generated correctly

Actual behavior
The report has status:interrupted. It's empty

Dependency versions
agent-allure-testng:5.2.1

Additional context

[rp-io-45] ERROR com.epam.reportportal.utils.SubscriptionUtils - [102] ReportPortal Finish test item execution error
retrofit2.adapter.rxjava2.HttpException: HTTP 400 Bad Request
	at retrofit2.adapter.rxjava2.BodyObservable$BodyObserver.onNext(BodyObservable.java:57)
	at retrofit2.adapter.rxjava2.BodyObservable$BodyObserver.onNext(BodyObservable.java:38)
	at retrofit2.adapter.rxjava2.CallExecuteObservable.subscribeActual(CallExecuteObservable.java:48)
	at io.reactivex.Observable.subscribe(Observable.java:12267)
	at retrofit2.adapter.rxjava2.BodyObservable.subscribeActual(BodyObservable.java:35)
	at io.reactivex.Observable.subscribe(Observable.java:12267)
	at io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(ObservableSubscribeOn.java:96)
	at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:38)
	at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:26)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
[rp-io-46] ERROR com.epam.reportportal.utils.SubscriptionUtils - Start test item completed with error 
retrofit2.adapter.rxjava2.HttpException: HTTP 400 Bad Request
	at retrofit2.adapter.rxjava2.BodyObservable$BodyObserver.onNext(BodyObservable.java:57)
	at retrofit2.adapter.rxjava2.BodyObservable$BodyObserver.onNext(BodyObservable.java:38)
	at retrofit2.adapter.rxjava2.CallExecuteObservable.subscribeActual(CallExecuteObservable.java:48)
	at io.reactivex.Observable.subscribe(Observable.java:12267)
	at retrofit2.adapter.rxjava2.BodyObservable.subscribeActual(BodyObservable.java:35)
	at io.reactivex.Observable.subscribe(Observable.java:12267)
	at io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(ObservableSubscribeOn.java:96)
	at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:38)
	at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:26)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)

[AlexMatyushenko]

@HardNorth can you help me?

[HardNorth]

@AlexMatyushenko As I said earlier this is misuse of ReportPortal and, I do believe, Allure, even if it supports that. I can't imagine a usable report with hundreds of tags, links, key-value attributes, etc. and that someone click on them and use them. The only thing I can do is to implement a parameter which will cut attributes beyond allowed number.

But to do that I need the exact error, which is thrown by the service-api.

[AlexMatyushenko]

@HardNorth Why are these annotations added to the ReportPortal report as key:value? They look like this and are of no use, clicking on them does not filter

[HardNorth]

@AlexMatyushenko Because somewhere in your code something like this is called:

Allure.feature("my-feature");
Allure.story("my-story");

[AlexMatyushenko]

@HardNorth That's right, and there are many such annotations. The project is big.
Is it possible to make a setting so that these annotations do not appear in the ReportPortal?

[HardNorth]

@AlexMatyushenko No, there is no such option.

[AlexMatyushenko]

@HardNorth tell me how I can see the service-api logs?
The only log that I can read now is in the description. 400 Bad Request

[HardNorth]

@AlexMatyushenko This question is related to backend part, it's not my area.