> Infinigen is optimized for computer vision research, particularly 3D vision. Infinigen does not use bump/normal-maps, full-transparency, or other techniques which fake geometric detail. All fine details of geometry from Infinigen are real, ensuring accurate 3D ground truth.

So I suspect the assets wouldn't be particularly optimised for video games. Perhaps a good starting point though!

[1] https://arxiv.org/abs/2406.11824

As an aside, hats off to Google to being able to serve an 11 year old video with no noticeable delay from what must be the coldest of caches.

As is pointed out elsewhere on this thread, we're tracking the request to disable the feature here: https://jira.atlassian.com/browse/CONFCLOUD-67922

There are a couple of workarounds documented on it until we reach a proper resolution.

As to the concern around permissions, I believe the reason we're requesting both read and write access to GitHub repositories is that their OAuth implementation bundles the read & write scopes together (https://developer.github.com/apps/building-oauth-apps/unders...). There's just no way to request _just_ read access to repository metadata, which is all the Smart Link feature actually requires.

For Google Drive, which supports more granular scopes, we request _only_ read access, not write access as the title of this post implies.

Comments URL: https://news.ycombinator.com/item?id=22873772

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=21776662

Points: 5

# Comments: 0

With GitHub + JIRA you get:

- associated branches, commits, and pull requests displayed on the JIRA issue view

- the ability to search for issues based on whether they have branches, commits, or pull requests associated with them

- the "Release Hub", which tracks issues that have outstanding pull requests, or have code but no pull request

- automatic issue transitions, which transition JIRA issue status based on repository events

It's flexible, but the usual automatic issue transition workflow is:

branch created: issue -> "In Progress"

pull request created: issue -> "In Review"

pull request merged: issue -> "Done"

Which works just as well with GitHub as it does with Bitbucket.

The main thing that Bitbucket + JIRA's integration adds is backlinks from Bitbucket to JIRA. Plus the ability to create branches in your Bitbucket repositories directly from JIRA.

If you're dead set on GitHub over Bitbucket, the best way to get "Atlassian" features is to adopt the Atlassian suite and replace GitHub with Bitbucket.

Disclosure: I worked on JIRA's DVCS integration.

edit: fixed formating

I came up with 19,290 using the generalized birthday formula[0] (actually after double-checking it's slightly closer to 19,291).

16,384 is the value you get using the square approximation method[1] which I believe is a bit less accurate in terms of probability, but faster to calculate. I think Git's using square approximation under the hood -- which is probably a good thing since I think it'll always yield a more conservative result.

[0]: https://en.wikipedia.org/wiki/Birthday_problem#Cast_as_a_col...

[1]: https://en.wikipedia.org/wiki/Birthday_problem#Square_approx...

I've put together another write-up of the Git 2.11 release that discusses some of the other new features (and goes into a little more detail on some of the 'sundries'): https://medium.com/@kannonboy/whats-new-in-git-2-11-64860aea...

Comments URL: https://news.ycombinator.com/item?id=13066516

Points: 25

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=12744175

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=12694318

Points: 91

# Comments: 41

However even in a strict branching workflow, there's still a chance you'll have genuine integration failures when two branches are merged, even if they independently pass the tests.

https://bitbucket.org/tpettersen/bitbucket-build-status-hook

That way if I update master before starting on a new feature, I get a notification if the tip of master is broken (or still building).

You pick a branch then (optionally) specify a sub-directory of your repository to deploy.

(full disclosure: I'm at Atlassian)

Comments URL: https://news.ycombinator.com/item?id=12298143

Points: 10

# Comments: 0

https://blog.bitbucket.org/2016/07/26/bitbucket-pipelines-be...

It is a paid offering, though you get two repositories free, and is very pretty reasonably priced beyond that.