Update to latest angular

Please allow angular 1.7 as peerDependency

Wow that was fast, I guess it will be on npm any minute now!
Thanks for beeing so responsive!

Yup, just published to npm. 👍

Feel like trying out a rewrite? Version 1.1.0 should be on npm soon. Added a service that tracks the window state. Check out the README.md.
Shouldn't break anything. The broadcast stuff is still there and functions the way it always has.


Refactor major components to streamline logic

Problem Statement
As I worked on #1568 I had hard time figuring out what was happening where, in fact I left a TODO there because I was unable to figure out what make function in the bundles/files/utils was trying to do:
https://github.com/ipfs-shipyard/ipfs-webui/blob/16e15a25ab999d4912ea05ebb81e9bad67457770/src/bundles/files/utils.js#L12-L78
Then as I was trying to find what listenes to FILES_WRITE_UPDATED actions, I was able to find nothing. Later I discovered that make function does some trickery where it dispatches FILES_X_STARTED, FILES_X_FINISHED actions and also does some extra stuff on finish. This all makes really difficult to know what happens where.
Solution
This pull request is attempt to streamline everything, so that looking at the specific doX function tells you all you need to know without having to look around other places to get a sense what happens after finish etc... In order to accomplish that it switches from FILES_X_STARTED / FILES_X_FINISHED style action dispatch to making FILES_X actions dispatch events with job field that that updates it's state (as in state machine) from Idle -> Active -> (Done | Failed).
This also gets rid of all the post success followups:
https://github.com/ipfs-shipyard/ipfs-webui/blob/16e15a25ab999d4912ea05ebb81e9bad67457770/src/bundles/files/utils.js#L42-L60
And post failure followups:
https://github.com/ipfs-shipyard/ipfs-webui/blob/16e15a25ab999d4912ea05ebb81e9bad67457770/src/bundles/files/utils.js#L61-L76
By using try { ... } finally { ... } in in the doX functions, so it's plain and clear:
https://github.com/ipfs-shipyard/ipfs-webui/blob/f235c331c80068a023359efd50cbef48a6008d9b/src/bundles/files/actions.js#L324-L338
Pull request also introduces idea of non atomic tasks that (start, make progress, finish or fail) so that doX tasks that report progress don't need to do custom workarounds:
https://github.com/ipfs-shipyard/ipfs-webui/blob/16e15a25ab999d4912ea05ebb81e9bad67457770/src/bundles/files/actions.js#L298-L310
Instead spawned tasks (that follow above described state machine) can yield, to produce update states:
https://github.com/ipfs-shipyard/ipfs-webui/blob/f235c331c80068a023359efd50cbef48a6008d9b/src/bundles/files/actions.js#L243-L251
And it adds typing for all of this so any inconsistencies could caught early on. In the process I also fixed bunch that existed.

Small ask: as noted during our chat today, we need to understand if/how this change impacts the way WebUI's opt-in Countly metrics are gathered (not a blocker, but we should know the impact before merging this).

This was a good call @lidel, indeed analytics seems to use mix of regexps and strings to hook into these actions, which is also a reason I have missed those:
https://github.com/ipfs-shipyard/ipfs-webui/blob/master/src/bundles/analytics.js#L6-L20
I will look into updating that module to take into account the changes made here.

@Gozala mind rebasing this PR?
We really want to merge this before https://github.com/ipfs-shipyard/ipfs-webui/pull/1615 (if possible)

@Gozala mind rebasing this PR?
We really want to merge this before #1615 (if possible)

Just pushed the version that merges changes from master. It end up been a bit more work than I have anticipated & I had not had a chance to do a testing with merged version yet.


Crash on parallel scan

go version: latest
dalfox version: latest
OS ubuntu
tried --multiscan, --mass,  --multicast --mass --mass-worker 100 and dalfox file urls.txt
all were qsreplace FUZZ
crashes not matter what.


Gulp tasks fail: Cannot find module "microsoft/sp-build-web"

Category

[ ] Question
[x] Bug
[] Enhancement

Expected or Desired Behavior
I have node version 10.19.0. I have gulp version 3.9.1. I have npm version 6.13.7
I am able to build and debug a new hello world webpart solution. I wanted to try js-display-list webpart. I ran the following commands:
npm install
gulp serve
I was expecting to try the js-display-list sample webpart on my hosted workbench.
Observed Behavior
I get the following error at the end of "gulp serve".
Error: Cannot find module '@microsoft/sp-build-web'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (E:\Sharepoint Projects\sp-dev-fx-webparts\samples\js-employee-spotlight\gulpfile.js:4:15)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)

I have tried
npm install --save-dev @micrsoft/sp-build-web
Following is what I got
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@micrsoft%2Fsp-build-web - Not found
npm ERR! 404
npm ERR! 404  '@micrsoft/sp-build-web@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! AppData\Roaming\npm-cache_logs\2020-02-22T17_37_24_309Z-debug.log


[sdk]: Include .c and .h items by default

Fixes #574
Instead of just ignoring all default items with EnableDefaultItems=false I decided to switch off all particular default item groups except the ones included in Compile items. This allows us to be better integrated with common SDK properties.
Since DefaultLanguageSourceExtension only supports 1 extension, others like .h were added separately with the same switching logic.
For the reference I used Microsoft.NET.Sdk.DefaultItems.props

CI seems unhappy with the changes. Could you please take a look?

There was a problem likely caused by us caching the templates produced during tests, in system-wide nuget cache. I'll take a look at that: we should not use the system cache during template/sdk tests.


fix: set explicit build-backend

The project seems to use poetry to manage its dependencies, and defining the build-system allows building it using the generic build frontend, which distros heavily rely on.
See https://github.com/python-poetry/poetry-core#usage.

Thank you!


Forbidden

When trying to update my theme I get an error (forbidden) in WordPress, but if I remove wp-update-server/packages/.htaccess it works. Am I doing something wrong?

Do you mean that wp-update-server is part of your theme, or that you're updating the theme from a wp-update-server instance installed somewhere else? If it's the second one, is the update process trying to download a ZIP file directly from the packages directory for some reason?
Either way, that's an unexpected error. Please check the Apache error log (and maybe also the PHP error log) for more details about the error.

Related to WP 6.4.3 changes? https://core.trac.wordpress.org/ticket/60398

I'm updating the theme from a wp-update-server instance installed somewhere else.

All right, so check the Apache error log on that update server. If it cannot parse the .htaccess file, or .htaccess is disabled, or something like that, there should be something in the log.
Also, try opening the update metadata URL in the browser and see if the download_url is valid. Generally, it should end with something like ?action=download&slug=whatever, and it should not point directly to the packages subdirectory.

The download URL is correct

I probably should have asked this earlier, but where/when exactly do you see the error, and what exactly does it say?

Like this:

In my functions.php:
$myUpdateChecker = PucFactory::buildUpdateChecker(
	'https://[domain]/wp-update-server/[theme-name]/info.json',
	__FILE__, //Full path to the main plugin file or functions.php.
	'[theme-name]'
);

In info.json:
{
    "version" : "1.0.1",
    "details_url" : "[my-bitbucket-url]",
    "download_url" : "[domain]/wp-update-server/packages/[theme-name].zip"
}

Is that wrong?
I have not changed anything else in wp-update-server

I see. It's not so much "wrong" as it is dramatically missing the point of wp-update-server. The purpose of this project is to automate the task of generating the JSON for the update checker (plus a few other minor benefits, like logging).
If you just want to use static files, you don't need wp-update-server at all. You can just make a new directory on your site and put your info.json and [theme-name].zip in that directory. Uploading wp-update-server to your site and then putting those files inside the wp-update-server directory provides no benefit, and can cause additional problems, as you discovered.

And if I want to automate the task of generating the JSON, what should I change?

I changed my functions.php to:
$myUpdateChecker = PucFactory::buildUpdateChecker(
	'https://[domain]/wp-update-server/?action=get_metadata&slug=[theme-name]',
	__FILE__, //Full path to the main plugin file or functions.php.
	'[theme-name]'
);

and I no longer seem to need to have a the info.json file, and it also works with having the .htaccess in place! Thank you for your help! :)

All right, nice to hear that it's working now. That change looks good to me. I will close this issue as completed.


ci: Reintroduce the check on raw test vm boot

Lets wait after launching the vm for testing until we see the welcome
message
Signed-off-by: Itxaka<EMAIL_ADDRESS>

I'd wait for my PR (https://github.com/rancher-sandbox/cOS-toolkit/pull/557) to finalize before merging this if you don't mind. There I did a couple of changes to speed up boot. Default SATA ports number is 30 and this has a huge impact on boot and causes at least a failure on initial OEM mount (even this should not hurt it might have impact on boot time).

oh I see, so if you dont specify it just  creates 30 ports?? Wow.

oh I see, so if you dont specify it just creates 30 ports?? Wow.

you never know right.. :rofl:

closed in favour of #591


[ nitro protocol ] Remove all GAS_LIMIT instances

Making this change didn't break anything. And it seems to allow ethers to automatically provide an accurate estimate for the gas limit.

I think this change should increase the probability of our deploy branch test (which runs puppeteer against the deployed app) passing. Accurate gas limits should get txs mined more quickly.


Update QT to 5.9.6

Update QT and other dependencies to 5.9.6

Updated: https://github.com/cevap/ion/pull/65


Wrong documentation displayed in tooltip for union of interface and function in VSCode

