pakoito Github contribution chart
pakoito Github Stats
pakoito Most Used Languages

Activity

21 Sep 2022

Pakoito

started

Started On 21 Sep 2022 at 10:56:12

Pakoito

Transforms PDF, Documents and Images into Enriched Structured Data

Forked On 21 Sep 2022 at 10:56:07
Issue Comment

Pakoito

Spotify first time Auth not working

Description

This issue is taking a while to solve as I cannot find the origin of it, therefore there'll be a guide on how to solve it below.
The actual issue is that when you create a new app on the Spotify Dashboard, AudioBand doesn't have enough permission to allow the user who made the app to use it, which is quite weird.

The exact error given is User not registered in the Developer Dashboard.

Manual Fix

  1. Go to the Spotify Dashboard -> log in -> go to your AudioBand app -> Add https://getyourspotifyrefreshtoken.herokuapp.com/callback to your redirect urls.
  2. Go to https://getyourspotifyrefreshtoken.herokuapp.com/ and enter your client id and secret there.
  3. Select the following scopes and press submit, you will receive your Spotify Refresh Token image
  4. Go to AudioBand Settings -> About -> Open Settings Folder (file explorer should open)
  5. Open settings.json, look for the setting called: Spotify Refresh Token and change it to be as followed: (underneath the red line you have to paste your Refresh Token received from the external site) image

Permanent Fix

So far I've tried changing around the settings on the Dashboard, yields were unsuccessful however.
I've tried adding my own account's email to the allowed users and tried changing the redirect urls.

On my main Spotify Account I can reset my authentication without issue, but it has Extended Quota on the Dashboard, while the new app doesn't and that fails.

I'll try to fix this issue soon as it is quite annoying.

Forked On 26 Aug 2022 at 03:18:33

Pakoito

Heroku is going down shortly, you may need an alternative deploy.

Commented On 26 Aug 2022 at 03:18:33

Pakoito

started

Started On 25 Aug 2022 at 10:57:25
Issue Comment

Pakoito

Made it so RxPaper2 would use the newest version of RxJava3 instead of RxJava2
Forked On 25 Aug 2022 at 10:53:34

Pakoito

It's been a year since this PR and I believe we had a chat about it, so in case I imagined it all up let me write down my thoughts here again :D

I believe RxPaper3 should be in a new repo by a new owner. I'm not spending enough time on opensource these years and someone else could give it more care. I'm happy to link to it once it's out.

Commented On 25 Aug 2022 at 10:53:34

Pakoito

Forked On 20 Aug 2022 at 11:23:38
Issue Comment

Pakoito

ESModule support failure due to `require`-ing our client code

Expected Behavior

Pointing the CMD to handler.handle.mjs should make the lambda compatible with ESModules.

Actual Behavior

When launching our handler with package.json specifying "modules" and pointing our Docker file to "handler.handle.mjs", we see a require error at runtime.

2022-07-20T12:09:01.317Z	undefined	ERROR	Uncaught Exception 	
{
    "errorType": "Error",
    "errorMessage": "require() of ES Module /var/task/app.js from /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js not supported.\nInstead change the require of app.js in /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js to a dynamic import() which is available in all CommonJS modules.",
    "code": "ERR_REQUIRE_ESM",
    "stack": [
        "Error [ERR_REQUIRE_ESM]: require() of ES Module /var/task/app.js from /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js not supported.",
        "Instead change the require of app.js in /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js to a dynamic import() which is available in all CommonJS modules.",
        "    at Module.Hook.Module.require (/var/task/node_modules/dd-trace/packages/dd-trace/src/ritm.js:72:33)",
        "    at _tryRequireSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:248:12)",
        "    at _loadUserAppSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:286:16)",
        "    at loadSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:374:19)",
        "    at Object.<anonymous> (/var/task/node_modules/datadog-lambda-js/dist/handler.js:35:27)",
        "    at _tryRequireFile (file:///var/runtime/index.mjs:857:37)",
        "    at _tryRequire (file:///var/runtime/index.mjs:907:25)",
        "    at _loadUserApp (file:///var/runtime/index.mjs:933:22)",
        "    at Object.UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:964:27)",
        "    at start (file:///var/runtime/index.mjs:1124:42)",
        "    at file:///var/runtime/index.mjs:1130:7",
        "    at async Promise.all (index 0)"
    ]
} 

Where app.js is our client code, transpiled to ES2020 using tsc with esmoduleinterop and isolatedModules enabled. Node is configured to use experimental node resolution for imports so file extensions aren't needed.

Steps to Reproduce the Problem

  1. Create a new Docker-based nodejs project with datadog. Use TSC to compile with configurations above.
  2. Point Docker to CMD ["node_modules/datadog-lambda-js/dist/handler.handler.mjs"]
  3. Deploy with serverless
  4. See error above

