Giter Club home page Giter Club logo

pyrogram's Introduction

Contact me

Telegram Visitors

Quick stats about me

Github Stats Top Languages
KurimuzonAkuma's github stats KurimuzonAkuma's top languages

pyrogram's People

Contributors

1pyxa1 avatar alissonlauffer avatar aliwoto avatar bakatrouble avatar colinshark avatar cometovart avatar customicon avatar cyanbook avatar danipulok avatar delivrance avatar furoin avatar jonatan1609 avatar josxa avatar kalmengr avatar kurimuzonakuma avatar mahesh0253 avatar mendelmaleh avatar mrnaif2018 avatar null-nick avatar octonezd avatar omg-xtao avatar princic-1837592 avatar ripeey avatar shivangkakkar avatar smartmanoj avatar spechide avatar sunda001 avatar teriks avatar trenoduro avatar yoilyl avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

pyrogram's Issues

Quotes disappear if you edit message

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

If you add quote to message and then edit it - quote will disappear

Steps to reproduce

  1. Try to edit message, add quote into it
  2. Edit it again, just add some text into already existing text, quote will disappear

Code example

message.edit(text=">" + "quote" + "\n" + message.text)
message.edit(text=message.text + "something")

Logs

No response

Error on get_chat caused by pinned messages

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

I found a single chat where the pinned messages has, for some reason unknown to me, a wrong id.

The problem is that, for that reason I'm unable to interact with the chat. It is possible to use a try except block for the pinned message retrieval?

Steps to reproduce

I simply get this error using the get chat on a chat called "vezzoblog". Up until now it's the only chat i had this problem

Code example

from pyrogram import Client

app=Client(...)

with app:
        app.get_chat("vezzoblog")

Logs

