profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/scmorrison/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Sam Morrison scmorrison CNS Technical Group, Inc. Fujisawa, Kanagawa, Japan http://cnstechgroup.com

scmorrison/aws-certified-sysops-administrator-associate 2

AWS Certified SysOps Administrator Associate Study Guide

scmorrison/AWS-API 1

AWS::API module for Perl 6

scmorrison/humantranslated-tui 1

Command line interface to HumanTranslated API.

scmorrison/JS-Minify 1

Perl 6 JavaScript minifier

scmorrison/Apollo-11 0

Original Apollo 11 guidance computer (AGC) source code.

scmorrison/assemble 0

Static site generator for Node.js, Grunt.js, and Yeoman (and soon, Gulp), using the Handlebars template engine. Used by Zurb Foundation, Zurb Ink, H5BP/Effeckt, Less.js / lesscss.org, Topcoat, Web Experience Toolkit, and hundreds of other projects to build sites, themes, components, documentation, blogs and gh-pages. Pull requests welcome, stars appreciated!

scmorrison/AWS-Status 0

CLI tool to pull latest AWS Status from status.aws.amazon.com. Includes MOTD support.

scmorrison/awsug-workshops 0

AWS UG - Workshop: EC2, Auto Scaling, CloudFormation

scmorrison/Bailador 0

A light-weight route-based web application framework for Perl 6

scmorrison/bash-it 0

A community bash framework.

push eventRaku/roast

Vadim Belman

commit sha a23d30d6a3f3240764a8d2c10325ac5596a1cd03

Mark a new test as todo Until MoarVM/MoarVM#1507 is merged

view details

push time in an hour

push eventRaku/roast

Nguyễn Gia Phong

commit sha fd078f9c6d894e4ee86bbb43f22ec0e045539dbd

Retire mkdir tests before it creates parents Currently mkdir would create parent directories if necessary.

view details

Nguyễn Gia Phong

commit sha 155f0fe7e11b0d5652aac7397140f7b8feedd3e6

Test mkdir on existing file

view details

Vadim Belman

commit sha 379aca1ede90e8f3e3dc292556d1f62ee52a2b9f

Merge pull request #736 from McSinyx/mkdir Test cases where mkdir should fail

view details

push time in an hour

PR merged Raku/roast

Test cases where mkdir should fail

The added tests should pass for MoarVM/MoarVM#1507. Edit: the final diff is confusing, please consider viewing each commit for the actual changes.

+8 -23

10 comments

1 changed file

McSinyx

pr closed time in an hour

push eventMoarVM/MoarVM

Daniel Green

commit sha 9b7ab7c448dd33c08128ae01cc2798bb91c34e41

Put include paths needed for HLL builds in config Currently the NQP and Rakudo builds use a hard-coded list, but this is prep work for getting their builds to actually use data taken from the MoarVM build they're using.

view details

MasterDuke17

commit sha b015e1a46862ac1f7e061d4c56a6ebab99e72998

Merge pull request #1508 from MasterDuke17/put_includes_needed_for_hll_builds_in_config Put include paths needed for HLL builds in config

view details

push time in 5 hours

PR merged MoarVM/MoarVM

Put include paths needed for HLL builds in config

Currently the NQP and Rakudo builds use a hard-coded list, but this is prep work for getting their builds to actually use data taken from the MoarVM build they're using.

+11 -0

0 comment

1 changed file

MasterDuke17

pr closed time in 5 hours

startedgithub/github-elements

started time in 5 hours

issue closedMoarVM/MoarVM

Random tests are failing with `No plan found in TAP output`

On various CI jobs different tests files are failing with the mentioned error, apparently being some MoarVM level failure.

Recent examples are:

https://dev.azure.com/MoarVM/MoarVM/_build/results?buildId=578&view=logs&j=d36c29d8-9236-5cd5-d848-768a0b8a3eb3&t=159b5397-e4a5-5784-febd-35f9e657944a

