no more paper stuff so rather some software where they have to type all the details into the computer
89 karma · joined November 9, 2017
no more paper stuff so rather some software where they have to type all the details into the computer
They could at least also publish it as a major version without the legacy layer
EDIT: I've just seen the reason described here: https://github.com/colinhacks/zod/issues/4371 TLDR: He doesn't want to trigger a "version bump avalanche" across the ecosystem. (Which I believe, wouldn't happen as they could still backport fixes and support the v3 for a time, as they do it right now)
https://docs.github.com/en/repositories/viewing-activity-and...
Maybe such a solution already exists, but I couldn't find it
Thought I'd give it a try and gave chatGPT 2 examples of existing tables and the corresponding TS types and asked it if it understood what it should do next. It explained the existing logic and also 2 edge cases hidden (e.g. if a type was boolean the column was UInt8 (to save 0/1))
Then I pasted all types in batches of 15 in and it generated with only 2-3 corrections needed, probably saving me around 1-2h of manual checking and/or creating. It understood that certain fields are non LowCardinality and therefore not used it.
Ryujinx did manage to create a build that also works very well on my M2, but hasn't been updated since half a year.
Still very impressive what they achieved already
When you used google/firebase deeplink[1] functionality it was copying a hash shortly before the deeplink, that was then pasted inside the app and could be used to link both web+app sessions together, which was really helpful.
[1] https://firebase.google.com/docs/dynamic-links/operating-sys...
So if you are going self-hosted, I can really recommend MailCow (https://mailcow.email/)
When he tried to forward these mails to the email address they provide for reporting spam, he got an automated mail delivery system email, that he was blocked from sending mails to that address...
The amount of wrong answers or just telling me something it has found on the web, which has nothing today with the topic is just annoying. Even basic questions seem to not work reliably and looking at the whole Alexa ecosystem it doesn't even feel close to "smart" home.
Lack of context awareness, connection to basic things like parcel delivery, washing machine and similar that would make my life a little easier (because I'm to lazy to open an app to look when my parcels will arrive or when the washing machine will finish) just ruin the whole thing for me.
Besides that, I've tried setting the male voice, but for some responses it just switches back to female Alexa??
Somewhat frustrating, but most of the times the issue was just that the apps were already compliant, but the reviewer on Apple/Google side was just not carefully checking
I have no other good examples for SSO than Grafana.
But something I would love to see more for logins are Application Tokens. We use Cloudflare Access for Team related logins, which will send such a token in the header, so the application can use it to authorize a user and by which group a user is in it can enable/disable features
https://developers.cloudflare.com/cloudflare-one/identity/au...
This solved our needs for multiple sign in options, as all is now managed through Cloudflare access, but this is obviously not a solution for everyone
We recently tried Signoz and Grafana Tempo and while I can't say something about uptrace yet (will definitely try it out) I want to list some pros and cons about them.
Grafana Tempo
Pros:
- Easy and smooth integration into our existing Grafana instance, no additional frontend needed
- No new storage engine needed (No additional Clickhouse, Postgres, etc) as it saves its data to S3
- Supports OTLP
Cons:
- Search is limited by param size and unique params (as its baked to be indexed)
- Ingestion is not in real time, but configurable (time to finish span)
Signoz:
Pros:
- Supports OTLP
- Integrates Logs and Metrics within the same service (for Grafana you need Loki then)
- Supports real time querying
Cons:
- Uses new storage engines (or extends the software stack) with adding ClickHouse
- Adds an additional frontend (might not be relevant for everyone)
- Doesn't provide SSO yet, so you need to manage users differently
Interesting to see, that UpTrace also chose ClickHouse (btw I love ClickHouse!)
Some questions:
- Can I easily disable certain features? (e.g. alerting)
- Is there support for SSO for self-hosted installation?
- Are there any recommendations for scaling (e.g. benchmarks) on how many spans/s are supported on what hardware?
Thanks in advance!
I remember trying the built-in batching but we had some trouble with it, so we just switched to <https://github.com/nikepan/clickhouse-bulk> which works without any issue since then.
Will have a look at the UIs listed there
- Super easy to setup - Easy to backup - Fast configuration (documentation could be better at some parts) - Similar SQL dialect as our devs use in MySQL
Only negative points I could find so far: - No 'good' management GUI as e.g. phpMyAdmin, pgAdmin, Mysql Workbench - Caching/Batching layers not directly implemented, but through external software
As we are a fairly small company all other analytical databases would have cost us a large amount of money/time more. Friends of us recently hired a group of data engineers/analytics who also brought all their AWS knowledge and toolings with them, which basically brought them to the same outcome as us, while we only have 5% of their costs and all our devs are able to either ingest or query some data
EDIT: Does anyone have some recommendations on what GUIs I could give our PMs to work with ClickHouse instead of writing queries? All SaaS I found didn't support ClickHouse yet or would cost us a newborn. Also what tools do your devs use when they work with ClickHouse data?
They will probably buy additional fuel before winter to prepare to run their generators in the times where electricity could be cut off.
Most of our devs were annoyed by some external toolings that supported Github but not Gitlab, Gitlab being slow or down, markdown rendering being terrible slow as well as almost all of the PR additions (e.g. eslint checks, test coverage reports etc) being in the top tiers (with pricings being out of scope for us).