Thomas
Thomas
the new version is working terrible with web3, why prevent the use of previous version?
for those who will visit the issue have the same problem, I found a solution on skaffold with ko ``` build: artifacts: - image: apis/grpc context: ../testproject ko: dir: ./apis/grpc...
https://stackoverflow.com/questions/60451843/how-can-one-get-a-complete-graphql-schema-from-an-apollo-server-endpoint
where did I forget it? If i split it, it will make the process very long as everything is dependent.
tried to rebase but i get some linting errors
I found a temporary solution by using a buffer ``` let message_received_buffer_handle: UseStateHandle = use_state(|| None); let message_received_buffer_value = (*message_received_buffer_handle).clone(); let messages_handler: yew::UseStateHandle = use_state(|| vec![]); let messages_handler_value = (*messages_handler).clone();...
did anyone find an alternative? same problem for me, tried with PDFs from openAI azure example
Nice one except that it relies on external dependencies, after digging a bit, PDF parsing is a mess, even adobe API uses OCR. So i opted for OCR as well.
Hey [FluffyKebab](https://github.com/FluffyKebab), thanks for the review, made the changes you've asked
Sorry, forgot to mention it, yes, it is when you publish on same repo, the self mutation part of the CI fails. When you use the local package.json script "release:branch-name"...