~sschwarzer

~sschwarzer/racket-glossary

Last active 23 days ago

~sschwarzer/ftputil

Last active 3 months ago
View more

Recent activity

Re: "PermanentError" in AWS Lambda 3 months ago

From Stefan Schwarzer to ~sschwarzer/ftputil

Hi Vrushab,

On 2022-05-18 15:50, Vrushab Mulik wrote:
> The ftputil library works well on my local PC but when I try it on AWS
> Lambda I get the following message
> 
> [ERROR] PermanentError: 530 Login authentication failed
> Debugging info: ftputil 5.0.4, Python 3.9.11 (linux)
> 
> Please help me on this one.

If you haven't already, can you please try to log in with
ftplib? If that works, can you send the code you use with
ftplib and the code you use with ftputil?

ftputil 5.0.4 released 3 months ago

From Stefan Schwarzer to ~sschwarzer/ftputil

ftputil 5.0.4 is now available from
https://ftputil.sschwarzer.net/download .


Changes since the last stable release 5.0.3
-------------------------------------------

- Fix cache invalidation for `FTPHost.rename` [1].

- Make stat cache invalidation for `FTPHost.remove`, `FTPHost.rmdir`
   and `FTPHost.rmtree` more robust in case an exception occurs during
   these operations.

Re: Long code lines in ticket descriptions should be easier to read 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

On 2022-04-11 12:09, Drew DeVault wrote:
> I thought we already had a ticket for this, but I can't find it. Can you
> file one here?
> 
> https://todo.sr.ht/~sircmpwn/todo.sr.ht/

Done, https://todo.sr.ht/~sircmpwn/todo.sr.ht/269 .

Re: Long code lines in ticket descriptions should be easier to read 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

On 2022-04-11 10:53, Drew DeVault wrote:
> When pasting large logs and such you're encouraged to stick them in a
> paste.sr.ht dump instead of directly onto todo.sr.ht.

That makes sense, but I think the stacktrace in that ticket isn't
that large. :-) But I do get your point!

What about _actually_ encouraging ticket submitters by recommending
using paste.sr.ht when entering a ticket? ;-) That is, putting a
remark near the ticket entry form, something similar to

   Tip: Use [paste.sr.ht](https://paste.sr.ht/) to add
   logs and stacktraces.

Long code lines in ticket descriptions should be easier to read 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

In case of relatively long code lines in ticket descriptions,
as in

   https://todo.sr.ht/~sschwarzer/ftputil/143

the layout shows only half of the longer lines. I do get a
horizontal scrollbar, but in my opinion it would be helpful
if the page layout showed more of the long lines.

If the screen is large is enough to make the browser window
much wider, there's still the curiosity that this doesn't
change the layout of the description and meta information,
but just adds empty space to the left and right.

Re: New ftputil infrastructure testing and feedback 4 months ago

From Stefan Schwarzer to ~sschwarzer/ftputil

On 2022-04-01 21:57, Stefan Schwarzer wrote:
> TL;DR: Unless I missed anything, all ftputil services are
> now migrated, either in their final form or in test mode.

The website including the ticket system is finally migrated.
If you find any problems, please let me know.

Best regards,
Stefan

New ftputil infrastructure testing and feedback 4 months ago

From Stefan Schwarzer to ~sschwarzer/ftputil

Hi everyone! :-)

TL;DR: Unless I missed anything, all ftputil services are
now migrated, either in their final form or in test mode.
Please give feedback on the below points, if possible by
Friday, 2022-04-08.

--------------------------------------------------

Here's a follow-up on the ftputil infrastructure migration
(see also [1]).

[1] https://lists.sr.ht/~sschwarzer/ftputil/%3C551179d0-b28b-b1c4-4405-8e5263270047%40sschwarzer.net%3E

Re: Two suggestions for Markdown CSS 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

On 2022-03-20 18:40, Stefan Schwarzer wrote:
> https://git.sr.ht/~sschwarzer/ftputil/tree/main/item/doc/ftputil.md
> 
> To make the layout even nicer, I have two suggestions:
> 
> - Leave a bit more space after each code block, similar
>     to the space before the code block.
> 
> - Use thin lines between table rows or use alternating
>     colors for the rows (or some other change to tell
>     table rows apart if cells are multi-line, which isn't
>     the case for the table in the above page).
What I wrote refers to the Markdown view when browsing
repositories.

Two suggestions for Markdown CSS 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

I was able to migrate my (main) documentation from
reStructuredText to Markdown and like the result. :-)

https://git.sr.ht/~sschwarzer/ftputil/tree/main/item/doc/ftputil.md

To make the layout even nicer, I have two suggestions:

- Leave a bit more space after each code block, similar
   to the space before the code block.

- Use thin lines between table rows or use alternating
   colors for the rows (or some other change to tell
   table rows apart if cells are multi-line, which isn't
   the case for the table in the above page).

Re: Defining explicit anchors in Markdown 4 months ago

From Stefan Schwarzer to ~sircmpwn/sr.ht-discuss

On 2022-03-20 13:50, Drew DeVault wrote:
> What you need is id="foo", not name.

This actually works. Thanks! :-)


The `name` attribute was recommended over `id` in some
answers on the matter that I read. But I now see that
`name` was actually declared as obsolete in newer HTML
standards.