Users are having issues with CUE 2

Users are reporting that using CUE 2 does not automatically detect the Corsair SDK.

FYI I have no problems with CUE 2.3.74 and 2.4.66
(Win 7, x64)

I have pushed a small update that fixes issues with CUE 2.
Version 0.5.1b

I don't know if this is the place to do it, but I have updated from 0.5.1a to b and it stopped working. I reverted to .a and it is working again.
.b has the "Could not start" try as administrator thing; I believe it was the thing it was supposed to fix. The CUE thing reports it is up to date (1.16.42).
I have a G910 KBD, Corsair mouse (M65 RGB) and headphones (Void RGB).
It all works just fine in 0.5.1a, including colors, though there are some minor issues.
2016_15_09.txt
Windows 10 Pro (10.0.14393)
CUE (1.16.42)
Aurora (0.5.1b)

Maybe try the lastest CUE version 2.5.66

Oddly enough, the updater claims there is no newer version. I wonder if it's an error on Corsair's side or it it has some issues to resolve.
I saw the new version on their website. I will try it tomorrow.

My CUE also fails to retrieve an update. My version's 2.4.66. I haven't had many issues with the dev version, the only problem I saw was that CUE has problems initializing at windows launch. But that's about it, pressing "Retry for connected devices" fixes it.

CUE update is disabled for open beta of CUE2

Checking in.
CUE 2.5.66
AURORA 0.5.1b
Aurora starts and works as expected but will not detect Corsair hardware. Software (CUE) is installed and working (I have reconfigured my old colors) and SDK is ON in settings, but Aurora says no connected devices. Keeps retrying and ultimately fails.
I also tried a manual retry about 5 minutes in, just to make sure. No connected devices for Corsair.
G910 is still humming along nicely (minus the known G keys issue).


Better English in README.md documentation

@Vehsamrak Can you make this change on my fork?

@dimiro1 Here you are: https://github.com/dimiro1/darwin/pull/1


[BugBash] Package list table does not fit its borders

On the my packages page:

Either table width should be compacted, or border widened, so there is no overlap

Removing Organizations epic, as this is more of a version formatting issue. Moving to backlog.


Measure user satisfaction with SimpleReport

From Tim Best:
Objective
Enable the USDS PRIME mission to get better, faster, complete and accurate data to STLT public health departments so they can take timely appropriate action, with an emphasis on flexibility and scale for pandemic readiness
Key Result
Measure the SimpleReport user sentiment (right measurement framework?) with who (facilities makes more sense)?
https://docs.google.com/document/d/1cIjdoARc_r6NDRQ_VUmuHfMspLrmVVkdRd1UMDpqf2k/edit?usp=sharing

Laura and Victor meeting tomorrow to discuss methodology around this. Tim has requested that we include questions measuring this in Touchpoint surveys.

settled on user satisfaction language and cleared it with Tim, now working on forms for PRA approval with @vz3


Variants Schema Redesign

We need to redesign the contract schema to match the design below.

Only exception to the design is I think that Wolf is going to add a Sku to the table as well.
So here's my initial proposal for the new schema:
repeated Option options    = 12;
repeated Sku skus          = 13;

message Option {
    string name                = 1;
    string description         = 2;
    repeated Variants variants = 3;

    message Variants {
        string name          = 1;
        Image image          = 2;
    }
}

message Sku {
	string combinations = 1;
	uint64 surcharge     = 2;
	string id                   = 3;
}

The options field is used primarily to enumerate what options are available so the UI can populate the drop down boxes for option selection during checkout.
We would eliminate the current string sku field and replace it with the repeated Sku object. This object would contain a string similar to what is used in inventory to identify which combination it represents. For example /large/blue.
The surcharge would be added to the base price found earlier in the listing.
id is a sku number.
Issues

In the above schema the image is attached to each variant (ie: large or blue but not /large/blue). Do we want to keep it this way or should the image be per combination?

We need better names for combinations and id. I called it id above just because having sku inside Sku seems weird. So help would be nice naming them.

What happens if they include a list of options but no list of skus?

Does this seem to work?

@rmisio @JustinDrake @jackkleeman @jjeffryes @drwasho

