profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ymtszw/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.
Yu Matsuzawa ymtszw @siiibo Tokyo, Japan https://scrapbox.io/ymtszw Elixir, Elm and other functional programming languages.

capitalist/elm-octicons 11

Octicons. For your Elm apps.

ymtszw/blick 2

Tech-presentation hub app, powered by Antikythera and Elm

utriage/utriage.github.io 1

Guild site for Ultimate Triage (US-Proudmoore)

ymtszw/build-elm-analyse 1

Run elm-analyse using atom-build

ymtszw/elm-broker 1

Data stream buffer for Elm application, inspired by Apache Kafka

ymtszw/elm-codegen 1

Thought experiment on Elm module file generator

ymtszw/absinthe 0

The GraphQL toolkit for Elixir

ymtszw/asdf-nodejs 0

Node.js plugin for asdf version manager

issue commenterlang/otp

openssl 3.0.0 compatible erlang version

For Homebrew users in mac:

openssl@3 is now installed if you invoke brew install openssl (without explicit version) and is linked to /usr/local/opt/openssl, which is one of the predefined standard locations of openssl. In that situation, due to the FIPS_mode related error posted above, build of erlang/otp 24.0.6 (presumably other versions too) with crypto/ssl/ssh will fail.

For now we need to use --with-ssl=$(brew --prefix openssl@1.1) option (when using brew with kerl or asdf-erlang)

satya-rajesh

comment created time in a day

PullRequestReviewEvent

push eventutriage/utriage.github.io

Gada

commit sha 18a6a23e4ef6fbd306961ba3298de9f4c4b5fbc1

chore: imageを入力しやすくする

view details

Gada

commit sha 5c4695e2f483bd023ae2a6d9ca5b174353df3536

feat: 9.1終了記事

view details

push time in 5 days

push eventutriage/utriage.github.io

Gada

commit sha 4464872a5fbe90b2015db14b301e547efef44781

feat: 2015年末年始の記事をサルベージ

view details

Gada

commit sha 7cc779623763e3322575adbcb0ca8dd49b510ee1

feat: 10周年

view details

Gada

commit sha 9d4535f35287d5d9a46681aa8dd0add09efcbaf2

feat: 全記事サルベージした

view details

Gada

commit sha f377a8af70bdabb9608e7459e6727fc4be5ab5ed

feat: 追記

view details

Gada

commit sha 1d1f22648da1559906320e079a94ef864077c816

feat: Odyn動画追加

view details

Gada

commit sha 52f2439db17a25d86fb90589d20a676d34f5c899

feat: サルベージ完了記念記事

view details

push time in 13 days

push eventutriage/utriage.github.io

Gada

commit sha 6d3ed310c503b3867ff5228397d740359b076455

chore: YouTube snippet追加

view details

Gada

commit sha 9fc166c9de483845434fa1a93e59f1c9bb8f9c74

feat: Gruul kill記事サルベージ

view details

Gada

commit sha ffb97e15c68758de582d60ba129fd48c1152de9c

feat: 追記

view details

Gada

commit sha 010d13bffe5c25c0a4ae859fa28164103acd8d26

feat: Mythic BRF記事サルベージ

view details

push time in 17 days

push eventutriage/utriage.github.io

Gada

commit sha f88288290baedd7a1c05242d501ca0f6f0ee6c87

feat: 動画も追加

view details

push time in 17 days

push eventutriage/utriage.github.io

Gada

commit sha e35a052c549c7bafe1d22ad5aa798881246f5259

feat: Mythic Try Raid最終回記事サルベージ

view details

push time in 17 days

push eventutriage/utriage.github.io

Yu Matsuzawa

commit sha feba9970cf551cd322ea95ebb67ce0b10b217c05

chore: image snippet

view details

Yu Matsuzawa

commit sha 4e0b0889970d2ee9ff7f141840a0b7a7e7fc92f6

chore: .vscode/をビルドに含めない

view details

Yu Matsuzawa

commit sha 34a965e722ad1fcd4a2244d206b46e7ad9e6d755

fix: --incrementalつかうとindexが再生成されないのでやめ

view details

Yu Matsuzawa

commit sha 8f38d798ab2f02331e8fb1977163deee19909092

feat: サルベージ記事2つ

view details

push time in 17 days

push eventutriage/utriage.github.io

Yu Matsuzawa

commit sha b31008ad461c4703a8776a9088d9ba3e55ac0cb4

fix: liquid文法

view details

push time in 17 days

push eventutriage/utriage.github.io

Yu Matsuzawa

commit sha 5b75265283a5f7f4951a074ba2b7a20bda4b77a0

feat: about.mdを更新

view details

push time in 17 days

PR merged utriage/utriage.github.io

Bump addressable from 2.7.0 to 2.8.0 dependencies

