timeout wmi queries longer than two seconds

This is an attempt to address:
https://github.com/StackExchange/wmi/issues/34

I'm not sure a default timeout of 2 seconds is the best option. How about adding a Timeout property to the Client type that is empty by default, meaning no timeout. Query will still use the default client which won't time out, but if you need to make your own client to do custom timeout things you can.

Thanks for the quick feedback! That seems reasonable, though i wonder at the number of users who will have to customize Clients to deal with something pretty common.
I'm seeing the hanging behavior while using https://github.com/shirou/gopsutil (at https://github.com/shirou/gopsutil/blob/master/cpu/cpu_windows.go#L117).
I'll give your suggestion a shot and update gopsutil as well. Thanks again!

There's a bit more in Query than just using the default client; adding that boilerplate in clients that wish to not hang on unresponsive WMI queries seems burdensome. How does adding a QueryWithTimeout convenience wrapper sound?

On further reflection, it's just as easy for the clients to set timeouts themselves as it is to set up custom clients for queries.


Account error 603 - account flagged as spam?

Hello,
For the last few days I cannot any more manage users in my Keybase teams - I always get an error message "ERROR CODE 603 - you cannot do this right now". According to what I have read in the keybase-friends #help channel it seems that my account may have been flagged as spam. Could anyone look into this issue? I just sent a description of the problem together with my logs via the Keybase app. Thanks a lot in advance!

After sending feedback with my logs twice via the Keybase app (to no avail) I have now tried reporting this issue directly from the command line (keybase log send). My log ID: cbf2f40ca4ae55f328299c1c.

reached out over chat


Use of some animations (e.g. CMU mocap database) leads to strange corruption of face

I'm not a Unity expert so perhaps there's something I'm doing wrong when importing? The CMU mocap database animations (http://mocap.cs.cmu.edu/) don't seem compatible with these models and the results are somewhat terrifying! It would be really useful to upload a small unity project with 3/4 of these models using a couple of open source animations (e.g. Mocap from CMU & mixamo) to promote research use. I'm using Unity 2018.4.12.

Accidentally duplicated due to laggy connection, see #7


Continued Fixing Translate extend cluster

please kindly review
/assign @irvifa
/assign @girikuncoro
/assign @phanama
issue ticket: #15341

@prabangkoro thanks for the follow up PR, this looks great! can you squash all your commits first into 1 before getting this in? this is for cleaner commit body message in master branch. refer to: https://stackoverflow.com/questions/14534397/squash-all-my-commits-into-one-for-github-pull-request
/lgtm

okaay, I'm trying to squash it

@prabangkoro please write proper commit message as this will be the only message shown in master branch, instead of "fix comment" how about "Following up PR #16421 to fix typos and wordings"

also, please becareful on rebasing so that you don't add additional "merge commit". Refer to this if you need it: https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase or https://blog.algolia.com/master-git-rebase
The straight forward way, you can simply go back to the commit before your change, rebase with upstream master (or origin master if your forked master is synced), apply your latest changes, then force push to your fork/branch

@girikuncoro
I'm sorry, I don't really get it and get confused on the rebase stuff :")
Hmm, I hope I get it right this time hehe

@prabangkoro this is perfect, thank you for doing this! 🎉 as usual, feel free to pick any other pages or fixes, so that you can claim your hacktoberfest tshirt
/lgtm
/approve


Setting an example value for a field in response object generates deprecation warnings with pydantic >= 2.5

Environment:

Python version: 3.12.3
Operating system: Ubuntu
Flask version: 2.3.3
flask-openapi3 version: 3.1.3

Warning
If I define a model setting Field.example (not defined in pydantic):
class MyResponse(BaseModel):
    stream_id: str = Field(..., example="some_stream")

then it causes warnings because it is not officially supported by pydantic:
PydanticDeprecatedSince20: Using extra keyword arguments on `Field` is deprecated and will be removed. Use `json_schema_extra` instead. (Extra keys: 'example'). Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.9/migration/

Error
If I define a model setting the Field.examples as advised by pydantic:
class MyResponse(BaseModel):
    stream_id: str = Field(..., examples="some_stream")

Then the examples value does not appear in the resulting OpenAPI schema.
This field was added in pydantic 2.5.0 by https://github.com/pydantic/pydantic/pull/8013
According to OpenAPI 3.1.0 specs, the use of example is deprecated:

Deprecated: The example property has been deprecated in favor of the JSON Schema examples keyword. Use of example is discouraged, and later versions of this specification may remove it.

Debugging the code I see that the 'examples' value is present in the json schema generated by pydantic but removed by flask_openapi3 when converting to the Schema model. It only defines an example and no examples.
I think the simplest fix would be to add a Schema.examples field in flask_openapi3/models/schema.py.

Same issue here. I’m already familiar with json_schema_extra and openapi_extra, but we would like to continue using field-level customization. This approach is compliant with the JSON Schema Draft 2020-12 and the OpenAPI Specification v3.1.0, as noted in the Pydantic documentation.
Are there any plans to support this?
P.S. A big thank you to the developers of flask_openapi3—I truly appreciate your work! I know answering questions can sometimes be annoying, but I think this discussion could be helpful for the project. 😊

@jeronimok see https://github.com/luolingchun/flask-openapi3/issues/177#issuecomment-2351402198


PHP_OS predefined constant was used instead of php_uname() function.

Bug Fixes #240
PHP_OS predefined constant was used instead of php_uname() function.

Thank you for contributing! 🎉


Fix mqtt watch mistake

etcd watcher option WithFilterDelete means not watch delete, not means only watch delete

All tests failed, please fix it


Search across courses

This is actually a really big idea. Make a search box that can search across courses.

Be really great to also pull in some fuzzy search library like Fuse: https://www.fusejs.io/
So have an "indexed" mode that might take a minute to populate, but also an "exact" search that goes faster.
One interesting thing might be how to handle HTML.

Having the ability to choose what courses, what resources (and what attributes of the resources).

Quickly select only published, unpublished, only courses with students or SIS data, etc

Indexing could be done as we load data. Cache it locally, and expire cache periodically. Provide a button to clear the cache.


Allow user to specify environment in provided script

Now user is allowed to specify AppKey and AppSecret in embed script. I am wondering whether we should also allow user to specify environment so that user could switch between Production/Sandbox environment.

I agree, add an options in <rc-phone> tag will be good.

Done. Need to add documents about the options of <rc-phone> tag.


this.session.open_live - syntax error

Hi, I have an error on a fresh installation of node_pcap:
It works fine when the filter arg is an empty string:
var pcapSession = pcap.createSession('en0', '')

But when I set it to a specific filter, e.g:
var pcapSession = pcap.createSession('en0', 'tcp.port eq 55082')

I get this error:
/path/to/project/node_modules/pcap/pcap.js:49
        this.link_type = this.session.open_live(this.device_name, this.filter, this.buffer_size, this.outfile, packet_ready, this.is_monitor);
                                      ^

Error: syntax error
    at Error (native)
    at new PcapSession (/path/to/project/node_modules/pcap/pcap.js:49:39)
    at Object.exports.createSession (/path/to/project/node_modules/pcap/pcap.js:123:12)
    at Object.<anonymous> (/path/to/project/project/index.js:5:24)

My configuration:

Node: v5.1.0
mac OS X yosemite

Further informations:
I installed pcap via npm from the github repo because I got a error on node-gyp rebuild when installing via npm repo.

@fuunnx I think your syntax for the filter is wrong. You should rather try something like,
var pcapSession = pcap.createSession('en0', 'tcp port 55082')
instead of tcp.port eq 55082
You can read more about pcap filters here: http://linux.die.net/man/7/pcap-filter

Indeed, it fixed the issue 😃
My bad, I used the Wireshark syntax. Thank you !
Maybe should we have more explicit error messages for this?

Glad its resolved. Yeah! Having explicit error messages would be great.
Send in a pull request if you got some time to work on that :)


Add a Gitter chat badge to README.md

daidokoro/qaz now has a Chat Room on Gitter
@daidokoro has just created a chat room. You can visit it here: https://gitter.im/daidokoro-qaz/Lobby.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Cancelled this one and recreated the group


entity to send orders to the circuit network

I've done some testing but am too sleepy to finish. Consider this a work in progress until I comment again, or someone else follows up with test results.
I have the unrelated commits as separate branches if you want those PR'd separately, or even removed.
CLOSES #4

PS: the circuit wire connection points and light offsets will need tweaking once better graphics are settled on. I copied the radar just to save time.

Thank you very much for your contribution! I will review when I am able to :).


Builds of Istio-Proxy

The GetEnvoy CLI should be able to consume builds of Istio-Proxy. This means building and publishing it via the manifest.
Note: It is not necessary to distribute via package managers.

@lizan could you take this and give an ETA?

Almost done, 1.2.5 binary: https://tetrate.bintray.com/getenvoy/getenvoy-istio-proxy-1.2.5.p0.g490fa3f-1p34.g71784a0-linux-glibc-release-x86_64.tar.xz

stale


nexus 4, android 5.1 , Chrome 43

Error: CrossStorageClient could not connect at eval (.../node_modules/cross-storage/lib/client.js:151:14)
Only happens on my nexus 4. Is there a known issue or maybe I'm just missing something?

I've got the same setup :) Is it maybe a latency issue, if using data. Have you tried increasing the timeout?

Hey, thanks, I increased it to 5s and it works :+1:


stitching not working too well

Hi,
sorry for this unspecific request, but I found some sample photos where stitching is working very poorly.
For example this one
With enblend and multiblend both, the results have clear borders
Could you have a look at it please?
Thanks

Oh someone else had that posted with an odd title...


services.AddMvc().SetCompatibilityVersion() does not work with OData

 public void ConfigureServices(IServiceCollection services)
        {
            services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_2);

             app.UseMvc(routeBuilder =>
            {
                routeBuilder.MapODataServiceRoute("ODataRoutes", "odata", dwhBuilder.GetEdmModel(app.ApplicationServices));
            });

....
now throws the following exception when using OData.

System.InvalidOperationException: 'Cannot use 'Microsoft.AspNet.OData.Routing.ODataRoute' with Endpoint Routin

g.'

The out-of-the-box OData implementation does not support Endpoint Routing. You'll want to file this issue on their repo. I'm not connected to their team directly or indirectly. There's no way I can fix this.
API Versioning will support Endpoint Routing soon, but it will using it's own facilities. The built-in OData routing facilities are different.

I was hoping I'd be able to get a jump on this, but it's a lot of work that I honestly cannot own. API versioning is imminently about to support Endpoint Routing, but since OData does not intrinsically support Endpoint Routing the API versioning support for OData doesn't either. As soon as the OData team supports Endpoint Routing, I'll make the necessary changes, if any. You can weigh-in on the existing, open issue in the OData repo OData/WebApi#1707. Thanks.


Vickel: Watch bestofiron.com

Vickel requests the watch of the watch_keyword bestofiron\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bestofiron\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


MAINT: spatial: Fix type annotation of query_ball_point

What does this implement/fix?
https://github.com/scipy/scipy/blob/483b75a0e9a089b4a0d8e7c26c6ad8b8b8b34007/scipy/spatial/_ckdtree.pyx#L850-L853
Fix type annotation of query_ball_point: p is keyword parameter

Mypy happy in CI, thanks @marinelay !


Issue with translatable FileUpload field

Package
filament/spatie-laravel-translatable-plugin
Package Version
v3.2.2
Laravel Version
v10.41.0
Livewire Version
No response
PHP Version
PHP 8.3.1
Problem description
Case 1: Creating new record issue
FileUpload field do not clear to upload translated image when switching locale
After filling both languages and saving, edit page will throw  Filament\Forms\Components\BaseFileUpload::Filament\Forms\Components\{closure}(): Argument #1 ($file) must be of type string, array given (https://flareapp.io/share/OmV0Wvp7)
Case 2: Updating record issue
Editing a record with only one locale filled, then uploading image for second locale will throw No synthesizer found for key: "" (https://flareapp.io/share/NPLRBLo5)
Expected behavior
Case 1: Creating new record issue
While creating new record it's expected to clear FileUpload field when locale is changed
After saving, it's expected to be able to edit the record
Case 2: Updating record issue
Image is expected to be uploaded when filling second locale
Steps to reproduce
Case 1: Creating new record issue

Click issues o menu
Click "New issue"
Fill "title" and "image"
Change language to spanish (image will not clear, will have to manually delete to upload new image)
Click "Create" button (error will throw after redirect to edit page)

Case 2: Updating record issue

Click issues o menu
Click "New issue"
Fill "title" and "image"
Click "Create" button
Change locale to spanish
Fill data (error will throw after image is uploaded)

Reproduction repository
https://github.com/msrivela/filament-issue-translatable
Relevant log output
No response

However, it doesn't look like you've provided much information on how to replicate the issue.

I can't see how I failed to provide enough information to replicate the issue, I provided a repository, flare links with error, step by step directions how to trigger the issue. It's all there.

I have the same problem, any solution to this problem?
From my debugging, it appeared that in the database, the "main" language is stored correctly as an array [id => file_name], but it is this "extra" language that is stored as a string.
When debugging the package, I noticed that the "main" language from the "additional" language differs in that, before writing translations in the "additional" languages, the file writes in the form [id => Livewire\Features\SupportFileUploads\TemporaryUploadedFile], and the "main" language (which writes correctly) in the form [id => file_name].

@kamil-bartczak @msrivela
I think the problem is that the 'hydratestate' is not triggered in the handleRecordUpdate.
go to Filament\Resources\Pages*EditRecord*\Concerns\Translatable method handleRecordUpdate and call $this->form->fill($this->data);
before $this->form->validate();
Let me know if it solves your problem !
As a side note, If you guys are using this with Builders/Repeaters there is another problem with the ordering.

@mybouhssina
Sadly that solution did not work for me.
I am in fact using inside a repeater in my project, but not in the reproduction repository.

@msrivela I'm sorry to hear that, I think this issue might be related:
https://github.com/filamentphp/filament/issues/11825

I can confirm I have the same problem.

See #11450

That is quite possible since my test use case seemingly only use hydrated hooks. I'll check it out and adjust

The latest changes to the PR should get it to work

Sticking to Filament 3.0.75 works, as mentioned by @msrivela
But for this to works in the latest version, i had to use both @mybouhssina and @Voltra workarounds. @Voltra solution fixing the lang switching on edit and @mybouhssina solution fixing the model saving issue.

@Lucathiel The latest version of the PR should include the fix @mybouhssina proposed, was there anything else you added?

as a side note, there is another problem I encountered while using Repeaters/Builders with this plugin. If my memory serves me well, it was whenever I switch language and save, the repeater/builder elements orders will change. From my understanding, it was due to saving the builder/repeaters in the old local data as objects with UUID keys and that JS doesn't guarantee the object properties order, so what I ended up doing is transforming these Objects to Arrays and the problem was solved, I can share the code if someone is interested.

I did encounter a very similar problem with filament-navigation. That one was package specific, but maybe something similar is still in the core filament components. The fix is simply to use an array and to push items onto it (instead of adding a new key using a UUID).
That being said, it's not specific to this issue and possibly not to this (sub-)package.

Same problem here 👋
I've tried to apply the changes suggested on PR #11450 and worked well for updating.
But for creating, when I try to change the language, the FileUpload component remains with the previous state: https://d.pr/v/kMz2bs
How did you solve this issue when creating?

Oh... we hadn't, yet. It's the same fix, I'm adding it now.

@abdukhashimov applying the patch derived from my PR should do the trick

I did the trick of creating a json file and tabs with field.lang
I tried the patch, it raised me issues with disabled fields. Disabled field was not populated even though it was returned from DB.

I did the trick of creating a json file and tabs with field.lang I tried the patch, it raised me issues with disabled fields. Disabled field was not populated even though it was returned from DB.

The disabled field was quite basic: It was the combo of Title and slug

I solved the problem with a walk around where I was using the latest version of filament which is 3.2.74, I solved it with downgrade filament version 3.1.8 and it work fine with me.

this also fixable with #11450 when using $this->form->getRawState() 👍

I am posting this same message across all Spatie Translatable issues & PRs
Hey all! Wanted to update you on where we're at with the translatable plugin.
I really appreciate your patience while this issue has been active. While I created the plugin for the community, I've never actually had a project where I needed to use it, and that's the same for the rest of the Filament team. As such, it's the reason why the plugin hasn't had as much attention as the others, and is much more unstable: I just don't have the environment to test all the use cases, nor the motivation to make it truly great.
As such, I put out a post a month ago and asked who in the community uses the plugin and has knowledge of plugin development. Luckily, Lara Zeus and Mohamed Sabil stepped forward, who are both authors of popular Filament plugins and are trusted by the community.
We are strongly considering handing over maintenance of the plugin to those developers, for the good of the community. You can find their fork at https://github.com/lara-zeus/translatable.
Since the new developers have lots of experience with the plugin and active projects that use it, they should be able to help debug issues easier and make a much more stable experience for other users.
If their work goes well until v4 is released, we will likely retire the plugin at that point and recommend the fork as an official replacement. If it does not go as expected and the community is unhappy, then we will reconsider this decision. I am closing this for now, and if we decide to take maintenance back officially then we will probably reopen it.
The existing plugin will continue to receive security updates indefinitely. Please let me know if you have any further questions.
Many thanks,
Dan

this an attempt to fix the issue if anyone willing to test this PR I would appreciate the feedback.

confirmed, tested @atmonshi PR, my problem was that i was trying to save images in a Repeater field and messed up my data in database and also when i was changing between languages when state was updated
tnks @atmonshi for the fix hope that we will have an official update on filament/spatie-laravel-translatable-plugin so we don't have to merge vendor files...

hey @paul2Dev my fork is the unofficial plugin for now. and a lot of fixes has been added there.
you can use it and you can open any issues there.


Task submission use cases

This is the possible use cases when submitting a task to the queue.
Case 1: Single Result
The user whould like to find or computer a result identified by a specific:

'program',
'driver',
'method',
'basis',
'molecule',
'options'.

The user will create the molecule and store it in the Database, and has its ID.
For the options, they should find it in the options table?? (TODO)
Ques: is the common case to have many of such single results at the same time?
The following is the logical steps to be done:

Search results table to see if it exists using the data s/he has (flaged with include_queued=True).

If found and status=COMPLETE) then return the results data.
if found but status=INCOMPLETE, then merge hooks and return the job ID and result ID or a top
level procedure ID
If not found at all, then add a result or a top level procedure, and submit a task into the queue.

This should be mostly done in the socket itself.
When a task is done:

if it's a simple result, store the data in task.base_result, then call the hooks.
if it's a procedure, "create" the children results, and then update the procedure object (it's id is in task.base_result) with those ids. Next, call the hooks.

I think the heart of this PR has been long closed. @doaa-altarawy Please let me know if you wish to reopen.


Add image_id label to recording rule

How to categorize this PR?

/area monitoring
/kind enhancement
/priority normal
What this PR does / why we need it:
Add image_id label to seed:images:count recording rule. This will make viewing the images more human readable since some of the container images are simply a SHA.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
@istvanballok @ThormaehlenFred
Release note:

Add `image_id` label to `seed:images:count` recording rule

@wyb1 , you need to rebase to make ci/cd happy as there was recently a change to the pipeline definitions (ref https://github.com/gardener/gardener/pull/2935).


Reorganizes the two results sections.

Renames, reorganizes, and re-links the results sections to distinguish between the Task- and Pipeline-level instructions. Also fixes some links and wording.

/test pull-tekton-pipeline-build-tests
/lgtm


[Base Command] Remove constructor, pass ID assignment to getter method.

Looks good! Do you mind adding a test in for calling twice
https://github.com/SmoothPhp/CQRS-ES-Framework/blob/master/tests/CommandBus/CommandTest.php

Can you add a test and pull request to the develop branch


Feature argo removal

📲 What
Argo removed from project
🤔 Why
With Swift.Codable we don't need Argo anymore
🛠 How
Swift.Codable protocol adoption for the models was implemented
⏰ TODO

[ ] Push Notification Testing
[ ] DeepLink Testing

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


New grid layout feedback

The new UI packs all lectures for a course into a grid; the old layout was much easier to navigate in my opinion.
I don't care for previews at all; I know from Moodle or Artemis which lecture I would want to (re-)watch and on which date it occured. Searching for dates is much harder now than just traversing down the old list of lectures as my eyes have to jump across the previews.
This is a breaking change for me, I feel strongly about this and rather use /old.

Thanks for the feedback! A list with the thumbnails on the side is surely an option too.
It's kind of a pity that most lecturers don't assign meaningful titles to their lectures. That would make it much more salient to users which VOD they are looking for.
May I ask about your opinion of the new start page?

It also helped in the old design that the videos where clustered by month. That way I was able to find the lecture I was seachring much faster.
It would be cool to keep at least the structure of the old design. Maybe with a thumbnail at the side (although it wouldn't be of any use at that size, since it is always look the same with a white screen with illegible text and a presenter in the corner, since realistically almost no lecturer will add custom thumbnails. And making the thumbnails readable in a list would increase the amount of scrolling too much for no functional benefit)

About the start page: when I use TUM live, it is usually in one of two use cases

there is a current livestream going on. Then it is good to have it large on the screen, like in the new design. That is a good change in my oppinion
I am behind on a lecture (or want to rewatch it) and select the course from the list to find the lecture. More often than not, I am not only looking for the last VoD and navigate through the course view. So, I think the recent VoDs have too much reelestate, compared to the list of my courses. (also currently, 2/3 of the screen is empty on my device. That space could be used)

In my opinion, one row with thumbnails of my current livestreams and below that a list of courses would be more functional (maybe even with a quick link to the recent VoD of the course). But this is only the way I would best use the system and it could be that most people use it differently ;-)
But overall it is a really cool tool and the whole livestream / VoD experience is really awesome. Good job on that!

start page
When searching for a lecture in the old design it was fairly easy for me:

Select course
Scroll to month
Select the one with the correct date

IMHO, the current new startpage gives too much space for thumbnails / the preview grid, and too little space for selectors (by semester, courses and public courses). I'd also doubt that the order of these is correct, as they should be ordered by relevance (my guess is that most students watch asynchronously).
A plus for the new site is that it feels faster when rendering new courses. Did you change the front-end stack? Can you also maybe comment on what motivated the whole front end change?
font
I also just realised that the font is hard to read, I'm on Windows, 1920x1080, and it's very small and icky somehow. Maybe adjusting the weight or making it some ticks bigger will solve this.

Once again, thank you for your valuable feedback. We are currently collecting opinions and comments to update the UI accordingly. Keep in mind that the UI, in its current state, is a WiP.
On the topic of lecture selection: We are currently working on reintroducing months for the course page. How this ultimately will look, we are not sure yet. However, there certainly won't be the need for a next button.
Thumbnails are certainly something to get used to, I know. Nonetheless, I firmly believe that by giving course admins the opportunity to be more creative (and be it custom thumbnails, or video sections), lectures could become more than the throw-away products they currently are. On that note, we are currently discussing deleting hundreds of hours of material from previous semesters for exactly that reason. But as I said, the Thumbnail-UI clearly can improve.
You hit the nail on its head with regard to performance. The old start and course pages are prime examples of small clean code bases becoming increasingly unmaintainable by adding feature upon feature. That's why we decided to redesign these pages from scratch using modern-day typescript.
Regarding the font: We don't supply any font family. Therefore what you see is probably the standard font for your particular browser. But I agree we can definitely enlarge certain elements. For the time being, use the zoom feature of your browser.


Pr correct test script

refine test case script which made it more robust or correct, or fail sometime.

The CI currently uses Vim version 9.0.  The support for deleting a file after a function exits by using the 'D' flag in writefile() was added in Vim 9.0.0379.  Can you remove this change from your PR?  I want to make sure the plugin works with Vim 9.0 and not rely on the latest Vim version.

ok, but if so i am adding test/Xtest.c and Xtest.cpp into gitignore as well, since in case it failed, it maybe left on the local.
// thx, anyway, now ci passed finnally... :rofl: l


Update author list

List is generated by git log --format='%an <%ae>' |sort |uniq with few manually post process.

Some of the names are fake.  Rincewind for instance is a character in Terry Pratchett novels.  At least with the email addresses we can vaguely tell who they are, but one has no email address.
Do we want to make a distinction between people who made non-trivial contributions, and people who made trivial contributions like fixing a simple typo?  That would probably weed out all of the fake names if we didn't credit people for just fixing a typo.

Changes:

Update the email and name list per @jrtc27's comment
Remove people who made trivial contributions from the list

Ping

In case, we want to find the email address to contact, we still can found that from git log.
Changes:

Only keep name in the author list.

Changes:

Sort by last name
One name per name

Preview PDF: riscv-abi.pdf


Feat(trait): Knative service visibility support

I'd like take up this issue.(#1712)
I also need this feature.
I'm not familiar with the manners, so please let me know if I am wrong.
Modifications

Add visibilitys option
https://knative.dev/docs/serving/services/private-services/

Release Note
Feat(trait): Knative service visibility support

@christophd
Thank you for your review.
Is there anything further I should do after this for the merge?
(I do not have permission to do the merge)

@halmakidon Unfortunately I also do not have merge permissions
Adding @tadayosi

@tadayosi
Thank you for your reply.
I'll leave the rest to you.


Navigate links inside hover_doc

Make it possible to navigate links inside hover_doc, like in image:

had implement
https://user-images.githubusercontent.com/41671631/226177896-9a234c2c-8554-4a21-87f2-bd5b47193cc7.mp4

Very cool! Does it also work with symbols? For example, in tsdoc, doing this
/** Directions of the anchor that are enabled to be picked by the user.
* Pre-defined combinations available through {@link enabledAnchorsCombinations}. */

Generates the screenshot

This command
:lua vim.lsp.buf_request(0, 'textDocument/hover', vim.lsp.util.make_position_params(), function(_, result, ctx) if not result then return end print(result.contents.value end)

Produces (note the link)
```typescript
(property) AnchorPickerProps.enabled?: Anchor[] | undefined
```
Directions of the anchor that are enabled to be picked by the user.
Pre-defined combinations available through [enabledAnchorsCombinations](file:///home/sorashi/Projects/bp/schemcat/src/components/AnchorPicker.tsx#L13%2C14).

support


Unable to close a todo if a completed todo has the same id

Example:
ID: 1 Title: Test1
ID: 2 Title: Test2
Completed Todos:
ID: 1 Title: Another Test
We will not be able to close the active todo with id 1.

Solved in v0.2.2


Traffic not flowing over clean GRE after cron reboot

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
Traffic routed over clean GRE tunnel seems to stop after a scheduled device reboot.
Let's say i have a site A with two lans, one wan, one gre

igb0 <IP_ADDRESS> (MPLS IP assigned by ISP)
igb1 <IP_ADDRESS>/24
igb2 <IP_ADDRESS>/24
gre0 <IP_ADDRESS>/30 (Leaning on WAN igb0 GW <IP_ADDRESS>)

Let's say i have a site B with one lan and one wan

igb0 <IP_ADDRESS> (MPLS IP assigned by ISP)
igb1 <IP_ADDRESS>/24
gre0 <IP_ADDRESS>/30 (Leaning on WAN igb0 GW <IP_ADDRESS>)

Site A routes when GRE is up:
<IP_ADDRESS>/24 via <IP_ADDRESS>
Site B routes when GRE is up:
<IP_ADDRESS>/24 via <IP_ADDRESS>
<IP_ADDRESS>/24 via <IP_ADDRESS>
After Cron scheduled device reboot i'm always founding traffic not flowing trough GRE tunnel, notice that GRE tunnel is up and reachable both directions. I'm actually just solving the problem disabling and enabling back the 3 routes writed above: after that i can see all the traffic flow over GRE tunnel as expected.
To Reproduce
Configure GRE tunnel between two devices, A and B.
On B: route A Lan over GRE with a static rotue entry
On A: route B Lan over GRE with a static route entry
Configure on Cron a scheduled reboot: once the device comes back up traffic will be forwarded to <IP_ADDRESS>/0 ignoring the static route(s) entry(es).
Expected behavior
I'm just expecting the traffic to flow over GRE as statics routes tolds to it.
Screenshots
N/A
Relevant log files
N/A
Additional context
N/A
Environment
OPNsense 20.7.7_1 (site A)
OPNsense 20.1.8_1 (site B)

Hi.
I was digging a bit on the problem via ssh:  i can clearly see that the gui isn't creating the routes under BSD os.
OS before cron reboot

root@opnsense:~ # route show <IP_ADDRESS>/24
route to: <IP_ADDRESS>
destination: <IP_ADDRESS>
mask: <IP_ADDRESS>
gateway: <IP_ADDRESS>
fib: 0
interface: gre0
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
0              0             0             0       1476            1           0

OS after cron reboot

root@opnsense:~ # route show <IP_ADDRESS>/24
route: route has not been found

OS after disabling and reenabling back static routes

root@opnsense:~ # route show <IP_ADDRESS>/24
route to: <IP_ADDRESS>
destination: <IP_ADDRESS>
mask: <IP_ADDRESS>
gateway: <IP_ADDRESS>
fib: 0
interface: gre0
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
0              0             0             0       1476            1           0

Hi.
I was digging a bit on the problem via ssh:  i can clearly see that the gui isn't creating the routes under BSD os.
OS before cron reboot

root@opnsense:~ # route show <IP_ADDRESS>/24
route to: <IP_ADDRESS>
destination: <IP_ADDRESS>
mask: <IP_ADDRESS>
gateway: <IP_ADDRESS>
fib: 0
interface: gre0
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
0              0             0             0       1476            1           0

OS after cron reboot

root@opnsense:~ # route show <IP_ADDRESS>/24
route: route has not been found

OS after disabling and reenabling back static routes

root@opnsense:~ # route show <IP_ADDRESS>/24
route to: <IP_ADDRESS>
destination: <IP_ADDRESS>
mask: <IP_ADDRESS>
gateway: <IP_ADDRESS>
fib: 0
interface: gre0
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
0              0             0             0       1476            1           0

Can you try this patch? https://github.com/opnsense/core/issues/3414#issuecomment-759328642

Can you try this patch? https://github.com/opnsense/core/issues/3414#issuecomment-759328642

@peironem are you on 21.1 now? I prepared another patch that looks like it will help in your case: a980771
# opnsense-patch a980771

Cheers,
Franco

Sorry, it needs two patches:
# opnsense-patch a980771 90ad674

Sorry @fichtner i moved all our firewalls on pfsense distribution because this issue was creating some nasty broblems on our sites interconnections.
If i'll buy any new firewall i'll test this.
Thanks anyway for your help.

Ok, no problem.
Note to self: clean up rc.newwanip


Add execve to CommandExecution

Not sure why this was left out initially, perhaps there is something I am overlooking? I think posix_spawn could be added for more coverage too. But it has a slightly different argument pattern than exists already, nevertheless easy to implement.

I think posix_spawn could be added for more coverage too. But it has a slightly different argument pattern than exists already, nevertheless easy to implement.

Nevermind, I see getTarget().getName().matches("\\_spawn%")

The change is now merged and should get deployed to lgtm.com in about two weeks.


[Issue]: How to redirect to one specific agent

Describe the issue
How to redirect the input based on expertise in groupchat?
For example, In a groupchat there are two agent (say math and science), the input is "what is 2+2", Based on the input the manager should redirect it to math Agent. The other agent should not reply. How to do this?
Thanks
Yogesh
Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response

Do you have an explicit rule/criteria for deciding what message to predict to which agent? If so, you could achieve it using a custom speaker_selection_method.  Find an example in this notebook: https://github.com/microsoft/autogen/blob/main/notebook/agentchat_groupchat_customized.ipynb

example above and lots of examples in 0.4


highway=track is never taken into account although routing across them might be "shorter"

I haven't read the source code, but as far as i know GraphHopper never uses highway=track for routing. I think there might be cases where routing via tracks (especially when these parts are short) should be considered.
Here is a simple example:
https://graphhopper.com/maps/?point=54.327536%2C9.908702&point=54.325459%2C9.911342
7km vs. >1km and  5min vs. >1min.
There might be better examples with much more indirect way when not navigating through a track.
In my opinion there should be a mechanism to detect if there is an shorter option via track (let's say if it saves about 400%of time or something). Maybe an algorithmic function can be found to take this into account.
I know integrating something like this might be very time intensive for developers, but should be made possible for the future.

As this came up on the mailing list again I had a look into your first example. One part of the way is tracktype=grade3 which is currently not allowed - only grade1
The problem is now really that some countries require 'track usage' and others like Austria forbid this, so related to #175 but will think about it.

Here's another example where it's critical that tracks are taken in account:
https://graphhopper.com/maps/?point=Dakhla الداخلة%2C Morocco&point=Nouadhibou%2C Mauritania&layer=MapQuest
Actually, tracks are taken in account, but only when tracktype = grade1. It should be extended to grade2 (above example) and even grade3 (OP example). Here's the relevant bit from CarFlagEncoder.acceptWay:
if (tt != null && !tt.equals("grade1"))
    return 0;

I would take every highway into account unless access-restrictions or maxheight or something forbid passing there. Imho this would be the only way for worldwide optimised routes.
Naive thoughts:
Every highway should have a base factor, that is hierarchical (primary>secondary etc) and certain tags are voting this factor up or down (tracktype, surface,smoothness etc). So you got diferent routes with factors for every piece of road. Now we could make use of the length of the ways and weight them with this factor.
By the way I don't know anything about the algorithms at Graphhopper, I just want to share my view :eyeglasses: You already mentioned that tags already considered for bikes and foot routes.
It does make sense to use a (short) way with a bad conditions if you are saving a lot of kilometers/miles! Especially in countries where there is a bad road network (for whatever the reason might be) that is essential to access some places like in 3rd world countries or huge countries like Australia.

Imho this would be the only way for worldwide optimised routes.

The problem is country specific defaults. So we really need #175 before including more streets which make problems in other countries. E.g. a track is often mapped without access restrictions and the default in Germany is that you can access it but in Austria the default is that it is forbidden.

Hmmmm… where do you get the information from ? is it austrian law ? there’s a proposal on openstreetmap that says otherwise:
http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions#Austria
so I would expect the mappers to follow this. But of course not all mappers follow the recommendations, we have to cope with thousands of different mappers with different ideas. If really all tracks are forbidden by default in some country, then a postgres sql request should take care of it all at once in the master DB. Or we could do it when we process the pbf - as proposed below.
At the end of the day, though, the ways that are not marked as access=no (or motorvehicle=no, etc..), in the DB or by post-processing, should be taken in account in the algorithm.
Now I don’t think this is such a big deal, if the speed is mapped to a pretty low value for those tracks, then a longer route through paved roads should be selected by the routing algorithm 99.9% of the time. Maybe we could do a test with, e.g., a new vehicle type such as 4x4 or motorbike, then we could compare and see if it really makes such a big difference ?
Laurent
On 15 janv. 2015, at 13:18, Peter<EMAIL_ADDRESS>wrote:

Imho this would be the only way for worldwide optimised routes.
The problem is country specific defaults. So we really need #175 before including more streets which make problems in other countries. E.g. a track is often mapped without access restrictions and the default in Germany is that you can access it but in Austria the default is that it is forbidden.
—
Reply to this email directly or view it on GitHub.

Thanks Laurent, not read the law, I had spoken with one from Austria :)

Now I don’t think this is such a big deal, if the speed is mapped to a pretty low value for those tracks,
then a longer route through paved roads should be selected by the routing algorithm 99.9% of the time.

That is a very good argument :) ! We can think about including at least grade2 before we properly implement this via #175

The workaround won't close this issue, but maybe suited for everyone ;). Will be live in ~2 days.


Win32_Interop.lib unresolved external symbol listAddNodeTail, aeWait, etc.

Hello, I'm using hiredis on windows 7 32-bit, Visual Studio 2013 Express
The redis and hiredis can be build without error.
But when I tried to build hiredis/example/libuv or libevent, I'm getting 'unresolved external symbol' error message from Win32_Interop.lib, the missing functions are listAddNodeTail, aeWait, etc.
my test project link to hiredis.lib,Win32_Interop.lib,libuv.lib (or libevent.lib)
Please help, thanks!

Hi @JerryYangJin
we are aware of the issue and we are going to fix it.
We don't have a release date yet.
We'll let you know when the fix will be available.
Thank you.

@enricogior , thank you for your update!

From now on for hiredis and hiredis issues please visit https://github.com/Microsoft/hiredis.
Thank you.

@enricogior  is this bug fixed?

Hi @dhdepddl
I don't work anymore on this project.


Cannot build provisioners without node-monorepo

Summary:
Provisioner project fails to build if it is not checked out as a submodule of node-monorepo.   The provisions project should be buildable entirely on it's own.
This is because tsconfig.json attempts to reference kubeclient tsconfigs from above the root of this repository.
To Reproduce:
Steps to reproduce the behavior:

Clone fresh copy of provisioners repository.
Attempt to build
See error

Observed Results:
A clear and concise description of what happened that was not expected.
Expected Behavior:
Project should be able to build.
Screenshots:

Failure Logs
@provisioner/common: $ tsc -b
@provisioner/contracts: $ tsc -b
@provisioner/common: error TS5083: Cannot read file '/home/connery/c6o/kubeclient/packages/kubeclient/tsconfig.json'.
@provisioner/common: error TS5083: Cannot read file '/home/connery/c6o/kubeclient/packages/contracts/tsconfig.json'.
@provisioner/common: error Command failed with exit code 1.
@provisioner/common: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@provisioner/contracts: error TS5083: Cannot read file '/home/connery/c6o/kubeclient/packages/contracts/tsconfig.json'.
Checklist

[ ] I am running the latest version
[ ] I checked the documentation and found no answer
[ ] I checked to make sure that this issue has not already been filed
[ ] I'm reporting the issue to the correct repository (for multi-repository projects)
[ ] I have provided sufficient information for the team

The issue is now resolved.


sysflow operator initial commit

Signed-off-by: Carlos Hsiao<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[x] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

The error from operator-olm-deployment is not clear to me.
May I have some clues to fix it?
Thanks.
===== Test: operator-olm-deployment =====
Failed to deploy the operator with OLM: java.lang.Exception: Error running Ansible playbook 'deploy-olm-operator.yml': hudson.AbortException: script returned exit code 2

/test CVP

/retest

/test CVP

The error from operator-olm-deployment is not clear to me.
May I have some clues to fix it?
Thanks.
===== Test: operator-olm-deployment =====
Failed to deploy the operator with OLM: java.lang.Exception: Error running Ansible playbook 'deploy-olm-operator.yml': hudson.AbortException: script returned exit code 2

This is problem on our side. This was fixed and we are retesting all pull requests. This might take a while

Thank you so much, @mvalahtv

@weii666, No problem.


Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'SegmentFetcher' could not be found. Verify that a module by this name is registered in the native binary.

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
React Native version:
Run react-native info in your terminal and copy the results here.
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Memory: 2.82 GB / 15.83 GB
Binaries:
Node: 14.11.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3
System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-201.87<IP_ADDRESS>53283
Visual Studio: Not Found
Languages:
Java: javac 15
Python: 3.8.7
npmPackages:
@react-native-community/cli: Not Found
react: ^17.0.1 => 17.0.2
react-native: 0.63.4 => 0.63.4
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
I don't really know how to recreate it. It was working perfectly and now this error shows up randomly. No new libraries added, nothing. Last major change was adding fonts to the app.
Expected Results
To show the screen without having to refresh the server to get rid of the error
Screenshot
The error showed up again and I was able to take a screenshot of it. This is what I see:

In my case i get the same message randomly when using metro server and fast refresh during development.

@adumat  Any luck rectifying this issue?


[WIP] v3 api

There are also some improvements on UI:

New table for interview selections and allocations:


Messaging/alert for not enough native token gas for amounts close to max

Overview
Currently in production, when selecting an amount that is close to, but not the max amount of an asset a user gets not enough ASSET.ASSET for gas.
Sending some amount less than very close to the available balance will result in a successful trade (if it is above the minimum)
Displaying to the User an amount of balance, and then not allowing them to interact with the balance in full has caused support tickets and a bad user experience for those transacting in small amounts and wishing to use their full balances in any transaction.
References and additional details
https://github.com/shapeshift/web/assets/94998097/eec5195c-f0fc-49ca-a227-e3f07b18ed05
Acceptance Criteria
Could we possibly allow a user to send all of their balance and subtract the gas after they have selected the full amount?
Man this feels like a feature request for Send Max.
Still gonna keep it as a ticket.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

This very use case was conflated with the "max" button functionality which ended up as a Rube Goldberg machine that had to fetch multiple quotes for a given swapper:

one to determine the fees
another to determine the quote using the input amount minus the fees from the previous quote

The issue is that network fee fluctuations were causing trade failures. We added a multiplier on the fee to allow for some fluctuations but it always meant balance was left over in the account, hence "send most" meme in product discussions.
I strongly recommend we avoid this

Man this feels like a feature request for Send Max.

if it walks like a duck...

per conversation on 1-22-24 product will look at error messagin to other UX to help user undertand

Hah, the ole send max of native asset. I think the solution is, sadly, none.

Operations writes a nice macro with product to explain why we're different. Decentralized and multiple quotes. Inherently, we can't tell you the max of the native token minus the quote until we...have the quote.
Closing because this can't really solve with UX and messaging.

From the product lens it should "just work" aka it gives you the maximum amount when you click on it. We could get creative with optimistic quoting if we have one protocol but we have like 4 swappers and will add more too.


Remove SpyderPluginMixin and improve external API

Important note: This change breaks compatibility between external plugins developed for Spyder 3.0 and 4.0 (but I think it's for the better).
Important note: Compatibility with Spyder 3.0 is maintained as long as plugins subclass from SpyderPluginWidget.

Due to differences in initialization of mixins between PyQt4 and PyQt5:
http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html#cooperative-multi-inheritance
I preferred to remove SpyderPluginMixin and convert it into BasePluginWidget and PluginWidget.
I think SpyderPluginMixin was a trick introduced by Pierre to more easily develop plugins with a single widget. However, by removing that mixing and creating all plugin widgets as attributes of themselves, we can have a way cleaner and simpler API for all plugins (the previous API was a mess!).
Now people that read Spyder source code will understand our design model: widgets are isolated, they are embedded in plugins, and if they need to communicate info to other plugins, they have to emit Qt signals which are captured and routed by its corresponding plugin.

TODO:

[x] Define a more basic class from which BasePluginWidget will inherit, This class will contain the methods we don't want users to know about in spyder.api (like create_toggle_view_action).
[x] Don't import spyder.api in spyder.plugins because we're not guaranteeing backwards compatibility anymore.

Is it possible to have a plugin without a widget? I think this could be useful for things like adding a menu item, or support for a programming language, or support for some types in the variable explorer.

Is it possible to have a plugin without a widget?

Not right now, but that's the next step. This just cleans our internal API for plugins with widgets and put it in decent shape :-)
After merging this one (which I think is ready), I'll open PRs in all our third-party plugin repos to make them subclass from SpyderPluginWidget instead of SpyderPluginMixin.

Ok, this is going in. Letting know @Nodd and @jitseniesen about it.


Adding a section to the intro about contributing

Description
Adding a paragraph about contributing to docs
Related Issue(s)
https://github.com/konstructio/colony-docs/issues/36
How to test

Yeah, years ago, people use to break line even in the middle of sentences at column 80. It was useful before we have better IDEs like today, but now it make text more difficult to read, update, and lint, so we decided not to do that on the docs. You could reconsider if you want, just sharing some context on the decision not to do it :)

@konstructcarrie did you also wanted to update the package-lock.json file?

@konstructcarrie did you also wanted to update the package-lock.json file?

Yep, just forgot to add it to the commit notes


Delete Custom Sound

:warning: Is your feature request related to a problem? Please describe

I don't see how I can customize the soundboard (even the material color). I'm not sure if I can remove custom sounds.
:bulb: Describe the solution you'd like

Press and hold on a sound to make the menu appear (the one to set a ringtone), and add an entry to delete a sound from the app.
:bar_chart: Describe alternatives you've considered

:page_facing_up: Additional context

:raising_hand: Do you want to develop this feature yourself?

[ ] Yes
[X] No

Fixed with https://github.com/OMGSoundboard/android-app/pull/100.


BNavItemDropdown position props are not working

Describe the bug
The props dropup, dropleft, dropright, right, left props are not working for BNavItemDropdown
Expected behavior
Proper positioning of dropdown with applied props. Even though they are applied in the code, they do not work
     <b-nav-item-dropdown class="user-dropdown" right>
        <template #button-content> User </template>
        <b-dropdown-item>Settings</b-dropdown-item>
        <b-dropdown-item>Sign Out</b-dropdown-item>
      </ b-nav-item-dropdown>

Environment (please complete the following information):
"bootstrap": "^5.2.0",
"bootstrap-vue-3": "^0.3.3",

From my testing, it appears that the menu inside the navbar is not able to go right, because it doesn't have enough space... I've noticed that it modifies the space of the navbar component. When I had built the component, it was all rendered in a simple b-nav, so no problems. But navbar spacing is static and doesn't like to move, so issues. This is all incorrect as the menu is rendered as a child of navbar, but actual affect is appeared to be outside the component. Complicated issue

Should be next on the list of things to do for v0.8.0

Fixed in v0.8.0. However, it should be noted that "right" and "left" props are removed - use "alignEnd" and "alignStart" respectively


Master to ExMigration

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/New-MailboxRestoreRequest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-App.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/users-and-groups/Set-UnifiedGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubSiteAssociation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppInfo.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Grant-SPOHubSiteRights.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Register-SPOHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHubSiteAssociation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Unregister-SPOHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPField.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPHubSiteAssociation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPNavigationNode.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPAccessToken.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHideDefaultThemes.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPInPlaceRecordsManagement.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListInformationRightsManagement.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListRecordDeclaration.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPNavigationNode.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUPABulkImportStatus.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Install-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPHubSiteAssociation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHideDefaultThemes.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPInPlaceRecordsManagement.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListInformationRightsManagement.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPListRecordDeclaration.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPTenantCdnPolicy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWebTheme.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Uninstall-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Unpublish-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Update-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/readme.md
:white_check_mark:Succeeded

sharepoint/sharepoint-ps/sharepoint-pnp/sharepoint-pnp.md
:white_check_mark:Succeeded

sharepoint/sharepoint-ps/sharepoint-server/Copy-SPActivitiesToWorkflowService.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Disable-ProjectServerLicense.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEmailNotification.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Disable-SPProjectEnterpriseProjectTaskSync.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Dismount-SPSiteMapDatabase.md
:white_check_mark:Succeeded
View (sharepoint-ps)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


HHH-13462 Introduce a fastpath for SessionImpl#fireLoad to be used by…

… internal loops
https://hibernate.atlassian.net/browse/HHH-13462
@gbadner @sebersole @dreab8  this patch introduces a copy of void SessionImpl#fireLoad(LoadEvent event, LoadType loadType), which skips these 3 operations:
 checkOpenOrWaitingForAutoClose();
 checkTransactionSynchStatus();
 delayedAfterCompletion();

I called the new method void fireLoadNoChecks(LoadEvent event, LoadType loadType) , this should make it much more effective when invoked from hot loops.
I do believe it's safe to skip these "checks" from internalLoad and from immediateLoad. Could you have a thought on that please?
Also: if you know of any other method which could be a good candidate to invoke this method safely, please let me know.

discussed this further with @dreab8 , then merged.


revises front-proxy sandbox to include envoy service sidecars alongsi…

…de each service
Commit Message: revises front-proxy sandbox to include envoy service sidecars alongside each service
Additional Description: none
Risk Level: Low
Testing: the sandbox's verify.sh script
Docs Changes: none
Release Notes: revise front-proxy sandbox to include envoy service sidecars alongside each service
Platform Specific Features: none
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

we also want to update the front-proxy/depends_on so its depending on the sidecars and not the backend services

that would necessitate configuring healthchecks for the sidecars.  i'll see if i can find an example..

that would necessitate configuring healthchecks for the sidecars. i'll see if i can find an example..

yeah - thinking further on this - i think we can make the front-proxy depend on the services being service_healthy and the sidecars being service_started - not 100% reliable, but i think probably will work (adding healthchecks would be better, im not sure we have done so in other Envoy services in our examples)

really appreciate the guidance and responsiveness to help me figure out how to get this right.


How to access ingress (macOS)

Hello, folks. I am trying to setup a simple app (with deployment, service and ingress). And I can not access ingress endpoint.
macOS: 10.14.3
Docker version 18.09.2

I have pretty basic setup. To reproduce:

./dind-cluster-v1.13.sh up

Everything is ok at this point and i can access dashboard.
> kubectl get nodes
NAME          STATUS   ROLES    AGE     VERSION
kube-master   Ready    master   6m34s   v1.13.0
kube-node-1   Ready    <none>   5m59s   v1.13.0
kube-node-2   Ready    <none>   5m58s   v1.13.0

kubectl create -f example.yaml

example.yaml:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: api-gateway-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
  rules:
  - http:
      paths:
      - path: /testpath
        backend:
          serviceName: hello-kubernetes
          servicePort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: hello-kubernetes
spec:
  type: LoadBalancer
  ports:
  - port: 80
    targetPort: 8080
  selector:
    app: hello-kubernetes
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hello-kubernetes
spec:
  replicas: 2
  selector:
    matchLabels:
      app: hello-kubernetes
  template:
    metadata:
      labels:
        app: hello-kubernetes
    spec:
      containers:
      - name: hello-kubernetes
        image: paulbouwer/hello-kubernetes:1.5
        ports:
        - containerPort: 8080

Here are results:
> kubectl get ing
NAME                  HOSTS   ADDRESS   PORTS   AGE
api-gateway-ingress   *                 80      2m20s

> kubectl get svc
NAME               TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
hello-kubernetes   LoadBalancer   <IP_ADDRESS>   <pending>     80:32184/TCP   4m31s
kubernetes         ClusterIP      <IP_ADDRESS>       <none>        443/TCP        7m57s

>kubectl get pod
NAME                                READY   STATUS    RESTARTS   AGE
hello-kubernetes-676bcb4ccb-9sprr   1/1     Running   0          4m7s
hello-kubernetes-676bcb4ccb-d6bpt   1/1     Running   0          4m7s

> kubectl get nodes -o wide
NAME          STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION     CONTAINER-RUNTIME
kube-master   Ready    master   11m   v1.13.0   <IP_ADDRESS>    <none>        Debian GNU/Linux 9 (stretch)   4.9.125-linuxkit   docker://18.9.0
kube-node-1   Ready    <none>   10m   v1.13.0   <IP_ADDRESS>    <none>        Debian GNU/Linux 9 (stretch)   4.9.125-linuxkit   docker://18.9.0
kube-node-2   Ready    <none>   10m   v1.13.0   <IP_ADDRESS>    <none>        Debian GNU/Linux 9 (stretch)   4.9.125-linuxkit   docker://18.9.0

And at this point I want to access my ingress endpoint and I can not (Operation timed out).
Service external ip address is in pending state. What am i doing wrong 🤔?

I don't think there is any ingress controller in dind .. Anyway it should relies on a third party reverse proxy ..
For external access I use an external nginx and nodeport services.

@Philippe-Collignon can post an example of your usage?

Same issue here

@Igor-lkm try: kubectl port-forward --address <IP_ADDRESS> nginx-deployment-76bf4969df-nrjwn 80:80
and then, access localhost:80

@zhongjixiuxing well, yep, that is working: nginx + port-forward,
my steps, more or less:

install ingress-nginx
Apply config.yaml:

apiVersion: v1
kind: ConfigMap
metadata:
  name: tcp-services
  namespace: ingress-nginx
data:
  81: 'default/hello-kubernetes:80'

(complained about port 80: port 80 cannot be used for TCP stream services. It is reserved for the Ingress controller., so I set port to 81, but i thank idea is clear :)
3. kubectl get pods --namespace=ingress-nginx to get a pod name
4.  kubectl port-forward --address <IP_ADDRESS> nginx-deployment-76bf4969df-nrjwn 81:81


create PPT for chapters presentation

First chapter presentation to occur on the 27 of Jan in London

Done http://www.slideshare.net/DinisCruz/owasp-summit-2017


Adding Jupyterlab operator for Openshift under community-operators #2194

Signed-off-by: Atef Aziz<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[x] Does your operator have nested directory structure?
[x] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
I dont have a right-hand menu but I'll try to add this PR to the project in the community-operators repo
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Is there a way I can add this to the new submissions project board? I don't see an option to do so here or directly on the board.

/retest

Added a commit to add the "support" metadata field to the CSV. One of the DCO checks mentioned a missing metadata key which may have been the "support" field.

/test CVP

/test CVP

/test CVP

CVP is down, we cannot test. Once they fix it, we can continue. Thanks for understanding.

/test CVP


feat(MeasureTheory/Integral): hasSum_integral_of_summable_integral_norm

A lemma on interchanging sums and integrals (pretty much equivalent tointegral_tsum, but without explicitly mentioning ENNReals, lintegrals etc). Also, correct a random capitalisation glitch I spotted in the process.

Thanks for the comments, I've uploaded a revised version

bors r+
Thanks!


[WIP] Pr virtual inherit of scheduled work item test

Describe problem solved by this pull request
Attempt to make px4::ScheduledWorkItem inherited virtually.
I created this PR to launch some CI test.

Can you remind me why this is needed?

Can you remind me why this is needed?

Thank you for your attention. My proposal is to make pca9685_pwm_out inheriting from both I2CSPIDriver and OutputModuleInterface, as PCA9685 is mounted on I2C bus while providing PWM outputs to motors and servos. Those two interface have ScheduledWorkItem as their common base class...


Keep pydantic type information at runtime

While trying to figure out https://github.com/samuelcolvin/pydantic/issues/1243 I stumbled over the following behavior:
class Foo(BaseModel):
    bar: PositiveInt

foo = Foo(bar=1)
type(foo.bar)  # int

I think it would be useful if foo.bar in the example above were of type PositiveInt at runtime since runtime checks seem to work as expected with PositiveInt, notice:
assert isinstance(PositiveInt(1), PositiveInt)
assert isinstance(PositiveInt(1), int)

assert not isinstance(1, PositiveInt)  # PositiveInt is more specific than int
assert not isinstance(PositiveInt(1), NegativeInt)

Minimal example where this would be useful:
from functools import singledispatch

class NaturalNumber(PositiveInt): pass

@singledispatch  # if no implementation is found
def my_abs(i): raise TypeError(f"bad operand type for my_abs(): '{type(i).__qualname__}'")

@my_abs.register  # handling 0, see End of the question for implementation of  'Zero'
def _(i: Zero) -> NaturalNumber: return NaturalNumber(0)

@my_abs.register # handling integers > 0
def _(i: PositiveInt) -> NaturalNumber: return NaturalNumber(i)

@my_abs.register # handling integers < 0
def _(i: NegativeInt) -> NaturalNumber: return NaturalNumber(-i)

then the following works at runtime:
assert isinstance(my_abs(PositiveInt(1)), NaturalNumber)
assert isinstance(my_abs(NegativeInt(1)), NaturalNumber)
assert isinstance(my_abs(Zero(0)), NaturalNumber)
assert not isinstance(NegativeInt(-2), NaturalNumber)  # -2 is not a natural number

Sidenotes/Questions:

fields types (like PositiveInt and also my implementation of Zero) do not perform runtime checks on their own e.g. (PositiveInt(-1) does raise an exception). This is somewhat unexpected; could this be changed without breaking existing code?
I tried having NaturalNumber inherit from Zero and PositiveInt but got TypeError: multiple bases have instance lay-out conflict, so without resolving this isinstance(Zero(0), NaturalNumber) would not work

Extras:
Implementation of Zero used above:
class Zero(int):

    @classmethod
    def __get_validators__(cls):
        yield cls.validate

    @classmethod
    def validate(cls, v):
        if not v == 0 :
            raise ValueError('Non-zero integer passed to constructor')
        return cls()

Humm, I'm not sure I agree though I agree it can be confusing.
I think this would cause more problems than it would solve, e.g. with other libraries not knowing how to deal with PositiveInt.
It would also be confusing since we can't return an instance if the type annotation in all cases, e.g. Json.

I think we should document this rather than changing the behavior.

When PositiveInt is a reasonable subclass of int reasonable functions (1) that take int should be able to handle this at runtime ( try PositiveInt(2) > 1 or PositiveInt(1) + 1)). For mypy this works out as well, since PositiveInt being a subclass of int makes it a sub type and functions behave covariantly with respect to their arguments.
Another nice benefit where mypy is concerned: observe type(PositiveInt(1) +1)) being int i.e. using "impure" functions like __add__ that know nothing about PositiveInt (and thus could violate the constraints of PositiveInt) downgrade the type to int. Any consumer of this result that expected an PositiveInt would now raise a TypeError because it can't be guaranteed that PositiveInt(1) + someInt is still positive.
Concerning Json over at https://github.com/python/typing/issues/182 someone suggested usingJSONType = t.Union[str, int, float, bool, None, t.Dict[str, t.Any], t.List[t.Any]]

(1) https://en.wikipedia.org/wiki/Liskov_substitution_principle

Ummm, this is really a deal breaker as I cannot use a custom json encoder on subclass instances of primitive types. :cry:

information is available in V2 via model.model_fields.


Netlify Build issue?

Hi @runemadsen! Running into an error where the build is "taking too long" and timing out on Netlify. See #261

I'm presently in the middle of a local build and will update here if it finished successfully.

Could this be an issue now that the site has many more pages? Is running npm run clean for every single deployment a problem?

Maybe we can address this over dessert?

The local build completed but the page queries did take 904 seconds!

Looking at this now! I'm going to try to upgrade to Gatsby v4, and then take a look at whether we need to downsize some of the images / add build caching to Netlify.

After looking into this yesterday, there's a number of factors leading to this happening:

The build time on Netlify (+30m) is significantly higher than on my local machine (5m). This must be caused by Netlify's build machines having much less power than my local one
Many images were above 1mb. This is an issue since every build resizes the images, and larger images seem to have an exponential effect on the build time. Netlify should in theory cache the image resize results and use them in the next build if they didn't change, but that doesn't seem to be happening despite updated the Netlify Gatsby plugin.
Gatsby will automatically create 3 sizes of each image to use for responsive designs. We might be able to run through the site and tweak that functionality for images that are just shown in small such as the showcase images