A common pattern in my code is to have an interface with a name Foo and a function Foo to construct an object that matches interface. Due to this bug its hard for the user to see the right documentation when consuming these entities.
TypeScript Version:  2.8.1 (as this is a bug that only manifests in the IDE, I'm not sure how to test on latest dev version)
Search Terms: "intellisense", "interface and function", "wrong documentation"
Code
/** This is documentation for the function */
function Foo(): Foo {
    return { foo: "foo" }
}

/** This is documentation for the interface */
interface Foo {
    foo: "foo"
}

const f: Foo = Foo()

Expected behavior: When hovering : Foo in VSCode, I expect to see the documentation for the interface.
Actual behavior: The documentation for the function is displayed.
Playground Link:
Related Issues:

I tested with versions 2.9.1 and 3.0.0-dev.20180609 and I can reproduce the issue with both.
@Duckers Use dev builds.

PRs welcomed. we will need to filter the documentation on declarations based on the meaning of the reference node.

As a lot of libraries (including mine) now probably have a bug-dependency here (as I keep moving docs that should be on the interface, to the function), for backwards compatibility we should probably display the function docs when no interface docs is available. Alternatively, always display a union of the docs, similar to how it shows a union of the entities.

On second thought;
When using the pattern of having an interface Foo and a function Foo to construct an object that matches the interface, the docs for those two entities are usually very interconnected. If they are treated as completely separate entities, we tend to end up having to duplicate information between them.
Hence, displaying a union (e.g. docs for both entities) is probably the most pragmatic solution as it allows us to specify information in one place, and have it displayed in all relevant contexts.

We now show both as requested


An Amazing Nextjs Docusaurus-like website!

Hey, I was searching for weeks for a way to integrate/migrate our Docusaurus website with dynamic rendered content, and we tried to tweak Docusaurus to be served via SSR instead of pre-building static assets so dynamic markdown docs could be fetched at runtime.
I stumbled upon this amazing recreation of docusaurus UI with nextjs which was exactly what i was starting to work on.
I think that an SSR Nextjs Docusaurus-like website, just like this awesome repo, would be an amazing contribution to the open source community!
Could you please share some resources and general information about a key points that used in this project that made it fill like an exact nextjs replica of docusaurus website? Is this repo is based on other opensource repo?
I'm looking into creating a general purpose Nextjs-Docusaurus open source implementation based on your worki(if this is allowed of course) and any details could help.
Again thank for this awesome repo!

Hi, this repository is not a Docusaurus like website. The documentation of Argos is built on top of Docusaurus. We just linked the two on the same domain.


update SPDX License info

What does this PR try to resolve?
fixes #12797

link to latest license info
update link for further info to main spdx page

Link to further info was pointing to a 2018 news update, now points to the main spdx page.

@bors r+

:pushpin: Commit eb9e7f2277c4d463bd48aa666f11ec457373e4ea has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit eb9e7f2277c4d463bd48aa666f11ec457373e4ea with merge c857ebb73a6680de0d2538c4b916865e50d8ad82...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing c857ebb73a6680de0d2538c4b916865e50d8ad82 to master...


feat: support run cortex foreground

Describe Your Changes
Running Cortex in the foreground provides developers with an additional tool for debugging and helps newcomers learn the flow. This ticket aims to support running Cortex in the foreground without disrupting the current workflow.
cortex start --foreground

Self Checklist

[x] Added relevant comments, esp in complex areas
[x] Updated docs (for bug fixes / features)
[ ] Created issues for follow-up changes or refactoring needed

@dan-homebrew @luke-nguyen990
This will depends on our decision for https://github.com/janhq/cortex.cpp/issues/1672

@dan-homebrew @luke-nguyen990 This will depends on our decision for #1672

@dan-homebrew @luke-nguyen990 This will depends on our decision for #1672

I want to explore and onboard myself more deeply here.
Before writing the code above, I already looked at the flow for log.

The current discussion seems to be about the approach and design for log streaming to files.
For this PR, I created a feature for log in the terminal specifically for optimizing local development


Mouse Pointer Crosshairs Across Monitors

Description of the new feature / enhancement
Enable mouse pointer cross hairs to flow across multiple monitors.
Scenario when this would be used?
I love the mouse pointer crosshairs for helping my eyes flow across the page.
I often have spreadsheets open across my two monitors.

It would be extremely helpful and useful to have the mouse crosshairs flow across multiple monitors to easier view / identify the row across the monitors. <<<
Does that make sense?
(And it would be helpful for other documents as well.)
Thank you for your consideration.
Thank everyone for their work on PowerToys!  Love 'em.

Supporting information
No response

/dup #16531


capture timezone info for dates search

dateparser.search.search_dates does not capture timezone info while dateparser.parse does. (See #488 )
Added timezone support for the search.
It may bring some false positives if the text contains a word stands for a timezone but not intent to

Thank you for that, @peonone!
I'm leaving some comments for your consideration.
Would be good if tests could pass without modifying them, there's also a performance improvement we could try.
Let me know what you think about those.

Thanks for the feedback @asadurski
I made the fixes and now all original test cases passed.


Design Components Overview page

goal: A page that will serve to see an overview of all components in the library.
This page main use is to assist the user to find quickly the component they are looking for.
Current
http://sap.github.io/techne/components.html
Maybe we to put them in categories...

@joseegm Based on some review of other sites and the need to link to this overview page from the homepage, we should have this page. I would suggest we update the current Components overview page with images for each component.
Here's an example - http://carbondesignsystem.com/components/overview
Ideally, @LeoT7508 or @jinjiahuangsap can create images for each base component that will look good as a whole on this overview page.

@LeoT7508
Let me know when you have something to show

@joseegm
When we have something to share we will. This weeks team call will probably be a good time to share stuff Jinjia and I have worked on.


feat: default values for ui-tools (#258)

override default values for "draw", "shape", "icon" and "text" when used with UI

Please check if the PR fulfills these requirements

[x] It's submitted to right branch according to our branching model
[x] It's right issue type on title
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has description for the breaking change

Description

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

Maybe you should add some contributors, like @jinwoo-kim-nhn and @junghwan-park, as reviewers of this PR.

Can you also add the option for the fill color in the shape class?

Thanks for your suggestion. How can I add reviewers?

How can I add reviewers?

Sorry, now that I looked into it I don't think it is possible to add reviewers.


Latitude and longitude functions have been removed and in the request…

Latitude and longitude functions have been removed and in the request body the parameters have been replaced with zero.

Pull Request Test Coverage Report for Build 378

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-1.3%) to 98.693%

Files with Coverage Reduction
New Missed Lines
%

index.js
2
97.87%

Totals

Change from base Build 372:
-1.3%

Covered Lines:
105

Relevant Lines:
107

💛  - Coveralls


Issue with k8s.io/docs/admin/high-availability/building/

This is a...

[ ] Feature Request
[ ] Bug Report

Problem:
Proposed Solution:
Page to Update:
https://kubernetes.io/...

@MOHAMMAD-SHAMSHAD, can you clarify what's the issue and link the page?


how i can send Dom7.ajax request  with async=false?

if send request as async:false then warn
[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its... bla bla bla.
And yet, there are cases when there is a need for a synchronous request.
What solution is there?

async:false is a depreciation of w3c, no relation with this framework.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help http://xhr.spec.whatwg.org/


登录失败，ping不通

Token登录失败： Post "https://auth.aliyundrive.com/v2/account/token": dial tcp [2408:4000:200::1c8]:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
登录失败
还有救吗

wifi可以ping通，校园网网线Ping不通是为什么呢。


Is there anyway to not to repeat "consumes" and "produces" formats?

Above all my REST endpoints, I have something like this:
#[api_v2_operation(consumes = "application/json", produces = "application/json")]

Is there anyway of setting them globally to not to mention them on every endpoint?

consumes and produces can be specified at the root level. With #219, it will be possible to modify the root schema.

So you mean I can use that new feature to develop this feature? Or is it already possible? :confused:

OK, I could make it work. Thanks @wafflespeanut
For people who'll reach here.
Additional to the example in #219 ticket, to set the defualt consumes and produces types, you can define something like, and then pass the spec to the wrap_api_with_spec function:
    let mut json = BTreeSet::new();
    json.insert(MediaRange(mime::APPLICATION_JSON));
    spec.consumes = json.clone();
    spec.produces = json;


Added definition_order parameter to CrossSelector

Right now you can't specify any chosen ordering in the selected list on the right side of a cross-selector as the filtering forces the items into the definition order for options. Note that when you set the order via value, the widget temporarily accepts the chosen ordering before reverting to definition order.
In some situations, you want to specify the ordering of the selected list based on the ordering you add/remove items to/from it. This PR adds a definition_order parameter that you can set to False to allow this use case.
I'm not entirely sure that self._lists[selected].values is the right set of values here but it does seem to work correctly in my (limited) testing. At the very least I no longer see the reordering back to definition order.

Two comments:

If you add options dynamically do we need special handling to ensure that this option is respected?

I'd like to see a test.

If you add options dynamically do we need special handling to ensure that this option is respected?

I don't think so. Adding options dynamically seems to work though any selection is cleared (true before this PR as well).

I'd like to see a test.

Agreed.

To recap the behavior I observed prior to this PR (and that is still present):

Adding to the options dynamically resets any selection even if the selected items are members of the new options.
Shrinking options does seem to filter out the selection on the right side without deselecting them and moving them to the left side.

The former point is probably a bug but I think the fix is outside the scope of this PR.

Looks good. Happy to merge.


[Feature Request]: Registration Functionality

Describe the bug
There is no dedicated registration page for new users to sign up.
To Reproduce
Steps to reproduce the behavior:

Go to the application.
Look for a sign-up or registration option.
Notice the absence of a dedicated registration page.
See the inability for new users to create an account.

Expected behavior
Create a registration page where new users can enter their details to sign up for an account.
Screenshots

Additional context
I am SSOC'24 Contributor.

@Niharika0104

duplicate #26


Only upload one file

I want thew plugin to behave exactly like a single file field. Thus if you choose a file a preview appears and then you choose a file again, instead of a second preview appearing it overwrites the first one. I'm using this for a avatar uploader and it doesn't make sense to be able to upload multiple avatars.

Hey,
has anyone figured this out yet? I was trying to do the same thing and came up with a solution that works, but it's a bit hacky, so please feel free to post a better way.
I couldn't find a way to clear the upload queue before adding a new file, so what I did is adjust the preview manually in the add callback and only submit the last file that was added by unbinding all previous click events from my submit button (I'm using the basic version of the plugin).
add: function (e, data) {

        //show file preview (overwriting previous preview)
        $.each(data.files, function (index, file) {
            $('.file_preview').html('<p>'+file.name+'</p>');
        });

        //unbind existing submit triggers, because we only use the file that was selected last
        $('.start').unbind('click');

        //bind submit to start button
        $('.start').click(function(){
            jqXHR = data.submit();
            return false;
        });
    }


Call markdown-link-check with a list of files

I would be nice (and improve Mega-Linter performances regarding markdown-link-check) if the CLI could take a list of files as parameter
Today, we can call  markdown-link-check "./README.md" , as described in the documentation
With such evolution, we could call markdown-link-check "./README.md" "./CHANGELOG.md" "./docs/index.md" ".docs/other.md"

This is a duplicate of #78

This is a duplicate of #78

oops sorry :)

oops sorry :)


