go to post Eduard Lebedyuk · Apr 22, 2021 Do you want to send a custom header with your HTTP request?
go to post Eduard Lebedyuk · Apr 22, 2021 Check WorkflowUI-ngx / WorkflowAPI for customizable rendering.
go to post Eduard Lebedyuk · Apr 20, 2021 Why? Your shell is run under your user (vrogers). You use $ZF(-1) to spawn a child process which inherits everything from parent. Ergo, $ZF(-1) started from shell is also run under your OS user.
go to post Eduard Lebedyuk · Apr 20, 2021 Correct. Terminal sessions are run under OS user who runs the terminal. CSP and Interoperability jobs run under cacheusr or irisusr by default or some other custom user if you specified that during installation.
go to post Eduard Lebedyuk · Apr 19, 2021 @Sean Connelly shared a tip on how to enable auto-complete for macros. No idea about routines though.
go to post Eduard Lebedyuk · Apr 18, 2021 During installation you specified the user who owns the system. Try running cstop as that user.
go to post Eduard Lebedyuk · Apr 18, 2021 You should check for disk speed and latency especially under heavy load. HS should be given a separate disk(s). Hyper-converged infrastructure like you describe can invite performance lags in unexpected ways. Calling @Mark Bolinsky.
go to post Eduard Lebedyuk · Apr 16, 2021 Generalize. 1. You can have 1 BP/1 BO called GET resource which gets: resource id resource type And based on that information constructs the required JSON. 2. If BP only proxies requests to BO you can skip BP and call BO straight from BS. Check out RESTForms2 - it does something similar (CRUD over classes) and there's only 4 handlers for all classes.
go to post Eduard Lebedyuk · Apr 15, 2021 If you want to minimize the roles given to a user, use Privileged Routine Applications. With them, only specific lines of code would have additional privileges, such as %DB_CACHESYS:R.
go to post Eduard Lebedyuk · Apr 15, 2021 For community Python Gateway I wrote an $lb -> tuple converter. You can check it out here. To be callable from Python you can expose it as a Python C extension.
go to post Eduard Lebedyuk · Apr 12, 2021 While I do agree, what's the use case? If you're requesting objects en masse it's usually via sql and it's easy to provide id there. In a case of a singular object you usually request it by ID so it's known beforehand.
go to post Eduard Lebedyuk · Apr 11, 2021 Interesting question! Here are my findings for store/intersystems/irishealth-community:2020.4.0.524.0 and a simple app in the USER namespace. Uncompressed (Mb) Compressed (Mb) IRIS 3 323 897 IRIS Squashed 3 293 893 App 8 436 1 953 App MSB 3 526 937 App Squashed 3 576 931 App MSB + Squashed 3 363 904 Notes: MSB means Multi Stage Build Squashed means that an image was built with a --squash option Uncompressed size is calculated via docker inspect -f "{{ .Size }}" $image Compressed size is calculated via (docker manifest inspect $image | ConvertFrom-Json).layers | Measure-Object -Property size -Sum More info on calculating image sizes is available here Conclusion: either MSB or Squashed work fine, but just MSB would be better for storage as it can have shared layers (squash always produces one unique layer). Squashed is easier to implement.
go to post Eduard Lebedyuk · Apr 9, 2021 The best place to do that is your REST broker. After you got your error from BP, just create your own error and pass that.
