profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/abury/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.
Aron abury @GymLeads Australia I build things on the internet

abury/ABPadLockScreen 497

A simple keypad lock screen for the iPad

abury/input-moment 0

React datetime picker powered by momentjs

abury/react-infinite-calendar 0

✨ Infinite scrolling date-picker built with React, with localization, themes, keyboard support, and more.

abury/react-native-touch-id 0

React Native authentication with the native Touch ID popup.

startedosdnk/react-native-reanimated-bottom-sheet

started time in 4 days

startedthodubois/react-native-woodpicker

started time in 6 days

startedaws-cloudformation/cloudformation-cli

started time in 7 days

issue commentwix/react-native-calendars

state value updates on calendar properties like "current" does not lead to the calendar re-rendering

I can not for the life of me get this to work. I've trawled all the tickets for a solution, tried setting the key, using different formats, using callbacks, NOTHING is working. Does anyone know the version where selecting a date actually works?

brandonra97

comment created time in 13 days

issue commentwix/react-native-calendars

refresh current props

Thanks for the reply @mickeylam, but no that doesn't work.

CorentinHeroux

comment created time in 13 days

issue commentwix/react-native-calendars

refresh current props

Try passing key={current} to your Calendar. It works for me

Glad this is working for some, but definitely not working for me. Given that current needs to be a Date type and key is a string, I'm not sure how this is supposed to work.

The type docs also say that we shouldn't need to use this. We shouldn't need to utilize an internal attribute for something as basic as programmatically selecting the selected date in a calendar. Might be worth discussing how we can get a proper fix this?

CorentinHeroux

comment created time in 14 days

issue commentexpo/expo-cli

Expo build failing for IOS

Is this still an issue? Fastlane is showing this as resolved: https://github.com/fastlane/fastlane/issues/19264#issuecomment-904318685

fessor10

comment created time in a month

startedquay/clair

started time in 2 months

startedxitongsys/parquet-go

started time in 2 months

issue commentdocker-library/postgres

My data lost after removing the container

@erulabs I'm seeing the same after updating to Postgres 13, did you find anything interesting in your research?

pavelkeyzik

comment created time in 2 months

startedheroku/umpire

started time in 2 months

issue closedelm-tooling/elm-language-client-vscode

Language server unable to start - Unkown system error

Hey all

I've been trying to get the elm language client to work for a few days without much luck. It looks like the language server is unable to start due to an unkown system error. It cites being unable to determine the elm version, but I'm not sure why that would be the case. Elm is installed globally and locally within node_modules.

Would love any insights on how I can get this to work!

I've double and triple checked everything. Elm is installed correctly, node 14 is installed, everything else elm related is working fine.

Current Behavior

Language server fails to start, output below:

[Info  - 8:55:47 am] Loading Elm tree-sitter syntax from ../../../../.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/tree-sitter-elm.wasm
[Info  - 8:55:47 am] Found 2 elm.json files for workspace /Users/<username>/Documents/apps/<project-name>/client
[Info  - 8:55:47 am] Found 1 unique elmWorkspaces for workspace /Users/<username>/Documents/apps/<project-name>/client
[Info  - 8:55:47 am] Starting language server for folder: file:///Users/<username>/Documents/apps/<project-name>/client
[Warn  - 8:55:47 am] {"errno":-8,"code":"Unknown system error -8","syscall":"spawnSync elm","path":"elm","spawnargs":["--version"],"originalMessage":"spawnSync elm Unknown system error -8","shortMessage":"Command failed with Unknown system error -8: elm --version\nspawnSync elm Unknown system error -8","command":"elm --version","stdout":"","stderr":"","failed":true,"timedOut":false,"isCanceled":false,"killed":false}
[Warn  - 8:55:47 am] Could not figure out elm version, this will impact how good the server works. 
 Error: Command failed with Unknown system error -8: elm --version
spawnSync elm Unknown system error -8
    at Object.spawnSync (internal/child_process.js:1067:20)
    at Object.spawnSync (child_process.js:611:24)
    at Function.module.exports.sync (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/node_modules/execa/index.js:167:25)
    at execCmdSync (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/utils/elmUtils.js:45:32)
    at Object.getElmVersion (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/utils/elmUtils.js:90:20)
    at Program.<anonymous> (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/program.js:172:36)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/program.js:24:58)