Investigate building on Windows with Visual Studio 2015 Update 2

The standard Visual Studio 2015 image breaks the Windows build on AppVeyor because somewhere in the Windows SDK AgileRef is not being properly declared. It should be defined in <wrl\client.h> The issue is similar to an old Chromium issue here.
AppVeyor saw other compiler errors due to updates to the Visual Studio 2015 image and began enabling the older Visual Studio 2015 Update 2 image for specific accounts that requested it in this Github issue.
We may want to do the same since Chromium uses Visual Studio 2015 Update 2 so NXT should build with the same version.

Chromium doesn't use MSVC anymore, so the limit is now whatever AppVeyor supports, which compiles already.


Supply Content.json for iOS

Images.xcassets didn't exist for me. First I created it manually. Later I realized that migrating to asset catalog inside xcode created these folders.
Created a new project just for getting the Content.json (so I didn't have to do it manually)
However, I discovered that some of the icons and most of the splash screens aren't mapped by the default Content.json generated by xcode (because filename isn't specified)
Now I'm still having to do it by hand...
And if all this is soved by doing it in another order or something then it would be nice to have it written in the readme

In case it's helpful
Contents.json.zip

What cordova version are you using?
When using the library, I don't have to write anything manually. Xcode just finds icons automatically, since they are in the good folder.

I haven't updated to the latest major version of cordova yet. I think the problem for me was that the folder you talk about didn't exist already and then it only mapped some of the images
I'll check what version exactly when I get back on monday

Version of cordova is 5.4.1


add msr-tools dep

Please add the following dependency to the rosdep database.
Package name:
msr-tools
Package Upstream Source:
https://github.com/intel/msr-tools
Purpose of using this:
read and write to CPU registers. useful for debugging and performance improvement.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

i don't have a debian machine

Ubuntu: https://packages.ubuntu.com/

msr-tools

Fedora: https://src.fedoraproject.org/browse/projects/

IF AVAILABLE

Arch: https://www.archlinux.org/packages/

IF AVAILABLE

Gentoo: https://packages.gentoo.org/

IF AVAILABLE

macOS: https://formulae.brew.sh/

IF AVAILABLE

Alpine: https://pkgs.alpinelinux.org/packages

IF AVAILABLE

NixOS/nixpkgs: https://search.nixos.org/packages

OPTIONAL

thank you @cottsay!


Send non-target extra variables to Listener's asyncMethod

Proposal
I wanted to propose the definition of an extraVars array that would send these variables together with the targets array in the Listener and listener_controller, so that the fields specified in the extraVars array would not be listened to, but merged with the targets array and sent back to preserve the original query parameters (while updating the respective targets field that triggered the asyncMethod).
Example
Let's say I define the targets array in SomeListener like so
class SomeListener extends Listener
{
    protected $targets = ['input3'];

    protected $asyncMethod = 'someAsyncMethod';

    ...
}

Problem is I have 3 inputs grouped in the same Layout so if I change input3 (triggering the Listener) after filling in input1 and input2 both of them would be reset because I didn't listen all 3 of them.
// App\Orchid\Screens\SomeScreen
class SomeScreen extends Screen
{
    ...

    public function someAsyncMethod(string $input1 = null, string $input2 = null, string $input3 = null)  {
        return [
            'input1' => $input1, // null
            'input2' => $input2, // null
            'input3' => $input3, // 'some string 3'
        ];
    }
}

// App\Orchid\Layouts\SomeLayout
class SomeLayout extends Layout
{
    ...

    protected function fields(): iterable
    {
        return [
            Input::make('input1'),
            Input::make('input2'),
            Input::make('input3'),
        ];
    }
}

Now using the proposed logic, I'd set the extraVars array and set both the input1 and input2 with it
class SomeListener extends Listener
{
    protected $extraVars = ['input1', 'input2'];
    protected $targets = ['input3'];

    protected $asyncMethod = 'someAsyncMethod';

    ...
}

With that input3 remains being the only target for the Listener to trigger and the fields specified in extraVars are reassembled in the asyncMethod
class SomeScreen extends Screen
{
    ...

    public function someAsyncMethod(string $input1 = null, string $input2 = null, string $input3 = null)  {
        return [
            'input1' => $input1, // 'some string 1'
            'input2' => $input2, // 'some string 2'
            'input3' => $input3, // 'some string 3'
        ];
    }
}

Does $extraVars work with Matrix field? Seems it doesn't join the matrix value at all?
Thanks!

@plamenradev I will look into it and let you know within the next few days. If necessary I'll add another PR to address your use case.


hardware: Add 3d printed case

Here is the design files for a basic 3d printed bottom case.
I think this will work with all the revisions. (Might need a slight change for USB-C)
Let me know if the names and folder structures are ok.
Files included:

.stl for direct 3d printing
.iegs for modifiying or altering the design.
.png preview image

It looks like this when assembled, it just helps to protect the exposed pins on the PCB.

it just helps to protect the exposed pins on the PCB.

I think this is a very good case personally; I've been heavily using it on a very cluttered desk full of electronics and random junk, and I think it has almost completely eliminated the hazards associated with that. So while it may seem "incomplete" because it only partially covers the board, I find it more than sufficient for daily use.

Let me know if the names and folder structures are ok.

Mostly ok, I would prefer a path like 3d-printed-base because spaces in filenames sometimes cause issues, but I can rename myself.

Neat. I can rename the folder and I'll also add the .f3d source file, shortly.

Thanks!


allow for base64 strings for plugin icons

This is a prerequisite for #140 (app search).
This PR will allow base64 strings for icons.

Coverage increased (+0.03%) to 88.92% when pulling 111c752ba7be168684d4b4f8328791b4d5bd3a47 on allow-base64-icons into 04ae300900b1ec9102665ee767ef9ed40453a4a0 on develop.


allow to search presets by tag

Some people might remember a preset by its OSM tag, or want to look up a preset which matches a tag documented in the OSM wiki.
The preset search bar could show presets if (one of) their tags matches the entered search text (e.g. landuse=railway should match the Railway Corridor preset). This could also be relaxed to match any one or two word input which corresponds to an OSM tag's key and/or value.
See https://github.com/openstreetmap/id-tagging-schema/issues/301

The search results already include matches based on the value, but not the key=value syntax:
https://github.com/openstreetmap/iD/blob/fc6c71160c6378fa16e70436304a3e3d6fdb30e2/modules/presets/collection.js#L124-L126


add RGPR data augmentation for person reid

