text:
deltalake-python: Missing support for adding new factories and logstores

Description
The Python binding has a hard-coded list of deltalake handlers that are registered:
https://github.com/delta-io/delta-rs/blob/fcd62ab10be9545eab296f03ae0e4324fc4be6cb/python/src/lib.rs#L2035-L2039
To add support for another object store (SAP BTP) we have a Rust crate available, we did not find a way to register these handlers onto the already existing Python binding.
The shared library that comes with deltalake-python does not expose an entry point for adding new object stores.
We ended up in forking delta-rs and adding the registration call as another line in the list above. But we don’t think using a fork to add an additional object store is an appropriate approach.
Have we missed something here? Shouldn’t there be a way to add additional stores in addition to the 5 existing ones?

I'll take a look on how an api should look like to expose and register an external handler

@MartinKolbAtWork it seems that this might be not possible or quite complex, I at least can't find any docs in Pyo3 to achieve this
Do you have the SAP BTP Object store published somewhere?

Hi @ion-elgreco ,
Thanks for looking into this. The integration for SAP BTP is currently used internally at SAP and might be published later, however currently I cannot share the code.
It’s actually using “SAP Data Lake Files” (https://help.sap.com/docs/hana-cloud-data-lake/user-guide-for-data-lake-files/understanding-data-lake-files) as object storge, which is accessible via SAP’s Business Technology Platform (BTP, https://www.sap.com/products/technology-platform.html).
I also investigated a possible solution and it’s especially challenging because the shared library packaged with the Wheel of deltalake-python would need binary compatibility with the shared library that would be packaged with the “add-on”. Ensuring the binary compatibility between these libraries (e.g. related to the used Rust version and the used version of the deltalake crate) would be hard to achieve. An approach that “tunnels” all calls between the two Rust libraries over Python could mitigate the binary compatibility issues but would probably suffer from poor performance.

Hello, I'm from the OpenDAL community, which aims to provide storage access to various services in multiple languages. Perhaps we can build something extensible to allow us to integrate with more storage services easily.
Tools we have now:

opendal rust core.
opendal python binding.
object_store_opendal which exposes object_store support via opendal.

@Xuanwo hey, I wasn't aware that opendal has an objectstore Impl, that's useful!
Any help on this is much appreciated :)

authors: MartinKolbAtWork Xuanwo ion-elgreco

repo: delta-io/delta-rs


text:
code snippets error in official website.

"Table Deletes, Updates, and Merges"
|--Use merge in streaming queries with foreachBatch
val deltaTable = io.delta.tables.DeltaTable.forName("aggregates")
object DeltaTable only has forPath() method.
Can not find this API in below maven dependencies:

io.delta
delta-core_2.11
0.3.0

I noticed some errors here.
Need to change this:
deltaTable.update(                // predicate using Spark SQL functions and implicits
  $"eventType" = "clck"),
  Map("eventType" -> lit("click"));

To this:
deltaTable.update(
  col("eventType") === "clck",
  Map("eventType" -> lit("click"))
)

If there is an open source version of the HTML docs, I'll be happy to make a PR.  Couldn't find them so maybe they're still closed source.

@phoeph  That is a mistake. I will fix it. Thank you.
@MrPowers That is a better example. Thank you.

I am new here.
May I know the next step is to close this issue？

source: gharchive/issue

authors: MrPowers phoeph tdas

repo: delta-io/delta

license_type: permissive

license_source: github-api


text:
Analyze security

Most especially the Rust parameters being transformed into JS parameters as strings needs to be analyzed. All of that serialization needs to be heavily sanitized.

Most especially the Rust parameters being transformed into JS parameters as strings needs to be analyzed. All of that serialization needs to be heavily sanitized.

This has probably been taken care of. We do not serialize the parameters anymore, we do a direct call on the JsValue of the canister function object

repo: demergent-labs/azle

license: MIT


text:
Update tut-integration-ui.md

I changed ‘’ single quotes to '' single quotes in the code to avoid errors.

opened an internal PR

source: gharchive/pull-request

authors: MosheEichler Ripper-S

repo: demisto/content-docs


text:
Tutorial Request: Containers 2: Deploy a Laravel App with Docker Compose

Issue Summary
Need tutorial for:
Containers 2: Deploy a Laravel App with Docker Compose

[ ] Task Description
[ ] Step 1
[ ] Step 2
[ ] Step n
[ ] Conclusion

Hi @denctl
Can you assign this to me? I would like to work on this

Sure!

repo: denctl/devops-handbook


text:
Question: Add custom cheats in addition to the built-in ones.

I installed navi, setup my .zshrc (eval "$(navi widget zsh)") that provides a lot of built-in cheats. I am trying to add a cheat of my own.

I read in the documentation that I can do this export NAVI_PATH="/folder/with/cheats:/another/folder" but that takes away the built-in and leaves only my own cheats.
I also found navi --path "/folder/with/cheats" but that is a one-off at the prompt. I would like to set it up once (add custom path where my cheats are) in my .zshrc

Is there a way to do that?

This should do the trick:
export NAVI_PATH="$(navi info cheats-path):/folder/with/cheats:/another/folder"

navi info cheats-path returns the default path for cheats

Thanks. It works now.

authors: denisidoro vivekragunathan

repo: denisidoro/navi


text:
Translation Request: Indonesian

hello Mr., I am a translator, I want to translate English into Indonesian, Because the majority of Indonesian people do not understand English.. I will be sincere if I am in trust

It's been two years. You didn't send a PR, so I'm closing it.

authors: denysdovhan rabooe

repo: denysdovhan/wtfjs

license: WTFPL


text:
Think through what we can know about agreements

The minutes typically feature a section of agreements formatted like this:

STRONG CITY BALTIMORE, INC. $52,000.00
Account: 5000-506316-6397-460505-601002
The organization will provide a member of their staff
(Baltimore Corps Fellow) to coordinate youth services
related special projects for the YouthWorks Summer program.
The funds will be drawn from the Maryland Department of
Labor, Licensing, and Regulation and State General Funds.
The period of the agreement is September 1, 2016 through
August 31, 2017.

What can we know about each agreement?
What are the columns we expect to include in each row in an agreements table?
What are some initial ideas about how the code can correctly identify each agreement?
Are there reasonable approaches for validating the accuracy of agreements data?

The DataWorks MD team had a good meeting today to combine our explorations of several PDFs. We will be combining some documents we created and work on demonstrating what we have been able to parse soon.

authors: dbbabcock james-trimarco


text:
[Design System] Assets: Update logos and emblems in flagship mobile app

Overview
What was updated in the Design System?
In va-mobile-library, the official VA logos and emblems were updated in version 0.6.0 of the Assets package and Figma library to be consistent with VA.gov. The new files are:

VALogo

VAOnDark.png
VAOnLight.png

serviceEmblems

vic-air-force-coat-of-arms.png
vic-army-symbol.png
vic-cg-emblem.png
vic-navy-emblem.png
vic-space-force-logo-on-dark.png
vic-space-force-logo-on-light.png
vic-space-force-logo.png
vic-usmc-emblem.png

What changes are recommended in the Flagship Mobile App?

In va-mobile-app, the VA logos and emblems in the VAIcon component should be updated as follows. After the files are updated, the vaParentLogo and dodBranch files should be removed from the VAIcon component.

Update: Logo.svg :arrow_right: VAOnDark.png
Update: AirForce.svg :arrow_right: vic-air-force-coat-of-arms.png
Update: Army.svg :arrow_right: vic-army-symbol.png
Update: CoastGuard.svg :arrow_right: vic-cg-emblem.png
Update: MarineCorps.svg :arrow_right: vic-usmc-emblem.png
Update: Navy.svg :arrow_right: vic-navy-emblem.png
New: VAOnLight.png
New: vic-space-force-logo-on-dark.png
New:  vic-space-force-logo-on-light.png
New: vic-space-force-logo.png

In Figma, the VA logos and emblems should be updated in the shipped files. After the files are updated, the Logo component should be removed from the Flagship Library file.

Where are these files used in the Flagship Mobile App?
Currently, the logos and service emblems are used on the home screen, profile screen, and Veteran Status.
Additional resources

How to use the Assets package
Documentation on Logos will be available in the coming weeks
For more information about Service Emblems, reach out to #va-mobile-design-system in Slack.

Acceptance criteria

[ ] Logos and emblems are updated in va-mobile-app with the files in va-mobile-library's Assets package
[ ] Logos and emblems are removed from VAIcon component in va-mobile-app
[ ] Logos and emblems are updated in shipped files in Figma.
[ ] Logos and emblems are removed from the Flagship Library file in Figma.

Closing in favor of the same thing in an Epic ticket: https://app.zenhub.com/workspaces/va-mobile-60f1a34998bc75000f2a489f/issues/gh/department-of-veterans-affairs/va-mobile-app/8784

authors: jessicawoodin kellylein

license: ISC


text:
Allow optional package manifest file name args in config.

Currently the NPM / Yarn plugin uses manifests such as package.json and yarn.lock, however some use cases such as CRA (Create React App) templates store the dependency manifest in an alternative file (templates.json) - an example can be seen here - https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template.json, other than the file name change the structure of the file is the same for the dependencies key. I propose adding an optional argument which can be defined in the YAML config to set an alternative manifest file name to allow for these cases.

Hi @robputt796, did you hear back anything about this issue? I'm having the same issue here.

This one is tricky because it's very similar to https://github.com/dependabot/dependabot-core/issues/2883, but slightly different because it's not just a config allow/ignore issue of already known manifests... it's about discovering manifests hiding in unexpected files. Unfortunately, the names of manifests are baked into our code logic in many, many places.
And it'd be hard to just make those file names configurable w/o losing a lot of simplicity... I'm afraid I just don't see us going this route in the foreseeable future, at least not generically for most ecosystems.
The better thing to do is probably open specific issues for specific file types you'd like to see supported. And then we can discuss on a case-by-case basis whether to expand that ecosystem to support that file.
For example, for Github actions, Maven, and Dockerfiles we've expanded over the past year the types of files that we scan. I could also see us doing something like this possibly down the road for certain python ecosystems and a bit more for dockerfiles.
I'm going to close as "wontfix" in the general sense, but please do file issues for the specific use cases you have in mind.

authors: abruzzi jeffwidman robputt796

repo: dependabot/dependabot-core


text:
Gradle dependencyResolutionManagement block not being processed

Package manager/ecosystem
Gradle
Updated dependency
com.android.tools.build:gradle Although this will effect all non-mavenCentral dependencies.
What you expected to see, versus what you actually saw
Expected: Repositories defined in the dependencyResolutionManagement block within the settings.gradle file are used by dependabot to search for dependency updates.
Actual: Dependabot is ignoring repositories defined in the dependencyResolutionManagement block.
Android studio has recently (as of at least AS 7.0.0 Canary 9) updated their create project templates to use the Gradle centralized-repository-declaration feature to define the repositories to use for the project dependencies. When running the Dependabot GIthub Action against a project using this, new dependencies are not being found.
Images of the diff or a link to the PR, issue or logs
This is a log from a project using the dependencyResolutionManagement in the settings.gradle file to define project repositories.
settings.gradle
---------------
dependencyResolutionManagement {
  repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
  repositories {
    google()
    mavenCentral()
  }
}

