Fork me on GitHub
#clojure-dev
<
2019-05-24
>
pyr11:05:18

in the new JIRA world, where do things happen once the support request is accepted, is the rest of the process visible or only between core members?

pyr11:05:19

We are also looking at a new process to obtain a contributor account and gain access to the system for commenting or other work. Stay tuned for more on that.''

pyr11:05:24

ok, found my answer

Alex Miller (Clojure team)12:05:35

Tickets are still publicly visible regardless

pyr12:05:09

I'm not finding where though at the moment

pyr12:05:13

http://clojure.atlassian.net lands me on the home for the support requests and doing requests -> all shows me no output

pyr12:05:00

direct links to an existing CLJ ticket have the same effect

pyr12:05:55

if I log out

pyr12:05:57

I can see them

Alex Miller (Clojure team)12:05:18

Yeah, I was just going to guess that

pyr12:05:26

so probably a migration wart

Alex Miller (Clojure team)12:05:38

Atlassuans identity model is ... weird

👍 4
pyr12:05:08

and I'm sure migrating from the age old install brought its own challenges 🙂

Alex Miller (Clojure team)12:05:35

I’ll look at your account or whether you have one when I get to a computer

pyr12:05:50

no rush anyway

pyr12:05:06

I'm supposed to be in the having previously edited crowd if that helps

Alex Miller (Clojure team)12:05:06

So you should have an account - did you do the reset process to get a new password ?

pyr12:05:27

I'm all setup with an account, I followed the link I received by email

Alex Miller (Clojure team)12:05:51

So when you log in, you can’t see links?

pyr12:05:44

Actually, I didn 't generate a new password but used google sign-on

pyr12:05:37

and yes, once logged in I cannot access tickets

pyr12:05:51

(email is <mailto:[email protected]|[email protected]> if that helps once you reach your computer)

Alex Miller (Clojure team)13:05:57

I don't think you can use google sign-on for this org as this site is not tied to a single domain

Alex Miller (Clojure team)13:05:07

you'll need to use email/password

bronsa13:05:22

uh, I logged in with google sign-on and it worked

bronsa13:05:11

FYI I get a 403 when I try to hit https://dev.clojure.org/, not sure if that was supposed to redirect

Alex Miller (Clojure team)13:05:20

that shouldn't at the moment, although it could

Alex Miller (Clojure team)13:05:33

well that's good to know

Alex Miller (Clojure team)13:05:40

@pyr your acct was missing access to the jira product, not sure how that happened, but it should help

pyr14:05:41

@alexmiller things look much better now, thanks!

Alex Miller (Clojure team)14:05:28

everyone should have had that added during the import, but maybe it messed up for some people. will probably do some spot checks later.

seancorfield23:05:13

`select-keys` does not preserve metadata on its first map argument. Yes, it does. Must be time to stop work -- I'm hallucinating! What would be the pros and cons of changing it to do so? I get the impression that several other functions have recently been "fixed" to do so...

andy.fingerhut23:05:46

Are you preparing ticket / patch for this? I can if you aren't already doing it.

seancorfield00:05:14

I was about to, but then when I tried to repro, it worked.

seancorfield00:05:27

I swear it had not worked when I first tested it...

andy.fingerhut00:05:06

Looking at select-keys implementation in Clojure 1.10, it looks like it should always preserve metadata

andy.fingerhut00:05:33

Change looks like it was made before release of Clojure 1.5