Update Sprite.js for renderCanvas method

Default when we change Sprite.width and height, we are changing Sprite.scale acutally. I need to change the size of Sprite but NOT changing its scale, so i modify Sprite.texture.frame size. I test changing Sprite.texture.frame size all right in WEBGL, but when i switch to CANVAS, i found the Sprite's size doesn't change.
I found the Sprite._renderCanvas's code drawImage not using texture.frame'size but using texture.crop's size. I think we should use frame's size for drawImage.

This change breaks sprites created from trimmed texture atlases. It should always use the crop value, not the frame size.

Also changing the width/height should change the scale. That's exactly how Pixi works internally (copied from how Flash does it). There will be no removal / changing of this in any version of Phaser 2, it's an API change beyond anything a point release is entitled to.

Thanks @photonstorm for pointing out, i forgot trimmed case.


Deployment streamlining and its restructuring

When we encounter development, ‘commit’ and deployment of some repo's code , the URL of some page may require frequent adjustments.
Some sources:

https://vercel.com/docs/projects/environment-variables/system-environment-variables
https://github.com/goplus/www/blob/master/goplus.org/widgets/build.js

fixed in #88


I am testing react native android and ios apps with appium using python and pytest. So do appcenter supports appium -python-client.If yes where is the documentation

@Veris-Mansi this is a duplicate of #538.


Update to 2.1: Configure Identity primary key data type in ASP.NET Core

Instead of:
 services.AddIdentity<ApplicationUser, ApplicationRole>()
        .AddEntityFrameworkStores<ApplicationDbContext>()
        .AddDefaultTokenProviders();

use this one if you are using default UI (new in ASP.NET Core 2.1):
services.AddIdentity<AcmeUser, AcmeRole>()
    .AddEntityFrameworkStores<ApplicationDbContext>()
    .AddDefaultUI()
    .AddDefaultTokenProviders();

AcmeUser and AcmeRole are customizations of IdentityUser and IdentityRole

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

ID: f5d03a65-2965-0261-3d05-bf2c89721fd2
Version Independent ID: 37f74d7d-ed17-eb35-183d-02f04183f880
Content: Configure Identity primary key data type in ASP.NET Core
Content Source: aspnetcore/security/authentication/identity-primary-key-configuration.md
Service: unspecified
Product: asp.net-core
GitHub Login: @AdrienTorris
Microsoft Alias: scaddie

@raffaeler  thanks for the heads up.

In the newly created project 2.1, I follow the instructions, but I will end up with an exception:
InvalidOperationException: No service for type 'Microsoft.AspNetCore.Identity.UserManager`1[Microsoft.AspNetCore.Identity.IdentityUser]' has been registered.

@MichalJana did you select the Individual User Accounts in the template dialog? Just click the Change Authentication button and pick that from the combobox.
The template works well for me.
Also, I strongly reccomend to read this article for the changes to the default UI feature

@raffaeler Yes I chose Individual User Accounts. Until I changed the primary key, everything worked. The exception occurred after changing the key according to the instructions.

@raffaeler Yes, after the change of the pk, I re-run the migration. This is a new project, where I did nothing but change pk.
DbContext
` public class ApplicationDbContext : IdentityDbContext<AppUser, AppRole, int>
{
public ApplicationDbContext(DbContextOptions options)
: base(options)
{
}
}
public class AppUser : IdentityUser<int> {}

public class AppRole : IdentityRole<int> {}`

Startup
`// This method gets called by the runtime. Use this method to add services to the container.
public void ConfigureServices(IServiceCollection services)
{
services.Configure(options =>
{
// This lambda determines whether user consent for non-essential cookies is needed for a given request.
options.CheckConsentNeeded = context => true;
options.MinimumSameSitePolicy = SameSiteMode.None;
});
        services.AddDbContext<ApplicationDbContext>(options =>
            options.UseSqlServer(
                Configuration.GetConnectionString("DefaultConnection")));

        services.AddIdentity<AppUser, AppRole>()
            .AddEntityFrameworkStores<ApplicationDbContext>()
			.AddDefaultUI()
			.AddDefaultTokenProviders();

        services.AddMvc()
			.SetCompatibilityVersion(CompatibilityVersion.Version_2_1)
			.AddControllersAsServices();`

@MichalJana  There are a few differences with my code. The most important is that I am using Guids instead of ints.
Did you scaffold the UI? If you did it, you may have some reference to IdentityUser instead of your new AppUser.
Also, at what point the exception is raised? Enable all the managed exceptions in the Exception settings and look at the stack trace.

I've created one more new application and used Guid instead of int. I did not scaffolded UI. I added migration and updated databases. Same exception:
System.InvalidOperationException: No service for type 'Microsoft.AspNetCore.Identity.UserManager1 [Microsoft.AspNetCore.Identity.IdentityUser]' has been registered.    at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService (IServiceProvider provider, Type serviceType)    at Microsoft.AspNetCore.Mvc.Razor.Internal.RazorPagePropertyActivator. <> c__DisplayClass8_0. <CreateActivateInfo> b__1 (ViewContext context)    at Microsoft.Extensions.Internal.PropertyActivator1.Activate (Object instance, TContext context)
   at Microsoft.AspNetCore.Mvc.Razor.Internal.RazorPagePropertyActivator.Activate (Object page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorPageActivator.Activate (IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync (IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync (IRazorPage page, ViewContext context, Boolean invokeViewStarts)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync (ViewContext context)
   at Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper.RenderPartialViewAsync (TextWriter writer, Object model)
   at Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper.ProcessAsync (TagHelperContext context, TagHelperOutput output)
   at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperRunner.RunAsync (TagHelperExecutionContext executionContext)
   at AspNetCore.Views_Shared__Layout.  b__46_1 ()
   at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperExecutionContext.SetOutputContentAsync ()
   at AspNetCore.Views_Shared__Layout.ExecuteAsync ()
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync (IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync (IRazorPage page, ViewContext context, Boolean invokeViewStarts)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync (ViewContext context, ViewBufferTextWriter bodyWriter)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync (ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync (ViewContext viewContext, String contentType, Nullable1 statusCode)    at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync (ActionContext actionContext, IVview view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync (ActionContext context, ViewResult result)
   at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync (ActionContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeResultAsync (IActionResult result)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResultFilterAsync [TFilter, TFilterAsync] ()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (ResultExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.ResultNext [TFilter, TFilterAsync] (State & next, Scope & scope, Object & state, Boolean & isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeResultFilters ()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter ()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow (ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next (State & next, Scope & scope, Object & state, Boolean & isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync ()
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync ()
   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke (HttpContext httpContext)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke (HttpContext context)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke (HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke (HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke (HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke (HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke (HttpContext context)

Are you sure you are using the last asp.net core 2.1 bits (RTM)?
If you can't resolve the issue, try putting the whole project in a repo so that the team can look at it ...

@raffaeler
dotnet --version returns 2.1.300. And nugets are 2.1.0

Try putting the code in a repo ...

Since I got exactly the same issue, I created a repo :
https://github.com/guillaumejay/IdentityInt
Hope it helps !

@HaoK  should this be moved to https://github.com/aspnet/Identity ?

The docs for the identity pieces are still correct here https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-primary-key-configuration?view=aspnetcore-2.1&tabs=aspnetcore2x but they need to be updated with additional steps for 2.1 to account for the scaffolder/default UI.
I'm not sure where everything eventually landed, but I believe the only way for this to work is to scaffold the UI and customize, @javiercn can you confirm?
cc @ajcvickers @blowdart

@HaoK Apart for the fix I posted here, I was successful in changing the PK to Guid without scaffolding everything.
FYI I scaffolded few parts after changing the PK and everything worked correctly.
Anyway, I didn't try to change to integer, maybe the problem is there. I will try as soon as I am back from my conference travel.

There shouldn't be any differences between Guids or integers really, so if nothing is scaffolded there shouldn't be any changes required for one or the other

@HaoK I agree, but as you can see from the tests I asked Michal to do, there are apparently no other changes other than the PK type.

What view is that issue coming from?
Have you updated _LoginPartial.cshtml?

https://github.com/guillaumejay/IdentityInt/blob/master/Views/Shared/_LoginPartial.cshtml#L3 This needs to be updated when you change the user.

Thanks ! I'm very tired, I should have found it...

@guillaumejay No problem!
Closing this as there's no more action to do here.


[Addon] Add Apache Kyuubi as a experimental addon

Apache Kyuubi is a popular serverless sql gateway in bigdata ecosystem. Recently, it has graduated from Apache Incubator to be a top level project. It would be good to add it to be a experimental addon.

Will try to support it soon.

Great idea!


merge from template-node-app

package.json

chore(deps): add ^11.5.17 remove ^11.5.15 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 6.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
v6.4.0
GitHub release

Your semantic-release bot :package::rocket:


Add the UserAvatar on the Grant Details page, and update UserAvatar component to generate an avatar for any user

Why is this issue important?
The Grant Details page shows the user avatar for different users who have set the team status.  Right now, the UserAvatar component only works for the logged in user.
Current State
No user avatar is present under the team status in the new Grant Details page.
Expected State
On the Grant Details page, there should be a User Avatar to the left of the team status text.
Implementation Plan
Update the UserAvatar component to work with any user
Relevant Code Snippets
No response

@TylerHendrickson any additional implementation details needed here or is this good to move to Ready? for reference, this was broken out from #2559

looks great to me in staging


Release of version <IP_ADDRESS> of xExchange

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #327 into master will increase coverage by 11.07%.
The diff coverage is 31.78%.

@@             Coverage Diff             @@
##           master     #327       +/-   ##
===========================================
+ Coverage    2.69%   13.76%   +11.07%
===========================================
  Files          38       39        +1
  Lines        4454     4619      +165
===========================================
+ Hits          120      636      +516
+ Misses       4334     3983      -351

Impacted Files
Coverage Δ

...FT_xExchMailboxServer/MSFT_xExchMailboxServer.psm1
0.53% <0%> (ø)
:arrow_up:

...chJetstressCleanup/MSFT_xExchJetstressCleanup.psm1
1.83% <0%> (ø)
:arrow_up:

...chReceiveConnector/MSFT_xExchReceiveConnector.psm1
0.44% <0%> (ø)
:arrow_up:

...MSFT_xExchImapSettings/MSFT_xExchImapSettings.psm1
2.77% <0%> (ø)
:arrow_up:

...ExchOutlookAnywhere/MSFT_xExchOutlookAnywhere.psm1
1.61% <0%> (ø)
:arrow_up:

...ectory/MSFT_xExchAutodiscoverVirtualDirectory.psm1
1.85% <0%> (ø)
:arrow_up:

...portService/MSFT_xExchMailboxTransportService.psm1
1.17% <0%> (ø)
:arrow_up:

...s/MSFT_xExchPopSettings/MSFT_xExchPopSettings.psm1
2.77% <0%> (ø)
:arrow_up:

...irtualDirectory/MSFT_xExchOabVirtualDirectory.psm1
1.13% <0%> (-0.05%)
:arrow_down:

...ExchMaintenanceMode/MSFT_xExchMaintenanceMode.psm1
0.25% <0%> (ø)
:arrow_up:

... and 33 more

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 93bc477...db736e4. Read the comment docs.


Dependabot configuration error

Describe the bug
Dependabot does not currently support child directories.  It's not running in /examples/ and we need to create an entry for each example.
To Reproduce

Contribution
Do you plan to raise a PR to address this issue?  YES

Planning to resolve this with wildcard in directory.  This feature should be available shortly
https://github.com/dependabot/dependabot-core/issues/2178


Forc ABI generation doesn't fail for scripts

Forc version: v0.1.6
Running forc json-abi for a script project gives the following output instead of an error:
$ forc json-abi
  Compiled library "core".
  Compiled library "core".
  Compiled library "lib-std".
  Compiled script "foo".
[]

Only contracts have an ABI, so forc json-abi should fail with an explanative error otherwise.

@adlerjohn can you think of any other instance where the json-abi output would be empty?

Empty, or error?

Empty, or error?

Maybe I'm misinterpreting, it is giving an empty json abi output, right? This is should give an error message: Cannot generate JSON ABI for non-contracts. But if there are any other reasons the command would produce an empty output, would we want it to catch that as an error too, or just leave as is?

Essentially, I'm asking if we actually need to check if it's a script, or if we can assume based on the empty output that it's a non-contract?

You have to check that it's a script or a predicate. It may be the case that a contract with no ABI produces an empty ABI file. That could happen if the contract is meant to be an upgradable implementation for example.


Try bundling with rollup

I noticed that the exported js contains a lot of extra code after the component.  I want to see  if Rollup saves that.
https://vuejs.org/v2/cookbook/packaging-sfc-for-npm.html

https://rollup-plugin-vue.vuejs.org/examples.html#component-library

I reverted this since it wasn't transpiling, pushed my WIP to https://github.com/BKWLD/vue-netlify-form/tree/rollup-transpile


Fix usage messages for podman image list, rm

The command documented in podman-image(1) is 'rm'. This is also
the human-friendly and expected subcommand name. Due to a
limitation in Cobra, it was implemented as 'rmi'.
This PR applies a variation of the hackery in #2471: instead of
enabling an alias, we change the command name from 'rmi' to 'rm'
but only within the 'podman image' subcommand. As a usability
bonus we also amend the examples.
Signed-off-by: Ed Santiago<EMAIL_ADDRESS>

LGTM
@baude PTAL

@rhatdan PTAL

@baude @rhatdan @TomSweeneyRedHat PTA(nother)L

@edsantiago One minor change and then LGTM
Tested with my script and this leaves us with just aliases.

/lgtm

/approve

Are these tests hung? Should I slash-retest?

bot, retest this please

We'll see if that does it. Otherwise, they're papr, so the openshift retest commands won't work, so we generally ping the maintainers on IRC and ask them to intervene manual-like

Alright, tests actually running now, hopefully will merge soon.


Add basic build instructions to the README

Thought I'd go ahead and add some basic but potentially helpful build instructions since the README was lacking them. Please feel free to add or change anything you'd like. These instructions should work for any platform that dotnet can be installed on.

Oh my gosh you're right, sorry for not catching that before opening the PR. Thanks for pointing it out for me.

If all's well, could you please merge?


Update styles.styl

Removes the rotation which has the potential to make people very nauseous (and has).

cf. #46
I'll take a look right now. Thanks for your contribution.

Also cf. #45

Oops. Pointing the wrong issue. :)


Multiple google api keys (MAPS_API_KEY) per Application

We're creating an SDK that uses google maps, and this sdk will be used in many applications that may also use google maps too !
Is there a solution for using several instances of google maps with several keys, one MAPS_API_KEY key for the library and another MAPS_API_KEY key for the application ?
Thanks in advance !

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@cchaouachi Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.


Add .qvs as one of the default extension for QlikView/Qlik Sense

I would like to propose .qvs as an added extension for Qlik View/Sense scripts. At least among the Qlik users I know, the two popular extensions are .qvs and .qvw. (.qvd is used for binary qlik data files). I can submit a pull request, but I'm not sure if I need to modify languages.ts, supportedExtensions.ts or both.

[x] I'm sure this issue is not a duplicate?

This is going to be supported via #522.


feat: implement send_messages_and_wait_commit on Axon chain endpoint

close #179, #180

the code structure is fine, but need to add test cases to check its feasibility with solidity contract

This PR is mainly focused on conversion between message and event type in solidity and forcerelay. If you want to test correction of this conversion then you have to a large dataset which needs much work. And it is not a good idea for now as our type is still possible to be changed.
If you mean test on whether the constructed transaction can be sent and accepted by solidity contract, and do not care about type conversion, then I think it should be put into another PR. That is an integration test which needs EVM mock or contract instance (I even think we don't need to test it as most of functionalities are provided by ether-rs and we just convert types)


refactor: remove launch_training and call sft_trainer directly

Description of the change

Get rid of launch_training.py so all argument parsing logic to stays in main function.

This will make it easier for contributors to make all changes needed to support new dataclasses in train() in one place.
Also makes it easier to test argument parsing and only have one location for it instead of duplication.
In addition, this moves the copying of the final checkpoint, logs, and .complete file into accelerate_launch which should dramatically improve errors for copying when tuning with multi-processes.

The sft_trainer.main() will then accept command line as well as JSON for args. We are trying to promote JSON over CLI.

Additionally, we are trying to make JSON conversion to dataclasses as the primary codepath - we will convert **kwargs to a dict and use parse_dict HF function to convert dict to associated dataclasses. This will make it easier to test one code path

This required moving the error logging into accelerate_launch (all good) and into sft_trainer. This means that users running sft_trainer will get an error.log created as well as different exit codes.
Since the sft_trainer script does not exist within the image, accelerate launch now triggers the python module tuning.sft_trainer - Changes each process to interpret the launch script as a Python module, executing with the same behavior as ‘python -m

How to verify the PR

Rebuilt the image using my fork to create Artifactory image. Deployed new image to cluster and tested with multi-GPU LoRA and fine tuning with a granite and llama model and both ran through successfully.
bash-5.1$ ls /data/anhuong/tuning_output/*refactor*
/data/anhuong/tuning_output/granite-13b-instruct-lora-multigpu-test-refactor:
config.json			  model-00004-of-00011.safetensors  model-00009-of-00011.safetensors  tokenizer.json
generation_config.json		  model-00005-of-00011.safetensors  model-00010-of-00011.safetensors  tokenizer_config.json
model-00001-of-00011.safetensors  model-00006-of-00011.safetensors  model-00011-of-00011.safetensors  training_logs.jsonl
model-00002-of-00011.safetensors  model-00007-of-00011.safetensors  model.safetensors.index.json
model-00003-of-00011.safetensors  model-00008-of-00011.safetensors  special_tokens_map.json

/data/anhuong/tuning_output/llama-13b-ft-multigpu-test-refactor:
added_tokens.json		  model-00004-of-00006.safetensors  rng_state_0.pth	     tokenizer_config.json
config.json			  model-00005-of-00006.safetensors  rng_state_1.pth	     trainer_state.json
generation_config.json		  model-00006-of-00006.safetensors  scheduler.pt	     training_args.bin
model-00001-of-00006.safetensors  model.safetensors.index.json	    special_tokens_map.json  training_logs.jsonl
model-00002-of-00006.safetensors  optimizer.bin			    tokenizer.json
model-00003-of-00006.safetensors  pytorch_model_fsdp.bin	    tokenizer.model

Was the PR tested

[ ] I have added >=1 unit test(s) for every new method I have added.
[x] I have ensured all unit tests pass

https://github.com/foundation-model-stack/fms-hf-tuning/actions/runs/9388517275/job/25884511262?pr=164#step:4:200
Something is incompatible with the trl package. You want to make trl==0.8.6 to get this PR merged fist ?

Have been looking into that too @tedhtchang thanks! I agree, adding the change, looks like adjusting to SFTConfig will take a bit more work than expected.


OSD-7196 Disable DMS for "fake" OSD clusters

Adds additional "managed.openshift.com/fake" annotation to skip.
Fixes logic when there are multiple annotations to skip.

Codecov Report

Merging #118 (6538426) into master (a1abf8c) will increase coverage by 0.12%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #118      +/-   ##
==========================================
+ Coverage   39.94%   40.07%   +0.12%
==========================================
  Files          14       14
  Lines         791      791
==========================================
+ Hits          316      317       +1
+ Misses        442      441       -1
  Partials       33       33

Impacted Files
Coverage Δ

...ntegration/deadmanssnitchintegration_controller.go
57.28% <100.00%> (+0.33%)
:arrow_up:

/approve


two question .

thanks for your sharing.nice work.
but could you pls show your ablation experiment result? especially the cbam.
and could u pls tell me why you didn't use  " c = qk.pow(2).sum(1).unsqueeze(1) “ in the code.
wait for your reply .

Haven't tried that before.
We will update the paper later on this. In short, the following softmax will cancel out this term.

Haven't tried that before.
We will update the paper later on this. In short, the following softmax will cancel out this term.

thank you .

Update: We tried without CBAM block and I would say that we don't really need it. We get -0.6 J&F in DAVIS and +0.1 global score in YouTubeVOS -- so nothing really significant. You are welcome to drop this block (see no_cbam branch).


How to chose the threshold for LocLoss?

Usually the [theta_1_1 theta_1_2; theta_2_1 theta_2_2] is mall (less than 1).  The parameters [theta_1_3 theta_1_3] will be much bigger (because this is the offset of cropped feature map or image part). So how to set the threshold of LocLoss for those two different types of parameters? Or I misunderstand the implement? Any suggestions? @daerduoCarey

I think you misunderstand the definition for theta_1_3 and theta_2_3. They should not be too large and should be of the same scale with other thetas. All thetas are defined to map a location from the source image to the target image in [-1, 1] scale, instead of the actual pixel space scale, e.g. [0, 224], [0, 256]. For example, any location in the source image or the target image is defined to be in [-1, 1], which is the relative location within the whole image.
Hope my reply answer your question. Thank you.

Got it. I misunderstand it. Thanks a lot. @daerduoCarey

Another question about the details. Consider the feature map is CHW. C is the channel. H, W are the height and width of the feature maps. Are the parameters [theta_1_1 theta_1_2 theta_1_3]  correspond with the feature width (denoted as x in original paper)? Or I misunderstand the  order of x and y in the original paper? Thanks. @daerduoCarey

Yes. You're right.

OK. Thanks a lot. @daerduoCarey

Yes. You're right.

Hi, author。In your code, I find that x_t and y_t are reversed, here is your source code
for(int i=0; i<output_H_ * output_W_; ++i) { 		data[3 * i] = (i / output_W_) * 1.0 / output_H_ * 2 - 1;               // this is y_t, I think, cause it is scale by 'output_H' 		data[3 * i + 1] = (i % output_W_) * 1.0 / output_W_ * 2 - 1;     // x_t 		data[3 * i + 2] = 1; 	}
And based on these codes, theta is also reversed,  [theta_1_1 theta_1_2 theta_1_3] correspond with [y_t x_t translation]。
Emm.....it looks weird. Is there something I miss? I will appreciate it if you could give me a reply. Thanks!


Check if area delete button exists before remove

If allowDelete is set to false .remove() will fail because $btDelete is undefined.

@newradius indeed ! thank's for the fix !


WIP tentative fixes the CI.

This is a combine of multiple patches.

Fixes timeout error on windows. , timeout are not working on windows.
Upgrade all to ubuntu 20.04
Switch to python3

@lygstate Please, don't do this.

This PR is still opened from your master branch. Please use git branches for development.
This PR still has multiple commits (7 at the moment).
 Non-English is not understood by most of the maintainers.
Please don't use PRs for testing your solutions. First of all, test your changes locally on your development machine. Then, have a fork of the repo on GH, have a branch therein for your changes, and push versions of your commit only there. Your Travis CI account and your GH Actions should be used to test them. Once everything is green, only then open a PR from the branch.

I'll keep closing PRs like this one when I see that they are used incorrectly.

Other than that, have separate PRs for separate enhancement ideas.

Bumping Ubuntu version is one thing.
Fixing Windows timeout is another.
Switching to python3 is yet another.

Maintainers may accept some of those ideas while reject others. (E.g., Ubuntu version bump is questionable without any justification given. It works now, who needs the change any why? Dropping Python2 support is again something some people may strongly argue against. Right now, our scripts work on all Python versions. What makes it necessary to drop the support of Python2? Does it block any functionality that mandates that change?)

@akosthekiss Please don't close this, I am using this to trigger the CI. after things fine, I'll split them

But you do know that you can trigger your own CI, don't you?

But you do know that you can trigger your own CI, don't you?

It's triggered now, but 3 hours ago, it's doesn't triggered.


[BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.0
What problem did you encounter?
after opening roblox through bloxstrap, i cannot access the menu where i can change the client settings nor hide chat box
Bloxstrap Log
N/A

Addressed in Wiki


Submit to F-droid

RFP @ https://gitlab.com/fdroid/rfp/issues/593.  Will keep this open as tracking.

@IzzySoft, would you mind helping with this?

Have you tried filing an RFP (Request For Packaging) with F-Droid? Not that hard, and you know the required facts better than me. That's all I could do anyway – I'm just a normal user :wink:

If you agree with the inclusion of this app in F-Droid, could you please tag your releases (see here), it would be very helpful for us. You could also attach the binaries to your releases (see here).
That's pretty easy and very helpful for those of us who aren't using Google services.

Attaching the .apk to your releases (as @Poussinou just suggested) would enable me to put your app in my repo immediately (until F-Droid has published it).

Thanks, @IbrahimYousre – find it in my repo now! You're not going for the official repo?

@IzzySoft I don't know how, I need some help with that.

@IbrahimYousre According to @IzzySoft's repo data, the app is debuggable, which is a problem.  Please remove for public releases.
@IzzySoft The RFP's been accepted, so, beyond the above, what does @IbrahimYousre need to do?

@TPS No idea what's missing. Maybe asking Pierre? He opened the FRP, and usually he's one of those processing those requests.
As for debuggable: that shouldn't be an issue for F-Droid. One can build an app for debug (as Ibrahim seems to do), or for production (what F-Droid does). AFAIK that's a decision made at build time, but I'm not a dev so I cannot say 100% sure.

@IzzySoft The merge request has not been merged yet (still waiting for a review from someone else) so it is not in the repository yet.

@TPS and @IbrahimYousre : as I (vaguely) stated above and @Rudloff just confirmed, you can ignore the "debuggable" flag. That's part of "compiling" the app: you either build it for "debug" or for "release". Obviously, @IbrahimYousre always built "for debug"; but F-Droid always builds for "release". So this is no issue here.

@TPS  and @IzzySoft Do I have to include a keystore in my repo? How would I make the app build for release, without publishing my developer keystore?

@IbrahimYousre Definitely not, you should never publish your keystore. For the official F-Droid repo, F-Droid uses its own keystore – and for mine, I just use the .apk. So if you want to provide an .apk so I can include your app with my repo until the official one is ready, simply build it on your machine and publish it here, see Creating Releases in the GitHub Help. But that's already done.
It might simply take a little time until a F-Droid maintainer integrates it.

Thanks @IzzySoft , This is the first time I release a software and I am confused a little bit. I will make another build for release.

No need to worry, @IbrahimYousre – everyone has started at some point :wink:
The build for release will be highly appreciated for my repo. For the official repo, as said, it's not needed as they build themselves.

@IbrahimYousre thanks, I've replaced the debug one!

As mentioned in #13, this landed @ https://f-droid.org/app/com.ibrahimyousre.resumebuilder ~1 week, & will wait merge to close.

@IbrahimYousre A question re: the release differences between GPlay & F-Droid:  GPlay reports it has v1.1.4, while the latest tagged release (which is what F-Droid uses) is 1.1.2.  Is there a reason not to keep parity via the tags?

Looking at the Releases, he just forgot to tag the new releases 1.1.3 and 1.1.4.
@IbrahimYousre Could you please tag this two releases, with the same pattern as before?

@Poussinou  I have skipped v1.1.3 entirely, it wan't released anywhere. I would tag v1.1.4 which is the current version at GPlay as @TPS has mentioned.


Razor Pages tutorial File Uploads topic

Fixes #4188
Review site link
Notes:

There were a number of tiny changes to the current tutorial, but there was one significant change: I'm of the philosophy that lists of objects should be plural (but I left the dB table names singular), so I refactored the current sample a bit to accommodate that approach. It's a bit more satisfying to have:

_context.Movies.Add(Movie); instead of _context.Movie.Add(Movie);
_context.Movies.SingleOrDefaultAsync(...) instead of _context.Movie.SingleOrDefaultAsync(...)
@foreach (var item in Model.Movies) instead of @foreach (var item in Model.Movie)

I also moved the RazorPagesMovie.cli.csproj file out into a "snapshot" folder. When the sample has two project files, Bower is a big 'ole :bomb:. We can't assume a dev will download and necessarily know that they should kill that second project file before attempting to run the sample. btw-- I added the Bower and BundlerMinifer bits to make them work. I'm still a bit concerned about having such in samples, but the sample is complete and functional with them wired up to work.
AFAIK the EF migrations work. I didn't run the entire tutorial from Step 1 (don't have VS installed here; I'm on VSC); however, the migrations did work locally with CLI dotnet ef xxxx commands. I assume the PS versions of the commands will be fine with PMC.

cc/ @danroth27 @DamianEdwards
Outline

Introduction

Purpose
Sample app (note file streaming for large files with a link)
Spec (two file uploads on the same POST; easy enough to downgrade to one, and this covers a common scenario with forms where a single multiple-file upload isn't appropriate)

Add static helper method to handle the upload bits
Add Schedule class to hold the movie schedule title and files' content
Update the MovieContext
Add Schedule table to the database with an EF migration
Add a FileUpload class to bind to the view
Add the file upload Razor Page
Add the file upload code-behind
Link the file upload Razor Page to the app's navigation
Add a confirm delete page with code-behind
Show the working file upload page with images
Additional resources (include IFormFile interface)

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@rynowak Please review

@guardrex Here's some feedback from @rynowak:
Two comments:
The code in FileHelpers should be dramatically simplified. IFormFile already has a length, and already does buffering to disk. This will just look like:
using (var reader = new StreamReader(file.CreateReadStream(), Encoding.UTF8))
{
    return reader.ReadToEndAsync();
}

The scary warning about “don’t do this for real” in FileHelpers is not helpful for anyone. We should show customers code they can use.
We already have limits in place about the size of uploads and form posts. We should show the code that validates the content type is expected and that the file encoding / file name is appropriate.

@scottaddie I'll make another pass on it tomorrow afternoon.

@scottaddie @rynowak PTAL Let's see if this is headed in the right direction.

It became simpler with the updated StreamReader setup. It became more complex moving it to more of a real world example (i.e., file validations).
In ProcessSchedule, I pass in the model state to generate an error on-the-fly if a check fails.
Therefore, I perform two model state checks in OnPostAsync: The first check is to catch any quick attribute-based failures. If that's all good, I go on to processing the files looking for any other file-based violations. Coming back from ProcessSchedule, I perform a second ModelState check.
In ProcessSchedule, I use a little reflection there with MemberInfo to grab the display name of the model property for the error messages so that magic strings aren't required.
I cleanse the FileName property just a hair by encoding it so that it can become part of error messages. The user would still need to add additional checks if they have other requirements (e.g., store it in a dB, use it in other ways). However if you'd like to see more checks done/shown with FileName, let me know.

@scottaddie Idk whaz up with that adding-model.md metadata violation. This PR doesn't touch that file AFAIK.
aspnetcore/tutorials/first-mvc-app-mac/adding-model.md

unexpected type String for metadata helpviewer_keywords, the expected type is string[]

typeof(FileUpload).GetProperty(scheduleFormFile.Name.Substring(scheduleFormFile.Name.IndexOf(".") + 1));

Oh no no get the file name by calling System.IO.Path.GetFileName rather than using substrings. I know the file name doesn't get used to persist to disk anywhere, but this, at least, shows people the right way to go about it should they ever want to.

@blowdart I see that the Name prop is provided by the Content-Disposition header:
"form-data; name=\"FileUpload.UploadPublicSchedule\"; filename=\"ANSI.txt\""

The substring is there to split that, since I just want the property name. I do see how fragile this is, except that if GetProperty can't be passed anything that would :boom: it would null out and no-op (i.e., if the Content-Disposition header was missing, malformed, or hacked). You still want me to run it through System.IO.Path.GetFileName anyway? I still need to split it ... I guess GetFileName is still going to return FileUpload.UploadPublicSchedule.
Regarding the FileName prop, is this of concern? ...
var fileName = WebUtility.HtmlEncode(scheduleFormFile.FileName);

Do you want me to do a System.IO.Path.GetFileName there on the scheduleFormFile.FileName before encoding it for the error message strings?

I passed it something nonsensical to see what it would do, and this approach seems to trap anything that would go wrong (property nulls out) ...
MemberInfo property = typeof(FileUpload).GetProperty("Geebers McScreebers!");

if (property != null)
{
    var dd = property.GetCustomAttribute(typeof(DisplayAttribute)) as DisplayAttribute;

    if (dd != null)
    {
        fieldDisplayName = $"{dd.Name} ";
    }
}

Therefore if the Content-Disposition header is missing, malformed, or hacked, shouldn't this be ok?
MemberInfo property = typeof(FileUpload).GetProperty(scheduleFormFile.Name.Substring(scheduleFormFile.Name.IndexOf(".") + 1));

If content-disposition is missing it's a bad file upload surely?

I see what you're trying to do, it's just odd :)
Yea, put it in
var fileName = WebUtility.HtmlEncode(System.IO.Path.GetFileName(scheduleFormFile.FileName));

And add a comment saying this will strip any path information passed as part of the filename?

If content-disposition is missing it's a bad file upload surely?

True, but even the MVC topic, File uploads in ASP.NET Core, doesn't get into the weeds. I guess the idea when that topic was written is that if the file upload fails internally (inside of the implementation behind IFormFile) that it will error out just like anything else.
I am concerned about any way possible that a hacker could break this code. I think the latest commit with the GetProperty won't break, but I'd like some dev team backup on that notion.

And add a comment saying this will strip any path information passed as part of the filename?

I did add the System.IO.Path.GetFileName on the last commit. I'll add a note next.

it's just odd

:grinning: ... you would prefer a magic string passed in to get the field name for the error message???

@guardrex  @scottaddie  what's left to get this published?

AFAIK it just needs a final review+sign-off.
There was just some minor concerns earlier about exactly what to show, since these also become recommendations on how to do things.
I favor passing in the model state now and faulting it in the file upload processor method that I built. I also try to avoid a magic string for the faulting control with a smidgen of MemberInfo.
I'm free over the next few days, so just let me know if anything needs to change, and I'll jump right on it.

@scottaddie  looks like this is ready to merge?

@blowdart Anything else you'd like addressed in this PR?

Nope


Move SACA Hub Log Analytics workspace to Tier 1

Benefit/Result/Outcome
Enable role separation by having log analytics work done in Tier 1.
Description
The current Log Analytics workspace is deployed to the SACA hub. Move to T1.
Acceptance Criteria

A log analytics workspace is deployed to T1.
Existing logs are forwarded to the T1 LA workspace.

Moved the scope for this issue into #128


raw hash data being re-formatted between formatter and setter

Rails 4.2, jsonapi-resources: 0.9.0
Part of my ember app submits a json hash as an attribute rather than creating lots of extra models. This is stored in postgres as jsonb.
I've noticed bugs since moving from mirage to rails (with jsonapi-resources) re: missing data. For example, an options hash that is submitted as:
{"atLeast": 3}
but for some reason (the bug) it's being stored as
{"at_least": 3}
To debug this I added a setter to the resource, and a custom serializer, and poked both with binding.pry / debugger to see what values were being passed in.
class RawValueFormatter < JSONAPI::ValueFormatter
  def self.format(raw_value)
    raw_value
  end

  def self.unformat(raw_value)
    # binding.pry
    raw_value
  end
end

# in the resource class
def options=(new_options)
  # binding.pry
  @model.options = new_options
end

The serializer receives the expected raw_value  {"atLeast": 3}, but the setter receives the other unexpected format.
Stringifying the data before submission seems like a work-around, but seems a bit strange.

@nruth I'm not sure why your keys are being reformatted. I just tested some JSON attributes and the keys are not being altered, though I was doing it with the sqlite db and storing the json in a string field. I tried it both with a value formatter and setter/getters to handle the json.
class JsonValueFormatter < JSONAPI::ValueFormatter
  class << self
    def format(raw_value)
      JSON.parse(raw_value)
    end

    def unformat(value)
      return if value.nil?
      value.to_s
    end
  end
end

class FooResource < JSONAPI::Resource
  attribute :extra_data
  attribute :extra_extra_data, format: :json

  def extra_data
    JSON.parse(_model.extra_data)
  end

  def extra_data=(extra_data)
    _model.extra_data = extra_data.to_s
  end
end

Thank you for checking! I guess it's application specific then, and sorry for the run-around. We have AMS in the app so perhaps that is interfering.
I'll try and reproduce this as a JR test case / in a new rails app, but closing the ticket as can't promise when that will happen.
In case anyone else picks this up and wants a quick work-around, I found that stringifying the object worked: an ember transform that json-encodes on submission, and API parsing back to object before saving to pg.


Feature request: Bring back macOS support

Prerequisites

[X] I have searched the repository’s issues, Kinde community and public roadmap to ensure my feature request isn’t a duplicate
[X] I have read the contributing guidelines
[X] I agree to the terms within the code of conduct

What is the problem you’re trying to solve?
I have a macOS app that needs the Kinde SDK
What solution would you like to see?
Bring back macOS support
Additional information
No response

@lockieluke we are reluctant to do this as Kinde requires an active internet connection to authenticate, would you be looking at using long token lifetimes?


Use React containers (or Hooks)

The Redux logic is sitting in the React components. Rewrite to use containers to make the code cleaner.

Hold off on this until Hooks have become standardised, as they may offer a cleaner approach.

Hooks + TypeScript are now being used in the codebase. There's still lots of older code (and my understanding of hooks has improved considerably since I last worked on Sparkled), so I'll probably refactor everything at some point.
Closing this for now.


Semantic information for Denotation.info and Database.sugars

#808 introduces a prototype implementation of infos and sugars that represents these introspection artifacts as strings. It turns out it's not that outrageous, because even strings can be extremely useful for code analysis tools.
However, we clearly need to provide more information to our users. Representing both infos and sugars as full-fledged trees sounds like a good idea.

I will take this on since I have an idea I'd like to try out.
I propose to

Change Sugar message in schema

message Sugar {
  Range range = 1;
-  string syntax = 2;
+  Attributes attributes = 3;
}

Sugar.syntax becomes Sugar.attributes.contents
m.Database.sugar(pos) returns Stat instead of String.

sugars at the same position are concatenated, example [1..1) [T] and [1..1) (blah) becomes [1..1) [T](blah). The ordering used for concatenation is 1) .apply 2) type params 3) implicit args.
Database.names includes names from nested sugars, this makes it possible to do name.symbol on names inside the returned Stat using the root Database.
If Sugar.attributes.contents does not parse as a Stat, then we prefix it with *. Example, .apply => *.apply/ [T] => *[T]/implicitConf(*)(args) is unchanged. The * identifier resolves to the symbol _root_.scala.meta.sugar.
other magic terms like * in conversion(*)(arg) also resolve to the symbol _root_.scala.meta.sugar.

#1000 took the first steps towards fixing this problem. The PR added two data structures Input.Sugar and semantic.Sugar, which can be used to attribute "invisible code". Now that this model is merged, I propose we

close this issue
delegate Database.denotations to #1015
open separate issues for bugs/rfe on the new model to attribute sugar


docker-engine.rpm push the fish completion in the wrong place

See https://github.com/fish-shell/fish-shell/issues/2436
The fish completion file should be in /usr/share/fish/vendor_completions.d

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

BUG REPORT INFORMATION
docker version: git master.  also affects docker-engine-1.8.2-1.fc22.x86_64
docker info: I didn't even bother installing docker.
uname -a: Linux [redacted] 4.1.6-200.fc22.x86_64 #1 SMP Mon Aug 17 19:54:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Provide additional environment details (AWS, VirtualBox, physical, etc.):
Inspection.  Also, the specfile is clearly wrong.
List the steps to reproduce the issue:

dnf install fish

curl -sS curl https://get.docker.com/ |sh

Read https://github.com/docker/docker/blob/master/hack/make/.build-rpm/docker-engine.spec#L146 and observe that the directory is indeed wrong.

Describe the results you received:
I didn't actually try it, but it will fail.  Or follow the link above for someone who did try it.
Describe the results you expected:
It shouldn't have failed.  I can't believe I'm typing this.
Provide additional info you think is important:
----------END REPORT ---------

ping @jfrazelle

Cool wanna open a pr

PR for RPM created in https://github.com/docker/docker/issues/17144
now looking at apt/deb

and pr for deb; https://github.com/docker/docker/issues/17145

Still getting this with latest 1.9.0 docker on CentOS 7?
Transaction check error:
  file /usr/share/fish/completions/docker.fish from install of fish-2.2.0-3.1.x86_64 conflicts with file from package docker-engine-1.9.0-1.el7.centos.x86_64

that PR was not in the release
On Wed, Nov 4, 2015 at 1:45 PM, bings<EMAIL_ADDRESS>wrote:

Still getting this with latest 1.9.0 docker on CentOS 7?
Transaction check error:
file /usr/share/fish/completions/docker.fish from install of fish-2.2.0-3.1.x86_64 conflicts with file from package docker-engine-1.9.0-1.el7.centos.x86_64
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16668#issuecomment-153875808.

it will be in the next one
On Wed, Nov 4, 2015 at 2:04 PM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

that PR was not in the release
On Wed, Nov 4, 2015 at 1:45 PM, bings<EMAIL_ADDRESS>wrote:

Still getting this with latest 1.9.0 docker on CentOS 7?
Transaction check error:
file /usr/share/fish/completions/docker.fish from install of fish-2.2.0-3.1.x86_64 conflicts with file from package docker-engine-1.9.0-1.el7.centos.x86_64
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16668#issuecomment-153875808.

@jfrazelle 1.9.1?

if @tiborvass wants
On Wed, Nov 4, 2015 at 3:48 PM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle 1.9.1?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16668#issuecomment-153906830.

<-- insert cute puppy eyes image here -->

Still happening with 1.9.1
Transaction check error:
  file /usr/share/fish/completions/docker.fish from install of fish-2.2.0-3.1.x86_64 conflicts with file from package docker-engine-1.9.1-1.el7.centos.x86_64

@ashtonbatty these changes are not used when building the 1.9.x RPMs, they'll probably land in the next, 1.10 release

So, at this time, the only way to install docker-engine package from docker repo is to use dnf download docker-engine-selinux docker-engine and install them with rpm -ivh --replacefiles ...
But any update of fish package with dnf update will break... It could be great to have a fix on 1.9.1-X package.

+1

Very annoying, especially because I cannot use the version of Docker provided in Fedora (for some reason, it is unable to log into the hub).
Can't it be fixed with the 1.9, or is there a repo with 1.10 ?

1.10 is now out; repo is at yum.dockerproject.org

Seems to work as expected. I updated and didn't had any problem.
Thanks


[BugFix] Fix mv may not completely refresh when create with property p…

…artition_refresh_number
What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #21419
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

@Youngwb @Astralidea

https://github.com/Mergifyio backport branch-3.0

https://github.com/Mergifyio backport branch-2.5


Routine of RAM size evaluation not sufficient and might cause issues

Environment
script version: v3.0.56
OS: DSM 7.2
Device: 1817+
RAM: 2x 8GB
Problem description
The evaluation of RAM size might cause issues because the condition of the grep command for dmidecode is not clear enough.
Example:
On my system the command dmidecode -t memory | grep "[Ss]ize" will return the following content.
Size: 8192 MB
Size: No Module Installed
Size: 8192 MB
Size: No Module Installed

Now you can imagine what will happen with the variables $ramsize and $bytes when evaluating with awk.
ramsize=$(printf %s "${array[num]}" | awk '{print $2}')
bytes=$(printf %s "${array[num]}" | awk '{print $3}')

The result is:
ramsize: 8192
bytes: MB
ramsize: No
bytes: Module
ramsize: 8192
bytes: MB
ramsize: No
bytes: Module

At the end of the loop we will have fortunately the correct numeric value for the variable $ramtotal. But the unit for $bytes is inconsitent.
ramtotal: 16384
bytes: Module

Proposed solution
My proposal is to make the grep command with an extended regular expression much more precise that will return only the size with numeric values and additionally with a valid unit either MB or GB as postfix at the end of the line.
#Proposal
dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$"

# Return
Size: 8192 MB
Size: 8192 MB

I haven´t checked other systems yet, but it could also lead to an error in the calculation of $ramtotal size.
Please have a look and check if the improvement can be implemented.

Nicely formatted issue, and nice solution. Thank you.

From a code review so far, it looks pretty good. I think this is fine now.
Thanks for the fix.


Allow using selectize API methods

Hi. I can't see it in code but is there a way to access selectize instance so I could use selectize events & api? For example I'd like to do open().

Sorry, I put console.log in onInitialize function and it doesn't work.

Are you using v1.1.1?
On Sat, Jan 17, 2015 at 1:45 PM, Qwal<EMAIL_ADDRESS>wrote:

Sorry, I put console.log in onInitialize function and it doesn't work.
—
Reply to this email directly or view it on GitHub
https://github.com/machineboy2045/angular-selectize/issues/30#issuecomment-70383601
.

My bad. I had 1.1.0 Thanks!


get and has method else removed

get and has method's redundant else condition removed.

this changes execution since the if condition is not returning anything.

Tests are failing.

@tillkruss Yeah. There is a mistake on the new if condition 😕

Please resubmit with Ci passing.


Add metrics about EventLoop

Micrometer does not support metrics for Netty's EventLoop. https://github.com/micrometer-metrics/micrometer/issues/522
We may add our custom metrics for EventLoop.

Number of EventLoops
Number of pending tasks.
...

This looks interesting. May I try on this issue ?

Looks interesting. If no one's assigned, may I look into the issues ?

For sure. Thanks for your interest. 😀

Checking to see if I missed a PR addressing this ticket? We need something like this internally so I wanted to build something ad-hoc. @seonwoo960000 are you actively working on it?

Hi @vkostyukov ! I'm not currently working on this and I think you can first work on this issue.

Thanks! I will grab this!

Got a PR here: #4750 4750


Show expired and completed tasks in a separate view

"As a user, I want expired and completed tasks presented in a separate view"

@RyanBalfanz CR?


Create 2024-02-05-munin.md

Blog: Reddit bot overview #151 - initial commit

Looks good to me, @StreamingDataApps can you look at the changes suggested by @StreamingDataApps? We can then merge it. Thanks

@SirCipher @brohitbrose All changes have been included, except those that depend on the project re-factor.

@StreamingDataApps, I think @SirCipher's comments are about adding references to the code (commits) for the items specified in the "Parting Thoughts" section

@StreamingDataApps Is this good to go now? It might be worth updating the file name to the current date before release but it's no big deal if not.

Needs one final review before we merge this one, will get to it this week

Looks good to me, @SirCipher can you take a quick look and approve?


Dell Alienware Aurora R7

hi, I can't get alienfx-tools to work yet, seeking help :-)

Just downloaded from here today, 0.9.0.
Windows 10 home 10.0.19043.
Alienware Command Center <IP_ADDRESS> installed already.
AlienFX Tools 3.1.200 installed already.
Aurora R7, 0VDT73, Bios 1.0.23, i3 8100, 8gb ram single stick, GTX 1060 3gb.
I can successfully run AWCC and change all the lights (there are 3 zones: the power button, the right case panel, the left case panel).
AlienFX, AlienFusion Windows Service both appear as status Running.
Doesn't appear to matter if I am running powershell as Administrator.
I did install the old DirectX stuff and rebooted and that didn't fix it.
There isn't anything for "enable 3rd party apps" that i can see anywhere in AWCC. Ah, the Windows task bar tray Alienware entry has a right-click menu, and allow 3rd party was on.

PS C:\Program Files\AlienFX Tools> .\alienfx-probe.exe
alienfx-probe v3.1.1
For each light please enter LightFX SDK light ID or light name if ID is not available
Tested light become green, and turned off after testing.
Just press Enter if no visible light at this ID to skip it.
Probing low-level access... AlienFX devices not present, please check device manage!

Wow!
Being honest, you are the first guy with Alienware desktop here.
Ok, let's check and add support for you gear, if possible.
 Download latest version (3.1.3) from here - 0.9.0 WAY too old!

After downloading, you can use alienfx-cli - it have Dell high-level support as well - try alienfx-cli high-level status or alienfx-cli high-level set-all=255,0,0
For low-level support, i need you help:

Open "Device manager"->"Human interface devices".
For each "HID-Compliant vendor-defined device", open properties, switch to "Details", switch "Property" to "Hardware ids" and tell me VID and PID.

If they use re-marked chip, i add it, but if it's something OEM - we need to scan interface, but it's a next step.

Thanks for your note! Apologies, no idea how I got the old version by mistake, my fault. I did just install v3.1.3. When I try "set-all=0,255,0" the lights do not change from their current red to the intended green. I also tried as Administrator, still no change.
There are a few too many HID entries to manually go through, there's 8 of them and that's annoying, so I am trying to find a way to export those but of course Windows UI/UX is sorta lame and frustrating this way... :-) I will add a reply when i get the information!
PS C:\Program Files\AlienFX Tools> .\alienfx-cli.exe high-level status
alienfx-cli v3.1.3
No low-level devices found, trying high-level...
Dell API ready
Dell API version <IP_ADDRESS> detected
Devices found: 1
Device #0, Name: Alienware AuroraR7 Chassis, Type: Desktop, Lights: 3
  Light #0, Name: Alienhead, Position Unknown, Color (0,0,0), Brightness: 0
  Light #1, Name: Side Left, Position Unknown, Color (0,0,0), Brightness: 0
  Light #2, Name: Side Right, Position Unknown, Color (0,0,0), Brightness: 0
Done.
PS C:\Program Files\AlienFX Tools> .\alienfx-cli.exe high-level set-all=0,255,0
alienfx-cli v3.1.3
No low-level devices found, trying high-level...
Dell API ready
Done.

 Get-WmiObject Win32_PNPEntity| Out-File -Append -Force "hwdump.txt"

then massaged it in emacs (i am not a windows person, really), then extracted the vendors...
type .\hwdumpB.txt| findstr vendor |Out-File vendors.txt

NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL04\\B&1ED82C98&0&0003"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL04;                               \\B&1ED82C98&0&0003"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_046D&PID_C537&MI_01&COL04\B&1ED82C98&0&0003; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_046D&PID_C537&REV_3400&MI_01&Col04, HID\VID_046D&PID_C537&MI_01&Col04, ;                               HID\VID_046D&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_046D&PID_C537&MI_01&COL04\B&1ED82C98&0&0003; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL05\\B&1ED82C98&0&0004"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL05;                               \\B&1ED82C98&0&0004"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_046D&PID_C537&MI_01&COL05\B&1ED82C98&0&0004; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_046D&PID_C537&REV_3400&MI_01&Col05, HID\VID_046D&PID_C537&MI_01&Col05, ;                               HID\VID_046D&UP:FF00_U:0002, HID_DEVICE_UP:FF00_U:0002...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_046D&PID_C537&MI_01&COL05\B&1ED82C98&0&0004; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL06\\B&1ED82C98&0&0005"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_046D&PID_C537&MI_01&COL06;                               \\B&1ED82C98&0&0005"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_046D&PID_C537&MI_01&COL06\B&1ED82C98&0&0005; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_046D&PID_C537&REV_3400&MI_01&Col06, HID\VID_046D&PID_C537&MI_01&Col06, ;                               HID\VID_046D&UP:FF80_U:0080, HID_DEVICE_UP:FF80_U:0080...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_046D&PID_C537&MI_01&COL06\B&1ED82C98&0&0005; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL08\\A&375BC78&0&0007"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL08;                               \\A&375BC78&0&0007"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_258A&PID_002A&MI_01&COL08\A&375BC78&0&0007; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_258A&PID_002A&REV_3109&MI_01&Col08, HID\VID_258A&PID_002A&MI_01&Col08, ;                               HID\VID_258A&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_258A&PID_002A&MI_01&COL08\A&375BC78&0&0007; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL07\\A&375BC78&0&0006"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL07;                               \\A&375BC78&0&0006"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_258A&PID_002A&MI_01&COL07\A&375BC78&0&0006; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_258A&PID_002A&REV_3109&MI_01&Col07, HID\VID_258A&PID_002A&MI_01&Col07, ;                               HID\VID_258A&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_258A&PID_002A&MI_01&COL07\A&375BC78&0&0006; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL06\\A&375BC78&0&0005"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL06;                               \\A&375BC78&0&0005"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_258A&PID_002A&MI_01&COL06\A&375BC78&0&0005; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_258A&PID_002A&REV_3109&MI_01&Col06, HID\VID_258A&PID_002A&MI_01&Col06, ;                               HID\VID_258A&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_258A&PID_002A&MI_01&COL06\A&375BC78&0&0005; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL05\\A&375BC78&0&0004"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL05;                               \\A&375BC78&0&0004"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_258A&PID_002A&MI_01&COL05\A&375BC78&0&0004; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_258A&PID_002A&REV_3109&MI_01&Col05, HID\VID_258A&PID_002A&MI_01&Col05, ;                               HID\VID_258A&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_258A&PID_002A&MI_01&COL05\A&375BC78&0&0004; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT
NEXT_ENTRY; __CLASS                     : Win32_PnPEntity; __SUPERCLASS                : CIM_LogicalDevice; __DYNASTY                   : CIM_ManagedSystemElement; __RELPATH                   : Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL03\\A&375BC78&0&0002"; __PROPERTY_COUNT            : 26; __DERIVATION                : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}; __SERVER                    : DESKTOP-B66FIOT; __NAMESPACE                 : root\cimv2; __PATH                      : \\DESKTOP-B66FIOT\root\cimv2:Win32_PnPEntity.DeviceID="HID\\VID_258A&PID_002A&MI_01&COL03;                               \\A&375BC78&0&0002"; Availability                : ; Caption                     : HID-compliant vendor-defined device; ClassGuid                   : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}; CompatibleID                : ; ConfigManagerErrorCode      : 0; ConfigManagerUserConfig     : False; CreationClassName           : Win32_PnPEntity; Description                 : HID-compliant vendor-defined device; DeviceID                    : HID\VID_258A&PID_002A&MI_01&COL03\A&375BC78&0&0002; ErrorCleared                : ; ErrorDescription            : ; HardwareID                  : {HID\VID_258A&PID_002A&REV_3109&MI_01&Col03, HID\VID_258A&PID_002A&MI_01&Col03, ;                               HID\VID_258A&UP:FF00_U:0001, HID_DEVICE_UP:FF00_U:0001...}; InstallDate                 : ; LastErrorCode               : ; Manufacturer                : (Standard system devices); Name                        : HID-compliant vendor-defined device; PNPClass                    : HIDClass; PNPDeviceID                 : HID\VID_258A&PID_002A&MI_01&COL03\A&375BC78&0&0002; PowerManagementCapabilities : ; PowerManagementSupported    : ; Present                     : True; Service                     : ; Status                      : OK; StatusInfo                  : ; SystemCreationClassName     : Win32_ComputerSystem; SystemName                  : DESKTOP-B66FIOT; PSComputerName              : DESKTOP-B66FIOT

(note that the "status" could not discover the current RGB settings since it reported (0,0,0) for all 3 zones, but they are currently set to red.)

(oh looks like originally i was using 3.1.200 up above at the top i think, i typed up the original notes wrong, not sure what was 0.9.0)

Dell API version <IP_ADDRESS> detected

Wow! Ancient!
Lights SHOULD change color by Dell API, but, most probably, AWCC switch it back. Try to use "loop" command after set-all, it block AWCC change (but also keep cli running).
VID_046D - Logitech. Do you have mouse or keyboard from them?
VID_258A - Seems like here it is. OEM from SinoWealth, they make LCD controllers. I didn't support it yet.
So... Easy way didn't work (but maybe AW become re-marked SW later).
Can you please install USBPcap, run it, then change some lights by AWCC, then send me a log?
I'll add support.

I updated to 3.1.301 just now as well.
No idea if this usbpcap will be of any help. I went into AWCC and changed the zone lights around in various ways.
https://drive.google.com/file/d/13wMdeZk2YgVc8-JCtgT9ZwCOcjY9RklZ/view?usp=sharing

You are correct that adding "loop" does make the lights change to the color I set.

About USBPcap - you can attach files right here, doesn't need use GD. Ok, i'll check.
Yes, AWCC try to restore colors after app exit in some cases.

I check you pcap.... Seems like you are choose wrong controller (need one with VID_258A devices inside). So no data.

Oh no! Ok I will try again. The USBPcap user interface doesn't seem very clear to me i guess, heh.

You can use it as a part of wireshark, then UI will be a bit better.

I think I was capturing the correct interface. There are 2 listed by USBPcap/Wireshark, and only the 1st one has devices on it, and only the 1st one shows any data when i capture. Also, the number of "vendor" things matches the count from Device Manager.
https://drive.google.com/file/d/1Q1db4SstkAPeDK5Llum78_C8g2CE6C2W/view?usp=sharing
I don't understand the dump because I searched for the vendor ID (had to get the endian order right ha ha?) and it looks to me like it was 1.6.0 but then there's nothing from 1.6.0 after the configuration. The only data looks to be USB_INTERRUPT with 1.9.1, which is maybe the hub for the mouse & keyboard.

Uh-oh. It means light device is not USB in this case, like the rest of devices.
Let me RTFM for a while...

... According to the specs, it should have classical v2-v3 chip inside.
But also have 3rd-party USB controller (ASMEDIA).
So we have 2 possibilities:

Chip is still connected to USB, but hidden. Can you look for ANY USB device with VID_187c?
Chip is connected to serial i/o interface (most probably). In this case, we need to find it's address. Can you check SMBIOS info at the any tool like rweverything or hwinfo?

Good news interface is the same like v2-v3 notebooks, we just need to find chip interface. ^_^

Nothing in the device dump that is 187c or anything like that as far as I can tell.
hwinfo / Motherboard / SMBIOS DMI / Port Connectors / Port Connector / type: unknown, internal reference: LED CONTROLLER.
rweeverything:
[Port Connector Information] (Type 8)
08 09 23 00 01 FF 00 00 FF 4C 45 44 20 43 4F 4E	..#......LED CON
54 52 4F 4C 45 52 00 00                        	TROLER..
Type	0x08 (8)
Length	0x09 (9)
Handle	0x0023 (35)
Internal Reference Designator	String1 - "LED CONTROLER"
Internal Connector Type	0xFF - Other
External Reference Designator	NULL
External Connector Type	0x00 - None
Port Type	0xFF - Other

i don't see how to find any more info however?!?!?

Handle	0x0023 (35)

This is enough for now. Let me work for some days, then i drop you a probe to check.

Uh-oh. I got some info and code.
Good news - There are Dell SMBIOS driver, even in source code. And i plan to add it anyway for fan control.
Bad news - it will be not a short story, so i can't predict then i done.
PS: BTW, all Aurora up to R6 use notebook USB chip.  And we still have probability it's USB, just some OEM like DARFON (AKA RGB keyboard).

I need you help.
I'm working on fan/power control as well as you gear support now.
Can you please install/run rweverything, open "ACPI" page, save all data and send it to me?
I want to check you structures and how far it from other ones.
T.I.A.!

I'm gonna be following this. I have an Aurora R7 as well as an Aurora R8 that I can provide info off my systems to you as well. the r8 just supports 8th and 9th gen Intel Core I chips.

@WildOne69
Welcome!
Is R8 doesn't have USB light device as well as R7? If it have, try to use alienfx-probe app and share the probe output, please!
In any case, i will be appreciated for ACPI dump from rweverything.

https://drive.google.com/file/d/1oMbYhgoZfEudqmF4BaG6hSc9OkmKY_-Z/view?usp=sharing please let me know when you've downloaded it :-)

Ok, thank you! I remove a link.

Status update - i make a new tool for direct ACPI access, this can be used for you lights too. It doesn't support you hardware yet, but will do. You can check early beta here.

Status update - i support fan control now, but still looking for ACPI function to control lights. Seems like R7 the only one requires this kind of access, so still looking for examples.

"Serial IO I2C host controller"? Should have Alienware VID.

which app should i use to check? in windows system information, i see only GTX and Audio irq's when searching for "Serial IO I2C..."

Common Windows "Device Manager". Then "Properties->Details->Hardware IDs".
Look for VID_187C.
I'm trying to find the control interface inside AWCC ACPI methods now, but still don't locate it.

Device Manager > View > Devices by container > Desktop XXXXX > Intel(R) Serial IO I2C Host Controller
A2E0 and A2E1
PCI\VEN_8086&DEV_A2E0&SUBSYS_08581028&REV_00
PCI\VEN_8086&DEV_A2E0&SUBSYS_08581028
PCI\VEN_8086&DEV_A2E0&CC_118000
PCI\VEN_8086&DEV_A2E0&CC_1180
PCI\VEN_8086&DEV_A2E1&SUBSYS_08581028&REV_00
PCI\VEN_8086&DEV_A2E1&SUBSYS_08581028
PCI\VEN_8086&DEV_A2E1&CC_118000
PCI\VEN_8086&DEV_A2E1&CC_1180

Switch to "Devices by connection" and check what is connected to these controllers, please!
As i said before, look for VEN_187C.

PS: If we still not locate device, let's try to grab AWCC to interface communication. I'll drop you the instruction.

Honestly unfortunately nothing found yet with 187C from all the GUI or complete device dumps I've done thus far, so I am wondering if maybe there's another vendor ID that alienware/dell could be using?
"Devices by connection" > DESKTOP-XXXXX > ACPI x64-based PC > Microsoft ACPI-Compliant System > PCI Express Root Complex > Intel(R) Serial IO I2C Host Controller {A2E0,A2E1} ... those do not show any sub-tree, they do not show any children connected to them, they are leaf nodes in the GUI.

According to Dell specs for your gear, you should have a common Alienware light control chip, v4 in my API.
I donno how (and for what) they hide it so deep.... AFAIK other desktops have common HID interface for it.
Ok, let's try to catch them.

Install USBPcap.
Install, reboot, run it, choose one of the controllers (which one - we need to find) and file name (abcd.pcap, for example).
Run AWCC, change some colors.
Stop USBPcap.
Check file - if it has small size (some kb) - it's not what we are looking for. Try other controller. It should be about 100kb+ in size.
If you found it - you can take a look yourself using WireShark and send it to me for analysis.

hm didn't we do this before up above in this thread, or will this be different data?

Yes, we do. I forget, sorry.
Buuuut.... Seems like i found in ACPI.
Take a look at your dump, search for Method(SETC!
Seems like it's what we're looking for.
Bad news, i can't include it into AlienFX directly. Good news, i can use this into AlienFan.

When I look for the SETC I see it in a few places in the ACPI dumps. There's
C5SETC, _SB_AMW1SETC, CM72pCM73bICPCSETC
dunno if that means anything/useful. :-)

No, look for EXACT "Method(SETC".
Looks like it is. Do you have 3 lights?

I am not finding "Method(SETC" anywhere, what should I use to dump it? Note that RW-Everything gives me an error when I try to use it to get ACPI data, so I've used msinfo32 and devcon, I have not seen that string in the output.
From devcon I did see:
ACPI\PNP0C14\AWCC
Name: Microsoft Windows Management Interface for ACPI
Driver is running.

I don't need it, i use direct ACPI method calls.
So.... I provide you the test version of alienFAN-cli soon (today or tomorrow). You can check did it change lights and some another things i found.
If all works - i'll think how to integrate it. But seems like it will be part of alienfan project, not alienfx ('cause it require ACPI access).

So, here are test version for you - alienfan-cli.zip
Unpack it (antivirus can complain!), then run alienfan-cli with some parameters. First, you can check is your hardware supported or not for fan control (it should be) - use, for example, alienfx-cli rpm or without parameters - you will see in output.
Even if it says "not supported", try to issue these commands:

alienfan-cli resetcolor - it should reset your color system, but i don't know what stage it will have after.
alienfan-cli setcolor=light,r,g,b - it should set light(s) to given color. WARNING! "Light" here is not the number, but bitmask. So use 1,2,4 (or combination for set more, than one).
alienfan-cli setcoloreffect=mode,num - I have no idea what it does, but something related to color system. "mode" can be in (1,3,4,6,7,9,10,12,13,15), "num" is 0 or 1 (enable/disable?).

Please, share results with me.

hi,
"resetcolor" opens a new command output window and says
AlienFan-cli v<IP_ADDRESS>
Supported hardware v4 detected, 3 fans, 3 sensors, 2 power states.

but then hangs and i can't even kill the window or process, have to manually power cycle.

Interesting...
So detection passed, but calling method loop inside. Ok, let me check.
PS: Did you check other commands?

Upd: Well, it's possible if light system busy (AWCC doing this?). The code inside \_SB.AMW1.SRST:
Store(One, IC6C)
While(One)
{
	If(LEqual(IC9C, One))
	{
		Break
	}
}

So it waits endlessly until light system reset done.
Noted. Let me think how to cut it from wait.

Oh, i found system lights init:
		\_SB.AMW1.ICPC()
		\_SB.AMW1.SETC(Zero, Zero, Zero, 0x04)
		\_SB.AMW1.SETC(Zero, Zero, Zero, 0x02)
		\_SB.AMW1.RCPC()
		\_SB.AMW1.SETB(0x0F, Zero)

So i need to modify code to keep this sequence. Wait a little.

Ok, try this - alienfan-cli.zip (NB: Reboot your system before use, i change the driver code, so need to reload it).
I've adds waiting timeout, so method call will fail if not finished in reasonable time.
Also, i change resetcolor and setcolor logic. Seems like resetcolor not needed, try setcolor first.
And seems like setcoloreffect should set brightness, not effect.

it always opens another command window to show the output which then goes away as soon as the command finishes so it is hard to see what it is reporting and hard to copy-paste it here.
BUT, success with "alienfan-cli.exe setcolor=2,0,255,0" to change the side lights, it really worked!
light 1 doesn't seem to work.
light 2 is the right hand side.
light 4 is the left hand side.
light 8 doesn't seem to work.

it always opens another command window to show the output

It's because it requires admin. Start administrator command prompt and run it from it.

BUT, success with "alienfan-cli.exe setcolor=2,0,255,0"

Great. You can also try to mix lights - use 3 or 5 or 7 as number. It's strange 1 not works (you have it, but seems like it is power button, maybe need some additional magic). 8 and higher will not work at all, as i see into code.
What about "setcoloreffect"? What it does?

Now i think how to integrate it... I don't want always share ACPI code. Maybe additional library for this, so fan and gui will use it. But not sure about ambient and haptics.

what do you mean by latest release? the zip from just up above? where is the "setcolormode" command docs?
other things look to work
C:\Users\x\Downloads\alienfan-cli>.\alienfan-cli.exe rpm
AlienFan-cli v<IP_ADDRESS>
Supported hardware v4 detected, 3 fans, 3 sensors, 2 power states.
Fan#0: 5237
Fan#1: 1103
Fan#2: 400

C:\Users\x\Downloads\alienfan-cli>.\alienfan-cli.exe temp
AlienFan-cli v<IP_ADDRESS>
Supported hardware v4 detected, 3 fans, 3 sensors, 2 power states.
CPU Internal Thermistor: 37
GPU Internal Thermistor: 31
FAN#3 sensor: 34

Thank you. What about getfans and setfans (but stop AWCCServiece first!)?
Can you please try alienfan-cli rpm unlock setfans=50,50,50 getfans rpm?
Last release is 1.3.0 is at GitHub - here (i publish it yesterday).
At your beta, this command name is setcoloreffect, but it is not right, so i change it into release.
I need to check - is this command control lights brightness (seems like this) and on/off state?

Thanks. setcolormode have 2 parameters. Should be brightness and on/off or some effects.
Can you try setcolormode=12,1, setcolormode=7,0, setcolormode=1,1, setcolormode=1,0?
If this doesn't change anything - the task is closed.
PS: Your system light control already integrated into alienfx-gui, but you need to enable fan control in "Settings" to use it (just set Power mode to 2nd value at "Fans" tab if you don't want to control fans).

Ooops!
It's a bug, sorry, thanks to reveal it. I will fix it at next release.
Please add 2 more arguments for now (any value, it will not be used) - setcolormode=1,0,1,1

setcolormode does change the lights, it is doing something at least. :-)

Full support added in AlienFx-Tools 5.0.4 and AlienFan-Tools 1.3.1


[BUG] libjpeg-turbo => 3.0.1

Description
Libjpeg-turbo has been updated to 3.0.1: https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.0.1
Code
https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.0.1
Expected Behavior
No response
Actual Behavior
No response
Version of SkiaSharp
2.88.3 (Current)
Last Known Good Version of SkiaSharp
2.88.2 (Previous)
IDE / Editor
Visual Studio Code (Linux)
Platform / Operating System
All
Platform / Operating System Version
No response
Devices
No response
Relevant Screenshots
No response
Relevant Log Output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@mattleibow Maybe the bug fixes in libjpeg-turbo 3.0.1 fix the bugs in the issues #2650 #2666 #2643, too? The release notes talks about AArch64, which I think is used for 64-bit iOS builds?

Any update on this? It is affecting all jpeg encoding on iOS devices with SkiaSharp 2.88.6.

1

I tested 3.0.1 and the latest main and I think this is an issue in libjpeg-turbo. For now I am reverting to the latest 2.x series.
I had a look at the original security issue and it does not affect the 2.x series because 12-bit jpegs are not actually supported in our build. The 2.x series required the entire library to be either 8-bit or 12-bit, and we use 8-bit. The 3.x series allowed for both simultaneously.
The security issue was just reported for 2.1.90 (which seems like a 2.x series but is actually a 3.0 beta). The current stable version is <IP_ADDRESS> which is on a separate branch.