Push replication in peer to peer

Connection type: Peer to Peer
Sometimes when I change a document on a device it says push replication is Active and it doesn't come back to Idle.
But the strange thing is that pull replication is working fine.
and after some random time it starts working
and i am getting below error:
12-15 13:02:56.435 16685-17331/com.android.***** W/RemoteRequest: com.couchbase.lite.replicator.RemoteRequest {GET, http://<IP_ADDRESS>:55000/localdb/_local/a1b9fc127fcf41699825f278d45a08120a8bd44a}: executeRequest() Exception: java.net.SocketTimeoutException.  url: http://<IP_ADDRESS>:55000/localdb/_local/a1b9fc127fcf41699825f278d45a08120a8bd44a
  java.net.SocketTimeoutException
      at java.net.PlainSocketImpl.read(PlainSocketImpl.java:484)
      at java.net.PlainSocketImpl.access$000(PlainSocketImpl.java:37)
      at java.net.PlainSocketImpl$PlainSocketInputStream.read(PlainSocketImpl.java:237)
      at okio.Okio$2.read(Okio.java:139)
      at okio.AsyncTimeout$2.read(AsyncTimeout.java:237)
      at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345)
      at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217)
      at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:211)
      at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
      at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:75)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
      at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
      at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
      at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
      at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
      at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
      at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:185)
      at okhttp3.RealCall.execute(RealCall.java:69)
      at com.couchbase.lite.replicator.RemoteRequest.executeRequest(RemoteRequest.java:261)
      at com.couchbase.lite.replicator.RemoteRequest.execute(RemoteRequest.java:165)
      at com.couchbase.lite.replicator.RemoteRequest.run(RemoteRequest.java:105)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
      at java.util.concurrent.FutureTask.run(FutureTask.java:237)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
      at java.lang.Thread.run(Thread.java:818)
