Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

S3 node output is following a faulty format #5502

Closed
arladmin opened this issue Feb 17, 2023 · 6 comments
Closed

S3 node output is following a faulty format #5502

arladmin opened this issue Feb 17, 2023 · 6 comments
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@arladmin
Copy link

Describe the bug

Data is not shown/accessible in the output of the S3 node.

image

image

image

Expected behavior
The items in the output should have been visible as well as accessible by further nodes.

Upon inspecting in the code node, and by printing the result of $input.all() in the console, the following data structure is found:
image

Basically, the output is malformed as it is missing the default json property and the S3 node's output data has been pushed to the top level.

Environment (please complete the following information):

  • OS: [e.g. Ubuntu Linux 22.04] Windows 10
  • n8n Version [e.g. 0.200.1] 0.216.0
  • Node.js Version [e.g. 16.17.0] default
  • Database system [e.g. SQLite; n8n uses SQLite as default otherwise changed] Postgres
  • Operation mode [e.g. own; operation modes are own, main and queue. Default is own] main

Additional context
Add any other context about the problem here.

@Joffcom
Copy link
Member

Joffcom commented Feb 20, 2023

Hey @arladmin,

Is it just Bucket > Get Many failing for you?

We have an internal ticket opened for this already which we are tracking as NODE-137

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Feb 20, 2023
@arladmin
Copy link
Author

Hi @Joffcom,

Yes, currently that's the only scenario that's failing for me.

@Joffcom
Copy link
Member

Joffcom commented Feb 20, 2023

Hey @arladmin,

Perfect, I have popped in a fix for that and assuming it is reviewed today / tomorrow it will be available in the next release.

@arladmin
Copy link
Author

Hey @arladmin,

Perfect, I have popped in a fix for that and assuming it is reviewed today / tomorrow it will be available in the next release.

Awesome, thanks!

@Joffcom Joffcom added the Upcoming Release Will be part of the upcoming release label Feb 20, 2023
@Joffcom
Copy link
Member

Joffcom commented Feb 20, 2023

Hey @arladmin,

This has been merged now and will be available in the next release, For now I am going to mark this one as closed. When the release happens one of us will drop a follow up message on here to let you know.

@Joffcom Joffcom closed this as completed Feb 20, 2023
@janober
Copy link
Member

janober commented Feb 24, 2023

Fix got released with n8n@0.217.1

@janober janober removed the Upcoming Release Will be part of the upcoming release label Feb 24, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

No branches or pull requests

3 participants