[flaky-test] [v2prov] [release/v2.7] Etcd restoration provisioning tests collecting/printing test data bundles when they are not actually failing

Flaky Test
Test_Operation_MP_EtcdSnapshotCreationRestoreInPlace
Test_Operation_MP_EtcdSnapshotOperationsWithThreeEtcdNodesOnNewNode
Test_Operation_MP_EtcdSnapshotOperationsOnNewNode
Test_Operation_Custom_EtcdSnapshotCreationRestoreInPlace
Test_Operation_Custom_EtcdSnapshotOperationsOnNewCombinedNode
Test_Operation_Custom_EtcdSnapshotOperationsOnNewNode

Release Branch
source branch of PR: release/v2.7
The tests are printing test data bundles and failure messages even though they are not actually failing. Furthermore, they are printing \n which is not useful.

Hello @Oats87
Can you confirm to me if this issue is also regarding this kind of Drone Build Failure:
--- FAIL: Test_Operation_Custom_EtcdSnapshotOperationsOnNewNode (1151.63s)
FAIL
FAIL	github.com/rancher/rancher/tests/v2prov/tests/custom	3044.249s

https://drone-pr.rancher.io/rancher/rancher/32876/4/2

@nicholasSUSE , nope. If a test actually reports FAIL it's indeed failing.
I see Test_Operation_Custom_EtcdSnapshotOperationsOnNewNode mentioned as intermittently failing before but I don't see flaky-test issue filed for it (it was before we established flaky-test processes). If you have a build where it failed please file flaky-test issue - https://github.com/rancher/rancher/issues/new?assignees=&labels=kind%2Fflaky-test&projects=&template=flaky-tests.md&title=[flaky-test]

@Oats87 , just reran CI on https://github.com/rancher/rancher/pull/42779. Please also create PR for release/v2.8 as well.

The following two cases failed in https://drone-publish.rancher.io/rancher/rancher/10741/4/2

Test_Operation_MP_EtcdSnapshotCreationRestoreInPlace
Test_Provisioning_Custom_ThreeNode


Mongo integratation to persist Data

By following these steps, you can efficiently manage a stateful graph in LangGraph, leveraging its upsert capabilities to maintain a dynamic and consistent graph database. This approach is particularly useful for applications that require real-time updates and historical state tracking, such as social networks, recommendation systems,Human decision, and knowledge graphs.

Thanks for the PR, @Mahdi-Ba ! I think it'll be a couple more  weeks before we move the custom checkpointer workflows out of Beta, at which point something like this may be more viable. As it stands (and likely because of the lack of that documentation), this example doesn't actually use the LangGraph API as it is intended, so I wouldn't recommend people use this specific approach

echoing @hinthornw , this is best done by creating a subclass of the langgraph checkpointer, something we will do once the interface is more stable


[bug]: Settings not being copied when using "Use all parameters"

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux, Firefox
GPU
cuda
VRAM
6GB
What happened?
img2img strength and restore face settings are not being copied when using "Use all parameters"
Screenshots
No response
Additional context
No response
Contact Details
No response

Face restore is expected, img2img fixed in upcoming release.
Postprocessing metadata cannot be recalled because we can have an arbitrary number of postprocessing steps in the metadata but cannot recall an arbitrary number of steps. So we have decided to not give a false impression that postprocessing steps can be recalled.


Same file upload

<FileInput name="myImages" accept=".png,.gif, .jpeg" className="chat-file-upload"                                                                placeholder="Upload Image" onChange={this.uploadFileToChat} multiple readAs='binary' >                                                     </FileInput>
If you try to upload same file again then it won't detect onChange event. Can you please add some method like ClearInput which will clear this input value?
Thanks!

I haven't fully tested this, but if you add value='' to the <FileInput> tag, it will allow you to repeat the same upload, as long as the component re-renders after the upload.


Process RITE feedback of first participant

Some minor tweaks to the UI according to the feedback of our first participant.

Is this spacing intentional (or is it my screen size), can't we just put them under each other.

Can you break words in a diff?

lgtm


When the data on the X-axis is blank, it will cause the chart to display blank

The data can not be blank, if you want to hide x-axis, you should set the options like this:
// custom option func
func(opt *charts.ChartOption) {
	opt.XAxis.Show = charts.FalseFlag()
},

When there is only one data, the height of the label occupies the entire coordinate axis, and the display is not very beautiful. I want to set the height smaller, so I think of filling in 4 empty strings. Here, I use . to fill it, because it uses empty strings. The string will become blank, so that the adaptively generated height after this operation will meet the requirements. How to set the height of the label to be fixed when the amount of data is small? Or I want the filled axis data not to be displayed

The null value is not supported. You can try using charts-rs，Web Demo Page: https://charts.npmtrend.com/， the options:
{
  "width": 600,
  "height": 400,
  "font_family": "Roboto",
  "sub_title_text": "Sub Title",
  "legend_align": "left",
  "type": "horizontal_bar",
  "title_text": "World Population",
  "x_axis_data": [
    "Brazil",
    "Indonesia",
    "USA",
    "India",
    "China",
    ""
  ],
  "series_list": [
    {
      "name": "2011",
      "label_show": true,
      "data": [
        18203,
        23489,
        29034,
        104970,
        131744,
        null
      ]
    },
    {
      "name": "2012",
      "label_show": true,
      "data": [
        19325,
        23438,
        31000,
        121594,
        134141,
        null
      ]
    }
  ],
  "series_label_formatter": "{t}",
  "series_label_position": null,
  "theme": "grafana"
}

Thank you, I chose the fan chart instead. I have one last question, can the Y-axis be set to an integer?

Set the max value of y axis:
// custom option func
func(opt *charts.ChartOption) {
	opt.YAxisOptions = []charts.YAxisOption{
		{
			Max: charts.NewFloatPoint(6.0),
		},
	}


Fix remaining vendor comments

This is a continuation of https://github.com/caskroom/homebrew-cask/pull/18051. The only missing point (as soon as it is achieved this issue can be closed) is:

[ ] Verify and improve all current … is the official download host per the vendor homepage comments in caskroom/cask.

How to help (needs to be made by maintainers):

Pick any (or many) cask from the list at the bottom of the post.
Go to its website, and verify the download URL.
Update it’s vendor comment above the url stanza appropriately. That may mean removing it entirely (in case the URL is now updated and from the same host as homepage), or updating it with the new rules introduced in #18051.
When you wish to stop, regenerate the list and update it on this post.

How to regenerate the list:
List will be copied to clipboard. Should be done only after you merge your fixes.
brew update
cd "$(brew --repository)/Library/Taps/caskroom/homebrew-cask/Casks"
grep --files-with-matches 'is the official download host per the vendor homepage' * | sed 's/^/+ /' | pbcopy
cd -

List

kylo.rb
league-of-legends.rb
metanota.rb
mypaint.rb
qbittorrent.rb

Pinging @victorpopkov since you’ve worked a lot on this as well.
Almost done. The ones left are the ones I couldn’t finish at the time for one reason or another (like not finding the download URL, or website being down).

This can be closed after merging https://github.com/caskroom/homebrew-cask/issues/22264.

Great news! Thank you.


multiboot2: remove odd offset thingy

This removes the weird load_with_offset thingy which can also be done via an adjusted pointer. -> less complexity
Furthermore, the Multiboot2 information structure now captures the lifetime of the context where it is created.

Hey @YtvwlD
What do you think about this API change? I'd like to get rid of the weird offset thingy. I do not see a reason why it is necessary at all. Please change my mind, if I miss something.

I did not understand why it was there, either. And the PR that added this came with no explanation either, right?
Perhaps this is for segmentation or something like that?

So, you are also in favor of this API change, @YtvwlD , right?

I don't have an opinion on this.


Pack register API should fail on pack register failure

This PR updates pack register API so it fails on failure in case a pack registration fails (error is returned to the client).
Before that, it didn't fail so it was hard to debug pack installation issue (st2 pack install would succeed even though if pack registration failed). This way it's also consistent with st2ctl reload / register content which fails on failure by default.
If for some reason user wants not to fail on failure, they can pass "fail_on_failure" option in the request body set to False.
While working on that I noticed there is another issue - we didn't actually fail on failure before if registration of pack itself failed, we only failed if pack resource registration failed.
TODO

[x] Tests (pack registration fail, pack registration fail)
[x] Make sure all the "failed to register" exception messages include name of the resource and / or pack which caused the failure

Note: We decided to include this in the next patch release (v2.0.1).

I'd say that fail_on_failure should be a client side feature. The way it is implemented in this PR gives user zero insight into what kind of content had been registered before the failure occured and essentially leaves st2 in a broken state. It was working for st2ctl because we had an intermediate results flushed to stdout. With st2api, we don't have this luxury.
Instead, API endpoint should attempt to register everything this instance has, gather all the errors happened and return them for client to decide on what to do with it.
The only use for server side fail_on_failure is for the case when it takes too long to register all the content every time, but I'd say we need to treat it as a dangerous feature one should be fully aware of consequences of using it. Also, the output format should be shared with the one proposed earlier (result + list of errors rather than a single faultstring).
Also, let me remind you that we still have fully functionsl implementation of fail_on_failure in st2ctl and that we intend on stop exposing registration process to the user during stage two and we'd better start thinking from the perspective "how it should work in the future" rather than "how it worked previously".

@enykeev Yes, it leaves stuff in a "semi consistent state", but this will always be the case no matter what approach we go with unless we implement some kind of transactions for registration (register all or nothing if a failure occurs).
This would be ideal, but imo that's overkill and users should be encouraged to run those checks themselves on their CI / CD servers to catch such issues before pushing things to production (that's what we do on Travis with our and community contributed packs).
Having said that, I think that failing early is good enough. I do agree though that there is a small difference between st2ctl and register API - st2ctl prints some logs so use has more context (if required), but this only happens when running it with -v flag which is not a default behavior.
To make it easier to troubleshoot when registering multiple packs using the API we could add debug=True or similar parameter which would cause it to collect and returns the logs and similar.
And it's also worth nothing that all of that only applies when registering multiple packs at once. On packs.install, we only register a single pack so this is not an issue. As @dzimine said, I would personally also be fine with this API just supporting registration of a single pack at once then this problem goes away completely.

Also, let me remind you that we still have fully functional implementation of fail_on_failure in st2ctl and that we intend on stop exposing registration process to the user during stage two and we'd better start thinking from the perspective "how it should work in the future" rather than "how it worked previously".