Log output
-----------
updater | INFO <job_96630779> Starting update job for otormaigh/playground-android
updater | INFO <job_96630779> Checking if com.android.tools.build:gradle 7.0.0-alpha09 needs updating
  proxy | 2021/03/16 19:32:56 [024] GET https://repo.maven.apache.org:443/maven2/com/android/tools/build/gradle/maven-metadata.xml
  proxy | 2021/03/16 19:32:56 [024] 200 https://repo.maven.apache.org:443/maven2/com/android/tools/build/gradle/maven-metadata.xml
updater | INFO <job_96630779> Latest version is 2.3.0
updater | INFO <job_96630779> No update needed for com.android.tools.build:gradle 7.0.0-alpha09

This is a log from a project using the allprojects in the root/build.gradle file to define project repositories.
build.gradle
------------
allprojects {
  repositories {
    google()
    mavenCentral()
  }
}

Log output
-----------
updater | INFO <job_96493573> Checking if com.android.tools.build:gradle 7.0.0-alpha08 needs updating
  proxy | 2021/03/16 05:12:26 [024] GET https://maven.google.com:443/com/android/tools/build/group-index.xml
  proxy | 2021/03/16 05:12:26 [024] 301 https://maven.google.com:443/com/android/tools/build/group-index.xml
  proxy | 2021/03/16 05:12:27 [026] GET https://dl.google.com:443/dl/android/maven2/com/android/tools/build/group-index.xml
  proxy | 2021/03/16 05:12:27 [026] 200 https://dl.google.com:443/dl/android/maven2/com/android/tools/build/group-index.xml
  proxy | 2021/03/16 05:12:27 [028] GET https://jcenter.bintray.com:443/com/android/tools/build/gradle/maven-metadata.xml
  proxy | 2021/03/16 05:12:27 [028] 200 https://jcenter.bintray.com:443/com/android/tools/build/gradle/maven-metadata.xml
  proxy | 2021/03/16 05:12:27 [030] GET https://dl.bintray.com:443/kotlin/kotlin-eap/com/android/tools/build/gradle/maven-metadata.xml
  proxy | 2021/03/16 05:12:27 [030] 404 https://dl.bintray.com:443/kotlin/kotlin-eap/com/android/tools/build/gradle/maven-metadata.xml
updater | INFO <job_96493573> Latest version is 7.0.0-alpha10

Poke

I just deployed @eikes' PR ; can you verify if this is now fixed please?


text:
APIs for dependabot config

Hi
I doubt this is the right place to ask but I could not find a better place.
There seems to be a dependabot service on GitHub with several options available.
Are there GitHub APIs to retrieve the configuration settings, such as whether alerts and security updates are turned on - https://docs.github.com/en/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies and https://docs.github.com/en/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates
In addition, are you going to merge all these settings into the dependabot.yml config file? It's confusing to have dependabot scattered in different places (a config file and in GitHub settings). I understand they may be different services in the backend, but the marketing around all these being "dependabot" makes it really confusing.

👋 Hey there! Sorry for the glacially slow response... we've been a bit buried.
I empathize with the confusion here.
AFAIK, we don't currently have API's to retrieve the configuration settings.
The UI generally controls settings for the security alerts and the dependabot.yml config file controls settings for version updates. We realize it's confusing, and there are efforts to improve that.

authors: jeffwidman laurentsimon


text:
Revert an erroneously removed method in the PR message builder

See: https://github.com/dependabot/dependabot-core/issues/2542
This method was removed in https://github.com/dependabot/dependabot-core/pull/2539 as part of a class extraction of most of the metadata_finder(dependency) helpers.
Unfortunately, it seems there is no test coverage that hits this code line at time of writing.

Still reading through the class, there are a few other similar _url helper methods that have been ✂  - will update with those and see if I can figure out a quick test case


text:
Bump bundler from 2.3.8 to 2.3.9 and automate it

This bumps the bundler version to the latest release, and adds a quick
'n dirty script to do it for us going forward.
This solution isn't ideal as places where we reference the version might
change, but I think it's an improvement over manually going through the
files. Also, if we happen to reference the same value as the bundler version
to mean something else in the same file, it'll get updated.

Looks good to me!

Thanks for checking in the automation! Looks good to me 🚀
Outside the scope of this change: Do you think we could define the Bundler version in one place as a constant and reference it throughout? I'm thinking we could have Dependabot keep it up-to-date   😄

I think it would be tricky, because we reference it in the Dockerfile, in Ruby source and bash scripts, the only things I can think of are real hacks 🤔

Thanks for checking in the automation! Looks good to me 🚀
Outside the scope of this change: Do you think we could define the Bundler version in one place as a constant and reference it throughout? I'm thinking we could have Dependabot keep it up-to-date   😄

I think it would be tricky, because we reference it in the Dockerfile, in Ruby source and bash scripts, the only things I can think of are real hacks 🤔

Same here. If I think of something I'll ping you 😄

authors: deivid-rodriguez jurre landongrindheim


text:
Uncaught TypeError: Cannot read property 'get' of null

[Enter steps to reproduce below:]

create .build-tools.cson
Accept

Atom Version: 1.12.0-beta5
Electron Version: 1.3.6
System: Ubuntu 16.04.1
Thrown From: build-tools package, v4.5.3
Stack Trace
Uncaught TypeError: Cannot read property 'get' of null
At /home/.../.atom/packages/build-tools/lib/view/command-edit-highlighting-pane.coffee:86

TypeError: Cannot read property 'get' of null
    at HighlightingPane.module.exports.HighlightingPane.get (/home/.../.atom/packages/build-tools/lib/view/command-edit-highlighting-pane.coffee:86:15)
    at CommandPane.module.exports.CommandPane.accept (/home/.../.atom/packages/build-tools/lib/view/command-edit-pane.coffee:185:14)
    at HTMLDivElement.<anonymous> (/home/.../.atom/packages/build-tools/lib/view/command-edit-pane.coffee:1:1)
    at space-pen-div.dispatch (/home/.../.atom/packages/build-tools/node_modules/jquery/dist/jquery.js:4435:9)
    at space-pen-div.elemData.handle (/home/.../.atom/packages/build-tools/node_modules/jquery/dist/jquery.js:4121:28)

Commands
  2x -4:10.1.0 core:move-down (atom-text-editor.editor.mini.is-focused)
     -4:06.7.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -4:06.7.0 build-tools:commands (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -4:05.1.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -4:05.1.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -4:03.9.0 command-palette:toggle (atom-workspace.workspace.scrollbars-visible-always.seti-compact.seti-icons.seti-roboto.seti-animate.theme-one-dark-syntax.theme-seti-ui)
     -4:00.4.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -4:00.4.0 build-tools:toggle (atom-workspace.workspace.scrollbars-visible-always.seti-compact.seti-icons.seti-roboto.seti-animate.theme-one-dark-syntax.theme-seti-ui)
     -3:05.2.0 tree-view:add-file (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -2:55.3.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  3x -2:55.1.0 tree-view:reveal-active-file (atom-workspace.workspace.scrollbars-visible-always.seti-compact.seti-icons.seti-roboto.seti-animate.theme-one-dark-syntax.theme-seti-ui)
     -2:35.3.0 build-tools:add-Custom-Commands (span#add-provider.inline-block.btn.btn-sm.icon.icon-plus)
     -1:00.9.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -0:59.8.0 core:cut (atom-text-editor.editor.mini.is-focused)
     -0:58.8.0 core:paste (atom-text-editor.editor.mini.is-focused)
  2x -0:56.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "atom-autocomplete-php",
      "autocomplete-php",
      "grunt-runner",
      "linter-php",
      "term3",
      "terminal-plus",
      "project-manager",
      "scroll-searcher",
      "hyperclick",
      "hyperclick-php",
      "js-hyperclick"
    ],
    "ignoredNames": [
      ".git",
      ".hg",
      ".svn",
      ".DS_Store",
      "._*",
      "Thumbs.db",
      "node_modules",
      "bower_components"
    ],
    "telemetryConsent": "limited",
    "themes": [
      "seti-ui",
      "one-dark-syntax"
    ]
  }
}

Installed Packages
# User
atom-autocomplete-php, v0.19.4 (inactive)
atom-beautify, v0.29.13 (active)
atom-formatter-jsbeautify, v1.1.2 (active)
atom-html-preview, v0.1.22 (active)
auto-indent-file, v0.2.0 (inactive)
autoclose-html, v0.23.0 (active)
autocomplete-json, v5.1.0 (active)
autocomplete-php, v0.3.7 (inactive)
autocomplete-plus, v2.33.1 (active)
build-tools, v4.5.3 (active)
cssfmt, v1.4.0 (inactive)
editor-stats, v0.17.0 (active)
editorconfig, v1.7.0 (active)
emmet, v2.4.3 (active)
foldername-tabs, v0.2.3 (active)
font-viewer, v0.3.1 (active)
git-blame, v0.4.11 (inactive)
git-control, v0.8.2 (inactive)
git-history, v3.2.0 (inactive)
git-log, v0.4.1 (active)
git-plus, v5.18.0 (active)
git-projects, v1.17.0 (inactive)
git-status, v0.3.4 (inactive)
git-time-machine, v1.5.3 (inactive)
goto-definition, v1.1.19 (active)
grunt-runner, v0.14.0 (inactive)
highlight-selected, v0.11.2 (active)
hyperclick, v0.0.39 (inactive)
hyperclick-php, v0.2.1 (inactive)
js-hyperclick, v1.9.0 (inactive)
jshint, v1.8.6 (active)
language-nginx, v0.6.2 (active)
linter, v1.11.18 (active)
linter-jsonlint, v1.3.0 (active)
linter-php, v1.3.1 (inactive)
minimap, v4.25.6 (active)
minimap-autohide, v0.10.1 (active)
minimap-git-diff, v4.3.1 (active)
navigate, v0.1.16 (active)
package-cop, v0.2.10 (active)
pretty-json, v1.6.1 (active)
project-manager, v3.3.3 (inactive)
project-viewer, v0.3.25 (active)
react, v0.16.1 (active)
rest-client, v1.3.1 (active)
scroll-searcher, v5.0.0 (inactive)
scroll-sync, v0.1.5 (inactive)
seti-icons, v1.3.4 (active)
seti-ui, v1.3.2 (active)
symbols-tree-view, v0.13.2 (active)
sync-settings, v0.7.2 (active)
synced-sidebar, v0.4.3 (active)
term, v0.2.4 (inactive)
term3, v0.22.1 (inactive)
terminal-plus, v0.14.5 (inactive)
todo, v0.6.0 (inactive)
trailing-spaces, v0.3.2 (active)
tree-view-git-branch, v0.1.2 (active)
tree-view-git-status, v1.2.0 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.45.0 (inactive)
base16-tomorrow-dark-theme, v1.3.0 (inactive)
base16-tomorrow-light-theme, v1.3.0 (inactive)
one-dark-ui, v1.6.2 (inactive)
one-light-ui, v1.6.2 (inactive)
one-dark-syntax, v1.5.0 (active)
one-light-syntax, v1.5.0 (inactive)
solarized-dark-syntax, v1.0.5 (inactive)
solarized-light-syntax, v1.0.5 (inactive)
about, v1.7.0 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.13.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.33.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.2 (active)
command-palette, v0.39.0 (active)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.202.0 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.158.8 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.1 (inactive)
settings-view, v0.243.1 (active)
snippets, v1.0.3 (active)
spell-check, v0.68.4 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.2 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.102.2 (active)
timecop, v0.33.2 (active)
tree-view, v0.210.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.46.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

