From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ffmpeg-devel-bounces@ffmpeg.org> Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 6582345E56 for <ffmpegdev@gitmailbox.com>; Sun, 20 Apr 2025 20:37:28 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id DAF3E687D4B; Sun, 20 Apr 2025 23:37:22 +0300 (EEST) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9950B687BB0 for <ffmpeg-devel@ffmpeg.org>; Sun, 20 Apr 2025 23:37:16 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id DEECB439EA for <ffmpeg-devel@ffmpeg.org>; Sun, 20 Apr 2025 20:37:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1745181436; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BJZo4Txdv+hFvYwyOTDrECUaL60aQtXZp4rISUo8yyw=; b=Al9L2zbsxy4qNIpzd06jq07uvsl8Q4GYZ8Rsszx9RNonaExP936xBvEKqA6BBZjs5jaRt/ Z2T3mFs2gWoKGkPTZ2TZ+b3d4u9RLoYfBTBY4woIrB292IbNK6SyBTFzBPHPOVHGILrCFC lQ79B5AuON+XBB5nJeC4iXA6Z8BDhaEvxPlJlG9wRosoMONxNM4+BTr8YWuRUbC0hJoJ4G 2CsfzHaMYgtlqZDUwWUliiuKI9utymIMq5Sr+LNTLh9hLlMWX2F4E9j8iKATHLZAyQpPAW +SYIkYN0Hj2kCjAOy5H1SSICo/Eewis6dg/UWCQ4KT5qNaKC1OA+LHJBagAovw== Date: Sun, 20 Apr 2025 22:37:15 +0200 From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Message-ID: <20250420203715.GG4991@pb2> References: <pull.64.ffstaging.FFmpeg.1744470718.ffmpegagent@gmail.com> <fed846502d637bc6ecf9e1d27e71a1d8a2168868.1744470718.git.ffmpegagent@gmail.com> <20250416214809.GO4991@pb2> <DM8P223MB0365037EF5020C075A0CB7B3BABD2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> <20250416234031.GQ4991@pb2> <DM8P223MB0365E4A34BB172A57A33E798BABC2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> <20250419022833.GA4991@pb2> <DM8P223MB0365D8244A50A819B4F12B86BABE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> MIME-Version: 1.0 In-Reply-To: <DM8P223MB0365D8244A50A819B4F12B86BABE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> X-GND-State: clean X-GND-Score: -85 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvfeekledtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdduhedmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfpihgvuggvrhhmrgihvghruceomhhitghhrggvlhesnhhivgguvghrmhgrhigvrhdrtggtqeenucggtffrrghtthgvrhhnpefgjeffkeduffevvefgtdetudeitdehveduueevkedtudejudejudelvdfftdeiffenucffohhmrghinhepfhhfmhhpvghgrdhorhhgrdhishenucfkphepgedurdeiiedrieejrdduudefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepgedurdeiiedrieejrdduudefpdhhvghloheplhhotggrlhhhohhsthdpmhgrihhlfhhrohhmpehmihgthhgrvghlsehnihgvuggvrhhmrgihvghrrdgttgdpnhgspghrtghpthhtohepuddprhgtphhtthhopehffhhmphgvghdquggvvhgvlhesfhhfmhhpvghgrdhorhhg X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH 2/3] doc/dict2: Add doc and api change for AVDictionary2 X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org> List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe> List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel> List-Post: <mailto:ffmpeg-devel@ffmpeg.org> List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help> List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe> Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Content-Type: multipart/mixed; boundary="===============4760031893187045127==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org> Archived-At: <https://master.gitmailbox.com/ffmpegdev/20250420203715.GG4991@pb2/> List-Archive: <https://master.gitmailbox.com/ffmpegdev/> List-Post: <mailto:ffmpegdev@gitmailbox.com> --===============4760031893187045127== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IvgXpvYLrArD1PPG" Content-Disposition: inline --IvgXpvYLrArD1PPG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 19, 2025 at 01:43:26PM +0000, softworkz . wrote: >=20 >=20 > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Michael Niedermayer > > Sent: Samstag, 19. April 2025 04:29 > > To: FFmpeg development discussions and patches <ffmpeg- > > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] [PATCH 2/3] doc/dict2: Add doc and api > > change for AVDictionary2 > >=20 > > Hi > >=20 > > On Thu, Apr 17, 2025 at 10:38:32PM +0000, softworkz . wrote: > > > > > > > > > > -----Original Message----- > > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > [...] > > > > the LLM would probably mix and confuse things and hallucinate > > > > a lot of nonsense. > > > > > > That's less of a problem meanwhile as the available context > > > windows have increased and operating on trac ticket discussions > > > does not create such long conversations where the context > > > window overflows and important parts fall off. > > > Some care might only need to be taken for that it doesn't ingest > > > really large log outputs as are sometimes included in the tickets. > > > > > > At this time, it would be still too bold to let it work fully > > > autonomously, but that's not necessary because its > > > operations could be easily arbitrated by conventional logic. > > > > > > It could be controlled by a set of tags - something like: > > > > > > - tracbot-error > > > - tracbot-inconclusive > > > - tracbot-needs-manual-review > > > - tracbot-awaiting-user-response > > > - tracbot-reproduced-in-master > > > - tracbot-fixed-in-master > > > > > > Then, a scheduler service would run over all open issues and > > > invoke the AI on it (see below). > > > > > > The scheduler would exclude tickets which already have one of > > > those tags assigned. > > > Additionally, it would include tickets that are tagged with > > > "tracbot-awaiting-user-response" and have been updated since > > > the tag was assigned. > > > > > > > > > When the AI is invoked on a ticked, it has clear instructions > > > to follow. The primary directive is to reproduce the reported > > > issue. If the specified information is unclear or incomplete > > > or when no test file is provided, it posts a message, asking > > > for the missing information and applies the awaiting-user-response > > > tag. > > > > > > The AI would have an execution environment in a Docker > > > container where it has access to a library with daily builds > > > from the past 5 years. > > > If the issue doesn't reproduce with the latest daily build, > > > it adds the tracbot-fixed-in-master tag. > > > > > > If it can be reproduced with the latest build, it "bisects" > > > the issue using the daily binaries. > > > It adds a message like: "Issue reproducible since version > > > 20xx-xx-xx and the tag tracbot-reproduced-in-master > > > > > > If it can't make sense of it, or is platform-specific or > > > needs certain hardware, or errors, it adds one of the > > > other tags. > > > > > > Some safeguards must be added to avoid anybody getting > > > into a longer chat with it (always ending with > > > awaiting-user-response), but otherwise, I don't think > > > that there's much that can go wrong. > > > > > > A mailing list could be set up, to which it reports it > > > operations, and where interested members (or anybody) > > > can subscribe to. This would provide a kind of real-time > > > monitoring by the community. > > > > > > > > > All-in-all I think it's well doable. > > > > > > Unfortunately though, I cannot spend that much time. > > > Perhaps a candidate for GSoC? > >=20 > > GsoC would need a mentor and a student/contributor wanting to work on > > this. > > Also this would need someone (ideally either the mentor or > > contributor) > > willing to maintain it after GSoC > >=20 > > And it would not surprise me if its more work for us to do this in > > GSoC > > than just do it ourselfs. >=20 >=20 > Hi Michael, >=20 >=20 > yea, that's also one of the reasons why I'm not considering myself as a= =20 > good teacher: I use to think that I'll be able to get it done by myself > even before I'm done explaining to someone else. >=20 > The other day I had let the same setup like for the dictionary run on=20 > it, and it struggled, saying it cannot get past the "Anubis" bot=20 > protection on trac.ffmpeg.org. Is that right, do we have that kind of > protection for the trac server? yes, the server was attacked by AI bots, which ignored robots.txt and caused "stability/usability" issues > If yes, is there another way to access > the trac site via API? talk with timo but wget works here thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB In fact, the RIAA has been known to suggest that students drop out of college or go to community college in order to be able to afford settlements. -- The RIAA --IvgXpvYLrArD1PPG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCaAVa9wAKCRBhHseHBAsP q+mbAJ9Cz8sPnLxQu49+LUbNGyHIJKbsIgCfVJE8CQoJe4t9ukNFQ4QWsqNGhvM= =Q2vv -----END PGP SIGNATURE----- --IvgXpvYLrArD1PPG-- --===============4760031893187045127== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". --===============4760031893187045127==--