One of the problems with that is that pack install command already uses register API which currently doesn't correctly report errors back to the users which makes a bad UX and also makes it hard to troubleshoot what is going on.

but this only happens when running it with -v flag which is not a default behavior.

I'm talking about the stage registration fails on. With the approach you proposed I can't tell what types of content has been registered and where in the process the fail had happened (eg have all the actions been registered). And after registration is over, there is no way to figure what was registered and what wasn't either...

To make it easier to troubleshoot when registering multiple packs using the API we could add debug=True or similar parameter which would cause it to collect and returns the logs and similar.

No point of hiding it behind the flag, you want to get this info 100% of times. It's never ok if your registration failed. You want to get it fixed asap, not running it again with some magic flag.
We're going to spend more time arguing than actually making the change. Again. And you know it's better UX to give user all the information upfront rather than making him rerun registration until he fixes all the errors one by one.

Current coverage is 75.38% (diff: 77.78%)

Merging #3080 into master will decrease coverage by 1.85%

@@             master      #3080   diff @@
==========================================
  Files           430        430
  Lines         22124      22071    -53
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          17086      16637   -449
- Misses         5038       5434   +396
  Partials          0          0

Diff Coverage
File Path

•••••      50%
st2common/st2common/util/api.py

•••••••••• 100%
st2common/st2common/models/api/pack.py

•••••••••• 100%
st2api/st2api/controllers/v1/packs.py

•••••••••• 100%
st2common/st2common/bootstrap/base.py

Powered by Codecov. Last update f42457a...e2f3842

Will also cherry-pick into v2.1.1 branch.


Enhance Cromwell WES endpoint for Dockstore WES CLI testing

One can build a self hosted Cromwell WES endpoint but the Cromwell code is currently not fully functional with respect to the WES schema. The code can be enhanced to better support the WES schema especially the workflow run POST request.
Enhancing this code would provide an endpoint to fully test the Dockstore WES CLI implementation.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Seabright Sprint 7 Gondola
┆Issue Number: DOCK-583
┆Epic: WES API support

➤ Walt Shands commented:
Directions for building the Cromwell WES endpoint from Jeff Gentry:
If you build Cromwell from source you should see a build wes2cromwell jar in cromwell/wes2cromwell/target/scala-2.12/. Either via config file or command line options you'll want to set config parameters wes2cromwell.interface, wes2cromwell.port, cromwell.interface, and cromwell.port. Run the jar as a separate server from the underlying Cromwell server.
At that point you should be able to send most well formed WES requests to the wes2cromwell process and it'll forward a reshaped request to the cromwell server, and intercept/reshape the response coming back from Cromwell.
I should also add that since that work, some of the simpler WES endpoints are now natively supported by Cromwell directly: service info, runs status, and runs cancel
So I'm pretty sure that I'm right that there's a catch-22 here. With the current WES shim code, workflow_url is passed to Cromwell as workflowUrl, and the first workflow_attachment (and only the first, see note below) is passed in as a workflowSource. Cromwell won't allow you to have both set, and WES requires workflow_url. While I remember this working at one point I'm likely remembering an earlier revision of the WES spec.
For the wes2cromwell code I don't know about codegen, but I doubt it (question on whether some server code was built with Swagger Codgen). There was an earlier incarnation developed by someone else, and then leading up to Basel I ported that to update w/ being more in line with the contemporary spec.  I'll add that there's also a small amount of code in Cromwell itself (package cromwell.webservice.routes.wes) which is (was?) my attempt at doing the work directly instead of having the shim layer.  Frankly I did the easy parts and that was the end of that.
re contributions - definitely. If someone wanted to wade into the code base and clean it up we'd not at all be opposed. If you're interested in going that route I can provide pointers and guidance as much as I can.
re workflow_attachment in general: I really regret pushing for that in the spec as the way that's structured isn't going to play nice with the libraries we use to handle HTTP. AFAICT it's going to require a lot of hand coding of everything the library is providing for us.
If you only want to send a single workflow file (which appears tobe the case) the easiest path would likely be to hack the wes2cromwell shim to not require workflow_url and then just do one or the other. It'd be moving things further away from WES compliance but if we start putting future effort into WES compliance it'll ultimately wind up in the native support path anyways

➤ Charles Overbeck commented:
Document changes that are needed by Broad.

➤ Walt Shands commented:
Instructions for setting up a local WES Cromwell endpoint and source code changes need are located here:
https://wiki.oicr.on.ca/display/DOC/Setting+up+a+local+Cromwell+WES+endpoint ( https://wiki.oicr.on.ca/display/DOC/Setting+up+a+local+Cromwell+WES+endpoint )
and duplicated here:
https://docs.google.com/document/d/1bOiHEakZ03mGjFkhSHrUuHCg43OBFxr7hut8SEq1oOo/edit#heading=h.o9r5yame6vdg ( https://docs.google.com/document/d/1bOiHEakZ03mGjFkhSHrUuHCg43OBFxr7hut8SEq1oOo/edit#heading=h.o9r5yame6vdg )


Release v0.6.3

What this PR does / why we need it:
release v0.6.3
trigger auto release
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/lgtm
/approve

/retest


Replace run_forever with start/stop

Speculative Issue for Discussion
The run_forever() API is prevalent throughout tickit. Components, adapters, schedulers etc. all have it. The idea is to collect this bucket of things into a giant asyncio task that is essentially :
asyncio.wait([thing.run_forever() for thing in all things])

This is convenient for running arbitrary simulations but painful to test. Tests need to know a component/adapter/scheduler has completed startup tasks and is ready to accept API calls. See https://github.com/dls-controls/tickit/issues/76. run_forever() often performs startup tasks opaquely, so the tests can't know when it's done. There have been various workarounds throughout the codebase such as exposing asyncio.Events or just having a sleep to allow servers time to start. None of these are ideal.
We also cannot easily shut things down between tests, there have been instances of tests breaking other tests. In some cases we have restored forcing task cancels.
I propose we go through and change all of these APIs from
async def run_forever(self) -> None:
    ...

to
async def start(self) -> None:
    ...

async def stop(self) -> None:
    ...

The contract then is that start() performs all startup tasks and can be awaited on and stop() can be awaited on until all tasks have shut down. It is then easy to offer a fixture for a particular component et al.
@pytest_asyncio.fixture
async def thing() -> Thing:
    thing = Thing(...)
    await thing.start()
    yield thing
    await thing.stop()

Tagging for discussion: @abbiemery @coretl @tpoliaw @DiamondJoseph

@abbiemery  has anyone been asigned to do this?


[TC-402] - ds xml_id is not editable

isn't this to make xml_id read-only?  title confused me..
and there are conflicts now..

conflicts resolved. this PR is to make ds.xml_id immutable. you're not allowed to change the xml_id of a deliveryservice once it has been established. bad things happen if you do...


Structure check modal window causes error when closed right after update

Bug appears almost randomly on the same preconditions. Try to reproduce it more than once.
Steps to Reproduce

Click "Structure Check" button
Remove two random checkboxes
Close "Structure check" modal window
See error or try again with different checkboxes

Expected behavior
Structure check state changed.
Actual behavior
Error message is shown in a bit after closing modal window.
Screenshots

https://user-images.githubusercontent.com/97884482/155752265-58cccd21-5783-4022-8484-03a842f0a8d4.mp4
Desktop:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/98.0.4758.109 Safari/537.36

Update after analysis:
Error is thrown when Check structure modal is closed before response from server was received.
To get consistent error reproduction, open Check structure and press Esc key right after modal appears, or right after click on any checkbox.


[PE-D][Tester C] Student name cut short

When viewing a student with a particularly long name, if the name does not fit in one line given the current window size, it it cut off with ellipses and there isn't a way to view the full name by scrolling or a display function, etc.
Steps to reproduce:
Add a student with ADDSTU with a very long name
View the application in a windowed mode such that the name no longer fits in the viewing box.

Labels: severity.VeryLow type.FeatureFlaw
original: eliotlee68/ped#1

Not a feature flaw. Is a functionality bug caused by extreme user behaviour: very long input values:

Problems caused by very long input values: When a user input is unusually long e.g., a very long name, a very large number, it can cause problems e.g., the UI layout can get messed up, some part of it might get cut off.
These can be considered cosmetic issues (i.e., severity.VeryLow) of type.FunctionalityBug.
However, if the problem can hinder the user (e.g., not seeing the last part of a very long name might not hinder the user but it does hinder the user if only the first few characters of the name is shown), the severity can be Low or higher.

To prove that this is not in scope, we need to specific in the UG that it is not supported

How to prove that something is response.NotInScope: In general, a flaw (e.g., a missing feature, a suboptimal design of a feature, a known bug) can be considered NotInScope if rectifying it is less important (based on the value/effort considerations) than the work that has been done already (because it is fine to delay lower priority work until future iterations).
In addition, the following (at least one) need to be satisfied:

The UG specifies it as not supported or coming in a future version.
The user cannot attempt to use the missing feature or when the user does so, the software fails gracefully, possibly with a suitable error message i.e., the software should not crash.

If a bug qualifies for response.NotInScope, the dev team will not be penalized, but the bug reporter will earn a small amount of credit for reporting it.

Todo:

[ ] Add in the user guide that our application does not support text wrapping within the student contact list display panel, so long name will be cut off. It is less important, as names are not this long in reality, and not having the full name does not make it harder for a tutor to differentiate a student in the contact list.


Docs[upstash_kafka_credential]: Add Example with permissions to access all topics

This pr adds an example to the documentation on how to add Kafka credentials that have permission to all topics in a cluster.

Thanks for the PR, @Cliftonz


Using codesearch for my own queries. (How to instanciate model.py Class)

Hello I managed to finetune codebert for the codesearch task, and I was wondering how I could use the model.bin I just created to perform codesearch on my own natural langage queries.
So the model.bin is a state dictionnary containing all the weight but I don't get how I am supposed to go from that to a working model.
I tried to instanciate it with
model = RobertaModel.from_pretrained("microsoft/codebert-base")
but it returns the following error
RuntimeError: Error(s) in loading state_dict for RobertaModel:
Missing key(s) in state_dict: "embeddings.position_ids", "embeddings.word_embeddings.weight", "embeddings.position_embeddings.weight", "

etc,etc
And I noticed that there is a Model class in model.py so it is probably the one I mused use but I don't get how am I supposed to instanciate it in order for the model to work ? Can you show me an example or explain me a little bit ?
Thank you very much