This is what I proposed during the last technical call. You have options (e.g. size and color). Each option has variants (e.g. small, medium, large). The SKUs enumerate the variant combinations with a well-defined defined ordering.
Each SKU has a price, quantity, image. This is maximally flexible. If the frontend wants to reuse images across SKUs, it can! If the frontend wants absolute prices, percentage surchages, absolute surchages, or something crazy, it can!
In the special case where there are no options, there's a single SKU corresponding to the empty combination.
For exampe suppose again the size variants are ["small", "medium", "large"] and the colour variants are ["green", "blue"]. Then the possible combinations would be [0, 0], [0, 1], [1, 0], [1, 1], [2, 0], [2, 1] corresponding to ["small", "green"], ["small", "blue"], ....

I don't think it makes sense to use the "sku" terminology for the repeated skus field. Really, it's just data that pertains to a variant combination. This is further enhanced by the fact that the sku is optional. Perhaps 'combinations' (or 'variantCombinations') would be better?
Also, I do think image would have to be at the combination level, although, since @cpacia mentioned it wouldn't be a problem to add a field later on, I think we could omit it for now. Or, it could be optional. The v2 client is not planning on supporting combo images for the initial release.
repeated Option options    = 12;
repeated Combination combinations          = 13;

message Option {
    string name                = 1; // size
    string description         = 2; // Choose a size please
    repeated Variants variants = 3;

    message Variants {
        string name          = 1; // large, medium, small
    }
}

message Combination {
	string variantCombo = 1; // large/red, large/medium, large/small
	uint64 surcharge     = 2; // 100
	string sku                = 3; // abc123
}

