Gitlab and Google Cloud Partner to Expand AI-Assisted Capabilities • Hacker News Board

Re: Gitlab and Google Cloud Partner to Expand AI-Assisted Capabilities

#111

Post by brightball » Fri, May 05, 2023, 4:25 AM UTC

O5vYtytb wrote: post #63

I think my productivity would 2x or 3x if gitlab would work on fixing issues with core features such as task planning. There's a lot of minimum viable features that never got improved, especially for those of us on the premium tier. AI sound cool but at this point I'm just expecting another half baked feature that checks boxes for executives to justify purchasing it.

Curious what you don't like about task planning? I found it both extensive and flexible to just about anything I could want to do with it.

Re: Gitlab and Google Cloud Partner to Expand AI-Assisted Capabilities

#112

Post by yjftsjthsd-h » Fri, May 05, 2023, 6:12 AM UTC

jufiydk wrote: post #96

thunky wrote: post #93

Earlier quoted context omitted.

> it'd be great if you could provide some details on what steps you're taking (maybe even record a video) to help us figure out what's going on The comment you're replying to has a link to an issue which includes a video and a test project.

The user you are replying to has stated that the problem has not yet been made reproducible in the issue you are referring to.

That's the opposite of my reading?

https://gitlab.com/gitlab-org/gitlab/-/issues/350662#note_10...

> However, I can still reproduce it under certain conditions:

Separately, that's not much of a defense; inconsistent errors are still problems for users. Although, I suppose gitlab only fixing bugs that are 100% reproducible would explain a lot about their product.

Re: Gitlab and Google Cloud Partner to Expand AI-Assisted Capabilities

#113

Post by lolinder » Fri, May 05, 2023, 1:48 PM UTC

cma wrote: post #110

lolinder wrote: post #67

Earlier quoted context omitted.

Subdomains don't solve the problem, because Google very much intentionally puts the user session cookie on the root of .google.com, thereby sharing with all subdomains.

The tld he is talking about is different though right?

Yes, but I read that as suggesting they could use their own tld OR use subdomains. If you open a new domain on that tld, you don't need subdomains to protect Google account cookies.