bd808
Repos
141
Followers
96
Following
69

🌻 The collaborative editing software that runs Wikipedia. Mirror from https://gerrit.wikimedia.org/g/mediawiki/core. See https://mediawiki.org/wiki/Developer_access for contributing.

3363
1147

A few useful functions and objects for manipulating ip addresses in python.

69
17

YAML-1.1 parser and emitter

C
67
30

IRC bot framework using mixins to provide commonly desired functionality

9
1

Mirror of https://gerrit.wikimedia.org/g/wikimedia/toolhub See https://www.mediawiki.org/wiki/Developer_access for contributing

7
1

Github mirror of "labs/striker" - our actual code is hosted with Gerrit (please see https://www.mediawiki.org/wiki/Developer_access for contributing)

3
1

Events

bd808 delete branch work/bd808/gcc-Werror
Created at 1 day ago

yaml.c: Use PHP_FE_END macro

emit.c: fix -Wsign-compare

Use size_t for strlen to avoid sign-compare warning.

ci: Use -Werror

Make gcc report warnings as errors so that we don't miss them in code review.

Created at 1 day ago
pull request closed
ci: Use -Werror

Make gcc report warnings as errors after cleaning up a few pedantic warnings.

Created at 1 day ago
bd808 delete branch work/bd808/deliberate-error
Created at 1 day ago
pull request closed
[DO NOT MERGE] Test new warning matchers

Introduce a deliberate compiler warning (incompatible pointer type) to verify that the matchers report it.

Created at 1 day ago

ci: Use -Werror

Make gcc report warnings as errors so that we don't miss them in code review.

Created at 1 day ago

Fix -Wmissing-field-initializers warnings

Update initializers for various yaml_event_t and zval variables to eliminate missing-field-initializers warnings.

ci: Use -Werror & -Wextra

  • Make gcc report warnings as errors
  • Enable extra warnings
  • Disable unused-variable warning as PHP internals trigger it
Created at 1 day ago

emit.c: fix -Wsign-compare

Use size_t for strlen to avoid sign-compare warning.

parse.c: Fix unused-value warning

Use a (void)(X) call to disable an unused value warning in 'eval_scalar' for the callbacks argument which is deliberately unused, but still needed to match the signature of other functions.

Fix -Wmissing-field-initializers warnings

Update initializers for various yaml_event_t and zval variables to eliminate missing-field-initializers warnings.

ci: Use -Werror & -Wextra

  • Make gcc report warnings as errors
  • Enable extra warnings
Created at 1 day ago

yaml.c: Use PHP_FE_END macro

ci: Use -Werror & -Wextra

  • Make gcc report warnings as errors
  • Enable extra warnings
Created at 1 day ago
pull request opened
ci: Use -Werror & -Wextra
  • Make gcc report warnings as errors
  • Enable extra warnings
Created at 1 day ago
bd808 create branch work/bd808/gcc-Werror
Created at 1 day ago
pull request opened
[DO NOT MERGE] Test new warning matchers

Introduce a deliberate compiler warning (incompatible pointer type) to verify that the matchers report it.

Created at 1 day ago
bd808 create branch work/bd808/deliberate-error
Created at 1 day ago

ci: Add matcher for GCC errors & warnings

Add the ammaraskar/gcc-problem-matcher@master helper to add gcc error and warning messages as code review comments.

ci: Update problem matchers

  • Move gcc matcher to linux builds
  • Add msvc matcher for windows builds
Created at 1 day ago
bd808 delete branch work/bd808/compiler-problem-matchers
Created at 1 day ago

ci: Update problem matchers

  • Move gcc matcher to linux builds
  • Add msvc matcher for windows builds
Created at 1 day ago
pull request closed
ci: Update problem matchers
  • Move gcc matcher to linux builds
  • Add msvc matcher for windows builds
Created at 1 day ago
bd808 delete branch master
Created at 1 day ago
bd808 delete branch bd808-php-8.2
Created at 1 day ago
pull request opened
ci: Update problem matchers
  • Move gcc matcher to linux builds
  • Add msvc matcher for windows builds
Created at 1 day ago
bd808 create branch work/bd808/compiler-problem-matchers
Created at 1 day ago
bd808 delete branch work/bd808/gcc-matcher
Created at 1 day ago

ci: Add matcher for GCC errors & warnings

Add the ammaraskar/gcc-problem-matcher@master helper to add gcc error and warning messages as code review comments.

Created at 1 day ago
pull request closed
ci: Add matcher for GCC errors & warnings

Add the ammaraskar/gcc-problem-matcher@master helper to add gcc error and warning messages as code review comments.

Created at 1 day ago
pull request opened
ci: Add matcher for GCC errors & warnings

Add the ammaraskar/gcc-problem-matcher@master helper to add gcc error and warning messages as code review comments.

Created at 1 day ago
bd808 create branch work/bd808/gcc-matcher
Created at 1 day ago

ci: update test PHP versions

Drop old 7.x versions and add a few new 8.x ones.

Created at 1 day ago
started
Created at 5 days ago
issue comment
Unable to use .env to set passwords etc.

@lindhe Have you declared the envvars that your .env file would populate in your docker-compose.yaml? That would typically look something like:

version: '3.7'
services:
  matterbridge:
    image: 42wim/matterbridge:stable
    restart: unless-stopped
    environment:
    - MATTERBRIDGE_IRC_TGBOT_PASSWORD
    - MATTERBRIDGE_TELEGRAM_MYIRC_TOKEN
    volumes:
    - ./matterbridge.toml:/etc/matterbridge/matterbridge.toml:ro
Created at 2 weeks ago
opened issue
Configurable message queueing and rate limit for Telegram groups

Is your feature request related to a problem? Please describe. time="2023-03-15T19:45:33Z" level=error msg="SendMessage failed: Too Many Requests: retry after 9" func=handleMessage file="gateway/handlers.go:228" prefix=gateway https://phabricator.wikimedia.org/T332226

Telegram groups can be set to slow mode to rate limit each member's posts. Currently when matterbridge exceeds the rate limit it will log an error message and continue on. This causes data loss on the Telegram view of the chat.

Describe the solution you'd like A perfect world solution would adaptively respond to the upstream rate limit. Per https://github.com/tdlib/telegram-bot-api/issues/75 this sounds like a complex problem, but the limit (if any exists) is returned by the getChat API endpoint response.

A less complex solution would be implementing the equivalent of the IRC client's MessageQueue and MessageDelay flood control settings. Ideally these would be configurable per-gateway.

Describe alternatives you've considered A workaround for this issue is to grant the Telegram account used by the gateway an administrator role in the Telegram group. No explicit permissions are needed for the role to bypass the rate limit, so it can be configured with all available "what can this admin do?" toggles turned off to limit the mischief the account might be used for.

Created at 2 weeks ago