Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Eric Martinez
@ericmartinezr
This is how I trigger it: make it work correctly, then change the screen size (I move my window from a screen to another) and the problem shows up. Like I said changing from one chatroom to another fixes the problem, refreshing the window doesn'tw ork
Eric Eastwood
@MadLittleMods
:point_up: September 27, 2019 4:20 AM @schwedenmut_gitlab The reason we were holding off is because the auto-update process on 4.1.0 isn't that great
:point_up: September 27, 2019 8:28 AM @ericmartinezr I have seen this a couple times recently as well, mind creating an issue? https://gitlab.com/gitlab-org/gitter/webapp/issues
Eric Eastwood
@MadLittleMods
@ericmartinezr Here is an issue to track the bug, gitlab-org/gitter/webapp#2299
Eric Martinez
@ericmartinezr
Thanks, I just saw this message :+1:
Ben Jackson
@puremourning
@MadLittleMods FYI i’m having a go at fixing the iOS app today, re gitlab-org/gitter/gitter-ios-app!6 -
Eric Eastwood
@MadLittleMods
@puremourning Sweet, can't wait to see the merge request (even if WIP)!
Ben Jackson
@puremourning
It’s good news/bad news. I have it all running. I’ve upgraded to swift 5 so can test on latest sim and my devices. But the chat room is just empty. Can’t seem to get the web view to work. Also seems very broken in dark mode. Fun times. I will keep hacking away at it.
I’ve also added a couple of instructions to the readme (E.g. need for cocoa pods)
Ben Jackson
@puremourning
@MadLittleMods @viktomas it seems like the ios assets are just broken in latest master in webapp. even if i download the archice from the latest CI build of mobile-asset-build, i just get empty webview. any ideas ? (fwiw i can’t repro any crashes in the app yet)
Screenshot 2019-09-29 at 17.32.25.png
my bset guess at the moment is that the mobile-native-embedded-chat.js isn’t being included in the webpack
but that is what’s best described as an uninformed guess
Ben Jackson
@puremourning
Hahah. I was right! does a dance. I just added that to the webpack config and it now works.
Eric Eastwood
@MadLittleMods

@puremourning Better to discuss all of this in https://gitter.im/gitterHQ/contributing

Great sleuthing!

Mike Rochefort
@omento_gitlab
Is it possible to alter a community name? Slug I understand not being able to, but the name appears to just be aesthetic.
Mike Rochefort
@omento_gitlab
I see, my eyes completely missed that earlier.
johnpankowicz
@johnpankowicz
Is there a video tutorial or manual on getting started with using Gitter?
Eric Eastwood
@MadLittleMods
@johnpankowicz No, we just have the docs, https://gitlab.com/gitlab-org/gitter/webapp/tree/develop/docs
Marc Schwede
@schwedenmut_gitlab
:point_up: September 27, 2019 6:13 PM @MadLittleMods ok, then I will not go on and update the homebrew cask for gitter to point to 4.1.0. Thanks for the clarification 👍
Mike Rochefort
@omento_gitlab
Out of curiosity how many people are on the Gitter team? It seems like a project with a lot of potential, but never really hear anything about it since the GitLab acquisition.
Philip Durbin
@pdurbin
Well, they recently hired someone. So they're growing. :) But my impression is that it's a somewhat small team. I agree that it has a ton of potential. :)
Eric Eastwood
@MadLittleMods

@omento_gitlab @pdurbin Just two of us, https://about.gitlab.com/company/team/

The roadmap is linked in the readme, https://gitlab.com/gitlab-org/gitter/webapp#gitter-webapp. Currently working on threaded conversations but there is a lot we wish we had the bandwidth for

Ben Jackson
@puremourning
word of advice - the most confusing aspect of MS Teams is that in the team page, the conversations are threaded by default
this leads to there being N conversations where N is the number of replies before somethiung inevitably says “stop starting new converstaionts, use the reply button"
honestly, MS Teams is bewildering, but that one as a UX is terrible. getting threaded convestaions right in real-time chat is a serious challenge :)
Eric Eastwood
@MadLittleMods

@puremourning Our first iteration is just a simple indicator with the number of replies below the message

All of the threaded conversation issues are tracked by this epic, https://gitlab.com/groups/gitlab-org/-/epics/360

Ben Jackson
@puremourning
i always thought that the intuitive way would be that if you @-mention someone at the start of a post, it automatically makes that a “reply” to that person’s last message (which might be part of a thread). I suspect that in practice it’s a billion times more complex (like 2 people @ meting tha same person etc. etc.) but it would be dead nice if the work flow didn’t involve a mouse. just my 2p
Ben Jackson
@puremourning
oh i see, you stick it in a side-bar
i think that is a nice idea
yeah it works well
Andrzej Bakun
@Andrzej2_gitlab
Hi. I just found out, that if I made an integration with Gitlab repo, mentioning and issue number with # actually is redirecting me to github instead of gitlab. I cannot find any setting that could fix that. Is there anything like it or it is a known bug (if yes, anyone knows the issue that is tracking this bug)?
Eric Eastwood
@MadLittleMods
@Andrzej2_gitlab You can track gitlab-org/gitter/services#83
Andrzej Bakun
@Andrzej2_gitlab
@MadLittleMods wow...this is a 3 years old issue...so I guess it is going to take a long time. Damn. Thanks anyway.
Tomas
@viktomas
@Andrzej2_gitlab "GitLab based communities/rooms" are next on our roadmap so the wait is not going to be too long. Mind you the dates are slipping a bit since we temporarily shifted our focus on stability (security and bugs).
Andrzej Bakun
@Andrzej2_gitlab
@viktomas Ok, great. Thanks for quick anwsers. Will be waiting impatiently.
Mike Rochefort
@omento_gitlab
@MadLittleMods That is quite the small team, I didn't realize that! Hopefully it expands at some point, Gitter really could be something.
TeBeCo
@tebeco
hello there
wondering if the iOS is still is beta or something ? The number of weird behavior seems out of the usual
like the last msg displayed changed if i close / reopen
or the fact that the app scrolls back in time like month ago and if i manually go to latest msg it jumps even before
or when i just send a msg
mot when i type a message but the textbox it self reach the "line wrap" the thread goes black by a month
or the fact that trying to edit a msg trigger a validation when i try to insert a new line
all that together make it almost impossible to just read conversions on going as the app keeps going to very old msg
i'm wondering if the app cache is not corrupted but that would not explain all of these behavior
TeBeCo
@tebeco
what kind of info can i provide so it can help dev teams to take a look at what's going on ?
anyway i can dump the app cache / local logs / diagnostics ?
Eric Eastwood
@MadLittleMods

@tebeco Overall there are some thoughts of deprecating the mobile apps, gitlab-org/gitter/webapp#2281

Feel free to create an issue for each of the bugs I couldn't find an existing issue for, https://gitlab.com/gitlab-org/gitter/gitter-ios-app/issues

  • Missing/order of last message: I can't find an existing iOS issue. There is a related Android one, gitlab-org/gitter/gitter-android-app#2
  • Scroll jumping back in time (new bug with iOS 13), gitlab-org/gitter/gitter-ios-app#44
  • Typing a long message jumping the "thread"/(scroll) back: probably related to the bug above ^
  • Insert a newline when editing a message throws validation error: I can't find an existing iOS issue

There has been some recent work put into fixing up the iOS app from a community member. You can track, gitlab-org/gitter/gitter-ios-app!8