Bumps addressable from 2.7.0 to 2.8.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md">addressable's changelog</a>.</em></p> <blockquote> <h1>Addressable 2.8.0</h1> <ul> <li>fixes ReDoS vulnerability in Addressable::Template#match</li> <li>no longer replaces <code>+</code> with spaces in queries for non-http(s) schemes</li> <li>fixed encoding ipv6 literals</li> <li>the <code>:compacted</code> flag for <code>normalized_query</code> now dedupes parameters</li> <li>fix broken <code>escape_component</code> alias</li> <li>dropping support for Ruby 2.0 and 2.1</li> <li>adding Ruby 3.0 compatibility for development tasks</li> <li>drop support for <code>rack-mount</code> and remove Addressable::Template#generate</li> <li>performance improvements</li> <li>switch CI/CD to GitHub Actions</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sporkmonger/addressable/commit/6469a232c0f1892809ff66737370c765d574e16c"><code>6469a23</code></a> Updating gemspec again</li> <li><a href="https://github.com/sporkmonger/addressable/commit/24336385de0261571b3adaad0431459edb420c79"><code>2433638</code></a> Merge branch 'main' of github.com:sporkmonger/addressable into main</li> <li><a href="https://github.com/sporkmonger/addressable/commit/e9c76b889789c75d7073c17b0ab557635d3f6704"><code>e9c76b8</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sporkmonger/addressable/issues/378">#378</a> from ashmaroli/flat-map</li> <li><a href="https://github.com/sporkmonger/addressable/commit/56c5cf7ece9223ff4240e07078cc26d3adbbbd30"><code>56c5cf7</code></a> Update the gemspec</li> <li><a href="https://github.com/sporkmonger/addressable/commit/c1fed1ca0a44c448e74d761fd44ed94869199807"><code>c1fed1c</code></a> Require a non-vulnerable rake</li> <li><a href="https://github.com/sporkmonger/addressable/commit/0d8a3127e35886ce9284810a7f2438bff6b43cbc"><code>0d8a312</code></a> Adding note about ReDoS vulnerability</li> <li><a href="https://github.com/sporkmonger/addressable/commit/89c76130ce255c601f642a018cb5fb5a80e679a7"><code>89c7613</code></a> Merge branch 'template-regexp' into main</li> <li><a href="https://github.com/sporkmonger/addressable/commit/cf8884f815c96b646c796f707bf768cf6eb65543"><code>cf8884f</code></a> Note about alias fix</li> <li><a href="https://github.com/sporkmonger/addressable/commit/bb03f7112e8e478240a0f96e1cc7428159b41586"><code>bb03f71</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sporkmonger/addressable/issues/371">#371</a> from charleystran/add_missing_encode_component_doc_entry</li> <li><a href="https://github.com/sporkmonger/addressable/commit/6d1d8094a66cbf932ecf69db6850bc9edaf86de0"><code>6d1d809</code></a> Adding note about :compacted normalization</li> <li>Additional commits viewable in <a href="https://github.com/sporkmonger/addressable/compare/addressable-2.7.0...addressable-2.8.0">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>

+2 -2

1 comment

1 changed file

dependabot[bot]

pr closed time in 17 days

delete branch utriage/utriage.github.io

delete branch : dependabot/bundler/addressable-2.8.0

delete time in 17 days

push eventutriage/utriage.github.io

dependabot[bot]

commit sha 8e0937b615ec776f4c0c08add021d61e80782bb7

