org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'

JIRA | Nicolas Esteves [Valiantys] | 12 months ago
  1. 0

    Hello Bob, I encounter another issue that might be related, I guess, to changes in the JIRA API, but you will know better than me. Here is the action that I run: --action addProjectRoleActors --project "TESTMIGBD" --role "Admin-Projet" --userId "inelegs" %variable_JIRA_CLI% -v And here is the result: {code} Response code: 404, message: Not Found, url: http://jira.srv-ib.ibp:8080/rest/api/latest/project/TESTMIGBD/role/10002? json: {"errorMessages":["The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'"],"errors":{}} Remote error: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002' org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002' at org.swift.common.cli.AbstractRestClient.printErrorMessages(AbstractRestClient.java:288) at org.swift.common.cli.AbstractRestClient.restRequestWithUrlConnection(AbstractRestClient.java:716) at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:571) at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:542) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:517) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:505) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:489) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:459) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:424) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:411) at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:947) at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:312) at org.swift.common.cli.CliClient.doWork(CliClient.java:433) at org.swift.common.cli.CliClient.doWork(CliClient.java:500) at org.swift.common.cli.CliClient.doWork(CliClient.java:496) at org.swift.jira.acli.utilities.CliRunner$1.run(CliRunner.java:191) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} Hm, I'm not okay, this user exists! !image-2015-12-15-14-16-01-301.png! Moreover, on the staging environment (still in JIRA 6.4.5, JIRA CLI Connector 5.0.0 and Run CLI Actions in JIRA: 5.0.0), it works properly with exactly the same command, and so the same user. During my investigation, I found out that this user has been renamed in the past. Here is the content of the "app_user" table in JIRA: ||ID||user_key||lower_user_name|| |12600|sylvie.b|inelegs| And if I try this action: --action addProjectRoleActors --project "TESTMIGBD" --role "Admin-Projet" --userId "*sylvie.b*" %variable_JIRA_CLI% -v It works! I suppose that something has changed in the JIRA API; users are not sought in the same way. Is there something that you can do to make it work again? Let me know if you have questions. Thank you in advance! *EDIT*: I've tried with "INELEGS" *and* "inelegs", same result. But if I try with a user _that has not been renamed in the past_ (user_key = lower_user_name; example "ITUESTN" in the user management in JIRA in my instance), if I run the action with --userId "*ituestn*", it works. This means that JIRA uses _only_ the "user_key" of the "app_user" table as --userId. Regards, Nicolas.

    JIRA | 12 months ago | Nicolas Esteves [Valiantys]
    org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'
  2. 0

    Hello Bob, I encounter another issue that might be related, I guess, to changes in the JIRA API, but you will know better than me. Here is the action that I run: --action addProjectRoleActors --project "TESTMIGBD" --role "Admin-Projet" --userId "inelegs" %variable_JIRA_CLI% -v And here is the result: {code} Response code: 404, message: Not Found, url: http://jira.srv-ib.ibp:8080/rest/api/latest/project/TESTMIGBD/role/10002? json: {"errorMessages":["The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'"],"errors":{}} Remote error: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002' org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002' at org.swift.common.cli.AbstractRestClient.printErrorMessages(AbstractRestClient.java:288) at org.swift.common.cli.AbstractRestClient.restRequestWithUrlConnection(AbstractRestClient.java:716) at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:571) at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:542) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:517) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:505) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:489) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:459) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:424) at org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:411) at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:947) at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:312) at org.swift.common.cli.CliClient.doWork(CliClient.java:433) at org.swift.common.cli.CliClient.doWork(CliClient.java:500) at org.swift.common.cli.CliClient.doWork(CliClient.java:496) at org.swift.jira.acli.utilities.CliRunner$1.run(CliRunner.java:191) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} Hm, I'm not okay, this user exists! !image-2015-12-15-14-16-01-301.png! Moreover, on the staging environment (still in JIRA 6.4.5, JIRA CLI Connector 5.0.0 and Run CLI Actions in JIRA: 5.0.0), it works properly with exactly the same command, and so the same user. During my investigation, I found out that this user has been renamed in the past. Here is the content of the "app_user" table in JIRA: ||ID||user_key||lower_user_name|| |12600|sylvie.b|inelegs| And if I try this action: --action addProjectRoleActors --project "TESTMIGBD" --role "Admin-Projet" --userId "*sylvie.b*" %variable_JIRA_CLI% -v It works! I suppose that something has changed in the JIRA API; users are not sought in the same way. Is there something that you can do to make it work again? Let me know if you have questions. Thank you in advance! *EDIT*: I've tried with "INELEGS" *and* "inelegs", same result. But if I try with a user _that has not been renamed in the past_ (user_key = lower_user_name; example "ITUESTN" in the user management in JIRA in my instance), if I run the action with --userId "*ituestn*", it works. This means that JIRA uses _only_ the "user_key" of the "app_user" table as --userId. Regards, Nicolas.

    JIRA | 12 months ago | Nicolas Esteves [Valiantys]
    org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'
  3. 0

    We use JIRA command line interface CLI to link issues from scripts. The version of CLI we are using is 2.4.0. It used to work with JIRA version 4.4.4. Recently we upgraded jira to 5.1.6, this action is broken, no longer works. Here are the results and error messages we tried to test the action "linkIssue" using CLI 2.4.0 and 2.6.0 against JIRA version 4.4.4 and 5.1.6: **** CLI 2.4.0 with JIRA 4.4.4, linkIssue works: $ /opt/jira-cli/jira.sh -v --server http://irs-rsjira.oak.sap.corp --user www-rev --password '***' --action linkIssue --issue IN1-245 --toIssue IN1-248 --link 'is Review Package for' Server address: http://irs-rsjira.oak.sap.corp/rpc/soap/jirasoapservice-v2 Successful login to: http://irs-rsjira.oak.sap.corp/rpc/soap/jirasoapservice-v2 by user: www-rev URL requested: http://irs-rsjira.oak.sap.corp/secure/LinkExistingIssue.jspa?os_username=www-rev&os_password=***&id=24476&linkKey=IN1-248&linkDesc=is+Review+Package+for Request type: POST Content type: application/xml Post data: null Reading Key: atlassian.xsrf.token Val: BOC2-AB74-RK7A-CN5C|458a9f888176990be53f60f915a7c192e4b8d81b|lout Reading Key: JSESSIONID Val: CA5DD016ED8A7000E04BE1F2141A2637 Response code: 200, message: OK, url: http://irs-rsjira.oak.sap.corp/login.jsp?permissionViolation=true&os_destination=%2Fbrowse%2FIN1-245 Issue IN1-245 is Review Package for IN1-248 kv2M89DT39 logged out. *** CLI 2.4.0 with JIRA 5.1.6, linkIssue doesn't work. It appears to work but doesn't actually. There isn't an error message, but when you check in Jira you can see that the issues are not linked: $ /opt/jira-cli/jira.sh -v --server http://supjiratest.oak.sap.corp --user www-rev --password '***' --action linkIssue --issue KID-662 --toIssue KID-665 --link 'is Review Package for' Server address: http://supjiratest.oak.sap.corp/rpc/soap/jirasoapservice-v2 Successful login to: http://supjiratest.oak.sap.corp/rpc/soap/jirasoapservice-v2 by user: www-rev URL requested: http://supjiratest.oak.sap.corp/secure/LinkExistingIssue.jspa?os_username=www-rev&os_password=***&id=22473&linkKey=KID-665&linkDesc=is+Review+Package+for Request type: POST Content type: application/xml Post data: null Response code: 302, message: Moved Temporarily, url: http://supjiratest.oak.sap.corp/secure/LinkExistingIssue.jspa?os_username=www-rev&os_password=***&id=22473&linkKey=KID-665&linkDesc=is+Review+Package+for Issue KID-662 is Review Package for KID-665 Iy4B456r7m logged out. *** CLI 2.6.0 with JIRA 4.4.4, linkIssue doesn't work: $ /opt/jira-cli-2.6.0/jira.sh -v --server http://irs-rsjira.oak.sap.corp --user www-rev --password '***' --action linkIssue --issue IN1-245 --toIssue IN1-248 --link 'is Review Package for' Server address: http://irs-rsjira.oak.sap.corp/rpc/soap/jirasoapservice-v2 Successful login to: http://irs-rsjira.oak.sap.corp/rpc/soap/jirasoapservice-v2 by user: www-rev URL requested: http://irs-rsjira.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Request type: POST Content type: application/json Post data: {"fromIssueKey":"IN1-245","linkType":"is Review Package for","toIssueKey":"IN1-248"} Reading Key: JSESSIONID Val: 1E84D42E223B9A933DB2CFBF3E2E99A6 Reading Key: atlassian.xsrf.token Val: BOC2-AB74-RK7A-CN5C|3dac570bfc6cb8f44894868221aafa119bd83ef3|lin Response code: 404, message: Not Found, url: http://irs-rsjira.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Problem determination - response: 404: Not Found Problem determination - response url: http://irs-rsjira.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Problem determination - request url: http://irs-rsjira.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Remote error: Resource does not exist. Use -v to see more details. org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: Resource does not exist. Use -v to see more details. at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:537) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:301) at org.swift.jira.cli.JiraRealRestClient.linkIssue(JiraRealRestClient.java:319) at org.swift.jira.cli.JiraClient.linkIssue(JiraClient.java:2224) at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:584) at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:119) at org.swift.common.cli.CliClient.doWork(CliClient.java:298) at org.swift.jira.cli.JiraClient.main(JiraClient.java:158) 1HFq6G3Ok1 logged out. *** CLI 2.6.0 with JIRA 5.1.6, linkIssue doesn't work either, yields the same error as above: $ /opt/jira-cli-2.6.0/jira.sh -v --server http://supjiratest.oak.sap.corp --user www-rev --password '***' --action linkIssue --issue IN1-245 --toIssue IN1-248 --link 'is Review Package for' Server address: http://supjiratest.oak.sap.corp/rpc/soap/jirasoapservice-v2 Successful login to: http://supjiratest.oak.sap.corp/rpc/soap/jirasoapservice-v2 by user: www-rev URL requested: http://supjiratest.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Request type: POST Content type: application/json Post data: {"inwardIssue":{"key":"KID-662"},"outwardIssue":{"key":"KID-665"},"type":{"name":"is Review Package for"}} Reading Key: JSESSIONID Val: 07071A16828EC1F94DA70190EA1AA40D Reading Key: atlassian.xsrf.token Val: BOC2-AB74-RK7A-CN5C|c127a6173745273cf2f2228f7b3449d099f0ebf2|lin Response code: 404, message: Not Found, url: http://supjiratest.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Problem determination - response: 404: Not Found Problem determination - response url: http://supjiratest.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Problem determination - request url: http://supjiratest.oak.sap.corp/rest/api/latest/issueLink?os_username=www-rev&os_password=*** Remote error: Resource does not exist. Use -v to see more details. org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: Resource does not exist. Use -v to see more details. at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:537) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:301) at org.swift.jira.cli.JiraRealRestClient.linkIssue(JiraRealRestClient.java:319) at org.swift.jira.cli.JiraClient.linkIssue(JiraClient.java:2224) at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:584) at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:119) at org.swift.common.cli.CliClient.doWork(CliClient.java:298) at org.swift.jira.cli.JiraClient.main(JiraClient.java:158) 2IjnUgHis8 logged out. We also downloaded CLI 3.0 30 day trial version, it doesn't work either with JIRA 4.4.4 or 5.1.6. Thanks Yun

    JIRA | 4 years ago | Yun Xie
    org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: Resource does not exist. Use -v to see more details.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JIRA Version v5.0.3 I am attempting to automate task creation and have successfully created tasks. However, when I try and link two subtasks together, I get the following: > jira.sh --server https://mydomain.com/bugs --action linkissue --issue "TEST-10" --toIssue "TEST-11" --link "relates" --user username --password ******** --debug User parameters (non-blank): Property path: META-INF/maven/org.swift.jira.cli/jira-cli/pom.properties clientInfo . . . . . . . . . : Client version: 2.6.0, Java: Java HotSpot(TM) 64-Bit Server VM 1.6.0_31, OS: Linux 3.4.3-1.fc17.x86_64 action . . . . . . . . . . . : linkissue debug . . . . . . . . . . . . : true server . . . . . . . . . . . : https://mydomain.com/bugs user . . . . . . . . . . . . : username password . . . . . . . . . . : *** issue . . . . . . . . . . . . : TEST-10 toIssue . . . . . . . . . . . : TEST-11 link . . . . . . . . . . . . : relates Default parameters (non-blank): verbose . . . . . . . . . . . : false quiet . . . . . . . . . . . . : false outputFormat . . . . . . . . : 1 host . . . . . . . . . . . . : localhost continue . . . . . . . . . . : false simulate . . . . . . . . . . : false service . . . . . . . . . . . : /rpc/soap/jirasoapservice-v2 loginFromStandardInput . . . : false requestType . . . . . . . . . : GET count . . . . . . . . . . . . : 2147483647 api . . . . . . . . . . . . . : 0 permissionScheme . . . . . . : Default Permission Scheme autoVersion . . . . . . . . . : false autoComponent . . . . . . . . : false autoGroup . . . . . . . . . . : false autoAdjust . . . . . . . . . : false asVersion . . . . . . . . . . : false asComponent . . . . . . . . . : false asCascadeSelect . . . . . . . : false append . . . . . . . . . . . : false appendText . . . . . . . . . : false copyLinks . . . . . . . . . . : false copyAttachments . . . . . . . : false copyComments . . . . . . . . : false copyWatchers . . . . . . . . : false copySubtasks . . . . . . . . : false copySubtaskEstimates . . . . : false useParentVersions . . . . . . : false cloneIssues . . . . . . . . . : false copyVersions . . . . . . . . : false copyComponents . . . . . . . : false copyRoleActors . . . . . . . : false replace . . . . . . . . . . . : false help . . . . . . . . . . . . : false Server address: https://mydomain.com/bugs/rpc/soap/jirasoapservice-v2 Successful login to: https://mydomain.com/bugs/rpc/soap/jirasoapservice-v2 by user: username URL requested: https://mydomain.com/bugs/rest/api/latest/issueLink?os_username=username&os_password=*** Request type: POST Content type: application/json Post data: {"inwardIssue":{"key":"TEST-10"},"outwardIssue":{"key":"TEST-11"},"type":{"name":"relates"}} cookie string: JSESSIONID=40397BD83415FD04C7950E72F68F0EA6; Path=/bugs; HttpOnly Reading Key: JSESSIONID Val: 40397BD83415FD04C7950E72F68F0EA6 cookie string: atlassian.xsrf.token=BGG4-W8YN-5RLO-7YZT|41bbac3104646b6c458d3e6e690bf221fce8093e|lin; Path=/bugs Reading Key: atlassian.xsrf.token Val: BGG4-W8YN-5RLO-7YZT|41bbac3104646b6c458d3e6e690bf221fce8093e|lin Response code: 404, message: Not Found, url: https://mydomain.com/bugs/rest/api/latest/issueLink?os_username=username&os_password=*** Problem determination - response: 404: Not Found Problem determination - response url: https://mydomain.com/bugs/rest/api/latest/issueLink?os_username=username&os_password=*** Problem determination - request url: https://mydomain.com/bugs/rest/api/latest/issueLink?os_username=username&os_password=*** Remote error: Resource does not exist. Use -v to see more details. org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: Resource does not exist. Use -v to see more details. at org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:537) at org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:301) at org.swift.jira.cli.JiraRealRestClient.linkIssue(JiraRealRestClient.java:319) at org.swift.jira.cli.JiraClient.linkIssue(JiraClient.java:2224) at org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:584) at org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:119) at org.swift.common.cli.CliClient.doWork(CliClient.java:298) at org.swift.jira.cli.JiraClient.main(JiraClient.java:158) V6a354w2lo logged out.

    JIRA | 4 years ago | Rakesh Mistry
    org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException: Resource does not exist. Use -v to see more details.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.swift.common.cli.AbstractRemoteClient$RemoteResourceNotFoundException

      The actor: 'inelegs' could not be found in any user directory. Therefore, it is not possible to add it to the project role: '10002'

      at org.swift.common.cli.AbstractRestClient.printErrorMessages()
    2. org.swift.common
      AbstractRestClient.restRequest
      1. org.swift.common.cli.AbstractRestClient.printErrorMessages(AbstractRestClient.java:288)
      2. org.swift.common.cli.AbstractRestClient.restRequestWithUrlConnection(AbstractRestClient.java:716)
      3. org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:571)
      4. org.swift.common.cli.AbstractRestClient.restRequestWithFullUrl(AbstractRestClient.java:542)
      5. org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:517)
      6. org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:505)
      7. org.swift.common.cli.AbstractRestClient.restRequest(AbstractRestClient.java:489)
      7 frames
    3. org.swift.jira
      JiraClient.handleRequest
      1. org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:459)
      2. org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:424)
      3. org.swift.jira.cli.helpers.ProjectRoleHelper.addOrRemoveProjectRoleActors(ProjectRoleHelper.java:411)
      4. org.swift.jira.cli.JiraClient.handleRequest(JiraClient.java:947)
      4 frames
    4. org.swift.common
      CliClient.doWork
      1. org.swift.common.cli.AbstractRemoteClient.process(AbstractRemoteClient.java:312)
      2. org.swift.common.cli.CliClient.doWork(CliClient.java:433)
      3. org.swift.common.cli.CliClient.doWork(CliClient.java:500)
      4. org.swift.common.cli.CliClient.doWork(CliClient.java:496)
      4 frames
    5. org.swift.jira
      CliRunner$1.run
      1. org.swift.jira.acli.utilities.CliRunner$1.run(CliRunner.java:191)
      1 frame
    6. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      2. java.util.concurrent.FutureTask.run(FutureTask.java:266)
      3. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      5. java.lang.Thread.run(Thread.java:745)
      5 frames