And if instanciate is too complicated, how can I use the inference.py file to get my predictions in a file? Like I give the model a string of the query and it output me the code predicted

Response here https://github.com/microsoft/CodeXGLUE/issues/52


Fix on kostenbaten calculations

[ ] Sign of EnergyTransactionVolume_kWh will be flipped in AnyLogic @GillisHommen and as a result the following logic should also flip:

        volume = obj.get("EnergyTransactionVolume_kWh", 0.0)
        if volume < 0:
            return volume * (
                obj.get("feedinTax_eurpkWh", 0.0) + obj.get("feedinPrice_eurpkWh", 0.0)
            )
        return volume * (
            obj.get("deliveryTax_eurpkWh", 0.0) + obj.get("deliveryPrice_eurpkWh", 0.0)
        )

[ ] Add a proportional tax method that depends on financial volume of other contracts
e.g. tax on energy delivery bill.
Two options:

AnyLogic takes care of determining these taxes and all financialTransaction volumes
Cost module also determines the taxes based on other contracts of a single agent (starter in update-kosten)

Sign of EnergyTransactionVolume_kWh has been flipped in AnyLogic. A positive energy transation volume now indicates an energy flow from contractHolder to contractScope. Or vice versa, a new energy use by the contract holder corresponds to a negative energy transaction volume.
This is now in line with the financial transaction volume, where also a negative financial transaction volume indicates money flowing from contractHolder to contractScope.

I have implemented accounting of money-flows corresponding to all energy carriers, including taxation (proportionalTax_pct) in Anylogic in the Base_1may model. This results in the contractData output giving 0 for all energyVolumes and non-zero for financialTransactionVolumes. This also applies the delivery/feedin tax with the correct sign.
It is possible to disable/roll-back this functionality by setting the anylogic model input "B anylogic costs for all contracts" to false.


Add License, Copyright, and Info to Footer

This PR adds a LICENSE.md, correct copyright info to the footer, and a message in the footer about images being released into the public domain.

@katestange, should we add the note about images being released into the public domain in the README as well?

Thanks, it all looks great!  Maybe we should let Glen chime in before we merge?

Sounds good to me!

OK, have pushed the changes that create the version that received general approval on Slack. Given the fairly large changes in this round, @liam-mulhall thanks for reviewing one last time and merging. Hopefully you will be able to do something similar in the Vue3 PR once this goes into main and you rebase that. Let me know when that's all happened and the Vue3 PR is ready for review.

I'm happy with the changes you made, @gwhitney. I think @katestange is too, so I'll merge and then add the changes to my PR. I'll let you know when my PR is ready for review.


Exceptions rpfree

Hi,
How can I handle exceptions in rpfree?
sometimes I have pointers made by malloc and I wish I could release those points with rpfree.
Thx

rpmalloc is not designed to be resilient to errors, you must never pass a bad pointer to rpfree, or any pointer to a memory block allocated outside of rpmalloc

I know, but I have that casuistry.
Any ideas that can help me?

Do you use the malloc overrides, or call rp* functions directly?

call rpfree

Then only pass pointers to rpfree that you allocated using the rpmalloc series of functions, or am I missing something?

First sorry for my English.
I want to use your memory manager because according to my tests it is much faster than new / delete from CRT.
In my case all the new assignments that my code makes use rpmalloc but in many cases I have to delete from a third-party pointer that can be rpmalloc or CRT.
I had always thought of doing rpfree but if the pointer is a new operator CRT, an exception is thrown, and I wish I could capture it.
I have no way of knowing if doing rpfree is a pointer created by CRT or by rpmalloc.

Then I understand. Unfortunately, for performance reasons, there is no good way to know if a pointer is allocated by rpmalloc or not. The library expects the user to pass valid pointers to rpfree.
I guess the library could keep track of memory pages it owns and check if the pointer is within those, but that would come at a performance cost. I can add a feature request for that for future implementation.

FWIW, Intel TBB allocator supports this using a magic number for each of its span I think, might be a good solution without incurring any performance penalty...

Problem is that unless you know it is a pointer to a block allocated by rpmalloc, it is generally not safe to access the span header to check the magic since that is usually located in another memory page -> might segfault if it is a pointer from some other allocator implementation.

At the moment I am solving the issue by marking the buffer with some magic numbers and it works for me.
The performance has increased significantly.
If the library is improved in the future I will change the code to improve it.
Thank you very much for everything


Move away from JQuery

After some research it seems it will be better to move away from JQuery and maintain  userUI behavior using Vanilla JS.
There are a lot of available vanilla JS libraries.
Plain JS
Vanilla List

Too much of a work. It will be revisited when app reaches close to v1.0.0


Add an oidvector type for use in pg_proc

Summary of the changes / Why this improves CrateDB
Closes https://github.com/crate/crate/issues/10131
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please


Portal Image Outdated

Hello! Notebooks now have Spark pools and samples. Tks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ec5910fd-89bc-1b75-11aa-2e3b540534d8
Version Independent ID: f1eed558-bd20-1991-98e8-9fbebfd3b0ee
Content: Introduction to the built-in Jupyter notebooks support in Azure Cosmos DB (Preview)
Content Source: articles/cosmos-db/cosmosdb-jupyter-notebooks.md
Service: cosmos-db
GitHub Login: @markjbrown
Microsoft Alias: mjbrown

@Rodrigossz Thank you for reaching out and letting us know.
The Notebooks feature is still in preview and the experience on the Azure portal is continuously evolving. So there might be some delay in updating the documentation.
We will make changes accordingly.

@deborahc will most certainly have updates to this page coming as Notebooks moves towards GA. I expect that will include updates to the screen caps as well.
Thanks for raising
#please-close


How do I use the Container attribute renname ?

In the documentation, it's described as follows:
#[serde(rename = "name")]
Serialize and deserialize this struct or enum with the given name instead of its Rust name.

Allows specifying independent names for serialization vs deserialization:

#[serde(rename(serialize = "ser_name"))]
#[serde(rename(deserialize = "de_name"))]
#[serde(rename(serialize = "ser_name", deserialize = "de_name"))]

Is there some example ?
I really can't figure out how it works, what effect does it have.
use serde::{Deserialize, Serialize};

#[derive(Serialize, Deserialize, Debug, Clone)]
#[serde(rename = "aaa")]
struct A {
    name: String,
}

#[derive(Serialize, Deserialize)]
struct B {
    a: A,
}

fn main() {
    let a = A {
        name: String::from("hello"),
    };
    let b = B { a: a.clone() };
    let str_a = serde_json::to_string(&a).unwrap();
    println!("json a: {}", str_a);

    let str_b = serde_json::to_string(&b).unwrap();
    println!("json b: {}", str_b);
}

It's output is:
json a: {"name":"hello"}
json b: {"a":{"name":"hello"}}

But I think the serialization result of a is like this:
{"aaa": {"name":"hello"}}

or the serialization result of b is like this:
{"aaa":{"name":"hello"}}

I know this is an old issue but for for anyone else
If you want B to deserialize like that you need to use an enum like this
use serde::{Deserialize, Serialize};

#[derive(Serialize, Deserialize, Debug, Clone)]
struct A {
    name: String,
}

#[derive(Serialize, Deserialize)]
enum B {
    #[serde(rename = "aaa")]
    a(A),
}

fn main() {
    let a = A {
        name: String::from("hello"),
    };
    let b = B::a(a.clone());
    let str_a = serde_json::to_string(&a).unwrap();
    println!("json a: {}", str_a);

    let str_b = serde_json::to_string(&b).unwrap();
    println!("json b: {}", str_b);
}

The rename doesnt do anything on the struct because structs are not externally tagged like enums are.

JSON does not serialize names of struct types, so if you are only testing this with JSON, you aren't going to see the effect. Some other data formats do serialize the type names.


Add asynchronous execution

Rate generator should be asynchronous to data source and worker execution. Data source has buffering implemented but maybe create a thread that fills data source buffer. Worker tasks have to be executed async using a thread pool so that the execution time doesnt affect rate generation.

Current implementation of the rate generator is purely analytical, that is, rates are simply calculated using only input parameters. Therefore no needs for threads/async execution.
Datasource already has a buffering implementation.
Now there is a generic async implementation of the worker API.


Create a basic Jail management interface

One of our customers has requested a feature, that will help them manage FreeBSD Jails in a similar fashion to VMs: automated provisioning, ZFS clone as a templating mechanism, automatic snapshots and replication, parent/backup detection, prod vs test, REST API functions, access to existing VM network bridges, default and VM-like resource limits, Jail uptime monitoring, start/stop/snapshot using our WebUI, automatic HA failover, etc.
Jails will never be a primary focus of our project, but having even a basic Jail management system will definitely help us in a long run.
I don't plan on publishing any app based, or pre-packaged Jails. Instead I would focus on creating the cross-platform app deployment approaches within Jails, FreeBSD VMs or FreeBSD baremetal hosts using Ansible, shell scripts, installation tutorials, and so on. This way it can be useful to a broader community of admins and users out there, and will boost the FreeBSD exposure.

hoster jail start and hoster jail stop are mostly working now (just a couple of things left to do, like resolv.conf generation on jail start, check and create an empty fstab file if it doesn't exist, and generate an rc.conf file if it doesn't exist).
Moving on to implementing the hoster jail bootstrap -r 13.2-RELEASE functionality now.

hoster jail start is now fully working
hoster jail bootstrap has been implemented

hoster jail deploy is mostly ready, just need to implement the flags to pick different resources on creation: cpu limit, ram limit, network name, ip address, etc
hoster jail start-all has been implemented
hoster jail destroy has been implemented

Shortly will be moving on to hoster jail config-reset and hoster jail change-parent.


After aborting the  request next all request is also getting abort automatically.

@azure/abort-controller:
1.0.1:
windows 10:
[ ] nodejs

12.18.3:

[ ] Chrome

Hi, I have implemented an abort signal to cancel the upload video request, and it's working fine. that means the request is getting aborted when I call the abort() method but here the problem is when I make another request without calling abort() then also the request is getting canceled. I want to prevent this behavior. Please help me out. thanks in advance.
This is where I trigger abort() to cancel the request.
cancelUpload(data) {
    if (data && !this.abortSignal.aborted) {
      setTimeout(() => this.controller.abort(), 1000);
    }
  }

Here I implemented abort signal
uploadFile(blockBlobClient, file, abortSignal) {
  return new Observable((observer) => {
    blockBlobClient
      .uploadBrowserData(file, {
        onProgress: this.onProgress(observer),
        blobHTTPHeaders: {
          blobContentType: file.type,
        },
        abortSignal: abortSignal,
      })
      .then(
        this.onUploadComplete(observer, file, blockBlobClient)
      )
      .catch((err) => {

        if (err.name === 'AbortError') { // handle abort()
          alert("Aborted!");
        } else {
          throw err;
        }
      });
  }).pipe(distinctUntilChanged());
}

@himanshu849 are you sharing your controller instance among different requests?  My understanding is that once an abortcontroler triggered abort signal, it will remain aborted. If that's the case, you might want to create new abortcontroller instance for new requests.


Add clock-related functions to platform-services, conditionally implement them in WASI ABI

Implement clock functions (clock_getres() and clock_gettime()) for the standard platform service.
The SGX, Nitro and Trustzone platform services don't implement those functions yet and return result::Result::Unavailable. They will be implemented later on in a separate PR.
result::Result::Success has been changed to include the time in nanoseconds (u64).
TODO:

Link clock functions to policies: Disable them by default, unless specified otherwise
Rebase on top of @egrimley-arm 's work on clap (#212 and #216)
Fixing rebase issues
Return more appropriate error codes

@gbryant-arm can you mark this as WIP and convert it to a draft PR until the policy aspect is implemented?

Incidentally, @gbryant-arm, you need to be signing all of your commits now using GPG.  I have put instructions for how to do this in the public Veracruz Slack channel.

Or (probably) git commit --amend.

You've just introduced a use of default_value, which I carefully removed in other pull requests!
@egrimley-arm I noticed. As mentioned in the TODO I'll rebase once the next PR is merged

Rebased and ready for review

The commit log message in the first commit (5b6ade221d7df0dc408ca919ef17a6a4c777d341) doesn't conform to the standard format, but I don't understand how GitHub generates the final log message when you do "Squash and merge".

I can see one problem, I think: in several places, different kinds of error are not being distinguished. Perhaps they don't have to be distinguished, but there's also a comment in one place that claims that there will be two different error codes: Unavailable or UnknownError.
There are several ways the clock funtions could fail:

They are not implemented on a particular platform.
They have not been enabled.
The clock_id was invalid. (This is EINVAL on Linux.)
Some unexpected or unrecognised error code was returned from a lower level.

However, I would guess that it is best to return the same error code in cases 1 and 2, and for case 4 you could perhaps panic and die rather than return UnknownError: that could be a lot less painful for people to debug in future.
Anyone else have any thoughts on this?

I agree that we need to distinguish between EINVAL and ENOSYS for different failure modes of the clock.  If we ever come across an unexpected return code, or an internal invariant failed, then we can panic.  Note that I think that's the only legitimate use of panic!() and similar partial functions/macros in the runtime: as a rule, panics should only ever be used to signal a serious bug in our code and we should be hardened against potentially malicious code trying to induce panics by feeding bad data to the runtime.

I can see one problem, I think: in several places, different kinds of error are not being distinguished. Perhaps they don't have to be distinguished, but there's also a comment in one place that claims that there will be two different error codes: Unavailable or UnknownError.
There are several ways the clock funtions could fail:

They are not implemented on a particular platform.
They have not been enabled.
The clock_id was invalid. (This is EINVAL on Linux.)
Some unexpected or unrecognised error code was returned from a lower level.

However, I would guess that it is best to return the same error code in cases 1 and 2, and for case 4 you could perhaps panic and die rather than return UnknownError: that could be a lot less painful for people to debug in future.
Anyone else have any thoughts on this?

I agree that we need to distinguish between EINVAL and ENOSYS for different failure modes of the clock. If we ever come across an unexpected return code, or an internal invariant failed, then we can panic. Note that I think that's the only legitimate use of panic!() and similar partial functions/macros in the runtime: as a rule, panics should only ever be used to signal a serious bug in our code and we should be hardened against potentially malicious code trying to induce panics by feeding bad data to the runtime.

According to the POSIX doc, clock_gettime() and clock_getres() will only return two possible errors:

EFAULT if tp (timespec structure containing the time) points outside the accessible address space

unlikely to happen, as tp doesn't exist in the WASI API (the timespec is returned instead of being passed by reference); the only place where it could happen is in the nix implementation

EINVAL if the clk_id specified is not supported on this system

might never happen depending on the implementation; glibc for example selects a default clock when the clock id doesn't match any existing clock

We could simply return:

at the platform service level: result::Result::Success or result::Result::UnknownError
at the WASI level: ErrNo::Access (clock flag not set in the policy) or ErrNo::Inval (generic error)

Alternatively we could propagate errno (the one that the low-level function returns) back to WASI to avoid having to define hundreds of error codes at the platform service level (platform-services/src/result.rs)

+1+1 = +1 reached, merging.


Migrate to installing OCF components with the new OFC Helm chart

There's a helm chart for OFC now, the idea is to move this into use here.
this will also include #154
Expected Behaviour

use new OFC Helm chart
Current Behaviour

We are cloning and creating override files to set functionality

/assign: me


fluent-plugin-record-reformer not work with td-agent version 0.12.12

I try to use by following this article it work.  Docker logger. That base on docker application.
But after i try to use with latest version of 'td-agent' it not work plugin can see any tail input file.

path exist.
permission correct.
no error.

I use td-agent with user td-agent while docker need root access. that my fault. thank you :)


Service invocation via request header removes trailing slash

Hi,
this week we tried to implement a Non-Dapr endpoint via HTTP. Normally we use the dapr-app-id in the header instead of the /v1.0/invoke/{appId}/method/{methodName}, but ran into an issue with one of our endpoints. For this endpoint we need to have a trailing slash, which doesn't arrive at our server. Strangely enough, the dapr logs show the trailing slash. Calling the endpoint with the /v1.0/invoke/{appId}/method/{methodName}/ version works. So my guess is, that it has something to to with the dapr-app-id header version. (Maybe the log is not correct?)
In what area(s)?

/area runtime
What version of Dapr?

1.13.0

Expected Behavior

URL should be send to the endpoint as specified.
Actual Behavior

Trailing slash is missing.
Steps to Reproduce the Problem

Dapr Kubernetes Sidecar
Calling the HTTPEndpoint via /v1.0/invoke/{appId}/method/{methodName}/ (including trailing slash), the server returns 200.
Dapr Log
time="2024-04-10T13:47:41.873135982Z" level=info msg="HTTP API Called" app_id=xy code=200 duration=1159 instance=xy-6d5bb584b-s4trc method="GET /v1.0/invoke/appId/method/my-demo/route/2024-04-08T00:00:00.0000000/2024-04-08T23:59:59.9990000/" scope=dapr.runtime.http-info size=4994 type=log ver=1.13.0

Server Log
2024-04-10 13:47:41 <IP_ADDRESS> GET /my-demo/route/2024-04-08T00:00:00.0000000/2024-04-08T23:59:59.9990000/ - 443 - <IP_ADDRESS> Go-http-client/2.0 - 200 0 0 1065 400 6610 800d

Calling the HTTPEndpoint via /{methodName}/ and dapr-app-id header, the server returns 404 (as the trailing slash is missing)
Dapr Log
time="2024-04-10T13:50:03.933427538Z" level=info msg="HTTP API Called" app_id=xy code=404 duration=11 instance=xy-6d5bb584b-s4trc method="GET /my-demo/route/2024-04-08T00:00:00.0000000/2024-04-08T23:59:59.9990000/" scope=dapr.runtime.http-info size=5848 type=log ver=1.13.0

Server Log
2024-04-10 13:50:03 <IP_ADDRESS> GET /my-demo/route/2024-04-08T00:00:00.0000000/2024-04-08T23:59:59.9990000 - 443 - <IP_ADDRESS> Go-http-client/2.0 - 404 0 2 10 400 6610 800d

Release Note

RELEASE NOTE:

Interesting find, will look into this.

@yaron2 This may be because path.Clean will simplify the path.
https://github.com/dapr/dapr/blob/master/pkg/api/http/directmessaging.go#L300
In the comments it said:
// The returned path ends in a slash only if it is the root "/".

But I'm wondering should we change this behavior? since path.Clean may be standard solution, is trailing slash reasonable?


(#25) Add a Django sample app

Create sample celery task usage
Include compare celery vs aiotaskq sample code in tests
Add ref to sample code in README, add sample code README
Include populate_db step in the tests

Codecov Report
Attention: Patch coverage is 60.00000% with 20 lines in your changes missing coverage. Please review.

Project coverage is 97.61%. Comparing base (f02f6ce) to head (a52e2c0).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

src/aiotaskq/app.py
28.57%
15 Missing :warning:

src/aiotaskq/utils.py
70.58%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #68      +/-   ##
==========================================
- Coverage   99.21%   97.61%   -1.61%
==========================================
  Files          18       23       +5
  Lines         635     1047     +412
==========================================
+ Hits          630     1022     +392
- Misses          5       25      +20

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fixes to support multiple Apps per package

Closes: NaN
What's Changed

Fixed the following methods to use to use app_config.name instead of app_label + conditional logic.

nautobot.core.api.utils.get_serializer_for_model
nautobot.core.utils.lookup.get_route_for_model
nautobot.core.utils.lookup.get_related_class_for_model
nautobot.extras.plugins.tables.InstalledPluginsTable
nautobot.extras.plugins.views.InstalledPluginsView

TODO

[ ] Outline Remaining Work, Constraints from Design

@snaselj What else is there to be done to get it across the finish line?

This PR is currently taken over by @whitej6, there will probably be more fixes comming here. Or would you rather finish this one and add other fixes to separate PRs? @HanlinMiao

@HanlinMiao it is ready for review.


does not play .webm files

Hi
I just tested playing .webm files.
No joy.
I made the webm file with
Screencastify (Screen Video Recorder) 1.6.5

could you maybe attach the webm audio file here or share it with<EMAIL_ADDRESS>so that I could experiment with it? I'm having issues finding a webm audio only file :D for testing

Forget it, I've found the bug. Will push the fix soon.

Should be fixed now!


Calculate overall test suites time from actual run time

The current time is based on summing up the individual test suites, which would assume that the individual test suites are executed in sequence. Since Jest by default executes the tests in parallel (possibly with some caching) the overall test time is typically significantly shorter.
This PR changes the overall test suites time to reflect the total runtime based from reported start time until the test run is done instead (when the reporter is called).
I understand that this could be a breaking change for some, so an alternative solution could be to keep current behavior but enable this new behavior through an options flag (o vice versa). Not sure if that's necessary through, so I created the PR with this small change to get some initial feedback.
Thoughts?

@viddo so sorry for taking so long to respond - I've been in Stockholm this week for work. I LOVE IT!
I was so surprised by this PR and I completely agree. This is the correct way to go about it. I'll do a major bump as part of this since it could be a breaking change to some.
Thank you!

@viddo 4.0.0 is now published to NPM containing your contribution. Thank you again!! https://github.com/palmerj3/jest-junit/releases/tag/v4.0.0

Oh, no worries at all!  :)
Version bump sounds sensible too. 👍
Thanks! 🙇