12-15 13:02:56.435 16685-17331/com.android.***** W/Sync: PusherInternal{http://<IP_ADDRESS>:55000/localdb, push, a1b9f}: Progress: set error = java.net.SocketTimeoutException

@shwetankb11,
Do you test Peer to Peer with good network condition? or not?
It seems a connection between two devices is disconnected. But push replicator (Socket) cannot detect it till SocketTimeoutException is thrown.

Yes both the replication were working at that moment.

I think if pull replication is working fine then the connection is good.
Please correct me if i am wrong.

Can you observe any error on another device?

No there is no error on the other device.

there is no error on the other device.

There are two possibilities:

From the stack trace, I believe the socket connection for push replication is disconnected, but push replicator could not detect disconnection till Exception is thrown.
On the other device, Listener (Router) is running to handle the request from the replicator. It could hang or causes the problem without printing error. Then it does not send the response.

NOTE: We need the reproducible environment to diagnose this problem.


SwaggerUi3Settings - EnableTryItOut property vs DeActivateTryItOut() method

Hi guys.
It looks like DeActivateTryItOut() method doesn't do anything at the moment.
With this code, button "Try it out" is removed
app.UseSwaggerGen(uiConfig: c =>
{
    c.EnableTryItOut = false;
}

With this code, the button "Try it out" stays on the swagger page
app.UseSwaggerGen(uiConfig: c =>
{
    c.DeActivateTryItOut();
}

Documentation (https://fast-endpoints.com/docs/swagger-support#enable-swagger) doesn't say anything about which approach should be used, but if the method exists, it should work, no? Is there a difference in using the property or the method?
I'm using package fastendpoints.swagger - 5.15.0
Thanks for your help

I believe the intellisense/XML documentation clears up the confusion:
https://github.com/FastEndpoints/FastEndpoints/blob/d898f59f628455346f6c9e5997730460cff033cf/Src/Swagger/Extensions.cs#L130-L135
So, the DeActivateTryItOut() extension method added by FE is for de-activating the try it out feature by default, because by default the feature is activated (expanded) in the Swagger UI.
On the other-hand, the EnableTryItOut property (which is provided by NSwag) dictates whether the button should be shown in the UI in the first place or not.
Hope that explains it...

Thanks @KateyBee for your answer. Just in case it is not clear to everyone what are the different outcomes, I will try to summarize:

Property EnableTryItOut = true will make the big blue button "Execute" automatically available to click. If set to false that button is gone.
Method DeActivateTryItOut() will require the user to click on "Try it out" to see the "Execute" button if EnableTryItOut = true.

Case 1 - no Execute button
app.UseSwaggerGen(uiConfig: c =>
{
    c.EnableTryItOut = false;
});

Case 2 - Execute button is shown automatically
app.UseSwaggerGen(uiConfig: c =>
{
    c.EnableTryItOut = true;
});

Case 3 - Execute button is only shown if user clicks on Try it out button
app.UseSwaggerGen(uiConfig: c =>
{
    c.EnableTryItOut = true;
    c.DeActivateTryItOut();
});

@heldersousa-planetpayment Great! That sure is going to be helpful. Thank you!


Restarts in g0 apps

We need restarts to do production science and debug longer sims.

Yes this is important. Perlmutter for example only allows 24 hour jobs, so restarts are necessary.

This functionality was added with PR https://github.com/ammarhakim/gkylzero/pull/319 into the gk-g0-app branch (https://github.com/ammarhakim/gkylzero/tree/gk-g0-app). The rest of the code will gain restart functionality when this branch is merged.


Selection to clipboard

@timkpaine can you provide some more reference for this issue.
I am interested to contribute to this project.


Shapefiles for Ladakh and J&K boundries

Hey team,
I am working on a spatial analysis of ID in India, and have been suggested to apply the new J&K and Ladakh boundaries instead of keeping them together. Can you suggest how to do so using the shapefiles already present? I considered combining the geometries at a district level, but it does not have the level of detail (geometry for gilgit and other districts) that the GoI used to define the new UTs. Is there an external dataset I can use to fix this?
Thanks!
Dev

Anybody working on this?

I also needed this for a Covid-19 Tracker website, but since it wasn't available, I used an SVG I made from  Map of UTs , found in this Press Release

We could use: http://<IP_ADDRESS>/WriteReadData/userfiles/India - Political1.pdf for the New UT Boundaries

Do we have the revised shape files ready? Is anyone working on it?


Update README with info on react-redux route params

Add an example of getting route params from react-router in mapStateToProps.

Thanks!


Feature - add delete function for Milvus DB

Delete data from Milvus DB using a filter.
Milvus allows us to delete data based on the primary key only.

Looks good! One comment, and also it sounds like Milvus just allows a filter for deletes?

Looks good! One comment, and also it sounds like Milvus just allows a filter for deletes?

Yeah, exactly. (collection_name and expr fields)
https://milvus.io/docs/delete_data.md

Looks good! One comment, and also it sounds like Milvus just allows a filter for deletes?

Yeah, exactly. (collection_name and expr fields)
https://milvus.io/docs/delete_data.md

But you say in the comments above that:
Milvus allows us to delete data based on the primary key only.

Looks good! One comment, and also it sounds like Milvus just allows a filter for deletes?

Yeah, exactly. (collection_name and expr fields)

https://milvus.io/docs/delete_data.md

But you say in the comments above that:
Milvus allows us to delete data based on the primary key only.

Correct, I mean that primary key must to be in expr field.
We can't delete by other fields.
I didn't mention the collection name in the previous comment sorry.

Thank you!


Add ability to specify fields from _source to reindex

This commit adds the ability to specify the fields from source to reindex
when using the Reindex API (ReindexOnServer in NEST).
Closes #3288

ported to 6.x and 5.x


[cli] Fix tamagui button

Description

The components/Button when using tamagui had wrong types.
This pr:

Changes the underlying component used for the tamagui button from YStack + SizebleText to Button
Generates the styled button in tamagui.config.js when navigation is enabled, not only when using a Stack, because we generate the button component always, even if the Tabs and Drawer template are not using it.
Fixes custom button types forwardRef<TamaguiElement, ButtonProps>
Custom button component now extends the types of the Tamagui Button

type ButtonProps = {
  title: string;
} & ComponentProps<typeof TButton>;

Sends the rest of tamagui button props down to the component <TButton {...tButtonProps} ref={ref}>

This allows us to use the Custom Button with all available tamagui props.

Related Issue
https://github.com/danstepanov/create-expo-stack/issues/275

Motivation and Context

How Has This Been Tested?

Create a new project with Expo Router Stack + Tamagui
passed the npx tsc --noEmit
Monkey tested the button and it works

Screenshots (if appropriate):

I think the components/Button.tsx is unnecessary when using Tamagui. It adds an unnecessary layer of abstraction on top of the Tamagui Button. Usually, we have custom buttons to address different variants (primary, secondary), but with tamagui, this can be achieved through theme variants.
The disadvantage of having a custom wrapper on top of the tamagui button is that it adds a bit of complexity, and also changes slightly the API around the title of the button. Not a big deal, but still.
I know that not adding it to the components, will complicate a bit the generation of the other screens, because it will be a different import and a slightly different way to render it, compared to other buttons.
WDYT?

I think the components/Button.tsx is unnecessary when using Tamagui. It adds an unnecessary layer of abstraction on top of the Tamagui Button. Usually, we have custom buttons to address different variants (primary, secondary), but with tamagui, this can be achieved through theme variants.
The disadvantage of having a custom wrapper on top of the tamagui button is that it adds a bit of complexity, and also changes slightly the API around the title of the button. Not a big deal, but still.
I know that not adding it to the components, will complicate a bit the generation of the other screens, because it will be a different import and a slightly different way to render it, compared to other buttons.
WDYT?

@Savinvadim1312 In the near future, we'll be revisiting the UI of all of the variants including theming, component layout, styling, as well as things like light/dark mode. I think we should revisit this question at that time. This will be explored just after we get the test suite out, over the next month. Very valid point though.


Adds --only-deps flag to the 'build' command.

As discussed in #287, adds a new flag (--only-deps) to the 'build' command, so only the dependencies of a rock are installed, and not the rock itself.
Feedback is welcome. Specially, I don't know if I should add this also here. I think it is best not to add it there, since 'install' removes the installed rock and we don't want that.

Sorry for all the commits. I intend to squash them before merging.

Appveyor build failed due to a transient network error.

If we're adding --only-deps, I think it needs to be added to luarocks install as well. In luarocks.install this would be better as a separate function, since reusing install.install_binary_rock would require greater changes.

Thanks. Will look into that. Also, any tips on the test? I have the problem that if the first command (luarocks build --only-deps) fails, the test passes by mistake. Is it ok to add something like set -e in a function?

I think chaining them with && does the trick.
test_build_only_deps_rockspec() { $luarocks download --rockspec lxsh ${verrev_lxsh} && $luarocks build ./lxsh-${verrev_lxsh}.rockspec --only-deps && { $luarocks show lxsh; [ $? -ne 0 ]; }; }

I've been writing all tests as single-lines because I used to grep the script, pipe and run it, but I think it's not necessary anymore.
Ah, please add them to testing.lua as well. I know it's unfinished and we still can't run it (so you'll have to guess the API a little), but I don't want to keep the list of tests out of sync until we finish the port and retire the bash version.

How about now?

Apart from the minor notes above, looks good to merge!

Thanks a lot!


Replace final mentions of Area

Replaced with possible rewards from the Community Service Hour community.

Perfect, thank you


What is the CMake syntax?

instructions, too, I suppose

I had to conda install pybind11 for this to work.  Then I followed the pybind11 rtd https://pybind11.readthedocs.io/en/stable/installing.html.
I created build/, cd'd into build/, then ran cmake ..
This was throwing until I modified the last like of CMakeLists.txt which was causing the problem.
I replaced ${SKBUILD_PROJECT_NAME} with build and the build worked.

I'm trying to get just a basic function added to _core.py.
I added this to main.cpp and then in the root directory ran
cd build
cmake ..
make

In the build directory i opened python and ran
import _core

_core.hello(1)

And it worked.
However, when I run pytest tests/ in the root directory, the tests no longer pass.
So my C++ is being compiled to a python module, and this is present in build/ but it does not become a submodule underneath tac_hep_coding_jam.

Ok after tracing it down, we don't need to use cmake at all - it's wrapped up in the pyproject.toml file, so we just call pip install . in the root directory after adding any methods to main.cpp.


Production website

The list indicated that we can't & we can migrate to a production web site
-Developer websites can't be converted to production websites. More information: Power Pages lifecycle
-Each user is allowed to create three developer websites. Once you've created your developer site, you can migrate it to a test or production site

Détails du document
⚠ Ne pas modifier cette section. Elle est requise pour learn.microsoft.com ➟ Liaison des problèmes GitHub.

ID: 6da19427-9c92-47b6-a1db-4254a67ce597
Version Independent ID: 6da19427-9c92-47b6-a1db-4254a67ce597
Content: Use developer websites
Content Source: power-pages-docs/getting-started/developer-sites.md
Service: power-pages
Sub-service: ****
GitHub Login: @ProfessorKendrick
Microsoft Alias: vamseedilli

Thank you for the feedback. The process of converting a website is different than migrating a website. We are updating our documentation to explain the differences. You cannot convert a developer website to a production website but you can migrate a developer website to a production site.


Clamp: Add Calculate Linear Clamp Extension

Description

This extension can generate a responsive linear clamp function based on px or rem values.
It's created based on the CSS Tricks article.
Screencast

Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

Hi @pernielsentikaer 👋🏼
It's my pleasure!
I recently added validation to all fields. I hope now this extension will be safer in use.
You can review this extension now 🔥

I think that it's a good idea, but for now, I don't see any use cases to extend. Maybe we could add another field for example select, to select bezier curves (not only linear).

Then just keep it as it for now :)

We could change the name/title of the extension to something like CSS Calculations and the folder to css-calculations instead?

Yes, of course, done 🚀


Inventory spot instances?

Would it be possible for terraform-inventory to include spot instances in the inventory? Specifically, when a spot request is fulfilled, is there any way to discover the IP of the resulting instance?

Nevermind. I failed to refresh my state before checking the inventory. I'm very happy and impressed with this tool.

Glad to be of service. Please do open another issue if you notice anything regarding spot instances which isn't working. I don't use them myself, so they're not very well tested.


[fix][test] Enable testMaxPendingChunkMessages

Motivation
The test testMaxPendingChunkMessages is disabled, this PR enables it.
Modifications

Fix some issues in the testMaxPendingChunkMessages
Enable testMaxPendingChunkMessages

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/RobertIndie/pulsar/pull/10

Codecov Report

Merging #18542 (79a9806) into master (aeb4503) will increase coverage by 16.57%.
The diff coverage is 51.61%.

@@              Coverage Diff              @@
##             master   #18542       +/-   ##
=============================================
+ Coverage     31.39%   47.96%   +16.57%
- Complexity     6651     9383     +2732
=============================================
  Files           697      617       -80
  Lines         68015    58521     -9494
  Branches       7285     6098     -1187
=============================================
+ Hits          21353    28072     +6719
+ Misses        43667    27421    -16246
- Partials       2995     3028       +33

Flag
Coverage Δ

unittests
47.96% <51.61%> (+16.57%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ersistentStreamingDispatcherMultipleConsumers.java
0.00% <0.00%> (ø)

...he/pulsar/client/impl/MultiTopicsConsumerImpl.java
22.26% <0.00%> (ø)

...ersistentStickyKeyDispatcherMultipleConsumers.java
58.91% <50.00%> (+20.44%)
:arrow_up:

...sistent/PersistentDispatcherMultipleConsumers.java
59.34% <75.00%> (+20.11%)
:arrow_up:

...pulsar/broker/admin/impl/PersistentTopicsBase.java
59.43% <100.00%> (+43.67%)
:arrow_up:

...lsar/client/impl/conf/ClientConfigurationData.java
96.66% <100.00%> (+0.11%)
:arrow_up:

...apache/pulsar/proxy/server/LookupProxyHandler.java
56.46% <0.00%> (-1.73%)
:arrow_down:

...va/org/apache/pulsar/client/impl/ConsumerImpl.java
14.84% <0.00%> (ø)

.../apache/pulsar/broker/namespace/LookupOptions.java
87.50% <0.00%> (ø)

...che/bookkeeper/mledger/impl/ManagedLedgerImpl.java

... and 245 more


Don't log flushing

We could add metrics, but we don't have evidence that we need them yet, and also this fork is soon to be replaced.
Helps with weaveworks/prism#36

:+1:


O-ring

Hello, I am doing a project where I apply the economic O-ring theory to sports teams in order to evaluate their performance. Would the O-ring theory contained in this code work for this application, and is it similar to the O-ring theory of economic development?

Thanks for being in touch - from my understanding, the O-ring theory in economics is quite different, so the algorithms in this package wouldn't help with that analysis.

Thanks!


dragCoefficient misspelt 6 times over 2 scripts

dragCoeffiecient??? One "e" too many. Should be "dragCoefficient"
Offending entries:
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/rocketfx.cs#L31
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/rocketfx.cs#L31
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/grenadefx.cs#L301
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/grenadefx.cs#L465
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/grenadefx.cs#L633
https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/game/art/datablocks/weapons/grenadefx.cs#L848
Happens 6 times but only 1 has a setting that is not zero. Not handy if you're gonna copy and paste example scripts though. ;)

I made fixes to all of these.


Purge config dir.

Easier management than keeping a lot of ensure absent in your configuration.

I don't see why this change should make it fail this way.
Also, the implementation work fine for me.

+1

Hi,
Thanks for your interest and your work. And please, excuse me for the delay.
I published a new release today.
Regards,


[e2e] Fail: Services [It] should be able to create a functioning NodePort service

Test can be found here:
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/service.go#L1165-L1191
Description:
Create a TCP NodePort service, and test reachability from a client Pod.
The client Pod MUST be able to access the NodePort service by service name and cluster
IP on the service port, and on nodes' internal and external IPs on the NodePort.

/assign

e2e tests failing in ipv4 and ipvs backend.
https://github.com/kubernetes-sigs/kpng/runs/4779261817?check_suite_focus=true


ESM for browser

Feature Request
The esm files cannot be used in the browser.
as follows:
<EMAIL_ADDRESS>// TypeError: Failed to resolve module specifier "tslib". Relative references must start with either "/", "./", or "../".

<EMAIL_ADDRESS>// TypeError: Failed to resolve module specifier "tslib". Relative references must start with either "/", "./", or "../".

https://github.com/ReactiveX/rxjs/issues/4416


issue with multiple range calendar

this is the start date that i set is  date: moment(date),
may you please help me with how to set an end date ?

Did you manage to resolve this issue?

Did you manage to resolve this issue?


[Carmageddon TDR 2000] - Direct3D mode fails to start

VMware Workstation 17 Pro (17.6.1 build-24319023)
SoftGPU v0.6.2024.40-alpha3
Carmageddon TDR 2000 fails to run in Direct3D mode.
When you first boot the game, it will perform a graphic/audio card check. After several flickering black screens, the test will be over without telling if it passed or failed.
Attempting to run the game, it will crash with this error:

By going into settings and then Display, you will see that you can choose the API, but no video cards are detected:

By comparison, here's how it should look like:
https://www.pcgamingwiki.com/wiki/Carmageddon_TDR_2000#/media/File:Carmageddon_TDR_2000_-_Display.png
Trying to start the game will bring up this error:

The game can be still played in Software, but the quality is abysmal:

Which ddraw mode are you using?

I'm not sure. How do I check this? From Windows or from the game? Because the game does not let me set anything up when selecting Direct3D Renderer.

So, I don't have a PC to check, you should navigate to 'regedit' and find a key related to ddraw and change from 'system' to 'wine' or vice versa

Okay, I got my head around and changed modes both on global and by manually adding a string with the exe. Unfortunately, no dice: if I set global to "system", I cannot use any HW renderer and the setup only let me choose SW. If global is on "wine", it doesn't matter if I set TDR2000.exe either "system" or "wine", I would still get that issue.

Could you try sofgpu v0.4.2023.19? Maybe it could be a regression

I've found the solution here: https://bugs.winehq.org/show_bug.cgi?id=6946
Basically, I just edited TDR2000.gfx and changed the 4th line to "0". This fixed the issue:

And the game now works properly in D3D mode. I don't know if this tweak can be manually added in SoftGPU for the next update:


memory not properly allocated in UX handler

dev branch crashes after two updates.

Issue closed as it was only ever in the dev branch.


Is the only way to communicate through console.debug? [Security]? (scoped exposed functions)

So, this is kind of a two part question/bug-report(?). It all started when I was trying to find a way to expose an external function (ala exposeFunction), but just to the scope of a page.evaluate(). Through looking into this, I discovered some interesting ways for arbitrary pages to break puppeteer, if their goal was to for example prevent headless Chrome from visiting them potentially, or worse, to attempt to break out of headless Chrome and possibly do nefarious things on the puppeteer process.
So, as  mentioned, this all started with me wanting to do something like this:
page.evaluate(puppeteerFunction => puppeteerFunction("called from client"), msg => console.log("properly scoped: " + msg));

In other words, I'd like to expose a function solely to my own custom evaluations within the page, rather than making them globally available for all scripts. I started poking around at the implementation of page.exposeFunction, and it seems that fundamentally the only way to get information "out" of the client and into puppeteer is through logging, as exposeFunction seems to log messages to be decoded through console listeners on the server end.
Even if there was a way to hide an exposed function from the global scope, such as this:
await page.exposeFunction("exposedFunction", ...);
// In my tests this doesn't actually work:
await page.evaluate(function ()
{
     var scoped = window.exposedFunction;
     delete window.exposedFunction;
     // Now only we can use exposedFunction. Again, in my experiments this doesn't work,
     // not to mention the fact that there exists a window where window.exposedFunction is
     // usable to anyone.
})

Anyways, if this strategy did work, then an adverserial script on the page could still mess around with console.debug to spark evaluations on the server:
console.debug("driver:page-binding", JSON.stringify({"name":"f","seq":1,"args":[]}))

In fact, a page could simply override console.debug to listen to whether they are in a puppeteer environment:
var original = console.debug;
var knownFunc = "";
console.debug = function (...args)
{
   if (args[0] !== "driver:page-binding")
      return original(...args);

   knownFunc = JSON.parse(args[1])["name"];
   // now I can start sending it stuff.
}

Interestingly enough, if your only goal is to create havoc (vs. say, try to "break out" of the page), then you can just do console.debug("driver:page-binding", "invalid_json") to make puppeteer angry, regardless of whether any functions have been exposed. The resulting exception seems to be caught at some point though, and thus the flow of the puppeteer program will not be halted (not sure if this is a good thing or a bad thing).
Anyways, all this to say, it would be nice if there was a JSHandle-like system to go from server to client. Or, perhaps simpler, a message passing system that could be scoped to just the single evaluate (which would be cleared after the evaluate returns or when the evaluates Promise resolves/rejects to properly define lifecycle, so that more complex function systems could be built on top, much like the console.debug system currently in use is):
page.evaluate(postMessage => postMessage("hello"), function receiveMessage(msg) { })

My only thoughts so far to make a tamper-proof / scoped system is to employ private/public key pairs and use the same console.debug strategy:
evaluateWithPostMessage = async function (f, receiveMessage, ...args)
{
    const keys = generate_key_pair();
    page._client.on('Runtime.consoleAPICalled', function (msg)
    {
          if (event.type !== "debug") return;
          if (event.args[0] !== "private-message") return;

          const message = decrypt(event.args[1], keys.public);

          // Message not intended for us, or something weird going on.
          if (message.substr(0, "private-message:".length) !== "private-message:")
               return;

          // Actually call function...
          const result = receiveMessage(msg.substr("private-message:".length));

          // Do the work of passing a result back.
    });
    await page.evaluate(function (code, key, ...args)
    {
         var postMessage = msg => console.debug("private-message", encrypt("private-message:" + msg, key));
         var compiled = new Function("postMessage", `return ${code}([].slice.apply(arguments, 1))`);

         return compiled(postMessage, ...args);
    }, f + "", keys.private, ...args);
}

Anyways, I'm happy to do all this if it's the only way, but I feel like there must be a better or more official way of passing an external function into a script to evaluate and to limit its scope just to that. Separately, ideally such a system could be expanded to the normal exposeFunction to avoid the potential for arbitrary pages to crash puppeteer.

Hey @tolmasky,
Sorry it took me so long to get to your bug report, this was an interesting read.
Indeed, we used to do console.debug for message-passing; this is no longer the case since we landed https://github.com/GoogleChrome/puppeteer/pull/2631. With this patch we now use protocol's Runtime.addBinding, so the attack you described here will be a little bit harder to perform. Still, it's very much doable.

Or, perhaps simpler, a message passing system that could be scoped to just the single evaluate

You can now do this using protocol's Runtime.addBinding and subsequent page.evaluate that grabs the binding; you mentioned it didn't work for you, but I'm quite sure I had a code somewhere that was re-using this exact approach.
For your purposes I'd pass in executionContextId as one of parameters for Runtime.addBinding. This way you'll scope the binding to the particular frame and iirc the binding won't be re-installed after navigation.
Our of curiosity, what's the usecase that makes you organize this kind of communication?

Hi @aslushnikov,
Thanks for the response. Our use case is that we currently use Puppeteer for our integration tests (and we will probably be releasing our framework for doing so as open source at some point). We basically had two concerns that arose:

Security
This applies specifically to uses of addBinding. Our product (that is, the product we are TESTING with said framework) currently uses a number of third party resources (such as typekit for example), as I am sure is quite common. Thus, the code we're running isn't just code we're completely in control of. My concern level is heightened with regard to running tests automatically in a CI environment if we are ever pulling what essentially amounts to untrusted code in a non-sandboxed environment. Prior to installing any custom functions into Puppeteer, we can basically trust the browser's separation to provide said sandbox. However, every addBinding we choose to employ creates a potential escape hatch for hijacked third party resources to, on the low end denial of service our CI/deploy, and on the high end potentially break out (ala the Electron vulnerabilities we have seen).

General encapsulation to not break stuff
This part is more straight forward and doesn't have anything to do with addBinding, just adding any code at all. Some tests run in the browser's context. For example, our product is an API, so we want test that the callbacks are called correctly (pseudo-code provided below):

// page.static is a method we created to load static html.
await page.static("<script src = "our-great-api.com"></script>")
await page.evaluate(() =>
{
     const callback = expect.mock.fn();
     ourAPI.doStuff(callback);
     expect(callback).toHaveBeenCalled();
});

So here the idea is that expect is defined globally (probably through evaluateOnNewDocument). We just don't want to have it available globally or polluting the global namespace so that 1) it can't be mutated by accident by someone, and also 2) doesn't potentially accidentally confuse third party scripts we include on the page (this is why simply scoping it to a single frame isn't sufficient). Again, the thing to remember is that our product (and many products) do include third party scripts and while we can correctly scope all our APIs, these "extra" testing functions can't.
Here are a few ideas we've played around with:

We could auto-wrap the evaluated code and include these special functions every time. Something like this:

page.testEvaluate = function (f)
{
    this.evaluate(`(expect => ${f + ""}())(${expect_definition})`);
}

This seems unfortunate to rerun the entirety of the source code of every library we want to provide on each test.

Piggy-back off of import/request interception. Similar to before, only we have a "secret" URL that holds these libraries, like "https://us/0298748930985940", which we intercept and return the source code for. So something like:

page.testEvaluate = function (f)
{
    this.evaluate(`import expect from "https://us/0298748930985940" ${f + ""}()`)
}

This has the benefit that we can theoretically also expose this to script tags for situations where we'd like to have a more declarative way of doing things first vs. having to always rely on evaluateOnNewDocument:
await page.static(`
<script>
      import expect from "https://our-libraries/expect"
      didLoadCallback = expect.fn.mock();
</script>
<script src = "our-great-api.com" data-load-callback="didLoadCallback"></script>")
`);

await page.testEvaluate(() => expect(didLoadCallback).toHaveBeenCalled());

The problem here is of course now "https://our-libraries/expect" is once again available to third party scripts (and they get the object identical copy, so mutations are possible).
Hopefully this sheds a little light into what we are doing. Basically, we'd like a way to have an "testing context" with functions not available and changing the code being tested. We can accomplish something close with the import trick (we'd probably use the secret URL method since otherwise we're right back where we started with it being globally available).
I think that's as far as we can get by operating on top of the Puppeteer API, however, from inside Puppeteer it would be nice to have a more official way of creating an expanded context for "orchestrator" separate from the page that is being manipulated (similar to the way that the Console is expected to be used by the user, not the page itself). From an API perspective, what was originally requested with .evaluate(functionHandles => code, functions) that scopes those variables to just that one evaluation would be nice. Beyond that, you could imagine something like

@tolmasky security-wise, addBinding will never be secure enough to rely on it. Chromium itself operates under assumption that the renderer process is compromised, so any call to addBinding might be malicious.
Regarding the encapsulation bit, you can already "fake" encapsulation like this:
const pptr = require('puppeteer');

(async () => {
  const browser = await pptr.launch();
  const page = await browser.newPage();
  const bindingName = Math.random().toString(36);
  await page.exposeFunction(bindingName, value => {
    console.log('Binding called! value: ' + value);
  });
  const bindingHandle = await page.evaluateHandle(bindingName => window[bindingName], bindingName);
  await page.evaluate(async binding => {
    await binding.call(null, 'yay!');
  }, bindingHandle);
  await browser.close();
})();

Would it work for you?


Adding Mac OS Support

I don't personally use MacOS, but it would be good for people who are making cross platform applications to have this feature, or something relatively close to the acrylic style.

Actually, this module appears to be modeled after the existing "vibrancy" support in Electron: https://www.electronjs.org/docs/api/browser-window#winsetvibrancytype-macos
So MacOS support isn't needed.

That's right, macOS supports the vibrancy option on the Electron itself. If this module is used in the same way as Windows in macOS, it is already processed to call the Electron built-in function without building the C module.


Improve peformance when first loading the homepage of your gitblit installation

Currently when you go to gitblit.example.com the website takes along time to load but if you go to the repo through the link it is faster too load. Loading the homepage should be made faster.

Agreed it should be faster.  I've looked into it a little.  Not sure what the problem is - but it's a VM problem.  I'll fix it sometime but it's not a high priority for me.

Thanks.
It is slow on Wikimedia so isen't just for dev.gitblit.org

Same symptoms different problem.

Ok.


Exception: Could not find module! lsasrv.dll

Hi, I have the following issue on one dump. The dump structure is fine, just the parsing of it fails for some weird reason.
Why is that caused ?
How could i potentially fix ? Is it something that has to do with my pypykatz version?
I remember i used to parse the same or similar dump some time in the past... not sure though

A dump from another system, Windows 10 and not Windows Server 2016 is parsed just fine

There are some weird edge-cases where parsing fails if for example the dump was taken within a few minutes of bootup. if it's a one-off issue then I can only help out potentially if you send me the dump file.


failover: ssl timeout

here are the sample data i have,
url: failover:(ssl://ec2-53-163-43-44.us-west-1.compute.amazonaws.com:61613?wireFormat.maxInactivityDuration=1200000)
username: docadeeccess
password: Ddddccess
additional ssl parameters.
trust store: doc-client.ts  (file attached)
trust store password: KEYsfft0r3Scrt
key store: doc-client.ks  (file attached)
key store password: KEYst0r3ffScrt
additional/optional parameters
reliable: true
queue name: DOC_REQUEST
I'm having below code
@login1='docaccrrress'
@passcode1='D0cCorrn@ccttess'
@options = "initialReconnectDelay=5000&randomize=false&useExponentialBackOff=false"
@remotehost1='ec2-53-163-43-44.us-west-1.compute.amazonaws.com'
client = Stomp::Client.new("failover:(stomp+ssl://#{@login1}:#{@passcode1}@#{@remotehost1}:61613)?#{@options}")
please correct my code and help me connection establishment

Little or no help is possible without error messages.
Timeouts can occur when code uses SSL but connects to a non-ssl port.  Check that.
Quit using a failover:// URL.  Follow the gem recommendations, which is to use a 'hash' login.
Quit saying something is attached, when there is nothing there.

ok..I will use the hash login..
Thanks for the reply

Closing this due to lack of further information from the OP.  Please re-open with additional examples if that is possible.


Ssl / Tls Connection Error when using RedmineManager

We changed our client due to a problem in https://github.com/zapadi/redmine-net-api.
See zapadi/redmine-net-api#171
We created a PR zapadi/redmine-net-api#172. Once it is merged and released we can revert the code from 0608386b845dba8f573bf5ea4450d63ed057c7f5

PR has been merged, waiting for release


Don't use red in the slider when virtual memory is 0 bytes total

Why is the virtual memory red in the slider when i don't have any virtual memory at all? The red makes me think something is wrong everytime i look at the slider. Another color would be nice or make it an option to select what ever color i want. At least use another color than red.
v18.40

Can you make a screenshot, please?

I tried to attach this file to the above message but it didn't worked... I don't know why i could add it here? Github issue?

Oh. What about piecharts? Do you have 3 or 4 of them?

3 or 4 of what?
I don't know if you could remove it completely if no virtual memory is installed?
How will it look like if you use piecharts? Any preview to show?

Those green circles on System Information page. You have a little part of it on your screenshot above.

I have 3 :)

Ok, this is a bug. I will fix it in 18.41


Use refactored PyCIEMSS lib

This PR refactors the service to use PyCIEMSS v0.1. The changes to the API are kept to a minimum but alterations are unavoidable since we are moving from "big box" to "small box" (atomic) operations.
PyCIEMSS features that still need to be incorporated into the service

[x] Pass parameters.dill into simulate (i.e. using inferred_parameters from calibrate for sample)
[x] Reimplement interventions (unclear which kind of interventions I should expose)
[ ] Fix solution mappings for ensemble-simulate to work with the new format

Regressions that have now been fixed but need to be incorporated into service

[x] Progress hook with additional 'loss' field.

Regressions in PyCIEMSS

[ ] Visualizations
[x] Progress hook
[ ] Ensemble Calibrate
[ ] Optimize operations
[ ] Logging decorator missing from ensemble-sample (very minor)

Please note the following regressions

#52
#53
#54
#55
#56

tl;dr: simulate and calibrate have been successfully refactored while there are various issues with everything else
Dashboard Results

simulate and calibrate now work for all except one models. This includes stockflow and regnets. All of the other other operations no longer pass


Added self test cases JPP_0512 and JPP_0513

JPP_0513 currently fail!
Reference:
https://github.com/test-fullautomation/python-jsonpreprocessor/issues/187#issuecomment-1892175292

Added self test case JPP_1002
To cover
https://github.com/test-fullautomation/python-jsonpreprocessor/issues/182


[tool_crash] StateError: Bad state: Future already completed

Command
flutter attach

@zhishui1314
Can you provide the complete error log along with flutter doctor -v ?


Allow to control the current directory of child processes

"Eradicate all occurrences of common courtesy from the documentation"
LMAAAAAAAAAAAAAAO


Disable tests that list artifacts across projects in hosted mode, fix bugs in listing artifacts across apis.

Fixes #841

As this didn't fail in CI, do we want to address that gap?

I don't think it's urgent, but I'll create an issue for that.


Fetching pull requests fails with "Not Found"

@ramya-rao-a has a reliable repro, I haven't been able to repro on my machine
Clone Microsoft/vscode-go
When expanding any of the category nodes in the tree that isn't just "Local Pull Requests", the octokit/rest library throws
GitHubRepository> Fetching all pull requests failed: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/pulls/#list-pull-requests"}

Now everybody knows all the remotes I ever used...


make chips always show all options

Feature Request
Would it be possible to make the chips component show all options when clicked? This is useful in situations when there is a finite set of options and It would be nice to present a user with all available options without them having to type anything.
What is the motivation / use case for changing the behavior?
Clicking in the chips area will show all available options.

This is done depending on your filtering implementation for chips, the demos use a filter method that puts an empty array in items when there is nothing typed in the input, you can just put the whole array in that case.


Table field mapping exception

in order to achieve data abstration in the scheduler layer.task-syncer has provides data mapping templates.but there seems to be some questions with the mapping between airflowDB.task_instance.try_number and comapssDB.task_instance.retry_times.
airflowDB.task_instance.try_number： execute count
comapssDB.task_instance.retry_times：retry count

try_number=1 is means execute once
retry_times=1  is means execute once ,retry once

@yuehan-mm We are already compatible with the airflow try_number problem, and the task-syncer mapping does not need to be modified, and we can be uniformly compatible in the program.


Cache bounding boxes, add st_extent, st_xmin/xmax/ymin/ymax for all types, enable setting SRS of output geometry when writing through GDAL, optimize st_intersects joins

Cache bounding boxes
We now compute and store the bounding boxes of geometries upon serialization to the GEOMETRY type. This allows us to quickly get the extent and optimize a lot of operations by first testing if their bounding box overlaps before we spend time or memory on further deserialization and computation.
Add st_extent and st_xmin, st_xmax, st_ymin, st_xmin
Because of the above these can now be implemented very easily and efficiently since they just have to deserialize the bounding box and nothing else, making it a o(n) operation for the GEOMETRY type. For the vectorized geometry POLYGON_2D and LINESTRING_2D types this is however computed on demand although there is no de/serialization costs for these anyway. For BOX_2D and POINT_2D these operations are basically zero-copy.
Enable setting the output SRS when writing through GDAL
You can now pass an optional "SRS" parameter to the GDAL copy function to set the spatial reference system of the output dataset explicitly. Example:
COPY (FROM t1) TO './test2.geojson' WITH (FORMAT GDAL, DRIVER 'GeoJSON', SRS 'EPSG:3857');

You should be able to pass anything that OGR understands
Optimize joins with st_intersects as join condition
Since getting the extents for geometries is so cheap now that we cache bounding boxes, I've implemented an experimental optimizer rule that rewrites inner joins using st_intersects as join condition to a comparison join on the extents followed by a st_intersects filter. This gets optimized into an IE-join which DuckDB does extremely well. I haven't tested it too much but I've seen a 5x improvement (joining 1mil nyc taxi ride pickup locations with 250~ taxi zones), and given that the complexity fundamentally changes (from O(MxN) to O(N log N)) I expect this to scale much better for even larger workloads.
I'm super excited about this and going to look into enabling this optimization for the other spatial predicates as well once I've done more testing.
You can read more about DuckDB's IE joins here

Cool! Will this enable predicate pushdown filtering on the bbox?

Not quite yet, but that's next!


Implement forward function resolution

This is a draft:  do not review

Enhance CqlPreprocessor visitor to compile function headers (AKA "preCompile")
Introduce a new common base class for CqlPreprocessor and Cql2ElmVisitor
Extract common methods from Cql2ElmProcessor to the new superclass
Store expression definition as a hash generated from the semantic function definition instead of a function String
Move loading of the system library from Cql2ElmProcessor to CqlPreprocessor
Move loading of the model from Cql2ElmProcessor to CqlPreprocessor
Note that errors will now be compiled in CqlPrerprocessor as they are in Cql2ElmProcessor instead of letting Exceptions get thrown
Introduce a new ForwardInvocationValidator that will a CallContext derived fro the calling function's representation of the called function versus an eligible function derived from a list of functions found by searching from a method name.  This includes comparing each side's list of parameter DataTypes as well as taking into account implicit conversions (ex FHIRHelpers)
Add new unit tests for various scenarios including dealing with overloads with normal types, generic types, as well as implicit conversions and namespace collisions (ex: System.Quantity vs FHIR.Quantity)

Closes:  https://github.com/cqframework/clinical_quality_language/issues/1191

Superseded by newer PR.


http/socks proxy support

Is your feature request related to a problem? Please describe.
Connect single database via proxy
Describe the solution you'd like
Add proxy config in Add connection

Hi @millken,
added in TODO list.


Storage not found when using in nuxt environment

There is no problem when using the Basic Usage method.
When using separate storage(localStorage, sessionStorage) for strategies in Advanced Usage
I get an 'is not defined' error.
Do I need any special settings?

I encountered the same problem, to solve it while waiting for a patch, it is possible to add a condition on the storage process.client. That way, it will be ignored on the server-side.
Example of code:
// store/index.ts
export const useState = defineStore('keyValue', {
  // states & actions & getters
  //
  //
  //
  persist: {
    enabled: true,
    strategies: [
      { key: "keyValue", storage: process.client ? sessionStorage : null },
    ]
  }

})


Try to fix playx support.

Media Player also affected

Will try fixing these issues sometime this week.

Couldn't get playx working despite fixing issues with external calls and enabling flash.  That being said, it seems to do a pretty good job of breaking itself regardless.
Media player has some more pressing issues -- It really seems to enjoy crashing.  I'll make it a priority I suppose.

Interestingly, Zor Player works fine.

PlayX now mostly works but crashes on deletion.

Hopefully fixed crash. Seems to paint with large black bars on top/sides. Not sure this is worth worrying about.


[auto_scheduler] buffer support, correctness check

This PR enables correctness check for a generated schedule.
It is useful for:

Metal / ROCM: For some invalid schedule, driver may skip it instead of return any errors (which will show as an impossble large FLOPS number)
Sparse kernel search

Example 1: correctness check. This will generate random buffers for correctness check
    if train_flag:
      #measure_ctx = auto_scheduler.LocalRPCMeasureContext(min_repeat_ms=300)
      measure_runner = auto_scheduler.RPCRunner("m1", "<IP_ADDRESS>", 9190, min_repeat_ms=300, timeout=30, repeat=3)
      tune_option = auto_scheduler.TuningOptions(
          num_measure_trials=1500,
          check_correctness=True,
          builder_n_parallel=1,
          runner=measure_runner,
          measure_callbacks=[auto_scheduler.RecordToFile(log_file)],
          verbose=2,
      )

      sch, args = auto_scheduler.auto_schedule(task, tuning_options=tune_option)

Example 2: Sparse tuning, this will register given buffers for measure.
if train_flag:
      #measure_ctx = auto_scheduler.LocalRPCMeasureContext(min_repeat_ms=300)
      measure_runner = auto_scheduler.RPCRunner("m1", "<IP_ADDRESS>", 9190, min_repeat_ms=300, timeout=30, repeat=3)
      tune_option = auto_scheduler.TuningOptions(
          num_measure_trials=1500,
          #runner=measure_ctx.runner,
          check_correctness=False,
          builder_n_parallel=1,
          runner=measure_runner,
          measure_callbacks=[auto_scheduler.RecordToFile(log_file)],
          verbose=2,
      )
      for k, v in BUFFER.items():
          tune_option.register_buffer(k, v)

cc @merrymercy  @FrozenGene

I recently refactored the task interface (https://github.com/apache/tvm/pull/7028).
The auto_schedule.py file is deleted.

@FrozenGene @merrymercy Updated.

I think you want to update submodule? So you have change showing you have changed the vta-hw submodule.

Updated

I find out this solution only work for a single task, but doesn't work with TaskScheduler. Will update it later.


Ge plugin: Show how many you can afford with the money you have

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. When horrible at math it would be nice to easily see how many I can buy with the cash I have in my inventory.
Describe the solution you'd like
Show the exact number of how many I can afford in the buy window of ge
Describe alternatives you've considered
No alternatives :P
Additional context
https://i.imgur.com/A225mKw.png

Duplicate of #8912


webrtc VideoFrame I420 not compatible with

Hi, webrtc in your repo io.github.crow-misia.libmediasoup-android:libmediasoup-android
has VideoFrame.Buffer and this one has method toI420() that returns VideoFrame.I420Buffer
But VideoFrame.I420Buffer is not compatible with I420Buffer from libyuv-android repo.
Can you fix it?
May be add methods to convert from webrtc I420 to your I420 and back from your I420 to webrtc I420
I have VideoProcessor that has callback fun onFrameCaptured(inputVideoFrame: VideoFrame?) and I need change this frame every frame.
Now I have to convert VideoFrame.Buffer.toI240() to nv21ByteArray : ByteArray - I have big function for that with code which I don't understand.
Then convert nv21 ByteArray to ByteBuffer, else I can't convert it to your buffers
byteBuffer = ByteBuffer.allocateDirect(nv21ByteArray.size).also {
                it.put(nv21ByteArray)
            }

Then I wrap byteBuffer by your Nv21Buffer
var nv21Buffer: Nv21Buffer = Nv21Buffer.wrap(byteBuffer, frame.buffer.width, frame.buffer.height)
Then I convert nv21Buffer to AbgrBuffer, then convert it to bitmap and do blur by Toolkit from com.google.android.renderscript
And now I need convert blured bitmap back to VideoFrame
            val abgrBuffer: AbgrBuffer = AbgrBuffer.allocate( frame.buffer.width, frame.buffer.height)

            nv21Buffer.convertTo(abgrBuffer)

            val inputBitmap = abgrBuffer.asBitmap()
            Toolkit.blur(inputBitmap, 20).also {
                it.copyPixelsToBuffer(abgrBuffer.asBuffer())
                it.recycle()
            }

            abgrBuffer.convertTo(nv21Buffer)

            val outFrame = VideoFrame(getFrameBufferByNv21Buffer(nv21Buffer), frame.rotation, frame.timestampNs)

            byteBuffer?.clear()
            byteBuffer = null

            nv21Buffer.close()
            abgrBuffer.close()

            return outFrame

This way so hard and I have too much memory leaks with buffers and bitmaps, maybe you can help me with this.
Thanks.

This is not a bug.
Android I420 is formatted as I420, YV12, NV12, or NV21, depending on the device.
ByteBuffer.allocateDirect will not release memory until after GC, so it is no surprise that allocating memory on a frame-by-frame basis will result in insufficient memory.

@crow-misia Ok, maybe you know how I should do it?
Convert VideoFrame.I420Buffer to your buffer without memory leak?

This is not a bug.
Android I420 is formatted as I420, YV12, NV12, or NV21, depending on the device.
ByteBuffer.allocateDirect will not release memory until after GC, so it is no surprise that allocating memory on a frame-by-frame basis will result in insufficient memory.

How do we get than the information which format is used internally? For example when i use camerax capture use case on galaxy S8 it seems to report the image.getFormat() does provide me the information, that this is YUV_420_888, but to convert it correctly i have to use nv21 instead. Does anyone know how to robustly determine the correct image format here?

I reworked my solution, @crow-misia  your library super useful thanks.


How to use debugger when uglifying?

How to use debugger for javascript when uglifying?

Per the Compressor Options of UglifyJS2, you need to set drop_debugger to false.
var gulp = require('gulp');
var uglify = require('gulp-uglify');
var pump = require('pump');

gulp.task('compress', function (cb) {
  pump([
        gulp.src('lib/*.js'),
        uglify({
          compressor: {drop_debugger: false}
        }),
        gulp.dest('dist')
    ],
    cb
  );
});

Today, the option is called compress, so the right config will be:
{compress: {drop_debugger: false}}


getBlogAvatar retrurns null

suddenly i keep getting empty results when trying to get any blog avatar using this code
$client = new Tumblr\API\Client('FaXbG***', 'qxuPr***');
$client->getBlogAvatar('david', 96);

https://api.tumblr.com/v2/blog/david.tumblr.com/avatar/96
not sure why its not getting the image, it worked before 🤒

This should be fixed now, thanks for reporting it!


python312Packages.slack-sdk: 3.33.2 -> 3.33.3

Diff: https://github.com/slackapi/python-slack-sdk/compare/refs/tags/v3.33.2...v3.33.3
Changelog: https://github.com/slackapi/python-slack-sdk/releases/tag/v3.33.3

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356128

x86_64-linux

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:x: 4 packages failed to build:

python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist

:white_check_mark: 6 packages built:

prowler
prowler.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356128

x86_64-linux

:fast_forward: 2 packages marked as broken and skipped:

krr
krr.dist

:white_check_mark: 10 packages built:

prowler
prowler.dist
python311Packages.slack-bolt
python311Packages.slack-bolt.dist
python311Packages.slack-sdk
python311Packages.slack-sdk.dist
python312Packages.slack-bolt
python312Packages.slack-bolt.dist
python312Packages.slack-sdk
python312Packages.slack-sdk.dist

diff lgtm, just waiting on ofborg in order to merge


Upload bigger images and retinafy them.

Previously from: https://github.com/dart-lang/pub-dartlang/issues/135

This issue has been moved to dart-lang/pub-dartlang#362.


Add option to reverse FlowContainer fill direction (HFlow bottom-to-top, VFlow right-to-left)

Adds an option to make horizontal FlowContainers add lines starting from the bottom instead of the top.
Video:
https://user-images.githubusercontent.com/66881186/222279524-b493f57e-2a49-45ad-b5f2-9cfcaae50ff3.mp4
Implements https://github.com/godotengine/godot-proposals/issues/6386

@TheSecondReal0 Remember that for GitHub video previews to work, you need to have a blank line before and after the video URL. I edited your post accordingly, but remember to do this in the future :slightly_smiling_face:

It's rather odd to have it only in HFlowContainer. The property could be renamed to e.g. reverse_fill and implemented in VFlow as right-to-left.

Layout direction is an internationalization option, you shouldn't mix the meanings here. It's effect should be applied on top of whatever the behavior is according to other options.

I agree layout direction shouldn't be used in this way, just acknowledging the workaround. I'll update this PR to handle vertical flows + rename variable

Renamed option to reverse_fill and made it affect vertical flow containers as well, not sure about the best way to describe it in documentation. When used in vertical containers it technically fills columns in the direction opposite layout_direction but that's less readable than "right to left". For now I just added another sentence but there's probably a better way to word it.
I added this edge case to be consistent with HFlowContainer switching directions when layout_direction changes, which doesn't seem to be explicitly documented anywhere.

You will need to remove the commit messages from the squash from your commit, all th ones copied from the merge, the message is much too big

The new message should probably be cleaned up as well, as it mostly contains minor progress descriptions not relevant to the commit like "ran --doctool"

Thanks for the review!

Just want to say how thrilled I am to be searching for my use case and find a PR adding the feature that was just approved 7 hours ago.

Needs a rebse to fix conflicts

Addressed @Geometror's nitpick (totally agree about ordering) and rebased. Hopefully ready to merge 🙏

Thanks!


Warning: Failed prop type: Invalid prop DotsWrapper of type object supplied to Slider, expected function.

I get this warning as well.

Same here, if I use a function returning a CustomDotsWrapper it gives me an error:

Objects are not valid as a React child (found: object with keys {$$typeof, render, displayName, attrs, componentStyle, foldedComponentIds, styledComponentId, target, withComponent, warnTooManyClasses, toString}). If you meant to render a collection of children, use an array instead.

I've got the same issue here. @ItsMrAkhil, do you  have any idea about how could we solve it?

Same issue

Same issue


Fix pruning of specialization dependencies

This comments out some code so that any dependency on an operation results in an edge to each specialization of that operation instead of just the specific specialization used. This is a patch to eliminate the issue, but we should consider either eliminating the commented out code and making this design change permanent (never prune dependencies of specializations even if they are unused), or allow for the pruning of both unused dependencies and the unused specialization itself.
Note that this also skips tests that fail due to the given work around.
Works around #757

@bettinaheim, I've been able to confirm that this workaround fixes the issue I was seeing using the generated packages and building code that uses AppyPauli and targets a provider.

/azp run

Annoyingly, this change means that the C# files produced will have more callables in them, which seems to be just enough to hit the timeout on the Linux perf tests. I tried a clean e2e build of main, and the Linux perf tests completed in 59 minutes, 4 seconds (see here). The limit is 60 minutes, so this PR is cancelled at 59 minutes and 59 seconds. From the logs, it looks like it gets cancelled at about 4/5ths of the way through, so making the test just slightly slower has resulted in hitting the timeout.

Given that this PR here https://github.com/microsoft/qsharp-runtime/pull/450 also had the runtime perf cancelled, the timeout may not actually be related to this change.

@swernli Closing this one, since I #764 deals with the same issue. I think we should have the feature branch there ready to merge to main soon, and otherwise we should cherry-pick that fix.


Make it possible to re-use active runners for a few workflow runs

Notes

in this case, it makes sense to terminate the runner using an idle timeout (e.g. terminate the runner if it doesn't do any job during the last 10 minutes)

Notes

in this case, it makes sense to terminate the runner using an idle timeout (e.g. terminate the runner if it doesn't do any job during the last 10 minutes)

How could this be implemented? Something like Cluster Autoscaler?
https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html
To make this work in cluster autoscaler way, you need to set up autoscaling groups and serverless app that terminates idle nodes.
Or, you could create cloudwatch alarm that scales out ASG when a SQS queue has pending messages, and scales in when SQS becomes empty for a while.
non-fio queue could deliver the same message twice , so FIFO queue would work better.

Calling this action with stop mode is no longer required if we use those methods?
If we create lambda function that periodically watches runner, stop action is useless.
SQS message's retention period can be short as 60 seconds, we could use that for emptying the queue, but setting too short value might terminate instance too early. Or, we could consume message manually and use retention as fallback, in case stop fails?

@vroad thank you for your ideas!
I thought about a bit different solution:

At the beginning of your workflow, you sill run the ec2-github-runner action. But in addition to the current parameters, you specify the number of EC2 instances you need to handle the workflow and the label, which will be assigned to each runner. Then, you use the label in the following jobs the workflow to run them on the newly created runners.
At the beginning of the execution, the action will check how many runners are already active with the specified label and create the rest if required.
When the action starts a new EC2 instance, some special code can be run, which monitors the active processes on the EC2 instance. If the EC2 instance is middle longer than some specified time, it can terminate itself and deregister the self-hosted runner on GitHub. However, this is the most unclear thing in this solution and should be verified properly.

In such a way, you should be able to gain the following benefits:

re-use runners for a few workflow runs;
at a consequence, save time at the beginning of some workflow runs as the runners will be already created;
the idle runners will be removed automatically;
for each workflow, you can specify different configurations and use different runners.

Does it make sense?

@vroad thank you for your ideas!
I thought about a bit different solution:

At the beginning of your workflow, you sill run the ec2-github-runner action. But in addition to the current parameters, you specify the number of EC2 instances you need to handle the workflow and the label, which will be assigned to each runner. Then, you use the label in the following jobs the workflow to run them on the newly created runners.
At the beginning of the execution, the action will check how many runners are already active with the specified label and create the rest if required.
When the action starts a new EC2 instance, some special code can be run, which monitors the active processes on the EC2 instance. If the EC2 instance is middle longer than some specified time, it can terminate itself and deregister the self-hosted runner on GitHub. However, this is the most unclear thing in this solution and should be verified properly.

In such a way, you should be able to gain the following benefits:

re-use runners for a few workflow runs;
at a consequence, save time at the beginning of some workflow runs as the runners will be already created;
the idle runners will be removed automatically;
for each workflow, you can specify different configurations and use different runners.

Does it make sense?

When the action starts a new EC2 instance, some special code can be run, which monitors the active processes on the EC2 instance. If the EC2 instance is middle longer than some specified time, it can terminate itself and deregister the self-hosted runner on GitHub. However, this is the most unclear thing in this solution and should be verified properly.

To reliably stop idle instances, the monitoring program should run outside of the instance.

If the instance is in ASG, unhealthy instances will get terminated, and new instances comes up as long as desired capacity is bigger than 0.
AWS doesn't always mark unresponsive instance as unhealthy, though.
To stop such instances you'll need custom health check. To save cost we can't keep ALB running, perhaps? So the only option left to us is custom lambda-based health check. Instances that does not report status correctly should be terminated.
Could be done without ASG, but no replacement instances come up.

When the action starts a new EC2 instance, some special code can be run, which monitors the active processes on the EC2 instance. If the EC2 instance is middle longer than some specified time, it can terminate itself and deregister the self-hosted runner on GitHub. However, this is the most unclear thing in this solution and should be verified properly.

To reliably stop idle instances, the monitoring program should run outside of the instance.

If the instance is in ASG, unhealthy instances will get terminated, and new instances comes up as long as desired capacity is bigger than 0.
AWS doesn't always mark unresponsive instance as unhealthy, though.
To stop such instances you'll need custom health check. To save cost we can't keep ALB running, perhaps? So the only option left to us is custom lambda-based health check. Instances that does not report status correctly should be terminated.
Could be done without ASG, but no replacement instances come up.

Just a random thought: would it be possible to use a mix of scheduled and workflow-run-triggered GitHub workflows to manage the pool of self-hosted runners (using ec2-github-runner to start/stop them)?


Migrate to Astro - Guide Stubs

This PR introduces stubs for various frameworks written by @sarah11918 (with support from @delucis for infra) that help document the process of migrating from another framework to Astro.
These stubs include the following frameworks:

Docusaurus
Eleventy
Gatsby
Gridsome
Hugo
Jekyll
Next.js
Nuxt
Pelican
SvelteKit
VuePress
WordPress

This current iteration of guides still needs proper stubs for NextJS and Gatsby before we're able to merge, hence the "Draft" status. This is a leftover from rebase dropping commits related to those two guides.
Further development of the NextJS and Gatsby guides can be found in #2211

Thanks for this, @crutchcorn! Just to clarify, these still have full content for Gatsby and Next. So, I can delete content here on this branch to make them actual stubs only?

OK, for anyone who might be arriving at this PR... still welcoming feedback, edits, comments! Don't be shy!
Will let this sit open for another 24hrs or so, but I think it's a good candidate for a FriYay Merge Day if we get enough concensus!
If by chance @crutchcorn is able to take a gentle readthrough for the recent changes/additions today or tomorrow, would love to make sure we catch anything that doesn't pass their smell test!


Fix the way we pass parameters to lerna so it is happy

basically, maven puts a quote around each parameter, and forces npm to take the entire parameter as a single parameter.

@Xenorith with this change, do we want to pin to a specific version?  Looking at other open source project, particularly, lerna itself. it seems like they use ^x.y.z most commonly.

hm in other places where we use lerna, we are using ~ to pin down the minor version, so i would prefer to maintain consistency, even though the usage/invocation pathway may be different

@Xenorith fixed version.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6078/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6079/
Test PASSed.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.0 please


⚠ Bofrost.es has degraded performance

In cfd8a05, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1426 ms

Resolved: Bofrost.es performance has improved in 2e330e2 after 6 minutes.


Documentation fixes

Fixed documentation of FulfillmentAutomation and TierConfigAutomation, and added documentation for ActivationTemplateResponse and ActivationTileResponse.

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   90.94%   90.94%
=======================================
  Files          31       31
  Lines        1413     1413
=======================================
  Hits         1285     1285
  Misses        128      128

Impacted Files
Coverage Δ

connect/resources/fulfillment_automation.py
33.78% <ø> (ø)
:arrow_up:

connect/models/activation_response.py
100% <ø> (ø)
:arrow_up:

connect/resources/tier_config_automation.py
97.29% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 858a256...12f88ba. Read the comment docs.


Use .Net Core instead of Mono

Can't be done -- the Google OAuth Nuget package does not support .Net Core at the moment.


Cleanup some code.

Cleanup some code.

@zhangzqit thanks for your contribution, we have removed the lambda function and merge the code to the master


Remove all imports from Loggers

Hello, guys.
Please remove all loggers from JAR'files
For example - slf4j
Due to exceptions like - ClassNotFound or StaticLoggerBinder.
It is ok, when you use logger while developing or testing, but remove imports to them before exporting to JAR file
Thanks in Advance

Show your pom.xml please :)

@raver119  I did not use pom.xml
I downloaded JAR (version: 0.8.0) files directly from maven repository

Ah. That explains. No way then, sorry. All this stuff is suited for use of build management systems, like maven or sbt or whatever.


[LocalizationProvider] Use correct locale type

Fixes https://github.com/mui-org/material-ui/issues/28925

[x] I have followed (at least) the PR section of the contributing guide.

Seems like there is not much activity on the pull request, and considering that we are moving the pickers to https://github.com/mui-org/material-ui-x I am closing the pull request. cc @flaviendelangle


No matches for kind "InferenceService" in version "serving.kubeflow.org/v1beta1"

/kind bug
What steps did you take and what happened:
I installed KFServing and Kubeflow, have tried with a v1alpha2 inference service which worked. However, I would like to use certain features made available in the v1beta1 version, mainly with regard to the V1beta1PredictorSpec and V1Volume. I always end up with the No matches for kind "InferenceService" in version "serving.kubeflow.org/v1beta1" error though.
What did you expect to happen
I expect the model to be deployed successfully
Environment:
Istio Version: 1.6.0
Knative Version: 0.14.3
KFServing Version: 0.4.1
Kubeflow version:1.2.0
Kubernetes version: (use kubectl version): client:1.19.3, server:1.18.14
OS (e.g. from /etc/os-release): macOS Catalina
/kind bug

@OfTheThorn v1beta1 version is not integration in kubeflow yet, we are expecting to install it in Kubeflow 1.3


[DNM][VL] test march=native

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@zhouyuan, we may also need to below setting.
https://github.com/apache/incubator-gluten/blob/main/cpp/core/CMakeLists.txt#L27

we may add build flag to control march. default is native.

we may add build flag to control march. default is native.

+1, will clean up on the build profile(native, avx512, avx2) and send out for review.


fake obs rate or local storage option

To give a -sort of- feedback to the user, we can periodically calculate their false observation rates and report back every week/month.
And/or we can allow store_locally=True option when publishing their observations, and allow user to store their own messages to their local machines.

False obs rate needs to be tracked in SNEWS CS.
Decide what counts as false observation.
Where it fits with retraction messages.
do not need to provide a tool for storing their-own messages.


setting for dart.flutterSdkPaths does not work

I have 2 flutter sdks on my labtop, so I add both path to the dart.flutterSdkPaths. Then I clicked the flutter version on the status bar, it only shows one option. Please help, thanks.

Please file this issue against the flutter extension. Thanks!


Can't add my ldap user into default env

Rancher Version:
1.1.3
Docker Version:
1.12
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher vs external db vs ldap
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Open default env and add user from ldap by login (not by full dn)
Results:
see picture

Expected:

After deleting default local user, it's has been done. No error any more

Did you at some point turn off authentication then turn it back on?

No, I don't.


Version build number is not updated, while there was a new version released

I've two versions installed in my test environment and the version build number is on both systems 0.1
On the first machine I have a build version 0.1. On this machine I have no search functionality within the CWE list by adding a new finding to a report. This machine is from 11/Nov/2021
On the second machine I have a build version 0.1. On this machine I have the search functionality within the CWE list by adding a new finding to a report. This machine is from 26/Nov/2021
By using a build number I can related issues to a version (build number) which will improve code quality and it will make communication easier.

In the meantime is for example this issue fixed:  https://github.com/1modm/petereport/issues/4
Both versions have the same build number.

You are right, I forgot to change the version, I will try to keep an updated changelog. Updated to v0.3

Tested - Solved


Fix development Linux setup

Fix Linux development setup
For Linux, it's neccessary generate SSL certificate for the application to use. If the application doesn't find the certificate, an error is thrown. This PR creates shell command to generate this certificate and a docker-compose file for development mode.

Created a docker-compose dev file for development mode
Fixed Dockerfile to use layer cache
Created a shell scripts file to generate ASP NET application certificate

Issue: https://github.com/MUnique/OpenMU/issues/189

Thank you! I did some smaller adjustments. Can you review my changes, do they make sense to you?

It's Ok


[BUG] Edit existing data

Package version, Laravel version
5.4
Expected behaviour
When looping each row from a file and edit its details, the result export file should contain the updates.
Actual behaviour
When looping a csv file inside the load callback, the row updates aren't persisted in the exported file.
Exception stack trace
There's no exception, the expected logical output is wrong.
Screenshot of Excel file
The csv column updated still having the same data that the loaded file after updating it in the callback.
Steps to reproduce the behaviour
Upload a CSV.
Load the CSV.
Loop through them by using the each method from the collection
Either use $obj->put() method or $obj->key property to set the new value
Export the resultant csv in the same format.

That's not how it works. You have to modify cells or append/prepend rows (see documentation)

Hi!
Have, the next question. I tried to edit some excel file used as template adding data from database. The template file has 3 sheets, in which one of it, has various formulas.
The problem, is that the generated excel doesn't preserve VLOOUKP formula, but actually preserve another formulas, like ISBLANK.

I know this is an old issue for an old version of laravel-excel (v2.1.x), but I just had a problem with this and I want to share what I figured out:

If you open a file you get an instance of Maatwebsite\Excel\Readers\LaravelExcelReader (let's call this $reader)
If you follow the docs and use $reader->get() or $reader->first() or $reader->all() then you get an instance of Maatwebsite\Excel\Collections\SheetCollection or Maatwebsite\Excel\Collections\RowCollection
If you modify these after opening an already existing file then calling ->export() or ->save() or ->string() will ignore your changes and use the original data that was in the file you opened.
However if you call $reader->sheet($sheetIndexOrName = 0) you get an instance of Maatwebsite\Excel\Classes\LaravelExcelWorksheet which extends PHPExcel_Worksheet
if you modify your LaravelExcelWorkSheet instance then calling ->export() or ->save() or ->string() will use your modified data as expected.


Add Multi-stage build to Dockerfile

We should adopt a multi-stage build for our Dockerfile. This should allow us to reduce the final image a fair bit.

Fixed by https://github.com/NebraLtd/hm-diag/pull/242


OpenCensus Trace Exporters.

A spec for writing Trace (aka span) Exporters.
Open TODOs:

[ ] What about events on spans?
[ ] Add Links to Spans spec
[ ] Add Annotations to Spans spec
[ ] What about span type? This can be set in OpenCensus.
[ ] Is there a "404" like status code we should be ignoring?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Okay, I updated this Pull Request to represent what our team implemented for the OpenCensus go exporter! 🎉

@rachelleahklein and @jkwatson This is reready for your review 🎈


Fix run repeatability/caching issues (#1138, #1139, #1140)

This fixes a number of issues discovered in 0.12.1. Two are sinter-only issues, and one is a kind of egregious (but in practice mostly benign) bug around case comparisons that almost entirely manifests in snowflake.
I had a heck of a time reproducing user reports, and the new integration tests have to really dig into the cache a bit more than I'd like, but I do believe this fixes #1140 and the tests will catch any regressions.
Basically, cache dict keys are now always lowercased, and access to fields from the inner Relation are also lowercased, but the underlying Relation representation is not.
One thing that's a bit weird is that added nodes now show up in list_relations as their inserted text (though with proper quoting fields). dbt seems to handle that well and the tests are okay, but it is a potential source of issues for things that inspect list_relations output. I don't see a way around that without trying to guess what the db would do to your relation names, which we discussed in slack and decided is not a great plan.

Sure! The easy example is on snowflake so I'll use that. Imagine you have models/model.sql and your schema is analytics. In snowflake, with quoting set to False and assuming you haven't set the server-side flag that defaults things to lowercase, the name of the relation will become ANALYTICS.MODEL on the database end when it's created.
Calling _list_relations() would then come back with schema="ANALYTICS", identifier="MODEL" with quoting set to True for schema/identifier on the resulting relation.
With this cache, you'll get schema="analytics", identifier="model" and quoting set to False. The old behavior is more precise, but the new behavior is as accurate as we can be without going out to the database and actually re-querying.

ok, thanks! That's really helpful. I think dbt has to work this way. It would be wholly unreasonable for us to predict the exact casing that Snowflake will pick in this case. The user might set quoted_identifier_ignore_case to TRUE, for example, and checking before each cache entry would defeat the purpose of caching. This is great, 🚢 it


⚠ Bofrost.com has degraded performance

In d7c3950, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 6124 ms

Resolved: Bofrost.com performance has improved in b079a18 after 6 minutes.


[Portal] Prepare deprecation of onRendered

Starting now, people can use the ref instead of the onRendered prop. I think that we should remove it in v5.
Closes #16595

I have removed the onRendered prop usage from the Popper.js component. It seems to work OK.

Rebased.


Add temperature, top-k and top-p logits processors

Hello,
In outlines.text.generate.sample, only greedy and multinomial methods are available. Would it be possible to implement some classical features in the multinomial function such as top_k, top_p or temperature ?
Thanks for your work,
Simon

Yes, definitely!

Also, we need to add beam search.

Tracked by #258

#533 introduces a small refactor of the samplers that would allow to pass the top_k and top_p arguments to the multinomial sampler. We could pass the temperature using the same mechanism as well

top-k was added in #642, and I opened separate issues for the other requests: #645 and #643.


Install system packages in weekly_fuzz workflow needed by debug collector

Fixes https://github.com/auxoncorp/modality-probe/runs/1892693303?check_suite_focus=true

Will follow up with new clippy changes and a version bump.