[Info  - 8:55:47 am] Reading elm.json from /Users/<username>/Documents/apps/<project-name>/client/elm.json
[Warn  - 8:55:47 am] {"errno":-8,"code":"Unknown system error -8","syscall":"spawnSync elm","path":"elm","spawnargs":["make"],"originalMessage":"spawnSync elm Unknown system error -8","shortMessage":"Command failed with Unknown system error -8: elm make\nspawnSync elm Unknown system error -8","command":"elm make","stdout":"","stderr":"","failed":true,"timedOut":false,"isCanceled":false,"killed":false}
[Error - 8:55:47 am] Error parsing files for /Users/<username>/Documents/apps/<project-name>/client/elm.json:
Error: ENOENT: no such file or directory, open '/Users/<username>/.elm/undefined/packages/NoRedInk/elm-json-decode-pipeline/1.0.0/elm.json'
[Error - 8:55:47 am] Notification handler 'textDocument/didOpen' failed with message: Cannot read property 'getTree' of undefined
[Error - 8:55:47 am] Notification handler 'textDocument/didOpen' failed with message: Cannot read property 'getTree' of undefined
[Error - 8:55:47 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:48 am] Request textDocument/foldingRange failed.
  Message: Request textDocument/foldingRange failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:48 am] TypeError: Cannot read property 'getTree' of undefined delayed processing of request
[Error - 8:55:48 am] Request textDocument/codeLens failed.
  Message: Request textDocument/codeLens failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:50 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:50 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 

Your Environment

<!--- Include as many relevant details about the environment you experienced the bug in -->

  • Version used: 2.2.0
  • Editor name and version VSCode 1.57.1
  • Environment name and version node v14.16.1, elm 0.19.1
  • Operating System and version: OSX 10.15.7

closed time in 3 months

abury

issue closedohler55/oj

v3.11.7 causing strange issues with non-rails app

Hi Team,

I'm investigating the details of this, but I was hoping to get a bit of insight if possible to help. After deploying this update to a non rails app, we found that a specific service started failing.

Totally aware that that's no where near enough information, I'm currently digging through multiple layers of obfuscation trying to get to the root cause, but I was hoping to gleen some understanding of this line

oj_default_options.mode = RailsMode;

would this have any impact on non rails apps at all? I assume not given the location and the default options don't seem to have changed after the update, it's just one of the straws I'm clutching at at the moment.

Cheers

closed time in 3 months

abury

issue commentohler55/oj

v3.11.7 causing strange issues with non-rails app

No worries, we'll re-open if/when we have more information.

abury

comment created time in 3 months

issue commentohler55/oj

v3.11.7 causing strange issues with non-rails app

I suspected that was the case, but thanks for clarifying.

abury

comment created time in 3 months

issue commentohler55/oj

v3.11.7 causing strange issues with non-rails app

Glad to hear it's not just us @tonobo, we're continuing to look into it this week, will report back here with any findings. Are you experiencing it on a non rails app as well?

@ohler55 the default mode shouldn't have changed in this release though right? I've checked the options for 3.11.6 and 3.11.7 and couldn't find any differences so feeling like this may be a dead end unfortunately.

Unfortunately the error we were receiving from our cloud provider makes absolutely no sense given the problem domain, suspect there may be an error in their reporting. We'll hopefully hear back from them today/tomorrow which should help us look into this more accurately.

abury

comment created time in 3 months

issue openedohler55/oj

v3.11.7 causing strange issues with Non Rails short lived tasks

Hi Team,

I'm investigating the details of this, but I was hoping to get a bit of insight if possible to help. After deploying this update to a non rails app, we found that a specific service started failing.

Totally aware that that's no where near enough information, I'm currently digging through multiple layers of obfuscation trying to get to the root cause, but I was hoping to gleen some understanding of what this line does:

oj_default_options.mode = RailsMode;

What was the default mode before? Is there something that non rails apps should be doing to ensure the same behavior as before?

Thanks!

created time in 3 months

issue commentelm-tooling/elm-language-client-vscode

Language server unable to start - Unkown system error

@Razzeee looks good:

Hi, thank you for trying out Elm 0.19.1. I hope you like it!
.... etc
Be sure to ask on the Elm slack if you run into trouble! Folks are friendly and
happy to help out. They hang out there because it is fun, so be kind to get the
best results!

abury

comment created time in 3 months

issue commentelm-tooling/elm-language-client-vscode

"MODULE NOT FOUND" error for test-dependencies