@palmerj3 why bump the major version to 4.0.0 and not the patch/minor version, i.e. 3.8.0 or 3.7.1? There doesn't seem to be any breaking changes in this update so bumping the major version gives out the wrong signals of the severity of the new version. And if there is a breaking change, may I suggest that it would be documented in the release notes? Thank you, keep up the awesomeness :)

@bostrom yeah I probably shouldn't have gone to 4.x in this case. But versions are cheap and, while it won't break peoples systems, I thought it might come as quite a surprise to people when their test suites quadruple in speed :)

@palmerj3 fair point, but although versions are cheap, the time I spend on figuring out what has broken in a major update and what changes the upgrade requires is not cheap 😉

@bostrom take a look at the releases tab and let me know how I could have made it less confusing. I'm committed to doing that :)  I do try to do a decent job explaining the TL;DR of each release and, ideally, linking out to the PRs involved. https://github.com/palmerj3/jest-junit/releases

@palmerj3 overall an excellent job! The only thing I'd add is a BREAKING CHANGES subsection for each major release, since major releases make me expect some breaking changes. If there aren't any breaking changes (ideally that wouldn't even be a major upgrade), then an explicit mention of that would be 👍
Otherwise nothing to complain about. Keep it up 🙏


Set Host header has no effect

Do you want to request a feature or report a bug?
Bug
What did you do?
Set Host header using Headers middleware.
  middlewares:
    example-headers:
      headers:
        customRequestHeaders:
          Host: "example.com"

What did you expect to see?
Correct set Host in HTTP request object. Due to https://github.com/golang/go/issues/29865 Host field of http.Request should be set directly because of Request.Write ignore Host header:
{
  "Method": "GET",
  "URL": {
    "Scheme": "",
    "Opaque": "",
    "User": null,
    "Host": "",
    "Path": "/status",
    "RawPath": "",
    "ForceQuery": false,
    "RawQuery": "format=json",
    "Fragment": ""
  },
  "Proto": "HTTP/1.1",
  "ProtoMajor": 1,
  "ProtoMinor": 1,
  "Header": {
    "Accept": [
      "*/*"
    ],
    "Host": [
      "example.com"
    ],
    "User-Agent": [
      "curl/7.58.0"
    ],
    "X-Forwarded-Host": [
      "<IP_ADDRESS>:8080"
    ],
    "X-Forwarded-Port": [
      "8080"
    ],
    "X-Forwarded-Proto": [
      "http"
    ],
    "X-Forwarded-Server": [
      "lb.example.com"
    ],
    "X-Real-Ip": [
      "<IP_ADDRESS>"
    ]
  },
  "ContentLength": 0,
  "TransferEncoding": null,
  "Host": "example.com",
  "Form": null,
  "PostForm": null,
  "MultipartForm": null,
  "Trailer": null,
  "RemoteAddr": "<IP_ADDRESS>:13094",
  "RequestURI": "/status?format=json",
  "TLS": null
}

What did you see instead?
Host field of http.Request is not set correctly:
{
  "Method": "GET",
  "URL": {
    "Scheme": "",
    "Opaque": "",
    "User": null,
    "Host": "",
    "Path": "/status",
    "RawPath": "",
    "ForceQuery": false,
    "RawQuery": "format=json",
    "Fragment": ""
  },
  "Proto": "HTTP/1.1",
  "ProtoMajor": 1,
  "ProtoMinor": 1,
  "Header": {
    "Accept": [
      "*/*"
    ],
    "Host": [
      "example.com"
    ],
    "User-Agent": [
      "curl/7.58.0"
    ],
    "X-Forwarded-Host": [
      "<IP_ADDRESS>:8080"
    ],
    "X-Forwarded-Port": [
      "8080"
    ],
    "X-Forwarded-Proto": [
      "http"
    ],
    "X-Forwarded-Server": [
      "lb.example.com"
    ],
    "X-Real-Ip": [
      "<IP_ADDRESS>"
    ]
  },
  "ContentLength": 0,
  "TransferEncoding": null,
  "Host": "<IP_ADDRESS>:8080",
  "Form": null,
  "PostForm": null,
  "MultipartForm": null,
  "Trailer": null,
  "RemoteAddr": "<IP_ADDRESS>:13094",
  "RequestURI": "/status?format=json",
  "TLS": null
}

Output of traefik version:
$ docker run -ti traefik:v2.2.0-rc2 version
Version:      2.2.0-rc2
Codename:     chevrotin
Go version:   go1.14
Built:        2020-03-11T17:42:16Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
traefik.yaml:
---
entryPoints:
  http:
    address: '<IP_ADDRESS>:8080'
  metrics:
    address: '<IP_ADDRESS>:9000'
metrics:
  prometheus:
    entryPoint: metrics
log:
  level: DEBUG
accessLog: {}
providers:
  file:
    watch: true
    filename: "/etc/traefik/example-lb.yml"
    debugLogGeneratedTemplate: true

example-lb.yml:
---
http:
  routers:
    example:
      entryPoints:
      - http
      middlewares:
      - example-headers
      - error-ratio-cb
      service: example
      rule: "PathPrefix(`/`)"

  middlewares:
    example-headers:
      headers:
        customRequestHeaders:
          Host: "example.com"
    error-ratio-cb:
      circuitBreaker:
        expression: 'ResponseCodeRatio(500, 600, 0, 600) > 0.10'

  services:
    example:
      loadBalancer:
        passHostHeader: true
        servers:
        - url: "https://origin.example.com"

duplicate of #5966, #6000,

@ldez do you have any plans to fix it? It is quite crucial for our use case and I can help you with PR. The only question here is the where is the best place to modify http.Request.Host field, in middleware itself or in proxy package. Or maybe there is another place to do that, what do you think?

do you have a concrete use case ?

We also need to pass Host with specific value. That is set of dynamically spawning servers with bunch of virtual hosts on them and we need to separate requests using virtual hosts. In the future we plan to get rid of that approach but for now traefik here is the best option for load balancer because it provides great observability and performance so we decided to move to traefik as load balancer in front of our fleet and then make any changes with better understanding how it is affect our platform. Also, AWS API Gateway requires that: https://stackoverflow.com/questions/39591495/nginx-proxy-pass-to-aws-api-gateway

Have to try to set passHostHeader to false (the default value is true)
https://docs.traefik.io/v2.1/routing/services/#pass-host-header

I've tried, has no effect unfortunatelly. I did some quick hack and looks like it works:
diff --git a/pkg/middlewares/headers/headers.go b/pkg/middlewares/headers/headers.go
index 4868c8cf..38663ea9 100644
--- a/pkg/middlewares/headers/headers.go
+++ b/pkg/middlewares/headers/headers.go
@@ -169,6 +169,9 @@ func (s *Header) modifyCustomRequestHeaders(req *http.Request) {
                        req.Header.Del(header)
                } else {
                        req.Header.Set(header, value)
+                       if header == "Host" {
+                               req.Host = value
+                       }
                }
        }
 }

thank you very much guys!

Closed by #6502.


fix: networkinterfaces belong system resource

这个 PR 实现什么功能/修复什么问题:
是否需要 backport 到之前的 release 分支:

release/2.11

/area region
/cc @swordqiu @yousong

Codecov Report

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

@@          Coverage Diff           @@
##           master   #2747   +/-   ##
======================================
  Coverage    7.23%   7.23%
======================================
  Files         472     472
  Lines       74451   74451
======================================
  Hits         5384    5384
  Misses      68615   68615
  Partials      452     452

Flag
Coverage Δ

#aFlag
7.23% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/policy/resources.go
0% <ø> (ø)
: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 225ee29...bcd9622. Read the comment docs.

/lgtm

/approve


Fix #222 - Non linear start-up time for large folders

Closing to remove unnecessary commit from it.


⚠ Thumbnails API Endpoint has degraded performance

In 6196c3f, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 4881 ms

Resolved: Thumbnails API Endpoint performance has improved in 9fd4868 after 2 minutes.


VS 2017 remote debugging tools link broken

It redirects to a page that says "Sorry, we couldn't find any downloads for you."  The VS 2019 remote debugging tools download link works fine.  This might affect other links - I didn't check them.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4a2fd746-82f7-1bac-9932-27c14cdfe0ca
Version Independent ID: 46b43a94-b750-2073-5e28-82183af092a9
Content: Remote Debug a C# or VB project - Visual Studio
Content Source: docs/debugger/remote-debugging-csharp.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@jordanmills Hi Jordan, which link did you have trouble with ? VS 2017? The links all work for me. For VS 2017 and VS 2015 (my.visualstudio.com links), you have to either sign in or be signed in already. What browser are you using?

I missed that message (I see the email now).  I think it was VS 2017 and 2014(?).  Yes the links want me to sign in, that was the problem.

I don't believe you need to sign in for the VS 2019, but you do for VS 2017/2015, because those links are on my.visualstudio.com, which was a business decision.


Failed to build latest version of pocketnet core node, because of incomplete CNode class.

In file included from pocketcoind.cpp:13:
In file included from ./init.h:14:
In file included from ./statistic.hpp:18:
./net.h:227:75: error: member access into incomplete type 'CNode'
virtual bool SendMessages(CNode* pnode) EXCLUSIVE_LOCKS_REQUIRED(pnode->cs_sendProcessing) = 0;
^
./net.h:47:7: note: forward declaration of 'CNode'
class CNode;
^

Pocketcoin core node build/compilation process is affected when used clang/++ not gcc/++.

Pocketcoin core node build/compilation process is affected when used clang/++ not gcc/++.

Could you create a docker image to reproduce the problem?


request new showcase for passkit.com

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

@JWLangford Thanks for the suggestion.


Add support for LMAX Disruptor 4.x

This PR is based on #1937 and adds support for LMAX Disruptor 4.x by:

