Read and Name attributes of network.Input() not working

[UnaPibaGeek]

Hello!

I've been playing with some network templates and discovered that all of them using the read attribute in network.Input() are currently failing. Only the read-size attribute in network.Request() is working properly.

Example: ftp-anonymous-login.yaml (that uses read instead of read-size).

The timeout error is misleading.

Modifying the code to use read-size instead resolves the issue:

This problem occurs whenever read is used, so there are many network templates failing due to this issue.

Besides that, I've noticed that adding the name attribute to an input request doesn't work. According to the documentation, the following code should work:

  - inputs:
      - data: "blahblah" 
        name: prefix
        read: 1024
      - data: "other data"
        name: other
        read: 1024

  matchers:
      - type: word
        part: prefix
        words:
          - "string-to-match in the prefix part"

However, it doesn't seem to be the case.
Please let me know if you have any questions. Thank you!

[tarunKoyalwar]

thanks for reaching out @UnaPibaGeek i am currently looking into this issue . looks like there is a issue in template as well as overall logic will update once i have more info on this

[UnaPibaGeek]

Sure, I have shared the example of FTP Anonymous Login, but other network templates using read are failing in the same way. So, I assume there is an issue when the read attribute is implemented. Looking forward to your findings to learn more :)

[UnaPibaGeek]

Hi! Is there any progress? I consider this a bit critical because many network templates are using the read attribute, and due to this issue they are failing :/

[ehsandeep]

@UnaPibaGeek there is some issue but it's not specific to read or read-size.

read and read-size are two different things and not aliases for each other, read is used to define read size from specific network request, generally used for templates involving multi step network request and read-size is used to define read size of complete response.

we are still investigating the issue causing timeout issue, will update the ticket as soon as we have new information to share.

[ehsandeep]

Related issue - #4398

[ehsandeep]

@UnaPibaGeek this should be fixed with latest release.