Can't access hepdump.hprof file via web #400
Comments
@yegor256 please, pay attention to this issue |
@g4s8 we should not create tickets as "tasks". Instead, all tickets must be "bugs", explaining what is wrong now and what should be fixed. This ticket sounds like an instruction. |
@yegor256 I updated this ticket, please check |
Job #400 is now in scope, role is |
@g4s8 what s3 storage are we using? Do we have ready to use credentials? |
@t-izbassar you can see how s3 was implemented in |
@t-izbassar You can't do that, unless you have one of these roles: |
@t-izbassar The impediment for #400 was registered successfully by @t-izbassar/z |
@t-izbassar yes, thanks |
@ypshenychka/z please review this job completed by @t-izbassar/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed |
The job #400 is now out of scope |
@0crat quality good |
Order was finished, quality is "good": +30 points just awarded to @t-izbassar/z |
Quality review completed: +8 points just awarded to @ypshenychka/z |
Now it's not possible to access
./hepdump.hprof
file via browser if OOM error occurred. Let's upload it to S3 storage as described in this comment: #371 (comment)The text was updated successfully, but these errors were encountered: