If it seems useful to you try reaching out to them on a GitHub issue and see whether they'd be willing to implement the missing features or collaborate with you in another way.
5,779 karma · joined February 19, 2013
If it seems useful to you try reaching out to them on a GitHub issue and see whether they'd be willing to implement the missing features or collaborate with you in another way.
I am not colourblind though, so I can't vouch for how good these are in practice, but at least there is some systematic thought that went into the process instead of ad-hoc rules.
I don't think your efforts are obsolete though, the 2 approaches could be combined IIUC your approach is based on computing values based on color science, and the tool/website is a more visual approach, it won't design the colorscheme for you, but you can use it to validate the colorscheme, or tweak it after the fact.
However note that it is quite difficult to get Zenbones work with existing colorschemes, I tried creating/tweaking one based on Zenburn, but in the end I had to go back to the original Zenburn because Zenbones just wasn't distinguishing enough for the various treesitter highlighting groups.
But perhaps some of the zenbones concepts could be combined with Penumbra in penumbra itself to have another variant in addition to the contrast++ one.
And as mentioned elsewhere there are scientific ways to produce colormaps that work for people with color vision deficiency too, so it'd be nice if that was addressed.
It would be nice if this used the upcoming WCAG3 contrast algorithm https://www.myndex.com/APCA/ and ensured it's minimum contrast meets the recommended values there for body text, etc.
There is a tool that can assist in designing color maps taking APCA into account https://huetone.ardov.me/
For perceptually uniform colormaps see also https://colorcet.com/
i.e. previously some code could've in theory assumed it only ever gets called by one thread at a time due to the global lock (and that lock would get dropped in a controlled manner by the usual released/acquire). I don't necessarily mean just global state in the C stubs (I don't recall seeing many of those), but implicit global/shared state in the C functions called. Reading manpages will usually tell whether a given function is safe to be called (or when not there are sometimes _r variants that are). This is no different than when writing regular multithreaded C code, one has to be more careful about what functions they can safely call. (and in fact current OCaml code can already be multithreaded, so if the C stub was meant to work correctly with multithreaded OCaml code with C->OCaml callbacks then it should've already taken necessary precautions).
I like the approach taken wrt to backward compatibility of sequential code though: only code that wants to take advantage of multicore will need to audit its C stubs for safety, if you don't use multicore everything will work as before.
How do you recommend to find these kinds of multicore-specific bugs in existing (or newly written) OCaml-C stubs? Would tools like parafuzz help here?
Nevertheless it is a useful board for testing software on RISC-V, e.g. I mostly use it to test the OCaml compiler and related programs on it.
[1] https://lore.kernel.org/lkml/mhng-423e8bdb-977e-4b99-a1bb-b8...
Citrix's goal is to enable everyone to work from anywhere, any time, and on any device. Citrix Hypervisor (formerly XenServer) is a virtualization product built on top of the open-source Xen hypervisor and XAPI toolstack.
Tech stack: * C (hypervisor, kernel, userspace) * OCaml * Python * CentOS 7.x
For the "hypervisor engineer" role prior experience with a hypervisor is not necessary, we also welcome developers who have experience with kernel-level development. OCaml experience is not required for this role.
You'll have the opportunity to actively contribute to various open-source projects that are part of the product.
For more details and to apply see the job descriptions:
* https://jobs.citrix.com/job/R25636/Senior-Hypervisor-Enginee... * https://jobs.citrix.com/job/R27481/Software-Engineer-Functio... * https://jobs.citrix.com/job/R26236/Lead-Software-Quality-Eng...
Note: due to COVID-19 the interview and work will be remote, with a gradual return to office, see https://jobs.citrix.com/covid
I wouldn't have invested in Deliveroo anyway: the best possible scenario for Deliveroo was the pandemic, once it is over it can only go downhill from there, there isn't more room to grow than that. [0] https://www.facebook.com/the.olive.grove.cambridge/photos/a....
There are ways around it: raise the ulimit for your user and run new enough podman to raise limit for fuse-overlayfs, use the 'vfs' driver (it has other perf issues). I heard (but haven't tested yet) that the 'btrfs' driver avoids all these problems and works from userspace. Obviously requires an FS formatted as btrfs...
There are also compatibility issues with Docker. E.g. one container was running sshfs inside Docker just fine, but fails with a permission error on /dev/fuse with podman.
* you are limited to 1024 FDs for your entire container. So running make -j40 usually ends up with various errors due to running out of file descriptors. You can of course raise the limit for your own user, but this may not be trivial on a shared system.
* getting podman to obey a raised user FD limit is non-trivial on CentOS 8. podman is not well supported on CentOS, you need latest Fedora if you want the various bugs/limitations fixed.
* fuse-overlayfs is a single process for the entire container and quickly becomes the bottleneck for any IO intensive operation (e.g. don't try running AFL inside podman, it'll be way too slow and peg the CPU at 99% running fuse-overlayfs).
Fuse shouldn't be necessary though if I could just give it access to the files that my user has access to (of course you'd loose the snapshotting/committing ability), perhaps using -v would improve performance?
Using docker on CentOS 7 was a lot easier (and faster) than using podman on CentOS 8.