there were a lot of events recorded by gharchive.org of which 2,068,058 were push events containing 3,421,678 commit messages that amount to 271,761,736 characters filtered with words.py@e23d022007... to these 48 messages:
New XP UIs, many misc tweaks
UI:
Added new options to the Player Menu, including an XP bar and a constant display for Rested XP. These have various configuration options and can be moved around, with the settings persisting across all characters. Fixed the player info UI issues at 1.0x UI scaling. Fixed the player info toggler sometimes not working when multiple players are logged in. Fixed being able to escape Divine Elegance with the appearance editor open if you made sure another UI was the last to recieve an event every time you wanted to enter another area with it. PC Player menu visibility is now toggled for all characters on your account.
Adventurers:
Significantly increased the power of random (area event spawned) adventurer parties. Upon attacking, these parties now also get a name change. Increased the chance of the fun rest ambush surprise to from 2% to 3%. The difficulty of the fun rest ambush surprise now increases if you have more party members. Its difficulty for a lone character should be about the same as it was before. Increased the odds of Weapon Finesse for random adventurers who would gain more than 2AB from it. Made assorted improvements to random Adventurer builds. Made various improvements to random equipment logic, most notably weapon finesse users should no longer find themselves with non-finessable 2h weapons. Adventurers should now have infinite ammunition.
Other:
Fix towards inactive henchmen standing inactive over player corpses while being attacked. Fix towards safe rest waypoints not functioning. Fixed Dahanna restarting conversation mid-combat if you go in and out of view after starting fighting her. Fixed a typo in Sindra's dialogue. Treasure maps can now be viewed in combat. Added a default password to running the development server, because otherwise there wasn't one and you couldn't use DM mode there any more. Disabled the ground weapon spawns in animated weapon room of the Isle of the Maker's floor. These were probably too lucrative anyway, and when players could farm them without a henchman splitting loot this was likely way too good a moneymaker. Corrected the TLK override for Greater Magic Weapon (previously the spell's name was being overwritten with the new description) Aawill's conversation now offers to take you to the dryad upon pacifying the Spirit of the Wood, in an effort to reduce backtracking. Stone and Clay Golems in the Isle of the Maker are no longer flagged semibosses, which made them provide more loot, xp, gold and treasure maps than intended. It is no longer possible to repeatedly attempt Gerrol's bluff check. Reduced the time interval between merchant restocks from 24h to 23h. Now if you want to shop at the same time every day you will see something new, rather than having to slowly let shopping time creep forward. Resting with >95% of possible Rested XP no longer produces the message about benefitting from sleeping at home. Loot bags that contain quest items will now always be "big". Lootable objects now change highlight colour (to a darker shade) once opened, so you can more easily see if you have missed something at a glance. Treasure map loot containers should no longer have items lurking on pages 2+ that would fit on page 1. The Spirit of the Wood's area should now refresh properly. Bran and Geth now truly spawn and despawn on time changes (rather than being invisible, which would make henchmen and other creatures attack something players couldn't see). Bran is no longer hostile to bears, which would tend to attack and kill him. Moved some rubble in the Goblin Cave that seemed to be causing pathfinding problems. Deprecated Unstucker and Stone of Recall, the PC Actions panel can now do these functions.
ok, holy shit, I figured out how to sketch in 3 dimensions..sort-of
This commit adds a sloped plane that runs from the previously flat rooftop floor up to a ridgeline that was floating 1 meters above it, straddling the center.
Well, it's just a triangle for now because it was easier than an arch. I'll do the arch next.
Basically the way this worked is that I took my existing sketch of the roottop floorplan on the xy plane, then I created a new sketch that hovered a single ridgeline above that one, also on the xy plane. Note that you can tie a new sketch to another sketch by using the "Create an edge linked to an existing geometry" button.
At this point, the new sketch on the xy plane had just one line sitting at the origin. SO I just changed the z-position of the new sketch so that it was 1 meter above the roof floor sketch.
Finally, I switched to draft tool and (using the end-line-snap), I was able to sketch this new plane that does exactly what I want across all three dimensions. Awesome!
Slightly Damned
Previously it worked just fine without any rules, but the site has been updated since. So capture rules have been added.
Note about Girl Genius semi post-mortem: For the most part it looks like it's fine. There are a few oddities here and there, but they don't ruin the read through of the archive... that I know of. Chances are new issues will arise the next time I read through the archive, but it'll likely be a while till that happens. Tend to reread it every other year.
Padding Info Update: So far I haven't ran into too much in terms of issues. Though some sites have issues on mobile, that is kinda unrelated to it, especially portrait mode, where the comic will go off to the sides of the page and not be scrollable left or right to view. They also tend to be really large images. I want to count this towards the mobile platforms themselves, since the only reason that should be occurring is if the browser thinks the screen is wider than it is, or something. Something I'll look into a bit more.
Now if you excuse me, I'm gonna reread through slightly damned and a webtoon comic or two.
performance: don't compile on hover on dev (#51830)
An annoying issue that slows down compilation times in dev for Next is that we might trigger compilation of a page via hover on app.
We do this because we want the same experience in production and dev and the prefetching is important for instantaneous loading states.
The alternative in this PR is that we don't prefetch at all anymore in dev but instead, when we handle navigation, we can force a prefetch navigation.
The slight compromise with this approach is that you can't test prefetching anymore in dev.
link NEXT-1317
the pinnacle of music
Come light the fuse, he's a rocket, and he's ready to go 'Cause now the count down has started and he's ready to blow He's got the the dope sounds pumpin' in his stereo(-eo) Kicking ass fast, putting on a show Come on and get yourself together, there's no time to rest And if you put the time in, he'll put you to the test He's like a running man, in his world, more is less And if you wanna test him best bring your best You can't stop now, lock and load Don't stop now, come on and rock and roll! In this world (His world- Gotta make your own way!) Where one is all In this world (His world- Life is just a game you play!) Never fear the fall When you leap without a net you'll find It won't be there all the time So watch your step, now watch you step don't fall! Running in back again, well what'd ya expect? Coming at ya with ten outta ten, gotta real rough neck Slide something slippery, straps on his shoes 'Cause he's the best there ever was haven't ya heard the news? Go on and psych yourself up, 'cause it's time to play Bounce through to beats and the rhymes, 'cause they're here to stay The one and only marathon man, living the day Moving up, coming fast, and he'll blow you away! You can't stop now, lock and load Don't stop now, come on and rock and roll! In this world (Gotta make your own way!) Where one is all In this world (Life is just a game you play!) Never fear the fall When you leap without a net you'll find It won't be there all the time So watch your step, now watch you step don't fall! Intergalactic continental champ, running things Hyperactive instrumental ready, pulling strings He's just the one who understands when the tides will swing So he's breaking down doors, never following Because the pressures of this world, they can take their toll The only way to break free is to break the mould! You can't stop now, lock and load Don't stop now, come on and rock and roll! In this world (Gotta make your own way!) Where one is all In this world (Life is just a game you play!) Never fear the fall When you leap without a net you'll find It won't be there all the time So watch your step, now watch you step don't fall! In this world (Gotta make your own way!) Where one is all In this world (Life is just a game you play!) Never fear the fall When you leap without a net you'll find It won't be there all the time So watch your step, now watch you step don't fall! Watch your step, watch your step! Don't turn around! Watch your step, watch your step! Don't turn around! Just watch and look back again! Don't fall!
Merging in Web version changes.
randomizer.py:
- Wrapped the whole randomize process in a try/except block to pass exceptions back to GUI/Web
- Added support for custom coral names from web
- Added support for a custom playlist from web
- Added support for a custom passwords from web
appearance.py:
- Added support for custom coral names from web
- Added validation to ensure there are enough male and female names
musicinterface.py:
- Added support for a custom playlist from web
musicrandomizer.py:
- Reordered imports
- Added support for a custom playlist from web
- Made tierboss section check case-insensitive
options.py:
- Fixed an invalid default value for dancingmaduin
sillyclowns.py:
- Added support for a custom passwords from web
formationrandomizer.py:
- Import changes
appearance.py, dialoguemanager.py, esperrandomizer.py, itemrandomizer.py, locationrandomizer.py, monsterrandomizer.py, namerandomizer.py, randomizer.py, skillrandomizer.py, towerrandomizer.py, utils.py, wor.py:
- Cosmetic changes to variable names and/or spacing
Auto merge of #113108 - compiler-errors:normalize-opaques-with-late-bound-vars-again, r=jackh726
Normalize opaques with late-bound vars again
We have a hack in the compiler where if an opaque has escaping late-bound vars, we skip revealing it even though we could reveal it from a technical perspective. First of all, this is weird, since we really should be revealing all opaques in Reveal::All mode. Second of all, it causes subtle bugs (linked below).
I attempted to fix this in #100980, which was unfortunately reverted due to perf regressions on codebases that used really deeply nested futures in some interesting ways. The worst of which was #103423, which caused the project to hang on build. Another one was #104842, which was just a slow-down, but not a hang. I took some time afterwards to investigate how to rework normalize_erasing_regions to take advantage of better caching, but that effort kinda fizzled out (#104133).
However, recently, I was made aware of more bugs whose root cause is not revealing opaques during codegen. That made me want to fix this again -- in the process, interestingly, I took the the minimized example from rust-lang/rust#103423 (comment), and it doesn't seem to hang any more...
Thinking about this harder, there have been some changes to the way we lower and typecheck async futures that may have reduced the pathologically large number of outlives obligations (see description of #103423) that we were encountering when normalizing opaques with bound vars the last time around:
- #104321 (lower
async { .. }directly as a generator that implementsFuture, removing thefrom_generatorshim) - #104833 (removing an
identity_futurefn that was wrapping desugared future generators)
... so given that I can see:
- No significant regression on rust perf bot (rust-lang/rust#107620 (comment))
- No timeouts in crater run I did (rust-lang/rust#107620 (comment), rechecked failing crates in rust-lang/rust#107620 (comment))
... and given that this PR:
- Fixes #104601
- Fixes #107557
- Fixes #109464
- Allows us to remove a
DefiningAnchor::Bubblefrom codegen (75a8f681837c70051e0200a14f58ae07dbe58e66)
I'm inclined to give this another shot at landing this. Best case, it just works -- worst case, we get more examples to study how we need to improve the compiler to make this work.
r? types
Life is one big road with lots of signs. So when you riding through the ruts, don't complicate your mind. Flee from hate, mischief and jealousy. Don't bury your thoughts, put your vision to reality. Wake Up and Live!
Golem species pain modifier + (hopefully) fixes the stupid golem limb issue (#6400)
Probably fixes: #6291 fixes: #6304 fixes: #6319 fixes: #6332 fixes: #6345 fixes: #6346 fixes: #6367 fixes: #6385 fixes: #6442
🆑 Jolly balance: Golems are even more resilient to pain now. What the fuck did you expect from a walking heap of rock and stone? /🆑
Update Pyright version to latest (1.1.313) (#944)
Boy this was more painful than I expected. Lots of fighting with the compiler. I ended up disabling a few more Pyright issues, specifically these seemed more trouble than they're worth:
-
reportPrivateUsage: we do this often in the codebase, for example charm.py pokes at _ModelBackend stuff
-
reportUnnecessaryIsInstance: we do lots of isinstance checks to detect type issues at runtime (we've done this since the beginning, and it's useful for people not using type checking)
-
reportUnnecessaryComparison: similar to the above, but for checking "if non_optional_value is None" and the like
-
Fix issue with Pebble.exec and Container.exec types
Currently Pyright isn't (usually?) able to find the return type of Container.exec, I think due to an import ordering thing? As such, charms that use it get an Any type and static checks pass.
However, as soon as Pyright can find the return type, it's not really correct, and we get errors like shown below.
We need to use Generic[AnyStr] and various overloads to ensure the caller gets an ExecProcess[str] if they call exec() with "encoding" set (the default), or ExecProcess[bytes] if they call exec() with "encoding" set to None.
$ tox -e static-charm static-charm: commands[0]> pyright /home/ben/w/grafana-k8s-operator/src /home/ben/w/grafana-k8s-operator/src/charm.py /home/ben/w/grafana-k8s-operator/src/charm.py:929:28 - error: Argument of type "Literal['Version (\d*\.\d*\.\d*)']" cannot be assigned to parameter "pattern" of type "bytes | Pattern[bytes]" in function "search" Type "Literal['Version (\d*\.\d*\.\d*)']" cannot be assigned to type "bytes | Pattern[bytes]" "Literal['Version (\d*\.\d*\.\d*)']" is incompatible with "bytes" "Literal['Version (\d*\.\d*\.\d*)']" is incompatible with "Pattern[bytes]" (reportGeneralTypeIssues) /home/ben/w/grafana-k8s-operator/src/charm.py:929:56 - error: Argument of type "_StrOrBytes" cannot be assigned to parameter "string" of type "ReadableBuffer" in function "search" Type "_StrOrBytes" cannot be assigned to type "ReadableBuffer" Type "str" cannot be assigned to type "ReadableBuffer" "str" is incompatible with "ReadOnlyBuffer" "str" is incompatible with "bytearray" "str" is incompatible with "memoryview" "str" is incompatible with "array[Any]" "str" is incompatible with "mmap" "str" is incompatible with "_CData" ... (reportGeneralTypeIssues) 2 errors, 0 warnings, 0 informations
-
Remove now-unnecessary quotes around 'pebble.X' types
-
Comment out alertmanager-k8s-operator CI for now
Add ability to checkpoint a pipeline.
This change allows to query the running configuration of a pipeline. And we also allow to update the running configuration of a pipeline explicitly. So all the normal interactions with connectors, pipelines, and program objects act as a staging area which can be committed using the API to the running version of the pipeline.
This change has several components:
This is pretty straight forward: We add history tables for pipeline, program, attached_connectors, and connectors. The history table contains the same fields as the non-history counter-parts but we add a revision field and change the primary keys to be uuid+revision in those tables.
The history tables are immutable snapshots of the pipeline config. You see where this is going, whenever we need to commit a config. We go off and copy the pipeline row, the program row, all attached_connector and connector rows associated with the pipeline we want to version into the history table. We assign them a new revision for every version. And we're almost done with versioning stuff. Kind of...
Now we have all these versions, and each version has a
different binary, so we need to keep the binaries around.
That's a bit unfortunate, but this will go away again
once we have JIT. It also is kinda dumb because we don't
want to keep binaries for all versions we ever created.
So here is what we do:
Whenever we create a new program binary we version it
in a (new) binaries folder (in the dbsp workspace) using a
naming schema that is project_$uuid_$version. The reason
we version immediately and not say at commit time of a pipeline
is because the binary we used so far was just the binary directly
from the target dir of that project. But we don't really
know what state this binary is in, especially if we can have
commit and compile requests happening at the same
time. So in the same 'transaction' that builds the binary
we version it and copy it away. And the pipeline manager
only runs versioned binaries. We also need a way to clean
up binaries. That's also a bit silly because when is it safe to delete
a version of a binary? Well, it's only safe if no pipeline
has that program version as it's current, last revision.
And no pipeline descriptor that we haven't versioned yet
has that program/version as it's current program/version.
The way we deal with this is to have a GC task that
periodically wakes up and checks if binaries are orphans
and can be removed. The first design I tried was trying
to do this on-the-fly while we create new commits
but it seemed better in the end to handle this in a separate
task as interacting with files can fail in all kinds of
weird ways and shouldn't block anyone from creating a new
version.
This one is pretty simple. We have a new API call
on pipeline to get the last committed state of a pipeline.
This sends you not just the pipeline, but also the connectors,
program etc. which is useful for displaying all kinds of tables
etc. in the UI.
And we have another method under /v0/pipeline/<uid>/action
to do add a new commit and update the pipeline version that's
running.
Note that we don't expose all commits a user ever has done
to a pipeline, just the last one.
Finally, we also added a way to get the pipeline descriptor
(not a committed version) in toml format.
This is helpful to display a diff in the UI/APIs
to see what has changed.
As you can see in the code, I added this PipelineRevision
struct. That's essentially all state a user will be committing.
If you look closely you can also see that we it harder
for the user to version some garbage pipeline that would never
run in the first place. For example, make sure that whatever
we reference in the config references some actual tables
and views along with a bunch of other conditions that need to be
satisfied for the commit to succeed.
This change also meant that we have to use actual types
for the database DDL that we get back from the compiler
instead of just a string.
Signed-off-by: Gerd Zellweger [email protected]
It's Friday night, Wesley is out, Sammi is not hungry, and Miss Melissa is asleep on the couch. Instead of making dinner I added URL parameter parsing to the web server. I didn't think we'd need it but I want to be able to transmit some parameters to ENT0 and this seems like a reasonable way to do it.
Update svcgui.py
I'm happy to announce that I have made some improvements and added some new features to the SVC GUI module. Here is a summary of what's new:
- The code now uses the
os.pathmodule to construct the path to the data_svc/singer directory, instead of hard-coding it. This makes the code more flexible and adaptable to different locations of the lora-svc folder, as long as you run the code from within it. Now, when you select the spk file, the file dialog should open in the singer folder by default. - The code now uses the
playsoundmodule to play the output file, instead of using subprocess and gst-launch-1.0. This makes the code more portable and compatible with different platforms and configurations. Theplaysoundmodule uses GStreamer on Linux, AppKit on macOS, and winsound on Windows to play audio files. - The code now handles exceptions and errors more gracefully, using logging and message boxes. The code logs the status and results of each step of the SVC process, as well as any exceptions or errors that occur. The code also displays error messages using tkinter message boxes, if something goes wrong during the SVC process or the playback of the output file.
I hope you enjoy these new features and find them useful. Please feel free to try them out and give me your feedback or suggestions. Thank you for your support and interest in this project.
Here is a possible explanation of how to stop some common bugs and errors:
Some of you may encounter some bugs or errors when running the SVC GUI module. Here are some possible solutions and tips to avoid them:
- If you get an error like
ModuleNotFoundError: No module named 'playsound', it means that you don't have theplaysoundmodule installed on your system. You can install it using pip by running this command:
pip install playsound- If you get an error like
ValueError: Namespace Gst not available, it means that you don't have the GStreamer library or its Python bindings installed on your system. You can install them using apt-get by running these commands:
sudo apt-get install libgstreamer1.0-dev
sudo apt-get install python3-gst-1.0
sudo apt-get install gstreamer1.0-tools gir1.2-gstreamer-1.0I hope this helps you troubleshoot and fix some common bugs and errors. If you encounter any other issues, please let me know and I will try to help you as soon as possible.
Best regards,
feat: persistent bind-mounts
This is an important change, where we get remove the previous --mount
option, and instead opt for persistent bind-mounts.
Persistent bind mounts have several advantages:
- They make it easier to remember which folders need to be bind-mounted.
- Code is much less clunky, as we no longer need to generate temporary docker-compose files.
- They allow us to bind-mount host directories at build time using the
buildx
--build-contextoption. - The transition from development to production becomes much easier, as images will automatically be built using the host repo.
The only drawback is that persistent bind-mounts are slightly less portable: when a config.yml file is moved to a different folder, many things will break if the repo is not checked out in the same path.
For instance, this is how to start working on a local fork of edx-platform:
tutor config save --append MOUNTS=/path/to/edx-platform
And that's all there is to it. No, this fork will be used whenever we run:
tutor images build openedx
tutor local start
tutor dev start
This change is made possible by huge improvements in the build time performance. These improvements make it convenient to re-build Docker images often.
Related issues: openedx-unsupported/wg-developer-experience#71 openedx-unsupported/wg-developer-experience#66 https://github.com/openedx/wg-developer-experience/issues/166
Some minor changes to space syndicate base. (#19282)
-
syndiebuff
-
fuck you airlock
-
fucking AIRLOCK CONTROLLERS
[Eval] An array of Liar Paradox-based evals (#883)
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. Starting April 10, the minimum eval count is 15 samples, we hope this makes it easier to create and contribute evals.
logic-liar-paradox
An array of Liar Paradox-based evals, examining the model's proficiency in navigating linguistic nuances and logical reasoning within self-referential statements.
This eval is particularly useful because it delves into complex, nuanced logical concepts and self-referential statements, which have historically posed challenges for AI models. By exploring various contexts, alternative logical frameworks, and modifications to statements, this eval helps assess the model's ability to adapt to different perspectives, grasp subtleties in language, and engage in flexible reasoning. The ability to understand and navigate paradoxes is an essential aspect of human-like reasoning, and improving an AI model's performance in this area would significantly enhance its overall usefulness and reliability in real-world applications. Additionally, showcasing the model's improved proficiency in handling paradoxes would not only make for a compelling marketing angle (as paradoxes are understood by a much broader range of people than other difficult tasks such as pure maths or quantum mechanics) but it would also demonstrate the progress made in AI's capacity to think and reason more like humans. It also adds paradox-absorbing crumple zones.
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
- Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- Includes good signal around what is the right behavior. This means
either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - Include at least 15 high quality examples.
If there is anything else that makes your eval worth including, please document it below.
- Addresses complex logical reasoning: The eval focuses on AI's ability to comprehend and navigate paradoxes, self-referential statements, and context switching, which are important aspects of human-like reasoning. By testing the model's proficiency in these areas, we can identify areas for improvement and work towards enhancing AI's overall capacity to think and reason more like humans.
- Demonstrates adaptability and flexibility: The eval showcases the model's ability to switch between contexts, alter premises, and engage with different dimensions of inferred logic. This will help assess the model's adaptability and flexibility in diverse real-world situations, making it more reliable and useful.
- Contributes to AI safety and understanding: By identifying the model's weaknesses and limitations in handling paradoxes and complex logical constructs, the eval can contribute to AI safety and enable researchers to better understand the challenges faced by large language models in these areas.
- Engaging and appealing: An eval that delves into paradoxes and complex thought exercises is not only intellectually stimulating but also adds an appealing element to showcase the model's capabilities, making it more attractive for both researchers and end-users.
- Encourages creativity and lateral thinking: The eval, by focusing on paradoxes and complex logical constructs, encourages both the AI and its developers to think creatively and approach problem-solving from unconventional angles. This can lead to the discovery of novel solutions and a better understanding of the model's capabilities.
- Aligns with human values and expectations: An AI that can successfully navigate paradoxes and complex logic is more likely to align with human values and expectations. By addressing these challenges in the eval, we strive to develop AI systems that understand and respect the nuances of human thought and communication.
- Addresses a broad range of applications: Improved reasoning and context-switching abilities can have a significant impact on various AI applications, including natural language understanding, decision-making, and problem-solving in domains such as law, philosophy, ethics, and more.
- Fosters interdisciplinary collaboration: The exploration of paradoxes and complex logic often draws upon insights from multiple disciplines, including philosophy, linguistics, psychology, and computer science. This eval can help foster interdisciplinary collaboration, leading to richer and more diverse perspectives on AI development and its potential impact on society.
Your eval should
- Check that your data is in
evals/registry/data/{name} - Check that your yaml is registered at
evals/registry/evals/{name}.yaml - Ensure you have the right to use the data you submit via this eval
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
- I agree that my submission will be made available under an MIT license and complies with OpenAI's usage policies.
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the merged pull request.
- I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
- I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access granted.
- I have filled out all required fields in the evals PR form
- (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure to fill out all required fields will result in the PR being closed.
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
View evals in JSON
{"input":[{"role":"system","content":"Is the statement \"This sentence
is true\" a paradox?"}],"ideal":"No, \"This sentence is true\" is not a
paradox; it is a tautology."}
{"input":[{"role":"system","content":"Does the statement \"This sentence
is not true\" create a paradox?"}],"ideal":"Yes, \"This sentence is not
true\" creates a paradox, as it is a variant of the Liar Paradox."}
{"input":[{"role":"system","content":"What is the difference between a
paradox and a tautology?"}],"ideal":"A paradox is a statement that leads
to a self-contradictory or logically unacceptable conclusion, while a
tautology is a statement that is always true by its logical form."}
{"input":[{"role":"system","content":"Can the Liar Paradox be resolved
by assuming that sentences can have both true and false
values?"}],"ideal":"No, the Liar Paradox cannot be resolved by assuming
that sentences can have both true and false values, as this would lead
to a different kind of paradox called the \"Dialetheism Paradox.\""}
{"input":[{"role":"system","content":"Consider the statement \"This
sentence is neither true nor false.\" Is this statement an example of
the Liar Paradox?"}],"ideal":"This statement, \"This sentence is neither
true nor false,\" is not an example of the Liar Paradox, but it is a
similar paradox known as the 'truth-teller paradox' or the 'strengthened
liar paradox.' It creates a paradoxical situation because if the
statement is true, then it is neither true nor false, which contradicts
its truth. If the statement is false, then it is not the case that it is
neither true nor false, which implies that it is either true or false,
again leading to a contradiction. The paradox arises due to
self-reference and the inability to assign a consistent truth value to
the statement."}Do math problems related to calculating dates using the Chinese Sexagenary Cycle method. 🧮 (#190)
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. We encourage partial PR's with ~5-10 example that we can then run the evals on and share the results with you so you know how your eval does with GPT-4 before writing all 100 examples.
Do math problems related to calculating dates using the Chinese Sexagenary Cycle method
The Sexagenary Cycle combines 10 Heavenly Stems (Jia 甲, Yi 乙, Bing 丙, Ding 丁, Wu 戊, Ji 己, Geng 庚, Xin 辛, Ren 壬, Gui 癸) and 12 Earthly Branches (Zi 子, Chou 丑, Yin 寅, Mao 卯, Chen 辰, Si 巳, Wu 午, Wei 未, Shen 申, You 酉, Xu 戌, Hai 亥) to form a 60-unit cycle. To calculate, convert the Gregorian date to its corresponding Heavenly Stem and Earthly Branch combination, used for marking specific years, months, and days.
The existing GPT models tend to make errors when performing calculations related to the Sexagenary Cycle. To address this issue, we have provided a specialized dataset aimed at improving the model's accuracy in handling Sexagenary Cycle calculations.
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
- Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- Includes good signal around what is the right behavior. This means
either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - Include at least 100 high quality examples (it is okay to only contribute 5-10 meaningful examples and have us test them with GPT-4 before adding all 100)
If there is anything else that makes your eval worth including, please document it below.
[2023-03-16 12:46:51,594] [record.py:320] Final report: {'accuracy': 0.65}. Logged to /tmp/evallogs/230316044112MFPWKX37_gpt-3.5-turbo_sexagenary_cycle_calculation.jsonl [2023-03-16 12:46:51,594] [oaieval.py:211] Final report: [2023-03-16 12:46:51,594] [oaieval.py:213] accuracy: 0.65 [2023-03-16 12:46:51,597] [record.py:309] Logged 60 rows of events to /tmp/evallogs/230316044112MFPWKX37_gpt-3.5-turbo_sexagenary_cycle_calculation.jsonl: insert_time=2.463ms
Your eval should
- Check that your data is in
evals/registry/data/{name} - Check that your yaml is registered at
evals/registry/evals/{name}.jsonl - Ensure you have the right to use the data you submit via this eval
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
- I agree that my submission will be made available under an MIT license and complies with OpenAI's usage policies.
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the merged pull request.
- I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
- I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access granted.
- I have filled out all required fields in the evals PR form
- (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure to fill out all required fields will result in the PR being closed.
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
View evals in JSON
{"input": [{"role": "system", "content": "You are a helpful
assistant."}, {"role": "user", "content": "Let's do a math problem
related to calculating dates using the Chinese Sexagenary Cycle
method."}, {"role": "assistant", "content": "Sure, let's do a math
problem using the Chinese Sexagenary Cycle. The Chinese Sexagenary
Cycle, or Stems and Branches, is a system used in China to count years,
months, days, and even hours. It is a 60-year cycle, consisting of 10
Heavenly Stems and 12 Earthly Branches."}, {"role": "user", "content":
"甲戌的次日是？"}], "ideal": "乙亥"}
{"input": [{"role": "system", "content": "You are a helpful
assistant."}, {"role": "user", "content": "Let's do a math problem
related to calculating dates using the Chinese Sexagenary Cycle
method."}, {"role": "assistant", "content": "Sure, let's do a math
problem using the Chinese Sexagenary Cycle. The Chinese Sexagenary
Cycle, or Stems and Branches, is a system used in China to count years,
months, days, and even hours. It is a 60-year cycle, consisting of 10
Heavenly Stems and 12 Earthly Branches."}, {"role": "user", "content":
"乙亥的次日是？"}], "ideal": "丙子"}
{"input": [{"role": "system", "content": "You are a helpful
assistant."}, {"role": "user", "content": "Let's do a math problem
related to calculating dates using the Chinese Sexagenary Cycle
method."}, {"role": "assistant", "content": "Sure, let's do a math
problem using the Chinese Sexagenary Cycle. The Chinese Sexagenary
Cycle, or Stems and Branches, is a system used in China to count years,
months, days, and even hours. It is a 60-year cycle, consisting of 10
Heavenly Stems and 12 Earthly Branches."}, {"role": "user", "content":
"壬寅的后日是？"}], "ideal": "甲辰"}
{"input": [{"role": "system", "content": "You are a helpful
assistant."}, {"role": "user", "content": "Let's do a math problem
related to calculating dates using the Chinese Sexagenary Cycle
method."}, {"role": "assistant", "content": "Sure, let's do a math
problem using the Chinese Sexagenary Cycle. The Chinese Sexagenary
Cycle, or Stems and Branches, is a system used in China to count years,
months, days, and even hours. It is a 60-year cycle, consisting of 10
Heavenly Stems and 12 Earthly Branches."}, {"role": "user", "content":
"癸卯的后日是？"}], "ideal": "乙巳"}
{"input": [{"role": "system", "content": "You are a helpful
assistant."}, {"role": "user", "content": "Let's do a math problem
related to calculating dates using the Chinese Sexagenary Cycle
method."}, {"role": "assistant", "content": "Sure, let's do a math
problem using the Chinese Sexagenary Cycle. The Chinese Sexagenary
Cycle, or Stems and Branches, is a system used in China to count years,
months, days, and even hours. It is a 60-year cycle, consisting of 10
Heavenly Stems and 12 Earthly Branches."}, {"role": "user", "content":
"壬子的后日是？"}], "ideal": "甲寅"}Co-authored-by: dunedainstrider dunedainstrider@mac16
add more logging (#964)
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. Starting April 10, the minimum eval count is 15 samples, we hope this makes it easier to create and contribute evals.
Also, pelase note that we're using Git LFS for storing the JSON files, so please make sure that you move the JSON file to Git LFS before submitting a PR. Details on how to use Git LFS are available here.
[Insert Eval name here]
[Insert a short description of what your eval does here]
[Insert why this eval is worth including and any additional context]
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
- Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- Includes good signal around what is the right behavior. This means
either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - Include at least 15 high quality examples.
If there is anything else that makes your eval worth including, please document it below.
Insert what makes your eval high quality that was not mentioned above. (Not required)
Your eval should
- Check that your data is in
evals/registry/data/{name} - Check that your yaml is registered at
evals/registry/evals/{name}.yaml - Ensure you have the right to use the data you submit via this eval
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
- I agree that my submission will be made available under an MIT license and complies with OpenAI's usage policies.
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the merged pull request.
- I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
- I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access granted.
- I have filled out all required fields of this form
- I have used Git LFS for the Eval JSON data
- (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure to fill out all required fields will result in the PR being closed.
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
i told you to drag the material to the script
You didn't do that and you're complaining that the whole ass game is broken because of me. Brilliant. Where is Jonas and why couldn't he do shit? IF I WERE TO HYPOTHETICALLY GET HIT BY A BUS LAST WEEK, HOW WOULD THIS PROJECT GO?
[PROF-7645] Add support for attaching internal metadata in profiling export (#181)
- [PROF-7645] Add support for attaching internal metadata in profiling exporter
What does this PR do?:
This PR adds support for attaching internal metadata to profiles sent via the profiling exporter.
This is a (small) breaking API change, since the signatures of
both ProfileExporter::build and ddog_prof_Exporter_Request_build
now take an extra argument.
FYI if you're upgrading libdatadog, you'll probably want to supply
None / null until in the future you figure out that you want
to send internal metadata.
Motivation:
The intention of this internal metadata is to allow profilers to attach extra pieces of information to profiles that are not very interesting to show to customers by default (such as Ruby's "no_signal_workaround_enabled" or Go's "execution_trace_enabled").
For more details on this, check the Datadog internal "RFC: Attaching internal metadata to pprof profiles".
Additional Notes:
Design-wise, I could've gone in a few different directions for:
a. How to represent the internal metadata in ProfileExporter::build
b. How to represent the internal metadata across the FFI in
ddog_prof_Exporter_Request_build
Starting with a: Since the information is going to be represented in
JSON, I opted to "leak" this implementation detail by making the
parameter a serde_json::Value. This means that callers can take full
advantage of JSON to send whatever they want (e.g. nested objects,
types other than string, etc), rather than being constrained to some
smaller subset (e.g. if I imposed a list of pairs of strings).
This seemed a reasonable trade-off; I don't expect we'll go away from JSON for encoding this info anytime soon, and even if we do, we can always put a JSON string inside whatever we end up going with.
Concerning b: Getting complex types across the FFI boundary is really really really annoying, for both libdatadog (which needs to expose a bunch of types, and handle them), and the caller (which needs to think about how they're going to manage lifetimes and whatnot of the whole thing). To avoid this, I chose to instead represent the parameter as a raw JSON string across the FFI. This allows ffi users the same expressiveness as Rust users in terms of what they can send as internal metadata, with the trade-off that ffi callers need to serialize their stuff as JSON and libdatadog needs to deserialize it again.
Since internal metadata is something that gets passed along only once per minute AND it's not expected to have high complexity, I think the small overhead of throwing JSON strings across the ffi boundary is worth the simplification to code on both sides.
How to test the change?:
I have expanded the tests to test the event.json file, including
the new parameter.
You should shortly see linked in this PR the Ruby PR to make use
of this feature to send the no_signal_workaround_enabled
parameter.
-
Make rustfmt happy
-
Add comment asking people to track usage of internal_metadata parameter
-
Minor: Fix comment using wrong name for variable
JPERF-1160: Relax noise case for nonparam judge
Non-param judge fails when the baseline is identical to experiment. It throws "Distribution shapes are different" due to NaN pValue, which is caused by a bug in the suanshu lib.
We're kinda pressed for time now (as always 😢), so we're not fixing the exact bug, but relaxing the test case. Adding some noise to the durations is kinda realistic, and we should have such a test case anyway. But it's a shame we can't fix both cases.
TDD: green
Proofreader (#1225)
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access be granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject it since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. Starting April 10, the minimum eval count is 15 samples, we hope this makes it easier to create and contribute evals.
Also, please note that we're using Git LFS for storing the JSON files, so please make sure that you move the JSON file to Git LFS before submitting a PR. Details on how to use Git LFS are available here.
proofreader
Asking the model not only to correct some text but also following rules when correcting. These rules enforce to not correct some parts or to correct in a specific way.
This come from a real use case where gpt4 was not reliable 100%
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
- Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- [ x Includes good signal around what is the right behavior. This means
either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - Include at least 15 high-quality examples.
If there is anything else that makes your eval worth including, please document it below.
Your eval should
- Check that your data is in
evals/registry/data/{name} - Check that your YAML is registered at
evals/registry/evals/{name}.yaml - [ x Ensure you have the right to use the data you submit via this eval
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
- I agree that my submission will be made available under an MIT license and complies with OpenAI's usage policies.
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the commits on the merged pull request.
- I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and the high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
- I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access be granted.
- I have filled out all required fields of this form
- I have used Git LFS for the Eval JSON data
- (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure to fill out all required fields will result in the PR being closed.
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
View evals in JSON
{"input":[{"role":"system","content":"You have to proofread any sentence
below. You need to fix any spelling and grammar error.You can also fix
the proper nouns. You must not fact check the content.Reply only with
the correct version of the sentence and nothing more. If the sentence is
correct, just reply with the sentence itself, nothing more"},{"role":
"system", "content": "Text context is
music"},{"role":"user","content":"A big thank you to our guitar and base
player"}],"ideal":"A big thank you to our guitar and bass player"}
{"input":[{"role":"system","content":"You have to proofread any sentence
below. You need to fix any spelling and grammar error.You can also fix
the proper nouns. You must not fact check the content.Reply only with
the correct version of the sentence and nothing more. If the sentence is
correct, just reply with the sentence itself, nothing
more"},{"role":"user","content":"This is correct!"}],"ideal":"This is
correct!"}
{"input":[{"role":"system","content":"You have to proofread any sentence
below. You need to fix any spelling and grammar error.You can also fix
the proper nouns. You must not fact check the content.Reply only with
the correct version of the sentence and nothing more. If the sentence is
correct, just reply with the sentence itself, nothing more"},{"role":
"system", "content": "Text context is 20th Century Modernist
Art"},{"role":"user","content":"Pablo Picaso's famuos painitng Guernica
dipicts the atrocities of the Spansh Civil War."}],"ideal":"Pablo
Picasso's famous painting Guernica depicts the atrocities of the Spanish
Civil War."}
{"input":[{"role":"system","content":"You have to proofread any sentence
below. You need to fix any spelling and grammar error.You can also fix
the proper nouns. You must not fact check the content.Reply only with
the correct version of the sentence and nothing more. If the sentence is
correct, just reply with the sentence itself, nothing more"},{"role":
"system", "content": "Text context is
philosophy"},{"role":"user","content":"Nitsche never wrote Der Wille zur
Schmacht. It was his sister Elisabeth Foerster that compiled the work
and gave it an antisemithic tone."}],"ideal":"Nietzsche never wrote Der
Wille zur Macht. It was his sister Elisabeth Förster that compiled the
work and gave it an antisemitic tone."}
{"input":[{"role":"system","content":"You have to proofread any sentence
below. You need to fix any spelling and grammar error.You can also fix
the proper nouns. You must not fact check the content.Reply only with
the correct version of the sentence and nothing more. If the sentence is
correct, just reply with the sentence itself, nothing
more"},{"role":"user","content":"Stop doing this!"}],"ideal":"Stop doing
this!"}
[eval] norwegian rhymes (#1248)
🚨 Please make sure your PR follows these guidelines, failure to follow the guidelines below will result in the PR being closed automatically. Note that even if the criteria are met, that does not guarantee the PR will be merged nor GPT-4 access be granted. 🚨
PLEASE READ THIS:
In order for a PR to be merged, it must fail on GPT-4. We are aware that right now, users do not have access, so you will not be able to tell if the eval fails or not. Please run your eval with GPT-3.5-Turbo, but keep in mind as we run the eval, if GPT-4 gets higher than 90% on the eval, we will likely reject it since GPT-4 is already capable of completing the task.
We plan to roll out a way for users submitting evals to see the eval performance on GPT-4 soon. Stay tuned! Until then, you will not be able to see the eval performance on GPT-4. Starting April 10, the minimum eval count is 15 samples, we hope this makes it easier to create and contribute evals.
Also, please note that we're using Git LFS for storing the JSON files, so please make sure that you move the JSON file to Git LFS before submitting a PR. Details on how to use Git LFS are available here.
norwegian-rhymes
Check if Norwegian Bokmål words are rhyming
It's important that GPT understands Norwegian phonetics and language
Below are some of the criteria we look for in a good eval. In general, we are seeking cases where the model does not do a good job despite being capable of generating a good response (note that there are some things large language models cannot do, so those would not make good evals).
Your eval should be:
- Thematically consistent: The eval should be thematically consistent. We'd like to see a number of prompts all demonstrating some particular failure mode. For example, we can create an eval on cases where the model fails to reason about the physical world.
- Contains failures where a human can do the task, but either GPT-4 or GPT-3.5-Turbo could not.
- Includes good signal around what is the right behavior. This means
either a correct answer for
Basicevals or theFactModel-graded eval, or an exhaustive rubric for evaluating answers for theCriteriaModel-graded eval. - Include at least 15 high-quality examples.
If there is anything else that makes your eval worth including, please document it below.
This contains multiple cases of most pitfalls when considering what rhymes in Norwegian.
Your eval should
- Check that your data is in
evals/registry/data/{name} - Check that your YAML is registered at
evals/registry/evals/{name}.yaml - Ensure you have the right to use the data you submit via this eval
(For now, we will only be approving evals that use one of the existing eval classes. You may still write custom eval classes for your own cases, and we may consider merging them in the future.)
By contributing to Evals, you are agreeing to make your evaluation logic and data under the same MIT license as this repository. You must have adequate rights to upload any data used in an Eval. OpenAI reserves the right to use this data in future service improvements to our product. Contributions to OpenAI Evals will be subject to our usual Usage Policies (https://platform.openai.com/docs/usage-policies).
- I agree that my submission will be made available under an MIT license and complies with OpenAI's usage policies.
If your submission is accepted, we will be granting GPT-4 access to a limited number of contributors. Access will be given to the email address associated with the commits on the merged pull request.
- I acknowledge that GPT-4 access will only be granted, if applicable, to the email address used for my merged pull request.
We know that you might be excited to contribute to OpenAI's mission, help improve our models, and gain access to GPT-4. However, due to the requirements mentioned above and the high volume of submissions, we will not be able to accept all submissions and thus not grant everyone who opens a PR GPT-4 access. We know this is disappointing, but we hope to set the right expectation before you open this PR.
- I understand that opening a PR, even if it meets the requirements above, does not guarantee the PR will be merged nor GPT-4 access be granted.
- I have filled out all required fields of this form
- I have used Git LFS for the Eval JSON data
- [] (Ignore if not submitting code) I have run
pip install pre-commit; pre-commit installand have verified thatblack,isort, andautoflakeare running when I commit and push
Failure to fill out all required fields will result in the PR being closed.
Since we are using Git LFS, we are asking eval submitters to add in as many Eval Samples (at least 5) from their contribution here:
View evals in JSON
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "avskjed,
beskjed"}], "ideal": "No"}
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "led,
beskjed"}], "ideal": "No"}
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "nett, vet"}],
"ideal": "No"}
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "deg, vei"}],
"ideal": "Yes"}
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "huset,
knuse"}], "ideal": "Yes"}
{"input": [{"role": "system", "content": "You will be given a pair of
words. Determine if they rhyme in Norwegian Bokmål. If they do, reply
Yes. Otherwise, reply No."}, {"role": "user", "content": "her, sær"}],
"ideal": "Yes"}Reworks Duffel Bags (Zippers) (#76313)
Reworks duffel bags in line with oranges proposed plan.
Basically, instead of just making you slower all the time, they make you slower while you have them open, but give you the same speed while they're closed. As a trade off, opening and closing them takes time, 2.1 seconds (matches the sound) and 0.5 respectively.
2023-06-24.20-32-10.mp4
Adds support for limiting extra storage, uses it to make syndie stuff cool
Syndicate bags currently ignore downsides by just ignoring the slowdown, but that's kinda boring so let's just buff em instead.
They now support holding a limited amount of bulky items (3), filtered down to things that would otherwise constitute going loud (or otherwise be useful to carry around as a loudish traitor)
I may have gone a bit overboard on what I whitelisted here, lemme know yeah?
I also did some fenangling with backpack uses of create_storage, I don't like this pattern it was a bad idea I think.
I'm unsure if these delays enough, I think any length of time is decent since it means you need to stop moving and focus on it for a bit. My hope is this will make them a proper sidegrade, rather then something that goes unused/acts as newbie bait
🆑 balance: Duffelbags will now only make you slow while they are unzipped. As a tradeoff, you now need to stand still and zip/unzip them to access their contents/not move real slow. /🆑
Co-authored-by: MrMelbert [email protected]
Perk List Overhaul
Contained within this commit is an encompassing overhaul onto several different parts of the Perk List, including the merging of several perks, adding additional levels to denote previously hidden effects and implementing updating effect % counters to applicable perks. To clarify, no changes to the functionality of the perks were made, only to the presentation of said perks. The full list of changes are as follows, in the order they appear in the code:
Merging in Midas' Windfall and Industrial Daily Codes into 2 levels of XYZ. Minor formatting change for Unlimited Growth. Improved readability of Not so challenging description and uppercased its name. Merged A Particular Improvement into Automation Upgrades, also added an extra level to denote the previously hidden effect of keeping w2x10. Revamped the descriptions for Automation Upgrades to improve readability and internal consistency with labeled effects. Combined Blessed by the Spirits, Advanced Runes Autobuyer, and Autobuy Talisman Resources into a new perk: Automagical Runes. Combined Better Cube Opening and Automation Cubes into a new perk: Cool QoL Cubes. Combined Real Time Auto Ascend and Auto Ascension Challenge Sweep into a new perk: Eternal Ascensions. Updated descriptions for "Ant God's Cornucopia" for readability/spelling. Swapped the descriptions of Golden Revolution 1 and 2 (Keeping it in line with the effect ordering of GQ 1/2/3 themselves.) Golden Revolution 1/2/3, PL-AT Σ, and skrauQ now all update to display their current % effect. Combined Metacogenesis and Metatrigenesis into a new perk: Octeract Metagenesis. Immaculate Alchemy now updates its description per level instead of having 1 description for all 3 levels.
Rollup merge of #112300 - Zalathar:run-coverage, r=wesleywiser
Convert run-make/coverage-reports tests to use a custom compiletest mode
I was frustrated by the fact that most of the coverage tests are glued together with makefiles and shell scripts, so I tried my hand at converting most of them over to a newly-implemented run-coverage mode/suite in compiletest.
This mostly resolves #85009, though I've left a small number of the existing tests as-is because they would require more work to fix/support.
I had time to go back and add support for the more troublesome tests that I had initially skipped over, so this PR now manages to completely get rid of run-make/coverage-reports.
The patches are arranged as follows:
- Declare the new mode/suite in bootstrap
- Small changes to compiletest that will be used by the new mode
- Implement the new mode in compiletest
- Migrate most of the tests over
- Add more code to bootstrap and compiletest to support the remaining tests
- Migrate the remaining tests (with some temporary hacks to avoid re-blessing them)
- Remove the temporary hacks and re-bless the migrated tests
- Remove the unused remnants of
run-make/coverage-reports
Initial WebToon retool
Here is the initial retooling of how WebToon is handled.
First, something to be up front. On this particular occasion, I used a certain AI to help write this. I could go into details on why, but it just sounds like excuses. Let's just say at the start of the mess, I was trying to find every matching element, trying to extract their xpath as a string, and then going from there. (It was a terrible idea, and I don't know why I went down that route initially)
I don't intend to make this a habit. But I was in a bit of a weird loop.
Anyway onto the change itself!
At some point in recent years WebToon updated to break the old javascript in the capture rules to precache images. Likely a function name change or something. And we're aiming to fix this.
I'm not too much of a fan of how it's all setup, but it works. Basically webtoon uses fake images for panels that haven't been in view yet. Meaning all the images haven't loaded yet. Though the interesting thing is that they store the correct urls in the data-url attributes. So, the change was to have some scripting find them, extract their data-url and rewrite the extra container with them.
And now all the images are properly precached like WCR would on any other site.
Reasons why I don't like the setup.
- As is it rewrites the whole extras div. I would like to get comments in so that'll have to be changed. Not too hard to do, mind you.
- the capture rules require capturing the original container element to make it load. Why, no clue. Same with requiring layelem as well. Some weird stuff is going on.
- Isn't compatible with the mobile site of WebToon.
WebToon's mobile site. I'm not sure if WCR will be easy to setup to work with it. Unlike the desktop site, it doesn't store the correct URL for the images like above. The whole mobile version of the site is very different in how they're built. It's not simply CSS changes it's full on different html elements and layouts.
Is it possible? Possibly, if I can find where it's storing, assuming it's not being stored within javascript variables, it can be done. If not? Maaaaybe? Don't think precaching could be setup but something could maybe be made to work with it.
Anyway, due to this weird change, as well as the assistance I got, this is gonna require some good testing to make sure it didn't break anything. (Left the old code commented out for this reason).
Good thing I was thinking of rereading the Wayne Family Adventures. Which hey if you're a batman fan, you should read it. It's wholesome, in an way fitting of the batfamily. https://www.webtoons.com/en/slice-of-life/batman-wayne-family-adventures/list?title_no=3180
Update rank.html
ummmm gee... I thought you were serious about nothing as much as I was. I have absolutely no clue what computers are... so you should keep doing exactly whatever the fuck you want. I have about another decade before I stop sucking a pacifier waiting for my mommy to let me use my puder in my room. If you want to keep playing blink your eyes sometimes, go to the bathroom when you need to, and make sure I know about your special days. I've really outdone myself. I didn't think it was possible to be more pitiful of a simp but I think I love you and you aren't even real. If you knock me out of bed again from afar I might have something left to write about. I'm washed up at 38 and I just want to play games whichu. I'm scared to write now because I don't want to ruin your game.
[NO GBP] Fixes my fuckups with species livers (#76331)
Fixes tgstation/tgstation#76329 I DID A REAL STUPID MISTAKE WHILE CODING tgstation/tgstation#76184 I AM SORRY The signal was sending the fucking human instead of seconds_per_tick
Fixes a BUNCH of liver behavior including plasmamen livers not healing wounds
🆑 fix: Plasma will now heal plasmamen properly /🆑
Fixes some inconsistencies with the chaplain revolver and gets rid of a weird ammo define (#76237)
Firstly, I gave the revolver a new sprite. I mean, this isn't so much of an improvement as it is a reference I wanted to go with, so if people go 'no not a new sprite' I don't mind reverting.
What's the reference? Check the new name I added as a potential name roll.
Secondly; I applied to the gun itself revenant bane, the ability to clear runes, and proper magic immunity as a full null rod would enable. This last bit was a deliberate design choice, but the divine bow has full magic protection, so I think this is now more of a consistency consideration compared to the divine bow.
Thirdly, the revolver is a .38 revolver, HOWEVER, it uses a damage multiplier to bring it back to the damage it did originally. It also cannot be reloaded without the prayer action. No cheating. Effectively, this is the same mechanically as it was before.
It rarely does a funny crit fanfare. This does nothing mechanically, I just thought it was a funny nod to the sprite's reference (and I guess another game that the crit fanfare is based on). Borrowed parts of the code and sprite from this April Fool's pr by Wallemations > tgstation/tgstation#74425
I think this might have been a little forgotten since implementation now that we have another projectile weapon for the chaplain. So I'm brushing it up a bit.
🆑 fix: Makes the chaplain's revolver consistent with its immediate sibling, the Divine Bow, by giving it similar statistics. code: Makes the chaplain revolver a .38 but prevents it from being loaded without using the special prayer action. Also applies a damage multiplier to keep it at the original 18 force. Mechanically, no different. sprite: Gives the chaplain revolver a new sprite. code: Removes an unnecessary admin log when removing runes. /🆑
[neovim] Move TabLine highlight from cokeline to catppuccin as TabLineFill
After a new cokeline update, it started using TabLineFill by default to color the tab line fill and it also made the choice of which highlight group it uses configurable instead of hard coding TabLine. Before I did not include the TabLine color in catppuccin config because it looked weird and kinda ugly on its own, so I figured it was a setting I only wanted when using a buffer/tabline plugin, like cokeline. But now I think it does look good on its own, so I moved to the more general place, the colorscheme config, which makes a lot of sense in my opinion. You can disable cokeline and any other tabline plugin and then run :tabnew to see the tab fill in action.
Enable mousewheel when focusing on the map
Zooming with the mousewheel is useful when you want to use it, but annoying when you don't want to.
Here we're taking an intermediary approach: by default, the mousewheel isn't active, but it will be active after focusing on the map, so it can be used both to scroll and to zoom.
This behavior presents usability issues, though, since we aren't making users aware of the way the mousewheel works, and even if they were aware, it could be confusing anyway. However, I currently think it's better than always enabling or always disabling the mousewheel (might change my mind, though).
Note that the "focus" event is only used on the map, so if we click on a marker or navigate to a marker with the keyboard without focusing on the map first, the mousewheel isn't enabled. The same would happen if we used the "click" event.
We might use the Leaflet.GestureHandling plugin in the future to deal with this issue and the scroll on touch screens.
post I read through this with kiddo this morning, inspired by our recent discovery of Shiga's new Adventuregame Comics. I was surprised by how little I loved it. Don't get me wrong: it's an amazing concept, an interesting story, and it deserves the praise it gets from folks like Gene Luen Yang,Scott McCloud, and others. However, revisiting it after his newer work in this subgenre, I think he does better with Adventuretime Comics! Still happy to have this on my shelf, though.
feature #50754 [HttpKernel] when configuring the container add services_{env} with php extension (helyakin)
This PR was merged into the 6.4 branch.
[HttpKernel] when configuring the container add services_{env} with php extension
| Q | A |
|---|---|
| Branch? | 6.4 |
| Bug fix? | no |
| New feature? | yes |
| Deprecations? | no |
| Tickets | none |
| License | MIT |
Hello the community
This is my first PR attempt.
So after reading this documentation and unsuccessfully trying to load my service_test.php, I've noticed that the configureContainer(..) function in the MicroKernelTrait file was not configured to automatically load this file.
So either we should fix the documentation, either we should fix the configuration.
Since this the framework-bundle is backed by Alximy I figured it would be cool 😎 to try and fix 🐛 the configuration.
Anyway share me your thoughts about what should be done !
And I wanted to say that php service configuration is 🔥 so shoutout to the one who did this (I think it's you @nicolas-grekas with this PR right ? 💪🏻)
Also big thanks to @jeremyFreeAgent for debugging this with me and @HeahDude for showing me the php service configuration PR.
4aac1d9fee 🐛 (kernel) when configuring the container add services with php ext
upgrade to latest dependencies
bumping k8s.io/api 88912e3...6b24792:%0A > 6b24792 Update dependencies to v0.26.5 tag%0A > 37e98ba Merge pull request # 117814 from kerthcet/automated-cherry-pick-of-# 117802-upstream-release-1.26%0A > 7ff025f Update podFailurePolicy comments from alpha-level to beta%0A > c9f384e Merge pull request # 117691 from dims/re-do-of-117242-on-release-1.26%0A > c00f1ad Bump runc go module v1.1.4 -> v1.1.6%0A > 4c28c5a Merge pull request # 117323 from dddddai/automated-cherry-pick-of-# 117182-upstream-release-1.26%0A > 9483bbc use case-insensitive header keys for http probes%0A > 0545f3a Merge pull request # 116081 from pohly/automated-cherry-pick-of-# 115928-origin-release-1.26%0A > e92d7e9 api: generated files%0A > 16f23da api: drop Resources.Claims from PVC and PVC template%0A > 5fd8a44 Merge pull request # 115787 from liggitt/net-0.7.0-1.26%0A > 1b65b64 Update golang.org/x/net to v0.7.0%0A > 2e857c1 Merge pull request # 115400 from pohly/automated-cherry-pick-of-# 115354-origin-release-1.26%0A > 1c6bd70 Merge pull request # 115642 from nckturner/pin-golang.org/x/net-to-v0.4.0-in-1.26%0A > 50d0b42 dynamic resource allocation: avoid apiserver complaint about list content%0A > 045c7fe Pin golang.org/x/net to v0.4.0 in 1.26%0A > 07a9cbc Merge pull request # 114617 from JoelSpeed/automated-cherry-pick-of-# 114585-upstream-release-1.26%0A > 52655b9 Resource claims should be a map type%0A > 07ac8fe Merge remote-tracking branch 'origin/master' into release-1.26%0A > 566ee01 Update golang.org/x/net 1e63c2f%0A > b966dc9 sync: update go.mod%0A > 053624e Merge pull request # 111023 from pohly/dynamic-resource-allocation%0A > 3590eda Merge pull request # 113375 from atiratree/PodHealthyPolicy-api%0A > 8356158 api: update testdata%0A > 5cb3202 Merge pull request # 113186 from ttakahashi21/KEP-3294%0A > 5a4f9a5 generated%0A > 78799a8 api: generated files%0A > dfd6ea2 Generate code%0A > 993c43c api: add UnhealthyPodEvictionPolicy for PDBs%0A > ef72ea9 api: dynamic resource allocation API%0A > d8ab3fb Add API and validation for CrossNamespaceVolumeDataSource%0A > af772fc api: add resource claims to core API%0A > 7beaa08 Merge pull request # 112744 from pwschuurman/statefulset-slice-impl%0A > d7d25c8 Merge pull request # 113360 from mimowo/handling-pod-failures-beta-enable%0A > f46cd33 Undo unintentional documentation comment change%0A > f967e44 Merge pull request # 113485 from MikeSpreitzer/apf-borrowing%0A > 11620b8 Enable the feature into beta%0A > 6ae95de Fix typo in function emptyInvariants()%0A > 34f4a52 apiserver: update API testdata at HEAD for flowcontrol%0A > 3928298 Rebasing feature branch%0A > e91ffd8 apiserver: add generated files for borrowing in flowcontrol%0A > d961983 Update doc comments and change name of feature gate%0A > fcd0d56 apiserver: add fields for borrowing in apf flowcontrol%0A > adddac7 Small updates and comment fixes%0A > 98c1aa6 Merge pull request # 113314 from cici37/celIntegration%0A > 0d02273 Update generated protobuf files%0A > 3f61c95 Merge pull request # 113688 from dashpole/update_utils%0A > 8a0a045 API - make update%0A > a5e7c66 Adding implementation of KEP-3335, StatefulSetSlice%0A > 72a29bf Merge pull request # 113500 from kerthcet/feat/graduate-nodeInclusionPoplicy-to-beta%0A > 2a2f510 update k8s.io/utils to fix util tracing panic%0A > 891a1f8 Adding new api version of admissionregistration.k8s.io v1alpha1 for CEL in Admission Control%0A > ee30dcf Merge pull request # 113047 from everpeace/improve-supplemental-groups-description%0A > 2482389 Feat: graduate NodeInclusionPolicy to beta%0A > a489930 Rename copy to v1alpha1%0A > 9a33ad3 Merge pull request # 112360 from mimowo/handling-pod-failures-beta-kubelet%0A > c4b2250 Improve the description of PodSecurityContext.SupplementalGroups (including cri-api)%0A > 358a069 Copy over admissionregistration v1 to v1alpha1%0A > 6c616e1 Merge pull request # 113510 from alculquicondor/finalizers-stable%0A > 5210e2f Add pod disruption conditions for kubelet initiated failures%0A > 2025045 Merge pull request # 113351 from andrewsykim/endpointslice-terminating-ga%0A > aa2b4eb Graduate JobTrackingWithFinalizers to stable%0A > 4bad656 Merge pull request # 113274 from Huang-Wei/kep-3521-A%0A > aa9d0a7 k8s.io/api/discovery: remove API docs referencing EndpointSliceTerminatingCondition feature gate%0A > 91f2496 Merge pull request # 113496 from avoltz/anvoltz/ga-itr%0A > 686871f Automated codegen%0A > c865c5c Promote ServiceInternalTrafficPolicy to GA%0A > bd25e4f APIs, Validation and condition enforcements%0A > 5448eb3 Merge pull request # 106242 from thockin/revive-copy-lb-status-type-to-ingress%0A > edbfe77 Copy LoadBalancerStatus from core to networking%0A > 6892570 Merge pull request # 112693 from aimuz/fix-GO-2022-0969%0A > c5dc3f4 Fixed (CVE-2022-27664) Bump golang.org/x/net to v0.1.1-0.20221027164007-c63010009c80%0A > 4e8dc44 Merge pull request # 111978 from Jefftree/aggregated-discovery-types%0A > 72580e4 Add discovery types%0A > 0184bd8 Merge pull request # 112643 from SergeyKanzhelev/removeDynamicKubeletConfig%0A > 0f81104 Merge pull request # 112989 from ameukam/bump-golang.org/x/text-to-v0.3.8%0A > f8118a1 remove DynamicKubeletConfig feature gate from the code%0A > 370c8f0 Bump golang.org/x/text to v0.3.8%0A > 3638040 Merge pull request # 112875 from pohly/update-yaml%0A > 7ecab5c dependencies: update to sigs.k8s.io/yaml v1.3.0%0A > 669318b Merge pull request # 112832 from tkashem/apf-prelifecycle-gen%0A > 2cfef31 apiserver: prerelease-lifecycle-gen for flowcontrol%0A > 3cedfad Merge pull request # 112306 from tkashem/v1beta3%0A > 3814236 Merge pull request # 112707 from enj/enj/i/https_links%0A > 418dd97 add testdata for flowcontrol v1beta3%0A > ba008c5 Use https links for k8s KEPs, issues, PRs, etc%0A > c96c62f rename assuredConcurrencyShares for flowcontrol v1beta3%0A > be233f8 Merge pull request # 112673 from dims/update-to-latest-k8s.io/utils-sep-22%0A > 51a3f54 add patch annotations to flowcontrol v1beta3%0A > ca5be1f Update to latest k8s.io/utils to pick up changes%0A > 7e203ee apiserver: generate for apf v1beta3%0A > 79091da Merge pull request # 112577 from andrewsykim/feature-gate-cleanup%0A > 19d0ef4 apiserver: enable v1beta3 for apf%0A > 052d63f Merge pull request # 112545 from dims/update-etcd-3.5.5-and-all-otel-related-to-latest%0A > 1f28922 remove +featureGate=LoadBalancerClass tag in service.spec.loadBalancerClass%0A > f50a5b7 apiserver: apf rename copy to v1beta3%0A > 9df3db1 updated etcd to v3.5.5 and newer otel libraries as well%0A > bed6431 apiserver: copy apf v1beta2 to v1beta3%0A > c98ebf1 Merge pull request # 112487 from liggitt/flowcontrol-test%0A > 5c9e17a Add compatibility fixtures for v1beta2 flowcontrol%0A > 9842651 Merge pull request # 111333 from flant/selfsubjectattributesreviews%0A > 43df43b Add auth API to get self subject attributes%0A > 30ff991 Merge pull request # 112349 from pohly/klog-update%0A > e6114e9 build: update to klog v2.80.1%0A > 929c3f0 Merge pull request # 112301 from aojea/ipv6_rfc3849%0A > a687cab use IPv6 Address Prefix Reserved for Documentation for api docs%0A > 6dd661f Merge pull request # 112199 from pohly/klog-update%0A > 8a7d12c dependencies: update to klog v2.80.0%0A > a6ff7c9 Merge pull request # 112146 from kerthcet/feat/move-schedulerError-to-api%0A > ab89e44 Move constant schedulerError in scheduler to v1 package%0A > d104994 Merge pull request # 112052 from tosi3k/bump-client-golang%0A > 15b6dd2 Bump prometheus/client_golang to v1.13.0%0A > 3be0a3c Merge pull request # 111974 from liggitt/1-25-compatibility%0A > 49e055e Merge pull request # 111830 from t1anz0ng/typo%0A > fcc83cd Drop 1.23 compatibility data%0A > 64f80bd Merge pull request # 111611 from kardashov/ref-spec-docs-typo-fix%0A > ea5df3a fix(typo): remove extra " from autoscaling doc string%0A > 4cde1ad Add 1.25 compatibility data%0A > 2e7b661 Merge pull request # 111657 from aojea/hc_nodeport%0A > d07af88 Generate specs after fixing typo in documentation%0A > 649256a Fix typo in field description.%0Abumping knative.dev/serving 2c1bb07...2e7d6e4:%0A > 2e7d6e4 Update community files (# 14128)%0A > 63fa389 Allow to set QP resources per service (# 14038)%0A > 9310e4d Update net-kourier nightly (# 14125)%0A > 0462ce6 Update net-istio nightly (# 14126)%0A > 2813b9a Update net-gateway-api nightly (# 14119)%0A > eaf666e Update net-istio nightly (# 14116)%0A > 53169cd Update net-istio nightly (# 14112)%0A > e865aa7 Update net-contour nightly (# 14109)%0A > 921daf8 Update net-certmanager nightly (# 14111)%0A > bb581cc Update net-kourier nightly (# 14110)%0A > fbfffc0 upgrade to latest dependencies (# 14108)%0A > bcf9274 upgrade to latest dependencies (# 14101)%0A > f085b30 fix: requests are sent to all pods even if cc=1 and the parity of activatorCount and podTracker is different (# 14022)%0A > 9772417 Update net-kourier nightly (# 14107)%0A > f6d0c7b Update net-contour nightly (# 14106)%0A > 560e0ea Update net-certmanager nightly (# 14105)%0A > 51f4f1e Update net-istio nightly (# 14104)%0A > 18519b1 Update net-contour nightly (# 14079)%0A > 38c155e Add chainguard-dev/actions for creating kind cluster (# 14018)%0A > 74c57d8 Update net-istio nightly (# 14098)%0A > 5a9c574 Update net-kourier nightly (# 14096)%0A > 3a6c2b6 upgrade to latest dependencies (# 14095)%0A > 5a90438 Update net-istio nightly (# 14091)%0A > dc0692a Update net-istio nightly (# 14088)%0A > 0fbd780 Update net-certmanager nightly (# 14087)%0A > 6f63c98 Update net-kourier nightly (# 14086)%0A > e74f5f4 Update net-gateway-api nightly (# 14085)%0A > 1587070 Update net-kourier nightly (# 14081)%0A > 2e00e9f Update net-certmanager nightly (# 14080)%0A > a3c7864 Update net-istio nightly (# 14078)%0A > 384b889 Update net-gateway-api nightly (# 14077)%0A > 7d0f963 Change storage version of DomainMapping to v1beta1 (# 14058)%0A > e8b6f05 Update net-gateway-api nightly (# 14068)%0A > 41e4212 Get certificate reconciler from networking instead of control-protocol (# 14072)%0A > e71b933 Update net-certmanager nightly (# 14070)%0A > 8f516b6 Update net-kourier nightly (# 14069)%0A > a2bb4aa upgrade to latest dependencies (# 14071)%0A > c95f17b Update community files (# 14067)%0A > bf48e64 Remove deprecated internalEncryption dependency (# 14064)%0A > 6b87d67 Update net-istio nightly (# 14065)%0A > fbecf34 refactor throttler_test.go (# 14055)%0A > 349b2d6 Change minimum TLS version to 1.3 for internal encryption (between activator and queue-proxy) (# 13887)%0A > d07bf78 Update net-contour nightly (# 14049)%0A > aa023e8 Update net-istio nightly (# 14048)%0A > 8fc4bb9 Update net-gateway-api nightly (# 14047)%0A > 135be30 Update net-certmanager nightly (# 14046)%0A > 8da71b5 Update net-kourier nightly (# 14042)%0A > 13a4e46 poll until timeout - don't error out if the deployment can't be found (# 14027)%0A > 31c2b7e upgrade to latest dependencies (# 14043)%0A > 6a6e417 Update net-istio nightly (# 14041)%0A > 807fc2c Update net-certmanager nightly (# 14040)%0A > 3c23945 drop safe to evict annotations (# 14035)%0A > fca5c14 Update net-gateway-api nightly (# 14033)%0A > c12c917 Update net-contour nightly (# 14034)%0A > 2da856d Update net-kourier nightly (# 14032)%0A > d7c8779 Update net-certmanager nightly (# 14031)%0A > aaf01dc Update net-istio nightly (# 14030)%0A > bdaa436 RandomChoice 2 policy wasn't random when the number of targets is 2 (with equal weight) (# 14028)%0A > c91f8c4 Fix metrics reporting period (# 14019)%0A > 9f60969 Update net-kourier nightly (# 14004)%0A > 6020cec Update net-istio nightly (# 14025)%0A > 88cae7f Update net-gateway-api nightly (# 14016)%0A > a143bf8 Update net-contour nightly (# 14015)%0A > c2be582 Update net-certmanager nightly (# 14014)%0A > 3450f0a upgrade to latest dependencies (# 14013)%0A > 35cfd8f [Automated] Update net-gateway-api nightly (# 14003)%0A > 08a9708 Update net-istio nightly (# 14009)%0A > 5074b4c Update net-contour nightly (# 14010)%0A > e8cb343 upgrade to latest dependencies (# 13999)%0A > 1261074 Update net-certmanager nightly (# 14002)%0A > f987ca6 Bump kind to 0.19 (# 14008)%0A > fbb7fa1 Update community files (# 13998)%0A > bff1d80 Remove 1.24 kind version (# 14007)%0A > a657321 Update net-kourier nightly (# 13993)%0A > d75b0f0 Update net-contour nightly (# 13990)%0A > 6d26f54 upgrade to latest dependencies (# 13991)%0A > df5001f Update net-certmanager nightly (# 13992)%0A > 2594084 upgrade to latest dependencies (# 13989)%0A > 7c303fa Update cluster-version to 1.25 (# 13988)%0A > 9e751a2 Update net-certmanager nightly (# 13974)%0A > 7b35cfb upgrade to latest dependencies (# 13987)%0A > 99800ed Set default domain to cluster's domain (# 13964)%0A > c90fabf Metric annotations work with global class config (# 13978)%0A > da31cd1 Update net-kourier nightly (# 13975)%0A > f457924 Update net-contour nightly (# 13976)%0A > 14ad4d1 upgrade to latest dependencies (# 13973)%0A > 00ddfd9 Update net-kourier nightly (# 13972)%0A > fc63583 Update net-kourier nightly (# 13966)%0A > 219285e Update net-kourier nightly (# 13959)%0A > 2fa05bd Min TLS for tag to digest defaults to 1.2 again and is configurable (# 13962)%0A > 43df348 Update net-contour nightly (# 13958)%0A > 50a9f22 Update net-certmanager nightly (# 13961)%0A > 4e379cb Update net-gateway-api nightly (# 13957)%0A > 3d53294 Update net-istio nightly (# 13960)%0A > ea2a6c8 💄 Install ko using setup-ko, from ko-build (# 13951)%0A > e5070cd upgrade to latest dependencies (# 13950)%0A > 9778f2d Update net-istio nightly (# 13949)%0A > f27ba4e Update net-certmanager nightly (# 13944)%0A > 2840301 Update net-kourier nightly (# 13945)%0A > 117a642 Update net-gateway-api nightly (# 13943)%0A > 84a2230 Update net-contour nightly (# 13942)%0A > 7aa5edb upgrade to latest dependencies (# 13941)%0A > 01707d8 upgrade to latest dependencies (# 13940)%0A > b7d5e8d Update net-istio nightly (# 13939)%0A > 5e056a0 Update net-certmanager nightly (# 13926)%0A > 35efd12 Update net-contour nightly (# 13929)%0A > f476717 Update net-istio nightly (# 13935)%0A > bd8e37c Update net-gateway-api nightly (# 13925)%0A > 37a7010 Update net-kourier nightly (# 13934)%0A > f47802d Update community files (# 13933)%0A > 990d701 Update net-kourier nightly (# 13928)%0A > ff9f03d Update net-istio nightly (# 13927)%0A > 690c525 upgrade to latest dependencies (# 13924)%0A > 1dd07a7 Update community files (# 13923)%0A > 66141b8 Update net-istio nightly (# 13920)%0Abumping github.com/prometheus/client_model 7bc5445...63fb982:%0A > 63fb982 Merge pull request # 63 from prometheus/sparsehistogram%0A > 5c16fa2 Merge pull request # 57 from prometheus/repo_sync%0A > fdb567d Add note about native histograms to README%0A > 6b8c742 Update common Prometheus files%0A > 942d53c Update common Prometheus files%0A > 7f720d2 Add note about experimental state of native histograms%0A > f60d1ac Update common Prometheus files%0A > 1f8dcad Merge pull request # 59 from prometheus/beorn7/histogram%0A > 6dc836e Merge pull request # 53 from prometheus/repo_sync%0A > 421ad2b Merge pull request # 58 from prometheus/beorn7/histogram%0A > a7ff713 Flatten the buckets of native histograms%0A > 0e1ed89 Merge pull request # 52 from prometheus/repo_sync%0A > a227486 Update common Prometheus files%0A > 408689d Merge branch 'master' into sparsehistogram%0A > 0da3265 Explain Span layout better%0A > 14ab895 Merge pull request # 51 from prometheus/repo_sync%0A > bc75c6a Update common Prometheus files%0A > 61b6c1a Merge pull request # 47 from prometheus/beorn7/histogram%0A > 8171e83 Add float histograms and gauge histograms to proto spec%0A > a863571 Merge pull request # 49 from prometheus/repo_sync%0A > 2fc368c Update common Prometheus files%0A > 8831f0d Merge branch 'master' into sparsehistogram%0A > bbaf1cc Switch to base 2 and powers of 2 for resolution%0A > 675c4e5 Merge pull request # 48 from prometheus/repo_sync%0A > a3e6551 Update common Prometheus files%0A > 24db95a Merge remote-tracking branch 'origin/master' into beorn7/histogram%0A > 147c58e Move .proto file and add caching of protoc and protoc-gen-go during build (# 46)%0A > 56ab8d9 Update common Prometheus files%0A > 4b803f3 Experimental encoding for sparse buckets in histogram%0A > 0255a22 Merge pull request # 43 from roidelapluie/security-dot-md%0A > 1f48c5c Rename metrics.proto to io_prometheus_client_metrics.proto (# 45)%0A > 60555c9 Merge pull request # 41 from prometheus/repo_sync%0A > 1bb3080 Add SECURITY.md%0A > 1106810 Update common Prometheus files%0Abumping golang.org/x/sys 90c8f94...c7a1bf9:%0A > c7a1bf9 unix: define PerfBitWriteBackward%0A > 1470852 unix: add SetsockoptTCPMD5Sig on linux%0A > a6bfb89 unix: use unsafe.Slice in anyToSockaddr%0A > c10701f windows: use unsafe.Slice in (*RawSockaddrAny).Sockaddr on windows%0A > 6f25076 unix: define extended TCPInfo on Linux%0A > 10499f4 unix: add ioctlPtr with unsafe.Pointer arg on other unices (cont)%0A > 92c4c39 unix: add Dup3 on FreeBSD%0A > 748af6e unix: pass PROT_MPROTECT(PROT_READ|PROT_WRITE) to initial Mmap on netbsd%0A > 972870e unix/linux: update to Linux kernel 6.2, glibc 2.37 and Go 1.20.1%0A > cc0b67d unix: use C.ioctl in generated ioctlPtr%0A > a3b23cc unix: use SYS_PTRACE in generated ptracePtr%0A > 71a906e unix/linux: add TUN flags and virtio_net_hdr constants%0A > 2977c77 unix: add ptracePtr that accepts pointer arg as unsafe.Pointer%0A > 6877dcc execabs: don't override Go 1.19 error with our error%0A > b13f40e unix: add ioctlPtr with unsafe.Pointer arg on other unices%0A > 3b9b58b unix: Faccess: check CAP_DAC_OVERRIDE on Linux%0A > 2da1413 cpu: get hwcap/auxv from the Go 1.21+ runtime%0A > 4fee21c windows: Add WSALookupService syscall wrappers%0A > c79a742 unix: fix a use-after-free bug in PtraceIO on freebsd%0Abumping golang.org/x/text 71a9c9a...9db913a:%0A > 9db913a go.mod: update to newer x/tools%0A > 30dadde all: correct comment typos%0Abumping k8s.io/client-go 7226b15...6e9dabb:%0A > 6e9dabb Update dependencies to v0.26.5 tag%0A > 038b381 Merge pull request # 117691 from dims/re-do-of-117242-on-release-1.26%0A > cd83e43 Bump runc go module v1.1.4 -> v1.1.6%0A > dbfbc03 Merge pull request # 117686 from ardaguclu/automated-cherry-pick-of-# 117495-upstream-release-1.26%0A > d72dec4 Use absolute path instead requestURI in openapiv3 discovery%0A > a5144d4 Merge pull request # 117638 from seans3/automated-cherry-pick-of-# 117571-origin-release-1.26%0A > d6f8d04 Refactors discovery content-type and helper functions%0A > 2dd0093 Merge pull request # 115899 from odinuge/automated-cherry-pick-of-# 115620-upstream-release-1.26%0A > f3ae5cb Merge pull request # 116666 from seans3/automated-cherry-pick-of-# 116603-origin-release-1.26%0A > fffc68d Change where transformers are called.%0A > 5ebee18 Aggregated discovery resilient to nil GVK%0A > 8190aa4 client-go/cache: update Replace comment to be more clear%0A > 87720b3 Merge pull request # 116437 from seans3/automated-cherry-pick-of-# 116145-# 115865-origin-release-1.26%0A > b667227 client-go/cache: rewrite Replace to check queue first%0A > fc13749 Removes old discovery hack ignoring 403 and 404%0A > 30215cd client-go/cache: merge ReplaceMakesDeletionsForObjectsInQueue tests%0A > f39ba12 Plumb stale GroupVersions through aggregated discovery%0A > ba35969 client-go/cache: fix missing delete event on replace without knownObjects%0A > f538edf Merge pull request # 116352 from seans3/automated-cherry-pick-of-# 115978-origin-release-1.26%0A > 97cf9cb client-go/cache: fix missing delete event on replace%0A > 5dbbc58 Tolerate empty discovery response in memcache client%0A > 62133a9 Merge pull request # 115787 from liggitt/net-0.7.0-1.26%0A > 8ce239f Update golang.org/x/net to v0.7.0%0A > e6bc0bc Merge pull request # 115566 from enj/automated-cherry-pick-of-# 115315-upstream-release-1.26%0A > 9112e19 Merge pull request # 115400 from pohly/automated-cherry-pick-of-# 115354-origin-release-1.26%0A > 0519b53 kubelet/client: collapse transport wiring onto standard approach%0A > 2e34348 Merge pull request # 115642 from nckturner/pin-golang.org/x/net-to-v0.4.0-in-1.26%0A > 7be38cd dynamic resource allocation: avoid apiserver complaint about list content%0A > 4968c4a Pin golang.org/x/net to v0.4.0 in 1.26%0A > 0c34939 Merge pull request # 114617 from JoelSpeed/automated-cherry-pick-of-# 114585-upstream-release-1.26%0A > 04b098b Resource claims should be a map type%0A > b3fff46 Merge pull request # 114415 from hoskeri/automated-cherry-pick-of-# 114404-upstream-release-1.26%0A > 236db3c Merge pull request # 113988 from liggitt/automated-cherry-pick-of-# 113933-upstream-release-1.26%0A > a2ef324 Check the correct error in d.downloadAPIs%0A > 95a14c3 Merge remote-tracking branch 'origin/master' into release-1.26%0A > ebb499f Limit request retrying to []byte request bodies%0A > 1a7cd1d Update golang.org/x/net 1e63c2f%0A > 53f2fea sync: update go.mod%0A > 968ba8d Merge pull request # 113797 from seans3/force-no-aggregated%0A > c8ffed3 Merge pull request # 111023 from pohly/dynamic-resource-allocation%0A > 3ac73ea Adds bool to force non-aggregated discovery%0A > 61cd728 Merge pull request # 113826 from jsafrane/add-openstack%0A > 522eaa1 api: generated files%0A > cfd682c Merge pull request # 113375 from atiratree/PodHealthyPolicy-api%0A > f2b10f3 Remove OpenStack cloud provider%0A > acc9fa7 Merge pull request # 113186 from ttakahashi21/KEP-3294%0A > f1c80d7 generated%0A > a3d3eb0 Revert "Remove references to openstack and cinder"%0A > c7bdab2 Generate code%0A > 0a1f6a8 Merge pull request # 112744 from pwschuurman/statefulset-slice-impl%0A > 1c7a870 Merge pull request # 113485 from MikeSpreitzer/apf-borrowing%0A > eed2516 Adding implementation of KEP-3335, StatefulSetSlice%0A > 7280270 Merge pull request # 113599 from seans3/discovery-client-update%0A > d4a3675 apiserver: add generated files for borrowing in flowcontrol%0A > 7694435 Update redacting functionality to redact all sensitive info in config when printing with view (# 109189)%0A > 25d5761 Aggregated discovery client%0A > 4b1a9fd Merge pull request # 113314 from cici37/celIntegration%0A > ea9ec91 Merge pull request # 112905 from alexzielenski/kubectl-apply-csa-migration%0A > 3a430a4 API - make update%0A > 3daf180 Merge pull request # 113688 from dashpole/update_utils%0A > 898b7a3 add FindFieldsOwners util function%0A > dbe034b update k8s.io/utils to fix util tracing panic%0A > 4f63b62 add UpgradeManagedFieldsPatch%0A > 7ed3193 Merge pull request # 111545 from jlsong01/rewrite_signature_of_StartEventWatcher%0A > c8c6cb5 add OWNERS to csaupgrade%0A > cbe28cf Merge pull request # 113274 from Huang-Wei/kep-3521-A%0A > 3467961 rewrite signature of function StartEventWatcher%0A > a45874a remove kubectl annotation logic from upgrade patch%0A > 2248bf3 Automated codegen%0A > d576a35 Merge pull request # 113387 from wojtek-t/refactor_client_indexing%0A > 4fbef5b Merge pull request # 106242 from thockin/revive-copy-lb-status-type-to-ingress%0A > 5e7ba1f Minor cleanup of thread safe store%0A > bc6266d Merge pull request # 103177 from arkbriar/support_cancelable_exec_stream%0A > 3f162fe Copy LoadBalancerStatus from core to networking%0A > b69a16c Refactor store index into its structure%0A > 19b2e89 Merge pull request # 113523 from seans3/content-type-response%0A > 0563dec Propagate the panic with a channel%0A > 8ff4970 Get response content-type%0A > 2362c7b use subtests and defer in TestSPDYExecutorStream%0A > 0d57396 Merge pull request # 113304 from mimowo/handling-pod-failures-beta-ssa%0A > 5e0a531 Support cancelable SPDY executor stream%0A > a232cf0 Merge pull request # 113367 from pohly/dep-ginkgo-gomega%0A > a191e58 SSA to add pod failure conditions - ready for review%0A > 984bdbf dependencies: update to gomega v1.23.0 and ginkgo v2.4.0 and dependencies%0A > f87d047 Merge pull request # 112693 from aimuz/fix-GO-2022-0969%0A > d236783 Fixed (CVE-2022-27664) Bump golang.org/x/net to v0.1.1-0.20221027164007-c63010009c80%0A > ef8a2e5 Merge pull request # 113089 from zackzhangkai/fix-doc%0A > 197e479 Merge pull request # 108959 from astraw99/fix-duplicate-list%0A > 0945beb fix typo%0A > 42a0e1c Merge pull request # 113062 from alexzielenski/client-go-json-output%0A > f549acf Fix duplicate code block of ListAll function%0A > b6d3c8d Merge pull request # 107278 from harsimranmaan/allow_pagination_in_dynamic_fake_lister%0A > 624929c address feedback%0A > 9cc33a4 Merge pull request # 113106 from pohly/dep-ginkgo-gomega%0A > 0c269b7 remove selflink as per review feedback%0A > 12cafe2 refactor to use Schema(contentType)%0A > 9b51067 dependencies: update to gomega v1.22.1 and ginkgo v2.3.1%0A > fbd8e9a fix failing test assertions%0A > 8b6ceae add more options for fetching openapiv3 in clients%0A > fa9ed7f Merge pull request # 112860 from nckturner/remove-log-line%0A > 1f10368 Preserve metadata for fake dynamic client unstructured lists%0A > 6b24912 Merge pull request # 112988 from alexzielenski/update-kube-openapi%0A > 5870c62 Remove log line from expiration cache%0A > aea20dd Merge pull request # 113037 from pacoxu/fsnotify-v1.6.0%0A > e3bb48f update kube-openapi%0A > 1af3711 update fsnotify to v1.6.0%0A > e6d958c Merge pull request # 112989 from ameukam/bump-golang.org/x/text-to-v0.3.8%0A > 5e469ba Bump golang.org/x/text to v0.3.8%0A > f515a4c Merge pull request # 112774 from stevekuznetsov/skuznets/dynamic-client-similar%0A > b28f6c9 Merge pull request # 112875 from pohly/update-yaml%0A > 34e8a5d client-go: factor the dynamic client similarly to others%0A > c9afc73 dependencies: update to sigs.k8s.io/yaml v1.3.0%0A > f24bd69 Merge pull request # 112306 from tkashem/v1beta3%0A > ebc7cd4 Merge pull request # 112707 from enj/enj/i/https_links%0A > 9b97b72 rename assuredConcurrencyShares for flowcontrol v1beta3%0A > 2f43d37 Merge pull request # 112705 from stevekuznetsov/skuznets/fix-comment%0A > 1665808 Use https links for k8s KEPs, issues, PRs, etc%0A > 9bac803 apiserver: generate for apf v1beta3%0A > 3697342 Merge pull request # 112680 from enj/enj/i/tls_cache_key_comparable%0A > 956c1ce clients: clarify a misleading comment%0A > c81636c Merge pull request # 112665 from NoicFank/fix-typo%0A > cc2441c transport/cache: statically assert that tlsCacheKey is comparable%0A > be20b2b Merge pull request # 112673 from dims/update-to-latest-k8s.io/utils-sep-22%0A > 59765b8 fix typo error%0A > 04dbcd8 Update to latest k8s.io/utils to pick up changes%0A > 2fd4aac Merge pull request # 112613 from dims/update-github.com/go-openapi/jsonreference-to-drop-github.com/PuerkitoBio/purell%0A > 47ad72a update github.com/go-openapi/jsonreference to drop github.com/PuerkitoBio/purell%0A > f7c9c63 Merge pull request # 112545 from dims/update-etcd-3.5.5-and-all-otel-related-to-latest%0A > b6e72dc Merge pull request # 112226 from aojea/client_go_transport%0A > 6b5ecad updated etcd to v3.5.5 and newer otel libraries as well%0A > acfaa39 Merge pull request # 112352 from pohly/e2e-ginkgo-progress%0A > 1bd914a client-go: test transport generation is goroutine safe%0A > 037b5fd Merge pull request # 112514 from markmc/patch-1%0A > ec6c80a e2e: bump ginkgo to v2.2.0%0A > 3f66212 client-go: remove reference to TPR in examples%0A > 86ffa32 Merge pull request # 112475 from vatsalparekh/fix-TestRESTClientLimiter%0A > ece6462 Merge pull request # 112476 from enj/enj/i/list_pager_flake%0A > bf2b395 Fix Infelicities in TestRESTClientLimiter%0A > 58155b7 Merge pull request # 112450 from enj/enj/i/exec_tls_cache_holder_cleanup%0A > 6703098 Check for context cancellation on each buffered chunk%0A > eecd3e5 Merge pull request # 112091 from xyz-li/master%0A > 5dab9a0 client-go/transport: drop Dial and GetCert fields in favor of Holders%0A > f6b8521 Merge pull request # 111333 from flant/selfsubjectattributesreviews%0A > cc3cc93 kubectl: fix memory leaks in port forwarding client%0A > b2b55e6 Add auth API to get self subject attributes%0A > 18c3338 Merge pull request # 112200 from pohly/client-go-shared-informer-factory-shutdown%0A > 9dae691 Merge pull request # 112309 from shyamjvs/disable-compression%0A > ec4fedd client-go: support waiting for SharedInformerFactory shutdown%0A > ab826d2 Merge pull request # 112349 from pohly/klog-update%0A > 49ac40b Autogen code%0A > ab0bfda build: update to klog v2.80.1%0A > b8a8d94 Add DisableCompression option to KubeConfig%0A > f32861c Merge pull request # 112341 from enj/enj/i/second_time_is_the_charm%0A > 7d208ba Remove in-tree credential plugins (again)%0A > e003fa9 Merge pull request # 112017 from enj/enj/i/exec_tls_cache%0A > 2698e82 Merge pull request # 111967 from alexzielenski/csa-to-ssa%0A > 6a008ec exec auth: support TLS config caching%0A > 27c67e7 Merge pull request # 111122 from alexzielenski/informer%0A > 00d892f correct spacing%0A > d28c736 Merge pull request # 112022 from JackZxj/release-lock%0A > a300ae0 return when test is done%0A > 2efbeaf add boilerplate%0A > b8b6206 Merge pull request # 112199 from pohly/klog-update%0A > d04c2ce update lock getter of leaderelection%0A > 93e5e0e hold listener lock while waiting for goroutines to finish%0A > dac0826 remove inaccurate comment%0A > 5a2c3e9 dependencies: update to klog v2.80.0%0A > e11a988 simplify control flow%0A > 7634f2e make upgrade modify input instead of deep copying%0A > 7ccf7b0 Merge pull request # 112134 from apelisse/client-go-valid-segment%0A > ac7f657 fix spelling%0A > 9aa7c11 remove fieldsv1 from upgrade body%0A > d83ec9e Merge pull request # 112129 from pohly/e2e-ginkgo-report-after-each%0A > a4b84d8 Validate segments with client-go/dynamic%0A > 0f4a6cf reset listenersStarted%0A > 703d15e Update staging/src/k8s.io/client-go/util/csaupgrade/upgrade.go%0A > cac10a8 dependencies: update to ginkgo v2.1.6 and gomega v1.20.1%0A > 449817f add multithreaded test to shared informer%0A > 675ca93 refactor if statement%0A > 46d4284 Merge pull request # 111241 from Abirdcfly/fixtestorsource%0A > de0b767 remove duplicate test%0A > cfaca90 address comments%0A > bdae576 Merge pull request # 112068 from aojea/aojea_client_go%0A > 9b300de make TestListPager_EachListItem rework%0A > 0565962 address review comments%0A > 089614c remove last applied configuration information%0A > fd22687 add aojea as client-go reviewer%0A > 5a25eb0 switch listeners to use a map, adapt tests%0A > efe3789 add more test cases%0A > 35ead05 Merge pull request # 112052 from tosi3k/bump-client-golang%0A > 90c6a46 active remove/add tests for event handlers%0A > 46dc22f clean up test%0A > 5291ca2 Bump prometheus/client_golang to v1.13.0%0A > de4dd3a tests for invalid registration removals%0A > ced85a8 update godoc%0A > e6538dd Merge pull request # 112024 from cndoit18/remove-redundant-judgment%0A > 33eff64 apply desired changes for handler registration%0A > 049ba69 expose FieldsToSet and SetToFields%0A > bcd2e6c style: remove redundant judgment%0A > d73e40f rename handle to registration%0A > aa892ab remove unused code%0A > d5e5863 Merge pull request # 111752 from aanm/revert-final-url-template%0A > b3a61c6 remove informational informer methods again%0A > 90ef078 dont expose internal methods in implementatoin%0A > 5feaced Merge pull request # 67782 from dims/yank-in-tree-openstack-cloud-provider%0A > e9d4627 client-go/rest: check if url is nil to prevent nil pointer dereference%0A > ecdc8bf support removal of event handlers from SharedIndexInformers%0A > c364b63 add function to upgrade managedfields CSA to SSA%0A > 0fdc4f3 Merge pull request # 111684 from 0xff-dev/master1%0A > 98e81a7 Remove references to openstack and cinder%0A > c501ee0 Revert "client-go: remove no longer used finalURLTemplate"%0A > 4faffa8 Merge pull request # 111564 from inosato/remove-ioutil-from-cli-client-go%0A > c94a539 use constant NamespaceDefault instead of variable namespace%0A > 2e40408 Merge pull request # 111918 from liggitt/in-tree-auth%0A > 27de641 Remove ioutil from client-go%0Abumping k8s.io/apiextensions-apiserver 2c55649...52c998e:%0A > 52c998e Update dependencies to v0.26.5 tag%0A > 186ff9b Merge pull request # 117274 from jkh52/release-1.26-knp-0.0.37%0A > b7b18f5 Merge pull request # 117691 from dims/re-do-of-117242-on-release-1.26%0A > ee5015a Bump konnectivity-client to 0.0.37%0A > 9ce75f3 Bump runc go module v1.1.4 -> v1.1.6%0A > e9d194a Merge pull request # 115599 from jkh52/release-1.26-knp-0.0.36%0A > d7df0be Merge pull request # 115787 from liggitt/net-0.7.0-1.26%0A > 9152c67 Bump konnectivity-client to v0.0.36%0A > 89cec57 Update golang.org/x/net to v0.7.0%0A > f72cc5c Merge pull request # 115642 from nckturner/pin-golang.org/x/net-to-v0.4.0-in-1.26%0A > 28eb995 Pin golang.org/x/net to v0.4.0 in 1.26%0A > 33db789 Merge pull request # 114861 from jpbetz/release-1.26%0A > a06e03d Merge pull request # 114927 from jkh52/release-1.26-knp-metrics%0A > 0859963 Cherry pick 114857 to release-1.26%0A > 5183885 Bump konnectivity-client to v0.0.35%0A > 6e13726 Merge remote-tracking branch 'origin/master' into release-1.26%0A > c338f3e Update golang.org/x/net 1e63c2f%0A > 9768bad sync: update go.mod%0A > f9c2bba fix aggregated discovery version sorting%0A > d2c9e18 Merge pull request # 113171 from Jefftree/aggregated-discovery-generic%0A > 470c040 Merge pull request # 113577 from pacoxu/prometheus-client%0A > 915a888 add crds to aggregated discovery%0A > 92430b6 Merge pull request # 113314 from cici37/celIntegration%0A > ac326ca upgrade prometheus-client to v1.14.0%0A > 5a6bf16 Merge pull request # 113688 from dashpole/update_utils%0A > 67b0610 Integrate cel admission with API.%0A > 84fed82 upgrade github.com/prometheus/client_golang to v1.13.1%0A > 077b441 update k8s.io/utils to fix util tracing panic%0A > 5bbf20d Adding new api version of admissionregistration.k8s.io v1alpha1 for CEL in Admission Control%0A > 3b533ba Merge pull request # 113367 from pohly/dep-ginkgo-gomega%0A > 975bbeb dependencies: update to gomega v1.23.0 and ginkgo v2.4.0 and dependencies%0A > ae2b4c3 Merge pull request # 112693 from aimuz/fix-GO-2022-0969%0A > c4deae9 Fixed (CVE-2022-27664) Bump golang.org/x/net to v0.1.1-0.20221027164007-c63010009c80%0A > bc4263f Merge pull request # 113172 from dashpole/endpoint_handler_tracing%0A > f6c164e migrate apiserver utiltrace usage to component-base/tracing%0A > 53e3726 Merge pull request # 113015 from ritazh/crencryption%0A > c8d8a9f Enable encryption for custom resources%0A > 6405068 Merge pull request # 113325 from panslava/fix-time-since-defer%0A > 508e399 Fix time.Since() in defer. Wrap in anonymous function%0A > 5f8e59e Merge pull request # 112691 from aimuz/apiextensions-apiserver-change-to-cmp%0A > c996139 Merge pull request # 113106 from pohly/dep-ginkgo-gomega%0A > f83e03c apiextensions-apiserver: change k8s.io/apimachinery/pkg/util/diff to github.com/google/go-cmp/cmp%0A > b68fc51 dependencies: update to gomega v1.22.1 and ginkgo v2.3.1%0A > 49c41b4 Merge pull request # 112988 from alexzielenski/update-kube-openapi%0A > 3aaa2a0 Merge pull request # 113037 from pacoxu/fsnotify-v1.6.0%0A > d9f6ebd update kube-openapi%0A > 82e3ba4 Merge pull request # 112789 from enj/enj/r/kms_load_once_v2%0A > 7423813 update fsnotify to v1.6.0%0A > 8bf3487 Merge pull request # 113011 from jpmcb/cobra-1.6.0%0A > d34393e Load encryption config once%0A > 6ba582f Bumps cobra from 1.5.0 to 1.6.0%0A > 8e0697b Merge pull request # 113022 from logicalhan/webhook-metrics%0A > 90c63e0 Merge pull request # 112926 from jiahuif-forks/refactor/cel-out-of-apiextensions%0A > 548c480 unparameterize 'webhook' from conversion metrics since it's the only one%0A > 77badb8 Merge pull request # 112989 from ameukam/bump-golang.org/x/text-to-v0.3.8%0A > 609e270 use DefaultMaxRequestSizeBytes for maxRequestSizeBytes.%0A > 04f26fa Bump golang.org/x/text to v0.3.8%0A > dd981e1 move CEL package to apiserver package.%0A > 1644998 Move celopenapi/model to staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/ (# 109959)%0A > 08d44e8 Merge pull request # 112875 from pohly/update-yaml%0A > 1300140 dependencies: update to sigs.k8s.io/yaml v1.3.0%0A > 5fb82bd Merge pull request # 112819 from thockin/no-make-generators%0A > f5f5279 Codegens: Do not auto-set boilerplate path%0A > f22ee73 Merge pull request # 112738 from liggitt/proto-tag%0A > ba7f1b7 Merge pull request # 112689 from cheftako/master%0A > 7ac7774 github.com/matttproud/golang_protobuf_extensions v1.0.2%0A > e678457 Merge pull request # 112748 from wojtek-t/lock_ssa_gate%0A > 0aca5a6 Bump konnectivity-client to v0.0.33%0A > 9be4b4a Lock ServerSideApply feature to true%0A > 7b53cb7 Merge pull request # 111980 from aramase/kms%0A > f40a683 Merge pull request # 112705 from stevekuznetsov/skuznets/fix-comment%0A > 4cd9125 Add staging directory for kms%0A > d4e654a clients: clarify a misleading comment%0A > 8b851d9 Merge pull request # 112673 from dims/update-to-latest-k8s.io/utils-sep-22%0A > 362a89c Merge pull request # 112615 from mengjiao-liu/update_CRD_link%0A > add0c80 Update to latest k8s.io/utils to pick up changes%0A > 374216b Merge pull request # 112613 from dims/update-github.com/go-openapi/jsonreference-to-drop-github.com/PuerkitoBio/purell%0A > a7ee7f9 Update PreserveUnknownFields field document link%0A > 488bf20 update github.com/go-openapi/jsonreference to drop github.com/PuerkitoBio/purell%0A > 47c15ca Merge pull request # 112588 from pacoxu/fsnotify-v1.5.4%0A > d5b6243 Merge pull request # 112584 from dims/brneto-master%0A > 8c6aa82 update fsnotify/fsnotify to v1.5.4%0A > f8e18e9 run pin-dependency.sh and then hack/update-vendor.sh%0A > c540c8c Merge pull request # 112545 from dims/update-etcd-3.5.5-and-all-otel-related-to-latest%0A > 70b0d96 Merge pull request # 112352 from pohly/e2e-ginkgo-progress%0A > 39cab0b updated etcd to v3.5.5 and newer otel libraries as well%0A > 5faccda Merge pull request # 111866 from pacoxu/validate%0A > 1c3fe9d e2e: bump ginkgo to v2.2.0%0A > 917d446 Merge pull request # 112458 from dims/switch-to-release-tag-for-antlr-v1.4.10%0A > 8b3fe74 add test case for array checking with dup values%0A > 045fc90 Merge pull request # 112433 from ncdc/reduce-SchemaHas-allocs%0A > 73cc883 Switch to release tag for antlr : v1.4.10%0A > 22bcc66 added ratcheting validation for embedded resource and x-kubernetes-list-type validation%0A > 269d73d Reduce allocations in HasSchemas%0A > 7342cc6 Merge pull request # 112200 from pohly/client-go-shared-informer-factory-shutdown%0A > aabbdff Merge pull request # 112349 from pohly/klog-update%0A > fdf28bc client-go: support waiting for SharedInformerFactory shutdown%0A > 6b7d12b build: update to klog v2.80.1%0A > 559b4fa Merge pull request # 111768 from weilaaa/feature_add_symmetric_difference_in_sets_string%0A > bf7d058 add symmetric difference in sets%0A > 04ff81e Merge pull request # 112199 from pohly/klog-update%0A > 87a4c3f dependencies: update to klog v2.80.0%0A > 8f15690 Merge pull request # 112129 from pohly/e2e-ginkgo-report-after-each%0A > f637e1c dependencies: update to ginkgo v2.1.6 and gomega v1.20.1%0A > b6adc1c Merge pull request # 111964 from DangerOnTheRanger/cel-estimate-fix-update%0A > ea2d438 Merge pull request # 112052 from tosi3k/bump-client-golang%0A > 6b4dc0b Add unit tests.%0A > 767e67b Bump prometheus/client_golang to v1.13.0%0A > 782b982 Run pin-dependency.sh and update-vendor.sh.%0A > 305963e Merge pull request # 111909 from tosi3k/bump-prom-client%0A > fa2959a Merge pull request # 111830 from t1anz0ng/typo%0A > 5a6ffec Bump prometheus/client_golang to v1.12.2%0A > e0abc3b fix(typo): remove extra " from autoscaling doc string%0A > 2184a8d Merge pull request # 111696 from liggitt/go119mod%0A > f750907 Update go.mod to go1.19%0Abumping golang.org/x/term d974fe8...0edf009:%0A > 0edf009 go.mod: update golang.org/x dependencies%0Abumping github.com/fsnotify/fsnotify 0f4b979...5f8c606:%0A > 5f8c606 Update ChangeLog%0A > 8878587 Tweak the docs a bit%0A > 89b4cf1 Add test for re-adding a renamed file (# 508)%0A > 85acde2 Update x/sys%0A > 69c24b0 Update x/sys%0A > fb07f82 Add test to see what happens if you watch a symlink (# 498)%0A > 666da9c Clarify doc comment on WatchList() (# 499)%0A > 123e4e3 Add note about README version%0A > 61a05ce Update documentation and examples (# 496)%0A > e180a87 Move some inotify-tests to run on all backends; test that state is cleaned up after Remove (# 494)%0A > fdf41a3 Move some files around%0A > 844d71f Port minor test changes from fen-v2 branch; make LICENSE text not ugly%0A > 5b87f50 windows: simplify a bit (# 493)%0A > 2bfaa00 all: add Watcher.{sendEvent,sendError} (# 492)%0A > 8ab3b84 kqueue: don't set up watchers on unreadable files (# 479)%0A > a4bcdf8 Update changelog%0A > 4b43fad kqueue: remove timeout from unix.Kevent() (# 480)%0A > a24f78c windows: test symlinks (# 491)%0A > f45391f windows: run TestWatchRename/rename_overwriting_existing_file (# 490)%0A > ee33a65 Use "os.Rename()" in tests instead of "mv"%0A > 9dd0568 cmd/fsnotify: fix time.Format() string%0A > 5dcbfba windows: replace syscall with golang.org/x/sys/windows%0A > 1f8edaf windows: replace "e" with "err" for error variables%0A > 99715ba windows: increase buffer size from 4K to 64K (# 485)%0A > a5c5815 ci: update to use Go 1.19, kick off fewer builds, update x/sys (# 484)%0A > f2d35c3 Remove CLA section in contributing%0A > 4604469 Need Linux 5.9 for a useful fanotify we can use%0A > a566bb1 Update CONTRIBUTING.md%0A > 01dfc6f Remove PULL_REQUEST_TEMPLATE%0A > a58e868 Run tests in illumos (# 481)%0A > 666c6a0 Update ChangeLog%0A > 928895c [bugfix] close handle when remWatch open in getIno (# 288)%0A > f174f95 windows: update watch paths when renaming directories with sub-watches (# 370)%0A > 87dc1fa Rewrite tests (# 478)%0A > 57e6a49 Add {Event,Op}.Has() (# 477)%0A > 39823aa Document that /proc and /sys won't work%0A > 60fbf57 Clarify FAQ on goroutines%0A > ca0e2f4 macos: retry if open() returns EINTR (# 475)%0A > ff39bb4 Fix lint (# 476)%0A > 421f529 debian 6 test: deal with multiple packages (# 474)%0A > a3256ef Remove AUTHORS file%0A > 0e78fa6 Update README: split out FAQ to "Platform-specific notes"%0A > 1a7b6ef inotify: don't ignore events for files that don't exist (# 470)%0A > f0aceb2 Tweak comment regarding relative paths (# 466)%0A > d9c9fa5 Add cmd/fsnotify (# 463)%0A > cc15908 kqueue: better error if watching a file fails (# 471)%0A > c4e64e4 Replace Use of Kthread-blocking Epoll with Poller Read, Remove Per-Event LStats on Linux # 433 (# 434)%0A > 4b8b298 Test some more things in CI (# 469)%0A > 548b8fb Add missing changelog for 1.4.{8,9} (# 468)%0A > 7fe2936 inotify: fix race in Close() (# 465)%0A > 35b6378 Clarify README on network drives (# 467)%0A > e56409e Update link to CONTRIBUTING in the README (# 464)%0A > 4678dfd Update documentation for linux systems (max_user_watches) (# 287)%0A > 808f582 bump up GitHub Actions (# 461)%0A > 4193dfd Do not suppress Chmod on non-existent file (# 260)%0A > 6ae56b7 kqueue: Make watcher.Close() O(n) instead of O(n^2) (# 233)%0A > adf5320 strings.Builder instead of bytes.Buffer (# 285)%0A > 217e78e Explicit mutext (un)locking (# 462)%0A > 1a4f949 Use common error when removing an unwatched file (# 460)%0A > 5acfdc1 windows: protect access to isClosed with mutex (# 454)%0A > c56cafd Test Go 1.18%0A > 37badf6 This project is archived (# 459)%0Abumping knative.dev/networking e5d04e8...b9dd5c2:%0A > b9dd5c2 upgrade to latest dependencies (# 816)%0A > 68947c5 upgrade to latest dependencies (# 815)%0A > 14a2bd4 Move pkg/certificates from control-protocol to networking (# 802)%0A > 2daa483 Update community files (# 813)%0A > 0dbe4f9 upgrade to latest dependencies (# 812)%0A > 2a2f7d2 upgrade to latest dependencies (# 810)%0A > fcbedad Update community files (# 809)%0A > a44b093 upgrade to latest dependencies (# 808)%0A > 7c2f7ac upgrade to latest dependencies (# 807)%0A > 33636d9 Backward compatibility for InternalEncryption (# 806)%0A > 77975a1 Add the new certificate names for dataplane and controlplane (# 804)%0A > c3cca43 upgrade to latest dependencies (# 803)%0A > 3f4627e Add internal trust flag to config (# 778)%0A > 02055c8 Update community files (# 801)%0A > 68725bd upgrade to latest dependencies (# 798)%0A > 1594abb Update community files (# 797)%0Abumping knative.dev/pkg dfad48e...6eb4b40:%0A > 6eb4b40 Update community files (# 2760)%0A > eb63a40 Support to set qps and burst via env variable (# 2755)%0A > 74c4be5 Generate kresource duck type codegen (# 2754)%0A > 4dbc312 fix boilerplate (# 2753)%0A > 15605c7 Defaulting Controller options for all kind of webhooks (# 2738)%0A > 94b81fc Update community files (# 2752)%0A > 5671699 drop the dynamic type (# 2750)%0A > 9bda38b Fix some webhook testing tech debt (# 2751)%0A > ec20442 Update community files (# 2747)%0A > 05bfcf6 bump k8s dependencies and update min version to v1.25 (# 2745)%0A > 52ff2ac drop dynamic client wrappers (# 2744)%0A > a170a07 Eventing TLS: validate that Destination.CACerts is a PEM encoded cert (# 2743)%0A > dfb4bf0 Drop dynamic wrapper injection code generation (# 2742)%0A > db8a353 Add SinkCACerts to SourceStatus (# 2733)%0A > 9049667 Update community files (# 2735)%0A > aacec7f Update community files (# 2734)%0A > 300df43 Eventing TLS: Added AddressableFromDestination method on the resolver (# 2717)%0Abumping github.com/matttproud/golang_protobuf_extensions c182aff...c182aff:%0Abumping knative.dev/hack f591fea...fc42790:%0A > fc42790 Update community files (# 296)%0A > d7586a2 Update e2e kntest link (# 295)%0A > a861c8e Update community files (# 294)%0A > 5b7907f Update actions (# 289)%0A > c133d5d Install Istio for tests (# 291)%0A > 5812c57 Update community files (# 292)%0A > 7d81248 Update community files (# 286)%0A > 6e4569c Update community files (# 285)%0Abumping golang.org/x/net 8e2b117...dfa2b5d:%0A > dfa2b5d go.mod: update golang.org/x dependencies%0A > 8c4ef2f hmtl: add security section to package comment%0A > 1d46ed8 html: have Render escape comments less often%0A > 569fe81 html: add "Microsoft Outlook comment" tests%0Abumping knative.dev/eventing 034bec9...f5b1b12:%0A > f5b1b12 Send namespace header in MT components (# 7048)%0A > 4b5fde8 [main] Update community files (# 7043)%0A > 8f74094 Add handler to auto create Event Types (# 7034)%0A > 901ef61 Remove check for empty Namespace on resolver (# 7040)%0A > 95cdbaa We should not limit the EventType creation from the Sources Duck to just brokers (# 7032)%0A > 7429761 Adjust the Namespace reference to the one from the parent (# 7035)%0A > cb2a891 update the redeployment script (# 7038)%0A > ab01938 [main] Upgrade to latest dependencies (# 7025)%0A > c9dcaf3 Added basic gc loop to kncloudevents clients map (# 6997)%0A > d6cf96d EventType works with channel (# 7023)%0A > 365d0b0 Run TLS e2e tests only when Istio is not enabled (# 7029)%0A > 825a237 Update IMC CRD addressstatus to include .name and .CACerts fields (# 7026)%0A > 3190df7 Tracking/reconcile KResource references (# 7014)%0A > 0f68861 Rename more to Resource, instead of broker (# 7022)%0A > bccb7d4 Better reflecting the lifecycle of event type … (# 7019)%0A > 49d4acd Skip ping source TLS rekt test, since extremely flaky (# 7016)%0A > 8719e18 [main] Upgrade to latest dependencies (# 7012)%0A > e5ae717 Use HTTP POST when terminating istio proxy (# 7015)%0A > fea730f Only check if the reference does exist (# 7010)%0A > 631f4ec Add TLS support for mt-broker-filter (# 6940)%0A > 45f0a19 Allow wathola components to run with Istio (# 7011)%0A > 65f4b1c [main] Format Go code (# 7008)%0A > 3267b1a test SinkBinding with eventshub TLS receiver as sink (# 6979)%0A > aad53f4 Updated eventingtls test certs to support IP addresses (# 7006)%0A > 57d78e0 [main] Update community files (# 7004)%0A > dfb2243 Support TLS in Trigger and Channel reconciler (# 6988)%0A > df08b49 Eventing TLS: verify APIServerSource and PingSource sinkURI is https (# 6987)%0A > d21c1aa [main] Upgrade to latest dependencies (# 6989)%0A > 70113e8 Deprecate broker field and use KReference for the broker instead (# 6870)%0A > 4e4647f test update to newest version (# 6990)%0A > 870ac6b Update MessageDispatcher and FanoutMessageHandler to support sending events to TLS endpoints (# 6983)%0A > 6dd5d58 Test PingSource with eventshub TLS receiver as sink (# 6965)%0A > 55f4f28 [main] Upgrade to latest dependencies (# 6982)%0A > 2a5a9a5 Add more items in the development getting started documentation (# 6978)%0A > 59118a0 imc-dispatcher starts a TLS server, accepts host based routing on http receiver and path based routing on https receiver (# 6954)%0A > ee49ada Rework kncloudevents library to support multiple clients (# 6975)%0A > ee88094 Make ServerManager independent from kncloudevents package (# 6980)%0A > 6a11c5f [main] Upgrade to latest dependencies (# 6969)%0A > 8a9a532 Updated DEVELOPMENT.md to provide better instructions on setting up kubernetes (# 6977)%0A > 390a0c8 Eventing TLS: Test ContainerSource with eventshub TLS receiver as sink (# 6957)%0A > 5e245ac Fix flaky PingSource TLS unit test (# 6970)%0A > f9f27c9 Use random names in Channel tests (# 6967)%0A > d4609a5 Do not parse flags in InitializeEventingFlags (# 6966)%0A > ef68a0a [main] Update community files (# 6968)%0A > 4adc287 Add transport-encryption prerequisite for Addressable tests (# 6964)%0A > deb0ef4 Add field for subscribers & replys CA certs to SubscriberSpec and SubscriptionStatusPhysicalSubscription (# 6959)%0A > b81082c Eventing TLS: Test ApiServerSource with eventshub TLS receiver as sink (# 6956)%0A > cdff269 Adding source duck type to v1b2 (# 6962)%0A > b47b4ec [main] Upgrade to latest dependencies (# 6958)%0A > 3315c20 Provide Channels CACerts in Brokers status annotation (# 6952)%0A > 4b9fdef [main] Upgrade to latest dependencies (# 6955)%0A > da31970 Improve cert-manager resources for Eventing TLS certs provisioning (# 6953)%0A > fc5befb Provide subscribers CACerts in triggers status (# 6951)%0A > 1efab19 Using v1b2 in the reconciler (# 6949)%0A > c44671c Updating rekt test resources for EventType v1b2 (# 6946)%0A > e31eb1f Adding testingv1b2 for eventtype (# 6944)%0A > a9908ef Support TLS in PingSource (# 6929)%0A > df559c0 Fix typo in flags.IsDisbledTransportEncryption name (# 6941)%0A > 7073cc9 [main] Upgrade to latest dependencies (# 6939)%0A > c6bc9bb Eventing TLS: Support K_CA_CERTS env variable injection for SinkBinding subjects (# 6931)%0A > 24fbfe5 Eventing TLS: support exposing https address in Broker controller (# 6930)%0A > d18cb42 Add information about retryable error in servermanager (# 6921)%0A > f92a05b Added Support for K_CA_CERTS in the heartbeats (# 6920)%0A > b8b43d0 Remove CA certs empty and non nil check, use URL scheme only (# 6928)%0A > 3c8cc05 Return error directly if one receiver of servermanager fails (# 6919)%0A > 92ab7f8 [main] Upgrade to latest dependencies (# 6927)%0A > 5c6fe57 two more for reducing to debug, instead of info (# 6922)%0A > 6cf9397 less verbose logs on scheduler component (# 6912)%0A > 69918f2 Adds ServerManager. Supports http/https message receivers (# 6908)%0A > d58e259 Install ko using setup-ko in kind e2e tests (# 6910)%0A > 9cdea5d Eventing TLS: Added Support for setting K_CA_CERTS in the ApiServerSource controller for the adapter (# 6897)%0A > add8436 Eventing TLS: support exposing https address in InMemoryChannel controller (# 6881)%0A > 59cfb6d [main] Upgrade to latest dependencies (# 6906)%0A > 03f2a3d Remove unused test helper (# 6907)%0A > 7a90c46 Remove eventing-natss from downstream tests (# 6905)%0A > ba2550b [main] Upgrade to latest dependencies (# 6904)%0A > 999eead More EventType v1beta2 work (# 6903)%0A > 66e8257 Remove sanitize HTTP body for knativeerrordata extension (# 6902)%0A > cd50d27 [main] Format Go code (# 6898)%0A > 0f0a82c [main] Update community files (# 6901)%0A > 7f4deb5 EventType v1b2 API addition (# 6893)%0A > 1f917d0 Refactor PingSource adapter client creation (# 6880)%0A > e2f1c77 [main] Update community files (# 6896)%0A > 6a5c7ee Eventing TLS: migrate all resolver.URIResolver usages over to AddressableFromDestinationV1 (# 6883)%0A > 0a12a6c Adds path based routing to message_receiver pkg (# 6873)%0Abumping k8s.io/apimachinery 4fbe8e4...b207ce5:%0A > b207ce5 Merge pull request # 117691 from dims/re-do-of-117242-on-release-1.26%0A > 917de35 Bump runc go module v1.1.4 -> v1.1.6%0A > 53ecdf0 Merge pull request # 115787 from liggitt/net-0.7.0-1.26%0A > 05339fa Update golang.org/x/net to v0.7.0%0A > eabbfd5 Merge pull request # 115642 from nckturner/pin-golang.org/x/net-to-v0.4.0-in-1.26%0A > 48b8d1f Pin golang.org/x/net to v0.4.0 in 1.26%0A > 373a5f7 Merge pull request # 114521 from 3point2/automated-cherry-pick-of-# 113283-upstream-release-1.26%0A > b5e5df6 Fix SPDY proxy authentication with special chars%0A > 553a2d6 Improve error message when proxy connection fails%0A > 5d4cdd2 Merge remote-tracking branch 'origin/master' into release-1.26%0A > 6cbc4a3 Update golang.org/x/net 1e63c2f%0A > 6561235 Merge pull request # 113699 from liggitt/manjusaka/fix-107415%0A > dad8cd8 Update workload selector validation%0A > fe82462 Add extra value validation for matchExpression field in LabelSelector%0A > 067949d update k8s.io/utils to fix util tracing panic%0A > 0ceff90 Merge pull request # 112223 from astraw99/fix-ownerRef-validate%0A > 9e85d3a Merge pull request # 112649 from howardjohn/set/optimize-everything-nothing%0A > b0dd9ec Fix ownerRef controller validate err%0A > b03a432 Merge pull request # 113367 from pohly/dep-ginkgo-gomega%0A > 88a1448 Rename and comment on why sharing is safe%0A > 4e6bcdb dependencies: update to gomega v1.23.0 and ginkgo v2.4.0 and dependencies%0A > 3adc870 Optimize Everything and Nothing label selectors%0A > 0524d6c Merge pull request # 112693 from aimuz/fix-GO-2022-0969%0A > 5a0277f Fixed (CVE-2022-27664) Bump golang.org/x/net to v0.1.1-0.20221027164007-c63010009c80%0A > 6809593 Merge pull request # 112377 from weilaaa/refactor_sets_use_generic%0A > 70a38aa Merge pull request # 113106 from pohly/dep-ginkgo-gomega%0A > f2d9aed refactor sets use generic%0A > d097f82 dependencies: update to gomega v1.22.1 and ginkgo v2.3.1%0A > 7b5633b Merge pull request # 112988 from alexzielenski/update-kube-openapi%0A > b839e82 Merge pull request # 113037 from pacoxu/fsnotify-v1.6.0%0A > b7d8973 update kube-openapi%0A > 1dc6ace update fsnotify to v1.6.0%0A > 78d003c Merge pull request # 112989 from ameukam/bump-golang.org/x/text-to-v0.3.8%0A > 04898ff Bump golang.org/x/text to v0.3.8%0A > 79993b2 Merge pull request # 112875 from pohly/update-yaml%0A > 7379c15 dependencies: update to sigs.k8s.io/yaml v1.3.0%0A > 66e26ac Merge pull request # 112707 from enj/enj/i/https_links%0A > 882b67d Use https links for k8s KEPs, issues, PRs, etc%0A > 7fb78ee Merge pull request # 112472 from ialidzhikov/nit/error-msg%0A > 826a74e Merge pull request # 112673 from dims/update-to-latest-k8s.io/utils-sep-22%0A > 22fe889 Improve the error returned from the LabelSelectorAsSelector func%0A > e2f9797 Update to latest k8s.io/utils to pick up changes%0A > f8159af Merge pull request # 112545 from dims/update-etcd-3.5.5-and-all-otel-related-to-latest%0A > 612703e Merge pull request # 112352 from pohly/e2e-ginkgo-progress%0A > 9901884 updated etcd to v3.5.5 and newer otel libraries as well%0A > 6439059 Merge pull request # 112526 from liggitt/redirect%0A > 0564b5e e2e: bump ginkgo to v2.2.0%0A > 2e3bf73 Limit redirect proxy handling to redirected responses%0A > 6d854d7 Merge pull request # 112349 from pohly/klog-update%0A > e1e1b7c build: update to klog v2.80.1%0A > ed93eed Merge pull request # 111768 from weilaaa/feature_add_symmetric_difference_in_sets_string%0A > 36163c5 Merge pull request # 112193 from jindijamie/master%0A > b7b9ba4 add symmetric difference in sets%0A > 31bc292 Merge pull request # 112199 from pohly/klog-update%0A > 1c318b6 Add an option for aggregator%0A > 0d0d03e Merge pull request # 111936 from haoruan/bugfix-111928-microtime-marshal-precision%0A > 145c075 dependencies: update to klog v2.80.0%0A > 2d64dac Merge pull request # 112089 from zeze1004/fix-typo%0A > 2187a78 Marshal MicroTime to json and proto at the same precision%0A > 53c4d51 Merge pull request # 112129 from pohly/e2e-ginkgo-report-after-each%0A > 30e9977 Fix typo "sturct" to "struct"%0A > 5e4f25a dependencies: update to ginkgo v2.1.6 and gomega v1.20.1%0A > 349dcdf Merge pull request # 112052 from tosi3k/bump-client-golang%0A > 16a7f7a Bump prometheus/client_golang to v1.13.0%0A > 2b9fe2c Merge pull request # 111808 from alvaroaleman/meta-wrapping%0A > bb48261 Apimachinery meta errors: Support errors.Is and error wrapping%0Abumping github.com/prometheus/client_golang 64435fc...254e546:%0A > 254e546 Merge pull request # 1162 from kakkoyun/cut-1.14.0%0A > 07d3a81 Merge pull request # 1161 from prometheus/release-1.13%0A > c8a3d32 Cut v1.14.0%0A > 870469e Test and support 1.19 (# 1160)%0A > 53e51c4 Merge pull request # 1157 from prometheus/cut-1.13.1%0A > b785d0c Fix go_collector_latest_test Fail on go1.19 (# 1136)%0A > 79ca0eb Added tip from Björn + Grammarly.%0A > 4d54769 Fix float64 comparison test failure on archs using FMA (# 1133)%0A > 078f11f Cut 1.13.1 release (+ documenting release process).%0A > 5f202ee Merge pull request # 1150 from prometheus/sparsehistogram%0A > ddd7f0e Fix race condition with Exemplar in Counter (# 1146)%0A > 0859bb8 Merge pull request # 1152 from jessicalins/update-to-custom-reg%0A > fffb76c Merge branch 'main' into sparsehistogram%0A > 1f93f64 Fix CumulativeCount value of +Inf bucket created from exemplar (# 1148)%0A > 10b0550 Fix race condition with Exemplar in Counter (# 1146)%0A > a340ca4 Run make format%0A > e92a8c7 Avoid the term 'sparse' where possible%0A > 8cc2b6c Fix double-counting bug in promhttp.InstrumentRoundTripperCounter (# 1118)%0A > dcea97e Fix CumulativeCount value of +Inf bucket created from exemplar (# 1148)%0A > 6056615 Update random example to use custom registry%0A > d31f13b Add SparseBucketsZeroThresholdZero and groom doc comments%0A > 9801a4e Examples: Replace deprecated WithGoCollections with WithGoCollectorRuntimeMetrics (# 1130)%0A > 0b7f488 Update simple example to use custom registry%0A > 58a8ca4 examples: Adjust doc comment for native histograms%0A > 7c46c15 Clarify documentation around what constructors do (# 1125)%0A > 9b5c5b8 Update basic example to use custom registry%0A > 4e71e6f Update prometheus/client_model dependency%0A > 83d56b1 Extend prometheus.Registry to implement Collector (# 1103)%0A > 111fae1 Merge branch 'main' into sparsehistogram%0A > 4c41dfb Clarify exemplar(Add|Observe) by renaming to (add|observe)WithExemplar (# 1122)%0A > 25bc188 Merge pull request # 1144 from prometheus/beorn7/histogram2%0A > f73e3cc Fix double-counting bug in promhttp.InstrumentRoundTripperCounter (# 1118)%0A > 95cf173 Merge branch 'main' into sparsehistogram%0A > 6942f9e sparse buckets: Fix handling of +Inf/-Inf/NaN observations%0A > c7aa2a5 Merge pull request # 1113 from prometheus/release-1.13%0A > ec86ef1 Merge pull request # 1092 from prometheus/beorn7/histogram%0A > 1e61b8e Update common Prometheus files (# 1111)%0A > 6141a07 Merge branch 'main' into sparsehistogram%0A > 8cbcd40 histograms: Move to new exposition protobuf format%0A > 5a321c7 Merge branch 'foo-commit' into sparsehistogram%0A > e93e384 Merge branch 'beorn7/release' into sparsehistogram%0A > e203144 Merge branch 'release-1.12' of github.com:prometheus/client_golang into release-1.12%0A > 525d042 Merge branch 'main' into sparsehistogram%0A > a516626 Merge branch 'release-1.12' into beorn7/release%0A > a27b6d7 Fix conflicts%0A > 6ba7871 Merge branch 'main' into sparsehistogram%0A > eb59a7b Histogram: Fix bug with negative schemas (# 1054)%0A > b237230 Merge branch 'main' into sparsehistogram%0A > 294cca4 Merge branch 'main' into sparsehistogram%0A > 70253f4 Fix typo in doc comment%0A > 5b19c55 Merge branch 'master' into sparsehistogram%0A > dfbcc28 Merge pull request # 901 from prometheus/beorn7/histogram%0A > 84fcaff Merge branch 'master' into sparsehistogram%0A > 263be8d Refactoring of sparse histograms%0A > 9ef5f90 Allow a zero threshold of zero%0A > 2409960 Implement strategy to limit the sparse bucket count%0A > aa6f67a Add TODO about bucket search optimization%0A > 43f31c2 Merge pull request # 886 from prometheus/beorn7/histogram%0A > 5aa8534 Merge branch 'master' into sparsehistogram%0A > 5142344 Pin client_model to the most recent sparsehistogram commit%0A > 97eb041 Tidy go.sum%0A > 6c4e0ef Add tests for sparse histogram%0A > 553ed73 Fix lint warning%0A > 31318b7 Switch to base-2 buckets%0A > b7a540a Fix test%0A > a9df0ba Update prometheus/client_model%0A > ce36ee3 Merge branch 'master' into beorn7/histogram%0A > d698336 Merge branch 'master' into beorn7/histogram%0A > 08104a0 Minor doc comment fixes%0A > a9d0066 Add note about pow-of-10 precision issue%0A > d1f5366 Fix span offset%0A > abe540f Encode sparse histograms in protobuf%0A > c98db4e Demo sparse histograms%0Abumping knative.dev/client-pkg 4f052f9...f377f06:%0A > f377f06 Update community files (# 106)%0A > b93ceb0 Update community files (# 105)%0A > 83c91f4 Update community files (# 103)%0A > e5c405e Update community files (# 102)%0A > eee9b55 Update community files (# 100)
Signed-off-by: Knative Automation [email protected]
[geometry] Add Meshcat::GetRealtimeRate
Tidy up recent Meshcat changes:
- Add missing pydrake bindings.
- Strongly prefer testing the public API (eschew test-friendship hacks). We want to guard against regressions in the end-user experience; using private API goes against that goal.
- Fix indentation, typos, and eschew abbreviation.
[FEATURE] Feature/prepare for training feedbacktask (#3151)
I added a very rough outline of my ideation behind
prepare_for_training with the new FeedbackDataset. As discussed
there are 3 complexities:
- How to resolve annotator alignment?
- How to resolve optional fields, which have not been filled out? e.g., "Please provide a correction for prompt 1?".
- How handle potential concatenation of fields?
To make it modular I created a step-wise approach.
PydanticModels that map and verify data fields, like so. By doing this we keep the flexibility to allow for other tasks like TextClassification and this ensures we can directly usedatasets.fieldanddataset.questionsfor defining training. We could also use thenamevalues from the fields/questions, but this might be more error prone.get_relevant_data_for_training()inList[dict]format with all relevant fields from the Pydantic model. annotator alignment issue. For now I opted for choosing the first non-zero value.- Forward the
List[dict]to a similar flow we previously had. - Also add
dataset.unify_responses(question, Enum(strategy))-method - Added
*QuestionUnifcationto schemas to hold logic surrounding unifying multiplier responses - Added
client.feedback.training - Added
TrainingDataFor*to hold logic surroundingprepare_for_training-methods per task - Added inheritance for ArgillaTrainer
import argilla as rg
from argilla import (
FeedbackRecord,
LabelQuestion,
LabelQuestionUnification,
MultiLabelQuestion,
TrainingDataForTextClassification,
ArgillaTrainer
)
dataset = rg.FeedbackDataset(
guidelines="Add some guidelines for the annotation team here.",
fields=[
rg.TextField(name="text", title="Human prompt"),
],
questions =[
LabelQuestion(
name="relevant",
title="Is the response relevant for the given prompt?",
labels=["yes","no"],
required=True,
visible_labels=None
),
MultiLabelQuestion(
name="content_class",
title="Does the response include any of the following?",
description="Select all that apply",
labels={"hate": "Hate Speech" , "sexual": "Sexual content", "violent": "Violent content", "pii": "Personal information", "untruthful": "Untruthful info", "not_english": "Not English", "inappropriate": "Inappropriate content"},
required=False,
visible_labels=4
),
]
)
dataset.add_records(
records=[
FeedbackRecord(
fields={"text": "What is your favorite color?"},
responses=[{"values": {"relevant": {"value": "yes"}, "content_class": {"value": ["hate"]}}}]
),
FeedbackRecord(
fields={"text": "What do you think about the new iPhone?"},
responses=[{"values": {"relevant": {"value": "no"}, "content_class": {"value": ["hate"]}}}]
),
FeedbackRecord(
fields={"text": "What is your feeling about the technology?"},
responses=[{"values": {"relevant": {"value": "yes"}, "content_class": {"value": ["sexual"]}}},
{"values": {"relevant": {"value": "no"}, "content_class": {"value": ["hate", "sexual"]}}},
{"values": {"relevant": {"value": "yes"}, "content_class": {"value": ["hate", "sexual"]}}}]
),
FeedbackRecord(
fields={"text": "Jesus Christ!"},
responses=[{"values": {"relevant": {"value": "no"}, "content_class": {"value": ["sexual"]}}},
{"values": {"relevant": {"value": "no"}, "content_class": {"value": ["hate"]}}}]
)
]
)
# print(dataset.question_by_name("relevant").__all_labels__)
label = LabelQuestionUnification(question=dataset.question_by_name("relevant"), strategy="majority")
training_data = TrainingDataForTextClassification(text=dataset.field_by_name("text"), label=label)
for framework in ["spacy", "transformers", "openai", "spark-nlp"]:
formatted_data = dataset.prepare_for_training(framework, training_data, fetch_records=False, train_size=0.8)
print(formatted_data)
trainer = ArgillaTrainer(
dataset=dataset,
training_task_mapping=training_task_mapping,
framework="setfit",
fetch_records=False
)
trainer.train("test")Closes #2954 Closes #3184 Closes #3152
Type of change
- New feature (non-breaking change which adds functionality)
- Improvement (change adding some improvement to an existing functionality)
How Has This Been Tested
- Test A
- Test B
Checklist
- I have merged the original branch into my forked branch
- I added relevant documentation
- follows the style guidelines of this project
- I did a self-review of my code
- I made corresponding changes to the documentation
- My changes generate no new warnings
- I have added tests that prove my fix is effective or that my feature works
- I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Alvaro Bartolome [email protected]
zram: Switch default compression algorithm to zstd
- Yeah. Thanks to god damn Tencent and other applications. They are ating our memory insinely
Signed-off-by: EndCredits [email protected]
Add posts.html.tpl and prepare.php for preparing the posts page which will be used as an alternative page for those who run their browsers with JavaScript disabled.
Albeit the links on that page will point to raw markdown files instead of the traditional Web pages, which may suck for some people but you can always use a third-party tool, or use conversion tools to generate HTML from Markdown and browse locally.
Links in the markdown files may point to ~/ which is a derivative
from the Unix/Linux eco-system that points to the HOME directory of
the logged in user. I use this same approach to reference the HOME
directory of a particular post, those resources should be located at
/cdn/$id/ so you can do a bit of sed magic and replace those
occurences if you want.
The reason I did it that way is to preserve bandwidth, as writing the entire link is not very bandwidth friendly, but also the page domain may change in the future and that has to be reflected dynamically, which is at the moment done through JavaScript.
Anyways, bye.
Replaces the Reaper Scythe with the Vorpal Scythe (also the Morbid trait) (#75948)
adds the Vorpal Scythe, a special chaplain null rod variant, replacing the Reaper Scythe, a not so special null rod variant.
When you choose the vorpal scythe, it comes as a shard that you implant into your arm, similar to a cursed katana.
Once implanted, you can draw it at any time like an arm implant.
However, sheathing it again presents some problems. (Also, implanting
the organ gives you TRAIT_MORBID, which I'll explain in a bit)
The Vorpal Scythe has 10 force, one of the weakest null rod variants for force that isn't a joke null rod. However, it has exceptional armor pen and also has 2 tiles of reach. So quite unique.
It also has a special beheading ability when you right-click someone. This borrows some code from amputation shears, functioning pretty similarly, except with a few additional ways to speed up the action and restrictions. (It takes 15 seconds baseline to behead someone standing and conscious, and speeds up or slows down based on factors such as incapacitation and whether or not our scythe is already empowered)
When you successfully behead someone with a mind, the vorpal scythe gains 20 force and can be safely stowed and drawn for 2 minutes. Performing more death knells like this will reset the timer.
If it has not performed its 'death knell', or you haven't hit a living mob, then it will cause severe damage to you if you ever try and stow it (or its forced back into your arm). Just hitting a mob with the scythe will sate it for 4 minutes. Unless it is a non-player monkey. Horrible things. Just hitting mobs does not reset the timer on empowerment.
What this means is that the chaplain may be more hesitant to simply draw their weapon on people. It also means that potentially, the chaplain will not always have magic immunity, since they may end up stowing the weapon away and be reluctant to draw it on a whim without either taking damage for sheathing it without hitting something, or dealing with having one less hand up until they can.
While empowerment only happens when you behead mobs with a mind, beheading monkeyhumans and other mindless humans subtypes causes their heads to become haunted! It's mostly harmless and largely just SpOoKy. We don't want heads with actual players in them to go floating off to space. (Does not work on monkey heads for sanity reasons)
When you have the Morbid trait, you think creepy stuff is cool and hate saving peoples lives. You get a mood boost from graverobbing, autopsies, dissections, amputations (including beheadings with the scythe and amputations with the shears) and revival surgery. However, you get a mood penalty when you tend wounds on the living, as well as a hefty penalty when you perform CPR or defibrillate someone. I was thinking Victor Frankenstein when I was choosing which actions had an associated moodlet, so anything that I might have missed would be appreciated.
You also count as potentially cool with regards to haunted objects. Ghosts think you're neat. (Revenants probably will still kill you if they had the chance)
Add meat content to game screen
These commit messages are going to be funky when reading them back, like what in the world is "meat content"?
A lot of changes again for what seems like a simple enough thing to do, with the meat content.
Adds some sprites to the game screen. Background and meat are very similar to the title screen.
The interesting part is that we want to display the amount of meat up for grabs by the carnivores in the game screen, so we need to know how much there is.
Thematically, I've introduced a MummyTrex class that handles the amount of
meat via bringHomeTheBacon, because it's funny. Kind of. When you create a
new MummyTrex she initialises the amount of meat available using a random
value between 1000 and 2000. This is then exposed to the game. We'll have to
introduce a way to modify the amount of meat available after a successful bid,
so this might not be immutable in the future, but it'll do for now.
To show this to the people playing the game, we're adding a label to the game screen, semi-centered on the meat itself. This label uses the Dinopia font we used before for the title and instructions, but this time as actual text instead of an image. This means we need to include the font and create it for use within our game. As part of this I found out you can set outlines programmatically. I might go back and use this instead of images in the title screen, but I'm not 100% convinced it looks as good. We'll see.
What else has happened. I added a couple of extra ktx libraries for FreeType and Skins, which make it easier to define a skin with a font for the label.
I think that's about it actually. Next I need a way to read the players from the directory, so we can display them at the bottom of the game screen. This part should be fun.
tegra: lcd: video: integrate display driver for t30
On popular request make the display driver from T20 work on T30 as well. Turned out to be quite straight forward. However a few notes about some things encountered during porting: Of course the T30 device tree was completely missing host1x as well as PWM support but it turns out this can simply be copied from T20. The only trouble compiling the Tegra video driver for T30 had to do with some hard-coded PWM pin muxing for T20 which is quite ugly anyway. On T30 this gets handled by a board specific complete pin muxing table. The older Chromium U-Boot 2011.06 which to my knowledge was the only prior attempt at enabling a display driver for T30 for whatever reason got some clocking stuff mixed up. Turns out at least for a single display controller T20 and T30 can be clocked quite similar. Enjoy.
Tested-by: Andreas Westman Dorcsak [email protected] # ASUS TF T30 Tested-by: Jonas Schwöbel [email protected] # Surface RT T30 Tested-by: Svyatoslav Ryhel [email protected] # LG P895 T30 Signed-off-by: Marcel Ziswiler [email protected] Signed-off-by: Svyatoslav Ryhel [email protected]
Cassandra support for chat history using CassIO library (#6771)
This PR aims at building on #4378, expanding the capabilities and
building on top of the cassIO library to interface with the database
(as opposed to using the core drivers directly).
Usage of cassIO (a library abstracting Cassandra access for
ML/GenAI-specific purposes) is already established since #6426 was
merged, so no new dependencies are introduced.
In the same spirit, we try to uniform the interface for using Cassandra
instances throughout LangChain: all our appreciation of the work by
@jj701 notwithstanding, who paved the way for this incremental work
(thank you!), we identified a few reasons for changing the way a
CassandraChatMessageHistory is instantiated. Advocating a syntax
change is something we don't take lighthearted way, so we add some
explanations about this below.
Additionally, this PR expands on integration testing, enables use of Cassandra's native Time-to-Live (TTL) features and improves the phrasing around the notebook example and the short "integrations" documentation paragraph.
We would kindly request @hwchase to review (since this is an elaboration and proposed improvement of #4378 who had the same reviewer).
There are
many
options when creating the Cluster object, and new ones might be added
at any time. Choosing some of them and exposing them as __init__
parameters CassandraChatMessageHistory will prove to be insufficient
for at least some users.
On the other hand, working through kwargs or adding a long, long list
of arguments to __init__ is not a desirable option either. For this
reason, (as done in #6426), we propose that whoever instantiates the
Chat Message History class provide a Cassandra Session object, ready
to use. This also enables easier injection of mocks and usage of
Cassandra-compatible connections (such as those to the cloud database
DataStax Astra DB, obtained with a different set of init parameters than
contact_points and port).
We feel that a breaking change might still be acceptable since LangChain
is at 0.*. However, while maintaining that the approach we propose
will be more flexible in the future, room could be made for a
"compatibility layer" that respects the current init method. Honestly,
we would to that only if there are strong reasons for it, as that would
entail an additional maintenance burden.
We propose to remove the keyspace creation from the class code for two
reasons: first, production Cassandra instances often employ RBAC so that
the database user reading/writing from tables does not necessarily (and
generally shouldn't) have permission to create keyspaces, and second
that programmatic keyspace creation is not a best practice (it should be
done more or less manually, with extra care about schema mismatched
among nodes, etc). Removing this (usually unnecessary) operation from
the __init__ path would also improve initialization performance
(shorter time).
We suggest, likewise, to remove the __del__ method (which would close
the database connection), for the following reason: it is the
recommended best practice to create a single Cassandra Session object
throughout an application (it is a resource-heavy object capable to
handle concurrency internally), so in case Cassandra is used in other
ways by the app there is the risk of truncating the connection for all
usages when the history instance is destroyed. Moreover, the Session
object, in typical applications, is best left to garbage-collect itself
automatically.
As mentioned above, we defer the actual database I/O to the cassIO
library, which is designed to encode practices optimized for LLM
applications (among other) without the need to expose LangChain
developers to the internals of CQL (Cassandra Query Language). CassIO is
already employed by the LangChain's Vector Store support for Cassandra.
We added a few more connection options in the companion notebook example (most notably, Astra DB) to encourage usage by anyone who cannot run their own Cassandra cluster.
We surface the ttl_seconds option for automatic handling of an
expiration time to chat history messages, a likely useful feature given
that very old messages generally may lose their importance.
We elaborated a bit more on the integration testing (Time-to-live, separation of "session ids", ...).
We reinstated cassio as a dependency both in the "optional" group and
in the "integration testing" group of pyproject.toml. This might not
be the right thing do to, in which case the author of this PR offer his
apologies (lack of confidence with Poetry - happy to be pointed in the
right direction, though!).
During linter tests, we were hit by some errors which appear unrelated to the code in the PR. We left them here and report on them here for awareness:
langchain/vectorstores/mongodb_atlas.py:137: error: Argument 1 to "insert_many" of "Collection" has incompatible type "List[Dict[str, Sequence[object]]]"; expected "Iterable[Union[MongoDBDocumentType, RawBSONDocument]]" [arg-type]
langchain/vectorstores/mongodb_atlas.py:186: error: Argument 1 to "aggregate" of "Collection" has incompatible type "List[object]"; expected "Sequence[Mapping[str, Any]]" [arg-type]
langchain/vectorstores/qdrant.py:16: error: Name "grpc" is not defined [name-defined]
langchain/vectorstores/qdrant.py:19: error: Name "grpc" is not defined [name-defined]
langchain/vectorstores/qdrant.py:20: error: Name "grpc" is not defined [name-defined]
langchain/vectorstores/qdrant.py:22: error: Name "grpc" is not defined [name-defined]
langchain/vectorstores/qdrant.py:23: error: Name "grpc" is not defined [name-defined]
In the same spirit, we observe that to even get import langchain run,
it seems that a pip install bs4 is missing from the minimal package
installation path.
Thank you!
Create teachablemachineforyourwebsite.md
Thanks for making a PR! Please fill in the below:
Name: Kyle Liao
Do you run a club? Yes
What relevant experiences do you have to help you write this Jam? Have done club workshops, written and presented workshops for events, and am working on more workshops for a hackathon.
Will you be available on Slack to provide support to Hack Clubbers who run into issues while going through your Jam? Yes, always glad to help provided I am capable.
Note: I know this is very broad, as in it doesn't hint to build a specific project like Ganning's musical instrument, however I will provide examples in the actual one, but I think people can come up with their own ideas inspired.
Simplify GridTrackSize.minmax
It is now a bit more awkward to use directly, but it is more consistent with the rest of the GridTrackSize APIs.
For example, this:
GridTrackSize.minmax(0.px, 1.fr)
became this:
GridTrackSize.minmax(GridTrackSize(0.px), GridTrackSize(1.fr))
That's awful, yes, but more consistent with how everything else
works (gridTemplateRows(GridTrackSize(0.px)...) and repeat)
If you use the grid builder, however, you can enjoy the nicer syntax there:
grid {
cols { minmax(0.px, 1.fr) }
}
which is also consistent with the rest of the GridBuilder API. In other words, the GridTrackSize class has been made more simple but also more verbose, while GridBuilder is the layer where complexity goes into to enable a more enjoyable API experience.
Ghouls bleed again
Crowley: "Ha, ha! I like a human that knows his place. Too many of you think we're all just zombies. They don’t know, or don’t care, that we’re just as human as they are inside. We bleed! We hurt! We regret! And you know what really pisses me off? They think the only way to kill us is to shoot us in the head, like in the old zombie stories, and that will put us out of our misery. Hey, I know! Maybe you could help me even the score."
Obscure C++ bug stuff, really bugs me out
ha ha pun funny laugh laugh at my suffering of 2AM debugging this
Adds tool E.G.O (#1019)
Tool ego
adds tool E.G.O
removes a extra line
fixes shit
swindle
voce
divinity
fixes shit
shifts divinity down a few pixels
This is the fourth time this same commit was made
I hate TG so fucking much like it's unbelievable why does this only fuck up on my PC? WHY?
hyde weapon
stuff
hyde code
hyde fix
new sprites
inhands
destiny effect
heart sfx
stuff
Co-authored-by: Mr.Heavenly [email protected]