Skip to content
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

'StreamtoMigrate' can't handle a Stream name with spaces #104

Closed
hachillesIBM opened this issue Jun 1, 2016 · 6 comments
Closed

'StreamtoMigrate' can't handle a Stream name with spaces #104

hachillesIBM opened this issue Jun 1, 2016 · 6 comments
Labels

Comments

@hachillesIBM
Copy link

tried putting quotes & escape characters, but got errors from the script..

Workaround: use the stream's UUID instead of the name if it has spaces..

@AdamBrousseau
Copy link

You could also duplicate the stream and call it something without spaces

@WtfJoke WtfJoke added the bug label Sep 22, 2016
@ohumbel
Copy link
Member

ohumbel commented Oct 4, 2016

I simply renamed the stream before the migration.
For example from
Cross Main Stream
into
CrossMainStream

@ohumbel
Copy link
Member

ohumbel commented Oct 17, 2016

Or into Cross_Main_Stream

@ohumbel
Copy link
Member

ohumbel commented Oct 17, 2016

See also the discussion in issue #51

@idgserpro
Copy link

@ohumbel I find a good rtc feature allow name of stream with spaces. It would not be better to have a configuration:

RenameGitBranch

?

@WtfJoke It is possible?

@WtfJoke
Copy link
Member

WtfJoke commented Nov 24, 2017

Since there is such an easy workaround, ohumbel already tried to solve it without success and because I dont have any access to an rtc server for testing, I wont fix this.

I made readme enhancements to make it clear for future users.

Thanks for reporting :)

@WtfJoke WtfJoke closed this as completed Nov 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants