@GoibiboSupport this is still unresolved . ive only recived refund from goibibo. not from @OfficialStarAir this flight was for first week of december still no refund.
@GoibiboSupport i have been trying to contact the support team for quiet a few days now. no way to reach you guys. ill soon be filing a consumer court complaint. my star air flight was canncelled . but this shows that i have canceled my flight. i was trying to request refund!
@GoibiboSupport pl try to close this asap. ive been waiting for the resolution for more than a month everytime u ask for 48hrs then 7 days then again 48 hrs and then close the tickets.
@GoibiboSupport i have been trying to contact the support team for quiet a few days now. no way to reach you guys. ill soon be filing a consumer court complaint. my star air flight was canncelled . but this shows that i have canceled my flight. i was trying to request refund!
@TheJupiterApp i have been unable to activate upi on my phone for past 2 months. i get the otp it auto fills and then error.
there been 0 help from your support
Web3 devs! Crush it with me on Alchemy - the ultimate platform for web3 development. Use my link to get $100 credits on the growth tier and start building your dapp. Join now: https://t.co/z9xWkOARaA
#poweredByAlchemy
CSS Trick ⭐️
You can create a resizable panel UI with CSS alone by leaning into resize and display:grid 👀
.panels{
display: grid;
grid-template-columns: auto 1fr; 👈
}
.resizer{
max-width: 100cqi;
overflow: hidden;
resize: horizontal; 👈
}
Putting a resizable element into the first panel provides a way to resize the layout as we're using "auto 1fr". You could also do this with other layout techniques but grid was the first that came to me 😅
But, the issue with resize is you can't style the teeny tiny little handle the browser provides... 🤦♂️ So, a trick for that is to scale the resizable element up and then clip the part we don't need 😯
.resizer {
height: 48px;
transform-origin: 100% 100%;
scale: 4;
clip-path: inset(calc(100% - 12px) 0 0 calc(100% - 12px));
}
And that gives you a slightly better hit spot for the resize handle plus the ability to move it around 🙌
It's not perfect by any means. It does raise the question of how hard would it be to implement support for styling the resize handle in the browser?
@CodePen link below! 👇
If you're still new to @PostgreSQL, here are some useful info bits from me:
1) tuples are physical versions of rows; you can start understanding them by selecting hidden columns ctid, xmin, xmax (all tables have them); start looking at this as early as possible, and later you won't be surprised by slow massive DELETE not reclaiming disk space, autovacuum, and bloat issues.
2) always use BUFFERS checking EXPLAIN ANALYZE – the right command is EXPLAIN (ANALYZE, BUFFERS)
3) throw away pgAdmin – stick with tmux&psql or, if you do need UI, use DBeaver or DataGrip or Postico (but still learn psql-fu, it will pay off)
4) enable as much logging as you can afford: log_checkpoints = 0, log_autovacuum_min_duration = 0, log_temp_files = 0, log_lock_waits = on, and as low non-negative log_min_duration_statement as you can afford – say, 200ms (watch out observer effect caused by too much logging though)
5) install pg_stat_statements – it's a must; and if you can install pg_stat_kcache and pg_wait_sampling (or pgsentinel) and auto_explain (these guys require a few decisions on settings though)
6) use thin cloning and branching @Database_Lab to develop and test (and yes, ChatGPT can be helpful, but it often has hallucinations, so always check it)
7) make sure data checksums are enabled
8) tune autovacuum to run frequently and move faster
9) query optimization will eventually be more important than configuration tuning, and more often needed – tune .conf "well enough" and then focus on continuous use of pg_stat_statements and EXPLAIN (ANALYZE, BUFFERS)
10) indexes need to be rebuilt, unfortunately, since their health decline over time – even in PG14+ with well-tuned autovacuum; prepare for that, better do it in an automated way; and clean up unused and redundant ones regularly