Thanks for the report.
v4.5.4 fixes a few issues I had wih Atom's beta channel, maybe it also fixes your problem.
Unfortunately I was not able to reproduce your bug. You said you created a .build-tools.cson and clicked on the "Accept"-Button of the command editor(?). If the issue persists, it would be nice if you could you tell me what happened between creating the file and clicking that button.

authors: deprint dexif

repo: deprint/build-tools-cpp

license: mit

license_source: bigquery


text:
pair to consolidate netlify seats

acceptance criteria

move to 3 seat pricing model
remove all users except an engineering and an admin seat (no person needed currently for third seat)

Yes. I am all for this. I don't have access to remove the seats :(


text:
🛑 Derailed Home is down

In 5e775b6, Derailed Home (https://derailed.one) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed Home is back up in 0b9e060.

repo: derailed-org/derailed-oss-status


text:
🛑 Derailed Home is down

In dbd7787, Derailed Home (https://derailed.one) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed Home is back up in 7230ebd.


text:
Skip language pages

Hello
Duo started adding characters \ alphabets learning on the web https://www.duolingo.com/characters
So far the following languages have them
https://www.duolingo.com/alphabets/ru/cyrillic
https://www.duolingo.com/alphabets/ja/hiragana
https://www.duolingo.com/alphabets/ja/katakana
https://www.duolingo.com/alphabets/uk/ukrainian
please make your extension work @ the https://www.duolingo.com/alphabets/
Thanks

Thanks for letting me know. Version 0.28 of the extension is out for review.

authors: alexseyk derat

repo: derat/duoleavemealone


text:
[BUG] Can't run a single component without running everything

In order to initialise the project what I'd like to do is something like
exo workspace init
exo start db
npx prisma migrate dev
exo stop db

In practice this doesn't work because exo apply is never called. But if I call exo apply that then runs every service, some of which misbehave if I haven't yet performed the initialisation.

Related: #324

authors: BenElgar brandonbloom

repo: deref/exo


text:
Installing delve on Windows gives an error

Please answer the following before submitting your issue:
C:\GoPath>go get github.com/derekparker/delve/cmd/dlv
github.com/derekparker/delve/proc
src\github.com\derekparker\delve\proc\disasm.go:9: undefined: ArchInst
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)?
What version of Go are you using? (go version)? go1.7.1 windows/386
What operating system and processor architecture are you using? Windows 10 x64
What did you do? Tried to install delve
What did you expect to see? Install successful
What did you see instead? Seems like an compilation error in one of the source files.  See above.

Delve only works with 64bit not 32bit.

FYI
@tinaschrepfer given that you are running 64bit operating system (you said it is Windows 10 x64), you should be able to install Go windows/amd64 (64bit version of Go). This will allow you to run Delve debugger.
Alex

Thanks!  That fixed part of my issue.  When I debug on VSCode using the latest version of delve I'm getting the following error:
can't load package: package internal: no buildable Go source files in C:\GoWork\src\internal
Seems like others are having the same issue: http://stackoverflow.com/questions/39458526/how-to-fix-delve-cant-load-package-package-internal-error
I worked around it by copying over an older version of delve.  Is this a known issue?
Thanks!
Tina

I'm getting the following error:

If you run go env command what does it output?
Also, can you build some simple go programs from command line? Can you try and debug one such program from command line. Tell us what you did - what your program looks like, what output you see.
Thank you.
Alex

Here's the go env output
C:\GoWork\bin>go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\GoWork
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
If i debug from command line using the latest delve, I get the following:
C:\GoWork\scratch>..\bin\dlv.exe debug
can't load package: package internal: no buildable Go source files in C:\Go\src\internal
exit status 1
But if I switch to older version of delve, it seems to work okay:
C:\GoWork\scratch>..\bin\dlv.exe debug
Type 'help' for list of commands.
(dlv)
My source code is pretty simple, just some printlns and a sort:
package main
import "fmt"
func main() {
strs := []string{"c", "a", "b"}
fmt.Println("testing")
fmt.Println("sorted strings: ", strs)
fmt.Println("test")
i := 1
for i <= 3 {
	fmt.Println("current i = ", i)
	i = i + 1
}

}

Yes it is broken on the tip.
2fad5abe74b311c853838ae4e00d83b9232f1a8a is the first bad commit
commit 2fad5abe74b311c853838ae4e00d83b9232f1a8a
Author: Koichi Shiraishi k@zchee.io
Date:   Tue Sep 13 03:13:21 2016 +0900
cmd: Support space separate flags for build-flags (#619)

Signed-off-by: Koichi Shiraishi <zchee.io@gmail.com>

Alex

PR #639 should fix this.

PR #639 should fix this.

Sure. I was bisecting as you have sent the PR. :-)
Alex

Alright, thanks anyway :)

I'm not seeing the fix reflected when I run "go get github.com/derekparker/delve/cmd/dlv".  Is there a different command to use to get the fix?

I'm not seeing the fix reflected when I run "go get github.com/derekparker/delve/cmd/dlv".

The fix is PR https://github.com/derekparker/delve/pull/639. The PR is still opened. It is not part of github.com/derekparker/delve repo. You can apply the PR to your repo localy to try it (google for instructions on how to apply a github PR). Or you can wait until PR is merged or rejected.

Is there a different command to use to get the fix?

Once change is in github.com/derekparker/delve/cmd/dlv, you could use "-u" flag
go get -u github.com/derekparker/delve/cmd/dlv

to update your local master branch to whatever github.com/derekparker/delve will be at the time. See go help get for correspondent help.
Alternatively you can use whatever git commands you know to update you local source.
Alex

google for instructions on how to apply a github PR

Download the patch then use git apply, this is one way to do it, but then your checkout will be out of sync with the remote and go get -u may stop working.

Who can merge it?

Fixed by 5d78c04

authors: aarzilli alexbrainman joegrasse tinaschrepfer wildfire810

repo: derekparker/delve


text:
nextStation variant not very reliable

Hey,
while implementing the new nextStation feature in my MagicMirror module, I noticed that the reliability of this method seems to be not so good. I assume this has to do with the VBB side of the service.
I get a Bad Gateway 504 error very often. Did you experience the same issues during your tests?
It seems to be more often on bus departures than on suburban lines though...
Greetings! And thank you very much for implementing this! ;)

I will dig into the logs to find requests that resulted in a 504. It would be very useful if you gave me some example on where this fails often.

You may also want to test vbb-departures-in-direction in isolation.

As a test, I picked 900000024207 (Kantstr./Leibnizstr.), where M49 & X34 cross the 101 line. I fetched departures in direction of 900000024252 (Schlüterstr.):
const depsInDirection = require('vbb-departures-in-direction')

const kantstrLeibnitzstr = '900000024207'
const schlueterstr = '900000024252'

depsInDirection(kantstrLeibnitzstr, schlueterstr, {when})
.then(console.log)
.catch(console.error)

It seems to work fine:
[
	{
		ref: '1|18729|10|86|19082017',
		station: {
			type: 'station',
			name: 'Kantstr./Leibnizstr.',
			coordinates: {…},
			id: '900000024207',
			products: {…}
		},
		when: '2017-08-19T16:03:00+02:00',
		direction: 'S+U Zoologischer Garten',
		line: {
			type: 'line',
			name: 'M49',
			class: 8,
			productCode: 3,
			productName: 'MB',
			product: 'bus',
			mode: 'bus',
			id: 'm49',
			symbol: 'M',
			nr: 49,
			metro: true,
			express: false,
			night: false
		},
		remarks: [ null ],
		trip: 18729,
		delay: 480
	},
	{
		ref: '1|22024|13|86|19082017',
		station: {
			type: 'station',
			name: 'Kantstr./Leibnizstr.',
			coordinates: {…},
			id: '900000024207',
			products: {…}
		},
		when: '2017-08-19T15:59:00+02:00',
		direction: 'S+U Zoologischer Garten',
		line: {
			type: 'line',
			name: 'X34',
			class: 8,
			productCode: 3,
			productName: 'B',
			product: 'bus',
			mode: 'bus',
			id: 'x34',
			symbol: 'X',
			nr: 34,
			metro: false,
			express: true,
			night: false
		},
		remarks: [ null ],
		trip: 22024,
		delay: 540
	},
	{
		ref: '1|18699|9|86|19082017',
		station: {
			type: 'station',
			name: 'Kantstr./Leibnizstr.',
			coordinates: {…},
			id: '900000024207',
			products: {…}
		},
		when: '2017-08-19T16:07:00+02:00',
		direction: 'S+U Zoologischer Garten',
		line: {
			type: 'line',
			name: 'M49',
			class: 8,
			productCode: 3,
			productName: 'MB',
			product: 'bus',
			mode: 'bus',
			id: 'm49',
			symbol: 'M',
			nr: 49,
			metro: true,
			express: false,
			night: false
		},
		remarks: [ null ],
		trip: 18699,
		delay: 1320
	}
]

The vbb.transport.rest equivalent to work as well:
curl -v 'https://vbb.transport.rest/stations/900000024207/departures?nextStation=900000024252'

Okay, the tests I did where with Bus stations Lückstr./Weitlingstr. and Münsterlandplatz (as direction)  with IDs 900000160019 and 900000160733 respectively. The request takes very long and the following error gets returned:

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx/1.10.3 (Ubuntu)

here's my cURL command: curl 'https://vbb.transport.rest/stations/900000160019/departures?when=now&nextStation=900000160733'
I tried other stations, they seem to work better.
I also just tried Alexanderplatz and Jannowitzbrücke (as direction) and get the following error:
{"error":true,"msg":"HCI Service: request failed"}

But this means, the error is on the VBB side, right?
Here's my cURL: curl 'https://vbb.transport.rest/stations/900000100004/departures?nextStation=900000100005&when=now'
And here's the output with -v:
*   Trying 51.15.70.111...
* TCP_NODELAY set
* Connected to vbb.transport.rest (51.15.70.111) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate: vbb.transport.rest
* Server certificate: Let's Encrypt Authority X3
* Server certificate: DST Root CA X3
> GET /stations/900000100004/departures?nextStation=900000100005&when=now HTTP/1.1
> Host: vbb.transport.rest
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 502 Bad Gateway
< Server: nginx/1.10.3 (Ubuntu)
< Date: Mon, 21 Aug 2017 20:33:24 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 50
< Connection: keep-alive
< X-Powered-By: vbb-rest https://github.com/derhuerst/vbb-rest
< Surrogate-Control: no-store
< Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate
< Pragma: no-cache
< Expires: 0
< ETag: W/"32-g1yCtKWat77YFBaGSPj0SeKUzrE"
< Vary: Accept-Encoding
<
* Connection #0 to host vbb.transport.rest left intact
{"error":true,"msg":"HCI Service: request failed"}%

