maintainer | Generate personal daily reports or summary AUTHORS | DevOps library

I am trying to install PySpark package Graphframes using spark-shell :

I use following script to get the description of a group in GitLab.

Script:

In my CMakeLists.txt I have:

I was assigned to work with ten year old legacy Java project which generates the following artifacts.

Simply put: I want to list the last N packages I've installed with Homebrew.

What is the best (and possibly fastest) way to accomplish this?

Note that I'm not fluent in Ruby, so any suggestions to 'hack the Homebrew code to do what you want' would get me nervous...

1. Read man pages, documentation, the Homebrew website, StackOverflow, googled with all sorts of variant questions, etc. No luck so far.
2. brew info [formula|cask] will actually tell the date when a formula/cask has been poured (which I assume means 'installed' outside the Homebrewosphere). So that value must be written somewhere — a database? a log?
3. Maybe there is an option to extract the poured date information via the JSON API? But the truth is that with Homebrew 3.1.9-121-g654c78c, I couldn't get any poured-date or similar element on the JSON output... the only dates that I get are related to git (presumably because they're more useful for Homebrew's internal workings). This would, in theory, be able to tell me what are the 'newest' versions of the formulae I have installed, but not the order I have installed them — in other words, I could have installed a year-old version yesterday, and I don't need to know that it's one year old, I only want to know I've installed it yesterday!

Although I couldn't figure out how to retrieve that information, I'm sure it is there, since brew info ... will give the correct day a particular formula was poured. Thus, one possible solution would be to capture all the information from brew info and then do a grep on it; thus, something like brew info | grep Poured should give me what I want. Needless to say, this takes eternities to run (in fact, I never managed to complete it — I gave up after several minutes).

Of course, I found out that there is a brew info --installed option — but currently, it only works with JSON output. And since JSON output will not tell the poured date, this isn't useful.

A possibility would be to do it in the following way:

• Extract all installed package names with brew info --installed --json=v1 | jq "map(.name)" > inst.json
• Parse the result so that it becomes a single line, e.g. cat inst.json | tr -d '\n\r\[\]\"\,'
• Now run brew info --formula (treat everything as a formula to avoid warnings) with that single line, pipe the result in another file (e.g. all-installed.txt)
• Go through that file, extract the line with the formula name and the date, and format it using something like cat all-installed.txt | sed -E 's/([[:alnum:]]+):? stable.*\n(.*\n){3,7}^ Poured from bottle on (.*)$/\1 -- \3\\n/g' | sort | tail -40 — the idea is to have lines just with the date and the formula name, so that it can get easily sorted [note: I'm aware that the regex shown doesn't work, it was just part of a failed attempt before I gave up this approach]

Messy. It also takes a lot of time to process everything. You can put it all in a single line and avoid the intermediary files, if you're prepared to stare at a blank screen and wait for several minutes.

I was trying to look for a) installation logs; b) some sort of database where brew would store the information I was trying to extract (and that brew info has access to). Most of the 'logs' I found were actually related to patching individual packages (so that if something goes wrong, you can presumably email the maintainer). However, by sheer chance, I also noticed that every package has an INSTALL_RECEIPT.json inside /usr/local/Cellar/, which seems to have the output of brew info --json=v1 package-name. Whatever the purpose of this file, it has a precious bit of information: it has been created on the date that this package was installed!

That was quite a bit of luck for me, because now I could simply stat this file and get its creation timestamp. Because the formula directories are quite well-formed and easy to parse, I could do something very simple, just using stat and some formatting things which took me an eternity to figure out (mostly because stat under BSD-inspired Unixes has different options than those popular with the SysV-inspired Linux).

For example, to get the last 40 installed formulae:

I am trying to set a enviroment variable from GITLAB to my Dockerfile ENV env_var_name=$CI_JOB_NAME but It seems that is not set

$CI_JOB_NAME is a GitLab enviroment variable

I'm getting the following error with GCC >=9 and std>=11 merely by adding the header (MacOSX on MacBook Pro 2020 and armadillo installed with Homebrew and the code is compiled with standard CMake configuration) #include to my project.

Undefined symbols for architecture x86_64: "___emutls_v._ZN4arma19mt19937_64_instanceE", referenced from: __GLOBAL__sub_I_Test_HPP.cpp in Test_HPP.cpp.o ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status make[2]: *** [Test_HPP] Error 1 make[1]: *** [CMakeFiles/Test_HPP.dir/all] Error 2

I've tried various hacks including optimization flags e.g. O2, O3 etc. but finally adding the preprocessor header #define ARMA_DONT_USE_WRAPPER apparently resolved the issue for now but I need an explanation to feel settled. If the above pre-processor is absolutely necessary to compile the code, should the armadillo library maintainers absorb the macro within the library itself? This kind of issues may take a lot of time to resolve as it is not originated in any programming logic.

Sorry for my english I'm French.

I develop in Flutter (dart) and I experience a strange behavior in my code using Cubit (Bloc) when I want to redirect to a page after a form submission (with "Reactive forms" package, but also with classic form) and the step of the Cubit loaded state: I see 2 calls to the page (2 builds) which gives a sort of "flapping" effect which means that the final user sees the interface charging twice.

It's my first application in Flutter.

I created an application containing a login form: when the form is submitted I print another form.

At the beginning of my application I was using "auto_route" package and I obtained a refresh of the page each time I clicked inside the text field after the login process. So I was not able to write anything inside the text field.

I was thinking that the problem came from the "Reactive forms" package so I opened an issue to the github repository of this package: issue opened

But as I didn't see where was the problem I came back to a much more basic development for my application and also a more basic method for managing the pages routing in order to explain my problem to the maintainer of the "Reactive forms" package, a really nice guy which really tried to help me.

But even the maintainer does not understand why I have this problem.

Now I reduced my more simple code in one page.

For the moment I don't have the problem when I clicked inside the text field but I see that interface is built twice and the Cubit loaded state which maybe explains why I had the initial problem.

So now I try to understand why the interface is built twice before debugging my original code.

I think my main problem is that the Cubit loaded state is waiting a synchronous widget return but when I try to redirect to a another page it needs an asynchronous action (with "auto_route" package or more simply using "Navigator.push()" action).

But I don't know how to call a Future inside a Cubit loaded state which wait a classic Widget.

I tried this:

I am following the instruction (https://github.com/huggingface/transfer-learning-conv-ai) to install conv-ai from huggingface, but I got stuck on the docker build step: docker build -t convai .

I am using Mac 10.15, python 3.8, increased Docker memory to 4G.

I have tried the following ways to solve the issue:

1. add numpy in requirements.txt
2. add RUN pip3 install --upgrade setuptools in Dockerfile
3. add --upgrade to RUN pip3 install -r /tmp/requirements.txt in Dockerfile
4. add RUN pip3 install numpy before RUN pip3 install -r /tmp/requirements.txt in Dockerfile
5. add RUN apt-get install python3-numpy before RUN pip3 install -r /tmp/requirements.txt in Dockerfile
6. using python 3.6.13 because of this post, but it has exact same error.
7. I am currently working on debugging inside the container by entering right before the RUN pip3 install requirements.txt

Can anyone help me on this? Thank you!!

The error: