Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    etorkia
    @etorkia
    Executing the default test script
    $ export JL_PKG=MCHammer
    Package name determined from repository url to be MCHammer
    9.23s$ julia --color=yes -e "if VERSION < v\"0.7.0-DEV.5183\"; Pkg.clone(pwd()); Pkg.build(\"${JL_PKG}\"); else using Pkg; if VERSION >= v\"1.1.0-rc1\"; Pkg.build(verbose=true); else Pkg.build(); end; end"
    Cloning default registries into ~/.julia
    Cloning registry from "https://github.com/JuliaRegistries/General.git"
    Added registry General to ~/.julia/registries/General
    ERROR: Package TOML [9d418dce-91a8-11e8-0173-7b01a971d501] not found in a registry.
    Stacktrace:
    [1] pkgerror(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:112
    [2] check_registered(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Operations.jl:924
    [3] #instantiate#81(::Nothing, ::Bool, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.instantiate), ::Pkg.Types.Context) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:473
    [4] instantiate at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:461 [inlined]
    [5] build(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}, ::Bool) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Operations.jl:710
    [6] #build#73(::Bool, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.build), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:399
    [7] #build at ./none:0 [inlined]
    [8] #build#72 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:380 [inlined]
    [9] #build at ./none:0 [inlined]
    [10] #build#69 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:377 [inlined]
    [11] (::getfield(Pkg.API, Symbol("#kw##build")))(::NamedTuple{(:verbose,),Tuple{Bool}}, ::typeof(Pkg.API.build)) at ./none:0
    [12] top-level scope at none:1
    The command "julia --color=yes -e "if VERSION < v\"0.7.0-DEV.5183\"; Pkg.clone(pwd()); Pkg.build(\"${JL_PKG}\"); else using Pkg; if VERSION >= v\"1.1.0-rc1\"; Pkg.build(verbose=true); else Pkg.build(); end; end"" failed and exited with 1 during .
    Your build has been stopped.
    image.png
    etorkia
    @etorkia
    Ok... I had tried deleting the Manifest.toml and it did not work... but now I think it was a depricated Manifest file that was causing all the issues.
    fatemehmehrabi
    @fatemehmehrabi
    i do not know anything to start writing documentation for my codes. what should i do?
    Benoît Legat
    @blegat
    Before each functions, you should but comments between triple quotes
    """
        f(a, b)
    
    Return the sum of `a` and `b`.
    """
    function f(a, b)
        return a + b
    end
    Morten Piibeleht
    @mortenpi
    @fatemehmehrabi You might want to also read
    Marcelo Forets
    @mforets
    Hi! When trying to host the documentation for a new package (https://github.com/JuliaReach/RangeEnclosures.jl/) we are getting this error:
    Setting environment variables from repository settings
    $ export DOCUMENTER_KEY=[secure]
    We were unable to parse one of your secure environment variables.
    Please make sure to escape special characters such as ' ' (white space) and $ (dollar symbol) with \ (backslash) .
    For example, thi$isanexample would be typed as thi\$isanexample. See https://docs.travis-ci.com/user/encryption-keys.
    did you get this error recently or have a suggestion for solving it? i generated the keys as in https://juliadocs.github.io/Documenter.jl/dev/man/hosting/
    Christian Schilling
    @schillic
    hi, i work with @mforets and we managed to resolve the problem
    for some reason, we have two profiles at Travis: one containing all repositories of our organization with a .org address here and one containing new repositories with a .com address here (the latter seems to be not public). we only tried to add the private key to the latter (the .com address), which did not work. adding it to the former (the .org address) worked
    Marcelo Forets
    @mforets
    👍
    Morten Piibeleht
    @mortenpi
    @schillic @mforets As far as I know, Travis is migrating things to the .com domain, so new open source repos are there as well now. But so far they are keeping the old repos still at .org.
    But you'd have to add keys for each repo separately anyway, right?
    Marcelo Forets
    @mforets
    The fact that there was a JuliaReach profile in travis.com and another one in travis.org messed things up
    Marcelo Forets
    @mforets

    But you'd have to add keys for each repo separately anyway, right?

    hmm the new github repo has only 1 deploy key. i think we just kept with https://travis-ci.org

    Casey Kneale
    @caseykneale
    Anyone a wizard with Documenter.jl? I have somehow borked my entire Docs
    I think it may be because I ran Pkg.update and got a new version of it or something?
    Casey Kneale
    @caseykneale
    Anyone know/have alternatives to Documenter.jl?
    Morten Piibeleht
    @mortenpi
    what error are you getting?
    Casey Kneale
    @caseykneale
    something about DOCUMENTER_KEY
    Júlio Hoffimann
    @juliohm
    How to cross-reference a page? I tried [Page Title](@ref) without success. In this case Page Title is the name of the page in the make.jl file.
    Yuri Elias Rodrigues
    @yurier
    Hello, I posted a difficulty I am having with DocStringExtensions, I hope my doubt is clear enough
    someone can help me?
    clu2stanford
    @clu2stanford
    error.png
    Hi, I've been trying to document a repo but the docstrings aren't showing. I included the @docs yyyymmdd2yyyy(d) in the index.md file and exported the functions in the module.
    clu2stanford
    @clu2stanford
    The repo is here: https://github.com/clu2stanford/DateUtils.jl. Why aren't the docstrings showing?
    Clark C. Evans
    @clarkevans
    Hi. For various projects I'm on, I've always wanted 2-column layout... ie for comparisons, macro vs non-macro form, etc.
    It seems some people are using raw in HTML in order to add this sort of feature. Would it be possible to have a convenient way (that doesn't litter HTML tags everywhere) in the markup processed by Documenter; so, some sort of plugin /w syntax markers that let me easily use two columns.
    mortenpi
    @mortenpi:matrix.org
    [m]
    @clarkevans: Markdown doesn't really have any syntax for this, so first one would have invent something that would also work with the parser in the Markdown stdlib (would probably have to rely on some custom at-blocks). Once you have that, in principle, generating the necessary HTML wouldn't be that difficult.
    That said, would it be possible to use tables?
    Clark C. Evans
    @clarkevans
    @mortenpi:matrix.org -- so it'd be great if it was responsive, people do read documentation on an iPhone, and in that case, tables are less than useful.
    I think a table is a stopgap, but it'd be great if Documenter had a set of built-in macros for a 2-column layout that could be integrated with the CSS styling of the page. Mostly what I want to do is compare two code blocks with each other. For example, DataFrames.jl vs Query.jl differences. Or for DataKnots, a macro form (very readable, but not Julia) and a non-macro form (raw Julia). Having these side-by-side is really important to facilitate comparisons and to not have the user distracted by contextual switching.
    Joey Huchette
    @joehuchette

    Hi all, I'm trying to deploy docs for a new package (https://github.com/joehuchette/Justitia.jl) and am running into some problems. I'm using a Github workflow, generated my two keys using DocumenterTools.genkeys, and then set them correctly in the Github repo (I think). But, when the workflow runs, it appears to crash pretty early in the deploy stage with:

    Initialized empty Git repository in /tmp/jl_mYkDJ1/.git/
    Failed to add the RSA host key for IP address 'XXX.XX.XXX.X' to the list of known hosts (/home/runner/.ssh/known_hosts).
    Load key "/home/runner/work/Justitia.jl/Justitia.jl/docs/.documenter": invalid format
    git@github.com: Permission denied (publickey).
    fatal: Could not read from remote repository.
    
    Please make sure you have the correct access rights
    and the repository exists.
    ┌ Error: Git failed to fetch git@github.com:joehuchette/Justitia.jl.git
    │ This can be caused by a DOCUMENTER_KEY variable that is not correctly set up.
    │ Make sure that the environment variable is properly set up as a Base64-encoded stringof the SSH private key. You may need to re-generate the keys with DocumenterTools.
    └ @ Documenter ~/.julia/packages/Documenter/FuXcO/src/Documenter.jl:554

    I've reset the keys a few times but I get the same failure. Am I missing something silly here? My best guess is that the public key I'm setting in "step 1" of uploading the keys, but I'm just copy-pasting the key right from the output of genkeys. Thanks in advance!

    *the public key is malformed
    Gert-Jan Both
    @GJBoth
    Hi! I really like the look of documenter.jl, but all our work is in python... Is it possible to use a document.jl as some sort of mkdocs style?
    I know its a bit of a weird question but I think the documentation style is very clear and clean so I'd love to be able to use it for non-Julia stuff
    Morten Piibeleht
    @mortenpi
    @GJBoth It's not available as a MkDocs theme. It's custom & specific to Documenter. But it is open source and the SCSS files are in the repo, so anyone could port it for other SSGs.
    For the use in Python: in principle there's nothing stopping you from using Documenter as a simple static site generator. But, of course, you wouldn't get any of the neat things like the evaluation of code snippets, integration with docstrings etc. And you'd still have to run it via Julia.
    Gert-Jan Both
    @GJBoth
    @mortenpi Thanks for the answer! I'll have a look at how hard it is to make an mkdocs theme using scss files. For me it was more about the looks; while all that stuff you mention is very nice, my main focus is clarity now
    Micah Smith
    @micahjsmith
    hi everyone, how can I include a file in my repo root in a generated documentation site? i.e. if I have /NEWS.md and my Documenter.jl site is in /docs, I would like to include ../NEWS.md in my sidebar. Currently I get
    $ julia --project=docs docs/make.jl
    [ Info: SetupBuildDirectory: setting up build directory.
    ERROR: LoadError: '../NEWS.md' is not an existing page!
    mortenpi
    @mortenpi:matrix.org
    [m]
    @micahjsmith: you can copy it over to docs/src before the makedocs call
    Micah Smith
    @micahjsmith
    okay, thanks. wondered if there was built in support.
    mortenpi
    @mortenpi:matrix.org
    [m]
    Nope, not at the moment. There is an open issue for that: JuliaDocs/Documenter.jl#551
    Benoît Legat
    @blegat
    Anyone already had the issue of the picture generated by a plot in a @example block being small