@shiffman Here's what I suggest for next steps:

Contact Netlify and ask if they can increase the build time (@shiffman)
Run through the repo and resize all showcase images to 800-100px max (?)
Check the gatsby setup when resizing responsive images and see if there are any performance gains (@runemadsen)

Does that sound okay to you?

@runemadsen yes, this sounds like a great plan! Could the fact that I am running npm run clean && npm run build be the issue related to the image resize results not caching? I added npm run clean when some aspects of the site weren't updating properly after a build, but we might have only thought this was happening due to a longer build time!
I can try removing that and see.
Yay!

Excellent. As long as you're just running clean on your local machine, it shouldn't be able to affect the build process on Netlify. But it will slow down your local build time.

Ah, but I am running it on Netlify itself! (not locally). I'm going to take that out now and see if that improves anything.

Hi!
A couple quick things:

I have requested a build limit increase, so the timeout should stop.
Running clean removes the cache, so it drastically increases the build time.
Image optimization is one of the biggest culprits in long Gatsby builds. Resizing those images down the the largest size you need them (keep 2x density in mind!) will make a big difference.

Does this site run the Netlify Gatsby plugin when it builds? That will further speed up builds if it’s not already in place. Search “Gatsby” here to install: https://app.netlify.com/plugins
Let me know if I can help with anything else!

