71 0

totallyscience github.io Totally Science

On one hand, there’s a UI change GitHub could implement that would greatly prevent this situation from happening again. On the other hand, one could try warn every github users that this situation can happen and to be carefull… medalla beer near me Well I have my opinion on which would be most effective. The issue wasn’t that the warning was different, it’s that the user level README repo is named “username/username”, but the organisation README is named “org/.githib”.

Anything that you put in predef.sc will be executed when you load the Ammonite REPL. This is a handy place to put common imports, setup code, or even call import $ivy to load third-party jars. The compilation of the predef is cached, so after the first run it should not noticeably slow down the initialization of your REPL. Note you can also perform file imports from your predef file, which are resolved relative to that file’s path. This is useful if your predef is large and you want to break it up into multiple files. Create scripts that you can run easily from the command line, without the overhead of setting up a “project” or waiting for SBT’s slow startup times.

Data privacy laws like GDPR probably require them to fully hard delete when a user asks for something to be deleted. So any undo functionality would need to make sure it’s compliant in every region that could have a privacy law. I’m not sure how realistic it would be to ask companies like Github to jump through all those hoops because people refused to read . There’s also an issue of taking a repo private, making changes when no one gets alerted, and making it public to make it harder for people to know what’s going on.

And, finally, let’s add all the files and commit our changes. Note that the `autodoc` documentation is still empty for our `helloWorld.py` script because it doesn’t have any functions or modules or docstrings. Let’s wrap the `print()` in a function so we can demonstrate how this will look with your code.

Compiled-code-caches are now properly invalidated when you change project-code while using Ammonite as a REPL for an existing SBT project. Construction of Paths from various types (Strings, java.nio.file.Path, java.io.File) is much more well behaved & consistent now. Converted all string-encoding methods to take a scala.io.Codec instead of a String or Charset, letting you pass in either of those types and having it be implicitly converted.