Specifications

  • Datadog NPM version: 6.81.X
  • Node version: 16.X

Stacktrace

2022-07-20T12:09:01.317Z	undefined	ERROR	Uncaught Exception 	
{
  "errorType": "Error",
  "errorMessage": "require() of ES Module /var/task/app.js from /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js not supported.\nInstead change the require of app.js in /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js to a dynamic import() which is available in all CommonJS modules.",
  "code": "ERR_REQUIRE_ESM",
  "stack": [
      "Error [ERR_REQUIRE_ESM]: require() of ES Module /var/task/app.js from /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js not supported.",
      "Instead change the require of app.js in /var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js to a dynamic import() which is available in all CommonJS modules.",
      "    at Module.Hook.Module.require (/var/task/node_modules/dd-trace/packages/dd-trace/src/ritm.js:72:33)",
      "    at _tryRequireSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:248:12)",
      "    at _loadUserAppSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:286:16)",
      "    at loadSync (/var/task/node_modules/datadog-lambda-js/dist/runtime/user-function.js:374:19)",
      "    at Object.<anonymous> (/var/task/node_modules/datadog-lambda-js/dist/handler.js:35:27)",
      "    at _tryRequireFile (file:///var/runtime/index.mjs:857:37)",
      "    at _tryRequire (file:///var/runtime/index.mjs:907:25)",
      "    at _loadUserApp (file:///var/runtime/index.mjs:933:22)",
      "    at Object.UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:964:27)",
      "    at start (file:///var/runtime/index.mjs:1124:42)",
      "    at file:///var/runtime/index.mjs:1130:7",
      "    at async Promise.all (index 0)"
  ]
} 

Forked On 28 Jul 2022 at 11:54:03

Pakoito

Thank you both for the help!

Commented On 28 Jul 2022 at 11:54:03

Pakoito

add merge function for *Effect
Merged On 03 Jul 2022 at 08:47:05

Pakoito

Commented On 03 Jul 2022 at 08:47:05

Pakoito

catch for EffectScope

This PR adds a small utility method for "simulating" catch as we have for exceptions. If this is useful, a bunch of other utility methods can be implemented on top of it, but first I wanted to know whether you like this catch.

Merged On 03 Jul 2022 at 08:46:26

Pakoito

Commented On 03 Jul 2022 at 08:46:26
Merge

Pakoito

catch for EffectScope

This PR adds a small utility method for "simulating" catch as we have for exceptions. If this is useful, a bunch of other utility methods can be implemented on top of it, but first I wanted to know whether you like this catch.

Forked On 03 Jul 2022 at 08:46:26

Pakoito

NIT: Recover first, operation last.
On 03 Jul 2022 at 08:46:26

Pakoito

started

Started On 03 Jul 2022 at 08:44:03

Pakoito

started

Started On 03 Jul 2022 at 08:43:56

Pakoito

Add an instability warning to the README for version3.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Reference rooms by id rather than coords. Doesn't build yet.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Add targetRoomId to the Edge class.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

First pass refactoring of the core library to not care about rooms being grid-aligned.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Fix a bunch of initial bugs.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Add colormaps and free-form (non-grid) dungeon constraints.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Make the GridDungeonView work with non-cardinal directions.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Scale rooms and edges differently.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Draw the original colormap behind the freeform dungeon.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Fix relative positioning of background and rooms.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Add some minor improvements to the API to make it easier to integrate into games.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Fix CountConstraints putting the entrance room at the top.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Enable the FreeformDungeonView to color by intensity as well as id.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Fix a division by zero when MaxKeys = 0. Closes gh-1.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Merge branch 'fix-gh-1' into version3

Conflicts: src/net/bytten/metazelda/generators/DungeonGenerator.java

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Remove a faulty assert -- sometimes false due to the generator being on a separate thread.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Allow certain edges between rooms to be preferred via weighting.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Make graphification probability configurable.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Add a bunch of new abilities:

  • Specify that certain rooms can only be placed after the generator has reached a certain key level.
  • Enable/disable goal rooms (alternative is just to place the boss).
  • Enable/disable locking of the boss door (required for the first bullet for subtle reasons, explained where OutOfRoomException is caught in DungeonGenerator).

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Allow clients more control over what kinds of rooms can be linked.

Pushed On 03 Jul 2022 at 08:43:51

Pakoito

Card IDE (CIDEr) - Design game cards using HTML/Handlebars, CSS, and tabular data

Forked On 03 Jul 2022 at 08:43:21

Pakoito

Dockerize
Forked On 29 Jun 2022 at 11:12:06

Pakoito

I do not understand your complaints, how GUI is involved in all of this and how is it any different in Apache.

Commented On 29 Jun 2022 at 11:12:06

Pakoito

Dockerize
Forked On 29 Jun 2022 at 11:08:43

Pakoito

...what?

Commented On 29 Jun 2022 at 11:08:43