Add RGPR data augmentation for person reid(An Effective Data Augmentation for person re-identification(https://arxiv.org/abs/2101.08533))
mgn_repvgg_wo_RGPR(epoch 60):
rank1: 90.44, mAP: 81.56
mgn_repvgg_w_RGPR(epoch 60):
rank1: 90.66, mAP: 82.16
mgn_repvgg_w_RGPR(epoch 120):
rank1: 91.07, mAP: 82.18

Thank you so much! Did you have experiment results with resnet50?


kubectl zsh completion cause directory path completion has extra space

Is this a BUG REPORT or FEATURE REQUEST? : BUG REPORT
Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: Aliyun ECS
OS: Ubuntu 16.04.4 LTS
Kernel: 4.4.0-105-generic
Install tools: zsh 5.1.1

What happened:
When hit tab to complete a sub directory path, zsh added an extra space after the directory path.
It causes press tab repeatly to complete additional path impossible.
What you expected to happen:
Like bash completion, only file completion with extra space, there should be no space after directory.
How to reproduce it:

Says there is a file foo/bar.yaml;
Typing kubectl apply -f f, then press tab;
It complete with foo/<space>, instead of foo/;
I need to delete this extra space, then press tab again to complete the file bar.yaml。

But there is another situation working correctly.

Same as ~/foo/bar.yaml;
Typing kubectl apply -f ~/f, then press tab, it finished with kubectl apply -f ~/foo/.

Anything else we need to know:
From debug log,  I got this for f completion.
_filedir @(json|yaml|yml) cur=f
RET=foo len=1

Got this for ~/f completion.
_filedir @(json|yaml|yml) cur=~/f
RET= len=0

It seems there is something different in RET=( $(compgen -f) ) of completion.go.

Any update on this?

/sig cli
/area kubectl
/kind bug
/priority P2

Can also reproduce on the below environment.  Similar to the working situation above with the tilde, autocompletion ofkubectl apply -f ./f does not cause this issue.
Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-30T21:39:38Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"darwin/amd64"}

Environment:
OS: macOS Mojave 10.14.1
Kernel: Darwin Kernel Version 18.2.0: Fri Oct  5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64
Install tools: zsh 5.6.2

/remove-lifecycle stale

A workaround for me is to just remove kubectl's completion for the "-f" flag and let it fallback to the standard zsh file / path completion.
I used
source <(kubectl completion zsh | sed '/"-f"/d')

instead of
source <(kubectl completion zsh)

/remove-lifecycle stale

/remove-lifecycle stale

Same issue here

Same issue here

/remove-lifecycle stale

Same issue here.
kubectl version info
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T23:41:24Z", GoVersion:"go1.14", Compiler:"gc", Platform:"darwin/amd64"}
zsh version info
zsh 5.8 (x86_64-apple-darwin19.3.0)

I have filed a PR https://github.com/kubernetes/kubernetes/pull/89479 to fix this issue, please give it a try and feel free to tell me any problem you encountered.

/assign knight42

A workaround for me is to just remove kubectl's completion for the "-f" flag and let it fallback to the standard zsh file / path completion.
I used
source <(kubectl completion zsh | sed '/"-f"/d')

instead of
source <(kubectl completion zsh)

I had to do the following, I just replaced with foo cause I was a bit frustrated
in this file
 ~/.o/p/k/kubectl.plugin.zsh
 if (( $+commands[kubectl] )); then
     __KUBECTL_COMPLETION_FILE="${ZSH_CACHE_DIR}/kubectl_completion"

     if [[ ! -f $__KUBECTL_COMPLETION_FILE || ! -s $__KUBECTL_COMPLETION_FILE ]]; then
         kubectl completion zsh >! $__KUBECTL_COMPLETION_FILE
     fi

vim ~/.oh-my-zsh/plugins/kubectl/kubectl.plugin.zsh

Change
kubectl completion zsh >! $__KUBECTL_COMPLETION_FILE

->
(kubectl completion zsh | sed "s/kubectl_apply/foo/g") >! $__KUBECTL_COMPLETION_FILE

then
rm ~/.oh-my-zsh/cache/kubectl_completion

then start new shell


NORMALIZED_NUMBER

Add a options to get NORMALIZED_NUMBER on Android.
Numbers on E164 format and commonly used on most application and Android gives it for free.
We should have a option to retrieve it.

please review https://github.com/rt2zz/react-native-contacts/pull/353 and let me know if it works


Step-into behaves as step-over

OS: ubuntu22.04 wsl and ubuntu22.04 on a x86_64 server
VSCode version:  1.77.2
CodeLLDB version: 1.9.2
Compiler: gcc
Debuggee: python3 native lib (such as tvm)
lldb-version:  16.0.0-custom

lldb always step over function calls, whether using the step-into button in the debug panel or using the "step" command on the command line. I cannot jump into the function, but it can stop at the breakpoint in the function.
these are my launch.json
        {
            "type": "lldb",
            "request": "launch",
            "name": "lldb test_conv2d",
            "program": "python3",
            "args": [
                "-m",
                "pytest",
                "-v",
                "test_conv_my.py"
            ],
            "cwd": "${workspaceFolder}/tests/st/ops/mytest",
            "env": {"LD_LIBRARY_PATH":"some ld path",
                    "PYTHONPATH":"some python path",
                },
                "initCommands": ["settings set target.process.thread.step-avoid-regexp ''"]

        }

Does it work in CLI lldb?

you mean using lldb in command line?

I have tried to use lldb to debug python native lib in command line and it also step over function calls.. Is it possible that this is a bug of lldb ？

Not sure if lldb bug or if something's wrong with your debug info.
In any case, I don't think this is caused by this extension.


Disable automatic Publish to PyPI

hey @AakashGfude not sure how this works -- but perhaps we should disable any automatic publishing to PyPI for now.

@mmcky, sure. I have not set up publishing to pypi yet in this repo. That CI hook. was not working anyways. you reckon I should remove that altogether from the CI?

Roger that -- Yeah let's comment it out for the time being (or remove) and document here. I imagine we will need to configure tokens etc. But let's not worry about that now.

removed in this one https://github.com/QuantEcon/quantecon-book-theme/pull/3 .


Add assertions to prove that scene2d code is on the GL thread

This was something I've been wanting to do for a bit now. A lot of code in LibGDX is unsafe to be called anywhere other then the GL thread, which generally is quite manageable, but when you have enough callbacks/helpers it's quite easy to start calling things from threads other then the GL thread, which can lead to race conditions causing crashing within the GL thread. This adds assertions (that you would have to enable when launching the JVM), that would catch the call to manipulate an object from somewhere other then the GL thread. Because they are completely ignored if they aren't enabled on JVM launch there should be no performance penalty during normal usage, but would make it much easier to track down this class of error when needed.
As an example of what of these assertions would look like when tripped:
Exception in thread "Thread-31" java.lang.AssertionError: Not on the GL thread
        at com.badlogic.gdx.scenes.scene2d.ui.Label.setText(Label.java:108)
        at com.badlogic.gdx.tests.LabelTest$1.run(LabelTest.java:141)

To do this I added a isGLThread() helper on the Graphics object that the asserts can use. I've only been able to test the Lwjgl and Lwjgl3 backends thus far, and will need help with the iOS and GWT backends. (I can test the Android one, but haven't gotten to it yet).
I'd like to extend this to a lot more of the scene2d code at a minimum, but before going further wanted to send in this prototype to get people's opinion.

Creating an static method (assertOnGlThread?) which contains the assert might be better for less code duplication. And the performance impact should be non-existent, since it will be very easy to inline an empty static method.

It would probably be better to implement this functionality in an external java agent.
I've added a quick implementation that matches the functionality of this PR (Except a warning instead of a fatal error) to https://github.com/PokeMMO/gdx-dbgagent

@PokeMMO great idea!

Even if we decide this belongs in an external tool, there is some benefit to be had to adding a custom annotation to methods in libgdx's source code. Maintaining a list of methods externally is much more fragile.

Yeah, I hadn't really considered a java agent for this either, I still need to try out what @PokeMMO linked, but on first glance it's probably a lot better :)

I think its much better to have this externally.  Where some higher level annotation system might be nice, its also very subjective as to what should get this treatment, and I think best being able to be configured on a per dev basis in some external agent.


Test coverage data not available if test run is using entirely-cached data

First of all, awesome plugin! It works really well.
The only issue I am experiencing is w.r.t. test coverage, if >= 1 test is being re-ran, it will correctly display the test coverage. If fully built from cache, it incorrectly displays the (lack of) code coverage.
Example if re-running >=1 test

Example if running entirely off of cache

Would be good to have a fix! Let me know if I can help.

@jpabeem I'll take a look tonight. And thank you for the feedback!

Jesus this auto-close, gonna have to take a look into those settings too. Anways jpabeem, can you bump the version to 0.3.2 and try?

Haha no worries. Awesome!! Thanks a lot for the quick triage + fix.
I have to wait a few days before I can consume this as we have a small lag internally, but will report back.


New-GSCalendarACL DisableNotifications switch

Fix for Issue #320
Added a new switch parameter to New-GSCalendarACL called DisableNotifications. When present it will prevent notifications being sent to users affected by the calendar sharing changes.
Seemed like a simple addition so I gave it a go. I am still learning how Git works though so hopefully I did everything correctly.
Thanks

Hi @scrthq
Thanks for the feedback that makes perfect sense and I will keep that in mind for the future.
I have pushed another commit that incorporates your suggested change.
Thanks!

Thanks @FISHMANPET. I am new to Git and still learning my way around it. I will have a look when I can and fix this up.

Hi @FISHMANPET. I have reverted the commit. Let me know if anything further is needed.


Insert helpful pull request name here

bro camellia goes hard

@Naquino14 pls revuew k thx

@Naquino14 ok

@Naquino14 it looks good

@Naquino14 great! Thank you for reviewing

❌ Deploy Preview for jovial-llama-14cbc3 failed.


Any thoughts on support WASM extensions?

Are there any thoughts on how to handle WASM extensions?
If an extension is implemented should it be always on or behind some sort of "feature flag" mechanism?

I'd love to support some of the extensions, though I don't think I'll have the time to work on any soon. I think in cases where an extension might change the behaviour or perf characteristics of compiled WASM, we'll have to make the extensions opt-in. But, I haven't been following closely enough so I don't know if there even are extensions like that. For example, I think the tail call extension just adds new call and return instructions to support tail calls.

Thanks for the reply.  I have been thinking about hacking on the vm a little and wanted to make sure I didn't do anything you may hate 😄


fix: default org only token url

Summary
The default path for the API to retrieve the runner token was calculated incorrectly including 'repos' instead of 'orgs' which causes the token retrieval to fail.
I'm guessing at some point github changed their API from https://api.github.com/repos/$org_name/ to https://api.github.com/orgs/$org_name/ which broke the behavior of the token_url when no repo is specified.
Fix Details

Changes the token_url calculation logic in the instance defined type to correctly use orgs when no github.com api string override is provided.
Adds some quick and dirty test code to make sure the creation script is built as expected.

Closing this PR in favor of #32


Lint toml with taplo

Thought it would make sense to lint & tidy up our toml files. If you're using VSCode then the tamasfe.even-better-toml extension will auto-format it for you

Good idea. I don't like how it tries to align comments for features, but otherwise it seems great.

It's way nicer in the cases of comments on multiple features or a comment after a short feature next to a long one, e.g.
"some_really_long_feature_name",
"x11" # gh actions runners don't like wayland

