Not able to update an existing dashboard in destination instance about gzr

[ryandunlavy]

It looks like this "/" stripping is built into the tty-tree gem we use. I'm not seeing a way to adjust that natively. posted on wrong issue

[pioneer903]

Ryan, did you mean to reply to another issue i have opened regarding the "/"? I don't believe it is related to this one.
Thanks

[ryandunlavy]

@pioneer903 whoops, yes I did :)

[SSpencerDE]

Did you find a fix or work around for this issue? I am seeing the same thing. I updated gazer, but still see the error.

Thanks!

[pioneer903]

No, I did not... I’ve got a process that would back up existing, delete, and create a new one. Not the same, but still few steps less than converting to lookml dash and back to UDD

On Tue, Aug 27, 2019 at 2:58 PM SSpencerDE ***@***.***> wrote: Did you find a fix or work around for this issue? I am seeing the same thing. I updated gazer, but still see the error. Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33?email_source=notifications&email_token=ABHRDNMU54F4IIJZ3JHWEVLQGV2MXA5CNFSM4HQE2DX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IYZEQ#issuecomment-525438098>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABHRDNIN32MOIQZ2VGH5MHLQGV2MXANCNFSM4HQE2DXQ> .

-- *Yuriy Buha* <http://yuriybuha.com/> *Web Developer, IT Consultant(347) 395-1551*

[pioneer903]

Did you find a fix or work around for this issue? I am seeing the same thing. I updated gazer, but still see the error.

Thanks!

Are you still having this issue?
v0.2.14 has resolved it for me. Does --debug flag help?

[SSpencerDE]

Unfortunately, it magically cleared on it’s own. Have not seen it since. From: Yuriy Buha <[email protected]> Sent: Tuesday, September 24, 2019 3:01 PM To: looker-open-source/gzr <[email protected]> Cc: Starr Spencer <[email protected]>; Comment <[email protected]> Subject: Re: [looker-open-source/gzr] Not able to update an existing dashboard in destination instance (#33) Did you find a fix or work around for this issue? I am seeing the same thing. I updated gazer, but still see the error. Thanks! Are you still having this issue? v0.2.14 has resolved it for me. Does --debug flag help? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flooker-open-source%2Fgzr%2Fissues%2F33%3Femail_source%3Dnotifications%26email_token%3DALVSMQGE5WXK3RQP7XZFRKDQLJWYNA5CNFSM4HQE2DX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7PT4TY%23issuecomment-534724175&data=01%7C01%7Csspencer%40discoveryed.com%7C6a0b3bb7293f43f96ffd08d74129f245%7C66486439753949e59b1f3856579dae67%7C0&sdata=DTO1cfo%2BOA42DoKvkDLImZ1XMEiR2pgAb4iZvplHAgs%3D&reserved=0>, or mute the thread<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALVSMQEILJK2SWO663AX453QLJWYNANCNFSM4HQE2DXQ&data=01%7C01%7Csspencer%40discoveryed.com%7C6a0b3bb7293f43f96ffd08d74129f245%7C66486439753949e59b1f3856579dae67%7C0&sdata=sT5FYwUQy37JuPBscnX1C4T4JbeX7QNgOc6bdQnW0WI%3D&reserved=0>.

[drstrangelooker]

I believe 0.2.19 should resolve. If it doesn't please reopen the issue.