GithubHelp home page GithubHelp logo

solid-calendar-store's People

Contributors

pheyvaer avatar rubenverborgh avatar zelzahn avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

zelzahn

solid-calendar-store's Issues

Failed to load remote context https://linkedsoftwaredependencies.org/bundles/npm/solid-calendar-store/^0.0.0/components/context.jsonld: Internal Server Error

HI,

I used the sample config file as instructed in the README. All seem well, however, when I was tried to access my server, the folllowing error log appeared:

022-02-18T13:17:38.843Z [Components.js] warn: Detected remote context lookup for 'https://linkedsoftwaredependencies.org/bundles/npm/solid-calendar-store/^0.0.0/components/context.jsonld' in /home/ubuntu/workspace/community-server/config-cal.json. This may indicate a missing or invalid dependency, or an invalid context URL.
2022-02-18T13:17:38.907Z [Components.js] warn: Detected remote context lookup for 'https://linkedsoftwaredependencies.org/bundles/npm/@rmlio/solid-rml-store/^0.0.0/components/context.jsonld' in /home/ubuntu/workspace/community-server/config-cal.json. This may indicate a missing or invalid dependency, or an invalid context URL.
Error: could not instantiate server from /home/ubuntu/workspace/community-server/config-cal.json
Error: Error while parsing file "/home/ubuntu/workspace/community-server/config-cal.json": Failed to load remote context https://linkedsoftwaredependencies.org/bundles/npm/solid-calendar-store/^0.0.0/components/context.jsonld: Internal Server Error
at Function.addPathToError (/home/ubuntu/.npm/_npx/519be4cd80562143/node_modules/componentsjs/lib/rdf/RdfParser.js:73:16)
at PassThrough. (/home/ubuntu/.npm/_npx/519be4cd80562143/node_modules/componentsjs/lib/rdf/RdfParser.js:46:38)
at PassThrough.emit (node:events:402:35)
at JsonLdParser. (/home/ubuntu/.npm/_npx/519be4cd80562143/node_modules/rdf-parse/lib/RdfParser.js:71:47)
at JsonLdParser.emit (node:events:402:35)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

It looks like a depedency issue. The jsonld file cannot be found in the given URL. Should a different version be used and updated in the config file?

Many thanks.

Clarify instructions wrt Google Calendar

The current instructions read:

Rename config/config-calendar-example.json to config/config-calendar.json.
Optional: configure use of Google Calendar. If you do not do this, calls involving Calendar will fail.

    Update calendar id of Google Calendar in config/config-calendar.json.
    Give Solid Calendar Store access to Google Calendar API via node scripts/get-google-access-token.js.

However, we should make clear that any ical feeds can be configured, including the secret feeds exposed by Google Calendar. So no special auth is required for GCal. (Only when ping-based realtime updates are requested._

User-level configuration?

Right now, the README describes that the (calendar) configuration should be loaded upon service start. It assumed the server is for a single user (pod) sits on the root.

Is there a way to allow the server to serve multiple pods, and each of them have their own calendar configurations as a file?

Potentially incomplete set-up instructions and versioning issues

I'm trying to set up this application and encountered some issues. Currently I find no way to work around all of them.
They seem to mean the set up instructions in README is incomplete.
Here they are:

  1. A directory personal/ should be created, otherwise error is thrown when doing npx.
  2. The file node_modules/@solid/community-server/config/ldp/permissions/acl.json is missing. I dig into the history of CSS, and found that this file was moved to config/ldp/modes/acl.json in commit e8dedf5c239f12c36b414c1dd9c6419a31f467de, and removed in commit 7f8b923399d0b9510ed1aaf4615e49b568ae5ea7. There is no longer this file in the current version of CSS.
  3. I temporarily work around the line requiring that acl.json, by deleting it. But it still gives errors: ErrorResourcesContext: Could not find (valid) component types for config "urn:solid-server:defau lt:ModesExtractor" among its types, or a requireName (the error message is quite long; I can supply if necessary).

This error does not look like anything I'm able to easily solve, so I'm asking for help, probably with an updated version of README and dependencies.

In addition, if I delete packages-lock.json and run npm i to regenerate it, it will be different from the one in the repo. Other errors will appear when running npm i, saying the errors below, and refuses to finish the "compilation" (tsc step):

^[src/google-calendar-get-store.ts:7:41 - error TS2307: Cannot find module '@solid/community-ser
ver/dist/ldp/representation/RepresentationPreferences' or its corresponding type declarations.  
                                                                                                
7 import {RepresentationPreferences} from "@solid/community-server/dist/ldp/representation/Repre
sentationPreferences";                                                                          
                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~                                                                           
                                                                                                
src/http-get-store.ts:8:43 - error TS2307: Cannot find module '@solid/community-server/dist/ldp/
representation/RepresentationPreferences' or its corresponding type declarations.               
                                                                                                
8 import { RepresentationPreferences } from "@solid/community-server/dist/ldp/representation/Rep
resentationPreferences";                                                                        
                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~ 

How to configure with multiple calendars?

I have several calendars, and each of them will have their own URL. How should I put them easily to the calendar store?
Currently, it looks like I need to copy-paste the RepresentationConverterStore with a HttpGetStore inside for multiple times, and manually change the URL and ID. Then I need to use multiple AggregateStore to aggregate them. This is quite painful.

Is there a better way? In particular, can some store accept multiple URLs and use the same method to handle/transform them?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.