t/02-rakudo/06-is.t                                           (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=112, Tests=1835, 188 wallclock secs ( 0.77 usr +  0.33 sys =  1.09 CPU)
Result: FAIL

https://dev.azure.com/MoarVM/MoarVM/_build/results?buildId=578&view=logs&j=d0f6403b-d137-5ae0-a533-f4bebafcc251&t=608d3b9b-a763-5670-6013-39559d8f7fdf

t/04-nativecall/13-cpp-mangling.t                             (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=112, Tests=1816, 110 wallclock secs ( 0.48 usr  0.12 sys + 194.46 cusr 18.49 csys = 213.55 CPU)
Result: FAIL

https://dev.azure.com/MoarVM/MoarVM/_build/results?buildId=576&view=logs&j=4def8e43-62b3-5cca-1c32-fbd5a1f0442a&t=6f17dd53-63e8-5611-e660-0bfbef84498f

t/02-rakudo/10-nqp-ops.t                                      (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=112, Tests=1839, 155 wallclock secs ( 0.77 usr +  0.25 sys =  1.02 CPU)
Result: FAIL

https://dev.azure.com/MoarVM/MoarVM/_build/results?buildId=565&view=logs&j=70f6b8a1-f3cf-5727-bd79-d08ddb1caf67&t=f59a17df-92a9-5d7f-18bb-7f81f1c720a8

t/05-messages/moar/01-errors.t                                (Wstat: 256 Tests: 0 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=112, Tests=1840, 212 wallclock secs ( 1.06 usr +  0.25 sys =  1.31 CPU)
Result: FAIL

closed time in 7 hours

Altai-man

startedeveningkid/denodb

started time in 9 hours

push eventRaku/roast

Vadim Belman

commit sha 60629f08189f916317fe21c2ebe9d57d7988b304

Add tests for indirect inheritance and role consuming Test for cases: role R[::T] is T {} role R[::T] does T {} In support of rakudo/rakudo#4407

view details

Vadim Belman

commit sha bd1754fcedac88f3ce5a2b68c948d80d176a1a73

Merge pull request #737 from vrurg/allow-generic-inheritance Add tests for indirect inheritance and role consuming

view details

push time in 17 hours

PR merged Raku/roast

Add tests for indirect inheritance and role consuming

Test for cases:

role R[::T] is T {}
role R[::T] does T {}

In support of rakudo/rakudo#4407

+31 -1

0 comment

1 changed file

vrurg

pr closed time in 17 hours

PR opened Raku/roast

Add tests for indirect inheritance and role consuming

Test for cases:

role R[::T] is T {}
role R[::T] does T {}

In support of rakudo/rakudo#4407

+31 -1

0 comment

1 changed file

pr created time in 19 hours

push eventRaku/doc

Coke

commit sha 96ece3fe646c657243bf0f2e94937f170bf4c219

fix typo/learn word

view details

push time in 20 hours

issue commentRaku/doc

incorrect deprecation notice on .child

Thanks! :100:

coke

comment created time in 20 hours

push eventRaku/doc

Coke

commit sha c7392ee08ac93dfd8e79dd1b8e51b418bd2953f8

Remove deprecation notice Closes #3902

view details

push time in 20 hours

issue closedRaku/doc

incorrect deprecation notice on .child

https://docs.raku.org/type/IO::Path#method_child was updated from noting an eventual deprecation to a specific deprecation in 6.d - but that deprecation doesn't exist in rakudo or roast.

We should remove the deprecation warning entirely.

closed time in 20 hours

coke

issue openedRaku/doc

incorrect deprecation notice on .child

https://docs.raku.org/type/IO::Path#method_child was updated from noting an eventual deprecation to a specific deprecation in 6.d - but that deprecation doesn't exist in rakudo or roast.

We should remove the deprecation warning entirely.

created time in 20 hours

push eventRaku/doc

chirvasitua

commit sha ada40bc6388f4650d5aa65cefc8675f3549acbf0

fix typo in Callable.pod6

view details

push time in a day

PR merged Raku/doc

fix typo in Callable.pod6

The problem

Text in Callable:

If the object needs to be stored in a &-sigiled container, is has to implement Callable.

(my emphasis).

Solution provided

the one-character change

is has to -> it has to

<!--

The template below contains optional suggestions. Simply omit it
if you think it does not apply to this PR.

Please state clearly in "The problem" what you are addressing with this
pull request, referencing the issue(s) where it is described.

In "Solution provided", tell us what you have done to address the
problem.

-->

+1 -1

0 comment

1 changed file

stuart-little

pr closed time in a day

push eventnodeschool/nairobi

Antony Sande

commit sha cd63e37166644556bc0499864e51efe71c65f82d

feat: add june eventbrite link

view details

push time in a day

issue commentosxmidi/LinVst

Valhalla Supermassive support?

  1. Use x64 version
  2. Try those winetricks:
    mfc42
    vcrun6
    
    Hopefully they'll help
khughitt

comment created time in 2 days

pull request commentRaku/roast

Test cases where mkdir should fail

the test is dependent on information not directly known to it. It is assumed [...] To make it really reliable it must look like: [...] $*VM.constants<PATH_MAX>

That's true. However, having such constant correctly defined, i.e. specifically for each file system (instead of just hardcoding to a number with one or two known exceptions) is nontrivial. In addition, directory creations used by this test suite is making other assumptions as well, e.g. make-temp-file relies on PATH_MAX to be at least some certain number due to the inclusion of some prefixes and timestamps. Therefore, I wonder if it is OK to not let perfect be the enemy of good here and allow an assertion that probabilistically always do the right job and a patch to MoarVM that (IMHO) correct the semantic that has been broken for at least half a decade. Of course the opposite could have been said, that if it stayed broken for so long then it's probably OK to leave it that way, but I'd much prefer the other outcome.

McSinyx

comment created time in 2 days

pull request commentRaku/roast

Test cases where mkdir should fail

I think you missed my comment of it is about the directory/filename length limit, not total path name.

Basically, my note extends well to other system-level constants too.

The primary point is that the test is dependent on information not directly known to it. It is assumed, but there is no proof of correctness. Thus we can't trust test outcome. To make it really reliable it must look like:

my $path = make-temp-dir.add("foobar").add("a" x ($*VM.constants<PATH_MAX> + 1));
McSinyx

comment created time in 2 days

pull request commentRaku/roast

Test cases where mkdir should fail

@vrurg, I think you missed my comment of it is about the directory/filename length limit, not total path name. Though, I want to bring up that mkdir is inherently platform dependent, e.g. the file permission concept on Windows is quite different from the three-byte POSIX one mkdir on Raku uses. In other words, if Reiser (some of the few file systems known by Wikipedia to have filename length limit greater than 255) is supported we might want a special indicator in the test case.

McSinyx

comment created time in 2 days

issue openedosxmidi/LinVst

Valhalla Supermassive support?

Greetings!

First off, apologies if this isn't the best place to ask for advice trouble-shooting a particular VST -- just let me know if there is a better outlet for this kind of thing and I would be happy to close this issue and move the discussion there.

I was wondering if you might have any suggestions for how to trouble-shoot an issue I'm encountering when attempting to install the free Valhalla Supermassive VST?

Attempting to run the installer produces an error message:

wine internal error cannot expand "autocf64" constant on this version of windows.

It seems like it may be an issue with the Inno Setup installer used?

I tried installing Inno Setup itself, just in case, but that had no effect.

I also tried installing an earlier version of Supermassive (1.0.0) which includes 32-bit support, but the result was the same.

Any ideas what the issue might be, or more generally, what might be a good approach to try and track down the problem?

Any suggestions you can provide would be greatly appreciated.

Regardless, thank you for taking the time to create and share LinVst! I'm looking forwarding to never having to boot a non-linux machine again :)

created time in 2 days

pull request commentRaku/roast

Test cases where mkdir should fail

@niner It looks like we have no legal way to find out what the value of PATH_MAX is and I'd say it's important enough to be available in a non-platform, non-backend dependable way.

McSinyx

comment created time in 2 days

PR opened Tokyo-Buffalo/pow-wow-calendar

Bump postcss from 7.0.27 to 7.0.36

Bumps postcss from 7.0.27 to 7.0.36. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/postcss/postcss/releases">postcss's releases</a>.</em></p> <blockquote> <h2>7.0.36</h2> <ul> <li>Backport ReDoS vulnerabilities from PostCSS 8.</li> </ul> <h2>7.0.35</h2> <ul> <li>Add <a href="https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users">migration guide link</a> to PostCSS 8 error text.</li> </ul> <h2>7.0.34</h2> <ul> <li>Fix compatibility with <code>postcss-scss</code> 2.</li> </ul> <h2>7.0.33</h2> <ul> <li>Add error message for PostCSS 8 plugins.</li> </ul> <h2>7.0.32</h2> <ul> <li>Fix error message (by <a href="https://github.com/admosity"><code>@​admosity</code></a>).</li> </ul> <h2>7.0.31</h2> <ul> <li>Use only the latest source map annotation (by <a href="https://github.com/emzoumpo"><code>@​emzoumpo</code></a>).</li> </ul> <h2>7.0.30</h2> <ul> <li>Fix TypeScript definition (by <a href="https://github.com/nex3"><code>@​nex3</code></a>)</li> </ul> <h2>7.0.29</h2> <ul> <li>Update <code>Processor#version</code>.</li> </ul> <h2>7.0.28</h2> <ul> <li>Fix TypeScript definition (by <a href="https://github.com/nex3"><code>@​nex3</code></a>).</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/postcss/postcss/blob/main/CHANGELOG.md">postcss's changelog</a>.</em></p> <blockquote> <h2>7.0.36</h2> <ul> <li>Backport ReDoS vulnerabilities from PostCSS 8.</li> </ul> <h2>7.0.35</h2> <ul> <li>Add migration guide link to PostCSS 8 error text.</li> </ul> <h2>7.0.34</h2> <ul> <li>Fix compatibility with <code>postcss-scss</code> 2.</li> </ul> <h2>7.0.33</h2> <ul> <li>Add error message for PostCSS 8 plugins.</li> </ul> <h2>7.0.36</h2> <ul> <li>Backport ReDoS vulnerabilities from PostCSS 8.</li> </ul> <h2>7.0.35</h2> <ul> <li>Add migration guide link to PostCSS 8 error text.</li> </ul> <h2>7.0.34</h2> <ul> <li>Fix compatibility with <code>postcss-scss</code> 2.</li> </ul> <h2>7.0.33</h2> <ul> <li>Add error message for PostCSS 8 plugins.</li> </ul> <h2>7.0.32</h2> <ul> <li>Fix error message (by <a href="https://github.com/admosity"><code>@​admosity</code></a>).</li> </ul> <h2>7.0.31</h2> <ul> <li>Use only the latest source map annotation (by Emmanouil Zoumpoulakis).</li> </ul> <h2>7.0.30</h2> <ul> <li>Fix TypeScript definition (by Natalie Weizenbaum).</li> </ul> <h2>7.0.29</h2> <ul> <li>Update <code>Processor#version</code>.</li> </ul> <h2>7.0.28</h2> <ul> <li>Fix TypeScript definition (by Natalie Weizenbaum).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/postcss/postcss/commit/67e3d7b3402c5d3d036ab7c1e781f86910d6ca72"><code>67e3d7b</code></a> Release 7.0.36 version</li> <li><a href="https://github.com/postcss/postcss/commit/54cbf3c4847eb0fb1501b9d2337465439e849734"><code>54cbf3c</code></a> Backport ReDoS vulnerabilities from PostCSS 8</li> <li><a href="https://github.com/postcss/postcss/commit/12832f3d203474bd273bd06bd3b2407567bfe09e"><code>12832f3</code></a> Release 7.0.35 version</li> <li><a href="https://github.com/postcss/postcss/commit/4455ef6baf84ceea87cb662131f95d798063896c"><code>4455ef6</code></a> Use OpenCollective in funding</li> <li><a href="https://github.com/postcss/postcss/commit/e867c794b5d646839350dd4b76f3cc81423413e6"><code>e867c79</code></a> Add migration guide to PostCSS 8 error</li> <li><a href="https://github.com/postcss/postcss/commit/32a22a98bc4de9c7a2489041ceae24eedc62144f"><code>32a22a9</code></a> Release 7.0.34 version</li> <li><a href="https://github.com/postcss/postcss/commit/22939829688574b9acdbd29106ca2ec9470b2b17"><code>2293982</code></a> Lock build targets</li> <li><a href="https://github.com/postcss/postcss/commit/2c3a111a940b373a60fae196e63931b3b6e9d8ca"><code>2c3a111</code></a> Release 7.0.33 version</li> <li><a href="https://github.com/postcss/postcss/commit/4105f21b48d75847e822e89746633792c478922b"><code>4105f21</code></a> Use yaspeller instead of yaspeller-ci</li> <li><a href="https://github.com/postcss/postcss/commit/c8d02a0da503f9fa5d96a854a2c9244710c18c72"><code>c8d02a0</code></a> Revert yaspeller-ci removal</li> <li>Additional commits viewable in <a href="https://github.com/postcss/postcss/compare/7.0.27...7.0.36">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>

+5 -4

0 comment

1 changed file

pr created time in 2 days

startedroidrage/lograge

started time in 2 days

startedscmorrison/uzu

started time in 2 days

pull request commentRaku/roast

Test cases where mkdir should fail

+1 from me

McSinyx

comment created time in 2 days