Fork me on GitHub

Is this channel about clojure.core/juxt or , or both πŸ˜›?


And is this a good place to ask questions about Apex? πŸ™‚

πŸ‘ 4

Ok cool πŸ™‚ I was wondering about the state of the openId code. It’s an approach I would like to use


Hi @jaihindhreddy this channel for

πŸ‘ 4

although we'll also try to answer questions about clojure.core/juxt if you have them πŸ˜‰


Ha! Thought so πŸ˜„. Thanks. Edit: Adding a channel topic might help.


I see a lot of open questions in this namespace Is it still under heavy development / design?


Yes, still under development. In brief, I'm currently working on finishing off because I need it for so many places in Apex, to do the job properly. On the OpenID-Connect front, there's some extra work in checking all the things they need to be asserted before it's ready for a proper security review/audit, but the code does work from a demo perspective, the JWTs are verified properly and it's all mostly there. I'll circle back soon for another go at finishing it along with the other Apex Ring middleware pieces on the roadmap. Hope that helps.


I pinged @malcolmsparks who can answer better than I @jeroenvandijk. Thanks for your Q


I have encountered a 'strange interaction' using the 'capsule' method of creating an upberjar as described in the Edge documentation. The screenshot shows the issue: Following the Edge documentation I cloned Edge to begin, then used 'bin/app' to create two apps, '' and 'my.two'. Following this I did the following: 1. Left, first show Java version being executed 2. Left, next create '' uberjar 3. Left, execute '' uberjar, and make sure it works, which it does 4. Left, kill '' with CTRL-C 5. Right, first show Java version being executed 6. Right, next create 'my.two' uberjar 7. Right, execute 'my.two' uberjar, and make sure it works, which it does 8. Right, kill 'my.two' with CTRL-C 8. Left, execute '' uberjar again, and make sure it works, *IT FAILS* 9. Left, execute '' uberjar again, and send stderr and stdout to files for analysis 10. Left, kill '' 11. Analyze stdout capture file finding an exception. 12. Left, rebuild '' 13. Left, execute '' uberjar, and make sure it works, which it does 14. Right, execute 'my.two' again, and make sure it works, *IT FAILS* 15. Analyze stdout capture file finding an exception. Thoughts?


Reading the capsule docs will help. The application id is used to generate a cache. So I would guess the cache is being overwritten

πŸ‘ 8

Given the steps, you probably need to specify an application id


Around 19:15 I discuss that code @jeroenvandijk


It's under development, but good enough to demo. It's more complete than anything similar I know of.


@malcolmsparks Thank you. I’ll have a look and provide feedback if that is helpful


Yes. The cache was being overwritten. Doing something like this fixed it: ../bin/capsule \ --application-id '' \ --application-version '1.0.0' \ --main 'edge.main' \ --extra-path 'target/prod' \ -A:prod project.jar It also appears that executing the resulting JAR file something like this: CAPSULE_CACHE_DIR='/tmp' java -jar project.jar will create the cache in /tmp, and delete it automatically after execution. Of course you loose whatever start performance is gained by the cache. Thanks all!

πŸ‘ 4