Aliasing undesirable field names

It seems like what a lot of people find undesirable about PostGraphQL is how fields are named. How can we build a system (whether it be a JSON map or otherwise) which allows people to rename automatically named fields?
Any ideas are welcome, I'm have no ideas at the moment.

How about implementing the alias by reflection over the GraphQL schema?
Basically just copy everything but the name.
Since the schema and the types can easily be queried using__schema and __types it's easy and doesn't impact performance as the resolving functions are identical.
This feature could be included in the GraphQL-JS library seperate from PostGraphQL.
I'm unsure when this should happen. At Postgres reflection time, node.js server initalizing, sowhere in between?

Isn't this what you're looking for?

@burkhardr No, that's not what where are trying to achieve. We want to alias the Query-definitions, because the Relay-compliant schemas aren't that human friendly.
Example: Alias users[0].posts[0].name means usersNodes[0].edges[0].node.postsNodesByUserId.edges[0].name

Well, you could do that server-side, but the GraphQL connections / edges are named like that for a reason. The link I posted above allows you to do aliasing on the client-side, which - while not as convenient - is definitely the easier solution.

This issue discusses a server side implementation. The thing with the alias in the query is that it's just working on one level.
With the built-in alias the only thing that actually happens is that the returned key has a different name, paths can't be simplified however. The primary function for alias is to be able to request and return multiple instances in one request.
By design this GraphQL query is impossible to fulfill
´´´
{ User(id: 1) {
name,
age
},
User(id: 2) {
name,
email
}
}
´´´
Because it's impossible to return both objects on the same me key.
The aim of the discussed alias function is to make querying nicer, the builtin function just complicates the query as it's longer:
{ User1: User(id: 1) {
  name,
  age
  },
  User2: User(id: 2) {
  name,
  email
  }
}

If you think of GraphQL as a straight REST replacement, then data structures like users[0].posts[0].name make perfect sense. Unfortunately, we're dealing with a graph here, so you won't be able to simplify things like edges and nodes away without losing some of the functionality they provide (e.g. pageInfo).
If you're willing to sacrifice that for added simplicity, then this feature should be strictly opt-in.

I don't understand why the feature should be opt-in.
The aliases have to be defined manually and they don't break the generated schema as they only offer a reference to the generated schema.
Can you elaborate?

I finding a better name for fields like postNodesByAuthorId on the server is fine by me because I feel that's what a lot of people find issue with.
What do you think about using constraint names for these field names? So if the reference to person from the author_id column was named author our forward query name could be simply author and our reverse query name could be postNodesByAuthor.
Making connections optional is something I've discussed with @rattrayalex in #16. I don't really like the idea because it duplicates a lot of logic, but if enough people articulate a want/need I'll reconsider. I really think solving the postNodesByAuthorId naming solution is the best compromise.

Connections themselves shouldn't be optional. Inferring the name of the connection from the FK/column name makes sense to me, but you'll still not arrive at something like users[0].posts[0].name (you'll always have edges[], node, etc. for connections).
Sorry for the confusion. My sole argument was around not being able to boil a graph down to the same format you'd get from a classical REST endpoint without sacrificing some of its functionality.

Closing in favor of a discussion in #42.


docker: set up Dockerfile for bcd

This PR fixes the Dockerfile for the bcd program. It is the prerequisite for the Euphrates 0.3.0 local deployment.
Test plan: sudo make build-docker

lgtm 👍
curious where is this planned to be deployed btw, my understanding was this will be used in finality-provider but that is not ready yet (as we just integrated wasmd)

It will be used in babylon-deployment (once we split the IBC relayer and the consumer chain in two docker containers)


Support Elm 0.15

Cool, thank you! Are you using this library for something? If so, what kind of stuff? I wasn't sure if there'd be a demand for an upgrade for 0.15

Ah yes we are here and there - mostly for this: https://groups.google.com/forum/#!searchin/elm-discuss/focus/elm-discuss/HkLaDvr5Ck8/FKCPeEstQdsJ

Ah, gotcha, thanks :)


Could not find a declaration file for module '@antv/g2'

G2 Version: 3.2.5
Platform:widows
Mini Showcase(like screenshots):
CodePen Link:

Perhaps you changed the value of the noImplicitAny attribute in your TypeScript compiler configuration.
{ "compilerOptions":{ "noImplicitAny":false } }

thx@jackytedy


yo bro

its not an issue or sum but wanna maybe make a stealer together or sum xd

It depend on what you want to do, add me on discord felix.argyle.

sended


File size limit?

Uploading a
Creating rom spiff_rom.bin of size 196608 bytes
Adding files in directory files
Unable to read file .
Unable to read file ..
bootstrap.css.gz added to spiffs (15615 bytes)
index.html added to spiffs (2876 bytes)
jquery.js.gz added to spiffs (30153 bytes)

Is there anything that could prevent 30K file to appear on the file system?

sorry I haven't had time to check. It might be a file extension based exclusion, or something else

Have you had chance to look at this?
If i build a spiffs with small 14 byte files they work fine.  If I build a spiffs with larger files (15-30kb) then the files get corrupted on the fs.


Invalid CA Certificate error for MQTT with TLS

I am connecting to MQTT broker which is protected. I have created below component spec based on details which work with a software like MQTT Explorer to connect to the broker from my machine.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mqttpubsub
spec:
type: pubsub.mqtt
version: v1
metadata:

name: url
value: "mqtt://brokeraddress:8883"
name: consumerID
value: consumerId
name: qos
value: 1
name: retain
value: "false"
name: cleanSession
value: "false"
name: backoffMaxRetries
value: "0"
name: caCert  #ca.pem
secretKeyRef:
name: caCert
key: caCert
name: clientCert
secretKeyRef:
name: clientCert
key: clientCert
name: clientKey
secretKeyRef:
name: clientKey
key: clientKey
auth:
secretStore: secretstore

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: secretstore
spec:
type: secretstores.local.file
version: v1
metadata:

name: secretsFile
value: secrets.json
name: nestedSeparator
value: ":"
name: multiValued
value: "false"

Secrets.json is stored in project directory.
However this does not work and i get following error.
error initializing pub sub pubsub.mqtt/v1: mqtt pub sub error: invalid ca certificate"
Do anyone or Dapr team have this use case implementation including certificates. because there are zero details provided anywhere!

hi, I have exactly same problem now. @mandarj123 have you resolved your issue?
I asked similar question in contrib: https://github.com/dapr/components-contrib/issues/2401
It will be nice to get some help on this?


site.ImagesUrl not replaced on translation

Hello @madoublet
there is an issue with translations and site.ImagesUrl params.
TEST CASE:
create new website
load an image element from editor and upload a new image
activate the language menu btn
reload the website
switch to another language
you will see the image won't be loaded and inside the url there is the site.ImagesUrl param not replaced.
I've created a demo website to let you try:
Go to: https://demo.respondcms.com/sites/imagetest/
Click on translate button and select FR.
Some method will replace the original URL with {{site.ImagesUrl}}files/mountains.png
Please, could you confirm ?
Thank you

IMO the problem is inside the translation method which is going to replace the image-x string.
Looking at the translation json file there is the same value "{{site.ImagesUrl}}files/mountains.png"

Confirmed. Setting FR as default language the image src will work but EN language is broken.

Here is the fix:
File: /site/js/respond.site.js Function i18n
line #117
// return i18n.t(text);	 #here we need to replace site.ImagesUrl with current domain
var t = i18n.t(text);
return this.replaceAll(t, '{{site.ImagesUrl}}', respond.site.settings.Domain + '/');

Enjoy!

I checked your test case and confirmed the issue.
I would be glad to apply this fix, but first I want to make sure I fully understand the issue.  I don't use the language translation feature, so I have never looked at how it works.
I see why the default language works.  It's because the {{site.ImagesUrl}} is replaced at the time the site is published into .html files.
What I don't understand is what causes the {{site.ImagesUrl}} to reappear when the language is switched.  Does the site retrieve and re-render the layout template when a new language is selected?
I appreciate any explanations you can provide - as well as your patience - while I work to better understand what is happening here.

This happens because the {{site.ImagesUrl}} is stored inside the translation json file (translation does not build other html files, this is just stored inside a json file and deployed).
So at the time of translation this must be replaced with the site base url.


Using Gsuite as IDP gives Error: app_not_configured_for_user

That’s an error.

Error: app_not_configured_for_user
Service is not configured for this user.
Request Details
idpid=C034yuk6
SAMLRequest=fVNdj9owEHznV6C8kw8SjmJBThT6gcRBBGkf+lIt9gasJrZrOz3u39dJuEKrHpasSOud8cx4MzVQlYrMa3sSgO/xZo7G9vlvnqhSGtIczr9aCSDDcEAEVGmIp2c+f1mToh0RpaSWVpfcP7D4KjEFtuRQdbLWcedvNh/X202rzfRRFNBljDPgQTkY0ZkVSjPBdmABM4MAmyaEYD4sQO+hX1MbxzDxH6/U6NmNqXAljQVhXD6PxIIwHwyiPYhJHJAm/ddClM8sF2BZ+slYZEggRAqayFNf5RymOJPpVVIIPG0TDgTD26zdlsEcZi+BL/eOiYsksI77lgXBzvez90TYZ8zvNskG33eUcyf81kIYWpK9R71L84xS+79VVeCQoaTb5QAcNKRoFjw7OvTuoRqPHSlmra6CVtDjp9G1gqhBQYWGvQ0uMVcWRTZOAerZSZLTl/aerM+Sl2Bfgdto5EdthbNB0baSWhiFlBccmfeHZl6W8nmhESzOPKtr9PrBX5dfZhJZO6EuGYtn21/ISoHmpnk4PAO1F99X77fti9KN2w6L9O5EUkKbPlfO3OdZata8KlJ3d67BiZfaXkL6L3mnOrgjO+29Ht/+bulv
RelayState=http://lapa.com.np/demo1/

