Nils Gudat

The workaround is to take my workaround from above and finish the work to turn it into a proper PR :)

Ah sorry, I had skimmed the existing issues but it wasn't obvious to me that this was discussed before. Your package your rules of course, but I would say it's...

A minimal change to enable this would be to define ``` function get_hist_temp_data(city::String = "", i_row::Int64 = 1; lat::Float64 = 0.0, long::Float64 = 0.0, start_date::String = "2023-01-01", end_date::String = "2023-01-10")...

Sure this works (although I didn't manage to do this myself before, I got some inscrutable error when calling the unexported function which isn't surprising given it's undocumented). My point...

This sounds like you're just on an old version of XLSX.jl - it used to return a data/column names tuple (so you had to do `DataFrame(XLSX.readtable("myfile.xlsx", 1)...)`) but since version...

This is probably good to close?

Please stop spamming the registry with repeated registration requests which all fail for the same reason, and read the results of the automerge action: > I was not able to...

I just checked `InfrastructureSensing` on JuliaHub to see how much usage it got which yielded nothing but intererstingly on JuliaHub the package is credited to @rbalexan. I'm not sure where...

Great detective work, looks like all packages can go into the "ping author" pile (and looks like at least some of the authors are still active in the community so...

Wouldn't the easiest way forward here for the authors to just retrospectively slap an MIT license on this and then there's no need to yank anything?