-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2025-02 dev log #11
Comments
OK, so I'm working on pondersource/dev-stock#160. Switching to the improve-shell-scripts branch was good, and I was able to add the test easily. The trouble is that the test is failing because OcmStub is not behaving in the way that Nextcloud expects. Maybe I should try to add a node.js webdav server into it, since I also want to test actual file access, and I don't want my stub to be too brittle. So the issues involved are: |
hm, mod_log_forensic worked and then it stopped logging things. Retrying now. |
This should give me the exact request and response that ocm-stub needs to mimic. |
Now I have the request body of the PROPFIND request but not the response body:
|
Will continue tomorrow! |
Ah, I can get the response by replaying the request with curl! |
Added a remote share now, this were the call from nextcloud2.docker to nextcloud1.docker: Discovery
Accepted notification
PROPFINDcurl -X 'PROPFIND' -d "@propfind.xml" -H 'Authorization: Basic MnBaaFNxRThEaVFMcWVJOg==' https://nextcloud1.docker/public.php/webdav/ Request body: <?xml version="1.0" encoding="UTF-8"?>
<d:propfind xmlns:d="DAV:">
<d:prop xmlns:x="http://owncloud.org/ns" xmlns:x1="http://open-collaboration-services.org/ns">
<d:getlastmodified/>
<d:getcontentlength/>
<d:getcontenttype/>
<x:permissions xmlns:x="http://owncloud.org/ns"/>
<x1:share-permissions xmlns:x="http://open-collaboration-services.org/ns"/>
<d:resourcetype/>
<d:getetag/>
<d:quota-available-bytes/>
</d:prop>
</d:propfind> Response body: <?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:oc="http://owncloud.org/ns" xmlns:nc="http://nextcloud.org/ns">
<d:response>
<d:href>/public.php/webdav/</d:href>
<d:propstat>
<d:prop>
<d:getlastmodified>Tue, 07 Jan 2025 08:26:30 GMT</d:getlastmodified>
<d:getcontentlength>164</d:getcontentlength>
<d:getcontenttype>text/plain</d:getcontenttype>
<oc:permissions>RGNVW</oc:permissions>
<d:resourcetype/>
<d:getetag>"b134a68c554798adf769917887321c83"</d:getetag>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<x1:share-permissions xmlns:x1="http://open-collaboration-services.org/ns"/>
<d:quota-available-bytes/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
</d:multistatus> |
Testing michielbdejong/ocm-stub#9 interactively now with:
|
Seems I have it working in dev now but not in ci. Maybe it's due to the longer filename, I'll try changing that. |
share-with OCM -> OC10, NC27, NC28 done. |
docker build --build-arg CACHEBUST="default" --file ./dockerfiles/ocmstub.Dockerfile --tag pondersource/ocmstub:v1.0.0 . |
On to Pivot! I'll start with solid-contrib/pivot#47 because that feels pretty fundamental. |
I need to decide what I want to do with the dev config. Should it be pretty unrelated to prod, so using in-memory storage etc, like the upstream default config? Probably not, it doesn't really help us. We don't have the same use case for dev config as upstream CSS, and people who just want to run a super simple CSS can do that by running npm start on CSS. What we probably want is a config that is as similar to prod as possible, so only some minor changes that make running on localhost easier:
|
Today was a pretty rough day digging deep into the lands where nothing works. In the end I got out of it by taking a step back, changing my strategy multiple times until I was able to peel off one confounding problem and get a clearer view of the other one, bisecting git history from the last time things were known to work (although comparing configs from three incompatible sources, namely the CSS config generator, older Pivot configs, and the css-mashlib repo), and using lolcathost.de and a self-signed cert, and I was able to close solid-contrib/pivot#47 so that feels worthwhile. The issues left for https://github.com/solid-contrib/pivot/milestone/1 feel doable for tomorrow, hoping to tag Pivot v1.5.0 according to schedule to finish this week. |
Done! |
First working week of the year 2025, plans:
OCM
Solid
The text was updated successfully, but these errors were encountered: