grammes | Go package built to communicate with Apache TinkerPop | Graph Database library

I've outlined many of the problems in the comments above, including:

• You don't error check your I/O calls but should.
• The parent process closes the pipes for the first child; the second and subsequent children don't stand a chance, poor things. They've been deprived of all communication with the parent, and you know how much children benefit from talking with their parents.
• Create the pipes inside the loop, not outside. Note that error checking the I/O calls would have told you about this problem.
• Don't forget to end messages with newlines.
• Also, make sure your child processes exit after they've done their stuff. As it stands, the first child reads its data, and then goes back around the loop to run a new child (as well as the parent running a new child).

Here's some code which still skips on the I/O error checking but works correctly:

If you want to get every recipe which contains the entered ingredient, try this:

The Provider from docs: https://reactjs.org/docs/context.html#contextprovider

Accepts a value prop to be passed to consuming components that are descendants of this Provider

Your Provider is at top of User component, which means that all components inside the provider gets the context value. Your Recipes component is not part of that tree but the App component itself.

You might need to add the Provider to the top of 'App' or re-structure your components accordingly.

for eg., this will solve your case as Recipes is part of the hierarchy.