I received this error message:

  MethodError: convert(::Type{Union{}}, ::Vector{Float32}) is ambiguous. Candidates:
    convert(::Type{T}, a::AbstractArray) where T<:Array in Base at array.jl:532
    convert(T::Type{var"#s79"} where var"#s79"<:BitArray, a::AbstractArray) in Base at bitarray.jl:577
    convert(T::Type{var"#s832"} where var"#s832"<:SparseArrays.SparseVector, m::AbstractVect

Spinning off new issue from reemerging discussion on closed issue #19061

sympy.stats.sample() has changed behaviour since v1.7, returning an iterator instead of actual sample(s), which is an issue:

• It breaks existing code by breaking the API (now returns an iterator rather than samples)
• The change was AFAIK made without warning about future API change
• The iterator serves no real pu

Is your feature request related to a problem? Please describe.
I'm studying geosat flares (link, link) and want to have a better idea of the cone of darkness that is created at a given distance.

Describe the solution you'd like
I want to select an object (satellite, moon, even planet) and see the

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

What is the feature ?

I'm trying out this library for the first time and I'm seeing several places where some shorthand functions would have been really pleasant:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. My plots are supposed to be white-on-black, which requires a lot of boilerplate on lots o

🙋 Feature Request

🔦 Context

If you paste in a t.co link, or whatever, it should follow it.

just to avoid problems some people may have if they haven't ran the format check script before updating localizations.

For the long term, we could clean up the code base a bit by internally using pathlib instead of os.path.join(....) and consorts. This is no vital or overly important task but it will help new contributors, to use it in new contributions and not introduce more old-style code, looking at the rest of the code base.

This is a pretty trivial (but longish) task and is a good first issue for new peo

We either do this all ourselves or do some reordering somewhere, I forget. But we should use the LaTeXML option now! brucemiller/LaTeXML#1044