When I let the code run on the mirror, it sometimes works ans sometimes not. But it seems to be very erratic...
I will reimplement the function with your vbb-departures-in-direction module and give you feedback when I tested it! It could take some days though, because time is rare at the moment...

[…] with Bus stations Lückstr./Weitlingstr. and Münsterlandplatz (as direction) with IDs 900000160019 and 900000160733 respectively. The request takes very long and the following error gets returned: […]

That is my fault. The vbb-departures-in-direction lookup underneath seems to take very long at this specific location. My nginx set up to send a 504 Gateway Time-out after 8 seconds. I increased it to 20 seconds now, thanks.

I also just tried Alexanderplatz and Jannowitzbrücke (as direction) and get the following error:
{"error":true,"msg":"HCI Service: request failed"}

But this means, the error is on the VBB side, right?

Correct, VBB side. In fact their service is unavailable quite often.

I will reimplement the function with your vbb-departures-in-direction module and give you feedback when I tested it!

Note that this is what I already do in vbb.transport.rest: I you pass the nextStation parameter, it will use vbb-departures-in-direction, otherwise it won't.
You can query the VBB HAFAS endpoint on your own (using vbb-departures-in-direction and/or vbb-hafas), but that won't change anything about their uptime.

Okay, so the issue has nothing to do with your API.
As I'm querying the service with the nextStation parameter, everything is right I think. So there's no need to use vbb-departures-in-direction. I didn't do any more tests about the timeout issue, but I assume it should work now...
Should we close this issue now?

As I'm querying the service with the nextStation parameter, everything is right I think. So there's no need to use vbb-departures-in-direction.

Not really.
yup, let's close. reopen if you encounter more issues.

repo: derhuerst/vbb-hafas

license: isc


text:
How to install the go-mockgen binary ?

Hello,
I'm using go-mockgen in one of my projects, where I have it run in a bash script.
I see in the README that the installation instructions are:
go get -u github.com/derision-test/go-mockgen/...

but as that's the old way of installing tools, go complains, and asks me to use go install instead.
So my bash script includes:
go install github.com/derision-test/go-mockgen/...
go generate ./...

When I run by bash script though, I get this output:
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/cmd/go-mockgen/args.go:11:2: missing go.sum entry for module providing package github.com/alecthomas/kingpin (imported by github.com/derision-test/go-mockgen/cmd/go-mockgen);
 to add:
        go get github.com/derision-test/go-mockgen/cmd/go-mockgen@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/internal/mockgen/generation/generate.go:13:2: missing go.sum entry for module providing package github.com/dave/jennifer/jen (imported by github.com/derision-test/go-mockgen/
internal/mockgen/generation); to add:
        go get github.com/derision-test/go-mockgen/internal/mockgen/generation@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/internal/mockgen/generation/generate_structs.go:9:2: missing go.sum entry for module providing package github.com/dustin/go-humanize (imported by github.com/derision-test/go-
mockgen/internal/mockgen/generation); to add:
        go get github.com/derision-test/go-mockgen/internal/mockgen/generation@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/internal/mockgen/generation/generate_comment.go:8:2: missing go.sum entry for module providing package github.com/mitchellh/go-wordwrap (imported by github.com/derision-test/
go-mockgen/internal/mockgen/generation); to add:
        go get github.com/derision-test/go-mockgen/internal/mockgen/generation@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/internal/mockgen/types/extract.go:13:2: missing go.sum entry for module providing package golang.org/x/tools/go/packages (imported by github.com/derision-test/go-mockgen/inte
rnal/mockgen/types); to add:
        go get github.com/derision-test/go-mockgen/internal/mockgen/types@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/testutil/gomega/anything_matcher.go:6:2: missing go.sum entry for module providing package github.com/onsi/gomega/format (imported by github.com/derision-test/go-mockgen/test
util/gomega); to add:
        go get github.com/derision-test/go-mockgen/testutil/gomega@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/testutil/gomega/called_with_matcher.go:8:2: missing go.sum entry for module providing package github.com/onsi/gomega/matchers (imported by github.com/derision-test/go-mockgen
/testutil/gomega); to add:
        go get github.com/derision-test/go-mockgen/testutil/gomega@v1.2.0
../../../../go/pkg/mod/github.com/derision-test/go-mockgen@v1.2.0/testutil/gomega/anything_matcher.go:7:2: missing go.sum entry for module providing package github.com/onsi/gomega/types (imported by github.com/derision-test/go-mockgen/testu
til/gomega); to add:
        go get github.com/derision-test/go-mockgen/testutil/gomega@v1.2.0

These missing entries are not actually missing entries, as I don't want them in my go project. go-mockgen is a tool I want to run on the project, but I don't necessarily want to add it as dependencies for my project.
Moreover, if I do run all the go get commands that are listed, whenever I will run go mod tidy, they will be removed, as they are not actually dependencies in my code.
Thanks

I believe that if you do a go install with an explicit version tag that it won't add it to your containing project. This StackOverflow solution indicates that could be a solution for you.
Could you try it and let me know if that works? I can update the installation instructions if you'd find them more clear.

I had the same issue and I fixed it by installing the tool via:
go install github.com/derision-test/go-mockgen/...@v1.3.1

authors: efritz nathani-axis w32blaster

repo: derision-test/go-mockgen


text:
Food recipe widget

This PR adds a widget that shows random food recipes and can open relevant YouTube cooking videos on tap
Repo: https://github.com/shfrmn/scriptable-recipe
Source code: https://github.com/shfrmn/scriptable-recipe/blob/main/food-recipe-widget.js

Good addition, thank you!

authors: dersvenhesse shfrmn

repo: dersvenhesse/awesome-scriptable


text:
Error while installing a bundle

Instructions were taken from here:
https://designfirst.io/systemruntime/documentation/docs/en/bundle-your-system.html
After the system was defined and saved into a file, I try to load it again using the command:
runtime.install('mysystem.json');
Error:
TypeError: $helper.getRuntime(...).system(...).id is not a function
... \node_modules\system-runtime\src\workflow.js:406
.id()
at action (... \node_modules\system-runtime\src\workflow.js:406:16)

Hi,
you get this error because:

the name of your json file is not good or
your json file is not in the same directory of your script.

I have updated the library so that you will now have a better error message. Example:
runtime: error when calling the action 'install' on component 'runtime' (class '_Runtime'): Cannot find module '/Users/aaa/project/invalid.json'

