Do we expect the following syntax to work?

julia> [Int, Float64, String, Bool] .<: Union{Int, String}
ERROR: syntax: space not allowed after ":" used for quoting

It works if you call <: as a broadcasted function:

julia> (<:).([Int, Float64, String, Bool], Union{Int, String})
4-element BitArray{1}:
 1
 0
 1
 0

Version info:

Julia Versio

Basic info

Application name: prom2teams
Application repo link: https://github.com/idealista/prom2teams
**Application h

The Heaviside function should be built in, but the following code throws the error Name Heaviside not defined. Trying to define Heaviside myself did nothing - based on the Traceback I guess it should be defined within lambdifygenerated.

from sympy import *
from IPython.display import display
mux, s, Px, Py, Pxe, Pye = symbols("mu_X s P_X P_Y P_X^* P_Y^*", positive=True)
vx,

As discussed in astropy/astropy#10185 (comment), it would be nice to avoid repetitive code such as

observer = ICRS(ra=0 * u.degree, dec=0 * u.degree,
                pm_ra_cosdec=0 * u.mas/u.yr, pm_dec=0 * u.mas/u.yr,
                distance=0 * u.pc, radial_velocity=0 * u.km/u.s)

in tests (or even implementations). Having a way to do ``

Checklist

Please ensure the following tasks are completed before filing a bug report.

• Read and understood the [Code of Conduct][code-of-conduct].
• Searched for existing issues and pull requests.

Description

Description of the issue.

The following code produces an array whose shape does not match what I'd expect:

Using Stellarium v0.19.1-86-g063f535f3b, I get the following image of the Moon. Compared with the photo from Wikipedia or the one from NASA or [this one also from NASA](https://solarsystem.nasa.gov/resources/843/rare-full-moon-on-christmas-day/?category=

Version of Singularity:

$ singularity version
3.5.2

Expected behavior

Given this simple def file:

$ more simple.def 
Bootstrap: library
From: ubuntu:18.04

%post

    mkdir -p /opt/openmpi-4.0.1 && cd $_
    pwd 

The pwd should print /opt/openmpi-4.0.1

Actual behavior

S

In order to perform refactoring and to add new features with more confidence, we need unit, integration and end-to-end tests for:

• algorithm parts. Seesrc/algorithms

• React parts - components and pages. See src/components and src/pages

• State management: redux reducers and sagas. See src/state

The infrastructure:

• jest and @testing-libraryare already set up. Un

In Advanced view when Activity on any of the items is set to Suspend, it will suspend that item for eternity until 'based on preferences' or 'always' is chosen.

In Simple view there is a Suspend button at the bottom, which suspends calculations for just one hour.
It does the same thing as the Snooze option in the (Windows) right-click BOINC Manager icon in the system tray.

For consistenc

This is just a placeholder issue to obtain feedback about the current state of the docs:

1. Are the docs clear enough?
2. Are the examples useful and real?
3. Is the information there for a newbie?
4. Is the information there for an advanced user?
5. Is the organization appropiate?
6. What can we do to improve it.

Example:
Run this tool (provide any directory as the aa input)

class: CommandLineTool
cwlVersion: v1.0
baseCommand: ["echo"]
inputs:
- type: Directory
  id: aa
  inputBinding:
    valueFrom: "$(self.listing.length)"
outputs:
  o1:
    type: Directory
    outputBinding:
      glob: $(inputs.aa.basename)
requirements:
- class: InlineJavascriptRequirement
- class: InitialWork

Issue tracker is only for Bugs and Features, before to open a new issue please read the Contributing document (link at the right), and use the forums if you need help or technical support.

Dollar signs entered into Builder loop nReps fields are being compiled to JS in the TrialHandler nReps parameter, causing a reference error in browsers, e.g., see Discourse post

Three very minor typos are present in these documents that break the code when copied-and-pasted as they are.

Link: https://gatk.broadinstitute.org/hc/en-us/community/posts/360056484652-Typos-in-docs

--

1.  https://gatk.broadinstitute.org/hc/en-us/articles/360036726571-LeftAlignAndTrimVariants

the fifth code block on this page

The field __name__ is a built-in module variable in python. E.g. if __name__ == "__main__": is commonly used. It is overwritten in the backends. In backend_glfw.py we have the lines:

# Backend name
__name__ = "GLFW"

https://github.com/glumpy/glumpy/blob/master/glumpy/app/window/backends/backend_glfw.py#L43

It means that print(type(app.Window())) returns `<class 'GLFW.Window'>

This would make the process for making small corrections easier for non-developers. From a comment on #8349.

This should be pretty easy to do and a good task for a new developer or community member looking to make a small contribution.

https://github.com/Revolutionary-Games/Thrive/blob/bf37ff573abcdafe05017db82999c9669449d83c/src/microbe_stage/Spawners.cs#L127

I noticed that the docs for EvaluationStatus indicate that "reported" is an acceptable value, but the code for EvaluationStatus itself will not accept it.

obspy.core.event.Pick(time=time, waveform_id=wid, phase_hint="P", evaluation_status="reported")

returns

`ValueError: Setting attribute "evaluation_status" failed. Value "reported" could not be converted to type "Enum(["preliminary

https://www.arxiv-vanity.com/papers/1401.5761/