carreau

Reminder that after more than a month, many repos _still_ don't show all PRs and Issues https://github.com/orgs/community/discussions/193463

i still can't see many pull requests in a bunch of repositories... it's been over a month

It's going to be a month since GitHub incident, a number of repos still do not show all pull requests with a few repos still missing dozens and the UI showing different counts in different places. GitHub support now autoclose report in minutes and does not fix it.

you can/should post that in the jupyter zulip chat.

I love how you are not even realising that behind the oatmilk ticket is written "last oatmilk", the behind the half and half one is written "only 3 half and half" behind the foo ticket "foo down to f(frequency of foo use)", and the person now now only need to go through the tickets at the end of the week (or if more than N tickets).

I will let you ponder if you need to reticket all, or just the reordered product, wether a stack can have multiple ticket (a white one say 5 from the last and one red one two from the back know wether you need an urgent order) etc...

And whether or miracle, if you don't receive any ticket a week that you don't need to reorder !

It's amazing how if that was expressed in term of resource allocation, reference counting, tagged pointers, scaling heuristic, garbage collect... that would click in people's mind, but many are incapable at abstracting because they feel they are beyond this.

I feel like you are confusing "more efficient" with "more convenient for me when I use milk because I think the secretary is my maid".

Well, it's just bad journalism, cause what they are referring to is a quantum inertial navigation system, not a clock – it's just thousands of time more precise. The plan happen to also have an atomic clock (which is used to properly integrate inertia through time), without having to rely on external GPS (which is a clock).

You just have to get closer to the source and find better information: https://www.gpsworld.com/uk-government-tests-quantum-inertia...

I think that's fairly normal, having alternative frontends can only be beneficial to the community. I know it also look like there is a single Jupyter team, but the project is quite large, there are a lot of constraints and disagreements internally and there is not way to accomodate all users in the default jupyter install. Alternative are always welcome ; at least if they don't fragment the ecosystem by being not backward compatible with the default.

Also to be fair I'm also one of the Jupyter dev that agree with many points of OP, and would have pulled it into a different direction; but regardldess I will still support people wanting to go in a different direction than mine.

IPython maintainer and Jupyter dev (even if I barely touch frontend stuff these days). Happy to see diversity, keep up the good work and happy new year. Feel free to open issues upstream if you find lack of documentation or issue with protocol. You can also try to reach to jupyter media strategy team, maybe they'll be open to have a blog post about this on blog.jupyter.org

Curious about the limitations that made you fork it instead of making an extension.

That's because it's native to the browser and not hijacked by JS: https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-snap...

In this repo: furry. A coworker of mine reported another repository of this author (or another contributor?) for according to my coworker containing CP. Read issue 474 as well.

Project that contains (contained?) porn in the source tree https://github.com/Alex313031/thorium/pull/469 and I've heard the maintainer also promotes some quite reprehensible stuff. So I can't support it.

While I agree this is marketing stunts in general, sometime the difference between 99.5 and 99.6 reemission is 0.5 vs 0.4 percent absorption. so one way of seeing it the second one is 20% better than the first one at not heating the building.

This is often the case for percentages "close" to 100%, e.g: with LED efficiency, for powerful LEDs the problem is not the quantity of light emitted but dissipating the heat that may need active cooling, so what may look like a few percent improvement is luminosity may actually be a much stronger decrease of the size of active cooling,

Or semi-transparent mirrors in physics, where you really make a difference between 99.95 and 99.96% reflectance, because what you really look at the transmitance.

Hum, that is interesting. I'm more thinking that in a perfect world the pristine-tar delta file should be empty. (Assuming I understand what pristine-tar is doing correctly).

For example I tend to use SOURCE_DATE_EPOCH to be the timestamp of the commit to make sure that anything that embed time is reproducible without extra instruction/manual process specific file.

Thanks for the article and taking the time to reply here.

Thanks for advice, and I assume you are the one who commented on the upstream issue. This show it is not trivial, and it would be nice to be done automatically by default.

As a curiosity, what would it entail to make the two tgz byte-for-byte identical ? There was/is some discussion in setuptools about how to normalize the tarball (https://github.com/pypa/setuptools/issues/2133#issuecomment-...) coudl something similar be applied to Building Python itself ?

Even on classical 2D microscope the illumination can be non-uniform, and you might need to calibrate your image.

Source: PhD in biolab with microscopes, and napari dev.

see also https://xon.sh/

Thanks for asking those question, and with the number of comments, thanks if you reach mine.

One of my hope is that this will affect the market and in particular the ability to have non-connected variants of some appliances.

My hope is that if the cost/risk if high enough, manufacturer won't put pointless connectivity - or at least the ability to disable connectivity – to some models.

I'm also hopping that will put an end of application that collect personal data, like my headphone app requiring I turn on GPS and give it access to my location start.

Thanks !

If you like interactive c/c++, how a look at https://github.com/jupyter-xeus/xeus-cling, that allow you to run the c/c++ repl in Jupyter, either in web interface, and terminal interfaces.

Now, I want to write a program the play that game...

> These photographs do not contain individuals working in British intelligence or document MI6 equipment and locations

Or so they want you to believe...

Sure, but you seem to be read this blog post in the narrow view of building as only "compiling an artifact" and not running the test suite across many platforms/condition, or any other work. I mean the author even points out that building the kernel is only a use-case that takes time for measurement purposes. For some projects I work on the compilation itself takes maybe 1/10 max of the total build and test. So even with infinite agressive compilation caching I would not gain much.

As I replied to the sibling comment, yes, I agree, but caching is not magic. You need to know what to invalidate, and you need to be allowed to spend time making test group that run depending on what have changed. So without policy and having devs being allowed to work on optimizing CI/reducing time, you can list plenty of strategies to make it faster but it will likely not happen.

Sure, and you are proving my point. You have to allocate time for someone to reply to all those questions and update the CI to only test what's necessary, or prioritize some test, and run the rest only if they pass etc.

So you do need policies to actually be allowed to optimise CI.

I my experience if you get more builders/faster hardware someone higher up will end up asking for more items in the build-matrix, and the CI time will balloon up again.

It's rarely only a question of just allocating money to more/better hardware, it's also a question of policy and willingness of your organisation to keep CI time short/feedback fast.

If it's ever a problem with the Jupyter trademark, you should be able to contact the Jupyter Trademark committee jupyter-trademarks@googlegroups.com. I'm not part of it anymore, but they might be able to help with any TM related thing. It may have been autodetection of the "Jupyter" keyword on a non Jupyter domain ?

Honestly that make you look like an ass.

You can "login with GitHub" on GitLab, and the minimum you can do for an open source project that is given to you for free is to make a tiny bit of effort to respect the maintainer choice. Really I assure it's _that_ easy, even I did it a few days ago.

If you are not capable of clicking on three button to login on a platform and say "thanks" to a maintainer on an issue that is already there, but have the time and energy to complain on HN, I'm not sure I would want you as a user.