profile
viewpoint
Andrew Forward aforward CrossFit HQ Ottawa, Ontario, Canada https://a4word.com Back to PHP and #elixir; TDD infected since jUnit 2.1, former cheesemaker, and working at #crossfit

aforward/safetybox 17

Security oriented helper functions for Elixir

aforward/ar2ecto 12

Migrate your active record migrations to ecto compatible migrations

aforward/appstats 5

A place to log actions done within your application, and provide usage statistics about how your application is being used.

aforward/doex 5

A Digital Ocean API v2 client for Elixir (yes, another one)

aforward/gen_template_api_client 5

A template for building API clients to 3rd party REST applications

aforward/sadbus 5

A dumb message bus for sharing data between microservices in a relatively decoupled mechanism

aforward/gen_template_ecto_service 4

A template for building an elixir service based on a Postgres database using Ecto.

aforward/fn_expr 2

The && operator (and invoke macro) for use with |> and anonymous functions / captures

aforward/10xdevelopers 1

The source code (and blog) for 10xdevelopers.com

aforward/acme_ex 1

A test implementation of Acme (Let's Encrypt) V2 server https://hexdocs.pm/acme_ex

startedaforward/version_tasks

started time in a day

issue openedumple/umple

Refactor Umple src directory and set up feature model

The src directory with Umple files is too messy, and there are some very large files.

This project would involve firstly,

  • making some subdirectories of src and putting certain functionality there so there are relatively few files left in the main directory. The subdirectories would be organized by architectural unit and feature (use git mv to do any moves to preserve history)
  • Splitting the largest files into smaller ones so no file is excessively massive.

Secondly it would involve creating a feature model of Umple as a whole that could be viewed in Umple, with the ability to generate a version of Umple with a subset of features (this would be as a case study rather than expressing a desire to actually switch of features, although in the extreme it might be possible to create a version of Umple that can deal with mixsets along with embedding methods in other languages only).

created time in 5 days

create barnchTMS-3102/TeamManagementSystem

branch : adding-modify-ability

created branch time in 6 days

push eventTMS-3102/TeamManagementSystem

Atinderpaul Kanwar

commit sha 0a261b2596e6dc40ab74c84bebed4e1316ff65da

Added create and modify pages

view details

Atinderpaul Kanwar

commit sha 626e1bc1f26c541dd20a6ac7f641ef7354ada3c6

removed binding.pry

view details

SamWorrod

commit sha ec09ec4aeef7bbf44e74ae32e31e30e0221568dd

Merge pull request #31 from TMS-3102/create_modify_tasks Added create and modify pages

view details

push time in 6 days

push eventTMS-3102/TeamManagementSystem

Atinderpaul Kanwar

commit sha 626e1bc1f26c541dd20a6ac7f641ef7354ada3c6

removed binding.pry

view details

push time in 6 days

create barnchTMS-3102/TeamManagementSystem

branch : create_modify_tasks

created branch time in 6 days

push eventTMS-3102/TeamManagementSystem

Chris

commit sha 4bfedb3c377a934eb67a08f24da150f43a65555f

react and drag n drop added

view details

SamWorrod

commit sha 9e4330a0a3f28c2111b0ed576f0111a9b408a640

Merge pull request #30 from TMS-3102/adding-react-try2 react and drag n drop added

view details

push time in 10 days

PR opened TMS-3102/TeamManagementSystem

Reviewers
react and drag n drop added
+17904 -5

0 comment

28 changed files

pr created time in 10 days

create barnchTMS-3102/TeamManagementSystem

branch : adding-react-try2

created branch time in 10 days

fork whatyouhide/broadway

Concurrent and multi-stage data ingestion and data processing with Elixir

fork in 10 days

create barnchTMS-3102/TeamManagementSystem

branch : adding-react

created branch time in 11 days

push eventTMS-3102/TeamManagementSystem

Jaimin Patel

commit sha 1dfd98b83bdbdd49e1475a4bc9b47642e88e3676

Task controller, model, migrations

view details

Jaimin Patel

commit sha c7283a50ec72e2790369f68861c26db6f98c73b9

tasks-users table creation

view details

Christopher Francis

commit sha c5cae17cd995d93889f6cef4cafdd658c52d10aa

Merge pull request #29 from TMS-3102/jaimin-controllers Jaimin controllers

view details

push time in 11 days

PR merged TMS-3102/TeamManagementSystem

Jaimin controllers

Creation of Tasks controller and model

+101 -3

0 comment

12 changed files

jaiminpatel98

pr closed time in 11 days

PR opened TMS-3102/TeamManagementSystem

Reviewers
Jaimin controllers

Creation of Tasks controller and model

+101 -3

0 comment

12 changed files

pr created time in 12 days

create barnchTMS-3102/TeamManagementSystem

branch : jaimin-controllers

created branch time in 12 days

issue openedumple/umple

Association to a Trait accepted syntactically but fails to generate valid code as it is not made part of trait

The example below is accepted by the Umple compiler, but does not generate valid Java code, and likely not a sensible internal metamodel.

It would be desirable if an association could be made to a trait (perhaps by reversing it and assuming that the association is defined insite the trait. However in the code below the compler mistakenly thinks that Medic is a valid class and generates Java.

Solution 1: Arrange for definitions of associations this way to become part of the trait, as if they had been defined in the trait

Solution 2: Disallow associations defined that connect to traits, with a suggestion that they must be moved inside the trait

I suggest Solution 1.

// This code fails to generate correct Java because it assumes there is a class Medic when Medic is a trait
class Person
{
  name;
  
  Integer healthId;
}

class Clinic
{
  name;
  * -- * Person registrant;
}


class Appointment {
  * -- 1 Clinic;
  * -- 1 Person;
  Time startTime;
  Date theDate;
}

class Diagnosis {
  * -- 1 Person;
  * -- 1 Medic;
  description;
  Date diagnosedDate;
}

class Treatment {
  description;
  * -- * Diagnosis;
  * -- 1 Medic prescriber;

}

class HealthPractitioner {
  isA Person;
  * employee -- * Clinic worksAt;
}

class MedicalDoctor {
  isA HealthPractitioner;
  isA Medic;
}


class Nurse {
  isA HealthPractitioner;
  isA Medic;
}

class NursePractitioner {
  isA HealthPractitioner;
  isA Medic;
}

class Paramedic {
  isA HealthPractitioner;
  
}

trait Medic {
  specialty;
  Integer yearCertified;
}

The following revised version of the code is fine (with the associations moved insite the trait; option 1 above is to do this silently in the metamodel.

// This code compiles correctly
class Person
{
  name;
  
  Integer healthId;
}

class Clinic
{
  name;
  * -- * Person registrant;
}


class Appointment {
  * -- 1 Clinic;
  * -- 1 Person;
  Time startTime;
  Date theDate;
}

class Diagnosis {
  * -- 1 Person;
  description;
  Date diagnosedDate;
}

class Treatment {
  description;
  * -- * Diagnosis;
}

class HealthPractitioner {
  isA Person;
  * employee -- * Clinic worksAt;
}

class MedicalDoctor {
  isA HealthPractitioner;
  isA Medic;
}


class Nurse {
  isA HealthPractitioner;
  isA Medic;
}

class NursePractitioner {
  isA HealthPractitioner;
  isA Medic;
}

class Paramedic {
  isA HealthPractitioner;
  
}

trait Medic {
  specialty;
  Integer yearCertified;
  1 -- * Diagnosis;
  1 -- * Treatment;
}

created time in 16 days

issue openedumple/umple

Support Umple syntax highlighting by Pygments

Pygments is widely used to highlight syntax in various programs, including in Wikipedia.

It would be highly beneficial to have complete support for Umple. Umple should be recognizable and have its keywords and constructs properly highlighted. Probably it should be done as an extension to Java since Java is the most common language embedded in Umple.

See https://pygments.org/languages/ and https://pygments.org/docs/lexers/ for a list of languages.

See https://github.com/pygments/pygments for the Github page to which a PR would need to be made

Some thoughts: Pygments has jvm lexers, and it would make sense that Umple be listed as one of them and extends java.

Instructions are here https://pygments.org/docs/lexerdevelopment/

created time in 17 days

created repositorywhatyouhide/training

created time in 20 days

fork sae-bom/writing

A collection of markdown articles, blogs, snippets and more. #nocode

fork in 25 days

GollumEvent

push eventumple/umple

Timothy Lethbridge

commit sha 786af3a467de3a2fab043c20ebab69931c82ea6a

Facilitating command line compilation

view details

TCLethbridge

commit sha d05143fd96283c419d1a8da7b7d2ee1705c518f3

Merge pull request #1654 from umple/FacilitateCmdLine Facilitating command line compilation

view details

push time in a month

PR merged umple/umple

Facilitating command line compilation

This makes the following changes:

  • It adds an option in UmpleOnline to put text in the copy buffer that can be pasted into a terminal in Linux or Mac in order to automatically create a directory, create the ump file in that directory, and compile it with Umple and then with Java. This will facilitate better use of UmpleOnline by people who want to make programs that run. The user has to have a JDK installed and also a path to the umple script (dev-tools) in their path.

  • It takes the Task feature out of beta and puts it at the top level of UmpleOnline

  • It fixes scripts for cleaning up on the server (they were not working on the server since we moved)

  • It makes the bumple script better by allowing the here argument to compile in different directories rather than just ~/umple

+133 -45

0 comment

8 changed files

TimLethbridge

pr closed time in a month

PR opened umple/umple

Facilitating command line compilation

This makes the following changes:

  • It adds an option in UmpleOnline to put text in the copy buffer that can be pasted into a terminal in Linux or Mac in order to automatically create a directory, create the ump file in that directory, and compile it with Umple and then with Java. This will facilitate better use of UmpleOnline by people who want to make programs that run. The user has to have a JDK installed and also a path to the umple script (dev-tools) in their path.

  • It takes the Task feature out of beta and puts it at the top level of UmpleOnline

  • It fixes scripts for cleaning up on the server (they were not working on the server since we moved)

  • It makes the bumple script better by allowing the here argument to compile in different directories rather than just ~/umple

+133 -45

0 comment

8 changed files

pr created time in a month

create barnchumple/umple

branch : FacilitateCmdLine

created branch time in a month

PR opened umple/umple

Bump junit from 3.8.2 to 4.13.1 in /Umplificator/UmplifiedProjects/weka-umplified-0

Bumps junit from 3.8.2 to 4.13.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/junit-team/junit4/releases">junit's releases</a>.</em></p> <blockquote> <h2>JUnit 4.13.1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.1.md">release notes</a> for details.</p> <h2>JUnit 4.13</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.md">release notes</a> for details.</p> <h2>JUnit 4.13 RC 2</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 RC 1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 3</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 2</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.12</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md">release notes</a> for details.</p> <h2>JUnit 4.12 Beta 3</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md">release notes</a> for details.</p> <h2>JUnit 4.12 Beta 2</h2> <p>No release notes provided.</p> <h2>JUnit 4.12 Beta 1</h2> <p>No release notes provided.</p> <h2>JUnit 4.11</h2> <p>No release notes provided.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.13.1.md">junit's changelog</a>.</em></p> <blockquote> <h2>Summary of changes in version 4.13.1</h2> <h1>Rules</h1> <h3>Security fix: <code>TemporaryFolder</code> now limits access to temporary folders on Java 1.7 or later</h3> <p>A local information disclosure vulnerability in <code>TemporaryFolder</code> has been fixed. See the published <a href="https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp">security advisory</a> for details.</p> <h1>Test Runners</h1> <h3>[Pull request <a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1669">#1669</a>:](<a href="https://github-redirect.dependabot.com/junit-team/junit/pull/1669">junit-team/junit#1669</a>) Make <code>FrameworkField</code> constructor public</h3> <p>Prior to this change, custom runners could make <code>FrameworkMethod</code> instances, but not <code>FrameworkField</code> instances. This small change allows for both now, because <code>FrameworkField</code>'s constructor has been promoted from package-private to public.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/junit-team/junit4/commit/1b683f4ec07bcfa40149f086d32240f805487e66"><code>1b683f4</code></a> [maven-release-plugin] prepare release r4.13.1</li> <li><a href="https://github.com/junit-team/junit4/commit/ce6ce3aadc070db2902698fe0d3dc6729cd631f2"><code>ce6ce3a</code></a> Draft 4.13.1 release notes</li> <li><a href="https://github.com/junit-team/junit4/commit/c29dd8239d6b353e699397eb090a1fd27411fa24"><code>c29dd82</code></a> Change version to 4.13.1-SNAPSHOT</li> <li><a href="https://github.com/junit-team/junit4/commit/1d174861f0b64f97ab0722bb324a760bfb02f567"><code>1d17486</code></a> Add a link to assertThrows in exception testing</li> <li><a href="https://github.com/junit-team/junit4/commit/543905df72ff10364b94dda27552efebf3dd04e9"><code>543905d</code></a> Use separate line for annotation in Javadoc</li> <li><a href="https://github.com/junit-team/junit4/commit/510e906b391e7e46a346e1c852416dc7be934944"><code>510e906</code></a> Add sub headlines to class Javadoc</li> <li><a href="https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae"><code>610155b</code></a> Merge pull request from GHSA-269g-pwp5-87pp</li> <li><a href="https://github.com/junit-team/junit4/commit/b6cfd1e3d736cc2106242a8be799615b472c7fec"><code>b6cfd1e</code></a> Explicitly wrap float parameter for consistency (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1671">#1671</a>)</li> <li><a href="https://github.com/junit-team/junit4/commit/a5d205c7956dbed302b3bb5ecde5ba4299f0b646"><code>a5d205c</code></a> Fix GitHub link in FAQ (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1672">#1672</a>)</li> <li><a href="https://github.com/junit-team/junit4/commit/3a5c6b4d08f408c8ca6a8e0bae71a9bc5a8f97e8"><code>3a5c6b4</code></a> Deprecated since jdk9 replacing constructor instance of Double and Float (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1660">#1660</a>)</li> <li>Additional commits viewable in <a href="https://github.com/junit-team/junit4/compare/r3.8.2...r4.13.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

pr created time in 2 months

more