Traceback (most recent call last):
  File "mydir/test_pyrogram.py", line 56, in <module>
    app.get_chat("vezzoblog")
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/sync.py", line 66, in async_to_sync_wrap
    return loop.run_until_complete(coroutine)
  File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/methods/chats/get_chat.py", line 87, in get_chat
    return await types.Chat._parse_full(self, r)
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/types/user_and_chats/chat.py", line 511, in _parse_full
    parsed_chat.pinned_message = await client.get_messages(
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/methods/messages/get_messages.py", line 117, in get_messages
    messages = await utils.parse_messages(self, r, replies=replies)
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/utils.py", line 155, in parse_messages
    reply_messages = await client.get_messages(
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/methods/messages/get_messages.py", line 115, in get_messages
    r = await self.invoke(rpc, sleep_threshold=-1)
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/methods/advanced/invoke.py", line 94, in invoke
    r = await session.invoke(
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/session/session.py", line 367, in send
    RPCError.raise_it(result, type(data))
  File "/.cache/pypoetry/virtualenvs/envname/lib/python3.10/site-packages/pyrogram/errors/rpc_error.py", line 91, in raise_it
    raise getattr(
pyrogram.errors.exceptions.bad_request_400.MessageIdsEmpty: Telegram says: [400 MESSAGE_IDS_EMPTY] - The requested message doesn't exist or you provided no message id (caused by "channels.GetMessages")

download_media(), the file size equals to 0 B

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

When downloading photo or video, sometimes some files have a size of 0 or are incomplete after downloading.

Steps to reproduce

download photos, some photo is 0 size.
image

Code example

file = await app.download_media(msg, file_name=filename_temp, progress=progress, progress_args=(download_msg,))

Logs

[10] Retrying "upload.GetFile" due to: Request timed out
Request timed out
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/client.py", line 971, in get_file
    r = await session.invoke(
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
    return await self.invoke(query, retries - 1, timeout)
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
    return await self.invoke(query, retries - 1, timeout)
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
    return await self.invoke(query, retries - 1, timeout)
  [Previous line repeated 7 more times]
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 412, in invoke
    raise e from None
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 361, in send
    raise TimeoutError("Request timed out")
TimeoutError: Request timed out

Question about get_media_group

Checklist

  • I believe the idea is awesome and would benefit the framework
  • I have searched in the issue tracker for similar requests, including closed ones

Description

In get_media_group.py, a -9 to +10 offset has been set to search media belonging to the same group. But when forwarding a batch of media groups at the same time, each media will come in with different order.

For example, I found a media group that includes these IDs: 466 468 472 476 479, so apparently +10 is not enough. Both Telegram PC and mobile can handle them well, but copy_media_group may fail if the first or the last ID has been used.

Do we have any better option other than to increase the offset?

Ответ в бизнес чате

Checklist

  • I believe the idea is awesome and would benefit the framework
  • I have searched in the issue tracker for similar requests, including closed ones

Description

Здравствуйте. Увидел что у вас реализован функционал для бизнес чатов, но ни как не могу понтять как реализовать ответ бота в бизнес чате на подобие такого?

@app.on_message()
async def echo(client, message):
    await client.send_message(
        chat_id=message.chat.id,
        text="Привет от бота!"
    )

Спасибо если сможете помочь.

Listen and ask feature

Checklist

  • I believe the idea is awesome and would benefit the framework
  • I have searched in the issue tracker for similar requests, including closed ones

Description

it would be nice if there was a feature to listen and ask for messages like in pyrofork and pyromod

send_media_group() send video without sound run error

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

when use send_media_group() send send video without sound, it run error.

Steps to reproduce

Traceback (most recent call last):
File "C:\demo\test\test.py", line 20, in
app.send_media_group(
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\sync.py", line 66, in async_to_sync_wrap
return loop.run_until_complete(coroutine)
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 646, in run_until_complete
return future.result()
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\methods\messages\send_media_group.py", line 450, in send_media_group
r = await self.invoke(
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\methods\advanced\invoke.py", line 94, in invoke
r = await session.invoke(
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\session\session.py", line 399, in invoke
return await self.send(query, timeout=timeout)
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\session\session.py", line 367, in send
RPCError.raise_it(result, type(data))
File "C:\Users\HC\AppData\Local\Programs\Python\Python310\lib\site-packages\pyrogram\errors\rpc_error.py", line 91, in raise_it
raise getattr(
pyrogram.errors.exceptions.bad_request_400.MediaEmpty: Telegram says: [400 MEDIA_EMPTY] - The media you tried to send is invalid (caused by "messages.SendMultiMedia")

Code example

app.send_media_group(
    xxxxxx,
    [
        InputMediaVideo("no sound.mp4", caption="video without sound"),
        InputMediaVideo("sound.mp4")
    ]
)

Logs

No response

Change the docs from pyrogram to yours

Checklist

  • I believe the idea is awesome and would benefit the framework
  • I have searched in the issue tracker for similar requests, including closed ones

Description

Hi, i saw you have your own docs for your fork
it will be great if you link your own docs instead of pyrogram docs in readme
Thanks for keeping pyrogram alive

SendScreenshotNotification not working

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

On the official version of pyrogram (2.0.106), the notification for sending screenshots worked.
Doesn't work on your fork (2.1.16)

Steps to reproduce

client.invoke(SendScreenshotNotification(
	  peer=client.resolve_peer(message.chat.id),
	  reply_to_msg_id=message.id,
	  random_id=app.rnd_id()
))
TypeError: SendScreenshotNotification.__init__() got an unexpected keyword argument 'reply_to_msg_id'

I tried changing the attribute name:

client.invoke(SendScreenshotNotification(
	  peer=client.resolve_peer(message.chat.id),
	  reply_to=message.id,
	  random_id=app.rnd_id()
))
File "pyrogram\raw\functions\messages\send_screenshot_notification.py", line 84, in write
  b.write(self.reply_to.write())
          ^^^^^^^^^^^^^^^^^^^
AttributeError: 'int' object has no attribute 'write'

But it still doesn't work

Code example

No response

Logs

No response

Auto restart return an Exception

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

The auto restart fails and bot stopped working.

Steps to reproduce

Make the bot having connection error and throwing OSError.

Code example

No response

Logs

Task exception was never retrieved
future: <Task finished name='Task-218707' coro=<Session.restart() done, defined at /usr/local/lib/python3.9/site-packages/pyrogram/session/session.py:183> exception=RuntimeError('read() called while another coroutine is already waiting for incoming data')>

where i can find docs ?

Checklist

  • I believe the idea is awesome and would benefit the framework
  • I have searched in the issue tracker for similar requests, including closed ones

Description

where i can find docs ?
kurigram d`not have any docs ?

[420 FLOOD_PREMIUM_WAIT_X] While Uploading video

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

I am trying to upload video but i am getting lots of [420 FLOOD_PREMIUM_WAIT_X] message, terminal getting full, so its difficult to check output.

Steps to reproduce

If i use progress_callback then only this spamming messages showing.
I just want to hide spam with using progress_callback

Code example

client.send_video(chat_id=username, reply_to_message_id=forum_id, video=video_path, caption=caption, progress=progress_callback, thumb=thumbnail_path, duration=int(duration), supports_streaming=True)

Logs

  0% 0.00/126M [00:00<?, ?B/s]Telegram says: [420 FLOOD_PREMIUM_WAIT_X] - A wait of 12 seconds is required (caused by "upload.SaveBigFilePart")
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/pyrogram/methods/advanced/save_file.py", line 109, in worker
    await session.invoke(data)
  File "/usr/local/lib/python3.10/dist-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/usr/local/lib/python3.10/dist-packages/pyrogram/session/session.py", line 367, in send
    RPCError.raise_it(result, type(data))
  File "/usr/local/lib/python3.10/dist-packages/pyrogram/errors/rpc_error.py", line 91, in raise_it
    raise getattr(
pyrogram.errors.exceptions.flood_420.FloodPremiumWait: Telegram says: [420 FLOOD_PREMIUM_WAIT_X] - A wait of 12 seconds is required (caused by "upload.SaveBigFilePart")

flooding error not supported for getStoriesById

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

I am downloading all the messages from a chat and i get this error. I think it's just missing an error handling on getSetoriesById

Steps to reproduce

I get this error using the get_chat_history method on a couple of chats. You can try on "BlogBeloso" to test this

Code example

from pyrogram import Client

app=Client(...)

with app:
    c=app.get_chat("BlogBeloso")
    for m in app.get_chat_history(c.id):
        print(m)

Logs

Traceback (most recent call last):
  File "/codedir/file1.py", line 79, in download_chat
    ) = await c.dump_all_messages_from_chat(
  File "/codedir/file2.py", line 92, in dump_all_messages_from_chat
    async for m in app.get_chat_history(target_id):
  File "/envdir/lib/python3.10/site-packages/pyrogram/methods/messages/get_chat_history.py", line 111, in get_chat_history
    messages = await get_chunk(
  File "/envdir/lib/python3.10/site-packages/pyrogram/methods/messages/get_chat_history.py", line 51, in get_chunk
    return await utils.parse_messages(client, messages, replies=0)
  File "/envdir/lib/python3.10/site-packages/pyrogram/utils.py", line 111, in parse_messages
    await types.Message._parse(
  File "/envdir/lib/python3.10/site-packages/pyrogram/types/messages_and_media/message.py", line 931, in _parse
    story = await client.get_stories(utils.get_peer_id(media.peer), media.id)
  File "/envdir/lib/python3.10/site-packages/pyrogram/methods/stories/get_stories.py", line 63, in get_stories
    r = await self.invoke(
  File "/envdir/lib/python3.10/site-packages/pyrogram/methods/advanced/invoke.py", line 94, in invoke
    r = await session.invoke(
  File "/envdir/lib/python3.10/site-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/envdir/lib/python3.10/site-packages/pyrogram/session/session.py", line 367, in send
    RPCError.raise_it(result, type(data))
  File "/envdir/lib/python3.10/site-packages/pyrogram/errors/rpc_error.py", line 91, in raise_it
    raise getattr(
pyrogram.errors.exceptions.flood_420.FloodWait: Telegram says: [420 FLOOD_WAIT_X] - A wait of 41 seconds is required (caused by "stories.GetStoriesByID")

The file id contains an expired file reference

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

app.download_media(message, file_name=filename)
some time it run error

pyrogram.errors.exceptions.bad_request_400.FileReferenceExpired: Telegram says: [400 FILE_REFERENCE_EXPIRED] - The file id contains an expired file reference, you must obtain a valid one by fetching the message from the origin context (caused by "upload.GetFile")

It may be because the download time is too long or there is a flood waiting. Can you automatically re-read the message and try to download?

Steps to reproduce

app.download_media(message, file_name=filename) show The file id contains an expired file reference

Code example

app.download_media(message, file_name=filename)

Logs

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/client.py", line 1007, in get_file
    r = await session.invoke(
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 367, in send
    RPCError.raise_it(result, type(data))
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/errors/rpc_error.py", line 91, in raise_it
    raise getattr(
pyrogram.errors.exceptions.bad_request_400.FileReferenceExpired: Telegram says: [400 FILE_REFERENCE_EXPIRED] - The file id contains an expired file reference, you must obtain a valid one by fetching the message from the origin context (caused by "upload.GetFile")

FLOOD_PREMIUM_WAIT_7

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

have set client sleep_threshold=89000
downloading media, the program is suddenly interrupted.
show FLOOD_PREMIUM_WAIT_7, and the downloaded file size is 0

Steps to reproduce

msg = await tiqu_user_app.get_messages(chat_id=msg.chat.id, message_ids=msg.id)
file = await tiqu_user_app.download_media(msg, file_name=filename_temp, progress=progress, progress_args=(download_msg, f"{len(msgs)}-{i+1}",))

the message is belong to media_group.

Code example

No response

Logs

Telegram says: [420 Flood] - [420 FLOOD_PREMIUM_WAIT_7] (caused by "upload.GetFile")
Traceback (most recent call last):
  File "my_bot.py", line 1899, in get_muilt_msg
    raise ChatForwardsRestricted
pyrogram.errors.exceptions.bad_request_400.ChatForwardsRestricted: Telegram says: [400 CHAT_FORWARDS_RESTRICTED] - The chat restricts forwarding content 

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/client.py", line 1007, in get_file
    r = await session.invoke(
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 399, in invoke
    return await self.send(query, timeout=timeout)
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 367, in send
    RPCError.raise_it(result, type(data))
  File "/usr/local/lib/python3.8/dist-packages/pyrogram/errors/rpc_error.py", line 80, in raise_it
    raise getattr(
pyrogram.errors.exceptions.flood_420.Flood: Telegram says: [420 Flood] - [420 FLOOD_PREMIUM_WAIT_7] (caused by "upload.GetFile")

showt he handler has been closed when running

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

showt he handler has been closed when running

Steps to reproduce

[10] Retrying "channels.GetChannels" due to: unable to perform operation on <TCPTransport closed=True reading=False 0x5b8fdc0>; the handler is closed
Task exception was never retrieved
future: <Task finished name='Task-2018290' coro=<Client.handle_updates() done, defined at /usr/local/lib/python3.8/dist-packages/pyrogram/client.py:582> exception=OSError(RuntimeError('unable to perform operation on <TCPTransport closed=True reading=False 0x5b8fdc0>; the handler is closed'))>
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/pyrogram/client.py", line 627, in handle_updates
channel=await self.resolve_peer(utils.get_channel_id(channel_id)),
File "/usr/local/lib/python3.8/dist-packages/pyrogram/methods/advanced/resolve_peer.py", line 111, in resolve_peer
await self.invoke(
File "/usr/local/lib/python3.8/dist-packages/pyrogram/methods/advanced/invoke.py", line 94, in invoke
r = await session.invoke(
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
return await self.invoke(query, retries - 1, timeout)
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
return await self.invoke(query, retries - 1, timeout)
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 422, in invoke
return await self.invoke(query, retries - 1, timeout)
[Previous line repeated 7 more times]
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 412, in invoke
raise e from None
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 399, in invoke
return await self.send(query, timeout=timeout)
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 350, in send
raise e
File "/usr/local/lib/python3.8/dist-packages/pyrogram/session/session.py", line 347, in send
await self.connection.send(payload)
File "/usr/local/lib/python3.8/dist-packages/pyrogram/connection/connection.py", line 69, in send
await self.protocol.send(data)
File "/usr/local/lib/python3.8/dist-packages/pyrogram/connection/transport/tcp/tcp_abridged.py", line 38, in send
await super().send(
File "/usr/local/lib/python3.8/dist-packages/pyrogram/connection/transport/tcp/tcp.py", line 104, in send
raise OSError(e)
OSError: unable to perform operation on <TCPTransport closed=True reading=False 0x5b8fdc0>; the handler is closed

Code example

No response

Logs

No response

MessageActionChatJoinedByRequest is not marked as a service message

Checklist

  • I am sure the error is coming from Pyrogram's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

The MessageActionChatJoinedByRequest is not marked as a service message in the filters.service filters

Steps to reproduce

add it to the enum message and filters.service and add it to the filters.service

image of the message
image

Code example

No response

Logs

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.