Thanks @jlengstorf!
We just upgraded to version 3 of the Netlify Gatsby plugin last week, and I think that helped a bit. We'll downsize images and see how fast we can get it to build :)
Rune

I don't want to jinx it build the build has doubled in speed and is now coming in around 15 minutes. . will keep this thread open for a bit longer but as of now it is all good by me!


[feat] custom load dependencies

Closes #1684
Problem
The invalidate function only re-runs load if fetch is used. This is not possible in cases where an APIClient does not allow for customization of the fetching process or when using non REST APIs like GraphQL.
Solution
Add a dependencies array to the LoadOutput (suggested by @Rich-Harris in https://github.com/sveltejs/kit/pull/1709).
The dependencies will be registered the in the same way fetch does it. This allows not only to invalidate real resources but entire pages or groups of pages.
Example Usage
<script context="module">
import { api } from '$lib/myapi';
export async function load({params}){
    const item = await api.getItem(params.id);
    return {
        props: { item },
        dependencies: [`/item-${params.id}`, 'custom:item-page']
    }
}
</script>

<script>
import Item from '$lib/Item.svelte';
import { invalidate } from '$app/navigation';
export let item;
</script>

<Item {item} />
<button on:click={()=> invalidate('custom:item-page') }>Reload Page</button>
<button on:click={()=> invalidate(`/item-${item.id}`) }>Reload Item</button>

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[X] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[X] This message body should clearly illustrate what problems it solves.
[X] Ideally, include a test that fails without this PR but passes with it.

Tests

[X] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[X] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

@icalvin102 just a quick question....
Is this problem not solved by page endpoints?
To the best of my understanding this should generate a load function on build.
By moving the $lib/myapi integration to the endpoint there should be no trouble on calling the load again ;)