That’s all we know.

I tested the php-saml toolkit with Google IdP and worked.
Can you provide more info? Where you get the error? On the IdP or at the SP?

At this thread I read that the issue is related with the fact that you have not provided the right ACS URL at Google settings.
https://github.com/omniauth/omniauth-saml/issues/116

Can i send in the details here personally?
On Tue, Mar 21, 2017 at 8:48 PM Sixto Martin<EMAIL_ADDRESS>wrote:

At this thread I read that the issue is related with the fact that you
have not provided the right ACS URL at Google settings.
omniauth/omniauth-saml#116
https://github.com/omniauth/omniauth-saml/issues/116
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/onelogin/php-saml/issues/204#issuecomment-288106936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYQmE5TB7HT0dUk33AhjCnmkfB8l675Zks5rn-ajgaJpZM4Mj1RJ
.

--
Regards
Sajan Maharjan
Software Developer
www.sajanmaharjan.com.np

You can send here, but omit the private key and other info that you consider private.

Thank you.
Here is the screenshot of the admin settings
[image: Inline image 1]
Here is the metadata
http://www.lapa.com.np/demo1/metadata.php
You can login from the following url
http://www.lapa.com.np/demo1/
And you can try logging in with the given email and pw for lapa.com.np
email<EMAIL_ADDRESS>password: test123#
On Tue, Mar 21, 2017 at 8:51 PM, Sixto Martin<EMAIL_ADDRESS>wrote:

You can send here, but omit the private key and other info that you
consider private.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/onelogin/php-saml/issues/204#issuecomment-288108119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYQmExJB8zNEIWc5OF3OVPBfEUQ7_cdAks5rn-eDgaJpZM4Mj1RJ
.

--
Regards
Sajan Maharjan
Software Developer
www.sajanmaharjan.com.np

Update:
When i login to the google user apps hub, and open the application from there, it logs in correctly. The above error only appears when i try to login from the php-saml application.

Can you upload the screenshot again? I'm not able to see it.
Also share the php-saml settings

What was the issue?

#213


add "init templates" cmd, used to list templates in format

What type of PR is this?
feature

What this PR does / why we need it:
list init templates from local or online, support json format. Hence, user can parse the specific elements of the templates.
Which issue(s) this PR fixes:

Fixes #265
Special notes for your reviewer:
If the cmd failed, the output is not in json format, even if "--output=json" is specified.
Does this PR introduce a user-facing change?

None

Additional documentation e.g., design docs, usage docs, etc.:

kusion init templates command helps you get the templates which are used to generate a scaffolding KCL project.
Here are the examples:
# Get name and description of internal templates
  kusion init templates
# Get templates from specific templates location, and output in json format
  kusion init templates https://github.com/<user>/<repo> --online=true --output=json

I have read the CLA Document and I hereby sign the CLA

@healthjyk please add an example output for this command

an successful output is like:

@healthjyk please add an example output for this command

an successful request is like:

@healthjyk please add an example output for this command

an successful request is like:
[
{
"dir": "/${userName}/.kusionup/current/templates/external/code-city",
"name": "code-city",
"projectName": "code-city",
"description": "Code City metaphor for visualizing Go source code in 3D.",
"quickstart": "kusion compile main.k -Y ci-test/settings.yaml",
"projectFields": [
{
"name": "AppName",
"description": "App name. Default to 'gocity'.",
"type": "string",
"default": "gocity"
},
{
"name": "ContainerPort",
"description": "The number of port to expose on the container's IP address.",
"type": "int",
"default": 4000
},
{
"name": "ServicePort",
"description": "The port that will be exposed by this service.",
"type": "int",
"default": 4000
}
],
"stacks": [
{
"name": "dev",
"fields": [
{
"name": "Image",
"description": "Docker image address of gocity. Default to 'yuanhao1223/gocity:latest'.",
"type": "string",
"default": "howieyuen/gocity:latest"
}
]
}
]
}
]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

102 of 153 (66.67%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 71.928%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/cmd/init/init.go
18
27
66.67%

pkg/cmd/init/options.go
84
126
66.67%

Files with Coverage Reduction
New Missed Lines
%

pkg/cmd/init/options.go
2
69.9%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
4858

Relevant Lines:
6754

💛  - Coveralls

The error message should output to stderr, but now the wrong git repo url will result in an error ouput in stdout. :
kusion init templates https://github.com/KusionStack/no-exist --online=true -o json
❌  no templates
kusion init templates KusionStack/kusion-templates.git --online=true -o json
❌  template 'kusionstack/kusion-templates.git' not found
kusion init templates https://github.com/kusion-templates.git --online=true -o json
❌  failed to retrieve git folder: invalid Git URL


Make the device play a sad tone if a request times out

implemented as of https://github.com/ComputerScienceHouse/letmein2/commit/a0ceff5388759fdbbb1a736703daeda52dc5cacb


[new idea] Adding expense tracker app in intermediate section

Is your feature request related to a problem? Please describe.
I am always frustrated when it comes for tracking my daily expenses. As tracking my total earning and daily expenses, I always get lost counting on my hands. This is not mine only but I think everyone's problem
Describe the solution you'd like
The simple and effective solution would be making a simple expense tracker app which takes total earnings in a month or day or week and takes the expense of daily and providing the current remaining balance to the user

Feel free to create a project like that by following the structure and I'll approve it.


Remove unnecessary calls to off() that trigger deprecation warnings

Followup to #1722.

why do you think that these are unnecessary? wouldn't it lead to memory-leaks if we removed them?

Believe it's ok because the original code was immediately putting the event handlers back on after just removing them.
I tested that multiple calls to on() with identical arguments doesn't result in the specified function being called multiple times, i.e. it doesn't allow the same [context, function] pair to be registered more than once. That means that the off() calls removed in this PR weren't ever doing much anyway.
Thoughts?


carla_spawn_objects.py中断后再次运行报错

E0518 10:16:42.794441 12779 node_manager.cc:101] [spawn_objects] this process will be terminated due to duplicated node[carla_spawn_objects], please ensure that each node has a unique name.

Under normal circumstances, you need to enter CTRL+C on the keyboard, and you need to close the terminal about bridge.py.
In addition, I can’t see your picture.

当我重启整个环境，问题就解决了


Replace pkg_resources with pkgutil.

pkg_resources (part of setuptools) is overkill for reading resource files. The standard library module pkgutil can do that just fine.

Hi, Benjamin. Thank you for submitting the PR. I have a few thoughts about this problem. As you said, the building process of the project depends on setuptools and pkg_resources came for free. Also, pkg_resources are used through out the project in many places, it is better to use one package consistently. Can you provide stronger reasoning to migrate to pkgutil?

Hi, Benjamin. Thank you for submitting the PR. I have a few thoughts about this problem. As you said, the building process of the project depends on setuptools and pkg_resources came for free. Also, pkg_resources are used through out the project in many places, it is better to use one package consistently. Can you provide stronger reasoning to migrate to pkgutil?

Just because setuptools is required in the build environment doesn't mean it needs to be required in the runtime environment. It should be possible to install a grpcio wheel into any environment which has just the packages in install_requires

pkg_resources does a huge amount of IO at import-time. Importing it is the death of any program that needs a quick startup time.

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,191      Total (<)     11,116,193

 No significant differences in binary sizes

Latest update applies yapf.

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,199      Total (=)     11,116,199

 No significant differences in binary sizes

Thank you for the review, lidizheng! Are you also the right person to look at #16916?


Data source for the CircleCI IP addresses

Would be helpful to have a data source that provides the IP addresses from https://circleci.com/docs/2.0/ip-ranges/ with attributes for the different ranges and all combined.
I currently do something like for ip in $(dig +short jobs.knownips.circleci.com); do aws ec2 authorize-security-group-ingress --group-id sg-018b811ddb76d3134 --protocol tcp --port 22 --cidr "${ip}/32" --region us-east-2; done. Would be nice to do this in Terraform.

This is how I've solved it without needing this specific provider.
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.46.0"
    }
    dns = {
      source  = "hashicorp/dns"
      version = "3.2.4"
    }
  }
}

provider "aws" {
  <your config here>
}

# this provider can be left empty
provider "dns" {}

data "dns_a_record_set" "circleci" {
  host = "jobs.knownips.circleci.com"
}

resource "aws_security_group" "circleci" {
  name        = "circleci"
  vpc_id      = aws_vpc.main.id
}

resource "aws_security_group_rule" "circleci" {
  security_group_id = aws_security_group.circleci.id

  protocol    = "tcp"
  type        = "ingress"
  to_port     = <yourport>
  from_port   = <yourport>
  cidr_blocks = [for k, v in data.dns_a_record_set.circleci.addrs : "${v}/32"]
  description = "Allow CircleCI"
}

Cool, i didn't even think to check if there was a generic DNS lookup provider!


Parse meta data in headers more consistently

This is a rewrite of the getMeta() to take into account what look like inconsistencies and to hopefully add extra useful information (separating name into name + long description). I've added a couple of tests, but it would be great to include some more to make sure this changeset doesn't break anything.
NOTE: this includes minor changes to the existing tests, so there may be some potential knock-on effects upstream. Please check carefully before accepting.
Issue: UniProt key=value descriptions can contain spaces
e.g.
OS=Homo sapiens
(added test and fixed)
Feature: the 'name' is now separated into the accession and an (optional) description
e.g
sp|abc|accession a long description OS=organism GN=genename
was:
{
  name: "accession a long description",
  ids: { sp: "abc" },
  details: { os: "organism", gn: "genename", en: "accession" }
}

now:
{
  name: "accession",
  desc: "a long description",
  ids: { sp: "abc" },
  details: { os: "organism", gn: "genename", en: "def" }
}

By the way, after I made these suggested changes I realised that this function is used as a generic parser rather than just to parse FASTA headers. I haven't really checked whether it does sensible things to other sequence formats.

By the way, after I made these suggested changes I realised that this function is used as a generic parser rather than just to parse FASTA headers. I haven't really checked whether it does sensible things to other sequence formats.

Currently only Fasta & Clustal are supported and my experience shows that either a similar header as in Fasta is used, or a very simple one.
Anyhow I just looked at your changes and they look great - seems like you understand the FASTA format better than myself ;-)
Thank you!


Replay fails due to maybe the navigation bar height

A recent test shows that some touches are too "low". They are actually above the navbar but when replaying they go too further, which messes thing up. So when calculating where to touch, the height of navbar should be considered.

found the reason.
The screen size (in pixel) obtained from the dumsys/getprop is different from that obtained from adb -lp.


[image_picker] crash when opening gallery more than once at ios 14

Configuration:

image_picker: ^0.6.7+11
Flutter 1.22.0 • channel stable

Issue:

Open gallery using this code

 final pickedImage = await picker.getImage(
      source: ImageSource.gallery,
      maxWidth: widget.containerWidth,
  );

select the image from gallery
reopen gallery using the first code again
the app crash

@t0n1zz have you solved this issue?

no, i just closed it because there is already been asked here
https://github.com/flutter/flutter/issues/66322

i face this problem too , any solution ? @t0n1zz

Just found a temporary fix by waiting a small duration before getting the image:
    await Future.delayed(Duration(milliseconds: 500));
    var pickedFile = await picker.getImage(
      source: source,
      imageQuality: ImageSource.gallery,
      maxWidth: 750,
    );

I think the issue is triggered when touching the screen while the native platform gallery becomes visible. Waiting half a second prevents this. Not the prettiest solution, but seems to work until the Flutter team fixes the main issue.


Setting up log file location for PhantomJSDriverService?

there are no easy way for java code to control name/location of the phantomjsdriver.log.
In org.openqa.selenium.chrome.ChromeDriverService, the log file can be set with a system property, could this do the same thing?

I have to agree with @denisa, @kennardconsulting and @myoffe on this. Currently I can't see a simple way of changing the log file name/path. We have to rewrite the builder code from createDefaultService:
new Builder().usingPhantomJSExecutable(phantomjsfile)
                .usingGhostDriver(ghostDriverfile)
                .usingAnyFreePort()
                .withProxy(proxy)
                .withLogFile(new File(PHANTOMJS_DEFAULT_LOGFILE))
                .usingCommandLineArguments(
                        findCLIArgumentsFromCaps(desiredCapabilities, PHANTOMJS_CLI_ARGS))
                .usingGhostDriverCommandLineArguments(
                        findCLIArgumentsFromCaps(desiredCapabilities, PHANTOMJS_GHOSTDRIVER_CLI_ARGS))
                .build();

but most of the properties are built using some protected static methods from the PhantomJSDriverService class, so there's really a lot of copying required to create a new instance of it.
If you could just expose the default service builder as suggested by @stembrain, everything would work out nicely.

As far as I can tell, the others are correct that it's currently impossible to specify a logfile without also re-implementing some other stuff. Given this, would a pull request that exposes the builder itself be accepted?


Add Archlinux to params

seems to work without any other modifications
Notice: /Stage[main]/Consul::Run_service/Service[consul]/ensure: ensure changed 'stopped' to 'running'

Archlinux only has official support for systemd

@vdloo This is great :tada:
But a few things...

Can you add the supported versions of arch linux? It doesn't have to be anything exhaustive but what you know.
Can we write a unit test for this? Here is an example

Thanks :smile:

Sure, but because of arch's rolling release system there aren't really versions like in Debian or RedHat though. I put in the 'operatingsystemrelease' that facter returned on my system but that's just the kernel version and can change between releases. So if the metadata.json is going to stay current it's probably going to need to be changed a couple times a month.
# facter operatingsystemrelease
4.1.5-1-ARCH

@vdloo actually, lets do something like this.

:100:
:bullettrain_side: LGTM

Thanks!


parameter dev-center-name is incorrect in the document

[Enter feedback here]
The learn document “Microsoft Dev Box Preview Azure CLI reference” found at Microsoft Dev Box Preview Azure CLI Reference - Microsoft Dev Box Preview | Microsoft Learn contains typographic errors.  I’m identifying two of them here.
az devcenter dev dev-box list --devcenter {devCenterName} `
az devcenter admin devbox-definition list --devcenter-name "Contoso" --resource-group "rg1"
The command format parameter for “dev-center-name” is incorrect throughout the document.  I have not tried every example command.
The CLI module reports the proper format for the command in the errors when encountering the malformed parameter and indicates that it should be
--dev-center-name

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

ID: 032e33b5-11fe-3b45-89a2-8062e2a7a2ab
Version Independent ID: db28072a-95c7-247c-6104-a42a3a5f2c31
Content: Microsoft Dev Box Preview Azure CLI Reference - Microsoft Dev Box Preview
Content Source: articles/dev-box/cli-reference-subset.md
Service: dev-box
GitHub Login: @RoseHJM
Microsoft Alias: rosemalcolm

@superjoe2000
Thanks for your feedback! We will investigate and update as appropriate.

Hi @superjoe, thank you for taking the time to share your ideas and feedback to help improve our documentation. I apologize for the delayed response. This article will soon be replaced by the auto-generated CLI reference documentation, which will be more consistent. For now, I've updated the --devcenter-name parameter to --dev-center-name throughout.
Thanks for your patience, and please know that we appreciate your contributions to keeping the documentation up to date.
#please-close


Fix typo in _write.parquet.py/store_parquet_metadata doc

Description of changes:
I just noticed that the letters of MSCK REPAIR TABLE in the documentation of awswrangler.s3.store_parquet_metadata are swapped. This PR fixes the typo.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: 0914606cc2c5c8a889eb59342083cb28d0233145
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-pDO66x4b9gEu
Commit ID: ddd238a024c5bf496c1c8f1d4b291b23a0a7424e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


relay option question

Hey Garrett thanks for an awesome tool its been really useful on many engagements. I have just one proposal to improve if not lot of effort is needed. The relay option, you implemented the option to add new computer account which is great but not all the time machine account quota is misconfigured, so I was thinking would it even be possible to utilize coercion(Poldarius Coercer) in order to obtain machine account hashes and then relay it to MECM/SCCM HTTP endpoint and then utilize the sccmwtf.py module to obtain policy file.

Love to hear it! And true that is a limitation if the MAQ is blocking you from doing much with it. About the relay though yes at some point in the future I'd like to implement the relay that @Tw1sm already wrote and is currently a PR for Impacket. If that gets merged I'd likely import the changes to sccmhunter.  That PR is here: https://github.com/fortra/impacket/pull/1425. But yes it is completely possible to coerce the enrollment.

Oh wasn't aware of that. Great news, thanks!


Allow overriding drawables locally (only for a specific PlayerView instance)

[REQUIRED] Use case description
My app has two players: video player and podcast player. Both should look different in terms of icons, buttons' positions, and spacing. Spacing and reordering buttons is easy, but it seems that the only option to replace icons is to do it globally1, for all PlayerViews.
Proposed solution
It would be great to have attributes similar to show_timeout2 for icons/resources used in the PlayerControlView.
e.g.:

play_resource_id
pause_resource_id
etc.

with the fallback to exo_styled_controls_play, exo_styled_controls_pause, .. if not present.
Alternatives considered
No alternatives were considered.

Ref.:

[1] https://exoplayer.dev/ui-components.html#overriding-drawables
[2] https://github.com/androidx/media/blob/release/libraries/ui/src/main/java/androidx/media3/ui/PlayerControlView.java#L102-L166

Please correct me if I'm wrong. Do I understand that you want:
playResourceId =
   a.getResourceId(R.styleable.PlayerView_play_resource_id,
                  /* defValue= */ R.drawable.exo_styled_controls_play);

and then you can define various xml views
app:play_resource_id="R.drawable.personal_controls_play"
or
app:play_resource_id="R.drawable.personal_controls_play_new"
and
<drawable name="personal_controls_play">@drawable/personal_play_circle_filled</drawable>
<drawable name="personal_controls_play_new">@drawable/personal_play_square</drawable>

Yes, exactly

Do you have any updates on this ticket?

Hi @ziem, apologies, I have been away for a month. I discussed this internally within the team and I don't see any issue with the proposed solution above. I will prioritise it next week and hopefully you can test it out in 1.4.0-alpha02.

Awesome, thank you 🙂


Added an api_timeout parameter to XMLRPC Client

In cases where launching many machines in parallel, the XMLRPC Client's
default timeout of 30 seconds wasn't long enough. This adds an optional
parameter to increase the timeout.

Nice thanks!


Staking flag never set to true

In the GetStakingInfoModel class, the property bool Staking is not set to true when the node starts staking.
It's only set to true when staking is resumed.
Repro steps:

have a wallet with funds
start staking
check that staking works
call the api/staking/getstakinginfo endpoint
see that enabled is set to true but staking is set to false.

Resolved


How to interpret inheritance with and without @discriminator

Say we have inheritance case without discriminator decorator(playground).  We have Pet as request body in create operation. I was wondering how to interpret this in the semantic:

Do we have inheritance releationship between Pet and Cat | Pet? Or just the composization relationship due Cat contains all properties of Pet?
Do we allow Cat or Dog as valid parameter in operation create?

The same questions are for enabling the decorator @discriminator("kind"). Are Cat or Dog valid parameters in operation create?
// @discriminator("kind")
model Pet {
  name: string;
  weight?: float32;
}
model Cat extends Pet {
  kind: "cat";
  meow: int32;
}
model Dog extends Pet {
  kind: "dog";
  bark: string;
}
op create(@body body: Pet): void;

extends is meant to describe inheritance relationship between models. Now it is true that without a discriminator you cannot deserialize to the write model.
There "could" be some valid reason to use inheritance without a discriminator but if you reference the base model you probably made an error and maybe you just meant to use composition via spread(... or model is) . We have an issue to lint against that scenario for azure specs https://github.com/Azure/typespec-azure/issues/3510.

Let me ask more direct - Do we have any implicit information the Cat is not allowed for that method in above example?

After talking with @MaryGao offline, I'll clarify a few things.
From a pure typespec point of view the example above is totally correct and an operation would allow a Cat model or Dog model to be passed to create.
If we think for example of typespec as a way to generate typescript interfaces(Or any other language) but that doesn't involve any serialization then there is no reason this shouldn't be allowed. An example of this use case is generation of the decorators typescript types form the typespec definition.
But as pointed in previous reply as soon as serialization is involved you are not able to deserialize the Cat or Dog model as you can't know which one it was without some discriminator. So in the case of an http library it definitely has little to no value to write that. If you want to support it, it is fine but this is also no something I would ever expect to be used correctly.

For tsp, it is valid. But I don't think it is valid for http. There is no good to write this but will involve lots of problems including ser/deser problem.

I have what is possibly a comparable interpretation, though I'm not entirely sure. Sharing in case it helps.
From my perspective, ignoring decorators, I would not expect an emitter or serializer to handle subclasses of a base class given an operation like op create(@body body: Pet): void;. To me, this says this operation takes a Pet and will serialize a Pet. Whether subclasses of Pet could be passed in to a generated operation or not would depend on the language, but as far as the serializer is concerned, the expectation is that the endpoint wants a Pet and a Pet only.
The fix to this interpretation is to be specific. Again in the absence of any decorators, that would mean doing something like: op create(@body body: Cat | Dog): void;. Now this clearly means you can pass one of these pets. We generate the corresponding OpenAPI from such a definition, but as noted, deserialization becomes problematic for typed languages. There are potential strategies for handling this, including writing a linter flagging such usages of non-discriminated unions.
As far as I'm concerned, the fact that adding @discriminator to the base type makes references to the base type behave as if its a union of all of its subtypes is a strange thing™, and have on numerous occasions wished I could delete it in favor of just allowing @discriminator on union declarations. This approach is more clear and more flexible, e.g. works in cases where you want to allow a Dog and a Cat but not a Lizard for some endpoints, though has the (IMO minor) cost of having to declare an additional union of all the base types if that's something you need.

Maybe I misunderstood, but can we treat inheritance and polymorphism two different things?
Inheritance is just reuse some of the  the base class stuff like properties methods, which means there's no way to call a subclass method via a baseclass pointers, therefore everywhere a base class exists can not be replaced by any of its subclasses, in those scenarios, base class are just normal class.
but if we want to change the runtime or compile behavior according to the type. in this case, we could use a base class pointers to call a sub class method, we have to specify discriminator to indicate there's a polymorphism here,
which means in the above case,
@discriminator("kind")
model Pet {
  name: string;
  weight?: float32;
}

we got an operation here op create(@body body: Pet): void;  any places Pet exists can be replaced by all its subclass and fallback to itself if no subclass matches.

Whether subclasses of Pet could be passed in to a generated operation or not would depend on the language.

Service team just leverages typespec to express their backend contract, regarding the above statement op create(@body body: Pet): void; do we have a clear answer for them - the body is open for Pet and its subclasses OR the body is in a closed state and only open to accept Pet objects?
If this is a general question for all services then emitter could follow that, if it is a case-by-case decision then emitter could do nothing.

The fact that adding @discriminator to the base type makes references to the base type behave as if its a union of all of its subtypes is a strange thing

It looks like magic to me. @discriminator is not just pointing discriminator property but like a syntax sugar.
// Case 1: with discrinminator
@discriminator("kind")
model Pet {
  name: string;
  weight?: float32;
}
model Cat extends Pet {
  kind: "cat";
  meow: int32;
}
model Dog extends Pet {
  kind: "dog";
  bark: string;
}
op create(@body body: Pet): void;

// Case 2: without discrinminator
model Pet {
  name: string;
  kind: string;
  weight?: float32;
}
model Cat extends Pet {
  kind: "cat";
  meow: int32;
}
model Dog extends Pet {
  kind: "dog";
  bark: string;
}
op create(@body body: Cat | Dog): void;

Maybe I misunderstood, but can we treat inheritance and polymorphism two different things?

I consider them separate from an API definition standpoint, but they cannot be separated for all emit targets where inheritance implies polymorphism. But I think this is fine.

but if we want to change the runtime or compile behavior according to the type. in this case, we could use a base class pointers to call a sub class method, we have to specify discriminator to indicate there's a polymorphism here,

I believe that is the intention of the @discriminator-on-base-class, but is the behavior I'm skeptical about and would prefer being explicit with unions.

Service team leverages typespec to express their backend contract, regarding the above statement op create(@body body: Pet): void; do we have a clear answer for them - the body is open for Pet and its subclasses OR the body is in a closed state and only open to accept Pet objects?

IMO the contract is simply that the service will take a Pet and may or may not support additional properties depending on convention we prefer. The default position would be that subtypes are allowed as that aligns with the TypeSpec type system's semantics, and in general, I believe services often do accept additional properties, so any subtype of Pet would be allowed, not just those that happen to be declared in the TypeSpec (@johanste has talked to me about this before, maybe he knows more). But in either case, I don't think the presence of subclasses should affect what this code means (in the absence of @discriminator at least).

It seems that below two cases are equivalent in typespec.

They are equivalent from a type system perspective yes (and I strongly prefer the latter), however @discriminator on the union is still useful for codegen because we don't need to infer what the discriminator is and we can ensure the discriminator is present on all union members as the API evolves. So I prefer this pattern:
model PetBase {
  name: string;
  kind: string; // adding discriminator property if missing
  weight?: float32;
}
model Cat extends PetBase {
  kind: "cat";
  meow: int32;
}
model Dog extends PetBase {
  kind: "dog";
  bark: string;
}

@discriminator("kind")
union Pet {
  Cat;
  Dog;
}
op create(@body body: Pet): void;

We have also discussed allowing union to express a subtyping relationship such that all union variants must be a subtype of the specified type, so Pet could be defined as:
@discriminator("kind")
union Pet extends PetBase {
  Cat;
  Dog;
}

This effectively prevents random other types that happen to have a "kind" field from being added to the union.

Note that there is an issue around how we should encourage types using extends in Azure APIs to use discriminators here: https://github.com/Azure/typespec-azure/issues/3510

closing a sduplicate


Simplified formatting for deppy.NotSatisfiable error

Today deppy.NotSatisfiable error contains the description of the whole problem and it is not clear what exactly went wrong from the error message.
We need to explore error formatting options which:

Describes in natural language what went wrong
Does not include the description of the whole problem

I really like how pip does it. Few examples I found on the internet (probably from different pip versions):
pandas-profiling 3.6.1 requires numpy<1.24,>=1.16.0, but you have numpy 1.24.1 which is incompatible.
numba 0.54.1 requires numpy<1.21,>=1.17, but you have numpy 1.24.1 which is incompatible.

Or more complex one:
The conflict is caused by:
    The user requested six==1.10.0
    bcrypt 3.2.0 depends on six>=1.4.1
    cvxpy 1.0.25 depends on six
    django-anymail 0.5 depends on six
    django-compat 1.0.15 depends on six>=1.10.0
    django-extensions 2.2.1 depends on six>=1.2
    drf-yasg 1.16.1 depends on six>=1.10.0
    fake-factory 0.6.0 depends on six
    google-api-core 1.26.0 depends on six>=1.13.0

This repo with examples on how to format errors might be useful: https://github.com/perdasilva/deconflictor.

I updated the description of the issue beucase it was initially not factually true: I origianlly said that deppy.NotSatisfiable contains description of the whole problem. It is not true: Deppy (thanks to Gini) only produces a minimised list of assumptions which together caused unsat.
I think readability of deppy.NotSatisfiable will be greatly influenced by the approach taken to building the constraints on the users side (e.g. IDs used, and how dependencies structured).

IDs used

I think we have overlooked this particular aspect as well. We should define a standard for how to structure IDs and perhaps add a package (not sure where) to help users build IDs that will be easier to reason about.


Improve scoring engine testing

Changeset coming from suggestions on #105 from @dheerajodha.

Thank you for your time on this PR.
Also, I think this line is duplicating line 107 above it.


Building without python causes repeated failures

Later Ubuntu releases do not come with a 'python' executable (i.e. python 2.7) installed by default.  Building OpenWeave on such a system results in a failure while attempting to run the gen-oid-table.py script.  Conveniently, the generated error message properly identifies that the python command was not found.
However, as a result of this failure, the ASN1OID.h file that is checked in as part of the openweave-core source tree is replaced with an empty file.  Subsequently, any attempt to build OpenWeave, even after python 2.7 is installed, fails with the following error:
../../src/include/Weave/Support/ASN1.h:123:28: error: 'OID' has not been declared
ASN1_ERROR GetObjectId(OID& oid);

This must be corrected by reverting the ASN1OID.h file.

Can we / do we work with any version of Python or do we strictly require Python 2.7?

Unclear.  But that script is very simple, so I expect the version doesn't matter.

Regardless of the Python version question, it seems like we'll / I'll need to differentiate between the "--{enable,disable}-python" support option (which is mostly about Device Manager and Happy) and just having a Python interpreter.
Having  a Python interpreter will be flat-out required, independent of the "--{enable,disable}-python" option.
I'll take a pass at coding this up.

It would also be nice to not have a version of ASN1OID.h checked in at all, and to have the make logic generate the script in the build directory, rather than the source directory.

Addressed in https://github.com/openweave/openweave-core/pull/240.


Make the cards responsive

@JenilGajjar20 Can you please assign this issue to me under hacktoberfest ?

Go for it @reetsrivastava

@JenilGajjar20 PR raised for the same https://github.com/JenilGajjar20/React-imageGallery/pull/12
Please check and let me know.


chain: encapsulate exceptions in rejections

#chain was dropping exceptions thrown by the use provided function f. I added a test case and changed the behavior so that the returned promise is rejected.
I did not (have to) change #chainError because it's not affected by this issue. However, it is affected by a related one. If its function f throws, the first #mapError will not return a promise of a promise of an error, but a promise of an error. This type error will also be silently dropped. If you want I can create a separate pull request to fix that as well.

Great catch: thank you. Do you have a failing test case for the corresponding chainError bug? It'd probably be easier to add that as a separate commit to this pull request.

Mhh.. the Travis builds seem to be failing due to a race condition. I can reliably reproduce it for #onRejected can chain failures in the browser. The tests work with the same variables as the beforeEach block. Thus the asynchronous resolves and rejects from the beforeEach block can butt in during tests and resolve/reject a promise before the test does. An assertion will fail or the test times out if the result isn't what coincidently was expected anyway.

I can commit a failing test for the #chainError bug. However, there are other such issues. Several methods making assumptions about a value's type are affected, specifically #chainError, #concat, #reduce, and #empty*. That's why I wanted to put it into a separate PR (but I guess I could/should have said that upfront).
*) Is it possible that #empty is broken anyways? It does not work for pending promies. If that's intended, then it is not affected.

I'm less fond of beforeEach blocks these days as they make the individual test cases harder to read and, in this case, cause weird race conditions. I'm happy to look at removing these to make the individual tests more explicit and hopefully avoid the weird bugs.
As for the type errors, would be good to capture all of these so perhaps a separate PR is better.

Okay, I looked at it a bit closer today and noticed that concat is not affected. I thought the returned promise would remain pending whenever chain(other) is called with other being no promise. But due to the other.onRejected(...) chain will not return a promise in the first place.
So it's down to chain, chainError and empty. Since I'm still not sure what to make of empty I just added the test cases and changes to this PR.
Also, I committed e368eef2976f07b564fd4afcab838ffe24f26ca0 to eradicate the non-determinism from the tests. If you want I can merge it into this PR or issue a separate one.

https://github.com/mudge/pacta/commit/e368eef2976f07b564fd4afcab838ffe24f26ca0 is fantastic and your introduction of rejected() makes me think we should use test data builders for all promise types really (e.g. emptyPromise(), fulfilledPromise()) to divorce the exact constructor arguments from the tests. I'll do that now and aim to merge that before this.

Now that I'm looking at this, the bug in chain is obvious (assuming that the yielded value pb has a map function) but why doesn't the fix you applied there (wrapping in a try...catch) work for chainError? Specifically, why does the following still fail the test?
var promise = new Promise();

this.mapError(f).mapError(function (pb) {
    try {
        pb.map(function (value) {
            promise.resolve(value);
        });

        pb.onRejected(function (reason) {
            promise.reject(reason);
        });
    } catch (e) {
        promise.reject(e);
    }
});

this.map(function(value) {
    promise.resolve(value);
});

return promise;

If f throws an exception, shouldn't mapError return a rejected promise for us to use? It looks like the promise that actually returns from chainError is totally unresolved but as it's been a while since I worked on this library, I'm struggling to see why.

It fails the test because the returned promise will yield a consequential error and not the root cause as the reason for rejection.
When f throws e1 it is is fed to the second mapError's handler. Since e1 does not implement map, a TypeError e2 is thrown. e2 ends up as the reason for rejection.
I can change the test to get rid of the root cause requirement, but I think it's a worthwhile property.

Of course: the time outs from the tests were throwing but once I removed the assertion that the exception types must be exact then I could see the second (somewhat useless) TypeError coming through.
I've rebased your branch against master and altered chain to match the chainError exception (the lack of symmetry was making me suspicious), you can see this in #9

As for empty, you're right that it only works on resolved promises at the moment. See https://github.com/fantasyland/fantasy-land#empty-method for the specification from Fantasy Land. As long as we can guarantee the Monoid property of p.concat(p.empty()) == p.empty().concat(p) == p, we should be good.

I guess the implementation could be changed to look as follows (which looks to be robust wrt. type errors).
/* empty :: Promise e a -> Promise e a */
Promise.prototype.empty = function () {
    return this.map(function (value) {
        return value.empty ? value.empty() : value.constructor.empty();
    });
};

Anyways, with I'm happy #9 and propose closing this PR.


add example for additional nodes in plugin

I accepted the CLA. Do I have to make something else to have the checks pass?


[Github] Remove duplicate gad_source from ignored parameter list

1. Why is this change necessary?
Parameter gad_source in shopware.http_cache.ignored_url_parameters is declared twice.
2. What does this change do, exactly?
Remove duplicate
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

Imported from Github. Please see: https://github.com/shopware/shopware/pull/5342

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39419
[created from NEXT-39419, comment 509775]

[public]

Status Change: Open

This issue is ready for implementation.
[created from NEXT-39419, comment 509792]

[public]

Status Change: In Progress

Work on this issue has started. It is now being implemented.
[created from NEXT-39419, comment 509793]

[public]

Status Change: In Review

Work on this ticket is complete and is now pending review.
[created from NEXT-39419, comment 509795]

[public]

FixVersion Change: <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>.
[created from NEXT-39419, comment 509794]

[public]

Status Change: Resolved

The ticket has been successfully completed; the solution is implemented and verified.
[created from NEXT-39419, comment 510040]


[FEATURE] Add Apache Kafka as an Event Interface alongside MQTT for Enhanced Message Processing and Reliability

Description:
Currently, our system provides an MQTT-based event interface. To improve flexibility and compatibility, especially in larger deployments, adding Apache Kafka as an alternative event interface would be highly beneficial.
Motivation
Integrating Kafka as an additional message broker would allow us to leverage Kafka’s capabilities across both repositories and registries. Kafka offers several key advantages that would enhance our event processing:

Commit-based Acknowledgment: Kafka allows consumers to confirm message processing through a commit, ensuring reliable delivery and processing confirmation. This feature would provide a robust mechanism to ensure that each event is fully processed, adding a layer of reliability over MQTT.
Scalability and Performance: Kafka’s architecture is designed to handle high-throughput, low-latency data feeds, making it ideal for applications that may require scaling over time.
Standardization: Kafka is widely used in the industry and would allow users to standardize their message processing infrastructure without needing to switch brokers for different parts of the system.

Proposed Solution

Develop an event interface for Kafka that can utilize Kafka’s advanced features, such as commit-based acknowledgments, to enhance the reliability and robustness of message processing.
Ensure Kafka can be applied across both registries and repositories for seamless integration.

I am interested in taking on the implementation of this feature.
Thank you for considering this enhancement!

523


sort transactions in ascending order

Currently the order of transaction is descending, for a transaction history an ascending order makes more sense.

I believe this is done?


Closed accounts get rating deleted

This causes issues all over the place as many calls expect that the rating of a player exist as integer value

The problem here is that some admin tools in heltour fail when players have no rating.


Permission denied error when attempting to install ethereumjs-testrpc

Expected Behavior
I expect it to install as stated in the installation instructions
Current Behavior
When I run:
sudo npm install -g ethereumjs-testrpc
I get this:
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b master https://github.com/debris/bignumber.js.git /home/fappycow/.npm/_cacache/tmp/git-clone-fe66107c npm ERR! /home/fappycow/.npm/_cacache/tmp/git-clone-fe66107c/.git: Permission denied npm ERR!  npm verb exit [ 1, true ]
Possible Solution
I tried running:
sudo npm install --unsafe-perm --verbose -g ethereumjs-testrpc
I also tried to clean my cache with sudo npm cache clean --force
and it seemed to just make the problem worse
Context
It has affected my sleep. I can't get this resolved.
Your Environment

Server type and version: nodejs and npm: 8.1.2 and 5.0.3 respectively
Operating System and version: Ubuntu 16.04

Closing due to inactivity/age


build: add Envelope method to tx builder

Add an Envelope method to TransactionBuilder to make it convenient
to sign transactions with externally-managed private keys. For most use
cases the current interface is ergonomic by creating an envelope builder
in the Sign method.
But if you're not managing private keys in the same application,
it's a little more cumbersome. One can either call Sign without any
signers, or manually Init and mutate a new transaction envelope
builder.
With this change, it's convenient to sign using custom signer
implementations that implement the envelope mutator interface.
env, err := tx.Envelope(externalSigner)

Or even sign with multiple keys, including in-memory seeds:
env, err := tx.Envelope(
        externalSigner,
        build.Sign{seed},
)

I'm also curious if y'all have any thoughts on exposing access to a TransactionEnvelopeBuilder's inner TransactionBuilder. It's already indirectly exposed through MutateTX. It would make it more convenient for implementing the TransactionEnvelopeMutator interface for the purpose of signing transactions.

@howardtw

@bartekn what do you think about exporting child here?
type TransactionEnvelopeBuilder struct {
	E *xdr.TransactionEnvelope

	child *TransactionBuilder
}


“-” ahead of time on topbar

Can you please remove the "-" ahead of time on topbar?
Thanks!

the - indicates that the heat is overdue and therefore the timer counts up again instead of down. I see no reason to change that.
./Klaas


Node doesn‘t reset msg.CurrentCount if queue is empty

If the queue is empty, the node still lists 1 message in the queue.
msg.CurrentCount still has 1

Hi, I am not sure I understand your issue correctly. The msg.CurrentCount represents the number of msg sent within the timeframe. In the animation shown in the description it represents the number on top of the arrows when the msg is forwarded through the ratelimiter.
If you would like the status of the queue, you can do this by sending a control msg to the ratelimiter node with msg.payload == "status" and get msg.payload.buffer_len in return.

Enable control mode:
Input: {"payload":"status","topic":"control"}
Output: {"payload":{"buffer_len":0,"timeoutLinkedIDs_len":0},"topic":"control"}

Example flow:

[{"id":"4a88d36b920e48f5","type":"rate-limiter","z":"d794394809627697","delay_action":"ratelimit","rate":"2","nbRateUnits":"10","rateUnits":"second","drop_select":"queue","addcurrentcount":true,"name":"","outputs":"1","buffer_size":"0","buffer_drop":"buffer_drop_new","emit_msg_2nd":false,"control_topic":"control","version":0.0018,"x":700,"y":1000,"wires":[["1ec4dca9236159cd"]]},{"id":"332a561118279e35","type":"debug","z":"d794394809627697","name":"status","active":true,"tosidebar":true,"console":false,"tostatus":true,"complete":"payload","targetType":"msg","statusVal":"payload.buffer_len","statusType":"msg","x":1070,"y":1000,"wires":[]},{"id":"1ec4dca9236159cd","type":"switch","z":"d794394809627697","name":"","property":"topic","propertyType":"msg","rules":[{"t":"eq","v":"control","vt":"str"},{"t":"else"}],"checkall":"true","repair":false,"outputs":2,"x":910,"y":1000,"wires":[["332a561118279e35"],["7c3587287bbd5706"]]},{"id":"7c3587287bbd5706","type":"debug","z":"d794394809627697","name":"messages","active":false,"tosidebar":true,"console":false,"tostatus":true,"complete":"true","targetType":"full","statusVal":"CurrentCount","statusType":"msg","x":1090,"y":1060,"wires":[]},{"id":"ea9762449aa9042d","type":"function","z":"d794394809627697","name":"burst","func":"let counter = 0;\nvar myObj = msg.payload;\nfunction waitSixty () {\n    setTimeout(()=>{\n        context.set(\"timeout\", false);\n    },msg.duration || 5000);\n}\nfunction repeatThirty (variable) {\n    var interval = setInterval(()=>{\n        counter++;\n        node.send([{ payload: variable, \"count\": counter}, null]);\n        var timeout = context.get(\"timeout\");\n        if (!timeout) {\n            clearInterval(interval);\n            node.send([null, { payload: counter, \"count\": counter }]);\n        }\n    },msg.interval || 1000);\n}\ncontext.set(\"timeout\",true);\nwaitSixty();\nrepeatThirty(myObj);\nreturn;","outputs":2,"timeout":"","noerr":0,"initialize":"","finalize":"","libs":[],"x":470,"y":1000,"wires":[["4a88d36b920e48f5"],[]]},{"id":"02fbcc6c42693832","type":"inject","z":"d794394809627697","name":"trigger 5 messages","props":[{"p":"payload"},{"p":"duration","v":"500","vt":"num"},{"p":"interval","v":"100","vt":"num"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":310,"y":1000,"wires":[["ea9762449aa9042d"]]},{"id":"bf82472d859602a7","type":"inject","z":"d794394809627697","name":"check status","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"control","payload":"status","payloadType":"str","x":450,"y":1060,"wires":[["e577dc8f67170a15","4a88d36b920e48f5"]]},{"id":"e577dc8f67170a15","type":"debug","z":"d794394809627697","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":630,"y":1060,"wires":[]}]

Works Perfect 👍


Hi, v2.0 alpha on linux compile problem

Hi, I'm trying the v2.0 on ubuntu20.04,  after install all depedenties on prerequisites doc,  run "cargo tauri dev", I got 3 errors, and these libraries can't be install by 'apt install ' where can't find the required version, error info:

error: failed to run custom build command for `glib-sys v0.18.1`

Caused by:
  process didn't exit successfully: `/mnt/data/client/tauri-test/src-tauri/target/debug/build/glib-sys-fff6c8c2a997afba/build-script-build` (exit status: 1)

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags glib-2.0 glib-2.0 >= 2.70

  The system library `glib-2.0` required by crate `glib-sys` was not found.
  The file `glib-2.0.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `glib-2.0.pc`.

warning: build failed, waiting for other jobs to finish...
The following warnings were emitted during compilation:

warning:

error: failed to run custom build command for `gio-sys v0.18.1`

Caused by:
  process didn't exit successfully: `/mnt/data/client/tauri-test/src-tauri/target/debug/build/gio-sys-906b2fba43046bbe/build-script-build` (exit status: 1)

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags gio-2.0 gio-2.0 >= 2.70

  The system library `gio-2.0` required by crate `gio-sys` was not found.
  The file `gio-2.0.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `gio-2.0.pc`.

The following warnings were emitted during compilation:

warning:

error: failed to run custom build command for `gobject-sys v0.18.0`

Caused by:
  process didn't exit successfully: `/mnt/data/client/tauri-test/src-tauri/target/debug/build/gobject-sys-f1af7ebd93d09388/build-script-build` (exit status: 1)

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags gobject-2.0 gobject-2.0 >= 2.70

  The system library `gobject-2.0` required by crate `gobject-sys` was not found.
  The file `gobject-2.0.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `gobject-2.0.pc`.

The following warnings were emitted during compilation:

warning:

error: failed to run custom build command for `soup3-sys v0.5.0`

Caused by:
  process didn't exit successfully: `/mnt/data/client/tauri-test/src-tauri/target/debug/build/soup3-sys-69aab4a189acf16a/build-script-build` (exit status: 1)

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags libsoup-3.0 libsoup-3.0 >= 3.0

  The system library `libsoup-3.0` required by crate `soup3-sys` was not found.
  The file `libsoup-3.0.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `libsoup-3.0.pc`.

Please give me some help, thanks.

Because Tauri requires webkitgtk 4.1 now (it was 4.0 in v1) the minimum version was increased to Ubuntu 22.04 unfortunately.

Is this mean the ubuntu develop env must >= ubuntu 22.04?   or I can install the 4.1 version on ubuntu 20.04?  which I don't find install method,  If yes, I will go to try install again..

you have to use ubuntu 22.04. I am not aware of a method to install 4.1 on ubuntu 20.04 (not counting vms and vm like things like docker)

ok. got it!  thankyou

ok. got it! thankyou

Hello, have you been running since you switched to 22.04?


Add User-Agent match for Windows 10 client

This change make the server compatible with a Windows 10 default client

Why is this not merged?

I had issues with creating/modifying folders on Windows 10, this fix completely solved the issues.

Please merge this and #25. I know maintaining software is a lot of work, but these PRs are literal single-line fixes with no side-effects that can be reviewed in seconds. Without this PR this image is useless to anyone that needs to support a windows installation.

@s-ol https://twitter.com/petewht/status/1100327258449997829 the dev team was made redundant; as far as I understand there's no one to answer your request at this company anymore.


Remove "text-lowercase" from content-header

Please consider removing the "text-lowercase" class from entity name in crud blades.
In German nouns are always written upper case, but I can't define the entity name in CrudController this way because it is changed in the blades.
Creating individual blades for this seems to be too much.
Is the "text-lowercase" necessary? Am I missing something?

You can remove it with JavaScript?

I'm sorry, but I don't understand your solution. How am I supposed to use JavaScript for this without defining individual blades?

Is there any concerns removing it?
Any language where we could run into Problems?
I only know german where this is really an issue.
text-uppercase for the beginning of the sentences (etc. ) would still be there and make lowercase entity names uppercase. but making uppercase defined names lowercase seems odd to me.

Totally agreed - I had to recreate the blade files myself a few times, because of this.
@OliverZiegler 's PR fixes this, and I've just merged it into dev - #667
Cheers!


Updated fr.yml for better translations

Many strings were missing from the file.
I'm not sure I got all of these strings right, because the context is not always obvious, but hopefully it's still an improvement.

Thank you, @Brachamul :+1:


@conda-forge-admin, please add user @dhirschfeld

Additional comment:
I'm happy to help out with the maintenance here...

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @dhirschfeld in conda-forge/mkdocs-material-extensions-feedstock#7.


[Rest Server] add cluster info api

Coverage increased (+0.03%) to 51.232% when pulling a2d58bcb6316a4cbd8af25cffebf13c34bf0558f on qinsu/rest/info into 7bd2477af4cc478a5891d9f65288a5aa60b57f42 on master.


Latitude is not properly converted to degrees from NMEA message

The NMEA message
$GPRMC,153007,A,5050.10288,N,00419.91808,E,000.1,078.9,100217,,,A*75
return a latitude of 6.xxx° while it should be 4.xxx°
I've created a fork on which I'll fix the conversion

Thx for your fix, I will put the fix in the next release!


Add plumelib_adjacent script

Merge after #352.  (Or, merge instead of #352, after approving #352, in order to avoid merge conflicts.)
Before merging this, please run the pipeline to update all the results.  That should also make CI pass.
Here is the motivation for this pull request:  It is important to update the results of strategy "X" according to the results of "X + plume-lib-fixups", where "plume-lib-fixups" is guaranteed to be correct.  This pull request adds "adjacent + plume-lib-fixups", in order to enable proper adjustment of the results of "adjacent".

@mernst I think you understand wrongly what import, adjacent and version numbers are. It's not a x+plumelib strategy but a partial way of running plumelib.

@mernst I think you understand wrongly what import, adjacent and version numbers are. It's not a x+plumelib strategy but a partial way of running plumelib.

Please see the email thread.  You are confusing implementation details with concepts.

@mernst There is no diff here anymore after reverting test results and merging main. I am not sure what exactly you want but it would be great to add the missing script here.

I think this is ready to be merged.  How do I update the reproducibility tests?

@mernst First plumelib needs to be fixed and then we can add new tools

Can you tell me what is necessary and how I can double-check it?  I think this pull request resolves the problem with plume-lib not running, which I corrected in https://github.com/benedikt-schesch/AST-Merging-Evaluation/pull/353/commits/083d6d4346d17872e2b914768d325468f3c4463e.

@mernst This branch does worse than #355 which simply uses an older hash and both branches do worse than #358 which simply uses the same older hash for pluemlib but it uses the main branch code. I look at git merge ort for this comparison.


Block not found at get_weight/3

Despite tackling #1315 the addition of the Maximum clock disparity into the equation to calculate future slots appeared to not be enough. After running a test with #1318 branch, the node was stable for ~40hours before the following happened:
2024-10-06 02:33:12.006	[Libp2p] Slot transition
2024-10-06 02:33:00.585	[Fork choice] Failed to add block: block is from the future
2024-10-06 02:33:00.585	[PendingBlocks] Saving block as invalid after ForkChoice.on_block/2 error: block is from the future
2024-10-06 02:33:00.529	[Optimistic Sync] Waiting 15.0 seconds to discover some peers before requesting blocks.
2024-10-06 02:33:00.529	[Fork choice] Adding new block
2024-10-06 02:33:00.468	Last message: {#Port<0.15>, {:data, <<10, 242, 74, 10, 40, 47, 101, 116, 104, 50, 47, 100, 51, 49, 102, 54, 49, 57, 49, 47, 98, 108, 111, 98, 95, 115, 105, 100, 101, 99, 97, 114, 95, 49, 47, 115, 115, 122, 95, 115, 110, 97, 112, 112, 121, 26, ...>>}}" mfa=:gen_server.error_info/8 pid=#PID<0.444.0>
2024-10-06 02:33:00.468	    (elixir 1.16.2) lib/stream.ex:1828: Enumerable.Stream.do_each/4
2024-10-06 02:33:00.468	    (elixir 1.16.2) lib/enum.ex:4839: Enumerable.List.reduce/3
2024-10-06 02:33:00.468	    (elixir 1.16.2) lib/stream.ex:1816: anonymous fn/3 in Enumerable.Stream.reduce/3
2024-10-06 02:33:00.468	    (elixir 1.16.2) lib/enum.ex:4396: anonymous fn/3 in Enum.reduce/3
2024-10-06 02:33:00.468	    (lambda_ethereum_consensus 0.1.0) lib/lambda_ethereum_consensus/fork_choice/head.ex:50: anonymous fn/6 in LambdaEthereumConsensus.ForkChoice.Head.get_weight/3
2024-10-06 02:33:00.468	    (elixir 1.16.2) lib/map.ex:450: Map.put_new_lazy/3
2024-10-06 02:33:00.468	    (lambda_ethereum_consensus 0.1.0) lib/types/store.ex:120: Types.Store.get_ancestor/3
2024-10-06 02:33:00.468	    (lambda_ethereum_consensus 0.1.0) lib/lambda_ethereum_consensus/store/blocks.ex:72: LambdaEthereumConsensus.Store.Blocks.get_block!/1
2024-10-06 02:33:00.468	** (RuntimeError) Block not found: 0x75e7d39a4266b27fb6260f64e2903e29e7de4fd0cfbc3af8e58fa28f7aaa0afa
2024-10-06 02:33:00.468	ts=2024-10-06T05:33:00.468 level=error msg="GenServer LambdaEthereumConsensus.Libp2pPort terminating
2024-10-06 02:33:00.446	[Fork choice] Block processed. Recomputing head.
2024-10-06 02:33:00.226	[Fork choice] Adding new block
2024-10-06 02:33:00.146	[Gossip] Block received, block.slot: 6038265.
2024-10-06 02:33:00.017	[Libp2p] Slot transition
2024-10-06 02:32:49.096	[Fork choice] Recomputed head
2024-10-06 02:32:49.096	[Fork choice] Added new block
2024-10-06 02:32:48.814	[Fork choice] Block processed. Recomputing head.
2024-10-06 02:32:48.625	[Fork choice] Adding new block

Things to have into account:

The block was marked as invalid while it just needed to wait 1 slot (if it really came before the slot transition)
In reality it came just after the slot transition! so it shoulded just work
Marking a canonnical block as invalid stops the following state transitions. We shouldn't mark a block as invalid if its from the futurre, maybe just leave them where it was.
We need a way to debug this in situ, because as far as the logs shows, the block was processed exactly at the time its slot was happening, so there is no chance it was from the future

The points detailed are an explanation of why the node stoped processing new blocks, but the issue was not caused by the block in the future error as first thought, instead it was caused by a missing block in the store, which after a restart of Libp2p made the store point again at the initial checkpoint and that caused the future block. The cause is really the missed block at the get_weight function.


Portfolio project deployment

In this milestone, I:

Worked using Github Pages to deploy my project.
Checked my Portfolio Online.
Updated my README file with the LIVE section.
Fixed some linters.

Thanks a lot for your time, Mr @gemmen29
Best wishes,
Javier.-


Added ElectroKart Ecommerce React Project

Closes: #656

Title : Adding Ecommerce Project
Name: : Ayushmaan Agarwal
Idenitfy yourself: : GSSOC

Describe the add-ons or changes you've made 📃
I have added this project to the Intermediate projects under react Projects
How Has This Been Tested? ⚙
It's been tested by Checking the code on any changes
Screenshots 📷
https://github.com/user-attachments/assets/280628b7-f982-4106-8abf-775429c78ca3
Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney sir i have added this to read me i think now i follows all guidelines


General improvements

This pull request includes the following changes:

Adds some #include statements to ensure the extra integer types (e.g. uint8_t) and size_t are defined
Changes the type of buff to void *
Adds inline to the function definitions.

Thank you for your PR and so sorry for late reply. Yes, #include <cstdint> and inline keyword is much better! But now I use much faster and flexible library so I will update this repository to the wrapper of such library. Thanks again!


Update list of official plugins in the docs

Description
There were several newer plugins missing from the list in the docs, so I thought it'd be helpful to update it.
I did notice while updating the list that react-static-plugin-favicons is listed under 'official plugins', but actually seems to be maintained outside of the main React Static repo - this seemed a bit misleading, so I seperated it out. That said, this does raise the question of 'should this repo maintain a list of unofficial plugins?' - happy to make changes if you think the answer is no or if you want me to merge the lists back together!
Changes/Tasks

Added all official plugins to the list in the docs.
Moved react-static-plugin-favicons to a seperate list of unofficial plugins.

Motivation and Context
The main motivation for this was discoverability - I spent a little time trying to set up MDX for myself, only to realize there was already a plugin for it :p
Types of changes

[x] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the documentation accordingly
[ ] I have updated the CHANGELOG with a summary of my changes (Do docs changes require a changelog entry? I will update it if so!)
[ ] My changes have tests around them (N/A)

nicely done!


extend replacementMap.json

Codecov Report

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

@@          Coverage Diff          @@
##           master   #262   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines          72     72
  Branches       10     10
=====================================
  Hits           72     72

Impacted Files
Coverage Δ

lib/dateCatcher.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix: get enum values without valueOf() (#387)

to avoid silent MissingPropertyException thrown by Groovy

Thanks for double checking, I thought the issue was avoided by doing it this way. I'll close this pr then as it does not resolve the issue.


Release 2.3.2

Questions
Answers

Description?
This release fixes critical errors related to the price formatting that affects payment modules

Type?
bug fix

BC breaks?
no

Deprecations?
no

How to test?
The only part modified in the module is related to sending the order confirmation email to the merchant

@PrestaShop/qa-team kindly reminder that this one is a critical bug fix :D

Hello @kpodemski ,
Thanks for the Release ! Looks good to me, QA ✅

Thank you @florine2623 😃


TypeError while doing server-rendering with minified version

In the dist version of react-datepicker (minified) there is this:
return je.Utils=("undefined"!=typeof window?window:t).PopperUtils

which results in TypeError: Cannot read property 'PopperUtils' of undefined
Perhaps (and it fixes the problem) the minified version should also have global there instead of t, like this:
return je.Utils=("undefined"!=typeof window?window:global).PopperUtils

...must be popper's issue? webpack issue? ...??

Were you able to solve this issue? I am also getting it when doing server rendering...

When using dist/react-datepicker.min.js, as it already comes packed and
minified, the global variable somehow gets lost, producing an error:
TypeError: Cannot read property 'PopperUtils' of undefined
To prevent this I'm directly using lib/datepicker.js instead.
You can either do import DatePicker from 'react-datepicker/lib/datepicker' or fork it and change package.json:
--- react-datepicker/package.json
+++ react-datepicker/package.json
@@ -5,7 +5,7 @@
   "version": "0.55.0",
   "license": "MIT",
   "homepage": "https://github.com/Hacker0x01/react-datepicker",
-  "main": "dist/react-datepicker.min.js",
+  "main": "lib/datepicker.js",
   "style": "dist/react-datepicker.min.css",
   "files": [
     "*.md",

Thank you, I had changed the minified version as you first suggested, but importing directly from source is better.
Anyway, shouldn't the package mantainers take notice of this? Seeing as the issue is closed, I don't see this getting fixed, and it breaks server rendering for someone who isn't aware of importing directly.

Who knows.... I'll reopen to see if this could get fixed somehow.
To me, IMHO, I believe package maintainers should always provide src with ES6/ES7 modules right there, so users could use any packaging they want when they have to and import directly from sources (and it should be the default). I actually think providing minified dist files (or even lib) is more trouble than we'd want.

Yeah, you are probably right, I wasn't even aware I was importing from the minified version by default, it can be confusing.


improve docs: useToggle demo link

Added a demo link for useToggle

Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update repository URL for UbxGps library

Hello!
I own the UbxGps library and it's been in the registry for a while, but with my previous GitHub username (1oginov).
I changed it to loginov-rocks and just aligning a link to the repository.
Link in the library.properties has already been updated: https://github.com/loginov-rocks/UbxGps/blob/main/library.properties#L8
Thank you!

Hello @loginov-rocks. The requested change is now in progress.
Unlike submissions, this type of request is still handled manually. The Library Manager index's maintainer occasionally comes through to clear all the outstanding requests and closes those issues/PRs when that is done. So you can get a notification if you're following the linked PR:
https://github.com/arduino/library-registry/pull/211
After that, you can monitor the indexing of the library via its logs web page:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager


Fix docstring

Codecov Report

Merging #24 into master will increase coverage by 0.02%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage    67.9%   67.92%   +0.02%
==========================================
  Files          30       30
  Lines        1346     1347       +1
==========================================
+ Hits          914      915       +1
  Misses        432      432

Impacted Files
Coverage Δ

src/component.jl
86.25% <ø> (ø)
:arrow_up:

src/components.jl
96.19% <100%> (+0.03%)
:arrow_up:

src/system_data.jl
88.66% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix: ctrader_sign_up page

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

@mayuran-deriv title please :)


Workspaces doesn't interact well with FancyZones

Microsoft PowerToys version
0.84.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Workspaces
Steps to reproduce
Create a Workspace with several apps
Configure FancyZones
Open a Workspace from a desktop icon
Attempt to use the FancyZone drag to zone feature (click shift drag)
✔ Expected Behavior
Expect window being dragged to highlight the nearest zone
❌ Actual Behavior
FancyZones are ignored for windows opened by Workspaces. To restore the expected behavior, windows opened by Workspaces must be closed and re-opened individually.
Other Software
No response

PowerToysReport_2024-09-06-12-00-57.zip

/dup #34566


[BUG] always updating roblox on startup despite already updated

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.
[X] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v.2.8.0
What problem did you encounter?

Everytime no matter when its already updated or not today, it always updates on startup.
auto update is off and it still does this.
Bloxstrap Log
N/A

same here, really need a fix

auto update is off and it still does this.

That's for auto updating Bloxstrap. Not Roblox.
Can you open go to Bloxstrap's logs folder at %localappdata%\Bloxstrap\Logs, create a zip archive of all the log files, upload it somewhere, and send a link to it here?

https://www.mediafire.com/file/hnqmva38fnxorvm/Logs.zip/file

ok now today it doesnt for some reason- this is really weird

You didn't have a single successful launch on the day you reported this issue. Are you aware of that?


Delete groups in openshift

If a group gets deleted in one of the external provides (in my case Azure) currently the group will keep existing in openshift.
Could it be possible to also check if a group got deleted and then also delete it in openshift?

anything is possible, code would have to be added which checked the groups it wants to sync, with the groups it currently has, and then delete any groups not in the new list of groups.

Duplicate of #34


Improve Vec usage with Vec::with_capacity

Where possible declare Vec size to avoid reallocation of vector.
https://doc.rust-lang.org/std/vec/struct.Vec.html#capacity-and-reallocation

Fixed with f6ff11e.


Dev Option to setup the Cropping ratio

Hello,
I'm wondering if an option to setup the cropping ratio exists ?
I mean to be able to chose ratio between : free cropping, 1:1, 16:9, 4:3....
If yes, how to do that ? If not, I think it will be a must to have to set cropping to a predefined ratio.
Regards
Awazleon

Those are the initial options. Unfortunatelly you cannot fix the ratio at this stage. But if you open a ticket for feature request we will be happy to add tha soon. For now we are close this PR which seems by mistake.
    // Default configuration
    var defaults = {
        area: [ 800, 600 ],
        crop: [ 200, 150 ],
        value: null,
        onload: null,
        onchange: null,
        remoteParser: null,
        allowResize: true,
        text: {
            extensionNotAllowed: 'The extension is not allowed',
        },
        eventListeners: {}
    };


Massive delay in Locals window after copying values

Clicking a Value field for an item in Locals, then copying the resulting selection and hitting escape or clicking away, causes the UI to freeze for a noticeably long time.

Clicking a Value field for an item in Locals, then copying the resulting selection and hitting escape or clicking away, causes the UI to freeze for a noticeably long time.

Issue is fixed in WinDbgX version 1.2410.11001.0


Update Xcode project setting Text-Based InstallAPI Verification Mode

Update Xcode settings TAPI_VERIFY_MODE to Errors Only.
Xcode setting reference

Closing PR. @bzbarsky-apple is going to properly fix the linking.


now skip-button is fixed

[ ] it probably have merge conflict with main (cause i fix what we merge earlier to the main)

perfect


Fix travis build test to include "go fmt" and "go vet"

Includes both "go fmt" and "go vet" as part of the travis CI build and fixes all reported warnings in the process.

Awesome. I'm not entirely sure if go vet couldn't hit us with false positives in the future but lets wait and see.