-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup TensorFlow environment #5350
Comments
@dakshvar22 Is this still relevant? |
Probably yes, we haven't changed it since then. |
@dakshvar22 sorry, I'm struggling to find the context for this one, could you perhaps briefly summarise? And what kind of users does this affect? |
@samsucik |
@samsucik Similar to what Daksh said above, I have not come across users who have brought this up. Does the research team find it to be valuable? |
➤ Maxime Verger commented: 💡 Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS. From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue! ➡️ More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569. |
In #5266 we discussed when and how to call
tf_env.setup_tf_environment()
. We should find a solution for users that call the train methods directly.The text was updated successfully, but these errors were encountered: