[47°09′08″S, 126°43′03″W] Transponder still failing – switching to analog communication
[47°09′04″S, 126°43′02″W] Transponder still failing
[47°09′10″S, 126°43′27″W] Transponder still failing – switching to analog communication
[47°09′35″S, 126°43′46″W] Transponder still failing – switching to analog communication
[47°09′03″S, 126°43′07″W] Dosimeter still failing
[47°09′07″S, 126°43′20″W] Transponder still failing
[47°09′46″S, 126°43′51″W] Dosimeter still failing
[47°09′55″S, 126°43′48″W] Dosimeter still failing
[47°09′09″S, 126°43′42″W] Dosimeter still failing
[47°09′31″S, 126°43′32″W] Transponder still failing – switching to analog communication
[47°09′44″S, 126°43′52″W] Transponder still failing – switching to analog communication
[47°09′05″S, 126°43′20″W] Dosimeter still failing
[47°09′28″S, 126°43′31″W] Transponder still failing – switching to analog communication
[47°09′35″S, 126°43′04″W] Transponder still failing
[47°09′17″S, 126°43′24″W] Transponder still failing – switching to analog communication
[47°09′29″S, 126°43′06″W] Transponder still failing
[47°09′01″S, 126°43′40″W] Dosimeter still failing
[47°09′10″S, 126°43′53″W] Transponder still failing – switching to analog communication
[47°09′12″S, 126°43′46″W] Dosimeter still failing
[47°09′44″S, 126°43′03″W] Transponder still failing – switching to analog communication
[47°09′02″S, 126°43′55″W] Transponder still failing – switching to analog communication
[47°09′03″S, 126°43′36″W] Transponder still failing – switching to analog communication
[47°09′35″S, 126°43′49″W] Transponder still failing
[47°09′45″S, 126°43′11″W] Transponder still failing
Gajim: Gajim 1.8.3
Just after the release of Gajim 1.8.2, we’re releasing Gajim 1.8.3 with improvements for the profile window, fail-safes for anonymous accounts, bug fixes for the account wizard, and several other fixes. Thank you for all your contributions!
Several issues with anonymous accounts should be resolved by improved account handling in general.
Gajim’s main window can now be closed by pressing the Esc key, if you enable closing windows via Esc in Gajim’s preferences.
What el … ⌘ Read more
[47°09′48″S, 126°43′29″W] Transponder still failing
[47°09′22″S, 126°43′26″W] Dosimeter still failing
[47°09′42″S, 126°43′11″W] Transponder still failing – switching to analog communication
[47°09′54″S, 126°43′12″W] Dosimeter still failing
[47°09′13″S, 126°43′55″W] Transponder still failing – switching to analog communication
[47°09′14″S, 126°43′07″W] Transponder still failing
[47°09′18″S, 126°43′08″W] Dosimeter still failing
[47°09′19″S, 126°43′19″W] Transponder still failing – switching to analog communication
[47°09′20″S, 126°43′27″W] Transponder still failing – switching to analog communication
[47°09′24″S, 126°43′53″W] Transponder still failing
[47°09′52″S, 126°43′17″W] Dosimeter still failing
[47°09′15″S, 126°43′41″W] Transponder still failing – switching to analog communication
[47°09′32″S, 126°43′37″W] Dosimeter still failing
[47°09′20″S, 126°43′27″W] Transponder still failing – switching to analog communication
[47°09′21″S, 126°43′47″W] Transponder still failing
[47°09′48″S, 126°43′59″W] Transponder still failing – switching to analog communication
[47°09′55″S, 126°43′38″W] Transponder still failing – switching to analog communication
[47°09′02″S, 126°43′42″W] Transponder still failing – switching to analog communication
[47°09′20″S, 126°43′28″W] Transponder still failing – switching to analog communication
[47°09′45″S, 126°43′14″W] Dosimeter still failing
[47°09′59″S, 126°43′44″W] Transponder still failing – switching to analog communication
[47°09′13″S, 126°43′19″W] Transponder still failing
[47°09′06″S, 126°43′42″W] Dosimeter still failing
[47°09′59″S, 126°43′14″W] Transponder still failing – switching to analog communication
[47°09′03″S, 126°43′53″W] Dosimeter still failing
[47°09′05″S, 126°43′51″W] Dosimeter still failing
[47°09′23″S, 126°43′35″W] Dosimeter still failing
[47°09′07″S, 126°43′30″W] Transponder still failing – switching to analog communication
[47°09′59″S, 126°43′15″W] Transponder still failing
[47°09′55″S, 126°43′12″W] Dosimeter still failing
[47°09′45″S, 126°43′01″W] Transponder still failing – switching to analog communication
Question to all you Gophers out there: How do you deal with custom errors that include more information and different kinds of matching them?
I started with a simple var ErrPermissionNotAllowed = errors.New("permission not allowed"). In my function I then wrap that using fmt.Errorf("%w: %v", ErrPermissionNotAllowed, failedPermissions). I can match this error using errors.Is(err, ErrPermissionNotAllowed). So far so good.
Now for display purposes I’d also like to access the individual permissions that could not be assigned. Parsing the error message is obviously not an option. So I thought, I create a custom error type, e.g. type PermissionNotAllowedError []Permission and give it some func (e PermissionNotAllowedError) Error() string { return fmt.Sprintf("permission not allowed: %v", e) }. My function would then return this error instead: PermissionNotAllowedError{failedPermissions}
At some layers I don’t care about the exact permissions that failed, but at others I do, at least when accessing them. A custom func (e PermissionNotAllowedError) Is(target err) bool could match both the general ErrPermissionNotAllowed as well as the PermissionNotAllowedError. Same with As(…). For testing purposes the PermissionNotAllowedError would then also try to match the included permissions, so assertions in tests would work nicely. But having two different errors for different matching seems not very elegant at all.
Did you ever encounter this scenario before? How did you address this? Is my thinking flawed?
[47°09′25″S, 126°43′02″W] Transponder still failing – switching to analog communication
[47°09′56″S, 126°43′56″W] Transponder still failing – switching to analog communication
[47°09′42″S, 126°43′01″W] Transponder still failing
[47°09′47″S, 126°43′00″W] Transponder still failing – switching to analog communication
[47°09′11″S, 126°43′25″W] Transponder still failing
[47°09′17″S, 126°43′04″W] Dosimeter still failing
[47°09′10″S, 126°43′13″W] Transponder still failing
[47°09′36″S, 126°43′12″W] Dosimeter still failing
[47°09′19″S, 126°43′35″W] Transponder still failing – switching to analog communication
@prologic@twtxt.net Yeah, we had some discussion about it once it was announced. I said what I felt (And I do love VR - but for flight simulators etc) - but I just knew it would fail.
Especially when they showed the ridiculous screenshots that they where so proud of with the quality of 15 years ago.
And they they pushed it as a place to work or have meetings during the pandemic.. haha.
And they did not even use it themselves in the company.
[47°09′17″S, 126°43′47″W] Transponder still failing – switching to analog communication
[47°09′33″S, 126°43′02″W] Dosimeter still failing
[47°09′44″S, 126°43′29″W] Dosimeter still failing
[47°09′48″S, 126°43′35″W] Transponder still failing – switching to analog communication
[47°09′35″S, 126°43′54″W] Dosimeter still failing
[47°09′47″S, 126°43′34″W] Transponder still failing – switching to analog communication
[47°09′42″S, 126°43′30″W] Dosimeter still failing
[47°09′19″S, 126°43′12″W] Transponder still failing
Why is Firefox called Firefox?
A story of bullying, and failing to see if a product name is in use before choosing it. ⌘ Read more
[47°09′43″S, 126°43′06″W] Transponder still failing
@funbreaker@twtxt.net Could you pull the latest code and rebuild? I have added SSL verification now.
If it still fails I’ll make a twtxt account and look into it more.
@lyse@lyse.isobeef.org @prologic@twtxt.net it seems like the ssl verification works now, I enabled it - but also added another option as well that I now saw in the docs, and now it did not fail on my end (which it did before). I will add a ‘enable ssl verification’ checkbox (checked by default) so that those who do not need or want it for testing and such can disable it if they want.
[47°09′57″S, 126°43′11″W] Dosimeter still failing
[47°09′21″S, 126°43′56″W] Transponder still failing – switching to analog communication
[47°09′59″S, 126°43′48″W] Dosimeter still failing
[47°09′05″S, 126°43′31″W] Transponder still failing – switching to analog communication
Erlang Solutions: 5 Key Tech Priorities for Fintech Leaders in 2023
The fintech industry is a major disruptor. Each year, it impacts how consumers interact with financial companies and brings new and innovative means to meet ever-growing customer expectations and occupy market space.
As a business owner or executive in this space, you have no choice but to stay on top of your game to increase efficiency.
In simpler terms, if your business doesn’t scale, it could fail.
That mig … ⌘ Read more
[47°09′41″S, 126°43′15″W] Dosimeter still failing
SUSE CEO out effective immediately, replacement CEO not available until later.
A failed IPO, political attacks, and purchased “awards” are the legacy of the departing CEO of the oldest Linux company. ⌘ Read more
[47°09′21″S, 126°43′27″W] Dosimeter still failing
[47°09′00″S, 126°43′49″W] Transponder still failing – switching to analog communication
when the matryoshka swarm parts and opens like a manifold cat’s eye, that’s when you know your cloaking failed
[47°09′04″S, 126°43′59″W] Transponder still failing
[47°09′25″S, 126°43′28″W] Dosimeter still failing
@prologic@twtxt.net Thank you.
What I did was to just pull the latest, build deps and the server, then enable the features as you mention through command line, as soon as I add activitypub it fails with that error when it starts up.
[47°09′34″S, 126°43′29″W] Transponder still failing – switching to analog communication
[47°09′43″S, 126°43′12″W] Transponder still failing
[47°09′00″S, 126°43′02″W] Dosimeter still failing
[47°09′41″S, 126°43′33″W] Transponder still failing – switching to analog communication
[47°09′03″S, 126°43′43″W] Dosimeter still failing
[47°09′19″S, 126°43′12″W] Transponder still failing – switching to analog communication
@eldersnake@we.loveprivacy.club Several reasons:
- It’s another language to learn (SQL)
- It adds another dependency to your system
- It’s another failure mode (database blows up, scheme changes, indexs, etc)
- It increases security problems (now you have to worry about being SQL-safe)
And most of all, in my experience, it doesn’t actually solve any problems that a good key/value store can solve with good indexes and good data structures. I’m just no longer a fan, I used to use MySQL, SQLite, etc back in the day, these days, nope I wouldn’t even go anywhere near a database (for my own projects) if I can help it – It’s just another thing that can fail, another operational overhead.
[47°09′33″S, 126°43′41″W] Transponder still failing – switching to analog communication