But yeah, definitely looks a little odd when there's nothing super close it's being aligned to


Update to rspec 3 format

Description
This repo currently uses rspec 2, which requires an old rake release that contains a CVE. We should get onto rspec 3, but this requires updating an old "should" format test.

I should probably include this change in #10 that's dealing with similar updates.


Update NPSP to get combined TDTM config if Advancement installed

This issue is created for support Advancement from NPSP.

**lurch: attach W-021135

Tracking W-021135

Included in beta release 3.126 (Beta 4)

Included in production release rel/3.126


German Keyboard Design

German keyboard design
https://www.figma.com/file/AzpS9d5OtP09SWBsUzedv6/Localization?node-id=2%3A904

Done in #143


Support for Phi-3-mini

If it is possible to support Phi-3-mini, please.
Thank you.

Hi there! Unfortunately I don't plan on actively supporting this repository (including adding support for new models), as it's meant to accompany the paper and support reproduction of the results. If you'd like to apply the method to new models, I suggest forking the repository and then making the appropriate changes there. Feel free to email me at<EMAIL_ADDRESS>if you have questions about how to do this.


[Proposal] @spaceless / @endspaceless keywords

I'm currently porting a Symfony/Twig project to Laravel/Blade, and I think it misses a tag to remove spaces between HTML tags on some parts of code.
For example, given this code:

Item 1

Item 2

Item 3

Item 4

If
 elements are inline-block with a 250px witdh, and
 is 1000px width, then the fourth element will not fit in the container, because of the spaces between tags.
Twig provide a way to handle this situation: the {% spaceless %} and {% endspaceless %} tag, which removes all spaces between HTML tags of the targeted block.
I created the same @spaceless and @endspaceless keywords with Blade::extends, but I think it could be usefull to pull this directly in the core Blade compiler.

Where to place Blade::extend in Laravel 5: http://stackoverflow.com/a/28641054/1331425


remove mcvine dependency

The current mcvine-related code is only used to reduce the nxspe/nxs files to IQE spectra. These code can be simply pulled into multiphonon.

@jniedziela requested this


New version: StochasticRounding v0.3.2

Registering package: StochasticRounding
Repository: https://github.com/milankl/StochasticRounding.jl
Created by: @milankl
Version: v0.3.2
Commit: 80c0deac4c7e93ef58a0c79682e97b631ccd4e1d
Reviewed by: @milankl
Reference: https://github.com/milankl/StochasticRounding.jl/issues/26

block


Fix errors in packages tests

[Linux/macOS] Fix data races:
Added channel to watcher structure so that
the watcher.Close function can safely wait
until the goroutine is done and avoid data
races that could occur with just the mutex locks.
[macOS] Fix json_test and watcher_test in packages:
The way FSEvents handles events we need to use the
flushDir function or the notify framework won't
generate events for files if the directory had already
files watched inside.
The flushDir was being called at the end of the Watch
method and therefore it wasn't executing in some cases
where the method was returning before the call.

Hopefully tests should all pass with these fixes in Linux and macOS and then we can keep them clean and I can start working in actually implementing some features.

Ok... this didn't go as planned 👎  any idea why the linux build can be failing on this change and not in https://travis-ci.org/limetext/backend/jobs/172770715?

I found a different approach to the race conditions and discovered that the kqueue backend for the notify library works better in macOS

Interesting. I don't like the idea of being forced to use tags, we can almost install LimeText by just doing go get github.com/limetext/lime-qml... But I guess Mac users are going to need a different build step anyway. It might be a good idea to do OS detection on the tags to make it clear that they are only for Mac.

When I get more time I will try to narrow down the problem so I can create an issue in the notify project to fix the FSevents implementation.
The notify package already checks forbthe architecture and only uses the kqueue tag in darwin. But I agree it should be mote visible I'll try to sort out the OS checks in the Makefile this week.

Changes Unknown when pulling c3302081ec43b86691d323d0f0195009d2306c7f on fmanno:fix-packages-tests into ** on limetext:master**.

Last commit makes the tags only applied in case of Darwin systems (kqueue is the default otherwise even in mac systems)

Changes Unknown when pulling 5b3e3598000875ef22ec2a39b9332735c228b0cf on fmanno:fix-packages-tests into ** on limetext:master**.


Blank dialog content

When I use the maven release 2.0.3, it works fine.  When I clone the repo's develop branch, and try to run the preferencesfx-demo, I get blank content in the preferences dialog as shown below.  I get the same for all of the demos.

Running on JDK1.8u141

Last good version seems to be https://github.com/dlemmermann/PreferencesFX/commit/5c942dc13e33418b3e7c6f9e851c4c60de7ad7a3


SubscriptionRequestsThrottled error

It would be nice to have some sort of information for the error SubscriptionRequestsThrottled. Even just linking to here, https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/request-limits-and-throttling would be nice.
An example would be Number of requests for subscription 'subid' and operation 'POST/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.COMPUTE/VIRTUALMACHINES/START' exceeded the backend storage limit. Please try again after '6' seconds.

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

ID: bc2ab43e-b864-aabd-9952-798e2af66264
Version Independent ID: 7064e4cd-4e84-0597-400a-71698b16bc6e
Content: Troubleshoot common Azure deployment errors - Azure Resource Manager
Content Source: articles/azure-resource-manager/troubleshooting/common-deployment-errors.md
Service: azure-resource-manager
Sub-service: troubleshooting
GitHub Login: @davidsmatlak
Microsoft Alias: davidsmatlak

#assign:davidsmatlak

@jgross-njnc Thanks for the feedback. I'll add the error code and link to the article.

Hi there, David. Thanks for looking into this. I was surprised it wasn't mentioned there at all but easy enough to add the error and that link.
Best regards,
Justin Gross
From: David Smatlak @.>
Sent: Tuesday, February 14, 2023 10:55 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Justin Gross @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] SubscriptionRequestsThrottled error (Issue #105248)
@jgross-njnchttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjgross-njnc&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Z5WJi2OwbDheAXgKxaZ2ozkQYq7e%2Bk1WgyKD9eDTqeA%3D&reserved=0 Thanks for the feedback. I'll add the error code and link to the article.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F105248%23issuecomment-1429975659&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dpx3FAolxBXaH0pXQfojpLVF0gjKQlgklcXITHsZKcs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA2IZC5OOVSCJEN6AQQ557CTWXOTG3ANCNFSM6AAAAAAU3XA5Q4&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JV0HNJYr%2FcIEVdcZizFHwebH9FuK3cwsY%2BXmYO5n114%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

David,
Maybe this page is better to link to or both? Troubleshooting throttling errors in Azure - Virtual Machines | Microsoft Learnhttps://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshooting-throttling-errors. Also, I see that this error is not listed on this page either, Common VM error codes in Azure - Virtual Machines | Microsoft Learnhttps://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/error-messages, so I guess that I will put feedback there as well.
Justin
From: David Smatlak @.>
Sent: Tuesday, February 14, 2023 10:55 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Justin Gross @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] SubscriptionRequestsThrottled error (Issue #105248)
@jgross-njnchttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjgross-njnc&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Z5WJi2OwbDheAXgKxaZ2ozkQYq7e%2Bk1WgyKD9eDTqeA%3D&reserved=0 Thanks for the feedback. I'll add the error code and link to the article.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F105248%23issuecomment-1429975659&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dpx3FAolxBXaH0pXQfojpLVF0gjKQlgklcXITHsZKcs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA2IZC5OOVSCJEN6AQQ557CTWXOTG3ANCNFSM6AAAAAAU3XA5Q4&data=05|01|justin.gross%40microsoft.com|c05fd7a1e0af4783bad008db0ea3e351|72f988bf86f141af91ab2d7cd011db47|1|0|638119869279544929|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JV0HNJYr%2FcIEVdcZizFHwebH9FuK3cwsY%2BXmYO5n114%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

I added the SubscriptionRequestsThrottled error code and links. The content is scheduled to publish after 4pm today.


[iOS][MapView] Support for changing annotation image

Any plan for allowing change of annotation image on the mapview?

I'll let @tadeuzagallo answer and close this (based on git blame).

+1

I got this working locally, would a PR be accepted/entertained for this?

If you want this to work with local xcassets imagery:

In RCTMapManager.m, change:

MKPinAnnotationView *annotationView = [[MKPinAnnotationView alloc] initWithAnnotation:annotation reuseIdentifier:@"RCTAnnotation"];
  annotationView.animatesDrop = annotation.animateDrop;

to
MKAnnotationView *annotationView = [[MKAnnotationView alloc] initWithAnnotation:annotation reuseIdentifier:@"RCTAnnotation"];
  annotationView.image = annotation.image;

In RCTPointAnnotation.h add:

@property (nonatomic, copy) UIImage *image;

In RCTConvert+MapKit.m , in the PointAnnotation portion add:

shape.image = [UIImage imageNamed:[RCTConvert NSString:json[@"image"]]];

In a proper PR I would imagine you'd want to account for external images and non-existince of the image prop and then default to MkPinAnnotationView.

Feel free to send a PR and assign to me.
As for missing images, using [RCTConvert UIImage:] should do all the necessary checks.


fix(multiprocessing): Make close() call the next steps close()

We are missing the call to next step's close() call in multiprocessing. In cases where the next step is Produce the consumer just hangs because the shutdown flag is not set.

@untitaker @lynnagara - Is calling next step's close() method incorrect here? The tests seem to be failing which is a bit surprising. Before I start digging into the test failures I would like to know whether what the PR is proposing is correct or not. For context: @phacops PR for ingest spans consumer test gets hung right now. Specifically this test https://github.com/getsentry/sentry/pull/54154/files#diff-0626054a3c2af5ad276c422567321f4bc326b8b091ff13e652c34f4560396e79R14. I narrowed it down to the KafkaProducer being stuck in this while loop forever because it never gets called with close(). The strategy for reference is here

I tried this fix but it doesn't seem to fix the issue unfortunately, still stuck in this loop.

next_step.close() is already being called in join. We can't call it here because then we wouldn't be able to keep forwarding remaining messages to the next step during shutdown

I found the problem. The Produce strategies join() does not call the producer's close(). Since the producer is running in a different thread and it's close method is not called, the thread hangs which causes the program to not terminate.
@phacops - Can you test this fix with your PR?

The fix in this PR works for the issue I'm facing.
@lynnagara I'd love if I didn't have to pass a producer to the Produce step in that case. As a user, I don't really want to be responsible but a Producerthat I then have to close "properly".


[QUESTION] Is this project still active?

It has been one year since the last commit. Telegramm API is on its 4.9 version right now. Is there any interest in keeping this project up-to-date?

Any updates on this?

Wondering about this also.

It seems the answer is no, too bad. I’m still using this one, but maybe should investigate https://github.com/fizruk/telegram-bot-simple instead.


fix: docs build command

Closes #728

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.62%. Comparing base (63ea7a7) to head (1a588cc).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #729   +/-   ##
=======================================
  Coverage   92.62%   92.62%
=======================================
  Files          71       71
  Lines        7955     7955
=======================================
  Hits         7368     7368
  Misses        587      587

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


Fix mismatched types when compiling for arm

Fixes #22

Actually it's worse than I thought.
https://github.com/rust-lang/libc/issues/1036
The underlying issue here is that musl defines the signature for ioctl like this:
int ioctl(int fd, int request, ...);
Whereas glibc defines it like this:
int ioctl(int fd, unsigned long request, ...);
Newer versions of nix provide macros that appear to work around this issue, as long as we don't do things like explicitly cast  as ::libc::c_ulong


Why not using 512 x 384 images of koniq10k to avoid resizing?

Hi, thanks for your IQA work!
I noticed that you resize the input image of koniq-10k dataset.
Since there are two resolutions of data in koniq-10k dataset, if you use 512 x 384 as input size, why not using 512 x 384 image size provided by koniq-10k ?

Sure you can use 512x384 images for directly training, it's just because we only downloaded the images of 1024x768 resolution...

@SSL92  ok thanks for you response.


feat(types): add nuxt error type

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

This add type for Nuxt error with interface NuxtError.
With that on error layout we can now use :
import { Component, Vue, Prop } from 'nuxt-property-decorator'
import { NuxtError } from '@nuxt/vue-app'

@Component({})
export default class ErrorPage extends Vue {
  @Prop({ required: true }) readonly error!: NuxtError;
}

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

@orblazer Isn't it related to https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/types/index.d.ts#L71 ?

Yes @kevinmarrec we probably can merge the 2 interface et keep the name NuxtError

@orblazer Alright, agreed. I would just want to know how you found the path property if you can link me code or documentation. Thanks in advance.

@kevinmarrec I have found path here : https://github.com/nuxt/nuxt.js/blob/31f5729828e1009a6db28fe90296c178451f9efd/packages/vue-app/template/server.js#L83

@orblazer Alright, then I'd say we can remove ErrorParams in favor of  NuxtError. Then do
export interface NuxtError {
  message?: string
  path?: string
  statusCode?: number
}

Comparing to your changes, notice statusCode as number and the alphabetical order of properties.

And also change Context.error signature to
error(error: NuxtError): void

Codecov Report

Merging #5950 into dev will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #5950      +/-   ##
==========================================
- Coverage   95.72%   95.68%   -0.04%
==========================================
  Files          82       82
  Lines        2689     2689
  Branches      690      690
==========================================
- Hits         2574     2573       -1
- Misses         97       98       +1
  Partials       18       18

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.35% <ø> (ø)
:arrow_up:

#unit
92.67% <ø> (-0.04%)
:arrow_down:

Impacted Files
Coverage Δ

packages/vue-renderer/src/renderer.js
93.49% <0%> (-0.82%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM, thanks for the types improvement @orblazer


⚠ Bofrost.at has degraded performance

In 8e8a426, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1117 ms

Resolved: Bofrost.at performance has improved in f24fb6f after 6 minutes.


bug:  cant find jellyfin paths

Description of the bug
After you helped me earlier to get the trigger setup I am seeing the following error ERROR autopulse::service::targets::emby: unable to find library for file: /media/Media/Video/TV/Regular/show/episode.mkv
sorry to keep bothering you.
Steps To Reproduce
add new download to sonarr and let it finish.
Additional Information
No response

Description of the bug
After you helped me earlier to get the trigger setup I am seeing the following error ERROR autopulse::service::targets::emby: unable to find library for file: /media/Media/Video/TV/Regular/show/episode.mkv sorry to keep bothering you.
Steps To Reproduce
add new download to sonarr and let it finish.
Additional Information
No response

Can you post your config?

I just changed the rewrite section to what you see in the config now. I "think" it may be working because i now see a couple "completed" items on the webui.
https://pastebin.com/QRXnUtVL

Your rewrite should be from where the file is before it moves to the folder where jellyfin will see it. So if a TV show is in /media/Media/Video/TV/Regular before it moves to  /media/TV/Regular and jellyfin reads TV shows from  /media/TV/Regular then that's correct

oh ok, so in my case it starts off in /media/Media/Downloads/Torrents/sonarr-tv. So that would go in the top one. got ya.

oh ok, so in my case it starts off in /media/Media/Downloads/Torrents/sonarr-tv. So that would go in the top one. got ya.

Yes, for example mine is /volume1/data/torrents/tv and from there it goes to /volume1/data/media/tv

ok, so i put that into the config and it is giving the error again.

Can you join the discord? and I can try my best to help https://discord.gg/fYvSNCHx


Window Shortcut Tweaks

Primarily a triggered global shortcut while the hain window is already open will no longer close it.

@cpriest, it seems that your formatting rules isn't same with the old one. especially, the vertical alignment generates unnecessary changes to commit.
in my opinion, it's better to follow the old one. or we can make the new one.
how do you think?

for now, i reverted the formatting to follow eslint config, editorconfig at 3b44ee56cc0a7dae7fe521c02fec52e8215d832e, but i'm not saying this is the best.

No problem, I had not setup eslint checking in my IDE before I had sent that in.  I have it setup now (though some of the other files have eslint violations.  I modified the eslint a bit to allow for the violations, they would be "no-restricted-syntax": "off", "no-multi-spaces": "off," that fine?

@cpriest That is fine :+1:
One thing to note is that package.json should not be formatted manually. (npm will do it)

and i have a question, why do you remove toggle function for the shortcut?
I thought it's useful. so i think it's better to make an option to disable it.

Well if I'm pressing a global shortcut key, shouldn't it always show the window?  The way it was, if I had the hain window already opened and pressed a shortcut key, it would close the hain window.  Seemed like a bug to me.
The toggle() function is still there, its just that a global shortcut key will always call show() with the query associated with the shortcut key.

then, I'll make an option to switch between toggle and show, because i prefer toggle than show, it can hide the window more faster than pressing esc

Strange, I didn't see your followup comment @appetizermonster, I can add the toggle as well if you can't get to it right away.
I'm working on a solution to indexing control panel items, UWP apps, etc.  What a PITA.


Item search returning bad request.

I'm currently experiencing problems with searching for items. No matter how I format the query, I get a bad request error. Here's the request that I send and the error response that I get:
GET search [type=track,q=Galantis - Firebird,limit=1]
--> BadRequest application/json {  "error" : {    "status" : 400,    "message" : Missing parameter type
"
Here's the call code:
result = await _spotify.Search.Item(new SearchRequest(SearchRequest.Types.Track, query)
                    {
                        Limit = limitResultAmout
                    });
Am I missing something obvious?

Are you on the latest version? 6.0.0-beta.6

This could be related to #461 , where query parameters were not added to the request successfully, depsite them being shown in the log. This has been fixed since version 6.0.0-beta.4

Yes, updating to the latest version has fixed the problem. Sorry for the trouble and thank you for the quick answer.

 ;)
If any other issues arise, feel free to open another issue


How to define a route without the CoreLayout props children?

I need a landing page 。
Visit the home page(path = '/') and check no session will redirection to /login
Do not want '/login' is in the CoreLayout under the props, but a complete page.
eg:
<Router>
    <Route path='/' component="CoreLayout">
    <Route path='/login' component="Login">
</Router>

Hi @onweer,
You should be able to do something like this:
import CoreLayout from '../layouts/CoreLayout/CoreLayout'
import Home from './Home'
import CounterRoute from './Counter'
import Login from './Login'

export const createRoutes = (store) => ([ // now we are passing an array of routes
  {
    path: '/',
    component: CoreLayout,
    indexRoute: Home,
    childRoutes: [
      CounterRoute(store)
    ]
  },
  {
    path: '/login',
    component: Login
  },
])

...

Don't forget to change PropType in AppContainer.js to PropType.array.isRequired
Hope this helps ;)
Best Regards

@bulicmatko Thanks ;) .

@bulicmatko

succress with
export const createRoutes = (store) => ([
  Login(store)
])

@onweer
Glad it helped ;)
Can maybe this issue be closed?


Avoid 6008 error when detecting licenser response is ko

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
2.5.21
Please ask your question
I have a custom license response (DASH-WIDEVINE) that I have to unwrap before giving it back to Player (managing response.data in player.getNetworkingEngine().registerResponseFilter).
But when I detect the response is invalid and so that I know playback will not be possible, I make a player.unload(), that seems to work, but in any case it triggers the onError() function and 6008 is raised. Is there another way to stop properly the Player in that case? Or to says to it to not wait for a response anymore?
The goal is to avoid the analytics player trackers, that listen and report every Player errors, to pollute the metrics, because  finally it's not an error relative to Player itself.
Thanks in advance for your help.

Error 6008 is LICENSE_RESPONSE_REJECTED.  This means you fed some data back to DrmEngine that was not valid.
I would suggest that you try something like this (untested) code below.  In the error case of your response handler, you can use a delay to try to make the cancelation happen before the invalid response is returned.
  if (invalid) {
    response.data = '';
    player.unload();
    // Block the response for 100 ms so that unload() can start tearing down internal components.
    // By the time DrmEngine receives this response, it should be in a state to ignore it.
    return new Promise((resolve) => setTimeout(resolve, 100));
  }

Does this help?

I've just tried and it seems to work fine. Thank you very much!
Just to be sure, the 100ms delay, can it depend of the device performance? I mean should I adapt this if I want to anticipate the clean unload can take more? Or maybe put the return on the promise of the unload ()?


Issue 1 - Grade build file now targets Java 8

This is great @DeaneOC! How about if we edit the CI job to download Java 8 as well?


Features to be restored from pre Qt version

This ticket lists features that have yet to be carried over from pre Qt version. Pre-release 0.3.1
https://github.com/cirquit/trdrop/releases/tag/v03.1

[ ] Save user settings to configuration file
[x] Background Graph Shadow Overlay (Restored in #109)
[ ] Tear Percentage in Framerate Graph

[ ] Video Exporting

All of those except the tear percentage in the framerate graph are on the roadmap for the v2.
Is this really the best way we can visualize tears? Because I feel this is really not easily understandable and visually cluttering.


changes based on the feedback from testing team

changes based on the feedback from testing team

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


Add views for overall audit with primary keys of the datatables

view v_audit_base with audit-columns plus table name, amount of primary keys (pk), sub view reference (e.g. v_audit_pk1)

view 'v_audit_pk0 etc. audit columns plus table name, view name. For tables without primary key.

view 'v_audit_pk1 etc. audit columns plus table name, view name, pk1_name,pk1_values. For tables with one primary key.

other pkX as needed.

veiw 'v_audit_complete' as union of all _pkX-views.

After Implementation the world looks different:

it is v_audit_sequence showing the only the audit transaction hierarchy in a flat table.

There is a view per table,combining v_audit_sequence, the audit header data and where possible the pk1 information.

v_audit_trail is now the complete view to audit trail. It's documented in the wiki ==> DONE!


Wrong path generated for chunked worker files

When a custom path is specified for emitted worker files as follows:
loader: require.resolve("worker-loader"),
options: {
    name: 'static/js/Custom.[hash].worker.js',
    publicPath: "/static/js/"
}
the output is as expected as long as the workers do not have chunked files. However, when they do contain chunks, the output is as follows:
1.08 KB        build\static\js\Custom.1d4ad84aa77f190d8b23.worker.js
717.74 KB      build\1.static\js\Custom.1d4ad84aa77f190d8b23.worker.js
649.83 KB      build\2.static\js\Custom.1d4ad84aa77f190d8b23.worker.js
As seen above, the first non-chunked worker file is placed in the static/js folder as expected but the chunked worker files are placed in 1.static\js and 2.static\js folders respectively.
This occurs because of the following code in index.js:
  worker.options = {
    filename,
   chunkFilename:[id].${filename},
    namedChunkFilename: null,
  };
where the [id] is tacked on in the chunkFilename without accounting for the fact that there may be a custom path specified - as supported by webpack.
This makes it impossible to emit chunked worker files to a desired directory which may be needed to apply caching headers to all static files, for instance.

+1

I'm having the same problem.

+1


Create LICENSE

This project does not identify a license anywhere. This is important, since without a license, you are not sharing the code. Instead, you are only showing it. Under GitHub TOS, users can only view and fork the repository without a license, nothing else.
To avoid this situation, I opened this PR to remind you to add a license (I chose the MIT license for this PR) so others can take this and put it in their own project. Our community pulse (Insights) is less than half finished, so I suggest it gets finished as soon as possible. :)

Just now seeing this. Didn't realize the license thing, thank you!


filter out legitimate Telemetry traffic to avoid false posiitves

https://github.com/reprise99/Sentinel-Queries/blob/d47d4a07fb6aa8601513c03583676ba4329f8799/Defender for Endpoint/Device-msdtPotentialExploit.kql#L89
add line:
| where RemoteUrl !endswith ".visualstudio.com" and RemoteUrl !endswith ".microsoft.com"

Did you want to submit a PR? Happy for you to contribute if you want to, otherwise I can add it

Issue fixed in merge


Add new cache states to determine plugin init

Summary
This expands the cases of using the cache state to determine if a plugin has been initialized or not; an initialized plugin can either be in a "cached" or "disabled" state.
Fixes #10639

Occurred changes and/or fixed issues

Technical notes summary

This also removes the getters for willBeCached() and isCached() as they are unused by Dashboard with this change
noCache can be manually set in the CRD so this isn't a good indicator for determining plugin initialization

Areas or cases that should be tested

Managing plugins should remain unchanged
Installing plugins should succeed when cache is disabled.

Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

What about the pooling mechanism and race conditions mentioned in https://github.com/rancher/dashboard/issues/10639? Do we need to deal with that?

Our current implementation handles the race conditions, but it does so with the assumption that a plugin will always report itself as being cached. This change preserves our current implementation by removing the requirement that a plugin reports itself as cached, instead requiring that it exits a "pending" state.
If we were unable to preserve our current implementation, then I think that we would need to implement a new polling mechanism. I think this approach is much more straightforward 🙂

Also, don't know how feasible it is, but creating a test that cover the installation of an extension bigger than 20mb would be good. Wdyt?

I am open to this. Do we have documentation on how we can publish an extension so that it can be accessed by our e2e tests?

What about the pooling mechanism and race conditions mentioned in #10639? Do we need to deal with that?

Our current implementation handles the race conditions, but it does so with the assumption that a plugin will always report itself as being cached. This change preserves our current implementation by removing the requirement that a plugin reports itself as cached, instead requiring that it exits a "pending" state.
If we were unable to preserve our current implementation, then I think that we would need to implement a new polling mechanism. I think this approach is much more straightforward 🙂

Also, don't know how feasible it is, but creating a test that cover the installation of an extension bigger than 20mb would be good. Wdyt?

I am open to this. Do we have documentation on how we can publish an extension so that it can be accessed by our e2e tests?

On the e2e we already add the ui-plugin-examples repo and some e2e tests with an extension https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/extensions/extensions.spec.ts#L23
We could create another one there with the conditions for that "20mb usecase", publish it on the repo and it would be automatically available to run an e2e about installing that extension.
https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/extensions/extensions.spec.ts covers install, uninstall, upgrade, rollback, etc, so a lot of code is already covered in that front.

@rak-phillip Let me know if you want to move this forward, I can approve it and we can capture another issue to cover this scenario as an e2e. At least this will allow us to "unblock" extensions running in against a -headbackend, if I am not mistaken


Folders

Would it be possible to add new folders and be able to move custom effects to these new folders? Thanks! Love your module.

Yes, a long term goal would allow for full customization of the folder layouts. So stay tuned but it could be a while

Completed as of v7


bugfix for docker build (per

https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53085816#53085816)

Can you fix the title of the PR? looks like it got truncated.
+1 after that.


[system-probe] Custom Prometheus Collectors

What does this PR do?
Replaces existing goroutine based prometheus collection for various telemetry with custom implementations of the prometheus collector interface. When prometheus "pulls" telemetry from the agent the Collect method is called and the updated values for the various telemetry are sent.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

How does prometheus know on which objects to call Collect/Describe ?  Does each object which implements those methods need to be registered in a prometheus.Registry?

tested on staging and stats are reporting for the custom collectors


A filtering example?

It'd be nice to have an example using angular filters :)

Can you give an example :) ?

Haha. Sure. I'll work one up.
On Thu, Jul 23, 2015, 12:23 PM Austin<EMAIL_ADDRESS>wrote:

Can you give an example :) ?
—
Reply to this email directly or view it on GitHub
https://github.com/Swimlane/angular-data-table/issues/28#issuecomment-124173170
.