Bump addressable from 2.7.0 to 2.8.0 Bumps [addressable](https://github.com/sporkmonger/addressable) from 2.7.0 to 2.8.0. - [Release notes](https://github.com/sporkmonger/addressable/releases) - [Changelog](https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md) - [Commits](https://github.com/sporkmonger/addressable/compare/addressable-2.7.0...addressable-2.8.0) --- updated-dependencies: - dependency-name: addressable dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Yu Matsuzawa

commit sha 806a6f687f37b3960e3ce04ea3f4ce3b2dc9cb55

Merge remote-tracking branch 'origin/dependabot/bundler/addressable-2.8.0'

view details

push time in 17 days

push eventutriage/utriage.github.io

Yu Matsuzawa

commit sha 246d1046e4d7f5419b46078c97f8c18b9078e7b0

feat: sylvanasクリア記事

view details

push time in 17 days

push eventymtszw/hiden

Yu Matsuzawa

commit sha c6f34e771cc51894614a43969c81381629c1abd9

chore: git-checkotuがnonzeroを返すようになったので、andを削除

view details

push time in 18 days

issue commentymtszw/elm-xml-decode

`stringAttr` cuts values

Since jinjor is inactive for a while, I'm considering vendoring jinjor/elm-xml-parser inside this package with open pull-requests applied to fix this issue. (Like dillonkearns/elm-markdown did.) Will work on it if I got time, but anyone else picking up the work it would be greatly appreciated.

miniBill

comment created time in 24 days

push eventymtszw/hiden

Yu Matsuzawa

commit sha 315d12c5c57b4b3d3e186b64f5355e3697923eea

chore: add wget

view details

push time in a month

pull request commentabsinthe-graphql/absinthe

Add failing test for macro deprecated field in SDL render

@benwilson512 Thanks, now it became clearer. Shame I haven't caught up with the latest features.

So the missing part is: in macro-defined schema, collaterally add "deprecated" directives in nodes when they have deprecate/1 macro or :deprecate attr attached, right? (Is this what @binaryseed meant in his post?)

I could possibly investigate this field in coming weekend(s). Any other guidance would be welcome if any.

maartenvanvliet

comment created time in a month

pull request commentabsinthe-graphql/absinthe

Add failing test for macro deprecated field in SDL render

@binaryseed Hi, let me clarify the situation so that I could tackle on the issue:

  • Currently Absinthe DOES support "defining" directives in macro schema, but DOES NOT support "calling/applying/using" defined directives as per https://elixirforum.com/t/how-to-apply-directives-on-fields-in-absinthe/20089/2 Is this still correct?
  • If the above holds, the most "proper" way to solve this issue is:
    • (1) introduce the whole directive mechanisms to support "applying" directives to various GQL locations as per https://spec.graphql.org/draft/#DirectiveLocation
    • and (2) render SDLs based on actually applied directives in our schema
    • then (3) with (2), @deprecated and maybe-future-coming other "default directives" (such as @skip) are mere directives inside, so they are rendered alongside with user-defined directives
  • "The whole directive mechanisms" is obviously a significant undertaking. My gut feeling says for now we should special-case @deprecated and use :deprecations in SDL rendering. What do you think on this?
    • Since deprecation mechanism is crucial for incremental type-safe development, I foresee many users will benefit from this.
    • For example, in our workflow we utilize GraphQL Inspector for detecting deprecations/breaking changes, so properly rendering @deprecated in SDL greatly contributes to our type-based confidence!

BTW, I have found that @deprecated on args and input fields were rather new and still not merged to the official spec, to my surprise. https://github.com/graphql/graphql-spec/pull/805

maartenvanvliet

comment created time in a month

PullRequestReviewEvent

Pull request review commentsiiibo/shujinosuke

[feat] launch automation

 const getChannelStateMessage = (channelId: string) => { const getListen = (client: SlackClient, event: SlackEvent) => {   switch (event.type) {     case 'app_mention':-      return (regExp: RegExp, callback: (client: SlackClient, event: AppMentionEvent) => void) => {-        const messageContent = event.text.replace(/^<@\w+>\s*/, '');-        if (messageContent.match(regExp)) {+      return (command: string, callback: (client: SlackClient, event: AppMentionEvent) => void) => {+        const commandRegExp = new RegExp(`<@\\w+[\\w\\s\|]*>\\s+${command}($|\\s+)`);

リマインダーで勝手に.が補われるパターンもここで対応していいと思います。

hi-se

comment created time in a month

PullRequestReviewEvent

Pull request review commentsiiibo/shujinosuke

[feat] launch automation

 const getChannelStateMessage = (channelId: string) => { const getListen = (client: SlackClient, event: SlackEvent) => {   switch (event.type) {     case 'app_mention':-      return (regExp: RegExp, callback: (client: SlackClient, event: AppMentionEvent) => void) => {-        const messageContent = event.text.replace(/^<@\w+>\s*/, '');-        if (messageContent.match(regExp)) {+      return (command: string, callback: (client: SlackClient, event: AppMentionEvent) => void) => {+        const commandRegExp = new RegExp(`<@\\w+[\\w\\s\|]*>\\s+${command}($|\\s+)`);

ああちょっと勘違いしてた。messageContentはなんか勝手に生成されるものじゃなくて自分で作ってたか。 (Botkitは確かにこんな感じの処理をやってメッセージ先頭のメンション文字列を削ってた記憶)

hi-se

comment created time in a month

PullRequestReviewEvent

Pull request review commentsiiibo/shujinosuke

[feat] launch automation

 const getChannelStateMessage = (channelId: string) => { const getListen = (client: SlackClient, event: SlackEvent) => {   switch (event.type) {     case 'app_mention':-      return (regExp: RegExp, callback: (client: SlackClient, event: AppMentionEvent) => void) => {-        const messageContent = event.text.replace(/^<@\w+>\s*/, '');-        if (messageContent.match(regExp)) {+      return (command: string, callback: (client: SlackClient, event: AppMentionEvent) => void) => {+        const commandRegExp = new RegExp(`<@\\w+[\\w\\s\|]*>\\s+${command}($|\\s+)`);

リマインダーで始まる場合(=@Shujinosukeが先頭に来てないメッセージ)でも、app_mentionイベントとして取れてました? その場合、messageContentはどうなってましたか?(event.textにマッチ対象を変えているが)

hi-se

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentsiiibo/figma-notification

Migration to heroku

アプリ招待確認しました。アイコンはFigmaのアイコン使わせてもらった

masam0

comment created time in a month

Pull request review commentsiiibo/figma-notification

Migration to heroku

 # figma-notification -Google Apps Script で作成している Slack Bot です。+TypeScript + Heroku で作成している Slack Bot です。  ## 機能 -- Figmaファイルの変更をSlackに通知+- Figmaファイルのバージョン更新をSlackに通知+- Figmaファイル上のコメントをSlackに通知   ## 環境構築 -- [clasp](https://github.com/google/clasp)をインストール-  - GAS プロジェクトの開発をローカルで行うためのツール-  - `npm install -g @google/clasp` など(詳細はリンク先参照)-- figma-notification の GAS プロジェクトにアクセスできるアカウントで `clasp login`+- [ngrok](https://ngrok.com/)をインストール+  - brew cask install ngrokなど+- [heroku CLI](https://devcenter.heroku.com/ja/articles/heroku-cli)をインストール - このリポジトリを clone して、以下実行    ```sh   asdf install   asdf reshim yarn   yarn   ```-- `clasp clone xxxSCRIPT-IDxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`を実行(引数はfigma-notificationのスクリプトID)--- 完全に新しいGASプロジェクトに移行する時は初回のみ以下の操作が必要(更新の場合は不要)-  - `yarn run buildpush` を実行-  - GASエディタを開き( `clasp open` )、 `init` 関数を実行する-    - 初回の実行時はGASに権限付与する必要があるので、画面にしたがって権限を付与する-    - `init` によってSlackTokenなど必要な情報がGASプロジェクトに登録される  ## 開発  ### テスト環境 -- テスト環境で開発する場合は `clasp deploy` で新規デプロイを行う-  - GASはデプロイの度に新規URLが作成されるので注意-  - コードを更新することが目的の場合は、新規デプロイではなくデプロイを更新する-    - デプロイの更新をするには `clasp deploy -i <deploymentID>` を実行する-- `https://api.slack.com/apps/A0108T7KFV0/event-subscriptions` からGASでデプロイしたWebAppのURL を設定-  - `https://script.google.com/macros/s/<deploymentID>/exec` のような値-- `https://api.slack.com/apps/A0108T7KFV0/interactive-messages` にも同じ値を設定-- 適当なテストチャンネルに"Figma-notification"アプリをインストール、もしくはすでにインストール済みのチャンネルで作業-- すでにクラウドにデプロイしたものがある場合、上記開発作業が完了したらデプロイ先ドメインの値に戻す-+- `.env-template`ファイルを基に`.env`ファイルを作成し、Slack Botのトークンを記述する。+- `yarn build`で`backend.js`ファイルを生成する。+- figma-notificationリポジトリ上で `heroku local`を実行(`yarn start`でも可)。localhostの5000番ポートでリクエストを受信できる+- `ngrok http 5000`で、先程のlocalhost:5000をngrok proxy 経由で露出+- [Figma APIサイト](https://www.figma.com/developers/api#webhooks_v2)上で、SiiiboチームのWebhookを登録+  - Webhook新規登録の場合はPOSTリクエスト+  - Webhook Endpoint URL更新の場合はPUTリクエスト+     ### 本番環境 -- GASへの移行後一時的に同期は解除されている-  - 近日中にGHAを用いて同期処理を実装する予定-- ローカルでコードを変更した後手動でデプロイ-  - `yarn run buildpush` を実行-  - `clasp deploy -i <deploymentId>` を実行+- Herokuに free dyno でデプロイする+- アカウントはtech@siiibo.com。認証情報は既存メンバから取得する+  - Heroku CLIをインストールすればローカルから情報の取得や設定ができる+- ローカル開発時に.envに設定している認証情報は、Heroku では Config Var として設定する+  - 待ち受けポートは、自動的に Heroku によってPORT環境変数経由で設定される+- GitHub リポジトリと同期しているので、GitHub にmasterブランチを push すればデプロイされる (作業中)
- GitHub リポジトリと同期しているので、GitHub にmasterブランチを push すればデプロイされる
  - Herokuの[Node.jsビルドパックのビルドプロセス](https://devcenter.heroku.com/ja/articles/nodejs-support#customizing-the-build-process)にしたがって、`build`及び`heroku-postbuild`などのスクリプトが実行される
  - サーバ起動コマンドは`Procfile`に記述する

最後、Heroku上でサーバ起動に至る部分が知りたかったので追記

masam0

comment created time in a month