@dreitzner page endpoints will only work if your API is written in sveltekit AFAIK.
Page endpoints wont work in SPA mode and/or when using third party APIs that rely on browser state like cookies that are not accessible from the sveltekit server.

thank you!


How to change route with react-router-dom  with out call url and not request to server

I use react-route-dom in React SSR (server side rendering) project. when i click on Links i want change route but not request to server (not request in SPA mode - request only in direct call)
i think we can use event.preventDefault() to stop default action of but i don't know how do it with Link.
question in stackoverflow

That is what Link will do for you. You must put it underneath a Router for it to work.

it's not my question solution. tell me, how can i do it with react-router or react-router-dom. i think this package can not support it.

React Router supports SSR. I'm not sure what you're asking, because your original question isn't clear. Do you have example code to look at?


[FEATURE REQUEST] Add a horse armour.

I really would like if you could add a horse armor to your mod.

Yes that'd be nice @codeman1o1


Prebuilt docker image line endings cause error

When running the container an error is encountered:
docker run --rm ghcr.io/jan-brinkmann/docker-rotate-backups
: not foundpoint.sh: line 2:
/home/entrypoint.sh: set: line 3: illegal option -

This is due to the windows line endings in the image in ghcr:
docker run --rm -it --entrypoint=sh ghcr.io/jan-brinkmann/docker-rotate-backups
/ # head -n3 /home/entrypoint.sh | od -t x1
0000000 23 21 2f 62 69 6e 2f 73 68 0d 0a 0d 0a 73 65 74
0000020 20 2d 65 0d 0a

Whereas the repo is correct:
# /tmp/docker-rotate-backups/src# head -n3 entrypoint.sh | od -t x1
0000000 23 21 2f 62 69 6e 2f 73 68 0a 0a 73 65 74 20 2d
0000020 65 0a

Hi. Did you find a way to fix this?

You can build it from the repo:
docker build https://github.com/jan-brinkmann/docker-rotate-backups.git#main -t docker-rotate-backups-custom
Then use the image "docker-rotate-backups-custom" in your compose or other commands.

Thanks


Lottie: Animation Segment(Marker) Support

issue: https://github.com/thorvg/thorvg/issues/2044