Add default to http_serde::header_map::deserialize

The Go SDK typically has omitEmpty for Rust's http::HeaderMap entries, and services like ALB omit them when they're not present. However, without a default parameter to the #[serde()] annotation, deserialization fails when they're missing instead of the desired behavior of producing an empty HeaderMap.
This changes #[serde(deserialize_with = "http_serde::header_map::deserialize")] annotations to #[serde(deserialize_with = "http_serde::header_map::deserialize", default)] so we get the desired behavior. A test is also added (in aws_lambda_events/src/custom_serde.rs -- feel free to suggest a better place if there is one) to verify the correctness of this change.

This has been verified in my own Lambda function behind an ALB, FWIW.


Updating your README.md and some documentation add

adding CODE_OF_CONDUCT.md and LICENSE

Hello ,Could you Please assign this issue to me !
Thankyou


Update with jump host and readme

Lower python requirement from 3.9 to 3.8
Add jump host section in readme
Adding jump host in terraform stage.
Clean up hardcoded project id and number.

LGTM

I am not sure we can support Python 3.8.  I seem to recall some library dependency on 3.9+.  IMO we should not lower the Python requirement to 3.8.

Also Python 3.8 is scheduled for EOL in Oct 2024.  3.9 is supported through 2025.

Updated the Readme to keep with python 3.9 requirement.
The jump host setting can be updated in next PR.

