minor bug in github pages learning lab course
it appears the learning bot suggests using a pr to reference closing itself (“closes #2”) rather than closing the issue it created earlier, which should be #1.

[[screen shot 2018-10-17 at 9.40.16 am.png]](https://aws1.discourse-cdn.com/github/original/2x/2/2ce2a930118577f58550cdb54b0111901983fdf3.png "screen shot 2018-10-17 at 9.40.16 am.png")

i know it might be interpreted as a generic example, but for new/learning users, this may be a…
hi [@nrebhun](/u/nrebhun),

thank you for catching that! to avoid confusion and to add clarity, the provided example should be closes #1. i’ll make sure a push goes up to make the update in the course instructions.
hello [@cjiang1](/u/cjiang1),

welcome to gitlab forum - thanks for your first contribution :slightly\_smiling\_face:

i think this is most probably caused by a misconfiguration - here’s an [example](https://gitlab.com/gitlab-org/gitlab-ce/issues/48349#note_129188834), fyi. okay, i think i found out what is happening: <https://github.com/drtimothyaldendavis/suitesparse/issues/45> oh my god … i have to appologize very, very much for wasting your time. as so often the problem is sitting in front of the screen :frowning:

i am using certbot inside a script where i make a backup of the /etc/letsencrypt folder, stops apache, on so on …

my mistake is, that my backup of /etc/letse… > You might have missed a bracket somewhere... Only such a mistake causes so many insignificant errors.
> 
> 


And to find it, [format your code](http://www.gidnetwork.com/b-38.html) properly. It's your first debugging tool. its to do with the jit optimisation, the same is true if you insert conditional debug statement in the code, matlab needs to prepare to stop execution. that error happens when there's no handle to close. i see you call the 'open()' and you're not getting an object reference error before closehandle(). check your memory.pointerwrite() function to make sure it's not doing a closehandle() prematurely. it sounds like you're calling closehandle() twice. it looks like you are right, this appears to be an issue. i will make sure that it gets fixed soon. ok, in that case we believe it should be fixed in the upcoming 13.1 update, let us know if this is not the case once it’s out. hi [@interactiverendering](/u/interactiverendering) ,

this is a little more complicated than it appears to be. in order to remove the close button from the form (because it would make revit crash in some cases) i had to remove that logo too. i’ll try and bring it back and let you know :slight\_smile: update. i’ve decided the information isn’t really appropriate for the class description, so i nixed it entirely. i’ve linked to the task scheduler article instead, which is much more relevant.

thanks again for bringing this to our attention!