@fall2019, could you please squash your unnecessary commits to the one?

Okay. I usually use squash on merge option. Will try to squash later.

Squashed all commits into one.

Okay. Thanks for reviewing and your article is really helpful. Will resolve the comments later.

You're welcome. Will try to resolve soon.

Resolved all comments.

Resolved comments.

Okay. Thanks for comments. Will resolve soon.  🤔It has been a mystery for me of how others come up with same format style. I didn't find formatter config in the repo so I just manually format it one after another.

@fall2019 Well, currently we don't have specific convention(formatter), but we're trying to keep as consistent style as possible.

Thanks for comments. All resolved rn.

Thanks. Resolved.

@hermet I guess the example part(LottieExtension) that I've just reviewed is not main part of this Marker feature. So let me know if I've overreviewed.
I can also improve LottieExtension part in this issue #2122

@tinyjin, I think you can focus on the feature enhancement first. Actually, examples should be added as a separate commit. @fall2019, Basically, we prefer atomic patches, the best form of the PR is to separate patches for feature enhancement and examples because feature enhancement would not depend on examples. So if you separate them, that will be better for us.

Alright. Resolved.

@fall2019 One more, please add yourself "https://github.com/thorvg/thorvg/blob/main/AUTHORS"  please.

Thanks. Resolved all comments.

@hermet
I've tested segment API in various suites, seems nicely working. (some minor consideration -> commented)
Here, I wanna make sure two things.
1. Unit test
Should we include unit test for marker & segment in this patch? Otherwise, I can also add all cases I've checked into testLottie.cpp and capiLottie.cpp right after merging.
2. Support marker comment in JSON objects.
"markers": [
    { "tm": 0, "cm": "{\\"name\\":\\"bird\\"}", "dr": 22 },
    { "tm": 22, "cm": "{\\"name\\":\\"explosion\\"}", "dr": 11 },
    { "tm": 33, "cm": "{\\"name\\":\\"feather\\"}", "dr": 77 }
]

This is also from RFC, the markers[].cm could be JSON string. Do you think it must be in this patch? I think we can gradually support this case in next patch.

1. Unit test
Should we include unit test for marker & segment in this patch? Otherwise, I can also add all cases I've checked into testLottie.cpp and capiLottie.cpp right after merging.

@tinyjin Yes, It would be better to perform unit testing, but it's not mandatory in this PR.
@fall2019 Since on this topic, Returning the list of marker names will be essential, so users can inquire about the available markers in the animation. Probably, like this:
uint32_t LottieAnimation::markerCnt();  //return the marker count
const char* LottieAnimation::markers(uint32_t idx); //return the marker name by a given index.

The items(unit test and apis) mentioned above are not the main focus at this point but will become essential eventually. Therefore, it's up to you. If you'd like to include them, please update the PR accordingly. Thanks.

2. Support marker comment in JSON objects.
"markers": [
    { "tm": 0, "cm": "{\\"name\\":\\"bird\\"}", "dr": 22 },
    { "tm": 22, "cm": "{\\"name\\":\\"explosion\\"}", "dr": 11 },
    { "tm": 33, "cm": "{\\"name\\":\\"feather\\"}", "dr": 77 }
]

This is also from RFC, the markers[].cm could be JSON string. Do you think it must be in this patch? I think we can gradually support this case in next patch.

@tinyjin No, it shouldn't be.

Add api
uint32_t LottieAnimation::markerCnt();  //return the marker count const char* LottieAnimation::markers(uint32_t idx); //return the marker name by a given index.
Resolved all comments.

@fall2019. So far pretty good.
It's around the corner. I'm going to soon wrap up this patch by my side.
Thanks.

Okay. On your side.

#2164


RFP proposal - Economic Audit Simulator

Grant Application
This application is (select one):

[x] Speculative (use this by default)
[ ] an RFP response

This application is (select one):

[x] Public (fully)
[ ] Public with private finances

Abstract
[Provide a brief description of your project here (summarise key points).

Proposal for an economic audit simulator on Substrate
If your application is part of a programme, please mention which in the first line of the abstract.

The details should be in the application 'document' that you add to this repo via a pull request.]
Checklist

[x ] The grants document has been read and understood.
[ x] The Google Form will be completed accurately. Note that the Google Form requires the pull request URL.
[x ] Abstract (above) is succinct and complete.
[ x] The application is being included into the correct directory: either 'targeted' or 'speculative'.
[x ] The application includes a project description.
[ ] The application includes all names of team members.
[ ] The application includes a description of the team's experience.
[ ] The application includes all necessary links (e.g. GitHub and LinkedIn)
[ ] The "Development Roadmap" section in the application has a timeline of development ("milestones").
[ ] The "Development Roadmap" section in the application has an estimate of funds required.
[ ] The "Development Roadmap" section gives an indication of the team's long term plans.
[ ] The "Development Roadmap" section includes documentation as a deliverable for at least one milestone.

Thanks for the RFP. That's great. Could you update the title in the md? And it would be nice if you could integrate some links into the rfp, which explain more concretely what gauntlet is doing or what you have in mind.

Hey guys, sorry i totally missed your comments @Noc2 . Thank you @alxs !


Prevent duplicate signups

We should track the users who are signed up so that if they try to sign up again, we can avoid trying to update their playlists' twice.
We may be able to do this by checking if permission has already been granted, otherwise we have to enable removal from our tracking also.

Hi, Can i work on this?

Hi, go for it @MaheshS08

Thank you, would you mind explaining this is in more detail ?

Thank you, would you mind explaining this is in more detail ?

Sure @MaheshS08 .
When a user signs up, we get a token from Spotify that we then send to our Lambda service. I think the token we receive is likely to be different every time (might be worth verifying this), even from the same user.
This token expires so we then fetch a different token from Spotify that allows us to continue performing API calls on their behalf. We should check if we already have a token for the user signing up - you might need to save more details about them in the db or do a lookup of their unique id before saving to do this.
Does that make sense?

Hi @KieranBond , I am facing some issue with application setup locally, could you please mention some instructions on this?

Have you read the readme @MaheshS08 ? What specifically are you struggling with?

You'll need to install GNU Make to run the command, or you can run the contents of the command in a terminal instead - it's essentially a shortcut for a Node command. Check out the makefile file to see what it's trying to run for you.
It sounds like you may need to run Docker compose up in the terminal at the root of the project and get the database running for your API to start up as that's on port 8000. Sorry, that's probably missing from the readme.
Does that make sense?

Oh and I can see you're running make run-website from the frontend folder. That needs to be done from the root folder also as the makefile is at the root.

Hi @KieranBond , I am able to run webapi after docker compose up command. Can I access http://localhost:8000/ in browser because i'm getting Site can't be reached?

The frontend will be accessible at http://localhost:8080, the backend will be http://localhost:5213 if running using the http launchsettings profile @MaheshS08

The database is at http://localhost:8080

Both frontend and database are same ? @KieranBond

Oh, sorry, typo on my end. The database is on port 8000 not 8080 @MaheshS08

But when I get localhost:8000 in browser it says site refused to connect , do I need to do anything before ? @KieranBond

That's because you're trying to connect to the database in your browser.
If you're trying to see the website then that's on port 8080

Your backend should be what connects to the database, as its configured to in the appsettings.development.json file

How's this going @MaheshS08?

Hi @KieranBond , sorry for the delayed response.
I'm currently out if station and will be back on Tuesday.
Sorry to inform this.
Let me know if that works for you

No worries, just checking - let me know if you need any help @MaheshS08

Hi, @KieranBond , I'm able to run website using Go Live option in VSCode, and when I signup it goes to mail chimp website, then after if i click continue to website it redirects to Tomorrowify.com.
Is this the behaviour ?
I'm unable to figure out what to do next !

You'll need to look at the /signup page @MaheshS08. It will also require you to change the callback URL we provide to Spotify to be your localhost equivalent.
Once that's setup you can see if Spotify provides a consistent response or not. If it doesn't, then we need to add logic in the backend to ignore the request


[ONNX] Support ScatterElements with reduction

Support ScatterElements on ONNX front-end as described in ONNX docs. Just now Scatter op implementation is used where reduction attribute is not supported at all. Also CI tests are supported for the op.
P.S. In other PRs after that I plan: 1. remove scatter_add and reconnect all its using to ScatterElements(reduction="add") 2. remove scatter implementation and use ScatterElements(reduction="update") instead of it. It will remove the restriction related to input tensor rank size (just now rank <= 4)

@tvm-bot rerun

@AndrewZhaoLuo I did not compare performance on GPU, but I prepared new PR where replace scatter_add by scatter_elements and reuse code for cuda

One moment for scatter_add: it is implemented for 1d, 2d, 3d and 4d input tensors, as scatter. I thought that I can reuse scatter_add approach, but as result I have done scatter_elements in general way without restrictions on input data rank

@tvm-bot rerun


can we get access to chrome://flags?

I'm on windows 10, version 5. Is there a way to turn off the smooth scrolling? I know that Franz is just Chromium with a nice wrapper, but it would be great to turn off smooth scrolling.

Other perspective for this issue is that on Linux smooth scrolling seems to be off, and I would prefer to have it on there. Access to chrome://flags would be really ideal, but at least toggle for smooth scroll would be nice.

access to chrome flags would be really nice

+1