splitting our EventHandler classes into two versions: one for 3.x and 4.x,
using the original TimeoutBlockingWaitStrategy,
adding an additional Maven Surefire run to test our async logger implementation with Disruptor 4.x.

Closes #1829

Hi @ppkarwasz, thank you for fixing this but I can't see the new version in the released notes?
https://logging.apache.org/log4j/2.x/release-notes.html
Or we should wait for the next 3.X version?

@Alanoudj, this will be made available in 2.23.0.
Log4j 3 will use Disruptor 4, there Disruptor 3 is completely removed.

Do you have any deadline for 2.23.0 version release?

@Alanoudj,
The log4j-api version 2.23.0 artifact will be used by both Log4j Core 2.23.0 and Log4j Core 3.0.0-beta2, so the ETA for 2.23.0 is around end of February.


Report on "missed opportunity" for cost savings due to resources not having a schedule attached

vs some particular schedule, eg Melbourne Business Hours (eg: 0800-1800)

Can use AWS Price List Query API to get the list price for resources.  But many things to consider if attempting to be accurate (contracted prices, reserved/spot instances, etc)


Attempt at fixing image size + minor fixes to text

Codecov Report

Merging #221 (f4a7aa5) into master (9ca691c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #221   +/-   ##
=========================================
  Coverage     44.72%   44.72%
  Complexity      683      683
=========================================
  Files           175      175
  Lines          3557     3557
  Branches        409      409
=========================================
  Hits           1591     1591
  Misses         1863     1863
  Partials        103      103

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 9ca691c...f4a7aa5. Read the comment docs.


Fixed tensor type issue in affinetransform and warp

Refer to #187.
Previously the following code would've given an error:
require 'torch'
require 'init'
torch.setdefaulttensortype('torch.FloatTensor')

local im = image.lena()
local matrix = torch.Tensor({{1,0.5},{0,1}}):double()
local im2 = image.affinetransform(im,matrix,'bilinear')

local fld = torch.zeros(2, 512, 512):double()
local im2 = image.warp(im,fld,'bilinear')

This seems to be because src.image.warp expects field to be of default tensor type. This issue is fixed by coercing passed matrix or field to default tensor type.

Thanks!

If the default tensor type is double, but the image is a float, this PR will make it fail.
/Users/tzaman/torch/install/bin/luajit: /Users/tzaman/torch/install/share/lua/5.1/image/init.lua:966: bad argument #3 to 'warp' (torch.FloatTensor expected, got torch.DoubleTensor)
Reproduce:
require 'torch'
require 'image'
torch.setdefaulttensortype('torch.DoubleTensor')
pr = image.lena():float()
makes_me = torch.zeros(2, 512, 512):double()
sad = image.warp(pr,makes_me,'bilinear')

Hi @TimZaman ,
I think you are mistaken. This PR didn't modify anything related to wrap. It modified affinetransform. In fact it fixed the exact bug you've faced with warp except for affinetransform.

@chsasank , how about line 955?
local field = field:typeAs(torch.Tensor()) -- coerce matrix to default tensor type
Should have been
local field = field:typeAs(src) -- coerce matrix to src tensor type

Do you agree that the above lua snippet a few comments back does not
currently work, and that this PR changes code (one line L955) for warp as
well?
On Tuesday, 4 October 2016, Sasank Chilamkurthy<EMAIL_ADDRESS>wrote:

That doesn't seem to work if src is not default tensor type.
This seems to be because src.image.warp expects field to be of default
tensor type.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/torch/image/pull/189#issuecomment-251357125, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHXSRESpyDgxzwprV_8xd9fKZsyViwPfks5qwjDKgaJpZM4J7wfR
.

Yeah, that does seem to be the case. The PR seems to be a bad attempt to fix bug #187 . I'm still figuring out where exactly the error is raised. I'd appreciate any help.
One problem with local field = field:typeAs(src) is that src can be a CharTensor. That'll round field to nearest integer and therefore producing unexpected results.

It makes sense to introduce some code testing, also with the affineTransform. The warp function's argument-3 (field) has to be the same as the image's.
I will suggest a PR to fix this. If you want to use a byte or char-tensor, you can manually char:float():warp():char() it back to its original state. This wasn't possible before this PR either, and has never seemed to raise any issues.
I'll make a new PR and add a minor test too so that we know what we're going in the right direction.

The warp function's argument-3 (field) has to be the same as the image's.

It'd be nice if you can point where this check is enforced. I have gone through generic/image.c but couldn't find it.


Use it for binary classification

Dear Authors,
Kindly let me know how to make use of the SWINT architecture for custom two class problem.
I wish to adopt it for my 2 class image problem.
Regards,
sk

Swin Transformer could be used as the backbone architecture for this 2 class classification problem.


Can not reproduce the reported results.

I load "net_last.pth" for VQ-VAE and "net_best_fid.pth" for the Transformer in 'VQTransformer_corruption05', and run the GPT_eval_multi.py code, and I can only achieve about 0.22 FID, which is higher than the reported 0.116. Can you reproduce the results with the provided weights?

I encountered similar problem. I used VQ_eval.py to evaluate the 'net_best_fid.pth' provided by the author and found that the FID was 0.278, not 0.070 as in the paper.

I encountered an issue during HumanML3d data conversion, may I ask how you resolved it?

I load "net_last.pth" for VQ-VAE and "net_best_fid.pth" for the Transformer in 'VQTransformer_corruption05', and run the GPT_eval_multi.py code, and I can only achieve about 0.22 FID, which is higher than the reported 0.116. Can you reproduce the results with the provided weights?

Can't reproduce the reported metric and got 0.22 FID too TAT. Wondering what's wrong with my testing command. Plz lmk if you have solved this problem. Desperate for help.


Move Propagated Workspaces to list of beta features

Prior to this, Propagated Workspaces was left under the list of alpha features
even though it was promoted to beta in PR https://github.com/tektoncd/pipeline/pull/6030. This PR moves it to
the list of beta features in the documentation.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind documentation

/test check-pr-has-kind-label

/lgtm


TODOs after 1.2.3 is released

High priority:

assign the byte-values to the new ACSP protocols, starting with ACSP_SESSION_INFO
compare the de/serialization of
MsgVersionInfo
MsgChat
MsgClientLoaded
RequestSessionInfo
MsgError

Low priority:

implement RequestSetSession
check for the existance of the ACSP_KICK_USER
implement PluginManager-methods for the new requests

Layer should now at least not fail when working with a 1.2.3 server.
TODOs left:
implement PluginManager-methods for the new requests

Left:

Handle Version + Errors
The MsgSessionInfo->RequestSetSession is doing strange things with the WaitTime, let's see what the Lord answeres. Currently you should set the WaitTime manually, maybe we just have to convert miliseconds to seconds.

Just want to let you know: I updated the example code with current examples. I like to see the diffs when a new version arrives.

ty neys, forgot about that.
I think we're cool with 1.2.3


QUESTION : SELL and BUY swapped?

Did the logic changed and the comments are old or am I missing something?

I guess it is because you changed from SPOT to MARGIN, any specific reason to that?

It was meant to work as a margin sell but what’s not possible due to several factors, so I will have to revert back to SPOT but in this branch.
If you want to find out how the sell strategy works see it explained here: https://youtu.be/qqXQgwuFI8s
Also, the sell logic how now been moved to its own branch so make sure to check that one out.

Okay so basically it should be worth reverting back to the previous code - SPOT - for buying and sell right?
Because even in the new branch you shared the order is still margin


phoenix.Matrix; Typo in up function

Method up reports wrong data. There is a typo in the source code - wrong matrix component returned:
    public inline function up() {
        return new Vector( elements[4], elements[5], elements[10] );
    } //up

Z coordinate sould be elements[6] instead of elements[10].

Well spotted, the new maths classes in embers have unit tests to validate silly things like this.
Thanks!


Send Variables in Annotations query

Adding variables to be send with annotations query

LGTM though I didn't test it!

Pushing this to production soon


lib/types: add intFlag

Follow up to #1753, which fixed how we document global-prefix settings options themselves, this PR fixes the respective sub-options.
Value must be 0 or 1. Boolean definitions are coerced using if v then 1 else 0, however when this is done a deprecation warning is printed.
Fixes #1741.
Plugins with known issues

[x] airline
[x] committia
[x] direnv
[x] goyo
[x] lazygit
[x] ledger
[x] markdown-preview
[x] sandwich (not sure; no_default_key_mappings is documented as int, but the implementation checks for definitions)
[x] sleuth
[x] tmux-navigator
[x] typst-vim
[x] vim-slime (not sure about slime_bracketed_paste. Other seem to be ints)
[x] zig

Other globalPrefix plugins:

[x] autosource has a mkBoolInt that could use this type
[ ] codeium-vim
note: there's also a nvim version
note: uses v:true and v:false values
[ ] copilot-vim (seems ok?)
[x] emmet (no bool opts)
[x] godot (no bool opts)
[x] improved-search (no settings)
[x] instant (only_cwd undocumented, but bool seems correct)
[x] julia-cell
[x] magma-nvim (repo archived, bool seems correct)
[x] molten (bool seems correct)
[ ] parinfer-rust (can't find force_balance upstream ?!)
[x] startify (no bool opts)
[x] tagbar (no bools)
[x] texpresso (no bools)
[x] undotree (no bools)
[x] vimtex (no bools)

colorschemes

[x] everforest has a mkEverforestBool that could use this type
[ ] nord - a lua plugin (with setup) but it's using mkVimPlugin with a globalPrefix!?
[x] one colorscheme

@nix-community/nixvim could someone give this a preliminary review before I start work fixing each affected plugin module?

All known issues of plugins using mkBool for 0 or 1 type options should now be fixed. Ready for review.
It's possible I missed some, as it was a very manual process to identify with each plugin's docs what type of value their toggle configs expect. If so this can be addressed on an ad-hoc bases in future PRs.

@mergifyio queue


ArrayField - Don't sort unless a sort by field is provided

Avoids default sorting by the 'uuid' so that the default is unsorted.  i.e. config order

Which problem are you trying to solve? config order itself isn't safe / guaranteed either.

When adding to a list of whatever, you never know the position in the list where to find it due to sorting by the uuid.  The uuid's do not appear to be chronological.  Especially when combining config from another system.
So the default 'uuid' sorting seems kind of random.  From a human perspective doesn't seem useful.  Leaving it unsorted if no sort field is provided seems a little more deterministic from a chronological perspective.  Seems more useful to me.
Why isn't config order safe?  It's the same data, just not sorted.
As far as guaranteed.  Well 'uuid' order seem kind of random too anyway.
From: Ad Schellevis<EMAIL_ADDRESS>Sent: Monday, April 27, 2020 11:59 PM
To: opnsense/core<EMAIL_ADDRESS>Cc: NOYB<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [opnsense/core] ArrayField - Don't sort unless a sort by field is provided (#4072)
Which problem are you trying to solve? config order itself isn't safe / guaranteed either.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/opnsense/core/pull/4072#issuecomment-620419340 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPCZMNFSBBQCO7UQDNEJMTROZ5EJANCNFSM4MSQLLPA .  https://github.com/notifications/beacon/AAPCZMMVMQJOMZN4JNJ6RPLROZ5EJA5CNFSM4MSQLLPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOET5NSDA.gif

it's is "random" in some sense, just as the ordering in the file would be, hence it doesn't really seem to make sense to change it. We really discourage using config ordering.

Uuid sort doesn't seem to provide any human usefulness.  While unsorted may not be a huge benefit, or guaranteed to strictly follow the config order. It does seem to at least to some degree.  Which seem to tend toward chronological.  Which is somewhat humanly useful.
Though the upside may not be huge, I'm not seeing any downside.  Net positive.
Would appreciate if the project could accommodate this.
Thanks for your consideration.

I'll take a look, I don't mind not sorting (and save cpu cycles), just want to make sure no one assumes anything by the "natural" order of things.

Thanks for taking a second look at this.
I recall seeing only one core feature that doesn't currently provide a sort by field.  Traffic Shaper in 2 of it's 3 searchBase calls.
Don't know about the plugins.  Other than my own.


app: add restrictions to search node

prevent adding children
if you have a regular node below a search node and use the keyboard shortcut to move the node up into a search node's results, the regular node is added to the search node, but it isn't visible. we should prevent users from adding any kind of children nodes to a search node.
prevent deleting search node children
users should be able to rearrange search node results, but they shouldn't be able to delete the results (children).

We might want to have a way to flag nodes as "read-only" but for now we can probably assume if they implement the objectChildren hook the children are "managed" so we would:

Not allow children to be deleted at the command level (or since they are references, ask if they want to delete the referenced node)
Make sure move commands skip these nodes
Prevent newline inserts (return key at end of node text)
Prevent/skip node when indenting
Prevent inserts relative to any of the children
No create references (since effectively performs an insert)

Moving children "out" seems like it could be useful in some cases, but not really with search. However, it doesn't seem like its necessary to prevent it yet.
Allowing user to re-arrange result nodes means persisting them. Right now they are created as temporary orphan nodes. If we instead create them as actual children to the search node (and perform a merge on subsequent searches), move operations should work and be persisted.


Clear all virtual titles before setting new ones

Otherwise, if buffer is re-read for whatever reason, new set of duplicated titles is displayed. The easiest way to trigger this is to do a :e in a zettel.

@oberblastmeister I have a feeling that was the intent all along? I might be missing something though

@oberblastmeister any chance you can take a look shortly? It is one line but should be a good "quality of life" improvement for everybody using the plugin.


Simplify cd to the executing script directory

Nitpicking - let us drop redundant cd "$(pwd)"

Any idea why this was there?

Any idea why this was there? My bash foo is poor.

Looks like it was inspired by https://stackoverflow.com/q/39340169   :-)
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

That snippet needs pwd to output the absolute path for the DIR variable.
We don't really need the absolute path, we want to change to the script's directory,
which is already done with cd "$(dirname ...)")


Fix PHP arrows in generated documentation.

Some example code in the generated docs contains the PHP arrow (=>), which is HTML-encoded and thus corrupted in code snippets.
This fixes the generation for these instances.

👍


Sky Kingdom

Description
Task: Sky Kigdom.
Feature: Feature which this tasks contributes to implementing
This task involves the design and generation of the Sky Kingdom's map section. The Sky Kingdom will feature floating islands, cloud-based terrains, and aerial structures. The primary focus of this task is to create a seamless and visually distinct map for the Sky Kingdom, using unique sky-themed tiles and textures. The map will include floating landmasses, pathways between islands, and large empty areas to simulate the vastness of the sky. Future gameplay may add vertical traversal mechanics and aerial landmarks for players to explore.
Example

Sky Biome Generation: The map will consist of various floating islands with sky-themed textures and environmental details like cloud paths.
Floating Landmarks::  Key landmarks such as floating temples and cloud bridges will be designed for future interaction.

Dependencies
List any tasks on which this ticket relies. If there is already an existing ticket, reference it using #xx. If a task needs to be implemented, and the issue does not already exist, make a new ticket and leave it unassigned for someone else to take on. Ensure other team members are aware of the issue.

