go to post Timothy Leavitt · Jan 4, 2024 @Enrico Parisi thank you for bringing this up, we'll try to turn around a fix shortly.
go to post Timothy Leavitt · Jan 4, 2024 @Enrico Parisi I appreciate all of your feedback, and your patience. Regarding tarball installation, I've created another issue for git-source-control on that topic (https://github.com/intersystems/git-source-control/issues/310) as well as one for IPM more generally (https://github.com/intersystems/ipm/issues/436).git-source-control is not officially InterSystems-supported, though it is maintained by people at InterSystems as a service to the developer community. The project certainly has not been abandoned, and there's actually an ongoing effort this month/next to deal with some of the rough edges (now to include your observations around CSP application mapping configuration). I'm personally committed to making it not feel half-baked.
go to post Timothy Leavitt · Dec 18, 2023 FWIW, I've nudged internally on the bug report for this and mentioned the post.
go to post Timothy Leavitt · Dec 1, 2023 Note - at some point I plan to release this code on the Open Exchange, just haven't gotten around to it yet.
go to post Timothy Leavitt · Nov 29, 2023 @Yuri Marx I appreciate the suggestion. We've thought about this, but the set of considerations for a migration to InterSystems IRIS are broader than fit in this format, and there are diminishing returns at this point for providing them via this tool. We also don't have data available in the right structure for older platform versions. There's a whole separate document covering IRIS migrations available from the WRC for supported customers - see https://wrc.intersystems.com/wrc/coDistDocs.csp .
go to post Timothy Leavitt · Nov 29, 2023 Wouldn’t it be great if there was a “Favorites” link in the management portal that would drop you right into this page with your IRIS version and the features that you’re using? I think so too! Keep an eye out, it’s coming soon via a new package on the Open Exchange.
go to post Timothy Leavitt · Nov 13, 2023 No offense taken - if you're working on a local dev environment/container/etc. it's absolutely a better experience to use a third party GUI rather than Git WebUI from git-source-control to manage things; the purpose of the source control extension in that case is just to do export of things in IRIS to the local filesystem. I generally just use GitHub Desktop. The Git WebUI is significantly more valuable in a remote / shared development environment where the alternative would be SSH'ing in and running git commands. This is still a valid option if you prefer and for the rare edge cases where something gets stuck.One clarification, though - the Git tools in IRIS Studio *do* carry over to VSCode if you're using isfs for server-side editing.
go to post Timothy Leavitt · Sep 13, 2023 What I want is all the old values of fields/properties, similar to {FieldName*O} in a row-object trigger I'd much rather not write but from an object perspective. Ultimately I want all of that data in object form.
go to post Timothy Leavitt · Jul 26, 2023 The web UI provides the option to stage and commit another user's changes (after confirming that yes, you really do mean to do so).
go to post Timothy Leavitt · Jul 26, 2023 I discussed this with Jason earlier this week. The simplest solution is to use the InterSystems Package Manager (IPM) with a local development environment model - if you have multiple local repos all loaded via zpm with the "-dev" flag, git-source-control will know the right place for everything to go and you can edit multiple projects under a single isfs folder in VSCode (or via Studio). Note, you may need to be more explicit than previously needed with the Directory attribute on resources in module.xml to get things perfectly right. If there are needs that this won't quite meet, it may be possible to improve git-source-control to provide further configuration options.
go to post Timothy Leavitt · Jun 22, 2023 I'm not a Mac user myself, but my first thought would just be to move the "workspace" folder somewhere else (e.g., under the database install root) that would inherently have the correct permissions, and chown appropriately. You can double check which user IRIS is running as with something like: ps aux | grep irisdb | grep SuperServer | tail -n 1 | cut -d' ' -f1
go to post Timothy Leavitt · Jun 21, 2023 @Gautam Rishi some things that would be helpful / might be worth looking into: Does the user IRIS runs as (most likely irisusr) have access to /Users/abc/workspace? If not I'd imagine all sorts of things could go wrong. (And git-source-control could be more helpful by making the root cause more obvious.) Where specifically is the error coming from? The error #5001 / message there doesn't seem to be in the git-source-control codebase, at least that I can find. If you set ^%oddENV("callererrorinfo")=2 it'll typically put the full stack trace in the error message. Just be sure to kill ^%oddENV("callererrorinfo") later so you don't keep getting it because it's noisy/annoying if you don't need it. What IRIS version are you running? (write $zv) In general, feel free to file a GitHub issue at https://github.com/intersystems/git-source-control/issues
go to post Timothy Leavitt · Jun 7, 2023 If you're looking to implement your own registry you'll also need client code to handle retrieving packages from, and publishing to, your own registry. (FWIW, built-in Artifactory support is under consideration.) This would involve extending https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage... and writing classes to implement the following interfaces:https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage...https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage... (Ignore the "Application" related methods - only "Module" is needed.) As an example, see:https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage...https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage...https://github.com/intersystems/ipm/blob/master/src/%25ZPM/PackageManage...
go to post Timothy Leavitt · Jun 7, 2023 Hi - I'd recommend looking at https://github.com/intersystems/git-source-control and watching a few of these videos: https://www.youtube.com/watch?v=elVQEU9MitE&pp=ygUuZ2l0IHNocmFlZCBkZXZlb... https://www.youtube.com/watch?v=Fh0uyC9owyE&pp=ygUuZ2l0IHNocmFlZCBkZXZlb... https://www.youtube.com/watch?v=QIb2ksEXdHk&pp=ygUuZ2l0IHNocmFlZCBkZXZlb...
go to post Timothy Leavitt · May 31, 2023 I've always wanted my Zen tablePane (T-Pain, as we call them for short) to be able to use autotune. So glad this is finally possible in 2022.1. Brings me back to the golden days in the late '00s where we did lots of things that seemed really cool at the time and feel kind of silly now.
go to post Timothy Leavitt · May 16, 2023 Solution was ultimately to just use a class and the CSPURL parameter. (Context: https://github.com/intersystems/git-source-control/pull/255 )
go to post Timothy Leavitt · May 16, 2023 I'll add to this, we use the same "embedded" source control behavior across Studio and VSCode for my team within InterSystems, and haven't had issues. @Richard Filoramo , one question re: TrackWare - do you know offhand which "Actions" and "Other Studio actions" it uses in the UserAction method from %Studio.Extension.Base (see class reference)? There are some limitations/differences between VSCode and Studio but they're on things we see as either less common or undesirable to support from VSCode. One such case we've previously deemed "undesirable" is Action = 3, "Run an EXE on the client. The Target is the name of an executable file on the client machine. It is the responsibility of the customer to ensure this EXE is installed in a suitable location." Your statement that your source control system is written in ObjectScript and Delphi makes me think this might matter to you. More generally, @Brett Saviano , there may be other aspects of complete support for the interface defined in %Studio.Extension.Base to consider.
go to post Timothy Leavitt · May 15, 2023 @Evgeny Shvarov I have a detailed writeup here (although Dmitry already hit the important point re: IPM): https://community.intersystems.com/post/unit-tests-and-test-coverage-obj... A few other notes: Unit test class instances have a property (..Manager) that refers to the %UnitTest.Manager instance, and may be helpful for referencing the folder from which unit tests were loaded (e.g., to load additional supporting data or do file comparisons without assuming an absolute path) or "user parameters" / "user fields" that were passed in the call to run tests (e.g., to support running a subset of tests defined in unit test code). Sure, you could do the same thing with PPGs or % variables, but using OO features is much better. I'll also often write unit tests that do setup in OnBeforeAllTests and cleanup in %OnClose, so that even if something goes very horribly wrong it'll have the best chance of actually running. Properties of the unit test are useful to store state relevant to this setup - the initial $TLevel (although that should always be 0), device settings, global configuration flags, etc.