I'm having the same issue, would love to know if there is a work around. The project I'm working on has the test file alongside the regular file with the Testsuffix.

robyoder

comment created time in 3 months

issue commentelm-tooling/elm-language-client-vscode

Language server unable to start - Unkown system error

I was able to resolve the issue by manually setting the global path(s) in the extension settings, but would be interested to know what stopped it from picking up the global/local versions manually.

abury

comment created time in 3 months

issue openedelm-tooling/elm-language-client-vscode

Language server unable to start - Unkown system error

Hey all

I've been trying to get the elm language client to work for a few days without much luck. It looks like the language server is unable to start due to an unkown system error.

Would love any insights on how I can get this to work!

I've double and triple checked everything. Elm is installed correctly, node 14 is installed, everything else elm related is working fine.

Current Behavior

Language server fails to start, output below:

[Info  - 8:55:47 am] Loading Elm tree-sitter syntax from ../../../../.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/tree-sitter-elm.wasm
[Info  - 8:55:47 am] Found 2 elm.json files for workspace /Users/<username>/Documents/apps/<project-name>/client
[Info  - 8:55:47 am] Found 1 unique elmWorkspaces for workspace /Users/<username>/Documents/apps/<project-name>/client
[Info  - 8:55:47 am] Starting language server for folder: file:///Users/<username>/Documents/apps/<project-name>/client
[Warn  - 8:55:47 am] {"errno":-8,"code":"Unknown system error -8","syscall":"spawnSync elm","path":"elm","spawnargs":["--version"],"originalMessage":"spawnSync elm Unknown system error -8","shortMessage":"Command failed with Unknown system error -8: elm --version\nspawnSync elm Unknown system error -8","command":"elm --version","stdout":"","stderr":"","failed":true,"timedOut":false,"isCanceled":false,"killed":false}
[Warn  - 8:55:47 am] Could not figure out elm version, this will impact how good the server works. 
 Error: Command failed with Unknown system error -8: elm --version
spawnSync elm Unknown system error -8
    at Object.spawnSync (internal/child_process.js:1067:20)
    at Object.spawnSync (child_process.js:611:24)
    at Function.module.exports.sync (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/node_modules/execa/index.js:167:25)
    at execCmdSync (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/utils/elmUtils.js:45:32)
    at Object.getElmVersion (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/utils/elmUtils.js:90:20)
    at Program.<anonymous> (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/program.js:172:36)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/<username>/.vscode/extensions/elmtooling.elm-ls-vscode-2.2.0/server/out/compiler/program.js:24:58)
[Info  - 8:55:47 am] Reading elm.json from /Users/<username>/Documents/apps/<project-name>/client/elm.json
[Warn  - 8:55:47 am] {"errno":-8,"code":"Unknown system error -8","syscall":"spawnSync elm","path":"elm","spawnargs":["make"],"originalMessage":"spawnSync elm Unknown system error -8","shortMessage":"Command failed with Unknown system error -8: elm make\nspawnSync elm Unknown system error -8","command":"elm make","stdout":"","stderr":"","failed":true,"timedOut":false,"isCanceled":false,"killed":false}
[Error - 8:55:47 am] Error parsing files for /Users/<username>/Documents/apps/<project-name>/client/elm.json:
Error: ENOENT: no such file or directory, open '/Users/<username>/.elm/undefined/packages/NoRedInk/elm-json-decode-pipeline/1.0.0/elm.json'
[Error - 8:55:47 am] Notification handler 'textDocument/didOpen' failed with message: Cannot read property 'getTree' of undefined
[Error - 8:55:47 am] Notification handler 'textDocument/didOpen' failed with message: Cannot read property 'getTree' of undefined
[Error - 8:55:47 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:48 am] Request textDocument/foldingRange failed.
  Message: Request textDocument/foldingRange failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:48 am] TypeError: Cannot read property 'getTree' of undefined delayed processing of request
[Error - 8:55:48 am] Request textDocument/codeLens failed.
  Message: Request textDocument/codeLens failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:50 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 
[Error - 8:55:50 am] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: Cannot read property 'getTree' of undefined
  Code: -32603 

Your Environment

<!--- Include as many relevant details about the environment you experienced the bug in -->

  • Version used: 2.2.0
  • Editor name and version VSCode 1.57.1
  • Environment name and version node v14.16.1, elm 0.19.1
  • Operating System and version: OSX 10.15.7

created time in 3 months