Also Python 3.8 is scheduled for EOL in Oct 2024. 3.9 is supported through 2025.

Updated with 3.9 in the jump host.

Note: the CI/CD is not working as intended. We will fix this in later PR.


Update munit-cats-effect-2 to 0.9.0

Updates org.typelevel:munit-cats-effect-2 from 0.4-e42dd8d to 0.9.0.
GitHub Release Notes
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "munit-cats-effect-2" } ]

labels: test-library-update

Codecov Report

Merging #10 (6070ce7) into develop (10f10f3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #10   +/-   ##
========================================
  Coverage    75.00%   75.00%
========================================
  Files            3        3
  Lines           36       36
========================================
  Hits            27       27
  Misses           9        9

Continue to review full report at Codecov.

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


NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Describe the bug
acontece quando eu tento conectar o banco de dados (Supabase) ao projeto
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-86fwpyjf
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce
tentar resolver, se possível
Expected behavior
esperava ter a pré-visualização do projeto
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 68404604,
  "usedJSHeapSize": 60565012,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context
Error:
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Zj (https://bolt.new/assets/components-BPQqK2_k.js:24:26518)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27829)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28297)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28102)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28102)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
    at dk (https://bolt.new/assets/components-BPQqK2_k.js:24:28102)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27978)
Component stack:
    at button
    at https://bolt.new/assets/login-CwjdxPzR.js:1:40172
    at https://bolt.new/assets/login-CwjdxPzR.js:1:17807
    at https://bolt.new/assets/login-CwjdxPzR.js:1:17424
    at https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:4487
    at https://bolt.new/assets/login-CwjdxPzR.js:1:17807
    at https://bolt.new/assets/login-CwjdxPzR.js:1:17424
    at https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:4487
    at https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:38662
    at https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:49:4734
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at Popper (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:38464)
    at Tooltip (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:49:3533)
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at TooltipProvider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:49:2869)
    at https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:89:15516
    at div
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at Popper (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:38464)
    at Tooltip (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:49:3533)
    at Provider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:2697)
    at TooltipProvider (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:49:2869)
    at HeaderActionButtons (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:89:16716)
    at div
    at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
    at header
    at Header (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:89:17108)
    at div
    at IndexLayout (https://bolt.new/assets/_index-NyEmdF5V.js:145:39818)
    at Index$1
    at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
    at Outlet (https://bolt.new/assets/index-BkkrDsoJ.js:36:7773)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27920)
    at App
    at ClientOnly (https://bolt.new/assets/ErrorBoundary-U3t4dt5d.js:1:1119)
    at Layout (https://bolt.new/assets/root-Dgim_hb8.js:60:25)
    at RenderedRoute (https://bolt.new/assets/index-BkkrDsoJ.js:36:3987)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27920)
    at DataRoutes (https://bolt.new/assets/components-BPQqK2_k.js:33:6470)
    at Router (https://bolt.new/assets/index-BkkrDsoJ.js:36:7825)
    at RouterProvider (https://bolt.new/assets/components-BPQqK2_k.js:33:3672)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27920)
    at ck (https://bolt.new/assets/components-BPQqK2_k.js:24:27920)

Hey @hlemprendimentos, thanks for the report.
We'll get this fixed soon, but meanwhile you can proceed by disabling the browser extension that your are using to translate the page into Portugal. The browser extension is breaking Bolt here.


[static][stdlib] Any ELF platform can build static binaries.

Currently, building static binaries is gated to Linux. In order for this to work, the compiler looks for a file with a list of flags and uses them to generate a statically linked binary. This is a static file copied from the repository.
However, when building stdlib statically, the link files are generated dynamically from the cmakefiles; specifically, this is necessary to get the correct reference to the ICU libraries, as ICU is not a mandatory part of the build process. Therefore, we use the same dynamic generation of the linker flag file used in static stdlib generation for static binary generation.
Additionally, libdl is apparently necessary for Linux, but is not for OpenBSD, so this is conditioned here in a similar way that the ICU libraries are referenced.
Some unit tests are fouled up by this change because for some reason ImageInspectionELF.cpp is split out of swiftCore and put into its own library, and there still remain references from swiftCore to lookupSymbol in ImageInspectionELF. This causes lazy binding errors at runtime which mess up the expectations in these unit tests. This PR doesn't take a position yet as to whether such a split is necessary, so mark these unit tests UNSUPPORTED for now.
One unit test on OpenBSD is marked XFAIL for now because the test refers to lld at HEAD and not the platform lld; the lld at HEAD on OpenBSD does not link static binaries properly but the platform lld works fine if manually tested.

Thanks for moving swift to BSD world further. Do you have plan to support FreeBSD as well?

cc @spevans, who may have some context on the splitting issue.

@mko-io: I have sent you a pm on forums.swift.org.

Never mind on the file comment - I missed the fact that you had removed the custom command.

The only reason it was ever gated on Linux was that I had no way to test on other ELF platforms and so couldnt correctly construct the static-executable-args file for non-Linux OSes.
Note -static-executable doesnt really work correctly on Linux at the moment and -ldl shouldnt actually be linked in. This is because dlopen() doesnt work in static binaries (used for stack traces in fatalError). The fix for this is in #29039 although that PR needs a refresh.
This is why there are 2 libImageInspectionELF{Shared,Static}.a files, the Static one implements it own version of dladdr (in swift::lookupSymbol).

Right. Maybe I haven't looked into it too deeply, but does it not make sense not have lookupSymbol fallback to the static mechanism if dlopen fails, rather than replacing lookupSymbol entirely?

It been a while since I looked at it but I believe my thinking was that on Linux with Glibc and static binaries, using the dl* functions should be avoided at all costs. However I will see if I can rework my PR to just use the static symbol lookup as a fall back to dladdr() and see how that goes.

@3405691582 btw there is an integration test @ apple/swift-integration-tests#69 that hasnt been merged but you could modify for OpenBSD to act as a test for this PR

@spevans unfortunately, Dispatch needs a lot of work to be done for OpenBSD, but something similar might work instead. Thanks for the pointer, I'll take a look.

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Feature requests

Hi, thanks for making this cool opensource uploader. I have some ideas that I think should be added in the next version.

[ ] Add env variable COLOR to change META tag theme-color
[ ] Add og:image META tag, there should be site Logo that was uploaded by owner or default logo.
[ ] Option to setup custom image upload directory
[ ] Option for owner to set rate limit and storage upload limit for user
[ ] Premium users, add option for admins to mark user as premium, then premium users should have another rate limit and storage limit + premium badge
[ ] Anti-alt system, that user's cannot create more accounts from one ip
[ ] Dark theme, custom themes support and option for users to change default theme in settings
[ ] Option to setup custom embed when generating uploader config, when embed is enabled, embed endpoint should be returned instead of normal image link, something like view/i/id, but the embed should be configurable (title, site name, description, color)
[ ] Render error page on error, instead of just plain text that displays the error
[ ] Text hosting, something like hastebin
[ ] Invisible links (spaces) option when generating uploader config (something like https://zws.im )
[ ] Option to use your own SMTP server for sending emails instead of sendgrid using  https://www.npmjs.com/package/nodemailer
[ ] Add optional Github, Google and Discord oauth, if no oauth details will be seted in .env, oauth should be disabled
[ ] Password protected files and links
[ ] Option to set expiration of files for user, for example that files of that user will be stored for 1 month and then will be deleted

Hope you like my ideas.

Thanks for the ideas. I will see what I can do.

Hi, thanks for making this cool opensource uploader. I have some ideas that I think should be added in the next version.

[ ]  Add env variable COLOR to change META tag theme-color
[ ]  Add og:image META tag, there should be site Logo that was uploaded by owner or default logo.
[ ]  Option to setup custom image upload directory
[ ]  Option for owner to set rate limit and storage upload limit for user
[ ]  Premium users, add option for admins to mark user as premium, then premium users should have another rate limit and storage limit + premium badge
[ ]  Anti-alt system, that user's cannot create more accounts from one ip
[ ]  Dark theme, custom themes support and option for users to change default theme in settings
[ ]  Option to setup custom embed when generating uploader config, when embed is enabled, embed endpoint should be returned instead of normal image link, something like view/i/id, but the embed should be configurable (title, site name, description, color)
[ ]  Render error page on error, instead of just plain text that displays the error
[ ]  Text hosting, something like hastebin
[ ]  Invisible links (spaces) option when generating uploader config (something like https://zws.im )
[ ]  Option to use your own SMTP server for sending emails instead of sendgrid using  https://www.npmjs.com/package/nodemailer
[ ]  Add optional Github, Google and Discord oauth, if no oauth details will be seted in .env, oauth should be disabled
[ ]  Password protected files and links
[ ]  Option to set expiration of files for user, for example that files of that user will be stored for 1 month and then will be deleted

Hope you like my ideas.

Sadly, this will be a while till this is released with the updated version.  Will release the new version with all the basics features first then add more to it.

Ok, another idea: Add option to set length of image code for normal users, premium users, admins and option to rename image to your custom name for premium users and admins

Ok, another ideas:

[ ]  Add option to set length of image code for normal users, premium users, admins and option to rename image to your custom name for premium users and admins
[ ]  Add option to set Discord or slack webhook url to .env, then all actions (including admin actions) should be logged there.

Btw when updated version will be released?

Don't really know.  Going to be trying to grind this new version out as fast I can bit it's a lot.

Ok, another ideas:

[ ]  Add option to set length of image code for normal users, premium users, admins and option to rename image to your custom name for premium users and admins
[ ]  Add option to set Discord or slack webhook url to .env, then all actions (including admin actions) should be logged there.

Btw when updated version will be released?

The all actions thing I could add this to the panel mostliky using websocket to make them real time as well.