This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-25
Channels
- # announcements (5)
- # babashka (23)
- # beginners (70)
- # cider (24)
- # clj-kondo (14)
- # cljsrn (2)
- # clojars (6)
- # clojure (195)
- # clojure-australia (1)
- # clojure-dev (2)
- # clojure-europe (27)
- # clojure-france (1)
- # clojure-nl (4)
- # clojure-norway (2)
- # clojure-spec (2)
- # clojure-uk (12)
- # clojurescript (3)
- # clojurewerkz (1)
- # core-async (21)
- # cursive (9)
- # datomic (37)
- # duct (3)
- # emacs (16)
- # events (4)
- # fulcro (34)
- # graalvm (12)
- # javascript (3)
- # jobs (4)
- # malli (1)
- # meander (3)
- # nrepl (1)
- # off-topic (27)
- # pathom (16)
- # re-frame (17)
- # reagent (19)
- # rewrite-clj (18)
- # sci (47)
- # shadow-cljs (179)
- # spacemacs (18)
- # sql (52)
- # tools-deps (80)
- # vim (27)
- # vrac (1)
- # xtdb (9)
I'm keeping track of my open source issues in a Github project board, but since I split one of my project up into an org, this doesn't work anymore, since I can't add issues from the org to my personal project board... does anyone know a good solution for this?
That's probably an Emacs package that does that hahaha
I have considered going back to Trello, but I'd rather not because the Github board integrates better with... Github. cc @danielcompton
You might be interested to take a look at the approach that Simon Willison uses: > …I shipped a 1.0 of github-to-sqlite. > > As you might expect, it’s a tool for importing GitHub data into a SQLite database. Today it can handle repositories, releases, release assets, commits, issues and issue comments. You can see a live demo built from Dogsheep organization data at http://github-to-sqlite.dogsheep.net (deployed by this GitHub action). > > I built this tool primarily to help me better keep track of all of my projects. Pulling the issues into a single database means I can run queries against all open issues across all of my repositories, and imporing commits and releases is handy for when I want to write my weeknotes and need to figure out what I’ve worked on lately. https://simonwillison.net/2020/Mar/25/weeknotes/
BTW if you’re not familiar with Datasette, check it out. It’s an excellent tool/system. You might even want to try using it to browse your GitHub data, like Willison does. You can try out his demo site to see what it’s like to use.
Put everything in the org?
:thinking_face: iirc gitlab allows for this
if you could deploy a question and answer site really easily and all you had to pick was the topic / domain / some names for chat rooms... which domain would you choose to have a q&a site for?
(let [text-input "home :id 42"]
(keys (edn/read-string
(pr-str {:kind (keyword text-input)}))))
=> (:kind :id)
I see why this works but surely there's a better way to do it?
Not a issue. Just sharing a odd behavior. I tryied to explore and create a "injection" or something cooler, but i failed 😅
oh if we are sharing things just because they are weird - I think this is the best cursedness / character-count (evil golf) program you can write in clojure
user=> (#(%1%2%):-{})
:-
alternate suggestions accepted
I think this is equal, but maybe aesthetically superior
user=> (#(%1%2%):%{})
:%
@U0CMVHBL2 taking your "confusion" response literally, the trick is that the parsing of #()
doesn't follow the standard clojure token recognition rules, so it's possible to eliminate spaces between symbols in a way that isn't valid in any other context
Perhaps if I had a bit more sleep last night, I might feel interested in figuring out what is going on there. It is also likely that even on 100% sleep I would think "as long as nothing like that ever gets past code review and into a code base I use" 🙂
haha right, I think the risk would be inside an injection attack where even if logged it wouldn't look like valid clojure code so it could sneak in...
Anybody who uses clojure.core/read or read-string on untrusted sources shouldn't get past code review, either, IMO
consider: malicious code that hides in a binary like an image file checked into the repo, then evaluated via read that "accidentally" has read-eval turned on, even if you looked at the binary it wouldn't look like clojure code, it doesn't even have spaces in it
(of course constructing anything "useful" that way would be a huge challenge to say the least)
but I don't primarily point it out for security reasons, mainly I find the idea that clojure would accept that code amusing on the face of it
I did my level best to scare people away from clojure.core/read in its http://ClojureDocs.org page years ago, without actually yelling.
I take that back. If ALL CAPS words are yelling, I yelled for a few words.