[x] Procedural generation for floating islands and cloud paths (#176 ).
[x] Sky kingdom map textures

Milestones
List of steps that need to be completed for this task.

[x] Step 1: Initial design of Sky Kingdom islands and pathways (Sept. 18).
[x] Step 2: Implement sky-themed tiles and textures (Sept. 20).
[ ] Step 3: Generate floating islands and map layout (Sept. 22).
[x] Step 4: Sky tiles with items designed (Sept. 24).
Completion Deadline: Sept. 29

Documentation

Main description of feature
User documentation
...

Members

@chloemicah
@praneetdhoolia
@JonnaHerman
@Howard-12
@BenGhahramaniUQ
@Dabbyyyy

Step 3 is not included in our design. We ultimately decided not to do step 3


Adding Kahn's Algorithm

I want to add Kahn's Algorithm in Graphs Folder
please assign me this issue:

@tom635 Assigned.
Go ahead 👍

Sir please assign this issue to me
Why you should assign this to me?
i am current rated 5 star at codechef with rating of 2153 and rated expert at codeforces with rating of 1776
https://codeforces.com/profile/navjotdadwal
https://www.codechef.com/users/navjot1234
So i can handle and solve this issue

Sir please assign me this issue i know how kahn's algorithm

@siddharth25pandey ,I can add a very well-explained code for this question, please assign it to me under hacktoberfest label.


How can I get traffic size in scripting API

How can I get traffic size in scripting API?

Please use the mitmproxy forums (https://discourse.mitmproxy.org/) for support/how-to questions. Thanks!


Bump caching of versioned artifacts to a week

Following the cache control configuration suggestion from:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#caching_static_assets
fixes: https://github.com/dart-lang/dart-pad/issues/1608

TBR: @devoncarew
Landing this PR to include it in the artifacts publish for Flutter 2.2.2 / Dart 2.13.3


linux/arm64 Image Published to Dockerhub

Is your feature request related to a problem? Please describe
linux/arm64 can be built but today it is not published on dockerhub.
Describe the solution you'd like
linux/arm64 to exist on Dockerhub.
Describe alternatives you've considered
Building my own linux/arm64 image and publishing it.
Additional context
No response

Hi @Conklin-Spencer-bah,
The docker images published on dockerhub contain both the architectures. The image automatically detects the underlying architecture and pulls the right layer accoordingly.
See https://hub.docker.com/r/opensearchproject/opensearch/tags

Closing this issue. Please re-open if you still have questions.
Thanks!


No error notification when bodyFile refers to missing file

WireMock: 2.32.0
WireMockConfig: new WireMockServer(new WireMockConfiguration().port(4646).notifier(notifier))
Failing test case: https://github.com/fvclaus/wiremock-invalid-bodyfile/blob/master/src/test/java/fvclaus/AppTest.java
I expected to receive an error notification, when an exception is thrown on the WireMock Server. I have also provided an executable Testcase in the repository linked above. It can be executed with mvn test.
We had a test in our project that was failing, because of this issue. With no output, I had to debug the test and sent a request to the WireMock instance to see the output. This took a while, because I had never seen a 500 returned from WireMock unintentionally before and was therefore not the first thing I checked.

Similar to #1407


File missing

In the folder NCSX_test_data, the file NCSX_coil_coeffs.dat referred to by tests/geo/surface_test_helpers.py is missing. I am wondering how the tests are passing such as those in tests/geo/test_boozersurface.py

Never mind. I noticed its moved to a different location.


Ability to store login details for SSH/telnet connections

Description of the new feature/enhancement
As much as I love the new Windows Terminal and all the fancy features that it offers, not being able to store the login details for my SSH or Telnet connections is kind of a deal-breaker for me.
As a Network guy, I roughly have 200+ devices that I connect to over SSH or Telnet, and some of them I access multiple times in a day so, having the ability to store the login details securely is crucial.
I have also tried setting up the SSH keys for authentication but, it becomes overwhelming very quickly as there are always new devices getting added. Sometimes, the device on the other end is not capable of storing SSH keys.
So, adding the ability to store username and password will make Windows Terminal a suitable replacement for something like M-Remote or Secure CRT.

Proposed technical implementation details (optional)

As much I love the SSH features in SecureCRT, XShells, etc, I wouldn't really ask for similar features in Windows Terminal, since Terminal is not a professional SSH client.
See https://github.com/microsoft/terminal/issues/9486#issuecomment-798965251

Yea, the party line is that the Terminal is a great terminal emulator. That's what we're trying to be first and foremost - not a ssh client. This is a really good idea for someone to write an extension in the future (when those are supported), but it's not something we'll be adding ourselves. Thanks!


Prettier and Live Server

Type: Bug
I had Prettier and Live Server downloaded as an extension but opened a new VS code window and it was not downloaded on there. When I tried to download them again, it said error whle installing "Prettier- Code Formatter" extension.. Please check the log for more details
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10700T CPU @ 2.00GHz (16 x 1992)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.83GB (7.63GB free)

Process Argv
--crash-reporter-id 9960bae2-90b5-4394-8bc0-7e1a5d2156ed

Screen Reader
no

VM
44%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30880073
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialog:30887143
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
synctok:30869157
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixtcf:30871695
pythonregdiag2:30871582
pyreplss2:30886141
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016cf:30886111
dsvsc017cf:30886113
dsvsc018:30886114
aa_t_chat:30882232

\duplicate https://github.com/microsoft/vscode/issues/198605
\unassign
\close

\close-as-not-planned

Sorry what is this for? Do I paste that in terminal?Sent from my iPhoneOn Nov 18, 2023, at 5:58 PM, goyalyashpal @.***> wrote:
\close-as-not-planned
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Sorry what is this for?

u have posted the same issue twice. didn't you read "duplicate #198605" ??

I didn’t mean to post twice. New to this so trying to figure it outSent from my iPhoneOn Nov 18, 2023, at 6:21 PM, goyalyashpal @.***> wrote:
Sorry what is this for?
u have posted the same issue twice. didn't you read "duplicate #198605" ??
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

/duplicate https://github.com/microsoft/vscode/issues/198605

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Regenerate .classpath files for .login and .login.tests

com.google.cloud.tools.eclipse.appengine.login.tests is pulling in two jars from .login, google-api-client-1.22.0.jar and google-oauth-client-1.22.0.jar, relating to OAuth.  GoogleLoginServiceTest.java is referencing com.google.api.client.auth.oauth2.Credential, whose definition references classes in google-http-client-1.22.0.jar:
public class com.google.api.client.auth.oauth2.Credential implements
    com.google.api.client.http.HttpExecuteInterceptor,
    com.google.api.client.http.HttpRequestInitializer,
    com.google.api.client.http.HttpUnsuccessfulResponseHandler {

Because this jar is not in .login.test's classpath, GoogleLoginServiceTest is generated with errors.
I used PDE's Regenerate Classpath and all is now well.

Tycho doesn't have a problem as it uses the OSGi metadata to resolve dependencies and .login.test is a fragment of .login and so shares its classpath, and .login's classpath has all 5 libraries.

After all, I guess all the five jars need to be exported? That makes sense. LGTM

PDE is responsible for taking the OSGi metadata and setting up JDT classpaths.

:rocket:


Can't press enter with exact name if there are still multiple options

Browser
Opera Gx
Description
In cases like these, it feels frustrating to not be able to press Enter even if the whole country is typed out. When the user presses enter, there is a check to make sure there is only one option. I would add a OR condition to that so that even if there is multiple options still, if one of them is exactly what the user typed, select that one.

Anything else?
No response

Happens with a few others as well like Dominica, Mali and Guinea


Support for cursors

This is needed to iterate over a large result set without preloading the entire set into memory. ResultSet.iterator could be made to work (maybe BidirectionalIterator could also be useful), but it currently isn't implemented like a database cursor.

I think BidirectionalIterator wouldn't really work without caching in memory, so if you care about not consuming more memory than necessary I'd just expose it as an Iterator probably.

I've added an PreparedStatement.selectCursor that steps through rows one by one in 8f1cdb3d4d5dd2acaeb7b568b726f336e8a68fbf.
You would use it like this:
final stmt = db.prepare('SELECT foo FROM bar');
final cursor = stmt.selectCursor();

while (cursor.moveNext()) {
  // use row with cursor.current
}

I opted to create a new method only returning an Iterator because Iterable typically implies that you can iterate over them multiple times. That's not really the case for an prepared statement, so it doesn't feel like the right interface to expose here.
Let me know if that sounds like it would work for you, I'll release it to pub then.

Thanks for the super fast response! I will try it out today.
In terms of the API, I will leave that to you. Although it seems to me that if  selectCursor() is the iterator, then PreparedStatement is the iterable (but only if you had a specialised PreparedSelectStatement). i.e. because the semantics of Iterable is that each time you iterate over it, it invokes iterator afresh.

Just tested it and it's working perfectly :+1:

Although it seems to me that if  selectCursor() is the iterator, then PreparedStatement is the iterable (but only if you had a specialised PreparedSelectStatement)

That's a good point. I had considered something like this, but in the end we'd have to prevent multiple iterators interleaving, so it will always be kind of a weird Iterable.
I've released the iterator in 1.2.0, we can always come up with a more fancy API later :)


increment dbaas-operator module to 0.1.5

Signed-off-by: Tommy Hughes<EMAIL_ADDRESS>

@wilybrace ready for review, thanks!


Fine tuning

How to fine tune your model?
I don't have sufficient data to retrain your model from scratch.
I want to fine tune your model on my data which has only two classes ?

Assuming you have:

your data in the correct format
you have generated your bounding box priors
you have created a config file for training
you have downloaded the pretrained inception-resnet-v3 checkpoint file

then the following will train only the detection head layers (the inception-resnet-v3 variables will remain fixed):
$ python train.py \
--tfrecords /home/ubuntu/Data/Datasets/COCO/tfrecords/train56945/* \
--priors /home/ubuntu/Data/experiments/detection/large_model_0/priors_7_nonrestricted.pkl \
--logdir /home/ubuntu/Data/experiments/detection/large_model_0/logdir \
--config /home/ubuntu/Data/experiments/detection/large_model_0/config_train.yaml \
--pretrained_model /home/ubuntu/Data/Models/Inception/inception_resnet_v2_2016_08_30.ckpt \
--fine_tune

To squeeze more performance out of the detector, you might need to train all of the weights after fine-tuning for a while.


How to provide mean & stddev to dali.fn.normalize

Hi all, I am super new to Dali Backend, but the benchmark I recently ran are incredible. I am trying to preprocess the data with Dali backend, but struggle with the "normalize" operation. I would like to specify a "per channel" mean & stddev ([c1, c2, c3] for example), but keep getting errors.
Here is what I've tried so far:
...
mean=[0.485, 0.456, 0.406],
stddev=[0.229, 0.224, 0.225]
...

...
mean=(0.485, 0.456, 0.406),
stddev=(0.229, 0.224, 0.225)
...

...
mean=dali.types.Constant([0.485, 0.456, 0.406]),
stddev=dali.types.Constant([0.229, 0.224, 0.225])
...

Here is the full code of my pipeline:
import nvidia.dali as dali
from nvidia.dali.plugin.triton import autoserialize

@autoserialize
@dali.pipeline_def(batch_size=8, num_threads=8, device_id=0)
def pipe():

    # Getting the images.
    images = dali.fn.external_source(device="gpu", name="input_0")

    # Resizing.
    images = dali.fn.resize(images, resize_x=224, resize_y=224)

    # Permutting NHWC to NCHW.
    images = dali.fn.transpose(images, perm=[2, 0, 1])

    # Rescaling 0-255 to 0-1.
    images = images / 255.

    # Normalizing (images - mean) / std.
    images = dali.fn.normalize(
        images,
        batch=False,
        mean=dali.types.Constant([0.485, 0.456, 0.406]),
        stddev=dali.types.Constant([0.229, 0.224, 0.225])
    )

    return images

Many thanks !!

Hello @Vincouux ,
Thank you for reaching out.
First thing I see is that you don't need to wrap the mean and stddev in the types.Constant:
    # Normalizing (images - mean) / std.
    images = dali.fn.normalize(
        images,
        batch=False,
        mean=[0.485, 0.456, 0.406],
        stddev=[0.229, 0.224, 0.225]
    )

If this doesn't help, could you please post the error message, so I'd know more what's going on?

Here is the error I am facing:
Traceback (most recent call last):
  File "<string>", line 5, in <module>
  File "<frozen importlib._bootstrap>", line 553, in module_from_spec
AttributeError: 'NoneType' object has no attribute 'loader'
Traceback (most recent call last):
  File "<string>", line 8, in <module>
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/_utils/autoserialize.py", line 72, in invoke_autoserialize
    dali_pipeline().serialize(filename=filename)
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/pipeline.py", line 1471, in create_pipeline
    pipe_outputs = func(*args, **fn_kwargs)
  File "/models/polyp_detection_exp114_20220523_preprocessing/1/dali.py", line 21, in pipe
    images = dali.fn.normalize(
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/fn.py", line 88, in fn_wrapper
    return op_wrapper(*inputs, **kwargs)
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/fn.py", line 80, in op_wrapper
    return op_class(**init_args)(*inputs, **call_args)
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/ops.py", line 621, in __init__
    _add_spec_args(self._schema, self._spec, kwargs)
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/ops.py", line 398, in _add_spec_args
    converted_value = _type_convert_value(dtype, value)
  File "/opt/tritonserver/backends/dali/conda/envs/dalienv/lib/python3.8/site-packages/nvidia/dali/types.py", line 110, in _type_convert_value
    return _known_types[dtype][1](val)
TypeError: float() argument must be a string or a number, not 'list'

To give a bit more context, the input image is of shape [-1, -1, 3]. After the resize and the permutation, it should be [3, 224, 224] based on the above pipeline I provided.
Many thanks @szalpal for you help !!!

@Vincouux
Generally, for image normalization it'd be better if you'd go for fn.crop_mirror_normalize instead of fn.normalize. For two reasons, one is that the former fuses 3 possible operations in one and the second is that the API would be more user friendly.
Therefore I'd advice you to use this instead of fn.normalize:
    images = dali.fn.crop_mirror_normalize(images,
                                           dtype=types.FLOAT,
                                           output_layout="CHW",
                                           crop=(224, 224),
                                           mean=[0.485, 0.456, 0.406],
                                           std=[0.229, 0.224, 0.225])

Should you have any more problems, don't hesitate to reach us out. Good luck in using DALI ;)

Furthermore, if you'd like to squeeze even more perf from this snippet, I'd suggest, that you plug the Rescaling 0-255 to 0-1. into the normalization by multiplying your normalization parameters by 255:
                                           mean=[0.485 * 255, 0.456 * 255, 0.406 * 255],
                                           std=[0.229 * 255, 0.224 * 255, 0.225 * 255])


ja: Make docs/concepts/services-networking/ingress.md follow v1.19 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/services-networking/ingress.md to follow v1.19 of the original (English) text.
Why is this needed
content/ja/docs/concepts/services-networking/ingress.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/tree/dev-1.19-ja.1/content/ja/docs/concepts/services-networking/ingress.md
Original
https://github.com/kubernetes/website/tree/release-1.19/content/en/docs/concepts/services-networking/ingress.md
diff between translated and v1.19
https://gist.github.com/496deaaf9c91fa3a2836e6409b17bcb1
Note
Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/triage accepted

Duplicated by issue #27457

/close


Fix take method in /lib/take.js

There is currently a method called take that lives in /lib/take.js.
It is incomplete and needs to be fixed!
Acceptance Criteria:

Running yarn test <methodName> results in tests passing.
You have written a skeleton method for someone else to work on.
You have written tests surrounding your skeleton method.
Running yarn lint does not print any errors to the console!

Please include the skeleton of a new method + an accompanying test for someone else to work on at the time of creating a pull request! A pull request will most likely be denied if it does not contain a skeleton method for someone else to work on! For more information, please read the Contributing Guide.
Thank you so much for your contribution!

@BlakeGuilloud  I would like to work on this