profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/mugli/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.

mugli/learning-graphql 913

An attempt to learn GraphQL

mugli/Avro-Keyboard 97

Unicode compliant native Bangla/Bengali Input Method Editor (IME) for Windows

mugli/go-kill-mysql-query 68

Interactively shows long running queries in MySQL server and provides option to kill them one by one

mugli/orkid-node 48

Reliable and modern Redis Streams based task queue for Node.js 🤖

mugli/container-from-scratch-in-go 31

Toy container build from scratch in Go solely for learning purpose

mugli/png2escpos 15

Quickly convert PNG files to ESC/POS format, for printing on Epson thermal point-of-sale printers. Written in Go/Golang

mugli/libavrophonetic 10

Go module providing classic (rule-based) and dictionary backed transliterators for Avro Phonetic

mugli/unstupify 10

Chrome extension for hiding Priyo.com posts on Facebook

mugli/rust-for-nodejs-developers 6

Code examples for people learning Rust coming from Node.js

mugli/orkid-ui 3

Dashboard to monitor and manage Orkid task queue ✨

created repositorygaearon/react-lag-radar

created time in 34 minutes

starteddomitriusclark/mdnext

started time in 40 minutes

startedrocicorp/replicache

started time in 40 minutes

release vercel/next.js

v11.0.1-canary.0

released time in 42 minutes

pull request commentfclairamb/afero-s3

Update module github.com/aws/aws-sdk-go to v1.38.62

Codecov Report

Merging #260 (c9561c4) into master (86f52e9) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #260   +/-   ##
=======================================
  Coverage   78.87%   78.87%           
=======================================
  Files           3        3           
  Lines         303      303           
=======================================
  Hits          239      239           
  Misses         40       40           
  Partials       24       24           

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 86f52e9...c9561c4. Read the comment docs.

renovate[bot]

comment created time in an hour

PR opened fclairamb/afero-s3

Update module github.com/aws/aws-sdk-go to v1.38.62

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
github.com/aws/aws-sdk-go require patch v1.38.61 -> v1.38.62

Release Notes

<details> <summary>aws/aws-sdk-go</summary>

v1.38.62

Compare Source

===

Service Client Updates
  • service/connect: Updates service API, documentation, and paginators
  • service/ec2: Updates service API
    • EC2 M5n, M5dn, R5n, R5dn metal instances with 100 Gbps network performance and Elastic Fabric Adapter (EFA) for ultra low latency
  • service/models.lex.v2: Updates service API and documentation
  • service/redshift-data: Updates service API and documentation
  • service/runtime.lex.v2: Updates service API and documentation

</details>


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+3 -1

0 comment

2 changed files

pr created time in an hour

create barnchfclairamb/afero-s3

branch : renovate/github.com-aws-aws-sdk-go-1.x

created branch time in an hour

release home-assistant/core

2021.6.5

released time in an hour

startedrocicorp/replicache

started time in 2 hours

startedsnowpackjs/astro

started time in 2 hours

startedwoltapp/blurhash

started time in 2 hours

PR opened athensresearch/athens

feat(rtc): add presence toolbar
+235 -1

0 comment

2 changed files

pr created time in 2 hours

push eventthlorenz/v8-perf

Thorsten Lorenz

commit sha 339e9db94ff25dc2b1015a9cc202f2bbd9b43e46

chore: removing patreon badge

view details

push time in 2 hours

starteddortania/OpenCore-Post-Install

started time in 3 hours

pull request commentnathankellenicki/node-poweredup

Fix path for constants after renaming it

Thanks for this! Not sure why it continued building for me, but I can see the error. Merged!

10on

comment created time in 3 hours

PR merged nathankellenicki/node-poweredup

Fix path for constants after renaming it

After merging PR https://github.com/nathankellenicki/node-poweredup/pull/130 project can not build from master branch. This fix should be resolve this issue.

+3 -3

0 comment

1 changed file

10on

pr closed time in 3 hours

push eventnathankellenicki/node-poweredup

Denis Pushkarev

commit sha fbf5b5ccf3807ed3d692d2654a84ca1dcc21a2d7

Fix path for constants after renaming it

view details

Nathan Kellenicki

commit sha 6a02a89e5ed34621132708e4fe84b4d1bdd137dc

Merge pull request #135 from 10on/master Fix path for constants after renaming it

view details

push time in 3 hours

startedvsavkin/large-repo

started time in 3 hours

startednewwwton/angular-tailwind-storybook

started time in 3 hours

release planetscale/cli

v0.47.0

released time in 4 hours

created repositoryjvns/fringe-2021-schedule

created time in 4 hours

release vercel/next.js

v11.0.0

released time in 4 hours

startedmgattozzi/zsh-module-poc

started time in 5 hours

issue openedathensresearch/athens

TypeError: Cannot read property 'offsetTop' of null

Problem

message=Uncaught TypeError: Cannot read property 'offsetTop' of null
source=file:///tmp/.mount_AthensTZzJa8/resources/app.asar/resources/public/js/compiled/renderer.js
Lineno=285
colno=483
error=TypeError: Cannot read property 'offsetTop' of null
``

**Screenshots/Demo**

This doesn't happen consistently, but appears to correspond to being on a page that's not today's page and then double-clicking the calendar icon to get to today's page. It may or may not require having the originating page designated as a shortcut.

**Athens Version**

Athens 1.0.0-BETA.88

created time in 5 hours

release prisma/prisma

2.25.0

released time in 5 hours

release vercel/next.js

v10.2.4-canary.19

released time in 5 hours

issue commentasyncapi/spec

Establish a mechanism for bindings specs to contribute schema objects for protocol headers

@GeraldLoeffler I'm happy that I understood you 😄

However, this should be treated like the other schemas in that directory (server.json, message.json, ...), with agreed-upon filename etc., so that the $ref from the AsyncAPI docs has the same syntax for all bindings:

yes exactly, that was my idea with common.json filename. If we go with tag versioning for bindings - every patch/minor/major version of binding will have separate git tag in repo, then we can still ref to appropriate version, but... writing each time https://raw.githubusercontent.com/asyncapi/bindings/master/http/json_schemas/common.json link can be annoying, so I don't know if it's possible with JSON Ref but having some shortcut for some links like https://raw.githubusercontent.com/asyncapi/bindings/master/http/json_schemas/common.json could be #bindings/http/common etc.

GeraldLoeffler

comment created time in 5 hours

issue commentasyncapi/spec

Establish a mechanism for bindings specs to contribute schema objects for protocol headers

thanks @magicmatatjahu for interpreting my thoughts and discussing them with @derberg ;) : you're right, my concern is that schemas like httpHeader from @derberg 's example should come from the binding spec, to make it much easier for AsyncAPI docs to refer to common protocol headers.

I certainly did not want to propose to

apply it automatically to the AsyncAPI document

but rather to discuss the issue and find an uniform approach for an AsyncAPI document to reference such a common schema of protocol headers.

I do think this could be a solution:

At the moment I can only suggest to have some common data (not only headers) for protocols/bindings inside the bindings repo and make $ref to them like $ref: https://raw.githubusercontent.com/asyncapi/bindings/master/http/json_schemas/common.json#headers

However, this should be treated like the other schemas in that directory (server.json, message.json, ...), with agreed-upon filename etc., so that the $ref from the AsyncAPI docs has the same syntax for all bindings: https://raw.githubusercontent.com/asyncapi/bindings/master/http/json_schemas/common.json#headers`

GeraldLoeffler

comment created time in 5 hours

startedsnowpackjs/astro

started time in 5 hours

release vercel/next.js

v10.2.4-canary.18

released time in 5 hours