With name the only field in the Variants object, it could be flattened to a list of strings, but what if in the future we want to associate some data with a variant? Would it be problematic with existing data to go from list of strings to a list of objects? If so, let's leave it as an object (sacrifice some bloat for some future proofing).
FWIW, I don't think I have any large objection to Justin's alternate representations of how the second object (the one he calls Sku) can reference the variant combo (whether it's 'large/red' or [large, red] or [0, 1]).

Agreed with @rmisio that the Sku is awkward. I've refined my suggestion below.
repeated Option options       // e.g. [sizeOption, colorOption]
repeated Combo combos         // e.g. [smallBlue, smallGreen, mediumBlue, ...]

message Option {
    string name               // e.g. "size"
    string description        // e.g. "Choose your T-shirt size"
    repeated string variants  // e.g. ["small", "medium", "large"]
}

message Combo {
    repeated int combination  // e.g. [1, 1]
    string sku
    uint64 price
    int quantity
    Image image
}

Those who haven't worked in a retail or ecommerce setting might find the term sku to be awkward, but that that's what products are called in retail. Nobody calls them combos. They say "I've got 10 skus I need to sell through", etc.

How do you differentiate between sku the product struct, and sku the string identifier?

Using Stock Keeping Unit in typical commerce can refer to both the product and the identification code, which can be confusing. I think SKU would be fine for the key, and we could use Identifier or Code for the identification in the object.

@jjeffryes @rmisio what do you think about using integers in the variant combos rather than the variant names?
It would look like:
"skus": [
                    {
                        "variantCombo": [
                            0,
                            0
                        ],
                        "productID": "932-33-2945"
                    },
                    {
                        "variantCombo": [
                            0,
                            1
                        ]
                    },
                    {
                        "variantCombo": [
                            1,
                            0
                        ],
                        "productID": "123-99-1111"
                    },
    ]

(thinking this through...)
options: [
  {
    name: 'size',
    description: 'choose a size please',
    variants: [
      {
        name: 'L'
      },
      {
        name: 'M'
      },
      {
        name: 'S'
      },
    ]
  },
  {
    name: 'color',
    description: 'choose a color please',
    variants: [
      {
        name: 'red'
      },
      {
        name: 'green'
      },
      {
        name: 'blue'
      },
    ]
  },
  {
    name: 'shape',
    description: 'choose a shape please',
    variants: [
      {
        name: 'circle'
      },
      {
        name: 'triangle'
      },
      {
        name: 'square'
      },
    ]
  }
]

So is you wanted a SKU for a large/red/circle, it would be [0, 0, 0]?
For small/green/square, it would be [2, 1, 3]?
(Sorry, just had to think that through. If my understanding is correct there on how that would work, then it sounds fine to me.)


Migration guide for migrating from v1 to v2

I feel a small migration guide on how to convert from v1 to v2 is needed. Could we make use of GitHub Wikis for this?

Created wiki - https://github.com/jackdomleo7/Cooltipz.css/wiki/How-to-migrate-from-v1-to-v2
Closing issue.


Set dirty when array field changes

readField's return value can be an array so in order to determine if a form is dirty, I handle this case by iterating through all the elements.

Thanks for this!! :+1:


Error linking sessions-get-and-post with symlink to granada samples

I followed your instructions at https://github.com/webappsdk/granada/wiki/Build-for-Linux-and-MacOS for building granada.  I am using Ubuntu 16.04.1 LTS.
Where is says "...link or put these granada folders respectively in the include, the src and the samples folder of your C++ REST SDK project." I chose to create symbolic links.  I commented out the samples except session-get-and-post.
Everything ran fine until linking when I received the following error.
[100%] Linking CXX executable ../../../Binaries/sessions-get-and-post
c++: error: ../../../Binaries/libcpprest.so.2.9: No such file or directory
samples/granada/sessions-get-and-post/CMakeFiles/sessions-get-and-post.dir/build.make:427: recipe for target 'Binaries/sessions-get-and-post' failed
make[2]: *** [Binaries/sessions-get-and-post] Error 1
CMakeFiles/Makefile2:1028: recipe for target 'samples/granada/sessions-get-and-post/CMakeFiles/sessions-get-and-post.dir/all' failed
make[1]: *** [samples/granada/sessions-get-and-post/CMakeFiles/sessions-get-and-post.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
It works fine when I copy the samples folder instead of making a link (still using links for include and src).  It looks like an issue with relative paths (../../../Binaries) not resolving properly after cd follows the symlink.  Not a big issue since it is just for the samples but I thought you may want to either correct the instructions or update the build to support the symlink.
I'm not terribly comfortable modifying the cpprest project in order to integrate granada.  Based on your comment regarding building for windows at the end of your last post on the issue at https://github.com/webappsdk/granada/issues/1, it looks like it should be possible to build granada as an so on Linux and build the samples referencing that so.  Can you explain your rationale for that choice vs. compiling granada as a separate so that relies on the cpprest so?
I recognize this is more of a discussion than an issue, but it looks like probably the best way to communicate unless you have a preferred alternative.  It has the advantage (and disadvantage ;-) of being available for others to view and learn from.

Hi,
Thank you for your suggestion,

I'm not terribly comfortable modifying the cpprest project in order to integrate granada. Based on your comment regarding building for windows at the end of your last post on the issue at #1, it looks like it should be possible to build granada as an so on Linux and build the samples referencing that so. Can you explain your rationale for that choice vs. compiling granada as a separate so that relies on the cpprest so?

I had the same reflexion months before,
This is how I saw things:
I didn't see what I think you call the C++ REST SDK project (I suppose you mean the structure as it is presented in their repository) as the C++ REST SDK library itself (I'm not saying you don't see it the same way). What I saw as cpprest library, is what is in the cpprest directory in include directory and the sources in the src directory. The other files and directories are just a way of structuring a project. I concieved granada as a layer on top of cpprest that should be integrated respecting the structure proposed by Microsoft developpers.
I agree with you, we should be able to create an empty project, and use links of both cpprest and granada without touching the respective projects.
I will look at it,
Thank you again.

Thanks for responding.  I apologize that it has taken me so long to respond myself.  I appreciate you sharing your thought process with me.  I think I do see the C++ REST SDK the same.  Your logic makes sense.  I just hadn't thought of it that way.
I would like to get your thoughts on the pros and cons of this method of integration with source code in the same tree vs. integrating as an so.  Is there a significant performance delta?  Would debugging be more difficult?  Are there other reasons you can think of to prefer one over the other?


Unit Testing - SearchDescriptor cannot be mocked

I would like to create mock objects of SearchDescriptor<T>. For instance when using NSubstitute, I would like to be able to do something like this:
var mockedSearchDescriptor = Substitute.For<ISearchDescriptor<MyType>>();

Unfortunately the SearchDescriptor<T> class does not have an interface that holds all its public members.
As a workaround I had to use the Adapter pattern as follows:
public interface ISearchDescriptorAdapter<T> where T : class
{
	SearchDescriptor<T> Type(Types type);
	SearchDescriptor<T> Index(Indices index);
	SearchDescriptor<T> Size(int size);

	// etc.
}

public class SearchDescriptorAdapter<T> : ISearchDescriptorAdapter<T> where T : class
{
	private readonly SearchDescriptor<T> _searchDescriptor;

	public SearchDescriptorAdapter()
	{
		_searchDescriptor = new SearchDescriptor<T>();
	}

	public SearchDescriptor<T> Type(Types type)
	{
		return _searchDescriptor.Type(type);
	}

	public SearchDescriptor<T> Index(Indices index)
	{
		return _searchDescriptor.Index(index);
	}

	public SearchDescriptor<T> Size(int size)
	{
		return _searchDescriptor.Size(size);
	}

	// etc.
}

It would now be possible to create a mocked object as follows:
var mockedSearchDescriptor = Substitute.For<ISearchDescriptorAdapter<MyType>>();

Feature request:
Create an ISearchDescriptor<T> interface that contains all public members of SearchDescriptor<T>, so that it can be mocked in a convenient way.

@mcijsouw You should be able to work with a real instance of SearchDescriptor<T>, and make assertions

on the serialized request using .DisableDirectStreaming() to capture the JSON within response.ApiCall.RequestBodyInBytes
Stub a response for a given request using InMemoryConnection

Both SearchDescriptor<T> and SearchRequest<T> implement ISearchRequest, so you should be able to create a stub ISearchRequest if you need to, but I don't think you need to, nor stub  SearchDescriptor<T>. Could you explain a little more about how you're unit testing?

@russcam Thanks for your input, that is an alternative approach I will keep in mind.
In my code I'm building a SearchDescriptor dynamically, based on various settings, user input, etc. For instance, I would like to parse query string parameters such as /api/controller/method?top=50 as follows:
public static class TopQueryParameterProcessor : IQueryParameterProcessor
{
	public static void Apply<T>(ISearchDescriptor<T> query, string value) where T : class
	{
		var maxSize = 10000;

		if (int.TryParse(value, out int size))
		{
			size = Math.Min(Math.Max(0, size), maxSize);
			query.Size(size);
		}
	}
}

To verify that the query.Skip method is invoked with the expected value, I would like to write my unit test as follows:
[TestMethod]
public void ShouldApplyTopParameter()
{
	var query = Substitute.For<ISearchDescriptor<MyEntity>>();
	TopQueryParameterProcessor.Apply(query, "37");

	// Assert
	query.Received(1).Top(37);
}

Unfortunately this is not possible at the moment because ISearchDescriptor does not exist. Serializing the request, capturing the query in JSON format, and then verifying the request feels a little cumbersome...

@mcijsouw You can assert this easily with
void Main()
{
    var searchDescriptor = new SearchDescriptor<MyEntity>();
    searchDescriptor.Size(10);

    ISearchRequest request = searchDescriptor;

    // assert with the test framework of your choice
    Console.WriteLine(request.Size == 10);
}

Since SearchDescriptor<T> implements ISearchRequest (explicitly).

@mcijsouw have you had a chance to look at using ISearchRequest within your unit tests?

@mcijsouw We’re closing this issue due to inactivity; if you’re still in need of resolution, feel free to re-open with the additional details 👍


Use CAM service account for broker commands

Use CAM service account credentials for orchestrate broker commands so user doesn't have to generate an API token so often (currently expire in 2 hours)

Authentication was put in place. Broker commands are still expecting the API_TOKEN from the environment. Update commands to use project and deployment parameters instead.


Serve all the public directory

The command artisan serve needs to serve all the public directory for delivering assets.

It was built only thanks to documentations.
Kind regards,

The command currently follows its sister command in laravel/framework. What is the use case that requires these changes?

In laravel/laravel the server.php file is in the root of the project.
So, when the docroot option is not given, the server do not deliver the right file when the server file return false.
The php server is probably seeking around the base path.

Ahh, I get it. Okay, I'll merge.

Thanks!


[Update Request]: Discord 64-bit version

What type of update are you requesting?
A new locale, architecture, or installer type of an existing version
Current Package Identifier
Discord.Discord
Package Version
1.0.9028
Please describe the changes you would like to see
The current Discord that is provided is 32bit only, can you include the 64bit version that is available at:
https://dl.discordapp.net/distro/app/stable/win/x64/1.0.9028/DiscordSetup.exe
Thank you

@xAphex - There's no v1.0.9028 present in the repository. Do you mean v1.0.9030?
D:\Workloads\winget-pkgs [master ≡]> winget search -e Discord.Discord --versions
已找到 Discord [Discord.Discord]
版本
--------
1.0.9030
1.0.9025
1.0.9024
1.0.9023
1.0.9018
1.0.9017
1.0.9016
1.0.9015
1.0.9013
1.0.9012
1.0.9011
1.0.9010
1.0.9008
1.0.9007
1.0.9006
1.0.9005
1.0.9004
D:\Workloads\winget-pkgs [master ≡]> winget show -e Discord.Discord
已找到 Discord [Discord.Discord]
版本: 1.0.9030
发布者: Discord Inc.
发布服务器 URL: https://discord.com
发布服务器支持 URL: https://support.discord.com
作者: Discord Inc.
描述: Discord 是最简单易用的通讯工具,兼具语音、视频以及文字信息功能。您可以聊聊天,拉拉家常,一起玩耍,与好友和社区保持紧密联系。
主页: https://discord.com
许可证: 专有软件
许可证 URL: https://discord.com/terms
隐私 URL: https://discord.com/privacy
版权所有: Copyright (c) 2023 Discord Inc. All rights reserved.
发行说明 URL: https://discord.com/blog/discord-update-june-22-2023-changelog
购买 URL： https://discord.com/nitro
标记：
  开黑
  游戏
  聊天
  语音
  语音聊天
安装：
  安装程序类型： exe
  安装程序区域设置： en-US
  安装程序 URL： https://discord.com/api/downloads/distributions/app/installers/latest?channel=stable&platform=win&arch=x86
  安装程序 SHA256： d85eb0787c08183f26c90213958966b1f7a3c11871060f338007a2bef15b3be7
  发布日期: 2023-12-13

The direct link doesn't work for me (even tried it on my personal laptop with my Discord creds), but this news article says:

The support for using a PC with a Windows 32-bit operating system is getting smaller and smaller. This week, the gaming-themed online messaging service Discord announced it would end its support for running its Windows app client on Windows 32-bit operating systems on December 1, 2023.

Based on this, should the x86 version be omitted in future manifests?

This is part of a small trend of applications halting 32-bit development in recent months. Including Git.

Winget is showing x86 upgrade for x64 discord package
The following packages have an upgrade available, but require explicit targeting for upgrade:
Name         Id                           Version           Available           Source
------------------------------------------------------------------------
Discord       Discord.Discord      1.0.9028        1.0.9030            winget

Latest version for x86 is 1.0.9030
Latest version for x64 is 1.0.9028


No response of the modal window to a click on a static background (data-bs-backdrop="static", data-backdrop="static").

When you click on the static background, the modal window pulsates slightly. This is achieved by assigning the model-static class and the overflow-y: hidden; style.
https://getbootstrap.com/docs/5.0/components/modal/#static-backdrop
In my opinion overflow-y: hidden; it is necessary before the animation, so that the animation does not cause the scroll bar when the modal window is enlarged, this can happen if the content almost completely fills the window.

I will update the Modal asap. Thanks

I will update the Modal asap. Thanks


style: Enable method-signature-style TypeScript ESLint rule

Added method-signature-style rule to ESLint rules with default property mode.
Resolves #1578

Good work! Looks like this caught a few places where our types weren't quite correct and we could have potentially done something not safe in the future


Feat: Tag Folder

https://github.com/vrtmrz/obsidian-tagfolder/issues/57#issuecomment-1374740807


Generate Vagrant Boxes with various kernel versions for nightly tests

This ticket tracks the testing of Cilium against a variety of kernel versions. We want all LTS Ubuntu releases. We should also figure out what users are using as well. This will set up for having test plans running against a variety of kernels as requested in #824 and nightly test runs in #1503 .

This is done with the net-next box. Yay!


Controller Support

Add support for user input from controllers: either Xbox, PS, or both. Support 2 players to start

Question: What is the max number of players? 4 or 8?


updating main intro text

Looks like this:

Coverage increased (+0.02%) to 83.643% when pulling f748e647e346aab2295028a803aed22099196842 on antgonza:update-main-page into e3e28ee9026ada023eec55b865caca4a4229607d on biocore:master.

@ackermag @ElDeveloper
do you have a chance to take a look at the text changes presented here?
Thanks!