Если вы ищете место, где можно найти бесполезные, но весёлые посты, то канал "не лёха" идеально подходит для вас! Под названием "не лёха" скрывается уютное место, где можно насладиться юмором и загадками без какой-либо серьёзности. За каналом стоит пользователь с никнеймом @starkow, который обещает размещать только самые ненужные и интересные вещи. Вас ждут шутки, мемы, и прочие забавные материалы, которые проведут вас в мир веселья и безмятежности. Если вы хотите немного расслабиться и поднять себе настроение, присоединяйтесь к каналу "не лёха" и наслаждайтесь бесценным бесполезием вместе с @starkow!
06 Aug, 19:34
06 Aug, 10:26
01 Aug, 14:59
.ton.run
or .ton.website
like this:01 Aug, 14:49
30 Jul, 16:20
@sottovoxbot henlo my dear fren @starkow
in the group chat and click the button that appeared. that simple!29 Jul, 17:55
addDocuments
into your index
instance of the meilisearch (and update it every time any document is created/edited/deleted on the main database so both dbs are in sync), probably updateTypoTolerance
so you can search and accept a few typos and then simply index.search('hello')
!const index = meilisearch.index('messages')
const messages = [
{ global_id: 1, chat_id: 10, message_id: 1, from: { user_id: 1, first_name: 'John', last_name: 'Doe' }, text: 'Hello world!' },
{ global_id: 2, chat_id: 10, message_id: 2, from: { user_id: 2, first_name: 'Jane', last_name: 'Doe' }, text: 'Hi!' },
{ global_id: 3, chat_id: 10, message_id: 3, from: { user_id: 1, first_name: 'John', last_name: 'Doe' }, text: 'How are you?' },
...
]
const response = await index.addDocuments(messages, {
primaryKey: 'global_id'
})
const response = await index.search('hello', {
attributesToSearchOn: ['text'],
filter: 'from.user_id = 1 AND chat_id = 10'
})
06 Jul, 11:09
log.Fatal
(or even log.Panic
? is it called this way? i dont actually remember) multiple lines? e.g. your log line is so long it's better to split it up into two lines. so you would normally do something like this: log.Fatal('... this is the first line');but you would quickly see that your second line of logs would never be executed because of this non-explicit exiting behavior
log.Fatal('... this is the second line');
... expected (!) handling further ...
log.Fatal
indicating that os.Exit
is called under the hood". and what about those half of programmers that don't use IDEs and code editors that splash with a hint every now and then? this logic must be as simple as possible and as obvious as possible: log.Fatal
means log`ging on a `Fatal
error, nothing else. period. why the fuck does an os.Exit
call even happen? for what reason?Error
" — why should i use not what i wanted to use? why are there some assumptions what and whatnot to use? i want to use fatal logging level (of course you know about logging levels, right? right???) and that's all, i dont want a logger to unexpectedly exit my program because golang developers went nuts when creating this language06 Jul, 10:27
log.Fatal(...)
?! that's absurd to say the least!exitOnFatal: true
or something) 30 Jun, 17:06
30 Jun, 12:15
30 Jun, 12:14
winterfall.ton
, btw)https://nft.starkow.dev/img
and takes a input
query parameter and returns either a image/png
if input
is valid or a json describing what went wrong 23 Jun, 18:09
05 Apr, 23:05