Thanks for a quick response! The new version gives a better error message indeed:
runtime: error when calling the action 'install' on component 'runtime' (class '_Runtime'): Cannot find module 'undefined/'
It looks like "undefined/" is added somewhere on the way to the file path.
I found out that combination with fs.readFile may bring you to the positive result:
fs.readFile(, 'utf8', (err, data) => {
runtime.install(data);
...

I made some search about your issue and it appears that on Windows 10 the command process.env.PWD could returns undefined. Are you on Windows 10 ?
I made a fix about this issue and I will deploy a new release with that fix very soon.

The library has been updated with the fix.

I am on Windows 10. After the library update the model can be loaded successfully.
Thanks for the quick help!

You are welcome. And thank you for having found this issue.
I will close this bug as it seems that your problem is fixed now.

Hi again, I am wondering, whether it would be possible to provide an absolute path instead of relative by calling runtime.install?

Yes, it is possible, I will check how to do that (i.e. if I use the same API or add a new one).

authors: aprelle ecarriou

repo: design-first/system-runtime


text:
add zenkit logo to brands

https://github.com/home-assistant/brands

See https://github.com/home-assistant/brands/pull/5865

Fixed by merge

repo: despokd/homeassistant-zenkit


text:
Node 8.x support

As per #48 runtime support under node 10.1 was dropped. Node 8.x is still widely used as a runtime, especially in servers. I suggest that it should be supported a bit longer.
Also note that the fs Promises API is still experimental in node 10.
These changes would be needed for node 8 support:

fs.promises was unavailable prior to node 10.

Use a library like normalize/mz for async fs operations, or use Util.promisify like before.

Don't use the global URL object. It was unavailable prior to node 10.

require('url').URL references the same object in earlier versions.

As a more long-term solution targeting earlier versions of node with Babel during the build step could be a solution, which still means newer features can be used in the code without having to worry about compatibility.

The initial approach with this fork was to move on and use new Node features. We have older version published on NPM if you want to stick with an older version of Node. Version 6.0 released today is written in Typescript, but targeting Node 10.

Node 10 finally became available in AWS Lambda as of a few days ago, which was my pain point. So we will be able to move on for now.
With that said, I don't see the point of not targeting Node 8 when it's still supported and widely adopted. You guys should try to support current versions of node, like many other npm libraries.
PS. The 6.0.0 release is completely broken

@c-bandy Yes, 6.0 got NPM publishing error, will publish 6.1 with localizations support today.

@c-bandy version 6.1 fixed NPM publishing issue

authors: c-bandy tinovyatkin

repo: destinationstransfers/passkit


text:
change FACTORY_POSTFIX from __factory to ContractFactory for compatibility with eslint camelcase rules

https://github.com/dethcrypto/TypeChain/blob/95517e999c2cf29a1e9a5e894ca5374ce7eae04b/packages/target-ethers-v5/src/common.ts#L1
is there technical reason it uses __factory as the postfix? if it is arbitrary then using ContractFactory as the postfix would fix eslint camelcase errors
since it is a postfix it should not conflict (although a bit ugly) with a contract name. it will be clear that this is the factory type not the instance type.
what do you think?

agree

It was mostly done like this because contracts that are factories do exist and the names would clash otherwise. Example contract named: UniswapPoolFactory. I think it's better to have this weird postfix to make it obvious that it's a typechain thing.

bummer. alright man

In case anyone wants to have something that looks nice, I use this utility functions to make the names better:
import {
  copySync,
  readFileSync,
  renameSync,
  writeFileSync
} from 'fs-extra'
import { glob } from 'glob'

export const renameFilesAndExports = () => {
  glob
    .sync('./types/ethers-contracts/**/*.ts', { absolute: true })
    .forEach(file => {
      const _content = readFileSync(file, 'utf-8')

      writeFileSync(
        file,
        _content.replace(/__factory/gm, 'Factory')
      )

      file.endsWith('__factory.ts') &&
        renameSync(file, file.replace('__factory', 'Factory'))
    })
}

export const makeExports = () => {
  renameFilesAndExports()
  exportArtifacts()

  const filesToReplaceContent = [
    './types/ethers-contracts/index.ts',
    './types/ethers-contracts/factories/index.ts'
  ]

  for (const file of filesToReplaceContent) {
    const content = readFileSync(file, 'utf8')

    writeFileSync(
      file,
      content.replace(/__factory/gm, 'Factory')
    )
  }
}

export const copyDeclarations = async () => {
  copySync(
    './types/ethers-contracts/',
    './dist/types/ethers-contracts/',
    {
      overwrite: true,
      filter: f => f.includes('.d.ts')
    }
  )
}

export const exportArtifacts = async () => {
  const artifacts = glob.sync(
    './smart-contracts/artifacts/*.json',
    {
      cwd: './src'
    }
  )

  const names = artifacts.map(file =>
    file
      .replace('./smart-contracts/artifacts/', '')
      .replace('.json', '')
  )

  const content = `import ADDRESSES from './smart-contracts/addresses.json'

${artifacts
  .map(
    (file, i) =>
      'import ' + names[i] + ' from ' + "'" + file + "'"
  )
  .join('\n')}

const ARTIFACTS = {
  ${names.join(',\n  ')}
}

export { ARTIFACTS, ADDRESSES }

  `

  writeFileSync('./src/index.ts', content)
}

export default {
  copyDeclarations,
  makeExports,
  exportArtifacts
}

repo: dethcrypto/TypeChain


text:
🛑 OKTicket is down

In 73769b0, OKTicket (https://www.okticket.es) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OKTicket is back up in e7d27da.

repo: dev-okticket/statusT


text:
pin rake version

pin rake dependency, since newer versions require rack which requires Ruby version >= 2.2.2.

great, thank you @chris-rock

repo: dev-sec/tests-ssh-hardening


text:
Remote host dev container: Command failed: docker build -f /tmp/devcontainercli

I'm on a macos host. Running vscode in remote host. Within a vm, then running opening the dev container within the remote host.
Happy to help in anyway, just let me know
You can create an identical virtual machine using multipass and the following cloud init
users:
  - default
  - name: vmuser
    sudo: ALL=(ALL) NOPASSWD:ALL
    ssh_authorized_keys:
    - ssh-ed25519 -----
groups:
- docker
snap:
  commands:
  - [install, docker]
runcmd:
- adduser vmuser docker
- reboot

[2023-08-26T07:01:37.740Z] Dev Containers 0.304.0 in VS Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794).
[2023-08-26T07:01:37.740Z] Start: Resolving Remote
[2023-08-26T07:01:37.749Z] Start: Run: ssh 192.168.64.134 /bin/sh
[2023-08-26T07:01:37.754Z] Start: Run in host: id -un
[2023-08-26T07:01:38.034Z] vmuser
[2023-08-26T07:01:38.034Z]
[2023-08-26T07:01:38.034Z] Stop (280 ms): Run in host: id -un
[2023-08-26T07:01:38.034Z] Start: Run in host: getent passwd vmuser
[2023-08-26T07:01:38.038Z] Stop (4 ms): Run in host: getent passwd vmuser
[2023-08-26T07:01:38.039Z] Start: Run in host: echo ~
[2023-08-26T07:01:38.042Z] /home/vmuser
[2023-08-26T07:01:38.042Z]
[2023-08-26T07:01:38.042Z] Stop (3 ms): Run in host: echo ~
[2023-08-26T07:01:38.042Z] Start: Run in host: test -x '/home/vmuser/.vscode-remote-containers/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node'
[2023-08-26T07:01:38.047Z]
[2023-08-26T07:01:38.047Z]
[2023-08-26T07:01:38.048Z] Exit code 1
[2023-08-26T07:01:38.048Z] Stop (6 ms): Run in host: test -x '/home/vmuser/.vscode-remote-containers/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node'
[2023-08-26T07:01:38.048Z] Start: Run in host: test -x '/home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node'
[2023-08-26T07:01:38.051Z]
[2023-08-26T07:01:38.051Z]
[2023-08-26T07:01:38.051Z] Stop (3 ms): Run in host: test -x '/home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node'
[2023-08-26T07:01:38.052Z] Start: Run in host: test -f '/home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node_modules/node-pty/package.json'
[2023-08-26T07:01:38.055Z]
[2023-08-26T07:01:38.055Z]
[2023-08-26T07:01:38.055Z] Stop (3 ms): Run in host: test -f '/home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node_modules/node-pty/package.json'
[2023-08-26T07:01:38.055Z] Start: Run in host: test -f '/home/vmuser/.vscode-remote-containers/dist/vscode-remote-containers-server-0.304.0.js'
[2023-08-26T07:01:38.058Z]
[2023-08-26T07:01:38.059Z]
[2023-08-26T07:01:38.059Z] Stop (4 ms): Run in host: test -f '/home/vmuser/.vscode-remote-containers/dist/vscode-remote-containers-server-0.304.0.js'
[2023-08-26T07:01:38.063Z] userEnvProbe: loginInteractiveShell (default)
[2023-08-26T07:01:38.063Z] userEnvProbe: not found in cache
[2023-08-26T07:01:38.063Z] userEnvProbe shell: /bin/sh
[2023-08-26T07:01:38.252Z] userEnvProbe PATHs:
Probe:     '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'
Container: None
[2023-08-26T07:01:38.257Z] Setting up container for folder or workspace: /home/vmuser/testing
[2023-08-26T07:01:38.257Z] Host: ssh://192.168.64.134
[2023-08-26T07:01:38.298Z] Start: Check Docker is running
[2023-08-26T07:01:38.298Z] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[2023-08-26T07:01:38.513Z] Stop (215 ms): Run in Host: docker version --format {{.Server.APIVersion}}
[2023-08-26T07:01:38.513Z] Server API version: 1.41
[2023-08-26T07:01:38.514Z] Stop (216 ms): Check Docker is running
[2023-08-26T07:01:38.514Z] Start: Run in Host: docker volume ls -q
[2023-08-26T07:01:38.679Z] Stop (165 ms): Run in Host: docker volume ls -q
[2023-08-26T07:01:38.680Z] Start: Run in Host: docker ps -q -a --filter label=vsch.local.folder=/home/vmuser/testing --filter label=vsch.quality=stable
[2023-08-26T07:01:38.950Z] Stop (270 ms): Run in Host: docker ps -q -a --filter label=vsch.local.folder=/home/vmuser/testing --filter label=vsch.quality=stable
[2023-08-26T07:01:38.950Z] Start: Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:39.073Z] Stop (123 ms): Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:39.073Z] Start: Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing
[2023-08-26T07:01:39.174Z] Stop (101 ms): Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing
[2023-08-26T07:01:39.174Z] Start: Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing
[2023-08-26T07:01:39.264Z] Stop (90 ms): Run in Host: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing
[2023-08-26T07:01:39.273Z] Start: Run in Host: /home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/vmuser/testing --id-label devcontainer.local_folder=/home/vmuser/testing --id-label devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/vmuser/testing/.devcontainer/devcontainer.json --mount-workspace-git-root true
[2023-08-26T07:01:39.557Z] @devcontainers/cli 0.50.0. Node.js v16.17.1. linux 5.15.0-79-generic x64.
[2023-08-26T07:01:39.557Z] Start: Run: git rev-parse --show-cdup
[2023-08-26T07:01:39.567Z] Stop (10 ms): Run: git rev-parse --show-cdup
[2023-08-26T07:01:39.569Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:39.699Z] Stop (130 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:39.664Z] Stop (391 ms): Run in Host: /home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/vmuser/testing --id-label devcontainer.local_folder=/home/vmuser/testing --id-label devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/vmuser/testing/.devcontainer/devcontainer.json --mount-workspace-git-root true
[2023-08-26T07:01:39.673Z] Start: Run in Host: /home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-af369e26-aa8b-4551-ba2b-ef120643e0c31693033296421 --workspace-folder /home/vmuser/testing --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/vmuser/testing --id-label devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/vmuser/testing/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-08-26T07:01:39.940Z] @devcontainers/cli 0.50.0. Node.js v16.17.1. linux 5.15.0-79-generic x64.
[2023-08-26T07:01:39.940Z] Start: Run: docker buildx version
[2023-08-26T07:01:40.256Z] Stop (316 ms): Run: docker buildx version
[2023-08-26T07:01:40.257Z] github.com/docker/buildx v0.10.4 c513d34049e499c53468deac6c4267ee72948f02
[2023-08-26T07:01:40.257Z]
[2023-08-26T07:01:40.258Z] Start: Resolving Remote
[2023-08-26T07:01:40.266Z] Start: Run: git rev-parse --show-cdup
[2023-08-26T07:01:40.272Z] Stop (6 ms): Run: git rev-parse --show-cdup
[2023-08-26T07:01:40.278Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:40.477Z] Stop (199 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/vmuser/testing --filter label=devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json
[2023-08-26T07:01:40.480Z] Start: Run: docker inspect --type image mcr.microsoft.com/devcontainers/go:1-1.21-bullseye
[2023-08-26T07:01:40.635Z] Stop (155 ms): Run: docker inspect --type image mcr.microsoft.com/devcontainers/go:1-1.21-bullseye
[2023-08-26T07:01:41.724Z] local container features stored at: /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/node_modules/vscode-dev-containers/container-features
[2023-08-26T07:01:41.727Z] Start: Run: tar --no-same-owner -x -f -
[2023-08-26T07:01:41.749Z] Stop (22 ms): Run: tar --no-same-owner -x -f -
[2023-08-26T07:01:41.760Z] Start: Run: docker build -f /tmp/devcontainercli-vmuser/updateUID.Dockerfile-0.50.0 -t vsc-testing-a657200756e273ad683c5fc254bcf3bcfc757c10e60fac109ba77ed794ef6226-uid --build-arg BASE_IMAGE=mcr.microsoft.com/devcontainers/go:1-1.21-bullseye --build-arg REMOTE_USER=vscode --build-arg NEW_UID=1000 --build-arg NEW_GID=1001 --build-arg IMAGE_USER=root /tmp/devcontainercli-vmuser/empty-folder
[2023-08-26T07:01:41.863Z] unable to prepare context: path "/tmp/devcontainercli-vmuser/empty-folder" not found
[2023-08-26T07:01:41.868Z] Stop (108 ms): Run: docker build -f /tmp/devcontainercli-vmuser/updateUID.Dockerfile-0.50.0 -t vsc-testing-a657200756e273ad683c5fc254bcf3bcfc757c10e60fac109ba77ed794ef6226-uid --build-arg BASE_IMAGE=mcr.microsoft.com/devcontainers/go:1-1.21-bullseye --build-arg REMOTE_USER=vscode --build-arg NEW_UID=1000 --build-arg NEW_GID=1001 --build-arg IMAGE_USER=root /tmp/devcontainercli-vmuser/empty-folder
[2023-08-26T07:01:41.818Z] Error: Command failed: docker build -f /tmp/devcontainercli-vmuser/updateUID.Dockerfile-0.50.0 -t vsc-testing-a657200756e273ad683c5fc254bcf3bcfc757c10e60fac109ba77ed794ef6226-uid --build-arg BASE_IMAGE=mcr.microsoft.com/devcontainers/go:1-1.21-bullseye --build-arg REMOTE_USER=vscode --build-arg NEW_UID=1000 --build-arg NEW_GID=1001 --build-arg IMAGE_USER=root /tmp/devcontainercli-vmuser/empty-folder
[2023-08-26T07:01:41.819Z]     at oAA (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:462:1066)
[2023-08-26T07:01:41.819Z]     at mK (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:462:1002)
[2023-08-26T07:01:41.819Z]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-08-26T07:01:41.819Z]     at async mAA (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:479:3660)
[2023-08-26T07:01:41.819Z]     at async LC (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:479:4775)
[2023-08-26T07:01:41.819Z]     at async jeA (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:611:12219)
[2023-08-26T07:01:41.819Z]     at async _eA (/home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js:611:11960)
[2023-08-26T07:01:41.825Z] Stop (2152 ms): Run in Host: /home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-af369e26-aa8b-4551-ba2b-ef120643e0c31693033296421 --workspace-folder /home/vmuser/testing --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/vmuser/testing --id-label devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/vmuser/testing/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-08-26T07:01:41.826Z] Exit code 1
[2023-08-26T07:01:41.830Z] Command failed: /home/vmuser/.vscode-server/bin/6c3e3dba23e8fadc360aed75ce363ba185c49794/node /home/vmuser/.vscode-remote-containers/dist/dev-containers-cli-0.304.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-af369e26-aa8b-4551-ba2b-ef120643e0c31693033296421 --workspace-folder /home/vmuser/testing --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/vmuser/testing --id-label devcontainer.config_file=/home/vmuser/testing/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/vmuser/testing/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-08-26T07:01:41.830Z] Exit code 1

total 52
drwxrwxrwt 13 root   root   4096 Aug 26 08:02 .
drwxr-xr-x 19 root   root   4096 Aug 26 07:56 ..
drwxrwxrwt  2 root   root   4096 Aug 26 07:56 .ICE-unix
drwxrwxrwt  2 root   root   4096 Aug 26 07:56 .Test-unix
drwxrwxrwt  2 root   root   4096 Aug 26 07:56 .X11-unix
drwxrwxrwt  2 root   root   4096 Aug 26 07:56 .XIM-unix
drwxrwxrwt  2 root   root   4096 Aug 26 07:56 .font-unix
drwxrwxr-x  4 vmuser vmuser 4096 Aug 26 08:01 devcontainercli-vmuser
drwx------  4 root   root   4096 Aug 26 07:56 snap-private-tmp
drwx------  3 root   root   4096 Aug 26 07:56 systemd-private-f462e0174c054d0abc5eb21c4153f0c5-systemd-logind.service-AXA7Ip
drwx------  3 root   root   4096 Aug 26 07:56 systemd-private-f462e0174c054d0abc5eb21c4153f0c5-systemd-resolved.service-nZK1Af
drwx------  3 root   root   4096 Aug 26 07:56 systemd-private-f462e0174c054d0abc5eb21c4153f0c5-systemd-timesyncd.service-MBLiC5
drwxrwxr-x  2 vmuser vmuser 4096 Aug 26 08:01 vscode-typescript1000
$ ls -la /tmp/devcontainercli-vmuser
total 24
drwxrwxr-x  4 vmuser vmuser 4096 Aug 26 08:01 .
drwxrwxrwt 13 root   root   4096 Aug 26 08:02 ..
drwxrwxr-x  8 vmuser vmuser 4096 Aug 26 08:01 container-features
-rw-rw-r--  1 vmuser vmuser 2065 Aug 26 07:59 control-manifest.json
drwxrwxr-x  2 vmuser vmuser 4096 Aug 26 07:59 empty-folder
-rw-rw-r--  1 vmuser vmuser 1273 Aug 26 08:01 updateUID.Dockerfile-0.50.0

Not sure why it might not find empty-folder when it is there. Do you use any security tools that might interfere here? What type of filesystem is /tmp on?
unable to prepare context: path "/tmp/devcontainercli-vmuser/empty-folder" not found

Not sure why it might not find empty-folder when it is there. Do you use any security tools that might interfere here? What type of filesystem is /tmp on?
unable to prepare context: path "/tmp/devcontainercli-vmuser/empty-folder" not found

Err, i'm not sure how to find out. I have changed nothing, just the default macos config. Its of one those hybrid filesystems, so it holds data in SSD and some in spinning drives.
Do you know a command to determine the if its different? I'm understanding is that its a normal file system, not a RAM or anything.

Not sure why it might not find empty-folder when it is there. Do you use any security tools that might interfere here? What type of filesystem is /tmp on?
unable to prepare context: path "/tmp/devcontainercli-vmuser/empty-folder" not found

LABEL=cloudimg-rootfs	/	 ext4	discard,errors=remount-ro	0 1
LABEL=UEFI	/boot/efi	vfat	umask=0077	0 1

Filesystem      Size  Used Avail Use% Mounted on
tmpfs           391M  992K  390M   1% /run
/dev/sda1        20G  2.0G   18G  11% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sda15      105M  6.1M   99M   6% /boot/efi
tmpfs           391M  4.0K  391M   1% /run/user/1001

Is there a better command ?

Arr, its an issue with the installation method https://snapcraft.io/docker.
Is this something the cli can support; changing the directory of the files which are created to all allow snaps default confinement to apply?
cat cloud-init.yml
users:
  - default
  - name: vmuser
    sudo: ALL=(ALL) NOPASSWD:ALL
    ssh_authorized_keys:
    - ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJi3WmihX63BYzsmFvBj1MsxkcSKGfIAgmOZfIJ6Ahf+ natured_amends0p@icloud.com
groups:
- docker
snap:
  commands:
  - [install, docker, --classic]
runcmd:
- adduser vmuser docker
- reboot
multipass launch --cloud-init ~/Desktop/cloud-init.yml --disk 20G --mem 4G --cpus 2 --name docker-vm

$ docker build -t test -f Dockerfile /tmp/empty
unable to prepare context: path "/tmp/empty" not found
$ ls -la
total 56
drwxrwxrwt 13 root   root   4096 Sep  5 12:55 .
drwxr-xr-x 19 root   root   4096 Sep  5 12:50 ..
drwxrwxrwt  2 root   root   4096 Sep  5 12:50 .ICE-unix
drwxrwxrwt  2 root   root   4096 Sep  5 12:50 .Test-unix
drwxrwxrwt  2 root   root   4096 Sep  5 12:50 .X11-unix
drwxrwxrwt  2 root   root   4096 Sep  5 12:50 .XIM-unix
drwxrwxrwt  2 root   root   4096 Sep  5 12:50 .font-unix
-rw-rw-r--  1 vmuser vmuser   37 Sep  5 12:54 Dockerfile
drwxrwxr-x  2 vmuser vmuser 4096 Sep  5 12:54 empty
drwx------  4 root   root   4096 Sep  5 12:50 snap-private-tmp
drwx------  3 root   root   4096 Sep  5 12:50 systemd-private-47075d106ad14badabec6490ba3a7377-systemd-logind.service-XvM9Uj
drwx------  3 root   root   4096 Sep  5 12:50 systemd-private-47075d106ad14badabec6490ba3a7377-systemd-resolved.service-UoBuLX
drwx------  3 root   root   4096 Sep  5 12:55 systemd-private-47075d106ad14badabec6490ba3a7377-systemd-timedated.service-IEoDzJ
drwx------  3 root   root   4096 Sep  5 12:50 systemd-private-47075d106ad14badabec6490ba3a7377-systemd-timesyncd.service-lp7wrW
$ cat Dockerfile
FROM alpine
WORKDIR /app
RUN adfasdf

running in home directory does work
$ vim Dockerfile
$ mkdir empty
$ docker build -t test -f Dockerfile ./empty
Sending build context to Docker daemon  1.583kB
Step 1/2 : FROM alpine
latest: Pulling from library/alpine
7264a8db6415: Pull complete
Digest: sha256:7144f7bab3d4c2648d7e59409f15ec52a18006a128c733fcff20d3a4a54ba44a
Status: Downloaded newer image for alpine:latest
 ---> 7e01a0d0a1dc
Step 2/2 : RUN asdfsd
 ---> Running in 489c581d9349

When inside the remote host, devcontainers extension will ask me to install docker
i'm getting the following output
 *  Executing task: chmod +x '/var/folders/9p/27z7ypt94t11m07t9yg46dlh0000gn/T/46886ac0-c53f-4d3e-95c7-6cf62ed471391693917975933-0.tmp.dmg' && open '/var/folders/9p/27z7ypt94t11m07t9yg46dlh0000gn/T/46886ac0-c53f-4d3e-95c7-6cf62ed471391693917975933-0.tmp.dmg'

 *  The terminal process failed to launch: Starting directory (cwd) "/Users/dev" does not exist.

Which seems like its trying to install a .dmg, but should it not be install docker for ubuntu, since i'm un a remote host

Similar issue in the extension repository: https://github.com/microsoft/vscode-remote-release/issues/5865

authors: chrmarti naturedamends

repo: devcontainers/cli


text:
Multiple active events not possible

Form link should be in content rather than card file.
Refer this.

Hey @rishav-singh-0 i can try to fix this issue?
My simple idea is using props for edit from static link to dynamic insert link.
It's a good idea? ->  href="old-static-link" -> href="props.link"

Yup that will do the thing.


text:
Avoid using .textContent

Text.data is faster:
https://esbench.com/bench/590c9cfe99634800a0347ffc

Indeed, .textContent is an order of magnitude slower. Apart from the code conflicts, is there anything blocking this PR? This is a pretty straight-forward and safe change, as you are checking n.nodeType === 3 (Text node, which is CharacterData and therefore has the data property).

authors: danielweck developit

repo: developit/preact-markup


text:
Preact + Custom Element Side Effects

Hi!
I'm trying to use Preact as React replacement in my mobile app. But it seems that Preact does not support Web Components used inside "render". Web Components is used from OnsenUI framework.
I think that i know why it does not work. Preact uses vdom-dom diffing algorithm, React uses vdom-vdom. Onsen's web components changes a DOM (trying to change) and Preact is thinking that it is not right and it's deny it.
Is there any solution with Preact?
Thanks.

@c58 - very interesting. Have you tried this with the beta version? (Currently 3.0.1)
To help me investigate, what are you seeing happen - for example: do the web components get instantiated, but their attributes are not set?
Thanks!

@developit unfortunately, 3.0.1 does not work too.
I've made an example to test it out.
https://github.com/c58/preact-webcomp-test
In src/index.js just uncomment Preact part and comment React part and see the difference.

Perfect, will take a look. Will be interesting to see if this is related to Shadow DOM polyfills.

@developit i've fixed minor mistake in the example. The issue is still there.

It looks like the way Onsen instantiates CustomElements.js (from the Polymer project) is causing it not to use Shadow DOM at all. This means things like <ons-page> moves all of its children into a different parent element, which seems like the kind of things Preact can't really account for.  I'm doing some testing to see how React can do the initial render without issue here, but I think a subsequent re-render would still mess things up for either framework.  Will get back to you shortly.

The same thing happened with mithril. About re-rendering: with react no issues at all. I have tried to change a content in ons-page and ons-toolbar – content re-rendered as expected.

5 февр. 2016 г., в 18:14, Jason Miller notifications@github.com написал(а):
It looks like the way Onsen instantiates CustomElements.js (from the Polymer project) is causing it not to use Shadow DOM at all. This means things like  moves all of its children into a different parent element, which seems like the kind of things Preact can't really account for. I'm doing some testing to see how React can do the initial render without issue here, but I think a subsequent re-render would still mess things up for either framework. Will get back to you shortly.
—
Reply to this email directly or view it on GitHub.

@c58 I came up with a test that shows that React behaves the same way after initial render.  The reason Preact and Mithril both remove ons's elements on initial render is because they build the DOM imperatively, whereas React initially uses a static HTML snapshot inserted via innerHTML to do so.
However, this means that changing the structure of the DOM using React will still cause issues.
Really this boils down to what Preact (and React) are designed for:  they are designed to constantly morph the DOM into a known state.  You simply specify the desired DOM structure, and the work of mutating the DOM to look correctly is done for you.
I've published my React example to a fork for you to look at, it shows that after 1s a DOM structure change within <ons-page> causes the same degradation visible via Preact & Mithril.
I'm definitely still open to working on this, but I think the issue here is a lot more specific than Web Components:  It's specifically integrating VDOM libraries with code that expects to be able to destructively mutate the DOM.
You can see a fairly complex example of how to account for this if you view the source of preact-mdl. Essentially, there is a wrapper placed around render() that tries to "backport" outside DOM mutations into the VDOM structure in order to preserve them.  However, I have not yet found a good way to account for "injected" layers using this technique - where children appended to an element are forcibly moved into a different parent outside the control of Preact.

Yes, you are right, it does not work :(
I will create an issue in OnsenUI repository.

On the positive side, thanks for letting me know about Onsen :)
I'm testing out Polymer + Preact as well to see if there are issues.

Closing for now, will revisit.

Hey there,
I'm running into an issue with a custom WebComponent not working when React is swapped for preact-compat. It seems to render on the initial view, but not subsequent views (IE, first page in a SPA app works, second page does not). Was there ever any workaround or resolution to this?

Hi @tconroy - would you be able to open a new issue in the preact-compat repo with a few details of your setup?  It doesn't seem related to this issue, since side effects have been fully supported in Preact since 6.x.

@developit Sure thing. Apologies, I should have posted there first. Hoping to get this resolved :)

Looks like the 'renders once, subsequent renders don't work' issue remains whether or not preact-compat is present :-S. I'm running:
    "preact": "8.1.0",
    "preact-router": "2.4.1",
    "wc-loader": "1.1.3"

After switching routes, the element (paper-input, vaadin-grid in this case) is still there in DOM (all attributes intact), but shady DOM is toast (as to why my setup defaults to shady dom despite browser support... ¯_(ツ)_/¯ ).

@H-Plus-Time I'm having a similar experience. FWIW my components are using the v1 spec ( not v0 ).
@developit -- is there any info I/we can provide to make debugging this easier/simpler?

this might come down to removing component recycling, which is already likely to happen for other reasons. preact just creates DOM elements via createElement(), there's no special behavior for WC's so there isn't really a place to workaround.  I'll try to ping you when I have something published without component recycling.

Sounds good @developit! I have a strong feeling that that is the issue -- although unfortunately my knowledge of web components is a bit limited.
If you would like me to test out a pre-release version to see if it fixes the issue on my end toss me a message and I'd be more than happy to report my findings.
Cheers!

authors: H-Plus-Time c58 developit tconroy

repo: developit/preact


text:
Finding a tile zoom of 1 takes 30s when quadkey_zoom is at 10 (or higher)

Intro
👋 hi there....I'm a big fan of the library! When using it with my tile server I noticed that low zoom levels were taking a really long time and a big chunk of it was being spent in find_quadkeys. It's super helpful the function is cached, but I'd love to figure out how to get the function call down to be sub-second (as that is how it performs for higher zoom levels) . Equally I have some ideas of work-arounds that I wanted to discuss to make sure I wasn't doing everything completely wrong 😅
Reproduce the issue
Here is an example setup to reproduce the issue:
from cogeo_mosaic.backends import MosaicBackend
import timeit

mosaic = MosaicBackend("https://raw.githubusercontent.com/developmentseed/mosaicjson-spec/refs/heads/master/0.0.3/example/dg_post_idai.json")

def run_mosaic_tile():
    try:
        mosaic.tile(1, 0, 1)
    except Exception:
        pass

print(f"Execution time: {timeit.timeit(run_mosaic_tile, number=1):.6f} seconds")

This prints Execution time: 27.068926 seconds for me.
The root of the issue makes sense as find_quadkeys will need to produce about 200k quad keys given the quadkey_zoom is at 10 and I'm asking for a zoom level of 1.
Questions
So my specific questions are:

Am I overlooking something or is this expected behavior?
I acknowledge the min zoom is a really low level that I could just not allow users to get to? This could be an option to consider (I'm semi-new to the geo space) but if possible, I'd love to actually support this use case
One workaround I've considered is to create multiple MosaicJSON files (at least one in the low zoom levels), for example one mosaic JSON at quadkey_zoom of 10  and another at a quadkey_zoom of 4 and route any zooms levels at 4 or lower to the quadkey_zoom of 4. Having multiple MosaicJSON files around feels a bit odd, but maybe I'm just incorrect to think that.

Hi @bh-perennial

The root of the issue makes sense as find_quadkeys will need to produce about 200k quad keys given the quadkey_zoom is at 10 and I'm asking for a zoom level of 1.

😱 don't do that! this is just a level too far from the quadkey zoom level. Imagine you have 200k quadkey and each quad keys has 1 or 2 files, when trying to build a tile you'll try to open 200k-400k rasters (multiple times the same) 😱
For a tile request to success I would say that you don't want to open more than 10 files!!! There is no magic with COG, it's not worth it to open a COG if it's to use for sub-pixel values 😅

I acknowledge the min zoom is a really low level that I could just not allow users to get to? This could be an option to consider (I'm semi-new to the geo space) but if possible, I'd love to actually support this use case

Just use a quadkey_zoom level which is in < than the min zoom of your data. https://github.com/developmentseed/mosaicjson-spec/tree/main/0.0.3#38-quadkey_zoom BUT still this should be couple levels up, not 9 levels.

One workaround I've considered is to create multiple MosaicJSON files (at least one in the low zoom levels), for example one mosaic JSON at quadkey_zoom of 10 and another at a quadkey_zoom of 4 and route any zooms levels at 4 or lower to the quadkey_zoom of 4. Having multiple MosaicJSON files around feels a bit odd, but maybe I'm just incorrect to think that.

Yeah we've looked into this a while ago https://github.com/developmentseed/mosaicjson-spec/discussions/22 but to be honest the Static file model should be deprecated. We know use pgstac for most of our mosaic backend https://github.com/stac-utils/titiler-pgstac but if you still want to have a simple static backend you might be better served with a geoparquet backend (https://github.com/developmentseed/cogeo-mosaic/issues/224)

Thank you @vincentsarago for the super quick and really helpful response!

authors: bh-perennial vincentsarago

repo: developmentseed/cogeo-mosaic


text:
Date element added to options page

What does this PR do?

Date Element added to the options page saved scrrolls.

files changed (for date) : save.js , options.js, options.css.

+some design and animation changes.

Screenshots and/or Live Demo

@RohitKaushal7 Let's not add the gradient to the background because currently it matches the overall extension theme.

@prateek3255 I have made the variable changes and restored the style changes (/* some commented out */), although there are still some hover animation (style changes). please remove the code lines what you feel doesn't suit.

Merged The Delete options and some style changes...
demo..

LGTM! Thanks for working on this @RohitKaushal7

repo: devfolioco/scrroll-in


text:
Kibana server is not ready yet.

Problem description
When I ran docker-compose on WSL it worked but when I run that compose file on Server gives some error
I changed .env file to new password with ' ' . And also I tried to change password without ' ' [a-z; A-z; 0-9]

Extra information
Stack configuration

Docker setup

$ docker version
Client: Docker Engine - Community
 Version:           20.10.14
 API version:       1.41
 Go version:        go1.16.15
 Git commit:        a224086
 Built:             Thu Mar 24 01:49:57 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.14
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.15
  Git commit:       87a90dc
  Built:            Thu Mar 24 01:48:24 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.5.11
  GitCommit:        3df54a852345ae127d1fa3092b95168e4a88e2f8
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.3-0-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker-compose version
docker-compose version 1.26.0, build d4451659
docker-py version: 4.2.1
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Container logs

$ docker-compose logs
kibana_1         | [2022-04-25T10:04:34.728+00:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. connect ECONNREFUSED 172.19.0.2:9200
kibana_1         | [2022-04-25T10:04:38.409+00:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. security_exception: [security_exception] Reason: unable to authenticate user [kibana_system] for REST request [/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip]
elasticsearch_1  | {"@timestamp":"2022-04-25T10:04:37.690Z", "log.level": "INFO", "message":"Authentication of [kibana_system] was terminated by realm [reserved] - failed to authenticate user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[7f68918abfe5][system_critical_read][T#1]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","trace.id":"b758ac14b7943c3a7d1241caea8c4d1b","elasticsearch.cluster.uuid":"gHWINeCAQvSNQqDZpy0pow","elasticsearch.node.id":"NF9tWXFlR0eF64oMdWjFgQ","elasticsearch.node.name":"7f68918abfe5","elasticsearch.cluster.name":"docker-cluster"}
elasticsearch_1  | {"@timestamp":"2022-04-25T10:04:44.026Z", "log.level": "WARN", "message":"Authentication to realm default_native failed - Password authentication failed for logstash_internal", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[7f68918abfe5][system_critical_read][T#1]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","elasticsearch.cluster.uuid":"gHWINeCAQvSNQqDZpy0pow","elasticsearch.node.id":"NF9tWXFlR0eF64oMdWjFgQ","elasticsearch.node.name":"7f68918abfe5","elasticsearch.cluster.name":"docker-cluster"}
logstash_1       | [2022-04-25T10:04:44,029][WARN ][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES instance, but got an error {:url=>"http://logstash_internal:xxxxxx@elasticsearch:9200/", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :message=>"Got response code '401' contacting Elasticsearch at URL 'http://elasticsearch:9200/'"}
elasticsearch_1  | {"@timestamp":"2022-04-25T10:04:45.062Z", "log.level": "INFO", "message":"Authentication of [kibana_system] was terminated by realm [reserved] - failed to authenticate user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[7f68918abfe5][system_critical_read][T#2]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","trace.id":"b758ac14b7943c3a7d1241caea8c4d1b","elasticsearch.cluster.uuid":"gHWINeCAQvSNQqDZpy0pow","elasticsearch.node.id":"NF9tWXFlR0eF64oMdWjFgQ","elasticsearch.node.name":"7f68918abfe5","elasticsearch.cluster.name":"docker-cluster"}

@S0b1t thanks for the detailed issue report 🙌
Could you please also share the output of docker-compose logs setup?

To me it looks like the stack was initialized with certain passwords (e.g. "changeme"), and then those passwords were changed inside the .env file without being applied to Elasticsearch first.
Passwords inside the .env file are only enforced on the first run. To change passwords at a later stage, it is necessary to refer to the following instructions: https://github.com/deviantony/docker-elk#setting-up-user-authentication
One way to solve the current problem is to remove the volume holding the /state/done file, as follows:
docker-compose rm setup
docker volume rm docker-elk_setup

Then run the setup again:
docker-compose up setup

This will reset the passwords of the kibana_system and logstash_internal users (but not the elastic user, which is special).
If the setup fails to authenticate with Elasticsearch, try changing the ELASTIC_PASSWORD value back to "changeme" inside the .env file, then try this last command again.

The warning about server.publicBaseUrl can safely be ignored.

That solved my issue. Thanks a lot:)

Glad it helped!

repo: deviantony/docker-elk


text:
Memcached cache not working

Monitoring the Memcached cache via telnet shows only a partially complete cache after the rebuild task is run. Review correct settings, as well as ascertain proper cache lifetime settings for memcached.

Anecdotal evidence from a UAT site  using memcached suggests that this is working.

Closing as FIXED in 3a6edf2.

repo: deviateltd/silverstripe-cacheable


text:
stop escape from propagating outside the dialog if possible

if escape is pressed inside the dialog we should stopPropagation incase the dialog is nested inside another popup that also is listening for escape keypress.

fixed in v1.0.5

repo: devlop/dialog


text:
🛑 Message Board is down

In b230c19, Message Board (https://msg-board-server.onrender.com/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Message Board is back up in 26333c3 after 26 minutes.

repo: devnullsans/upptime-monitor


text:
🛑 Photoz ICVJ is down

In a2511db, Photoz ICVJ (https://photoz-icvj.onrender.com/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Photoz ICVJ is back up in f197cba after 6 minutes.


text:
Cannot create domain record with V2 API

https://github.com/devo-ps/dopy/blob/master/dopy/manager.py#L362
In V2, DO API return a "domain_record" json object, not "record" as in V1, see: https://developers.digitalocean.com/documentation/v2/#domain-records
Other domain record functions are ok.

Hi @mbugela and @zbal,
any chance to merge this soon? I run into this problem today as well...
Thanks,
Karel

Hi @zbal,
I really want this to be merged too, the feature is broken right now.
Thanks

+1

Hi guys - just merged - will push the change to pypi today. Thanks for the PR!

authors: KarelJakubec certifiedloud mbugeia zbal

repo: devo-ps/dopy


text:
#570: fix git rev parse error if not in project

fixes #570
Also include small cleanup from #467 and small partial fix of #525

Since #570 is a critical blocker bug, that already prevented @WorkingAmeise from setting up his IDE, I will merge this right away without waiting for review approval...

Pull Request Test Coverage Report for Build 10635936161
Details

0 of 0   changed or added relevant lines in 0 files are covered.
21 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.001%) to 64.839%

Files with Coverage Reduction
New Missed Lines
%

com/devonfw/tools/ide/context/AbstractIdeContext.java
21
58.91%

Totals

Change from base Build 10629501002:
0.001%

Covered Lines:
5731

Relevant Lines:
8529

💛  - Coveralls

authors: coveralls hohwille

repo: devonfw/IDEasy


text:
Apply use client directive to IntercomProvider

The App Router in NextJS 13 requires Providers used in server components to have the use client directive.
This means that using IntercomProvider in a Root Layout (which must be an SRC) requires wrapping it in a client-side component.
This PR declares the provider as a client component.
See: https://nextjs.org/docs/getting-started/react-essentials#rendering-third-party-context-providers-in-server-components

Big thanks for this PR. However, I'm not planning to introduce any platform/framework specifics in this library

Big thanks for this PR. However, I'm not planning to introduce any platform/framework specifics in this library

@devrnt I don't believe the "use client" is framework-specific. It's part of React's server component realm. See https://github.com/reactjs/rfcs/blob/main/text/0227-server-module-conventions.md
NextJS happens to be the first major framework adopting RSCs.

Big thanks for this PR. However, I'm not planning to introduce any platform/framework specifics in this library

@devrnt I don't believe the "use client" is framework-specific. It's part of React's server component realm. See https://github.com/reactjs/rfcs/blob/main/text/0227-server-module-conventions.md
NextJS happens to be the first major framework adopting RSCs.

Fair enough, but I stand by my position. This could be reconsidered in the future when the adoption rate is higher and/or this feature is more requested

authors: devrnt rubendinho

repo: devrnt/react-use-intercom


text:
⚠ Mobitopup has degraded performance

In 6ef34d0, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 8494 ms

Resolved: Mobitopup performance has improved in b5a2d4c.


text:
.anyOf query return is inconsistent but .bulkGet works

is there any difference in the concurrency logic for bulkGet and where('id').anyOf([...])?
it seems like anyOf has some sort of debounce that suffers from a race condition.
if we call .anyOf rapidly the final result may not be current. it works if we add a short delay between each call.
.bulkGet does not suffer from this, but I'd like to use anyOf so we can sort

anyOf uses an IDBCursor to iterate results sequencially  in index order while bulkGet executes multiple calls to IDBObjectStore.get() in parallel.
AnyOf has been almost untouched for 8 years. There have been shaky bugs in the Safari implementation of IDBCursor historically but for the last 3-4 years or so, I haven't heard of any race-condition bugs in IDBCursor particularly.
Would it be possible to create a reproduction of the issue in jsfiddle or similar? That would help a lot.

authors: dfahlander frankleng


text:
Add a method to send a jukebox popup to Player

The method was there in session but it was never added to player

Looks good, thank you!

repo: df-mc/dragonfly


text:
Required fields Google News

According to the documentation, there are some more required fields.
I added a couple of those fields.
Documentation I based myself on: https://support.google.com/news/publisher/answer/74288?hl=en

@mkurz Can you approve this pull request and make a new release? The current GoogleNewsSitemap is outdated and therefore useless.

I will have a look but I am very very busy right now. Maybe send me a reminder in like two weeks or so.
Can you also check the pull request if it is ok?

@mkurz

Maybe send me a reminder in like two weeks or so

Can you approve this pull request and make a new release?

@berjanjonker I hope I will find time soon for this pull request, sorry I am very busy right  now.

Fixed via 1ceac7f3f079231d8ac511091102f5ff290e7dc5

Version 1.1.0 containing this fix should be available in a few hours.

authors: TomWalbers berjanjonker mkurz


text:
Failed to execute 'add' on 'IDBObjectStore'

Code
dexie.service.ts
import Dexie from 'dexie';
import { IJourney, Journey } from '../models/journey.model';

export class DexieService extends Dexie {
  journey: Dexie.Table<IJourney, number>;
  constructor() {
    super('driver-app');
    const db = this;
    db.version(1).stores({
      journey: 'id,date,capacity,route,loc',
    });
    db.journey.mapToClass(Journey);
    db.journey.add(new Journey(1, new Date(), 2, 3, 4));
  }
}

journey.model.ts
export interface IJourney {
  id: number;
  date: Date;
  capacity: number;
  route: number;
  loc: number;
}
export class Journey implements IJourney {
  id: number;
  date: Date;
  capacity: number;
  route: number;
  loc: number;
  constructor(id: number, date: Date, capacity: number, route: number, loc: number) {}
}

Description
The above code is part of an angular app run with DexieService provided in 'app.module.ts' and being in the constructor of a view.
Versions

Angular 6.1.2
Dexie 2.0.4

Problem
I get the following error message, as a result of the db.journey.add(new Journey(1, new Date(), 2, 3, 4));:
Unhandled rejection: DataError: Failed to execute 'add' on 'IDBObjectStore': Evaluating the object store's key path did not yield a value.
Error: Failed to execute 'add' on 'IDBObjectStore': Evaluating the object store's key path did not yield a value.
    at http://localhost:4200/vendor.js:134044:79
    at supplyIdbStore (http://localhost:4200/vendor.js:133718:24)
    at http://localhost:4200/vendor.js:133223:28
    at usePSD (http://localhost:4200/vendor.js:132706:16)
    at newScope (http://localhost:4200/vendor.js:132603:14)
    at http://localhost:4200/vendor.js:133221:24
    at http://localhost:4200/vendor.js:134310:30
    at executePromiseTask (http://localhost:4200/vendor.js:132310:9)
    at new Promise (http://localhost:4200/vendor.js:132127:5)
    at Transaction._promise (http://localhost:4200/vendor.js:134309:25)
From previous:
    at Transaction._promise (http://localhost:4200/vendor.js:134309:25)
    at tempTransaction (http://localhost:4200/vendor.js:133220:26)
    at http://localhost:4200/vendor.js:133210:61
    at http://localhost:4200/vendor.js:132725:23
    at callListener (http://localhost:4200/vendor.js:132408:19)
    at endMicroTickScope (http://localhost:4200/vendor.js:132495:25)
    at IDBOpenDBRequest.__zone_symbol__ON_PROPERTYsuccess (http://localhost:4200/vendor.js:132562:17)
    at IDBOpenDBRequest.wrapFn (http://localhost:4200/polyfills.js:3510:39)

My primary key is "inbound" as it says in the docs about bulk add here. When I tried including a key I get this different error implying I was right about not providing the key:
Unhandled rejection: DataError: Failed to execute 'add' on 'IDBObjectStore': The object store uses in-line keys and the key parameter was provided.
Error: Failed to execute 'add' on 'IDBObjectStore': The object store uses in-line keys and the key parameter was provided.
    at http://localhost:4200/vendor.js:134044:54
    at supplyIdbStore (http://localhost:4200/vendor.js:133718:24)
    at http://localhost:4200/vendor.js:133223:28
    at usePSD (http://localhost:4200/vendor.js:132706:16)
    at newScope (http://localhost:4200/vendor.js:132603:14)
    at http://localhost:4200/vendor.js:133221:24
    at http://localhost:4200/vendor.js:134310:30
    at executePromiseTask (http://localhost:4200/vendor.js:132310:9)
    at new Promise (http://localhost:4200/vendor.js:132127:5)
    at Transaction._promise (http://localhost:4200/vendor.js:134309:25)
From previous:
    at Transaction._promise (http://localhost:4200/vendor.js:134309:25)
    at tempTransaction (http://localhost:4200/vendor.js:133220:26)
    at http://localhost:4200/vendor.js:133210:61
    at http://localhost:4200/vendor.js:132725:23
    at callListener (http://localhost:4200/vendor.js:132408:19)
    at endMicroTickScope (http://localhost:4200/vendor.js:132495:25)
    at IDBOpenDBRequest.__zone_symbol__ON_PROPERTYsuccess (http://localhost:4200/vendor.js:132562:17)
    at IDBOpenDBRequest.wrapFn (http://localhost:4200/polyfills.js:3510:39)

This is almost certainly me being an idiot, but if you could help me anyway I would be eternally greatful!

Seems the constructor does not set any property. So basically you are adding an empty object.

Oh my god I'm so sorry for wasting your time. It's typescript and I thought it could automatically do the assignment but it turns out I need a public or private keyword (relevant article).
journey.model.ts
export interface IJourney {
  id: number;
  date: Date;
  capacity: number;
  route: number;
  loc: number;
}
export class Journey implements IJourney {
  constructor(
    public id: number,
    public date: Date,
    public capacity: number,
    public route: number,
    public loc: number
  ) {}
}

authors: adnathanail dfahlander